{"id":8474,"date":"2025-10-11T16:20:00","date_gmt":"2025-10-11T10:20:00","guid":{"rendered":"https:\/\/webisoft.com\/articles\/?p=8474"},"modified":"2025-10-25T19:24:47","modified_gmt":"2025-10-25T13:24:47","slug":"avalanche-smart-contract","status":"publish","type":"post","link":"https:\/\/blog.webisoft.com\/avalanche-smart-contract\/","title":{"rendered":"Avalanche Smart Contract Guide for Beginners"},"content":{"rendered":"\r\n

Let’s imagine for a moment you’re an explorer, standing at the edge of a vast, snow-capped mountain range. It’s vast, full of unknowns, and yet, full of limitless possibilities. Sounds daunting?\u00a0<\/p>\r\n\r\n\r\n\r\n

Well, that’s similar to stepping into the world of Avalanche smart contracts. Just like scaling a mountain, getting to grips with Avalanche smart contracts might seem intimidating at first.<\/p>\r\n\r\n\r\n\r\n

Yet, it’s an exciting adventure waiting for those ready to explore the future of decentralized applications (DApps).\u00a0<\/p>\r\n\r\n\r\n\r\n

Using this guide, you will discover the crevices and slopes of creating and deploying smart contracts on the Avalanche blockchain.<\/p>\r\n\r\n\r\n\r\n

We’ll get into Solidity programming, Truffle tooling, and Ethereum Virtual Machine intricacies. Buckle up, your journey starts here!<\/p>\r\n\r\n\r\n\r\n

Introducing Avalanche: Unleashing Power in the Decentralized World<\/h2>\r\n\r\n\r\n\r\n

 <\/p>\r\n\r\n\r\n

\r\n
\"Introducing<\/figure><\/div>\r\n\r\n\r\n

 <\/p>\r\n\r\n\r\n\r\n

Imagine an ecosystem that’s not just secure, adaptable, and expandable, but also specifically designed for developing decentralized applications.<\/p>\r\n\r\n\r\n\r\n

This is the vision brought to life by Ava Labs\u2019 founder and Cornell University\u2019s computer science professor, Emin G\u00fcn Sirer, and it’s known as Avalanche.\u00a0<\/p>\r\n\r\n\r\n\r\n

As one of the fastest and most interoperable platforms in the blockchain universe, Avalanche makes creating tailor-made applications on the blockchain a reality for anyone. The lifeblood of this ecosystem is its native token – AVAX.<\/p>\r\n\r\n\r\n\r\n

Threefold Blockchain Magic<\/h3>\r\n\r\n\r\n\r\n

The strength of Avalanche lies in its unique design – a trinity of inbuilt blockchains, each engineered for a distinct function. Here’s the breakdown:<\/p>\r\n\r\n\r\n\r\n

Exchange Chain (X-Chain)<\/h3>\r\n\r\n\r\n\r\n

This component serves as a hub for creating, trading, and managing assets and their transactions.<\/p>\r\n\r\n\r\n\r\n

Platform Chain (P-Chain)<\/h3>\r\n\r\n\r\n\r\n

With its main job being the coordination of validators and the management and creation of subnets, the P-Chain plays a vital role in Avalanche\u2019s ecosystem.<\/p>\r\n\r\n\r\n\r\n

Contract Chain (C-Chain)<\/h3>\r\n\r\n\r\n\r\n

But what’s a blockchain ecosystem without smart contracts? Enter the C-Chain, an embodiment of the Ethereum Virtual Machine that’s designed for creating smart contracts.<\/p>\r\n\r\n\r\n\r\n

Since our focus is on Avalanche smart contracts, let’s delve a little deeper into the C-Chain.<\/p>\r\n\r\n\r\n\r\n

The Power of the Contract Chain<\/h4>\r\n\r\n\r\n\r\n

The Contract Chain lets you develop Ethereum-fit smart contracts as well as stand as the go-to blockchain for Avalanche smart contracts.<\/p>\r\n\r\n\r\n\r\n

With superior throughput, affordable gas pricing, quick transaction confirmation times, and increased speed, the C-Chain stands out from the Ethereum Virtual Machine.<\/p>\r\n\r\n\r\n\r\n

All of these perks stem from its utilization of the Proof-of-Stake consensus mechanism, underpinned by the Snowman consensus protocol.<\/p>\r\n\r\n\r\n\r\n

Unleashing Avalanche’s Key Features<\/h2>\r\n\r\n\r\n\r\n

 <\/p>\r\n\r\n\r\n

\r\n
\"Unleashing<\/figure><\/div>\r\n\r\n\r\n

 <\/p>\r\n\r\n\r\n\r\n

Let’s unwrap some of the essential elements that make Avalanche shine.<\/p>\r\n\r\n\r\n\r\n

Scalability<\/h3>\r\n\r\n\r\n\r\n

Avalanche is a powerhouse, managing an impressive 4500 transactions per second, making it an extraordinarily scalable, robust, and efficient protocol.<\/p>\r\n\r\n\r\n\r\n

Speed<\/h3>\r\n\r\n\r\n\r\n

In a race of blockchain ecosystems, Avalanche takes the gold medal, staking its claim as the fastest smart contract platform, gauged by its time-to-finality.<\/p>\r\n\r\n\r\n\r\n

Security<\/h3>\r\n\r\n\r\n\r\n

Forget the 51% standard – Avalanche takes security to another level. Its powerful protocol guarantees robust security that is considerably more substantial.<\/p>\r\n\r\n\r\n\r\n

Interoperability and Flexibility<\/h3>\r\n\r\n\r\n\r\n

Avalanche’s architecture is built to welcome a plethora of blockchain assets, with AVAX acting as a security measure and a unit of exchange, marking Avalanche as a universal and versatile ecosystem.<\/p>\r\n\r\n\r\n\r\n

Sustainability<\/h3>\r\n\r\n\r\n\r\n

Bidding adieu to the energy-intensive proof-of-work consensus mechanism, Avalanche embraces the proof-of-stake consensus mechanism.<\/p>\r\n\r\n\r\n\r\n

It’s a move that ensures a sustainable, less energy-consuming platform, making Avalanche a green choice in the blockchain world.<\/p>\r\n\r\n\r\n\r\n

Developing and Deploying Smart Contracts on Avalanche<\/h2>\r\n\r\n\r\n\r\n

Building and launching a smart contract on Avalanche may seem intimidating, but fear not! I’m here to walk you through the process. And don’t worry, it’s not as tough as you might think.\u00a0<\/p>\r\n\r\n\r\n\r\n

We’re going to use Solidity, a language specifically designed for implementing smart contracts, so it’s perfect for our needs.<\/p>\r\n\r\n\r\n\r\n

Essential Tools for the Job<\/h3>\r\n\r\n\r\n\r\n

To shape your smart contracts for Avalanche, you can use a wide variety of tools such as Hardhat, Remix, and more. For our purposes though, we’ll focus on using Truffle in combination with Avalanche’s C-chain blockchain.\u00a0<\/p>\r\n\r\n\r\n\r\n

Why Truffle? You can write, compile, manage migrations, generate artifacts, and even interact with contracts that have already been deployed using this tool.<\/p>\r\n\r\n\r\n\r\n

Setting Up the Workspace<\/h3>\r\n\r\n\r\n\r\n

 <\/p>\r\n\r\n\r\n

\r\n
\"Setting<\/figure><\/div>\r\n\r\n\r\n

 <\/p>\r\n\r\n\r\n\r\n

Before we dive into the nitty-gritty of creating smart contracts, we need to ensure our workspace is properly set up. Here are the key elements we’ll need:<\/p>\r\n\r\n\r\n\r\n

Avalanche Network Runner: This tool lets you run a localized Avalanche network<\/p>\r\n\r\n\r\n\r\n

NodeJS (Version 8.9.4 or later)<\/p>\r\n\r\n\r\n\r\n

Truffle: You can get it by running \u201cnpm install -g truffle\u201d<\/p>\r\n\r\n\r\n\r\n

1. Launching a Local Avalanche Network<\/h4>\r\n\r\n\r\n\r\n

Starting with the Avalanche Network Runner, it’s an excellent tool that enables us to run a localized Avalanche network, which we can interact with in real-time. Let’s kick things off by running a 5-node Avalanche network.\u00a0<\/p>\r\n\r\n\r\n\r\n

cd \/path\/to\/avalanche-network-runner<\/strong><\/p>\r\n\r\n\r\n\r\n

# start a five node staking network<\/strong><\/p>\r\n\r\n\r\n\r\n

.\/go run examples\/local\/fivenodenetwork\/main.go<\/strong><\/p>\r\n\r\n\r\n\r\n

Keep it running as long as you want, and when you’re done, just hit CTRL + C.<\/p>\r\n\r\n\r\n\r\n

2. Truffle Directory Creation and Dependency Installation<\/h4>\r\n\r\n\r\n\r\n

Once our network is up and running, let’s open a fresh terminal tab and focus on setting up our “Truffle” directory and installing dependencies. This is the space where you’ll be doing most of your work.<\/p>\r\n\r\n\r\n\r\n

cd \/path\/to\/directory<\/strong><\/p>\r\n\r\n\r\n\r\n

After deciding where you want your Truffle workspace, generate a new path and christen it “Truffle.”\u00a0<\/p>\r\n\r\n\r\n\r\n

mkdir truffle; cd truffle<\/strong><\/p>\r\n\r\n\r\n\r\n

Now it’s time to install the essential tools, using \u201cnpm\u201d, get web3.js, a library which acts as a bridge between the AvalancheJS and Ethereum Virtual Machine (EVM) for swapping chains.<\/p>\r\n\r\n\r\n\r\n

npm install web3 avalanche -s<\/strong><\/p>\r\n\r\n\r\n\r\n

Web3 will provide us with an HTTP server, which is a channel for web3 to engage using the EVM. Let’s finish off our truffle project by building a boilerplate.<\/p>\r\n\r\n\r\n\r\n

truffle init<\/strong><\/p>\r\n\r\n\r\n\r\n

Remember when you construct your own development network, it automatically deposits funds into some static accounts. For these addresses, we’ll employ @truffle\/hdwallet-provider to generate accounts.<\/p>\r\n\r\n\r\n\r\n

npm install @truffle\/hdwallet-provider<\/strong><\/p>\r\n\r\n\r\n\r\n

3. Tailoring Your truffle-config.js<\/h4>\r\n\r\n\r\n\r\n

Once you initiate Truffle, it’s going to create a file named “truffle-config.js”. This file needs your attention now. We’re going to inject some code into this to make it work for us.<\/p>\r\n\r\n\r\n\r\n

const Web3 = require(“web3”);<\/strong><\/p>\r\n\r\n\r\n\r\n

const HDWalletProvider = require(“@truffle\/hdwallet-provider”);<\/strong><\/p>\r\n\r\n\r\n\r\n

const protocol = “http”;<\/strong><\/p>\r\n\r\n\r\n\r\n

const ip = “localhost”;<\/strong><\/p>\r\n\r\n\r\n\r\n

const port = 9650;<\/strong><\/p>\r\n\r\n\r\n\r\n

Web3.providers.HttpProvider.prototype.sendAsync = Web3.providers.HttpProvider.prototype.send;<\/strong><\/p>\r\n\r\n\r\n\r\n

const provider = new Web3.providers.HttpProvider(<\/strong><\/p>\r\n\r\n\r\n\r\n

${protocol}:\/\/${ip}:${port}\/ext\/bc\/C\/rpc<\/strong><\/p>\r\n\r\n\r\n\r\n

);<\/strong><\/p>\r\n\r\n\r\n\r\n

const privateKeys = [<\/strong><\/p>\r\n\r\n\r\n\r\n

“0x56289e99c94b6912bfc12adc093c9b51124f0dc54ac7a766b2bc5ccf558d8027”,<\/strong><\/p>\r\n\r\n\r\n\r\n

“0x7b4198529994b0dc604278c99d153cfd069d594753d471171a1d102a10438e07”,<\/strong><\/p>\r\n\r\n\r\n\r\n

“0x15614556be13730e9e8d6eacc1603143e7b96987429df8726384c2ec4502ef6e”,<\/strong><\/p>\r\n\r\n\r\n\r\n

“0x31b571bf6894a248831ff937bb49f7754509fe93bbd2517c9c73c4144c0e97dc”,<\/strong><\/p>\r\n\r\n\r\n\r\n

“0x6934bef917e01692b789da754a0eae31a8536eb465e7bff752ea291dad88c675”,<\/strong><\/p>\r\n\r\n\r\n\r\n

“0xe700bdbdbc279b808b1ec45f8c2370e4616d3a02c336e68d85d4668e08f53cff”,<\/strong><\/p>\r\n\r\n\r\n\r\n

“0xbbc2865b76ba28016bc2255c7504d000e046ae01934b04c694592a6276988630”,<\/strong><\/p>\r\n\r\n\r\n\r\n

“0xcdbfd34f687ced8c6968854f8a99ae47712c4f4183b78dcc4a903d1bfe8cbf60”,<\/strong><\/p>\r\n\r\n\r\n\r\n

“0x86f78c5416151fe3546dece84fda4b4b1e36089f2dbc48496faf3a950f16157c”,<\/strong><\/p>\r\n\r\n\r\n\r\n

“0x750839e9dbbd2a0910efe40f50b2f3b2f2f59f5580bb4b83bd8c1201cf9a010a”,<\/strong><\/p>\r\n\r\n\r\n\r\n

];<\/strong><\/p>\r\n\r\n\r\n\r\n

module.exports = {<\/strong><\/p>\r\n\r\n\r\n\r\n

networks: {<\/strong><\/p>\r\n\r\n\r\n\r\n

development: {<\/strong><\/p>\r\n\r\n\r\n\r\n

provider: () => {<\/strong><\/p>\r\n\r\n\r\n\r\n

return new HDWalletProvider({<\/strong><\/p>\r\n\r\n\r\n\r\n

privateKeys: privateKeys,<\/strong><\/p>\r\n\r\n\r\n\r\n

providerOrUrl: provider,<\/strong><\/p>\r\n\r\n\r\n\r\n

});<\/strong><\/p>\r\n\r\n\r\n\r\n

},<\/strong><\/p>\r\n\r\n\r\n\r\n

network_id: “*”,<\/strong><\/p>\r\n\r\n\r\n\r\n

gas: 3000000,<\/strong><\/p>\r\n\r\n\r\n\r\n

gasPrice: 225000000000,<\/strong><\/p>\r\n\r\n\r\n\r\n

},<\/strong><\/p>\r\n\r\n\r\n\r\n

},<\/strong><\/p>\r\n\r\n\r\n\r\n

};<\/strong><\/p>\r\n\r\n\r\n\r\n

Remember, if you’re thinking about sending API calls to an alternative AvalancheGo node, it’s possible to tweak the “protocol”, \u201cport\u201d, and “ip”. Keep in mind that the “gas” and “gasPrice” are adjusted to align with the Avalanche C-chain parameters.<\/p>\r\n\r\n\r\n\r\n

4. Introducing Storage.sol<\/h4>\r\n\r\n\r\n\r\n

Let’s create a fresh file named “Storage.sol” within the “contracts” directory and populate it with some specific code.<\/p>\r\n\r\n\r\n\r\n

\/\/ SPDX-License-Identifier: MIT<\/strong><\/p>\r\n\r\n\r\n\r\n

pragma solidity >=0.4.22 <0.9.0;<\/strong><\/p>\r\n\r\n\r\n\r\n

\/**<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0* @title Storage<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0* @dev Store & retrieve value in a variable<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0*\/<\/strong><\/p>\r\n\r\n\r\n\r\n

contract Storage {<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0\u00a0uint256 number;<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0\u00a0\/**<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0\u00a0\u00a0* @dev Store value in variable<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0\u00a0\u00a0* @param num value to store<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0\u00a0\u00a0*\/<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0\u00a0function store(uint256 num) public {<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0number = num;<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0\u00a0}<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0\u00a0\/**<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0\u00a0\u00a0* @dev Return value<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0\u00a0\u00a0* @return value of ‘number’<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0\u00a0\u00a0*\/<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0\u00a0function retrieve() public view returns (uint256){<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0return number;<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0\u00a0}<\/strong><\/p>\r\n\r\n\r\n\r\n

}<\/strong><\/p>\r\n\r\n\r\n\r\n

This “Storage” file serves as the smart contract for Solidity, enabling us to record a number onto a blockchain via a function called “store” and later retrieve that number with a “retrieve” function.<\/p>\r\n\r\n\r\n\r\n

5. Creating a New Migration<\/h4>\r\n\r\n\r\n\r\n

Our next move is to append some more code into a fresh file. This one’s called “2_deploy_contracts.js” and resides in the directory of “migrations”.\u00a0<\/p>\r\n\r\n\r\n\r\n

It’s in charge of managing the deployment of our smart contract “Storage” into the blockchain.<\/p>\r\n\r\n\r\n\r\n

const Storage = artifacts.require(“Storage”);<\/strong><\/p>\r\n\r\n\r\n\r\n

module.exports = function (deployer) {<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0deployer.deploy(Storage);<\/strong><\/p>\r\n\r\n\r\n\r\n

};<\/strong><\/p>\r\n\r\n\r\n\r\n

6. Composing Contracts Using Truffle<\/h4>\r\n\r\n\r\n\r\n

Every time you make changes to “Storage.sol”, you must compile it with Truffle.\u00a0<\/p>\r\n\r\n\r\n\r\n

truffle compile<\/strong><\/p>\r\n\r\n\r\n\r\n

Here’s what you need to watch out for:<\/p>\r\n\r\n\r\n\r\n

Compiling your contracts…<\/strong><\/p>\r\n\r\n\r\n\r\n

===========================<\/strong><\/p>\r\n\r\n\r\n\r\n

> Compiling .\/contracts\/Migrations.sol<\/strong><\/p>\r\n\r\n\r\n\r\n

> Compiling .\/contracts\/Storage.sol<\/strong><\/p>\r\n\r\n\r\n\r\n

> Artifacts written to \/path\/to\/build\/contracts<\/strong><\/p>\r\n\r\n\r\n\r\n

> Compiled successfully using:<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0– solc: 0.5.16+commit.9c3226ce.Emscripten.clang<\/strong><\/p>\r\n\r\n\r\n\r\n

7. Your C-Chain Accounts\u00a0<\/h4>\r\n\r\n\r\n\r\n

Truffle tends to lean on the first account it can find on your C-chain client as the sender (“from” address) at the time you’re deploying your smart contracts to the C-chain.\u00a0<\/p>\r\n\r\n\r\n\r\n

Just make sure that this default account is already pre-loaded with some AVAX.<\/p>\r\n\r\n\r\n\r\n

Truffle Accounts<\/h5>\r\n\r\n\r\n\r\n

You can inspect the accounts that Truffle brings in by using the truffle console.<\/p>\r\n\r\n\r\n\r\n

To open the console of truffle, follow these steps:<\/p>\r\n\r\n\r\n\r\n

truffle console –network development<\/strong><\/p>\r\n\r\n\r\n\r\n

If you encounter an error message stating that the API call was rejected due to the chain not being fully bootstrapped, you’ll need to sit tight till the chain is prepared and ready for use. This shouldn’t take long.<\/p>\r\n\r\n\r\n\r\n

While you’re inside the truffle console, here’s what you can do:<\/p>\r\n\r\n\r\n\r\n

truffle(development)> accounts<\/strong><\/p>\r\n\r\n\r\n\r\n

[<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0‘0x8db97C7cEcE249c2b98bDC0226Cc4C2A57BF52FC’,<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0‘0x9632a79656af553F58738B0FB750320158495942’,<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0‘0x55ee05dF718f1a5C1441e76190EB1a19eE2C9430’,<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0‘0x4Cf2eD3665F6bFA95cE6A11CFDb7A2EF5FC1C7E4’,<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0‘0x0B891dB1901D4875056896f28B6665083935C7A8’,<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0‘0x01F253bE2EBF0bd64649FA468bF7b95ca933BDe2’,<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0‘0x78A23300E04FB5d5D2820E23cc679738982e1fd5’,<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0‘0x3C7daE394BBf8e9EE1359ad14C1C47003bD06293’,<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0‘0x61e0B3CD93F36847Abbd5d40d6F00a8eC6f3cfFB’,<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0‘0x0Fa8EA536Be85F32724D57A37758761B86416123’<\/strong><\/p>\r\n\r\n\r\n\r\n

]<\/strong><\/p>\r\n\r\n\r\n\r\n

If you’re keen to check the balance, simply type in the below command:<\/p>\r\n\r\n\r\n\r\n

truffle(development)> await web3.eth.getBalance(accounts[0])<\/strong><\/p>\r\n\r\n\r\n\r\n

‘50000000000000000000000000’<\/strong><\/p>\r\n\r\n\r\n\r\n

truffle(development)> await web3.eth.getBalance(accounts[1])<\/strong><\/p>\r\n\r\n\r\n\r\n

‘0’<\/strong><\/p>\r\n\r\n\r\n\r\n

You’ll notice that “accounts[0]” (your default account) has a balance, whereas “accounts[1]” is empty.<\/p>\r\n\r\n\r\n\r\n

Funding Your Accounts<\/h5>\r\n\r\n\r\n\r\n

For the purpose of funding your list of “accounts”, there’s a handy script that you can download and use with the below command:<\/p>\r\n\r\n\r\n\r\n

wget -nd -m https:\/\/raw.githubusercontent.com\/ava-labs\/avalanche-docs\/master\/scripts\/fund-cchain-addresses.js<\/strong><\/p>\r\n\r\n\r\n\r\n

To execute the script, enter the given code:<\/p>\r\n\r\n\r\n\r\n

truffle exec fund-cchain-addresses.js –network development<\/strong><\/p>\r\n\r\n\r\n\r\n

This script will distribute 1000 AVAX into every one of your “accounts”. After you’ve executed the script without a hitch, you can verify the balances with:<\/p>\r\n\r\n\r\n\r\n

truffle(development)> await web3.eth.getBalance(accounts[0]);<\/strong><\/p>\r\n\r\n\r\n\r\n

‘50000001000000000000000000’<\/strong><\/p>\r\n\r\n\r\n\r\n

truffle(development)> await web3.eth.getBalance(accounts[1]);<\/strong><\/p>\r\n\r\n\r\n\r\n

‘1000000000000000000’<\/strong><\/p>\r\n\r\n\r\n\r\n

Connecting with Personal APIs<\/h5>\r\n\r\n\r\n\r\n

Your node accounts link with private APIs. “Web3” includes several functions that utilize this API, like “web3.eth.personal.unlockAccount”, “web3.eth.personal.newAccount”, and so on.\u00a0<\/p>\r\n\r\n\r\n\r\n

This API, however, isn’t active by default. You can only enable it via “C-chain”\/”Coreth” configurations. The current Avalanche Network Runner doesn’t allow you to enable this API.\u00a0<\/p>\r\n\r\n\r\n\r\n

Thus, these features can only be accessed if you manually launch your network with the “internal-private-personal” API switched on via the “eth-apis” flag.<\/p>\r\n\r\n\r\n\r\n

8. Let’s Get Those Migrations Running<\/h4>\r\n\r\n\r\n\r\n

We’re all set! It’s time to run the migrations and launch your “Storage” contract. Here’s how you do it:<\/p>\r\n\r\n\r\n\r\n

truffle(development)> migrate –network development<\/strong><\/p>\r\n\r\n\r\n\r\n

After running the migrations, you’ll notice this:<\/p>\r\n\r\n\r\n\r\n

Compiling your contracts…<\/strong><\/p>\r\n\r\n\r\n\r\n

===========================<\/strong><\/p>\r\n\r\n\r\n\r\n

> Everything is up to date, there is nothing to compile.<\/strong><\/p>\r\n\r\n\r\n\r\n

Migrations dry-run (simulation)<\/strong><\/p>\r\n\r\n\r\n\r\n

===============================<\/strong><\/p>\r\n\r\n\r\n\r\n

> Network name:\u00a0 \u00a0 ‘development-fork’<\/strong><\/p>\r\n\r\n\r\n\r\n

> Network id:\u00a0 \u00a0 \u00a0 1<\/strong><\/p>\r\n\r\n\r\n\r\n

> Block gas limit: 99804786 (0x5f2e672)<\/strong><\/p>\r\n\r\n\r\n\r\n

1_initial_migration.js<\/strong><\/p>\r\n\r\n\r\n\r\n

======================<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0Deploying ‘Migrations’<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0———————-<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0> block number:\u00a0 \u00a0 \u00a0 \u00a0 4<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0> block timestamp: \u00a0 \u00a0 1607734632<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0> account: \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 0x34Cb796d4D6A3e7F41c4465C65b9056Fe2D3B8fD<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0> balance: \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 1000.91683679<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0> gas used:\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 176943 (0x2b32f)<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0> gas price: \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 225 gwei<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0> value sent:\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 0 ETH<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0> total cost:\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 0.08316321 ETH<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0————————————-<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0> Total cost:\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 0.08316321 ETH<\/strong><\/p>\r\n\r\n\r\n\r\n

2_deploy_contracts.js<\/strong><\/p>\r\n\r\n\r\n\r\n

=====================<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0Deploying ‘Storage’<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0——————-<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0> block number:\u00a0 \u00a0 \u00a0 \u00a0 6<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0> block timestamp: \u00a0 \u00a0 1607734633<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0> account: \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 0x34Cb796d4D6A3e7F41c4465C65b9056Fe2D3B8fD<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0> balance: \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 1000.8587791<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0> gas used:\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 96189 (0x177bd)<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0> gas price: \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 225 gwei<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0> value sent:\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 0 ETH<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0> total cost:\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 0.04520883 ETH<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0————————————-<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0> Total cost:\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 0.04520883 ETH<\/strong><\/p>\r\n\r\n\r\n\r\n

Summary<\/strong><\/p>\r\n\r\n\r\n\r\n

=======<\/strong><\/p>\r\n\r\n\r\n\r\n

> Total deployments: \u00a0 2<\/strong><\/p>\r\n\r\n\r\n\r\n

> Final cost:\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 0.13542204 ETH<\/strong><\/p>\r\n\r\n\r\n\r\n

If you skipped the step to create your account over the C-chain, you’ll likely encounter this error:<\/p>\r\n\r\n\r\n\r\n

Error: Expected parameter ‘from’ not passed to function.<\/strong><\/p>\r\n\r\n\r\n\r\n

Likewise, if you didn’t make sure to pre-fund the account, you might see an error like this:<\/p>\r\n\r\n\r\n\r\n

Error:\u00a0 *** Deployment Failed ***<\/strong><\/p>\r\n\r\n\r\n\r\n

“Migrations” could not deploy due to insufficient funds<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0* Account:\u00a0 0x090172CD36e9f4906Af17B2C36D662E69f162282<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0* Balance:\u00a0 0 wei<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0* Message:\u00a0 sender doesn’t have enough funds to send tx. The upfront cost is: 1410000000000000000 and the sender’s account only has: 0<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0* Try:<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0+ Using an adequately funded account<\/strong><\/p>\r\n\r\n\r\n\r\n

9. Contract Engagement Time<\/h4>\r\n\r\n\r\n\r\n

Congratulations! Your “Storage” contract is live and ready. Now, we’ll record a number there and retrieve it. This involves heading back to the console of Truffle:<\/p>\r\n\r\n\r\n\r\n

Now, let’s get a hold of the deployed contract “Storage”:<\/p>\r\n\r\n\r\n\r\n

truffle(development)> let instance = await Storage.deployed()<\/strong><\/p>\r\n\r\n\r\n\r\n

This action will return the following:<\/p>\r\n\r\n\r\n\r\n

undefined<\/strong><\/p>\r\n\r\n\r\n\r\n

The creation of a blockchain number<\/h5>\r\n\r\n\r\n\r\n

Now that you’ve got a hold of the “Storage” contract, you can use its “store” method to put a number onto the blockchain.\u00a0<\/p>\r\n\r\n\r\n\r\n

truffle(development)> instance.store(1234)<\/strong><\/p>\r\n\r\n\r\n\r\n

You’ll be dealing with code that looks a bit like this:<\/p>\r\n\r\n\r\n\r\n

{<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0tx: ‘0x10afbc5e0b9fa0c1ef1d9ec3cdd673e7947bd8760b22b8cdfe08f27f3a93ef1e’,<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0receipt: {<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0\u00a0blockHash: ‘0x8bacbce7c9d835db524bb856288e3a73a6afbe49ab34abd8cd8826db0240eb21’,<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0\u00a0blockNumber: 9,<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0\u00a0contractAddress: null,<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0\u00a0cumulativeGasUsed: 26458,<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0\u00a0from: ‘0x34cb796d4d6a3e7f41c4465c65b9056fe2d3b8fd’,<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0\u00a0gasUsed: 26458,<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0\u00a0logs: [],<\/strong><\/p>\r\n\r\n\r\n\r\n

\r\n

\u00a0logsBloom: ‘0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000’,<\/strong><\/p>\r\n<\/blockquote>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0\u00a0status: true,<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0\u00a0to: ‘0x0d507b0467baef742f9cc0e671eddbdf6df41d33’,<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0\u00a0transactionHash: ‘0x10afbc5e0b9fa0c1ef1d9ec3cdd673e7947bd8760b22b8cdfe08f27f3a93ef1e’,<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0\u00a0transactionIndex: 0,<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0\u00a0\u00a0rawLogs: []<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0},<\/strong><\/p>\r\n\r\n\r\n\r\n

\u00a0\u00a0logs: []<\/strong><\/p>\r\n\r\n\r\n\r\n

}<\/strong><\/p>\r\n\r\n\r\n\r\n

Blockchain Number Reading<\/h5>\r\n\r\n\r\n\r\n

To retrieve the number you stored on the blockchain, you can call the “retrieve” function on the contract “Storage” instance.<\/p>\r\n\r\n\r\n\r\n

truffle(development)> let i = await instance.retrieve()<\/strong><\/p>\r\n\r\n\r\n\r\n

You should expect to see this:<\/p>\r\n\r\n\r\n\r\n

undefined<\/strong><\/p>\r\n\r\n\r\n\r\n

Your “retrieve” call will yield a “BN” (big number). If you want to view the actual value, use its “.toNumber” function:<\/p>\r\n\r\n\r\n\r\n

truffle(development)> i.toNumber()<\/strong><\/p>\r\n\r\n\r\n\r\n

Voila! Your original blockchain number is now visible.\u00a0<\/p>\r\n\r\n\r\n\r\n

1234<\/strong><\/p>\r\n\r\n\r\n\r\n

It’s quite a journey, isn’t it? But remember, practice makes perfect. Keep going!<\/p>\r\n\r\n\r\n\r\n

Crafting the Blockchain Future with Webisoft’s Avalanche Services<\/h2>\r\n\r\n\r\n\r\n

Looking for innovative ways to unlock new business growth possibilities with the power of blockchain? Webisoft has you covered.\u00a0<\/p>\r\n\r\n\r\n\r\n

We’re all about offering a spectrum of blockchain development services<\/a> tailored to startups and companies eager to harness this revolutionary technology.\u00a0<\/p>\r\n\r\n\r\n\r\n

Whether it’s Avalanche, or any other top-notch blockchain system, our developers deliver nothing short of top-notch solutions that align with your vision.<\/p>\r\n\r\n\r\n\r\n

Bespoke Blockchain Solutions<\/h3>\r\n\r\n\r\n\r\n

Avalanche subnets’ virtual machines are our playground for developing bespoke public and private blockchains.<\/p>\r\n\r\n\r\n\r\n

Our services include setting up a node for the main network, developing subnets and virtual machines, and adding validation.\u00a0<\/p>\r\n\r\n\r\n\r\n

With Webisoft, get ready for a tailored blockchain experience.<\/p>\r\n\r\n\r\n\r\n

Unveiling dApps Potential<\/h3>\r\n\r\n\r\n\r\n

Our talented pool of developers have a knack for constructing DeFi dApps that are fit with Ethereum.<\/p>\r\n\r\n\r\n\r\n

Their technical acumen means you get polished dApps that enable trading of everything from traditional equities and commodities to alternative assets.<\/p>\r\n\r\n\r\n\r\n

Creating Smart Contracts with Solidity<\/h3>\r\n\r\n\r\n\r\n

Keeping our fingers on the pulse of Avalanche advancements and new integrations is second nature to our team.<\/p>\r\n\r\n\r\n\r\n

This proactive approach allows us to craft and execute solidity-matched smart contracts on Avalanche with finesse.\u00a0<\/p>\r\n\r\n\r\n\r\n

Our services encompass all the stages of smart contract development including audits, architecture design, and implementation.<\/p>\r\n\r\n\r\n\r\n

NFT Solutions \u2013 The Digital Frontier<\/h3>\r\n\r\n\r\n\r\n

The Webisoft blockchain wizards are adept at curating NFT solutions. We’re talking wallet integration, development of NFT marketplace, intuitive UI design, secure NFT storage solutions, and feature integrations for businesses rooted in blockchain.\u00a0<\/p>\r\n\r\n\r\n\r\n

Leveraging state-of-the-art blockchain technologies, such as Avalanche, we construct and launch robust NFT solutions.<\/p>\r\n\r\n\r\n\r\n

Wallet Development \u2013 The Key to Asset Management<\/h3>\r\n\r\n\r\n\r\n

Looking for a personalized, user-centric, and secure wallet for managing funds on the Avalanche network? Look no further.<\/p>\r\n\r\n\r\n\r\n

Our developers can whip up a custom Avalanche wallet that enables seamless receipt, asset transfer, and swapping.<\/p>\r\n\r\n\r\n\r\n

Final Words<\/h2>\r\n\r\n\r\n\r\n

Our expedition through the mountainous landscape of Avalanche smart contracts comes to a close. Along the way, we encountered a variety of tools and methods.<\/p>\r\n\r\n\r\n\r\n

We used Solidity for contract creation, Truffle for deployment and interaction, and learned to handle different errors like a pro.\u00a0<\/p>\r\n\r\n\r\n\r\n

You\u2019ve set up your local Avalanche network, and interacted with your smart contract using the Ethereum Virtual Machine.<\/p>\r\n\r\n\r\n\r\n

More importantly, you’ve successfully scaled the challenging heights of deploying and interacting with smart contracts on the Avalanche blockchain.\u00a0<\/p>\r\n\r\n\r\n\r\n

Remember, each journey enhances your understanding and skills in the rapidly evolving field of blockchain technology.<\/p>\r\n\r\n\r\n\r\n

Let this adventure be a stepping-stone for more advanced explorations into the breathtaking world of blockchain.<\/p>\r\n\r\n\r\n\r\n

Safe travels on your continued journey!Unleash the power of blockchain and transform your business with Webisoft<\/a>.<\/p>\r\n\r\n\r\n\r\n

Our expert developers are eager to provide top-tier Avalanche solutions, from custom dApps to NFT marketplace developments. Don’t let the blockchain revolution pass you by \u2013 connect with Webisoft today!<\/p>\r\n","protected":false},"excerpt":{"rendered":"

Let’s imagine for a moment you’re an explorer, standing at the edge of a vast, snow-capped mountain range. It’s vast,…<\/p>\n","protected":false},"author":1,"featured_media":14441,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[57],"tags":[],"class_list":["post-8474","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-smart-contracts"],"acf":[],"_links":{"self":[{"href":"https:\/\/blog.webisoft.com\/wp-json\/wp\/v2\/posts\/8474","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.webisoft.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.webisoft.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.webisoft.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.webisoft.com\/wp-json\/wp\/v2\/comments?post=8474"}],"version-history":[{"count":0,"href":"https:\/\/blog.webisoft.com\/wp-json\/wp\/v2\/posts\/8474\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.webisoft.com\/wp-json\/wp\/v2\/media\/14441"}],"wp:attachment":[{"href":"https:\/\/blog.webisoft.com\/wp-json\/wp\/v2\/media?parent=8474"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.webisoft.com\/wp-json\/wp\/v2\/categories?post=8474"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.webisoft.com\/wp-json\/wp\/v2\/tags?post=8474"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}