THIS IS INTENDED FOR RUNNING A LOCAL VERSION OF ETHEREUM FOR TESTING PURPOSES. IT HAS NOT BEEN TESTED HOW THIS SOFTWARE INTERACTS WITH THE REAL BLOCKCHAIN. DO NOT USE THIS ON A COMPUTER THAT RUNS A REAL ETHEREUM NODE SINCE YOU MAY RISK LOSING YOUR PRIVATE KEYS IF YOU DO NOT KNOW WHAT YOU ARE DOING!
Tools to avoid having to work in the Geth console directly
Currently we support OS X and Linux!
- Geth (https://github.com/ethereum/go-ethereum/wiki/geth)
- solc (https://solidity.readthedocs.io/en/develop/installing-solidity.html)
- Clone repo
- Go to geth_tools folder
- install cpanminus (
sudo apt-get install cpanminus) cpanm --installdeps .(remember the dot)- Run
run_geth.pl
You may need to run
cpanm --local-lib=~/perl5 local::lib && eval $(perl -I ~/perl5/lib/perl5/ -Mlocal::lib)
-- Alternatively run the install_on_linux bash script
Now a fully configured geth instance should be running in DEV mode. This running instance will only mine when there are transactions and it runs its own, local blockchain.
Solidity and Sword contracts can now be deployed by running compile_and_deploy.pl
Make sure a Geth client is running by starting the program ./run_geth.pl
Compile and deploy to a local version of the Ethereum blockchain:
./compile_and_deploy.pl <outdir> <source_code_file>
Run methods on the deployed smart contract:
./run_code.pl <outdir> <javascript_to_execute>
So a smart contract can be deployed and executed without having to interact with the geth console.
When writing JavaScript to execute, the deployed smart contracts are automatically put into scope. They may be referred to as "<contract_name>_", i.e., the contract name followed by an underscore. If the deployed contract has a constructor which has an argument with the name "tokenSymbol" or "dataFeedSymbol", the value of this constructor (which is set when executing compile_and_deploy.pl) will be part of the variable name such that this smart contract is referred to as <contract_name>_<tokenSymbol> or <contract_name>_<dataFeedSymbol> in the JavaScript. This is to allow the user to interact with several contracts of the same type but with different symbols, such as token contracts or data feed contracts.
./deploy_and_compile.pl contains a precompiler. This means that you when defining smart contracts can use keywords to access addresses of other smart contracts. The keyword "_address_my_" will be substituted with your own Ethereum address. The keyword "_address_<contract_name>_" will be substituted with the address of a contract that you have alread deployed. <contract>_<name> uses the same naming convention as the JavaScript does, as described in the section above.