Loops HouseNEAR Rehearsal

NEAR HACKATHON
Team
1 member- ABOwner
Abdulqodir Iyanda
Overview
NEAR Rehearsal helps maintainers review the financial consequences of a contract repair before merging it. A refund can look correct while silently deleting another user’s unpaid obligation. Rehearsal checks both the intended recovery and the obligations that must survive.
Our supported workflow is: inspect a repair, validate its setup, execute the acceptance policy in a local NEAR Sandbox, compare payouts and liabilities, then export a portable handoff that another reviewer can rebuild or replay independently. In the pinned Sputnik #238 repair family, a plausible clear-all patch is rejected for erasing Bob’s liability; the supplied repair returns Alice’s bond while preserving Bob’s obligation and checking retries, authority and inherited state. A second recorded Sputnik #226 case demonstrates an existing proposal surviving an upgrade and executing its payment.
Try the public evidence workbench at https://rehearsal.dolepee.com/consequences/. It clearly labels recorded execution. Fresh replay runs locally; confined source compilation requires supported Linux. The demo uses a supplied repair, not a fresh AI-generated patch. Exported evidence binds the candidate, policy and measured outcomes for independent review. Rehearsal supports these bounded Sputnik workflows, rather than arbitrary NEAR contract repair.