Skip to content

Releases: starkware-libs/starknet-specs

v0.7.1

24 Mar 07:59
76bdde2
Compare
Choose a tag to compare

Minor fix adding the execution_resources property to l1_handler transaction traces. This is already the behavior of full nodes, so no changes are expected from the POV of dapps communicating with the json-rpc. Note that /v0_7 URLs will refer to the latest v0.7.x, that is, there is no need to refer to patch versions explicitly when interacting with Starknet nodes.

Changelog

Full Changelog: v0.7.0...v0.7.1

v0.7.0

14 Mar 07:27
4233164
Compare
Choose a tag to compare

Starknet's JSON-RPC v0.7.0. This version captures the changes associated with Starknet v0.13.1, allowing nodes to externalize information related to EIP4844. Dapps that communicate with nodes over v0.6.0 of the specs will continue to work, but will not enjoy the lower fee estimates resulting by the introduction of blobdata.

Changelog

Full Changelog: v0.6.0...v0.7.0

v0.7.0-rc2

03 Mar 14:05
7ae9e7b
Compare
Choose a tag to compare
v0.7.0-rc2 Pre-release
Pre-release

Changelog

  • Fix: add 4844-related fields to the pending block header by @ArielElp in #194
  • Spec organization: Introduce TXN_RECEIPT_WITH_BLOCK_INFO and remove the pending receipts objects by @ShahakShama in #195

Full Changelog: v0.7.0-rc1...v0.7.0-rc2

v0.7.0-rc1

22 Feb 08:11
c7a5e4f
Compare
Choose a tag to compare
v0.7.0-rc1 Pre-release
Pre-release

Changelog

  • refactor BLOCK_BODY_WITH_RECEIPTS by @ArielElp in #191
  • fix: make data_gas related fields required in the block header by @ArielElp in #193

Full Changelog: v0.7.0-rc0...v0.7.0-rc1

v0.7.0-rc0

02 Feb 08:56
159fb9c
Compare
Choose a tag to compare
v0.7.0-rc0 Pre-release
Pre-release

The first release candidate for Starknet's JSON-RPC v0.7.0. This version is aimed to be supported by nodes after the Starknet upgrade to v0.13.1, although dapps can keep communicating with nodes over v0.6.0 of the specs.

Changelog

Full Changelog: v0.6.0...v0.7.0-rc0

v0.6.0

07 Dec 13:15
4966593
Compare
Choose a tag to compare

Chanelog

  • Change execution resource counters to integers by @OmriEshhar1 in #147
  • Allow EMITTED_EVENT to contain events from the pending block by @ShahakShama in #151
  • Disallow block_hash/block_number/new_root in the PENDING_BLOCK_HEADER schema by @OmriEshhar1 in #154
  • Introduce v3 transactions by @ArielElp in #149
  • Add state_diff to L1_HANDLER and DELEGATE call type by @ArielElp in #161
  • Add resources to internal calls within a trace by @ArielElp in #160
  • add stricter restrictions on v3 fields by @ArielElp in #169
  • Make trace fields optional (as in 0.5.1) by @ArielElp in #172
  • Refactor traceTransactions and estimateFee, and rename STRK to FRI by @ArielElp in #174
    • use the name fri for $10^{-18}$ strk
    • added TRANSACTION_EXECUTION_ERROR
    • added the SKIP_VALIDATE flag to starknet_estimateFee
    • clarified semantics of simulate and estimate: simulateTransactions should provide traces whenever possible and reply with TRANSACTION_EXECUTION_ERROR in cases of validation failure or internal error. estimateFee however is expected to fail with TRANSACTION_EXECUTION_ERROR when a transaction reverts, in order to avoid a scenario where transactions that are known to revert are sent to the network by mistake.

Bug fixes

New Contributors

Full Changelog: v0.5.0...v0.6.0

v0.6.0-rc5

03 Dec 16:57
06ea3b7
Compare
Choose a tag to compare
v0.6.0-rc5 Pre-release
Pre-release

Changelog

Full Changelog: v0.6.0-rc4...v0.6.0-rc5

v0.6.0-rc4

29 Nov 11:42
6e0d2ce
Compare
Choose a tag to compare
v0.6.0-rc4 Pre-release
Pre-release

Changelog

New Contributors

Full Changelog: v0.6.0-rc3...v0.6.0-rc4

v0.6.0-rc3

27 Nov 14:48
Compare
Choose a tag to compare
v0.6.0-rc3 Pre-release
Pre-release

Changelog

  • Refactor traceTransactions and estimateFee, and rename STRK to FRI by @ArielElp in #174
    • use the name fri for $10^{-18}$ strk
    • added TRANSACTION_EXECUTION_ERROR
    • added the SKIP_VALIDATE flag to starknet_estimateFee
    • clarified semantics of simulate and estimate: simulateTransactions should provide traces whenever possible and reply with TRANSACTION_EXECUTION_ERROR in cases of validation failure or internal error. estimateFee however is expected to fail with TRANSACTION_EXECUTION_ERROR when a transaction reverts, in order to avoid a scenario where transactions that are known to revert are sent to the network by mistake.

Full Changelog: v0.6.0-rc2...v0.6.0-rc3

v0.6.0-rc2

22 Nov 23:02
237fe16
Compare
Choose a tag to compare
v0.6.0-rc2 Pre-release
Pre-release

Changelog

New Contributors

Full Changelog: v0.6.0-rc1...v0.6.0-rc2