Loops HouseLockstep

NEAR HACKATHON
Team
1 member- MAOwner
Marc Donovici
Overview
Community DAOs often fund things together: a meetup, a hackathon, a maintainer stipend. Each council can only pay for certain things, waits for the others, and has no way to enforce "we pay if they pay". Pledges can add up to more than the plan costs while the plan still cannot happen.
Lockstep makes the pledge conditional and the outcome all-or-nothing. Each DAO votes once, with an ordinary Sputnik FunctionCall proposal, to pledge up to an amount for specific cost lines. No money moves. The page computes the most the pledges can legally cover (a max-flow with a min-cut certificate anyone can recheck) and says exactly what completes the plan, e.g. "50 tUSD for speaker travel completes it; 50 for food would not". Anyone can fill that gap with an escrowed top-up.
On activation, Lockstep pulls each DAO's share through a Transfer proposal on the DAO itself, filed and approved by a one-member role the DAO installed by vote, with the plan id in msg (ft_transfer_call). If every share arrives, the payees are paid. If any transfer fails, for example because a DAO spent the money elsewhere, Sputnik marks it Failed, Lockstep reads that back and refunds everything that arrived. Nobody pays for part of a plan, and the money stays in each treasury until settlement. Councils see all of it as ordinary proposals in their treasury app (shown in Trezu's testnet mode).
Live on NEAR testnet: lockstep.testnet has no access keys. Four plans settled and four rolled back on chain; npm run verify checks every plan from public data without keys (65/65 on 5 Nov). Demo: https://lockstep-f45z2r7dda-ew.a.run.app Rust contract (near-sdk 5.30), Sputnik DAO v2, NEP-141, NEP-330; 21 contract tests, 5 sandbox end-to-end tests with real DAO votes.