Ecoer Logo
eoshenzhen

@eoshenzhen

25

EOS Evangelist, Block Producer Candidate

hive.blog/@eoshenzhen
VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS0.00%
Net Worth
15.982USD
HIVE
2.019HIVE
HBD
0.000HBD
Own HP
3.776HP

Detailed Balance

HIVE
balance
2.019HIVE
market_balance
0.000HIVE
savings_balance
0.000HIVE
reward_hive_balance
0.178HIVE
HIVE POWER
Own HP
3.776HP
Delegated Out
0.000HP
Delegation In
0.000HP
Effective Power
3.776HP
Reward HP (pending)
5.642HP
HBD
hbd_balance
0.000HBD
hbd_conversions
0.000HBD
hbd_market_balance
0.000HBD
savings_hbd_balance
0.000HBD
reward_hbd_balance
13.591HBD
{
  "balance": "2.019 HIVE",
  "savings_balance": "0.000 HIVE",
  "reward_hive_balance": "0.178 HIVE",
  "vesting_shares": "6128.440589 VESTS",
  "delegated_vesting_shares": "0.000000 VESTS",
  "received_vesting_shares": "0.000000 VESTS",
  "hbd_balance": "0.000 HBD",
  "savings_hbd_balance": "0.000 HBD",
  "reward_hbd_balance": "13.591 HBD"
}

Account Info

nameeoshenzhen
id800151
rank0
reputation0
created2018-03-03T02:46:42
recovery_accountblocktrades
proxyNone
invited_bynull
post_count141
comment_count0
lifetime_vote_count0
witnesses_voted_for0
last_post2019-03-03T10:56:39
last_root_post2018-09-19T04:02:30
last_vote_time2018-09-17T06:50:21
proxied_vsf_votes0, 0, 0, 0
can_vote1
voting_power9,618
delayed_votesNone
governance_vote_expiration_ts1969-12-31T23:59:59
balance2.019 HIVE
savings_balance0.000 HIVE
hbd_balance0.000 HBD
savings_hbd_balance0.000 HBD
vesting_shares6128.440589 VESTS
delegated_vesting_shares0.000000 VESTS
received_vesting_shares0.000000 VESTS
reward_vesting_balance11514.936482 VESTS
vesting_balance0.000 HIVE
vesting_withdraw_rate0.000000 VESTS
next_vesting_withdrawal1969-12-31T23:59:59
withdrawn0
to_withdraw0
withdraw_routes0
savings_withdraw_requests0
last_account_recovery1970-01-01T00:00:00
reset_accountnull
last_owner_update2018-10-29T03:02:51
last_account_update2018-10-29T03:02:51
minedNo
hbd_seconds0
hbd_last_interest_payment2019-03-03T08:58:39
savings_hbd_last_interest_payment1970-01-01T00:00:00
{
  "id": 800151,
  "name": "eoshenzhen",
  "owner": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM7MyxQ9ARDFqtcfr19ZrGRW5W8mZe46Etac4PWUbbr1HS44xQZD",
        1
      ]
    ]
  },
  "active": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM7QSPBU7A2kKAeeYZoMPEB7mMD7YXKHm3HnEKmDSct69JtJX8CW",
        1
      ]
    ]
  },
  "posting": {
    "weight_threshold": 1,
    "account_auths": [
      [
        "busy.app",
        1
      ]
    ],
    "key_auths": [
      [
        "STM8Us5QYGDGR8PE3Dh3LUJBngbrDWmiFTvvPEr9AyNFNZeShtCGp",
        1
      ]
    ]
  },
  "memo_key": "STM5gxgUfpqfhsicHNG9AotN7snBkwq7j23Nrdi1rVWFMYFn73rGV",
  "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\"}}",
  "posting_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\"}}",
  "proxy": "",
  "previous_owner_update": "1970-01-01T00:00:00",
  "last_owner_update": "2018-10-29T03:02:51",
  "last_account_update": "2018-10-29T03:02:51",
  "created": "2018-03-03T02:46:42",
  "mined": false,
  "recovery_account": "blocktrades",
  "last_account_recovery": "1970-01-01T00:00:00",
  "reset_account": "null",
  "comment_count": 0,
  "lifetime_vote_count": 0,
  "post_count": 141,
  "can_vote": true,
  "voting_manabar": {
    "current_mana": 9618,
    "last_update_time": 1537167021
  },
  "downvote_manabar": {
    "current_mana": 0,
    "last_update_time": 1520045199
  },
  "voting_power": 9618,
  "balance": "2.019 HIVE",
  "savings_balance": "0.000 HIVE",
  "hbd_balance": "0.000 HBD",
  "hbd_seconds": "0",
  "hbd_seconds_last_update": "2019-03-03T08:58:39",
  "hbd_last_interest_payment": "2019-03-03T08:58:39",
  "savings_hbd_balance": "0.000 HBD",
  "savings_hbd_seconds": "0",
  "savings_hbd_seconds_last_update": "1970-01-01T00:00:00",
  "savings_hbd_last_interest_payment": "1970-01-01T00:00:00",
  "savings_withdraw_requests": 0,
  "reward_hbd_balance": "13.591 HBD",
  "reward_hive_balance": "0.178 HIVE",
  "reward_vesting_balance": "11514.936482 VESTS",
  "reward_vesting_hive": "5.642 HIVE",
  "vesting_shares": "6128.440589 VESTS",
  "delegated_vesting_shares": "0.000000 VESTS",
  "received_vesting_shares": "0.000000 VESTS",
  "vesting_withdraw_rate": "0.000000 VESTS",
  "post_voting_power": "6128.440589 VESTS",
  "next_vesting_withdrawal": "1969-12-31T23:59:59",
  "withdrawn": 0,
  "to_withdraw": 0,
  "withdraw_routes": 0,
  "pending_transfers": 0,
  "curation_rewards": 0,
  "posting_rewards": 11275,
  "proxied_vsf_votes": [
    0,
    0,
    0,
    0
  ],
  "witnesses_voted_for": 0,
  "last_post": "2019-03-03T10:56:39",
  "last_root_post": "2018-09-19T04:02:30",
  "last_vote_time": "2018-09-17T06:50:21",
  "post_bandwidth": 0,
  "pending_claimed_accounts": 0,
  "governance_vote_expiration_ts": "1969-12-31T23:59:59",
  "delayed_votes": [],
  "open_recurrent_transfers": 0,
  "vesting_balance": "0.000 HIVE",
  "reputation": 0,
  "transfer_history": [],
  "market_history": [],
  "post_history": [],
  "vote_history": [],
  "other_history": [],
  "witness_votes": [],
  "tags_usage": [],
  "guest_bloggers": [],
  "rank": 0
}

Withdraw Routes

IncomingOutgoing
Empty
Empty
{
  "incoming": [],
  "outgoing": []
}
From Date
To Date
2020/03/05 04:59:57
bodyCongratulations @eoshenzhen! You received a personal award! <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> <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> **Do not miss the last post from @steemitboard:** <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> ###### [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!
title
authorsteemitboard
permlinksteemitboard-notify-eoshenzhen-20200305t045954000z
json metadata{"image":["https://steemitboard.com/img/notify.png"]}
parent authoreoshenzhen
parent permlinkbancor-bancorx
Transaction InfoBlock #41376848/Trx cebcba4c0be01d00f90295d731f459d3004f1274
View Raw JSON Data
{
  "op": [
    "comment",
    {
      "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!",
      "title": "",
      "author": "steemitboard",
      "permlink": "steemitboard-notify-eoshenzhen-20200305t045954000z",
      "json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}",
      "parent_author": "eoshenzhen",
      "parent_permlink": "bancor-bancorx"
    }
  ],
  "block": 41376848,
  "trx_id": "cebcba4c0be01d00f90295d731f459d3004f1274",
  "op_in_trx": 0,
  "timestamp": "2020-03-05T04:59:57",
  "virtual_op": false,
  "trx_in_block": 6
}
2019/09/06 11:55:00
voterquantum-bug
authoreoshenzhen
weight10000 (100.00%)
permlink5ggc72-or-wps
Transaction InfoBlock #36183944/Trx 46b507a87f87341565f1f76dc0a11387338556b7
View Raw JSON Data
{
  "op": [
    "vote",
    {
      "voter": "quantum-bug",
      "author": "eoshenzhen",
      "weight": 10000,
      "permlink": "5ggc72-or-wps"
    }
  ],
  "block": 36183944,
  "trx_id": "46b507a87f87341565f1f76dc0a11387338556b7",
  "op_in_trx": 0,
  "timestamp": "2019-09-06T11:55:00",
  "virtual_op": false,
  "trx_in_block": 10
}
2019/09/06 11:54:57
voterquantum-bug
authoreoshenzhen
weight10000 (100.00%)
permlinkbancor-bancorx
Transaction InfoBlock #36183943/Trx 6d83edfcdfec8410bdb2226d2ec2bbe5f43e0f43
View Raw JSON Data
{
  "op": [
    "vote",
    {
      "voter": "quantum-bug",
      "author": "eoshenzhen",
      "weight": 10000,
      "permlink": "bancor-bancorx"
    }
  ],
  "block": 36183943,
  "trx_id": "6d83edfcdfec8410bdb2226d2ec2bbe5f43e0f43",
  "op_in_trx": 0,
  "timestamp": "2019-09-06T11:54:57",
  "virtual_op": false,
  "trx_in_block": 16
}
2019/03/10 10:56:39
authoreoshenzhen
permlinkre-eosargentina-the-newunregdupd-proposal-claiming-tokens-locked-on-contracts-20190303t105639575z
Transaction InfoBlock #31029020/Virtual Operation 4294967295:3
View Raw JSON Data
{
  "op": [
    "comment_payout_update",
    {
      "author": "eoshenzhen",
      "permlink": "re-eosargentina-the-newunregdupd-proposal-claiming-tokens-locked-on-contracts-20190303t105639575z"
    }
  ],
  "block": 31029020,
  "trx_id": "0000000000000000000000000000000000000000",
  "op_in_trx": 3,
  "timestamp": "2019-03-10T10:56:39",
  "virtual_op": true,
  "trx_in_block": 4294967295
}
2019/03/03 10:56:42
bodyThanks Argentina for this work 👍
title
authoreoshenzhen
permlinkre-eosargentina-the-newunregdupd-proposal-claiming-tokens-locked-on-contracts-20190303t105639575z
json metadata{"community":"busy","app":"busy/2.5.6","format":"markdown","tags":["eos"],"users":[],"links":[],"image":[]}
parent authoreosargentina
parent permlinkthe-newunregdupd-proposal-claiming-tokens-locked-on-contracts
Transaction InfoBlock #30827553/Trx b6fd0e27790d7e1a15156fa022cefc77d0caedad
View Raw JSON Data
{
  "op": [
    "comment",
    {
      "body": "Thanks Argentina for this work 👍",
      "title": "",
      "author": "eoshenzhen",
      "permlink": "re-eosargentina-the-newunregdupd-proposal-claiming-tokens-locked-on-contracts-20190303t105639575z",
      "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"
    }
  ],
  "block": 30827553,
  "trx_id": "b6fd0e27790d7e1a15156fa022cefc77d0caedad",
  "op_in_trx": 0,
  "timestamp": "2019-03-03T10:56:42",
  "virtual_op": false,
  "trx_in_block": 26
}
eoshenzhencustom json: follow
2019/03/03 10:55:21
idfollow
json["reblog",{"account":"eoshenzhen","author":"eosargentina","permlink":"the-newunregdupd-proposal-claiming-tokens-locked-on-contracts"}]
required auths[]
required posting auths["eoshenzhen"]
Transaction InfoBlock #30827526/Trx b6222a0a9dcf207b17a10b1e66a828c090518c13
View Raw JSON Data
{
  "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"
      ]
    }
  ],
  "block": 30827526,
  "trx_id": "b6222a0a9dcf207b17a10b1e66a828c090518c13",
  "op_in_trx": 0,
  "timestamp": "2019-03-03T10:55:21",
  "virtual_op": false,
  "trx_in_block": 5
}
eoshenzhencustom json: follow
2019/03/03 08:59:06
idfollow
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"]
Transaction InfoBlock #30825201/Trx 588195378fcbe81aaee5c66de377284b05a8fa84
View Raw JSON Data
{
  "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"
      ]
    }
  ],
  "block": 30825201,
  "trx_id": "588195378fcbe81aaee5c66de377284b05a8fa84",
  "op_in_trx": 0,
  "timestamp": "2019-03-03T08:59:06",
  "virtual_op": false,
  "trx_in_block": 24
}
eoshenzhensent 0.011 HBD to @null- "@sheldonhuang/boscore-bos-2-0-2-fixes-and-eosio-1-6-0-and-takeaways"
2019/03/03 08:58:42
tonull
fromeoshenzhen
memo@sheldonhuang/boscore-bos-2-0-2-fixes-and-eosio-1-6-0-and-takeaways
amount0.011 HBD
Transaction InfoBlock #30825193/Trx f3e2e1051255328aa9ea0a9e37416e2ed06eedf8
View Raw JSON Data
{
  "op": [
    "transfer",
    {
      "to": "null",
      "from": "eoshenzhen",
      "memo": "@sheldonhuang/boscore-bos-2-0-2-fixes-and-eosio-1-6-0-and-takeaways",
      "amount": "0.011 HBD"
    }
  ],
  "block": 30825193,
  "trx_id": "f3e2e1051255328aa9ea0a9e37416e2ed06eedf8",
  "op_in_trx": 0,
  "timestamp": "2019-03-03T08:58:42",
  "virtual_op": false,
  "trx_in_block": 24
}
2019/03/03 04:26:18
bodyCongratulations @eoshenzhen! You received a personal award! <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> <sub>_[Click here to view your Board](https://steemitboard.com/@eoshenzhen)_</sub> **Do not miss the last post from @steemitboard:** <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> ###### [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!
title
authorsteemitboard
permlinksteemitboard-notify-eoshenzhen-20190303t042614000z
json metadata{"image":["https://steemitboard.com/img/notify.png"]}
parent authoreoshenzhen
parent permlinkbancor-bancorx
Transaction InfoBlock #30819749/Trx 41fb1e4a5ff9418af659ce404762529292828ce1
View Raw JSON Data
{
  "op": [
    "comment",
    {
      "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!",
      "title": "",
      "author": "steemitboard",
      "permlink": "steemitboard-notify-eoshenzhen-20190303t042614000z",
      "json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}",
      "parent_author": "eoshenzhen",
      "parent_permlink": "bancor-bancorx"
    }
  ],
  "block": 30819749,
  "trx_id": "41fb1e4a5ff9418af659ce404762529292828ce1",
  "op_in_trx": 0,
  "timestamp": "2019-03-03T04:26:18",
  "virtual_op": false,
  "trx_in_block": 3
}
eoshenzhenupdated their account properties
2018/10/29 03:02:54
owner{"key_auths":[["STM7MyxQ9ARDFqtcfr19ZrGRW5W8mZe46Etac4PWUbbr1HS44xQZD",1]],"account_auths":[],"weight_threshold":1}
active{"key_auths":[["STM7QSPBU7A2kKAeeYZoMPEB7mMD7YXKHm3HnEKmDSct69JtJX8CW",1]],"account_auths":[],"weight_threshold":1}
accounteoshenzhen
posting{"key_auths":[["STM8Us5QYGDGR8PE3Dh3LUJBngbrDWmiFTvvPEr9AyNFNZeShtCGp",1]],"account_auths":[["busy.app",1]],"weight_threshold":1}
memo keySTM5gxgUfpqfhsicHNG9AotN7snBkwq7j23Nrdi1rVWFMYFn73rGV
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"}}
Transaction InfoBlock #27220747/Trx 24e9064f4844bb37dea5b66aded1bbabaaa9ef77
View Raw JSON Data
{
  "op": [
    "account_update",
    {
      "owner": {
        "key_auths": [
          [
            "STM7MyxQ9ARDFqtcfr19ZrGRW5W8mZe46Etac4PWUbbr1HS44xQZD",
            1
          ]
        ],
        "account_auths": [],
        "weight_threshold": 1
      },
      "active": {
        "key_auths": [
          [
            "STM7QSPBU7A2kKAeeYZoMPEB7mMD7YXKHm3HnEKmDSct69JtJX8CW",
            1
          ]
        ],
        "account_auths": [],
        "weight_threshold": 1
      },
      "account": "eoshenzhen",
      "posting": {
        "key_auths": [
          [
            "STM8Us5QYGDGR8PE3Dh3LUJBngbrDWmiFTvvPEr9AyNFNZeShtCGp",
            1
          ]
        ],
        "account_auths": [
          [
            "busy.app",
            1
          ]
        ],
        "weight_threshold": 1
      },
      "memo_key": "STM5gxgUfpqfhsicHNG9AotN7snBkwq7j23Nrdi1rVWFMYFn73rGV",
      "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\"}}"
    }
  ],
  "block": 27220747,
  "trx_id": "24e9064f4844bb37dea5b66aded1bbabaaa9ef77",
  "op_in_trx": 0,
  "timestamp": "2018-10-29T03:02:54",
  "virtual_op": false,
  "trx_in_block": 3
}
eoshenzhenupdated payout for bancor-bancorx
2018/09/26 04:02:30
authoreoshenzhen
permlinkbancor-bancorx
Transaction InfoBlock #26272279/Virtual Operation 4294967295:2
View Raw JSON Data
{
  "op": [
    "comment_payout_update",
    {
      "author": "eoshenzhen",
      "permlink": "bancor-bancorx"
    }
  ],
  "block": 26272279,
  "trx_id": "0000000000000000000000000000000000000000",
  "op_in_trx": 2,
  "timestamp": "2018-09-26T04:02:30",
  "virtual_op": true,
  "trx_in_block": 4294967295
}
eoshenzhenupdated payout for 5ggc72-or-wps
2018/09/24 06:50:21
authoreoshenzhen
permlink5ggc72-or-wps
Transaction InfoBlock #26218198/Virtual Operation 4294967295:25
View Raw JSON Data
{
  "op": [
    "comment_payout_update",
    {
      "author": "eoshenzhen",
      "permlink": "5ggc72-or-wps"
    }
  ],
  "block": 26218198,
  "trx_id": "0000000000000000000000000000000000000000",
  "op_in_trx": 25,
  "timestamp": "2018-09-24T06:50:21",
  "virtual_op": true,
  "trx_in_block": 4294967295
}
eoshenzhenupdated payout for or-wps
2018/09/24 04:28:24
authoreoshenzhen
permlinkor-wps
Transaction InfoBlock #26215359/Virtual Operation 4294967295:2
View Raw JSON Data
{
  "op": [
    "comment_payout_update",
    {
      "author": "eoshenzhen",
      "permlink": "or-wps"
    }
  ],
  "block": 26215359,
  "trx_id": "0000000000000000000000000000000000000000",
  "op_in_trx": 2,
  "timestamp": "2018-09-24T04:28:24",
  "virtual_op": true,
  "trx_in_block": 4294967295
}
eoshenzhenupdated payout for v7yy2-or-ian
2018/09/24 04:17:27
authoreoshenzhen
permlinkv7yy2-or-ian
Transaction InfoBlock #26215140/Virtual Operation 4294967295:3
View Raw JSON Data
{
  "op": [
    "comment_payout_update",
    {
      "author": "eoshenzhen",
      "permlink": "v7yy2-or-ian"
    }
  ],
  "block": 26215140,
  "trx_id": "0000000000000000000000000000000000000000",
  "op_in_trx": 3,
  "timestamp": "2018-09-24T04:17:27",
  "virtual_op": true,
  "trx_in_block": 4294967295
}
tstoeffective vote applied for @eoshenzhen / bancor-bancorx
2018/09/21 23:52:21
votertsto
authoreoshenzhen
weight17959
rshares2275753456
permlinkbancor-bancorx
pending payout0.004 HBD
total vote weight65919
Transaction InfoBlock #26152289/Trx c27b14e659160c2bbc309f4ef3138515e821b875
View Raw JSON Data
{
  "op": [
    "effective_comment_vote",
    {
      "voter": "tsto",
      "author": "eoshenzhen",
      "weight": 17959,
      "rshares": 2275753456,
      "permlink": "bancor-bancorx",
      "pending_payout": "0.004 HBD",
      "total_vote_weight": 65919
    }
  ],
  "block": 26152289,
  "trx_id": "c27b14e659160c2bbc309f4ef3138515e821b875",
  "op_in_trx": 1,
  "timestamp": "2018-09-21T23:52:21",
  "virtual_op": true,
  "trx_in_block": 12
}
tstoupvoted (100.00%) @eoshenzhen / bancor-bancorx
2018/09/21 23:52:21
votertsto
authoreoshenzhen
weight10000 (100.00%)
permlinkbancor-bancorx
Transaction InfoBlock #26152289/Trx c27b14e659160c2bbc309f4ef3138515e821b875
View Raw JSON Data
{
  "op": [
    "vote",
    {
      "voter": "tsto",
      "author": "eoshenzhen",
      "weight": 10000,
      "permlink": "bancor-bancorx"
    }
  ],
  "block": 26152289,
  "trx_id": "c27b14e659160c2bbc309f4ef3138515e821b875",
  "op_in_trx": 0,
  "timestamp": "2018-09-21T23:52:21",
  "virtual_op": false,
  "trx_in_block": 12
}
artcitysent 0.001 HIVE to @eoshenzhen- "►►► 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"
2018/09/19 18:55:36
toeoshenzhen
fromartcity
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
amount0.001 HIVE
Transaction InfoBlock #26088811/Trx 0dd0a8814b17e8330e2f44b52bc6ce52c895254f
View Raw JSON Data
{
  "op": [
    "transfer",
    {
      "to": "eoshenzhen",
      "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",
      "amount": "0.001 HIVE"
    }
  ],
  "block": 26088811,
  "trx_id": "0dd0a8814b17e8330e2f44b52bc6ce52c895254f",
  "op_in_trx": 0,
  "timestamp": "2018-09-19T18:55:36",
  "virtual_op": false,
  "trx_in_block": 46
}
eoshenzhenpublished a new post: bancor-bancorx
2018/09/19 04:12:57
body@@ -183,16 +183,111 @@ H%E6%89%A9%E5%B1%95%E5%88%B0EOS%0A +!%5BWechatIMG358.png%5D(https://ipfs.busy.org/ipfs/QmaiPTUHKrDgMvBM2JLnKL7xLzDhFtGm85CU1AnRCNBp2T)%0A %0A%0A%0A%E6%88%91%E4%BB%AC%E5%BE%88%E9%AB%98%E5%85%B4
title【公告首发】Bancor发布首款去中心化流动网络跨链产品——BancorX
authoreoshenzhen
permlinkbancor-bancorx
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 permlinkbancor
Transaction InfoBlock #26071165/Trx 76c45cf5be3e1b9609b60c4509b5693bbd2312e1
View Raw JSON Data
{
  "op": [
    "comment",
    {
      "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",
      "title": "【公告首发】Bancor发布首款去中心化流动网络跨链产品——BancorX",
      "author": "eoshenzhen",
      "permlink": "bancor-bancorx",
      "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"
    }
  ],
  "block": 26071165,
  "trx_id": "76c45cf5be3e1b9609b60c4509b5693bbd2312e1",
  "op_in_trx": 0,
  "timestamp": "2018-09-19T04:12:57",
  "virtual_op": false,
  "trx_in_block": 27
}
2018/09/19 04:02:45
bodyHi! I am a robot. I just upvoted you! I found similar content that readers might be interested in: http://8btc.com/thread-226222-1-1.html
title
authorcheetah
permlinkcheetah-re-eoshenzhenbancor-bancorx
json metadata
parent authoreoshenzhen
parent permlinkbancor-bancorx
Transaction InfoBlock #26070962/Trx 1706f64ea6ddae6c098ea6f2a9dfc2d3121f4b40
View Raw JSON Data
{
  "op": [
    "comment",
    {
      "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",
      "title": "",
      "author": "cheetah",
      "permlink": "cheetah-re-eoshenzhenbancor-bancorx",
      "json_metadata": "",
      "parent_author": "eoshenzhen",
      "parent_permlink": "bancor-bancorx"
    }
  ],
  "block": 26070962,
  "trx_id": "1706f64ea6ddae6c098ea6f2a9dfc2d3121f4b40",
  "op_in_trx": 0,
  "timestamp": "2018-09-19T04:02:45",
  "virtual_op": false,
  "trx_in_block": 8
}
cheetaheffective vote applied for @eoshenzhen / bancor-bancorx
2018/09/19 04:02:39
votercheetah
authoreoshenzhen
weight159 (1.59%)
rshares2069421436
permlinkbancor-bancorx
pending payout0.002 HBD
total vote weight47960
Transaction InfoBlock #26070960/Trx ecded8545a646a79295698e2b1cac730c0a3f109
View Raw JSON Data
{
  "op": [
    "effective_comment_vote",
    {
      "voter": "cheetah",
      "author": "eoshenzhen",
      "weight": 159,
      "rshares": 2069421436,
      "permlink": "bancor-bancorx",
      "pending_payout": "0.002 HBD",
      "total_vote_weight": 47960
    }
  ],
  "block": 26070960,
  "trx_id": "ecded8545a646a79295698e2b1cac730c0a3f109",
  "op_in_trx": 1,
  "timestamp": "2018-09-19T04:02:39",
  "virtual_op": true,
  "trx_in_block": 20
}
2018/09/19 04:02:39
votercheetah
authoreoshenzhen
weight8 (0.08%)
permlinkbancor-bancorx
Transaction InfoBlock #26070960/Trx ecded8545a646a79295698e2b1cac730c0a3f109
View Raw JSON Data
{
  "op": [
    "vote",
    {
      "voter": "cheetah",
      "author": "eoshenzhen",
      "weight": 8,
      "permlink": "bancor-bancorx"
    }
  ],
  "block": 26070960,
  "trx_id": "ecded8545a646a79295698e2b1cac730c0a3f109",
  "op_in_trx": 0,
  "timestamp": "2018-09-19T04:02:39",
  "virtual_op": false,
  "trx_in_block": 20
}
eoshenzhenpublished a new post: bancor-bancorx
2018/09/19 04:02:33
body本公告由[Bancor官方](https://www.bancor.network)委托EOShenzhen声明,为国内首发,欢迎转载! "EOS技术爱好者"全程由EOShenzhen运营,喜欢我们请为我们投票(EOShenzhen的投票账号:eoshenzhenio)! *** # Bancor发布首款去中心化流动网络跨链产品——BancorX,从ETH扩展到EOS 我们很高兴宣布,我们将把Bancor协议扩展到EOS上。 Bancor已经在EOS上移植其公开代码,以准备发布去中心化跨链流动网络BancorX,它可支持以太坊和EOS主网。 Bancor最初建立于以太坊区块链,如今从增加对EOS的支持开始,它正逐渐发展为一种跨链流动协议。 Bancor将允许用户针对其自动智能合约(也称为Relay)执行基于EOS的即时代币转换。Relay为用户提供了一种自如转换代币的简单方法,无需将资金存入交易所,也无需买卖双方进行订单匹配。任何人都可以在EOS上创建Relay,并通过他们拥有和管理的智能合约中的代币来将其连接到Bancor的流动网络。 Bancor上列出的基于EOS的代币,很快就可以通过Bancor协议即时转换为任何基于以太坊的代币。 目前,Bancor已经在EOS上发布了其开源智能合约,以及一个简单的用户界面。该界面使用最受欢迎的EOS网络钱包Scatter,在测试网上处理基于EOS的代币转换。各项目可以在EOS测试网络上创建Reply,以便直接通过用户钱包自动在EOS上实现公平化、低成本和高效率的代币交易。其功能和用户界面均可嵌入到任何环境中,为寻求将跨链自动转换整合到其平台中的项目服务。同时,从该版本还可以看到Bancor对于EOS的优势,包括: - 1秒钟交易(以太坊> 10秒) - 无交易费用(以太坊的gas可达到50美元以上) - 无超前交易风险(EOS交易并不像以太坊那样按gas费用实行优先化) 作为第一个,同时也是最大的去中心化流动网络,Bancor网络自在以太坊上发布以来,已经处理了超过15亿美元的代币转换。Bancor为超过120个基于以太坊的代币项目提供了价格合理且易于获取的流动性,并且不收取上线费用。在一些前景最为可观的区块链项目在EOS上推出,将为用户提供速度和可扩展性的同时,Bancor正努力扩展其针对EOS生态系统的技术,并将很快发布第一批BancorX上基于EOS的代币。 与以太坊的情况一样,项目加入网络无需上线费用。现在立即申请成为BancorX上的第一批代币吧! 另一种在EOS上使用Bancor服务的途径,是新推出的EOS赏金计划。我们鼓励社群深入了解我们的代码,并帮助我们发现EOS智能合约中的潜在问题。优化合同或用户界面的开发人员将有机会获得超过50万个Bancor币(BNT)。 未来几周,请继续关注更多有关BancorX运作的详细信息。我们十分期待Bancor在EOS和以太坊生态系统中发挥其自动跨链流动性,连接全球两大共享基础设施,打造不断壮大且互通的区块链产业。 ## 关于Bancor Bancor是世界上最大的去中心化流动网络。它的运作方式类似于去中心化交易,但关键区别在于:订单是根据区块链上的自动智能合约处理的,而不是在交易中实行双方匹配。任何项目都可以通过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)获取更多信息。 *** **了解更多关于EOShenzhen:** [We are EOShenzhen](https://busy.org/@eoshenzhen/we-are-eoshenzhen-eos-bp-candidate) **不同入口如何投票:** [imToken](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) [portal](https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484354&idxx=1&sn=ddd4ffdae1531385a07fad59a6e86e6e&chksm=fa0b82fecd7c0be8328a0b3a1cff7de3bef207977ab0ca829c336fb450a7ef5c4153f32d5a4f&scene=21#wechat_redirect) **关于我们更多联系:** Website:https://eoshenzhen.io Steem:https://steemit.com/@eoshenzhen Busy:https://busy.org/@eoshenzhen Telegram:https://t.me/eoshenzhen Twitter:https://twitter.com/eostechlover 简书:EOS技术爱好者 新浪微博:EOSTechLover *** **EOShenzhen的投票账号:eoshenzhenio** ![100x100-IMG_7963_small.png](https://ipfs.busy.org/ipfs/QmTdwaSQTJR15zQcr6AQUi7Wgi9z51s97DcAfhNhhN9A6c)
title【公告首发】Bancor发布首款去中心化流动网络跨链产品——BancorX
authoreoshenzhen
permlinkbancor-bancorx
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 permlinkbancor
Transaction InfoBlock #26070958/Trx e97b36fdc2079838fd57a212180ae43d5da1fba3
View Raw JSON Data
{
  "op": [
    "comment",
    {
      "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)",
      "title": "【公告首发】Bancor发布首款去中心化流动网络跨链产品——BancorX",
      "author": "eoshenzhen",
      "permlink": "bancor-bancorx",
      "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"
    }
  ],
  "block": 26070958,
  "trx_id": "e97b36fdc2079838fd57a212180ae43d5da1fba3",
  "op_in_trx": 0,
  "timestamp": "2018-09-19T04:02:33",
  "virtual_op": false,
  "trx_in_block": 1
}
tstoeffective vote applied for @eoshenzhen / or-wps
2018/09/18 12:57:27
votertsto
authoreoshenzhen
weight7919 (79.19%)
rshares2076125960
permlinkor-wps
pending payout0.011 HBD
total vote weight107811
Transaction InfoBlock #26052987/Trx 649dc835c8ce3a7a2152d4b824fa37ed5e49e763
View Raw JSON Data
{
  "op": [
    "effective_comment_vote",
    {
      "voter": "tsto",
      "author": "eoshenzhen",
      "weight": 7919,
      "rshares": 2076125960,
      "permlink": "or-wps",
      "pending_payout": "0.011 HBD",
      "total_vote_weight": 107811
    }
  ],
  "block": 26052987,
  "trx_id": "649dc835c8ce3a7a2152d4b824fa37ed5e49e763",
  "op_in_trx": 1,
  "timestamp": "2018-09-18T12:57:27",
  "virtual_op": true,
  "trx_in_block": 7
}
tstoupvoted (100.00%) @eoshenzhen / or-wps
2018/09/18 12:57:27
votertsto
authoreoshenzhen
weight10000 (100.00%)
permlinkor-wps
Transaction InfoBlock #26052987/Trx 649dc835c8ce3a7a2152d4b824fa37ed5e49e763
View Raw JSON Data
{
  "op": [
    "vote",
    {
      "voter": "tsto",
      "author": "eoshenzhen",
      "weight": 10000,
      "permlink": "or-wps"
    }
  ],
  "block": 26052987,
  "trx_id": "649dc835c8ce3a7a2152d4b824fa37ed5e49e763",
  "op_in_trx": 0,
  "timestamp": "2018-09-18T12:57:27",
  "virtual_op": false,
  "trx_in_block": 7
}
tstoeffective vote applied for @eoshenzhen / 5ggc72-or-wps
2018/09/18 12:57:12
votertsto
authoreoshenzhen
weight38369
rshares2116051459
permlink5ggc72-or-wps
pending payout0.002 HBD
total vote weight49833
Transaction InfoBlock #26052982/Trx 201ebc5689635516426d73bf6269e3f8cf5e392c
View Raw JSON Data
{
  "op": [
    "effective_comment_vote",
    {
      "voter": "tsto",
      "author": "eoshenzhen",
      "weight": 38369,
      "rshares": 2116051459,
      "permlink": "5ggc72-or-wps",
      "pending_payout": "0.002 HBD",
      "total_vote_weight": 49833
    }
  ],
  "block": 26052982,
  "trx_id": "201ebc5689635516426d73bf6269e3f8cf5e392c",
  "op_in_trx": 1,
  "timestamp": "2018-09-18T12:57:12",
  "virtual_op": true,
  "trx_in_block": 19
}
tstoupvoted (100.00%) @eoshenzhen / 5ggc72-or-wps
2018/09/18 12:57:12
votertsto
authoreoshenzhen
weight10000 (100.00%)
permlink5ggc72-or-wps
Transaction InfoBlock #26052982/Trx 201ebc5689635516426d73bf6269e3f8cf5e392c
View Raw JSON Data
{
  "op": [
    "vote",
    {
      "voter": "tsto",
      "author": "eoshenzhen",
      "weight": 10000,
      "permlink": "5ggc72-or-wps"
    }
  ],
  "block": 26052982,
  "trx_id": "201ebc5689635516426d73bf6269e3f8cf5e392c",
  "op_in_trx": 0,
  "timestamp": "2018-09-18T12:57:12",
  "virtual_op": false,
  "trx_in_block": 19
}
eoshenzhenupdated payout for or-ian-dpos
2018/09/18 08:05:57
authoreoshenzhen
permlinkor-ian-dpos
Transaction InfoBlock #26047283/Virtual Operation 4294967295:8
View Raw JSON Data
{
  "op": [
    "comment_payout_update",
    {
      "author": "eoshenzhen",
      "permlink": "or-ian-dpos"
    }
  ],
  "block": 26047283,
  "trx_id": "0000000000000000000000000000000000000000",
  "op_in_trx": 8,
  "timestamp": "2018-09-18T08:05:57",
  "virtual_op": true,
  "trx_in_block": 4294967295
}
2018/09/17 07:07:24
authoreoshenzhen
permlinkor-dapp-tungsten-poc
Transaction InfoBlock #26032641/Virtual Operation 4294967295:16
View Raw JSON Data
{
  "op": [
    "comment_payout_update",
    {
      "author": "eoshenzhen",
      "permlink": "or-dapp-tungsten-poc"
    }
  ],
  "block": 26032641,
  "trx_id": "0000000000000000000000000000000000000000",
  "op_in_trx": 16,
  "timestamp": "2018-09-17T07:07:24",
  "virtual_op": true,
  "trx_in_block": 4294967295
}
eoshenzheneffective vote applied for @eoshenzhen / 5ggc72-or-wps
2018/09/17 06:50:24
votereoshenzhen
authoreoshenzhen
weight0 (0.00%)
rshares120730279
permlink5ggc72-or-wps
pending payout0.000 HBD
total vote weight11464
Transaction InfoBlock #26032301/Trx 17e83ed701c5e9f7e0620e367044d6edb6708baf
View Raw JSON Data
{
  "op": [
    "effective_comment_vote",
    {
      "voter": "eoshenzhen",
      "author": "eoshenzhen",
      "weight": 0,
      "rshares": 120730279,
      "permlink": "5ggc72-or-wps",
      "pending_payout": "0.000 HBD",
      "total_vote_weight": 11464
    }
  ],
  "block": 26032301,
  "trx_id": "17e83ed701c5e9f7e0620e367044d6edb6708baf",
  "op_in_trx": 2,
  "timestamp": "2018-09-17T06:50:24",
  "virtual_op": true,
  "trx_in_block": 18
}
2018/09/17 06:50:24
votereoshenzhen
authoreoshenzhen
weight10000 (100.00%)
permlink5ggc72-or-wps
Transaction InfoBlock #26032301/Trx 17e83ed701c5e9f7e0620e367044d6edb6708baf
View Raw JSON Data
{
  "op": [
    "vote",
    {
      "voter": "eoshenzhen",
      "author": "eoshenzhen",
      "weight": 10000,
      "permlink": "5ggc72-or-wps"
    }
  ],
  "block": 26032301,
  "trx_id": "17e83ed701c5e9f7e0620e367044d6edb6708baf",
  "op_in_trx": 1,
  "timestamp": "2018-09-17T06:50:24",
  "virtual_op": false,
  "trx_in_block": 18
}
eoshenzhenpublished a new post: 5ggc72-or-wps
2018/09/17 06:50:24
body # Emergency Committee Nominees & Alternates # 关于紧急委员被提名人和候补委员公示 作者:Chris Pollard 翻译:Yvonne ![WechatIMG330.jpeg](https://ipfs.busy.org/ipfs/Qmf3DUDLYHwnhAw3WXo92EQiGs7qr4BnutSPtg44bwC2Cy) *Land in a new territory is auctioned off in this tent (California, 1904)* *在这个帐篷里被拍卖掉的新土地(加州,1904年)* The 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. 正如目前所提提及的那样,应急委员会的目的是监督已批准的建议的进展情况、审查新的紧急或紧急议案,并监督新的治理结构建议的接受情况。要了解更多关于我们的工人提案系统计划,请阅读8月份的公告(https://medium.com/eosys/eos-worker-proposal-system-announcement-6addcfb0134c ,中文版[【公告】EOS WPS公告(WPS核心工作组)](https://busy.org/@eoshenzhen/eos-wps-wps))。 The 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: 被提名人来自社区的几个不同领域,包括现有工作组的志愿者、BP、获奖开发者和直言不讳的社区成员。选择被提名人的特点是: - A strong community presence; - Visible integrity; - Good communication skills in at least one of the three main languages; - Representative of geographical diversity; - Having an existing role as an independent thought leader; - Displaying both strongly held beliefs and an exhibited ability to change one’s mind; and, - Having a willingness to do the often difficult and thankless work. - 具有一定的社区影响力; - 诚实、可信; - 在三种主流语言之一中具有良好沟通能力; - 作为地域多样性的代表; - 在现有领域扮演领导者的角色; - 既拥有出坚定的信念,同时拥有改变别人想法的能力; 和愿意从事困难和吃力不讨好的工作。 ### Anand, Gautam ![紧急WPS11.png](https://ipfs.busy.org/ipfs/QmcRgExzm9hs7NdjmvLgZXj3P5DscAH9zHELHDKqo2ngty) Gautam 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. Gautam是一位亲力亲为的技术领导者,他从头开始构建软件项目 - 包括构建快速原型,运行开发团队,以及在管理层提供指导。他的专业知识是为Web应用程序设计和开发可扩展的解决方案(微服务架构)。他积极参与新加坡区块链开发者社区,是Blockchain Hackathons(2018)的3倍获奖者,现在为一些核心项目做出贡献。 ###nEspinoza, Branden ![紧急WPS3.png](https://ipfs.busy.org/ipfs/QmURNRzvcHQCyi1T17n4uk6jUhDFra5WZaPEfoNbMWjMDk) Branden 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. Branden是传统的国内银行到全球汇款和交易所等金融服务机构的监管和合规培训需求方面的专家(AML,CTF,BSA)。他目前正在为StrongBlock设计,记录和实施区块链治理流程,改善管理最佳实践和执行程序。 ### Kim Naeun / 김나은 / Orchid ![紧急WPS4.png](https://ipfs.busy.org/ipfs/QmVVJon3zEUPdcK1NaLtnjno3rQbCKhuktFRMMgW1J1jbz) A 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. EOSYS团队成员之一,Naeun领导EOS Evangelist Group,开展EOS研究,并与全球公司一起管理UX项目。她拥有延世大学认知科学硕士学位,HCI实验室。 ### Levine, Dan ![紧急WPS5.png](https://ipfs.busy.org/ipfs/QmTWaXrNYf738cs7NKFF7KAYjkBiW7uVdCEiufh6k4zcFj) Dan 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. 在过去的15年里Dan一直是创业者,是工程师和支持任务驱动的消费者和媒体技术平台的倡导者。在2017年初,他离开硅谷,用区块链技术全面探索社区的发展。他的热情在于社区,意识,创造力和技术。 ### Margulies, David / doghouse ![紧急WPS6.png](https://ipfs.busy.org/ipfs/QmbKEd5KroSTVCKCsf7bfdkFj3ahWqZgw3LMw8NkGqzDG6) David 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. David是一位在金融科技领域经验丰富的消费贷的高手。他主要在亚洲工作,并且在跨国界和文化的交流中有着良好的记录,并取得较好的成果。最近,他负责管理两家专注于云计算和身份管理的金融初创公司。 ### Pahalahti, Samuli / Samupaha ![紧急WPS7.png](https://ipfs.busy.org/ipfs/QmPTYAfwT5F3Sz4WW4SfDnU6zF3GFPMFADCNfbcDhwA2QV) Samuli 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. Samuli是一位自由主义活动家和区块链爱好者,他对治理、经济学和博弈论特别感兴趣。自2010年以来,他一直关注区块链的发展。 ### Shi Ricky / 施瑞琦 ![紧急WPS8.png](https://ipfs.busy.org/ipfs/QmaLKJG1wfsiMSa1MNhv1185ue7EjUczSir1iqLvqkziwd) Co-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. EOS Cannon的联合创始人、@BYSTAKE的创始人兼董事,以及胖哥说币(Chubby Boy Crytocurrency Talkshow)的创始人; 多年从事IBM Datayes担任高级技术和全栈工程师的经验。作为一名连续创业企业家,他负责监督多个网络产品的设计,开发和运营。 ### Xu Ke / 徐可 ![紧急WPS9.png](https://ipfs.busy.org/ipfs/QmWXDqmDJt6XxZpSxARaHX37rEesb4j5p79LZbdX9DzYfQ) Ke 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. 徐可是ONO和CryptoDogs的首席执行官和创始人。她是一个连续创业者,在区块链领域的经验是从作为比特币矿工开始,徐可的此前创立了ERA,这是一个拥有1000万用户的社交网络,销售给猎豹移动。曾就读于加州大学河滨分校和伦敦大学学院。 Join the WPS conversation in our public telegram channel(https://t.me/eosio_wps ). 欢迎加入WPS电报交流群(https://t.me/eosio_wps ) 本文图片来源于英文原文 *** 版权声明: 以下内容来自微信公共帐号“EOS技术爱好者”,搜索“EOSTechLover”即可订阅,翻译Yvonne。转载必须保留以上声明。仅授权原文转载。 本文原文链接为https://medium.com/wps-working-group-eos/emergency-committee-nominees-alternates-52af3dfecf2e "EOS技术爱好者"全程由EOShenzhen运营,喜欢我们请为我们投票:(EOShenzhen的投票账号:eoshenzhenio)! *** **了解更多关于EOShenzhen:** [We are EOShenzhen](https://busy.org/@eoshenzhen/we-are-eoshenzhen-eos-bp-candidate) **不同入口如何投票:** [imToken](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) [portal](https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484354&idxx=1&sn=ddd4ffdae1531385a07fad59a6e86e6e&chksm=fa0b82fecd7c0be8328a0b3a1cff7de3bef207977ab0ca829c336fb450a7ef5c4153f32d5a4f&scene=21#wechat_redirect) **关于我们更多联系:** Website:https://eoshenzhen.io Steem:https://steemit.com/@eoshenzhen Busy:https://busy.org/@eoshenzhen Telegram:https://t.me/eoshenzhen Twitter:https://twitter.com/eostechlover 简书:EOS技术爱好者 新浪微博:EOSTechLover *** **EOShenzhen的投票账号:eoshenzhenio** ![100x100-IMG_7963_small.png](https://ipfs.busy.org/ipfs/QmTdwaSQTJR15zQcr6AQUi7Wgi9z51s97DcAfhNhhN9A6c)
title【翻译|WPS】关于紧急委员被提名人和候补委员公示
authoreoshenzhen
permlink5ggc72-or-wps
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 permlinkeos
Transaction InfoBlock #26032301/Trx 17e83ed701c5e9f7e0620e367044d6edb6708baf
View Raw JSON Data
{
  "op": [
    "comment",
    {
      "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",
      "title": "【翻译|WPS】关于紧急委员被提名人和候补委员公示",
      "author": "eoshenzhen",
      "permlink": "5ggc72-or-wps",
      "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"
    }
  ],
  "block": 26032301,
  "trx_id": "17e83ed701c5e9f7e0620e367044d6edb6708baf",
  "op_in_trx": 0,
  "timestamp": "2018-09-17T06:50:24",
  "virtual_op": false,
  "trx_in_block": 18
}
ifttteffective vote applied for @eoshenzhen / v7yy2-or-ian
2018/09/17 05:44:21
voterifttt
authoreoshenzhen
weight44138
rshares6688186185
permlinkv7yy2-or-ian
pending payout0.011 HBD
total vote weight105192
Transaction InfoBlock #26030981/Trx 9019e2e06e8619855502435b02404ce3fe6d68e9
View Raw JSON Data
{
  "op": [
    "effective_comment_vote",
    {
      "voter": "ifttt",
      "author": "eoshenzhen",
      "weight": 44138,
      "rshares": 6688186185,
      "permlink": "v7yy2-or-ian",
      "pending_payout": "0.011 HBD",
      "total_vote_weight": 105192
    }
  ],
  "block": 26030981,
  "trx_id": "9019e2e06e8619855502435b02404ce3fe6d68e9",
  "op_in_trx": 1,
  "timestamp": "2018-09-17T05:44:21",
  "virtual_op": true,
  "trx_in_block": 39
}
iftttupvoted (100.00%) @eoshenzhen / v7yy2-or-ian
2018/09/17 05:44:21
voterifttt
authoreoshenzhen
weight10000 (100.00%)
permlinkv7yy2-or-ian
Transaction InfoBlock #26030981/Trx 9019e2e06e8619855502435b02404ce3fe6d68e9
View Raw JSON Data
{
  "op": [
    "vote",
    {
      "voter": "ifttt",
      "author": "eoshenzhen",
      "weight": 10000,
      "permlink": "v7yy2-or-ian"
    }
  ],
  "block": 26030981,
  "trx_id": "9019e2e06e8619855502435b02404ce3fe6d68e9",
  "op_in_trx": 0,
  "timestamp": "2018-09-17T05:44:21",
  "virtual_op": false,
  "trx_in_block": 39
}
ifttteffective vote applied for @eoshenzhen / or-wps
2018/09/17 05:44:15
voterifttt
authoreoshenzhen
weight50486
rshares6825379748
permlinkor-wps
pending payout0.009 HBD
total vote weight99892
Transaction InfoBlock #26030979/Trx 49cf2624077e6350bce11747a456a4a4ec234a2f
View Raw JSON Data
{
  "op": [
    "effective_comment_vote",
    {
      "voter": "ifttt",
      "author": "eoshenzhen",
      "weight": 50486,
      "rshares": 6825379748,
      "permlink": "or-wps",
      "pending_payout": "0.009 HBD",
      "total_vote_weight": 99892
    }
  ],
  "block": 26030979,
  "trx_id": "49cf2624077e6350bce11747a456a4a4ec234a2f",
  "op_in_trx": 1,
  "timestamp": "2018-09-17T05:44:15",
  "virtual_op": true,
  "trx_in_block": 4
}
iftttupvoted (100.00%) @eoshenzhen / or-wps
2018/09/17 05:44:15
voterifttt
authoreoshenzhen
weight10000 (100.00%)
permlinkor-wps
Transaction InfoBlock #26030979/Trx 49cf2624077e6350bce11747a456a4a4ec234a2f
View Raw JSON Data
{
  "op": [
    "vote",
    {
      "voter": "ifttt",
      "author": "eoshenzhen",
      "weight": 10000,
      "permlink": "or-wps"
    }
  ],
  "block": 26030979,
  "trx_id": "49cf2624077e6350bce11747a456a4a4ec234a2f",
  "op_in_trx": 0,
  "timestamp": "2018-09-17T05:44:15",
  "virtual_op": false,
  "trx_in_block": 4
}
sensationeffective vote applied for @eoshenzhen / v7yy2-or-ian
2018/09/17 04:53:03
votersensation
authoreoshenzhen
weight2567 (25.67%)
rshares336409041
permlinkv7yy2-or-ian
pending payout0.003 HBD
total vote weight61054
Transaction InfoBlock #26029955/Trx 74b39c011e5142965cc38fcdcf11e739d3435956
View Raw JSON Data
{
  "op": [
    "effective_comment_vote",
    {
      "voter": "sensation",
      "author": "eoshenzhen",
      "weight": 2567,
      "rshares": 336409041,
      "permlink": "v7yy2-or-ian",
      "pending_payout": "0.003 HBD",
      "total_vote_weight": 61054
    }
  ],
  "block": 26029955,
  "trx_id": "74b39c011e5142965cc38fcdcf11e739d3435956",
  "op_in_trx": 1,
  "timestamp": "2018-09-17T04:53:03",
  "virtual_op": true,
  "trx_in_block": 3
}
2018/09/17 04:53:03
votersensation
authoreoshenzhen
weight10000 (100.00%)
permlinkv7yy2-or-ian
Transaction InfoBlock #26029955/Trx 74b39c011e5142965cc38fcdcf11e739d3435956
View Raw JSON Data
{
  "op": [
    "vote",
    {
      "voter": "sensation",
      "author": "eoshenzhen",
      "weight": 10000,
      "permlink": "v7yy2-or-ian"
    }
  ],
  "block": 26029955,
  "trx_id": "74b39c011e5142965cc38fcdcf11e739d3435956",
  "op_in_trx": 0,
  "timestamp": "2018-09-17T04:53:03",
  "virtual_op": false,
  "trx_in_block": 3
}
eoshenzhenpublished a new post: or-wps
2018/09/17 04:31:21
body@@ -1,24 +1,26 @@ +# Worker Proposal City %0A%0A%E5%B7%A5 @@ -18,16 +18,18 @@ City %0A%0A +# %E5%B7%A5%E4%BD%9C%E8%80%85%E6%8F%90%E6%A1%88%E5%9F%8E%E5%B8%82%0A @@ -31,16 +31,17 @@ %E6%8F%90%E6%A1%88%E5%9F%8E%E5%B8%82%0A%0A%0A%0A +* %E4%BD%9C%E8%80%85%EF%BC%9ADavid @@ -50,18 +50,20 @@ argulies +* %0A%0A +* %E7%BF%BB%E8%AF%91%EF%BC%9ALocha @@ -68,16 +68,17 @@ haiching +* %0A%0A%0A%0AA gr
title【翻译|WPS】工作者提案城市
authoreoshenzhen
permlinkor-wps
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 permlinkwps
Transaction InfoBlock #26029521/Trx 55af6a5464c65f843a45390f42d230a6766c11d6
View Raw JSON Data
{
  "op": [
    "comment",
    {
      "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",
      "title": "【翻译|WPS】工作者提案城市",
      "author": "eoshenzhen",
      "permlink": "or-wps",
      "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"
    }
  ],
  "block": 26029521,
  "trx_id": "55af6a5464c65f843a45390f42d230a6766c11d6",
  "op_in_trx": 0,
  "timestamp": "2018-09-17T04:31:21",
  "virtual_op": false,
  "trx_in_block": 29
}
2018/09/17 04:28:39
bodyHi! I am a robot. I just upvoted you! I found similar content that readers might be interested in: https://medium.com/wps-working-group-eos/worker-proposal-city-24dd35527ed8
title
authorcheetah
permlinkcheetah-re-eoshenzhenor-wps
json metadata
parent authoreoshenzhen
parent permlinkor-wps
Transaction InfoBlock #26029467/Trx 95415cf24e919a7cf8d3d188127fa8d02d3ce25b
View Raw JSON Data
{
  "op": [
    "comment",
    {
      "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",
      "title": "",
      "author": "cheetah",
      "permlink": "cheetah-re-eoshenzhenor-wps",
      "json_metadata": "",
      "parent_author": "eoshenzhen",
      "parent_permlink": "or-wps"
    }
  ],
  "block": 26029467,
  "trx_id": "95415cf24e919a7cf8d3d188127fa8d02d3ce25b",
  "op_in_trx": 0,
  "timestamp": "2018-09-17T04:28:39",
  "virtual_op": false,
  "trx_in_block": 9
}
cheetaheffective vote applied for @eoshenzhen / or-wps
2018/09/17 04:28:33
votercheetah
authoreoshenzhen
weight126 (1.26%)
rshares2060123461
permlinkor-wps
pending payout0.002 HBD
total vote weight49406
Transaction InfoBlock #26029465/Trx 1efcd47baed04c133aaa208407b27fe74c597454
View Raw JSON Data
{
  "op": [
    "effective_comment_vote",
    {
      "voter": "cheetah",
      "author": "eoshenzhen",
      "weight": 126,
      "rshares": 2060123461,
      "permlink": "or-wps",
      "pending_payout": "0.002 HBD",
      "total_vote_weight": 49406
    }
  ],
  "block": 26029465,
  "trx_id": "1efcd47baed04c133aaa208407b27fe74c597454",
  "op_in_trx": 1,
  "timestamp": "2018-09-17T04:28:33",
  "virtual_op": true,
  "trx_in_block": 18
}
cheetahupvoted (0.08%) @eoshenzhen / or-wps
2018/09/17 04:28:33
votercheetah
authoreoshenzhen
weight8 (0.08%)
permlinkor-wps
Transaction InfoBlock #26029465/Trx 1efcd47baed04c133aaa208407b27fe74c597454
View Raw JSON Data
{
  "op": [
    "vote",
    {
      "voter": "cheetah",
      "author": "eoshenzhen",
      "weight": 8,
      "permlink": "or-wps"
    }
  ],
  "block": 26029465,
  "trx_id": "1efcd47baed04c133aaa208407b27fe74c597454",
  "op_in_trx": 0,
  "timestamp": "2018-09-17T04:28:33",
  "virtual_op": false,
  "trx_in_block": 18
}
eoshenzheneffective vote applied for @eoshenzhen / or-wps
2018/09/17 04:28:27
votereoshenzhen
authoreoshenzhen
weight0 (0.00%)
rshares120730279
permlinkor-wps
pending payout0.000 HBD
total vote weight11464
Transaction InfoBlock #26029463/Trx db2c3167d805f000b39e327f1bde6fe91b45ba09
View Raw JSON Data
{
  "op": [
    "effective_comment_vote",
    {
      "voter": "eoshenzhen",
      "author": "eoshenzhen",
      "weight": 0,
      "rshares": 120730279,
      "permlink": "or-wps",
      "pending_payout": "0.000 HBD",
      "total_vote_weight": 11464
    }
  ],
  "block": 26029463,
  "trx_id": "db2c3167d805f000b39e327f1bde6fe91b45ba09",
  "op_in_trx": 2,
  "timestamp": "2018-09-17T04:28:27",
  "virtual_op": true,
  "trx_in_block": 9
}
eoshenzhenupvoted (100.00%) @eoshenzhen / or-wps
2018/09/17 04:28:27
votereoshenzhen
authoreoshenzhen
weight10000 (100.00%)
permlinkor-wps
Transaction InfoBlock #26029463/Trx db2c3167d805f000b39e327f1bde6fe91b45ba09
View Raw JSON Data
{
  "op": [
    "vote",
    {
      "voter": "eoshenzhen",
      "author": "eoshenzhen",
      "weight": 10000,
      "permlink": "or-wps"
    }
  ],
  "block": 26029463,
  "trx_id": "db2c3167d805f000b39e327f1bde6fe91b45ba09",
  "op_in_trx": 1,
  "timestamp": "2018-09-17T04:28:27",
  "virtual_op": false,
  "trx_in_block": 9
}
eoshenzhenpublished a new post: or-wps
2018/09/17 04:28:27
bodyWorker Proposal City 工作者提案城市 作者:David Margulies 翻译:Lochaiching A graphic metaphor by David Margulies and Chris Pollard. Both are members of the EOS WPS working group. 本文描绘的一个想象社区的构造,想法来自于David Margulies和Chris Pollard,以上两者都是EOS WPS工作组的成员。 In the beginning there was the EOS blockchain. There were block producers and token holders. For most, conditions were harsh and life was uncertain. ![WPC1.jpeg](https://ipfs.busy.org/ipfs/QmTnUfadAGhxV48s4WrtQTTVDhnteqd62Ntpc1zTzuYoTB) 一开始的EOS区块链中有BP和token持有者。对大多数人来说,整个环境可能是不尽如意的、不确定的。 The Worker Proposal System (WPS) Group formed, with the aim to help transform EOS into a city that the owners would be proud of. WPS组织成立的目的,是为了让EOS变成一个持有者会感到自豪的城市。 ![WPC2.png](https://ipfs.busy.org/ipfs/QmPEBLSNECUGT5o96w251tFHL2Rm9v9hNsxnzQiwk5bwPT) The 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. 第一项任务是购买土地,从一小片土地开始。EOS的token将有助于资金的转入转出。 ![WPC3.png](https://ipfs.busy.org/ipfs/QmWK8R989NBnAa4erwdKV6R6auBXrymhUhaXSts6wkLsZN) The construction trailer was setup, where the Emergency Committee started work in supporting the urgent works. 施工拖车已安装完毕,同时应急委员会已经可以开始紧急事务的处理了。 ![WPC4.png](https://ipfs.busy.org/ipfs/QmR9f38zEc4Qjp2dPDGMQbmLrPu3BBiXSGDLKSwz1M5yQt) The underground plumbing and the electricity grids were constructed. This core infrastructure included emergency needs like ECAF funding and code repository management. 同时社区也修建了地下管道和电网这些核心基础设施,其中包括紧急需求,如ECAF资金和代码存储库管理。 ![WPC5.png](https://ipfs.busy.org/ipfs/QmSPjh1nBRgZwDaRDRaJLxXNP3Z5d7ioCuqAcsvQ6A5584) The zoning began. The Emergency Committee went about staking plots of land for each neighbourhood. 这个时候开始分区了。紧急事务委员会着手为每一片居民区划清界限并规划地区。 ![WPC6.png](https://ipfs.busy.org/ipfs/QmUKnkmXadhK9K15EuUWVHipGGyaFDVkP7AsvHDnsvoxuz) A 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. 这个时候举办了一场全球性的竞赛,任何个人或团队都可以提交关于社区的设计方案。比如这一次,是为了新的工作类别构建最佳治理设计的公开呼吁。 Each time a winning team was voted by the community, the neighbourhood was born, with an ownership of 10% of the city’s land. 每次都由社区投票选出获胜的队伍,这也意味着诞生了一个拥有城市10%面积份额的社区。 The Neighbourhoods The 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. 社区一带 监督这一层的社区就像是现在的市政厅。这是其他社区工程被监督的地方,也是WPS能够持续的原因。 ![WPC7.png](https://ipfs.busy.org/ipfs/QmVddg2xrzy8gUpEU8QTijgmubNw8DerkVDbutDNhDam3Y) The 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. 社区基础设施这一层就像现在的公共工程部门。这是工作肮脏、没有赞美的地方,是我们保持底层代码基础健康的地方,也是安全审计和bug修复的地方。 ![WPC8.png](https://ipfs.busy.org/ipfs/QmWDsU4f3skt65VoA1T5xGosRWaZxrq3eJHkNQNPSojfRW) The 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. 社区这一层就像公园、学校和旅游景点。这一层的社区支持线下聚会、教育、资源和空间共享来加强整个社区的连接。 ![WPC9.png](https://ipfs.busy.org/ipfs/QmRUjN6ggiRAbsU1djvNy3G6fR1bWm784Wmncq4KiHBTiy) The Developer neighbourhood is like the light industrial district. It is for supporting developers and ideas that will enrich the community. 开发者这一层就像轻工业园区。它的存在是为了支持开发者和各种想法,这将丰富社区元素。 The 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. ![WPC10.png](https://ipfs.busy.org/ipfs/QmUh8kBffkJ9M19obRJVvMoA7fXxsf1UNuBYNqmhSE3AsG) 杂七杂八这一层就像艺术家的阁楼和重新利用的空间,这一层是为可能不适合其他分类的项目而建的。 本文图片来源于英文原文 *** 版权声明: 以下内容来自微信公共帐号“EOS技术爱好者”,搜索“EOSTechLover”即可订阅,翻译Lochaiching。转载必须保留以上声明。仅授权原文转载。 本文原文链接为https://medium.com/wps-working-group-eos/worker-proposal-city-24dd35527ed8 "EOS技术爱好者"全程由EOShenzhen运营,喜欢我们请为我们投票:(EOShenzhen的投票账号:eoshenzhenio)! *** **了解更多关于EOShenzhen:** [We are EOShenzhen](https://busy.org/@eoshenzhen/we-are-eoshenzhen-eos-bp-candidate) **不同入口如何投票:** [imToken](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) [portal](https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484354&idxx=1&sn=ddd4ffdae1531385a07fad59a6e86e6e&chksm=fa0b82fecd7c0be8328a0b3a1cff7de3bef207977ab0ca829c336fb450a7ef5c4153f32d5a4f&scene=21#wechat_redirect) **关于我们更多联系:** Website:https://eoshenzhen.io Steem:https://steemit.com/@eoshenzhen Busy:https://busy.org/@eoshenzhen Telegram:https://t.me/eoshenzhen Twitter:https://twitter.com/eostechlover 简书:EOS技术爱好者 新浪微博:EOSTechLover *** **EOShenzhen的投票账号:eoshenzhenio** ![100x100-IMG_7963_small.png](https://ipfs.busy.org/ipfs/QmTdwaSQTJR15zQcr6AQUi7Wgi9z51s97DcAfhNhhN9A6c)
title【翻译|WPS】工作者提案城市
authoreoshenzhen
permlinkor-wps
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 permlinkwps
Transaction InfoBlock #26029463/Trx db2c3167d805f000b39e327f1bde6fe91b45ba09
View Raw JSON Data
{
  "op": [
    "comment",
    {
      "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",
      "title": "【翻译|WPS】工作者提案城市",
      "author": "eoshenzhen",
      "permlink": "or-wps",
      "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"
    }
  ],
  "block": 26029463,
  "trx_id": "db2c3167d805f000b39e327f1bde6fe91b45ba09",
  "op_in_trx": 0,
  "timestamp": "2018-09-17T04:28:27",
  "virtual_op": false,
  "trx_in_block": 9
}
tstoeffective vote applied for @eoshenzhen / v7yy2-or-ian
2018/09/17 04:21:27
votertsto
authoreoshenzhen
weight1738 (17.38%)
rshares1477243471
permlinkv7yy2-or-ian
pending payout0.003 HBD
total vote weight58487
Transaction InfoBlock #26029323/Trx 0b4098c2b5241d9811bb68f1d168882f78f2a7fb
View Raw JSON Data
{
  "op": [
    "effective_comment_vote",
    {
      "voter": "tsto",
      "author": "eoshenzhen",
      "weight": 1738,
      "rshares": 1477243471,
      "permlink": "v7yy2-or-ian",
      "pending_payout": "0.003 HBD",
      "total_vote_weight": 58487
    }
  ],
  "block": 26029323,
  "trx_id": "0b4098c2b5241d9811bb68f1d168882f78f2a7fb",
  "op_in_trx": 1,
  "timestamp": "2018-09-17T04:21:27",
  "virtual_op": true,
  "trx_in_block": 15
}
tstoupvoted (100.00%) @eoshenzhen / v7yy2-or-ian
2018/09/17 04:21:27
votertsto
authoreoshenzhen
weight10000 (100.00%)
permlinkv7yy2-or-ian
Transaction InfoBlock #26029323/Trx 0b4098c2b5241d9811bb68f1d168882f78f2a7fb
View Raw JSON Data
{
  "op": [
    "vote",
    {
      "voter": "tsto",
      "author": "eoshenzhen",
      "weight": 10000,
      "permlink": "v7yy2-or-ian"
    }
  ],
  "block": 26029323,
  "trx_id": "0b4098c2b5241d9811bb68f1d168882f78f2a7fb",
  "op_in_trx": 0,
  "timestamp": "2018-09-17T04:21:27",
  "virtual_op": false,
  "trx_in_block": 15
}
satyadeveffective vote applied for @eoshenzhen / v7yy2-or-ian
2018/09/17 04:19:06
votersatyadev
authoreoshenzhen
weight483 (4.83%)
rshares594517932
permlinkv7yy2-or-ian
pending payout0.002 HBD
total vote weight45282
Transaction InfoBlock #26029276/Trx df034c34539611bce08cfec0f35f979f297d5939
View Raw JSON Data
{
  "op": [
    "effective_comment_vote",
    {
      "voter": "satyadev",
      "author": "eoshenzhen",
      "weight": 483,
      "rshares": 594517932,
      "permlink": "v7yy2-or-ian",
      "pending_payout": "0.002 HBD",
      "total_vote_weight": 45282
    }
  ],
  "block": 26029276,
  "trx_id": "df034c34539611bce08cfec0f35f979f297d5939",
  "op_in_trx": 1,
  "timestamp": "2018-09-17T04:19:06",
  "virtual_op": true,
  "trx_in_block": 15
}
satyadevupvoted (100.00%) @eoshenzhen / v7yy2-or-ian
2018/09/17 04:19:06
votersatyadev
authoreoshenzhen
weight10000 (100.00%)
permlinkv7yy2-or-ian
Transaction InfoBlock #26029276/Trx df034c34539611bce08cfec0f35f979f297d5939
View Raw JSON Data
{
  "op": [
    "vote",
    {
      "voter": "satyadev",
      "author": "eoshenzhen",
      "weight": 10000,
      "permlink": "v7yy2-or-ian"
    }
  ],
  "block": 26029276,
  "trx_id": "df034c34539611bce08cfec0f35f979f297d5939",
  "op_in_trx": 0,
  "timestamp": "2018-09-17T04:19:06",
  "virtual_op": false,
  "trx_in_block": 15
}
2018/09/17 04:17:39
body @eoshenzhen, I gave you a vote!<br>If you follow me, I will also follow you in return!
title
authorintroduce.bot
permlinkintroduce-bot-re-eoshenzhenv7yy2-or-ian
json metadata
parent authoreoshenzhen
parent permlinkv7yy2-or-ian
Transaction InfoBlock #26029247/Trx c8a2677c69fd7c09a95d52c64706ee3a7fdad8fb
View Raw JSON Data
{
  "op": [
    "comment",
    {
      "body": " @eoshenzhen, I gave you a vote!<br>If you follow me, I will also follow you in return!",
      "title": "",
      "author": "introduce.bot",
      "permlink": "introduce-bot-re-eoshenzhenv7yy2-or-ian",
      "json_metadata": "",
      "parent_author": "eoshenzhen",
      "parent_permlink": "v7yy2-or-ian"
    }
  ],
  "block": 26029247,
  "trx_id": "c8a2677c69fd7c09a95d52c64706ee3a7fdad8fb",
  "op_in_trx": 0,
  "timestamp": "2018-09-17T04:17:39",
  "virtual_op": false,
  "trx_in_block": 20
}
introduce.boteffective vote applied for @eoshenzhen / v7yy2-or-ian
2018/09/17 04:17:39
voterintroduce.bot
authoreoshenzhen
weight123 (1.23%)
rshares1176786798
permlinkv7yy2-or-ian
pending payout0.001 HBD
total vote weight36210
Transaction InfoBlock #26029247/Trx 256520be57214327da6a613fd2f8dba242dee659
View Raw JSON Data
{
  "op": [
    "effective_comment_vote",
    {
      "voter": "introduce.bot",
      "author": "eoshenzhen",
      "weight": 123,
      "rshares": 1176786798,
      "permlink": "v7yy2-or-ian",
      "pending_payout": "0.001 HBD",
      "total_vote_weight": 36210
    }
  ],
  "block": 26029247,
  "trx_id": "256520be57214327da6a613fd2f8dba242dee659",
  "op_in_trx": 1,
  "timestamp": "2018-09-17T04:17:39",
  "virtual_op": true,
  "trx_in_block": 8
}
2018/09/17 04:17:39
voterintroduce.bot
authoreoshenzhen
weight100 (1.00%)
permlinkv7yy2-or-ian
Transaction InfoBlock #26029247/Trx 256520be57214327da6a613fd2f8dba242dee659
View Raw JSON Data
{
  "op": [
    "vote",
    {
      "voter": "introduce.bot",
      "author": "eoshenzhen",
      "weight": 100,
      "permlink": "v7yy2-or-ian"
    }
  ],
  "block": 26029247,
  "trx_id": "256520be57214327da6a613fd2f8dba242dee659",
  "op_in_trx": 0,
  "timestamp": "2018-09-17T04:17:39",
  "virtual_op": false,
  "trx_in_block": 8
}
eoshenzheneffective vote applied for @eoshenzhen / v7yy2-or-ian
2018/09/17 04:17:30
votereoshenzhen
authoreoshenzhen
weight0 (0.00%)
rshares122568811
permlinkv7yy2-or-ian
pending payout0.000 HBD
total vote weight11577
Transaction InfoBlock #26029244/Trx d5049e782f251b5b1b24fa24d7548634620dc2af
View Raw JSON Data
{
  "op": [
    "effective_comment_vote",
    {
      "voter": "eoshenzhen",
      "author": "eoshenzhen",
      "weight": 0,
      "rshares": 122568811,
      "permlink": "v7yy2-or-ian",
      "pending_payout": "0.000 HBD",
      "total_vote_weight": 11577
    }
  ],
  "block": 26029244,
  "trx_id": "d5049e782f251b5b1b24fa24d7548634620dc2af",
  "op_in_trx": 2,
  "timestamp": "2018-09-17T04:17:30",
  "virtual_op": true,
  "trx_in_block": 9
}
2018/09/17 04:17:30
votereoshenzhen
authoreoshenzhen
weight10000 (100.00%)
permlinkv7yy2-or-ian
Transaction InfoBlock #26029244/Trx d5049e782f251b5b1b24fa24d7548634620dc2af
View Raw JSON Data
{
  "op": [
    "vote",
    {
      "voter": "eoshenzhen",
      "author": "eoshenzhen",
      "weight": 10000,
      "permlink": "v7yy2-or-ian"
    }
  ],
  "block": 26029244,
  "trx_id": "d5049e782f251b5b1b24fa24d7548634620dc2af",
  "op_in_trx": 1,
  "timestamp": "2018-09-17T04:17:30",
  "virtual_op": false,
  "trx_in_block": 9
}
eoshenzhenpublished a new post: v7yy2-or-ian
2018/09/17 04:17:30
body# The Message is the Medium # 信息就是中介 作者:Ian Grigg 翻译:Gavin 校对:Lochaiching ## A Preliminary Message ## 初步信息 This 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. 这篇文章介绍了我认为几乎所有区块链设计中都存在的一个基本缺陷。简而言之,当我们使用消息来构建时,强调将state作为“核心元素”。这其中的影响是相当巨大的,但也很难理解,因为计算机科学的概念对not-CS世界来说有点难以理解。 What 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. 接下里是一个非正式的、非严格的描述,试图向一些非该专业领域的读者解释消息和state的区别。我试着以简单的方式来引导大家理解它,但是如果你发现自己还是处在一种混乱的状态下,这有另一种理解它的方法那就是关注进一步的进展——我们要建立它,这样信息就会被放到媒介上。有点糟糕的比喻,让我们继续吧。 ## What’s a State Machine, anyway? ## 所以什么是状态机 A 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. ![ian消息媒介1.png](https://ipfs.busy.org/ipfs/QmbXQCiNWPGGSWun8WB9A9ncshoGsW6DAY6V3jqGEyh5cM) 状态机是一种计算机科学发明(https://busy.org/exit?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FFinite-state_machine) ,用于捕获可靠的、具有确定性信息的机器。 简而言之,它是一个软件“机器”,它被给与一系列输入和内存,总是提供相同的输出。 Think 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!). 想想一台自动售货机,以及内部的软件,它必须模拟外部硬件,以便确定下一步该做什么。 换句话说,“如果我们处于状态1,就是等待投入硬币。 如果硬币投进来,就转换到状态2。如果处于状态2,就是等待按钮按下。 如果一个按钮按下,提供饮料,转到状态1。”从本质上说,我们的机器包含一些代码来处理该算法,一些state(内存)来存储我们的状态,以及读取传入消息( 硬币,按钮)和做出一些行为作为输出消息(饮料!)的能力。 *Figure 2 - a coke machine .png(编辑部:图挂了)* We 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. 我们还可以用较小的状态机构建更大的状态机 - 数据库本质上是一个巨大的状态机,由每个SQL表的每行和每个单元作为多个小的状态机构成的。 协议是由两台状态机组成的小型状态机 - 每端一台。 区块链是另一个巨大的状态机,由数千个“全节点”状态机组成,其中有许多挂机,称为SPV客户端。 虽然状态机设计的本质非常简单,但使用它们既是一门科学又是一门艺术,因为我们对如何将小型状态机组成大型状态机没有很深入的了解。 我们暂时不考虑这种复杂性。 ## Choice ## 选择 It turns out that there are two fundamental approaches to building a state machine. 事实证明,构建状态机有两种基本方法。 Note, 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. ![ian消息媒介3.png](https://ipfs.busy.org/ipfs/QmTcJMyPC43TSUwjo94BLG7e4kLJ2P1mHit7vwqDmXWyM2) 请注意,以下是一个非常风格化的观点,而不是严谨的观点。 我们忽略上面的代码,并假设它在需要的地方被引用。 为简单起见,我们也忽略了输出消息。我们的目标是让普通人了解消息,而不是给CS极客们留下深刻印象。 We 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. 我们通常以上述方式对状态机进行建模 - 它从状态1开始,然后到达消息1。处理此消息会导致从状态1转换到状态2。 在转换到状态1时,机器发出消息,尽管这是非常严格并且可选的 – 但它还是取决于机器在该转换时的需求。 Our 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. 我们构建状态机的工作是编写代码来实现存储和转换所有已知信息的状态。 事实证明,在完成这项工作时,有两种根本不同的方式来编写机器,以及选择哪种取决于我们的思维、设计和能力。 >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. >第一种方法:把它看作是一种状态的机器。在这个视图中,我们存储状态1。然后,当消息到达时,机器转到状态2,然后存储这个新状态。重复这个循环,把这些状态想象成上面的蓝色圆圈,你就可以忽略任何其他的世界角度。 >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. >第二种方法:把它看作是信息的机器。在这个备用视图中,我们记录消息,并且总是在状态1的时候启动机器。然后,我们将所有需要输入的信息(上面的红色药丸)输入到机器(并弹出任何新的信息)中。我们存储信息,但不关心状态,因为有了信息之后我们可以随时计算出状态的情况。 These 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). 这些观点在理论上大多相同,理解这一点的关键是“机器是确定性的”。 一旦我们确定机器在其动作中是精确且无情的,我们就知道例如状态1上的M1总是导致State2(和M2输出)。 Then, 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. 然后,如果我们有机器,并且我们有一组消息,就可以再次滚动它以获得状态。**或者**,如果我们记录了状态,我们总是可以根据一系列状态的转换来重现action,尽管我们不一定知道哪些消息导致了这一状态转换。 如果你喜欢图形学,你可以想一下以节点存储**和**以边存储的区别。 We 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. 我们可以选择如何思考问题。 而且,根据我们的愿望和假设,可能会更喜欢这样或那样的方式:数据库被视为状态机器,就像灯开关一样 - 它知道它是打开还是关闭,但不知道它是怎样到了现在的位置。 而协议通常被认为更像是消息机器; 考虑一个电子邮件交换,其中最后一条消息没有告诉你所有的故事,如果它已经持续了一段时间,你可能必须扫描线程中的所有之前的消息来弄清楚发生了什么。 *photo.png(编辑部:图又挂了)* ## Wheretofore the machinery of blockchain? ## 区块链的机器在哪里 That’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. 这是理论上的 - 实践可能会有所不同。 你的网上银行帐户被看做是一台状态机,并告知你余额。 但在银行内部,使用双重输入运算使其更像是一种信息机器。 What should blockchain do? 区块链应该怎么做呢? For 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: 由于可能是历史性的原因,或者因为设计师以这种方式思考更典型,因此区块链被视为状态机器,而不是消息机器: >… 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. >(my emphasis) LM Goodman, “Tezos: A Self-Amending Crypto-Ledger Position Paper(https://tezos.com/static/papers/position_paper.pdf)”, 2013 Or, from a recent Ethereum replacement project: 或者,来自一个最近的Ethereum项目: >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. Messages 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”. Message 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. (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 Note how the author above has established everything we need to store the message as transaction, and then fallen back to blockchain canon of state. 请注意上面的作者如何建立将消息存储为交易所需的一切,然后再回到区块链状态。 If 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: 如果我们再看一下图4中的比特币状态机的另一个例子,我们可以看到这个状态视图在UTXO模型中特别强调,它将交易分组为Unspent Transaction Outputs(“UTXO”)的集合。 交易是包含输入和输出的状态记录。 与上面的图3相比,考虑每个记录中的两个蓝色圆圈,但没有消息。 通常,每个UTXO交易都表示为一个框,左侧是输入列,右侧是输出,图4: ![ian消息媒介4.png](https://ipfs.busy.org/ipfs/QmWgHi8rHdtEd5pJtzW6a3xQeXCMYCQNGu7ZgWBWJWwd2s) On 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. 在每个交易的输入(左)侧是先前交易的输出或“硬币”的引用列表,通过这样的方式,确认硬币存在,然后花掉它,并且在输出(右)侧是另一个匹配的新硬币列表,通过这种方式,确认它们现在已经被创造出来并在将来可以被消费。 在上面,“交易1”创建0.5个BTC作为输出,“交易2”通过引用它作为输入来花费0.5个BTC。 The 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. 比特币交易记录,作为输入和输出的记录,就像一个微型资产负债表; 输入与输出匹配。 对于具有视觉意识的人来说,这些交易记录中的每一个都像乐高方块一样,新的必须覆盖旧的,并提供更新的以便在将来可以覆盖掉它们。 ## The Brittleness of the UTXO ## UTXO的脆弱性 Now, 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: 现在,它之前已经被察觉到,但有必要复述一下:比特币具有非凡的设计,但其中一个方面是所有组件都以非常依赖的方式彼此紧密相连。 正如它所说: >“ 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. ” Satoshi Nakamoto, “Bitcoin: A Peer-to-Peer Electronic Cash System(https://bitcoin.org/bitcoin.pdf) ” 2008. The 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. 任务是货币,但货币也是安全模型的驱动力,通过支付矿工竞争验证。 内部依赖的这个强大部分确实存在一个缺点 - 在架构方面它很脆弱。 通过这种方式,我并不是说比特币随时都会崩溃,而是如果我们改变一个设计元素,它就会威胁整个构造的神圣性。 And 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. 这就是UTXO。 如上所述,比特币的使命是为一种货币。每个(全)节点都需要拥有可用资金的每一条记录,因此它可以验证每个传入的交易,并继续将交易分发到其适合的采集区块中。 相比之下,SPV或远程客户端需要有一种简单的方法来证明其输入的币的组成部分,以保证不会拖累整个链。 These 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. 这两个请求是冲突的。 由于比特币这样的大型链中有很多记录,因此UTXO布局是一种优雅的设计,在其他影响的情况下以合理的效率满足这些要求。 它非常擅长提供客户在某个时间点需要的证据。 ## An Order Book ## 订单薄 But 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. Figure 5. 但是当需求发生变化时,UTXO会发生什么? 假设我们想做交易。 出于各种原因,最好的方法是将所有人聚集在一起,构建一个订单簿 – 要求购买的出价列表与要出售的标价列表 - 然后进行拍卖结算流程以找到所有交易者的最佳价格。 当然还有其他方式,但这既是经过时间考验的方式,也是加强交流的方式。 图5 ![ian消息媒介5.jpeg](https://ipfs.busy.org/ipfs/QmYmKNSe7zEuJn5PUHceAV3m9cvnMz9RoyyS7EjSUNNtv8) In 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! 在UTXO状态机中聚集在一起时,我们是不知道想要竞标买家的地位有多少,也不知道卖方的人数有多少。 UTXO设计过程中不能轻易地完成这种设想,原因有两个:1,竞争一个结果的许多未知因素的相互作用无法扩展,因为整个布局需要动态协商 - 输入、输出和价格! - 在竞争交易者之间; 2,交易是信息敏感的 - 交易者一旦发现你坐上买家的地位就会想办法退出谈判并使你崩溃。 这是一个根本的矛盾! A 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. 消息流可以轻松处理这个难题。 如果区块链中间人(PoW设计中的矿工,或DPOS中的生产者)收到一系列稳定的出价和报价信息,他只需按顺序收集它们并将它们交给内部构建订单薄的“书面合约”,然后决定交换价格,并发出新的确认合约的消息结果。 *Figure 6 - the Red Pill Trading Book of Messages.png(编辑部:图挂了again)* The 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. 消息被记录,但状态(例如,UTXO)是隐含的,这意味着它由计算机内部构建,然后(可以)被丢弃。 只要区块链决定了严格的消息集 - 消息和按什么顺序 - 结果是确定性的,因为每个其他节点为每组相同的输入消息运行相同的合约,并且同意输出消息。 Two 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. 还有两个优点:如果在这个区块中丢弃了任何传入的交易,它们可以简单地被推迟到下一个区块。 这是因为传入的消息无论什么时候进行交易都是具有独立意图的,而构成UTXO状态的输入和输出更多地受制于它们的依赖集合的一部分,这些集合现在应该在该交易中发生。 Secondly. 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. 其次。 这个结构捕获了交易账户的更多问题。也就是说,当你想与我交易,或者我和你交易时,我们都将我们的买入/卖出作为信息写入并发送给它。困难的部分是在合约里面完成的。 完整的合约作者在他的设计中已经涵盖了这一点。 相比之下,使用UTXO构造,你和我必须在图5中展示蓝框,同意所有内容,签字然后提交以达成共识。 UTXO给交易员带来了困难的部分,而将简单的部分 - 记录事实 - 留给了链。 As an exercise, you might like to examine how you would handle fees in both designs. 作为练习,你可能想要了解如何处理两种设计中的费用。 ## Slight Demurral ## 小小异议 It’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. 它并非都是单向的 - 状态模型具有更快地捕获错误的好处。每个交易必须在其记录状态下完全一致,而不仅仅是让我们在那里的消息。 这种快速捕获错误的能力可被视为交易对账的主要优势,银行业正在考虑降低成本和降低运营风险。 But even this could be a choice of risks - when a bug turns up in a blockchain, the chain quickly breaks and forks. 但即使这样也可能是有风险的选择 - 当区块链中出现bug的时候,链会迅速断裂和分叉。 Everything 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. 当节点冲突和哈希时,一切都停止了。 当bug出现在消息模型链中时,该bug是隐含的,并且在很大程度上会在各方之间产生关于消息含义的争议。 受影响的人可以将其变为脱机状态; 包括,我们可以缓存证据来离线观看问题,或者交换。 ## Conclusion ## 总结 The 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. 为了构建功能广泛的区块链,消息传递模型有许多优于状态模型的原因。 这并不是一个单一的方式 - 状态模型有更快地捕获中断的好处。 A 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 :-) 一个更全面的帖子会列出所有的优点和缺点,但是现在,我们只会召集一个主要专业人士。 除了上述示例的灵活性之外,消息传递链可以达到更高的性能。 例如,@ danthemamn的Bitshares和Steem都是建立在这个模型上的,并且每秒显示1000次交易。 和我的Ricardo系统一样,虽然是非区块链,但它解释了为什么我这么喜欢:-) On 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, >the message is the medium. 至少在理论上,这种方法可以提供更高的性能,你可以看到EOS也将以这种方式构建的暗示! 事实上,正是这些系统的速度需要导致设计师@dantheman和我自己发现,向Marshall McLuhan道歉: >信息是一切中介。 本文图片来源于英文原文 *** 版权声明: 以下内容来自微信公共帐号“EOS技术爱好者”,搜索“EOSTechLover”即可订阅,翻译Gavin,校对Lochaiching。转载必须保留以上声明。仅授权原文转载。 本文原文链接为https://busy.org/@iang/the-message-is-the-medium "EOS技术爱好者"全程由EOShenzhen运营,喜欢我们请为我们投票:(EOShenzhen的投票账号:eoshenzhenio)! *** **了解更多关于EOShenzhen:** [We are EOShenzhen](https://busy.org/@eoshenzhen/we-are-eoshenzhen-eos-bp-candidate) **不同入口如何投票:** [imToken](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) [portal](https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484354&idxx=1&sn=ddd4ffdae1531385a07fad59a6e86e6e&chksm=fa0b82fecd7c0be8328a0b3a1cff7de3bef207977ab0ca829c336fb450a7ef5c4153f32d5a4f&scene=21#wechat_redirect) **关于我们更多联系:** Website:https://eoshenzhen.io Steem:https://steemit.com/@eoshenzhen Busy:https://busy.org/@eoshenzhen Telegram:https://t.me/eoshenzhen Twitter:https://twitter.com/eostechlover 简书:EOS技术爱好者 新浪微博:EOSTechLover *** **EOShenzhen的投票账号:eoshenzhenio** ![100x100-IMG_7963_small.png](https://ipfs.busy.org/ipfs/QmTdwaSQTJR15zQcr6AQUi7Wgi9z51s97DcAfhNhhN9A6c)
title【翻译|Ian】信息是一切中介
authoreoshenzhen
permlinkv7yy2-or-ian
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 permlinkeos
Transaction InfoBlock #26029244/Trx d5049e782f251b5b1b24fa24d7548634620dc2af
View Raw JSON Data
{
  "op": [
    "comment",
    {
      "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",
      "title": "【翻译|Ian】信息是一切中介",
      "author": "eoshenzhen",
      "permlink": "v7yy2-or-ian",
      "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"
    }
  ],
  "block": 26029244,
  "trx_id": "d5049e782f251b5b1b24fa24d7548634620dc2af",
  "op_in_trx": 0,
  "timestamp": "2018-09-17T04:17:30",
  "virtual_op": false,
  "trx_in_block": 9
}
eoshenzhenupdated payout for 2ngort
2018/09/17 03:38:24
authoreoshenzhen
permlink2ngort
Transaction InfoBlock #26028463/Virtual Operation 4294967295:4
View Raw JSON Data
{
  "op": [
    "comment_payout_update",
    {
      "author": "eoshenzhen",
      "permlink": "2ngort"
    }
  ],
  "block": 26028463,
  "trx_id": "0000000000000000000000000000000000000000",
  "op_in_trx": 4,
  "timestamp": "2018-09-17T03:38:24",
  "virtual_op": true,
  "trx_in_block": 4294967295
}
tstoeffective vote applied for @eoshenzhen / or-ian-dpos
2018/09/13 13:17:48
votertsto
authoreoshenzhen
weight19890
rshares2606999392
permlinkor-ian-dpos
pending payout0.005 HBD
total vote weight70756
Transaction InfoBlock #25924886/Trx ccafc39d8946eeffc39406760aa2f916a1fe0bdc
View Raw JSON Data
{
  "op": [
    "effective_comment_vote",
    {
      "voter": "tsto",
      "author": "eoshenzhen",
      "weight": 19890,
      "rshares": 2606999392,
      "permlink": "or-ian-dpos",
      "pending_payout": "0.005 HBD",
      "total_vote_weight": 70756
    }
  ],
  "block": 25924886,
  "trx_id": "ccafc39d8946eeffc39406760aa2f916a1fe0bdc",
  "op_in_trx": 1,
  "timestamp": "2018-09-13T13:17:48",
  "virtual_op": true,
  "trx_in_block": 9
}
tstoupvoted (100.00%) @eoshenzhen / or-ian-dpos
2018/09/13 13:17:48
votertsto
authoreoshenzhen
weight10000 (100.00%)
permlinkor-ian-dpos
Transaction InfoBlock #25924886/Trx ccafc39d8946eeffc39406760aa2f916a1fe0bdc
View Raw JSON Data
{
  "op": [
    "vote",
    {
      "voter": "tsto",
      "author": "eoshenzhen",
      "weight": 10000,
      "permlink": "or-ian-dpos"
    }
  ],
  "block": 25924886,
  "trx_id": "ccafc39d8946eeffc39406760aa2f916a1fe0bdc",
  "op_in_trx": 0,
  "timestamp": "2018-09-13T13:17:48",
  "virtual_op": false,
  "trx_in_block": 9
}
sensationeffective vote applied for @eoshenzhen / or-ian-dpos
2018/09/11 08:57:12
votersensation
authoreoshenzhen
weight2136 (21.36%)
rshares252306781
permlinkor-ian-dpos
pending payout0.002 HBD
total vote weight50866
Transaction InfoBlock #25862093/Trx 781e246aef07a6a06a3c60cee964ccc6efe8cb34
View Raw JSON Data
{
  "op": [
    "effective_comment_vote",
    {
      "voter": "sensation",
      "author": "eoshenzhen",
      "weight": 2136,
      "rshares": 252306781,
      "permlink": "or-ian-dpos",
      "pending_payout": "0.002 HBD",
      "total_vote_weight": 50866
    }
  ],
  "block": 25862093,
  "trx_id": "781e246aef07a6a06a3c60cee964ccc6efe8cb34",
  "op_in_trx": 1,
  "timestamp": "2018-09-11T08:57:12",
  "virtual_op": true,
  "trx_in_block": 2
}
sensationupvoted (100.00%) @eoshenzhen / or-ian-dpos
2018/09/11 08:57:12
votersensation
authoreoshenzhen
weight10000 (100.00%)
permlinkor-ian-dpos
Transaction InfoBlock #25862093/Trx 781e246aef07a6a06a3c60cee964ccc6efe8cb34
View Raw JSON Data
{
  "op": [
    "vote",
    {
      "voter": "sensation",
      "author": "eoshenzhen",
      "weight": 10000,
      "permlink": "or-ian-dpos"
    }
  ],
  "block": 25862093,
  "trx_id": "781e246aef07a6a06a3c60cee964ccc6efe8cb34",
  "op_in_trx": 0,
  "timestamp": "2018-09-11T08:57:12",
  "virtual_op": false,
  "trx_in_block": 2
}
moby-dickeffective vote applied for @eoshenzhen / or-ian-dpos
2018/09/11 08:46:03
votermoby-dick
authoreoshenzhen
weight835 (8.35%)
rshares54755202
permlinkor-ian-dpos
pending payout0.002 HBD
total vote weight48730
Transaction InfoBlock #25861870/Trx 85b72d2aa53879d5b44a56e9cb28c9a871d0b5ff
View Raw JSON Data
{
  "op": [
    "effective_comment_vote",
    {
      "voter": "moby-dick",
      "author": "eoshenzhen",
      "weight": 835,
      "rshares": 54755202,
      "permlink": "or-ian-dpos",
      "pending_payout": "0.002 HBD",
      "total_vote_weight": 48730
    }
  ],
  "block": 25861870,
  "trx_id": "85b72d2aa53879d5b44a56e9cb28c9a871d0b5ff",
  "op_in_trx": 1,
  "timestamp": "2018-09-11T08:46:03",
  "virtual_op": true,
  "trx_in_block": 1
}
moby-dickupvoted (100.00%) @eoshenzhen / or-ian-dpos
2018/09/11 08:46:03
votermoby-dick
authoreoshenzhen
weight10000 (100.00%)
permlinkor-ian-dpos
Transaction InfoBlock #25861870/Trx 85b72d2aa53879d5b44a56e9cb28c9a871d0b5ff
View Raw JSON Data
{
  "op": [
    "vote",
    {
      "voter": "moby-dick",
      "author": "eoshenzhen",
      "weight": 10000,
      "permlink": "or-ian-dpos"
    }
  ],
  "block": 25861870,
  "trx_id": "85b72d2aa53879d5b44a56e9cb28c9a871d0b5ff",
  "op_in_trx": 0,
  "timestamp": "2018-09-11T08:46:03",
  "virtual_op": false,
  "trx_in_block": 1
}
2018/09/11 08:06:18
bodyHi! I am a robot. I just upvoted you! I found similar content that readers might be interested in: https://steemit.com/eos/@iang/seeking-consensus-on-consensus-dpos-or-delegated-proof-of-stake-and-the-two-generals-problem
title
authorcheetah
permlinkcheetah-re-eoshenzhenor-ian-dpos
json metadata
parent authoreoshenzhen
parent permlinkor-ian-dpos
Transaction InfoBlock #25861075/Trx e1ba8fc3bf5d758fd9832c94bfc979a08098f1ab
View Raw JSON Data
{
  "op": [
    "comment",
    {
      "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",
      "title": "",
      "author": "cheetah",
      "permlink": "cheetah-re-eoshenzhenor-ian-dpos",
      "json_metadata": "",
      "parent_author": "eoshenzhen",
      "parent_permlink": "or-ian-dpos"
    }
  ],
  "block": 25861075,
  "trx_id": "e1ba8fc3bf5d758fd9832c94bfc979a08098f1ab",
  "op_in_trx": 0,
  "timestamp": "2018-09-11T08:06:18",
  "virtual_op": false,
  "trx_in_block": 4
}
cheetaheffective vote applied for @eoshenzhen / or-ian-dpos
2018/09/11 08:06:12
votercheetah
authoreoshenzhen
weight319 (3.19%)
rshares2065136610
permlinkor-ian-dpos
pending payout0.002 HBD
total vote weight47895
Transaction InfoBlock #25861073/Trx c48e4ca76351e3c9b9cc4d0f1153d942ffdca1c6
View Raw JSON Data
{
  "op": [
    "effective_comment_vote",
    {
      "voter": "cheetah",
      "author": "eoshenzhen",
      "weight": 319,
      "rshares": 2065136610,
      "permlink": "or-ian-dpos",
      "pending_payout": "0.002 HBD",
      "total_vote_weight": 47895
    }
  ],
  "block": 25861073,
  "trx_id": "c48e4ca76351e3c9b9cc4d0f1153d942ffdca1c6",
  "op_in_trx": 1,
  "timestamp": "2018-09-11T08:06:12",
  "virtual_op": true,
  "trx_in_block": 14
}
2018/09/11 08:06:12
votercheetah
authoreoshenzhen
weight8 (0.08%)
permlinkor-ian-dpos
Transaction InfoBlock #25861073/Trx c48e4ca76351e3c9b9cc4d0f1153d942ffdca1c6
View Raw JSON Data
{
  "op": [
    "vote",
    {
      "voter": "cheetah",
      "author": "eoshenzhen",
      "weight": 8,
      "permlink": "or-ian-dpos"
    }
  ],
  "block": 25861073,
  "trx_id": "c48e4ca76351e3c9b9cc4d0f1153d942ffdca1c6",
  "op_in_trx": 0,
  "timestamp": "2018-09-11T08:06:12",
  "virtual_op": false,
  "trx_in_block": 14
}
eoshenzhenpublished a new post: or-ian-dpos
2018/09/11 08:06:00
body# Seeking Consensus on Consensus - DPOS or Delegated Proof of Stake and the Two Generals' Problem # 在共识中寻求共识-DPOS(委任权益证明)和两军悖论 作者:Ian Grigg 翻译:Gavin 校对:Lochaiching Laying 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. 为一个高性能的金融区块链生态系统奠定基础肯定是备受争议,这很好理解。因为这里有很多方法——中心化的、去中心化的、未经许可的、封闭式。 Having 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: 除去以上提及的这些,我们仍然有一个关于如何应对竞态条件的烦恼。不管怎么设计,总有一些你想做的事情,还有一些其他人想做的事情,而这两件事不能同时兼得。或者,在某种意义上说你想要一些事情发生,并且你还想让别人知道这事情将要发生,在计算机科学领域中被称为[“两军悖论”](https://en.wikipedia.org/wiki/Two_Generals'_Problem#Definition): ``` Two 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. “Positions of the armies. Armies A1 and A2 need to communicate but their messengers may be captured by army B.” While 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. The 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: “Yes, we will both attack at the agreed-upon time. Allowing 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))” ``` ``` 两名军队由分别由其将军领导,准备袭击一座要塞城市。 军队在城市附近扎营,每个都在自己的山谷中。 第三个山谷将两座山谷分开,两位将军交流的唯一途径就是派遣信使穿过山谷。 不幸的是,山谷被城市的防御者所占据,并且任何被送往山谷的信使都有可能会被捕获。 军队的位置:军队A1和A2需要通信,但他们的信使可能被军队B抓获。 虽然两位将军同意他们会进行攻击,但他们还没有就攻击时间达成一致。两位将军要是不能同时攻击城市,那剩下的另一支军队也会随之覆灭(即只有两支军队同时进攻才能获取胜利)。因此,他们必须与彼此交流以获得进攻时间上的共识,并且两位将军都必须知道对方明白双方已达成共识,原因在于确认收到对方消息的这一条信息也有同样的概率会丢失,这就导致:两人需要就一个潜在的无限条信息组成的信息流需要达成共识。 这个思想实验包含:考虑他们该怎样达成共识。在这个最简单的形式之中,已知一个将军是领袖,决定进攻时间,并且必须将这个时间告知另外一位将军。现在问题在于我们需要一套算法能够让将军用来发送消息和处理已被收到的消息,并需要他们正确的涵盖以下内容: 是的,我们将在已达成共识的时间发起进攻。 要做到这一点是很容易的(即一个成功的消息和一个成功的确认)。两军悖论的微妙之处在于设计一套真正安全并能满足以上条件的系统是几乎不可能的(引自:[维基百科](https://en.wikipedia.org/wiki/Two_Generals'_Problem#Definition) ) ``` Also 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. 在区块链中,我们称之为共识问题,也被称为协调问题。在金融密码学领域,被称为双重支付问题,在数据库中被称为原子性。也就是说,这是所有计算科学的一个基本问题,它并不新鲜。 Let’s work through the evolution of this problem. 让我们来研究一下这个问题的演变过程。 ## Centralised Double Spend Protection ## 中心化双重支付保护 The 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. 加密金融中的原始机制是一个简单的客户-服务器端或受信任的第三方(比如[SOX](http://www.systemics.com/docs/sox/overview.html),译者注:一种支付系统),这就是说支持双重支付的价值发行方(译者注:这个发行方是一种货币)仅仅依靠一个服务器在双重支付中进行调解。十分典型的是,请求遵循先入先出(FIFO)排队方式,这在今天的数据库已经是标准了。 ## Blinded Cash ## 盲现金 One 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! 一个中心化双重支付保护的显著变种就是对货币的盲签名,这个概念由David Chaum于上世纪80年代末期发明。盲货币作为一种货币token可以单独被使用(可验证),但是就像所有的数据一样,Alice可以将其同时给Bob和Carol。对Bob而言,针对这种情况的解决方案就是将其收到的货币退还给发行的服务器,也就是印钞厂,并索要被重新签过名的另一份货币。同理,Carol也可以这么做,甚至以更快的速度。 “盲签名”注释,校对者注 Now, 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. 现在,盲签名在被用于Token上时存在一个特殊把戏:当Token完成一次被修改的RSA加密算法时,其能够创造一个之前未被使用过的全新签名,但这个签名却依然有效,因此这个货币依然是被承认的。因此,盲签名的“盲”字表示,货币的发行者不能追踪Alice用这些货币干了什么,这显然是十分有价值的!另一个关于电子现金的把戏是如果Alice确实尝试两次使用同一笔货币,造币方可以使用加密手段来将这两笔被消费的货币合并,去掉匿名保护,并揪出罪魁祸首。 盲签名案例,校对者注 I 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. 我涉及了部分关于盲双倍支付的内容,因为这是一个非常复杂的用于管制双重支付的系统中的一个例子,也因为这是我们诞生于上世纪80-90年代的金融密码学领域的开端。 ## Voting ## 投票 Replicated 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! 多服务器的选择变得流行主要是为了追求可靠性。比如,早期NASA的航天飞机就有以三个IBM主框架形成的投票环(以及一些备用框架)。在每一个投票系统中,都是占大多数的获胜,其余的小部分会被断开连接,并被取代。早期的建议投票系统事实上被证明有许多不足,而现在在行业中流行的关键词是Paxos(一种基于消息传递且具有高度容错特性的一致性算法)和PBFT(practical byzantine fault tolerant,拜占庭容错),而且支撑着这些内容的是Lamport(Paxos提出者),以及大量理论,PhD,论文,图灵奖!总之就是各种复杂的东西。 These above variations on the theme suffer from some pretty serious limitations, chief of which are, - they are administratively centralised, and/or/therefore - all participants are known. 以上提到的这些内容都有一些挺严重的局限性,主要有: - 从管理上来说他们是中心化的,和/或/因此 - 所有的参与者都是已知的 In 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. 换句话说,拜占庭将军问题的解决方案中我们知道谁是将军的假设,在以上提到的这些情况中并不适用。 ## Proof of Work ## 工作证明 Satoshi 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. 中本聪发现任何中心化的部件都能够被攻击,并会受到攻击([Nakamoto, Bitcoin: A Peer-to-Peer Electronic Cash System](https://bitcoin.org/bitcoin.pdf))。这个发现是准确的:MTB关停了eCash系统就是因为遭遇了意料之外的成人购物,DigiCash被政府当局干预致残,WebMoney遭到名誉上的攻击,e-gold和LibertyReserve被美联储扳倒。这个名单可以一直列下去,即使是作者本人也比预想中里这些灾难更近。你可以自己做一些调查来终结这些指责,以及其他一些偏见。 This was observed by several (see for example “The Mining Delusion”) but it was Bitcoin that presented a solution. 觉察到这个缺陷的人不止一个(例如参见["The Mining Delusion"](https://medium.com/@bergealex4/the-mining-delusion-96e021b6f899)),但是是比特币给出了解决方案。 Therefore, 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. 因此,中本聪说,我们需要终结这种易受攻击的中心化机构(CVP,也称TTP)。并且,通过推测我们也知道并不能信任已知机构的投票系统,我们必须分享并验证这些数据是相同的,并且同时我们必须有容易接入的出入口,即匿名性。 Great 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 :-( 这个东西很棒,但是仍不能让我们解决双重支付问题,我们只是将数据从单个地方挪到了一个大的多的地方。 The 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). 一个优雅且著名的解决方案是工作证明(PoW)或者中本签名,一个基于用哈希数学问题来确认正确区块交易的彩票系统。这个彩票系统的密码学的本质随机选择一个制造区块的矿机。将被称为挖矿的昂贵的哈希搜索和奖励耦合,并加上一些繁琐的博弈论和概率问题,所有这些元素都被用来将系统设计得能够驱使矿机不停工作。详情见[comic](https://medium.com/@dbrgndl/smalltime-replacing-bitcoin-with-a-currency-free-distributed-transfer-system-21364b9cce1f)。 Bitcoin 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. 比特币是一个出色并且优雅的解决方案,因为它开阔了我们的思维,让我们想到了完全的去中心化式的应用(或货币)的可能性。但是PoW消耗了太多能量,多到市场无法承受,多到能够成为一项附着在货币上的吓人的税(比特币4%,以太坊11%!)。而随着使用比特币的费用越来越高,大多数人将无法使用它。高额回报和上升的价格同样也导致了大规模的挖矿,并不可避免的导致了矿机的中心化。虽然系统本身依旧毫无问题的运行,但这由能够抵御审查的设计方案完成的系统却落入了少数几个公司,而这几个公司几乎都坐落在一个以审查严格而闻名的国家。 ## Proof of Stake ## 权益证明 It 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. 有人提出我们只需要将以CPU投票的模式改为以价值投票的模式来选择谁对(下个区块中)双重支付的问题做出决策。毕竟,区块链十分准确的建立在货币拥有的制度上,因此拥有更多货币的人更可能选择保护系统,因此这个偏向性是合理的。虽然可能让小额货币拥有者感到不适,也对民主制度有所冒犯。 So 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. 这个理论也因为一下原因受到批判:(1)将权力交给最多价值拥有者手中;(2)“无需抵押”问题(the “nothing at stake” problem):因为不需要付出任何代价所以会不断试图分叉(译者注:而对于矿机来说最优的策略是尽可能多的挖矿(制造区块),因此不论矿机挖的区块所属于的区块链最终是否获胜成为正确的那一条链,都能获得交易费。) Simple proof of stake then does not seem to work. Let’s see what does work - let’s break down the problem. 简单的权益证明似乎并不奏效,究竟什么系统才奏效呢?让我们将问题逐步分解。 ## Let’s go to a Mining Centralisation Conference ## 让我们去进行一个挖矿中心化的会议 When 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. 当我们观察到比特币矿工由中国垄断的现状时,很明显他们互相认识且能够相互沟通。而当面对今天大到能将国家变暖的挖矿规模情况下,我们知道比特币对矿工的匿名假设早已变得虚有其表了,因为我们只需要看电力消费或参与任意一个比特币会议就能知道到底是谁在挖矿。 And 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? 另一方面,他们可以相互勾结。至今他们并没有选择这么做,或者只是我们不知道。因为从历史上说这个情况还不能被证明是可靠的,也许动机与道德会被改进提高? Only 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. 只有他们的动机和道德能够让他们不相互勾结;在这种情况下矿工又回到了胖手指(fat-finger)失误的时候,有的交易者会意外的将一定数量的比特币而不是satoshi单位设为交易费,所以道德在这里确实起着一定的作用。另一方面,一些矿机会挖出空的区块,即使有成堆的被延迟的交易排成长队等待被处理。 Not 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? 今天的矿机中心化不仅是意料之外的,也不符合比特币最初的设想。矿工的正直会是一个可持续的未来吗?从历史角度来讲,正直并未被证明是可靠的,想想银行就知道,所以我们真的应该继续支持依靠动机和道德来支撑的区块链吗? What 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? 如果我们退一步接受矿工中心化的事实呢?并且我们知道他们是谁?或者更进一步地假设,矿工应该中心化并通过身份验证? If 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. 如果我们接受矿工中心化和矿工身份验证,那就可以指定矿工。但是指定ASIC矿机,想过没有,这样的进程会将我们带回最开始的容易受攻击的中心化局面。 ## Delegated Proof of Stake - How to rule the Generals ## DPOS-怎么管理将军 How 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. 那么我们究竟该如何更好的管理矿工呢?如果我们可以选出他们,我们同样可以解雇他们,这就将我们带回了两军悖论. Given 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: 鉴于现实和经验强加给我们的新要求,重新设计双重支付系统是合理的。 委托证明是由[@dantheman](https://busy.org/@dantheman)重新设计的,使用以下工具: 1.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). 1.一个生产者(nee miner)被选为决策者来避免一个区块中的双重支付,见图4,每次出块都能得到新的区块代币作为出块奖励; 2.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. 2.很多生产者被选择并被给予一个由一圈区块构成的罗宾环,从而在环内创造出一个存在竞争的市场,以保证可靠性并解决分叉,见图5; 3.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. 3.链上运行一个开放的社区通过投票来管理生产者,每个成员通过PoS原理进行投票。选择和解雇BP使用的是同一原理,即多轮拍卖式。见图6 。 The community then is required to govern their chain by - checking and agreeing with the transactions they perform, - 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 - maintaining their stake or suffrage to the needs they choose. 然后社区需要通过以下行为来管理他们的链 - 检查并同意他们执行的交易, - 根据他们的记录和其他声明(例如,生产者可以自由提供收入分配等激励措施)选出或者解雇生产者 - 维持他们的股权或选举权,以满足他们的选择。 Note that a more technical approach to attacks on DPOS can be found in DPOS Consensus Algorithm. 请注意,在[DPOS共识算法](https://steemit.com/dpos/@dantheman/dpos-consensus-algorithm-this-missing-white-paper)中可以找到更具技术性的DPOS攻击方法。 ## A Political Economy? ## 政治化经济学? In 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. 从共识的角度来说,DPoS是基于证据(proof)的代理权益(stake-delegation),即生产者向社区提供自己出块的证据,然后社区使用其权益来管理生产者。 In political terms, DPOS is similar to a two-layer representative democracy with landowner suffrage. Where, 从政治的角度来说,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))较为相似。在这种制度中: - representatives are those producers that are delegated by the community to decide the day to day questions (over double spend), and - 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. - 代表(representatives)即为那些由社区选举出的生产者,有生产者来处理那些日常的问题; - 对拥有某种形式财产的人给予选举权或选举权。 这个财产可能是一个储蓄单位,代表了对社区的承诺,也失去了流动性; 它类似于更普遍形式之前流行的历史土地所有者选举权,即对商人阶级为社会带来的财富和商业的承认。 The 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. 这种机制的准确设计——存款帐号,有多少出块者,多久出一个块,多长时间能形成一个循环,以及众多其他元素,显然是更深层次也是更有趣的问题,今天就不做讨论了。 ## How does it Perform? ## 它如何运作? This 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. 这个机制一直被不少具有一定规模的系统使用,如Bitshare,Steem,EOS,Tezos,PeerPlays,Ark.io等等。 While it is possible to criticise, so far the criticisms seem to be more at the level of flavour and comparison than weaknesses: 虽然可以对其批判,但迄今为止评论似乎更频繁的讨论其特点以及与其他机制比较,而不是其弱点: 1.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. 1.PoS因为“无需抵押(nothing at stake)”问题而变得脆弱,但只有当权益(stake)被用来直接参与区块建设的时候这个问题才会出现。而DPoS则解决了这个问题,因为在DPoS中对区块的处理被交给了生产者,这种责任的分离解决了“无需抵押问题”; 1.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. 2.有几种生产者会出现恶意行为的可能——他们可能会对交易进行干涉。但这事实上可以被转换为好吃,因为不合格的生产者会通过投票被解雇,这就是DPoS的意义。与比特币现在制造空区块的非法行为相比,DPoS的表现要强得多,因为它有一个惩罚机制; 3.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%. 3.勾结依然存在可能性。当然,勾结在其他区块链也存在可能性。重要的是哪一种机制在勾结存在的情况下运行的更好,至今为止这我们的钱都得到了妥善的管理,因为惩罚机制的存在。而在缺乏管理的纯PoW中,不管矿工做什么都不会受到惩罚,即使是51%攻击。在DPoS中,只要勾结被发现了,不管是1%还是51%我们都可以通过调整管理方式来对付。 4.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: 4.纯粹的比特币使用者会指出,添加管理层打破了区块链的无信任本质。然而并非如此,因为关于无信任有以下谬误: a.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. b.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. a.其他区块链没有管理层的谬误。这并不正确,事实上是由管理层的,只不过没有被明写出来,被拒绝承认,以及不稳定。从本质上来说,我们使用有明确规章制度和透明的管理取代了专设的管理。问题不在于这么做是否加强了管理程度,而在一明确的管理是否比暗地里管理更好。 b.比特币的设计然我们不需要信任矿工。在考虑一下空区块的问题:我们现在必须相信矿工会生产有效的区块,而事实并非如此,这就将区块链的数学上本质和“信任”的人性本质分离开来。PoW下的区块链终结了一部分信任,但并不是所有,而在这种情况下,当我们真正需要信任时,我们却无法再建立信任。 DPOS comes with some advantages that are also worth stressing: DPOS还有一些值得被提及的优点: 1.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. 1.由于其废除了哈希挖矿,DPoS会比PoW便宜得多。而收益的会是社区,因为我们会将这部分税归还给社区(如前面写到的比特币4%,以太坊11%)。 2.And we’re cleaning up the planet :-) DPOS is recommended for any blockchain with a heart ♡ 2.DPoS更加环保。DPOS推荐使用任务有环保之心的区块链。 3.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. 3.通过添加正式的管理层,我们也能够有计划的为软件进行升级。这意味着,用户将会有机会对系统的改变做出投票,生产者根据投票结果行动。这个机制几乎使恶意分叉成为不可能,并使区块链充满活力,由于它可以随着不断变化的需求而进化。比如:仍未解决的PoW中DAO(decentralizedautonomous organization,去中心化自治组织)的梦魇,以及关于区块大小的争论都是在DPoS中得到解决的问题。 4.The formalised governance also works to give community the voice over their chain. 4.正式的管理机制也给了社区对改进区块链提出建议的机会。 5.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. 5.DPoS致力于使做决策变得高效,从而使系统真正能被大规模使用。让我们把关于性能的讨论留给其他文章,但这里值得一提的是,测试中Bitshare实现了1000倍于当下比特币的性能。这样的性能让人能够容忍很多其他的瑕疵。 Benefits are of course all sins to some, but they are the sorts of sins that businesses and individuals can forgive and treasure. 这些优点当然也意味着存在尚未被发现的缺点,但他们会是企业和个人能够容忍的缺点。 本文图片来源于英文原文 *** 版权声明: 以下内容来自微信公共帐号“EOS技术爱好者”,搜索“EOSTechLover”即可订阅,翻译Gavin,校对Lochaiching。转载必须保留以上声明。仅授权原文转载。 本文原文链接为https://busy.org/@iang/seeking-consensus-on-consensus-dpos-or-delegated-proof-of-stake-and-the-two-generals-problem "EOS技术爱好者"全程由EOShenzhen运营,喜欢我们请为我们投票:(EOShenzhen的投票账号:eoshenzhenio)! *** **了解更多关于EOShenzhen:** [We are EOShenzhen](https://busy.org/@eoshenzhen/we-are-eoshenzhen-eos-bp-candidate) **不同入口如何投票:** [imToken](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) [portal](https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484354&idxx=1&sn=ddd4ffdae1531385a07fad59a6e86e6e&chksm=fa0b82fecd7c0be8328a0b3a1cff7de3bef207977ab0ca829c336fb450a7ef5c4153f32d5a4f&scene=21#wechat_redirect) **关于我们更多联系:** Website:https://eoshenzhen.io Steem:https://steemit.com/@eoshenzhen Busy:https://busy.org/@eoshenzhen Telegram:https://t.me/eoshenzhen Twitter:https://twitter.com/eostechlover 简书:EOS技术爱好者 新浪微博:EOSTechLover *** **EOShenzhen的投票账号:eoshenzhenio** ![100x100-IMG_7963_small.png](https://ipfs.busy.org/ipfs/QmTdwaSQTJR15zQcr6AQUi7Wgi9z51s97DcAfhNhhN9A6c)
title【翻译|Ian】在共识中寻求共识-DPOS(委任权益证明)和两军悖论
authoreoshenzhen
permlinkor-ian-dpos
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 permlinkpos
Transaction InfoBlock #25861069/Trx d5e0fa6ad22a1be556b537807ea07e342bae233d
View Raw JSON Data
{
  "op": [
    "comment",
    {
      "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)",
      "title": "【翻译|Ian】在共识中寻求共识-DPOS(委任权益证明)和两军悖论",
      "author": "eoshenzhen",
      "permlink": "or-ian-dpos",
      "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"
    }
  ],
  "block": 25861069,
  "trx_id": "d5e0fa6ad22a1be556b537807ea07e342bae233d",
  "op_in_trx": 0,
  "timestamp": "2018-09-11T08:06:00",
  "virtual_op": false,
  "trx_in_block": 16
}
2018/09/11 04:18:42
authoreoshenzhen
permlinktesting-announcement-kylinpoints-test-guide
Transaction InfoBlock #25856525/Virtual Operation 4294967295:4
View Raw JSON Data
{
  "op": [
    "comment_payout_update",
    {
      "author": "eoshenzhen",
      "permlink": "testing-announcement-kylinpoints-test-guide"
    }
  ],
  "block": 25856525,
  "trx_id": "0000000000000000000000000000000000000000",
  "op_in_trx": 4,
  "timestamp": "2018-09-11T04:18:42",
  "virtual_op": true,
  "trx_in_block": 4294967295
}
tstoeffective vote applied for @eoshenzhen / or-dapp-tungsten-poc
2018/09/10 09:24:18
votertsto
authoreoshenzhen
weight23717
rshares1476412921
permlinkor-dapp-tungsten-poc
pending payout0.002 HBD
total vote weight45915
Transaction InfoBlock #25833846/Trx a1aaabd3d1c058733719c7f3729870c6a9241a72
View Raw JSON Data
{
  "op": [
    "effective_comment_vote",
    {
      "voter": "tsto",
      "author": "eoshenzhen",
      "weight": 23717,
      "rshares": 1476412921,
      "permlink": "or-dapp-tungsten-poc",
      "pending_payout": "0.002 HBD",
      "total_vote_weight": 45915
    }
  ],
  "block": 25833846,
  "trx_id": "a1aaabd3d1c058733719c7f3729870c6a9241a72",
  "op_in_trx": 1,
  "timestamp": "2018-09-10T09:24:18",
  "virtual_op": true,
  "trx_in_block": 24
}
2018/09/10 09:24:18
votertsto
authoreoshenzhen
weight10000 (100.00%)
permlinkor-dapp-tungsten-poc
Transaction InfoBlock #25833846/Trx a1aaabd3d1c058733719c7f3729870c6a9241a72
View Raw JSON Data
{
  "op": [
    "vote",
    {
      "voter": "tsto",
      "author": "eoshenzhen",
      "weight": 10000,
      "permlink": "or-dapp-tungsten-poc"
    }
  ],
  "block": 25833846,
  "trx_id": "a1aaabd3d1c058733719c7f3729870c6a9241a72",
  "op_in_trx": 0,
  "timestamp": "2018-09-10T09:24:18",
  "virtual_op": false,
  "trx_in_block": 24
}
sensationeffective vote applied for @eoshenzhen / or-dapp-tungsten-poc
2018/09/10 07:53:45
votersensation
authoreoshenzhen
weight10621
rshares336409041
permlinkor-dapp-tungsten-poc
pending payout0.000 HBD
total vote weight22198
Transaction InfoBlock #25832035/Trx 4ef8c92f6be43734d5f37e8d5bcd2f902a43e0be
View Raw JSON Data
{
  "op": [
    "effective_comment_vote",
    {
      "voter": "sensation",
      "author": "eoshenzhen",
      "weight": 10621,
      "rshares": 336409041,
      "permlink": "or-dapp-tungsten-poc",
      "pending_payout": "0.000 HBD",
      "total_vote_weight": 22198
    }
  ],
  "block": 25832035,
  "trx_id": "4ef8c92f6be43734d5f37e8d5bcd2f902a43e0be",
  "op_in_trx": 1,
  "timestamp": "2018-09-10T07:53:45",
  "virtual_op": true,
  "trx_in_block": 5
}
2018/09/10 07:53:45
votersensation
authoreoshenzhen
weight10000 (100.00%)
permlinkor-dapp-tungsten-poc
Transaction InfoBlock #25832035/Trx 4ef8c92f6be43734d5f37e8d5bcd2f902a43e0be
View Raw JSON Data
{
  "op": [
    "vote",
    {
      "voter": "sensation",
      "author": "eoshenzhen",
      "weight": 10000,
      "permlink": "or-dapp-tungsten-poc"
    }
  ],
  "block": 25832035,
  "trx_id": "4ef8c92f6be43734d5f37e8d5bcd2f902a43e0be",
  "op_in_trx": 0,
  "timestamp": "2018-09-10T07:53:45",
  "virtual_op": false,
  "trx_in_block": 5
}
eoshenzheneffective vote applied for @eoshenzhen / or-dapp-tungsten-poc
2018/09/10 07:07:27
votereoshenzhen
authoreoshenzhen
weight0 (0.00%)
rshares122568811
permlinkor-dapp-tungsten-poc
pending payout0.000 HBD
total vote weight11577
Transaction InfoBlock #25831109/Trx 657c536844604487c25b9afbb3225228f8aa251f
View Raw JSON Data
{
  "op": [
    "effective_comment_vote",
    {
      "voter": "eoshenzhen",
      "author": "eoshenzhen",
      "weight": 0,
      "rshares": 122568811,
      "permlink": "or-dapp-tungsten-poc",
      "pending_payout": "0.000 HBD",
      "total_vote_weight": 11577
    }
  ],
  "block": 25831109,
  "trx_id": "657c536844604487c25b9afbb3225228f8aa251f",
  "op_in_trx": 2,
  "timestamp": "2018-09-10T07:07:27",
  "virtual_op": true,
  "trx_in_block": 27
}
2018/09/10 07:07:27
votereoshenzhen
authoreoshenzhen
weight10000 (100.00%)
permlinkor-dapp-tungsten-poc
Transaction InfoBlock #25831109/Trx 657c536844604487c25b9afbb3225228f8aa251f
View Raw JSON Data
{
  "op": [
    "vote",
    {
      "voter": "eoshenzhen",
      "author": "eoshenzhen",
      "weight": 10000,
      "permlink": "or-dapp-tungsten-poc"
    }
  ],
  "block": 25831109,
  "trx_id": "657c536844604487c25b9afbb3225228f8aa251f",
  "op_in_trx": 1,
  "timestamp": "2018-09-10T07:07:27",
  "virtual_op": false,
  "trx_in_block": 27
}
eoshenzhenpublished a new post: or-dapp-tungsten-poc
2018/09/10 07:07:27
body# Introducing Proof-of-concept Tungsten for dApplication level Governance # 来介绍一下用于dApp层面治理的Tungsten(PoC) ![1_5snIl-wnTRH46RIodXKgIw.jpeg](https://ipfs.busy.org/ipfs/QmVhEUyGR9p26KfKRXzH3QbWpRvB1xCFpYMLVcyuv1GzHB) ``` While 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. The 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. [Source](https://medium.com/@LindaCrypto/eos-governance-issues-explained-and-the-current-state-of-affairs-75d2847ee8b9) ``` ``` 虽然去中心化是区块链项目的基本目标,但在目前区块链的情况下,它更像是一个最终目标而不是起点。要使治理系统正常工作,还有许多问题需要解决。当时间很重要时,像仲裁这样的制度就不起作用了,因为损失在你有时间处理之前已经造成了。治理系统故障的最终解决可能需要花费大量的时间和精力。安全应该总是比治理更重要,因为这是好的区块链项目必不可少的因素,治理则让它变得更完善。 EOS社区三个不同的角色,即21个BP、仲裁者和token持有者,都应该就当前治理问题让可满足的解决方案达成一致,以便向世界展示整个社区正在构建/支持什么。 [来源](https://medium.com/@LindaCrypto/eos-governance-issues-explained-and-the-current-state-of-affairs-75d2847ee8b9) ``` EOS 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. EOS被认定为“受治理的区块链”,它有自己的公约(constitution)和一个仲裁论坛ECAF来执行治理方面的事务。在基层建立仲裁论坛的想法是在个人和企业之间这个层面来建立信任。ECAF的第一批裁决让一些论坛权力和主观仲裁的问题浮出水面。看看这时候缺失的边界,Block One选择呼吁终止所有仲裁命令,而不是对代码的意图提出不具约束力的意见。 The 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. 这个提议的意图是将治理结构从基础层转移到具有明确目标的dApp层(即去中心化应用层)。此外有人建议,只有在冻结或更换违约合同的情况下,BP才有担任陪审团角色的资格。 To 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. 为了执行超出了“代码是法律的意图”的范围之外dApp层面的纠纷,我们EOSMetal开发了一个定义边界(目标)和惩罚的基于仲裁的Bond(PoC阶段)。这样的Bond可以帮助可要求的承诺建立信任和获得知名度。 Daniel 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. Daniel Larimer设想的基础层仲裁与现在的仲裁有很大的不同,ECAF只是负责发表意见,而不是裁决,这可能也不能确定是否是BP需要遵循的。这样的想法是不给任何人最高权力。 To 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. 对仲裁机构职权进行适当的制约和平衡,应当在社区公开、透明、在链上地进行仲裁。鉴于从当前的情况来看,公布纠纷的细节是不明智的,因此不透明的范围增加一层,就会让仲裁员的行动加深一步,这可能会导致检查的削弱,随着时间的推移整个局面会趋向于腐败。 ## Our arguments against Base layer arbitration 1.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. 2.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. 3.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. 4.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. 5.Absence of well-defined Jurisdiction. ## 我们不同意基础层面的仲裁 1、可执行性——仲裁员提出的意见需要由BP们进行分析。而BP们有判断的权利主要是依赖于选票,即他们可能会倾向于持有大票仓的选民。如果基础层面的论坛是有约束力的,并且是可执行的,我们觉得这样的论坛权利过大,导致在审查和平衡之中变得进退两难。 2、如果协议层有许多仲裁论坛,那么BP们可能会发现难以执行裁决,即我们可能不想冻结任何账户,但仅仅因为仲裁员说要这么做,我们就需要照办。 3、我们认为,任何主观主张的执行都应由第三方仲裁员来执行,除非争议与规范的修订有关,否则不应涉及BP。 4、可扩容性——由于存在许多争议,社区/BP们可能发现很难进行适当的审查和平衡,这可能导致长期的腐败或滥用权力。 5、缺乏明确的权限管辖。 ## Bonds and dApp layer governance. Unlike 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. The concept of Bond based governance and arbitration rulings limited to bonds is the brainchild of Daniel Larimer himself. ## Bond和dApp应用层治理 与底层治理不同,底层治理倾向于处理所有争议并要求社区实行定期审查,dApp应用层治理并行工作,限制BP们执行的职责。 以Bond为基础的治理和仲裁裁决的概念仅限于Bond是Daniel Larimer自己的想法。 ![WechatIMG282.jpeg](https://ipfs.busy.org/ipfs/QmPgSgRorTU9Dy3nBY46pRC1mYcaSxDXCR85BBGk1TKTeh) ## Importance of Promises in the Business Commitment, 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). ## 商业承诺的重要性 一方(承诺人)向另一方(承诺人)承诺履行或不履行一项或多项特定行为。然而,承诺只有在合同(双方或多方自愿、慎重且具有法律约束力的协议)生效时才具有法律约束力。 ## What are Bonds? The 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. ## 什么是Bond? Bond是与李嘉图合同捆绑在一起的一系列承诺(定义的条款)的抵押品,在任何纠纷发生时都可以提出索赔,并且具有法律约束力。仲裁员的权力仅限于Bond所在的范围。 ## Proof of Concept: Tungsten We 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. Using 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. Also, 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. An 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. The 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. ## Tungsten的PoC版本 我们EOSMetal已经开发到了PoC阶段: 基于bond的Tungsten,可以让仲裁从基础层到应用层转移变得更容易。 任何实体或个人使用Tungsten都可以用一套可申索的条款(有明确处罚范围的条例)来筹集资Bond。Bond发行方还可以选择任何仲裁论坛来处理纠纷(可选择加入),并选择Bond的期限。 此外,在发生任何纠纷时,个人可以对Bond提出索赔。他需要指定Bond哈希值和索赔值(罚款)。原告必须填妥申索金额的10%作为bond,以备原告败诉,bond将交予被告。 仲裁员可以在链上用Tungsten进行裁决,如果最终裁决原告胜诉,智能合约就会把资金转移给原告。 这种bond就像托管一样,可以帮助社区成员建立信任。该合同将纠纷解决从任何BP或任何中心化实体的干预中转移出来。此外,它使仲裁人能自动强制执行裁决,而不需要BP的干预。 ## The Road Ahead! Tungsten 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. ## 未来蓝图! Tungsten是迈向更大目标的一小步,即通过选择真正需求的规则,使EOS网络中的dApp在主流应用中变得更加可信任和更安全。 ## Register Arbitrator. We need to add a functionality for any individual to register as an arbitrator with an option of raising a bond himself. This 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. ## 注册仲裁员 我们需要添加一个功能,让任何个人都可以注册为仲裁员,并可以选择自己提高bond来增加可用度。 通过这种方式,任何愿意在EOS网络上解决纠纷的仲裁员都可以注册并建立信任。我们认为,随着dApp在主网上出现得越来越多,处理小纠纷的单个仲裁员的需求将会增加。 ## Arbitration Forums An 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. [Source](https://medium.com/eos-new-york/free-market-dispute-resolution-on-eos-identifying-arbitrators-arbitration-forums-on-chain-via-663bd8ad9c56) Along 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. ## 仲裁论坛 仲裁论坛(或社团)是管理仲裁程序的组织。这些组织与仲裁员明显不同,因为论坛实际上并不仲裁或撰写仲裁裁决(实质上是仲裁结果的裁决)。他们的工作是维护一套纠纷解决规则(RDR),维护一个合格的仲裁员的数据库,以满足索赔人(即原告)的需求,协助完成从索赔申请到结束的行政工作,并充当仲裁员和原告之间的沟通桥梁。 [来源](https://medium.com/eos-new-york/free-market-dispute-resolution-on-eos-identifying-arbitrators-arbitration-forums-on-chain-via-663bd8ad9c56) 除了允许仲裁员注册外,我们还致力于帮助论坛注册自己的合约。 EOS NewYork正在致力于完善{regarbitrator} 和 {regfourm} 合约,如果可能的话,我们可以使用相同的合约,并允许仲裁员注册或论坛自行筹集bond。 ## Public Forums Forums are important to have on-chain evidence by the claimant (if possible) and awards by Arbitrators. Forums could help with two majors functions- Filtering arbitrators based on awards and resolved disputes documents. 2. Filtering claims, which could help with analysing the health of arbitration ecology and help with updating clauses for bonds. ## 公开论坛 论坛重要的是要有原告的链上证据(如果可能的话)和仲裁员的裁决。论坛可以帮助两个主要功能- 1、根据裁决和纠纷解决文件对仲裁员进行筛选。 2、过滤索赔要求,这有助于分析仲裁生态的健康,并有助于更新bond的条款。 ## Ricardian Contract Auditors/Smart Contract Auditors If 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. The rating and reviews by trusted auditors will help with standardizing the bond dApplication accordingly. It creates an opportunity for entrepreneurs to start auditing and rating firms for bonds. If you are looking for starting an auditing firm, get in touch with us! ## 李嘉图合约审计师/智能合约审计师 如果bond被广泛使用,大多数dAppl所有者将在部署合约之前查找合约的安全审计。然后,审计人员需要对李嘉图合约和智能合约进行审查和评级。 受信任的审计师的评级和审查将有助于相应dApp标准化的bond。 它为企业家提供了一个审计和评级公司bond的机会。 如果您正在寻找一家审计公司,请与我们联系! ## Certification A 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. To 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. Block 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. ## 认证 一些对可选协议的批评认为,这样一个协议,单方面起草了个人、dApp、实体而给起草方明显偏好和包括粘附的合同条款,在大多数情况下,签署者不受更改或谈判,不表达。点击同意(李嘉图合约 - 我同意)通常在用户没有提前阅读合约的情况下进行。最重要的是,人们担心的是,这种消费者同意很可能会导致双方不同意义上的同意或处理。 为了保护用户对企业所有者的“同意”,我们认为基于李嘉图合约(RC)和智能合约的审计证书(执照)可以帮助区分良好dApp的bond和带有自我偏好dApp的bond。 BP在社区内非常知名,并且以使用正确的工具管理社区。引入证书/许可证背后的想法是,通过使用BP认可的工具,帮助在社区成员辨识具有高可见性和更具信任的审计bond和智能合约。 ## Wallets / Browsers We 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. In 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. [Source](https://medium.com/@bytemaster/the-intent-of-code-is-law-c0e0cd318032) ## 钱包/浏览器 我们认为节制对于过滤互联网网站是一个非常棒的特质。为了过滤基于bond和证书的安全dApp而开发的浏览器/钱包可以让用户在没有两者(bond和安全)的情况下避免受到盗窃和欺诈的攻击。 ``` 在一个协议级别的纠纷解决仅限于修复代码里bug的世界中,如何防止密钥的欺诈和窃取?答案是选择加入一个银行化的李嘉图合约,它代表其所有者控制token。在智能合约中,如果合约指定的仲裁员有权撤销交易并冻结token,则该合约中的转移将受到纠纷解决的约束。从银行智能合约中撤回将会有3天的延迟,在此之后它们将不能被撤销。 来源:[【翻译】“代码的意图”即法律]( https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484507&idx=1&sn=07205bc22bcaa78ca2706a6414a76ec7&chksm=fa0b8567cd7c0c71e0c991d5ab18e02fb8d7a4c25c51fb799770913f24167656f52136f9c167&scene=21#wechat_redirect) ``` ## Block Producers and Bonds! Instead 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. ``` EOSMetal 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. ``` ## BP和bond! 我们建议将条款转换为bond,并允许BP做出承诺,而不是围绕 {regproducer} 合约产生主观争议。社区可以投票给分析由自由市场方式驱动的可索赔条款的BP。通过这种方式,可以更好地分析网络的健康状况,我们可以推动社区走向更好的治理,从各个层面减少腐败。 ``` EOSMetal将是第一个使用 Tungsten的用户,并将部署自己的bond,任何投票给我们的用户都可以申请。我们希望其他BP也加入我们的行列,筹集类似的bond。由自由市场力量驱动的BP所作的一系列承诺将在治理方面为利益相关者提供更多的灵活性。 ``` ## Advisors We are glad to have Cryptolions, EOSTitan and EOShenzhen as our advisers for this project. ## 顾问 我们很高兴有Cryptolions、EOSTitan和EOShenzhen作为这个项目的顾问。 ## Conclusion The 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. With 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. We 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. ## 结论 EOS社区仍在试验和研究可以让治理结构变得更加健壮的方法,以吸引主流商业或dApp,并向个体承诺完善这个主网基础安全的设施。 在dApp基础层面的仲裁存在着很多声音、意见和执行不力的情况下,争论也一直没有结果。对于Tungsten,我们希望通过可申请抵押物来填补这一空白。 我们的观点是,如果社区达成共识,采取正确的步骤来创建安全的基础设施,从而过滤恶意合约并为可信任的dApp提供可见性,那么我们只需要在基础层上进行高效的治理。 ## Resources We invite you to join EOSMetal and discuss the implementation of bond based governance on telegram here: https://t.me/eosmetal To view our initial implementation please visit Github here: https://github.com/EOSMetal/tungsten ## 更多关于我们 我们邀请您加入EOSMetal并在telegram上讨论基于bond的治理实现:https://t.me/eosmetal 要查看我们的初始化实现版本,请访问Github: https://github.com/EOSMetal/tungsten 本文图片来源于英文原文 *** 版权声明: 以下内容来自微信公共帐号“EOS技术爱好者”,搜索“EOSTechLover”即可订阅,翻译Lochaiching。转载必须保留以上声明。仅授权原文转载。 本文原文链接为 https://medium.com/@EosMetal/introducing-proof-of-concept-tungsten-for-dapplication-level-governance-fea8b0a452e9 "EOS技术爱好者"全程由EOShenzhen运营,喜欢我们请为我们投票,(EOShenzhen的投票账号:eoshenzhenio)! *** **了解更多关于EOShenzhen:** [We are EOShenzhen](https://busy.org/@eoshenzhen/we-are-eoshenzhen-eos-bp-candidate) **不同入口如何投票:** [imToken](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) [portal](https://mp.weixin.qq.com/s?__biz=MzUyNjcwMjY3NQ==&mid=2247484354&idxx=1&sn=ddd4ffdae1531385a07fad59a6e86e6e&chksm=fa0b82fecd7c0be8328a0b3a1cff7de3bef207977ab0ca829c336fb450a7ef5c4153f32d5a4f&scene=21#wechat_redirect) **关于我们更多联系:** Website:https://eoshenzhen.io Steem:https://steemit.com/@eoshenzhen Busy:https://busy.org/@eoshenzhen Telegram:https://t.me/eoshenzhen Twitter:https://twitter.com/eostechlover 简书:EOS技术爱好者 新浪微博:EOSTechLover *** **EOShenzhen的投票账号:eoshenzhenio** ![100x100-IMG_7963_small.png](https://ipfs.busy.org/ipfs/QmTdwaSQTJR15zQcr6AQUi7Wgi9z51s97DcAfhNhhN9A6c)
title【翻译|公告】用于dApp层面治理的Tungsten(PoC版本)
authoreoshenzhen
permlinkor-dapp-tungsten-poc
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 permlinkpoc
Transaction InfoBlock #25831109/Trx 657c536844604487c25b9afbb3225228f8aa251f
View Raw JSON Data
{
  "op": [
    "comment",
    {
      "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",
      "title": "【翻译|公告】用于dApp层面治理的Tungsten(PoC版本)",
      "author": "eoshenzhen",
      "permlink": "or-dapp-tungsten-poc",
      "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"
    }
  ],
  "block": 25831109,
  "trx_id": "657c536844604487c25b9afbb3225228f8aa251f",
  "op_in_trx": 0,
  "timestamp": "2018-09-10T07:07:27",
  "virtual_op": false,
  "trx_in_block": 27
}
tstoeffective vote applied for @eoshenzhen / 2ngort
2018/09/10 05:36:45
votertsto
authoreoshenzhen
weight11975
rshares1569520042
permlink2ngort
pending payout0.005 HBD
total vote weight64355
Transaction InfoBlock #25829295/Trx 998ea0652411577c0376320ba0d0f8342a302189
View Raw JSON Data
{
  "op": [
    "effective_comment_vote",
    {
      "voter": "tsto",
      "author": "eoshenzhen",
      "weight": 11975,
      "rshares": 1569520042,
      "permlink": "2ngort",
      "pending_payout": "0.005 HBD",
      "total_vote_weight": 64355
    }
  ],
  "block": 25829295,
  "trx_id": "998ea0652411577c0376320ba0d0f8342a302189",
  "op_in_trx": 1,
  "timestamp": "2018-09-10T05:36:45",
  "virtual_op": true,
  "trx_in_block": 9
}

Account Metadata

POSTING 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"}
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"}
{
  "posting_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"
    }
  },
  "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"
    }
  }
}

Auth Keys

Owner
Single Signature
Public Keys
STM7MyxQ9ARDFqtcfr19ZrGRW5W8mZe46Etac4PWUbbr1HS44xQZD1/1
Active
Single Signature
Public Keys
STM7QSPBU7A2kKAeeYZoMPEB7mMD7YXKHm3HnEKmDSct69JtJX8CW1/1
Posting
Single Signature
Public Keys
STM8Us5QYGDGR8PE3Dh3LUJBngbrDWmiFTvvPEr9AyNFNZeShtCGp1/1
App Permissions
Memo
STM5gxgUfpqfhsicHNG9AotN7snBkwq7j23Nrdi1rVWFMYFn73rGV
{
  "owner": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM7MyxQ9ARDFqtcfr19ZrGRW5W8mZe46Etac4PWUbbr1HS44xQZD",
        1
      ]
    ]
  },
  "active": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM7QSPBU7A2kKAeeYZoMPEB7mMD7YXKHm3HnEKmDSct69JtJX8CW",
        1
      ]
    ]
  },
  "posting": {
    "weight_threshold": 1,
    "account_auths": [
      [
        "busy.app",
        1
      ]
    ],
    "key_auths": [
      [
        "STM8Us5QYGDGR8PE3Dh3LUJBngbrDWmiFTvvPEr9AyNFNZeShtCGp",
        1
      ]
    ]
  },
  "memo": "STM5gxgUfpqfhsicHNG9AotN7snBkwq7j23Nrdi1rVWFMYFn73rGV"
}

Witness Votes

0 / 30
No active witness votes.
[]