I understand the thesis, and I agree that privacy becoming an embedded infrastructure layer across RWA, DeFAI, DePIN and other applications could create continuous network usage. But this is still a thesis, not an answer to the token economics question.
For example, with Carrot, we need to know exactly how ROSE is required for ROFL usage, who pays for the computation, how much ROSE is consumed per workload, and whether that creates measurable demand, staking or burn pressure on the token.
The same applies to Privana, Midas, SemiLiquid and other integrations.
That’s why I’m specifically asking the Product/BD and technical teams for the actual mechanism and numbers. Ambassadors can explain the vision, but they cannot define or confirm the protocol’s economic model.
I’m not questioning the potential of the strategy. I’m asking the team to show how that potential translates into measurable value for ROSE.
Well said — you’re asking all the right questions.
I fully support everything you’ve raised and asked about today. These are important questions that deserve clear and transparent answers.
Thanks for laying this out so clearly, these are important questions, and you're right that the role of ROSE in this model is exactly what matters most to holders.
I'll just add honestly: as you noted yourself, the actual economic mechanics, how ROSE demand is created, consumption, any staking or burn dynamics, aren't something ambassadors or mods can define or confirm. That's protocol design, and I wouldn't want to give you a version that doesn't match what the team ships.
As Goose mentioned, a lot of this is tied to Privana V1, which is launching very soon, and how ROSE integrates into Privana is exactly what should become clearer as it rolls out. I know that isn't the fully satisfying answer you're after, but I'd rather point you to where the real detail will come from than speculate on mechanics that aren't finalized. 🌹
But that’s exactly why we need an Oasis team member here who actually knows their stuff, a developer, someone from BD, or anyone close to the project rather than mods copy-pasting the same tweets every day. It adds zero value, and after years of this, there is still no real, informed discussion in the Telegram
I appreciate the clarification 🤝
As a large investor studying the project, I would find it very useful to have one clear explanation of the new Oasis strategy, the role of ROSE and how the ecosystem is expected to create value going forward.
In particular, I think the team should clarify:
- What specific actions or services will require ROSE?
- How Privana usage is expected to create organic demand for ROSE
- Whether ROSE will be used for fees, collateral, staking, access or other functions
- Whether any mechanisms will create buy pressure, burns or permanent token locking
- How ROSE is connected to ROFL compute and what happens when external applications use Oasis infrastructure
- How projects such as Carrot, SemiLiquid, Midas, IO.net and other integrations will ultimately interact with ROSE
- Regarding the Midas Series A investment: what is the specific strategic benefit of this investment for Oasis Protocol and ROSE holders, beyond the potential financial return to the Foundation, and how does the team plan to translate Midas’s growth into actual Oasis network usage or ROSE demand?
- How usage across external ecosystems translates into value for Oasis and ROSE holders
- What role the Foundation and treasury will play in the new model
- What KPIs the team will use to measure whether the new strategy is actually succeeding
- And importantly, what is the go-to-market and marketing strategy for Privana and the new Oasis direction?
The last point is particularly important to me. There is currently a significant gap in marketing and public awareness around Privana, even with V1 approaching. A strong product still needs users, distribution and a clear narrative to succeed, and this requires marketing, which is currently missing.
I believe publishing this publicly (an article, X post, etc.) would be very positive for the project. It would give investors and developers a much clearer understanding of the strategy, reduce speculation and help the community communicate
Thank you for laying all of this out so clearly. I'll pass your suggestion along to the team, together with the specific points you've listed. I can't promise if or when something like that would be published, but I'll make sure the feedback is relayed. 🌹
Of course, small investors have exactly the same right to this information! I think transparency should be equally important for everyone.
As for what qualifies as a “large investor”, everyone probably has their own benchmark. In my case, I consider $200K+ allocations to promising projects to be a significant investment, so naturally I look at transparency and long-term value creation from that perspective.
Oasians, we need your help!
We’re collecting feedback on:
🔹 Rose App & Oasis Explorer
🔹 Mods & Support experience on Discord/Telegram
🔹 What you want better – product, docs, dev support & more!
Just fill out the form below, only takes a couple of minutes
CommuniTEE Feeeeedback :D
🎙 New Privacy Talks episode is out.
Your data is being fed into AI models without anyone asking. This one covers X's push to ditch its FTC privacy order, Siri running on Google Gemini after WWDC 2026, the "Web3 is dead" debate, GitHub Copilot's billing shock, and crypto's brutal month.
Plus a conspiracy corner theory that stuck with us: what if on-chain privacy was quietly cracked years ago?
🎧 YouTube → https://youtu.be/kBfrCkU1Yqw
🎧 Spotify → https://sptfy.in/ec79
🎧 X → https://x.com/MinnyTheRapper/status/2085378053459370169
Every AI agent you delegate to has a hidden trust problem: it runs on a server owned by someone else. Right now, most platforms ask you to rely on privacy policies and Terms of Service—essentially an honor system with better branding.
True security isn't policy; it's structural. By shifting from trust-based promises to cryptographic guarantees, confidential compute ensures operators cannot access your prompts, data, or model reasoning.
Read the full breakdown on X to see why the future of AI delegation relies on hardware-enforced privacy:
https://x.com/OasisProtocol/status/2082707772064551033
Ссылка click to show
Most Web3 projects build for crypto users. Diode builds for enterprises and regulated industries that need complete data control.
By leveraging Oasis for control plane privacy, Diode delivers three core layers:
Zero-Trust Networking: WireGuard-native infrastructure that connects servers, IoT devices, and remote teams without exposing data.
Encrypted Communication: Blockchain-defined "Zones" that function as a private, leak-proof alternative to Slack.
Private B2B AI: Safe LLM queries over internal data governed by Oasis-anchored access controls.
Read the full breakdown on how Diode uses Oasis to power enterprise privacy—including real-world cases like Clean Connect and Chevron:
https://oasis.net/blog/diode-private-infra-with-oasis
G
Ссылка click to show
The safest key is the one no single person or server actually holds.
Threshold cryptography splits a secret into multiple shares across different parties. Require 3 out of 5 shares to approve an action? Compromise one or two servers, and an attacker still gets zero access. It completely eliminates single points of failure, single-admin risks, and the need to "just trust the operator."
Read the full breakdown on X to see how splitting the secret replaces trust with structural security:
https://x.com/OasisProtocol/status/2081982998405382220