Add unit tests for the contract initialisation function setting all state fields correctly

[Chucks1093]

Summary

The contract initialisation function sets the admin address, base price, protocol fee, and treasury address. Unit tests should confirm every field is readable from contract state immediately after initialisation and that calling initialise a second time panics with already_initialised.

Scope

• Call initialise with known values and assert each field is readable from state
• Assert calling initialise a second time panics with already_initialised
• Assert state is unchanged after the second initialise attempt

Acceptance Criteria

• All fields readable from state after initialisation
• Second initialise panics with already_initialised
• State unchanged after second attempt

ETA: 12 hours

---

Coordinate on Telegram

[mayborn005]

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

Hello @maintainer, I'd love to work on this issue. I'll keep the implementation simple, clean, and well-tested.

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

[LayanGift]

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

Hello Maintainer,
I’d like to take ownership of this issue. I’ll implement the required changes, test them properly, and submit a pull request for review.

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

[Neche58]

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

hi maintainer i will like to work ont his issue please

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

[Akinloluwa20]

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

I would love to work on this issue

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

[drips-wave]

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

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

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Third Campaign campaign!

@mayborn005's PR #729 was approved and merged by @Chucks1093.

🏆 @mayborn005: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (694 total points). Track your full progress on GrantFox.

👏 Great work, @mayborn005! Keep contributing to accesslayerorg.

[drips-wave]

This issue has been completed by @mayborn005 as part of the Stellar Wave Program's 8th Wave 🥳

😎 @mayborn005: You earned 150 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.