Release Passport

Problem: when an open-source project changes hands, nobody installing it can tell, and nobody has anything at stake (event-stream, 2018). Product: Release Passport makes a project's release authority a NEP-171 NFT on NEAR that is also a real account, .rp.relpass-emilh.testnet, created by the contract with no access keys and running one immutable wallet deployed once as a global contract by hash. The passport lists every release with each file's sha256; anyone checks a download in the browser or with a zero-dependency CLI, which verifies itself. A tampering report confirmed by the passport's fixed arbiter marks the release COMPROMISED for everyone and pays the reporter from the bond. Transferring the NFT hands over release rights, bond and earnings, and the seller keeps nothing: the wallet obeys only the NFT contract, every action checks the current holder, a transfer cancels pending withdrawals, money in flight returns to the token, approvals are off and nft_transfer_call locks the passport until it settles. How NEAR fits: NFT-owned sub-accounts with no keys, global contracts by hash, NEP-171 and NEP-297. Live on testnet with one passport's full history (release, sponsorship, confirmed report, bounty paid, sale, the buyer's release and withdrawal); 29 unit tests; the README has do-X-see-Y steps. Same author's other project: Patch Fund (track social).