The web.
Your browser trusts its connection and the code it receives. This page cannot independently attest its own delivery.
AN EXPERIMENT IN DIGITAL TRUST
An interactive laboratory for cryptography, identity, and decentralized networks.
Change a message. Generate a key.
See what happens.
Generate a key, change a message, and inspect the result. The constellation is a conceptual map; the experiments below perform the actual checks.
Try the hash experiment ↗02 / THE LABORATORY
Change a bit. Break a signature. Seal a message.
These are real operations, performed in your browser.
Use sample text, not valuable secrets.
A tiny change to the input can change roughly half the output bits. Not because the data is encrypted. Because a hash is a fingerprint.
The comparison toggles bit 0 of the first byte, not an entire character. Nothing is uploaded.
Waiting for Web Crypto…Flip a bit to compare.Create a temporary signing key, sign a message, then change the message. The public key can detect the change without knowing the private key.
The private key is non-extractable and held only in this page’s memory. This proves possession of that key, not a real-world identity.
No key. No claim.
Generate a session key to begin.Not signed.Verification uses your browser’s Web Crypto API. No wallet, account, server challenge, or blockchain transaction.
Encryption hides the message. Authentication detects modification. Flip a ciphertext bit and see why both matter.
A fresh key and 96-bit nonce are created for every encryption. This is a disposable demonstration, not secure storage. Reloading loses the key.
No message encrypted.Not generated.A location says where to ask. A content identifier says which bytes you want. Change those bytes and the address changes.
A real, locally calculated raw-block CID. No IPFS node is contacted. This content is not published, pinned, or made retrievable.
Waiting for Web Crypto…This is not a UnixFS directory CID. The website’s release CID must be computed from the complete release with a consistent importer configuration.
Explore a wallet connection without sending a transaction. You can request a plainly worded demonstration signature, but this build does not independently verify wallet signatures.
No balance lookup, chain switching, approvals, WalletConnect relay, or transaction requests. A visitor wallet does not establish ownership of Domojo. Clearing this page does not revoke permissions in your wallet.
Nothing requested.
Nothing to approve.
—No signature requested.03 / INSPECT DOMOJO
Explore the files behind this release and how they’re checked. Planned experiments will connect Domojo’s releases to IPFS, signed IPNS updates, and a read-only onion mirror.
Each check explains what it establishes—and what still depends on trust.
Your browser trusts its connection and the code it receives. This page cannot independently attest its own delivery.
One immutable address for one release. Content still needs someone to retain and provide it. An address is not a backup.
A key signs a changing pointer to content. The name can stay while releases change. Record freshness and availability still matter.
A different route to the same experiment. A v3 onion address authenticates a service key—not a person, or a connection to a wallet.
INSPECT THIS RELEASE
Compare fresh downloads against the release’s SHA-256 manifest. A match demonstrates consistency, not an independently trusted origin.
NOT BOUND TO THIS RELEASEVerification has not been run.
The checker and manifest arrive together. This check cannot prove the host is uncompromised or attest the code already running. An externally trusted CID or signing key is a separate trust anchor.
ABOUT THIS EXPERIMENT
Domojo is an independent, read-only laboratory. The Hash, Sign, Seal, and Address experiments process your input locally in this browser. Wallet interactions are optional and have their own disclosures.
04 / THE UNEXPLORED EDGES
Build the evidence first. Add a chain only when it answers a question the other layers cannot.