-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
feat(website): create testnet docs #428
Conversation
4e14a4b
to
b5490f6
Compare
ce4ae8b
to
5279d91
Compare
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
* wording * Update _category_.json * more * Update get-started.md
node runners cannot become a proposer yet. (afaik)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great. Just my two small commits.
Also, is there anything we can say about the L2 block time? You mention the delay in Bridge
section, but what about in the Explore the Network
section. You mention 12 sec L1 blocks there; can we say anything about L2 avg. block times?
L2 avg block time depends on the behavior of all proposers in the network. Currently we deployed 3 our own proposers which propose new L2 blocks every 12 - 60 seconds (the interval is random). And an empty block proposer who proposes an empty L2 blocks every 2 minutes. But users can start their own proposers and customize its behavior by changing the code, or they can just call the contract directly, since our protocol design is fully decentralized... |
No description provided.