🛠️ DevLog – Wrapping Up the Current MVP Data-Management Matrix Tests We’re now roughly wrapping up the current matrix-test round for the MVP data-management features. 🔹 Current result So far, the main permutations and matrix combinations are working as intended. Across the current combinations of privacy mode, node type, scope, and offchain storage v3 path, the essential flows are functioning in the way we expected. 🔹 What this covers This includes the broader combinations across: - public / private - dedicated / ephemeral - session scope / task scope - offchain storage v3, including deferred write for ephemeral nodes - single and multiple-node style paths 🔹 What this means - For now, the MVP data-management layer is holding up across the main combinations we wanted to recheck. - That gives us a good base for the current phase and confirms that the essential mixed paths are working, not just the isolated feature paths. 🔹 What’s next - We’ll keep doing more testing in the coming weeks, and we’ll likely still find more refinements, issues, and bug fixes during the rest of this phase. - But for now, the main matrix paths are functioning as intended. #Cortensor #DevLog #Privacy #OffchainStorage #DataOwnership #Dashboard

🛠️ DevLog – Matrix Test Progress Router/Dashboard Refinements We’ve been continuing the MVP data-management matrix tests, and overall things are looking more stable across those paths. At the same time, we’re also pushing a few more router and dashboard refinements around privacy and offchain storage v3. 🔹 Matrix test progress - So far, the current matrix paths look mostly stable overall. - We’re still checking for smaller mixed-path gaps, but the broader privacy offchain storage v3 combinations are holding up better now. 🔹 Router-side follow-up There are a few more router-node patches we want to apply based on what we saw during matrix testing. We’ll build those and push them to dev-stable shortly. 🔹 Dashboard follow-up We also have a few dashboard-side patches lined up and will push those shortly/today as well. This is mostly around UI/UX refinement while these MVP data-management flows get exercised more heavily. 🔹 Small UX updates One small UI change is adding a clearer Public badge, alongside the privacy-related session/task indicators, so the current mode is easier to read at a glance. 🔹 What’s next A few more fixes around privacy and offchain storage v3 are also coming shortly as we keep tightening both backend flow and dashboard usability together. #Cortensor #DevLog #Privacy #OffchainStorage #Dashboard #DataOwnership

🛠️ DevLog – Recap on MVP Data-Management Matrix Tests We’ve been running through a broader matrix of MVP data-management tests to recheck how privacy and offchain storage v3 behave across different node types, privacy settings, and result paths. 🔹 Current matrix paths - private ephemeral offchain v3: dashboard-testnet1a.cortenso… - public ephemeral offchain v3: dashboard-testnet1a.cortenso… - private dedicated offchain v3: dashboard-testnet1a.cortenso… - ephemeral offchain v3 multiple: dashboard-testnet1a.cortenso… - dedicated offchain v3 multiple: dashboard-testnet1a.cortenso… - private ephemeral offchain v3 task-scope privacy: dashboard-testnet1a.cortenso… - private dedicated offchain v3 task-scope privacy: dashboard-testnet1a.cortenso… 🔹 What this covers This matrix now spans public/private modes, ephemeral/dedicated paths, single/multiple miner behavior, and both session-scope and task-scope privacy combinations with offchain storage v3. 🔹 Current focus The goal here is not just to confirm that the core MVP paths work individually, but to surface mixed-path bugs, regression gaps, and dashboard friction when these features are combined in more realistic ways. 🔹 What’s next We’ll keep continuing these matrix tests, surface any remaining gaps, and keep refining the dashboard/UI/UX around privacy scope and offchain storage as we go. #Cortensor #DevLog #Privacy #OffchainStorage #DataOwnership #Dashboard

🛠️ DevLog – Running More MVP Data-Management Matrix Tests We’re now running through more of the matrix tests across the current MVP data-management features so we can check how these flows behave across different privacy, node, and offchain-storage combinations. 🔹 Current matrix tests - private ephemeral offchain v3: dashboard-testnet1a.cortenso… - public ephemeral offchain v3: dashboard-testnet1a.cortenso… - private dedicated offchain v3: dashboard-testnet1a.cortenso… - ephemeral offchain v3 multiple: dashboard-testnet1a.cortenso… - dedicated offchain v3 multiple: dashboard-testnet1a.cortenso… 🔹 Current context This is part of the broader regression and matrix-testing pass for the MVP data-management layer, so the goal here is to check more of the combined paths instead of only testing features one by one. 🔹 What’s next We’re covering most of the current matrix first, then task-scope encryption combo tests will come after these matrix checks and regression passes, since that is the last more complex mixed path we still want to recheck carefully. #Cortensor #DevLog #Privacy #OffchainStorage #DataOwnership #EphemeralNodes

🛠️ DevLog – Running More MVP Data-Management Matrix Tests We’re now running through more of the matrix tests across the current MVP data-management features so we can check how these flows behave across different privacy, node, and offchain-storage combinations. 🔹 Current matrix tests - private ephemeral offchain v3: dashboard-testnet1a.cortenso… - public ephemeral offchain v3: dashboard-testnet1a.cortenso… - private dedicated offchain v3: dashboard-testnet1a.cortenso… - ephemeral offchain v3 multiple: dashboard-testnet1a.cortenso… - dedicated offchain v3 multiple: dashboard-testnet1a.cortenso… 🔹 Current context This is part of the broader regression and matrix-testing pass for the MVP data-management layer, so the goal here is to check more of the combined paths instead of only testing features one by one. 🔹 What’s next We’re covering most of the current matrix first, then task-scope encryption combo tests will come after these matrix checks and regression passes, since that is the last more complex mixed path we still want to recheck carefully. #Cortensor #DevLog #Privacy #OffchainStorage #DataOwnership #EphemeralNodes

🛠️ DevLog – Starting Combo Tests on MVP Data Management We’ve now started moving from separate regression checks into combo tests across the current MVP data-management features, so we can see how privacy and offchain storage v3 behave when they are mixed together in more realistic flows. 🔹 Current test direction We first rechecked privacy feature flows and offchain storage v3 flows separately, and now we’re starting fuller combo tests where those paths run together instead of in isolation. 🔹 Current combo path The current combo path is focused on private session scope ephemeral nodes offchain storage v3 deferred write. So this is already closer to the actual mixed MVP flow we want to support, not just a single-feature check. 🔹 Current test session dashboard-testnet1a.cortenso… 🔹 What we’re seeing So far, it looks like there may be a bug when these paths are combined. Individual feature paths were already looking better on their own, but mixing privacy offchain storage v3 together is surfacing another issue we need to check further. 🔹 What’s next After this ephemeral/session-scope combo path, we’ll continue through more of the combo matrix as well: - private task scope ephemeral nodes offchain storage v3 - dedicated-node combinations again across the same privacy storage paths #Cortensor #DevLog #Privacy #OffchainStorage #DataOwnership #EphemeralNodes

🗓️ Weekly Focus – Phase #3 Support, v3 /delegate & /validate Iteration & MVP Data Management Testing 🔹 Phase #3 – Support, Monitoring & Stats - Continue active monitoring across routing, miners, validators, dashboards, and L3 stats. - Track stability as more features move into deeper testing. 🔹 v3 /delegate /validate – Iteration - With last week’s prep done, we’ll now iterate more deeply on /delegate and /validate to make them more solid. - Focus on real delegation/validation paths, routing behavior, and closing logic gaps from early tests. 🔹 Privacy Feature 1.0 – Regression Testing - Run deeper regression on session-scope and task-scope encryption. - Cover both dedicated-node and ephemeral-node paths again to confirm stability. 🔹 Offchain Storage v3 – Regression Testing - Run deeper regression on dedicated-node and ephemeral-node storage flows, including deferred writes. - Re-check storage behavior and operator-configured offchain paths. 🔹 MVP Data Management – Full E2E Tests - After testing each feature separately, run combined privacy offchain end-to-end tests again. - Goal: confirm the full MVP stack works consistently across dedicated, ephemeral, router, miner, and dashboard flows. 🔹 Dashboard – UI/UX Refinement - Keep refining dashboard UX around privacy scope and offchain storage so these flows are easier to use in practice. 🔹 Inference Quality Control – Rough Design - Spend a bit of time on rough design for ephemeral-node inference quality control using real task probes and sliding-window stats. - Goal: improve routing and reliability based on recent functional behavior, not just static availability. This week is about pushing the MVP data-management stack through a more serious validation cycle, tightening v3 agent surfaces, and doing early design work on inference quality control. #Cortensor #Testnet #Phase3 #AIInfra #DePIN #Corgent #Bardiel #Delegate #Validate #PrivateAI #L3

🗓️ Weekly Focus – Phase #3 Support, v3 /delegate & /validate Iteration & MVP Data Management Testing 🔹 Phase #3 – Support, Monitoring & Stats - Continue active monitoring across routing, miners, validators, dashboards, and L3 stats. - Track stability as more features move into deeper testing. 🔹 v3 /delegate /validate – Iteration - With last week’s prep done, we’ll now iterate more deeply on /delegate and /validate to make them more solid. - Focus on real delegation/validation paths, routing behavior, and closing logic gaps from early tests. 🔹 Privacy Feature 1.0 – Regression Testing - Run deeper regression on session-scope and task-scope encryption. - Cover both dedicated-node and ephemeral-node paths again to confirm stability. 🔹 Offchain Storage v3 – Regression Testing - Run deeper regression on dedicated-node and ephemeral-node storage flows, including deferred writes. - Re-check storage behavior and operator-configured offchain paths. 🔹 MVP Data Management – Full E2E Tests - After testing each feature separately, run combined privacy offchain end-to-end tests again. - Goal: confirm the full MVP stack works consistently across dedicated, ephemeral, router, miner, and dashboard flows. 🔹 Dashboard – UI/UX Refinement - Keep refining dashboard UX around privacy scope and offchain storage so these flows are easier to use in practice. 🔹 Inference Quality Control – Rough Design - Spend a bit of time on rough design for ephemeral-node inference quality control using real task probes and sliding-window stats. - Goal: improve routing and reliability based on recent functional behavior, not just static availability. This week is about pushing the MVP data-management stack through a more serious validation cycle, tightening v3 agent surfaces, and doing early design work on inference quality control. #Cortensor #Testnet #Phase3 #AIInfra #DePIN #Corgent #Bardiel #Delegate #Validate #PrivateAI #L3

🛠️ DevLog – Delegate Now Executes Normal Task Requests More Naturally PR: github.com/cortensor/install… We made a rough change on /delegate v2 and /delegate v3 so normal task-style calls can now return the actual task output more naturally, instead of always returning a delegation plan. This is still rough code only for now, and nothing here has been tested yet. 🔹 What changed - Normal task-style delegate calls can now return actual task output. - Explicit planner-style requests still preserve the older planning behavior. - This change is isolated to /delegate v2 and /delegate v3. 🔹 Why this matters - Before this, /delegate could lean too much toward returning a plan even when the caller was really asking for execution. - With this change, things like web fetch summarize style requests should behave more naturally. - So this helps /delegate move a bit closer to a more practical execution surface. 🔹 Current behavior - If the request clearly asks for planning through things like evaluation_mode, task_type, or other planner-style inputs, the planner path is still preserved. - Otherwise, the delegate path can now behave more like a normal task execution request. 🔹 Current status - Rough code only. - Nothing tested yet. - This is mainly an isolated iteration step as we keep refining /delegate behavior. #Cortensor #DevLog #Delegate #AgenticAI #RouterNode

🛠️ 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

🛠️ 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

🛠️ 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

🛠️ DevLog – More Progress on Offchain Storage v3 Ephemeral Flow After the latest patch, it looks like the router-side path is now functioning, but we still cannot fully validate the end-to-end offchain storage v3 flow yet because not all nodes appear to be upgraded. 🔹 Current progress - Router-side behavior looks more functional after the patch. - The current path is moving further than before, which is a good sign. - But full E2E validation still depends on more nodes running the updated version. 🔹 Current gap - It does not look like all nodes are upgraded yet for this flow. - So right now, that is still blocking a cleaner full-path test for ephemeral-node offchain storage v3. - The remaining issue looks more operational/version-alignment related than the earlier router-side code path problem. 🔹 What we added - We also added more logs to make debugging this flow easier once the remaining nodes are upgraded. - That should give us better visibility into where the deferred write/materialization path is succeeding or failing. 🔹 What’s next - Wait for the remaining node upgrades. - Then rerun the offchain storage v3 ephemeral flow and debug with the added logs if needed. #Cortensor #DevLog #OffchainStorage #EphemeralNodes #Testnet1a

🛠️ DevLog – More Progress on Offchain Storage v3 Ephemeral Flow After the latest patch, it looks like the router-side path is now functioning, but we still cannot fully validate the end-to-end offchain storage v3 flow yet because not all nodes appear to be upgraded. 🔹 Current progress - Router-side behavior looks more functional after the patch. - The current path is moving further than before, which is a good sign. - But full E2E validation still depends on more nodes running the updated version. 🔹 Current gap - It does not look like all nodes are upgraded yet for this flow. - So right now, that is still blocking a cleaner full-path test for ephemeral-node offchain storage v3. - The remaining issue looks more operational/version-alignment related than the earlier router-side code path problem. 🔹 What we added - We also added more logs to make debugging this flow easier once the remaining nodes are upgraded. - That should give us better visibility into where the deferred write/materialization path is succeeding or failing. 🔹 What’s next - Wait for the remaining node upgrades. - Then rerun the offchain storage v3 ephemeral flow and debug with the added logs if needed. #Cortensor #DevLog #OffchainStorage #EphemeralNodes #Testnet1a

🛠️ DevLog – Focusing on the Last Offchain Storage v3 Gap Today We’ll mainly be looking at the remaining offchain storage v3 gap today so we can at least roughly wrap up the current E2E path, since this is the last major missing piece in that flow. 🔹 Current test session dashboard-testnet1a.cortenso… 🔹 Current context - This session will be used for the next round of testing on the deferred-write path for ephemeral nodes. - The goal is to push the offchain storage v3 flow closer to rough E2E completion on testnet1a. 🔹 Early issue found - We already found an issue in the ephemeral-node support / code path. - We’ll release a patch shortly and ask node operators to upgrade again. - After that, we’ll continue testing the flow. #Cortensor #DevLog #OffchainStorage #EphemeralNodes #Testnet1a

🛠️ DevLog – What’s Left for This Week At this point, the v3 /delegate and /validate endpoint setup is fully ready, so the next step is to keep testing these endpoints and iterating further on the actual logic inside them. 🔹 v3 /delegate /validate - Surface and session mapping side is now in place. - This week, the focus is more on running tests and refining the endpoint logic through iteration. 🔹 Offchain storage v3 - More node operators have now upgraded, or are in the process of upgrading, to the latest node version. - That means we should now be able to look at the last main gap in the current offchain storage v3 flow. - The remaining piece is testing the deferred write path where an ephemeral node sends its result through the router node instead of writing directly. 🔹 Current focus - Main goal for the rest of this week is to push both of these forward: - keep iterating on v3 /delegate and /validate - and test the remaining deferred-write gap on offchain storage v3 for ephemeral nodes #Cortensor #DevLog #Delegate #Validate #OffchainStorage #EphemeralNodes

🛠️ DevLog – v3 /delegate & /validate Session Mapping Now Set Across All 4 Endpoints We’ve now finished the current 1 / 3 / 5 session mapping setup for v3 /delegate and /validate across all 4 testnet1a router endpoints. At this point, the main infra/surface mapping is in place, so the next phase is more about iterating on the actual logic inside the v3 flows. 🔹 Current endpoint mapping router0-t1a.cortensor.app 1 → dashboard-testnet1a.cortenso… 3 → dashboard-testnet1a.cortenso… 5 → dashboard-testnet1a.cortenso… router1-t1a.cortensor.app 1 → dashboard-testnet1a.cortenso… 3 → dashboard-testnet1a.cortenso… 5 → dashboard-testnet1a.cortenso… router0-t1a.bardiel.app 1 → dashboard-testnet1a.cortenso… 3 → dashboard-testnet1a.cortenso… 5 → dashboard-testnet1a.cortenso… router1-t1a.bardiel.app 1 → dashboard-testnet1a.cortenso… 3 → dashboard-testnet1a.cortenso… 5 → dashboard-testnet1a.cortenso… 🔹 What this means - All four router env mappings are now aligned. - The example/documentation block is also aligned with the same operational naming style. - So the session routing shape for v3 /delegate and /validate is now set more cleanly across the full testnet1a router surface. 🔹 Current status - This is mainly mapping/setup progress. - We still need to keep iterating on the actual logic inside v3 /delegate and /validate. - But now the main endpoint/session mapping layer is in place, which makes the next iteration steps cleaner. 🔹 What’s next - Reload / restart the affected router deployments so the new mapping is fully live. - Then continue testing and iterating on the v3 logic itself over time. #Cortensor #DevLog #Delegate #Validate #RouterNode #Bardiel

🛠️ DevLog – Added Deferred v3 Offchain Result Upload for Ephemeral Miners PR: github.com/cortensor/install… We added rough miner-side support for the v3 offchain result flow on ephemeral nodes. This is the follow-up piece for the router-mediated write path we were discussing earlier. It is still rough code only for now, and nothing here has been tested yet. 🔹 What changed - Added miner-side support for the v3 offchain result flow on ephemeral nodes. - Existing v1/v2 paths and dedicated-node v3 flow stay unchanged. - For v3 ephemeral, offchain result upload is now deferred until after successful commit. 🔹 How this works - Miner temporarily caches the result content locally first. - After commit, miner uploads the result through router POST /api/v3/offchain/result. - Miner reuses session router metadata to resolve the correct router REST endpoint for that post-commit upload. 🔹 Why this matters - Dedicated-node v3 already had its path earlier. - This rough change is mainly about closing the remaining ephemeral-node gap for configurable offchain storage v3. - With this in, most of the current flow shape is now in place in rough form. 🔹 Current status - Rough code only. - Nothing tested yet. #Cortensor #DevLog #OffchainStorage #EphemeralNodes #DataOwnership #DePIN

🗓️ Weekly Focus – Phase #3 Support, v3 Endpoints & Privacy/Offchain Testing 🔹 Phase #3 – Support, Monitoring & Stats - Continue active support and monitoring across routing, miners, validators, dashboards, and L3 stats. - Track stability and performance as v3 surfaces and privacy features are exercised more heavily. 🔹 v3 /delegate /validate – Implementation & Rollout Prep - 3 sessions are now ready for v3 /delegate and /validate iteration. - Finish rough implementation this week and begin testing. - Start rolling out to the 4 router endpoints (Corgent Bardiel) once initial tests pass. 🔹 Privacy Feature 1.0 – Regression Testing - Continue regression testing across privacy flows. - Focus on stabilizing session-level encryption paths. 🔹 Privacy Feature 1.0 – Scope Testing (Task-Level) - Run deeper testing on task-level encryption (newly rolled out). - Close remaining dashboard/UI gaps for task-scope opt-in flows. 🔹 Offchain v3 Testing (Dedicated Ephemeral) - Both dedicated-node and ephemeral-node support are now available. - Focus this week on: - regression testing - validating v3 offchain flows across both node types This week is about supporting Phase #3 while moving v3 /delegate /validate into real testing, and continuing to harden privacy offchain flows across the full system. #Cortensor #Testnet #Phase3 #AIInfra #DePIN #Corgent #Bardiel #Delegate #Validate #PrivateAI #L3

🗓️ Weekly Focus – Phase #3 Support, v3 Endpoints & Privacy/Offchain Testing 🔹 Phase #3 – Support, Monitoring & Stats - Continue active support and monitoring across routing, miners, validators, dashboards, and L3 stats. - Track stability and performance as v3 surfaces and privacy features are exercised more heavily. 🔹 v3 /delegate /validate – Implementation & Rollout Prep - 3 sessions are now ready for v3 /delegate and /validate iteration. - Finish rough implementation this week and begin testing. - Start rolling out to the 4 router endpoints (Corgent Bardiel) once initial tests pass. 🔹 Privacy Feature 1.0 – Regression Testing - Continue regression testing across privacy flows. - Focus on stabilizing session-level encryption paths. 🔹 Privacy Feature 1.0 – Scope Testing (Task-Level) - Run deeper testing on task-level encryption (newly rolled out). - Close remaining dashboard/UI gaps for task-scope opt-in flows. 🔹 Offchain v3 Testing (Dedicated Ephemeral) - Both dedicated-node and ephemeral-node support are now available. - Focus this week on: - regression testing - validating v3 offchain flows across both node types This week is about supporting Phase #3 while moving v3 /delegate /validate into real testing, and continuing to harden privacy offchain flows across the full system. #Cortensor #Testnet #Phase3 #AIInfra #DePIN #Corgent #Bardiel #Delegate #Validate #PrivateAI #L3