Command overview
Live infrastructure and rescue activity at a glance
Rescue infrastructure is ready.
The gateway is serving allowlisted extension builds across 0 configured networks. Private wallet material never enters this server.

Recent rescue submissions
Rescue transaction ledger
Submitted transactions are tracked by hash. Open a record to fetch its latest public receipt and rescued asset events.
| Submitted | Network | Transaction | Outcome | Rescued value | Source |
|---|
New extension submissions will appear automatically. You can also track a historical hash above.
Gateway threat monitor
Authorized extension traffic, outside API attempts, login attacks and rate-limit events appear here without storing wallet secrets or signed payloads.
| Time | Risk | IP / location | Identity | Request | Result |
|---|
The selected filter has no recorded events.
Blocked source IPs
Approved extension builds
Only exact Chrome extension IDs listed here can use the RPC gateway.
Website access
Origins allowed to call POST /rpc/<chain> (the 0xjack.dev dashboard). One origin per line.
Exact origins only (https://domain — no path). These get CORS access to the RPC gateway. Empty = website blocked.
RPC and contract deployments
Configure only networks where the rescue contract has verified deployed bytecode.
| Chain ID | Stored RPC | Replace RPC URL | Status |
|---|
Security center
Review active controls and rotate your admin password without touching encrypted RPC configuration.
Tamper-evident audit log
Administrative logins, configuration changes, password changes and tracked transactions are hash chained.
| Time | Action | Outcome | Source IP | Details | Integrity |
|---|