From c181b814cb04be35f34b9fd20f844db0e19427a2 Mon Sep 17 00:00:00 2001 From: Steve Goodman <39279277+stoobie@users.noreply.github.com> Date: Wed, 29 Nov 2023 15:36:45 +0200 Subject: [PATCH 1/3] Minor edits in account interface --- .../architecture_and_concepts/pages/Accounts/approach.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/components/Starknet/modules/architecture_and_concepts/pages/Accounts/approach.adoc b/components/Starknet/modules/architecture_and_concepts/pages/Accounts/approach.adoc index 3a1c4440a0..5ed1ec5133 100644 --- a/components/Starknet/modules/architecture_and_concepts/pages/Accounts/approach.adoc +++ b/components/Starknet/modules/architecture_and_concepts/pages/Accounts/approach.adoc @@ -30,7 +30,7 @@ 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 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"). +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_. From 92c8ce3075e5ec4d324f74895810f64ece977660 Mon Sep 17 00:00:00 2001 From: Steve Goodman <39279277+stoobie@users.noreply.github.com> Date: Wed, 29 Nov 2023 15:42:34 +0200 Subject: [PATCH 2/3] Update components/Starknet/modules/architecture_and_concepts/pages/Accounts/approach.adoc --- .../architecture_and_concepts/pages/Accounts/approach.adoc | 1 + 1 file changed, 1 insertion(+) diff --git a/components/Starknet/modules/architecture_and_concepts/pages/Accounts/approach.adoc b/components/Starknet/modules/architecture_and_concepts/pages/Accounts/approach.adoc index 5ed1ec5133..1e3c8dfa8c 100644 --- a/components/Starknet/modules/architecture_and_concepts/pages/Accounts/approach.adoc +++ b/components/Starknet/modules/architecture_and_concepts/pages/Accounts/approach.adoc @@ -34,3 +34,4 @@ A nonce serves two important roles: * 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_. + From 37ef846840f553440c8f24755d15f127af5399f6 Mon Sep 17 00:00:00 2001 From: Steve Goodman <39279277+stoobie@users.noreply.github.com> Date: Wed, 29 Nov 2023 16:30:32 +0200 Subject: [PATCH 3/3] Update components/Starknet/modules/architecture_and_concepts/pages/Accounts/approach.adoc --- .../architecture_and_concepts/pages/Accounts/approach.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/components/Starknet/modules/architecture_and_concepts/pages/Accounts/approach.adoc b/components/Starknet/modules/architecture_and_concepts/pages/Accounts/approach.adoc index 1e3c8dfa8c..4765abc122 100644 --- a/components/Starknet/modules/architecture_and_concepts/pages/Accounts/approach.adoc +++ b/components/Starknet/modules/architecture_and_concepts/pages/Accounts/approach.adoc @@ -33,5 +33,5 @@ A nonce serves two important roles: * 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_. +While 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_.