From 96c04b5d559eb5591cad45c2b2915a450ce3c6c7 Mon Sep 17 00:00:00 2001 From: geoknee Date: Fri, 16 May 2025 10:28:35 +0100 Subject: [PATCH 1/8] use a table to summarize actions --- pages/notices/pectra-fees.mdx | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/pages/notices/pectra-fees.mdx b/pages/notices/pectra-fees.mdx index d9167fa85..c01eb4612 100644 --- a/pages/notices/pectra-fees.mdx +++ b/pages/notices/pectra-fees.mdx @@ -37,6 +37,15 @@ Please review your [Ecotone scalar chain configuration](/operators/chain-operato If your chain uses a zero blob base fee scalar, meaning it's configured to price for calldata only, you may need to update the base fee scalar and/or the blob base fee scalar. Otherwise, no action is necessary and the rest of this section does not apply. + + | `baseFeeScalar` | `blobBaseFeeScalar` | batcher DA | Action | + |-----------------|---------------------|-------------------------------|----------------------------------------------------------------------------------------- | + | any | >~10^4 | `calldata`, `blob` or `auto` | No action required | + | b_s | 0 | `calldata` | Check scalar config, and considering setting b_s -> b_s * 10/4 to preserve profit margin | + | any | 0 | `blob` or `auto` | Check scalar config, and considering setting a positive `blobBaseFeeScalar` | + + + ### Chains charging for calldata DA and spending on calldata DA If your chain uses a zero blob base fee scalar and your batcher is configured to submit using calldata *only*, then you should take the opportunity to check your chain's profit margin according to [this guide](/operators/chain-operators/management/blobs) and make any adjustments to your Ecotone scalars as necessary. This will ensure that, since you are paying exclusively for calldata DA, you are charging users appropriately such that your target profit margin is as desired. From df186b52e1ae0d7c3adaed2728e826189f4a4ae5 Mon Sep 17 00:00:00 2001 From: geoknee Date: Fri, 16 May 2025 12:21:00 +0100 Subject: [PATCH 2/8] refine --- pages/notices/pectra-fees.mdx | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-) diff --git a/pages/notices/pectra-fees.mdx b/pages/notices/pectra-fees.mdx index c01eb4612..3ced0845d 100644 --- a/pages/notices/pectra-fees.mdx +++ b/pages/notices/pectra-fees.mdx @@ -37,12 +37,14 @@ Please review your [Ecotone scalar chain configuration](/operators/chain-operato If your chain uses a zero blob base fee scalar, meaning it's configured to price for calldata only, you may need to update the base fee scalar and/or the blob base fee scalar. Otherwise, no action is necessary and the rest of this section does not apply. +The impact and recommended actions for each of the possible configurations are summarised in the followsing table, and explained in more detail below: - | `baseFeeScalar` | `blobBaseFeeScalar` | batcher DA | Action | - |-----------------|---------------------|-------------------------------|----------------------------------------------------------------------------------------- | - | any | >~10^4 | `calldata`, `blob` or `auto` | No action required | - | b_s | 0 | `calldata` | Check scalar config, and considering setting b_s -> b_s * 10/4 to preserve profit margin | - | any | 0 | `blob` or `auto` | Check scalar config, and considering setting a positive `blobBaseFeeScalar` | + + | `baseFeeScalar` | `blobBaseFeeScalar` | batcher DA | Impact | Action | + |-----------------|---------------------|-------------------------------|------- | ---------------------------------------------------------------------------------------- | + | any | >~10^4 | `calldata`, `blob` or `auto` | | No action required | + | `x` | 0 | `calldata` | Undercharging L2 Users | Check scalar config, and considering setting `baseFeeScalar` to `x * 10/4` to preserve profit margin | + | any | 0 | `blob` or `auto` | Overcharging L2 Users most of the time | Check scalar config, and considering setting a positive `blobBaseFeeScalar` | @@ -54,7 +56,9 @@ If your profit margin was perfectly tuned before Pectra, then you should scale y ### Chains charging for calldata DA and spending on blob DA If your chain uses a zero blob base fee scalar and 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. -As ever, you may continue to tweak the Ecotone scalars as desired in order to adjust the profitability of your chain. + +### General remarks +As ever, you may continue to tweak the Ecotone scalars as desired in order to adjust the profitability of your chain. We recommend profitability is monitored continually so that you can adjust the scalars as necessary. ### Technical references From 9202267303c3a75dd826331adebd4ef10ef12173 Mon Sep 17 00:00:00 2001 From: geoknee Date: Fri, 16 May 2025 12:24:22 +0100 Subject: [PATCH 3/8] pnpm fix --- pages/notices/pectra-fees.mdx | 21 ++++++++++----------- 1 file changed, 10 insertions(+), 11 deletions(-) diff --git a/pages/notices/pectra-fees.mdx b/pages/notices/pectra-fees.mdx index 3ced0845d..238be7b9d 100644 --- a/pages/notices/pectra-fees.mdx +++ b/pages/notices/pectra-fees.mdx @@ -31,33 +31,32 @@ Chains configured for blob data availability remain entirely unaffected by the P Since the Ecotone upgrade, the Optimism protocol prices L2 transactions using a function that incorporates the L1 base fee as well as the L1 blob base fee. The other inputs are the so-called "Ecotone scalars": operator-controlled parameters stored in the SystemConfig contract which can be used to tune the chain's (approximate) target profit margin for DA. -Please review your [Ecotone scalar chain configuration](/operators/chain-operators/management/blobs). +Please review your [Ecotone scalar chain configuration](/operators/chain-operators/management/blobs). -If your chain uses a zero blob base fee scalar, meaning it's configured to price for calldata only, you may need to update the base fee scalar and/or the blob base fee scalar. Otherwise, no action is necessary and the rest of this section does not apply. + If your chain uses a zero blob base fee scalar, meaning it's configured to price for calldata only, you may need to update the base fee scalar and/or the blob base fee scalar. Otherwise, no action is necessary and the rest of this section does not apply. The impact and recommended actions for each of the possible configurations are summarised in the followsing table, and explained in more detail below: - - | `baseFeeScalar` | `blobBaseFeeScalar` | batcher DA | Impact | Action | - |-----------------|---------------------|-------------------------------|------- | ---------------------------------------------------------------------------------------- | - | any | >~10^4 | `calldata`, `blob` or `auto` | | No action required | - | `x` | 0 | `calldata` | Undercharging L2 Users | Check scalar config, and considering setting `baseFeeScalar` to `x * 10/4` to preserve profit margin | - | any | 0 | `blob` or `auto` | Overcharging L2 Users most of the time | Check scalar config, and considering setting a positive `blobBaseFeeScalar` | - - +| `baseFeeScalar` | `blobBaseFeeScalar` | batcher DA | Impact | Action | +| --------------- | ------------------- | ----------------------------- | -------------------------------------- | ---------------------------------------------------------------------------------------------------- | +| any | >\~10^4 | `calldata`, `blob` or `auto` | | No action required | +| `x` | 0 | `calldata` | Undercharging L2 Users | Check scalar config, and considering setting `baseFeeScalar` to `x * 10/4` to preserve profit margin | +| any | 0 | `blob` or `auto` | Overcharging L2 Users most of the time | Check scalar config, and considering setting a positive `blobBaseFeeScalar` | ### Chains charging for calldata DA and spending on calldata DA + If your chain uses a zero blob base fee scalar and your batcher is configured to submit using calldata *only*, then you should take the opportunity to check your chain's profit margin according to [this guide](/operators/chain-operators/management/blobs) and make any adjustments to your Ecotone scalars as necessary. This will ensure that, since you are paying exclusively for calldata DA, you are charging users appropriately such that your target profit margin is as desired. If your profit margin was perfectly tuned before Pectra, then you should scale your base fee scalar by 10/4. ### Chains charging for calldata DA and spending on blob DA -If your chain uses a zero blob base fee scalar and 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. +If your chain uses a zero blob base fee scalar and 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. ### General remarks + As ever, you may continue to tweak the Ecotone scalars as desired in order to adjust the profitability of your chain. We recommend profitability is monitored continually so that you can adjust the scalars as necessary. ### Technical references From 20bfcfbfa5ead7602ee9e24002dda940fb69c273 Mon Sep 17 00:00:00 2001 From: geoknee Date: Fri, 16 May 2025 12:25:01 +0100 Subject: [PATCH 4/8] tweak --- pages/notices/pectra-fees.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/notices/pectra-fees.mdx b/pages/notices/pectra-fees.mdx index 238be7b9d..5fd6626e5 100644 --- a/pages/notices/pectra-fees.mdx +++ b/pages/notices/pectra-fees.mdx @@ -34,7 +34,7 @@ Since the Ecotone upgrade, the Optimism protocol prices L2 transactions using a Please review your [Ecotone scalar chain configuration](/operators/chain-operators/management/blobs). - If your chain uses a zero blob base fee scalar, meaning it's configured to price for calldata only, you may need to update the base fee scalar and/or the blob base fee scalar. Otherwise, no action is necessary and the rest of this section does not apply. + If your chain uses a zero blob base fee scalar, meaning it's configured to price for calldata only, you may need to update the base fee scalar and/or the blob base fee scalar. Otherwise, no action is necessary. The impact and recommended actions for each of the possible configurations are summarised in the followsing table, and explained in more detail below: From 4b8ae75451e7988f0221c0208f7ed70efdc770e6 Mon Sep 17 00:00:00 2001 From: geoknee Date: Fri, 16 May 2025 12:33:52 +0100 Subject: [PATCH 5/8] rabbit suggestions --- pages/notices/pectra-fees.mdx | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/pages/notices/pectra-fees.mdx b/pages/notices/pectra-fees.mdx index 5fd6626e5..3683f37bb 100644 --- a/pages/notices/pectra-fees.mdx +++ b/pages/notices/pectra-fees.mdx @@ -34,16 +34,16 @@ Since the Ecotone upgrade, the Optimism protocol prices L2 transactions using a Please review your [Ecotone scalar chain configuration](/operators/chain-operators/management/blobs). - If your chain uses a zero blob base fee scalar, meaning it's configured to price for calldata only, you may need to update the base fee scalar and/or the blob base fee scalar. Otherwise, no action is necessary. + If your chain uses a zero blob base fee scalar, meaning it is configured to price for calldata only, you may need to update the base fee scalar and/or the blob base fee scalar. Otherwise, no action is necessary. -The impact and recommended actions for each of the possible configurations are summarised in the followsing table, and explained in more detail below: +The impact and recommended actions for each of the possible configurations are summarized in the following table, and explained in more detail below: | `baseFeeScalar` | `blobBaseFeeScalar` | batcher DA | Impact | Action | | --------------- | ------------------- | ----------------------------- | -------------------------------------- | ---------------------------------------------------------------------------------------------------- | -| any | >\~10^4 | `calldata`, `blob` or `auto` | | No action required | -| `x` | 0 | `calldata` | Undercharging L2 Users | Check scalar config, and considering setting `baseFeeScalar` to `x * 10/4` to preserve profit margin | -| any | 0 | `blob` or `auto` | Overcharging L2 Users most of the time | Check scalar config, and considering setting a positive `blobBaseFeeScalar` | +| any | >\~10^4 | `calldata`, `blob`, or `auto` | | No action required | +| `x` | 0 | `calldata` | Undercharging L2 Users | Check scalar config and consider setting `baseFeeScalar` to `x * 10/4` to preserve profit margin | +| any | 0 | `blob` or `auto` | Overcharging L2 Users most of the time | Check scalar config and consider setting a positive `blobBaseFeeScalar` | ### Chains charging for calldata DA and spending on calldata DA @@ -57,7 +57,8 @@ If your chain uses a zero blob base fee scalar and your batcher is configured to ### General remarks -As ever, you may continue to tweak the Ecotone scalars as desired in order to adjust the profitability of your chain. We recommend profitability is monitored continually so that you can adjust the scalars as necessary. +Continue tweaking the Ecotone scalars as desired to adjust your chain's profitability. +We recommend profitability is monitored continually so that you can adjust the scalars as necessary. ### Technical references From 31e40f870f02490a68074a838342b73f8fa7cccb Mon Sep 17 00:00:00 2001 From: geoknee Date: Fri, 16 May 2025 12:36:22 +0100 Subject: [PATCH 6/8] pnpm fix --- pages/notices/pectra-fees.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/pages/notices/pectra-fees.mdx b/pages/notices/pectra-fees.mdx index 3683f37bb..be3b3daba 100644 --- a/pages/notices/pectra-fees.mdx +++ b/pages/notices/pectra-fees.mdx @@ -39,9 +39,9 @@ Please review your [Ecotone scalar chain configuration](/operators/chain-operato The impact and recommended actions for each of the possible configurations are summarized in the following table, and explained in more detail below: -| `baseFeeScalar` | `blobBaseFeeScalar` | batcher DA | Impact | Action | -| --------------- | ------------------- | ----------------------------- | -------------------------------------- | ---------------------------------------------------------------------------------------------------- | -| any | >\~10^4 | `calldata`, `blob`, or `auto` | | No action required | +| `baseFeeScalar` | `blobBaseFeeScalar` | batcher DA | Impact | Action | +| --------------- | ------------------- | ----------------------------- | -------------------------------------- | ------------------------------------------------------------------------------------------------ | +| any | >\~10^4 | `calldata`, `blob`, or `auto` | | No action required | | `x` | 0 | `calldata` | Undercharging L2 Users | Check scalar config and consider setting `baseFeeScalar` to `x * 10/4` to preserve profit margin | | any | 0 | `blob` or `auto` | Overcharging L2 Users most of the time | Check scalar config and consider setting a positive `blobBaseFeeScalar` | From e083b620a06bfe5c12502334facf62b1dbb872ab Mon Sep 17 00:00:00 2001 From: Blessing Krofegha Date: Fri, 16 May 2025 12:41:22 +0100 Subject: [PATCH 7/8] updated wording --- pages/notices/pectra-fees.mdx | 2 +- words.txt | 2 -- 2 files changed, 1 insertion(+), 3 deletions(-) diff --git a/pages/notices/pectra-fees.mdx b/pages/notices/pectra-fees.mdx index be3b3daba..0f5e51c4d 100644 --- a/pages/notices/pectra-fees.mdx +++ b/pages/notices/pectra-fees.mdx @@ -58,7 +58,7 @@ If your chain uses a zero blob base fee scalar and your batcher is configured to ### General remarks Continue tweaking the Ecotone scalars as desired to adjust your chain's profitability. -We recommend profitability is monitored continually so that you can adjust the scalars as necessary. +Chain operators should monitor profitability continuously so that scalars can be adjusted as necessary. ### Technical references diff --git a/words.txt b/words.txt index b2d3f4106..5ba68d7a9 100644 --- a/words.txt +++ b/words.txt @@ -107,7 +107,6 @@ dripcheck Drippie Eigen EIPs -emmitted ENABLEDEPRECATEDPERSONAL enabledeprecatedpersonal enginekind @@ -141,7 +140,6 @@ FPVMs Fraxtal funcationality Funct -gameplay GASCAP gascap gaslessly From 1c672260c06c510ef70ca46ce32f76d1c06f3f33 Mon Sep 17 00:00:00 2001 From: Blessing Krofegha Date: Fri, 16 May 2025 12:48:12 +0100 Subject: [PATCH 8/8] Auto-fix: Update breadcrumbs, spelling dictionary and other automated fixes --- words.txt | 230 +++++++++++++++++++++++++++--------------------------- 1 file changed, 115 insertions(+), 115 deletions(-) diff --git a/words.txt b/words.txt index c834a93c3..5dbe5bf14 100644 --- a/words.txt +++ b/words.txt @@ -1,7 +1,7 @@ -accountqueue ACCOUNTQUEUE -accountslots +accountqueue ACCOUNTSLOTS +accountslots ACDC ADDI ADDIU @@ -9,58 +9,58 @@ ADDU airgap Allnodes allocs -alphanet Alphanet -alphanets +alphanet Alphanets +alphanets altda ANDI Ankr Apeworx Arweave authrpc -autorelay Autorelay +autorelay autorelayer basefee bcde -betanet Betanet -betanets +betanet Betanets +betanets BGEZ BGTZ Biconomy BLEZ -blobpool BLOBPOOL +blobpool blobspace Blockdaemon blockhash blocklists -blocklogs BLOCKLOGS -blockprofilerate +blocklogs BLOCKPROFILERATE +blockprofilerate Blockscout -blockspace Blockspace +blockspace blocktime -blocktimes Blocktimes -bloomfilter +blocktimes BLOOMFILTER +bloomfilter BLTZ Bootcamp bootnode -bootnodes -Bootnodes BOOTNODES +Bootnodes +bootnodes bottlenecked -brotli Brotli -callouts +brotli Callouts +callouts CCIP cdef Celestia @@ -72,65 +72,65 @@ chaosnet Chugsplash Clabby codebases -collateralized Collateralized +collateralized compr Comprensive -computependingblock COMPUTEPENDINGBLOCK +computependingblock confs Consen corsdomain counterfactually -crosschain Crosschain +crosschain Crossmint Dapphub daserver -datacap DATACAP -datadir +datacap DATADIR +datadir devdocs -devnet Devnet -devnets +devnet Devnets +devnets direnv -disabletxpoolgossip DISABLETXPOOLGOSSIP -discv +disabletxpoolgossip Discv +discv DIVU Drand dripcheck Drippie Eigen EIPs -enabledeprecatedpersonal ENABLEDEPRECATEDPERSONAL +enabledeprecatedpersonal enginekind -erigon Erigon -etherbase +erigon ETHERBASE +etherbase Ethernity Ethernow -ethstats ETHSTATS -evmtimeout +ethstats EVMTIMEOUT +evmtimeout excercise executability exfiltrate -exitwhensynced EXITWHENSYNCED -extradata +exitwhensynced EXTRADATA +extradata Farcaster Faultproof -fdlimit FDLIMIT +fdlimit Flashblocks Flashbots forkable @@ -140,52 +140,52 @@ FPVMs Fraxtal funcationality Funct -gascap GASCAP +gascap gaslessly -gcmode GCMODE +gcmode Gelato gifs -globalqueue GLOBALQUEUE -globalslots +globalqueue GLOBALSLOTS +globalslots gokzg growthepie hardfork hardforks -healthcheck HEALTHCHECK +healthcheck healthchecks -historicalrpc HISTORICALRPC -historicalrpctimeout +historicalrpc HISTORICALRPCTIMEOUT -holesky -Holesky +historicalrpctimeout HOLESKY +Holesky +holesky IERC -ignoreprice IGNOREPRICE +ignoreprice Immunefi -inator Inator -influxdbv +inator INFLUXDBV +influxdbv initcode -ipcdisable IPCDISABLE +ipcdisable ipcfile -ipcpath IPCPATH +ipcpath IPFS Isthumus JALR -journalremotes JOURNALREMOTES -jspath +journalremotes JSPATH +jspath jwtsecret Keccak leveldb @@ -194,34 +194,34 @@ Lisk logfile logfmt Mainnets -maxage MAXAGE -maxbackups +maxage MAXBACKUPS -maxpeers +maxbackups MAXPEERS -maxpendpeers +maxpeers MAXPENDPEERS -maxprice +maxpendpeers MAXPRICE -memprofilerate +maxprice MEMPROFILERATE -merkle +memprofilerate Merkle +merkle MFHI MFLO Mgas Minato -minfreedisk MINFREEDISK -minsuggestedpriorityfee +minfreedisk MINSUGGESTEDPRIORITYFEE +minsuggestedpriorityfee Mintable Mintplex MIPSEVM Mitigations -monitorism Monitorism +monitorism Moralis Mordor mountpoint @@ -231,142 +231,142 @@ MTHI MTLO MULT multiaddr -multichain Multichain +multichain multiclient multisigs MULTU nethermind -netrestrict NETRESTRICT -networkid +netrestrict NETWORKID -newpayload +networkid NEWPAYLOAD +newpayload nextra -nocompaction NOCOMPACTION -nodekey +nocompaction NODEKEY -nodekeyhex +nodekey NODEKEYHEX +nodekeyhex nodename Nodies -nodiscover NODISCOVER -nolocals +nodiscover NOLOCALS -noprefetch +nolocals NOPREFETCH -nopruning +noprefetch NOPRUNING -nosyncserve +nopruning NOSYNCSERVE +nosyncserve Numba -offchain Offchain +offchain opchaina opchainb -opcm OPCM +opcm Openfort oplabs opnode's outfile Pausability pcscdpath -pectra Pectra +pectra Pectra's -peerstore Peerstore +peerstore peerstores -permissioned Permissioned -permissionless +permissioned Permissionless +permissionless permissionlessly Perps Peta Pimlico POAP POAPs -pprof PPROF -precommitments +pprof Precommitments +precommitments preconfigured predeploy -predeployed Predeployed -predeploys +predeployed Predeploys +predeploys prefunded -preimage Preimage -preimages +preimage PREIMAGES +preimages preinstall -preinstalls Preinstalls -prestate +preinstalls Prestate +prestate prestates PREVRANDAO -pricebump PRICEBUMP -pricelimit +pricebump PRICELIMIT +pricelimit productionize productionized Protip Proxied -proxyd Proxyd +proxyd Pyth Pyth's QRNG -quicknode Quicknode +quicknode quickstarts rebalancing reemit Reemitting -regenesis Regenesis +regenesis Reimagine -rejournal REJOURNAL -remotedb +rejournal REMOTEDB +remotedb Reown Reown's replayability replayor reposts reproven -requiredblocks REQUIREDBLOCKS +requiredblocks rollouts -rollups Rollups +rollups Routescan rpckind -rpcprefix RPCPREFIX +rpcprefix rpcs RPGF -runbooks Runbooks +runbooks RWAs safedb Schnorr -sepolia -Sepolia SEPOLIA +Sepolia +sepolia seqnr -sequencerhttp SEQUENCERHTTP +sequencerhttp serv signup SLLV @@ -375,16 +375,16 @@ SLTIU SLTU smartcard snapshotlog -snapsync Snapsync +snapsync Solana Soneium soyboy Spearbit SRAV SRLV -stablecoins Stablecoins +stablecoins statefulset structs subcomponents @@ -393,21 +393,21 @@ subheaders subsecond SUBU Sunnyside -superchain -Superchain SUPERCHAIN +Superchain +superchain Superchain's superchainerc Superlend Superloans Superscan Superseed -supersim Supersim -syncmode +supersim SYNCMODE -synctarget +syncmode SYNCTARGET +synctarget syscalls SYSCON thirdweb @@ -420,8 +420,8 @@ Twei txfeecap txmgr txns -txpool TXPOOL +txpool txproxy txproxyd uncensorable @@ -432,21 +432,21 @@ Unprotect unsubmitted UPNP upstreaming -verkle VERKLE -vhosts +verkle VHOSTS -viem +vhosts Viem -viem's +viem Viem's -vmdebug +viem's VMDEBUG -vmodule +vmdebug VMODULE +vmodule xlarge XORI ZKPs ZKVM -zora Zora +zora