<?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 Dimitri De Jonghe on Medium]]></title>
        <description><![CDATA[Stories by Dimitri De Jonghe on Medium]]></description>
        <link>https://medium.com/@DimitriDeJonghe?source=rss-86da257a59b6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*G7v60EyWKcqra1K5.jpg</url>
            <title>Stories by Dimitri De Jonghe on Medium</title>
            <link>https://medium.com/@DimitriDeJonghe?source=rss-86da257a59b6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 03:39:02 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@DimitriDeJonghe/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[Building Rare Effect — decentralized, virtual and interactive]]></title>
            <link>https://medium.com/keyko/building-rare-effect-decentralized-virtual-and-interactive-c61e68d1e787?source=rss-86da257a59b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/c61e68d1e787</guid>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[arts3]]></category>
            <category><![CDATA[cryptoart]]></category>
            <category><![CDATA[rareeffect]]></category>
            <category><![CDATA[decentralization]]></category>
            <dc:creator><![CDATA[Dimitri De Jonghe]]></dc:creator>
            <pubDate>Wed, 17 Feb 2021 17:03:12 GMT</pubDate>
            <atom:updated>2021-02-17T23:57:27.524Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introducing Arts 3.0</h3><h4>A New Value Paradigm for Creatives</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EVOkq4Q_CjiRovv1br0FLg.jpeg" /><figcaption>A mobile screenshot from my talk in VR about <a href="http://New Value Paradigms for Digital Artists">New Value Paradigms for Digital Artists</a> @ Rare Effect</figcaption></figure><h3>Our Journey in Arts 3.0</h3><p>In the past months the Keyko Dōjō has been merging forces with local and global creative and arts communities in Lisbon, veteran web3 development houses and underground event organizers to form <a href="https://linktr.ee/artprogression.now">Art Progression Now</a> (APN). Our mission: to show artists, collectors, builders and investors that “creativity is a basic human right” which demands a new value paradigm.</p><p>Here are some articles that explain who we are and what our mission is:</p><ul><li><a href="https://medium.com/keyko/the-rare-effect-exhibition-50c1b3fb77d0">Arts Progression Now presents the first “Rare Effect” Exhibition</a></li><li><a href="https://medium.com/keyko/rethinking-provenance-ownership-and-the-distribution-of-art-d3191bbfa01f">Rethinking Provenance, Ownership and the Distribution of Art</a></li></ul><p>In this post, I will briefly describe our mission, coined “Arts 3.0” and then deep dive into what we’ve built and our plans for the future.</p><h3>Arts Progression Now</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aXEyaviz2ZL7pQXjkaZK2Q.png" /><figcaption>Check out <a href="https://medium.com/u/69a316bf9043">Jesse Steele</a>’s talk on <a href="https://www.youtube.com/watch?v=1L3Om989IBE&amp;ab_channel=ArtProgressionNowAPN">DAO Identity</a> on APN’s Youtube Channel</figcaption></figure><p>With Arts Progression Now we committed to onboard, build and deploy web3 solutions that empower artists. This means that we leverage the power of decentralization, blockchain and tokens to explore new value paradigms for artists.</p><p>Hereto we coin a new term: <strong>Arts 3.0</strong>.</p><h3>Arts 3.0</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y0HYl-a3TjPri_Nr4mQjhQ.png" /></figure><p>Following the analogy of web 3.0 where the consumer from web 2.0 is being rewired to include self-sovereignty and neutral, open infrastructure for value sharing, we can frame Arts 3.0 as an evolution of (digital) arts.</p><p>The key concepts of Arts 3.0 are the digitization of the arts or the provenance attached to specific artwork or artists, as well as the addition of a programmable value layer using the power of blockchain, tokens and smart contracts. As a side note: physical artworks can have a digital twin that leverages unique identifiers and cryptographic-secured NFC tags to record the provenance in a digital and self-sovereign fashion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5zmyAH2MWug6xyurDRvj5w.png" /></figure><p>Unpacking Arts 3.0 reveals a few new paradigms and additional layers of infrastructure that artists can take advantage of.</p><p>First of all, the artist is able to tokenize the artworks using Non-fungible Tokens (NFTs). This means that the artists are publishing their artworks and licensing/ownership rights themselves without being bound to a label or publishing company. Moreover, with the idea of unique editions, digital arts can be copied while protecting ownership of title, hence introducing a novel form of digital scarcity.</p><p>Second of all, once the NFTs are minted, the artist can leverage decentralized finance (DeFi) tools to orchestrate the value flow around the artwork. This opens up many possibilities such as revenue splits, fractional ownership, earning from secondary market sales, new types of auctions, pricing algorithms and improved liquidity, access to money markets that provide borrowing, lending, collateralization, strategy vaults, gambling and so forth.</p><p>All of the above can only be possible in an open, permissionless infrastructure where standards and norms are available such that value can be compounded: an NFT could have a fractional ownership structure that borrows some shares in order to lend other NFTs and earn interest on top of that. This is just one small example, but DeFi lovers will know how to compound value. ;)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Zbg0G4jrVfgQs280" /></figure><h3>Rare Effect Framework</h3><p>We took our mission and experience into action and started collaborating in a virtual exhibition we call “Rare Effect”. It’s meant to give artists a global and open platform to display their artworks, make it available on the marketplace, run interactive events and performances and collect new ideas.</p><p>The name Rare Effect comes from squashing together “Rare, Fair and Rekt”:</p><ul><li>Rare: Digital scarcity, provenance &amp; attribution.</li><li>Fair: New forms of value distribution and community governance.</li><li>Rekt: Adding speculation and gamification to entertain collectors and investors.</li></ul><h4>Virtual Gallery</h4><p>Our virtual Gallery is hosted on <a href="https://www.cryptovoxels.com/play?coords=N@331W,127N">CryptoVoxels</a> and was gratefully offered to us by our partner <a href="https://mintbase.io/">Mintbase</a>. Once we had access to this digital property, our creative builder <a href="https://twitter.com/Serste2">Serste</a> modeled the space with the same look and feel as our partner <a href="https://arrozestudios.pt/">Arroz Estudios</a>.</p><p>The textures and walls are exactly what you can find when you come over to Lisbon to visit this magical gallery in the middle of the harbor. People can explore the gallery, interact with the artworks, chat with other visitors, have a party, enjoy the talks and streams and so forth.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*uWkOqEw_LaotMAjKvTjfKQ.gif" /></figure><h4>Stream: Talks, Interviews, DJ sets, Arts-on-the-loop</h4><p>Since we’re collaborating with Arroz Estudios and the local arts community in Lisbon, we managed to line up a sick program for 10 days, introducing 11 artists, numerous talks, interviews, DJ sets, live performances, short movies and parties. It’s a pretty <a href="https://www.youtube.com/channel/UCNg2GRLXJKcFxV1jPoacb5g">amazing channel to tune into!</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/635/1*DCWQvpDEtakDKb1gfRHBag.png" /></figure><p>We stream everything through twitch (and sometimes there’s a glitch) and broadcast directly to our screen in CryptoVoxels, as well as on YouTube and Facebook. The recordings are all made available so you can watch them later.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BVkxJWQq3kUMy4hozhP5Zw.gif" /></figure><h4>NFT Marketplace</h4><p>After our call for artists and some curation and selection we ended up with a selection of stunning art from 16 creators:</p><p>•abysms •Amir Shayesteh Tabar •burst_ •Daniele Grosso •Eddie Ivers •Emmanuel Koto •Erica Doo •Islam Allam •Ivelina Ivanova •Kibo •Laura Penez •Pawel Mendrek •Rivka Dette •Sandra Araújo •Sandrine Deumier •Sean Mick</p><p>The artworks are in our virtual gallery and can be purchased with a click. You will be linked to our decentralized application on<a href="https://rareeffect.io/"> rareeffect.io</a> and from there you can buy on mintbase or make a bid on opensea.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2Z6u6ZG9czDRYF1Zq8JJFA.gif" /></figure><h4>Crypto-Interaction: Performances and Artworks with a decentralized App</h4><p>Did I already mention we made an app, a decentralized one (a dApp)? If not, then here it is: <a href="https://rareeffect.io/">rareeffect.io</a>. This app makes you interact with the blockchain without the need to know or set up much. At least that’s what we aimed for...</p><p>The application has:</p><ul><li>A gallery view and artwork view to browse and purchase arts.</li><li>A “burner wallet with zero setup” to allow for gamified interaction with game tokens ($GRAIN) on the rinkeby testnet of ethereum.</li><li>Token Airdrops to become a $GRAIN whale by finding secrets and redeeming them for tokens.</li><li>Voting on the choices during live performances using with Bonding Curves from the NFette tooling provided by <a href="https://www.linumlabs.com/index.html">Linum Labs</a>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QmgZp0DA-dbgBMOdfjU8vw.gif" /><figcaption>You can use the Rare Effect App to interact with the artworks &amp; performances</figcaption></figure><p>Here you can see how everything ties together during an interactive virtual dance performance of the artist<a href="https://www.instagram.com/dette.art/"> Rivka Dette</a>. While being broadcasted live, visitors can vote with their airdopped $GRAIN tokens to influence the storyline of the performance. It gets very meta very soon.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/460/1*oEtFbJeaKkpT-a7CvzB12A.gif" /><figcaption>Footage from Rivka Dette’s performance complete with crypto enabled voting</figcaption></figure><h3>What’s Next?</h3><p>We have a lot of ideas, great energy and can’t wait to make our virtual experience even better. Here is what you can expect…</p><h4>Physical Exhibition Twin</h4><p>Once the COVID measures relax and we can host physical events, we’ll do another edition of Rare Effect with a physical exhibition as well. Everything will be connected. :)</p><h4>Arts 3.0 Events Platform</h4><p>We’re keen on modularizing our platform as well as putting our code in the open-source domain. This way you can fork and we can merge your requests!</p><h4>Decentralized Organization &amp; Tokenization</h4><p>Obviously, we also want to migrate to an open and incentivized community. This means we’re thinking of creating a governance token, an asset reserve and a voting structure around that. Stay tuned!</p><p>Article written by <a href="https://twitter.com/DimitriDeJonghe">Dimitri De Jonghe</a> in close collaboration with Metaxu Labs: <a href="https://twitter.com/malte_slk">Malte Sielski</a>, <a href="https://twitter.com/e11io11">Elliott Brunet</a>, <a href="https://twitter.com/amha_samson">Samson Mulugeta Amha</a>, <a href="https://medium.com/linum-labs">Linum Labs</a>: <a href="https://twitter.com/Paulapbpb">Paula Pettit</a>, <a href="https://medium.com/@w.s.schwab">William Schwab</a>, <a href="https://www.loominate.co/">Loominate</a>, <a href="https://www.linkedin.com/in/jessewsteele/">Jesse Steele</a>, <a href="http://patrickcaire.com/">Patrick Caire</a>, <a href="https://www.rivkadette.com/welcome">Rivka Dette</a>, <a href="https://twitter.com/ArrozEstudios">Arroz Estudios</a>: Steven McKay, Cintia Pinto, <a href="https://twitter.com/mintbase">Mintbase</a>: <a href="https://twitter.com/CarolinWend">Carolin Wend</a>, <a href="https://twitter.com/nategeier">Nate Geier</a>, <a href="https://twitter.com/Serste2">Serste</a>, <a href="https://twitter.com/FiresMouth">Gianluca Boccadifuoco</a> and all other members of <a href="https://twitter.com/artprogressnow">Arts Progression Now</a></p><blockquote>Keyko is a Web 3.0 solutions provider offering integrated decentralized solutions and advisory for enterprise and startups. We thrive on providing organizations and individuals insights into this emerging digital world where capitalism and ownership are being profoundly rethought.</blockquote><blockquote>If you would like to know more about our services or are interested in having a chat please reach out to us on info@keyko.io or visit our website <a href="https://www.keyko.io/">here.</a></blockquote><blockquote>If you enjoyed this article let us know by clapping or leaving your comment below</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c61e68d1e787" width="1" height="1" alt=""><hr><p><a href="https://medium.com/keyko/building-rare-effect-decentralized-virtual-and-interactive-c61e68d1e787">Building Rare Effect — decentralized, virtual and interactive</a> was originally published in <a href="https://medium.com/keyko">Keyko</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Exploring the SEA: Service Execution Agreements]]></title>
            <link>https://blog.oceanprotocol.com/exploring-the-sea-service-execution-agreements-65f7523d85e2?source=rss-86da257a59b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/65f7523d85e2</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[service-agreement]]></category>
            <category><![CDATA[homepage]]></category>
            <category><![CDATA[technical-architecture]]></category>
            <dc:creator><![CDATA[Dimitri De Jonghe]]></dc:creator>
            <pubDate>Fri, 30 Nov 2018 09:23:33 GMT</pubDate>
            <atom:updated>2018-12-05T11:22:29.309Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>This blogpost expands on the <a href="https://blog.oceanprotocol.com/a-deep-dive-into-ocean-protocol-design-8fe78fcf8aa">technical architecture of Ocean Protocol</a>. Specifically we’ll deep dive into Service Execution Agreements (SEAs). SEAs glue together services providers, consumers and verifiers in the Ocean Protocol Network.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jgw_2h5o7ZzjmhAaQgfR9g.jpeg" /><figcaption>Ready to conquer the SEAs… [credits: <a href="https://medium.com/u/6c175db80c87">Kwinten Crauwels</a>]</figcaption></figure><p>In our previous posts [<a href="https://blog.oceanprotocol.com/captains-orders-tis-the-season-for-shipping-d2551982f467">1</a>, <a href="https://blog.oceanprotocol.com/oep-11-service-agreements-63421ca76d9f">2</a>], we referenced why it became clear that Service Level Agreements or SLAs pretty much hold together the world as we know it. Entire physical and digital service supply chains are being glued together by contractual bindings to mitigate counterparty risk, enforce availability, reliability and uptime.</p><p>In the Ocean Network we care about data and AI services being fairly exchanged, protecting all ends of the business transaction. This way terms and conditions of a service agreement are known upfront without relying on an external party for dispute inter-mediation. Service Agreements and their life cycle form the basis for:</p><ul><li>Decentralized access control</li><li>Dispute resolution</li><li>Provenance of service consumption</li><li>Network rewards and incentives</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F8TlR1VbuOw0di8_UVCGkg.png" /><figcaption>Pay-for-Service or Service-for-Pay? A chicken or egg problem…</figcaption></figure><p>In the remainder of this post we’ll have a more technical deep dive in the concepts of SEAs that are deployed in the Ocean Network.</p><h3>Unhappy Paths in Service Execution</h3><p>A lot can go wrong when dealing with data services. We’ll depict a few cases here, but many more can exist at the edge cases:</p><ul><li>Services might not exist, although the consumer paid for them.</li><li>Services might be delivered correctly, however the consumer refuses or forgets to reward the service provider.</li><li>Service providers might not grant access to rightful users or do grant access to non-rightful users.</li><li>The service didn’t meet the functional requirements or performance expectations of the consumer.</li><li>Service response or logs got “lost” in the network or translation.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ki3BlbuBa4ezYKPW7ej2BQ.png" /><figcaption>Some unhappy paths in the world of service request/response.</figcaption></figure><p>There are many ways to survive such disaster scenarios. A typical procurement division would establish <em>legal agreements</em> between the suppliers and consumers. Digital services have the ability to add layers of <em>mathematical security</em> (encryption, signatures, hashes, cryptographic proofs &amp; attestations) and automation.</p><p>Distributed service networks give a layer of <em>redundancy</em> at the cost of replication. As the trust level decreases, for example in the case of (anonymous) permission-less networks, one can explore <em>economic and reputational incentives</em> that utilize the underlying native token.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x2p92prI0Y6wbuuT6V1i2w.png" /><figcaption>Shades of Service Agreements and trust (red: low trust / green: more trust)</figcaption></figure><p>The more critical a service is within a supply chain, the more stringent the levels of guarantees that need to be enforced. One can imagine that an early warning system for natural disasters requires a higher level tolerance level than the humidity sensor in my basil plant (arguably, though).</p><h3>Everyone has Conditions</h3><p>Similar to the way legal SLAs in procurement have Terms and Conditions, Ocean SEAs have conditions that can be embedded as code in a smart contract.These conditions need to be fulfilled by the counterparties in the agreement.</p><p>As an example we depict a scenario where a Provider delivers a verified data service to a Consumer. Such a data service can vary from a simple data retrieval to complex computation in a Machine Learning (ML) or Artificial Intelligence (AI) environment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Glvfmqd_Xkm92VZJVMJ0xQ.png" /><figcaption>Three parties engaging in a service agreement.</figcaption></figure><p>In the above scenario, a <em>Provider</em> is willing to deliver a data service after a <em>Consumer</em> ensures a payment will follow upon delivery. The <em>Consumer</em> in turn will only pay if granted access to the service and the performance of the service is verified by a <em>Verifier</em>. The <em>Verifier</em> (or network of <em>Verifiers</em>) also demands to see a payment before she puts in any verification work.</p><p>The above scenario’s can be more complex or simple depending on the use case. In what follows, we’ll dive a bit deeper in how SEAs are composed.</p><h3>Anatomy of a modular Service Execution Agreement</h3><p>In Ocean Protocol, SEAs have a modular design to encompass flexibility for onboarding and consuming a variety of web2.0 (cloud/on-premise) and web3.0 services.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Tt0vxsGF6Xva1yg8clW6cA.png" /><figcaption>Components of a Service Execution Agreement.</figcaption></figure><p>We identify three main parts in a SEA:</p><h4>Service Identifier</h4><p>A cryptographic ID that uniquely identifies the service to be consumed. The actual metadata and endpoint/access details of the service are kept off-chain for both scale and privacy reasons. Such details can be communicated peer-to-peer or <em>resolved</em> in a permissioned or permissionless metadata network.</p><p>Since we encourage standards and interoperability we’ve chosen to adopt the emerging <a href="https://w3c-ccg.github.io/did-spec/">W3C Decentralized Identity (DID)</a> standard. Agents, Services and Domains are addressed by a DID (e.g. “<em>did:op:12345s3rv1c3”</em>) in Ocean Protocol. Their respective DID documents — which contain metadata and service consumption information — live on public/permissioned/private data stores. We’re moving towards Ocean Identifiers with integrity checks, versioning and non-repudiation. More information about our implementation can be found in <a href="https://github.com/oceanprotocol/OEPs/tree/master/7">OEP7</a>.</p><h4>Conditions and Fulfillments</h4><p>In an imperfect world, we are dealing with off-chain, on-chain, side-chain and other-chain services and events. These services can either execute correctly, almost correctly or even fail. At some point in time the Ocean SEAs will be interested in knowing the status of these services in order to settle or resolve disputes.</p><p>Hence we introduce conditions and fulfillments. In short, we’re talking about cryptographic and non-cryptographic conditions that can be fulfilled. Each condition has a validation function that returns either <em>“True”</em>, <em>“False“</em> or <em>“Unknown”</em>. <em>“Unknown” </em>values imply that a condition has not been provably fulfilled. All conditions start out as <em>“Unknown”</em>. The validation logic is executed on-chain. Conditions can be regarded as the <em>inputs</em> to a SEA.</p><p>Conditions allow us to flexibly encode <a href="https://oceanprotocol.com/tech-whitepaper.pdf">Proof-of-Service</a> into SEAs. Conditions are the challenges to be solved and fulfillments are the solutions. Reward logic distributes the outputs depending on the fulfilled conditions. Such conditions can vary from simple cryptographic challenges (e.g. provide a pre-image that computes a hash with trailing zeros, or prove that you have the private key corresponding to a public key), to more complex ones (e.g. SN/TARKs, compute attestations, proof-of-spacetime, proof-of-retrievability) and to more subjective ones (e.g. <em>m-of-n</em> signatures in a voting or curation scenario, stake/slash, …).</p><p>When validation events occur in non-Ocean networks, conditions can simply link to oracles or bridge contracts to resolve the dispute.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a0CRQlNR8rly7aFdCjY_xQ.png" /><figcaption>From conditions over fulfillments to rewards. Conditions are the challenges to be solved and fulfillments are the solutions (green: fulfilled/valid, orange:unfulfilled/unknown, red:invalid). Reward logic distributes the outputs depending on the fulfilled conditions.</figcaption></figure><p>The actual implementation of conditions and fulfillments is a variant of the <a href="https://tools.ietf.org/html/draft-thomas-crypto-conditions-04">crypto-conditions</a> IETF draft, initiated by the Interledger protocol. Each condition/fulfillment is a cryptographic challenge/proof pair such as:</p><ul><li><em>hash / pre-image</em>: find a pre-image that computes to a given hash. The computation of the hash of the pre-image happens on-chain. This condition is useful for a party to prove that they have knowledge of a secret.</li><li><em>public key + message / signature</em>: sign a given message with a private key corresponding to a given public key. The verification of the signature happens on-chain. Useful to prove an identity in an asymmetric key pair scheme.</li><li><em>m-of-n threshold</em>: validates to <em>“True”</em> if <em>m</em> out of <em>n</em> conditions have been correctly fulfilled. Useful for multi-party dispute resolution such as voting.</li><li><em>query/resolve</em>: link to a publicly available state value (that is recorded with a timestamp) and resolve/compare that value upon validation. The query is executed on-chain, hence it’s limited to GET operations within the state context of the chain (e.g. <em>contractAddress.getValue</em>). Useful to bridge services and oraclize off-chain values.</li></ul><p>Conditions can be combined in more complex logic to express:</p><ul><li><em>payment conditions: the amount of token submitted to the contract equals the predefined token price.</em></li><li><em>access control: an access-control secret has been communicated with the Consumer. [see also </em><a href="https://blog.oceanprotocol.com/secure-on-chain-access-control-for-ocean-protocol-38dca0af820c"><em>this post</em></a><em>]</em></li><li><em>verified compute: a network of Verifiers agrees and signs that a service was correctly delivered or not. [link to post coming soon]</em></li></ul><p>We foresee that multiple conditions can emerge in the ecosystem, hence careful audits and curation is required to green-light those conditions that can be safely plugged into a SEA. In the future, we can make use of governance contracts such as <a href="https://medium.com/@ilovebagels/token-curated-registries-1-0-61a232f8dac7">Token-Curated Registries</a>, <a href="https://medium.com/@DimitriDeJonghe/curated-governance-with-stake-machines-8ae290a709b4">stake machines</a> or DAOs.</p><h4>Reward logic</h4><p>The outputs of a <em>SEA</em> are rewards that are typically distributed to agents that have fulfilled one or more conditions. Rewards can be issued in the form of payments, royalties, permissions, badges, reputation or lottery tickets for a network reward function, and so on. As multiple reward mechanics can be envisioned, they are consolidated in governed templates, similar to the library of conditions.</p><p>A basic reward structure implemented in Ocean Protocol is the <em>Escrow or Hold token. </em>Here tokens are locked up in an SEA in order to be either:</p><ul><li><em>Executed</em> if all conditions are fulfilled before a timeout occurs. Executing the payment means that the locked token can be transferred to the receiving party.</li><li><em>Aborted</em> if not all conditions are fulfilled after the timeout occurs. Aborting the payment means that the locked token is returned to the issuing party.</li></ul><p>In future releases we will target more complex reward schemes such as payment streams, bounties, competitions and royalty schemes.</p><h3>The Life of a Service Execution Agreement</h3><p>Having all components of a SEA in place, one can start publishing services, attaching a SEA and interact on marketplaces with consumers. We’ll explain each step in a bit, but first some more details.</p><h4>Service Publication</h4><p>A provider can provision services by defining metadata (see <a href="https://github.com/oceanprotocol/OEPs/tree/master/8">OEP8</a>) and API calls for access, consumption and monitoring (see <a href="https://github.com/oceanprotocol/OEPs/tree/master/11">OEP11</a>).</p><p>Next, the provider takes on the role as a publisher (or delegates that role) in a marketplace. A publisher chooses a SEA from the templates and includes it in the Service Identity Document before publishing in a marketplace [see <a href="https://github.com/oceanprotocol/OEPs/tree/master/11#publishing">here</a> for details]. Publishing methods range from <a href="https://github.com/oceanprotocol/aquarius">a public metadata store (called Aquarius</a>) over Web APIs/forums or peer-to-peer messaging.</p><p>Once a service is published, it can be discovered by a consumer. This will lead to both parties instantiating a SEA by signing and executing the agreement [see <a href="https://github.com/oceanprotocol/OEPs/tree/master/11#consuming">here</a> for details].</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5tHl9_uYKPDH7bXKF6Zo5Q.png" /><figcaption>Ocean Protocol’s publishing flow: From Resource to Service Execution Agreement.</figcaption></figure><p>Next up, we’ll be exploring a few lifecycles of various SEAs during their operation.</p><h4>Access Control</h4><p>One elementary SEA is provisioning <a href="https://github.com/oceanprotocol/brizo">access control to off-chain resources</a> with escrow-ed rewards. This use case is explained more in detail <a href="https://blog.oceanprotocol.com/secure-on-chain-access-control-for-ocean-protocol-38dca0af820c">in this post</a>. Here are the relevant events for the SEA:</p><ol><li><em>Sign and Execute:</em> Both parties agree and an instance of the Access Control SEA is created.</li><li><em>Payment:</em> Consumer locks up the required token amount in escrow.</li><li><em>Access:</em> The service Provider grants access to the resource and reports this event on-chain.</li><li><em>Rewards:</em> The escrow will either execute or abort, taking the <em>access condition</em> and <em>timeout</em> into consideration.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NnhmRqcTwlXCm9EObJ7Upg.png" /><figcaption>Life of a Simple Acces Control SEA after publication.</figcaption></figure><p>Notice that in the off-chain access control scenario, it is only proven that some access token has been communicated, not that the token was actually valid and consumed in a session.</p><h4>Verified Services</h4><p>A more complex use case extends the above access control by adding verification events to the service [work in progress, coming up in a next release]. Here, the resource provider submits one or more service proofs or attestations to a Verifier network.</p><p>The Verifier network is tasked with resolving disputes about the performance of the service (e.g. <a href="https://github.com/oceanprotocol/ocean/issues/165">Truebit</a>, <a href="https://github.com/oceanprotocol/ocean/issues/18">fitchain</a>, E<a href="https://github.com/enigmampc">nigma</a>, F<a href="https://github.com/filecoin-project">ilecoin</a>, etc.). Here, the SEAs are connected by either an oracle or bridge contract that can be queried using query conditions. Hence, the SEA will be able to simply link and resolve the dispute resolution outcome of the Verifier network.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2X0_AqACu7ry7Jxaodh8uw.png" /><figcaption>An external verifier network used for validating proofs-of-service and bridging the outcome of the dispute resolution cycle.</figcaption></figure><h4>Putting it all together</h4><p>As a summary, we’ve laid the groundwork in order to put all events in the life of a SEA togther. Notice that multiple SEAs can easily be executed in parallel. Off-/side-chain resources and authorization servers simply need to listen to the pre-defined events emitted from the SEA.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U-DedkHrpSvCYU99hJoEzQ.png" /><figcaption>The life of a Ocean Protocol SEA from publishing to consumption and validation.</figcaption></figure><h3>Conclusion</h3><p>We introduced the anatomy and life cycle of Ocean Protocol’s Service Execution Agreements. These agreements are the basis for provable provenance, dispute resolution, reward mechanics and so on. They’re basically the glue that connect the data services in the Ocean Protocol Ecosystem and beyond.</p><p>Now that you know there are SEAs in the Ocean, go ahead and…</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FwBzhgMlpcuag8%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FwBzhgMlpcuag8%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FwBzhgMlpcuag8%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="256" frameborder="0" scrolling="no"><a href="https://medium.com/media/8b067447b83c206db996db381267edba/href">https://medium.com/media/8b067447b83c206db996db381267edba/href</a></iframe><p>Thanks to <a href="https://medium.com/u/9104a5aaeb71">Don Gossen</a>, <a href="https://medium.com/u/8ab281366479">Aitor Argomániz</a>, <a href="https://medium.com/u/f1e17af9a3ea">Fang Gong</a>, <a href="https://medium.com/u/ff2c9ae5d5a3">Ahmed Ali</a>, <a href="https://medium.com/u/6c175db80c87">Kwinten Crauwels</a>, <a href="https://medium.com/u/43c527adde71">Sebastian Gerske</a>, <a href="https://medium.com/u/27170c3d395b">Emily Hirschberg</a>, <a href="https://medium.com/u/b1195533f664">Stefan Thomas</a>, <a href="https://medium.com/u/8b3554d951df">Evan Schwartz</a>, <a href="https://medium.com/u/68468a2d58be">Francesco Gadaleta</a>, <a href="https://medium.com/u/7cb369a906d7">John Enevoldsen</a>, <a href="https://medium.com/u/bdcb9406216f">Troy McConaghy</a>, <a href="https://medium.com/u/43cbf13aebc9">Bruce Pon</a> and <a href="https://medium.com/u/f1cb98e196bc">Trent McConaghy</a> for inspiration, collaboration and edits.</p><p>Useful links:</p><ol><li><a href="https://blog.oceanprotocol.com/a-deep-dive-into-ocean-protocol-design-8fe78fcf8aa">Deep dive into Ocean Protocol design: <em>https://blog.oceanprotocol.com/a-deep-dive-into-ocean-protocol-design-8fe78fcf8aa</em></a></li><li><a href="https://blog.oceanprotocol.com/captains-orders-tis-the-season-for-shipping-d2551982f467">Trilobite release:<em> https://blog.oceanprotocol.com/captains-orders-tis-the-season-for-shipping-d2551982f467</em></a></li><li><a href="https://github.com/oceanprotocol/OEPs/tree/master/7">OEP7 — Decentralized Identifiers in Ocean Protocol: <em>https://github.com/oceanprotocol/OEPs/tree/master/7</em></a></li><li><a href="https://github.com/oceanprotocol/OEPs/tree/master/8">OEP8 — Metadata Ontology: <em>https://github.com/oceanprotocol/OEPs/tree/master/8</em></a></li><li><a href="https://blog.oceanprotocol.com/oep-11-service-agreements-63421ca76d9f">Introducing OEP11: <em>https://blog.oceanprotocol.com/oep-11-service-agreements-63421ca76d9f</em></a></li><li><a href="https://github.com/oceanprotocol/OEPs/tree/master/11">OEP11 — Service Execution Agreements: <em>https://github.com/oceanprotocol/OEPs/tree/master/11</em></a></li><li><a href="https://github.com/oceanprotocol/aquarius">Ocean Metadata — Aquarius: <em>https://github.com/oceanprotocol/aquarius</em></a></li><li><a href="https://github.com/oceanprotocol/brizo">Ocean Access Control — Brizo: https://github.com/oceanprotocol/brizo</a></li><li><a href="https://blog.oceanprotocol.com/secure-on-chain-access-control-for-ocean-protocol-38dca0af820c">Secure On-chain Access Control for Ocean Protocol: <em>https://blog.oceanprotocol.com/secure-on-chain-access-control-for-ocean-protocol-38dca0af820c</em></a></li></ol><p>We hope you are ready to dive in — check out <a href="https://github.com/oceanprotocol/dev-ocean">Dev-Ocean</a> to get a sense of what we’ve been working on, and fire all your technical questions in <a href="https://gitter.im/oceanprotocol/Lobby">our Gitter chatroom</a>.</p><p>Follow <strong>Ocean Protocol</strong> on <a href="https://twitter.com/oceanprotocol">Twitter,</a> <a href="https://t.me/joinchat/GUyxrE0Hi154D0NrlOqLFg">Telegram</a>, <a href="https://www.linkedin.com/company/ocean-protocol/">LinkedIn</a>, <a href="https://www.reddit.com/r/oceanprotocol/">Reddit</a>, <a href="https://github.com/oceanprotocol">GitHub</a> &amp; <a href="https://oceanprotocol.com/newsletter/">Newsletter</a> for project updates and announcements.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=65f7523d85e2" width="1" height="1" alt=""><hr><p><a href="https://blog.oceanprotocol.com/exploring-the-sea-service-execution-agreements-65f7523d85e2">Exploring the SEA: Service Execution Agreements</a> was originally published in <a href="https://blog.oceanprotocol.com/">Ocean Protocol</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Can you provide an example?]]></title>
            <link>https://medium.com/@DimitriDeJonghe/can-you-provide-an-example-e162bb3ef557?source=rss-86da257a59b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/e162bb3ef557</guid>
            <dc:creator><![CDATA[Dimitri De Jonghe]]></dc:creator>
            <pubDate>Thu, 25 Oct 2018 11:27:53 GMT</pubDate>
            <atom:updated>2018-10-25T11:27:53.273Z</atom:updated>
            <content:encoded><![CDATA[<p>Can you provide an example?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e162bb3ef557" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ocean Protocol Advisor— Prof. Dr. Sebastian Gajek]]></title>
            <link>https://blog.oceanprotocol.com/ocean-protocol-advisor-prof-dr-sebastian-gajek-5f7e3bd60802?source=rss-86da257a59b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/5f7e3bd60802</guid>
            <category><![CDATA[people]]></category>
            <category><![CDATA[cryptography]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[data-science]]></category>
            <dc:creator><![CDATA[Dimitri De Jonghe]]></dc:creator>
            <pubDate>Tue, 02 Oct 2018 07:50:04 GMT</pubDate>
            <atom:updated>2018-10-02T07:53:43.375Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>30+ leaders are bringing their capabilities and expertise to help launch a Data Economy around Ocean</strong></p><p>In the deep waters of the crypto-underworld, we’ve noticed that <a href="https://weeve.network/">Weeve</a> is making waves with a serious impact. Their secret? A smooth and creamy combination of academic rigour and cryptography, with a pinpoint market focus. This vision was laid out to us by Prof. Dr. <a href="https://twitter.com/weeveSebastian">Sebastian Gajek</a>, Weeve Co-founder &amp; CTO and Professor in Cryptography at Flensburg University.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t2Mkils3AKwoLtSwj14D-g.jpeg" /></figure><p>Sebastian’s dedication to cryptography extends beyond his work and into his everyday life — he has a genuine pet <a href="https://dogecoin.com/">doge</a> — and we admire his quickness to connect to others, as well as the ease and energy with which he engages the Weeve community <a href="https://medium.com/weeves-world/singapore-to-shanghai-weeve-in-asia-e62bb787cbba">worldwide</a>.</p><p>Ocean Protocol cares about provenance, as it implies attribution, forensics and fair value capture. Provenance of data starts with the data generation device itself, hence the need for trusted data oracles is a holy grail for the supply side in the Ocean network. Even better is that these trusted data sources can come from IoT or embedded devices and have hardware security to prevent attacks. Add a secure compute layer? weeveOS can do it all.</p><p>Sebastian gave us great insights in their Token Curation development such as <a href="https://medium.com/coinmonks/graded-token-curated-decisions-with-up-downvoting-designing-cryptoeconomic-ranking-and-2ce7c000bb51">the graded TCR</a>. More importantly is that many of their developments, research and insights are being widely shared in the open source community. This proves that Sebastian has his values truly aligned with Ocean Protocol: democratize access to knowledge and intelligence, and that communities precede economies.</p><p><strong>Two Minutes with Sebastian Gajek</strong></p><p><strong>Why are you supporting Ocean Protocol?</strong></p><p><em>Ocean Protocol amasses all that is needed to change the digital world of tomorrow and I am humbled that I have a ‘Berghain Bouncer’ nod to enter into Ocean’s ocean and help make waves. It is my firm belief that data, as an emerging digital asset, prerequisites with a need for assessment in order to activate it’s value. With this being said, Ocean’s innovative techniques in Mechanism Design are carving the path forward for this to happen. The talented team always delivers on ambitious visions and I see no reason to doubt their ability to change the digital world of tomorrow (*Grabs arm bands and jumps in*).</em></p><p><strong>What capabilities will you bring as an Advisor?</strong></p><p><em>As a human who wears two hats, one being a researcher and the other being an entrepreneur, I look forward to continue supporting and helping Ocean in the following ways. Firstly, I am a Professor of Cryptography and Information Security and have been designing protocols and systems for just short of two decades. Blockchain and specifically blockchain-based protocols like the Ocean Protocol is a perfect application in my expertise. I look forward to help out here when needed. My second hat pertains to </em><a href="https://weeve.network/"><em>Weeve</em></a><em>, a company I founded, which addresses the problem of Trusted IoT Data Oracles using novel cryptographic proof techniques and protocols, efficient enough to be executed on IoT devices, and their monetization through data marketplaces. With these proofs, called Testimonies, the value of the truthfulness and information integrity is publicly verifiable. Therefore, with data attestation we thwart fake data and can curate high-quality Data Networks. As truthful and cryptographically verifiable data is the gas to the Ocean Protocol, it was natural to establish a partnership and work alongside each other. I am looking forward to the continued collaboration in order to build a Data Economy of truthful, factual and valuable Digital Data Assets.</em></p><p><strong>Why do you support the team?</strong></p><p><em>Clearly the team must be emphasised. The three musketeers (Bruce, Dimitri, Trent) are ingenius with the guts to advance blockchain-based AI “where no man has gone before” (Star Trek). From all the blockchain projects out there Ocean Protocol is clearly among the most elaborated ones and utilizes the power of blockchain in an out-of-the-box way. This already shows the ambitions and capabilities of the team. The team does also an awesome job to build a community utilizing the Ocean Protocol. That is key to a wide adoption of their platform.</em></p><p><strong>Biography</strong></p><p><a href="https://www.linkedin.com/in/sebastiangajek/">Sebastian Gajek</a> is a Doctor of Cryptography with over 15 years of experience. He is also a professor at the <a href="https://www.itsc.inf.hs-flensburg.de/">Flensburg University of Applied Sciences</a> and lectures on cryptography, system security and the blockchain. Prof. Dr. Sebastian Gajek is Weeve’s CTO. He has a strong focus on the topics of cryptographic algorithm design and system security. Prior to Weeve, he held a research position at NEC Laboratories Europe, where he transferred foundational security research to products. He was a postdoctoral fellow at Tel Aviv University and obtained his PhD from the renowned Horst-Görtz Institute for IT-Security, one of the leading academic institutes for information security in Europe.</p><p>He received his Doctoral Degree at age 28 and professorship at the age of 35. He has filed more than 15 patents, and he has been the author and co-author on more than 25 peer-reviewed papers published at international conferences. He speaks 5 languages, including German, English, Hebrew, C and Solidity.</p><p>Ready to dive in? Follow <strong>Ocean Protocol</strong> on <a href="https://twitter.com/oceanprotocol">Twitter,</a> <a href="https://t.me/joinchat/GUyxrE0Hi154D0NrlOqLFg">Telegram</a>, <a href="https://www.linkedin.com/company/ocean-protocol/">LinkedIn</a>, <a href="https://www.reddit.com/r/oceanprotocol/">Reddit</a>, <a href="https://github.com/oceanprotocol">Github</a> &amp; <a href="https://oceanprotocol.com/newsletter/">Newsletter</a> for project updates and announcements.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5f7e3bd60802" width="1" height="1" alt=""><hr><p><a href="https://blog.oceanprotocol.com/ocean-protocol-advisor-prof-dr-sebastian-gajek-5f7e3bd60802">Ocean Protocol Advisor— Prof. Dr. Sebastian Gajek</a> was originally published in <a href="https://blog.oceanprotocol.com/">Ocean Protocol</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Deep Dive into Ocean Protocol Design]]></title>
            <link>https://blog.oceanprotocol.com/a-deep-dive-into-ocean-protocol-design-8fe78fcf8aa?source=rss-86da257a59b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/8fe78fcf8aa</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[deeptech]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Dimitri De Jonghe]]></dc:creator>
            <pubDate>Mon, 13 Aug 2018 14:17:16 GMT</pubDate>
            <atom:updated>2018-08-13T14:17:16.749Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>This post outlines the main concepts in the Ocean Protocol design. We flesh out many higher level concepts described in the Ocean whitepaper; and introduces the idea of curation to problem tribes (groups of people solving a specific problem). Also, we lay out the different layers of the protocol stack and discuss some of the major components and capabilities.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6KKXZS3EgwchQf7-Du48Gg.png" /><figcaption>Release the Kraken! [credits: <a href="https://medium.com/u/6c175db80c87">Kwinten Crauwels</a>]</figcaption></figure><h4>Introduction</h4><p>At the current pace of digitization, we see the emergence of vast, expansive platforms that capture gargantuan amounts of data and efficiently extract intelligence from them. Users are farmed for behavioral data by platforms which maximise for data ownership. They then can steer the user behavior to outcomes that are within their favor. Data is abundant and data acquisition is growing. But the vast majority is locked up in platforms, enterprises and institutions. This leaves little resources and incentives for communities to collaborate on data and intelligence problems that can help build out a more sustainable and equitable future.</p><p>In this post we discuss how Ocean Protocol helps building out <em>Public Intelligence Networks</em>. Rent-free and open networks where humans can contribute resources such as data, compute, intellect and opinion to solve problems that humanity faces:</p><ul><li>Mapping out the state of our ecological resources and predicting the supply and demand of basic necessities like clean water, energy, food and shelter</li><li>Shedding light on and giving voice to suppressed minorities using neutral data feeds without bias or censorship</li><li>Early warning systems for disease outbreaks, space exploration and meteorite impact, fake news, digital security attacks, …</li><li>Universal recommenders for services, health, media, match making, social media triage, …</li></ul><p>The above is a just a sample of interesting fields where we believe Ocean Protocol can contribute.</p><p>One of the big questions we ask ourselves is how to incentivize communities, companies, and individuals to nurture raw data into intelligence for the commons? Data wants to be available. Knowledge can be extracted from data and open, incentivized intelligence networks have the potential to solve problems at global scale.</p><p>Those tribes that have missions with a context that is most aligned with this ideal are likely to be trail-blazers. <a href="https://seths.blog/2008/10/free-tribes-ebo/">Seth Godin’s Tribes</a> gives us many examples, and notes the visceral force behind tribalism:</p><blockquote>Tribes are the social equivalent to breathing. Their existence is like an involuntary process that creates social order.… Our value is determined by how we compare to others in the tribe, or by how large a tribe we can create.</blockquote><p>Bitcoin taught us how to pool resources in order to secure a network. The infrastructure is tokenized and the network distributes rewards related to the security (amount of hashing power) that is contributed to the overall network. The token quantifies the work/value creation (ie. security, storage and validation) of each miner in the system.</p><p>At <a href="https://blog.oceanprotocol.com/">Ocean Protocol</a> we’re intrigued by how tokenized ecosystems enable:</p><ul><li>Fair value capture and attribution across the ecosystem</li><li>Incentive designs that promote availability over walled gardens</li><li>Public markets that drive down the marginal cost of utilities</li><li>The creation of tribes with a clear Schelling point, signalling and governance structures</li></ul><p>The next question is, how can we leverage technology, ethics, and community to free data and intelligence from the status quo?</p><p>In the next section we discuss the concept of tribes. After that we’ll move into the data service supply chains following up with decentralized data services. Finally we lay out our protocol stack and conclude.</p><h3>Problem Solving Tribes</h3><p>Arguably, open source communities give us a taste on how collaborative commons could look. Similarly to enterprises and NGOs they share a mission and a vision. Online communities are very powerful [<a href="https://legacy.gitbook.com/book/hintjens/social-architecture/details">Social Architecture from Pieter Hintjens</a> is a must read]. At Ocean Protocol we want communities to flourish and solve problems at an unseen scale and pace. We coin ocean communities “<em>Tribes”</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k7aBZqppWz9NXBm1pO3bew.png" /><figcaption>A fictitious set of tribes that could (and should) exist on Ocean Protocol. Also shown: the internal structure of such a tribe.</figcaption></figure><p>Members of a tribe have consensus on the mission and the problems they are facing. Tribes can implement a governance structure using building blocks ranging from <a href="https://aragon.org/">Aragon</a> to custom <a href="https://medium.com/@DimitriDeJonghe/curated-governance-with-stake-machines-8ae290a709b4">curated governance</a>. Tribes might want to use their local token to measure the local value capture and implement local incentives structures. There are many possibilities to decouple the local tribe token from the native Ocean token, for example one can provide decentralized exchanges, automated market makers and <a href="https://medium.com/@simondlr/tokens-2-0-curved-token-bonding-in-curation-markets-1764a2e0bee5">bonding curves</a>. They manage funds, tasks and incentives whenever they feel the need to.</p><p>In this post, we prefer tribes over marketplaces. Digital tribes carry a broader basis than merely an exchange of value. They entail a Schelling point, a community, a mission and vision, incentives, local economies, signalling, curation, governance, bounties, and tasks. At Ocean Protocol, we aim to facilitate data science and problem-solving tribes to empower themselves.</p><h3>Data Service Supply Chains</h3><p>Data Science flows are evolving and are an increasingly significant driving force behind our contemporary economical, social, and political systems. At the core are <a href="https://en.wikipedia.org/wiki/Extract,_transform,_load">ETLs/ELTs</a>, <a href="https://en.wikipedia.org/wiki/Enterprise_service_bus">enterprise and/or data service busses</a>, orchestration services, data warehouses/lakes and so on. One way to look at them is that they harvest the intelligence from raw data streams in the context of the tribe’s mission. The more streams that are nurtured (parsed, cleaned, labelled, feature extracted, …), the more accurate the prediction and more valuable are the knowledge insights.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T9CNMA-ZRf9uTVEQqHwcdg.png" /><figcaption>A simple representation of a data service supply chain</figcaption></figure><p>Above is a simple representation on what such a data service supply chain for intelligence looks like. In each stage, the data is extracted, transformed and the result is persisted, analyzed, and annotated. Orchestration of these data science flows happen either within a single system or environment such as Apache Spark, Kaggle, Anaconda, scikit-learn, Keras, Tensorflow, pytorch, and many more. No matter how complex such flows become, the goals are always similar:</p><blockquote>“Efficiently extract intelligence [insights] from data”</blockquote><h4>Intelligence Extraction = Data + Algorithms + Infrastructure</h4><p>Algorithms are used to analyze data and predict future events based on historical data. Lots of data and heavy compute. Data and algorithms meet at the compute infrastructure. Where the compute capability resides is important from a viewpoint of scale, privacy and integrity. Note how this is different than actually exchanging data by transferring it over the wire.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Dbo9RDF1RniyJlhx4tDcmA.png" /><figcaption>Some ways to merge data, algorithms &amp; compute</figcaption></figure><ul><li><em>Big data</em> has a lot of inertia and doesn’t want to move [right bottom of figure]. The solution is to bring compute to the data or minimize the distance between them [right top of figure][see the <a href="https://what-if.xkcd.com/31/">FedEx Bandwidth</a>]</li><li>A sound <em>privacy</em> strategy is zero-escapes: constraints on data-escapes or model-escapes will dictate where the compute capability happens [eg. <a href="https://fitchain.io/">Fitchain</a>]. Or in zero-knowledge mode for modest problems [eg. <a href="http://openmined.org/">OpenMined</a>, <a href="https://enigma.co/">Enigma</a>]</li><li><em>“Trusted compute suppliers”</em> such that can deliver compute attestations such as Trusted Execution Environments on hardware, Multi-Party Compute networks, verifiable compute such as <a href="https://truebit.io/">Truebit</a>, or established and transparent brokers could facilitate outsourcing the compute [see <a href="https://cacm.acm.org/magazines/2015/2/182636-verifying-computations-without-reexecuting-them/pdf">this excellent paper</a> of Michael Walfish]</li></ul><p>Now that we have our basic primitives in place, let’s imagine how a decentralized version would look like…</p><h3>A Decentralized Inter-Service Network</h3><p>When striving for a maximally available data service infrastructure at lowest marginal cost, one can think of creating a public, open and rent-free market for each stage of the pipeline. Suppliers of all sorts (web2.0 &amp; 3.0) can publish their assets to decentralized tribal communes and tokenize their service value.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VizoLLnBihfiVZXG4yTMYQ.png" /><figcaption>A decentralized inter-service network.</figcaption></figure><p>One of the goals of the Ocean Network is the promotion of assets into such public networks through signalling. Another one is to connect existing data, compute, algorithm, storage, analytics networks into an inter-service network. We believe that unstoppable and incentivized intelligence pipelines have the potential to become the new backbone for problem solving communities. Of course this means bridging networks, resolving oracles, and enabling web2.0 services by on-chain authorization technology.</p><p>The Ocean Network is more a bazaar than a marketplace. Signalling makes that you know which ingredients make the most sense for your data science recipe.</p><h3>A Tokenized Protocol Stack</h3><p>The Ocean decentralised network has 3 significant layers:</p><ul><li>The <strong>Keeper</strong> layer that manages service agreements, low level access control, accounts, balances, and the incentive schema (or block reward).</li><li>The <strong>Verification </strong>layer that introduces cryptographic challenges to improve the integrity and security of the services.</li><li>A <strong>Curation </strong>layer that serves as a discovery mechanism as well as signalling and governance aspects. This layer accounts for human subjectivity.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MafJIDwyPuzB99tMpbUvWw.png" /><figcaption>Protocol layers in the Ocean Network</figcaption></figure><p>At the core of Ocean Protocol are <strong>Service Agreements running on the Keeper</strong>. Keepers maintain the shared state such as a DAG and run a decentralized virtual machine that interprets a smart contract language such as Solidity, Viper, or Rust/eWASM. The keepers will also reward good behavior in the network by minting and distributing Ocean Tokens.</p><p>Ocean Service Agreements are implemented as smart contracts that dis-intermediate between Service Suppliers and Consumers. You could reason about them as <a href="https://en.wikipedia.org/wiki/Service-level_agreement">Service-Level Agreements</a> running on a decentralized network to ensure both customer service and supplier protection. The details of the service agreements are out of scope for this blogpost, but we’ll dive into them in a later session. Here’s what you should know about them:</p><ul><li>A service agreement operates as a decentralized escrow, holding payments and warranties. Terms and conditions govern the relationship between the parties involved in the contract. The contract resolves (ie the contract “executes” or “aborts” the payments) by means of fulfilling sufficient conditions in the contract [inspired by the <a href="https://interledger.org/rfcs/0003-interledger-protocol/">Interledger Protocol</a>].</li><li>The contracts are used for authorization in our <a href="https://github.com/oceanprotocol/OEPs/tree/master/10"><strong>decentralized access control</strong></a> protocol. Off-chain services are connected to Ocean Protocol by means of a plugin system for asset suppliers.</li><li>The conditions for resolving the contract reflect the quality of service delivery.</li></ul><p>Ocean <strong>Verifiers</strong> are there to make sure the conditions/clauses in the Service Agreements are verified and enforced. Verifiers post <em>challenges</em> for provers and verify the returned <em>proof</em>. The type of challenge depends on the service offering (data integrity, storage, service execution, …). For cryptographic proofs of service we refer to the service integrity section of our <a href="https://oceanprotocol.com/tech-whitepaper.pdf">technical whitepaper</a>.</p><p>While Verifiers are suited for validating deterministic tasks emerging from prover-verifier interactions, Ocean <strong>Curators </strong>take into account more subjective measures such as opinion and signalling.<strong> </strong>In essence, tokenized curation is a way to make opinion a scarce resource and to facilitate the discovery of assets through signalling that opinion. Curators have skin in the game as they vote and bet.</p><p>Another key component in curated discovery is the ability to publish and query for metadata. Due to privacy, permissions and legal reasons, we believe that metadata is best kept off-chain and managed by the tribes. <strong>OceanDB</strong> is a discovery mechanism that can leverage a multitude of your favorite data stores such as <a href="https://www.bigchaindb.com/">BigchainDB</a>, MongoDB, CouchDB, and so on. One design goal here is to stay compliant to the <a href="http://identity.foundation/">W3C decentralized identity</a> specifications such as DIDs, DDOs, universal resolvers and Identity Hubs.</p><p>Finally, we recognize that there will be rainy days, where suppliers, consumers, verifiers and curators might not come to an agreement to resolve a service agreement. Hence, we provision the ability for legally binding contracts that are enforced by a <strong>dispute resolution layer</strong> [see <a href="https://www.mattereum.com/">Mattereum</a> or <a href="https://kleros.io/">Kleros</a>].</p><p>The above stack will gradually be implemented with the coming release plan of Ocean Protocol. It’s noteworthy that each layer can activate new applications, independent of the end-to-end integration of the stack: decentralized access control on cloud resources, verifiers for outsourced machine learning, curated discovery and knowledge graphs, AI governance, a marketplace for orchestration services and so on.</p><p>The above stack will gradually be implemented with the <a href="https://github.com/oceanprotocol/dev-ocean/blob/master/PROJECT_MAP.md">coming release plan</a> of Ocean Protocol.</p><h3>Conclusion</h3><p>On the horizon, we envision an oasis of complex public intelligence networks where problem-solving tribes pool their resources to establish sustainable and anti-fragile collaborative commons. Our protocol stack aims to glue together a rich supply chain of data services which can steer our future away from the a broken system of market capitalism and data monopolies. Unite the tribes!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FVK0dgpGgiddcI%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FVK0dgpGgiddcI%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FVK0dgpGgiddcI%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="261" frameborder="0" scrolling="no"><a href="https://medium.com/media/73414244935683b38c92d9e136d7af22/href">https://medium.com/media/73414244935683b38c92d9e136d7af22/href</a></iframe><p>Ready to dive in? Follow Ocean Protocol on <a href="https://twitter.com/oceanprotocol">Twitter,</a> <a href="https://t.me/joinchat/GUyxrE0Hi154D0NrlOqLFg">Telegram</a>, <a href="https://www.linkedin.com/company/ocean-protocol/">LinkedIn</a>, <a href="https://www.reddit.com/r/oceanprotocol/">Reddit</a>. Be with us for every step of our BUIDLing journey- subscribe to our <a href="https://oceanprotocol.com/newsletter/">Newsletter</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8fe78fcf8aa" width="1" height="1" alt=""><hr><p><a href="https://blog.oceanprotocol.com/a-deep-dive-into-ocean-protocol-design-8fe78fcf8aa">A Deep Dive into Ocean Protocol Design</a> was originally published in <a href="https://blog.oceanprotocol.com/">Ocean Protocol</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Curated Governance with Stake Machines]]></title>
            <link>https://medium.com/@DimitriDeJonghe/curated-governance-with-stake-machines-8ae290a709b4?source=rss-86da257a59b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/8ae290a709b4</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[governance]]></category>
            <category><![CDATA[commons]]></category>
            <category><![CDATA[curation]]></category>
            <category><![CDATA[game-theory]]></category>
            <dc:creator><![CDATA[Dimitri De Jonghe]]></dc:creator>
            <pubDate>Mon, 04 Dec 2017 21:13:49 GMT</pubDate>
            <atom:updated>2017-12-07T22:18:33.259Z</atom:updated>
            <content:encoded><![CDATA[<p>co-authored by <a href="https://medium.com/u/3308dd31324b">Gautam Dhameja</a>, <a href="https://medium.com/u/886c8d1ce1c7">Tom Debus</a> and <a href="https://medium.com/u/c6a623ce7060">Günsu Pancar</a>.<br>direct or indirect intellectual input by <a href="https://medium.com/u/f1cb98e196bc">Trent McConaghy</a>, <a href="https://medium.com/u/e006ffecda2d">Tim Daubenschütz</a>, <a href="https://medium.com/u/9104a5aaeb71">Don Gossen</a>, <a href="https://medium.com/u/248539c9783">Jernej Pregelj</a>, <a href="https://medium.com/u/7e7962706fb8">Rhys Lindmark</a>, <a href="https://medium.com/u/e407fd16d290">Jake Vartanian</a>, <a href="https://medium.com/u/951a18ca0efe">Luke Duncan</a>, <a href="https://medium.com/u/4380e912132e">Mike Goldin</a> and <a href="https://medium.com/u/9afbf877fa2f">Simon de la Rouviere</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/544/1*y0qVzg8nAOP3M2Mu7JwNlQ.png" /><figcaption>An image to attract the attention of the reader.</figcaption></figure><p>Humans have the tendency of being egocentric. Personal gains are more tempting than doing something for the common good. It’s our will to survive and thrive and it’s easy to forget that collaboration probably leads to more sustainable solutions. But not all is lost… I hope…</p><p>One approach could be to give someone a reward when they accomplish some objectives. Self-interest is fed by the reward and steers the human to do something that’s useful for “the system”. Let’s now think of “the system” as the common goods, public interest and global governance. Worth a try…</p><p>Looking at game theories I stumbled upon <a href="https://medium.com/@ilovebagels/token-curated-registries-1-0-61a232f8dac7">token-curated lists</a>. And they look pretty neat to me. Here is my take on it: steer token holders to curate items that should or should not belong to a list. If your opinion reconciles with the majority, you win more token. So, one is encouraged to predict what others think about that specific item. Here’s the catch: “predict what others think”.</p><p>Now, governance of the common goods is a bit more complicated than a single list of curated items. People and governed objects have various states, funnels, interconnections, dependencies and so on. Here we explore token-curated lists as building blocks for more complex curated automata.</p><h3>Curated Governance</h3><p>Belgium. A small country with <a href="https://en.wikipedia.org/wiki/List_of_governments_in_Belgium">6 governments</a>, 2 kings &amp; queens, 3 communities, 3 regions, 9 provinces, 3 official languages, coalitions, oppositions and what not? In the meanwhile it holds the record for <a href="http://www.telegraph.co.uk/news/worldnews/europe/belgium/8936857/Belgium-to-have-new-government-after-world-record-541-days.html">540 days without a government</a>. As a Belgian, it kinda felt as if nothing really changed and daily life went on as always…</p><p>Governance by tribes takes over in self-organizing communities (<a href="https://district0x.io/">district0x</a>, <a href="https://aragon.one/">Aragon</a>, <a href="http://nativetoken.io/">nativetoken</a>). Like-minded people signal ideas, opinions and influence. It’s necessary to build anti-fragile networks that flourish whilst remaining sustainable. See how tribes and subcultures form around common interest and reputation in social networks, knowledge platforms, open-source, art, and so on. Tribes exchange ideas and curate information they care about. Curation processes sift out the relevant information such that we know what’s hot or not and detect scams and time-sucks.</p><p>Give expert communities a carrot and a stick and they become self-sustaining. Reputation (<a href="https://www.reddit.com/r/memes/">reddit</a>, S<a href="https://stackexchange.com/questions?tab=hot">tackOverflow</a>, <a href="https://news.ycombinator.com/">HackerNews</a>, <a href="https://github.com/caffeinewriter/Awesome-xkcd">comics</a>, <a href="http://musicmap.info/">music</a>, peer-reviewed publications, …) or financial gains (crypto-economics, prediction markets, freelancing, …) pushes community members to process information within their expertise domain (curation, modeling, review, ….). Curators and curated topics have an incentive to form an integral connection with the community.</p><p><a href="https://medium.com/@ilovebagels/token-curated-registries-1-0-61a232f8dac7">Token-curated lists</a> (<a href="https://medium.com/u/4380e912132e">Mike Goldin</a> et al.) and <a href="https://medium.com/@simondlr/introducing-curation-markets-trade-popularity-of-memes-information-with-code-70bf6fed9881">curation markets</a> (<a href="https://medium.com/u/9afbf877fa2f">Simon de la Rouviere</a> et al.) show potential for incentivized community-driven governance. Items on these lists are vetted by the curators and may yield benefits such as attention, visibility, extended permissions and so on. We’ll cover an extended version that models multiple curated lists and dependencies between them. Much like a finite state machine or automaton.</p><p>However alienating the above concepts might sound, they are actually native to our current societies. One can think of how people get elected or achieve status, how bills pass through parliament, gaining gradual benefits when climbing up a ladder (credit scoring, KYC tiers, researcher’s status, …).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*zZwVs3-1tP1llpR2FM7v0A.jpeg" /><figcaption>Screenshot of a knowledge graph from Sid Meier’s Civilization III</figcaption></figure><p>Knowledge graphs such as in Sid Meier’s Civilization and Starships and Tokens illustrate the point of tokenized governance. Here, one needs to evolve their civilization by allocating budget on specific research items. For example: once a civilization learned the alphabet, it could move on in learning how to write. Writing combined with pottery allows one to gain the knowledge of map making and so on. In a democracy, the allocation of budget requires consensus and misuse leads to revolts and looting parties. A related interesting read is <a href="https://medium.com/u/f1cb98e196bc">Trent McConaghy</a>’s blogpost on <a href="https://blog.bigchaindb.com/starships-and-tokens-d8c32728a24b">Starships and Tokens</a>.</p><h3>Token-Curated Registries</h3><p>The principles of <a href="https://medium.com/@ilovebagels/token-curated-registries-1-0-61a232f8dac7">token-curated registries</a> (TCRs) are simple: a group of like-minded souls curate a list of items using a propose-challenge mechanism. One can propose an item to go on the list and supports the proposal using bonded stake with a token that is native to the system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TuoCxHYMnPArjY-5NJCWFw.png" /><figcaption>Sketch of Token-curated Registries [image credits: <a href="https://medium.com/u/e006ffecda2d">Tim Daubenschütz</a>, <a href="https://medium.com/u/9104a5aaeb71">Don Gossen</a>]</figcaption></figure><p>Each proposal can be challenged or not. During a challenge, stake is matched and a voting round starts. The winning party feasts from the looted stake and the losing party is slashed. When a proposal loses it is removed from the list.</p><p>This mechanism incentivizes curators to participate in the list, as each proposal for change could lead to a token reward. A useful strategy is to comply with the majority of the community by estimating or predicting the outcome of a challenge. Interestingly, individuals are rewarded by predicting community goals…</p><h3>Labels &amp; Rules</h3><p>When dealing with multiple “tribes” of experts or distinct verticals, it might make sense to spin up multiple TCRs or allow to filter by labels and signals. Curation groups might then focus on different governance objects, hence separating signal from the noise.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/384/1*maZvLah7K9y2T2RcIoIE3Q.png" /><figcaption>A Labeled TCR. A Proposal might appear on multiple times on the list under different labels.</figcaption></figure><p>One example for Labeled TCRs can be the categorization of music by genres. Projects such as <a href="http://musicmap.info/">MusicMap</a> and Spotify’s algorithmic map allow for a visual interconnected exploration of music. Currently there are only one or a few curators (the website owners) that use their expert knowledge to map songs onto genres and find connections between genres. If one can incentivize a community, subculture or other stake holders to map our music history in return for reputation, attention or token, this could lead to a drastically new approach to music discovery by curation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H7H4pKsWwsuhgJtuZJpLXQ.png" /><figcaption>A curated playlist of top-10 songs in a specific genre. Each genre can be regarded as a label or a filter.</figcaption></figure><p>One step further would be to attach label-specific rules. This allows to model interactions and links between TCRs. Many interesting use cases follow: permission groups, data governors, policy with hierarchy and escalation, funnels for reputation and standardization, curated knowledge domains, social graphs and groups, ...</p><p>Here we explore the notion of <a href="https://en.wikipedia.org/wiki/Finite-state_machine">Finite state machines </a>(FSMs) in a curated context. FSMs are a type of <a href="https://en.wikipedia.org/wiki/Automata_theory">automata</a> that contain a finite number of states and transitions (state memory + combinatorial logic). Automata are used to model broad classes of physical and behavioral processes.</p><p>Stake machines model governance using the concepts of curation and FSMs. This can give a community an incentive to participate in global goals and avoid steering towards a <a href="https://en.wikipedia.org/wiki/Tragedy_of_the_commons">tragedy of the commons</a>. To achieve this, we’ll need a few building blocks:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/785/1*aoydE0SFXyVTXT8BRC0gKA.png" /><figcaption>Schematic of a Labeled TCR with Rules</figcaption></figure><h4>Token &amp; Stake</h4><p><em>Tokens</em> are units of <em>stake.</em><br><em>Stake</em> is used to express opinion.</p><h4>Tribe &amp; Opinion</h4><p><em>Tribes</em> are opinionated community groups where the members hold token. <br>An <em>opinion</em> is expressed by means of bonded power (ie staked token or curation market).</p><h4>Proposals &amp; challenges</h4><p><em>Proposals</em> capture every change to the governed “state” of the community.<br><em>Challenges</em> are finite epochs where opinion is expressed upon <em>proposals</em> through voting or similar.</p><h4>Proposers &amp; challengers</h4><p><em>Proposers</em> want add <em>items </em>and<em> </em>bond it with <em>stake</em>.<br><em>Challengers</em> oppose to a change and bond it with <em>stake</em>.<br>or dual:<br>Challengers want to address issues and proposers solve these issues and thereby taking the issued stake as a bounty</p><h4>Labels &amp; Rules</h4><p>Each state in a stake machine has a <em>label </em>and<em> </em>group together <em>proposals.</em><br>Each <em>label</em> can implement a specific set of <em>rules</em>.<br><em>Rules</em> themselves can be <em>proposals</em> and may be challenged.</p><p>The rules model the conditions under which <em>changes</em> may occur for a specific label. Hence it’s possible to constrain the proposals, challenges, token holders and model relationships in the system. In order to resolve and validate the rules, all the necessary information needs to be available to the system or token holders.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/976/1*85Hi7cys0WtL0ovK5CLbUw.png" /><figcaption>An example of state rules with dependencies</figcaption></figure><h4>Dynamics</h4><p>Say we want to implement a governance funnel with some stages. Each stage can have a label like <em>1, 2, …, X, X+1. </em>In order for a proposal to be PROPOSED in stage <em>X+1</em>, it needs to be ACCEPTED in the previous stage <em>X</em>. This can be implemented by attaching a rule to the label that checks if the proposal is ACCEPTED in stage X. Such rules can be enforced by the system using some smart contract language. Similar rules can be devised to have label-dependent MIN_DEPOSIT or restricting the curators to a specific label.</p><p>Governance objects can gradually evolve through a stake machine as long as they comply to the rules set by community. Restriction of the curators per label enables tribes, roles, permissions, KYC tiers and so on. Think of splinter groups that fork from a set of rules and make them more stringent to make membership more “exclusive”.</p><p>As with any system, complexity and security tend to be at odds with each other. Simple queries and logic is advisable at the semantic level of the rules.</p><h3>Examples</h3><h4>Open-source governance: Github, RFCs, forks, peer review, …</h4><p>Open source code, documents, papers, standards, etc undergoes a curation process that’s governed by a group of experts that maintain a repository. These communities implement a form of hierarchy to reward behavior that’s in line with goals of the project. Frequent contributors decide on which changes will make it into the project or not.</p><p>For example: code changes are represented by pull requests (PRs) and request for approval. When approved, then everybody who downloads and runs the code will use that change. It’s important that these changes don’t contain malicious code or viruses, hence curation is done as a means for security audit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/946/1*A2QYKuGRPBPGwZajZqBfrw.png" /><figcaption>Stake machine for open-source code governance. Notice how Rules can apply both on governed objects as well as curators and proposers.</figcaption></figure><p>It’s easy to setup a stake machine that would incentivize the community to crowd source the project with code and audits. The roles in the community are Requesters that contribute PRs and Reviewers that have proven their skills and project mind-share in the past. In order to belong to this group, again a TCR per group can be implemented, making the list of curators curated again. The incentive can lead to more project engagement and larger communities because holders earn tokens that represent reputation, attention, governance, donation, …</p><h4>Curated Utility Networks</h4><p>In a following example, we can explore governance in tokenized systems such as public utility networks. Validation and policing of proofs in return for a token reward is framed as a staking mechanism, as well as protocol changes and corresponding voting weight. It’s closely related to <a href="https://github.com/paritytech/parity/wiki/Proof-of-Authority-Chains">Proof-of-Authority</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/694/1*HMKNmrH5QL1tNAmw-lFAtQ.png" /><figcaption>Curated governance in a purely fictional public utility network.</figcaption></figure><p>The above picture is a bit hyperbolic, but in the world of blogs it doesn’t really matter.</p><p>Of course there are many other governance objects like smart contract code, <a href="https://zap.store/">oracles</a>, <a href="https://www.khanacademy.org/">scaffold-based education</a>, <a href="https://medium.com/@simondlr/ada1afad086a">curated AI’s</a>, data quality, semantics, rules, norms, and so on…</p><h3>Wrap up</h3><p>Exploring the potential of curated governance is quite an exciting pastime. This blogpost is incomplete of course. Still many important pieces need to be developed, proven and so on.</p><p>But, following efforts by and for the community are probably the way forward — or just make me happy:</p><ul><li>TCR-solidity: <a href="https://github.com/skmgoldin/tcr">https://github.com/skmgoldin/tcr</a></li><li>The $teak network: <a href="https://medium.com/truebit/announcing-the-steak-network-c3d44290d53d">https://medium.com/truebit/announcing-the-steak-network-c3d44290d53d</a></li><li>Discussion groups on the topic: <a href="https://gitter.im/Curation-Markets/Lobby">https://gitter.im/Curation-Markets/Lobby</a></li></ul><p>Feel free to drop a line in the comments or email dimi&lt;at&gt;bigchaindb&lt;dot&gt;com.</p><p>co-authored by <a href="https://medium.com/u/3308dd31324b">Gautam Dhameja</a>, <a href="https://medium.com/u/886c8d1ce1c7">Tom Debus</a> and <a href="https://medium.com/u/c6a623ce7060">Günsu Pancar</a>.<br>direct or indirect intellectual input by <a href="https://medium.com/u/f1cb98e196bc">Trent McConaghy</a>, <a href="https://medium.com/u/e006ffecda2d">Tim Daubenschütz</a>, <a href="https://medium.com/u/9104a5aaeb71">Don Gossen</a>, <a href="https://medium.com/u/248539c9783">Jernej Pregelj</a>, <a href="https://medium.com/u/7e7962706fb8">Rhys Lindmark</a>, <a href="https://medium.com/u/e407fd16d290">Jake Vartanian</a>, <a href="https://medium.com/u/951a18ca0efe">Luke Duncan</a>, <a href="https://medium.com/u/4380e912132e">Mike Goldin</a> and <a href="https://medium.com/u/9afbf877fa2f">Simon de la Rouviere</a>.</p><h4>Changelog</h4><p>2017/12/07 Minor fixes and more attributions</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8ae290a709b4" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>