ARCHIVE/xrpl-dev-portal
1
0
Fork 0
mirror of https://github.com/XRPLF/xrpl-dev-portal.git synced 2025-11-28 07:35:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update/remove legacy links

Browse Source
This commit is contained in:
mDuo13
2025-05-08 17:01:48 -07:00
parent cd44b8e1d5
commit 4ba07466e1
101 changed files with 628 additions and 612 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
blog/2019/multisignreserve-enabled.md
View File

@@ -10,24 +10,24 @@ markdown:
---
# MultiSignReserve is Now Available
[As previously announced](https://developers.ripple.com/blog/2019/multisignreserve-expected.html), the MultiSignReserve amendment [became enabled on the XRP Ledger](https://xrpcharts.ripple.com/#/transactions/C421E1D08EFD78E6B8D06B085F52A34A681D0B51AE62A018527E1B8F54C108FB) on 2019-04-17.
[As previously announced](/blog/2019/multisignreserve-expected.md), the MultiSignReserve amendment [became enabled on the XRP Ledger](https://xrpcharts.ripple.com/#/transactions/C421E1D08EFD78E6B8D06B085F52A34A681D0B51AE62A018527E1B8F54C108FB) on 2019-04-17.
## Action Recommended
If you are already using multi-signing, no changes are necessary to continue using it. Optionally, you can now benefit from the reduced reserve requirements by [replacing your existing SignerList](https://developers.ripple.com/set-up-multi-signing.html) with an identical or updated one.
If you are already using multi-signing, no changes are necessary to continue using it. Optionally, you can now benefit from the reduced reserve requirements by replacing your existing SignerList with an identical or updated one.
If you are not using multi-signing yet, feel free to take this opportunity to [Set Up Multi-Signing](https://developers.ripple.com/set-up-multi-signing.html) with the reduced reserve requirements.
If you are not using multi-signing yet, feel free to take this opportunity to [Set Up Multi-Signing](/docs/tutorials/how-tos/manage-account-settings/set-up-multi-signing) with the reduced reserve requirements.
## MultiSignReserve Summary
Reduces the [owner reserve](https://developers.ripple.com/reserves.html#owner-reserves) to 5 XRP counted against your XRP Ledger account when it owns a [multi-signing](https://developers.ripple.com/multi-signing.html) SignerList, regardless of the number of signers. The reserve requirement for previously-created SignerList objects remains unchanged. To reduce the reserve requirement of SignerList objects created before this amendment was enabled, use a [SignerListSet transaction](https://developers.ripple.com/signerlistset.html) to replace the SignerList after this amendment has been enabled. (The replacement can be identical to the previous version.)
Reduces the [owner reserve](/docs/concepts/accounts/reserves#owner-reserves) to 5 XRP counted against your XRP Ledger account when it owns a [multi-signing](/docs/concepts/accounts/multi-signing) SignerList, regardless of the number of signers. The reserve requirement for previously-created SignerList objects remains unchanged. To reduce the reserve requirement of SignerList objects created before this amendment was enabled, use a [SignerListSet transaction](/docs/references/protocol/transactions/types/signerlistset.md) to replace the SignerList after this amendment has been enabled. (The replacement can be identical to the previous version.)
Before this amendment, the owner reserve for a SignerList ranged from 15 to 50 XRP, depending on the number of signers in the list.
## Learn, ask questions, and discuss
Related documentation is available in the [XRP Ledger Dev Portal](https://developers.ripple.com/), including detailed example API calls and web tools for API testing.
Related documentation is available in the [XRP Ledger Dev Portal](/docs/), including detailed example API calls and web tools for API testing.
Other resources: