Skip to content

Commit

Permalink
Update 10.index.md for 404 link (#46)
Browse files Browse the repository at this point in the history
Added some copy changes
  • Loading branch information
AlbionaHoti authored Aug 23, 2024
1 parent 0125ad7 commit 31adaa1
Showing 1 changed file with 5 additions and 5 deletions.
10 changes: 5 additions & 5 deletions content/tutorials/how-to-send-l1-l2-transaction/10.index.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,15 +3,15 @@ title: Send a transaction from L1 to L2
description: This how-to guide explains how to send a transaction from Ethereum that interacts with a contract deployed on ZKsync.
---

The [ZKsync Era smart contracts](https://github.com/matter-labs/era-contracts/tree/main/l1-contracts/contracts/zksync)
The [ZKsync Era smart contracts](https://github.com/matter-labs/era-contracts/tree/main/l1-contracts/contracts)
allow a sender to request transactions on Ethereum (L1) and pass data to a contract deployed on ZKsync Era (L2).

In this example we'll send a transaction to an L2 contract from L1 using `zksync-ethers`, which provides helper methods to simplify the process.
In this example, we'll send a transaction to an L2 contract from L1 using `zksync-ethers`, which provides helper methods to simplify the process.

## Common use cases

Along with ZKsync Era's built-in censorship resistance that requires multi-layer interoperability,
there are some common use cases that need L1 to L2 transaction functionality, such as:
some common use cases need L1 to L2 transaction functionality, such as:

- Custom bridges.
- Multi-layer governing smart contracts.
Expand All @@ -20,8 +20,8 @@ there are some common use cases that need L1 to L2 transaction functionality, su

Before continuing, make sure you have the following:

- Destination contract ABI: in order to execute a transaction on a contract on L2,
you'll need the contract's ABI. For this example we'll use a `Greeter.sol` contract that is deployed
- Destination contract ABI: to execute a transaction on a contract on L2,
you'll need the contract's ABI. For this example, we'll use a `Greeter.sol` contract that is deployed
on [ZKsync Sepolia testnet](https://sepolia.explorer.zksync.io/address/0x543A5fBE705d040EFD63D9095054558FB4498F88)).
- L1 RPC endpoint: to broadcast the L1->L2 transaction to the network.
You can find [public Sepolia RPC endpoints in Chainlist](https://chainlist.org/chain/11155111).
Expand Down

0 comments on commit 31adaa1

Please sign in to comment.