[ IDENTITY ]

ncbd.dev█

Not Centralized, But Distributed

[ STATUS ]
NODES1,247
UPTIME99.97%
LATENCY12ms
CONSENSUSACHIEVED
PEERS834
[ NAVIGATION ]
> about > topology > principles > disconnect
[ CONTENT ]

$ cat about.txt

ncbd.dev is a philosophy encoded as infrastructure. Every node in the network is both client and server, both consumer and provider. There is no center to attack, no single point of failure, no authority that can unilaterally alter the shared state.

$ cat philosophy.txt

Decentralization is not merely a technical architecture. It is a statement about trust, resilience, and the distribution of power. When no single entity controls the network, the network belongs to everyone who participates in it.

$ cat technical.txt

Built on a gossip protocol with Byzantine fault tolerance, ncbd achieves consensus across geographically distributed nodes without requiring a coordinator. State synchronization occurs through Merkle-DAG structures that enable efficient verification of data integrity.

[ NETWORK TOPOLOGY ]
         ┌──────┐
         │ NODE │
         │  001 │
         └──┬───┘
       ┌────┴────┐
   ┌───┴──┐  ┌───┴──┐
   │ NODE │  │ NODE │
   │  002 │  │  003 │
   └───┬──┘  └───┬──┘
   ┌───┴──┐  ┌───┴──┐
   │ NODE │  │ NODE │
   │  004 │  │  005 │
   └───┬──┘  └──┬───┘
       └────┬────┘
         ┌──┴───┐
         │ NODE │
         │  006 │
         └──────┘

$ Each node maintains connections to 3-7 peers. Network self-heals on node departure within < 200ms.

[ PRINCIPLES ]

[001] REDUNDANCY — No single point of failure. Every piece of data exists on multiple nodes. The network survives the loss of any individual participant.

[002] TRANSPARENCY — All protocol changes are proposed, debated, and ratified by network participants. The rules are visible to everyone who follows them.

[003] SOVEREIGNTY — Each node controls its own data and participation. No external authority can compel a node to act against its operator's wishes.

[004] RESILIENCE — The network routes around damage. Partitions heal. Consensus reconverges. The system was designed to survive adversarial conditions.

[005] SIMPLICITY — The protocol is minimal by design. Complexity is the enemy of security. Every feature must justify its existence against the cost of its attack surface.