“A person needs tamper-evident, dated proof that a file existed without disclosing it; DEMI Capsule Card v2.6 solves this by hashing the file locally via SHA-256 in the browser, collecting an A$9 card payment through Lemon Squeezy, and storing the record with an Ethereum anchor and UPL code via DEMI Worker V5.8.7.”
PropositionsT1: Client-side SHA-256 fingerprinting — file is hashed in the user's browser and never uploaded | T2: Card payment processing — A$9 fee collected via Lemon Squeezy before registration proceeds | T3: DEMI Worker V5.8.7 — stores the record and returns a UPL code | T4: Ethereum anchoring — record is anchored on Ethereum, verifiable on Etherscan | T5: Blue result screen — loaded from the Worker, shared across all DEMI interfaces, displays UPL code, anchor link, owner key, certificate, Saved package, and AI package | T6: Optional Parent code — checked against the Registry if supplied | T7: Listed or sealed record modes — supported at registration | T8: Privacy output rules — no email or owner key appears in public output | T9: Fallback screen — displayed if the shared result script cannot load
ConstraintsPlatform: ramsmile.com/demicapsule, maintained by UplitAU Pty Ltd | Card payment: A$9 via Lemon Squeezy (required before record creation) | Worker version: DEMI Worker V5.8.7 | Hashing standard: SHA-256, executed client-side only | Blockchain: Ethereum; anchor must be visible on Etherscan | Privacy: email and owner key must not appear in public output | Parent code: optional field, validated against DEMI Registry if provided | Record visibility: listed or sealed modes only | Result screen: must be loaded from Worker and shared by every DEMI interface; fallback required if script load fails | Document version: v2.6
MechanismsT1: Verify no network file-upload request is made during hashing — inspect browser network tab; confirm hash matches record post-registration | T2: Confirm payment gate blocks record creation until Lemon Squeezy confirms A$9 transaction | T3: After payment, query Worker endpoint and confirm UPL code is returned and record is stored | T4: Take the returned anchor link and confirm the transaction appears on Etherscan with matching data | T5: Load blue screen from Worker URL; confirm all six elements render (UPL code, anchor link, owner key, certificate, Saved package, AI package); test across multiple DEMI interfaces for shared delivery | T6: Submit a valid Parent code and confirm Registry lookup succeeds; submit invalid code and confirm rejection | T7: Register once as listed, once as sealed; confirm visibility behaviour differs correctly | T8: Audit public output and network responses for absence of email and owner key strings | T9: Block the shared script and confirm fallback screen renders without error
BoundariesOut of scope: file content transmission or server-side file storage; payment provider internals beyond Lemon Squeezy confirmation; other DEMI interface implementations beyond the card page | Planned but not yet built or confirmed: live proof of the purple screen (the pre-payment or in-payment screen) on a first real card registration is explicitly unresolved | OPEN: live proof of the purple screen on the first real card registration has not yet been demonstrated.