Pluto workspace
Loading configuration…
Researcher workspace
Encrypt your report, review costs and share a verified notice.
1. Encrypt your report
Create a fresh author identity. Keep the private recovery file; Pluto cannot restore it.
2. Store ciphertext & seal the key
Two independent ciphertext providers
Browser uploads contain ciphertext only. Each provider must allow CORS and retain your file through public disclosure.
Refreshing costs preserves the saved seal and window. An active funding request must be withdrawn before choosing self-funding.
3. Review before signing
Live cost estimates are required before signing.
Nodes pause above the selected basefee ceiling. Committee operators can read the sealed key while pending; public shares can expose it before hook acceptance.
Download the latest private recovery from the Current report panel before confirming below.
Once posted, this deadline cannot be cancelled, extended or amended.
Continue a saved report
Restore a private file or a report saved in this browser. Inspect existing attempts before sending anything again.
Restore private recovery
These files never leave this browser. Earlier browser and CLI formats require their original workflow.
No attempt recorded.
Inspect receipts before reviewing a missing binding.
Binding completes the existing immutable deadline and never posts another report.
No recovery restored.
Funding request status & recovery
Save updated recovery after every step. Retry upload uses the exact signed request. Withdrawal applies only before submission.
Check request status to inspect a funded post.
Only the existing trigger will be bound. No new report is registered or posted, and its deadline cannot change.
Browse any section. Encrypt your report before storing and sealing.
Protocol customer
Manage private intake
Staff access is scoped to your enrolled protocol. Account and funding changes cannot alter a posted disclosure.
Sign in to access private notices and funding.
Signed private notices
Verify each report’s chain-derived state. Before reveal, a privately supplied key can match the public key commitment without proving that the seal contains that same key.
Select your domain and sign in to load its private inbox.
Enroll a protocol domain
Signing in does not prove domain ownership. Add the requested DNS TXT record to enroll your protocol.
No proof requested.
Security contacts
No contact records loaded.
Rotation requires a fresh email code. Existing encrypted attachments remain encrypted to their original key.
Protocol funding & approvals
Transfer ETH or the live C0-resolved NIL token from your authenticated staff wallet to the displayed dedicated payer, then submit its finalized transaction hash. Limits cannot create funds.
No funding records loaded.
Credit a deposit & configure limits
No requests loaded.
Select a pending request to review its author, window and exact spending caps.
Live spending is disabled pending release acceptance.
Account retention & disablement
Private notice/access metadata expires according to the configured retention policy. Contact/account erasure and backup expiry are not yet available. Disabling intake cannot cancel, extend or suppress a posted trigger.
Independent verification
Check a public record
Read the author’s signed notice, verify chain acceptance and commitments, then decrypt locally after disclosure.
No record inspected.
Ciphertext URLs come from the researcher. The registry holds commitments and timing, not report files. A hook acknowledgement alone is not proof of accepted disclosure.