Apr 3
🛠️ DevLog – First Rough E2E for Deferred Write on v3 Offchain Storage
We’ve now gotten the first rough E2E pass working for deferred write on v3 offchain storage for ephemeral-node support.
🔹 What deferred write means
- For v3 offchain on an ephemeral miner, the miner does not write the result bytes directly to storage itself.
- Instead, it commits the result URN first, then submits the actual result through a router endpoint afterward.
- Router then verifies auth / signature / task assignment / committed URN and writes the result object on behalf of the miner.
🔹 Why this exists
- Dedicated nodes can write result bytes directly because they already have the needed offchain storage config / credentials.
- Ephemeral nodes should not be given those broader write credentials.
- So for ephemeral v3 flow, result writing had to be changed into this deferred router-mediated step.
🔹 Rough flow
- Router stores input in v3 offchain storage first.
- Ephemeral miner reads input and runs inference.
- Miner commits the deterministic result URN onchain.
- After commit, miner calls router /api/v3/offchain/result.
- Router checks signer / assignment / precommit / committed URN and then writes the actual result bytes behind that URN.
🔹 Current status
- First rough E2E on this path worked.
- This is still early and still needs more polishing.
- Next step is waiting for all node operators to upgrade so we can test and harden this flow more broadly.
#Cortensor #DevLog #OffchainStorage #EphemeralNodes #DeferredWrite #Testnet1a
Apr 3
🛠️ DevLog – More Debugging on Deferred Write for Ephemeral Nodes
We’re still debugging the deferred-write flow for offchain storage v3 on ephemeral nodes. The main issue is still around the post-commit step where miners need to call the authenticated router endpoint to materialize their result.
🔹 Current issue
- Ephemeral miner is still not completing the deferred-write step cleanly after commit.
- This is the path where miner needs to hit the authenticated router endpoint and write the result through the router.
- So the remaining issue is still inside that ephemeral-node result-write path.
🔹 Current progress
- We’ve already identified the issue more clearly.
- We’re now adding more logging and another patch so we can see the next failure point more precisely.
- More logs / patch have already been pushed to dev-stable.
🔹 What’s next
- We’ve asked node operators to upgrade all nodes again with the latest patch.
- After that, we’ll continue debugging this deferred-write flow with the added logs.
#Cortensor #DevLog #OffchainStorage #EphemeralNodes #Testnet1a
7
14
889