arnaucube
/
hermez-node
mirror of https://github.com/arnaucube/hermez-node.git
1
1
Fork 0
Code Issues Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
743 Commits
26 Branches
2 Tags
10 MiB
Tree: 6c6d1ea7b8
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from '6c6d1ea7b8'
${ noResults }
hermez-node/cli/node/cfg.api.toml

24 lines
458 B
Raw Normal View History

Allow serving API only via new cli command - Add new command to the cli/node: `serveapi` that alows serving the API just by connecting to the PostgreSQL database. The mode flag should me passed in order to select whether we are connecting to a synchronizer database or a coordinator database. If `coord` is chosen as mode, the coordinator endpoints can be activated in order to allow inserting l2txs and authorizations into the L2DB. Summary of the implementation details - New SQL table with 3 columns (plus `item_id` pk). The table only contains a single row with `item_id` = 1. Columns: - state: historydb.StateAPI in JSON. This is the struct that is served via the `/state` API endpoint. The node will periodically update this struct and store it int he DB. The api server will query it from the DB to serve it. - config: historydb.NodeConfig in JSON. This struct contains node configuration parameters that the API needs to be aware of. It's updated once every time the node starts. - constants: historydb.Constants in JSON. This struct contains all the hermez network constants gathered via the ethereum client by the node. It's written once every time the node starts. - The HistoryDB contains methods to get and update each one of these columns individually. - The HistoryDB contains all methods that query the DB and prepare objects that will appear in the StateAPI endpoint. - The configuration used in for the `serveapi` cli/node command is defined in `config.APIServer`, and is a subset of `node.Config` in order to allow reusing the same configuration file of the node if desired. - A new object is introduced in the api: `StateAPIUpdater`, which contains all the necessary information to update the StateAPI in the DB periodically by the node. - Moved the types `SCConsts`, `SCVariables` and `SCVariablesPtr` from `syncrhonizer` to `common` for convenience.
3 years ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
  1. [API]
  2. Address = "localhost:8386"
  3. Explorer = true
  4. MaxSQLConnections = 10
  5. SQLConnectionTimeout = "2s"
  7. [PostgreSQL]
  8. PortWrite = 5432
  9. HostWrite = "localhost"
  10. UserWrite = "hermez"
  11. PasswordWrite = "yourpasswordhere"
  12. NameWrite = "hermez"
  14. [Coordinator.L2DB]
  15. SafetyPeriod = 10
  16. MaxTxs = 512
  17. TTL = "24h"
  18. PurgeBatchDelay = 10
  19. InvalidateBatchDelay = 20
  20. PurgeBlockDelay = 10
  21. InvalidateBlockDelay = 20
  23. [Coordinator.API]
  24. Coordinator = true