 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 |
|
[API]Address = "localhost:8086"Explorer = true
[Debug]APIAddress = "localhost:12345"
[StateDB]Path = "/tmp/iden3-test/hermez/statedb"
[PostgreSQL]Port = 5432Host = "localhost"User = "hermez"Password = "yourpasswordhere"Name = "hermez"
[Web3]URL = "http://localhost:8545"
[Synchronizer]SyncLoopInterval = "1s"StatsRefreshPeriod = "1s"
[Synchronizer.StartBlockNum] Rollup = 1 Auction = 1 WDelayer = 1
[SmartContracts]Rollup = "0x6F4e99522F4eB37e0B73D0C0373147893EF12fD5"Auction = "0x5E0816F0f8bC560cB2B9e9C87187BeCac8c2021F"WDelayer = "0x5D94e3e7aeC542aB0F9129B9a7BAdeb5B3Ca0f77"TokenHEZ = "0x2b7dEe2CF60484325716A1c6A193519c8c3b19F3"TokenHEZName = "Hermez Network Token"
[Synchronizer.InitialVariables.Auction] DonationAddress = "0x0000000000000000000000000000000000000001" BootCoordinator = "0xb4124cEB3451635DAcedd11767f004d8a28c6eE7" DefaultSlotSetBid = [ "10000000000000000000", "10000000000000000000", "10000000000000000000", "10000000000000000000", "10000000000000000000", "10000000000000000000", ] ClosedAuctionSlots = 2 OpenAuctionSlots = 4320 AllocationRatio = [4000, 4000, 2000] Outbidding = 1000 SlotDeadline = 20
[Synchronizer.InitialVariables.WDelayer] # HermezRollupAddress = HermezGovernanceDAOAddress = "0x0000000000000000000000000000000000000001" WhiteHackGroupAddress = "0x0000000000000000000000000000000000000001" HermezKeeperAddress = "0x0000000000000000000000000000000000000001" WithdrawalDelay = 60 EmergencyModeStartingTime = 0 EmergencyMode = false
[Synchronizer.InitialVariables.Rollup] FeeAddToken = "10" ForgeL1L2BatchTimeout = 10 WithdrawalDelay = 1209600 # 60 * 60 * 24 * 7 * 2 # [[Synchronizer.InitialVariables.Rollup.Buckets]] # CeilUSD = 0 # BlockStamp = 0 # Withdrawals = 0 # BlockWithdrawalRate = 0 # MaxWithdrawals = 0 # [[Synchronizer.InitialVariables.Rollup.Buckets]] # CeilUSD = 0 # BlockStamp = 0 # Withdrawals = 0 # BlockWithdrawalRate = 0 # MaxWithdrawals = 0 # [[Synchronizer.InitialVariables.Rollup.Buckets]] # CeilUSD = 0 # BlockStamp = 0 # Withdrawals = 0 # BlockWithdrawalRate = 0 # MaxWithdrawals = 0 # [[Synchronizer.InitialVariables.Rollup.Buckets]] # CeilUSD = 0 # BlockStamp = 0 # Withdrawals = 0 # BlockWithdrawalRate = 0 # MaxWithdrawals = 0 # [[Synchronizer.InitialVariables.Rollup.Buckets]] # CeilUSD = 0 # BlockStamp = 0 # Withdrawals = 0 # BlockWithdrawalRate = 0 # MaxWithdrawals = 0
|
