The Evolution of the Skywire Codebase

Seven Years, 12,000+ Commits, 45 Contributors, Three GitHub Organizations

The Skywire codebase has been through multiple complete architectural redesigns since its first commit in March 2019. What started as a mainnet implementation for a mesh networking protocol has evolved into a unified platform encompassing an encrypted overlay network, a VPN, a port forwarding system, a reward economy, and — most recently — a multi-coin blockchain toolchain. This article traces that evolution.

2019: The Foundation

March 2019 — 志宇 (Evan Lin) pushed the first commit: “first implementation of skywire mainnet.” The initial codebase established the core abstractions that still exist today: transports (bidirectional communication channels between visors), routing tables, and the visor as the fundamental network node.

The early architecture was designed around a clean separation between transport types. A transport could be anything — TCP, UDP, or something more exotic — as long as it implemented the transport interface. This flexibility would prove critical later.

Contributors in this era: 志宇 (Evan Lin), ivcosla, BigOokie, Sir Darkrengarius, Nikita Kryuchkov

May 2019 — Sir Darkrengarius and Nikita Kryuchkov joined the project, beginning what would become two of the most prolific contribution periods in the codebase’s history. Darkrengarius would go on to contribute over 1,000 commits focused on core architecture.

June 2019 — DMS was renamed to DMSG (“as per Brandon’s request”). The Distributed Messaging System became the encrypted overlay network that would underpin all of Skywire’s communication. DMSG introduced secp256k1 public key identity, the Noise protocol for end-to-end encryption, and relay servers that forward ciphertext without being able to decrypt it.

October 2019 — Skynet appeared in the codebase for the first time, with Sir Darkrengarius implementing the initial port forwarding structs and wiring them into the visor startup sequence.

2019 by the numbers: 2,762 commits. The foundation year. No stable releases yet — the software was pre-release.

2020: VPN, Apps, and the Process Model

March–April 2020 — The VPN implementation landed. First the client (creating TUN interfaces and routing tables), then the server. This was the first “killer app” for Skywire — a full VPN that routes traffic through the peer-to-peer network instead of centralized servers.

The VPN, along with the SOCKS5 proxy (Skysocks) and Skychat messaging, established the application model that would go through several major redesigns. In this era, Skywire apps were external processes. The visor would spawn each app as a separate OS process, communicating over Unix sockets or named pipes. A process manager tracked PIDs, handled restarts, and collected logs.

This model was conceptually clean — apps were isolated, could crash without taking down the visor, and could be developed independently. But it had operational costs: process spawning was slow, managing multiple binaries was complex, and the IPC overhead added latency.

May 2020 — Moses Narrow’s first commit: adding Makefile package directives and systemd services. This marked the beginning of a long focus on deployment, packaging, and making Skywire installable as a system service — work that would continue for years.

Releases: v0.1.0 (March 2020), v0.2.0 through v0.2.3 (April), v0.3.0 (October) — the first public releases.

2020 by the numbers: 3,298 commits — the peak development year.

2019: The GitHub Organization Split

September 2019 — A crisis outside the codebase disrupted the project. Due to a dispute involving individuals who had gained control of the skycoin.net domain and the github.com/skycoin GitHub organization, the development team migrated to a new organization: github.com/SkycoinProject.

On September 17, ivcosla committed “moved to SkycoinProject.” Over the following days, imports were rewritten, remotes were updated, and development continued under the new organization. The Skywire mainnet repo became SkycoinProject/skywire-mainnet, DMSG moved to SkycoinProject/dmsg, and dozens of related repos were forked or recreated.

This was a disruptive period. Import paths changed throughout the codebase, CI configurations needed updating, and the community had to be redirected to the new organization. But development never stopped — within days of the migration, Darkrengarius and Evan Lin were merging PRs under the new organization.

Eventually, control of the original github.com/skycoin organization was recovered, and the repos migrated back. But the scars of the split lingered in the codebase for years — skycoinproject import paths persisted in various files and were still being cleaned up as late as December 2024 (PR #1912).

Beyond the public codebase, the Skywire project spans three GitHub organizations: github.com/skycoin (106 repos — the public codebase), github.com/SkycoinProject (22 repos — remnants of the 2019 migration), and github.com/skycoinpro (41 repos — private operational infrastructure including the mobile wallets, deployment configs, whitelisting services, reward system, DevOps, and monitoring bots). At peak, the ecosystem had over 150 repositories across these organizations.

2021: Infrastructure at Scale

Development shifted toward the infrastructure needed to run Skywire as a production network. The Transport Discovery, Service Discovery, Uptime Tracker, Route Finder, and Address Resolver were all refined and hardened.

April 2021 — Erson Pereira (ersonp) joined the project, contributing 640 commits over the following years focused on the CLI, service infrastructure, and deployment tooling.

The reward system’s mainnet rules were established and iterated, with Asgaror maintaining the rules documentation. The economics of running Skywire nodes — how operators get compensated for providing network infrastructure — became a first-class concern.

Releases: v0.4.0 (March 2021), v0.4.1, v0.4.3 (September), v0.5.0 (October), v0.5.1 — rapid iteration toward the v1.0 milestone.

2021 by the numbers: 2,951 commits.

2022–2023: Fragmentation, Stabilization, and the Repo Sprawl

By 2022, the Skywire ecosystem had fragmented across a sprawl of separate repositories. The network services lived in skywire-services. Shared utilities lived in skywire-utilities. The manager UI was in skywire-manager. The DMSG library was in dmsg. The updater was in skywire-updater. Service discovery, uptime tracker, and deployment configs each had their own repos. At one point, there were over a dozen skywire-* repositories under the skycoin organization.

March 2022 — ersonp began pulling skywire-utilities packages into the main Skywire repo — netutil, cipher, buildinfo, httputil. This was the first step toward consolidating everything back into a single repository.

On the transport layer, STCPR (TCP with port reuse) and SUDPH (UDP hole punching) matured as direct peer-to-peer transport types, complementing the relay-based DMSG transport. The visor ping mechanism was refined, autoconnect logic improved, and the Address Resolver handling became more robust.

DmsgWeb emerged during this period — a resolving SOCKS5 proxy that lets web browsers access sites hosted entirely within the DMSG overlay network. Inspired by I2P, DmsgWeb maps .dmsg domains to public keys and routes traffic through the encrypted overlay.

Releases: v0.6.0 (February 2022), v1.0.0 (July 2022 — the first stable release, after 7 release candidates), v1.0.1, v1.1.0, v1.1.1, v1.2.0, v1.2.1, v1.3.0 through v1.3.16 (December 2023) — 27 releases in two years, the most active release period.

2022–2023 by the numbers: 2,797 commits combined.

2024–2025: The Great Consolidation

The separate repos were systematically merged into the main Skywire repository:

• February 2024 — Apps integrated into the unified binary (PR #1704)
• March 2024 — Move to merged binary complete (PR #1776)
• November 2024 — Joint compilation with Skycoin (PR #1901)
• December 2024 — skywire-utilities imports replaced with internal packages (PR #1912)
• March 2025 — skywire-services migrated into the main repo (PR #1937)
• March 2026 — skywire-manager dependencies migrated and UI rebuilt

A pivotal architectural decision drove this consolidation: merge everything into one binary.

February 2024 — PR #1704 implemented Cobra CLI integration for all apps and merged them into a single compilation unit. The individual app binaries (vpn-server, vpn-client, skysocks, skysocks-client, skychat) became subcommands of the main skywire binary.

March 2024 — PR #1776 (“Move to merged binary”) completed the transition. One skywire binary now contained the visor, all CLI commands, all network services, all DMSG utilities, all native applications, and bundled tools like jq (gojq) and a text editor (femto).

But the apps were still launched as external processes internally. The unified binary used os.Args[0] detection and symlinks to determine which “app” was being invoked, then ran the appropriate code path. The process manager still spawned child processes — they just happened to be the same binary with different arguments.

Releases: v1.3.17 through v1.3.28 (February 2024–September 2024), v1.3.29 (July 2025 — after 11 release candidates spanning 9 months), v1.3.30, v1.3.31 (October 2025).

2025: From Processes to Function Calls

October 2025 — The final piece of the app architecture puzzle: PR #2079 refactored the app launcher to launch apps via direct function calls instead of spawning OS processes. The VPN server, VPN client, SOCKS5 proxy, and other apps now run as goroutines within the visor process, with reverse compatibility for managing external apps when needed.

This eliminated process spawning overhead, simplified deployment (no more PID tracking, no zombie processes), and made the visor a single-process system. Log management became simpler — no more collecting stdout/stderr from child processes. And startup was near-instantaneous since there’s no exec involved.

The transition was careful: the internal launcher and external launcher coexist, with the internal path used by default and the external path available as a fallback. Comprehensive E2E tests were added to verify both modes.

Also in 2025: The Skycoin blockchain toolchain was embedded into the Skywire binary. skywire skycoin daemon, skywire skycoin cli, skywire skycoin web, skywire skycoin explorer, and skywire skycoin newcoin — the full Skycoin stack became accessible from the same binary that runs the mesh network. One download, one install, everything.

2026: Fibercoins, Route Multiplexing, and CXO

Dynamic Fibercoin branding — the FIBER_TOML environment variable now makes the entire toolchain adapt to any Fibercoin. Help menus, ASCII art banners, CLI defaults, data directories — everything reflects the configured coin. AIX and Privateness were the first third-party Fibercoins verified with this system.

Route multiplexing — connections can now spread traffic across multiple transports simultaneously, with latency-weighted transport selection, packet reordering, and SACK-based retransmission. This is the first phase of multi-path routing.

CXO integration — the Content-Addressable Object System, a distributed data storage layer, was integrated into the Skywire binary.

Transport Discovery overhaul — the TPD migrated from PostgreSQL to Redis, added per-transport and per-visor bandwidth metrics, and enabled the transition to bandwidth-based rewards.

Releases: v1.3.32 (January 2026), v1.3.33, v1.3.34 (February — native .pkg and .msi installers), v1.3.36 (March — TPD overhaul, network globe), v1.3.37 (March — route multiplexing, CXO, embedded Skycoin v0.28.4).

The Architecture Today

What started as separate binaries for each component is now a single process:

skywire
├── visor        — the Skywire node
├── cli          — 20+ subcommands for managing everything
├── svc          — all 13 network services
├── dmsg         — DMSG overlay (server, discovery, web, curl, pty, socks)
├── app          — VPN, proxy, chat, skynet (launched as goroutines)
├── util         — jq, text editor, HTTP client
└── skycoin      — full Skycoin blockchain toolchain
    ├── daemon   — full node
    ├── cli      — wallet, transaction, blockchain queries
    ├── web      — multi-coin thin client wallet
    ├── explorer — blockchain explorer
    └── newcoin  — Fibercoin creation

The evolution from “collection of separate programs communicating over IPC” to “single binary, single process, function-call app launching” took six years and thousands of commits. Each stage — external processes, unified binary with process spawning, and finally direct function calls — solved the problems of the previous stage while introducing new capabilities.

Contributors

29 unique contributors have worked on the Skywire codebase (45 git author names, consolidated by identity):

What’s Next

The codebase continues to evolve. Active areas of development include route multiplexing refinement, CXO integration, bandwidth-based reward economics, and Fibercoin ecosystem tooling. The architecture is now stable enough that new features layer on top rather than requiring rewrites — a sign of maturity after seven years of iteration.

See also: Skywire: One Binary, Everything You Need | Route Multiplexing | Bandwidth-Based Rewards