Raymond Chu
Raymond Chu
@ljedrz Does this PR need any refreshing (cargo fmt looks to be failing) since it hasn't been merged in a while
Yea seems like it's due to a CI versioning issue. Can revisit once CI is run
Needs further tweaking on snarkVM metrics side. Relevant PR - https://github.com/ProvableHQ/snarkOS/pull/3064
Might be a good opportunity to expand our metrics macro usage as well. We are currently bound to a single type of `histogram` and `gauge` usage, despite the underlying `metrics`...
The program name and function (or closure) name should be easily accessible from the stack used the evaluate the instruction. However, the program line number might be difficult.
@d0cd @kaimast ^From our CLI discussions in https://github.com/ProvableHQ/snarkOS/pull/3759#discussion_r2289244686
Would the `value_to_json` and `mapping_to_json` functions be more useful in snarkVM?
`1 + (3f+1)/3 = n/3 +1` is the availability threshold, which in theory should be sufficient for having at least 1 honest response. However that indeed does not take stake...
Ah i missed that. It is still unclear to me where to add additional ledger tests that require the `test` feature. For now I lumped a new test into `ledger-with-valid-solutions`,...
Seems quite beneficial, if integrated properly, I can't think of any real downsides to this besides general state bloat. 2 things to consider: 1. Design should properly reflect a default...