About the Singularity Block Explorer
What this is
Singularity Block Explorer is the public block explorer for the Singularity testnet, chain id 17743 (0x454f). The testnet runs the ETO virtual machine, a multi-VM runtime in which EVM, SVM, WASM, Move, ZK programs execute against one atomic ledger. The explorer shows that single state through each machine's lens: the same block height read by eth_blockNumber, getSlot and eto_getStats, side by side.
It is also the chain data gateway for the other Singularity properties. The raw RPC node sends a malformed CORS response to browsers, so browser-side reads route through this site's server-side JSON API, which is CORS-open and read-only.
Who runs it
The explorer is built and operated by The Singularity, the team behind the ETO protocol and the Singularity testnet. The source is public on GitHub under the etofdn organisation, and the deployed site is built from that repository.
The honesty contract
Nothing on the trust surface is fabricated. Views ship zeroed and fill only from real sources, and every payload names the source that served it: the indexer, a last-known-good cache, or the chain read directly from the node. When the indexer is dead or has fallen behind the chain head, the API serves the tip chain-direct and says so, and the status badge reads "Indexer stale" instead of "Live".
Liveness is judged from the age of the newest block's timestamp, never from "the request returned 200": a halted chain answers every call instantly. Empty surfaces render designed empty states that say why they are empty, never placeholder rows.
The network
Native token: SING, held as 9-decimal lamports on the native ledger and wei-scaled (18 decimals) on the EVM surface. Public JSON-RPC endpoint: https://rpc.entropytoorder.xyz. Public indexer: https://indexer.entropytoorder.xyz. Both are testnet infrastructure and may pause or reset; the explorer reports such states rather than hiding them.