It depends. If projects can migrate smart contracts/code from other chains without much overhead and use their existing tooling as well, then yes. Could work the reverse way as well, projects starting on VSC and then being able to migrate to another chain/their own chain later on.

Think of it like building with Lego versus custom blocks. With Lego (like EVM), you can rebuild, reuse parts, or plug into other sets easily. There's a whole ecosystem around it.

But with custom blocks (a custom framework), you're stuck. It might work well in one place, but if yo want to move or expand, you'll probably have to rebuild everything from scratch because nothing else is compatible.

So, ultimately, it’s about flexibility and not being locked in.

---

That said, there's one thing that makes me wonder:

> No, VSC uses the native Hive tokens for all transactions on the network. **We plan to launch a token once the project is self sustainable via a fair launch.**

Technologies can always be replaced or added under the same cryptocurrency. Meaning, Hive could add native EVM support to its codebase or spin up a separate EVM chain, running under the same cryptocurrency, HIVE. But having an L2 which is supposed to be an extension, then having its own cryptocurrency, where does that leave HIVE?

I'm sure it's all in good faith, it's simply important that the value flows back to HIVE.

I understand your concern, but it's a bit more nuanced than just "not believing".

Hive isn't just a technology. It's also a community, a cryptocurrency, and an ecosystem. All of that combined is what makes Hive what it is.

Like I mentioned to @meno - technologies can always be changed, replaced or added under the same cryptocurrency.

Take EOS as an example. They recently rebranded to [Vaulta](https://vaulta.com) and did a 1:1 token swap from $EOS to $A. New name, new token symbol, but the same stakeholders and community. One of their main value props now is Vaulta EVM. They have zero connection to Ethereum (ETH), the cryptocurrency, but they adopted the standard. Same cryptocurrency, multiple technologies underneath.

![image.png](https://files.peakd.com/file/peakd-hive/therealwolf/23tkmuyPd6NpFgSaqh8R9rpfm82mxCzg5WU8rRiXotWTxTvnz2jTZrLHMY1xsp8Bgb7nU.png)

I still believe in Hive. Pretty sure I said that twice in the video too :D. It's simply: as a developer, it’d be great to have Hive Native and Hive EVM side by side.

Thank you! The centralization is less of an issue on Hive Engine, due to their own consensus mechanism. What I wanted to highlight more is the reliability of apps built on a non-standard framework. That might not have come across clearly in the video, so I wanted to clarify.