ZBProxy
🚀Transfer your network data, bypassing the Hypixel unofficial address detection!
Runssource: GitHubhomepageGoApache-2.0commit 5570a6aec577
Go, Apache-2.0 licensed. The project labels itself: go, golang, hypixel, minecraft, proxy, reverse proxy, socks and socks5.
ZBProxy runs. An Argusic agent installed it in 2 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
ZBProxy builds from source with Go 1.22.5, starts, auto-generates configuration, and listens on port 25565. All local unit tests pass except one pre-existing test that requires an external SRV DNS record not available in this environment.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Go compiler not installed in container (no root for apt)1 minute
- Test TestSystemOutbound_DialContextWithSRV fails: external SRV record dummy.launium.com does not resolve in this environment
- Install time
- 2 minutes
- Cold machine to finish
- 4 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- /tmp/zbproxy started and printed 'ZBProxy started' plus 'Listening on :25565'; ss -tlnp confirmed process listening; go test exited non-zero only due to the SRV test; all other test packages (bufio, domain, mcprotocol, proxyprotocol, set) passed
- Model tokens used
- 97,544
- Exact commit tested
- 5570a6aec577
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
varint_test.go:37: VarInt -1 ReadFrom [255 255 255 255 15]
varint_test.go:37: VarInt -2147483648 ReadFrom [128 128 128 128 8]
--- PASS: TestReadFrom (0.00s)
PASS
ok github.com/layou233/zbproxy/v3/common/mcprotocol 0.003s
testing: warning: no tests to run
PASS
ok github.com/layou233/zbproxy/v3/common/set 0.002s [no tests to run]
Now I have everything I need for the report.
tokens used
97,544
Now I have everything I need for the report.Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 2 minutes, faster than the median of the 11 comparable projects Argusic has measured.
- Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 12 go projects Argusic has installed and timed, ZBProxy was the 4th fastest to reach a running state, and 12 of 12 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 2 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
gogolanghypixelminecraftproxyreverse-proxysockssocks5varintzerocopy
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/zbproxy)Questions
- Does ZBProxy run?
- Yes. ZBProxy runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test ZBProxy?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 5570a6aec577. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test ZBProxy?
- The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does ZBProxy take to install?
- 2 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does ZBProxy need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing ZBProxy?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does ZBProxy compare with the alternatives?
- Of the 12 go projects Argusic has installed and timed, ZBProxy was the 4th fastest to reach a running state, and 12 of 12 reached one at all.
- Where is the evidence for ZBProxy?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.