ruvnet/ruflo · error
⚠ [Discovery] OFFLINE MODE - Could not resolve IPNS: ${ipnsN
Error message
⚠ [Discovery] OFFLINE MODE - Could not resolve IPNS: ${ipnsName} What it means
Warning in resolveIPNS: IPNS resolution failed across all gateways (network offline or gateways unreachable), so the store switches to offline mode for this lookup.
Source
Thrown at v3/@claude-flow/cli/src/transfer/store/discovery.ts:211
ipnsName,
cid,
resolvedAt: new Date().toISOString(),
expiresAt: new Date(Date.now() + 3600000).toISOString(),
};
this.ipnsCache.set(ipnsName, resolution);
console.log(`[Discovery] Resolved IPNS via redirect to CID: ${cid}`);
return resolution;
}
}
} catch (error) {
console.warn(`[Discovery] IPNS resolution via ${gateway} failed:`, error);
// Continue to next gateway
}
}
// Fallback: Generate deterministic CID for well-known registries
console.warn(`⚠ [Discovery] OFFLINE MODE - Could not resolve IPNS: ${ipnsName}`);
console.warn(`⚠ [Discovery] Using built-in fallback registry (may be outdated)`);
const fallbackCid = this.generateFallbackCID(ipnsName);
const resolution: IPNSResolution = {
ipnsName,
cid: fallbackCid,
resolvedAt: new Date().toISOString(),
expiresAt: new Date(Date.now() + 3600000).toISOString(),
};
this.ipnsCache.set(ipnsName, resolution);
return resolution;
}
/**
* Generate deterministic fallback CID for offline/demo mode
*/
private generateFallbackCID(input: string): string {
const hash = crypto.createHash('sha256').update(input + 'registry').digest();View on GitHub (pinned to fa13ee4ad6)
Solutions
- Check network access and the IPNS name; the client runs offline with the fallback registry until IPNS resolution succeeds.
Defensive patterns
Strategy: fallback
When it happens
Trigger: Thrown at v3/@claude-flow/cli/src/transfer/store/discovery.ts:211 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of ruvnet/ruflo@fa13ee4ad6 (2026-08-18).
Data as JSON: /api/errors/1854ac14c1a4ed0d.
Report an issue: GitHub.