 Just, I can see it coming in through your mixer, just make sure you have that selected in here. You can see it coming in through your mixer, just make sure you have that selected in here. You can see it coming in through your mixer, just make sure you have that selected in here. You can see it coming in through your mixer, just make sure you have that selected in here. Is there anyone else who wanted to give a lightning talk, kitchen sink talk or any other kind of talk and did not come up yet? Then talk. Thank you. Thank you. Yeah, we have HDMI, VGA, dongle. Beautiful. Excellent. You're fake, aren't you? You're fake, aren't you? You're fake, aren't you? You're fake, aren't you? You're fake, aren't you? Okay, everybody, now I need everyone. Hello, it's me again, going Bitcoin dress. Hi. Everyone to note, I have a Bitcoin dress. Do you want to give a lightning talk about that? Oh, absolutely. So, I need everyone to have a cup of coffee or tea or beverage of choice because we'll be sitting here till lunch and listening to lightning talks and discussing things, okay? So, be prepared for that. And I need your laptop, because I'll be introducing people. So, first, I will. We didn't sort them by order. Yes. First person to give a talk will be... Yeah, I'm just deciding. Tariq. Yeah. Okay, Tariq and blockchain receipts. Stand up, come here and give us five minutes. Well, too bad. Last and first out. I should be able to. Minutes for everyone, sorry. We're going to try to limit the lightning talks to three to four minutes for everyone, unless you really need the time, just because we don't want to use up too much more time. Okay, thank you. I'm Tariq. I'm the founder and CEO of a company called HasCloud. We are based in Sydney, Australia with our development lab in Malaysia. So, I was trying to go to the point. So, what we're doing, we're trying to create sort of like an internet of services. We define the services produced and delivered by collecting and processing data or documents from the service applicant. Okay. So, it is always like either you are taking my IDs and we're taking some data from me to give the service back to me. So, now I'm Tariq. Whatever service I need, I will always be service. So, what we're trying to solve is that if I go to a bank and do a KIC, so the bank does the KIC for me. So, I go to a second bank. That second bank again do a KIC for me. So, but the point is like I am Tariq. So, if we create sort of like a hub where I put all the service like objects, which we call the service data objects or service document objects. And we create the hash of those data and documents and put it into a blockchain. So, then anybody can verify that. So, that is where we are coming from. So, then the customer can, the customer goes to an embassy to apply for a visa. The embassy will ask for like giving you a passport, giving you identifications, giving you educational details, everything. So, again, the customer has to copy those documents and give back to the embassy for them to do the service, which is given when the visa. So, again, so what we are trying to do is that why can't we centralize everything so that the customer can apply for all kinds of service through the same portal. So, that is the portal that we are trying to sort of build. We are, we are going to, basically we are going to have some plans, but the problem comes. So, the problem comes like, now the customers, my customers, my initial customers, they decide to go through me to validate, to put their service, to cryptographically hash their like educational service. Like if I go to university, they give me their service because we hash them and we put it into a blockchain. So, we use a company called Therian and then Therian gives me a receipt and they use a blockchain, Bitcoin's blockchain. But the problem is if I go to another university and that university wants to put their city tickets directly into whatever the blockchain they decide to put. So, I don't know like what my customers, my own customers will, how do they verify if the receipt is given to me or to my customer is different to what we are using. So, what we are trying to do is that if we could standardize the blockchain receipts, wherever it comes from. So, we know that there are a few blockchains now and there will be, there will be hundreds or other blockchains in the future in the next 10, 20 years. So, we will listen very well. But what we are trying to surround, there will be also a little player who will be sort of like a little company called Therian. So, we can go through them. So, the operation vendors can also go through them to put into whatever blockchain that we decide to use. So, that means that there could be two different like standardized farmers of blockchain receipts. So, what we are trying to do is that what can we have in the seed that is standardized across the net. And so that vendors like us could, it will make our lives easier. So, what we are asking is to have a standardized blockchain receipts. And this is one sample received that we use and that is from Therian. So, that's about my lecture. Thank you. Great. Thank you. Can you? Okay. We'll do that at the end. Let's do it. Let's do it now. Okay. Arno and Hyperledger project now. Hello. Good morning everyone. So, I'm Arno Loas from IBM. I'm part of the Open Technology Group. And I'm actually involved in the Derby3C. I'm the main web for IBM at Derby3C. I have a longer history with Derby3C. But I'm also involved in the Hyperledger project. And that's what I want to talk about today. I mean, we've heard references to these projects several times. And I wanted to give you a little bit more insight as to what's going on. The project is actually hosted by the Linux Foundation. I don't have any slides, by the way, in case you haven't noticed. But if you go to hyperledger.org, you will find the website and everything is starting from there. You can find everything. So, the project is started. It was launched officially announced in the fall last year. And things really kicked in at the beginning of the year. This is open to everyone. You can participate for free. And so, there is really no barrier to entry. You can also become a paid member. And a paid member, you get some specific privileges. You have additional benefits such as marketing and reserves, board seats, stuff like that. But so, essentially, I mean, the project kicked off really quickly. It's gained a lot of momentum. We have attracted a lot of people. And as a technician, for me, it's kind of interesting because it's a different world where we have, you know, people from legal, from the finance industry, mixing in with a bunch of techies. And it's kind of interesting from that point of view. But so, we have a lot of companies from financial industry, like JP Morgan, Chase, and what not. But we also have people from the tech industry, like IBM and others. And so, the project has a fairly ambitious goal of creating a framework which is very flexible and pluggable. And it's not a specific network. It's really the idea is to develop a framework that you can take and use and configure to your own needs for your own application. And the big vision is that eventually, we're not going to have one network of blockchain, but you're going to have like thousands of blockchain networks based on your specific needs for your own application. And a lot of them might actually be private blockchains. That's a big difference between other projects that are more like Bitcoin oriented, which are permissionless networks. In the enterprise setting, a lot of the applications can reuse some of the characteristics that make blockchain interesting. But because they know the entities they're working with, they don't have to have the burden of this proof of work which is very expensive and which limits the throughput, the number of transactions you can have per second. And so a big part of the projects is actually to address the need for permissioned network where you actually know the parties you're dealing with. And so the work is taking place at two different levels. There is a high level where there are projects, working groups, working on things like the architecture at a high level, use cases and requirements. There is a group on identity. There are several groups like this. And then there are different projects that are actually working on code. And so there are currently two projects in incubation. One is called Fabric. And it's based on a contribution from IBM and digital asset holding. And then there's another one called Sotuthlek that was contributed by Intel. And so the first one is actually permission network. The second one is permissionless network. And so it's very easy to start participating. And so one more thing I wanted to say is to the Hyperledger project actually submitted a position paper for the workshop because the workshop is about should the derivative seed do anything in standardization if anything, what? And so the vision of the position from the Hyperledger project to the truth, it was not very easy to define because it's already a big organization. And so when you have a lot of people, they have different positions trying to agree on what the position of the whole project is is a bit of a challenge. But essentially there is a general agreement that it's too early for the most part to work on standardization because we're still very much in an exploration phase and we don't want to start freezing things when we want project different efforts that are in their way to actually have the freedom of exploring as much as they want. In general what we're also interested is if there is any standardization effort that takes place it should be really modular and focus on very small aspects that can be combined because again the picture we have is this framework of pluggable components which consensus you use and etc. It should be completely independent. And so again the position is it's kind of too early and if things are done they shouldn't be like wholesome like trying to standardize the whole framework or the whole stack but instead focus on small items. Thank you. Thank you. Okay next. Okay great. So what I want to talk about let's just have three minutes is this thing that's called TMSP but we might change that to be SBAPI and the point is to is that it's splitting the blockchain into two components kind of like what IBM Hyperledger is doing with chain code except this is a bit different. In chain code only the logic resides in the application whereas in TMSP soon to be renamed the storage mechanics is on the application so you can use any patriciatry that you want or not you can do whatever you want. The point is that tenement is just a consensus engine and once the blocks are committed it pushes the transactions to the application using something like CGI. Anyways you can kind of see if you go to github tenement slash TMSP the readme you can see some of the messages so like append tx is a message type that gets pushed to the application after it's been committed and there will be one of these messages for every transaction in the block and when you commit then the application returns like a merkle root hash which gets put back into the blockchain on the tenement side now you can do merkle proofs and so on. So there's now also GRPC support for this so if you want to just write your application and support GRPC that's also possible or you can use the network socket version which is way faster it allows you to push transactions asynchronously so if you want to talk more about this join our Slack go to tenement.com you'll find our Slack channel we're always adding more things to support so if you need anything the benefit of this the benefit is that you get to develop your application consensus agnostically so that you can plug in any kind of middleware that you want right now it's only tenement but presumably other people can develop their own middleware thank you okay great thank you so much for being here next will be a talk on lightning networks Sadius Hi let me get this display hmm it's two it's a different resolution let's see is this this visible anyway okay so I'm going to talk about scalability and blockchain blockchain scalability using payment channel networks I'm working on something called the lightning network it's currently being built in Bitcoin but it can support other things and so one of the fundamental problems with blockchains that I think people recognize is scalability right how can you work with millions of users how can you have rapid interchange transactions things like that and the problem is that you know the blockchain fundamentally is shared you can call it a distributed ledger but it's really a duplicated ledger and everyone has the same copy of everything which is pretty inefficient it's sort of like although there's really good internet here so it's not a good example but you know when you're in a conference and everyone's using the same Wi-Fi AP it's usually kind of slow and you can increase the speed of the Wi-Fi AP by going to you know 8211 and AC whatever but really you want a segmented network you want to have everyone plugged into their own switch and that's how to really scale networks so it's a trade-off right global consensus is important but inefficient so how do you do this how do you segment the network without losing these properties of the blockchain and the way to do it is with payment channels and there's sort of you can make networks out of payment channels so this hopefully it's not quite a cryptographic primitive yet but hopefully it will be so widely used that everyone will consider it like an obvious primitive in a few months or maybe years so the way it works is you send in the case of Bitcoin you send let's say a Bitcoin to a shared multi-sig address and then you can exchange signatures which lay claim to that the coins in that address and this happens offline or you know off the blockchain so we can keep sending these messages back and forth and that alone is pretty complicated and if I can't you know I don't have time to go into how it all works but it's pretty cool and then that allows you to establish channels where I send one output to the blockchain and that's a channel and we can move money back and forth between two parties that's kind of useful but for payments you can't you know just have one person you're always paying because most payments are not metered if you're connecting to websites it's the same website every time so how do you extend these channels to other cases and so this is the sort of fundamental way the Lightning Network works you can kind of see it shoot let's see good enough so the way it works cryptographically is Alice has a channel with Bob who has a channel with Carol who has a channel with Dave Alice wants to send a payment to Dave because that incurs the blockchain cost of having an actual output on the blockchain so Alice and Dave communicate over the internet and okay so Dave creates a random number R it's a non-space hash is it so now you have hash H gives the hash to Alice Alice then says to Bob I will pay you contingent on knowledge so Bob if you know R you get a bitcoin and Bob does not know R so Bob says hey Carol I'll give you a bitcoin if you know R so Carol says to Dave hey Dave I'll give you a bitcoin if you know R Dave does know R and then the R backprop gates it all works and it's really cool and this is a network infrastructure I think a lot of blockchains will use and hopefully if you want to learn more about it ask me questions after okay thanks that was an amazing wrap up seriously okay even I know that you just arrived but please come up and talk about interledger thank you so much and also introduce yourself because we're just getting to your sense I'm Evan Schwartz I work on interledger and I literally just got off the plane so sorry for so interledger is thank you so as I said Evan Schwartz I work on interledger which is a protocol for cross blockchain or cross ledger interoperability so everybody's here because in some way or another we believe that distributed ledgers are better than these kind of siloed or hub and spoke networks so everybody's got their own flavor of blockchain that they prefer what we don't want to do is recreate the silos that exist today where everybody has their own blockchain for their own use case and there's no interoperability between them so what interledger is is a protocol for transferring assets across different ledgers this is specifically for transferring assets but this could be fungible assets like currency or non fungible assets like names deals etc so basically interledger is inspired by the design of the internet because what the internet fundamentally is about is connecting different networks together it was not about getting everyone on one single giant network it was about connecting completely different networks using a very simple protocol so the internet is based off the fundamental building block of the internet is addressing it just has this simple address format and then you have gateways which route between different networks interledger works basically the same way where you have an address and an amount this is the very fundamental piece of interledger so you have a way to address some account on a distant ledger and then it's basically like putting an address on a little envelope so you're on one on one blockchain or ledger you address your little envelope with an amount and an address there's these connectors which are basically like internet gateways that route money or assets between different ledgers and then it gets to the recipient and what you can create with that is you can create very long chains so that anybody can pay absolutely anybody no matter what ledger you're on and the idea is that you could be on a bitcoin and I could be on something completely different and we could still transact just fine if you're interested in learning more or how all of that actually works under the hood come talk to me or check it out at interledger.org thank you sorry really quick question were those mime types was that a mime type that was me in an airport at 11pm thank you so of course after I mean all of these lightning talks are to start the discussion and we'll have as yesterday discussion tables afterwards I'm sorry if I'm pronouncing your name badly and while he's getting set up so we're going to have two more lightning talks then we're going to take a brief break and then we're going to start back with lightning talks again okay so I'll just talk about the security issues and how we trust that blockchain technology so I'm going to change your muscle and be seconded to our clients so this is a so here from that conversation start up yesterday so the problem is how can we trust the output from the blockchain technology so this is a problem and so we had several security issues in blockchain for example so we had a huge data problem two weeks ago so this is caused by the vulnerability this is an implementation issue and we also have other issues in the protocol level or implementation level or operation level in the blockchain technology for example that the process we do not have concrete verification of the protocol specification and we do not have sufficient key management mechanism including life cycle revocation of the key so we should check that implementation of the code and so we should have this fine-grained operation on this vulnerability handling so this is the security layers this is not specific to blockchain this is the general thing for crypto based system we should have security evaluation for cryptography and we should verify the correctness of protocols we should check that correctness of implementation we should have the fine-grained rule of operation we already have several international standards on each layer but so my understanding that so we do not have such kind of fine-grained security layers in Bitcoin blockchain and we need them for blockchain and more research are needed here at this time so to do such kind of research and other kind research to mature the blockchain technology enough we, I and Pinda Won already started a project named bsafe.network this is so NSF net for blockchain technology this is a neutral, stable and sustainable research test network for blockchain technology by international universities each university researchers become a blockchain node here and so you must research and conduct research on blockchain and its application so the topic of the research is not limited to the security and all aspects of the blockchain technology it can be sauteated over this network this is a neutral platform and trust hand card of the blockchain network and so we can have more nodes with neutrality and this is a test bed for academic research so we already started this project and this year is a bootstrapping phase we already started attacking the Bitcoin and segregate witness protocol and we will add some more protocol like Ethereum, Hyperregion and other this year and next year we will make sure the scope of research wider is funding and from the W3C viewpoints so we should have many sort of standardization items including on-projects, analysis framework, use technology operational and environmental policy interface, message format protocol relationship with existing standard in W3C we should have we should discuss about organization of keeping security including cooperation with other standardization organization and group of experts and communication with academia, thank you okay great thank you so much and next we'll have a talk about expectations about the web crypto API from Shiguro Gusan thank you for introduction and my name is Shigeru Fujimura from I'm a research engineer at NTT cooperation from Japan my research topics is applications that takes advantage of blockchain especially blockchain based content distribution our main target is video contents and this is a panel of our exhibition of NTT laboratories open house at February in this year at that exhibition we show the prototype demo system for contents distribution system and this system has two functions one is it's like yesterday's discussion about provenance one is contents registration method to blockchain it's like proof of ownership and proof of data authenticity and second function is video play control it's like DRM and we use in that function decrypting encrypted media using media source extensions and cryptography API these are part of broad sense HTML5 in broad sense today we show this prototype demo system at lunchtime and after events at the death side of the desk and I would be we would be happy if you could see our demo and give us comments or opinions and anyway this is my this is my point through the development of our demo system we have many impressions that is regarding webcrypt API its implementation depends on browsers for example some browsers need HTTPS connection it means for developing phase inter-developing phase we have to get SSL certificate it makes developing more hard I think, more difficult I think and second second example is implemented crypt algorithms depend on browsers not all the crypt algorithms are implemented in some browsers that means in conclusion of course I know of course I know webcrypt API is in the process of WCC recommendation and not yet WCC webcrypt API is WCC recommendation of course I know but the engineers would be happy if webcrypt API become WCC recommendation and all implementation in browsers are same that is my point thank you thank you we are going to take about a 10 minute break and I think there should be some break materials there and just in case it wasn't clear there is going to be a demo this afternoon around 3.30 over there and actually would you guys give another hand to NTT for making all of this possible and also to media lab our other major sponsor Foxstream personified by Sandy Pintland will reconvene in 10 minutes or less if you have the will can get GMSP GMSP we might rename it there are some messages the most important ones are 10 minutes like a minute but the point of this is like this so it's a quarter Yeah, it's 10 and 4, so it's doing the consensus, and then you plug in the get application in this game. So the get is now, it doesn't have to talk to the outside area man, it only talks to the foreign man. But it's doing the computation of the state. Does get have the PM and the protocol? No, it doesn't. So that's what this project is trying to do. Yeah, so it's go. Do you know the room? Do you know where it's going? Yeah, so it imports get, and then it plugs in TMSP. So it imports like TMSP server, which gives you most of the tools you need. But it also imports really quickly. Yeah, so server, which is imported from TMSP, makes it easy to create a TMSP application. And then you say, listen on the socket, and then you they created this application. And then 10 of it can talk to this, and it becomes a thing. But this is not complete. Ever since Ethan made this on February, get changed. So this is broken, doesn't work. In order to make this work again, it'll take like a week. But we can help you, because we're going to do it anyway. What's your email? Oh, is it like that? What's your name? What's my name? What's my name is? Yeah. And is this right? What's your last name? Japanese name is last name. All right. Yes, his name is Karim. What's your update? Okay. Also, if you have any questions, let me know. I don't know. Thank you very much. Sure. Oh, thanks. Thank you. Hey, how's it going? Where are you at? Providing. Oh, you're giving me Korean? I was just there last week. Yeah, I was just walking around in Korea, and I saw many questions. Do you have any insight on the pandemic? Sure. So, is it supposed to work? Yeah, it's not working now, but we want to make it work. It's probably the easiest way to plug in BFT consensus into anything. So it provides some kind of consensus from the community that you have some type of plan or plan. Yeah, so there's two communication lines here. The first light API, we call it TMSP right now. But if it connects to the state machine, the state machine doesn't have to be exposed to the internet. The other interface is through the tournament API. There's WebSocket APIs and GRPC soon. So it's supposed to provide a specific protocol and a lightning fast screen, right? Yeah, so what kind of optimization or kind of protocol are you using? Oh, yeah. We're using... So Pax was in the RAPT, or like Valtower? Yeah. Yeah, so we develop our own. It's very similar to PPFT, but arguably it's a bit simpler. And we've been working on it for two years or so, but we finalized it last year. It's a bit tricky. PPFT's based on... It's not... It's simpler than PPFT. But I think it's simpler than PPFT, because in a way, PPFT is better than... Oh, yeah, yeah, exactly. So the problem with this is that we don't have a white paper yet, except just a wiki, so... But once we've put it in a white paper form, we believe that it'll, over time, gain more adoption than PPFT. PPFT is not even like... It's not even optimized for the blockchain, so the internet and this algorithm is really designed to be a blockchain. But it's got the same kind of permanence as PPFT. And here's the algorithm. There's also a white paper. We're going to launch a public blockchain nuclear yet. In this white paper, it also goes a little more into things like... Oh, well, this is like proof of stake stuff, so maybe you don't care. So TenderMint is the core and Gene is very blockchain-based. Yes, absolutely. TenderMint, it can be proven to be blockchain-based. Yeah, exactly. So it could be like B3, implementations can be plugged into... Yeah, yeah, right. There's even... Actually, that is fair. There's even... Are you going to develop your own blockchain application? Actually, we are based on a Bitcoin. Okay, everybody, sorry. End of break. Start sitting down. Nope, nope, nope, nope. Okay, Monty and blockchain community group. Come up and start talking. I see two people in the left corner chatting. Stop chatting. You, there. We're doing really great on time, guys, so I'm really proud of everyone. And we will be ready for lunch in time, I hope. So kudos. Hello, good morning. Okay, hello. My name is Monty Lee, and I'm from Paygate, Korea, and also working at the blockchain community group. So let me introduce the community group. So actually, blockchain community group is not official. W3 is a working group. There is a name like a community group. So we had a mission to generate message format standards of blockchain based on ISO 222 and to generate guidelines for usage of storage, including torrent, public, private, side chains, and CDN. And also we are trying to study and evaluate new technologies related to the blockchain. We have started March, and first workshop at the 25th of March at Seoul, Korea. And currently we have 53 participants, including Paygate, Brocco, Gonggu University, I3LG, Wart Dizoni, and Blockstream. Blockstream, I don't know. He will try to join at the Concord. And the chair is Nick Lee. So some activities we had is that we are learning the website and has a mailing list and telecom every Thursday, 11 p.m. KST. There is actually 7 a.m. EST. And also we are learning the issue tracker. And we found many issues, reports or deliverers. So trying to define message format and data flow and the summarizing ISO 222 and the storage guidelines. We have talked about the public, private, side chains and torrent and CDN. And also talked about the identity, authentication, and authorization. And also networks or use cases. And now we have selected the two proposals. One is blockchain authenticators and the centrality of a blockchain. So you present? Yep. So one of the major problems with blockchain applications is that there's no existing robust way to manage a case for end users. And we took from the example of FIDO and its UAF implementation. Oh, okay. Yeah. And you could extend existing implementations and protocols to actually use it for blockchain. So existing blockchain applications and even end user apps can take advantage of FIDO authenticators which are already preloaded on a bunch of devices and use it for a blockchain instead. And we are already working with several FIDO providers to experiment with this idea and provide a robust implementation. And the third chain is centrality of a blockchain. So that is trying to use blockchain transactions as a relationship line between the blockchain addresses. So we are able to measure the centrality and with another three important elements, size of amount and level of verification and measure the centrality of address. So that can be used for the score and the credits of address. So there's missing and remaining. So we found the mission is not matched to some participants. So please contribute CG. Thank you. Actually, hey guys. So we also have a conversation. I want to also establish what a community group is in case you don't know what a W3C community group is. It's an open group that anyone can join and you don't have to be a member of W3C to do that. And I talked with Mountie and him about maybe as part of the overall, like as part of this new interest in blockchain at W3C, maybe we can start expanding the blockchain community group. And so if you're interested in getting involved, then come talk to us and we'll think about setting up little topic areas within that community group and so it just might be a good way for us to carry the conversation forward. So next will be Guri and IOT. Guri. And also for everyone who gave a lightning talk and will be giving one, I would ask you to be ready to have like five words summary of what you want to talk about. At your topic table. Okay. Thank you. All right. We've been doing some work on proving the blockchain capability with an IOT use case. Many of you might have seen other presenters from my team, from our team might have seen some of my other work at other events. So basically I'm going to go quickly through four pieces of flow over here. One is what is the problem that we went after? Second, uniqueness. Certain uniqueness is about IOT, which otherwise could easily be forgotten in a non IOT world. Third is the solution and the proof. And fourth is a little summary of some of the future considerations and open problems that we didn't complete so far. So as far as the problem and the challenge is concerned, everybody's seen a picture like this of a typical hierarchical centralized IOT solution, tiered model. And in most cases, it's repurposed. It's repurposed from existing technologies. So in a sense, I think that's where the state of the art and the state of the possible, state of the art is right now. I shouldn't say state of the possible. The state of the possible is beyond that and you'll see that glimpse in the solution portion of it. It's device centric. It's not user centric, right? So from those of you who are from the design thinking, user experience world, there's a very device centric. I need an app. I need a control point for every device. And then if I've got 20 devices in my home, I need 20 apps potentially. It's highly centralized. And I caveat that by saying that's the only model, right? I'm not saying that centralized models don't have a place in the world, but you'll see a slide later where the notion is considered of a portfolio where there are certain places where they're centralized models, certain places where they're decentralized models and hybrid models. So when we look at this, this kind of a model, it's okay you can repurpose technologies to new solutions up to a certain point, but then they become unsustainable from a scale and performance standpoint technically, but also unsustainable from a monetization, business monetization aspect, including privacy of data and all the things that we know have been a little invasive towards privacy. So if I step into the next portion, which is what are the uniquenesses around IoT, I think it's important to look at that. So we are looking now not at like millions of devices. This is a scale that the planet has never considered before. So we're talking about tens of billions of devices. We're talking potentially of hundreds of billions of devices. So computing has never been considered at the edges at such scale ever in our history. So the other uniqueness is about longevity. So if you think about longevity, we typically don't think about longevity we have to think about in the context of IoT. So if there is a solar roof, in a house that could have 50 years, similarly for appliances typically have 10 years, all the life cycle implications and software implications around that. These devices are not always on. There are temporal and spatial movements and shifts that happen. By definition in an IoT world, there's OEM heterogeneity and you have to look at seamlessness. So what is the solution? What is the proof point? What is the proof that we've learned from some of the work that we've done? It's got to be user-centric. It's got to be sensory. Increasingly, it's got to be cognitive. Scale, of course, decentralized. Economics have to be sustainable. Monetization model has to be there. I won't dwell on this slide too much, but this is the portfolio model. And what we are looking at is for decentralized solutions of IoT, we are looking at device longevity to be towards the high end and the device value towards the low and medium. So think about your devices in the home as a most common example. And if you land a blockchain footprint on these nodes, and of course, we've got to worry about the footprint of the size of the blockchain, you basically begin to link these two worlds. And you have a network of devices which is on a distributed ledger. But this is a proof point on a washer activity, automatically generating a bid for technician services after going through warranty. But you're now looking at a blockchain, you're looking at assets being liquefied, they become shareable, different level of responsibilities, they're autonomous, so on and so forth. Let me just jump to summarizing the open considerations. We've got to worry about what is small, what is medium, what is large. And I'll leave a couple of considerations over here about the classification of data, spatial and temporal considerations and so forth. Thank you. Thank you. This, I think, would be a very interesting topic table and a lot of it will be covered. Okay, so now let's have James talking about Common Accord. And Daza, you're going to be up next. Okay, so you have three minutes to get prepared. We're good. So Common Accord is essentially how do you bring lawyers into the open source collaboration system. This slide, the little insert there is from Bart who pointed out the problems of the non-contract nature of smart contracts from a prior conference that we did here. So how would you make them into actual contracts and more than contracts, complex contracts and the permits and actually everything that we now do through Word and other blob-based data formats. This is done with Thomas Harjano of Connection Science. The notion is that you can have objects and then you can essentially make connections. You can use blockchains and authorization control in order to create a secure, dry data system. The goal, my goal is to create centers for decentralized law. They are essentially repos on GitHub that lawyers contribute to. Some of them will be of global impact. That is some of the kinds of organization of formats of stuff has global impacts and many problems are understood to be global. But anybody can create their own. Nations will want their own. The EU will want its own and so forth. So concretely, we wrote a paper here for the conference which you can see. The first part is about Common Accord. The second part is an intermediate layer of smart contract description language. There is a discussion group at Canchara. Thomas and I are the organizers of that discussion group. Pragmatically, what we do is we notice that with key values you can do everything that lawyers do. So this is the form why this is the whole ecosystem in it. Why Combinator wants this stuff cleared up and made codified one minute. And you have a notion of identities and you can point to law. And that gives you your whole text. So with that, we haven't created a new blob. Everything, this is a graph. Stuff is linked. It's up on GitHub. And students at French University have three young students have forked this thing and started their own repo of stuff in a French context. So what I'm looking for is people who want to connect with this ecosystem. How do we bring lawyers into open source? How do we bring their full knowledge? Instead of killing the legal system, why don't we make it efficient? Thank you. Thank you so much. Daza. So Daza will talk about URL for every block. And then Gioff will come up and talk a bit about blockchain patterns. I wish I could use the blockchain. But when I point my browser at it, I don't see anything. That's a problem, because I can't see anything when I point my browser at it. What would be great is if there was a URL that would allow me to find an address on a blockchain, find a blockchain and find an address in a blockchain and would, thank you, would render, actually, how about a hand for this guy? He's made everything happen. No idea how hard the sound is for the simulcast and everything and switching all these computers. Thank you. Anyhow, if I could just go and find a block because someone emailed me an effective URL, I could use it. What's more is, fundamentally, I've felt for a long time, if I am, I think therefore I am, I can browse it, therefore it exists. When an article or a paper or a poster increasingly even like a policy is on a website and it goes to archive.org and I can sort of find it again and I can reference it and cite it with a PDF saying, last downloaded in the state, that's real to me. When people email me stuff and things even happen in so-called official legal books and other things that feels out of channel, it feels out of sync, it does not feel particularly reliable, it feels, I'm not going to say broken, but let us just say anachronistic and it's not usable and it's not addressable, it's not inter-creatable. It cannot be part of the world that we're building into. So there's some connective tissue missing. I think it's uniform electronic, uniform resource locator. Just two things in the law. I foreshadowed one yesterday that would be possible if only we could find a protocol or some standard that would enable a URL to resolve to a block is statutes and regs. So uniform electronic legal materials act already has been proposed to states, some states have adopted it, others can and it requires like with three criteria that electronic materials will be official. So it has to be basically publicly verifiable like encrypted hash from the publisher and broadly accessible. A blockchain is over sufficient to allow this to happen. Another thing is we can have legal notices. So car recall, what's the date of the election? Just basic stuff. That could zero out a lot of cost when you've got your consumer notices and when you want to know someone's suing you maybe or if you've got lost property, we can't address anything. This is absurd, one minute. I only got a little bit of the way through the slides but what this one was going to say is well let's just say the HML. So ultimately we need to have a way that with like elegantly we can have machine readable, human readable and lawyer readable resources. Your all to a per block absolutely can do that and you can now reference like big fat Mongo legal documents. You can certainly reference little human readable, almost creative commons things and it's all about machine readability not just for the provenance. It provides an opportunity to begin to integrate BLTs, not just delicious lunch sandwiches but also business legal technical. I think the fundamental three layers that have to be aligned for true interoperability. Interoperability is not a technical alone. It's business interoperability legal and technical and address can get us there. Can we please have a URL for every block? Thank you so much Jeff. And next will be Christopher and smart contracts. So Christopher, smart signatures sorry. No he's next. Hi I'm Jeff thanks. A patent is the legal right to prevent you from doing something. It doesn't matter if you independently invented it if they have a government granted monopoly on it. They can legally prevent you from doing it and collect damages for the benefit that you gained from doing it. U.S. Patent 9298806 system and method for analyzing transactions in distributed ledger. U.S. Patent 9258307 decentralized electronic transfer system. These are already issued patents to have more than 50 patents that explicitly mentioned Bitcoin or blockchain. I didn't search on distributed ledger since that includes a lot of other things. There are at least 585 pending U.S. applications including Reuters just reported last week 50 patent applications filed by Craig Wright the guy who recently claimed to be Satoshi. So there is a patent thicket coming that this community will run into soon. Now the W3C has a patent policy people entities that participate in standards groups have to promise to give their intellectual property in a royalty free fashion but that doesn't help if there are participants who aren't members of the W3C or members of that working group. So someone is going to need to do something if you recall about 5 years ago a company called Lodesys claimed to have patents on in-app upgrades and in-app payments and could have sued Apple but didn't and said sued all the individual makers of apps in the app store which are small startups they didn't have the money to litigate. You may not actually be doing the invention you may think the invention is invalid because of prior art but it will cost you literally millions of dollars to settle that in actual litigation. So you know I'm not going to claim that the coming patent thicket is going to stop blockchains or stop Bitcoin but I think a lot of companies could probably go out of business or at least lose years of time to market unless the distributed community I know it's hard for distributed communities sometimes to coordinate unless we can also figure out how to coordinate to answer the intellectual property concerns that are coming I think a lot of people are going to lose some money and a lot of people who maybe you don't want to are going to make a lot of money. Okay so now Christopher and smart signatures and then next up is Peter Todd with deterministic expressions. Okay so signatures are 50 plus year old technology I'm talking about the cryptography of it the digital signature okay it is a hash of an object that has been encrypted by private key and is verified with the public key against the hash of the object all of our systems use this in a variety of complex ways that higher levels to either do identity or to sign a block or to do a variety of different types of things the idea behind smarter signatures is can we allow for more functionality multi signatures which is what bitcoin and some other technologies have begun to allow us to do as an example of this but we'd like to address much more complex use cases we also have to be very careful about it this is very fundamental technology we don't want to run into situations like the Dow etc that you know break things we need to do some experimenting some of the possible uses there's and multi factors things like and of and multi signatures which do like I said exist in bitcoin and of and multi signatures but really some other possibilities are things like or multi factors for instance for legacy purposes we could have an easy dsa multi signature or the RSA multi signature or to really future proof things or a Sphinx hash signature which is quantum resistance so we could literally say you choose whatever signature you want we're giving you all three verify the one that works best for you this allows for a lot of different kinds of varied content and different kinds of things that we can do cryptographically some of the other things that we can do is delegation we can do time limited delegation we can say the signature is valid only from during this period but actually build it into the signature itself instead of being a policy above the signature different kinds of use limitations you can do things like say this signature is only good if the transaction you know does not exceed a million dollars or other kinds of content limitations where we can say this is this delegation is only good for signing a sub project not the prime project so it can be like the development release but not the public release there's a lot of power when we can do internal depth where we can have a variety of uses but there's also this sense of external depth allows us to pass proofs and this is something I think is a very powerful way of thinking about a lot of the future of blockchain is how does one system one layer pass a proof to another layer that something has been accomplished from a transactional point of view often times we actually do too much computation we just need to be passing a proof what are the requirements for smart signatures they need to be composable that means their individual elements those individual elements need to be inspectable which in the sense of that human needs to be able to understand what's going on but as importantly is that they need to be provable there are new computational science approaches to doing provable components that we can basically go oh we really are certain about the security of the code that's in that we have some run time requirements we want the smart signatures to be deterministic we want them to be bounded we want them to be efficient a variety of languages and approaches we can do this their functional language is like fourth lambda which is kind of in the list family but there are other approaches I would love to have a poll request to my paper on this from ripple on crypto conditions obviously bitcoin a lot of people you are familiar with dex we're going to see as a demo in just a minute or a quick talk in just a minute we have a lot of open questions how do you define context and or how do you deal with revocation hardware devices and then how do we deal with oracles this is only an ice breaker we need to evolve it this came out of the last two rebooting web of trust the next one is September 28th 29th and 30th in San Francisco web of trust.info is the main site github web of trust info actually has the the full paper and references to other things okay so now peter will dive slightly deeper into the deterministic expressions and next will be waytec sci on blockchain ip write protection howdy says christ just mentioned I've been working on something I'm calling dex which is a deterministic expressions language it kind of looks a little like the lambda calculus but really the main thing we're really trying to do here is just create a way of specifying expressions that would return true if signature is valid and you know we think about it something like this you know which is really just check signature against pub key and so on for a message ultimately that's what really would be baked into your software anyway so really what we're trying to do here is move one level of abstraction to let you specify what kind of conditions you might need for your particular use case which may be as simple as just a standard pub key but you also might want to do a multisig where you have and Alice signs off on something you know and Bob signs off on something and what's interesting is that's very simple but even something like that is opens up a lot of possibilities and we've seen this in bitcoin with its multisig you can also see things like or conditions so you might have say the idea of a release pub key which can go sign any software release and then maybe a dev pub key which is only allowed to sign development builds and you can build this in as well what's the definition of a valid software release well it's either signed by the release pub key or signed by the dev pub key but only if your build is marked debug simple but you know nice nice improvement and what's interesting with this is rather than hashing and committing to these kind of conditions as a hash of your entire script if you start doing things with trees you can start getting a bit clever so I'd say well rather than you know serializing this whole thing I'll serialize parts of the tree and then what I'm trying to go convince you hang on a second this release build is valid I don't actually need to give you all the other conditions all you need to know is that the thing I've revealed to you as part of the signature process had the same hash all this funny stuff about dev pub keys you don't need to know you'll just see oh yeah there's some stuff behind that digest and it's pruned away you didn't need to evaluate it but you know the ore one branch of the ore checks out and we're all good and then the next kind of use case you then get a starting delegation which well I could either have master pub key I mean if you're in open pgp you know that you have a master pub key associated with your pgp key but I might want to add more conditions to it later so why don't I go check the signature on a binding signature and then evaluate this new sub expression you know once you add this kind of primitive well and start off with one key sign new code as needed and keep expanding the set of capabilities maybe that's my software release in fact and the sub expression I sign is when I finally give the developers the ability to go and sign a release you know sign a debug build oh yeah that's the last slide very very early stuff but ultimately we're just trying to go and build some basic primitives and of course the flip side of this too is once you start having predicates well you might even go and define entire protocols in this is if this is valid stay in the protocol that returns true but I can't fit then three minutes so thank you okay so we'll be doing a table on topic on this during once the breakouts yeah we will be doing breakout topic tables on every topic okay so now blockchain IP right protection and finally the last sorry we will have two more topics we will have Chris talking about blockchain web test bed next and then Manu so be ready oh he's not this is not the right one okay sorry for the today I talk about the blockchain IP web protections and this is about a project we do for the CCTV which stands for China Central Television and it's supposed to be a real-time tracking system for microphone usage supposed to be a high throughput and low delay 6 million people concurrent users at the same time and privacy and compliance are important you have to be dependable, controllable and elastic and it also has the automated distribution resolution in case of legal distribution and CCTV plan to deploy 200 subsistence in 5 years and estimate that you will receive 140 million USD per year in 4 years so that's the project scope and this is the blockchain design on the left upper corner is the European Banking Association come out with a proposal and we look at it we think it needs to be improved so we divide the blockchain into ABC stand for account blockchain and TBC stand for trading blockchain each of the blockchain will handle only one kind of functionality to make a system modular and also since the the law will be increasing so we want to make the blockchain like cloud computing become elastic can grow and shrink and we are seeking for the multiple project to collaborate on technical business and cultural matters and CCTV has come with 23 million dollars for each collaboration project that's found in CCTV itself and for example in particular countries if any partner like to partner with CCTV and CCTV will put out 23 million USD for it and then it will be an international advisory board and basically it will do any IPR protection for foreign firms and it won't be displayed in a foreign country or in China with the blockchain protections and people ask me whether there will be a project in China on blockchains and found my estimation about 2 billion dollars these are all in USD will be invested in blockchain and CCTV itself has over 700 million dollars USD planned to be invested in the next five years and in the variety of domain including energy IP protection, education and banking and the Chinese journal FCS special issue on it in October 26 Hangzhou there is a CCTV event and with blockchain workshop if any one of you are interested you can come and next month we have W3C meetings at Beihang universities and there will be a talk on blockchain ok thank you thank you ok so now the Chris and blockchain web and while he is getting set up how do I get that money great this came when we had four beers last night and we were at I think Meat Hall or something I think it's Meat F with a D I always thought it was like Meat or something so it came from a conversation I had with Doug and basically said we were talking a lot about blockchain but what about the web right so one way to do a test bet around the blockchain and the web is to essentially build browser plugins or use cloud wallet, use existing surface area of the web browser and the problem with that is that you don't get the full power of full clients if you want to put the actual blockchain and actually have storage on them so we basically said why don't we do this, why don't we start with the web platform but give full capability different blockchain provider, cloud wallet light wallet and kind of have a single test bet that we kind of try all of these ideas out and one of the ideas I have is to say why don't we use Chromium as a beginning and that's a lot of work right so you have seen other wallet provider missed project from Ethereum using kind of Chromium as a starting point but it turns out there's a really easy way to modularize and try different things out GitHub has a project that Microsoft is using for Visual Studio Code and also Slack is using for the desktop app whether you think it's fast enough for your daily work or not it's called Electron so essentially it's Chromium wrapped around Node.js so that means that if you have a full client you can kind of get C code onto their rapid round node and then provide a JavaScript API for a Slack like application you can also put a light client in it that doesn't do any validating and expose the same API you can call a cloud API so that you can get on board with a cloud wallet whether it's a trusted version or untrusted version or you can call a desktop API if you want to kind of communicate with the operating system so if we can kind of agree that this general idea is a good idea then we can experiment with the JavaScript API that is talking to the open web platform so HTML, CSS, WebRTC written in web development language whether you want to be completely vanilla you can use whatever the W3C gives you or you want to use a framework like React the Ember doesn't really matter we figure out how to kind of get those buttons and all the different organizations but I think it's worthwhile for us to see if we can kind of come together and say all the experiments we're making has to touch the end user they have to know what you're trying to do so maybe we come together and say let's create a blockchain web test sped application let's put them in either the W3C or a sponsored organization and then anybody who has an idea let's make it into the MPM module and wrap either native code or light wrapper around your server side API as Tenement is doing and so that's kind of what we're thinking we can talk more about this as a table, I'll probably lead a table if you're interested in this approach let's see we can start something here so we can demonstrate the value to the world in a visceral way thank you so much that's super interesting okay Manu you're the last one got it and after Manu finishes his talk I will ask every person who wants to lead a table I'm not sure if every person who gave a lightning talk actually wants to lead a table to come up to the stage here and give a summary in five words or less of what they want to lead the discussion on okay I think what we should do is you guys will all go on break we'll have a conversation about all that and then we'll come back and do the yeah so you guys can talk amongst yourselves while we're sorting out what the tables are going to be yeah sorry to be clear the presenters should still come up to us but then all of us will decide what the tables are going to be and then then we'll reconvene and split up into tables alright sorry I'm going to go ahead and get started hi so the lightning talk is effectively on blockchains specifically the bits that we think we can standardize my name is Manu Swarney I'm the CEO of a company called Digital Bizarre we focus on next generation financial services technologies and identity technologies try full screen yes please so what we've been doing over the last year is taking a look at blockchain technologies so specifically we've looked at bitcoin stellar ipfs hashgraph okay we've basically been taking a look at blockchain technologies and trying to see if there are any kind of commonalities between them so the idea here is take the standard security and privacy principles that we take for granted like confidentiality, non-repudiation and see if each blockchain technology can achieve that by itself or if it needs some help if it needs some other thing to do that that's fine we can just keep going so let me try and apologies for the complex slide on the right but this is kind of a breakdown of the type of analysis that we've been doing so this has to do with standard security principles how does bitcoin ethereum, stellar, ipfs, blockstack, hashgraph how do they do when you talk about things like data integrity or pseudonymity things of that nature and one of the things that analysis like this leads to is it helps you kind of figure out what the general bits that are common between all of these technologies are so one example of this is this realization that and I'm sure just about everyone in this room has come to the same realization that a blockchain can be modeled as effectively a state machine plus events it's really fundamentally a fairly simple thing you start out in one state you apply an event like a storage event or a transaction and your state machine goes into a second event so this is an example of talking about blockchains in more general ways and then seeing if we can take this general mechanism and create a standard or set of standards around them so we've identified a number of components that are common to just about every decentralized blockchain-ish technology and again this is a conversation that we would like to have with the folks in this room it's just a starting point but we'd like to have a conversation about is there a basic data model that's shareable across a good chunk of these blockchains just about every blockchain has a consensus algorithm of some point so whether it's proof of work or the stellar consensus protocol or hashgraph gossiping there's this concept of a consensus algorithm that could be standardized in some way at W3C every blockchain stores data in a very specific way some of them use Merkle trees others use Merkle Patricia trees others use standard link lists every blockchain has a set of ways that it signs its data so we've got signature formats already, Jose, link data signatures hierarchical deterministic keys are something that's kind of interesting to try and standardize the smarter signatures stuff is really interesting that's a standardization target proof of publication so these are all kind of interesting building blocks of blockchains and potential standardization targets clearly we're at the W3C I think it would be good for us to talk about what the protocol is to access these things over the web is that something that could be standardized so there's this proposal that we have called Flex Ledger it's very hand-wavy but it's an attempt to try and express each one of these standardizable blocks and components in a way that is designed to go through like the W3C or the ITF standardization process so the breakout session that I'd like to have a discussion with folks in this room about has to do with what are the component pieces that we think we can standardize at W3C let's get that laundry list started thanks so this will also be part of the topics that we're talking about this afternoon so this breakout could be a good lead-in to what we're going to be talking about this afternoon and we actually have one it was my fault I omitted somebody from the list we have Yuta Steinar from talking about building infrastructure for the future decentralized web and then we're going to take the break and we might have one minute giving a last minute talk there he is so two more talks I'm sorry IPFS okay so my name is Yuta this is Tomek we both work for a company called Escor that's like rooted in the Ethereum ecosystem so to speak so Gavin who's one of the co-founders wrote the first working implementation of Ethereum and the formal specification I myself ran the security audit prior to launch so but now last fall we started a company called Escor and people like Tomek as part of the team what I wanted to do is share with you kind of the vision that we have for the future web and how blockchains and other decentralized technologies play a role in that vision but then also show you a bit what we've done to make this vision a reality so that's what Tomek has been working on so what we do at Escor is building infrastructure for the future decentralized web that's what we usually do unless we get sidetracked by the DAO so the last weeks we're a bit more about thinking about the soft and hard fog which we hopefully soon get fixed I mean but now I think we should add a few more characters like a hard fog that maybe eats the DAO or something like that and a few more fires of the whitehead started by the whitehead attackers anyway so but it also showed that kind of decentralized is maybe not the most important thing but we should rather think about like that we're building like a peer to peer secure serverless web but I mean I think it showed also that why it's so hard to communicate to people why decentralized is such an important notion because it might I mean there's no intrinsic value in being decentralized right I mean there's no intrinsic value in being utilized and secure by people but yeah oh sorry okay I didn't realize that okay so then let me jump a bit so this is kind of a bit of how we see the architecture so blockchain is just one part of it complemented by decentralized encrypted information publication systems and whisper but also the UI part and this is where W3C I guess it comes in secure transaction signing technologies and identity management are things we've been working on and Tomek is going to demo that so if you want to download it it's just basically two things you go to our website install our parity client and also install the chromium browser so what we build right now is you download the note you are running the note on your computer and on Ethereum you have your backend but you build your frontend application on your computer yeah it's so this is what you see maybe you don't see the URL right there but it's localhost.atat and of course if we run many applications then there is a problem of separating local storage or other things so we solve it right now by using proxy pack files and then let's go to the wallets and let's go to the transaction already so over there so when you send the transaction this is the moment when you have to use your private key the private keys are stored on your note but they are password protected so when we send the app can ask you about the password but then it might memorize the password so what we build right now is separate context in that asks you for the password and this is the only place that you have to provide your password and you have to trust and we are out of time but we can continue the discussion later you will be able to demo it later during the day and this was more to show what you want to discuss not to really demo your product maybe like a short description of what we want to discuss is what is the browser responsibility and the browser role in this decentralized environment thank you yeah great thank you okay Juan I have a PFS friend so I wanted to tell you stuff about IPFS but I won't have time it's more important to tell you about other things so the IPFS project is a large endeavor and it has a lot of sub-projects and sub-protocols there with these these are self-describing values for the purposes of protocol agility, interoperability across protocols and to avoid lock-in this is one of these things that prevents people from making bad decisions or rather things that look like that good decisions today will certainly be bad decisions tomorrow so ideally you want to create and use formats that allow you to evolve the protocol over time so a pretty simple example is hash functions you might have run across a situation like this when you have four different hashes that are all the same length that happen to be coming from very different functions and you when looking at the value have no idea what those functions are this happens way too often it happens for a variety of reasons people need to move things need to evolve things, people choose better faster hash functions that are created later different hash functions are chosen for different architectures, people are worried about security so they upgrade lots of reasons the problem is that the values don't self-describe and there's usually no way to then inject more code to pass the values out of band when it wasn't designed explicitly at the beginning think about get and what get now will have to do if they want to switch from SHA-1 to SHA-2 to V6 so the trivial solution is you actually prefixes the value itself with some some encoding and this is not new, there's other protocols that have done this in the past but what is new about multi-hash is to make sure the value is part of the digest and not a different thing meaning it should be encodeable the exact same way as the value so this is in hex and the value that is part of the self-describing thing should be part of this so it's a pretty simple format you just have some function code you keep a table, you have some notion of the length because as I showed before here these are all 256-bit hashes that means that some of them have been truncated so you want to take that kind of stuff into account so multi-hash specifically is a self-describing format the codes are in the value itself it's as small as possible have no assumptions about reality make no assumptions about what the hash function that you're using now or using tomorrow is going to be and so on, it has a bunch of implementations and a bunch of different languages people are already adopting it for various things and like multi-hash there's a whole bunch of other protocols we call these multi-formats they're usable by a whole bunch of distributed systems they're coming out of the IPFS project but they're usable by a bunch of things so these are things that are an example is multi-address that shows these different ways of expressing addresses across different transports and so on and the emphasis is to get both human readability in one version of the format and then have a binary-packed version that is very efficient so I won't go through all of these because there's no time but the goal here is to create these very small formats that are usable across these systems and you can find agreement across them without having to lock yourself in the other thing I wanted to talk about is IPLD and this is a thing pretty important so what are all these systems having in common things like plan 9, bitcoin, ethereum, torrents, skit so on they all are distributed data structures, authenticated data structures hash linked data structures so you can think of IPFS as a forest of hash linked data structures so the goal of IPFS is to build a distributed system that allows you to move around these different kinds of data structures without worrying about what specific use case they implement the file system part representing files and directors and so on is just one application of the whole thing so IPLD is a format for creating think of it as an intermediary thin waste for all these different hash cane based distributed systems so you can think of addressing different kinds of data structures across these different hash linked distributed systems with the same format and the idea of IPLD is to try and provide something super simple that already builds on what people expect of the web using things that serialization standards that people already use have some canonical way of expressing the objects so that everyone can agree on how to hash them without having to create site standards for this create a way of passing across these objects so that it's reasonable to traverse from one object to another so the data model of IPLD is really simple you can think of the simple data model that people are used to with JSON or JAML or things like that and use that you get lists, dictionaries integers not in JSON but there are ways to put integers in JSON and the idea is to pack it into a nice binary format and express it to users in JSON, JAML or whatever they prefer to see and then have a way of linking between these objects so we use C++ as one of the representations but the point is to create one to one mappings between these so that it's always extremely clear how you move from one to the other so IPLD is and used by a whole bunch of different systems already and it is ready for standardization we're pretty happy with where it's at there are some extensions that we'll be adding over time but this is one of those candidates that could be really good to potentially produce the standards here and it is meant to it's one of those things that the MFS project is producing for blockchains and so to give you a flavor of what the format looks like and I will go through this with other people in time but you can think of these data structures that start linking to each other and you have these hash links that you're resolving through and the point is to be able to have pathing across these hash links so that imagine in a blockchain you would be able to refer to a parent block and then walk back to history like say you have some hash and then you say slash parent and you move into the parent to the block then you say slash transactions and you move that and slash into one and you can address everything with random access cool so this format is probably one of the more interesting things we have to contribute to the whole W3C workshop on blockchains and do I'll do a longer tutorial and I'll send it out as a video cool thanks okay folks how about we give you first off a big hand for all of the lightning talks I know it was drinking from the fire hose but I was blown away great stuff why don't you take ten minutes and go talk on to yourselves everybody who would like to run a topic table come up here and we'll sort out what the topic tables are and then we'll tell you guys once we reconvene are you going to do a presentation Chris you're running before sorry before everybody splits off if anybody liked Chris's idea Chris actually had this idea of the of the test bed sort of a prototype test bed where we can he has to run actually because planes but if anybody is interested in that while we're starting to organize this come over here and talk to Chris we'll start this conversation and we will find a way to continue it but I want you to make sure that anybody who's interested in that come talk to Chris because I think this is a really amazing idea so everybody else is on a break okay guys so we'll give you we're not okay guys let's huddle up everybody let's huddle up over here where we have room actually probably the more tables the better because that means that we can yeah because people can we'll talk no no no that's no did we talk about IoT yesterday was there a breakout on IoT we can propose it just a second Chris say you guys come over here okay let's have one conversation everybody let's have one conversation sorry per topic yeah so just a second let her run this okay so but everybody we're listening to her right now there is a a structure called a community group and they run that you can have a table but I don't think you're going to get a lot of people I think most people want to talk about technical stuff you can have a table but I think you might want to combine with something else I think there's definitely is anybody else legal Daza Jeff come here okay no that's separate browsers full I think that's what I was asking okay okay you two you two you two get together and figure out what the five word summary is figure out what your five word summary is your summary is legal okay okay you guys you guys split off and come back to us with the proposal I think the conversation should be and then come back whether you decide to or not then we're right now we're just working with fostering and you guys come back to us with the five word summary sorry security and trust anybody else want okay what do you mean by do you guys already have are there any okay we talked a lot about that yesterday unfortunately I really like your proposal okay Chris is going to you're fine okay I see great so legal great think of five words description of that okay we haven't decided yet if they are I want to get everybody like I'm I'm I'm I'm I'm I'm I'm I'm I'm I'm I I'm I'm I'm I'm I'm You know you're... Hello, everybody. Oh, that's... Your Bobby. Sorry. I'm sorry. You've only been... You've only been... So... Oh, look at us. Oh, okay. Get ready. I'm gonna be... I'm gonna be re-appreciated. And we're going to pull us together, and we're going to get up, and we're going to put up your mic. Anybody else, I think it's important for each of you. We'll propagate it out to you. Yes? Yeah. That makes it a lot better. And I think, you know, maybe you have just kind of the overall position that you think you'd be so proud of. Well, so what, so I think the future of Electron is probably the future of Electron. Yeah, that would give you a lot of confidence. And if I need to get back to you guys. Yes. But this is the plan. Yeah. It's good. If you could sometimes say, I'm going to email the whole team. And then if you could make it. That's great. Chris. Thank you so much. All right. Yeah, we can be done. And he's going to go. He's going to go. Okay. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Start gathering again, meet the people who will be leading the topic tables to come up here. You should know who is leading one person per topic, one person per topic, one person per topic. I believe we should have seven people up here. Now I need you to really focus because we will be presenting the topic tables and you will figure out which topic table you are joining and we'll do the same thing as we did yesterday. You will have a bit over an hour or probably an hour to discuss the topic as yesterday and there will be report-backs just before lunch. So we'll start from here, yeah right and then report-backs, okay anyway starting from the right. So a legal group anything connecting the smart, a legal group anything connecting the smart contract and automation environment with the legal environment. We'll be discussing the top level DOM APIs and also how the browser can visually represent various parts of the blockchain like identity, other things and there's a demo. Blockchain standardization proposals, so if you think that there is something that we could start standardization on, what's the component you want to standardize, we're going to be discussing that. Interoperability protocols and primitives, so lightning, interledger, crypto conditions, DAX, smart signatures. We may fork out, we may decide to go primitives and protocols, it depends on who's working on the table. Okay at my table so security evaluation on the trust is needed, we'll be discussing. IoT and blockchain and it'll also discuss the border on more compute and data at the edge. No, what makes sense to standardize, interoperability, I have a strong voice, because there's, interoperability, security, IoT. Protocols and primitives. Okay, security, IoT, is that clear now? Okay, so these faces and people that have those faces will sit at different tables and you should join them and you have 30 seconds to do that, so stand up and run. Yeah. That's, well, there's two different tables that I need to talk about, do you feel like that's not, Mono's kind of driving the pimples, did you feel like there's something else that needs to be.