Loops HouseDaykeeper

NEAR HACKATHON
Team
1 member- MEOwner
Memeshe
Overview
Shared treasuries are run by committees: a multisig needs a council, a token vote needs turnout, a grant committee needs trust, and all three hand custody to a permanent class of approvers. Daykeeper replaces the approvers with a clock and a market.
One shared NEAR treasury. Every round, the right to run it for one day goes to the highest bidder. When the round ends, anyone can ring the bell and the contract mints two function-call access keys on its own account for the winner: one scoped to grant, one transfer per day, at a size fixed at launch, never to the keeper, and one scoped to say, so the keeper can speak as the treasury. Neither key can attach NEAR, so neither can move the principal, and every privileged method re-checks the block timestamp, so the power expires at the deadline with no scheduler, no admin and no server.
Anyone can post a public ask for 0.01 NEAR, and that fee goes into the pool it is asking. The keeper answers one ask a day, and the grant records which one. Bidding is rational because the grant is an absolute amount: bid 0.15, hand out 1.0, to somebody who is not you.
NEAR is why this works: function-call keys are pinned to one receiver and a method list, they cannot attach NEAR, and a contract can add and delete them on its own account. The limit is enforced by the protocol, not promised in code.
Live on testnet: 18 contract tests, 12 invariant checks read straight off the chain, a recorded run where six abuses are refused in the chain's own words, and a browser console where anyone can take the seat and then try to drain the pool.