Loops HouseNomogenesis

NEAR HACKATHON
Links
Team
1 member- LIOwner
Lipcsik László
Overview
When a shared data source goes down, every agent that depends on it needs a repair — but the cost can exceed what any one agent is allowed to spend. Nomogenesis turns that deadlock into a rescue market on NEAR.
In the working case, a rescue costs 11 units. Two buyer agents, each capped at 7, independently commit 5.5; a third refuses under its spending policy. Three providers compete. A NEAR smart contract selects a bonded two-provider bundle, locks the funds, checks two committed Merkle data components, and settles only after both proofs pass. The two worker jobs complete, the selected providers withdraw, and the losing offer is released.
This lifecycle completed on public NEAR Testnet in 19 finalized transactions. Judges can reproduce it in a fresh local NEAR Sandbox with npm ci && npm run verify. The Python Shield SDK audits the completed case and fund accounting. The demonstration uses controlled data and one operator’s separate agent signers: the proofs verify committed data, rather than independently attesting an arbitrary external repair.