<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Things Lab - Medium]]></title>
        <description><![CDATA[We make things! - Medium]]></description>
        <link>https://medium.com/things-lab?source=rss----df3405b9c372---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Things Lab - Medium</title>
            <link>https://medium.com/things-lab?source=rss----df3405b9c372---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 07:11:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/things-lab" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[IOTA Permanode As a Service]]></title>
            <link>https://medium.com/things-lab/iota-permanode-as-a-service-b907216c6931?source=rss----df3405b9c372---4</link>
            <guid isPermaLink="false">https://medium.com/p/b907216c6931</guid>
            <category><![CDATA[permanode]]></category>
            <category><![CDATA[dlt]]></category>
            <category><![CDATA[storage]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[iota]]></category>
            <dc:creator><![CDATA[Stefano Della Valle]]></dc:creator>
            <pubDate>Tue, 31 Mar 2020 15:21:23 GMT</pubDate>
            <atom:updated>2020-03-31T17:56:55.170Z</atom:updated>
            <content:encoded><![CDATA[<h4>Long-lasting data storage on IOTA’s Tangle</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4OhxRe7-scNzabZEaqjOxw.png" /></figure><p>At first glance it may seem absurd that someone would need a service in order to have an IOTA node.<br>That’s because the activation of a known IOTA node is in fact a very simple operation, and in the coming releases the configuration of peering with other nodes will be fully automated.</p><p>However, node activation may be required for several reasons and some of these introduce additional complexities.</p><p>For example, if an application based on the IOTA network publishes data, being able to ensure node response times is a key factor. This involves an organizational cost and a specific expertise to keep the node efficient as performance needs increase.</p><p>Another typical requirement of such applications is to preserve this data over a long period of time.</p><p>The standard node actually deletes transactions from its database after a configurable period of time, and it does not provide any function to discriminate which transactions to delete and which ones to keep.</p><p>These two needs, which were directly perceived by us during the development of our other projects, motivated us to create the Things Lab Permanode service.</p><h4>The Things Lab Permanode service</h4><p>Things Lab’s IOTA Permanode service provides a fully managed IOTA node with “industry grade” features and the peculiarity of preserving the transactions produced by customers, according to their specific time requirement.</p><p>Each customer can create a specific application identity that will tag their transactions, allowing them to be precisely identified in the database.</p><p>The system has been developed on the Google Firebase platform and is therefore able to<strong> support virtually unlimited simultaneous connections,</strong> making it possible to guarantee the performance and reliability of the service.</p><p>In this first version, the service supports the following standard IRI API (IOTA Reference Implementation):</p><ul><li>GetTransactionToApprove: returns two valid transactions to link a new transaction;</li><li>BroadcastTransaction: sends one or more transactions to other IOTA public network nodes;</li><li>StoreTransaction: stores transactions on Google Firestore database.</li></ul><p>Needless to say, the performance of the database is extremely high and is not affected by the number of connected customers.</p><p>Soon we will also release the AttachToTangle function, which runs ProfOfWork, thus providing all the API needed to create an IOTA transaction.</p><h4>Data model</h4><p>The call to StoreTransaction causes the transaction to be registered with its properties:</p><ul><li>Hash;</li><li>Address;</li><li>Tag;</li><li>Bundle;</li><li>Timestamp;</li><li>Application ID;</li><li>Private flag.</li></ul><p>Note: Application ID and Private flag are additional parameters produced by the Permanode application platform.</p><h4>Searching and retrieving transactions in the database</h4><p>The following search functions are also provided:</p><ul><li>FindTransactions: given the parameters of one or more transactions (tag, bundle, address, etc.), it searches the database and returns all hashes of all transactions that possess the required characteristics;</li><li>GetTrytes: gives the hashes of one or more transactions and returns the data structure in trytes.</li></ul><p>The FindTransaction function has been extended to allow the search for transactions in a time range and by Application ID.</p><blockquote><strong><em>Please note that the FindTransaction feature of the Permanode service can only return transactions that have been recorded with the StoreTransaction feature. No transactions generated by other nodes and received via “gossip protocol” are stored in the Permanode.</em></strong></blockquote><blockquote><strong><em>In other words, this Permanode is a node that can guarantee the indefinite storage of your data, NOT all the transactions produced by the IOTA network.</em></strong></blockquote><blockquote><strong><em>However, all transactions stored by all Things Lab Permanode service’s customers are visible and can be retrieved by the FindTransactions or GetTrytes functions.</em></strong></blockquote><h3>Virtual private node</h3><p>For some applications, privacy is a key factor.<br>To support these applications, the Permanode service provides a special entry point to which it responds identically except for the StoreTransactions and BroadcastTransaction API.</p><p>By calling StoreTransactions on this endpoint, the transaction will be stored in the database with a privacy flag that excludes it from the GetTryes and FindTransacions responses from the owner of the transaction.</p><p>The BroadcastTransaction function on this endpoint does not perform any operations and avoids the propagation of the transaction to the other network nodes.</p><p>Obviously value transactions sent to this endpoint will never be confirmed.<br>This functional option is equivalent to activating a private network of IOTA nodes that exclusively share transactions created by an application. Given the virtually unlimited capacity of the system, this mode is more efficient and cost-effective.</p><h3>Persistence of transactions</h3><p>Normal IOTA nodes cannot store transactions on their local database indefinitely. This is due to various factors:</p><ul><li>Unlike other technologies, IOTA network nodes operate in asynchronous mode, so the incoming transaction volume is virtually unlimited and it is therefore impossible to guarantee indefinite retention of all transactions on all nodes;</li><li>It is not possible to filter incoming transactions with some particular algorithm, because every new transaction could be fundamental to identify a conflict in the Tangle.</li></ul><p>To limit the growth of the local database, the node then performs an operation called “local snapshot” which in summary removes the oldest transactions at zero value or with validity.</p><p>The deletion could be done selectively with application logic, but it would force to have one node for each application.</p><p><strong>The Things Lab Permande solves this issue by combining the functionality of standard nodes with the virtually unlimited storage capacity of the Google Firebase platform.</strong></p><p>The storage process is defined based on the needs of the individual client’s application, as each transaction sent by a client with the StoreTransaction function is stored in the Google Firestore database with its own characteristics (tag, bundle, address) plus two other parameters:</p><ul><li>Timestamp;</li><li>Application ID.</li></ul><p>A special function, RemoveTrasaction, allows each customer to delete a set of their own transactions that they no longer consider necessary by indicating a time period.</p><p>Customers can only delete their own transactions selected by the Application ID.</p><h3>Architecture</h3><p>The system consists of the following components:</p><ul><li>Registration front end: allows customers to activate a profile, purchase the service, check the amount of transactions stored in the system and perform searches;</li><li>Application front-end: it consists of a series of Google Firebase Functions that respond to entry points by supporting standard IRI calls and extended service functions;</li><li>IOTA Nodes: two or more IOTA nodes managed and monitored by Things Lab to which calls received from the application front-end are forwarded and must be managed by a standard node synchronized with the rest of the network. In particular, the GetTransactionsToApprove and BroadcastTransactions are addressed to IOTA nodes;</li><li>Performance monitor: it is a service active on an external vps that simulates a user and constantly checks the operating status of the system, alerting the Things Lab team in case the response times are higher than set limits or IOTA nodes are not synchronized.</li></ul><h3>Service and storage costs</h3><p>The service will likely be priced with “Service Tokens” that can be purchased in packages of different sizes.</p><p>These Tokens can be spent to purchase the storage of transactions and using API functions.</p><p>Note: these “Service Tokens” will only be an internal currency for the service, they are NOT a form of cryptocurrency and they will NOT be traded or sold to the public.</p><p>More details about the pricing and economic conditions will come soon.</p><h4><strong><em>Our Permanode solution will soon be used in combination with our </em></strong><a href="https://medium.com/things-lab/productid-4c9c8a7cbb4"><strong><em>ProductID</em></strong></a><strong><em> in a very exciting and groundbreaking project, stay tuned for further details!</em></strong></h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b907216c6931" width="1" height="1" alt=""><hr><p><a href="https://medium.com/things-lab/iota-permanode-as-a-service-b907216c6931">IOTA Permanode As a Service</a> was originally published in <a href="https://medium.com/things-lab">Things Lab</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is wrong in the DB concurrency adoption forecast]]></title>
            <link>https://medium.com/things-lab/what-is-wrong-in-the-db-concurrency-adoption-forecast-dea1bc4d42c6?source=rss----df3405b9c372---4</link>
            <guid isPermaLink="false">https://medium.com/p/dea1bc4d42c6</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[iota]]></category>
            <category><![CDATA[adoption]]></category>
            <category><![CDATA[bds]]></category>
            <category><![CDATA[economy]]></category>
            <dc:creator><![CDATA[Stefano Della Valle]]></dc:creator>
            <pubDate>Wed, 05 Feb 2020 16:10:20 GMT</pubDate>
            <atom:updated>2020-02-05T16:10:20.329Z</atom:updated>
            <content:encoded><![CDATA[<h4>Human vs machine economy</h4><p>Recently, Deutsche Bank released an interesting study comparing the development of the Internet with the spread of crypto-currency. You can download it <a href="https://www.dbresearch.com/PROD/RPS_EN-PROD/PROD0000000000504589/The_Future_of_Payments_-_Part_III__Digital_Currenc.pdf">here</a>.</p><p>I really enjoy the “money flower” on page 4, which immediately makes visually understandable the great variety of contexts in which we use currency.</p><p>And of course it is impressive to note the overlapping of the Internet adoption curve with the number of crypto-currency wallets.</p><p>Where’s the mistake?</p><p>The basic error that I identified in this study is the tendency to consider the adoption of Internet, measured in millions of users, comparable with the adoption of cryptos, measured in number of wallets.</p><p>In my opinion these two quantities are not comparable, for a simple reason: Internet is a network that supports multiple applications, wallets are a single application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*3d7_2tR3DqfQKAA3euVOSA.png" /></figure><p>I superimposed on the DB chart the logos of the main platforms that have actually contributed to the adoption of Internet and the consequent development of the network, trying to maintain a consistent time sequence with the represented trend. The interval represented is from 1995 to 2010.</p><p>I think the point is easy to understand: the global development of Internet has been supported by new applications and new tools, that have produced significant benefits in many commercial and industrial sectors.</p><p>On the contrary, the DB study suggests that the progressive adoption of crypto-currencies is self-supported, or justified by reasons inherent in the wallet application.</p><p>Everyone does know that currently the possibility to use crypto-currency wallets to make real purchases is very limited. It can even be argued that it is not even an urgently felt necessity because of price volatility, which in turn is derived from the speculative nature of the main crypto-currencies.</p><p>For this reason, DB’s report claims that there is a large demand for stable coins, the availability of which could actually accelerate the spread of wallets, and it appears to be correct.</p><p>I therefore agree that if reliable stable coins will not be made available by the national monetary authorities, they will certainly be offered by economic operators of similar global reputation, such as Facebook or Amazon.</p><p>However, it seems clear to me that the demand for stable coins is not significant to measure real adoption. As an example, Amazon could easily create its own currency with a stable exchange rate against USD, that would be easily widely adopted without the need for it to be actually distributed, peer-to-peer and based on a permissionless network.</p><h4>Real crypto applications</h4><p>So, what is the adoption path for crypto coins that we can actually predict?</p><p>Practically, today there is only one great application for crypto-currencies: trading.<br>All the others have a marginal impact and are considered MPVs.<br>Clearly, this it is not an application destined to be widely adopted by generic users.</p><p>I believe that, as it happened for the development of Internet, specific applications that require and leverage the peculiarities of crypto coins will have to emerge .</p><p>And here emerges a problem though: the main peculiarity of cryptocurrencies, the one that is the reason for the rapid adoption and wide participation, is the reduced ability of financial authorities to control what happens in the markets. The principle behind these systems is “code rules”, i.e. we do not want authorities, monetary policies and processes based on human initiative.<br>Instead, we want a system that manages itself programmatically.</p><p>Finally, it should be noted that current digital payment systems, although not based on distributed networks, are widespread. I cannot remember a historical case where a “traditional” system has been replaced by a more “innovative” one in the absence of significant economic reasons.</p><p>In summary:<br>- real crypto currencies are not manageable by financial authorities;<br>- the main advantages of crypto currencies are privacy, independence from financial institutions, lack of market regulation.</p><p>I think it is clear that these factors are very unlikely to produce wide and rapid adoption, especially in the presence of unfriendly regulations.</p><h4>So, are the cryptos dying?</h4><p>Absolutely not.</p><p>As it happened with Internet, we need to find those new applications that we are perhaps struggling to imagine today, but which will give a real boost to adoption.</p><p>In 1995 no one would have imagined that only five years later we would be able to make intercontinental calls for free with Skype. How many would have imagined that we could travel the world without having to get a detailed map, thanks to Google Maps? And who would have bet that it would become normal for anyone to publish photos, books and videos at no cost on Facebook, Medium and Youtube?</p><p>These are the advantages that have made Internet an indispensable tool, advantages that we can represent in economic terms, such as savings or increased productivity.</p><p>We must find the same advantages to say that cryptos will grow as much as Inernet did.</p><h4>Technical aspects</h4><p>There is an additional technical aspect that makes the comparison between Internet adoption and crypto adoption completely inappropriate: Internet is designed to scale infinitely and has no fees.</p><p>Between 1990 and the birth of Internet as we know it, there has been a fierce battle between ITU (International Telecommunication Union) and IETF (Internet Engineering Task Force), in order to decide who was to manage the development of the network and how it had to be done. ITU basically wanted to charge for traffic and thought that an isochronous (synchronous) network would be indispensable to guarantee the support of audio-video services. Fortunately, IETF and the asynchronous network won and as we know, audio and video services are not affected at all.</p><p>Today, we have a technical limit to adoption that I think is very underestimated in the DB study: almost all cryto-currency platforms do not scale because they are synchronous and ask for a fee to send money.</p><p>If Internet had had these limitations, it would have never expanded the way it did.</p><h4>Conclusion</h4><p>I am not able to make exhaustive predictions about the many possible applications of the (real) crypto currencies that will certainly come, but I am able to highlight a fact already proven: there is a large demand for payment instruments that make trust a commodity.</p><p>In simple terms, this means being able to send small amounts of value as payment for a commercial transaction, in which a small amount of service or product has been obtained.</p><p>This miniaturization of trade allows the exchange between unreliable counterparties to take place without the need for a third party escrow.</p><p>This stems from the reduced risks that both parties can accept in the case the other party stops supplying or paying. The loss is so small that there is no need to cover the risk with agreements, penalties or insurance.</p><p>Obviously, miniaturization of transactions is not compatible with fees, and a large volume of transactions is needed to move a lot of value.</p><p>This makes this model unlikely to be used for human purposes, but it is perfect for the automation of industrial and commercial purchasing processes.</p><p>Thism thus explains my interest in IOTA, the only crypto platform that has an asynchronous backbone, and why <a href="https://www.omg.org/">OMG</a> is working to create an industry standard for value exchange via DLT.</p><h4>In conclusion</h4><p>Yes: DB’s prediction of adoption will come true, but it is possible that wallet applications that are used as an element of comparison will not be used by humans, but instead by machines.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dea1bc4d42c6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/things-lab/what-is-wrong-in-the-db-concurrency-adoption-forecast-dea1bc4d42c6">What is wrong in the DB concurrency adoption forecast</a> was originally published in <a href="https://medium.com/things-lab">Things Lab</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Coodicide is coming]]></title>
            <link>https://medium.com/things-lab/coodicide-is-coming-ae595217feba?source=rss----df3405b9c372---4</link>
            <guid isPermaLink="false">https://medium.com/p/ae595217feba</guid>
            <category><![CDATA[iota]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[distributed-ledgers]]></category>
            <category><![CDATA[dlt]]></category>
            <dc:creator><![CDATA[Stefano Della Valle]]></dc:creator>
            <pubDate>Wed, 22 Jan 2020 10:03:48 GMT</pubDate>
            <atom:updated>2020-01-22T15:38:30.068Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*64UhKq_mpVIJelTd" /></figure><h3>Coordicide is coming</h3><h4>A new academic paper describing the functional principles of the new version of the IOTA network has been released in recent days. You can find it <a href="https://blog.iota.org/iota-releases-updated-coordicide-whitepaper-9fde4e01c3a7">here</a></h4><p>Those who read my writing knows that I’m a fan of technology, crypto currency in general and especially IOTA.</p><p>Now I could go on describing the innovative ideas that the new WP of IOTA contains, enumerating the various components that ensure the distribution of consensus even in the absence of economic incentive.</p><p>I could, but I don’t, because the document would deserve an in-depth examination for practically every page, but I don’t think this would help to understand once and for all what the value of the IOTA is and why it is fundamental for technological development in the coming years.</p><p>So I try to give an answer to this simple question: what is the reason why the IOTA should be successful, perhaps more than any other DLT seen so far?</p><p>We have to say that only time will tell whether IOTA will be more or less successful than other projects, but that I personally have very few doubts.</p><p>My feeling comes partly from the fact that I am fortunate enough to be able to read documents like this new WP and get a clear idea of the feasibility. But it also comes from the fact that by now daily news of new patents of applications and technologies in which IOTA is mentioned as a specific solution to manage critical and functional aspects. If also Intel, Bosh, Siemens and dozens of other giants of the IT and TLC market have the same perception as me, maybe it is not a wrong feeling.</p><p>IOTA will therefore (almost) certainly be successful as a technological system for IT and IoT solutions where the use of a public network of nodes is useful, convenient or fundamental.</p><p>In practice IOTA is on the same level as the Internet: both are advantageous because they scale, are free and are public.</p><p>A solid argument, but one that certainly does not satisfy the most skeptical and especially those who are used to thinking of a decentralized network as a system that can exist only if the nodes that make it up get a reward.</p><p>Yet there are many examples in nature of organisations (including human ones) in which each individual participates and contributes to the functioning of the system in an absolutely voluntary way and without economic return. Bringing this model into a technological system seems not easy, but in reality it is exactly what will be achieved with the implementation of the content of the IOTA whitepaper.</p><p>To explain how a completely decentralized network works without economic incentives, I must highlight some aspects of the design of the best known decentralized networks such as Bitcoin, Ethereum, Dash, Tezos, ...</p><p>These network are defined “peer-to-peer”, meaning that value exchange takes place between nodes that communicate directly. In reality, since 2010 (therefore already in the Bitcoin system) nodes have undergone a process of specialization that has distorted the idea of peer-to-peer.</p><p>Today it is the “wallets” that create transactions and pass it to a node that propagates it but does not manage the creation of the block. This phase is supported by miners with dedicated nodes and processors specialized in calculating the hash function. A transaction created by the “wallet” is practically non-existent until a third party takes it over and inserts it into a valid block.</p><p>More or less this is true in all crypto networks, both POW-based and POS-based.</p><p>Master node, validators, routers, miners, full nodes, light nodes, etc. are all elements that make up the network, creating a sophisticated organization that specifically supports an extremely secure monetary application. Any other application can be realized as a superstructure of the monetary application.</p><p>The problem is that this model based on specialized components is not supported if the critical nodes are not incentivized.</p><p>There are various ways to encourage the participation of key nodes. A direct incentive is the fees paid for each transaction that are obtained by the fastest miner or the validator that approves it. Another method is the rewards paid per block, another is the interest given to those who delegate a masternode by providing capital.</p><p>Finally, there is also a form of “deferred” incentive constituted by the possibility that the value of the token grows as the size of the network grows, which gives an incentive to activate functional nodes even without direct reward. This is the form that worked best for Bitcoin.</p><p>This is because even if all the nodes were not remunerated, if the network grew without moving tokens there would not be a real economic effect capable of creating a demand for tokens and therefore to its growth.</p><p><strong>Here’s the difference with IOTA: it is a network equipped with a token having the same name, but is specifically designed to handle non-economic transactions and support decentralized communication in an unreliable medium.</strong></p><p>This type of transaction moves data and to do so, since a data can have a negligible value, it cannot be burdened with a cost, neither direct in the form of fees, nor indirect in any other form that brings an advantage to those who own the token.</p><p>If there was a form of indirect cost it would still be a cost that would make the network unusable for many applications.</p><p>So IOTA has no fees, no mining, no reward and no specialized nodes. Each node is functionally equal and equivalent, at least in the main network. Satellite networks for specific real time applications will have particular nodes, but they will always use either the same protocol and the same design philosophy.</p><p>These simple features explain why IOTA is the ideal solution for industrial applications that have made it chosen by the world’s technology giants: you can design an application using IOTA technology without having to worry about any side effects.</p><p>In practice IOTA provides designers with one thing that no other network can do: define and respect KPIs (Key Performance Indicators) of a service based on an IOTA node.</p><p>For example, it is possible to size the node to handle a certain amount of transactions per second. This performance level is not affected by what happens on the other nodes and is therefore perfectly controllable.</p><p>In other words, the IOTA makes it possible to design any type of distributed application without the constraints arising from the monetary application of the network limiting its feasibility.</p><p><strong>In summary IOTA provides the same advantages as a private DLT, but as the node is part of a public network, it also provides a token and distributed consent on the status of the register of economic transactions.</strong></p><p>One may now wonder what is the purpose and value of the token. The answer is twofold.</p><p>First of all, it should be noted that the “applicative nodes” that create only data transactions, being equal to any other node, help to provide consent to economic transactions. This is a unique advantage among crypto systems.</p><p>Secondly, being able to move data reliably over a public network without cost is exactly what happened in 1995 with the birth of the web. In that case the data was complex “content” and intended for human users. Today, recipients are among the billions of connected devices that can benefit from buying and selling data and services.</p><p>While the in the web, intended for human beings, is inevitable to reuse the same currencies that we use in the real world, in the “web of things” there is no reason to use Euro, Dollar or Swiss Franc. On the contrary, there is a very good reason not to do it.</p><p>The reason is that economic transactions made with payment systems designed for us humans have a very high cost, justified by the value of what we buy online and the ancillary services provided. But how much can information like “car engine temperature” be worth right now? Probably a few thousandths, or less. In addition, things, unlike humans, do not need additional features, such as credit or the cancellation of a transaction made by mistake.</p><p>Here then it is evident the usefulness of the token that, like the data, travels on the IOTA network at zero cost allowing to move value and complete micro business transactions.</p><p>At first glance it may seem like little stuff, but if only 10% of 3 trillion devices will need to buy and sell data or services, the token economy will explode.</p><p>So, a completely different approach, not in competition with other networks or even with traditional currencies, which has a very solid rationale derived from a new market that has a very high probability of birth.</p><p>I can then mention what will happen after the end of the “coordination”.</p><p>The dev team is already working to expand the IOTA protocol to support the specificities of the Qubic project.</p><p>So we have to expect further evolutions that will lead to new functional levels of the network with nodes able to perform smart contracts and produce consensus on data authenticity. In this case, since smartcontracts cannot have a predefined and limited cost, the nodes that will support them will get a reward. However, this is not a reward for participating in the network, but for making specific calculations and helping to give consensus to a specific Qubic transaction. A cost and a reward given not in competitive terms leading to a cost race.</p><p>Finally, we will see another step forward focused on giving each person and each device an identity. Today this issue is addressed and solved with a tool like our <a href="https://medium.com/things-lab/productid-2-0-60e1c5dbd9f3">ProductID</a>, but it is obviously impossible to imagine that every smallest device, every even insignificant object is equipped with a smartcard. The ideal solution is to have certainty of a person’s identity and to associate their “things” to their profile.</p><p>This is also a specific theme that, at network level, only IOTA has the goal to study and solve.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ae595217feba" width="1" height="1" alt=""><hr><p><a href="https://medium.com/things-lab/coodicide-is-coming-ae595217feba">Coodicide is coming</a> was originally published in <a href="https://medium.com/things-lab">Things Lab</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ProductID 2.0]]></title>
            <link>https://medium.com/things-lab/productid-2-0-60e1c5dbd9f3?source=rss----df3405b9c372---4</link>
            <guid isPermaLink="false">https://medium.com/p/60e1c5dbd9f3</guid>
            <category><![CDATA[iota]]></category>
            <category><![CDATA[industry-4-0]]></category>
            <category><![CDATA[tracking]]></category>
            <category><![CDATA[identification]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Stefano Della Valle]]></dc:creator>
            <pubDate>Wed, 08 Jan 2020 15:56:00 GMT</pubDate>
            <atom:updated>2020-01-08T15:56:00.621Z</atom:updated>
            <content:encoded><![CDATA[<h4>Development goes forward</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/333/1*-aU5kAQVP4_QqITEVgq9hA.png" /></figure><p>Six months after the initial launch of ProductID, we have obtained many confirmations of the importance and usefulness of such a tool in many industrial contexts.</p><p>We have therefore decided to invest and expand the functions of the system.</p><h3>ProductID’s Basics</h3><p>The main feature of ProductID is to provide an identification property of a generic object.</p><p>To grant a strong security level, the ID property provided by the system is dynamically generated each time the ID verification is needed, and it’s valid only for that specific verification request.</p><p>This procedure is very similar to an OTP (one time passcode or password), used as second authentication factor to log in to critical web pages.</p><p>Smart objects can be programmed to generate an OPT with various technologies, but how is it possible to provide an OTP tool to a <em>passive object</em>, to a <em>location</em>, or even to an <em>event</em>?</p><p>The solution we have adopted is to provide a generic object with a cryptographic smartcard, specially programmed for this purpose.</p><h3>The ProductID smart card</h3><p>An OTP code is produced using a factor that changes each time it is used. For example, the current time and date at the moment of the request. By applying a digital signature function to this factor, we get an always different signature, which is verifiable by anyone who knows the encryption key used.</p><p><strong>That’s exactly what our smartcard does.</strong></p><p>To allow the OTP code verification, the smartcard simulates the behavior of a NFC TAG by generating an URL. The URL is updated every time a NFC reader (for example a smartphone) activates the smartcard.</p><p>The URL provides an identification code assigned to the smartcard, an usage counter and a signature generated with an asymmetric key.</p><p>The website activated by the URL is able to validate the signature and certify the identity of the smartcard and what it represents.</p><h3>Ensure non-reusability</h3><p>The weak point of all identification systems is the possibility of cloning the security element. In our case, the security element is the private key securely generated and stored within the smartcard. It cannot be extracted to create a cloned smartcard.</p><p>However, it is possible to copy the entire URL which contains a valid signature.</p><p>To exclude that a valid signature can be used more than once, ProductID adopts a simple yet very robust solution: for each validation, the data contained in the URL is published onto the IOTA distributed ledger, using a <a href="https://docs.iota.org/docs/iota-js/0.1/mam/introduction/overview">MAM channel</a>.</p><p>The website that is activated to validate the signature, check the signature consistency and subsequently verifying that the signature has not been used previously.</p><h3>Avoid individual weak points</h3><p>The previously described architecture lacks most of the weaknesses of a typical authentication platform. In particular, the public key of each smartcard is published on the IOTA distributed ledger, and replicated on thousands of nodes. This prevents any attack that tries to change the key in ProductID central server to invalidate the smartcards.</p><p>In addition, the IOTA DLT consists of a network of public nodes, but no one can publish a valid transaction without knowing the seed of the smartcard-specific MAM channel. This ensures that cloned or tampered with cards can not be validated.</p><h3>Basic uses cases</h3><h4>Anti-counterfeiting of valuables</h4><p>This is the first and most basic use-case for ProductID: a smartcard is associated with an object, typically a valuable item.</p><p>By reading the smartcard, the validation website is activated. If the smartcard has produced a valid OTP code, the system redirects the browser to a web page that describes the product associated with the smartcard.</p><p>The destination page verifies that the access is made through a redirection managed by the validation site, and then displays the information related to the specific object. Otherwise it will display a generic page.</p><p>Since cloning the smartcard is not possible, this tool makes it possible to certify the uniqueness of the product associated with the smartcard.</p><p>The smartcard can be integrated into the object by providing a certificate of origin, or associated as a quality certificate. In both cases, a counterfeit product will lack this security add-on.</p><h4>Production process tracking</h4><p>Applying a smartcard to an object, even before it is produced, results in a precise tracking during the production process.</p><p>The functional logic is the same as the one of the anti-counterfeiting system, with an additional step: after validation of the OTP code produced by the card, the validation site requires the insertion (manual or automatic) of additional data related to the production phase.</p><p>It then publishes a validation message that also contains the production phase data obtained by the operator.</p><p>When the production process has been completed, a command is provided to the system, which will then be stored in the validation message. From that moment on, at each activation through the use of the smartcard, the validation site will no longer ask for additional information, but will allow the user to view the history of the production of the object associated with the smartcard.</p><h3>Advanced use cases</h3><h4>Proof of presence</h4><p>When a smartcard is installed on a wall or an indicator pole, ProductID can be used to certify the presence of a person in a specific place and time.</p><p>By activating the smartcard with a common smartphone, the user is prompted to identify themself.</p><p>By recording the successful validation of the OTP code produced by the card on the IOTA distributed ledger, the ProductID system also records the identity provided by the user. This information is not modifiable and can be obtained at any time using the unique code of the smartcard.</p><h4>Supply chain tracking</h4><p>This model provides the logical connection of events generated by different smartcards. In addition to the basic validation process, the system requires user identification (e.g. with a social network account login).</p><p>The process is simplified by using a specific web app. After the first login, the user does not need to log in again.</p><p>Each event (smarcard reading action) recorded on the IOTA DLT includes a link to the previous event. This makes it possible to record the sequence of activities carried out by an operator on a given batch that is being processed, and link to subsequent steps carried out by other operators.</p><p>Example of application in food production:</p><ul><li>the operator activates the smartcard installed on a sign identifying the place of the operation;</li><li>the operator collects a certain quantity of products and deposits them in a container (lot) equipped with a smartcard. They activate the smartcard and record the operation;</li><li>when the lot is complete another operator takes it over. They too activate the smartcard and record the operation;</li><li>the lot is moved and processed through various stages by various operators, who register their activity by activating the smartcard. They also recorded their presence on site by activating the specific smartcard installed in the facility;</li><li>the lot can be split into sublots. The operator who carries out the operation will activate the smartcards of each container;</li><li>at the end of the production process, finished product packages are produced with the production lot code embedded (in QRcode format).</li></ul><p>Reading the QRcode, it is possible to obtain the entire sequence of events that lead back to the collection of the raw material to a certain place.</p><h4>Smart actuators</h4><p>One of the most critical safety issues in the industrial world is the verification of the authorization of operators to use critical systems. Normally, an authorized operator has a simple key (mechanical or electronic) to enable the system. However, a key is a weak tool: it can be copied and used illegally or even temporarily transferred to another operator.</p><p>ProductID makes it possible to reduce these risk factors with the following approach:</p><ul><li>a smartcard provides the digital identity to the actuator;</li><li>the operator who wants to activate the system reads the smartcard and identifies themself;</li><li>identification must be carried out by a reliable system that discourages the operator from passing it on to a third party;</li><li>if the smartcard produces a valid OTP code, and the operator is actually authorized to operate on the device, the system sends an unlock command.</li></ul><p>The command can be made through the IOTA distributed ledger on a MAM channel dedicated to the device, or through third party communication systems.</p><h4>Smart devices’ ID</h4><p>The smartcard can be produced in various form factors. These include the classic SIM format.</p><p>In this case the ProductID smartcard can function as a security element providing various security functions.</p><p>For example, the smartcard can sign a challenge token sent by a system that requires the device to prove its identity.</p><p>The device uses the smartcard to close the token and returns it.</p><p>The central system is able obtain the device’s ID and the signed token, and can easily validate the signature and identify the device with certainty.</p><p>The public keys stored on the IOTA distributed ledger make the process easy and secure. It is also very easy to create a black list of devices that are no longer authorized.</p><h4>Identity of low-critical smart devices.</h4><p>In all cases where the device cannot interact with a smart card to obtain an OTP, it is still possible to use the ProductID backend system to validate the device’s identity with an acceptable level of security.</p><p>The device activation process is similar to the smartcard initialization: the central system creates a MAM channel for the device, and the device sends a public key to the central ProductID system that publishes it on to the IOTA distributed ledger.</p><p>The device registers its own public key along with company recorded data and messages. Anyone can validate a message using the unique device identity code provided by the system and the public key obtainable using the identity code.</p><p>In this scenario, the certainty of the identity of the device is entrusted to the ability of the device to keep its credentials confidential.</p><h4>Secure asset management and data quality validation</h4><p>Managing large fleets of IoT devices can be extremely complex. The IOTA DLT provides a very reliable layer to allow devices to publish data in an “unconnected” way with a central system.</p><p>This scenario distributes on thousands of nodes of the IOTA network, even private, the problem of the scalability of the platform. In fact, the recipients of this data do not need to turn to a central intermediary platform to obtain the data, but simply have to request it from their node, which will be sized according to their needs.</p><p>This very efficient approach also solves the problem of data reliability of devices that are doubtfully compliant with quality and safety policies.</p><p>The validation is simple:</p><ul><li>each device publishes data on an IOTA MAM channel whose starting address is the device’s unique ID provided by ProductID backend;</li><li>whenever a data consumer wants to validate the quality of data published by a device, they will use the identification code to obtain information on its operational status and revision level;</li><li>whenever a device is updated to a higher release, its profile can be updated by the ProductID server, or it can be assigned a new ID.</li></ul><h3>System API</h3><p>In designing the evolution of ProductID, we decided to extend the possibility of third parties to use the system more easily. A customer who wants to benefit from ProductID can request to have smartcards that activate their own URL. ProductID no longer mediates the interaction between user and web app.</p><p>However, the web app is not able to validate the data produced by the card itself. We have therefore set up a series of REST APIs that provide the web app with the necessary tools.</p><p>These are the first APIs available:</p><p>1) <strong>GET_CARD_INFO_FROM_MAM -</strong> by providing the card ID (parameter that the card inserts in the URL), ProductID accesses the restricted MAM channel and obtains the configuration parameters of the card; accesses the public MAM channel to obtain the data of the last reading and the possible association of the card and the associated device. Returns:</p><ul><li>the URL with which the card is associated, where for example it is possible to display product-specific information with which the card is associated;</li><li>the ID of an associated device if present;</li><li>the request to identify the user through a login before displaying data;</li><li>the last reading counter, information that allows you to understand if the reading that has been passed has already been used previously;</li><li>the public RSA key that allows you to validate the signature contained in the URL generated by the card.</li></ul><p>2)<strong> TAP_ACTION - </strong>by providing the entire URL generated by the card and a parameter that indicates the required action, the system performs two possible actions:</p><ul><li>if the parameter is “validate only” ProductID back end uses the URL provided and validates it - the card usage counter must be higher than the last one stored on the MAM and the digital signature must be validated with the public key retrived in the last published public MAM message. If the card is valid it returns a success message;</li><li>if the parameter is “update”, the back end validates the card-generated URL and records the data on the card’s public MAM channel, making the URL unusable a second time.<br>The user can also ask to include a PAYLOAD in the message. This field can be used to store application’s data together with the tap event data. If the card is valid and the writing operation has been successful, it returns the MAM channel ID where the data has been stored.</li></ul><p>We plan to publish other APIs making the ProductID system more transparent and easier to integrate with smartcards into critical applications.</p><h3>Conclusion</h3><p>The combination between the power of the IOTA network and the simplicity and security of ProductID cryptographic smartcards addresses many issues in a revolutionary and innovative way.</p><p>In comparison, current technologies are extremely expensive and insecure.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=60e1c5dbd9f3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/things-lab/productid-2-0-60e1c5dbd9f3">ProductID 2.0</a> was originally published in <a href="https://medium.com/things-lab">Things Lab</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[IOTA Smart Lock — Proof of Concept]]></title>
            <link>https://medium.com/things-lab/iota-smart-lock-proof-of-concept-6d3acdce5631?source=rss----df3405b9c372---4</link>
            <guid isPermaLink="false">https://medium.com/p/6d3acdce5631</guid>
            <category><![CDATA[iota]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[iot]]></category>
            <category><![CDATA[locks]]></category>
            <category><![CDATA[smart]]></category>
            <dc:creator><![CDATA[Stefano Della Valle]]></dc:creator>
            <pubDate>Tue, 10 Sep 2019 12:37:06 GMT</pubDate>
            <atom:updated>2019-09-10T12:37:06.103Z</atom:updated>
            <content:encoded><![CDATA[<h3>IOTA Smart Lock — Proof of Concept</h3><h4>Exploring the idea behind our upcoming new innovative solution</h4><p><strong><em>Note:</em></strong><em> this is a translation of a </em><a href="https://www.linkedin.com/pulse/iota-smart-lock-stefano-della-valle/"><em>post that was published on LinkedIn</em></a><em> in italian a few months ago. A prototype has been realized since then, we will soon release additional information about this solution.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5eYOyrGdLMpvmbSSmV_OMQ.jpeg" /></figure><p>Opening a lock is a very common action, and nowadays we perform it many times everyday without realizing how complex it is on many layers.</p><p>In time, locks and keys have become more and more sophisticated, especially in the digital era with electronic locks and digital keys.</p><h3>The “hidden” function of keys</h3><p>We are so used to using keys that we sometimes forget that they have two different functions:</p><ul><li>mechanically or electronically activate the lock;</li><li>granting the right and faculty to use the first function.</li></ul><p>The second function seems implicit, but it is not: if I find someone else’s lost key I can physically open its lock, but I don’t have the legal right to do so.</p><p>On the other hand, if I have guests in my home, I might give them the house keys, and at the same time I also explicitly give the permission to lock and unlock the door.</p><h3>Keys can be both strong and weak at the same time</h3><p>A perfect example of how a key/lock system can be very resilient to breaking but very weak when it comes to verify the usage authorization are “keyless” security systems of modern cars.</p><p>These systems work with a central unit in the car which identifies the key thanks to radio encrypted messages. It is impossible to clone the key and create alternative messages to unlock the car.</p><p>Just like mechanical keys, whoever holds the key can open the lock, but they don’t necessarily have the authorization to do so.</p><p>In addition, with these systems it is also possible to unlock the car even without physically holding the key and without using force: only two people and two transceivers are needed.<br>The first person follows the car’s owner, while the second person waits beside the car. The two transceiver create a radio bridge between the key and the car: the key receives the signal from the car and it activates. Car and key “think” they are in proximity and exchange information. The car unlocks and security systems are deactivated.</p><p>With this example, we can see how hard it is even with digital systems to fight potential unauthorized accesses, and how modern solutions end up creating even more attack opportunities. The real problem though is still the total absence of usage authorization control, which is practically impossible with legacy systems and still not completely solved with digital solutions.</p><h3>IOTA Smart Lock</h3><p>The goal of this project is to enable an authorization control process for digital keys, and we aim to accomplish it by separating the two functions of keys which we discussed above.</p><p><a href="https://medium.com/things-lab/productid-4c9c8a7cbb4">ProductID, our digital identity solution for objects</a>, can be successfully customized and adapted for this purpose, first of all solving the fundamental problem of establishing if a user trying to activate a lock is actually in physical proximity of the lock itself, and then checking if the user is authorized to use the key.</p><p><strong>Components of this solution:</strong></p><ul><li>any electronic lock;</li><li>any device able to run a IOTA client as a controller;</li><li>ProductID initialized smart card for the lock’s digital identity;</li><li>web front-end to identify the users;</li><li>back-end to elaborate the info gathered by the front-end and validate the user’s identity.</li></ul><p><strong>How it works:</strong></p><ul><li>the smart card is read with a smartphone and opens a web page of the ProductID front-end;</li><li>if the smart card is valid, the front-end redirects the browser to the Smart Lock front-end;</li><li>the Smart Lock fron-end analyzes the validity of the URL of provenience, and gets access to the ID of the smart card, which is connected to a list of authorized users;</li><li>the Smart Lock front-end gathers the parameters for the secure identification of the user (explained in the following paragraph);</li><li>the Smart Lock front-end forwards the identification parameters and, if the user is authorized, the back-end makes the controller open the lock.</li></ul><h3>User identification procedures</h3><p>The identification of the user who is trying to open a lock can be achieved with different degrees of security:</p><ul><li>UID + PIN code: this is the simplest and less secure method. If the user ID and the PIN code are in the authorization list, the identification is valid;</li><li>account with external AAA (Google, Facebook, LinkedIn, etc.): if the credentials used to log in are validated by the external server, the identification is valid;</li><li>account with external AAA + facial recognition: the front-end collects an image of the user’s face and the back-end checks with the one set during the configuration.</li></ul><h3>Attack resistance</h3><p>ProductID is resilient to replay attacks and the smart card can not be cloned.</p><p>Radio bridge attack is useless too. The ProductID smart card can be read also offline, but only for the proximity check (proof of location); in order to unlock the door, user credentials are also needed if the verification of the authorization is requested.</p><p>If we don’t consider coercion or the use of force to break the lock (which are possible attacks independently of the key), either the user offers a valid identification, or the system can not be tampered with or fooled.</p><h4>Development has been moving fast since the first publication of this document, we will soon release a more detailed report of our prototype for this solution, stay tuned!</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6d3acdce5631" width="1" height="1" alt=""><hr><p><a href="https://medium.com/things-lab/iota-smart-lock-proof-of-concept-6d3acdce5631">IOTA Smart Lock — Proof of Concept</a> was originally published in <a href="https://medium.com/things-lab">Things Lab</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Distributed Data Logger]]></title>
            <link>https://medium.com/things-lab/distributed-data-logger-50601ec45a1b?source=rss----df3405b9c372---4</link>
            <guid isPermaLink="false">https://medium.com/p/50601ec45a1b</guid>
            <category><![CDATA[data]]></category>
            <category><![CDATA[dlt]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[iota]]></category>
            <category><![CDATA[logging]]></category>
            <dc:creator><![CDATA[Stefano Della Valle]]></dc:creator>
            <pubDate>Wed, 28 Aug 2019 10:35:10 GMT</pubDate>
            <atom:updated>2019-08-28T11:06:22.821Z</atom:updated>
            <content:encoded><![CDATA[<h4>Advanced MAM explorer for Industry 4.0 applications</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x6ye-IvFNpfJMJE4taJ5Fg.png" /><figcaption>Graphic UI of the current DDL beta release</figcaption></figure><p><strong>Distributed Data Logger (DDL) was created with the purpose of extending and boosting the well-known Masked Authenticated Messaging (MAM) second IOTA layer, allowing a MAM channel reader to access additional features.</strong></p><p>More specifically a MAM channel has these properties:</p><p>- it can be read only starting from a known root id (the unique message identification number) up to the last message in the channel;</p><p>- it can be read only sequentially, because the fetch function, given a root id, returns one message, a requested number of messages, or all messages in the channel starting from that root;</p><p>- there is no way to know in advance how many messages are stored in a MAM channel from a given root id, without reading all the channel up to the last messages.</p><p><strong>These properties are not reducing MAM’s usefulness, but in some cases they are inconvenient.</strong></p><p>For example both MAM writer and receiver, communicating on a channel for a long time, need to store the root id of the last message exchanged safely, in order to be able to start again from that point if the system needs to be restarted losing the state.<br>In doing this, <strong>they lose the opportunity to retrieve all the messages older than the last one they have managed</strong>.</p><p>To solve this issue, the first root id of the channel can be stored too, allowing the parties to start from the end or from the beginning to retrieve some data from the channel.</p><p>But what happens if the channel contains thousands of messages?<br>The transmitter is able to skip all the channel’s content and restart from the last root id, but the receiver, who needs to retrieve a specific message in a time frame, needs to process all the channel from the beginning with a lot of effort.</p><p>We found it really unpractical, and that’s why <strong>we started searching for a way to not only speed up the search, but also filter it</strong>: this is basically how our Distributed Data Logger came to life.</p><h3>Features</h3><p>Distributed Data Logger looks like generic public MAM decoders and can actually decode a generic MAM channel like any other. If the messages in the channel (the MAM message payload) have a specific format however, DDL is able to provide some useful additional features.</p><p>The UI is pretty simple and intuitive. Distributed Data Logger lets you choose a provider (otherwise a default one will be used) and then asks you for the entity root (first root of your MAM).</p><p>Once you copy/paste the entity root id (the root id of a MAM channel produced by an entity) you only need to press the Tab and<strong> the tool will automatically check if your MAM has the right characteristics to unlock the advanced features and filters</strong>.</p><p>If not, you’ll still be able to use the standard fetch which is similar to the one of the MAM decoder</p><h3>How to enable the advanced features?</h3><p>The secret behind the boost is a simple JSON structure.</p><p>Every message published on the MAM will contain a field “count”, which basically represents its position in the MAM. Besides, starting from the first message, a field “prevRoot10” and “root10” will be added every 10 messages and will respectively contain the root of the 10th previous message and the root of the 10th following message.</p><p>Every 100 messages a “root100” field will be added (together with the two described above). Same goes for every 1000 messages with a field “root1000” containing the 1000th following root.</p><p><strong><em>Example:</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9ix1biRHqyniiknnYxqBTg.png" /></figure><p>Thanks to this approach and to specific algorithms it is possible to literally jump from one message to the other to get to the desired one in a considerably small amount of time.</p><p>In addition, the overload in term of message size is around 100 tryte every 10 messages, which is not a critical amount.</p><p>When messages contain the link to the other root in the channel, DDL is able to quickly find the last messages in the channel providing the channel dimension (in term of number of messages contained). Then it becomes simple to move backwards in the past messages or to ask DDL to retrieve messages from a specific sequence number.</p><p>Anyway the most interesting feature is the possibility to ask DDL to retrieve messages in a specific timeframe.</p><p>DDL is very fast in rolling such structured MAM channels thanks to a sophisticated implementation (dichotomic search for example).</p><p>Last but not least, DDL makes it possible to activate a “listen” feature to automatically retrieve messages from a channel in near real time</p><p>To try DDL, you can use this root id. The channel contains more than 7000 messages.</p><p><strong><em>Root id: “</em></strong>APBFWNCJWDCPINZDOXDJDXXQVLZARSOXCGL9QHDWSOCOPOODKDYZRGVFMMK9VPZKQSYKHXZZJMPZOBHTV”</p><h3>Use cases</h3><p>DDL can be useful in many cases where data needs to be distributed from a source to one or more receivers that would otherwise need to navigate the channel.</p><p>A typical case is an environmental sensor that publishes data which needs to be verified only in some specific conditions.</p><p>Another interesting use case is common in industrial environments. Industrial equipments are normally controlled by PCs that collect events from sensors to activate an actuator: these PCs keep their work history on local log files, and in case of trouble engineers need to remotely access those logs to identify the issue. This leads to two common situations:</p><ol><li>remote devices logs are accessible via internet (hopefully through a VPN);</li><li>remote devices are not accessible in any way from outside the local network due to security restrictions.</li></ol><p>In the first case engineers are allowed to access the remote device and solve the issue, but at the same time the whole remote network is exposed to unauthorized operations by the authorized engineers or someone else with their access credentials.</p><p>The second case appears to be more secure, but after engineers reach the device locally, they are again able to access the whole local network.</p><p>Hopefully the engineers are honest, but the risk of a fraudulent action on a critical industrial network can not be underestimated.</p><p>The simple solution to both these risky cases is to <strong>let the remote device write its logs on a DDL</strong>: engineers can access the logs in any moment without the need to access the remote network directly.</p><h3>Try the beta!</h3><blockquote><strong><em>The public beta version of DDL can be found </em></strong><a href="https://ddl.thingslab.network/"><strong><em>here</em></strong></a><strong><em>.</em><br><em>Keep in mind that, as a beta, it will most likely have many and even severe bugs, any feedback is very welcome!<br>Also, we are actively working on it and making improvements, so expect downtimes or slowness.</em></strong></blockquote><h3>Conclusion</h3><p>DDL is a great tool to improve IOTA’s standard MAM implementation, implemented only by adding a JSON structured information in the message payload, which remains perfectly compatible with any MAM reader and with standard libraries.</p><p><a href="https://github.com/thingswizard/ddlMessagePublisher"><strong>Here</strong></a><strong> </strong>you can find the sample code to write the messages in the JSON format described above.</p><p>We are obviously available to provide countless additional features, services and customization, just to name a few:</p><p>- customized DDL front-end;</p><p>- possibility to encrypt MAM messages with a side key to grant total privacy of the messages payload;</p><p>- adding an entity directory to allow to search the logs of many entities using an easier entity naming than the root id;</p><p>- fast IOTA node able to attach to tangle hundreds of MAM messages per second;</p><p>- private IOTA network for the users who need a totally controlled environment.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=50601ec45a1b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/things-lab/distributed-data-logger-50601ec45a1b">Distributed Data Logger</a> was originally published in <a href="https://medium.com/things-lab">Things Lab</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Physical asset exchange with IOTA]]></title>
            <link>https://medium.com/things-lab/physical-asset-exchange-with-iota-f68a2fc0989d?source=rss----df3405b9c372---4</link>
            <guid isPermaLink="false">https://medium.com/p/f68a2fc0989d</guid>
            <category><![CDATA[iota]]></category>
            <category><![CDATA[dlt]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Stefano Della Valle]]></dc:creator>
            <pubDate>Mon, 25 Mar 2019 13:11:20 GMT</pubDate>
            <atom:updated>2019-03-26T13:53:53.545Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*UTNJ8-hLQPXKWEJFWg3zuQ.jpeg" /></figure><p>DLTs (Distributed Ledger Technologies) are the latest evolution of the public register to designate the ownership of properties and assets since the Middle Ages.</p><p>While most of public registers record only the variation of the asset’s ownership, DLTs incorporate additional features:</p><p>- they can record the change of ownership of an asset;</p><p>- they can record the value of the asset;</p><p>- they manage the fund movement from the buyer to the seller.</p><p>These features are clearly visible in the Ethereum platform, where an ERC#721 token can change ownership recording the applied price and moving the funds.</p><p>Hence, I wondered: is it possible to create a marketplace of valuable physical products that provides the same features that Ethereum provides to a digital product?</p><p>The first answer that arises spontaneously is no. DLTs are able to guarantee consensus only on the DLT’s native information, i.e. the balance of a wallet at a given time.</p><p>In the absence of authority that certifies and above all guarantees (therefore commits itself to cover the damages in case of errors) the value of a balance registered outside the DLT in a given moment, it is not possible to reach consensus on the on-chain representation of the off-chain wallet (what happens, for example, with most stablecoins).</p><p>However, there is a category of real assets that have a particular property: by nature, they cannot be duplicated, or if duplicated do not lose value.</p><p>For example, a house is an asset that even if built identically in another place does not lose value. A piece of land cannot be duplicated. A livestock item, even if cloned, does not lose value, etc.</p><p>Even simpler products such as luxury goods are unique. Of course, it is possible to create a perfect fake or a very similar replica, but if there was a tool that could identify a specific product, then even this category of objects would not lose value in being cloned because the clone (and the original) would be easily recognizable.</p><p>In fact, there are countless reproductions of Leonardo’s Mona Lisa that have no ambition at all to be considered original. This sort of secondary market increases the value of the original because there are no dubs that a clone is a clone.</p><p><strong>The good news is that such a tool exists: it’s </strong><a href="https://medium.com/things-lab/productid-4c9c8a7cbb4"><strong>ProductID</strong></a><strong>.</strong></p><p><a href="https://medium.com/things-lab/productid-4c9c8a7cbb4">We presented ProductID to the market a few weeks ago</a>. In short, ProducID attributes to a physical object a unique digital identity recorded on the <a href="https://www.iota.org/">IOTA</a> ledger, the Tangle.</p><p><strong>At this point to the question “is it possible to create a marketplace of real goods that provide the same features that Ethereum provides to digital goods?” we can answer yes!</strong></p><h3>How the marketplace can be created</h3><p>ProductID uses a Smart Card to grant digital identity to objects and assets and uses an IOTA MAM (Masked Authenticated Message) channel to register the digital identity as a digital twin of the real product.</p><p>Once the twin exists in the IOTA ledger it is possible to manage it with the ledger functions.</p><p>In other words, we can create a digital market place of non-duplicable assets represented in the IOTA ledger.</p><p>The application environment requires:</p><p>- the owner of a valuable product or asset (wner identity can be provided by a third-party system);</p><p>- the digital twin of the asset created with ProductID;</p><p>- a potential buyer who intends to acquire ownership of the asset (identified through a third-party system).</p><p>The current state of the asset is recorded in a MAM channel. Each time the Smart Card is read a message is added to the channel with the essential data (the public key, the token usage counter, etc.) and the owner’s data (possibly in anonymous form but validated by a third-party system).</p><p>The MAM channel is written by the ProductID system’s back-end, that has been designed to be very versatile: in a basic use case it only writes a new message every time the tag is read and validated, but it is designed to also operate as an escrow too.</p><p>This can be the executive flow:</p><p>- buyer and seller negotiate the price;</p><p>- once an agreement has been reached the buyer sends the amount (in IOTA) to an address provided by the ProductID system;</p><p>- the owner can see the confirmed transaction on the IOTA ledger;</p><p>- the owner provides the tag to the buyer and informs the escrow;</p><p>- the buyer scans the tag to accept and commit the transaction;</p><p>- the transaction is completed and the ProductID back-end can deliver the fund to the seller’s wallet while updating the MAM channel recording the identity of the new owner.</p><p>The transaction moved the funds and traced both the new owner and the exchange price.</p><h3>Risks and vectors of attack</h3><p>Currently, the ProductID back-end is centralized, so it has the same risk factors of every centralized system, except one: it does not have a unique central database where critical information resides. All system’s information is stored on the IOTA ledger.</p><ul><li>Risks of cloning real estate properties are obviously non-existent, but clearly someone can create a digital twin of one fake or of a non-existent asset. This risk can be addressed in many ways. In my opinion, the best option is that is the digital identity have to be released by a public authority. A public notary service, for example, can create the digital twin and certify the existence of the real asset represented by the smart card. This information is recorded by ProductID system on the Ledger. After the Smart Card’s initialization by the authority, the asset is tradable on a digital marketplace without further involvement of the authority being required.</li><li>A manufacturer of valuable goods can try to deliver two original products on the market with a single digital twin. This risk is non-existent because one of the two product will miss the tag and it can’t be sold as original.</li><li>The owner of two assets tries to sell one with the tag of the other. This is possible but he is practically selling the asset with which the tag belongs to. In the first stage, the buyer can evaluate this attempt.</li><li>The risk that a fraudulent act will be executed from within the ProductID system is also practically non-existent. The system cannot generate digital signatures instead of tags. Therefore, it is not able to attribute the ownership of a digital twin to those who are not physically in possession of the tag itself.</li></ul><p>The system is, therefore, able to provide a high-quality escrow service. But we aim to decentralize the back-end anyway.</p><p>What if the buyer to not scan the tag in receiving it? the escrow will release the funds to the seller in any case after a specific amount of time.</p><p>What if the buyer wants to revoke the transaction? Within a specific amount of time, he can send the tag to the escrow platform. The escrow verifies the tag, ships it to the seller and sends the funds back to the buyer.</p><h3>Real world use cases</h3><p>The described scenario can be applied to many markets of valuable products.</p><p>Affirmed stakeholders such as auction houses and valuable products sales networks should evaluate this kind of service in order to increase the transparency of their operations.</p><p>In addition, the adoption of this tool may be requested by insurers in exchange for discounts on anti-theft premiums.</p><h3>Conclusion</h3><p>The token economy that developed on Ethereum in 2017 has given controversial results. The main issues are the poor performances of the Ethereum network and transaction fees and, in the end, the small number of users willing to use the service represented by these tokens.</p><p>However, the creation of digital non-fungible tokens representing real estate assets or valuable products does not create money out of thin air but can increase the security of trades and reduce the risk of frauds.</p><p>The use of a cryptographic Smart Card allows us to build an automatic escrow service even without a having smart contract.</p><p>This is possible because the smart card is able to confirm the Eecrow operation (change of ownership) by signing an event, so basically, it executes out of the DLT what the Smart Contract does internally, guaranteeing the consensus on the event.</p><p>The future availability of <a href="https://qubic.iota.org/">Qubic</a> should allow us to decentralize the ProductID back-end, thus achieving a perfect similarity with a smart contract on the Ethereum platform.</p><p>Therefore, ProductID is the perfect tool for creating innovative platforms that can create additional value in established markets.</p><p>It does not replace the notarial function, which is indeed essential to initially identify some assets and its initial owners and create the digital twins, but makes it possible to update the public register of valuable properties and creates a public exchange platform, which is missing at the moment.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f68a2fc0989d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/things-lab/physical-asset-exchange-with-iota-f68a2fc0989d">Physical asset exchange with IOTA</a> was originally published in <a href="https://medium.com/things-lab">Things Lab</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Private blockchains vs. public blockchains]]></title>
            <link>https://medium.com/things-lab/private-blockchains-vs-public-blockchains-b7dae667a197?source=rss----df3405b9c372---4</link>
            <guid isPermaLink="false">https://medium.com/p/b7dae667a197</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[dlt]]></category>
            <category><![CDATA[private-blockchain]]></category>
            <category><![CDATA[distributed-ledgers]]></category>
            <category><![CDATA[iota]]></category>
            <dc:creator><![CDATA[Stefano Della Valle]]></dc:creator>
            <pubDate>Mon, 18 Mar 2019 16:40:55 GMT</pubDate>
            <atom:updated>2019-03-20T12:38:36.791Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*GTsPvgyGC__kncVuowibMQ.jpeg" /></figure><p>First of all, I would like to point out that the word “blockchain” refers to the data structure that can store the information that in a monetary exchange system are called “ transactions”. This is why the blockchain has become synonymous with ledger.</p><p>Second, it must be explained that the reason a blockchain is a preferred choice over a database is because linking transactions in blocks and linking blocks between them creates a computational difficulty to an attempt to modify the data.</p><p>In a traditional database, the impediment to modify a data is dependent on the performance of the host machine’s operating system which is, of course, prone to attacks in many ways.</p><h3><strong>Distributed consensus</strong></h3><p>As demanding as it may be, modifying a blockchain is not impossible.</p><p>For this reason, a network of nodes has been created to replicate the blockchain and to produce a “distributed consensus” on its validity.</p><p>Distributed consensus is a way to combine the opinion of multiple independent subjects and guarantee certainty.</p><p>It could be defined as a democratic process of signing the statement “the data contained in our copies of the blockchain is authentic”.</p><p>As for a law that in the democracy is valid for all, if the majority agrees on the validity of the blockchain then the blockchain is valid for all.</p><h3><strong>Creation of the distributed network</strong></h3><p>The advantage of having many copies of the blockchain is obvious, however, supporting a replica of the blockchain has a cost. If we want many nodes to be activated, we need to provide them with an incentive that exceeds the costs.</p><p>Since it is not possible to remunerate all the nodes, a race is carried out for each block. The fastest node able to validate a block is assigned with a remuneration. In addition, it gets the transactions fees.</p><p>This is why a public blockchain can have a large number of nodes.</p><p>The larger the number of nodes, the greater the distributed consensus on the replicated blockchain is and the more difficult it is to create a valid distributed blockchain that was tampered with.</p><h3><strong>What is a private blockchain?</strong></h3><p>The nodes of a public network are:</p><p>- uncontrolled: there is no node management center</p><p>- not forced to operate: they can interrupt their calculation at any time.</p><p>- unauthorized: they participate in the network without asking someone for permission.</p><p>Equivalently, the nodes of a private network are or can be:</p><p>- controlled: they can belong to a company that manages them;</p><p>- authorized: only an authorized node can enter the network and manage transactions.</p><p>So we can say that a privately distributed blockchain is equal to a publicly distributed blockchain (as a matter of fact you can use the same software) and the only difference is in the organization of the nodes.</p><h3><strong>Pros and cons of blockchains</strong></h3><p><strong><em>Issues on consensus</em></strong></p><p>It is clear that without a large number of nodes a public blockchain is easily attackable: a few nodes can become the majority and confirm invalid blocks.</p><p>Therefore, small public networks cannot produce a strong consensus on their blockchain.</p><p>Since a private network is not open, an external attack is not possible. However, it is possible for an internal attack to occur, organized by the node managers or coordinated by the company that controls them.</p><p>Secondly, a private network is comparable to a small public network. In both cases, the consensus on the ledger is very poor.</p><p>One could say that consensus on a private network is not necessary because you trust those who use it. If distributed consensus is not required, why use a complex technology instead of a simple database, delegating to a database manager the task of managing its content?</p><p><strong><em>Effect on the token value</em></strong></p><p>If the ledger is attackable then its content is not safe. Therefore, the value represented in the ledger (the sum of the balance of every address) is not safe.</p><p>This is the reason why the value of the token managed on a blockchain with a small public network cannot be high. The risk of loss is too high for big money investments to make sense.</p><p>Of course, a private blockchain can be used to log transactions of any token.</p><p>The problem is: who will have enough trust to invest in a token managed by a company on a private blockchain system?</p><p>The answer is twofold:</p><p>- if the company is unknown, no one will ever trust it;</p><p>- if the company is well known and appreciated, certainly many will invest in its tokens as many would invest in its shares.</p><p>It remains to be seen why this company should use a private blockchain instead of a widely used and reliable payment system or, in the case, a simple database.</p><p><strong><em>Privacy</em></strong></p><p>If you need to manage data and transactions in absolute privacy you must choose between two options:</p><p>- use a public blockchain encrypting transactions so as to make them understandable only to those who have been authorized;</p><p>- to use a private blockchain.</p><p>However, it should be noted that it is not necessary to be able to decipher a transaction in order to verify that it has not been altered.</p><p>Therefore, encrypted transactions on public blockchain can have a high consensus. While transactions on a private blockchain, encrypted or not, will never have it.</p><p><strong><em>Performance</em></strong></p><p>Public blockchains can’t be fast. At least not those that are based on Proof of Work.</p><p>The faster the block generation and bigger the blocks are, the lower becomes the number of nodes that can compete on a block. The risk of a coordinated attack increases proportionally.</p><p>So if you want performance is good to think of a private blockchain. Although, if you need a certain performance, why use a blockchain?</p><p><strong><em>Service Level Agreement</em></strong></p><p>If you are planning a business model based on a public blockchain, you need to know that no one will ever give you a service level agreement. Costs, performance and reliability are not predefined and cannot be controlled. Reliability depends on the behavior of the nodes operating according to economic interest. Greater economic advantage results in increased costs and/or reduced performance.</p><p>So, if you need a service level agreement you probably have to use a private blockchain.</p><p>But once again I wonder why you would use a private blockchain if you need to control costs and performance. A database is definitely more performing and easier to manage.</p><p><strong><em>Governance</em></strong></p><p>One of the strengths of a public blockchain is the system of governance. If the number of nodes is high enough, the blockchain and the token it manages acquire value. This rewards the contribution of a large distributed organisation working to improve the platform.</p><p>The same obviously cannot happen in a private blockchain. On the contrary, in a consortium of companies sharing a private blockchain, it is easy to find one who actually coordinates the whole system. Over time, consortium participants may change or no longer be interested in that tool.</p><p>The risks inthis scenario arevery high: the persistence of the blockchain can be compromised by the disappearance of the interest of some partners.</p><h3>PoS vs. PoW</h3><p>I have analyzed the advantages and disadvantages of public vs. private blockchains by referring to blockchains with a Proof of Work based mining process.</p><p>Someone might dispute that with the Proof of Stake system things would be very different, to the full benefit of the public blockchain. I think it doesn’t change much at all.</p><p>A PoS system is based on the risk of losing capital. Instead of investing in powerful mining systems, in a PoS system, a validator node immobilizes a capital that is lost if it does not behave properly.</p><p>The PoS in a private blockchain does not make sense.</p><p>On a public blockchain it has only one significant effect: the performance can be high because the validation of the block does not require heavy computations. The rest (privacy, service level agreement, etc.) remains unchanged.</p><p>In addition, PoS has its own flaws: the number of validators is theoretically unlimited and with various methods you can avoid centralization on a few validators. However, the number of validators can be very small compared to the total number of users. In fact, in a still nascent market, the value of the token can fluctuate a lot. The reward for having immobilized the capital does not encourage those owners who have the ability to speculate on the market earning much more in the presence of volatility.</p><p>This scenario is currently very present and I think it will be for a long time, creating dangerous scenarios of centralization.</p><h3>IOTA, a special case.</h3><p>I conclude this roundup of pros and cons on the blockchain with positive news: there is an alternative.</p><p>IOTA doesn’t use the blockchain, but that’s an unimportant detail.</p><p>The interesting thing is that there is no mining and therefore there are no fees, rewards and validator nodes. Network management is cooperative.</p><blockquote><strong><em>The practical effect is that owning a IOTA node is simple and cheap. It is quite similar to owning and managing a database. With IOTA it is then possible to obtain a perfect compromise between a public network with data replication on thousands of other nodes and private network with costs, performance and reliability guaranteed by our node (or by a group of our nodes).</em></strong></blockquote><p>This is why we mostly base our projects on IOTA instead of using private or public blockchains.</p><h3>Conclusion</h3><p>My opinion is simple: private blockchains grant lot of advantages vs. public ones only for those projects that do not require a distributed consensus.</p><p>The absence of distributed consensus is a common attribute of many contemporary platforms. The modification or deletion of data or the presence of false data on portals such as Facebook, AirBnB or TripAdvisor is normal. No wonder either. So if you’re planning on creating an old-fashioned platform, a private blockchain might be a good choice.</p><p><strong>But the value of distributed consensus is immense and it is essential to emerge from the normality of contemporary solutions. Leveraging distributed consensus means taking a leap forward and achieving the level of reliability that the big names in the industry have taken decades to build.</strong></p><p>I think choosing a private blockchain is a missed opportunity to make that leap.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b7dae667a197" width="1" height="1" alt=""><hr><p><a href="https://medium.com/things-lab/private-blockchains-vs-public-blockchains-b7dae667a197">Private blockchains vs. public blockchains</a> was originally published in <a href="https://medium.com/things-lab">Things Lab</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[TrackingID]]></title>
            <link>https://medium.com/things-lab/trackingid-3694a2643062?source=rss----df3405b9c372---4</link>
            <guid isPermaLink="false">https://medium.com/p/3694a2643062</guid>
            <category><![CDATA[dlt]]></category>
            <category><![CDATA[supply-chain]]></category>
            <category><![CDATA[iota]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[tracking]]></category>
            <dc:creator><![CDATA[Gabriela Gambarini]]></dc:creator>
            <pubDate>Wed, 13 Mar 2019 14:04:33 GMT</pubDate>
            <atom:updated>2019-03-13T16:57:21.214Z</atom:updated>
            <content:encoded><![CDATA[<h4>A ProductID-based solution for supply chain tracking and ownership management</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/995/1*HZFvJPX-8WeyfIXDcISAFg.png" /><figcaption>TrackingID login page in our current prototype</figcaption></figure><h4>Introduction</h4><p><strong>Tracking specific information</strong> regarding a product can be a very<strong> difficult task</strong> considering how big and complex supply chains have become. Most of today’s supply chain still operates with <strong>paper documents and archaic processes</strong> that slow down international trade and cause a <strong>negative impact on the economy</strong>. The legitimacy of the data is trusted to the person who recorded it, leaving much to human error.</p><p>Even if this information is digitalized, each different entity has its own preferred software and forms in which the original data can be modified, shortened and even excluded of parts that they would consider unimportant. This data is forwarded down the supply chain making it very <strong>difficult to track back certain information</strong> regarding a product or a process.</p><p><a href="https://www.cdc.gov/ecoli/2018-outbreaks.html">The 2018 E. Coli outbreak in the United States and Canada</a> has been associated with the consumption of romaine lettuce and ground beef. The CDC has advised consumers and food establishments to avoid the consumption of the lettuce until more information about the outbreak source becomes available. The lack of transparency regarding where the products have been and how they were handled makes it hard to find where it all went wrong. While the investigation happened, the producer suffers from the cut on sells.</p><h4><strong>The solution</strong></h4><p>Having developed a revolutionary technology for the identification and anti-counterfeiting of objects (<a href="https://medium.com/p/4c9c8a7cbb4/edit">ProductID</a>), we can <strong>go further and create a product tracking platform that can be integrated in virtually any existing supply chain</strong>.</p><p>Distributed Ledger Technologies (DLT) and Identity of Things are the tools that can be implemented on the supply chain to make it <strong>more productive and transparent</strong>. By associating each product with an identifier, such as a crypto Smart Card, one can collect all the essential information regarding the product and then publish it on a distributed ledger (the <a href="https://www.iota.org/">IOTA Tangle</a> in our case), so that in every step of the processit is possible to have direct access to the original data and its history. The information regarding the product’s location and status will be fetched in real time with guaranteed integrity.</p><p><strong>By using a DLT protocol, the amount of time that it takes to track for example a food item back to its source would be reduced to seconds, as compared to days or even weeks.</strong></p><p>Things Lab’s TrackingID uses cryptographic smart cards that can publish on the IOTA distributed ledger. Those smart cards are attached to products and batches that will be transported.</p><p>When the product is ready and out for transportation, <strong>the manufacturer will read the card using any NFC reader</strong>, including his smartphone, and will log in to its personalized manufacturer’s webpage. There, he can fill his specific form which displays whatever parameter he wants to add along with the product’s geographic location. The card will publish this information on the IOTA ledger and there it will be stored.</p><p>Each future step (transportation, wholesaler, inventory etc) will have a different form relevant to its own step when the card is read. <strong>The history of the product will keep being updated and can be accessed by all the authorized parts</strong>. When it arrives at the consumer, they can also use their own smartphone to access it.</p><p><strong>The validity of the smart card is guaranteed by its private key</strong> that produces a digital signature. Whenever the card is read, it increases its personal internal counter that along with the private key creates a dynamic signature for each counter. This counter and signature are published on the product’s MAM channel so Tracking ID can access that data and compare the signature with its respective index.</p><p>The private key is stored on the card’s own internal secure memory, thus it cannot be copied. In case of the card being cloned, it would only possess a static signature, therefore, the index associated with that signature will be equal or lower than the last one stored on the IOTA ledger proving that the card is a copy.</p><h4><strong>How it works</strong></h4><ul><li>The card is read and verified then, its dynamic URL redirects the user to Tracking ID’s webpage where the user will login on his specific stage and will visualize his own form;</li><li>the user fills his personalized form and publishes it on the Tangle with the product’s geographic location;</li><li>when the product arrives at the following step, the next user will perform the same operation. The user can only access the forms when the previous stage form has been published. For example, a wholesaler will not be able to publish anything until the transportation company has read the card and publish the form proving that the product has arrived;</li><li>when the product arrives at the consumer, it can scan the card using his smartphone’s NFC reader and check all the published history.</li></ul><p>In the case of more valuable products such as wine, certain pharmaceuticals, luxury bags, etc. the Smart Card will be inserted on each individual product. However, for lower value products, a smart card would be inserted on the products batches, containing a higher quantity of products. The tracking system would work the same way for the batch but each individual product would have a QR code. Those QR codes will be linked to the batch and upon reading would show the last batch location and notify if the location where the consumer got the product is suspiciously far from the batch’s final selling venue.</p><h4><strong>Potential applications</strong></h4><p>This system can be used to track goods even in remote areas (oceans, for example) displaying also information regarding the shipment sensors. Food security can also be improved by having access to producers and transport data (where it was cultivated, the temperature and humidity during transport, etc). The pharmaceutical supply chain can be tracked so that only EMA approved drugs arrive at hospital and pharmacies guaranteeing also that none of the dangerous drugs escapes from the supply chain.</p><h4><strong>Use case example</strong></h4><p>A pharmaceutical manufacturer produces drugs of different values. One of the most expensive drugs that they produce has an important counterfeit problem. The manufacturer inserts a smart-card inside each individual package. For more common medications, the card is inserted on a batch of packages, which each possess a QR code associated with the batch’s card.</p><p>The manufacturer initializes the card and publishes the data to the tangle. The drugs will be transported and each time the distributor goes through customs he will update the tracking history of the cargo.</p><p>A wholesaler that is waiting for the pharmaceuticals logs on its webpage and checks the last published location. When the cargo arrives, first the wholesaler checks the validity of the medication by reading the cards and verifying that they are the actual cards that have been updating the channel. He then fills his form and sends the products to its selling points.</p><p>A medications batch is then sent to the pharmacy where all its history is again checked and updated. The consumer uses its own smartphone NFC reader to verify the single drug smart-card and with the QR code, it can see all the history of the batch that the box was part of, until the pharmacy. The only way for falsification to occur would be from the part of the pharmacy. All of this data was fetched from the IOTA ledger by the Tracking ID’s front-end and kept available in a single webpage.</p><p>Other entities can benefit from the process, even if they are not directly involved in the supply chain: in our example it would be invaluable for a health insurance provider to have access to the recorded data, in order to receive additional information about everything that happened (where the drug was, which drug the consumer bough and where, and then consumed) to discourage and filter out fake claims.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3694a2643062" width="1" height="1" alt=""><hr><p><a href="https://medium.com/things-lab/trackingid-3694a2643062">TrackingID</a> was originally published in <a href="https://medium.com/things-lab">Things Lab</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ProductID]]></title>
            <link>https://medium.com/things-lab/productid-4c9c8a7cbb4?source=rss----df3405b9c372---4</link>
            <guid isPermaLink="false">https://medium.com/p/4c9c8a7cbb4</guid>
            <category><![CDATA[supply-chain]]></category>
            <category><![CDATA[anti-counterfeit]]></category>
            <category><![CDATA[iot]]></category>
            <category><![CDATA[iota]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Stefano Della Valle]]></dc:creator>
            <pubDate>Tue, 05 Mar 2019 17:27:17 GMT</pubDate>
            <atom:updated>2019-03-13T13:25:50.371Z</atom:updated>
            <content:encoded><![CDATA[<h4>A solution for the identification and anti-counterfeiting of products</h4><h4><em>Edit: why IOTA?</em></h4><p><em>I have been asked to explain why we use IOTA for this solution. The answer is simple: </em><strong><em>IOTA is currently the only distributed ledger that lets us create professional applications with direct control over cost, performance and reliability</em></strong><em>. The resulting efficiency does not depend on the network usage level, nor is it affected by variable costs deriving from the transactions fees, and at the same time the data is replicated, made immutable in the process, on all the other nodes of the network. A perfect combination of control over a private node and resilience of a public network.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8wwzUpiWOMhBAEu7bv5_fw.jpeg" /><figcaption>Our hardware prototype of ProductID, an IOTA-based crypto Smart Card</figcaption></figure><h4>Introduction</h4><p>The evaluation of the origin of a product, i.e. the identity of its manufacturer, is an important matter for many industrial and commercial sectors.</p><p><strong>Preventing the illicit exploitation of established brands, </strong>which would otherwise suffer a loss of market share and profit, is not the only objective of anti-counterfeiting. Even more important is to <strong>protect the final purchaser</strong> who expects to buy an original product, conform to the quality specifications necessary for its given purpose. The <strong>supply chain is another process affected</strong> and often exploited for the production and distribution of fake products.</p><p>The counterfeit product, intended to be sold on illegitimate business, is typically made with inferior materials and significantly lower quality of assembly compared to the original. However, these features are <strong>difficult to determine</strong> by the final consumer or by the trader who receives a proposal from a wholesaler.</p><p>The solution to the problem has always been based on the addition of distinctive elements on the product that are clearly visible and difficult to replicate. In short, <strong>the strategy is to make the replication of that product expensive</strong>. However, this approach has lost its effectiveness due to the <strong>increased availability and cost reduction of industrial printers and technological devices</strong> needed to reproduce labels, holograms, RFID tags, and other elements that would be attached to the final product to make it distinguishable. <strong>This is why manufacturers no longer adopt expensive solutions that may shortly become ineffective</strong>.</p><p>This said, in a totally different field (digital documents production) the counterfeiting issue has been completely solved with solutions based on digital encryption: the <strong>digital signature</strong> of documents (digital) and e-mail messages (certified mail).</p><p><strong>The digital signature of e-mails and documents is costly, but since the volume of “signatureable” objects is very high, a low cost per signature is achieved.</strong></p><p>The technology on which the digital signature is based is now virtually inviolable.</p><p><strong>The idea behind our solution is simple: offer to every industrial and commercial sector the same level of security provided by the solutions of digital signature or certified mail.</strong></p><h4>The digital signature system</h4><p>Digital signatures are based on a series of technical and organizational elements that are not easily replicable in a generic context:</p><ul><li>the signature is produced with an asymmetric encryption algorithm, so without the private key it is not possible to create a valid signature;</li><li>the public key is inserted in a certificate stored on a public server. Anyone can obtain the certificate and therefore the public key to confirm the validation of the signature;</li><li>the private key is produced and stored on a device capable of creating the signature. The private key is therefore never exposed so it is not clonable.</li></ul><p>The organizational part of this system is <strong>too complex to validate a generic product</strong>, especially in the case of popular and low-cost items. However, the general scheme remains valid and has a superior effectiveness compared to simpler solutions because it raises the costs necessary to obtain a credible falsification.</p><h4>ProductID Security Strategy</h4><p>The security level of our ProdutctID solution is based on a series of measures that produce the <strong>same level of security as the digital signature, but with lower operating costs</strong>:</p><ul><li>use of electronic signature algorithms with an asymmetric key;</li><li>use of cryptographic tokens similar to those used for digital signatures;</li><li>decentralized public key repositories.</li></ul><h4>Key publication system</h4><p>Unlike the system used for the signature and certified mail, <strong>ProductID does not use a centralized storage controlled by an institution or a company</strong>: the keys are stored in a registry that is distributed, unalterable, replicated on hundreds of servers and accessible to the public without intermediaries.</p><p><strong>This reduces the operating cost of the system since the security of the public key container is intrinsic to the public register (IOTA in this case).</strong></p><h4>Signature validation system</h4><p>The process of validating a signature (therefore a token) is carried out by a web front end, therefore it is not necessary to create a specific app.</p><p><strong>The web front end is also distributed: the code is stored on the same distributed ledger where the public keys are stored. This prevents any possible attack on the validation server code that would make the entire security architecture ineffective.</strong></p><h4>Token validation</h4><p>The token used for the digital signature creates the signature by receiving data from an application. This element, besides being a cost, is also a potential point of attack. In the ProductID system, in most cases, an app is not required. The token generates a signature using a variable factor (the number of times the token has been read). The signature and the variable factor are stored in the register at each reading. This makes the signature only valid for a given factor and prevents that factor from being used twice.</p><p>The writing operation is currently performed by a centralized server managed by Things Lab. This is the only point of centralization of the security system but <strong>its decentralization is predicted by the end of 2019 due to functional components of the IOTA system</strong>.</p><h4>Visualization of product data</h4><p>Once the Smart Card has been validated, the verification web page is able to redirect the browser to the original product page of the brand owner’s website. The site can validate the request in two ways:</p><ul><li>validating on its own the signature passed as a parameter;</li><li>accepting the redirect only if it comes from the ProductID site.</li></ul><p>This means that<strong> product-specific data cannot be accessed without a valid and validated token</strong>.</p><h4>Traceability</h4><p>The use of the Smart Card to validate the property of a good or a product is only a simple case of traceability.</p><p>ProductID is designed to manage the validation of a product through the registration of the validation factor produced by the Smart Card (user counter plus the signature with asymmetric key). Since the security container does not limit the amount or the type of data stored, the <strong>writing of metadata is also automatically supported</strong> as the card is read.</p><p>A practical tracking example of the manufacturing steps:</p><ul><li>the product enters a processing facility;</li><li>the smartcard is read and validated.</li></ul><p>The validation web front end redirects it to a tracking web page:</p><ul><li>using the card’s number as a parameter, the page identifies in which processing phase the product is;</li><li>the page presents a form that the operator has to fill in;</li><li>when the operator confirms, the tracking page asks the back-end to write the data on the register;</li><li>the back-end validates the request and publishes the data.</li></ul><p>When leaving the processing facility, the sequence is repeated with its appropriate form.</p><p>If trust is a sensitive factor in the process, in the second and third steps the human operator can be replaced for the input by certified sensors (i.e. genomic sensor to determine the type and origin of a substance) or by independent oracles (even with a distributed consensus, for example using <a href="https://qubic.iota.org/">IOTA’s Qubic</a> in the near future) that are able to collect information from external sources.</p><h3>Comparing with other common solutions</h3><h4>Label with QR code</h4><p>QR codes can contain a variety of information. To allow the identification of a product, the QR code must contain an URL that makes it possible to activate a web page by passing a unique identification code.</p><p>The solution based on QR code is<strong> limited by its static nature</strong>: if not inserted in a package or protected by a “scratchable” film, the QR code can easily be copied and applied to a fake product.</p><p>Moreover, if the product data were publicly verifiable, it would be easy to create false QR codes that would correctly activate the validation server. <strong>This solution is therefore only possible with a fully centralized and protected system</strong>. This reduces the level of trust in the certification provided and produces hidden costs related to the need to protect and maintain a centralized server.</p><h4>NFC TAG</h4><p>NFC technology allows the creation of tags that can interact with a radio reading device at close range (Near Field Communication).</p><p>NFC technology is very versatile, but not all electronic labels are the same.</p><p>The most common NFC tags are simple memories (e.g. tags based on NXP NTAG213/215/216 chips). If used to open a validation webpage, no advantage over the QR code would be offered. <strong>They are widely available on the market and can be written with a simple mobile phone. Cloned tags are identifiable only with tools that require specific expertise.</strong></p><p>More sophisticated tags are able to do a minimum of processing and produce a signature.</p><p>Just like ProductID, the signature given as a parameter to a web server is based on an usage counter, so it changes every time the tag is read.</p><p>This approach is much more resistant to counterfeiting as it is not possible to extract from the original tag the key used to make the digital signature, and therefore an invalid tag will never produce a valid signature. However, this approach has an important limit: to contain the cost of producing the tag, a symmetrical signature algorithm is used, which means that the key used to sign is the same that must be used to verify the signature. <strong>This implies that the key cannot be published and therefore the verification must be performed by a centralized server that stores it</strong>.</p><p>The cost to protect the server from attacks is a critical factor. But <strong>even with a high level of protection from external attacks, the centralized server is always subject to risks of internal attacks</strong>: any violation of this server would result in the loss of security of all valid tags.</p><h4>Non-digital or hybrid solutions</h4><p>Some manufacturers have proposed “analog” solutions to produce labels that are easy to read by an optical scanner but not as easy to reproduce thanks to a fairly complex production process.</p><p>The same approach is being studied to produce digital tags. The identification code is derived from the physical uniqueness of the chip.</p><p>These strategies are certainly advantageous because they are cheap and currently complex to violate, but their effectiveness is limited by the need to use specific apps or readers.</p><h4>Comparative analysis of traditional signatured-based systems vs. ProductID</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/777/1*Z3PrSpWnAZisSc5UlOGwew.png" /></figure><p>In general, you can notice that the ProductID solution is not unlike other well-known and secure digital signature systems, but it is <strong>much safer</strong> in comparison to a low-cost system based on symmetric cryptography, especially in the long term.</p><p><strong>The use of IOTA</strong> as public ledger, shared among hundreds of nodes and dozens of permanodes, makes it <strong>impossible to tamper with the public key and dramatically decreases the security management costs</strong>.</p><h4>Low-cost hybrid solution</h4><p>The ProductID system offers the top security amongst the anti-counterfeit systems: however, the Smart Cart cost makes it convenient only to protect high-cost products.</p><p>A hybrid system is proposed to protect low-cost products:</p><ul><li>a Smart Card is used to identify a batch of a specific product;</li><li>each batch is distributed as a unit to the dealer/distributor/reseller. The reading of the Smart Card combined with the arrival of the batch to the location where it is separated into individual products creates a geographic point of reference;</li><li>each individual product contains a QR code that was previously associated with the Smart Card.</li></ul><p>When the final consumer scans the QR code, they will see the information associated with the batch and the sales location where the batch was intended to arrive.</p><p>The same web page is able to inform the client of a possible fraud if the sales point is too distant from the official destination point of the batch</p><h4>Proof of ownership</h4><p>The life of the Smart Card is virtually unlimited. This fact, associated with the equally unlimited availability over time of the IOTA distributed ledger on special nodes (permanodes) makes it possible to attribute an additional meaning to the token associated with valuable products.</p><p>It is easy to add a reference to the product owner’s identity to transform the token itself into a proof of the ownership of the product.</p><h4>Residual risks</h4><p>Decentralization combined with digital signature techniques makes it virtually impossible to breach the system’s security.</p><p><strong>The only possibility left to a counterfeiter is to create an entire fake chain of products, tokens that simulate the ProductID Smart Card and a website that simulates the one of the original manufacturer.</strong></p><p><strong>This risk is not manageable with the technology of the digital signature token, but there are many tools to protect consumers from fraud carried out via email or fake websites similar to the real ones (phishing). Therefore this risk is also easily manageable.</strong></p><h4>Conclusions</h4><p>ProductID is the top solution for security, anti-counterfeiting, tracking and ownership management of valuable products and critical components that need to be identified with certainty. <strong>The adoption of Smart Cards in conjunction with the IOTA technology produces the best price/security ratio on the market.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4c9c8a7cbb4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/things-lab/productid-4c9c8a7cbb4">ProductID</a> was originally published in <a href="https://medium.com/things-lab">Things Lab</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>