\n
\n
![\"Comprehensive](\"https:\/\/image.blockchain.news:443\/features\/052E732CDC0184391FF0A028CC1D40A3A21073F8765712CD8FA1350C21CF9589.jpg\")
\n
\n <\/a>
\n <\/figure>\n
Developers are at the heart of the Injective (INJ)ecosystem. With a diverse range of dApps spanning Web3 finance, Injective offers something for everyone. If you\u2019ve been following the Injective ecosystem and want to learn more about creating your first dApp on Injective, this guide is for you.<\/p>\n
Installing injectived<\/code><\/h2>\ninjectived<\/code> is the CLI tool used to interact with the Injective network. You can use the injectived<\/code> CLI to compile, deploy, and interact with Injective smart contracts, run your own node, and more. Before installing it, ensure you have rustup<\/code><\/a> along with recent versions of rustc<\/code> and cargo<\/code> installed. Currently, testing can be done with Rust v1.58.1+.<\/p>\nAdditionally, you need to install the wasm32-unknown-unknown<\/code> target and the cargo-generate<\/code> Rust crate.<\/p>\nYou can check versions via the following commands:<\/p>\n
rustc --version\ncargo --version\nrustup target list --installed<\/code><\/pre>\nIf wasm32<\/code> is not listed, run this command:<\/p>\nrustup target add wasm32-unknown-unknown<\/code><\/p>\nTo install cargo-generate<\/code>, run:<\/p>\ncargo install cargo-generate<\/code><\/pre>\nTo install injectived<\/code> on your machine, you have two options: install it from the binary or from source. For complete instructions on both methods, see Install Injectived<\/a>.<\/p>\nYour First Smart Contract<\/h2>\n
A smart contract can be considered an instance of a singleton object whose internal state is persisted on the blockchain. Users can trigger state changes or query the contract’s state by sending JSON messages. These JSON messages are different from Injective messages such as MsgSend<\/code> and MsgExecuteContract<\/code>.<\/p>\nAs a smart contract developer, your job is to define three functions that compose your smart contract’s interface:<\/p>\n
\ninstantiate()<\/code>: a constructor called during contract instantiation to provide the initial state<\/li>\nexecute()<\/code>: called when a user wants to invoke a method on the smart contract<\/li>\nquery()<\/code>: called when a user wants to retrieve data from the smart contract<\/li>\n<\/ul>\nIn our sample counter contract<\/a>, we will implement one instantiate<\/code>, one query<\/code>, and two execute<\/code> methods.<\/p>\nCounter Template<\/h3>\n
In your working directory, launch your smart contract with the recommended folder structure and build options by running the following commands:<\/p>\n
cargo generate --git https:\/\/github.com\/CosmWasm\/cw-template.git --branch 1.0 --name my-first-contract\ncd my-first-contract<\/code><\/pre>\nThis template will provide you with the basic boilerplate and structure for a smart contract. In the src\/contract.rs<\/a> file you will find that the standard CosmWasm entry points instantiate()<\/a>, execute()<\/a>, and query()<\/a> are properly exposed and connected.<\/p>\nState<\/h3>\n
State handles the database where smart contract data is stored and accessed.<\/p>\n
The starting template<\/a> has the following basic state, a singleton struct State<\/code> containing:<\/p>\n\ncount<\/code>, a 32-bit integer that execute()<\/code> messages will interact by increasing or resetting it.<\/li>\nowner<\/code>, the sender address of the MsgInstantiateContract<\/code>, which determines if certain execution messages are permitted.<\/li>\n<\/ul>\nInstantiateMsg<\/h3>\n
InstantiateMsg<\/code> is provided to the contract when a user instantiates a contract on the blockchain through a MsgInstantiateContract<\/code>. This message supplies the contract with its configuration as well as its initial state.<\/p>\nOn Injective, uploading a contract’s code and instantiating a contract are separate events, unlike on Ethereum. This separation allows a small set of vetted contract archetypes to exist as multiple instances sharing the same base code, but be configured with different parameters (imagine one canonical ERC20, and multiple tokens that use its code).<\/p>\n
ExecuteMsg<\/h3>\n
ExecuteMsg<\/code> is a JSON message passed to the execute()<\/code> function through a MsgExecuteContract<\/code>. Unlike InstantiateMsg<\/code>, ExecuteMsg<\/code> can exist as several different types of messages to account for the various types of functions that a smart contract can expose to users. The ExecuteMsgs<\/code><\/a>: Increment<\/code> and Reset<\/code>.<\/p>\n\nIncrement<\/code> has no input parameter and increases the value of count by 1.<\/li>\nReset<\/code> takes a 32-bit integer as a parameter and resets the value of count to the input parameter.<\/li>\n<\/ul>\nQueryMsg<\/h3>\n
The GetCount<\/code> query message has no parameters and returns the count<\/a> value.<\/p>\nUnit test<\/h3>\n
Unit tests should be run as the first line of assurance before deploying the code on-chain. They are quick to execute and can provide helpful backtraces on failures with the RUST_BACKTRACE=1<\/code> flag:<\/p>\ncargo unit-test \/\/ run this with RUST_BACKTRACE=1 for helpful backtraces<\/code><\/pre>\nYou can find the unit test implementation at src\/contract.rs<\/code><\/p>\nBuilding the Contract<\/h3>\n
Now that we understand and have tested the contract, we can run the following command to build the contract. This will check for any preliminary errors before we optimize the contract in the next step.<\/p>\n
cargo wasm<\/code><\/pre>\nNext, we must optimize the contract in order to ready the code for upload to the chain.<\/p>\n
CosmWasm has rust-optimizer<\/a>, an optimizing compiler that produces a small and consistent build output. The easiest method to use the tool is through a published Docker image\u2014check here<\/a> for the latest x86 version, or here<\/a> for the latest ARM version. With Docker running, use the following command to mount the contract code to \/code<\/code> and optimize the output (you can use an absolute path instead of $(pwd)<\/code> if you don’t want to cd to the directory first):<\/p>\nFor x86:<\/p>\n
docker run --rm -v \"$(pwd)\":\/code \\\n --mount type=volume,source=\"$(basename \"$(pwd)\")_cache\",target=\/code\/target \\\n --mount type=volume,source=registry_cache,target=\/usr\/local\/cargo\/registry \\\n cosmwasm\/rust-optimizer:0.12.12<\/code><\/pre>\nFor ARM64:<\/p>\n
docker run --rm -v \"$(pwd)\":\/code \\\n --mount type=volume,source=\"$(basename \"$(pwd)\")_cache\",target=\/code\/target \\\n --mount type=volume,source=registry_cache,target=\/usr\/local\/cargo\/registry \\\n cosmwasm\/rust-optimizer-arm64:0.12.12<\/code><\/pre>\nThis produces an artifacts<\/code> directory with a PROJECT_NAME.wasm<\/code> and a checksums.txt<\/code> file containing the SHA256<\/code> hash of the Wasm file. The Wasm file is compiled deterministically, meaning anyone else running the same Docker image on the same Git commit should get an identical file with the same SHA256<\/code> hash.<\/p>\nUpload the Wasm Contract<\/h3>\n
As mentioned above, Wasm smart contracts are uploaded via the injectived<\/code> CLI. To proceed, initialize and fund an account with test funds (see here<\/a> for instructions). Once that is done, enter the following command to upload the contract:<\/p>\n# inside the \"injective-core-staging\" container, or from the contract directory if running injectived locally\nyes 12345678 | injectived tx wasm store artifacts\/my_first_contract.wasm \\\n--from=$(echo $INJ_ADDRESS) \\\n--chain-id=\"injective-888\" \\\n--yes --fees=1000000000000000inj --gas=2000000 \\\n--node=https:\/\/k8s.testnet.tm.injective.network:443<\/code><\/pre>\nNext, enter your address on the Injective Testnet Explorer<\/a> and look for a transaction with the txhash<\/code> returned from storing the code on-chain. The transaction type should be MsgStoreCode<\/code>.<\/p>\nAnd voil\u00e0! You have successfully created and uploaded your first smart contract on Injective. For more information and context around each step, see here<\/a>.<\/p>\nBuild a Front End<\/h2>\n
While it is possible to interact with your contract through the Injective CLI, this is not ideal for most dApp users. A web UI can provide a much better experience. A web UI can provide a much better experience. Rather than sending transaction messages through injectived<\/code>, we can abstract away the complexity and provide the user with two buttons\u2014one to increment the count and one to reset the count.<\/p>\nFor example, see the counter website example<\/a>. A high level guide on developing the front end using Vue and the Injective TypeScript SDK can be found in injective-simple-sc-counter\/nuxt<\/a>. For a React implementation, see injective-simple-sc-counter-ui\/next<\/a>.<\/p>\nNow, interacting with the contract is as simple as clicking a button and signing with a wallet such as MetaMask (ensure the account is set to Ethereum Goerli Testnet to avoid a chain ID mismatch error).<\/p>\n
And just like that, you have built your first dApp on Injective!<\/p>\n
About Injective<\/h3>\n
Injective is a lightning fast interoperable layer one blockchain optimized for building the premier Web3 finance applications. Injective provides developers with powerful plug-and-play modules for creating unmatched dApps. INJ is the native asset that powers Injective and its rapidly growing ecosystem. Injective is incubated by Binance and is backed by prominent investors such as Jump Crypto, Pantera and Mark Cuban.<\/p>\n
Website<\/a> | Telegram<\/a> | Discord<\/a> | Blog<\/a> | Twitter<\/a> | Learn<\/a> | Youtube<\/a> | Facebook<\/a> | LinkedIn<\/a> | Reddit<\/a> | Instagram<\/a> | Orbit Newsletter<\/a><\/p>\nImage source: Shutterstock<\/i><\/span> <\/p>\n <\/p>\n
\n
\n \n <\/div>\n
Additionally, you need to install the You can check versions via the following commands:<\/p>\n If To install To install A smart contract can be considered an instance of a singleton object whose internal state is persisted on the blockchain. Users can trigger state changes or query the contract’s state by sending JSON messages. These JSON messages are different from Injective messages such as As a smart contract developer, your job is to define three functions that compose your smart contract’s interface:<\/p>\n In our sample counter contract<\/a>, we will implement one In your working directory, launch your smart contract with the recommended folder structure and build options by running the following commands:<\/p>\n This template will provide you with the basic boilerplate and structure for a smart contract. In the src\/contract.rs<\/a> file you will find that the standard CosmWasm entry points instantiate()<\/a>, execute()<\/a>, and query()<\/a> are properly exposed and connected.<\/p>\n State handles the database where smart contract data is stored and accessed.<\/p>\n The starting template<\/a> has the following basic state, a singleton struct On Injective, uploading a contract’s code and instantiating a contract are separate events, unlike on Ethereum. This separation allows a small set of vetted contract archetypes to exist as multiple instances sharing the same base code, but be configured with different parameters (imagine one canonical ERC20, and multiple tokens that use its code).<\/p>\n The Unit tests should be run as the first line of assurance before deploying the code on-chain. They are quick to execute and can provide helpful backtraces on failures with the You can find the unit test implementation at Now that we understand and have tested the contract, we can run the following command to build the contract. This will check for any preliminary errors before we optimize the contract in the next step.<\/p>\n Next, we must optimize the contract in order to ready the code for upload to the chain.<\/p>\n CosmWasm has rust-optimizer<\/a>, an optimizing compiler that produces a small and consistent build output. The easiest method to use the tool is through a published Docker image\u2014check here<\/a> for the latest x86 version, or here<\/a> for the latest ARM version. With Docker running, use the following command to mount the contract code to For x86:<\/p>\n For ARM64:<\/p>\n This produces an As mentioned above, Wasm smart contracts are uploaded via the Next, enter your address on the Injective Testnet Explorer<\/a> and look for a transaction with the And voil\u00e0! You have successfully created and uploaded your first smart contract on Injective. For more information and context around each step, see here<\/a>.<\/p>\n While it is possible to interact with your contract through the Injective CLI, this is not ideal for most dApp users. A web UI can provide a much better experience. A web UI can provide a much better experience. Rather than sending transaction messages through For example, see the counter website example<\/a>. A high level guide on developing the front end using Vue and the Injective TypeScript SDK can be found in injective-simple-sc-counter\/nuxt<\/a>. For a React implementation, see injective-simple-sc-counter-ui\/next<\/a>.<\/p>\n Now, interacting with the contract is as simple as clicking a button and signing with a wallet such as MetaMask (ensure the account is set to Ethereum Goerli Testnet to avoid a chain ID mismatch error).<\/p>\n And just like that, you have built your first dApp on Injective!<\/p>\n Injective is a lightning fast interoperable layer one blockchain optimized for building the premier Web3 finance applications. Injective provides developers with powerful plug-and-play modules for creating unmatched dApps. INJ is the native asset that powers Injective and its rapidly growing ecosystem. Injective is incubated by Binance and is backed by prominent investors such as Jump Crypto, Pantera and Mark Cuban.<\/p>\n Website<\/a> | Telegram<\/a> | Discord<\/a> | Blog<\/a> | Twitter<\/a> | Learn<\/a> | Youtube<\/a> | Facebook<\/a> | LinkedIn<\/a> | Reddit<\/a> | Instagram<\/a> | Orbit Newsletter<\/a><\/p>\n Image source: Shutterstock<\/i><\/span> <\/p>\n <\/p>\n injectived<\/code> is the CLI tool used to interact with the Injective network. You can use the injectived<\/code> CLI to compile, deploy, and interact with Injective smart contracts, run your own node, and more. Before installing it, ensure you have rustup<\/code><\/a> along with recent versions of rustc<\/code> and cargo<\/code> installed. Currently, testing can be done with Rust v1.58.1+.<\/p>\nwasm32-unknown-unknown<\/code> target and the cargo-generate<\/code> Rust crate.<\/p>\nrustc --version\ncargo --version\nrustup target list --installed<\/code><\/pre>\nwasm32<\/code> is not listed, run this command:<\/p>\nrustup target add wasm32-unknown-unknown<\/code><\/p>\ncargo-generate<\/code>, run:<\/p>\ncargo install cargo-generate<\/code><\/pre>\ninjectived<\/code> on your machine, you have two options: install it from the binary or from source. For complete instructions on both methods, see Install Injectived<\/a>.<\/p>\nYour First Smart Contract<\/h2>\n
MsgSend<\/code> and MsgExecuteContract<\/code>.<\/p>\n\n
instantiate()<\/code>: a constructor called during contract instantiation to provide the initial state<\/li>\nexecute()<\/code>: called when a user wants to invoke a method on the smart contract<\/li>\nquery()<\/code>: called when a user wants to retrieve data from the smart contract<\/li>\n<\/ul>\ninstantiate<\/code>, one query<\/code>, and two execute<\/code> methods.<\/p>\nCounter Template<\/h3>\n
cargo generate --git https:\/\/github.com\/CosmWasm\/cw-template.git --branch 1.0 --name my-first-contract\ncd my-first-contract<\/code><\/pre>\nState<\/h3>\n
State<\/code> containing:<\/p>\n\n
count<\/code>, a 32-bit integer that execute()<\/code> messages will interact by increasing or resetting it.<\/li>\nowner<\/code>, the sender address of the MsgInstantiateContract<\/code>, which determines if certain execution messages are permitted.<\/li>\n<\/ul>\nInstantiateMsg<\/h3>\n
InstantiateMsg<\/code> is provided to the contract when a user instantiates a contract on the blockchain through a MsgInstantiateContract<\/code>. This message supplies the contract with its configuration as well as its initial state.<\/p>\nExecuteMsg<\/h3>\n
ExecuteMsg<\/code> is a JSON message passed to the execute()<\/code> function through a MsgExecuteContract<\/code>. Unlike InstantiateMsg<\/code>, ExecuteMsg<\/code> can exist as several different types of messages to account for the various types of functions that a smart contract can expose to users. The ExecuteMsgs<\/code><\/a>: Increment<\/code> and Reset<\/code>.<\/p>\n\n
Increment<\/code> has no input parameter and increases the value of count by 1.<\/li>\nReset<\/code> takes a 32-bit integer as a parameter and resets the value of count to the input parameter.<\/li>\n<\/ul>\nQueryMsg<\/h3>\n
GetCount<\/code> query message has no parameters and returns the count<\/a> value.<\/p>\nUnit test<\/h3>\n
RUST_BACKTRACE=1<\/code> flag:<\/p>\ncargo unit-test \/\/ run this with RUST_BACKTRACE=1 for helpful backtraces<\/code><\/pre>\nsrc\/contract.rs<\/code><\/p>\nBuilding the Contract<\/h3>\n
cargo wasm<\/code><\/pre>\n\/code<\/code> and optimize the output (you can use an absolute path instead of $(pwd)<\/code> if you don’t want to cd to the directory first):<\/p>\ndocker run --rm -v \"$(pwd)\":\/code \\\n --mount type=volume,source=\"$(basename \"$(pwd)\")_cache\",target=\/code\/target \\\n --mount type=volume,source=registry_cache,target=\/usr\/local\/cargo\/registry \\\n cosmwasm\/rust-optimizer:0.12.12<\/code><\/pre>\ndocker run --rm -v \"$(pwd)\":\/code \\\n --mount type=volume,source=\"$(basename \"$(pwd)\")_cache\",target=\/code\/target \\\n --mount type=volume,source=registry_cache,target=\/usr\/local\/cargo\/registry \\\n cosmwasm\/rust-optimizer-arm64:0.12.12<\/code><\/pre>\nartifacts<\/code> directory with a PROJECT_NAME.wasm<\/code> and a checksums.txt<\/code> file containing the SHA256<\/code> hash of the Wasm file. The Wasm file is compiled deterministically, meaning anyone else running the same Docker image on the same Git commit should get an identical file with the same SHA256<\/code> hash.<\/p>\nUpload the Wasm Contract<\/h3>\n
injectived<\/code> CLI. To proceed, initialize and fund an account with test funds (see here<\/a> for instructions). Once that is done, enter the following command to upload the contract:<\/p>\n# inside the \"injective-core-staging\" container, or from the contract directory if running injectived locally\nyes 12345678 | injectived tx wasm store artifacts\/my_first_contract.wasm \\\n--from=$(echo $INJ_ADDRESS) \\\n--chain-id=\"injective-888\" \\\n--yes --fees=1000000000000000inj --gas=2000000 \\\n--node=https:\/\/k8s.testnet.tm.injective.network:443<\/code><\/pre>\ntxhash<\/code> returned from storing the code on-chain. The transaction type should be MsgStoreCode<\/code>.<\/p>\nBuild a Front End<\/h2>\n
injectived<\/code>, we can abstract away the complexity and provide the user with two buttons\u2014one to increment the count and one to reset the count.<\/p>\nAbout Injective<\/h3>\n
\n
\n \n <\/div>\n