Omega v0.20.9 release

Full Changelog: 0.207...0.20.9

Omega v0.20.8 release

Full Changelog: 0.207...0.20.8

v0.20.7 Release

Blockchain synchronisation improved.
From 8 hours reduced to 2 with better package transmission.
Automatic snapshot download as a second option.

v0.20.6 Release. LWMA adjustments and enforcing.

Omega Core 0.20.6
Omega Core 0.20.6 is a mandatory network upgrade release.

Summary
Bumps the advertised network protocol to 70232.
Rejects peers below protocol 70232.
Requires masternodes participating in DKGs to use protocol 70232.
Upgrade rationale
Mainnet crossed the LWMA transition at block 3200000, and the corrective LWMA boundary intended for block 3200070 must be enforced by a distinct release. Nodes remaining on the previous 70231 release line can still appear protocol compatible while validating the old retarget behaviour.

This release creates a clean compatibility boundary for the corrected rule set.

Operator action
Upgrade all trusted nodes and miners to Omega Core 0.20.6.
Disconnect or ban peers that remain on the old release line.
Do not mix 70231 and 70232 nodes during rollout if you want to stay on the corrected chain.

v0.20.4 Release. Blockchain Hardening

SMSG layer, daemon and blockchain hardening.

Full Changelog: 0.20.3...0.20.4

Omega Core 0.20.3 Release

Omega Core 0.20.3

https://omegablockchain.net

What is Omega?

Omega is a peer-to-peer digital currency and blockchain platform launched on 2 January 2018.
It is forked from Dash Core and extends it with a number of protocol-level features including
on-chain encrypted messaging, Schnorr signatures, and an improved proof-of-work difficulty
algorithm. The network runs with 60-second block times and masternode-based governance.

What's New in 2026

The following features and improvements have been implemented this development cycle,
starting from the Dash 19.3 base:

Consensus Protocol Upgrades

• Version-gated peer disconnect — Nodes running protocol version below 70231 are
  disconnected at block 3,190,000 (10,000 blocks before the hard fork). This ensures the
  network is fully upgraded before consensus rules change at block 3,200,000. Omega 0.20.1
  advertises protocol version 70231.

• Schnorr Signatures — Full Schnorr signature consensus activated at block 3,200,000.
  Includes OP_CHECKDATASIG and OP_CHECKDATASIGVERIFY opcodes, enabling compact
  multi-party signing and cross-chain atomic swap constructions.

• LWMA Difficulty Algorithm — Zawy's LWMA (Linearly Weighted Moving Average) difficulty
  adjustment activated at block 3,200,000 with a 60-block window. Provides faster and more
  stable difficulty retargeting compared to the legacy algorithm, improving resistance to
  hash rate fluctuations.

• Increased Script Element Size — Extended script element size of 4096 bytes activated at
  block 3,200,000 via SCRIPT_ENABLE_LARGE_ELEMENTS (up from the base 520-byte limit),
  enabling more complex script constructions.

• Increased Standard Transaction Size — MAX_STANDARD_TX_SIZE raised to 400 KB.

• Legacy Fork Activations Buried — Old soft fork activation logic (BIP65, BIP66, CSV)
  buried at their historical heights, simplifying validation.

Masternode RPC Improvements

• masternode count — PoSe ban counts — The top-level object and each per-type sub-object
  (regular, hpmn) now include a pose_banned field, so you can see at a glance how many
  masternodes are currently banned without parsing masternodelist manually.

• masternodelist json — extended fields — Each entry now includes three additional fields
  after pubkeyoperator:

  Field	Type	Description
  registeredheight	number	Block height at which the ProRegTx was mined
  posebanheight	number	Block height at which the masternode was PoSe-banned (−1 if not banned)
  poserevidedheight	number	Block height at which the masternode last revived from a PoSe ban (−1 if never revived)

• Correct status ordering — Status values are now evaluated in the correct priority order:
  POSE_BANNED → WAITING_CONFIRMATION → ENABLED. Previously a banned masternode that was
  also awaiting collateral confirmation could be shown as WAITING_CONFIRMATION.

• masternode status [proTxHash] — Accepts an optional proTxHash argument. When supplied,
  returns the full status object for that masternode regardless of whether the local node is
  running in masternode mode. Useful for monitoring any masternode from a full node or wallet.

• masternode payments — count limit — The count parameter is now capped at ±1000.
  Requests above this limit return an RPC_INVALID_PARAMETER error immediately, preventing
  unbounded disk reads.

• masternode winners — count-aware projection — The forward projection (blocks after the
  chain tip) now honours the count argument. Previously it always returned exactly 20 projected
  entries regardless of the requested window.

Secure Messaging (SMSG)

On-chain encrypted peer-to-peer messaging ported from Particl, integrated directly into
the Omega consensus layer:

• SMSG Library — Full secure messaging implementation (src/smsg/) including encrypted
  message storage, key management, and P2P relay.

• TRANSACTION_SMSG_ROOM — New transaction type (type 8) for funding decentralised
  messaging rooms on-chain.

• Confidential SMSG Funding — Confidential transaction support for SMSG room funding,
  activated at block 3,144,000 on mainnet. SMSG_ROOM transactions (type 8) activate at
  block 3,200,000.

• SMSG Key Generation UI — GUI button in the Qt wallet to generate and manage SMSG keys.

• Messages Tab — Dedicated messaging tab in the Qt wallet interface.

• SMSG Blockchain Scan Performance — Replaced O(N²) LevelDB batch-write with chunked
  direct writes (sync=false, 1000 keys per flush). A full mainnet public-key scan now
  completes in seconds rather than hanging indefinitely.

• SMSG Scan Abort and Resume — The blockchain scan can be stopped mid-way via the
  Messages tab. Progress (last fully-processed block height) and all discovered public keys
  up to that point are saved immediately. The next scan resumes from where it left off.

• SMSG Scan Progress Logging — Block progress is logged every 50,000 blocks during a
  scan so the user can monitor throughput in the debug log.

SMSG Topic Channels

Topic Channels extend the SMSG module with broadcast messaging and per-topic routing,
enabling application-layer protocols such as decentralised real estate marketplaces,
classified listings, and contract signalling — all running on the Omega P2P network
without any centralised server.

Broadcast Channels (Shared-Key)

Each topic has a deterministic shared keypair derived from the topic string. When a
node subscribes to a topic, the shared key is imported into its SMSG keystore. Messages
sent to a topic with an empty recipient address are encrypted to this shared key, so
all subscribers can decrypt and read them — similar to the Trollbox but per-topic.

This enables public listings: a seller publishes a property to omega.listings.uk and
every subscribed node can read it without knowing the seller in advance.

FNV-1a Cleartext Routing

Each topic-channel message (version 4) carries a 4-byte FNV-1a hash of the full topic
string in the cleartext header (nonce[0..3]). Nodes compare this hash against their
subscribed topic hashes and drop non-matching messages without decryption, minimising
storage and CPU overhead.

This is per-topic granular: subscribing to omega.listings.uk does not force the node
to store omega.listings.japan.

Message Referencing

Topic messages carry an optional 20-byte parent_msgid field. This enables:

• Listing updates — publish a new message referencing the original listing ID
• Listing withdrawal — send a cancellation referencing the listing
• Reply threads — link negotiations back to a specific listing

Extended Local Retention

Each topic message includes a retention_days field (0–365). Subscribing nodes honour
this value for topic index persistence — a listing with retention_days=30 remains in
the local index for 30 days even after the raw SMSG bucket expires at the default TTL.

Topic Naming

Topics follow the format omega.<domain>[.<subdomain>]:

Topic	Purpose
omega.listings	General classified listings
omega.listings.uk	UK property listings
omega.listings.uk.london	London-specific listings
omega.chat	Public chat channels
omega.contract	Contract signalling
omega.match	Matching / discovery

Rules: lowercase ASCII [a-z0-9.], starts with omega., max 64 characters.

RPC Commands

# Subscribe to a topic (imports the topic's shared key)
omega-cli smsgsubscribe "omega.listings.uk"

# Unsubscribe
omega-cli smsgunsubscribe "omega.listings.uk"

# List current subscriptions
omega-cli smsglisttopics

# Broadcast a listing (empty address_to = broadcast to all subscribers)
omega-cli smsgsend "oMyAddress" "" '{"title":"3BR flat","price":250000}' \
    false 0 false false false "omega.listings.uk" "" 30

# Update an existing listing (reference the original msgid)
omega-cli smsgsend "oMyAddress" "" '{"price":240000}' \
    false 0 false false false "omega.listings.uk" "a1b2c3...original_msgid" 30

# Retrieve the newest 20 listings for a topic
omega-cli smsggetmessages "omega.listings.uk" 20

Wire Format (version 4)

Field	Location	Description
version[0]	Header byte 4	4 — topic channel message
version[1]	Header byte 5	0 — free topic message
nonce[0..3]	Header bytes 96–99	FNV-1a hash of topic string (cleartext routing)
topic_len	Encrypted payload at PL_HDR+0	1 byte, topic string length
topic	Encrypted payload at PL_HDR+1	ASCII topic string
parent_msgid	After topic	20 bytes, zero if no parent
retention_days	After parent_msgid	2 bytes (uint16), suggested local retention

Old nodes (version < 4 awareness): Store() accepts the message, Decrypt() returns
SMSG_UNKNOWN_VERSION — old nodes relay topic messages transparently. No hard fork required.

Wallet & GUI

• Masternode Wizard — Step-by-step masternode setup wizard added to the Qt GUI.
  If an error occurs during registration, the wizard displays a structured error
  code with an explanation and suggested fix. See the error reference below.

• Governance Tab — Full governance interface in the Qt wallet. Browse proposals,
  vote Yes/No/Abstain with all your masternodes in one click, and create new budget
  proposals directly from the GUI. Supports wallets controlling multiple masternodes —
  each vote is cast with every masternode whose voting key is held in the wallet.
  See the Governance Guide below.

• Update Notification — The Qt walle...

Omega Core 0.20.2 Release

Omega Core 0.20.2

https://omegablockchain.net

What is Omega?

Omega is a peer-to-peer digital currency and blockchain platform launched on 2 January 2018.
It is forked from Dash Core and extends it with a number of protocol-level features including
on-chain encrypted messaging, Schnorr signatures, and an improved proof-of-work difficulty
algorithm. The network runs with 60-second block times and masternode-based governance.

Consensus Protocol Upgrades

• Version-gated peer disconnect — Nodes running protocol version below 70231 are
  disconnected at block 3,190,000 (10,000 blocks before the hard fork). This ensures the
  network is fully upgraded before consensus rules change at block 3,200,000. Omega 0.20.1
  advertises protocol version 70231.

• Schnorr Signatures — Full Schnorr signature consensus activated at block 3,200,000.
  Includes OP_CHECKDATASIG and OP_CHECKDATASIGVERIFY opcodes, enabling compact
  multi-party signing and cross-chain atomic swap constructions.

• LWMA Difficulty Algorithm — Zawy's LWMA (Linearly Weighted Moving Average) difficulty
  adjustment activated at block 3,200,000 with a 60-block window. Provides faster and more
  stable difficulty retargeting compared to the legacy algorithm, improving resistance to
  hash rate fluctuations.

• Increased Script Element Size — Extended script element size of 4096 bytes activated at
  block 3,200,000 via SCRIPT_ENABLE_LARGE_ELEMENTS (up from the base 520-byte limit),
  enabling more complex script constructions.

• Increased Standard Transaction Size — MAX_STANDARD_TX_SIZE raised to 400 KB.

• Legacy Fork Activations Buried — Old soft fork activation logic (BIP65, BIP66, CSV)
  buried at their historical heights, simplifying validation.

Masternode RPC Improvements

• masternode count — PoSe ban counts — The top-level object and each per-type sub-object
  (regular, hpmn) now include a pose_banned field, so you can see at a glance how many
  masternodes are currently banned without parsing masternodelist manually.

• masternodelist json — extended fields — Each entry now includes three additional fields
  after pubkeyoperator:

  Field	Type	Description
  registeredheight	number	Block height at which the ProRegTx was mined
  posebanheight	number	Block height at which the masternode was PoSe-banned (−1 if not banned)
  poserevidedheight	number	Block height at which the masternode last revived from a PoSe ban (−1 if never revived)

• Correct status ordering — Status values are now evaluated in the correct priority order:
  POSE_BANNED → WAITING_CONFIRMATION → ENABLED. Previously a banned masternode that was
  also awaiting collateral confirmation could be shown as WAITING_CONFIRMATION.

• masternode status [proTxHash] — Accepts an optional proTxHash argument. When supplied,
  returns the full status object for that masternode regardless of whether the local node is
  running in masternode mode. Useful for monitoring any masternode from a full node or wallet.

• masternode payments — count limit — The count parameter is now capped at ±1000.
  Requests above this limit return an RPC_INVALID_PARAMETER error immediately, preventing
  unbounded disk reads.

• masternode winners — count-aware projection — The forward projection (blocks after the
  chain tip) now honours the count argument. Previously it always returned exactly 20 projected
  entries regardless of the requested window.

Secure Messaging (SMSG)

On-chain encrypted peer-to-peer messaging ported from Particl, integrated directly into
the Omega consensus layer:

• SMSG Library — Full secure messaging implementation (src/smsg/) including encrypted
  message storage, key management, and P2P relay.

• TRANSACTION_SMSG_ROOM — New transaction type (type 8) for funding decentralised
  messaging rooms on-chain.

• Confidential SMSG Funding — Confidential transaction support for SMSG room funding,
  activated at block 3,144,000 on mainnet. SMSG_ROOM transactions (type 8) activate at
  block 3,200,000.

• SMSG Key Generation UI — GUI button in the Qt wallet to generate and manage SMSG keys.

• Messages Tab — Dedicated messaging tab in the Qt wallet interface.

• SMSG Blockchain Scan Performance — Replaced O(N²) LevelDB batch-write with chunked
  direct writes (sync=false, 1000 keys per flush). A full mainnet public-key scan now
  completes in seconds rather than hanging indefinitely.

• SMSG Scan Abort and Resume — The blockchain scan can be stopped mid-way via the
  Messages tab. Progress (last fully-processed block height) and all discovered public keys
  up to that point are saved immediately. The next scan resumes from where it left off.

• SMSG Scan Progress Logging — Block progress is logged every 50,000 blocks during a
  scan so the user can monitor throughput in the debug log.

SMSG Topic Channels

Topic Channels extend the SMSG module with broadcast messaging and per-topic routing,
enabling application-layer protocols such as decentralised real estate marketplaces,
classified listings, and contract signalling — all running on the Omega P2P network
without any centralised server.

Broadcast Channels (Shared-Key)

Each topic has a deterministic shared keypair derived from the topic string. When a
node subscribes to a topic, the shared key is imported into its SMSG keystore. Messages
sent to a topic with an empty recipient address are encrypted to this shared key, so
all subscribers can decrypt and read them — similar to the Trollbox but per-topic.

This enables public listings: a seller publishes a property to omega.listings.uk and
every subscribed node can read it without knowing the seller in advance.

FNV-1a Cleartext Routing

Each topic-channel message (version 4) carries a 4-byte FNV-1a hash of the full topic
string in the cleartext header (nonce[0..3]). Nodes compare this hash against their
subscribed topic hashes and drop non-matching messages without decryption, minimising
storage and CPU overhead.

This is per-topic granular: subscribing to omega.listings.uk does not force the node
to store omega.listings.japan.

Message Referencing

Topic messages carry an optional 20-byte parent_msgid field. This enables:

• Listing updates — publish a new message referencing the original listing ID
• Listing withdrawal — send a cancellation referencing the listing
• Reply threads — link negotiations back to a specific listing

Extended Local Retention

Each topic message includes a retention_days field (0–365). Subscribing nodes honour
this value for topic index persistence — a listing with retention_days=30 remains in
the local index for 30 days even after the raw SMSG bucket expires at the default TTL.

Topic Naming

Topics follow the format omega.<domain>[.<subdomain>]:

Topic	Purpose
omega.listings	General classified listings
omega.listings.uk	UK property listings
omega.listings.uk.london	London-specific listings
omega.chat	Public chat channels
omega.contract	Contract signalling
omega.match	Matching / discovery

Rules: lowercase ASCII [a-z0-9.], starts with omega., max 64 characters.

RPC Commands

# Subscribe to a topic (imports the topic's shared key)
omega-cli smsgsubscribe "omega.listings.uk"

# Unsubscribe
omega-cli smsgunsubscribe "omega.listings.uk"

# List current subscriptions
omega-cli smsglisttopics

# Broadcast a listing (empty address_to = broadcast to all subscribers)
omega-cli smsgsend "oMyAddress" "" '{"title":"3BR flat","price":250000}' \
    false 0 false false false "omega.listings.uk" "" 30

# Update an existing listing (reference the original msgid)
omega-cli smsgsend "oMyAddress" "" '{"price":240000}' \
    false 0 false false false "omega.listings.uk" "a1b2c3...original_msgid" 30

# Retrieve the newest 20 listings for a topic
omega-cli smsggetmessages "omega.listings.uk" 20

Wire Format (version 4)

Field	Location	Description
version[0]	Header byte 4	4 — topic channel message
version[1]	Header byte 5	0 — free topic message
nonce[0..3]	Header bytes 96–99	FNV-1a hash of topic string (cleartext routing)
topic_len	Encrypted payload at PL_HDR+0	1 byte, topic string length
topic	Encrypted payload at PL_HDR+1	ASCII topic string
parent_msgid	After topic	20 bytes, zero if no parent
retention_days	After parent_msgid	2 bytes (uint16), suggested local retention

Old nodes (version < 4 awareness): Store() accepts the message, Decrypt() returns
SMSG_UNKNOWN_VERSION — old nodes relay topic messages transparently. No hard fork required.

Wallet & GUI

• Masternode Wizard — Step-by-step masternode setup wizard added to the Qt GUI.
  If an error occurs during registration, the wizard displays a structured error
  code with an explanation and suggested fix. See the error reference below.

• Governance Tab — Full governance interface in the Qt wallet. Browse proposals,
  vote Yes/No/Abstain with all your masternodes in one click, and create new budget
  proposals directly from the GUI. Supports wallets controlling multiple masternodes —
  each vote is cast with every masternode whose voting key is held in the wallet.
  See the Governance Guide below.

• Update Notification — The Qt wallet checks the GitHub Releases API once after the
  blockchain is fully synchronised. If a newer release is available, a clickable status bar
  label appears with a direct...

Omega v0.20.1 release

Omega Core 0.20.1

https://omegablockchain.net

What is Omega?

Omega is a peer-to-peer digital currency and blockchain platform launched on 2 January 2018.
It is forked from Dash Core and extends it with a number of protocol-level features including
on-chain encrypted messaging, Schnorr signatures, and an improved proof-of-work difficulty
algorithm. The network runs with 60-second block times and masternode-based governance.

Blockchain Specification

Network Ports

Network	P2P	RPC	Platform P2P	Platform HTTP
Mainnet	7777	7778	26656	443
Testnet	17777	17778	22000	22001
Devnet	17577	17578	22100	22101
Regtest	17677	17678	22200	22201

Block Parameters

Parameter	Mainnet	Testnet
Block time	60 seconds	60 seconds
Difficulty retarget window	600 seconds	86400 seconds
Miner confirmation window	2016 blocks	1440 blocks
Rule change activation threshold	1916 (95%)	1080 (75%)
Coinbase maturity	100 blocks	100 blocks
Maximum block size	2 MB (DIP0001)	2 MB
Maximum standard tx size	400 KB	400 KB

Addresses

Type	Mainnet prefix	Testnet prefix
Pay-to-pubkey-hash	o	y
Pay-to-script-hash	7	8 or 9
Genesis block	2 January 2018
Seed node	seed.omegablockchain.net

Block Reward Schedule (Mainnet)

The block reward follows a stepped schedule for early blocks, then a
difficulty-proportional formula, with a periodic halving applied on top.

Block range	Base reward
0 (genesis)	580,000 OMEGA (premine, ~0.5% of supply cap)
1 – 999	10 OMEGA
1,000 – 9,999	15 OMEGA
10,000 – 19,999	30 OMEGA
20,000 – 29,999	50 OMEGA
30,000 – 49,999	75 OMEGA
50,000 – 59,999	100 OMEGA
60,000 – 74,999	135 OMEGA
75,000 – 94,999	170 OMEGA
95,000 – 124,999	195 OMEGA
125,000 – 144,999	81 OMEGA
145,000 – 174,999	41 OMEGA
175,000 – 199,999	21 OMEGA
200,000+	Difficulty-adjusted: 2,222,222 / ((diff + 2600) / 9)², clamped to 5–21 OMEGA

Periodic decline: Every 498,855 blocks (~1 year), the subsidy is reduced by
approximately 30.3% (nSubsidy -= nSubsidy / 3.3). There is no fixed supply cap —
the difficulty-adjusted reward (5–21 OMEGA) continues indefinitely, declining with
each halving interval. Circulating supply exceeds 33 million OMEGA.

Block Reward Distribution (Heights > 66,000)

Recipient	Share of total subsidy
Miners	63%
Masternodes	27%
Governance budget	10%

Early network (historical):

Height range	Masternode share of miner+MN pool
0 – 33,000	80%
33,001 – 66,000	50%
66,001+	30%

Masternode Collateral

Type	Collateral	Governance voting weight	Active from
Regular	1,000 OMEGA	1	genesis
High Performance	10,000 OMEGA	10	block 3,200,000

Collateral must reach 15 confirmations before the masternode is accepted into
the valid set. InstantSend locks require 6 confirmations and are kept for
24 blocks.

Governance & Budget

Parameter	Mainnet value
Superblock cycle	35,000 blocks (~30 days at 74.1s avg)
Superblock maturity window	1,662 blocks (~3 days before superblock)
Budget start block	115,000
Proposal fee (current)	1 OMEGA (non-refundable)
Proposal fee (pre-DIP0024)	5 OMEGA (non-refundable)
Collateral confirmations required	6
Minimum quorum	10 masternodes
Passing threshold	(Yes − No) ≥ total_masternodes / 10
Governance filter elements	20,000

Superblock Budget Projection (as of block 3,149,180)

	Current	After next reduction
Block reward	2.16643258 OMEGA	~1.5097 OMEGA
Budget per block (10%)	0.21664 OMEGA	~0.15097 OMEGA
Pool per superblock cycle	~7,582 OMEGA	~5,284 OMEGA
Reduction	—	−30.3%

Next reward reduction: block 3,491,985 (~342,805 blocks away, estimated ~13 January 2027)

Reduction interval: 498,855 blocks (~30.3% decrease per interval, applied as reward -= reward / 3.3).

Transaction Fees

Parameter	Value
Min relay transaction fee	1,000 sat/kB
Dust relay fee	3,000 sat/kB
Default wallet tx fee	0 (uses fee estimator)
Max standard tx sigops	4,000

Consensus Activation Heights (Mainnet)

Feature	Activation height
DIP0001 (2 MB blocks)	782,208
DIP0003 (deterministic masternodes)	2,250,000
DIP0003 enforcement	2,300,000
DIP0008 (ChainLocks)	2,350,000
Confidential SMSG funding	3,144,000
Peer enforcement (protocol 70231 required)	3,190,000
Schnorr signatures	3,200,000
Large script elements (4096 bytes)	3,200,000
SMSG_ROOM transactions (type 8)	3,200,000
LWMA difficulty algorithm	3,200,000
High Performance masternodes	3,200,000

What's New in 2025-2026

The following features and improvements have been implemented this development cycle,
starting from the Dash 19.3 base:

Consensus Protocol Upgrades

• Version-gated peer disconnect — Nodes running protocol version below 70231 are
  disconnected at block 3,190,000 (10,000 blocks before the hard fork). This ensures the
  network is fully upgraded before consensus rules change at block 3,200,000. Omega 0.20.1
  advertises protocol version 70231.

• Schnorr Signatures — Full Schnorr signature consensus activated at block 3,200,000.
  Includes OP_CHECKDATASIG and OP_CHECKDATASIGVERIFY opcodes, enabling compact
  multi-party signing and cross-chain atomic swap constructions.

• LWMA Difficulty Algorithm — Zawy's LWMA (Linearly Weighted Moving Average) difficulty
  adjustment activated at block 3,200,000 with a 60-block window. Provides faster and more
  stable difficulty retargeting compared to the legacy algorithm, improving resistance to
  hash rate fluctuations.

• Increased Script Element Size — Extended script element size of 4096 bytes activated at
  block 3,200,000 via SCRIPT_ENABLE_LARGE_ELEMENTS (up from the base 520-byte limit),
  enabling more complex script constructions.

• Increased Standard Transaction Size — MAX_STANDARD_TX_SIZE raised to 400 KB.

• Legacy Fork Activations Buried — Old soft fork activation logic (BIP65, BIP66, CSV)
  buried at their historical heights, simplifying validation.

Secure Messaging (SMSG)

On-chain encrypted peer-to-peer messaging ported from Particl, integrated directly into
the Omega consensus layer:

• SMSG Library — Full secure messaging implementation (src/smsg/) including encrypted
  message storage, key management, and P2P relay.

• TRANSACTION_SMSG_ROOM — New transaction type (type 8) for funding decentralised
  messaging rooms on-chain.

• Confidential SMSG Funding — Confidential transaction support for SMSG room funding,
  activated at block 3,144,000 on mainnet. SMSG_ROOM transactions (type 8) activate at
  block 3,200,000.

• SMSG Key Generation UI — GUI button in the Qt wallet to generate and manage SMSG keys.

• Messages Tab — Dedicated messaging tab in the Qt wallet interface.

• SMSG Blockchain Scan Performance — Replaced O(N²) LevelDB batch-write with chunked
  direct writes (sync=false, 1000 keys per flush). A full mainnet public-key scan now
  completes in seconds rather than hanging indefinitely.

• SMSG Scan Abort and Resume — The blockchain scan can be stopped mid-way via the
  Messages tab. Progress (last fully-processed block height) and all discovered public keys
  up to that point ...

Omega Core 0.20.0 Release

Omega Core 0.20

https://omegablockchain.net

What is Omega?

Omega is a peer-to-peer digital currency and blockchain platform launched on 2 January 2018.
It is forked from Dash Core and extends it with a number of protocol-level features including
on-chain encrypted messaging, Schnorr signatures, and an improved proof-of-work difficulty
algorithm. The network runs with 60-second block times and masternode-based governance.

• Port: 7777 (mainnet), 17778 (testnet)
• Block time: 60 seconds
• Addresses start with: o
• Script addresses start with: 7
• Genesis block: 2 January 2018
• Seed node: seed.omegablockchain.net

What's New in 2025-2026

The following features and improvements have been implemented this development cycle,
starting from the Dash 19.3 base:

Consensus Protocol Upgrades

• Schnorr Signatures — Full Schnorr signature consensus activated at block 3,205,000.
  Includes OP_CHECKDATASIG and OP_CHECKDATASIGVERIFY opcodes, enabling compact
  multi-party signing and cross-chain atomic swap constructions.

• LWMA Difficulty Algorithm — Zawy's LWMA (Linearly Weighted Moving Average) difficulty
  adjustment activated at block 3,220,000 with a 60-block window. Provides faster and more
  stable difficulty retargeting compared to the legacy algorithm, improving resistance to
  hash rate fluctuations.

• Increased Script Element Size — MAX_SCRIPT_ELEMENT_SIZE raised from 520 to 4096 bytes,
  enabling more complex script constructions.

• Increased Standard Transaction Size — MAX_STANDARD_TX_SIZE raised to 400 KB.

• Legacy Fork Activations Buried — Old soft fork activation logic (BIP65, BIP66, CSV)
  buried at their historical heights, simplifying validation.

Secure Messaging (SMSG)

On-chain encrypted peer-to-peer messaging ported from Particl, integrated directly into
the Omega consensus layer:

• SMSG Library — Full secure messaging implementation (src/smsg/) including encrypted
  message storage, key management, and P2P relay.

• TRANSACTION_SMSG_ROOM — New transaction type (type 8) for funding decentralised
  messaging rooms on-chain.

• Confidential SMSG Funding — Confidential transaction support for SMSG room funding,
  activated at block 3,205,000 on mainnet.

• SMSG Key Generation UI — GUI button in the Qt wallet to generate and manage SMSG keys.

• Messages Tab — Dedicated messaging tab in the Qt wallet interface.

Wallet & GUI

• Masternode Wizard — Step-by-step masternode setup wizard added to the Qt GUI.

• Rebranding — Full Omega branding applied throughout: splash screen, colour scheme,
  icons, window titles, and copyright notices updated.

• Qt Upgrade — Qt upgraded from 5.12.11 to 5.15.18 for improved compatibility and
  security.

Build System

• Guix Reproducible Builds — Full GNU Guix reproducible build support upgraded and
  working for Linux (x86_64, aarch64) and Windows (x86_64-w64-mingw32).

• Dependency Cache Persistence — Built dependency cache now stored at
  ~/.cache/guix-base-cache by default, surviving guix-clean between builds.

• Python 3.12 Compatibility — Build scripts updated to support Python 3.12.

• Seeds Updated — DNS seed list refreshed.

Building

Linux / macOS

./autogen.sh
./configure
make -j$(nproc)

Reproducible builds via GNU Guix

# All platforms (Linux x86_64, Linux aarch64, Windows x86_64)
./contrib/guix/guix-build

# Single platform
HOSTS="x86_64-w64-mingw32" ./contrib/guix/guix-build
HOSTS="x86_64-linux-gnu" ./contrib/guix/guix-build
HOSTS="aarch64-linux-gnu" ./contrib/guix/guix-build

Built dependency tarballs are cached at ~/.cache/guix-base-cache and source tarballs
at ~/.cache/guix-sources, so they survive guix-clean.

Dependencies

cd depends
make HOST=x86_64-linux-gnu -j$(nproc)

License

Omega Core is released under the terms of the MIT license. See COPYING for more
information or see https://opensource.org/licenses/MIT.

Omega Core is derived from Dash Core, which is derived from Bitcoin Core.

Development Process

The master branch is the stable release branch. Development work is done in feature branches
and merged when stable.

Issues and contributions: https://github.com/OmegaBlockchain/omega/issues

v0.19.4

DIP3 postponed to block height 2,250,000
DIP3 enforcement to 2,300,000
DIP8 postponed to block height 2,350,000