You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
after a lot of discussion between @Fi3, @TheBlueMatt, @Sjors, @GitGab19 and myself, we realized that some aspects of the spec were not clear
in summary:
"async" terminology is causing a lot of confusion... different people hold different interpretations of the term, so we need more clear wording around this feature
after a lot of discussion between @Fi3, @TheBlueMatt, @Sjors, @GitGab19 and myself, we realized that some aspects of the spec were not clear
in summary:
ShortIds
andSipHash
were originally introduced as a strategy for optimizing bandwidth ofDeclareMiningJob
, but it was later realized that the computation trade-offs don't really seem to justify it (as discussed in Make more clear how we use the block header to calculate the txs short ids (job declarator) #99)DeclareMiningJob
message needs aprev_hash
field, so that JDS can avoid acknowledging work for old tipsSubmitSolution
message needs aversion
field so that JDS can reconstruct the block before propagation (as it was partially rolled)extranonce_size
,min_ntime
andversion
fields ofSetCustomMiningJob
message are redundant and should be removedThe text was updated successfully, but these errors were encountered: