Next scheduled rescrape ... never
Version 1
Last scraped
Edited on 17/07/2025, 12:31:36 UTC
But TXID ed2d8fbedc5860092ae7d72aeb0d81b31d5560f39a9069e2830dcdfef82295d8 isn't exist on Bitcoin blockchain (according to few Bitcoin block explorer). So you're trying to spend non-existent Bitcoin.

Hey, good catch! You're absolutely right. I fixed it and this is the proper tx, I'm pretty sure:

Code:
0100000002d89522f8fecdd0832e69909af360551db3810deb2ad7e72a096058dcbe8f2ded0000000000ffffffffd89522f8fecdd0832e69909af360551db3810deb2ad7e72a096058dcbe8f2ded0100000000ffffffff01382d0000000000001976a914fc11decd0e0ab7a332459314069c027328e1dde188ac00000000

A couple of the numbers were in reverse order, so I fixed them to match the tx in question.

Now I've graduated to the next error: "RPC error -26: bad-txns-nonstandard-inputs"

 Cheesy

I guess I need someone running a custom version of Bitcoin to push the transaction through for me...

In any case, thanks, I would have never thought to decode the TX to double-check everything was in order.

To ask the obvious: have you tried emailing dexx@?

Guess I'll do that now...



Edit:

Some transactions from Counterparty were created with invalid public keys and are no longer redeemable.

See also: https://github.com/bitcoin/bitcoin/issues/5939

Oh...
Original archived Re: Help needed spending non-standard multisig outputs from Counterparty transaction
Scraped on 17/07/2025, 12:01:46 UTC
But TXID ed2d8fbedc5860092ae7d72aeb0d81b31d5560f39a9069e2830dcdfef82295d8 isn't exist on Bitcoin blockchain (according to few Bitcoin block explorer). So you're trying to spend non-existent Bitcoin.

Hey, good catch! You're absolutely right. I fixed it and this is the proper tx, I'm pretty sure:

Code:
0100000002d89522f8fecdd0832e69909af360551db3810deb2ad7e72a096058dcbe8f2ded0000000000ffffffffd89522f8fecdd0832e69909af360551db3810deb2ad7e72a096058dcbe8f2ded0100000000ffffffff01382d0000000000001976a914fc11decd0e0ab7a332459314069c027328e1dde188ac00000000

A couple of the numbers were in reverse order, so I fixed them to match the tx in question.

Now I've graduated to the next error: "RPC error -26: bad-txns-nonstandard-inputs"

 Cheesy

I guess I need someone running a custom version of Bitcoin to push the transaction through for me...

In any case, thanks, I would have never thought to decode the TX to double-check everything was in order.

To ask the obvious: have you tried emailing dexx@?

Guess I'll do that now...