WHAT THIS DEMO IS
CED Shield proves a PDF or a session existed. Midnight and Lace see only the SHA-256, the timestamp, and the wallet. The content stays in CED.
Solid Wave 2 path: Lace attests the commitment (signData). No fake txid. Circuit recordSeal in CedShield.compact is the contract; an on-chain send waits for deploy + ZK keys. Jarvis, Retell, and Meta never enter this path. CED_SHIELD_ENABLED stays off in the product.
HOW A JUDGE VERIFIES
- Connect Lace Midnight Preview on preprod.
- Hash the sample in the browser (SHA-256 never leaves this page).
- Sign. If Lace stubs
signData, copy the JSON: live wallet + hash,on_chain_txid: null.
GitHub: CedShield.compact · recordSeal · CED-WEB repo
1. CONNECT LACE
window.midnight — DApp connector. It does not enter the voice HUD.
Extension: Lace Midnight Preview. Network: preprod.
2. HASH SAMPLE
SHA-256 in the browser. Compact expects Bytes<32> + kind.
3. SIGN IN LACE
We request signData from Lace. Today the extension returns that the method is not implemented. The seal is still wallet + hash, with no invented signature.
After connect and hash, press here. If Lace does not sign, the JSON below still counts.
SEAL (HASH + SIGNATURE, NO CONTENT)
Connect Lace, hash, and sign to see the seal a judge can verify.
ON-CHAIN VS OFF-CHAIN
GOES TO MIDNIGHT / LACE
- content_sha256
- sealed_at
- wallet + unshielded signature
- kind (pdf | session)
STAYS IN CED
- Chat, voice, PDFs
- Audio and transcript
- Meta / Tavily / Gemini
Pilot module. Not in Jarvis. English for AKINDO judges. Wave 2 deck · Back to CED