npm publish

[Nana-EC]

Problem

Currently we've versioned the repo however other consumers of the precompile functions are forced to copy contracts and compile themselves. This results in inconsistency of the details of the contracts and ads extra work on the consumers

Solution

Publish npm versions of the repo along with releases. We should also support deployment of alpha releases.

Alternatives

No response

[app-matt]

💯 Would definitely love to see an npm package being published for easier use of the SC precompiles!

[acuarica]

In addition to publish the npm package, we should explore how Foundry users can consume the precompile functions.

Foundry uses git submodules to consume dependencies https://book.getfoundry.sh/projects/dependencies.

As an example, solmate https://github.com/transmissions11/solmate allows both Hardhat and Foundry users to consume their contracts.

[Nana-EC]

We should have separate packages for

• https://github.com/hashgraph/hedera-smart-contracts/tree/main/contracts/system-contracts (should include ABI files)
• https://github.com/hashgraph/hedera-smart-contracts/tree/main/system-contract-dapp-playground

This will allow for other repos to more easily consume the contracts e.g. foundry example as noted above by @acuarica