Bitcoin Forum
May 29, 2024, 06:53:54 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Transaction version 2, Why is it possible and Why isn't it rejected?  (Read 576 times)
Coding Enthusiast (OP)
Legendary
*
Offline Offline

Activity: 1039
Merit: 2783


Bitcoin and C♯ Enthusiast


View Profile WWW
April 13, 2017, 05:42:50 PM
Merited by ABCbits (1)
 #1

The following tx was recently mined in block#461739 and it contains "2" as its version field.
9ac722ca8177a5528e945c081d5d9b021f91d4687838e66c82e7b4589173a88e

I could not find anything on version 2 and as far as I can tell the current consensus dictates version 1 only and should reject anything else.

Block/transaction versions other than 1 are not accepted.

So what am I missing?

Projects List+Suggestion box
Donate: 1Q9s or bc1q
|
|
|
FinderOuter(0.19.1)Ann-git
Denovo(0.7.0)Ann-git
Bitcoin.Net(0.26.0)Ann-git
|
|
|
BitcoinTransactionTool(0.11.0)Ann-git
WatchOnlyBitcoinWallet(3.2.1)Ann-git
SharpPusher(0.12.0)Ann-git
achow101
Moderator
Legendary
*
expert
Offline Offline

Activity: 3402
Merit: 6659


Just writing some code


View Profile WWW
April 13, 2017, 06:29:44 PM
Merited by ABCbits (1)
 #2

Version 2 transactions are the new standard. Bitcoin Core by default makes v2 transactions. A transaction must have a version number of 2 or greater to support OP_CSV.

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!