As discussed in planning, we need an IPFS conn to be able to register primary and secondary name services (e.g. the primary name service to track an up-to-date pointer to the HEAD commit IPFS CID would be file-system managed by db; the IPNS name service would be secondary, but the conn would update both on successful txns)
Implementation Considerations
It is possible to see a delay & failure in the attempts to update the IPNS name service. Because that would be the secondary name service, it would be important to (1) possibly try async attempts in the background on failure to update the IPNS pointer, and (2) to ensure we don't attempt retries (or wait to care about success/failure responses from IPNS) if a new transaction has rendered the previous transaction outdated
Description
As discussed in planning, we need an IPFS
conn
to be able to register primary and secondary name services (e.g. the primary name service to track an up-to-date pointer to the HEAD commit IPFS CID would be file-system managed bydb
; the IPNS name service would be secondary, but theconn
would update both on successful txns)Implementation Considerations
It is possible to see a delay & failure in the attempts to update the IPNS name service. Because that would be the secondary name service, it would be important to (1) possibly try async attempts in the background on failure to update the IPNS pointer, and (2) to ensure we don't attempt retries (or wait to care about success/failure responses from IPNS) if a new transaction has rendered the previous transaction outdated