Files
aitbc/docs/archive/expert/issues/01_preflight_checklist.md
aitbc 19d415a235
Some checks failed
Blockchain Synchronization Verification / sync-verification (push) Failing after 3s
CLI Tests / test-cli (push) Failing after 3s
Cross-Chain Functionality Tests / test-cross-chain-sync (push) Successful in 2s
Cross-Chain Functionality Tests / test-cross-chain-transactions (push) Successful in 3s
Cross-Chain Functionality Tests / test-cross-chain-bridge (push) Has been skipped
Cross-Chain Functionality Tests / test-multi-chain-consensus (push) Successful in 2s
Cross-Chain Functionality Tests / aggregate-results (push) Has been skipped
Deploy to Testnet / deploy-testnet (push) Successful in 1m12s
Documentation Validation / validate-docs (push) Failing after 8s
Documentation Validation / validate-policies-strict (push) Successful in 3s
Integration Tests / test-service-integration (push) Successful in 2m6s
Multi-Chain Island Architecture Tests / test-multi-chain-island (push) Successful in 2s
Multi-Node Blockchain Health Monitoring / health-check (push) Failing after 4s
P2P Network Verification / p2p-verification (push) Successful in 4s
Package Tests / Python package - aitbc-agent-sdk (push) Successful in 32s
Package Tests / Python package - aitbc-core (push) Successful in 14s
Package Tests / Python package - aitbc-crypto (push) Successful in 12s
Package Tests / Python package - aitbc-sdk (push) Successful in 9s
Package Tests / JavaScript package - aitbc-sdk-js (push) Successful in 8s
Package Tests / JavaScript package - aitbc-token (push) Successful in 17s
Python Tests / test-python (push) Successful in 15s
Security Scanning / security-scan (push) Successful in 27s
Node Failover Simulation / failover-test (push) Successful in 7s
Multi-Node Stress Testing / stress-test (push) Successful in 6s
Cross-Node Transaction Testing / transaction-test (push) Successful in 4s
feat: add SQLCipher database encryption support and consolidate agent documentation
- Add SQLCipher encryption for ait-mainnet database with configurable flag
- Add db_encryption_enabled and db_encryption_key_path config settings
- Implement encryption key loading and PRAGMA key setup via connection events
- Add shutdown_db function for proper database cleanup
- Export middleware classes in aitbc/__init__.py
- Fix import path in sync.py for settings
- Remove duplicate agent documentation from docs
2026-05-03 12:00:38 +02:00

2.0 KiB
Raw Blame History

Preflight Checklist (Before Implementation)

Use this checklist before starting Stage 20 development work.

Tools & Versions

  • Circom v2.2.3+ installed (circom --version)
  • snarkjs installed globally (snarkjs --help)
  • Node.js + npm aligned with repo version (node -v, npm -v)
  • Vitest available for JS SDK tests (npx vitest --version)
  • Python 3.13+ with pytest (python --version, pytest --version)
  • NVIDIA drivers + CUDA installed (nvidia-smi, nvcc --version)
  • Ollama installed and running (ollama list)

Environment Sanity

  • .env files present/updated for coordinator API
  • Virtualenvs active (.venv for Python services)
  • npm/yarn install completed in packages/js/aitbc-sdk
  • GPU available and visible via nvidia-smi
  • Network access for model pulls (Ollama)

Baseline Health Checks

  • npm test in packages/js/aitbc-sdk passes
  • pytest in apps/coordinator-api passes
  • pytest in apps/blockchain-node passes
  • pytest in apps/wallet-daemon passes
  • pytest in apps/pool-hub passes
  • Circom compile sanity: circom apps/zk-circuits/receipt_simple.circom --r1cs -o /tmp/zkcheck

Data & Backup

  • Backup current .env files (coordinator, wallet, blockchain-node)
  • Snapshot existing ZK artifacts (ptau/zkey) if any
  • Note current npm package version for JS SDK

Scope & Branching

  • Create feature branch for Stage 20 work
  • Confirm scope limited to 0104 task files plus testing/deployment updates
  • Review success metrics in 00_nextMileston.md

Hardware Notes

  • Target consumer GPU list ready (e.g., RTX 3060/4070/4090)
  • Test host has CUDA drivers matching target GPUs

Rollback Ready

  • Plan for reverting npm publish if needed
  • Alembic downgrade path verified (if new migrations)
  • Feature flags identified for new endpoints

Mark items as checked before starting implementation to avoid mid-task blockers.