<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>The Irrefutable History of You: Distributed Ledgers and Semantics for Ubiquitous Personal Ratings</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Allan Third</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>John Domingue</string-name>
          <email>john.domingueg@open.ac.uk</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Knowledge Media Institute, Open University</institution>
          ,
          <addr-line>Milton Keynes, MK7 6AA</addr-line>
          ,
          <country country="UK">UK</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>A recurring theme in the science- ction series Black Mirror is the consequence for society of an over-focus on social networking. The episode Nosedive imagines a future in which every public interaction a person has is rated by the other parties, and every aspect of ones life depends on the overall rating computed from these. In this paper, we show how such a scenario is already technically possible using existing technologies such as distributed ledgers, and discuss means by which the negative possibilities may be ameliorated using semantic approaches.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>
        The television drama Black Mirror [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] focuses, in each standalone episode, on
the potential personal and social consequences of the use of technology, basing its
plots on forms of technology which can be imagined as at least partially plausible
extensions of what is available or in use today. The societies depicted are usually
in some sense dystopian, although not always (San Junipero [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] being a notable
counterexample). A recurring theme across a number of episodes is the idea of
an over-focus on social networking.
      </p>
      <p>
        The episode Nosedive [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] depicts a world in which every public interaction
with another person can be rated, between zero and ve stars, by means of a
smartphone { after any interaction, pointing the phone's camera at the person
one wishes to rate brings up a picture of that person and an interface to rate
them. Ratings can also be given for social media posts. Ratings are aggregated for
each person, so that it is also possible for anyone to view someone's aggregate
rating, again, by holding up their phone or looking at an online pro le. The
ubiquity of ratings has developed huge social importance, with employment,
personal and social consequences { a person might qualify, or not, to rent a
home, or get a job, or enter a social venue based on their rating. The society
shown is one of constant e ort to maintain or improve ones rating, and the
plot of the episode follows how one woman's attempts to signi cantly improve
her own rating go wrong, and through a series of unfortunate events, back re,
leading to her rating nosediving from just over four to nearly zero over a short
period of time.
      </p>
      <p>We rst show that the scenario of Nosedive can already be implemented using
technologies available now, before discussing possible technical approaches which
could minimise the negative social consequences of a hypothetical ubiquitous
adoption of such a rating system.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Distributed Ledgers</title>
      <p>
        An emerging area of research in the Web concerns the use of distributed ledgers,
based on the blockchain data structure, to serve as immutable trustworthy record
stores in environments where trust is lacking. Originally developed to underpin
the Bitcoin cryptocurrency [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ], blockchains are being experimented with for
a number of use cases, including veri able educational certi cation [
        <xref ref-type="bibr" rid="ref14 ref17 ref9">9, 14, 17</xref>
        ],
data integrity and access [
        <xref ref-type="bibr" rid="ref1 ref18">1, 18</xref>
        ] and Internet-of-Things applications [
        <xref ref-type="bibr" rid="ref19 ref6">6, 19</xref>
        ]. The
design of a blockchain is such that the integrity of its contents are guaranteed by
a large network of nancially and organisationally independent nodes, and the
cost of editing a record is prohibitively high, meaning that once entered onto a
blockchain, a record is e ectively immutable and irrefutable.
      </p>
      <p>A distributed ledger is based on a blockchain: a timestamped sequential series
of records shared in toto across a network of nodes. There is no central or
authoritative node, and every node has the potential to add new records to the
ledger. New records are added by consensus: anyone who wishes to add data to
a node submits a cryptographically-signed request to do so. Each node competes
for the right to add (\mine") a new block of transactions to the blockchain, with
that right awarded by consensus among all the nodes. The precise method of
consensus varies between di erent types of blockchain. The important feature of
any consensus mechanism is that there should be a cost involved in attempting to
mine blocks, and a reward for the successful node, to encourage good behaviour
among nodes. The winning node selects a set of pending record transactions and
groups them into a block, which is added to the chain. Requiring a consensus
between a large network of ( nancially, and organisationally) unrelated nodes
in order to add any data to the chain guarantees that spurious data cannot be
inserted by a malicious agent, and, due to the fact that modifying an older record
requires the entire chain following the modi ed record be rewritten as if from
scratch, the records entered in a blockchain are e ectively immutable.</p>
      <p>
        Distributed ledger platforms such as Ethereum [
        <xref ref-type="bibr" rid="ref20">20</xref>
        ] add the ability to have
executable code embedded in a blockchain, in so-called \smart contracts".
Because the code of a smart contract is stored on the blockchain like any other
record, it is immutable and traceable to the account of the person who deployed
it to the platform. This means that smart contracts can be relied on as not
having been tampered with. If the source code of a contract is also made available,
it is possible to verify that the deployed version is genuinely created from the
given source. An open source smart contract, then, can be trusted as a genuine
implementation of what its source code describes, which allows everyone who
interacts with the contract to verify that it behaves in the way that is expected
of it. Smart contracts are therefore usable to mediate transactions between users
on a distributed ledger platform in a trustworthy way.
      </p>
      <p>Records on a distributed ledger are public, and, as stated earlier, all nodes
on the network have a complete copy of the entire chain. This does not mean,
however, that everything must be readable by everyone; records can contain
encrypted data, and, with a suitable cryptographic key management infrastructure,
the data owner can implement a \selective visibility" system, only permitting
chosen others to view the full or partial contents of a record.
3</p>
    </sec>
    <sec id="sec-3">
      <title>Implementing the Nosedive rating system</title>
      <p>We see two main technical requirements to implement the Nosedive rating
system. To simplify the discussion, let us say that person A wishes to give person
B a rating of n stars, where n is a natural number between 0 and 5 in relation to
a face-to-face interaction I between A and B. Person C, at a later date, wants
to view this rating's value.
1. the ability for A's mobile device to recognise B's proximity and provide A
with the ability to select B's name and apply the rating.
2. Ratings must be unforgeable and incapable of being tampered with, and
always attributable to both A and B in their respective roles in the rating
transaction.</p>
      <p>In the episode, A simply needs to hold her device up facing B rather than
making a selection on the screen to achieve 1; potentially we can imagine
advanced facial recognition in addition to the other techniques described here
enabling this. And 2 is never explicitly stated; however, we must assume that it
applies in order for the system to carry the weight in people's lives that it is
shown to do.</p>
      <p>To implement 1, it is possible to take advantage of the widespread availability
of accurate GPS devices in modern smartphones. If each phone registered its
current location in a public database, it would be possible for A's phone to use
its own location to query for nearby phones, and then, from the returned list
of devices, query each in turn, via some presumably standardised interface, for
a user pro le, containing, e.g., B's name, picture, cryptographic public key and
\rating account" details. To ensure as best as possible that ratings of B were tied
to B's actual behaviour (and not, for example, the behaviour of someone who has
stolen B's phone), it may be necessary to require some biometric identi cation
of B. For non-proximate ratings, pro les can be shared via social media.</p>
      <p>
        2 can be developed using a distributed ledger with smart contracts. If A
and B both have accounts on a distributed ledger, publicised via their user
pro les, then it would easily be possible for A to submit a numerical rating to
B's \rating" smart contract via a cryptographically-signed request. If C reads
B's pro le, then he can query B's rating contract to view the rating n. A suitable
public key infrastructure would support trustworthy attribution of the rating to
A and prevent forgery, and the properties of the distributed ledger would ensure
that ratings could not be tampered with once made { collectively making the
ratings e ectively irrefutable. In fact, we are currently experimenting with the
scenario of distributed-ledger-based reputation transactions ([
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]) using the idea
of \reputation tokens" to be used in education as a means of recognising and
accrediting soft skills that traditionally are not adequately covered by traditional
assessment and accreditation.
      </p>
      <p>Signed and immutably timestamped records on the ledger would provide,
therefore, an e ectively irrefutable record of all rated interactions in a person's
history with the system. While it would be possible, and perhaps simpler in some
ways, to implement a system using a centralised database without a ledger, one
could not then be certain that ratings could not be tampered with by those with
access to the database.</p>
      <p>The technologies required are already developed and in use, and it would not
be technically di cult to build the Nosedive system using them.
4</p>
    </sec>
    <sec id="sec-4">
      <title>Potential for abuse</title>
      <p>
        It should be noted at the outset that there are already currently-obtaining
situations in which people voluntarily take part in systems in which they are rated by
other users, either explicitly or implicitly. Every user of the auction site eBay [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ],
for example, has a rating determined by other users re ecting their status as a
\good citizen" of the site. Forum/discussion sites which implement a \Like"
button on contributions can show the total number of \likes" a user has received on
the site. (The tabletop games community site Boardgamegeek [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], for example,
does this with \thumbs", its \like" system.) In a somewhat more sophisticated
way, online dating sites provide rankings of users, although these rankings are
context-sensitive and depend on the user viewing them, in terms of how well
users match the viewers. The algorithms computing the rankings are generally
proprietary; it seems reasonable to assume that they are in some way learned
from similar users.
      </p>
      <p>
        The bulk of existing research into online rating systems has focused on
online sales systems or discussion forums such as these. Desiderata for an online
reputation system are suggested in [
        <xref ref-type="bibr" rid="ref21">21</xref>
        ], and include mechanisms to prevent or
discourage users from changing their identities to \discard" a bad rating, and
to limit the e ect of \memory" in ratings - to prevent historical low ratings
from dragging an average down even when a person's current ratings are
consistently high. One of the desiderata is also that ratings from high-ranking users be
weighted more than those of low-ranking ones { an idea which we discuss below
in section 5.1.
      </p>
      <p>
        It is clear, however, that the disastrous outcome for the protagonist in
Nosedive is not far-fetched; a system for ubiquitous ratings of people, for any reason,
and with profound social consequences, is ripe for abuse. We envisage this abuse
in the form of malicious, trivial or thoughtless low ratings directly, as shown
in the episode, as well as in over-interpretation of low ratings in inappropriate
contexts. In existing ranking systems, [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ] showed that negative rankings have
a disproportionate e ect on reputation compared to positive rankings. While it
may well be appropriate to refuse to buy from an eBay seller with a low rating,
it is clearly not appropriate to refuse to hire someone on the basis of, for
example, their social life. Even supposing that one accepted the concept of rating
each public interaction according to perceived merit, there is no a priori reason
to believe that \fair" ratings are achievable. People have been shown to assess
in others in a discriminatory manner based on existing prejudices in otherwise
identical circumstances (see, e.g., [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ]). We may therefore reasonably expect that
groups disadvantaged on the basis of gender, ethnic origin, sexuality, and so on,
would become disadvantaged in terms of ratings. Indeed, in Nosedive, those who
are shown to be experience the most signi cant consequences as a result of low
ratings are members of existing disadvantaged groups, by gender or race.. The
protagonist's brother, however (white, male and hinted to be heterosexual) is
shown to be less invested in the need for a high rating, and it seems plausible
that ones investment in ratings in general would vary in inverse proportion to
societal privilege.
5
      </p>
    </sec>
    <sec id="sec-5">
      <title>Minimising the e ects of a Nosedive rating system</title>
      <p>Let us suppose that some social or economic pressure leads to the widespread
adoption of such a technology. In itself this appears to be unlikely, for reasons
including the scenario which is the central plot of Nosedive, but for the sake of
argument, let us assume that it takes place. And let us assume that such a system
could be enforced, perhaps by economic pressures, to be close to universal, so
that everyone had access to the relevant hardware and software to take part,
and the options for \opting out" were limited to non-existent. (In practice, we
assume that none of these are achievable, particularly the latter two, and that
such a system has so many manifest and serious ethical and social problems with
it that widespread adoption would be resisted very very strongly, su ciently to
undermine its implementation at all.) But if it did, what measures could be put
in place to protect users from malicious or punitive ratings?
5.1</p>
      <sec id="sec-5-1">
        <title>Automatic or manual moderation</title>
        <p>The most obvious, and on the surface, likely to be e ective, approach would be if
B had the power to accept or reject ratings at will, but of course, to do so would
undermine the concept of a rating and would lead to the vast majority of, if not
all, people having only the maximum rating. Even a slight modi cation, in which
ratings are accepted or rejected, but the recipient does not know the value of the
rating at the time of acceptance, would still tend to lead to overall high average
ratings, as people would generally choose to accept ratings for interactions which
they felt had gone well.</p>
        <p>Take into account the rating of the rater Low-rated people's ratings do
not count as much as those of high-rated people, i.e., A's ratings are weighted
by her own rating.</p>
        <p>
          This approach might seem good on paper, but is likely to be harmful in
practice. Given the hypothesis that the distribution of high and low ratings
would come to re ect existing power structures in society, there is the potential
for this approach simply to end up entrenching disadvantage. An episode of the
sitcom Community [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ] with a similar theme to Nosedive envisaged this precise
scenario, with the outcome being a very highly strati ed society with little social
movement.
        </p>
        <p>Take into account the rating history of raters. The ratings of someone
who frequently rates people low are weighted less than the ratings of others.</p>
        <p>This is also subject to being gamed. All a malicious person needs to do is to
give high ratings to interactions which are not important to them in order to
maintain rating in uence on those who do. It also would only a ect persistently
low-rating people, and would have no e ect on the situation where B receives
many low ratings from a large number of otherwise typically-rating people. (This
may well have been the case at a number of points in the episode, such as when
the protagonist receives a lot of low ratings because she's standing on the highway
in tra c, or when she takes over the microphone at the wedding.)</p>
        <p>This would also be relevant to other forms of gaming of the rating system. For
example, family and friend groups might cooperate to increase their members'
ratings, while antagonistic social groups could do the opposite. Analysis of rating
history could identify patterns such as this, and allow for normalisation of ratings
to re ect them.</p>
        <p>Require mutual ratings If only A rates B in relation to I, nothing happens
to B's rating until and unless B also rates A in relation to I.</p>
        <p>This would provide B with some control and the ability to avoid ratings
which are predicted to be bad. However, bearing in mind we are discussing a
hypothetical situation where society as a whole has decided to adopt ubiquitous
rating, it seems less than likely that this level of control would be accepted.</p>
        <p>Mutual agreement would be one of the mechanisms by which erroneous
ratings could be corrected (for example, in the case of misidenti cation of a person).
Meta-rating Nearby people are randomly selected to \rate a rating", with
low-ranked ratings being withdrawn or reversed.</p>
        <p>
          This approach has the potential to make a di erence, and has been
implemented with positive e ects in discussion systems { a notable example being the
Slashdot technology news site [
          <xref ref-type="bibr" rid="ref15">15</xref>
          ], where every contribution in a discussion can
be rated by other users, and whose \metamoderation" system has been shown
to succeed in maintaining civility in discussions [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ]. This method could also be
used to address erroneous ratings.
        </p>
        <p>Potential di culties with this method are the overhead of \meta-rating" {
would people be willing to expend the extra e ort to do it? { and the observation
that meta-ratings are just as likely to be a ected by conscious and unconscious
bias as the ratings themselves.</p>
        <p>Apply a cost to giving ratings If there were a cost to rating someone, or a
limit on the number of ratings which could be given (within a particular time
period, for example), then it may serve to deter frivolous ratings. If the cost were
nancial, of course, this would again serve to entrench existing status. If simply
a limit in the number of ratings, there is a chance that malicious ratings would
be less likely.
5.2</p>
      </sec>
      <sec id="sec-5-2">
        <title>Semantic approaches</title>
        <p>
          Contextual ratings Rather than a semantics-free number, ratings are instead
applied to a particular category of interaction or behaviour, e.g., \this rating is
for a customer in a retail purchasing interaction". [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ] argues that ratings should
always be interpreted relative to their original context.
        </p>
        <p>This allows ne-grained information to be conveyed. Speci cally, it allows
for more subtle interpretation of ratings. So in hiring someone, an employer
will not (indeed, should not) be concerned with what that person is like as a
wedding guest, and can therefore exclude all ratings related to irrelevant
transactions. More speci cally, an aggregate rating could be computed not across all
interactions, but across all interactions of speci ed types, such as all nancial
interactions. With more sophisticated interfaces and possibly smarter systems,
the context could be extended to support the notion of evidence for a rating to
be recorded alongside the rating itself.</p>
        <p>For contextual ratings to function, there would need to be an ontology of
human interaction describing the categorical relationships between interaction
types (such as that a retail transaction is a nancial interaction, for example).
Manual modelling, however, is only likely to get so far, given the range and
complexity of human interactions which take place. Fine-grained categorisations
could be crowdsourced, with, perhaps, some central editorial approval or
moderation process to avoid discriminatory or o ensive categories.</p>
        <p>Reasoning could be carried out on semantic representations to derive new
categories or specialised ratings { this has potential for positive or negative
consequences. For example, it might then be possible for malicious users to simulate
discriminatory categories indirectly by deriving them. Positive possibilities
include, among others, the ability to identify patterns in ratings received, which
might help to limit or avoid negative e ects. (The same approach would apply if
it were also possible to nd out the ratings that someone had given too, which
would improve transparency in the process regardless.)
Purely semantic ratings The idea of contextual ratings could be taken one step
further, and the idea of numerical ratings could be dropped entirely. So instead
of \B is rated 4", or \B is rated 4 in relation to I, which is a retail interaction",
it would be \B is rated \helpful" in relation to I, which is a retail interaction".
Models would need to be developed for relevant attributes, such as \helpful"
which could be associated with particular interactions, or interaction types, and
with su cient ontological semantics, reasoning could be carried out as with
numbers. Such contextual semantic ratings would be more ne-grained still, and
o er more exibility, while perhaps helping people to avoid the habit of
overinterpreting numbers. Aggregation too need not be purely numerical; aggregate
categories using vague quali ers, such as \mostly harmless", could be computed.
Selective visibility of ratings It could even be possible, using smart
contracts, to enforce restrictions on ratings that are taken into account; if C has
to specify up-front the reason for reading B's rating, with B's acceptance of
the reason, there could be hardcoded, crowdsourced, or legally mandated sets of
interaction types which may be considered in computing the rating. Potentially
the user could have the ability to override the request and add further limits
onto the considered interaction types. However, this latter ability seems likely to
be subject to the same social pressures as requiring approval or mutual rating
before a new rating has e ect.</p>
        <p>Two-way personalisation Combining semantic representation of contextual
rating data with selective visibility gives the potential for all parties, A, B and
C, to provide semantic descriptions of preferences and inputs which can be used
for ne-grained negotiation of requests and permissions when it comes to rating,
being rated and viewing other ratings, from which one would expect good
practices to emerge from privacy-conscious users which could be adopted by those
less skilled when it comes to technology and privacy protections.
6</p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>Conclusions</title>
      <p>We have described how a ubiquitous personal rating system, as shown in the
Black Mirror episode Nosedive, could be implemented using technologies
available today, backed up by smart-contract-enabled distributed ledger platforms
which ensure the availability of e ectively immutable histories of e ectively
irrefutable records of ratings. We have speculatively discussed potential
moderation techniques and Semantic Web technologies which might aim to limit the
negative consequences of such a system.</p>
      <p>None of the speculated measures do more than mitigate the possibilities of
abuse, and it is hard to see how anything other than avoiding the system at all
could prevent it entirely. Currently-used personal rating systems are limited to
very speci c contexts, such as eBay, with no consequences beyond those contexts,
but a ubiquitous system is inevitably subject to many forms of abuse.</p>
      <p>While we believe it is highly unlikely that society as a whole would adopt
a Nosedive system, there have of course been historical and recent instances of
societies choosing options not in the best interest of the majority of its members.
Expecting a technological solution to scenarios such as this is nave; technology
can be designed to support safe choices or minimise dangerous ones, but
ultimately, it can rarely, if ever, enforce them. if there were a signi cant danger
that Nosedive-style ratings were to become a ubiquitous phenomenon, the most
e ective approach would likely be to tackle the economic and social pressures
leading to this danger.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Azaria</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ekblaw</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vieira</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lippman</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Medrec: Using blockchain for medical data access and permission management</article-title>
          .
          <source>In: Open and Big Data (OBD)</source>
          , International Conference on. pp.
          <volume>25</volume>
          {
          <fpage>30</fpage>
          .
          <string-name>
            <surname>IEEE</surname>
          </string-name>
          (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Blum</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Deay</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Saccardo</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kolb</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ridley</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Padrick</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          , Diego,
          <string-name>
            <given-names>D.</given-names>
            ,
            <surname>Roller</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Harmon</surname>
          </string-name>
          ,
          <string-name>
            <surname>D.</surname>
          </string-name>
          :
          <article-title>App development and condiments</article-title>
          .
          <source>Community S5(E8)</source>
          (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3. BoardGameGeek: https://boardgamegeek.com (
          <year>Jul 2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Brooker</surname>
            ,
            <given-names>C.: Black</given-names>
          </string-name>
          <string-name>
            <surname>Mirror. Zeppotron</surname>
          </string-name>
          (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Brooker</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          : San Junipero.
          <source>Black Mirror S3(E4)</source>
          (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Christidis</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Devetsikiotis</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Blockchains and smart contracts for the internet of things</article-title>
          .
          <source>IEEE Access 4</source>
          ,
          <issue>2292</issue>
          {
          <fpage>2303</fpage>
          (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7. eBay: https://ebay.com (
          <year>Jul 2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Jones</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schur</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Brooker</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          :
          <string-name>
            <surname>Nosedive. Black Mirror</surname>
          </string-name>
          <article-title>S3(E1) (</article-title>
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9. KMi: http://blockchain.open.ac.
          <source>uk (Jan</source>
          <year>2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Lampe</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zube</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lee</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Park</surname>
            ,
            <given-names>C.H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Johnston</surname>
          </string-name>
          , E.:
          <article-title>Crowdsourcing civility: A natural experiment examining the e ects of distributed moderation in online forums</article-title>
          .
          <source>Government Information Quarterly</source>
          <volume>31</volume>
          (
          <issue>2</issue>
          ),
          <volume>317</volume>
          {
          <fpage>326</fpage>
          (
          <year>2014</year>
          ), http://www.sciencedirect.com/science/article/pii/S0740624X14000021
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Mui</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mohtashemi</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ang</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Szolovits</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Halberstadt</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Ratings in distributed systems: A bayesian approach</article-title>
          .
          <source>In: Proceedings of the Workshop on Information Technologies and Systems (WITS)</source>
          . pp.
          <volume>1</volume>
          {
          <issue>7</issue>
          (
          <year>2001</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Nakamoto</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Bitcoin: A peer-to-peer electronic cash system (</article-title>
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Oreopoulos</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Why do skilled immigrants struggle in the labor market? a eld experiment with thirteen thousand resumes</article-title>
          .
          <source>American Economic Journal. Economic Policy</source>
          <volume>3</volume>
          (
          <issue>4</issue>
          ),
          <volume>148</volume>
          (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Sharples</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Domingue</surname>
            ,
            <given-names>J.:</given-names>
          </string-name>
          <article-title>The blockchain and kudos: A distributed system for educational record, reputation and reward</article-title>
          .
          <source>In: European Conference on Technology Enhanced Learning</source>
          . pp.
          <volume>490</volume>
          {
          <fpage>496</fpage>
          . Springer (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15. Slashdot: http://slashdot.org (
          <year>Jul 2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16. Standi rd, S.S.:
          <article-title>Reputation and e-commerce: ebay auctions and the asymmetrical impact of positive and negative ratings</article-title>
          .
          <source>Journal of management 27(3)</source>
          ,
          <volume>279</volume>
          {
          <fpage>295</fpage>
          (
          <year>2001</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>Third</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Domingue</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bachler</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Quick</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          :
          <article-title>Blockchains and the Web position paper</article-title>
          .
          <source>In: W3C Workshop on Distributed Ledgers on the Web</source>
          (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <surname>Third</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tiddi</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bastianelli</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Valentine</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Domingue</surname>
          </string-name>
          , J.:
          <article-title>Towards the temporal streaming of graph data on distributed ledgers</article-title>
          .
          <source>In: 2nd International Workshop on Linked Data and Distributed Ledgers</source>
          ,
          <source>Supplementary Proceedings of the 14th Extended Semantic Web Conference</source>
          (forthcoming
          <year>2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <string-name>
            <surname>Valentine</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          : GreenDATA. http://projects.kmi.open.ac.uk/greendata (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20.
          <string-name>
            <surname>Wood</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          :
          <article-title>Ethereum: A secure decentralised generalised transaction ledger</article-title>
          .
          <source>Ethereum Project Yellow Paper</source>
          (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          21.
          <string-name>
            <surname>Zacharia</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Maes</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Trust management through reputation mechanisms</article-title>
          .
          <source>Applied Arti cial Intelligence</source>
          <volume>14</volume>
          (
          <issue>9</issue>
          ),
          <volume>881</volume>
          {
          <fpage>907</fpage>
          (
          <year>2000</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>