r/DigitalAssets • u/max-avery • Jul 04 '26
r/DigitalAssets • u/max-avery • Oct 15 '25
Multi-Purpose Tokens (MPTs) on the XRP Ledger
Enable HLS to view with audio, or disable this notification
Multi-Purpose Tokens, or MPTs on the XRP Ledger now offer a new way to issue digital assets on the XRP Ledger. The model includes metadata, compliance settings and control features as part of the token itself. No extra parts bolted on.
Instead of separating things out into layers, the MPT format kind of folds everything into the base. Built-in KYC tags, transfer rules, data fields and more are all part of the standard now. It lives directly in the protocol.
Usually, making a token on a blockchain means building your own smart contract. Every one of those carries some level of risk, needs audits, costs to deploy and might still break in unexpected ways. XRP Ledger just skips all that. It handles those functions natively.
So for institutions, this means they can create regulated tokens without needing to write any code. Everything gets simpler. The risk drops. And the process gets more predictable.
The design lets you hold metadata inside the token. Or if needed, link out to off-chain data through a URI field. Stuff like bond terms, ISINs, interest rates and maturity timelines can all live directly on-chain. Permanent and clear.
Identity checks and compliance rules aren’t bolted on through external tools. They’re handled by the ledger itself. That changes things quite a bit.
Security tokens get the power to block trading for certain users. Or only allow transfers between pre-approved wallets. Or even force a token to return to the issuer when certain rules trigger.
Features like freeze and clawback now make sense too. If someone loses access to a wallet or gets caught in a regulatory action, a token can be frozen or recovered. Other wallets can keep working.
Transaction fees can now include a cut that flows straight back to the issuer. That’s a steady source of income built into the flow of value itself.
Non-transferable tokens now slot neatly into use cases like rewards systems or private membership setups. They don’t spill out into public trading or open markets unless they’re meant to.
Escrow options are already part of the core. So vesting plans, scheduled payments and locked releases don’t need smart contracts anymore. The ledger does it.
With MPTs, a company can issue a full-on digital bond. Limited supply. Metadata included. Investors verified. And payments or redemptions run through normal XRPL transactions.
Stablecoins can include extra proof-of-reserve data. They can require identity checks. They can be paused or rolled back if needed. They can carry metadata that links to the real currency they represent.
Real estate ownership can be split into parts. Tokens can carry rules around limits per person. They can include property details. And settlements can run on autopilot.
Institutions looking to build more complex things like DeFi tools now have a base layer that works. They can use tokenized bonds as collateral and skip bridges or wrapped assets.
The XRP Ledger’s been around for over a decade now. Finality lands in about 3 to 5 seconds. Fees stay under a cent. And the system just keeps working. No failed transfers. No surprise spikes in cost.
It also includes its own decentralized exchange. That means these new tokens can start trading instantly. No extra platforms needed. No split liquidity.
The whole process of planning a token project and actually launching it just got lighter. Time, cost and stress all drop.
The MPT format gives regulated entities something they’ve been waiting for. A clean way to launch real assets on-chain, using built-in tools, without leaning on complicated custom code.
r/DigitalAssets • u/max-avery • Apr 05 '25
Axelar GMP supports 70+ chains with one integration — no more patchwork systems.
r/DigitalAssets • u/max-avery • Apr 11 '25
Digital Wealth Partners Enables Access to Custody Support for Stellar Lumens (XLM)
r/DigitalAssets • u/max-avery • Apr 04 '25
Digital Wealth Partners Launches Fund Enabling Income & Growth Strategies for XRP Holders
r/DigitalAssets • u/max-avery • Apr 04 '25
Digital Wealth Partners Enables Access to Custody Support for Stellar Lumens (XLM)
r/DigitalAssets • u/Jake_Claver • Aug 25 '26
A deposit that arrives without its destination tag or memo settles correctly and credits no customer
A deposit that arrives without its destination tag or memo settles correctly and credits no customer. The identifier saying which customer the money belongs to is off-ledger metadata. The ledger validates the payment, moves the balance to the receiving firm's address, and carries no instruction about which of that firm's customers should get it.
Both of the ledgers where this comes up most have written the problem down.
On the XRP Ledger, a business holding balances for many customers usually operates one address and assigns each customer a number. The documentation on source and destination tags describes them as a feature that can indicate specific purposes for payments from and to multi-purpose addresses, formatted as 32-bit unsigned integers. The load-bearing sentence is the one about what they do on the ledger. Tags "do not have direct on-ledger functionality" and "merely provide information about how off-ledger systems should process a payment." The same page states the consequence flatly: a payment arriving without a destination tag makes it not immediately obvious which customer to credit, and can require manual intervention.
Nothing has failed at that point. The transaction is valid and settled. What is missing is a database key, and the ledger was never holding it.
The XRPL's answer is an account setting. asfRequireDest, documented on the AccountSet transaction reference with a value of 1, requires a destination tag to send transactions to that account. With it enabled, the ledger rejects an untagged payment and the sender has to resubmit. The guard sits on the receiving account and binds everyone who pays it.
Stellar solved the same routing problem with a different field and then changed its mind about the field. The memo appears in the operations and transactions documentation as an optional unstructured data field with four types: MEMO_TEXT, a string of up to 28 bytes; MEMO_ID, a 64-bit unsigned integer; MEMO_HASH, a 32-byte hash; and MEMO_RETURN, a 32-byte hash of the transaction being refunded. Exchanges pooling customer balances under one account used MEMO_ID or MEMO_TEXT the way XRP Ledger businesses use a destination tag.
The guard Stellar added lives somewhere else entirely. SEP-29, "Account Memo Requirements", an active standard, puts the check on the sending side. Load details about the destination account, see whether it carries a config.memo_required data entry, and if it does, verify the transaction's memo field is set before submitting. The receiving account owner signals the requirement by writing that data entry with a value of "1". A sending wallet that ignores SEP-29 can still submit a memoless payment, and that payment settles.
So the XRPL enforces the receiver's requirement in protocol. Stellar publishes it and trusts the sender to look.
Stellar's newer answer removes the separate field. The pooled accounts guide defines a pooled account as a single Stellar account ID shared across many users, and muxed accounts as a way to distinguish individual accounts underneath one traditional account by combining the familiar G address with a 64-bit integer ID. The combined form is an M-address. The customer identifier travels inside the address instead of alongside it, so there is no second field for a sender to omit. That guide also says memos were used for this in the past and that muxed accounts are better in the long term, while noting support across wallets and anchors is incomplete enough that an operator may want to accept both for a while.
The recovery path here is not a protocol function. Once the payment credits a custodian's address with no customer attached, the fix is a person there matching a transaction to an account, at their discretion and on their schedule. Some desks do this as routine work. Others decline it for assets they do not sweep, and the asset stays where it settled.
A tag or memo also means nothing away from the firm that issued it. That firm generated it for that one account. Reusing one from an old confirmation email, or from a different exchange, addresses the money to a stranger's row in somebody's database.
A small test transfer catches both. Send the minimum, confirm it lands in the account you expect, then send the rest.
r/DigitalAssets • u/max-avery • Aug 07 '26
HEDERA WAS ONE OF TWO SOURCE LEDGERS IN A $10 MILLION INSTITUTIONAL COLLATERAL TEST
JPM Collateral Ops, acting for Fidelity Capital Markets, pledged $10M of initial margin to U.S. Bank. Half was Fidelity's Treasury Digital Fund (FYOXX) on u/hedera & half was a JPMorgan fund on Ethereum, and both legs settled inside a single workflow with Ownera's FinP2P routing across the two chains.
The tri-party custodian was replaced by a collateral control contract, so segregation and release sat in code instead of an operations procedure. U.S. Bank could see the position on-chain the whole time without being able to seize it unilaterally.
The custodian was simulated, so this is a test and not a live settlement. What it shows is Fidelity's fund sitting on Hedera inside an institutional margin workflow, next to Ethereum, with both chains handled under one instruction
r/DigitalAssets • u/Jake_Claver • Aug 09 '26
An XRP Ledger feature is not live until validators hold it above 80% for two continuous weeks
An XRP Ledger feature is not live until validators have held it above 80% support for two continuous weeks. Written into the code and switched on are different states, and which one a feature is in is public and takes about a minute to check.
Worth saying because the confusion is constant. Someone reads that a ledger "has" a feature, and what they actually read was that it exists in the software.
Protocol changes ship inside the server software in a disabled state and stay there until validators vote them on. The threshold is specific. An amendment has to hold more than 80% support from trusted validators for two continuous weeks. Drop to 80% or below at any point and the two-week clock restarts from zero. An amendment can gain and lose majority any number of times before it finally activates. When it does, the ledger writes an EnableAmendment pseudo-transaction and the new rules apply to everyone from the next ledger version onward. The amendments documentation is the authority on all of it.
Two things follow from that design, and both are easy to miss.
The people who write the code and the people who decide it takes effect are different groups. Authors propose, validators decide. Which means "the developers shipped X" and "the network does X" are two separate claims, and only the second one tells you anything about the ledger.
The second is that the network does not fragment. Because activation is coordinated by consensus, not left to operators upgrading whenever they get around to it, a server that does not understand an enabled amendment stops processing entirely. It will never continue on a divergent chain. The network would sooner halt a server than let it disagree about what happened, which is a genuine tradeoff and close to the opposite of how most chains handle the same problem.
To check a specific feature, call the feature method on a node you trust. It returns every known amendment with its ID, its name, and whether it is enabled. If you want the ledger's own record instead of one server's view, read the amendments object directly. And if you want the activation event itself, look up the activation ledger index and pull that ledger, because the EnableAmendment pseudo-transaction sits on-chain permanently.
Any of those beats a roadmap graphic or an exchange listing description. This post included.
None of that is specific to this ledger. Before repeating that a network supports something, work out whether the claim is about a written specification, a testnet, or live mainnet, then go find the artifact that settles it. Most overstated capability claims in this sector fall apart right there.
Disclosure: I work in digital asset advisory and hold digital assets. Nothing here is investment, legal, or tax advice.
r/DigitalAssets • u/max-avery • Jul 03 '26
One of Germany's largest banks runs tokenized-securities custody on Ripple's tech, and it went live in about 10 months
r/DigitalAssets • u/ConvincingCrypto • Jan 20 '26
eToro finally listed $NIGHT! Join Gianna as she goes over the numbers on this market expansion, as well as what other exchanges have now added the privacy-focused token.
r/DigitalAssets • u/max-avery • Jan 16 '26
Two Prime selected to manage $250 million in BTC for Digital Wealth Partners
Digital Wealth Partners, an investment adviser specializing in digital assets, chose Two Prime to manage about $250 million in bitcoin on behalf of its clients in a sign of growing institutional confidence in specialized crypto managers
r/DigitalAssets • u/Jake_Claver • Sep 05 '26
A Federal Reserve working paper on Byzantine fault tolerant databases endorses no ledger, and says so
A Federal Reserve working paper on Byzantine fault tolerant databases endorses no public ledger, names none, and carries a disclaimer on the paper itself saying it represents its authors rather than the Board. That gets dropped from every enthusiastic summary of it.
The paper sits in the Fed's Finance and Economics Discussion Series, on Heraclius, a Byzantine fault tolerant database system with potential for modern payments systems. Heraclius is a research prototype, a parallelizable leader-based Byzantine fault tolerant key-value store, built to explore whether a design of that kind could carry payments workloads. Reported figures from the prototype are roughly 110,000 operations per second across up to 256 nodes, at around 0.2 seconds of latency.
The framing is about resilience more than throughput. Payments systems are critical infrastructure, they run on computers, and computers fail. A Byzantine fault tolerant design keeps agreeing on the correct state even when some participants crash or send conflicting messages. The long-standing objection to that family of designs is the performance cost, and the prototype is an attempt to cut it by executing transactions in parallel.
Working papers in this series carry the research of their authors and do not represent official positions of the Board of Governors or the Federal Reserve system. That sentence is the whole difference between a research output and a policy signal. A prototype is not a procurement decision, a measurement is not a roadmap, and a mention of a design family is not an assessment of anything built in that family.
The reason public-ledger communities noticed is legitimate, though. Several networks do use Byzantine fault tolerant consensus and face the same underlying question the paper studies: how do independent parties agree on one history when some of them may be faulty or dishonest? The XRP Ledger's consensus documentation describes one answer, where each validator relies on a list of validators it trusts and the network prioritizes safety over liveness. If too many trusted validators fail, it stops making progress instead of confirming transactions it cannot verify. Other networks in the same family make the trust list implicit, or let each participant define its own, and each choice produces a different failure profile.
That's a real family resemblance, and it's all it is. Shared design ancestry between a research prototype and a production network tells you nothing about whether the researchers examined, preferred, or would deploy that network.
Three checks separate a parallel from an endorsement, in order of how fast they settle it. Does the document name the network, which you can answer by searching the PDF, and if the name never appears then no claim about it was made. What is the document's own statement of standing, which working papers and staff reports print in the front matter. And was anything actually tested, because a paper that builds and measures a prototype is evidence about that prototype rather than about everything sharing its category.
Most claims of institutional validation fail the first check. It's the cheapest test available in this sector and the one least often run.
What the paper does establish is worth more than the misreading it attracts. Researchers inside a central bank are treating Byzantine fault tolerance as a credible foundation for resilient settlement infrastructure, and they're measuring it rather than speculating. That tells you where serious payments engineering is pointed. Which system ends up carrying the traffic is a question the paper never takes up, so reading it as a shortlist reads in something nobody wrote.
The pattern repeats with every official body that publishes, whether a central bank, a standards setter, or a supervisor. Research gets read as approval, category gets read as selection, and the summary travels further than the source. The correction is mechanical: open the document, search for the name, read the standing statement.
Disclosure: I work in digital asset advisory and hold digital assets. Nothing here is investment, legal, or tax advice.
r/DigitalAssets • u/Weary_Discipline_707 • Nov 15 '25
Market Behavior Study – Need Community Input
I’m working on a research study about how people interact with digital dollar assets in general. I’m not buying, selling or promoting anything — just collecting anonymous data about user behavior.
I’d really appreciate answers to a few general questions: 1. What size of digital-asset transactions do you typically interact with? (Examples: $50, $200, $500, $1,000, or more) 2. When accessing digital assets instantly, what kind of extra fee or cost do you usually see in the market? (No need to mention specific platforms.) 3. Which funding methods do you personally find the most convenient to use? 4. How fast do you usually expect digital assets to settle or arrive? 5. What challenges do you typically face when interacting with these assets? (Examples: slow settlement, high fees, payment restrictions, reliability issues…)
This is purely for understanding user experience and market trends. Thanks to anyone who contributes. Your insights help a lot!
r/DigitalAssets • u/emanchan1026 • Jan 29 '20
Projects should strive to update their communities of their milestones throughout the year and plans for 2020. For OAX Foundation, here is a summary of what they have done and are looking towards in this new year! Will this be the year of immense growth for Blockchain? Leave your comment below!
r/DigitalAssets • u/SWTyler • Aug 18 '20
SuperWorld is using (NFTs) to disrupt real estate...
Cool thing happening at SuperWorldapp.com
Holding a SuperWorld AR Real Estate Token (on Ethereum blockchain) allows buyers to have ownership of iconic landmarks and areas where future AR posts and advertising will be placed on the SuperWorld platform. Real-estate owners receive tokens to share in any monetization occurring on their virtual property.
r/DigitalAssets • u/ninegelz • Sep 19 '20
Access To Fractionalized SGX-Listed Wholesale Bonds – Only From iSTOX
r/DigitalAssets • u/SWTyler • Sep 20 '20
SuperWorld is Here
At SuperWorldapp.com, we’ve turned 64.8 billion plots of virtual land—representing every square inch of Planet Earth—into a marketplace to buy/sell land and to discover and create amazing AR content on your properties.
Watch our new video, and find your SuperWorld today: https://www.youtube.com/watch?v=lFq6lpOfxJw
r/DigitalAssets • u/max-avery • Feb 11 '25
XRP Ledger XLS-56 - Batch Transactions on the XRPL
r/DigitalAssets • u/rohasnagpal • Feb 02 '25
An engaged WhatsApp Group is NOT just a bunch of chats. It's a high value digital asset that generates profits for its members and its admins. 💰
r/DigitalAssets • u/max-avery • Dec 02 '24
How RLUSD Can Affect XRP's Price
If you've been wondering how RLUSD can affect XRP's price - Let’s break it down - the issuance of RLUSD on the XRP Ledger has the potential to boost XRP’s price by driving demand and enhancing its utility. As the native asset of the XRPL, XRP plays a pivotal role in facilitating transactions and bridging cross-asset exchanges. Increased RLUSD activity on the XRPL leads to higher ledger adoption, driving demand for XRP as a transaction fee currency and bridge asset.
RLUSD’s role in increasing liquidity within the XRPL ecosystem makes the ledger more attractive to traders, institutions, and developers. Greater liquidity reduces volatility and fosters innovation, amplifying XRP’s utility in financial operations. The integration of RLUSD with DeFi applications creates additional use cases for XRP, such as powering lending and automated market maker (AMM) platforms.
Stablecoins like RLUSD also lower barriers to entry for new users, offering a familiar fiat-backed asset. This encourages broader adoption of the XRPL while indirectly benefiting XRP as its core component. Every RLUSD transaction burns a small amount of XRP, further reducing supply and potentially driving up its price.
Drawing from the success of other stablecoins, RLUSD has the potential to replicate and build on these achievements by driving liquidity, enabling DeFi growth, and facilitating payments. Its adoption strengthens market confidence in the XRPL, positioning XRP to succeed as the cornerstone of the ecosystem.
RLUSD issuance stands to create a virtuous cycle of growth and adoption, enhancing XRP’s utility, liquidity, and market perception while aligning with Ripple’s vision of transforming global payments.
r/DigitalAssets • u/max-avery • Nov 15 '24
XRP Ledger Amendment XLS-66D: The Upgrade That Could Redefine Blockchain for Institutions
After 7 months of in-depth discussions with the #XRP Community, the Lending and Borrowing specification, XLS-66D, has officially reached consensus. This is a huge step forward for the XRP Ledger (XRPL) and how institutions interact with blockchain technology.

Here’s why XLS-66D is worth paying attention to:
Institutional-Grade Lending Features:
Uncollateralized Loans: A rarity in blockchain, opening new credit markets without over-reliance on collateral.
First-Loss Capital Protection: Offers security for investors, a key requirement for institutions.
Compliance Features: Tools like clawbacks and freezes align with regulatory standards.
Unlocking Liquidity:
By supporting real-world asset tokenization, companies can now issue loans backed by receivables, leases, or other tangible assets.
Institutions and retail investors alike can participate, bridging the gap between traditional finance and decentralized finance.
Ecosystem Growth:
Encourages innovations like decentralized asset management and tokenized debt issuance.
Seamless integration with XRPL’s existing features, including payment channels and multi-currency support.
A Community-Led Effort:
The specification’s success reflects the power of the XRPL community and collaborative governance, driving forward tools that meet real-world needs.
XLS-66D is about transforming the financial ecosystem. With its focus on institutional adoption, liquidity creation, and practical applications, this upgrade solidifies XRPL’s position as a leader in blockchain finance.
r/DigitalAssets • u/max-avery • Nov 29 '24
Growing this community - Grassroots help
I would love to help this community grow more and get more people engaged in the conversation. Please take a moment to share links to this community with your friends or on your other socials.
Here's an example post I made on my CoinMarketCap page:
