WARNING!!! **Currently we think Redspot 0.1 framework is not suit for future requirements, thus we create a new repo redspot which based on a new framework and migrate all Redspot 0.1 features to a new project. **
**Redspot-v0.1 is not maintained any more, if you need to use redspot, please use this repo redspot. **
Redspot is named after Jupiter's Great Red Spot, which is also the largest DOT in the solar system. Redspot's target project is Truffle (https://github.com/trufflesuite/truffle) in Truffle Suite. Redspot is a development environment, testing framework and asset pipeline for pallet-contracts. Redspot is trying to let the development of ink! be projectized and simplify the testing and interacting with contracts.
In Redspot v0.1, we will finish：
- Can read a config file and generate a contract project's framework, including contract source and tests directories. Redspot's command can recognise the structure of the project and distinguish the corresponding file locations.
- Provide some simple commands to do the actions, such as "compile", "test" and "deploy".
- Connect with different RPCs of substrate nodes depending on a config, then do test, deployment, etc.
- Integrate polkadot.js for tests and connect with nodes.
This project is used for contracts developer, if developers want to deploy and test on a blockchain, we advice developer to use "jupiter" blockchain, which is a open testnet for substrate pallet-contracts. Better than that, jupiter also provide a develop type node, that could very easily for testing contracts.
Please refer to this for more information: https://github.com/patractlabs/jupiter
Riot Group for disscusion: https://app.element.io/#/room/#PatractLabsDev:matrix.org
- Get Started Immediately
- Install from template
- Directory tree
- Project config
- Compile contract
- Contect nodes
- Test contract
- Deploy contract
- config
- artifacts
- contractApi
- Q&A
$ npx redspot-new flipper(npx is a package runner tool that comes with npm 5.2+ and higher, it ensures that you always install the latest version)
Redspot will create a directory called flipper inside the current folder.
Once the installation is done, you can open your project folder:
$ cd flipperInside the newly created project, you can run some built-in commands:
Compile your contract into wasm
Test your contract
Migrate your contract
(It works only on substrate-rc6 and the latest version of ink!)
Redspot provides several contract templates: flipper, delegator , dns, erc20, erc721 , incrementer, multisig_plain. You can intall them like this:
$ npx redspot-new <app-name> --template <template-name>For instance: npx redspot-new erc20 --template erc20
The default contract template is flipper.
app-name/
|-.vscode/
|-launch.json
|-artifacts/
|- <would store compile contract artifacts, e.g. contracts abi(json) and wasm files>
|-migrations/
|-1_deploy_contracts.js
|-node_modules/
|- ...
|-tests/
|- <template-name>.test.js
|- Cargo.toml
|- lib.rs
|- package.json
|- redspot-config.js
-
The files generated by
yarn buildare inartifactsfolder by default. There are compile artifacts for contracts, like contract abi and wasm files. -
migrationskeepsmigratefiles which are called byyarn migrate. There are used for deploy contracts, Developer could modify those files and decide how to deploy contracts. -
testkeeps test files. There are used for test contracts. Currently we provide a objectified way to operate contracts, just like web3.js for Ethereum solidity contracts, developer could call for data or submit a contract call by invoke the functions or a contract object. -
lib.rsis your main contract code. Sub-contract code can be put in anywhere. (Please refer todelegatorcontract).Note: current ink! have not been stable, when ink! be stable, we would use a directory
contractsto keep you contract files and projects. -
redspot-config.jsis some default project config. Developer should modify this config file to suit develop environment- blockchain ip and port (endpoints).
- substrate blockchain "Extending types" for polkadot.js sdk
- key pairs for deploy and test.
You can set up your project config in redspot-config.js, here are the config settings in redspot-config.js:
module.exports = {
// Compilation output directory
outDir: './artifacts',
// Can add custom network name like: product, local
networks: {
// Network name
development: {
// types will be added to polkadot-js
types: {
// Address: "AccountId",
// LookupSource: "AccountId",
},
// The endpoint url must be websocket one
endpoints: ['ws://127.0.0.1:9944'],
// Default account settings
accounts: [
{
name: 'alice',
publicKey: '0xd43593c715fdd31c61141abd04a99fd6822c8558854ccde39a5684e7a56da27d',
secretKey:
'0x98319d4ff8a9508c4bb0cf0b5a78d760a0b2082c02775e6e82370816fedfff48925a225d97aa00682d6a59b95b18780c10d7032336e88f3442b42361f4a66011',
},
],
},
},
};
Use command yarn build to compile the contracts and abi files used for generating contracts in project. This command can compile both main contract and sub-contract, but please notice that it can only produce the abi files of the main contract. (Will be resolved in the future use-ink/cargo-contract#60)
Prerequisites:
- rust-src:
rustup component add rust-src - wasm-opt: https://github.com/WebAssembly/binaryen#tools
- cargo contract v0.7.0:
cargo install --git https://github.com/paritytech/cargo-contract cargo-contract --force - rust nightly: https://rust-lang.github.io/rustup/installation/index.html#installing-nightly
You can specify the contract name to compile, by default it compiles all contracts in the workspace.
$ yarn build --package <ContractName>You can also specify the toolchain needed by compilation. The default one is nightly:
$ yarn build --toolchain stableThe files generated by compilation will be in artifacts directory by default.
Redspot only supports the substrate rc6, you can compile the latest substrate code, or using our substrate contract test chain Jupiter (https://github.com/patractlabs/jupiter) for development. Jupiter has been done some optimization on contract test.
Please take a notice, for some chains (like Jupiter), they require adding some types in redspot-config.js to make them work, otherwise may end up with signature error.
types: {
Address: "AccountId",
LookupSource: "AccountId",
}
Redspot uses jest as the test framework. You can pass jest cli options to yarn test command like this:
yarn test --runInBand
The above command indicates that jest will excute the test files by sequence.
Specially: you can specify the network you want by yarn test --network <networkname>.
All <name>.test.js files inside the tests directory will get tested and each file has its independent sandbox environment.
Global variables config and artifacts are injected to the test files.
Heads up, if contract code has been updated, please rum yarn build first to compile the project then run yarn test to test it.
yarn migrate will excute the files in migrateions directory, the prefix numbers in filenames indicate the excute order.
Run yarn migrate --network <networkname> to specify the network you want to link.
Similarly, global variables config and artifacts are injected to the migrate files as well.
Global variable config keeps your project configurations and api object.
The api object used to be injected to polkadot.
The accounts set in redspot-config.js
You can get an abstract contract instance by calling const contract = artifacts.require(<contractName>). It also has some other functions: putCode, instantiate, deployed, load.
Find the paring wasm files automatically and upload to test net.
contract.instantiate(signer: KeyringPair, codeHash: Hash | string, inputData: any, endowment: number | BN = new BN('10000000000'), gasRequired: number | BN = new BN('10000000000'))
By instantiating the contract with the given parameters, the function will get an instantiated contract address. Heads up: the same parameter cannot be instantiated multiple times in the same chain.
contract.deployed(signer: KeyringPair, codeHash: Hash | string, inputData: any, endowment: number | BN = new BN('10000000000'), gasRequired: number | BN = new BN('10000000000'))
Similar to instantiate, but will return an instance of contractApi.
Load the instantiated contract and return an instance of contractApi
contractApi can be obtained by contract.load and contract.deployed, it can call the methods of the contract.
contractApi.messages.balanceOf(Alice.publicKey).call(<option>) It calls the balanceOf method of the contract and returns the corresponding type by rpc.
contractApi.messages.transfer(Bob.publicKey, '100000').send(<option>) It sends a contract transfer to the chain and get a Result type.
interface Result {
account: string;
txHash?: string;
blockHash?: string;
message?: string;
data?: any;
status: 'error' | 'event' | 'queued' | 'success';
result: SubmittableResult;
events?: {
bytes: string;
section: string;
method: string;
phaseType: string;
phaseIndex: number;
args: any[];
}[];
}
The events of the contract are decoded.
When you run npx redspot project it automatically installs the latest version of Redspot.
To update an existing project to a new version of Redspot, you only need to run a command in the project:
yarn upgrade redspot --latest
It will install the latest redSpot version in your project.
Redspot initializes with a debug configuration file in your project. You can run it like this:
