Context
Currently, deployment addresses and URLs are configured via environment variables (see .env.example):
RPC_URLGOLDSKY_ENDPOINTPERP_MANAGER_ADDRESSUSDC_ADDRESS
This approach was necessary during active development when addresses were frequently redeployed. However, once deployments are frozen/stable, these values should be hardcoded directly in the SDK.
Benefits
- Simplifies SDK integration for implementors
- Reduces configuration burden (no need to look up and specify addresses)
- Provides sensible defaults for production usage
Proposal
Once deployment addresses stabilize, hardcode them in the SDK while maintaining the ability to override via configuration if needed (e.g., for testing or custom deployments).
References
Target Version
0.2.1
Context
Currently, deployment addresses and URLs are configured via environment variables (see
.env.example):RPC_URLGOLDSKY_ENDPOINTPERP_MANAGER_ADDRESSUSDC_ADDRESSThis approach was necessary during active development when addresses were frequently redeployed. However, once deployments are frozen/stable, these values should be hardcoded directly in the SDK.
Benefits
Proposal
Once deployment addresses stabilize, hardcode them in the SDK while maintaining the ability to override via configuration if needed (e.g., for testing or custom deployments).
References
Target Version
0.2.1