{
  "block": 41376848,
  "op": [
    "comment",
    {
      "author": "steemitboard",
      "body": "Congratulations @eoshenzhen! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@eoshenzhen/birthday2.png</td><td>Happy Birthday! - You are on the Steem blockchain for 2 years!</td></tr></table>\n\n<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@eoshenzhen) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=eoshenzhen)_</sub>\n\n\n**Do not miss the last post from @steemitboard:**\n<table><tr><td><a href=\"https://steemit.com/steemitboard/@steemitboard/use-your-witness-votes-and-get-the-community-badge\"><img src=\"https://steemitimages.com/64x128/https://cdn.steemitimages.com/DQmTugCUsoXX762vg1CuHRrpnPbfnjPogp8iCGv7F2kSVuj/image.png\"></a></td><td><a href=\"https://steemit.com/steemitboard/@steemitboard/use-your-witness-votes-and-get-the-community-badge\">Use your witness votes and get the Community Badge</a></td></tr></table>\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
      "json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}",
      "parent_author": "eoshenzhen",
      "parent_permlink": "bancor-bancorx",
      "permlink": "steemitboard-notify-eoshenzhen-20200305t045954000z",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-03-05T04:59:54",
  "trx_id": "cebcba4c0be01d00f90295d731f459d3004f1274",
  "trx_in_block": 6,
  "virtual_op": 0
}

{
  "block": 36183944,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "5ggc72-or-wps",
      "voter": "quantum-bug",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-09-06T11:54:57",
  "trx_id": "46b507a87f87341565f1f76dc0a11387338556b7",
  "trx_in_block": 10,
  "virtual_op": 0
}

{
  "block": 36183943,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "bancor-bancorx",
      "voter": "quantum-bug",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-09-06T11:54:54",
  "trx_id": "6d83edfcdfec8410bdb2226d2ec2bbe5f43e0f43",
  "trx_in_block": 16,
  "virtual_op": 0
}

{
  "block": 30827553,
  "op": [
    "comment",
    {
      "author": "eoshenzhen",
      "body": "Thanks Argentina for this work 👍",
      "json_metadata": "{\"community\":\"busy\",\"app\":\"busy/2.5.6\",\"format\":\"markdown\",\"tags\":[\"eos\"],\"users\":[],\"links\":[],\"image\":[]}",
      "parent_author": "eosargentina",
      "parent_permlink": "the-newunregdupd-proposal-claiming-tokens-locked-on-contracts",
      "permlink": "re-eosargentina-the-newunregdupd-proposal-claiming-tokens-locked-on-contracts-20190303t105639575z",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-03-03T10:56:39",
  "trx_id": "b6fd0e27790d7e1a15156fa022cefc77d0caedad",
  "trx_in_block": 26,
  "virtual_op": 0
}

{
  "block": 30827526,
  "op": [
    "custom_json",
    {
      "id": "follow",
      "json": "[\"reblog\",{\"account\":\"eoshenzhen\",\"author\":\"eosargentina\",\"permlink\":\"the-newunregdupd-proposal-claiming-tokens-locked-on-contracts\"}]",
      "required_auths": [],
      "required_posting_auths": [
        "eoshenzhen"
      ]
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-03-03T10:55:18",
  "trx_id": "b6222a0a9dcf207b17a10b1e66a828c090518c13",
  "trx_in_block": 5,
  "virtual_op": 0
}

{
  "block": 30825201,
  "op": [
    "custom_json",
    {
      "id": "follow",
      "json": "[\"reblog\",{\"account\":\"eoshenzhen\",\"author\":\"sheldonhuang\",\"permlink\":\"boscore-bos-2-0-2-fixes-and-eosio-1-6-0-and-takeaways\"}]",
      "required_auths": [],
      "required_posting_auths": [
        "eoshenzhen"
      ]
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-03-03T08:59:03",
  "trx_id": "588195378fcbe81aaee5c66de377284b05a8fa84",
  "trx_in_block": 24,
  "virtual_op": 0
}

{
  "block": 30825193,
  "op": [
    "transfer",
    {
      "amount": "0.011 SBD",
      "from": "eoshenzhen",
      "memo": "@sheldonhuang/boscore-bos-2-0-2-fixes-and-eosio-1-6-0-and-takeaways",
      "to": "null"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-03-03T08:58:39",
  "trx_id": "f3e2e1051255328aa9ea0a9e37416e2ed06eedf8",
  "trx_in_block": 24,
  "virtual_op": 0
}

{
  "block": 30819749,
  "op": [
    "comment",
    {
      "author": "steemitboard",
      "body": "Congratulations @eoshenzhen! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@eoshenzhen/birthday1.png</td><td>Happy Birthday! - You are on the Steem blockchain for 1 year!</td></tr></table>\n\n<sub>_[Click here to view your Board](https://steemitboard.com/@eoshenzhen)_</sub>\n\n\n**Do not miss the last post from @steemitboard:**\n<table><tr><td><a href=\"https://steemit.com/carnival/@steemitboard/carnival-2019\"><img src=\"https://steemitimages.com/64x128/http://i.cubeupload.com/rltzHT.png\"></a></td><td><a href=\"https://steemit.com/carnival/@steemitboard/carnival-2019\">Carnival Challenge - Collect badge and win 5 STEEM</a></td></tr></table>\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) and get one more award and increased upvotes!",
      "json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}",
      "parent_author": "eoshenzhen",
      "parent_permlink": "bancor-bancorx",
      "permlink": "steemitboard-notify-eoshenzhen-20190303t042614000z",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-03-03T04:26:15",
  "trx_id": "41fb1e4a5ff9418af659ce404762529292828ce1",
  "trx_in_block": 3,
  "virtual_op": 0
}

{
  "block": 27220747,
  "op": [
    "account_update",
    {
      "account": "eoshenzhen",
      "active": {
        "account_auths": [],
        "key_auths": [
          [
            "STM7QSPBU7A2kKAeeYZoMPEB7mMD7YXKHm3HnEKmDSct69JtJX8CW",
            1
          ]
        ],
        "weight_threshold": 1
      },
      "json_metadata": "{\"profile\":{\"profile_image\":\"https://steemitimages.com/DQmRvaGk76sQQi5d69R6zsVQFRo4ucCwUDTzTEE9AQh9e6W/IMG_7963.PNG\",\"cover_image\":\"https://i.imgur.com/K973Lpf.jpg\",\"location\":\"Shenzhen, China\",\"website\":\"https://eoshenzhen.io/\",\"name\":\"EOShenzhen\",\"about\":\"EOS Evangelist, Block Producer Candidate\",\"twitter\":\"EOSTechLover\",\"youtube\":\"EOShenzhen\"}}",
      "memo_key": "STM5gxgUfpqfhsicHNG9AotN7snBkwq7j23Nrdi1rVWFMYFn73rGV",
      "owner": {
        "account_auths": [],
        "key_auths": [
          [
            "STM7MyxQ9ARDFqtcfr19ZrGRW5W8mZe46Etac4PWUbbr1HS44xQZD",
            1
          ]
        ],
        "weight_threshold": 1
      },
      "posting": {
        "account_auths": [
          [
            "busy.app",
            1
          ]
        ],
        "key_auths": [
          [
            "STM8Us5QYGDGR8PE3Dh3LUJBngbrDWmiFTvvPEr9AyNFNZeShtCGp",
            1
          ]
        ],
        "weight_threshold": 1
      }
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-10-29T03:02:51",
  "trx_id": "24e9064f4844bb37dea5b66aded1bbabaaa9ef77",
  "trx_in_block": 3,
  "virtual_op": 0
}

{
  "block": 26152289,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "bancor-bancorx",
      "voter": "tsto",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-21T23:52:18",
  "trx_id": "c27b14e659160c2bbc309f4ef3138515e821b875",
  "trx_in_block": 12,
  "virtual_op": 0
}

{
  "block": 26088811,
  "op": [
    "transfer",
    {
      "amount": "0.001 STEEM",
      "from": "artcity",
      "memo": "►►► Hi ! You think your post is underrated ? Send 1 SBD or STEEM to @artcity , ☑ Resteem to 16.000+ Followers , ☑ +150 Upvote , ☑ ArtCity 100% Upvote . URL as Memo . Service Active 24/7",
      "to": "eoshenzhen"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-19T18:55:33",
  "trx_id": "0dd0a8814b17e8330e2f44b52bc6ce52c895254f",
  "trx_in_block": 46,
  "virtual_op": 0
}

{
  "block": 26071165,
  "op": [
    "comment",
    {
      "author": "eoshenzhen",
      "body": "@@ -183,16 +183,111 @@\n H%E6%89%A9%E5%B1%95%E5%88%B0EOS%0A\n+!%5BWechatIMG358.png%5D(https://ipfs.busy.org/ipfs/QmaiPTUHKrDgMvBM2JLnKL7xLzDhFtGm85CU1AnRCNBp2T)%0A\n %0A%0A%0A%E6%88%91%E4%BB%AC%E5%BE%88%E9%AB%98%E5%85%B4\n",
      "json_metadata": "{\"tags\":[\"bancor\",\"cross\",\"chain\"],\"image\":[\"https://ipfs.busy.org/ipfs/QmaiPTUHKrDgMvBM2JLnKL7xLzDhFtGm85CU1AnRCNBp2T\",\"https://ipfs.busy.org/ipfs/QmTdwaSQTJR15zQcr6AQUi7Wgi9z51s97DcAfhNhhN9A6c\"],\"links\":[\"https://www.bancor.network\",\"https://www.bancor.network/?utm_source=medium&utm_medium=pr&utm_content=gamedex&utm_campaign=announcement\",\"https://support.bancor.network/hc/en-us/articles/360002098551-Apply-to-join-the-Bancor-Network\",\"https://t.me/bancor\",\"https://busy.org/@eoshenzhen/we-are-eoshenzhen-eos-bp-candidate\",\"https://busy.org/@eoshenzhen/voting-through-imtoken\",\"https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484391&idx=2&sn=8fa9e724a729ecd8bb8e7d2722c14add&chksm=fa0b82dbcd7c0bcd5266bf3cd179d90964b2879c361d26da7cf3e2790b4d87fc34878e57ec9c&scene=21#wechat_redirect\",\"https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484354&idxx=1&sn=ddd4ffdae1531385a07fad59a6e86e6e&chksm=fa0b82fecd7c0be8328a0b3a1cff7de3bef207977ab0ca829c336fb450a7ef5c4153f32d5a4f&scene=21#wechat_redirect\",\"https://eoshenzhen.io\",\"https://steemit.com/@eoshenzhen\"],\"app\":\"busy/2.5.6\",\"format\":\"markdown\",\"community\":\"busy\",\"users\":[\"eoshenzhen\"]}",
      "parent_author": "",
      "parent_permlink": "bancor",
      "permlink": "bancor-bancorx",
      "title": "【公告首发】Bancor发布首款去中心化流动网络跨链产品——BancorX"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-19T04:12:54",
  "trx_id": "76c45cf5be3e1b9609b60c4509b5693bbd2312e1",
  "trx_in_block": 27,
  "virtual_op": 0
}

{
  "block": 26070962,
  "op": [
    "comment",
    {
      "author": "cheetah",
      "body": "Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in:\nhttp://8btc.com/thread-226222-1-1.html",
      "json_metadata": "",
      "parent_author": "eoshenzhen",
      "parent_permlink": "bancor-bancorx",
      "permlink": "cheetah-re-eoshenzhenbancor-bancorx",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-19T04:02:42",
  "trx_id": "1706f64ea6ddae6c098ea6f2a9dfc2d3121f4b40",
  "trx_in_block": 8,
  "virtual_op": 0
}

{
  "block": 26070960,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "bancor-bancorx",
      "voter": "cheetah",
      "weight": 8
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-19T04:02:36",
  "trx_id": "ecded8545a646a79295698e2b1cac730c0a3f109",
  "trx_in_block": 20,
  "virtual_op": 0
}

{
  "block": 26070958,
  "op": [
    "comment",
    {
      "author": "eoshenzhen",
      "body": "本公告由[Bancor官方](https://www.bancor.network)委托EOShenzhen声明，为国内首发，欢迎转载！\n\n\n\n\n\"EOS技术爱好者\"全程由EOShenzhen运营，喜欢我们请为我们投票（EOShenzhen的投票账号：eoshenzhenio）！\n***\n# Bancor发布首款去中心化流动网络跨链产品——BancorX，从ETH扩展到EOS\n\n\n\n我们很高兴宣布，我们将把Bancor协议扩展到EOS上。 Bancor已经在EOS上移植其公开代码，以准备发布去中心化跨链流动网络BancorX，它可支持以太坊和EOS主网。\n\n\n\nBancor最初建立于以太坊区块链，如今从增加对EOS的支持开始，它正逐渐发展为一种跨链流动协议。 Bancor将允许用户针对其自动智能合约（也称为Relay）执行基于EOS的即时代币转换。Relay为用户提供了一种自如转换代币的简单方法，无需将资金存入交易所，也无需买卖双方进行订单匹配。任何人都可以在EOS上创建Relay，并通过他们拥有和管理的智能合约中的代币来将其连接到Bancor的流动网络。 Bancor上列出的基于EOS的代币，很快就可以通过Bancor协议即时转换为任何基于以太坊的代币。\n\n\n\n目前，Bancor已经在EOS上发布了其开源智能合约，以及一个简单的用户界面。该界面使用最受欢迎的EOS网络钱包Scatter，在测试网上处理基于EOS的代币转换。各项目可以在EOS测试网络上创建Reply，以便直接通过用户钱包自动在EOS上实现公平化、低成本和高效率的代币交易。其功能和用户界面均可嵌入到任何环境中，为寻求将跨链自动转换整合到其平台中的项目服务。同时，从该版本还可以看到Bancor对于EOS的优势，包括：\n\n- 1秒钟交易（以太坊> 10秒）\n\n- 无交易费用（以太坊的gas可达到50美元以上）\n\n- 无超前交易风险（EOS交易并不像以太坊那样按gas费用实行优先化）\n\n\n\n作为第一个，同时也是最大的去中心化流动网络，Bancor网络自在以太坊上发布以来，已经处理了超过15亿美元的代币转换。Bancor为超过120个基于以太坊的代币项目提供了价格合理且易于获取的流动性，并且不收取上线费用。在一些前景最为可观的区块链项目在EOS上推出，将为用户提供速度和可扩展性的同时，Bancor正努力扩展其针对EOS生态系统的技术，并将很快发布第一批BancorX上基于EOS的代币。 与以太坊的情况一样，项目加入网络无需上线费用。现在立即申请成为BancorX上的第一批代币吧！\n\n\n\n另一种在EOS上使用Bancor服务的途径，是新推出的EOS赏金计划。我们鼓励社群深入了解我们的代码，并帮助我们发现EOS智能合约中的潜在问题。优化合同或用户界面的开发人员将有机会获得超过50万个Bancor币（BNT）。\n\n\n\n未来几周，请继续关注更多有关BancorX运作的详细信息。我们十分期待Bancor在EOS和以太坊生态系统中发挥其自动跨链流动性，连接全球两大共享基础设施，打造不断壮大且互通的区块链产业。\n\n\n\n## 关于Bancor\n\nBancor是世界上最大的去中心化流动网络。它的运作方式类似于去中心化交易，但关键区别在于：订单是根据区块链上的自动智能合约处理的，而不是在交易中实行双方匹配。任何项目都可以通过Bancor网络上创建Relay，从而轻松整合代币，让用户能够直接通过钱包享受自动化的公平有效的代币转换服务。凭借ETH、DAI、BNB等的8000多个交易对，Bancor上的代币可以实现即时转换。Bancor技术影响着全球范围内的组织和人员，包括区块链团队和代币持有者，以及非洲、亚洲及其他地区的现实社区。访问 [Bancor Web App](https://www.bancor.network/?utm_source=medium&utm_medium=pr&utm_content=gamedex&utm_campaign=announcement)即可立即转换代币，在[Bancor网络上列出您的代币](https://support.bancor.network/hc/en-us/articles/360002098551-Apply-to-join-the-Bancor-Network)或者加入  [Bancor Telegram group](https://t.me/bancor)获取更多信息。\n\n\n\n\n***\n\n**了解更多关于EOShenzhen：**\n\n[We are EOShenzhen](https://busy.org/@eoshenzhen/we-are-eoshenzhen-eos-bp-candidate)\n\n**不同入口如何投票：**\n[imToken](https://busy.org/@eoshenzhen/voting-through-imtoken)\n[火币](https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484391&idx=2&sn=8fa9e724a729ecd8bb8e7d2722c14add&chksm=fa0b82dbcd7c0bcd5266bf3cd179d90964b2879c361d26da7cf3e2790b4d87fc34878e57ec9c&scene=21#wechat_redirect)\n[portal](https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484354&idxx=1&sn=ddd4ffdae1531385a07fad59a6e86e6e&chksm=fa0b82fecd7c0be8328a0b3a1cff7de3bef207977ab0ca829c336fb450a7ef5c4153f32d5a4f&scene=21#wechat_redirect)\n\n**关于我们更多联系：**\nWebsite：https://eoshenzhen.io\n\nSteem：https://steemit.com/@eoshenzhen\n\nBusy：https://busy.org/@eoshenzhen\n\nTelegram：https://t.me/eoshenzhen\n\nTwitter：https://twitter.com/eostechlover\n\n简书：EOS技术爱好者\n\n新浪微博：EOSTechLover\n***\n**EOShenzhen的投票账号：eoshenzhenio**\n![100x100-IMG_7963_small.png](https://ipfs.busy.org/ipfs/QmTdwaSQTJR15zQcr6AQUi7Wgi9z51s97DcAfhNhhN9A6c)",
      "json_metadata": "{\"tags\":[\"bancor\",\"cross\",\"chain\"],\"image\":[\"https://ipfs.busy.org/ipfs/QmTdwaSQTJR15zQcr6AQUi7Wgi9z51s97DcAfhNhhN9A6c\"],\"links\":[\"https://www.bancor.network\",\"https://www.bancor.network/?utm_source=medium&utm_medium=pr&utm_content=gamedex&utm_campaign=announcement\",\"https://support.bancor.network/hc/en-us/articles/360002098551-Apply-to-join-the-Bancor-Network\",\"https://t.me/bancor\",\"https://busy.org/@eoshenzhen/we-are-eoshenzhen-eos-bp-candidate\",\"https://busy.org/@eoshenzhen/voting-through-imtoken\",\"https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484391&idx=2&sn=8fa9e724a729ecd8bb8e7d2722c14add&chksm=fa0b82dbcd7c0bcd5266bf3cd179d90964b2879c361d26da7cf3e2790b4d87fc34878e57ec9c&scene=21#wechat_redirect\",\"https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484354&idxx=1&sn=ddd4ffdae1531385a07fad59a6e86e6e&chksm=fa0b82fecd7c0be8328a0b3a1cff7de3bef207977ab0ca829c336fb450a7ef5c4153f32d5a4f&scene=21#wechat_redirect\",\"https://eoshenzhen.io\",\"https://steemit.com/@eoshenzhen\",\"https://busy.org/@eoshenzhen\",\"https://t.me/eoshenzhen\",\"https://twitter.com/eostechlover\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
      "parent_author": "",
      "parent_permlink": "bancor",
      "permlink": "bancor-bancorx",
      "title": "【公告首发】Bancor发布首款去中心化流动网络跨链产品——BancorX"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-19T04:02:30",
  "trx_id": "e97b36fdc2079838fd57a212180ae43d5da1fba3",
  "trx_in_block": 1,
  "virtual_op": 0
}

{
  "block": 26052987,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "or-wps",
      "voter": "tsto",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-18T12:57:24",
  "trx_id": "649dc835c8ce3a7a2152d4b824fa37ed5e49e763",
  "trx_in_block": 7,
  "virtual_op": 0
}

{
  "block": 26052982,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "5ggc72-or-wps",
      "voter": "tsto",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-18T12:57:09",
  "trx_id": "201ebc5689635516426d73bf6269e3f8cf5e392c",
  "trx_in_block": 19,
  "virtual_op": 0
}

{
  "block": 26032301,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "5ggc72-or-wps",
      "voter": "eoshenzhen",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-17T06:50:21",
  "trx_id": "17e83ed701c5e9f7e0620e367044d6edb6708baf",
  "trx_in_block": 18,
  "virtual_op": 0
}

{
  "block": 26032301,
  "op": [
    "comment",
    {
      "author": "eoshenzhen",
      "body": "\n\n\n\n\n# Emergency Committee Nominees & Alternates\n\n# 关于紧急委员被提名人和候补委员公示\n\n作者：Chris Pollard\n\n翻译：Yvonne\n![WechatIMG330.jpeg](https://ipfs.busy.org/ipfs/Qmf3DUDLYHwnhAw3WXo92EQiGs7qr4BnutSPtg44bwC2Cy)\n*Land in a new territory is auctioned off in this tent (California, 1904)*\n*在这个帐篷里被拍卖掉的新土地(加州，1904年)*\n\n\n\nThe purpose of the Emergency Committee, as it’s currently referred to, is to provide oversight on progress of approved proposals, review new urgent or emergency proposals, and to oversee the receipt of proposals for new governance structures. To learn more about our worker proposal system plan, read the August announcement.\n\n\n\n正如目前所提提及的那样，应急委员会的目的是监督已批准的建议的进展情况、审查新的紧急或紧急议案，并监督新的治理结构建议的接受情况。要了解更多关于我们的工人提案系统计划，请阅读8月份的公告（https://medium.com/eosys/eos-worker-proposal-system-announcement-6addcfb0134c ，中文版[【公告】EOS WPS公告（WPS核心工作组）](https://busy.org/@eoshenzhen/eos-wps-wps)）。\n\n\n\nThe nominees are from several different areas of the community, including existing working group volunteers, block producer team members, award-winning developers and outspoken community members. The characteristics of nominee selection were:\n\n\n\n被提名人来自社区的几个不同领域，包括现有工作组的志愿者、BP、获奖开发者和直言不讳的社区成员。选择被提名人的特点是:\n\n\n\n- A strong community presence;\n\n- Visible integrity;\n\n- Good communication skills in at least one of the three main languages;\n\n- Representative of geographical diversity;\n\n- Having an existing role as an independent thought leader;\n\n- Displaying both strongly held beliefs and an exhibited ability to change one’s mind; and,\n\n- Having a willingness to do the often difficult and thankless work.\n\n\n\n- 具有一定的社区影响力;\n\n- 诚实、可信;\n\n- 在三种主流语言之一中具有良好沟通能力;\n\n- 作为地域多样性的代表;\n\n- 在现有领域扮演领导者的角色;\n\n- 既拥有出坚定的信念，同时拥有改变别人想法的能力; 和愿意从事困难和吃力不讨好的工作。\n\n\n\n### Anand, Gautam\n![紧急WPS11.png](https://ipfs.busy.org/ipfs/QmcRgExzm9hs7NdjmvLgZXj3P5DscAH9zHELHDKqo2ngty)\nGautam is a hands-on technical leader who has built software projects from the ground up — that includes building rapid prototypes, running developer teams, and providing guidance at the management level. His deep expertise is in designing and developing scalable solutions (micro-service architecture) for web applications. He is proactive in the Singapore blockchain developer community, is a 3x Winner of Blockchain Hackathons (2018) and now contributes to some core projects.\n\n\n\nGautam是一位亲力亲为的技术领导者，他从头开始构建软件项目 - 包括构建快速原型，运行开发团队，以及在管理层提供指导。他的专业知识是为Web应用程序设计和开发可扩展的解决方案（微服务架构）。他积极参与新加坡区块链开发者社区，是Blockchain Hackathons（2018）的3倍获奖者，现在为一些核心项目做出贡献。\n\n\n\n###nEspinoza, Branden\n![紧急WPS3.png](https://ipfs.busy.org/ipfs/QmURNRzvcHQCyi1T17n4uk6jUhDFra5WZaPEfoNbMWjMDk)\n\nBranden is a regulatory and compliance training needs expert (AML, CTF, BSA) for financial service organizations from traditional domestic banks to global remittance and exchange houses. He is currently working for StrongBlock designing, documenting, and implementing blockchain governance processes, change management best practices, and execution procedures.\n\n\n\nBranden是传统的国内银行到全球汇款和交易所等金融服务机构的监管和合规培训需求方面的专家（AML，CTF，BSA）。他目前正在为StrongBlock设计，记录和实施区块链治理流程，改善管理最佳实践和执行程序。\n\n\n\n### Kim Naeun / 김나은 / Orchid\n![紧急WPS4.png](https://ipfs.busy.org/ipfs/QmVVJon3zEUPdcK1NaLtnjno3rQbCKhuktFRMMgW1J1jbz)\nA team member of EOSYS, Naeun leads the EOS Evangelist Group, conducts research on EOS, and manages UX projects with global companies. She has a masters degree in Cognitive Science from Yonsei University, HCI Lab.\n\n\n\n\nEOSYS团队成员之一，Naeun领导EOS Evangelist Group，开展EOS研究，并与全球公司一起管理UX项目。她拥有延世大学认知科学硕士学位，HCI实验室。\n\n\n\n### Levine, Dan\n![紧急WPS5.png](https://ipfs.busy.org/ipfs/QmTWaXrNYf738cs7NKFF7KAYjkBiW7uVdCEiufh6k4zcFj)\nDan has been an entrepreneur, engineer and advocate for mission driven consumer and media technology platforms for the past 15 years. At the start of 2017, he left Silicon Valley to explore full time the evolution of community with blockchain technology. His passion lies at the intersection of community, consciousness, creativity and technology.\n\n\n\n在过去的15年里Dan一直是创业者，是工程师和支持任务驱动的消费者和媒体技术平台的倡导者。在2017年初，他离开硅谷，用区块链技术全面探索社区的发展。他的热情在于社区，意识，创造力和技术。\n\n\n\n### Margulies, David / doghouse\n![紧急WPS6.png](https://ipfs.busy.org/ipfs/QmbKEd5KroSTVCKCsf7bfdkFj3ahWqZgw3LMw8NkGqzDG6)\nDavid is a consumer lending veteran with a focus on FinTech. He has worked mainly in Asia and has a track record with liaising across borders and cultures in order to deliver results. Most recently, he has overseen the management of two financial startups which focus on cloud computing and identity management.\n\n\n\nDavid是一位在金融科技领域经验丰富的消费贷的高手。他主要在亚洲工作，并且在跨国界和文化的交流中有着良好的记录，并取得较好的成果。最近，他负责管理两家专注于云计算和身份管理的金融初创公司。\n\n\n\n### Pahalahti, Samuli / Samupaha\n![紧急WPS7.png](https://ipfs.busy.org/ipfs/QmPTYAfwT5F3Sz4WW4SfDnU6zF3GFPMFADCNfbcDhwA2QV)\nSamuli is a libertarian activist and a blockchain enthusiast who is especially interested in governance, economics and game theory. He has been following the advancement of the blockchain scene since 2010.\n\n\n\nSamuli是一位自由主义活动家和区块链爱好者，他对治理、经济学和博弈论特别感兴趣。自2010年以来，他一直关注区块链的发展。\n\n\n\n### Shi Ricky / 施瑞琦\n![紧急WPS8.png](https://ipfs.busy.org/ipfs/QmaLKJG1wfsiMSa1MNhv1185ue7EjUczSir1iqLvqkziwd)\nCo-founder of EOS Cannon, Founder and Director of @BYSTAKE, and 胖哥说币 (Chubby Boy Crytocurrency Talkshow) blogger owner; many years experiences from working in IBM Datayes as a senior technology and full stack engineer. As a serial startup entrepreneur, he has overseen the design, development and operation of multiple web products.\n\n\n\nEOS Cannon的联合创始人、@BYSTAKE的创始人兼董事，以及胖哥说币（Chubby Boy Crytocurrency Talkshow）的创始人; 多年从事IBM Datayes担任高级技术和全栈工程师的经验。作为一名连续创业企业家，他负责监督多个网络产品的设计，开发和运营。\n\n\n\n### Xu Ke / 徐可\n![紧急WPS9.png](https://ipfs.busy.org/ipfs/QmWXDqmDJt6XxZpSxARaHX37rEesb4j5p79LZbdX9DzYfQ)\nKe Xu is the CEO and founder of ONO and CryptoDogs. A serial entrepreneur with her first experience in blockchain as a Bitcoin miner, Ke Xu previously founded ERA, a social network with 10 million users sold to Cheetah Mobile. Ke studied at the University of California, Riverside and the University College London.\n\n\n\n徐可是ONO和CryptoDogs的首席执行官和创始人。她是一个连续创业者，在区块链领域的经验是从作为比特币矿工开始，徐可的此前创立了ERA，这是一个拥有1000万用户的社交网络，销售给猎豹移动。曾就读于加州大学河滨分校和伦敦大学学院。\n\n\n\n\n\nJoin the WPS conversation in our public telegram channel（https://t.me/eosio_wps ).\n\n欢迎加入WPS电报交流群（https://t.me/eosio_wps ）\n\n\n\n\n\n\n本文图片来源于英文原文 \n***\n版权声明：\n\n以下内容来自微信公共帐号“EOS技术爱好者”，搜索“EOSTechLover”即可订阅，翻译Yvonne。转载必须保留以上声明。仅授权原文转载。\n\n本文原文链接为https://medium.com/wps-working-group-eos/emergency-committee-nominees-alternates-52af3dfecf2e\n\n\"EOS技术爱好者\"全程由EOShenzhen运营，喜欢我们请为我们投票：（EOShenzhen的投票账号：eoshenzhenio）！\n***\n\n**了解更多关于EOShenzhen：**\n\n[We are EOShenzhen](https://busy.org/@eoshenzhen/we-are-eoshenzhen-eos-bp-candidate)\n\n**不同入口如何投票：**\n[imToken](https://busy.org/@eoshenzhen/voting-through-imtoken)\n[火币](https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484391&idx=2&sn=8fa9e724a729ecd8bb8e7d2722c14add&chksm=fa0b82dbcd7c0bcd5266bf3cd179d90964b2879c361d26da7cf3e2790b4d87fc34878e57ec9c&scene=21#wechat_redirect)\n[portal](https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484354&idxx=1&sn=ddd4ffdae1531385a07fad59a6e86e6e&chksm=fa0b82fecd7c0be8328a0b3a1cff7de3bef207977ab0ca829c336fb450a7ef5c4153f32d5a4f&scene=21#wechat_redirect)\n\n**关于我们更多联系：**\nWebsite：https://eoshenzhen.io\n\nSteem：https://steemit.com/@eoshenzhen\n\nBusy：https://busy.org/@eoshenzhen\n\nTelegram：https://t.me/eoshenzhen\n\nTwitter：https://twitter.com/eostechlover\n\n简书：EOS技术爱好者\n\n新浪微博：EOSTechLover\n***\n**EOShenzhen的投票账号：eoshenzhenio**\n![100x100-IMG_7963_small.png](https://ipfs.busy.org/ipfs/QmTdwaSQTJR15zQcr6AQUi7Wgi9z51s97DcAfhNhhN9A6c)\n\n",
      "json_metadata": "{\"community\":\"busy\",\"app\":\"busy/2.5.6\",\"format\":\"markdown\",\"tags\":[\"eos\",\"wps\",\"emergency\",\"committee\",\"alternates\"],\"users\":[\"eoshenzhen\",\"BYSTAKE\"],\"links\":[\"https://medium.com/eosys/eos-worker-proposal-system-announcement-6addcfb0134c\",\"https://busy.org/@eoshenzhen/eos-wps-wps\",\"/@bystake\",\"/@bystake\",\"https://t.me/eosio_wps\",\"https://t.me/eosio_wps\",\"https://medium.com/wps-working-group-eos/emergency-committee-nominees-alternates-52af3dfecf2e\",\"https://busy.org/@eoshenzhen/we-are-eoshenzhen-eos-bp-candidate\",\"https://busy.org/@eoshenzhen/voting-through-imtoken\",\"https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484391&idx=2&sn=8fa9e724a729ecd8bb8e7d2722c14add&chksm=fa0b82dbcd7c0bcd5266bf3cd179d90964b2879c361d26da7cf3e2790b4d87fc34878e57ec9c&scene=21#wechat_redirect\"],\"image\":[\"https://ipfs.busy.org/ipfs/Qmf3DUDLYHwnhAw3WXo92EQiGs7qr4BnutSPtg44bwC2Cy\",\"https://ipfs.busy.org/ipfs/QmcRgExzm9hs7NdjmvLgZXj3P5DscAH9zHELHDKqo2ngty\",\"https://ipfs.busy.org/ipfs/QmURNRzvcHQCyi1T17n4uk6jUhDFra5WZaPEfoNbMWjMDk\",\"https://ipfs.busy.org/ipfs/QmVVJon3zEUPdcK1NaLtnjno3rQbCKhuktFRMMgW1J1jbz\",\"https://ipfs.busy.org/ipfs/QmTWaXrNYf738cs7NKFF7KAYjkBiW7uVdCEiufh6k4zcFj\",\"https://ipfs.busy.org/ipfs/QmbKEd5KroSTVCKCsf7bfdkFj3ahWqZgw3LMw8NkGqzDG6\",\"https://ipfs.busy.org/ipfs/QmPTYAfwT5F3Sz4WW4SfDnU6zF3GFPMFADCNfbcDhwA2QV\",\"https://ipfs.busy.org/ipfs/QmaLKJG1wfsiMSa1MNhv1185ue7EjUczSir1iqLvqkziwd\",\"https://ipfs.busy.org/ipfs/QmWXDqmDJt6XxZpSxARaHX37rEesb4j5p79LZbdX9DzYfQ\",\"https://ipfs.busy.org/ipfs/QmTdwaSQTJR15zQcr6AQUi7Wgi9z51s97DcAfhNhhN9A6c\"]}",
      "parent_author": "",
      "parent_permlink": "eos",
      "permlink": "5ggc72-or-wps",
      "title": "【翻译|WPS】关于紧急委员被提名人和候补委员公示"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-17T06:50:21",
  "trx_id": "17e83ed701c5e9f7e0620e367044d6edb6708baf",
  "trx_in_block": 18,
  "virtual_op": 0
}

{
  "block": 26030981,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "v7yy2-or-ian",
      "voter": "ifttt",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-17T05:44:18",
  "trx_id": "9019e2e06e8619855502435b02404ce3fe6d68e9",
  "trx_in_block": 39,
  "virtual_op": 0
}

{
  "block": 26030979,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "or-wps",
      "voter": "ifttt",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-17T05:44:12",
  "trx_id": "49cf2624077e6350bce11747a456a4a4ec234a2f",
  "trx_in_block": 4,
  "virtual_op": 0
}

{
  "block": 26029955,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "v7yy2-or-ian",
      "voter": "sensation",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-17T04:53:00",
  "trx_id": "74b39c011e5142965cc38fcdcf11e739d3435956",
  "trx_in_block": 3,
  "virtual_op": 0
}

{
  "block": 26029521,
  "op": [
    "comment",
    {
      "author": "eoshenzhen",
      "body": "@@ -1,24 +1,26 @@\n+# \n Worker Proposal City %0A%0A%E5%B7%A5\n@@ -18,16 +18,18 @@\n  City %0A%0A\n+# \n %E5%B7%A5%E4%BD%9C%E8%80%85%E6%8F%90%E6%A1%88%E5%9F%8E%E5%B8%82%0A\n@@ -31,16 +31,17 @@\n %E6%8F%90%E6%A1%88%E5%9F%8E%E5%B8%82%0A%0A%0A%0A\n+*\n %E4%BD%9C%E8%80%85%EF%BC%9ADavid\n@@ -50,18 +50,20 @@\n argulies\n+*\n %0A%0A\n+*\n %E7%BF%BB%E8%AF%91%EF%BC%9ALocha\n@@ -68,16 +68,17 @@\n haiching\n+*\n %0A%0A%0A%0AA gr\n",
      "json_metadata": "{\"community\":\"busy\",\"app\":\"busy/2.5.6\",\"format\":\"markdown\",\"tags\":[\"wps\",\"eos\",\"city\",\"proposal\"],\"users\":[\"eoshenzhen\"],\"links\":[\"https://medium.com/wps-working-group-eos/worker-proposal-city-24dd35527ed8\",\"https://busy.org/@eoshenzhen/we-are-eoshenzhen-eos-bp-candidate\",\"https://busy.org/@eoshenzhen/voting-through-imtoken\",\"https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484391&idx=2&sn=8fa9e724a729ecd8bb8e7d2722c14add&chksm=fa0b82dbcd7c0bcd5266bf3cd179d90964b2879c361d26da7cf3e2790b4d87fc34878e57ec9c&scene=21#wechat_redirect\",\"https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484354&idxx=1&sn=ddd4ffdae1531385a07fad59a6e86e6e&chksm=fa0b82fecd7c0be8328a0b3a1cff7de3bef207977ab0ca829c336fb450a7ef5c4153f32d5a4f&scene=21#wechat_redirect\",\"https://eoshenzhen.io\",\"https://steemit.com/@eoshenzhen\",\"https://busy.org/@eoshenzhen\",\"https://t.me/eoshenzhen\",\"https://twitter.com/eostechlover\"],\"image\":[\"https://ipfs.busy.org/ipfs/QmTnUfadAGhxV48s4WrtQTTVDhnteqd62Ntpc1zTzuYoTB\",\"https://ipfs.busy.org/ipfs/QmPEBLSNECUGT5o96w251tFHL2Rm9v9hNsxnzQiwk5bwPT\",\"https://ipfs.busy.org/ipfs/QmWK8R989NBnAa4erwdKV6R6auBXrymhUhaXSts6wkLsZN\",\"https://ipfs.busy.org/ipfs/QmR9f38zEc4Qjp2dPDGMQbmLrPu3BBiXSGDLKSwz1M5yQt\",\"https://ipfs.busy.org/ipfs/QmSPjh1nBRgZwDaRDRaJLxXNP3Z5d7ioCuqAcsvQ6A5584\",\"https://ipfs.busy.org/ipfs/QmUKnkmXadhK9K15EuUWVHipGGyaFDVkP7AsvHDnsvoxuz\",\"https://ipfs.busy.org/ipfs/QmVddg2xrzy8gUpEU8QTijgmubNw8DerkVDbutDNhDam3Y\",\"https://ipfs.busy.org/ipfs/QmWDsU4f3skt65VoA1T5xGosRWaZxrq3eJHkNQNPSojfRW\",\"https://ipfs.busy.org/ipfs/QmRUjN6ggiRAbsU1djvNy3G6fR1bWm784Wmncq4KiHBTiy\",\"https://ipfs.busy.org/ipfs/QmUh8kBffkJ9M19obRJVvMoA7fXxsf1UNuBYNqmhSE3AsG\",\"https://ipfs.busy.org/ipfs/QmTdwaSQTJR15zQcr6AQUi7Wgi9z51s97DcAfhNhhN9A6c\"]}",
      "parent_author": "",
      "parent_permlink": "wps",
      "permlink": "or-wps",
      "title": "【翻译|WPS】工作者提案城市"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-17T04:31:18",
  "trx_id": "55af6a5464c65f843a45390f42d230a6766c11d6",
  "trx_in_block": 29,
  "virtual_op": 0
}

{
  "block": 26029467,
  "op": [
    "comment",
    {
      "author": "cheetah",
      "body": "Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in:\nhttps://medium.com/wps-working-group-eos/worker-proposal-city-24dd35527ed8",
      "json_metadata": "",
      "parent_author": "eoshenzhen",
      "parent_permlink": "or-wps",
      "permlink": "cheetah-re-eoshenzhenor-wps",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-17T04:28:36",
  "trx_id": "95415cf24e919a7cf8d3d188127fa8d02d3ce25b",
  "trx_in_block": 9,
  "virtual_op": 0
}

{
  "block": 26029465,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "or-wps",
      "voter": "cheetah",
      "weight": 8
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-17T04:28:30",
  "trx_id": "1efcd47baed04c133aaa208407b27fe74c597454",
  "trx_in_block": 18,
  "virtual_op": 0
}

{
  "block": 26029463,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "or-wps",
      "voter": "eoshenzhen",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-17T04:28:24",
  "trx_id": "db2c3167d805f000b39e327f1bde6fe91b45ba09",
  "trx_in_block": 9,
  "virtual_op": 0
}

{
  "block": 26029463,
  "op": [
    "comment",
    {
      "author": "eoshenzhen",
      "body": "Worker Proposal City \n\n工作者提案城市\n\n\n\n作者：David Margulies\n\n翻译：Lochaiching\n\n\n\nA graphic metaphor by David Margulies and Chris Pollard. Both are members of the EOS WPS working group.\n\n\n\n本文描绘的一个想象社区的构造，想法来自于David Margulies和Chris Pollard，以上两者都是EOS WPS工作组的成员。\n\n\n\nIn the beginning there was the EOS blockchain. There were block producers and token holders. For most, conditions were harsh and life was uncertain.\n![WPC1.jpeg](https://ipfs.busy.org/ipfs/QmTnUfadAGhxV48s4WrtQTTVDhnteqd62Ntpc1zTzuYoTB)\n一开始的EOS区块链中有BP和token持有者。对大多数人来说，整个环境可能是不尽如意的、不确定的。\n\n\n\nThe Worker Proposal System (WPS) Group formed, with the aim to help transform EOS into a city that the owners would be proud of.\n\n\n\nWPS组织成立的目的，是为了让EOS变成一个持有者会感到自豪的城市。\n![WPC2.png](https://ipfs.busy.org/ipfs/QmPEBLSNECUGT5o96w251tFHL2Rm9v9hNsxnzQiwk5bwPT)\nThe first task was to purchase the land; a small piece of land to start with. These were the EOS tokens that would help to fund the transformation.\n\n\n\n第一项任务是购买土地，从一小片土地开始。EOS的token将有助于资金的转入转出。\n![WPC3.png](https://ipfs.busy.org/ipfs/QmWK8R989NBnAa4erwdKV6R6auBXrymhUhaXSts6wkLsZN)\nThe construction trailer was setup, where the Emergency Committee started work in supporting the urgent works.\n\n\n\n施工拖车已安装完毕，同时应急委员会已经可以开始紧急事务的处理了。\n![WPC4.png](https://ipfs.busy.org/ipfs/QmR9f38zEc4Qjp2dPDGMQbmLrPu3BBiXSGDLKSwz1M5yQt)\nThe underground plumbing and the electricity grids were constructed. This core infrastructure included emergency needs like ECAF funding and code repository management.\n\n\n\n同时社区也修建了地下管道和电网这些核心基础设施，其中包括紧急需求，如ECAF资金和代码存储库管理。\n![WPC5.png](https://ipfs.busy.org/ipfs/QmSPjh1nBRgZwDaRDRaJLxXNP3Z5d7ioCuqAcsvQ6A5584)\n The zoning began. The Emergency Committee went about staking plots of land for each neighbourhood.\n\n\n\n这个时候开始分区了。紧急事务委员会着手为每一片居民区划清界限并规划地区。\n![WPC6.png](https://ipfs.busy.org/ipfs/QmUKnkmXadhK9K15EuUWVHipGGyaFDVkP7AsvHDnsvoxuz)\nA global competition was held, where any person or team could submit a design for a neighbourhood. This was an open call to build the best governance design for a new category of works.\n\n\n\n这个时候举办了一场全球性的竞赛，任何个人或团队都可以提交关于社区的设计方案。比如这一次，是为了新的工作类别构建最佳治理设计的公开呼吁。\n\n\n\nEach time a winning team was voted by the community, the neighbourhood was born, with an ownership of 10% of the city’s land.\n\n\n\n每次都由社区投票选出获胜的队伍，这也意味着诞生了一个拥有城市10%面积份额的社区。\n\n\n\nThe Neighbourhoods\n\nThe Oversight neighbourhood is like the city hall. This is is where the works in other neighbourhoods are overseen and where the Worker Proposal System is maintained.\n\n\n\n社区一带\n\n监督这一层的社区就像是现在的市政厅。这是其他社区工程被监督的地方，也是WPS能够持续的原因。\n![WPC7.png](https://ipfs.busy.org/ipfs/QmVddg2xrzy8gUpEU8QTijgmubNw8DerkVDbutDNhDam3Y)\nThe Infrastructure neighbourhood is like the Department of Public Works. This is where the work is dirty and there is no praise. This is where we keep the underlying code base healthy, where security audits and bug patches are done.\n\n\n\n社区基础设施这一层就像现在的公共工程部门。这是工作肮脏、没有赞美的地方，是我们保持底层代码基础健康的地方，也是安全审计和bug修复的地方。\n![WPC8.png](https://ipfs.busy.org/ipfs/QmWDsU4f3skt65VoA1T5xGosRWaZxrq3eJHkNQNPSojfRW)\nThe Community neighbourhood is like the public parks, the schools and the tourist attractions. This neighbourhood supports meetups, education and the resources and spaces that strengthen the community.\n\n\n\n社区这一层就像公园、学校和旅游景点。这一层的社区支持线下聚会、教育、资源和空间共享来加强整个社区的连接。\n![WPC9.png](https://ipfs.busy.org/ipfs/QmRUjN6ggiRAbsU1djvNy3G6fR1bWm784Wmncq4KiHBTiy)\nThe Developer neighbourhood is like the light industrial district. It is for supporting developers and ideas that will enrich the community.\n\n\n\n开发者这一层就像轻工业园区。它的存在是为了支持开发者和各种想法，这将丰富社区元素。\n\n\n\nThe Miscellaneous neighbourhood is like the artist lofts and the repurposed space. This neighbourhood is for swag, burning and projects that may not fit in anywhere else.\n![WPC10.png](https://ipfs.busy.org/ipfs/QmUh8kBffkJ9M19obRJVvMoA7fXxsf1UNuBYNqmhSE3AsG)\n杂七杂八这一层就像艺术家的阁楼和重新利用的空间，这一层是为可能不适合其他分类的项目而建的。\n\n\n\n本文图片来源于英文原文\n\n***\n版权声明：\n\n以下内容来自微信公共帐号“EOS技术爱好者”，搜索“EOSTechLover”即可订阅，翻译Lochaiching。转载必须保留以上声明。仅授权原文转载。\n\n本文原文链接为https://medium.com/wps-working-group-eos/worker-proposal-city-24dd35527ed8\n\n\"EOS技术爱好者\"全程由EOShenzhen运营，喜欢我们请为我们投票：（EOShenzhen的投票账号：eoshenzhenio）！\n***\n\n**了解更多关于EOShenzhen：**\n\n[We are EOShenzhen](https://busy.org/@eoshenzhen/we-are-eoshenzhen-eos-bp-candidate)\n\n**不同入口如何投票：**\n[imToken](https://busy.org/@eoshenzhen/voting-through-imtoken)\n[火币](https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484391&idx=2&sn=8fa9e724a729ecd8bb8e7d2722c14add&chksm=fa0b82dbcd7c0bcd5266bf3cd179d90964b2879c361d26da7cf3e2790b4d87fc34878e57ec9c&scene=21#wechat_redirect)\n[portal](https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484354&idxx=1&sn=ddd4ffdae1531385a07fad59a6e86e6e&chksm=fa0b82fecd7c0be8328a0b3a1cff7de3bef207977ab0ca829c336fb450a7ef5c4153f32d5a4f&scene=21#wechat_redirect)\n\n**关于我们更多联系：**\nWebsite：https://eoshenzhen.io\n\nSteem：https://steemit.com/@eoshenzhen\n\nBusy：https://busy.org/@eoshenzhen\n\nTelegram：https://t.me/eoshenzhen\n\nTwitter：https://twitter.com/eostechlover\n\n简书：EOS技术爱好者\n\n新浪微博：EOSTechLover\n***\n**EOShenzhen的投票账号：eoshenzhenio**\n![100x100-IMG_7963_small.png](https://ipfs.busy.org/ipfs/QmTdwaSQTJR15zQcr6AQUi7Wgi9z51s97DcAfhNhhN9A6c)\n\n",
      "json_metadata": "{\"community\":\"busy\",\"app\":\"busy/2.5.6\",\"format\":\"markdown\",\"tags\":[\"wps\",\"eos\",\"city\",\"proposal\"],\"users\":[\"eoshenzhen\"],\"links\":[\"https://medium.com/wps-working-group-eos/worker-proposal-city-24dd35527ed8\",\"https://busy.org/@eoshenzhen/we-are-eoshenzhen-eos-bp-candidate\",\"https://busy.org/@eoshenzhen/voting-through-imtoken\",\"https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484391&idx=2&sn=8fa9e724a729ecd8bb8e7d2722c14add&chksm=fa0b82dbcd7c0bcd5266bf3cd179d90964b2879c361d26da7cf3e2790b4d87fc34878e57ec9c&scene=21#wechat_redirect\",\"https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484354&idxx=1&sn=ddd4ffdae1531385a07fad59a6e86e6e&chksm=fa0b82fecd7c0be8328a0b3a1cff7de3bef207977ab0ca829c336fb450a7ef5c4153f32d5a4f&scene=21#wechat_redirect\",\"https://eoshenzhen.io\",\"https://steemit.com/@eoshenzhen\",\"https://busy.org/@eoshenzhen\",\"https://t.me/eoshenzhen\",\"https://twitter.com/eostechlover\"],\"image\":[\"https://ipfs.busy.org/ipfs/QmTnUfadAGhxV48s4WrtQTTVDhnteqd62Ntpc1zTzuYoTB\",\"https://ipfs.busy.org/ipfs/QmPEBLSNECUGT5o96w251tFHL2Rm9v9hNsxnzQiwk5bwPT\",\"https://ipfs.busy.org/ipfs/QmWK8R989NBnAa4erwdKV6R6auBXrymhUhaXSts6wkLsZN\",\"https://ipfs.busy.org/ipfs/QmR9f38zEc4Qjp2dPDGMQbmLrPu3BBiXSGDLKSwz1M5yQt\",\"https://ipfs.busy.org/ipfs/QmSPjh1nBRgZwDaRDRaJLxXNP3Z5d7ioCuqAcsvQ6A5584\",\"https://ipfs.busy.org/ipfs/QmUKnkmXadhK9K15EuUWVHipGGyaFDVkP7AsvHDnsvoxuz\",\"https://ipfs.busy.org/ipfs/QmVddg2xrzy8gUpEU8QTijgmubNw8DerkVDbutDNhDam3Y\",\"https://ipfs.busy.org/ipfs/QmWDsU4f3skt65VoA1T5xGosRWaZxrq3eJHkNQNPSojfRW\",\"https://ipfs.busy.org/ipfs/QmRUjN6ggiRAbsU1djvNy3G6fR1bWm784Wmncq4KiHBTiy\",\"https://ipfs.busy.org/ipfs/QmUh8kBffkJ9M19obRJVvMoA7fXxsf1UNuBYNqmhSE3AsG\",\"https://ipfs.busy.org/ipfs/QmTdwaSQTJR15zQcr6AQUi7Wgi9z51s97DcAfhNhhN9A6c\"]}",
      "parent_author": "",
      "parent_permlink": "wps",
      "permlink": "or-wps",
      "title": "【翻译|WPS】工作者提案城市"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-17T04:28:24",
  "trx_id": "db2c3167d805f000b39e327f1bde6fe91b45ba09",
  "trx_in_block": 9,
  "virtual_op": 0
}

{
  "block": 26029323,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "v7yy2-or-ian",
      "voter": "tsto",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-17T04:21:24",
  "trx_id": "0b4098c2b5241d9811bb68f1d168882f78f2a7fb",
  "trx_in_block": 15,
  "virtual_op": 0
}

{
  "block": 26029276,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "v7yy2-or-ian",
      "voter": "satyadev",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-17T04:19:03",
  "trx_id": "df034c34539611bce08cfec0f35f979f297d5939",
  "trx_in_block": 15,
  "virtual_op": 0
}

{
  "block": 26029247,
  "op": [
    "comment",
    {
      "author": "introduce.bot",
      "body": " @eoshenzhen, I gave you a vote!<br>If you follow me, I will also follow you in return!",
      "json_metadata": "",
      "parent_author": "eoshenzhen",
      "parent_permlink": "v7yy2-or-ian",
      "permlink": "introduce-bot-re-eoshenzhenv7yy2-or-ian",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-17T04:17:36",
  "trx_id": "c8a2677c69fd7c09a95d52c64706ee3a7fdad8fb",
  "trx_in_block": 20,
  "virtual_op": 0
}

{
  "block": 26029247,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "v7yy2-or-ian",
      "voter": "introduce.bot",
      "weight": 100
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-17T04:17:36",
  "trx_id": "256520be57214327da6a613fd2f8dba242dee659",
  "trx_in_block": 8,
  "virtual_op": 0
}

{
  "block": 26029244,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "v7yy2-or-ian",
      "voter": "eoshenzhen",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-17T04:17:27",
  "trx_id": "d5049e782f251b5b1b24fa24d7548634620dc2af",
  "trx_in_block": 9,
  "virtual_op": 0
}

{
  "block": 26029244,
  "op": [
    "comment",
    {
      "author": "eoshenzhen",
      "body": "# The Message is the Medium\n\n# 信息就是中介\n\n\n\n作者：Ian Grigg\n翻译：Gavin\n校对：Lochaiching\n\n\n\n## A Preliminary Message\n\n## 初步信息\n\nThis post introduces what I think is a fundamental flaw in almost all blockchain designs. In brief, it is the emphasis on state as the ‘atomic element’, when we could also build using messages instead. The implications of this are quite severe, but also quite hard to understand because the computer science concepts are a bit inaccessible to the non-CS world.\n\n\n\n这篇文章介绍了我认为几乎所有区块链设计中都存在的一个基本缺陷。简而言之，当我们使用消息来构建时，强调将state作为“核心元素”。这其中的影响是相当巨大的，但也很难理解，因为计算机科学的概念对not-CS世界来说有点难以理解。\n\n\n\nWhat follows is a very informal, non-rigourous description to try and explain the difference between messaging and state to the non-technical audience. I’ve tried to get the simple message across but if you find yourself in a state of confusion, there is another way to understand it and that is to watch this space - we’re going to build it,so then the message will be put to the medium. Enough bad analogies, let’s forge on.\n\n\n\n接下里是一个非正式的、非严格的描述，试图向一些非该专业领域的读者解释消息和state的区别。我试着以简单的方式来引导大家理解它，但是如果你发现自己还是处在一种混乱的状态下，这有另一种理解它的方法那就是关注进一步的进展——我们要建立它，这样信息就会被放到媒介上。有点糟糕的比喻，让我们继续吧。\n\n\n\n## What’s a State Machine, anyway?\n\n## 所以什么是状态机\n\nA state machine is a computer science invention to capture the reliable, deterministic machine. In words, it is a software “machine” that given some set of inputs and memory, always delivers the same outputs.\n![ian消息媒介1.png](https://ipfs.busy.org/ipfs/QmbXQCiNWPGGSWun8WB9A9ncshoGsW6DAY6V3jqGEyh5cM)\n\n状态机是一种计算机科学发明(https://busy.org/exit?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FFinite-state_machine) ，用于捕获可靠的、具有确定性信息的机器。 简而言之，它是一个软件“机器”，它被给与一系列输入和内存，总是提供相同的输出。\n\n \n\nThink about a vending machine, and the software inside, which has to simulate the hardware machine so as to figure out what to do next. In words,  “if we are in State 1, wait for coin. If a coin turns up, enter State 2. If in State 2, wait for button push. If a button push turns up, deliver drink, go to State 1.” In essence then, our machine consists of some code to handle that algorithm, some state (memory) to recall where we are, and an ability to read incoming messages (coins, buttons) and write outsome instructions as messages (drink!).\n\n\n\n想想一台自动售货机，以及内部的软件，它必须模拟外部硬件，以便确定下一步该做什么。 换句话说，“如果我们处于状态1，就是等待投入硬币。 如果硬币投进来，就转换到状态2。如果处于状态2，就是等待按钮按下。 如果一个按钮按下，提供饮料，转到状态1。”从本质上说，我们的机器包含一些代码来处理该算法，一些state（内存）来存储我们的状态，以及读取传入消息（ 硬币，按钮）和做出一些行为作为输出消息（饮料！）的能力。\n\n\n\n*Figure 2 - a coke machine .png（编辑部：图挂了）*\n\n\n\nWe can also construct bigger state machines out of smaller ones - a database is essentially an enormous state machine, made up many little machines for each SQL table, each row and each cell. A protocol is a small state machine made of two state machines - one for each end. A blockchain is another enormous state machine, made of thousands of “full node” state machines with lots of hangers-on called SPV clients. While the essence of the design of a state machine is pretty simple, using them is as much an art as a science because we don’t have a great view on how to compose small state machines into large state machines. But we’ll leave aside that complexity for now.\n\n\n\n我们还可以用较小的状态机构建更大的状态机 - 数据库本质上是一个巨大的状态机，由每个SQL表的每行和每个单元作为多个小的状态机构成的。 协议是由两台状态机组成的小型状态机 - 每端一台。 区块链是另一个巨大的状态机，由数千个“全节点”状态机组成，其中有许多挂机，称为SPV客户端。 虽然状态机设计的本质非常简单，但使用它们既是一门科学又是一门艺术，因为我们对如何将小型状态机组成大型状态机没有很深入的了解。 我们暂时不考虑这种复杂性。\n\n\n\n## Choice\n\n## 选择\n\nIt turns out that there are two fundamental approaches to building a state machine.\n\n\n\n事实证明，构建状态机有两种基本方法。\n\n\n\nNote, what follows is a very stylised viewpoint, not a rigorous one. We ignore the code above, and just assume it is referenced wherever needed. We also ignore the output messages, for simplicity. Our goal is to get you to a state of understanding the message, not to impress CS geeks.\n![ian消息媒介3.png](https://ipfs.busy.org/ipfs/QmTcJMyPC43TSUwjo94BLG7e4kLJ2P1mHit7vwqDmXWyM2)\n请注意，以下是一个非常风格化的观点，而不是严谨的观点。 我们忽略上面的代码，并假设它在需要的地方被引用。 为简单起见，我们也忽略了输出消息。我们的目标是让普通人了解消息，而不是给CS极客们留下深刻印象。\n\n \n\nWe normally model the state machine as above - it starts out in State One, and then Message 1 arrives. The processing of this message causes a transition from State One to State Two. On transitioning to State 1, the machine sends out messages,although that is strictly optional - it depends on the machine’s needs at that transition.\n\n\n\n我们通常以上述方式对状态机进行建模 - 它从状态1开始，然后到达消息1。处理此消息会导致从状态1转换到状态2。 在转换到状态1时，机器发出消息，尽管这是非常严格并且可选的 – 但它还是取决于机器在该转换时的需求。\n\n\n\nOur job in building the state machine is to write the code to store and transition all states for all known messages. It turns out that, in doing this job, there are two fundamentally different ways in which to write the machine, and the choice of which colours our thinking, our design and eventually our capabilities.\n\n\n\n我们构建状态机的工作是编写代码来实现存储和转换所有已知信息的状态。 事实证明，在完成这项工作时，有两种根本不同的方式来编写机器，以及选择哪种取决于我们的思维、设计和能力。\n\n\n\n>First Way: Thinking of it as a machine of states. In this view, we store State One. Then, when the message arrives, the machine turns over to State Two, and we store that new state. Repeat! Think of the states as the Blue Circles above, and you can ignore any other view of the world.\n\n\n\n>第一种方法：把它看作是一种状态的机器。在这个视图中，我们存储状态1。然后，当消息到达时，机器转到状态2，然后存储这个新状态。重复这个循环，把这些状态想象成上面的蓝色圆圈，你就可以忽略任何其他的世界角度。\n\n\n\n>Second Way: Thinking of it as a machine of messages. In this alternate view, we record the messages. We always start the machine at State One. Then we pump all of the incoming messages (Red Pills above) into the machine (and out pops any new messages). We store the messages, but don’t bother with the state, because we can calculate it any time.\n\n\n\n>第二种方法：把它看作是信息的机器。在这个备用视图中，我们记录消息，并且总是在状态1的时候启动机器。然后，我们将所有需要输入的信息(上面的红色药丸)输入到机器(并弹出任何新的信息)中。我们存储信息，但不关心状态，因为有了信息之后我们可以随时计算出状态的情况。\n\n\n\nThese views are mostly equivalent in theory, and the trick to understanding this is that the machine is deterministic . Once we’ve established the machine as being exact and unforgiving in its actions, we know that for example M1 on State1 always results in State2 (and M2 out).\n\n\n\n这些观点在理论上大多相同，理解这一点的关键是“机器是确定性的”。 一旦我们确定机器在其动作中是精确且无情的，我们就知道例如状态1上的M1总是导致State2（和M2输出）。\n\n\n\nThen, if we have the machine, and we have the set of messages, we can always roll it again to get the states. **OR** , if we have recorded the states, we can always walk the chain of states to reproduce the action, although we don’t necessarily know what messages caused that journey. If you like your graphs, you could think of the distinction as storing the nodes **OR** storing the edges.\n\n\n\n然后，如果我们有机器，并且我们有一组消息，就可以再次滚动它以获得状态。**或者**，如果我们记录了状态，我们总是可以根据一系列状态的转换来重现action，尽管我们不一定知道哪些消息导致了这一状态转换。 如果你喜欢图形学，你可以想一下以节点存储**和**以边存储的区别。\n\n\n\nWe have a choice about how we think about things. And, depending on our desires and assumptions, we are likely to prefer one way or the other: databases are seen as machines of state, as is a light switch - it knows whether it is on or off, but doesn’t know how it got to where it is now. Whereas protocols are typically thought of more as machines of messages; consider an email exchange in which the last message doesn’t tell you all the story, and if it’s been a while you might have to scan all the previous messages in thread to work out what’s happening.\n\n\n\n我们可以选择如何思考问题。 而且，根据我们的愿望和假设，可能会更喜欢这样或那样的方式：数据库被视为状态机器，就像灯开关一样 - 它知道它是打开还是关闭，但不知道它是怎样到了现在的位置。 而协议通常被认为更像是消息机器; 考虑一个电子邮件交换，其中最后一条消息没有告诉你所有的故事，如果它已经持续了一段时间，你可能必须扫描线程中的所有之前的消息来弄清楚发生了什么。\n\n*photo.png（编辑部：图又挂了）*\n\n\n\n## Wheretofore the machinery of blockchain?\n\n## 区块链的机器在哪里\n\nThat’s in theory - practice can be different. Your online bank account is presented as a machine of state, with balance being told to you. But inside the bank, use of double entry accounting makes it more a machine of messages.\n\n\n\n这是理论上的 - 实践可能会有所不同。 你的网上银行帐户被看做是一台状态机，并告知你余额。 但在银行内部，使用双重输入运算使其更像是一种信息机器。\n\n\n\nWhat should blockchain do?\n\n\n\n区块链应该怎么做呢？\n\n\n\nFor reasons that might be historical, or maybe because it’s more typical for designers to think this way, blockchains are seen as machines of state, and not as machines of messages:\n\n\n\n由于可能是历史性的原因，或者因为设计师以这种方式思考更典型，因此区块链被视为状态机器，而不是消息机器：\n\n\n\n>… The goal of a blockchain is to represent a single state being concurrently edited. In order to avoid conflicts between concurrent edits, it represents the state as a ledger, that is as a series of transformations applied to an initial state. These transformations are the “blocks” of the blockchain, and — in the case of Bitcoin — the state is mostly the set of unspent outputs.\n\n\n>(my emphasis) LM Goodman, “Tezos: A Self-Amending Crypto-Ledger Position Paper(https://tezos.com/static/papers/position_paper.pdf)”, 2013\n\n\n\nOr, from a recent Ethereum replacement project:\n\n\n\n或者，来自一个最近的Ethereum项目：\n\n\n\n>How do transaction semantics fit into our description of contracts?  From the process level, a transaction is an acknowledgment that  a message has been“witnessed” at a channel.\nMessages themselves are virtual objects, but  the pre-state and post-state of a contract , referring to the states before and after a message is sent by one agent and witnessed by another,  are recorded and timestamped in storage , also known(in a moral sense) as the “blockchain”.\nMessage passing is an atomic operation. Either a message is witnessed, or it is not,and only the successful witnessing of a message qualifies as a verifiable transaction that can be included in a block.\n(author’s emphasis in  bold, my emphasis in  italics ) anon?, “RChain Architecture - Contract Design(https://rchain-architecture.readthedocs.io/en/latest/contracts/contract-design.html) ”, 2017 RChain Cooperative\n\n\n\nNote how the author above has established everything we need to store the message as transaction, and then fallen back to blockchain canon of state.\n\n\n\n请注意上面的作者如何建立将消息存储为交易所需的一切，然后再回到区块链状态。\n\n\n\nIf we look at the Bitcoin state machine in Figure 4 below for another example, we can see this state view writ large in the UTXO model, which groups  transactions as collections of  Unspent Transaction Outputs (“UTXO”). The transaction is a record of state that includes the input,  and the output. Comparing to Figure 3 above, think of both of the blue circles in each record, but none of the messages. Normally each UTXO transaction is represented as a box with a column of inputs on the left, and outputs on the right, Figure 4:\n\n\n\n 如果我们再看一下图4中的比特币状态机的另一个例子，我们可以看到这个状态视图在UTXO模型中特别强调，它将交易分组为Unspent Transaction Outputs（“UTXO”）的集合。 交易是包含输入和输出的状态记录。 与上面的图3相比，考虑每个记录中的两个蓝色圆圈，但没有消息。 通常，每个UTXO交易都表示为一个框，左侧是输入列，右侧是输出，图4：\n![ian消息媒介4.png](https://ipfs.busy.org/ipfs/QmWgHi8rHdtEd5pJtzW6a3xQeXCMYCQNGu7ZgWBWJWwd2s)\n\nOn the input (left) side of each transaction is a list of references to prior outputs or“coins”, by which presence they are then spent, and on the output (right) side is another matching list of new coins, by which presence they are now created and spendable in the future. Above, “Transaction 1” creates a 0.5BTC coin as an output, and “Transaction 2” spends the 0.5BTC coin by citing it as an input.\n\n\n\n在每个交易的输入（左）侧是先前交易的输出或“硬币”的引用列表，通过这样的方式，确认硬币存在，然后花掉它，并且在输出（右）侧是另一个匹配的新硬币列表，通过这种方式，确认它们现在已经被创造出来并在将来可以被消费。 在上面，“交易1”创建0.5个BTC作为输出，“交易2”通过引用它作为输入来花费0.5个BTC。\n\n\n\nThe Bitcoin transaction record, as a record of both inputs and outputs, is like a miniature balance sheet; the inputs match the outputs. For the visually minded,each of these transaction records is also like lego blocks in that new ones must plug onto old ones, and provide for newer ones to plug into them in the future.\n\n\n\n比特币交易记录，作为输入和输出的记录，就像一个微型资产负债表; 输入与输出匹配。 对于具有视觉意识的人来说，这些交易记录中的每一个都像乐高方块一样，新的必须覆盖旧的，并提供更新的以便在将来可以覆盖掉它们。\n\n\n\n## The Brittleness of the UTXO\n\n## UTXO的脆弱性\n\nNow, it has been observed before, but it is worth repeating: the Bitcoin design is of an extraordinary design, but one of its facets is that all of the components are strongly linked to each other in a very dependent way. As it says:\n\n\n\n现在，它之前已经被察觉到，但有必要复述一下：比特币具有非凡的设计，但其中一个方面是所有组件都以非常依赖的方式彼此紧密相连。 正如它所说：\n\n\n\n>“ A purely peer-to-peer version of electronic cash would allow online payments to be sent directly from one party to another without going through a financial institution. ”\nSatoshi Nakamoto, “Bitcoin: A Peer-to-Peer Electronic Cash System(https://bitcoin.org/bitcoin.pdf) ” 2008.\n\n\n\nThe mission was the money, but the money is also the driver for the security model, by means of paying miners to compete to validate. This powerful facet of intra-dependency does have one weakness - it is brittle in architectural terms. By this, I do not mean that Bitcoin is about to fall apart at any moment, but rather, if we change one design element, it threatens the sanctity of the entire architecture.\n\n\n\n任务是货币，但货币也是安全模型的驱动力，通过支付矿工竞争验证。 内部依赖的这个强大部分确实存在一个缺点 - 在架构方面它很脆弱。 通过这种方式，我并不是说比特币随时都会崩溃，而是如果我们改变一个设计元素，它就会威胁整个构造的神圣性。\n\n\n\nAnd so it is with the UTXO. As mentioned, the mission of Bitcoin was a money. Every(full) node needs to have each record of the money available for it, so it can validate every incoming transaction, and proceed to distribute the transactions into its proposed block for mining. In contrast, SPV or remote clients need to have an easy way of proving just their component of incoming coins, without dragging in the whole chain.\n\n\n\n这就是UTXO。 如上所述，比特币的使命是为一种货币。每个（全）节点都需要拥有可用资金的每一条记录，因此它可以验证每个传入的交易，并继续将交易分发到其适合的采集区块中。 相比之下，SPV或远程客户端需要有一种简单的方法来证明其输入的币的组成部分，以保证不会拖累整个链。\n\n\n\nThese two requirements are in conflict. Because there are a lot of records in a big chain like Bitcoin, the UTXO layout is an elegant design that meets both those requirements with a reasonable efficiency given its other impacts. It is very good at providing the proof that a client needs at a point in time.\n\n\n\n这两个请求是冲突的。 由于比特币这样的大型链中有很多记录，因此UTXO布局是一种优雅的设计，在其他影响的情况下以合理的效率满足这些要求。 它非常擅长提供客户在某个时间点需要的证据。\n\n\n\n## An Order Book\n\n## 订单薄\n\nBut what happens to the UTXO when the requirements change? Let’s say we want to do trading. For various reasons, the best way to do this is to bring everyone together, construct an order book - a list of bids to buy versus a list of offers to sell - and then run an auction clearing process to find the best price for all traders. There are other ways of course, but this is both the time-tested way and the way imposed by exchanges. \n\nFigure 5.\n\n\n\n但是当需求发生变化时，UTXO会发生什么？ 假设我们想做交易。 出于各种原因，最好的方法是将所有人聚集在一起，构建一个订单簿 – 要求购买的出价列表与要出售的标价列表 - 然后进行拍卖结算流程以找到所有交易者的最佳价格。 当然还有其他方式，但这既是经过时间考验的方式，也是加强交流的方式。 \n\n图5\n\n![ian消息媒介5.jpeg](https://ipfs.busy.org/ipfs/QmYmKNSe7zEuJn5PUHceAV3m9cvnMz9RoyyS7EjSUNNtv8)\n\nIn coming together in a UTXO state machine, an unknown number of people want to bid for positions on the buy side, as do an unknown number of people on the sell side. The UTXO design cannot easily facilitate this design for two reasons: 1. The interaction of many unknowns competing for one result does not scale because the entire layout needs to be negotiated on the fly - inputs, outputs and prices! – between the competing traders; and 2. trading is information sensitive - if there is a way to pull out of the negotiation and collapse it, traders will do that once they’ve spotted your position. This is a fundamental contradiction!\n\n\n\n在UTXO状态机中聚集在一起时，我们是不知道想要竞标买家的地位有多少，也不知道卖方的人数有多少。 UTXO设计过程中不能轻易地完成这种设想，原因有两个：1，竞争一个结果的许多未知因素的相互作用无法扩展，因为整个布局需要动态协商 - 输入、输出和价格！ - 在竞争交易者之间; \n\n2，交易是信息敏感的 - 交易者一旦发现你坐上买家的地位就会想办法退出谈判并使你崩溃。 这是一个根本的矛盾！\n\n\n\nA messaging flow can handle this conundrum easily. If the blockchain intermediator (the miner in a PoW design, or the producer in DPOS) receives a steady series of messages for bids and offers, he simply collects them up in order and hands them to the “book contract” which internally constructs the book, decides on the swap price,and sends new messages out confirming the contract’s outcome.\n\n\n\n消息流可以轻松处理这个难题。 如果区块链中间人（PoW设计中的矿工，或DPOS中的生产者）收到一系列稳定的出价和报价信息，他只需按顺序收集它们并将它们交给内部构建订单薄的“书面合约”，然后决定交换价格，并发出新的确认合约的消息结果。\n\n*Figure 6 - the Red Pill Trading Book of Messages.png（编辑部：图挂了again）*\n\n\n\nThe messages are logged, but the state (e.g., UTXO) is  implied , which means it is constructed by the computer internally, and then (can be) thrown away. As long as the blockchain has decided on the strict set of messages - both which messages and in what order - the result is deterministic because every other node runs the same contract for each set of the same input messages, and concurs on the output messages.\n\n\n\n消息被记录，但状态（例如，UTXO）是隐含的，这意味着它由计算机内部构建，然后（可以）被丢弃。 只要区块链决定了严格的消息集 - 消息和按什么顺序 - 结果是确定性的，因为每个其他节点为每组相同的输入消息运行相同的合约，并且同意输出消息。\n\n\n\nTwo more advantages: if any incoming trades are dropped in this block they can simply be deferred to the next block. That’s because the incoming messages are independent  intents to trade whenever, whereas the inputs and outputs making the UTXO state are more constrained to being parts of their dependent collection that should happen now, inside that very transaction.\n\n\n\n还有两个优点：如果在这个区块中丢弃了任何传入的交易，它们可以简单地被推迟到下一个区块。 这是因为传入的消息无论什么时候进行交易都是具有独立意图的，而构成UTXO状态的输入和输出更多地受制于它们的依赖集合的一部分，这些集合现在应该在该交易中发生。\n\n\n\nSecondly. This construct captures much more of the problem of the trading book.That is, when you want to trade with me, or I with you, we both write our bid/offer as a message and send it in. The hard part is done inside the contract, and the smart contract author has covered that in her design. In contrast, with the UTXO construct, it is you and I that have to lay out the blue box in Figure 5, agree on everything, sign off and then submit it for consensus. UTXO leaves the hard part to us the traders, and the easy part - logging the fact - to the chain.\n\n\n\n其次。 这个结构捕获了交易账户的更多问题。也就是说，当你想与我交易，或者我和你交易时，我们都将我们的买入/卖出作为信息写入并发送给它。困难的部分是在合约里面完成的。 完整的合约作者在他的设计中已经涵盖了这一点。 相比之下，使用UTXO构造，你和我必须在图5中展示蓝框，同意所有内容，签字然后提交以达成共识。 UTXO给交易员带来了困难的部分，而将简单的部分 - 记录事实 - 留给了链。\n\n\n\nAs an exercise, you might like to examine how you would handle fees in both designs.\n\n\n\n作为练习，你可能想要了解如何处理两种设计中的费用。\n\n\n\n## Slight Demurral\n\n## 小小异议\n\nIt’s not all one way - the state model has the benefit of trapping bugs more quickly.Every transaction has to be perfectly in agreement in its recorded state, not just the messages that got us there. This ability to trap errors quickly could be seen as a major advantage in reconciliation of trades, which the banking sector is looking at for cost and operational risk reduction.\n\n\n\n它并非都是单向的 - 状态模型具有更快地捕获错误的好处。每个交易必须在其记录状态下完全一致，而不仅仅是让我们在那里的消息。 这种快速捕获错误的能力可被视为交易对账的主要优势，银行业正在考虑降低成本和降低运营风险。\n\n\n\nBut even this could be a choice of risks - when a bug turns up in a blockchain, the chain quickly breaks and forks.\n\n\n\n但即使这样也可能是有风险的选择 - 当区块链中出现bug的时候，链会迅速断裂和分叉。\n\n\n\nEverything stops while nodes argue and hash. When a bug hits a message-model chain, the bug is implicit, and for the most part generates a dispute between parties over the meaning of the messages. Persons impacted can take it offline; including, we could develop the proofs to watch the issue offline, or exchain.\n\n\n\n当节点冲突和哈希时，一切都停止了。 当bug出现在消息模型链中时，该bug是隐含的，并且在很大程度上会在各方之间产生关于消息含义的争议。 受影响的人可以将其变为脱机状态; 包括，我们可以缓存证据来离线观看问题，或者交换。\n\n\n\n## Conclusion\n\n## 总结\n\nThe messaging model is for many reasons superior to the state model for the purpose of building broadly capable blockchains. It’s not all one way - the state model has the benefit of trapping breaks more quickly.\n\n\n\n为了构建功能广泛的区块链，消息传递模型有许多优于状态模型的原因。 这并不是一个单一的方式 - 状态模型有更快地捕获中断的好处。\n\n\n\nA fuller post would list all the pros and cons, but for now, we’ll just call out one major pro. Other than the ?exibility of the above example, messaging chains can reach much higher performance. For example, Bitshares and Steem by[@danthemamn](https://busy.org/@danthemamn) were all built on this model, and show 1000s of transactions per second. As was my Ricardo system, albeit non-blockchain, but it explains why it is so easy for me to like :-)\n\n\n\n一个更全面的帖子会列出所有的优点和缺点，但是现在，我们只会召集一个主要专业人士。 除了上述示例的灵活性之外，消息传递链可以达到更高的性能。 例如，@ danthemamn的Bitshares和Steem都是建立在这个模型上的，并且每秒显示1000次交易。 和我的Ricardo系统一样，虽然是非区块链，但它解释了为什么我这么喜欢:-)\n\n\n\nOn paper at least, this approach promises much higher performance, and you can possible see a hint that EOS will be built this way too! Indeed, it was the need for speed in those systems that led designer [@dantheman](https://busy.org/@danthemamn) and myself to the discovery that, with apologies to Marshall McLuhan,\n\n>the message is the medium.\n\n\n\n至少在理论上，这种方法可以提供更高的性能，你可以看到EOS也将以这种方式构建的暗示！ 事实上，正是这些系统的速度需要导致设计师@dantheman和我自己发现，向Marshall McLuhan道歉：\n\n>信息是一切中介。\n\n\n\n本文图片来源于英文原文 \n***\n版权声明：\n\n以下内容来自微信公共帐号“EOS技术爱好者”，搜索“EOSTechLover”即可订阅，翻译Gavin，校对Lochaiching。转载必须保留以上声明。仅授权原文转载。\n\n本文原文链接为https://busy.org/@iang/the-message-is-the-medium\n\n\"EOS技术爱好者\"全程由EOShenzhen运营，喜欢我们请为我们投票：（EOShenzhen的投票账号：eoshenzhenio）！ \n***\n\n**了解更多关于EOShenzhen：**\n\n[We are EOShenzhen](https://busy.org/@eoshenzhen/we-are-eoshenzhen-eos-bp-candidate)\n\n**不同入口如何投票：**\n[imToken](https://busy.org/@eoshenzhen/voting-through-imtoken)\n[火币](https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484391&idx=2&sn=8fa9e724a729ecd8bb8e7d2722c14add&chksm=fa0b82dbcd7c0bcd5266bf3cd179d90964b2879c361d26da7cf3e2790b4d87fc34878e57ec9c&scene=21#wechat_redirect)\n[portal](https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484354&idxx=1&sn=ddd4ffdae1531385a07fad59a6e86e6e&chksm=fa0b82fecd7c0be8328a0b3a1cff7de3bef207977ab0ca829c336fb450a7ef5c4153f32d5a4f&scene=21#wechat_redirect)\n\n**关于我们更多联系：**\nWebsite：https://eoshenzhen.io\n\nSteem：https://steemit.com/@eoshenzhen\n\nBusy：https://busy.org/@eoshenzhen\n\nTelegram：https://t.me/eoshenzhen\n\nTwitter：https://twitter.com/eostechlover\n\n简书：EOS技术爱好者\n\n新浪微博：EOSTechLover\n***\n**EOShenzhen的投票账号：eoshenzhenio**\n![100x100-IMG_7963_small.png](https://ipfs.busy.org/ipfs/QmTdwaSQTJR15zQcr6AQUi7Wgi9z51s97DcAfhNhhN9A6c)\n\n",
      "json_metadata": "{\"community\":\"busy\",\"app\":\"busy/2.5.6\",\"format\":\"markdown\",\"tags\":[\"eos\",\"message\",\"medium\"],\"users\":[\"danthemamn\",\"dantheman\",\"iang\",\"eoshenzhen\"],\"links\":[\"https://busy.org/exit?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FFinite-state_machine\",\"https://tezos.com/static/papers/position_paper.pdf\",\"https://rchain-architecture.readthedocs.io/en/latest/contracts/contract-design.html\",\"https://bitcoin.org/bitcoin.pdf\",\"https://busy.org/@danthemamn\",\"https://busy.org/@danthemamn\",\"/@dantheman\",\"https://busy.org/@iang/the-message-is-the-medium\",\"https://busy.org/@eoshenzhen/we-are-eoshenzhen-eos-bp-candidate\",\"https://busy.org/@eoshenzhen/voting-through-imtoken\"],\"image\":[\"https://ipfs.busy.org/ipfs/QmbXQCiNWPGGSWun8WB9A9ncshoGsW6DAY6V3jqGEyh5cM\",\"https://ipfs.busy.org/ipfs/QmTcJMyPC43TSUwjo94BLG7e4kLJ2P1mHit7vwqDmXWyM2\",\"https://ipfs.busy.org/ipfs/QmWgHi8rHdtEd5pJtzW6a3xQeXCMYCQNGu7ZgWBWJWwd2s\",\"https://ipfs.busy.org/ipfs/QmYmKNSe7zEuJn5PUHceAV3m9cvnMz9RoyyS7EjSUNNtv8\",\"https://ipfs.busy.org/ipfs/QmTdwaSQTJR15zQcr6AQUi7Wgi9z51s97DcAfhNhhN9A6c\"]}",
      "parent_author": "",
      "parent_permlink": "eos",
      "permlink": "v7yy2-or-ian",
      "title": "【翻译|Ian】信息是一切中介"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-17T04:17:27",
  "trx_id": "d5049e782f251b5b1b24fa24d7548634620dc2af",
  "trx_in_block": 9,
  "virtual_op": 0
}

{
  "block": 25924886,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "or-ian-dpos",
      "voter": "tsto",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-13T13:17:45",
  "trx_id": "ccafc39d8946eeffc39406760aa2f916a1fe0bdc",
  "trx_in_block": 9,
  "virtual_op": 0
}

{
  "block": 25862093,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "or-ian-dpos",
      "voter": "sensation",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-11T08:57:09",
  "trx_id": "781e246aef07a6a06a3c60cee964ccc6efe8cb34",
  "trx_in_block": 2,
  "virtual_op": 0
}

{
  "block": 25861870,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "or-ian-dpos",
      "voter": "moby-dick",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-11T08:46:00",
  "trx_id": "85b72d2aa53879d5b44a56e9cb28c9a871d0b5ff",
  "trx_in_block": 1,
  "virtual_op": 0
}

{
  "block": 25861075,
  "op": [
    "comment",
    {
      "author": "cheetah",
      "body": "Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in:\nhttps://steemit.com/eos/@iang/seeking-consensus-on-consensus-dpos-or-delegated-proof-of-stake-and-the-two-generals-problem",
      "json_metadata": "",
      "parent_author": "eoshenzhen",
      "parent_permlink": "or-ian-dpos",
      "permlink": "cheetah-re-eoshenzhenor-ian-dpos",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-11T08:06:15",
  "trx_id": "e1ba8fc3bf5d758fd9832c94bfc979a08098f1ab",
  "trx_in_block": 4,
  "virtual_op": 0
}

{
  "block": 25861073,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "or-ian-dpos",
      "voter": "cheetah",
      "weight": 8
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-11T08:06:09",
  "trx_id": "c48e4ca76351e3c9b9cc4d0f1153d942ffdca1c6",
  "trx_in_block": 14,
  "virtual_op": 0
}

{
  "block": 25861069,
  "op": [
    "comment",
    {
      "author": "eoshenzhen",
      "body": "# Seeking Consensus on Consensus - DPOS or Delegated Proof of Stake and the Two Generals' Problem\n\n\n\n# 在共识中寻求共识-DPOS(委任权益证明)和两军悖论\n\n\n\n作者：Ian Grigg\n\n翻译：Gavin\n\n校对：Lochaiching\n\n\n\nLaying down the rails for a high performance financial blockchain-based ecosystem is well understood if controversial because there are a number of approaches - centralised, decentralised, un-permissioned, walled garden.\n\n\n\n为一个高性能的金融区块链生态系统奠定基础肯定是备受争议，这很好理解。因为这里有很多方法——中心化的、去中心化的、未经许可的、封闭式。\n\n\n\nHaving chosen all that, we still have that one nagging itch of how to deal with race conditions. No matter the design, there’s always something you want to do and something someone else wants to do where these two things can’t both happen. Or, it’s cast in the sense that you want something to happen, and you want someone else to know this is going to happen too, known in the computer science worlds as Two Generals problem:\n\n\n\n除去以上提及的这些，我们仍然有一个关于如何应对竞态条件的烦恼。不管怎么设计，总有一些你想做的事情，还有一些其他人想做的事情，而这两件事不能同时兼得。或者，在某种意义上说你想要一些事情发生，并且你还想让别人知道这事情将要发生，在计算机科学领域中被称为[“两军悖论”](https://en.wikipedia.org/wiki/Two_Generals'_Problem#Definition)：\n\n\n```\nTwo armies, each led by a general, are preparing to attack a fortified city. The armies are encamped near the city, each in its own valley. A third valley separates the two hills, and the only way for the two generals to communicate is by sending messengers through the valley. Unfortunately, the valley is occupied by the city's defenders and there's a chance that any given messenger sent through the valley will be captured.\n\n\n“Positions of the armies. Armies A1 and A2 need to communicate but their messengers may be captured by army B.”\n\n\n\nWhile the two generals have agreed that they will attack, they haven't agreed upon a time for attack. It is required that the two generals have their armies attack the city at the same time in order to succeed, else the lone attacker army will die trying. They must thus communicate with each other to decide on a time to attack and to agree to attack at that time, and each general must know that the other general knows that they have agreed to the attack plan. Because acknowledgement of message receipt can be lost as easily as the original message, a potentially infinite series of messages is required to come to consensus.\n\n\n\nThe thought experiment involves considering how they might go about coming to consensus. In its simplest form one general is known to be the leader, decides on the time of attack, and must communicate this time to the other general. The problem is to come up with algorithms that the generals can use, including sending messages and processing received messages, that can allow them to correctly conclude:\n\n\n\n“Yes, we will both attack at the agreed-upon time.\n\nAllowing that it is quite simple for the generals to come to an agreement on the time to attack (i.e. one successful message with a successful acknowledgement), the subtlety of the Two Generals' Problem is in the impossibility of designing algorithms for the generals to use to safely agree to the above statement. (cite Wikipedia(https://en.wikipedia.org/wiki/Two_Generals'_Problem#Definition))”\n```\n\n```\n两名军队由分别由其将军领导，准备袭击一座要塞城市。 军队在城市附近扎营，每个都在自己的山谷中。 第三个山谷将两座山谷分开，两位将军交流的唯一途径就是派遣信使穿过山谷。 不幸的是，山谷被城市的防御者所占据，并且任何被送往山谷的信使都有可能会被捕获。\n\n\n\n军队的位置：军队A1和A2需要通信，但他们的信使可能被军队B抓获。\n\n\n\n虽然两位将军同意他们会进行攻击，但他们还没有就攻击时间达成一致。两位将军要是不能同时攻击城市，那剩下的另一支军队也会随之覆灭（即只有两支军队同时进攻才能获取胜利）。因此，他们必须与彼此交流以获得进攻时间上的共识，并且两位将军都必须知道对方明白双方已达成共识，原因在于确认收到对方消息的这一条信息也有同样的概率会丢失，这就导致：两人需要就一个潜在的无限条信息组成的信息流需要达成共识。\n\n\n这个思想实验包含：考虑他们该怎样达成共识。在这个最简单的形式之中，已知一个将军是领袖，决定进攻时间，并且必须将这个时间告知另外一位将军。现在问题在于我们需要一套算法能够让将军用来发送消息和处理已被收到的消息，并需要他们正确的涵盖以下内容：\n\n\n\n是的，我们将在已达成共识的时间发起进攻。\n\n\n要做到这一点是很容易的（即一个成功的消息和一个成功的确认）。两军悖论的微妙之处在于设计一套真正安全并能满足以上条件的系统是几乎不可能的（引自：[维基百科](https://en.wikipedia.org/wiki/Two_Generals'_Problem#Definition) )\n```\n\n\nAlso known as the coordination problem. In blockchains we call it the consensus problem. In the financial cryptography world, it’s the double spend problem, and in databases, atomicity. Which is to say this is a fundamental problem in all of computing science, and it’s not new just because, ya know, blockchain.\n\n\n\n在区块链中，我们称之为共识问题，也被称为协调问题。在金融密码学领域，被称为双重支付问题，在数据库中被称为原子性。也就是说，这是所有计算科学的一个基本问题，它并不新鲜。\n\n\n\nLet’s work through the evolution of this problem.\n\n\n让我们来研究一下这个问题的演变过程。\n\n\n\n## Centralised Double Spend Protection\n\n## 中心化双重支付保护\n\nThe original mechanism in financial cryptography is the simple client-server or trusted third party (like SOX), which is to say that the issuer of a double-spendable value like a coin runs a single server that mediates the double spends. Typically, the requests are queued up on a first in, first out (FIFO) basis, which is standard in databases these days.\n\n\n\n加密金融中的原始机制是一个简单的客户-服务器端或受信任的第三方（比如[SOX](http://www.systemics.com/docs/sox/overview.html)，译者注：一种支付系统），这就是说支持双重支付的价值发行方（译者注：这个发行方是一种货币）仅仅依靠一个服务器在双重支付中进行调解。十分典型的是，请求遵循先入先出（FIFO）排队方式，这在今天的数据库已经是标准了。\n\n \n## Blinded Cash\n\n## 盲现金\n\nOne notable variation of centralised double spend protection was the blinded signature over coins, invented by David Chaum in the late 1980s ([Chaum, Achieving Electronic Privacy](http://ganges.cs.tcd.ie/mepeirce/Project/Chaum/sciam.html)). The blinded coin was independently usable (verifiable) as a monetary token, but like all data, Alice could hand it to both Bob and Carol at the same time. The solution then was for Bob to push the coin back to the issuance server, known as a mint, and ask for a freshly signed one. Carol should do the same, and be faster!\n\n\n\n一个中心化双重支付保护的显著变种就是对货币的盲签名，这个概念由David Chaum于上世纪80年代末期发明。盲货币作为一种货币token可以单独被使用（可验证），但是就像所有的数据一样，Alice可以将其同时给Bob和Carol。对Bob而言，针对这种情况的解决方案就是将其收到的货币退还给发行的服务器，也就是印钞厂，并索要被重新签过名的另一份货币。同理，Carol也可以这么做，甚至以更快的速度。\n\n\n\n\n\n“盲签名”注释，校对者注\n\n\n\nNow, the special trick of the blinded signature on the token was that when pushed through a modified form of RSA, it could morph to create a new signature that the issuer had not created, but was still valid and therefore could identify a real coin to the issuer. Blinding therefore meant the issuer couldn’t track what Alice did with her coins, a very valuable thing! A further trick with eCash was that if Alice did try to spend the coin twice, the mint could use some crypto to combine both erstwhile spent coins, strip out the psuedonymous protection, and reveal who the naughty girl was.\n\n\n\n现在，盲签名在被用于Token上时存在一个特殊把戏：当Token完成一次被修改的RSA加密算法时，其能够创造一个之前未被使用过的全新签名，但这个签名却依然有效，因此这个货币依然是被承认的。因此，盲签名的“盲”字表示，货币的发行者不能追踪Alice用这些货币干了什么，这显然是十分有价值的！另一个关于电子现金的把戏是如果Alice确实尝试两次使用同一笔货币，造币方可以使用加密手段来将这两笔被消费的货币合并，去掉匿名保护，并揪出罪魁祸首。\n\n\n\n\n\n盲签名案例，校对者注\n\n\n\nI include mention of blinded double spending partly because it is an example of a very complicated scheme to catch double spending, and partly because it started our field of financial cryptography - invented back in the mid 1980s and built in the mid 1990s.\n\n\n\n我涉及了部分关于盲双倍支付的内容，因为这是一个非常复杂的用于管制双重支付的系统中的一个例子，也因为这是我们诞生于上世纪80-90年代的金融密码学领域的开端。\n\n\n\n## Voting\n\n## 投票\n\nReplicated servers became the in-thing typically for purposes of reliability. For example, the early NASA space shuttles had a voting ring of 3 primary IBM mainframes (and a couple of standbys). On every important act in a voting circle, a majority would win, and a minority could be disconnected and replaced. Early simple majority voting schemes proved to be a lot of trouble, and now the ruling buzzwords are Paxos and PBFT (practical byzantine fault tolerant), but do note that behind them there are lashings of Lamport, theory, bickering Byzantine Generals, PhDs, papers and Turing Prizes, oh my!\n\n\n\n多服务器的选择变得流行主要是为了追求可靠性。比如，早期NASA的航天飞机就有以三个IBM主框架形成的投票环（以及一些备用框架）。在每一个投票系统中，都是占大多数的获胜，其余的小部分会被断开连接，并被取代。早期的建议投票系统事实上被证明有许多不足，而现在在行业中流行的关键词是Paxos（一种基于消息传递且具有高度容错特性的一致性算法）和PBFT（practical byzantine fault tolerant，拜占庭容错），而且支撑着这些内容的是Lamport（Paxos提出者），以及大量理论，PhD，论文，图灵奖！总之就是各种复杂的东西。\n\n\n\nThese above variations on the theme suffer from some pretty serious limitations, chief of which are,\n\n- they are administratively centralised, and/or/therefore\n\n- all participants are known.\n\n\n\n以上提到的这些内容都有一些挺严重的局限性，主要有：\n\n- 从管理上来说他们是中心化的，和/或/因此\n\n- 所有的参与者都是已知的\n\n\n\nIn other words, the various Byzantine Generals Solutions assume that we know who the generals are, and famously that’s not usefully true in all cases.\n\n\n\n换句话说，拜占庭将军问题的解决方案中我们知道谁是将军的假设，在以上提到的这些情况中并不适用。\n\n\n\n## Proof of Work\n\n## 工作证明\n\nSatoshi observed that any centralised component can be attacked, and likely will be (Nakamoto, Bitcoin: A Peer-to-Peer Electronic Cash System). This observation was accurate : MTB shut its blinded eCash down due to unexpected adult shopping, DigiCash was hamstrung by authorities, WebMoney was hit by a reputation attack, e-gold was brought down by the Feds, as was LibertyReserve. DigiGold and e-Bullion failed due to founder actions. The list is exhausting, and your chastened author was closer to some of these disasters than was comfortable. You should do your own research to eliminate blame, forgetfulness and other biases.\n\n\n\n中本聪发现任何中心化的部件都能够被攻击，并会受到攻击（[Nakamoto, Bitcoin: A Peer-to-Peer Electronic Cash System](https://bitcoin.org/bitcoin.pdf)）。这个发现是准确的：MTB关停了eCash系统就是因为遭遇了意料之外的成人购物，DigiCash被政府当局干预致残，WebMoney遭到名誉上的攻击，e-gold和LibertyReserve被美联储扳倒。这个名单可以一直列下去，即使是作者本人也比预想中里这些灾难更近。你可以自己做一些调查来终结这些指责，以及其他一些偏见。\n\n\n\nThis was observed by several (see for example “The Mining Delusion”) but it was Bitcoin that presented a solution.\n\n\n\n觉察到这个缺陷的人不止一个(例如参见[\"The Mining Delusion\"](https://medium.com/@bergealex4/the-mining-delusion-96e021b6f899))，但是是比特币给出了解决方案。\n\n\n\nTherefore, Satoshi argued, we need to eliminate the centralised vulnerability party (CVP, also known as a trusted third party or TTP). And by deduction, as we can’t trust voting by known parties, we must all share and prove the same data, and we must accept and relish easy entry and exit - psuedonymity.\n\n\n\n因此，中本聪说，我们需要终结这种易受攻击的中心化机构（CVP，也称TTP）。并且，通过推测我们也知道并不能信任已知机构的投票系统，我们必须分享并验证这些数据是相同的，并且同时我们必须有容易接入的出入口，即匿名性。\n\n\n\nGreat stuff, but we still haven’t solved the double-spend problem, we’ve just moved it from a single place to a very much larger place :-(\n\n\n\n这个东西很棒，但是仍不能让我们解决双重支付问题，我们只是将数据从单个地方挪到了一个大的多的地方。\n\n\n\nThe elegant and famous solution to this was proof of work (POW) or the nakamoto signature - a lottery based on hash-puzzle over a correct block of transactions. The cryptographic nature of the hash lottery selects one single miner at random, who produces the block. Coupling the costly hash search called mining with a reward and adding in some complicated game theory and probability is all designed to keep the miners on the straight and narrow. See [comic](https://medium.com/@dbrgndl/smalltime-replacing-bitcoin-with-a-currency-free-distributed-transfer-system-21364b9cce1f).\n\n\n\n一个优雅且著名的解决方案是工作证明（PoW）或者中本签名，一个基于用哈希数学问题来确认正确区块交易的彩票系统。这个彩票系统的密码学的本质随机选择一个制造区块的矿机。将被称为挖矿的昂贵的哈希搜索和奖励耦合，并加上一些繁琐的博弈论和概率问题，所有这些元素都被用来将系统设计得能够驱使矿机不停工作。详情见[comic](https://medium.com/@dbrgndl/smalltime-replacing-bitcoin-with-a-currency-free-distributed-transfer-system-21364b9cce1f)。\n\n \n\nBitcoin is a brilliant and elegant solution because it opens our thinking to the possibility of fully distributed applications, with money. But PoW burns up energy to the value that the market can bear, which amounts to a horrible tax on the entire value of the currency (as of time of writing, 4% on Bitcoin, and 11% on Ethereum, big ouch!) and as the Bitcoin chain moves to a fee base this means fees will bite hard, lifting Bitcoin out of reach of most people. High rewards and the rising price also resulted in economies of scale for mining, resulting inevitably in the concentration of miners. Although the system itself happily carries on, a perverse consequence of the censorship-resistant design is that the power of censorship now rests in the hands of about a dozen businesses, with most in one country that is not famous for resisting the urge to censor.\n\n\n\n比特币是一个出色并且优雅的解决方案，因为它开阔了我们的思维，让我们想到了完全的去中心化式的应用（或货币）的可能性。但是PoW消耗了太多能量，多到市场无法承受，多到能够成为一项附着在货币上的吓人的税（比特币4%，以太坊11%！）。而随着使用比特币的费用越来越高，大多数人将无法使用它。高额回报和上升的价格同样也导致了大规模的挖矿，并不可避免的导致了矿机的中心化。虽然系统本身依旧毫无问题的运行，但这由能够抵御审查的设计方案完成的系统却落入了少数几个公司，而这几个公司几乎都坐落在一个以审查严格而闻名的国家。\n\n\n\n## Proof of Stake\n\n## 权益证明\n\nIt was observed by someone (?) that we could simply replace the voting-with-CPU with voting-with-value in order to choose who makes the decision on (the next block of) double-spends. After all, the blockchain precisely establishes who owns what currency, and those who have more skin in the game are more likely to preserve the system, so it is an aligned bias. If uncomfortable to the small player, and somewhat offensive to democratic principles.\n\n\n\n有人提出我们只需要将以CPU投票的模式改为以价值投票的模式来选择谁对（下个区块中）双重支付的问题做出决策。毕竟，区块链十分准确的建立在货币拥有的制度上，因此拥有更多货币的人更可能选择保护系统，因此这个偏向性是合理的。虽然可能让小额货币拥有者感到不适，也对民主制度有所冒犯。\n\n\n\nSo the theory goes. In practice, it has been criticised for (1) placing the power in the hands of those with most value, and also (2) for the “nothing at stake” problem which occurs when a bet on an alternate chain does not cost if it doesn’t survive.\n\n\n\n这个理论也因为一下原因受到批判：（1）将权力交给最多价值拥有者手中；（2）“无需抵押”问题（the “nothing at stake” problem）：因为不需要付出任何代价所以会不断试图分叉（译者注：而对于矿机来说最优的策略是尽可能多的挖矿（制造区块），因此不论矿机挖的区块所属于的区块链最终是否获胜成为正确的那一条链，都能获得交易费。）\n\n\n\nSimple proof of stake then does not seem to work. Let’s see what does work - let’s break down the problem.\n\n\n\n简单的权益证明似乎并不奏效，究竟什么系统才奏效呢？让我们将问题逐步分解。\n\n## Let’s go to a Mining Centralisation Conference\n\n## 让我们去进行一个挖矿中心化的会议\n\nWhen we look at Bitcoin’s current state of a dozen or so well-known mostly Chinese miners, it is clear that they are all known, to us and to each other, and they can and do communicate. When we get to mining pools the size of today’s country-warming rigs, Bitcoin’s assumption of psuedonymity for miners becomes tenuous - just follow the electricity. Or go to any bitcoin scaling conference.\n\n\n\n当我们观察到比特币矿工由中国垄断的现状时，很明显他们互相认识且能够相互沟通。而当面对今天大到能将国家变暖的挖矿规模情况下，我们知道比特币对矿工的匿名假设早已变得虚有其表了，因为我们只需要看电力消费或参与任意一个比特币会议就能知道到底是谁在挖矿。\n\n \n\nAnd they could collude. So far, they have not chosen to do so, or, at least not obviously. As that’s a situation that hasn’t proven reliable historically, maybe incentives & ethics can be bolstered?\n\n\n\n另一方面，他们可以相互勾结。至今他们并没有选择这么做，或者只是我们不知道。因为从历史上说这个情况还不能被证明是可靠的，也许动机与道德会被改进提高？\n\n\n\nOnly their incentives and their ethics keep the miners from colluding; it is the case that miners have returned the occasional fat-finger error, ones in which a trader has accidentally sent many BTC in fees instead of many satoshi, so ethics has some play here. On the other hand, some miners have mined empty blocks, even when the queue of delayed transactions or ‘mempool’ is exploding.\n\n\n\n只有他们的动机和道德能够让他们不相互勾结；在这种情况下矿工又回到了胖手指（fat-finger）失误的时候，有的交易者会意外的将一定数量的比特币而不是satoshi单位设为交易费，所以道德在这里确实起着一定的作用。另一方面，一些矿机会挖出空的区块，即使有成堆的被延迟的交易排成长队等待被处理。\n\n\n\nNot only is today’s miner concentration and cooperation unanticipated, the Bitcoin design was deliberately focussed on an alternate vision. Is miner integrity a sustainable future? Integrity is a cause that hasn’t proven reliable historically in for example banking, so maybe we should continue to bolster the incentives & ethics of blockchain?\n\n\n\n今天的矿机中心化不仅是意料之外的，也不符合比特币最初的设想。矿工的正直会是一个可持续的未来吗？从历史角度来讲，正直并未被证明是可靠的，想想银行就知道，所以我们真的应该继续支持依靠动机和道德来支撑的区块链吗？\n\n\n\nWhat if we work backwards and accept the fact that the miners can be concentrated? And that we know who they are? Or more controversially, miners should be concentrated and should be identified?\n\n\n\n如果我们退一步接受矿工中心化的事实呢？并且我们知道他们是谁？或者更进一步地假设，矿工应该中心化并通过身份验证？\n\n\n\nIf we accept miner concentration and miner identification, we could simply appoint them. But appointing the Asic Generals just brings us back to the original centralised vulnerability situation.\n\n\n\n如果我们接受矿工中心化和矿工身份验证，那就可以指定矿工。但是指定ASIC矿机，想过没有，这样的进程会将我们带回最开始的容易受攻击的中心化局面。\n\n\n\n## Delegated Proof of Stake - How to rule the Generals\n\n## DPOS-怎么管理将军\n\nHow then would we govern miners better? If we can appoint them, we can dismiss them as well, which brings us back to the Two Generals’ Problem.\n\n\n\n那么我们究竟该如何更好的管理矿工呢？如果我们可以选出他们，我们同样可以解雇他们，这就将我们带回了两军悖论.\n\n \n\nGiven a new set of requirements forced on us by reality and experience, it is plausible to re-design the double spend system. Delegated Proof of Stake is just such a redesign, by @dantheman, using a combination of the tools above:\n\n\n\n鉴于现实和经验强加给我们的新要求，重新设计双重支付系统是合理的。 委托证明是由[@dantheman](https://busy.org/@dantheman)重新设计的，使用以下工具：\n\n\n\n1.A Producer (nee miner) is selected as decision maker to prevent double spends in one block. See Figure 4. Each block produced is rewarded by new currency (no change here).\n\n\n\n1.一个生产者（nee miner）被选为决策者来避免一个区块中的双重支付，见图4，每次出块都能得到新的区块代币作为出块奖励；\n\n\n\n2.Many producers are selected and given a round-robin rotation for a round of blocks, thus creating a competitive market within the round, ensuring overall reliability, and resolving forks. See Figure 5.\n\n\n\n2.很多生产者被选择并被给予一个由一圈区块构成的罗宾环，从而在环内创造出一个存在竞争的市场，以保证可靠性并解决分叉，见图5；\n\n\n\n3.The chain runs an open community poll to manage the producers, in which each member may vote according to proof of stake. Producers are both selected and dismissed in the same way - an auction for the next round. See Figure 6.\n\n\n\n3.链上运行一个开放的社区通过投票来管理生产者，每个成员通过PoS原理进行投票。选择和解雇BP使用的是同一原理，即多轮拍卖式。见图6 。 \n\n\n\nThe community then is required to govern their chain by\n\n- checking and agreeing with the transactions they perform,\n\n- voting the producers in and out based on their record and other pronouncements (e.g,. the producers are free to offer incentives such as revenue splitting) and\n\n- maintaining their stake or suffrage to the needs they choose.\n\n\n\n然后社区需要通过以下行为来管理他们的链\n- 检查并同意他们执行的交易，\n- 根据他们的记录和其他声明（例如，生产者可以自由提供收入分配等激励措施）选出或者解雇生产者\n\n- 维持他们的股权或选举权，以满足他们的选择。\n\n \n\nNote that a more technical approach to attacks on DPOS can be found in DPOS Consensus Algorithm.\n\n\n\n请注意，在[DPOS共识算法](https://steemit.com/dpos/@dantheman/dpos-consensus-algorithm-this-missing-white-paper)中可以找到更具技术性的DPOS攻击方法。\n\n\n\n## A Political Economy?\n\n## 政治化经济学？\n\nIn consensus terms, DPOS is stake-delegation over proof - the producers provide the proof over the blocks, and the community uses its stake to delegate the producers.\n\n\n\n从共识的角度来说，DPoS是基于证据（proof）的代理权益（stake-delegation），即生产者向社区提供自己出块的证据，然后社区使用其权益来管理生产者。\n\n\n\nIn political terms, DPOS is similar to a two-layer representative democracy with landowner suffrage. Where,\n\n\n\n从政治的角度来说，DPoS与基于土地拥有者投票的两层代理民主制度（[two-layerrepresentative democracy](https://en.m.wikipedia.org/wiki/Representative_democracy) with [landowner suffrage](https://en.m.wikipedia.org/wiki/Suffrage#Wealth.2C_tax_class.2C_social_class)）较为相似。在这种制度中：\n\n\n\n- representatives are those producers that are delegated by the community to decide the day to day questions (over double spend), and\n\n- suffrage, or the right to vote on representatives, is given to those who hold a certain form of property. This property might be a savings unit which represents a commitment to the community, and also a loss of liquidity; it resembles the historical landowner suffrage popular before more universal forms, as recognition of the wealth and commerce that the merchant class brought to society.\n\n\n\n- 代表（representatives）即为那些由社区选举出的生产者，有生产者来处理那些日常的问题；\n\n- 对拥有某种形式财产的人给予选举权或选举权。 这个财产可能是一个储蓄单位，代表了对社区的承诺，也失去了流动性; 它类似于更普遍形式之前流行的历史土地所有者选举权，即对商人阶级为社会带来的财富和商业的承认。\n\n\n\nThe precise design of this mechanism - savings account, how many producers, how long a block, how long a round, what happens if?? - is obviously a deep and interesting question, and we’ll not go there today.\n\n\n\n这种机制的准确设计——存款帐号，有多少出块者，多久出一个块，多长时间能形成一个循环，以及众多其他元素，显然是更深层次也是更有趣的问题，今天就不做讨论了。\n\n\n\n## How does it Perform?\n\n## 它如何运作？\n\nThis mechanism has been shown to work in at least 2 large scale systems, Bitshares and Steem, and of course DPOS is to be used in EOS. It has also been chosen by Tezos, PeerPlays and Ark.io.\n\n\n\n这个机制一直被不少具有一定规模的系统使用，如Bitshare，Steem，EOS，Tezos，PeerPlays，Ark.io等等。\n\n\n\nWhile it is possible to criticise, so far the criticisms seem to be more at the level of flavour and comparison than weaknesses:\n\n\n\n虽然可以对其批判，但迄今为止评论似乎更频繁的讨论其特点以及与其他机制比较，而不是其弱点：\n\n\n\n1.Proof of stake is weak because of “nothing at stake” but this only matters when the stake is put to the direct question of a block. Delegation solves that - in DPOS the stake is put to the vote on the Producers, while the block is handled by a direct Producer round. Separation by delegation solves the “nothing at stake” problem.\n\n\n\n1.PoS因为“无需抵押（nothing at stake）”问题而变得脆弱，但只有当权益（stake）被用来直接参与区块建设的时候这个问题才会出现。而DPoS则解决了这个问题，因为在DPoS中对区块的处理被交给了生产者，这种责任的分离解决了“无需抵押问题”；\n\n\n\n1.There are possibilities for the producers to behave badly - they can censor transactions. But this is actually a flipped into benefit because badly behaved producers can also be voted out - that’s the point of delegation. Contrasting with Bitcoin’s current malpractice of the month of mining empty blocks, DPOS performs far better because it has a punishment mechanism.\n\n\n\n2.有几种生产者会出现恶意行为的可能——他们可能会对交易进行干涉。但这事实上可以被转换为好吃，因为不合格的生产者会通过投票被解雇，这就是DPoS的意义。与比特币现在制造空区块的非法行为相比，DPoS的表现要强得多，因为它有一个惩罚机制；\n\n\n\n3.There are possibilities to collude. Of course, collusion is also possible in other chains, as the above photo suggests. The question is really about which will perform better under collusion, and so far, our money’s on the organised governance because of punishment - skin in the game. The ad hoc or un-governed arrangement of pure PoW means that miners can’t be punished, even if they decide to mount their fabled 51% attack. In DPOS, once collusion is surfaced, it’s possible to adjust governance rules to deal with it be it at 51% or at 1%.\n\n\n\n3.勾结依然存在可能性。当然，勾结在其他区块链也存在可能性。重要的是哪一种机制在勾结存在的情况下运行的更好，至今为止这我们的钱都得到了妥善的管理，因为惩罚机制的存在。而在缺乏管理的纯PoW中，不管矿工做什么都不会受到惩罚，即使是51%攻击。在DPoS中，只要勾结被发现了，不管是1%还是51%我们都可以通过调整管理方式来对付。\n\n\n\n4.The purist bitcoiner will point out that by adding a governance layer, we’ve broken the trustless nature of the blockchain. Not so, as trustlessness rests on fallacies:\n\n\n\n4.纯粹的比特币使用者会指出，添加管理层打破了区块链的无信任本质。然而并非如此，因为关于无信任有以下谬误：\n\n\n\na.Fallacy that there is no governance layer in other chains. In practice there are governance layers, but they are unwritten, denied, and inconstant or abused. In essence, we are replacing ad hoc (anarchic? captured?) governance with written, constitutional, formal and transparent governance. The question is not whether this adds governance, but whether explicit governance is better than the hidden intrigue.\n\n\n\nb.Fallacy that the Bitcoin design means we don’t have to trust the miners. Consider the empty block syndrome again: we now have to trust the miners to produce decent blocks for the community, and they don’t, which exposes the gap between the mathematical nature of the blockchain and the human nature of ‘trust.’ The blockchain under PoW eliminates some trust but not all, and in this case, it destroys the possibility for the trust when it is needed.\n\n\n\na.其他区块链没有管理层的谬误。这并不正确，事实上是由管理层的，只不过没有被明写出来，被拒绝承认，以及不稳定。从本质上来说，我们使用有明确规章制度和透明的管理取代了专设的管理。问题不在于这么做是否加强了管理程度，而在一明确的管理是否比暗地里管理更好。\n\n\n\nb.比特币的设计然我们不需要信任矿工。在考虑一下空区块的问题：我们现在必须相信矿工会生产有效的区块，而事实并非如此，这就将区块链的数学上本质和“信任”的人性本质分离开来。PoW下的区块链终结了一部分信任，但并不是所有，而在这种情况下，当我们真正需要信任时，我们却无法再建立信任。\n\n\n\nDPOS comes with some advantages that are also worth stressing:\n\n\n\nDPOS还有一些值得被提及的优点:\n\n\n\n1.As it eliminates the hash mining, it is far cheaper than Proof of Work. In effect we are releasing the mining tax back to the community - as of writing 4% Bitcoin and 11% Ethereum.\n\n\n\n1.由于其废除了哈希挖矿，DPoS会比PoW便宜得多。而收益的会是社区，因为我们会将这部分税归还给社区（如前面写到的比特币4%，以太坊11%）。\n\n\n\n2.And we’re cleaning up the planet :-) DPOS is recommended for any blockchain with a heart ♡\n\n\n\n2.DPoS更加环保。DPOS推荐使用任务有环保之心的区块链。\n\n\n\n3.By adding a layer of formalised governance, we also set the scene for upgrades to the software. That is, users have a real mechanism to vote on a change, and producers have a real vote to follow. This mechanism pretty much makes the adversarial fork debate go away, and makes the chain fluid and dynamic - it can evolve quickly to suit evolving needs. I.e., the unsolved PoW nightmares of DAO and the blocksize debate are solved problems under DPOS.\n\n\n\n3.通过添加正式的管理层，我们也能够有计划的为软件进行升级。这意味着，用户将会有机会对系统的改变做出投票，生产者根据投票结果行动。这个机制几乎使恶意分叉成为不可能，并使区块链充满活力，由于它可以随着不断变化的需求而进化。比如：仍未解决的PoW中DAO（decentralizedautonomous organization，去中心化自治组织）的梦魇，以及关于区块大小的争论都是在DPoS中得到解决的问题。\n\n\n\n4.The formalised governance also works to give community the voice over their chain.\n\n\n\n4.正式的管理机制也给了社区对改进区块链提出建议的机会。\n\n\n\n5.DPOS works to channel the decision making into a high-performance and high-efficiency rig that allows truly massive throughput. Let’s leave performance to other posts, but it’s worth stating that Bitshares has tested at 1000X that which Bitcoin can achieve in its current form. That sort of performance creates a lot of headroom for forgiveness.\n\n\n\n5.DPoS致力于使做决策变得高效，从而使系统真正能被大规模使用。让我们把关于性能的讨论留给其他文章，但这里值得一提的是，测试中Bitshare实现了1000倍于当下比特币的性能。这样的性能让人能够容忍很多其他的瑕疵。\n\n\n\nBenefits are of course all sins to some, but they are the sorts of sins that businesses and individuals can forgive and treasure.\n\n\n\n这些优点当然也意味着存在尚未被发现的缺点，但他们会是企业和个人能够容忍的缺点。\n\n\n\n本文图片来源于英文原文 \n\n\n\n\n***\n版权声明：\n\n以下内容来自微信公共帐号“EOS技术爱好者”，搜索“EOSTechLover”即可订阅，翻译Gavin，校对Lochaiching。转载必须保留以上声明。仅授权原文转载。\n\n\n\n本文原文链接为https://busy.org/@iang/seeking-consensus-on-consensus-dpos-or-delegated-proof-of-stake-and-the-two-generals-problem\n\n\n\n\"EOS技术爱好者\"全程由EOShenzhen运营，喜欢我们请为我们投票：（EOShenzhen的投票账号：eoshenzhenio）！\n***\n\n**了解更多关于EOShenzhen：**\n\n[We are EOShenzhen](https://busy.org/@eoshenzhen/we-are-eoshenzhen-eos-bp-candidate)\n\n**不同入口如何投票：**\n[imToken](https://busy.org/@eoshenzhen/voting-through-imtoken)\n[火币](https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484391&idx=2&sn=8fa9e724a729ecd8bb8e7d2722c14add&chksm=fa0b82dbcd7c0bcd5266bf3cd179d90964b2879c361d26da7cf3e2790b4d87fc34878e57ec9c&scene=21#wechat_redirect)\n[portal](https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484354&idxx=1&sn=ddd4ffdae1531385a07fad59a6e86e6e&chksm=fa0b82fecd7c0be8328a0b3a1cff7de3bef207977ab0ca829c336fb450a7ef5c4153f32d5a4f&scene=21#wechat_redirect)\n\n**关于我们更多联系：**\nWebsite：https://eoshenzhen.io\n\nSteem：https://steemit.com/@eoshenzhen\n\nBusy：https://busy.org/@eoshenzhen\n\nTelegram：https://t.me/eoshenzhen\n\nTwitter：https://twitter.com/eostechlover\n\n简书：EOS技术爱好者\n\n新浪微博：EOSTechLover\n***\n**EOShenzhen的投票账号：eoshenzhenio**\n![100x100-IMG_7963_small.png](https://ipfs.busy.org/ipfs/QmTdwaSQTJR15zQcr6AQUi7Wgi9z51s97DcAfhNhhN9A6c)",
      "json_metadata": "{\"tags\":[\"pos\"],\"users\":[\"dantheman\"],\"image\":[\"https://ipfs.busy.org/ipfs/QmTdwaSQTJR15zQcr6AQUi7Wgi9z51s97DcAfhNhhN9A6c\"],\"links\":[\"https://en.wikipedia.org/wiki/Two_Generals'_Problem#Definition\",\"http://www.systemics.com/docs/sox/overview.html\",\"http://ganges.cs.tcd.ie/mepeirce/Project/Chaum/sciam.html\",\"https://bitcoin.org/bitcoin.pdf\",\"https://medium.com/@bergealex4/the-mining-delusion-96e021b6f899\",\"https://medium.com/@dbrgndl/smalltime-replacing-bitcoin-with-a-currency-free-distributed-transfer-system-21364b9cce1f\",\"https://busy.org/@dantheman\",\"https://steemit.com/dpos/@dantheman/dpos-consensus-algorithm-this-missing-white-paper\",\"https://en.m.wikipedia.org/wiki/Representative_democracy\",\"https://en.m.wikipedia.org/wiki/Suffrage#Wealth.2C_tax_class.2C_social_class\",\"https://busy.org/@iang/seeking-consensus-on-consensus-dpos-or-delegated-proof-of-stake-and-the-two-generals-problem\",\"https://busy.org/@eoshenzhen/we-are-eoshenzhen-eos-bp-candidate\",\"https://busy.org/@eoshenzhen/voting-through-imtoken\",\"https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484391&idx=2&sn=8fa9e724a729ecd8bb8e7d2722c14add&chksm=fa0b82dbcd7c0bcd5266bf3cd179d90964b2879c361d26da7cf3e2790b4d87fc34878e57ec9c&scene=21#wechat_redirect\",\"https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484354&idxx=1&sn=ddd4ffdae1531385a07fad59a6e86e6e&chksm=fa0b82fecd7c0be8328a0b3a1cff7de3bef207977ab0ca829c336fb450a7ef5c4153f32d5a4f&scene=21#wechat_redirect\",\"https://eoshenzhen.io\",\"https://steemit.com/@eoshenzhen\",\"https://busy.org/@eoshenzhen\",\"https://t.me/eoshenzhen\",\"https://twitter.com/eostechlover\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
      "parent_author": "",
      "parent_permlink": "pos",
      "permlink": "or-ian-dpos",
      "title": "【翻译|Ian】在共识中寻求共识-DPOS(委任权益证明)和两军悖论"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-11T08:05:57",
  "trx_id": "d5e0fa6ad22a1be556b537807ea07e342bae233d",
  "trx_in_block": 16,
  "virtual_op": 0
}

{
  "block": 25833846,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "or-dapp-tungsten-poc",
      "voter": "tsto",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-10T09:24:15",
  "trx_id": "a1aaabd3d1c058733719c7f3729870c6a9241a72",
  "trx_in_block": 24,
  "virtual_op": 0
}

{
  "block": 25832035,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "or-dapp-tungsten-poc",
      "voter": "sensation",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-10T07:53:42",
  "trx_id": "4ef8c92f6be43734d5f37e8d5bcd2f902a43e0be",
  "trx_in_block": 5,
  "virtual_op": 0
}

{
  "block": 25831109,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "or-dapp-tungsten-poc",
      "voter": "eoshenzhen",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-10T07:07:24",
  "trx_id": "657c536844604487c25b9afbb3225228f8aa251f",
  "trx_in_block": 27,
  "virtual_op": 0
}

{
  "block": 25831109,
  "op": [
    "comment",
    {
      "author": "eoshenzhen",
      "body": "# Introducing Proof-of-concept Tungsten for dApplication level Governance\n\n\n\n# 来介绍一下用于dApp层面治理的Tungsten（PoC）\n\n![1_5snIl-wnTRH46RIodXKgIw.jpeg](https://ipfs.busy.org/ipfs/QmVhEUyGR9p26KfKRXzH3QbWpRvB1xCFpYMLVcyuv1GzHB)\n```\nWhile decentralization is the ultimate goal for blockchain projects, in the current state of blockchain affairs it’s more of an end goal than a starting point. There are still a lot of issues that need to be ironed out in order for a governance system to work properly. When time is of the essence a system like arbitration doesn’t work, because when you wait too long the damage has already been done. The ultimate resolution of the governance system failures might take a lot of time and effort. Security should always be more important than governance, because it is the base of a good blockchain project and governance is a nice addition.\n\n\n\nThe three different actors in the EOS community, being the 21 block producers, arbitrators and token holders, should all agree on a satisfiable solution to the current governance issues in order to move forward and show the world what they are building/supporting.\n\n\n\n[Source](https://medium.com/@LindaCrypto/eos-governance-issues-explained-and-the-current-state-of-affairs-75d2847ee8b9)\n```\n\n\n\n```\n虽然去中心化是区块链项目的基本目标，但在目前区块链的情况下，它更像是一个最终目标而不是起点。要使治理系统正常工作，还有许多问题需要解决。当时间很重要时，像仲裁这样的制度就不起作用了，因为损失在你有时间处理之前已经造成了。治理系统故障的最终解决可能需要花费大量的时间和精力。安全应该总是比治理更重要，因为这是好的区块链项目必不可少的因素，治理则让它变得更完善。\n\n\n\nEOS社区三个不同的角色，即21个BP、仲裁者和token持有者，都应该就当前治理问题让可满足的解决方案达成一致，以便向世界展示整个社区正在构建/支持什么。\n\n\n\n[来源](https://medium.com/@LindaCrypto/eos-governance-issues-explained-and-the-current-state-of-affairs-75d2847ee8b9)\n```\n\n\nEOS is always termed as the governed block-chain which has its own constitution and an arbitration forum ECAF to enforce it. The idea of including an arbitration forum on the base layer was to establish trust between the individuals and businesses. The very first set of rulings by ECAF, raised many questions on forums power and subjective arbitration. Looking at the missing boundaries, Block One called for an end to all arbitration orders other than to render non-binding opinions on the intent of the code.\n\n\n\nEOS被认定为“受治理的区块链”，它有自己的公约（constitution）和一个仲裁论坛ECAF来执行治理方面的事务。在基层建立仲裁论坛的想法是在个人和企业之间这个层面来建立信任。ECAF的第一批裁决让一些论坛权力和主观仲裁的问题浮出水面。看看这时候缺失的边界，Block One选择呼吁终止所有仲裁命令，而不是对代码的意图提出不具约束力的意见。\n\n\n\nThe proposal intention was to shift the governance structure from the base layer to dApplication layer with clearly defined objectives. Also, it was proposed that block producers act as jury only in case of freezing or replacing a broken contract.\n\n\n\n这个提议的意图是将治理结构从基础层转移到具有明确目标的dApp层（即去中心化应用层）。此外有人建议，只有在冻结或更换违约合同的情况下，BP才有担任陪审团角色的资格。\n\n\n\nTo enforce the dApplication layer disputes outside the scope of “intent of code is law”, we at EOSMetal have developed a Proof of Concept of Bond based arbitration with defined boundaries (objective) and penalties. The bond could help make claimable promises to establish trust and gain visibility.\n\n\n为了执行超出了“代码是法律的意图”的范围之外dApp层面的纠纷，我们EOSMetal开发了一个定义边界(目标)和惩罚的基于仲裁的Bond（PoC阶段）。这样的Bond可以帮助可要求的承诺建立信任和获得知名度。\n\n\n\nDaniel Larimer envisioned base layer arbitration to be very different than what it is now. ECAF was just liable to give opinions not rulings, which may or may not be followed by Block Producers. The idea was to give no one the supreme powers.\n\n\n\nDaniel Larimer设想的基础层仲裁与现在的仲裁有很大的不同，ECAF只是负责发表意见，而不是裁决，这可能也不能确定是否是BP需要遵循的。这样的想法是不给任何人最高权力。\n\n\n\nTo place proper check and balances on the misuse of the power by Arbitration forums, the proceedings were ought to transparent, on-chain and open for judgment by the community. As it is unwise to share the details of the disputes looking at current scenarios, a layer of opaqueness adds to the actions of arbitrators which weakens checks and are subjected to get corrupt over time.\n\n\n\n对仲裁机构职权进行适当的制约和平衡，应当在社区公开、透明、在链上地进行仲裁。鉴于从当前的情况来看，公布纠纷的细节是不明智的，因此不透明的范围增加一层，就会让仲裁员的行动加深一步，这可能会导致检查的削弱，随着时间的推移整个局面会趋向于腐败。\n\n\n\n## Our arguments against Base layer arbitration\n\n1.Enforceability — Opinions rendered by Arbitrator are needed to analyze by Block producer. The judgments by Block Producers are mostly dependent on getting votes i.e they could be swayed in favor of large voters. If Base layer forums are binding and are enforceable, we feel that’s too much power in the hands of forums and check and balances become difficult.\n\n2.If the protocol layer has many arbitration forums, then BPs may find it difficult to enforce the awards i.e we may not want to freeze any accounts just because an arbitrator says so.\n\n3.We believe enforcement of any subjective claims should be enforced by third-party arbitrators and should not have any involvement of Block Producers unless disputes are related to fixing the code.\n\n4.Scalability — with many disputes arising, the community/ the Block Producers may find it difficult to have proper check and balances which might lead to corruption or abuse of power in long-term.\n\n5.Absence of well-defined Jurisdiction.\n\n\n\n## 我们不同意基础层面的仲裁\n\n1、可执行性——仲裁员提出的意见需要由BP们进行分析。而BP们有判断的权利主要是依赖于选票，即他们可能会倾向于持有大票仓的选民。如果基础层面的论坛是有约束力的，并且是可执行的，我们觉得这样的论坛权利过大，导致在审查和平衡之中变得进退两难。\n\n\n\n2、如果协议层有许多仲裁论坛，那么BP们可能会发现难以执行裁决，即我们可能不想冻结任何账户，但仅仅因为仲裁员说要这么做，我们就需要照办。\n\n\n\n3、我们认为，任何主观主张的执行都应由第三方仲裁员来执行，除非争议与规范的修订有关，否则不应涉及BP。\n\n\n\n4、可扩容性——由于存在许多争议，社区/BP们可能发现很难进行适当的审查和平衡，这可能导致长期的腐败或滥用权力。\n\n\n\n5、缺乏明确的权限管辖。\n\n\n\n## Bonds and dApp layer governance.\n\nUnlike base layer governance which tends to handle all the disputes and demands regular checks by the community, the dApplication layer governance works in parallel limiting the responsibilities of BPs to enforce.\n\nThe concept of Bond based governance and arbitration rulings limited to bonds is the brainchild of Daniel Larimer himself.\n\n\n\n## Bond和dApp应用层治理\n\n与底层治理不同，底层治理倾向于处理所有争议并要求社区实行定期审查，dApp应用层治理并行工作，限制BP们执行的职责。\n\n\n\n以Bond为基础的治理和仲裁裁决的概念仅限于Bond是Daniel Larimer自己的想法。\n![WechatIMG282.jpeg](https://ipfs.busy.org/ipfs/QmPgSgRorTU9Dy3nBY46pRC1mYcaSxDXCR85BBGk1TKTeh)\n\n## Importance of Promises in the Business\n\nCommitment, given by one party(the promisor) to another (the promisee) to carry out or refrain from carrying a specified act or acts. Promises, however, are legally binding only when they are made in the contract (voluntary, deliberate, and legally binding agreement between two or more parties).\n\n\n\n## 商业承诺的重要性\n\n一方(承诺人)向另一方(承诺人)承诺履行或不履行一项或多项特定行为。然而，承诺只有在合同(双方或多方自愿、慎重且具有法律约束力的协议)生效时才具有法律约束力。\n\n\n\n## What are Bonds?\n\nThe bonds are the collateral raised against a set of promises (clauses defined) bundled with the Ricardian contract which could be claimed in case of any disputes and are legally binding. The arbitrator powers are just limited to bonds.\n\n\n\n## 什么是Bond?\n\nBond是与李嘉图合同捆绑在一起的一系列承诺(定义的条款)的抵押品，在任何纠纷发生时都可以提出索赔，并且具有法律约束力。仲裁员的权力仅限于Bond所在的范围。\n\n\n\n## Proof of Concept: Tungsten\n\nWe at EOSMetal have developed a proof-of-concept: Tungsten based on bonds which could ease the shift of arbitration from Base layer to dApplication layer.\n\nUsing Tungsten any entity or individual could raise a bond with a set of claimable clauses (promises with defined penalties). A bond issuer could also choose any arbitration forums to handle the disputes (opt-in) and select the time frame of the bond.\n\nAlso, in case of any disputes, an individual could claim against the bond. He would need to specify the bond hash and claim value (penalty). A claimant will have to fill 10% of the claim amount as a bond which goes to the defendant in case the claimant loses the award.\n\nAn arbitrator could put the rulings on-chain using the Tungsten and if the ruling is in favor of the claimant, the smart contract transfers the funds to claimant.\n\nThe bond acts like escrow and could help with establishing trust within the community members. The contract shifts the dispute resolution away from any influence of Block Producers or any centralized entity. Also, it makes the awards by Arbitrator self-enforceable without the need of intervention from Block Producers.\n\n\n\n## Tungsten的PoC版本\n\n我们EOSMetal已经开发到了PoC阶段: 基于bond的Tungsten，可以让仲裁从基础层到应用层转移变得更容易。\n\n\n\n任何实体或个人使用Tungsten都可以用一套可申索的条款(有明确处罚范围的条例)来筹集资Bond。Bond发行方还可以选择任何仲裁论坛来处理纠纷(可选择加入)，并选择Bond的期限。\n\n\n\n此外，在发生任何纠纷时，个人可以对Bond提出索赔。他需要指定Bond哈希值和索赔值(罚款)。原告必须填妥申索金额的10%作为bond，以备原告败诉，bond将交予被告。\n\n\n\n仲裁员可以在链上用Tungsten进行裁决，如果最终裁决原告胜诉，智能合约就会把资金转移给原告。\n\n\n\n这种bond就像托管一样，可以帮助社区成员建立信任。该合同将纠纷解决从任何BP或任何中心化实体的干预中转移出来。此外，它使仲裁人能自动强制执行裁决，而不需要BP的干预。\n\n\n\n## The Road Ahead!\n\nTungsten is a small step towards the bigger goal of making EOS network dApplications trusted and secure for mainstream adoption with the flexibility of opting own set of rules.\n\n\n\n## 未来蓝图！\n\nTungsten是迈向更大目标的一小步，即通过选择真正需求的规则，使EOS网络中的dApp在主流应用中变得更加可信任和更安全。\n\n\n\n\n\n## Register Arbitrator.\n\nWe need to add a functionality for any individual to register as an arbitrator with an option of raising a bond himself.\n\nThis way any arbitrator who is willing to resolve disputes on EOS network could register and establish trust. We feel as the dApplications starts coming up on the network the need for individual arbitrators handling small disputes will increase.\n\n\n\n## 注册仲裁员\n\n我们需要添加一个功能，让任何个人都可以注册为仲裁员，并可以选择自己提高bond来增加可用度。\n\n\n\n通过这种方式，任何愿意在EOS网络上解决纠纷的仲裁员都可以注册并建立信任。我们认为，随着dApp在主网上出现得越来越多，处理小纠纷的单个仲裁员的需求将会增加。\n\n\n\n## Arbitration Forums\n\nAn arbitration forum or association is an organization that administers arbitration proceedings. These organizations are distinctly different from arbitrators because the forum does not actually arbitrate or write arbitral awards (essentially the rulings that are the result of arbitration). Their job is to maintain a set of rules for dispute resolution (RDR), maintain a database of qualified arbitrators to match-make with the needs of the claimants, assist in the administrative tasks from claim filing to close, and act as a hub of communication between the arbitrator and the claimants.\n\n\n\n[Source](https://medium.com/eos-new-york/free-market-dispute-resolution-on-eos-identifying-arbitrators-arbitration-forums-on-chain-via-663bd8ad9c56)\n\n\n\nAlong with allowing arbitrators to register, we are also working on the contract to help forums register themselves. EOS NewYork is working towards the {regarbitrator} and {regfourm} contracts, if possible, we could use the same contracts and allow the registered arbitrators or forums raise bonds themselves.\n\n\n\n## 仲裁论坛\n\n仲裁论坛（或社团）是管理仲裁程序的组织。这些组织与仲裁员明显不同，因为论坛实际上并不仲裁或撰写仲裁裁决(实质上是仲裁结果的裁决)。他们的工作是维护一套纠纷解决规则(RDR)，维护一个合格的仲裁员的数据库，以满足索赔人（即原告）的需求，协助完成从索赔申请到结束的行政工作，并充当仲裁员和原告之间的沟通桥梁。\n\n\n\n[来源](https://medium.com/eos-new-york/free-market-dispute-resolution-on-eos-identifying-arbitrators-arbitration-forums-on-chain-via-663bd8ad9c56)\n\n\n\n除了允许仲裁员注册外，我们还致力于帮助论坛注册自己的合约。 EOS NewYork正在致力于完善{regarbitrator} 和 {regfourm} 合约，如果可能的话，我们可以使用相同的合约，并允许仲裁员注册或论坛自行筹集bond。\n\n\n\n## Public Forums\n\nForums are important to have on-chain evidence by the claimant (if possible) and awards by Arbitrators. Forums could help with two majors functions-\n\nFiltering arbitrators based on awards and resolved disputes documents.\n\n2. Filtering claims, which could help with analysing the health of arbitration ecology and help with updating clauses for bonds.\n\n\n\n## 公开论坛\n\n论坛重要的是要有原告的链上证据(如果可能的话)和仲裁员的裁决。论坛可以帮助两个主要功能-\n\n1、根据裁决和纠纷解决文件对仲裁员进行筛选。\n\n2、过滤索赔要求，这有助于分析仲裁生态的健康，并有助于更新bond的条款。\n\n\n\n## Ricardian Contract Auditors/Smart Contract Auditors\n\nIf Bonds are widely used the majority of dApplication owners will look for security auditing of contracts before deploying them. Ricardian contract and Smart Contract will be needed to be then reviewed and rated by the Auditors.\n\nThe rating and reviews by trusted auditors will help with standardizing the bond dApplication accordingly.\n\nIt creates an opportunity for entrepreneurs to start auditing and rating firms for bonds.\n\n\n\nIf you are looking for starting an auditing firm, get in touch with us!\n\n\n\n## 李嘉图合约审计师/智能合约审计师\n\n如果bond被广泛使用，大多数dAppl所有者将在部署合约之前查找合约的安全审计。然后，审计人员需要对李嘉图合约和智能合约进行审查和评级。\n\n\n\n受信任的审计师的评级和审查将有助于相应dApp标准化的bond。\n\n\n\n它为企业家提供了一个审计和评级公司bond的机会。\n\n\n\n如果您正在寻找一家审计公司，请与我们联系!\n\n\n\n## Certification\n\nA criticism of opt-in kind of agreement argues that such an agreement, which is drafted unilaterally by the individual/ dApplication/entity while giving clear preference to the drafting party and includes uniform terms in an adhesion contract that are not subject to changes or negotiations, does not express, in most cases, the genuine consent of the signer. The click of consent (Ricardian contract — I agree) is often carried out without the contract being read in advance by the user. The bottom line is that the concern is that such consumer consent is likely to give rise to illusory consent or settlement.\n\nTo safeguard users to give illusory consent to the business owner we feel certificates (licenses) based on auditing of RC and Smart-Contract could help to distinguish the good bond dApplications from self-preference bonds dApplication.\n\nBlock Producers are very well known within the community and steward the community towards using the right set of tools. The idea behind introducing certificates/licenses is to help audited bonds and smart contracts with high visibility and more trust within community members using the tools endorsed by Block Producers.\n\n\n\n## 认证\n\n一些对可选协议的批评认为，这样一个协议，单方面起草了个人、dApp、实体而给起草方明显偏好和包括粘附的合同条款，在大多数情况下，签署者不受更改或谈判，不表达。点击同意(李嘉图合约 - 我同意)通常在用户没有提前阅读合约的情况下进行。最重要的是，人们担心的是，这种消费者同意很可能会导致双方不同意义上的同意或处理。\n\n\n\n为了保护用户对企业所有者的“同意”，我们认为基于李嘉图合约（RC）和智能合约的审计证书(执照)可以帮助区分良好dApp的bond和带有自我偏好dApp的bond。\n\n\n\nBP在社区内非常知名，并且以使用正确的工具管理社区。引入证书/许可证背后的想法是，通过使用BP认可的工具，帮助在社区成员辨识具有高可见性和更具信任的审计bond和智能合约。\n\n\n\n## Wallets / Browsers\n\nWe think moderation is a great tool used on the internet which helps to filter the websites. The Browsers/ wallets developed to filter secure dApplications based on bonds and certifications could make users less vulnerable to thefts and scams with no bonds and security.\n\n\n\nIn a world where protocol-level dispute resolution is limited to fixing bugs in the code, how does one protect against fraud and theft of keys? The answer is to opt-in to a banking Ricardian contract which controls the tokens on behalf of their owners. Transfers within the smart contract are subject to dispute resolution where the contract-appointed arbitrators have the power to reverse transactions and freeze tokens. Withdraws from the banking smart contract is subject to a 3-day delay after which they cannot be reversed.\n\n\n\n[Source](https://medium.com/@bytemaster/the-intent-of-code-is-law-c0e0cd318032)\n\n\n\n## 钱包/浏览器\n\n我们认为节制对于过滤互联网网站是一个非常棒的特质。为了过滤基于bond和证书的安全dApp而开发的浏览器/钱包可以让用户在没有两者（bond和安全）的情况下避免受到盗窃和欺诈的攻击。\n\n\n```\n在一个协议级别的纠纷解决仅限于修复代码里bug的世界中，如何防止密钥的欺诈和窃取？答案是选择加入一个银行化的李嘉图合约，它代表其所有者控制token。在智能合约中，如果合约指定的仲裁员有权撤销交易并冻结token，则该合约中的转移将受到纠纷解决的约束。从银行智能合约中撤回将会有3天的延迟，在此之后它们将不能被撤销。\n\n来源：[【翻译】“代码的意图”即法律]( https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484507&idx=1&sn=07205bc22bcaa78ca2706a6414a76ec7&chksm=fa0b8567cd7c0c71e0c991d5ab18e02fb8d7a4c25c51fb799770913f24167656f52136f9c167&scene=21#wechat_redirect)\n```\n\n\n## Block Producers and Bonds!\n\nInstead of having subjective disputes around the {regproducer} contract, we propose shifting the clauses to bonds and allow Block Producers to make promises. The community could vote for the Block Producers analyzing the claimable clauses driven by the free-market approach. In this way, the health of the network could be analyzed better and we could drive community towards better governance, with corruption removed from all the layers.\n\n\n```\nEOSMetal will be the first user of Tungsten and will deploy its own bonds which could be claimed by any user voting us. We hope many other Block Producers will join our initiative and raise similar bonds. The set of promises made by Block Producers governed by free market forces will provide the flexibility for stakeholders in terms of governance.\n```\n\n\n## BP和bond！\n\n我们建议将条款转换为bond，并允许BP做出承诺，而不是围绕 {regproducer} 合约产生主观争议。社区可以投票给分析由自由市场方式驱动的可索赔条款的BP。通过这种方式，可以更好地分析网络的健康状况，我们可以推动社区走向更好的治理，从各个层面减少腐败。\n\n\n```\nEOSMetal将是第一个使用 Tungsten的用户，并将部署自己的bond，任何投票给我们的用户都可以申请。我们希望其他BP也加入我们的行列，筹集类似的bond。由自由市场力量驱动的BP所作的一系列承诺将在治理方面为利益相关者提供更多的灵活性。\n```\n\n\n## Advisors\n\nWe are glad to have Cryptolions, EOSTitan and EOShenzhen as our advisers for this project.\n\n\n\n## 顾问\n\n我们很高兴有Cryptolions、EOSTitan和EOShenzhen作为这个项目的顾问。\n\n\n\n## Conclusion\n\nThe EOS community is still experimenting and looking at various options to create a robust governance structure which attracts the mainstream businesses or dApplication and promises individuals a secure infrastructure.\n\nWith many voices, opinions and missing implementation of dApp base layer arbitration the debate has been back and forth with no outcomes. With Tungsten, we hope to fill the void with the help of claimable collaterals.\n\nWe feel if the community reaches a consensus of taking right steps towards creating the secure infrastructure which filters the malicious contracts and provides visibility to trusted dApplication, we would just need lean governance on base layer.\n\n\n\n## 结论\n\nEOS社区仍在试验和研究可以让治理结构变得更加健壮的方法，以吸引主流商业或dApp，并向个体承诺完善这个主网基础安全的设施。\n\n\n\n在dApp基础层面的仲裁存在着很多声音、意见和执行不力的情况下，争论也一直没有结果。对于Tungsten，我们希望通过可申请抵押物来填补这一空白。\n\n\n\n我们的观点是，如果社区达成共识，采取正确的步骤来创建安全的基础设施，从而过滤恶意合约并为可信任的dApp提供可见性，那么我们只需要在基础层上进行高效的治理。\n\n\n\n## Resources\n\nWe invite you to join EOSMetal and discuss the implementation of bond based governance on telegram here: https://t.me/eosmetal\n\nTo view our initial implementation please visit Github here: https://github.com/EOSMetal/tungsten\n\n\n\n## 更多关于我们\n\n我们邀请您加入EOSMetal并在telegram上讨论基于bond的治理实现：https://t.me/eosmetal\n\n\n\n要查看我们的初始化实现版本，请访问Github: https://github.com/EOSMetal/tungsten\n\n\n\n本文图片来源于英文原文\n\n\n***\n版权声明：\n\n以下内容来自微信公共帐号“EOS技术爱好者”，搜索“EOSTechLover”即可订阅，翻译Lochaiching。转载必须保留以上声明。仅授权原文转载。\n\n\n\n本文原文链接为 https://medium.com/@EosMetal/introducing-proof-of-concept-tungsten-for-dapplication-level-governance-fea8b0a452e9\n\n\n\n\"EOS技术爱好者\"全程由EOShenzhen运营，喜欢我们请为我们投票，（EOShenzhen的投票账号：eoshenzhenio）！\n\n\n***\n\n**了解更多关于EOShenzhen：**\n\n[We are EOShenzhen](https://busy.org/@eoshenzhen/we-are-eoshenzhen-eos-bp-candidate)\n\n**不同入口如何投票：**\n[imToken](https://busy.org/@eoshenzhen/voting-through-imtoken)\n[火币](https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484391&idx=2&sn=8fa9e724a729ecd8bb8e7d2722c14add&chksm=fa0b82dbcd7c0bcd5266bf3cd179d90964b2879c361d26da7cf3e2790b4d87fc34878e57ec9c&scene=21#wechat_redirect)\n[portal](https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484354&idxx=1&sn=ddd4ffdae1531385a07fad59a6e86e6e&chksm=fa0b82fecd7c0be8328a0b3a1cff7de3bef207977ab0ca829c336fb450a7ef5c4153f32d5a4f&scene=21#wechat_redirect)\n\n**关于我们更多联系：**\nWebsite：https://eoshenzhen.io\n\nSteem：https://steemit.com/@eoshenzhen\n\nBusy：https://busy.org/@eoshenzhen\n\nTelegram：https://t.me/eoshenzhen\n\nTwitter：https://twitter.com/eostechlover\n\n简书：EOS技术爱好者\n\n新浪微博：EOSTechLover\n***\n**EOShenzhen的投票账号：eoshenzhenio**\n![100x100-IMG_7963_small.png](https://ipfs.busy.org/ipfs/QmTdwaSQTJR15zQcr6AQUi7Wgi9z51s97DcAfhNhhN9A6c)\n\n",
      "json_metadata": "{\"community\":\"busy\",\"app\":\"busy/2.5.6\",\"format\":\"markdown\",\"tags\":[\"poc\",\"governance\",\"app\",\"tungsten\"],\"users\":[\"LindaCrypto\",\"bytemaster\",\"EosMetal\",\"eoshenzhen\"],\"links\":[\"https://medium.com/eos-new-york/free-market-dispute-resolution-on-eos-identifying-arbitrators-arbitration-forums-on-chain-via-663bd8ad9c56\",\"https://medium.com/eos-new-york/free-market-dispute-resolution-on-eos-identifying-arbitrators-arbitration-forums-on-chain-via-663bd8ad9c56\",\"https://medium.com/@bytemaster/the-intent-of-code-is-law-c0e0cd318032\",\"https://t.me/eosmetal\",\"https://github.com/EOSMetal/tungsten\",\"https://t.me/eosmetal\",\"https://github.com/EOSMetal/tungsten\",\"https://medium.com/@EosMetal/introducing-proof-of-concept-tungsten-for-dapplication-level-governance-fea8b0a452e9\",\"https://busy.org/@eoshenzhen/we-are-eoshenzhen-eos-bp-candidate\",\"https://busy.org/@eoshenzhen/voting-through-imtoken\"],\"image\":[\"https://ipfs.busy.org/ipfs/QmVhEUyGR9p26KfKRXzH3QbWpRvB1xCFpYMLVcyuv1GzHB\",\"https://ipfs.busy.org/ipfs/QmPgSgRorTU9Dy3nBY46pRC1mYcaSxDXCR85BBGk1TKTeh\",\"https://ipfs.busy.org/ipfs/QmTdwaSQTJR15zQcr6AQUi7Wgi9z51s97DcAfhNhhN9A6c\"]}",
      "parent_author": "",
      "parent_permlink": "poc",
      "permlink": "or-dapp-tungsten-poc",
      "title": "【翻译|公告】用于dApp层面治理的Tungsten（PoC版本）"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-10T07:07:24",
  "trx_id": "657c536844604487c25b9afbb3225228f8aa251f",
  "trx_in_block": 27,
  "virtual_op": 0
}

{
  "block": 25829295,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "2ngort",
      "voter": "tsto",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-10T05:36:42",
  "trx_id": "998ea0652411577c0376320ba0d0f8342a302189",
  "trx_in_block": 9,
  "virtual_op": 0
}

{
  "block": 25828441,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "2ngort",
      "voter": "sensation",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-10T04:54:00",
  "trx_id": "ead1a9fe5128f2db0496810d6ea1cd2d5a3052e9",
  "trx_in_block": 3,
  "virtual_op": 0
}

{
  "block": 25828278,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "2ngort",
      "voter": "moby-dick",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-10T04:45:51",
  "trx_id": "437a5e2dbf6115ddd4cc31011f0f8bd2d87724a3",
  "trx_in_block": 4,
  "virtual_op": 0
}

{
  "block": 25826933,
  "op": [
    "comment",
    {
      "author": "cheetah",
      "body": "Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in:\nhttps://medium.com/@therealopenbazaar/the-case-for-dumb-contracts-6308aa5b757",
      "json_metadata": "",
      "parent_author": "eoshenzhen",
      "parent_permlink": "2ngort",
      "permlink": "cheetah-re-eoshenzhen2ngort",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-10T03:38:36",
  "trx_id": "040b9b5586e583f981889b91d7abd57a1fe57382",
  "trx_in_block": 36,
  "virtual_op": 0
}

{
  "block": 25826932,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "2ngort",
      "voter": "cheetah",
      "weight": 8
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-10T03:38:33",
  "trx_id": "927a4d791b1e609673226acb8708f57c5b256dd7",
  "trx_in_block": 0,
  "virtual_op": 0
}

{
  "block": 25826929,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "2ngort",
      "voter": "eoshenzhen",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-10T03:38:24",
  "trx_id": "e5a5a192c306aec3436c9816853be2a5823617b9",
  "trx_in_block": 20,
  "virtual_op": 0
}

{
  "block": 25826929,
  "op": [
    "comment",
    {
      "author": "eoshenzhen",
      "body": "# The Case for Dumb Contracts\n\n# 无效合约案例\n\n来源：OpenBazaar\n\n翻译：Gavin\n\n校对：Lochaiching \n\n\n```\nDisclaimer: This was written hours before the recent attack on TheDAO. The opinions in this article do not necessarily represent those held by other OpenBazaar developers.\n```\nWritten by Dr Washington Sanchez\n\n\n```\n免责声明：本文是在最近TheDAO被攻击之前几个小时写的。 本文中的观点不代表其他所有OpenBazaar开发人员持有的观点。\n```\n\n\n由Washington Sanchez博士撰写\n\n\n\n译者注：TheDAO：The DAO项目是区块链物联网公司Slock.it发起的一个众筹项目。原本该公司只想采用DAO（去中心化自治）来运作自己的系统Universal Sharing Network (USN)。后来发现这个机制也适合其他项目，因此决定创建The DAO，意为“DAO之母”。\n\n\n\n\n\nOpenBazaar receives a lot of feature requests and suggestions, which we welcome. One frequently asked question is whether we will migrate to a smart contract platform like Ethereum.\n\n\n\nOpenBazaar收到很多功能改进相关请求和建议，我们很欢迎和鼓励这么做。 其中经常被问到的一个问题是：我们是否会迁移到像以太坊那样的智能合约平台上。\n\n\n\n\n\nThere are a number of compelling reasons to move to Ethereum:\n\n1.Ethereum has a more professional and friendly development community compared to Bitcoin Core\n\n2.Ethereum has a larger transaction capacity, and their developers have a sensible attitude to scaling\n\n3.Ethereum is a smart contract platform that can initiate the transfer of funds based on external triggers\n\n\n\n这里有一些强有力的理由来让我们迁移到以太坊上：\n\n1.与比特币核心相比，以太坊拥有更专业和友好的开发社区\n2.以太坊拥有更大的交易能力，他们的开发人员对扩展有一种明智的态度\n3.以太坊是一个智能合约平台，可以根据外部触发器启动资金转移\n\n\n\n\n\nSimilarly, there are also reasons to move away from Bitcoin. The events of the ongoing block-size debate have signaled to us and other Bitcoin-related projects that the network may become prohibitively expensive in the near future.\n\n\n\n同样，也有理由让我们从比特币中迁移出来。 一直持续的关于区块大小限制的争论已向我们和其他与比特币相关的项目发出信号，表明该网络在不久的将来可能会变得非常昂贵。\n\n\n\n\n\nBitcoin Core appears to be committed to constraining the block size to drive up on-chain transaction fees and establish a ‘fee market’. Sadly, this will set Bitcoin on a course of pricing-out transactions, and ultimately people, from the blockchain (especially in the developing world).\n\n\n\n比特币核心似乎正在努力限制区块大小以提高链上交易费用并建立“收费市场”。 可悲的是，这将使比特币成为一种定价交易的过程，并最终吸引来区块链（特别是发展中国家）的人们。\n\n\n\n\n\nEven though we’re excited by the scaling capacity of the lightning network, the price of admission is fundamentally determined by on-chain transaction fees. Focusing on the lightning network at the expense of on-chain scaling is like upgrading to a 12-lane highway while ignoring the 1-lane onramp.\n\n\n\n尽管我们对闪电网络的扩展能力感到兴奋，但入场价格基本上取决于链上的交易费用。 以牺牲链上扩展性为代价专注于闪电网络，就像升级到12车道的高速公路而忽略单车道的匝道。\n\n\n\n\n\nConcerns such as these have prompted many of our colleagues to embrace Ethereum. But why haven’t we?\n\n\n\n诸如此类的一些担忧已经促使我们的许多同行接受了以太坊。 但为什么我们没有呢？\n\n\n\n\n\n1.Bitcoin. We believe that Bitcoin will become the dominant currency for global trade in the world. Short of a unfixable bug, or mass abandonment, we’re stubbornly devoted to Bitcoin.\n\n\n\n1.比特币。 我们相信比特币将成为全球贸易的主要货币。 只要没有碰到不可修复的漏洞或者大规模的放弃，我们还是执着地致力于比特币。\n\n\n\n\n\n2.Security. Bitcoin has existed for 7 years and survived multiple assassination attempts. The security of the network and incentives are firmly established and well-tested. Moving to a new blockchain with weaker security and brand new attack vectors is unwise and premature for OpenBazaar.\n\n\n\n2.安全。 比特币已经存在了7年，并在多次黑客攻击中幸存下来。 网络的安全性和激励措施已经非常牢固，并经过充分测试。 迁移到具有较弱安全性，并且容易成为黑客们新的攻击目标的新区块链，对于OpenBazaar来说是不明智和不成熟的。\n\n\n\n\n\n3.Network effects. The Bitcoin ecosystem is more mature and has maintained a defensible network effect.\n\n\n\n3.网络效应。 比特币生态系统更加成熟，并保持了可防御的网络效应。\n\n\n\n\n\nThese reasons are mostly focused on the currency and network aspects of Bitcoin. But what about smart contracts?\n\n\n\n这些原因主要集中在比特币的货币和网络方面。 那智能合约呢？\n\n\n\n\n\n## Ricardian Contracts\n\n## 李嘉图合约\n\nOpenBazaar uses Ian Grigg’s Ricardian contracts（http://iang.org/papers/ricardian_contract.html ；中文版：[李嘉图合约究竟讲了什么](https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247483996&idx=1&sn=d5bfe47c7b2c0d605a0277edadfdf705&chksm=fa0b8360cd7c0a7602314443cdf879198e9919ebad804b2f8f1f0b02207aa0627b48eebd93a9&scene=21#wechat_redirect)）. In a Ricardian contract, the trading parties are represented as cryptographic identities using public key cryptography. Digital signatures are considered as a proof of agreement. The cryptographic identities of the parties, along with the semantic terms and conditions of the contract, are digitally signed and verified by both parties. Valid signatures associated with the public keys quoted in the contract validate the contract.\n\n\n\nOpenBazaar使用Ian Grigg的李嘉图合约http://iang.org/papers/ricardian_contract.html ；中文版：[李嘉图合约究竟讲了什么](https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247483996&idx=1&sn=d5bfe47c7b2c0d605a0277edadfdf705&chksm=fa0b8360cd7c0a7602314443cdf879198e9919ebad804b2f8f1f0b02207aa0627b48eebd93a9&scene=21#wechat_redirect)）。 在李嘉图合约中，交易方使用公钥加密表示加密身份。 数字签名被视为协议证明。 双方的加密身份以及合约的语义条款和条件，都由双方来进行数字签名和验证。 用与合约中引用的公钥相关联的有效签名来验证合约的有效性。\n\n\n\n\n\nHowever, the contract itself is not self-enforcing. Nothing about the contract forces either party to abide by the terms and conditions they have agreed to. In many ways, Ricardian contracts are the cryptographic implementation of the title-transfer theory of contract, developed by Williamson Evers and Murray Rothbard.\n\n\n\n但是，合约本身并不是自我执行的。 合约的任何内容都不会强迫任何一方遵守他们同意的条款和条件。 在一定程度上，李嘉图合约是由Williamson Evers和Murray Rothbard开发的[合约所有权转移理论](https://en.wikipedia.org/wiki/Title-transfer_theory_of_contract)的加密实现。\n\n\n\n\n\n## Title Transfer Theory of Contract\n\n## 合约所有权转移理论\n\nThe theory states that all property has a title, or an assignment of ownership. Title can be transferred freely to another individual or exchanged for other property. In the exchange, the transfer of title is conditional upon the physical delivery of the good or service.\n\n\n\n该理论指出，所有财产都有所有权，和所有权转让权。 所有权可以自由地转让给另一个人，或者用来交换其他财产。 在交换中，所有权的转让取决于商品或服务的实际交付。\n\n\n\n\n\nFor example, Alice and Bob write a contract to exchange 10 chickens for 1 Bitcoin. Alice can give Bob 1 Bitcoin immediately, fulfilling her end of the contract, and retains the title to Bob’s 10 chickens. If Bob delivers the chickens, the contract is considered fulfilled with both the title and underlying property transferred to their new respective owners. If Bob fails to deliver the chickens, he has defrauded Alice of her property. The chickens rightfully belongs to Alice by virtue of the title that she holds after handing over 1 Bitcoin.\n\n\n\n例如，Alice和Bob写了一份合约，用1个比特币交换10只鸡。 Alice可以立即给Bob 1比特币，履行完她的合约，并持有了Bob的10只鸡的所有权。 如果Bob交付了鸡，则认为合约已经履行，所有权和相关财产都转移给了新的所有者。 如果Bob未能送鸡，他就欺骗了Alice的财产。 因为Alice在给与Bob 1比特币后，拥有了所有权，所以这只鸡属于Alice。\n\n\n\n\n\nAlthough the title-transfer theory of contract is an excellent framework we can use to resolve disputes and understand who justly deserves property, it is unenforceable. Ricardian contracts is simply a digital format to immutably record these title-transfer agreements using cryptographic identities.\n\n\n\n虽然合约所有权转移理论是一个非常好的框架，我们可以用它来解决争议，还能弄清楚谁应该得到财产，但它是无法执行的。 李嘉图合约只是一种数字化格式，可以用加密身份来不可变地记录这些所有权转让协议。\n\n\n\n\n\n## Smart Contracts\n\n## 智能合约\n\nEnter Nick Szabo with his proposal for “smart contracts”. Smart contracts simultaneously transfer both the title and good/service between transacting individuals. As a result, these contracts are said to be self-enforcing, in that valid contracts execute without human involvement. A simple example is a vending machine, which is programmatically designed to give you a candy bar after adding enough coins in the machine. A dumb contract, in comparison, would be equivalent to a customer handing over cash to a worker in a convenience store. The customer can try and steal the candy bar, or the worker can take the money and not hand-over the candy bar. Either case is a failure by one party to delivery property in exchange for title.\n\n\n\n说起Nick Szabo提出的“智能合约”提案。 智能合约在交易个人之间同步地转移所有权和商品/服务。 因此，这些合同被认为是自我执行的，因为有效合同在没有人为参与的情况下执行。 一个简单的例子是自动售货机，它以编程方式设计，向机器中投入足够的硬币后会为你提供一个糖果。 相比之下，无效合约相当于顾客将现金交给便利店的工作人员。 顾客可以试着偷走糖果，或者工作人员可以拿钱而不是交出糖果。 两种失败的情况都是因为一方未能交付财产来换取所有权导致的。\n\n\n\n\n\nSmart contracts irrevocably link the exchange of one party’s title and property with another. This is done so well that both title and property are essentially indistinguishable. Indeed, perhaps it is a matter of technological progress that title and property are considered separate entities.\n\n\n\n智能合约不可撤销地将一方的所有权和财产的交换与另一方的交换联系起来。 这样要是做得好的话，所有权和财产本质上都是难以区分。 实际上，所有权和财产被视为独立的实体也许是技术进步的原因。\n\n\n\n\n\nHowever, smart contracts can only be made for goods or services that are digitally controlled. For example, I can create a smart contract to lease a car that conditionally gives my driver’s smartphone the capacity to start the engine, provided I am making regular payments on the lease. This won’t work for my ’71 Ford Pinto.\n\n\n\n但是，智能合约只能用于数字化控制的商品或服务。 例如，我可以创建一个智能合约来租赁一辆汽车，有条件地给我司机的智能手机提供启动汽车引擎的能力，前提是我要定期支付租赁费用。 但这不适用于我71年的Ford Pinto。\n\n\n\n\n\nWhere a smart contract cannot be made directly for the item to be exchanged, the typical strategy employed is to find a proxy that mostly represents control of the underlying item. For example, I may have a refundable deposit that is tapped if a payment is missed.\n\n\n\n如果不能直接为要交换的项目制定智能合约，则采用的典型策略是找到可以代替项目的代理。 例如，如果错过付款，我可能会收到退还的押金。\n\n\n\n\n\nThe more the smart contract is disconnected from controlling the item being exchanged, the weaker the integrity of contract.\n\n\n\n智能合约与控制交换项目脱节越多，合约的完整性就越弱。\n\n\n\n\n\n## Smart Contracts in OpenBazaar\n\n## OpenBazaar中智能合约\n\nAside from some types of digital goods, the exchange of physical goods and most services cannot be safely represented in a smart contract. Alice may want to sell an ordinary chair to Bob, but Alice can’t cryptographically prevent Bob from physically sitting in the chair until payment is made, nor can Bob teleport the chair to his house upon payment.\n\n\n\n除了某些类型的数字商品之外，实物商品和大多数服务的交换都不能用智能合约来安全地表示。 Alice可能想把一把普通的椅子卖给Bob，但Alice不可能用密码学相关技术阻止Bob在付款之前坐在椅子上，Bob也不能在付款后将椅子传送到他家。\n\n\n\n\n\nThe analogue world is resistant to the true potential of smart contracts.\n\n虚拟世界抑制了智能合约的真正潜力。\n\n\n\n\n\nAs a result, people have turned to regulating other aspects of trade with smart contracts, such as shipping or dispute resolution.\n\n\n\n因此，人们开始将智能合约致力于贸易的其他方面，例如运输或解决纠纷。\n\n\n\n\n\nTransactions in OpenBazaar require both the Buyer and Vendor’s digital signature to release funds from a Bitcoin address. In the case of multisignature escrow, a third party called a ‘Moderator’ is used if there is some dispute in the execution of the contracts that the Buyer and Vendor cannot resolve. The Moderator has the tie-breaking vote to release funds to either party.\n\n\n\nOpenBazaar中的交易事务要求买方和卖方的数字签名，来从比特币地址上释放资金。 在多重签名托管的情况下，如果买方和卖方无法解决的合约执行时存在的争议，则使用称为“Moderator”的第三方。 Moderator通过打破平局的投票向任何一方发放资金。\n\n\n\n\n\nThese transactions are manually initiated, as in they require the user to be online and push a button. Without a doubt this is inefficient compared to smart contracts, which can trigger the release of funds based on data retrieved from an API call. The participants in the smart contract do not need a Moderator.\n\n\n\n这些交易是手动启动的，因为它们要求用户在线并按下按钮。 毫无疑问，与智能合约相比，这是低效的，智能合约可以根据从API调用中检索到的数据触发资金的释放。 智能合约中的参与者不需要Moderator。\n\n\n\n\n\nIn the case of ecommerce, for example, one may be tempted to write a smart contract to release funds from an address based on the shipping agent’s delivery of an item to the address requested by the Buyer. The tracking API would simple report that the item (represented by a unique tracking number) has arrived at its destination. The smart contract would read this input and release the funds to the Vendor. If the item was lost or returned to the Vendor, the smart contract could automatically refund the Buyer. If the API never reports delivery of the item to the destination address, the Buyer can be refunded after 30 days for example. No Moderator is necessary to facilitate the release of funds in these situations.\n\n\n\n例如，在电子商务的情况下，人们可能会试图根据运输代理商将物品交付到买方要求的地址来编写智能合约以从地址释放资金。 跟踪API会简单地报告项目（由唯一的跟踪号码表示）已到达目的地。 智能合约将读取此输入并将资金发放给卖方。 如果物品丢失或退回给卖方，智能合约可自动退还买方资金。 如果API从未报告将物品交付到目的地地址，则可以在30天后退还买方资金。 在这些情况下，不需要Moderator来监督资金的发放。\n\n\n\n\n\nHowever, a closer look reveals a number of obvious problems. The Vendor could ship a box of rocks to the Buyer. The API would still report that the item was successfully delivered to the requested address, triggering the release of funds. Even if the Buyer wants to initiate a dispute, the funds are unrecoverable. Does the shipping agent need to stay and witness the unboxing of the item to verify the content’s integrity? If so, then we have essentially returned to a dumb contract, requiring a human to manually trigger the release of funds.\n\n\n\n然而，仔细观察会发现许多明显的问题。 卖方可以向买方运送一箱石块。 API仍然会报告该项目已成功运输到请求的地址，从而触发资金的释放。 即使买方想要发起争议，资金也是无法收回的。 运输代理商是否需要留下并亲眼目睹物品的拆箱以验证完整性？ 如果是这样，那么我们基本上又回到了一个无效合同，要求人工手动触发资金的释放。\n\n\n\n\n\nAlternatively, depending on the value of the item, the Buyer could purchase another smart contract to DDoS the API source for enough time to trigger a refund transaction to the Buyer… essentially tricking the smart contract into thinking that the item was never delivered.\n\n\n\n或者，根据物品的价值，买方可以向DDoS购买另一个智能合约API接口，以便有足够的时间为买方触发退款交易...实际上是在欺骗智能合约，使其认为该物品从未交付过。\n\n\n\n\n\nThis is by no means an authoritative or general-purpose critique of smart contracts, or even smart contracts for ecommerce. Rather, it is to say that smart contracts are fantastic at facilitating automated and human-independent interactions. Once human interaction is required and factored into consideration, smart contracts become significantly more difficult to design with enough checks and balances to incentivize good behavior.The [DAO](http://hackingdistributed.com/2016/06/13/the-dao-can-turn-into-a-naturally-arising-ponzi/)is a cautionary tale to projects that want to capture complex human interaction in a smart contract.\n\n\n\n这绝不是对智能合约，甚至算不上电子商务智能合约的权威性或通用性批评。 更确切地说，智能合约在促进自动化和人类独立的交互方面非常出色。 一旦需要人工干预并将其考虑在内，并有足够的制衡来激励良好的行为，那样的话，智能合约就会变得更加难以设计，对于那些想要在智能合约中捕捉复杂的人际互动的项目来说，The [DAO](http://hackingdistributed.com/2016/06/13/the-dao-can-turn-into-a-naturally-arising-ponzi/)就是一个警示。\n\n\n\n\n\nTo be clear once more, we’re not anti-smart contracts or even projects like TheDAO. Many of us in OpenBazaar have been in the Bitcoin community since the beginning. We’ve seen the rise and fall of companies, projects and the next ‘killer app’. We’ve seen people repeatedly lose money chasing the shiny new thing. One of our highest values is protecting the integrity of user’s funds. If that means using dumber contracts that are less efficient because they requiring manual processing, so be it.\n\n\n\n再次声明，我们不是反对智能合同，更不是像TheDAO这样的项目。 OpenBazaar的许多人从一开始就在比特币社区中。 我们已经看过了公司，项目和下一个“Killer app”的兴衰。 我们看到人们因为反复追逐闪亮的新事物而亏损金钱。 我们的最高价值之一是保护用户资金的完整性。 如果这意味着需要使用需要手动处理从而效率较低的无效合同，那就这样做吧。\n\n\n\n\n\n## What About Scaling?\n\n## 关于扩展\n\nWe prefer to see on-chain scaling to the point where the volume of transactions (at ultra-low fees) is sufficient to cover the marginal costs of mining, in the absence of the block reward. This will also create a low admission price to the lightning network, making a high volume transaction network affordable and accessible to anyone in the world.\n\n\n\n在缺乏区块奖励的情况下，我们更倾向于将交易量扩展到（以超低费用）足以支付采矿的边际成本的程度。 这也将为闪电网络创造一个低入场价格，使世界上任何人都可以负担得起并使用大量交易网络。\n\n\n\n\n\nDespite the technical challenges associated with increasing the block size, the swift development of segregated witness demonstrate that innovative and complex changes can be implemented when there is sufficient will within the Bitcoin development community.\n\n\n\n尽管面对区块大小限制相关的技术挑战，但分离见证的迅速发展表明，当比特币开发社区有足够的意愿时，可以实施创新和复杂的变革。\n\n\n\n\n\nSpecial thanks to Brian Hoffman, Sam Patterson and Michael Folkson for their comments and corrections.\n\n\n\n特别感谢Brian Hoffman，Sam Patterson和Michael Folkson的评论和更正。\n\n***\n\n本文图片来源于网络\n\n版权声明：\n\n以下内容来自微信公共帐号“EOS技术爱好者”，搜索“EOSTechLover”即可订阅，翻译Gavin，校对Lochaiching。转载必须保留以上声明。仅授权原文转载。\n\n\n\n本文原文链接为https://medium.com/@therealopenbazaar/the-case-for-dumb-contracts-6308aa5b757\n\n\n\n\"EOS技术爱好者\"全程由EOShenzhen运营，\n\n喜欢我们请为我们投票\n\n（EOShenzhen的投票账号：eoshenzhenio）！\n\n***\n\n**了解更多关于EOShenzhen：**\n\n[We are EOShenzhen](https://busy.org/@eoshenzhen/we-are-eoshenzhen-eos-bp-candidate)\n\n**不同入口如何投票：**\n[imToken](https://busy.org/@eoshenzhen/voting-through-imtoken)\n[火币](https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484391&idx=2&sn=8fa9e724a729ecd8bb8e7d2722c14add&chksm=fa0b82dbcd7c0bcd5266bf3cd179d90964b2879c361d26da7cf3e2790b4d87fc34878e57ec9c&scene=21#wechat_redirect)\n[portal](https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484354&idxx=1&sn=ddd4ffdae1531385a07fad59a6e86e6e&chksm=fa0b82fecd7c0be8328a0b3a1cff7de3bef207977ab0ca829c336fb450a7ef5c4153f32d5a4f&scene=21#wechat_redirect)\n\n**关于我们更多联系：**\nWebsite：https://eoshenzhen.io\n\nSteem：https://steemit.com/@eoshenzhen\n\nBusy：https://busy.org/@eoshenzhen\n\nTelegram：https://t.me/eoshenzhen\n\nTwitter：https://twitter.com/eostechlover\n\n简书：EOS技术爱好者\n\n新浪微博：EOSTechLover\n***\n**EOShenzhen的投票账号：eoshenzhenio**\n![100x100-IMG_7963_small.png](https://ipfs.busy.org/ipfs/QmTdwaSQTJR15zQcr6AQUi7Wgi9z51s97DcAfhNhhN9A6c)\n\n",
      "json_metadata": "{\"community\":\"busy\",\"app\":\"busy/2.5.6\",\"format\":\"markdown\",\"tags\":[\"contract\",\"rc\",\"case\"],\"users\":[\"therealopenbazaar\",\"eoshenzhen\"],\"links\":[\"http://iang.org/papers/ricardian_contract.html\",\"https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247483996&idx=1&sn=d5bfe47c7b2c0d605a0277edadfdf705&chksm=fa0b8360cd7c0a7602314443cdf879198e9919ebad804b2f8f1f0b02207aa0627b48eebd93a9&scene=21#wechat_redirect\",\"http://iang.org/papers/ricardian_contract.html\",\"https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247483996&idx=1&sn=d5bfe47c7b2c0d605a0277edadfdf705&chksm=fa0b8360cd7c0a7602314443cdf879198e9919ebad804b2f8f1f0b02207aa0627b48eebd93a9&scene=21#wechat_redirect\",\"https://en.wikipedia.org/wiki/Title-transfer_theory_of_contract\",\"http://hackingdistributed.com/2016/06/13/the-dao-can-turn-into-a-naturally-arising-ponzi/\",\"http://hackingdistributed.com/2016/06/13/the-dao-can-turn-into-a-naturally-arising-ponzi/\",\"https://medium.com/@therealopenbazaar/the-case-for-dumb-contracts-6308aa5b757\",\"https://busy.org/@eoshenzhen/we-are-eoshenzhen-eos-bp-candidate\",\"https://busy.org/@eoshenzhen/voting-through-imtoken\"],\"image\":[\"https://ipfs.busy.org/ipfs/QmTdwaSQTJR15zQcr6AQUi7Wgi9z51s97DcAfhNhhN9A6c\"]}",
      "parent_author": "",
      "parent_permlink": "contract",
      "permlink": "2ngort",
      "title": "【翻译】无效合约案例"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-10T03:38:24",
  "trx_id": "e5a5a192c306aec3436c9816853be2a5823617b9",
  "trx_in_block": 20,
  "virtual_op": 0
}

{
  "block": 25656637,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "testing-announcement-kylinpoints-test-guide",
      "voter": "tsto",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-04T05:40:21",
  "trx_id": "98a8bf03bcf8abd914bcb657eccf19c5205f5231",
  "trx_in_block": 19,
  "virtual_op": 0
}

{
  "block": 25655048,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "testing-announcement-kylinpoints-test-guide",
      "voter": "rushmichaels",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-04T04:20:54",
  "trx_id": "86b872776168e83167172a284005ec154b897b35",
  "trx_in_block": 3,
  "virtual_op": 0
}

{
  "block": 25655004,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "testing-announcement-kylinpoints-test-guide",
      "voter": "eoshenzhen",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-04T04:18:42",
  "trx_id": "13178eb14aff7a5035e5a0b8987e0556f287a88a",
  "trx_in_block": 24,
  "virtual_op": 0
}

{
  "block": 25655004,
  "op": [
    "comment",
    {
      "author": "eoshenzhen",
      "body": "Glad to announce it——From now on，there are Points in Kylin Testnet（CryptoKylin Testnet，Website：https://www.cryptokylin.io/）！\n\nEOShenzhen has written a Bancor exchange model based KylinsPoints, and deployed on the KylinPoints account currently. Below is a guide to the test, which can be used on the CryptoKylin Testnet  for EOS token convert to KLP, and it can convert  reversely(Under the premise that the Connector contains EOS).\n\nWe plan to finish UI on the KylinPoints exchange and we welcome you to test it and give your valuable comments.\n\nHere's the full text of the test guide:\n***\n# Kylin_Bancor_Points Test Guide\n\n## Inspiration\n\nEOS Ram System\n\n>The project is currently in alpha version, and there may be a lot of problems.\n\n## Manual Test Guide\n## Introduction to KLP Bancor Token:\n\nAccount **kypsmintager**: used for minting token, deploying the klp.token smart contract\n\nAccount **kylinspoints**: used to transfer token, deploy the klp.connector smart contract\n\n- the testing account transfers to EOS to kylinspoints and returns KLP token\n\n- the testing account transfers KLP to kylinspoints and returns EOS token\n\n```\ncleos -u http://api-kylin.eoshenzhen.io:8890 kylinspoints klp.contracts/build/klp.token\n```\n\n## 1.1. Preparation\n\nhttp://faucet.cryptokylin.io/create_account?XXXX\n\nhttp://faucet.cryptokylin.io/get_token?XXXX\n\n\n## 2. Transfer EOS to kylinspoints account\n```\ncleos -u http://api-kylin.eoshenzhen.io:8890 push action kylinspoints transfer '[\"kylinspoints\", \"testsaccount\", \"1.234 EOS\", \"convert KLP\"]' -p kylinspoints\n```\n\n## 3. Transfer KLP to kylinspoints account\n```\ncleos -u http://api-kylin.eoshenzhen.io:8890 push action kylinspoints transfer '[\"testsaccount\", \"kylinspoints\", \"1000 KLP\", \"transfer KLP\"]' -p testsaccount\n```\n\n## Visual operation\n\n```\ncurl --request POST \\\n\n    --url http://api-kylin.eoshenzhen.io:8890/v1/chain/get_table_rows \\\n\n    --data\n\n'{\"code\":\"kylinspoints\",\"scope\":\"kylinspoints\",\"table\":\"klpmarket\", \"json\":\"true\"}'\n```\n\n## UI \n\n（ing...）\n\n[中文版指南地址](https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484901&idx=1&sn=7ab55ba05192810268055525c9c2386a&chksm=fa0b84d9cd7c0dcfc0a3ec194470457b38660c0e586b9a3bb2368a2283ce890c9b7dea341036&token=1650958697&lang=zh_CN#rd)\n\n***\n\n\n**了解更多关于EOShenzhen：**\n\n[We are EOShenzhen](https://busy.org/@eoshenzhen/we-are-eoshenzhen-eos-bp-candidate)\n\n**不同入口如何投票：**\n[imToken](https://busy.org/@eoshenzhen/voting-through-imtoken)\n[火币](https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484391&idx=2&sn=8fa9e724a729ecd8bb8e7d2722c14add&chksm=fa0b82dbcd7c0bcd5266bf3cd179d90964b2879c361d26da7cf3e2790b4d87fc34878e57ec9c&scene=21#wechat_redirect)\n[portal](https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484354&idxx=1&sn=ddd4ffdae1531385a07fad59a6e86e6e&chksm=fa0b82fecd7c0be8328a0b3a1cff7de3bef207977ab0ca829c336fb450a7ef5c4153f32d5a4f&scene=21#wechat_redirect)\n\n**关于我们更多联系：**\nWebsite：https://eoshenzhen.io\n\nSteem：https://steemit.com/@eoshenzhen\n\nBusy：https://busy.org/@eoshenzhen\n\nTelegram：https://t.me/eoshenzhen\n\nTwitter：https://twitter.com/eostechlover\n\n简书：EOS技术爱好者\n\n新浪微博：EOSTechLover\n***\n**EOShenzhen的投票账号：eoshenzhenio**\n![100x100-IMG_7963_small.png](https://ipfs.busy.org/ipfs/QmTdwaSQTJR15zQcr6AQUi7Wgi9z51s97DcAfhNhhN9A6c)\n\n",
      "json_metadata": "{\"community\":\"busy\",\"app\":\"busy/2.5.6\",\"format\":\"markdown\",\"tags\":[\"test\",\"kylinpoints\",\"kylin\",\"testnet\"],\"users\":[\"eoshenzhen\"],\"links\":[\"https://www.cryptokylin.io/）！\",\"http://faucet.cryptokylin.io/create_account?XXXX\",\"http://faucet.cryptokylin.io/get_token?XXXX\",\"https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484901&idx=1&sn=7ab55ba05192810268055525c9c2386a&chksm=fa0b84d9cd7c0dcfc0a3ec194470457b38660c0e586b9a3bb2368a2283ce890c9b7dea341036&token=1650958697&lang=zh_CN#rd\",\"https://busy.org/@eoshenzhen/we-are-eoshenzhen-eos-bp-candidate\",\"https://busy.org/@eoshenzhen/voting-through-imtoken\",\"https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484391&idx=2&sn=8fa9e724a729ecd8bb8e7d2722c14add&chksm=fa0b82dbcd7c0bcd5266bf3cd179d90964b2879c361d26da7cf3e2790b4d87fc34878e57ec9c&scene=21#wechat_redirect\",\"https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484354&idxx=1&sn=ddd4ffdae1531385a07fad59a6e86e6e&chksm=fa0b82fecd7c0be8328a0b3a1cff7de3bef207977ab0ca829c336fb450a7ef5c4153f32d5a4f&scene=21#wechat_redirect\",\"https://eoshenzhen.io\",\"https://steemit.com/@eoshenzhen\"],\"image\":[\"https://ipfs.busy.org/ipfs/QmTdwaSQTJR15zQcr6AQUi7Wgi9z51s97DcAfhNhhN9A6c\"]}",
      "parent_author": "",
      "parent_permlink": "test",
      "permlink": "testing-announcement-kylinpoints-test-guide",
      "title": "【Testing Announcement】KylinPoints test guide"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-04T04:18:42",
  "trx_id": "13178eb14aff7a5035e5a0b8987e0556f287a88a",
  "trx_in_block": 24,
  "virtual_op": 0
}

{
  "block": 25630396,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "3pbvsv-or-ian",
      "voter": "tsto",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-03T07:47:30",
  "trx_id": "9447f3f28f39db94269ee4c4e2e63c9aaf93f906",
  "trx_in_block": 21,
  "virtual_op": 0
}

{
  "block": 25629961,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "or-wps-wpf",
      "voter": "tsto",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-03T07:25:42",
  "trx_id": "e0903d06e280aa1f5b07040f05e27d9ba919a09a",
  "trx_in_block": 8,
  "virtual_op": 0
}

{
  "block": 25626957,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "3pbvsv-or-ian",
      "voter": "sensation",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-03T04:55:15",
  "trx_id": "62c071c6174f5c4dcfbf717026123cf3f90b44a9",
  "trx_in_block": 5,
  "virtual_op": 0
}

{
  "block": 25626752,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "3pbvsv-or-ian",
      "voter": "moby-dick",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-03T04:45:00",
  "trx_id": "471b873c6faba98068436dba8b4a8e32faf28b54",
  "trx_in_block": 9,
  "virtual_op": 0
}

{
  "block": 25625690,
  "op": [
    "comment",
    {
      "author": "cheetah",
      "body": "Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in:\nhttps://steemit.com/eos/@iang/towards-a-ricardian-constitution",
      "json_metadata": "",
      "parent_author": "eoshenzhen",
      "parent_permlink": "3pbvsv-or-ian",
      "permlink": "cheetah-re-eoshenzhen3pbvsv-or-ian",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-03T03:51:51",
  "trx_id": "7118b635406d8d80bf578a0fdd4d75dec5141016",
  "trx_in_block": 5,
  "virtual_op": 0
}

{
  "block": 25625688,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "3pbvsv-or-ian",
      "voter": "cheetah",
      "weight": 8
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-03T03:51:45",
  "trx_id": "69b9fe49be5d5980544bfe9b0dea4938f79aa15b",
  "trx_in_block": 32,
  "virtual_op": 0
}

{
  "block": 25625685,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "3pbvsv-or-ian",
      "voter": "eoshenzhen",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-03T03:51:36",
  "trx_id": "92f29b1d2f5d66bdb0d358860a1b1a3fe1a5420c",
  "trx_in_block": 21,
  "virtual_op": 0
}

{
  "block": 25625685,
  "op": [
    "comment",
    {
      "author": "eoshenzhen",
      "body": "版权声明：\n\n以下内容来自微信公共帐号“EOS技术爱好者”，搜索“EOSTechLover”即可订阅，翻译Gavin，校对Lochaiching。转载必须保留以上声明。仅授权原文转载。\n\n\n\n本文原文链接为https://busy.org/@iang/towards-a-ricardian-constitution ，由本号“EOS技术爱好者”翻译。\n\n\n\n\"EOS技术爱好者\"全程由EOShenzhen运营，喜欢我们请为我们投票（EOShenzhen的投票账号：eoshenzhenio）！\n***\n\n\n# Towards A Ricardian Constitution\n\n# 走进李嘉图合约\n\n\n\n*作者：Ian Grigg*\n\n*翻译：Gavin*\n\n*校对：Lochaiching*\n\n\n\n## Intro\n\n## 介绍\n\nThis is a thought experiment in several parts in what it would take to turn a blockchain Constitution like the EOS proposal into a full Ricardian Contract. Which isn’t as difficult as it sounds, and could lead to some surprising benefits.\n\n\n\n这是一个在几个方面进行的思想实验，目的是将一个区块链的合约，如EOS提案变成一份完整的李嘉图合同。这并不像听起来那么难，而且可能会带来一些意想不到的好处。\n\n\n\n\n\nFor the quick intro, a Ricardian contract(http://iang.org/papers/ricardian_contract.html) is a prose or legal contract that includes computer-parsable markup. In that order: it is first and foremost a human-readable document, and only secondly is it a machine readable document.\n\n\n\n先进行一下简单介绍，李嘉图合约（http://iang.org/papers/ricardian_contract.html ）是一种散文，或者说是一种包含计算机可标记标记的法律合约。按这顺序来看的话：它首先是一个人类可读的文档，其次是机器可读的文档。\n\n\n\n\n\nThe humans come first because they (we?) are the hard cases. For a contract to be a contract, there must be intent, which means the humans not only have to know about it, they have to understand it, so as to be able to legally enter into agreement in a manner that will be accepted by any (human-staffed) court as a legal contract. Establishing that exact intent is so important that we often turn it into a ceremony that is as well known to people as it is to courts - signing.\n\n\n\n人类是放在第一位考虑的，因为他们（我们？）是困难的那一部分。对于合约之所以可以称为合约，它必须有目的，这意味着人不仅要知道它,还必须完全理解它，以便能够以一种被所有（human-staffed）法院看做是一个合法的合约的方式来达成协议。建立这种确切的意图是非常重要的，以至于我们经常把它变成一个众所周知的仪式，就像法院签署一样。\n\n\n\n\n\nAll this human stuff turns out to be a very hard problem to do digitally (https://blogs.perficient.com/2015/03/03/21-cfr-part-11-decoded-electronic-signature-general-requirements-2/ ), whereas making a computer understand a document is easy - just shove some markup in there. Remember that ordering - humans first, computers second - as you’re reading through this odd construction.\n\n\n\n将所有这些人类的东西来实现数字化是一个非常困难的问题（https://blogs.perficient.com/2015/03/03/21-cfr-part-11-decoded-electronic-signature-general-requirements-2/ ），而让计算机理解文档却是很容易的——只要在其中插入一些标记就可以了。当你阅读这个不熟悉的合约时，记住这个排序——人类第一位，计算机第二位。\n\n\n\n\n\n## Part 1 - A Ricardian Layout\n\n## 李嘉图结构\n\nLet’s try it then! Let’s take a prose constitution, and shove some markup in it. By way of an example, here is a clause from an example version of a Constitution(https://steemit.com/eos/@dantheman/what-could-a-blockchain-constitution-look-like )that might or might not be useful for EOS:\n\n\n\n让我们尝试一下!我们来写一个散文公约（https://steemit.com/eos/@dantheman/what-could-a-blockchain-constitution-look-like ），并在其中加入一些标记。例如，这里有一个示例版本合约的一个条款，它可能对EOS有用，也可能没有用：\n\n\n```\nARTICLE 3 - Currency\nThe Community hereby creates a currency known as EXAMPLE, possession of which is evidence of a contribution to the community. The quantity of EXAMPLE shall increase no more than 5% per year after the first 1 billion EXAMPLE are distributed.\n```\n\n\n\n\nNote how the author of this clause ([@dantheman](https://steemit.com/eos/@dantheman/what-could-a-blockchain-constitution-look-like )) expects others to use this example, even to the extent of a hint to change EXAMPLE into MyCoin or YourCoin or BobCoin or somesuch. It’s a bit laborious but necessary to make this clause adaptable for different contexts - and this is where we get to the nub of the argument: we want to keep the precision of a proper contract, but we’d like the computer to do some of the editing & presentation work of taking the above template and turning it into a finalised contract for us, when we use it in the specific context of the blockchain.\n\n\n\n大家注意，本条款的作者（[@dantheman](https://steemit.com/eos/@dantheman/what-could-a-blockchain-constitution-look-like)）希望其他人使用这个示例，甚至在很大程度上暗示可以将EXAMPLE更改为MyCoin或YourCoin或BobCoin或类似的东西。这有点费力，但很有必要通过这么修改来使这一条款适用于不同的上下文——这就是我们的核心论点：我们希望保持一个合适的合约的准确性，但当我们想让它用于特定的区块链上下文中，又希望让计算机做一些编辑和演示工作，就需要使用上述的模板将其转换为我们的最终合同。\n\n\n\nAnd we want to enable the humans (and the computer) to easily interpret the results, as well.\n\n\n\n我们也想让人类（和计算机）都能很容易地解释结果。\n\n \n\n\n\n## Contract Cake\n\n## 合约蛋糕\n![ian走进合约1.png](https://ipfs.busy.org/ipfs/QmcidWZwyR7JUAueDU1j6PCeHFqn7McneS1BaBZ9ws1tKn)\n\nIn order to get our contract cake and eat it too, let’s add some markup and some parameters to those parts to that may be different from context to context. We already saw that the name of the coin is one such parameter, to which we can add the initial total issue amount, and the rate of inflation rate after the initial issue is done; all of these depend heavily on the context in which the contract is being issued:\n\n\n\n为了得到我们的合约蛋糕并吃掉它，让我们为那些改变上下文之后变得不同的部分添加一些标记和一些参数，我们已经看到，币的名称就是一个参数，我们可以加上初始的总发行数量，以及在初始发行完成后的增发率;所有这些都很大程度上取决于合约签发的环境：\n\n\n```\nArticle 3 - Currency\n\nCOINNAME = IangBux\nINFLATION = 5%\nINITIALISSUE = 1,000,000,000\n\nThe Community hereby creates a currency known as COINNAME, possession of which is evidence of a contribution to the community. The quantity of COINNAME shall increase no more than INFLATION per year after the first INITIALISSUE of COINNAME are distributed.\n```\n\n\n\n\nWith a graphical contracts editor, we can process the above dry document to display the prose contract derived from the above.\n\n\n\n使用图形合约编辑器，我们可以处理上述干文档以显示从上面得到的散文性质合约。 \n![ian走进合约2.png](https://ipfs.busy.org/ipfs/QmeuQFrc6zHFWxLFkKMJFxSsiGGdGjr4oMzDgdRW3m951o)\n\nYou can imagine a hover-over on those colour-highlighted parts that reveal the original name that has been substituted. Or, we could have a mode to track the variables by colours and highlighting, as within a programmer’s IDE (integrated development environment):\n\n\n\n你可以试着将鼠标悬停在那些已替换了原始名称的颜色高亮的部分上。 或者，我们可以使用一种模式来按颜色跟踪变量并突出显示，就像在程序员的IDE（集成开发环境）中一样：\n![ian走进合约3.png](https://ipfs.busy.org/ipfs/QmPf2JZD4ANuNhkuSJBezh8JgxW9NCGG3GKjBk6TsHUY1v)\n\nHours of fun!\n\n\n\n很欢乐的时光！\n\n\n\n\n\nNow, it’s important to realise something here. We don’t want too much fun. The reason for this is that those that have too much fun with graphics and tricks and toolkits and FLASH and popups and special offers and other abominations make it harder and harder for those who are the primary users of this system - the users. As Einstein put it, this system needs to be made as simple as possible, but no simpler!\n\n\n\n现在，重要的是要意识到一些东西。我们不想要太多的乐趣。这样做的原因是，那些对图形、技巧、工具包、FLASH、弹出窗口、特殊优惠和其他令人厌恶的东西有太多乐趣的人，会使那些个系统的主要使用者——用户们使用起来变得更加困难。就像爱因斯坦说的，这个系统应该做到尽可能简洁，但不简单！\n\n\n\n\n\n## Declare your variables, for the contract win!\n\n## 为了合约可以成功，请声明你的变量！\n\nIn the above, we have separated out the parameters from the prose. Interestingly, this is a winning idea in both legal writing and in computer coding. For the legal profession, this is known as contract templating(https://arxiv.org/abs/1608.00771), which allows one contract template to be used across many contracting parties - a great saving in legal fees. You can find more on templating over at Common Accord(https://CommonAccord.org).\n\n\n\n在上面，我们已经把这些参数从散文中分离出来了。有趣的是，这在法律编写和计算机编码中都是一个成功的想法。对于法律行业来说，这就是所谓的合约模板(https://arxiv.org/abs/1608.00771 )，它允许一个合约模板在许多缔约方之间被使用——这是法律费用的巨大节省。你可以在Common Accord (https://CommonAccord.org )上找到更多的模板。\n\n\n\n\n\nFor you coders, declaring your variables in advance forces the programmer to be clear and precise about what is intended. And allows the compiler to help you to follow that intent, e.g., by identifying that all parameters are correctly assigned. For both disciplines, it makes the product easier to read by other professionals, which makes it easier and cheaper to maintain.\n\n\n\n对于代码人员而言，事先声明变量会使其对所要做的事情保持清晰和准确的认识。并使得编译器来帮助你遵循该意图，例如，通过编辑器来确认所有的参数都已被正确地分配。对于这两个学科来说，它使产品更容易被其他专业人员阅读，这使得维护起来更容易，也更便宜。\n\n\n\n\n\n## A slightly more advanced Markup\n\n## 一种更加高级的标记\n\nThe above however is a little hard to code - what happens if we actually want to write in an acronym such as COINNAME or ARTICLE ? What happens when we want a bolded (upper case) warning about inflation, because,you know, central banks & lawyers!?\n\n\n\n然而，上面的代码有点难以实现——如果我们真的想用COINNAME或ARTICLE等首字母缩略词写一下会发生什么？ 当我们想要一个关于增发的粗体（大写）警告时会发生什么，因为你知道中央银行和律师！？\n\n\n\n\n\nFor this reason we would typically advise a simple markup within the prose. Here’s an example that uses a JSON-like format(https://en.wikipedia.org/wiki/JSON ) to set the parameters, and a hybrid to allocate the values.\n\n\n\n出于这个原因，我们通常会在散文中使用一个简单的标记。 这是一个使用类似JSON的格式 (https://en.wikipedia.org/wiki/JSON ) 来设置参数的示例，以及一个混合使用来用于分配值。\n\n\n```\nArticle 3 - Currency\n\n{\n“COINNAME”: “IangBux”,\n“INFLATION”: “5%”,\n“INITIALISSUE”: “1,000,000,000”\n“SYMBOL”: “$”\n“DECIMALS”: “2”\n}\n\nThe Community hereby creates a currency known as {COINNAME}, possession of which is evidence of a contribution to the community. The quantity of {COINNAME} shall increase no more than {INFLATION} per year after the first {INITIALISSUE} of {COINNAME} are distributed.\n```\n\n\nThat is the raw text, with some extra bits needed below. Now, your parser for this is quite simple:\n\n1.scan through and pull out all the JSON parts to set some internal variables. In short, JSON blocks are signalled by a curly braces, each opening and closing alone on a line alone, as normal.\n\n2.What is left is prose, which needs to be checked for pairs of curly braces, holding parameters to be substituted. Curly braces are safe in this context because a prose legal contract wouldn’t need to use them (I hope!) so they are available for simple parsing.\n\n3.Feel free to add some colour or mild formatting to accentuate the slightly smart activity that is going on.\n\n\n\n这是原始文本，下面需要一些额外的比特值。 现在你的解析器非常简单：\n\n1.扫描并取出所有的JSON部分来设置一些内部变量。简而言之，JSON区块是由一个花括号发出的，每个单独的打开和关闭都是正常的。\n\n2.剩下的是散文，需要检查成对的花括号，保持要替换参数。在这种情况下，花括号是安全的，因为散文法律合约不需要使用它们（我希望如此），因此它们可以用于简单的解析。\n\n3.请随意添加一些颜色或柔和的格式，以强调正在进行的轻微的智能活动。\n\n\n\n\n\nThis is simple, but not too simple like the earlier arrangements. JSON is good for parameters but lousy at readable text; prose is hopeless for parameters, but claims great readability.\n\n\n\n这很简单，但不像之前的预料那么简单。JSON对参数有好处，但可读性很差；散文对于参数来说是很不友好的，但是它的可读性很好。\n\n\n\n\n\n## As simple as possible, but no simpler\n\n## 尽可能简约，而不是简单\n\nMixing prose & params together in a hybrid creates a simple, computer-readable and human-readable contract that can now be varied and used in different contexts. Our primary goal is still intact - the contract remains no more difficult for a human to read than the original prose; any unreadability that is left over is probably due to the original text, but lawyers have to help us there with plain language contracts (please!).\n\n\n\n将散文和参数混合在一起，创造了一个简单的、计算机可读的和人类可读的合约，现在可以在不同的上下文中进行变化和使用。我们并没有违背我们的主要目标——合约对于人类来说，阅读起来并不比原始的散文更困难；剩下的任何不可读性可能都是由于原始文本造成的，但是不要忘记律师们会用简单的语言合约来帮助我们（请！）。\n![ian走进合约4.png](https://ipfs.busy.org/ipfs/QmaPSKv3PDYL8e7X8Neso67AxUwiNzzs23ys6KTKHSHrMf)\n\nWe could of course use any number of formats. I’ve used INI format in the past. You could use LaTeX or XML, but I won’t be so rude as to inflict those abominations on you in this post! The point here to remember is (a) the purpose of this is first, foremost and always to make the text readable by humans, especially those who don’t spend their life deep in code and technics, and (b) keep it as simple as possible, but no simpler ;-)\n\n\n\n我们当然可以使用任意数量的格式。 我过去使用过INI格式。 你可以使用LaTeX或XML，但我不会那么粗鲁，不能在这篇帖子中给你带来这些麻烦的东西！ 这里要记住的几点是：（a）这首先是最重要的目的是让人们可以阅读文本，特别是那些不会在代码和技术上花费很多精力的人，以及（b）尽可能的简约，但不简单;-)\n\n\n\n\n\nHaving laid down the basic idea of how, my next post will be a brief discussion on why getting the document nailed down matters in the hard-core digital transaction sense, before returning to the Constitution.\n\n\n\n在清晰了基本思路之后，我的下一篇文章将简要讨论为什么在得到反馈的架构之前，将文档固定在硬核数字交易具有重大意义。\n\n\n\n \n\nEnd notes: \n\nfor further reading, see the original paper Ricardian contract(http://iang.org/papers/ricardian_contract.html ). The Clack et al paper Smart Contract Templates: foundations, design landscape and research directions(https://arxiv.org/abs/1608.00771 ) presents current thinking. The most advanced thinking on a clause editor I have seen is at Common Accord(https://CommonAccord.org ). For smart contracts and objectification of blockchain contracts see The Sum of all Chains(http://financialcryptography.com/mt/archives/001556.html ) and in video(http://financialcryptography.com/mt/archives/001556.html ) but that takes us chasing Alice down the rabbithole. \n![ian走进合约5.png](https://ipfs.busy.org/ipfs/QmVpwxupgGq2fxLAmDmgGMLG2pUfuHYTFofC6NR5Q8GtcN)\n本文图片来源于英文原文\n\n***\n\n\n**了解更多关于EOShenzhen：**\n\n[We are EOShenzhen](https://busy.org/@eoshenzhen/we-are-eoshenzhen-eos-bp-candidate)\n\n**不同入口如何投票：**\n[imToken](https://busy.org/@eoshenzhen/voting-through-imtoken)\n[火币](https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484391&idx=2&sn=8fa9e724a729ecd8bb8e7d2722c14add&chksm=fa0b82dbcd7c0bcd5266bf3cd179d90964b2879c361d26da7cf3e2790b4d87fc34878e57ec9c&scene=21#wechat_redirect)\n[portal](https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484354&idx=1&sn=ddd4ffdae1531385a07fad59a6e86e6e&chksm=fa0b82fecd7c0be8328a0b3a1cff7de3bef207977ab0ca829c336fb450a7ef5c4153f32d5a4f&scene=21#wechat_redirect)\n\n**关于我们更多联系：**\nWebsite：https://eoshenzhen.io\n\nSteem：https://steemit.com/@eoshenzhen\n\nBusy：https://busy.org/@eoshenzhen\n\nTelegram：https://t.me/eoshenzhen\n\nTwitter：https://twitter.com/eostechlover\n\n简书：EOS技术爱好者\n\n新浪微博：EOSTechLover\n***\n**EOShenzhen的投票账号：eoshenzhenio**\n![100x100-IMG_7963_small.png](https://ipfs.busy.org/ipfs/QmTdwaSQTJR15zQcr6AQUi7Wgi9z51s97DcAfhNhhN9A6c)\n\n ",
      "json_metadata": "{\"community\":\"busy\",\"app\":\"busy/2.5.6\",\"format\":\"markdown\",\"tags\":[\"rc\",\"ricardian\",\"constitution\"],\"users\":[\"iang\",\"dantheman\",\"eoshenzhen\"],\"links\":[\"https://busy.org/@iang/towards-a-ricardian-constitution\",\"http://iang.org/papers/ricardian_contract.html\",\"http://iang.org/papers/ricardian_contract.html\",\"https://blogs.perficient.com/2015/03/03/21-cfr-part-11-decoded-electronic-signature-general-requirements-2/\",\"https://blogs.perficient.com/2015/03/03/21-cfr-part-11-decoded-electronic-signature-general-requirements-2/\",\"https://steemit.com/eos/@dantheman/what-could-a-blockchain-constitution-look-like\",\"https://steemit.com/eos/@dantheman/what-could-a-blockchain-constitution-look-like\",\"https://steemit.com/eos/@dantheman/what-could-a-blockchain-constitution-look-like\",\"https://steemit.com/eos/@dantheman/what-could-a-blockchain-constitution-look-like\",\"https://arxiv.org/abs/1608.00771\"],\"image\":[\"https://ipfs.busy.org/ipfs/QmcidWZwyR7JUAueDU1j6PCeHFqn7McneS1BaBZ9ws1tKn\",\"https://ipfs.busy.org/ipfs/QmeuQFrc6zHFWxLFkKMJFxSsiGGdGjr4oMzDgdRW3m951o\",\"https://ipfs.busy.org/ipfs/QmPf2JZD4ANuNhkuSJBezh8JgxW9NCGG3GKjBk6TsHUY1v\",\"https://ipfs.busy.org/ipfs/QmaPSKv3PDYL8e7X8Neso67AxUwiNzzs23ys6KTKHSHrMf\",\"https://ipfs.busy.org/ipfs/QmVpwxupgGq2fxLAmDmgGMLG2pUfuHYTFofC6NR5Q8GtcN\",\"https://ipfs.busy.org/ipfs/QmTdwaSQTJR15zQcr6AQUi7Wgi9z51s97DcAfhNhhN9A6c\"]}",
      "parent_author": "",
      "parent_permlink": "rc",
      "permlink": "3pbvsv-or-ian",
      "title": "【翻译|Ian】走进李嘉图合约"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-03T03:51:36",
  "trx_id": "92f29b1d2f5d66bdb0d358860a1b1a3fe1a5420c",
  "trx_in_block": 21,
  "virtual_op": 0
}

{
  "block": 25623206,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "or-wps-wpf",
      "voter": "ifttt",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-03T01:47:27",
  "trx_id": "ad7cdcae033bd0b3481483e72e3d3895173b5bb3",
  "trx_in_block": 32,
  "virtual_op": 0
}

{
  "block": 25621920,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "or-wps-wpf",
      "voter": "eoshenzhen",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-03T00:43:00",
  "trx_id": "e2e88fc1a1e0796300f4f7855cec1fc362fc8d82",
  "trx_in_block": 20,
  "virtual_op": 0
}

{
  "block": 25621920,
  "op": [
    "comment",
    {
      "author": "eoshenzhen",
      "body": "版权声明：\n\n以下内容来自微信公共帐号“EOS技术爱好者”，搜索“EOSTechLover”即可订阅，翻译Lochaiching。转载必须保留以上声明。仅授权原文转载。\n\n\n\n本文原文链接为https://drive.google.com/file/d/1pQRNf69WLA36NMVAFq8MS0AO4q5F0-AE/view\n\n\n\n\"EOS技术爱好者\"全程由EOShenzhen运营，喜欢我们请为我们投票（EOShenzhen的投票账号：eoshenzhenio）！\n***\n\n\n\n\n\n# WPS Development Request for Worker Proposal Funding \n\n# WPS申请WPF的发展资金\n\n\n\nDate: 2018-08-31 \n\nProject Lead: Jae Chung\n\n\n\n## Building the platform to fund innovation on EOS\n\n## 在EOS上建立创新资金平台\n\n\n\n### Proposal Summary\n\n● This proposal includes the following scope of work:\n\n○ Smart contracts for registration, submission, proposal review, and voting.\n\n○ Web platform for registration, submission, forum and voting.\n\n○ Software that incorporates the needs of new categories as they come online.\n\n○ Secure infrastructure to deploy the platform.\n\nThe funding asked for 6 months is $378,421\n\n\n\n### 提案摘要\n\n●该提案包括以下阐述的工作范围:\n\n○智能合约注册、提交、审查提案和投票\n\n○网页平台的注册、提交、论坛和投票。\n\n○软件，包含新类别功能上线时的需要。\n\n○平台部署安全基础设施\n\n○这次申请资金共计是378421美元（6个月）\n\n\n\n### Introduction\n\nOur mission is to support the growth of EOS Ecosystem by developing the WPS software, a platform for the community to review, discuss, select, fund, and hold accountable projects proposed by community members to benefit EOS.\n\nThe EOS WPS is a process which allows the community members to fund projects proposed by other community members for the good of the ecosystem. It is a critical piece of software which directly contributes to the success of the system and manages funding. However, it is quite complicated to design and implement a decentralized yet governable system that supports those who are willing to innovate for the community, while managing to prevent non-legitimate projects and frauds from stealing from the network.\n\nThe problems the community faces in deploying the WPS system:\n\n● How can EOS Community members share their ideas and request funding?\n\n● Once requested, how can the community intelligently discuss those proposals?\n\n● Once discussed, how will will they select which ones to fund?\n\n● Once funded, how will they track the projects to completion?\n\n● Once completed, how can the community evaluate it?\n\n● How do we make the WPS work?\n\nHow do we continuously implement new features based on community feedback?\n\n\n### 介绍\n\n我们的任务是通过开发WPS软件来完善EOS生态系统的发展。WPS软件是一个让社区成员为了让EOS社区变得更好而提出可以审查、讨论、选择、资助项目的平台。\n\n\n\nEOS WPS是一个为某些社区成员能为社区提出有利于生态系统的项目而申请相关资金的存在。它是一个举足轻重的软件，对整个系统的成功和资金的管理有直接作用。然而，设计和实现一个去中心化但可治理的系统是相当复杂的，它支持那些愿意为社区创新的人，同时想办法防止不合法的项目和欺诈从网络窃取到不法财富。\n\n\n\n社区在推行WPS系统时所面对的问题:\n\n- 如何让EOS社区成员更好地分享他们的想法和资金申请?\n\n- 一旦申请，社区如何明智地讨论这些提案?\n\n- 一旦讨论，他们会选择哪些资金申请?\n\n- 一旦资助，他们将如何跟踪项目保证项目完成?\n\n- 一旦完成，如何评价它对社区的价值?\n\n- 如何使WPS正常运转?\n\n- 如何基于社区的反馈不断迭代功能?\n\n\n\n### The Solution: The EOS WPS Software and Platform\n\nA native EOS dapp created for the EOS community, allowing the token holders to:\n\n● Propose projects to benefit the ecosystem\n\n● Review and discuss the proposals\n\n● Vote on proposals to be funded\n\n● Oversee funded projects status\n\n● Review the results later to understand the impact\n\nTrack all actions real-time on chain\n\n\n\n### 解决方案：EOS WPS软件和平台\n\n为EOS社区创建的本地EOS dapp，允许token持有者:\n\n●提出对生态系统受益的项目\n\n●评审和讨论提案\n\n●投票表达对提案的资助与否\n\n●监督受资助项目的运作状态\n\n●评审项目成果的影响\n\n●在链上实时跟踪所有action\n\n\n\n\n\n### Proposal Details\n\n**Phased Approach**\n\nPhase 0: Technology Foundation \n\nPhase 1: WPS Bootstrap System (Emergency Phase) \n\nPhase 2: WPS beta \n\nPhase 3: WPS v1.0 \n\nPhase 4: Ongoing maintenance\n\n\n\n### 提案的细节\n\n**分阶段实现**\n\n第0阶段：技术基础\n\n第1阶段：WPS引导系统(紧急阶段)\n\n第2阶段：WPS beta版本\n\n第3阶段：WPS 1.0版本\n\n第4阶段：持续维护\n\n\n\n#### Phase 0: Technology Foundation\n\nTimeline: Aug / Sept \n\nDeliverables: Initial Codebase for community peer review\n\n*Time volunteered by active community members ahead of funding to get the project moving\n\n\n\n#### 第0阶段：技术基础\n\n时间轴：8月/ 9月\n\n交付：社区同行评审的初始基础代码\n\n*具体时间由活跃的社区成员在资助项目之前自愿提供的时间段，再进行商议\n\n\n\n#### Phase 1: WPS Bootstrap System (Emergency Phase)\n\nTimeline: October / November \n\nDeliverables: A working, functional WPS platform, with limited functionality. Includes: Create Proposals, List Proposals, Review Proposals, Vote on Proposals, Fund Proposals \n\nCost: Budget breakdown in appendix\n\n\n\n#### 第一阶段：WPS引导系统(紧急阶段)\n\n时间轴：10月/ 11月\n\n交付：一个工作的、功能性的WPS平台（功能有限）\n\n包括：创建提案、列出提案、审查提案、投票表决提案、资金提案\n\n成本：附录在预算细目中\n\n\n\n#### Phase 2: WPS beta functionality\n\nTimeline: December / January \n\nDeliverables: Completed beta functionality, full infrastructure deployed. \n\nIncludes: Expanded review tools and on chain evaluation of proposals, expanded review on chain tracking of project progress, completed project metrics\n\nCost: Budget breakdown in appendix\n\n\n\n#### 第2阶段：WPS beta功能\n\n时间轴：12月/ 1月\n\n交付：已完成的beta功能，完整的基础设施部署。\n\n包括：扩展的评审工具和链上评估提案，项目进度链上跟踪的扩展评审，已完成的项目指标\n\n成本：附录在预算细目中\n\n\n\n#### Phase 3: WPS v1.0\n\nTimeline: March / April \n\nDeliverables: Polished UX and Security Audits \n\nIncludes: Following projects, discussion threads, navigation bar, project history, following friends, donations, separate categories, and features suggested by the community on forum discussions. \n\nCost: Budget breakdown in appendix\n\n\n\n#### 第3阶段：WPS 1.0 版本\n\n时间轴：3月/ 4月\n\n交付：优化的UX和安全审计\n\n包括：接下来的项目、讨论线程、导航栏、项目历史、关注者、捐赠事项、单独的类别，以及社区在论坛讨论上建议的功能。\n\n成本：附录在预算细目中\n\n\n\n#### Phase 4: Ongoing Maintenance\n\nTimeline: April+ \n\nDeliverables: Fix outstanding bugs, update code to match EOS.IO code updates, maintain servers, continue adding features based on community feedback. \n\nCost: Smaller ongoing costs, to be voted in separately by a worker proposal once the WPS has launched\n\n\n\n#### 第4阶段：持续维护\n\n时间轴：四月或四月后\n\n交付：修复明显的bug、更新代码以匹配EOS.IO代码更新\\维护服务器，基于社区反馈继续迭代\n\n成本：较小的持续成本，一旦WPS启动，将由WP单独表决\n\n\n\n### Our Team\n\nDevelopment:\n\nSungjae Chung (HKEOS) - https://www.linkedin.com/in/sungjaechung/ \n\n\n\nSyed Jafri (EOS Cafe Calgary) - https://www.linkedin.com/in/sjsyedjafri/ \n\n\n\nHugo Campanella (HKEOS) - https://www.linkedin.com/in/hugocampanella/ \n\n\n\nAdrian Hunter (Saltblock) - https://www.linkedin.com/in/adrian-michael-hunter/ \n\n\n\nBoram Kim (EOSeoul) - https://www.linkedin.com/in/boram-k-b2530669/ \n\n\n\nThomas Do (EOSeoul) - https://www.linkedin.com/in/thomas-do-01911516a \n\n\n\nAlfred Cheuk (HKEOS) - https://www.linkedin.com/in/alfredcheuk/ \n\n\n\nSheldon Huang (EOShenzhen) - https://github.com/sheldonhh \n\n\n\nAbbas Ali (Blockmatrix) - https://github.com/abbasali \n\n\n\nKedar Iyer (Libertyblock) - https://www.linkedin.com/in/kedar-iyer-47552649/ \n\n\n\nHarry Kim (EOSYS) - https://www.linkedin.com/in/jungyoon-kim-3658a2135/ \n\n\n\nSungmin Ma (EOSeoul) - https://www.linkedin.com/in/sungmin-ma-1a3a9b160/\n\n\n\nAdvisors:\nMichael Yeates (EOSDAC, advisor) \n\nEric Björk (EOS sw/eden, advisor) \n\nJohn Milburn (advisor)\n\n\n\n### 我们的团队\n\n开发者：\n\nSungjae Chung (HKEOS)、Syed Jafri (EOS Cafe Calgary)、Hugo Campanella (HKEOS)、Adrian Hunter (Saltblock)、Boram Kim (EOSeoul)、Thomas Do (EOSeoul)、Alfred Cheuk (HKEOS)、Sheldon Huang (EOShenzhen)、Abbas Ali (Blockmatrix)、Kedar Iyer (Libertyblock)、Harry Kim (EOSYS)、Sungmin Ma (EOSeoul)\n\n\n\n顾问：\n\nMichael Yeates (EOSDAC, 顾问) \n\nEric Björk (EOS sw/eden, 顾问) \n\nJohn Milburn (顾问)\n\n\n\n### Why Trust Us?\n\n● We are committed to the EOS Ecosystem, affiliated with 7 different standby block producers.*\n\n● We are familiar with EOS software, infrastructure, and deeply involved in the network technology. We have even submitted patches to the EOS.IO code itself, and some of our developers our responsible for managing the EOS-Mainnet repository.\n\n● We have a combined 50+ years of technology development experience.\n\n● We volunteered our time for the past 90 days to put together an initial foundation for the project which is available now for community code review.\n\n● Members of our team have created well-known community tools and projects, including:\n\n○ Bloks.io (block explorer)\n\n○ EOS Test Cave\n\n○ Eosnova.io (Wallet)\n\n\n\n\n### 为什么应该信任我们?\n\n●我们致力于EOS的生态系统，来自于7个不同的备用BP。*\n\n●我们熟悉EOS软件、基础设施、并深入参与网络技术。我们也向EOS.IO代码提交g补过丁。我们的一些开发人员负责管理EOS-Mainnet的存储库。\n\n●我们综合起来有超过50 年以上的技术开发经验。\n\n●我们作为志愿者在过去90天一起检查最初的基础项目的代码（即现在社区可用的代码）。\n\n●我们的团队成员开发过社区皆知的工具和项目，包括:\n\n○ Bloks.io (区块搜索器)\n\n○ EOS Test Cave\n\n○Eosnova.io(钱包)\n![WechatIMG257.jpeg](https://ipfs.busy.org/ipfs/QmPEEARUo2vrbVE5qbtbTyVt3dcsfDqnYY9ot3tXTGDsTA)\n*原型预览*\n\n\n\n### Our Development Process\n\n● We develop using Agile software methodologies so that we can adapt to changing requirements as we learn about WPS needs.\n\nOur development process will be broken down in bi-weekly development sprints during which we will continuously loop through the following phases; discover, design, code and test. This approach will allow us to quickly learn from previous sprints and iterate the platform regularly.\n\n● We commit to transparency to the EOS Community with bi-weekly updates, a public code repository, a public development backlog (Trello Board) and of course open sourcing the code itself.\n\n\n\n### 我们的开发过程\n\n- 我们使用 Agile软件开发方法，这样我们可以适应不断变化的WPS的需求。\n\n- 我们的开发过程将在两周一次的开发冲刺中被分配完成，在此期间我们将一直循环执行以下阶段：发现、设计、写代码和测试。这种方法将允许我们快速回顾学习前面各个短期目标并定期迭代平台。\n\n- 我们承诺的透明度将会随着EOS社区的双周刊更新，并且会有公共代码库,一个公开开发的待办事项列表(Trello Board)，最后当然会开源代码。\n\n\n\n### Budget Breakdown - $378,421\n\n● 12 Team Members working 80-120 hours per month on the project, with hours and costs decreasing in later phases.\n\n○ 1 Product Manager, 2 UI/UX Designers / Front-End Developers, 2 System & Security Engineers, 2 Lead Software Engineers, and 5 Software Engineers\n\n○ $59.5k per month for the first 4 months (phase 1 & 2), $45.8k per month for the following 2 months (phase 3). A total of $329.7k for the 6 months.\n\n● Infrastructure Costs\n\n○ $15.6k for servers, $750 for EOS staking\n\n● Additional Costs\n\n$15k for security audit.\n\n\n\n### 预算列表——378421美元\n\n●每月12个团队成员将为项目工作80 - 120小时，在后续阶段时间和成本将会逐渐降低。\n\n○1名产品经理，2名 UI / UX设计师/前端开发人员，2名系统安全工程师，2名软件工程师领导，5名软件工程师\n\n○前4个月每月59500美元(第1&第2阶段)，接下来的2个月每月45900美元(第3阶段)，总共6个月需要的是329700美元。\n\n●基础设施成本\n\n○15600美元用于服务器，750美元用于EOS的质押\n\n●额外成本\n\n○15000的安全审计。\n\n\n\n\n\n*本文图片来源于英文原文*\n***\n\n\n**了解更多关于EOShenzhen：**\n\n[We are EOShenzhen](https://busy.org/@eoshenzhen/we-are-eoshenzhen-eos-bp-candidate)\n\n**不同入口如何投票：**\n[imToken](https://busy.org/@eoshenzhen/voting-through-imtoken)\n[火币](https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484391&idx=2&sn=8fa9e724a729ecd8bb8e7d2722c14add&chksm=fa0b82dbcd7c0bcd5266bf3cd179d90964b2879c361d26da7cf3e2790b4d87fc34878e57ec9c&scene=21#wechat_redirect)\n[portal](https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484354&idx=1&sn=ddd4ffdae1531385a07fad59a6e86e6e&chksm=fa0b82fecd7c0be8328a0b3a1cff7de3bef207977ab0ca829c336fb450a7ef5c4153f32d5a4f&scene=21#wechat_redirect)\n\n**关于我们更多联系：**\nWebsite：https://eoshenzhen.io\n\nSteem：https://steemit.com/@eoshenzhen\n\nBusy：https://busy.org/@eoshenzhen\n\nTelegram：https://t.me/eoshenzhen\n\nTwitter：https://twitter.com/eostechlover\n\n简书：EOS技术爱好者\n\n新浪微博：EOSTechLover\n***\n**EOShenzhen的投票账号：eoshenzhenio**\n![100x100-IMG_7963_small.png](https://ipfs.busy.org/ipfs/QmTdwaSQTJR15zQcr6AQUi7Wgi9z51s97DcAfhNhhN9A6c)\n\n",
      "json_metadata": "{\"community\":\"busy\",\"app\":\"busy/2.5.6\",\"format\":\"markdown\",\"tags\":[\"eos\",\"wps\",\"wpf\",\"fund\"],\"users\":[\"eoshenzhen\"],\"links\":[\"https://drive.google.com/file/d/1pQRNf69WLA36NMVAFq8MS0AO4q5F0-AE/view\",\"https://www.linkedin.com/in/sungjaechung/\",\"https://www.linkedin.com/in/sjsyedjafri/\",\"https://www.linkedin.com/in/hugocampanella/\",\"https://www.linkedin.com/in/adrian-michael-hunter/\",\"https://www.linkedin.com/in/boram-k-b2530669/\",\"https://www.linkedin.com/in/thomas-do-01911516a\",\"https://www.linkedin.com/in/alfredcheuk/\",\"https://github.com/sheldonhh\",\"https://github.com/abbasali\"],\"image\":[\"https://ipfs.busy.org/ipfs/QmPEEARUo2vrbVE5qbtbTyVt3dcsfDqnYY9ot3tXTGDsTA\",\"https://ipfs.busy.org/ipfs/QmTdwaSQTJR15zQcr6AQUi7Wgi9z51s97DcAfhNhhN9A6c\"]}",
      "parent_author": "",
      "parent_permlink": "eos",
      "permlink": "or-wps-wpf",
      "title": "【翻译|公告】WPS申请WPF的发展资金"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-03T00:43:00",
  "trx_id": "e2e88fc1a1e0796300f4f7855cec1fc362fc8d82",
  "trx_in_block": 20,
  "virtual_op": 0
}

{
  "block": 25609249,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "ian-v-7",
      "voter": "quantum-bug",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-09-02T14:08:48",
  "trx_id": "554b5e814cfefe20472a663578129ad605a26e6f",
  "trx_in_block": 14,
  "virtual_op": 0
}

{
  "block": 25469627,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "61wwgj-or-ian",
      "voter": "tsto",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-08-28T17:44:00",
  "trx_id": "10f3669b27dd99d81ce71408e76569b763142321",
  "trx_in_block": 11,
  "virtual_op": 0
}

{
  "block": 25469621,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "2ahhsp-or-ian",
      "voter": "tsto",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-08-28T17:43:42",
  "trx_id": "4787d67ed47449f0d4fc51cea3e1f07fd2da3e71",
  "trx_in_block": 26,
  "virtual_op": 0
}

{
  "block": 25461973,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "2ahhsp-or-ian",
      "voter": "coin.info",
      "weight": 694
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-08-28T11:21:12",
  "trx_id": "ab3ad6bcaebe7ebc7c9b95d69bf562ae07d1d38c",
  "trx_in_block": 63,
  "virtual_op": 0
}

{
  "block": 25461972,
  "op": [
    "comment",
    {
      "author": "coin.info",
      "body": "**Coins mentioned in post:**\n\nCoin | | Price (USD) | 📈 24h | 📈 7d\n- | - | - | - | -\n**BTC** | Bitcoin | 6940.409$ | _3.12%_ | _7.86%_\n**EOS** | EOS | 5.404$ | _4.4%_ | _11.93%_\n**ETH** | Ethereum | 286.503$ | _3.29%_ | _2.06%_\n**STEEM** | Steem | 0.973$ | _5.92%_ | _11.2%_",
      "json_metadata": "{\"app\":\"coininfo/1.0.0\",\"format\":\"markdown\"}",
      "parent_author": "eoshenzhen",
      "parent_permlink": "2ahhsp-or-ian",
      "permlink": "re-eoshenzhen-2ahhsp-or-ian-20180828t112107532z",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-08-28T11:21:09",
  "trx_id": "7b250bdb5afd261f7d42b32e2b508f038c8c6757",
  "trx_in_block": 1,
  "virtual_op": 0
}

{
  "block": 25451838,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "2ahhsp-or-ian",
      "voter": "sensation",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-08-28T02:53:36",
  "trx_id": "1edac3f43a5e8a7b88c45f5d4059aa54c97e1128",
  "trx_in_block": 6,
  "virtual_op": 0
}

{
  "block": 25451832,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "ian-v-7",
      "voter": "sensation",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-08-28T02:53:18",
  "trx_id": "8161327ad3b4046a6f1df53f81fa3b58a0e95847",
  "trx_in_block": 1,
  "virtual_op": 0
}

{
  "block": 25450629,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "61wwgj-or-ian",
      "voter": "eoshenzhen",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-08-28T01:53:03",
  "trx_id": "c151ab2470c3ab1281136f0137083857f41eecef",
  "trx_in_block": 28,
  "virtual_op": 0
}

{
  "block": 25450629,
  "op": [
    "comment",
    {
      "author": "eoshenzhen",
      "body": "版权声明：\n\n以下内容来自微信公共帐号“EOS技术爱好者”，搜索“EOSTechLover”即可订阅，翻译Gavin，校对Lochaiching。转载必须保留以上声明。仅授权原文转载。\n\n\n\n本文原文链接 https://busy.org/@iang/why-go-full-ricardian-the-digital-contract ，由本号“EOS技术爱好者”翻译。\n\n\n\n\"EOS技术爱好者\"全程由EOShenzhen运营，喜欢我们请为我们投票（EOShenzhen的投票账号：eoshenzhenio）！\n\n***\n\n# Why Go Full Ricardian - the digital contract\n\n*作者：Ian Grigg*\n\n*翻译：Gavin*\n\n*校对：Lochaiching*\n\n\n\nIn the [last post]( https://steemit.com/eos/@iang/towards-a-ricardian-constitution) I outlined what it took to create a document that was both human readable and machine readable, good enough for a legal contract, and also good enough to support an accounting model like cryptocurrency. Now that we have that contract that both the computer and the human can read, and agree upon, it remains to communicate it.\n\n\n\n在上一篇文章中，我概述了创建一个人类可读和机器可读的文档，对于法律合约来说已经是足够好的存在了，而且还足以支持加密货币这样的会计模型。 既然我们已经拥有计算机和人类都可读，并能达成一致意见的合约，那么接下来要做的就是将它传达出去。\n\n \n\nMost prose contracts are written, emailed, argued about & redlined & mangled, eventually to be signed and then confined to the bottom of a drawer. To be forgotten, which is perhaps an odd way to treat something so central to the nature of business and agreement.\n![WechatIMG264.png](https://ipfs.busy.org/ipfs/QmcHRyNzhMSdDday45Z16nKy2SLb9Ds5cvhiSnE3wWPC9F)\n大多数散文合约都是书面形式，通过电子邮件发送、争论和修改，最终签署，然后定稿放在抽屉的底部。真可能被遗忘，这也许是一种不恰当的方式来处理商业业务和协议的核心。\n\n\n\nNot so a digital contract! As we have injected into the contract the key parameters that make this contract special, we can now actually use the contract in a transactional way: to communicate what a payment, trade or other transaction is.\n\n\n\n这不是一个数字合同！由于我们已经在合约中注入了使这个合约变得特别的关键参数，那么我们现在就可以以交易的方式实际使用合约：来传达支付、交易或其他交易的信息。\n\n\n\nTo do this we have to use a hashing trick from cryptography. We take the hash (“cryptographic message digest”) of the above document and embed it in all the transactions that refer to that contract. This means that the transactions ‘know’ about the contract in some sense.\n\n\n\n要做到这一点，我们必须使用密码学的hashing trick。我们使用上述文档的哈希码（“加密消息摘要”），并将其嵌入到所有涉及该合同的事务中。这意味着交易在某种意义上是“透明”的。\n![ian最大化2.png](https://ipfs.busy.org/ipfs/QmQn8A1aSHT5y6iqqGkG3LmXH71o7LHfyZimVemjyzmm6g)\n*Hashing trick注释(校对者注), 来源http://sofasofa.io/*\n\nFor example, if the transaction were a payment from Alice to Bob of say dollars, then the contract would describe the dollars. To see how this works, consider this payment where Alice pays Bob:\n```\n{Alice, Bob, 100, dollars}\n```\n\n\n例如，如果交易是从Alice到Bob的使用美元来付款，那么合约将描述美元。要了解其工作原理，请考虑Alice向Bob支付的款项：\n```\n{Alice, Bob, 100, dollars}\n```\n\n\nThis record might maybe describe a transaction in some contexts, but it isn’t really good enough in a complicated, global world - I might send you Hong Kong dollars, and you might be expecting Singapore dollars. Oops! Also, that number that’s in the record - is that 100 referring to 100 dollars or 1.00 dollars being 100 cents or a 100 satoshi-dollars which might be about 0.000001 dollars each?\n\n\n\n这条记录可能会在某些情况下描述一个交易，但在一个复杂的全球化世界中它并不够好——我可能会寄给你港元，而你可能会期待我会给你寄新加坡币。对了！ 此外，记录中的那个数字 - 100指的是100美元，或者等值于1美元的100美分，或者100聪美元，每聪美元可能只等价于0.000001美元？\n\n\n\nThe computer can’t really tell, and if the computer, as your digital angel, can’t know then you can’t know. Oh, yes, databases and all that but they are just honeytraps for insider frauds and viruses and other horrors. If databases could do payments for everyone, blockchain wouldn’t have been invented.\n\n\n\n计算机无法分辨出来，如果计算机，作为你的数字天使，它无法知道那么你就无法知道。哦，是的，数据库和所有这些，但它们只是对于内部诈骗、病毒和其他恐怖的蜜罐。如果数据库能够为每个人完成支付操作，那么区块链就不会被发明出来了。\n\n\n\nLet’s now see how we do this in a Ricardian fashion. I pay you:\n```\n{Alice, Bob, 10000, ABC1234IANG66DOLLAR911911HASH}\n```\nis actually less intelligible than the above. Which is an advantage because now your client software has to fix its and your information misery.\n\n\n\n现在让我们看看我们如何以李嘉图的方式做到这一点。 我付钱给你：\n```\n{Alice, Bob, 10000, ABC1234IANG66DOLLAR911911HASH} \n```\n实际上比上面的要更加不容易理解。这是一个优势，因为现在你的客户端软件必须处理它和你的信息问题。\n\n\n\nWhat happens is this. Your client software, your digital angel, has to take that horrible hash thing ABC1234IANG66DOLLAR911911HASH and go look up a document that matches the hash.\n\n\n\n事情是这样的。你的客户端软件，你的数字天使，必须读取那个的哈希值ABC1234IANG66DOLLAR911911HASH， 并去查找一个匹配哈希值的文档。\n\n\n\nBecause it’s a hash, there is only one document, and that document self-proves itself as being the document of the hash - take that, you insider scummers! And, assuming that the document is a contract as described in the [last post](https://steemit.com/eos/@iang/towards-a-ricardian-constitution), then we have some simple parameters that can be extracted out of it. With these parameters being easily recoverable using our above markup and parameter techniques, your digital angel can now tell you:\n```\nBob, you’ve been paid $100.00 in IangBux by Alice. We know this currency and we liked it before. This takes your balance to $120.00 and your savings plan is on track!\n```\n\n\n因为它是一个哈希值，所以只有一个文档与其对应，并且该文档可以自我证明它是哈希值所匹配的文档——有了这个，你就是知道这个内幕的人！ 并且，假设文档是上一篇文章中描述的合约，那么我们可以从中提取一些简单的参数。 使用我们上述的标记和参数技术可以轻松恢复这些参数，你的数字天使现在可以告诉你：\n```\nBob，你已经在IangBux收到Alice支付的100美元了。 我们知道这种货币，我们之前喜欢它。 你的余额将提高到120.00美元，你的储蓄计划正在按计划进行！\n```\n\n\nAll the context of the contract is now at the hands of the client software, instantly and without confusion.\n\n\n\n合同的所有上下文现在都在客户端软件的手中，具有即时性并且有序。\n\n\n\n\n\n## Why the contract needs to be digitised\n\n## 为什么合约需要数字化\n\nThis becomes much clearer in any large scale world. An ISDA Swaps contract can run to 300 pages long, and can fill drawers and consume hours of time - digitisation allows those drawers to be emptied, but also gives us instant and permanent access to everything in the contract of repetitive value! Permanency is a big win too - if you know anyone who is older than 70, ask them what the contract of their favourite currency was - chances are they will talk wistfully about the gold window and how the bank promised to pay the bearer 1 pound of sterling silver and other such other stories. Unfortunately for the Bank of England and the Federal Reserve, they didn’t have cryptography available to them in those days, and couldn’t lock their contracts down with hashes. Inevitably, without such discipline, the contract slipped away, and we’re left with legend.\n\n\n\n在任何大规模的世界中，这都变得更加清晰。 ISDA Swaps合约可以长达300页，可以填充抽屉并消耗数小时的时间——数字化可以清空这些抽屉的存在，同时也让我们能够在重复价值的合约中获取即时和永久的使用权！ 永久性也是一个巨大的胜利——如果你认识一个年龄超过70岁的人，问问他们最喜欢的货币合约是什么，他们有可能会对以前美元兑换金子的窗口充满渴望之情，以及银行承诺向持票人支付1英镑标准的纯银和其他此类故事。不幸的是，对于英格兰银行和美联储来说，他们当时没有可用的密码学技术，也无法用哈希相关技术来锁定他们的合约。不可避免地，如果没有这样的学科，合约就会慢慢失效消失掉，只给我们会留下一段传奇。\n\n\n\nWhat is the contract today for the US dollar? If it was in Ricardian form, you would know, precisely. As it is not, the “contract” is little more than a marketing slogan that is changed as and when the Federal Reserve needs another brand makeover.\n\n\n\n今天的美元合同是什么？如果按照李嘉图形式，你就会准确地知道。事实并非如此，“合约”不过是一个营销口号，当美联储需要另一个品牌改造时，它就会改变。\n\n\n\nBrands are useful, and the state can get away with just the one brand. But in the open contractual space of blockchain, we need contractual certainty for digital issuances, not least because there are so many issuances - ERC-20s! ICOs! and those are the polite terms - that these days it is hard to tell what any of them mean. And by using the approach mentioned [earlier](https://steemit.com/eos/@iang/towards-a-ricardian-constitution) we gain some much-appreciated precision: prose for legals, parameters for variability, and hashes to lock the precision into an accounting system.\n\n\n\n品牌是有用的，国家可以只使用一个品牌。但在区块链的开放合同空间中，我们需要追求数字发行的合约的确定性，因为有太多的发行-ERC-20和ICO了！这些都是礼貌用语——这么短时间很难说清楚它们的含义。通过使用前面提到的方法，我们获得了一些非常容易接受的精度值：法律的散文，可变的参数，以及将精度锁定到会计系统中的哈希值。\n\n![ian最大化3.png](https://ipfs.busy.org/ipfs/QmeQ67cJPcoNWQMZ12zsxZP5vem7dhQVThu3Sjp4Aj1Ji6)\n(Soft note - this concept of {prose, params and code} is further explored in [Sum of all Chains](http://financialcryptography.com/mt/archives/001556.html) but it's too much for one post.)\n\n\n\n稍微注意——{散文、参数和代码}的概念进一步探讨[所有链] (http://financialcryptography.com/mt/archives/001556.html)，但是它对于一个帖子的内容来说实在是太多了。\n\n\n\n\n\n## The Ricardian Constitution\n\n## 李嘉图合约\n\nIf the contract were a constitution for a chain, this would bring the benefit that the blockchain’s code could extract the parameters directly. A chain could follow its inflation rate, simply by reading what the users had agreed in the constitution. Then the code would follow suit by looking up the constitution and extracting out the number directly - no more hard coding, no more duplication, no more cumbersome alignment of code with prose.\n\n\n\n如果合约是一种链的结构，那么区块链的代码就可以直接提取出这些参数。只需阅读用户在合约中达成的协议，这个链就可以跟随其增发率发生变化。 然后代码将通过查阅合约并直接提取数字来跟进——不再需要硬编码，不再需要重复，不再需要根据散文进行繁琐的代码调整。\n\n\n\nThe hash of the Constitution could also appear in key instructions and would therefore signify - by custom - that the initiator of that transactio**** **** ****greeing to the constitution. For example, if the CREATE-NEW-ACCOUNT instruction included the hash, this enters that account to the Constitution, which in turn defines the Community: all who have accounts are all under the same Constitution and are all in the Community.\n\n\n\n合约的哈希值也可能出现在关键指令中，因此，根据惯例，该交易的发起者默认为已经同意合约内容。例如，如果CREATE-NEW-ACCOUNT指令包含了哈希值，那么该账户被添加到合约中中，而合约又定义了社区：所有拥有账户的人都在同一个合约下，并且都在社区中。\n\n\n\nIn sum, using the Ricardian form brings specific advantages to a community blockchain:\n\n\n\n总而言之，使用李嘉图形式为社区区块链带来了特定的优势：\n\n1.The hash mechanism means it is impossible to be uncertain about which document we are talking about, which removes large areas of confusion:\n\n  - In selecting its constitution, the community votes over a hash of that constitution, which points to the precise document\n  - The transactions on the blockchain lock into a hash, so they are bound to the correct and useful document.\n\n\n\n1、哈希机制意味着我们不可能不确定我们正在讨论哪个文档，从而消除了大量的混淆：\n- 在选择合约时，社区对该合约的主题进行投票，该合约指向精确的文件\n- 区块链上的事务锁定为一个哈希码，因此它们被绑定到正确且有用的文档\n\n2.The prose of the contract means that we can use all the fine tradition of law to express our desired agreement, and to explain and interpret it when needed - which removes a lot of uncertainties and makes our business that much clearer.\n- Note that this doesn’t change the way the document is created - you can use lawyers to draft your contract, or you can write it yourself.\n- Plain writing is preferred however it is done!\n\n2. 合约的散文意味着我们可以利用所有优良的法律传统来表达我们期望的协议，并在需要的时候解读和诠释它——这消除了许多不确定性，使我们的业务更加清晰：\n- 请注意，这并没有改变文档原来的创建方式——你可以找律师来起草合约，或者你也可以自己编写\n- 简单朴素的写作是首选，一定要这么做\n\n3.The parameters mean we can not only demarcate key points for the reader, we can communicate them to the computer too.\n- The name, initial quantity & inflation are now parameters within our contract, which makes it easy to colour them for effect for the human reader, and feed them into the program for the computer ‘reader’.\n- The display parameters allow the program to handle symbols and decimals of all forms.\n\n\n3、参数意味着我们不仅可以为读者划分关键点，我们还可以将它们传达给计算机。\n\n- 名称，初始量和增发率是在我们当前合约中的参数，这使得它们很方便为读者设置颜色，并将他们输入到计算机“读者”的程序中。\n\n- 显示允许程序处理所有表格的符号和小数的参数。\n\n\n\n4.It is now relatively easy for alternative chains to build a different business proposition. The parameters signpost what they have to change when starting up their chain.\n\n\n\n4、通过替代链来构建不同的业务主张变得相对简单。这些参数在启动它们的链时，会标记出它们必须需要改变的东西。\n\n\n\n5.There’s only one document which is the source of truth\n\n- No more separate parameter files, no more discoordination\n- No more hard coding!\n\n\n\n5、只有一份文档是真正的源文件\n- 没有更多单独的参数文件，不会再有不协调的情况\n- 没有更多的硬编码！\n\n\n\n\n\n本文图片来源于英文原文\n***\n\n\n**了解更多关于EOShenzhen：**\n\n[We are EOShenzhen](https://busy.org/@eoshenzhen/we-are-eoshenzhen-eos-bp-candidate)\n\n**不同入口如何投票：**\n[imToken](https://busy.org/@eoshenzhen/voting-through-imtoken)\n[火币](https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484391&idx=2&sn=8fa9e724a729ecd8bb8e7d2722c14add&chksm=fa0b82dbcd7c0bcd5266bf3cd179d90964b2879c361d26da7cf3e2790b4d87fc34878e57ec9c&scene=21#wechat_redirect)\n[portal](https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484354&idx=1&sn=ddd4ffdae1531385a07fad59a6e86e6e&chksm=fa0b82fecd7c0be8328a0b3a1cff7de3bef207977ab0ca829c336fb450a7ef5c4153f32d5a4f&scene=21#wechat_redirect)\n\n**关于我们更多联系：**\nWebsite：https://eoshenzhen.io\n\nSteem：https://steemit.com/@eoshenzhen\n\nBusy：https://busy.org/@eoshenzhen\n\nTelegram：https://t.me/eoshenzhen\n\nTwitter：https://twitter.com/eostechlover\n\n简书：EOS技术爱好者\n\n新浪微博：EOSTechLover\n***\n**EOShenzhen的投票账号：eoshenzhenio**\n![100x100-IMG_7963_small.png](https://ipfs.busy.org/ipfs/QmTdwaSQTJR15zQcr6AQUi7Wgi9z51s97DcAfhNhhN9A6c)\n\n",
      "json_metadata": "{\"community\":\"busy\",\"app\":\"busy/2.5.6\",\"format\":\"markdown\",\"tags\":[\"ian\",\"ricardian\",\"contract\",\"digital\",\"eos\"],\"users\":[\"iang\",\"eoshenzhen\"],\"links\":[\"https://busy.org/@iang/why-go-full-ricardian-the-digital-contract\",\"https://steemit.com/eos/@iang/towards-a-ricardian-constitution\",\"http://sofasofa.io/\",\"https://steemit.com/eos/@iang/towards-a-ricardian-constitution\",\"https://steemit.com/eos/@iang/towards-a-ricardian-constitution\",\"http://financialcryptography.com/mt/archives/001556.html\",\"http://financialcryptography.com/mt/archives/001556.html\",\"https://busy.org/@eoshenzhen/we-are-eoshenzhen-eos-bp-candidate\",\"https://busy.org/@eoshenzhen/voting-through-imtoken\",\"https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484391&idx=2&sn=8fa9e724a729ecd8bb8e7d2722c14add&chksm=fa0b82dbcd7c0bcd5266bf3cd179d90964b2879c361d26da7cf3e2790b4d87fc34878e57ec9c&scene=21#wechat_redirect\"],\"image\":[\"https://ipfs.busy.org/ipfs/QmcHRyNzhMSdDday45Z16nKy2SLb9Ds5cvhiSnE3wWPC9F\",\"https://ipfs.busy.org/ipfs/QmQn8A1aSHT5y6iqqGkG3LmXH71o7LHfyZimVemjyzmm6g\",\"https://ipfs.busy.org/ipfs/QmeQ67cJPcoNWQMZ12zsxZP5vem7dhQVThu3Sjp4Aj1Ji6\",\"https://ipfs.busy.org/ipfs/QmTdwaSQTJR15zQcr6AQUi7Wgi9z51s97DcAfhNhhN9A6c\"]}",
      "parent_author": "",
      "parent_permlink": "ian",
      "permlink": "61wwgj-or-ian",
      "title": "【翻译|Ian】为什么要最大化李嘉图合约范围？"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-08-28T01:53:03",
  "trx_id": "c151ab2470c3ab1281136f0137083857f41eecef",
  "trx_in_block": 28,
  "virtual_op": 0
}

{
  "block": 25450069,
  "op": [
    "vote",
    {
      "author": "eoshenzhen",
      "permlink": "ian-v-7",
      "voter": "eoshenzhen",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-08-28T01:25:00",
  "trx_id": "9ee33c096632f8a7a507209d9360aed6ed9aecdc",
  "trx_in_block": 28,
  "virtual_op": 0
}