Bitcoin Stack Change is a query and reply web site for Bitcoin crypto-currency fans. It solely takes a minute to enroll.
Anyone can ask a query
Anyone can reply
The most effective solutions are voted up and rise to the highest
Requested
Seen
9 instances
Have just a few questions in regards to the nVersion area within the transaction serialization format and they’re associated to the aim of this area.
-
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, thenSequenceworth 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 thennSequenceis used for relative time lock. What are the opposite functions of this area, if any? -
What are all the usual and consensus guidelines for this area? Can it have any worth beneath the consensus guidelines, however just one and a pair of beneath the usual guidelines?
-
If there’s consensus and commonplace guidelines for this area, how are modifications made to this area? For instance, if the consensus and commonplace 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 doable that the worth of this area can now be additionally 2 as a way to add this modification? How will model 3, 4, 5 or 10 be enabled? Arduous fork?
requested 2 hours in the past
LeaBit is a brand new contributor to this web site. Take care in asking for clarification, commenting, and answering.
Try our Code of Conduct.