ProtocolValueDeveloper integration
Protocol-defined values are not market prices. Values from contracts can be independently checked. Static JSON snapshots never constitute live wallet quotations or proof of redemption.
Lightweight JSON resources
| Resource | Use |
|---|---|
| Asset directory | Minimal metadata; not a verified LIVE feed. |
| POU historical reference | Block-pinned historical observation with provenance. |
| Canonical POU evidence | Formula, contracts, snapshot and validation information. |
Read the POU reference directly
Network: BNB Smart Chain (chain ID 56). Token: 0x4C42587b1DA6a121CBa48053C19A534B6C091198. Protocol: 0xe7603361925c5483C22A02D5B3DeADD0ab467f5A.
Method: referencePriceIncludingQuarantineWad() · calldata 0xe7926f76 · output scale: 18 decimals · quote: protocol-native USDT reference.
{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0xe7603361925c5483C22A02D5B3DeADD0ab467f5A","data":"0xe7926f76"},"latest"]}Execute against a trusted BNB Chain JSON-RPC endpoint. Pin reads to a specific block and verify the block hash, code identity, math, and applicable operational controls before declaring any observation verified. An eth_call response alone is insufficient for full technical admission.
Data model principles
Represent large integers and decimal amounts as strings; identify token, chain, quote unit, function, calldata, block number/hash, observation time, and proof provenance. Keep valuation type, redeemability, and execution evidence separate. Never combine values with different units without explicitly verified conversion.
Integration status
No CoinGecko, MetaMask or Rabby native-price acceptance is implied. Market data, when available, must be distinguished from protocol-native reference values. This version continues publishing the existing USDT-based catalog; multi-unit reader support has not been deployed.