`reissue_certificate` does not index the new certificate and leaves the old one active

[feyishola]

issue_certificate records new certs in IssuerCertIds/OwnerCertIds, but reissue_certificate (lib.rs:400-476) only stores the certificate and emits an event — it never calls append_cert_id. Reissued certificates are therefore invisible to get_certificates_by_issuer / get_certificates_by_owner. The parent (old_id) is also left Active, so both parent and child are simultaneously valid despite "reissue/supersede" semantics. Fix: append the new id to both indexes and mark the original Revoked/Superseded (emitting a revocation event).

[bolajigate-cell]

@bolajigate-cell has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

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

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

[Demilade10]

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

Hi I can fix this

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

[Johnsource-hub]

@Johnsource-hub has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi, I'd like to work on this issue.

I have hands-on experience with backend development, databases, and API design, as well as frontend work with React and modern CSS. I write tested, maintainable code and enjoy contributing to open source projects.

I've reviewed the issue and I'm confident I can implement a solid solution while following the project's conventions.

Happy to get started right away if assigned — looking forward to contributing.

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

[tobiadewola41-eng]

@tobiadewola41-eng has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I would like

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

[holystrings]

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

Hello Maintainer! After going through the issue and its acceptance criteria, I’m confident that this task matches my skills and experience. I’m prepared to investigate the existing implementation, make the necessary changes, and ensure the final solution behaves as expected. I’m available to start immediately and would be happy to take ownership of this issue. Kindly assign it to me.

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

[OmniZlatoon]

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

Sir please assign me your issues. I am desperate to work but issues are scarce. my Eta is 5 hours max.

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

[drips-wave]

Congratulations, @OmniZlatoon! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @OmniZlatoon: 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 🌊