4c0d8dedea
Account's address was used as a primary key in accounts db and as a deterministic id of an account in some API calls. Also it was used as a part of the name of the account specific database. This revealed some extra information about the account and wasn't necessary. At first the hash of the address was planned to be used as a deterministic id, but we already have a keyUid which is calculated as sha256 hash of account's public key and has similar properties: - it is deterministic - doesn't reveal accounts public key or address in plain |
||
---|---|---|
.. | ||
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