status-go/services/accounts
osmaczko 2ced83abb7
chore_: replace geth logger with zap logger (#5962)
closes: #6002
2024-10-28 20:54:17 +00:00
..
accountsevent chore_: replace geth logger with zap logger (#5962) 2024-10-28 20:54:17 +00:00
settingsevent chore_: replace geth logger with zap logger (#5962) 2024-10-28 20:54:17 +00:00
README.md
accounts.go chore_: replace geth logger with zap logger (#5962) 2024-10-28 20:54:17 +00:00
multiaccounts.go Fix/timesource offline (#4309) 2023-11-13 14:06:32 -05:00
service.go Fix account not being stored 2023-10-24 19:01:46 +01:00
settings.go chore(identity)_: remove old social links implementation (#5214) 2024-05-24 10:35:34 +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