 So, I'll talk about the X-ZiChain, it's a X-ZiChain Ethereum 1.0 with one more exciting feature. Native token of this X-ZiChain is dying. Right now this die is breached from Ethereum network. And where should we build this X-ZiChain on the ETH Berlin hackathon, which is exciting. We didn't build it on the hackathon because we were responses, but we created the idea and did some prototypes. And after about three weeks after the ETH Berlin hackathon, we partnered with Matildao and launched this X-ZiChain. But to understand how we figure out this idea, I'll talk a little bit about PWA and other X-ZiChains. So, PWA core is a X-ZiChain based on the ETH with smart contracts which define governance and zero control mechanism of this X-ZiChain. Also, native token of this X-ZiChain is back to Ethereum. It means that native token can be transferred back and forth using custodian free bridge. And the bridge is an essential part of this construction because we don't have the bridge and we cannot bridge tokens, then it's hard to define what is the token of this network. So, our idea is to make Ethereum platform pass human scale well for some types of applications with, let's say, less requirements for full centralization. And some tasks which need fast and less expensive network migrate to this platform. So, mostly it's used as a staging network because usually in web services like internet services we have something like testing environment, staging environment and production environment. In blockchain we usually have testing and production. We don't have something small, which is protection, but also we can break it and no one will see it. So, essential part of this X-ZiChain is that native token is bridged to Ethereum and back. So, I think we are the first X-ZiChain or Ethereum which bridged native token back and forth. We launched it in May 2018 with security settings of two signatures from three independent validators that are required to relay event between networks. And up to date this bridged 13 millions of pure tokens. Token prices aren't very much at the current market, right? But it's exciting that about 5% of the equity of the independent network is represented in the form of an ESC20 token on Ethereum right? Native token originally was created on the X-ZiChain. Not like, you know, some networks, they create ESC20 token and after they move ESC20 token to their network, he was, and some other tokens. And sometimes they make like one way process, okay, let's just move out of Ethereum power on blockchain, right? Here it's a bit different. X-ZiChain launched with its own token distribution and emission. And after this native token was bridged to Ethereum in the form of ESC20 token. And after token holders decided to move part of this liquidity, decided themselves, right? Someone asked, they just received an instrument where they can, you know, define how many tokens they want to move and they move it. We don't know exact use cases when people move their native tokens into ESC20 tokens, but I think that's the main use cases of the network between networks. On the right side of the table, you can see that a native token is listed on one set of exchanges and ESC20 representation is listed on another set of exchanges. And you can see that people are using this token bridge every day. So that's very exciting that this type of inter-large protocol between two EMBase networks exists in production and still secure, not hacked, and works in custodial free environment. So token bridge is, sorry for complex, but here basically it's a smart contract on two networks which define which token they bridge and a group of oracles between them. So initially this bridge was started as a fork of parity bridge, but after we rewrote it and now it's token bridge. And it has five components, oracles, which observe events on two networks and related events in the forms of transactions. Smart contract is deployed on both networks. UI application is a bridge UI application where users can decide and define which amount of tokens they want to move. Monitor, which observe balances and can report to both networks to users of the token bridge that balances are different. For example, if the bridge is hacked, anyone can check this using monitoring tool that balances are different. And also this bridge is deployed using standard deployment playbooks. So we know when we deploy an instance of the bridge that all validators run the same, say for unsafe software. So it's written by the standard deployment strategy. But for our case it worked well. So we know that validators deploy their bridge using standard deployment tools. And this deployment tool is independently audited by third party. So this bridge supports three modes. The first bridge for UI was native 2 years and 20. So basically it's two sets of operations. Lock on lock and mint and burn. So native token is locked and unlocked. And it's obvious because usually in public chains we cannot mint and burn native tokens. And on the Ethereum magnet it's a use it when you mint it and burn it. When you lock one pure token on pure SHE, validators relate this event. And smart contracts on the Ethereum side repeat signatures of these related events. And if threshold is reached, they mint new use it when you're playing token. When user move this monster, this token is burned and the corresponding native token is unlocked. So it's quite easy. We support one more quality, which is use it when you're playing. It can be mint and burn, unlock, unlock, unlock, unlock. So it can be deployed in different strategies. And with SHE we figure out that on SHE we can experiment with consensus. And we can launch a new chain with consensus. Back to the bridge. So in this chain, use it when token is locked and unlocked on the Ethereum magnet side. Because we cannot print and mint and burn, die ourselves without following the rules of the smart contract. And the native token is minted and burnt. So what is die? Everyone knows about die, right? So it's a stable token, programmatic stable token on Ethereum platform. Now it's a market level for dies less because GDP is decreasing and so forth. So and here let's introduce X-Dai chain. I thought that X-Dai chain should be hard spoon. Hard spoon is when we take liquidity of one network and move this liquidity to another network. And make next network complementary to the first network. But some people told me that it's not the right definition. The right definition of hard spoon is when we move this liquidity. You cannot move liquidity back like in Ethereum 2.0, right? You move ETH to Ethereum 2.0, no way back. But Ethereum 2.0 or the complementary network for Ethereum 1.0, right? So we decided to name it softknife. So we take a pie, make a slice, move the slice to another network. But we can move the slice back. So on this hard spoon softknife, there is no ambition, right? So when plus created, the worth is zero. So when we start this network, the worth is zero for each block. No premium, right? And there is no reward in the next block, so empty network. And the only way to get native point on this network is to breach FC20 token defined basically in smart contract with this side chain from Ethereum to this side chain. So when the network is started, all balances of all native tokens are zero, right? My first user moved his die on this side chain then, breach related to this event. And the aggregation of signatures on this validator start performed on the side chain side. And side chain basically print new native tokens. So good thing about side chains that we can define for you guys for this smart contract, we can make this execution free, right? So breach is like system smart contract and execution aggregation of signatures free. And this is also good for protection of customer funds, right? Because good thing about free aggregation of signatures, is that it's very likely that validators will run out of balances on this side of the breach, right? And after they aggregated their signatures, any user can relay this event. So basically it's quite reversed plasma from my perspective, a form of reversed plasma. So what's our benefits of this exit chain? So it's compatible with Ethereum 1.0, right? It has all benefits of pure way type of network. It's fast, and it's scalable. It's scalable horizontally and vertically. So vertically it's scalable because while they just can decide, okay guys, this hardware is not enough, let's make bigger hardware, let's increase block size, let's decrease block time and so forth, right? And horizontally means that networks can be launched on premise, both for extra or for other chains. So like if this security model is working, then other projects can launch their own chains. And we will see this model more and more this year, with part of chains and protocol, with zones and cosmos, with side chains with POE and other projects, right? And also the most important and most exciting for me is that everything is stable. We think they just think about this, right? Yes price is stable, platform usage is stable, open systems are stable, and yeah, exciting. For me, it's exciting, right? So like, guest price can be fixed on this. If it's not enough, you know, someone can launch another side chain with option of guest price, right? And it's defined inside and, yeah, it's cool. So people actually used, like, we have 78 users who breached their type back and forth. 25,000 died back and forth. So this side chain had market capital 3,000 died. We could go, now it's 1,000 died and something. And it's also a very interesting example, right? So it's a side chain probably, you know, tried to hack it, you know, it's very hard to hack, you know, all these parts are audited and presumably decentralized. The market travel of the whole construction is very small. So it can be created, this side chain is included for different use cases and for different DSC20 tokens. Yeah, there is a blockchain store for this side chain, you know, people send transactions and they use it. There are some problems with all side chains based on this type of consensus, even though we're trying to make it decentralized and they introduced our security model which we call self-governed PoE. So in self-governed PoE, validators can decide who are validators and then use the network by themselves. So they have on-chain governance and they had ceremony when the first group of validators was unworded for this network. And after validators decide who are the validators. For exit chain, our validators are from the same industry, but they're independent entities. It's one, the first validator is pure in ourselves, the second validator is make it down, and the third validator is give it, quite high group and fourth validator is proper fire, synchronizing, turn. So we have four validators at the moment and each of these validators can decide, can create a pilot to get new validator or remove a validator from the network. And majority of two validators in 72 hours will add new validator or remove validator from the network. So no one can stop two validators from adding new validator or remove these validators. That's what we call self-governed PoE. For our first network, we could start it with 12 validators, now it's 23 validators and then time to add 25 validators till the end of the year. For exit chain, we have four validators but still there are some doubts about decentralization of this solution and that's what we're trying to solve in the second version of exit chain. So with that's upcoming update for exit chain, we plan to replace PoE consensus to TPOS, basically replicated some good parts of EOS consensus into a smart contract in Solarisium and we'll have EOS on Ethereum. And that's for EOS. You're not excited about EOS? Yeah, they have some interesting parts. But we will use this type of what we call practical propo state for zealot control and incentive model but underlying consensus is our implementation of dynamic antibody BFT which is well-known consensus and its strongest features are that it's leaderless and censorship resistant and that it's integrated into our fork of priority plan which we hope to merge with the priority plan later next year. And yeah, this censorship resistant gives some great features for any permissioned network because while they don't see all transactions but they include the blocks in unencrypted form before they create the block. So when I'm validated and I'm selected to create the block I see some transactions encrypted and some transactions unencrypted. To achieve this, this consensus is using threshold signatures and this encryption part is a part of consensus so it's good for censorship resistance and DPOS is giving some other features that we don't know who validators are they can be anyone, even a dog that can be a validator on these consensus and staking token and native token can be different for example, this network can use Ethereum as a staking token and make up Xdai as native token and any year 2020 or native token can be a staking token and also native token can be any year 2020 or native token so it gives a lot of combinations what you can do and Bank Core with Ethereum as a staking token and Bank Core as a native token and you can run fast tags on this and its own liquidity of staking mechanism will be in bridge 12 mainnet or other Ethereum compatible network and for our token bridge we are adding new features that set of validators of a token bridge will be the same set of validators as a network so let's I think we have some time for demo I don't know how to show it and just a network running somewhere but what we have here we have watching is for full feature watching is for cold waxed out we can see here that market cap of this network is $1,600 it's very very small effort right so effort to break it will be much much more ready so wax are fast can be faster, can be second, one second plug sub second plug with high temperature BFT and POP instantly final you see some people use it 4 minutes ago 3 hours ago it's not me, someone else who used it really so wax cap supports much more electrification so API REST API GraphQL API but for free and you can install it on your service and you just cannot show you ads to your data so also paid contract paid property so this contract and so forth supports GraphQL, RPC so basically this explorer is a part of sidechain if you deploy sidechain for yourself you can take this plug scope plug chain explorer and you have the same experience for free open source written in black sphere there are some other networks I just want to mention girly testnet girly testnet future of Ethereum 1.0 testnet you know what is the most exciting that it's supported by multiple plans right? and it heads up to Alfred so with respect to okay so that's a bridge for Xdive you can see some stats you know 79 users used it bridge 26,000 dieback and forth so this bridge holds 65k of Xdive so it's a bit minted this native token 1600 native tokens were minted and there's a massive graph of die and you can see that people use more deposits than withdrawals which is good right? so who are validators? 3 validators no names yet but this model is not very secure at the moment so one signature is required to relay this event from 3 or 30 so each of them can relay this let's see 404 for our pure bridge 404 for our pure bridge which is production bridge which holds 13 million pure tokens we have 3 validators it's a subset of validators of pure network and 2 signatures are required from 3 validators to relay the event so none of them can relay event without another for Xdive for now it's it's a bit different so one signature is required from 304 and that's because we are deploying 4 validators from from brief from give it it takes some time because he is in Latin America now but after we deploy 4 validators it will be 3 signatures from 4 validators that are required to relay event between that person and also there are limits as for our other bridges so for example if all validators are hacked we know that the maximum damage will be per day so it's defined by limits on these networks so let's send something I have 17J on my net it's our fork of MetaMask because MetaMask are not founded to sidechains and forks if you have a sidechain and you try to edit MetaMask they will say no so that's why we built our own fork and now this is friendly and faster and we will see what is faster or some other bugs ok let's switch to Xdai why I am switching to Xdai because transactions on Xdai is faster so we need to wait for less confirmations so what I need to make to relay my Xdai back to DAI turn it to specify amount and send transaction and that's it so after I send this transaction validators will see this event they will wait 8 blocks do you know why why are we waiting for blocks because Ethereum is for block yeah yeah and Ethereum is for block so there is no this probabilistic finality as the same with POA which is based on right now authoritarian also with probabilistic finality and with Honey Budget it will be instant finality so when we will send from Xdai chain 2.0 back to Ethereum it will be 0 confirmation 1 confirmation oops so what's going on ok so after we waited for it for it to last and my Xdai is burnt so how do we burn it I think we just send it to this 0.0 account and the burn of DAI is the biggest account holder on Xdai chain let's see so after validators waited for 8 blocks they created the transaction on the Ethereum side and the latest event to Xdai chain smart contract on the Ethereum side this smart contract will send me Xdai tokens so you can see that I received back Xdai on the Ethereum side so that's Xdai and I think Xdai can buy something from logic you know but if I need to run smart contracts with a stable yes price stable execution price I can take some of my DAI move it to this stage environment and play with it and I think it can be used for many types of applications games, gambling, insurance anything right um any questions two questions right first one why having a native token why not allowing any token to be used for gas second question why not flask yeah there is a proposal to use any token for gas this this thing is interesting because you know something that is created from hackathons usually should be simple right but also to change how you think about things here why we didn't think about it before to figure out on the hackathon because for me I think okay we have a native token usually there is some emission rules how we create native tokens and no one will allow you to create life without this emission curve or some inflation model but here is basically network is empty and on event it creates new native tokens so for me it was okay we can do this because inside chain we have this exciting feature in Paris called block reward smart contract where we can define a reward per block and bridge smart contracts are hooked into this block reward and block reward on the vent from the bridge produce native tokens and why not plasma why not plasma can be plasma yeah so the same concept can be used as plasma I think that the concept that bridge operations are free on site chain site and anyone can relay back these events and also that validators of the bridge are the same validators as validators of consensus and consensus is anonymous and the validators are anonymous security model defined by market needs so I think it's very near by security assumptions on one side and on the other side the set chains are very small small set chains and now to implement something working and give it to users but this XZG will be used on VTH.org if anyone can it will be used for operations between participants of a THDenver and vendors so if you buy food at THDenver you will use XDAI but in actually in rep form of XDAI so it will be something interesting anyone knows why we will rep XDAI on XDAG into your citizen representation of XDAI any ideas now well it's not easy like first idea was let's give this XDAI to any participant there is some fund I don't know let's say $10,000 and we give some XDAI to each participant but if some participants will not spend as native points we don't have any way to get native points back which are not spent so that's why this token is rep first into your security token with upgradability and not spent XDAI will be returned back to organizers and they can spend on some needles actually I almost answered all my questions so basically you hooked into the block reward and then you issue and you die you make it I mean this is an awesome model because this model allows all of these special purpose changes to chains which we will see in the future and especially transferring the value expected for and to make that that's awesome so just as a technical understanding currently the nodes watching they will listen to events and they wait 8 blocks or something and today we can from the state if this is still a function to call or does it just rerun block them from these blocks on to take the ends still there or how could he know that maybe it was not yeah they have a counter for it twice after that they are from the state yeah from the state and can be RPC or local security settings if you want very light value they don't know to use RPC and security the Honey Better BFT is like the input version of the BFT where you have an encryption and on top of that the smart counter governance is then like a voted I mean delegated from the state yes that's right so Honey Better BFT is a way for nodes of validators to achieve consensus set of messages and include them into blocks and governance and visible control define who are validators and why they are validators and our self governed POA there is a governance for each validator to propose a valid and if this valid is confirmed then validator set has changed with DPUS there will be a staking ground like let's say a week and whoever stakes more more likely will be included into the validator set what is the unfreeze period for these stakes one staking around it's one week wait in one week right and the voting if you say 2,000 participants why 2,000 max like why is the limit of the smart counter how it's built well for Honey Better a number of faults calculated 3 multiplied by a number of faults plus 1 in security and vital consensus for example if we want 7 up to 740 months then it's a 3 multiplied by 7 plus 1 is 22 validators so how many candidates is good enough so we decided let's just take two orders of magnitude we can make more it's sidechain you can define block size bigger there is a sidechain called GoChain they have block size of 140 million just a block and you can actually you can get 400 transactions per second if you're 1.0 then we finally can run I think 2 or what about the unreal engines yes but next time you can one question how could be applied to an energy for for an energy supply like for an energy industry for an energy industry how could be applied is it enough it will be enough throughput to to take data from from this from like if you want to control like the energy and the flow and stuff from a supply or to a consumer well based on market conditions so have non-volatile chains is not good right for consumers so volatile chains will be better because you know there are expenses of the lord every day it's kind of true but with as I mentioned there is a go chain we have 114 million gas per block and here on Seiji you can define it with every one right and also you can play with other stuff and we that's great that we have 1.x modifications to appear in protocol which will make improvements in stability into a 1.x and because you are from Paris we are waiting this from you right more optimization when to go to Paris okay to go to turn with you now the source we are open source like of course like I think like I'm I hope that PR from outside as well as outside e-book will be more actively supported I, it's my hope like in Paris sounds interesting sounds like some it's open source but PR policy policy can be different in different there are open source projects right try to get Ethereum class sections or if you're here is another one okay last question before last question I haven't followed the recent developments so much for the poor but now you said that you will implement cyber attack resistance through staking yeah but wasn't the original idea to have actual like proof of authority by registered through like legal notaries or something like this is this still like on the table or did you abandon that idea yeah sure so it sounds faithful and that's our first method which is volatile and that's a list of validators of this first method you can see 23 validators at the moment it's all tasks without all data from comp launching that's by the way it's a proof of physical address now this proof of physical address is open source and supports your C725 token so the client who contributed to the pipeline it's kind of strange right so the proof of authority network creates the legal proof of stake consensus but that's what market is demanding right now right you have to have staking and coins created by a proof of authority network can be staked in the legal proof of stake network so for our first upgrade we use pure tokens it's fine like both models are working it's hard to to get any let's say peer review on our governance model because it's very conservative area and people don't want to accept that launching governance of pure network actually it's great they think like oh it's just some kind of centralized because it's in the US for example or some other arguments it's quite hard to get some independent opinions about this model it's interesting to there's all governance decisions on chain and they made by off chain by individuals but you can see that they have some agreement and disagreement about adding or removing validators so this guy was either by 16 votes or 3 against but before he had a problem before he applied the same validator applied a few months ago and they decided nothing about validators why? because he was traded from the perspective of validators because he used some post box as his proof of physical address and they figured out they made their own fidelity on something but now they figured out that he's working for Google and he posted his physical address of his data and this model is working and this great thing about this governance is that it's enforceable automatically so when the valid is finished any validators can finalize and enforce this action and also anyone can propose a new valid with type of a manufacturing contract basically any validator can propose a placement of the full governance model if you want to add a new type of like we did with emission funds I copied this model from use so the network produced additional emission validators can decide how to spend this emission so like this belt was added by launching governance enforced by supermajority of validators so they decided ok let's have this new functionality and this is enforceable consensus the same this new model will not work for any consensus but it will work for DPOAs for DPOAs to plant a mint of minting of governance token which can be used to upgrade bridges and upgrade consensus so the same here you have to have a let's say yeah I cannot add valid because my key is not voting key and voting key is a part of my identity on chain as a validator and when I'm onboard as a validator I receive three keys from I receive a pool of my voting key, mining key and pair of keys from other validators so they include my voting key and I can create valid well with DPOAs I have to I have to be a part of active group of black producers and also I have to take some governance token to make decisions about I don't know if it's more risk or less let's see now it's time to break