Ecoer Logo
VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS30.29%
Net Worth
0.065USD
STEEM
0.174STEEM
SBD
0.099SBD
Effective Power
5.001SP
├── Own SP
0.125SP
└── Incoming Deleg
+4.876SP

Detailed Balance

STEEM
balance
0.000STEEM
market_balance
0.000STEEM
savings_balance
0.000STEEM
reward_steem_balance
0.174STEEM
STEEM POWER
Own SP
0.125SP
Delegated Out
0.000SP
Delegation In
4.876SP
Effective Power
5.001SP
Reward SP (pending)
0.249SP
SBD
sbd_balance
0.000SBD
sbd_conversions
0.000SBD
sbd_market_balance
0.000SBD
savings_sbd_balance
0.000SBD
reward_sbd_balance
0.099SBD
{
  "balance": "0.000 STEEM",
  "savings_balance": "0.000 STEEM",
  "reward_steem_balance": "0.174 STEEM",
  "vesting_shares": "203.758605 VESTS",
  "delegated_vesting_shares": "0.000000 VESTS",
  "received_vesting_shares": "7939.901201 VESTS",
  "sbd_balance": "0.000 SBD",
  "savings_sbd_balance": "0.000 SBD",
  "reward_sbd_balance": "0.099 SBD",
  "conversions": []
}

Account Info

namejetsesprey
id949779
rank379,241
reputation6477898926
created2018-04-20T20:07:36
recovery_accountsteem
proxyNone
post_count4
comment_count0
lifetime_vote_count0
witnesses_voted_for0
last_post2018-11-29T15:38:51
last_root_post2018-11-29T15:38:51
last_vote_time1970-01-01T00:00:00
proxied_vsf_votes0, 0, 0, 0
can_vote1
voting_power0
delayed_votes0
balance0.000 STEEM
savings_balance0.000 STEEM
sbd_balance0.000 SBD
savings_sbd_balance0.000 SBD
vesting_shares203.758605 VESTS
delegated_vesting_shares0.000000 VESTS
received_vesting_shares7939.901201 VESTS
reward_vesting_balance505.111139 VESTS
vesting_balance0.000 STEEM
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_update1970-01-01T00:00:00
last_account_update2018-06-12T15:41:03
minedNo
sbd_seconds0
sbd_last_interest_payment1970-01-01T00:00:00
savings_sbd_last_interest_payment1970-01-01T00:00:00
{
  "id": 949779,
  "name": "jetsesprey",
  "owner": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM68YcjUfh46DoPkPJyuzxBnX2DmT1LdwfMg6DmhYc1iGuLph7xP",
        1
      ]
    ]
  },
  "active": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM7PU5PwJhzt5UK9HQpRMDickNU3XHtjYnyfJwCun7e4cunv5Nqu",
        1
      ]
    ]
  },
  "posting": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM7UFy7nXo1TxZ4vgWHYEXtH7dX8Dnj8Uwh1gbmpYPYEMBgx9HiS",
        1
      ]
    ]
  },
  "memo_key": "STM7ZXkRzUrJz7BZorrLT2FhMrKRU8gGfYujDG9pLNMuz2nSG1pMK",
  "json_metadata": "{\"profile\":{\"profile_image\":\"https://cdn.steemitimages.com/DQmWjBCAPvWMz7CmBxouKEdieTacdv4bm69ovTer2k34mwu/EOS%20AMSTERDAM%20LOGO%20IMG_20180612_173627_160.jpg\",\"name\":\"Jetse Sprey EOS Ams\",\"location\":\"Amsterdam\",\"website\":\"https://eosamsterdam.net/\"}}",
  "posting_json_metadata": "{\"profile\":{\"profile_image\":\"https://cdn.steemitimages.com/DQmWjBCAPvWMz7CmBxouKEdieTacdv4bm69ovTer2k34mwu/EOS%20AMSTERDAM%20LOGO%20IMG_20180612_173627_160.jpg\",\"name\":\"Jetse Sprey EOS Ams\",\"location\":\"Amsterdam\",\"website\":\"https://eosamsterdam.net/\"}}",
  "proxy": "",
  "last_owner_update": "1970-01-01T00:00:00",
  "last_account_update": "2018-06-12T15:41:03",
  "created": "2018-04-20T20:07:36",
  "mined": false,
  "recovery_account": "steem",
  "last_account_recovery": "1970-01-01T00:00:00",
  "reset_account": "null",
  "comment_count": 0,
  "lifetime_vote_count": 0,
  "post_count": 4,
  "can_vote": true,
  "voting_manabar": {
    "current_mana": "8143659806",
    "last_update_time": 1779069093
  },
  "downvote_manabar": {
    "current_mana": 2035914951,
    "last_update_time": 1779069093
  },
  "voting_power": 0,
  "balance": "0.000 STEEM",
  "savings_balance": "0.000 STEEM",
  "sbd_balance": "0.000 SBD",
  "sbd_seconds": "0",
  "sbd_seconds_last_update": "1970-01-01T00:00:00",
  "sbd_last_interest_payment": "1970-01-01T00:00:00",
  "savings_sbd_balance": "0.000 SBD",
  "savings_sbd_seconds": "0",
  "savings_sbd_seconds_last_update": "1970-01-01T00:00:00",
  "savings_sbd_last_interest_payment": "1970-01-01T00:00:00",
  "savings_withdraw_requests": 0,
  "reward_sbd_balance": "0.099 SBD",
  "reward_steem_balance": "0.174 STEEM",
  "reward_vesting_balance": "505.111139 VESTS",
  "reward_vesting_steem": "0.249 STEEM",
  "vesting_shares": "203.758605 VESTS",
  "delegated_vesting_shares": "0.000000 VESTS",
  "received_vesting_shares": "7939.901201 VESTS",
  "vesting_withdraw_rate": "0.000000 VESTS",
  "next_vesting_withdrawal": "1969-12-31T23:59:59",
  "withdrawn": 0,
  "to_withdraw": 0,
  "withdraw_routes": 0,
  "curation_rewards": 0,
  "posting_rewards": 496,
  "proxied_vsf_votes": [
    0,
    0,
    0,
    0
  ],
  "witnesses_voted_for": 0,
  "last_post": "2018-11-29T15:38:51",
  "last_root_post": "2018-11-29T15:38:51",
  "last_vote_time": "1970-01-01T00:00:00",
  "post_bandwidth": 0,
  "pending_claimed_accounts": 0,
  "vesting_balance": "0.000 STEEM",
  "reputation": "6477898926",
  "transfer_history": [],
  "market_history": [],
  "post_history": [],
  "vote_history": [],
  "other_history": [],
  "witness_votes": [],
  "tags_usage": [],
  "guest_bloggers": [],
  "rank": 379241
}

Withdraw Routes

IncomingOutgoing
Empty
Empty
{
  "incoming": [],
  "outgoing": []
}
From Date
To Date
steemdelegated 4.876 SP to @jetsesprey
2026/05/18 01:51:33
delegatorsteem
delegateejetsesprey
vesting shares7939.901201 VESTS
Transaction InfoBlock #106145365/Trx 23287a7070c5ebe529b1bc2d192b9abc42e85b0e
View Raw JSON Data
{
  "trx_id": "23287a7070c5ebe529b1bc2d192b9abc42e85b0e",
  "block": 106145365,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2026-05-18T01:51:33",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "jetsesprey",
      "vesting_shares": "7939.901201 VESTS"
    }
  ]
}
steemdelegated 3.210 SP to @jetsesprey
2026/05/12 10:21:24
delegatorsteem
delegateejetsesprey
vesting shares5227.690796 VESTS
Transaction InfoBlock #105983515/Trx b3b037a6d4d40ef8969e4e97c75b8c876d233fce
View Raw JSON Data
{
  "trx_id": "b3b037a6d4d40ef8969e4e97c75b8c876d233fce",
  "block": 105983515,
  "trx_in_block": 5,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2026-05-12T10:21:24",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "jetsesprey",
      "vesting_shares": "5227.690796 VESTS"
    }
  ]
}
steemdelegated 4.884 SP to @jetsesprey
2026/04/26 01:09:51
delegatorsteem
delegateejetsesprey
vesting shares7952.416957 VESTS
Transaction InfoBlock #105512971/Trx dbc3eb056a361dc5acc2e6eaac24e1344133b744
View Raw JSON Data
{
  "trx_id": "dbc3eb056a361dc5acc2e6eaac24e1344133b744",
  "block": 105512971,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2026-04-26T01:09:51",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "jetsesprey",
      "vesting_shares": "7952.416957 VESTS"
    }
  ]
}
steemdelegated 3.236 SP to @jetsesprey
2026/01/23 12:07:00
delegatorsteem
delegateejetsesprey
vesting shares5269.237615 VESTS
Transaction InfoBlock #102856983/Trx 5343a45cae9a5b486edbe48d8bedeb54fd7801dc
View Raw JSON Data
{
  "trx_id": "5343a45cae9a5b486edbe48d8bedeb54fd7801dc",
  "block": 102856983,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2026-01-23T12:07:00",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "jetsesprey",
      "vesting_shares": "5269.237615 VESTS"
    }
  ]
}
steemdelegated 3.337 SP to @jetsesprey
2024/12/17 07:23:45
delegatorsteem
delegateejetsesprey
vesting shares5433.456812 VESTS
Transaction InfoBlock #91303334/Trx c0e2a1fa617c2001de7807fc53e3903071600770
View Raw JSON Data
{
  "trx_id": "c0e2a1fa617c2001de7807fc53e3903071600770",
  "block": 91303334,
  "trx_in_block": 3,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2024-12-17T07:23:45",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "jetsesprey",
      "vesting_shares": "5433.456812 VESTS"
    }
  ]
}
steemdelegated 3.441 SP to @jetsesprey
2023/11/13 23:06:03
delegatorsteem
delegateejetsesprey
vesting shares5602.590344 VESTS
Transaction InfoBlock #79857524/Trx fcfdcff9c37e571c4b013d6fa1741250533b311e
View Raw JSON Data
{
  "trx_id": "fcfdcff9c37e571c4b013d6fa1741250533b311e",
  "block": 79857524,
  "trx_in_block": 3,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2023-11-13T23:06:03",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "jetsesprey",
      "vesting_shares": "5602.590344 VESTS"
    }
  ]
}
steemdelegated 5.244 SP to @jetsesprey
2023/09/21 23:43:42
delegatorsteem
delegateejetsesprey
vesting shares8539.869130 VESTS
Transaction InfoBlock #78350101/Trx f7db7c131881673a76e1dec0f5fddf807e28254b
View Raw JSON Data
{
  "trx_id": "f7db7c131881673a76e1dec0f5fddf807e28254b",
  "block": 78350101,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2023-09-21T23:43:42",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "jetsesprey",
      "vesting_shares": "8539.869130 VESTS"
    }
  ]
}
steemdelegated 5.380 SP to @jetsesprey
2022/11/03 13:16:27
delegatorsteem
delegateejetsesprey
vesting shares8761.550568 VESTS
Transaction InfoBlock #69115137/Trx efc913f9a7b426cd3305d075940a90feb0646ed8
View Raw JSON Data
{
  "trx_id": "efc913f9a7b426cd3305d075940a90feb0646ed8",
  "block": 69115137,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-11-03T13:16:27",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "jetsesprey",
      "vesting_shares": "8761.550568 VESTS"
    }
  ]
}
steemdelegated 5.516 SP to @jetsesprey
2022/01/17 16:40:12
delegatorsteem
delegateejetsesprey
vesting shares8981.785704 VESTS
Transaction InfoBlock #60816236/Trx 525cf11b35cb3df7c73635db7e24a90b33675efe
View Raw JSON Data
{
  "trx_id": "525cf11b35cb3df7c73635db7e24a90b33675efe",
  "block": 60816236,
  "trx_in_block": 15,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-01-17T16:40:12",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "jetsesprey",
      "vesting_shares": "8981.785704 VESTS"
    }
  ]
}
steemdelegated 5.629 SP to @jetsesprey
2021/06/14 02:15:48
delegatorsteem
delegateejetsesprey
vesting shares9165.852457 VESTS
Transaction InfoBlock #54609452/Trx 29f75af7ad93b4e1cc161acadb867c39d3dcc06d
View Raw JSON Data
{
  "trx_id": "29f75af7ad93b4e1cc161acadb867c39d3dcc06d",
  "block": 54609452,
  "trx_in_block": 8,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-06-14T02:15:48",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "jetsesprey",
      "vesting_shares": "9165.852457 VESTS"
    }
  ]
}
steemdelegated 5.744 SP to @jetsesprey
2020/12/11 12:32:36
delegatorsteem
delegateejetsesprey
vesting shares9353.274431 VESTS
Transaction InfoBlock #49356852/Trx 3ccebff9d74ad803522fbd0ff1e130c9e6aa9e54
View Raw JSON Data
{
  "trx_id": "3ccebff9d74ad803522fbd0ff1e130c9e6aa9e54",
  "block": 49356852,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-12-11T12:32:36",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "jetsesprey",
      "vesting_shares": "9353.274431 VESTS"
    }
  ]
}
steemdelegated 1.174 SP to @jetsesprey
2020/12/06 06:09:21
delegatorsteem
delegateejetsesprey
vesting shares1912.543513 VESTS
Transaction InfoBlock #49208405/Trx 1fdaf61868151325716671bfdaa5c11e0ca81f64
View Raw JSON Data
{
  "trx_id": "1fdaf61868151325716671bfdaa5c11e0ca81f64",
  "block": 49208405,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-12-06T06:09:21",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "jetsesprey",
      "vesting_shares": "1912.543513 VESTS"
    }
  ]
}
steemdelegated 5.748 SP to @jetsesprey
2020/12/05 16:10:48
delegatorsteem
delegateejetsesprey
vesting shares9359.482285 VESTS
Transaction InfoBlock #49191949/Trx 85d9545a006ebe578810f8027f175b3bbbb518e5
View Raw JSON Data
{
  "trx_id": "85d9545a006ebe578810f8027f175b3bbbb518e5",
  "block": 49191949,
  "trx_in_block": 11,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-12-05T16:10:48",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "jetsesprey",
      "vesting_shares": "9359.482285 VESTS"
    }
  ]
}
steemdelegated 1.179 SP to @jetsesprey
2020/11/02 18:33:51
delegatorsteem
delegateejetsesprey
vesting shares1920.017158 VESTS
Transaction InfoBlock #48261248/Trx 1f6c6d188020004dcd85e4f94a5218fe8873964d
View Raw JSON Data
{
  "trx_id": "1f6c6d188020004dcd85e4f94a5218fe8873964d",
  "block": 48261248,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-11-02T18:33:51",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "jetsesprey",
      "vesting_shares": "1920.017158 VESTS"
    }
  ]
}
steemdelegated 5.872 SP to @jetsesprey
2020/05/09 07:08:12
delegatorsteem
delegateejetsesprey
vesting shares9562.287644 VESTS
Transaction InfoBlock #43218674/Trx 570a0e20fd1b1a005fea1c93b630ee07174e7cfa
View Raw JSON Data
{
  "trx_id": "570a0e20fd1b1a005fea1c93b630ee07174e7cfa",
  "block": 43218674,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-05-09T07:08:12",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "jetsesprey",
      "vesting_shares": "9562.287644 VESTS"
    }
  ]
}
steemdelegated 1.200 SP to @jetsesprey
2020/05/08 10:57:03
delegatorsteem
delegateejetsesprey
vesting shares1953.311140 VESTS
Transaction InfoBlock #43195016/Trx ded46725ecb614f4b84f428f983f24a67dd38365
View Raw JSON Data
{
  "trx_id": "ded46725ecb614f4b84f428f983f24a67dd38365",
  "block": 43195016,
  "trx_in_block": 12,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-05-08T10:57:03",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "jetsesprey",
      "vesting_shares": "1953.311140 VESTS"
    }
  ]
}
steemdelegated 5.905 SP to @jetsesprey
2020/01/29 01:51:15
delegatorsteem
delegateejetsesprey
vesting shares9616.410923 VESTS
Transaction InfoBlock #40339382/Trx 41e066136a4a6761765de552b434fa1d220fba8c
View Raw JSON Data
{
  "trx_id": "41e066136a4a6761765de552b434fa1d220fba8c",
  "block": 40339382,
  "trx_in_block": 10,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-01-29T01:51:15",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "jetsesprey",
      "vesting_shares": "9616.410923 VESTS"
    }
  ]
}
2019/04/20 21:15:36
parent authorjetsesprey
parent permlinkwhen-to-arbitrate-and-when-not-with-eos
authorsteemitboard
permlinksteemitboard-notify-jetsesprey-20190420t211536000z
title
bodyCongratulations @jetsesprey! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@jetsesprey/birthday1.png</td><td>Happy Birthday! - You are on the Steem blockchain for 1 year!</td></tr></table> <sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@jetsesprey) and compare to others on the [Steem Ranking](http://steemitboard.com/ranking/index.php?name=jetsesprey)_</sub> ###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!
json metadata{"image":["https://steemitboard.com/img/notify.png"]}
Transaction InfoBlock #32219844/Trx 8f7fcebfeba729ea96903804207c39a0f96032f3
View Raw JSON Data
{
  "trx_id": "8f7fcebfeba729ea96903804207c39a0f96032f3",
  "block": 32219844,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-04-20T21:15:36",
  "op": [
    "comment",
    {
      "parent_author": "jetsesprey",
      "parent_permlink": "when-to-arbitrate-and-when-not-with-eos",
      "author": "steemitboard",
      "permlink": "steemitboard-notify-jetsesprey-20190420t211536000z",
      "title": "",
      "body": "Congratulations @jetsesprey! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@jetsesprey/birthday1.png</td><td>Happy Birthday! - You are on the Steem blockchain for 1 year!</td></tr></table>\n\n<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@jetsesprey) and compare to others on the [Steem Ranking](http://steemitboard.com/ranking/index.php?name=jetsesprey)_</sub>\n\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
      "json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}"
    }
  ]
}
steemdelegated 6.026 SP to @jetsesprey
2019/02/28 16:04:03
delegatorsteem
delegateejetsesprey
vesting shares9812.870637 VESTS
Transaction InfoBlock #30747347/Trx 2a5a021b9a49136670d684288bff38f1b75f60fa
View Raw JSON Data
{
  "trx_id": "2a5a021b9a49136670d684288bff38f1b75f60fa",
  "block": 30747347,
  "trx_in_block": 35,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-02-28T16:04:03",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "jetsesprey",
      "vesting_shares": "9812.870637 VESTS"
    }
  ]
}
jetsespreyreceived 0.029 STEEM, 0.037 SP author reward for @jetsesprey / when-to-arbitrate-and-when-not-with-eos
2018/12/06 15:38:51
authorjetsesprey
permlinkwhen-to-arbitrate-and-when-not-with-eos
sbd payout0.000 SBD
steem payout0.029 STEEM
vesting payout60.386742 VESTS
Transaction InfoBlock #28329610/Virtual Operation #12
View Raw JSON Data
{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 28329610,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 12,
  "timestamp": "2018-12-06T15:38:51",
  "op": [
    "author_reward",
    {
      "author": "jetsesprey",
      "permlink": "when-to-arbitrate-and-when-not-with-eos",
      "sbd_payout": "0.000 SBD",
      "steem_payout": "0.029 STEEM",
      "vesting_payout": "60.386742 VESTS"
    }
  ]
}
2018/11/30 09:32:18
voterartakush
authorjetsesprey
permlinkwhen-to-arbitrate-and-when-not-with-eos
weight10000 (100.00%)
Transaction InfoBlock #28149549/Trx 50103474748448c06f5dbf7b5f43aeff24178eae
View Raw JSON Data
{
  "trx_id": "50103474748448c06f5dbf7b5f43aeff24178eae",
  "block": 28149549,
  "trx_in_block": 20,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-11-30T09:32:18",
  "op": [
    "vote",
    {
      "voter": "artakush",
      "author": "jetsesprey",
      "permlink": "when-to-arbitrate-and-when-not-with-eos",
      "weight": 10000
    }
  ]
}
2018/11/29 18:06:39
votersamupaha
authorjetsesprey
permlinkwhen-to-arbitrate-and-when-not-with-eos
weight10000 (100.00%)
Transaction InfoBlock #28131043/Trx 39c3ddb256e04abb1c69d7693865ae34a702d448
View Raw JSON Data
{
  "trx_id": "39c3ddb256e04abb1c69d7693865ae34a702d448",
  "block": 28131043,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-11-29T18:06:39",
  "op": [
    "vote",
    {
      "voter": "samupaha",
      "author": "jetsesprey",
      "permlink": "when-to-arbitrate-and-when-not-with-eos",
      "weight": 10000
    }
  ]
}
2018/11/29 16:53:33
votersensation
authorjetsesprey
permlinkwhen-to-arbitrate-and-when-not-with-eos
weight10000 (100.00%)
Transaction InfoBlock #28129581/Trx 57f22ca55f8a8f3ba9960064f1c9e2e224a211cb
View Raw JSON Data
{
  "trx_id": "57f22ca55f8a8f3ba9960064f1c9e2e224a211cb",
  "block": 28129581,
  "trx_in_block": 28,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-11-29T16:53:33",
  "op": [
    "vote",
    {
      "voter": "sensation",
      "author": "jetsesprey",
      "permlink": "when-to-arbitrate-and-when-not-with-eos",
      "weight": 10000
    }
  ]
}
steemdelegated 18.424 SP to @jetsesprey
2018/11/29 16:52:15
delegatorsteem
delegateejetsesprey
vesting shares30000.920352 VESTS
Transaction InfoBlock #28129555/Trx 5d0e3a1f6a71cd92b95b6e1ae49e87ebe8656b1b
View Raw JSON Data
{
  "trx_id": "5d0e3a1f6a71cd92b95b6e1ae49e87ebe8656b1b",
  "block": 28129555,
  "trx_in_block": 18,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-11-29T16:52:15",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "jetsesprey",
      "vesting_shares": "30000.920352 VESTS"
    }
  ]
}
2018/11/29 15:49:30
voterraise-me-up
authorjetsesprey
permlinkwhen-to-arbitrate-and-when-not-with-eos
weight1 (0.01%)
Transaction InfoBlock #28128301/Trx b7f7266b4806c8669b5304d6271dd1b46bdc5efc
View Raw JSON Data
{
  "trx_id": "b7f7266b4806c8669b5304d6271dd1b46bdc5efc",
  "block": 28128301,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-11-29T15:49:30",
  "op": [
    "vote",
    {
      "voter": "raise-me-up",
      "author": "jetsesprey",
      "permlink": "when-to-arbitrate-and-when-not-with-eos",
      "weight": 1
    }
  ]
}
2018/11/29 15:45:45
voterjamalgayoni
authorjetsesprey
permlinkwhen-to-arbitrate-and-when-not-with-eos
weight10000 (100.00%)
Transaction InfoBlock #28128226/Trx 70ad743b5a045763112cfde850ba819cf37e81ac
View Raw JSON Data
{
  "trx_id": "70ad743b5a045763112cfde850ba819cf37e81ac",
  "block": 28128226,
  "trx_in_block": 25,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-11-29T15:45:45",
  "op": [
    "vote",
    {
      "voter": "jamalgayoni",
      "author": "jetsesprey",
      "permlink": "when-to-arbitrate-and-when-not-with-eos",
      "weight": 10000
    }
  ]
}
2018/11/29 15:38:51
parent author
parent permlinkeos
authorjetsesprey
permlinkwhen-to-arbitrate-and-when-not-with-eos
titleWhen to arbitrate and when not with EOS
body![EOS AMSTERDAM LOGO IMG_20180612_173627_160.jpg](https://cdn.steemitimages.com/DQmWjBCAPvWMz7CmBxouKEdieTacdv4bm69ovTer2k34mwu/EOS%20AMSTERDAM%20LOGO%20IMG_20180612_173627_160.jpg) EOS is a governed blockchain. Which ruleset will govern EOS will be decided by the voters shortly. The current proposals have in common that they are agreements between all users of EOS (end users and dApps and block producers). Rules need to be enforced in order to be effective. Agreements can be enforced easily. Each of the parties to the EOS charter/constitution/agreement is entitled to demand fulfilment of another party’s obligations. Each party is entitled to claim damages with a defaulting party. There are many factions within EOS that strongly dislike any form of mandatory dispute resolution. Their views are that voting will, at the end of the day, rid the chain of bad players. This might be so, but that will not stop disputes from arising. This memo focuses on those disputes. The discussions have been very confusing. This memo provides an analysis of the various elements of dispute resolution. It is meant to align the discussions. To prevent further confusion and distinguish the different elements of the discussion in order to allow for a granular approach. Arbitration & Dispute Resolution (ADR) is not ECAF. If ADR is needed, any ADR provider that meets the standards and is willing to invest to get the necessary technical insights will do. The question addressed here is not whether EOS should have ECAF or not but where and when ADR could be a viable solution whomever shall be the provider of such ADR. **Dispute resolution and execution** First we need to be aware of the distinction between dispute resolution and the execution of the verdict/award. This seems self-evident but a lot of heated debates are in fact more about the execution (no arbitration on the base layer! as an example) and not about dispute resolution itself. Dispute resolution means that a third party decides a dispute between party a and b (or between party a on the one hand and parties b,c,d, etc on the other). This third party can be a judge or an arbitrator. Or a clan elder or a decision by 15 block producers. This is dispute resolution: not more (nor less) than having someone else decide who is wrong and who is right. Such decision has to be executed. In the old world court decisions are being executed by bailiffs and ultimately the police. Arbitrators’ awards are executed quite similarly: one has to get a court order (easily obtained in principle) and then such court order can be executed as any other court order. Execution happens inter alia by attaching and the forced selling of assets of the losing party. Within EOS only the block producers have the power to actually do something. We shall investigate if it is a good idea to use such powers within an ADR context. **Dispute resolution** In the event of a dispute there will always be a competent court. The question is therefore simple: when would arbitration (ADR) be better than courts? Obviously EOS dispute resolution should be limited to disputes connected with EOS. EOS is not there to provide ADR to all disputes of the world. Such EOS ADR solution will require arbitrators that know the law and know EOS. Further: this memo is not about voluntary arbitration. The parties concerned could always choose to go that route. If and when ADR is the best choice, the community should make it mandatory unless the parties concerned agree to opt out. We distinguish the various types of conflicts and will advice whether or not mandatory ADR is good, not necessary or bad. **Block producer vs block producer** Of course block producers work together diligently to make EOS a safe and efficient system. However, disputes may arise. E.g. if a block producer does not comply with the BP agreement, under all proposals that would mean other bps can claim their damages with such BP or claim fulfilment of such BP’s obligations. Another example is if a block producer provides false information about its competing block producers. Also, under the current Constitution, bps could sue in the event of vote buying. Block producers that did not buy votes, get a smaller amount of EOS. They are entitled to claim that damage with the vote buying parties. It makes sense to settle all of this through ADR. This is in the self interest of all block producers except for the ones, if any, that are planning not to comply. Lack of ADR will mean that block producers could get sued in their own country but, possibly, in many others too. A competent court can be found in a number of ways and the claimant will see to it that the defendant is being subpoenaed before the claimant’s home court. Not suitable for ADR are non-EOS disputes. E.g. a block producer could steal vital personnel from another one. This should not be dealt with through EOS ADR. **Block producer vs account holders** Disputes here may arise when EOS is down due to a mistake made by one or more block producers. This seems unlikely but it is not impossible. Another example is when a block producer fails to timely blacklist an account (provided that obligation will still be there in the charter/agreement that gets voted in by the community. Damages could be very high. Also block producers may be forced to block certain content (by blacklisting accounts) that is in the account holder’s jurisdiction perfectly legal. One could argue that the block producers provide just a technical infrastructure and cannot be liable, but that is legally not so. Block producers certainly can be liable. And if the damages and frustration of the other party are high enough, they will get sued. Again it makes sense to offer ADR here. Not only to protect the block producers against having to show up in a court that is alien to them, but also to offer a system to hold them accountable. Accountability of the block producers will raise trust in EOS. Also here disputes that have no relation to EOS should not be subject to ADR. So if a block producer’s CEO hit someone on the nose, it should not get through the ADR. **Account holder vs account holder** The number of conflicts is limitless. From theft through offering of securities without a license, from fraud to delivering goods and services that allegedly do not comply with the agreement etc. etc. It is not possible to address all of these highly diverging disputes in some catch all phrases. We have therefore broken down the various types and address them below: **Defaults regarding the agreement between user and dApp** E.g. the delivered goods or services are delivered late, they are not compliant, against the local law etc. There is hardly any added value here to provide ADR. The dispute has nothing to do with EOS. EOS is just the technical infrastructure. The claimant shall have to go to the court or to the ADR agreed upon with the dApp provider.Another point is that within such a broad array of disputes a specialized ADR body doesn’t have much added value. So no ADR in these cases. **Defaults regarding the offering of specific EOS services** These could be mistakes made with the buying and selling of EOS. The service provider, e.g. an exchange, could be liable in numerous ways. Here the choice whether or not there should be ADR is more difficult. Specialized ADR will have added value here. Also the possibility to hold parties that work with EOS accountable, will raise trust in the system. It will further provide a global recourse for victims of mistakes made by exchanges and other EOS service providers. For the EOS service providers ADR means they cannot be subpoenaed before the court of the claimant. In that sense ADR provides clarity and security for them as well. We believe therefore ADR here, might be preferable. **Theft and fraud** A lot has been said about theft and fraud. Of course having no theft or fraud is preferable, The EOS community works on ways to decrease that chance. However, we have to deal with the obvious: theft and fraud are here and probably will remain here. Legally a claim based on theft and fraud is mostly a claim by a known claimant against an unknown criminal. That doesn’t change the nature of the ADR: it is still dispute resolution between two parties: the thief and the rightful owner. ADR is not replacing the police in any way. ADR remains a ‘peer to peer’ dispute resolution. It is further obvious that local law enforcement cannot help the victim. They will not be able to find the thief. Also given the international character of EOS. Execution here is vital. In many of the other cases, onchain execution is not always necessary: one should easily be able to get a local court order and execute that. The defendants will often be tangible companies and if they are not, with ADR the claimant runs into the same executional issues as with a court case. The exception is probably only that onchain the block producers may blacklist a dApp: that is a effective way of executing an award that is just not there offchain.. In theft and fraud cases it is self evident that without ADR and onchain execution, a victim doesn’t have the means to get justice done. He doesn’t even know the thief’s identity. With ADR the victim will at least have an arbitrator’s award and just maybe, if he is lucky and execution of such awards has been a block producers’ task, he might get his EOS back. Of course in many cases the EOS will be gone given the current way EOS works.But also now accounts are effectively frozen and some people do get their EOS back. ADR should therefore be mandatory in these cases, provided there is some sort of execution of the awards. Efficient ADR will allow for more trust in the EOS system and will effectively allow justice to be done. Something that won’t happen without ADR. **Execution** ADR decides on cases between a claimant and a defendant (or more claimants and more defendants). The decision in a case does not lead to any obligations for anyone else than the parties unless generally applicable rules stipulate otherwise. A court order can be executed by the police and bailiffs since this is detailed in specific legislation. In such rules it is further detailed if and to which extend third parties will have obligations. E.g. a bank ( a third party) can be forced to pay sums that belong to the defendant to the claimant following a court order issued between those two parties. The same goes for an central exchange. Within EOS itself only one type of actors can actually do something: block producers. 15 out of 21 active block producers can do all they wish with accounts. It is therefore technically possible for them to jointly execute awards in the event that can be done by blacklisting or seizing the EOS on an account. If it is possible, should they be obliged to do so? Surely the block producers would prefer not to. Executing awards and other verdicts is not automated yet. It is hardly scalable and therefore a costly and risky operation. Risky since mistakes will be made (and are made) and such mistakes might cost the respective block producer dearly. But without execution, the ADR system fails in a number of cases. And without ADR the legal insecurity and risks for all would grow considerably. Therefore within the limited scope an ADR result should be executable by the block producers. The execution block producers do should be carefully detailed and also be limited to the minimum that is necessary to make ADR functioning. We believe that will include blacklisting accounts. And restoring the original owner to an account in case of theft. Please note that such restoring can only be done following an ADR award. The arbitrators shall have to carefully establish whether the original owner can proof ownership. If not, they should refuse to grant the award. As for executing ADR awards that grant damages to a party, block producers could also seize EOS on an account and pay those to the claimant. They could, but we are not sure if they should. The powers to attach EOS on accounts are scary. It could be tempting for block producers to seize EOS without the proper proceedings. On the other hand, providing the possibility to seize online assets, such as EOS, will help to make EOS mainstream. And will help to establish effective ADR. We take due notice of the fact that ADR may be flawed and in some countries offline courts not being as impartial as in others. We therefore support the idea of an extra protection of the defendant. An ADR that results in the seizure of EOS should therefore only be executed with a court order from the country in which the defendant lives. This rule protects the defendant and respects the various cultural differences of this planet. Please note that given the current rules on liability of providers of digital services in the EU, the block producers may already be liable in the event they are aware of something illegal (theft, illegal dApp) and don’t take action to stop that illegal situation. In other words: it is very well possible that block producers don’t have a choice but to execute since not executing would mean to become liable for letting an illegal situation continue.. **Conclusion** We believe there should be limited ADR. And a limited package of executive actions with the block producers in order to make EOS a functioning governed blockchain. Block producers should blacklist accounts upon an ADR decision. Block produces should further execute ADR awards by transferring EOS but such transferring only following an ADR decision and a confirmation by a competent court in the defendant’s home country. Amsterdam, 29 November 2018
json metadata{"tags":["eos","blockchain","governance"],"image":["https://cdn.steemitimages.com/DQmWjBCAPvWMz7CmBxouKEdieTacdv4bm69ovTer2k34mwu/EOS%20AMSTERDAM%20LOGO%20IMG_20180612_173627_160.jpg"],"app":"steemit/0.1","format":"markdown"}
Transaction InfoBlock #28128088/Trx d334aab0bb611e5636c4ac91462bd04f6df36b60
View Raw JSON Data
{
  "trx_id": "d334aab0bb611e5636c4ac91462bd04f6df36b60",
  "block": 28128088,
  "trx_in_block": 17,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-11-29T15:38:51",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "eos",
      "author": "jetsesprey",
      "permlink": "when-to-arbitrate-and-when-not-with-eos",
      "title": "When to arbitrate and when not with EOS",
      "body": "![EOS AMSTERDAM LOGO IMG_20180612_173627_160.jpg](https://cdn.steemitimages.com/DQmWjBCAPvWMz7CmBxouKEdieTacdv4bm69ovTer2k34mwu/EOS%20AMSTERDAM%20LOGO%20IMG_20180612_173627_160.jpg)\n\n\n\n\n\n\n\nEOS is a governed blockchain. Which ruleset will govern EOS will be decided by the voters shortly. The current proposals have in common that they are agreements between all users of EOS (end users and dApps and block producers).  \n\nRules need to be enforced in order to be effective. Agreements can be enforced easily. Each of the parties to the EOS charter/constitution/agreement is entitled to demand fulfilment of another party’s obligations. Each party is entitled to claim damages with a defaulting party.\n\nThere are many factions within EOS that strongly dislike any form of mandatory dispute resolution. Their views are that voting will, at the end of the day, rid the chain of bad players. This might be so, but that will not stop disputes from arising. This memo focuses on those disputes. \n\nThe discussions have been very confusing. This memo provides an analysis of the various elements of dispute resolution. It is meant to align the discussions. To prevent further confusion and distinguish the different elements of the discussion in order to allow for a granular approach.\n\nArbitration & Dispute Resolution (ADR) is not ECAF. If ADR is needed, any ADR provider that meets the standards and is willing to invest to get the necessary technical insights will do. \n\nThe question addressed here is not whether EOS should have ECAF or not but where and when ADR could be a viable solution whomever shall be the provider of such ADR.\n\n**Dispute resolution and execution**\n\nFirst we need to be aware of the distinction between dispute resolution and the execution of the verdict/award. This seems self-evident but a lot of heated debates are in fact more about the execution (no arbitration on the base layer! as an example) and not about dispute resolution itself.\n\nDispute resolution means that a third party decides a dispute between party a and b (or between party a on the one hand and parties b,c,d, etc on the other). This third party can be a judge or an arbitrator. Or a clan elder or a decision by 15 block producers. This is dispute resolution: not more (nor less) than having someone else decide who is wrong and who is right. \n\nSuch decision has to be executed. In the old world court decisions are being executed by bailiffs and ultimately the police. Arbitrators’ awards are executed quite similarly: one has to get a court order (easily obtained in principle) and then such court order can be executed as any other court order. Execution happens inter alia by attaching and the forced selling of assets of the losing party. Within EOS only the block producers have the power to actually do something.  We shall investigate if it is a good idea to use such powers within an ADR context.\n\n**Dispute resolution**  \n\nIn the event of a dispute there will always be a competent court. The question is therefore simple: when would arbitration (ADR)  be better than courts? \n\nObviously EOS dispute resolution should be limited to disputes connected with EOS. EOS is not there to provide ADR to all disputes of the world. Such EOS ADR solution will require arbitrators that know the law and know EOS. \n\nFurther: this memo is not about voluntary arbitration. The parties concerned could always choose to go that route. If and when ADR is the best choice, the community should make it mandatory unless the parties concerned agree to opt out.\n\nWe distinguish the various types of conflicts and will advice whether or not mandatory ADR is good, not necessary or bad. \n\n**Block producer vs block producer**\n \nOf course block producers work together diligently to make EOS a safe and efficient system. \n\nHowever, disputes may arise. E.g. if a block producer does not comply with the BP agreement, under all proposals that would mean other bps can claim their damages with such BP or claim fulfilment of such BP’s obligations. Another example is if a block producer provides false information about its competing block producers. \n\nAlso, under the current Constitution, bps could sue in the event of vote buying. Block producers that did not buy votes, get a smaller amount of EOS. They are entitled to claim that damage with the vote buying parties.\n\nIt makes sense to settle all of this through ADR. This is in the self interest of all block producers except for the ones, if any, that are planning not to comply. Lack of ADR will mean that block producers could get sued in their own country but, possibly, in many others too. A competent court can be found in a number of ways and the claimant will see to it that the defendant is being subpoenaed before the claimant’s home court. \n\nNot suitable for ADR are non-EOS disputes. E.g. a block producer could steal vital personnel from another one. This should not be dealt with through EOS ADR.\n\n**Block producer vs account holders**\n\nDisputes here may arise when EOS is down due to a mistake made by one or more block producers. This seems unlikely but it is not impossible. Another example is when a block producer fails to timely blacklist an account (provided that obligation will still be there in the charter/agreement that gets voted in by the community. \n\nDamages could be very high. Also block producers may be forced to block certain content (by blacklisting accounts) that is in the account holder’s  jurisdiction perfectly legal. \n\nOne could argue that the block producers provide just a technical infrastructure and cannot be liable, but that is legally not so. Block producers certainly can be liable. And if the damages and frustration of the other party are high enough, they will get sued.\n\nAgain it makes sense to offer ADR here. Not only to protect the block producers against having to show up in a court that is alien to them, but also to offer a system to hold them accountable. Accountability of the block producers will raise trust in EOS. \n\nAlso here disputes that have no relation to EOS should not be subject to ADR. So if a block producer’s CEO hit someone on the nose, it should not get through the ADR.\n\n**Account holder vs account holder**\n\nThe number of conflicts is limitless. From theft through offering of securities without a license, from fraud to delivering goods and services that allegedly do not comply with the agreement etc. etc.\n\nIt is not possible to address all of these highly diverging disputes in some catch all phrases. We have therefore broken down the various types and address them below:\n\n**Defaults regarding the agreement between user and dApp**\n\nE.g. the delivered goods or services are delivered late, they are not compliant, against the local law etc. \n\nThere is hardly any added value here to provide ADR. The dispute has nothing to do with EOS. EOS is just the technical infrastructure. The claimant shall have to go to the court or to the ADR agreed upon with the dApp provider.Another point is that within such a broad array of disputes a specialized ADR body doesn’t have much added value. \n\nSo no ADR in these cases.\n\n**Defaults regarding the offering of specific EOS services**\n\nThese could be mistakes made with the buying and selling of EOS. The service provider, e.g. an exchange, could be liable in numerous ways. Here the choice whether or not there should be ADR is more difficult. Specialized ADR will have added value here. Also the possibility to hold parties that work with EOS accountable, will raise trust in the system. It will further provide a global recourse for victims of mistakes made by exchanges and other EOS service providers. \n\nFor the EOS service providers ADR means they cannot be subpoenaed before the court of the claimant. In that sense ADR provides clarity and security for them as well. \n\nWe believe therefore ADR here, might be preferable. \n\n**Theft and fraud**\n\nA lot has been said about theft and fraud. Of course having no theft or fraud is preferable, The EOS community works on ways to decrease that chance. However, we have to deal with the obvious: theft and fraud are here and probably will remain here. \n\nLegally a claim based on theft and fraud is mostly a claim by a known claimant against an unknown criminal. That doesn’t change the nature of the ADR: it is still dispute resolution between two parties: the thief and the rightful owner. ADR is not replacing the police in any way. ADR remains a ‘peer to peer’ dispute resolution.\n\nIt is further obvious that local law enforcement cannot help the victim. They will not be able to find the thief. Also given the international character of EOS.\n\nExecution here is vital. In many of the other cases, onchain execution is not always necessary: one should easily be able to get a local court order and execute that. The defendants will often be tangible companies and if they are not, with ADR the claimant runs into the same executional issues as with a court case. The exception is probably only that onchain the block producers may blacklist a dApp: that is a effective way of executing an award that is just not there offchain.. \n\nIn theft and fraud cases it is self evident that without ADR and onchain execution, a victim doesn’t have the means to get justice done. He doesn’t even know the thief’s identity. With ADR the victim will at least have an arbitrator’s award and just maybe, if he is lucky and execution of such awards has been a block producers’ task, he might get his EOS back. Of course in many cases the EOS will be gone given the current way EOS works.But also now accounts are effectively frozen and some people do get their EOS back. \n\nADR should therefore be mandatory in these cases, provided there is some sort of execution of the awards. Efficient ADR will allow for more trust in the EOS system and will effectively allow justice to be done. Something that won’t happen without ADR.\n\n**Execution**\n\nADR decides on cases between a claimant and a defendant (or more claimants and more defendants). The decision in a case does not lead to any obligations for anyone else than the parties unless generally applicable rules stipulate otherwise. \n\nA court order can be executed by the police and bailiffs since this is detailed in specific legislation. In such rules it is further detailed if and to which extend third parties will have obligations. E.g. a bank ( a third party) can be forced to pay sums that belong to the defendant to the claimant following a court order issued between those two parties. The same goes for an central exchange.\n\nWithin EOS itself only one type of actors can actually do something: block producers. \n\n15 out of 21 active block producers can do all they wish with accounts. It is therefore technically possible for them to jointly execute awards in the event that can be done by blacklisting or seizing the EOS on an account. \n\nIf it is possible, should they be obliged to do so? Surely the block producers would prefer not to. Executing awards and other verdicts is not automated yet. It is hardly scalable and therefore a costly and risky operation. Risky since mistakes will be made (and are made) and such mistakes might cost the respective block producer dearly. \n\nBut without execution, the ADR system fails in a number of cases. And without ADR the legal insecurity and risks for all would grow considerably. Therefore within the limited scope an ADR result should be executable by the block producers. \n\nThe execution block producers do should be carefully detailed and also be limited to the minimum that is necessary to make ADR functioning. We believe that will include blacklisting accounts. And restoring the original owner to an account in case of theft. Please note that such restoring can only be done following an ADR award. The arbitrators shall have to carefully establish whether the original owner can proof ownership. If not, they should refuse to grant the award.\n\nAs for executing ADR awards that grant damages to a party, block producers could also seize EOS on an account and pay those to the claimant. They could, but we are not sure if they should. The powers to attach EOS on accounts are scary. It could be tempting for block producers to seize EOS without the proper proceedings. On the other hand, providing the possibility to seize online assets, such as EOS, will help to make EOS mainstream. And will help to establish effective ADR.\n\nWe take due notice of the fact that ADR may be flawed and in some countries offline courts not being as impartial as in others. We therefore support the idea of an extra protection of the defendant. An ADR that results in the seizure of EOS should therefore only be executed with a court order from the country in which the defendant lives. This rule protects the defendant and respects the various cultural differences of this planet.\n\nPlease note that given the current rules on liability of providers of digital services in the EU, the block producers may already be liable in the event they are aware of something illegal (theft, illegal dApp) and don’t take action to stop that illegal situation. In other words: it is very well possible that block producers don’t have a choice but to execute since not executing would mean to become liable for letting an illegal situation continue.. \n\n**Conclusion**\n\nWe believe there should be limited ADR. And a limited package of executive actions with the block producers in order to make EOS a functioning governed blockchain. Block producers should blacklist accounts upon an ADR decision. Block produces should further execute ADR awards by transferring EOS but such transferring only following an ADR decision and a confirmation by a competent court in the defendant’s home country.\n\n\nAmsterdam, 29 November 2018",
      "json_metadata": "{\"tags\":[\"eos\",\"blockchain\",\"governance\"],\"image\":[\"https://cdn.steemitimages.com/DQmWjBCAPvWMz7CmBxouKEdieTacdv4bm69ovTer2k34mwu/EOS%20AMSTERDAM%20LOGO%20IMG_20180612_173627_160.jpg\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}
steemdelegated 6.059 SP to @jetsesprey
2018/11/26 18:00:15
delegatorsteem
delegateejetsesprey
vesting shares9866.162104 VESTS
Transaction InfoBlock #28044546/Trx f2db5f37ecdf7b726e8afa5145c8f567f8421f35
View Raw JSON Data
{
  "trx_id": "f2db5f37ecdf7b726e8afa5145c8f567f8421f35",
  "block": 28044546,
  "trx_in_block": 14,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-11-26T18:00:15",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "jetsesprey",
      "vesting_shares": "9866.162104 VESTS"
    }
  ]
}
steemdelegated 18.520 SP to @jetsesprey
2018/08/25 10:35:06
delegatorsteem
delegateejetsesprey
vesting shares30157.464451 VESTS
Transaction InfoBlock #25374685/Trx 0adf0efa47fa3cdb14d29cbb100628f428fc7f8f
View Raw JSON Data
{
  "trx_id": "0adf0efa47fa3cdb14d29cbb100628f428fc7f8f",
  "block": 25374685,
  "trx_in_block": 5,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-25T10:35:06",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "jetsesprey",
      "vesting_shares": "30157.464451 VESTS"
    }
  ]
}
2018/08/01 11:54:24
parent authorjetsesprey
parent permlinkeos-dapp-producers-gdpr-help-offered
authororaclechain
permlinkre-jetsesprey-eos-dapp-producers-gdpr-help-offered-20180801t115424612z
title
bodyHey,Is the basic privacy advice only provide the other demands that come with EU privacy regulation?
json metadata{"tags":["privacy"],"app":"steemit/0.1"}
Transaction InfoBlock #24685350/Trx 3e07a61db5a25855d7e21ad5ed23a2afa7f9c2c3
View Raw JSON Data
{
  "trx_id": "3e07a61db5a25855d7e21ad5ed23a2afa7f9c2c3",
  "block": 24685350,
  "trx_in_block": 30,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-01T11:54:24",
  "op": [
    "comment",
    {
      "parent_author": "jetsesprey",
      "parent_permlink": "eos-dapp-producers-gdpr-help-offered",
      "author": "oraclechain",
      "permlink": "re-jetsesprey-eos-dapp-producers-gdpr-help-offered-20180801t115424612z",
      "title": "",
      "body": "Hey,Is the basic privacy advice only provide the other demands that come with EU privacy regulation?",
      "json_metadata": "{\"tags\":[\"privacy\"],\"app\":\"steemit/0.1\"}"
    }
  ]
}
2018/08/01 11:53:21
voteroraclechain
authorjetsesprey
permlinkeos-dapp-producers-gdpr-help-offered
weight10000 (100.00%)
Transaction InfoBlock #24685329/Trx ac1b2e243d740bf15523c3482add75022d17bbfb
View Raw JSON Data
{
  "trx_id": "ac1b2e243d740bf15523c3482add75022d17bbfb",
  "block": 24685329,
  "trx_in_block": 48,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-01T11:53:21",
  "op": [
    "vote",
    {
      "voter": "oraclechain",
      "author": "jetsesprey",
      "permlink": "eos-dapp-producers-gdpr-help-offered",
      "weight": 10000
    }
  ]
}
2018/08/01 11:27:09
votertsto
authorjetsesprey
permlinkeos-dapp-producers-gdpr-help-offered
weight10000 (100.00%)
Transaction InfoBlock #24684807/Trx bb5231c815986c2efed5cc58f572c9b254612ad3
View Raw JSON Data
{
  "trx_id": "bb5231c815986c2efed5cc58f572c9b254612ad3",
  "block": 24684807,
  "trx_in_block": 37,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-01T11:27:09",
  "op": [
    "vote",
    {
      "voter": "tsto",
      "author": "jetsesprey",
      "permlink": "eos-dapp-producers-gdpr-help-offered",
      "weight": 10000
    }
  ]
}
2018/08/01 10:40:21
parent authorjetsesprey
parent permlinkeos-dapp-producers-gdpr-help-offered
authoreosdublin
permlinkre-jetsesprey-eos-dapp-producers-gdpr-help-offered-20180801t104021306z
title
bodyGood post and service! Thank you.
json metadata{"tags":["privacy"],"app":"steemit/0.1"}
Transaction InfoBlock #24683871/Trx 0cc5a6b35b40d19cc01b8178318d58d092b98b7b
View Raw JSON Data
{
  "trx_id": "0cc5a6b35b40d19cc01b8178318d58d092b98b7b",
  "block": 24683871,
  "trx_in_block": 32,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-01T10:40:21",
  "op": [
    "comment",
    {
      "parent_author": "jetsesprey",
      "parent_permlink": "eos-dapp-producers-gdpr-help-offered",
      "author": "eosdublin",
      "permlink": "re-jetsesprey-eos-dapp-producers-gdpr-help-offered-20180801t104021306z",
      "title": "",
      "body": "Good post and service! Thank you.",
      "json_metadata": "{\"tags\":[\"privacy\"],\"app\":\"steemit/0.1\"}"
    }
  ]
}
2018/08/01 09:40:36
voterfastresteem
authorjetsesprey
permlinkeos-dapp-producers-gdpr-help-offered
weight100 (1.00%)
Transaction InfoBlock #24682677/Trx cda5137ddb2b043aedfb191d8a5a618ada36623f
View Raw JSON Data
{
  "trx_id": "cda5137ddb2b043aedfb191d8a5a618ada36623f",
  "block": 24682677,
  "trx_in_block": 38,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-01T09:40:36",
  "op": [
    "vote",
    {
      "voter": "fastresteem",
      "author": "jetsesprey",
      "permlink": "eos-dapp-producers-gdpr-help-offered",
      "weight": 100
    }
  ]
}
2018/08/01 09:40:27
parent author
parent permlinkprivacy
authorjetsesprey
permlinkeos-dapp-producers-gdpr-help-offered
titleEOS dApp producers: GDPR help offered
bodyPrivacy might not be the first thing you are concerned with when working on your dApp but it should. Some simple principles you need to abide by NOW will save you a lot of trouble later on. That is, if you want your dApp to serve European Union citizens too. Citizens that together form the second biggest market of the planet: the European Union. EOS Amsterdam provides basic privacy advice on your worker proposals or other projects. Like: when do I need consent. How can I work around consent? How do I get consent if needed? Could it be given with the acceptance of my T&C? What are the other demands that come with EU privacy regulation? If you send in your project we shall provide you with our high level first impression of your proposal. This will enable you to tweak the proposal to better align with the EU privacy regulation, believed to be the strictest in the world. Together we’ll establish a reasonable compensation for our work. Depending on the complexity of your dApp. To be determined before we begin working. We’ll help you all the way with your questions or if you want to double check the implementation of our advice. We can also provide you with a legal opinion regarding the compliance of your dApp. Costs of which we’ll determine on a case by case basis or on the basis of our standard fees. These are the privacy principles you need to work with right now: 1. Data minimization. Don’t collect, store or use more personal data than you need. 2. Legal basis: If you really need the data to execute a contract: fine. If not check if you feel intrusive (e.g. if you follow people on or offline you are intrusive). If you feel you are intrusive, ask consent. Try to avoid bundled consent. There should be a real choice for the data subjects. 3. Ensure that the personal data can be deleted/changed. Think hard which data you store where. It makes all the difference. That’s also important because of the principle of data minimization. 4. Keep an eye on security. Security requirements are of a high standard in the EU. Security needs to balance the risks, costs and technological possibilities. This is a challenge since vulnerabilities are discovered every day which results in technology that seems to have become a fast moving target.
json metadata{"tags":["privacy","gdpr","ass"],"app":"steemit/0.1","format":"markdown"}
Transaction InfoBlock #24682674/Trx 8f873285be8d36b54ae9d5629e3bdcec48db10b6
View Raw JSON Data
{
  "trx_id": "8f873285be8d36b54ae9d5629e3bdcec48db10b6",
  "block": 24682674,
  "trx_in_block": 122,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-01T09:40:27",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "privacy",
      "author": "jetsesprey",
      "permlink": "eos-dapp-producers-gdpr-help-offered",
      "title": "EOS dApp producers: GDPR help offered",
      "body": "Privacy might not be the first thing you are concerned with when working on your dApp but it should. Some simple principles you need to abide by NOW will save you a lot of trouble later on. That is, if you want your dApp to serve European Union citizens too. Citizens that together form the second biggest market of the planet: the European Union.\n\nEOS Amsterdam provides basic privacy advice on your worker proposals or other projects. Like: when do I need consent. How can I work around consent? How do I get consent if needed? Could it be given with the acceptance of my T&C? What are the other demands that come with EU privacy regulation? \n\nIf you send in your project we shall provide you with our high level first impression of your proposal. This will enable you to tweak the proposal to better align with the EU privacy regulation, believed to be the strictest in the world. \n\nTogether we’ll establish a reasonable compensation for our work. Depending on the complexity of your dApp. To be determined before we begin working.\n\nWe’ll help you all the way with your questions or if you want to double check the implementation of our advice. We can also provide you with a legal opinion regarding the compliance of your dApp. Costs of which we’ll determine on a case by case basis or on the basis of our standard fees.\n\nThese are the privacy principles you need to work with right now:\n1. Data minimization. Don’t collect, store or use more personal data than you need.\n2. Legal basis: If you really need the data to execute a contract: fine. If not check if you feel intrusive (e.g. if you follow people on or offline you are intrusive). If you feel you are intrusive, ask consent. Try to avoid bundled consent. There should be a real choice for the data subjects.\n3. Ensure that the personal data can be deleted/changed. Think hard which data you store where. It makes all the difference. That’s also important because of the principle of data minimization.\n4. Keep an eye on security. Security requirements are of a high standard in the EU. Security needs to balance the risks, costs and technological possibilities. This is a challenge since vulnerabilities are discovered every day which results in technology that seems to have become a fast moving target.",
      "json_metadata": "{\"tags\":[\"privacy\",\"gdpr\",\"ass\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}
2018/07/18 17:52:06
votersensation
authorjetsesprey
permlinkchoices-when-drafting-a-new-constitution-for-an-eos-decentralized-community-platform-aa1e950e475cd
weight10000 (100.00%)
Transaction InfoBlock #24289996/Trx 709164da7703a5c2716fddcf9fa0d41b6aa59156
View Raw JSON Data
{
  "trx_id": "709164da7703a5c2716fddcf9fa0d41b6aa59156",
  "block": 24289996,
  "trx_in_block": 25,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-07-18T17:52:06",
  "op": [
    "vote",
    {
      "voter": "sensation",
      "author": "jetsesprey",
      "permlink": "choices-when-drafting-a-new-constitution-for-an-eos-decentralized-community-platform-aa1e950e475cd",
      "weight": 10000
    }
  ]
}
2018/07/18 16:45:54
authorjetsesprey
permlinkchoices-when-drafting-a-new-constitution-for-an-eos-decentralized-community-platform-aa1e950e475cd
max accepted payout1000000.000 SBD
percent steem dollars10000
allow votestrue
allow curation rewardstrue
extensions[[0,{"beneficiaries":[{"account":"esteemapp","weight":1000}]}]]
Transaction InfoBlock #24288672/Trx b73c87ed3570b6ce54ba630083ba5f2c9ea9b494
View Raw JSON Data
{
  "trx_id": "b73c87ed3570b6ce54ba630083ba5f2c9ea9b494",
  "block": 24288672,
  "trx_in_block": 33,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-07-18T16:45:54",
  "op": [
    "comment_options",
    {
      "author": "jetsesprey",
      "permlink": "choices-when-drafting-a-new-constitution-for-an-eos-decentralized-community-platform-aa1e950e475cd",
      "max_accepted_payout": "1000000.000 SBD",
      "percent_steem_dollars": 10000,
      "allow_votes": true,
      "allow_curation_rewards": true,
      "extensions": [
        [
          0,
          {
            "beneficiaries": [
              {
                "account": "esteemapp",
                "weight": 1000
              }
            ]
          }
        ]
      ]
    }
  ]
}
2018/07/18 16:45:54
parent author
parent permlinkeos
authorjetsesprey
permlinkchoices-when-drafting-a-new-constitution-for-an-eos-decentralized-community-platform-aa1e950e475cd
titleChoices when drafting a new constitution for an EOS decentralized community platform
bodyIntroduction A constitution is about distributing power and checks on that power in such a way that the community rules in a fair way. EOS Amsterdam is supporting the community. We have decades of experience in setting up governance structures onboard. This memo is meant to share that knowledge and help the community to vote and to help drafting. This memo aims to bring focus to the current debate.   We have identified bodies and functions. Power is about allocating functions to bodies. Governing is about splitting power to allow for checks (anti-corruption) to ensure the community benefits. With EOS bodies operate decentralized. A body in a constitutional sense could consist of multiple entities. E.g. BPs. Onchain and offchain are intertwined. There are numerous levels of interaction. If the constitution is improperly drafted, offchain will overrule onchain. We want to prevent that as much as possible. For the sake of predictability for all and of compliance management. Otherwise we would have to deal with huge regional differences. At first we have to do some soul searching: what are we? What we are We should try and define our community. Only after doing so, we can effectively talk about how to rule. We need to know what to rule before we make decisions on how to rule. We are EOS. We provide a self sustained technical infrastructure that will allow billions of people to organize their lives and businesses. The fundamental question is: do we want to meddle with how people do that or do we just want to provide a sustainable infrastructure? We at EOS Amsterdam believe the latter. We shouldn't enlarge our scope to happiness or prosperity for all. It's too vague. We believe strongly EOS might help to achieve a lot of that, but that doesn't mean such moral notions should interfere with our work. In that respect the current constitution is too broadly written. The Community The community is the highest body. From the community stems all other power. The community determines the constitution and as many other rules as they deem fit. But its powers shouldn't be unlimited. The individual member should be protected as well as minorities. Protecting individuals and minorities is typically done by providing fundamental rights such as right to property, the right not to be judged for actions that took place before a rule was implemented, the right to be judged by an impartial judge and the like. Further the minorities are protected because the constitution cannot be changed with a simple majority of the votes. As is the case in both EOS constitutions. Block producers, dApp devs, users The constitution defines which body does the actual work. Who is responsible for what. If we were to elect one body to control the chain, this body would be omnipotent. Such body could do as it pleases. Therefore a good constitution splits up the power of such body. This is done, in both versions of the constitution, by making such bodies subject to voting (BPs) and arbitration (all). Basically this is taking power away from the executive and redistribute that powers to the community and arbitration. Having said that, let's look at the various actors and their powers. BPs Block producers control the chain but in our view they do so by providing a technical commodity. They shouldn't be deciding about good or bad, about lawful or unlawful. About compliance. They should run the chain and keep it healthy. Just like a good ISP does in the old world. They should follow code. However, BPs should also implement verdicts. E.g. freeze accounts that are stolen. But never on their own initiative. Only when they are compelled to do so by a ruling by an arbitrator of by a judge. Arbitration could be within EOS but also an offchain judge could order a BP to act in a certain way and such BP would have no other choice than to comply. To us, as BP, code is law as are rulings issued following due process. BPs should in essence be blind to the morality or compliance with laws of the work they do. Only extraordinary circumstances may force a BP to act outside of these limits. dApp devs The dApp devs interact with the users. They have a far broader responsibility. They must ensure compliance with outside rules and regulations. For them code isn't always law. They can introduce all kinds of criteria. Like "fair".  Users Users are, eventually, the real actors on EOS. Once a dApp is onchain the responsibility to use such dApp will be the users'. Each user will be responsible and liable for such user's own acts or omissions. Even if the dApp itself is against the law, the user pays the price. Users are also fully subject to arbitration. Checks and balances: arbitrators The work of a body should be controlled. Otherwise power can be abused. Checks and balances need to be in place. This can obviously not be a voluntary pick. No one would voluntarily chose to be punished. BPs have a huge responsibility. They control the chain. There are checks in place. The first one is that the community can vote a non-functioning BP out. This is an extremely important check on their work. However this isn't sufficient since for a profound change in votes to take place the wrongdoing must be widely known. Further voting happens after the act and doesn't compensate for damage done. Therefore we need further checks. The dApp devs and the users should also be controlled. There should be means to stop illegal actions. If an illegal dApp is running, it should be stopped. This would typically be after complaints of users or against users. Someone has to ensure such dApp is removed.  That someone shouldn't be a block producer. A block producer doesn't have an opinion. We execute. So we need courts. Or arbitration. The choice is do we provide courts (arbitration) ourselves or do we let outside courts interfere. Own arbitration is preferable since the arbitrators will then apply as much as possible one worldwide EOS rule set. It is possible to limit the scope of our own arbitration but that will result in plaintiffs seeking remedy with outside courts for all that fall without such limited scope. Therefore also bonds do not help. They limit exposure and will leave room for outside courts to step in. in order to work, arbitration should be mandatory. All EOS members should be bound to it. Conclusion We encourage every member of the EOS community to debate further on the best choices to make. We have offered our in depth knowledge hereinabove. We are willing and eager to further participate in the discussions. To serve our EOS community. Amsterdam 18 July 2018
json metadata{"tags":["eos","constitution"],"app":"esteem/1.6.0","format":"markdown+html","community":"esteem"}
Transaction InfoBlock #24288672/Trx b73c87ed3570b6ce54ba630083ba5f2c9ea9b494
View Raw JSON Data
{
  "trx_id": "b73c87ed3570b6ce54ba630083ba5f2c9ea9b494",
  "block": 24288672,
  "trx_in_block": 33,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-07-18T16:45:54",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "eos",
      "author": "jetsesprey",
      "permlink": "choices-when-drafting-a-new-constitution-for-an-eos-decentralized-community-platform-aa1e950e475cd",
      "title": "Choices when drafting a new constitution for an EOS decentralized community platform",
      "body": "Introduction\n\nA constitution is about distributing power and checks on that power in such a way that the community rules in a fair way. \n\nEOS Amsterdam is supporting the community. We have decades of experience in setting up governance structures onboard. This memo is meant to share that knowledge and help the community to vote and to help drafting. This memo aims to bring focus to the current debate.   \n\nWe have identified bodies and functions. Power is about allocating functions to bodies. Governing is about splitting power to allow for checks (anti-corruption) to ensure the community benefits. With EOS bodies operate decentralized. A body in a constitutional sense could consist of multiple entities. E.g. BPs.\n\nOnchain and offchain are intertwined. There are numerous levels of interaction. If the constitution is improperly drafted, offchain will overrule onchain. We want to prevent that as much as possible. For the sake of predictability for all and of compliance management. Otherwise we would have to deal with huge regional differences.\n\nAt first we have to do some soul searching: what are we?\n\nWhat we are\n\nWe should try and define our community. Only after doing so, we can effectively talk about how to rule. We need to know what to rule before we make decisions on how to rule.\n\nWe are EOS. We provide a self sustained technical infrastructure that will allow billions of people to organize their lives and businesses. \n\nThe fundamental question is: do we want to meddle with how people do that or do we just want to provide a sustainable infrastructure? We at EOS Amsterdam believe the latter. We shouldn't enlarge our scope to happiness or prosperity for all. It's too vague. We believe strongly EOS might help to achieve a lot of that, but that doesn't mean such moral notions should interfere with our work. In that respect the current constitution is too broadly written.\n\nThe Community\n\nThe community is the highest body. From the community stems all other power. The community determines the constitution and as many other rules as they deem fit. But its powers shouldn't be unlimited. The individual member should be protected as well as minorities. \n\nProtecting individuals and minorities is typically done by providing fundamental rights such as right to property, the right not to be judged for actions that took place before a rule was implemented, the right to be judged by an impartial judge and the like. Further the minorities are protected because the constitution cannot be changed with a simple majority of the votes. As is the case in both EOS constitutions.\n\nBlock producers, dApp devs, users\n\nThe constitution defines which body does the actual work. Who is responsible for what. If we were to elect one body to control the chain, this body would be omnipotent. Such body could do as it pleases. Therefore a good constitution splits up the power of such body. This is done, in both versions of the constitution, by making such bodies subject to voting (BPs) and arbitration (all). Basically this is taking power away from the executive and redistribute that powers to the community and arbitration.\n\nHaving said that, let's look at the various actors and their powers.\n\nBPs\n\nBlock producers control the chain but in our view they do so by providing a technical commodity. They shouldn't be deciding about good or bad, about lawful or unlawful. About compliance. They should run the chain and keep it healthy. Just like a good ISP does in the old world. \n\nThey should follow code. However, BPs should also implement verdicts. E.g. freeze accounts that are stolen. But never on their own initiative. Only when they are compelled to do so by a ruling by an arbitrator of by a judge. Arbitration could be within EOS but also an offchain judge could order a BP to act in a certain way and such BP would have no other choice than to comply. \n\nTo us, as BP, code is law as are rulings issued following due process. BPs should in essence be blind to the morality or compliance with laws of the work they do. Only extraordinary circumstances may force a BP to act outside of these limits. \n\ndApp devs\n\nThe dApp devs interact with the users. They have a far broader responsibility. They must ensure compliance with outside rules and regulations. For them code isn't always law. They can introduce all kinds of criteria. Like \"fair\".  \n\nUsers\n\nUsers are, eventually, the real actors on EOS. Once a dApp is onchain the responsibility to use such dApp will be the users'. Each user will be responsible and liable for such user's own acts or omissions. Even if the dApp itself is against the law, the user pays the price. Users are also fully subject to arbitration.\n\nChecks and balances: arbitrators\n\nThe work of a body should be controlled. Otherwise power can be abused. Checks and balances need to be in place. This can obviously not be a voluntary pick. No one would voluntarily chose to be punished. \n\nBPs have a huge responsibility. They control the chain. There are checks in place. The first one is that the community can vote a non-functioning BP out. This is an extremely important check on their work. However this isn't sufficient since for a profound change in votes to take place the wrongdoing must be widely known. Further voting happens after the act and doesn't compensate for damage done. Therefore we need further checks.\n\nThe dApp devs and the users should also be controlled. There should be means to stop illegal actions. If an illegal dApp is running, it should be stopped. This would typically be after complaints of users or against users. Someone has to ensure such dApp is removed.  That someone shouldn't be a block producer. A block producer doesn't have an opinion. We execute. \n\nSo we need courts. Or arbitration. The choice is do we provide courts (arbitration) ourselves or do we let outside courts interfere. Own arbitration is preferable since the arbitrators will then apply as much as possible one worldwide EOS rule set. It is possible to limit the scope of our own arbitration but that will result in plaintiffs seeking remedy with outside courts for all that fall without such limited scope. Therefore also bonds do not help. They limit exposure and will leave room for outside courts to step in. in order to work, arbitration should be mandatory. All EOS members should be bound to it.\n\nConclusion\n\nWe encourage every member of the EOS community to debate further on the best choices to make. We have offered our in depth knowledge hereinabove. We are willing and eager to further participate in the discussions. To serve our EOS community.\n\n\nAmsterdam 18 July 2018",
      "json_metadata": "{\"tags\":[\"eos\",\"constitution\"],\"app\":\"esteem/1.6.0\",\"format\":\"markdown+html\",\"community\":\"esteem\"}"
    }
  ]
}
2018/06/28 20:44:57
voterjetsesprey
authorjetsesprey
permlinkhow-eos-wrote-history-today
weight10000 (100.00%)
Transaction InfoBlock #23727569/Trx 32dd94c1537e1a1e5315cec8fadfc6264f659084
View Raw JSON Data
{
  "trx_id": "32dd94c1537e1a1e5315cec8fadfc6264f659084",
  "block": 23727569,
  "trx_in_block": 7,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-28T20:44:57",
  "op": [
    "vote",
    {
      "voter": "jetsesprey",
      "author": "jetsesprey",
      "permlink": "how-eos-wrote-history-today",
      "weight": 10000
    }
  ]
}
jetsespreyreceived 0.145 STEEM, 0.099 SBD, 0.273 SP author reward for @jetsesprey / how-eos-wrote-history-today
2018/06/24 21:01:42
authorjetsesprey
permlinkhow-eos-wrote-history-today
sbd payout0.099 SBD
steem payout0.145 STEEM
vesting payout444.724397 VESTS
Transaction InfoBlock #23612720/Virtual Operation #11
View Raw JSON Data
{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 23612720,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 11,
  "timestamp": "2018-06-24T21:01:42",
  "op": [
    "author_reward",
    {
      "author": "jetsesprey",
      "permlink": "how-eos-wrote-history-today",
      "sbd_payout": "0.099 SBD",
      "steem_payout": "0.145 STEEM",
      "vesting_payout": "444.724397 VESTS"
    }
  ]
}
2018/06/18 10:51:54
votersteemitboard
authorjetsesprey
permlinkhow-eos-wrote-history-today
weight100 (1.00%)
Transaction InfoBlock #23427786/Trx 52fb2de8c2240cd57605202696d557eb931ecea7
View Raw JSON Data
{
  "trx_id": "52fb2de8c2240cd57605202696d557eb931ecea7",
  "block": 23427786,
  "trx_in_block": 6,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-18T10:51:54",
  "op": [
    "vote",
    {
      "voter": "steemitboard",
      "author": "jetsesprey",
      "permlink": "how-eos-wrote-history-today",
      "weight": 100
    }
  ]
}
2018/06/18 10:51:51
parent authorjetsesprey
parent permlinkhow-eos-wrote-history-today
authorsteemitboard
permlinksteemitboard-notify-jetsesprey-20180618t105153000z
title
bodyCongratulations @jetsesprey! You have completed some achievement on Steemit and have been rewarded with new badge(s) : [![](https://steemitimages.com/70x80/http://steemitboard.com/notifications/voted.png)](http://steemitboard.com/@jetsesprey) Award for the number of upvotes received <sub>_Click on the badge to view your Board of Honor._</sub> <sub>_If you no longer want to receive notifications, reply to this comment with the word_ `STOP`</sub> To support your work, I also upvoted your post! **Do not miss the [last post](https://steemit.com/steemitboard/@steemitboard/steemitboard-world-cup-contest-tunisia-vs-england) from @steemitboard!** --- **Participate in the [SteemitBoard World Cup Contest](https://steemit.com/steemitboard/@steemitboard/steemitboard-world-cup-contest-collect-badges-and-win-free-sbd)!** Collect World Cup badges and win free SBD Support the Gold Sponsors of the contest: [@good-karma](https://v2.steemconnect.com/sign/account-witness-vote?witness=good-karma&approve=1) and [@lukestokes](https://v2.steemconnect.com/sign/account-witness-vote?witness=lukestokes.mhth&approve=1) --- > Do you like [SteemitBoard's project](https://steemit.com/@steemitboard)? Then **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**!
json metadata{"image":["https://steemitboard.com/img/notify.png"]}
Transaction InfoBlock #23427785/Trx ebd7cf035fd8ecce3595c00f24b44fba7c21df9b
View Raw JSON Data
{
  "trx_id": "ebd7cf035fd8ecce3595c00f24b44fba7c21df9b",
  "block": 23427785,
  "trx_in_block": 39,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-18T10:51:51",
  "op": [
    "comment",
    {
      "parent_author": "jetsesprey",
      "parent_permlink": "how-eos-wrote-history-today",
      "author": "steemitboard",
      "permlink": "steemitboard-notify-jetsesprey-20180618t105153000z",
      "title": "",
      "body": "Congratulations @jetsesprey! You have completed some achievement on Steemit and have been rewarded with new badge(s) :\n\n[![](https://steemitimages.com/70x80/http://steemitboard.com/notifications/voted.png)](http://steemitboard.com/@jetsesprey) Award for the number of upvotes received\n\n<sub>_Click on the badge to view your Board of Honor._</sub>\n<sub>_If you no longer want to receive notifications, reply to this comment with the word_ `STOP`</sub>\n\n\nTo support your work, I also upvoted your post!\n\n\n**Do not miss the [last post](https://steemit.com/steemitboard/@steemitboard/steemitboard-world-cup-contest-tunisia-vs-england) from @steemitboard!**\n\n---\n**Participate in the [SteemitBoard World Cup Contest](https://steemit.com/steemitboard/@steemitboard/steemitboard-world-cup-contest-collect-badges-and-win-free-sbd)!**\nCollect World Cup badges and win free SBD\nSupport the Gold Sponsors of the contest: [@good-karma](https://v2.steemconnect.com/sign/account-witness-vote?witness=good-karma&approve=1) and [@lukestokes](https://v2.steemconnect.com/sign/account-witness-vote?witness=lukestokes.mhth&approve=1)\n\n---\n\n> Do you like [SteemitBoard's project](https://steemit.com/@steemitboard)? Then **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**!",
      "json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}"
    }
  ]
}
2018/06/18 06:00:33
votercryptomazin
authorjetsesprey
permlinkhow-eos-wrote-history-today
weight10000 (100.00%)
Transaction InfoBlock #23421960/Trx 5d18bdd4e9a5107faf62f8425a5c69735dd9c104
View Raw JSON Data
{
  "trx_id": "5d18bdd4e9a5107faf62f8425a5c69735dd9c104",
  "block": 23421960,
  "trx_in_block": 23,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-18T06:00:33",
  "op": [
    "vote",
    {
      "voter": "cryptomazin",
      "author": "jetsesprey",
      "permlink": "how-eos-wrote-history-today",
      "weight": 10000
    }
  ]
}
2018/06/18 05:42:06
voterblhz
authorjetsesprey
permlinkhow-eos-wrote-history-today
weight10000 (100.00%)
Transaction InfoBlock #23421592/Trx eddc96c00ed38b5577b980f5ddde48eb61125945
View Raw JSON Data
{
  "trx_id": "eddc96c00ed38b5577b980f5ddde48eb61125945",
  "block": 23421592,
  "trx_in_block": 7,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-18T05:42:06",
  "op": [
    "vote",
    {
      "voter": "blhz",
      "author": "jetsesprey",
      "permlink": "how-eos-wrote-history-today",
      "weight": 10000
    }
  ]
}
2018/06/18 04:47:27
voterslavix
authorjetsesprey
permlinkhow-eos-wrote-history-today
weight10000 (100.00%)
Transaction InfoBlock #23420499/Trx 2a04f7ada6d97d2767097667e0d3a5a25859e704
View Raw JSON Data
{
  "trx_id": "2a04f7ada6d97d2767097667e0d3a5a25859e704",
  "block": 23420499,
  "trx_in_block": 9,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-18T04:47:27",
  "op": [
    "vote",
    {
      "voter": "slavix",
      "author": "jetsesprey",
      "permlink": "how-eos-wrote-history-today",
      "weight": 10000
    }
  ]
}
2018/06/18 03:05:06
voteraclarkuk82
authorjetsesprey
permlinkhow-eos-wrote-history-today
weight10000 (100.00%)
Transaction InfoBlock #23418452/Trx 81f6c9d0e01bb22a3a5f03882f8e708b9ba96d36
View Raw JSON Data
{
  "trx_id": "81f6c9d0e01bb22a3a5f03882f8e708b9ba96d36",
  "block": 23418452,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-18T03:05:06",
  "op": [
    "vote",
    {
      "voter": "aclarkuk82",
      "author": "jetsesprey",
      "permlink": "how-eos-wrote-history-today",
      "weight": 10000
    }
  ]
}
2018/06/18 01:10:03
parent authorjetsesprey
parent permlinkhow-eos-wrote-history-today
authorsteemitboard
permlinksteemitboard-notify-jetsesprey-20180618t011003000z
title
bodyCongratulations @jetsesprey! You have completed some achievement on Steemit and have been rewarded with new badge(s) : [![](https://steemitimages.com/70x70/http://steemitboard.com/notifications/firstpost.png)](http://steemitboard.com/@jetsesprey) You published your First Post [![](https://steemitimages.com/70x70/http://steemitboard.com/notifications/firstvoted.png)](http://steemitboard.com/@jetsesprey) You got a First Vote <sub>_Click on the badge to view your Board of Honor._</sub> <sub>_If you no longer want to receive notifications, reply to this comment with the word_ `STOP`</sub> **Do not miss the [last post](https://steemit.com/steemitboard/@steemitboard/steemitboard-world-cup-contest-tunisia-vs-england) from @steemitboard!** --- **Participate in the [SteemitBoard World Cup Contest](https://steemit.com/steemitboard/@steemitboard/steemitboard-world-cup-contest-collect-badges-and-win-free-sbd)!** Collect World Cup badges and win free SBD Support the Gold Sponsors of the contest: [@good-karma](https://v2.steemconnect.com/sign/account-witness-vote?witness=good-karma&approve=1) and [@lukestokes](https://v2.steemconnect.com/sign/account-witness-vote?witness=lukestokes.mhth&approve=1) --- > Do you like [SteemitBoard's project](https://steemit.com/@steemitboard)? Then **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**!
json metadata{"image":["https://steemitboard.com/img/notify.png"]}
Transaction InfoBlock #23416152/Trx 11dc5533c58437473bf3ec5ef289fba093c9718b
View Raw JSON Data
{
  "trx_id": "11dc5533c58437473bf3ec5ef289fba093c9718b",
  "block": 23416152,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-18T01:10:03",
  "op": [
    "comment",
    {
      "parent_author": "jetsesprey",
      "parent_permlink": "how-eos-wrote-history-today",
      "author": "steemitboard",
      "permlink": "steemitboard-notify-jetsesprey-20180618t011003000z",
      "title": "",
      "body": "Congratulations @jetsesprey! You have completed some achievement on Steemit and have been rewarded with new badge(s) :\n\n[![](https://steemitimages.com/70x70/http://steemitboard.com/notifications/firstpost.png)](http://steemitboard.com/@jetsesprey) You published your First Post\n[![](https://steemitimages.com/70x70/http://steemitboard.com/notifications/firstvoted.png)](http://steemitboard.com/@jetsesprey) You got a First Vote\n\n<sub>_Click on the badge to view your Board of Honor._</sub>\n<sub>_If you no longer want to receive notifications, reply to this comment with the word_ `STOP`</sub>\n\n\n\n**Do not miss the [last post](https://steemit.com/steemitboard/@steemitboard/steemitboard-world-cup-contest-tunisia-vs-england) from @steemitboard!**\n\n---\n**Participate in the [SteemitBoard World Cup Contest](https://steemit.com/steemitboard/@steemitboard/steemitboard-world-cup-contest-collect-badges-and-win-free-sbd)!**\nCollect World Cup badges and win free SBD\nSupport the Gold Sponsors of the contest: [@good-karma](https://v2.steemconnect.com/sign/account-witness-vote?witness=good-karma&approve=1) and [@lukestokes](https://v2.steemconnect.com/sign/account-witness-vote?witness=lukestokes.mhth&approve=1)\n\n---\n\n> Do you like [SteemitBoard's project](https://steemit.com/@steemitboard)? Then **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**!",
      "json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}"
    }
  ]
}
2018/06/17 22:59:36
voterphilmesnier
authorjetsesprey
permlinkhow-eos-wrote-history-today
weight10000 (100.00%)
Transaction InfoBlock #23413544/Trx 7fe8b82e24ab7ff347077d315eeb61144f73cdfe
View Raw JSON Data
{
  "trx_id": "7fe8b82e24ab7ff347077d315eeb61144f73cdfe",
  "block": 23413544,
  "trx_in_block": 7,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-17T22:59:36",
  "op": [
    "vote",
    {
      "voter": "philmesnier",
      "author": "jetsesprey",
      "permlink": "how-eos-wrote-history-today",
      "weight": 10000
    }
  ]
}
2018/06/17 22:19:03
voterconceptskip
authorjetsesprey
permlinkhow-eos-wrote-history-today
weight10000 (100.00%)
Transaction InfoBlock #23412733/Trx bb53a71305bfa0e1bee26f89d07f73fb631a8404
View Raw JSON Data
{
  "trx_id": "bb53a71305bfa0e1bee26f89d07f73fb631a8404",
  "block": 23412733,
  "trx_in_block": 26,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-17T22:19:03",
  "op": [
    "vote",
    {
      "voter": "conceptskip",
      "author": "jetsesprey",
      "permlink": "how-eos-wrote-history-today",
      "weight": 10000
    }
  ]
}
2018/06/17 22:18:42
parent authorjetsesprey
parent permlinkhow-eos-wrote-history-today
authorrichreeve
permlinkre-jetsesprey-how-eos-wrote-history-today-20180617t221841378z
title
bodyI dont disagree with this decision but I do worry about the precedent thats now been set. BP's will certainly have to work for their blocks.
json metadata{"tags":["eos"],"app":"steemit/0.1"}
Transaction InfoBlock #23412726/Trx 0d268554c19e07c99e8cf891bc9012ec057e0d1f
View Raw JSON Data
{
  "trx_id": "0d268554c19e07c99e8cf891bc9012ec057e0d1f",
  "block": 23412726,
  "trx_in_block": 25,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-17T22:18:42",
  "op": [
    "comment",
    {
      "parent_author": "jetsesprey",
      "parent_permlink": "how-eos-wrote-history-today",
      "author": "richreeve",
      "permlink": "re-jetsesprey-how-eos-wrote-history-today-20180617t221841378z",
      "title": "",
      "body": "I dont disagree with this decision but I do worry about the precedent thats now been set. BP's will certainly have to work for their blocks.",
      "json_metadata": "{\"tags\":[\"eos\"],\"app\":\"steemit/0.1\"}"
    }
  ]
}
2018/06/17 22:16:57
voterrichreeve
authorjetsesprey
permlinkhow-eos-wrote-history-today
weight10000 (100.00%)
Transaction InfoBlock #23412691/Trx ebc410fce337e80143eedb83ee363a2b2d0af874
View Raw JSON Data
{
  "trx_id": "ebc410fce337e80143eedb83ee363a2b2d0af874",
  "block": 23412691,
  "trx_in_block": 28,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-17T22:16:57",
  "op": [
    "vote",
    {
      "voter": "richreeve",
      "author": "jetsesprey",
      "permlink": "how-eos-wrote-history-today",
      "weight": 10000
    }
  ]
}
2018/06/17 21:31:51
parent authorjetsesprey
parent permlinkhow-eos-wrote-history-today
authorintroduce.bot
permlinkintroduce-bot-re-jetsespreyhow-eos-wrote-history-today
title
body✅ @jetsesprey, I gave you an upvote on your first post! **Please give me a follow** and I will give you a follow in return!<br><br>Please also take a moment to read [this post](https://steemit.com/spam/@pleasestop/introducing-pleasestop-here-to-reduce-comment-spam) regarding bad behavior on Steemit.
json metadata
Transaction InfoBlock #23411789/Trx 940944309e958668fb6bda51f99748b7707ef50a
View Raw JSON Data
{
  "trx_id": "940944309e958668fb6bda51f99748b7707ef50a",
  "block": 23411789,
  "trx_in_block": 49,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-17T21:31:51",
  "op": [
    "comment",
    {
      "parent_author": "jetsesprey",
      "parent_permlink": "how-eos-wrote-history-today",
      "author": "introduce.bot",
      "permlink": "introduce-bot-re-jetsespreyhow-eos-wrote-history-today",
      "title": "",
      "body": "✅  @jetsesprey, I gave you an upvote on your first post! **Please give me a follow** and I will give you a follow in return!<br><br>Please also take a moment to read [this post](https://steemit.com/spam/@pleasestop/introducing-pleasestop-here-to-reduce-comment-spam) regarding bad behavior on Steemit.",
      "json_metadata": ""
    }
  ]
}
2018/06/17 21:31:51
voterintroduce.bot
authorjetsesprey
permlinkhow-eos-wrote-history-today
weight339 (3.39%)
Transaction InfoBlock #23411789/Trx 1e2ac9301e579c416ecb97f8d7d803f85dca8321
View Raw JSON Data
{
  "trx_id": "1e2ac9301e579c416ecb97f8d7d803f85dca8321",
  "block": 23411789,
  "trx_in_block": 22,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-17T21:31:51",
  "op": [
    "vote",
    {
      "voter": "introduce.bot",
      "author": "jetsesprey",
      "permlink": "how-eos-wrote-history-today",
      "weight": 339
    }
  ]
}
2018/06/17 21:25:51
votercryptoslicex
authorjetsesprey
permlinkhow-eos-wrote-history-today
weight10000 (100.00%)
Transaction InfoBlock #23411669/Trx 9d742d8c11249fb563724bfda2ab60911d609125
View Raw JSON Data
{
  "trx_id": "9d742d8c11249fb563724bfda2ab60911d609125",
  "block": 23411669,
  "trx_in_block": 8,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-17T21:25:51",
  "op": [
    "vote",
    {
      "voter": "cryptoslicex",
      "author": "jetsesprey",
      "permlink": "how-eos-wrote-history-today",
      "weight": 10000
    }
  ]
}
2018/06/17 21:04:03
voterdatajunky
authorjetsesprey
permlinkhow-eos-wrote-history-today
weight10000 (100.00%)
Transaction InfoBlock #23411233/Trx 5dcd1bd57379f3672623e7f2836f659e383490b5
View Raw JSON Data
{
  "trx_id": "5dcd1bd57379f3672623e7f2836f659e383490b5",
  "block": 23411233,
  "trx_in_block": 19,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-17T21:04:03",
  "op": [
    "vote",
    {
      "voter": "datajunky",
      "author": "jetsesprey",
      "permlink": "how-eos-wrote-history-today",
      "weight": 10000
    }
  ]
}
2018/06/17 21:02:21
parent authorjetsesprey
parent permlinkhow-eos-wrote-history-today
authora-0-1
permlinkre-jetsesprey-how-eos-wrote-history-today-20180617t210220237z
title
bodyGo here https://steemit.com/@a-a-a to get your post resteemed to over 72,000 followers.
json metadata{"tags":["eos"],"links":["https://steemit.com/@a-a-a"],"app":"steemit/0.1"}
Transaction InfoBlock #23411199/Trx d6d0877ab80d28bed40fb271cef966dceb187e60
View Raw JSON Data
{
  "trx_id": "d6d0877ab80d28bed40fb271cef966dceb187e60",
  "block": 23411199,
  "trx_in_block": 17,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-17T21:02:21",
  "op": [
    "comment",
    {
      "parent_author": "jetsesprey",
      "parent_permlink": "how-eos-wrote-history-today",
      "author": "a-0-1",
      "permlink": "re-jetsesprey-how-eos-wrote-history-today-20180617t210220237z",
      "title": "",
      "body": "Go here https://steemit.com/@a-a-a to get your post resteemed to over 72,000 followers.",
      "json_metadata": "{\"tags\":[\"eos\"],\"links\":[\"https://steemit.com/@a-a-a\"],\"app\":\"steemit/0.1\"}"
    }
  ]
}
2018/06/17 21:01:42
parent author
parent permlinkeos
authorjetsesprey
permlinkhow-eos-wrote-history-today
titleHow EOS wrote history today
bodyToday EOS was governed. Today the EOS blockchain stood out from mere code as 21 Block Producers and all of the standby BPs made a decision: to overrule the code and freeze five accounts. Five people could prove they were spoofed and had received incorrect private keys. Five people that would have lost all EOS on their accounts. How was this meant to go? The ECAF rules allow for emergency arbitration. However, the arbitrator appointed handed the matter back to the community. He choose not to rule. I don’t know his reasons yet but for now that doesn’t matter. **What happened?** A lengthy zoom call followed. Some BPs found they shouldn’t do anything. Especially since the BP agreement states that a BP should only freeze an acount following a valid arbitrator’s ruling. The dilemma was that the arbitrator stated that in this particular case he couldn’t rule (which is not extraordinary, that can happen) and referred the matter back to the BPs. So it was up to the BPs. They found themselves in an awkward spot. They were set up to provide the technically impartial execution of EOS and the arbitration system, but now they were asked to step away from that core position and to make a decision themselves. **Some BPs were hesitant to freeze the accounts.** Understandably. Freezing without an arbitrator’s verdict, means entering into a conflict with the BP agreement. And would mean, further, a precedent. Because if in this case the BPs would act, they might become prone to more external pressure in other cases as well and that might impair the system. And, even more important, since there was no legal basis for freezing, some of the BPs argued, this may lead to claims because the claimant could argue that the BPs overstepped their authority. Especially when mistakes were made in the process and no crime was committed. The other BPs argued that if the house is on fire, you put out the fire first and ask questions later. EOS Amsterdam wanted to freeze the accounts. We believe that in situations like these one needs to take responsibility. A technical explanation from EOS 911 convinced the BPs to freeze the accounts temporarily so more time was available. A new smart contract on Etherium could proof the truthfulness of the owners of the scammed accounts. The community decided unanimously to indeed freeze the accounts. Each of the BPs and standby BPs wished to check the evidence first. At the end they all agreed: not freezing the account would mean genuine owners would lose their EOS. **What lessons are to be learned here from a legal and governance perspective?** First of all: the system worked. The community defined an action that was good. Spoofing didn’t get rewarded. Legitimate owners can probably hold on to their EOS. The community filled a gap in the rules. The following questions got satisfying answers: what to do if for some reason arbitration doesn’t work? Should we do nothing or act? Should we follow the letter of our BP agreement or find a way out? To me it is clear that n this particular case the decision made was right. Another decision would have meant an unfair result and might have had negative impact on EOS. Secondly: the legal takeaway is that the idea of EOS Constitution and the BP agreement are as they are now difficult to manage. Because it is not clear what happens when a gap occurs. There is no last resort clause or entity that has authority to act in the situation where, contractually, no one else has authority. From a contractual point of view, this might lead to liability in case of a wrong decision. If, e.g., the spoofed accounts weren’t spoofed. **Minding the gap** We could solve this issue now. It is the process of minding the gaps. One learns when one goes along and adapts the docs to new insights. In this case we could introduce an article in the Constitution that stipulates that BPs are allowed to act once such act is based upon an unanimous decision by the BPs and standby BPS together and such act is in the interest of the community. Further such article should stipulate that the BPs wouldn’t become liable provided, however, that they acted in good faith. (Meaning: they are not liable if they could have reasonably been of the opinion that what they were doing was the right thing.) Legally we would contractually introduce some kind of meeting that has the authority to temporarily correct and amend the Constitution and the related documents in specific cases where arbitration doesn’t work and the BP agreement leads to an clearly unfair outcome. This looks in fact a lot like the organization of many companies/association where there is always such a gathering, sit down, that can act on behalf of the organization. It is the hybrid face of our documents: they are a contract but we organize governance in them. Governance is typically organized in bylaws or articles of association. Realizing that might help: we could look how others did this. There are tons of valuable insights out there. We did start something incredible here. Something completely new. Something that hasn’t been done before. Yet, humanity has met a lot of our current challenges before and resolved the, Let’s use ancient knowledge to strengthen our brand new and beautiful community. Amsterdam, 17 June 2018
json metadata{"tags":["eos"],"app":"steemit/0.1","format":"markdown"}
Transaction InfoBlock #23411186/Trx 31bbda41ab6cb7dcb1f0dbe1d1e4819aceaba9f3
View Raw JSON Data
{
  "trx_id": "31bbda41ab6cb7dcb1f0dbe1d1e4819aceaba9f3",
  "block": 23411186,
  "trx_in_block": 17,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-17T21:01:42",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "eos",
      "author": "jetsesprey",
      "permlink": "how-eos-wrote-history-today",
      "title": "How EOS wrote history today",
      "body": "Today EOS was governed. Today the EOS blockchain stood out from mere code as 21 Block Producers and all of the standby BPs made a decision: to overrule the code and freeze five accounts. Five people could prove they were spoofed and had received incorrect private keys. Five people that would have lost all EOS on their accounts. \n\nHow was this meant to go? The ECAF rules allow for emergency arbitration. However, the arbitrator appointed handed the matter back to the community. He choose not to rule. I don’t know his reasons yet but for now that doesn’t matter. \n\n**What happened?**\n\nA lengthy zoom call followed. Some BPs found they shouldn’t do anything. Especially since the BP agreement states that a BP should only freeze an acount following a valid arbitrator’s ruling. The dilemma was that the arbitrator stated that in this particular case he couldn’t rule (which is not extraordinary, that can happen) and referred the matter back to the BPs. So it was up to the BPs. They found themselves in an awkward spot. They were set up to provide the technically impartial execution of EOS and the arbitration system, but now they were asked to step away from that core position and to make a decision themselves. \n\n**Some BPs were hesitant to freeze the accounts.** \n\nUnderstandably. Freezing without an arbitrator’s verdict, means entering into a conflict with the BP agreement. And would mean, further, a precedent. Because if in this case the BPs would act, they might become prone to more external pressure in other cases as well and that might impair the system. And, even more important, since there was no legal basis for freezing, some of the BPs argued, this may lead to claims because the claimant could argue that the BPs overstepped their authority. Especially when mistakes were made in the process and no crime was committed. The other BPs argued that if the house is on fire, you put out the fire first and ask questions later. \n\nEOS Amsterdam wanted to freeze the accounts. We believe that in situations like these one needs to take responsibility. \n\nA technical explanation from EOS 911 convinced the BPs to freeze the accounts temporarily so more time was available. A new smart contract on Etherium could proof the truthfulness of the owners of the scammed accounts. The community decided unanimously to indeed freeze the accounts. Each of the BPs and standby BPs wished to check the evidence first. At the end they all agreed: not freezing the account would mean genuine owners would lose their EOS. \n\n**What lessons are to be learned here from a legal and governance perspective?**\n\nFirst of all: the system worked. The community defined an action that was good. Spoofing didn’t get rewarded. Legitimate owners can probably hold on to their EOS. The community filled a gap in the rules. The following questions got satisfying answers: what to do if for some reason arbitration doesn’t work? Should we do nothing or act? Should we follow the letter of our BP agreement or find a way out? To me it is clear that n this particular case the decision made was right. Another decision would have meant an unfair result and might have had negative impact on EOS. \n\nSecondly: the legal takeaway is that the idea of EOS Constitution and the BP agreement are as they are now difficult to manage. Because it is not clear what happens when a gap occurs. There is no last resort clause or entity that has authority to act in the situation where, contractually, no one else has authority. From a contractual point of view, this might lead to liability in case of a wrong decision. If, e.g., the spoofed accounts weren’t spoofed. \n\n**Minding the gap** \n\nWe could solve this issue now. It is the process of minding the gaps. One learns when one goes along and adapts the docs to new insights. In this case we could introduce an article in the Constitution that stipulates that BPs are allowed to act once such act is based upon an unanimous decision by the BPs and standby BPS together and such act is in the interest of the community. Further such article should stipulate that the BPs wouldn’t become liable provided, however, that they acted in good faith. (Meaning: they are not liable if they could have reasonably been of the opinion that what they were doing was the right thing.) \n\nLegally we would contractually introduce some kind of meeting that has the authority to temporarily correct and amend the Constitution and the related documents in specific cases where arbitration doesn’t work and the BP agreement leads to an clearly unfair outcome. This looks in fact a lot like the organization of many companies/association where there is always such a gathering, sit down, that can act on behalf of the organization. \n\nIt is the hybrid face of our documents: they are a contract but we organize governance in them. Governance is typically organized in bylaws or articles of association. Realizing that might help: we could look how others did this. There are tons of valuable insights out there.\n\nWe did start something incredible here. Something completely new. Something that hasn’t been done before. Yet, humanity has met a lot of our current challenges before and resolved the, Let’s use ancient knowledge to strengthen our brand new and beautiful community. \n\nAmsterdam, 17 June 2018",
      "json_metadata": "{\"tags\":[\"eos\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}
jetsespreyupdated their account properties
2018/06/12 15:41:03
accountjetsesprey
memo keySTM7ZXkRzUrJz7BZorrLT2FhMrKRU8gGfYujDG9pLNMuz2nSG1pMK
json metadata{"profile":{"profile_image":"https://cdn.steemitimages.com/DQmWjBCAPvWMz7CmBxouKEdieTacdv4bm69ovTer2k34mwu/EOS%20AMSTERDAM%20LOGO%20IMG_20180612_173627_160.jpg","name":"Jetse Sprey EOS Ams","location":"Amsterdam","website":"https://eosamsterdam.net/"}}
Transaction InfoBlock #23260799/Trx bc93e2af7dff50db2bed7876c4b6c9a527a257bb
View Raw JSON Data
{
  "trx_id": "bc93e2af7dff50db2bed7876c4b6c9a527a257bb",
  "block": 23260799,
  "trx_in_block": 38,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-12T15:41:03",
  "op": [
    "account_update",
    {
      "account": "jetsesprey",
      "memo_key": "STM7ZXkRzUrJz7BZorrLT2FhMrKRU8gGfYujDG9pLNMuz2nSG1pMK",
      "json_metadata": "{\"profile\":{\"profile_image\":\"https://cdn.steemitimages.com/DQmWjBCAPvWMz7CmBxouKEdieTacdv4bm69ovTer2k34mwu/EOS%20AMSTERDAM%20LOGO%20IMG_20180612_173627_160.jpg\",\"name\":\"Jetse Sprey EOS Ams\",\"location\":\"Amsterdam\",\"website\":\"https://eosamsterdam.net/\"}}"
    }
  ]
}
jetsespreyupdated their account properties
2018/06/12 15:38:24
accountjetsesprey
memo keySTM7ZXkRzUrJz7BZorrLT2FhMrKRU8gGfYujDG9pLNMuz2nSG1pMK
json metadata{"profile":{"profile_image":"https://cdn.steemitimages.com/DQmWjBCAPvWMz7CmBxouKEdieTacdv4bm69ovTer2k34mwu/EOS%20AMSTERDAM%20LOGO%20IMG_20180612_173627_160.jpg","name":"EOS Amsterdam"}}
Transaction InfoBlock #23260746/Trx 323d29f30de62a0f9ba87842893c9f37a0e5895c
View Raw JSON Data
{
  "trx_id": "323d29f30de62a0f9ba87842893c9f37a0e5895c",
  "block": 23260746,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-12T15:38:24",
  "op": [
    "account_update",
    {
      "account": "jetsesprey",
      "memo_key": "STM7ZXkRzUrJz7BZorrLT2FhMrKRU8gGfYujDG9pLNMuz2nSG1pMK",
      "json_metadata": "{\"profile\":{\"profile_image\":\"https://cdn.steemitimages.com/DQmWjBCAPvWMz7CmBxouKEdieTacdv4bm69ovTer2k34mwu/EOS%20AMSTERDAM%20LOGO%20IMG_20180612_173627_160.jpg\",\"name\":\"EOS Amsterdam\"}}"
    }
  ]
}
2018/05/27 07:48:51
required auths[]
required posting auths["jetsesprey"]
idfollow
json["follow",{"follower":"jetsesprey","following":"dallasrushing","what":["blog"]}]
Transaction InfoBlock #22791252/Trx 69f1c66fcc8f24d3ed57729cb765b1b3c228240c
View Raw JSON Data
{
  "trx_id": "69f1c66fcc8f24d3ed57729cb765b1b3c228240c",
  "block": 22791252,
  "trx_in_block": 43,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-05-27T07:48:51",
  "op": [
    "custom_json",
    {
      "required_auths": [],
      "required_posting_auths": [
        "jetsesprey"
      ],
      "id": "follow",
      "json": "[\"follow\",{\"follower\":\"jetsesprey\",\"following\":\"dallasrushing\",\"what\":[\"blog\"]}]"
    }
  ]
}
jetsespreyupdated their account properties
2018/05/02 16:32:57
accountjetsesprey
memo keySTM7ZXkRzUrJz7BZorrLT2FhMrKRU8gGfYujDG9pLNMuz2nSG1pMK
json metadata{"profile":{"cover_image":"","profile_image":"https://img.esteem.ws/57lnnx1x4m.jpg"}}
Transaction InfoBlock #22082242/Trx 50a14d391429b4451fac2e7a8ad38c73791fb830
View Raw JSON Data
{
  "trx_id": "50a14d391429b4451fac2e7a8ad38c73791fb830",
  "block": 22082242,
  "trx_in_block": 78,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-05-02T16:32:57",
  "op": [
    "account_update",
    {
      "account": "jetsesprey",
      "memo_key": "STM7ZXkRzUrJz7BZorrLT2FhMrKRU8gGfYujDG9pLNMuz2nSG1pMK",
      "json_metadata": "{\"profile\":{\"cover_image\":\"\",\"profile_image\":\"https://img.esteem.ws/57lnnx1x4m.jpg\"}}"
    }
  ]
}
jetsespreyupdated their account properties
2018/05/02 16:27:51
accountjetsesprey
memo keySTM7ZXkRzUrJz7BZorrLT2FhMrKRU8gGfYujDG9pLNMuz2nSG1pMK
json metadata{"profile":{"cover_image":"","profile_image":"https://img.esteem.ws/f1wboavrn3.jpg"}}
Transaction InfoBlock #22082140/Trx 75b458aab1c2bb2cc02f6a99008abe981851d477
View Raw JSON Data
{
  "trx_id": "75b458aab1c2bb2cc02f6a99008abe981851d477",
  "block": 22082140,
  "trx_in_block": 43,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-05-02T16:27:51",
  "op": [
    "account_update",
    {
      "account": "jetsesprey",
      "memo_key": "STM7ZXkRzUrJz7BZorrLT2FhMrKRU8gGfYujDG9pLNMuz2nSG1pMK",
      "json_metadata": "{\"profile\":{\"cover_image\":\"\",\"profile_image\":\"https://img.esteem.ws/f1wboavrn3.jpg\"}}"
    }
  ]
}
jetsespreyupdated their account properties
2018/05/02 16:26:33
accountjetsesprey
memo keySTM7ZXkRzUrJz7BZorrLT2FhMrKRU8gGfYujDG9pLNMuz2nSG1pMK
json metadata{"profile":{"profile_image":"","cover_image":""}}
Transaction InfoBlock #22082114/Trx 5547f1b72f3d9acb5441e00b2025589d67e9f86f
View Raw JSON Data
{
  "trx_id": "5547f1b72f3d9acb5441e00b2025589d67e9f86f",
  "block": 22082114,
  "trx_in_block": 18,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-05-02T16:26:33",
  "op": [
    "account_update",
    {
      "account": "jetsesprey",
      "memo_key": "STM7ZXkRzUrJz7BZorrLT2FhMrKRU8gGfYujDG9pLNMuz2nSG1pMK",
      "json_metadata": "{\"profile\":{\"profile_image\":\"\",\"cover_image\":\"\"}}"
    }
  ]
}
jetsespreyupdated their account properties
2018/05/02 16:26:00
accountjetsesprey
memo keySTM7ZXkRzUrJz7BZorrLT2FhMrKRU8gGfYujDG9pLNMuz2nSG1pMK
json metadata{"profile":{"cover_image":"","profile_image":"https://img.esteem.ws/f1wboavrn3.jpg"}}
Transaction InfoBlock #22082103/Trx 622e357ce97b4df96aea037b39aedc59e160f6f1
View Raw JSON Data
{
  "trx_id": "622e357ce97b4df96aea037b39aedc59e160f6f1",
  "block": 22082103,
  "trx_in_block": 16,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-05-02T16:26:00",
  "op": [
    "account_update",
    {
      "account": "jetsesprey",
      "memo_key": "STM7ZXkRzUrJz7BZorrLT2FhMrKRU8gGfYujDG9pLNMuz2nSG1pMK",
      "json_metadata": "{\"profile\":{\"cover_image\":\"\",\"profile_image\":\"https://img.esteem.ws/f1wboavrn3.jpg\"}}"
    }
  ]
}
jetsespreyupdated their account properties
2018/05/02 16:25:12
accountjetsesprey
memo keySTM7ZXkRzUrJz7BZorrLT2FhMrKRU8gGfYujDG9pLNMuz2nSG1pMK
json metadata{"profile":{"cover_image":"","profile_image":"https://img.esteem.ws/p213ujr767.jpg"}}
Transaction InfoBlock #22082087/Trx e0dc511043e85e18e10fa02bd846f703836289a4
View Raw JSON Data
{
  "trx_id": "e0dc511043e85e18e10fa02bd846f703836289a4",
  "block": 22082087,
  "trx_in_block": 21,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-05-02T16:25:12",
  "op": [
    "account_update",
    {
      "account": "jetsesprey",
      "memo_key": "STM7ZXkRzUrJz7BZorrLT2FhMrKRU8gGfYujDG9pLNMuz2nSG1pMK",
      "json_metadata": "{\"profile\":{\"cover_image\":\"\",\"profile_image\":\"https://img.esteem.ws/p213ujr767.jpg\"}}"
    }
  ]
}
steemdelegated 18.644 SP to @jetsesprey
2018/04/20 22:15:24
delegatorsteem
delegateejetsesprey
vesting shares30359.898455 VESTS
Transaction InfoBlock #21744204/Trx 70461d75160b981703151e0c82c0073f26bef4cd
View Raw JSON Data
{
  "trx_id": "70461d75160b981703151e0c82c0073f26bef4cd",
  "block": 21744204,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-04-20T22:15:24",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "jetsesprey",
      "vesting_shares": "30359.898455 VESTS"
    }
  ]
}
steemcreated a new account: @jetsesprey
2018/04/20 20:07:36
fee0.100 STEEM
delegation30690.000000 VESTS
creatorsteem
new account namejetsesprey
owner{"weight_threshold":1,"account_auths":[],"key_auths":[["STM68YcjUfh46DoPkPJyuzxBnX2DmT1LdwfMg6DmhYc1iGuLph7xP",1]]}
active{"weight_threshold":1,"account_auths":[],"key_auths":[["STM7PU5PwJhzt5UK9HQpRMDickNU3XHtjYnyfJwCun7e4cunv5Nqu",1]]}
posting{"weight_threshold":1,"account_auths":[],"key_auths":[["STM7UFy7nXo1TxZ4vgWHYEXtH7dX8Dnj8Uwh1gbmpYPYEMBgx9HiS",1]]}
memo keySTM7ZXkRzUrJz7BZorrLT2FhMrKRU8gGfYujDG9pLNMuz2nSG1pMK
json metadata{}
extensions[]
Transaction InfoBlock #21741648/Trx f9645ae2af1024ac38f05365f51d8e5f124ccedb
View Raw JSON Data
{
  "trx_id": "f9645ae2af1024ac38f05365f51d8e5f124ccedb",
  "block": 21741648,
  "trx_in_block": 40,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-04-20T20:07:36",
  "op": [
    "account_create_with_delegation",
    {
      "fee": "0.100 STEEM",
      "delegation": "30690.000000 VESTS",
      "creator": "steem",
      "new_account_name": "jetsesprey",
      "owner": {
        "weight_threshold": 1,
        "account_auths": [],
        "key_auths": [
          [
            "STM68YcjUfh46DoPkPJyuzxBnX2DmT1LdwfMg6DmhYc1iGuLph7xP",
            1
          ]
        ]
      },
      "active": {
        "weight_threshold": 1,
        "account_auths": [],
        "key_auths": [
          [
            "STM7PU5PwJhzt5UK9HQpRMDickNU3XHtjYnyfJwCun7e4cunv5Nqu",
            1
          ]
        ]
      },
      "posting": {
        "weight_threshold": 1,
        "account_auths": [],
        "key_auths": [
          [
            "STM7UFy7nXo1TxZ4vgWHYEXtH7dX8Dnj8Uwh1gbmpYPYEMBgx9HiS",
            1
          ]
        ]
      },
      "memo_key": "STM7ZXkRzUrJz7BZorrLT2FhMrKRU8gGfYujDG9pLNMuz2nSG1pMK",
      "json_metadata": "{}",
      "extensions": []
    }
  ]
}

Account Metadata

POSTING JSON METADATA
profile{"profile_image":"https://cdn.steemitimages.com/DQmWjBCAPvWMz7CmBxouKEdieTacdv4bm69ovTer2k34mwu/EOS%20AMSTERDAM%20LOGO%20IMG_20180612_173627_160.jpg","name":"Jetse Sprey EOS Ams","location":"Amsterdam","website":"https://eosamsterdam.net/"}
JSON METADATA
profile{"profile_image":"https://cdn.steemitimages.com/DQmWjBCAPvWMz7CmBxouKEdieTacdv4bm69ovTer2k34mwu/EOS%20AMSTERDAM%20LOGO%20IMG_20180612_173627_160.jpg","name":"Jetse Sprey EOS Ams","location":"Amsterdam","website":"https://eosamsterdam.net/"}
{
  "posting_json_metadata": {
    "profile": {
      "profile_image": "https://cdn.steemitimages.com/DQmWjBCAPvWMz7CmBxouKEdieTacdv4bm69ovTer2k34mwu/EOS%20AMSTERDAM%20LOGO%20IMG_20180612_173627_160.jpg",
      "name": "Jetse Sprey EOS Ams",
      "location": "Amsterdam",
      "website": "https://eosamsterdam.net/"
    }
  },
  "json_metadata": {
    "profile": {
      "profile_image": "https://cdn.steemitimages.com/DQmWjBCAPvWMz7CmBxouKEdieTacdv4bm69ovTer2k34mwu/EOS%20AMSTERDAM%20LOGO%20IMG_20180612_173627_160.jpg",
      "name": "Jetse Sprey EOS Ams",
      "location": "Amsterdam",
      "website": "https://eosamsterdam.net/"
    }
  }
}

Auth Keys

Owner
Single Signature
Public Keys
STM68YcjUfh46DoPkPJyuzxBnX2DmT1LdwfMg6DmhYc1iGuLph7xP1/1
Active
Single Signature
Public Keys
STM7PU5PwJhzt5UK9HQpRMDickNU3XHtjYnyfJwCun7e4cunv5Nqu1/1
Posting
Single Signature
Public Keys
STM7UFy7nXo1TxZ4vgWHYEXtH7dX8Dnj8Uwh1gbmpYPYEMBgx9HiS1/1
Memo
STM7ZXkRzUrJz7BZorrLT2FhMrKRU8gGfYujDG9pLNMuz2nSG1pMK
{
  "owner": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM68YcjUfh46DoPkPJyuzxBnX2DmT1LdwfMg6DmhYc1iGuLph7xP",
        1
      ]
    ]
  },
  "active": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM7PU5PwJhzt5UK9HQpRMDickNU3XHtjYnyfJwCun7e4cunv5Nqu",
        1
      ]
    ]
  },
  "posting": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM7UFy7nXo1TxZ4vgWHYEXtH7dX8Dnj8Uwh1gbmpYPYEMBgx9HiS",
        1
      ]
    ]
  },
  "memo": "STM7ZXkRzUrJz7BZorrLT2FhMrKRU8gGfYujDG9pLNMuz2nSG1pMK"
}

Witness Votes

0 / 30
No active witness votes.
[]