Loops Housemorrow

NEAR HACKATHON
Team
1 member- CEOwner
Cem AYYILDIZ
Overview
Morrow: a time-lock vault for real Bitcoin, enforced by a NEAR contract through Chain Signatures. No soft fork, no bridge, no wrapped BTC.
PROBLEM. Whoever holds your Bitcoin keys can spend in the next block; nothing calls it back. Bitcoin has no vaults (OP_VAULT/OP_CTV inactive).
WHAT WE BUILT. Coins sit in a Bitcoin P2WSH address spendable by (a) owner key + NEAR co-signer key, (b) guardian key + co-signer key to the recovery address only, (c) owner key alone after a timelock if NEAR is gone. The co-signer key is derived by NEAR Chain Signatures (v1.signer-prod.testnet / v1.signer) for the Vault Contract, which has no access keys, builds every Bitcoin tx itself, and refuses to co-sign a withdrawal before the user's delay. During the delay any guardian can claw back. Guarantees: no instant theft, safe-direction recovery, no hostage, no silent rule changes.
HOW NEAR IS USED. Rust contract contracts/vault, deployed and locked: morrow-vault-v1.testnet (testnet) and morrow-vault.near (mainnet), code_hash 3JwGeYBT3FQjyNDhcQ86sTjCEcix2KuTJPePzGxRefsZ, reproducible with make wasm. Every spend is a sign_input call answered by the NEAR MPC network.
VERIFY (all public). Web app https://morrow-web-341572138939.europe-west1.run.app: connect Meteor/Intear testnet wallet at /vault/new, create a signet vault, fund it, request a withdrawal as a thief, claw it back. Done end to end on 2026-11-14 as Vault #176: /vault/176 and /proof/176; funding tx c0950780bcdf…, clawback tx 43d6b7ac173f… on mempool.space/signet. Proof Page reads rules, code_hash and lock live from NEAR RPC and recomputes the address in-browser. make demo runs scenarios S-1..S-7 against the live testnet signer (15 min, no keys); CI does the same, log in evidence/.
STACK. Rust (near-sdk), TypeScript core + CLI, React web, Playwright e2e, Docker regtest. MIT.
LIMITS. No audit; no real BTC claimed on mainnet; Telegram guardian alerts not built.