Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions docs/multi-eoa-sequencers/prd.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,11 +16,11 @@ Note: We can pull up delivery based on what we see/want in prod: if people are u

# Background

An Ethereum address can either choose to send legacy transactions **or** blob transactions at the same time to prevent some DDoS attacks. ([Ref](https://github.com/ethereum/go-ethereum/issues/28925#issuecomment-1925601084))
An Ethereum address can send either legacy transactions or blob transactions, but not both concurrently, to prevent some DDoS attacks ([Ref](https://github.com/ethereum/go-ethereum/issues/28925#issuecomment-1925601084))

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe this change, alters the context of the description, so maybe its not correct to modify like this? It implies that both types of transactions can be sent at the same time.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes it's


Further, because all transactions must respect the expected nonce value from the account, if a blob transaction is sent, but is not included within a desired timeframe, it must be cancelled or replaced; this operation is expensive, requiring [a 100% price increase from the initial (blob)gas prices](https://github.com/ethereum/go-ethereum/blob/6143c350ae1ecf3330678be02b4c2745bb6b8134/core/txpool/blobpool/config.go#L34).

Separately, sequencers in Aztec are able perform multiple actions during their slot, including:
Separately, sequencers in Aztec are able to perform multiple actions during their slot, including:

- [propose](https://github.com/AztecProtocol/aztec-packages/blob/27f1eca25c4c5849d32541b5ad1d3068d5d1911a/l1-contracts/src/core/libraries/rollup/ProposeLib.sol#L71) a block to the L1 (a blob transaction)
- [signal/vote](https://github.com/AztecProtocol/aztec-packages/blob/27f1eca25c4c5849d32541b5ad1d3068d5d1911a/l1-contracts/src/governance/proposer/EmpireBase.sol#L55) at the governance proposer (non-blob)
Expand Down Expand Up @@ -51,7 +51,7 @@ The validators are able to separate their proposer from their attester. This pro
## Assumptions

- Validators may only vote at the governance proposer and slash proposer during their L2 slot for which they are sequencer.
- We use ethereum blobs for DA.
- We use Ethereum blobs for DA.

# User Stories

Expand All @@ -61,7 +61,7 @@ Alice is making transactions on Aztec. She is happy when they are promptly inclu

## Sequencer

Sally Sequencer wants to make money running a validator on the aztec network.
Sally Sequencer wants to make money running a validator on the Aztec network.

Sally is happy when her node publishes Aztec blocks because that means she makes money when that block is proven.

Expand Down Expand Up @@ -93,14 +93,14 @@ WHERE: end user and sequencer user stories.

If needed, the current sequencer **SHOULD** prioritize their block submission over their voting.

WHY: it more important for network liveness, and blob transactions need more time to get included.
WHY: it is more important for network liveness, and blob transactions need more time to get included.
WHERE: end user story and developer apprehension

### ATTR03

Beyond updating payload addresses for votes, node operators **SHOULD NOT** need to make live updates to their node's configuration to ensure that they are consistently producing blocks.

WHY: if things are hard, people don't do them. in this case, that would mean degraded performance for all aztec users.
WHY: if things are hard, people don't do them. in this case, that would mean degraded performance for all Aztec users.
WHERE: sequencer user story.

### ATTR04
Expand Down