The Ethereum Virtual Machine (EVM) is the runtime environment for smart contracts in Ethereum. It is a 256-bit register stack, designed to run the same code exactly as intended. It is the fundamental consensus mechanism for Ethereum. The formal definition of the EVM is specified in the Ethereum Yellow Paper.[34][37] On February 1, 2018, there were 27,500 nodes in the main Ethereum network.[38] Ethereum Virtual Machines have been implemented in C++, Go, Haskell, Java, JavaScript, Python, Ruby, Rust, Elixir, Erlang, and soon, WebAssembly (currently under development).
Both blockchains have the same features and are identical in every way up to a certain block where the hard-fork was implemented. This means that everything that happened on Ethereum up until the hard-fork is still valid on the Ethereum Classic Blockchain. From the block where the hard fork or change in code was executed onwards, the two blockchains act individually.
Third-party internet services called online wallets offer similar functionality but may be easier to use. In this case, credentials to access funds are stored with the online wallet provider rather than on the user's hardware.[97] As a result, the user must have complete trust in the online wallet provider. A malicious provider or a breach in server security may cause entrusted bitcoins to be stolen. An example of such a security breach occurred with Mt. Gox in 2011.[98]
Ethereum was initially described in a white paper by Vitalik Buterin,[10] a programmer involved with Bitcoin Magazine, in late 2013 with a goal of building decentralized applications.[11][12] Buterin had argued that Bitcoin needed a scripting language for application development. Failing to gain agreement, he proposed development of a new platform with a more general scripting language.[4]:88
لضمان صحّة عمليات التحويل، يقوم نظام البيتكوين بالاحتفاظ بسجل حسابات تُسجل فيه جميع الإجراءات التي تتم على الشبكة يُطلق عليه اسم سلسلة الكُتل (بالإنجليزية: block chain). تتشارك جميع العُقد المتواجدة على شبكة البيتكوين هذا السجل عبر نظام يعتمد على بروتوكول بِتكُيِن. تحتوي سلسلة الكُتل على جميع الإجراءات التي تمت باستخدام بِتكُيِن، وهو ما يُمكن من معرفة الرصيد الذي يملكه كل عنوان على هذه الشبكة. يُطلق على هذا المفهوم وصف السلسلة للترابط المتواجد ما بين الكُتل، حيث تحتوي كل كُتلة على هاش الكُتلة التي تسبقها ويتواصل الأمر إلى غاية الوصول إلى الكُتلة الأولى التي يُطلق عليها اسم "كتلة التكوين" (بالإنجليزية: genesis block) . تكوين السلسلة بهذه الطريقة يجعل من مهمة تغيير أي كُتلة بعد مرور مُدة مُعينة على إنشائها في غاية الصعوبة، حيث أن تغيير أي كُتلة يتطلب تغيير كل الكُتل التي تليها بسبب الحاجة إلى إعادة حساب هاش كل كُتلة لتحديث قيمة هاش الكُتلة السابقة فيها. هذه الخاصية هي ما يجعل من مُشكل الإنفاق المُتكرر لنفس العُملات في غاية الصعوبة على بِتكُيِن، بل ويُمكن اعتبار سلسلة الكُتل العمود الفقري الذي لا يُمكن لعُملة بِتكُيِن الوقوف من دونه[10].
As with other cryptocurrencies, the validity of each ether is provided by a blockchain, which is a continuously growing list of records, called blocks, which are linked and secured using cryptography.[30][31] By design, the blockchain is inherently resistant to modification of the data. It is an open, distributed ledger that records transactions between two parties efficiently and in a verifiable and permanent way.[32] Unlike Bitcoin, Ethereum operates using accounts and balances in a manner called state transitions. This does not rely upon unspent transaction outputs (UTXOs). State denotes the current balances of all accounts and extra data. State is not stored on the blockchain, it is stored in a separate Merkle Patricia tree. A cryptocurrency wallet stores the public and private "keys" or "addresses" which can be used to receive or spend ether. These can be generated through BIP 39 style mnemonics for a BIP 32 "HD Wallet". In Ethereum, this is unnecessary as it does not operate in a UTXO scheme. With the private key, it is possible to write in the blockchain, effectively making an ether transaction.
Both blockchains have the same features and are identical in every way up to a certain block where the hard-fork was implemented. This means that everything that happened on Ethereum up until the hard-fork is still valid on the Ethereum Classic Blockchain. From the block where the hard fork or change in code was executed onwards, the two blockchains act individually.
×