this file implements the encrypted data store at rest.

create an encrypted wallet using electrum recovery words.

create an encrypted wallet using using random data.

create an encrypted wallet using using random data.

create an encrypted wallet using using random data.

extract 12 byte nonce from the data and deseal the data.

this function is used to encrypt/decrypt payment id as the operation is symmetric XOR, is the same in both direction.

all data in encrypted within the storage using this, PERIOD all data has a new nonce, appended to the the data , last 12 bytes.

generate user account using recovery seeds.

generate keys for view only wallet.

generate keys for view only wallet.

generate key from password.

generate keys from using random numbers.

generate keys from seed which is from the recovery words or we feed in direct.

stores height to block hash mapping for later on syncing.

used to encrypt payment id.

indices of all funds ready to spend.

stores all incoming funds, key is global output index encrypted form.

stores all tx where our funds were spent.

funds sorted by block height.

each tx id is a bucket.

indices of all funds already spent.

funds spent by block height.

mapping which output -> spent where.

used to track height to block hash mapping.

used to track which funds have been spent (only on chain ) and which output was consumed.

all metadata is stored in this bucket.

any notes attached.

this contains all TXs in which we have spent OUR FUNDS.

all payment ID to output index will have this string prepended,.

to randomly choose ring members when transactions are created.

used to keep secret keys for any tx this wallet has created.

used to keep secret keys for any tx this wallet has created.

all TX to output index will have this string prepended.

all main chain txs are stored in this bucket.

this global variable should be within wallet structure.

see this https://godoc.org/golang.org/x/crypto/pbkdf2.

all random outputs are stored within wallet in this form to be used as ring members.

all components requiring access to wallet must use , this struct to communicate this structure must be update while mutex.

this structure is kept by wallet.

this is stored in disk in encrypted form.