LO KO | LCM | OpSec

@ColleIda The claim time is over , you should have received your new token automatically if you import the right contract address @ColleIda

@OpSecCloud Hello i want to claim my tokens

Introducing OneSec v2: The only platform you will need to deploy dapps on the decentralized web. - Connect your GitHub - Choose your repository - Select your web framework and click deploy It’s that easy! We’ll handle IPFS hosting, ENS assignment (DNS if you prefer), packagers and completely automate your CI/CD pipeline. We’ll also show you analytics, where your visitors are from and what’s popular. For debugging, we’ll show you server side logs as well. All this comes at cost cheaper than any current web2 offering AND we have free tiers! Here’s a demo of us deploying a starter app end to end in under 2 minutes: - End of post, beware of scammers!

@technibody @technibody Did you send your old $Opsec token to the recovery address before snapshot was taken?

@OpSecCloud I send my opsec on thrust wallet , i can see thé transaction on the blockchain but nothing on my wallet why? And what i have to do?

$OPSEC V2 Trading Now LIVE! After months of working around the clock, the wait is finally over and the moment we’ve all been waiting for is finally here! The beast has awoken from his slumber and $OPSEC V2 trading is now officially enabled, marking the start of something HUGE!!!! We have a bit of a surprise for you, because of your loyalty and the fact Eth is pumping, we are now launching at 55M MC instead of the 50M we promised. Whatever you do at this point is entirely up to you, but you don’t want to miss what is coming! You’ve been warned, you know $OPSEC was the first mover and what this team is capable of because at $55M MC, we are way down on our potential! OpSec V2 Official CA - 0x8be8c50e7D7aCFf6084899e71a6Db085fF7134C8 -End of post, beware of scammers!

@ts3622850 @ts3622850 Did you miss sending your old V1 $Opsec tokens to the recovery address before the snapshot for the new tokens was taken?

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 soon. - End of post, beware of malicious links in the comments below!

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 we roll out the fully-fledged web3 dApp hosting platform. Stay tuned for more updates! - End of post, beware of any malicious links in the comments below!

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! - End of post, beware of malicious links in the comments below!

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 has officially opened for your chance to gain an airdrop reward up until January 20th 2025. Simply put; A random snapshot will be taken, the larger your $OPSEC holdings, the higher your airdrop allocation will be. Those that sell any before the snapshot will have a 2x penalty, providing holders with better airdrops. 20% of unclaimed tokens will be airdropped post window end of 20th January. Thank you for all the support so far on the rebuilding of OpSec V2, we are only just warming up! - End of post, beware of malicious links in the comments below!

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. Official Telegram; t.me/OpSecCLoud From there, we will then enter the window for the random snapshot of $OPSEC holders to be taken. (Around 30% give or take after everyone is sorted will be left unclaimed) This will commence from 3pm UTC onwards up until 20th January 2025. Official claim website; cloudverse.opsec.computer On a small side note; We’re almost done with OneSec v2. - End of post, beware of malicious links in the comments below!

@evlaun64 @4everblues66 Did you send your old $Opsec token to the recovery address before snapshot was taken?

@OpSecCloud Never sent my V2 tokens after multiple complaints and following specific instructions posted on X

@itsme_kingsley @itsme_kingsley Did you send your old $Opsec token to the recovery address before snapshot for the new token was taken?

@OpSecCloud I have messaged you multiple Times trying to claim my v2 with no help. Please respond

@4everblues66 @4everblues66 You didn’t send your old $Opsec token to the recovery address before snapshot was taken.

@AzamImran7 @AzamImran7 What issues do you have claim your new $Opsec token.

@OpSecCloud Cant claim

@lukapericADA @lukapericADA You did not transfer your old token to the recovery address before snapshot was taken?

@OpSecCloud So your telling me, that if I just saw this, my old tokens are worthless???

@MoMoneyMofo1 @MoMoneyMofo1 When did that happen, and do you have the transaction Ids?

@OpSecCloud I need help from a Mod to air my case. I was given a claim number by someone posing as a rep of OpSec and they ended stealing from me. OpSec please honor this claim ticket and help me to migrate.

@JchapmanSD @JchapmanSD The portal to claim the new $Opsec token is closed , you have to manually claim directly from the contract for you to receive the new token.

@OpSecCloud I already sent my V1 tokens a few months back as instructed. How do I receive the V2 tokens now? Weren't they airdropped to our wallet?

@MoMoneyMofo1 @MoMoneyMofo1 If you send your old $opsec token to the recovery address, you will be able to claim the new token through the claim portal.

@OpSecCloud Is there anyone who actually successfully migrated thier tokens from V1 to V2? Please share

@releu1 @releu1 Did you send your old $Opsec token to the recovery address before snapshot was taken?

@OpSecCloud Hey, I missed to claim. Can I still do it?

@JuanJesusGarayT @JuanJesusGarayT El equipo anunció la fecha límite para presentar reclamaciones; ¿Por qué no reclamaste tu nuevo token $Opsec antes de que se cerrara el portal?

@OpSecCloud Todavía esperando el link oficial para poder reclamar los tokens que les envié a su Wallet

@ts3622850 @ts3622850 Import your ledger to a Dex wallet and import the new token address for your $Opsec to reflect if you claimed before deadline.

@ts3622850 @ts3622850 Did you send your old $opsec token to the recovery address before snapshot was taken?