StaticBit.io

📖 We wrote the entire text of War and Peace into XRPL mainnet. All 3,339,794 bytes of it, split across 3,278 transactions, in 15.3 minutes. Then we read it back out of the ledger and compared it to the original. Byte-for-byte match, SHA-256 verified. 💰 IT COST FOUR CENTS 0.039336 XRP total. Every transaction paid 12 drops, and not one paid more. XRPL's base fee does not scale with transaction size — Transactor::calculateBaseFee charges the same for an empty transaction and one carrying a full kilobyte of memo. Bytes are free. For 3.19 MB that full-history nodes will now keep forever, the network charged about four cents. That asymmetry is the whole experiment. 🔀 THE PART WE DID NOT EXPECT We rehearsed on testnet first. Mainnet was faster. ▸ Upload time: 20.84 min on testnet, 15.3 min on mainnet ▸ Ledgers consumed: 378 on testnet, 236 on mainnet ▸ Our share of a ledger, median: 90.9% on testnet, 8.3% on mainnet On an empty testnet we were the traffic — filling ledgers with ourselves, sometimes 100% of one. On mainnet the same 3,278 transactions dissolved into ordinary volume and rode along faster. The network never noticed. open_ledger_fee stayed at 10 drops throughout, the transaction queue stayed empty, and ledgers held a median of 171 transactions against an expected size of around 733. 📐 WHAT THE PROTOCOL ALLOWS ▸ Memo ceiling is 1024 bytes for the whole serialized Memos array (STTx.cpp:695, isMemoOkay). Useful payload: 1019 ▸ Adding an 11-byte MemoType tag pushes the transaction over the limit — it fails local checks ▸ In the ledger each transaction occupies 1323.1 bytes: 1172.5 blob plus 150.6 metadata, or 1.298x the payload ▸ The queue accepts at most 10 transactions per account (TxQ.h:165) ▸ A default node keeps the last 256 ledgers (Config.h:209). "Forever" only applies to full-history nodes 🗜 A COMPRESSION PARADOX bzip2 squeezes the Russian text 5.72x, so it would fit in 909 transactions and 0.009 XRP. But compressed bytes look like noise to RocksDB, which cannot compress them again — each stored byte then costs 1.5x more on disk. Net disk saving: 3.98x, not 5.72x. Plain text is the opposite: RocksDB compresses it almost exactly as much as transaction overhead inflates it, landing at 1.048x. 📚 WE WERE PREDICTED In XRPL-Standards discussion #103, someone wrote that memo examples would "land us in episode 143 of the 'I'll put my files on ledger in chunks' discussion" and that "sane people know this is a bad idea." We are that episode. We just measured it. This lands two weeks after the community argued over whether the memo limit should be raised at all — one side holding that paying the fee should buy you the space, the other that every node stores it forever. Nobody put a number on it. Here is one: at today's limit, 1 GB works out to 1.05 million transactions and 12.64 XRP. ⚙️ Worth knowing: XRPL already has a per-byte fee, it is just not used for memos. An EscrowFinish carrying a fulfillment costs 330 drops plus 10 drops for every 16 bytes of the preimage. The mechanism exists. Memos simply do not use it. 🔗 Read any chapter, assembled live from the ledger: staticbit-io.github.io/war-a… Code and dataset: github.com/StaticBit-io/war-… The site stores no copy of the book. Every character is fetched from transaction memos at read time and SHA-256 checked before display. Account: rU1A1kuVpYHk3TZYWJxVtPUc94aXyteizy — its entire history is the novel. #XRPL #XRP #Tolstoy

Apple sucks—we were hosted on their platform for a year and a half, then two months ago they removed our app, and now their support team won’t respond.

💯

It was true, before Batch on mainnet. 😄😄😄 @daniel_wwf

We support everything on the XRPL, including things that haven't even launched on mainnet yet - but I understand what you're talking about.

no problem with WalletConnect. Well, more precisely, of course, there are problems, but you need to understand what to do. We sent 4 PRs to their repository, conducted 300+ hours of testing to make it convenient for our users

based on @xrpl_commons

I'm trying to understand why everyone limits the way they connect, Joey uses WalletConnect, but not only it, there are others in the ecosystem, but they don't know that they can connect. Why not just specify WalletConnect?

3⃣ LP tokens are votes on the fee (0–1%, weighted). Not guaranteed income: if prices move and stay, the loss can exceed the fees. xrpl.org/docs/concepts/token…

2⃣ Fees accrue inside every trade: they stay in the pool, nothing is paid out. 20 trades later the pool held 151.76 XRP for the same 150,000 LP. AMMWithdraw (tfWithdrawAll) returns your share, fees included. 👇👇

1⃣ Deposit both assets in the pool's proportion and you get LP tokens, a share of the pool. On a test ledger: 100 + 100 gave 100,000 LP; a second provider's 50 + 50 gave 50,000. No fee for a two-asset deposit. 👇👇👇

as long as everyone migrates CSC remains one of the most profitable pools)

12 wallets sent the same Batch into one XRP Ledger ledger. One got the trade, and the fee had nothing to do with it. 3.5 minutes on canonical order, open ledger escalation and why Batch swarms fill the cheap part of each ledger. On a test ledger. @XRPLF #XRPEducationMonth

soon will only RLUSD, without xrp

withdraw from a vault

fixCleanup3_6_0 #XRPLedger

XRP - intergalactic asset, it doesn't care about anything.

🤣

brazil first