News·Opentensor Blog·Oct 15, 2024, 22:13 UTC

EVM on Bittensor

Ethereum compatibility layer has arrived in the Bittensor ecosystem. Using this Bittensor feature you can:- Deploy and interact with any Ethereum smart contract, without any need to change it, on the subtensor blockchain. - Access all the standard Ethereum JSON-RPC methods from this EVM compatibility layer on Bittensor. When this EVM feature is turned ON, it allows the subtensor blockchain to execute Ethereum-compatible smart contracts. Note that all operations performed by this new subtensor EVM feature are executed solely on the subtensor blockchain, not on the Ethereum blockchain. This blog post explains in simple terms what this is and how it works. Head on over to EVM Tutorials section of Bittensor developer documentation to start playing with this feature. How an Ethereum smart contract works On the Ethereum network, nodes such as full nodes, validator nodes and archive nodes run the Ethereum Virtual Environment (EVM) run-time environment. Smart contracts operate under this EVM. See the below high-level diagram. To understand what it means to have a smart contract in Bittensor, it helps if we go over how one creates, deploys and interacts with a smart contract. The below overview is not meant to be comprehensive. Creating and deploying a smart contract on Ethereum As a developer, your developer journey would look like this: Step 1: Write a smart contract You write a smart contract code using a language like Solidity. The smart contract code defines the logic, functions, and state variables. Step 2: Compile the smart contract You compile the smart contract code locally using a compiler like Solc (Solidity compiler). Compilation converts the Solidity code into EVM bytecode. The compiler also generates an Application Binary Interface (ABI), a JSON file that describes the contract’s interface to the smart contract. Step 3: Deploy the smart contract To deploy the contract, you will create an Ethereum transaction. Your deployment transaction will contain: Recipient

Read the article at Opentensor Blog ↗

Taosis indexes announcements, articles and releases about Bittensor subnets from their own channels and keeps a record of each. The text above is the source’s; the figures are read from the chain by Taosis.