What is the purpose of having the collection on the site? it's causing issues, slowing the site to the point can't be used. Should we consider just having the listings only and remove the collections? It's worth noting that there are other sites that could host the collection instead.

When I sign the dummy UTXO, I get this error with the taproot address format, but it works fine with SegWit:

Error:
Cannot finalize input #0. Missing withness utxo.

It would be great to have various sorting options for the inscriptions that are listed in the decentralized order book

The obvious ones I can think of are:

• Inscription # (high/low)
• Price (high/low)

It would be great to be able to filter the display inscriptions listed in the decentralized order book on various attributes

The obvious ones I can think of are:

• Inscription type (image/video/text/etc)
• Collection (only show inscriptions from that collection)

Feature request, but the label is missing on github repo.
Add support to cancel a listing once the PSBT was signed.

How to get the item sale price,Look at the code to get the nft price through this link
wss://nostr.openordex.org/

I think it would be nice if the content on the 802 event were a json instead of the raw PSBT. The reason is that it would be nice for a "listing" to have some additional comment on it so that it can show up nicely as a post in normal nostr feeds.

For example, if i want to sell an Astral Babe, I might want to add a comment: "Check out my sub 10k Astral Babe!", and the nostr clients may add some cool UI on top of these events that adds a button to "buy" it

When I open the PBST in Sparrow wallet, it says, "Invalid message length, was 122 not 126". How to fix it?

When I manually paste in the message, Sparrow asks for an address. When I put my wallet address, the 'Sign' button is not clickable.

I'm writing this as I am very disappointed in ordinals-wallet repo mods. They created a standard they control. Can't we build a merge workflow that will not be dependent on a few biased mods who are skipping pull requests? Right now as I'm writing this, their repo has no activity for three days already.

I'm suggesting that we build a true trustless ordinals collection standard that will also use circleci which will automatically merge with the main branch if all checks are green. Ordinals wallet can use its own standard to list collections on its website but OpenOrdex should be open for all without the middle man. Middle man could only be CircleCi checker.

gm gm - Do you know why the ordinals-collection pull requests are not getting pulled? Seems like they are stale

Assuming this happens because the site is trying to parse non-valid JSON. Should probably display something more like "looks like this collection doesn't exist"

Main Net Example Transaction: https://mempool.space/tx/eed97b6a306b7350784f3a573b46396b6cce404d9ffd67fa982ac757cd6588eb

Resulting location of the inscription: https://ordinals.com/inscription/6dcb3ed8eb96793b7c2917cdeda37197be78af928356167a385814ddcd45014bi0

As the taker constructs the new outputs, they map the first input as 1000 sats, second input as the inscription output and first output as 1000 + inscribedInputSize sats

The result is that the inscribed sat is at satIndex=1000 in the new output

This can result in downstream UX issues where the inscription is likely to be sent to the miner as a fee (not possible so long as the satIndex=0 and the inscribed UTXO is always the first input in the transaction that spends it)

Specified sighash value does not match value stored in PSBT.

• Run bitcoin-qt
• Load psbt from clipboard
• Copy psbt f rom openordex
• Paste psbt from openordex into bitcoin-qt
• Tap sign

I confirmed inscription id is listed in ord wallet inscriptions, receive address set to default

So I followed all the steps and got the PSBT on bitcoin-cli, but upon submitting I get stuck on this screen:
I used a different receive address. I tried Segwit and Taproot addresses.

Currently in openordex sell offer PSBT inputs are prematurely finalized which makes it difficult for the buyer to verify the signatures. This makes it easy to create fake listings which are commonplace on decentralized marketplaces.

Example of inscription #0 listed on openordex for 456 sats.
https://openordex.org/inscription?number=6fb976ab49dcec017f1e201e84395983204ae1a7c2abf7ced0a85d692e442799i0

PSBT inputs are not intended to be finalized until they no longer need to be validated by third parties. In the sell order workflow, the marketplace should not finalize the seller input prior to broadcasting the offer which would allow easier subsequent validation of the signature. Similarly, the buyer workflow should validate the signature on input 0 and finalize it prior to broadcasting.

Recommended changes to openordex:

1. Do not finalize the input of a sell offer (wallet specific flags need to be sent to prevent finalization, update bitcoin-cli instructions)
2. Do not require that inputs are finalized when validating sell offer psbts. Instead, if it is not finalized, validate the signature and discard if it is invalid.
3. Alert users when viewing sell offers that were prematurely finalized since the signature may be invalid and thus may fail when broadcast to the mempool
4. Update the NIP to clarify that the PSBT inputs should not be finalized

I'm not sure if this project is actively maintained or just a proof of concept, but wanted to post this here in the hope that others working on decentralized marketplaces will take this into consideration.

It would be useful to be able to sort collections based on the lowest inscription number in the collection. Might be dependent on #14

It also may make sense for the default sort to be via lowest inscription # (or maybe random each time the page loads)

Possibly other sorting options, but can't think of any good ones right now.

btcToSat(btc) function is unsafe due to javascript floating point imprecision.

> let price = 0.01000014;
> price === satToBtc(btcToSat(price));
false

it may cause problems in generating and validating psbt offers.

I suggest using a safe arbitrary-precision decimal library for btc-denominated values and arithmetic.

example
https://openordex.org/inscription?number=26482871f33f1051f450f2da9af275794c0b5f1c61ebf35e4467fb42c2813403i0

steps to create fake bugged listing.

step 1, create raw tx (no need to broadcast) with address xyz123
step 2, go to any inscription on openordex press create listing, put any price, for receiver put address xyz123
step 3, paste raw tx from step 1 into psbt field, press publish listing

conclusion bugged fake listing.

For a collection page, if an inscription in the collection has been listed in the order book show that it is available to buy similar to what is shown in the listings page.

eg. this inscription is listed for sale https://openordex.org/inscription?number=59edb28a4c0c6a9fb319ae6f4e8d5f979b44e786fa127ad012d1eeda83cd944ei0

but it's not reflected on the collections page https://openordex.org/collection?slug=timechain

I would guess this one might be tricky to implement, as I'm not sure if there is any way to query the nostr relay for only offers which belong to a particular collection?

I used unisat on taproot. I signed the transaction and the signed version appeared in the box. Then I clicked the 'List inscription for sale' button, and it just sits there on 'Submitting'. I saw bug #82 so I then tried PW2PKH but I got the same problem that's in that bug.

When I try to list with xverse in chromium it says "Cannot read properties of undefined (reading 'isUserSignedIn')" at the top of the page.

https://mempool.space/tx/f2784d81cafb56bf7ade3d5426a5110f4335fdb811aaa2b850210152d12babf1#vout=0

https://ordinals.com/output/f2784d81cafb56bf7ade3d5426a5110f4335fdb811aaa2b850210152d12babf1:0

Right now it seems like it's only possible to view the "latest" inscriptions that have been listed for sale. It would be great if it were possible to view all inscriptions that are listed

Description

Trying to list inscription signed from unisat wallet. when clicked on List Inscription for sale getting alert Please sign and finalize the PSBT before submitting it.

For each collection It would be useful to be able to see the range of inscription numbers, and the total supply on the overview page.

See https://ordinalswallet.com/collections for an example of this

'Output' in this snippet is of type 'string'

for (const output in tx.outs) 
    try { tx.setWitness(output, []) } catch { } 
}

but tx.setWitness expects a 'number', which results in an exception

Is it a normal behavior?

When looking at the overview page of inscriptions listed in "latest listings" it does not currently show the inscription number. I think that would be a useful peice of information to add. Many collectors are interested in the inscription number, and currently you need to click into each one to see what it is.

PS. I love openordex ❤️

With the hiro wallet installed as a Chrome extension, I can navigate to an inscription page successfully, like this one:

https://openordex.org/inscription?number=3dc8445abc5d4c34dbcdd11f1cd002aaf22eb817911a1274a53076e8883cfa01i0

But then when I click on the "Buy Inscription ... " button, nothing happens.