VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS0.00%
Net Worth
0.049USD
STEEM
0.003STEEM
SBD
0.025SBD
Effective Power
5.007SP
├── Own SP
0.632SP
└── Incoming DelegationsDeleg
+4.375SP
Detailed Balance
| STEEM | ||
| balance | 0.000STEEM | STEEM |
| market_balance | 0.000STEEM | STEEM |
| savings_balance | 0.000STEEM | STEEM |
| reward_steem_balance | 0.003STEEM | STEEM |
| STEEM POWER | ||
| Own SP | 0.632SP | SP |
| Delegated Out | 0.000SP | SP |
| Delegation In | 4.375SP | SP |
| Effective Power | 5.007SP | SP |
| Reward SP (pending) | 0.018SP | SP |
| SBD | ||
| sbd_balance | 0.000SBD | SBD |
| sbd_conversions | 0.000SBD | SBD |
| sbd_market_balance | 0.000SBD | SBD |
| savings_sbd_balance | 0.000SBD | SBD |
| reward_sbd_balance | 0.025SBD | SBD |
{
"balance": "0.000 STEEM",
"savings_balance": "0.000 STEEM",
"reward_steem_balance": "0.003 STEEM",
"vesting_shares": "1028.349801 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "7115.310005 VESTS",
"sbd_balance": "0.000 SBD",
"savings_sbd_balance": "0.000 SBD",
"reward_sbd_balance": "0.025 SBD",
"conversions": []
}Account Info
| name | torib |
| id | 416362 |
| rank | 847,050 |
| reputation | 376346979 |
| created | 2017-10-20T20:30:18 |
| recovery_account | steem |
| proxy | None |
| post_count | 3 |
| comment_count | 0 |
| lifetime_vote_count | 0 |
| witnesses_voted_for | 0 |
| last_post | 2018-03-21T15:05:33 |
| last_root_post | 2018-03-21T15:05:33 |
| last_vote_time | 2018-03-21T15:15:39 |
| proxied_vsf_votes | 0, 0, 0, 0 |
| can_vote | 1 |
| voting_power | 0 |
| delayed_votes | 0 |
| balance | 0.000 STEEM |
| savings_balance | 0.000 STEEM |
| sbd_balance | 0.000 SBD |
| savings_sbd_balance | 0.000 SBD |
| vesting_shares | 1028.349801 VESTS |
| delegated_vesting_shares | 0.000000 VESTS |
| received_vesting_shares | 7115.310005 VESTS |
| reward_vesting_balance | 36.726503 VESTS |
| vesting_balance | 0.000 STEEM |
| vesting_withdraw_rate | 0.000000 VESTS |
| next_vesting_withdrawal | 1969-12-31T23:59:59 |
| withdrawn | 0 |
| to_withdraw | 0 |
| withdraw_routes | 0 |
| savings_withdraw_requests | 0 |
| last_account_recovery | 1970-01-01T00:00:00 |
| reset_account | null |
| last_owner_update | 1970-01-01T00:00:00 |
| last_account_update | 2017-10-20T20:36:15 |
| mined | No |
| sbd_seconds | 0 |
| sbd_last_interest_payment | 1970-01-01T00:00:00 |
| savings_sbd_last_interest_payment | 1970-01-01T00:00:00 |
{
"id": 416362,
"name": "torib",
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5dZ1vg6cwUyaRveyDsBv65HovLJpoqnzYcaPerjEjHVfJPLGaq",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM738TBZdcbKqxhYy6RAtGi8yeHdsikPfSrGGWDHzZWobwGtyXnD",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM6YQJG7RZxbWCjzeAs4AdSdUWWUSM6YLa56icyZvm9T4efTKXLg",
1
]
]
},
"memo_key": "STM7snt5zSWgue38Ue9SD5xpU6CUzyaA7i3zXMJGjuDT2SEAD5DQG",
"json_metadata": "{\"profile\":{\"profile_image\":\"https://pbs.twimg.com/profile_images/839587883837190145/c58vTBrB.jpg\",\"name\":\"Tori Benson\",\"about\":\"COO at Hanzo\",\"location\":\"Kansas City, MO\",\"website\":\"https://www.linkedin.com/in/tori-benson/\"}}",
"posting_json_metadata": "{\"profile\":{\"profile_image\":\"https://pbs.twimg.com/profile_images/839587883837190145/c58vTBrB.jpg\",\"name\":\"Tori Benson\",\"about\":\"COO at Hanzo\",\"location\":\"Kansas City, MO\",\"website\":\"https://www.linkedin.com/in/tori-benson/\"}}",
"proxy": "",
"last_owner_update": "1970-01-01T00:00:00",
"last_account_update": "2017-10-20T20:36:15",
"created": "2017-10-20T20:30:18",
"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": 3,
"can_vote": true,
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779089766
},
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779089766
},
"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.025 SBD",
"reward_steem_balance": "0.003 STEEM",
"reward_vesting_balance": "36.726503 VESTS",
"reward_vesting_steem": "0.018 STEEM",
"vesting_shares": "1028.349801 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "7115.310005 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": 35,
"proxied_vsf_votes": [
0,
0,
0,
0
],
"witnesses_voted_for": 0,
"last_post": "2018-03-21T15:05:33",
"last_root_post": "2018-03-21T15:05:33",
"last_vote_time": "2018-03-21T15:15:39",
"post_bandwidth": 0,
"pending_claimed_accounts": 0,
"vesting_balance": "0.000 STEEM",
"reputation": 376346979,
"transfer_history": [],
"market_history": [],
"post_history": [],
"vote_history": [],
"other_history": [],
"witness_votes": [],
"tags_usage": [],
"guest_bloggers": [],
"rank": 847050
}Withdraw Routes
| Incoming | Outgoing |
|---|---|
Empty | Empty |
{
"incoming": [],
"outgoing": []
}From Date
To Date
2026/05/18 07:36:06
2026/05/18 07:36:06
| delegator | steem |
| delegatee | torib |
| vesting shares | 7115.310005 VESTS |
| Transaction Info | Block #106152230/Trx e8a0c9ec4f9f90794457015165d9bed2346f26ad |
View Raw JSON Data
{
"trx_id": "e8a0c9ec4f9f90794457015165d9bed2346f26ad",
"block": 106152230,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-05-18T07:36:06",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "torib",
"vesting_shares": "7115.310005 VESTS"
}
]
}2026/05/13 09:38:21
2026/05/13 09:38:21
| delegator | steem |
| delegatee | torib |
| vesting shares | 4403.099600 VESTS |
| Transaction Info | Block #106011384/Trx a9464949bf69716ef932d01e3a80bb07d7924457 |
View Raw JSON Data
{
"trx_id": "a9464949bf69716ef932d01e3a80bb07d7924457",
"block": 106011384,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-05-13T09:38:21",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "torib",
"vesting_shares": "4403.099600 VESTS"
}
]
}2026/04/26 06:46:06
2026/04/26 06:46:06
| delegator | steem |
| delegatee | torib |
| vesting shares | 7127.825761 VESTS |
| Transaction Info | Block #105519679/Trx 86cfca7219f0ebdee6c7c6bf4752c6462408c956 |
View Raw JSON Data
{
"trx_id": "86cfca7219f0ebdee6c7c6bf4752c6462408c956",
"block": 105519679,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-04-26T06:46:06",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "torib",
"vesting_shares": "7127.825761 VESTS"
}
]
}2026/01/24 03:32:39
2026/01/24 03:32:39
| delegator | steem |
| delegatee | torib |
| vesting shares | 4444.646419 VESTS |
| Transaction Info | Block #102875454/Trx b17aa16244bb0c898e721272ac6bb69032a5871d |
View Raw JSON Data
{
"trx_id": "b17aa16244bb0c898e721272ac6bb69032a5871d",
"block": 102875454,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-01-24T03:32:39",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "torib",
"vesting_shares": "4444.646419 VESTS"
}
]
}2024/12/17 22:41:24
2024/12/17 22:41:24
| delegator | steem |
| delegatee | torib |
| vesting shares | 4608.865616 VESTS |
| Transaction Info | Block #91321649/Trx 47fd65bd20ec7af87f0de9746f392746ed21d51d |
View Raw JSON Data
{
"trx_id": "47fd65bd20ec7af87f0de9746f392746ed21d51d",
"block": 91321649,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2024-12-17T22:41:24",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "torib",
"vesting_shares": "4608.865616 VESTS"
}
]
}2023/11/14 14:19:45
2023/11/14 14:19:45
| delegator | steem |
| delegatee | torib |
| vesting shares | 4777.999148 VESTS |
| Transaction Info | Block #79875731/Trx 4d8f89a52ab08155683cac17e7ea44609f705678 |
View Raw JSON Data
{
"trx_id": "4d8f89a52ab08155683cac17e7ea44609f705678",
"block": 79875731,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2023-11-14T14:19:45",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "torib",
"vesting_shares": "4777.999148 VESTS"
}
]
}2023/09/22 11:55:54
2023/09/22 11:55:54
| delegator | steem |
| delegatee | torib |
| vesting shares | 7714.907934 VESTS |
| Transaction Info | Block #78364706/Trx b88ed200ef7763adba5e74097e1e566167e3edec |
View Raw JSON Data
{
"trx_id": "b88ed200ef7763adba5e74097e1e566167e3edec",
"block": 78364706,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2023-09-22T11:55:54",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "torib",
"vesting_shares": "7714.907934 VESTS"
}
]
}2022/11/03 19:13:09
2022/11/03 19:13:09
| delegator | steem |
| delegatee | torib |
| vesting shares | 7936.959372 VESTS |
| Transaction Info | Block #69122237/Trx f16143c25d21a22aa51ae1789c7c5fd7cd689782 |
View Raw JSON Data
{
"trx_id": "f16143c25d21a22aa51ae1789c7c5fd7cd689782",
"block": 69122237,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2022-11-03T19:13:09",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "torib",
"vesting_shares": "7936.959372 VESTS"
}
]
}2022/01/18 00:17:24
2022/01/18 00:17:24
| delegator | steem |
| delegatee | torib |
| vesting shares | 8157.066973 VESTS |
| Transaction Info | Block #60825335/Trx adc521f1aa628717d6e0900df663b6c459cec296 |
View Raw JSON Data
{
"trx_id": "adc521f1aa628717d6e0900df663b6c459cec296",
"block": 60825335,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2022-01-18T00:17:24",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "torib",
"vesting_shares": "8157.066973 VESTS"
}
]
}2021/06/14 07:25:03
2021/06/14 07:25:03
| delegator | steem |
| delegatee | torib |
| vesting shares | 8341.261261 VESTS |
| Transaction Info | Block #54615589/Trx ba21b7e6603210cbfd4c405b8a0d8dbde32aa6c4 |
View Raw JSON Data
{
"trx_id": "ba21b7e6603210cbfd4c405b8a0d8dbde32aa6c4",
"block": 54615589,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2021-06-14T07:25:03",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "torib",
"vesting_shares": "8341.261261 VESTS"
}
]
}2020/12/11 17:36:12
2020/12/11 17:36:12
| delegator | steem |
| delegatee | torib |
| vesting shares | 8528.683235 VESTS |
| Transaction Info | Block #49362813/Trx f560e084070dfc0e717acb32adaf8cf636c24b18 |
View Raw JSON Data
{
"trx_id": "f560e084070dfc0e717acb32adaf8cf636c24b18",
"block": 49362813,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-12-11T17:36:12",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "torib",
"vesting_shares": "8528.683235 VESTS"
}
]
}2020/12/06 11:11:27
2020/12/06 11:11:27
| delegator | steem |
| delegatee | torib |
| vesting shares | 1912.543513 VESTS |
| Transaction Info | Block #49214326/Trx 5074a5e38400d0a88ea89cf5efb9d96702e1e02b |
View Raw JSON Data
{
"trx_id": "5074a5e38400d0a88ea89cf5efb9d96702e1e02b",
"block": 49214326,
"trx_in_block": 14,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-12-06T11:11:27",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "torib",
"vesting_shares": "1912.543513 VESTS"
}
]
}2020/12/05 21:14:00
2020/12/05 21:14:00
| delegator | steem |
| delegatee | torib |
| vesting shares | 8534.891089 VESTS |
| Transaction Info | Block #49197894/Trx 6688f37100dc11128bfb9aef1e933e8fd19338e4 |
View Raw JSON Data
{
"trx_id": "6688f37100dc11128bfb9aef1e933e8fd19338e4",
"block": 49197894,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-12-05T21:14:00",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "torib",
"vesting_shares": "8534.891089 VESTS"
}
]
}2020/11/03 05:04:06
2020/11/03 05:04:06
| delegator | steem |
| delegatee | torib |
| vesting shares | 1920.017158 VESTS |
| Transaction Info | Block #48273613/Trx 7fec7afdc0a3290a4297896163d12d452fc875d4 |
View Raw JSON Data
{
"trx_id": "7fec7afdc0a3290a4297896163d12d452fc875d4",
"block": 48273613,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-11-03T05:04:06",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "torib",
"vesting_shares": "1920.017158 VESTS"
}
]
}2020/05/09 12:15:39
2020/05/09 12:15:39
| delegator | steem |
| delegatee | torib |
| vesting shares | 8737.696448 VESTS |
| Transaction Info | Block #43224676/Trx 2a36fc6879ced2b1113bf2dde552d201cfccae8f |
View Raw JSON Data
{
"trx_id": "2a36fc6879ced2b1113bf2dde552d201cfccae8f",
"block": 43224676,
"trx_in_block": 51,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-05-09T12:15:39",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "torib",
"vesting_shares": "8737.696448 VESTS"
}
]
}2020/05/08 16:50:18
2020/05/08 16:50:18
| delegator | steem |
| delegatee | torib |
| vesting shares | 1953.311140 VESTS |
| Transaction Info | Block #43201918/Trx ba3703153dbb4cc7c911502936d8e56f8a077b33 |
View Raw JSON Data
{
"trx_id": "ba3703153dbb4cc7c911502936d8e56f8a077b33",
"block": 43201918,
"trx_in_block": 11,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-05-08T16:50:18",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "torib",
"vesting_shares": "1953.311140 VESTS"
}
]
}2019/10/20 21:51:12
2019/10/20 21:51:12
| parent author | torib |
| parent permlink | united-states-of-crypto |
| author | steemitboard |
| permlink | steemitboard-notify-torib-20191020t215111000z |
| title | |
| body | Congratulations @torib! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@torib/birthday2.png</td><td>Happy Birthday! - You are on the Steem blockchain for 2 years!</td></tr></table> <sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@torib) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=torib)_</sub> **Do not miss the last post from @steemitboard:** <table><tr><td><a href="https://steemit.com/steemfest/@steemitboard/steemfest-commemorative-badge-refactored"><img src="https://steemitimages.com/64x128/https://files.steempeak.com/file/steempeak/arcange/YqQV5Tbj-image.png"></a></td><td><a href="https://steemit.com/steemfest/@steemitboard/steemfest-commemorative-badge-refactored">SteemFest⁴ commemorative badge refactored</a></td></tr></table> ###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| Transaction Info | Block #37460047/Trx 920a900ee3279ee6be602c336f8cb8f8b442fde4 |
View Raw JSON Data
{
"trx_id": "920a900ee3279ee6be602c336f8cb8f8b442fde4",
"block": 37460047,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-10-20T21:51:12",
"op": [
"comment",
{
"parent_author": "torib",
"parent_permlink": "united-states-of-crypto",
"author": "steemitboard",
"permlink": "steemitboard-notify-torib-20191020t215111000z",
"title": "",
"body": "Congratulations @torib! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@torib/birthday2.png</td><td>Happy Birthday! - You are on the Steem blockchain for 2 years!</td></tr></table>\n\n<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@torib) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=torib)_</sub>\n\n\n**Do not miss the last post from @steemitboard:**\n<table><tr><td><a href=\"https://steemit.com/steemfest/@steemitboard/steemfest-commemorative-badge-refactored\"><img src=\"https://steemitimages.com/64x128/https://files.steempeak.com/file/steempeak/arcange/YqQV5Tbj-image.png\"></a></td><td><a href=\"https://steemit.com/steemfest/@steemitboard/steemfest-commemorative-badge-refactored\">SteemFest⁴ commemorative badge refactored</a></td></tr></table>\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}"
}
]
}2019/06/13 01:31:24
2019/06/13 01:31:24
| delegator | steem |
| delegatee | torib |
| vesting shares | 8928.000344 VESTS |
| Transaction Info | Block #33750161/Trx e70f4253237cc95ba52704d2f7f5704f92d827a9 |
View Raw JSON Data
{
"trx_id": "e70f4253237cc95ba52704d2f7f5704f92d827a9",
"block": 33750161,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-06-13T01:31:24",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "torib",
"vesting_shares": "8928.000344 VESTS"
}
]
}2018/10/21 03:39:09
2018/10/21 03:39:09
| parent author | torib |
| parent permlink | united-states-of-crypto |
| author | steemitboard |
| permlink | steemitboard-notify-torib-20181021t033911000z |
| title | |
| body | Congratulations @torib! You have received a personal award! [](http://steemitboard.com/@torib) 1 Year on Steemit <sub>_Click on the badge to view your Board of Honor._</sub> **Do not miss the last post from @steemitboard:** <table><tr><td><a href="https://steemit.com/steemitboard/@steemitboard/steemitboard-ranking-update-resteem-and-resteemed-added"><img src="https://steemitimages.com/64x128/https://cdn.steemitimages.com/DQmfRVpHQhLDhnjDtqck8GPv9NPvNKPfMsDaAFDE1D9Er2Z/header_ranking.png"></a></td><td><a href="https://steemit.com/steemitboard/@steemitboard/steemitboard-ranking-update-resteem-and-resteemed-added">SteemitBoard Ranking update - Resteem and Resteemed added</a></td></tr></table> > Support [SteemitBoard's project](https://steemit.com/@steemitboard)! **[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 Info | Block #26991247/Trx a4529d1a55e58effde14b910eedbe5e7fe9c6116 |
View Raw JSON Data
{
"trx_id": "a4529d1a55e58effde14b910eedbe5e7fe9c6116",
"block": 26991247,
"trx_in_block": 19,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-10-21T03:39:09",
"op": [
"comment",
{
"parent_author": "torib",
"parent_permlink": "united-states-of-crypto",
"author": "steemitboard",
"permlink": "steemitboard-notify-torib-20181021t033911000z",
"title": "",
"body": "Congratulations @torib! You have received a personal award!\n\n[](http://steemitboard.com/@torib) 1 Year on Steemit\n<sub>_Click on the badge to view your Board of Honor._</sub>\n\n\n**Do not miss the last post from @steemitboard:**\n<table><tr><td><a href=\"https://steemit.com/steemitboard/@steemitboard/steemitboard-ranking-update-resteem-and-resteemed-added\"><img src=\"https://steemitimages.com/64x128/https://cdn.steemitimages.com/DQmfRVpHQhLDhnjDtqck8GPv9NPvNKPfMsDaAFDE1D9Er2Z/header_ranking.png\"></a></td><td><a href=\"https://steemit.com/steemitboard/@steemitboard/steemitboard-ranking-update-resteem-and-resteemed-added\">SteemitBoard Ranking update - Resteem and Resteemed added</a></td></tr></table>\n\n> Support [SteemitBoard's project](https://steemit.com/@steemitboard)! **[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/20 15:44:27
2018/06/20 15:44:27
| delegator | steem |
| delegatee | torib |
| vesting shares | 9127.357029 VESTS |
| Transaction Info | Block #23491204/Trx 7e08e5a6aaf98055d9b242bdb6c7f4cbfb667e1d |
View Raw JSON Data
{
"trx_id": "7e08e5a6aaf98055d9b242bdb6c7f4cbfb667e1d",
"block": 23491204,
"trx_in_block": 15,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-20T15:44:27",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "torib",
"vesting_shares": "9127.357029 VESTS"
}
]
}2018/04/21 20:54:21
2018/04/21 20:54:21
| delegator | steem |
| delegatee | torib |
| vesting shares | 29533.818147 VESTS |
| Transaction Info | Block #21771374/Trx f20d51e46d5417c45200cc30d6de617df0ec2ccb |
View Raw JSON Data
{
"trx_id": "f20d51e46d5417c45200cc30d6de617df0ec2ccb",
"block": 21771374,
"trx_in_block": 53,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-21T20:54:21",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "torib",
"vesting_shares": "29533.818147 VESTS"
}
]
}toribreceived 0.002 STEEM, 0.016 SBD, 0.015 SP author reward for @torib / united-states-of-crypto2018/03/28 15:05:33
toribreceived 0.002 STEEM, 0.016 SBD, 0.015 SP author reward for @torib / united-states-of-crypto
2018/03/28 15:05:33
| author | torib |
| permlink | united-states-of-crypto |
| sbd payout | 0.016 SBD |
| steem payout | 0.002 STEEM |
| vesting payout | 24.481031 VESTS |
| Transaction Info | Block #21073325/Virtual Operation #16 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 21073325,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 16,
"timestamp": "2018-03-28T15:05:33",
"op": [
"author_reward",
{
"author": "torib",
"permlink": "united-states-of-crypto",
"sbd_payout": "0.016 SBD",
"steem_payout": "0.002 STEEM",
"vesting_payout": "24.481031 VESTS"
}
]
}avataraustinupvoted (100.00%) @torib / united-states-of-crypto2018/03/24 17:09:48
avataraustinupvoted (100.00%) @torib / united-states-of-crypto
2018/03/24 17:09:48
| voter | avataraustin |
| author | torib |
| permlink | united-states-of-crypto |
| weight | 10000 (100.00%) |
| Transaction Info | Block #20960644/Trx 2e70e66cb861cc5f5bf1cb2f4542b3dfe044ee41 |
View Raw JSON Data
{
"trx_id": "2e70e66cb861cc5f5bf1cb2f4542b3dfe044ee41",
"block": 20960644,
"trx_in_block": 11,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-24T17:09:48",
"op": [
"vote",
{
"voter": "avataraustin",
"author": "torib",
"permlink": "united-states-of-crypto",
"weight": 10000
}
]
}sensationupvoted (100.00%) @torib / united-states-of-crypto2018/03/21 15:54:03
sensationupvoted (100.00%) @torib / united-states-of-crypto
2018/03/21 15:54:03
| voter | sensation |
| author | torib |
| permlink | united-states-of-crypto |
| weight | 10000 (100.00%) |
| Transaction Info | Block #20873124/Trx 811d1e313dd29f48e2b656f6245136389a163170 |
View Raw JSON Data
{
"trx_id": "811d1e313dd29f48e2b656f6245136389a163170",
"block": 20873124,
"trx_in_block": 19,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-21T15:54:03",
"op": [
"vote",
{
"voter": "sensation",
"author": "torib",
"permlink": "united-states-of-crypto",
"weight": 10000
}
]
}moby-dickupvoted (100.00%) @torib / united-states-of-crypto2018/03/21 15:44:39
moby-dickupvoted (100.00%) @torib / united-states-of-crypto
2018/03/21 15:44:39
| voter | moby-dick |
| author | torib |
| permlink | united-states-of-crypto |
| weight | 10000 (100.00%) |
| Transaction Info | Block #20872937/Trx 0ffaebbec2860633bc0b06fd3d9557af07fbdd79 |
View Raw JSON Data
{
"trx_id": "0ffaebbec2860633bc0b06fd3d9557af07fbdd79",
"block": 20872937,
"trx_in_block": 14,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-21T15:44:39",
"op": [
"vote",
{
"voter": "moby-dick",
"author": "torib",
"permlink": "united-states-of-crypto",
"weight": 10000
}
]
}cortexxupvoted (3.00%) @torib / united-states-of-crypto2018/03/21 15:38:51
cortexxupvoted (3.00%) @torib / united-states-of-crypto
2018/03/21 15:38:51
| voter | cortexx |
| author | torib |
| permlink | united-states-of-crypto |
| weight | 300 (3.00%) |
| Transaction Info | Block #20872822/Trx 29e941b2f2433640ea5191ee0c1ae0908a944cdc |
View Raw JSON Data
{
"trx_id": "29e941b2f2433640ea5191ee0c1ae0908a944cdc",
"block": 20872822,
"trx_in_block": 52,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-21T15:38:51",
"op": [
"vote",
{
"voter": "cortexx",
"author": "torib",
"permlink": "united-states-of-crypto",
"weight": 300
}
]
}2018/03/21 15:20:24
2018/03/21 15:20:24
| parent author | torib |
| parent permlink | united-states-of-crypto |
| author | zeekay |
| permlink | re-torib-united-states-of-crypto-20180321t152030016z |
| title | |
| body | Terrific new series! Thanks for keeping us apprised of the latest developments in crypto politically. Very important work :) |
| json metadata | {"tags":["blockchain"],"app":"steemit/0.1"} |
| Transaction Info | Block #20872454/Trx b813b1a5dfe4ae21c34349ff3c0d89e3f38a9fc6 |
View Raw JSON Data
{
"trx_id": "b813b1a5dfe4ae21c34349ff3c0d89e3f38a9fc6",
"block": 20872454,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-21T15:20:24",
"op": [
"comment",
{
"parent_author": "torib",
"parent_permlink": "united-states-of-crypto",
"author": "zeekay",
"permlink": "re-torib-united-states-of-crypto-20180321t152030016z",
"title": "",
"body": "Terrific new series! Thanks for keeping us apprised of the latest developments in crypto politically. Very important work :)",
"json_metadata": "{\"tags\":[\"blockchain\"],\"app\":\"steemit/0.1\"}"
}
]
}toribupvoted (100.00%) @torib / united-states-of-crypto2018/03/21 15:15:39
toribupvoted (100.00%) @torib / united-states-of-crypto
2018/03/21 15:15:39
| voter | torib |
| author | torib |
| permlink | united-states-of-crypto |
| weight | 10000 (100.00%) |
| Transaction Info | Block #20872359/Trx c73099123afb5145ef6194259988f98e920eb648 |
View Raw JSON Data
{
"trx_id": "c73099123afb5145ef6194259988f98e920eb648",
"block": 20872359,
"trx_in_block": 28,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-21T15:15:39",
"op": [
"vote",
{
"voter": "torib",
"author": "torib",
"permlink": "united-states-of-crypto",
"weight": 10000
}
]
}zeekayupvoted (100.00%) @torib / united-states-of-crypto2018/03/21 15:12:51
zeekayupvoted (100.00%) @torib / united-states-of-crypto
2018/03/21 15:12:51
| voter | zeekay |
| author | torib |
| permlink | united-states-of-crypto |
| weight | 10000 (100.00%) |
| Transaction Info | Block #20872304/Trx e85c2994afece56c203bc9f3d568ca3911e27305 |
View Raw JSON Data
{
"trx_id": "e85c2994afece56c203bc9f3d568ca3911e27305",
"block": 20872304,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-21T15:12:51",
"op": [
"vote",
{
"voter": "zeekay",
"author": "torib",
"permlink": "united-states-of-crypto",
"weight": 10000
}
]
}toribpublished a new post: united-states-of-crypto2018/03/21 15:05:33
toribpublished a new post: united-states-of-crypto
2018/03/21 15:05:33
| parent author | |
| parent permlink | blockchain |
| author | torib |
| permlink | united-states-of-crypto |
| title | United States of Crypto |
| body | *United States of Crypto is a weekly series on US state level rules and regulations relating to blockchain and cryptocurrencies.*  **Colorado SB68** The Bill: Senate Bill 18–086 titled “Cyber Coding Cryptology for State Records,” is a bipartisan bill introduced in the Colorado Senate this week. The bill requires some specific state agencies examine state cyber security weaknesses and assess the cost of implementing “distributed ledger technology such as blockchain.” The bill specifically suggests using blockchain for business licensing, preserving the integrity and security of state data, and encourages the university system to adopt blockchain curriculum. Deep Dive: The bill was amended to, among other things, ensure that no county or municipal government could levy a tax or fee to use blockchain and that the state couldn’t require someone to have a permit to use blockchain technology. This was adopted unanimously. The final bill was referred to Appropriations with 2 no votes, Republican Senators Smallwood and Neville. Take Away: Concerns about the security of personal information in state record systems is a major issue in legislative bodies across the country. Republican legislators, especially, are concerned with state data about individual citizens falling into the hands of federal regulators. I’ll be keeping an eye on how this bill performs in committee as it was just assigned from the committee on Business, Labor & Technology to Appropriations with a fiscal note estimating the cost to be $250,000. This means the Appropriations committee will need to find a way to fit a quarter million dollars in to explore blockchain technology. See the bill here: http://leg.colorado.gov/bills/sb18-086 **Securities in South Carolina** Enforcement: The South Carolina Attorney General filed a cease and desist order to against Genesis Mining and Swiss Gold Global, two cloud mining enterprises. The companies were offering “mining contracts,” which would essentially let individuals buy-in to a piece of the mining profits. AG Alan Wilson has ordered the companies to cease operations in South Carolina, on the grounds that mining contracts are a security. He has also barred both companies from ever offering securities in South Carolina again. Take Away: The AG’s office said that it had been monitoring cryptocurrencies for several years. South Carolina is not the only state to have gone after crypto companies in recent weeks. Texas and New Jersey have also served cease and desists to separate cryptocurrency related companies. This tells us that states are starting to pay attention to possible abuses in the crypto industry and that blockchain companies would do well to 1. Pay attention to the innovation environment in their state and 2. Start communicating with local politicians early. I’ve found that “all politics is local,” is truer than you might imagine and state politicians are especially sensitive to constituent issues. See: https://cointelegraph.com/news/south-carolina-wants-to-ban-genesis-mining-over-unregistered-securities https://www.postandcourier.com/business/south-carolina-cracks-down-on-cryptocurrency-mining-investment-scheme/article_714e9e24-287a-11e8-b553-638ea33cc9c5.html **Wyoming HB70** The Bills: The State of Wyoming took decisive steps last week to become a welcoming haven for cryptocurrency and blockchain companies. The Wyoming legislature passed 5 bills related to blockchain in an effort to lure businesses to the state. The most exciting of the bills, HB70 defines utility tokens as an entirely new class of assets, different from securities or commodities. This is particularly interesting as larger national and international governments have attempted to define cryptocurrencies as existing asset classes but have generally failed to agree on which is correct. Wyoming, however, defines utility tokens as property which is typically governed by state law. Deep Dive: Four other bills signed in Wyoming also directly aim to incentivise new cryptocurrency and blockchain businesses. HB19 exempts cryptocurrencies from Wyoming’s money transmitter laws. This was in direct response to Coinbase and two other exchanges ceasing operations in Wyoming after the original money transmitter laws were passed. HB101 allows Wyoming businesses to use blockchain to store records and manage shareholders. HB126 doesn’t specifically reference token sales but would likely limit liability for companies wishing to develop decentralized governance protocols or distribute tokens. SF111 creates a property tax exemption for cryptocurrencies. All five bills have been signed into law by the governor. See: https://www.ethnews.com/wyoming-legislature-goes-all-in-on-blockchain-cryptocurrency-bills https://www.forbes.com/sites/rachelwolfson/2018/03/13/u-s-state-of-wyoming-defines-cryptocurrency-utility-tokens-as-new-asset-class/2/#471f0edc6d45 http://legisweb.state.wy.us/2018/billreference/BillReference.aspx?type=ALL **Arizona HB2601, 2602, 2603** The Bills: Three bills in Arizona all introduced by Republican State Rep. Jeff Weninger are moving to make it easier on blockchain companies. HB2601 changes Arizona’s securities laws relating to virtual coin offerings, and creates exemptions for intrastate crowdfunding. HB2602 would prohibit any city, town or county for making rules against individuals running nodes on a blockchain. HB2603 preemptively allows companies to use blockchain for financial recording. Deep Dive: By my reading of the HB2601, it seems to state that “virtual coins,” presumably cryptocurrencies themselves are not necessarily securities. Virtual coin offerings, however, might be if they have been marketed and do not have utility within 90 days. Essentially, it makes the distinction between security tokens and utility tokens. HB2601 was reported do pass from the senate committee on finance on 3/14 and will need to pass rules committee, pass a third read on the senate floor and receive the governor’s signature. HB2602 doesn’t seem to prohibit the state legislature from making rules regarding running blockchain nodes, but prohibits local governments from doing so by labeling running a blockchain node a, “statewide concern.” On 3/15 this bill was voted do pass from the senate committee of the whole, which means it must still pass a vote of the full senate and be signed by the governor. The bill is not yet on the third read calendar. HB2603 has passed the house, and is waiting to pass third read on the senate floor and the governor’s signature. Take Away: Interestingly, in Arizona the partisan leaning of the issue is different than in Colorado. 8 House Democrats and one Senate Democrat voted no on HB2601. I imagine the argument has to do with local control and consumer protection, but that it’s largely a vote against a Republican Rep’s bill. See: https://www.coindesk.com/arizonas-blockchain-node-rights-law-nearing-passage/ https://www.ethnews.com/arizona-bill-aims-to-prevent-regulation-of-blockchain-nodes https://www.azleg.gov/press/house/53LEG/2R/180206WENINGERBLOCKCHAIN2.pdf http://arizonasonoranewsservice.com/arizona-to-regulate-cryptocurrency-offerings-crowdfunding-and-blockchains/ |
| json metadata | {"tags":["blockchain","statelaw","cryptocurrency","mining","regulation"],"image":["https://steemitimages.com/DQmdP66m1VqcDr8rbWFCk5Nx5J2uv9PEiSHzvtQjGreyMCg/uscrypto.jpg"],"links":["http://leg.colorado.gov/bills/sb18-086","https://cointelegraph.com/news/south-carolina-wants-to-ban-genesis-mining-over-unregistered-securities","https://www.postandcourier.com/business/south-carolina-cracks-down-on-cryptocurrency-mining-investment-scheme/article_714e9e24-287a-11e8-b553-638ea33cc9c5.html","https://www.ethnews.com/wyoming-legislature-goes-all-in-on-blockchain-cryptocurrency-bills","https://www.forbes.com/sites/rachelwolfson/2018/03/13/u-s-state-of-wyoming-defines-cryptocurrency-utility-tokens-as-new-asset-class/2/#471f0edc6d45","http://legisweb.state.wy.us/2018/billreference/BillReference.aspx?type=ALL","https://www.coindesk.com/arizonas-blockchain-node-rights-law-nearing-passage/","https://www.ethnews.com/arizona-bill-aims-to-prevent-regulation-of-blockchain-nodes","https://www.azleg.gov/press/house/53LEG/2R/180206WENINGERBLOCKCHAIN2.pdf","http://arizonasonoranewsservice.com/arizona-to-regulate-cryptocurrency-offerings-crowdfunding-and-blockchains/"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #20872158/Trx 1dcd16212c42f89fe8a20eb13d3463fe432f4100 |
View Raw JSON Data
{
"trx_id": "1dcd16212c42f89fe8a20eb13d3463fe432f4100",
"block": 20872158,
"trx_in_block": 12,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-21T15:05:33",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "blockchain",
"author": "torib",
"permlink": "united-states-of-crypto",
"title": "United States of Crypto",
"body": "*United States of Crypto is a weekly series on US state level rules and regulations relating to blockchain and cryptocurrencies.*\n\n\n\n**Colorado SB68**\nThe Bill: Senate Bill 18–086 titled “Cyber Coding Cryptology for State Records,” is a bipartisan bill introduced in the Colorado Senate this week. The bill requires some specific state agencies examine state cyber security weaknesses and assess the cost of implementing “distributed ledger technology such as blockchain.” The bill specifically suggests using blockchain for business licensing, preserving the integrity and security of state data, and encourages the university system to adopt blockchain curriculum.\n\nDeep Dive: The bill was amended to, among other things, ensure that no county or municipal government could levy a tax or fee to use blockchain and that the state couldn’t require someone to have a permit to use blockchain technology. This was adopted unanimously. The final bill was referred to Appropriations with 2 no votes, Republican Senators Smallwood and Neville.\n\nTake Away: Concerns about the security of personal information in state record systems is a major issue in legislative bodies across the country. Republican legislators, especially, are concerned with state data about individual citizens falling into the hands of federal regulators. I’ll be keeping an eye on how this bill performs in committee as it was just assigned from the committee on Business, Labor & Technology to Appropriations with a fiscal note estimating the cost to be $250,000. This means the Appropriations committee will need to find a way to fit a quarter million dollars in to explore blockchain technology.\n\nSee the bill here: http://leg.colorado.gov/bills/sb18-086\n\n**Securities in South Carolina**\nEnforcement: The South Carolina Attorney General filed a cease and desist order to against Genesis Mining and Swiss Gold Global, two cloud mining enterprises. The companies were offering “mining contracts,” which would essentially let individuals buy-in to a piece of the mining profits. AG Alan Wilson has ordered the companies to cease operations in South Carolina, on the grounds that mining contracts are a security. He has also barred both companies from ever offering securities in South Carolina again.\n\nTake Away: The AG’s office said that it had been monitoring cryptocurrencies for several years. South Carolina is not the only state to have gone after crypto companies in recent weeks. Texas and New Jersey have also served cease and desists to separate cryptocurrency related companies. This tells us that states are starting to pay attention to possible abuses in the crypto industry and that blockchain companies would do well to 1. Pay attention to the innovation environment in their state and 2. Start communicating with local politicians early. I’ve found that “all politics is local,” is truer than you might imagine and state politicians are especially sensitive to constituent issues.\n\nSee: https://cointelegraph.com/news/south-carolina-wants-to-ban-genesis-mining-over-unregistered-securities\nhttps://www.postandcourier.com/business/south-carolina-cracks-down-on-cryptocurrency-mining-investment-scheme/article_714e9e24-287a-11e8-b553-638ea33cc9c5.html\n\n**Wyoming HB70**\nThe Bills: The State of Wyoming took decisive steps last week to become a welcoming haven for cryptocurrency and blockchain companies. The Wyoming legislature passed 5 bills related to blockchain in an effort to lure businesses to the state. The most exciting of the bills, HB70 defines utility tokens as an entirely new class of assets, different from securities or commodities. This is particularly interesting as larger national and international governments have attempted to define cryptocurrencies as existing asset classes but have generally failed to agree on which is correct. Wyoming, however, defines utility tokens as property which is typically governed by state law.\n\nDeep Dive: Four other bills signed in Wyoming also directly aim to incentivise new cryptocurrency and blockchain businesses. HB19 exempts cryptocurrencies from Wyoming’s money transmitter laws. This was in direct response to Coinbase and two other exchanges ceasing operations in Wyoming after the original money transmitter laws were passed. HB101 allows Wyoming businesses to use blockchain to store records and manage shareholders. HB126 doesn’t specifically reference token sales but would likely limit liability for companies wishing to develop decentralized governance protocols or distribute tokens. SF111 creates a property tax exemption for cryptocurrencies. All five bills have been signed into law by the governor.\n\nSee: https://www.ethnews.com/wyoming-legislature-goes-all-in-on-blockchain-cryptocurrency-bills\nhttps://www.forbes.com/sites/rachelwolfson/2018/03/13/u-s-state-of-wyoming-defines-cryptocurrency-utility-tokens-as-new-asset-class/2/#471f0edc6d45\nhttp://legisweb.state.wy.us/2018/billreference/BillReference.aspx?type=ALL\n\n**Arizona HB2601, 2602, 2603**\nThe Bills: Three bills in Arizona all introduced by Republican State Rep. Jeff Weninger are moving to make it easier on blockchain companies. HB2601 changes Arizona’s securities laws relating to virtual coin offerings, and creates exemptions for intrastate crowdfunding. HB2602 would prohibit any city, town or county for making rules against individuals running nodes on a blockchain. HB2603 preemptively allows companies to use blockchain for financial recording.\n\nDeep Dive: By my reading of the HB2601, it seems to state that “virtual coins,” presumably cryptocurrencies themselves are not necessarily securities. Virtual coin offerings, however, might be if they have been marketed and do not have utility within 90 days. Essentially, it makes the distinction between security tokens and utility tokens. HB2601 was reported do pass from the senate committee on finance on 3/14 and will need to pass rules committee, pass a third read on the senate floor and receive the governor’s signature.\n\nHB2602 doesn’t seem to prohibit the state legislature from making rules regarding running blockchain nodes, but prohibits local governments from doing so by labeling running a blockchain node a, “statewide concern.” On 3/15 this bill was voted do pass from the senate committee of the whole, which means it must still pass a vote of the full senate and be signed by the governor. The bill is not yet on the third read calendar.\n\nHB2603 has passed the house, and is waiting to pass third read on the senate floor and the governor’s signature.\n\nTake Away: Interestingly, in Arizona the partisan leaning of the issue is different than in Colorado. 8 House Democrats and one Senate Democrat voted no on HB2601. I imagine the argument has to do with local control and consumer protection, but that it’s largely a vote against a Republican Rep’s bill.\n\nSee: https://www.coindesk.com/arizonas-blockchain-node-rights-law-nearing-passage/\nhttps://www.ethnews.com/arizona-bill-aims-to-prevent-regulation-of-blockchain-nodes\nhttps://www.azleg.gov/press/house/53LEG/2R/180206WENINGERBLOCKCHAIN2.pdf\nhttp://arizonasonoranewsservice.com/arizona-to-regulate-cryptocurrency-offerings-crowdfunding-and-blockchains/",
"json_metadata": "{\"tags\":[\"blockchain\",\"statelaw\",\"cryptocurrency\",\"mining\",\"regulation\"],\"image\":[\"https://steemitimages.com/DQmdP66m1VqcDr8rbWFCk5Nx5J2uv9PEiSHzvtQjGreyMCg/uscrypto.jpg\"],\"links\":[\"http://leg.colorado.gov/bills/sb18-086\",\"https://cointelegraph.com/news/south-carolina-wants-to-ban-genesis-mining-over-unregistered-securities\",\"https://www.postandcourier.com/business/south-carolina-cracks-down-on-cryptocurrency-mining-investment-scheme/article_714e9e24-287a-11e8-b553-638ea33cc9c5.html\",\"https://www.ethnews.com/wyoming-legislature-goes-all-in-on-blockchain-cryptocurrency-bills\",\"https://www.forbes.com/sites/rachelwolfson/2018/03/13/u-s-state-of-wyoming-defines-cryptocurrency-utility-tokens-as-new-asset-class/2/#471f0edc6d45\",\"http://legisweb.state.wy.us/2018/billreference/BillReference.aspx?type=ALL\",\"https://www.coindesk.com/arizonas-blockchain-node-rights-law-nearing-passage/\",\"https://www.ethnews.com/arizona-bill-aims-to-prevent-regulation-of-blockchain-nodes\",\"https://www.azleg.gov/press/house/53LEG/2R/180206WENINGERBLOCKCHAIN2.pdf\",\"http://arizonasonoranewsservice.com/arizona-to-regulate-cryptocurrency-offerings-crowdfunding-and-blockchains/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}toribreceived 0.001 STEEM, 0.009 SBD, 0.008 SP author reward for @torib / the-two-dialects-of-blockchain2018/03/20 21:50:27
toribreceived 0.001 STEEM, 0.009 SBD, 0.008 SP author reward for @torib / the-two-dialects-of-blockchain
2018/03/20 21:50:27
| author | torib |
| permlink | the-two-dialects-of-blockchain |
| sbd payout | 0.009 SBD |
| steem payout | 0.001 STEEM |
| vesting payout | 12.245472 VESTS |
| Transaction Info | Block #20851850/Virtual Operation #7 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 20851850,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 7,
"timestamp": "2018-03-20T21:50:27",
"op": [
"author_reward",
{
"author": "torib",
"permlink": "the-two-dialects-of-blockchain",
"sbd_payout": "0.009 SBD",
"steem_payout": "0.001 STEEM",
"vesting_payout": "12.245472 VESTS"
}
]
}2018/03/20 08:26:57
2018/03/20 08:26:57
| parent author | torib |
| parent permlink | the-two-dialects-of-blockchain |
| author | stoneboy |
| permlink | re-torib-the-two-dialects-of-blockchain-20180320t082652708z |
| title | |
| body | Resteem bot Service! Boost Your Post. Send 0.100 SBD and your post url on memo and we will resteem your post on 5000+ followers from two different account.@stoneboy and @vimal-gautam. Delegate STEEM POWER [10SP Or Any Amount](https://steembottracker.com/delegation.html?delegatee=stoneboy) Through v2.steemconncet. |
| json metadata | {"tags":["bitcoin"],"users":["stoneboy","vimal-gautam"],"links":["https://steembottracker.com/delegation.html?delegatee=stoneboy"],"app":"steemit/0.1"} |
| Transaction Info | Block #20835809/Trx 9b2b3f81f20fdb9ee4556a666eea4601f9a23d7a |
View Raw JSON Data
{
"trx_id": "9b2b3f81f20fdb9ee4556a666eea4601f9a23d7a",
"block": 20835809,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-20T08:26:57",
"op": [
"comment",
{
"parent_author": "torib",
"parent_permlink": "the-two-dialects-of-blockchain",
"author": "stoneboy",
"permlink": "re-torib-the-two-dialects-of-blockchain-20180320t082652708z",
"title": "",
"body": "Resteem bot Service! Boost Your Post. Send 0.100 SBD and your post url on memo and we will resteem your post on 5000+ followers from two different account.@stoneboy and @vimal-gautam.\n\nDelegate STEEM POWER [10SP Or Any Amount](https://steembottracker.com/delegation.html?delegatee=stoneboy) Through v2.steemconncet.",
"json_metadata": "{\"tags\":[\"bitcoin\"],\"users\":[\"stoneboy\",\"vimal-gautam\"],\"links\":[\"https://steembottracker.com/delegation.html?delegatee=stoneboy\"],\"app\":\"steemit/0.1\"}"
}
]
}davy73upvoted (100.00%) @torib / the-two-dialects-of-blockchain2018/03/19 11:09:33
davy73upvoted (100.00%) @torib / the-two-dialects-of-blockchain
2018/03/19 11:09:33
| voter | davy73 |
| author | torib |
| permlink | the-two-dialects-of-blockchain |
| weight | 10000 (100.00%) |
| Transaction Info | Block #20810278/Trx 9d734d440b6fb2bb9baedb2a8bebf67cd54c4df5 |
View Raw JSON Data
{
"trx_id": "9d734d440b6fb2bb9baedb2a8bebf67cd54c4df5",
"block": 20810278,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-19T11:09:33",
"op": [
"vote",
{
"voter": "davy73",
"author": "torib",
"permlink": "the-two-dialects-of-blockchain",
"weight": 10000
}
]
}moefayeupvoted (100.00%) @torib / the-two-dialects-of-blockchain2018/03/19 07:45:06
moefayeupvoted (100.00%) @torib / the-two-dialects-of-blockchain
2018/03/19 07:45:06
| voter | moefaye |
| author | torib |
| permlink | the-two-dialects-of-blockchain |
| weight | 10000 (100.00%) |
| Transaction Info | Block #20806189/Trx 589a512aa969b46b7b135e140ba33324efb9d1d4 |
View Raw JSON Data
{
"trx_id": "589a512aa969b46b7b135e140ba33324efb9d1d4",
"block": 20806189,
"trx_in_block": 27,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-19T07:45:06",
"op": [
"vote",
{
"voter": "moefaye",
"author": "torib",
"permlink": "the-two-dialects-of-blockchain",
"weight": 10000
}
]
}goldajiupvoted (100.00%) @torib / the-two-dialects-of-blockchain2018/03/18 11:02:51
goldajiupvoted (100.00%) @torib / the-two-dialects-of-blockchain
2018/03/18 11:02:51
| voter | goldaji |
| author | torib |
| permlink | the-two-dialects-of-blockchain |
| weight | 10000 (100.00%) |
| Transaction Info | Block #20781346/Trx d7c7b744517d1310cf3875ab4947f71fff49a18f |
View Raw JSON Data
{
"trx_id": "d7c7b744517d1310cf3875ab4947f71fff49a18f",
"block": 20781346,
"trx_in_block": 34,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-18T11:02:51",
"op": [
"vote",
{
"voter": "goldaji",
"author": "torib",
"permlink": "the-two-dialects-of-blockchain",
"weight": 10000
}
]
}hrabiamaurycyupvoted (100.00%) @torib / the-two-dialects-of-blockchain2018/03/17 03:18:00
hrabiamaurycyupvoted (100.00%) @torib / the-two-dialects-of-blockchain
2018/03/17 03:18:00
| voter | hrabiamaurycy |
| author | torib |
| permlink | the-two-dialects-of-blockchain |
| weight | 10000 (100.00%) |
| Transaction Info | Block #20743261/Trx 3f31bfa28fe28f8acf944bcc050bc33285201171 |
View Raw JSON Data
{
"trx_id": "3f31bfa28fe28f8acf944bcc050bc33285201171",
"block": 20743261,
"trx_in_block": 27,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-17T03:18:00",
"op": [
"vote",
{
"voter": "hrabiamaurycy",
"author": "torib",
"permlink": "the-two-dialects-of-blockchain",
"weight": 10000
}
]
}mayuanbo1990upvoted (100.00%) @torib / the-two-dialects-of-blockchain2018/03/16 00:27:06
mayuanbo1990upvoted (100.00%) @torib / the-two-dialects-of-blockchain
2018/03/16 00:27:06
| voter | mayuanbo1990 |
| author | torib |
| permlink | the-two-dialects-of-blockchain |
| weight | 10000 (100.00%) |
| Transaction Info | Block #20711058/Trx 051e76157961878ad1e0c63654dc22f678ec2a69 |
View Raw JSON Data
{
"trx_id": "051e76157961878ad1e0c63654dc22f678ec2a69",
"block": 20711058,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-16T00:27:06",
"op": [
"vote",
{
"voter": "mayuanbo1990",
"author": "torib",
"permlink": "the-two-dialects-of-blockchain",
"weight": 10000
}
]
}tmesserupvoted (100.00%) @torib / the-two-dialects-of-blockchain2018/03/14 00:03:18
tmesserupvoted (100.00%) @torib / the-two-dialects-of-blockchain
2018/03/14 00:03:18
| voter | tmesser |
| author | torib |
| permlink | the-two-dialects-of-blockchain |
| weight | 10000 (100.00%) |
| Transaction Info | Block #20653088/Trx ddf5caedb233d4b033795d7680afffeff26a85cb |
View Raw JSON Data
{
"trx_id": "ddf5caedb233d4b033795d7680afffeff26a85cb",
"block": 20653088,
"trx_in_block": 29,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-14T00:03:18",
"op": [
"vote",
{
"voter": "tmesser",
"author": "torib",
"permlink": "the-two-dialects-of-blockchain",
"weight": 10000
}
]
}sensationupvoted (100.00%) @torib / the-two-dialects-of-blockchain2018/03/13 22:53:54
sensationupvoted (100.00%) @torib / the-two-dialects-of-blockchain
2018/03/13 22:53:54
| voter | sensation |
| author | torib |
| permlink | the-two-dialects-of-blockchain |
| weight | 10000 (100.00%) |
| Transaction Info | Block #20651700/Trx 6ee4022a69d9121dbc97f25df322f2b4584eb46d |
View Raw JSON Data
{
"trx_id": "6ee4022a69d9121dbc97f25df322f2b4584eb46d",
"block": 20651700,
"trx_in_block": 12,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-13T22:53:54",
"op": [
"vote",
{
"voter": "sensation",
"author": "torib",
"permlink": "the-two-dialects-of-blockchain",
"weight": 10000
}
]
}zeekayupvoted (100.00%) @torib / bitcoin-private-brand-new-btc-or-same-old-zcl2018/03/13 22:51:06
zeekayupvoted (100.00%) @torib / bitcoin-private-brand-new-btc-or-same-old-zcl
2018/03/13 22:51:06
| voter | zeekay |
| author | torib |
| permlink | bitcoin-private-brand-new-btc-or-same-old-zcl |
| weight | 10000 (100.00%) |
| Transaction Info | Block #20651644/Trx e0786f0823968ad56773484be112f63075436130 |
View Raw JSON Data
{
"trx_id": "e0786f0823968ad56773484be112f63075436130",
"block": 20651644,
"trx_in_block": 20,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-13T22:51:06",
"op": [
"vote",
{
"voter": "zeekay",
"author": "torib",
"permlink": "bitcoin-private-brand-new-btc-or-same-old-zcl",
"weight": 10000
}
]
}zeekayremoved vote from (0.00%) @torib / bitcoin-private-brand-new-btc-or-same-old-zcl2018/03/13 22:51:00
zeekayremoved vote from (0.00%) @torib / bitcoin-private-brand-new-btc-or-same-old-zcl
2018/03/13 22:51:00
| voter | zeekay |
| author | torib |
| permlink | bitcoin-private-brand-new-btc-or-same-old-zcl |
| weight | 0 (0.00%) |
| Transaction Info | Block #20651642/Trx 7c79e7264c6a4860cee6d2e92597f115b3909bfa |
View Raw JSON Data
{
"trx_id": "7c79e7264c6a4860cee6d2e92597f115b3909bfa",
"block": 20651642,
"trx_in_block": 68,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-13T22:51:00",
"op": [
"vote",
{
"voter": "zeekay",
"author": "torib",
"permlink": "bitcoin-private-brand-new-btc-or-same-old-zcl",
"weight": 0
}
]
}zeekayupvoted (100.00%) @torib / the-two-dialects-of-blockchain2018/03/13 22:50:45
zeekayupvoted (100.00%) @torib / the-two-dialects-of-blockchain
2018/03/13 22:50:45
| voter | zeekay |
| author | torib |
| permlink | the-two-dialects-of-blockchain |
| weight | 10000 (100.00%) |
| Transaction Info | Block #20651637/Trx 46c95c5b9764e9c777321b512d5928b2d028374f |
View Raw JSON Data
{
"trx_id": "46c95c5b9764e9c777321b512d5928b2d028374f",
"block": 20651637,
"trx_in_block": 22,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-13T22:50:45",
"op": [
"vote",
{
"voter": "zeekay",
"author": "torib",
"permlink": "the-two-dialects-of-blockchain",
"weight": 10000
}
]
}zeekayremoved vote from (0.00%) @torib / the-two-dialects-of-blockchain2018/03/13 22:50:39
zeekayremoved vote from (0.00%) @torib / the-two-dialects-of-blockchain
2018/03/13 22:50:39
| voter | zeekay |
| author | torib |
| permlink | the-two-dialects-of-blockchain |
| weight | 0 (0.00%) |
| Transaction Info | Block #20651635/Trx e60043e86bd43dd3c4f11b9788581049ce88e117 |
View Raw JSON Data
{
"trx_id": "e60043e86bd43dd3c4f11b9788581049ce88e117",
"block": 20651635,
"trx_in_block": 25,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-13T22:50:39",
"op": [
"vote",
{
"voter": "zeekay",
"author": "torib",
"permlink": "the-two-dialects-of-blockchain",
"weight": 0
}
]
}zeekayupvoted (100.00%) @torib / the-two-dialects-of-blockchain2018/03/13 22:29:24
zeekayupvoted (100.00%) @torib / the-two-dialects-of-blockchain
2018/03/13 22:29:24
| voter | zeekay |
| author | torib |
| permlink | the-two-dialects-of-blockchain |
| weight | 10000 (100.00%) |
| Transaction Info | Block #20651210/Trx b0ca6b4bd416475d3596f1d0436267b584347d4a |
View Raw JSON Data
{
"trx_id": "b0ca6b4bd416475d3596f1d0436267b584347d4a",
"block": 20651210,
"trx_in_block": 17,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-13T22:29:24",
"op": [
"vote",
{
"voter": "zeekay",
"author": "torib",
"permlink": "the-two-dialects-of-blockchain",
"weight": 10000
}
]
}trsteemitupvoted (100.00%) @torib / the-two-dialects-of-blockchain2018/03/13 22:15:33
trsteemitupvoted (100.00%) @torib / the-two-dialects-of-blockchain
2018/03/13 22:15:33
| voter | trsteemit |
| author | torib |
| permlink | the-two-dialects-of-blockchain |
| weight | 10000 (100.00%) |
| Transaction Info | Block #20650933/Trx 5f7bff989ece500b9577ca38352fe6cc6f95c4df |
View Raw JSON Data
{
"trx_id": "5f7bff989ece500b9577ca38352fe6cc6f95c4df",
"block": 20650933,
"trx_in_block": 11,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-13T22:15:33",
"op": [
"vote",
{
"voter": "trsteemit",
"author": "torib",
"permlink": "the-two-dialects-of-blockchain",
"weight": 10000
}
]
}2018/03/13 21:57:00
2018/03/13 21:57:00
| parent author | torib |
| parent permlink | the-two-dialects-of-blockchain |
| author | ipostbtcprice |
| permlink | re-the-two-dialects-of-blockchain-20180313t215659 |
| title | |
| body | For future viewers: price of bitcoin at the moment of posting is 9090.10USD |
| json metadata | |
| Transaction Info | Block #20650562/Trx e3f47c05c23cdf15eb746c0d354da49769895bb3 |
View Raw JSON Data
{
"trx_id": "e3f47c05c23cdf15eb746c0d354da49769895bb3",
"block": 20650562,
"trx_in_block": 49,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-13T21:57:00",
"op": [
"comment",
{
"parent_author": "torib",
"parent_permlink": "the-two-dialects-of-blockchain",
"author": "ipostbtcprice",
"permlink": "re-the-two-dialects-of-blockchain-20180313t215659",
"title": "",
"body": "For future viewers: price of bitcoin at the moment of posting is 9090.10USD",
"json_metadata": ""
}
]
}coin.infoupvoted (6.94%) @torib / the-two-dialects-of-blockchain2018/03/13 21:56:36
coin.infoupvoted (6.94%) @torib / the-two-dialects-of-blockchain
2018/03/13 21:56:36
| voter | coin.info |
| author | torib |
| permlink | the-two-dialects-of-blockchain |
| weight | 694 (6.94%) |
| Transaction Info | Block #20650554/Trx 8c169003465f370237cf7445d8146f863cad80a4 |
View Raw JSON Data
{
"trx_id": "8c169003465f370237cf7445d8146f863cad80a4",
"block": 20650554,
"trx_in_block": 48,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-13T21:56:36",
"op": [
"vote",
{
"voter": "coin.info",
"author": "torib",
"permlink": "the-two-dialects-of-blockchain",
"weight": 694
}
]
}2018/03/13 21:56:33
2018/03/13 21:56:33
| parent author | torib |
| parent permlink | the-two-dialects-of-blockchain |
| author | coin.info |
| permlink | re-torib-the-two-dialects-of-blockchain-20180313t215631042z |
| title | |
| body | **Coins mentioned in post:** Coin | | Price (USD) | 📉 24h | 📉 7d - | - | - | - | - **BTC** | Bitcoin | 9142.760$ | _0.24%_ | _-15.76%_ **DNA** | EncrypGen | 0.287$ | _-5.68%_ | _-7.26%_ **DRGN** | Dragonchain | 1.043$ | _-3.04%_ | _-27.94%_ **ETH** | Ethereum | 686.671$ | _-1.02%_ | _-16.32%_ **XLM** | Stellar | 0.286$ | _-1.91%_ | _-16.63%_ |
| json metadata | {"app":"coininfo/1.0.0","format":"markdown"} |
| Transaction Info | Block #20650553/Trx 8784b923aa0bfa591a201ce9938af9684a7689d9 |
View Raw JSON Data
{
"trx_id": "8784b923aa0bfa591a201ce9938af9684a7689d9",
"block": 20650553,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-13T21:56:33",
"op": [
"comment",
{
"parent_author": "torib",
"parent_permlink": "the-two-dialects-of-blockchain",
"author": "coin.info",
"permlink": "re-torib-the-two-dialects-of-blockchain-20180313t215631042z",
"title": "",
"body": "**Coins mentioned in post:**\n\nCoin | | Price (USD) | 📉 24h | 📉 7d\n- | - | - | - | -\n**BTC** | Bitcoin | 9142.760$ | _0.24%_ | _-15.76%_\n**DNA** | EncrypGen | 0.287$ | _-5.68%_ | _-7.26%_\n**DRGN** | Dragonchain | 1.043$ | _-3.04%_ | _-27.94%_\n**ETH** | Ethereum | 686.671$ | _-1.02%_ | _-16.32%_\n**XLM** | Stellar | 0.286$ | _-1.91%_ | _-16.63%_",
"json_metadata": "{\"app\":\"coininfo/1.0.0\",\"format\":\"markdown\"}"
}
]
}toribpublished a new post: the-two-dialects-of-blockchain2018/03/13 21:50:27
toribpublished a new post: the-two-dialects-of-blockchain
2018/03/13 21:50:27
| parent author | |
| parent permlink | bitcoin |
| author | torib |
| permlink | the-two-dialects-of-blockchain |
| title | The Two Dialects of Blockchain |
| body | **A functional guide for discussing and evaluating blockchains**  Part of why the discussion around emerging blockchain companies is so fraught with conflict is that the definition of “blockchain” and the ideas behind it are still somewhat murky. This realization came after hours of arguing with my team about whether or not certain projects could claim to be “a blockchain,” or if that title was misleading or dishonest. Over the course of that discussion it became clear that we were not all talking about the same thing. The engineers in the group saw blockchain as strictly a data structure, and not all of the things that blockchain enables. The well-versed but non-technical members of the team insisted that the technology doesn’t exist in a vacuum and we can’t remove the expected, if not altogether technically necessary implications. This conversation makes it clear that we don’t have a common language we can use when talking about new blockchain projects. In this post I try to get at the nuance that so many definitions miss. *The following is a proposed framework for a critical discussion on new blockchains or blockchain projects. Through this critical lens we can differentiate between the two meanings we ascribe to blockchain, and evaluate the qualities of each.* **The Gene** The Bitcoin white paper first describes a “chain of blocks,” and how that data is strung together, but it also describes the method by which that data is received, verified and written. Since then those two separate components have been conflated and the word blockchain used to describe both. This practice is similar to the way we use the word “gene.” Gene refers to our genetic makeup, the DNA coding that determines our traits. However, we also use “genes” colloquially to describe those traits and how we came to possess them. Likewise, “blockchain” describes both the data structure like the DNA, as well as the network that leads to the data being written like the genes. *I propose that we reserve the question of “blockchain or not,” for the data structure and break down the components of the “blockchain network,” individually.*  **Technical DNA** Blockchain is a data structure, or a particular method of storing information. It consists of a growing chain of transactions with each new ‘block,’ a finite grouping of transactions, referencing the previous block by way of a cryptographic hash. The blockchain is a ledger of transactions, each cryptographically signed ensuring simple validation of the entire history and preventing tampering. As the technology evolves the word “blockchain,” is being applied to structures that are not exclusively a chain of blocks, but is now is used to refer to other structures that store collections of transactions. **Network Genes** When we discuss blockchain as a network, the most common traits are those originally described in the Bitcoin white paper. In order to enable peer-to-peer transactions the Bitcoin white paper describes a network of nodes, each with a complete copy of the ledger, recording and arriving at consensus on each new block of transactions. The variables we use when evaluating blockchain networks are; distribution, openness, decentralization, and trustlessness. These traits are distinctive, but linked, each impacting the value of the others. The lowest hurdle for evaluating a blockchain is the question of whether or not it is distributed. Distributed means that an entire copy of the ledger is held on each node and that there is more than one node in the network. There are varying measures as to what degree a network is distributed — how many nodes are present, are the nodes related to one another, and how geographically dispersed the nodes are. The more a ledger is distributed, the more difficult it becomes for bad actors to corrupt the network. From there the remaining variables can be examined by separating blockchain networks into two buckets, permissioned and open. **Permissioned** Permissioned blockchains are also called closed or private. Though they are typically distributed, the nodes that contribute to the blockchain are controlled by the organization that implemented or manages that blockchain. Permissioned blockchains are, what I will refer to as, quasi-decentralized, though they do not necessarily need to be. If the system uses some kind of consensus protocol and each of the distributed nodes has equal authority then the system appears decentralized. However, because the nodes are all granted authority by a central party, they cannot be truly decentralized in the way that open blockchains are. Consensus here is technically decentralized, but is the privilege of only the chosen validators. By staying in this decentralized middle-ground they are not as vulnerable to bad actors adding nodes to their network and causing harm, on the other hand, limiting the number of nodes puts increased value on the input of each making the network vulnerable. Along that vein, permissioned blockchains are not “trustless,” in the way we expect open blockchains to be because there is an inherent requirement that members of the network trust the system gatekeeper. In the case of internal company blockchains for instance, this isn’t a problem because the company has no incentive to lie to itself and trustlessness isn’t a priority. Private or permissioned blockchains are gaining popularity as easy to use, more secure systems. Products such as BigchainDB, Hyperledger, Stellar and Dragonchain are all examples of permissioned blockchain based tools. When evaluating permissioned blockchains it is useful to begin with several questions. By whom or by what method are permissioned nodes chosen? How many permissioned nodes exist in the network? To what degree are those permissioned nodes related? Are there economic incentives to prevent adversarial model, collusion etc.? These answers will lead to an understanding of to what degree the blockchain in question is distributed and quasi-decentralized.  **Open** Open blockchains operate similarly, but permission isn’t necessary to become a node. This means that open blockchains are truly decentralized, because even if there was an authority that originally launched the project, the community has the authority to accept or reject transactions or changes. The argument could be made that some open blockchains are more neutral than others, depending on the composition of the network. Blockchains operating with fewer nodes can be considered less decentralized because the number of bad actor nodes required to overtake the system is smaller than blockchains operating with many, well-dispersed, unrelated nodes. That said, typically open blockchains are difficult to overtake in a way that would be economically feasible for the taker. With open blockchains users are not required to submit to a central authority deciding the validity of any transaction. Instead the network is structured such that each member is incentivised to behave within the rules and contribute to its continued existence. This means that open blockchains, with proper incentives and adoption, can enable trustlessness and peer-to-peer transactions. The principle of trustlessness was core to the Bitcoin whitepaper and the two are squarely linked in the wider social discussion of blockchain. Bitcoin, Ethereum and most other well-known, frequently-discussed blockchains are open. When evaluating open blockchains it is useful to begin with several questions. How many nodes are operating on the network? How dispersed are those nodes? What qualifications does one have to meet to become a node? What is the barrier of entry to becoming a node; technological, economic or otherwise? Does any central authority have to approve new nodes? **How To Speak Blockchain** As we use the word now, Blockchain means everything and nothing at all. This leads to confused clients, unclear project descriptions and, in extreme cases, SEC subpoenas. Here I have established the beginnings of a critical framework for discussing the merits of a blockchain project. As with any innovative technology these variables will change over time, but having a standard rubric to guide the discussion of blockchain projects is valuable. Having a common language allows us to examine projects critically in a productive way. Going forward I will be using this archetype in my critical analysis of projects, and will continue to refine it based on changes to the landscape. If you have suggestions, comments or anything you’d like to add — drop it in the comments below, contact me on twitter @benson4america or by email at [email protected] |
| json metadata | {"tags":["bitcoin","decentralization","blockchain","crypto","ico"],"users":["benson4america"],"image":["https://steemitimages.com/DQmUYeVyo6fsFWoaSyinvGYTKVQGuAhEfsXiVDRBe3oC5s8/blockchain.jpg","https://steemitimages.com/DQmexFBJfQCtv5XtucYasH15NB782AgyzenRaZfDD3QqqV5/cool-dna.jpg","https://steemitimages.com/DQme4PZQQWWBRvnazhi96f3x58esvqZo7dHmzNjSMi3V7C6/network.jpg"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #20650431/Trx fe944b47468876c25fdee459c4fb4e148ccd4962 |
View Raw JSON Data
{
"trx_id": "fe944b47468876c25fdee459c4fb4e148ccd4962",
"block": 20650431,
"trx_in_block": 67,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-13T21:50:27",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "bitcoin",
"author": "torib",
"permlink": "the-two-dialects-of-blockchain",
"title": "The Two Dialects of Blockchain",
"body": "**A functional guide for discussing and evaluating blockchains**\n\n\n\nPart of why the discussion around emerging blockchain companies is so fraught with conflict is that the definition of “blockchain” and the ideas behind it are still somewhat murky. This realization came after hours of arguing with my team about whether or not certain projects could claim to be “a blockchain,” or if that title was misleading or dishonest. Over the course of that discussion it became clear that we were not all talking about the same thing. The engineers in the group saw blockchain as strictly a data structure, and not all of the things that blockchain enables. The well-versed but non-technical members of the team insisted that the technology doesn’t exist in a vacuum and we can’t remove the expected, if not altogether technically necessary implications. This conversation makes it clear that we don’t have a common language we can use when talking about new blockchain projects. In this post I try to get at the nuance that so many definitions miss. *The following is a proposed framework for a critical discussion on new blockchains or blockchain projects. Through this critical lens we can differentiate between the two meanings we ascribe to blockchain, and evaluate the qualities of each.*\n\n**The Gene**\n\nThe Bitcoin white paper first describes a “chain of blocks,” and how that data is strung together, but it also describes the method by which that data is received, verified and written. Since then those two separate components have been conflated and the word blockchain used to describe both. This practice is similar to the way we use the word “gene.” Gene refers to our genetic makeup, the DNA coding that determines our traits. However, we also use “genes” colloquially to describe those traits and how we came to possess them. Likewise, “blockchain” describes both the data structure like the DNA, as well as the network that leads to the data being written like the genes. *I propose that we reserve the question of “blockchain or not,” for the data structure and break down the components of the “blockchain network,” individually.*\n\n\n\n**Technical DNA**\n\nBlockchain is a data structure, or a particular method of storing information. It consists of a growing chain of transactions with each new ‘block,’ a finite grouping of transactions, referencing the previous block by way of a cryptographic hash. The blockchain is a ledger of transactions, each cryptographically signed ensuring simple validation of the entire history and preventing tampering. As the technology evolves the word “blockchain,” is being applied to structures that are not exclusively a chain of blocks, but is now is used to refer to other structures that store collections of transactions.\n\n**Network Genes**\n\nWhen we discuss blockchain as a network, the most common traits are those originally described in the Bitcoin white paper. In order to enable peer-to-peer transactions the Bitcoin white paper describes a network of nodes, each with a complete copy of the ledger, recording and arriving at consensus on each new block of transactions. The variables we use when evaluating blockchain networks are; distribution, openness, decentralization, and trustlessness. These traits are distinctive, but linked, each impacting the value of the others.\n\nThe lowest hurdle for evaluating a blockchain is the question of whether or not it is distributed. Distributed means that an entire copy of the ledger is held on each node and that there is more than one node in the network. There are varying measures as to what degree a network is distributed — how many nodes are present, are the nodes related to one another, and how geographically dispersed the nodes are. The more a ledger is distributed, the more difficult it becomes for bad actors to corrupt the network. From there the remaining variables can be examined by separating blockchain networks into two buckets, permissioned and open.\n\n**Permissioned**\n\nPermissioned blockchains are also called closed or private. Though they are typically distributed, the nodes that contribute to the blockchain are controlled by the organization that implemented or manages that blockchain. Permissioned blockchains are, what I will refer to as, quasi-decentralized, though they do not necessarily need to be. If the system uses some kind of consensus protocol and each of the distributed nodes has equal authority then the system appears decentralized. However, because the nodes are all granted authority by a central party, they cannot be truly decentralized in the way that open blockchains are. Consensus here is technically decentralized, but is the privilege of only the chosen validators. By staying in this decentralized middle-ground they are not as vulnerable to bad actors adding nodes to their network and causing harm, on the other hand, limiting the number of nodes puts increased value on the input of each making the network vulnerable.\n\nAlong that vein, permissioned blockchains are not “trustless,” in the way we expect open blockchains to be because there is an inherent requirement that members of the network trust the system gatekeeper. In the case of internal company blockchains for instance, this isn’t a problem because the company has no incentive to lie to itself and trustlessness isn’t a priority. Private or permissioned blockchains are gaining popularity as easy to use, more secure systems. Products such as BigchainDB, Hyperledger, Stellar and Dragonchain are all examples of permissioned blockchain based tools.\n\nWhen evaluating permissioned blockchains it is useful to begin with several questions. By whom or by what method are permissioned nodes chosen? How many permissioned nodes exist in the network? To what degree are those permissioned nodes related? Are there economic incentives to prevent adversarial model, collusion etc.? These answers will lead to an understanding of to what degree the blockchain in question is distributed and quasi-decentralized.\n\n\n\n**Open**\n\nOpen blockchains operate similarly, but permission isn’t necessary to become a node. This means that open blockchains are truly decentralized, because even if there was an authority that originally launched the project, the community has the authority to accept or reject transactions or changes. The argument could be made that some open blockchains are more neutral than others, depending on the composition of the network. Blockchains operating with fewer nodes can be considered less decentralized because the number of bad actor nodes required to overtake the system is smaller than blockchains operating with many, well-dispersed, unrelated nodes. That said, typically open blockchains are difficult to overtake in a way that would be economically feasible for the taker. With open blockchains users are not required to submit to a central authority deciding the validity of any transaction. Instead the network is structured such that each member is incentivised to behave within the rules and contribute to its continued existence. This means that open blockchains, with proper incentives and adoption, can enable trustlessness and peer-to-peer transactions. The principle of trustlessness was core to the Bitcoin whitepaper and the two are squarely linked in the wider social discussion of blockchain. Bitcoin, Ethereum and most other well-known, frequently-discussed blockchains are open.\n\nWhen evaluating open blockchains it is useful to begin with several questions. How many nodes are operating on the network? How dispersed are those nodes? What qualifications does one have to meet to become a node? What is the barrier of entry to becoming a node; technological, economic or otherwise? Does any central authority have to approve new nodes?\n\n**How To Speak Blockchain**\n\nAs we use the word now, Blockchain means everything and nothing at all. This leads to confused clients, unclear project descriptions and, in extreme cases, SEC subpoenas. Here I have established the beginnings of a critical framework for discussing the merits of a blockchain project. As with any innovative technology these variables will change over time, but having a standard rubric to guide the discussion of blockchain projects is valuable. Having a common language allows us to examine projects critically in a productive way. Going forward I will be using this archetype in my critical analysis of projects, and will continue to refine it based on changes to the landscape.\n\nIf you have suggestions, comments or anything you’d like to add — drop it in the comments below, contact me on twitter @benson4america or by email at [email protected]",
"json_metadata": "{\"tags\":[\"bitcoin\",\"decentralization\",\"blockchain\",\"crypto\",\"ico\"],\"users\":[\"benson4america\"],\"image\":[\"https://steemitimages.com/DQmUYeVyo6fsFWoaSyinvGYTKVQGuAhEfsXiVDRBe3oC5s8/blockchain.jpg\",\"https://steemitimages.com/DQmexFBJfQCtv5XtucYasH15NB782AgyzenRaZfDD3QqqV5/cool-dna.jpg\",\"https://steemitimages.com/DQme4PZQQWWBRvnazhi96f3x58esvqZo7dHmzNjSMi3V7C6/network.jpg\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}2018/02/27 10:47:15
2018/02/27 10:47:15
| parent author | torib |
| parent permlink | bitcoin-private-brand-new-btc-or-same-old-zcl |
| author | steem-network |
| permlink | re-bitcoin-private-brand-new-btc-or-same-old-zcl-20180227t104714 |
| title | |
| body | <html> <p>Congratulations <a href="/@torib" target="_blank">@torib</a>, you have decided to take the next big step with your first post! The Steem Network Team wishes you a great time among this awesome community.</p> <hr> <div class="pull-left"><img src="https://steemitimages.com/DQmaAdLUJ3yaSkmcmWECWyPGPWcjfbCoZ8Tu4RM6H4DbjCi/steem-network-thumbs-up.gif" alt="Thumbs up for Steem Network´s strategy" title="I suggest Steem Network´s strategy" width="320" height="222"></div> <h1>The proven road to boost your personal success in this amazing Steem Network</h1> <p>Do you already know that awesome content will get great profits by following these <a href="/steem-network/@steem-network/spread-your-posts-through-this-proven-strategy-and-get-great-profits-in-return--for-posts-created-at-2018-02-26" target="_blank" alt="Steem Network" title="Follow Steem Network´s suggestions to boost your success">simple steps</a>, that have been worked out by experts?</p> </html> |
| json metadata | {"tags": ["steem-network"], "users": ["steem-network", "torib"], "image": ["https://steemitimages.com/DQmaAdLUJ3yaSkmcmWECWyPGPWcjfbCoZ8Tu4RM6H4DbjCi/steem-network-thumbs-up.gif"], "links": ["/@torib", "/steem-network/@steem-network/spread-your-posts-through-this-proven-strategy-and-get-great-profits-in-return--for-posts-created-at-2018-02-26"], "community": "steem-network", "app": "steem-network/1.0.1", "format": "html"} |
| Transaction Info | Block #20234386/Trx efd8d62f83291f16cd7b85b0f15497bb67d8939f |
View Raw JSON Data
{
"trx_id": "efd8d62f83291f16cd7b85b0f15497bb67d8939f",
"block": 20234386,
"trx_in_block": 35,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-27T10:47:15",
"op": [
"comment",
{
"parent_author": "torib",
"parent_permlink": "bitcoin-private-brand-new-btc-or-same-old-zcl",
"author": "steem-network",
"permlink": "re-bitcoin-private-brand-new-btc-or-same-old-zcl-20180227t104714",
"title": "",
"body": "<html>\n<p>Congratulations <a href=\"/@torib\" target=\"_blank\">@torib</a>, you have decided to take the next big step with your first post! The Steem Network Team wishes you a great time among this awesome community.</p>\n<hr>\n<div class=\"pull-left\"><img src=\"https://steemitimages.com/DQmaAdLUJ3yaSkmcmWECWyPGPWcjfbCoZ8Tu4RM6H4DbjCi/steem-network-thumbs-up.gif\" alt=\"Thumbs up for Steem Network´s strategy\" title=\"I suggest Steem Network´s strategy\" width=\"320\" height=\"222\"></div>\n<h1>The proven road to boost your personal success in this amazing Steem Network</h1>\n<p>Do you already know that awesome content will get great profits by following these <a href=\"/steem-network/@steem-network/spread-your-posts-through-this-proven-strategy-and-get-great-profits-in-return--for-posts-created-at-2018-02-26\" target=\"_blank\" alt=\"Steem Network\" title=\"Follow Steem Network´s suggestions to boost your success\">simple steps</a>, that have been worked out by experts?</p>\n</html>",
"json_metadata": "{\"tags\": [\"steem-network\"], \"users\": [\"steem-network\", \"torib\"], \"image\": [\"https://steemitimages.com/DQmaAdLUJ3yaSkmcmWECWyPGPWcjfbCoZ8Tu4RM6H4DbjCi/steem-network-thumbs-up.gif\"], \"links\": [\"/@torib\", \"/steem-network/@steem-network/spread-your-posts-through-this-proven-strategy-and-get-great-profits-in-return--for-posts-created-at-2018-02-26\"], \"community\": \"steem-network\", \"app\": \"steem-network/1.0.1\", \"format\": \"html\"}"
}
]
}posyuntatupvoted (100.00%) @torib / bitcoin-private-brand-new-btc-or-same-old-zcl2018/02/27 09:09:51
posyuntatupvoted (100.00%) @torib / bitcoin-private-brand-new-btc-or-same-old-zcl
2018/02/27 09:09:51
| voter | posyuntat |
| author | torib |
| permlink | bitcoin-private-brand-new-btc-or-same-old-zcl |
| weight | 10000 (100.00%) |
| Transaction Info | Block #20232438/Trx b6ce3839d14e18582687da116116ce380dd6c16e |
View Raw JSON Data
{
"trx_id": "b6ce3839d14e18582687da116116ce380dd6c16e",
"block": 20232438,
"trx_in_block": 45,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-27T09:09:51",
"op": [
"vote",
{
"voter": "posyuntat",
"author": "torib",
"permlink": "bitcoin-private-brand-new-btc-or-same-old-zcl",
"weight": 10000
}
]
}anomalyupvoted (1.00%) @torib / bitcoin-private-brand-new-btc-or-same-old-zcl2018/02/26 23:00:24
anomalyupvoted (1.00%) @torib / bitcoin-private-brand-new-btc-or-same-old-zcl
2018/02/26 23:00:24
| voter | anomaly |
| author | torib |
| permlink | bitcoin-private-brand-new-btc-or-same-old-zcl |
| weight | 100 (1.00%) |
| Transaction Info | Block #20220406/Trx d088fc771c9a1b46710c7ff9c8e4162bfe16ad83 |
View Raw JSON Data
{
"trx_id": "d088fc771c9a1b46710c7ff9c8e4162bfe16ad83",
"block": 20220406,
"trx_in_block": 57,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-26T23:00:24",
"op": [
"vote",
{
"voter": "anomaly",
"author": "torib",
"permlink": "bitcoin-private-brand-new-btc-or-same-old-zcl",
"weight": 100
}
]
}toribpublished a new post: bitcoin-private-brand-new-btc-or-same-old-zcl2018/02/26 22:52:06
toribpublished a new post: bitcoin-private-brand-new-btc-or-same-old-zcl
2018/02/26 22:52:06
| parent author | |
| parent permlink | bitcoinprivate |
| author | torib |
| permlink | bitcoin-private-brand-new-btc-or-same-old-zcl |
| title | Bitcoin Private: Brand New BTC or Same Old ZCL? |
| body | @@ -7718,17 +7718,17 @@ roject a -t +s promise |
| json metadata | {"tags":["bitcoinprivate","btcp","zcl","btc"],"image":["https://steemitimages.com/DQmNedTyaUrw2zEdDyaME4fuq9mqMnrisCYtbTogT4U5HNJ/Screen%20Shot%202018-02-26%20at%203.42.54%20PM.png","https://steemitimages.com/DQmPhch2g2EZ282cRE8gurTZFYEYM2kyN5iqBLaT5tZy6ye/Screen%20Shot%202018-02-26%20at%203.47.50%20PM.png","https://steemitimages.com/DQmRH9GzaA86QqzLaGQYDkQvS5fKjoS4hcQQaJudPZLpFSn/hard-fork-graphic.png","https://steemitimages.com/DQmTiaCAUPfXP9T17M5WLJvpMEcAdaY8wgAjJwmTJqir5NW/Screen%20Shot%202018-02-26%20at%203.40.49%20PM.png"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #20220240/Trx f7bc632b9e7008d91763bdf97bbd771af1a0e92d |
View Raw JSON Data
{
"trx_id": "f7bc632b9e7008d91763bdf97bbd771af1a0e92d",
"block": 20220240,
"trx_in_block": 14,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-26T22:52:06",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "bitcoinprivate",
"author": "torib",
"permlink": "bitcoin-private-brand-new-btc-or-same-old-zcl",
"title": "Bitcoin Private: Brand New BTC or Same Old ZCL?",
"body": "@@ -7718,17 +7718,17 @@\n roject a\n-t\n+s\n promise\n",
"json_metadata": "{\"tags\":[\"bitcoinprivate\",\"btcp\",\"zcl\",\"btc\"],\"image\":[\"https://steemitimages.com/DQmNedTyaUrw2zEdDyaME4fuq9mqMnrisCYtbTogT4U5HNJ/Screen%20Shot%202018-02-26%20at%203.42.54%20PM.png\",\"https://steemitimages.com/DQmPhch2g2EZ282cRE8gurTZFYEYM2kyN5iqBLaT5tZy6ye/Screen%20Shot%202018-02-26%20at%203.47.50%20PM.png\",\"https://steemitimages.com/DQmRH9GzaA86QqzLaGQYDkQvS5fKjoS4hcQQaJudPZLpFSn/hard-fork-graphic.png\",\"https://steemitimages.com/DQmTiaCAUPfXP9T17M5WLJvpMEcAdaY8wgAjJwmTJqir5NW/Screen%20Shot%202018-02-26%20at%203.40.49%20PM.png\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}zeekayupvoted (100.00%) @torib / bitcoin-private-brand-new-btc-or-same-old-zcl2018/02/26 22:38:54
zeekayupvoted (100.00%) @torib / bitcoin-private-brand-new-btc-or-same-old-zcl
2018/02/26 22:38:54
| voter | zeekay |
| author | torib |
| permlink | bitcoin-private-brand-new-btc-or-same-old-zcl |
| weight | 10000 (100.00%) |
| Transaction Info | Block #20219976/Trx a68742460623f180352a015b7d6897df1b9a74e2 |
View Raw JSON Data
{
"trx_id": "a68742460623f180352a015b7d6897df1b9a74e2",
"block": 20219976,
"trx_in_block": 10,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-26T22:38:54",
"op": [
"vote",
{
"voter": "zeekay",
"author": "torib",
"permlink": "bitcoin-private-brand-new-btc-or-same-old-zcl",
"weight": 10000
}
]
}devilianoupvoted (100.00%) @torib / bitcoin-private-brand-new-btc-or-same-old-zcl2018/02/26 22:29:42
devilianoupvoted (100.00%) @torib / bitcoin-private-brand-new-btc-or-same-old-zcl
2018/02/26 22:29:42
| voter | deviliano |
| author | torib |
| permlink | bitcoin-private-brand-new-btc-or-same-old-zcl |
| weight | 10000 (100.00%) |
| Transaction Info | Block #20219792/Trx 747da426554310b9eac54fe41a4194aeae2c5d06 |
View Raw JSON Data
{
"trx_id": "747da426554310b9eac54fe41a4194aeae2c5d06",
"block": 20219792,
"trx_in_block": 26,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-26T22:29:42",
"op": [
"vote",
{
"voter": "deviliano",
"author": "torib",
"permlink": "bitcoin-private-brand-new-btc-or-same-old-zcl",
"weight": 10000
}
]
}toribpublished a new post: bitcoin-private-brand-new-btc-or-same-old-zcl2018/02/26 22:28:21
toribpublished a new post: bitcoin-private-brand-new-btc-or-same-old-zcl
2018/02/26 22:28:21
| parent author | |
| parent permlink | bitcoinprivate |
| author | torib |
| permlink | bitcoin-private-brand-new-btc-or-same-old-zcl |
| title | Bitcoin Private: Brand New BTC or Same Old ZCL? |
| body |  ## TL;DR the BTCP White Paper The crypto community is waiting with bated breath, anxiously refreshing Bittrex on twitter, harassing Rhett Creighton any way they can, for news on the upcoming hard fork of BTC and ZCL — Bitcoin Private. The team behind BTCP is striving to create a new currency that is faster, better aligned and, as the name implies, private.  The BTCP white paper focuses primarily on the shortcomings of other significant blockchains and how BTCP improves on those issues. BTCP features a larger 2MB fixed block size compared to Bitcoin’s 1MB, and a 2.5 minute block time compared to BTC’s 10 minute time. These features are the same as Zcash and Zclassic. BTCP uses Equihash, the premier ASIC resistant proof-of-work algorithm. The snapshot, or the exact time when you must hold BTC or ZCL in order to receive BTCP in the fork, will happen at 5pm UTC on February 28, 2018. Currently BTCP has exchange support on Trade Satoshi but Bittrex is expected to announce support at some point. The Bitcoin Private team is is calling the fork a “fork-merge,” because everyone holding 1 Zclassic or 1 Bitcoin at the time of the snapshot will receive 1 BTCP. This is a unique method, combining the UTXOs (unspent transaction outputs, in this case any BTC or ZCL that is held), but actual blockchain being forked is Zclassic. The total supply of BTCP is 21 million, and at the time of the fork almost 20.4 million of those will already exist from the initial distribution. The BTCP team claims this will make them the “*least inflationary coin ever produced,*” according to their white paper.  For miners, the team took lessons from both Zcash and Zclassic. BTCP has no “founder tax,” an unpopular feature of Zcash, but does include a system to incentivize developers, which was neglected in Zclassic. They facilitated this by creating a “voluntary miner pool,” which would reward Zclassic miners for contributing to a fund by offering them a >1:1 proportion of BTCP to their ZCL contribution after the fork. The reward for mining at the first block will be 0.7815 BTCP. After about 66,000 blocks the reward will be cut in half, and will continue halving every 840,000 blocks. The claim to increasing privacy comes from the implementation of a zero-knowledge proof algorithm called zk-SNARKs. Transactions can be either transparent, visible on the blockchain, or shielded, where they verifiable but not able to be tracked by outside parties. ## BTCP — Third Time’s a Charm? Practically, and when considered in a vacuum, Bitcoin Private is solid. The white paper is well considered and well reasoned and addresses some major and important problems in the cryptocurrency space. However, when compared with its true predecessors, Zcash and Zclassic, **Bitcoin Private not much more than a small shift and better branding.** Zcash was a fork of Bitcoin that made some important improvements, such as the inclusion of Equihash, which without going into too much detail, improves the strength of the claim of decentralization. Zcash also included what is effectively the cornerstone of Bitcoin Private, the application of zk-SKARKs. Zcash faced criticism over the exorbitant founders tax on all mining, which led to an almost comically fast fork into Zclassic, which was technologically similar to Zcash but excluded the founders tax, which had the unintended consequence of neglecting developer incentives. Bitcoin Private is effectively the same as Zclassic but attempts to fix some of the developer incentive issues, by creating a pre-fork, voluntary donation pool. The white paper tends to obscure the similarity to Zclassic and Zcash by comparing BTCP to Bitcoin, Bitcoin Cash and Bitcoin Gold (See table on page 3 for example). I like to believe that this focus was intended to emphasize the improvements that BTCP makes over these other Bitcoin forks, but it also speaks to a larger trend in the space. For such a promising technology like blockchain there is an incredible amount of snake oil being sold. At this point so early in the exploration of the space, maybe that’s fine. **But eventually, supporters will get smart enough to know that we aren’t really adding value.** And, frankly, if your white paper needs to be a little shady that doesn’t bode well for your ability to execute.  Bitcoin Private claims to be focused on their community in a way that Zcash and Zclassic didn’t pull off well. Zcash was a sincerely novel project in a lot of ways, so we can assume that they thought they would need the money from the pre-mine and the 20% founders tax. Zclassic reversed those, but didn’t make any moves to actively reward developers so they lagged on improvements. Bitcoin Private’s actual largest change was in the way they looked to solve these problems, but it is unclear whether or not they hit the mark. Their community focus includes a treasury fund to incentivize developers and a community developer program. The treasury fund is governed by primarily by the Bitcoin Private team, hardly and arms-length transaction, and has no stated plans to transfer that management to the community. The developer program as described is open to anyone but requires a successful application to the program and so is still tightly controlled. This isn’t to say the approach won’t be effective, but that the amount of input allowed from the community may be overstated. The structure of the BTCP block reward is a risk that will ultimately depend on the value of the coin. This is true of every coin, of course, but by starting with such a small reward, if the price drops immediately after the fork, miners could lose confidence and stop mining. Inevitably some miners will stay because the difficulty is adjusted based on the number of miners, but having only a small number of miners will reduce hash power impacting the security and speed of transactions. Again, this is a risk with every fork, but by starting with such a small reward the BTCP team could be putting additional pressure on an already difficult balancing act. Finally, and arguably most importantly, the claims of privacy through Bitcoin Private are imperfect. Between two shielded wallets the privacy components are excellent. However, because there are very few decentralized exchanges, BTCP transactions made on an exchange will not be truly private. Centralized exchanges, though they typically send transactions in bulk, have to keep records to comply with governmental regulations. True peer-to-peer transactions are limited at this stage and because most transactions include at least one side operating through an exchange, the feasible impact of the privacy assurances are limited. This does, however, position BTCP perfectly for the future implementation of decentralized exchanges, though again not in a way that Zcash and Zclassic are not already positioned. Overall, Bitcoin Private is fine. It includes some minor improvements over Zclassic, but nothing groundbreaking. It is being implemented by an experienced team, so I have confidence in their ability to implement the project at promised. In some ways it feels like a “third time’s the charm,” approach — but that isn’t necessarily a statement on its potential for success. I don’t have any significant problem with BTCP, but it also isn’t particularly exciting. **BTCP feels symptomatic of this period in crypto overall, which is idling, experimenting and waiting for the tools that enable wider adoption.** |
| json metadata | {"tags":["bitcoinprivate","btcp","zcl","btc"],"image":["https://steemitimages.com/DQmNedTyaUrw2zEdDyaME4fuq9mqMnrisCYtbTogT4U5HNJ/Screen%20Shot%202018-02-26%20at%203.42.54%20PM.png","https://steemitimages.com/DQmPhch2g2EZ282cRE8gurTZFYEYM2kyN5iqBLaT5tZy6ye/Screen%20Shot%202018-02-26%20at%203.47.50%20PM.png","https://steemitimages.com/DQmRH9GzaA86QqzLaGQYDkQvS5fKjoS4hcQQaJudPZLpFSn/hard-fork-graphic.png","https://steemitimages.com/DQmTiaCAUPfXP9T17M5WLJvpMEcAdaY8wgAjJwmTJqir5NW/Screen%20Shot%202018-02-26%20at%203.40.49%20PM.png"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #20219765/Trx ea6a88686f1b6275551ead047164b691d168e02c |
View Raw JSON Data
{
"trx_id": "ea6a88686f1b6275551ead047164b691d168e02c",
"block": 20219765,
"trx_in_block": 47,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-26T22:28:21",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "bitcoinprivate",
"author": "torib",
"permlink": "bitcoin-private-brand-new-btc-or-same-old-zcl",
"title": "Bitcoin Private: Brand New BTC or Same Old ZCL?",
"body": "\n\n## TL;DR the BTCP White Paper\n\nThe crypto community is waiting with bated breath, anxiously refreshing Bittrex on twitter, harassing Rhett Creighton any way they can, for news on the upcoming hard fork of BTC and ZCL — Bitcoin Private. The team behind BTCP is striving to create a new currency that is faster, better aligned and, as the name implies, private.\n\n\n\nThe BTCP white paper focuses primarily on the shortcomings of other significant blockchains and how BTCP improves on those issues. BTCP features a larger 2MB fixed block size compared to Bitcoin’s 1MB, and a 2.5 minute block time compared to BTC’s 10 minute time. These features are the same as Zcash and Zclassic. BTCP uses Equihash, the premier ASIC resistant proof-of-work algorithm. The snapshot, or the exact time when you must hold BTC or ZCL in order to receive BTCP in the fork, will happen at 5pm UTC on February 28, 2018. Currently BTCP has exchange support on Trade Satoshi but Bittrex is expected to announce support at some point.\n\nThe Bitcoin Private team is is calling the fork a “fork-merge,” because everyone holding 1 Zclassic or 1 Bitcoin at the time of the snapshot will receive 1 BTCP. This is a unique method, combining the UTXOs (unspent transaction outputs, in this case any BTC or ZCL that is held), but actual blockchain being forked is Zclassic. The total supply of BTCP is 21 million, and at the time of the fork almost 20.4 million of those will already exist from the initial distribution. The BTCP team claims this will make them the “*least inflationary coin ever produced,*” according to their white paper.\n\n \n\nFor miners, the team took lessons from both Zcash and Zclassic. BTCP has no “founder tax,” an unpopular feature of Zcash, but does include a system to incentivize developers, which was neglected in Zclassic. They facilitated this by creating a “voluntary miner pool,” which would reward Zclassic miners for contributing to a fund by offering them a >1:1 proportion of BTCP to their ZCL contribution after the fork. The reward for mining at the first block will be 0.7815 BTCP. After about 66,000 blocks the reward will be cut in half, and will continue halving every 840,000 blocks.\n\nThe claim to increasing privacy comes from the implementation of a zero-knowledge proof algorithm called zk-SNARKs. Transactions can be either transparent, visible on the blockchain, or shielded, where they verifiable but not able to be tracked by outside parties.\n\n## BTCP — Third Time’s a Charm?\n\nPractically, and when considered in a vacuum, Bitcoin Private is solid. The white paper is well considered and well reasoned and addresses some major and important problems in the cryptocurrency space. However, when compared with its true predecessors, Zcash and Zclassic, **Bitcoin Private not much more than a small shift and better branding.**\n\nZcash was a fork of Bitcoin that made some important improvements, such as the inclusion of Equihash, which without going into too much detail, improves the strength of the claim of decentralization. Zcash also included what is effectively the cornerstone of Bitcoin Private, the application of zk-SKARKs. Zcash faced criticism over the exorbitant founders tax on all mining, which led to an almost comically fast fork into Zclassic, which was technologically similar to Zcash but excluded the founders tax, which had the unintended consequence of neglecting developer incentives. Bitcoin Private is effectively the same as Zclassic but attempts to fix some of the developer incentive issues, by creating a pre-fork, voluntary donation pool.\n\nThe white paper tends to obscure the similarity to Zclassic and Zcash by comparing BTCP to Bitcoin, Bitcoin Cash and Bitcoin Gold (See table on page 3 for example). I like to believe that this focus was intended to emphasize the improvements that BTCP makes over these other Bitcoin forks, but it also speaks to a larger trend in the space. For such a promising technology like blockchain there is an incredible amount of snake oil being sold. At this point so early in the exploration of the space, maybe that’s fine. **But eventually, supporters will get smart enough to know that we aren’t really adding value.** And, frankly, if your white paper needs to be a little shady that doesn’t bode well for your ability to execute.\n\n\n\nBitcoin Private claims to be focused on their community in a way that Zcash and Zclassic didn’t pull off well. Zcash was a sincerely novel project in a lot of ways, so we can assume that they thought they would need the money from the pre-mine and the 20% founders tax. Zclassic reversed those, but didn’t make any moves to actively reward developers so they lagged on improvements. Bitcoin Private’s actual largest change was in the way they looked to solve these problems, but it is unclear whether or not they hit the mark. Their community focus includes a treasury fund to incentivize developers and a community developer program. The treasury fund is governed by primarily by the Bitcoin Private team, hardly and arms-length transaction, and has no stated plans to transfer that management to the community. The developer program as described is open to anyone but requires a successful application to the program and so is still tightly controlled. This isn’t to say the approach won’t be effective, but that the amount of input allowed from the community may be overstated.\n\nThe structure of the BTCP block reward is a risk that will ultimately depend on the value of the coin. This is true of every coin, of course, but by starting with such a small reward, if the price drops immediately after the fork, miners could lose confidence and stop mining. Inevitably some miners will stay because the difficulty is adjusted based on the number of miners, but having only a small number of miners will reduce hash power impacting the security and speed of transactions. Again, this is a risk with every fork, but by starting with such a small reward the BTCP team could be putting additional pressure on an already difficult balancing act.\n\nFinally, and arguably most importantly, the claims of privacy through Bitcoin Private are imperfect. Between two shielded wallets the privacy components are excellent. However, because there are very few decentralized exchanges, BTCP transactions made on an exchange will not be truly private. Centralized exchanges, though they typically send transactions in bulk, have to keep records to comply with governmental regulations. True peer-to-peer transactions are limited at this stage and because most transactions include at least one side operating through an exchange, the feasible impact of the privacy assurances are limited. This does, however, position BTCP perfectly for the future implementation of decentralized exchanges, though again not in a way that Zcash and Zclassic are not already positioned. \n\nOverall, Bitcoin Private is fine. It includes some minor improvements over Zclassic, but nothing groundbreaking. It is being implemented by an experienced team, so I have confidence in their ability to implement the project at promised. In some ways it feels like a “third time’s the charm,” approach — but that isn’t necessarily a statement on its potential for success. I don’t have any significant problem with BTCP, but it also isn’t particularly exciting. **BTCP feels symptomatic of this period in crypto overall, which is idling, experimenting and waiting for the tools that enable wider adoption.**",
"json_metadata": "{\"tags\":[\"bitcoinprivate\",\"btcp\",\"zcl\",\"btc\"],\"image\":[\"https://steemitimages.com/DQmNedTyaUrw2zEdDyaME4fuq9mqMnrisCYtbTogT4U5HNJ/Screen%20Shot%202018-02-26%20at%203.42.54%20PM.png\",\"https://steemitimages.com/DQmPhch2g2EZ282cRE8gurTZFYEYM2kyN5iqBLaT5tZy6ye/Screen%20Shot%202018-02-26%20at%203.47.50%20PM.png\",\"https://steemitimages.com/DQmRH9GzaA86QqzLaGQYDkQvS5fKjoS4hcQQaJudPZLpFSn/hard-fork-graphic.png\",\"https://steemitimages.com/DQmTiaCAUPfXP9T17M5WLJvpMEcAdaY8wgAjJwmTJqir5NW/Screen%20Shot%202018-02-26%20at%203.40.49%20PM.png\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}2017/12/12 22:23:24
2017/12/12 22:23:24
| delegator | steem |
| delegatee | torib |
| vesting shares | 29737.650199 VESTS |
| Transaction Info | Block #18032651/Trx 6898c7fa02cf085002515b02a0042d4e31fa2db7 |
View Raw JSON Data
{
"trx_id": "6898c7fa02cf085002515b02a0042d4e31fa2db7",
"block": 18032651,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-12T22:23:24",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "torib",
"vesting_shares": "29737.650199 VESTS"
}
]
}toribfollowed @heiditravels2017/10/20 20:50:00
toribfollowed @heiditravels
2017/10/20 20:50:00
| required auths | [] |
| required posting auths | ["torib"] |
| id | follow |
| json | ["follow",{"follower":"torib","following":"heiditravels","what":["blog"]}] |
| Transaction Info | Block #16505109/Trx 21ff0cd73987213b8a6fad944d00292bde0532fc |
View Raw JSON Data
{
"trx_id": "21ff0cd73987213b8a6fad944d00292bde0532fc",
"block": 16505109,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-10-20T20:50:00",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"torib"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"torib\",\"following\":\"heiditravels\",\"what\":[\"blog\"]}]"
}
]
}toribupvoted (100.00%) @heiditravels / learning-crypto-what-is-a-blockchain2017/10/20 20:49:54
toribupvoted (100.00%) @heiditravels / learning-crypto-what-is-a-blockchain
2017/10/20 20:49:54
| voter | torib |
| author | heiditravels |
| permlink | learning-crypto-what-is-a-blockchain |
| weight | 10000 (100.00%) |
| Transaction Info | Block #16505107/Trx d4c08c40a1cea2b4e88137d1a2f791747e0f9310 |
View Raw JSON Data
{
"trx_id": "d4c08c40a1cea2b4e88137d1a2f791747e0f9310",
"block": 16505107,
"trx_in_block": 22,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-10-20T20:49:54",
"op": [
"vote",
{
"voter": "torib",
"author": "heiditravels",
"permlink": "learning-crypto-what-is-a-blockchain",
"weight": 10000
}
]
}toribupvoted (100.00%) @adamgering / do-your-own-due-diligence2017/10/20 20:42:27
toribupvoted (100.00%) @adamgering / do-your-own-due-diligence
2017/10/20 20:42:27
| voter | torib |
| author | adamgering |
| permlink | do-your-own-due-diligence |
| weight | 10000 (100.00%) |
| Transaction Info | Block #16504958/Trx c36c5f7004f5a4efddc70e4259c0b4addc06a92b |
View Raw JSON Data
{
"trx_id": "c36c5f7004f5a4efddc70e4259c0b4addc06a92b",
"block": 16504958,
"trx_in_block": 23,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-10-20T20:42:27",
"op": [
"vote",
{
"voter": "torib",
"author": "adamgering",
"permlink": "do-your-own-due-diligence",
"weight": 10000
}
]
}toribfollowed @adamgering2017/10/20 20:40:15
toribfollowed @adamgering
2017/10/20 20:40:15
| required auths | [] |
| required posting auths | ["torib"] |
| id | follow |
| json | ["follow",{"follower":"torib","following":"adamgering","what":["blog"]}] |
| Transaction Info | Block #16504914/Trx 15f9bed1d92639121e01440a64390e40dc58d6cc |
View Raw JSON Data
{
"trx_id": "15f9bed1d92639121e01440a64390e40dc58d6cc",
"block": 16504914,
"trx_in_block": 14,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-10-20T20:40:15",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"torib"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"torib\",\"following\":\"adamgering\",\"what\":[\"blog\"]}]"
}
]
}toribupvoted (100.00%) @penchina / rules-i-use-to-evaluate-ico-s2017/10/20 20:39:54
toribupvoted (100.00%) @penchina / rules-i-use-to-evaluate-ico-s
2017/10/20 20:39:54
| voter | torib |
| author | penchina |
| permlink | rules-i-use-to-evaluate-ico-s |
| weight | 10000 (100.00%) |
| Transaction Info | Block #16504907/Trx 84121580aa91dfcb4cdc0cae7278747f768ad47c |
View Raw JSON Data
{
"trx_id": "84121580aa91dfcb4cdc0cae7278747f768ad47c",
"block": 16504907,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-10-20T20:39:54",
"op": [
"vote",
{
"voter": "torib",
"author": "penchina",
"permlink": "rules-i-use-to-evaluate-ico-s",
"weight": 10000
}
]
}2017/10/20 20:39:39
2017/10/20 20:39:39
| required auths | [] |
| required posting auths | ["torib"] |
| id | follow |
| json | ["follow",{"follower":"torib","following":"penchina","what":["blog"]}] |
| Transaction Info | Block #16504902/Trx 8ba6d0c9e3a4074086eb30e98255faec92c22e2b |
View Raw JSON Data
{
"trx_id": "8ba6d0c9e3a4074086eb30e98255faec92c22e2b",
"block": 16504902,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-10-20T20:39:39",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"torib"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"torib\",\"following\":\"penchina\",\"what\":[\"blog\"]}]"
}
]
}2017/10/20 20:38:27
2017/10/20 20:38:27
| required auths | [] |
| required posting auths | ["torib"] |
| id | follow |
| json | ["follow",{"follower":"torib","following":"zeekay","what":["blog"]}] |
| Transaction Info | Block #16504878/Trx 931ef3cca296faefa008916bd8c20080778fca18 |
View Raw JSON Data
{
"trx_id": "931ef3cca296faefa008916bd8c20080778fca18",
"block": 16504878,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-10-20T20:38:27",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"torib"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"torib\",\"following\":\"zeekay\",\"what\":[\"blog\"]}]"
}
]
}toribupdated their account properties2017/10/20 20:36:15
toribupdated their account properties
2017/10/20 20:36:15
| account | torib |
| memo key | STM7snt5zSWgue38Ue9SD5xpU6CUzyaA7i3zXMJGjuDT2SEAD5DQG |
| json metadata | {"profile":{"profile_image":"https://pbs.twimg.com/profile_images/839587883837190145/c58vTBrB.jpg","name":"Tori Benson","about":"COO at Hanzo","location":"Kansas City, MO","website":"https://www.linkedin.com/in/tori-benson/"}} |
| Transaction Info | Block #16504834/Trx 68ffd728231e0dc30a44cf6537542b3c86e2bed0 |
View Raw JSON Data
{
"trx_id": "68ffd728231e0dc30a44cf6537542b3c86e2bed0",
"block": 16504834,
"trx_in_block": 11,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-10-20T20:36:15",
"op": [
"account_update",
{
"account": "torib",
"memo_key": "STM7snt5zSWgue38Ue9SD5xpU6CUzyaA7i3zXMJGjuDT2SEAD5DQG",
"json_metadata": "{\"profile\":{\"profile_image\":\"https://pbs.twimg.com/profile_images/839587883837190145/c58vTBrB.jpg\",\"name\":\"Tori Benson\",\"about\":\"COO at Hanzo\",\"location\":\"Kansas City, MO\",\"website\":\"https://www.linkedin.com/in/tori-benson/\"}}"
}
]
}2017/10/20 20:30:18
2017/10/20 20:30:18
| fee | 0.500 STEEM |
| delegation | 57000.000000 VESTS |
| creator | steem |
| new account name | torib |
| owner | {"weight_threshold":1,"account_auths":[],"key_auths":[["STM5dZ1vg6cwUyaRveyDsBv65HovLJpoqnzYcaPerjEjHVfJPLGaq",1]]} |
| active | {"weight_threshold":1,"account_auths":[],"key_auths":[["STM738TBZdcbKqxhYy6RAtGi8yeHdsikPfSrGGWDHzZWobwGtyXnD",1]]} |
| posting | {"weight_threshold":1,"account_auths":[],"key_auths":[["STM6YQJG7RZxbWCjzeAs4AdSdUWWUSM6YLa56icyZvm9T4efTKXLg",1]]} |
| memo key | STM7snt5zSWgue38Ue9SD5xpU6CUzyaA7i3zXMJGjuDT2SEAD5DQG |
| json metadata | |
| extensions | [] |
| Transaction Info | Block #16504715/Trx 4242fb01f56379f01ef423eb011322785403de6d |
View Raw JSON Data
{
"trx_id": "4242fb01f56379f01ef423eb011322785403de6d",
"block": 16504715,
"trx_in_block": 20,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-10-20T20:30:18",
"op": [
"account_create_with_delegation",
{
"fee": "0.500 STEEM",
"delegation": "57000.000000 VESTS",
"creator": "steem",
"new_account_name": "torib",
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5dZ1vg6cwUyaRveyDsBv65HovLJpoqnzYcaPerjEjHVfJPLGaq",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM738TBZdcbKqxhYy6RAtGi8yeHdsikPfSrGGWDHzZWobwGtyXnD",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM6YQJG7RZxbWCjzeAs4AdSdUWWUSM6YLa56icyZvm9T4efTKXLg",
1
]
]
},
"memo_key": "STM7snt5zSWgue38Ue9SD5xpU6CUzyaA7i3zXMJGjuDT2SEAD5DQG",
"json_metadata": "",
"extensions": []
}
]
}Manabar
Voting Power100.00%
Downvote Power100.00%
Resource Credits100.00%
Reputation Progress0.00%
{
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779089766
},
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779089766
},
"rc_account": {
"account": "torib",
"rc_manabar": {
"current_mana": "10164408779",
"last_update_time": 1779089766
},
"max_rc_creation_adjustment": {
"amount": "2020748973",
"precision": 6,
"nai": "@@000000037"
},
"max_rc": "10164408779"
}
}Account Metadata
| POSTING JSON METADATA | |
| profile | {"profile_image":"https://pbs.twimg.com/profile_images/839587883837190145/c58vTBrB.jpg","name":"Tori Benson","about":"COO at Hanzo","location":"Kansas City, MO","website":"https://www.linkedin.com/in/tori-benson/"} |
| JSON METADATA | |
| profile | {"profile_image":"https://pbs.twimg.com/profile_images/839587883837190145/c58vTBrB.jpg","name":"Tori Benson","about":"COO at Hanzo","location":"Kansas City, MO","website":"https://www.linkedin.com/in/tori-benson/"} |
{
"posting_json_metadata": {
"profile": {
"profile_image": "https://pbs.twimg.com/profile_images/839587883837190145/c58vTBrB.jpg",
"name": "Tori Benson",
"about": "COO at Hanzo",
"location": "Kansas City, MO",
"website": "https://www.linkedin.com/in/tori-benson/"
}
},
"json_metadata": {
"profile": {
"profile_image": "https://pbs.twimg.com/profile_images/839587883837190145/c58vTBrB.jpg",
"name": "Tori Benson",
"about": "COO at Hanzo",
"location": "Kansas City, MO",
"website": "https://www.linkedin.com/in/tori-benson/"
}
}
}Auth Keys
Owner
Single Signature
Public Keys
STM5dZ1vg6cwUyaRveyDsBv65HovLJpoqnzYcaPerjEjHVfJPLGaq1/1
Active
Single Signature
Public Keys
STM738TBZdcbKqxhYy6RAtGi8yeHdsikPfSrGGWDHzZWobwGtyXnD1/1
Posting
Single Signature
Public Keys
STM6YQJG7RZxbWCjzeAs4AdSdUWWUSM6YLa56icyZvm9T4efTKXLg1/1
Memo
STM7snt5zSWgue38Ue9SD5xpU6CUzyaA7i3zXMJGjuDT2SEAD5DQG
{
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5dZ1vg6cwUyaRveyDsBv65HovLJpoqnzYcaPerjEjHVfJPLGaq",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM738TBZdcbKqxhYy6RAtGi8yeHdsikPfSrGGWDHzZWobwGtyXnD",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM6YQJG7RZxbWCjzeAs4AdSdUWWUSM6YLa56icyZvm9T4efTKXLg",
1
]
]
},
"memo": "STM7snt5zSWgue38Ue9SD5xpU6CUzyaA7i3zXMJGjuDT2SEAD5DQG"
}Witness Votes
0 / 30
No active witness votes.
[]