Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove unpublished files #746

Merged
merged 4 commits into from
Aug 15, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 0 additions & 2 deletions components/Starknet/modules/api/nav.adoc

This file was deleted.

14 changes: 0 additions & 14 deletions components/Starknet/modules/api/pages/api-reference.adoc

This file was deleted.

Original file line number Diff line number Diff line change
Expand Up @@ -3,12 +3,8 @@
[id="block_structure"]
= Block structure

In Starknet, the block is defined as a list of transactions and a block header.
In Starknet, the block is defined as a list of transactions and a block header containing the following fields:

[id="block_header"]
== Block header

The following fields define the block header:

[%autowidth]
|===
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -117,7 +117,7 @@ To avoid having to interact with both L1 and L2 when sending a message, L1 → L
The sequencer takes this fee in exchange for handling the message. The sequencer charges the fee in full upon updating the L1 state with the consumption of this message.

The fee itself is calculated in the xref:../Network_Architecture/Fees/fee-mechanism.adoc#overall_fee[same manner] as
"regular" L2 transactions. You can use the xref:documentation:cli:commands.adoc#starknet-estimate_fee[CLI] to get an estimate of an L1 → L2 message fee.
"regular" L2 transactions. You can use the xref:documentation:cli:starkli.adoc#starknet-estimate_fee[CLI] to get an estimate of an L1 → L2 message fee.

[id="structure_and_hashing_l1-l2"]
=== L1 → L2 structure and hashing
Expand Down

This file was deleted.

This file was deleted.

Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ The contract address is a unique identifier of the contract on Starknet. It is a

* `prefix` - The ASCII encoding of the constant string `STARKNET_CONTRACT_ADDRESS`.
* `deployer_address` - The deployer address, unless `deploy_from_zero` is `true`, in which case it is `0`.
* `salt` - The salt passed by the contract calling the syscall.
* `salt` - The salt passed by the contract calling the syscall, provided by the transaction sender.
* `class_hash` - See xref:./class-hash.adoc#computing_the_cairo_1_class_hash[the class hash documentation].
* `constructor_calldata_hash` - xref:Cryptography/hash-functions.adoc#pedersen_array_hash[Array hash] of the inputs to the constructor.

Expand All @@ -21,6 +21,13 @@ contract_address := pedersen(
constructor_calldata_hash)
----

[NOTE]
====
A random `salt` ensures unique addresses for smart contract deployments, preventing conflicts when deploying identical contract classes.

It also thwarts replay attacks by influencing the transaction hash with a unique sender address.
====

You can find more detail of the address computation in the https://github.com/starkware-libs/cairo-lang/blob/ed6cf8d6cec50a6ad95fa36d1eb4a7f48538019e/src/starkware/starknet/services/api/gateway/contract_address.py#L12[Cairo code repository].


Loading
Loading