You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Inco is using a private monorepo for internal needs
During a discussion @silasdavis mentioned this repo can transition into the main source for external integrators tooling.
I think it indeed makes sense, to propose here alongside the confidential ERC20 reference implementation, the future others reference standard implementations and standards, and confidential smart contract tooling (what's needed to code a dapp on inco, not bothering the dev with the protocol side).
The github issues can also function as confidential standard improvement proposals, similar to Ethereum's ERCs.
This would involve organizing this repo in packages, published to npm, one per standard implem.
Arguably we can use a new repo for this base.
This repo could still be forked to serve as new dapp project template (or could be extracted in another repo).
Opening the issue for discussion
The text was updated successfully, but these errors were encountered:
Inco is using a private monorepo for internal needs
During a discussion @silasdavis mentioned this repo can transition into the main source for external integrators tooling.
I think it indeed makes sense, to propose here alongside the confidential ERC20 reference implementation, the future others reference standard implementations and standards, and confidential smart contract tooling (what's needed to code a dapp on inco, not bothering the dev with the protocol side).
The github issues can also function as confidential standard improvement proposals, similar to Ethereum's ERCs.
This would involve organizing this repo in packages, published to npm, one per standard implem.
Arguably we can use a new repo for this base.
This repo could still be forked to serve as new dapp project template (or could be extracted in another repo).
Opening the issue for discussion
The text was updated successfully, but these errors were encountered: