Claim + orderly liquidity
The integration should remain optional. Claiming tokens does not require a sale and C1 should not be presented as the default action for every recipient.Recipient choice
The recipient chooses whether to hold, transfer or make a selected amount available through C1.
Single-sided inventory
Only the unlocked token is contributed. No matching quote-side LP position is required from the recipient.
External distribution
Aggregators, intent systems and other execution infrastructure can reach the same underlying C1 inventory.
Progressive completion
Each fill settles atomically while the selected position can complete over time as buyers arrive.
Integration patterns
1
Claim + referral
The platform presents C1 as an optional post-claim liquidity route and sends the recipient to the relevant FlowState flow.
2
Claim + C1 contribution
The claim experience lets the recipient choose an amount to make available through C1 while the remainder follows the platform’s normal claim path.
3
Embedded inventory contribution
Where the platform architecture supports it, selected unlocked inventory can be deposited into the relevant C1 Pool as part of the claim experience.

