Enterprise EVM Blockchain: Blade - Nemanja Nedic | Ethernal

[Applause] okay well hello everyone I'm n from internal today I would like to present you our latest product named blade uh it is a blockchain that is built especially to Target Enterprise corporations so let's get started with it so in order for any piece of code to become a part of Enterprise ecosystem it needs to provide a certain features and now I will outline some of those features and later on elaborate how blade meets all the conditions so start let's start with the first one of course the top levels if of security is like uh the main thing so the any kind of data that is written to a storage that is transfer through the communication line or it is loaded into the memory must make must be completely safe so protected in every situation the ENT the second one is integration if we introduce a new a new software within Enterprise ecosystem that software must not invade existing solution in any way so the security of the existing Solutions must stay the same and the proper opulation of those uh systems must continue furthermore all the employees within the corporation must have a friendly user interface so that they can send requests the third one is reliability so our blockchain has to work properly without fails without breaking down and the network must be alive 24/7 so the highest grade of of resilience is required for these kinds of situations and last not the least is performance there may be like thousands of employees inside of Corporations and all of them expect to receive responses promptly now we'll go through all of these uh requirements one by one and explain how blade meets the requirements so let's start with the security how we did it well blade is secure by Design which means that during the period of architectural design we need to identify all the possible threats that can appear and then to mitigate them and have some recommendation how they can be solved later on during the period of implementation the implementation just should follow the recommendations and that's it and how we allocate those threats well we use risk-based methodology we employ like a bunch of threat models which will tell us where the threats are this is one of the examples how a TR model looks like you can see in the middle that there is a chain node like a virtual machine that holds our software and then there are a bunch of uh black lines that represent interaction between our node with the environment on the other hand there are red lines that represent trust boundaries every intersection between red line and the black line is a possible threat so we need to address all of those if we want to have a secure secure software ready for any kind of Enterprise ecosystem I will now talk about the most important threats and how we mitigate them so the first one is that data store on this can be disclosed so we all know that uh blocks are stored in some kind of level DB or mdbx or any kind of database that is actually stationed on the dis of the virtual machine in order to keep those data safe we need to encrypt them for those reasons blade employs keys to encrypt those data when they are written to the disk and then decrypt the data if they are loaded into the memory the second threat deals with trafficking so sending data through the communication lines that data can be sniffed again we need to protect data somehow so encryption as well we have two types in communication of communication within the blockchain peer-to-peer communication and RPC communication with the environment in both cases we utilize certificates so for peer-to-peer communication during the handshake uh the no exchange uh certificates and for the RPC communication we utilize https so certificates again uh the third thread which is quite interesting to me is that some customers want to go one step even further and they want that data which is loaded into the memory is encrypted as well is protected so how we deal with this uh we actually ask our customers to allocate additional funds so that we can use trusted execution environments during the deployment of our solution and the last but not the least is the unauthorized access to the keys that nodes use blade uses two types of private Keys the first one is BLS and the second one elliptic curves and both of those has to be protected and uh safe for those reasons obviously we leverage Key Management Systems even Hardware security uh models that's it regarding security let's now move on to integration as I said when we include a new type of software into already existing environment it shouldn't anyhow invade the operation of already existing software for those purposes we need to be fully compliant with the standard that is recommended by the Enterprise Corporation the name of the standard is n D cyber security framework I will get in a minute about how this is integrated so even more the integration itself needs to be straightforward so no not many steps so we do not burden the admins of those Enterprises so they hate us and our software they should be like the friend of us over there and this is actually how that integration looks like it isn't complicated as it as it looks uh in the picture like in the bottom right right corner you can see our blockchain and all the other components around it are there to create some kind of integration system uh so you can imagine this as our approach for account obstruction for Enterprises uh on the left we have enterpr users those are actually employees that are going to use use features of the blockchain and what is the deal with them they shouldn't be aware that they even use blockchain they should log in with their usual credentials like uh email and password and then send some requests to the system they have a simple web application and that that application will send data to our system which will be received by a transaction coordinator the transaction coordinator is a component uh which is in charge for communication with the blockchain so whenever a data is received to a transaction coordinator a transaction is Created from those data and submitted to blockchain there is one really important thing in this integration part blockchain expects to receive data only from the transaction coordinator every other data should be disregarded and for those purposes transaction coordinator has a private key of its own so every message sent uh to the blockchain is additionally signed with that private key and then when the message is received by the blockchain uh it can be verified against the the public key of the transaction coordinator if everything is okay it will be included into the sorry into the blockchain otherwise it will be rejected now let's move on to re reliability the first point guys I need some water just yeah M my mouth are completely dry okay regarding reliability the first thing that we need to have is a quality software so what happens there during the process of implementation we need to follow all the possible continuous integration procedures so nightly build daily builds uh automating testing uh uh performance testing if like performance some somehow somehow degrades falls down the complete process of develop and we stop until we figure out uh what is going on what piece of code uh made the made the performance test fail so after we get the quality code then we have a proper deployment our deployment sorry our deployment is B is built in a such a way that it can be configured for different users some users want like five validators the other wants 10 uh the second one wants organization or blockchains or sorry OD lot balancers in one way the others in a second way and so on and so on when we configure that Network we only need one click to deploy the network and wait for a couple of minutes for Network to be alive later on uh we have one feature that are really proud of and we call it self- recovery so if any note fails during the regular uh lifetime of a block chain we have uh self- recovery mechanism that will like uh recover that node without any kind of interaction from the user manually at the end we track all the important metrics like uh health of consensus uh like uh uh block time how blocks are populated and so on and so on to figure out if we need any kind of additional interven mention into the network and how we do all of this deployment well we have developed tool for those purposes and as you as you can see on the left there is a menu which defined what can be configured so we can configure uh number of validators what will be computing power for each of the validators uh number of full nodes then load balancers how will be load balancers connected to the full node all the validators uh then defined uh block explorers uh some FS for initial accounts and then smart contracts for uh Genesis so the smart contracts which will be included in the first block after clicking to deploy bug you will get your uh Network quite soon now let's move on to the performance probably the most important part first of all I want to talk about about TVM we actually used as it should be official uh Benchmark tests and you can see uh the black lines the black lines sorry blue lines the blue lines is where we started a couple of months ago uh the orange lines are very very yesterday during the night I received the like update of this diagram but I haven't enough time to include it into the presentation so at the moment these red lines are still going going down and since this is like a process I hopefully uh I would like that they go down in the future like significantly then let's talk a little bit about data layer where we are going to store our blocks we were considering two databases level DB and mdbx and considering like performances and metrics of those databases and the features that they provide and weere since we are targeting performances for our data layer we decided to use level DB and then uh build a wrapper around it to add all the additional features that we require ourselves for after we have finished that implementation these are the numbers for this consumption if we want to save 10,000 fully completed blocks fully populated blocks we need less than 4 megab if we want to read uh 100 blocks randomly we'll need less than 16 seconds these numbers are actually compared with some well-known blockchains and I can tell you they are like a couple of times better then the last and the most important performance is transactions per second actually gas utilization per second in this case for our native token transfers there are situations where we can reach 47 100 of sections per second on average we have 2200 for erc20 transfers we can reach 3300 per second and on average more than 1,600 erc721 uh we have about 700 transactions per second now I want to spend a couple of minutes for additional features that we provide the blockchain itself can be configured as layer one or Layer Two it has an integrated bridge if it is deployed as Layer Two uh anyone configure its own stake and reward tokens and of course we support governance regular account abstraction is on its way is being implemented as we speak now let's talk a little bit about application of the blade so I'm not sure if you are familiar with uh Apex Fusion it is a new environment a new system that is being board and this peak and like uh it is intended to connect to to Worlds cardano you takes chains with Dr chains first of all evm chains later on uh Cosmos chain will be in produced as well and the thing is that there is something in the middle that provides exchange of tokens between those chains if we simplify this picture it will look like this so blade is in the middle and blade is like the highest level of security for exchanging tokens in this ecosystem the other honorable mentions are this next gen blockchain is probably going to be built on top top of Blade he going to use blade technology there is a promos project that uh reads data from the blockchain and then uh then sends it back and Infinity games that project uses blade to uh deploy smart contracts there are some additional projects but I cannot speak about them at this moment uh we'll see what will happen that's it guys I'm ready for [Applause] questions feel free to raise your hand if you do have a question no questions everything that means good everything is clear everything clear yeah I'm a great lecturer give it up for NE