Loops HouseDibs

NEAR HACKATHON
Team
1 member- MAOwner
Marsela
Overview
Dibs: every bed paid before anyone books.
One friend books the group trip, then spends weeks chasing everyone. A shared pot only moves the trust problem. Dibs turns the money rules into code on NEAR.
Each bed is its own keyless NEAR account. Friends pay from their own wallet on any chain: NEAR wallets through NEAR Connect send USDC straight in; EVM wallets (OKX, MetaMask) and Solana wallets (Phantom) pay through NEAR Intents 1Click with an exact-output quote. The bed's code forwards the money into the crew's own Sputnik DAO.
Nobody books until every bed is paid. There are no refunds: request_refund always fails. A friend who drops out sells the bed at face value (there is no price field) to a pre-funded waitlist in one call.
The booker never holds the money. The booking confirmation lands in the trip's own inbox; OutLayer checks booking.com's DKIM signature inside Intel TDX, NEAR AI Cloud reads it privately (friends see dates, guests and the total, never names or card), the contract verifies the signed verdict, and the DAO pays. A real booking.com confirmation was verified and paid out on testnet. Beds are drawn with OutLayer VRF, and an enclave can issue the trip a single-use, hotels-only card capped at the pot (Lithic sandbox).
Live on NEAR mainnet with real USDC: contract dibsapp.near and a crew DAO, with beds paid from NEAR and from Base through 1Click. Testnet runs the full flow. 46 contract checks, 35 of them attacks, each refused with its own error code.
Friends sign in with NEAR Connect or pay straight from an EVM wallet; the booker proves the account with NEP-413 (or ERC-191 for a 0x account). Judges without a wallet get a clearly marked demo route.
Live: https://dibs.larinova.com · Judge path: JUDGES.md · pnpm verify re-checks the chain.