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

WebAssembly support

Open
#5,085 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
go, wasm

Research direction

Start with the linked PR #5084 to see the current WASM work, then investigate the chunk-retrieval failure described here and whether it is related to WASM interop or retrieval between two nodes. The issue also identifies Go build flags as part of the implementation and notes Viper and go-libp2p compatibility concerns. Done means Bee runs in a browser with working chunk retrieval; WASI support is also in scope.

Written by the indexing model from the issue text.

Description

Summary

Implement proper support for both WASM and WASI (first WASM).

The PR for WASM is here: https://github.com/ethersphere/bee/pull/5084

Right now chunk retrieval is not working, which is either related to wasm interop or to a bug in the retrieval mechanism when there's just two nodes.

Notes

Viper supports WASM as of 1.7.1: https://github.com/spf13/viper/issues/1071
go-libp2p fails to compile because of WebRTC transport: https://github.com/libp2p/go-libp2p/issues/3277

Motivation

being able to run bee in a browser

Implementation

go flags

Drawbacks

idk

Dominant language
Go
Stars
1.5k
Forks
390
Avg merge
2d 8h
Merged PRs (30d)
19

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 ethersphere/bee

All issues in ethersphere/bee

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.