Feature/990 chain abstraction

[theblockstalk]

software API

Polymorphic classes implement chain, account and transaction features needed

storage

The only thing that needs to be stored to be able to restore an account is the private key.

When the user creates an account or login

1. Generate the deterministic seed with generateSeedFromPassword()
2. for each chain a. generates the private key from the seed using generatePrivateKeyFromSeed() b. For each chain, check if the account exists (if needed - Ethereum is not needed) c. Store the private key in the persistent storage d. create an IAccount for each chain

when the application opens and the App initializes, it should check for stored private keys and create a new IAccount for each chain with an account

[sadiabbasi]

software API

Polymorphic classes implement chain, account and transaction features needed

storage

The only thing that needs to be stored to be able to restore an account is the private key.

When the user creates an account or login

1. Generate the deterministic seed with generateSeedFromPassword()
2. for each chain a. generates the private key from the seed using generatePrivateKeyFromSeed() b. For each chain, check if the account exists (if needed - Ethereum is not needed) c. Store the private key in the persistent storage d. create an IAccount for each chain

when the application opens and the App initializes, it should check for stored private keys and create a new IAccount for each chain with an account

is it okay to store private key in the storage?

[theblockstalk]

software API

Polymorphic classes implement chain, account and transaction features needed

storage

The only thing that needs to be stored to be able to restore an account is the private key. When the user creates an account or login

1. Generate the deterministic seed with generateSeedFromPassword()
2. for each chain a. generates the private key from the seed using generatePrivateKeyFromSeed() b. For each chain, check if the account exists (if needed - Ethereum is not needed) c. Store the private key in the persistent storage d. create an IAccount for each chain

when the application opens and the App initializes, it should check for stored private keys and create a new IAccount for each chain with an account

is it okay to store private key in the storage?

depends how the are stored of course. If they are on the users device they are pretty good.

• Especially if there is no API to export them
• especially if they are stored using encryption at rest
• especially as they are stored in protected storage (offered by most mobile operating systems)

[theblockstalk]

https://github.com/Tonomy-Foundation/Tonomy-ID-SDK/issues/336 this issue is blocking the Veramo library from compiling. So I reverted to not use these libraries