Contact Us
Contact routes
- General enquiries:
Corrections, data questions, anything that does not fit the rows below.
- Security:
Vulnerability reports only. Read the bug bounty scope first — it says what is in scope and what to include.
- Advertising:
Placements, sponsorship and rates. See Advertise.
- Privacy and data protection:
Requests about server logs. Note the limit in the privacy policy: on-chain data cannot be erased by anyone, including us.
There is no contact form on this page, on purpose
Arcscan has no inbox service behind the website. A form would accept your message and discard it, and you would have no way to tell — an address you can see is the honest shape. All four routes above are the same mailbox today, which is why they read alike; it is a real one, and naming the row you are writing under in your subject line is what sorts them.
Elsewhere
Arcscan's account on X is @arcscanio. It is the only social account this site publishes, so an account posting under this name anywhere else is not connected to Arcscan.
It is a place to find Arcscan, not a route to reach it. Correspondence, security reports, advertising and privacy enquiries go to the addresses above — those are the routes this site publishes.
Things we genuinely cannot do
Arcscan reads a public blockchain. It does not operate it, custody anything on it, or have any privileged access to it. That rules out a category of requests we would otherwise be glad to help with:
- Reverse or cancel a transaction. Arc has deterministic finality: a committed transaction is permanent, and no explorer, validator or issuer can undo it.
- Recover funds sent to the wrong address, or lost keys. We have no relationship with any address and no ability to move anything.
- Remove an address, transaction or contract from the chain. We can correct how Arcscan displays something; the underlying record is on a public ledger replicated by everyone running a node.
- Act on a support request that reached you through a chat group. Arcscan runs no chat, no DM support and no wallet-connect flow. Anyone claiming otherwise while asking for a seed phrase is stealing from you.
Reporting something that looks wrong on this site
Include the URL and, where it applies, the transaction hash, block height or address you were looking at. Those three identifiers make a report reproducible; a screenshot usually does not, because the same page can be served from the node or from an index that is behind, and network status is what distinguishes the two.