Eirel SDK guidance: routing, compliance, wallet issues

Team clarified miner submission flow: build agents as routers (fetch URLs, route to search/compute/answer), pass compliance checks, register endpoints, then status-check before scoring. A user reported 401 authorization error when registering; root cause identified as CLI using wrong wallet identity—clear cache or force identity via flags/env vars. Deployment queues are normal; watch dashboard for actual timing.

• •Build routers, not chatbots; fetch URLs when present in prompts
• •Submission flow: build → compliance (green) → register → status check
• •401 CLI error: wrong wallet identity; clear ~/.eirel/ cache or force via flags
• •Deployments queued is expected; build and deploy phases normal