Have a couple of questions in regards to the nVersion area within the transaction serialization format and they’re associated to the aim of this area.

  1. What does this area inform us? Within the sense that whether it is model 1, the transaction fields are like this, whether it is model 2, the transaction fields are like that, and so forth. I do not see this area being supposed for this. I solely know that the transaction model have an effect on nSequence. If the model is 1, the nSequence worth has no function (it was supposed as a substitute area, however is now disabled and you’ll put no matter you need in model 1) and if model is 2 then nSequence is used for relative time lock. What are the opposite functions of this area, if any?

  2. What are all the usual and consensus guidelines for this area? Can it have any worth below the consensus guidelines, however only one and a couple of below the usual guidelines?

  3. If there’s consensus and customary guidelines for this area, how are modifications made to this area? For instance, if the consensus and customary rule for this area was that it should be 1, then how was the addition of a relative timelock context to nSequences within the presence of model 2 achieved? That’s, how was it potential that the worth of this area can now be additionally 2 to be able to add this transformation? How will model 3, 4, 5 or 10 be enabled? Exhausting fork?

LeaBit is a brand new contributor to this website. Take care in asking for clarification, commenting, and answering.
Try our Code of Conduct.