- 
                Notifications
    You must be signed in to change notification settings 
- Fork 1.6k
Ledger Object IDs
        Elliot Lee edited this page Jan 20, 2023 
        ·
        3 revisions
      
    Ledger objects on the XRP Ledger have a unique ID, which is a hash of some kind.
Use the ledger_entry method to retrieve an object from the ledger.
The index parameter specifies the unique ID of the object to retrieve.
Some useful ledger object IDs:
- Amendments: 7DB0788C020F02780A673DC74757F23823FA3014C1866E72CC4CD8B226CD6EF4
- NegativeUNL: 2E8A59AA9D3B5B186B0B9E0F62E6C02587CA74A4D778938E957B6357D364B244
Here is one way to get the hash:
auto keylet = keylet::negativeUNL();                                                                  
auto key = keylet.key;                                                                                
JLOG(m_journal.info()) << "nunl key : " << strHex(key);
There was a possibility of predicting NFT token IDs by using the sequence. Most NFT brokers look at the created/modified node and compare final/previous fields - in order to get the tokenID after mint. This has become the standard way of getting the newly-minted tokenID.
A snapshot of one week of NFT sales volumes:
| Broker | Sales count | Sales volume (thousands of XRP) | 
|---|---|---|
| xrp.cafe | 1,048 | 536 | 
| onXRP | 887 | 357 | 
| nftmaster | 20 | 0.02 |