Move all full-node logic under a build tag
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- go
- Domain
- backend, build-system
Research direction
Start by mapping where Bee’s full-node logic and existing build-tag configuration are defined; the issue names no files or tests. Check how browser, EFI, Android, and microcontroller targets are currently built, then identify the checks that depend on full-node behavior. Done means the optional build tag excludes the intended logic without breaking other targets or dependent checks.
Written by the indexing model from the issue text.
Description
Summary
It makes no sense to run a full node in a browser, inside a EFI module, Android or on a cheap microcontroller. In order to simplify the logic, decrease bundle size and improve perf, build tags could be utilized.
Motivation
Simplification of the architecture of Bee for low-end targets. Significant decrease of bundle size.
Implementation
A build tag that is enabled by default which can be turned off, which would exclude all full node logic from the compilation. A name could be -tag full-node
Drawbacks
Need to be careful not to affect other parts of the logic that might depend on full node checks
- Dominant language
- Go
- Stars
- 1.5k
- Forks
- 390
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 19
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ethersphere/bee
-
Chequebook deployment uses a fixed 175,000 gas limit; it needs about 630,000 under Glamsterdam (live on Sepolia since 2026-10-06)Possibly taken @sbackend123 claimed this 10 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
ethersphere/bee#5650 · 1 assignee ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
ethersphere/bee#5666 ·
Maintainers usually reply within 2 days
-
Add a transaction inbox for outbound chain transactionsPossibly taken @sbackend123 claimed this 4 days ago. Openseen
Difficulty 5/5 Over a week Newbie friendliness 35/100
ethersphere/bee#5660 · 1 assignee ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
ethersphere/bee#5659 ·
Maintainers usually reply within 2 days
-
accepted seen
Difficulty 4/5 3-5 days Newbie friendliness 40/100
ethersphere/bee#5648 · 1 comment ·
Maintainers usually reply within 2 days
Similar issues
-
[Bug]: message-level cache_control on chat messages is dropped, so Anthropic prompt caching never triggersPossibly taken @Atharva-Kanherkar claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day
-
documentation good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
eugenioenko/ttt#1000 ·
Maintainers usually reply within 1 day
-
bug needs-acceptance wg/developer-experience-ecosystem
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
vllm-project/semantic-router#5249 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Billionmail/BillionMail#389 ·
-
在“产品文档”下拉列表，增加“探索”频道Openenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
DaoCloud/DaoCloud-docs#7489 ·
Maintainers usually reply within 1 day