Loops HouseRSVPay

NEAR HACKATHON
Team
1 member- DEOwner
Dex Bennett
Overview
Problem: at Indonesian weddings, guests give cash in envelopes (amplop), and the family keeps a notebook of who gave how much, because they are expected to give back when that guest hosts a celebration, often 5 to 20 years later. The notebook gets lost, and note-taking apps close long before the cycle ends.
Product: RSVPay turns that notebook into an NFT that holds its own money. A host opens a celebration and gets one envelope NFT (NEP-171). Guests scan a QR and give with no wallet to install. Every gift is an entry in the NFT: who, how much, the wish. A share of 0 to 10%, fixed when the envelope is opened, stays locked in that guest's name and can only ever leave as a reply to that guest. When the guest later opens their own celebration, the old envelope rings, and one tap sends the kept share plus a top-up into the guest's envelope, linked to the original gift. If the envelope NFT is passed on, the money, the book and the promises move with it and the previous holder is locked out, also while a transfer is still settling.
How NEAR fits: the contract account has zero access keys, so nobody can change the rules of a promise that has to last decades; CI rebuilds the source to the code hash on chain on every push. Each gift pays for the storage of its own entry. Accounts have readable names, which matters when a family reads its own book.
State: live on testnet (rsvpay-v2.testnet), play money, not audited. One button on the site runs the whole story with real transactions in about 40 seconds. 55 contract tests, 14 live attack checks (10 hostile calls refused, 4 safe-state checks such as zero keys), a 22-row threat model, and on-chain checks of the transfer paths. No independent users yet; Google login and sponsored gas are on the roadmap.