1. What FATK is used for
- Community testing rewards and contributor incentives.
- Internal campaigns and ecosystem utility flows.
- Alliance settlement only when seller accepts FATK terms.
2. What FATK does not guarantee
- Automatic acceptance by external NFT sellers.
- Automatic liquidity comparable to major stable assets.
- Cash payout semantics for community testing rewards.
3. Why confusion appears in NFT purchase flow
`buyNFT` in your contract pays seller using the alliance ERC20 token, but execution is only allowed for a previously approved acquisition tuple (NFT, tokenId, seller, price, deadline). If alliance token is FATK, seller receives FATK. This is contract-defined behavior, not UI convention. Therefore, the settlement token must be selected with seller agreement in mind.
4. Recommended strategy by environment
| Environment | Recommended alliance token | Reason |
|---|---|---|
| Local development | FATK | Fast bootstrap and deterministic tests. |
| Sepolia testing | Test stable ERC20 or commonly accepted test token | Closer to realistic settlement expectations. |
| Production | Liquid settlement asset agreed by both parties | Lower OTC friction and clearer pricing. |
5. Product-level guidance
Keep FATK as ecosystem incentive token, but expose settlement token choice explicitly in create flow and documentation. This preserves utility while keeping real trading paths practical.