<?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[Stories by Niels Klomp on Medium]]></title>
        <description><![CDATA[Stories by Niels Klomp on Medium]]></description>
        <link>https://medium.com/@niels.klomp?source=rss-1af481e54512------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*SjkgtJwMv3bto0GuqZypOA.jpeg</url>
            <title>Stories by Niels Klomp on Medium</title>
            <link>https://medium.com/@niels.klomp?source=rss-1af481e54512------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 02:33:21 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@niels.klomp/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[A distributed verifiable censorship resistent e-mail service on top of Factom!]]></title>
            <link>https://medium.com/swlh/a-distributed-verifiable-censorship-resistent-e-mail-service-on-top-of-factom-9c32fc511672?source=rss-1af481e54512------2</link>
            <guid isPermaLink="false">https://medium.com/p/9c32fc511672</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[identity]]></category>
            <category><![CDATA[factom]]></category>
            <category><![CDATA[email]]></category>
            <category><![CDATA[decentralization]]></category>
            <dc:creator><![CDATA[Niels Klomp]]></dc:creator>
            <pubDate>Wed, 04 Mar 2020 00:24:59 GMT</pubDate>
            <atom:updated>2020-03-04T00:34:11.030Z</atom:updated>
            <content:encoded><![CDATA[<p>A lot of people have asked me over time what <a href="https://factomprotocol.org/">Factom</a> and it&#39;s related technologies like <a href="https://www.fatprotocol.org/">FAT</a>, <a href="https://pegnet.org/">PegNet</a> are and how W3C standards like Decentralized Identifiers and Verifiable Credentials fit in. Recently whilst discussing a proposal of a technical community member about creating another token to combine some work which is already present or almost ready in <a href="https://factomprotocol.org/">Factom</a>, it became clear to me that I need to write more for people to get what the Factom Protocol is about.</p><p>At <a href="https://sphereon.com/">Sphereon</a> we have a long term vision for both <a href="https://sphereon.com/">Sphereon</a>, it&#39;s partners, the <a href="https://factomprotocol.org/">Factom Protocol</a> and it&#39;s use cases. Since we cannot disclose everything at this point in time, let me just grab a &#39;little&#39; example of what we believe should be possible with Factom based technologies, to hopefully make it clear to people that Factom is a bit more than only hashes or proofs. This example is a bit of a stretch, isn&#39;t fully thought through, so people can probably shoot some holes in it. If it were completely thought through and if we had enough people, it would already exist ;) It does show the order of magnitude we are thinking for some projects within <a href="https://sphereon.com/">Sphereon</a> and <a href="https://factomprotocol.org/">Factom</a>. It also hopefully inspires some people to think out of the box, as I could write several similar services, products or even business plans using Factom based technologies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*evjtvH_Uu8V0PIpy6ckwkA.jpeg" /></figure><h3>Decentralized e-mails really?</h3><p>Let&#39;s say I want to use an e-mail service as a company, I can fully trust, which isn&#39;t run by a single company, is censorship resistant and above all can prove an e-mail is not altered at any point in time, as well as prove that the e-mail existed at a certain point in time and me being the author of the e-mail, optionally encrypting the contents. Would be cool huh?</p><h3>Shopping list</h3><p>Ok let&#39;s start with some building blocks we certainly will need:</p><ul><li><a href="https://www.w3.org/TR/did-core/">Decentralized Identifiers</a></li><li><a href="https://www.fatprotocol.org/">Factom Asset Tokens</a></li><li><a href="https://pegnet.org/">PegNet integration as payment rails</a></li><li><a href="https://www.fatprotocol.org/">(FAT) Smart Contracts</a></li></ul><h3>Decentralized Identifiers</h3><p>Decentralized identifiers are the next form of identities for Persons, Devices, Objects based on public/private keys. See some other blog posts of mine for more details. For now it is important to remember that you can compare DIDs to a website URL like <a href="https://sphereon.com,/">https://sphereon.com,</a> only then for a document on Factom that describes attributes about an identity. See the W3C site for more technical details: <a href="https://www.w3.org/TR/did-core/">https://www.w3.org/TR/did-core/</a></p><h4>E-mail signature and proofs</h4><p>How can you prove an e-mail is not altered and have it timestamped at the same time? Simple an e-mail has a well defined structure. The most important part you want to prove are the body, attachments, subject and recipients. All parts of an e-mail you can quite easily grab. When the sending e-mail server or even the mailclient would use this data, generate a hash or series of hashes, maybe even in a tree (merkletree), you simply have to generate a signature with a private key associated to a DID you control. You publish the data in a predefined location, or a location people can lookup from your DID document in the Factom blockchain and anybody that knows your DID or public key could verify the message at a later point in time.</p><p>This proves the e-mail has not been altered. Every single change to the subject, recipients, or contents would invalidate the signature and hashes. It also proves that the e-mail existed at a specific point in time. In theory the e-mail could exist before the point in time, but the content certainly existed at the moment it was anchored in Factom. Since you are the sender of the e-mail and your DID also is associated to your e-mail adress, people can also trust it was really you that send the message (DID-dns/web associates your e-mail address and/or domain). You could use your or recipient keys as well to encrypt data, depending on the use case.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*inYRJ1H4m3w6D4Rm2YkQ-w.jpeg" /></figure><h4>Verification</h4><p>Verification could be done in multiple ways. Recieving mail servers could already do checks and insert results in the headers of the e-mails along the way, even using their Factom based DIDs. It is simply verifying whether the DID from the sender is correct and whether the signature can be verified based on the subject, content, sender and recipients. If something like this would become the norm, you could create a reputation system based on it, making spam way harder.</p><p>Obviously for end-users it is easier to have some plugins for Outlook, Office365, Gmail or on your mobile phone. Basically it uses the same process as desribed above.</p><h4>E-mail Authentication</h4><p>Sending and receiving e-mails uses authentication protocols, ideally these would be integrated with DID-auth on Factom in the future. Meaning passwordless authentication, using private keys stored in a personal wallet/vault, with you deciding when/where they can be used. This however would require support by both the sending mail (SMTP) server as well as mailbox server (IMAP, POP3, MAPI). Definately possible, but would require writing custom modules in some open-source projects like for example Postfix (SMTP) and Courier (IMAP/POP3). It would allow you to decrypt mails on the fly, or ask you to confirm on your mobile phone and sign the mail before sending it out. Eradicating almost completely the posibility of somebody else sending in your name.</p><h4>Censorship resistance</h4><p>What about the censorship resistence you mentioned? Well <a href="https://factomprotocol.org/">Factom</a> with it’s commit-reveal scheme is already censorship resistant itself. Basically you pay with a hash for a spot in the blockchain. The content you will post later and nodes are required to anchor the data (oversimplified). Since the whole idea here was to be able to prove mails have not been tampered with, as well as being able to verify that every step of the way, it means every party in a mail interaction or in the distributed mail service would be able to verify the data to be correct. If a bad actor would have found it’s way into the system, it would be quite easy to make a consensus or reputation system that would kick out the actor eventually. The last party in the network touching the mail would be the problem, but eventually even that one is verifiable externally.</p><h3>Decentralized or distributed much?</h3><p>&quot;Ok Niels, although a bit technical, I think I can follow you to this point. But what about the above makes it decentralized?&quot; Good question….absolutely nothing ;)</p><p>To make it decentralized you will have to make it distributed first and at the same time ensure people are incentivized to run mail-services for you. Otherwise you get the problem of Torrents. People wanting to leech their files, without giving back (seeding) to the rest.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OI8r3B1Q5A0Mgpuy2x-yag.jpeg" /></figure><h4>Registry</h4><p>First you need to have a registry based system where people providing e-mail services for sending (SMTP) as well as storing (IMAP/POP3). This could be created on top of Factom, together with DIDs. Obviously it would need some work to figure that out completely. But given you can create (virtual) chains for all your data on Factom it should be doable. For arguments sake let&#39;s assume people can register their sending servers (SMTP) and storing services (IMAP/POP3) in a system like that on Factom, together with addresses for receiving tokens.</p><p>Whenever a new &quot;customer&quot; registers, it submits it&#39;s registration data to a FAT smart contract. Providers that fit the requirements and that are in the registry would automatically provision infrastructure upon the first payment. The registry would be updated, DNS entries would be created (I leave DNS out of scope in this article, as that is a bit of a project itself :P) to make sure you can receive e-mails, as well as make sure that other mailservers would accept mail from you.</p><h4>Subscription and incentives</h4><p>The end-user would be paying a monthly subscription based on a currency of choice in <a href="https://pegnet.org/">PegNet</a> (stablecoin network). Different plans for storage retention and sizes could be created. Internally a special FAT token will be used, this ensures parties are incentivized to run the services and keep them up. As long as the end-user keeps paying the nodes providing the services are required to provide SMTP services and store e-mails (IMAP/SMTP). Obviously you want to create shards and redundancy in the network as it grows, and rebalance when nodes would drop out. A FAT smart contract would ensure the tokens paid by the end-user get distributed to the parties running the services for the end-user. By including a reputation system, parties providing reliable services (uptime) and/or for a long time (duration) get relatively more rewards. Rewards are locked up and paid out over time, with a weight more towards the end, to ensure providers do not run after a payment.</p><p>The token would very much like PegNets only free floating token PEG be valued by the market. What are people willing to pay for a service like this and what would infra providers want to receive? They also have Entry Credit costs to cover, besides the obvious infra costs. Would you trust a system handling your e-mails when there is no central party? Would you trust parties to not read mail? I guess it is a nice thought experiment whether a system like this would be economical viable. Obviously I haven&#39;t done the math and for the e-mail case would be skeptical. The part up to the decentralization chapter is the easier part and not dependent on decentralization at all.</p><p>I am just presenting this as an example of combining Factom related technologies to create a distributed solution and to let you hopefully think outside the box when you start to combine several Factom and W3C technologies. Nope Factom is not about hashes alone ;)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9c32fc511672" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/a-distributed-verifiable-censorship-resistent-e-mail-service-on-top-of-factom-9c32fc511672">A distributed verifiable censorship resistent e-mail service on top of Factom!</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Factom vision — tokenization - part 3]]></title>
            <link>https://medium.com/swlh/factom-vision-tokenization-part-3-542b031d8d19?source=rss-1af481e54512------2</link>
            <guid isPermaLink="false">https://medium.com/p/542b031d8d19</guid>
            <category><![CDATA[currency-exchange]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[tokenization]]></category>
            <category><![CDATA[factom]]></category>
            <category><![CDATA[asset-management]]></category>
            <dc:creator><![CDATA[Niels Klomp]]></dc:creator>
            <pubDate>Sat, 20 Jul 2019 21:40:38 GMT</pubDate>
            <atom:updated>2019-07-20T21:40:38.286Z</atom:updated>
            <content:encoded><![CDATA[<h3>Factom vision — tokenization - part 3</h3><p>This series of articles is about my personal vision for the Factom Protocol and where I believe the protocol should be headed. This is the 3rd part of multiple stories as I would like to take the time for the less technical inclined people to get the full vision. Please note that the vision will be mentioned in part during every single story, but the last story will be about the vision itself. In my <a href="https://medium.com/swlh/factom-vision-the-building-blocks-part-1-954145e4a320?source=post_page---------------------------">first</a> and <a href="https://medium.com/swlh/factom-vision-the-building-blocks-part-2-b64aefb20dae">second</a> article I have been talking about identities, verifiable credentials and zero knowledge. Now I will be talking about tokenization, stable coins and again I will include some identities in the mix. I guess you noticed a pattern by now ;)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j1rYRChpeDrZsbQxPWYMdQ.jpeg" /><figcaption>Coins and identities?</figcaption></figure><h3>Factom tokenization is FAT</h3><p><a href="https://github.com/Factom-Asset-Tokens/FAT">FAT</a>, short for <a href="https://github.com/Factom-Asset-Tokens/FAT">Factom Asset Tokens</a> are a collection of open source, data-only, blockchain tokenization standards. FAT Tokens open up affordable, secure decentralized crypto tokens to the world. Anyone can send, receive, and create their own tokens for a <strong>low</strong> and even more important <strong>fixed</strong> cost. FAT offers the security of Bitcoin, Ethereum and Factom combined, simply because the Factom blockchain anchors a proof every 10 minutes into the Bitcoin and Ethereum blockchains for additional security. FAT also has the flexibility of Ethereum, all for a <em>fixed</em> price that is roughly <em>1/100th</em> of the price of Ethereum. FAT tokens are fixed at $0.001 USD per transaction and $0.012 USD per new token issuance. The latter of course is only needed to bring tokens into existence. Immagine bringing tokens into existence representing millions of dollars for the price of $0.012 and then transacting these tokens for only $0.001 USD per transaction.</p><h4>Fungible FAT-0 tokens</h4><p>The <a href="https://github.com/Factom-Asset-Tokens/FAT#fat-0">FAT-0</a> specification describes a fungible token. Fungible tokens are tokens that are interchangeable and indistinguishable, like for instance currencies. To hold 20 dollars it doesn’t matter which 20 dollar bill I hold. It even doesn’t have to be one bill at all. Only the number on the bills and coins matter as it denotes the value and that should add up to 20.</p><p>FAT-0 is much like Ethereum <a href="https://theethereum.wiki/w/index.php/ERC20_Token_Standard">ERC20</a> tokens. ERC20 tokens became wildly popular for Initial Coin Offerings because of their simplicity and interoperability (easily supported by exchanges for instance). Among the most successful ERC20 token sales were EOS, TON and Filecoin, raising more than $200 million dollar each. A quick scan on <a href="https://etherscan.io/">Etherscan.io</a> these days shows there are over <em>200.000</em> ERC20 token contracts and thus that many different types of ERC20 tokens. The largest one, BNB created by the Binance Exchange, representing a Market Cap of $4,718,612,571, individual coin price of $30.3376 and 314,298 holders at time of writing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/870/0*rNlU7hB0ezW_iQFt.png" /></figure><p>A first ITO on FAT using FAT-0 tokens has already been announced to take place at a later stage by <a href="https://triall.io/">Triall</a>.</p><p>A blockchain ecosystem for clinical trials, that <a href="https://medium.com/@niels.klomp/the-worlds-first-clinical-trial-in-production-on-the-blockchain-has-just-been-announced-by-the-e05b73557dd0">recently announced</a> the World’s first live clinical trial in production on the Factom blockchain.</p><h4>Non-Fungible FAT-1 tokens</h4><p>The <a href="https://github.com/Factom-Asset-Tokens/FAT/blob/master/fatips/1.md">FAT-1</a> specification describes a non-fungible asset token standard. A non-fungible token represents something unique that is not interchangeable. A nice little comparison for non-fungible tokens is a baseball card collection. These cards contain unique information and have different levels of rarity. The card itself is the same piece of paper obviously with the same manufacturing cost, but if we blindly swap 2 cards, one person probably is very happy whilst the other one is not. Simply because the cards represent different information and have value in the eyes of the holders. Just like a non-fungible token you also cannot split the baseball card in two or more pieces. Non-Fungible FAT-1 tokens, just like baseball cards are non divisible. This is in sharp contrast to the Fungible FAT-0 tokens. Whenever you talk about collectables quite often the provenance also comes into play. Which person(s) held your cards in the past for instance. Non-Fungible tokens incorporate the same concept.</p><p>To sum up, Non-Fungible FAT-1 tokens:</p><ul><li>Are tradable in whole number token increments only</li><li>Are unique, and can have unique properties</li><li>Have a history of the addresses they’ve resided at</li></ul><p>FAT-1 tokens are much like Ethereum <a href="http://erc721.org/">ERC721</a> tokens, which probably are best known by the <a href="https://www.cryptokitties.co/">CryptoKitties</a> rage. A quick look at <a href="https://etherscan.io/">Etherscan.io</a> shows there are currently 2,006 ERC721 Token Contracts. Non-fungible tokens by their nature are harder than fungible token. Non-Fungible tokens are being used on Factom for instance by DBGrow (the creators of FAT) and other parties with an Asset Holding company to tokenize options contracts with an interest to tokenize more of their portfolio as the technology matures.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fbdp7DsrX7hY&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dbdp7DsrX7hY&amp;image=http%3A%2F%2Fi.ytimg.com%2Fvi%2Fbdp7DsrX7hY%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/c8704e59818acdbd818f11a4fd839139/href">https://medium.com/media/c8704e59818acdbd818f11a4fd839139/href</a></iframe><h3>Identity based transactions and addresses</h3><p>Every public blockchain uses addresses and transactions to transact coins. Factom is no different. What is different however is that Factom has separated storage of information away from these transactions, by virtue of its data structures and a secondary usage token, the Entry Credit (EC). The EC pays for the data storage at a fixed price, using a commit and reveal scheme to be censorship resistant. This article will become even longer if I have to explain that in detail I am afraid, so I will leave it at that. The key takeaway is that Factom doesn’t have the limitation to have to store everything within a transaction context, like most other blockchains.</p><p>These public addresses are the public parts somebody can hand out to the other party. The private part is basically your wallet. A common misconception is that tokens are physically stored in your wallet. No, only the private key(s) are stored in your wallet! The private key is what allows you to control the tokens that reside on their public key counterparts, the public address(es). You sign the transaction using your private key, which in turn makes it a valid transaction as the transaction always has the context of the sending address (you), to verify your signature against.</p><p>If you have read my previous articles you should probably by now have made the connection that the identities (DIDs) I talked about earlier where basically also a combination of an address (DID), public key(s), management and attributes. A DID is a common cross ledger standard for identities using much of the same concepts of native addresses on a blockchain. An address is typically not used to identify somebody or something in the wider world. Most of the time they are only used in peer 2 peer transactions only.</p><p>Wouldn’t it be nice if I could transact to a person, organization or smart contract that has been verified using a Know Your Customer (KYC) process in some cases? If an address is associated with a DID that has been verified by for instance a bank or the government, you know you are transacting with that party without a doubt. Or a use case where you need to be sure somebody is at least 18 years old (Verifiable Credentials) to perform the transaction. Not sure? Well hopefully you get it after reading the next example.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mJCG_Lnv3FsUzRjVw1hM3A.jpeg" /></figure><h3>Booking a hotel in the future?</h3><p>How would booking a hotel room look like in a future where you combine DIDs, Verifiable Credentials, tokenization (and smart contracts, IoT)? Smart contracts and IoT will be explained in the next story. That story will also expand the example started here.</p><p>A hotel typically doesn’t allow you to book a room if you are not at least 18 years of age. The hotel needs your address, contact info, credit card information, passport/id-card and the names of the other guests. Typically a photocopy of your passport is being made, which in a lot of EU countries is officially not allowed. You are not allowed to handover your passport unsupervised to non-authorities let alone let them make photocopies, as these are restricted to only a few use cases and booking a hotel room certainly isn’t one of them. How are you sure it does not fall into the wrong hands?</p><p>Wouldn’t it be much nicer if the hotel already knows it is you right from the start, so whilst registering using the hotel or booking site? You use your DID to login to the hotel or booking site and book the hotel room of your choice. You selectively disclose that you are at least 18 years old (instead of your exact birthdate), which has been verified by a trusted 3rd party. You disclose contact information and the DIDs of your fellow guests. Next you pay for it using tokens which are held in reserve for the hotel, more on that last part in the next story about smart contracts.</p><p>Now you show up at the accommodation. Although being greeted in the lobby is nice, for sake of showcasing the possibilities let’s skip that. You already got confirmation about the rooms you have booked. You can just walk up to the door and either use the hotel app or your fingerprint to open the doors. Same for your fellow guests. How is that possible? Well you and your guests simply prove that you are in control of the DIDs that have been used to book the hotel rooms (see previous story) in the first place. Remember that DIDs allow for authentication (including biometrics)</p><p>Want to use the minibar? Well I am guessing by now you see you could use the similar process as opening the door. Booked access to some additional amenities? Just prove you are in control of the DID(s). Bartender wanting to pour you a drink containing alcohol? Same concept together with verifying the claim that you are at least 18/21 years old. Does he need to know your room number? Of course not, that is already tied to your DID in their system. Want to hear your favorite music or netflix movies in the room? Well the room can know it is you in the first place and just ask for permission to authenticate and load your music/video account on the device for 24 hours.</p><p>Although just a little example of what would be possible using Factom, it showcases the immense impact technologies like Factom can have in our daily lives. We might not be completely ready for it yet, but the concept of identities, verifiable credentials, tokenization, smart contracts and IoT combined promise some very interesting opportunities for the future.</p><h3>Designed (micro) economies</h3><p>At <a href="https://sphereon.com/">Sphereon</a> we use FAT for instance for a type of welfare benefits in the Netherlands. Much like your typical food stamps, Dutch local governments often have their own fund for people in social or economical need.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/272/1*B8KYrSFLKehyXYgZxm_pYA.png" /><figcaption>Example of inhabitant app</figcaption></figure><p>They get benefits for activities or products, like sports- and hobbyclubs, the library, musea, clothing etc. Instead of doing that all administratively, which is really cumbersome and intensive, we have designed a graph like token economy, where there are 3 parties. The local government issuing tokens to the recipients (inhabitants). The inhabitants can pay for these services or products only using the tokens at registered and known parties (KYC), like musea or shops. Optionally inhabitants can remain anonymous in the whole process (even to the local government).</p><p>Tokens can only flow from the local government to the inhabitant to the shop and back to the government where the tokens can be burned. The local government sends out an invoice to the shop owner using self billing (a negative invoice) and pay the shop owner Fiat money. This means that a process that took several weeks and sometimes months in the past could be done in real time if they like. In reality to keep the administration department happy the Fiat payout is done in batches. There is more to this use case than meets the eye, but this story is already becoming too long ;)</p><h3>PegNet — Decentralized autonomous stable coin network</h3><p>On of the very exiting things being build on top of Factom and on top of FAT is a completely new stable coin network that is unlike anything I have seen to date. Currently there are typically 3 types of stable coin solutions. I recommend <a href="https://medium.com/witnet/the-next-step-for-stablecoins-decentralized-oracles-da12e0792fc">this medium article</a> if you want to know more about them. They all have in common that they are somehow collateralized.</p><p>From the <a href="https://pegnet.org/">PegNet</a> FAQ: Pegnet is a decentralized network of tokens pegged (stabilized) to different currencies and assets that allows for trading and conversion of value without the need for counterparties. It is a fully auditable, open source stable coin network using the competition of PoW and external oracles to converge on the prices of currencies and assets.</p><p>Yeah that is right. No counterparty. I am not going to explain how it exactly works. I recommend you to read the <a href="https://docs.google.com/document/d/1yv1UaOXjJLEYOvPUT_a8RowRqPX_ofBTJuPHmq6mQGQ/edit#">whitepaper </a>and <a href="https://pegnet.org/">website</a>. PegNet has several unique features:</p><ul><li>In wallet conversion of assets. So convert from a pegged US dollar into Gold (pegged), without an intermediary like an exchange</li><li>Proof of Work for to make Oracle data secure and trusted</li><li>Burn and mint model of assets (conversions). If you convert you burn the source tokens into the newly create target tokens</li><li>Fully trustless network. Nobody is in charge or operating it</li><li>A unique PoW hash algorithm that should be ASSIC resistant and doesn’t use as much energy as a typical Proof of Work solution.</li></ul><p>So a stable coin network running on top of Factom and using FAT, that can track several Fiat currencies, crypto currencies as well as other assets like gold, silver, oil. All convertible in your own wallet without having to use an exchange. This allows for payment solutions with automatic conversions. Or people going to stable USD or EUR from their BTC, FTC or ETH on price swings. It allows stable coin usage in smart contracts etc. Is there no need for Exchanges anymore then? No, you still need exchanges to get out of PegNet obviously. If you want real USD some party has to convert the pegged value into the real asset.</p><p>Although still in heavy development there already is interest in providing liquidity as well as exchange integrations for PegNet. As PegNet will be build on top of FAT for tokenization it means developers and exchanges will be able to leverage FAT for Fungible tokens, including Pegged Tokens at the same time.</p><h3>Consensus algorithms</h3><p>To know how Factom works, where the protocol governance is heading and how tokenization fits in, first some explanation about consensus algorithms.</p><p><em>Proof of Work</em> is the resource incentive consensus algorithm used by Bitcoin and Ethereum for instance. Basically it is a competition between parties to solve a really hard computational puzzle in a limited amount of time to complete a transaction. The winner gets a reward in the native currency. People see a lot of drawbacks, especially the amount of resources (power) that have to be “wasted”. But it is basically the only consensus algorithm that has proven itself in the course of a decade.</p><p><em>Proof of Stake</em> and <em>Proof of Authority</em> are quite similar to each other, but different from Proof of Work. With <em>Proof of Stake</em> you set aside a certain amount of coins/wealth for a period of time to show your interest in the network. The more you “lockup” the more power you have. <em>Proof of Authority</em> is a modified version of Proof of Stake. Instead of coins parties put their identity at stake. This means your identity has to be (and remain) squeaky clean. Both consensus algorithms don’t “waste” the amount of resources that a Proof of Work consensus algorithm uses.</p><p>Lastly there is Proof of Burn. Basically you are removing tokens from circulation by burning them on purpose, making the tokens more scarce and increasing the price for others. Typically employed by miners. It is not a perfect fit for us, but quite similar in nature. I’d like to coin our future Proof of Burn more like <strong>Proof of Usage</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/696/1*pisAu0BbIO4j6CtWIjuETg.jpeg" /></figure><h4>Consensus in Factom</h4><p>Factom uses Proof of Authority primarily for it’s Authority Set, which then is secured by additional Proof of Work blockchains, because every 10 minutes proofs (Merkletree roots) are anchored into the Bitcoin and Ethereum blockchains. However our governance has had the foresight that only Proof of Authority anchoring into Proof of Work will not be enough. Our governance has been designed as a slow process for a reason. To make sure we get a nicely balanced ecosystem with regards to distributing power. Meaning that we are working towards giving all FCT token-holders a voice using Delegated Proof of Stake up to a certain percentage of the total voting power. The same holds true for the users of the protocol. The ones putting in the data, by burning Factoid (FCT) tokens into Entry Credits (EC) and spending those when anchoring data. This resembles the Proof of Burn mentioned above. It is not quite similar and I rather call it <strong>Proof of Usage</strong>.</p><p>Combine all of this and you get the Authority Set running the nodes having a certain percentage of voting power, together with token holders having a certain percentage of power as well as users of the protocol having a percentage, all using different algorithms. One might notice we miss developers in this equation. Well developers typically can be put in one or more of these categories, given we have a grant pool that pays outs grants in the form of FCT every 3 months.</p><h4>Using tokenization and DIDs in Factom governance?</h4><p>So 4 algorithms all playing nicely together? Yeah that is a bit of a technical problem we are working hard on to resolve. A really nice voting specification and implementation that is fully decentralized and censorship resistant has already been created. It works based on identities (not DIDs at the moment unfortunately). DIDs will be the future solution for the Authority Node Operators (Proof of Authority). We need identities attached to FCT addresses (Proof of Stake) and Entry Credit Transactions (Proof of Usage) to finish the final pieces of the puzzle.</p><p>When that puzzle is complete, we have a balanced system using Proof of Stake, Proof of Authority and Proof of Usage to make decentralized decisions and secure the network. The latter is again reinforced by the Proof of Work of Bitcoin and Ethereum network. A pretty neat and balanced combination if you ask me.</p><p><em>Liked it? Please do me a favor. You can clap up to 50 times so the story will be seen by more people. Questions and/or remarks? Please comment on the article!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=542b031d8d19" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/factom-vision-tokenization-part-3-542b031d8d19">Factom vision — tokenization - part 3</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The World’s First Clinical Trial In Production On The Blockchain Has Just Been Announced By The…]]></title>
            <link>https://medium.com/swlh/the-worlds-first-clinical-trial-in-production-on-the-blockchain-has-just-been-announced-by-the-e05b73557dd0?source=rss-1af481e54512------2</link>
            <guid isPermaLink="false">https://medium.com/p/e05b73557dd0</guid>
            <category><![CDATA[compliance]]></category>
            <category><![CDATA[blockchain-technology]]></category>
            <category><![CDATA[factom]]></category>
            <category><![CDATA[clinical-trials]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Niels Klomp]]></dc:creator>
            <pubDate>Sat, 13 Jul 2019 13:22:17 GMT</pubDate>
            <atom:updated>2019-07-13T13:22:17.402Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>The World’s First Clinical Trial In Production On The Blockchain Has Just Been Announced By The Triall Foundation</strong></h3><p><strong>On behalf of the Triall Foundation, I am excited to announce the world’s first clinical trial in production on the blockchain. A beta version of the foundation’s <em>Verial</em> software application was given green light for use in a real-world clinical trial and is now live in production, following positive assessment of its compliance with international regulations and quality standards for medical research. This marks an important milestone in a journey that we initiated over two years ago. Furthermore, to the best of our knowledge, this represents the first real-world implementation of blockchain in a clinical trial. Below, I’ll briefly introduce Triall, the <em>Verial</em> application, and our plans for a blockchain-enabled future of smarter, safer, and more-efficient medical research.</strong></p><p><em>Niels Klomp is the CTO of Triall, CTO of Sphereon, and elected guide of the Factom Blockchain.</em></p><p><strong>Triall Foundation: smarter, safer, more-efficient clinical trials</strong></p><p><a href="https://www.triall.io/">Triall</a> brings together a consortium of clinical trial specialists and blockchain engineers, and was founded to tackle some of the persisting issues that make clinical trial operations overly complex, lengthy, and resource-inefficient. (More info on clinical trials can be found in <a href="https://medium.com/triall-foundation/a-brief-introduction-to-clinical-trials-medical-research-and-pharmaceutical-innovation-b6c126c998ec">this</a> Medium article.)</p><p>Most importantly, due to trials involving many different organizations, locations, and data sources, virtually all clinical researchers experience issues with keeping track of their documents and data. Yet, increasingly stringent regulations demand meticulous documentation of all clinical trial conducts, and all documents and their changes should be auditable at any time.</p><p>Lacking oversight hampers recordkeeping, resulting in costly reiterations, errors, and even safety risks for patients and consumers.</p><p>We believe that applying blockchain technology in the collection and processing of clinical trial data will become the industry’s golden standard. Among other promising use cases (as outlined in the Triall <a href="https://www.triall.io/#whitepaper">whitepaper</a>), blockchain can provide the many stakeholders involved in a clinical trial with indisputable proof that data has been recorded at a set time under a verifiable condition.</p><p>To improve the auditability and operational efficiency of clinical trial operations, Triall together with technology partner <a href="https://sphereon.com/">Sphereon</a> is developing a series of modular applications on top of the blockchain infrastructure of the <a href="https://www.factomprotocol.org/">Factom Protocol</a>.</p><p><strong>Verial: a blockchain-enabled document management solution for clinical researchers</strong></p><p><em>Verial</em> represents the first application in this series. The clinical document management solution enables users to establish verifiable proof of the integrity and authenticity of essential research documents, and to establish an immutable audit trail of their evolution over the course of a clinical trial.</p><p>These utilities are powerful, as it generates proof that these documents have not been altered after registration. Hence, it promises to drastically improve the reliability and auditability of clinical research throughout the pharmaceutical development chain, and fully answers to calls for meticulous documentation and data transparency by the U.S. Food &amp; Drug Administration (FDA), European Medicine Agency (EMA), and other regulatory authorities.</p><p>Following positive assessment of its compliance with clinical trial regulations and guidelines, we have initiated the use of <em>Verial </em>in a first real-world clinical trial (phase II, &lt;50 participants) as a pilot to optimize usability. This will allow our development team to optimize usability and work towards a first release-candidate version.</p><p><strong>The promising use case for blockchain in clinical trials</strong></p><p>We strongly believe blockchain can revolutionize the way we approach pharmaceutical research and development, by assuring the integrity and transparency of clinical evidence, and by offering advanced solutions for managing identities and data access. Below, I’ll cover three examples of clinical trial procedures in which our in-development applications promise to add significant value.</p><p><strong><em>1.</em></strong> <strong><em>Informed consent</em></strong></p><p>Patients should only be enrolled in a clinical trial after having provided their full, informed consent on the study design and procedures. Proof of informed consent takes the form of an Informed Consent Form (ICF), signed by the patient. Unfortunately, <a href="http://www.picronline.org/article.asp?issn=2229-3485;year=2013;volume=4;issue=2;spage=144;epage=147;aulast=Gupta">the ICF is regarded as one of the most fabricated documents in clinical research</a>, and researchers are sometimes seen to enroll patients or even start data collection before the ICF is signed.</p><p>By registering a hash of the signed ICF on the blockchain, researchers can prove that the patient has consented to participate in the clinical trial in a timely, unfalsifiable, and verifiable way. Moreover, as clinical trial data-capturing tools may also be integrated with the blockchain layer, conditional terms can be set in place, such as only allowing data inputs for a specific patient after that patient’s ICF has been registered on the blockchain. In case there has been a change to the study design (as registered in a trial protocol document), data inputs could be allowed only after patients have consented to the protocol alterations.</p><p><strong><em>2.</em></strong> <strong><em>Predefined outcome measures</em></strong></p><p>There have been numerous instances where researchers have changed their initial clinical trial hypothesis and analysis plan after analyzing their research data — a process known as p-hacking or data dredging. This is a dangerous malpractice because it increases the chance for false-positive errors, and regulations therefore explicitly state that outcome measures need to be defined prior to the start of the study. By registering a hash of the Statistical Analysis Plan on the blockchain before the start of the trial, researchers can prove that they have adhered to the predefined outcome measures.</p><p><strong><em>3.</em></strong> <strong><em>Database lock</em></strong></p><p>To prevent unintentional and unauthorized changes after final data entry, check-up, and analysis, regulations stipulate that the clinical trial database is locked after data collection has concluded (the ‘database lock’). Strikingly, there have been various cases where researchers did alter their evidence, with health-damaging and costly consequences.</p><p>Using blockchain technology, researchers can generate verifiable proof that their data set has not been altered. This can be done in an easy and efficient way, by generating and registering a single hash (32 bytes + optional metadata) of the entire clinical trial database (hundreds of GB).</p><p><strong>Like to known more?</strong></p><p>· Follow <a href="https://f1000research.com/articles/6-66/v5">this link </a>for an academic paper on the registering of patient informed consent on a blockchain ledger.</p><p>· Want to know more about Triall? You can download our <a href="https://www.triall.io/#whitepaper">whitepaper</a>, or visit our <a href="https://www.triall.io/">website</a> and <a href="https://insights.triall.io/">blog</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/430/1*UpbnxbmhPEWIzXrhRJIZ5Q.png" /></figure><p><strong><em>Clinical trials: Facts and Figures</em></strong><em>. Over half of the global pharmaceutical R&amp;D budget (totaling US$ 172 billion in 2018) is currently spent on clinical trials. The market for clinical trials is dominated by European and North-American organizations, and roughly 80% of all research subjects enrolled in trials origin from these regions. More info on clinical trials can be found in </em><a href="https://medium.com/triall-foundation/a-brief-introduction-to-clinical-trials-medical-research-and-pharmaceutical-innovation-b6c126c998ec"><em>this</em></a><em> Medium article.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/134/1*ugruTMjLO-xEvP98BH6WpQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e05b73557dd0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/the-worlds-first-clinical-trial-in-production-on-the-blockchain-has-just-been-announced-by-the-e05b73557dd0">The World’s First Clinical Trial In Production On The Blockchain Has Just Been Announced By The…</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Factom vision — the building blocks, part 2]]></title>
            <link>https://medium.com/swlh/factom-vision-the-building-blocks-part-2-b64aefb20dae?source=rss-1af481e54512------2</link>
            <guid isPermaLink="false">https://medium.com/p/b64aefb20dae</guid>
            <category><![CDATA[decentralized-identity]]></category>
            <category><![CDATA[identity]]></category>
            <category><![CDATA[factom]]></category>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Niels Klomp]]></dc:creator>
            <pubDate>Wed, 10 Jul 2019 00:30:36 GMT</pubDate>
            <atom:updated>2019-07-10T07:35:29.379Z</atom:updated>
            <content:encoded><![CDATA[<h3>Factom vision — the building blocks, part 2</h3><p>In my <a href="https://medium.com/swlh/factom-vision-the-building-blocks-part-1-954145e4a320">previous article</a> I started my personal vision for the Factom Protocol and where I believe the protocol should be headed. This is the 2nd part of multiple stories as I would like to take the time for the less technical inclined people to get the full vision. Please note that the vision will be mentioned in part during every single story, but the last story will be about the vision itself. These stories will be about identities, verifiable credentials, zero knowledge proofs, tokenization, smart contracts, stable coins, IoT and general data proofs and how that all fits together in one single platform where the user can model their own data as well. In the <a href="https://medium.com/swlh/factom-vision-the-building-blocks-part-1-954145e4a320">first article</a> I was talking about Identities, Decentralized Identifiers (DIDs), Privacy, Decentralized Key Management Systems and authentication. This story will still be expanding upon DIDs. I promise next ones will have other subjects ;)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nTO9pNhSgnie4kdnzlcYYQ.png" /><figcaption>Will we have digital passport in the future?</figcaption></figure><h3>Verifiable Claims</h3><p>The best way to introduce the concept of verifiable claims is to again quote the <a href="https://w3c.github.io/vc-use-cases/">W3C Verifiable Claims working group</a>:</p><blockquote>A <em>verifiable claim</em> is a qualification, achievement, quality, or piece of information about an <a href="https://w3c.github.io/vc-use-cases/#dfn-entities">entity’s</a> background such as a name, government ID, payment provider, home address, or university degree. Such a claim describes a quality or qualities, property or properties of an entity which establish its existence and uniqueness.</blockquote><p>What the above doesn’t state is that it is about digital claims. The world around us is rapidly becoming more and more digital. Yet for whatever reason we trust analogue/paper processes more than digital processes. Probably because digital information is so easily manipulated. Hacks, conscious manipulation, deep fakes, photoshopped images are some of the examples everybody knows about.</p><h4>How do we create trust currently?</h4><p>We start by trusting central authorities. We have the state issue driver licenses, passports, identity cards, visa, social security numbers. Tax authorities providing income and tax data both for natural persons as well as businesses. We have the chamber of commerce providing incorporation data about businesses and people associated with it. Employers providing proofs about employment and wages, to name a few.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hnASPd8u8au1AEOHIfI2FQ.png" /></figure><p>If you are lucky this data is provided in some digital form as well, but most of the times it is not. Even if it is provided in a digital form it rarely is interchangeable. We are stuck with information scattered across paper most of the time. What happens when you want to get a mortgage? You go through this whole Know Your Customer (KYC) process, where they gather all kinds of information about yourself and your potential partner. Information is being scanned, archived, duplicated into backend systems. That is after you have gathered everything and handed it over to the mortgage provider.</p><p>Have you ever wondered why we trust most of that information? Simply because it is printed on official paper and with easy access to the entity that provided the information in the form of phone numbers and e-mail addresses. In some circumstance of course there are security features incorporated in the document(s) itself. Passports are the best example of documents with security features obviously.</p><p>Have you ever wondered how many entities have made copies of this type of information? Or how many entities still have that data on file about you? Or in how many systems that is stored? How is it secured? How many people have accessed the information? Is it even secure, or might it have been hacked? Ok let’s not get you paranoid now ;)</p><h4>Verifiable Claims to the rescue</h4><p>I talked about cross ledger (blockchain) decentralized identifiers (DIDs) in my previous article. A way to have digital self-created and managed identities for people, pets, devices and organizations that are universal resolvable like web browser URLs. What if I could make some digital claim using a DID attached to me, like for instance my date of birth and some claims you can derive from that, like my age and whether I am over 18 or not?</p><p>How would you trust these claims if I issued the claims myself using an identity (DID) I also created myself in the first place? Well how do wo do that currently? I go to my city hall to get my passport, drivers license or ID card that proves my data of birth. Simply because they are the only authorized party that can provide me the document. What if they could digitally sign the claim about my data of birth, as well as the derivative claims? If my city would also have a DID it means they could use it to sign the claim. Since anybody could verify the DID and signature of the city as well, you can trust that claim is valid. Of course I want to be able to store the claims about myself as well as selectively disclose what claims to present to the person wanting to do the verification; the Inspector/Verifier. The process itself is a bit more complex, but the picture below shows the process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Iybm1EP8L8A7y-v83Lz9XA.png" /></figure><h4>Example: Combining DID auth and Verifiable Credentials</h4><p>Let’s say I want to visit a website that has an age restriction, where you need to be at least 21 years old (no do not ask what type of site this example is about). How to get in without revealing my actual age or date of birth?</p><p>First if the site would support WebAuthn or DID-auth I could use my DIDs on Factom to prove I am in control of the identity and by a challenge response system using my private key attached to an authenticator app or web browser I would get in without ever using an insecure password.</p><p>Next the website asks for the proof I am over 21 years old. In my credentials repository I might have stored multiple credentials issued by multiple issuers that would satisfy this requirement. My browser or application asks which credential I would like to present/use. I choose one and the website will check the credential in the background and let me in. All of this in a seamless way without disclosing too much information. All the website knows now is that I am allowed to login and are over 21 years of age, which has been asserted by a party the website trusts. They do not know my real age let alone my date of birth. I am in control of disclosure of that information. That is what selective disclosure is about.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/775/1*GSC4dByNKtbrQ_xD_NA1Vg.png" /></figure><h4>Passport less travel?</h4><p>“People are never going to trust that and not use passports anymore. Let alone authorities allowing you to not use a physically passport during travel”.</p><p>Well news flash: I live in the Netherlands and my country has a world first. As an experiment it will become possible in 2020 to travel between Amsterdam, The Netherlands and Canada without a passport. Simply by means of a smartphone app that loads information about your passport into a secure vault. Three guesses what type of technology is involved in making that happen. All mainstream media have reported about it. Some examples (in Dutch):</p><p><a href="https://www.nu.nl/tech/5955438/canada-en-nederland-lanceren-project-om-te-vliegen-zonder-paspoort.html">https://www.nu.nl/tech/5955438/canada-en-nederland-lanceren-project-om-te-vliegen-zonder-paspoort.html</a></p><p><a href="https://www.telegraaf.nl/nieuws/1046147697/wereldprimeur-paspoortloos-naar-canada">https://www.telegraaf.nl/nieuws/1046147697/wereldprimeur-paspoortloos-naar-canada</a></p><h3>Zero-knowledge Proofs</h3><p>Zero-knowledge is a really really hard mathematical problem, so it also really hard to explain. This article is way too short to start trying to explain it in a comprehensible way, so I am not even going to try. If you are interested in the concept I suggest to read for example one of the links below. A zero-knowledge proof is where a prover (P) can prove that he knows information <em>i</em> to a verifier (V) without communicating any other information to V other than the fact that P knows <em>i.</em></p><p>A zero-knowledge proof satisfies the following three properties:</p><ul><li><strong><em>Completeness</em></strong> is the high-probabilistic chance that if P is telling the truth, V will eventually be convinced that P is telling the truth.</li><li><strong><em>Soundness</em></strong> is the fact that P can <em>only </em>convince V if P is telling the truth.</li><li><strong><em>Zero-knowledgeness</em></strong><em> </em>is that V doesn’t learn <em>anything</em> about P’s secret knowledge (solution).</li></ul><ul><li><a href="https://www.binance.vision/blockchain/zk-snarks-and-zk-starks-explained">zk-SNARKs and zk-STARKs Explained | Binance Academy</a></li><li><a href="https://blockonomi.com/zero-knowledge-proofs/">What Are Zero-Knowledge Proofs? Complete Beginner&#39;s Guide</a></li></ul><p>Zero knowledge has several use cases, to quote one of our community members involved with Zero-knowledge technology on top of Factom:</p><blockquote>Zero-knowledge is a transformative technology, with applications ranging from on-chain scalability and anonymous voting to preservation of sensitive information in B2B data exchanges — <a href="https://www.linkedin.com/in/vaganev/">Valentin Ganev</a></blockquote><p>One of the key concepts to take away from this article about Zero-knowledge proofs is that they are all about privacy preservation. The Factom Protocol is a public open blockchain, meaning everybody can see every piece of information. This means you never ever want to store Personally Identifiable Information on Factom (or on any other public blockchain) . Zero-knowledge solutions allow you to store sensitive information on a public blockchain shielding it in a safe way from prying eyes. Allowing you to prove information to others without revealing the actual data. It can be used in the above mentioned Verifiable Credentials for instance.</p><h3>Offchain personal data storage — Identity Hubs</h3><p>As mentioned above a public blockchain should never be used to store personal identity data. Simply because you cannot delete if from the blockchain. This would be a GDPR nightmare in the making. Simple encryption also is not really a good idea, as the encryption scheme might be broken in 10–20 years time.</p><p>You want to have a different solution for secure storage of personal data and information. Identity Hubs coined by the <a href="https://identity.foundation/">Decentralized Identity Foundation</a> are that solution.</p><p>Identity Hubs are personal datastores that are off-chain and that typically contain personal data. They allow you to store sensitive data, like identity information, official documents, photos etc. in a way where you are in full control of disclosure. Nobody without explicit permission will be able to access any data stored in your Identity Hub. You are able to share subsets of data with other people, apps, organizations and at the same time retain a record of usage. Important to note is that one person or organization is not limited to one identity hub. You can have multiple independent hubs.</p><h4>Relationship to DIDs?</h4><p>Up until now I only talked about DIDs in the context of identities and authentication. I also explained you can see it as URLs. But there is more to DIDs. They allow you to do service discovery. Meaning they will allow you to interact with additional systems, symply by looking up information in the DID document on the blockchain. You can best compare it with a phonebook. If you know what you are looking for (the start location), you are able to lookup additional data. Identity hubs can be resolved using the DIDs. DIDs will also be used for authorization and access to the data, including revoking access.</p><h4>Inversion of control</h4><p>Something which is common for developers, but here I am talking about the fact that the user will be in control about data. It is stored in your own Identity Hubs. These hubs can be located on your personal devices, or in trusted cloud environments like Microsoft Azure (ok no jokes about trust now). Whenever a website would like to have access to certain data it accesses your Identity Hub and only gets the particular item it is allowed to fetch, instead of them having all the data stored in their databases.</p><h3>DIDs coming full circle</h3><p>Below is a picture courtesy of Microsoft. It nicely explain how DIDs can be used to access identity data, verifiable credentials (DID attestations), authentication for people, organizations, apps and devices and off chain storage of data. I happens that Factom is a really nice protocol suited to make that happen in the near future.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pnVJqqCmzRhebLtW" /></figure><h3>Whats next?</h3><p>Next articles will be about other technologies like tokenization, stable coins, smart contracts, IoT. We will leave the world of DIDs mostly behind us, although these technologies each also have some relation to DIDs.</p><p>Questions? Please let me know</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b64aefb20dae" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/factom-vision-the-building-blocks-part-2-b64aefb20dae">Factom vision — the building blocks, part 2</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Factom vision —  the building blocks, part 1]]></title>
            <link>https://medium.com/swlh/factom-vision-the-building-blocks-part-1-954145e4a320?source=rss-1af481e54512------2</link>
            <guid isPermaLink="false">https://medium.com/p/954145e4a320</guid>
            <category><![CDATA[vision]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[factom]]></category>
            <category><![CDATA[decentralized-identifier]]></category>
            <dc:creator><![CDATA[Niels Klomp]]></dc:creator>
            <pubDate>Mon, 08 Jul 2019 22:59:54 GMT</pubDate>
            <atom:updated>2019-07-09T19:24:06.205Z</atom:updated>
            <content:encoded><![CDATA[<h3>Factom vision — the building blocks, part 1</h3><p>As I mentioned in my <a href="https://medium.com/@niels.klomp/visionary-704c72a66521">previous story</a> about vision and which has been way too long ago, the <a href="https://factomprotocol.org/">Factom Protocol</a> has seen a lot of development since it’s decentralization little over a year ago. I will talk about the challenges we have faced and are still facing in future articles. I would like to take this moment to talk about my personal vision for the Factom Protocol and where I believe the protocol should be headed.</p><p><a href="https://factomprotocol.org/">Factom</a> has long been mostly about Proofs alone. You have this fingerprint called a hash of an object or file, or have this series of hashes to do proofs. Proof of Existence, Proof of Process etc. In itself that is really important for independently verifiable proofs and audits, but not necessarily the most sexy use case in blockchain. Since the inception of the grant pool in Factom to pay for development, marketing and governance related work we have seen many projects and products being added to the ecosystem. It is now time to share part of <a href="https://sphereon.com/">Sphereon’s</a> , <a href="https://triall.io/">Triall’s</a> and my personal vision for the protocol to kick of a wider discussion about the future of Factom. This is part of multiple stories as I would like to take the time for the less technical inclined people to get the full vision. Please note that the vision will be mentioned in part during every single story, but the last story will be about how it all should fit together according to me. These stories will be about identities, verifiable credentials, zero knowledge proofs, tokenization, smart contracts, stable coins, IoT and general data proofs and how that all fits together in one single platform where the user can model their own data as well.</p><h3>Data blockchain — refresher</h3><p>Factom is a pure data blockchain, allowing people to create their own data structures on top in chains you can create yourself. The concept is really powerful much like your own file cabinet or Inbox, where you are in control how you archive your e-mails. You can put all your e-mail in one Inbox or you can create a complete nested folder structure with e-mail distributed amongst them. It is up to the owner to decide what works best. This characteristic is a really important one and more on that later!</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*-KT4taZ0BiNB9-5oQuunhQ.png" /><figcaption>Image copyright RewardChain</figcaption></figure><h3>Identities on Factom (DIDs)</h3><p>Factom has had native identities from the start, but recently Decentralized Identifiers (DIDs) have been added. DIDs are current a W3C community specification, but with backing by major players like Microsoft we believe DIDs will form the basis for identity management in the future. DIDs are also called self sovereign identities and they are the key to enabling all kinds of solutions. From signing data, to voting, to web(app) authentication, to attestations and claims. A DID is attached to you as a person, to your device(s) or could even be attached to your children or pets. In that case you are in control of their identity as a pet obviously cannot do that itself.</p><p>This identity is cross ledger and can best be compared with a URL you type in your browser to visit a website. The DID points to a document on a blockchain that holds information about an identity. Of course that identity is a living thing. It can be updated or revoked over time. Also you would poses several different identities over time and at the same time. There is software available that allows IT vendors to integrate DIDs across several blockchains in a universal manner.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/0*mf-qdB0k1TzmkBcN.png" /><figcaption>A DID, a “URL”-like object pointing to identity data</figcaption></figure><p>The Factom Protocol is a really nice blockchain because of it’s fixed low price data entry, meaning DIDs also have a fixed low price on Factom. DIDs are primed to become the standard identity solution on top of the Factom protocol, mostly replacing the native identities and certainly replacing the so called node/server identities that are in place today on the Factom blockchain. Every product/project on top of Factom should standardize on DIDs in my opinion. Luckily we have Factom Interoperability Specifications now (more on that in another article), which provide specifications for vendors to make sure their application will be interoperable with other products performing similar functions.</p><h4>DIDs and Privacy by Design</h4><p><em>(shamelessly copied from the </em><a href="https://w3c-ccg.github.io/did-primer/#dids-and-verifiable-credentials-0"><em>W3C DID primer</em></a><em>)</em></p><p>Privacy is an essential component of any identity management solution. A DID architecture can incorporate <a href="https://en.wikipedia.org/wiki/Privacy_by_design"><em>Privacy by Design</em></a> at the very lowest levels of infrastructure and thus become a powerful, new, privacy-preserving technology if deployed using best practices such as:</p><ol><li><strong>Pairwise-pseudonymous DIDs.</strong> While DIDs can be used as well-known public identifiers, they can also be used as private identifiers issued on a per-relationship basis. So rather than a person having a single DID, like a cell phone number or national ID number, she can have thousands of pairwise-unique DIDs that cannot be correlated without her consent, yet can still be managed as easily as an address book.</li><li><strong>Off-chain private data.</strong> Storing any type of PII on Factom or any public blockchain, even encrypted or hashed, is dangerous for two reasons: 1) the encrypted or hashed data is a global correlation point when the data is shared with multiple parties, and 2) if the encryption is eventually broken (e.g., <a href="https://en.wikipedia.org/wiki/Quantum_computing"><em>quantum computing</em></a>), the data will be forever accessible on an immutable public ledger. So the best practice is to store all private data off-chain and exchange it only over encrypted, private, peer-to-peer connections.</li><li><strong>Selective disclosure.</strong> The decentralized PKI (DPKI) that DIDs make possible opens the door to individuals gaining greater control over their personal data in two ways. First, it enables it to be shared using encrypted digital credentials. Second, these credentials can use <a href="https://en.wikipedia.org/wiki/Zero-knowledge_proof"><em>zero-knowledge proof cryptography</em></a> for <a href="https://www.forbes.com/sites/bernardmarr/2016/03/16/why-data-minimization-is-an-important-concept-in-the-age-of-big-data/"><em>data minimization</em></a>, e.g., you can disclose that you are over a certain age without disclosing your exact birthdate.</li></ol><h4>Trust</h4><p>How can 2 parties trust each other though when the identities have not been build using traditional federated solutions like SSL certificate authorities? These identities have been completely build from scratch by the users themselves remember.</p><ul><li>Use Challenge/response messages for real-time verification of keys. Only the owner of the private key can interact and make sure the challenge completes successfully.</li><li>Exchange of credentials signed by other trusted parties, so called “verifiable credentials”, whose public keys can also be verified against a ledger of choice by virtue of DIDs. More in this subject further down ;)</li></ul><h3>Decentralized Key Management Systems (DKMS)</h3><p>Identities alone however are not enough. You need easy applications and solutions to create and manage your identities, and to manage identities of others. Think of a single person, pet or device. These identities need to interact with other identities. Either pairwise, in groups, within business units or organizations. Remember you will not have one DID, you will probably have hundreds and in most cases one per relationship. A relationship can be again a person, device, pet, organization or group of people. See it like your own private encrypted channel to interact with each other. All that identity management requires an easy to use and comprehensive system.</p><p>You need to be able to easily create, replace and retire keys without having to know all the fine details. Much like you use a wallet for cryptocurrencies without knowing how that actually works (for most people ;) ). TCP/IP connects all the computers nowadays, but only a really small percentage of people know how that works. You don’t need to know/worry about it.</p><p>As system that ideally allows you to model real world relationships. Meaning you want this to be available both to individuals as well as companies, organizations and even clubs and associations, or in Factom governance for instance for standing parties like guides, Authority Node Operators, users of the protocol and Factoid token holders.</p><h3>DID Authentication</h3><p>What is wrong with our current password based authentication? To quote <a href="https://webauthn.guide/">https://webauthn.guide/</a></p><blockquote>Passwords have an ever-growing list of problems associated with them, both for users and developers. Users have to worry about passwords being stolen by phishing tools, or their passwords being leaked online if websites they have accounts with are compromised. They have to worry about creating and remembering passwords without dedicated password management tools. Developers have to worry about all the complications of passing passwords through systems and safely storing them in databases.</blockquote><p>WebAuthn to the rescue! WebAuthn is a really recent <a href="https://w3c.github.io/webauthn">specification</a> written by the <a href="https://www.w3.org/">W3C</a> and <a href="https://fidoalliance.org/">FIDO</a>, with the participation of Google, Mozilla, Microsoft and others. It is supported by Windows 10, Chrome, Firefox, Edge and upcoming support on Safari. With mobile implementations for Android and soon IoS.</p><p>It works using public and private keys instead of passwords to quote the above site again:</p><blockquote>It allows servers to integrate with the strong authenticators now built into devices, like Windows Hello or Apple’s Touch ID. Instead of a password, a private-public keypair (known as a <strong>credential</strong>) is created for a website. The private key is stored securely on the user’s device; a public key and randomly generated credential ID is sent to the server for storage. The server can then use that public key to prove the user’s identity.</blockquote><blockquote>The public key is not secret, because it is effectively useless without the corresponding private key. The fact that the server receives no secret has far-reaching implications for the security of users and organizations. Databases are no longer as attractive to hackers, because the public keys aren’t useful to them.</blockquote><h4>But that is not DIDs right?</h4><p>Nope you are absolutely correct, but DIDs are build using the same principles. Public and private key pairs. A DID has specific mechanisms for authentication purposes, called DID-auth</p><p>To quote <a href="https://github.com/WebOfTrustInfo/rwot6-santabarbara/blob/master/final-documents/did-auth.md">https://github.com/WebOfTrustInfo/rwot6-santabarbara/blob/master/final-documents/did-auth.md</a></p><blockquote>We define DID Auth as a ceremony where an <em>identity owner</em>, with the help of various components such as web browsers, mobile devices, and other agents, proves to a <em>relying party</em> that they are in control of a DID. This means demonstrating control of the DID using the mechanism specified in the DID Document’s “authentication” object. This could take place using a number of different data formats, protocols, and flows. DID Auth includes the ability to establish mutually authenticated communication channels and to authenticate to web sites and applications.</blockquote><p>Although the scopes of both differ, I do hope people see the resemblance and the fact that DID authentication for instance allows Public and Private key pairs to be used, it makes WebAuthn and DID-auth a nice pair.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F301478766%3Fapp_id%3D122963&amp;dntp=1&amp;url=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F301478766&amp;image=http%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F740040298_1280.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="1920" height="1080" frameborder="0" scrolling="no"><a href="https://medium.com/media/6fa6be26a3c15151a1fa4eaefb4dc267/href">https://medium.com/media/6fa6be26a3c15151a1fa4eaefb4dc267/href</a></iframe><p>Using DIDs for authentication means you need to have proper solutions to provide the authentication. Currently <a href="https://off-blocks.com/">Off-Blocks</a> a digital identity and signature solution on top of Factom and Sphereon a BaaS and blockchain integration specialist are looking to add DID auth and WebAuthn support into off-blocks. Authenticator support has been on the roadmap of Off-Blocks for quite some time, but even with the app not out yet we are seeing demand for this use case already.</p><h3>What’s next</h3><p>We only scratched the surface. The next story will be about Verifiable Credentials, Zero knowledge proofs, Identity hubs, followed by pieces about tokenization, smart contracts and iOT, followed by “the vision”.</p><p>Let me know what you think.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=954145e4a320" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/factom-vision-the-building-blocks-part-1-954145e4a320">Factom vision —  the building blocks, part 1</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Visionary?]]></title>
            <link>https://medium.com/@niels.klomp/visionary-704c72a66521?source=rss-1af481e54512------2</link>
            <guid isPermaLink="false">https://medium.com/p/704c72a66521</guid>
            <category><![CDATA[future]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[data-integrity]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[factom]]></category>
            <dc:creator><![CDATA[Niels Klomp]]></dc:creator>
            <pubDate>Sun, 18 Nov 2018 00:20:01 GMT</pubDate>
            <atom:updated>2018-11-18T16:28:57.245Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><strong>“The year of Factom” ?</strong></blockquote><h3>Visionary?</h3><p>Paul Snow, CEO of Factom, Inc. the inventors of the Factom ® protocol, mentioned several months ago that 2018 would be “the year of Factom”. His comment has been ridiculed by some and questioned by others. Mostly by Factoid (FCT) token holders, the native crypto currency of the Factom ® blockchain. That sentiment is understandable as the price of the Factoid token has lost more than 90% of its value since the all-time high and the token seemed to have been hit harder than most other crypto projects.</p><p>Paul and his team have been proven to be visionaries in the past. Bringing the two-token system to Factom meaning enterprise don’t have to deal with crypto currencies, inventing segregated witness (segwit) before Bitcoin ran off with it, to name a few. He just might be right again. As the year is nearing its end, I will use this piece to highlight some of the noticeable accomplishments this year as well as dig briefly into exciting new projects being worked on. I will post some subsequent and more in depth pieces about several subjects.</p><h3>Full decentralization</h3><p>At the beginning of 2018 the Factom ® blockchain ran on servers, called nodes that were in sole possession of Factom Inc. Milestone 3 or M3, bringing full decentralization was long anticipated, but at the end of Q1 preparations to make this happen have begun. It started pretty much with community member Quintilian starting <a href="http://www.factom-testnet.com/index">a community testnet</a> together with Factom Inc. This meant gathering and attracting talented people and organizations to run the nodes. It meant creating a governance structure and document to which all (standing) parties must adhere. This meant the community chose 5 Guides out of their midst to make sure that the total decentralization process would take shape and several standing parties will find their place in the governance. These are FCT holders, users of the protocol by means of burning Entry Credits, the utility token, Authority Node Operators and grant recipients all get a place in the protocol, without any separate organization being able to gain full control. Without going into all the details in this piece, we now have 5 guides, 25 separate authority node operators running the network and developing solutions for Factom, weekly meetings, a grant pool for marketing, legal support, support projects and development projects.</p><h3>Authority Node Operators</h3><p>As mentioned, we now have 25 Authority Node Operators (ANOs), which eventually will become at least 65 ANOs. We held 2 ANO application rounds and will hold another round in the not too distant future. The 25 ANOs currently run 2 authority nodes each. They receive factoids as an incentive to run these nodes. Contrary to most projects a lot of these ANOs are also involved in all kinds of aspects of the protocol. From governance, to marketing to making sure we are listed on exchanges. The funny thing is that exchanges are not ready to handle a fully decentralized protocol like Factom, since they want to talk to CEOs, CTOs of the protocol. Guess what? There is none for the protocol, we have 25 ANOs and to some extent 5 guides currently deciding, with new standing parties to be added as well. We have ANOs doing development work, both open-source and making commercial solutions. With one common denominator. All this work touches Factom somehow. Being tools to enhance user experience, tools to integrate with Factom, tools to enhance the governance process and products/solutions that run on Factom and bring usage of the network.</p><p>We even have several ANOs that are building commercial solutions. “Federate This”, an ANO with a background in Aviation is focussed on building applications for the Aviation Industry. Its first product is Off-Blocks: a Mobile App for Digital Identity on Factom. What you can do with that Identity is quite exciting. It’s intended to be used both in and out the Flight deck.</p><p>Building Innovation Management Ltd, a UK based company who aims to reduce the cost of construction by bringing existing technology (Building Information Modeling) into the construction site for all workers. Its aim is to build a SAAS platform that uses the anchoring power of Factom to improve site safety and track workers while lowering the overheads of doing these activities. Other features it aims to offer through their SAAS are remove wasted effort, increase visibility of site metrics (completion percentage, delays, etc), and shorten the communication path between construction workers and designers.</p><p>In less than a half year countless developers, business people and other enthusiasts have taken on the mission to build out the Factom protocol to become the number one Data Integrity Protocol in the world. During bearish times, where ANOs make no money at all and are even investing money, people are still building behind the scenes on the Factom protocol. Has it been simple, of course not. It simply shows the resolve and the belief of the parties that have put blood, sweat and tears into it and will do so for the future as well.</p><h3>Where do we stand now?</h3><p>What has been accomplished last 6 months besides the already mentioned decentralization, standing parties and governance? The stability of the Factom blockchain has been improved drastically. Performance enhancements have been made as well. Below is a list with things already accomplished this year.</p><h4>Forum and social media</h4><p>We have the <a href="https://factomize.com/forums/">Factomize forum</a> for standing parties and external people to discuss, hold polls, and do votes. It helps the governance as it facilitates timed discussions and automatic votes, considering the standing parties.</p><p>We have a rather active <a href="https://discordapp.com/invite/YYM9w2V">Discord</a>, that is mostly hidden from the general public, people might have gotten the impression that Factom was not moving at all.</p><h4>Partners and noteworthy news</h4><p>· Factom Inc announced a partnership with FPT, a Vietnam based rapidly expanding IT company with a staff of 30.000 people, including an USA division focused on digital transformation for Fortune 1000 clients. (<a href="https://www.factom.com/company/news/press-release/fpt-and-factom-blockchain-as-a-service/">more info</a>)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/272/1*q0Q62_V8Bhn2pGNv4Yrd7Q.png" /><figcaption>Preview of Factom app</figcaption></figure><p>· An outside company affiliated with the Factom protocol, <a href="https://sphereon.com/">Sphereon</a> took their first large Financial Services company on Factom to the mainnet (production), doing roughly 1 million document registrations a year. It also took their first Dutch city to production with an integration in their IT system for council documents and a public verification website integrated into their official website. Lastly it partnered with Validsign to integrate their “traditional” document signing solution with blockchain capabilities. Sphereon is doing more than 40 blockchain projects.</p><p>· <a href="https://de-facto.pro/">DeFacto</a> an ANO from Russia settled an agreement with a Russian developer of commercial realty (top 10 Forbes Russia), integrating Factom into business processes of its shopping mall. Expected mainnet onboarding in Q4 2018. (<a href="https://de-facto.pro/blog/report-q3-2018">more info</a>)</p><p>· Factom, Inc. is the first blockchain company that went into the 4th and final stage of the Department of Homeland Security Innovation program <a href="https://twitter.com/factom/status/1007695382359560192">with their project to secure IOT data</a> (border camera’s).</p><p>· Equator, an Altisource business unit and a leading provider of residential loan default software and marketing solutions for many of the country’s top servicers, real estate agents and vendors, announced an agreement with Factom Inc. to integrate the Factom® Harmony blockchain-as-a-service (BaaS) platform into the Equator® PRO solution. (<a href="https://www.factom.com/company/news/press-release/equator-blockchain-solution/">more info</a>)</p><p>· Hangzhou Court (China) Accepts Factom Blockchain as Evidence in Online Copyright Trial. A court in the Zhejiang-province capital of Hangzhou has confirmed the legal validity of electronic data stored via the blockchain as evidence in an online copyright trial. This is really shows the value of Factom in legal cases.</p><p>·Several ANOs and related companies are talking or working with enterprise clients currently.</p><h4>First grants awarded and most implemented</h4><p>Some of the notable grants that have been awarded have been implemented already or work is progressing nicely</p><p>· Adding Official Ledger Nano S support so FCT holders can safely store their FCT on a hardware USB wallet (<a href="https://www.reddit.com/r/factom/comments/9xfzr7/officially_released_ledger_nano_s_support/">announcement</a> of the developers, <a href="https://www.ledger.fr/2018/11/06/fourth-edition-of-cryptotuesday-brings-6-new-additions-to-ledgers-application-list/">announcement</a> of Ledger)</p><p>· The release of <a href="https://www.myfactomwallet.com/#/">MyFactomWallet</a>, although online a complete client side, easy and safe way to manage your Factoids, with integration of the Ledger Nano S.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*hDpoLsedqioQGdkyQh2Bgw.png" /></figure><p>· Legal review of our governance. Although not as sexy, we believe that having a proper governance and making sure we do everything in our power to be compliant with laws and regulations is paramount for any blockchain project targeted at enterprise usage</p><p>· A Factom Android and <a href="https://github.com/bi-foundation/factom-java">Java client</a> for developers. Besides the existing <a href="https://github.com/PaulBernier/factomjs">Javascript</a> and <a href="https://github.com/FactomProject/factom">Golang</a> implementations this enhances the developer experience. More implementations are being worked on (Python) or are released outside of grants as well (<a href="https://github.com/FactoidAuthority/FactomSharp">#C/.NET client</a>). This means most popular software languages can now directly integrate with the Factom blockchain and not having to rely on the Factom Inc or Sphereon BaaS solutions.</p><h4>New protocol website coming</h4><p>Currently a lot of work has been done on the soon to be released new protocol website. This website will be the one stop shop for all different types of stakeholders to learn more about the Factom ® protocol, the global Data Integrity Protocol. It holds resources for developers, crypto currency investors, governance and people wanting to learn about Factom their business case(s). In the mean time Factom Inc also released their new website. The protocol website which has been created and populated by the Authority Node Operators will show a clear distinction between Factom Inc offering commercial solutions and the protocol website targeting the above audience.</p><p>We have great Factom related statistics at <a href="https://factoshi.io/">https://factoshi.io/</a> as well as a shiny new additional explorer at <a href="https://explorer.factoid.org/">https://explorer.factoid.org/</a>. If you want to find info and graphs about usage of the network, the price of the token, the locations of the teams I urge you to checkout these sites.</p><h3>Ongoing and Future work</h3><p>We recently had another grant round, which was so overcrowded that with current crypto prices we were unfortunately not able to award all parties a grant. Next grant round will be start in roughly 2 months, so if you are interested in Factom® development or becoming an Authority Node Operator, this is the time to get started. Most of the projects are currently being worked on and a lot of them will even be released next quarter. This is only the public known projects. Several companies are building new solutions on top of Factom that are not mentioned. I know because Sphereon has several projects as well as some of it’s partners. These are mostly enterprise targeted solutions. Both in infra, identity, access management. Sever based solutions as well as mobile solutions.</p><h4>Factom® Asset Token (FAT)</h4><p>One of the most impressive projects that was started 6 months ago by <a href="https://dbgrow.com/">DBGrow, Inc</a>. is <a href="https://github.com/Factom-Asset-Tokens/FAT">FAT, the Factom ® Asset Token protocol</a>. FAT will bring fungible and non-fungible tokens as well as smart contracts to the Factom ® in an efficient, modular, composable, and extensible way allowing developers to layer token functionality to meet their specific use case. FAT tokens are exceedingly efficient, with a cost of $0.012 to issue any number of tokens, and $0.001 to transfer tokens. FAT thrives in data intensive applications, such as non-fungible tokens. This efficiency is further amplified by the ability to integrate them into FAT Smart Contracts that will be able to write arbitrarily large amounts of data into the blockchain for a static $0.001 per kb of data, a feature other protocols cannot match.</p><p>The <a href="https://github.com/Factom-Asset-Tokens/FAT">FAT protocol</a> has already garnered interest from a variety of parties. It is working with <a href="https://sphereon.com/">Sphereon</a>, to create tokenized currencies with unique graph-based network properties that will be deployed in several cities in the Netherlands for government aid. Additionally, FAT has received interest in creating programmable currencies and tokenizing financial instruments like bonds and options contracts on the FAT protocol from a variety of government and corporate entities. Including American Alliance Transnational Corporation, a new holding company representing vast asset holdings, to initially tokenize two billion dollars’ worth of options contracts on the Factom Asset Token protocol.</p><h4>Decentralized Identifiers</h4><p>A DID is a Decentralized Identifier. It is a way to give an identity with a pointer (URL) to any device, organization, person, asset, document whatever fully in control of the owner of the identity. It removes the centralized component of identities we have now (large organizations like Google, FB, governments, Certificate Authorities) and makes identity management completely decentralized and self-sovereign. The trust is inferred from the shared immutable ledger (Factom). You can literally compare a DID to an URL. A traditional URL is a pointer you use to lookup webpages in a browser, a DID is a pointer to somebody’s (or something’s) identity (that certainly doesn’t mean one person would only have one DID btw. Far from it). DIDs are believed by some to become the future identity layer of the Internet. The concept is being backed by large players like Microsoft, Accenture and IBM for instance. DIDs allow for of chain storage of data in control of the holder, with verification, attestation, authentication and service discovery on Factom.</p><h4>FactomMask</h4><p>FactomMask will break down development and ux barriers, making interaction with the Factom blockchain possible from within a browser. FactomMask will store your keys encrypted safely in your browser extension, logging into MyFactomWallet will be seamless. It will provide the software equivalent to a hardware wallet in terms of key services (e.g. Transaction signing, public address query and derivation, and message signing using your identity). Ledger hardware wallet for added security. It will include identity vaults, which will allow the user to manage various logins to different sites and sign transactions on the Factom blockchain. FactomMask will be capable of integrating Factom® Identities and provide Factom-related sites/apps a secure means of access via identities. It will allow mapping DNS-style names to wallet addresses, website spoof protection, certificate authority capabilities. Extendable Capability where web developers can extend functionality through dapps and smart contracts.</p><h4>Integration into Alfresco</h4><p><a href="https://www.alfresco.com/">Alfresco</a> is working on a new customizable client on top of their populair Document Management System. This solution will be introduced during Amazon Reinvent. One of the largest IT conferences in the world. <a href="https://sphereon.com/">Sphereon</a> has been working closely with Alfresco on bringing in a fully open-source Factom blockchain integration into their new solution.</p><h4>Some other notable projects</h4><p><strong>Courtesy nodes:</strong> A courtesy node system is being put in place by several ANOs to provide courtesy nodes using a single URL with load balancing providing easy and free support to the Factom API that can be used for instance for MyFactomWallet, On-Chain Voting, the Factom Enterprise Wallet a future Factom Open-Source BaaS API, Accounting scripts or developers testing functionality.</p><p><strong>Verifiable claims:</strong> Driver’s licenses are used to claim that we are capable of operating a motor vehicle, university degrees can be used to claim our education status, and government-issued passports enable holders to travel between countries. Verifiable claims provide a standard way to express these sorts of claims on the Web in a way that is cryptographically secure, privacy respecting, and automatically verifiable. Research will be conducted to implement Verifiable claims together with DIDs on Factom.</p><p><strong>Open-source Factom BaaS: </strong>An<strong> </strong>Open-source API with advanced functions will lower barrier to entry for traditional (non-blockchain) developers &amp; developer companies and bring new developers, clients and users to the Protocol.</p><p><strong>[H]ERC:</strong> The Human Protocol, is a Supply Chain Management Platform and General Proof of Custody Provider. We leverage Factom as a Notary for our reference hashes and act as a use case for Factom as well as other decentralised solutions. Having our own blockchain or being on another more global payments settlement layer will never edge out Factom as we intend to store our references hashes in Factom, and thus in Bitcoin, throughout the entirety of our experiments, enterprise, and commercial use of our platform.</p><p><strong>Hackathons:</strong> 2 Dedicated Factom hackathons have been organized by Factom, Inc. More are being planned by other ANOs across the globe as well. Sphereon is in talks with Dutchchain to look at whether Factom can be part of the largest blockchain hackathon on the world.</p><p><strong>Hyperledger Fabric:</strong> The <a href="https://blockchain-innovation.org/">Blockchain Innovation Foundation</a> proposed a grant for anchoring data from a Hyperledger Fabric permissioned blockchain into the public Factom blockchain. This adds a public Witness to a Fabric Hyperledger network, increasing its trustworthiness.</p><h3>The year of Factom?</h3><p>As the CTO of Sphereon, working daily with enterprise and public services clients both domestic and abroad on blockchain and Factom projects, as well as being a Factom blockchain guide, working daily with a lot of talented people in the Factom ecosystem, I certainly believe this is the year of Factom. The year where the foundation for the future of Factom has been made a reality. The year where people will finally notice where the project is heading, and the year people will look back at and agree that this was the year where Factom took off. In terms of resources, talent, integrations, use cases, decentralization. The year where development accelerated at an unbelievable rapid pace. The year where the price of FCT did in no way do justice to what has been achieved behind the scenes. Maybe the strength alone of the people behind the project already could have made this the year of Factom. The fact that they continue to #BUIDL shows true determination. It is the start of becoming the global Data Integrity Protocol. Definitely “the Year of Factom” as a visionary already mentioned.</p><p>(this is the start of several future pieces about Factom)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=704c72a66521" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>