Eduard S 3b99953007 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
.github/workflows	Feature/merge history l2 tables (#156)	4 years ago
api	Redo coordinator structure, connect API to node	4 years ago
apitypes	Update SQL types, improve SQL *big.Int	4 years ago
batchbuilder	Add HashGlobalInputs for ZKInputs	4 years ago
cli/node	Redo coordinator structure, connect API to node	4 years ago
common	Redo coordinator structure, connect API to node	4 years ago
config	Redo coordinator structure, connect API to node	4 years ago
coordinator	Redo coordinator structure, connect API to node	4 years ago
db	Redo coordinator structure, connect API to node	4 years ago
eth	Redo coordinator structure, connect API to node	4 years ago
log	Add transakcio set type define, add set load [...]	4 years ago
node	Redo coordinator structure, connect API to node	4 years ago
priceupdater	Insert ETH as HistoryDB token	4 years ago
synchronizer	Redo coordinator structure, connect API to node	4 years ago
test	Redo coordinator structure, connect API to node	4 years ago
txselector	Add HashGlobalInputs for ZKInputs	4 years ago
.gitignore	Implement first iteration of node	4 years ago
README.md	Add the ability to run the API forever when testing	4 years ago
go.mod	Fix exit table, set delayed_withdrawn in exits	4 years ago
go.sum	Integrate til into api	4 years ago

README.md

hermez-node

Go implementation of the Hermez node.

Test

First run a docker instance of the PostgresSQL (where yourpasswordhere should be your password)

POSTGRES_PASS=yourpasswordhere; sudo docker run --rm --name hermez-db-test -p 5432:5432 -e POSTGRES_DB=hermez -e POSTGRES_USER=hermez -e POSTGRES_PASSWORD="$POSTGRES_PASS" -d postgres

Then, run the tests with the password as env var

POSTGRES_PASS=yourpasswordhere ETHCLIENT_DIAL_URL=yourethereumurlhere go test -p 1 ./...

NOTE: -p 1 forces execution of package test in serial. Otherwise they may be executed in paralel and the test may find unexpected entries in the SQL databse because it's shared among all tests.

There is an extra temporal option that allows to run the API server through the Go tests. This should be removed once the API can be properly initialized, with data from the synchronizer and so on. To use this, run FAKE_SERVER=yes POSTGRES_PASS=yourpasswordhere ETHCLIENT_DIAL_URL=yourethereumurlhere go test -timeout 0 ./api -p 1 -count 1 -v

Lint

Install golangci-lint
Once installed, to check the lints

golangci-lint run --timeout=5m -E whitespace -E gosec -E gci -E misspell -E gomnd -E gofmt -E goimports -E golint --exclude-use-default=false --max-same-issues 0