XRPLF / rippled

Decentralized cryptocurrency blockchain daemon implementing the XRP Ledger protocol in C++
https://xrpl.org
ISC License
4.5k stars 1.46k forks source link

Support the escrow feature for issued tokens #4106

Closed wojake closed 2 years ago

wojake commented 2 years ago

Currently, rippled only supports the escrow feature for XRP. This is much appreciated by the ecosystem but the XRP Ledger will benefit tremendously from an escrow feature for issued tokens as there are multiple use cases and benefits of supporting them at a protocol-layer, there are also much more use cases for it when the Hooks amendment is rolled out. It is possible to implement an escrow feature on a Hook but implementing an escrow feature at a protocol-layer allows us to set a standard and it is much more reliable & secure. It also saves the XRPL's validator's resources as they wouldn't be needing to compute spaghetti code from Hooks that want implement an escrow feature for tokens <- if hooks are implemented

Issued tokens = currencies, tokens, NFTs, IOUs

As expected, the XRP Ledger has increased in terms of usage and development which excludes the utility of XRP alone, multiple tokens and currencies (soon NFTs) has been issued on the mainnet behind projects, stablecoin issuance, tools and Ripple has also been advocating to support CBDCs on the XRPL for quite some time. To increase the use case and the reliability of issued tokens on the XRPL, it's best to introduce the native escrow feature for issued tokens.

Benefits:

I'm involving Hooks into the proposal as Hooks can support an escrow feature for issued tokens. If NFTs are being introduced at a protocol-layer, I think this feature should be introduced in the same manner as funds are involved.

wojake commented 2 years ago

https://github.com/XRPLF/XRPL-Standards/discussions/72

KarmaCoverage commented 2 months ago

Hey wojake, How did this come out?