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

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

For XRP holders it means more utility - idle XRP can potentially earn yield through lending, and the whole XRPL gets a real DeFi primitive for credit.

zero trades

We’re not waiting for the amendments to start building. Deposit to vault → see shares before signing Pay loan → schedule + full amount shown before confirmation All of this is already in StaticBit (DevNet). Mainnet just needs the green light from validators. #XRPL #lending #protocol #amendments

Kitchen’s ready. Vaults + Loans flows in StaticBit are fully cooked - deposit, shares, payment schedule, LoanPay. All live on DevNet. As soon as the amendments hit 80% and activate, the same UI just turns on for mainnet. No app update needed. Let’s cook. 👨‍🍳

lacks the ability to log in through WalletConnect ☹️

we have x402 for xrpl .Net devs github.com/StaticBit-io/Xrpl…

Happy Diwali, Mayukha tell us more about how you celebrate this holiday.

We are ready for lending protocol

StaticBit 2.6 is ready for XRPL vaults and the Lending Protocol. The Vaults, Loan Brokers and Loans screens are in the app. They show your positions, and before you sign you see what you receive and what you give. The SingleAssetVault and LendingProtocol amendments are not enabled on mainnet as of Nov 8, so the section is empty there for now. It works on DevNet. Also in 2.6: - Account import by private key: Add new wallet, Import account, Private key. It accepts 64 hex characters, or 66 with a 00 prefix (secp256k1) or ED prefix (ed25519). - Every Features card on the home screen opens: 20 ledger object types, including Checks, NFTs, Escrow, MPTs, Credentials, DIDs and Permissioned Domains. View only. - Max network fee in settings: a cap on the automatic fee, 0.01 XRP by default. If you back up a wallet added by private key, restore the backup on 2.6 or newer: version 2.5 does not read that key type. iOS: the update isn't available yet, we're working it out with Apple. Get it: Google Play play.google.com/store/apps/d… #StaticBit #XRPL #Ripple #XRPLCommunity

Links to metadata die 🪦 When an NFT, an MPT, a DID or a credential keeps its picture and description off the ledger, the ledger entry holds only a link. The file sits on IPFS, on the issuer’s own server or in an S3 bucket. Part of the projects on XRPL no longer maintain their storages, images and metadata nft live only with marketplaces who downloaded them and store them in their storages. 🪦🪦🪦

Backup in StaticBit: Settings, Security, Backup. Save it as a password-protected file or QR code, check it there, and keep a copy off this phone. No app at hand? The decoder on GitHub opens a backup: staticbit-io.github.io/walle…. You need the password you set when making it, and it can't be recovered. #StaticBit #XRPL