Gm! A friendly reminder that you have until the 11th of December to complete your V2 claim as-long as you’re eligible! Some people that have had problems claiming are being worked on and will be sorted out. Please only use official links to claim: cloudverse.opsec.computer

Claim deadline update: Tomorrow at 3pm UTC the claiming portal will be disabled! (11th December 2024, 3pm UTC) Any issues that have been made to our mods in our Telegram will be sorted out as long as you have provided all required documentation to prove you’re eligible.

IMPORTANT NEWS: We are now going to start our staging servers migration process for OneSec v2 During this time OneSec v1 may experience issues, apologies in advance for service disruption. We will be going live after this migration process. Will announce a more accurate ETA

The Claim Deadline has now officially closed! 33% of the supply has been unclaimed! (Give or take a couple % on users who had issues and will be resolved) Claiming of OpSec V2 has now been disabled, anyone that raised an issue with our mods will be sorted. Now, the window

With OneSec v2 closing in, our Code-bot is keeping our Telegram community up-to-date with all new code being added/changed for OneSec v2! Follow in our Telegram; t.me/OpSecCLoud The time to call for developers to test and for whom want hosting is around the corner! -

We’re gearing up ready to launch our OneSec v2 beta, if you’re in our Telegram, you’ll have seen our GitHub activity surge! As we move into this "beta" phase, we're focused on gathering valuable feedback from developers testing the platform. This feedback will be crucial before

That’s a wrap for 2024! 🎉 Happy New Year everyone and thanks to everyone for your continued support of OpSec. It’s been a year full of ups and downs but we’re extremely excited for what’s coming in 2025! We hope you all enjoyed your holidays and spent time with family,

Important update regarding January 20th airdrop window:🚨 We’ve decided to extend the window till February 28th! This decision has been made to allow us to push OneSec V2 out and get marketing done whilst this event continues to run on in the background for you and any new

Development update for OneSec v2: • All testing for OneSec v2 done • Dev environment moved to staging (last stage) • Staging tests are complete Next: • Final internal check before we roll out together with marketing • Launch will be announced on X and Telegram - End

Burn complete! 🔥 1.1% of the $OPSEC supply has now officially been removed from the circulating supply. This approximately equates to $103,000 at the time of the burn. This is just the start for our burn journey. More to come! Burn receipt: etherscan.io/tx/0x97ea6fbd8…

The stage is set. We have our flagship product on the verge of launch this month. But, before we do, let’s take a dive into the comparison between OneSec and the newly built OneSec V2. 👇 ONESEC FEATURE LIST V1: - Deploy to IPFS - Assign Onesec subdomains - Wallet Auth

OpSec Powers Agentic Ethereum: ETHGlobal $5,000 prize pool for teams that push boundaries. Build self-healing, autonomous apps using OneSec’s zero-config hosting—deploy via GitHub, auto-detect any stack (Svelte, Next.js, etc.), and prove your app’s resilience by hosting ≥90%

We wanted to take a moment to express our appreciation for our community and the ongoing support you have provided. We’ve faced some setbacks, but we’ve been here for over a year, battling through tough times while consistently developing and ensuring that we deliver on our

A good start for us. Developers have jumped on and are using OneSec V2, just as we hoped for! We just deployed our first site: genesis.opsec.run This is just the start. Open for all devs. Free for everyone. Code like it’s 2025, deploy like it’s the apocalypse.

If you’re a developer and you want to provide feedback in a safe and awesome environment regarding OneSec V2, join our only official Dev Room - t.me/+-ljRF52FnRcyM… Feel free to leave all your feedback in there and give us as much information as possible on anything and

OneSec V2 Dev Update: - fixed responsive ui issues - github connectivity issues and username (cosmetic) - fixed react template bug - fixed more deployment bugs - small changes to text and ui

User feedback has been very helpful and positive in response to OneSec V2. Through users in our TG group providing on going feedback, and hackers from the ETH Global Hackathon. A development update has been pushed through with the following fixes: - All known repo bugs

Important Update: Airdrop Window Now Closed 🚨 The extended airdrop window for the January 20th event has officially closed as of February 28th. Thank you to everyone who participated! Within March, we’ll be distributing the 6.6% supply to our holders from the snapshot date

OpSec v2 isn’t going anywhere, our developers have been working tirelessly over the past few months to build the future of OpSec v2. With the launch of OneSec v2, we’ve proven we can deliver a successful product, and the overwhelming positive feedback we’ve received speaks for

The reason why OneSec v2 will be a massive succes: - Unmatched Scalability: Built on IPFS, it scales seamlessly as your app grows, no bottlenecks, no limits. - Enhanced Control: Wallet auth and customizable subdomains put you in the driver’s seat. - Resilient Performance: