So I feel the need to do this, in attempt to protect some people. I BELIEVE
@WARONRUGS
is scamming it’s following. They came from ASEAL, the group that was anti rug and ended up rugging. I shilled I am aware, I made concerns clear in a hope to protect my following and (1/?)

I am here to once again try and do this. Shappy one of the admins, dumps on all of you his following after loading his bag very early with projects they may or may not be paid to endorse. There have been examples of those projects for example, “just hodl” the (2/?)
project that followed ASEAL ended in a rug. The reason I know this for a fact is I have his wallet address. Shappy during the ASEAL admins days knew forced admins to verify their addresses. (3/?)
Shappy dumped all of his ASEAL tokens two days before the announcement that the liquidity was being drained. You can see my tweet here: https://t.co/rfVtoK7X2I
Video proof of Shappys dm and wallet:
https://t.co/CL450oXdAg transaction on the 9th before his the liquidity drain of $ASEAL on the 11th
You can look into the other projects he was able to load up early on, shilled, that later turned out to be rugs.
They have a moral guise, into taking all your funds. They made a fake $BASE telegram channel to try and actively fud the project. https://t.co/Oz23Wy2FZk as you can see here. I'm not touching anything these people touch with a ten foot pole. You DYOR though, I did.
$ASEAL used a bot to get to #1 on dextools and I believe they use this on other projects, I know this because it was discussed in admin chat for ASEAL. Projects they endorse constantly go to #1 on DEXtools and magically disappear.
If this all can be explained and I will delete.
They actively ask for tips as well, do you guys not make enough on your PNDs?
https://t.co/hQos72OKXG
Note this thread uses $ASEAL and $JH as examples there are other coins they play with and continue to play with you can see that through the transaction history’s. This is not specifically just about those “prorekts”

More from Scam

You May Also Like

A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.

Legacy site *downloads* ~630 KB CSS per theme and writing direction.

6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices

https://t.co/qyl4Bt1i5x


PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.

735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices

https://t.co/w7oNG5KUkJ


The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.

The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.