Connex :: Developers Insights

[darrenvechain]

Arrange a meeting with Darren to get his insights on Connex as he is one of the main users from a Foundation perspective.

• Promise which resolves at the next block ??
• Handy util functions ??

Things to consider:

• DON'T use Connex as inspiration, it has some things it does well, and some things it does poorly
• Connex repo description: Connex is the mono-repo contains libraries to help build dApps for VeChain.
• IMO we need a client that can be used across both the frontend and the backend
• Separate wallet clients and Thor clients. In connex, the Sync2 wallets are baked into the library, which makes it quite difficult to extend. We should allow dApps to configure whatever wallets they want, with ease

dApp considerations:

• IMO our hardhat plugins should be the point of reference for dApp devs. Hardhat is the go-to dApp tool, which makes contract deployment and interaction very simple, so we should make libraries that are easy to integrate with
• Make it easy to do delegation and multiple clauses for our hardhat plugin

[nwbrettski]

As part of a wider developer discussion it has been suggested that we pivot aware from connex and instead focus on being more aligned with Hardhat and Foundry.

A follow on task is to identify a list of functions from both Hardhat and Foundry to identify what functionality the vechain-sdk should be able to provide.