Closed m4sterbunny closed 1 day ago
Name | Link |
---|---|
Latest commit | 8398b1a3ccef234e0cf5a16bbacd15f68265a40f |
Latest deploy log | https://app.netlify.com/sites/ethereumorg/deploys/667d25a4797a1e000892b995 |
Deploy Preview | https://deploy-preview-13201--ethereumorg.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
Lighthouse |
7 paths audited Performance: 42 (🔴 down 7 from production) Accessibility: 92 (no change from production) Best Practices: 83 (🔴 down 9 from production) SEO: 93 (no change from production) PWA: - View the detailed breakdown and full score reports |
To edit notification comments on pull requests, go to your Netlify site configuration.
I think I need to update Snap further for better detail: there are 2 things to sync Blockchain World state Snap sync: Blockchain from genesis, World state from trusted checkpoint
Quick housekeeping notes...
"12003(docs):fixes as per issue"
Issue Names: I see you're referencing an issue (12003). By convention, we'll place [Fixes #12003]
at the end of the issue name. Please try to start with a brief summary title for your changes. Ie. "Update node syncing content [Fixes #12003]` ("fixes as per issue" isn't very helpful when skimming through issue names 😆 )
Issue Body: Try to use the default template to get started. Under a ## Description
you can describe in more detail your changes, then under ## Relate issue
you can add - Fixes #12003
to cleanly link the PR to the issue it's fixing.
Thanks!
I think I resolved all @wackerow PTAL Apologies for poor hygiene, been lone writer for too long >> will learn to play nicely with others again
@all-contributors please add @m4sterbunny for content
@wackerow
I've put up a pull request to add @m4sterbunny! :tada:
Description
Execution client summary table did not link users to sync types Sync types were poorly identified and incomplete
Small proofs including:
Issue
Fixes #12003