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
Re-implemented Local Resource Conservation in Rust with all the interfaces and components, new code is slightly unit tested and error handling is more than summary for now: https://github.com/PurpleTimez/rust-lrc
Understanding that LRC is testing code only and that the interfaces will change heavily with the progress of the protocol. I still have 2 observations so far.
Firstly, should all internal opportunity_cost math be done in f64 or float64, like floating arithmetic can be cumbersome to handle and I'm not sure it has a real impact on reputation-based jamming handling ?
Secondly, all the resolution period and block_time, I think LocalResourceManager internal interface would gain to be defined with a block hash and timestamp, that way the opportunity_cost can be adapted to the real difficulty period ?
I'll see to integrate rust-lrc in the rust-lightning sample to test this further, and I think I still have a branch somewhere trying to add rust-lightning support in sim-ln. I won't have that much time to make progress on that during the coming weeks, though I
don't forget go back to it.
The text was updated successfully, but these errors were encountered:
Re-implemented Local Resource Conservation in Rust with all the interfaces and components, new code is slightly unit tested and error handling is more than summary for now: https://github.com/PurpleTimez/rust-lrc
Understanding that LRC is testing code only and that the interfaces will change heavily with the progress of the protocol. I still have 2 observations so far.
Firstly, should all internal
opportunity_cost
math be done inf64
orfloat64
, like floating arithmetic can be cumbersome to handle and I'm not sure it has a real impact on reputation-based jamming handling ?Secondly, all the resolution period and
block_time
, I thinkLocalResourceManager
internal interface would gain to be defined with a block hash and timestamp, that way theopportunity_cost
can be adapted to the real difficulty period ?I'll see to integrate
rust-lrc
in the rust-lightning sample to test this further, and I think I still have a branch somewhere trying to add rust-lightning support insim-ln
. I won't have that much time to make progress on that during the coming weeks, though Idon't forget go back to it.
The text was updated successfully, but these errors were encountered: