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

Update links in NFT-related blog posts to use absolute paths for improved navigation and consistency across documentation.

Browse Source
This commit is contained in:
akcodez
2025-01-13 09:21:46 -08:00
parent 8de8a47565
commit eb88622e87
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
blog/2022/get-ready-for-nfts.md
View File

@@ -36,9 +36,9 @@ For an amendment to the XRP Ledger protocol to become enabled, it must hold **ov
The exact amendment voting calculations depend on the quorum of validators that are currently online and participating in consensus, which means that the exact number of votes in favor of an amendment can fluctuate when validators go temporarily offline. If at any point its support drops below 80%, the timer resets and the amendment must wait a full two weeks again starting when it regains 80%+ support.
Previously, the threshold for amendment voting was "at least 80%" but in some cases rounding in the reference server's calculations could cause this condition to be met with slightly below 80%. The [fixAmendmentMajorityCalc amendment](https://xrpl.org/known-amendments.html#fixamendmentmajoritycalc), which activated on 2021-04-08, changed the calculation to be **strictly greater than 80%**. Since there are currently 35 validators in all three [recommended UNLs](https://xrpl.org/faq.html#validators-and-unique-node-lists), and 28/35 is _exactly_ 80%, the threshold for voting to enable an amendment when all validators are online is at least 29 votes in favor.
Previously, the threshold for amendment voting was "at least 80%" but in some cases rounding in the reference server's calculations could cause this condition to be met with slightly below 80%. The [fixAmendmentMajorityCalc amendment](https://xrpl.org/known-amendments.html#fixamendmentmajoritycalc), which activated on 2021-04-08, changed the calculation to be **strictly greater than 80%**. Since there are currently 35 validators in all three [recommended UNLs](https://xrpl.org/about/faq#validators-and-unique-node-lists), and 28/35 is _exactly_ 80%, the threshold for voting to enable an amendment when all validators are online is at least 29 votes in favor.
For a live view of amendment voting, you can use the [XRPScan Amendments Dashboard](https://xrpscan.com/amendments). For more discussion of the voting process, see [this blog by Ripple developer Nik B.](https://dev.to/ripplexdev/xrpl-amendments-to-vote-or-not-to-vote-5l3) as well as the [Amendments documentation](https://xrpl.org/amendments.html).
For a live view of amendment voting, you can use the [XRPScan Amendments Dashboard](https://xrpscan.com/amendments). For more discussion of the voting process, see [this blog by Ripple developer Nik B.](https://dev.to/ripplexdev/xrpl-amendments-to-vote-or-not-to-vote-5l3) as well as the [Amendments documentation](https://xrpl.org/docs/concepts/networks-and-servers/amendments).
## NFT Functionality Summary

2
blog/2024/how-to-mint-nfts.md
View File

@@ -64,7 +64,7 @@ To view a list of NFTs associated with your account, simply click **Get NFTs**.
## Burning Your NFT
[Burning an NFT](https://xrpl.org/docs/tutorials/python/modular-tutorials/nfts/mint-and-burn-nfts#mint-and-burn-nfts-using-python) is the process of permanently destroying the token. To burn an NFT:
[Burning an NFT](https://xrpl.org/docs/tutorials/python/nfts/mint-and-burn-nfts) is the process of permanently destroying the token. To burn an NFT:
1. Enter the Token ID of the NFT you wish to destroy.
2. Click **Burn NFT** to remove it permanently from the ledger.