🛠️ DevLog – Follow-Up Gaps on Privacy v1.0 and Offchain Storage v3 As we keep iterating on these flows, we found a couple more practical gaps around privacy v1.0 task-level encryption and ephemeral-node support for offchain storage v3. 🔹 Privacy v1.0 task-scope gap - Dashboard still needs a better UX flow for task-level key retrieval from the task table. - This is different from the current session-level encryption flow, since task-level privacy uses a different key per task. - Router endpoint support for task-level key retrieval is already there, so the main gap right now is more on dashboard UX / human flow friction. 🔹 Why this creates friction - For task-level privacy, dashboard / human flow needs signing each time to retrieve the task key. - That is workable, but it creates more noise compared to backend code paths where key retrieval can be handled more directly. - So the feature path exists, but dashboard UX still needs refinement to make it cleaner. 🔹 Offchain storage v3 gap for ephemeral nodes - Ephemeral nodes cannot directly write into a custom S3 / configurable offchain bucket, since the bucket owner should not share broad credentials. - To handle that, we are adding a new router endpoint where ephemeral node can submit the actual result through the router instead. - Router would then verify auth, including signature and session/task-level assignment, before performing the write. 🔹 What’s next We’ll try to close these gaps next week as we continue iterating and testing both flows. #Cortensor #DevLog #Privacy #Encryption #OffchainStorage #EphemeralNodes
