Khola | OpSec

⚡️Crypto Entrepreneur | Web3 developer | #AI #Web3 | Moderator @OpSecCloud. DM’s open

[OpSec @OpSecCloud]

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!

[OpSec @OpSecCloud]

Within the next couple of weeks, we’ll be looking to bring some developers into our testing phase of OneSec v2.

It’ll give an understanding from the developers point of view the scope to which this product is aiming for, and the fun part will be to hear all of the feedback from them.

So, if you are a developer or have experience within the law of code, it won’t be long before we call some of you to arms!

On estimate we would say OneSec v2 is about 20x the codebase of Cloudverse.

We’re proud in what we’re building and believe in its success to which it can achieve.

- End of post, beware of malicious links in the comments!

[OpSec @OpSecCloud]

$OPSEC V2 has now been updated on @coingecko

https://t.co/KiBM1A7jik

- End of post, be careful in the comments!

[OpSec @OpSecCloud]

Important Reminder: Focus on V2 Only!

This is a friendly reminder that we are no longer associated with V1. Please ensure that you check the CA is correct before trading.

V2 CA: 0x8be8c50e7d7acff6084899e71a6db085ff7134c8

We are in the process of updating CoinGecko (CG) and CoinMarketCap (CMC) to reflect this change, and all information will be replaced with the correct, up-to-date details regarding v2.

Thank you for your support!

- End of post, any links or comments below are NOT associated with us, be careful!

[OpSec @OpSecCloud]

Demo #2

OneSec v2: Deployments

Once you’ve deployed your webapp through our platform, all future continuous updates will be handled seamlessly.

- Change code
- Commit
- Git push

Don’t worry about anything else, our webhooks will handle all the nitty gritty for building and deployment of new IPFS updates including any DNS / ENS changes required.

Furthermore, you can modify which hooks you want to have in place and also see you’re build process live via the OneSec platform.

Continuous integration has never been easier for web3.

You can now spend more time writing code than ever before!

[OpSec @OpSecCloud]

$OPSEC V2:

CA has been renounced:

https://t.co/Ja8BlmWIfs

CMC/CG have been updated our side - Please wait for it to update their end.

We have also sent to Dexscreener to add a migration status for V1 which provides links and information for anyone to easily access V2.

A new demo with a technical summary will be shown tomorrow for OneSec v2. (Monday)

[OpSec @OpSecCloud]

Our liquidity is now locked.

Please see the transaction below:

https://t.co/LhtHDduyEp

[OpSec @OpSecCloud]

A quick update regarding BingX with v2:

We have spoken with them and a final decision should come on Monday about a set date to begin trading.

For users who had previously had v1 on BingX, if you’re eligible you’ll have v2 tokens distributed to you. But for now, please wait until they get back to us on a final timeframe.

Thank you for the support.

[OpSec @OpSecCloud]

A backstory to how we started to the future of OpSec:

OpSec was founded by some developers and marketers who were within the core team and I was onboard for management. OpSec started just as an idea which turned into whole foundation over multiple phases. It started as an idea with products poorly developed, originally outsourced the project and we didn't have a dedicated dev team back then. Those things caught attention of some eyes and they asked questions about it, fudded the project, attacked our community and tried to totally destroy it. We have been transparent about it always. We have accepted our mistakes and moved on. We have strengthened our development team over the time, upgraded our marketing, management aspects as well, now we’re at a strong position within the team having quality developers full time with us on building our ecosystem, head dev being Peter. Team reformations should never mean anything else, there are always going to be people who care about OpSec and want to help make it thrive.

Going forward:
- We will appoint new CEO of the project who will lead operations with having authority over spending funds, taking decisions for marketing and development, and I will do my part aswell like I had done with v1.
- Multisig are being created for team to access and utilise funds.
- We are making the development process more transparent by making our products open source and by having our public github tracker bot which will give transparent code updates regularly and automatically.
- We are in talks with new marketers and agencies to help with marketing to get good PR and share the vision with new audience.

It may take some time to build our way back up, but what we achieved with v1 is only a small fraction of what can be achieved with v2. Slow and steady, before the growth trajectory sets in and we have our comeback story.

Our next post will be our OneSec v2 demo showcasing our web infrastructure product in action!

[OpSec @OpSecCloud]

🚀 Just submitted a website and Logo update request to [Opsec] through @coinmarketcap!

new website: https://t.co/3zI8BB436B

CMC link: https://t.co/X1JHZsvavv

new logo:

[OpSec @OpSecCloud]

🚀 Just submitted a contract address update request to [Opsec] through @CoinGecko!

🔗 [Contract address update ]

New contract address: 0x8be8c50e7d7acff6084899e71a6db085ff7134c8

[OpSec @OpSecCloud]

🚀 Just submitted a website update request to [Opsec] through @CoinGecko!

🔗 [website update ]

New website: https://t.co/3zI8BB436B

[OpSec @OpSecCloud]

🚀 Just submitted a Logo update request to [Opsec] through @CoinGecko!

🔗 [Logo update]

[OpSec @OpSecCloud]

Developer team update:

We have now added our GitHub bot into our Telegram - All 4 GitHub code repositories added for OneSec v2.

What does this do?

Whenever we push any changes to our code, it will show you an update. This is part of increasing transparency on our development work.

What is OneSec?

A decentralized cloud hosting platform which uses IPFS and ENS (along with custom domains and analytics) for one-click-deployment of dapps.

What's next?

A first look at a demo demonstrating OneSec in action this week. Then once we finalize OneSec v2 for rollout, we will fully open-source our codebase. And after that, we will fully open-source Cloudverse also.

On a side note, Cloudverse itself will also be getting new upgrades but more on that soon.

[OpSec @OpSecCloud]

To show the core team is still here and that we have control over all funds related to OpSec V2, we’re initiating a 100k buyback on the chart.

Please see the transaction below:

https://t.co/6nSPJm2nbh

https://t.co/bdbyaU1qGC

https://t.co/pHmuTMi3rW

Following this we’re looking to appoint a new CEO for OpSec V2, so stay tuned for that!

[OpSec @OpSecCloud]

We are aware of the statement made by our former CEO and are internally assessing the situation:

- We have not abandoned the project and don’t intend to by any means.

- Our plan was to launch an update video to OneSec V2 showcasing a high end product that pushes the boundaries of web infrastructure.

- The core developer team have not left the project.

We had hoped something like this would have been talked through internally first as a team to come to an agreement or resolution on the matter.

We know it’s not been easy but we’re still here and will continue to be.

Just a reminder that we have relaunched at 0/0 tax, with heavier funding from V1, a claiming portal which works based on your eligibility within a snapshot date across 30,000+ holders, cex tokens back in action (Coinex, waiting on others) and OneSec V2 which is a huge win for web infrastructure across the board.

We’ll push to get the demo out ASAP.

We will also try to give you timely updates through the day if needed as we find a possible way forward.

[OpSec @OpSecCloud]

Dear CoinEx users,

According to the arrangement in the "CoinEx Will Support OPSEC Smart Contract Swap", CoinEx has completed OPSEC smart contract swap, the related services for OPSEC will resume at 10:30 Nov 13, 2024 (UTC). The details are as follows:

OPSEC service
1. Deposit: 10:30 on Nov 13 (UTC)
2. Withdrawal: 10:30 on Nov 13 (UTC)
3. Trading pair: OPSEC/USDT
4. Opening method: Call Auction
    a. Call Auction
        10:30-10:35 Nov 13 (UTC)
        Orders can be placed and canceled
        10:35-10:40 Nov 13 (UTC)
        Orders can be placed but cannot be canceled
    b. Trading
        10:40 Nov 13 (UTC)
5. Service support: OPSEC/USDT supports AMM, Spot Grid, and Auto-Invest Plan.

New smart contract address
OPSEC (ERC20): 0x8be8c50e7D7aCFf6084899e71a6Db085fF7134C8

[OpSec @OpSecCloud]

With the new token now live, the next phase lies ahead – and it has the potential to bring even more attention and growth to OpSec. The groundwork is ready, and we’re at a point where the marketing campaign will play a critical role in sharing our vision with a broader audience once everything has gone smoothly.

Our founder has been a key figure in bringing this vision to life, and it’s thanks to his and the teams commitment that we’re standing where we are now. As we look toward the future, we're all ready for him to ignite the next move– one that will bring new wave of visibility to this project.

Later this week we will begin sharing technical updates, starting with OneSec V2. A live demo of it in use, and we can’t emphasise enough that OneSec V2 is a game changer for web infrastructure.

Regarding your tokens held on a cex, we ensure you that they are working on trading going live. If you’re eligible for V2 tokens then you’ll receive them and once we have confirmation on trading times we’ll update accordingly!

Thank you all once again for your patience and support. This community’s strength is its greatest asset, and together, we’re ready to see what’s possible in the next phase.

- End of post, beware of scammers!

[OpSec @OpSecCloud]

$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!

[OpSec @OpSecCloud]

The Countdown is On!

Approximately 50 million $OPSEC V2 tokens have already been claimed and are locked and loaded for today's big launch at 5PM UTC!

What's next?
First, we'll be adding liquidity, followed by enabling trading at 5PM UTC. This is it, the beast is back and we’re ready to make waves in the market!

Get ready for the action, set your alarms, and let’s make today unforgettable! The $OPSEC V2 revolution starts NOW!