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

fix: More minor edits in account interface #982

Merged
merged 3 commits into from
Nov 29, 2023
Merged

fix: More minor edits in account interface #982

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c181b81
Minor edits in account interface
stoobie Nov 29, 2023
92c8ce3
Update components/Starknet/modules/architecture_and_concepts/pages/Ac…
stoobie Nov 29, 2023
37ef846
Update components/Starknet/modules/architecture_and_concepts/pages/Ac…
stoobie Nov 29, 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
7 changes: 4 additions & 3 deletions components/Starknet/modules/architecture_and_concepts/pages/Accounts/approach.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,8 @@ For more information on accounts in Ethereum, see link:https://ethereum.org/en/d

A nonce serves two important roles:

* It guarantees transaction hash uniqueness (this is important for good UX)
* It provides replay protection to the account (since the signature refers to a particular nonce, the transaction can't be replayed by a malicious party)
* It guarantees transaction hash uniqueness, which is important for a good user experience.
* It provides replay protection to the account. Because the signature refers to a particular nonce, a malicious party cannot replay the transaction.

As seen above, Starknet currently determines the sequential nonce structure at the protocol level. In the future, Starknet will consider a more flexible design, extending account abstraction to nonce management, also referred to as _nonce abstraction_.
stoobie marked this conversation as resolved.
Show resolved Hide resolved
stoobie marked this conversation as resolved.
Show resolved Hide resolved

As seen above, Starknet currently determines the nonce structure (sequential) at the protocol level. In the future, Starknet will consider a more flexible design, extending account abstraction to nonce management (previously referred to as "nonce abstraction").
Loading