Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ord list <UTXO> won't list inscriptions and runes #3701

Closed
shadowysathunter opened this issue Apr 27, 2024 · 4 comments · Fixed by #3766
Closed

ord list <UTXO> won't list inscriptions and runes #3701

shadowysathunter opened this issue Apr 27, 2024 · 4 comments · Fixed by #3766
Assignees

Comments

@shadowysathunter
Copy link

The command ord list <utxo> lists all sats that belong to that UTXO, but it (or any other command) won't list the inscriptions and runes.

@cryptoni9n
Copy link
Collaborator

Hi shadowy,

You're correct, ord list <OUTPUT> lists all sats in a utxo - that is all it purports to do:

Usage: ord list

Arguments:
List sats in <OUTPOINT>.

If you want to list the inscriptions, you can use ord wallet output and if you want to list the runes, you can use ord wallet balance.

I hope this helps.

@shadowysathunter
Copy link
Author

If you want to list the inscriptions, you can use ord wallet output and if you want to list the runes, you can use ord wallet balance.

I hope this helps.

I need to list runes/inscriptions for any arbitrary UTXO, that do not necessary belongs to me, juts like I can do with rare sats and the ord listcommand.

@cryptoni9n
Copy link
Collaborator

If you want to list the inscriptions, you can use ord wallet output and if you want to list the runes, you can use ord wallet balance.
I hope this helps.

I need to list runes/inscriptions for any arbitrary UTXO, that do not necessary belongs to me, juts like I can do with rare sats and the ord listcommand.

I see - @raphjaph I've tagged this as an enhancement request for your review

@raphjaph
Copy link
Collaborator

raphjaph commented May 6, 2024

This makes sense, it should return more info. I think this command hasn't been updated since we first implemented sat tracking so it should be updated to reflect all kinds of assets that can be held in a utxo. It's probably quite an easy change if @shadowysathunter wants to take a stab at it.

It should return many of the infos found in the /output/<OUTPOINT> server endpoint: https://ordinals.com/output/e567f206de5548e3b8a1b483fd95d9348c8b2608b5c5853462c241f84d0bf4a8:0

@raphjaph raphjaph added the stream label May 6, 2024
@cryptoni9n cryptoni9n self-assigned this May 16, 2024
cryptoni9n added a commit to cryptoni9n/ord that referenced this issue May 18, 2024
fixes ordinals#3701 - I've added the /output/<OUTPOINT> fields to the `ord list` command into a section called 'list'.  I also reordered the fields in the existing 'ranges' section to make more logical sense.  There is a small amount of redundancy now with the list.sat_ranges vs ranges.start & end, and list.value vs ranges.size.
cryptoni9n added a commit to cryptoni9n/ord that referenced this issue May 18, 2024
fixes ordinals#3701 - I've added the /output/<OUTPOINT> fields to the `ord list` command into a section called 'list'.  I also reordered the fields in the existing 'ranges' section to make more logical sense.  There is a small amount of redundancy now with the list.sat_ranges vs ranges.start & end, and list.value vs ranges.size.
cryptoni9n added a commit to cryptoni9n/ord that referenced this issue May 18, 2024
fixes ordinals#3701 - I've added the /output/<OUTPOINT> fields to the `ord list` command into a section called 'list'.  I also reordered the fields in the existing 'ranges' section to make more logical sense.  There is a small amount of redundancy now with the list.sat_ranges vs ranges.start & end, and list.value vs ranges.size.
cryptoni9n added a commit to cryptoni9n/ord that referenced this issue May 18, 2024
fixes ordinals#3701 - I've added the /output/<OUTPOINT> fields to the `ord list` command into a section called 'list'.  I also reordered the fields in the existing 'ranges' section to make more logical sense.  There is a small amount of redundancy now with the list.sat_ranges vs ranges.start & end, and list.value vs ranges.size.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants