 So hi, yma yw Bob Somwell. I'm the Executive Director of the Ethereum Classic Cooperative. I've been in that position since January. I previously worked at the Foundation, at Consensus, on the Enterprise Ethereum Alliance, where I worked for the set-up of that, and then I was the co-lead architect during that set-up, and then I was the Secretary of the Technical Working Group a'r cyfeirio y TSC, ac rydw i'n ei wneud yn rhywbeth yn mynd i'r hyffordd. Ac rydyn ni'n wedi'u gwybod i wneud ar gael. Felly, rydyn ni'n wedi'i gweithio i'r hollegau i chi'r hollegau. Rydyn ni'n meddwl yma yn rysgrifio'r hollegau ar gyfer cael ei wneud, byddwn i'w meddwl gwirio'r nadodran yn cyffredig. Mae'n meddwl ffodol yn ymdill. Felly mae'r ddodran y dyfodol o'r ddodran. Mae'r ddodran a'r ddodran yn ymdillogol. Mae'r ddodran o'r ddodran, ac mae'n ddodran o'r ddodran. Ond yma'n ddodran, mae'n cael eu ffordd i'w wneud. ..y'r Llyfrgell Llyfrgell, mae gennym yn cael y Llyfrgell Llyfrgell Llyfrgell. Felly, y ffrindiau i'r ddweud yw'r ffordd yn y Llyfrgell Llyfrgell yn 2015. Felly, mae'n gweithio'r projectaidd. Mae'n gweithio'r ddweud. Mae'n gweithio'r ddweud. Felly, mae gennym. A'r ddweud y gweithio'r gweithio i'r ddweud yw Llyfrgell Llyfrgell. Felly, Llyfrgell wasio'r ddweud yn y ffordd yn y Llyfrgell Llyfrgell yn y gweithio. Ac mae'n gweithio i'r ddweud yw'r ffordd yn byd y Bersantiam opgodau. So, classic is now not very far behind ETH. So, for Atlantis we had three clients with support. That's multi-geath, which is a downstream of the foundation geath. We had classic geath, which is a very ancient code base which was basically forked at the time of the dow, and then cobbled along for a little bit further, but is essentially in deprecation state. So, classic geath is not going to make it to the next fork. It's going to be a happy retirement for classic geath, as we clap it into retirement for its service, but its time is over. Parity has had support for both ETC and ETH throughout, so that's not a problem. And those are the three code bases that we've had for Atlantis. The other primary code base that there is on classic is Mantis, which is from IOHK. Now at the time that classic started, Charles Hoskinson returned into the classic side and said that as an Ethereum founder he felt a responsibility to support the original vision, that he felt that really he should get involved and help out. So he hired a community manager and he funded Let's Talk ETC podcast as well. And also Kevin Lord has done social media and sort of outreach bits and pieces as well. But they spent two years building a new code base in Scala, which is one of the tercest Ethereum clients that there is, and apparently is also the lowest memory footprint and highest performance. But nobody is really aware of it within the broader Ethereum ecosystem because it's been a classic only client, so nobody knows about it. Work started on that code base to add ETH support as well, but that team essentially got defunded and slowed down and stopped as of December of last year, really with Charles refocusing his efforts on Cardano and really sort of half exiting the classic ecosystem because of continual infighting and really feeling that he couldn't do the interesting things within classic that he wanted to. He sort of said if classic is just the litecoin of Ethereum, who wants to do that? We recently had the Ethereum Classic Summit in Vancouver, my hometown of Vancouver, and Charles, close to the end, only a few weeks to come, finally agreed that he would come and speak. So Charles had the closing keynote and through the conference, we basically like romanced him back in, charmed him back in and really what's going to happen there is that that code base is going to be revived. So as we go into our forthcoming hard forks, Mantis should be added into the set of clients there. So classic geth will be retired and you will have geth and you will have parity and you will have Mantis coming in as well. But not just that, you will also have Hyperledger Bezu. Now you may have heard of Bezu. So Bezu was previously called Pantheon and where that code base has come from is when I was involved with setting up the Enterprise Ethereum Alliance, myself and Shahan were the code lead architects and we did the tech talk at the launch event at which I said, so Shahan is the Distributed Systems PhD and I'm the cheerleader. So he basically then has spent the last two years back inside Consensus building a new code base from scratch. So that is permissively licensed to Apache 2. It is written in Java and it is Ethereum mainnet compatible, also supports CLEAK, also supports Istanbul BFT, also supports privacy features and is also compliant with the EEA specification. So it's really like, it's all of the stuff, it's all of the good stuff and it's really something that we've been striving for. I think for about three years is to get to a very high quality code base in a language which is broadly used under that kind of licensing and governance within the Linux foundation which basically lets large enterprises come and engage because I think really what you want to have with Ethereum clients is something like Linux kernel kind of model that you start out, well hey, here's a project just for fun but then things get serious and basically enterprises start depending on that stuff and they start picking up the load. So you see the Linux kernel, the major contributors are the big companies that have a need for that because really what you want is you want these big companies to be carrying the engineering load. You can't have the get team with four or five people carrying the weight of the world on their back forever. That just isn't going to work. You need large professional teams and that's really what started with Pantheon. So what the classic cooperative is doing is we are funding ETC support in Bezu and it's the very first thing that's happening within that code being within Hyperledger. So very soon what you will have is a client which can run Ethereum mainnet, ETC mainnet, Cotty, Gawly or any of these private scenarios. So chain safe for doing the work who did the work on classic to get that working for Atlantis. Now to work on Hyperledger code bases you don't have to be a Hyperledger member, anyone can work on those because we love Hyperledger. So we joined Hyperledger as well. We're applying to. So Hyperledger for anyone that doesn't know is a collaboration project within the Linux Foundation which is an umbrella for a set of open source blockchain technologies. So Hyperledger Fabric is the one that you hear about all the time that originally came from IBM. There's Sawtooth that originally came from Intel. You have Burrow which is an EVM but not mainnet compatible that was done by Monax. You have Iroha and you also have Hyperledger Indie which is an identity piece. The other thing that we've done is apply to join the Enterprise Ethereum Alliance. Well, why would we do that? Well, the fact is that you've seen announced here at this conference the mainnet initiative where the Ethereum Foundation and the EEA are basically working together on specking out use cases and protocol definitions for use of the mainnet for enterprise scenarios. So really the specification work that you've had happening within the EE are private or consortium chains. When we started the EEA the vision was that the mainnet and basically private and public these things would converge and that's where we're getting to right now and what you'll see really with classic being involved as well is that the specifications really like the yellow paper if you look at the yellow paper the yellow paper assumes that you have one network in the world. Eth mainnet hard coded block numbers in the specification and that is not the way to do a specification of a technology stack of a protocol. You should really have a modular setup that's like here is what an Ethereum stack looks like. Appendix A here is the definition of an eth mainnet here's the definition of an ETC mainnet here's the definition of a private chain running a proof of authority so we're going to help with that. Another thing that we've done recently is revived the old website. We had a maintenance issue one of the first things that my predecessor at the co-op Anthony Lucardi did was commissioned a spanky new wordpress website but the problem with that is wordpress websites only your admin can update it so we didn't really have a good means for the community to contribute changes back in. The earlier website that we had was based on GitHub and you could just do pull requests but you know it didn't look great so what we've done over the last little while is basically revived that old website but made it look nicer and updated the content and the guy who originally did the web design on that has just reappeared he actually attended the summit because he sees everything happening in classic and is like oh this is quite interesting I'm coming back so he can come back and help with the website because he did it originally. The other problem that we've had is problems of east-west communication specifically our Chinese community and other Asian communities have been very disconnected with the west and for China specifically a primary reason for that is the great firewall so if you are in mainland China you can't access Twitter you can't access Discord you can't access GitHub and specifically the communication channels are a major problem because the Discord and the Twitter that's where all of the communication happens so what I've done is well what's the answer well you use WeChat you can use WeChat anywhere in the world so we now have a mobile comms channel which is just an open WeChat channel where we've gathered all of the community people from all of the sides and myself and Yas and all of a sudden these communication gaps barring time zones they're done everyone is very communicative if you can communicate so we're doing that what we're going to do is on that main website we are adding internationalisation because we also had this siloing thing of the ethereum classic.org was English only and then other communities have built their own websites but then they don't have they're having to replicate well here's a tutorial about how we write a smart contract and what is classic and so on but by having language support within that base website most countries maybe that's enough that you just point to ethereumclassic.org and do the drop down you know like normal websites like professional people can do but somehow we've not done so we're going to do that and I mean that's not to say well you have to only use the official website obviously anyone can do whatever they like on their own and add their own pieces but we should have that basic information available to everyone and one of the other things that we can have in there is blog posts so this site allows you to use simple markdown for blog posts we have been using medium medium again blocked by the firewall so the flow that we will have instead is blog posts happening on that website that's accessible anywhere in the world probably in English first and then if you are flipping to one of the other language choices well you're going to get it in English if there isn't a translation if there is you're going to get it in your own language so that's a pattern which is not only breaching you know bridging east and west it's also bridging other communities Italian, German, French you know lots of these country specific ones that they're not necessarily developers you know that they are enthusiasts who can probably do a translation but you know they're essentially receiving information you know they're not necessarily ever going to be doing protocol changes or changes to clients but open that stuff up the other piece that we have is that the classic has signed a contract with Masari so Masari provide basically high quality financial information on particular coins and they're also showing developer activity you know where your repositories are what your transaction rate are and a lot of information about how the governance works what legal entities are involved how decisions are made what the issuance is and so on there hasn't been high quality information on classic and something as simple as the fact that we've had sort of messed up repositories and things have been pointing at Ethereum project where actually the work is happening in Ethereum classic or in another area you get this false data saying hey there's no developer activity there's no commits have happened and that's just wrong but really having that public disclosure is something that's very important to me I've been maintaining this conflict of interests statement myself for two years now where I list essentially all of my financial arrangements all of my associations all of my historical salaries my crypto holdings my tax filings everything because I think that in a sea of scammers you distinguish yourself by being transparent so that's what we've been up to we've got pending changes we're basically I think going to fast follow Istanbul so within a few months ETC is going to be caught up and moving between chains is going to be very trivial and beyond catching up we're actually going to have a few further changes so amazingly perhaps ETC is actually going to be objectively better than F1 within a few months which I think is going to blow people's minds gas prices will be lower the bloats will not be there the irregular state transaction will not be there and state channels work there's no need to bloat the L1 because we've got working state channels now so I think in a few months time we're going to be in a really great place people are going to be very surprised to say even if you don't have any ideological alignment it's just maybe a better deployment choice and there's my time up has anyone got any quick questions yep so Masari will have that information generally speaking I believe we've got a reasonable amount of transactions but they're primarily value transfers there is a DAP ecosystem but it's weak and that really is because these foundational things have been missing when we're at that point of having those foundations I think we are going to get an awful lot of DAP developers supporting both moving over really because it's easy to do so and it's going to be sort of cheaper and cheaper and better there's lots of things that have been doing to help that onboarding some of which Terry announced earlier like Gitcoin Swarm Support with MetaMask I think we can get MetaMask really very soon with some of the changes that they announced so I think we can have a Moloch Dow for funding a whole range of things which really should be the story should be all of the tools that you love on Ethereum same deal on Classic so 51% attacks are possible on any chain that's the nature of proof of work something though that I think maybe people don't kind of clock is that 51% attacks are not necessarily disastrous to the network they attack single participants who have poor trust models specifically usually exchanges an exchange who has received stuff and released things without getting a suitable amount of confirmations if you have less hash power well you really need to wait for a lot more confirms before proceeding that's the source of stuff that only really generally affects large value transfers if you're just doing little state changes of dappy stuff just don't wait a lot of confirms anyway I guess it's like a bus pass or whatever is money it's not hard money but that's fine not everything has to be rock hard money so I think the answer is that you are going to have that security at the bottom layer and you get less and less as you go higher up and really the thing that is going to get that security is having more hash power and that will happen as the developers come over as more and more activities happening that attracts the hash that gets you the security and there is no other answer than that really for P.I.W that's the nature of it so we have to get the activity when we get the activity we'll get the hash and we'll get the security thank you