Raymond Chu

This is likely partially addressed with - https://github.com/ProvableHQ/snarkVM/pull/2884

What are the heavy parts of the `check_next_block` call? The Transaction verification results should be cached already; are there other parts of the verification process that are costly? Maybe the...

How relevant/applicable is this with the new Process + Stack changes? I assume the optimizations here using caches may still be useful, but there are quite a number of merge...

We currently have an implementation of this in snarkOS via a REST endpoint: `GET //program/{programID}/mapping/{mappingName}?all={true}&metadata={true}` https://github.com/ProvableHQ/snarkOS/blob/6d11788df01e1173f2c92e784d710d7c6bab9868/node/rest/src/routes.rs#L232-L233. This is an expensive operation because a mapping can be enormous, so the route...

Does this apply to compiled `snarkOS` binaries via `cargo install --path .`? What does that process look like? Additional documentation in the PR description/in the code would be helpful to...

So if `cargo install --locked --features test_targets --path .` is used, the `snarkOS` binary will always have the `test_targets` version of the coinbase targets? We should have some failsafes where...

You can query your public credits with an API request - https://api.explorer.provable.com/v1/mainnet/program/credits.aleo/mapping/account/?metadata=true OR looking up your address in a public explorer like - https://explorer.provable.com/

I believe this was due to the networks not being live or the boostrap nodes being down. Please reopen this issue if you still experience the same problem.

This is a known issue, but thank you for flagging this again. Our current recommendations for mitigations is for Validators to run their own "Core Clients" which acts as the...

Should we addressed with https://github.com/AleoNet/snarkOS/pull/3348