Accounts

Define a customer wallet state
The account contains complete information about a user's private wallet. It is linked by the intermediate key η\etaη
 derived from the spending key σ\sigmaσ
owned by the user. The holder of the spending key is called an account owner.
The account holds the current balance value and spent offset which separates all notes into spent and unspent. This is sufficient data to retrieve a wallet state.
An account is a tuple (d,Pd,i,b,e)(d, P_d, i, b, e)(d,Pd​,i,b,e)
 where:
​ddd
 (10 bytes) is a random diversifier which is updated every time an account is updated. It acts like a salt.
​PdP_dPd​
 (32 bytes) is diversified public key (a value derived from the ddd
 and intermediate key η\etaη
): Pd=η∗ToSubGroupHashE(Fr)(d)P_d = \eta * \text{ToSubGroupHash}_{E(F_r)}(d)Pd​=η∗ToSubGroupHashE(Fr​)​(d)
​
​iii
(6 bytes) is the spent offset. It separates used (spent) and unused notes in the Merkle tree . Note that indexes below iii
 are considered to be spent.
​bbb
(8 bytes) is the current account balance
​eee
(8 bytes) is an energy(XP) unit ("integral" account balance)
The raw account size is 64 bytes.
Account transaction data never appears unencrypted in a public field. Only the account owner can decrypt it.
Zero account
When a user creates their first transaction there will not be an existing account in the Merkle tree. In this case a zero account should be used where all fields are zero except η\etaη
.​
Technical Implementation - Previous
Accounts and Notes
Notes
Last modified 7mo ago