aztec-packages
aztec-packages copied to clipboard
AztecProtocol
## Overview In the current implementation the validator client does NOT have suitable timeouts encoded. If it cannot receive information from peers it will hand indefinitely and miss its slot....
## Overview For the sake of getting things working the validator receives blocks that sign over the archiver, and not lists of transactions. They also do not re ex. We...
## Overview After a given period of time, the attestation pool should self prune itself, removing any attestations stored for epochs / slots that are no longer required.
## Overview One of the main reasons the validator client exists is to perform DA capabilities for the provers. Add methods such that other nodes can request missing information (...
## Overview In https://github.com/AztecProtocol/aztec-packages/pull/7854, where the validator client a code organisation issue is bandaided by having the p2p client call back into the validator client whenever it receives a proposal...
## Overview Validator client information is currently requested from the smart contract whenever it is required. The validator client should have a synced local view of this
## Overview ATM, all nodes attempt to create and submit block proposals to each other, regardless if they are the leader or not. The validator client should sync the current...
There are currently some unconstrained steps, because otherwise we'd have multiple rows per opcode on the main trace.
Emitted size reductions ``` AppSubscription::assert_block_number with size 406 => 403 AppSubscription::assert_not_expired with size 399 => 396 AppSubscription::constructor with size 2476 => 2456 Auth::constructor with size 2012 => 1995 Auth::get_authorized with...
