> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kek.pro/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Treat Solana and Robinhood Chain as separate protocol paths.
> Write for people using the KEK.PRO app.
> Treat displayed fees, limits, and availability as environment-specific unless labeled as protocol constants.

# Network and deployments

> Bind Robinhood Chain identity to environment-specific KEK.PRO manifests, ABIs, RPCs, explorers, and finality policy.

KEK.PRO separates network support from deployment evidence. A chain profile
can exist before KEK.PRO contracts are deployed there.

<figure className="kek-figure kek-figure--warning" data-mark="CHAIN" aria-labelledby="network-evidence-title">
  <div className="kek-figure__header">
    <span id="network-evidence-title">Network identity / deployment evidence</span>
    <small>Profile ≠ verified release</small>
  </div>

  <div className="kek-figure__body">
    <div className="kek-readout kek-readout--two">
      <div><span>Robinhood Chain testnet</span><strong>46630</strong><small>Historical KEK.PRO development manifest is checked in.</small></div>
      <div><span>Robinhood Chain mainnet</span><strong>4663</strong><small>Network profile exists; no checked-in KEK.PRO deployment manifest.</small></div>
    </div>
  </div>

  <figcaption className="kek-figure__caption"><strong>Gate every write.</strong> Match chain, addresses, runtime hashes, ABIs, source revision, configuration, and finality policy.</figcaption>
</figure>

## Network identity

| Environment             | Chain ID | Native asset | Public RPC                                | Explorer                                                         |
| ----------------------- | -------: | ------------ | ----------------------------------------- | ---------------------------------------------------------------- |
| Robinhood Chain mainnet |   `4663` | ETH          | `https://rpc.mainnet.chain.robinhood.com` | [Blockscout](https://robinhoodchain.blockscout.com)              |
| Robinhood Chain testnet |  `46630` | ETH          | `https://rpc.testnet.chain.robinhood.com` | [Testnet explorer](https://explorer.testnet.chain.robinhood.com) |

Treat public RPCs as shared infrastructure. They may be rate limited. Confirm
the reported chain ID before asking the wallet to sign.

## Available KEK.PRO evidence

<div className="status-line status-line--testnet">
  Robinhood Chain testnet · chain ID 46630 · historical development manifest
</div>

The checked-in testnet manifest records deployment block `93747023`, contract
addresses, runtime code hashes, ABI hashes, and source revision
`1a41aa8d096a4dd6ac298835483850ece8dce02b`.

That manifest proves only that a development deployment was recorded. It
predates later source hardening and does not prove that the current source or
current `abi/v2` files are deployed.

<div className="status-line status-line--planned">
  Robinhood Chain mainnet · chain ID 4663 · network profile only
</div>

There is no checked-in KEK.PRO deployment manifest for mainnet. The repository
does contain pinned fork checks for Robinhood Chain's V3 dependencies. Those
checks do not prove that KEK.PRO contracts are deployed.

## Release identity

Treat these fields as one versioned unit:

```text theme={"theme":{"light":"github-light","dark":"github-dark"}}
chain ID
deployment block
contract addresses + runtime hashes
source revision
ABI files + ABI hashes
protocol version
launch and DEX configuration IDs
finality policy
```

Matching `protocolVersion` strings are not enough when ABI hashes differ.

## Preflight every session

<Steps>
  <Step title="Resolve the chain">
    Require the wallet and every RPC to report the intended chain ID.
  </Step>

  <Step title="Select one release">
    Load an approved deployment manifest and its exact ABI manifest. Do not
    combine addresses and ABIs from different revisions.
  </Step>

  <Step title="Verify code and links">
    Compare runtime hashes. Confirm the factory, locker, deployer, V3
    dependencies, Permit2, and block provider.
  </Step>

  <Step title="Read live policy">
    Fetch launch and DEX configs, launch enablement, fee allocation,
    recipients, compounding policy, and optional feature readiness.
  </Step>

  <Step title="Apply finality">
    Treat sequencer-confirmed activity as provisional until the selected
    staged-finality policy promotes it.
  </Step>
</Steps>

Robinhood Chain is an Arbitrum-style L2. Before relying on a log, confirm that
it remains canonical under the selected finality policy.