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

Fixes | Closes | Resolves # ## Description _Explanation about why the PR is necessary._ ## Changes: - Change 1 - Change 2 ## Types of changes _Leave only items...

## Description To perform a sync, we needed to execute one call to the API for each deployed contract. After this PR gets merged, this call to the feeder is...

core

The JSON RPC method `starknet_getStateUpdate` returns decimal formatted strings in its output. For example the following request: ```json { "jsonrpc": "2.0", "method": "starknet_getStateUpdate", "params": [ 0 ], "id": 1 }...

bug
good first issue
rpc

Resolves #361 ## Description Solve the problem that exists around the initial block fetched. ## Changes: - Set as default that the minimum block synced and the current block synced,...

Closes #334 ## Description Update the docker image ## Changes: - Install python dependencies inside docker image - Add workflow for uploading docker image to docker hub ## Types of...

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

cli

resolves #350, resolves #352 ## Description Fix bugs on the RPC related to errors and params management. ## Changes: - Fix `starknet_getStorageAt` params order - Add custom error types: `NewUnexpectedError`,...

rpc

**Describe the bug** When the server starts, the `starknet_blockNumber` RPC returns 0 while the first block isn’t synched, including the case when I’m restarting the sync from a block >...

core
rpc

The following error message is shown to the user sometimes which is is not valid according to the JSON RPC 2.0 specification. ```json { "jsonrpc": "2.0", "error": {}, "id": 1...

bug
rpc