[hpmaxi]

Summary

Closes #268

The share token, the compliance stub and the identity verifier never extended their instance TTL. The vault and oracle extend theirs; these three did not, and on testnet their instances already read as archived. Every call that does work on them now extends the instance to 30 days, like the vault. The runbook and the written TTL policy follow in the next PR.

Changes

• The share token extends its instance on transfer, transfer_from, approve and every role call.
• The identity verifier extends it on allow, is_allowed and verify_identity.
• The compliance stub extends it on every hook the token calls and on its admin calls.
• TESTING.md lists the new tests.

Acceptance criteria

• Each of the three contracts extends its instance on the calls listed above
• One test per contract shows a call restoring a decayed instance

Test plan

Automated tests

1. SOROBAN_SDK_BUILD_SYSTEM_SUPPORTS_SPEC_SHAKING_V2=1 cargo test --locked
2. All suites pass; the new tests are the *_instance_ttl ones.

Manual verification

None; the testnet redeploy comes with the group release.

Breaking changes

None.

Checklist

• Self-reviewed my own diff
• Tests added or updated
• Docs updated (if applicable)
• No unrelated changes bundled in

Screenshots

None.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
strata-vault-kit-app	Ready	Preview	Oct 20, 2026 5:43pm UTC

[luchobonatti]

• M-09 (new balances not extended on creation) seems out of scope here. Is it planned for another PR or upstream?

[luchobonatti]

Maybe also extend in balance and total_supply? A later wind-down claim only reads balance, so a quiet wind-down could still let the instance lapse.

[hpmaxi]

Added in #276 (9516c95): balance and total_supply now extend the token's instance before they read, so a wind-down that only reads balances keeps the token alive. A test lets the instance fall below its threshold and checks that a balance read brings it back to the full 30 days.

[hpmaxi]

@luchobonatti On new balances not being extended when they are created: it's in this stack, in #276. Every call that writes a share balance or a freeze, and every role grant, reads the entry back through OpenZeppelin's own reads, so a new entry reaches its extend target in the transaction that creates it.