Skip to content

Commit 61facb0

Browse files
fixed errors in l1 to l2 conversion
1 parent 6ebc98a commit 61facb0

File tree

1 file changed

+1
-1
lines changed
  • not-so-smart-contracts/cairo/L1_to_L2_address_conversion

1 file changed

+1
-1
lines changed

not-so-smart-contracts/cairo/L1_to_L2_address_conversion/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ In Starknet, addresses are of type `felt` while on L1 addresses are of type `uin
44

55
# Example
66

7-
Suppose that the following code to initiate L2 deposits from L1. The first example has no checks on the `to` parameter and thus depending on the users' address, it is possible to transfer tokens to an unexpected address on L2. The second example, however, verifies to make sure this check cannot happen.
7+
Suppose that the following code to initiate L2 deposits from L1. The first example has no checks on the `to` parameter and thus depending on the users' address, it is possible to transfer tokens to an unexpected address on L2. The second example, however, verifies to make sure this check cannot happen. Note that the code is just a simplification of how messages are sent on L1 and processed on L2. For a more thorough overview, see here: https://www.cairo-lang.org/docs/hello_starknet/l1l2.html.
88

99
```solidity
1010
uint256 public constant STARKNET_FIELD_PRIME; // the prime order P of the elliptic curve used

0 commit comments

Comments
 (0)