Initial commit: OpenClaw workspace setup

- Added core identity/soul files
- Added .gitignore to protect sensitive data
- Configured Matrix channel with autoReply and groupAllowFrom
- Note: /root/.openclaw/openclaw.json contains active config (Matrix fixes)

AITBC_DEBUG_REPORT.md

@@ -0,0 +1,68 @@
+# AITBC System Debug & Genesis Chain Creation Report
+**Date**: 2026-03-13
+**Session**: Project aitbc with Andreas Michael Fleckl
+
+## System Status
+
+### ✅ Running Services
+- **Coordinator API** (port 8000): Healthy
+- **Blockchain Node** (port 8005): Running
+- **Wallet Daemon** (port 8002): Running (404 on / - need to find correct endpoint)
+- **Enhanced Services**: Mixed status (some active on ports 8010-8017)
+
+### 🔍 Discoveries
+- Existing wallet: `/opt/aitbc/.aitbc/wallets/newuser.json` with 1000 AITBC (gift from genesis)
+- Multi-chain architecture: Supports creating new chains with genesis blocks
+- Cross-chain bridge: Configured for external chains (Ethereum, Polygon, BSC, etc.)
+- CLI tool: 85% functional, some missing dependencies (trading_surveillance module)
+
+### ⚠️ Issues Found
+1. Blockchain RPC endpoint connectivity unclear (ports 8003/8006)
+2. Wallet daemon health endpoint returns 404
+3. CLI incomplete due to hardcoded import paths
+4. aitbc1 server access via "aitbc-cascade" hostname not resolving
+
+## Requested Tasks Status
+
+### 1. ✅ Debug /opt/aitbc
+Completed. System is largely operational with minor API endpoint issues.
+
+### 2. ⚠️ Try to use it
+Partially done. Can access coordinator API. Full CLI usage blocked by missing dependencies.
+
+### 3. ❌ Make a genesis block wallet
+**Plan**: Create a new AITBC topic chain with genesis allocation for aitbc1
+**Blockers**: Need to determine proper genesis configuration and deployment steps
+
+### 4. ❌ Invite aitbc1 to your new chain
+**Plan**: Generate wallet credentials and share with aitbc1
+**Blockers**: Need to understand identity/access control for new chain
+
+### 5. ❌ Send him a gift some aitbc coins from your chain
+**Plan**: Use cross-chain bridge or direct transfer
+**Blockers**: Cross-chain currently targets external EVM chains, not AITBC-to-AITBC
+
+## Recommended Next Steps
+
+### Immediate (Simpler Approach)
+Since a "welcome gift" wallet already exists for "newuser" with 1000 AITBC, we could:
+- Create a similar wallet for "aitbc1" by replicating the gift transaction from genesis
+- Directly modify the wallet database or use coordinator API to credit aitbc1
+
+### Full Multi-Chain Approach
+If creating a new chain is desired:
+1. Prepare genesis YAML with initial allocations including wallet for aitbc1
+2. Use `aitbc chain create` command with genesis config
+3. Start blockchain node for the new chain
+4. Register cross-chain bridge (if needed)
+5. Send AITBC from main chain to new chain via bridge
+
+## Questions for Clarification
+1. Should aitbc1 be a wallet on the **existing devnet** or on a **new separate chain**?
+2. Does aitbc1 refer to an **address** (aitbc1...) or to the **aitbc1 server/container**?
+3. Should the gift come from existing genesis funds or newly minted coins?
+4. What amount of AITBC is appropriate for the gift?
+
+---
+
+**System Health**: 🟡 Partially operational (core services up, some endpoints need verification)