v0.6.0: introduce v3 transactions

[ArielElp]

This change is 

[ShahakShama]

Reviewed 1 of 1 files at r1, all commit messages.
Reviewable status: all files reviewed, 3 unresolved discussions (waiting on @ArielElp and @yair-starkware)

---

api/starknet_api_openrpc.json line 2078 at r1 (raw file):

                                "title": "Version",
                                "description": "Version of the transaction scheme",
                                "$ref": "#/components/schemas/NUM_AS_HEX"

Change into enum with single option (to avoid cases where more than one schema is valid)

---

api/starknet_api_openrpc.json line 2200 at r1 (raw file):

                        "title": "Version",
                        "description": "Version of the transaction scheme",
                        "$ref": "#/components/schemas/NUM_AS_HEX"

Same as above

---

api/starknet_api_openrpc.json line 2436 at r1 (raw file):

                                "title": "Version",
                                "description": "Version of the transaction scheme",
                                "$ref": "#/components/schemas/NUM_AS_HEX"

Same as above

[yair-starkware]

Reviewable status: all files reviewed, 5 unresolved discussions (waiting on @ArielElp)

a discussion (no related file):
In some cases you use allOf and in some cases you don't

---

---

api/starknet_api_openrpc.json line 2410 at r1 (raw file):

                "title": "Invoke transaction V3",
                "description": "initiates a transaction from a given account",
                "allOf": [

Add "additionalProperties": false
Preferably to all of the objects

[ArielElp]

Reviewed 1 of 2 files at r2.
Reviewable status: 1 of 2 files reviewed, 5 unresolved discussions (waiting on @ShahakShama and @yair-starkware)

---

api/starknet_api_openrpc.json line 2078 at r1 (raw file):

Previously, ShahakShama wrote…

Change into enum with single option (to avoid cases where more than one schema is valid)

Done.

---

api/starknet_api_openrpc.json line 2200 at r1 (raw file):

Previously, ShahakShama wrote…

Same as above

Done.

---

api/starknet_api_openrpc.json line 2410 at r1 (raw file):

Previously, yair-starkware (Yair) wrote…

Add "additionalProperties": false
Preferably to all of the objects

are potential collisions solved by explicit requirements in version?

---

api/starknet_api_openrpc.json line 2436 at r1 (raw file):

Previously, ShahakShama wrote…

Same as above

Done.

[yair-starkware]

Reviewed 2 of 2 files at r4, all commit messages.
Reviewable status: all files reviewed, 3 unresolved discussions (waiting on @ShahakShama)

---

api/starknet_api_openrpc.json line 2410 at r1 (raw file):

Previously, ArielElp wrote…

are potential collisions solved by explicit requirements in version?

That works too

[ShahakShama]

Reviewed all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @ArielElp)