FAQ
Direct answers for the current protocol
This page focuses on the exact FlashAlliance flow that is live now, including seller approval pages, buyer approval pages, fixed quotas, and the one-alliance-one-trade rule.
Top questions
- Can one alliance buy many NFTs over time? No. One alliance supports one full lifecycle only.
- Why can a non-participant open an alliance page? The page is public for reading, but non-participants are read-only.
- Why do seller and buyer need separate pages? Because they are external actors who only need to approve one specific transfer or payment.
- Does approval transfer the NFT or FATK immediately? No. Approval only grants permission. Execution happens later.
Flow questions
- Why does deposit fail after sale? Because the alliance is closed and cannot reopen funding.
- Why must the second acquisition vote match the first proposal? Acquisition governance is tuple-bound to prevent parameter drift.
- Why did sale execution fail after everyone voted? Usually because the buyer did not approve FATK for the alliance.
- Why does acquisition execution fail after everyone voted? Usually because the seller no longer owns the NFT or never approved it.
Common errors
- Amounts look microscopic. That alliance was created with broken token units and must be abandoned.
- Dashboard volume is empty. If subgraph is unavailable, the frontend now falls back to RPC-based counting and summing.
- NFT still appears after sale. The page shows historical sale context, but the alliance no longer holds the NFT.
- Raised amount still appears after buy. In the new UI this is split into funding, deployed capital, treasury balance, and proceeds depending on state.