Install Ethereum Wallet
If you don’t have a clue about what is Ethereum or a smart contract, you.
What you will learn
- Where install ethereum wallet fits into an Ethereum application.
- Which assumptions should be tested before a mainnet deployment.
- What to read next when this concept is working.
If you don’t have a clue about what is Ethereum or a smart contract, you should first read what is Ethereum.
The fastest way to get started with Ethereum smart contract programing is Ethereum Wallet. It’s a native application available for Windows, MacOSX and Linux. You can download it from the Github project.
Key-handling choices can be tested against the private-key custody and recovery guide for Bitcoin.
Before anything, Ethereum Wallet needs to connect to the block chain and synchronize.
Once the sync is done choose the test network. On the test network any transaction will be done with test Ethereum so it does not cost you anything to develop. Keep in mind that while you are on the test network your contracts won’t be accessible from the normal Ethereum network.
A wallet design should distinguish signing keys from recovery material; see how Bitcoin private keys and seed phrases work.
Then you have to choose a password and don’t forget it. You don’t have to worry too much as the password will only affect the test network.
Once this is done you should see the Ethereum Wallet main screen displaying your account address and current balance which should be 0.
Social engineering often bypasses otherwise sound code. Compare the attack with the Bitcoin phishing and fraud warning guide.
On the test network you can easily get Ethereum by selecting in the menu Start mining.
Let the app run a little and you’ll see Ethereum in your account. It can takes around an hour to get your Ethereum. In the future, you will need a small amount of Ethereum to deploy your smart contracts to the blockchain and interact with them. You can now start writing your first smart contract.
Turn the example into production evidence
A working demo is the beginning of verification, not the end. Add tests for failure paths, inspect every permission, and record the chain, contract address, compiler, and dependency versions used for the deployment.
Check behavior
Test expected inputs, boundary values, reverts, events, and calls made to other contracts.
Check operations
Plan key storage, monitoring, pause or upgrade authority, and a response if an assumption stops being true.