|
Title: Transaction Version (expected to be 1 but I got 0) Post by: sidazhang on February 19, 2014, 01:59:09 AM http://test.webbtc.com/tx/f1ebaf4604158a8a385cb55d1c0ca5efde98ab2d6f92bc667a02485f258c064e http://test.webbtc.com/tx/f1ebaf4604158a8a385cb55d1c0ca5efde98ab2d6f92bc667a02485f258c064e.json I thought all transactions are currently versioned 1. How come this is 0? Does anyone have any clue as to why? I am not able to find any documentations on version 0 transactions Title: Re: Transaction Version (expected to be 1 but I got 0) Post by: maaku on February 19, 2014, 08:43:48 AM A transaction's nVersion field may be set to any value. I don't suggest writing code that does so, however, as you place yourself at risk against future soft-fork changes which give the nValue field meaning.
|