No. Proof generation and sensitive witness data stay in the client-side flow. Your private keys and transaction details never leave your browser.
No. You only need to provide the transaction hash and your claim parameters. No wallet connection required.
No. API key entry is optional advanced mode only. The default flow works without any API keys.
Yes. Local setup and baseline flow are designed for no-card operation using free-tier/public provider paths.
Only proof-related public claims and redacted receipt output. They cannot see the actual transaction amount, exact timestamp, sender address, receiver address, or transaction hash.
GhostReceipt uses Groth16 zk-SNARKs to prove statements about your transaction without revealing the underlying data. The proof is generated in your browser using Circom circuits and snarkjs.
Currently Bitcoin, Ethereum (native ETH + ERC-20 USDC), and Solana (native SOL).
Yes. Ethereum supports both native ETH and ERC-20 USDC claim modes through the same oracle fetch flow.
No. Each receipt includes an oracle signature over canonical blockchain data. The zero-knowledge proof cryptographically binds your claim to the oracle-signed transaction data.
GhostReceipt calls /api/oracle/* first. If that route is unavailable (network failure, 404/405, or 5xx), it can retry against an optional edge backup base configured by the operator. Normal 4xx responses (including rate limits) are returned directly and do not trigger backup retries.
It proves your claim satisfies the circuit against oracle-signed canonical transaction facts. It does not remove trust in the current single oracle operator and upstream data providers.
GhostReceipt shows validation strength as passive metadata, with no extra clicks required:
consensus_verified: primary and peer providers agreed before signing.single_source_fallback: peer was unavailable, and best-effort mode allowed signing with the primary source.single_source_only: consensus checks were off or no peer path was configured.Bitcoin valueAtomic currently maps to total transaction output value (sum(vout) / output_total), not recipient-specific net received value. For multi-output transactions, treat it as tx-level evidence.
Typically under 60 seconds on modern devices. The process includes fetching transaction data, validating constraints, and generating the zero-knowledge proof in your browser.
Yes. GhostReceipt is designed for freelancers, merchants, accounting teams, and DAO contributors who need verifiable payment evidence without exposing sensitive financial data.