├── LANGS.md
├── README.md
├── SUMMARY.md
├── book.json
├── cn
├── README.md
├── SUMMARY.md
└── [Chinese]-Ethereum-TOC.md
├── cover.jpg
├── de
├── README.md
├── SUMMARY.md
├── [German]-Clearinghaus.md
├── [German]-Ethereum-TOC.md
├── [German]-RLP.md
└── [German]-White-Paper.md
├── en
├── 1984 not a manual.jpg
├── 511fabd217df7170.png
├── 68747470733a2f2f7777772e7a656e6875622e696f2f626c6f672f636f6e74656e742f696d616765732f323031342f4f63742f4f7267616e697a65642d426f6172642e6a7067.jpeg
├── 75a077d5b29328e7.png
├── 7aa064deb75b8a8a.png
├── 8cae536fb9ea9dae.png
├── README.md
├── SUMMARY.md
├── Start with why.md
├── They why, How and What.md
├── a57b769af1448548.png
├── build_macos.md
├── build_ubuntu.md
├── build_windows.md
├── building_on_mac_os.md
├── building_on_ubuntu.md
├── building_on_windows.md
├── c64df7f3e1e2680b.png
├── design_philosophy.md
├── design_rationale.md
├── etherean_languages.md
├── ethereum_apis.md
├── ethereum_javascript_api.md
├── ethereum_json_rpc.md
├── ethereum_mining_algo.md
├── ethereumbuilders.md
├── get_involved.md
├── glossary.md
├── go_build.md
├── how_it_works.md
├── installing_ethereum.md
├── mac_build_cpp.md
├── mac_cpp_build.md
├── mac_go_build.md
├── manualbuild.md
├── open_collaboration_system.md
├── open_collaboration_welcomed.md
├── python_build.md
├── serpent.md
├── serpent_features.md
├── serpent_tutorials.md
├── single_smart_contracts.md
├── smart_contract_tutorials.md
├── smart_contracts_intro.md
├── smart_contracts_systems.md
├── solidity.md
├── solidity_features.md
├── solidity_tutorials.md
├── special_thanks.md
├── thank_you.md
├── this_is_a_knowledge_remix.md
├── tutorials
│ └── tutorials.md
├── ubuntu_cpp_build.md
├── ubuntu_go_build.md
├── under_the_hood.md
├── vitalik-diagrams
│ ├── SVG-files
│ │ ├── appecosystem.svg
│ │ ├── apply_block_diagram.svg
│ │ ├── apply_tx_diagram.svg
│ │ ├── asichome1.svg
│ │ ├── block.svg
│ │ ├── blockchain.svg
│ │ ├── centralized_multichain.svg
│ │ ├── chain_forks.svg
│ │ ├── chain_selection.svg
│ │ ├── chain_selection2.svg
│ │ ├── chain_selection3.svg
│ │ ├── chain_selection4.svg
│ │ ├── chain_selection5.svg
│ │ ├── chaindiag.svg
│ │ ├── clientserver.svg
│ │ ├── colored_coins_utxo_tree.svg
│ │ ├── contract_execution_flowchart.svg
│ │ ├── contract_relationship.svg
│ │ ├── contract_relationship2.svg
│ │ ├── cpuhome.svg
│ │ ├── cube.svg
│ │ ├── currency.svg
│ │ ├── ecthingy.svg
│ │ ├── endo1.svg
│ │ ├── endo10.svg
│ │ ├── endo2.svg
│ │ ├── endo20.svg
│ │ ├── endo3.svg
│ │ ├── endo30.svg
│ │ ├── endo4.svg
│ │ ├── endo5.svg
│ │ ├── entropy.svg
│ │ ├── ess1.svg
│ │ ├── ess2.svg
│ │ ├── ether_sale_process.svg
│ │ ├── ethertransition.svg
│ │ ├── executionpath.svg
│ │ ├── failurerate.svg
│ │ ├── fourpoints.svg
│ │ ├── futarchy.svg
│ │ ├── futarchy0.svg
│ │ ├── futarchy_bottom.svg
│ │ ├── futarchy_top.svg
│ │ ├── grandequation.svg
│ │ ├── grandequation2.svg
│ │ ├── heap1.svg
│ │ ├── heap2.svg
│ │ ├── heap20.svg
│ │ ├── heap3.svg
│ │ ├── heap4.svg
│ │ ├── heap5.svg
│ │ ├── heap6.svg
│ │ ├── hubchain.svg
│ │ ├── hubspoke.svg
│ │ ├── incentives.svg
│ │ ├── inflation.svg
│ │ ├── lightproof.svg
│ │ ├── liquidity.svg
│ │ ├── marginalsanctions.svg
│ │ ├── markov.svg
│ │ ├── merkle.svg
│ │ ├── merkle_basic.svg
│ │ ├── merkle_basic2.svg
│ │ ├── merklesum.svg
│ │ ├── merklesum2.svg
│ │ ├── miner_receives_block_flowchart.svg
│ │ ├── miner_receives_data_flowchart.svg
│ │ ├── minernet1.svg
│ │ ├── minernet2.svg
│ │ ├── minernet3.svg
│ │ ├── minernet4.svg
│ │ ├── minernet5.svg
│ │ ├── mining_process_flowchart.svg
│ │ ├── mofnsafety.svg
│ │ ├── multikdf.svg
│ │ ├── namereg.svg
│ │ ├── needforpreselection.svg
│ │ ├── orgs1.svg
│ │ ├── orgs2.svg
│ │ ├── orgs3.svg
│ │ ├── paretochart.svg
│ │ ├── paretoscaling.svg
│ │ ├── portfolio_replication.svg
│ │ ├── pos_checkpoints.svg
│ │ ├── pos_header.svg
│ │ ├── pos_selection2.svg
│ │ ├── pos_split.svg
│ │ ├── possec.svg
│ │ ├── pow_header.svg
│ │ ├── powsec.svg
│ │ ├── quadrant_chart.svg
│ │ ├── quadrant_chart2.svg
│ │ ├── readme.md
│ │ ├── roadmap.svg
│ │ ├── roadmap3.svg
│ │ ├── schellingcoin.svg
│ │ ├── schellingcoin_collective_payoff.svg
│ │ ├── schellingcoin_payoff1.svg
│ │ ├── schellingcoin_payoff2.svg
│ │ ├── schellingvote.svg
│ │ ├── scoringrule.svg
│ │ ├── secdao_accounts.svg
│ │ ├── secretmulitply3.svg
│ │ ├── secretmultiply.svg
│ │ ├── secretmultiply2.svg
│ │ ├── serpentcode.svg
│ │ ├── sha3repeat.svg
│ │ ├── shadowchain.svg
│ │ ├── sidechains.svg
│ │ ├── slasher1sec.svg
│ │ ├── slasher2sec.svg
│ │ ├── slasherghost.svg
│ │ ├── stacktrace.svg
│ │ ├── stake_low_influence.svg
│ │ ├── statetransition.svg
│ │ ├── strip.svg
│ │ ├── supplychart.svg
│ │ ├── threepoints.svg
│ │ ├── treap.svg
│ │ ├── treap2.svg
│ │ ├── twolines.svg
│ │ ├── twolinesum.svg
│ │ ├── twolinesum2.svg
│ │ ├── twopoints.svg
│ │ ├── tworound.svg
│ │ ├── tx.svg
│ │ ├── txbatch.svg
│ │ ├── utilitychart.svg
│ │ └── where_to_mine.svg
│ ├── appecosystem.png
│ ├── apply_block_diagram.png
│ ├── apply_tx_diagram.png
│ ├── asichome1.png
│ ├── barmodel.png
│ ├── bitcoin_price_chart.png
│ ├── block.png
│ ├── blockchain.png
│ ├── centralized_multichain.png
│ ├── chain_forks.png
│ ├── chain_selection.png
│ ├── chain_selection2.png
│ ├── chain_selection3.png
│ ├── chain_selection4.png
│ ├── chain_selection5.png
│ ├── chaindiag.png
│ ├── clientserver.png
│ ├── colored_coins_utxo_tree.png
│ ├── contract_execution_flowchart.png
│ ├── contract_relationship.png
│ ├── contract_relationship2.png
│ ├── cpuhome.png
│ ├── cube.png
│ ├── currency.png
│ ├── ecthingy.png
│ ├── endo1.png
│ ├── endo1.svg.png
│ ├── endo10.svg.png
│ ├── endo2.svg.png
│ ├── endo20.svg.png
│ ├── endo3.svg.png
│ ├── endo30.svg.png
│ ├── endo4.svg.png
│ ├── endo5.svg.png
│ ├── entropy.png
│ ├── ess1.png
│ ├── ess2.png
│ ├── ether_sale_process.png
│ ├── etherscriper.png
│ ├── ethertransition.png
│ ├── executionpath.png
│ ├── failurerate.png
│ ├── fault_tolerance_1.png
│ ├── fault_tolerance_2.png
│ ├── fourpoints.png
│ ├── futarchy.png
│ ├── futarchy0.png
│ ├── futarchy_bottom.png
│ ├── futarchy_top.png
│ ├── grandequation.png
│ ├── grandequation2.png
│ ├── heap1.png
│ ├── heap2.png
│ ├── heap20.png
│ ├── heap3.png
│ ├── heap4.png
│ ├── heap5.png
│ ├── heap6.png
│ ├── hubchain.png
│ ├── hubspoke.png
│ ├── image2.png
│ ├── incentives.png
│ ├── inflation.png
│ ├── lightproof.png
│ ├── liquidity.png
│ ├── marginalsanctions.png
│ ├── markov.png
│ ├── merkle.png
│ ├── merkle_basic.png
│ ├── merkle_basic2.png
│ ├── merklesum.png
│ ├── merklesum2.png
│ ├── messenger.png
│ ├── miner_receives_block_flowchart.png
│ ├── miner_receives_data_flowchart.png
│ ├── minernet1.png
│ ├── minernet2.png
│ ├── minernet3.png
│ ├── minernet4.png
│ ├── minernet5.png
│ ├── mining.jpg
│ ├── mining_process_flowchart.png
│ ├── mofnsafety.png
│ ├── multikdf.png
│ ├── namereg.png
│ ├── needforpreselection.png
│ ├── orgs1.png
│ ├── orgs2.png
│ ├── orgs3.png
│ ├── paretochart.png
│ ├── paretoscaling.png
│ ├── pools.png
│ ├── portfolio_replication.png
│ ├── pos_checkpoints.png
│ ├── pos_header.png
│ ├── pos_selection2.png
│ ├── pos_split.png
│ ├── pow_header.png
│ ├── powsec.png
│ ├── quadrant_chart.png
│ ├── quadrant_chart2.png
│ ├── readme.md
│ ├── roadmap.png
│ ├── roadmap3.png
│ ├── schellingcoin.png
│ ├── schellingcoin_collective_payoff.png
│ ├── schellingcoin_payoff1.png
│ ├── schellingcoin_payoff2.png
│ ├── schellingvote.png
│ ├── scoringrule.png
│ ├── secdao_accounts.png
│ ├── secretmulitply3.png
│ ├── secretmultiply.png
│ ├── secretmultiply2.png
│ ├── serpentcode.png
│ ├── sha3repeat.png
│ ├── shadowchain.png
│ ├── sidechains.png
│ ├── slasher1sec.png
│ ├── slasher2sec.png
│ ├── slasherghost.png
│ ├── spv1.png
│ ├── spv2.png
│ ├── stacktrace.png
│ ├── stake_low_influence.png
│ ├── statetransition.png
│ ├── strip.png
│ ├── supplychart.png
│ ├── threepoints.png
│ ├── treap.png
│ ├── treap2.png
│ ├── twolines.png
│ ├── twolinesum.png
│ ├── twolinesum2.png
│ ├── twopoints.png
│ ├── tworound.png
│ ├── tx.png
│ ├── txbatch.png
│ ├── utilitychart.png
│ └── where_to_mine.png
├── what_is_ethereum.md
├── whitepaper.md
├── win_cpp_build.md
└── win_go_build.md
├── es
├── README.md
├── SUMMARY.md
└── [Spanish]-Ethereum-TOC.md
├── fr
├── README.md
└── SUMMARY.md
├── it
├── README.md
├── SUMMARY.md
├── [Italian] Impostare il proprio ambiente di sviluppo Ethereum.md
├── [Italian] Introduzione allo sviluppo su Ethereum.md
├── [Italian] Tutorials sui contratti intelligenti.md
├── [Italian] caratteristiche di Solidity.md
├── [Italian] caratteristiche di serpent.md
├── [Italian] ethereum apis.md
├── [Italian] glossario.md
├── [Italian] installazione su Mac.md
├── [Italian] installazione su Ubuntu.md
├── [Italian] installazione su Windows.md
├── [Italian] l'imperativo di business dietro la visione di Ethereum.md
├── [Italian]-Ethereum-TOC.md
├── [Italian]-Libro-Bianco.md
├── [Italian]-Libro-Giallo.md
├── [Italian]-cosa-e-ethereum.md
├── [Italian]-ethereum_javascript_api.md
├── [Italian]-ethereum_json_rpc.md
├── [Italian]-installare_ethereum.md
├── [Italian]-mac_cpp_build.md
├── [Italian]-mac_go_build.md
├── [Italian]-ringraziamenti.md
├── [Italian]-ringraziamenti_speciali.md
├── [Italian]-ripasso_conoscitivo.md
├── [Italian]-ubuntu_cpp_build.md
├── [Italian]-ubuntu_go_build.md
├── [Italian]-win_cpp_build.md
├── [Italian]-win_go_build.md
├── [Italian]Cos_e_Ethereum.md
├── [Italian]Design_rationale.md
├── [Italian]La_filosofia_di_progettazione_di_Ethereum.md
├── [Italian]_Tutorials_su_Serpent.md
├── [Italian]_Tutorials_su_Solidity.md
├── [Italian]benvenute_collaborazioni.md
├── [Italian]il_perche_il_come_il_quando.md
└── [Italiano] Appunti sulla Scalabilità dei Protocolli Blockchain.md
├── jp
├── README.md
└── SUMMARY.md
├── kr
├── README.md
└── SUMMARY.md
└── ro
├── README.md
└── SUMMARY.md
/LANGS.md:
--------------------------------------------------------------------------------
1 | ### Choose your language
2 |
3 | * [English](en)
4 | * [Chinese](cn)
5 | * [Español](es)
6 | * [Italian](it)
7 | * [German](de)
8 | * [French](fr)
9 | * [Romanian](ro)
10 | * [Japanese](jp)
11 | * [Korean](kr)
12 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | ###**This guide is still under heavy development.*
2 |
3 | Into the ether
4 | =======
5 |
6 | ###Continuing the experiment ...
7 |
8 | When the grand experiment that is Bitcoin began, the anonymous wizard desired to test two parameters:
9 |
10 | 1. **a trustless, decentralized database enjoying security enforced by the austere relentlessness of cryptography**
11 |
12 | 2. **a robust transaction system capable of sending value across the world without intermediaries.**
13 |
14 | Yet the past five years years have painfully demonstrated a **_third_ missing feature: a sufficiently powerful Turing-complete scripting language**. Up until this point, most innovation in advanced applications such as domain and identity registration, user-issued currencies, smart property, smart contracts, and decentralized exchange has been highly fragmented, and implementing any of these technologies has required creating an entire meta-protocol layer or even a specialized blockchain. Theoretically, however, each and every one of these innovations and more can potentially be made hundreds of times easier to implement, and easier to scale, if only there was a stronger foundational layer with a powerful scripting language for all of these protocols to build upon. And this need is what we seek to satisfy.
15 |
16 | Ethereum is a modular, stateful, Turing-complete contract scripting system married to a blockchain and developed with a philosophy of simplicity, universal accessibility and generalization. Our goal is to provide a platform for decentralized applications - an android of the cryptocurrency world, where all efforts can share a common set of APIs, trustless interactions and no compromises.
17 |
18 | ###... together
19 |
20 | During the past year there have been a number of developers and researchers who have either worked for Ethereum or working on ideas as volunteers and happen to spend lots of time interacting with the Ethereum community, and this set of people has coalesced into a group dedicated to building out the vision set by Vitalik Buterin in the Ethereum Whitepaper.
21 |
22 | We ask for the community to join us as volunteers, developers, investors and evangelists seeking to enable a fundamentally different paradigm for the Internet and the relationships it provides.
23 |
24 |
--------------------------------------------------------------------------------
/SUMMARY.md:
--------------------------------------------------------------------------------
1 | # Summary
2 |
3 | * [Introduction](README.md)
4 | * [Thank you.](thank_you.md)
5 | * [This is a knowledge remix](this_is_a_knowledge_remix.md)
6 | * [Special Thanks](special_thanks.md)
7 | * [Open Collaboration Welcomed](open_collaboration_welcomed.md)
8 | * [The Why, How and What](They why, How and What.md)
9 | * [Ethereum design philosophy](design_philosophy.md)
10 | * [Design rationale](design_rationale.md)
11 | * [What can you do with it?](what_is_ethereum.md)
12 | * [Installing Ethereum Client](installing_ethereum.md)
13 | * [Building on Ubuntu](building_on_ubuntu.md)
14 | * [C++](ubuntu_cpp_build.md)
15 | * [Go](ubuntu_go_build.md)
16 | * [Building on Mac OS](building_on_mac_os.md)
17 | * [C++](mac_cpp_build.md)
18 | * [Go](mac_go_build.md)
19 | * [Building on Windows](building_on_windows.md)
20 | * [C++](win_cpp_build.md)
21 | * [Go](win_go_build.md)
22 | * [Ethereum APIs](ethereum_apis.md)
23 | * [JSON RPC API](ethereum_json_rpc.md)
24 | * [Javascript API](ethereum_javascript_api.md)
25 | * [Smart Contracts](smart_contract_tutorials.md)
26 | * [Solidity Features](solidity_features.md)
27 | * [Serpent Features](serpent_features.md)
28 | * [Serpent Tutorials](serpent_tutorials.md)
29 | * [Solidity Tutorials](solidity_tutorials.md)
30 | * Resources
31 | * [Whitepaper](whitepaper.md)
32 | * [Glossary](glossary.md)
33 | * [Ξaster Egg](vitalik-diagrams/readme.md)
34 |
35 |
--------------------------------------------------------------------------------
/book.json:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/book.json
--------------------------------------------------------------------------------
/cn/README.md:
--------------------------------------------------------------------------------
1 | ###**本指南是不断发展.*
2 |
3 | Ethereum builders 指导
4 | =======
5 |
--------------------------------------------------------------------------------
/cn/SUMMARY.md:
--------------------------------------------------------------------------------
1 | # Sumar
2 |
3 | * [Introducere](README.md)
4 | * [Thank you.](thank_you.md)
5 | * [This is a knowledge remix](this_is_a_knowledge_remix.md)
6 | * [Multumiri speciale](special_thanks.md)
7 | * [Open Collaboration Welcomed](open_collaboration_welcomed.md)
8 | * [The Why, How and What](They why, How and What.md)
9 | * [Ethereum design philosophy](design_philosophy.md)
10 | * [Design rationale](design_rationale.md)
11 | * [What can you do with it?](what_is_ethereum.md)
12 | * [Installing Ethereum Client](installing_ethereum.md)
13 | * [Build pe Ubuntu](building_on_ubuntu.md)
14 | * [C++](ubuntu_cpp_build.md)
15 | * [Go](ubuntu_go_build.md)
16 | * [Build pe Mac OS](building_on_mac_os.md)
17 | * [C++](mac_cpp_build.md)
18 | * [Go](mac_go_build.md)
19 | * [Build pe Windows](building_on_windows.md)
20 | * [C++](win_cpp_build.md)
21 | * [Go](win_go_build.md)
22 | * [API-uri Ethereum](ethereum_apis.md)
23 | * [JSON RPC API](ethereum_json_rpc.md)
24 | * [Javascript API](ethereum_javascript_api.md)
25 | * [Smart Contracts](smart_contract_tutorials.md)
26 | * [Solidity Features](solidity_features.md)
27 | * [Serpent Features](serpent_features.md)
28 | * [Serpent Tutorials](serpent_tutorials.md)
29 | * [Solidity Tutorials](solidity_tutorials.md)
30 | * Resurse
31 | * [Whitepaper](whitepaper.md)
32 | * [Glosar](glossary.md)
33 |
34 |
--------------------------------------------------------------------------------
/cn/[Chinese]-Ethereum-TOC.md:
--------------------------------------------------------------------------------
1 | 中文读者可以在[以太中国](www.ethchina.org)和[中文论坛](www.1tf.org)获知最新信息。
2 |
3 | 白皮书:[以太坊(Ethereum ):下一代智能合约和去中心化应用平台](https://github.com/ethereum/wiki/wiki/White-Paper-%5BChinese%5D)
4 |
5 | [Serpent语言指南](https://github.com/ethereum/wiki/wiki/%5B%E4%B8%AD%E6%96%87%5D-Serpent%E6%8C%87%E5%8D%97)
6 |
7 | [以太坊开发计划](https://github.com/ethereum/wiki/wiki/%E4%BB%A5%E5%A4%AA%E5%9D%8A%E5%BC%80%E5%8F%91%E8%AE%A1%E5%88%92)
8 |
9 | [术语表](https://github.com/ethereum/wiki/wiki/%E6%9C%AF%E8%AF%AD%E8%A1%A8)
--------------------------------------------------------------------------------
/cover.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/cover.jpg
--------------------------------------------------------------------------------
/de/README.md:
--------------------------------------------------------------------------------
1 | ###**Dieser Leitfaden ist noch in der Entwicklung.*
2 |
3 | Ethereum builders Führung
4 | =======
5 |
--------------------------------------------------------------------------------
/de/SUMMARY.md:
--------------------------------------------------------------------------------
1 | # Sumar
2 |
3 | * [Introducere](README.md)
4 | * [Thank you.](thank_you.md)
5 | * [This is a knowledge remix](this_is_a_knowledge_remix.md)
6 | * [Multumiri speciale](special_thanks.md)
7 | * [Open Collaboration Welcomed](open_collaboration_welcomed.md)
8 | * [The Why, How and What](They why, How and What.md)
9 | * [Ethereum design philosophy](design_philosophy.md)
10 | * [Design rationale](design_rationale.md)
11 | * [What can you do with it?](what_is_ethereum.md)
12 | * [Installing Ethereum Client](installing_ethereum.md)
13 | * [Build pe Ubuntu](building_on_ubuntu.md)
14 | * [C++](ubuntu_cpp_build.md)
15 | * [Go](ubuntu_go_build.md)
16 | * [Build pe Mac OS](building_on_mac_os.md)
17 | * [C++](mac_cpp_build.md)
18 | * [Go](mac_go_build.md)
19 | * [Build pe Windows](building_on_windows.md)
20 | * [C++](win_cpp_build.md)
21 | * [Go](win_go_build.md)
22 | * [API-uri Ethereum](ethereum_apis.md)
23 | * [JSON RPC API](ethereum_json_rpc.md)
24 | * [Javascript API](ethereum_javascript_api.md)
25 | * [Smart Contracts](smart_contract_tutorials.md)
26 | * [Solidity Features](solidity_features.md)
27 | * [Serpent Features](serpent_features.md)
28 | * [Serpent Tutorials](serpent_tutorials.md)
29 | * [Solidity Tutorials](solidity_tutorials.md)
30 | * Resurse
31 | * [Whitepaper](whitepaper.md)
32 | * [Glosar](glossary.md)
33 |
34 |
--------------------------------------------------------------------------------
/de/[German]-Clearinghaus.md:
--------------------------------------------------------------------------------
1 | ### Einleitung
2 | Bei manchen Finanzinstrumente wie ["Future"] (http://de.wikipedia.org/wiki/Future) (keine Geldtermingeschäfte) können sich die Parteien gegen Zahlungsausfälle gegenüber dem Geschäftspartner (i.d.R. bei einem Clearinghaus) absichern. Im Wesentlichen liefert eine Clearingstelle diese Garantie über ein Verfahren, bei dem die Gewinne und Verluste, die sich aus dem börslichen Handel dieser Features über die Vertragslaufzeit ergeben, durch tägliche Abrechnung in Bargeld umgewandelt werden.
3 | ### Tägliche Abrechnung
4 | Wie erklärt, wird die "tägliche Abrechnung" von Gewinnen oder Verlusten in Bargeld konvertiert. Dieser Vorgang wird auch ** Marktbewertung ** bezeichnet und lässt sich am Besten über ein Beispiel veranschaulichen.
5 | Angenommen zwei Parteien gehen einen Vertrag ein, einen [Vertragsgegenstand] (http://de.wikipedia.org/wiki/Underlying) zu einem vereinbarten Preis von 100 USD in einem Monat zu kaufen/verkaufen. Um diesen Vertrag einzugehen verlangt die Clearingstelle einen Vorschuss beider Partein, die diesen vorab begleichen müssen. Also die Partei, die den Vertragsgegenstand kaufen will [(** Halter der long position **)] (http://de.wikipedia.org/wiki/Long_und_Short) und die Partei, die den Vertragsgegenstand verkaufen will [(** Halter der short position **)] (http://de.wikipedia.org/wiki/Long_und_Short).
6 | Die Vorschusszahlung möge 5 USD betragen und wird einbezahlt in einen **margin account** des Clearinghauses, gebunden an den spezifischen Vertrag.
7 | Während der Laufzeit des Vertrags variiert der Betrag auf dem **margin account**. Die in dem Vertrag involvierten Parteien müssen das Guthaben des **margin account** über einem bestimmten Level halten, genannt **maintenance margin requirement**, der von dem Clearinghaus bestimmt wird und i.d.R. unterhalb der Höhe des Zahlungsvorschusses liegt.
8 | Am Ende eines jeden Tages wird die Clearingstelle einen ** Abrechnungspreis ** bieten (in der Regel ein Durchschnittspreis aller Trades, die im Laufe des Tages passiert sind) um dann das ** Mark-to-Market-Verfahren ** (tägliche Abrechnungs) durchzuführen.
9 | In unserem konkreten Beispiel nehmen wir an, dass die Höhe der Sicherheitsleistung, die nicht unterschritten werden darf (**maintenance margin requirement**) auf einen Betrag von 3 USD festgelegt wird und die kaufende Partei 10 Verträge eingeht. D.h. es wird eine Vorschusszahlung von 10 x 5 USD = 50 USD fällig. Wir gehen auch davon aus, dass das Geld von der Clearingstelle nicht zurückgebucht werden kann (z.B. Überschüsse). Der Initialpreis (des Future Contracts) beträgt 100 USD.
10 | Ein vollständiges beispiel zeigt die folgende Tabelle. Es sei darauf hingeweisen, dass beide Tafeln die täglichen Salden beider Partein berichten (long position und short position).
11 | #### Tafel A. Halter der Long Position von 10 Verträgen
12 | |Tag (1)|Startsaldo (2)|Vorschusszahlung (3)|[Settlementpreis](http://boerse.ard.de/boersenwissen/boersenlexikon/settlement-preis-100.html) (4)| Änderung des Preises des (5)|Gewinn/Verlust (6)|Endsaldo (7)|
13 | |:----------:|-------------:|------:|---:|---:|---:|---:|
14 | |0|0|50|100.0| - | - |50|
15 | |1|50|0|99.20| -0.80| -8|42|
16 | |2|42|0|96.00| -3.20| -32|10|
17 | |3|10|40|101.00|5.00|50|100|
18 | |4|100|0|103.50|2.50|25|125|
19 | |5|125|0|103.00| -0.50| -5|120|
20 | |6|120|0|104.00|1.00|10|130|
21 | #### Tafel B. Halter der Short Position von 10 Verträgen
22 | |Tag (1)|Startsaldo (2)|Vorschusszahlung (3)|[Settlementpreis](http://boerse.ard.de/boersenwissen/boersenlexikon/settlement-preis-100.html) (4)| Änderung des Preises des (5)|Gewinn/Verlust (6)|Endsaldo (7)|
23 | |:----------:|-------------:|------:|---:|---:|---:|---:|
24 | |0|0|50|100.0| -| -|50
25 | |1|50|0|99.20| -0.80|8|58
26 | |2|58|0|96.00| -3.20|32|90
27 | |3|90|0|101.00|5.00| -50|40
28 | |4|40|0|103.50|2.50| -25| 15
29 | |5|15|35|103.00| -0.50| 5|55
30 | |6|55|0|104.00|1.00| -10|45|}
31 | Der Tag des Vertragsabschlusses wird als'' Tag 0'' bezeichnet, an dem beide Parteien eine Vorschusszahlung von 50 USD hinterlegen. Wir nehmen an, dass am "Tag 1" der Preis des Futures auf 99,20 USD fällt, wie in Spalte 4 der Tafel A angegeben. In Spalte 5 können wir die Änderung des Preises des Futures sehen -0,80 USD (99,20 - 100) und dieser Betrag wird mit der Zahl der Verträge (10) multipliziert um in Spalte 6 den Gewinn/Verlust zu erhalten: -0,80 x 10 = - 8 USD. Der Endsaldo ist in Spalte 7 zu sehen, welcher dem Anfangssaldo des nächsten Tages entspricht. Der Endsaldo am Tag 1 für den Inhaber der Long-Position ist 42 USD und liegt somit über dem Mindestsaldo der Sicherheitsleistung (**maintenance margin**) von 3 x 10 USD = 30 USD, so dass keine Nachschuss erforderlich ist, um über diesen Wert zu kommen.
32 | ### Ethereum Clearinghaus Implementierung und Logik
33 | * gilt es für alle Verträge?
34 | * welches Falg muss gesetzt werden um die Clearinghaus zu ermöglichen?
35 | * wie werden das Geld / Ether belastet / gutgeschrieben? Push oder Pull System?
36 | * Normalerweise verwenden Clearinghäuser einen durchschnittlichen Tagespreis (nicht den Abschlusspreis). Wie ist das umsetzen? Dies ist wichtig um Preismanipulation zu VERMEIDEN! Ethereum würde noch mehr gefährdet sein als klassische Clearingstellen.
37 | * Was passiert im Falle des Ausfalls (fehlerhafte Nachschussaufforderung)? Reputationssystem?
38 | * viele Verträge benötigen einen externen Marktkurs (z.B. Goldpreis von CME oder LIBOR, kinssätze). Wie können sie damit gefüttert werden?
39 | * kann Geld von der Clearingstelle zurückgebucht werden (z.B. überschüssige Mittel / Gewinne)? Es wäre einfacher, wenn dies nicht der Fall wäre.
40 | * Was ist, wenn die Parteien wirklich den Vertragsgegenstand austauschen wollen? Z.B. keine Bargeld- / Ether- Abmachungen? (NICHT SUPPORTED VOM CLEARINGHAUS)
41 | * Verluste / Gewinne werden durch durch die von der Clearingstelle zur Verfügung gestellten Hebel von Natur aus vergrößert. AKZEPTABEL FUER ETHERUEM? HINWEIS: OBWOHL DIE VOLLSTÄDIGE SUMME NICHT VORAB HINTERLEGT WERDEN BRAUCHT
42 | ### Code reference sample
43 |
--------------------------------------------------------------------------------
/de/[German]-Ethereum-TOC.md:
--------------------------------------------------------------------------------
1 | ### Willkommen bei Ethereum, der nächsten Generation von elektronischen Verträgen und der Plattform für dezentrale Anwendungen.
2 |
3 | [Ethereum whitepaper](https://github.com/ethereum/wiki/wiki/%5BGerman%5D-White-Paper)
4 |
5 | [RLP](https://github.com/ethereum/wiki/wiki/%5BEnglish%5D-RLP), die Recursive Linear Prefix - Spezifikation für Kodierung der Daten ation, used for data encoding bei Ethereum.
6 |
7 | [Patricia Tree](https://github.com/ethereum/wiki/wiki/%5BEnglish%5D-Patricia-Tree), die Spezifikation des Merkle Patricia Baums (aka Trie), die Struktur zum Speichern und Hashen der Blockkette in Ethereum.
8 |
9 | [Wire protocol](https://github.com/ethereum/wiki/wiki/%5BEnglish%5D-Wire-Protocol) Spezifikation.
10 |
11 | [CLL](https://github.com/ethereum/wiki/wiki/%5BEnglish%5D-CLL), die Spezifikation der "C-ähnlichen Programmiersprache" für die Gestaltung von Verträgen.
12 |
13 | [Dagger](https://github.com/ethereum/wiki/wiki/%5BEnglish%5D-Dagger), die "proof-of-work" Spezifikation Ethereums.
14 |
15 | [Block Protocol 2.0](https://github.com/ethereum/wiki/wiki/%5BEnglish%5D-Block-Protocol-2.0)
16 |
17 | [Layers](https://github.com/ethereum/wiki/wiki/%5BEnglish%5D-Layers)
18 |
19 | [Clearinghaus](https://github.com/ethereum/wiki/wiki/%5BGerman%5D-Clearinghaus)
20 |
--------------------------------------------------------------------------------
/de/[German]-RLP.md:
--------------------------------------------------------------------------------
1 | Der Zweck von RLP ist es, beliebig verschachtelte Arrays von binären Daten zu kodieren. RLP wird als Hauptcodierungsverfahren verwendet, um Objekte in Etherieum in serieller Reihenfolge zu kodieren. Das heisst RLP kodiert Strukturen, spezielle Datentypen wie [Strings] (http://de.wikipedia.org/wiki/Zeichenkette), [Integers] (http://de.wikipedia.org/wiki/Integer_%28Datentyp%29) und [Floats] (http://de.wikipedia.org/wiki/Gleitkommazahl), bis hin zu höheren Protokollebenen. Integer werden in Ethereum standardmäßig im [Big Endian] (http://de.wikipedia.org/wiki/Byte-Reihenfolge) Binärfomat verarbeitet.
2 | Wenn man RLP z.B. zum Kodieren eines Wörterbuchs verwendet, sind die beiden vorgeschalgenen Standardformen entweder `[[k1, v1], [k2, v2] ...]` mit Schlüsselwörtern in lexikographische Ordnung oder besser die Kodierung des [Patricia Baums] (https://github.com/ethereum/wiki/wiki/Patricia-Tree) (wie es Eutherium tut).
3 |
4 | ### Definition
5 | Die RLP-Koding erfolgt in einem Element. Ein Element wird wie folgt definiert:
6 |
7 | * Ein String (z.B. eine Byte Array) ist ein Element
8 | * Eine Liste von Elementen ist ein Elemet
9 |
10 | Elemente können z.B. sein:
11 | - ein leerer String
12 | - ein String mit dem Wort "cat"
13 | - eine Liste von beliebig vielen anderen Zeichen
14 | - komplexere Daten wie `["cat",["puppy","cow"],"horse",[[]],"pig",[""],"sheep"]`.
15 |
16 | Bitte beachten: In dem Rest dieses Artikels wird "String" als Synonym für "eine bestimmte Anzahl von Bytes von binären Daten" verwendet. Es wird keine besondere Kodierung betrachtet und auch nichts über den Inhalt des Strings ausgesagt.
17 |
18 | Die RLP-Kodierung funktioniert wie folgt:
19 | * Für ein einzelnes Byte innerhalb des Bereiches `[0x00, 0x7f]` erfolgt eine individuelle RLP-Kodierung.
20 | * Ist ein String 0 bis 55 Byte lang enthält die RLP-Kodierung den Wert **0x80** + die Länge des Strings, gefolgt vom Stringinhalt. Der Wertebereich des ersten Bytes ist `[0x80, 0xb7]`.
21 | * Ist ein String länger als 55 Byte, enthält die RLP-Kodierung das erste Byte mit dem Wert **0xb7** + die Länge für String+Stringlänge in Binärformat, gefolgt von der Länge des Strings, gefolgt vom Stringinhalt. Z.B. ein 1024 Byte langer String wird kodiert als `\xb9\x04\x00` gefolgt vom Stringinhalt. Der Wertebereich des ersten Bytes ist `[0xb8, 0xbf]`.
22 | * Ist die Gesamtlänge der Nutzdaten einer Liste (z.B. die kombinierte Länge aller Elemente) zwischen 0 und 55 Bytes, enthält die RLP-Kodierung das Byte mit dem Inhalt **0xc0** + die Länge der Liste, gefolgt von der Verkettung der RLP-Kodierungen der Elemente. Der Wertebereich des ersten Bytes ist `[0xc0, 0xf7]`.
23 | * Ist die Gesamtlänge der Nutzdaten einer Liste mehr als 55 Byte, enthält die RLP-Kodierung das Byte mit dem Inhalt **0xf7** + die Länge für Liste+Listenlänge in Binärformat, gefolgt von der Länge der Liste, gefolgt von der Verkettung der RLP-Kodierungen der Elemente. Der Wertebereich des ersten Bytes ist `[0xf8, 0xff]`.
24 | Als Code sieht das so aus:
25 | ```python
26 | def rlp_encode(input):
27 | if isinstance(input,str):
28 | if len(input) == 1 and chr(input) < 128: return input
29 | else: return encode_length(len(input),128) + input
30 | elif isinstance(input,list):
31 | output = encode_length(len(input),192)
32 | for item in input: output += rlp_encode(item)
33 | return output
34 | def encode_length(L,offset):
35 | if L < 56:
36 | return chr(L + offset)
37 | elif L < 256**8:
38 | BL = to_binary(L)
39 | return chr(len(BL) + offset + 55) + BL
40 | else:
41 | raise Exception("input too long")
42 | def to_binary(x):
43 | return '' if x == 0 else to_binary(int(x / 256)) + chr(x % 256)
44 | ```
45 | ### Beispiele
46 |
47 | Der String "dog" = [ 0x83, 'd', 'o', 'g' ]
48 |
49 | Die Liste [ "cat", "dog" ] = `[ 0xc8, 0x83, 'c', 'a', 't', 0x83, 'd', 'o', 'g' ]`
50 |
51 | Der leere String ('null') = `[ 0x80 ]`
52 |
53 | Die leere Liste = `[ 0xc0 ]`
54 |
55 | Der Integer 15 = `[ 0x0f ]`
56 |
57 | Der Integer 1024 = `[ 0x82, 0x04, 0x00 ]`
58 |
59 | Die [mengentheoretischen Darstellung] (http://en.wikipedia.org/wiki/Set-theoretic_definition_of_natural_numbers) von zwei, `[ [], [[]], [ [], [[]] ] ] = [ 0xc7, 0xc0, 0xc1, 0xc0, 0xc3, 0xc0, 0xc1, 0xc0 ]`
60 |
61 | Der String "Lorem ipsum dolor sit amet, consectetur adipisicing elit" = `[ 0xb8, 0x38, 'L', 'o', 'r', 'e', 'm', ' ', ... , 'e', 'l', 'i', 't' ]`
62 |
--------------------------------------------------------------------------------
/en/1984 not a manual.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/1984 not a manual.jpg
--------------------------------------------------------------------------------
/en/511fabd217df7170.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/511fabd217df7170.png
--------------------------------------------------------------------------------
/en/68747470733a2f2f7777772e7a656e6875622e696f2f626c6f672f636f6e74656e742f696d616765732f323031342f4f63742f4f7267616e697a65642d426f6172642e6a7067.jpeg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/68747470733a2f2f7777772e7a656e6875622e696f2f626c6f672f636f6e74656e742f696d616765732f323031342f4f63742f4f7267616e697a65642d426f6172642e6a7067.jpeg
--------------------------------------------------------------------------------
/en/75a077d5b29328e7.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/75a077d5b29328e7.png
--------------------------------------------------------------------------------
/en/7aa064deb75b8a8a.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/7aa064deb75b8a8a.png
--------------------------------------------------------------------------------
/en/8cae536fb9ea9dae.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/8cae536fb9ea9dae.png
--------------------------------------------------------------------------------
/en/README.md:
--------------------------------------------------------------------------------
1 | ###**This guide is still under heavy development.*
2 |
3 | Into the ether
4 | =======
5 |
6 | ###Continuing the experiment ...
7 |
8 | When the grand experiment that is Bitcoin began, the anonymous wizard desired to test two parameters:
9 |
10 | 1. **a trustless, decentralized database enjoying security enforced by the austere relentlessness of cryptography**
11 |
12 | 2. **a robust transaction system capable of sending value across the world without intermediaries.**
13 |
14 | Yet the past five years years have painfully demonstrated a **_third_ missing feature: a sufficiently powerful Turing-complete scripting language**. Up until this point, most innovation in advanced applications such as domain and identity registration, user-issued currencies, smart property, smart contracts, and decentralized exchange has been highly fragmented, and implementing any of these technologies has required creating an entire meta-protocol layer or even a specialized blockchain. Theoretically, however, each and every one of these innovations and more can potentially be made hundreds of times easier to implement, and easier to scale, if only there was a stronger foundational layer with a powerful scripting language for all of these protocols to build upon. And this need is what we seek to satisfy.
15 |
16 | Ethereum is a modular, stateful, Turing-complete contract scripting system married to a blockchain and developed with a philosophy of simplicity, universal accessibility and generalization. Our goal is to provide a platform for decentralized applications - an android of the cryptocurrency world, where all efforts can share a common set of APIs, trustless interactions and no compromises.
17 |
18 | ###... together
19 |
20 | During the past year there have been a number of developers and researchers who have either worked for Ethereum or working on ideas as volunteers and happen to spend lots of time interacting with the Ethereum community, and this set of people has coalesced into a group dedicated to building out the vision set by Vitalik Buterin in the Ethereum Whitepaper.
21 |
22 | We ask for the community to join us as volunteers, developers, investors and evangelists seeking to enable a fundamentally different paradigm for the Internet and the relationships it provides.
23 |
24 |
--------------------------------------------------------------------------------
/en/SUMMARY.md:
--------------------------------------------------------------------------------
1 | # Summary
2 |
3 | * [Introduction](README.md)
4 | * [Thank you.](thank_you.md)
5 | * [This is a knowledge remix](this_is_a_knowledge_remix.md)
6 | * [Special Thanks](special_thanks.md)
7 | * [Open Collaboration Welcomed](open_collaboration_welcomed.md)
8 | * [The Why, How and What](They why, How and What.md)
9 | * [Ethereum design philosophy](design_philosophy.md)
10 | * [Design rationale](design_rationale.md)
11 | * [What can you do with it?](what_is_ethereum.md)
12 | * [Installing Ethereum Client](installing_ethereum.md)
13 | * [Building on Ubuntu](building_on_ubuntu.md)
14 | * [C++](ubuntu_cpp_build.md)
15 | * [Go](ubuntu_go_build.md)
16 | * [Building on Mac OS](building_on_mac_os.md)
17 | * [C++](mac_cpp_build.md)
18 | * [Go](mac_go_build.md)
19 | * [Building on Windows](building_on_windows.md)
20 | * [C++](win_cpp_build.md)
21 | * [Go](win_go_build.md)
22 | * [Ethereum APIs](ethereum_apis.md)
23 | * [JSON RPC API](ethereum_json_rpc.md)
24 | * [Javascript API](ethereum_javascript_api.md)
25 | * [Smart Contracts](smart_contract_tutorials.md)
26 | * [Solidity Features](solidity_features.md)
27 | * [Serpent Features](serpent_features.md)
28 | * [Serpent Tutorials](serpent_tutorials.md)
29 | * [Solidity Tutorials](solidity_tutorials.md)
30 | * Resources
31 | * [Whitepaper](whitepaper.md)
32 | * [Glossary](glossary.md)
33 | * [Ξaster Egg](vitalik-diagrams/readme.md)
34 |
35 |
--------------------------------------------------------------------------------
/en/Start with why.md:
--------------------------------------------------------------------------------
1 | # Start with why
2 |
3 |
--------------------------------------------------------------------------------
/en/They why, How and What.md:
--------------------------------------------------------------------------------
1 | # The Why, How and What
2 |
3 |
--------------------------------------------------------------------------------
/en/a57b769af1448548.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/a57b769af1448548.png
--------------------------------------------------------------------------------
/en/build_macos.md:
--------------------------------------------------------------------------------
1 | # Building on MacOS
2 |
3 | # Installing cpp-ethereum on OS X
4 |
5 | ### Using Homebrew
6 |
7 | First tap the ethereum brew:
8 | ```
9 | brew tap ethereum/ethereum
10 | ```
11 |
12 | For the latest stable version:
13 | ```
14 | brew install ethereum
15 | brew linkapps
16 | ```
17 |
18 | For the latest cutting edge developer version:
19 | ```
20 | brew reinstall ethereum --devel
21 | brew linkapps
22 | ```
23 |
24 | Then open `AlethZero.app` from your Applications folder. You can also run `eth` (CLI) or `neth` (ncurses interface).
25 |
26 | For options and patches, see: https://github.com/ethereum/homebrew-ethereum
27 |
28 | ### Downloading .app package directly
29 |
30 | If you're just interested in the GUI client AlethZero without the command line interfaces, download the latest [stable](http://build.ethdev.com/builds/OSX%20C%2B%2B%20master%20branch/AlethZero-OSX-latest.tar.bz2) or [cutting edge](http://build.ethdev.com/builds/OSX%20C%2B%2B%20develop%20branch/AlethZero-OSX-latest.tar.bz2) version.
--------------------------------------------------------------------------------
/en/build_ubuntu.md:
--------------------------------------------------------------------------------
1 | {% include "git+https://github.com/ethereum/cpp-ethereum.wiki.git/Building-on-Ubuntu.md" %}
--------------------------------------------------------------------------------
/en/build_windows.md:
--------------------------------------------------------------------------------
1 | # Building on Windows
2 |
3 | # Installing cpp-ethereum on Windows
4 |
5 | This will work on Windows 8.1. Other versions of Windows should work, but haven't been tested.
6 |
7 | Get the [Visual C++ Redistributable Package for Visual Studio 2013](http://www.microsoft.com/en-US/download/details.aspx?id=40784). Download the 32 bit version (vcredist_x86.exe) even when you have a 64 bit Version of Windows.
8 |
9 | Then, download the latest [stable](http://build.ethdev.com/builds/Windows%20C%2B%2B%20master%20branch/AlethZero-Win32-latest.7z) or [cutting edge](http://build.ethdev.com/builds/Windows%20C%2B%2B%20develop%20branch/AlethZero-Win32-latest.7z) binary version.
10 |
11 |
--------------------------------------------------------------------------------
/en/building_on_mac_os.md:
--------------------------------------------------------------------------------
1 | # Building on Mac OS
2 |
3 |
--------------------------------------------------------------------------------
/en/building_on_ubuntu.md:
--------------------------------------------------------------------------------
1 | # Building on Ubuntu
2 |
3 |
--------------------------------------------------------------------------------
/en/building_on_windows.md:
--------------------------------------------------------------------------------
1 | # Building on Windows
2 |
3 |
--------------------------------------------------------------------------------
/en/c64df7f3e1e2680b.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/c64df7f3e1e2680b.png
--------------------------------------------------------------------------------
/en/design_philosophy.md:
--------------------------------------------------------------------------------
1 | # Design philosophy
2 |
3 | These are the core tenets that sparked the work on Ethereum's architeture and imlementation.
4 |
5 | ## Simplicity
6 | The Ethereum protocol should be as simple as possible, even at the cost of some data storage inefficiency or time inefficiency. An average programmer should ideally be able to follow and implement the entire specification, so as to eventually help minimize the influence that any specific individual or elite group can have on the protocol and furthering the vision of Ethereum as a protocol that is open to all. Optimizations which add complexity should not be included unless they provide very substantial benefit.
7 |
8 | ## Universality
9 | It is a fundamental part of Ethereum’s design philosophy that Ethereum does not have “features”. Instead, Ethereum provides an internal Turing-complete scripting language which you can use to construct any smart contract or transaction type that can be mathematically defined. Want to invent your own financial derivative? With Ethereum, you can. Want to make your own currency? Set it up as an Ethereum contract. Want to set up a full-scale Daemon or Skynet? You may need to have a few thousand interlocking contracts, and be sure to feed them generously, to do that, but nothing is stopping you.
10 |
11 | ## Modularity
12 | Different parts of the Ethereum protocol should be designed to be as modular and separable as possible. Over the course of development, it should be easy to make a small protocol modification in one place and have the application stack continue to function without any further modification. Innovations such as Dagger, Patricia trees and RLP should be implemented as separate libraries and made to be feature-complete even if Ethereum does not require certain features so as to make them usable in other protocols as well. Ethereum development should be maximally done so as to benefit the entire cryptocurrency ecosystem, not just itself.
13 |
14 | ## Non-Discrimination
15 | The protocol should not attempt to actively restrict or prevent specific categories of usage, and all regulatory mechanisms in the protocol should be designed to directly regulate the harm, not attempt to oppose specific undesirable applications. You can even run an infinite loop script on top of Ethereum for as long as you are willing to keep paying the per-computational-step transaction fee for it.
16 |
17 | ## Agility
18 | Details of the Ethereum protocol are not set in stone. Although we will be extremely judicious about making modifications to high-level constructs such as the C-like language and the address system, computational tests later on in the development process may lead us to discover that certain modifications to the algorithm or scripting language will substantially improve scalability or security. If any such opportunities are found, we will make use of them.
--------------------------------------------------------------------------------
/en/design_rationale.md:
--------------------------------------------------------------------------------
1 | {% include "git+https://github.com/ethereum/wiki.wiki.git/Design-Rationale.md" %}
--------------------------------------------------------------------------------
/en/etherean_languages.md:
--------------------------------------------------------------------------------
1 | # Etherean Languages
2 |
3 |
--------------------------------------------------------------------------------
/en/ethereum_apis.md:
--------------------------------------------------------------------------------
1 | # The Ethereum APIs
2 |
3 |
--------------------------------------------------------------------------------
/en/ethereum_javascript_api.md:
--------------------------------------------------------------------------------
1 | # The Ethereum Javascript API
2 |
3 | {% include "git+https://github.com/ethereum/wiki.wiki.git/JavaScript-API.md" %}
--------------------------------------------------------------------------------
/en/ethereum_json_rpc.md:
--------------------------------------------------------------------------------
1 | # Ethereum JSON RPC
2 |
3 | {% include "git+https://github.com/ethereum/wiki.wiki.git/JSON-RPC.md" %}
--------------------------------------------------------------------------------
/en/ethereum_mining_algo.md:
--------------------------------------------------------------------------------
1 | # Ethereum Mining Algo
2 |
3 | {% include "git+https://raw.githubusercontent.com/wiki/ethereum/wiki/Ethash-Design-Rationale.md" %}
--------------------------------------------------------------------------------
/en/ethereumbuilders.md:
--------------------------------------------------------------------------------
1 | # Ethereum.Builders
2 |
3 | ###Start with why
4 |
5 | The _Internet_ is more than a company, organization or application. It offers a way for people to communicate, collaborate and trade resources and knowledge real-time at a planetary scale. In the past 20+ years the Internet has become indispensable and we rely heavily on it for many things - from talking to our loved ones to running world-wide economies. Considering how important the Internet is to us and humanity as a whole, it only make sense to have its foundations open, transparent and trustworthy.
6 |
7 | For the past few years centralized services such as Google and Facebook have steadily become **the internet** for many people. [The influence they have][1] on the choices and behavior of the totality of individual human beings translates to real power to influence the course of history and we should strive for a better solution that the ones available now, for this reason alone if nothing else.
8 |
9 | You might think we learned something the last 6000+ years of recorded history - or rather what's left of it. Numerous times we have seen burned books and libraries, attempts to edit the history of events for political or personal gain and the toxic nature of monopolies and centralization in general. Too much centralized power has never ended up well.
10 |
11 | Currently the Internet is written on water because it runs on top of data storage mediums designed to be edited and changed. It’s not the right technology for _everything_ and it introduces a number of wrong trust dimensions. In some cases such we **need** an immutable history. Things that are written, and just don’t change.
12 |
13 | Add on top of that the fact that your personal data (searches, posts, pictures, messages, etc) belong to **anyone but you** and you get a pretty grim picture of the digital reality we live in. Things have never been so centralized and at this scale in the history of our civilization. This is where we are now and things could certainly use some improvement.
14 |
15 | Ethereum is a 100% crowd founded, open source technology created out of necessity for a trustworthy foundation on which we can rebuild and heal the Internet. It is envisioned as a platform that enables people to easily build decentralized applications, **transparent and trustworthy by design**. From email services that **[don't read your emails][2]** to **unforgeable voting systems**, an entire multi-verse of possibilities and applications is waiting to be explored by the brave and open-minded.
16 |
17 | Ethereum builders is a self organizing community that thrives on communication, mass collaboration and solution-oriented thinking. Use your creative freedom, **identify what inspires you, own it, and push it.** Take risks, learn from your mistakes, and most of all, have fun. You are not only welcome to experiment here but encouraged, so throw your craziest of ideas on the boards and have fun!
18 |
19 | From here on, together, we can do more
20 |
21 | If we can build a better system, then more than 2 billion people will have a way to regain control over their information, privacy and digital lives. This is an important goal, worthy of time, attention and commitment. We deserve a neutral, open and trustworthy Internet with privacy as a standard, not a feature. Period.
22 |
23 | This is the dawn of the crypto renaissance
24 |
25 |
26 | #Our values
27 |
28 | Our values converge in a culture that revolves around exploration, creativity, problem solving, and a willingness to push fast and iterate. We work hard as a team, have fun as a team, and we never take ourselves too seriously.
29 |
30 | ###1. Transparency
31 | Transparency is the foundation for building trust in an open network. Transparent community-based processes promote participation, accountability and trust.
32 |
33 | ###2. Meritocracy
34 | In a meritocracy, the best ideas win. Each person’s value comes from his or her individuality and uniqueness and the capacity to engage and interact with others to make the fruits of that uniqueness available. Successful work determines which projects rise and gather effort from the community.
35 |
36 | ###3. Open Information
37 | A free exchange of ideas is critical to creating an environment where people are allowed to learn and use existing information toward creating new ideas. Spawned from this core idea, free and open source software promotes the development of the Internet as an open and trustworthy public resource.
38 |
39 | ###4. Open collaboration
40 | When we are free to collaborate we can solve problems that no one person may be able to solve on their own and learn from each other in the process.
41 |
42 | ###5. Rapid Prototyping
43 | Learn by doing. Rapid prototypes can lead to rapid failures, but that leads to better solutions found faster. When you're free to experiment, you can look at problems in new ways and look for answers in new places.
44 |
45 | ###6. Pluralism & Diversity
46 | No one has done this before. This means that there is no "right" or "wrong" way of doing things and by definition it's a trial and error process. From each failed experiment we learn and improve for the next experiment.
47 |
48 | ###7. Practical idealism
49 | Technologies and solutions that can be generalized as _world positive_ are worthy to be pursued and explored. When others ask _why bother?_ we ask _why not?_
--------------------------------------------------------------------------------
/en/get_involved.md:
--------------------------------------------------------------------------------
1 | # Get Involved
2 |
3 | So you're interested in getting involved? You are :sparkles: awesome :sparkles: !
4 |
5 | If you want to dive straight in then jump on the GitHub repos and decide from there what you want to work on.
6 |
7 | If you want to devote a few hours per day doing it then please get in touch with us at hello@ethereum.builders.
8 |
9 | .... what else?
--------------------------------------------------------------------------------
/en/go_build.md:
--------------------------------------------------------------------------------
1 | {% include "git+https://github.com/ethereum/go-ethereum.wiki.git/Instructions-for-getting-the-Go-implementation-of-Ethereum-and-the-Mist-browser-installed-on-Ubuntu-14.04-(trusty).md" %}
--------------------------------------------------------------------------------
/en/how_it_works.md:
--------------------------------------------------------------------------------
1 | {% include "git+https://github.com/ethereum/wiki.wiki.git/White-Paper.md" %}
--------------------------------------------------------------------------------
/en/installing_ethereum.md:
--------------------------------------------------------------------------------
1 | # Installing Ethereum
2 |
3 |
--------------------------------------------------------------------------------
/en/mac_build_cpp.md:
--------------------------------------------------------------------------------
1 | https://github.com/ethereum/cpp-ethereum/wiki/Building-on-MacOS
--------------------------------------------------------------------------------
/en/mac_cpp_build.md:
--------------------------------------------------------------------------------
1 | {% include "git+https://github.com/ethereum/cpp-ethereum.wiki.git/Building-on-MacOS.md" %}
--------------------------------------------------------------------------------
/en/mac_go_build.md:
--------------------------------------------------------------------------------
1 | {% include "git+https://github.com/ethereum/go-ethereum.wiki.git/Building-Instructions-for-Mac.md" %}
--------------------------------------------------------------------------------
/en/manualbuild.md:
--------------------------------------------------------------------------------
1 | # Manual Build
2 |
3 | Ethereum has binaries for common platforms:
4 | * **[Mac OS X, stable](http://build.ethdev.com/builds/OSX%20C%2B%2B%20master%20branch/AlethZero-OSX-latest.tar.bz2)** and **[Mac OS X, cutting-edge](http://build.ethdev.com/builds/OSX%20C%2B%2B%20develop%20branch/AlethZero-OSX-latest.tar.bz2)**. You may also choose to [use Homebrew](Installing Clients#installing-cpp-ethereum-on-os-x) (a longer process but you can edit the source code).
5 | * **[Windows 32-bit, stable](http://build.ethdev.com/builds/Windows%20C%2B%2B%20master%20branch/AlethZero-Win32-latest.7z)** and **[Windows 32-bit, cutting-edge](http://build.ethdev.com/builds/Windows%20C%2B%2B%20develop%20branch/AlethZero-Win32-latest.7z)**; you'll also need to install the [MSVC Redistributable](http://www.microsoft.com/en-US/download/details.aspx?id=40784) prior. *TODO: Bundle this or static link*
6 | * **Ubuntu**
7 |
8 |
9 |
10 | If you like the idea of developing on Ethereum, the best development platform currently is Ubuntu 14.04 with the QtCreator IDE. If you would like to know more about building Ethereum for your platform you'll want to inspect:
11 |
12 | * Building on Ubuntu
13 | * Building on MacOS
14 | * Building on Windows
15 |
16 | Please also see the community edited page on [[Compatibility Info and Build Tips]] for other distributions and operating systems. If you have anything else to add (e.g. instructions for your favourite distribution), please add to the page and make it a useful resource!
--------------------------------------------------------------------------------
/en/open_collaboration_system.md:
--------------------------------------------------------------------------------
1 | # Open collaboration system
2 |
3 | ###Ideate. Co-Create. Iterate.
4 | > Whatever you do, or dream you can, begin it. Boldness has genius and power and magic in it.
5 |
6 | In this guide it will be assumed that you already have a GitHub account and [Chrome on your machine][1]. If you don't have a GitHub account yet you can easily [get one here][2].
7 |
8 | 
9 |
10 | **In this guide you'll learn how to setup the following:**
11 |
12 | 1. [GitHub Collaboration Extension][3]
13 | 2. [Open Source Economics Engine][4]
14 | 3. *Optional [Project Focused IM][5]
15 |
16 | ------
17 | ###Step one. Supercharge GitHub workflows
18 |
19 | Transform your usual GitHub account into a powerful project management tool in just two steps:
20 |
21 | **1.** Go to https://www.zenhub.io/ or directly install the Chrome extension from [the webstore](https://chrome.google.com/webstore/detail/zenhub-for-github/ogcgkffhplmphkaahpmffcafajaocjbd)
22 |
23 | **2.** Connect your GitHub account with Zenhub.
24 |
25 | * You can check if everything went okay by checking [your Github application settings](https://github.com/settings/applications). You should see ZenHub as one of the authorized applications.
26 |
27 | 
28 |
29 |
30 | If ZenHub has been correctly installed, then a new tab called **"board(s)"** should appear on your GitHub repo pages. The **board(s)** are populated by the issues created, each new issue becoming a card on the new ZenHub board tab.
31 |
32 | This is how a populated board should look like:
33 |
34 | 
35 |
36 | Please read these articles if you want to understand more about how ZenHub works:
37 |
38 | * [Getting started with ZenHub](https://www.zenhub.io/blog/getting-started-with-zenhub/)
39 | * [Supercharge GitHub Workflows](https://www.zenhub.io/blog/supercharge-github-workflows-introducing-zenhub-part-i/)
40 |
41 |
42 | TIP: **The _B_ key serves as a keyboard shortcut to display the boards in repos, while _F_ is used for quick repo switching.**
43 |
44 | *Please note that you __need__ to install the zenhub extension in order to view and use GitHub as described in this guide.*
45 |
46 | --------
47 | ###Step two. Accelerate open source with Bountysource
48 |
49 | One of the biggest problems surrounding open source, community based projects is resource starvation. In our case we'll Bountysource to get around the resource starvation issue and allow the community to guide itself and become self sustainable in the process.
50 |
51 | 1. Go to [Bountysource][6] and sign in with your GitHub account.
52 |
53 | 2. Create, contribute or solve the current issues listed in the [ethereum builders GitHub repos][7]
54 | 
55 |
56 | This is the screen you'll see when opening an issue on bountysource.
57 | 
58 |
59 |
60 |
61 | Things will get more interesting once we'll have the possibility of creating DAOs but in the meantime this is a pretty cool solution as well. You're fully setup now to contribute to all the existent issues and also create new bounties.
62 | 
63 |
64 | -------
65 |
66 | ### *Step three. Enhance GitHub interactivity with Gitter.
67 |
68 | Besides GitHub we also use an application called Gitter. Very straightforward setup process, incredibly well suited app for distributed communities and projects like this one. With this tool you're able to transform your favorite repos into your favorite chatrooms ^_^
69 | 
70 |
71 | Get started by [signing up for the free account][8] and allow it the access it needs in order to function properly.
72 |
73 | For those of you that don't like the permissions requested please read this:
74 |
75 | * [Why do you ask for write access to my profile?](https://gitter.zendesk.com/hc/en-us/articles/200178961-Why-do-you-ask-for-write-access-to-my-profile-)
76 | * [You want write access on my private repos? Are you insane?](https://gitter.zendesk.com/hc/en-us/articles/200178971-You-want-write-access-on-my-private-repos-Are-you-insane-)
77 |
78 | #Highfive! You're all set!
79 |
80 |
81 |
82 |
83 | [1]: https://github.com/ethereumbuilders
84 | [2]: https://github.com/join
85 | [3]: https://chrome.google.com/webstore/detail/zenhub-for-github/ogcgkffhplmphkaahpmffcafajaocjbd
86 | [4]: https://www.bountysource.com/
87 | [5]: https://gitter.im/
88 | [6]: https://www.bountysource.com/signin
89 | [7]: https://github.com/ethereumbuilders
90 | [8]: https://gitter.im/login/github?action=signup&source=intro-signup
91 |
--------------------------------------------------------------------------------
/en/open_collaboration_welcomed.md:
--------------------------------------------------------------------------------
1 | # Open Collaboration Welcomed
2 |
3 | This book lives on GitHub. You can find everything listed in this book [also in this repository](https://github.com/ethereumbuilders/GitBook).
4 |
5 | If you want to jump straight in and contribute directy from GitHub, feel free to do so and enjoy the warm fuzzy feeling for being part of something truly world-changing.
6 |
7 | If you want to be part of the GitBook contributors team please get in touch with us at hello@ethereum.builders and we'll get back to you as soon as humanly possible.
8 |
9 | If you want to join our friendly GitBook Gitter chatroom to say hello, contribute or give feedback click the button bellow.
10 |
11 | See you there!
12 |
13 | [](https://gitter.im/ethereumbuilders/GitBook?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
--------------------------------------------------------------------------------
/en/python_build.md:
--------------------------------------------------------------------------------
1 | # Python
2 |
3 | ### Installation:
4 |
5 | - Python2.7 is required
6 |
7 |
8 |
9 |
10 | ``git clone https://github.com/ethereum/pyethereum/``
11 |
12 | ``python setup.py install``
13 |
14 |
15 |
16 | Running the client:
17 |
18 |
19 | ``pyeth`` at the commandline will start the ethereum node and connect to the p2p network.
20 |
21 | Note: At the first invocation a default configuration will be written to ~/.pyethereum (location depending on your platform).
22 | You can edit this file to suite your needs.
23 |
24 |
25 | Interacting with the network:
26 |
27 | ``pyethclient`` is the command line client to inspect and manipulate the ethereum blockchain.
28 |
29 |
--------------------------------------------------------------------------------
/en/serpent.md:
--------------------------------------------------------------------------------
1 | Serpent is one of the high-level programming languages used to write Ethereum contracts. The language, as suggested by its name, is designed to be very similar to Python; it is intended to be maximally clean and simple, combining many of the efficiency benefits of a low-level language with ease-of-use in programming style, and at the same time adding special domain-specific features for contract programming. The latest version of the Serpent compiler, available [on github](http://github.com/ethereum/serpent), is written in C++, allowing it to be easily included in any client.
2 |
3 | This tutorial assumes basic knowledge of how Ethereum works, including the concept of blocks, transactions, contracts and messages and the fact that contracts take a byte array as input and provide a byte array as output. If you do not, then go [here](https://github.com/ethereum/wiki/wiki/Ethereum-Development-Tutorial) for a basic tutorial.
4 |
5 | ### Differences Between Serpent and Python
6 |
7 | The important differences between Serpent and Python are:
8 |
9 | * Python numbers have potentially unlimited size, Serpent numbers wrap around 2256. For example, in Serpent the expression `3^(2^254)` suprisingly evaluates to 1, even though in reality the actual integer is too large to be recorded in its entirety within the universe.
10 | * Serpent has no decimals.
11 | * Serpent has no concept of strings (at this point)
12 | * Serpent has no list comprehensions (expressions like `[x**2 for x in my_list]`), dictionaries or most other advanced features
13 | * Serpent has no concept of first-class functions. Contracts do have functions, and can call their own functions, but variables (except storage) do not persist across calls.
14 | * Serpent has a concept of persistent storage variables (see below)
15 | * Serpent has an `extern` statement used to call functions from other contracts (see below)
16 |
17 | ### Installation
18 |
19 | In order to install the Serpent python library and executable do:
20 |
21 | sudo pip install ethereum-serpent
22 |
23 | If you want a library you can directly call from C++, instead do:
24 |
25 | git clone http://github.com/ethereum/serpent
26 | cd serpent
27 | make
28 | sudo make install
29 |
30 |
--------------------------------------------------------------------------------
/en/serpent_features.md:
--------------------------------------------------------------------------------
1 | # Serpent Features
2 |
3 | Serpent is one of the high-level programming languages used to write Ethereum contracts. The language, as suggested by its name, is designed to be very similar to Python; it is intended to be maximally clean and simple, combining many of the efficiency benefits of a low-level language with ease-of-use in programming style, and at the same time adding special domain-specific features for contract programming. The latest version of the Serpent compiler, available [on github](http://github.com/ethereum/serpent), is written in C++, allowing it to be easily included in any client.
4 |
5 | This tutorial assumes basic knowledge of how Ethereum works, including the concept of blocks, transactions, contracts and messages and the fact that contracts take a byte array as input and provide a byte array as output. If you do not, then go [here](https://github.com/ethereum/wiki/wiki/Ethereum-Development-Tutorial) for a basic tutorial.
6 |
7 | ### Differences Between Serpent and Python
8 |
9 | The important differences between Serpent and Python are:
10 |
11 | * Python numbers have potentially unlimited size, Serpent numbers wrap around 2256. For example, in Serpent the expression `3^(2^254)` suprisingly evaluates to 1, even though in reality the actual integer is too large to be recorded in its entirety within the universe.
12 | * Serpent has no decimals.
13 | * Serpent has no list comprehensions (expressions like `[x**2 for x in my_list]`), dictionaries or most other advanced features
14 | * Serpent has no concept of first-class functions. Contracts do have functions, and can call their own functions, but variables (except storage) do not persist across calls.
15 | * Serpent has a concept of persistent storage variables
16 | * Serpent has an `extern` statement used to call functions from other contracts
--------------------------------------------------------------------------------
/en/single_smart_contracts.md:
--------------------------------------------------------------------------------
1 | # Single smart contracts
2 |
3 |
--------------------------------------------------------------------------------
/en/smart_contract_tutorials.md:
--------------------------------------------------------------------------------
1 | # Smart Contracts
2 |
3 |
--------------------------------------------------------------------------------
/en/smart_contracts_intro.md:
--------------------------------------------------------------------------------
1 | # Smart contracts intro
2 |
3 | Smart contracts are cryptographic "boxes" that contain value and only unlock it if certain conditions are met, can also be built on top of the platform, with vastly more power than that offered by Bitcoin scripting because of the added powers of Turing-completeness, value-awareness, blockchain-awareness and state.
4 |
5 | Financial derivatives are the most common application of a "smart contract", and one of the simplest to implement in code. The main challenge in implementing financial contracts is that the majority of them require reference to an external price ticker; for example, a very desirable application is a smart contract that hedges against the volatility of ether (or another cryptocurrency) with respect to the US dollar, but doing this requires the contract to know what the value of ETH/USD is.
6 |
7 | The simplest way to do this is through a "data feed" contract maintained by a specific party (eg. NASDAQ) designed so that that party has the ability to update the contract as needed, and providing an interface that allows other contracts to send a message to that contract and get back a response that provides the price.
8 |
9 | Given that critical ingredient, the hedging contract would look as follows:
10 |
11 | 1. Wait for party A to input 1000 ether.
12 | 2. Wait for party B to input 1000 ether.
13 | 3. Record the USD value of 1000 ether, calculated by querying the data feed contract, in storage, say this is $x.
14 | 4. After 30 days, allow A or B to "reactivate" the contract in order to send $x worth of ether (calculated by querying the data feed contract again to get the new price) to A and the rest to B.
15 |
16 | Such a contract would have significant potential in crypto-commerce. One of the main problems cited about cryptocurrency is the fact that it's volatile; although many users and merchants may want the security and convenience of dealing with cryptographic assets, they many not wish to face that prospect of losing 23% of the value of their funds in a single day. Up until now, the most commonly proposed solution has been issuer-backed assets; the idea is that an issuer creates a sub-currency in which they have the right to issue and revoke units, and provide one unit of the currency to anyone who provides them (offline) with one unit of a specified underlying asset (eg. gold, USD). The issuer then promises to provide one unit of the underlying asset to anyone who sends back one unit of the crypto-asset. This mechanism allows any non-cryptographic asset to be "uplifted" into a cryptographic asset, provided that the issuer can be trusted.
17 |
18 | In practice, however, issuers are not always trustworthy, and in some cases the banking infrastructure is too weak, or too hostile, for such services to exist. Financial derivatives provide an alternative. Here, instead of a single issuer providing the funds to back up an asset, a decentralized market of speculators, betting that the price of a cryptographic reference asset (eg. ETH) will go up, plays that role. Unike issuers, speculators have no option to default on their side of the bargain because the hedging contract holds their funds in escrow. Note that this approach is not fully decentralized, because a trusted source is still needed to provide the price ticker, although arguably even still this is a massive improvement in terms of reducing infrastructure requirements (unlike being an issuer, issuing a price feed requires no licenses and can likely be categorized as free speech) and reducing the potential for fraud.
19 |
--------------------------------------------------------------------------------
/en/smart_contracts_systems.md:
--------------------------------------------------------------------------------
1 | # Smart contracts systems
2 |
3 |
--------------------------------------------------------------------------------
/en/solidity_features.md:
--------------------------------------------------------------------------------
1 | # Solidity Features
2 |
3 | {% include "git+https://github.com/ethereum/wiki.wiki.git/Solidity-Features.md" %}
--------------------------------------------------------------------------------
/en/solidity_tutorials.md:
--------------------------------------------------------------------------------
1 | #Solidity Tutorials
2 |
3 | {% include "git+https://github.com/ethereum/wiki.wiki.git/Solidity-Tutorial.md" %}
4 |
--------------------------------------------------------------------------------
/en/special_thanks.md:
--------------------------------------------------------------------------------
1 | # Special thanks
2 |
3 | Through their work, these people make this guide possible.
4 |
5 | ####Vitalik Buterin
6 |
7 | _Inventor of Ethereum_
8 |
9 | **Gavin Wood**
10 |
11 | _C++/IDE/Whisper/Swarm Lead_
12 |
13 | **Jeffrey Wilcke**
14 |
15 | _Go/Mist Project Lead_
16 |
17 |
18 | *(the list will get bigger soon)*
19 |
20 | ...
21 |
22 | ...
23 |
24 | ...
25 |
26 | In the end, we'd also like to thank **_you_** for being part of this and for your support in making this happen.
--------------------------------------------------------------------------------
/en/thank_you.md:
--------------------------------------------------------------------------------
1 | # Thank _you_.
2 |
3 | Our philosophy at Ethereum is that every developer no matter what their level of technical ability should be able to create amazing things on our open-source, blockchain based platform.
4 |
5 | With this in mind we started this guide to help developers, from seasoned full stack developer to a complete beginner to learn how to setup the Ethereum clients, build DAPPs and in the process learn the skills necessary to build decentralized applications on top of Ethereum.
6 |
7 |
--------------------------------------------------------------------------------
/en/this_is_a_knowledge_remix.md:
--------------------------------------------------------------------------------
1 | ## This is a knowledge remix
2 |
3 | Just as in the Bitcoin ecosystem, in the beginning, there was quite a bit of knowledge fragmentatation - one blog post here, a forum post tutorial there, a misleading article there and so on.
4 |
5 | This book represents a mashup of wiki pages, tutorials and other relevant information that so far has been scattered without an easy way to find and access it.
6 |
7 | ###The aim of this work
8 |
9 | This guide tries to create an **easy to access ethereum knowledge base** that can help people from all around the world to **start experimenting with blockchain technologies**.
10 |
11 | Hopefully through this work, we will get closer to a reality in which we all realize that as long as we experiment with blockchain related technologies, we enrich the decentralized ecosystem in our own unique ways - contributing to something bigger than any individual project or initiative.
12 |
13 |
--------------------------------------------------------------------------------
/en/tutorials/tutorials.md:
--------------------------------------------------------------------------------
1 | This is where Ken's tutorials will be placed.
2 |
--------------------------------------------------------------------------------
/en/ubuntu_cpp_build.md:
--------------------------------------------------------------------------------
1 | {% include "git+https://github.com/ethereum/cpp-ethereum.wiki.git/Building-on-Ubuntu.md" %}
2 |
--------------------------------------------------------------------------------
/en/ubuntu_go_build.md:
--------------------------------------------------------------------------------
1 | {% include "git+https://github.com/ethereum/go-ethereum.wiki.git/Building-Instructions-for-Ubuntu.md" %}
--------------------------------------------------------------------------------
/en/under_the_hood.md:
--------------------------------------------------------------------------------
1 | # Under the hood
2 |
3 |
--------------------------------------------------------------------------------
/en/vitalik-diagrams/SVG-files/colored_coins_utxo_tree.svg:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
171 |
--------------------------------------------------------------------------------
/en/vitalik-diagrams/SVG-files/currency.svg:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
84 |
--------------------------------------------------------------------------------
/en/vitalik-diagrams/SVG-files/failurerate.svg:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
117 |
--------------------------------------------------------------------------------
/en/vitalik-diagrams/SVG-files/grandequation2.svg:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
137 |
--------------------------------------------------------------------------------
/en/vitalik-diagrams/SVG-files/heap6.svg:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
176 |
--------------------------------------------------------------------------------
/en/vitalik-diagrams/SVG-files/namereg.svg:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
74 |
--------------------------------------------------------------------------------
/en/vitalik-diagrams/SVG-files/orgs1.svg:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
178 |
--------------------------------------------------------------------------------
/en/vitalik-diagrams/SVG-files/orgs3.svg:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
173 |
--------------------------------------------------------------------------------
/en/vitalik-diagrams/SVG-files/paretoscaling.svg:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
161 |
--------------------------------------------------------------------------------
/en/vitalik-diagrams/SVG-files/pos_split.svg:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
148 |
--------------------------------------------------------------------------------
/en/vitalik-diagrams/SVG-files/readme.md:
--------------------------------------------------------------------------------
1 | These are the editable SVG files for the diagrams linked in the parent folder. As a note, there might be problems if trying to open them from other applications than Inkscape.
2 |
--------------------------------------------------------------------------------
/en/vitalik-diagrams/SVG-files/serpentcode.svg:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
98 |
--------------------------------------------------------------------------------
/en/vitalik-diagrams/SVG-files/twopoints.svg:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
166 |
--------------------------------------------------------------------------------
/en/vitalik-diagrams/appecosystem.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/appecosystem.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/apply_block_diagram.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/apply_block_diagram.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/apply_tx_diagram.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/apply_tx_diagram.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/asichome1.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/asichome1.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/barmodel.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/barmodel.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/bitcoin_price_chart.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/bitcoin_price_chart.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/block.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/block.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/blockchain.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/blockchain.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/centralized_multichain.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/centralized_multichain.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/chain_forks.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/chain_forks.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/chain_selection.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/chain_selection.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/chain_selection2.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/chain_selection2.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/chain_selection3.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/chain_selection3.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/chain_selection4.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/chain_selection4.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/chain_selection5.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/chain_selection5.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/chaindiag.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/chaindiag.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/clientserver.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/clientserver.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/colored_coins_utxo_tree.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/colored_coins_utxo_tree.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/contract_execution_flowchart.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/contract_execution_flowchart.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/contract_relationship.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/contract_relationship.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/contract_relationship2.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/contract_relationship2.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/cpuhome.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/cpuhome.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/cube.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/cube.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/currency.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/currency.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/ecthingy.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/ecthingy.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/endo1.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/endo1.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/endo1.svg.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/endo1.svg.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/endo10.svg.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/endo10.svg.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/endo2.svg.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/endo2.svg.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/endo20.svg.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/endo20.svg.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/endo3.svg.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/endo3.svg.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/endo30.svg.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/endo30.svg.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/endo4.svg.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/endo4.svg.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/endo5.svg.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/endo5.svg.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/entropy.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/entropy.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/ess1.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/ess1.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/ess2.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/ess2.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/ether_sale_process.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/ether_sale_process.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/etherscriper.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/etherscriper.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/ethertransition.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/ethertransition.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/executionpath.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/executionpath.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/failurerate.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/failurerate.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/fault_tolerance_1.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/fault_tolerance_1.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/fault_tolerance_2.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/fault_tolerance_2.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/fourpoints.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/fourpoints.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/futarchy.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/futarchy.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/futarchy0.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/futarchy0.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/futarchy_bottom.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/futarchy_bottom.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/futarchy_top.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/futarchy_top.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/grandequation.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/grandequation.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/grandequation2.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/grandequation2.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/heap1.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/heap1.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/heap2.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/heap2.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/heap20.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/heap20.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/heap3.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/heap3.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/heap4.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/heap4.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/heap5.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/heap5.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/heap6.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/heap6.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/hubchain.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/hubchain.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/hubspoke.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/hubspoke.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/image2.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/image2.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/incentives.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/incentives.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/inflation.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/inflation.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/lightproof.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/lightproof.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/liquidity.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/liquidity.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/marginalsanctions.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/marginalsanctions.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/markov.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/markov.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/merkle.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/merkle.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/merkle_basic.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/merkle_basic.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/merkle_basic2.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/merkle_basic2.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/merklesum.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/merklesum.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/merklesum2.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/merklesum2.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/messenger.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/messenger.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/miner_receives_block_flowchart.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/miner_receives_block_flowchart.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/miner_receives_data_flowchart.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/miner_receives_data_flowchart.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/minernet1.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/minernet1.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/minernet2.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/minernet2.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/minernet3.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/minernet3.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/minernet4.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/minernet4.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/minernet5.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/minernet5.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/mining.jpg:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/mining.jpg
--------------------------------------------------------------------------------
/en/vitalik-diagrams/mining_process_flowchart.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/mining_process_flowchart.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/mofnsafety.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/mofnsafety.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/multikdf.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/multikdf.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/namereg.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/namereg.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/needforpreselection.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/needforpreselection.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/orgs1.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/orgs1.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/orgs2.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/orgs2.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/orgs3.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/orgs3.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/paretochart.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/paretochart.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/paretoscaling.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/paretoscaling.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/pools.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/pools.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/portfolio_replication.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/portfolio_replication.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/pos_checkpoints.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/pos_checkpoints.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/pos_header.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/pos_header.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/pos_selection2.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/pos_selection2.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/pos_split.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/pos_split.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/pow_header.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/pow_header.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/powsec.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/powsec.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/quadrant_chart.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/quadrant_chart.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/quadrant_chart2.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/quadrant_chart2.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/roadmap.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/roadmap.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/roadmap3.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/roadmap3.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/schellingcoin.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/schellingcoin.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/schellingcoin_collective_payoff.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/schellingcoin_collective_payoff.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/schellingcoin_payoff1.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/schellingcoin_payoff1.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/schellingcoin_payoff2.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/schellingcoin_payoff2.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/schellingvote.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/schellingvote.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/scoringrule.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/scoringrule.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/secdao_accounts.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/secdao_accounts.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/secretmulitply3.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/secretmulitply3.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/secretmultiply.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/secretmultiply.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/secretmultiply2.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/secretmultiply2.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/serpentcode.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/serpentcode.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/sha3repeat.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/sha3repeat.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/shadowchain.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/shadowchain.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/sidechains.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/sidechains.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/slasher1sec.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/slasher1sec.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/slasher2sec.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/slasher2sec.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/slasherghost.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/slasherghost.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/spv1.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/spv1.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/spv2.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/spv2.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/stacktrace.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/stacktrace.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/stake_low_influence.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/stake_low_influence.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/statetransition.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/statetransition.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/strip.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/strip.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/supplychart.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/supplychart.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/threepoints.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/threepoints.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/treap.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/treap.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/treap2.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/treap2.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/twolines.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/twolines.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/twolinesum.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/twolinesum.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/twolinesum2.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/twolinesum2.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/twopoints.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/twopoints.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/tworound.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/tworound.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/tx.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/tx.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/txbatch.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/txbatch.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/utilitychart.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/utilitychart.png
--------------------------------------------------------------------------------
/en/vitalik-diagrams/where_to_mine.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/ethereumbuilders/GitBook/ca79dc1b059c6b4326cefbe98f9466229faec9fa/en/vitalik-diagrams/where_to_mine.png
--------------------------------------------------------------------------------
/en/what_is_ethereum.md:
--------------------------------------------------------------------------------
1 | # What can you do with it
2 |
3 | {% include "git+https://github.com/ethereum/wiki.wiki.git/Ethereum-Development-Tutorial.md" %}
--------------------------------------------------------------------------------
/en/win_cpp_build.md:
--------------------------------------------------------------------------------
1 | {% include "git+https://github.com/ethereum/cpp-ethereum.wiki.git/Building-on-Windows.md" %}
--------------------------------------------------------------------------------
/en/win_go_build.md:
--------------------------------------------------------------------------------
1 | Need to create a wiki page with instructions for windows Go
--------------------------------------------------------------------------------
/es/README.md:
--------------------------------------------------------------------------------
1 | ###**Esta guía está todavía en desarrollo pesado.*
2 |
3 | Ethereum builders guía.
4 | =======
5 |
6 |
--------------------------------------------------------------------------------
/es/SUMMARY.md:
--------------------------------------------------------------------------------
1 | # Sumar
2 |
3 | * [Introducere](README.md)
4 | * [Thank you.](thank_you.md)
5 | * [This is a knowledge remix](this_is_a_knowledge_remix.md)
6 | * [Multumiri speciale](special_thanks.md)
7 | * [Open Collaboration Welcomed](open_collaboration_welcomed.md)
8 | * [The Why, How and What](They why, How and What.md)
9 | * [Ethereum design philosophy](design_philosophy.md)
10 | * [Design rationale](design_rationale.md)
11 | * [What can you do with it?](what_is_ethereum.md)
12 | * [Installing Ethereum Client](installing_ethereum.md)
13 | * [Build pe Ubuntu](building_on_ubuntu.md)
14 | * [C++](ubuntu_cpp_build.md)
15 | * [Go](ubuntu_go_build.md)
16 | * [Build pe Mac OS](building_on_mac_os.md)
17 | * [C++](mac_cpp_build.md)
18 | * [Go](mac_go_build.md)
19 | * [Build pe Windows](building_on_windows.md)
20 | * [C++](win_cpp_build.md)
21 | * [Go](win_go_build.md)
22 | * [API-uri Ethereum](ethereum_apis.md)
23 | * [JSON RPC API](ethereum_json_rpc.md)
24 | * [Javascript API](ethereum_javascript_api.md)
25 | * [Smart Contracts](smart_contract_tutorials.md)
26 | * [Solidity Features](solidity_features.md)
27 | * [Serpent Features](serpent_features.md)
28 | * [Serpent Tutorials](serpent_tutorials.md)
29 | * [Solidity Tutorials](solidity_tutorials.md)
30 | * Resurse
31 | * [Whitepaper](whitepaper.md)
32 | * [Glosar](glossary.md)
33 |
34 |
--------------------------------------------------------------------------------
/es/[Spanish]-Ethereum-TOC.md:
--------------------------------------------------------------------------------
1 | ### Bienvenidos a Ethereum, la plataforma para la siguiente generación de contratos inteligentes y aplicaciones descentralizadas.
2 |
3 | [Whitepaper de Ethereum](https://google.com)
4 |
5 | [RLP](https://google.com), Prefijo Linear Recursivo (Recursive Linear Prefix), usado para codificación de datos a través de Ethereum.
6 |
7 | [Patricia Tree](https://google.com) especificaciones del árbol Merkle Patricia (“Merkle Patria Tree”, también conocido como Trie), la estructura usada para almacenar y procesar a través de funciones Hash el estado de la cadena de bloques en Ethereum.
8 |
9 | [Protocolo de conexión](https://google.com), especificaciones.
10 |
11 | [CLL](https://google.com), Lenguage de alto nivel similar a C usado para crear contratos, especificaciones.
12 |
13 | [Dagger](https://google.com), Prueba de trabajo (Proof-of-work) de Ethereum.
14 |
15 | [Protocolo de Bloques 2.0](https://google.com)
16 |
17 | [Capas](https://google.com)
18 |
19 | [Cámara de compensación](https://google.com)
20 |
--------------------------------------------------------------------------------
/fr/README.md:
--------------------------------------------------------------------------------
1 | ###**Ce guide est encore en cours de développement.*
2 |
3 | Guide des constructeurs Ethereum
4 | =======
5 |
6 | Entre l'Ether
7 | =======
8 |
9 | ###L'expérience continue...
10 |
11 | Lorsque la grande expérience que représente Bitcoin a commence, son créateur/magicien anonyme souhaitait tester deux paramètres:
12 |
13 | 1. **Une base de donnes décentralisée, ne requérant aucune confiance, et qui se reposerait sur la sécurité procurée de manière si implacable par la cryptographie.**
14 |
15 | 2. **Un système de transaction capable d’envoyer de la valeur a l’autre bout du monde et sans intermédiaires.**
16 |
17 | Cependant ces cinq dernières années ont démontrées qu’une **troisième fonctionnalité est manquante: un langage de script puissant et Turing-complet**. Jusqu'à présent, la plupart des innovations au sein d’applications avancées telles que l’enregistrement de domaines et d'identités, de création de monnaies, de propriétés intelligente, de contrats intelligents et d'échanges décentralisés ont été extrêmement fragmentées, et les implémenter requiert la création d’une couche de protocole méta ou même d’une chaîne-de-blocs spécialisée. En théorie cependant, chacune des ces innovations, et plus, pourrait être rendue des centaines de fois plus simple a implémenter, et rendue élargissable beaucoup plus simplement, s’il y avait une simple fondation avec un langage de script que tous ces protocoles pourraient utiliser comme tremplin. Et c’est le problème que nous essayons de régler.
18 |
19 | Ethereum est un système de scripting de contrats qui est modulaire, stateful et Turing-complet, marié a une chaîne-de-bloc, et développé avec une philosophie de simplicité, accessibilité et généralisation universelle. Notre but est de fournir une plate-forme pour des applications décentralisées - un androïde du monde de la crypto-monnaie - où tous ces efforts peuvent utiliser un ensemble d’API commun, des interactions sans besoin de confiance et pas de compromis.
20 |
21 | ###… ensemble.
22 |
23 | Durant l'année passée, un certain nombre de développeurs et chercheurs ayant soit travaillé pour Ethereum ou sur des idées en tant que volontaires, et qui ont passé beaucoup de temps a interagir avec la communauté d’Ethereum, s’est regroupé en un ensemble dédié a la mise en place de la vision du papier séminal d’Ethereum écrit par Vitalik Buterin.
24 |
25 | Nous demandons donc a la communauté de se joindre a nous comme volontaires, développeurs, investisseurs et évangiles qui cherchent a permettre ce paradigme fondamentalement diffèrent pour l’Internet et les relations qu’il met a disposition.
26 |
--------------------------------------------------------------------------------
/fr/SUMMARY.md:
--------------------------------------------------------------------------------
1 | # Sumar
2 |
3 | * [Introducere](README.md)
4 | * [Thank you.](thank_you.md)
5 | * [This is a knowledge remix](this_is_a_knowledge_remix.md)
6 | * [Multumiri speciale](special_thanks.md)
7 | * [Open Collaboration Welcomed](open_collaboration_welcomed.md)
8 | * [The Why, How and What](They why, How and What.md)
9 | * [Ethereum design philosophy](design_philosophy.md)
10 | * [Design rationale](design_rationale.md)
11 | * [What can you do with it?](what_is_ethereum.md)
12 | * [Installing Ethereum Client](installing_ethereum.md)
13 | * [Build pe Ubuntu](building_on_ubuntu.md)
14 | * [C++](ubuntu_cpp_build.md)
15 | * [Go](ubuntu_go_build.md)
16 | * [Build pe Mac OS](building_on_mac_os.md)
17 | * [C++](mac_cpp_build.md)
18 | * [Go](mac_go_build.md)
19 | * [Build pe Windows](building_on_windows.md)
20 | * [C++](win_cpp_build.md)
21 | * [Go](win_go_build.md)
22 | * [API-uri Ethereum](ethereum_apis.md)
23 | * [JSON RPC API](ethereum_json_rpc.md)
24 | * [Javascript API](ethereum_javascript_api.md)
25 | * [Smart Contracts](smart_contract_tutorials.md)
26 | * [Solidity Features](solidity_features.md)
27 | * [Serpent Features](serpent_features.md)
28 | * [Serpent Tutorials](serpent_tutorials.md)
29 | * [Solidity Tutorials](solidity_tutorials.md)
30 | * Resurse
31 | * [Whitepaper](whitepaper.md)
32 | * [Glosar](glossary.md)
33 |
34 |
--------------------------------------------------------------------------------
/it/README.md:
--------------------------------------------------------------------------------
1 | ###**Questa guida è ancora in fase di sviluppo.*
2 |
3 | Guida di costruttori Ethereum. Qui potete trovare i documenti di Ethereum tradotti in Italiano
4 | =======
5 |
6 | ## L'esperimento continua ...
7 |
8 | Quando e' iniziato quel grande esperimento che prende il nome di *Bitcoin*, il mago anonimo che l'ha sviluppato ha voluto testare due parametri:
9 |
10 | * **un database decentralizzato basato sulla fiducia, in grado di godere della sicurezza imposta dalla inesorabile austerita' della crittografia;**
11 |
12 | * **un sistema di transazioni robusto in grado di inviare valore in tutto il mondo, senza intermediari.**
13 |
14 | Eppure gli ultimi cinque anni anni hanno dolorosamente mostrato che mancava una terza caratteristica: ***un linguaggio di scripting Turing-completo sufficientemente potente***. Fino ad ora, la maggior parte delle innovazioni come il dominio e l'identità di registrazione, le valute emesse direttamente dagli utenti, la smart property, gli smart contracts, e lo scambio decentralizzato sono state altamente frammentate, e la realizzazione di ciascuna di queste tecnologie ha richiesto la creazione di un intero meta-protocollo o addirittura di una blockchain specializzata. Teoricamente, però, ognuna di queste innovazioni e centinaia di altre possono potenzialmente essere rese infinitamente volte più facili da implementare, e più facili da accrescere, se solo ci fosse un livello fondamentale più forte con un potente linguaggio di scripting sul quale tutti questi protocolli possano basarsi. Noi stiamo cercando di soddisfare questo bisogno.
15 |
16 | Ethereum è un sistema di scripting dei contratti modulare, stateful, Turing-completo sposato con un blockchain e sviluppato secondo una filosofia di semplicità, accessibilità universale e generalizzazione. Il nostro obiettivo è quello di fornire una piattaforma per applicazioni decentralizzate - un androide del mondo delle criptovalute, dove tutti gli sforzi possano condividere un insieme comune di API, interazioni basate sulla fiducia e senza compromessi.
17 |
18 | ## ... Insieme
19 |
20 | Lungo il corso dello scorso anno un discreto numero di sviluppatori e ricercatori hanno lavorato per Ethereum oppure hanno lavorato su idee come volontari ed e' capitato loro di interagire spesso con la comunità Ethereum. Questo gruppo di persone si e' quindi fuso in un gruppo dedicato a realizzare la visione tracciata da Vitalik Buterin nel suo Libro Bianco.
21 |
22 | Chiediamo alla comunità di unirsi a noi come volontari, sviluppatori, investitori e portavoce per contribuire allo sviluppo di un paradigma fondamentalmente diverso per Internet e per le relazioni che questo rende possibili.
23 |
--------------------------------------------------------------------------------
/it/SUMMARY.md:
--------------------------------------------------------------------------------
1 | # Sommario
2 |
3 | * [Introduzione](README.md)
4 | * [Ringraziamenti]([Italian]-ringraziamenti.md)
5 | * [Ripasso conoscitivo]([Italian]-ripasso_conoscitivo.md)
6 | * [Ringraziamenti speciali]([Italian]-ringraziamenti_speciali.md)
7 | * [Collaborazioni benvenute]([Italian]benvenute_collaborazioni.md)
8 | * [Il Perche', il Come e il Quando ]([Italian]il_perche_il_come_il_quando.md)
9 | * [La filosofia di progettazione di Ethereum]([Italian]La_filosofia_di_progettazione_di_Ethereum.md)
10 | * [Design rationale]([Italian]Design_rationale.md)
11 | * [Cos e' Ethereum?]([Italian]-cosa-e-ethereum.md)
12 | * [Installare il Client di Ethereum]([Italian]-installare_ethereum.md)
13 | * [Su Ubuntu]([Italian] installazione su Ubuntu.md)
14 | * [C++]([Italian]-ubuntu_cpp_build.md)
15 | * [Go]([Italian]-ubuntu_go_build.md)
16 | * [Su Mac OS]([Italian] installazione su Mac.md)
17 | * [C++]([Italian]-mac_cpp_build.md)
18 | * [Go]([Italian]-mac_go_build.md)
19 | * [Su Windows]([Italian] installazione su Windows.md)
20 | * [C++]([Italian]-win_cpp_build.md)
21 | * [Go]([Italian]-win_go_build.md)
22 | * [API-uri Ethereum]([Italian] ethereum apis.md)
23 | * [JSON RPC API]([Italian]-ethereum_json_rpc.md)
24 | * [Javascript API]([Italian]-ethereum_javascript_api.md)
25 | * [I contratti intelligenti (smart contracts)]([Italian] Tutorials sui contratti intelligenti.md)
26 | * [Caratteristiche di Solidity]([Italian] caratteristiche di Solidity.md)
27 | * [Caratteristiche di Serpent]([Italian] caratteristiche di serpent.md)
28 | * [Tutorials su Serpent]([Italian]_Tutorials_su_Serpent.md)
29 | * [Tutorials su Solidity]([Italian]_Tutorials_su_Solidity.md)
30 | * Risorse
31 | * [Il Whitepaper]([Italian]-Libro-Bianco.md)
32 | * [Lo Yellowpaper]([Italian]-Libro-Giallo.md)
33 | * [Glossario]([Italian] glossario.md)
34 |
35 |
--------------------------------------------------------------------------------
/it/[Italian] Impostare il proprio ambiente di sviluppo Ethereum.md:
--------------------------------------------------------------------------------
1 | Lo sviluppo su Ethereum e’ stato concepito per essere estremamente facile da imparare per gli sviluppatori – e i linguaggi di programmazione sono abbastanza simili allo Javascript che chiunque conosca quel linguaggio dovrebbe acquisirne padronanza piuttosto velocemente.
2 |
3 | Ci sono tre programmi che ogni sviluppatore dovrebbe scaricare – Alethzero, Mist e Mix.
4 |
5 | * **Alethzero** e’ un client a interfaccia grafica con caratteristiche avanzate come chain private, force mining e una webkit suite completa.
6 |
7 | * **Mist** e’ il browser delle Dapp e il client per il mining nel quale gli utenti accederanno alle vostre Dapps.
8 |
9 | * Infine, **Mix** e’ un ambiente di sviluppo integrato – concepito appositamente per sviluppare e debuggare i contratti e i loro corrispettivi front-end.
10 |
11 | ## Requisiti software:
12 |
13 | Impostare un ambiente di sviluppo dovrebbe essere abbastanza semplice per chiunque ha mai progettato una pagina web prima d’ora – abbiamo tre programmi specifici che dovreste scaricare:
14 |
15 | In primo luogo, [scaricate](https://github.com/ethereum/cpp-ethereum/wiki) l’ultima versione stabile di Alethzero, il nostro client scritto in C++, e installatelo sul vostro sistema operativo. Se avete problemi con l’ultima versione stabile di sviluppo, provate a passare alla versione cutting edge, che dovrebbe risolvere alcuni dei problemi. Se invece scegliete di fare un build della vostra versione, allora le istruzioni sono qui.
16 |
17 | In secondo luogo, installate [Mix](https://github.com/ethereum/cpp-ethereum/releases) il nostro ambiente di sviluppo integrato disponibile per Windows e Mac. Se utilizzate Linux, seguite le istruzioni qui per installare Mix.
18 |
19 | Infine, installate [Mist](https://github.com/ethereum/go-ethereum#automated-dev-builds) per testare le vostre Dapps e calibrare i vostri front-end a mano a mano che li sviluppate.
20 |
21 | ## Extras
22 |
23 | Un text editor o Mix puo’ essere utilizzato per creare il codice backend dei contratti che scriveremo. Per il linguaggio Serpent vi suggeriamo di programmare il vostro editor affinche’ consideri i contratti scritti in Serpent e salvati con il suffisso ‘.se’ come sintassi python e per il linguaggio Solidity vi consigliamo di salvare i files con il suffisso ‘.sol’.
24 |
25 | Il live refresh non e’ raccomandato mentre lavorate sulla vostra front-end in html, dato che non e’ stato testato appieno.
26 |
27 | ## Installare Alethzero
28 |
29 | Il nostro ambiente di sviluppo integrato Mix e’ al momento in constante sviluppo e nonostante alcune caratteristiche siano gia’ presenti in questo tutorial ci concentreremo principalmente sullo sviluppo dei contratti, e la costruzione dei frontend utilizzando il nostro client di sviluppo Alethzero. Alethzero ha un compilatore gia’ integrato, una console javascript, e gli strumenti necessari per dare un’occhiata allo stato della blockchain.
30 |
31 | A meno che non sia espressamente specificato, questo tutorial deve essere eseguito su Alethzero utilizzando una chain privata e senza connettersi alla rete – inserire contratti nella rete di test dovrebbe essere riservato a quei contratti che volete condividere con altri. Quando caricate alethzero in questa modalita’ e’ possibile che altri accedano alla vostra chain fintanto che utilizzano lo stesso nome e usano la funzione ‘connect-to-peer’ per connettersi direttamente.
32 |
--------------------------------------------------------------------------------
/it/[Italian] Tutorials sui contratti intelligenti.md:
--------------------------------------------------------------------------------
1 | #Tutorials sui contratti intelligenti (smart contracts)
2 |
--------------------------------------------------------------------------------
/it/[Italian] caratteristiche di serpent.md:
--------------------------------------------------------------------------------
1 | #Caratteristiche di Serpent
2 |
--------------------------------------------------------------------------------
/it/[Italian] ethereum apis.md:
--------------------------------------------------------------------------------
1 | #Ethereum APIs
2 |
--------------------------------------------------------------------------------
/it/[Italian] installazione su Mac.md:
--------------------------------------------------------------------------------
1 | #Installazione su Mac
2 |
--------------------------------------------------------------------------------
/it/[Italian] installazione su Ubuntu.md:
--------------------------------------------------------------------------------
1 | #Installazione su Ubuntu
2 |
--------------------------------------------------------------------------------
/it/[Italian] installazione su Windows.md:
--------------------------------------------------------------------------------
1 | #Installazione su Windows
2 |
--------------------------------------------------------------------------------
/it/[Italian]-Ethereum-TOC.md:
--------------------------------------------------------------------------------
1 | ### Benvenuti. Ethereum: il contratto intelligente di nuova generazione e piattaforma di applicazioni decentralizzate.
2 |
3 | [Libro Bianco di Ethereum](https://github.com/ethereum/wiki/wiki/%5BItalian%5D-Libro-Bianco)
4 |
5 | [RLP](https://google.it), la caratteristica del prefisso lineare ricorsivo, utilizzato per la codifica dei dati attraverso Ethereum.
6 |
7 | [Patricia Tree](https://google.it) la caratteristica dell'albero Merkle Patricia (conosciuta anche come Trie), la struttura utilizzata per archiviare e processare attraverso la funzione di Hash lo stato della catena di blocchi in Ethereum.
8 |
9 | [Protocollo di connessione](https://google.it), caratteristiche.
10 |
11 | [Serpente](https://google.it), il linguaggio di alto livello usato per scrivere contratti. Vedi il tutorial qui.
12 |
13 | [LLL](https://google.it), caratteristica di Basso-Livello "Linguaggio di Basso Livello", usata per scrivere contratti nella serie PoC da Poc-3
14 |
15 | [Dagger](https://google.com), Prova di lavoro "proof-of-work" di Ethereum.
16 |
17 | [Protocollo di Blocco 2.0](https://google.it)
18 |
19 | [Protocolli](https://google.it)
20 |
21 | [Camera di Compensazione](https://google.it)
22 |
23 | [Introduzione allo sviluppo su Ethereum](https://github.com/ethereum/wiki/wiki/%5BItalian%5D-Introduzione-allo-sviluppo-su-Ethereum)
24 |
25 | [Impostare il proprio ambiente di sviluppo Ethereum](https://github.com/ethereum/wiki/wiki/%5BItalian%5D-Impostare-il-proprio-ambiente-di-sviluppo-Ethereum)
26 |
--------------------------------------------------------------------------------
/it/[Italian]-ethereum_json_rpc.md:
--------------------------------------------------------------------------------
1 | #Ethereum JSON
2 |
--------------------------------------------------------------------------------
/it/[Italian]-installare_ethereum.md:
--------------------------------------------------------------------------------
1 | #Installazione del client di Ethereum
2 |
--------------------------------------------------------------------------------
/it/[Italian]-mac_cpp_build.md:
--------------------------------------------------------------------------------
1 | Nonostante Mavericks sia richiesto per compilare l'app, l'app e' stata testata per girare su 10.8, 10.9 e 10.10.
2 |
3 | ## Compilazione con Homebrew
4 |
5 | Per la release stabile:
6 | ```
7 | brew tap ethereum/ethereum
8 | brew install cpp-ethereum --build-from-source
9 | brew linkapps cpp-ethereum
10 | ```
11 |
12 | Per la release di sviluppo:
13 | ```
14 | brew reinstall cpp-ethereum --devel --build-from-source
15 | brew linkapps cpp-ethereum
16 | ```
17 |
18 | E con l'opzione `--with-gui` potete anche compilare AlethZero e la suite di sviluppo Mix.
19 |
20 | Poi fate `open /Applications/AlethZero.app`, `eth` (CLI) o `neth` (interfaccia ncurses)
21 |
22 | Per opzioni e patches, guardate: https://github.com/ethereum/homebrew-ethereum
23 |
24 | ## Compilazione manuale
25 |
26 | ### Prerequisiti
27 | * Il piu' recente Xcode su Mavericks (almeno Xcode 5.1+).
28 | * Il manager di pacchetti Homebrew http://brew.sh *o* il manager di pacchetti MacPorts http://macports.org
29 | * XQuartz http://xquartz.macosforge.org/landing/
30 |
31 | ### Istallate le dependencies
32 |
33 | Utilizzando homebrew:
34 |
35 | brew install boost --c++11 # this takes a while
36 | brew install boost-python --c++11
37 | brew install cmake qt5 cryptopp miniupnpc leveldb gmp libmicrohttpd libjson-rpc-cpp
38 |
39 | O, utilizzando MacPorts:
40 |
41 | port install boost +universal # this takes a while
42 | port install cmake qt5-mac libcryptopp miniupnpc leveldb gmp
43 | (probably missing libmicrohttpd and libjson-rpc-cpp)
44 |
45 | ### Clonate il repository della sorgente e create una cartella di compilazione
46 | git clone https://github.com/ethereum/cpp-ethereum.git
47 | cd cpp-ethereum
48 | mkdir -p build # create build folder ('build' ignored by git)
49 |
50 | ### Compilate
51 | cd build
52 | cmake ..
53 | make -j6
54 | make install
55 |
56 | Questo installera' anche il cliente a linea di comando e le librerie in /usr/local.
57 |
58 | ### Istruzioni XCode
59 | Dalla cartella root del progetto:
60 | ```
61 | mkdir build_xc
62 | cd build_xc
63 | cmake -G Xcode ..
64 | ```
65 | Questo generera' un project file xcode insieme a delle configurazioni per voi: ethereum.xcodeproj . Aprite questo file in XCode e dovrete essere in grado di compilare il progetto.
66 |
67 | ## Troubleshooting
68 |
69 | Errori di collegamento possono essere generalmente risolti facendosi sicuri di avere gli indirizzi corretti:
70 |
71 | export LIBRARY_PATH=/opt/local/lib # this is MacPorts's default
72 |
73 | Fate in modo che il vostro `macdeployqt` puo' essere trovato. Ethereum si aspetta che sia in `/usr/local/opt/qt5/bin/macdeployqt` quindi fate un symlink se non c'e':
74 |
75 | ln -s `which macdeployqt` /usr/local/opt/qt5/bin/macdeployqt
76 |
77 | Se non pianificate di partecipare allo sviluppo, fate in modo di compilare dal ramo master, non da quello develop o altri. Questi rami spesso possono essere rotti o avere altri requisiti.
78 |
--------------------------------------------------------------------------------
/it/[Italian]-mac_go_build.md:
--------------------------------------------------------------------------------
1 | ## Installazione con Homebrew
2 |
3 | Il modo piu' semplice di installare go-ethereum e' di utilizzare la propria tap Homebrew. Se non avete Homebrew, [installatelo qui](http://brew.sh).
4 |
5 | Poi eseguite il seguente comando per aggiungere la tap e installare `geth`:
6 |
7 | ```shell
8 | brew tap ethereum/ethereum
9 | brew install ethereum
10 | ```
11 |
12 | Potete installare la branch di sviluppo aggiungendo `--devel`:
13 |
14 | ```shell
15 | brew install ethereum --devel
16 | ```
17 |
18 | Per installare `mist`, aggiungete `--with-gui`.
19 |
20 | Dopo l'installazione, eseguite `geth` per far partire il vostro nodo.
21 |
22 | Per opzioni e patches, guardate: https://github.com/ethereum/homebrew-ethereum
23 |
24 | ## Compilare dal codice sorgente
25 |
26 | ### Compilare Geth (il client da linea di comando, CLI)
27 |
28 | Clonate la repository Github in una cartella di vostra scelta:
29 |
30 | ```shell
31 | git clone https://github.com/ethereum/go-ethereum
32 | ```
33 |
34 | Compilare `geth` richiede l'installazione di alcune librerie esterne:
35 |
36 | * [GMP](https://gmplib.org)
37 | * [Go](https://golang.org)
38 |
39 | ```shell
40 | brew install gmp go
41 | ```
42 |
43 | Infine, compilate il programma `geth` dando il comando seguente.
44 | ```shell
45 | cd go-ethereum
46 | make geth
47 | ```
48 |
49 | Adesso potete eseguire `build/bin/geth` per far partire il vostro nodo.
50 |
51 | ### Compilare Mist (GUI)
52 |
53 | **Nota: Mist al momento e' in fase di sviluppo percio' il funzionamento non e' garantito.**
54 |
55 | Clonate la repository in una cartella qualsiasi:
56 |
57 | ```shell
58 | git clone https://github.com/ethereum/go-ethereum
59 | ```
60 |
61 | Compilare `mist` richiede l'installazione di alcune librerie esterne:
62 |
63 | * [GMP](https://gmplib.org)
64 | * [Qt 5](https://www.qt.io)
65 | * [Qt 5 WebEngine](http://wiki.qt.io/QtWebEngine)
66 | * [Go](https://golang.org)
67 |
68 | Installate in primo luogo le suddette:
69 |
70 | ```shell
71 | brew install gmp go qt5
72 | brew link -f qt5 # This is required, sorry.
73 | ```
74 |
75 | Infine compilate `mist` dando il comando seguente:
76 |
77 | ```shell
78 | cd go-ethereum
79 | make mist
80 | ```
81 |
82 | Mist non cerca autonomamente nel posto giusto i componenti dell'interfaccia grafica. Potete dunque settare il percorso dei componenti mediante linea di comando.
83 |
84 | ```shell
85 | build/bin/mist --asset_path cmd/mist/assets
86 | ```
87 |
88 | Oppure eseguitelo dalla sua directory sorgente:
89 |
90 | ```shell
91 | cd cmd/mist
92 | ../../build/bin/mist
93 | ```
94 |
95 |
--------------------------------------------------------------------------------
/it/[Italian]-ringraziamenti.md:
--------------------------------------------------------------------------------
1 |
2 | # Ringraziamenti
3 |
4 | La nostra filosofia qui ad Ethereum e' che ogni sviluppatore - non importa quale sia il suo livello tecnico di abilita' - debba essere in grado di creare cose meravigliose sulla nostra piattaforma open-source, basata sulla blockchain.
5 |
6 | Tenendo cio' a mente, abbiamo lanciato questa guida per aiutare gli sviluppatori, da quelli esperti e abili su tutte le piattoforme ai principianti, ad imparare come impostare i clients di Ethereum, progettare le DAPPS e nel mentre imparare quelle skills necessarie a costruire applicazioni decentralizzate sulla piattaforma di Ethereum.
7 |
8 | A contribuire alla traduzione in Italiano: L. Maria Pedretti [Linkedin](https://it.linkedin.com/in/leonardompedretti), M. Terzi - [Linkedin](https://uk.linkedin.com/in/massimilianoterzi)
9 |
10 |
--------------------------------------------------------------------------------
/it/[Italian]-ringraziamenti_speciali.md:
--------------------------------------------------------------------------------
1 | # Ringraziamenti speciali
2 |
3 | Tramite il loro lavoro, queste persone stanno rendendo possibile la scrittura di questa guida.
4 |
5 | ####Vitalik Buterin
6 |
7 | _Creatore di Ethereum_
8 |
9 | **Gavin Wood**
10 |
11 | _C++/IDE/Whisper/Swarm Lead_
12 |
13 | **Jeffrey Wilcke**
14 |
15 | _Go/Mist Project Lead_
16 |
17 |
18 | *(la lista crescera' rapidamente molto presto)*
19 |
20 | ...
21 |
22 | ...
23 |
24 | ...
25 |
26 | Per la guida in Italiano:
27 |
28 | **L.Pedretti e M.Terzi**
29 |
30 | _http://www.ethereum-italia.it/_
31 |
32 | Infine, vorremmo anche ringraziare **_voi_** per far parte di questo progetto e per il vostro aiuto nel rendere possibile tutto cio'.
33 |
--------------------------------------------------------------------------------
/it/[Italian]-ripasso_conoscitivo.md:
--------------------------------------------------------------------------------
1 |
2 | ## Ripasso conoscitivo
3 |
4 | Esattamente come per l'ecosistema di Bitcoin, all'inizio c'era una certa frammentazione della conoscenza - un post su un blog qui, un tutorial su un forum li, un confuso articolo da un'altra parte e cosi' via.
5 |
6 | Questo libro rappresenta una collezione di pagine wiki, tutorials e altre informazioni rilevanti che fino ad ora erano sparse in giro per la rete, senza che fosse alcuna possibilita' di trovarle in maniera semplice.
7 |
8 | ## Lo scopo di questo lavoro
9 |
10 | Questa guida si propone di essere una maniera semplice per accedere alla knowledge base di Ethereum, in modo da poter aiutare persone da tutto il mondo ad iniziare a sperimentare con le tecnologie della blockchain.
11 |
12 | Si spera che attraverso questo lavoro, fintanto che ci avviciniamo ad una realta' nella quale tutti capiamo che piu' sperimentiamo con le tecnologie blockchain, e piu' arricchiamo l'ecosistema decentralizzato in modi unici - stiamo contribuendo a qualcosa di piu' grande che ad un mero progetto o ad un'iniziativa individuale.
13 |
14 |
--------------------------------------------------------------------------------
/it/[Italian]-ubuntu_go_build.md:
--------------------------------------------------------------------------------
1 | ## Opzione 1: Installazione da PPA
2 |
3 | Per avere la piu' recente versione in sviluppo, sia `ppa:ethereum/ethereum` che `ppa:ethereum/ethereum-dev` sono necessarie. Se voleste la versione stabile della release relativa all'ultima PoC (Prova di Concetto), omettete semplicemnte la PPA `-dev`.
4 |
5 | **Attenzione: La PPA `ethereum-qt` aggiornera' l'installazione Qt5 del vostro sistema, dalla 5.2 su Trusty e dalla 5.3 su Utopic, alla 5.4.*
6 |
7 | ```
8 | sudo apt-get install software-properties-common
9 | sudo add-apt-repository ppa:ethereum/ethereum-qt
10 | sudo add-apt-repository ppa:ethereum/ethereum
11 | sudo add-apt-repository ppa:ethereum/ethereum-dev
12 | sudo apt-get update
13 | sudo apt-get install ethereum
14 | ```
15 |
16 | Adesso scrivete `mist` per l'interfaccia grafica o `geth` per la linea di comando.
17 |
18 | In alternativa, potete installare solamente la interfaccia a linea di comando o solo l'interfaccia grafica, rispettivamente tramite `apt-get install geth` o `apt-get install mist`.
19 |
20 | ## Opzione 2: Installazione automatica
21 |
22 | **Nota** Sezione obsoleta, per favore usate le PPA.
23 |
24 | [Lo script di installazione di Mist](https://gist.github.com/tgerring/d4ab3f1672ed91a53c6c) installera' tutto cio' che e' necessario su una installazione di Ubuntu 14.04 ed iniziera' l'esecuzione di Mist.
25 |
26 | ```
27 | wget https://gist.githubusercontent.com/tgerring/d4ab3f1672ed91a53c6c/raw/677a3dd9c6db099eee620657bf7fb1e664173ee1/mist-develop.sh -O install
28 | chmod +x install
29 | ./install
30 | ```
31 |
32 | ## Opzione 3: Compilazione manuale dai codici sorgenti
33 |
34 | ### Installare Go
35 |
36 | Verificate che Go e' installato scrivendo `go version` e controllando la versione. Se non lo e', controllate [Installing Go](https://github.com/ethereum/go-ethereum/wiki/Installing-Go) (in inglese)
37 |
38 | ### Prerequisiti
39 |
40 | Mist dipende dalle seguenti librerie esterne, che devono essere installate:
41 | * [GMP](https://gmplib.org)
42 | * [Readline](http://www.gnu.org/s/readline/)
43 | * [Qt 5.4](http://www.qt.io/download-open-source/).
44 |
45 | Innanzitutto installate GMP & Readline dalle loro repositories:
46 | ```
47 | sudo apt-get install -y libgmp3-dev libreadline6-dev
48 | ```
49 | Dunque, seguite le istruzioni per [Building Qt](https://github.com/ethereum/go-ethereum/wiki/Building-Qt) (in inglese)
50 |
51 | ### Installare Mist
52 | Adesso che avete finito con i prerequisiti, i comando seguenti compileranno il client a interfaccia grafica Mist:
53 |
54 | go get -u github.com/ethereum/go-ethereum/cmd/mist
55 |
56 | (Probabilmente avrete bisogno di lanciare prima il comando "sudo apt-get install mercurial")
57 |
58 | **Nota**: Mist non cerca automaticamente nel posto giusto per i componenti dell'interfaccia grafica. Percio' dovete lanciare questo comando dalla sua directory di compilazione.
59 |
60 | cd $GOPATH/src/github.com/ethereum/go-ethereum/cmd/mist && mist
61 |
62 | o altrimenti fornite al sistema un'opzione assoluta `-asset_path`:
63 |
64 | mist -asset_path $GOPATH/src/github.com/ethereum/go-ethereum/cmd/mist/assets
65 |
66 | Per rimuovere il bisogno di ricordare questo complicato comando, potete create quanto segue in un file su $GOPATH/bin :
67 |
68 | #!/bin/bash
69 | cd $GOPATH/src/github.com/ethereum/go-ethereum/cmd/mist && mist
70 |
71 | Chiamate il file 'misted' e rendetelo eseguibile:
72 |
73 | chmod +x $GOPATH/bin/misted
74 |
75 | Adesso Mist puo' essere lanciato con il comando `misted`
76 |
--------------------------------------------------------------------------------
/it/[Italian]-win_cpp_build.md:
--------------------------------------------------------------------------------
1 |
2 |
--------------------------------------------------------------------------------
/it/[Italian]-win_go_build.md:
--------------------------------------------------------------------------------
1 |
2 |
--------------------------------------------------------------------------------
/it/[Italian]Cos_e_Ethereum.md:
--------------------------------------------------------------------------------
1 |
2 |
--------------------------------------------------------------------------------
/it/[Italian]La_filosofia_di_progettazione_di_Ethereum.md:
--------------------------------------------------------------------------------
1 |
2 | # La filosofia di progettazione
3 |
4 | Qui sotto abbiamo dettagliato i principi chiave che ispirano il lavoro sull'architettura e l'implementazione di Ethereum
5 |
6 | ## Semplicita'
7 | Il protocollo di Ethereum dovrebbe essere il piu' semplice possible, persino a costo di qualche inefficienza nell'immagazzinamento dei dati o inefficienza temporale. Un programmatore qualunque dovrebbe essere idealmente in grado di seguire e implementare l'intero concetto, in modo anche da minimizzare l'influenza che ogni determinato individuo o un gruppo di elite puo' esercitare sul protocollo stesso e incoraggiare la visione che Ethereum e' un protocollo aperto a tutti. Le ottimizzazioni che aggiungono complessita' non dovrebbero essere apportate a meno che non portino benefici sostanziali.
8 |
9 | ## Universalita'
10 | Una componente fondamentale della filosofia di progettazione di Ethereum e' che Ethereum non possiede "caratteristiche". Invece, Ethereum fornisce al suo interno un linguaggio di scripting Turing-completo che potete utilizzare per costruire qualsiasi "contratto intelligente" (smart contract) o tipologia di transazione che puo' essere definita matematicamente. Volete creare il vostro derivato finanziario? Con Ethereum, potete. Volete creare la vostra valuta? Fatelo con un contratto di Ethereum. Volete mettere in piedi un Daemon o Skynet in larga scala? Per farlo avrete forse bisogno di un paio di migliaia di contratti interellati, e dovrete far si' che si alimentino generosamente di carburante, ma niente vi proibisce di farlo.
11 |
12 | ## Modularita'
13 | Componenti diverse del protocollo di Ethereum dovrebbero essere progettate in modo da poter essere il piu' modulari e separabili possibile. Durante la fase di sviluppo dovrebbe essere facile poter fare una piccola modifica sul protocollo e avere l'insieme dell'applicazione che continua a funzionare senza ulteriori modifiche. Quelle innovazioni come Dagger, i Patricia trees e RLP dovrebbero essere implementate come librerie separate e costruite per essere complete anche se Ethereum non ha bisogno di alcune determinate caratteristiche, ma in modo che possano essere utilizzabili anche per altri protoccoli. Lo sviluppo di Ethereum dovrebbe essere pensato per apportare beneficio a tutto l'ecosistema delle criptovalute, e non solo a se' stesso.
14 |
15 | ## Non-Discriminazione
16 | Il protocollo non dovrebbe tentare di restringere attivamente o impedire determinate categorie di utilizzo, e i meccanismi di regolamentazione nel protocollo dovrebbero essere progettati in modo da regolare il danno, non da tentare di opporre specifiche applicazioni indesiderabili. Potete persino far girare uno script che genera un loop infinito su Ethereum fintanto che avete disponibilita' a pagare per la fee di transazione legata all'utilizzo computazionale della rete per farlo girare.
17 |
18 | ## Agilita'
19 | I dettagli del protocollo di Etheruem non sono marcati nella pietra. Nonostante il fatto che saremo estremamente giudiziosi nel fare modifiche ai costrutti di alto-livello come il linguaggio in stile C e il sistema di indirizzamento, prove computazionali piu' in avanti nel processo di sviluppo ci potranno indirizzare a scoprire che alcune modifiche all'algoritmo o al linguaggio di scripting miglioreranno sostanzialmente la scalabilita' o la sicurezza. Se avremo opportunita' del genere, state certi che ne faremo uso.
20 |
--------------------------------------------------------------------------------
/it/[Italian]_Tutorials_su_Serpent.md:
--------------------------------------------------------------------------------
1 | #Tutorials su Serpent
2 |
--------------------------------------------------------------------------------
/it/[Italian]benvenute_collaborazioni.md:
--------------------------------------------------------------------------------
1 | # Collaborazioni sono benvenute
2 |
3 | Questa guida vive su GitHub. Potete trovare tutto il contenuto di questa guida [anche in questa repository](https://github.com/ethereumbuilders/GitBook).
4 |
5 | Se volete saltare a bordo direttamente e contribuire su GitHub, per favore fatelo e godetevi quella trepida emozione di far parte di qualcosa che cambiera' veramente il mondo.
6 |
7 | Se volete far parte dei contributori del GitBook per favore scrivete a hello@ethereum.builders (in Inglese) e ciao@ethereum.builders (in Italiano, non ancora attiva) e vi risponderemo appena umanamente possibile.
8 |
9 | Se volete iscrivervi alla nostra chatroom su Gitter per salutarci, contribuire o dare del feedback cliccate sul pulsante sottostante.
10 |
11 | A presto!
12 |
13 | [](https://gitter.im/ethereumbuilders/GitBook?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
14 |
--------------------------------------------------------------------------------
/it/[Italian]il_perche_il_come_il_quando.md:
--------------------------------------------------------------------------------
1 |
2 | # Il Perche', Il Come e il Quando
3 |
--------------------------------------------------------------------------------
/jp/README.md:
--------------------------------------------------------------------------------
1 | ###**Questa guida è ancora in fase di sviluppo.*
2 |
3 | Guida di costruttori Ethereum.
4 | =======
5 |
--------------------------------------------------------------------------------
/jp/SUMMARY.md:
--------------------------------------------------------------------------------
1 | # Sumar
2 |
3 | * [Introducere](README.md)
4 | * [Thank you.](thank_you.md)
5 | * [This is a knowledge remix](this_is_a_knowledge_remix.md)
6 | * [Multumiri speciale](special_thanks.md)
7 | * [Open Collaboration Welcomed](open_collaboration_welcomed.md)
8 | * [The Why, How and What](They why, How and What.md)
9 | * [Ethereum design philosophy](design_philosophy.md)
10 | * [Design rationale](design_rationale.md)
11 | * [What can you do with it?](what_is_ethereum.md)
12 | * [Installing Ethereum Client](installing_ethereum.md)
13 | * [Build pe Ubuntu](building_on_ubuntu.md)
14 | * [C++](ubuntu_cpp_build.md)
15 | * [Go](ubuntu_go_build.md)
16 | * [Build pe Mac OS](building_on_mac_os.md)
17 | * [C++](mac_cpp_build.md)
18 | * [Go](mac_go_build.md)
19 | * [Build pe Windows](building_on_windows.md)
20 | * [C++](win_cpp_build.md)
21 | * [Go](win_go_build.md)
22 | * [API-uri Ethereum](ethereum_apis.md)
23 | * [JSON RPC API](ethereum_json_rpc.md)
24 | * [Javascript API](ethereum_javascript_api.md)
25 | * [Smart Contracts](smart_contract_tutorials.md)
26 | * [Solidity Features](solidity_features.md)
27 | * [Serpent Features](serpent_features.md)
28 | * [Serpent Tutorials](serpent_tutorials.md)
29 | * [Solidity Tutorials](solidity_tutorials.md)
30 | * Resurse
31 | * [Whitepaper](whitepaper.md)
32 | * [Glosar](glossary.md)
33 |
34 |
--------------------------------------------------------------------------------
/kr/README.md:
--------------------------------------------------------------------------------
1 | ###**Questa guida è ancora in fase di sviluppo.*
2 |
3 | Guida di costruttori Ethereum.
4 | =======
5 |
--------------------------------------------------------------------------------
/kr/SUMMARY.md:
--------------------------------------------------------------------------------
1 | # Sumar
2 |
3 | * [Introducere](README.md)
4 | * [Thank you.](thank_you.md)
5 | * [This is a knowledge remix](this_is_a_knowledge_remix.md)
6 | * [Multumiri speciale](special_thanks.md)
7 | * [Open Collaboration Welcomed](open_collaboration_welcomed.md)
8 | * [The Why, How and What](They why, How and What.md)
9 | * [Ethereum design philosophy](design_philosophy.md)
10 | * [Design rationale](design_rationale.md)
11 | * [What can you do with it?](what_is_ethereum.md)
12 | * [Installing Ethereum Client](installing_ethereum.md)
13 | * [Build pe Ubuntu](building_on_ubuntu.md)
14 | * [C++](ubuntu_cpp_build.md)
15 | * [Go](ubuntu_go_build.md)
16 | * [Build pe Mac OS](building_on_mac_os.md)
17 | * [C++](mac_cpp_build.md)
18 | * [Go](mac_go_build.md)
19 | * [Build pe Windows](building_on_windows.md)
20 | * [C++](win_cpp_build.md)
21 | * [Go](win_go_build.md)
22 | * [API-uri Ethereum](ethereum_apis.md)
23 | * [JSON RPC API](ethereum_json_rpc.md)
24 | * [Javascript API](ethereum_javascript_api.md)
25 | * [Smart Contracts](smart_contract_tutorials.md)
26 | * [Solidity Features](solidity_features.md)
27 | * [Serpent Features](serpent_features.md)
28 | * [Serpent Tutorials](serpent_tutorials.md)
29 | * [Solidity Tutorials](solidity_tutorials.md)
30 | * Resurse
31 | * [Whitepaper](whitepaper.md)
32 | * [Glosar](glossary.md)
33 |
34 |
--------------------------------------------------------------------------------
/ro/README.md:
--------------------------------------------------------------------------------
1 | ###**Acest ghid este in continua dezvoltare.*
2 |
3 | Ghidul ethereum builders.
4 | =======
5 |
--------------------------------------------------------------------------------
/ro/SUMMARY.md:
--------------------------------------------------------------------------------
1 | # Sumar
2 |
3 | * [Introducere](README.md)
4 | * [Thank you.](thank_you.md)
5 | * [This is a knowledge remix](this_is_a_knowledge_remix.md)
6 | * [Multumiri speciale](special_thanks.md)
7 | * [Open Collaboration Welcomed](open_collaboration_welcomed.md)
8 | * [The Why, How and What](They why, How and What.md)
9 | * [Ethereum design philosophy](design_philosophy.md)
10 | * [Design rationale](design_rationale.md)
11 | * [What can you do with it?](what_is_ethereum.md)
12 | * [Installing Ethereum Client](installing_ethereum.md)
13 | * [Build pe Ubuntu](building_on_ubuntu.md)
14 | * [C++](ubuntu_cpp_build.md)
15 | * [Go](ubuntu_go_build.md)
16 | * [Build pe Mac OS](building_on_mac_os.md)
17 | * [C++](mac_cpp_build.md)
18 | * [Go](mac_go_build.md)
19 | * [Build pe Windows](building_on_windows.md)
20 | * [C++](win_cpp_build.md)
21 | * [Go](win_go_build.md)
22 | * [API-uri Ethereum](ethereum_apis.md)
23 | * [JSON RPC API](ethereum_json_rpc.md)
24 | * [Javascript API](ethereum_javascript_api.md)
25 | * [Smart Contracts](smart_contract_tutorials.md)
26 | * [Solidity Features](solidity_features.md)
27 | * [Serpent Features](serpent_features.md)
28 | * [Serpent Tutorials](serpent_tutorials.md)
29 | * [Solidity Tutorials](solidity_tutorials.md)
30 | * Resurse
31 | * [Whitepaper](whitepaper.md)
32 | * [Glosar](glossary.md)
33 |
34 |
--------------------------------------------------------------------------------