VeTools Milestone 2 and 3 Submission

[hazelcaus]

Milestone Submission

• PR Link: VeChain Grant Proposal -- VeTools (VeChain VSCode Toolkit) #151

All deliverables completed per agreement. Additionally, VeTools v1.0.7 is live on the VSCode Marketplace. Source code: https://github.com/hazelcaus/vetools

Additionally because of the delay between our previous milestone deliverable and now, we have decided to complete development of all milestones.

Further: the RPC node urls for Vechain network are incorrect and I've been unable to find proper EVM-compatible RPC Urls. As such, these are the only pending requirements. Would just need to make quick updates to these urls and release an update.

[hazelcaus]

@libotony @NecoSherry

[libotony]

Further: the RPC node urls for Vechain network are incorrect and I've been unable to find proper EVM-compatible RPC Urls. As such, these are the only pending requirements. Would just need to make quick updates to these urls and release an update.

VeChain is compatible with ethereum ecosystem at the EVM level, but not at the API level. In another word, VeChain doesn't have a ethereum like RPC interface, it has its own defined RESTful API.

Here is some useful links of tools use ethereum sdks in VeChain:

1. https://github.com/vechain/web3-providers-connex
2. https://github.com/vechain/hardhat-plugins
3. https://github.com/vechain/vechain-sdk-js

@hazelcaus

[libotony]

I started with a fresh new workspace as instructed in the extension documentation. I have encountered the following error when compiling the contracts.

vetools>>> 
> [email protected] compile
> hardhat compile

vetools>>> Error HH1: You are not inside a Hardhat project.
vetools>>> For more info go to https://hardhat.org/HH1 or run Hardhat with --show-stack-traces
vetools>>> 
vetools>>> Finished running command

[hazelcaus]

I started with a fresh new workspace as instructed in the extension documentation. I have encountered the following error when compiling the contracts.

vetools>>> 
> [email protected] compile
> hardhat compile

vetools>>> Error HH1: You are not inside a Hardhat project.
vetools>>> For more info go to https://hardhat.org/HH1 or run Hardhat with --show-stack-traces
vetools>>> 
vetools>>> Finished running command

@libotony I'm not able to reproduce your issue. Please see this video of me trying to achieve the same thing. I'm able to flawlessly create a new project and compile contracts successfully.

If it might help, please try creating a separate folder prior to selecting VeTools: New Project and then selecting that folder during the command execution

[hazelcaus]

Here's an updated link to the video @libotony

[libotony]

Here's an updated link to the video @libotony

Thanks for the video, the project I have created using [email protected] seems not having the file hardhat.config.ts

[hazelcaus]

Thank you for confirming @libotony. It turns out that VSCode didn't package the typescript files within the resources folder. As a result, the key files (including hardhat.config.ts) was missing. Should be fixed now in v1.0.9.

[hazelcaus]

@libotony were you able to get it to work?

[libotony]

Thank you for the update, I have tried the new version v1.0.9. Compile contract is working, but I have still have some issue during deploy:

• LocalNode seems to be a ganache instance, it has some difference from vechain's instance.
• Deploy to TestNet has an error hardhat.config.ts not found, after renaming the filename, it is telling H0061: Script scripts/deploy.ts doesn't exist
• Regarding the delivery files, please put milestones separately.

[hazelcaus]

thanks @libotony. We have fixed the deploy.ts issue -- there was an unpatched commit pending we didn't notice priorhand.

re: delivery files, we have already completed both milestones 2 and 3 and the PR reflects it as so. Imo, this would be better to parse and process and wrap up this grant proposal.

re: localNode is a ganache instance for testing because I wasn't able to get connex api to work via hardhat for some reason. Is there a technical forum/POC I can reach out to to fix this? I'll shortly describe the issue as a followup

[libotony]

re: delivery files, we have already completed both milestones 2 and 3 and the PR reflects it as so. Imo, this would be better to parse and process and wrap up this grant proposal.

We don't mind if you deliver 2 and 3 together, we suggest the milestone to be put into two different files as the process was described here https://github.com/vechain/grant-program/tree/master/milestone-delivery#milestone-delivery-process

[libotony]

re: localNode is a ganache instance for testing because I wasn't able to get connex api to work via hardhat for some reason. Is there a technical forum/POC I can reach out to to fix this? I'll shortly describe the issue as a followup

This might be an issue related to this comment:

VeChain is compatible with ethereum ecosystem at the EVM level, but not at the API level. In another word, VeChain doesn't have a ethereum like RPC interface, it has its own defined RESTful API.
Here is some useful links of tools use ethereum sdks in VeChain:
https://github.com/vechain/web3-providers-connex
https://github.com/vechain/hardhat-plugins
https://github.com/vechain/vechain-sdk-js

[hazelcaus]

Thanks @libotony. Will do so (separation of milestone delivery shortly).

wrt to running a Thor Solo node, I'm getting the following error (I have built Thor from source via the build instructions):

Is there a technical forum/POC I can reach out to to fix this?

Also: is there any resource from which I can download pre-built Thor nodes for various architectures? Ideally, we want to abstract this away as much as possible from the user, but if it's unavoidable, we can have the user build the Solo node async and then we can reference the binary within the extension

[libotony]

Thanks @libotony. Will do so (separation of milestone delivery shortly).

wrt to running a Thor Solo node, I'm getting the following error (I have built Thor from source via the build instructions):

Is there a technical forum/POC I can reach out to to fix this?

Also: is there any resource from which I can download pre-built Thor nodes for various architectures? Ideally, we want to abstract this away as much as possible from the user, but if it's unavoidable, we can have the user build the Solo node async and then we can reference the binary within the extension

With the same parameter, I can successfully launch the solo instance.

Also: is there any resource from which I can download pre-built Thor nodes for various architectures?

Sorry, currently we are not publishing binaries.