Loops HouseKeyhole

NEAR HACKATHON
Links
Team
1 member- OLOwner
Oluwatobiloba Lawal
Overview
Sharing a private file usually means giving up control of it. Once an email attachment or a shared drive link is out, the recipient can keep a copy, the access never expires, and nobody can prove who opened it or when. Taking it back isn’t possible.
Keyhole fixes that by keeping the file in a safe you own. The file is encrypted on your device, so what’s stored is only ciphertext. When you want someone to see it, you create a link that opens specific files for a set time. They don’t need an account. They see the pages with their name watermarked on them and a countdown showing how long they have. If you change your mind, you end access and the link stops working right away. If you sell the safe, you can hand it over with escrow, and every old link dies. Two extras build on this. Ask lets the recipient question the documents, with answers from private AI running on attested hardware and citations back to your pages. Claims lets you share a single signed fact in place of the whole document.
NEAR is what makes the control trustworthy rather than just promised. Each safe is an NFT that you hold, and direct transfer is refused, so ownership only changes through the handover flow. The contract keyhole-06728d.testnet records who has access, to which files, and until when. Before any key is released, the visit is written to a receipt chain on NEAR. That log can’t be quietly edited, and any tampering shows up as Broken. The release service reads NEAR itself and sends its half of the key only after the visit is recorded, so nothing opens without a record. The contract has no access keys, so no one can upgrade it, and the /proof page checks that live.