Issue #2 — Contract Initialization & Admin Queries

[yusuftomilola]

With the scaffold in place, the contract needs a one-time initialize entry point to store the admin address and payment token. We also need the two public query functions (admin, payment_token) so that front-ends and tests can read back the configured values.

Task

Building on the code from Issue #1, add the following public functions to the #[contractimpl] block:

1. pub fn initialize(env: Env, admin: Address, payment_token: Address) -> Result<(), Error>

   • Return Error::AlreadyInitialized if DataKey::Admin already exists in instance storage.
   • Call admin.require_auth().
   • Write admin to DataKey::Admin and payment_token to DataKey::PaymentToken in instance storage.
   • Emit an event: topic = (symbol_short!("init"),), data = (admin, payment_token).

2. pub fn admin(env: Env) -> Result<Address, Error>

   • Delegate to Self::get_admin(&env).

3. pub fn payment_token(env: Env) -> Result<Address, Error>

   • Delegate to Self::get_payment_token(&env).

Files to modify

• contracts/workspace_booking/src/lib.rs

Acceptance criteria

• cargo check -p workspace_booking passes.
• cargo clippy -p workspace_booking -- -D warnings passes.
• Calling initialize twice panics with Error(Contract, #3) (AlreadyInitialized).
• admin() returns the address passed to initialize.
• payment_token() returns the token address passed to initialize.
• The init event is emitted on successful initialization.

Technical notes

• Guard against double-initialization with env.storage().instance().has(&DataKey::Admin).
• symbol_short! macros are limited to 9 characters.

[soma-enyi]

Gm Gm Maintainer!!!!
I would like to work on this issue!!!!

[Bosun-Josh121]

Hello,

I am an active open-source contributor and I have a strong background in backend and smart contract engineering (specifically Stellar/Soroban) and I would like to tackle this issue.

This issue aligns perfectly with my skillset as I have previously built similar functionality and have reviewed the current codebase, so I am prepared to navigate the architecture without issues.

I can commit to delivering a clean, tested solution within 24 hours. I value clear communication and i'm happy to iterate on any feedback during the review process.

[gelluisaac]

I’m interested in tackling this! I have a strong background in smart contract development and full-stack systems, so I'm well-equipped to handle the requirements here. Could you please assign this to me?

[anonfedora]

I'm Anonfedora, I'm a Fullstack Blockchain Engr. I'm proficient in Rust (soroban), Rust serverside with Axum and tokio, Nestjs, epxressjs have vast experience in contributing and building on the Stellar ecosystem with the Rust using soroban's SDK.
I'm also good at comprehensively testing features.
ETA: < 8 hours

[devJaja]

Hello, I’m a smart contract and full-stack developer actively contributing to open-source ecosystems. I’ve worked on 30+ projects across the ecosystem, with hands-on experience in Solidity, Cairo, Soroban, JavaScript, TypeScript, Rust, and building on the Stellar ecosystem. I’m passionate about delivering secure and scalable blockchain systems and would love the opportunity to support and contribute to this issue.

[ussyalfaks]

I would like to contribute by implementing the initialize, admin, and payment_token entry points for the workspace booking contract, ensuring secure one-time initialization, proper authorization, storage validation, event emission, and test coverage to guarantee safe and verifiable contract configuration. ETA: 4–6 hrs.

[ryzen-xp]

Hi maintainers 👋
I’m a blockchain developer with strong expertise in Stellar, Rust,TS and Stellar SDK integrations. I’ve worked on multiple Stellar-based smart contract and backend systems.

I understand the scope of this issue and can deliver a reliable, production-quality solution with proper tests and documentation.
Plz assign me !!

ETA: 14 hours

[auracule007]

Hi maintainers, I'm Promise Adedokun. I'm a blockchain developer with solid experience working with Stellar, Rust, and Soroban smart contract development. I've built and deployed multiple production-ready contracts with proper initialization patterns and access controls. I'd like to work on this contract initialization issue. I can implement the one-time initialize function with admin authentication and storage persistence, add the public query functions for admin and payment token, ensure proper error handling for double-initialization, and include event emission with the correct symbol format. My ETA is 3-4 hours.

[bitstarkbridge]

I’d like to work on this issue because it directly impacts reliability and developer experience. Problems around deployment, repository configuration, and contract/network mismatches can block contributors entirely, so resolving them has immediate value for both the maintainers and the broader user base. I’m particularly motivated by issues that require careful debugging and clear documentation, since solving them not only fixes the immediate bug but also improves the overall workflow and prevents future regressions.

[phertyameen]

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

From the description, the task involves adding the initialize entry point and query functions to store and expose the Admin and PaymentToken in instance storage. The implementation will include:

Guarding initialization with Error::AlreadyInitialized

Calling admin.require_auth() before writing state

Storing Admin and PaymentToken under DataKey

Emitting the (symbol_short!("init"),) event with (admin, payment_token)

Implementing the admin() and payment_token() query methods for external reads

I’ll also include tests to confirm:

initialization succeeds once
re-initialization fails
stored values can be queried correctly.

If no one else is actively working on it, I can open a PR shortly.