Re: Help needed spending non-standard multisig outputs from Counterparty transaction

Quote from: nutildah on July 17, 2025, 12:01:46 PM

I fixed it and this is the proper tx, I'm pretty sure:

Code:

0100000002d89522f8fecdd0832e69909af360551db3810deb2ad7e72a096058dcbe8f2ded0000000000ffffffffd89522f8fecdd0832e69909af360551db3810deb2ad7e72a096058dcbe8f2ded0100000000ffffffff01382d0000000000001976a914fc11decd0e0ab7a332459314069c027328e1dde188ac00000000

Quote from: nutildah on July 17, 2025, 12:01:46 PM

Edit:

Quote from: dexX7 on October 07, 2017, 02:13:08 PM

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...

Yeah, UTXO you try to spend (based on new raw TX) is recognized by several Counterparty explorer. See those,
https://www.xcp.io/tx/ed2d8fbedc5860092ae7d72aeb0d81b31d5560f39a90692e83d0cdfef82295d8
https://www.tokenscan.io/tx/ed2d8fbedc5860092ae7d72aeb0d81b31d5560f39a90692e83d0cdfef82295d8

Quote from: nutildah on July 17, 2025, 12:01:46 PM

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...

For different case of non-standard (but valid) TX, what you need is miner who're willing to to add such TX. Other pool may do it if you contact them, while MARA currently being the only one who offer such service (MARA Slipstream) in automated way.