Protocol
Risks
WickDeck protocol constraints can reduce certain technical risks, but cannot guarantee token value, creator behavior, market liquidity, or trading outcomes.
WickDeck protocol constraints can reduce certain technical risks, but cannot guarantee token value, creator behavior, market liquidity, or trading outcomes.
What is it?
This page lists failure modes the rest of the docs mention in passing. It is not complete. Anything that can happen to a token on a public chain can happen here.
Why does it exist?
Protocol constraints are easy to read as protection. They are constraints on specific technical powers. They are not a book of outcomes.
How does it work?
- Token value can go to zero after a fully compliant launch.
- Creator behavior is not bound by the bond. A creator bond gives launchers economic skin in the game. It is not insurance and does not guarantee market quality or creator behavior.
- Market liquidity can be thin on the curve and thin after Ignition even when LP is locked.
- Wallet limits reduce simple single-wallet concentration during bonding. They do not prevent coordinated actors from using multiple wallets.
- Expired launches enter sell-only mode. New buys are disabled, but holders may sell back through the bonding curve.
- Routing and bridges can fail or cost more than the ticket estimate.
- Intel and Scan are analytical signals. They are not a suitability test.
- Factory admin can change the live trading fee. Deadline managers can extend a window.
- Catalog and some terminal figures may still be demo data while contracts are pinned on testnet.
What can go wrong?
WickDeck protocol constraints can reduce certain technical risks, but cannot guarantee token value, creator behavior, market liquidity, or trading outcomes.
What should traders understand?
If you only read one page, read this one and Wick Standard. Then look at the specific market’s Scan before you trade.