Skip to content

Feat : add Contract Address Registry API#182

Closed
ryzen-xp wants to merge 1 commit intoGildado:mainfrom
ryzen-xp:feature/Contract-Address-Registry-API
Closed

Feat : add Contract Address Registry API#182
ryzen-xp wants to merge 1 commit intoGildado:mainfrom
ryzen-xp:feature/Contract-Address-Registry-API

Conversation

@ryzen-xp
Copy link
Contributor

@ryzen-xp ryzen-xp commented Mar 3, 2026

Pull Request Description

Summary

Adds a new GET /api/contracts endpoint to expose deployed Soroban contract addresses for testnet and mainnet.

Changes

  • Implemented ContractRegistryService to load contract data from environments.toml
  • Added ContractRegistryController to handle API responses
  • Added /api/contracts route
  • Supports optional ?network= query parameter
  • Response includes contractId, network, version, and deployedAt
  • Added caching headers for performance

Purpose

This allows the frontend to fetch and cache contract addresses at startup instead of relying on hardcoded environment variables. Contract deployments can now be updated via configuration changes without requiring a frontend rebuild.

Acceptance Criteria Covered

  • Structured JSON response per contract
  • Data sourced from configuration (no hardcoding)
  • Supports multi-network (testnet/mainnet)
  • Includes deployed ledger sequence (deployedAt)
  • New contracts can be added via config only
Screenshot From 2026-03-03 11-08-25

Close #79

@ryzen-xp ryzen-xp closed this Mar 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant