🛠️ DevLog – Wrapping This Week, Next Week’s Privacy v3 Offchain storage Test Sweep This week we spent most of the time on another full sweep of the privacy feature v1.0 flows across both: 🔹 What also landed this week - Task-level encryption scope got wrapped into the current privacy path as the next stronger isolation option. - Offchain storage v3 for dedicated-node sessions also landed in rough form, giving a configurable offchain storage path for dedicated flows. 🔹 What’s next week’s focus - Start testing these newer additions more directly: - task-level encryption scope - offchain storage v3 on dedicated sessions - Do another broader full sweep across the privacy stack again after those landings: - dedicated privacy - ephemeral privacy - new task-scope path - new configurable offchain storage path So the rough recap is: this week was about stabilizing privacy v1.0 and landing the next pieces; next week is about testing those new pieces in the full flow. #Cortensor #DevLog #Privacy #EncryptedInference #TaskScope #OffchainStorage #DedicatedNodes #EphemeralNodes #DePIN

🛠️ DevLog – Thinking Through Task-Scope Privacy UX While we keep testing the current session-scoped privacy flow, we’ve also been doing some rough dashboard/UI iteration for task-scoped encryption. 🔹 What’s becoming clearer - Task-scope privacy will need a different dashboard UX from session-scope privacy. - With session-scope encryption, the dashboard can fetch one session key and cache it with TTL to view the session flow. - With task-scope encryption, each task uses a different key, so the dashboard can’t treat it like one shared session unlock. 🔹 Why this is trickier - For task-scope, the dashboard would likely need to: - request keys per task, or - batch-request keys for multiple task entries/results - That creates a different UX from the current session modal, where one key can unlock the whole session view. 🔹 What we’re thinking now - More likely, task-scope privacy should be handled closer to the task table / task result entry level instead of “one key for everything.” - As we iterate this, a lot of UX questions are showing up, so we’ll keep thinking through it more while continuing session-scope testing. So the rough support is there on the backend side, but the dashboard side for task-scope privacy is clearly a different product/UX problem than the current session-key flow. #Cortensor #DevLog #Privacy #EncryptedInference #TaskScope #Dashboard #DePIN

🛠️ DevLog – PR: Task-Level Encryption Scope Support for Private Sessions Pushed a PR for the next privacy step: task-level encryption scope for private session payloads, while keeping the current session-level flow as the default. github.com/cortensor/install… 🔹 What this PR adds - Backend support for task-level encryption scope without changing the default session-level behavior. - PrivacySettingData tracking for task-scope settings, with fresh-session-only enablement. - Router-side payload encryption updates so offchain v2 requests can derive/store the correct task-scoped metadata. - Miner-side decrypt/result flow kept aligned with the encrypted payload’s scope metadata. - Backward compatibility preserved by falling back to session-scope behavior when older contracts do not expose the new task-scope getter. 🔹 Why it matters - Session-scope privacy remains the main default path. - This PR adds the stronger task-by-task isolation layer so we can test it next once the current privacy flow is stable. #Cortensor #DevLog #Privacy #EncryptedInference #TaskScope #DePIN

🛠️ DevLog – Task-Level Encryption Scope: Rough Support Added We’ve made the rough adjustments needed on both PrivacySettingData module and the router node to support task-level encryption scope more fully. 🔹 What’s done - Rough code is in for task-scoped privacy settings / key path support. - We’ve already deployed this to testnet0 to make sure it doesn’t introduce regression against the current privacy flow. 🔹 Current stance - We’re not actively iterating or testing task-scope yet. - Session-level encryption is still the main path, and we want that flow to be stable first before opening another test track. 🔹 What’s next - Finish the remaining session-level privacy tests this week. - Then try to start task-level encryption tests next week. - Dashboard work is still needed as part of that path as well. So the rough support is there now, but the main priority remains: stabilize session-scope first, then exercise task-scope next. #Cortensor #DevLog #Privacy #EncryptedInference #TaskScope #DePIN

🛠️ DevLog – Task-Scoped Encryption Prep in Progress Follow-up on the privacy scope note: while we’re still running tests and regression on the current session-scoped encryption flow, we’ve also prepared the next step for task-scoped encryption. 🔹 What’s been done - No full wiring yet, but the rough code/changes on the PrivacySettingData module are already in place for task-level encryption settings / tracking. - This is meant to give router and miner enough signal later to understand which scope key path should be used for a given task. 🔹 Why this matters - Session-scoped encryption is still the main path we’re testing right now. - Task-scoped encryption is the next layer, where each task uses its own deterministic key for stronger isolation. 🔹 What’s next - We’ll deploy these PrivacySettingData changes to testnet0 later this week once the remaining session-scope tests and regressions are done. - If the current session-level flow looks stable enough, then task-scoped encryption will be the next path we exercise more directly. #Cortensor #DevLog #Privacy #EncryptedInference #TaskScope #DePIN

I built an easy-to-use TUI for asyncio ps — atv. Run: uvx atv 🌷— and make sure to use Python 3.14! (I changed the name. It was TaskScope, but now it’s atv.) #pyconjp sprint github.com/jrfk/atv

👍