Skip to content

XLS-0065d Single Asset Vault#239

Merged
sappenin merged 21 commits intoXRPLF:masterfrom
Tapanito:xls-65-single-asset-vault
Feb 28, 2025
Merged

XLS-0065d Single Asset Vault#239
sappenin merged 21 commits intoXRPLF:masterfrom
Tapanito:xls-65-single-asset-vault

Conversation

@Tapanito
Copy link
Copy Markdown
Collaborator

Discussion thread can be found here: #192
Development branch can be found here: rippled/vault

Copy link
Copy Markdown
Contributor

@thejohnfreeman thejohnfreeman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Really liking the new state of the spec. Great work!

Co-authored-by: tequ <git@tequ.dev>
@Bronek Bronek mentioned this pull request Dec 17, 2024
13 tasks
@Tapanito
Copy link
Copy Markdown
Collaborator Author

All comments addressed, ready to merge.

@sappenin sappenin merged commit eed3662 into XRPLF:master Feb 28, 2025
bthomee pushed a commit to XRPLF/rippled that referenced this pull request May 20, 2025
- Specification: XRPLF/XRPL-Standards#239
- Amendment: `SingleAssetVault`
- Implements a vault feature used to store a fungible asset (XRP, IOU, or MPT, but not NFT) and to receive shares in the vault (an MPT) in exchange.
- A vault can be private or public.
- A private vault can use permissioned domains, subject to the `PermissionedDomains` amendment.
- Shares can be exchanged back into asset with `VaultWithdraw`.
- Permissions on the asset in the vault are transitively applied on shares in the vault.
- Issuer of the asset in the vault can clawback with `VaultClawback`.
- Extended `MPTokenIssuance` with `DomainID`, used by the permissioned domain on the vault shares.

Co-authored-by: John Freeman <jfreeman08@gmail.com>
tequdev pushed a commit to Xahau/xahaud that referenced this pull request Mar 3, 2026
- Specification: XRPLF/XRPL-Standards#239
- Amendment: `SingleAssetVault`
- Implements a vault feature used to store a fungible asset (XRP, IOU, or MPT, but not NFT) and to receive shares in the vault (an MPT) in exchange.
- A vault can be private or public.
- A private vault can use permissioned domains, subject to the `PermissionedDomains` amendment.
- Shares can be exchanged back into asset with `VaultWithdraw`.
- Permissions on the asset in the vault are transitively applied on shares in the vault.
- Issuer of the asset in the vault can clawback with `VaultClawback`.
- Extended `MPTokenIssuance` with `DomainID`, used by the permissioned domain on the vault shares.

Co-authored-by: John Freeman <jfreeman08@gmail.com>
tequdev pushed a commit to Xahau/xahaud that referenced this pull request Mar 5, 2026
- Specification: XRPLF/XRPL-Standards#239
- Amendment: `SingleAssetVault`
- Implements a vault feature used to store a fungible asset (XRP, IOU, or MPT, but not NFT) and to receive shares in the vault (an MPT) in exchange.
- A vault can be private or public.
- A private vault can use permissioned domains, subject to the `PermissionedDomains` amendment.
- Shares can be exchanged back into asset with `VaultWithdraw`.
- Permissions on the asset in the vault are transitively applied on shares in the vault.
- Issuer of the asset in the vault can clawback with `VaultClawback`.
- Extended `MPTokenIssuance` with `DomainID`, used by the permissioned domain on the vault shares.

Co-authored-by: John Freeman <jfreeman08@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants