Skip to content
Menu

2z Wireguard Vpn

Uncategorised

Is this your project? Claim and verify →

Open-source control plane for programmable WireGuard routing over DoubleZero, with TypeScript/Go services, multi-region gates and observability.

What HEY knows

Building
Last shipped 3 days agoShipping: 2 meaningful events in 30 days; latest ship 3 days ago. Evidence Source

Build Momentum 35How it is measured

Latest ship
Code changes, week of 2026-10-12 – 2026-10-18 · 6 commits · · Code activity
FollowCreate alertTerminal previewView latest ship
Share

Follow puts 2z Wireguard Vpn on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.

No account? Email me 2z Wireguard Vpn’s changes

No account and no password. HEY stores the address and what you asked for, sends one confirmation, and nothing else until you confirm. Every email has a one-click unsubscribe that deletes the address.

Or read its RSS feed.

Token market · context
No token tracked
Not yet known
Unknown2 gaps: Official docs (no source), API description (no source). HEY read its website and found no link to docs.

HEY can answer 8 of the 10 research questions that apply · Research coverage

Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Shipping.
“Shipping” by the activity rule: 2 meaningful events in the last 30 days, the newest 2026-10-16.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-10-12 – 2026-10-18 · 6 commitsCode changes, week of 2026-10-05 – 2026-10-11 · 10 commitsCode changes, week of 2026-09-07 – 2026-09-13 · at least 53 commits+2 moreWhat HEY derivedHEY’s activity rule reads the counted events as “Shipping”.Not concludedIt says what HEY can read of the building, not how good the project is, who is behind it, or what its token will do. Quiet or unknown is not "abandoned".
Verified Builder.
The quality gate found verified building evidence from the project's own sources.
Source2 registered sources, 0 of them context only.ReadRecordsCode changes, week of 2026-10-12 – 2026-10-18 · 6 commitsCode changes, week of 2026-10-05 – 2026-10-11 · 10 commitsCode changes, week of 2026-09-07 – 2026-09-13 · at least 53 commits+3 moreWhat HEY derivedThe quality gate’s stored decision: “Verified Builder”.Not concludedA verified builder is one whose shipping HEY confirmed from public evidence. It does not say who runs the project — that is the ownership claim, a separate check.
Market figures are context only and never change activity status. Methodology
LinksWebsiteGitHubSources

Latest ship

Checked

Code changes, week of 2026-10-12 – 2026-10-18 · 6 commits

Code activitySource linked

What changed, in the repository’s own words:

3 active days in hyperspace-zone/2z-wireguard-vpn.

This week HEY looked inside 1 of 6 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

Record ship:e95059d5… · HEY counts it as building; it does not judge the release’s quality or what it means for the token.

View evidence ↗

Builder activity

Bars: meaningful, source-backed ships per week (count). Weeks run Monday to Sunday, UTC, labelled by their Monday. Commits are aggregated, a code week counted once. Hatched: 2 weeks before HEY began reading this project’s sources — not yet read, not zero.

Questions HEY can answer about 2z Wireguard Vpn — as of 2026-10-19

Is 2z Wireguard Vpn still being built?
DerivedShipping: 2 meaningful events in 30 days; latest ship 3 days ago. Evidence
What did 2z Wireguard Vpn ship last?
FactCode changes, week of 2026-10-12 – 2026-10-18 · 6 commits — Code activity, 3 days ago. Evidence
What does HEY not know about 2z Wireguard Vpn?
Unknown2 gaps: Official docs (no source), API description (no source). HEY read its website and found no link to docs. Details

Build timeline

  1. Code changes, week of 2026-10-05 – 2026-10-11 · 10 commits

    Code activitySource linked

    What changed, in the repository’s own words:

    3 active days in hyperspace-zone/2z-wireguard-vpn.

    This week HEY looked inside 1 of 10 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

    View evidence

  2. Code changes, week of 2026-09-21 – 2026-09-27 · 1 commit

    Code activitySource linked

    1 active day in hyperspace-zone/2z-wireguard-vpn.

    Documentation or maintenance only — not counted as building. This week HEY looked inside 1 commit to see what changed: 1 documentation or maintenance only.

    View evidence

  3. Code changes, week of 2026-09-07 – 2026-09-13 · at least 53 commits

    Code activitySource linked

    What changed, in the repository’s own words:

    4 active days in hyperspace-zone/2z-wireguard-vpn.

    This week HEY looked inside 3 of 49 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.

    View evidence

  4. Code changes, week of 2026-08-24 – 2026-08-30 · at least 23 commits

    Code activitySource linked

    What changed, in the repository’s own words:

    5 active days in hyperspace-zone/2z-wireguard-vpn.

    This week HEY looked inside 3 of 23 commits to see what changed: 1 changed code, 2 documentation or maintenance only. One code change is enough for the week to count, so HEY stopped there.

    View evidence

  5. DoubleZero Grant Milestone 3

    GitHub releaseSource verified

    Milestone 3 acceptance bundle for the Hyperspace DoubleZero grant. Highlights: · Mainnet live with 29 schedulable gates across 28 unique PoPs. · Documented managed deployment automation, validated by a production canary rollout. · Native SOL account funding and 0.0001 SOL config… Show all
    • Milestone 3 acceptance bundle for the Hyperspace DoubleZero grant. Highlights:
    • Mainnet live with 29 schedulable gates across 28 unique PoPs.
    • Documented managed deployment automation, validated by a production canary rollout.
    • Native SOL account funding and 0.0001 SOL config purchase live in production.
    • DoubleZero cost-event ingestion and 15% Hyperspace markup are implemented and test-covered; the current IBRL has supplied no billable upstream events.
    • Google OAuth, Resend email OTP, config management, QR/download helpers, and routing exclusions validated.
    • Real WireGuard acceptance…
    View evidence

Research notes

Written by HEY researchers and reviewed before publishing. Commentary with sources — not the project's own claims, and not evidence of shipping.

Know something about 2z Wireguard Vpn? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

What changed

6 changes on HEY’s record for 2z Wireguard Vpn: 1 release · 5 weeks of code pushed.

All 6 changes for 2z Wireguard Vpn →

The full change record holds 2 more, of kinds this list leaves out — lock records and HEY’s own research bookkeeping among them. Full record (JSON)

Research coverage

HEY can answer 8 of the 10 research questions that apply.

8 of 10 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 1mo ago.

Building

  • Building activityMeasuredRead 7m ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 1mo ago.
  • TimelineMeasured

Official site

  • Official docsNo sourceHEY read its website and found no link to docs.
  • API descriptionNo sourceIts website links no API description.
  • Official site changesMeasuredRead 2d ago.

Code and packages

  • Repository detailsMeasuredRead 8h ago.
  • Published packagesMeasuredRead 8h ago.

Not applicable here: Package advisories, Contract creation, Contract activity, Verified source, Contract interface, Current market, Market history, Supply distribution, Locks, Market checks, Protocol economics.

A count of what HEY has read, never a score: projects are not compared or ordered by it. Unknown is never zero. The same states: coverage API.

Sources