Help needed spending non-standard multisig outputs from Counterparty transaction

[nutildah]

Hi chat,

I need some big brained input on this one. I am trying to spend the multisig outputs from this transaction (I have hundreds like it and the end goal is to collect all of them, which is >$1k in BTC):

https://mempool.space/tx/ed2d8fbedc5860092ae7d72aeb0d81b31d5560f39a90692e83d0cdfef82295d8

I managed to "vibe code" my way to a broadcast-able transaction that spends the 2 outputs to the address of origin, but I received the following error on Electrum and other push tx services:

"bad-txns-inputs-missingorspent"

(I know they are unspent b/c I used a service in 2014 to redeem a bunch of similar outputs; that transaction is here).

I tried recreating the transaction for the network to recognize that multisig outputs are being spent, and now I get this error:

"scriptsig-not-pushonly"

Something to keep in mind is that this is a "fake multisig" transaction, meaning it just requires 1 of 2 signatures; the 1st public key comes from my address and the 2nd public key is fake.

This is the service I used to create the multisig output consolidation transaction in 2014, but it is no longer functioning:

http://redeem.bitwatch.co/

They even have a thread on this forum.

So my question is, if I paste the raw hex tx here, could you tell me why the transaction is being rejected?

An easier question to answer might be is there a push tx service for non-standard transactions? I'm not sure if they exist, but would be good to know if one is out there.

Thanks for your help.

[Skjadoon]

Hi chat,

I need some big brained input on this one. I am trying to spend the multisig outputs from this transaction (I have hundreds like it and the end goal is to collect all of them, which is >$1k in BTC):

https://mempool.space/tx/ed2d8fbedc5860092ae7d72aeb0d81b31d5560f39a90692e83d0cdfef82295d8

I managed to "vibe code" my way to a broadcast-able transaction that spends the 2 outputs to the address of origin, but I received the following error on Electrum and other push tx services:

"bad-txns-inputs-missingorspent"

(I know they are unspent b/c I used a service in 2014 to redeem a bunch of similar outputs; that transaction is here).

I tried recreating the transaction for the network to recognize that multisig outputs are being spent, and now I get this error:

"scriptsig-not-pushonly"

Something to keep in mind is that this is a "fake multisig" transaction, meaning it just requires 1 of 2 signatures; the 1st public key comes from my address and the 2nd public key is fake.

This is the service I used to create the multisig output consolidation transaction in 2014, but it is no longer functioning:

http://redeem.bitwatch.co/

They even have a thread on this forum.

So my question is, if I paste the raw hex tx here, could you tell me why the transaction is being rejected?

An easier question to answer might be is there a push tx service for non-standard transactions? I'm not sure if they exist, but would be good to know if one is out there.

Thanks for your help.

Only way: run your own node with non-standard TXs allowed, or pay a miner to include it.

[nutildah]

Only way: run your own node with non-standard TXs allowed, or pay a miner to include it.

Trust me if I had Bitcoin Core on my computer I would have tried it. I can't help but think there's a way to do it through a push tx service. And I wouldn't want to pay a miner to include it if its malformed, which may be the case. I tried doing it through here:

https://bitaccelerate.com/pushtx/

which says this at the bottom:

"This service is using the "sendrawtransaction" method of the Bitcoin Core client. Your transaction must be signed and must not contain unconfirmed inputs."

But still got an error.

For reference, this is the unsigned transaction, would be grateful if someone could analyze it and tell me if something is wrong:

Code:

0100000002d89522f8fecd0d83e269909af360551db3810deb2ad7e72a096058dcbe8f2ded0000000000ffffffffd89522f8fecd0d83e269909af360551db3810deb2ad7e72a096058dcbe8f2ded0100000000ffffffff01382d0000000000001976a914fc11decd0e0ab7a332459314069c027328e1dde188ac00000000

This is the error I get from blockstream.info/tx/push when attempting to broadcast the signed transaction:

"sendrawtransaction RPC error -25: bad-txns-inputs-missingorspent"

[LoyceV]

This is the service I used to create the multisig output consolidation transaction in 2014, but it is no longer functioning:
http://redeem.bitwatch.co/

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

This project has served very well, but lost it's purpose, given that it is no longer economic to redeem dust-ish outputs, it costs more to retrieve the dust.

This was probably written when Bitcoin prices were much lower. It might be worth resurrecting the service.

[ABCbits]

For reference, this is the unsigned transaction, would be grateful if someone could analyze it and tell me if something is wrong:

Code:

0100000002d89522f8fecd0d83e269909af360551db3810deb2ad7e72a096058dcbe8f2ded0000000000ffffffffd89522f8fecd0d83e269909af360551db3810deb2ad7e72a096058dcbe8f2ded0100000000ffffffff01382d0000000000001976a914fc11decd0e0ab7a332459314069c027328e1dde188ac00000000

This is the error I get from blockstream.info/tx/push when attempting to broadcast the signed transaction:

"sendrawtransaction RPC error -25: bad-txns-inputs-missingorspent"

This is decode result using https://live.blockcypher.com/btc/decodetx/

Code:

{
    "addresses": [
        "1PypgzaAJXHzLPvkLQwWzqwn1AyhJd9YUi"
    ],
    "block_height": -1,
    "block_index": -1,
    "confirmations": 0,
    "double_spend": false,
    "fees": 0,
    "hash": "4fdb912af649ec80bb3a13f3d42429d69e2069cbd7880ecf87dccc51f875f7fe",
    "inputs": [
        {
            "age": 0,
            "output_index": 0,
            "prev_hash": "ed2d8fbedc5860092ae7d72aeb0d81b31d5560f39a9069e2830dcdfef82295d8",
            "script_type": "empty",
            "sequence": 4294967295
        },
        {
            "age": 0,
            "output_index": 1,
            "prev_hash": "ed2d8fbedc5860092ae7d72aeb0d81b31d5560f39a9069e2830dcdfef82295d8",
            "script_type": "empty",
            "sequence": 4294967295
        }
    ],
    "outputs": [
        {
            "addresses": [
                "1PypgzaAJXHzLPvkLQwWzqwn1AyhJd9YUi"
            ],
            "script": "76a914fc11decd0e0ab7a332459314069c027328e1dde188ac",
            "script_type": "pay-to-pubkey-hash",
            "value": 11576
        }
    ],
    "preference": "low",
    "received": "2025-07-17T09:28:27.217923583Z",
    "relayed_by": "3.239.97.190",
    "size": 126,
    "total": 11576,
    "ver": 1,
    "vin_sz": 2,
    "vout_sz": 1,
    "vsize": 126
}

prev_hash inside inputs refer to output from TXID you're trying to spend. But TXID ed2d8fbedc5860092ae7d72aeb0d81b31d5560f39a9069e2830dcdfef82295d8 isn't exist on Bitcoin blockchain (according to few Bitcoin block explorer). So you're trying to spend non-existent Bitcoin.

[nutildah]

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"

 

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

[ABCbits]

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

Code:

0100000002d89522f8fecdd0832e69909af360551db3810deb2ad7e72a096058dcbe8f2ded0000000000ffffffffd89522f8fecdd0832e69909af360551db3810deb2ad7e72a096058dcbe8f2ded0100000000ffffffff01382d0000000000001976a914fc11decd0e0ab7a332459314069c027328e1dde188ac00000000

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

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

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

 

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.

[Cricktor]

As ABCbits says, if your redeem transaction is valid but only non-standard, you could try to submit your transaction via slipstream.mara.com. They say they accept non-standard transactions which other nodes won't relay and thus hardly can reach any miners mempool.

The Slipstream service might impose other restrictions to non-standard transactions and I haven't used it to submit non-standard transactions because I don't need to. You pay a higher fee rate than normal, but it's quite reasonable and especially now when mempool isn't much full at all.

It would be the goto method for me if I had a non-standard transaction or a transaction that I don't want to be seen in public until it is actually confirmed and mined into a block.

[flatfly]

Not sure if you're aware of this, but your tx has an empty scriptsig, maybe that's the issue.

(Just a wild guess)

[nutildah]

Here's an interesting update & a puzzle for anyone who appreciates spotting the differences between different types of transactions. I managed to consolidate & spend some of the outputs thanks to a new Counterparty wallet feature.

Here's an example consolidation tx:

https://mempool.space/tx/17579e4d114a20678f4b869544f606437a053a2618bf11f721cc008e7db5c67d

Here's an example of a multisig output that is consolidate-able:

https://mempool.space/tx/646c03331f9ffd3d95da80896164fbf4bed2c68efc0bc646dd3146f2942f004b#vout=0

And here's some examples of multisig outputs that are not (not recognized by the wallet as such, anyway):

https://mempool.space/tx/cf747d954ea20775dc4cca2e8336dfb64a82c596afdc2e52d939677308f05486#vout=0
https://mempool.space/tx/3cf38a4fdfb47908567e276a42db1d6c18f2c3280acc24f3595f54b4fc5e5e6d#vout=0
https://mempool.space/tx/d15b15a956166447893b2f2c8849b9d2892fea0fc24bbedf74b246816025bea0#vout=0
https://mempool.space/tx/b9297449020c0eaae35e2ab38744ed59ad928300a909de2b8242c9196805ac23#vout=0

I have also prepared this post to share with the developer so maybe he can also shed some light on how the wallet logic works.

Not sure if you're aware of this, but your tx has an empty scriptsig, maybe that's the issue.

(Just a wild guess)

Right I left it out on purpose, I forget what my exact reasoning was at the time.