Ethereum
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 Ethereum | 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 | Not here | Needs a Data plane this deployment does not run. |
Ethereum is EVM, chain id 1.
Its engine here is ethereum.
What Ethereum 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 chain has a protocol condition for finality: a block either meets it or does not, and waiting longer does not make a block that has met it any more final. Depth is not meaningful here.
- The strongest thing Ethereum says is
FINALIZED. - Its intermediate condition is
SAFE. - Depth is not what settles a block here, so this deployment does not count to one.
Paying on Ethereum
Not on this deployment.
Ethereum is followed properly by a Data plane that ingests and records the chain, rather than by the light path that reads one destination at a time. No Data plane is attached here, so a payment watch on Ethereum is refused when you open it and says so, rather than being accepted and followed by nothing.
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":"ethereum",
"address":"0x742d35Cc6634C0532925a3b844Bc454e4438f44e"}'Omit asset for the native coin; name a contract address to read a token. Your key must be scoped to ethereum and to a product that carries balance.get.
Known limitations on Ethereum
- 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.