Skip to content

docs: extend new code after an upgrade - #171

Open
0xdevcollins wants to merge 1 commit into
testnetfrom
docs/keep-uploaded-code-live
Open

0xdevcollins wants to merge 1 commit into
testnetfrom
docs/keep-uploaded-code-live

Conversation

@0xdevcollins

Copy link
Copy Markdown
Collaborator

What

One paragraph at the end of section 1 of docs/upgrade-runbook.md: how long new code lives on each network, that the backend's daily ContractTtlKeepaliveCron now renews the code each contract runs (boundlessfi/boundless-nestjs#970), and the stellar contract extend command to run by hand where that job is not running. On testnet it says to extend 60 days at a time, because 180 days of rent for the events code does not fit in one transaction fee.

Why

New code gets the network minimum: ~120 days on mainnet, ~7 on testnet. The contracts renew it only when a call lands in its last day (touch_instance). After the 8 Oct testnet upgrade, the events 2.1.0 code was archived once QA traffic stopped, and every staging escrow op then had to restore ~63 KB first. It was restored and extended by hand on 20 Oct.

Docs only; no contract change.

New code starts with the network's minimum lifetime, about 7 days on testnet,
and the contracts renew it only when a call lands in its last day. Testnet's
events 2.1.0 code was archived that way in October 2026. Note the backend
keepalive that now renews it, and the manual command for when it is not
running.
@almanax-ai

almanax-ai Bot commented Oct 20, 2026

Copy link
Copy Markdown

Plan expired

Your subscription has expired. Please renew your subscription to continue using CI/CD integration and other features.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant