BuildX - $GRABS

8.2K posts

BuildX - $GRABS banner
BuildX - $GRABS

BuildX - $GRABS

@BuildXrp

Creator of https://t.co/Kcg0KY3zaj | XRPL innovation builder Quick replies across the TL: music legends, sports tension, memes, whales & moon facts Join: https://t.co/hcVNdW7OeT

xrp Katılım Aralık 2024
839 Takip Edilen4.8K Takipçiler
Enjooyer
Enjooyer@0xEnjooyer·
"there are no good devs" Yeah no shit. Good dev spends $5k and 300 hours building. Rugger spends $300 and 15 minutes copy pasting. Good dev's coin does a 3x. Rugger's does a 50x before the pull. Good dev gets called a scammer when it retraces. Rugger is already on coin number 4. Good devs spend months shipping content and updates, no one cares. Rugger drops the next CA, everyone is in. WE made the incentives completely backwards yet everyone wants to blame the launchpad or the bundlers. YOU have the power to vote with your wallet. Vote.
English
242
135
1.1K
73.9K
Money Minded Apes
Money Minded Apes@moneymindedapes·
across 20k NFTs we might’ve earned 10 XRP in royalties in the past 30 days. Cost about $1500 or so a month to run mma just domains, internet, servers, subscriptipn fees, software. Income must increase or expenses must decrease. You decide.
English
10
8
28
2.4K
BuildX - $GRABS retweetledi
Vegas
Vegas@VegasLamb·
💖 Happy Valentine’s Day, Grabbers! 🙌 Today’s the day for the epic COREUM (TX) airdrop to all MG Grab Bags holders! 🤙 🎁 Even with the artist hiccup🍿rewards are flowing!💰– evolve your NFTs & earn passive yields year-round on XRPL and other blockchains! Join the Discord: discord.com/invite/9EChBbK…. 🚀 Mint here for the next holiday drop👇 xrp.cafe/collection/mg-… @TheMoneyGrabs DYOR & stay scam-safe! ❤️💰 #MoneyGrabbers #ValentinesDayAirdrop #XRPL #NFT #CryptoRewards #TX
English
0
5
9
524
MrBeast
MrBeast@MrBeast·
Like this tweet if you see it, curious if that causes it to get pushed to more people.
English
3.9K
1.3K
81.8K
2M
Sam Altman
Sam Altman@sama·
Peter Steinberger is joining OpenAI to drive the next generation of personal agents. He is a genius with a lot of amazing ideas about the future of very smart agents interacting with each other to do very useful things for people. We expect this will quickly become core to our product offerings. OpenClaw will live in a foundation as an open source project that OpenAI will continue to support. The future is going to be extremely multi-agent and it's important to us to support open source as part of that.
English
5K
4.3K
46.5K
16.7M
BuildX - $GRABS
BuildX - $GRABS@BuildXrp·
Just pause and think about this!
BuildX - $GRABS tweet media
English
1
1
7
134
BuildX - $GRABS
BuildX - $GRABS@BuildXrp·
@KanaKemo @Acquired_Savant @JoelKatz That's their argument though: Ripple won't give them funds, hence why they charge transaction fees to help maintain and prop up the XRPL's brittle infrastructure. (paraphrased, not my words)
English
0
1
3
346
KanaKemo
KanaKemo@KanaKemo·
@Acquired_Savant A user was charged 659 XRP for simply using the native dex. The fee should be 0.000012 but xaman charged this user 659 and dimmed it in transactions so user wouldnt notice Worst part Ripple keeps funding these scammers and wont give XRP holders any alternatives @JoelKatz
KanaKemo tweet media
English
14
11
40
6.5K
Patrick L Riley
Patrick L Riley@Acquired_Savant·
Xaman already uses your seed to silently sign a SECOND hidden transaction behind the scenes without user approval, routing 'fees' straight to their pocket without a separate explicit approval. Now they're pushing XLS-103d nested multisig. Don't be fooled, this opens the door to deeper background drains disguised as 'security.' if this protocol passes, you can bet that Xaman would approve themselves as one of the 'nested signatures'. Audit your txns on XRPScan after paying a Xaman fee. Was it one tx or two? XLS-103d isn't something the ledger needs, it's an attack vector disguised as legitimate just like Xaman wallet. Self-custody means NO hidden signatures. #XRPL #Xaman #XLS103d
Wietse Wind - 🪝🛠 Xaman® + XRPL + Xahau@WietseWind

It is Aug 16, 2025. In my Twitter DM's, a worried community member asks for help/advice. He has $200k in XRP in an XRPL account, and he set up Multi Sign. Then he set up multi sign for the accounts he used for the initial Multi Sign. Unknowingly, he created a "nested Multi Sign" setup. While the XRPL allows one to configure this, it creates a condition that can never be resolved: even with access to the secrets belonging to the nested Multi Sign accounts, the XRPL will never accept the signatures because of the nested condition. At @XRPLLabs we can't just fix this, because code is law and the XRPL code happens to allow setting up a condition where one is locked out of their wallet 🥹 The only way to resolve this, is an amendment. An amendment that allows for nested signatures. I don't know many people who can actually code this, but I happen to have the privilege of working alongside of one of the few: @RichardXRPL. And @sereneblade is a loing long time contributor to the XRPL and good friend of @XRPLLabs. So what did we do? We discussed, and started coding. Resulting in an amendment we submitted today to the rippled/XRPL code base. With this code change, merged into a future release by @RippleXDev and voted in by validators, our community member reaching out to me on August 16th last year will get access to his funds again. Here's the (hopefully to be merged and voted in) amendment: github.com/XRPLF/rippled/… There are some take-aways here 😉 Yours, Your friends at @XRPLLabs 🙏

English
46
52
214
35.3K
Patrick L Riley
Patrick L Riley@Acquired_Savant·
@RippleMuse1111 I do most things through code right now on my desktop, but I am working on a new wallet for the ledger.
English
8
1
26
1.6K
Wietse Wind - 🪝🛠 Xaman® + XRPL + Xahau
It is Aug 16, 2025. In my Twitter DM's, a worried community member asks for help/advice. He has $200k in XRP in an XRPL account, and he set up Multi Sign. Then he set up multi sign for the accounts he used for the initial Multi Sign. Unknowingly, he created a "nested Multi Sign" setup. While the XRPL allows one to configure this, it creates a condition that can never be resolved: even with access to the secrets belonging to the nested Multi Sign accounts, the XRPL will never accept the signatures because of the nested condition. At @XRPLLabs we can't just fix this, because code is law and the XRPL code happens to allow setting up a condition where one is locked out of their wallet 🥹 The only way to resolve this, is an amendment. An amendment that allows for nested signatures. I don't know many people who can actually code this, but I happen to have the privilege of working alongside of one of the few: @RichardXRPL. And @sereneblade is a loing long time contributor to the XRPL and good friend of @XRPLLabs. So what did we do? We discussed, and started coding. Resulting in an amendment we submitted today to the rippled/XRPL code base. With this code change, merged into a future release by @RippleXDev and voted in by validators, our community member reaching out to me on August 16th last year will get access to his funds again. Here's the (hopefully to be merged and voted in) amendment: github.com/XRPLF/rippled/… There are some take-aways here 😉 Yours, Your friends at @XRPLLabs 🙏
English
87
146
876
148.2K
🚜Kang
🚜Kang@KangSchwepe·
@BuildXrp @Vet_X0 If issuer address is blackholed already, you won't be able to unless you happen to have asfAllowTrustLineLocking (flag 17) set.
English
1
0
1
27
BuildX - $GRABS
BuildX - $GRABS@BuildXrp·
@Vet_X0 So this is a major bummer you cant do previously blackholed tokens
BuildX - $GRABS tweet media
English
1
0
0
145