Base
Everything on this page is generated from the running deployment. If a capability stops being served, the row for it changes rather than staying true-looking.
| What | Method | On Base | Notes |
|---|---|---|---|
| Read a balance | balance.get | Available | Native and token balances, by contract address. |
| Read network state | network.status | Available | The engine's lifecycle, bootstrap, continuity and observation axes. |
| Watch for a payment | payments/watch | Available | Followed by the light acquisition path, one bounded read per pass. |
Base is EVM, chain id 8453.
Its engine here is base.
What Base means by settled
Reported in this chain’s own vocabulary. It is never translated into a shared “confirmed”, because the translation is where the money goes missing.
This is a rollup. Its sequencer confirms a block immediately, and that confirmation is a promise by the sequencer rather than by the protocol. The block becomes irreversible when the batch containing it is finalised on Ethereum, which is where the guarantee actually lives.
- The strongest thing Base says is
L1_FINALIZED. - Its intermediate condition is
L2_SAFE. - Depth is not what settles a block here, so this deployment does not count to one.
Paying on Base
This deployment follows Base for payments and can watch one destination for one asset.
- The asset this deployment can identify here is USDC (USD Coin), named as
0x833589fcd6edb6e08f4c7c32d4f71b54bda02913, with 6 decimals read from the contract rather than assumed. - Amounts are compared as an integer count of the smallest unit. A float would round, and a rounded payment is a dispute.
- Detection and settlement are separate standings. You choose which one your checkout ships on.
The address is the whole destination on this network; no routing value is needed.
A first request
curl https://api.stonereason.com/v1/rpc \
-H 'authorization: Bearer $XRPC_KEY' \
-H 'content-type: application/json' \
-d '{"method":"balance.get","network":"base",
"address":"0x742d35Cc6634C0532925a3b844Bc454e4438f44e"}'Omit asset for the native coin; name a contract address to read a token. Your key must be scoped to base and to a product that carries balance.get.
Known limitations on Base
- Free Beta: nothing is priced and no availability is promised.
- Answers here rest on something asserted from outside the protocol -- a checkpoint published by somebody, or a header that carries no proof of its own canonicity. However much cryptography verifies beneath it, the claim is capped by that assertion, and this is said in every response rather than assumed away.
- Source independence is unestablished here: this deployment cannot show that two sources it might ask are operated separately, so agreement between them is treated as availability rather than as evidence.
- No transaction history, no archive and no broadcast on the Beta surface.