How many devs are working on VSC and who are they?
Myself plus two others (@platinium and @piyushjha), both new to hive from outside the ecosystem. Looking to hire another 1-2 devs.
In percentage how do you think custom json tx will be increased compared to right now?
It's unclear at the moment. There will be a very slight increase less than 1% for anchor blocks as custom_json. It's really going to be a matter of choice whether DAPPs decide whether transactions should go on chain or offchain. For non time critical operations it can stay offchain and causes no increase in on chain custom_json
In which language are you writing the core code?
Typescript/javascript
Do you think that L2 contracts have the same credibility and security as L1?
Within the smart contracts themselves there is no difference between L1 and L2 contracts. However, L2 smart contracts do not have the same ownership security of L1 contracts that a L1 system would provide. We use a multisig combined with governance structure to handle the onchain custody.
Don't you think that being at 3 projects at same time as dev is like playing to much instruments at same time?
Maybe, I'm doing the best I can to make it all work.
Do you agree that instead of excuses about complexity, being pragmatic, the real reason is that smart contracts on L1 is just for best ones on C++?
I'm not sure what you mean by the last part. Could you rephrase?
Forgetting complexity, do you agree that smart contracts on L1 is much better than any smart contract on L2?
For L1 custody yes, but it depends on the use case. L2 smart contracts can scale a lot better than L1 through scaling solutions. There is a lot more flexibility with what can be done offchain which can allow entirely new use cases not possible on chain.
If your second proposal is not approved what will you do?
TBD. I aim to continue working on the project for atleast another month or two after that.
Thanks for replying!
Are you using scripts from other sources or you've written everything from scratch?
What are the incentives to people run a node?
I mean, Blockchain was written in C++, smart contracts in C++ is hardest than in JavaScript, C++ have a bigger learning curve. Not even saying that performance it's bigger and memory control much better, which would mean lowest specifications for nodes. Anyone on team have C++ skills?
This means that if 2nd proposal is not funded there are changes of not be concluded? Or you pretend to finish no matter what?
Mostly from scratch
At the moment nothing, but later on that would HBD from transaction fees / staked HBD interest
The language choice does affect development. It's a lot faster to write JS code by far. Another big difference for us is there are 10x more web3 libraries in JS than C++. IPFS related libs, VMs, API libs, etc. All of it makes development time a lot less. I can understand C++ for the most part, but I haven't worked with it directly for a long time.
The goal is to release the testnet which will provide the barebones functions of what VSC aims to do. It will be online and operational for anyone to deploy on and start using to build applications on. However, that testnet might not have everything DAPPs want, and for sure won't have every we ultimately want to build, but it will definitely provide the basic functions of smart contracts.
One last question to you.
As far as I know, blocktrades and team pretend to implement smart contracts, I believe in the next 2 years.
From no smart contracts to 2 smart contracts, don't you think it's too much and someone is wasting time?
From my current knowledge it would a L2 approach as well, but with little to no hive direct interaction. At the moment from what I know I wouldn't say it would be very useable for DAPPs. There is a lot more to just bringing contracts to hive, like also making them scalable, providing onboarding onramps, etc. There is a lot more we are targeting that would be attractive to developers.