Repository navigation
keep_alive never refreshes instance storage, so a contract kept alive only via keep_alive can still archive Admin/Oracle/Treasury #566
Description
Problem
keep_alive is the permissionless TTL refresh (#97) meant for quiet periods. In all three contracts it extends the target record and its sub-records, but never calls extend_instance_ttl(&env) (grep -c extend_instance_ttl inside each keep_alive → 0). Instance storage holds Admin, Oracle, Treasury, FeeBps, Paused and MaxSponsors. If no other state-changing call happens for the instance TTL window, the instance archives, and every entrypoint fails until someone restores it, even though keepers were dutifully calling keep_alive.
Suggested fix
Call extend_instance_ttl(&env) in every keep_alive, and add a TTL test that advances the ledger past the instance threshold while calling only keep_alive.
Activity
urielit1313-creator commentedon Oct 13, 2026
Submitted PR #570 resolving this issue across all contracts (
escrow,maintenance-pool, andmilestones).Details
extend_instance_ttl(&env)insidekeep_aliveacross all three contracts so periodic calls maintain active instance storage (Admin,Oracle,Treasury,FeeBps,Paused,MaxSponsors) alongside persistent records.test_keep_alive_extends_instance_ttl) advancing ledger sequence past the 100,000 threshold, executingkeep_alive, and asserting instance storage TTL is restored to 500,000 ledgers.Payout Address (Base USDC):
0xfE777c43e4B0A24fFA1527eD520d1E7f9ECED483huangji6693-max commentedon Oct 27, 2026
Submitted PR #764 calling
extend_instance_ttl(&env)inkeep_aliveacrossescrow,milestones, andmaintenance-pool, with TTL regression tests (test_keep_alive_refreshes_instance_ttl) in all three contracts: #764ravimahatonp commentedon Oct 27, 2026
Hello team,
I examined the issue "keep_alive never refreshes instance storage, so a contract kept alive only via keep_alive can still archive Admin/Oracle/Treasury" in mergefi/contracts and would be glad to implement the required changes.
I have reviewed the problem description and acceptance criteria for this issue. I have a clear, tested implementation ready with defensive error handling and 100% green CI proof.
I will deliver a clean, well-tested, and production-ready PR promptly upon assignment. Kindly assign this issue to me.
Thank you!