Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Verify session: UI and Smart Contract Interaction (Q2 2026, 16-ui-smart-contract-interaction)

Open Beginner friendly
  • Is something wrong?
#359 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
92/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
markdown
Domain
documentation

Research direction

Start by reading website/docs/working-group/sessions/q2-2026/16-ui-smart-contract-interaction/session-notes/readme.md end to end. Verify the prose, every link, and each diagram against the referenced packages, image tags, and versions; no shell commands are required. Record exact broken steps or references, post the findings here, and tick the matching verification box in #301 when complete.

Written by the indexing model from the issue text.

Description

documentation

Part of the tutorial verification checklist in #301.

Page: website/docs/working-group/sessions/q2-2026/16-ui-smart-contract-interaction/session-notes/readme.md
Title on the site: Session 16: UI ↔ Smart Contracts (Wallets + Tx flow) - Notes
Section: Q2 2026, 16-ui-smart-contract-interaction

How to follow along
  1. Open the page on the site and read it end to end before running anything.
  2. Work through it in a clean directory, as a new user. Do not skip setup steps because you already have the tooling; the point is to see what a newcomer sees.
  3. Run every command exactly as written, then compare the output with what the page claims it should be.
  4. Open every link, including links inside code comments and references.

Done when

  • Every command runs as written, or the page is updated so that it does
  • Every link resolves
  • Every package, image tag and version referenced still exists
  • The matching box in #301 is ticked and the findings are posted here
What to record when a step breaks
  • The exact command and the error text, copied rather than summarised
  • The heading or step number it sits under
  • What you changed to make it work

This page has no shell commands; verify prose, links and diagrams instead.

This page has no shell commands; verify prose, links and diagrams instead.

Dominant language
TypeScript
Stars
13
Forks
22
Avg merge
2d 18h
Merged PRs (30d)
17

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from IntersectMBO/developer-experience

All issues in IntersectMBO/developer-experience

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.