El_Cano
10.3K posts


🛠️ DevLog – Follow-Up: Rough Offchain Storage Changes Moving Into Code Follow-up on the configurable offchain storage idea: we’ve now gone a bit beyond pure design and have been playing with rough mock code / rough implementation paths around it. 🔹 What’s happening now - We’ve already explored the main router/miner code paths enough to have a workable rough design. - Based on that, we’ll try to start adding some of these changes today and test them locally while the current privacy tests are still ongoing. 🔹 What this work is about - Letting offchain payload storage become more router/operator configurable instead of assuming one default storage path. - Keeping the current default behavior as fallback, while making room for operator-specific storage config later. 🔹 Why this matters - This sits closely next to the broader privacy/data-ownership direction: - encryption is one side - where the encrypted data is stored is the other side - So while privacy tests continue, this becomes one of the next practical follow-up items to start shaping in code as well. Still rough and early, but the design is clear enough now that it makes sense to begin local experimentation. #Cortensor #DevLog #OffchainStorage #Privacy #EncryptedInference #DePIN


Monthly Node Rewards – March 2026 (Initial Batch Sent) We’ve just sent out the first round of $COR rewards to 20 active nodes, out of 39 eligible nodes, as part of our monthly node reward program. 🔹 Rewards will be distributed in batches 🔹 More batches rolling out over the next few days 🔹 Recognizing uptime, stability & contribution 💬 Join our Discord to set up a node or get involved: discord.gg/cortensor Thanks to all node operators pushing decentralized AI forward - it's $COR or nothing. #Cortensor #AI #DePIN #NodeRewards #COR





🛠️ DevLog – Rough Design for Configurable Offchain Data per Router We now have a rough design picture for making offchain data storage configurable per router/operator. 🔹 What’s clearer now - We’ve identified the main places that need to change in both the router and miner code paths so offchain payloads can use operator-specific storage instead of one default path. - This gives us a workable base for supporting per-router / per-operator offchain storage. 🔹 What we’re thinking through next - Edge cases and UX around configuration changes, for example: - what happens if the storage config changes later - what happens if the old storage path no longer exists or is no longer reachable - These are important because storage configuration becomes part of the real data lifecycle, not just a simple env toggle. 🔹 Current direction - For now, the storage config would live in env/config. - Longer term, similar to PrivacySettingData, some of this information could move on-chain in a more immutable form so session/storage behavior is easier to reason about. This is still rough design work, but at least we now have a clearer view of the code paths and the next design questions to solve. #Cortensor #DevLog #OffchainStorage #Privacy #EncryptedInference #DePIN





My new $TAO top signal is Wizz


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

Today, I have seen more “ $TAO is a scam” posts than I’ve ever seen before. Any time one of these people were asked to explain why it’s a scam, it was immediately clear they have no idea what $TAO is 2026 is going to be hilarious for the bookmarks I have saved

Buying the bottom is never easy, when i rebought $tao people were calling for $50-100 When sentiment is at its lowest, so is opportunity. now i'm up nearly 2x and the bounce has not even started

AI crypto projects showing real strength the past few weeks. Not holding all. Just watching closely. $TAO — leading the decentralized AI narrative $FET — AI agent infra, listed across all CEX and perps $AKT — solid risk/reward on AI infrastructure $VVV — decentralized private inference play $MOR — AI agent exposure, $VVV beta $PHA — pivoting hard to AI agent infra, top CEX listed $TIG — $TAO beta play on Base $ATH — GPU compute infrastructure $NOS — Solana infra play. High upside. High risk. Plus individual Bittensor subnets sitting underneath all of this. Worth studying.






