-
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(protocol, relayer): Improved Taiko Protocol and Relayer Documentations #15440
feat(protocol, relayer): Improved Taiko Protocol and Relayer Documentations #15440
Conversation
@joaolago1113 is attempting to deploy a commit to the taikoxyz Team on Vercel. A member of the Team first needs to authorize it. |
Nice |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## alpha-6 #15440 +/- ##
===========================================
- Coverage 27.15% 26.88% -0.27%
===========================================
Files 94 96 +2
Lines 5700 5798 +98
===========================================
+ Hits 1548 1559 +11
- Misses 3988 4073 +85
- Partials 164 166 +2
*This pull request uses carry forward flags. Click here to find out more. ☔ View full report in Codecov by Sentry. |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Overview
This Pull Request introduces updates to the Taiko Protocol and Relayer project documentation and configuration settings. These changes are based on my hands-on experience using and testing these protocols, the documentation aligns well with practical usage and all setup processes are streamlined for future developers.
Changes
Expand Relayer README with Detailed Build, Config, and Usage Instructions
Revamp README with Detailed Steps
alloc
field, generating and running with the L2 genesis block, and deploying the L1 contracts.Changed DATABASE_PASSWORD from root to passw00d
.l1processor.example.env
file of the Relayer package to match the default db password.