Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update wording on AA Deploying accounts #540

Merged
merged 2 commits into from
Jun 13, 2023
Merged

Update wording on AA Deploying accounts #540

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8e6c50f
Update wording on AA Deploying accounts
Jun 12, 2023
7b49d64
Merge branch 'dev' into james/Change-wording-on-deploy-new-account
JameStark Jun 13, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions ...architecture_and_concepts/pages/Account_Abstraction/deploying_new_accounts.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,9 +1,8 @@
[id="deploying_new_accounts"]
= Deploying new accounts

Since xref:documentation:starknet_versions:version_notes.adoc#version0.10.1[StarkNet version 0.10.1] the historical method of deploying accounts on StarkNet, the `deploy` transaction, has been removed.

It has now been replaced with the `deploy_account` transaction which allows you to deploy an account and pay fees from a pre-funded address (thus solving the issue of how to pay fees while not yet having a deployed account).
Starknet provides the `deploy_account` transaction in order to deploy new accounts to the
network.

## Deploy account transaction

Expand Down
6 changes: 4 additions & 2 deletions ...onents/StarkNet/modules/architecture_and_concepts/pages/Fees/fee-mechanism.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,8 @@ The only limitation on the sequencer (enforced by the Starknet OS) is that the a
Presently, the sequencer only takes into account L1 costs involving proof submission. There are two components affecting the L1 footprint of a transaction:

* xref:computation[Computational complexity]: the heavier the transaction, the larger its portion in the proof verification cost.
* xref:on-chain-data[On chain data]: L1 calldata cost originating from xref:../Data_Availability/on_chain_data.adoc[data availability] and L2→L1 messages.
* xref:on-chain-data[On chain data]: L1 calldata cost originating from xref:Data_Availability/on-chain-data.adoc[data availability]
and L2→L1 messages.

== Fee Units

Expand Down Expand Up @@ -98,7 +99,8 @@ The on chain data associated with a transaction is composed of three parts

==== Storage Updates

Whenever a transaction updates a key at the storage of some contract, the following xref:../Data_Availability/on-chain-data.adoc[data] reaches L1:
Whenever a transaction updates a key at the storage of some contract, the following xref:Data_Availability/on-chain-data.adoc[data]
reaches L1:

* Contract_address
* Number of updated keys in that contract
Expand Down