Releases: NethermindEth/juno
v0.14.3-rc0
This release focuses on RPC stability improvements and bug fixes.
- Modified custom versioned constants handling: If you use custom versioned constants, you'll need to update your configuration to match the new structure.
Changed
- Enhanced versioned constants: CUSTOM_VERSIONED_CONSTANTS now stores a map of custom files, fetching from this map first before falling back to blockifier for versions not in the map.
- Updated to Go 1.24
- HTTP timeout defaults for better connection handling
Fixed
- Event filtering now correctly handles processed events when starting from pending state
- Storage proof generation properly returns BLOCK_NOT_FOUND in specific edge cases (RPC v8)
- Empty storage keys in getStorageProof requests no longer cause errors (RPC v8)
- Improved L1 interaction with more reliable finalized block retrieval
Full Changelog: v0.14.2...v0.14.3-rc0
v0.14.2
This release restores backward compatibility for RPC v0.6 and v0.7 by reverting the change to the revert_error
message in the starknet_call
response when an entry point is not found.
Fixed
- RPC v0.6 / v0.7: Restored the previous error message for missing entry points in
starknet_call
(#2650) by @AnkushinDaniil
Full Changelog: v0.14.1...v0.14.2
v0.14.1
This release addresses an issue with traceBlockTransactions
failing due to class caching issues triggered by specific RPC call sequences.
Fixed
- RPC v0.6: Issue with pending blocks in
TransactionReceiptByHash
method (#2642) by @hudem1 - Tracing: Fixed class cache poisoning causing failures in
traceBlockTransactions
(#2644) by @infrmtcs
Full Changelog: v0.14.0...v0.14.1
v0.14.0
New release to support Starknet v0.13.5.
The changes from the previous release (v0.13.3) to this are small but still very important. We decided to name it v0.14.0 instead of v0.13.4 to give a clear vision that the previous release wouldn't support the latest version of Starknet.
You must upgrade to this release before Starknet 0.13.5 is rolled out on the testnets and mainnet.
Added
- Support for Starknet v0.13.5: Ensuring compatibility with the latest Starknet version.
Fixed
- Transaction status subscription hanging: Resolved an issue where the subscription for the starknet_subscribeTransactionStatus method could get stuck.
Full Changelog: v0.13.3...v0.14.0
v0.13.3
This release includes several important fixes to improve RPC stability and transaction handling.
Fixed
- Fixed fee estimation issues:
- Resolved failures due to absence of L1 data gas
- Corrected VM versioned constants selection for accurate fee calculation
- Fixed extremely large
gas_consumed
values instarknet_estimateFee
andstarknet_simulate
responses
- Fixed transaction trace format to match specifications across all RPC versions
- Resolved JSON marshalling errors in
starknet_call
for RPC v6-7 that caused empty responses - Added proper
ENTRYPOINT_NOT_FOUND
error handling forstarknet_call
Full Changelog: v0.13.2...v0.13.3
v0.13.2
This hot fix release focuses on resolving issues with starknet_getBlockWithTxs
in RPC v0.7 and v0.6, where some transactions returned an empty response.
Fixed
- RPC v6 and v7: Fixed an issue where
starknet_getBlockWithTxs
sometimes returned an empty response for certain transactions, causing errors.
by @hudem1 in #2575 - RPC v0.8: No longer support adding transactions with versions lower than v3.
by @AnkushinDaniil in #2544
Full Changelog: v0.13.1...v0.13.2
v0.13.1
This release restores backward compatibility for RPC v0.7 by reintroducing transaction_hash
in starknet_getBlockWithReceipts
, along with several minor improvements.
Fixed
- Restored
transaction_hash
instarknet_getBlockWithReceipts
for v0_7 compatibility (#2528)
Full Changelog: v0.13.0...v0.13.1
v0.13.0
This release focuses on RPC v0.8 support and compatibility with upcoming Starknet v0.13.4.
⚠️ Important Upgrade Notice ⚠️
- Users must upgrade before Starknet v0.13.4 deployment to maintain sync capability
- Database migration:
- Backup your database before upgrading
- Migration may take several minutes or more depending on hardware
- WARNING: Interrupting the migration may corrupt the entire database
Breaking Changes
- The
--eth-node
flag is now mandatory (use--disable-l1-verification
if L1 verification is not needed)
Added
- RPC v0.8.0-rc3 as the default version under
/
and/rpc/v0_8
- RPC v0.7 remains available for compatibility -
/rpc/v0_7
- RPC v0.6 remains available for compatibility -
/rpc/v0_6
- RPC v0.7 remains available for compatibility -
- WebSocket subscription support
- Dynamic runtime log level control via HTTP
- Small DB improvements by adding a dedicated Key type
- Support for the latest Blockifier version
Changed
- Deprecated
juno_subscribeNewHeads
,juno_unsubscribe
,juno_getProof
in favor ofstarknet_
prefixed methods
Fixed
- Removed
transaction_hash
from thegetBlockWithReceipts
response (still available in the receipt) as it was not compliant with the spec.
Full Changelog: v0.12.5...v0.13.0
v0.12.5
This release focuses on improving performance and ensuring stability across key functionalities.
Added
- Optimized Sync and RPC Performance: Increased the default
db-cache-size
to1GiB
, significantly improving synchronization speed and reducing response times for key operations. (#2244)
Changed
- Dependency Alignment: Updated internal dependencies to maintain compatibility and streamline the build process. (#2293)
Fixed
- Enhanced Compilation Error Handling: Improved handling of certain edge cases during contract compilation to ensure better system reliability. (#2297)
Full Changelog: v0.12.4...v0.12.5
v0.12.4
This release focuses on supporting Starknet 0.13.3.
⚠️ Important Upgrade Notice ⚠️
You must upgrade to this release before Starknet 0.13.3 is rolled out on the testnet and mainnet. Failing to do so will result in the inability to sync new (Starknet 0.13.3) blocks.
To get the schedule for upcoming Starknet updates, follow this thread: Starknet Roadmap Updates.
Added
- Support for Starknet v0.13.3: Ensuring compatibility with the latest Starknet version.
Full Changelog: v0.12.3...v0.12.4