You are viewing a single comment's thread from:

RE: VSC Proposal - Interim - Bring Smart Contracts to Hive

in #vsc6 months ago (edited)

simplest logic
3-speak starting second layer 2 network. 3 proposals for spk network, 2 L2 networks to run it.
I wonder what happened to peerplays, @theycallmedan don't you think people play you sometimes?
I guess if this network will succeed spk is going to drop dlux and use this one
then other proposal for dlux is pure waste of money for HIVE?
Didn't look up the code, it could be much worse if it's just fork of their previous work(I guess dlux in this case?)
It's weird enough already looking by people building together on one network to start another network eventually...

That's from someone who is really interested in any L2 on hive, bridges, contracts and all that. I think you ignore some things on very basic level that's why overall it ends with fails streak, but I know nothing about L2 networks on HIVE.

Sort:  

Please keep in mind VSC is a completely separate project from SPK/DLux. VSC is being built completely from the ground up and no such forking has occurred. We are building VSC to be a powerful smart contract core for all HIVE DAPPs not just SPK, or any of the like. In comparison, Dlux is primarily a project specific L2 network, whereas VSC is meant to be a hive engine replacement and successor. The intent here is to build technology anyone can use for NFTs, tokens, airdrops, backends, wrapping, etc, and make that as open and freely available as possible plus provide sophisticated tools to tackle onboarding and scalability.

Everything is public on our github repo: https://github.com/vsc-eco/vsc-node

Feel free to ask me any further questions, I'd be happy to answer.