v0.14.0 transactions reference #1636

LandauRaz · web-flow · commit 7fc1a3cf2489 · 2025-06-26T10:40:28.000-04:00
diff --git a/components/Starknet/modules/resources/pages/transactions-reference.adoc b/components/Starknet/modules/resources/pages/transactions-reference.adoc
@@ -5,13 +5,13 @@
 To review how transaction appear in the Starknet API, see https://github.com/starkware-libs/starknet-specs/blob/b5c43955b1868b8e19af6d1736178e02ec84e678/api/starknet_api_openrpc.json[starknet_api_openrpc.json^].
 ====
 
-== `INVOKE` transaction
+== `INVOKE` v3
 
-=== v3 transaction fields
+=== Transaction fields
 
 include::partial$snippet_transaction_fields_master_table.adoc[]
 
-=== v3 hash calculation
+=== Hash calculation
 
 The `INVOKE` v3 transaction hash is calculated as a Poseidon hash over the given transaction elements, specifically:
 
@@ -36,7 +36,116 @@ Where:
 * `invoke` is a constant prefix string, encoded in ASCII.
 include::partial$snippet_transaction_params.adoc[]
 
-=== v1 transaction fields
+== `DECLARE` v3
+
+:declare:
+
+The `DECLARE` transaction introduces new contract classes into the state of Starknet, enabling other contracts to deploy instances of those classes or use them in a library call. For more information, see xref:architecture-and-concepts:smart-contracts/contract-classes.adoc[contract classes].
+
+=== Transaction fields
+
+include::partial$snippet_transaction_fields_master_table.adoc[]
+
+=== Hash calculation
+
+The hash of a v3 `DECLARE` transaction is computed as follows:
+
+[,subs="quotes"]
+----
+declare_v3_tx_hash = _h_(
+  "declare",
+  version,
+  sender_address,
+  _h_(tip, l1_gas_bounds, l2_gas_bounds, l1_data_gas_bounds),
+  _h_(paymaster_data),
+  chain_id,
+  nonce,
+  data_availability_modes,
+  _h_(account_deployment_data),
+  class_hash,
+  compiled_class_hash
+)
+----
+
+Where:
+
+* `declare` is a constant prefix string, encoded in ASCII.
+include::partial$snippet_transaction_params.adoc[]
+* `class_hash` is the hash of the contract class. See xref:architecture-and-concepts:smart-contracts/class-hash.adoc#computing_the_cairo_1_class_hash[Class Hash] for details about how the hash is computed
+* `compiled_class_hash` is the hash of the compiled class
+generated by the Sierra->Casm compiler that is used in Starknet
+
+== `DEPLOY_ACCOUNT` v3
+
+:deploy_account:
+
+Since StarkNet v0.10.1 the `DEPLOY_ACCOUNT` transaction replaces the `DEPLOY` transaction for deploying account contracts.
+
+To use it, you should first pre-fund your new account address so that you can pay the transaction fee. You can then send the `DEPLOY_ACCOUNT` transaction.
+
+For more information, see xref:architecture-and-concepts:accounts/deploying-new-accounts.adoc[].
+
+=== Transaction fields
+
+include::partial$snippet_transaction_fields_master_table.adoc[]
+
+=== Hash calculation
+
+The hash of a `DEPLOY_ACCOUNT` transaction is computed as follows:
+
+[,subs="quotes"]
+----
+deploy_account_v3_tx_hash = _h_(
+  "deploy_account",
+  version,
+  contract_address,
+  _h_(tip, l1_gas_bounds, l2_gas_bounds, l1_data_gas_bounds),
+  _h_(paymaster_data),
+  chain_id,
+  nonce,
+  data_availability_modes,
+  _h_(constructor_calldata),
+  class_hash,
+  contract_address_salt
+)
+----
+
+Where:
+
+* `deploy_account` is a constant prefix string, encoded in ASCII.
+include::partial$snippet_transaction_params.adoc[]
+* `class_hash` is the hash of the xref:architecture-and-concepts:smart-contracts/contract-classes.adoc[contract class]. See xref:architecture-and-concepts:smart-contracts/class-hash.adoc[Class Hash] for details about how the hash is computed.
+* `contract_address` is the address of the newly deployed account. For information on how this address is calculated, see xref:architecture-and-concepts:smart-contracts/contract-address.adoc[Contract address].
+
+== Additional information
+
+=== Signature
+
+While Starknet does not have a specific signature scheme built into the protocol, the Cairo language, in which smart contracts are written, does have an efficient implementation for ECDSA signature with respect to a STARK-friendly curve. For more information, see xref:architecture-and-concepts:cryptography.adoc[].
+
+The generator used in the ECDSA algorithm is stem:[G=\left(g_x, g_y\right)] where:
+
+stem:[g_x=874739451078007766457464989774322083649278607533249481151382481072868806602] stem:[g_y=152666792071518830868575557812948353041420400780739481342941381225525861407]
+
+=== Chain ID
+
+Chain IDs are given as numbers, representing the ASCII encoding of specific constant strings, as illustrated by the following Python snippet:
+
+[source,python]
+----
+chain_id = int.from_bytes(value, byteorder="big", signed=False)
+----
+
+The following constants are currently used. They correspond to the chain IDs that Starknet currently supports:
+
+* `SN_MAIN` for Starknet's main network.
+* `SN_SEPOLIA` for Starknet's public testnet on Sepolia.
+
+== Legacy information
+
+=== `INVOKE` v1
+
+==== Transaction fields
 
 [%autowidth.stretch]
 |===
@@ -51,7 +160,7 @@ include::partial$snippet_transaction_params.adoc[]
 When the fields that comprise a transaction change, either with the addition of a new field or the removal of an existing field, then the transaction version increases.
 |===
 
-=== v1 hash calculation
+==== Hash calculation
 
 The `INVOKE` v1 transaction hash is calculated as a hash over the given transaction elements,
 specifically:
@@ -78,7 +187,9 @@ Where:
 * `_h_` is the xref:architecture:cryptography.adoc#pedersen_hash[Pedersen] hash
 
 
-=== v0 hash calculation
+=== `INVOKE` v0
+
+==== Hash calculation
 
 The hash of a v0 `INVOKE` transaction is computed as follows:
 
@@ -103,55 +214,9 @@ Where:
 
 :!invoke:
 
-== `DECLARE` transaction
+=== `DECLARE` v2
 
-:declare:
-
-The `DECLARE` transaction introduces new contract classes into the state of Starknet, enabling other contracts to deploy instances of those classes or use them in a library call. For more information, see https://book.cairo-lang.org/ch100-01-contracts-classes-and-instances.html[the Cairo Book].
-
-// [IMPORTANT]
-// ====
-// You can only declare Cairo classes with v2 and v3 of the `DECLARE` transaction type.
-//
-// v1, which declares Cairo 0 classes, is deprecated and will be removed in a future Starknet version.
-//
-// v0 is no longer supported.
-// ====
-
-=== v3 transaction fields
-
-include::partial$snippet_transaction_fields_master_table.adoc[]
-
-=== v3 hash calculation
-
-The hash of a v3 `DECLARE` transaction is computed as follows:
-
-[,subs="quotes"]
-----
-declare_v3_tx_hash = _h_(
-  "declare",
-  version,
-  sender_address,
-  _h_(tip, l1_gas_bounds, l2_gas_bounds, l1_data_gas_bounds),
-  _h_(paymaster_data),
-  chain_id,
-  nonce,
-  data_availability_modes,
-  _h_(account_deployment_data),
-  class_hash,
-  compiled_class_hash
-)
-----
-
-Where:
-
-* `declare` is a constant prefix string, encoded in ASCII.
-include::partial$snippet_transaction_params.adoc[]
-* `class_hash` is the hash of the contract class. See https://book.cairo-lang.org/ch100-01-contracts-classes-and-instances.html[the Cairo Book^] for details about how the hash is computed
-* `compiled_class_hash` is the hash of the compiled class
-generated by the Sierra->Casm compiler that is used in Starknet
-
-=== v2 transaction fields
+==== Transaction fields
 
 [%autowidth.stretch]
 |===
@@ -168,7 +233,7 @@ generated by the Sierra->Casm compiler that is used in Starknet
 When the fields that comprise a transaction change, either with the addition of a new field or the removal of an existing field, then the transaction version increases.
 |===
 
-=== v2 hash calculation
+==== Hash calculation
 
 The hash of a v2 `DECLARE` transaction is computed as follows:
 
@@ -193,7 +258,9 @@ Where:
 * `class_hash` is the hash of the contract class. See https://book.cairo-lang.org/ch100-01-contracts-classes-and-instances.html[the Cairo Book^] for details about how the hash is computed
 * `compiled_class_hash` is the hash of the compiled class generated by the Sierra->Casm compiler that is used in Starknet
 
-=== v1 transaction fields
+=== `DECLARE` v1
+
+==== Transaction fields
 
 [NOTE]
 ====
@@ -213,8 +280,7 @@ The `DECLARE` v1 transaction was used to declare Cairo 0 classes.
 When the fields that comprise a transaction change, either with the addition of a new field or the removal of an existing field, then the transaction version increases.
 |===
 
-
-=== v1 hash calculation
+==== Hash calculation
 
 The hash of a v1 `DECLARE` transaction is computed as follows:
 
@@ -242,7 +308,9 @@ computed.
 * `_h_` is the xref:architecture:cryptography.adoc#pedersen_hash[Pedersen] hash
 
 
-=== v0 hash calculation
+=== `DECLARE` v0
+
+==== Hash calculation
 
 [NOTE]
 ====
@@ -275,49 +343,9 @@ Where:
 
 :!declare:
 
-== `DEPLOY_ACCOUNT` transaction
-
-:deploy_account:
-
-Since StarkNet v0.10.1 the `DEPLOY_ACCOUNT` transaction replaces the `DEPLOY` transaction for deploying account contracts.
+=== `DEPLOY_ACCOUNT` v1
 
-To use it, you should first pre-fund your new account address so that you can pay the transaction fee. You can then send the `DEPLOY_ACCOUNT` transaction.
-
-For more information, see xref:architecture:accounts#deploying_new_accounts.adoc[Deploying new accounts].
-
-=== v3 transaction fields
-
-include::partial$snippet_transaction_fields_master_table.adoc[]
-
-=== v3 hash calculation
-
-The hash of a `DEPLOY_ACCOUNT` transaction is computed as follows:
-
-[,subs="quotes"]
-----
-deploy_account_v3_tx_hash = _h_(
-  "deploy_account",
-  version,
-  contract_address,
-  _h_(tip, l1_gas_bounds, l2_gas_bounds, l1_data_gas_bounds),
-  _h_(paymaster_data),
-  chain_id,
-  nonce,
-  data_availability_modes,
-  _h_(constructor_calldata),
-  class_hash,
-  contract_address_salt
-)
-----
-
-Where:
-
-* `deploy_account` is a constant prefix string, encoded in ASCII.
-include::partial$snippet_transaction_params.adoc[]
-* `class_hash` is the hash of the contract class. See https://book.cairo-lang.org/ch100-01-contracts-classes-and-instances.html[the Cairo Book^] for details about how the hash is computed.
-* `contract_address` is the address of the newly deployed account. For information on how this address is calculated, see https://book.cairo-lang.org/ch100-01-contracts-classes-and-instances.html[the Cairo Book^].
-
-=== v1 transaction fields
+==== Transaction fields
 
 [%autowidth]
 |===
@@ -332,7 +360,7 @@ include::partial$snippet_transaction_params.adoc[]
 | `version` | `FieldElement` | The transaction's version. The value is 1. +
 |===
 
-=== v1 hash calculation
+==== Hash calculation
 
 The hash of a `DEPLOY_ACCOUNT` transaction is computed as follows:
 
@@ -360,9 +388,9 @@ Where:
 
 :!deploy_account:
 
-== `DEPLOY` transaction
+=== `DEPLOY` v0
 
-=== v0 hash calculation
+==== Hash calculation
 
 If you need to retrieve the hash of an existing `DEPLOY` transaction, you can use this information to calculate the hash of the transaction.
 
@@ -389,23 +417,3 @@ Where:
 `sn_keccak` is xref:architecture:cryptography.adoc#starknet_keccak[Starknet Keccak].
 * `chain_id` is a constant value that specifies the network to which this transaction is sent. For more information, see xref:#chain_id[].
 * `contract_address` is calculated as described see https://book.cairo-lang.org/ch100-01-contracts-classes-and-instances.html[the Cairo Book^].
-
-== Additional information
-
-=== Signature
-
-While Starknet does not have a specific signature scheme built into the protocol, the Cairo language, in which smart contracts are written, does have an efficient implementation for ECDSA signature with respect to a STARK-friendly curve. For more information, see xref:architecture:cryptography.adoc[].
-
-=== Chain ID
-
-Chain IDs are given as numbers, representing the ASCII encoding of specific constant strings, as illustrated by the following Python snippet:
-
-[source,python]
-----
-chain_id = int.from_bytes(value, byteorder="big", signed=False)
-----
-
-The following constants are currently used. They correspond to the chain IDs that Starknet currently supports:
-
-* `SN_MAIN` for Starknet's main network.
-* `SN_SEPOLIA` for Starknet's public testnet on Sepolia.
