deploy: 9d2eed7

print.html

@@ -7430,7 +7430,7 @@ <h1 id="op-stack-configurability"><a class="header" href="#op-stack-configurabil
 These requirements are currently a draft, pending governance approval.</p>
 <h2 id="consensus-parameters"><a class="header" href="#consensus-parameters">Consensus Parameters</a></h2>
 <div class="table-wrapper"><table><thead><tr><th>Config Property</th><th>Description</th><th>Administrator</th><th>Standard Config Requirement</th><th>Notes</th></tr></thead><tbody>
-<tr><td><a href="https://github.com/ethereum-optimism/optimism/blob/c927ed9e8af501fd330349607a2b09a876a9a1fb/packages/contracts-bedrock/src/L1/SystemConfig.sol#L176">Batch Inbox address</a></td><td>L1 address where calldata/blobs are posted (see <a href="protocol/../glossary.html#batcher-transaction">Batcher Transaction</a>).</td><td>Static</td><td>Current convention is <code>0xff000...000{chainId}</code>.</td><td>Follow convention if possible. A future hardfork plans to migrate Batch Inbox Addresses to better support <code>uint256</code> sized chain IDs.</td></tr>
+<tr><td><a href="https://github.com/ethereum-optimism/optimism/blob/c927ed9e8af501fd330349607a2b09a876a9a1fb/packages/contracts-bedrock/src/L1/SystemConfig.sol#L176">Batch Inbox address</a></td><td>L1 address where calldata/blobs are posted (see <a href="protocol/../glossary.html#batcher-transaction">Batcher Transaction</a>).</td><td>Static</td><td>Current convention is <code>versionByte || keccak256(bytes32(chainId))[:19]</code>, where <code>||</code> denotes concatenation, <code>versionByte</code> is <code>0x00</code>, and <code>chainId</code> is a <code>uint256</code>.</td><td>It is recommended, but not required, to follow this convention.</td></tr>
 <tr><td><a href="protocol/./system_config.html#batcherhash-bytes32">Batcher Hash</a></td><td>A versioned hash of the current authorized batcher sender(s).</td><td><a href="protocol/configurability.html#admin-roles">System Config Owner</a></td><td><code>bytes32(uint256(uint160(batchSubmitterAddress)))</code></td><td><a href="protocol/../protocol/batcher.html">Batch Submitter</a> address padded with zeros to fit 32 bytes.</td></tr>
 <tr><td><a href="https://github.com/ethereum-optimism/superchain-registry/blob/main/superchain/configs/chainids.json">Chain ID</a></td><td>Unique ID of Chain used for TX signature validation.</td><td>Static</td><td>Foundation-approved, globally unique value <sup class="footnote-reference"><a href="#chain-id">1</a></sup>.</td><td>Foundation will ensure chains are responsible with their chain IDs until there's a governance process in place.</td></tr>
 <tr><td><a href="protocol/../protocol/withdrawals.html#withdrawal-flow">Challenge Period</a></td><td>Length of time for which an output root can be removed, and for which it is not considered finalized.</td><td><a href="protocol/configurability.html#admin-roles">L1 Proxy Admin</a></td><td>7 days</td><td>High security. Excessively safe upper bound that leaves enough time to consider social layer solutions to a hack if necessary. Allows enough time for other network participants to challenge the integrity of the corresponding output root.</td></tr>

protocol/configurability.html

@@ -215,7 +215,7 @@ <h1 id="op-stack-configurability"><a class="header" href="#op-stack-configurabil
 These requirements are currently a draft, pending governance approval.</p>
 <h2 id="consensus-parameters"><a class="header" href="#consensus-parameters">Consensus Parameters</a></h2>
 <div class="table-wrapper"><table><thead><tr><th>Config Property</th><th>Description</th><th>Administrator</th><th>Standard Config Requirement</th><th>Notes</th></tr></thead><tbody>
-<tr><td><a href="https://github.com/ethereum-optimism/optimism/blob/c927ed9e8af501fd330349607a2b09a876a9a1fb/packages/contracts-bedrock/src/L1/SystemConfig.sol#L176">Batch Inbox address</a></td><td>L1 address where calldata/blobs are posted (see <a href="../glossary.html#batcher-transaction">Batcher Transaction</a>).</td><td>Static</td><td>Current convention is <code>0xff000...000{chainId}</code>.</td><td>Follow convention if possible. A future hardfork plans to migrate Batch Inbox Addresses to better support <code>uint256</code> sized chain IDs.</td></tr>
+<tr><td><a href="https://github.com/ethereum-optimism/optimism/blob/c927ed9e8af501fd330349607a2b09a876a9a1fb/packages/contracts-bedrock/src/L1/SystemConfig.sol#L176">Batch Inbox address</a></td><td>L1 address where calldata/blobs are posted (see <a href="../glossary.html#batcher-transaction">Batcher Transaction</a>).</td><td>Static</td><td>Current convention is <code>versionByte || keccak256(bytes32(chainId))[:19]</code>, where <code>||</code> denotes concatenation, <code>versionByte</code> is <code>0x00</code>, and <code>chainId</code> is a <code>uint256</code>.</td><td>It is recommended, but not required, to follow this convention.</td></tr>
 <tr><td><a href="./system_config.html#batcherhash-bytes32">Batcher Hash</a></td><td>A versioned hash of the current authorized batcher sender(s).</td><td><a href="#admin-roles">System Config Owner</a></td><td><code>bytes32(uint256(uint160(batchSubmitterAddress)))</code></td><td><a href="../protocol/batcher.html">Batch Submitter</a> address padded with zeros to fit 32 bytes.</td></tr>
 <tr><td><a href="https://github.com/ethereum-optimism/superchain-registry/blob/main/superchain/configs/chainids.json">Chain ID</a></td><td>Unique ID of Chain used for TX signature validation.</td><td>Static</td><td>Foundation-approved, globally unique value <sup class="footnote-reference"><a href="#chain-id">1</a></sup>.</td><td>Foundation will ensure chains are responsible with their chain IDs until there's a governance process in place.</td></tr>
 <tr><td><a href="../protocol/withdrawals.html#withdrawal-flow">Challenge Period</a></td><td>Length of time for which an output root can be removed, and for which it is not considered finalized.</td><td><a href="#admin-roles">L1 Proxy Admin</a></td><td>7 days</td><td>High security. Excessively safe upper bound that leaves enough time to consider social layer solutions to a hack if necessary. Allows enough time for other network participants to challenge the integrity of the corresponding output root.</td></tr>