Starknet 🐺🐱 (@Starknet): Devs and project buildooors

Devs and project buildooors This is your final reminder: Starknet v0.13.4 is now live on Testnet and will be deployed to Mainnet around March 17. This update introduces breaking changes that may impact your projects: the sooner you prepare, the better! So here’s your last monthly reminder to take action 🫵 1️⃣ Termination of RPC versions < v0.7 Starknet full nodes will only support RPC versions v0.7 and above. Make sure you're using an up-to-date version. Note that RPC v0.8 will be released with Starknet v0.13.4. Full node client teams are currently implementing the spec. - We recommend using it to benefit from the latest features such as storage proofs and the introduction of L2 gas. However, RPC v0.8 does not support the deprecated transaction versions 0,1,2. - If your project consumes receipts and/or traces, you should upgrade to RPC v0.8. 2️⃣ Wallet ⇄ DApp API Changes After extensive community collaboration, the Starknet Wallet <> DApp API is receiving a major update along with a new starknet-js version. This update breaks the coupling between wallets, DApps, and Starknet.js versions, enabling faster development cycles. - Migration is very very simple: Instead of using the old method of initiating an Account object returned by the wallet, you can now use WalletAccount, which abstracts the new API. Starknet-js handles the rest. - Since only RPC versions ≥ 0.7 will be supported, make sure you're using starknet-js v6.9.0 or later. Get ready for a better DevX, and a cheaper, faster Starknet on Mainnet 🫵