Back to Home
    Public Specification

    Protocol Specification

    The complete public architecture of Denaris — how it is built, why it is built that way, and which decisions define the protocol at launch.

    30 Sections
    Section 1

    Purpose of This Specification

    This document defines the public protocol architecture of Denaris. It is not intended to be a low-level implementation manual, nor a purely academic formal spec. Its role is to explain how Denaris is built, why it is built that way, and which architectural decisions define the protocol at launch.

    Denaris should be understandable before it asks to be trusted.

    This specification focuses on:

    • The logic of the protocol
    • The scope of the MVP core
    • The relationship between the monetary model and the technical architecture
    • The design choices that distinguish Denaris from both legacy first-generation designs and bloated altcoin architectures
    Section 2

    Protocol Identity

    Denaris is a money-first, proof-of-work settlement protocol.

    What Denaris IS

    Base-layer monetary network
    UTXO-based system
    Modernized proof-of-work architecture
    Deliberate room for future growth

    What Denaris is NOT

    A generalized world computer
    A broad application chain
    An NFT-first chain
    A DeFi execution platform
    A narrative-driven feature aggregator

    Denaris is designed to be serious digital money infrastructure.

    Section 3

    Core Design Objectives

    The Denaris protocol is built to satisfy six main technical objectives.

    3.1

    Monetary Credibility

    The architecture must support the project's monetary identity, not dilute it.

    3.2

    Launch Resilience

    The protocol must launch cleanly and remain stable during the most fragile early network phase.

    3.3

    Network Practicality

    The node, networking, and sync model should remain realistic for technically serious operators.

    3.4

    Architectural Restraint

    The MVP should contain what is necessary and avoid what belongs in later phases.

    3.5

    Future Compatibility

    Leave room for future privacy, L2, smart-policy, and machine-native payment layers.

    3.6

    Technical Legibility

    The design should be understandable, explainable, and defensible.

    These objectives define what Denaris includes — and what it deliberately excludes.

    Section 4

    Consensus Model

    4.1 Proof of Work

    Denaris uses proof of work as its consensus mechanism. This is a foundational decision. Denaris is explicitly designed as a hard-money-oriented protocol, and proof of work remains the most appropriate consensus model for that category because it ties block production to external cost rather than purely internal stake weight.

    • Externally costly block production
    • Objective miner competition
    • Consensus identity legible to users who take monetary neutrality and protocol hardness seriously

    4.2 Why not Proof of Stake?

    Denaris is not trying to optimize for stake-based capital coordination. It is trying to build a neutral monetary base layer with stronger continuity to the proof-of-work tradition, while improving launch architecture, network posture, and protocol discipline.

    This is a category choice, not just a technical choice.

    Section 5

    Launch Mining Architecture

    Mining Algorithm

    RandomX — memory-hard, CPU-friendly, ASIC-resistant

    This is one of the most important protocol decisions in the project.

    5.2 Why this mining model exists

    The purpose of this design is to reduce the probability of immediate launch capture by pre-existing Bitcoin-compatible industrial ASIC infrastructure. A new proof-of-work monetary network launched in 2026 should not pretend that mining hardware asymmetry is irrelevant.

    5.3 Launch mining objectives

    • Broaden early participation
    • Reduce instant industrial domination
    • Improve distribution quality
    • Give the network time to stabilize under more open initial conditions

    5.4 Algorithm: RandomX

    RandomX Algorithm Properties

    Memory-hard (CPU-optimized)

    ASIC-resistant by design

    Proven security track record

    Not SHA-256 clone-compatible

    Section 6

    Block Target and Cadence

    Target Block Interval

    90-second blocks

    6.2 Why 90 seconds?

    This target was selected because it offers a stronger long-term compromise than both slow legacy cadence and overly aggressive fast-block vanity design.

    • Materially faster than Bitcoin
    • Easier to defend than a 60-second launch
    • More stable for relay and propagation
    • Better aligned with Denaris' identity as a serious settlement layer

    Denaris is designed around reliable cadence, not around chasing the shortest possible confirmation rhythm for marketing purposes.

    Section 7

    Difficulty Adjustment

    Adjustment Model

    ASERT-style continuous difficulty adjustment

    The purpose of this model is to keep block production near the target cadence even when miner participation changes quickly.

    Design Benefits

    Cadence consistency

    Network predictability

    Launch-phase resilience

    7.4 Clarification

    Difficulty adjustment protects timing, not total supply by itself. This is why Denaris combines difficulty logic with a reward warm-up phase and a smooth emission model.

    Section 8

    Ledger Model

    Architecture

    UTXO-based ledger model

    8.2 Why UTXO?

    • Clear ownership semantics
    • Clean auditability
    • Stronger coin control
    • Natural compatibility with money-first design
    • Better discipline around custody and transfer logic

    Denaris is designed around money behavior, not generic application sprawl.

    Section 9

    Signature and Output Design

    Denaris launches with a modern cryptographic authorization stack built on Schnorr signatures, native Taproot, and MAST.

    Cryptographic Stack

    Schnorr signatures (secp256k1, 64-byte)
    Native BIP341 Taproot model
    MuSig multi-party aggregation
    MAST conditional payment branches
    Multisig-friendly transaction design
    Future policy-oriented flexibility

    9.3 Benefits

    • Cleaner multisig via MuSig aggregation (appears as single signer on-chain)
    • Future vault structures with hidden spending conditions
    • Policy-based custody logic via MAST branches
    • More modern wallet architecture

    This does not mean Denaris launches as a generalized smart-contract chain. It means it adopts a more modern and composable monetary base-layer design.

    Section 10

    Scripting Scope

    Denaris supports money-adjacent programmable policy, not generalized app-chain execution.

    MVP Scripting Scope vs Exclusions

    Supports

    • Standard spend conditions via Schnorr + Taproot
    • Multisig workflows with MuSig aggregation
    • MAST-based conditional branches
    • Timelocks and custody-oriented policy paths
    • Gasless onboarding via SIGHASH_ANYONECANPAY (sponsors cover fees for new users)
    • Future smart-policy logic compatibility

    Excludes at MVP

    • Broad virtual machine
    • Arbitrary application logic
    • Generalized DeFi execution
    • Gas-market complexity tied to open-ended computation

    Denaris is designed for smart money behavior, not generalized on-chain app sprawl.

    Section 11

    Monetary Logic in Protocol Form

    Headline Supply

    42,000,000 DENRS

    Emission Horizon

    ~60 years smooth emission

    Year One Target

    ~3.4M DENRS

    Tail Emission

    Minimal perpetual security emission

    11.5 Reward Warm-Up Phase

    90-Day Warm-Up Schedule

    Days 0–30
    25%
    Days 31–60
    50%
    Days 61–90
    75%
    Day 91+
    100%

    11.6 Treasury Logic

    Treasury Allocation

    6% transparent development treasury per block

    This is protocol-native reward logic, not a giant premine.

    Section 12

    Treasury Architecture

    12.1 Treasury Role

    • Protocol development
    • Audits
    • Public infrastructure
    • Explorer and client systems
    • Long-term protocol stewardship

    12.2 Why protocol-native?

    Embedding treasury logic into the reward structure is cleaner than creating a large discretionary insider reserve at genesis. It also improves transparency and public legibility.

    Transparency Requirements

    Public

    Documented

    Structurally understandable

    Section 13

    Networking Architecture

    A 2026 protocol should not default to legacy-era networking assumptions if stronger, cleaner choices are available.

    Transport

    Encrypted peer-to-peer transport from launch

    • Seed nodes
    • Public peer discovery
    • Explorer integration
    • Realistic self-hosted node operation

    Network Layer Goals

    Robust

    Practical

    Modern

    Launch-friendly

    Section 14

    Node Philosophy

    14.1 Full-node Realism

    Denaris is designed so that a serious user can run a full node on:

    • A normal VPS
    • A modest self-hosted machine
    • A practical technical environment without institutional-scale hardware

    A monetary protocol loses credibility if meaningful verification becomes unrealistic for technically serious participants.

    14.3 MVP Expectation

    Understandable

    Stable

    Configurable

    Suitable for real-world use

    Section 15

    Wallet and CLI Scope

    The Denaris MVP includes a practical baseline wallet and CLI interaction model. At minimum:

    Address generation

    Send & receive

    Balance visibility

    Mining payout routing

    Operational control

    Chain-state inspection

    A protocol is not launch-ready if it can only be understood conceptually. Denaris must be operationally legible as well.

    Section 16

    Privacy Posture: BIP 352 Implementation

    Privacy-aware, not privacy-maximalist.

    16.1 Mechanism — Silent Payments (BIP 352)

    Denaris utilizes BIP 352 (Silent Payments) as its primary privacy layer. Each transaction creates a unique P2TR (Pay-to-Taproot) output that is cryptographically tied to the recipient but mathematically indistinguishable from regular outputs to third-party observers.

    16.2 The Shared Secret

    The protocol uses the sender's private key and the receiver's scanning key to generate a shared secret, which is then used to "tweak" the recipient's public key for the specific transaction. This ensures that no link can be established between multiple payments to the same entity by analyzing the public ledger.

    16.3 Light Client Optimization

    To maintain "Zero-Sync" performance, Denaris employs GCS (Golomb-Coded Sets) filters. This allows mobile wallets to scan the blockchain for their specific Silent Payment outputs without compromising privacy or downloading unnecessary data.

    16.4 Alias Synergy

    The Denaris Alias system acts as the frontend for Silent Payments, allowing users to send "invisible" payments to a simple @name handle.

    16.5 MVP Privacy Components

    • BIP 352 Silent Payments for non-interactive one-time addresses
    • A more modern network transport posture
    • Cleaner metadata assumptions
    • GCS filters for privacy-preserving light client scanning

    16.6 Future Privacy Direction

    • Stronger address privacy extensions
    • Improved wallet-level privacy tooling
    • More advanced optional payment privacy features

    Silent Payments let Denaris achieve high-grade financial confidentiality without the regulatory baggage of "Privacy Coin" architectures.

    Section 17

    L2 and Data-Lane Readiness

    Denaris is built in the L2 era, and its architecture reflects that.

    MVP Position

    L2-ready / DA-ready — not activated at genesis

    • Scalable settlement structures
    • Cleaner transient data publication
    • Machine-native payment overlays
    • Future protocol-layer extensibility

    Denaris is designed for scalable settlement, not for launch bloat.

    Section 18

    AI Readiness

    Denaris is not designed as an AI-branded protocol. However, it ships with concrete infrastructure for machine-native interaction.

    The protocol includes:

    • AI-Agent RPC proxy — a Role-Based Access Control (RBAC) gateway allowing autonomous software bots to hold restricted API permission keys (e.g., 'ConditionalSpender') and transact securely within defined boundaries.
    • Denaris Sentinel — experimental interception hooks for AI-driven heuristic scam detection in the mempool, flagging suspicious transactions before confirmation.
    • Machine-readable monetary infrastructure for autonomous value transfer.
    • Explorer and wallet compatibility with intelligent AI-adjacent tooling.

    AI-ready with concrete tooling, not AI-dependent marketing. That is the correct architectural and brand posture.

    Section 19

    Explorer Compatibility

    Denaris is intended to be explorer-friendly from launch. A serious protocol should offer public visibility into:

    • Block production
    • Transaction activity
    • Chain progression

    19.3 MVP Expectation

    • Block indexing
    • Transaction indexing
    • Basic public chain transparency
    Section 20

    Advanced Authorization Model

    Denaris implements a complete modern authorization stack: 64-byte Schnorr signatures on secp256k1, native BIP341 Taproot with hidden spending conditions, MAST branching for conditional payment logic, and MuSig aggregation for multi-party signatures that appear as a single signer on-chain. Gasless onboarding is achieved through specialized SIGHASH_ANYONECANPAY signature hashing, allowing sponsors to cover transaction fees for new users at the consensus level.

    Authorization Stack

    Schnorr (secp256k1, 64-byte)
    Native BIP341 Taproot
    MAST conditional branches
    MuSig multi-party aggregation
    SIGHASH_ANYONECANPAY gasless
    Taproot-tweaked key paths

    Modern authorization, not complexity for its own sake.

    Section 21

    Vault and Recovery Architecture

    Denaris is designed with stronger self-custody assumptions in mind. That includes delayed paths, recovery-aware spending models, and clearer multi-path authorization structure. The objective is not to turn the chain into a general smart-contract platform, but to support stronger money custody patterns directly within a disciplined monetary architecture.

    Custody Architecture Direction

    Delayed Paths

    Time-gated spending

    Recovery Models

    Safe fallback routes

    Multi-Path Auth

    Structured access

    • Vault-style delayed spending logic
    • Recovery-aware authorization paths
    • Multi-path custody structure
    • Not a smart-contract platform — money custody discipline
    Section 22

    Treasury Safety Model

    Denaris does not frame treasury funds as a simple founder-controlled wallet. The architecture direction includes delayed release logic, operator safety layers, emergency control thinking, and cleaner stewardship structure. The treasury is intended to behave more like protocol infrastructure than discretionary loose capital.

    Treasury Safety Layers

    Delayed Release

    Time-gated disbursement logic

    Operator Safety

    Layered access controls

    Emergency Controls

    Crisis response architecture

    Clean Stewardship

    Protocol-grade governance

    The treasury is protocol infrastructure, not discretionary loose capital.

    Section 23

    Light Client Direction

    Denaris is not being designed only around heavyweight full-node assumptions. Its architecture also considers future light-client and lightweight verification directions, including cleaner query surfaces, proof-oriented flows, and more practical client access patterns over time.

    Light Client Design Considerations

    Clean query surfaces

    Proof-oriented flows

    Practical access patterns

    Lightweight verification

    Section 24

    Adaptive Fee Market

    Rather than assuming static transaction pricing forever, Denaris combines ASERT-style difficulty adjustment with Elastic Block Space — dynamically sized blocks that expand under congestion — supplemented by real-time Transaction Telemetry at the P2P layer, effectively eliminating "pending transaction anxiety" for end users.

    Fee Direction

    ASERT + Elastic Block Space + Transaction Telemetry

    • Dynamic fee estimation under load with Elastic Block Space
    • Real-time P2P transaction telemetry for confirmation visibility
    • Smarter transaction prioritization
    • Congestion-responsive pricing
    • Preserved auditability and monetary discipline
    Section 25

    Upgrade and Activation Architecture

    Future protocol improvements should not be introduced through chaos. Denaris is being designed with structured deployment, activation, compatibility, and rollout discipline in mind, so future features can be introduced through clearer lifecycle logic and lower split risk.

    Upgrade Lifecycle

    Proposal

    Define scope

    Deployment

    Code release

    Signaling

    Network readiness

    Activation

    Clean transition

    Protocol improvements through discipline, not chaos.

    Section 26

    Stateless-Ready Direction

    Denaris considers longer-term Utreexo accumulator and stateless-oriented directions. This does not mean the launch system is fully stateless, but it does mean the architecture is already shaped with state commitment, proof-carrying validation direction, Zero-Sync (ZK-STARK) preparation, and future node-burden reduction in mind.

    Stateless Architecture Direction

    Utreexo accumulators

    State commitments

    ZK-STARK preparation

    Node burden reduction

    Section 27

    Quantum Migration Readiness

    Denaris is not pretending to be post-quantum today. Instead, it is being built with migration discipline in mind: cleaner upgrade paths for key families, future cryptographic transition planning, and architecture that can evolve if long-term assumptions around signatures and security materially change.

    • Cleaner upgrade paths for key families
    • Future cryptographic transition planning
    • Architecture that evolves with security assumptions
    • Migration discipline, not post-quantum theater

    Not post-quantum theater — migration discipline built into the architecture.

    Section 28

    What Denaris Deliberately Excludes From MVP

    Denaris is defined not only by what it includes, but by what it deliberately refuses to force into genesis.

    Excluded From MVP

    Generalized smart-contract VM
    App-chain identity
    NFT-oriented primitives
    Full privacy-heavy launch complexity
    Full blob lane activation at genesis
    Protocol-level AI dependence
    Unnecessary consensus-adjacent novelty

    This is not a lack of ambition. It is protocol discipline.

    Section 29

    MVP vs V2 Boundary

    MVP Includes

    • Proof of work
    • UTXO accounting
    • Memory-hard launch mining
    • 90-second blocks
    • Continuous difficulty adjustment
    • Modern signature/output posture
    • Money-policy scripting
    • Treasury logic
    • Launch warm-up logic
    • Encrypted networking
    • Node and CLI baseline
    • Explorer compatibility

    V2 May Include

    • Richer fee/package relay behavior
    • Stronger policy extensions
    • More advanced privacy improvements
    • Deeper L2/data-lane activation
    • Stronger developer/operator ergonomics

    Denaris is strongest when the launch protocol is clean, credible, and sharp — not overloaded.

    Section 30

    Summary

    Denaris is a proof-of-work, UTXO-based, money-first protocol designed to modernize where crypto learned something useful and remain conservative where money infrastructure requires discipline.

    • Proof-of-work credibility
    • Launch-resilient mining architecture
    • Continuous difficulty adjustment
    • 90-second block targets
    • Smooth long-horizon issuance
    • Minimal perpetual security emission
    • Transparent treasury logic
    • Modern network assumptions
    • Future-ready restraint

    Denaris is not trying to become everything. It is trying to become one of the strongest modern monetary base layers in the category.

    Appendix

    Protocol Snapshot

    Protocol Name

    Denaris

    Project Label

    Project Denaris

    Ticker

    DENRS (working)

    Consensus

    Proof of Work (RandomX)

    Mining Posture

    RandomX CPU-friendly, ASIC-resistant

    Ledger Model

    UTXO

    Block Target

    90 seconds

    Difficulty Model

    ASERT continuous + Elastic Block Space

    Signature Scheme

    Schnorr (secp256k1)

    Headline Supply

    42,000,000 DENRS

    Emission Horizon

    60 years

    Tail Emission

    Minimal perpetual

    Deflationary Mechanism

    20% Base Fee Burn

    Treasury

    6% protocol dev

    Base Address

    Base58 / Denaris Alias System

    Launch Phase

    90-day warm-up

    Networking

    Encrypted P2P