arufa-research / junokit

Junokit is a development framework for building juno contracts. The aim of the project is to make juno contracts development process simple, efficient and scalable.

Junokit

Junokit is a development framework for building juno contracts. The aim of the project is to make juno contracts development process simple, efficient and scalable. User can focus on logic of juno contract and not much about further steps in development. It facilitates features such as initiating project repo from contract templates, easy compilation of contracts, deployment, Interacting with contracts using schema and contract testing framework.

Requirements

The minimum packages/requirements are as follows:

• Node 14+
• Yarn v1.22+ or NPM `v6.0+**
• Connection to an Juno node.

Install junokit

Installation from released version

To install junokit globally in your system you can use:

• Using Yarn: yarn global add junokit
• Using NPM: npm install -g junokit

Installation from master.

The master branch corresponds to the latest version.

To use junokit on your system, follow the steps below:

$ git clone https://github.com/arufa-research/junokit.git
$ cd junokit
$ yarn install
$ yarn build
$ cd packages/junokit
$ yarn link
$ chmod +x $HOME/.yarn/bin/junokit

Install dependencies

Setup Rust compiler

$ cd infrastructure
$ make setup-rust

Follow our infrastructure README for instructions how to setup a private network.

Usage

Initialize a project

$ junokit init <project-name>

This will create a directory inside current directory with boiler-plate code. The contracts/ directory has all the rust files for the contract logic. scripts/ directory contains .js scripts that user can write according to the use case, a sample script has been added to give some understanding of how a user script should look like. test/ directory contains .js scripts to run tests for the deployed contracts.

Listing Tasks

To see the possible tasks (commands) that are available, go to project's folder.

$ junokit

This is the list of built-in tasks. This is your starting point to find out what tasks are available to run.

Compile the project

To compile the contracts, Go to project directory:

$ cd <project-name>
$ junokit compile

This command will generate compiled .wasm files in artifacts/contracts/ dir and schema .json files in artifacts/schema/ dir.

Cleanup Artifacts

To clear artifacts data, use

$ junokit clean

This will remove the artifacts directory completely. To clean artifacts for only one contract, use

$ junokit clean <contract-name>

This will remove specific files related to that contract.

Running user scripts

User scripts are a way to define the flow of interacting with contracts on some network in form of a script. These scripts can be used to deploy a contract, query/transact with the contract.A sample script scripts/sample-script.js is available in the boilerplate.

Run tests

$ yarn run test

License

This project is forked from hardhat, and just base on the hardhat-core part then modify it under MIT license.

Thanks

hardhat - Hardhat is a development environment to compile, deploy, test, and debug your Ethereum software. Get Solidity stack traces & console.log.

junokit's Issues

Only init and deploy working with ujuno on mainnet and not execute msg

Recheck this

Junokit Run scripts error

When running the command:
junokit run scripts/sample-script.ts --network testnet

The code returns the following errors:

Could not find a declaration file for module 'junokit'. <Path of junokit index.js> Could not find a declaration file for module 'junokit'

Try npm i --save-dev @types/junokit if it exists or add a new declaration (.d.ts) file containing declare module 'junokit';`

sample-project/artifacts/typescript_schema/Counter.ts (41,17): Property 'queryMsg' does not exist on type 'CounterQueryContract'.

sample-project/artifacts/typescript_schema/Counter.ts (91,23): Property 'executeMsg' does not exist on type 'CounterContract'.

sample-project/artifacts/typescript_schema/Counter.ts (110,23): Property 'executeMsg' does not exist on type 'CounterContract'.

Add docs for plugin system

Importing Coin from cosmjs conflicts with local Coin

If there is Coin struct in a given contract, such as cw-core, the the generated typescript_schema/ has definition conflict of Coin.

Auto recompile ts when running scripts/tests using junokit command

Updated tests for wasm-ast-types package

Add tests for creating TS Contract objects (extends Contract class) for sample-project

Have a linter in sample-project and templates repo

Checks for ts files in scripts/ and test/ directories. These checks can include variable case, line length etc. Adding eslint should be enough.

cargo.toml file takes local path

When creating a junokit project the cargo.toml created in contracts use local paths from cw-controller,cw-storage-plus,cw20. Junokit compile hence does not work, removing the local paths from the cargo.toml file lets the contracts compile. Here's how the code looks:

cw-controllers = { version = "0.13.2" }
cw-storage-plus = { version = "0.13.2" }
cw20 = { version = "0.13.2" }

Improve the migration flow

1. Current flow is, clear the checkpoint, deploy new codeId, add manually the contract address to checkpoint, run the migrate step.
2. The manual steps should be automated.
3. The scripts need not be commented out through the process.
4. The contracts version and migration history should be stored in the checkpoints.
5. Migration script should have cleaner structure.

Fix the schema parsing that has been fixed in Polar

arufa-research/polar#93

Handle Cw20ExecuteMsg in wasm-ast-typescript

Add support for mainnet fork

Add support for deploying multiple instances of same contract