RPC settings
Add a custom RPC endpoint and view router stats. Custom endpoints are session-only and never persisted.
Add custom RPC
Note for deployed site users: the strict Content-Security-Policy
only allows requests to the default providers. A custom URL will be
blocked by your browser unless you run ClaimApp locally
or fork the repo with your URL in index.html's CSP meta tag.
Router stats
1. Load your wallet
Enter a public address to scan read-only, or a private key to also claim. Keys stay in memory only.
⚠ Only paste a private key on a device you trust. Double-check the URL in your address bar. This app never transmits keys — verify by checking the Network tab in devtools.
2. Scan for claimables
Each source runs independently. Currently enabled: Clanker. More sources coming as modules are added.
3. Your claimables
Security model
- No backend. This site is 100% static HTML/JS/CSS served from GitHub Pages. There is no server to compromise.
- Keys stay local. Private keys are held in a JavaScript closure, never written to localStorage, sessionStorage, cookies, or the DOM.
- No telemetry. Zero analytics, zero tracking pixels, zero third-party scripts.
- No external fetches. A strict Content-Security-Policy blocks every outbound request except Base RPC endpoints you approve.
- Auditable. ~500 lines of handwritten JS. Read it all in an afternoon: source on GitHub.
- Wiped on exit. Closing or refreshing the tab clears the wallet. No "remember me" checkbox exists.
- Run local if you prefer. Clone the repo and open
index.htmldirectly — no install needed.
Donations keep development going:
0x7a3E312Ec6e20a9F62fE2405938EB9060312E334