status-go/services/accounts
Sale Djenic c2b17acc07 feat: 5 functions added, the same as we had, but without pass verification (need for a keycard users)
The following three new functions introduced, for which password should be verified
on the client side (in case of a keycard user we don't have keystores to check pass):
- `AddAccountWithMnemonicPasswordVerified`
- `AddAccountWithMnemonicAndPathPasswordVerified`
- `AddAccountWithPrivateKeyPasswordVerified`
- `GenerateAccountPasswordVerified`
- `GenerateAccountWithDerivedPathPasswordVerified`

update
2022-10-28 13:27:55 +02:00
..
README.md Accounts data management (#1530) 2019-08-20 18:38:40 +03:00
accounts.go feat: 5 functions added, the same as we had, but without pass verification (need for a keycard users) 2022-10-28 13:27:55 +02:00
multiaccounts.go Use image server for all kind of images and integrate identity rings 2022-09-16 09:52:08 +01:00
out.json Add api method settings_getConfigs to retrieve list of configs in a batch quer 2019-08-22 17:32:44 +03:00
service.go Use image server for all kind of images and integrate identity rings 2022-09-16 09:52:08 +01:00
settings.go feat: add bio 2022-08-16 14:29:00 +02:00

README.md

Settings service

Settings service provides private API for storing all configuration for a selected account.

To enable:

  1. Client must ensure that settings db is initialized in the api.Backend.
  2. Add settings to APIModules in config.

API

settings_saveConfig

Parameters

  • type: string - configuratin type. if not unique error is raised.
  • conf: bytes - raw json.

settings_getConfig

Parameters

  • type: string

Returns

  • conf raw json

settings_saveNodeConfig

Special case of the settings_saveConfig. In status-go we are using constant node-config as a type for node configuration. Application depends on this value and will try to load it when node is started. This method is provided in order to remove syncing mentioned constant between status-go and users.

Parameters

  • conf: params.NodeConfig