Known limits: v0.1.0-tester.1

The first build for outside testers, on Bittensor testnet, subnet 611. Please read these before you report a bug. They are known, and most have a task to fix them.

What is in it

• Nodes, mechanism 0. bwos-node for Linux x86_64 and aarch64. One static binary serves both kinds of node: a kernel node (Ubuntu 24.04, kernel WireGuard and FRR 10, set up by install.sh) and a no-root node (bwos-node run --mode userspace, a plain process or the container image). Both open probe sessions to every validator, answer probes, hand over the node's consent, and take capacity tests.
• Linking, without a server. Bind up to 7 nodes to your hotkey inline, with the link page or with bwos bind ... commit --inline on Linux.
• Solvers, mechanism 1. bwos-solver daemon fetches each window's snapshot, runs your solver (--solver-cmd, any language), signs and commits the table, and serves it for validators to pull. minimal_solver is a starting point.
• Router. The Linksys WRT1900AC v1 image (stock OpenWrt 24.10.4 plus the Transit Fabric packages), and the packages on their own.
• Checking. bwos-validator chain-status --network test --netuid 611, a read-only JSON view of each UID's commitment, axon and weights.

Known limitations

• Validators are ours. Every validator on 611 is run by the Transit Fabric team. Some measurements come from probe sessions not yet matched to where their results are collected. One operator could answer different validators from different machines (threat T300). We accept that on testnet only while every validator is ours. It must close before any outside validator takes part.
• Capacity is tested one network at a time. Tests are drawn per network (a /24 for IPv4). One machine behind several networks' addresses is tested at different times, and each test sees its whole rate. Random spot co-tests across a UID's networks come later (OQ-286). Please don't exploit it. Report what you find.
• Behind NAT, capacity counts at most 100 Mb/s. A node behind NAT is tested by dialing out to the validator, an interim method. A public node with an open TCP 8621 is tested at its full rate.
• About 220 Mb/s per flow. On cloud VMs one flow over the overlay carries about 220 Mb/s, so a single-flow test tops out there.
• No customer traffic. Nodes carry only other nodes' overlay traffic and validators' test traffic. There is no VPN exit. Nothing goes out to the public internet.
• Peering is self-service, with limits. A node is paid for capacity only with a BGP session to a node of another UID. Transit Fabric doesn't assign peers yet. Our public node adds yours by itself once you post your peer card in a "Peering request" Issue and validators list your node. It takes one node per UID, first come. Or swap cards with another tester. Two nodes both behind NAT can't peer (no hole punching yet).
• Router nodes aren't measured yet. A router node can peer and carry traffic, but validators can't measure or pay it.
• No macOS or Windows binaries. Mac and Windows users link nodes with the link page and run nodes on Linux. btcli works everywhere.
• The probe agents are listed by hand. network.json lists each validator's probe agent. If we add or move a validator, we publish a new network.json.
• The validator set anchor ages. validator-set.json is good for about 29 hours from its block. A running node follows newer sets by itself, but a node can't start from an expired one. Make a current one with bwos validator-set build --fetch.
• Releases aren't signed yet. Check SHA256SUMS against the hash we announce by a second route. Signed releases and an updater come later.
• More than 7 nodes on one hotkey need manifest mode. Its manifest must be re-committed at least every other window (about 2.4 hours; OQ-210). A node can forward its files only up to about 13 nodes. With more than 16 nodes, a validator reveals at most 16 consents per UID (OQ-263).
• The reference solver earns nothing, and neither will minimal_solver. A table must beat the reference by 2% to be paid.
• Prototype data plane. A packet's source is checked only as far as the link it came on. Link reports are what each node says of itself, unsigned.

Reporting

Issues for problems. Report a vulnerability for security issues and ways to earn more than you carry.