Little or no consistency in toolkits and packages available on Secret network

Hi, devs of Secret network. I’ve recently been looking to implement a flex-multisig contract but came across a severe issue. Firstly, it’s not implemented by anyone. Even if the code works properly, there’s no guarantee that the code will work without any problems.

Secondly, Cw-plus is a standard used by most blockchains across the cosmos ecosystem, but we don’t have that on the secret network. We have a secret toolkit that is always slightly different than CW-plus. It makes it very difficult for a dev to quickly onboard SN without changing much of their code and vice versa.

Several organizations are working on secret network that are using their toolings.
Example:

  1. Shade protocol’s version of CW-PLUS: securesecrets/CW-plus: Production Quality contracts under open source licenses (GitHub.com).
    But the contracts are not maintained(Obviously, they have no duty whatsoever towards this)

  2. Scrt labs’ version of CW-PLUS: scrtlabs/CW-plus: Production Quality contracts under open source licenses (GitHub.com).
    Have a lot of errors and does not compile.

The summary of all these paragraphs is that we need one single repository either maintained by Scrt labs or the community. Repo should be a fork of CW-PLUS. We can add new packages as we go, but at minimum, we need to have secret networks version of CW-plus up and running + maintained.

5 Likes

Agreed. This is pretty necessary, and the lack of crossover causes quite a bit of difficulty for people familiar with cosmwasm already to build here. I really think it would be great if assaf could complete those CW-Plus tools, but if he’s unable to, we can make it into dev committee bounties to get them all into working condition possibly.

2 Likes

I agree that it would be beneficial to have the CW-plus contracts up to date for Secret Network. These are boilerplate contracts for cosmwasm chains and the fact that we can’t work with them without compile errors on Secret Network probably sets the bar of entry too high for most devs coming into the ecosystem who want working contracts to start with

2 Likes

@assafmo any comments pls