Skip to content
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

Suggest a tutorial: Server components for web3 apps #13158

Open
1 of 2 tasks
qbzzt opened this issue Jun 13, 2024 · 4 comments
Open
1 of 2 tasks

Suggest a tutorial: Server components for web3 apps #13158

qbzzt opened this issue Jun 13, 2024 · 4 comments
Assignees
Labels
content 🖋️ This involves copy additions or edits feature ✨ This is enhancing something existing or creating something new request for comments 🗣️ A request for comments has been made; discussion and input is encouraged

Comments

@qbzzt
Copy link
Contributor

qbzzt commented Jun 13, 2024

Tutorial title

Server components for web3 apps

Tutorial 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 applications that are centralized (because the server is a point of failure), but can interact with web3 entities.

Tutorial tags

server, offchain, centralized

Skill level

Beginner

Hosted on ethereum.org or hosted elsewhere?

Hosted on ethereum.org

For tutorials to be hosted on Ethereum.org: Tutorial Content

  • Introduction: Why a Centralized Server?
  • Getting started: Node, TypeScript, and Viem
  • Listening to Events
  • Responding with Transactions
  • Conclusion, when is this an appropriate solution?

For tutorials hosted elsewhere: URL to tutorial

No response

Would you like to work on this issue?

  • Yes
  • No
@qbzzt qbzzt added content 🖋️ This involves copy additions or edits feature ✨ This is enhancing something existing or creating something new labels Jun 13, 2024
@github-actions github-actions bot added the needs triage 📥 This issue needs triaged before being worked on label Jun 13, 2024
@wackerow wackerow added request for comments 🗣️ A request for comments has been made; discussion and input is encouraged and removed needs triage 📥 This issue needs triaged before being worked on labels Jun 13, 2024
@wackerow
Copy link
Member

@qbzzt Interesting... so would these "server components" be like front end components? Or more of an API that is listening to events and capable of responding with actions?

cc: @minimalsm

@qbzzt
Copy link
Contributor Author

qbzzt commented Jun 13, 2024

They can be either. I'm thinking of a use case that requires listening to events, but it can be triggered by any other input too.

@wackerow
Copy link
Member

Gotcha, I see what you're getting at here. Sounds good from my end!

@qbzzt
Copy link
Contributor Author

qbzzt commented Jun 23, 2024

Written (#13228). Next, I'll submit a proposal for a sequel that teaches how to use zero-knowledge proofs for a centralized component that holds a secret state and can be trusted (#13234). Do you think it's better to use Zokrates or Cairo?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content 🖋️ This involves copy additions or edits feature ✨ This is enhancing something existing or creating something new request for comments 🗣️ A request for comments has been made; discussion and input is encouraged
Projects
None yet
Development

No branches or pull requests

2 participants