Skip to content

Implement Soroban client service` #55

@Nemenwq

Description

@Nemenwq

Dependencies: Issue #26.

Context:
All services need a consistent way to call Soroban contracts.

Scope:

  • In scope: A shared wrapper with call + simulate helpers.
  • Out of scope: Full key management solution.

Implementation Notes:

  • Provide a single interface used across services so it’s easy to mock in unit tests.
  • Centralize:
    • network selection (testnet/mainnet)
    • contract IDs
    • fee settings / timeout defaults

Acceptance Criteria:

  • callContract and simulateTransaction available.
  • Signing handled internally (from env/secure config).

Files: backend/shared/soroban-client/

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions