Sabitlenmiş Tweet
votesa ■
3.9K posts
votesa ■
@votesa
every cycle i find a new way to roundtrip. growth.
Katılım Mayıs 2021
1.4K Takip Edilen4.2K Takipçiler
rh chain was a good reminder that early never feels early.
it feels dumb.
my recent rh chain gains from entries to ATHs:
$CASHCAT 14m → 225m, 16x
$WISHBONE 468k → 9.5m, 20x
$HOODIE 1m → 6.5m, 6x
$INDEX 2.05m → 6m, 3x
everyone reviewed robinhood chain as a product launch. my angle was base timing getting weird, rh mainnet and B20 mainnet one week apart.
nobody cared until the first stupid chart printed. then the same timeline went from "wtf is this chain" to "how do i bridge".
all of this was posted here in real time, with dates to check. next one goes up the same way.
English
@robinhoodjesus looks like it. these guys should have some kind of announcement coming up soon.
English
How a third-party factory copied NOXA’s on-chain identity, launched ~1,800 tokens under a misleading badge, and collected fees from users — while multi-million-dollar platforms failed to notice.
I traced the contracts, owners, funding and fee routing.
Here’s what happened 🧵
English
hard to sell “positive-sum crypto” while Base keeps platforming projects people already brought receipts on.
i sent my @o1_exchange findings directly to key people at Base.
not vague drama. actual onchain work around the airdrop, where ~95% of claimed tokens went to wallets with zero prior tx history.
i also spoke with o1 founders and devs myself. they told me and other users they would clarify it.
then nothing.
Base never commented, o1 never clarified, and the actual concern was just left hanging.
now the same project keeps getting Base support, visibility and ecosystem listings.
that is not a “false info” issue.
if the findings were wrong, someone could have said so and shown why.
instead everyone stayed quiet while the project kept getting pushed.
meanwhile actual builders still have to fight for attention.
Brian Armstrong@brian_armstrong
@CoinbaseDuck This part is key "steering user towards positive sum crypto use case, liquidity, users/customers are your best moat"
English
@votesa @o1_exchange Well, it seems silence is the best weapon against the bitter truth
English
@votesa @o1_exchange yeah transparency matters a lot here, especially when real builders are getting overlooked
English
votesa ■ retweetledi
I’m sorry @brian_armstrong as far as I can remember this is the last thing you did on Base. Probably the least positive sum use case we’ve had in years.
Why don’t you actually jump onchain and do some positive sum activities?
- buy some community coins
- use @Veildotcash to help grow privacy and the anonset
- try @bankrbot, talk about @lienfiapp or trading platforms like @DefinitiveFi etc.
It would be much more impactful for Base than just talking about it. Steer users with actions.
Brian Armstrong@brian_armstrong
@CoinbaseDuck This part is key "steering user towards positive sum crypto use case, liquidity, users/customers are your best moat"
English
@0xDeployer @kevincodex @gitlawb feels like this one was on kevin, but good to see you handled it quickly as usual 🫡
English
heads up a $GITLAWB token was deployed on robinhood chain today ahead of schedule. it is NOT the official token. do not buy it unless you like pain.
we’re working with @kevincodex and @gitlawb to launch $GITLAWB as an omnichain token. it is not live yet.
official CA will only come from this account + kevin/gitlawb.
English
@kevincodex tbh most people don’t really care whether they buy your token on base or robinhood chain. the real play here is just farming another wave of attention and collecting more trading fees on a new chain
English
hey guys do you want to bridge $GITLAWB to RH? same what bankr did?
deployer@0xDeployer
$BNKR is now omnichain and the entire thing was done through the Bankr agent. If you have a coin you can do the same thing using Bankr skills. Links to skills in the quoted post.
English
vvv创始人关注了 @_proxystudio @ErikVoorhees
base:0xb3d7e0c3c39a1d3f1b304663065a2f83ddf56d8e 0xb3d7e0c3c39a1d3f1b304663065a2f83ddf56d8e
$LIQ 0x09b8903abf2ea0721e34427353988c2f43c6d64f
日本語
