Tombstones for deleted contracts

[Asheeyah23]

Background

When a contract's storage TTL expires, downstream consumers need a signal that it's gone.

What to build

Track contract liveness; emit a tombstone row when storage entries expire.

Key files

• src/indexer/tombstones.ts (new)

Acceptance criteria

• Tombstones inserted on expiry detection
• Tested with fixture

Drips Wave · Complexity: Intermediate · 150 points

---

Docs (W033–W040)

---

Required: Before submitting, join the contributor Telegram so your work can be tracked and counted toward the Stellar Wave: https://t.me/+fxHXq8f1SwlkZDBk

[rahimatonize]

@rahimatonize has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi maintainer, I would love to work on this issue, could you please assign me to it

ℹ️ Repo Maintainers: To accept this application, review their application or assign @rahimatonize to this issue.

[dubemoyibe-star]

@dubemoyibe-star has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi, I'd like to take this issue.

I'll implement contract tombstone tracking so expired contracts produce a clear deletion signal for downstream consumers. The work will include adding the tombstone handling logic, recording tombstone entries when storage expiry is detected, and ensuring the behavior is covered with fixture-based tests.

This should make contract lifecycle changes easier to track and help consumers handle expired contracts reliably.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @dubemoyibe-star to this issue.

[Maximum-Prosper]

@Maximum-Prosper has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hey Maintainer.
I;d like to work on this issue, please kindly assign.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Maximum-Prosper to this issue.

[githoboman]

@githoboman has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

helllo would love to work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @githoboman to this issue.

[collinsezedike]

@collinsezedike has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Interesting one, the tricky part is detecting expiry itself since there's no explicit "deleted" event on-chain, just storage that stops existing once its TTL runs out.

Here's my plan:

• src/indexer/tombstones.ts: periodically check tracked contracts' storage entries against the ledger, comparing the entry's TTL/expiration ledger against current ledger height
• When an entry crosses into expired territory, insert a tombstone row recording the contract id, the ledger at which expiry was detected, and any other relevant metadata for downstream consumers
• Guard against re-inserting a tombstone for an already-tombstoned contract
• Test with a fixture simulating a contract whose TTL has expired, confirming a tombstone is correctly inserted exactly once

Happy to start as soon as I'm assigned.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @collinsezedike to this issue.

[drips-wave]

Congratulations, @githoboman! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @githoboman: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊