CIGO market-access paper · public version 1.0 · July 2026
CIGO Whitepaper
CIGO is a BNB Smart Chain market-access token published by the COSIGO system for public trading, liquidity access, request-desk settlement, and CIGO-specific market infrastructure.
CIGO is separate from COSIGO™. CIGO is not the COSIGO™ silver-referenced Ethereum token, is not silver-backed, is not a share of COSIGO, is not a debt claim, is not a redemption certificate, and is not a claim on COSIGO reserves or redemption inventory.
This paper documents the intended role of CIGO, the limits of its public market structure, the risks created by decentralized exchange liquidity, the reason for administrative controls, and the distinction between visible wallet value, pool quotes, and actual available fulfillment.
1. Current official CIGO contract
The following BNB Smart Chain contract is the current official CIGO contract for wallet import, market reference, public disclosures, and current CIGO activity.
0x3a38e963f524E0dDFB75dFa1752b4Cd1364F5560
View current CIGO contract on BscScan ↗
Older, retired, test, or mistaken contract references should be treated as historical unless this page and the official market notice identify them as current.
2. Purpose and market-access role
CIGO is intended to create a public market-access layer around the COSIGO ecosystem without representing ownership of COSIGO™ inventory, silver holdings, redemption reserves, or business assets.
Its purpose is limited and practical:
- provide a public BNB Smart Chain token for CIGO-specific market activity;
- support live DEX liquidity and request-desk settlement paths;
- give users a visible token for CIGO trading, quoting, wallet import, and market reference;
- separate speculative public-market activity from COSIGO™ silver-reference disclosures;
- publish risks openly rather than presenting thin liquidity as guaranteed exit value.
3. Difference between CIGO and COSIGO™
CIGO and COSIGO™ are intentionally separated.
- CIGO is a BNB Smart Chain market-access token for trading, liquidity, and public market activity.
- COSIGO™ refers to the separate COSIGO system and silver-referenced COSIGO™ disclosures.
- CIGO is not silver-backed and does not grant a right to redeem silver.
- CIGO does not represent equity, profit share, voting ownership, or a claim on COSIGO reserves.
- CIGO market prices may move independently from any COSIGO™ reference, inventory, or disclosure.
This separation exists to reduce confusion. A public-market token can trade sharply above or below any reference idea. Users should not treat CIGO wallet balance, DEX price, or chart value as proof of collateral backing.
4. Liquidity structure and fake-liquidity risk
CIGO uses public liquidity through the active CIGO / BSC-USD PancakeSwap V2 pool and a separate reviewed/manual request flow. These are different paths.
- Public swap: direct market swap through the active pool, subject to pool depth, slippage, tax, gas, and price movement.
- Request desk: reviewed/manual settlement flow with published quote logic, wallet caps, and available-fulfillment limits.
- Reference quote: a comparison aid, not a guarantee that a large trade can clear at one flat price.
Thin pools can create misleading wallet values. A token can display a price while the paired USDT/BNB depth is too small to support large exits. Volume can also be distorted by bots, related wallets, or repeated small trades. For that reason, COSIGO should not present CIGO liquidity as stronger than the actual available pool depth or request-desk fulfillment capacity.
5. Pool curves and trade impact
CIGO pool trades do not clear against a flat shelf price. A larger buy or sell walks through the pool curve, changing the average execution price as the trade size grows.
This means a visible small-quote price, wallet display, or chart value may differ sharply from the result of a larger trade. Public CIGO interfaces should therefore continue to show live pool status, request-desk estimates, slippage warnings, and clear explanations of pool-curve behavior.
For current pool references, see trade.cosigo.io/pool.html ↗.
6. Fees, taxes, gas, and interface limits
A CIGO trade may include several cost layers. Depending on route and direction, a user may experience CIGO contract tax, PancakeSwap V2 pool fee, BNB network gas, slippage, and current pool movement.
The official live swap interface does not add a separate trade.cosigo.io interface fee. The request desk may include published manual quote assumptions, caps, or safety buffers depending on the route and available fulfillment. These should be disclosed in the interface before a user acts.
Public swap size limits are used to reduce accidental large approvals, user error, and unexpected pool impact. Such limits are protective controls, not guarantees of value, liquidity, or outcome.
7. Administrative controls and governance risk
CIGO was designed with administrative controls intended to reduce bot pressure, whale concentration, early-market abuse, and liquidity extraction. Protective controls can be useful during early market formation, but they also create centralization and trust risks.
Users, reviewers, wallets, and labelers should evaluate these controls openly. Administrative powers can affect transfer behavior, market access, wallet limits, taxes, blacklist or restriction behavior where supported, and future operating policy. Any such control should be understood as a risk as well as a protective measure.
COSIGO does not regard the existence of early-market controls as evidence of fraud or malicious design. At the same time, COSIGO recognizes that centralized controls require clear disclosure and user caution.
8. Request-desk settlement model
The CIGO request desk provides a reviewed/manual flow separate from direct public swap execution. It is intended to help users compare routes, avoid unnecessary large swap impact, and settle only after a request is generated, reviewed, and clearly instructed.
A request-desk quote is not the same thing as a guaranteed public pool exit. The quote can be capped by available fulfillment, wallet limits, manual desk rules, pool depth, and route-specific assumptions.
Current request flow: trade.cosigo.io/request.html ↗.
9. Wallet, scanner, and label risk
CIGO may trigger warnings, labels, or caution messages from third-party wallets, scanners, DEX frontends, browser tools, and security systems. These systems may be delayed, inconsistent, incomplete, discretionary, or based on low-popularity assumptions rather than confirmed misconduct.
COSIGO disputes broad labels that impair CIGO access without identifying a specific abusive function or confirmed misconduct. Users should still read warnings carefully, verify the contract address, review public disclosures, and avoid relying on any single wallet or scanner as the complete source of truth.
Public label notes: labels.cosigo.io ↗.
10. Chain, DEX, and infrastructure dependencies
CIGO depends on BNB Smart Chain for the current token contract, wallet balances, transfers, and public pool activity. It also depends on external infrastructure such as wallets, RPC providers, block explorers, DEX frontends, and PancakeSwap pool contracts for normal public market access.
If PancakeSwap frontends fail but BNB Smart Chain and the pool contracts remain usable, CIGO may still be accessible through other interfaces, direct contract interaction, alternate DEX routing, or manual settlement paths. If BNB Smart Chain itself becomes permanently unusable, CIGO faces existential chain risk and would require a public holder-snapshot and migration process if recovery is possible.
11. Emergency migration policy
If a contract, chain, DEX, wallet-access, or infrastructure failure creates a serious continuity problem, COSIGO should publish a migration notice before asking users to act.
A responsible migration process should include:
- the reason for migration;
- the old and new contract addresses;
- a holder snapshot method and timestamp if relevant;
- how custodian, treasury, and pool balances are treated;
- what users must do and what users should avoid;
- public links to official pages and block explorer records.
Users should ignore unofficial migration messages, direct messages, seed-phrase requests, and wallet-drain links. COSIGO will never need a user seed phrase to migrate or verify a wallet balance.
12. User risk summary
- CIGO is speculative and may lose value.
- CIGO is not silver-backed and is not a redemption claim.
- Thin liquidity can make displayed values misleading.
- Large trades can move pool price sharply.
- Wallets and scanners may show warnings or inconsistent labels.
- Administrative controls create centralization risk.
- BNB Smart Chain, PancakeSwap, wallets, RPC providers, and public frontends are external dependencies.
- Users are responsible for verifying contract addresses before signing transactions.