Open qbzzt opened 5 days ago
Name | Link |
---|---|
Latest commit | 367f25c2ccb2eff3689bd8f8f54441566cd736d6 |
Latest deploy log | https://app.netlify.com/sites/ethereumorg/deploys/6677a006fb247d000889a2cc |
Deploy Preview | https://deploy-preview-13228--ethereumorg.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
Lighthouse |
7 paths audited Performance: 45 (🔴 down 2 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.
Name | Link |
---|---|
Latest commit | 572625cd8eb222319ec7ffea89ef5f4cdd7e8d95 |
Latest deploy log | https://app.netlify.com/sites/ethereumorg/deploys/66781440e9b365000818aa93 |
Deploy Preview | https://deploy-preview-13228--ethereumorg.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
Lighthouse |
7 paths audited Performance: 45 (🔴 down 2 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.
A tutorial on how to write a centralized server component / agent
Description
After this tutorial, you will be able to write TypeScript servers that listen to events on a blockchain and respond accordingly with their own transactions. This will enable you to write centralized applications (because the server is a point of failure), but can interact with web3 entities. The same techniques can also be used to write an agent that responds to on-chain events without a human in the loop.
Related Issue
Closing: #13158