how to broadcast v01 sig is non canonical.

[analking]

what version bitcoin core is required for v01 tx?

01000000017f5e04f7dbbc06cd88fd20e922960731594c7bbd5bfb8ab9c137d8c50ac7c4e501000 0008b483045022100ad19d8944591fb647306fc281d27bd40e0cda09d69c99129de77f8abbb37e4 8a022043d8de7fdfa0d9ec0918bfa96a0f786080324034297811d46c81b257c791a556014104161 c71cbde74f28cfffa05e3a543282f8500a289a67c75a81edff29f3c64cfda7e3ccdbf63b1206b16 653bfd91029ce0b3552e64d4e36d4d6b7d6935d47a4d86ffffffff010005e805160100001976a91 4c8a3535793d51f143d6451f4bf6cb2e74a6c589888ac00000000

[Ambatman]

Since it has a Witness data and version 1 then is a Segwit transaction.
So the minimum version would be Bitcoin Core version 0.13.0 but for better performance I would say version 13.1
They were the first version that implemented BIP 141 which is Segwit.
But other current versions can broadcast this with relatively better patches as a result of updates.

[analking]

Since it has a Witness data and version 1 then is a Segwit transaction.
So the minimum version would be Bitcoin Core version 0.13.0 but for better performance I would say version 13.1
They were the first version that implemented BIP 141 which is Segwit.
But other current versions can broadcast this with relatively better patches as a result of updates.

how avoid this error .13.1? is it need set in conf file?


brad@brad-Z790I-Lightning-WiFi:~/bitcoin-0.13.1$ bitcoin-cli -maxtxfee=1000000000000 sendrawtransaction 01000000017f5e04f7dbbc06cd88fd20e922960731594c7bbd5bfb8ab9c137d8c50ac7c4e501000 0008b483045022100ad19d8944591fb647306fc281d27bd40e0cda09d69c99129de77f8abbb37e4 8a022043d8de7fdfa0d9ec0918bfa96a0f786080324034297811d46c81b257c791a556014104161 c71cbde74f28cfffa05e3a543282f8500a289a67c75a81edff29f3c64cfda7e3ccdbf63b1206b16 653bfd91029ce0b3552e64d4e36d4d6b7d6935d47a4d86ffffffff010005e805160100001976a91 4c8a3535793d51f143d6451f4bf6cb2e74a6c589888ac00000000
error code: -26
error message:
256: absurdly-high-fee

[pooya87]

Since it has a Witness data and version 1 then is a Segwit transaction.

There is no witness in the raw tx posted by OP.
Additionally the output OP is trying to spend is a simple P2PKH from 2010 worth 12000 BTC and the uncompressed public key used in the signature script doesn't give the same hash as the one used in the P2PKH output meaning it is an invalid tx!
https://mempool.space/tx/e5c4c70ac5d837c1b98afb5bbd7b4c5931079622e920fd88cd06bcdbf7045e7f

Checking the pubkey, it has nothing to do with the address (hence the script evaluation failure on OP_CHECKEQUALVERIFY).

Code:

pub: 04161c71cbde74f28cfffa05e3a543282f8500a289a67c75a81edff29f3c64cfda7e3ccdbf63b1206b16653bfd91029ce0b3552e64d4e36d4d6b7d6935d47a4d86

expected: 12ib7dApVFvg82TXKycWBNpN8kFyiAN1dr
actual uncomp: 1NpfEmz9kAjaSmWfxGKQA1KJiDDXdRxDnq
actual comp: 1CwCF1bn5iTnxqgTwfy3piy6gmEL1dNcN8

To OP you can't spend other people's money using any random key. It has to be the key that belongs to that address which I'm guessing you don't have!

[Ambatman]

Since it has a Witness data and version 1 then is a Segwit transaction.

There is no witness in the raw tx posted by OP.

Thank you for the correction. After the version, I assumed that it was 0001, marker 00 and flag 01.
Which is usually found in Segwit.

022043d8de7fdfa0d9ec0918bfa96a0f786080324034297811d46c81b257c791a556014104161 c71cbde74f28cfffa05e3a543282f8500a289a67c75a81edff29f3c64cfda7e3ccdbf63b1206b16 653bfd91029ce0b3552e64d4e36d4d6b7d6935d47a4d86ffffffff010005e805160100001976a91 4c8a3535793d51f143d6451f4bf6cb2e74a6c589888ac

I took the above as the Witness data since it was after my supposed output and before Locktime

Code:

00000000

P2PKH from 2010 worth 12000 BTC and the uncompressed public key used in the signature script doesn't give the same hash as the one used in the P2PKH output meaning it is an invalid tx!

So the fee error OP faced was as a result of the fact that

Code:

maxtxfee=1000000000000 which is 10000BTC is lower than 12000BTC-2.94BTC(output)=11997.06(fee)

[analking]

yes,  i bootstrapped the below with the old ledger from my ancestor. assuming the key is correct (it is), do you notice any issue broadcast this new tx on core .13.1 ?

0200000001310add102977f5991ba254f8a09d7b3d4933e57c6753b906899c05a4964fdbd700000 0008b483045022100aeea7d5f7d5c18227a9b376bcb3d13b468c0d40163f405b636d8c1114fa8c3 a302203857d0237bb87041b8670017fb2cea0b8ce0e89b5b0101b636d9665ec9074b57014104bb2 2453bb85ec2beefb0c6f1255c6b93b3c1a4a0813af207b4fa6570f2fe2afb1ffb5617f8a0a090dc beab5b136e82a0a0351dc7b274bd797a344b8c1df5a777ffffffff0300943577000000001976a91 4c8a3535793d51f143d6451f4bf6cb2e74a6c589888ac26093a29000000001976a91462e907b15c bf27d5425399ebf6f0fb50ebb88f1888ac0000000000000000206a1e4920414d2057484f2049204 14d204252414434323839312057204c4f564500000000

[pooya87]

yes,  i bootstrapped the below with the old ledger from my ancestor. assuming the key is correct (it is), do you notice any issue broadcast this new tx on core .13.1 ?

04bb22453bb85ec2beefb0c6f1255c6b93b3c1a4a0813af207b4fa6570f2fe2afb1ffb5617f8a0a 090dcbeab5b136e82a0a0351dc7b274bd797a344b8c1df5a777

Same problem.
You can't spend other people's bitcoins using any random key you come up with. It has to be the same key that generated the public key that was hashed and created the address! Verification fails on OP_EQUALVERIFY and it doesn't matter which bitcoin core version you use to push this.