Skip to content

Latest commit

 

History

History
362 lines (248 loc) · 17.8 KB

preface.asciidoc

File metadata and controls

362 lines (248 loc) · 17.8 KB
Raw

Preface

Writing Mastering Ethereum

As with, I suspect, a great many thinks, this book came about as the merging of several different threads stories and ideas. For my part I had been wishing to write a book that expanded on the Yellow Paper (my technical description of the Ethereum protocol) for some time, primarily to open it up to a wider audience than the original greek-letter-infused document could posibly allow.

Plans were underway---publishers had been found---when I got talking to Andreas. I knew Andreas from the very beginning of my tenure with Ethereum. Having coded the first few Ethereum proofs of concept, Andreas was a notable personality in the space who was interested in learning more about what we were doing. He downloaded and built my code to see, I presume, what the fuss was about first hand. We chatted a little over Skype and I was happy to find that he was generally supportive of what we were experimenting with.

Fast-forward two years and it’s the 29th of May, 2016. Andreas had mentioned he’d be interesting in working on a following book to Mastering Bitcoin that covered Ethereum and finally, we were both, oddly enough, in the same city at the same time. We met up for a coffee to chat about working on a project together - a merging of our ideas, so to speak. The upshot of the meeting was to agree to pursue it. With both of us being devotees of the open-source paradigm we were both committed to this being something of a community-effort and released under a creative commons license. Thankfully our publishers, O’Reilly, were happy to agree.

With O’Reilly on-board with our proposal, we pushed forward with content. Co-authoring content that needs to be coherent is not necessarily an easy task. In our case, the workflow was essentially involved Andreas writing an initial draft of each chapter and me following up, injecting or mending technical content as needed. I think things worked reasonably well, but we’ll let you be the ultimate judge…​

Intended audience

On the bees on this book’s cover

The Western honey bee (Apis mellifera) is a species that exhibits highly complex behavior that, ultimately, benefits its hive. Each individual bee operates freely under a set of simple rules and communicate findings of importance by pheromones and waggle dance. This dance carries valuable information like the position of the sun and relative geographical coordinates from the hive to the target in question. By interpreting this dance, the bees can relay on this information or act on it, thus, carrying out the decentralized will of swarm intelligence.

Although bees form a caste-based society and have a queen for producing offspring, there is no central authority or leader in a beehive. The highly intelligent and sophisticated behavior exhibited by a multithousand-member colony is an emergent property that arises from the interaction of the individuals in a social network.

Nature demonstrates that decentralized systems can be resilient and can produce emergent complexity and incredible sophistication without the need for a central authority, hierarchy, or complex parts.

Conventions used in this book

The following typographical conventions are used in this book:

Italic

Indicates new terms, URLs, email addresses, filenames, and file extensions.

Constant width

Used for program listings, as well as within paragraphs to refer to program elements such as variable or function names, databases, data types, environment variables, statements, and keywords.

Constant width bold

Shows commands or other text that should be typed literally by the user.

Constant width italic

Shows text that should be replaced with user-supplied values or values determined by context.

Tip

This icon signifies a tip or suggestion.
Note

This icon signifies a general note.
Warning

This icon indicates a warning or caution.

Code examples

The examples are illustrated in Solidity, JavaScript and Python, and using the command line of a Unix-like operating system. All code snippets are available in the GitHub repository in the code subdirectory of the main repository. Fork the book code, try the code examples, or submit corrections via GitHub:

All the code snippets can be replicated on most operating systems with a minimal installation of compilers, interpreters and libraries for the corresponding languages. Where necessary, we provide basic installation instructions and step-by-step examples of the output of those instructions.

Some of the code snippets and code output have been reformatted for print. In all such cases, the lines have been split by a backslash (\) character, followed by a newline character. When transcribing the examples, remove those two characters and join the lines again and you should see identical results to those shown in the example.

All the code snippets use real values and calculations where possible, so that you can build from example to example and see the same results in any code you write to calculate the same values. For example, the private keys and corresponding public keys and addresses are all real. The sample transactions, contracts, blocks, and blockchain references have all been introduced to the actual Ethereum blockchain and are part of the public ledger, so you can review them.

Using code examples

This book is here to help you get your job done. In general, if example code is offered with this book, you may use it in your programs and documentation. You do not need to contact us for permission unless you’re reproducing a significant portion of the code. For example, writing a program that uses several chunks of code from this book does not require permission. Selling or distributing a CD-ROM of examples from O’Reilly books does require permission. Answering a question by citing this book and quoting example code does not require permission. Incorporating a significant amount of example code from this book into your product’s documentation does require permission.

We appreciate, but do not require, attribution. An attribution usually includes the title, author, publisher, ISBN, and copyright. For example: "Mastering Ethereum by Andreas M. Antonopoulos and Gavin Wood (O’Reilly), 978-1-491-97194-9. Copyright 2018."

Some editions of this book are offered under an open source license, such as CC-BY-NC, in which case the terms of that license apply.

If you feel your use of code examples falls outside fair use or the permission given above, feel free to contact us at permissions@oreilly.com.

Ethereum addresses and transactions in this book

The Ethereum addresses, transactions, keys, QR codes, and blockchain data used in this book are, for the most part, real. That means you can browse the blockchain, look at the transactions offered as examples, retrieve them with your own scripts or programs, etc.

However, note that the private keys used to construct the addresses printed in this book have been "burned". This means that if you send money to any of these addresses, the money will either be lost forever or will likely be taken since anyone who reads the book can take it using the private keys printed herein.

Warning

DO NOT SEND MONEY TO ANY OF THE ADDRESSES IN THIS BOOK. Your money will be taken by another reader, or lost forever.

O’Reilly Safari

Note

Safari (formerly Safari Books Online) is a membership-based training and reference platform for enterprise, government, educators, and individuals.

Members have access to thousands of books, training videos, Learning Paths, interactive tutorials, and curated playlists from over 250 publishers, including O’Reilly Media, Harvard Business Review, Prentice Hall Professional, Addison-Wesley Professional, Microsoft Press, Sams, Que, Peachpit Press, Adobe, Focal Press, Cisco Press, John Wiley & Sons, Syngress, Morgan Kaufmann, IBM Redbooks, Packt, Adobe Press, FT Press, Apress, Manning, New Riders, McGraw-Hill, Jones & Bartlett, and Course Technology, among others.

For more information, please visit http://oreilly.com/safari.

How to contact us

Please address comments and questions concerning this book to the publisher:

  • O'Reilly Media, Inc.
  • 1005 Gravenstein Highway North
  • Sebastopol, CA 95472
  • 800-998-9938 (in the United States or Canada)
  • 707-829-0515 (international or local)
  • 707-829-0104 (fax)

Send comments or technical questions about this book to bookquestions@oreilly.com.

For more information about our books, courses, conferences, and news, see our website at https://www.oreilly.com.

Find us on Facebook: https://facebook.com/oreilly

Follow us on Twitter: https://twitter.com/oreillymedia

Contacting the authors

Information about Mastering Ethereum as well as the Open Edition and translations are available on: https://ethereumbook.info/

Contacting Andreas

You can contact Andreas M. Antonopoulos on his personal site: https://antonopoulos.com/

Subscribe to Andreas’s channel on YouTube: https://www.youtube.com/aantonop

Like Andreas’s page on Facebook: https://www.facebook.com/AndreasMAntonopoulos

Follow Andreas on Twitter: https://twitter.com/aantonop

Connect with Andreas on LinkedIn: https://linkedin.com/company/aantonop

Andreas would also like to thank all of the patrons who support his work through monthly donations. You can support Andreas on Patreon at: https://patreon.com/aantonop

Contacting Gavin

You can contact Dr. Gavin Wood on his personal site: http://gavwood.com/

Follow Gavin on Twitter: https://twitter.com/gavofyork

Gavin generally hangs out in the Polkadot Watercooler on Riot.im: https://riot.im/app/#/room/#polkadot-watercooler:matrix.org

Acknowledgments by Andreas

I owe my love of words and books to my mother, Theresa, who raised me in a house with books lining every wall. My mother also bought me my first computer in 1982, despite being a self-described technophobe. My father, Menelaos, a civil engineer who published his first book at 80 years old, was the one who taught me logical and analytical thinking and a love of science and engineering.

Thank you all for supporting me throughout this journey.

Acknowledgments by Gavin

My mother secured my first computer for me at the age of 9 years from a neighbour without which my technical progress would no doubt have been lessened. I also owe her my childhood fear of electricity and must acknowledge Trevor and my grandparents, who performed the grave duty of "watching me plug it in" time after time, and without whom said computer would have been useless. I must also acknowledge the various educators I have been lucky to have through my life, from said neighbour Sean (who taught me my first copmuter program), to Mr. Quinn my primary school teacher who fixed it for me to do more programming and less history through to secondary-school teachers like Richard Furlong-Brown, who fixed it for me to do more programming and less rugby.

I must thank the mother of my children, Jutta, for continued support and the many people in my life, friends new and old, that keep me, roughly-speaking, sane. Finally, a huge dollop of thanks must go to Aeron Buchanan without whom the last five years of my life could never possibly have unfolded in the way they did and without whose time, support and guidance this book would not be in as good a shape as it is.

Contributions

Many contributors offered comments, corrections, and additions to the early-release draft on GitHub.

Contributions on GitHub were facilitated by two GitHub editors who volunteered to project manage, review, edit, merge and approve pull requests and issues:

  • Lead Github Editor: Francisco Javier Rojas Garcia (fjrojasgarcia)

  • Assisting Github Editor: William Binns (wbnns)

Major contributions were provided in the chapters on DApps, ENS, Fork History, Gas, EVM, Oracles, Smart Contract Security and Vyper. Additional contributions, which were not included in the first edition due to time and space constraints can be found in the contrib folder on the GitHub repository. Thousands of smaller contributions were provided throughout the book, improving the quality, legibility and accuracy of the book. Sincere thanks to all those who contributed!

Following is an alphabetically sorted list of all GitHub contributors, including their GitHub ID in parentheses:

  • Abhishek Shandilya (abhishandy)

  • Adam Zaremba (zaremba)

  • Adrian Li (adrianmcli)

  • Adrian Manning (agemanning)

  • Alejandro Santander (ajsantander)

  • Alejo Salles (fiiiu)

  • Alex Manuskin (amanusk)

  • Alex Van de Sande (alexvandesande)

  • Anthony Lusardi (pyskell)

  • Assaf Yossifoff (assafy)

  • Ben Kaufman (ben-kaufman)

  • Bok Khoo (bokkypoobah)

  • Brian Ethier (dbe)

  • Bryant Eisenbach (fubuloubu)

  • Chanan Sack (chanan-sack)

  • Christopher Gondek (christophergondek)

  • Chris Remus (chris-remus)

  • Cornell Blockchain (CornellBlockchain)

    • Alex Frolov (sashafrolov)

    • Brian Guo (BrianGuo)

    • Brian Leffew (bleffew99)

    • Giancarlo Pacenza (GPacenza)

    • Lucas Switzer (LucasSwitz)

    • Ohad Koronyo (ohadh123)

    • Richard Sun (richardsfc)

  • Cory Solovewicz (CorySolovewicz)

  • Dan Shields (NukeManDan)

  • Daniel Jiang (WizardOfAus)

  • Daniel McClure (danielmcclure)

  • Daniel Peterson (danrpts)

  • Denis Milicevic (D-Nice)

  • Dennis Zasnicoff (zasnicoff)

  • Diego H. Gurpegui (diegogurpegui)

  • Dimitris Tsapakidis (dimitris-t)

  • Enrico Cambiaso (auino)

  • Ersin Bayraktar (ersinbyrktr)

  • Flash Sheridan (FlashSheridan)

  • Franco Daniel Berdun (fMercury)

  • Hon Lau (masterlook)

  • Hudson Jameson (Souptacular)

  • Iuri Matias (iurimatias)

  • Ivan Molto (ivanmolto)

  • Jacques Dafflon (jacquesd)

  • Jason Hill (denifednu)

  • Javier Rojas (fjrojasgarcia)

  • Joel Gugger (guggerjoel)

  • Jonathan Velando (rigzba21)

  • Jon Ramvi (ramvi)

  • Jules Lainé (fakje)

  • Kevin Carter (kcar1)

  • Krzysztof Nowak (krzysztof)

  • Lane Rettig (lrettig)

  • Leo Arias (elopio)

  • Luke Schoen (ltfschoen)

  • Liang Ma (liangma)

  • Marcelo Creimer (mcreimer)

  • Martin Berger (drmartinberger)

  • Masi Dawoud (mazewoods)

  • Matthew Sedaghatfar (sedaghatfar)

  • Michael Freeman (stefek99)

  • Miguel Baizan (mbaiigl)

  • Mike Pumphrey (bmmpxf)

  • Mobin Hosseini (iNDicat0r)

  • Nagesh Subrahmanyam (chainhead)

  • Nichanan Kesonpat (nichanank)

  • Nick Johnson (arachnid)

  • Omar Boukli-Hacene (oboukli)

  • Paulo Trezentos (paulotrezentos)

  • Pet3rpan (pet3r-pan)

  • Pierre-Jean Subervie (pjsub)

  • Pong Cheecharern (Pongch)

  • Qiao Wang (qiaowang26)

  • Raul Andres Garcia (manilabay)

  • Roger Häusermann (haurog)

  • Solomon Victorino (bitsol)

  • Steve Klise (sklise)

  • Sylvain Tissier (SylTi)

  • Taylor Masterson (tjmasterson)

  • Tim Nugent (timnugent)

  • Timothy McCallum (tpmccallum)

  • Tomoya Ishizaki (zaq1tomo)

  • Vignesh Karthikeyan (meshugah)

  • Will Binns (wbnns)

  • Xavier Lavayssière (xalava)

  • Yash Bhutwala (yashbhutwala)

  • Yeramin Santana (ysfdev)

  • Zhen Wang (zmxv)

  • ztz (zt2)

Without the help offered by everyone listed above, this book would not have been possible. Your contributions demonstrate the power of open source and open culture, and we are eternally grateful for your help. Thank you.

Sources

Some of the content of this book references or sources various public and open-licensed sources:

License: The MIT License (MIT)

License: The MIT License (MIT)

License: The MIT License (MIT)

License: Arxiv Non-Exclusive-Distribution

License: The MIT License (MIT)

License: Apache 2.0

License: Creative Commons CC0

Licence: Creative Commons CC BY 4.0