Live Network

SIKKA: The blockless
smart ledger. ⚑

A radically simple, parallel-scalable currency for humans, autonomous agents, and machines. πŸ€–

πŸ’Έ 0 Fees  β€’  πŸ›‘οΈ Quantum-Safe  β€’  🌐 Tor-Native  β€’  🀝 Native Multisig

Join Discord Web Wallet Source Code
Live Network Telemetry

Watch the DAG grow in real time

Every transaction extends the graph with exactly two parents. Tips glow β€” click any node to explore or simulate a new attachment.

DAG Size
β€”
Active Tips
β€”
PoW Difficulty
β€”
Work Factor
β€”
Why SIKKA?

A scalable smart ledger. Not a blockchain.

Zero Fees

SIKKA has strictly 0 fees. When you send SIKKA, the exact amount arrives. No gas, no priority fees, no hidden costs.

Blockless Architecture

Technically, SIKKA is not a blockchain. It uses no Proof of Stake and no global Proof of Work race. Every transaction is its own accepted unit extending the DAG.

Parallel Scalable

Unlike blockchains that congest, SIKKA is parallel scalable. Because transactions process asynchronously, the more users interact with the network, the faster it gets.

Architecture

Traditional Chains vs Sikka

Traditional Blockchains Sikka DAG
Wait for next block Attach instantly to DAG tips
Sequential chain growth Parallel graph growth
Miners or validators decide ordering Transactions extend graph directly
Transaction fees & gas Exact-value feeless transfers
Classical signatures ML-DSA-87 post-quantum signatures
Global block race Per-transaction work
Core Protocol

Elegantly simple invariants.

Exactly Two Parents

Every non-genesis transaction references precisely two earlier transactions. A true directed acyclic graph, not a blockchain.

Exact Balance Only

Inputs must exactly equal outputs. There is no fee field. The sender transmits the full amount with cryptographic certainty.

Per-Transaction PoW

Each transaction mines its own SHA3-256 nonce. This provides built-in spam resistance. Abusive traffic becomes computationally expensive as difficulty scales with network congestion.

Proof of Work

Spam resistance without fees.

Sikka has no gas and no miner fees. Instead, every transaction solves a SHA3-256 puzzle whose difficulty rises automatically when the network is busy β€” a CPU cost for attackers, not an economic barrier for normal users.

Difficulty Formula
required_bits = BaseBits + floor(recent_count / 60) Γ— 2
BaseBits = 2  β€’  BucketSize = 60 txs  β€’  BucketBits = 2
recent_count = transactions timestamped in the last 60 seconds

Normal use

At baseline load, ~4 hashes per payment. Negligible on any device.

Under attack

Each extra 60 txs/min adds 2 bits β€” 4Γ— more work per bucket.

Not a fee β€” a throttle

There is no recipient and no money collected. Honest senders always pay the baseline. Flooders pay exponentially more CPU as they raise network load β€” and each transaction they submit makes the next one harder for everyone, including themselves.

Congestion scaling

Expected hashing work per transaction at different load levels

Txs in last 60 s Required bits Expected hashes
0 – 59 normal 2 ~4
60 – 119 4 ~16
120 – 179 6 ~64
180 – 239 8 ~256
240 – 299 10 ~1,024
Anti-selfish-mining

Tip commitment

PoW is bound to the live state of both parent tips at mining time. You cannot pre-mine a stockpile of transactions and dump them later β€” if the DAG moves while you hash, your work is instantly stale.

An attacker mining against outdated tips produces parent hashes that no longer match. The node rejects the transaction; the CPU cost is wasted.

PoW Input
pow_input = txID
|| parent[0].pow_hash
|| parent[1].pow_hash
|| nonce
pow_hash = SHA3-256(pow_input)
Conflict Resolution

Probabilistic finality.

Double-spends are not instantly rejected. Competing transactions enter the DAG and race until accumulated work picks a winner β€” per UTXO, without blocks, miners, or a global coordinator.

1

Both accepted

If two transactions spend the same UTXO, both are gossiped and stored. No mempool gatekeeper decides which one "gets in."

2

Work accumulates

Each descendant adds weight: 2pow_bits per transaction in its subtree. The branch with more cumulative work wins.

3

One survives

Once weight crosses the confirmation threshold, the canonical spend is settled. The loser is pruned after a grace period for slow Tor peers.

Winner Selection
canonical_spend = argmax cumulative_weight(tx)
cumulative_weight(tx) = Ξ£ 2pow_bits over all descendants of tx
Tie-break: lower tx_id (lexicographic) wins
Confirmed when cumulative_weight β‰₯ 200
Losers retained for 960 s grace (~16 min) before deletion

No global lock

Concurrent double-spends resolve by accumulated work β€” like competing forks, but at per-UTXO granularity instead of whole-chain reorgs.

Deterministic convergence

Every honest node applies the same argmax rule. No coordinator, no validator set β€” all nodes converge on identical ledger state.

Fast in practice

At base difficulty (2 bits), reaching 200 weight means ~200 descendants at ~4 hashes each. Under normal load, finality settles in seconds.

Cryptography

Post-quantum ready.

Sikka relies entirely on the ML-DSA-87 (Dilithium) signature scheme. We do not use any classical elliptic curves, ensuring maximum security against future quantum threats.

  • No classical fallbacks Pure post-quantum cryptography.
  • Deterministic sync State verification is fully deterministic.
Transaction Spec
txid = SHA3-256(version || parents || inputs || outputs || ts)
pow_hash = SHA3-256(txid || pow_nonce)
witness = ML-DSA-87 signature(s)
1
2
...
16

Up to 16 wallets

Collaborative Tx Building

Smart Wallets

Native n-of-n multisig.

In Sikka, standard wallets are inherently n-of-n, and multisig is elegantly abstracted as an m-of-n wallet. There are no complicated, risky smart contracts required.

Because of this simple yet powerful abstraction, any single transaction can be collaboratively built and signed by up to 16 different wallets together. This dramatically simplifies complex multi-party flows and institutional custody.

Networking

Privacy and interoperability.

Tor-Native

Privacy is built into networking from the start. Nodes seamlessly advertise onion addresses, communicate privately, and support managed Tor integration to expose privacy-friendly peer connectivity globally.

HTTP Federation

Sikka nodes expose a clean HTTP API with CORS support. This makes it incredibly easy to federate networks, build lightweight web clients, and integrate directly with existing web applications.

Tokenomics

Every SIKKA goes to the network.

A fixed genesis supply with no inflation, no premine, and no team allocation. 100% of all SIKKA is distributed to node operators who keep the DAG alive.

19,960,907
Fixed Max Supply

Pre-issued entirely in genesis. The cap encodes 19960907 β€” no emission schedule, no mining rewards, no hidden minting.

100% To Operators

The entire supply flows to people running nodes. No VC slice, no foundation treasury β€” decentralization by design.

Units

  • SIKKA β€” singular coin
  • SIKKE β€” plural
  • CHILLAR β€” smallest unit  1 SIKKA = 1010 chillar
Run a node β†’ earn your share of the network.
Try before you run

Get SIKKA and test the network

A few of our volunteers operate community faucets so anyone can receive a small amount of SIKKA, create a wallet, and send a real transaction across the DAG β€” no node required to start.

Join our Discord to claim a few SIKKAs every 6 hours and experience feeless, parallel transfers firsthand.

Operator Guide

Run a Sikka Node

A tiny ~17 MB static binary containing the wallet, explorer, full DAG engine, and managed Tor. Everything you need, zero configuration required.

Docker Quick Start
docker run -d --restart unless-stopped -p 8080:8080 besoeasy/sikka:latest

Then open http://localhost:8080 in your browser.