WALLETAmbire Wallet

The upcoming xrpld v3.3.0 release is bringing five XRP Ledger amendments into focus, with changes aimed at tokenized assets , fee abstraction, permissioning, batching, and more flexible MPT functionality. XRP Ledger release materials say the release is scheduled for early August and includes Confidential MPT, Batch, Permission Delegation, Sponsored Fees and Reserves, and Dynamic MPT. As with other XRP Ledger amendments, activation requires 80% validator consensus. That last detail is important. A release does not mean every feature is automatically live. The code can ship, but amendments still need validator support before they activate on the network. So this is a major upgrade moment, but not an instant switch-on for institutional use cases. TL;DR xrpld v3.3.0 includes five amendments. Features include Confidential MPT, Batch, Permission Delegation, Sponsored Fees and Reserves, and Dynamic MPT. Activation requires 80% validator consensus. Why This Upgrade Matters XRP Ledger upgrades often matter more than the immediate market reaction suggests. The network’s long-term relevance depends on what developers, institutions, and wallet providers can actually build. New amendments can change user experience, compliance tooling, tokenized asset design, and transaction flow. The v3.3.0 bundle appears especially focused on making the ledger more flexible for advanced use cases. That includes tokenized assets, delegated permissions, batching, and fee sponsorship. These are not meme-market features. They are infrastructure features. For banks, issuers, wallet providers, and payment companies, that kind of functionality can matter more than short-term price action. Sponsored Fees Could Improve User Experience Sponsored Fees and Reserves may be one of the most user-facing amendments. In normal crypto UX, users often need to hold the native asset to pay fees or maintain reserves. That creates onboarding friction. A new user may want to interact with an app, but first needs XRP for network costs. Sponsored fee mechanisms can change that. If another party can cover fees or reserves, wallets and apps can create smoother onboarding. Users may interact with XRP Ledger applications without thinking about fee funding at every step. That can be especially useful for enterprise or consumer payment flows, where forcing users to understand native-token mechanics can be a barrier. Confidential MPT And Dynamic MPT Aim At Tokenized Assets Multi-Purpose Tokens, or MPTs, are part of XRPL’s tokenized asset direction. Confidential and dynamic features could help issuers create more flexible asset models, especially where privacy, permissioning, or changing asset behavior is important. That may matter for institutional tokenization. Banks and asset issuers often need controls that open, permissionless token systems do not provide by default. They may need transfer rules, confidentiality, compliance logic, or delegation structures. The v3.3.0 amendments appear to push XRPL further in that direction. But it is important not to overstate this. The presence of amendments does not guarantee banks will adopt them immediately. It simply gives builders more tools. Batch And Permission Delegation Add Operational Flexibility Batch transactions and permission delegation may sound technical, but they can improve how applications operate. Batching can make multi-step actions smoother, while permission delegation can reduce the need for constant direct signing from a primary account. Together, they can make XRPL apps more practical for users and institutions managing recurring or complex flows. That matters because blockchain usability is often limited by transaction friction. The more a network can simplify operations without weakening security, the easier it becomes to build applications that feel normal to users. Watch Validator Consensus The market should watch validator support rather than assuming immediate activation. XRPL’s amendment process is designed to require broad agreement before changes go live. That protects the network from rushed upgrades, but it also means features can take time to activate. For developers, the release is a signal to prepare. For users, the practical impact comes only once amendments pass the threshold and are enabled on the network. The v3.3.0 release gives XRPL a stronger roadmap for tokenization and UX upgrades. The next test is whether validators support the amendments and whether builders use them. This article is based on XRP Ledger xrpld v3 .3.0 release materials. This article was written by the News Desk and edited by Samuel Rae. This report is based on information released in disclosures at primary source documentation .

Ripple has unlocked 1 billion XRP from escrow for August, continuing the monthly release process that has long shaped XRP supply discussions. XRP Ledger escrow data shows the unlock took place on August 1, 2026, in three tranches. Historically, Ripple has often re-locked a large portion of the released XRP, commonly around 70%, into new long-term escrow contracts within the first week. That is the key point. A 1 billion XRP unlock sounds dramatic, but it does not mean all 1 billion tokens immediately enter active market circulation. Some may be re-locked. Some may be used for liquidity , institutional sales, ecosystem activity, or operational purposes. For XRP holders, the unlock matters because it is a predictable supply event. But predictable does not mean irrelevant. TL;DR Ripple unlocked 1 billion XRP from escrow on August 1. The release came in three tranches. Not all unlocked XRP necessarily enters market circulation. Why XRP Escrow Exists Ripple’s escrow system was designed to make XRP releases more predictable. Instead of leaving the market guessing about when large amounts of XRP might move, scheduled escrow releases create a visible monthly rhythm. That transparency helps, but it does not eliminate supply concerns. Every unlock still raises the same question: how much of the released XRP will actually become liquid? If Ripple re-locks most of the tokens, market impact may be limited. If more XRP remains available, traders may watch for sell-side pressure or distribution activity. That is why escrow tracking matters. It is less about the headline unlock and more about what happens after it. The Re-Lock Pattern Matters Ripple’s historical escrow practice points to a typical pattern where the company re-locks about 700 million XRP. That pattern has become part of how the market reads these events. Traders are not only watching the unlock itself, but also the subsequent escrow transactions. If the re-lock is in line with expectations, the market may treat the unlock as routine. If Ripple leaves more tokens liquid than usual, it may attract more attention. The monthly escrow cycle is therefore a supply-management signal. It is not automatically bullish or bearish. It depends on the details. Escrow Does Not Equal Immediate Selling This is where headlines can mislead. “Ripple unlocks 1 billion XRP” can sound like 1 billion XRP is about to hit exchanges . That is not necessarily true. Released tokens can be re-locked, held, allocated, or moved in ways that do not immediately create spot selling. That distinction matters because XRP is already a highly narrative-sensitive asset. Regulation, ETF speculation, Ripple partnerships, ledger upgrades, escrow movements, and whale activity can all affect sentiment. Overstating an escrow unlock can create unnecessary noise. The responsible read is that a scheduled supply event occurred, and traders should monitor the re-lock and subsequent wallet flows . XRP Supply Transparency Cuts Both Ways Ripple’s escrow system gives the market something to observe, which is better than opacity. But it also means every monthly release becomes a recurring debate. Supporters argue that the process is transparent and managed. Critics argue that large scheduled releases remain an overhang. Both views can exist at once. The escrow system reduces surprise, but the unlocked supply still matters. Predictability does not make supply irrelevant. For XRP holders, the August release is another routine but important checkpoint. What To Watch Next The next step is simple: follow the re-locks and wallet movements. If most of the unlocked XRP returns to escrow, the event will likely be treated as part of the normal monthly cycle. If more XRP remains liquid or moves toward exchanges, traders may pay closer attention. The unlock itself is not the whole story. The post-unlock handling is where the supply signal becomes clearer. This article is based on public XRP Ledger escrow data for Ripple’s August 2026 release . This article was written by the News Desk and edited by Samuel Rae. This report is based on information released in disclosures at primary source documentation .

XRP News XRP (XRP), the native altcoin of the XRP Ledger, is at the center of an infrastructure advisory after Ripple engineering director Vijay Khanna urged node operators on Aug. 2 to i

Price predictions for XRP often face immediate criticism because of the cryptocurrency’s implied market capitalization. According to crypto commentator and developer Bird, that reaction is based on a misunderstanding of how market capitalization works and how digital asset markets are valued over time. In a detailed tweet, Bird urged investors to focus less on today’s market cap figures and more on the XRP Ledger’s long-term growth potential if tokenization and institutional adoption continue to expand. Bird explained that market capitalization is calculated by multiplying the last traded price by the circulating supply. He emphasized that this figure does not represent the amount of money invested in an asset. Instead, prices are determined at the margin, meaning relatively small amounts of new capital can increase an asset’s overall valuation significantly. For that reason, Bird believes arguments that dismiss XRP price targets solely because of market capitalization overlook how financial markets function. People hear XRP to $100 or even $589 and immediately say, "The market cap would be impossible." I personally think that's one of the biggest misconceptions in crypto. Market cap is simply the last traded price multiplied by the circulating supply. It does not mean that amount… — Bird (@Bird_XRPL) July 31, 2026 Long-Term Value Depends on the XRP Ledger’s Growth Bird suggested that XRP should be evaluated based on what the XRP Ledger could become over the next five, ten, or twenty years rather than what it represents today. He described a future where trillions of dollars in tokenized real-world assets , including government bonds, corporate debt, equities, real estate, commodities, private credit, stablecoins, and money market funds, operate on-chain. He also pointed to the potential growth of RLUSD and other digital assets issued natively on the XRP Ledger. Combined with decentralized exchanges, automated market makers, institutional lending, AI-driven transactions, institutional and retail trading, and interconnected global liquidity pools, Bird believes the network could evolve into a major financial ecosystem rather than remaining a traditional cryptocurrency platform. According to Bird, if that transformation occurs, XRP would no longer derive its value solely from speculative trading. Instead, it would serve as the native asset supporting a large financial infrastructure used by institutions, businesses, developers, liquidity providers, and investors. Supply, Demand, and Liquidity Could Shape Future Prices Bird argued that the long-term value of XRP would ultimately depend on supply and demand. Since XRP has a finite supply, increasing participation from retail investors, financial institutions, corporations, exchange-traded funds, banks, and liquidity providers could create greater competition for available tokens. He added that not every XRP will remain actively available for purchase. Some holdings could become locked in liquidity pools, used as collateral, secured within ETFs, controlled by institutions, held by long-term investors, or permanently lost. As the liquid supply declines while demand grows, Bird believes market prices could naturally adjust higher. Bird also stressed that institutions require deep liquidity for large-value settlements. Higher XRP valuations, he argued, would allow each token to facilitate greater amounts of value, making the network more efficient for large-scale financial transactions. We are on X, follow us to connect with us :- @TimesTabloid1 — TimesTabloid (@TimesTabloid1) June 15, 2025 Institutional Adoption Remains the Key Requirement Although Bird expressed optimism about XRP’s long-term prospects, he acknowledged that achieving prices such as $100 or even $589 would require extraordinary progress. He stated that a $100 valuation would likely depend on widespread institutional adoption of the XRP Ledger, a tokenized asset market measured in trillions of dollars, continued growth of RLUSD and other on-chain assets, global regulatory clarity, deep liquidity, and tens of millions of XRP holders. Reaching $589, he added, would require an even higher level of adoption, with the XRP Ledger becoming one of the world’s dominant financial networks supporting tens of trillions of dollars in tokenized assets and economic activity alongside hundreds of millions of users. Bird clearly states that these outcomes are ambitious rather than guaranteed. However, he maintained that history has repeatedly shown how industries once viewed as unrealistic eventually became mainstream. For that reason, he believes it is more appropriate to assess XRP based on the long-term potential of the XRP Ledger instead of limiting expectations to its current role in the digital asset market. Disclaimer : This content is meant to inform and should not be considered financial advice. The views expressed in this article may include the author’s personal opinions and do not represent Times Tabloid’s opinion. Readers are advised to conduct thorough research before making any investment decisions. Any action taken by the reader is strictly at their own risk. Times Tabloid is not responsible for any financial losses. Follow us on X , Facebook , Telegram , and Google News The post XRP at $100 or $589? Here’s Why Market Cap Is Not A Limiting Factor appeared first on Times Tabloid .

The market is witnessing a substantial surge of activity, as XRP's payments volume surges above 1 billion.

On Jan. 10, 2026, a bitcoin and litecoin holder handed over their 12-word recovery phrase to someone posing as Trezor support and watched $282 million vanish in minutes, not because any encryption was broken, but because those 12 words are the entire wallet, and whoever holds them holds the funds. The Words Aren’t a Password.

The post XRP Ledger v3.3.0 Upgrade Adds Five New Features for Banks and Tokenized Assets appeared first on Coinpedia Fintech News The XRP Ledger is preparing for one of its biggest upgrades yet. RippleX will roll out xrpld v3.3.0 next week, introducing five new features focused on tokenized assets, privacy, and institutional finance. While the update is not yet live, it could make XRPL more attractive to banks and businesses using blockchain. XRPL Moves Closer to …

You flick a feature flag, restart your node, and suddenly blocks land faster than your logs can scroll. That was the vibe across a few Cosmos testnets the week the new release family dropped. Cosmos announced the "Cosmos Ledger" 2026.1 set with CometBFT v0.39, Cosmos SDK v0.54 (now shipping BlockSTM), and Cosmos EVM v0.7.0. In their own tests, they reported roughly 2,000 transactions per second sustained with sub-second blocks on a 5‑validator, 32‑CPU network when BlockSTM and Krakatoa were enabled Cosmos (cosmos.network blog) . This is not just another benchmark tweet. Parallel execution changes how you design modules, how you think about conflicts, and how validators size their hardware. It is a building-time decision, not a marketing line. Cosmos Ledger 2026.1 is a curated component set that says, in effect, here is a combination we validated together. The headline is BlockSTM landing in the SDK, but the context matters: CometBFT v0.39 and the Krakatoa path work alongside it, and Cosmos EVM v0.7.0 is part of the set. Builders who want multi-core gains and sub-second cadence now have a path that is official rather than experimental. Parallel execution is a capability, not a guarantee. Your state layout and transaction conflicts decide whether you see 2x or 7x. Who is affected? Pretty much everyone building or running a Cosmos appchain. Module developers need to think about access patterns. App teams need to plan migrations carefully. Validators will revisit CPU core counts and scheduler tuning. And EVM-style chains on Cosmos get a fresh reason to revisit mempool policies and fee markets. What BlockSTM Actually Does on Cosmos Optimistic concurrency, then conflict repair BlockSTM is a software transactional memory approach wired into the Cosmos SDK. The idea is simple to say and tricky to get right: execute many transactions speculatively in parallel, track which keys they read and write, then fix up any conflicts by re-running losers after the winners commit. It is optimistic concurrency for blocks. The SDK docs publish microbenchmarks that show real multi-core scaling. In a 10k transaction "no-conflict" workload, the peak speedup hits roughly 6.9x at 15 workers and about 6.6x at 10 workers. Even a worst-case, high-conflict workload shows around a 5x gain at 10 workers Cosmos SDK docs — Block‑STM (docs.cosmos.network) . That does not mean your chain will see those exact numbers, but it sets a ceiling that looks meaningful. Why Krakatoa shows up in the footnotes The Cosmos team’s 2k TPS claim explicitly called out BlockSTM plus Krakatoa on a 5-validator, 32-CPU rig Cosmos (cosmos.network blog) . You can read that as a reminder that parallel execution is only one part of the pipe. Proposer logic, mempool behavior, and consensus pacing all decide how much throughput you can actually feed into the executor. It is still deterministic All of this stays deterministic because the system resolves conflicts in a well-defined way. The order in the block plus the dependency graph guides validation and re-execution. When you cross-check on different machines, you land on the same state. Inside Cosmos Ledger 2026.1: Components and Defaults Cosmos Ledger 2026.1 is not a single binary. It is a release family, a validated set that slots together. Here is a quick snapshot of what is in scope: ComponentVersionRoleWhat to watchCosmos SDKv0.54State machine frameworkBlockSTM is available and opt-in; new execution runner and wiringCometBFTv0.39Consensus and networkingKrakatoa path referenced in tests; contributes to sub-second cadenceCosmos EVMv0.7.0EVM execution for Cosmos chainsValidated alongside the set; consider EVM state access patterns The Cosmos blog frames the sustained ~2,000 TPS number as a test outcome on a specific topology rather than a universal promise. That nuance matters and is worth repeating Cosmos (cosmos.network blog) . Parallel Execution in Practice: How to Turn It On In SDK v0.54, BlockSTM is opt-in. The wiring is not hard, but there are gotchas you need to respect. The docs call out specific configuration rules that materially affect migration Cosmos SDK docs — Block‑STM (docs.cosmos.network) : Set the block executor to BlockSTM. Config key looks like block-executor = "block-stm". If you wire this from code, use the provided helper such as SetBlockSTMTxRunner. Worker threads default to 0, which resolves to min(GOMAXPROCS, NumCPU). You can override with block-stm-workers if you want hard bounds. Enable pre-estimation. The flag is block-stm-pre-estimate and it should be true per docs. Disable the block gas meter. If the block gas meter stays on, the parallel runner will panic. Plan this change in your upgrade handler and clearly communicate it to downstream tooling. Re-validate your ABCI hooks and anything that expects single-threaded execution. Some modules might rely on implicit ordering. Make it explicit. Stage the rollout. Start on a devnet, then a canary testnet with production-like hardware before mainnet activation. Here is a simple example of what a config stanza may look like in practice. Your app’s file layout may differ, so treat this as conceptual, not a copy-paste: block-executor = "block-stm"block-stm-workers = 0block-stm-pre-estimate = true# ensure block gas metering is disabled in your app wiring Performance Reality: Where the 2k TPS Comes From The Cosmos team’s measured result, roughly 2,000 TPS with sub-second blocks on a 5-validator, 32-CPU rig, came from a setup tuned for parallelism with BlockSTM and Krakatoa enabled Cosmos (cosmos.network blog) . That gives us three takeaways. Throughput is workload-shaped If your transactions mostly touch separate parts of state, BlockSTM can scale. The SDK microbenchmarks show the ceiling: about 6.9x at 15 workers on no-conflict tests and around 5x even in worst-case conflict-heavy patterns Cosmos SDK docs — Block‑STM (docs.cosmos.network) . Real apps land somewhere in between. A DEX with a single busy pool will conflict more than an NFT marketplace minting to millions of unique accounts. Block time is not just execution Consensus pacing, network hops, and proposer behavior contribute to sub-second cadence. That is where CometBFT v0.39 and Krakatoa matter. They set the rhythm for how quickly you can finalize a block once the executor has done its part. Hardware sizing changes On a single-core world, faster CPUs win. In a multi-core executor, more cores and cache-friendly layouts win. Validators will probably revisit their core counts and NUMA layouts once they see real mainnet load patterns. What This Means for ATOM Builders and Appchains Design for concurrency from day one State key layout decides your parallel headroom. If you shard hot counters or avoid funneling every write through a single global store, BlockSTM has more space to work. Think in terms of per-user, per-pool, or per-market keys rather than one-size-fits-all accumulators. Cosmos EVM chains need to test access patterns Cosmos EVM v0.7.0 is in the validated set. Whether your EVM transactions parallelize well depends on how contracts touch storage. Heavy contention on the same contract slots will dampen gains, while broad, independent calls will benefit more. It is worth running realistic replay traces on your devnet to see where conflicts spike. Fee markets and mempool policy will evolve A parallel executor gives you room to prioritize different kinds of work. Chains might consider mempool lanes, hints, or fee multipliers that nudge low-conflict, high-throughput flows to the front, while not starving necessary but contentious operations. Module authors should sanitize assumptions If a module depended on implicit single-threaded ordering, make that ordering explicit. Document which store keys act as mutexes. Add tests that simulate conflicting writes and verify the outcomes. Migration playbook for teams Profile today’s workload. Sample real blocks, tag transactions by touched keys, and estimate conflict rates. Stage a testnet on SDK v0.54 + CometBFT v0.39 with BlockSTM toggled. Mirror hardware from mainnet validators. Replay captured traffic. Compare wall-clock block times and end-to-end latency with BlockSTM on and off. Iterate on key layout. If hotspots show up, restructure keys to reduce write contention. Formalize rollout gates. Only schedule mainnet switch once telemetry is clean and external indexers are ready for any changes. Tradeoffs, Tuning, and Things Nobody Mentions Telemetry noise goes up before it goes down When you parallelize, the logs look busier, and some operators interpret that as instability. Expect a period where you calibrate metrics, alert thresholds, and dashboards to the new execution path. Gas remains policy, but meters change Block gas metering must be disabled with BlockSTM, per the SDK docs Cosmos SDK docs — Block‑STM (docs.cosmos.network) . That does not mean fees vanish. It means you should revisit any assumptions where block-level gas budgets influenced throughput pacing. MEV dynamics shift Parallel execution does not erase MEV, but it can change the shape of search strategies. If conflicts decide which transactions get re-executed or delayed, ordering games will adapt. Keep an eye on proposer policies and auction mechanisms if your appchain runs one. Interchain effects Faster local finality can improve cross-chain latency for IBC flows, but only if both ends tune similarly. If one chain sprints and the other jogs, end-to-end latency remains bounded by the slower leg. Risks & What Could Go Wrong Hidden contention: A small number of hot keys can erase parallel gains and even increase variance. Incorrect wiring: Leaving the block gas meter enabled will panic the parallel runner and halt your node on activation. Module assumptions: Code that relied on implicit single-thread serial order may behave incorrectly under concurrency. Validator heterogeneity: Uneven hardware across the set can magnify proposer-vs-validator performance gaps. Operational complexity: More threads, more tuning. Misconfigured workers or scheduler parameters can underperform. Over-claiming performance: Marketing a lab number as a mainnet promise invites user frustration and trust hits. Activate BlockSTM only after you can show, with your own traces, that conflict rates are low enough to justify it on your chain. Frequently Asked Questions What is Cosmos Ledger 2026.1 in plain terms? It is a validated release family that pairs CometBFT v0.39, Cosmos SDK v0.54 with BlockSTM available, and Cosmos EVM v0.7.0. The Cosmos team published this set and shared test results showing roughly 2,000 TPS with sub-second blocks on a specific 5-validator, 32-CPU setup with BlockSTM and Krakatoa enabled Cosmos (cosmos.network blog) . Does BlockSTM change consensus or just execution? Just execution. CometBFT still handles consensus and networking. BlockSTM sits in the SDK’s execution layer, attempting to run many transactions in parallel, resolving conflicts deterministically before commit. How do I enable BlockSTM on my chain? Set the executor to block-stm or call the helper to install the BlockSTM runner, enable pre-estimation, choose a worker count or leave it at 0 to auto-size, and disable the block gas meter. The SDK docs emphasize the gas meter point because leaving it on will trigger a panic in the parallel runner Cosmos SDK docs — Block‑STM (docs.cosmos.network) . Will I get the 2,000 TPS number on my mainnet? Maybe, maybe not. That test ran on a 5-validator, 32-CPU lab with BlockSTM and Krakatoa enabled. Your throughput depends on workload conflicts, hardware, network conditions, and mempool policy. Use replay traces and profile first. What do the SDK microbenchmarks actually say? They report large gains for low-conflict loads, with peak speedup around 6.9x at 15 workers on a 10k no-conflict workload, and around 5x even in worst-case conflict-heavy tests at 10 workers. Treat these as ceilings, not promises Cosmos SDK docs — Block‑STM (docs.cosmos.network) . Is it safe to roll this into a live appchain today? It is in the validated set, which is encouraging, but stability still depends on your code and operations. Stage on a testnet, measure conflicts, and ensure downstream infra and explorers are ready. Parallel execution introduces new failure modes if miswired. How does this affect EVM-compatible Cosmos chains? Cosmos EVM v0.7.0 is part of the 2026.1 set. Whether you see big wins depends on storage access patterns across contracts. If your flow fans out across many keys, expect better scaling. If it bottlenecks on a few hot slots, gains will be modest. None of this is financial advice. Treat performance claims as starting points and verify on your own workloads. Disclaimer: This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial, or other advice.

BTC sentiment fell to a four-month low after Coldcard's $38M exploit.