-
Notifications
You must be signed in to change notification settings - Fork 293
dev: Upgrade Madara JSON-RPC specs to v0.6.0-rc5 #1291
Comments
This issue will be solved gradually starting with a v0.5.1 (last stable) full upgrade. Please reffer to the v0.5.1 release. |
Now that #1313 is about to be merged to implement v0.5.1 and v0.6.0 has been released here: https://github.com/starkware-libs/starknet-specs/releases. We can continue on another issue. I'll comment it under here and close it when v0.5.1 is merged. |
There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale. |
I can help by grabbing this issue Imported BROADCASTED_DECLARE_TXN in write API. |
0.6.0 being tracked #1352 |
Upgrade Madara JSON-RPC specs to v0.6.0-rc5
Overview
This issue concerns the implementation of the latest version of Starknet's JSON-RPC API: v0.6.0-rc5 within Madara (currently on v0.4.0) to ensure and maintain full compatibility with Starknet.
Detailed Description
Since version 0.4.0 of Starknet RPC, here's what has changed:
v0.5.1 New Features
broadcasted declare txn
: Separated fromdeclare txn
.starknet_specVersion
endpoint.l1_gas_price
andstarknet_version
to block header.execution_resources
.CONTRACT_ERROR
Enhancement: Included string data.starknet_getTransactionStatus
and removedstarknet_pendingTransactions
.PENDING_STATE_UPDATE
Schema Fix: Addressed schema issues.broadcasted_declare_txn_v1
Fields: Added missing fields.traceBlockTransaction
error type.v0.6.0 New Features
BROADCASTED_DECLARE_TXN
in write API.VALIDATION_FAILURE
.starknet_estimateFee
.traceTransactions
andestimateFee
.STRK
toFRI
.TRANSACTION_EXECUTION_ERROR
.SKIP_VALIDATE
flag tostarknet_estimateFee
.FEE_ESTIMATE
.DECLARE_TXN_V1
version.FELT
and made built-in resources optional.PENDING_DEPLOY_TXN_RECEIPT
.EMITTED_EVENT
in pending block.PENDING_BLOCK_HEADER
.state_diff
toL1_HANDLER
andDELEGATE
call type.Goals/Objectives
To implement all the new features of the latest version as well as to reference here any potential problems and changes to track the status of the implementation.
Potential Challenges/Risks
Track potential risks or problems of the implementation: TBD.
Testing
Update and set up tests for the implementation: TBD.
Timeline
I expect the implementation to take around one week: TBD.
The text was updated successfully, but these errors were encountered: