Phase-1

TESTNET PHASE 1 BETA LAUNCH: DECONSTRUCTING THE VOICE OF THE PROTOCOL

Phase 1 is the foundational public testnet. It validates the voice-driven smart contract engine, the Light Node mesh, the initial developer gateway and the community incentive framework. The objective is to convert human intention to secure on-chain logic while gathering telemetry, security signals and high-quality natural language training data that will guide Phase 2 and Phase 3.

Goals and success criteria

Primary goals

• Validate the Intent Compiler pipeline end to end: voice/ text input → semantic parse → secure code generation → sandbox simulation → attested deployment.

• Bootstrap a robust Light Node mesh that demonstrates distributed uptime, heartbeat claims and NPT accrual mechanics.

• Onboard the first 25,000 testnet participants via a controlled waitlist and Zealy guild campaigns.

• Exercise the API surface for simulation, deploy, attest and claim flows and capture developer feedback at scale.

Phase 1 acceptance criteria

• The intent compiler produces reproducible, compilable contracts in supported languages for 90 percent of validated intents under pilot load.

• Sandbox simulation matches verifier re-execution results 99 percent of the time.

• The mining coordinator correctly enforces step reductions and publishes per-node rates and global counters publicly.

Waitlist, access and incentives

• Phase 1 access is limited to 25,000 participants. Slots are tiered as normal waitlist, quest participants and trusted testers. Priority is assigned using role tiering, developer experience and demonstrated community contribution. Zealy guild campaigns run immediately and are integrated with the waitlist to seed early tasks.

• Participants earn points for onboarding, running nodes, completing API tests, submitting reproducible bugs and participating in Zealy quests. Points map to leaderboard rank and drive NPT reward eligibility, limited edition NFTs and priority access to Phase 2. Top contributors receive special DAO bootstrapping privileges

• Reward rules, campaign manifests and claim procedures are published. All rewards and mint events produce audit receipts that are anchorable to the audit store.

The core innovation: Voice-driven Smart Contract Engine

Phase 1 launches an Intent Compiler that interprets human natural language, extracts required parameters and produces safe, efficient contract artifacts ready for sandbox testing and optional deployment. The system is designed for both developers and non-technical creators.

• Input capture
Voice or typed input captured via API Hunter endpoints or the Base App.
Multilingual ASR converts speech to text when voice is used.

• Semantic deconstruction
Natural language parser extracts entities, actions, triggers, schedules, recipients, assets and constraints.
An intent schema is produced: canonical action, parameters and required clarifications.
• Validation loop
If ambiguity or safety flags are detected, the system asks clarifying questions.
Example: "Should the 24 hour trigger be block time or wall clock time?"
Clarifications are persisted as part of the audit trail.
• Template selection and safe generation
The compiler selects audited templates from the canonical library, applies parameter substitution and generates gas-efficient source code.
The template library is curated and continuously audited.
• Static analysis and AI audit
Generated code is run through linters, static analyzers and an AI-assisted security detector that highlights reentrancy, unchecked transfers, risky oracles and potential MEV exposure.
High risk findings block deployment until resolved.
• Sandbox simulation
The code is executed in a deterministic sandbox replicating target chain semantics.
The simulation returns execution traces, gas estimates and suggested mitigations.
• Attested deploy
On user approval, the bytecode is deployed.
A verifier committee can re-execute and sign attestations for high-assurance deployments.
All artifacts are anchored to the audit store.

Light Node deep dive

The Light Node is a minimal node client designed to decentralize inference and uptime responsibilities while keeping participation accessible. Light Nodes register on-chain, emit heartbeats, participate in proof of uptime and assist with non-sensitive inference relay tasks. They are the primary recipients of the Lite Node NPT allocation during testnet.

Recommended profile
• Minimum: 6 GB RAM, modest CPU and low disk footprint.
• Function: partial sync, heartbeat channel, local agent for ASR/TTS caching, relay of inference requests to nearby Full/Hosted nodes when needed.

Lifecycle and UX
• Typical CLI lifecycle (reference public repo netrum-lite-node):

git clone https://github.com/NetrumLabs/netrum-lite-node
cd netrum-lite-node
npm install
netrum-new-wallet
netrum-check-basename
netrum-node-sign
netrum-node-register
netrum-sync
netrum-mining
netrum-claim

Claims create on-chain receipts that are verifiable and anchorable.

Architecture (component summary)
• Local Agent and CLI. Wallet, domain checks, local telemetry.
• Heartbeat channel. Persistent connection to mining coordinator for claim eligibility.
• On-chain Registry. Node identity, registration and claims are anchored to Base.
• Mining Coordinator. Aggregates heartbeats and computes per-node accrual.

Mining economics and emission logic

Lite Node mining logic (Phase 1)
Mining rate for Lite Nodes adapts to both total supply and active miner count:

• Per-supply trigger: mining speed drops every 30,000 NPT minted

• Per-miner trigger: mining speed drops every 500 active miners.

• Final stage floor: approximately 0.047 NPT / day per Lite Node in late lifecycle stages

These step triggers are published by the Mining Coordinator. Operators can compute the expected accrual from the public counters.

Full Node
Full Nodes are not yet public in Phase 1 and are expected in later stages.

Next Steps

Now that you have read everything, here's what you can do next:

Testnet Phase 2

Quick Start

Learn the basics and get started quickly.