RTP_John

Your absoutely wrong, and fortunately, the blockchain proves it. Rather than spread lies you should be more responsible. Do an ounce of research before posting FUD like this. Here's what happened, when, and why: 1. An $RTP holder of 2%+ (worth more than $3 Million USD at the time) was contacted on his cell phone by a scammer who claimed that his crypto accounts were under attack. Through a series of phone calls and text messages, the holder was directed to enter his keys on a website. Regretably, he was unsophisticated and gave up his keys. 2. Within a few minutes, the holder's $RTP was stolen from this wallet: BmnzzD1rHn3jVWNpmhsAdNUhfzMC8xQWebcyDLENLTFP 3. The attacker then sold $90k USD worth of $RTP, followed by other smaller sells. In total, the attacker profited over 1,000 SOL. 4. The victim/holder contacted our team to notify us of the attack. 5. We had 1 choice to make--and we had to make it quickly: do nothing (realizing that this bad actor had enough supply to truly rug the project and steal 99.9% of the liquidity) or use the team's supply to take the remaining liquidity and migrate it to a new token, after which we could air drop 1:1 all legit holders with the new token. 6. To protect all holders and the liqudity, we chose to act and protect, not sit idly and be further victimized. We used the casino's 55% supply wallet of $RTP to sell as much as possible and take 99% of the liqiduity before the attacker could. That was ~5,000 SOL. 7. Within minutes, we used all of that liquidity to fund a new LP and deploy $RTP.BET. 8. Within hours, we air dropped every wallet that legit held $RTP with the exact amount of the new RTP.BET token (1:1). Obviously we excluded the compromised wallet from the holder who got attacked (he is out all of his holdings / personal responsibility) as well as all of the wallets we traced where the hacker was starting to spread around the old $RTP token before rugging it. 9. Here are all of the known wallet addresses tied to the attacker: 7HASig8J1zmX6cgnnGhHf8dsfMX4119yKm7K6qqpZPjo FSwhF8DKpjAGGDQ5L61gbkDGTjdmG4gCfwvz8ZdK3Zoy 3BShwQp2QPdBDi3FfYxu2biS4Xd27pijqD5ECoYvYatZ EZVYX97TLjuPrNHFQtTtmJ8Lzq4PkqRZEjKnzHQer6Le EbS1nvPqMebQ8NkBBNPGxGa7iGCoqiMroHGz1317vK72 4NCGZ9k5TosiFZTxENaGdmenBTt5ubxe8eAhZATzRN6N 7rc6HHudfbN6SnEAmwZ8MnBsN9mcwQdqR7Z4ebSFdrVA FDDz5QXjf5NDEJ2aYW2nMStLdEAgDPznwMYx5VmvGFUM 4Vu4MMY7L74bjWtyTTLg2bGQuFcByEjUgnYrkZkmGbBC 779tyG9vBPfuNk2zJU3aG9sBbz7Sh5zdBfJrVKvTpLPw **We have reported these addresses to CEX/authorities and flagged them as stolen. 10. Every holder of $RTP on Phantom was able to immediately see and access their $RTP.BET tokens. They just had to go to Manage Tokens > make it visible. 11. Every holder of $RTP on a DEX like @coinbase or MEXC was also in receipt of the air drop (we verified for anyone who provided their wallet and proved this on Solscan), but they are waiting to see their tokens. It's a matter of the CEX making the new token visible. We posted about this earlier today. Check our X. 12. Most importantly, look at the new RTP.BET. You will see the 1:1 in tokens held by 147+ legit holders. You will also see the initial funding of the LP with all of the SOL that was extracted during the protect/migrate protocol we had to run to protect holders. dextools.io/app/token/rtpb… 13. Since this event, several others have tried to scam by lying that they previously held $RTP and didn't get their air drops. But when they are asked for the wallet address to prove they held $RTP, they can't do it or offer a fresh wallet that clearly never held anything, let alone $RTP. 14. The discrepancy between the ~300 holder count in $RTP before the migration and the 158+ holder count of $RTP.BET is simply that we excluded the hacker's addresses, the victim's address, and, based on the snapshot from Solscan, any addresses that were clearly bots and held, i.e., 100 $RTP. That said, anyone who previously held $RTP and feels they did not receive their airdrop, we are happy to investigate. Thus far, every single legit holder who has asked us to verify has had verification on Solscan and they are satisfied. The trouble of anyone on X posting without complete information or fairness of doing due diligence is that it sends out the wrong message. We took action to proect our project and its holders, not rug them. Just because a chart shows a sudden rug-type event does not ALWAYS mean it was a rug. The only reason the old $RTP chart looks like a rug is because we took action to protect the liquidity. This is all independently verifiable. Hopefully others like @Chyan who also posted negatively about our actions can review this post and the blockchain and recant publicly. Either way, onward and upward for us. We will not be stopped or deterred.