Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question about Namespace contracts #1692

Open
sanderlooijenga opened this issue Jul 10, 2023 · 2 comments
Open

Question about Namespace contracts #1692

sanderlooijenga opened this issue Jul 10, 2023 · 2 comments

Comments

@sanderlooijenga
Copy link

Which of the contracts is the latest (looking at https://github.com/kadena-io/chainweb-node/tree/master/pact/namespaces)?

Maybe a README could be added?

@edmundnoble
Copy link
Contributor

Hullo,

The latest is always ns.pact at the top level, with historical versions of the contract in subfolders. I can see about documenting that when we give coin the same treatment.

@LindaOrtega
Copy link
Contributor

LindaOrtega commented Sep 20, 2023

Would it be possible to follow this same convention (top level is always the most up to date) for the rest of the contracts?

It might not be so easy to do with the coin contract though:
The top level version of coin.pact was updated 10 months ago. But v5 was updated last month. I was surprised that the top level version of coin.repl was updated last month along with the v5 version.
And inside v5 are a couple of contracts, like coin-v5-install.pact, which seem to override coin.pact?
A README could help though.

Screenshot 2023-09-20 at 11 25 04 AM Screenshot 2023-09-20 at 11 24 58 AM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants