Nana Essilfie-Conduah

Potential approach - 1st - system contract interfaces only i.e. IHederaTokenService, IHRC719 etc - 2nd - low level wrapping contracts - once we've had some keen eyes on it to...

Thanks @maksimKrukovich for the ticket and context. We're in full agreement with you on the value and relevance of forking. It's just a bit tricky. For context most EVM tools...

Revisiting. Forking for contracts using non system contract logic should work fine. if there's an issue there let's explore what hardhat is doing. If it's system contract logic related then...

@ebadiere was this resolved or does it still need to be covered?

Hi @mamorales1 thanks for the ticket. Indeed it does seem to be a gap, we'll take a look and circle back here.

@MiroslavGatsanoga I think this can be closed. Thanks

@quiet-node had a suggestion to make the https://github.com/hashgraph/hedera-smart-contracts/tree/main/contracts/system-contracts stand out more. Move other items under a sub folder of say https://github.com/hashgraph/hedera-smart-contracts/tree/main/contracts/examples @Ferparishuertas agreed

Goal would be https://github.com/hashgraph/hedera-smart-contracts/tree/main/contracts/system-contracts would be the folder that is included in the npm package that developers can import and utilize. Examples under here should also be moved out to...

@acuarica suggested we consider a separate repo to highlight system contracts even more. There's potential to make usage with other tools easier. Q: Would this also be satisfied by a...

@david-bakin-sl checking but is this not captured by the contents of https://github.com/hashgraph/hedera-smart-contracts/tree/main/contracts-abi/contracts/system-contracts What's an example of a consensus node API that isn't the user API? Agreed and the intent should...