CloudService (OP)
Newbie
Activity: 5
Merit: 0
|
 |
May 31, 2026, 10:33:11 PM
Last edit: July 29, 2026, 08:46:15 PM by CloudService |
|
Cloud Service (CS) | Layer 1 | PoW | ZelHash (GPU) | Decentralized Cloud + AI Inference
═══════════════════════════════════════════════════════════════════
─────────────────────────────────────────────────────────────────◆ ABSTRACTCloud Service is a new Layer 1 Proof-of-Work blockchain whose founding mission is stated in its genesis block: "01/May/2026 — 94% of Global Cloud Controlled by Big Tech as Computing Demand Soars. Now It Belongs to Everyone." Cloud Service is built on the Flux/Zcash protocol codebase — not a naive Bitcoin clone. It inherits Equihash-based PoW with GPU-friendly ZelHash, Sapling shielded transactions, DigiShield + LWMA difficulty adjustment, and a tiered node infrastructure layer. On top of that base layer, Cloud Service adds OPoI (Proof of Inference) — a second, native consensus-secured market that lets staked node operators earn CS by contributing AI inference capacity, not just hash power. The network is designed to underpin a decentralized public cloud: miners secure the ledger, nodes provide compute and AI inference capacity, and the protocol funds its own ecosystem without relying on an ICO, pre-sale, or external venture capital. ─────────────────────────────────────────────────────────────────◆ TECHNICAL SPECIFICATIONS| Crypto Name | Cloud Service | | Ticker | CS | | Blockchain | Public, Layer 1 | | Consensus | Proof of Work (PoW) | | Mining Algorithm | ZelHash — Equihash(125, 4) — GPU-friendly, ASIC-resistant | | Block Time | 2 minutes | | Block Reward | 150 CS (after slow-start ramp, blocks 2–20,000) | | Halving Interval | 655,350 blocks (~2.5 years) | | Emission Schedule | 150 CS → 75 CS → 37.5 CS (permanent, no supply cap) | | Coinbase Maturity | 100 blocks | | Difficulty Adjustment | DigiShield (17-block window) + LWMA (60-block window) | | Privacy | Sapling shielded transactions (zk-SNARKs) | | OPoI (AI Inference Layer) | Native consensus feature — stake-gated inference market, active from mainnet block 100,000 | | P2P Port | 26125 (mainnet) / 26128 (testnet) | | RPC Port | 26124 (mainnet) | | Address Prefix | t1… (transparent) / csa… (shielded) | | Genesis Block | 069c0f4ff0427ee02edb625106bdf0e7fd4e28845dee020a493e9d8fd47c09c3 | | Protocol Base | Flux / Zcash codebase | | BIP44 Coin Type | 19999 | | Magic Bytes | 0xC5 0x53 0x01 0x01 |
─────────────────────────────────────────────────────────────────◆ EMISSION SCHEDULE DETAIL- Block 1: 13,020,000 CS — initial infrastructure allocation (see fund disclosure below)
- Blocks 2–10,000: Slow-start ramp (linearly increasing from ~0 to 150 CS)
- Blocks 10,001–20,000: Slow-start ramp continuation (linearly approaching 150 CS)
- Blocks 20,001–655,350: 150 CS per block
- Halving 1 (block ~675,350): 75 CS per block
- Halving 2 (block ~1,330,700): 37.5 CS per block — permanently stabilized
- No further halvings after round 2. Emission continues permanently at 37.5 CS/block with no end date.
Rationale for stable emission: The 150 CS block reward is split across miners and multiple tiers of infrastructure nodes. After two halvings the reward stabilizes at 37.5 CS so that node operators retain a predictable long-term incentive without the revenue cliff that indefinite halving creates. Natural deflation occurs through lost wallets and transaction fees. ─────────────────────────────────────────────────────────────────◆ WHAT IS DIFFERENT FROM BITCOIN / FLUX?Why not just use Bitcoin?Bitcoin's 10-minute blocks, SHA-256 ASIC dominance, and absence of a native node infrastructure layer make it unsuitable as the base layer for a decentralized cloud network. Cloud Service inherits the battle-tested Flux/Zcash protocol and makes targeted changes: - ZelHash (Equihash 125,4): GPU-optimized PoW algorithm. Keeps mining accessible to commodity hardware and distributes hash power geographically.
- 2-minute block time: Faster finality for cloud workload settlements versus Bitcoin's 10-minute and Zcash's 75-second intervals.
- Stabilized emission (no cliff after halving 2): Prevents the node-operator revenue collapse that undermines long-lived infrastructure networks.
- New genesis chain: Cloud Service is not a merge-mine or airdrop derivative. It is a standalone new chain with its own genesis block, magic bytes (0xC5 0x53), and P2P ports.
- CS-specific DNS seeds and network identity: Fully independent P2P network (seed.cscloudservice.com).
- Sapling privacy layer inherited: Shielded transactions available from genesis, providing optional privacy for compute service payments.
- Tiered node infrastructure: P2SH-secured node registration allows operators to contribute compute resources and earn a share of the block reward.
- OPoI — native AI inference market: a consensus-level layer (see dedicated section below) that lets staked operators get paid in CS for serving verifiable AI inference — no other Flux/Zcash-derived chain has this.
─────────────────────────────────────────────────────────────────◆ OPoI — PROOF OF INFERENCE (DECENTRALIZED AI COMPUTE)Alongside ZelHash PoW mining, Cloud Service nodes can earn CS by contributing AI inference capacity to the network through OPoI (Proof of Inference) — a second, independent market built directly into consensus, not a side service bolted on top. - Stake-gated providers: node operators lock CS collateral on-chain to register as an inference provider for one or more supported model tiers.
- Privacy-preserving requests: only the prompt's hash is committed on-chain — the prompt content itself is delivered off-chain, so the ledger never exposes user data.
- Redundant computation, majority consensus: requests can be answered by multiple independent providers in parallel; the network resolves the canonical result by majority agreement, discouraging lazy or dishonest answers.
- Governed model registry: supported models (dense and Mixture-of-Experts architectures) are pinned by a merkle-rooted manifest that can be extended via stake-weighted vote — adding a new model doesn't require a hard fork.
- Commit-reveal fraud challenges: any participant can challenge a suspect response by posting collateral plus a commitment hash. If the challenge is upheld, the provider's stake is slashed; if it's frivolous, the challenger's own collateral is burned instead — symmetric cost, no free griefing.
- Permissionless auditors: for verifiable (deterministic/code) tasks, a quorum of independent auditors votes PASS/FAIL on submitted work, with payment and slashing both gated by majority result.
- On-chain reputation: every provider accrues a reputation score from its history of responses, challenges, and slashes, queryable by anyone on the chain.
- Per-token payment: inference rewards are paid via coinbase proportionally to tokens generated, on top of the standard block subsidy.
- Pool-friendly: miners connect through a stratum bridge to participate — no open inbound ports or manual key custody required, the same convenience pool-mining already offers for PoW.
The result: Cloud Service doesn't just rent out storage or bandwidth like a typical decentralized cloud project — it turns idle GPU inference capacity into a verifiable, slashing-secured on-chain market, protected by the same stake + fraud-proof trust model that secures the coin itself. ─────────────────────────────────────────────────────────────────◆ FULL FUND DISCLOSURE (No Hidden Allocations)The protocol contains scheduled on-chain fund disbursements to specific addresses. These are hard-coded in the consensus layer and fully auditable in the source code. All amounts and destination addresses are public: | Fund | Amount | Block Height | Purpose | | Block 1 Allocation | 13,020,000 CS | 1 | Initial infrastructure bootstrap | | Exchange Fund | 100,000,000 CS | 100,000 | CEX listing & liquidity | | Foundation Fund | 10,000,000 CS | 101,000 | Non-profit foundation | | Swap Pool | 20,000,000 CS × 10 installments | Every 21,600 blocks from block 102,000 | DEX liquidity / ecosystem swaps | | Dev Fund | 5,000,000 CS × 100 installments | Every 21,600 blocks from block 150,000 | Core development (~8.3 years) | | Marketing Fund | 5,000,000 CS × 100 installments | Every 21,600 blocks from block 150,001 | Ecosystem growth (~8.3 years) |
These disbursements are enforced by consensus rules and verifiable by any full node.─────────────────────────────────────────────────────────────────◆ EXCHANGES (CEX & DEX)CEX (Native Coin)DEX (Wrapped Token)─────────────────────────────────────────────────────────────────◆ SOURCE CODE & OFFICIAL LINKS─────────────────────────────────────────────────────────────────◆ HOW TO PARTICIPATE — BUILD & RUN A NODEFull documentation: https://docs.cscloudservice.com─────────────────────────────────────────────────────────────────◆ MININGCloud Service uses ZelHash (Equihash 125,4) — GPU mining. ASIC miners will not work on this network. Recommended miners:- lolMiner
- MiniZ
- NVIDIA: T-Rex (check ZelHash support)
Pool mining: https://miningtothelastblock.top─────────────────────────────────────────────────────────────────◆ COMMUNITY─────────────────────────────────────────────────────────────────The Cloud Service source code is open-source and distributed under the MIT License.
All fund allocations listed above are hardcoded in consensus and publicly verifiable.
This is not financial advice. Mining and running nodes carries risk. [/list] |
