MaxYel

@HugoPhilion Flare is now completely dependent on XRP. Hugo, did you build a slave for XRP or an innovative network? What have you turned FLARE into? Where is BTC, where are the other networks? Where is the real utility in the real world? Where is the oracle network?

Today I am thankful for the XRPL escrow feature 🙏 It is a key part of our design of FXRP.

No trust. Only proof. CYPHER anchored on Ethereum: TX:
0x966082221153de41c0fbc6e94c7f90b181aa3428987c1f008cdda5b5ce86e1a7 DATA:
CYPHER|7130c2c2e814f62dc1c70fcf36c4ca5ddaac5a70064f0b3de4dd022ed6d4ca95|MaxYel Immutable. Public. Verifiable. #Cypher #OnChain #Crypto #QmaxCypher

@Tabbakhh @HugoPhilion @FlareNetworks Bravo 🍾 0,0078 $ 🤡

Another day and the same address just minted ~1M FXRP. Just another Friday on @FlareNetworks ☀️

@MinusWells Ripple, SBI, Pantera, Kraken & Chris Larsen sold XRP, dropped the price. Then they gave me these dollars for XRPN. A simple pyramid. And all the idiots clap their hands. Bravo.👏

🚨 BREAKING: The "MicroStrategy of #XRP" is about to SHOCK the entire market… 😱 $1 BILLION+ war chest. Backed by Ripple, SBI, Pantera, Kraken & Chris Larsen himself. Nasdaq ticker XRPN incoming Q1 2026. Building the LARGEST public XRP treasury EVER, and actively growing it with lending + DeFi yield (not just sitting there like an ETF). Meanwhile FUD'ers still screaming "centralized" while Brad Garlinghouse drops truth bombs and institutions quietly stack billions in XRP rails. You still sleeping on $XRP at these levels? 😴 Or are you ready for the real supply shock that's coming? This isn't hype. This is legacy money choosing its side. RT if you're loading up before XRPN hits Nasdaq 🔥 #XRP #XRPN #Ripple

Now, the quantum resistance roadmap. Today, four things in Ethereum are quantum-vulnerable: * consensus-layer BLS signatures * data availability (KZG commitments+proofs) * EOA signatures (ECDSA) * Application-layer ZK proofs (KZG or groth16) We can tackle these step by step: ## Consensus-layer signatures Lean consensus includes fully replacing BLS signatures with hash-based signatures (some variant of Winternitz), and using STARKs to do aggregation. Before lean finality, we stand a good chance of getting the Lean available chain. This also involves hash-based signatures, but there are much fewer signatures (eg. 256-1024 per slot), so we do not need STARKs for aggregation. One important thing upstream of this is choosing the hash function. This may be "Ethereum's last hash function", so it's important to choose wisely. Conventional hashes are too slow, and the most aggressive forms of Poseidon have taken hits on their security analysis recently. Likely options are: * Poseidon2 plus extra rounds, potentially non-arithmetic layers (eg. Monolith) mixed in * Poseidon1 (the older version of Poseidon, not vulnerable to any of the recent attacks on Poseidon2, but 2x slower) * BLAKE3 or similar (take the most efficient conventional hash we know) ## Data availability Today, we rely pretty heavily on KZG for erasure coding. We could move to STARKs, but this has two problems: 1. If we want to do 2D DAS, then our current setup for this relies on the "linearity" property of KZG commitments; with STARKs we don't have that. However, our current thinking is that it should be sufficient given our scale targets to just max out 1D DAS (ie. PeerDAS). Ethereum is taking a more conservative posture, it's not trying to be a high-scale data layer for the world. 2. We need proofs that erasure coded blobs are correctly constructed. KZG does this "for free". STARKs can substitute, but a STARK is ... bigger than a blob. So you need recursive starks (though there's also alternative techniques, that have their own tradeoffs). This is okay, but the logistics of this get harder if you want to support distributed blob selection. Summary: it's manageable, but there's a lot of engineering work to do. ## EOA signatures Here, the answer is clear: we add native AA (see eips.ethereum.org/EIPS/eip-8141 ), so that we get first-class accounts that can use any signature algorithm. However, to make this work, we also need quantum-resistant signature algorithms to actually be viable. ECDSA signature verification costs 3000 gas. Quantum-resistant signatures are ... much much larger and heavier to verify. We know of quantum-resistant hash-based signatures that are in the ~200k gas range to verify. We also know of lattice-based quantum-resistant signatures. Today, these are extremely inefficient to verify. However, there is work on vectorized math precompiles, that let you perform operations (+, *, %, dot product, also NTT / butterfly permutations) that are at the core of lattice math, and also STARKs. This could greatly reduce the gas cost of lattice-based signatures to a similar range, and potentially go even lower. The long-term fix is protocol-layer recursive signature and proof aggregation, which could reduce these gas overheads to near-zero. ## Proofs Today, a ZK-SNARK costs ~300-500k gas. A quantum-resistant STARK is more like 10m gas. The latter is unacceptable for privacy protocols, L2s, and other users of proofs. The solution again is protocol-layer recursive signature and proof aggregation. So let's talk about what this is. In EIP-8141, transactions have the ability to include a "validation frame", during which signature verifications and similar operations are supposed to happen. Validation frames cannot access the outside world, they can only look at their calldata and return a value, and nothing else can look at their calldata. This is designed so that it's possible to replace any validation frame (and its calldata) with a STARK that verifies it (potentially a single STARK for all the validation frames in a block). This way, a block could "contain" a thousand validation frames, each of which contains either a 3 kB signature or even a 256 kB proof, but that 3-256 MB (and the computation needed to verify it) would never come onchain. Instead, it would all get replaced by a proof verifying that the computation is correct. Potentially, this proving does not even need to be done by the block builder. Instead, I envision that it happens at mempool layer: every 500ms, each node could pass along the new valid transactions that it has seen, along with a proof verifying that they are all valid (including having validation frames that match their stated effects). The overhead is static: only one proof per 500ms. Here's a post where I talk about this: ethresear.ch/t/recursive-st… firefly.social/post/farcaster…

@MinusWells @WietseWind x.com/maxyelq/status…

Listening to all the FUD swirling around $XRP wallets? I find it hilarious how the new kids on the block would side with anything but the dev legend Wind @WietseWind is straight-up the best #XRPL dev we have grinding today, building, shipping, securing. His masterpiece @XamanWallet has been the gold standard since 2021: 5+ years of flawless operation, zero hacks, endless upgrades, and actually listening to the community while others chase hype. Your wallet isn't some cute accessory... it's your North Star for retaining (and growing) your wealth through every market storm and scam wave. Me? I'd never deviate from Xaman. Not now, not ever🔒 Why gamble on shiny new toys when the proven king, built by a true legend, is still dominating? Stay smart. Stay Xaman 🍻 #XRP #XRPL #Xaman

@XamanWallet ❌When will you give a full report on all requests from your wallet to the external RPC that you use? ❌Where is the audit of data from users who pass through your nodes? ❌Users' IP addresses, how do you protect them? @XamanWallet

Self-Custody $XRP. Choose Freedom.

@Handy_4ndy ❌When will you give a full report on all requests from your wallet to the external RPC that you use? ❌Where is the audit of data from users who pass through your nodes? ❌Users' IP addresses, how do you protect them? @XamanWallet

Another thing that often falls under the radar is the #Xaman Revshare program, a porportion of said fee's are actually kicked back to the platform you initiated the transaction from... Enabling platforms to monitise through xaman integrations!

@XamanWallet @XRPLLabs ❌When will you give a full report on all requests from your wallet to the external RPC that you use? ❌Where is the audit of data from users who pass through your nodes? ❌Users' IP addresses, how do you protect them? @XamanWallet

We are sunsetting Xaman Pro. From Jan 30, 2026, Pro can no longer be purchased. Why? Xaman has evolved. We offer an exceptional product + real human support for everyone. If you bought Pro after Feb 1, 2025, it stays active 1 year from purchase. From @XRPLLabs: Thank you! 🙏

@XamanWallet ❌When will you give a full report on all requests from your wallet to the external RPC that you use? ❌Where is the audit of data from users who pass through your nodes? ❌Users' IP addresses, how do you protect them? @XamanWallet

We’re clearing the path for what comes next, more ways to use XRPL without splitting the experience into “basic” vs “premium”. On the roadmap: big DEX + AMM improvements, a new take on pathfinding for cheaper/smarter routing, and more. Read more: xaman.app/blog/pro

@monerify ❌Monero is unique only in the registry (blockchain) itself Monero. As soon as you connect your wallet and make a transaction, you are no longer anonymous. This is a feature of the Internet. So stop lying.❌

DO NOT BUY MONERO! some of you may have noticed this cryptocurrency all over your timeline while feeling confused as to why it is not listed in your favorite exchange (i know it's binance) when it's outperforming ever other asset in the planet earth year to date here's a lesson for all of you, monero is a privacy focused coin that you should stay as far away as possible from because upon obtaining it, it allows you to: - transact anonymously with other individuals (and avoid taxation (bad!)) - increase the value of your purchasing power in time against other assets (lame!) - have censorship resistant money to carry around with you (not good!) this coin is delisted from most exchanges for your own good please spread awareness and let others know to avoid this cryptographic currency as much as possible thank you for your attention to this matter

How will blockchains adapt to quantum computing? Circle Research explains how the industry is preparing for Q-Day. circle.com/blog/preparing…

@TrustWallet ❌There is no anonymity or privacy in your wallet. And also security.

Action required for users impacted by the Browser Extension v2.68 incident: We identified a limited group of ~36k wallets (0.016% of our user base) still having a compromised wallet(s). All impacted users have already been directly notified via a security incident banner on your Trust Wallet Browser Extension. In case the users haven't opened extension to see the banner, we also tried to notify them if the same wallet addresses have been imported to their mobile version, via: •a mobile app notification with action required notice •a pop up when you open the Trust Wallet mobile app If you have been notified, please abandon the old compromised wallet, create a new wallet and move your funds immediately to ensure your assets remain safe. Instruction below. If you have not received a notification, you are not affected and no action is required. Step-by-step guide: short.trustwallet.com/action-require… This applies to all wallets that used Trust Wallet Browser Extension version 2.68 between December 24-26, 2025.

❌The blockchain was not created for surveillance. ❌But it was observation that became his standard. ❌Under the banner of security, the industry has lost anonymity — and with it the chance to become a real alternative to the banking system.

Verifiable computation isn’t a blockchain breakthrough. It’s a cloud computing breakthrough that crypto accidentally incubated. Here’s why that matters.

@XamanWallet As you can see, the developers of @XamanWallet just wash their hands of it and don't want to be responsible for owning your data: IP addresses; MAC addresses; Other metadata. 🚩You have no privacy when using the Xaman wallet.

Self-custody is the only option. A third party doesn’t hold your assets, your transactions can't be paused, limited, or controlled by anyone else. You decide when and how you transact. That’s why self-custody matters, especially for $XRP. Be in charge, with @XamanWallet.

🚩Your data passes through many insecure nodes. 0 privacy. User → Ledger Device → Ledger Live → Ledger Sync → Ledger Servers → RPC Providers → Blockchain Nodes @Ledger @MetaMask @XamanWallet @BifrostWallet

@WietseWind @Kirjakulov @XRPLLabs @XamanWallet @WietseWind still didn't answer the main question - how do they delete data? IP addresses, headers, and request contents always appear in the server's memory. This is a lie: "Xaman is fully preserving privacy"

@Kirjakulov @MaxYelQ @XRPLLabs @XamanWallet Well you can, with -f

Warning! @XRPLLabs and @XamanWallet *do not* store your email address, IP address and we do not send you emails like this. If you receive an email like this, the sender is 🚨 fake, the site is 🚨 fake and the message is 🚨 scam! ⚠️ This NEVER comes from us. This is a SCAM!

@WietseWind @Kirjakulov @XRPLLabs @XamanWallet 🚩IP addresses, headers, and request contents always appear in the server's memory. Fact 🚩Logging audit has already been conducted? 🚩The “logless” reverse proxy mode is enabled? 🚩CF logging is disabled? 🚩the server is configured with "zero logs" at the kernel level?