[FE-31] Build PublicVerificationPage

[mftee]

Problem

Third parties such as lawyers, land bureaus, and government officials cannot verify a document's integrity without creating a SMALDA account. The public verification endpoint (BE-23) exists but there is no corresponding public-facing page.

Proposed Solution

Create a PublicVerificationPage inside frontend/module/verify/ that is accessible without authentication and allows anyone to verify a document hash against the Stellar blockchain.

Acceptance Criteria

• Page requires no login — it is publicly accessible
• Renders a prominent hash input field with a Verify button
• Validates that the input is a 64-character hex string before submitting — shows inline error for invalid format
• On submit, calls GET /api/module/verify/:hash and displays the result
• Verified result shows: a green Verified on Stellar banner, the Stellar transaction hash (using StellarTransactionLink FE-11), ledger number, and anchored timestamp
• Unverified result shows: a red Not verified on Stellar banner and a message that no blockchain record was found for this hash
• Includes a brief explanation of what document hash verification means for users unfamiliar with blockchain
• All component files live inside frontend/module/verify/

[levoski1]

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

Kinly assign me this issue

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

[udoyechinenyevictoria]

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

Hello! Please can I work on this issue?

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

[Tinna23]

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

Hey,

I can take this on if it’s still open.

Looks pretty manageable from what I’ve seen, and I’ll just follow the existing patterns in the codebase and make sure it’s implemented cleanly and tested properly.

Happy to jump in on it.

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

[drips-wave]

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

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