Non-standard tx (anyone-can-spend OP_N) — 77,943 sats fee for the miner who incl

[SherlockSH]

Hello everyone,

I need help from anyone who runs a Bitcoin mining node (pool operator, solo miner, or developer) and is willing to include one non-standard transaction in a block.

THE SITUATION

I have a test transaction that is perfectly valid under consensus rules but is rejected by the standard mempool policy because its inputs are non-standard. It spends 1,900 anyone-can-spend OP_N outputs (empty scriptSig) and pays out to a single P2WPKH output.

Details of the test tx:

- txid: 56eb50f246f56228246731534b32b0421a3115672cc8d11e0ebcbf5f61f8513a
- type: legacy
- inputs: 1,900 (anyone-can-spend OP_N, empty scriptSig)
- outputs: 1 x P2WPKH
- vsize: 77,943 (~1 sat/vB)
- fee: 77,943 sats

WHAT I NEED

A bitcoind patched to accept non-standard inputs (I have the patch: acceptnonstdinputs-v31.1.patch, I can share it by PM). Once the tx is accepted by the node, the block template will include it, and the miner who finds the block keeps the fee automatically (paid via coinbase, no trust needed).

WHAT'S IN IT FOR YOU

77,943 sats, credited directly to the coinbase of the block you find. This is a test to validate the approach; if it works, there may be more similar transactions.

WHAT I AM NOT ASKING FOR

- No keys, no private data — the tx contains no script of value, it is pure fee bait.
- No payments in advance, no KYC, no "software to install".
- The patch and raw hex are shared with anyone who demonstrates control of a real mining node.

If you can help, or know someone who can, please reply here or send me a PM. Happy to share full details.

Thanks!

[BitMaxz]

I don't think you'll need someone here to do this; I think you can use some accelerator offers out there if you want a custom node to confirm your transaction. 
Like on the mempool here: https://mempool.space/accelerator and ViaBTC here:  https://www.viabtc.com/en/tools/txaccelerator

But expect a high service fee. I don't know if the free option in ViaBTC will help compared to the paid one to prioritize your transaction.

I'm not just confident of sharing some files you mention above from newbie that's suspicious than just using the 3rd party service that I mention above.

[philipma1957]

Viabtc will charge a lot but it will be the best way to get it done.

[SherlockSH]

I don't think you'll need someone here to do this; I think you can use some accelerator offers out there if you want a custom node to confirm your transaction. 
Like on the mempool here: https://mempool.space/accelerator and ViaBTC here:  https://www.viabtc.com/en/tools/txaccelerator

But expect a high service fee. I don't know if the free option in ViaBTC will help compared to the paid one to prioritize your transaction.

I'm not just confident of sharing some files you mention above from newbie that's suspicious than just using the 3rd party service that I mention above.

Thanks for the suggestions — I appreciate the pointers. Two technical notes on why the accelerator route can't apply here, for anyone following along:

1) Accelerators only prioritize transactions that are already in the mempool (theirs or the public one). This transaction is non-standard: the mempool rejects it with bad-txns-nonstandard-inputs, because its 1,900 inputs spend anyone-can-spend BIP141 witness programs (versions 2-16), which the DISCOURAGE policy flag refuses at admission. It never sits in any mempool, so there is nothing for an accelerator to pick up.

2) The economics: this tx pays ~77,943 sats (~1 sat/vB) embedded — deliberately. The miner who includes it keeps the fee; no external payment, no custody, no keys, no KYC. Accelerator pricing targets urgent high-fee standard traffic; this tx is the opposite by design.

The route that does work: any pool or miner includes the tx directly in its block template (getblocktemplate -> submitblock). Block validation is consensus-only — it does not run mempool policy checks — and this tx is consensus-valid (BIP141 anyone-can-spend, empty scriptSig, weight 311,772 WU ~ 7.79% of a block). Verified in practice: the identical construction, including a 1,900-input version, confirmed 31/31 in blocks on a regtest chain.

On sharing files from a newbie account — fair point. To be precise: the only file involved is the raw transaction itself, which is public data (every input/output is already on-chain; no private keys, no identity). It can be verified with any node or explorer.

So if ViaBTC or any pool ever wants to include it via its own template, the 77,943 sats are theirs. Txid: 56eb50f2...513a. Details through official channels only.

[SherlockSH]

Viabtc will charge a lot but it will be the best way to get it done.

Thanks. On "the best way to get it done": two blockers make ViaBTC's accelerator unable to touch this one — and price isn't even the issue:

1) Accelerators only work on transactions already in the mempool (you submit a txid that is queued there). This transaction is non-standard: the mempool rejects it (bad-txns-nonstandard-inputs) because its 1,900 inputs spend anyone-can-spend BIP141 witness programs v2-16. It sits in no mempool anywhere, so there is no txid for an accelerator to prioritize — free or paid.

2) The design deliberately has no external payment: 77,943 sats (~1 sat/vB) are embedded in the transaction and go to whoever mines it. A paid accelerator service would cost more than the fee itself — paying to spend money.

What does work: a pool includes the tx straight into its block template (getblocktemplate -> submitblock). Block validation is consensus-only, and this tx is consensus-valid — weight 311,772 WU (~7.79% of a block); verified 31/31 on a regtest chain, including a 1,900-input version. If ViaBTC the pool ever wants it in its own blocks, the 77,943 sats are theirs, no service fee. Txid: 56eb50f2...513a.

[ABCbits]

1) Accelerators only work on transactions already in the mempool (you submit a txid that is queued there). This transaction is non-standard: the mempool rejects it (bad-txns-nonstandard-inputs) because its 1,900 inputs spend anyone-can-spend BIP141 witness programs v2-16. It sits in no mempool anywhere, so there is no txid for an accelerator to prioritize — free or paid.

2) The design deliberately has no external payment: 77,943 sats (~1 sat/vB) are embedded in the transaction and go to whoever mines it. A paid accelerator service would cost more than the fee itself — paying to spend money.

What does work: a pool includes the tx straight into its block template (getblocktemplate -> submitblock). Block validation is consensus-only, and this tx is consensus-valid — weight 311,772 WU (~7.79% of a block); verified 31/31 on a regtest chain, including a 1,900-input version. If ViaBTC the pool ever wants it in its own blocks, the 77,943 sats are theirs, no service fee. Txid: 56eb50f2...513a.

Have you checked https://slipstream.mara.com/? It accept some types/kinds of non-standard TX from raw TX (so you don't have to broadcast to whole Bitcoin network/node it in first place). Make sure to check the FAQ and terms, because there are some limitation imposed by them.

[SherlockSH]

1) Accelerators only work on transactions already in the mempool (you submit a txid that is queued there). This transaction is non-standard: the mempool rejects it (bad-txns-nonstandard-inputs) because its 1,900 inputs spend anyone-can-spend BIP141 witness programs v2-16. It sits in no mempool anywhere, so there is no txid for an accelerator to prioritize — free or paid.

2) The design deliberately has no external payment: 77,943 sats (~1 sat/vB) are embedded in the transaction and go to whoever mines it. A paid accelerator service would cost more than the fee itself — paying to spend money.

What does work: a pool includes the tx straight into its block template (getblocktemplate -> submitblock). Block validation is consensus-only, and this tx is consensus-valid — weight 311,772 WU (~7.79% of a block); verified 31/31 on a regtest chain, including a 1,900-input version. If ViaBTC the pool ever wants it in its own blocks, the 77,943 sats are theirs, no service fee. Txid: 56eb50f2...513a.

Have you checked https://slipstream.mara.com/? It accept some types/kinds of non-standard TX from raw TX (so you don't have to broadcast to whole Bitcoin network/node it in first place). Make sure to check the FAQ and terms, because there are some limitation imposed by them.

Thanks for the pointer — Slipstream was the one lead we hadn't checked yet, and it turned out to be the most relevant one. I looked into it properly:

1) It's real and live: MARA's official direct-submission portal/API for non-standard transactions — raw hex straight to their pool, no public broadcast needed. It opened to the general public this month, free, with no extra fees beyond the network fee.

2) I read the FAQ and the Terms in full before touching it. The catch is in the Terms, Section IX "Special Requests", clause 9.1: anyone-can-spend transactions "will not be accepted by default on Slipstream", and users with special requests "must contact foundation@mara.com". So for our exact case (anyone-can-spend witness v2-v16 inputs), the portal itself won't take the transaction by default — but MARA's own terms point to the precise channel for it.

3) I've contacted them through that channel (foundation@mara.com) — the one their terms designate for this exact situation — with the test transaction attached. Their mempool policy handles our size fine (311,772 WUs vs their 3,991,000 WU limit), and I offered to adjust the fee to their minimum submission rate if they want to test on that basis.

I'm keeping the thread open because I'm still waiting on responses from the pools I contacted through their official channels. As soon as I have anything concrete, I'll post an update here.

Thanks again for the info — genuinely helpful.