OpSec

$OPSEC

Anyone Hodling OpSec!! The deadline for transferring your V1 tokens to get V2 tokens is coming in a few days.

Official notice from OpSec TG:

Dear $OPSEC Community,

A few important updates about the $OPSEC V2 relaunch. Our team has been working tirelessly to ensure a smooth transition and to bring new benefits to our holders.

Key Updates:

External V2 Contract Audit This Week:

The new token contract is finalised and will undergo security audits by Hacken starting Wednesday. We expect the audits to be completed by Friday, allowing us to proceed with the relaunch shortly after.

Enhanced Features:

The new contract will feature 0 buy and sell tax, increased liquidity, and improved security measures. These enhancements are designed to provide a better experience and greater value for all $OPSEC holders.

Token Migration Deadline for DEX & CEX holders 26/07/24

For those using DEX platforms (Trust Wallet, MetaMask, Uniswap, Ledger, Trezor, etc..), please send your V1 tokens to the official V2 recovery address: 0x362538c16a2868038AE72B608c080B6433f979C9 by 26/07/24.

For CEX platform users (BingX, CoinEx), please await further instructions. We are coordinating with these exchanges to ensure a seamless transition.

Practically: OpSec sends the V2 tokens and CEX's send V1 back.

Distribution Plan:

Calculations and holders for V2 have been finalised. After thorough discussions, we have decided on a claim-based distribution method. This approach offers several advantages:

Reduces gas fees for the team, allowing us to reinvest those funds into the community. ⁃ Minimizes the risk of exploits and scams.
Spreads out trading pressure, cascading token buy / sell orders.
An eligibility form will be posted on CloudVerse, allowing users to check their claim status and ensure they receive their V2 tokens securely.

CAUTION: We don't do airdrops!

Recap: Action Needed

DEX Users: Send V1 tokens to the official V2 recovery address.
CEX Users: No further actions needed. Your CEX will take care of the V2 Migration.
Community Members: Stay engaged, spread the word, and help us build momentum.

We appreciate your continued support and patience as we finalise these crucial steps. The team is committed to transparency and security, and we will continue to provide regular updates. Thank you for being a part of the $OPSEC community and we look forward to executing V2 swiftly for everyone.

Follow only official instructions and channels for all $OPSEC-related activities.

Official links:

https://twitter.com/OpSecCloud https://opsec.computer/ https://t.me/OpSecCloud https://discord.gg/opseccloud

End of post, beware of scammers - Show Less