g8keep

$GRIND token launch: The token was deployed successfully but a massive influx of traffic caused the indexer to fail. We immediately noticed user's purchasing the token directly from the contract. We believe the token was easily identified by the 21.5 ETH initial liquidity Pons provided. When we were able to manually index the token, it was nearing bonding, and determined mutually with the GRIND team that posting the CA before bonding would lead to users aping and eating significant penalties. The snipe protection worked exactly as intended due to the protection at the protocol level, not the UI level. Due to this, we determined the best course of action would be to wait until the token migrated and then post the CA that is tradable everywhere. If this token was launched on any other platform, snipers would’ve been able to accumulate a substantially higher supply of tokens (in this case with the purchase amounts, nearly all of the available supply) which was prevented through g8keep’s sniper protection No addresses were airdropped tokens tokens prior to the token migrated. Please note that Dexscreener does not track the amount spent on tokens in the bonding curve, so it looks like users spent nothing but sold tokens. This is not the case. Everything is onchain and verifiable. We will post a further follow-up detailing the transactions of the buyers and sellers during the bonding curve phase.

The fastest way to trade any token on hyperEVM There is no second best Refer users & earn rakebacks on their trading fees [soon] Trade & earn points for [redacted] hyper.g8.xyz

Memescope is officially live on hyperG8 Trade all @LiquidLaunchHL pre-bonded tokens at light speed The time to hyper trench is now You will now earn points for trading on hyperG8, and they'll be retroactively distributed

Trade @LiquidLaunchHL pre-bonded tokens at light speed on the fastest trading terminal on hyperEVM HyperG8 Memescope Coming soon

@VickieC1982 @666Sixpaths Really appreciate you both!

@666Sixpaths @g8_keep Best TL;DR ive seen yet. S/O to @g8_keep 👏👏👏

I honestly believed sniper protection meant sniping was impossible, now I learned it can't be totally avoided and some technical stuff I haven't figured out fully yet @g8_keep did prevent snipers getting away with a large chunk of the total supply so shoutout to them 🐸

@hazza_360 @thecrypto411 There is a large distinction between liquidity of a token and the token's market cap The token started with 50k liquidity and 5% of the tokens supply in the curve An 50k unpenalized buy & sell would crater the token. The buy was protected and the output was SEVERELY penalized

@g8_keep @thecrypto411 That makes no sense, that sounds like little to no penalty on a 50k buy! What was the market cap when they bought, surely not 100k

$GRIND token launch: The token was deployed successfully but a massive influx of traffic caused the indexer to fail. We immediately noticed user's purchasing the token directly from the contract. We believe the token was easily identified by the 21.5 ETH initial liquidity Pons provided. When we were able to manually index the token, it was nearing bonding, and determined mutually with the GRIND team that posting the CA before bonding would lead to users aping and eating significant penalties. The snipe protection worked exactly as intended due to the protection at the protocol level, not the UI level. Due to this, we determined the best course of action would be to wait until the token migrated and then post the CA that is tradable everywhere. If this token was launched on any other platform, snipers would’ve been able to accumulate a substantially higher supply of tokens (in this case with the purchase amounts, nearly all of the available supply) which was prevented through g8keep’s sniper protection No addresses were airdropped tokens tokens prior to the token migrated. Please note that Dexscreener does not track the amount spent on tokens in the bonding curve, so it looks like users spent nothing but sold tokens. This is not the case. Everything is onchain and verifiable. We will post a further follow-up detailing the transactions of the buyers and sellers during the bonding curve phase.

@hazza_360 @MrYellow1899 yes. the snipe protection and penalties worked exactly as they would normally. The UI does not contain any snipe protection logic. It is 100% in the protocol.

@g8_keep @MrYellow1899 But it was stated that the penalty starts at 20x. Did this happen?

@cryptokarlheinz @Pons_ETH @imthatdexter @Spuds___ the protection is onchain. there is no protection on the ui. even if the UI listed the token, the same people would have bought the same transactions, and likely dumped faster as more users would have entered the token. we'll speak about this more in the twitter space tonight

@g8_keep @Pons_ETH @imthatdexter @Spuds___ don't get me wrong, i really love g8keep thats actually the reason why it really hurts how things went today launch could have been an awesome proof-of-concept but it kinda turned into the opposite the best onchain snipe protection is worthless without same protection on UI

The Claims site will be up shortly Something to note: The issue was the pair address was not live until it bonded. So sending the CA would have caused more confusion with no pairs. People were buying direct to contract, but the snipe protection was still working. For instance the screenshot of the $73k sale. That guy paid more than $50k because of the penalties. We will detail all this once everything is in order.

@cryptokarlheinz @Pons_ETH @imthatdexter @Spuds___ at that point, if we were to do so, users would immediately ape and get instantly dumped on by bots and lose nearly 100% of their investment and the token likely would have never migrated.

@Pons_ETH @imthatdexter @Spuds___ @g8_keep you should have posted instructions how to buy from contract to still give everyone a fair chance

@DecryptoPioneer @Pons_ETH It is near impossible to entirely prevent sniping The sniper spent $50k and sold everything for 1.5x Traditionally they would have owned 70%+ of the tokens supply and entirely ruined it Our protection worked, our UI didn't

@Pons_ETH @Pons_ETH all those claim by you and the @g8_keep team about unsnipable is just delusion then? Damn man i dont know how to react in this issue. Gatekeep that platform had one single task!!! To prevent sniping! Its a joke. Whats the point of such platform then?

Guy who I have been nothing but respectful to, and asked me for a $GRIND allocation for his community... Is now flexing that they took advantage of our issue At least you know it was not the team that did this... I look forward to the armchair sleuths who sent false accusations now sending an apology.

@Ogcsn We really appreciate this ❤️

@g8_keep I think you’re doing great work at G8 but sniping is something that cannot be totally prevented. Maybe reduced to a minimal level but not totally blocked. Great work 🙏🏽

@Pons_ETH @Spuds___ Most hyped token launch for us (and abstract) 🙏

@Spuds___ @g8_keep Well to be fair, they have launched many tokens. This one was caused issues for some reason.

@TWDTim @GrindTheCoin @grok The answer is that we are a launchpad, not related to the claim

@g8_keep @GrindTheCoin @grok The question is when claim. You didn’t answer

@MasterMemeSol No We are explaining that even though the website went down, which we’ve taken accountability for, our protocol level protection still prevented the sniper from obtaining > 70% of the supply

yeah we failed, but we didn't fail as hard as others would have? 🤣

@TWDTim @GrindTheCoin @grok explain this like I’m 5

@g8_keep @GrindTheCoin I’m Lost

@KingslyBella G8keep makes no funds from penalties or bonding curve trading

@MrYellow1899 The sniper spent $50k and sold everything for a 1.5x Traditionally this purchase would have allowed them to obtain>70% of the supply It was protected

@g8_keep Sounds like another "protected" launch not being protected

@Hershkowitzy @0itsali0 @MintedNFTs You’d prefer 70% of the supply to be owned by one person instead?

@g8_keep @0itsali0 @MintedNFTs Pons literally said he partnered with you to prevent sniping. Not prevent "some" sniping. It's worse to set this expectation and miss than to do nothing.

the supposed $GRIND launch was meant to be unsnipeable (which was false and it was sniped by a minted member with 12 ETH, he made 18 ETH off that buy) i shared it to @MintedNFTs within the first couple of minutes of the launch before the tweet was announced, myself and members bought before everyone. xeetio.

@tyk3e @CrashDavis03 @0itsali0 @MintedNFTs x.com/poppunkonchain…

@g8_keep @CrashDavis03 @0itsali0 @MintedNFTs Where is the money going to ?

@SwissScotch @sslainy14967 @Jbeanedoteth2 @GrindTheCoin @Phin_totten @AbstractChain @Pons_ETH Correct thank you

@sslainy14967 @Jbeanedoteth2 @GrindTheCoin @Phin_totten @AbstractChain @Pons_ETH @g8_keep no a sniper penalty, if you ok paying the penalty, you can snipe it just heavily impacts the amount of supply you can snipe

Recently launched a token @GrindTheCoin which was endorsed by many Influencers as well as @Phin_totten from the @AbstractChain In the photo you can see the sales of the team in the first minutes So far there have been no clear comments from the project founder @Pons_ETH nor from ceo @g8_keep - @PopPunkOnChain I find the comments about the person getting a ticket ridiculous