61527f8c78
This is the first step of improvements over keypairs/keycards/accounts. - `SyncKeypairFull` protobuf removed - `SyncKeypair` protobuf is used for syncing all but the watch only accounts - `SyncAccount` is used only for syncing watch only accounts - related keycards are synced together with a keypair - on any keypair change (either it's just a keypair name or any change made over an account which belongs to that keypair) entire keypair is synced including related keycards - on any watch only account related change, that account is synced with all its details |
||
---|---|---|
.. | ||
accountsevent | ||
README.md | ||
accounts.go | ||
multiaccounts.go | ||
out.json | ||
service.go | ||
settings.go |
README.md
Settings service
Settings service provides private API for storing all configuration for a selected account.
To enable:
- Client must ensure that settings db is initialized in the api.Backend.
- 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