Bitcoin Forum
December 29, 2025, 12:22:37 PM *
News: Latest Bitcoin Core release: 30.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: When was the bug in <decoderawtransaction> fixed?  (Read 131 times)
kurve21 (OP)
Newbie
*
Offline Offline

Activity: 9
Merit: 7


View Profile
December 09, 2025, 08:15:04 AM
Last edit: December 09, 2025, 03:33:07 PM by kurve21
Merited by ABCbits (2), vapourminer (1), garlonicon (1)
 #1

In the core version v0.18.1 there is still an error with "decoderawtransaction".
For example, the Tx 54549260d3aa4ee5410022e209699844fb2e2b7d1059221e8c03fb5bad211533 cannot be decoded correctly. The witness field is not recognized.
I know that this bug has been fixed in the latest version. My question is, in which version exactly was the bug fixed? So what is the oldest version where this bug is fixed?
Anything anyone could find out it would be great! Thank you!

-----------------------------------------------------------------------------------
Edit:
I did a little testing and figured it out for myself. In V.0.21.1 the error is no longer there.
mcdouglasx
Sr. Member
****
Offline Offline

Activity: 868
Merit: 437



View Profile WWW
December 09, 2025, 08:16:19 PM
 #2

I was looking for a commit in the repository that mentioned this and couldn't find it, but let's assume it was because the improvement was made gradually and not in a single update, since this was improved incrementally over time.

█████████████████████████
█████████████████████████
███████▀█████████▀███████
█████████████████████████
█████████████████████████
████████████▀████████████
███████▀███████▄███████
███████████▄▄▄███████████
█████████████████████████
█████████████████████████
█████████████████████████
█████████████████████████
█████████████████████████

2UP.io 
NO KYC
CASINO
██████████████████████████
████████████████████████
███████████████████████
███████████████████
██████████████████████
███████████████████████
███████████████████████
██████████████████
███████████████████████
██████████████████
███████████████████████
████████████████████████
██████████████████████████
███████████████████████████████████████████████████████████████████████████████████████
 
FASTEST-GROWING CRYPTO
CASINO & SPORTSBOOK

 

███████████████████████████████████████████████████████████████████████████████████████
███████████████████████████
█████████████████████████
███████████████████████
███████████████████████
████████████████████████
███████████████████████
███████████████████████
██████████████████████
████████████████████████
███████████████████████
███████████████████████
█████████████████████████
███████████████████████████
 
WELCOME BONUS
200% + 500 FS
█▀▀▀











█▄▄▄
▀▀▀█











▄▄▄█
ercewubam
Jr. Member
*
Offline Offline

Activity: 36
Merit: 73


View Profile
December 10, 2025, 04:20:42 AM
Merited by ABCbits (5), vapourminer (1), d5000 (1), hugeblack (1)
 #3

Quote
I was looking for a commit in the repository that mentioned this and couldn't find it
Let's see: https://github.com/bitcoin/bitcoin/pull/8149

If you want to find a commit, where Segwit was introduced, then it is here: https://github.com/bitcoin/bitcoin/commit/d612837814020ae832499d18e6ee5eb919a87907
nc50lc
Legendary
*
Offline Offline

Activity: 3010
Merit: 8175


Self-proclaimed Genius


View Profile
December 10, 2025, 05:39:31 AM
Merited by ABCbits (5), vapourminer (4), kurve21 (2), garlonicon (1)
 #4

For example, the Tx 54549260d3aa4ee5410022e209699844fb2e2b7d1059221e8c03fb5bad211533 cannot be decoded correctly.
-snip-
-----------------------------------------------------------------------------------
Edit:
I did a little testing and figured it out for myself. In V.0.21.1 the error is no longer there.
It's actually in v0.21.0, just a minor version lower than it.
BTW, it'll work in your v0.18.1 if you add is_witness flag (true) after the raw transaction hex in the command.

If you're looking for the PR and Commit, here are those:

███████████████████████████
███████▄████████████▄██████
████████▄████████▄████████
███▀█████▀▄███▄▀█████▀███
█████▀█▀▄██▀▀▀██▄▀█▀█████
███████▄███████████▄███████
███████████████████████████
███████▀███████████▀███████
████▄██▄▀██▄▄▄██▀▄██▄████
████▄████▄▀███▀▄████▄████
██▄███▀▀█▀██████▀█▀███▄███
██▀█▀████████████████▀█▀███
███████████████████████████
.
.Duelbits PREDICT..
█████████████████████████
█████████████████████████
███████████▀▀░░░░▀▀██████
██████████░░▄████▄░░████
█████████░░████████░░████
█████████░░████████░░████
█████████▄▀██████▀▄████
████████▀▀░░░▀▀▀▀░░▄█████
██████▀░░░░██▄▄▄▄████████
████▀░░░░▄███████████████
█████▄▄█████████████████
█████████████████████████
█████████████████████████
.
.WHERE EVERYTHING IS A MARKET..
█████
██
██







██
██
██████
Will Bitcoin hit $200,000
before January 1st 2027?

    No @1.15         Yes @6.00    
█████
██
██







██
██
██████

  CHECK MORE > 
kurve21 (OP)
Newbie
*
Offline Offline

Activity: 9
Merit: 7


View Profile
December 10, 2025, 08:06:43 AM
Merited by vapourminer (1)
 #5

For example, the Tx 54549260d3aa4ee5410022e209699844fb2e2b7d1059221e8c03fb5bad211533 cannot be decoded correctly.
-snip-
-----------------------------------------------------------------------------------
Edit:
I did a little testing and figured it out for myself. In V.0.21.1 the error is no longer there.
It's actually in v0.21.0, just a minor version lower than it.
BTW, it'll work in your v0.18.1 if you add is_witness flag (true) after the raw transaction hex in the command.

If you're looking for the PR and Commit, here are those:


perfect, thank you very much!
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!