Æternity is a promising blockchain platform with great potential for many application scopes. One such great feature is the native support for state channels.
In this article we will explore how we built a peer-to-peer browser game to explore this Æternity capability; along examine related features of the platform such as ForgAE and companion tools and the Sophia functional contract development language
The purpose of this configuration is to generate a Docker environment of 2 nodes connected together running on Geth and monitor them using Ethstat (at localhost:3000). Then we can use MetaMask as well as Remix to connect to the first node (localhost:8545) to send simple transtractions, like sending Ether, or complex transactions like the creation or call of a smart contract.
In my last article, I’ve shown you how to make a Solidity ERC20 Token for the RSK Mainnet, how to import and use OpenZeppelin libraries and contracts, and how to use Truffle to deploy and interact with our contract.
Although we succeeded in our quest and accomplished our objectives using Truffle, eventually this suite might present failures when you are sending transactions, deploying or managing accounts. In our case, while following the previous article instructions, I’ve had problems managing newly created accounts in Truffle and sending transactions.
In the last article, we have seen how to build an RSK node in our computer, select the proper network for development, configure Truffle to connect and deploy our future contracts, add accounts to our node and obtain funds to use them to pay the gas.
You should have now your node in the selected network fully synced, and at least one account with funds configured in the truffle and RSK node config files for our deployments.
In this article, we’ll be discussing deployment and interaction of Smart-Contracts over the RSK network. Our contract will be an ERC20 Token, based on the OpenZeppelin libraries, and we will deploy it directly into the Mainnet.