Skip to content

February 23 ‐ March 8

umwelt edited this page Feb 23, 2026 · 1 revision

February 23 ‐ March 8

Weekly Work Plan

1. iOS & Android Store Submission

Objective: Submit and publish mobile apps to Apple App Store and Google Play Store for review and verification.

  • Generate and assign all required store assets (icons, screenshots, feature graphics, promotional text).
  • Prepare App Store Connect listing (description, keywords, privacy policy, support URL).
  • Prepare Google Play Console listing (store listing, content rating questionnaire, data safety form).
  • Build signed release candidates for both platforms.
  • Submit iOS build for App Store Review.
  • Submit Android build for Google Play Review.
  • Monitor review status and respond to any rejection feedback immediately.
  • Target: verification and approval on both platforms.

Deliverable: Sovereign Network app officially submitted and under review on both iOS and Android stores, with all assets and metadata in place.

2. SOV Token Distribution Testing

Objective: Validate that users can send and receive SOV tokens reliably across the network.

  • End-to-end test of SOV send/receive between multiple user wallets.
  • Verify balance updates, transaction confirmations, and history accuracy.
  • Stress test with concurrent transfers across different nodes.
  • Validate edge cases: insufficient balance, duplicate sends, network interruption mid-transfer.
  • Confirm notification and receipt flow on both sender and receiver side.

Deliverable: SOV token distribution fully tested and stable for internal user-to-user transfers.

3. CBE Token – Testnet Launch & Overlay Transaction Test

Objective: Launch CBE token on testnet and validate overlay transaction layer.

  • Deploy CBE token contract on testnet environment.
  • Execute overlay transaction tests (CBE transfers across nodes).
  • Validate cross-token interaction between SOV and CBE where applicable.
  • Confirm token registry, supply invariants, and accounting integrity on testnet.
  • Debug and resolve any inconsistencies found during testing.
  • Document testnet results and known issues.

Deliverable: CBE token live on testnet with overlay transactions tested and debugged.

4. Fiat On-Ramp Mechanism

Objective: Enable users to purchase CBE tokens using fiat currency.

  • Integrate fiat on-ramp provider (payment gateway / third-party service).
  • Implement purchase flow in mobile app (amount selection → payment → token delivery).
  • Test end-to-end: fiat payment → CBE credit to user wallet.
  • Debug and stabilize the full on-ramp pipeline.
  • Handle error states: failed payments, partial transactions, refund logic.
  • Validate compliance and KYC requirements if applicable.

Deliverable: Users can buy CBE tokens with fiat currency through a stable, tested on-ramp mechanism.

5. CBE Contract Deployment On-Chain

Objective: Deploy the CBE smart contract to the production chain.

  • Finalize contract code and complete audit review.
  • Prepare deployment scripts and parameters (supply cap, treasury allocation, permissions).
  • Deploy CBE contract on-chain.
  • Verify contract state, initial supply, and access controls post-deployment.
  • Confirm token is indexed and visible in explorer / registry.

Deliverable: CBE contract deployed on-chain with verified state and supply integrity.

6. Validator Bootstrap & Node Release

Objective: Prepare validators for network bootstrap and release participating node software to the community.

  • Confirm all validators are configured and ready for bootstrap.
  • Finalize participating node release build.
  • Write and publish setup instructions for community node operators.
  • Release node software package with documentation.
  • Onboard initial community participants and provide support channel.

Deliverable: Validators bootstrapped, participating node software released, and community instructions published.

7. Consensus, Backup & Disaster Recovery Testing

Objective: Validate consensus mechanism resilience, backup procedures, and emergency controls.

  • Run consensus test across all active validators and nodes.
  • Test automated backup and restore procedures.
  • Simulate disaster recovery scenarios (node failure, data corruption, network partition).
  • Test emergency pause mechanism for system, nodes, and tokens.
  • Validate that paused state is recoverable and resumable without data loss.
  • Document all recovery procedures and emergency playbooks.

Deliverable: Consensus validated, backup/recovery tested, and emergency pause mechanism confirmed operational.

Weekly Success Criteria

  • iOS and Android apps submitted to stores and under review.
  • SOV token send/receive tested and stable across users.
  • CBE token launched on testnet with overlay transactions verified.
  • Fiat on-ramp functional and debugged for CBE purchases.
  • CBE contract deployed on-chain with verified integrity.
  • Validators bootstrapped and community node release published.
  • Consensus, backup, disaster recovery, and emergency pause all tested and documented.

Clone this wiki locally