From c83bd19829582f307688493da764e115d3112306 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Adam=20Chuda=C5=9B?= Date: Wed, 5 Feb 2025 12:05:03 +0000 Subject: [PATCH] near-implicit nonce --- specs/DataStructures/Account.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/specs/DataStructures/Account.md b/specs/DataStructures/Account.md index 320e70730..8b66f49f6 100644 --- a/specs/DataStructures/Account.md +++ b/specs/DataStructures/Account.md @@ -119,7 +119,7 @@ An account with implicit account ID can only be created by sending a transaction - The account will be created with the account ID. - The account balance will have a transfer balance deposited to it. -- If this is NEAR-implicit account, it will have a new full access key with the ED25519-curve public key of `decode_hex(account_id)` and nonce `0`. +- If this is NEAR-implicit account, it will have a new full access key with the ED25519-curve public key of `decode_hex(account_id)` and nonce `(block_height - 1) * MULTIPLIER` (to address an issues discussed [here](https://gov.near.org/t/issue-with-access-key-nonce/749)). - If this is ETH-implicit account, it will have the [Wallet Contract](#wallet-contract) deployed, which can only be used by the owner of the Secp256K1 private key where `'0x' + keccak256(public_key)[12:32].hex()` matches the account ID. Implicit account can not be created using `CreateAccount` action to avoid being able to hijack the account without having the corresponding private key.