Arbos60 upgrade main branch

docs/partials/_glossary-partial.mdx

@@ -3,7 +3,7 @@ partial_type: glossary
 title: 'Arbitrum Glossary Definitions'
 description: 'Comprehensive glossary of Arbitrum terminology and definitions'
 author: anegg0
-last_reviewed: 2026-06-08
+last_reviewed: 2026-06-17
 ---
 
 ### Activation {#activation}
@@ -409,6 +409,12 @@ Anyone can become a validator by running an Arbitrum node, without permission.
 
 A web application maintained by [Offchain Labs](/intro/glossary#offchain-labs) showcasing the Arbitrum ecosystem; visit it [here](https://portal.arbitrum.io/).
 
+### Prechecker Node {#prechecker-node}
+
+An [Arbitrum full node](/intro/glossary#arbitrum-full-node) configured to pre-validate transactions before forwarding `eth_sendRawTransaction` to the [Sequencer](/intro/glossary#sequencer), insulating it from transactions that would fail.
+
+At a configurable strictness level, a prechecker verifies the transaction type, signature, intrinsic gas (including L1 calldata gas), fee cap, nonce, sender balance, and any `eth_sendRawTransactionConditional` storage conditions. When [compliance filtering](/launch-arbitrum-chain/configure-your-chain/advanced/compliance-filtering) is enabled, it also rejects transactions that touch restricted addresses.
+
 ### Precompile {#precompile}
 
 A precompile is a predefined smart contract with a special address that provides specific functionality executed natively by the Arbitrum client, rather than at the EVM bytecode level. Precompiles are used to introduce functions that would be computationally expensive if run in EVM bytecode, or to facilitate interactions between the parent and child chains. Arbitrum supports all Ethereum precompiles and also provides additional precompiles specific to Arbitrum chains, which can be called from smart contracts like regular Solidity functions[(1)](https://docs.arbitrum.io/build-decentralized-apps/precompiles/overview).

docs/partials/glossary/_prechecker-node.mdx

@@ -0,0 +1,9 @@
+---
+title: Prechecker Node
+key: prechecker-node
+titleforSort: Prechecker Node
+---
+
+An [Arbitrum full node](/intro/glossary#arbitrum-full-node) configured to pre-validate transactions before forwarding `eth_sendRawTransaction` to the [Sequencer](/intro/glossary#sequencer), insulating it from transactions that would fail.
+
+At a configurable strictness level, a prechecker verifies the transaction type, signature, intrinsic gas (including L1 calldata gas), fee cap, nonce, sender balance, and any `eth_sendRawTransactionConditional` storage conditions. When [compliance filtering](/launch-arbitrum-chain/configure-your-chain/advanced/compliance-filtering) is enabled, it also rejects transactions that touch restricted addresses.

static/glossary.json

@@ -379,6 +379,10 @@
     "title": "Portal",
     "text": "<p>A web application maintained by <a href=\"/intro/glossary#offchain-labs\">Offchain Labs</a> showcasing the Arbitrum ecosystem; visit it <a href=\"https://portal.arbitrum.io/\">here</a>.</p>\n"
   },
+  "prechecker-node": {
+    "title": "Prechecker Node",
+    "text": "<p>An <a href=\"/intro/glossary#arbitrum-full-node\">Arbitrum full node</a> configured to pre-validate transactions before forwarding <code>eth_sendRawTransaction</code> to the <a href=\"/intro/glossary#sequencer\">Sequencer</a>, insulating it from transactions that would fail.</p>\n<p>At a configurable strictness level, a prechecker verifies the transaction type, signature, intrinsic gas (including L1 calldata gas), fee cap, nonce, sender balance, and any <code>eth_sendRawTransactionConditional</code> storage conditions. When <a href=\"/launch-arbitrum-chain/configure-your-chain/advanced/compliance-filtering\">compliance filtering</a> is enabled, it also rejects transactions that touch restricted addresses.</p>\n"
+  },
   "precompile": {
     "title": "Precompile",
     "text": "<p>A precompile is a predefined smart contract with a special address that provides specific functionality executed natively by the Arbitrum client, rather than at the EVM bytecode level. Precompiles are used to introduce functions that would be computationally expensive if run in EVM bytecode, or to facilitate interactions between the parent and child chains. Arbitrum supports all Ethereum precompiles and also provides additional precompiles specific to Arbitrum chains, which can be called from smart contracts like regular Solidity functions<a href=\"https://docs.arbitrum.io/build-decentralized-apps/precompiles/overview\">(1)</a>.</p>\n"