Whitepaper - Ethereum Classic With Cover

Ethereum Classic Documentation, Release 0.1
info Additional metadata output from the compiler
source The source code
language
languageVersion
compilerVersion
abiDefinition
userDoc
developerDoc
The contract language (Solidity, Serpent, LLL)
The contract language version
The solidity compiler version that was used to compile this contract.
The Application Binary Interface Definition
The NatSpec Doc for users.
The NatSpec Doc for developers.
The immediate structuring of the compiler output (into code and info) reflects the two very different paths of
deployment. The compiled EVM code is sent off to the blockchain with a contract creation transaction while the
rest (info) will ideally live on the decentralised cloud as publicly verifiable metadata complementing the code on
the blockchain.
If your source contains multiple contracts, the output will contain an entry for each contact, the corresponding
contract info object can be retrieved with the name of the contract as attribute name. You can try this by inspecting
the most current GlobalRegistrar code:
contracts = eth.compile.solidity(globalRegistrarSrc)
Create and deploy a contract
Before you begin this section, make sure you have both an unlocked account as well as some funds.
You will now create a contract on the blockchain by sending a transaction to the empty address with the EVM
code from the previous section as data.
Note: This can be accomplished much easier using the online Solidity realtime compiler or the Mix IDE program.
var primaryAddress = eth.accounts[0]
var abi = [{ constant: false, inputs: [{ name: 'a', type: 'uint256' } ]
var MyContract = eth.contract(abi)
var contract = MyContract.new(arg1, arg2, ..., {from: primaryAddress, data: evmByteCodeFromPreviou
All binary data is serialised in hexadecimal form. Hex strings always have a hex prefix 0x.
Note: Note that arg1, arg2, ... are the arguments for the contract constructor, in case it accepts any. If
the contract does not require any constructor arguments then these arguments can be omitted.
It is worth pointing out that this step requires you to pay for execution. Your balance on the account (that you put
as sender in the from field) will be reduced according to the gas rules of the EVM once your transaction makes
it into a block. After some time, your transaction should appear included in a block confirming that the state it
brought about is a consensus. Your contract now lives on the blockchain.
The asynchronous way of doing the same looks like this:
MyContract.new([arg1, arg2, ...,]{from: primaryAccount, data: evmCode}, function(err, contract) {
if (!err && contract.address)
console.log(contract.address);
});
82 Chapter 1. Contents