 I'd like to share with you a little bit of the vision of the EA and how we are working toward intersection and working collaboratively with Ethereum Foundation and other organizations as well, moving forward. Just a little background from where I spent 12 years at Intel in the telecom side of things. So it's very interesting in my world and how it addresses the world of more of open source. So it's been a learning experience to figure out how we marry the best of both worlds. And I think that's one of the reasons why I think I was even invited to take the role of heading up the EA, is that we need to do that. We shouldn't try to reinvent the wheel. And so there's lots of benefits from both aspects of looking at what's the purest version of open source and how does that work? And how do you also protect the enterprises of which we address? And that's how we started. I joined last January, but as many of you know, the initial date was, Joe Lubin told me, it was February 29th of the prior year. And so in any event, it's a very new organization. But the intent was, OK, we have the open mainnet and there's a vision and a purpose for it. But again, what about the enterprise? And we are leaving out the opportunity for enterprises to do good in the world, as well as be profitable. So that's partially of the role of what I believe we should do and how we work. So we formed. And what we ended up doing, we took a look at initially the EA was even thinking of writing code. But when you look at the organizations that I am very familiar with or standards orgs that I'm familiar with and have been actively engaged in the last 15, 20 years, such as the IEEE. And I don't know if you're familiar with some of these, Etsy, and then 3GPP. And 3GPP is a partnership project. It's a group. It's not even formal. They write a spec. There's no code. And then it goes to Etsy, which is the European version of a standards org. But it covers international. And then it gets rubber stamped. And then it becomes a global spec. And the end result, and this is the philosophy that I'd really like to see, is that if you buy a cell phone here in Prague, and it's made in Korea, and then you show up in Venezuela and you buy a SIM card, you expect that phone to work. And that's all about interoperability and global interoperability. And that's the vision that I'd like to see our world be. And the way to do it is to have a standards org. And so a standards org doesn't write code. We should never compete with our members who do work. And then in order to enforce the standards code, you need some form of certification. And that's the reason why all these phones work. And where I come from, it's called NWIOT Network Interoperability Testing. Every one of those operators, buy that phone, they plug it into their own network, or they don't sign off on it. So we can't do all those things because that's hardware. But there's things that we could do for software. And there's lots of ways that you guys, because I originally came out of the entertainment gaming industry as a product marketing manager, there's lots that you can do to assure interoperability. So that's where I'm coming from. That's where I've got support from our board and the folks in our world. How do we do that using the EA? So I've walked you through. I'm not gonna go through all the slides, but you'll be able to get them. So I already share with you why standards are really important because without that, we can't accomplish that goal. In our org, we have a very good board of directors. And initially, I was telling some of the guys, I don't want you to think right now. I know it is all the biggest companies in the world. Where are they compared to the smallest ones? But, and as you know, in the world of blockchain and the enterprise, the lowest hanging fruit are financial services. So of course, and there's Amber, hi Amber. So she helps start the quorum side of things. So at any event, that was low hanging fruit. But if you take a look at some of the folks on our board, Andrew Miller from the University of Illinois, and then so we try to have a balanced approach and everybody gets one vote, no matter how big or small you are. And the organization, since I started, we've doubled in size. And I can share with you the argument that we make is okay, if you're looking for interoperability, if you're looking for of assurance, and I can tell you it's not easy to convince the enterprises to bet down, let alone understand what blockchain is, but to bet down and make a commitment, not easy. And so that's our story. We use what the EA is about. And it can help all of you, even if you're looking at where we're headed, which I would like to see us and when we talk about the roadmap. Enhance our specifications so we can do things to help accelerate the adoption on the public mainnet, because right now we're not doing that, but we want to. So we have 500 members and we're growing, continually growing more and more, and the reason why is they do want these enterprises whether small or large, and particularly if they buy from smaller companies, and I'm an ex-intel guy, but I can tell you, if Intel's competing in that very small company, it's really hard for the small company to get some traction. So being part of an organization like an EA, when you say you're writing code that conforms to the EA, here it's certified, they feel better about taking the risk. We're diversified, we have members from all over the world with different categories of business. So we try, the bottom line is folks are joining us in all the different areas. The way we're organized, we have a legal advisory group. We're not doing a tremendous amount of legal work, but we do try to intersect there. The technical spec work is headed by Connors Fenson, he'll come up and talk to you a little bit about a roadmap and our stack, and then we're forming a certification working group, and actually now we're gonna form a global test net, and that global test net means if you guys are writing solutions based on Enterprise Ethereum, and you can use our test net, we have a goal of getting that up and running. We now have a commitment from different companies, including Microsoft, to help us do this. So we plan to implement that, and then you can actually have your customers that they don't have to be a member of the org, and they can use it. And I'm just checking the time, is it tracking there or where is it? It tracked the time. You're there, keep me posted. Okay, so another thing that we do is we now have associate member programs, so I don't know if some of you saw it, but we entered an agreement with Hyperledger, and I was invited to present, and we did get an applause when Brian Bellendorf, and I don't know if he's here, invited me, but at the end of the day, I encourage the folks who work on Fabric to develop a version that can conform to the EA spec, and since they're not a standards org, there's very good synergy, and we invite all these other orgs that could be synergistic because there isn't any one org that really solves all the problems that you need for developing solutions for blockchain. We also are very involved with the Diff organization, some of the folks are familiar with the organizations that do social impact. We don't plan to deal with and write solutions for identity, we'll partner with the W3C, with Diff, ID 2020, and come up with solutions, so again, we don't want to reinvent the wheel. And so, how we operate, we have technical working groups, we also have special interest groups, and so we have one for financial services, one for health, and we're a member-driven org, we don't run the org, the members do, so if anybody wanted to have more visibility, whatever members want to see, they join and they raise their hands and they can make it happen, so that's how the org works, and that's how all standards of org works. So, with that, I wanted to bring up Connor, so I come out of the world of telecom, and telecom they have, it's called an OSI7 layer stack, we want to formalize how work is done technically, so you can have multiple vendors of choice, and by the way, this stack, you don't even need to take a photo, if you go to our website, now you don't even have to say who you are, because you can just go to our website and you can download our stack and our spec, everything, and just do whatever you want and developing whatever you want, and then if you want to use our logo, or go through our certification process, then you would be asked to join because of intellectual property requirements, et cetera, but anybody here can download our spec and work on Enterprise Ethereum, so I'll turn it over to Connor, he's gonna walk you through and talk to you a little bit about our architecture stack. Thanks, Ron, hey everyone. So, I'm the chair of the TechSpect Working Group, but I'm also, I guess, developer by background, I wrote Web 3J, the Java library for working with Ethereum and have my own blockchain technology startup as well, so I come at this from a, I guess, a dev perspective, ultimately. The idea, though, with the architecture stack, as Ron said, I guess inspiration was the ISI 7-layer model, but really it was the first artifact that the EA produced and put out there as a reference point to try and capture everything that we're thinking about with respect to the EA. The actual inspiration for the stack was a talk that was done at DevCon last year, where one of the developers working for the foundation did a talk on the anatomy of an Ethereum client, and one of the really neat things that they did there was they highlighted the components in yellow that were aligned with the yellow paper and basically adopted that idea as well, because I thought it's a really neat way of talking in terms of where these things are formally specified in the yellow paper, then also those components that are core to just general Ethereum, and then we added on a piece which was what we see as being more enterprise-focused pieces. The key always with the EA has been about Ethereum technology, and so we always see the initiatives that we're doing as being a super set of what's happening in the world of public Ethereum. We never want to sort of be separating ourselves from it because many members of the EA are passionate about Ethereum technology. That's why they joined up. That's what got me into it as well, because I came from an enterprise background, but then really like the Ethereum technology, and it reminds me of the community, reminds me somewhat of what of the Linux community back in the day, and we all know how well that panned out there as well. But the stack, I'm not gonna go through all the different layers about it now, but I think the key point is that we're trying to just encompass everything that we believe is in scope there, and you can certainly review it on your own time and go over to the EA website to review it. What I did wanna talk about though was the specifications that we've released this week. We released two new specifications. On this slide here, we have the organizations that directly contributed to these specifications. I think historically there's been sort of a perception with the EA that there was only a few firms contributing to it, but I think what's really nice about this is it shows that you've got a fairly good cross-section of different companies getting involved in the actual specification work, which I think is really cool to see. And so this week, the two specs that we released, one of them was the client specification V2, and so we released V1 to coincide with the consensus coin desk conference in May of this year. We're now on a six month release cycle with the EA specifications, whereby every six months the next version will come out, so we'd envisage the next one will be likely April next year. All of the development of these specifications now is taking place on GitHub. We're following similar sort of processes to how the W3C specs are being developed, so members are submitting issues and pull requests with changes. They get approved by just different members. There's actually gonna be a lot more transparency as well very soon in that we're going to be, the actual repose no longer gonna be private, so people can see exactly what's happening as the specifications evolve. But in terms of the highlights, just wanted to sort of bring your attention to a couple of them. One of them is that we've now, in the A-spec, we have a core set of JSON RPC API implementations from Ethereum that you need to implement. We're going to have an Enterprise Ethereum client. We've also added some additional ones, this EEA, which we use in EEA namespace, and this is mainly right now functioned around supporting the privacy models that are specified by the EEA. So these are your core entire approach to privacy where you have transactions being stored off chain, but also there's some on-chain techniques as well that the likes of Clematics have been promoting with their actual client implementation. We also reference the pre-compiled contracts as well, so we list the eight pre-compiled contracts that are specified in the yellow paper. They're all now referenced in the A-spec as being mandatory requirements. And the other thing as well is that we've actually provided an API for network permissioning. The governance of private permission networks is obviously a challenge, and so we've now included in our specification an API for this based on work that some members have contributed. So for us, I think it's a good move forward in that right now there's not really any standardization around this just yet. And we've also added in a security considerations section, but that's more based on just best practices around security for these permission chains. The other big specification release was the off-chain trusted compute spec, and so this was mainly driven by Intel and Iexec, but a number of different contributors did get involved, including Oracleize and I think Consensus did some stuff. But the point is it provides a JSON-RPC-based API for vendors whereby they can achieve or really achieve a few different things there. One is use it for Oracle-type services, another where they just want to use a secure enclave to do some sort of computation, or it could just be doing some sort of computations off-chain in a, again, a secure environment, but stuff that wouldn't actually be easy to do on-chain due to the performance requirements. So for us, we're really happy that it's made it out there because it's a second spec. We envisaged that there will be multiple specs appearing over time, but especially given that it's ready in time for this conference as well, we're happy to have it out there and I'm really keen for people to take a look and start feeding back into it. And so that was all I was gonna say here, and I'll pass back to Ron to talk about the roadmap. Thank you. So we have a timetable for roadmaps and we try to tie it to events, so it puts pressure on the folks doing work. And so that helps. So our plan is to have a six month, as Connor said, a six month cadence. So we're an open door. Anyone who wants to be involved in the EA can be a member and just to share with you. So you know, it's $3,000 for a member with a company that has 50 or less employees. So we try to make it affordable. We're a nonprofit, so the money that comes in just pays for the work that we do trying to support the activities to get the spec done. We're not a profit making venture and we don't make a lot of money and what we get, we get approved by our board and then we spend it on making sure our test net will get in place. We have a test net. We'll try to promote to the whole world the benefits of blockchain technology. So those are some of the things we do. And again, we hire folks to work on our spec and as far as making sure it conforms to the quality and caliber that if we show our spec to a standards org and there's, they're called SDOs, standards development orgs. They're even more rigid like IEEE and we're not, we're like a wifi alliance so we can do marketing. So the quality and caliber of our spec has to be top notch and that's why our spec version is 0.5 for the trusted execution because it's really our first one out. So we're not making it a formal spec yet compared to the other work that we're doing. So every six months, we'll be coming out with a new one. We're trying to get to the point of, you don't see the test net there because I wasn't sure that we'll have one until I get commitments from members to say they're gonna do it and now I just got those commitments here at DevCon. So we absolutely, and in order to make that happen, you need a common consensus mechanism, correct? So that's what we're working on. So anyone who's interested and you could have a reason, not everybody's looking at enterprise side things but we do wanna scale so our solutions can support all kinds of future aspects of what maybe some of the things that you're working on and then we'll have, so we'll be tying our next one time to, like the consensus 2018 event type frame and then by next DevCon we'll have release four and then our plans to launch certification. You do certification through independent labs. So I wanna leave it just a couple of minutes so we're just about done. I just share with you, we're really committed to social impact. Part of the reason why I have this here is that we're going to work hard to get the enterprises to support and they already do, I've learned about it through some of our board members but we really wanna do a good job to help the whole side of social impact. So with that said, we have just about five minutes for any questions. So there you go. Connor, you can come up in case it's technical. Thanks. On the roadmap is there gonna be another client implementation of Quorum? Okay, that's a good question. So initially Quorum jump-started the work that we did and but right now what we, I'd say this about six months ago, we transitioned that there was a Quorum working group and Amber was completely involved and she can tell you, we transitioned that and we did change the name because we want the work, we want this to be a collective. So there isn't anything that Quorum's work contribute to the technical spec that's built into the spec that you'll download. And so there are multiple clients that are all incorporated rolled into one that should be have the level interoperability is defined by what they all agree upon that's required must have. So you have Clearmatics, you have BlockApps, you have the new Pantheon solution. All of those folks worked very closely together. So Quorum is a platform or you can download the source code, write the Quorum and but the goal is and it is because the Quorum guys are very involved in our org it'll conform to the A spec. Any other questions, Alex? Sorry, could you share? I know that there was a couple of sessions that we had on interaction with like public Ethereum. Could you just give a high level overview of what the outcomes of those were? Yeah, I'll talk a little bit about it and where so we've had multiple meetings with the folks from public Ethereum and our goal is we should be very collegially working collaboratively together and we are. We tracked the roadmap that goes on and the Ethereum Foundation, we had some meetings where we talk about like the EIP process and how the EIP process should benefit, we should be mutually benefiting each other. So we had a two hour meeting that Connor actually presented on and others and so we will actually look at what we develop and if we can see things that can work on the ECRs or any of the EIPs that makes sense, we'll do it. And we're also giving visibility to the folks in the Ethereum Foundation too. They can go participate and see what we're doing. What's not on here and I'll just say right now the work we're doing is our private permission networks. I've talked to folks in our org and teammates. We want a roadmap to address public commercial networks that use the Ethereum mainnet and so part of what we're looking to do and I've talked to a number of companies they to join us and contribute. How do we bring that in and so we're leveraging, there's so many opportunities for the public mainnet that are commercial and I can think of some that I'd love to see like get rid of the ticket scalpers, the second hand ticket market. I would pay money to have that done. So your imagination could just take you everywhere for what we want to do because there's a lot of work but you definitely need to create a spec, you need to get it certified if you're gonna get like FIFA or anybody else to say I'm gonna buy into it, they're gonna want to know that there's 500 companies behind it, there's multiple vendors that they can pick from. Any other questions? Great, thanks very much. Thank you.