Skip to content

February 9 ‐ 20

umwelt edited this page Feb 16, 2026 · 1 revision

Weekly Work Plan

1. Service Access: Node → AI Chatbot

Objective: Allow service access nodes to connect and interact with the AI chatbot.

  • Define authentication model between node and chatbot service.
  • Implement secure API layer (token-based or key-based auth).
  • Map node identity to wallet_id / DID resolution.
  • Implement request routing and rate limiting.
  • Log all interactions for audit and performance monitoring.
  • Internal test: multiple nodes hitting chatbot concurrently.
  • Define failure modes and fallback behavior.

Deliverable: Nodes can securely query AI chatbot and receive deterministic responses.


2. Mobile App Integration

Objective: Integrate node + chatbot + wallet layer into mobile app.

  • Add service access configuration in app settings.
  • Connect mobile wallet to node endpoint.
  • Implement chatbot UI (minimal functional interface).
  • Validate message signing before request dispatch.
  • Handle async response + error states.
  • Local caching strategy for session continuity.
  • Internal build for iOS test distribution.

Deliverable: Mobile app connected to node, able to access AI chatbot through wallet-authenticated session.


3. Internal Release: SOV Send / Receive

Objective: Enable internal token transfers between users.

  • Finalize transaction struct for SOV transfer.
  • Validate signature scheme (Dilithium verification).
  • Implement mempool → block inclusion flow.
  • Confirm balance update consistency.
  • Prevent double spend edge cases.
  • Add transaction history view in app.
  • Internal QA: multi-user transfer simulation.

Deliverable: Users can send and receive SOV internally with confirmed balances.


4. Validate Sign-In Methods

Objective: Confirm all supported authentication flows.

  • Test seed-based wallet restoration.
  • Test DID-based login.
  • Validate device-bound identity logic.
  • Ensure session persistence works correctly.
  • Test logout + re-login edge cases.
  • Verify signature challenge-response flow.
  • Confirm no ambiguity between wallet_id and key_id.

Deliverable: Stable and reproducible authentication across all supported methods.


5. Validate Account Recovery Phrase

Objective: Confirm deterministic recovery flow.

  • Generate wallet from seed phrase.
  • Delete local state.
  • Restore from recovery phrase.
  • Confirm wallet_id matches original.
  • Confirm DID matches original.
  • Confirm balance state syncs correctly.
  • Add warning and confirmation UX for recovery export.

Deliverable: Recovery phrase fully restores identity, wallet, and balances without divergence.


6. CBE Token Initial Supply – Internal Backend Test

Objective: Validate initial minting logic for CBE token.

  • Define genesis allocation (treasury / compensation pool).
  • Execute initial mint transaction on internal network.
  • Validate supply invariants.
  • Confirm token registry indexing.
  • Simulate internal transfer.
  • Confirm accounting integrity (no inflation beyond cap).
  • Log full audit trace.

Deliverable: CBE initial supply minted and verified in internal backend environment.


Weekly Success Criteria

  • Node ↔ AI chatbot functional.
  • Mobile app integrated and internally distributable.
  • SOV transfers working in internal network.
  • Authentication and recovery flows validated.
  • CBE token initial supply successfully minted and tested.

Clone this wiki locally