stayers.funProtocol Addresses
Official SDK references and the separately configured Stayers account.
Code exists; Stayers production behavior is not yet verified.
Stayers uses the official Meteora program identifiers supplied by its installed SDKs. A Stayers-specific reusable DBC configuration is a separate account and must not be replaced with a sample or another platform's address.
SDK reference addresses
| Program | SDK reference identifier | Explorer lookup |
|---|---|---|
| Meteora DBC | dbcij3LWUppWqq96dh6gJWwBifmcGfLSB5D4DuSMaqN | Reference account ↗ |
| Meteora DAMM v2 | cpamdpZCGKUy5JxQXB4dcpGPiikHawvSWAd6mEn1sGG | Reference account ↗ |
These are reference identifiers verified against the installed SDK exports. They are not evidence of a successful Stayers launch.
Check deployment state
The Transparency dashboard checks mainnet genesis and executable program accounts when its private RPC is configured. Verified public addresses receive Solscan links and an observation timestamp.
The Stayers DBC configuration is shown only when the deployment supplies it and the expected program owns the account. If it is absent or unreadable, the value remains Not verified.
Verify a token relationship
A valid Meteora pool alone is not necessarily a Stayers launch. The pool must reference the intended Stayers configuration, with a matching mint and the required supply/authority policy.
Use actual program/state verification and confirmed transaction evidence. Never infer platform membership from a token name, ticker, screenshot or familiar logo.
Updating references
Address changes require a reviewed SDK/integration update. Documentation should not silently follow an arbitrary address entered by a page visitor. The public dashboard accepts no user-supplied RPC endpoint or configuration override.