vicsn

Results 78 issues of vicsn

## Motivation In order to further debug the source of stale transmissions, we should track what they are. ## Test Plan - [ ] Succesful devnet - prerelease-v3.9.7

## 🚀 Feature We should trigger try_advancing_block_synchronization, not at a fixed interval but on specific events. It should just be the following New block locators were received All outstanding block...

feature

## Motivation This helps debugging when transactions fail to land. I'm not aware of any services which depend on the specific format of these logs at the moment. We have...

## 🚀 Feature Currently, validators share their own and their core client ip addresses out of band and manually set them as a flag to `snarkos start`. This process has...

feature

## 🚀 Feature Upgrades which e.g. change tx validation can use event or message version bumps for validators and clients respectively. This ensures that an updated node doesn't connect to...

feature
Low Priority

## 🐛 Bug Report There appears not to be any code that prevents a peer from being both a bootstrap peer and a trusted peer. If it is both, then...

bug

## 🐛 Bug Report Link to CircleCI run: https://app.circleci.com/pipelines/github/ProvableHQ/snarkVM/14155/workflows/0a197f84-44b3-43ab-a83b-3a1f4751debb/jobs/651196

bug

## 🚀 Feature This is a tracking issue to collect feedback regarding usecases and designs for light client nodes. This would be useful to reduce resource requirements for: - bridges,...

feature

## 🐛 Bug Report The CUDA feature speeds up [NTTs and MSMs](https://github.com/ProvableHQ/snarkOS/pull/3489), which is not a part of the current puzzle. This is confusing.

bug

## 🐛 Bug Report Certain snarkOS endpoints are protected by a randomly generated authentication token (generated in `fn jwt_secret`): - `get_node_address` - `get_mapping_values` - more endpoints could be coming here:...

bug