ACTUAL DEVICE EVIDENCE · PRIVATE BETA v0.5

Test legacy encrypted-wallet compatibility

This opt-in page collects public chain observations and your report of the real wallet workflow, explicit transfer review and safe pending state. No extension, desktop wallet or local server is required on the visitor's device.

This collector covers legacy encrypted-file wallets only. The default 12-word wallet uses the Wallet page; this collector does not qualify its mnemonic operations. Never enter recovery words here.

Evidence limits and privacy

Run the actual application in a second tab on this same approved HTTPS origin. This collector never reads wallet storage, wallet files, passwords or decrypted backups and makes no wallet or ledger signing request. The capability probe signs only a public test challenge with its own temporary key. It sends only bounded read-only API requests. The downloaded report contains public transaction/account identifiers and selected device details. Keep it private until reviewed.

A browser user-agent is an untrusted hint, not proof of Windows, ChromeOS or a physical phone. Device and workflow entries below are owner-reported, pending review. This page cannot issue a verified native/guest-OS pass; a reviewer must inspect genuine OS/browser evidence. A Linux container, viewport or spoofed user-agent does not qualify another platform.

Open the actual demo wallet ↗ Open persisted Explorer ↗

Capability probe has not run.

1. Actual device and independent source identity

Read OS and browser versions from the device's Settings/About screens. Record only the product/version; omit account names, e-mail, serial numbers, file paths, hostnames and screenshots of personal settings. For ChromeOS use the built-in Chrome browser, without Crostini. For iOS use actual Safari; desktop WebKit is supplementary only.

Real operating system OS product version/build only Actual browser Browser version only Environment provenance I checked the real OS/browser About screens; these are not inferred from a user-agent or simulated viewport. Independently supplied exact application commit Independently supplied source digest, if recorded in the handoff Independently supplied exact genesis hash

2. Perform the complete wallet journey

Check each item only after completing it in the actual application. Do not paste passwords or backup contents here. Keep the backup encrypted and its password separately. The operator cannot recover a lost wallet. Browser storage may be cleared or evicted; a download alone is not proof of recovery.

For cross-browser recovery, use the same downloaded encrypted file and password in another supported browser. Compare the exact public address and submit a new signed transfer from the recovered identity. On ChromeOS use Files; on iOS use Files; on Android use its normal file picker. A physical device is required to qualify mobile file/touch behavior.

Cross-browser backup origin (product only, optional)Original/recovered public demo addressPublic recipient demo addressReal 25 tPOUT transfer ID, signed by the recovered wallet

3. Review and download structured evidence

The report distinguishes executed native capability probes, current server-reported public records and your manual attestations. The server's claimed commit and genesis are checked against your independently supplied pins; neither is independently authenticated merely by fetching it. Public records are corroboration, not proof of which browser held the signing key.

Observed outcomeExact blocker category, if anyI entered only demo public identifiers and product versions. I will review any separate screenshots for personal information before private submission.

No report generated. Missing platforms remain release blockers.