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.

109 lines
3.2 KiB

Redo coordinator structure, connect API to node - API: - Modify the constructor so that hardcoded rollup constants don't need to be passed (introduce a `Config` and use `configAPI` internally) - Common: - Update rollup constants with proper *big.Int when required - Add BidCoordinator and Slot structs used by the HistoryDB and Synchronizer. - Add helper methods to AuctionConstants - AuctionVariables: Add column `DefaultSlotSetBidSlotNum` (in the SQL table: `default_slot_set_bid_slot_num`), which indicates at which slotNum does the `DefaultSlotSetBid` specified starts applying. - Config: - Move coordinator exclusive configuration from the node config to the coordinator config - Coordinator: - Reorganize the code towards having the goroutines started and stopped from the coordinator itself instead of the node. - Remove all stop and stopped channels, and use context.Context and sync.WaitGroup instead. - Remove BatchInfo setters and assing variables directly - In ServerProof and ServerProofPool use context instead stop channel. - Use message passing to notify the coordinator about sync updates and reorgs - Introduce the Pipeline, which can be started and stopped by the Coordinator - Introduce the TxManager, which manages ethereum transactions (the TxManager is also in charge of making the forge call to the rollup smart contract). The TxManager keeps ethereum transactions and: 1. Waits for the transaction to be accepted 2. Waits for the transaction to be confirmed for N blocks - In forge logic, first prepare a batch and then wait for an available server proof to have all work ready once the proof server is ready. - Remove the `isForgeSequence` method which was querying the smart contract, and instead use notifications sent by the Synchronizer to figure out if it's forging time. - Update test (which is a minimal test to manually see if the coordinator starts) - HistoryDB: - Add method to get the number of batches in a slot (used to detect when a slot has passed the bid winner forging deadline) - Add method to get the best bid and associated coordinator of a slot (used to detect the forgerAddress that can forge the slot) - General: - Rename some instances of `currentBlock` to `lastBlock` to be more clear. - Node: - Connect the API to the node and call the methods to update cached state when the sync advances blocks. - Call methods to update Coordinator state when the sync advances blocks and finds reorgs. - Synchronizer: - Add Auction field in the Stats, which contain the current slot with info about highest bidder and other related info required to know who can forge in the current block. - Better organization of cached state: - On Sync, update the internal cached state - On Init or Reorg, load the state from HistoryDB into the internal cached state.
4 years ago
Redo coordinator structure, connect API to node - API: - Modify the constructor so that hardcoded rollup constants don't need to be passed (introduce a `Config` and use `configAPI` internally) - Common: - Update rollup constants with proper *big.Int when required - Add BidCoordinator and Slot structs used by the HistoryDB and Synchronizer. - Add helper methods to AuctionConstants - AuctionVariables: Add column `DefaultSlotSetBidSlotNum` (in the SQL table: `default_slot_set_bid_slot_num`), which indicates at which slotNum does the `DefaultSlotSetBid` specified starts applying. - Config: - Move coordinator exclusive configuration from the node config to the coordinator config - Coordinator: - Reorganize the code towards having the goroutines started and stopped from the coordinator itself instead of the node. - Remove all stop and stopped channels, and use context.Context and sync.WaitGroup instead. - Remove BatchInfo setters and assing variables directly - In ServerProof and ServerProofPool use context instead stop channel. - Use message passing to notify the coordinator about sync updates and reorgs - Introduce the Pipeline, which can be started and stopped by the Coordinator - Introduce the TxManager, which manages ethereum transactions (the TxManager is also in charge of making the forge call to the rollup smart contract). The TxManager keeps ethereum transactions and: 1. Waits for the transaction to be accepted 2. Waits for the transaction to be confirmed for N blocks - In forge logic, first prepare a batch and then wait for an available server proof to have all work ready once the proof server is ready. - Remove the `isForgeSequence` method which was querying the smart contract, and instead use notifications sent by the Synchronizer to figure out if it's forging time. - Update test (which is a minimal test to manually see if the coordinator starts) - HistoryDB: - Add method to get the number of batches in a slot (used to detect when a slot has passed the bid winner forging deadline) - Add method to get the best bid and associated coordinator of a slot (used to detect the forgerAddress that can forge the slot) - General: - Rename some instances of `currentBlock` to `lastBlock` to be more clear. - Node: - Connect the API to the node and call the methods to update cached state when the sync advances blocks. - Call methods to update Coordinator state when the sync advances blocks and finds reorgs. - Synchronizer: - Add Auction field in the Stats, which contain the current slot with info about highest bidder and other related info required to know who can forge in the current block. - Better organization of cached state: - On Sync, update the internal cached state - On Init or Reorg, load the state from HistoryDB into the internal cached state.
4 years ago
  1. package api
  2. import (
  3. "errors"
  4. "sync"
  5. "github.com/gin-gonic/gin"
  6. "github.com/hermeznetwork/hermez-node/common"
  7. "github.com/hermeznetwork/hermez-node/db/historydb"
  8. "github.com/hermeznetwork/hermez-node/db/l2db"
  9. "github.com/hermeznetwork/hermez-node/db/statedb"
  10. "github.com/hermeznetwork/tracerr"
  11. )
  12. // TODO: Add correct values to constants
  13. const (
  14. createAccountExtraFeePercentage float64 = 2
  15. createAccountInternalExtraFeePercentage float64 = 2.5
  16. )
  17. // Status define status of the network
  18. type Status struct {
  19. sync.RWMutex
  20. Network Network `json:"network"`
  21. Metrics historydb.Metrics `json:"metrics"`
  22. Rollup common.RollupVariables `json:"rollup"`
  23. Auction common.AuctionVariables `json:"auction"`
  24. WithdrawalDelayer common.WDelayerVariables `json:"withdrawalDelayer"`
  25. RecommendedFee common.RecommendedFee `json:"recommendedFee"`
  26. }
  27. // API serves HTTP requests to allow external interaction with the Hermez node
  28. type API struct {
  29. h *historydb.HistoryDB
  30. cg *configAPI
  31. s *statedb.StateDB
  32. l2 *l2db.L2DB
  33. status Status
  34. chainID uint16
  35. }
  36. // NewAPI sets the endpoints and the appropriate handlers, but doesn't start the server
  37. func NewAPI(
  38. coordinatorEndpoints, explorerEndpoints bool,
  39. server *gin.Engine,
  40. hdb *historydb.HistoryDB,
  41. sdb *statedb.StateDB,
  42. l2db *l2db.L2DB,
  43. config *Config,
  44. chainID uint16,
  45. ) (*API, error) {
  46. // Check input
  47. // TODO: is stateDB only needed for explorer endpoints or for both?
  48. if coordinatorEndpoints && l2db == nil {
  49. return nil, tracerr.Wrap(errors.New("cannot serve Coordinator endpoints without L2DB"))
  50. }
  51. if explorerEndpoints && hdb == nil {
  52. return nil, tracerr.Wrap(errors.New("cannot serve Explorer endpoints without HistoryDB"))
  53. }
  54. a := &API{
  55. h: hdb,
  56. cg: &configAPI{
  57. RollupConstants: *newRollupConstants(config.RollupConstants),
  58. AuctionConstants: config.AuctionConstants,
  59. WDelayerConstants: config.WDelayerConstants,
  60. },
  61. s: sdb,
  62. l2: l2db,
  63. status: Status{},
  64. chainID: chainID,
  65. }
  66. // Add coordinator endpoints
  67. if coordinatorEndpoints {
  68. // Account
  69. server.POST("/account-creation-authorization", a.postAccountCreationAuth)
  70. server.GET("/account-creation-authorization/:hezEthereumAddress", a.getAccountCreationAuth)
  71. // Transaction
  72. server.POST("/transactions-pool", a.postPoolTx)
  73. server.GET("/transactions-pool/:id", a.getPoolTx)
  74. }
  75. // Add explorer endpoints
  76. if explorerEndpoints {
  77. // Account
  78. server.GET("/accounts", a.getAccounts)
  79. server.GET("/accounts/:accountIndex", a.getAccount)
  80. server.GET("/exits", a.getExits)
  81. server.GET("/exits/:batchNum/:accountIndex", a.getExit)
  82. // Transaction
  83. server.GET("/transactions-history", a.getHistoryTxs)
  84. server.GET("/transactions-history/:id", a.getHistoryTx)
  85. // Status
  86. server.GET("/batches", a.getBatches)
  87. server.GET("/batches/:batchNum", a.getBatch)
  88. server.GET("/full-batches/:batchNum", a.getFullBatch)
  89. server.GET("/slots", a.getSlots)
  90. server.GET("/slots/:slotNum", a.getSlot)
  91. server.GET("/bids", a.getBids)
  92. server.GET("/state", a.getState)
  93. server.GET("/config", a.getConfig)
  94. server.GET("/tokens", a.getTokens)
  95. server.GET("/tokens/:id", a.getToken)
  96. server.GET("/coordinators", a.getCoordinators)
  97. }
  98. return a, nil
  99. }