Reference

Evidence

Every contract and every settled transaction, each naming the file its value comes from - so a reader who does not trust this page can check it against the chain and against the repository.

Nothing on this page is typed by hand into a paragraph. Each row is imported from src/lib/evidence.ts, which in turn imports the addresses from src/utils/constants.ts - the same constants the running application uses. A value that changes in the app changes here.

Every hash and address below is verified against a live RPC by node scripts/verify-evidence.mjs, which fails on a transaction that did not succeed or an address with no contract at it.

Transactions

Transaction register

11 entries · 5 mainnet · 6 sepolia
05

Private send and unshield on mainnet

mainnet

One apply_actions proved by the STRK20 prover through Starkscan: ViewingKeySet, Deposit of 3 STRK, two EncNoteCreated (1 STRK sent privately to the owner account, 1 STRK kept shielded) and a Withdrawal of 1 STRK back to public. 5 events from the pool.

Hash
0x6342cd9a1c1f4f9cd85f6561b3d78ed196c0ee3a332b8cc1feacd89e739360eVoyager
Status
SUCCEEDED
Block
15,768,124
Source
src/lib/evidence.ts

Contracts

Rows marked STARKWARE are not ours: the privacy pool and the shadow anonymizer are StarkWare's deployments, used rather than redeployed. The distinction matters when you are deciding whom to trust - that cryptography is audited, and the helpers around it are not.

Contract register

11 entries · 1 mainnet · 10 sepolia

Retired

Listed rather than deleted. A deployment that was live and then abandoned is exactly what a reader deserves to find named, and this one's failure is the most instructive bug in the repository - see the vault.

Retired register

1 entry

What this does not prove

The source repository is github.com/kamalbuilds/neobank, and the contract work is at starknet-shadow-account-starter.