Programs
Program addresses
The program ids per environment, and which are deployed.
What is live today
TREND runs on its own dev validator. The mainnet programs are not deployed: their ids are reserved and no launch exists there. Statement as of 2026-10-10.
| Program | Where | Id | Status |
|---|---|---|---|
trend_launch | Dev validator | G5VTggvWQRn9skJJ1YrDfPvpprVZYdhkUgCRxwpfcokz | Deployed on the dev validator |
trend_acquire | Dev validator | 6vNymM2JMoAS3VzXmmrEweRm3Ac5zkLs23NzDydemgEo | Deployed on the dev validator |
trend_launch | Mainnet | TREND9g3kaNTBfoQ98FVi4B2LVFAEmZVU5z6xxq9CLN | Reserved, not deployed yet |
trend_acquire | Mainnet | CARDSCV6h6VPBtz3k6QtWGWVnMhJZj2vfSyWpB4UsCcB | Reserved, not deployed yet |
| Program | Role |
|---|---|
trend_launch | Launches, the bonding curve, completion and migration |
trend_acquire | The collectible leg: acquisition and conversion |
- Dev ids are the ids of the programs on the dev validator, taken from the IDL the programs build with. They exist on that validator only.
- Mainnet ids are reserved. Nothing is deployed at them, so an account read, a log subscription or a token page for them returns nothing today. This page changes, with a date, when a program is deployed.
GET /healthz returns the programId the API you are calling is configured for. Compare it with this table before you
trust a stream of events.