Environments
Keep local testing, approved canaries, and production traffic separate.
Each integration uses an explicit API origin, credentials, campaign configuration, and network profile. There is no demo: true field that turns a production request into a safe test.
Local development#
Local examples use chain 31337, the synthetic token symbol TST, and clearly fictional fixture addresses. Fixture responses are useful for interface and error-path testing. They do not prove that a token exists, that an operator wallet holds it, or that a real transfer has occurred.
Supply a local test key through the development setup. Do not reuse a production key in a fixture environment.
Remote testing#
Use the testing origin and approved chain/token profile provided for your integration. The hosted testing profile is Robinhood Chain Testnet (chain 46630) with a configured test ERC-20 of no monetary value; a separate sandbox or faucet is not guaranteed by this contract, and the operator's test wallet must hold that token before anything is sent.
Synthetic activity belongs in an isolated project and environment. Changing an event label to test does not prevent a live campaign from queueing a real transfer.
Campaign issuance modes#
The campaign object exposes issuanceMode separately from its active/paused status:
| Mode | Behavior |
|---|---|
disabled | New issuance is not enabled for that campaign. |
canary | Issuance is restricted to the approved small-value launch test and its recipient controls. Real tokens may be involved. |
live | The approved production integration may issue within its configured limits. |
A campaign can be active while issuance is disabled. Check both fields. A live mode is not evidence that every accepted allocation is already approved or sent.
Moving to production#
Receive the approved HTTPS origin, production key, campaign ID, token contract, decimals, and chain ID. Confirm the expected profile before sending any allocation. Do not infer network support from a familiar ticker or address.
Keep environment identity in your own reward-outbox records. Deduplication is scoped to the project, environment, and operation; sending the same business event to two separate environments can create two independent rewards.
Do not copy local pending instructions into a live queue. Construct a reviewed production rollout with explicit event selection and recipient authorization.
What examples mean#
Example timestamps, addresses, and IDs are documentation fixtures, not deployment configuration. Any path showing a local origin is intended for development only. No public production API hostname is implied by the Slices website domain.
Related: Testing your integration, Going live, and Assets.