Dear Joaquin, All, I have shared a few ideas for discussion in the document. Moreover, apologies for the delay, there was a request to share further information about the IOTA ledger. In particular: - the energy consumption, - the transaction per seconds, - and who is working on Digital Twins. Here is a little more information, happy to discuss further during our brainstorming session. Michele *Re to transaction per seconds*, we are already over 1000 transaction per second processed with a confirmation time (finality), lower than 30 seconds. New launch of IOTA Chrysalis, will also increase TPS and lower the confirmation time to 1 second. All the new feature here: https://blog.iota.org/iota-chrysalis-a-new-dawn/ *Re to digital twin (DT): *we didn't build anything yet but there is interest from stakeholders in this group, https://www.constructionblockchain.org/ such as Bentley Infrastructure. Main focus is on building digital twins for BEMS. However this combines well also with cities digital twins. We were thinking to abstract creation of DT from DTDL from MS Azure and NGSI to IOTA stream. A topic also proposed for further discussion. This will create easy mapping of immutable DT. *Re to energy,* as mentioned it is not easy to measure, however: Given our focus on low power devices, our system potentially offers energy savings over existing solutions, which require high powered servers. In DLTs, expensive energy consumption typically arises in DLTs from PoW (or proof of work), which serves a dual purpose. First, PoW is a sybil protection mechanism, which limits the number of identities an attack can create. Second, PoW is a mechanism that limits access to the network. The IOTA protocol and the IOTA Data Sharding Protocol replaces each of these mechanisms with energy-efficient alternatives. Here is a small excerpt on our sustainability features. *The IOTA Foundation recognizes the importance of reducing carbon emissions. Moreover, reducing the energy consumption of DLTs is directly related to enabling low power devices and IoT networks. Therefore, the IOTA Foundation will continue to work to reduce carbon emissions as new technologies are available. The IOTA Foundation has an exceptional track record when it comes to decreasing emissions. The IOTA Protocol has recently undergone some dramatic improvements through the Chrysalis project. Before Chrysalis, the IOTA Network was running on ternary software and using the quantum resistant Winternitz One time Signature, or WOTS. After Chrysalis, IOTA moved to a binary architecture and enabled the ED25591 signature scheme. As a result, the IOTA Network received a huge boost in network efficiency, substantially reducing our carbon footprint per transaction on a Rasberry Pi 3 from 155 J to 6 J, a 96% reduction. The Chrysalis network, and the PreChrysalis network are both still secured by proof of work, but this proof of work will be phased out with our coordicide project which implements IOTA 2.0. With this in mind it would be difficult to compare IOTA against other PoW-based consensus ledgers, thus making IOTA the most suitable DLT to achieve carbon neutrality, when combined with other emerging green-infrastructure technologies (such green cloud). Since carbon neutrality can only arise in a DLT if the components are being sourced off of sustainable energy. Lastly, another energy saving innovation in IOTA is our second layer approach to smart contracts. In most blockchains, smart contracts run directly on the chain, and anyone wishing to validate all of the blocks in the chain must execute every smart contract. Smart contracts can be very heavy, and millions of nodes executing them is a waste of energy. In the IOTA Smart Contract Protocol, a committee of nodes execute the smart contract, and post periodic, auditable state updates which essentially consist of a hash. Nodes uninterested in a particular smart contract can ignore the contract and the state updates themselves, and only process the transaction containing them. Thus, smart contracts add no more computational nor energy overhead, to validating the ledger. * On Tue, Feb 23, 2021 at 12:22 PM joaquin.salvachua <joaquin.salvachua at upm.es> wrote: > Hello, > > After the different presentations we agree on deliver some information > regarding possible collaborations with ongoing on activities. > > Please fill this in the following document before next Monday in order to > have a brainstorming meeting on Tuesday: > > > https://docs.google.com/document/d/1-OInwjgp52bsRi9oxUF0VKteudvJIk-CpkdfOJ_KOJE/edit?usp=sharing > > Best Regards > > Joaquin Salvachua > > > > __________________________________________________________________________________________ > > You can get more information about our cookies and privacy policies on the > following links: > - https://wiki.fiware.org/FIWARE_Privacy_Policy > - https://wiki.fiware.org/Cookies_Policy_FIWARE > > > fiware-roadmap-dlt mailing list > fiware-roadmap-dlt at lists.fiware.org > > To unsubscribe from fiware-roadmap-dlt mailing list, go to the information > page of the list at: > https://lists.fiware.org/listinfo/fiware-roadmap-dlt > > -- *IOTΛ Foundation* Head of Telco & Infrastructure Development https://www.linkedin.com/in/michelenati/ -- *IOTA Foundation* c/o Nextland Strassburgerstraße 55 10405 Berlin, Germany Board of Directors: Dominik Schiener, Serguei Popov, Navin Ramachandran ID/Foundation No.: 3416/1234/2 (Foundation Register of Berlin) -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-roadmap-dlt/attachments/20210303/71b68a73/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy