Gui
notably, i'm also moving the `AutoUpdateGenesis` concept out of genesis.go, and turn this into a flag, since i believe this should be handled via env vars on each deployment
it's deterministic because the SQL statements produced by each node are the same (bit-by-bit) . this was not the case with the raw db format.
this PR is far from finished but since the road ahead is just repeating what i did for /elections to the rest of the endpoints, i'd really appreciate some early...
so far: these endpoints are deprecated * GET /accounts/{organizationID}/elections/status/{status}/page/{page} * GET /accounts/{organizationID}/elections/page/{page} * GET /elections/page/{page} * POST /elections/filter/page/{page} in favor of: * GET /elections?page={page}&organizationID={organizationID}&status={status}&electionID={electionID}&withResults={withResults} (i added, for completeness, a new...
just in case, i've tested this with a new benchmark (BenchmarkElectionList) and confirmed a 10x improvement on that endpoint as well, no regressions
this commit introduced an invalid encoding in logs https://github.com/cometbft/cometbft/commit/9710d69f65804f346a88b15829f0c5fc05711e15 i'll report it upstream
proposed a fix upstream https://github.com/cometbft/cometbft/pull/4062
my fix was merged yesterday upstream :v:
we can of course wait for the final version instead of rushing into the rc1
another related idea is to implement a "consistency check" on indexer, that for example recalculates the elections results looking at the state, and verifies the indexer has the same results.