The Blockchain Infrastructure Layer for the Orbital Economy.
Purpose-built for satellite identity, spectrum governance, and Proof-of-Orbit consensus.
Orbital SDK is DSEL's proprietary fork of Cosmos SDK — audited across 847,000 lines of source code and upgraded with orbital-native primitives that the vanilla Cosmos ecosystem cannot provide.
Built for the $130B satellite economy, Orbital SDK introduces cryptographic satellite identity, GNSS-based validator rights, spectrum tokenization, and governance-grade orbital slot management — all on a sovereign IBC-compatible chain.
Orbital SDK ships four production-grade modules that extend Cosmos SDK with capabilities native to the satellite economy. Each module is independently upgradeable via governance.
The world's first consensus mechanism where validators earn block rights by cryptographically proving their satellite's real-time GNSS orbital position. PoO replaces stake-weight alone with verifiable orbital attestation, enabling space-based validator infrastructure with built-in fraud deterrence.
A sovereign identity layer for orbital assets. Every registered satellite receives a deterministic on-chain address derived from NORAD ID, launch epoch, and operator key. The module manages the full satellite lifecycle from pre-launch registration through deorbitation.
Tokenizes radio frequency spectrum allocations as fungible on-chain assets. Bandwidth tokens are CW20-compatible, represent verified ITU-registered spectrum capacity, and can be atomically traded on decentralized markets — bringing transparency and liquidity to a $7.4B/year dispute-ridden market.
Represents geostationary and non-geostationary orbital slots as NFTs (USATS standard). Governs the lifecycle of orbital position rights through on-chain governance proposals, enabling transparent slot allocation, trading, and retirement across five orbital classes.
Before extending Cosmos SDK, DSEL's engineering team conducted a rigorous line-by-line review of the upstream codebase, identifying and remediating critical vulnerabilities that remain unpatched in standard distributions.
Identified a race condition in CometBFT's validator set update logic during epoch transitions. Under high validator churn, concurrent goroutines accessing the proposer priority map without proper mutex locking could cause non-deterministic block production and chain halt.
The default BIP-39 mnemonic generation in Cosmos SDK's keyring used Go's crypto/rand correctly, but the BIP-44 HD derivation path lacked domain separation for satellite-class keys, creating potential cross-context key reuse vectors in multi-tenant deployments.
IBC channel handshake timeout parameters were configurable by relayers without chain-side validation bounds. A malicious relayer could set artificially short timeouts on bandwidth token transfers, causing forced channel closure and temporary asset lockup.
Under burst transaction loads (>800 TPS), the CometBFT mempool's flush-on-commit path serialised all pending transaction re-checks synchronously, introducing 400–900ms latency spikes between blocks and degrading user-facing finality times significantly.
Cosmos SDK governance module did not enforce strict proposal ID monotonicity checks across chain upgrades. A coordinated validator set could replay a previously-passed proposal with a recycled ID post-upgrade, potentially re-executing already-enacted parameter changes.
How Orbital SDK compares to vanilla Cosmos SDK and Ethereum L2 rollups across the capabilities that matter for satellite and spectrum infrastructure.
| Feature | ⬡ Orbital SDK (DSEL) | Cosmos SDK (vanilla) | Ethereum L2 |
|---|---|---|---|
| Consensus mechanism | Proof-of-Orbit (PoO) | CometBFT PoS | Optimistic / ZK Rollup |
| Block time | ~2s (orbital-tuned) | ~5–7s (default) | ~2s (inherits L1 finality) |
| Finality | Instant (BFT) | Instant (BFT) | 7-day challenge window |
| Satellite identity primitive | ✓ Native (x/satellite) | ✗ Not available | ✗ Not available |
| GNSS proof support | ✓ Built-in (x/poo) | ✗ Not available | ✗ Not available |
| Orbital slot NFTs | ✓ USATS standard (x/orbital) | ✗ Not available | ⚠ Generic ERC-721 only |
| Bandwidth tokenization | ✓ CW20 spectrum tokens | ✗ Not available | ⚠ Custom contracts only |
| PQC readiness | ✓ Dilithium shim included | ✗ ECDSA only | ✗ ECDSA / BLS only |
| IBC support | ✓ Full IBC v2 + hardened | ✓ IBC v2 | ✗ Not native |
| CosmWasm support | ✓ CosmWasm 1.5 | ✓ CosmWasm 1.x | ✗ EVM only |
| PoO fraud slashing | ✓ Automatic on-chain | ✗ Not applicable | ✗ Not applicable |
| Spectrum governance | ✓ On-chain ITU coordination | ✗ Generic params only | ⚠ Off-chain multisig |
| License | Apache 2.0 + Proprietary ext. | Apache 2.0 | MIT / LGPL |
| Patent protection | ✓ UK Patent filed (15 claims) | ✗ None | ✗ None applicable |
| Satellite / spectrum fit | ✓ Purpose-built | ✗ Generic L1 | ✗ Generic L2 |
Orbital SDK ships with the dseld binary — a single executable to initialise, manage, and query the dsel-1 chain. Full module documentation at dsel.ae.
Orbital SDK embodies novel inventions in distributed consensus, satellite cryptography, and orbital economics that are protected by intellectual property filings in the United Kingdom and internationally. Organisations deploying Orbital SDK in commercial satellite operations should review the licensing terms prior to deployment.
The Proof-of-Orbit (PoO) consensus mechanism, USATS orbital slot NFT standard, x/satellite address extension, x/bandwidth spectrum token protocol, and x/orbital governance module are subject to patent protection and proprietary trade secret claims. Unauthorised replication, reverse-engineering, or commercialisation of these components without a valid DSEL licence is prohibited. This notice does not constitute a warranty of non-infringement for upstream Cosmos SDK components. All trade marks referenced herein remain the property of their respective owners. DSEL Ltd is incorporated in the Abu Dhabi Global Market (ADGM), Abu Dhabi, United Arab Emirates.