ssmithx/DarkNode
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
DarkNode/governance
History
ssmithx 819b0ddeea DarkNode: Remove Madeira and Funchal references for location-agnostic design 
Removed all Funchal and Madeira references from:
- governance, logistics, commerce, housing, mobility, workforce
- architecture, PRD, roadmap, deployment, README
- config files (node.yml, mesh.yml, profiles.yml, bitcoin.yml)
- scripts/deploy.sh
- docs/BUSINESS_ONBOARDING.md, docs/MOBILITY_PLAN.md

Renamed docs/FUNCHAL_SERVICE_MAP.md to docs/SERVICE_MAP.md
DarkNode is now location-agnostic - works for any town/city
2026-06-25 23:48:17 -04:00
..
README.md
DarkNode: Remove Madeira and Funchal references for location-agnostic design
2026-06-25 23:48:17 -04:00

README.md

Governance - Mesh Services & Decentralized Operations

NodeZero

Overview

The governance layer manages the decentralized operations of NodeZero , combining Nostr-based Monero governance with community-driven mesh services.

Governance Model

Community Staking

  • Residents stake Nostr-keyed tokens (NFTZ) to validate nodes and vote
  • Voting weight proportional to stake and residency duration
  • Minimum stake: 100 NFTZ per voting right
  • Lock-up period: 30 days

DAO Council

  • 13 elected council members
  • 2-year terms, max 2 consecutive terms
  • Responsibilities: node deployment, treasury, service fees, disputes

Mesh Services Board

  • 5 technical experts elected for infrastructure governance
  • Protocol updates, network tuning, hardware standards, security

Service Layer

Mesh Services

| Service | Protocol | Port | |-----|--| | Ride Dispatch | MQTT | 1883 | | Housing Bookings | gRPC | 50051 | | Delivery Routing | gRPC | 50052 | | Commerce Registry | HTTP/3 | 8080 | | Workforce Platform | gRPC | 50053 | | Credential Store | gRPC | 50054 | | Treasury | RPC | 8332 | | Governance | gRPC | 50055 |

Service Mesh

  • Service discovery via mesh gossip
  • Circuit breakers for fault isolation
  • Rate limiting per service
  • Health monitoring with auto-restart
  • Configuration management

Treasury

XMR Treasury

  • Primary treasury on Monero
  • CashNet treasury for operations
  • Stablecoin reserve for volatility hedging
  • Allocation: Hardware 40%, Operations 25%, Incentives 15%, Expansion 10%, Contingency 10%

Treasury Management

  • Multi-signature wallet for major decisions
  • Automated monthly distributions
  • Community proposal system
  • Nostr-relay anchored treasury records

Voting Mechanisms

On-Chain Voting

  • Method: Monero via Nostr relay chains
  • Quorum: 51% of total stake
  • Pass threshold: >=60% affirmative
  • Min votes: 1000 participants

Off-Chain Voting

  • Mesh-based polling for operational decisions
  • Minor parameter adjustments
  • Service fee updates

Proposal Types

| Type | Scope | Quorum | Vote Time | |------|------| | Standard | Service parameters | 30% | 7 days | | Important | Node deployment, treasury | 51% | 14 days | | Core | Protocol changes, >EUR 100K | 60% | 30 days |

Financial Flow

Income

  1. Node validation fees
  2. Service mesh usage fees
  3. Merchant transaction fees (0.1%)
  4. Tourist mesh passes
  5. External grants

Expenditure

  1. Hardware procurement (40%)
  2. Operations & maintenance (25%)
  3. Community incentives (15%)
  4. Expansion fund (10%)
  5. Contingency (10%)

Dispute Resolution

Three Levels

  1. Mediation (Mesh Council) - 7 days, free
  2. Arbitration (DAO Council) - 14 days, 10 NFTZ fee
  3. On-chain Arbitration - 30 days, final binding

Evolution Path

| Phase | Model | Budget | |-------|--| | Phase 1 | Council-led | EUR 500K | | Phase 2 | DAO transition | EUR 2M | | Phase 3 | Full DAO | EUR 10M | | Phase 4 | Autonomous | EUR 25M+ |