Contact
Bug reports and data questions
The fastest route to the people who run this explorer is a GitHub issue on the public repository. Use it for wrong or missing data, a page that fails to render, an API response that disagrees with the chain, or a request for a new RPC method on the console allowlist.
When a figure looks wrong, include the URL, the time (UTC), and the `source` and `meta` fields from the matching JSON API response (for example GET /api/overview or GET /api/blocks). Those fields name which upstream served the page, which is usually the whole diagnosis.
Security disclosures
This site is a read-only explorer: it holds no user accounts, no funds and no private keys for visitors. The Studio page can fund and deploy from a server-side testnet wallet of its own; a finding that lets a visitor misuse that wallet, reach a host outside the RPC allowlist through /api/rpc, or bypass the request limits is a security issue. Please report it privately through a GitHub security advisory on the repository rather than a public issue.
Direct contact
E-mail: naman@entropytoorder.xyz. Replies come from the The Singularity engineering team; issues on GitHub are answered faster. Infrastructure status for the RPC and the indexer is reflected live in the explorer's own status badge and in the `meta` of every API response.
Post: The Singularity, 3230 Market St, Philadelphia, PA 19104, US.