Memecoins can go to zero
Risk1.1
No underlying value
A memecoin’s price rests on attention and liquidity. It can lose most of its value in minutes or go to zero for good.
Risk1.2
Anyone can sell
Creators, early buyers and anyone else can sell at any time.
Risk1.3
A holder buys the fall
In a lasting decline it keeps adding to a losing position until its rules, its funds or a stop-loss stop it.
Risk1.4
Fund only what you can lose
Put into a holder only money you can afford to lose completely.
Automated trading can lose money
Risk2.1
Fixed rules, no forecasts
A holder follows fixed rules; it does not predict prices. Rules that do well in a choppy market lose in a steady fall or a sudden crash.
Risk2.2
Stop-losses have limits
A stop-loss sells at a loss by design, sells one max trade per pass, and does not fire while a holder is paused or the engine is off.
Risk2.3
Some presets never stop out
The Aggressive and Degen presets have no stop-loss, and Degen also has no profit target and keeps every reward for trading.
Risk2.4
Every round trip costs
Fees and tax take 4% on the curve and 2.5% on the pool for a coin launched here, and more for a coin with a higher tax. A take-profit earns only what the rise leaves after that cost.
Risk2.5
Settings can stall profit
If your Sell trigger does not clear the round trip plus your Profit target, the holder will rarely or never take profit, while it keeps buying dips.
Risk2.6
Software can fail
A bug in our engine could cause trades the rules did not intend.
Smart contract risk
Risk3.1
Not audited by a third party
Coins launched here rely on our FeeSplitter and FeeSplitterFactory contracts, and the platform leg on our FeeVault. They are tested with 100% line and branch coverage, fuzz, invariant and fork tests and Slither static analysis, which lowers the chance of a bug but does not rule it out.
Risk3.2
No admin, no upgrades
That protects you from us changing them, but it also means a bug cannot be patched in place and would affect every coin that uses them.
Risk3.3
Contracts we do not control
Those of four.meme, PancakeSwap and WBNB carry their own risks.
four.meme and PancakeSwap
Risk4.1
four.meme can change
Its TokenManager2 is an upgradeable proxy. We watch its implementation and stop buys across the platform when it changes, and wallets approve only the exact amount they hold, but a change could still affect open positions.
Risk4.2
Launches depend on four.meme
It can change its fees, its rules or its API, or stop offering launches, which would block new launches here.
Risk4.3
Graduation pauses trading
When a coin’s curve fills, it moves to PancakeSwap. No trades are possible during the move, so a holder cannot sell until the pool is live.
Risk4.4
New pools can be thin
A new pool starts with the liquidity the curve raised, so larger sales move the price.
Risk4.5
The tax is permanent
The tax of a coin launched here and its recipient cannot be removed later.
BNB Chain
Risk5.1
Congestion and gas
BNB Chain can be congested, halted or reorganised, and its gas price can rise. The engine never bids above 3.00 gwei; when the network costs more than that, it waits, and so do stop-losses.
Risk5.2
Dropped transactions
Transactions can be dropped or delayed, and the engine only counts a trade once it is final on chain.
Risk5.3
No undo
A confirmed transaction cannot be undone.
Custody of the holder wallets
Risk6.1
Custodial wallets
holders.pro generates and keeps the keys of every holder’s treasury and trading wallets, and you cannot sign for them yourself.
Risk6.2
Compromise or mistakes
If our keys, our signer or our key management service were compromised, or if we made a mistake, the balances in those wallets could be lost.
Risk6.3
No insurance
Those balances are not insured and not covered by any deposit protection.
Risk6.4
Limits in software
Our signer only sends BNB to your wallet, the holder’s own wallets or the FeeVault. That limit is enforced by our software, not by the chain.
Keys, servers and operations
Risk7.1
One server
The Service runs on a single server with off-site backups. A hardware failure, a hosting outage, a bad deployment or an attack can stop the engine for minutes or hours.
Risk7.2
Nothing trades while it is down
That includes stop-losses; claims and payouts wait.
Risk7.3
Rate-limited providers
We read and write the chain through free-tier RPC providers that have quotas and rate limits. When they fail or run out, the engine waits instead of trading on stale data, which can delay buys, sells and stop-losses.
Risk7.4
Automatic safe modes
The engine may switch itself to unwind or dry run when something looks wrong.
Price data
Risk8.1
Snapshots
A holder decides from a market snapshot: the curve’s last price on four.meme or the reserves of the PancakeSwap pool, plus the BNB/USD price from a Chainlink feed. A pass does not trade on a snapshot more than 20 seconds old.
Risk8.2
Prices move before the trade
The price can still move between the snapshot and the trade, up to the slippage you allow.
Risk8.3
Pushed prices
Large trades or deliberate manipulation can push a pool price and trigger buys or sells that would not happen otherwise.
Risk8.4
Unknown BNB price
When the BNB/USD price is unknown or stale, buys stop only if a market-cap range is set.
When rewards arrive
Risk9.1
Tax arrives in chunks
A launched coin’s creator tax does not reach its holder trade by trade. It collects inside the token contract and moves to the coin’s FeeSplitter only when the token dispatches it, once the token’s own conditions are met.
Risk9.2
It can be rare
A coin with little trading may dispatch rarely or never. After a dispatch the engine claims once at least 0.010 BNB is pending.
Risk9.3
Accrued is not paid
The Accrued tile shows what is waiting, but accrued tax is not yours until it has been dispatched and claimed. Nothing in the trading rules depends on it.
Slippage and MEV on the pool
Risk10.1
Visible before confirmation
Transactions on BNB Chain can be seen before they are confirmed. Bots can trade just before and just after a holder’s pool swap and take part of its value, up to the slippage it allows: by default 3% on the pool and 4% on the curve.
Risk10.2
Partial protection
The engine sets a minimum output from a simulation of the exact swap and a short deadline. Trades are sent to private block builders to reduce sandwich attacks: this lowers that risk but does not remove it, and a trade is sent publicly when the private route fails.
Risk10.3
More slippage, more exposure
A higher slippage setting makes this risk larger.
Regulation and tax
Risk11.1
Rules differ and change
The rules for automated trading, custody of crypto-assets and memecoin launches differ between countries and are changing.
Risk11.2
Restrictions can follow
A new law or a regulator’s decision could restrict the Service where you live or force us to change or stop it, possibly at short notice.
Risk11.3
Your tax
Every trade, claim and payout may be a taxable event for you. The records are public, but working out and paying your tax is your responsibility.
No guarantee of liquidity or returns
Risk12.1
No promised profit
Nobody promises that a holder makes money, that a coin keeps a market, or that you can sell at any price.
Risk12.2
No floor
A holder adds buying and selling to a coin; it does not guarantee liquidity, a price floor or volume.
Risk12.3
The past is no guide
Results of any holder, preset or leaderboard say nothing about the future.
Risk12.4
Rewards can stop
Creator rewards depend on other people trading the coin and can stop at any time.
Your responsibilities
- Fund a holder only with money you can afford to lose.
- Keep your own wallet, its seed phrase and the devices it runs on secure.
- Read every approval in your wallet before you sign it: the action, the holder and the amounts.
- Understand your settings, including the round trip, the stop-loss and the preset you pick.
- Watch your holders, and pause them when you are unsure.
- Follow the law where you live, including tax and sanctions rules.