juno icon indicating copy to clipboard operation
juno copied to clipboard

Starknet client implementation.

Results 334 juno issues
Sort by recently updated
recently updated
newest added

**Describe the bug** Following current instructions in gojuno.xyz means that every time you run juno, state is wiped. We need to have persistent storage on disk or on a docker...

devops

We should have a clear description of how to read and use the logs correctly. See E.g., https://docs.nethermind.io/nethermind/ethereum-client/logging-configuration For some good examples.

devops

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...

good first issue

Right now we use codecov for test coverage. There are some base tools included with Go that might be enough. We should check if it could be replaced, and if...

good first issue
dependencies

RIght now, you can push changes to docs and break them in main.

documentation
devops

This functionality will enable support for the `get_transaction_id_by_hash` and `get_transaction_hash_by_id` routes in the REST API. The transaction id can be thought of as a global index of the transaction in...

db
core

Add documentation in https://gojuno.xyz for trie, based on [this](#129)

documentation

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...

good first issue
crypto

We're not using the server code, but are instead using Juno as a RPC client. The client package depends on some `internal` bits which then pull in `mdbx` which introduces...

rpc

**Describe the bug** Each time the app encounters an error that we should not recover, instead of Panic, and printing all the stack traces, we should handle that error, print...

good first issue
core