01 / TRANSPORTOBSERVED
The web.
Your browser trusts its connection and the code it receives. This page cannot independently attest its own delivery.
Current document origin
AN EXPERIMENT IN DIGITAL TRUST
How do you
know this
is me?
An address is a claim.
A signature is a proof.
Explore the space between them.
No account. No uploads. No token.
CRYPTOGRAPHIC CONSTELLATIONFIELD / 001
DRAG TO ROTATE · SELECT A NODE
THE CENTRAL QUESTION
One identity. Different kinds of evidence.
This field is a conceptual map, not a live network. Local experiments light up the relationships they actually demonstrate.
STATIC APPLICATIONLOCAL CRYPTOGRAPHY / EXPLICIT TRUST BOUNDARIESEXPERIMENTAL v0.1.0
02 / THE LABORATORY
Less belief.
More evidence.
Change a bit. Break a signature. Seal a message.
These are real operations, performed in your browser.
Use sample text, not valuable secrets.
SHA-256 / THE AVALANCHE EFFECT
One bit in.
A different world out.
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.
256 BITS / OUTPUT DIFFERENCEBASELINE
0/ 256 bits changed0.0%
ORIGINAL DIGEST
Waiting for Web Crypto…COMPARISON DIGEST
Flip a bit to compare. Changed output bit Measured, not simulated.
ECDSA P-256 / PROOF OF POSSESSION
A secret you
don’t have to share.
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.
LOCAL SIGNATURE CHECKP-256 / SHA-256
No key. No claim.
PUBLIC KEY FINGERPRINT / SHA-256
Generate a session key to begin.SIGNATURE / IEEE P1363 FORMAT
Not signed.Verification uses your browser’s Web Crypto API. No wallet, account, server challenge, or blockchain transaction.
AES-256-GCM / AUTHENTICATED ENCRYPTION
Unreadable.
Until you have the key.
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.
CIPHERTEXT + 128-BIT TAGAES-GCM
CIPHERTEXT / HEX
No message encrypted.NONCE / HEX
Not generated.Waiting for an experiment.
CIDv1 / CONTENT ADDRESSING
The address
is in the content.
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.
EXACT CONTENT / EXACT ADDRESSNOT PUBLISHED
CIDv1 / BASE32
Waiting for Web Crypto…- Version
- 1
- Codec
- raw · 0x55
- Multihash
- sha2-256 · 0x12
- Digest length
- 32 bytes · 0x20
This is not a UnixFS directory CID. The website’s release CID must be computed from the complete release with a consistent importer configuration.
OPTIONAL / EXPLICIT CONSENT
An address.
Not your identity.
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.
Connecting shares your selected address with this page and its scripts. Your wallet may contact its own providers. Use an empty experimental wallet; never enter a seed phrase here.
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.
WALLET SESSIONNOT CONNECTED
Nothing requested.
Nothing to approve.
ADDRESS / REPORTED BY YOUR WALLET
—SIGNATURE RECEIPT / NOT INDEPENDENTLY VERIFIED
No signature requested. THIS APPLICATION SENDS NO EXPERIMENT INPUTS TO A SERVERYOUR BROWSER REMAINS PART OF THE TRUST MODEL
03 / THE SPECIMEN IS THE SITE
Same object.
Different trust.
Domojo is the thing being examined.
Not a hosting platform. Not a gateway for strangers.
The unfinished parts are labeled unfinished.
02 / CONTENTNOT PUBLISHED
IPFS.
One immutable address for one release. Content still needs someone to retain and provide it. An address is not a backup.
STATIC PAYLOAD READY · NO CID CLAIMED
03 / CONTINUITYNOT CONFIGURED
IPNS.
A key signs a changing pointer to content. The name can stay while releases change. Record freshness and availability still matter.
AWAITING AN OWNER-CONTROLLED KEY
04 / SERVICE IDENTITYNOT CONFIGURED
Onion.
A different route to the same experiment. A v3 onion address authenticates a service key—not a person, or a connection to a wallet.
READ-ONLY MIRROR · OPERATOR SETUP NEEDED
INSPECT THIS RELEASE
Check the bytes.
Question the checker.
Compare fresh downloads against the release’s SHA-256 manifest. A match demonstrates consistency, not an independently trusted origin.
RELEASE / v0.1.0MANIFEST ↗
OWNER WALLET
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.
BY DESIGN
No public uploads. No arbitrary CID retrieval. No pinning API. No user namespaces. No fund custody. No claim that a glowing graph is a security audit.
04 / THE UNEXPLORED EDGES
Trust is not a switch.
It’s a set of questions.
Signed release bindings PLANNEDBrowser-verified IPNS PLANNEDZero-knowledge proofs RESEARCHPost-quantum signatures RESEARCHOn-chain attestations RESEARCH
Build the evidence first. Add a chain only when it answers a question the other layers cannot.