PinkSale
Rejected venues wait the longest for re-review; a rejection has to earn another look before the scheduled date.
REJECTED. PinkSale is a permissionless token launchpad and locker, not a diversified investment or yield protocol. A client entering a sale underwrites the issuer, token code, allocation, listing, market making, liquidity-lock terms, and possible KYC/audit provider—none of which PinkSale standardizes into a security judgment. Reported launchpad TVL is capital temporarily committed across unrelated issuers, so it cannot support a venue-level allocation.
- A specific PinkSale-issued asset enters the research perimeter and receives its own issuer, eligibility, control, and liquidity file
- The exact campaign publishes verified legal entity, offering terms, beneficial owners, audited code, treasury controls, allocation, and enforceable redemption rights
- A proposed-size secondary exit is demonstrated after all issuer and team unlocks are modeled
The research file
Mechanism and client claim
Project creators configure presales, fair launches, token minting, vesting, and liquidity locks across supported chains. Buyers contribute the sale asset and receive a newly issued token if the campaign finalizes; the creator may direct part of proceeds into DEX liquidity and retain the remainder according to configured terms. Locking LP tokens prevents their withdrawal until a date but does not restrict token minting, transfer taxes, blacklists, admin changes, unlocked team supply, off-platform wallets, or the market value of either reserve. Every campaign is therefore a separate issuer-underwriting file.
Control, governance, and legal perimeter
PinkSale provides contracts and an interface, while the project creator chooses token code, sale parameters, allocations, liquidity percentage, lock duration and promotional claims. Optional KYC and audits come from third-party providers and do not guarantee recovery or commercial legitimacy. Platform and contract admins add one control surface, but the issuer remains the dominant one. An advisor cannot substitute a PinkSale badge, automated locker, or platform aggregate for beneficial-owner verification, securities analysis, transfer eligibility, code review, treasury controls and conflict disclosures on the offered token.
Incident and operating record
Launchpads are exposed to scams, failed launches, flawed token contracts, compromised project keys and economically abusive but code-compliant designs. The reviewed PinkSale materials warn users to perform their own diligence and do not promise that KYC or audit status eliminates loss. No single PinkSale contract incident decides the verdict because venue-level approval would still pool unrelated issuer risks. The absence of a loss at the launcher cannot prove the honesty, solvency, legal status or post-launch behavior of thousands of independent token creators.
Exit, liquidity, and failure path
Before finalization, refund rights depend on the campaign contract and configured success conditions. After distribution, exit depends on whether the token lists, how much liquidity was actually seeded, the percentage and duration of LP locks, token transfer controls, taxes, unlocked supply, and market demand. A locked LP token does not lock the contributed base asset for the buyer and does not guarantee a bid. Aggregate launchpad TVL is especially poor evidence of executable liquidity because it spans campaigns, chains, stages and tokens that are not fungible with one another.
Comparison and decision
A separately reviewed on-chain security or asset can document issuer, holder claim, legal eligibility, reserves, transfer restrictions and redemption. PinkSale offers none of those facts at venue level; it is the distribution plumbing through which a candidate might appear. The advisor perimeter should ingest an individual token only after it crosses materiality or client relevance and then underwrite that issuer directly. Reopen is campaign-specific, never a blanket PinkSale approval.
Sources
The claims above trace to these. Where a number could not be independently verified, the thesis says so.
- PinkSale Docs — launchpad overview · primary · accessed 2026-08-19
Supports: launchpad services, sale types, supported chains - PinkSale Docs — liquidity lock · primary · accessed 2026-08-19
Supports: LP-token lock, unlock date, limitations - PinkSale Docs — KYC · primary · accessed 2026-08-19
Supports: third-party KYC, badge scope, no recovery guarantee - PinkSale Docs — audit · primary · accessed 2026-08-19
Supports: third-party audit, token contract scope - PinkSale — Terms and conditions · primary · accessed 2026-08-19
Supports: platform role, user responsibility, risk disclosure - DefiLlama — PinkSale protocol data · secondary · accessed 2026-08-19
Supports: protocol category, chain perimeter, current TVL
Inherited controls
The verdict above grades the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The least safe layer sets the position’s grade, and the position table names which one that is.
| Chain | Verdict | Grade | Control constraint |
|---|---|---|---|
| BNB Smart Chain | Rejected | freezable | the validator set concentrates around one company, and the chain has been halted by decision. |
| Ethereum | Approved | sovereign | No sequencer, no upgrade key, no operator who can be compelled — rule changes require social consensus. |
| Polygon PoS | Rejected | hybrid | a public validator set orders transactions, but a 5-of-9 multisig can instantly upgrade staking and canonical bridge contracts, while a 5-of-8 controls custom child tokens. |
| Cronos | Rejected | freezable | the validator set and direction are governed by one exchange company. |
| Avalanche | Approved · limits | crypto-backed | no party can freeze or seize C-Chain funds, but one vendor writes the only production client and Messari measured over a third of stake hosted on AWS. |