Add Pectra user fees notice #1608
Conversation
✅ Deploy Preview for docs-optimism ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
📝 Walkthrough""" WalkthroughThe changes introduce new documentation and updates related to the Ethereum L1 Pectra upgrade and its impact on OP Stack chains. A new notice page explains the effects of EIP-7623 on user fees and provides guidance for chain operators on adjusting fee scalars. The chain operators' preparation instructions are updated to include a step referencing this new notice. The blobs management documentation is expanded with a warning about fee scaling post-Pectra and introduces an "auto" data availability mode for batchers. Additionally, the metadata JSON is updated to include the new notice, and the word list file is reformatted with systematic casing changes. Sequence Diagram(s)sequenceDiagram
participant ChainOperator
participant NoticesPage
participant PectraFeesNotice
participant BatcherConfig
ChainOperator->>NoticesPage: Read Pectra upgrade instructions
NoticesPage->>PectraFeesNotice: Refer to fee scalar adjustment notice
ChainOperator->>PectraFeesNotice: Review fee adjustment guidance
ChainOperator->>BatcherConfig: Update fee scalars and DA mode as advised
Possibly related PRs
Suggested reviewers
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (5)
pages/notices/_meta.json(1 hunks)pages/notices/pectra-changes.mdx(1 hunks)pages/notices/pectra-fees.mdx(1 hunks)pages/operators/chain-operators/management/blobs.mdx(3 hunks)words.txt(9 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
`**/*.mdx`: "ALWAYS review Markdown content THOROUGHLY with the following criteria: - First, check the frontmatter section at the top of the file: 1. For regular pages, ensure AL...
**/*.mdx: "ALWAYS review Markdown content THOROUGHLY with the following criteria:
- First, check the frontmatter section at the top of the file:
- For regular pages, ensure ALL these fields are present and not empty:
--- title: [non-empty] lang: [non-empty] description: [non-empty] topic: [non-empty] personas: [non-empty array] categories: [non-empty array] content_type: [valid type] ---
- For landing pages (index.mdx or files with ), only these fields are required:
--- title: [non-empty] lang: [non-empty] description: [non-empty] topic: [non-empty] ---
- If any required fields are missing or empty, comment:
'This file appears to be missing required metadata. Please check keywords.config.yaml for valid options and add the required fields manually. You can validate your changes by running:pnpm validate-metadata ```'- Use proper nouns in place of personal pronouns like 'We' and 'Our' to maintain consistency in communal documentation.
- Avoid gender-specific language and use the imperative form.
- Monitor capitalization for emphasis. Avoid using all caps, italics, or bold for emphasis.
- Ensure proper nouns are capitalized in sentences.
- Apply the Oxford comma.
- Use proper title case for buttons, tab names, page names, and links. Sentence case should be used for body content and short phrases, even in links.
- Use correct spelling and grammar at all times (IMPORTANT).
- For H1, H2, and H3 headers:
- Use sentence case, capitalizing only the first word.
- Preserve the capitalization of proper nouns, technical terms, and acronyms as defined in the 'nouns.txt' file located in the root directory of the project.
- Do not automatically lowercase words that appear in the 'nouns.txt' file, regardless of their position in the header.
- Flag any headers that seem to inconsistently apply these rules for manual review.
- When reviewing capitalization, always refer to the 'nouns.txt' file for the correct capitalization of proper nouns and technical terms specific to the project.
"
pages/notices/pectra-changes.mdxpages/operators/chain-operators/management/blobs.mdxpages/notices/pectra-fees.mdx
🪛 LanguageTool
words.txt
[duplication] ~2-~2: Možný preklep: zopakovali ste slovo
Context: ACCOUNTQUEUE accountqueue ACCOUNTSLOTS accountslots ACDC ADDI ADDIU ADDU airgap Allnodes al...
(WORD_REPEAT_RULE)
[duplication] ~11-~11: Možný preklep: zopakovali ste slovo
Context: ... ADDI ADDIU ADDU airgap Allnodes allocs Alphanet alphanet Alphanets alphanets altda ANDI Ankr Ape...
(WORD_REPEAT_RULE)
[duplication] ~13-~13: Možný preklep: zopakovali ste slovo
Context: ...irgap Allnodes allocs Alphanet alphanet Alphanets alphanets altda ANDI Ankr Apeworx Arweave authrpc...
(WORD_REPEAT_RULE)
[duplication] ~21-~21: Možný preklep: zopakovali ste slovo
Context: ...altda ANDI Ankr Apeworx Arweave authrpc Autorelay autorelay autorelayer basefee bcde Betanet betane...
(WORD_REPEAT_RULE)
[duplication] ~26-~26: Možný preklep: zopakovali ste slovo
Context: ...elay autorelay autorelayer basefee bcde Betanet betanet Betanets betanets BGEZ BGTZ Biconomy BL...
(WORD_REPEAT_RULE)
[duplication] ~28-~28: Možný preklep: zopakovali ste slovo
Context: ...utorelayer basefee bcde Betanet betanet Betanets betanets BGEZ BGTZ Biconomy BLEZ BLOBPOOL blobpo...
(WORD_REPEAT_RULE)
[duplication] ~34-~34: Možný preklep: zopakovali ste slovo
Context: ...tanets betanets BGEZ BGTZ Biconomy BLEZ BLOBPOOL blobpool blobspace Blockdaemon blockhash blockli...
(WORD_REPEAT_RULE)
[duplication] ~40-~40: Možný preklep: zopakovali ste slovo
Context: ...bspace Blockdaemon blockhash blocklists BLOCKLOGS blocklogs BLOCKPROFILERATE blockprofilerate Block...
(WORD_REPEAT_RULE)
[duplication] ~42-~42: Možný preklep: zopakovali ste slovo
Context: ...lockhash blocklists BLOCKLOGS blocklogs BLOCKPROFILERATE blockprofilerate Blockscout Blockspace blockspace blockt...
(WORD_REPEAT_RULE)
[duplication] ~45-~45: Možný preklep: zopakovali ste slovo
Context: ...PROFILERATE blockprofilerate Blockscout Blockspace blockspace blocktime Blocktimes blocktimes BLOOMFI...
(WORD_REPEAT_RULE)
[duplication] ~48-~48: Možný preklep: zopakovali ste slovo
Context: ...ckscout Blockspace blockspace blocktime Blocktimes blocktimes BLOOMFILTER bloomfilter BLTZ Bootcamp b...
(WORD_REPEAT_RULE)
[duplication] ~50-~50: Možný preklep: zopakovali ste slovo
Context: ...ckspace blocktime Blocktimes blocktimes BLOOMFILTER bloomfilter BLTZ Bootcamp bootnode BOOTNODES Bootno...
(WORD_REPEAT_RULE)
[duplication] ~55-~55: Možný preklep: zopakovali ste slovo
Context: ...LTER bloomfilter BLTZ Bootcamp bootnode BOOTNODES Bootnodes bootnodes bottlenecked Brotli brotli Ca...
(WORD_REPEAT_RULE)
[duplication] ~59-~59: Možný preklep: zopakovali ste slovo
Context: ...TNODES Bootnodes bootnodes bottlenecked Brotli brotli Callouts callouts CCIP cdef Celestia Ce...
(WORD_REPEAT_RULE)
[duplication] ~61-~61: Možný preklep: zopakovali ste slovo
Context: ...es bootnodes bottlenecked Brotli brotli Callouts callouts CCIP cdef Celestia Celestia's chainid C...
(WORD_REPEAT_RULE)
[duplication] ~78-~78: Možný preklep: zopakovali ste slovo
Context: ...alized collateralized compr Comprensive COMPUTEPENDINGBLOCK computependingblock confs Consen corsdomain counterfactuall...
(WORD_REPEAT_RULE)
[duplication] ~84-~84: Možný preklep: zopakovali ste slovo
Context: ...onfs Consen corsdomain counterfactually Crosschain crosschain Crossmint Dapphub daserver DATACAP data...
(WORD_REPEAT_RULE)
[duplication] ~89-~89: Možný preklep: zopakovali ste slovo
Context: ...n crosschain Crossmint Dapphub daserver DATACAP datacap DATADIR datadir devdocs Devnet devnet D...
(WORD_REPEAT_RULE)
[duplication] ~91-~91: Možný preklep: zopakovali ste slovo
Context: ...ssmint Dapphub daserver DATACAP datacap DATADIR datadir devdocs Devnet devnet Devnets devnets d...
(WORD_REPEAT_RULE)
[duplication] ~94-~94: Možný preklep: zopakovali ste slovo
Context: ...DATACAP datacap DATADIR datadir devdocs Devnet devnet Devnets devnets direnv DISABLETXPOOLGOS...
(WORD_REPEAT_RULE)
[duplication] ~96-~96: Možný preklep: zopakovali ste slovo
Context: ...p DATADIR datadir devdocs Devnet devnet Devnets devnets direnv DISABLETXPOOLGOSSIP disabletxpoo...
(WORD_REPEAT_RULE)
[duplication] ~99-~99: Možný preklep: zopakovali ste slovo
Context: ...cs Devnet devnet Devnets devnets direnv DISABLETXPOOLGOSSIP disabletxpoolgossip Discv discv DIVU Drand dripcheck Drippi...
(WORD_REPEAT_RULE)
[duplication] ~101-~101: Možný preklep: zopakovali ste slovo
Context: ...DISABLETXPOOLGOSSIP disabletxpoolgossip Discv discv DIVU Drand dripcheck Drippie Eigen EIPs...
(WORD_REPEAT_RULE)
[duplication] ~109-~109: Možný preklep: zopakovali ste slovo
Context: ...DIVU Drand dripcheck Drippie Eigen EIPs ENABLEDEPRECATEDPERSONAL enabledeprecatedpersonal enginekind Erigon erigon ETHERBASE ethe...
(WORD_REPEAT_RULE)
[duplication] ~112-~112: Možný preklep: zopakovali ste slovo
Context: ...NAL enabledeprecatedpersonal enginekind Erigon erigon ETHERBASE etherbase Ethernity Ethernow ...
(WORD_REPEAT_RULE)
[duplication] ~114-~114: Možný preklep: zopakovali ste slovo
Context: ...ecatedpersonal enginekind Erigon erigon ETHERBASE etherbase Ethernity Ethernow ETHSTATS ethstats EV...
(WORD_REPEAT_RULE)
[duplication] ~118-~118: Možný preklep: zopakovali ste slovo
Context: ... ETHERBASE etherbase Ethernity Ethernow ETHSTATS ethstats EVMTIMEOUT evmtimeout excercise executa...
(WORD_REPEAT_RULE)
[duplication] ~120-~120: Možný preklep: zopakovali ste slovo
Context: ...se Ethernity Ethernow ETHSTATS ethstats EVMTIMEOUT evmtimeout excercise executability exfiltrate EXIT...
(WORD_REPEAT_RULE)
[duplication] ~125-~125: Možný preklep: zopakovali ste slovo
Context: ...eout excercise executability exfiltrate EXITWHENSYNCED exitwhensynced EXTRADATA extradata Farcaster Faultproo...
(WORD_REPEAT_RULE)
[duplication] ~127-~127: Možný preklep: zopakovali ste slovo
Context: ...xfiltrate EXITWHENSYNCED exitwhensynced EXTRADATA extradata Farcaster Faultproof FDLIMIT fdlimit Fl...
(WORD_REPEAT_RULE)
[duplication] ~131-~131: Možný preklep: zopakovali ste slovo
Context: ...XTRADATA extradata Farcaster Faultproof FDLIMIT fdlimit Flashblocks Flashbots forkable forkchoi...
(WORD_REPEAT_RULE)
[duplication] ~146-~146: Možný preklep: zopakovali ste slovo
Context: ... Funct gameplay GASCAP gascap gaslessly GCMODE gcmode Gelato gifs GLOBALQUEUE globalqueue GLO...
(WORD_REPEAT_RULE)
[duplication] ~150-~150: Možný preklep: zopakovali ste slovo
Context: ...cap gaslessly GCMODE gcmode Gelato gifs GLOBALQUEUE globalqueue GLOBALSLOTS globalslots gokzg growthepi...
(WORD_REPEAT_RULE)
[duplication] ~152-~152: Možný preklep: zopakovali ste slovo
Context: ...ode Gelato gifs GLOBALQUEUE globalqueue GLOBALSLOTS globalslots gokzg growthepie hardfork hardforks HEA...
(WORD_REPEAT_RULE)
[duplication] ~158-~158: Možný preklep: zopakovali ste slovo
Context: ...ots gokzg growthepie hardfork hardforks HEALTHCHECK healthcheck healthchecks HISTORICALRPC historicalrp...
(WORD_REPEAT_RULE)
[duplication] ~161-~161: Možný preklep: zopakovali ste slovo
Context: ...ks HEALTHCHECK healthcheck healthchecks HISTORICALRPC historicalrpc HISTORICALRPCTIMEOUT historicalrpctimeo...
(WORD_REPEAT_RULE)
[duplication] ~163-~163: Možný preklep: zopakovali ste slovo
Context: ...ealthchecks HISTORICALRPC historicalrpc HISTORICALRPCTIMEOUT historicalrpctimeout HOLESKY Holesky holesky IERC IGNOREPRIC...
(WORD_REPEAT_RULE)
[duplication] ~165-~165: Možný preklep: zopakovali ste slovo
Context: ...STORICALRPCTIMEOUT historicalrpctimeout HOLESKY Holesky holesky IERC IGNOREPRICE ignoreprice Im...
(WORD_REPEAT_RULE)
[duplication] ~169-~169: Možný preklep: zopakovali ste slovo
Context: ...rpctimeout HOLESKY Holesky holesky IERC IGNOREPRICE ignoreprice Immunefi Inator inator INFLUXDBV influx...
(WORD_REPEAT_RULE)
[duplication] ~172-~172: Možný preklep: zopakovali ste slovo
Context: ...y IERC IGNOREPRICE ignoreprice Immunefi Inator inator INFLUXDBV influxdbv initcode IPCDISABLE...
(WORD_REPEAT_RULE)
[duplication] ~174-~174: Možný preklep: zopakovali ste slovo
Context: ...RICE ignoreprice Immunefi Inator inator INFLUXDBV influxdbv initcode IPCDISABLE ipcdisable ipcfile ...
(WORD_REPEAT_RULE)
[duplication] ~177-~177: Možný preklep: zopakovali ste slovo
Context: ...tor inator INFLUXDBV influxdbv initcode IPCDISABLE ipcdisable ipcfile IPCPATH ipcpath IPFS Isthumus J...
(WORD_REPEAT_RULE)
[duplication] ~180-~180: Možný preklep: zopakovali ste slovo
Context: ... initcode IPCDISABLE ipcdisable ipcfile IPCPATH ipcpath IPFS Isthumus JALR JOURNALREMOTES journ...
(WORD_REPEAT_RULE)
[duplication] ~185-~185: Možný preklep: zopakovali ste slovo
Context: ...file IPCPATH ipcpath IPFS Isthumus JALR JOURNALREMOTES journalremotes JSPATH jspath jwtsecret Keccak leveldb ...
(WORD_REPEAT_RULE)
[duplication] ~187-~187: Možný preklep: zopakovali ste slovo
Context: ...umus JALR JOURNALREMOTES journalremotes JSPATH jspath jwtsecret Keccak leveldb lightkdf Lisk ...
(WORD_REPEAT_RULE)
[duplication] ~199-~199: Možný preklep: zopakovali ste slovo
Context: ...k logfile logfmt Mainnets MAXAGE maxage MAXBACKUPS maxbackups MAXPEERS maxpeers MAXPENDPEERS maxpendp...
(WORD_REPEAT_RULE)
[duplication] ~201-~201: Možný preklep: zopakovali ste slovo
Context: ...ets MAXAGE maxage MAXBACKUPS maxbackups MAXPEERS maxpeers MAXPENDPEERS maxpendpeers MAXPRICE maxp...
(WORD_REPEAT_RULE)
[duplication] ~203-~203: Možný preklep: zopakovali ste slovo
Context: ...MAXBACKUPS maxbackups MAXPEERS maxpeers MAXPENDPEERS maxpendpeers MAXPRICE maxprice MEMPROFILERATE mempro...
(WORD_REPEAT_RULE)
[duplication] ~205-~205: Možný preklep: zopakovali ste slovo
Context: ...EERS maxpeers MAXPENDPEERS maxpendpeers MAXPRICE maxprice MEMPROFILERATE memprofilerate Merkle me...
(WORD_REPEAT_RULE)
[duplication] ~207-~207: Možný preklep: zopakovali ste slovo
Context: ...ENDPEERS maxpendpeers MAXPRICE maxprice MEMPROFILERATE memprofilerate Merkle merkle MFHI MFLO Mgas Minato MIN...
(WORD_REPEAT_RULE)
[duplication] ~209-~209: Možný preklep: zopakovali ste slovo
Context: ... maxprice MEMPROFILERATE memprofilerate Merkle merkle MFHI MFLO Mgas Minato MINFREEDISK minfr...
(WORD_REPEAT_RULE)
[duplication] ~215-~215: Možný preklep: zopakovali ste slovo
Context: ...ate Merkle merkle MFHI MFLO Mgas Minato MINFREEDISK minfreedisk MINSUGGESTEDPRIORITYFEE minsuggestedpri...
(WORD_REPEAT_RULE)
[duplication] ~217-~217: Možný preklep: zopakovali ste slovo
Context: ...FLO Mgas Minato MINFREEDISK minfreedisk MINSUGGESTEDPRIORITYFEE minsuggestedpriorityfee Mintable Mintplex MIPSEVM Mitigations M...
(WORD_REPEAT_RULE)
[duplication] ~223-~223: Možný preklep: zopakovali ste slovo
Context: ...e Mintable Mintplex MIPSEVM Mitigations Monitorism monitorism Moralis Mordor mountpoint MOVN MOVZ MTH...
(WORD_REPEAT_RULE)
[duplication] ~240-~240: Možný preklep: zopakovali ste slovo
Context: ... multiclient multisigs MULTU nethermind NETRESTRICT netrestrict NETWORKID networkid NEWPAYLOAD newpaylo...
(WORD_REPEAT_RULE)
[duplication] ~242-~242: Možný preklep: zopakovali ste slovo
Context: ...ULTU nethermind NETRESTRICT netrestrict NETWORKID networkid NEWPAYLOAD newpayload nextra NOCOMPACTI...
(WORD_REPEAT_RULE)
[duplication] ~244-~244: Možný preklep: zopakovali ste slovo
Context: ...ESTRICT netrestrict NETWORKID networkid NEWPAYLOAD newpayload nextra NOCOMPACTION nocompaction NODEKE...
(WORD_REPEAT_RULE)
[duplication] ~247-~247: Možný preklep: zopakovali ste slovo
Context: ... networkid NEWPAYLOAD newpayload nextra NOCOMPACTION nocompaction NODEKEY nodekey NODEKEYHEX nodekeyhex n...
(WORD_REPEAT_RULE)
[duplication] ~249-~249: Možný preklep: zopakovali ste slovo
Context: ...ayload nextra NOCOMPACTION nocompaction NODEKEY nodekey NODEKEYHEX nodekeyhex nodename Nodies N...
(WORD_REPEAT_RULE)
[duplication] ~251-~251: Možný preklep: zopakovali ste slovo
Context: ...COMPACTION nocompaction NODEKEY nodekey NODEKEYHEX nodekeyhex nodename Nodies NODISCOVER nodiscover N...
(WORD_REPEAT_RULE)
[duplication] ~255-~255: Možný preklep: zopakovali ste slovo
Context: ...y NODEKEYHEX nodekeyhex nodename Nodies NODISCOVER nodiscover NOLOCALS nolocals NOPREFETCH noprefetch...
(WORD_REPEAT_RULE)
[duplication] ~257-~257: Možný preklep: zopakovali ste slovo
Context: ...x nodename Nodies NODISCOVER nodiscover NOLOCALS nolocals NOPREFETCH noprefetch NOPRUNING nopruni...
(WORD_REPEAT_RULE)
[duplication] ~259-~259: Možný preklep: zopakovali ste slovo
Context: ...NODISCOVER nodiscover NOLOCALS nolocals NOPREFETCH noprefetch NOPRUNING nopruning NOSYNCSERVE nosyncs...
(WORD_REPEAT_RULE)
[duplication] ~261-~261: Možný preklep: zopakovali ste slovo
Context: ...NOLOCALS nolocals NOPREFETCH noprefetch NOPRUNING nopruning NOSYNCSERVE nosyncserve Numba Offchain ...
(WORD_REPEAT_RULE)
[duplication] ~263-~263: Možný preklep: zopakovali ste slovo
Context: ...PREFETCH noprefetch NOPRUNING nopruning NOSYNCSERVE nosyncserve Numba Offchain offchain opchaina opchai...
(WORD_REPEAT_RULE)
[duplication] ~266-~266: Možný preklep: zopakovali ste slovo
Context: ...nopruning NOSYNCSERVE nosyncserve Numba Offchain offchain opchaina opchainb OPCM opcm Openfort op...
(WORD_REPEAT_RULE)
[duplication] ~270-~270: Možný preklep: zopakovali ste slovo
Context: ...mba Offchain offchain opchaina opchainb OPCM opcm Openfort oplabs opnode's opstack outfil...
(WORD_REPEAT_RULE)
[duplication] ~279-~279: Možný preklep: zopakovali ste slovo
Context: ...s opstack outfile Pausability pcscdpath Pectra pectra Pectra's Peerstore peerstore peerstores...
(WORD_REPEAT_RULE)
[duplication] ~282-~282: Možný preklep: zopakovali ste slovo
Context: ...bility pcscdpath Pectra pectra Pectra's Peerstore peerstore peerstores Permissioned permissioned Pe...
(WORD_REPEAT_RULE)
[duplication] ~285-~285: Možný preklep: zopakovali ste slovo
Context: ...Pectra's Peerstore peerstore peerstores Permissioned permissioned Permissionless permissionless permissio...
(WORD_REPEAT_RULE)
[duplication] ~287-~287: Možný preklep: zopakovali ste slovo
Context: ...re peerstores Permissioned permissioned Permissionless permissionless permissionlessly Perps Peta Pimlico POA...
(WORD_REPEAT_RULE)
[duplication] ~295-~295: Možný preklep: zopakovali ste slovo
Context: ...ionlessly Perps Peta Pimlico POAP POAPs PPROF pprof Precommitments precommitments preconfig...
(WORD_REPEAT_RULE)
[duplication] ~297-~297: Možný preklep: zopakovali ste slovo
Context: ...rps Peta Pimlico POAP POAPs PPROF pprof Precommitments precommitments preconfigured predeploy Predeployed pre...
(WORD_REPEAT_RULE)
[duplication] ~301-~301: Možný preklep: zopakovali ste slovo
Context: ... precommitments preconfigured predeploy Predeployed predeployed Predeploys predeploys prefunded Preimag...
(WORD_REPEAT_RULE)
[duplication] ~303-~303: Možný preklep: zopakovali ste slovo
Context: ...gured predeploy Predeployed predeployed Predeploys predeploys prefunded Preimage preimage PREIMAGES p...
(WORD_REPEAT_RULE)
[duplication] ~306-~306: Možný preklep: zopakovali ste slovo
Context: ...eployed Predeploys predeploys prefunded Preimage preimage PREIMAGES preimages preinstall Preinsta...
(WORD_REPEAT_RULE)
[duplication] ~308-~308: Možný preklep: zopakovali ste slovo
Context: ... predeploys prefunded Preimage preimage PREIMAGES preimages preinstall Preinstalls preinstalls Pres...
(WORD_REPEAT_RULE)
[duplication] ~311-~311: Možný preklep: zopakovali ste slovo
Context: ...preimage PREIMAGES preimages preinstall Preinstalls preinstalls Prestate prestate prestates PREVRANDAO ...
(WORD_REPEAT_RULE)
[duplication] ~313-~313: Možný preklep: zopakovali ste slovo
Context: ...ages preinstall Preinstalls preinstalls Prestate prestate prestates PREVRANDAO PRICEBUMP pricebum...
(WORD_REPEAT_RULE)
[duplication] ~317-~317: Možný preklep: zopakovali ste slovo
Context: ... Prestate prestate prestates PREVRANDAO PRICEBUMP pricebump PRICELIMIT pricelimit productionize pro...
(WORD_REPEAT_RULE)
[duplication] ~319-~319: Možný preklep: zopakovali ste slovo
Context: ...restates PREVRANDAO PRICEBUMP pricebump PRICELIMIT pricelimit productionize productionized Protip Pro...
(WORD_REPEAT_RULE)
[duplication] ~325-~325: Možný preklep: zopakovali ste slovo
Context: ...uctionize productionized Protip Proxied Proxyd proxyd Pyth Pyth's QRNG Quicknode quicknode qu...
(WORD_REPEAT_RULE)
[duplication] ~327-~327: Možný preklep: zopakovali ste slovo
Context: ...uctionized Protip Proxied Proxyd proxyd Pyth Pyth's QRNG Quicknode quicknode quickstarts ...
(WORD_REPEAT_RULE)
[duplication] ~330-~330: Možný preklep: zopakovali ste slovo
Context: ... Proxied Proxyd proxyd Pyth Pyth's QRNG Quicknode quicknode quickstarts rebalancing Regenesis regen...
(WORD_REPEAT_RULE)
[duplication] ~334-~334: Možný preklep: zopakovali ste slovo
Context: ...knode quicknode quickstarts rebalancing Regenesis regenesis Reimagine REJOURNAL rejournal REMOTEDB ...
(WORD_REPEAT_RULE)
[duplication] ~337-~337: Možný preklep: zopakovali ste slovo
Context: ...balancing Regenesis regenesis Reimagine REJOURNAL rejournal REMOTEDB remotedb Reown Reown's replaya...
(WORD_REPEAT_RULE)
[duplication] ~339-~339: Možný preklep: zopakovali ste slovo
Context: ...regenesis Reimagine REJOURNAL rejournal REMOTEDB remotedb Reown Reown's replayability replayor re...
(WORD_REPEAT_RULE)
[duplication] ~341-~341: Možný preklep: zopakovali ste slovo
Context: ...e REJOURNAL rejournal REMOTEDB remotedb Reown Reown's replayability replayor reposts reprov...
(WORD_REPEAT_RULE)
[duplication] ~347-~347: Možný preklep: zopakovali ste slovo
Context: ...replayability replayor reposts reproven REQUIREDBLOCKS requiredblocks rollouts Rollups rollups Routescan rpck...
(WORD_REPEAT_RULE)
[duplication] ~350-~350: Možný preklep: zopakovali ste slovo
Context: ... REQUIREDBLOCKS requiredblocks rollouts Rollups rollups Routescan rpckind RPCPREFIX rpcprefix r...
(WORD_REPEAT_RULE)
[duplication] ~354-~354: Možný preklep: zopakovali ste slovo
Context: ...louts Rollups rollups Routescan rpckind RPCPREFIX rpcprefix rpcs RPGF Runbooks runbooks RWAs safedb...
(WORD_REPEAT_RULE)
[duplication] ~358-~358: Možný preklep: zopakovali ste slovo
Context: ...n rpckind RPCPREFIX rpcprefix rpcs RPGF Runbooks runbooks RWAs safedb Schnorr SEPOLIA Sepolia sep...
(WORD_REPEAT_RULE)
[duplication] ~363-~363: Možný preklep: zopakovali ste slovo
Context: ...F Runbooks runbooks RWAs safedb Schnorr SEPOLIA Sepolia sepolia seqnr SEQUENCERHTTP sequencerht...
(WORD_REPEAT_RULE)
[duplication] ~367-~367: Možný preklep: zopakovali ste slovo
Context: ...b Schnorr SEPOLIA Sepolia sepolia seqnr SEQUENCERHTTP sequencerhttp serv signup SLLV SLTI SLTIU SLTU smartc...
(WORD_REPEAT_RULE)
[duplication] ~385-~385: Možný preklep: zopakovali ste slovo
Context: ...olana Soneium soyboy Spearbit SRAV SRLV Stablecoins stablecoins statefulset structs subcomponents subga...
(WORD_REPEAT_RULE)
[duplication] ~397-~397: Možný preklep: zopakovali ste slovo
Context: ...nd SUBU Sunnyside SUPERCHAIN Superchain superchain Superchain's superchainerc Superlend Superloans Su...
(WORD_REPEAT_RULE)
[duplication] ~404-~404: Možný preklep: zopakovali ste slovo
Context: ...uperlend Superloans Superscan Superseed Supersim supersim SYNCMODE syncmode SYNCTARGET synctarget...
(WORD_REPEAT_RULE)
[duplication] ~406-~406: Možný preklep: zopakovali ste slovo
Context: ...s Superscan Superseed Supersim supersim SYNCMODE syncmode SYNCTARGET synctarget syscalls SYSCON t...
(WORD_REPEAT_RULE)
[duplication] ~408-~408: Možný preklep: zopakovali ste slovo
Context: ...eed Supersim supersim SYNCMODE syncmode SYNCTARGET synctarget syscalls SYSCON thirdweb threadcreate t...
(WORD_REPEAT_RULE)
[duplication] ~436-~436: Možný preklep: zopakovali ste slovo
Context: ...ubmitted UPNP upstreaming VERKLE verkle VHOSTS vhosts Viem viem Viem's viem's VMDEBUG vmdebug...
(WORD_REPEAT_RULE)
[duplication] ~438-~438: Možný preklep: zopakovali ste slovo
Context: ...upstreaming VERKLE verkle VHOSTS vhosts Viem viem Viem's viem's VMDEBUG vmdebug VMODULE v...
(WORD_REPEAT_RULE)
[duplication] ~442-~442: Možný preklep: zopakovali ste slovo
Context: ...e VHOSTS vhosts Viem viem Viem's viem's VMDEBUG vmdebug VMODULE vmodule xlarge XORI ZKPs ZKVM Z...
(WORD_REPEAT_RULE)
[duplication] ~444-~444: Možný preklep: zopakovali ste slovo
Context: ...Viem viem Viem's viem's VMDEBUG vmdebug VMODULE vmodule xlarge XORI ZKPs ZKVM Zora zora
(WORD_REPEAT_RULE)
[duplication] ~450-~450: Možný preklep: zopakovali ste slovo
Context: ...g VMODULE vmodule xlarge XORI ZKPs ZKVM Zora zora
(WORD_REPEAT_RULE)
pages/notices/pectra-fees.mdx
[style] ~24-~24: Consider a more concise word here.
Context: ...e, so almost all chains make use of it. In order to continue to optimize for chains operati...
(IN_ORDER_TO_PREMIUM)
[grammar] ~26-~26: A verb may be missing after “It”. Please verify.
Context: ...xperience a reduction in profitability. It possible for such chains to be making a loss on ...
(PRP_JJ)
[uncategorized] ~26-~26: A comma may be missing after the conjunctive/linking adverb ‘Therefore’.
Context: ... costs under certain market conditions. Therefore all chains should check their fee scala...
(SENT_START_CONJUNCTIVE_LINKING_ADVERB_COMMA)
[style] ~41-~41: Consider a more concise word here.
Context: ...to tweak the Ecotone scalars as desired in order to adjust the profitability of your chain....
(IN_ORDER_TO_PREMIUM)
🔇 Additional comments (6)
pages/notices/_meta.json (1)
2-2: Register new notice in metadata
The entry"pectra-fees": "Pectra user fees notice"correctly registers the new notice page in_meta.json, matchingpages/notices/pectra-fees.mdx.pages/notices/pectra-changes.mdx (1)
105-108: Verify relative link to the new notice
The new step “Double-check your fee scalars” adds a helpful reference topectra-fees.mdx. Please confirm that the relative link./pectra-fees.mdxresolves correctly in the built site (you may want to use an absolute link/notices/pectra-feesif needed).pages/operators/chain-operators/management/blobs.mdx (3)
52-52: Confirm code snippet formatting
The spacing around the assignment operator in the example (newBaseFeeScalar = prevBaseFeeScalar * 1.1) improves readability and aligns with common style.
124-126: Check link path in callout
The warning callout correctly highlights the need to scaleBaseFeeScalarpost-Pectra, but please verify that the relative link../../notices/pectra-fees.mdxresolves to the intended notice page (consider using an absolute link/notices/pectra-fees).
152-155: Introduce auto DA mode section
The new “Use auto DA mode in your batcher” section provides valuable guidance on cost optimization by automatically switching between blobs and calldata.pages/notices/pectra-fees.mdx (1)
1-16: Frontmatter completeness and correctness
All required frontmatter fields (title,description,lang,content_type,topic,personas,categories) are present and non-empty for a notice page.
Wiz Scan Summary
To detect these findings earlier in the dev lifecycle, try using Wiz Code VS Code Extension. |
There was a problem hiding this comment.
Actionable comments posted: 2
♻️ Duplicate comments (1)
pages/notices/pectra-fees.mdx (1)
26-27: Fix grammar, punctuation, and spelling in loss warning
This sentence is missing a verb, lacks punctuation, and 'availabilty' is misspelled. Please apply the following corrections:- It possible for such chains to be making a loss on data availabilty costs under certain market conditions. Therefore all chains should check their fee scalar config. + It is possible for such chains to incur losses on data availability costs under certain market conditions. Therefore, all chains should check their fee scalar configuration.🧰 Tools
🪛 LanguageTool
[grammar] ~26-~26: A verb may be missing after “It”. Please verify.
Context: ...xperience a reduction in profitability. It possible for such chains to be making a loss on ...(PRP_JJ)
[uncategorized] ~26-~26: This verb may not be in the correct tense. Consider changing the tense to fit the context better.
Context: ...ability. It possible for such chains to be making a loss on data availabilty costs under ...(AI_EN_LECTOR_REPLACEMENT_VERB_TENSE)
[uncategorized] ~26-~26: A comma may be missing after the conjunctive/linking adverb ‘Therefore’.
Context: ... costs under certain market conditions. Therefore all chains should check their fee scala...(SENT_START_CONJUNCTIVE_LINKING_ADVERB_COMMA)
🧹 Nitpick comments (3)
pages/notices/pectra-fees.mdx (3)
18-18: Consider rephrasing the H1 for clarity
'Pectra impact on…' could be clearer as 'Impact of Pectra on user fees and chain profitability.' This improves readability and aligns with common phrasing.- # Pectra impact on user fees and chain profitability + # Impact of Pectra on user fees and chain profitability
24-24: Simplify phrasing for brevity
Use 'To continue optimizing' instead of the longer 'In order to continue to optimize':- In order to continue to optimize for chains operating with blob DA, the Optimism protocol's current DA fee pricing formula has remained unchanged despite Pectra activating on Ethereum. + To continue optimizing for chains operating with blob DA, the Optimism protocol's current DA fee pricing formula has remained unchanged despite Pectra activating on Ethereum.🧰 Tools
🪛 LanguageTool
[style] ~24-~24: Consider a more concise word here.
Context: ...e, so almost all chains make use of it. In order to continue to optimize for chains operati...(IN_ORDER_TO_PREMIUM)
40-40: Add missing comma and adjust preposition
For clarity and correctness, add a comma after 'Without such a change' and use 'on the rare occasions':- Without such a change it is likely that you are overcharging users most of the time, and undercharging them in the rare occasions where blob DA is more expensive than calldata DA on Ethereum mainnet. + Without such a change, it is likely that you are overcharging users most of the time and undercharging them on the rare occasions when blob DA is more expensive than calldata DA on Ethereum mainnet.🧰 Tools
🪛 LanguageTool
[uncategorized] ~40-~40: A comma might be missing here.
Context: ...ately for using blob DA. Without such a change it is likely that you are overcharging ...(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)
[uncategorized] ~40-~40: The preposition “on” seems more likely in this position than the preposition “in”.
Context: ...ost of the time, and undercharging them in the rare occasions where blob DA is mor...(AI_EN_LECTOR_REPLACEMENT_PREPOSITION_IN_ON)
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (2)
pages/notices/pectra-fees.mdx(1 hunks)words.txt(2 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
`**/*.mdx`: "ALWAYS review Markdown content THOROUGHLY with the following criteria: - First, check the frontmatter section at the top of the file: 1. For regular pages, ensure AL...
**/*.mdx: "ALWAYS review Markdown content THOROUGHLY with the following criteria:
- First, check the frontmatter section at the top of the file:
- For regular pages, ensure ALL these fields are present and not empty:
--- title: [non-empty] lang: [non-empty] description: [non-empty] topic: [non-empty] personas: [non-empty array] categories: [non-empty array] content_type: [valid type] ---
- For landing pages (index.mdx or files with ), only these fields are required:
--- title: [non-empty] lang: [non-empty] description: [non-empty] topic: [non-empty] ---
- If any required fields are missing or empty, comment:
'This file appears to be missing required metadata. Please check keywords.config.yaml for valid options and add the required fields manually. You can validate your changes by running:pnpm validate-metadata ```'- Use proper nouns in place of personal pronouns like 'We' and 'Our' to maintain consistency in communal documentation.
- Avoid gender-specific language and use the imperative form.
- Monitor capitalization for emphasis. Avoid using all caps, italics, or bold for emphasis.
- Ensure proper nouns are capitalized in sentences.
- Apply the Oxford comma.
- Use proper title case for buttons, tab names, page names, and links. Sentence case should be used for body content and short phrases, even in links.
- Use correct spelling and grammar at all times (IMPORTANT).
- For H1, H2, and H3 headers:
- Use sentence case, capitalizing only the first word.
- Preserve the capitalization of proper nouns, technical terms, and acronyms as defined in the 'nouns.txt' file located in the root directory of the project.
- Do not automatically lowercase words that appear in the 'nouns.txt' file, regardless of their position in the header.
- Flag any headers that seem to inconsistently apply these rules for manual review.
- When reviewing capitalization, always refer to the 'nouns.txt' file for the correct capitalization of proper nouns and technical terms specific to the project.
"
pages/notices/pectra-fees.mdx
🪛 LanguageTool
pages/notices/pectra-fees.mdx
[style] ~24-~24: Consider a more concise word here.
Context: ...e, so almost all chains make use of it. In order to continue to optimize for chains operati...
(IN_ORDER_TO_PREMIUM)
[grammar] ~26-~26: A verb may be missing after “It”. Please verify.
Context: ...xperience a reduction in profitability. It possible for such chains to be making a loss on ...
(PRP_JJ)
[uncategorized] ~26-~26: This verb may not be in the correct tense. Consider changing the tense to fit the context better.
Context: ...ability. It possible for such chains to be making a loss on data availabilty costs under ...
(AI_EN_LECTOR_REPLACEMENT_VERB_TENSE)
[uncategorized] ~26-~26: A comma may be missing after the conjunctive/linking adverb ‘Therefore’.
Context: ... costs under certain market conditions. Therefore all chains should check their fee scala...
(SENT_START_CONJUNCTIVE_LINKING_ADVERB_COMMA)
[uncategorized] ~40-~40: A comma might be missing here.
Context: ...ately for using blob DA. Without such a change it is likely that you are overcharging ...
(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)
[uncategorized] ~40-~40: The preposition “on” seems more likely in this position than the preposition “in”.
Context: ...ost of the time, and undercharging them in the rare occasions where blob DA is mor...
(AI_EN_LECTOR_REPLACEMENT_PREPOSITION_IN_ON)
[style] ~42-~42: Consider a more concise word here.
Context: ...to tweak the Ecotone scalars as desired in order to adjust the profitability of your chain....
(IN_ORDER_TO_PREMIUM)
words.txt
[duplication] ~95-~95: Možný preklep: zopakovali ste slovo
Context: ...datacap DATACAP datadir DATADIR devdocs devnet Devnet devnets Devnets direnv disabletxpoolgos...
(WORD_REPEAT_RULE)
🔇 Additional comments (1)
words.txt (1)
95-95:✅ Verification successful
Verify 'devdocs' entry for consistency
Ensure that the lowercase 'devdocs' entry aligns with how the term is used and cased across the documentation. If 'DevDocs' is a proper noun or brand name, consider capitalizing it consistently.
🏁 Script executed:
#!/bin/bash # Verify occurrences of 'devdocs' in the docs to confirm correct casing rg -n 'devdocs' -- '*.mdx' '*.md'Length of output: 124
🏁 Script executed:
#!/bin/bash # Search entire repository for any case variations of 'devdocs' rg -in 'devdocs' .Length of output: 212
No ‘devdocs’ casing inconsistencies detected
The term is used exclusively in lowercase in both the search dictionary and the documentation, so no action is needed:
- words.txt:95 –
devdocs- pages/stack/superchain-ops-guide.mdx:131 – link text
[devdocs]🧰 Tools
🪛 LanguageTool
[duplication] ~95-~95: Možný preklep: zopakovali ste slovo
Context: ...datacap DATACAP datadir DATADIR devdocs devnet Devnet devnets Devnets direnv disabletxpoolgos...(WORD_REPEAT_RULE)
There was a problem hiding this comment.
Actionable comments posted: 0
♻️ Duplicate comments (1)
pages/notices/pectra-fees.mdx (1)
3-3: Fix noun/verb confusion in frontmatter description
The frontmatterdescriptionuses the verb “affect” where the noun “effect” is appropriate. Update it to:- description: L1 Pectra affect on user fees and chain profitability analysis + description: L1 Pectra effect on user fees and chain profitability analysis
🧹 Nitpick comments (3)
pages/notices/pectra-fees.mdx (3)
22-22: Ensure consistent naming of OP Stack
The term “OPStack” here should match the usage “OP Stack” elsewhere in the document to maintain naming consistency. Change:- may affect OPStack chains *before the [Ecotone upgrade]... + may affect OP Stack chains *before the [Ecotone upgrade]...
26-26: Fix grammar and spelling in warning sentence
This sentence is missing the verb “is”, has a typo in “availability”, and needs a comma after “Therefore”. Apply:- It possible for such chains to be making a loss on data availabilty costs under certain market conditions. Therefore all chains should check their fee scalar config. + It is possible for such chains to be making a loss on data availability costs under certain market conditions. Therefore, all chains should check their fee scalar config.🧰 Tools
🪛 LanguageTool
[grammar] ~26-~26: A verb may be missing after “It”. Please verify.
Context: ...xperience a reduction in profitability. It possible for such chains to be making a loss on ...(PRP_JJ)
[uncategorized] ~26-~26: This verb may not be in the correct tense. Consider changing the tense to fit the context better.
Context: ...ability. It possible for such chains to be making a loss on data availabilty costs under ...(AI_EN_LECTOR_REPLACEMENT_VERB_TENSE)
[uncategorized] ~26-~26: A comma may be missing after the conjunctive/linking adverb ‘Therefore’.
Context: ... costs under certain market conditions. Therefore all chains should check their fee scala...(SENT_START_CONJUNCTIVE_LINKING_ADVERB_COMMA)
40-40: Add comma after introductory clause and adjust preposition
The sentence would read more clearly with a comma after the opening clause and using “on” instead of “in”:- Without such a change it is likely that you are overcharging users most of the time, and undercharging them in the rare occasions where blob DA is more expensive than calldata DA on Ethereum mainnet. + Without such a change, it is likely that you are overcharging users most of the time and undercharging them on the rare occasions where blob DA is more expensive than calldata DA on Ethereum mainnet.🧰 Tools
🪛 LanguageTool
[uncategorized] ~40-~40: A comma might be missing here.
Context: ...ately for using blob DA. Without such a change it is likely that you are overcharging ...(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)
[uncategorized] ~40-~40: The preposition “on” seems more likely in this position than the preposition “in”.
Context: ...ost of the time, and undercharging them in the rare occasions where blob DA is mor...(AI_EN_LECTOR_REPLACEMENT_PREPOSITION_IN_ON)
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (3)
pages/notices/pectra-changes.mdx(1 hunks)pages/notices/pectra-fees.mdx(1 hunks)pages/operators/chain-operators/management/blobs.mdx(3 hunks)
🚧 Files skipped from review as they are similar to previous changes (2)
- pages/notices/pectra-changes.mdx
- pages/operators/chain-operators/management/blobs.mdx
🧰 Additional context used
📓 Path-based instructions (1)
`**/*.mdx`: "ALWAYS review Markdown content THOROUGHLY with the following criteria: - First, check the frontmatter section at the top of the file: 1. For regular pages, ensure AL...
**/*.mdx: "ALWAYS review Markdown content THOROUGHLY with the following criteria:
- First, check the frontmatter section at the top of the file:
- For regular pages, ensure ALL these fields are present and not empty:
--- title: [non-empty] lang: [non-empty] description: [non-empty] topic: [non-empty] personas: [non-empty array] categories: [non-empty array] content_type: [valid type] ---
- For landing pages (index.mdx or files with ), only these fields are required:
--- title: [non-empty] lang: [non-empty] description: [non-empty] topic: [non-empty] ---
- If any required fields are missing or empty, comment:
'This file appears to be missing required metadata. Please check keywords.config.yaml for valid options and add the required fields manually. You can validate your changes by running:pnpm validate-metadata ```'- Use proper nouns in place of personal pronouns like 'We' and 'Our' to maintain consistency in communal documentation.
- Avoid gender-specific language and use the imperative form.
- Monitor capitalization for emphasis. Avoid using all caps, italics, or bold for emphasis.
- Ensure proper nouns are capitalized in sentences.
- Apply the Oxford comma.
- Use proper title case for buttons, tab names, page names, and links. Sentence case should be used for body content and short phrases, even in links.
- Use correct spelling and grammar at all times (IMPORTANT).
- For H1, H2, and H3 headers:
- Use sentence case, capitalizing only the first word.
- Preserve the capitalization of proper nouns, technical terms, and acronyms as defined in the 'nouns.txt' file located in the root directory of the project.
- Do not automatically lowercase words that appear in the 'nouns.txt' file, regardless of their position in the header.
- Flag any headers that seem to inconsistently apply these rules for manual review.
- When reviewing capitalization, always refer to the 'nouns.txt' file for the correct capitalization of proper nouns and technical terms specific to the project.
"
pages/notices/pectra-fees.mdx
🪛 LanguageTool
pages/notices/pectra-fees.mdx
[style] ~24-~24: Consider a more concise word here.
Context: ...e, so almost all chains make use of it. In order to continue to optimize for chains operati...
(IN_ORDER_TO_PREMIUM)
[grammar] ~26-~26: A verb may be missing after “It”. Please verify.
Context: ...xperience a reduction in profitability. It possible for such chains to be making a loss on ...
(PRP_JJ)
[uncategorized] ~26-~26: This verb may not be in the correct tense. Consider changing the tense to fit the context better.
Context: ...ability. It possible for such chains to be making a loss on data availabilty costs under ...
(AI_EN_LECTOR_REPLACEMENT_VERB_TENSE)
[uncategorized] ~26-~26: A comma may be missing after the conjunctive/linking adverb ‘Therefore’.
Context: ... costs under certain market conditions. Therefore all chains should check their fee scala...
(SENT_START_CONJUNCTIVE_LINKING_ADVERB_COMMA)
[uncategorized] ~40-~40: A comma might be missing here.
Context: ...ately for using blob DA. Without such a change it is likely that you are overcharging ...
(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)
[uncategorized] ~40-~40: The preposition “on” seems more likely in this position than the preposition “in”.
Context: ...ost of the time, and undercharging them in the rare occasions where blob DA is mor...
(AI_EN_LECTOR_REPLACEMENT_PREPOSITION_IN_ON)
[style] ~42-~42: Consider a more concise word here.
Context: ...to tweak the Ecotone scalars as desired in order to adjust the profitability of your chain....
(IN_ORDER_TO_PREMIUM)
|
|
||
| [EIP-7623](https://eips.ethereum.org/EIPS/eip-7623) increases the amount of gas payable for calldata transactions. These include such transactions as those used by OPStack chains *before the [Ecotone upgrade](https://specs.optimism.io/protocol/ecotone/overview.html)* when blob data availability (blob DA) was introduced. | ||
|
|
||
| Blob DA has now been the default and recommended option for the OPStack for some time, so almost all chains make use of it. In order to continue to optimize for chains operating with blob DA, the Optimism protocol's current DA fee pricing formula has remained unchanged despite Pectra activating on Ethereum. |
There was a problem hiding this comment.
Maybe add something like
"This allowed us to leave the base fee scalar of modern fee configurations unchanged, because it accounts for only the fixed intrinsic gas cost of 21,000 of a blob transaction."
| If your batcher is configured to submit using calldata *only*, then you should: | ||
|
|
||
| * scale your base fee scalar by 10/4. | ||
|
|
||
| This will ensure that, since you are paying exclusively for calldata DA, you are charging users appropriately such that your target profit margin is the same as it was before Pectra. |
There was a problem hiding this comment.
We should add, " under the assumption that you observed a perfectly realized profit margin before the Ethereum Pectra upgrade". And realistically, chains should just watch their actually achieved profit margin and adjust accordingly, which is something they need to do regularly anyways.
There was a problem hiding this comment.
we worked out a rejig of this section, ptal
|
|
||
| This will ensure that, since you are paying exclusively for calldata DA, you are charging users appropriately such that your target profit margin is the same as it was before Pectra. | ||
|
|
||
| If your batcher is configured to submit using blob DA, or configured to automatically choose the cheaper of the two DA modes, then you should adjust your Ecotone scalars for blob DA pricing (meaning a nonzero blob base fee scalar). You are referred back to [this guide](/operators/chain-operators/management/blobs). Doing so will ensure that you are charging accurately for using blob DA. Without such a change it is likely that you are overcharging users most of the time, and undercharging them in the rare occasions where blob DA is more expensive than calldata DA on Ethereum mainnet. |
There was a problem hiding this comment.
We should somehow highlight that this paragraph applies only to chains who use an outdated calldata base fee-only fee configuration.
There was a problem hiding this comment.
And we should acknowledge that this is only possible if the SystemConfig has a version() of at least x.y.z (the Ecotone one), and that an upgrade to a newer SystemConfig is strongly recommended.
There was a problem hiding this comment.
I added subsections here 4be4827 which hopefully helps.
Let's discuss the versioning thing.
There was a problem hiding this comment.
Discussion with @sebastianst today: even very old SystemConfig implementations can actually support a blob DA config.
The instructions here https://docs.optimism.io/operators/chain-operators/management/blobs would not apply out of the box. But on a case-by-case basis it might be an interesting option.
There was a problem hiding this comment.
Probably not worth getting into the weeds of this versioning subtlety here.
There was a problem hiding this comment.
I realize that his file needs an overhaul. By default, all examples should use blobs and a modern blob base fee-based config.
There was a problem hiding this comment.
Discussed with @sebastianst: we think there are still edge cases (very quiet chains) which may want to configure for exclusively calldata.
Builds on #1607