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
With Scroll, your favorite tools for building and testing smart contracts just work.
17
18
18
-
Since Scroll is bytecode equivalent with the EVM, you’ll just need to point your favorite builder tools at a Scroll Sepolia Testnet RPC Provider.
19
+
Since Scroll is bytecode equivalent with the EVM, you’ll just need to point your favorite builder tools at a Scroll RPC Provider.
19
20
20
21
If you run into any issues, please reach out in [our Discord](https://discord.gg/scroll).
21
22
22
-
## Acquiring Testnet Ether
23
+
## Acquiring Ether
23
24
24
-
To start building on Scroll, you'll first need to acquire some testnet ETH. See the [Faucet](/user-guide/faucet) page for tips on getting test tokens on Sepolia. After this, you can bridge your testnet ETH to the Scroll Sepolia Testnet (Layer 2) using our [Bridge](/user-guide/bridge).
25
+
Scroll uses ETH as its native currency, which will be needed to pay transaction fees for deploying and interacting with the network.
26
+
27
+
To start building on Scroll, we suggest you begin with using our Scroll Sepolia testnet. You'll first need to acquire some testnet ETH. See the [Faucet](/user-guide/faucet) page for tips on getting test tokens on Sepolia. After this, you can bridge your testnet ETH to the Scroll Sepolia Testnet (Layer 2) using our [Sepolia Bridge](https://sepolia.scroll.io/bridge), as described in the [Bridge article](/user-guide/bridge).
25
28
26
29
For a walkthrough, start with the User Guide's [Setup](/user-guide/setup) page.
27
30
31
+
Once you're ready to deploy on Scroll's mainnet, you can bridge over ETH using [our native bridge](https://scroll.io/bridge/) or one of the 3rd-party bridges.
32
+
28
33
## Network Configuration
29
34
35
+
### Scroll Mainnet
36
+
37
+
Use the table below to configure your Ethereum tools to the Scroll mainnet.
| Block Explorer URL |[https://sepolia-blockscout.scroll.io](https://sepolia-blockscout.scroll.io/)|[https://sepolia.etherscan.io](https://sepolia.etherscan.io)|
61
+
| Network Name | Scroll Sepolia | Ethereum Sepolia |
A number of technical details differ between Ethereum mainnet's EVM and Scroll's modified design for a zkEVM. Below you can see those differences as they exist on Scroll Sepolia.
13
+
A number of technical details differ between Ethereum mainnet's EVM and Scroll's modified design for a zkEVM. Below you can see those differences as they exist on Scroll and Scroll Sepolia.
14
14
15
15
For open-source contributors and infrastructure builders, please contact our team for additional support.
16
16
@@ -71,7 +71,7 @@ When verifying `EXTCODESIZE`, it is expensive to load the whole contract data in
71
71
72
72
## Block Time
73
73
74
-
The Sepolia Testnet aims for a constant block time of 3 seconds. This is shorter and more consistent than the 12 seconds used in the Ethereum under ideal conditions.
74
+
Scroll aims for a constant block time of 3 seconds. This is shorter and more consistent than the 12 seconds used in the Ethereum under ideal conditions.
75
75
76
76
This was chosen for two reasons:
77
77
@@ -90,7 +90,7 @@ You can read in more detail on Shanghai hard fork differences from London on the
90
90
91
91
## Transaction Fees
92
92
93
-
The fee charged to Scroll Sepolia transactions contains two parts:
93
+
The fee charged to Scroll transactions contains two parts:
94
94
95
95
-**L2 gas fee:** similar to L1, the amount of L2 execution fee equals to `L2_gas_price * L2_gas_used`, covering the following costs:
Copy file name to clipboardExpand all lines: src/content/docs/en/developers/index.mdx
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ ensuring that all code executed on the Scroll Layer 2 behaves just as if it were
28
28
29
29
## Getting Started
30
30
31
-
**Looking to build on the Scroll Sepolia Testnet?**
31
+
**Looking to build on the Scroll?**
32
32
33
33
- For the essentials: Check out the [Developer Quickstart](/developers/developer-quickstart)
34
34
- For a tutorial walking through deploying your first smart contract on Scroll, read our [contract deployment tutorial](/developers/guides/contract-deployment-tutorial)
@@ -78,9 +78,9 @@ ensuring that all code executed on the Scroll Layer 2 behaves just as if it were
78
78
<ToggleElementanchor="community">
79
79
<divslot="title">Community — Scroll brings together users and builders.</div>
80
80
<p>
81
-
We know the challenges of building in the open and getting user engagement before mainnet release! Scroll has a
82
-
blossoming community of users and builders, and with a Discord community of over 100,000 users eager to try out
83
-
applications on our testnet, we’re excited to connect builders with users that can provide real-world feedback.
81
+
We know the challenges of building in the open and getting user engagement! Scroll has a blossoming community of
82
+
users and builders, and with a Discord community of over 500,000 members eager to try out applications on our
83
+
testnet or mainnet, we’re excited to connect builders with users that can provide real-world feedback.
Copy file name to clipboardExpand all lines: src/content/docs/en/developers/l1-and-l2-bridging/the-scroll-messenger.mdx
+6-2Lines changed: 6 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,11 +24,15 @@ the messenger smart contract deployed on L1, `L1ScrollMessenger`. To send a mess
24
24
## Finalizing transactions on L1
25
25
26
26
Any upcoming transactions from L2 need to be finalized using the `relayMessageWithProof` function on the Scroll Messenger
27
-
contract. We call this process "submitting an Execute Withdrawal transaction," and it is required for both sending arbitrary messages and transferring assets through a gateway or the router. When you use `relayMessageWithProof`, you'll have to provide a Merkle inclusion proof showing your transaction is included in the trie of "withdrawal" messages, along with other parameters. Producing this proof and these values can be done locally and permissionlessly, but at the moment, the easiest way to retrieve these parameters is through our backend API hosted at https://sepolia-api-bridge.scroll.io/api/.
27
+
contract. We call this process "submitting an Execute Withdrawal transaction," and it is required for both sending arbitrary messages and transferring assets through a gateway or the router. When you use `relayMessageWithProof`, you'll have to provide a Merkle inclusion proof showing your transaction is included in the trie of "withdrawal" messages, along with other parameters. Producing this proof and these values can be done locally and permissionlessly, but at the moment, the easiest way to retrieve these parameters is through our backend APIs:
0 commit comments