Polygon PoS
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 Polygon PoS | 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. |
Polygon PoS is EVM, chain id 137.
Its engine here is polygon.
What Polygon PoS 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 Polygon PoS 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 Polygon PoS
This deployment follows Polygon PoS for payments and can watch one destination for one asset.
- The asset this deployment can identify here is USDT (Tether USD), named as
0xc2132d05d31c914a87c6611c10748aeb04b58e8f, 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":"polygon",
"address":"0x742d35Cc6634C0532925a3b844Bc454e4438f44e"}'Omit asset for the native coin; name a contract address to read a token. Your key must be scoped to polygon and to a product that carries balance.get.
Known limitations on Polygon PoS
- 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.