IronLock IronLock is the first BNB Chain token launchpad where rugpulls are technically impossible. Every safety feature is permanently locked into the smart contract at launch. No admin, no developer, and not even IronLock itself can override them. When a developer launches through IronLock, the smart contract automatically enforces:
No reviews yetBe the first to leave a review for IronLock.xyz
Maker
📌
What inspired me to build IronLock? 💔
I lost over $10,000 in memecoin rugpulls.
The worst part? Every single one looked legit at first. Professional websites. Active communities. Promises of "liquidity locked" and "team tokens vested."
But I kept losing money. And I realized: these safety features were optional. Devs could choose to enable them — or not. Most didn't. And when I asked why, the answer was always "trust us."
I got tired of "trust me, bro."
So I built IronLock — a launchpad where safety features aren't optional. They're hardcoded into the smart contract.
🔒 180-day LP locks — you can't remove liquidity early
⏳ 90-day dev vesting — no instant dumps
🛡️ Anti-snipe — bots can't front-run
💰 Community refund votes — if the dev abandons, you get your money back
No admin overrides. No "we'll do it later." Just code that protects everyone.
I built this so no one else has to lose their savings to rugpulls.
🔗 Try it: https://ironlock.xyz
Report
If the safety features are permanently locked in, what happens if a real exploit is found later - can it ever be patched or does the contract stay frozen forever?
Report
Maker
@ayhankroglpz1m This is the most important tradeoff in trustless
design and you're right to ask it.
The honest answer: the core safety features
(LP lock, vesting, milestone releases) are
permanent and cannot be patched. This is
intentional — if they could be changed,
they wouldn't be trustless.
However, we handle exploits in two ways:
1. New versions — if a critical exploit is found,
we deploy IronLock v2 with the fix. Existing tokens
stay on v1 (frozen as-is), new launches use v2.
Users can see which version a token launched on.
2. Pre-launch audits — we're getting a professional
security audit before mainnet to catch exploits
before real funds are at risk. The audit report
will be public.
3. Bug bounty — we'll run a public bug bounty
program so the community can find issues before
bad actors do.
The tradeoff is real: immutability = trust but
also = no patches. It's the same tradeoff Bitcoin
makes. We believe the audit + bug bounty is the
right approach rather than admin keys that defeat
the whole purpose.
Report
Curious how you handle liquidity provisioning then if the contract is locked with no admin keys?
When Milestone 1 triggers, the contract automatically
calls PancakeSwap's addLiquidityETH() function — 30%
of raised BNB + the corresponding token amount are
sent directly to PancakeSwap to create the LP pair.
The LP tokens come back to the IronLock contract
where they stay locked for 180+ days.
No admin keys involved at any point — the smart
contract handles the entire liquidity provisioning
automatically. The dev never touches the BNB that
goes to liquidity.
Report
love the idea of locking safety features directly into the contract so no one can flip a switch later. worth trying out when more projects start launching there.
Report
Maker
@ersin168162 Thanks Ersin! That's exactly the core idea —
safety enforced by code, not promises. No admin
can flip a switch and change the rules after launch.
Would love to hear your feedback once you try it out
If the safety features are permanently locked in, what happens if a real exploit is found later - can it ever be patched or does the contract stay frozen forever?
@ayhankroglpz1m This is the most important tradeoff in trustless
design and you're right to ask it.
The honest answer: the core safety features
(LP lock, vesting, milestone releases) are
permanent and cannot be patched. This is
intentional — if they could be changed,
they wouldn't be trustless.
However, we handle exploits in two ways:
1. New versions — if a critical exploit is found,
we deploy IronLock v2 with the fix. Existing tokens
stay on v1 (frozen as-is), new launches use v2.
Users can see which version a token launched on.
2. Pre-launch audits — we're getting a professional
security audit before mainnet to catch exploits
before real funds are at risk. The audit report
will be public.
3. Bug bounty — we'll run a public bug bounty
program so the community can find issues before
bad actors do.
The tradeoff is real: immutability = trust but
also = no patches. It's the same tradeoff Bitcoin
makes. We believe the audit + bug bounty is the
right approach rather than admin keys that defeat
the whole purpose.
Curious how you handle liquidity provisioning then if the contract is locked with no admin keys?
@berktrh4 Great question! Here's how it works:
When Milestone 1 triggers, the contract automatically
calls PancakeSwap's addLiquidityETH() function — 30%
of raised BNB + the corresponding token amount are
sent directly to PancakeSwap to create the LP pair.
The LP tokens come back to the IronLock contract
where they stay locked for 180+ days.
No admin keys involved at any point — the smart
contract handles the entire liquidity provisioning
automatically. The dev never touches the BNB that
goes to liquidity.
love the idea of locking safety features directly into the contract so no one can flip a switch later. worth trying out when more projects start launching there.
@ersin168162 Thanks Ersin! That's exactly the core idea —
safety enforced by code, not promises. No admin
can flip a switch and change the rules after launch.
Would love to hear your feedback once you try it out
at ironlock.xyz 🔒