OUTERNET Testnet Whitepaper & Roadmap

This document describes a live testnet, not a live financial network. Every token named below - CCT, ETHTEST, USDCTEST, REPT - is a participation/points token created for this testnet only. None of them have been issued through, or are backed by, any real currency, security, or asset, and none of them will convert into real value without a completed independent security audit and legal/regulatory review first. There is no fixed date for that, and nothing here should be read as a promise that it is coming.

What OUTERNET Actually Is

OUTERNET is CreditChain's live testnet: a real proof-of-stake + reputation (PoSR) blockchain, written from scratch in Go, currently run across two independently operated nodes that gossip transactions, produce blocks, and reconcile their chains with each other over a plain HTTP peer protocol. It is not a simulation or a mockup sitting on top of a database - every balance, loan, vote, and validator record shown in the dashboard is the result of a real signed transaction that was sequenced into a real block.

How It Operates - the short version

• Wallets are self-certifying. Registering generates a real Ed25519 keypair in your browser; your address is derived directly from your public key (SHA256(publicKey)[:20]). The node never needs to have seen your address before to trust a request from it.
• Every mutating action is signed. Staking, borrowing, voting, transferring - each one is signed client-side with your private key before it ever reaches the server, and every node independently re-verifies that signature before acting on it. Nothing is trusted just because "the server said so."
• Nothing changes instantly. Submitting an action (a stake, a vote, a loan) queues a transaction; the actual balance/loan/ vote change happens exactly once, when a validator confirms it inside a block. This is what lets two independently-run nodes end up with byte-identical state instead of quietly drifting apart.
• Validators are chosen by stake + reputation. PoSR selection weighs both how much a validator has staked and their on-chain reputation score, and a validator can only produce blocks through the specific node its owner explicitly delegated to - not any node that happens to know about it.
• Reputation is one score, used everywhere. A single 0-100 Reputation value per wallet drives your Credit Tier (Bronze → Silver → Gold → Diamond → Genesis), which in turn sets your borrow limit, your interest rate, and now your REPT progression rewards - see below.

Sections of the OUTERNET Dashboard

Each entry below is a real, working page - what it's for and what it actually does on-chain.

Wallet (Register / Login)

Generates a real Ed25519 keypair client-side
Address = SHA256(public key)[:20]
Private key never leaves the browser

The one-time entry point. There is no username/password account behind the scenes - whoever holds the keypair in local storage on your device IS the account. Losing it means losing access to that address, exactly like a real wallet.

Faucet

One claim per address
Funds a fresh wallet with starter test CCT

Lets a new tester get moving without needing someone else to send them funds first.

Staking

Stake ETHTEST -> earn CCT rewards
Unstake -> enters an unbonding period before funds are available

Staked ETHTEST also counts as collateral for borrowing, and is what qualifies a wallet to register as a validator once it clears the minimum stake threshold.

Borrow & Lend

Requires collateral: locked CCT OR staked ETHTEST
Borrow limit + interest rate scale with Credit Tier
Borrowed funds land in USDCTEST - a separate ledger from CCT,
so "earned" and "borrowed" balances are never mixed together

Repaying a loan on time (and funding one as a lender) both raise your reputation - the credit-scoring half of the "CreditChain" concept, in its current, collateral-gated form.

Reputation & REPT

Credit Tiers: Bronze < Silver < Gold < Diamond < Genesis
REPT mints once, the FIRST time you ever reach a new tier:
  Silver 50 - Gold 200 - Diamond 750 - Genesis 2500
Dropping a tier and climbing back does not re-mint it

REPT is the newest addition: a token whose entire supply is earned through genuine reputation progression, not staking or borrowing - a way for "your reputation gained value" to mean something concrete.

Governance

Create a proposal -> open for voting
Vote weight = your current voting power

Every proposal and every vote is itself a signed, block-confirmed transaction - governance history is part of the chain, not a separate poll system bolted on top of it.

Validator Dashboard

Register once staked + reputable enough
Delegate block production to a specific node
Track blocks produced, missed blocks, slash count, uptime

Shows whether you're the currently elected leader, and - if a validator misses a round or double-signs - the slashing penalty that gets applied, replicated identically across every node.

Explorer

Paginated block list + paginated transaction list
Search by block #, block hash, transaction id, or address

A real block explorer: browse recent activity a page at a time instead of an unbounded dump, or search the full chain directly for anything older than what's currently on screen.

Identity, Settings

Surface the same underlying wallet/node identity and local preferences - no separate account system, no separate database record of who you are beyond the keypair itself.

Architecture Recap

Backend:     Go, no external framework, vanilla net/http
Consensus:   Proof of Stake + Reputation (PoSR)
Networking:  HTTP-based peer gossip (tx/block/chain sync),
             shared-secret gated between known peers
Persistence: JSON snapshots to disk (blockchain.json / state.json)
Auth:        Signed request envelopes (Ed25519) on every
             mutating endpoint - no passwords, no sessions
Frontend:    Plain HTML/CSS/JavaScript, Web Crypto API for
             client-side signing

Known, Disclosed Limitations

Every item below is a deliberate, currently-accepted simplification - not a hidden bug:

• A chain fork that diverges from a block a node has already applied does not auto-resolve; it requires manual operator intervention rather than risking silent state corruption.
• A validator's "missed block" report is trusted from whichever node reports it first, once confirmed on-chain - there is no multi-node confirmation requirement for that specific offense type yet (double-signing, by contrast, is independently re-verified from cryptographic evidence by every node before it's applied).
• No independent security audit has been performed. This whitepaper and the disclaimer banner shown throughout the app say so on purpose, and will keep saying so until one has.

Roadmap

Phase 0 - Testnet Core (live now)

• ✓ PoSR consensus with automatic block production
• ✓ Signed-request authentication on every mutating action
• ✓ Real 2-node P2P network with gossip + chain sync
• ✓ Staking, borrowing, governance, reputation, REPT
• ✓ Slashing for missed blocks and double-signing
• ✓ Block explorer with pagination and search

Phase 1 - Hardening the Testnet

• ☐ Domain name + real TLS certificates in front of both nodes
• ☐ Automated backups of chain/state data
• ☐ Broader validator set beyond the current two operator-run nodes
• ☐ Multi-node confirmation for missed-block slashing reports

Phase 2 - Growing the Testnet

• ☐ Wider tester onboarding beyond the initial pilot group
• ☐ Developer-facing token registry (custom testnet tokens with their own CCT-paired liquidity pool)
• ☐ Independent professional security audit

Phase 3 - Beyond Testnet (not scheduled)

Any path from testnet participation tokens toward real value would require the audit above, plus separate legal and regulatory review, completed first. That work has not started and this roadmap does not promise a date for it.