Loops HouseHoldUp

NEAR HACKATHON
Team
1 member- DAOwner
danial soleimani
Overview
Many crypto scams do not break into a wallet; they persuade the owner to pay. A fake support desk asks you to move funds to a "safe" wallet, or a supplier's invoice arrives with a new address. Chainalysis estimates crypto scams took in at least $14 billion on-chain in 2025, and a payment cannot be pulled back once it is final.
HoldUp is a Telegram payments bot on NEAR. Payments to people you have not marked as trusted wait a short time first. Funds sit in HoldVault, our own NEAR contract. Paying a new payee creates a hold (5 minutes on the hosted testnet demo). While it waits, deterministic rules and open-weight AI models check the payee's on-chain history and the message that prompted the payment. If something looks wrong, an oracle account extends the hold and records reason codes and the sha256 of its evidence on-chain. Only the sender, or a guardian they chose, can cancel; the money then returns to the sender's balance. Anyone can release a hold once its time has passed. Trusted payees (trust takes effect after a delay) are paid at once, up to a daily cap.
How NEAR fits:
- The oracle's only key is a function-call key limited to one method, extend_hold. The contract accepts only a later release time, at most 72 hours after the payment, so the AI can add time but cannot move, release or cancel money.
- HoldVault has no access keys and no upgrade method. Anyone can check its key list and code hash.
- Each user gets a named sub-account whose key can call seven vault methods. Telegram ids never go on-chain.
- Payments use native NEAR and NEP-141 tokens (a test stablecoin in the demo).
- Every hold, extension, cancel and release is a NEP-297 event. Cancels after a flag are counted per payee on-chain; once two senders have cancelled, the next sender to that payee is braked by a rule within seconds.
Live on NEAR testnet, with test tokens only: vault.holdup-soleimani.testnet, bot @HoldUp_HoldUp_bot.