Assets
Identify the reward token by chain and contract, not by ticker alone.
Every campaign has one approved ERC-20 reward asset on one EVM chain. Read it from the campaign resource; there is no public asset-catalog endpoint in this version.
This is a synthetic local asset example. It is not a supported production token listing.
Asset identity#
The authoritative identity is the pair chainId + tokenAddress. symbol is a display label and must not be used to route a payout, select a network, or establish issuer identity.
decimals determines how raw integer amounts are displayed as token units. Obtain it from the approved campaign configuration rather than assuming every token has 18 decimals.
A reward response includes the campaign asset so that the original instruction remains interpretable in reports.
What approval covers#
Before activating a campaign, the operator verifies the exact token and network profile: contract identity, decimals, transfer behavior, applicable limits, the operator's wallet and send path, and the required recipient restrictions.
Implementing ERC-20 methods does not make every token suitable. Fee-on-transfer, rebasing, restricted-transfer, or unusual token behavior can conflict with exact net allocations and must be assessed explicitly. A campaign's amount limits are also far stricter than the API's uint256 representation limit.
Do not infer approval from a familiar ticker, the existence of a network connection, or another application's successful integration.
Stock Tokens and other approved tokens#
The allocation API does not distinguish reward amounts by marketing category. It issues the exact amount of the approved campaign token. For a restricted asset, the partner and operator must satisfy the agreed eligibility and distribution controls before issuance and sending.
An accepted API request does not establish legal eligibility or ownership rights in an underlying company. These technical docs do not replace the asset's current issuer terms or the campaign's eligibility review.
What Slices does not do#
Slices does not source, mint, bridge, wrap, swap, or price tokens in this version. It does not convert a dollar-denominated reward into token units. The operator holds the inventory in their own wallet, and the customer backend supplies the exact allocation.
There is no GET /v1/assets, token-selection parameter on issuance, or public asset-approval API. Read the approved asset through Get a campaign.
Check before sending#
Compare the returned chain ID, token contract, and decimals with your approved integration configuration. Treat any mismatch as a stop condition. Do not silently substitute a token with the same symbol.
Use Token amounts to handle decimal conversion without losing precision.
Related: Campaigns, Recipients, and Going live.