RepuX协议

RepuX协议 重要通知

  1. 请仔细阅读本节和以下章节,标题是“免责声明”、“REPUX不作任何陈述和保证”、“您的陈述和保证”、“前瞻性陈述的注意事项”、“不做建议”、“关于分配和传播的限制”、“不提供证券或注册”以及“风险和不确定性”。 如果您对所采取的行动有任何疑问,请咨询您的法律、财务、税务或其他专业顾问。

  2. RepuX令牌(正如白皮书中所定义的)无意在任何司法管辖区构成证券。 本白皮书并不构成任何类型的招股说明书或要约文件,亦无意构成任何司法管辖区证券的要约或证券投资的招揽。 欲了解更多信息,请参阅RepuX有限公司保密私募发行备忘录。

  3. 本白皮书并不构成或形成任何有关出售的任何意见的一部分,也不构成RepuX购买任何RepuX令牌的任何要约的任何招揽。

  4. RepuX令牌的分销商将是RepuX有限公司(“RepuX”)的一个关联公司,并将RepuX令牌销售的所有收益部署资助RepuX协议、业务和运营。

  5. 任何人不得就销售和购买RepuX令牌订立任何合同或有约束力的法律承诺,并且不会在本白皮书的基础上接受加密货币或其他形式的支付。

  6. 分销商与作为买方您之间的任何协议以及与任何买卖RepuX令牌有关的协议,仅受单独的、列出该协议条款与条件(“条款与条件”)文件的约束。 若条款条件与本白皮书有不一致之处,以前者为准。

  7. 除非您有资格成为美国标准下的“认可投资者”,否则您没有资格购买预售中的任何RepuX令牌(正如本白皮书所定义的)。

  8. 在推出RepuX协议之前,认可投资者可以通过SAFT合同获得购买预售中的RepuX令牌的权利。 如果您是有兴趣参加预售的认可投资者,请直接与我们联系。

  9. 没有任何监管机构审查或批准本白皮书中所列的任何信息。 根据任何司法管辖区的法律、监管要求或规则,还没有或将要采取这样的行动。 本白皮书的发布、分发或传播并不意味着遵守适用的法律、监管要求或规则。

  10. 存在与RepuX和/或RepuX基金会及其各自的业务和运营、RepuX令牌和令牌销售有关的风险和不确定性。 有关风险和责任的完整列表,请参阅“RepuX有限公司保密私募发行备忘录”。

  11. 本白皮书及其任何部分或其任何副本不得带到或传播到任何禁止或限制分发或传播本白皮书的国家。

  12. 若不包括本节和下列章节,标题为“免责声明”、“REPUX不作任何陈述和保证”、“您的陈述和保证”、“前瞻性陈述的注意事项”、“不做建议”、“关于分配和传播的限制”、“不提供证券或注册”以及“风险和不确定性”,则本白皮书的任何部分均不得被复制、分发或传播。

免责声明

  1. 在适用的法律、法规和规则允许的最大范围内,RepuX和/或RepuX基金会不承担任何由于您接受或依赖本白皮书或其任何部分而产生或与之有关的、间接的、特殊的、附带的、作为结果的,或任何形式的、侵权的合同,或其他方面的(包括但不限于毛收入、收入或利润的损失,以及使用或数据的丢失)的损失。

RepuX不做任何陈述和保证

  1. RepuX和/或RepuX基金会不会以任何形式向任何实体或个人做出或声称作出任何陈述、保证或承诺,包括与本白皮书所载任何信息的真实性、准确性和完整性相关的任何陈述、保证或承诺。

RepuX的陈述和保证

  1. 通过访问和/或接受据有本白皮书或其中任何部分(视情况而定)中的任何信息,您向RepuX和/或RepuX基金会声明并保证如下:

    1. 您同意并确认,RepuX令牌不以任何形式在任何司法管辖区域构成证券;

    2. 您同意并承认,本白皮书并不构成任何形式的招股说明书或要约文件,也无意构成任何司法管辖区内的证券要约或证券投资招揽,您没有义务订立任何合同或具有约束力的法律承诺,在本白皮书的基础上不接受加密货币或其他形式的支付;

    3. 您同意并确认,没有任何监管机构审查或批准本白皮书中所列的信息,没有根据任何司法管辖区的法律、法规要求或规则采取任何行动,本白皮书对于您的的发布、分发或传播并不意味着已经遵守适用的法律、监管要求或规则;

    4. 您同意并承认,本白皮书、承诺和/或令牌销售的完成不应被您解释、理解或视为RepuX和/或RepuX基金会、RepuX令牌以及令牌销售优劣的标志;

    5. 本白皮书、其任何部分或其任何副本的分发或传播,或您对本白皮书、其任何部分或其任何副本的接受,均不受您所在司法管辖区域内的适用法律、法规或规则的禁止或限制,并且在与据有有限制的情况下,您已自行承担责任遵守并符合所有此类限制,且不对RepuX和/或RepuX基金会负责;

    6. 您同意并承认,在您想购买任何RepuX令牌的情况下,RepuX令牌不得被解释、理解、分类或视为:

      1. 除了加密货币以外的任何种类的货币;

      2. 任何人或实体(不论是RepuX和/或RepuX基金会)发行的公司债券、股票或股份,有关该等公司债券、股票或股份的权利、期权或衍生品;

      3. 集体投资计划中的单位;

      4. 商业信托单位;

      5. 商业信托单位的衍生品;或

      6. 任何其他证券或任何类别的证券。

    7. 您充分知晓并理解,如果您不是符合美国标准的“认证投资者”,则您没有资格参加RepuX令牌的预售;

    8. 您对加密货币、基于区块链的软件系统、加密货币钱包或其他相关令牌存储机制、区块链技术和智能合约技术有基本的了解;

    9. 您充分了解并理解,在您想购买任何RepuX令牌的情况下,存在与RepuX和RepuX基金会及其各自的业务和运营、RepuX令牌和令牌销售相关的风险;

    10. 您同意并承认,RepuX和RepuX基金会均不承担任何由于您接受或依赖本白皮书或其任何部分而产生或与之有关的、间接的、特殊的、附带的、作为结果的,或任何形式的、侵权的合同,或其他方面的(包括但不限于毛收入、收入或利润的损失,以及使用或数据的丢失)的损失;以及

    11. 上述所有陈述及保证,自您访问和/或接受拥有本白皮书或其任何部分(视情况而定)时均属真实、完整、准确及无误导性。

关于前瞻性陈述的警示性说明

  1. 本白皮书可能包含某些前瞻性陈述,包括但不限于涉及未来营运业绩和涉及风险和不确定性的计划的陈述。 我们使用诸如“期望”、“预期”、“相信”、“估计”,这些词语的否定词以及类似的表达来确定前瞻性陈述。 这些前瞻性陈述涉及已知和未知的风险、不确定性和其他因素,出于任何原因,这些可能会导致RepuX和/或RepuX基金会的实际结果、业绩或成就与那些在前瞻性陈述中明示或暗示的预测未来结果,存在重大差异。

  2. 本白皮书中的任何信息均不应视为有关RepuX、RepuX基金会、RepuX令牌和令牌销售在业务、法律、财务或税务方面的建议。 您应该就RepuX和/或RepuX基金会及其各自的业务和运营、RepuX令牌和令牌销售咨询您自己的法律、财务、税务或其他专业的顾问。 您应该了解,您可能需要无限期承担购买RepuX令牌的财务风险。

分发和传播的限制

  1. 本白皮书或其任何部分的分发或传播可能受到任何司法管辖区的法律、监管要求和规则的禁止或限制。 在有任何限制适用的情况下,您应自行负责,告知自己并遵守适用于您据有本白皮书或其部分内容(视情况而定)的任何限制,且对RepuX和/或RepuX基金会不承担任何责任。 已经被分发到或传播到本白皮书副本的人员、被提供访问权或以其他方式据有本白皮书的人员,不得将其分发给任何其他人,不得为任何目的复制或以其他方式分发本白皮书或此处包含的任何信息,也不允许或造成同样的情况发生。

不提供证券或注册

  1. 本白皮书并不构成任何类型的招股说明书或要约文件,亦无意构成任何司法管辖区证券的要约或证券投资的招揽。 任何人都不得订立任何合同或有约束力的法律承诺,并且在本白皮书的基础上不接受任何加密货币或其他形式的支付。 有关销售和购买RepuX令牌的任何协议仅受该协议的条款及条件的约束,并不受其他文件的约束。 若条款条件与本白皮书有不一致之处,以前者为准。

  2. 没有任何监管机构审查或批准本白皮书中所列的任何信息。 根据任何司法管辖区的法律、监管要求或规则,还没有或将要采取这样的行动。 本白皮书的发布、分发或传播并不意味着遵守适用的法律、监管要求或规则。

风险和不确定性

  1. 潜在的RepuX令牌购买者应在任何购买RepuX令牌之前,仔细考虑和评估与RepuX、RepuX基金会及其各自的业务和运营、RepuX令牌和令牌销售相关的所有风险和不确定性、本白皮书中的所有信息以及任何条款和条件。 倘有任何此等风险和不确定性发展成为实际事件,则RepuX和/或RepuX基金会的业务、财务状况、经营业绩及前景可能受到重大不利影响。 在这种情况下,您可能会失去全部或部分RepuX令牌的价值。

RepuX远景

我们的远景是创建一个协议,通过在收取者、开发者和用户之间的高效转换,促进数据的货币化,随着时间的推移,该协议也将允许评估数据的可靠性和声誉。 通过我们的RepuX协议,数据收取者可以将数据传输给数据用户或应用程序开发人员以交换RepuX的令牌。 开发人员可以在RepuX协议上构建,利用收取者传输的数据生成产品和服务,这些产品和服务然后被传输到各个行业的终端用户,以换取RepuX令牌。 通过RepuX协议,我们希望为数据带来额外的价值。

RepuX的目标和目的

我们预计,数据货币化将成为未来个人和实体的主要收入来源。 据估计,到2025年,全世界将创造的字节数据量,将从2015年只有不到10泽字节上升到180泽字节(或180万亿兆字节)。1

我们的RepuX协议的目标和目的如下:

总之,我们的最终目标是建立一个安全、可靠、高性能的数据传输协议,该协议可以与由第三方开发的各种不同的应用程序整合,供不同的行业使用。

[1]2030亿大数据分析市场的六大预测

什么是RepuX?

“RepuX将允许数据收取者、应用程序开发者和数据用户共享数据和创造价值的机会,而这种机会在当前市场中不存在”

RepuX是一个协议级别的框架(“RepuX协议”),各种类型的不可变数据可以在不同的公司和个人收取者、开发者和用户之间得到商品化和交换。 RepuX协议结合多种分散式技术,如InterPlanetary文档系统(或IPFS)2,Sia3,Ethereum4,EOS5,并提供升级到定制高吞吐量区块链的潜力。 通过促进对等之间的数据和价值传输,RepuX协议在数据收取者、应用程序开发者和数据用户之间创建数据共享的可能性,而这种可能性在当前市场中不存在。 RepuX协议为数据生产者提供了一个机会,通过促进向多个行业的用户提供这些数据来创造他们的数据中的价值,同时消除了在这个过程中对中间人的需求。

随着RepuX协议的发展,RepuX已经准备好充分利用机器学习、大数据和人工智能对大规模综合数据的依赖,并推动这些领域的创新。 通过每个实体和每次交易对于数据可靠性的评估,并通过甲骨文系统的验证,我们可以确保RepuX协议内的完整性,并为数据用户提供他们对于购买数据的内容和质量更高的信心。

[2]见https://github.com/ipfs/ipfs
[3]见https://www.sia.tech/whitepaper.pdf
[4]见https://github.com/ethereum/wiki/wiki/White-Paper
[5]见https://github.com/EOSIO/Documentation/blob/master/ TechnicalWhitePaper.md

预售和RepuX令牌销售

RepuX有限公司正在创建5亿个RepuX令牌(“RepuX令牌”)。 RepuX公司正在进行预售在公开发行时获得RepuX令牌的权利,该权利通过一个“简单的未来令牌协议(“预售”)”只提供给认证投资者,一旦RepuX协议可操作,随后就开始更广泛的RepuX令牌的发行。

RepuX令牌是ERC20令牌,它将代表与RepuX协议相连接的唯一支付数据服务的方法。 在令牌销售期间,合格的购买者可以通过转让以太(“ETH”)购买RepuX令牌。

预售中的每个参与者,都必须根据适用的证券法提供有关他们作为“受信投资者”(或类似概念)的信息。 每位售前参与者以及令牌销售中的每位RepuX令牌购买者都将被要求提供“了解您的客户”(或KYC)信息。 RepuX将进行一些检查,以确保我们遵守我们的反洗钱(或AML)要求和程序。

人工智能和机器学习

数据创造正在不断地以不断增长的步伐发生。 那些数据有价值。 目前,这些数据的收集、使用和分发是由某些大型公司实体主导。

与此同时,人工智能(或AI)的投资正以非常快的速度增长。 据估计,AI开发市场每两年就翻一番以上。 人工智能有可能显著改变经济的许多方面。 在AI领域内,机器学习能力在过去几年中有了极大的提高。 这种机器学习能力与分散式的数据访问相结合,实现了基于分散式数据应用的产业化。 由于机器学习在过去的数据基础上建立知识,因此所创建的模型只与输入到模型中的数据一样好。

RepuX协议有可能消除那些可以轻松接触到机器学习数据集的人与那些不能接触到机器学习数据集的人之间的“数字鸿沟”。

机器学习是人工智能的一个分支,它使得计算机系统直接从数据的例子中学习。


图1:麦肯锡公司2017年讨论文件6

[6]见https://royalsociety.org/~/media/policy/projects/machine-learning/publications/machine-learning-report.pdf

大数据

大数据需要大型数据集,这些数据集通常由企业或组织收集,作为日常运作的副产品。 例如,这样的数据集可以是连带时间和地点的疾病诊断的医学数据库。 不幸的是,由于许多大数据数据集通常与企业或组织的立即操作不直接相关,因此经常被忽略和丢弃。 这些数据集可以很容易地货币化并且被其他公司使用,这些公司可能从这些数据中受益。 例如,一家超市连锁店内成功的产品交付清单可能对寻求进入特定地区的新供应商有用。 缺少的是:

基本数据市场的一个例子是勇敢浏览器,它最近出售了他们的基本关注令牌(或BAT)。 在勇敢浏览器中,用户可以有选择地将他们的浏览数据或他们的关注数据“销售”(基于匿名的)给营销人员,然后这些营销人员购买这些数据并以BAT7进行支付。

[7]见https://basicattentiontoken.org/

信任和透明度

共享数据集的主要挑战之一是数据交易中不同方之间缺乏信任。 一个人很难确定一个特定的数据集是否有条理、精确而富有洞察力,而不需要首先访问数据集来评估它。 另外,可能还存在一些与缺乏各方在数据交易中可以碰面的通用平台的问题。

如果这个信任问题能够充分得到解决,那么欺诈率可能会大大降低,同时,各行业的许多其他潜在数据交易也可能会实现,比如保险、国际贸易和小额贷款中的数据交易。

通过设计,区块链内在地对所涉及的数据修改具有抵抗力。 区块链是一个不断增长的记录列表,称为区块,这些记录列表通过密码术被链接和保护。 每个区块通常包含一个复述指针作为与前一个区块的链接、时间戳和交易数据。 区块链可以作为一个开放的分布式账本,可以有效地、以可验证和永久性的方式记录双方之间的交易。 为了用作分布式账本,区块链通常由一个对等网络共同管理,遵守用于验证新区块的协议。 一旦被记录,若不改变所有后续区块(这需要网络多数人的共谋),任何给定区块中的数据不能被回溯地改变。 区块链技术使欺诈率降低,从而实现大量潜在的应用。

这使得区块链非常适合作为RepuX协议的基础,在此协议中,安全性和交易完整性至关重要。

RepuX技术

概述

RepuX协议的技术可以分解成四个独立层。

图2:REPUX协议的细分

应用程序层位于RepuX协议的顶部。 这一前端层由各种分散式应用程序(Dapps)组成,第三方应用程序开发人员可以在现有的RepuX API基础架构上进行构建。 这方面的例子可以是一个允许个人或实体出售社交媒体使用数据以交换访问网站的服务。

RepuX协议的下一层是数据层。 这一层由在RepuX中可以购买和销售的所有数据组成。 通过将数据层存储在IPFS、StorJ8或Sia等分散式基础架构中,我们不仅确保数据的存在,而且确保数据以分散式的方式存储。 数据所有权、共享、安全和隐私偏好可以通过使用区块链本身的多重签名密码原语来实现,以确保数据在链上被冗余地得到保护,并且也只能被优先方看到和使用。

为了处理在数据层上发生的交易,我们采用一个分散式的逻辑层。 这一层可以建立在现有的以太坊基础设施之上。然而,我们也正在探索EOS的使用,这是一个定制的、可能会扩展到数百万交易的区块链基础架构。

在RepuX协议的基础上,我们建立一个价值层,为上面的层提供权限,并确保人们能够在RepuX协议中为他们所做的工作得到适当的补偿。 我们已经创建了RepuX令牌作为这个价值层的一部分,以允许各方为购买和销售数据和其他商品和/或服务而相互发送价值支付。 令牌的价值可以与它们在数据共享契约服务中使用的需求成比例,而不同层次的令牌持有量可以实现更高级和更大规模的数据共享能力。 这充当了公平分配可用的基于区块链的数据存储的机制,并充当令牌的需求工具,从而实现公平的数据使用。

应用程序层和APIs

区块链凭借对等网络来管理分布式社区中的交易和互动,并通过分散式分类账来管理这种治理,这种分配式分类帐得益于分布式计算基础架构和通用的协议,这使得很难创建欺诈性交易。 通过区块链和分散化,每个实体都被纳入流程中,没有任何一个单一实体能够控制全部流程。

我们从一开始就设计了RepuX,以创建一个任何应用程序开发人员都可以在RepuX协议上工作的应用程序编程接口(或API)。 这个可延展的协议意味着RepuX不是为了一个特定的目的而设计的,而是允许开发人员在它的基础上为了许多不同行业的潜在利益而建造。

API结构

我们打算使用易于使用的Web3.js + Metamask API,这将使得第三方轻松访问,并在RepuX基础架构上快速构建外部应用程序。 除了易于使用的JS APIs之外,我们还可以启用更多基于应用程序的APIs,第三方可以它们为基础进行开发。

数据层

为了确保用户数据以分散的方式存储,我们将使用许多不同的技术。 在本白皮书中,我们描述使用IPFS复述的基于IPFS1的基础架构。 通过RepuX协议,我们使用IPFS来维护我们的逻辑层和APIs中由复述所引用的数据的数据库。 通过使用IPFS,我们不仅确保了我们数据的分散性质,而且通过IPFS复述来确保数据是永久性的。

什么是IPFS?

InterPlanetary文件系统(或IPFS)是一种旨在创建一个永久和分散的方法来存储和共享文件的协议。 它是一个内容寻址、对等超媒体分发协议。 IPFS网络中的节点形成一个分布式文件系统。 IPFS通过一个独特的“复述”对内容片段做地址记录。 IPFS允许创建完全分散的技术,这些技术可以连接同一文档系统内的所有计算设备。 IPFS类似于“变态下载”群体以分散但有组织的方式交换信息。

IPFS的主要特点

IPFS具有以下特点:

但是,由于基础设施仍在快速成熟,我们将继续探索更多的数据基础设施选项,如Storj和Sia。

逻辑

由于我们的RepuX协议包含声誉评估和数据购买和销售,因此我们需要开发一种处理在我们网络上的交易的算法。 在本白皮书中,我们提出一种利用以太坊智能合约能力以分散和透明的方式处理逻辑的方法。 由于以太坊的长期速度,我们将积极尝试状态渠道、EOS、Sharding,甚至是定制的区块链基础设施。

以太坊和智能合约

比特币引入了区块链的概念,使人们能够在没有单一控制机构的情况下进行交易。在此基础上,以太坊开发了分布式计算机的想法。

以太坊是一个基于开源、公共、区块链的分布式计算平台,具有智能合约(脚本)功能。 它提供一个分散的图灵完整的虚拟机,以太坊虚拟机,它可以使用国际公共节点网络执行脚本。 以太坊还提供一个名为“以太”(或ETH)的加密货币令牌,它可以在账户之间传输,并用于补偿进行计算的参与者节点。

实质上,以太坊是一个分散的世界计算机,它使分散的应用程序(或Dapps)能够在全球同步的状态下执行。 由于以太坊能够传递价值和信息,我们可以开发一个能够实现RepuX协议基本功能的演示智能程序。

智能合约是在以太坊区块链上运行的程序,由交易或其他智能合约触发。 智能合同消除了与传统支付系统相关的摩擦,并确保交易涉及的各方都能即时得到支付,并具有无可辩驳的交易证据。

数据

如从下面的演示中可以看出,我们将IPFS数据复述存储在以太坊智能合约之中的私有数据数组中。 稍后可以通过向该智能合约发送预先指定数量的RepuX令牌来访问此项。

pragma solidity ^0.4.8;
contract Registry is Ownable {
    using SafeMath for uint256;
    address public tokenAddress;
    address[] public dataProducts;
    mapping (address => address[]) public dataCreated; mapping (address => address[]) public dataPurchased; mapping (address => bool) public isDataProduct;

event CreateDataProduct(address dataProduct, string ipfsHash);
    event PurchaseDataProduct(address dataProduct, address buyer);
    function Registry(address _tokenAddress) {
        owner = msg.sender;
        tokenAddress = _tokenAddress;
    }

    function deleteDataProduct(address addr) public onlyOwner returns(bool) {
        bool deleted = false;
        uint256 deletedIndex = 0;

    for (; deletedIndex<dataProducts.length; deletedIndex++) {
        if (addr == dataProducts[deletedIndex]) {
            deleted = true;
            break;
        }
    }

    if (deleted) {
        isDataProduct[addr] = false;
        dataProducts[deletedIndex] = dataProducts[dataProducts.length.sub(1)]; delete dataProducts[dataProducts.length.sub(1)];
        dataProducts.length = dataProducts.length.sub(1);
        isDataProduct[addr] = false;
    }
    return deleted;
}

    function createDataProduct(string _name, string _description,
        string ipfsHash, string category, uint256 _price, uint256 size
        ) public returns(address){
        address newDataProduct = new DataProduct(msg.sender, tokenAddress, _name,
        _description, ipfsHash, category, _price, size);
        dataProducts.push(newDataProduct);
        dataCreated[msg.sender].push(newDataProduct);
        isDataProduct[newDataProduct] = true;
        CreateDataProduct(newDataProduct, ipfsHash);
        return newDataProduct;
    }

    function registerUserPurchase(address user) public {
        require(isDataProduct[msg.sender]);
        dataPurchased[user].push(msg.sender);
        PurchaseDataProduct(msg.sender, user);
    }

    function getDataProducts() public constant returns (address[]){
        return dataProducts;
    }

    function getDataCreatedFor(address addr) public constant returns (address[]) {
        return dataCreated[addr];
    }

    function getDataCreated() public constant returns (address[]) {
        return getDataCreatedFor(msg.sender);
    }

    function getDataPurchasedFor(address addr) public constant returns (address[]) {
        return dataPurchased[addr];
    }

    function getDataPurchased() public constant returns (address[]) {
        return getDataPurchasedFor(msg.sender);
    }
}

RepuX反馈和声誉

世界经济建立在一个信任体系之上。 虽然这使得全球化的跨国贸易蓬勃发展,但越来越难以使较小企业和个人在较大的实体中建立声誉。 这已经导致了权力日益集中的分配,伤害了小企业。

同样地,没有一定权威支持的数据通常被认为是不可用的。 这意味着,越来越少的人和企业能够在首先不经过中间人的情况下销售他们的数据。 为了解决这个问题,我们已经在RepuX协议中的每笔交易背后附带了评级和声誉。 如从下面的演示中可以看出,我们将IPFS数据复述存储在以太坊智能合约之中的私有数据数组中。 稍后可以通过向该智能合约发送预先指定数量的RepuX令牌来访问此项。

甲骨文

诚信和信任问题是在线半匿名市场的核心问题。 诚信和信任促进交易的效率。 支付宝、阿里巴巴和电子湾等公司背后的主要想法是解决交易中的信任问题。

备注一:集中式系统中的信任

在集中式的系统中,通过创建一个评级系统,连同一个将那个评级分配给每个交易的中央权威机构,建立信任相对容易。

在发生争议或可疑交易的情况下,各方仅向中央权威机构提交证据,然后由中央权威机构决定交易结果。 即使在中央权威机构的控制下,这个评级也可以被操纵和人为地被提升。9

在分散式系统中,这样的评级机制需要在没有这个中央权威机构的情况下进行。甲骨文系统是这一问题最前沿的解决方案。

使用甲骨文系统时,每笔交易或者异常高的或可疑的评级在被应用于买方和卖方的RepuX地址之前,都需要通过甲骨文。

[9]见https://pages.ebay.com/help/policies/feedback-manipulation.html

RepuX甲骨文智能合同演示:

contract OracleChallenge {
    using SafeMath for uint;
    address public tokenAddress;
    RepuX public RPX;
    uint public initThreshold;
    uint public blockThreshold;
    address public challenged;
    string public descriptionHash;
    address public initiater;
    boolean public initiated;
    boolean public success;
    boolean public ended;
    address[] public voters;
    mapping (address => uint) voterStakes;
    mapping (address => boolean) voterChoices;
    mapping (address => string) evidenceHashes;
    mapping (boolean => uint) stakeTally;
    boolean public leading;
    uint public lastChangeBlock;
    boolean public result;
    boolean public rewardDistributed;
    event Vote(address voter, uint stake, boolean supports);
    event Result(boolean success);

        modifier onlyInitiater() {
        if (msg.sender != initiater) throw;
        _;
        }

        modifier beforeEnd() {
            if (ended) throw;
            _;
        }

        modifier afterEnd() {
            if (!ended) throw;
            _;
        }

        modifier afterInit() {
            if (!initiated) throw;
            _;
        }



        function OracleChallenge(address _challenged, string _descriptionHash) {
            //Constructor function
            challenged = _challenged;
            descriptionHash = _descriptionHash;
            initiater = msg.sender;
        }

        function updateDescription(string newHash) public onlyInitiater beforeEnd {
            descriptionHash = newHash;
        }

        function initiate(uint amount) public onlyInitiater {
            if (amount < initThreshold) throw;
            if (initiated) throw;
            initiated = true;
            voters.push(msg.sender);
            voterStakes[msg.sender] = voterStakes[msg.sender].add(amount);
            voterChoices[msg.sender] = true;
            stakeTally[true] = stakeTally[true].add(amount);
            leading = true;
            lastChangeBlock = block.number;
            RPX.transferFrom(msg.sender, this, amount);
        }

        function vote(boolean support, uint amount, string evidenceHash) public beforeEnd afterInit { tally();
            if (ended) throw;
            if (voted(msg.sender) && support != voterChoices[msg.sender]) throw;
            if (amount == 0) throw;
        RPX.transferFrom(msg.sender, this, amount);
                if (!voted(msg.sender)){
                    voters.push(msg.sender);
            }
            voterStakes[msg.sender] = voterStakes[msg.sender].add(amount); stakeTally[support] = stakeTally[support].add(amount);
            if (evidenceHash != „”){
                evidenceHashes[msg.sender] = evidenceHash;
            }
            Vote(msg.sender, amount, support);
            tally();
        }

        function tally() public beforeEnd afterInit {
            boolean currentLead;
            if (stakeTally[true] > stakeTally[false]) {
                currentLead = true;
            } else if (stakeTally[true] > stakeTally[false]) {
                currentLead = false;
            } else {
                currentLead = leading;

            }

            if (currentLead != leading) {
                lastChangeBlock = block.number;
            } else {
                if (block.number.sub(lastChangeBlock) >= blockThreshold) { result = leading;
                ended = true;
                Result(result);
                distributeRewards();
                }
            }
        }


    function distributeRewards() public afterEnd {
        if (rewardDistributed) {
            Throw;
        }
            rewardDistributed = true;
                for (uint i=0; i < voters.length; i++) {
                    address v = voters[i];
                    uint r = reward(v);
                    if (r > 0) {
                        RPX.transfer(v, r.add(voterStakes[v]));
                    }
                }
            }

            function reward(address addr) constant private afterEnd returns (uint amount) {
                if (voterChoices[addr] != result) {
                    return 0;
                }
                return voterStakes[addr].mul(stakeTally[!result]).div(stakeTally[result]);
            }

            function voted(address addr) constant public returns (boolean) {
                return (voterStakes[addr] > 0);
            }

            function getChoice(address addr) constant public returns (boolean) {
                return voterChoices[addr];
            }

            function getStake(address addr) constant public returns (uint) {
                return voterStakes[addr];
            }




            function getTally(boolean choice) constant public returns (uint) {
                return stakeTally[choice];
            }
        }

通过将甲骨文系统整合到RepuX协议中,我们正在建立一种可以减少在线市场系统中常见的潜在欺诈的方法。

替代区块链

区块链环境不断变化,每天都有创新发生。 因此,RepuX仍然乐于探索将未来可能开发的更有效果、更高效率和可扩展的区块链纳入其中。 目前的示例逻辑合约是使用以太坊的可靠性编程语言构建的。 然而,以太坊仍在发展之中。 我们已经考虑过许多不同的解决方案,目前认为权威证明(或POA)定制区块链很可能是长期最快、最安全的区块链方法。 但是,与权益证明(POS)和工作证明(或POW)相比,它提供的分散化更少.10 最终,我们需要在速度与安全之间取得平衡。一方面是分散化。另一方面,是在最后的RepuX协议的不同逻辑系统中进行选择。

[10]见https://github.com/paritytech/parity/wiki/Proof-of-Authority-Chains

RepuX协议潜在机会的示例

虽然RepuX被设计成一个具有多种不同潜在应用程序的协议级基础结构,但是我们在下面提供了一些使用RepuX协议的潜在机会的例子。 请注意,这些是由第三方应用程序开发人员可以使用RepuX协议并在其基础上构建的情况的示例,不应与RepuX协议本身的建议功能混淆。

下面所举的例子并不是对RepuX协议的潜在用途的详尽描述。

档案数据库

使用RepuX协议的一个潜在机会是与存储在各种档案数据库中的数据相连接。 例如,史密森博物馆拥有一个数十年来收集的庞大档案资料数据库。 这个数据库包含大量的图像数据、文本数据、时间数据和其他可能有用的汇总元数据信息。

不幸的是,史密森尼博物馆很难找到这些数据的买家。 史密森尼可以将这些数据授权给专门从事博物馆的个别公司;然而,进入一个更广阔的市场将更好地为史密森把这些数据货币化。 目前,没有一个占主导地位的接口或平台供 史密森使用以便为这些数据进入更广阔的市场。

RepuX可能会提供一个平台,供史密森为史密森数据进入一个更广阔的市场。 通过将汇总的和匿名的数据上传到RepuX协议的存储层(IPFS),史密森可以为了它的数据而访问更多的潜在客户。 为了进行研究或其他类型的数据分析而寻找综合历史数据的个人和实体,都可以通过RepuX协议轻松地支付博物馆。 通过检查卖家的声誉,潜在买家得到保证数据是合法的。 由于付款是通过区块链上的RepuX令牌发送的,因此卖家得到保证他们将得到适当和分散的支付。

大数据

基于机器学习的分析预计在未来几年内将增长超过2,000亿美元.11 它是一项根植于大数据可用性的大生意。

我们将以Artiq为例。 Artiq是一家基于自然语言的机器学习公司,拥有从情绪分析到文本识别等众多神经深度学习12模型。 Artiq使用这些训练有素的模型,以便为他们的客户削减运营成本。 不幸的是,Artiq花费它的将近80%的收入来收集和准备原始数据本身,经常派人到现场扫描文档的图片,以便训练Artiq的机器学习算法。

RepuX协议可能会帮助像Artiq这样的公司,将数据购买者(如Artiq)与数据收集者相匹配,从而为这样的公司节省大量的时间和成本。 有很多公司(如Evernote)收集庞大的手写文本数据库。 在将这些数据匿名化并在RepuX上提供销售后,Artiq和其他类似的机器学习公司可以从其行业或领域的声誉良好的数据收集者那里购买这些数据,并使用它来训练机器学习算法,从而大大降低运营成本。

[11]见https://www.forbes.com/sites/gilpress/2017/01/20/6-predictions-for--203-billion-big-data- analytics-market /#b96256e20838 [12]见http://ieeexplore.ieee.org/document/6817512/

广告和在线内容

免费增值模式(免费提供基本的数字产品或服务,但为更丰富的功能而收取费用)正迅速成为消费类软件产品的事实上的模型。 用户可以免费访问基本产品或服务;然而,以收集有关用户的数据形式提供产品或服务的实体生成价值。 广告商通常会为这种行为数据支付高额的费用。

我们提供以下虚构的例子。 保罗是一名平面设计师,经常使用他的电脑。 通过使用RepuX协议,第三方应用程序开发人员可以创建程序,保罗可以自愿将其安装到他的计算机上,以记录他的匿名计算机用户数据。 保罗并不介意与其他公司分享这个匿名的数据。

保罗可以立即使用RepuX协议将这些数据提供给潜在的购买者,从而从侧面的数据销售中产生一些额外的收入。 如果保罗持续提供合法、准确和格式良好的数据,他的声誉就会在RepuX协议上上升,这可能会导致他的数据的额外销售。 广告商会欣赏保罗数据的可靠性和可用性,保罗因为他的数据而得到公平的补偿。

电子商务和国际贸易

宏山是一家位于深圳的虚构电子商务企业。 宏山为世界各地的公司制造电子产品。 宏山最大的担忧之一是在解决国际结算中的信任、速度和可靠性。 国际金融结算往往需要多个步骤,三天以上才能收到付款。 延迟的发货和订单也意味着宏山不能可靠地知道客户是否按时付款。 宏山可以使用阿里巴巴等中间商;然而,这些中间商往往为每笔销售收取相当大的费用,以及每年的会员费。13

[13]见https://revenuesandprofits.com/alibaba-makes-money-2016-update/

RepuX协议可以解决这种不确定性和延迟。 RepuX建立在已经到位的基于信誉的系统之上的基础架构, 它可以在每笔交易之后添加某种信任和审查系统。 RepuX协议的这一声誉元素是建立在宏山和其他类似制造商长期的评论基础上的,这将允许宏山有选择地确定哪些客户更有可能按时付款。 同样地,在选择国际制造商的时候,像宏山这样的公司客户也会从RepuX协议的声誉元素中获益。

RepuX可以在甲骨文系统上构建的RepuX协议的声誉元素中开发一个可选的托管系统,从而可以将交易置于一个保持期,以帮助确保恰当的结算。 如果发生欺诈行为,交易各方都必须向甲骨文系统提交可访问的证据,在投票期结束后,如果大多数人确定交易是欺诈性的,那么交易将被推翻。

信用评分

信用评分是根据个人在长期内的经济声誉来确定的。 RepuX协议可以帮助做到这一点。 随着通过RepuX议定书长期发展的内置声誉历史,第三方可以直接从一个人所做的交易中评估这个人的可信度。 一般来说,个人想建立一个强大的信用历史,这将激励这些人在日常交易中使用RepuX协议。

电子销售点(或EPOS)

EPOS设备代表了另一个可以有利地实施RepuX协议的另一个地方。通过EPOS使用RepuX协议进行的每次销售都将:

  1. 被记录在区块链中;

  2. 公开可见;以及

  3. 作为一个不变的会计记录,从而消除欺诈。

小额贷款

小额贷款行业价值超过400亿美元,预计每年将增长20-30%。

由于可以在RepuX协议中建立信用记录,第三方开发人员可以使用RepuX协议构建一个类似小额贷款机构的应用程序。 这样一个小额贷款机构可以利用RepuX协议的声誉元素中所有的信用评估,在区块链上无欺诈和可公开审计。

使用RepuX协议,小额贷款可以轻松地在债权人和借款人之间融资。 例如,债权人可以很容易地购买大量的RepuX声誉认证的贷款,并获得保证,在借款人背后有一定的声誉。

病历

PhenoPh是一家虚构的药品制造和开发公司。 PhenoPh有多种医院经常使用的产品。 PhenoPh也有很多其所销售的药物方面的竞争对手。 为了有效地与竞争对手进行竞争,PhenoPh必须进行重大的市场研究。

RepuX协议可能为这类药品公司的市场研究提供有价值的帮助。 医院收集了大量与他们销售的药品以及病人事件和治疗有关的数据。 这些数据通常对个别医院没有用处。然而,当这些数据被像PhenoPh等公司匿名和汇总时,它对于市场研究的目的可能变得非常有价值。

通过访问这些数据,PhenoPh不仅可以更好地了解其产品及其竞争对手的市场,而且还有可能预测以前无法做到的医疗信息趋势,从而大大地增加其竞争优势。

RepuX令牌使用

数据销售和购买

RepuX将允许RepuX令牌持有者从RepuX协议的销售者那里购买数据。 RepuX协议还将允许数据销售者从购买其数据的个人或实体接收Repux令牌形式的付款。 来自数据收集者的原始数据和/或由第三方应用程序开发人员开发的各种增值内容,可以通过市场或双边交易中的Repux令牌进行购买和销售,数据收集者将开发评估他们的数据的方法。

应用声誉

无论是与数据相关的还是其他方式的每笔交易,都允许Repux协议的用户互相给予对方一个“声誉”。 这是RepuX协议的一个关键特点,因为它使用户能够评估和确定谁是值得信赖的交易对手,谁不是,并且将有助于把在RepuX协议上提供的垃圾邮件和其他错误的数据集过滤掉。

如果各方之间的交易存在争议或声誉被认为不正确,那么Repux协议的用户将被要求向甲骨文系统提交证据以供进一步的验证。

在甲骨文网络上运行

如果交易或信誉评级需要获得甲骨文的批准,RepuX令牌持有者可以自愿提交RepuX令牌并在甲骨文系统中投票。 如果RepuX令牌持有人对正确的判断进行投票,那么他们将获得象征性的费用,例如,应该支付的Repux令牌的0.5%。 这种分散式的判断系统不仅可以为RepuX令牌持有者提供奖励,还可以帮助RepuX协议消除欺诈性交易和提升声誉,否则可能会损害RepuX协议的整体声誉和使用。

建立在网络之上

拥有RepuX令牌将使持有者能够在RepuX协议之上开发第三方应用程序。 例如,第三方开发者可以创建一个应用程序,允许用户出售他们的行为数据,并以RepuX令牌的形式得到支付。 通过拥有更多的RepuX令牌,这个应用程序将能够为业务、研究或其他方面汇聚更大量的数据。

RepuX令牌销售

预售和令牌销售

RepuX令牌是RepuX协议功能的一个组成部分。

RepuX将在未来的某个日期,通过“简单的未来令牌协议(“预售”)”,预售接收RepuX令牌的权利,这仅提供给“认证投资者”。 预售将持续整个十二月份,在基准率$0.20("基准率”)上五折优惠。 任何感兴趣的认证投资者可以通过[email protected]直接联系RepuX,并在repux.io/saft.html下载空白的SAFT,以便了解更多信息。

RepuX计划于2017年12月推出预售,一旦RepuX协议开始运作,2018年3月将进行代币销售。 预售将一直开放至2018年3月开始代币销售。 将提供五部分令牌销售,第一部分在基准率上折扣30%,第二部分在基准率上折扣25%,第三部分在基准率上折扣20%,第四部分在基准率上折扣15%,最后部分在基准率上折扣10%。 我们将推出RepuX令牌,供应5亿张令牌,按照下面表2标题“RepuX令牌费率和分配”进行分配。 RepuX令牌和以太之间的令牌销售市场交换率将基于一个RepuX令牌等于$0.20美元的等价性。

为了在RepuX协议上从事数据交易,数据收集者、数据购买者或第三方开发者必须获取RepuX令牌。

令牌标准

ERC20标准为以太坊区块链上的数字资产提供了一个通用接口。 RepuX令牌遵循ERC20令牌标准,这意味着RepuX令牌持有者可以使用现有的以太坊钱包应用程序(例如Parity, Mist, MyEtherWallet等),很容易地管理和传输他们的RepuX令牌。

RepuX令牌费率和分配

由于RepuX协议的目标是让用户尽可能控制他们的数据,所以RepuX以分散的方式设计了令牌销售。 此分配可能视乎售前售卖的RepuX令牌数量而有所变动,并将在预售结束时最后确定。


表1:RepuX令牌费率

折扣 令牌 价格
预售 50% 100 000 000 $0.10
1-7 30% 75 000 000 $0.14
8-13 25% 15 000 000 $0.15
14-19 20% 15 000 000 $0.16
20-25 15% 15 000 000 $0.17
26-31 10% 30 000 000 $0.18

表2:RepuX令牌的计划分配

事件 分配
预售 20%
令牌销售期间售出的* 30%
奖励汇聚 10%
在平台上售出的 23%
创始团队,3年归属期 12%
大使 3%
令牌销售赏金 2%

*Unsold tokens will be locked up for one year.

所得收益用途

RepuX预计,预售的大量收益将用于推进RepuX协议和RepuX令牌生态系统的开发。

所有未完成的RepuX令牌将由RepuX基金会管理。 RepuX Foundation是一家巴拿马非营利组织,创建于2017年10月,在3½ Miles Philip S.W. Goldson Highway, Belize City, Belize的New Horizon Building大楼地面楼层设有办事处。 RepuX基金会的成立是为了保护RepuX令牌以及代表RepuX通过预售和令牌销售所筹集的资金。 RepuX致力于社区的参与和赞助用户参与分散式数据的世界。 RepuX令牌、相关联的网络和市场都使用由RepuX基金会创建、拥有或许可的商业秘密和知识产权。

RepuX应用程序示例

以下是一个用户可以与RepuX协议进行互动的示例接口。

图3:REPUX协议示例接口

代码分析

下面,我们演示一下我们用来在以太坊网络上演示我们的功能的智能合同草案版本。 请注意,这是一个示例实施,最终的实施可能会更改(也可能是一个自定义区块链的实施)。

下面的合同为RepuX协议上的数据交易定义了一个标准接口。 数据所有者可以通过这个接口管理他们的数据。 数据所有者也可以设置和更新其数据的定价(以RepuX令牌的方式)。 数据所有者也可以更新他们的数据,而版本历史将被合同永久性地记录下来。

contract DataProduct is Ownable {
  using SafeMath for uint256;
  address public registryAddress;
  Registry public registry;
  address public tokenAddress;
  ERC20 private token;
  string public name;
  string public description;
  string public ipfsHash;
  string public category;
  uint256 public price;
  uint256 public size;
  uint256 public creationTimeStamp;
  mapping (address => bool) public ownership;
  mapping (address => bool) public rated; mapping (address => bool) public ratings;
  uint256 public purchaseCount;
  uint8 public minScore = 0;
  uint8 public maxScore = 5;
  mapping (uint8 => uint256) public scoreCount;
  mapping (address => uint8) private userRatings;
  mapping (address => bool) private userRated;
  uint256 public rateCount;
  uint256 private ownerDeposit;
  event Purchase(address purchaser, address recipient);
  event DataUpdate(string originalHash, string newHash);
  event PriceUpdate(uint256 originalPrice, uint256 newPrice);
  modifier onlyRegistry() {
      require(msg.sender == registryAddress);
      _;
  }

  function DataProduct(address _owner, address _tokenAddress, string _name, string _description, string _ipfsHash, string _category, uint256 _price, uint256 _size) public {
    registryAddress = msg.sender;

    registry = Registry(registryAddress);
    owner = _owner;
    ownership[owner] = true;
    tokenAddress = _tokenAddress;
    token = ERC20(tokenAddress);
    name = _name;
    description = _description;
    ipfsHash = _ipfsHash;
    category = _category;
    price = _price;
    size = _size;
    creationTimeStamp = block.timestamp;
  }

    function ownerWithdraw(uint256 amount) public onlyOwner { require(amount <= ownerDeposit);
    ownerDeposit = ownerDeposit.sub(amount); assert(token.transfer(owner, amount));
  }

  function ownerWithdrawAll() public onlyOwner {
    require(ownerDeposit > 0);
    uint256 amount = ownerDeposit; ownerDeposit = 0;
    assert(token.transfer(owner, amount));
  }

  function ownerWithdrawAll() public onlyOwner {
    require(ownerDeposit > 0);
    uint256 amount = ownerDeposit; ownerDeposit = 0;
    assert(token.transfer(owner, amount));
  }

  function getOwnerDeposit() public constant onlyOwner returns(uint256) {
    return ownerDeposit;
  }

  function setPrice(uint256 newPrice) public onlyOwner {
    PriceUpdate(price, newPrice);
    price = newPrice;
  }

  function setSize(uint256 newSize) public onlyOwner {
    size = newSize;
  }

  function setName(string newName) public onlyOwner {
    require(keccak256(newName) != keccak256(„”));
    name = newName;
  }



  function setDescription(string newDescription) public onlyOwner {
    description = newDescription;
  }

  function setCategory(string newCategory) public onlyOwner {
    category = newCategory;
  }

  function purchaseFor(address recipient) public {
    require(!getOwnership(recipient));
    ownership[recipient] = true;
    assert(token.transferFrom(msg.sender, this, price));
    ownerDeposit = ownerDeposit.add(price);
    purchaseCount = purchaseCount.add(1);
    Purchase(msg.sender, recipient);
    registry.registerUserPurchase(recipient);
  }

  function purchase() public {
    purchaseFor(msg.sender);
  }

  function rate(uint8 score) public {
    require(getOwnership(msg.sender));
    require(score >= minScore && score <= maxScore);
    if (userRated[msg.sender]) {
      uint8 originalScore = userRatings[msg.sender];
      require(score != originalScore);
      scoreCount[originalScore] = scoreCount[originalScore].sub(1);
    } else {
      rateCount = rateCount.add(1);
      userRated[msg.sender] = true;
    }
    scoreCount[score] = scoreCount[score].add(1);
    userRatings[msg.sender] = score;
  }

  function cancelRating() public {
    require(userRated[msg.sender]);
    userRated[msg.sender] = false;
    uint8 score = userRatings[msg.sender];
    scoreCount[score] = scoreCount[score].sub(1);
    userRatings[msg.sender] = 0;
    rateCount = rateCount.sub(1);
  }




  function setData(string _ipfsHash) public onlyOwner {
    require(keccak256(_ipfsHash) != keccak256(„”));
    DataUpdate(ipfsHash, _ipfsHash);
    ipfsHash = _ipfsHash;
  }

  function getOwnership(address addr) public constant returns(bool) {
    return ownership[addr];
  }

  function getTotalRating() public constant returns(uint256) {
    uint256 total = 0;
    for (uint8 score=minScore; score<=maxScore; score++) {
      total = total.add(scoreCount[score].mul(score));
    }
    return total;
  }

  function getDataProductFor(address addr) public constant returns (
    //address _this,
    address _owner,
    string _name,
    string _description, string _ipfsHash,
    string _category, uint256 _price,
    uint256 _size,
    uint256 _totalRating,
    uint256 _rateCount,
    uint256 _purchaseCount,
    bool _ownership
  ){
    //_this = this;
    _owner = owner;
    _name = name;
    _description = description; _ipfsHash = ipfsHash;
    _category = category;
    _size = size;
    _price = price;
    _totalRating = getTotalRating();
    _rateCount = rateCount;
    _purchaseCount = purchaseCount;
    _ownership = getOwnership(addr);
  }

  function getDataProduct() public constant returns (
    //address _this,
    address _owner,
    string _name,
    string _description,


    string _ipfsHash,
    string _category,
    uint256 _price,
    uint256 _size,
    uint256 _totalRating,
    uint256 _rateCount,
    uint256 _purchaseCount,
    bool _ownership
  ){
    return getDataProductFor(msg.sender);
  }
}

购买者可以使用RepuX令牌在分散式的平台上购买数据。 智能合约还将允许那些已经购买了数据的人对数据进行评级,从而提高RepuX协议的声誉元素。 由于评级系统是在区块链上运行,它将是完全开放和透明的。

虽然这个合同定义了一个标准接口,但是具体的实施可以改变,以适应来自不同行业的数据或被不同行业使用的数据的不同用例。 例如,可以将额外属性添加到智能合约中以反映与数据相关的特定行业信息。 定价和支付功能也可以改变,以支持不同的支付方式,如订阅模式。

路线图

2017年7月
40万美元的种子资金
2017年9月
来自行业的董事会顾问
2017年10月
RepuX基金会成立
2017年11月
通过合作伙伴发布重大发行公告
代码审核
在区块链博览会上发表讲话
2017年12月
RepuX协议已推出
参加Blockshow Asia
2018年3月
令牌销售
2018年4月
令牌销售审计
2018年5月
RepuX协议开放给开发者
2018年6月
RepuX 平台允许分散式的企业应用程序

我们预计在接下来的几个月里,我们将迅速加快行动。 我们已经完成了RepuX协议级别框架的规范,各种类型的个人和实体数据可以在不同的各方之间被货币化和交换。 在我们计划的2018年2月份的代币销售中,我们将使用我们自己的以太坊智能合约和RepuX代币分配网络界面。

在为令牌销售做准备时,我们将于12月初做一个主要分销公告。

一旦令牌销售完成,我们将能够向我们的企业整合合作伙伴提供基础设施以用于他们的令牌发行,我们的当务之急将是雇用一个更大的C级执行团队,并完成我们与WorkHQ的首次企业整合。

我们的理念是初步测试我们在内部以及与我们的企业整合合作伙伴建立的工具。 然后,我们将在经过彻底测试后向公众推出“RepuX协议”。

RepuX团队

Marcin Welner

在信息行业总共20年。 12年的编程背景。 领导多达100人的部门。 喜欢从头开始建设项目。 在仓储、物流、供应链、电子商务、库存管理、ERP、CRM系统邻域具有广泛的业务技能。

Aleksandra Staszewska

Over 10 years of experience working as Business Analyst in projects for banking, public administration and telco sectors. Worked for national census data analyzing, processing and reporting. Big Data enthusiast having in-depth knowledge of Business intelligence and Data Warehouse systems.

William Ryan

With over 15 years in technology experience and a Bachelor’s in Communication, William has developed a strong passion for community development, fintech, blockchain and philanthropy. His focus is to bring people and technology together for the greater good of humanity, and believes that blockchain has the power to carry that out.

Przemysław Kocznur

10 years of experience as a Senior Software Engineer for companies like Procter&Gamble (Bruno Banani, Mexx, Tom Tailor, Puma Fragrances, Replay), Philips, Bigstar, Hipp, Always, Tchibo, Konica Minolta, Crunchips, Plus, Sygnity, Allegro.

Krzysztof Durałek

Senior User Interface Engineer with over 15 years of experience in Media and FinTech industries. Specializes in modern web technologies with focus on performance, user experience and code quality.

Dawid Rashid

Over 4 years of experience as Full Stack Engineer (JEE, PHP & JS). Contributed to number of projects including the biggest European digital currency exchange platform and Marketing Automation software.

Damian Babula

Software Developer. An early entrant into the bitcoin/blockchain arena, contributed on numerous cryptography-related projects, many of which were open-source. Currently, he is specializing on decentralized applications, development based on smart-contracts and stand-alone blockchains.

Pierre Benezech

4 years of experience in the Blockchain world, working on the integration of different Blockchain technologies for projects within the TelCo, Retail, and Finance industries, and more recently in two ICO initiatives. Speaker at various conferences in the UK, Blockchain Practice Lead at Sytel Reply UK and leader of Blockchain training sessions for employees across Europe.

Partners and Advisors

Dr Jay Best

Dr Best is named Top Crypto Strategist UK 2017, seasoned C-level executive and board member, having pioneered deep learning on GPUs at MIT, now spending most time between London, Cambridge, Oxford and Edinburgh as a lecturer, advisor and investor.

Mateusz Mach

Forbes 30 Under 30. COO of the Opus Foundations - music streaming platform based on Ethereum and IPFS. Advisor to many blockchain based projects running his own Ethereum focused software development company.

Lee Hills

Lee has over a decades’ experience in international corporate structuring and regulated businesses. Lee is especially adept at dealing with new sectors, obtaining regulatory approvals and sourcing/ designing banking solutions for sectors that are considered high risk. This has led Lee to widening his scope of technology expertise to the Blockchain sector, where he was the lead advisor to the first blockchain gambling license and is advising numerous ICOs on jurisdictional matters, AML/ CFT compliance and post ICO business structuring and growth.

Steven Ormond-Smith

Steven is a qualified Chartered Certified Accountant with over 20 years, offshore financial management and control experience. Steven has gained extensive experience in outsourcing projects for banks, law rms, fiduciary, property and trading companies. Prior to founding OrmCo, Steven worked for a Fund Administration company for four years, managing the nance function for several fully listed and AIM listed companies quoted on the London Stock Exchange. Steven has also gained valuable experience working for two of the ‘Big Four’ accounting rms.

WorkHQ

WorkHQ is a cloud based software as a sales platform for small & medium businesses. Its flagship product is its inventory management systems which connects with JD, Amazon and Taobao. WorkHQ plans to release its api to third party developers to develop on top of its platforms while continuing to develop crucial core modules such as accounting, hr and tax returns.

Troutman Sanders LLP

Founded in 1897, Troutman Sanders LLP is an international law firm with more than 650 attorneys practicing in 16 offices located throughout the United States and Asia. The firm’s clients range from large multinational corporations to individual entrepreneurs and reflect virtually every sector and industry. The firm’s heritage of extensive experience, exceptional responsiveness and an unwavering commitment to service has resulted in strong, long-standing relationships with clients across the globe. In recognition of the firm’s strong service culture, Troutman Sanders has been on the BTI Client Service A-Team for 13 consecutive years.

Melrose PR

Melrose PR is a public relations and creative marketing agency located in the heart of Silicon Beach, CA. As millennials working in new media, we sit at the intersection of traditional PR channels and emerging engagement platforms, providing integrated marketing communication solutions for blockchain companies.

Risk Factors

Acquisition of RepuX Tokens involves a high degree of risk. You should consider carefully the risks described below, together with all of the other information contained in this White Paper before making a decision to acquire RepuX Tokens. The following risks entail circumstances under which, our business, financial condition, results of operations and prospects could suffer

Risks associated with the acquisition of RepuX Tokens

RepuX may not successfully develop, market and launch the RepuX Protocol.

Although the RepuX Protocol will be operational prior to the Token Sale, it has not yet been fully developed by RepuX and additional capital funding, as well as developer and management expertise, time and effort will be necessary in order to fully develop and successfully launch a version of the RepuX Protocol in which various types of individual and corporate data can be monetized and exchanged between sellers and purchasers as described above under the heading “Repux Goals and Objectives” (the “Repux Protocol Launch”). RepuX may have to make changes to the speci cations of the RepuX Protocol or RepuX Tokens for any number of legitimate reasons or RepuX may be unable to develop the RepuX Protocol in a way that realizes those specifications or any form of a functioning protocol. It is possible that there may never be operational RepuX Tokens or an operational RepuX Protocol. The RepuX Protocol or RepuX Tokens, if successfully developed and maintained, may not meet expectations of holders of RepuX Tokens at the time of use. Furthermore, despite good faith efforts to develop and launch the RepuX Protocol and subsequently to develop and maintain the RepuX Protocol, it is still possible that the RepuX Protocol will experience malfunctions or otherwise fail to be adequately developed or maintained, which may negatively impact the RepuX Protocol and RepuX Tokens.

RepuX will use the proceeds of the Pre-Sale to make significant investments to develop an operational version of the RepuX Protocol and will subsequently continue to enhance the RepuX Protocol's utility and value, with the goal of achieving the Repux Protocol Launch. However, RepuX may not have or may not be able to obtain the technical skills and expertise needed to successfully complete development of the RepuX Protocol and progress it to a successful RepuX Protocol Launch. While RepuX has sought to retain and continue to competitively recruit experts, there may be a shortage of management, technical, scientific, research and marketing personnel with appropriate training to develop and maintain the RepuX Protocol. If RepuX is not successful in its efforts to demonstrate to users the utility and value of the RepuX Protocol, RepuX may not be able to proceed with the RepuX Protocol Launch.

The acquisition of RepuX Token may involve a high degree of risk.

Financial and operating risks confronting startups are signi cant. The startup market in which RepuX competes is highly competitive and the percentage of companies that survive and prosper is small. Startups often experience unexpected problems in the areas of product development, marketing, financing, and general management, among others, which frequently cannot be solved. In addition, startups may require substantial amounts of nancing, which may not be available through private placements, public markets or otherwise.

RepuX may be forced to cease operations or take actions that result in a Dissolution Event.

It is possible that, due to any number of reasons, including, but not limited to, an unfavorable fluctuation in the value of cryptographic and at currencies, the inability by RepuX to establish the RepuX Tokens’ utility,complete development of the Repux Protocol and proceed with the RepuX Protocol Launch, the failure of commercial relationships, or intellectual property ownership challenges, RepuX may no longer be viable to operate and RepuX may dissolve or take actions that result in a dissolution event.

The tax treatment of the RepuX Token distribution is uncertain and there may be adverse tax consequences for holders upon certain future events.

The tax characterization of the RepuX Tokens is uncertain, and each investor must seek its own tax advice in connection with the acquisition of the RepuX Tokens.The acquisition of RepuX Tokens pursuant to the Token Sale may result in adverse tax consequences to investors, including withholding taxes, income taxes and tax reporting requirements. Each person acquiring RepuX Tokens should consult with and must rely upon the advice of its own professional tax advisors with respect to the United States and non-U.S. tax treatment of an acquisition of the RepuX Tokens.

Risks associated with the RepuX Tokens and the RepuX Protocol

The RepuX Protocol may not be widely adopted and may have limited users.

It is possible that the RepuX Protocol will not be used by a large number of individuals, companies and other entities or that there will be limited public interest in the creation and development of distributed ecosystems (such as the RepuX Protocol) more generally or distributed applications to be used on the RepuX Protocol. Such a lack of use or interest could negatively impact the the RepuX Protocol and the utility of the RepuX Tokens.

Alternative protocols may be established that compete with or are more widely used than the RepuX Protocol.

It is possible that alternative protocols could be established that utilize the same or similar open source code and protocol underlying the RepuX Protocol and attempt to facilitate data monetizing services that are materially similar to the RepuX Protocol’s services. The RepuX Protocol may compete with these alternative protocols, which could negatively impact the RepuX Protocol and the RepuX Tokens.

The open-source structure of the RepuX Protocol means that the RepuX Protocol may be susceptible to developments by users or contributors that could damage the RepuX Protocol and RepuX’s reputation and could affect the utilization of the RepuX Protocol and the RepuX Tokens.

The RepuX Protocol will operate based on an open-source protocol maintained by RepuX and other contributors. As an open source project, the RepuX Protocol will not be represented, maintained or monitored by an official organization or authority. The open-source nature of the RepuX Protocol means that it may be difficult for RepuX or contributors to maintain or develop the RepuX Protocol and RepuX may not have adequate resources to address emerging issues or malicious programs that develop within the RepuX Protocol adequately or in a timely manner. Third parties not affiliated with RepuX may introduce weaknesses or bugs into the core infrastructure elements of the RepuX Protocol and open-source code which may negatively impact the RepuX Protocol. Such events may result in a loss of trust in the security and operation of the RepuX Protocol and a decline in user activity and could negatively impact the utility of the RepuX Tokens.

The RepuX Protocol may be the target of malicious cyberattacks or may contain exploitable flaws in its underlying code, which may result in security breaches and the loss or theft of RepuX Tokens. If the RepuX Protocol’s security is compromised or if the RepuX Protocol is subjected to attacks that frustrate or thwart our users’ ability to access the RepuX Protocol, their RepuX Tokens or the RepuX Protocol data monetization services, users may cut back on or stop using the RepuX Protocol altogether, which could seriously curtail the utilization of the RepuX Tokens.

The RepuX Protocol structural foundation, the open-source protocol, the software application and other interfaces or applications built upon the RepuX Protocol are still in an early development stage and are unproven, and there can be no assurances that the RepuX Protocol and the creating, transfer or storage of the RepuX Tokens will be uninterrupted or fully secure, which may result in a complete loss of users’ RepuX Tokens or an unwillingness of users to access, adopt, utilize and build upon the RepuX Protocol. Further, the RepuX Protocol may also be the target of malicious attacks seeking to identify and exploit weaknesses in the software or the RepuX Protocol, which may result in the loss or theft of RepuX Tokens. For example, if RepuX and the RepuX Protocol are subject to unknown and known security attacks (such as double-spend attacks, 51% attacks, or other malicious attacks), this may materially and adversely affect the RepuX Protocol. In any such event, if the RepuX Protocol Launch does not occur or if the RepuX Protocol is not widely adopted, the RepuX Tokens would have no utility.

The regulatory regime governing the blockchain technologies, cryptocurrencies, tokens and token offerings such as RepuX Protocol and the RepuX Tokens is uncertain, and new regulations or policies may materially adversely affect the development of the RepuX Protocol and the utility of the RepuX Tokens.

Regulation of tokens (including the RepuX Tokens) and token offerings such as this, cryptocurrencies, blockchain technologies, and cryptocurrency exchanges currently is undeveloped and likely to rapidly evolve, varies significantly among international, federal, state and local jurisdictions and is subject to significant uncertainty. Various legislative and executive bodies in the United States and in other countries may in the future, adopt laws, regulations, guidance, or other actions, which may severely impact the development and growth of the RepuX Protocol and the adoption and utility of the RepuX Tokens. Failure by RepuX, the RepuX Foundation or certain users of the RepuX Protocol to comply with any laws, rules and regulations, some of which may not exist yet or are subject to interpretation and may be subject to change, could result in a variety of adverse consequences, including civil penalties and fines.

As blockchain networks and blockchain assets have grown in popularity and in market size, federal and state agencies have begun to take interest in, and in some cases, regulate, their use and operation. In the case of virtual currencies, U.S. state regulators like the New York Department of Financial Services have created new regulatory frameworks. Others, as in Texas, have published guidance on how their existing regulatory regimes apply to virtual currencies. Some U.S. states, like New Hampshire, North Carolina, and Washington, have amended their state’s statutes to include virtual currencies into existing licensing regimes. Treatment of virtual currencies continues to evolve under U.S. federal law as well. The U.S. Department of the Treasury, Securities and Exchange Commission (SEC), and Commodity Futures Trading Commission (CFTC), for example, have published guidance on the treatment of virtual currencies. The U.S. Internal Revenue Service released guidance treating virtual currency as property that is not currency for U.S. federal income tax purposes, although there is no indication yet whether other courts or U.S. federal or state regulators will follow this classification. Both U.S. federal and state agencies have instituted enforcement actions against those violating their interpretation of existing laws.

The regulation of non-currency use of blockchain assets is also uncertain. The CFTC has publicly taken the position that certain blockchain assets are commodities, and the SEC has issued a public report stating U.S. federal securities laws require treating some blockchain assets as securities. To the extent that a domestic government or quasi-governmental agency exerts regulatory authority over a blockchain network or asset, the RepuX Protocol and the RepuX Tokens may be materially and adversely affected.

Blockchain networks also face an uncertain regulatory landscape in many non-U.S. jurisdictions such as the European Union, China and Russia. Various non-U.S. jurisdictions may, in the near future, adopt laws, regulations or directives that affect the RepuX Protocol. Such laws, regulations or directives may conflict with those of the U.S. or may directly and negatively impact our business. The effect of any future regulatory change is impossible to predict, but such change could be substantial and materially adverse to the development and growth of the RepuX Protocol and the adoption and utility of the RepuX Tokens.

New or changing laws and regulations or interpretations of existing laws and regulations, in the U.S. and other jurisdictions, may materially and adversely impact the value of the ETH virtual currency used to acquire RepuX Tokens and otherwise materially and adversely affect the structure or RepuX Tokens and the rights of the holders of RepuX Tokens.

Issuance of RepuX Tokens May Constitute the Issuance of a “Security” Under U.S. Federal Securities Laws

The RepuX Token is a utility token that has a specific consumptive use – i.e., it allows participants in the RepuX Protocol to receive and pay value for data sharing by individuals and entities, and make data available, on a distributed network with significant advantages over current data sharing solutions. Due to the nature of the RepuX Tokens and the manner in which they are being offered, we do not think they should be considered “securities”, as that term is defined in the Securities Act of 1933, as amended (the "Securities Act").

On July 25, 2017, the SEC issued a Report of Investigation (the "Report") under Section 21(a) of the Securities Exchange Act of 1934, as amended (the “Exchange Act”), describing an SEC investigation of The DAO, a virtual organization, and its use of distributed ledger or blockchain technology to facilitate the offer and sale of DAO Tokens to raise capital. The SEC applied existing U.S. federal securities laws to this new paradigm and determined that DAO Tokens were securities. The SEC stressed that those who offer and sell securities in the U.S. are required to comply with U.S. federal securities laws, regardless of whether those securities are purchased with virtual currencies or distributed with blockchain technology. The SEC's announcement, and the related Report, may be found here: https://www.sec.gov/news/press-release/2017-131.

On December 11, 2017, the SEC issued a Cease-and-Desist Order (the “Order”)against Munchee Inc. (“Munchee”) finding that the California-based company’s initial coin offering of its tokens (the “Munchee Tokens”) to raise capital for its blockchain-based food review service constituted an unlawful unregistered offering and sale of securities. The SEC noted in the Order that Munchee had described in its white paper and elsewhere: (1) the actions that it would take to increase the value of Munchee Tokens (including taking Munchee Tokens out of circulation by “burning” them), (2) that it would ensure the ability of holders of Munchee Token to trade them on secondary markets, and (3) how it would buy and sell Munchee Tokens, using its retained holdings, in order to ensure that there was a liquid secondary market in Munchee Tokens. The SEC further noted that, while Munchee told potential purchasers that they would be able to use Munchee Tokens to buy goods or services in its “ecosystem” in the future, as of the time of the offering, they were not able to do so because the ecosystem had not yet been constructed. The SEC also noted that Munchee had “primed purchasers’ reasonable expectations of profit through statements on blogs, podcasts and Facebook that talked about profits.” As a result of these and other factors, the SEC determined that the Munchee Tokens were “securities” and the offering and sale of the Munchee Tokens in its initial coin offering violated the Securities Act. After being contacted by the SEC on November 1, 2017, Munchees terminated its initial coin offering and refunded purchasers’ funds. The Order can be found at: https://www.sec.gov/litigation/admin/2017/33-10445.pdf.

On the same day as it issued the Order, SEC Chairman Jay Clayton released a public statement addressing cryptocurrencies and initial coin offerings (the “Statement”). The Statement cautioned both market professionals and investors and reiterated the SEC’s focus on the application of U.S. federal securities laws to blockchain-based offerings and products, including secondary trading. In the Statement, Chairman Clayton noted that, “Merely calling a token a ‘utility’ token or structuring it to provide some utility does not prevent the token from being a security... Tokens and offerings that incorporate features and marketing efforts that emphasize the potential for profits based on the entrepreneurial or managerial efforts of others continue to contain the hallmarks of a security under U.S. [federal securities] law.” The Statement also noted the possibilities of legally compliant private placements of tokens, tokens that are not securities and avenues by which blockchain based investment and trading might be conducted lawfully, suggesting a goal of regulating rather than eliminating these growing digital markets. The Statement can be found at: https://www.sec.gov/news/public-statement/statement-clayton-2017-12-11

After reviewing the Report, the Order and the Statement, RepuX believes that RepuX Tokens and the manner in which they are being offered are substantially different from the DAO Tokens and Munchee Tokens and their offering processes, and so RepuX Tokens should not be considered “securities” under U.S. federal securities laws. Nevertheless, as noted by the SEC in the Report, the issuance of tokens represents a new paradigm and the application of the federal securities laws to this new paradigm is very fact specific. If RepuX Tokens were deemed to be securities under U.S. federal securities laws, we may be required to terminate the Token Sale in the U.S. and refund funds received from U.S. purchasers of RepuX Tokens. Depending on the portion of the overall Token Sale participants who are U.S. persons, that could result in the RepuX Protocol becoming no longer viable and RepuX being forced to dissolve.

The rights to acquire RepuX Tokens in the Pre-Sale may be subject to registration under the Exchange Act if RepuX has assets above $10 million and more than 2,000 persons participate in the Offering

Companies with total assets above $10 million and more than 2,000 holders of record of its equity securities, or 500 holders of record of its equity securities who are not accredited investors, must register that class of equity securities with the SEC under the Exchange Act. With the capital raised from the Pre-Sale and the Token Sale, RepuX may surpass $10 million in assets as it builds out the RepuX Protocol. Furthermore, the rights to purchase RepuX Tokens pursuant to the SAFTs are likely considered a security under U.S. securities law and because there is the possibility that the Pre-Sale and the Token Sale may surpass 2,000 investors, RepuX may have more than 2,000 holders of record of its equity securities following the Pre-Sale. However, it is possible that the right to acquire RepuX Tokens pursuant to a SAFT is not an “equity security” even if it is a “security”. If the total assets and equity security holders conditions are met, then RepuX would have to register the Pre-Sale and/or the Token Sale with the SEC, which would be a laborious and expensive process. If such registration takes place, much of the information regarding the Pre-Sale and the Token Sale will be available to the public. RepuX would have the ability to avoid registration in such a scenario if the rights to purchase RepuX Tokens pursuant to the SAFTs convert into the RepuX Tokens prior to the last day of RepuX’s fiscal year, but, due to the unpredictable nature of complex software development such as the RepuX Protocol, there is no guarantee that the RepuX Protocol will have launched by such a date.

Holders of RepuX Tokens will have no control and RepuX may only have limited control once the RepuX Protocol Launch occurs.

The RepuX Protocol is comprised of open-source technologies that depend on a network of computers to run certain software programs to process transactions. Because of this less centralized model, RepuX has limited control over the RepuX Tokens and the RepuX Protocol once launched. In addition, holders of RepuX Tokens are not and will not be entitled, to vote or receive dividends or be deemed the holder of capital stock of RepuX for any purpose, nor will anything be construed to confer on holders of RepuX Tokens any of the rights of a stockholder of RepuX or any right to vote for the election of directors or upon any matter submitted to stockholders at any meeting thereof, or to give or withhold consent to any corporate action or to receive notice of meetings, or to receive subscription rights or otherwise.

There may be occasions when certain individuals involved in the development and launch of the RepuX Protocol may encounter potential conflicts of interest in connection with the RepuX Protocol Launch, such that said party may avoid a loss, or even realize a gain, when other holders of RepuX Tokens are suffering losses.

There may be occasions when certain individuals involved in the development and launch of the RepuX Protocol or RepuX Tokens may encounter potential conflicts of interest in connection with the Token Sale and the RepuX Protocol Launch, such that said party may avoid a loss, or even realize a gain, when other holders of the RepuX Tokens are suffering losses. Holders of RepuX Tokens may also have conflicting tax, and other interests with respect to RepuX Tokens, which may arise from the terms of the RepuX Tokens, the RepuX Protocol code, the RepuX Protocol, the timing of the RepuX Protocol Launch or other RepuX Token offerings, or other factors. Decisions made by the key employees of RepuX on such matters may be more beneficial for some holders of RepuX Tokens than for others.

Holders of RepuX Tokens may lack information for monitoring their holdings.

A holder of RepuX Tokens may not be able to obtain all information it would want regarding RepuX, RepuX Tokens, or the RepuX Protocol, on a timely basis or at all. It is possible that a holder of RepuX Tokens may not be aware on a timely basis of material adverse changes that have occurred with respect to the RepuX Protocol. While RepuX has made efforts to use open-source development for the RepuX Tokens, this information may be highly technical by nature. As a result of these difficulties, as well as other uncertainties, a holder of RepuX Tokens may not have accurate or accessible information about the RepuX Protocol.

RepuX Tokens have no history.

The RepuX Token will be a newly formed token and have no history. Each RepuX Token should be evaluated on the basis that RepuX or any third party’s assessment of the prospects of the RepuX Protocol may not prove accurate, and that RepuX will not achieve its business objective.

If the RepuX Protocol is unable to satisfy data protection, security, privacy, and other government-and industry-specific requirements, its growth could be harmed.

There are a number of data protection, security, privacy and other government- and industry-specific requirements, including those that require companies to notify individuals of data security incidents involving certain types of personal data. Security compromises could harm RepuX Protocol’s reputation, erode user confidence in the effectiveness of its security measures, negatively impact its ability to attract new users, or cause existing users to stop using the RepuX Protocol.

The further development and acceptance of blockchain networks, including the RepuX Protocol, which are part of a new and rapidly changing industry, are subject to a variety of factors that are difficult to evaluate. The slowing or stopping of the development or acceptance of blockchain networks and blockchain assets would have a material adverse effect on the successful development and adoption of the RepuX Protocol and the RepuX Tokens.

The growth of the blockchain industry in general, as well as the blockchain networks with which the RepuX Protocol will rely and interact, is subject to a high degree of uncertainty. The factors affecting the further development of the cryptocurrency industry, as well as blockchain networks, include, without limitation:

A decline in the popularity or acceptance of ETH or other blockchain-based tokens would adversely affect our results of operations.

The slowing or stopping of the development, general acceptance and adoption and usage of blockchain networks and blockchain assets may deter or delay the acceptance and adoption of the RepuX Protocol and the RepuX Tokens.

The prices of blockchain assets are extremely volatile. Fluctuations in the price of digital assets could materially and adversely affect our business.

The prices of blockchain assets such as ETH have historically been subject to dramatic fluctuations and are highly volatile. Several factors may influence the utility of the RepuX Tokens, including, but not limited to:

A decrease in the price of a single blockchain assets may cause volatility in the entire blockchain asset industry and may affect other blockchain assets including the RepuX Tokens. For example, a security breach that affects RepuX Token holder or user confidence in ETH may affect the industry as a whole and may also cause the utility of the RepuX Tokens and other blockchain assets to be uncertain.

References

目录