KODE
Protocol researchConnect wallet ↗
EARLY BUILDOPEN DEVELOPMENT PROTOCOL

Code belongs
to the builders.

Kode is a decentralized development environment and on-chain version control system—built for teams that want to own their code, identity, and collaboration layer.

Connect wallet to enter →›_ Read the architecture
2Client surfacesWeb + Desktop
0Account databasesWallet-native access
P2PRepository syncContent addressed
0x71…A93F
0x0C…114B
0xF2…9DA0
VERIFIED COMMITc4f8a2dtree 8d42 · parent 9ac1
◇
EVM ANCHORBlock #6,214,088
CONTENT ADDRESSEDPEER VERIFIEDWALLET SIGNED
01THE PREMISE

The development stack should not own the developer.

Modern collaboration depends on centralized identity, repositories, and permission systems. Kode replaces those assumptions with portable cryptographic identity and verifiable state.

Files remain off-chain. Coordination moves on-chain only where shared consensus matters.

01↗
⌁

Local-first development

Edit, commit, and inspect history close to your machine—without waiting for a centralized service.

02↗
◎

Peer-synced repositories

Content-addressed objects move directly between authorized peers through the Kode protocol.

03↗
◇

On-chain coordination

Protected refs, access policies, and pull-request state become independently verifiable.

02ONE PROTOCOL, TWO SURFACES

Built for the browser.
Native on desktop.

The interface is shared. Platform capabilities stay behind explicit adapters, while the Go node remains the source of P2P behavior.

CLIENT SURFACES
W
Kode WebNext.js · Zustand
D
Kode DesktopWails · Native bridge
SHARED PROTOCOL BOUNDARY
VERIFIED CORE
G
Go P2P NodeObjects · Discovery · Sync
Ξ
EVM ContractsBranches · PRs · Access
◇
03IDENTITY WITHOUT ACCOUNTS

Your wallet is your identity.

No password table. No application-owned user database. Kode authorizes access through domain-bound challenges, wallet signatures, address recovery, and on-chain repository policies.

  1. 01RequestReceive an expiring challenge.
  2. 02SignApprove it with your wallet.
  3. 03VerifyRecover identity from the signature.
  4. 04AuthorizeResolve repository policy on-chain.
04BUILD IN PUBLIC

The path to a sovereign developer workspace.

We start with interface and protocol boundaries before activating high-trust infrastructure.

DONE
Interface foundationWeb workspace and product system
DONE
Protocol specificationsObjects, capabilities, and fixtures
NOW
Local VCS engineCanonical objects and atomic storage
04
P2P nodeDiscovery and repository sync
THE FIRST MILESTONE IS LIVE

Enter the workspace.

Connect your wallet, sign a free challenge, and enter your private development workspace.

Connect wallet →