You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: components/Starknet/modules/resources/pages/chain-info.adoc
+36-26Lines changed: 36 additions & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,80 +31,90 @@ Starting from v0.13.0, blockifier-related constants and limits are defined for e
31
31
Starting from v0.13.5, resources are denominated in units of L2 gas, L1 gas, and L1 data gas.
32
32
====
33
33
34
-
[%autowidth.stretch]
34
+
[cols="1,2,1,1"]
35
35
|===
36
36
| Entity | Description | Sepolia | Mainnet
37
37
38
38
| Block time
39
-
| The maximum amount of time within which a pending block is closed, if no other limit is met.
39
+
| The maximum amount of time within which a pending block is closed, if no other limit is met
40
40
| 30 seconds
41
41
| 30 seconds
42
42
43
43
| Max L2 gas per block
44
-
| The maximum amount of L2 gas that a block can contain.
45
-
within each block to ensure block production times remain consistent and predictable.
44
+
a| The maximum amount of L2 gas that a block can contain
45
+
[NOTE]
46
+
====
47
+
This limit ensures block production times remains consistent and predictable.
48
+
====
46
49
| 5 * 10^9^
47
50
| 5 * 10^9^
48
51
49
52
| Max L2 gas per transaction
50
-
| The maximum number of computational steps, measured in L2 gas, that a transaction can contain when processed on the Starknet network.
53
+
a| The maximum number of computational steps, measured in L2 gas, that a transaction can contain when processed on the Starknet network
54
+
[NOTE]
55
+
====
51
56
This limit is important for ensuring the efficient execution of transactions and preventing potential congestion.
57
+
====
52
58
| 10^9^
53
59
| 10^9^
54
60
55
61
| Max state updates per transaction
56
-
| The maximum number of storage updates that a single transaction can generate. This limit helps maintain network stability and predictable performance.
62
+
a| The maximum number of storage updates that a single transaction can generate
63
+
[NOTE]
64
+
====
65
+
This limit helps maintain network stability and predictable performance.
66
+
====
57
67
| 2,000
58
68
| 2,000
59
69
60
70
| Max number of events per transaction
61
-
| The maximum number of events that a transaction can emit during its execution.
71
+
| The maximum number of events that a transaction can emit during its execution
62
72
| 1,000
63
73
| 1,000
64
74
65
75
| Max number of data felts per event
66
-
| The maximum number of felts that an event can contain in its `data` array.
76
+
| The maximum number of felts that an event can contain in its `data` array
67
77
| 300
68
78
| 300
69
79
70
80
| Max number of key felts per event
71
-
| The maximum number of felts that an event can contain in its `keys` array.
81
+
| The maximum number of felts that an event can contain in its `keys` array
72
82
| 50
73
83
| 50
74
84
75
85
| Max L2 gas for `validate`
76
-
| The maximum number of computational steps, measured in Cairo steps, for a `validate` function.
86
+
| The maximum number of computational steps, measured in Cairo steps, for a `validate` function
77
87
| 10^8^
78
88
| 10^8^
79
89
80
-
| Max contract bytecode size (felts)
81
-
| The maximum size of the bytecode or program that a smart contract can have on Starknet.
90
+
| Max contract bytecode size
91
+
| The maximum size of the bytecode or program that a smart contract can have on Starknet
92
+
| 81,920 felts
93
+
| 81,920 felts
82
94
83
-
Bytecode is the low-level code that comprises smart contracts. Limiting this size helps manage the complexity of contracts and the overall efficiency of the network.
84
-
| 81,920
85
-
| 81,920
86
95
| Max contract class size
87
-
| The maximum size for a contract class within Starknet.
88
-
89
-
Contract classes are a fundamental building block for smart contracts, and limiting their size can have implications for the network's scalability and security.
96
+
a| The maximum size for the Sierra file of a contract class within Starknet
97
+
[NOTE]
98
+
====
99
+
This limit is important for ensuring the network's scalability and security.
100
+
====
90
101
| 4,089,446 bytes
91
102
| 4,089,446 bytes
92
103
93
104
| IP address limits
94
-
| In order to reduce network spam, Starknet limits the amount of contract reads and writes that a single IP
95
-
address can make.
105
+
| The amount of contract reads and writes that a single IP address can make (in order to reduce network spam)
0 commit comments