Josh Klopfenstein
Josh Klopfenstein
## Description Juno panics if only `--sync-enable` is provided. We can fix this by removing the need for the `--sync-trustless` param. ## Changes - Remove the `--sync-trustless` config param. Instead,...
Fixes #309 ## Description Right now there is tight coupling in the sync process (mostly centered around the enormous [`Synchronizer`](https://github.com/NethermindEth/juno/blob/1543782b96584696b046d147569d219efd268c76/internal/sync/sync.go#L27) struct). This PR "modularizes" the sync process by making the...
**Problem** If an error is caught in [`checkErrChs`](https://github.com/NethermindEth/juno/blob/7735bff86b9e243266dbe6070a329a949409bda0/cmd/juno/main.go#L397), we immediately exit with a log message. **Solution** Call [`shutdown`](https://github.com/NethermindEth/juno/blob/7735bff86b9e243266dbe6070a329a949409bda0/cmd/juno/main.go#L362), attempting to exit cleanly without a stack trace.
**Problem** The documentation site is deployed on every commit to the main branch. This is confusing to users who may only use the latest release. **Solution** Deploy docs for each...
**The Problem** Right now, we sync state from L1 and blocks/transactions/etc. from L2 in the same logic. This makes for an enormous `Synchronizer` object that encapsulates a myriad of unrelated...
Right now, we don't test anything in the main package (`cmd/juno`). With [recent](https://github.com/NethermindEth/juno/pull/288) [PRs](https://github.com/NethermindEth/juno/pull/295), the main package has become much more modular and easier to test. This is also be...
The `divMod` function in [points.go](https://github.com/NethermindEth/juno/blob/64ec93002abdc74e44bf6b20995a192bb07236fd/pkg/crypto/pedersen/points.go#L2050-L2058) is a major bottleneck when applying state diffs to the local database. Right now, we are using `big.Int`s, which are inefficient. **Solution** An implementation of...
## Description Implement a logger interface and a `Log` struct that uses `zap.SugaredLogger` under the hood. Note: this PR is not directly designed to make log messages more descriptive. ##...
## Description Clarify logs by adjusting the level of some messages (mostly from `Info` -> `Debug`) and by editing the messages themselves. ## Changes: - Adjust logs - Clarify messages...
**Problem** Right now, we require the zap logging library directly (transitively requiring all code to use zap for logging as well). Furthermore, we frequently import a global logger rather than...