Roadmap
Known deferrals and what's coming next
All 61 operations documented in this guide are implemented and shipped. This page
covers scaffolding gaps around the node — ProcessStudio form rendering, tests, and verification — not
missing operations.
Known Deferrals
| Item | Status | Notes |
|---|---|---|
GetNodeEntitiesAsync() |
Not implemented | Entity declarations for ProcessStudio form rendering. Matches the reference Ethereum node, which also omits it — tracked as ISSUE-17 in the design docs. |
| Unit tests | Follow-up work item | No automated test suite yet for the executor, services, or domain layers. |
| DB Forms / FormControls | Follow-up work item | Database-backed form definitions for the ProcessStudio designer are not yet authored. |
| Live-daemon verification | Follow-up work item | The review pass verified factory↔routing↔partial-cast consistency and output-contract uniformity by code review; running all 61 operations against a live Kubo + Cluster daemon pair has not yet been done. |
Hardening History
Beyond the initial build, a review + hardening pass already landed the following fixes — included here so it's clear what's already been through a second pass, not just first-draft code:
storage/verifyIntegrityCIDv1 inference — previously false-failed for content originally added as CIDv1; now infers the CID version from the expected CID's own prefix.storage/uploadAndPin— the KubobaseUrlis only required on the non-Cluster path, so a Cluster-only configuration doesn't need a Kubo connection it never uses.- Operation strings normalized to uniform camelCase across all 61 operations.
sizeBytesoutput keys renamed tosizefor consistency.IPFSResilienceHandlerfixed to buffer request content once before the retry loop (re-reading disposed content had broken retries for every upload operation).dag/statfield parsing corrected toTotalSize/UniqueBlocks;key/importswitched to the required multipartkeyfile part.- Every typed HTTP client has default URI logging disabled so a remote-pin API key carried in a query string can never leak through framework request logs.
- SSRF deny-list hardened against IPv4-mapped IPv6 encoding bypasses.
- Error codes normalized to
UPPER_SNAKE; all user-supplied query values escaped.
Full technical detail: see the executor project's
DevelopmentHistoryLog.md and the operation-reference
Docs/IPFSNodeExecutor.md in the node's source (linked from the
IpfsAgents repository's src/
folder).