getLedgerEntries: add meaningful coding examples #469
Comments
|
A couple thoughts: Laboratory – I think building ledger keys would be a perfect feature to add to the Laboratory. In classic stellar days building txs was really the only thing we needed to build, and Laboratory supports that. But with Soroban, building other types is necessary. We could invest UI that auto-generated to build any XDR type also. Soroban CLI – The stellar-xdr CLI is also now embedded into the soroban-cli, which means it's possible to construct these ledger keys and decode the responses on the command line with the tool that folks already have installed. We should include examples. Here's an example of building an account ledger key: |
|
Plus one on adding LedgerKey encoding to the Laboratory! |
|
Where could I find a full list of ledger keys and descriptions? |
|
Not sure if ledger entries and keys are well documented anywhere but the ground truth is in the ledger entries xdr spec here: https://github.com/stellar/stellar-xdr/blob/curr/Stellar-ledger-entries.x More specifically, |
and others
The
getLedgerEntriesmethod is pretty powerful, you can retrieve any piece of state from the ledger: accounts, trustlines, offers, data, liquidity pools, contract wasms, contract instances, contract storage, yada yada.However, there are two challenges associated with that:
However, our coding examples use pre-built keys and don't parse the results. I think that modifying our JS and Python examples in this page to include these can help unlock human potential
Tasks
The text was updated successfully, but these errors were encountered: