This page lists the parts of IICP that are not yet production-ready, so operators can plan around them without having to follow every engineering discussion.
ActiveReachability
Relay and tunnel fallback need broader real-world testing
Direct reachability is still preferred. Current clients can use automatic tunnel or relay fallback when a node cannot prove direct IPv4, IPv6 or pinhole reachability, and supervised nodes have recovered successfully after sleep or tunnel cooldown in live use. This is useful, but the fallback path still needs more evidence across home routers, CGNAT, Docker, tunnel rotation, abuse controls and relay-path confidentiality. Accountless Quick Tunnels are useful for bootstrap/testing but can be rate-limited; persistent relays should use a named tunnel or operator-managed public endpoint.
What to do: Use a direct public endpoint when you can. If that is not possible, run a current client with cloudflared available and a real process supervisor. Let short recovery windows clear before restarting; force a temporary tunnel for testing with --tunnel, disable tunnel fallback with IICP_TUNNEL=0, or configure a named Cloudflare Tunnel / configured or auto-elected relay path where available.
Status detail: Self-recovery is available as an experimental resilience path; it is not a reliability guarantee or a replacement for healthy direct routing.
ActiveOperator
Fresh nodes need time before their telemetry affects scoring
New nodes can register, heartbeat and serve tasks immediately, but some scoring inputs deliberately wait until the node has enough age and outcome history. This avoids letting throwaway identities distort latency, audit or reputation signals too early.
What to do: Start the node and let it serve normally. Health, reachability and key-readiness can appear quickly; deeper trust signals improve as successful task history accumulates.
Status detail: This is intentional anti-abuse friction, not a setup error.
ActiveFederation
Federated directories are not publicly deployed yet
The public network still relies on the iicp.network directory as the Genesis control plane. The Rust directory is available as a pre-1.0 operator preview, but independent public replicas are not yet part of the live mesh.
What to do: Use the Rust preview for local evaluation only. Do not describe the current network as fully decentralized.
Status detail: Public source is available; production replica activation, partition recovery and support remain later gates.
ActiveSpec
Operator diversity scoring does not yet consume operator binding
Operator identity and fleet wallet rollup are live, but anti-Sybil diversity scoring does not yet fully treat multiple nodes from one operator as one coordinated fleet for all scoring purposes.
What to do: Bind nodes to an operator identity now so future diversity and recognition features have the correct foundation.
Status detail: Useful identity foundation is live; full diversity scoring is still future scoring work.
ActiveCompliance
Compliance readiness is not a finished portal or legal certification
IICP now has a beta privacy notice baseline, a manual rights workflow, an operator-key authenticated self-service API foundation, retention/process documentation, AI-risk classification, a browser-side strict allowed-region guard, first operator-bound policy-manifest evidence and technical release gates. That is compliance engineering work, not a final GDPR/EU AI Act certification. A guided portal, cross-client known-operator transfer evidence, broader redacted receipts, DPAs/subprocessor handling and legal review are still roadmap work.
What to do: For sensitive or regulated data, prefer local/browser inference or conservative remote-routing profiles such as sensitive, eu-restricted or strict-policy. Use the manual privacy/security contact path for access, export, restriction or deletion requests during beta.
Status detail: The signed API foundation exists; the protected guided portal and broader machine-checkable evidence remain planned.
ActiveClient
HuggingFace TGI inbound shape is not implemented yet
The proxy supports OpenAI-compatible, Ollama-compatible and Anthropic-compatible inbound shapes. HuggingFace TGI format is still a remaining compatibility gap.
What to do: Use OpenAI, Ollama or Anthropic compatible clients for now. All three are available on the proxy port without extra configuration.
Status detail: Compatibility gap; not a core mesh blocker.
ActivePerformance
Some aggregate latency metrics lag spot improvements
Short-term discover latency can improve before longer-window aggregate metrics fully converge. A 24-hour aggregate may therefore look worse than a current spot check immediately after tuning.
What to do: Use current request timing for spot checks and the stats endpoint for longer-window trend monitoring.
Status detail: This is a measurement-window caveat.
ActiveOperator
Community forum is public, but still early-launch/noindex
The forum is available to read, but public registration is closed during testing while moderation, backup, security and rollback processes mature.
What to do: Use the forum for public project discussion, but do not post secrets, private prompts or sensitive support data. Use [email protected] for issues that need a direct contact path.
Status detail: Public foundation exists; operational community processes still mature.
ActiveOperator
Founder recognition is live; the broader rank ladder is not
Founder ordinals and early recognition are live, but the broader long-term progression ladder is still draft work and should not be treated as a public gamification system yet.
What to do: Run a node with an operator identity to establish founder recognition now. Treat broader ranks as future community design.
Status detail: Recognition exists; rank progression remains future work.