 Thank you, Jamie. And I'm really glad to see this conference take off. Wall Street has been an early adopter of all sorts of information technologies. That's an obvious statement. But open source software has been a big thing here for a long time, too. I remember even in the late 90s, lots of pockets of people using Python, using PHP and Apache and technologies, and even the first inklings of big data and such. And they wouldn't tell their bosses. They wouldn't tell anybody because it was Wall Street. You didn't tell anybody anything about how your operations worked. And what's been nice to see over the last 20 years is Wall Street opening up and starting to contribute code upstream to open source projects and get official recognition from their CIOs and CTOs and such that not only is there a reason to use open source software, there's a reason to contribute back. So that's been really great to see. And one of those places where this has manifested itself is not just in the standards operating systems, the cloud kind of movement, that sort of thing, but in new wave technology domains as well, where things are still being sorted out. And it's not just the proprietary vendors figuring this out. It's open source communities trying to make that happen, too. So Wall Street has been a really big part of the Hyperledger project for a long time. And I've been really happy to see that and happy to see this event covering all sorts of different sides of the blockchain space as well. You've heard a bit about kind of the cryptocurrency side and the public ledger side. And I wanted to talk more today about what we're doing at Hyperledger on more of the enterprise side of blockchain technology. And all of you now have probably also heard that at the Linux Foundation, there's a bit more than just Linux going on. In fact, the template that the Foundation had forged around bringing together two layers of community, one layer being the software developers, giving them kind of a neutral ground to work together. And just enough structure, just enough bureaucracy to make sure people are maximally efficient with their time and able to ship software that enterprises can trust. But not actually doing the software development ourselves instead acting somewhat as air traffic control. And then the second layer being the commercial ecosystem on top, bringing companies together to help build their use of the technology and how they explain that to their customers. And in the blockchain space, what has started out, perhaps, as a kind of a move from talking about purely the payment side and programmable money and people talking about the blockchain. If you ever hear somebody use the definite article in front of the word blockchain, what they've missed, perhaps, is that the way people are rolling this stuff out now is as a lot of different ledgers that are specific to a given community. A community that might be forged around a set of use cases in, say, the banking sector, around trade finance or around payments. But it could also be around a community of organizations focused on health care, a community of organizations focused on the supply chain. I'll talk about a couple of examples that are using hyperledger technology today. But we're increasingly seeing this kind of multi-ledgered world. And that if we do it wrong, that will be a whole lot of different technologies, a lot of bespoke, small batch, artisanal kind of blockchains out there that end up being pretty complex to manage. If we do it right, then we have a lot of common software underneath, a lot of common protocols between those parties. And that's really what we're trying to build at hyperledger is recognizing that there are lots of different motives for building these blockchains, building these distributed systems. And some of those strive architectural decisions that lend themselves towards either particular consensus mechanisms on a distributed ledger, particular approaches to smart contract languages. Some that may need to be more locked down because they're in a very regulated space, where the cost of being wrong is very high. Others that are more opened up, more participants on the network, a lesser kind of regulatory or contractual relationship between the parties, full-turing completeness is desired in the smart contract system, that sort of thing. And so supporting that whole spectrum is really where we've focused. We like to think of ourselves as a home for token agnostic technologies, and that ultimately what we come up with could be used to build a very widespread payment system, but it could also be used to build that network between five banks that people want to see deployed. How do we support that full spectrum? And in a way, it's kind of like the way that the database world never really converged on only one true database. Instead, you have MySQL and Cassandra and Berkeley DB and all these other kind of points in the solution space. And it probably will be the same way for blockchain technology as well, which is why at Hyperledger, rather than say, hey, there's one true architecture, like actually, frankly, you have in the Linux kernel. You have Linus Torvalds with a very strong opinion and his lieutenants and other developers in that community saying, we'll do a lot of experimentation. We'll try a lot of things. But ultimately, we're going to converge on probably objectively the right way to build a certain approach to file system drivers, to process management, that sort of thing. Instead, at Hyperledger, we said, this is still a young space. We still don't know what the solution space looks like, how continuous is it? Can it be solved with one single architecture, or does it require things that are semantically or conceptually as different as MySQL and Cassandra? And so we took very early on a big tent approach, or as we've called it, the greenhouse. And now have 10 different projects within that greenhouse, all at different stages of the move from pure R&D project to finalized in production. Two that are now in production and being used in some pretty fun places. And I'll show that in a bit, are Hyperledger Fabric and Hyperledger Sawtooth. And I'll go to more depth on what they do and their differences in just a bit. But overall, five of those 10 are what we're calling frameworks. And these are technologies that if a group of you were to go build a distributed ledger, to build a common system of record between yourselves, each of you would stand up a node that you'd have control over. And that might be hosted in the cloud, that could be hosted with somebody providing a blockchain as a service service, or it could be on your own physical hardware if you really wanted your hands around that. But you'd stand up a node, you'd point that node at a certificate authority, which kind of acts like the referee on a football field. They grant a certificate to participate in that blockchain network. That would also point you to the other peers. And you fire that up and run, and you start writing transactions and confirming other people's transactions in a way you go. So that's what we're calling a framework. And today, we have five different frameworks in Hyperledger. Again, two of those Fabric and Sawtooth, two others that are really getting a lot of, well, actually, the other three are all getting traction in different ways and are specific in ways. Indie is very focused on distributed digital identity. Hyperledger Borough is an implementation of the Ethereum virtual machine. And Eroha is this kind of redheaded stepchild from Japan that is very focused on payments and very focused on mobile. And we're still trying to figure out exactly the right way to fit it in. But we'll go into more depth on that in a bit. And then a whole bunch of tools that make using these technologies better. One that's an authoring environment called Hyperledger Composer. Another that's kind of a cluster management tool called Cello, which is being really reoriented around Kubernetes, using Kubernetes as the deployment and management framework. Hyperledger Explorer, which is about being able to browse around your ledger and see how these bits are connected and these transactions are connected to each other. And then a performance package called Hyperledger Caliper, which is about trying to get to an apples to apples comparison when you characterize the performance of a given blockchain network. A whole lot of momentum has emerged in the almost three years that we've been around. December 2015 was when we were announced. February 2016 is when the first code dropped. And in that time, I think we've done pretty well in terms of building the broader developer ecosystem and the broader commercial ecosystem around Hyperledger. We recently crossed 800 different contributors across those 10 different projects, some more than others. Some are much more mature as projects than others. But all of them now, all of the ones that have gone to production are now at the point where the contributor community is larger than just one vendor, than just one company. And that's pretty important, because that's part of the reason we exist is to provide this kind of multi-stakeholder framing around each of our open source projects. Lots of activity out there on the international side as well, blockchain technology is not being driven by Silicon Valley as much as many of the other technology movements. So for us, it's been important to have active meetup communities and software development and events like our hack fests and others in places like Singapore and Beijing and all over Europe. And so the meetup communities are truly global at this point. And they're getting together. They're talking about use cases. They're also writing code. We also have had a lot of activity recently in these working groups and working groups for us. Some of them are cross-cutting and very technically focused, one on architecture, for example, that has published a series of papers on consensus mechanisms, on smart contracts, that sort of thing to try to weave together these five different frameworks that we have into something that makes some sort of coherent kind of sense. The identity working group has also been very active in trying to talk about how do we reconcile blockchains with the GDPR, for example. And then also some sector-specific working groups that we've launched, one around health care, which was an essential way to try to reach a community that had lots of questions about blockchain technology and very little background or experience in distributed systems. And so trying to meet them where they are and talk about use cases, talk about constraints. When would you not use a blockchain? There's a lot of reasons not to use a blockchain. It's a very slow database. But to try to talk about where that would make sense, that community actually said, well, let's pick a use case. And somebody said, well, we're in the breast milk donor supply chain business. And there's some real problems with the way things work today that maybe blockchain technology might address. That community now has spun up its own software development project around implementing blockchain technology, implementing Hyperledger for that use case as a public exposition of how do we build something like this? How do we marry the constraints of the use case with the constraints of the technology and figure out something interesting? That's been really fun to watch. But by and large, lots of different fun activity going on. Oh, I should also mention the membership base, because like other Linux Foundation projects, all of our work is done publicly. It's all open source. There's no special rights that accrue to members in terms of access to code or participation in the open source project. But we're supported in our efforts by our members. And so we've grown from kind of the companies you've heard of and expect companies like IBM and Intel and DTCC, which I'm sure many of you hear. Nobody outside of Wall Street has heard of DTCC. And I think they prefer it that way. But I really like them. Hi, Rob. And you'll hear from Rob yesterday. You'll hear from them the whole of your new today. Yeah, good, because it's an awesome story. But we've also grown in the form of adding kind of really top tier participation from health care companies, companies like Change Health Care, who have a network in production today processing millions of transactions a day, which from a big data perspective is still small beans. But these are transactions that have to do with flowing health care insurance claims from basically from clinics and doctors to payers and back. And Change Health Care is part of McKesson. And they process about $2 trillion a year worth of health care claims. 80% of all health care claims in the United States get touched by their system at one point or another. And so they're in production with the network now. But we've also added lots of other members, lots of geographic diversity to what we do. By the way, in the last slide, Baidu might seem like an odd duck to be there. Baidu is actually doing a lot with blockchain technology internally, as well as deploying a blockchain as a service offering. And we're seeing 10 cents in Alibaba. All have also launched blockchain as a service cloud offerings in China for supply chain purposes and for others. And companies like Airbus and Daimler, who are not blockchain companies. They're not even IT companies, but who see that reinventing their business at a pretty deep level. So a really fun group of companies, and even a broader general membership, that represents companies across finance, across health care, and all sorts of different supply chain settings. Supply chain isn't really a sector so much as something every sector does. So it's been really fun to see that play out in all these areas. In addition to building relationships with lots of government agencies, nonprofits, student associations, and other universities out there, both these kinds of organizations don't support us financially, which is great. They support us in other ways. We use these as a lever to get out to their communities, as well. When somebody like the Produce Marketing Association wants to talk with us, we're like, why? And it's because everybody in the produce shipping business is talking about using blockchain technology as a way to keep the next E. coli disaster from causing all produce from California from being banned for the entire US market, and blockchain technology potentially plays a role in that sort of thing. So let me talk really quickly about a couple of use cases that we've seen Hyperledger in production today serving real needs. There's a network that's been set up by Deutsche Bank, HSBC, Santander, Society General, a lot of other large banks to manage the flow of paper related to letters of credit related to all the kinds of bureaucracy and paperwork that gets involved in getting a container of stuff from one side of the world to the other. Nobody wants to send a bank wire to an address and then not see their stuff actually get delivered. So the financial world is set up all sorts of intermediaries and guarantees and insurers and export import banks and all this infrastructure to deal with a low trust environment when something like blockchain technology can really step in and cut a lot of the complexity and a lot of the different layers down to just a few. And so this network is about those banks helping their member accounts, their member companies, small and mid-sized businesses predominantly get easier access to credit, establish their history as a good trading partner much more efficiently and cut the time to issue a lot of this paperwork and documents. And believe it or not, the cost of sending a container from Shanghai to Los Angeles, half that cost is in the paperwork. And so if projects like this, especially if they start to involve port authorities and export authorities and such in managing that flow could do a lot to cut the cost of shipping goods around the world. Similarly, when it comes to food, there's a project that IBM and Walmart and a couple of other anchors have established. It's now in production. It's called the Food Trust Network. Initially it's focused on leafy greens and the kind of domestic supply chain around that in the United States. Walmart actually had just announced that they will be requiring all of their suppliers, their tier one suppliers around leafy greens to all of their stores to be on this network next year. And by 2020, they think that goes well, they require the next tier beyond. Now, if it was just focused on Walmart, then it would just be a Walmart API and you could just build it as a Walmart central database. But even Walmart doesn't have the market strength to be able to say, we want this all to be centralized on us whether they would perhaps like that like any business would, but that wouldn't carry enough weight with the rest of the ecosystem to make sense. Instead, Walmart is setting this up again with IBM and others and they're inviting other retailers to be a part of that. They're inviting their competitors to be a part of that because that increases the value for everybody in that ecosystem. And ultimately the governance organization behind that will have to reflect that kind of diversity. It'd be interesting to see where that goes. And in China, there's some really big deployments that have been done kind of almost without our awareness or knowledge. There's a bank called China Minsheng Bank that has driven the deployment with about a dozen other large banks in China, including CITIC, which is perhaps the one that you've heard of, to also process domestic letters of credit, which are basically corporate debt. The first day that they launched this in production, they processed 100 million rem in B, which is about $16 million of US dollars worth of letters of credit issuance, and they're now up to a couple hundred million rem in B per day. This is a market that worldwide processes a couple trillion dollars a day, US. So this is still kind of just a small segment of it, but pretty exciting. And that's on fabric now in production. Likewise, there's another project that's a startup. They're based in China that is built a legal documents blockchain for a number of these internet courts that have been set up in China. These are courts where you can appear, present evidence, talk to a jury, and then get your case resolved entirely online. And there's reasonable concern that the repository of these documents was a really attractive target for hackers. So having a document repository that could be tied to timestamps, it could be tied to hashes of those documents where you could get a sense of is this the complete record of all the documents in that system was pretty essential. So they've been deployed now for almost a year. They have 10 million documents in the repository. All sorts of business legal processes have actually converged to deliver this. So that's really fun to see. Just briefly on kind of like what's new with each of the different frameworks, fabric was 1.0 like mid last year. So 1.3, which is in release candidate now is ready. It's got a bunch of new feature support for different kinds of languages in the smart contract system for something called zero knowledge assets, which is a way of kind of having confidentiality around transactions. Lots of different parameters you can tune if performance is your goal. You can trade off performance for decentralization and get higher speed that way. All sorts of interesting things. Sawtooth as well, recently was released as 1.0, 1.1 is coming up pretty soon. And it was the first one to support solidity smart contracts. These are the smart contract languages. This is the smart contract language used by the Ethereum ecosystem. Indy, I mentioned is kind of our identity focused tool. This is a network that's being used by somebody called the Sovereign Foundation to build a kind of a global kind of overlay connecting identities across different blockchain ledgers in a way that's protective of individual identity and of individual confidentiality. There's a big project in the Philippines now to use this to implement a KYC mechanism but pivoted around individuals. It's kind of like if you had control over your credit rating, your credit history and could decide who to share that data with and audit that sharing, this is a platform for doing that. I mentioned borough. Borough is our EVM interpreter that gets plugged into Sawtooth and actually support in fabric for it now. This is the only Apache licensed EVM out there. And it's been a key part of building a bridge to the public ledger community and to the community of other companies built around that. In fact, we've announced recently last week, actually, a partnership with the Enterprise Ethereum Alliance which is a standards body in the Ethereum space. We hope to actually use as a basis for finding other projects that are related to the Ethereum ecosystem that we can work on together. Really exciting stuff. And finally, I mentioned, everyone asked about interoperability if you have all these different ledgers out there. Doesn't that hurt your ability to actually have a really fluid marketplace? And there's going to be a lot of different approaches to interop and a lot of different backbone ledgers, I think that will connect and act as kind of a discovery tool between ledgers. But one of our plays here is a toolkit. It's still pretty young. It's called Quilt and it's an implementation of the interledger standard which is a way to do atomic swaps between these different networks. You want to buy a house and you want to pay for it with Bitcoin. You really want transactions on those two different ledgers to both succeed or both fail. Otherwise you need escrow and all that kind of stuff. And this is a toolkit for doing those kinds of things. Another big win for us in the last year is we put out an educational course on edX that has had over 100,000 people sign up for it. Some of you might have taken it and seen my face on the videos and I'm sorry for that. But it's gotten really great reviews and in fact we've added more content to that. We've also developed some more formal training around managing hyperledger fabric and sawtooth infrastructure and we'll start doing developer certification against those standards and a test for a harness against those standards before the end of the year. And with that, that's kind of the state of where we are now. It's really a rocket ship. Very few of us on my staff have gotten a full night's worth of sleep in the last couple of months because we've been on such this rocket ship but it's really exciting and the amount of actual productive pickup of these tools has been great to see. It's not aspirational, it's real and it's here today. Thank you very much.