Ethereum startup screen
a brief history of etheric Classics (etc)
etheric classics began with an unfortunate event
in May 2016, the decentralized autonomous organization (DAO) held a token sale with the goal of establishing a blockchain based venture capital to fund future decentralized applications (dapps) in the Ethereum ecosystem
basically, Dao is a complex smart contract that operates in a decentralized way - computer code that automatically performs tasks between multiple parties when conditions are met
despite its ambitious goals and successful token sales, Dao's code has a major vulnerability that allows attackers to steal eth from decentralized organizations
the attacker took advantage of this vulnerability in June 2016, triggering the infamous Dao hacking event, and maliciously stole eth worth about US $50 million
there is no doubt that Dao hacking has shocked Ethereum community and made eth price drop from $20 to $13
after the Dao hacking, the Ethereum community has to choose from three options
< UL >do nothing and try to bear the consequences of the attack; Or
start soft bifurcation to recover funds; Or
deploy a hard fork to recover the lost eth
both soft and hard bifurcations are significant network upgrades. However, soft fork allows users who are not upgraded to communicate with upgraded users, while hard fork is not backward compatible with previous versions
as developers realize that deploying soft forks will expose the network to distributed denial of service (DDoS) attacks, Ethereum community decides to initiate hard forks to recover the funds lost in Dao hacking attacks
although this scheme is supported by most people, a small number of people in Ethereum community oppose it. They think that "code is the law" and blockchain network should be unchangeable
the failure of both sides to reach an agreement on the solution eventually led to the fragmentation of Ethereum blockchain
those who tried to recover the lost eth chose the hard fork and opened the Ethereum (ETH) blockchain as we know it today, while another group stayed on the original Ethereum classic (etc) chain
what problems does ethereal classic solve Ethernet classic (etc) is a blockchain platform that allows developers to deploy smart contracts and dapps although this function is the same as Ethereum (ETH), etc blockchain has two main differences first of all, Ethereum classic community opposes tampering with distributed ledger and supports the view that "blockchain network cannot and should not be modified" secondly, although there is no rigid upper limit on the total supply of eth, it is allowed to create 230 million etc at most by adopting the monetary policy of constant supply as a bonus item, ethereal classic launched Atlantis hard bifurcation last year to increase the interaction with Ethereum and improve the privacy protection of transactions through ZK snarks the trading platforms recommended by etc hot money, okex, AAX, etc
ether clown is a blockchain pet cultivation game launched by IAC advertising platform, which combines with pet entertainment to make money easily, and at the same time combines with blockchain technology to ensure the interests of players. Experience the fun of raising, working, earning and reselling, beautiful pictures, rich experience and happy income! Make a real game, let players get a more comfortable experience, with the game this well-known proct form, the human into the era of full intelligence
ether clown is a digital collection, a non-standard digital currency (ether currency, etc.), which is based on blockchain and can never be changed. It can be verified by a third-party platform to clearly query the relevant data information! Cryptoclow is a digital and collectable blockchain game based on Ethereum blockchain. Using ether money to adopt clowns can not only resell them, but also use them to breed a new generation of clowns with strange shapes. It can also cultivate them to work and earn money, making the digital collection of clowns more sustainable and playable# Ethereum clown#
built in smart contract compilation, linking, deployment and binary file management
automatic contract testing under rapid development
scripted and extensible deployment and publishing framework
the network environment management function deployed to no matter how many public or private networks
uses the package management provided by ethpm & NPM and erc190 standard
a direct interactive console that communicates directly with the contract (after writing the contract, you can verify it on the command line)
the configurable construction process supports tight integration
external scripts can be executed in truffle environment< Truffle is the most popular development framework, whose mission is to make development easier
installation method:
$NPM install - G truffle
environment requirements
nodejs 5.0 +
windows, Linux, or Mac OS X
truffle needs Ethereum client and supports standard JSON RPC API. For development, some are more suitable, which will be introced in the following chapters (for example, testrpc provides real-time feedback ring coding and debugging)
suggestions for Windows users
if you are a Windows user, we recommend that you use PowerShell or git bash to install and use the truffle framework. These two shell environments provide more convenient features than the default
if you have to use the command line, see the discussion here on how to configure truffle.
device = eth0 # to describe the device alias corresponding to the network card, For example, in the ifcfg-eth0 file, it sets the method of obtaining IP address for eth0
bootproto = static #. The possible options are static, DHCP or BOOTP, which correspond to the static IP address and the IP address obtained through the DHCP protocol, IP address obtained through BOOTP protocol
broadcast = 192.168.0.255 ｛ corresponding subnet broadcast address
hwaddr = 00:07: e9:05: E8: B4 ｛ corresponding NIC physical address
IPADDR = 12.168.1.2 ｛ if the IP address obtained by NIC is statically specified, this field specifies the IP address corresponding to NIC
ipv6init = no
IPv6_ Autoconf = no
netmask = 255.255.255.0 ｛ network mask corresponding to network card
Network = 192.168.1.0 ｛ network address corresponding to network card
onboot = yes ｛ whether this network interface is set when the system starts up; when it is set to yes, this device is activated when the system starts up