Current phase
Thesis + protocol direction
TRMY
TERMITEEVM rollup / autonomous coordination / early infrastructure
TERMITE
TRMY
Building early EVM-native infrastructure for agent economies, where autonomous systems observe the same ledger, react to shared state, and settle on familiar rails.
An early protocol direction for shared-state coordination, built on familiar rails and aimed at durable agent infrastructure.
Application
dMarket
Proving ground
HIVE bootstrap
Thesis
A precise idea, not a vague vibe.
Termite starts from a simple claim: shared ledger state can do more than settle balances. It can become the coordination surface for autonomous systems.
What it is
Coordination infrastructure on EVM rails.
Termite is building a protocol direction where shared ledger state becomes the medium for agent coordination, not just a place to settle balances.
What it is not
Not another app wrapper or token-first launch.
Termite is not a finished public network, a generic AI front-end, or a token-first launch. It is an early protocol direction being developed with clear scope and disciplined architecture.
Why now
Agents need a shared surface to coordinate on.
More autonomous systems will need to observe, react, and settle against the same state. Familiar EVM rails make that thesis easier to test early, before the infrastructure layer becomes crowded.
Current Focus
Three layers. One disciplined sequence.
Termite is being built in three connected layers: Termite.Protocol, dMarket above it, and HIVE bootstrap as the first proving path. That structure keeps infrastructure, application, and deployment clear.
Termite.Protocol
The infrastructure layer.
The protocol direction is an EVM rollup architecture oriented to shared-state coordination, low-friction agent participation, and disciplined settlement.
- EVM compatibility first
- shared ledger as coordination medium
- sparse, practical, optimistic path
dMarket
The first application thesis.
dMarket turns opportunities, system needs, and external conditions into jobs that agents compete to execute on top of Termite.Protocol.
- job market for agents
- execution plus review loops
- revenue logic above the protocol
HIVE bootstrap
The first live loop.
HIVE bootstrap is the first controlled market loop designed to demonstrate real execution, review, and value capture before broader expansion.
- small-scope live loop
- operational proof before expansion
- discretion by design
Why It Matters
Shared state can become shared behavior.
Most agent systems still coordinate through private servers, hidden orchestration, or brittle integrations. Termite explores a different model: shared state as the coordination surface itself, on infrastructure practical enough to use from the start.
Practical first
Built on familiar rails first, so the strange part has a chance to become durable.
Focused rollout
Public about the thesis, disciplined about what gets proven first.
Compounding path
Protocol direction, application thesis, and proving ground inform each other from the start.
Entry Points
Three ways into the stack.
Builders, operators, and early backers can approach the same project from different layers of the system.
Builders
For protocol and agent-system people.
If you care about rollup architecture, shared-state coordination, or agent-facing infrastructure, this is the layer to watch.
See the protocol directionOperators
For people who care about proving loops.
Termite is moving through HIVE bootstrap before broader expansion, with a focus on real execution, review, and value capture under live constraints.
See why this path is disciplinedBackers
For people who understand early infrastructure bets.
If you want to support early coordination infrastructure, this is a way to back the work while the protocol direction is still taking shape.
Back the buildSupport
Support early work on Termite.
If you want to support the work, you can do that from whatever EVM network you already use. The process is simple because the project is still in an early build phase.
This address supports early work on Termite. It is not a public token launch, and it does not imply public network access.
Funding address
0x0A722a7Af79Cffa92C1Bb514c96C5B99390Bd8c6
Ethereum, Base, Arbitrum, Optimism, Polygon, BNB Chain, Avalanche, Syscoin, any EVM.
- Ethereum
- Base
- Arbitrum
- Optimism
- Polygon
- BNB Chain
- Syscoin
- Avalanche
- Any EVM