Whitepaper

01

Abstract

Protocol overview

Cosanta is an open-source, decentralized payment network whose native asset is COSA.

The network maintains a public UTXO ledger without a central issuer or settlement operator. Independent nodes validate every transaction and block against the same consensus rules. Stakers create blocks, while a collateralized masternode layer provides quorum-based services and decentralized governance.

Independent validation

Every full node checks transaction signatures, unspent outputs, block structure, stake proofs and reward limits before accepting state.

Stake-based security

After the bootstrap phase, block production uses Proof of Stake instead of continuous competitive hash computation.

Two-tier network

Deterministic masternodes form quorums for transaction locks, block locks and governance without replacing full-node validation.

Protocol heritage

Cosanta Core is a fork of Dash Core and retains its Bitcoin-derived UTXO model, peer-to-peer networking and service-node architecture. Cosanta changes network identity, monetary parameters and consensus by activating PoS at block 100,000.

Open the upstream Dash Core repository

02

System model

Network architecture

Cosanta separates local key management, consensus validation and service-layer quorum duties. This separation keeps wallet ownership distinct from block production and masternode operation.

Wallets Exchange APIs Explorer

Cosanta Core

P2P network Mempool UTXO Validation

Layer 01 Proof-of-Stake chain Block production and ordered ledger

Layer 02 Masternode network LLMQ services and governance

Full node

Downloads the chain, maintains the UTXO set and independently enforces all consensus rules. A full node does not need to be a masternode.

Staker

Runs a synced wallet with eligible COSA outputs and signs a valid PoS block when an output finds a stake kernel.

Masternode

Locks the required collateral, registers on the deterministic list and participates in service quorums when selected.

Wallet or integration

Creates and signs transactions, tracks confirmations and queries a trusted local node or a separately secured service.

03

Proof of Stake

Proof-of-Stake consensus

PoS has been enforced on Cosanta mainnet since block 100,000. It makes ownership of an eligible UTXO, rather than raw hashing power, the resource used to propose a block.

The target interval is 150 seconds and difficulty is adjusted continuously. Block discovery remains probabilistic: holding eligible stake increases the expected chance of producing a block but does not create a fixed or guaranteed return.

01

Select eligible outputs

The staking wallet considers unspent COSA outputs that meet confirmation rules and have existed for at least 86,400 seconds. Masternode collateral is protected from staking by default.
02

Test the stake kernel

The node tests eligible outputs and permitted timestamps against the current PoS target. More eligible value increases expected selection probability.
03

Construct and sign

When a kernel meets the target, the wallet constructs the block stake transaction, includes valid mempool transactions and signs the block with the key controlling the selected output.
04

Validate and propagate

Peers verify that the output is unspent and mature, the kernel and timestamps satisfy the target, signatures are valid and the claimed reward does not exceed consensus limits.

Conceptual probability P(block) ∝ eligible stake ÷ network difficulty

This relationship explains expected selection only; the implementation evaluates discrete stake kernels, and short-term results may differ substantially from the average.

PoS activation #100,000

Minimum stake age 86,400 s

Target spacing 150 s

Difficulty retarget Every block

Staking requires a fully synchronized node and safe access to the signing key. Encrypt the wallet, keep offline backups and unlock only for staking where supported. Pool yield depends on the staking rewards actually earned and on the pool’s luck in finding blocks. Wrapped COSA represents the operator’s obligation to users: the service accepts native COSA and issues BEP-20 tokens in return. Their market price and tradability are supported by liquidity provided on PancakeSwap.

04

Service layer

Masternodes and quorums

A deterministic masternode list anchors a second network tier. Collateral proves a long-lived economic commitment; it does not grant permission to change consensus rules. Full nodes still verify the resulting transactions, blocks and quorum signatures.

Regular masternode collateral 10,000 COSA

Evo masternode collateral 40,000 COSA

Collateral remains under the owner’s key but must stay unspent while the masternode is registered and active.

IS

InstantSend

Locks transaction inputs through an LLMQ signature so conflicting spends can be rejected before ordinary block depth accumulates.

CL

ChainLocks

Signs the first valid block observed at a height, making deep reorganizations substantially harder once the network accepts the lock.

DAO

Governance

Active masternode operators vote on proposals; approved payments can be settled through the protocol’s superblock budget mechanism.

Mainnet quorum profiles in Cosanta Core
Service	Quorum profile	Protocol role
ChainLocks	`LLMQ_400_60`	Threshold signing for block locks
InstantSend	`LLMQ_60_75`	Rotating quorum for deterministic transaction locks
Platform	`LLMQ_100_67`	Quorum profile reserved for platform services

05

Planned Layer 2

Cosanta Platform: planned Layer 2

Architecture status Planned · not active on mainnet

The Layer 2 network does not yet process user state and is not part of active Cosanta consensus. The design below describes the intended development direction, not a currently operating product.

Cosanta plans to build its own Layer 2 platform as a fork and adaptation of the open-source Dash Platform stack, using Tenderdash as its BFT consensus engine.

Tenderdash is a Tendermint fork adapted for dynamic masternode quorums and BLS threshold signatures. It is the consensus component of the platform; state storage, the data protocol and developer interfaces form separate layers. In the Cosanta version, these components are intended to integrate with the Layer 1 PoS chain and the Cosanta deterministic masternode list.

LAYER 1 · ACTIVE

Cosanta Core

Native COSA, UTXO payments, emission, Proof of Stake, masternodes and Layer 1 finality remain on the primary chain.

PoS / UTXO Deterministic masternodes LLMQ_100_67

L1 ↔ L2 anchor Planned validator selection and rotation from deterministic masternodes using the LLMQ_100_67 profile.

LAYER 2 · PLANNED

Cosanta Platform

A separate state chain for fast confirmation, verifiable data changes and decentralized application services.

Tenderdash BFT consensus, voting rounds and a quorum threshold signature

Drive / Protocol State-transition execution, storage and cryptographic proofs

DAPI / SDK A decentralized API and client access to Layer 1 and Layer 2

BFT finality

A block commits after agreement by more than two thirds of the active validator set. If a quorum cannot be reached, finalization should halt to preserve state consistency.

LLMQ and BLS

Tenderdash replaces a static validator set with rotating masternode subsets. A BLS threshold signature represents the quorum decision as one compact signature.

Same-block execution

The target design inherits same-block execution: the AppHash committed in a block header represents state after the included transitions have executed.

Data contracts, not EVM

The planned platform targets identities, documents and schema-governed data with signed state transitions. It does not imply EVM compatibility or arbitrary Solidity contracts.

Implementation stages

01

Fork and adaptation

Select a compatible Tenderdash/Platform baseline, replace network identities and integrate it with Cosanta Core, PoS and the masternode model.

02

Credit pool funding consensus.MN_RRHeight = 1013576;

At mainnet block 1,013,576, MN_RR activates and the protocol begins reallocating the Platform share of the masternode reward to the credit pool. This starts funding the pool; it does not launch or activate Cosanta Platform.

03

Devnet and testnet

Test DKG, validator rotation, quorum-loss halts, deterministic state, DAPI and protocol upgrades under adversarial conditions.

04

Separate Platform launch

Cosanta Platform will launch later through a separate activation process, after devnet and testnet validation, public specifications, audits and operator software are ready. Block 1,013,576 is not the Platform launch height.

The LLMQ_100_67 profile already exists in Cosanta Core parameters, but this alone does not mean Layer 2 is live. Until a separate activation, performance, fees, application features and platform economics remain design targets.

06

UTXO ledger

Transactions and the UTXO ledger

COSA is accounted for as unspent transaction outputs. A transaction consumes existing outputs and creates new outputs whose spending conditions are defined by scripts and cryptographic keys.

01 Select inputs Reference unspent outputs

02 Sign Authorize with private keys

03 Propagate Nodes validate and relay

04 Settle PoS block and quorum locks

No account balance in consensus

A displayed wallet balance is the sum of spendable UTXOs controlled by its keys. Change from a payment is normally returned as a newly created output.

Fees

The difference between total inputs and outputs is the transaction fee. Nodes apply relay and mempool policies in addition to block-level consensus checks.

Key ownership

The protocol recognizes valid signatures, not identities or support requests. Losing a private key or recovery phrase generally means losing control of its COSA.

Confirmation and locks

A block confirmation orders the transaction in the PoS chain. InstantSend and ChainLocks add quorum-signed protection against conflicting spends and reorganizations.

07

COSA economics

Emission and distribution

COSA has a protocol-defined emission curve with an approximate maximum supply of 56.04 million coins.

The launch used a low-reward PoW bootstrap. PoS activated at block 100,000, masternode payments began later, and the base subsidy rises in scheduled steps before entering long-term halvings. Transaction fees are added to the permitted block reward and do not create additional supply by themselves.

Fair launch

Launched without a premine

The Cosanta mainnet launched publicly on 16 July 2021 without a pre-created reserve of native COSA allocated before the chain started. Coins entered circulation through protocol-defined rewards for blocks produced by network participants.

Native COSA premine: 0 COSA
Public launch: 2021-07-16
Initial block reward: 0.01 COSA

The no-premine statement applies to the native COSA coin and the Layer 1 launch. The later BEP-20 contract representation on BNB Smart Chain has a separate supply and distribution history.

Launch statement ↗ Public reward schedule ↗

Condensed mainnet subsidy schedule
Block range	Base subsidy	Protocol phase
0–99,999	0.01 → 0.09 COSA	PoW bootstrap and monopoly protection
100,000–525,251	0.10 → 0.50 COSA	PoS active; gradual subsidy ramp
525,252–999,999	0.50 → 45 COSA	PoS with progressive masternode allocation
1,000,000–≈1,048,576	50 COSA	Peak base subsidy and budget activation
≈1,048,576–≈2,097,152	25 COSA	First scheduled halving
≈2,097,152+	12.5 COSA, then halved at scheduled intervals	Long-term finite emission

Treasury

After the budget start height, the protocol reserves a subsidy share for approved governance payments through superblocks.

Service rewards

The masternode share begins at 0.1% and is progressively reallocated toward the long-term 60% target defined in Core.

Supply cap

The maximum is an emission-schedule result, not a freely mintable token setting. Consensus rejects rewards above the permitted subsidy.

Liquid staking

Wrapped COSA on BNB Smart Chain

BNB Smart Chain BEP-20

Wrapped COSA is a BEP-20 token connecting the native Cosanta network to a staking pool and the BNB Smart Chain ecosystem. A user can deposit native COSA into the pool and receive wrapped COSA under the service rules. The pool aggregates deposits and uses the native coins for staking on the Cosanta network, while the token remains available in the user’s compatible wallet.

Native COSA and wrapped COSA are recorded on separate ledgers: the former on the Cosanta UTXO blockchain, the latter by a BEP-20 contract on BNB Smart Chain. The wrapped token does not create additional native-coin emission at the Cosanta protocol level.

01 Native COSA Coins exist on the primary Cosanta UTXO network.

02 Pool deposit The user sends COSA to the staking-pool service address.

03 Pooled staking The pool aggregates native coins and participates in block creation.

04 Wrapped COSA The pool transfers BEP-20 tokens from its existing reserve to the user.

How to obtain wrapped COSA

Route A · gateway

Obtain wrapped COSA through @piratecash_bot

The exchange is performed through @piratecash_bot: deposit native COSA and request a withdrawal of wrapped COSA to your BNB Smart Chain (BEP-20) address.

Open @piratecash_bot

Route B · swap

Buy on PancakeSwap

Wrapped COSA can also be acquired directly from an available liquidity pool with a BNB Smart Chain-compatible self-custody wallet.

Open PancakeSwap

Official wrapped COSA contract · BNB Smart Chain 0x5f980533b994c93631a639deda7892fc49995839 BscScan ↗ Fixed supply: 64,000,000 COSA · 8 decimals · the full supply was minted when the contract was deployed

Trust boundaries and risks

Wrapped COSA and staking-pool operation are outside the Cosanta mainnet consensus. The contract does not mint tokens automatically on deposit and does not implement a native trustless bridge: cross-network conversion is operated by the project gateway from the existing supply. The project gateway available through @piratecash_bot guarantees native COSA ↔ wrapped COSA exchange in both directions. Before depositing or swapping, verify the contract address, distribution and redemption rules, fees and custody terms for native coins. DEX price, yield and liquidity are not guaranteed by the Cosanta protocol.

Bidirectional exchange gateway @piratecash_bot ↗

09

Trust model

Security and trust boundaries

Security is layered: signatures protect ownership, PoS orders valid state transitions, full nodes enforce consensus, and LLMQ signatures add fast protection against transaction conflicts and chain reorganizations.

Conflicting transactions

Nodes reject spends of already consumed outputs, while InstantSend can lock inputs before normal confirmation depth is reached.

InstantSend · UTXO

Chain reorganizations

ChainLocks bind quorum agreement to a block at a given height and reduce the practical scope for reorganizing accepted history.

ChainLocks · LLMQ

Invalid stake or reward

Every node verifies stake eligibility, kernel target, block signature, transaction validity and maximum reward independently.

PoS · validation

Wallet compromise

Consensus cannot restore stolen keys. Encryption, recovery-phrase backups, system hardening and separation of operator keys remain user responsibilities.

signatures · backups

This document describes the protocol; it is not an audit, investment promise or guarantee of uninterrupted operation. The executable Cosanta Core consensus code is authoritative if this overview and an active software release differ.

10

Reference

Integration reference

Production integrations should run a compatible Cosanta Core node, validate the reported network and genesis block, wait for the confirmation or lock policy appropriate to their risk model, and test upgrades before deployment.

Native symbol: COSA
Decimal places: 8
Mainnet P2P port: 60606
Public address prefix: C
Genesis time: 2021-07-16 13:32 UTC
Genesis block hash: 00000216af2a362c1833a0a608408bcdc69d23b276e47d7510a776e3b0bb1fce