Topic: Trasactions with "sequence":0 (Read 829 times)
Sequence numbers aren't very useful today because tx replacement is disabled. Nothing stops you setting a non-MAX_INT sequence number if you like though. It's probably indeed a separate implementation that isn't quite following the standard behavior.
If you view the last transaction in block 110300 you can see it has a line saying "sequence":0
https://blockexplorer.com/rawtx/c99c49da4c38af669dea436d3e73780dfdb6c1ecf9958baa52960e8baee30e73
This is also true for the last transaction in block 112696, for two transactions near the end of 113341 and the last three in 113599 but for no more to date (block 129000ish)
Does anyone know what was going on? I presume someone was testing a non-standard client.
ByteCoin
https://blockexplorer.com/rawtx/c99c49da4c38af669dea436d3e73780dfdb6c1ecf9958baa52960e8baee30e73
This is also true for the last transaction in block 112696, for two transactions near the end of 113341 and the last three in 113599 but for no more to date (block 129000ish)
Does anyone know what was going on? I presume someone was testing a non-standard client.
ByteCoin
Jump to: