ethpandaops / assertoor Goto Github PK

Add a task that requests funds from the shadowvault

The shadowfork vault is a contract deployed to public testnets that is designed to release funds safely on a shadow fork.
Withdrawal transactions to this contract revert on the regular public testnets.
The contract can be used to gather some funds for subsequent tests on shadow forks.

• Add task generate_shadowvault_withdrawal
• Task should request funds from the ShadowForkVault via the shadowWithdraw function
• The required proof for the shadowWithdraw function can be generated via the generateHeaderProof function

The assertoor UI should be capable of:

• Create Test runs (with custom config)
• Cancel queued or running test runs

Completed tests should be removed from the task history after configurable amount of time.
Default should be 3 days.

The list of executed list is currently displayed as a flat table:

There should be a graph in the blank area before the ID column that shows the relationship of these tasks.
eg. in the example above, task ID 3 & 4 are children of of task ID 2. This should be easily recognizable from the graph.

Add a new task check_consensus_eth1_votes:

• Check ETH1 votes in current eth1 voting period
• Check deposit roots of votes
  https://discord.com/channels/595666850260713488/892088344438255616/1215073165496029245

Add a proper API interface that is capable of:

• List test definitions
• List test runs
  • Filtered by test id
• Get test run details (list of tasks + status + logs)
  • Trimmed details (no logs, just task list & status)
• Run Test (create test instance, add to queue & return run id)
• Cancel Test

Assertoor should be able to serve a security trimmed version of the UI for public access.

Key points:

• separate port
• no task logs
• no task / test configs
• no api access

Replace big.Int with custom helper.BigInt for all config settings.
The native big.Int does not support parsing big values as string.

Rel 4018563

Reminder to keep the documentation up to date!

Missing stuff:

• schedule section in test configuration & test scheduler description
• coordinator section in test configuration with general settings (test retention time & execution concurrency)
• existence of API, api.enabled setting & reference to swagger api documentation within the assertoor UI
• enhance description of variable system (global / test config is not passed down to all task configs)
• describe configVars and the ability to use jq syntax for more complex expressions

Nice to have:

• Description of assertoor code structure
• How to use assertoor as go library (call tasks, call tests)

Assertoor needs to cache the validator set to avoid it from being requested for every task that needs it.
Currently there is no caching, so if there are like 4 tasks that need it, assertoor will request it 4 times.
That's quite some memory overhead as the validator set on holesky is extremely big.