VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS0.00%
Net Worth
0.056USD
STEEM
0.002STEEM
SBD
0.039SBD
Effective Power
5.007SP
├── Own SP
0.636SP
└── Incoming DelegationsDeleg
+4.372SP
Detailed Balance
| STEEM | ||
| balance | 0.002STEEM | STEEM |
| market_balance | 0.000STEEM | STEEM |
| savings_balance | 0.000STEEM | STEEM |
| reward_steem_balance | 0.000STEEM | STEEM |
| STEEM POWER | ||
| Own SP | 0.636SP | SP |
| Delegated Out | 0.000SP | SP |
| Delegation In | 4.372SP | SP |
| Effective Power | 5.007SP | SP |
| Reward SP (pending) | 0.020SP | 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.039SBD | SBD |
{
"balance": "0.002 STEEM",
"savings_balance": "0.000 STEEM",
"reward_steem_balance": "0.000 STEEM",
"vesting_shares": "1033.749470 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "7109.910336 VESTS",
"sbd_balance": "0.000 SBD",
"savings_sbd_balance": "0.000 SBD",
"reward_sbd_balance": "0.039 SBD",
"conversions": []
}Account Info
| name | selfdrivingsandp |
| id | 256944 |
| rank | 976,572 |
| reputation | 441932858 |
| created | 2017-07-13T03:59:18 |
| recovery_account | steem |
| proxy | None |
| post_count | 37 |
| comment_count | 0 |
| lifetime_vote_count | 0 |
| witnesses_voted_for | 0 |
| last_post | 2018-01-24T12:15:06 |
| last_root_post | 2018-01-24T12:15:06 |
| last_vote_time | 2017-12-28T16:00:06 |
| proxied_vsf_votes | 0, 0, 0, 0 |
| can_vote | 1 |
| voting_power | 0 |
| delayed_votes | 0 |
| balance | 0.002 STEEM |
| savings_balance | 0.000 STEEM |
| sbd_balance | 0.000 SBD |
| savings_sbd_balance | 0.000 SBD |
| vesting_shares | 1033.749470 VESTS |
| delegated_vesting_shares | 0.000000 VESTS |
| received_vesting_shares | 7109.910336 VESTS |
| reward_vesting_balance | 41.223366 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 | 2017-07-13T04:00:27 |
| last_account_update | 2017-07-13T04:00:27 |
| 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": 256944,
"name": "selfdrivingsandp",
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7dihyRe2u9jJLCeMJBcn2wUN3nsKdi6HRt2YGAvmUeyFgD5sDg",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7FDU5MEtRnUk1LdQMwUwCFPG7u5YyZyG7kgSkFdUWqfnUKfe5d",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7carZV2iSRZkP94kopB6vDfCfPFeQT2a4og5birKDUEC8yaYtZ",
1
]
]
},
"memo_key": "STM88N5Wkv2gMuZzAkz5zwKmWKsmEn8idgJ2mCr97B82n3GFFRvtv",
"json_metadata": "",
"posting_json_metadata": "",
"proxy": "",
"last_owner_update": "2017-07-13T04:00:27",
"last_account_update": "2017-07-13T04:00:27",
"created": "2017-07-13T03:59: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": 37,
"can_vote": true,
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779085065
},
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779085065
},
"voting_power": 0,
"balance": "0.002 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.039 SBD",
"reward_steem_balance": "0.000 STEEM",
"reward_vesting_balance": "41.223366 VESTS",
"reward_vesting_steem": "0.020 STEEM",
"vesting_shares": "1033.749470 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "7109.910336 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": 38,
"proxied_vsf_votes": [
0,
0,
0,
0
],
"witnesses_voted_for": 0,
"last_post": "2018-01-24T12:15:06",
"last_root_post": "2018-01-24T12:15:06",
"last_vote_time": "2017-12-28T16:00:06",
"post_bandwidth": 0,
"pending_claimed_accounts": 0,
"vesting_balance": "0.000 STEEM",
"reputation": 441932858,
"transfer_history": [],
"market_history": [],
"post_history": [],
"vote_history": [],
"other_history": [],
"witness_votes": [],
"tags_usage": [],
"guest_bloggers": [],
"rank": 976572
}Withdraw Routes
| Incoming | Outgoing |
|---|---|
Empty | Empty |
{
"incoming": [],
"outgoing": []
}From Date
To Date
steemdelegated 4.372 SP to @selfdrivingsandp2026/05/18 06:17:45
steemdelegated 4.372 SP to @selfdrivingsandp
2026/05/18 06:17:45
| delegator | steem |
| delegatee | selfdrivingsandp |
| vesting shares | 7109.910336 VESTS |
| Transaction Info | Block #106150668/Trx adf0f90572492fdae498c009c978ba6c96010afb |
View Raw JSON Data
{
"trx_id": "adf0f90572492fdae498c009c978ba6c96010afb",
"block": 106150668,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-05-18T06:17:45",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "selfdrivingsandp",
"vesting_shares": "7109.910336 VESTS"
}
]
}steemdelegated 2.704 SP to @selfdrivingsandp2026/05/13 04:25:27
steemdelegated 2.704 SP to @selfdrivingsandp
2026/05/13 04:25:27
| delegator | steem |
| delegatee | selfdrivingsandp |
| vesting shares | 4397.699931 VESTS |
| Transaction Info | Block #106005143/Trx 0d41aa14e94cae69b3cce6cd3f53995b9b5ac22a |
View Raw JSON Data
{
"trx_id": "0d41aa14e94cae69b3cce6cd3f53995b9b5ac22a",
"block": 106005143,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-05-13T04:25:27",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "selfdrivingsandp",
"vesting_shares": "4397.699931 VESTS"
}
]
}steemdelegated 4.380 SP to @selfdrivingsandp2026/04/26 05:29:27
steemdelegated 4.380 SP to @selfdrivingsandp
2026/04/26 05:29:27
| delegator | steem |
| delegatee | selfdrivingsandp |
| vesting shares | 7122.426092 VESTS |
| Transaction Info | Block #105518150/Trx 0c2efcfd83c3b794c6251614c5d8d0899168c903 |
View Raw JSON Data
{
"trx_id": "0c2efcfd83c3b794c6251614c5d8d0899168c903",
"block": 105518150,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-04-26T05:29:27",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "selfdrivingsandp",
"vesting_shares": "7122.426092 VESTS"
}
]
}steemdelegated 2.730 SP to @selfdrivingsandp2026/01/24 00:04:48
steemdelegated 2.730 SP to @selfdrivingsandp
2026/01/24 00:04:48
| delegator | steem |
| delegatee | selfdrivingsandp |
| vesting shares | 4439.246750 VESTS |
| Transaction Info | Block #102871311/Trx 0fcef973620cfa4a6c00c07e49acd5bc20858d78 |
View Raw JSON Data
{
"trx_id": "0fcef973620cfa4a6c00c07e49acd5bc20858d78",
"block": 102871311,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-01-24T00:04:48",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "selfdrivingsandp",
"vesting_shares": "4439.246750 VESTS"
}
]
}steemdelegated 2.831 SP to @selfdrivingsandp2024/12/17 19:14:30
steemdelegated 2.831 SP to @selfdrivingsandp
2024/12/17 19:14:30
| delegator | steem |
| delegatee | selfdrivingsandp |
| vesting shares | 4603.465947 VESTS |
| Transaction Info | Block #91317519/Trx c358af6f594a5289fdcd74ec02c504c868324295 |
View Raw JSON Data
{
"trx_id": "c358af6f594a5289fdcd74ec02c504c868324295",
"block": 91317519,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2024-12-17T19:14:30",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "selfdrivingsandp",
"vesting_shares": "4603.465947 VESTS"
}
]
}steemdelegated 2.935 SP to @selfdrivingsandp2023/11/14 10:55:48
steemdelegated 2.935 SP to @selfdrivingsandp
2023/11/14 10:55:48
| delegator | steem |
| delegatee | selfdrivingsandp |
| vesting shares | 4772.599479 VESTS |
| Transaction Info | Block #79871670/Trx 3302b3057f9ed76d2d506ef8f0a62a3ac2f80d78 |
View Raw JSON Data
{
"trx_id": "3302b3057f9ed76d2d506ef8f0a62a3ac2f80d78",
"block": 79871670,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2023-11-14T10:55:48",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "selfdrivingsandp",
"vesting_shares": "4772.599479 VESTS"
}
]
}steemdelegated 4.740 SP to @selfdrivingsandp2023/09/22 10:24:39
steemdelegated 4.740 SP to @selfdrivingsandp
2023/09/22 10:24:39
| delegator | steem |
| delegatee | selfdrivingsandp |
| vesting shares | 7709.508265 VESTS |
| Transaction Info | Block #78362888/Trx b616fae250e4497a967e7caf35a898c91f9956c0 |
View Raw JSON Data
{
"trx_id": "b616fae250e4497a967e7caf35a898c91f9956c0",
"block": 78362888,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2023-09-22T10:24:39",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "selfdrivingsandp",
"vesting_shares": "7709.508265 VESTS"
}
]
}partitura.lifeupvoted (100.00%) @selfdrivingsandp / right-to-be-forgotten2022/11/06 09:21:30
partitura.lifeupvoted (100.00%) @selfdrivingsandp / right-to-be-forgotten
2022/11/06 09:21:30
| voter | partitura.life |
| author | selfdrivingsandp |
| permlink | right-to-be-forgotten |
| weight | 10000 (100.00%) |
| Transaction Info | Block #69196471/Trx f922dfa0d6fc8f0fa241761bb6cf3174968dec16 |
View Raw JSON Data
{
"trx_id": "f922dfa0d6fc8f0fa241761bb6cf3174968dec16",
"block": 69196471,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2022-11-06T09:21:30",
"op": [
"vote",
{
"voter": "partitura.life",
"author": "selfdrivingsandp",
"permlink": "right-to-be-forgotten",
"weight": 10000
}
]
}steemdelegated 4.877 SP to @selfdrivingsandp2022/11/03 17:51:54
steemdelegated 4.877 SP to @selfdrivingsandp
2022/11/03 17:51:54
| delegator | steem |
| delegatee | selfdrivingsandp |
| vesting shares | 7931.559703 VESTS |
| Transaction Info | Block #69120621/Trx be48ef0253e6651b124f644d0faa3f72f9cc14af |
View Raw JSON Data
{
"trx_id": "be48ef0253e6651b124f644d0faa3f72f9cc14af",
"block": 69120621,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2022-11-03T17:51:54",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "selfdrivingsandp",
"vesting_shares": "7931.559703 VESTS"
}
]
}steemdelegated 5.012 SP to @selfdrivingsandp2022/01/17 23:03:30
steemdelegated 5.012 SP to @selfdrivingsandp
2022/01/17 23:03:30
| delegator | steem |
| delegatee | selfdrivingsandp |
| vesting shares | 8151.667304 VESTS |
| Transaction Info | Block #60823863/Trx bdf1e849c3e8650d05beea62b0b698c421f5e59f |
View Raw JSON Data
{
"trx_id": "bdf1e849c3e8650d05beea62b0b698c421f5e59f",
"block": 60823863,
"trx_in_block": 51,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2022-01-17T23:03:30",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "selfdrivingsandp",
"vesting_shares": "8151.667304 VESTS"
}
]
}steemdelegated 5.126 SP to @selfdrivingsandp2021/06/14 06:14:30
steemdelegated 5.126 SP to @selfdrivingsandp
2021/06/14 06:14:30
| delegator | steem |
| delegatee | selfdrivingsandp |
| vesting shares | 8335.861592 VESTS |
| Transaction Info | Block #54614188/Trx 0c9c10294ad757c9c0cbc6ae1c8a1e0686a7f678 |
View Raw JSON Data
{
"trx_id": "0c9c10294ad757c9c0cbc6ae1c8a1e0686a7f678",
"block": 54614188,
"trx_in_block": 9,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2021-06-14T06:14:30",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "selfdrivingsandp",
"vesting_shares": "8335.861592 VESTS"
}
]
}steemdelegated 5.241 SP to @selfdrivingsandp2020/12/11 16:26:45
steemdelegated 5.241 SP to @selfdrivingsandp
2020/12/11 16:26:45
| delegator | steem |
| delegatee | selfdrivingsandp |
| vesting shares | 8523.283566 VESTS |
| Transaction Info | Block #49361454/Trx 67da56544f96bb6b98677de847b82958b5560d24 |
View Raw JSON Data
{
"trx_id": "67da56544f96bb6b98677de847b82958b5560d24",
"block": 49361454,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-12-11T16:26:45",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "selfdrivingsandp",
"vesting_shares": "8523.283566 VESTS"
}
]
}steemdelegated 1.176 SP to @selfdrivingsandp2020/12/06 10:02:27
steemdelegated 1.176 SP to @selfdrivingsandp
2020/12/06 10:02:27
| delegator | steem |
| delegatee | selfdrivingsandp |
| vesting shares | 1912.543513 VESTS |
| Transaction Info | Block #49212975/Trx 9d287f01ed0362410433ecf656fe802408562f12 |
View Raw JSON Data
{
"trx_id": "9d287f01ed0362410433ecf656fe802408562f12",
"block": 49212975,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-12-06T10:02:27",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "selfdrivingsandp",
"vesting_shares": "1912.543513 VESTS"
}
]
}steemdelegated 5.245 SP to @selfdrivingsandp2020/12/05 20:04:36
steemdelegated 5.245 SP to @selfdrivingsandp
2020/12/05 20:04:36
| delegator | steem |
| delegatee | selfdrivingsandp |
| vesting shares | 8529.491420 VESTS |
| Transaction Info | Block #49196538/Trx 1309ddac207097eaa0519bb8aaee68dbe3269ebd |
View Raw JSON Data
{
"trx_id": "1309ddac207097eaa0519bb8aaee68dbe3269ebd",
"block": 49196538,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-12-05T20:04:36",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "selfdrivingsandp",
"vesting_shares": "8529.491420 VESTS"
}
]
}steemdelegated 1.181 SP to @selfdrivingsandp2020/11/03 02:40:09
steemdelegated 1.181 SP to @selfdrivingsandp
2020/11/03 02:40:09
| delegator | steem |
| delegatee | selfdrivingsandp |
| vesting shares | 1920.017158 VESTS |
| Transaction Info | Block #48270789/Trx 9777f7d336d0b65f0cea011478971040772925fb |
View Raw JSON Data
{
"trx_id": "9777f7d336d0b65f0cea011478971040772925fb",
"block": 48270789,
"trx_in_block": 11,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-11-03T02:40:09",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "selfdrivingsandp",
"vesting_shares": "1920.017158 VESTS"
}
]
}steemdelegated 5.369 SP to @selfdrivingsandp2020/05/09 11:05:27
steemdelegated 5.369 SP to @selfdrivingsandp
2020/05/09 11:05:27
| delegator | steem |
| delegatee | selfdrivingsandp |
| vesting shares | 8732.296779 VESTS |
| Transaction Info | Block #43223302/Trx 0b783cd59750aeb029ed2e6aa09872f602fccc2f |
View Raw JSON Data
{
"trx_id": "0b783cd59750aeb029ed2e6aa09872f602fccc2f",
"block": 43223302,
"trx_in_block": 8,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-05-09T11:05:27",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "selfdrivingsandp",
"vesting_shares": "8732.296779 VESTS"
}
]
}steemdelegated 1.201 SP to @selfdrivingsandp2020/05/08 15:29:48
steemdelegated 1.201 SP to @selfdrivingsandp
2020/05/08 15:29:48
| delegator | steem |
| delegatee | selfdrivingsandp |
| vesting shares | 1953.311140 VESTS |
| Transaction Info | Block #43200347/Trx fce58e1bf93ffe5b61c502bd2915582431be9ce8 |
View Raw JSON Data
{
"trx_id": "fce58e1bf93ffe5b61c502bd2915582431be9ce8",
"block": 43200347,
"trx_in_block": 12,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-05-08T15:29:48",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "selfdrivingsandp",
"vesting_shares": "1953.311140 VESTS"
}
]
}steemdelegated 5.377 SP to @selfdrivingsandp2020/04/16 03:16:45
steemdelegated 5.377 SP to @selfdrivingsandp
2020/04/16 03:16:45
| delegator | steem |
| delegatee | selfdrivingsandp |
| vesting shares | 8745.184227 VESTS |
| Transaction Info | Block #42569135/Trx 50b82ffd29b038942d2b8eaa9785718e5d8f5273 |
View Raw JSON Data
{
"trx_id": "50b82ffd29b038942d2b8eaa9785718e5d8f5273",
"block": 42569135,
"trx_in_block": 13,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-16T03:16:45",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "selfdrivingsandp",
"vesting_shares": "8745.184227 VESTS"
}
]
}2019/07/13 05:22:36
2019/07/13 05:22:36
| parent author | selfdrivingsandp |
| parent permlink | protection-against-the-oncoming-artificial-intellgience-onslaught |
| author | steemitboard |
| permlink | steemitboard-notify-selfdrivingsandp-20190713t052236000z |
| title | |
| body | Congratulations @selfdrivingsandp! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@selfdrivingsandp/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/@selfdrivingsandp) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=selfdrivingsandp)_</sub> ###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| Transaction Info | Block #34617525/Trx 05caa1cd57a322a3b7ac06a808a6703e64673378 |
View Raw JSON Data
{
"trx_id": "05caa1cd57a322a3b7ac06a808a6703e64673378",
"block": 34617525,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-07-13T05:22:36",
"op": [
"comment",
{
"parent_author": "selfdrivingsandp",
"parent_permlink": "protection-against-the-oncoming-artificial-intellgience-onslaught",
"author": "steemitboard",
"permlink": "steemitboard-notify-selfdrivingsandp-20190713t052236000z",
"title": "",
"body": "Congratulations @selfdrivingsandp! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@selfdrivingsandp/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/@selfdrivingsandp) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=selfdrivingsandp)_</sub>\n\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}"
}
]
}steemdelegated 5.498 SP to @selfdrivingsandp2019/05/12 20:23:51
steemdelegated 5.498 SP to @selfdrivingsandp
2019/05/12 20:23:51
| delegator | steem |
| delegatee | selfdrivingsandp |
| vesting shares | 8940.801040 VESTS |
| Transaction Info | Block #32852078/Trx 917876e643445591281b72a849f28288c17f5651 |
View Raw JSON Data
{
"trx_id": "917876e643445591281b72a849f28288c17f5651",
"block": 32852078,
"trx_in_block": 16,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-05-12T20:23:51",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "selfdrivingsandp",
"vesting_shares": "8940.801040 VESTS"
}
]
}2018/07/13 05:02:39
2018/07/13 05:02:39
| parent author | selfdrivingsandp |
| parent permlink | protection-against-the-oncoming-artificial-intellgience-onslaught |
| author | steemitboard |
| permlink | steemitboard-notify-selfdrivingsandp-20180713t050241000z |
| title | |
| body | Congratulations @selfdrivingsandp! You have received a personal award! [](http://steemitboard.com/@selfdrivingsandp) 1 Year on Steemit <sub>_Click on the badge to view your Board of Honor._</sub> **Do not miss the last post from @steemitboard:** [SteemitBoard World Cup Contest - Semi Finals - Day 1](https://steemit.com/steemitboard/@steemitboard/steemitboard-world-cup-contest-semi-finals-day-1) --- **Participate in the [SteemitBoard World Cup Contest](https://steemit.com/steemitboard/@steemitboard/steemitboard-world-cup-contest-collect-badges-and-win-free-sbd)!** Collect World Cup badges and win free SBD Support the Gold Sponsors of the contest: [@good-karma](https://v2.steemconnect.com/sign/account-witness-vote?witness=good-karma&approve=1) and [@lukestokes](https://v2.steemconnect.com/sign/account-witness-vote?witness=lukestokes.mhth&approve=1) --- > Do you like [SteemitBoard's project](https://steemit.com/@steemitboard)? Then **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| Transaction Info | Block #24130692/Trx ee81bd19c8ede637feba2b502195191974d8dc97 |
View Raw JSON Data
{
"trx_id": "ee81bd19c8ede637feba2b502195191974d8dc97",
"block": 24130692,
"trx_in_block": 34,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-07-13T05:02:39",
"op": [
"comment",
{
"parent_author": "selfdrivingsandp",
"parent_permlink": "protection-against-the-oncoming-artificial-intellgience-onslaught",
"author": "steemitboard",
"permlink": "steemitboard-notify-selfdrivingsandp-20180713t050241000z",
"title": "",
"body": "Congratulations @selfdrivingsandp! You have received a personal award!\n\n[](http://steemitboard.com/@selfdrivingsandp) 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[SteemitBoard World Cup Contest - Semi Finals - Day 1](https://steemit.com/steemitboard/@steemitboard/steemitboard-world-cup-contest-semi-finals-day-1)\n\n---\n**Participate in the [SteemitBoard World Cup Contest](https://steemit.com/steemitboard/@steemitboard/steemitboard-world-cup-contest-collect-badges-and-win-free-sbd)!**\nCollect World Cup badges and win free SBD\nSupport the Gold Sponsors of the contest: [@good-karma](https://v2.steemconnect.com/sign/account-witness-vote?witness=good-karma&approve=1) and [@lukestokes](https://v2.steemconnect.com/sign/account-witness-vote?witness=lukestokes.mhth&approve=1)\n\n---\n\n> Do you like [SteemitBoard's project](https://steemit.com/@steemitboard)? Then **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}"
}
]
}steemdelegated 5.620 SP to @selfdrivingsandp2018/05/17 02:42:27
steemdelegated 5.620 SP to @selfdrivingsandp
2018/05/17 02:42:27
| delegator | steem |
| delegatee | selfdrivingsandp |
| vesting shares | 9140.316132 VESTS |
| Transaction Info | Block #22497549/Trx 1ec3f68f76bd2adcfea63776679bcdded67f6afa |
View Raw JSON Data
{
"trx_id": "1ec3f68f76bd2adcfea63776679bcdded67f6afa",
"block": 22497549,
"trx_in_block": 21,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-17T02:42:27",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "selfdrivingsandp",
"vesting_shares": "9140.316132 VESTS"
}
]
}money-dreamersent 0.001 STEEM to @selfdrivingsandp- "Gift!"2018/01/25 06:14:33
money-dreamersent 0.001 STEEM to @selfdrivingsandp- "Gift!"
2018/01/25 06:14:33
| from | money-dreamer |
| to | selfdrivingsandp |
| amount | 0.001 STEEM |
| memo | Gift! |
| Transaction Info | Block #19279612/Trx a5bbb3098ad565b1090edbc1e78a8c8cbfb32bf6 |
View Raw JSON Data
{
"trx_id": "a5bbb3098ad565b1090edbc1e78a8c8cbfb32bf6",
"block": 19279612,
"trx_in_block": 33,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-25T06:14:33",
"op": [
"transfer",
{
"from": "money-dreamer",
"to": "selfdrivingsandp",
"amount": "0.001 STEEM",
"memo": "Gift!"
}
]
}selfdrivingsandppublished a new post: protection-against-the-oncoming-artificial-intellgience-onslaught2018/01/24 12:15:06
selfdrivingsandppublished a new post: protection-against-the-oncoming-artificial-intellgience-onslaught
2018/01/24 12:15:06
| parent author | |
| parent permlink | artificialintelligence |
| author | selfdrivingsandp |
| permlink | protection-against-the-oncoming-artificial-intellgience-onslaught |
| title | Protection Against the Oncoming Artificial Intellgience Onslaught |
| body | An insurance company has [increased premiums](https://www.theguardian.com/technology/shortcuts/2018/jan/23/a-sign-that-youre-not-keeping-up-the-trouble-with-hotmail-in-2018) for those with Hotmail address. The machine learning algorithm decided that [Hotmail users are more likely to crash](https://www.thesun.co.uk/motors/5401901/admiral-hikes-insurance-costs-for-drivers-using-hotmail-email-addresses/). “Certain domain names are associated with more accidents than others.” However, this is not the first such [instance](https://www.thesun.co.uk/motors/5393978/insurance-race-row-john-mohammed/). MOTORISTS are being stung for almost £1,000 more to insure cars if their name is Mohammed. Top firms Admiral, Marks & Spencer, Bell, Elephant and Diamond all give far lower quotes when the driver has the English name John, a Sun investigation reveals. At what point is enough is enough? When will we start protecting our personal information and demand transparency regarding costs and fees? |
| json metadata | {"tags":["artificialintelligence","privacy","security"],"links":["https://www.theguardian.com/technology/shortcuts/2018/jan/23/a-sign-that-youre-not-keeping-up-the-trouble-with-hotmail-in-2018","https://www.thesun.co.uk/motors/5401901/admiral-hikes-insurance-costs-for-drivers-using-hotmail-email-addresses/","https://www.thesun.co.uk/motors/5393978/insurance-race-row-john-mohammed/"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #19258030/Trx 891a15a2f0e2c6b8d4612b05ed5553f053811d55 |
View Raw JSON Data
{
"trx_id": "891a15a2f0e2c6b8d4612b05ed5553f053811d55",
"block": 19258030,
"trx_in_block": 30,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-24T12:15:06",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "artificialintelligence",
"author": "selfdrivingsandp",
"permlink": "protection-against-the-oncoming-artificial-intellgience-onslaught",
"title": "Protection Against the Oncoming Artificial Intellgience Onslaught",
"body": "An insurance company has [increased premiums](https://www.theguardian.com/technology/shortcuts/2018/jan/23/a-sign-that-youre-not-keeping-up-the-trouble-with-hotmail-in-2018) for those with Hotmail address. The machine learning algorithm decided that [Hotmail users are more likely to crash](https://www.thesun.co.uk/motors/5401901/admiral-hikes-insurance-costs-for-drivers-using-hotmail-email-addresses/). \n\n“Certain domain names are associated with more accidents than others.”\n\nHowever, this is not the first such [instance](https://www.thesun.co.uk/motors/5393978/insurance-race-row-john-mohammed/).\n\nMOTORISTS are being stung for almost £1,000 more to insure cars if their name is Mohammed.\n\nTop firms Admiral, Marks & Spencer, Bell, Elephant and Diamond all give far lower quotes when the driver has the English name John, a Sun investigation reveals.\n\nAt what point is enough is enough? When will we start protecting our personal information and demand transparency regarding costs and fees?",
"json_metadata": "{\"tags\":[\"artificialintelligence\",\"privacy\",\"security\"],\"links\":[\"https://www.theguardian.com/technology/shortcuts/2018/jan/23/a-sign-that-youre-not-keeping-up-the-trouble-with-hotmail-in-2018\",\"https://www.thesun.co.uk/motors/5401901/admiral-hikes-insurance-costs-for-drivers-using-hotmail-email-addresses/\",\"https://www.thesun.co.uk/motors/5393978/insurance-race-row-john-mohammed/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}2018/01/24 11:57:48
2018/01/24 11:57:48
| voter | rialdisaputra1 |
| author | selfdrivingsandp |
| permlink | tesla-firetruck-accident-the-need-for-vehicle-to-vehicle-communication |
| weight | 10000 (100.00%) |
| Transaction Info | Block #19257684/Trx 56beac7053c2307a69ba89c1b9cda87d9739ec8d |
View Raw JSON Data
{
"trx_id": "56beac7053c2307a69ba89c1b9cda87d9739ec8d",
"block": 19257684,
"trx_in_block": 25,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-24T11:57:48",
"op": [
"vote",
{
"voter": "rialdisaputra1",
"author": "selfdrivingsandp",
"permlink": "tesla-firetruck-accident-the-need-for-vehicle-to-vehicle-communication",
"weight": 10000
}
]
}selfdrivingsandppublished a new post: tesla-firetruck-accident-the-need-for-vehicle-to-vehicle-communication2018/01/24 11:56:09
selfdrivingsandppublished a new post: tesla-firetruck-accident-the-need-for-vehicle-to-vehicle-communication
2018/01/24 11:56:09
| parent author | |
| parent permlink | autopilot |
| author | selfdrivingsandp |
| permlink | tesla-firetruck-accident-the-need-for-vehicle-to-vehicle-communication |
| title | Tesla Firetruck Accident - The Need for Vehicle to Vehicle Communication |
| body | Again we have another AutoPilot Tesla accident. Fortunately there were no injuries.  Again, we have Tesla selling a production car yet playing the legal game where the liability is on the driver. How is it an vehicle being sold with AutoPilot is unable to recognize a large red firetruck with lights on? The firetruck was helping out another accident on the freeway! This further provides argument that vehicle to vehicle communication is needed. Why rely on computer vision alone? |
| json metadata | {"tags":["autopilot","selfdriving","v2v","dsrc"],"image":["https://steemitimages.com/DQmVgQuPwessr6hCZyYQixtYfQ49eNjyKZ7Wf78ucic8BQ6/image.png"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #19257651/Trx ef06735992629928dbde09023ccd77bf998f6749 |
View Raw JSON Data
{
"trx_id": "ef06735992629928dbde09023ccd77bf998f6749",
"block": 19257651,
"trx_in_block": 11,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-24T11:56:09",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "autopilot",
"author": "selfdrivingsandp",
"permlink": "tesla-firetruck-accident-the-need-for-vehicle-to-vehicle-communication",
"title": "Tesla Firetruck Accident - The Need for Vehicle to Vehicle Communication",
"body": "Again we have another AutoPilot Tesla accident. Fortunately there were no injuries.\n\n\n\n\nAgain, we have Tesla selling a production car yet playing the legal game where the liability is on the driver.\n\nHow is it an vehicle being sold with AutoPilot is unable to recognize a large red firetruck with lights on? The firetruck was helping out another accident on the freeway!\n\nThis further provides argument that vehicle to vehicle communication is needed. Why rely on computer vision alone?",
"json_metadata": "{\"tags\":[\"autopilot\",\"selfdriving\",\"v2v\",\"dsrc\"],\"image\":[\"https://steemitimages.com/DQmVgQuPwessr6hCZyYQixtYfQ49eNjyKZ7Wf78ucic8BQ6/image.png\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}selfdrivingsandpfollowed @hottopic2018/01/24 11:51:36
selfdrivingsandpfollowed @hottopic
2018/01/24 11:51:36
| required auths | [] |
| required posting auths | ["selfdrivingsandp"] |
| id | follow |
| json | ["follow",{"follower":"selfdrivingsandp","following":"hottopic","what":["blog"]}] |
| Transaction Info | Block #19257560/Trx 6596adf55acd3fe1f7e6e85c434371b21f5d215e |
View Raw JSON Data
{
"trx_id": "6596adf55acd3fe1f7e6e85c434371b21f5d215e",
"block": 19257560,
"trx_in_block": 44,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-24T11:51:36",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"selfdrivingsandp"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"selfdrivingsandp\",\"following\":\"hottopic\",\"what\":[\"blog\"]}]"
}
]
}selfdrivingsandppublished a new post: crypto-sense2018/01/23 04:38:45
selfdrivingsandppublished a new post: crypto-sense
2018/01/23 04:38:45
| parent author | |
| parent permlink | cryptocurrency |
| author | selfdrivingsandp |
| permlink | crypto-sense |
| title | Crypto Sense? |
| body | Suppose I make a new proof of stake coin. The supply is fixed and coins are not earned by any nodes. There are no transaction fees. The only way to get coins is to somehow receive coins from the initial distribution or purchasing off exchanges. Now suppose the security model of my coin is delegated proof of stake, where representatives make all voting decisions. Also, my coin favors performance over security. One might wonder how these representatives are chosen? How could they get so many coins if there was no reward mechanism? Did they somehow get all the coins via the distribution? Did they really sink so much money to purchase the coins from exchanges? What if I then say that this coin will create it's own exchange to trade? Does any of this start to raise questions? Is the exchange a way for the developers or inside group to dump and sell their coins? |
| json metadata | {"tags":["cryptocurrency","exchanges","cryptosense","blockchain"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #19220120/Trx 55d14068733dfb3291639027b4f165c9700ce45c |
View Raw JSON Data
{
"trx_id": "55d14068733dfb3291639027b4f165c9700ce45c",
"block": 19220120,
"trx_in_block": 44,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-23T04:38:45",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "cryptocurrency",
"author": "selfdrivingsandp",
"permlink": "crypto-sense",
"title": "Crypto Sense?",
"body": "Suppose I make a new proof of stake coin. The supply is fixed and coins are not earned by any nodes. There are no transaction fees.\n\nThe only way to get coins is to somehow receive coins from the initial distribution or purchasing off exchanges.\n\nNow suppose the security model of my coin is delegated proof of stake, where representatives make all voting decisions. Also, my coin favors performance over security.\n\nOne might wonder how these representatives are chosen? How could they get so many coins if there was no reward mechanism? Did they somehow get all the coins via the distribution? Did they really sink so much money to purchase the coins from exchanges?\n\nWhat if I then say that this coin will create it's own exchange to trade?\n\nDoes any of this start to raise questions?\n\nIs the exchange a way for the developers or inside group to dump and sell their coins?",
"json_metadata": "{\"tags\":[\"cryptocurrency\",\"exchanges\",\"cryptosense\",\"blockchain\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}changtimwuupvoted (100.00%) @selfdrivingsandp / security-thoughts-on-raiblocks2018/01/13 10:16:03
changtimwuupvoted (100.00%) @selfdrivingsandp / security-thoughts-on-raiblocks
2018/01/13 10:16:03
| voter | changtimwu |
| author | selfdrivingsandp |
| permlink | security-thoughts-on-raiblocks |
| weight | 10000 (100.00%) |
| Transaction Info | Block #18939014/Trx 065f731f64259ae4fda83dbf36a863ad82453160 |
View Raw JSON Data
{
"trx_id": "065f731f64259ae4fda83dbf36a863ad82453160",
"block": 18939014,
"trx_in_block": 34,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-13T10:16:03",
"op": [
"vote",
{
"voter": "changtimwu",
"author": "selfdrivingsandp",
"permlink": "security-thoughts-on-raiblocks",
"weight": 10000
}
]
}chokheshevupvoted (100.00%) @selfdrivingsandp / thoughts-on-social-scalability2018/01/12 21:40:06
chokheshevupvoted (100.00%) @selfdrivingsandp / thoughts-on-social-scalability
2018/01/12 21:40:06
| voter | chokheshev |
| author | selfdrivingsandp |
| permlink | thoughts-on-social-scalability |
| weight | 10000 (100.00%) |
| Transaction Info | Block #18923925/Trx 4ea9234308ccc45c9129b62d41efeae1864be1c8 |
View Raw JSON Data
{
"trx_id": "4ea9234308ccc45c9129b62d41efeae1864be1c8",
"block": 18923925,
"trx_in_block": 13,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-12T21:40:06",
"op": [
"vote",
{
"voter": "chokheshev",
"author": "selfdrivingsandp",
"permlink": "thoughts-on-social-scalability",
"weight": 10000
}
]
}2018/01/12 20:56:36
2018/01/12 20:56:36
| parent author | selfdrivingsandp |
| parent permlink | re-prakashkagitha-re-selfdrivingsandp-thoughts-on-social-scalability-20180112t144319100z |
| author | prakashkagitha |
| permlink | re-selfdrivingsandp-re-prakashkagitha-re-selfdrivingsandp-thoughts-on-social-scalability-20180112t205630972z |
| title | |
| body | Centralization helps new initiatives grow faster, for sure. But in the case where majority vote is vital to decide whether those proposed initiatives are worth perceiving, initiatives that has no majority vote are not worth perceiving. Decentralized governance makes all the people ( stakeholders, users) the owners of the company, but only decentralized, thus having the validation, by involvement of a large mass, but not their stupidity as one or one small group. Stopping good initiatives because they came from other group is not anyone's interest. Nonetheless, centralized governance is sane until we have the technological improvements to engineer stupidity-proof, more efficient governance models. |
| json metadata | {"tags":["social-scalability"],"app":"steemit/0.1"} |
| Transaction Info | Block #18923058/Trx 5b257b28612eb31d02e917f70262876c827f7f36 |
View Raw JSON Data
{
"trx_id": "5b257b28612eb31d02e917f70262876c827f7f36",
"block": 18923058,
"trx_in_block": 17,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-12T20:56:36",
"op": [
"comment",
{
"parent_author": "selfdrivingsandp",
"parent_permlink": "re-prakashkagitha-re-selfdrivingsandp-thoughts-on-social-scalability-20180112t144319100z",
"author": "prakashkagitha",
"permlink": "re-selfdrivingsandp-re-prakashkagitha-re-selfdrivingsandp-thoughts-on-social-scalability-20180112t205630972z",
"title": "",
"body": "Centralization helps new initiatives grow faster, for sure. But in the case where majority vote is vital to decide whether those proposed initiatives are worth perceiving, initiatives that has no majority vote are not worth perceiving. Decentralized governance makes all the people ( stakeholders, users) the owners of the company, but only decentralized, thus having the validation, by involvement of a large mass, but not their stupidity as one or one small group. \n\nStopping good initiatives because they came from other group is not anyone's interest. \nNonetheless, centralized governance is sane until we have the technological improvements to engineer stupidity-proof, more efficient governance models.",
"json_metadata": "{\"tags\":[\"social-scalability\"],\"app\":\"steemit/0.1\"}"
}
]
}2018/01/12 14:43:21
2018/01/12 14:43:21
| parent author | prakashkagitha |
| parent permlink | re-selfdrivingsandp-thoughts-on-social-scalability-20180112t121319548z |
| author | selfdrivingsandp |
| permlink | re-prakashkagitha-re-selfdrivingsandp-thoughts-on-social-scalability-20180112t144319100z |
| title | |
| body | I'm not clear why decentralized governance is an improvement. I can see the advantage of permissionless participation though. The quickest way to kill an initiative is to create a committee to "investigate". So I'm not sure why decentralized governance would actually achieve anything and be able to handle serious issues or disruptions. Social checks and balances can be manipulated, look at politics today. Multiple parties doesn't really move along important issues and can actually be used to halt initiatives due to lack of majority vote. In fact, many security protocols are built on the collusion assumption in that it only takes one honest non colluding party to halt a multi party computation. So why would decentralization help improve governance, when in fact it's used for the opposite? |
| json metadata | {"tags":["social-scalability"],"app":"steemit/0.1"} |
| Transaction Info | Block #18915611/Trx c59672d5537bcbb6ee12036f54fad984aeb53e53 |
View Raw JSON Data
{
"trx_id": "c59672d5537bcbb6ee12036f54fad984aeb53e53",
"block": 18915611,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-12T14:43:21",
"op": [
"comment",
{
"parent_author": "prakashkagitha",
"parent_permlink": "re-selfdrivingsandp-thoughts-on-social-scalability-20180112t121319548z",
"author": "selfdrivingsandp",
"permlink": "re-prakashkagitha-re-selfdrivingsandp-thoughts-on-social-scalability-20180112t144319100z",
"title": "",
"body": "I'm not clear why decentralized governance is an improvement. I can see the advantage of permissionless participation though.\n\nThe quickest way to kill an initiative is to create a committee to \"investigate\". So I'm not sure why decentralized governance would actually achieve anything and be able to handle serious issues or disruptions. Social checks and balances can be manipulated, look at politics today. \n\nMultiple parties doesn't really move along important issues and can actually be used to halt initiatives due to lack of majority vote. In fact, many security protocols are built on the collusion assumption in that it only takes one honest non colluding party to halt a multi party computation.\n\nSo why would decentralization help improve governance, when in fact it's used for the opposite?",
"json_metadata": "{\"tags\":[\"social-scalability\"],\"app\":\"steemit/0.1\"}"
}
]
}prakashkagithaupvoted (100.00%) @selfdrivingsandp / thoughts-on-social-scalability2018/01/12 12:13:30
prakashkagithaupvoted (100.00%) @selfdrivingsandp / thoughts-on-social-scalability
2018/01/12 12:13:30
| voter | prakashkagitha |
| author | selfdrivingsandp |
| permlink | thoughts-on-social-scalability |
| weight | 10000 (100.00%) |
| Transaction Info | Block #18912622/Trx 24983a282bff4df59eeab7c0556dc4dcfd26ca0d |
View Raw JSON Data
{
"trx_id": "24983a282bff4df59eeab7c0556dc4dcfd26ca0d",
"block": 18912622,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-12T12:13:30",
"op": [
"vote",
{
"voter": "prakashkagitha",
"author": "selfdrivingsandp",
"permlink": "thoughts-on-social-scalability",
"weight": 10000
}
]
}2018/01/12 12:13:21
2018/01/12 12:13:21
| parent author | selfdrivingsandp |
| parent permlink | thoughts-on-social-scalability |
| author | prakashkagitha |
| permlink | re-selfdrivingsandp-thoughts-on-social-scalability-20180112t121319548z |
| title | |
| body | Great thought!! I think DAO (Decentralized Autonomous organizations) are socially scalable. We need decentralized organizations which can be more effective in charities, technological campanies, educational institutions and so on. I think there is more room for the decentralization of governance in many field in this open new world. Don't you think? |
| json metadata | {"tags":["social-scalability"],"app":"steemit/0.1"} |
| Transaction Info | Block #18912619/Trx 7684d74d3fbb5b0f84b132a4aa00f0b187c51413 |
View Raw JSON Data
{
"trx_id": "7684d74d3fbb5b0f84b132a4aa00f0b187c51413",
"block": 18912619,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-12T12:13:21",
"op": [
"comment",
{
"parent_author": "selfdrivingsandp",
"parent_permlink": "thoughts-on-social-scalability",
"author": "prakashkagitha",
"permlink": "re-selfdrivingsandp-thoughts-on-social-scalability-20180112t121319548z",
"title": "",
"body": "Great thought!!\nI think DAO (Decentralized Autonomous organizations) are socially scalable. We need decentralized organizations which can be more effective in charities, technological campanies, educational institutions and so on. I think there is more room for the decentralization of governance in many field in this open new world. Don't you think?",
"json_metadata": "{\"tags\":[\"social-scalability\"],\"app\":\"steemit/0.1\"}"
}
]
}selfdrivingsandppublished a new post: thoughts-on-social-scalability2018/01/12 12:09:18
selfdrivingsandppublished a new post: thoughts-on-social-scalability
2018/01/12 12:09:18
| parent author | |
| parent permlink | social-scalability |
| author | selfdrivingsandp |
| permlink | thoughts-on-social-scalability |
| title | Thoughts on Social Scalability |
| body | @@ -1,260 +1,78 @@ -Will no %22social scalability%22 equivalent be expected to exist in blockchains such as Bitcoin?%0A%0ASurely there is a certain asymmetry that exists in technological breakthroughs. The observed impact is far larger than the invested energy or capital.%0A%0AHowever, s +Should we really expect that Bitcoin continues to be %22social scalable%22? S houl @@ -290,16 +290,17 @@ d system +a tic vuln @@ -401,17 +401,17 @@ complete -l +n ess theo @@ -721,16 +721,66 @@ c system + for transactions (and is not longer peer to peer) . By wha @@ -839,32 +839,92 @@ can -be scaled in such a way? +continue to scale when in fact it's going from peer to peer to a centralised system. %0A%0AIn @@ -1307,30 +1307,81 @@ his -can be easily replaced +the supporting ecosystem be easily replaced by a socially scalable system ?%0A%0AT @@ -2055,9 +2055,10 @@ are -1 +an are |
| json metadata | {"tags":["social-scalability","blockchain","bitcoin"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #18912538/Trx 04e586c5c5d1bab6ebf6ab0c81704525c38c64ae |
View Raw JSON Data
{
"trx_id": "04e586c5c5d1bab6ebf6ab0c81704525c38c64ae",
"block": 18912538,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-12T12:09:18",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "social-scalability",
"author": "selfdrivingsandp",
"permlink": "thoughts-on-social-scalability",
"title": "Thoughts on Social Scalability",
"body": "@@ -1,260 +1,78 @@\n-Will no %22social scalability%22 equivalent be expected to exist in blockchains such as Bitcoin?%0A%0ASurely there is a certain asymmetry that exists in technological breakthroughs. The observed impact is far larger than the invested energy or capital.%0A%0AHowever, s\n+Should we really expect that Bitcoin continues to be %22social scalable%22? S\n houl\n@@ -290,16 +290,17 @@\n d system\n+a\n tic vuln\n@@ -401,17 +401,17 @@\n complete\n-l\n+n\n ess theo\n@@ -721,16 +721,66 @@\n c system\n+ for transactions (and is not longer peer to peer)\n . By wha\n@@ -839,32 +839,92 @@\n can \n-be scaled in such a way?\n+continue to scale when in fact it's going from peer to peer to a centralised system.\n %0A%0AIn\n@@ -1307,30 +1307,81 @@\n his \n-can be easily replaced\n+the supporting ecosystem be easily replaced by a socially scalable system\n ?%0A%0AT\n@@ -2055,9 +2055,10 @@\n are \n-1\n+an\n are\n",
"json_metadata": "{\"tags\":[\"social-scalability\",\"blockchain\",\"bitcoin\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}selfdrivingsandppublished a new post: thoughts-on-social-scalability2018/01/12 12:04:12
selfdrivingsandppublished a new post: thoughts-on-social-scalability
2018/01/12 12:04:12
| parent author | |
| parent permlink | social-scalability |
| author | selfdrivingsandp |
| permlink | thoughts-on-social-scalability |
| title | Thoughts on Social Scalability |
| body | Will no "social scalability" equivalent be expected to exist in blockchains such as Bitcoin? Surely there is a certain asymmetry that exists in technological breakthroughs. The observed impact is far larger than the invested energy or capital. However, should we really expect that technology alone will run autonomously and scale seamlessly? What reason is there to believe that we can simply spend cheap computing resources to avoid the expensive human redundancy and systemtic vulnerability to human error? At what point do computational limits and theory such as Godel's incompleteless theorem hinder the technology scalability? Sure we can throw more resources into maintaining the Bitcoin network and cast by the wayside saying that the costs to maintain the network is far cheaper than having an army of accountants, lawyers, and regulators. Except for one fact. Bitcoin is a very specific system. By what extension should we believe that an entire system can be scaled in such a way? In fact, let's take a look at two pieces. First the ecosystem required to interact with Bitcoin and second newer blockchains such as Ethereum. It's very hard to ignore the fact that the ecosystem around actually using Bitcoin is full of security vulnerabilities. In fact, simply casting this aside saying that these are known issues is concerning. What evidence is there that this can be easily replaced? There's a growing centralization of mining power. Why is this a good thing? Should we somehow feel better that someone with more resources is controlling and making decisions? Someone says, ok well fork the chain if you have a problem. Well, I fork Bitcoin and can't an existing mining pool just attempt to attack me? Fact is not easy to take all my Bitcon assets and fork in case of a dispute. The centralization of Bitcoin mining power, why is this socially scalable? Second observation. Attempts to build an "ecosystem" around blockchain is not really functioning so well. There is an army of accountants and lawyers and regulators that are required. Exchanges are 1 area that comes to mind. What about Ethereum? Is this socially scalable? Why is creating a large running world computer deemed to be safe? As if bugs will not happen or creep in? As if serious impacting bugs have not crept in to smart contracts already? The biggest and well known computer is the Internet today. It's nowhere close to being socially scalable. There are dozens of bugs everyday, just look at how routing is managed by humans. Internet service providers and the entire industry is regulated. Would it be nice if we could have social scalability? Sure. Is it realistic to assume that we can have a large ecosystem? If we do, it will clearly be a large technology break through. |
| json metadata | {"tags":["social-scalability","blockchain","bitcoin"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #18912437/Trx e7760a7b1cb28686c8596cfc9ca626fb9e0c25ca |
View Raw JSON Data
{
"trx_id": "e7760a7b1cb28686c8596cfc9ca626fb9e0c25ca",
"block": 18912437,
"trx_in_block": 10,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-12T12:04:12",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "social-scalability",
"author": "selfdrivingsandp",
"permlink": "thoughts-on-social-scalability",
"title": "Thoughts on Social Scalability",
"body": "Will no \"social scalability\" equivalent be expected to exist in blockchains such as Bitcoin?\n\nSurely there is a certain asymmetry that exists in technological breakthroughs. The observed impact is far larger than the invested energy or capital.\n\nHowever, should we really expect that technology alone will run autonomously and scale seamlessly?\n\nWhat reason is there to believe that we can simply spend cheap computing resources to avoid the expensive human redundancy and systemtic vulnerability to human error?\n\nAt what point do computational limits and theory such as Godel's incompleteless theorem hinder the technology scalability?\n\nSure we can throw more resources into maintaining the Bitcoin network and cast by the wayside saying that the costs to maintain the network is far cheaper than having an army of accountants, lawyers, and regulators.\n\nExcept for one fact. Bitcoin is a very specific system. By what extension should we believe that an entire system can be scaled in such a way?\n\nIn fact, let's take a look at two pieces. First the ecosystem required to interact with Bitcoin and second newer blockchains such as Ethereum.\n\nIt's very hard to ignore the fact that the ecosystem around actually using Bitcoin is full of security vulnerabilities. In fact, simply casting this aside saying that these are known issues is concerning. What evidence is there that this can be easily replaced?\n\nThere's a growing centralization of mining power. Why is this a good thing? Should we somehow feel better that someone with more resources is controlling and making decisions?\n\nSomeone says, ok well fork the chain if you have a problem. Well, I fork Bitcoin and can't an existing mining pool just attempt to attack me?\n\nFact is not easy to take all my Bitcon assets and fork in case of a dispute.\n\nThe centralization of Bitcoin mining power, why is this socially scalable?\n\nSecond observation. Attempts to build an \"ecosystem\" around blockchain is not really functioning so well. There is an army of accountants and lawyers and regulators that are required. Exchanges are 1 area that comes to mind.\n\nWhat about Ethereum? Is this socially scalable? Why is creating a large running world computer deemed to be safe? As if bugs will not happen or creep in? As if serious impacting bugs have not crept in to smart contracts already?\n\nThe biggest and well known computer is the Internet today. It's nowhere close to being socially scalable. There are dozens of bugs everyday, just look at how routing is managed by humans. Internet service providers and the entire industry is regulated.\n\nWould it be nice if we could have social scalability?\n\nSure.\n\nIs it realistic to assume that we can have a large ecosystem?\n\nIf we do, it will clearly be a large technology break through.",
"json_metadata": "{\"tags\":[\"social-scalability\",\"blockchain\",\"bitcoin\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}selfdrivingsandpreceived 0.023 SBD, 0.006 SP author reward for @selfdrivingsandp / raiblocks-lack-of-settlement-finality2018/01/11 16:17:12
selfdrivingsandpreceived 0.023 SBD, 0.006 SP author reward for @selfdrivingsandp / raiblocks-lack-of-settlement-finality
2018/01/11 16:17:12
| author | selfdrivingsandp |
| permlink | raiblocks-lack-of-settlement-finality |
| sbd payout | 0.023 SBD |
| steem payout | 0.000 STEEM |
| vesting payout | 10.240555 VESTS |
| Transaction Info | Block #18888715/Virtual Operation #32 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 18888715,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 32,
"timestamp": "2018-01-11T16:17:12",
"op": [
"author_reward",
{
"author": "selfdrivingsandp",
"permlink": "raiblocks-lack-of-settlement-finality",
"sbd_payout": "0.023 SBD",
"steem_payout": "0.000 STEEM",
"vesting_payout": "10.240555 VESTS"
}
]
}swansontecupvoted (100.00%) @selfdrivingsandp / security-thoughts-on-raiblocks2018/01/09 20:46:45
swansontecupvoted (100.00%) @selfdrivingsandp / security-thoughts-on-raiblocks
2018/01/09 20:46:45
| voter | swansontec |
| author | selfdrivingsandp |
| permlink | security-thoughts-on-raiblocks |
| weight | 10000 (100.00%) |
| Transaction Info | Block #18836523/Trx ef0360089831a3f2e30d28bf0ecd676a931cfca6 |
View Raw JSON Data
{
"trx_id": "ef0360089831a3f2e30d28bf0ecd676a931cfca6",
"block": 18836523,
"trx_in_block": 25,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-09T20:46:45",
"op": [
"vote",
{
"voter": "swansontec",
"author": "selfdrivingsandp",
"permlink": "security-thoughts-on-raiblocks",
"weight": 10000
}
]
}steemdelegated 18.257 SP to @selfdrivingsandp2018/01/09 07:12:48
steemdelegated 18.257 SP to @selfdrivingsandp
2018/01/09 07:12:48
| delegator | steem |
| delegatee | selfdrivingsandp |
| vesting shares | 29691.404081 VESTS |
| Transaction Info | Block #18820252/Trx f7312b5fdf56b58a8aba87d363923dc15a0a8978 |
View Raw JSON Data
{
"trx_id": "f7312b5fdf56b58a8aba87d363923dc15a0a8978",
"block": 18820252,
"trx_in_block": 23,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-09T07:12:48",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "selfdrivingsandp",
"vesting_shares": "29691.404081 VESTS"
}
]
}2018/01/05 23:31:54
2018/01/05 23:31:54
| parent author | selfdrivingsandp |
| parent permlink | re-cryptohazard-re-selfdrivingsandp-raiblocks-lack-of-settlement-finality-20180105t210910100z |
| author | cryptohazard |
| permlink | re-selfdrivingsandp-re-cryptohazard-re-selfdrivingsandp-raiblocks-lack-of-settlement-finality-20180105t233152478z |
| title | |
| body | What I don't like is how they say: yay we have a DAG it's awesome. The real question is how to choose from two *concurrent* block or chain? They vote hence PoS. So how do they fix PoS issues? I was really disappointed by the attacks they studied in the whitepaper. |
| json metadata | {"tags":["raiblocks"],"app":"steemit/0.1"} |
| Transaction Info | Block #18724753/Trx 23a028788676f40214234bc52f65efe384eea176 |
View Raw JSON Data
{
"trx_id": "23a028788676f40214234bc52f65efe384eea176",
"block": 18724753,
"trx_in_block": 18,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-05T23:31:54",
"op": [
"comment",
{
"parent_author": "selfdrivingsandp",
"parent_permlink": "re-cryptohazard-re-selfdrivingsandp-raiblocks-lack-of-settlement-finality-20180105t210910100z",
"author": "cryptohazard",
"permlink": "re-selfdrivingsandp-re-cryptohazard-re-selfdrivingsandp-raiblocks-lack-of-settlement-finality-20180105t233152478z",
"title": "",
"body": "What I don't like is how they say: yay we have a DAG it's awesome. The real question is how to choose from two *concurrent* block or chain? They vote hence PoS. So how do they fix PoS issues? I was really disappointed by the attacks they studied in the whitepaper.",
"json_metadata": "{\"tags\":[\"raiblocks\"],\"app\":\"steemit/0.1\"}"
}
]
}selfdrivingsandpfollowed @cryptohazard2018/01/05 21:10:30
selfdrivingsandpfollowed @cryptohazard
2018/01/05 21:10:30
| required auths | [] |
| required posting auths | ["selfdrivingsandp"] |
| id | follow |
| json | ["follow",{"follower":"selfdrivingsandp","following":"cryptohazard","what":["blog"]}] |
| Transaction Info | Block #18721926/Trx 33458d42300aebbe07740723f2baa0002b8cf6ce |
View Raw JSON Data
{
"trx_id": "33458d42300aebbe07740723f2baa0002b8cf6ce",
"block": 18721926,
"trx_in_block": 42,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-05T21:10:30",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"selfdrivingsandp"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"selfdrivingsandp\",\"following\":\"cryptohazard\",\"what\":[\"blog\"]}]"
}
]
}2018/01/05 21:09:33
2018/01/05 21:09:33
| parent author | cryptohazard |
| parent permlink | re-selfdrivingsandp-raiblocks-lack-of-settlement-finality-20180105t183158591z |
| author | selfdrivingsandp |
| permlink | re-cryptohazard-re-selfdrivingsandp-raiblocks-lack-of-settlement-finality-20180105t210910100z |
| title | |
| body | One of the first points to address should be how the ledger is balanced. Many of these DAGs sidestep the issue and focus on alternative security attacks. At least with PoS we can formalize a model. Many of these DAGs just simply choose to sidestep these particular ledger issues, a little too slick for comfort. |
| json metadata | {"tags":["raiblocks"],"app":"steemit/0.1"} |
| Transaction Info | Block #18721907/Trx 4187dc8507a7b90dccb403e0801062bbf354e6fd |
View Raw JSON Data
{
"trx_id": "4187dc8507a7b90dccb403e0801062bbf354e6fd",
"block": 18721907,
"trx_in_block": 24,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-05T21:09:33",
"op": [
"comment",
{
"parent_author": "cryptohazard",
"parent_permlink": "re-selfdrivingsandp-raiblocks-lack-of-settlement-finality-20180105t183158591z",
"author": "selfdrivingsandp",
"permlink": "re-cryptohazard-re-selfdrivingsandp-raiblocks-lack-of-settlement-finality-20180105t210910100z",
"title": "",
"body": "One of the first points to address should be how the ledger is balanced. Many of these DAGs sidestep the issue and focus on alternative security attacks.\n\nAt least with PoS we can formalize a model. Many of these DAGs just simply choose to sidestep these particular ledger issues, a little too slick for comfort.",
"json_metadata": "{\"tags\":[\"raiblocks\"],\"app\":\"steemit/0.1\"}"
}
]
}selfdrivingsandppublished a new post: raiblocks-lack-of-settlement-finality2018/01/05 21:05:33
selfdrivingsandppublished a new post: raiblocks-lack-of-settlement-finality
2018/01/05 21:05:33
| parent author | |
| parent permlink | raiblocks |
| author | selfdrivingsandp |
| permlink | raiblocks-lack-of-settlement-finality |
| title | Raiblocks Lack of Settlement Finality |
| body | @@ -304,17 +304,16 @@ e downsi -%0A de is th @@ -432,17 +432,16 @@ he first -%0A major i @@ -659,17 +659,16 @@ ccounts, -%0A negativ @@ -787,17 +787,16 @@ dger and -%0A sacrifi @@ -1043,17 +1043,16 @@ ombining -%0A these a @@ -1299,17 +1299,16 @@ ven pote -%0A ntially @@ -1458,17 +1458,17 @@ x honest -%0A + and mali |
| json metadata | {"tags":["raiblocks","security","attack","settlement","byzantine"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #18721827/Trx d210bc73040b236b9014926efa3f4021b3849f8b |
View Raw JSON Data
{
"trx_id": "d210bc73040b236b9014926efa3f4021b3849f8b",
"block": 18721827,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-05T21:05:33",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "raiblocks",
"author": "selfdrivingsandp",
"permlink": "raiblocks-lack-of-settlement-finality",
"title": "Raiblocks Lack of Settlement Finality",
"body": "@@ -304,17 +304,16 @@\n e downsi\n-%0A\n de is th\n@@ -432,17 +432,16 @@\n he first\n-%0A\n major i\n@@ -659,17 +659,16 @@\n ccounts,\n-%0A\n negativ\n@@ -787,17 +787,16 @@\n dger and\n-%0A\n sacrifi\n@@ -1043,17 +1043,16 @@\n ombining\n-%0A\n these a\n@@ -1299,17 +1299,16 @@\n ven pote\n-%0A\n ntially \n@@ -1458,17 +1458,17 @@\n x honest\n-%0A\n+ \n and mali\n",
"json_metadata": "{\"tags\":[\"raiblocks\",\"security\",\"attack\",\"settlement\",\"byzantine\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}cryptohazardupvoted (100.00%) @selfdrivingsandp / raiblocks-lack-of-settlement-finality2018/01/05 18:32:03
cryptohazardupvoted (100.00%) @selfdrivingsandp / raiblocks-lack-of-settlement-finality
2018/01/05 18:32:03
| voter | cryptohazard |
| author | selfdrivingsandp |
| permlink | raiblocks-lack-of-settlement-finality |
| weight | 10000 (100.00%) |
| Transaction Info | Block #18718760/Trx ef3e7dca62034f23f367b3a794ab345cd51a34b1 |
View Raw JSON Data
{
"trx_id": "ef3e7dca62034f23f367b3a794ab345cd51a34b1",
"block": 18718760,
"trx_in_block": 33,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-05T18:32:03",
"op": [
"vote",
{
"voter": "cryptohazard",
"author": "selfdrivingsandp",
"permlink": "raiblocks-lack-of-settlement-finality",
"weight": 10000
}
]
}2018/01/05 18:32:00
2018/01/05 18:32:00
| parent author | selfdrivingsandp |
| parent permlink | raiblocks-lack-of-settlement-finality |
| author | cryptohazard |
| permlink | re-selfdrivingsandp-raiblocks-lack-of-settlement-finality-20180105t183158591z |
| title | |
| body | I view them as a PoS consensus. I haven't seen what was the interest of the DAG over a blockchain. |
| json metadata | {"tags":["raiblocks"],"app":"steemit/0.1"} |
| Transaction Info | Block #18718759/Trx 667f1472841abcf2fee497a134909a5b3ff30030 |
View Raw JSON Data
{
"trx_id": "667f1472841abcf2fee497a134909a5b3ff30030",
"block": 18718759,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-05T18:32:00",
"op": [
"comment",
{
"parent_author": "selfdrivingsandp",
"parent_permlink": "raiblocks-lack-of-settlement-finality",
"author": "cryptohazard",
"permlink": "re-selfdrivingsandp-raiblocks-lack-of-settlement-finality-20180105t183158591z",
"title": "",
"body": "I view them as a PoS consensus. I haven't seen what was the interest of the DAG over a blockchain.",
"json_metadata": "{\"tags\":[\"raiblocks\"],\"app\":\"steemit/0.1\"}"
}
]
}selfdrivingsandppublished a new post: raiblocks-lack-of-settlement-finality2018/01/05 15:26:42
selfdrivingsandppublished a new post: raiblocks-lack-of-settlement-finality
2018/01/05 15:26:42
| parent author | |
| parent permlink | raiblocks |
| author | selfdrivingsandp |
| permlink | raiblocks-lack-of-settlement-finality |
| title | Raiblocks Lack of Settlement Finality |
| body | @@ -35,16 +35,44 @@ y.%0A%0AThe +main issue is that only the receiver @@ -138,16 +138,19 @@ ction.%0A%0A +## What pro @@ -891,16 +891,44 @@ ality.%0A%0A +## Potential Attack Vector%0A%0A Combinin @@ -1518,9 +1518,898 @@ o decide - +.%0A%0A## Where to go from Here?%0A%0AIt's hard to ignore that Raiblocks made a design design to perform balance updates asynchronously. The fact that the balance itself is included in the sent transaction as a store of record is not explained. What makes this secure? Sure it might be fast though seems like a pretty important design decision to sacrifice performance for speed.%0A%0ABlockchains verify the ledger in each block and take 6 blocks to ensure to strange behavior (in Bitcoin).%0A%0A%0A### Have All Receivers Verify the Entire Ledger?%0A%0AThis hardly seems practical or possible. Especially since a receiver might not be online to confirm a transaction.%0A%0A### Go to epochs and have the ledger validated?%0A%0AThis would make Rablocks a blockchain and no longer a DAG.%0A%0A%0A%0AIn conclusion, Raiblocks seems to only be concerned in the whitepaper with double spends and not the balancing of the ledger itself . |
| json metadata | {"tags":["raiblocks","security","attack","settlement","byzantine"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #18715053/Trx 9a18116e0585f0fd406321370205eaa0cbb462d1 |
View Raw JSON Data
{
"trx_id": "9a18116e0585f0fd406321370205eaa0cbb462d1",
"block": 18715053,
"trx_in_block": 48,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-05T15:26:42",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "raiblocks",
"author": "selfdrivingsandp",
"permlink": "raiblocks-lack-of-settlement-finality",
"title": "Raiblocks Lack of Settlement Finality",
"body": "@@ -35,16 +35,44 @@\n y.%0A%0AThe \n+main issue is that only the \n receiver\n@@ -138,16 +138,19 @@\n ction.%0A%0A\n+## \n What pro\n@@ -891,16 +891,44 @@\n ality.%0A%0A\n+## Potential Attack Vector%0A%0A\n Combinin\n@@ -1518,9 +1518,898 @@\n o decide\n-\n \n+.%0A%0A## Where to go from Here?%0A%0AIt's hard to ignore that Raiblocks made a design design to perform balance updates asynchronously. The fact that the balance itself is included in the sent transaction as a store of record is not explained. What makes this secure? Sure it might be fast though seems like a pretty important design decision to sacrifice performance for speed.%0A%0ABlockchains verify the ledger in each block and take 6 blocks to ensure to strange behavior (in Bitcoin).%0A%0A%0A### Have All Receivers Verify the Entire Ledger?%0A%0AThis hardly seems practical or possible. Especially since a receiver might not be online to confirm a transaction.%0A%0A### Go to epochs and have the ledger validated?%0A%0AThis would make Rablocks a blockchain and no longer a DAG.%0A%0A%0A%0AIn conclusion, Raiblocks seems to only be concerned in the whitepaper with double spends and not the balancing of the ledger itself\n .\n",
"json_metadata": "{\"tags\":[\"raiblocks\",\"security\",\"attack\",\"settlement\",\"byzantine\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}2018/01/05 15:20:09
2018/01/05 15:20:09
| parent author | peterv |
| parent permlink | re-selfdrivingsandp-security-thoughts-on-raiblocks-20180105t121611368z |
| author | selfdrivingsandp |
| permlink | re-peterv-re-selfdrivingsandp-security-thoughts-on-raiblocks-20180105t152008800z |
| title | |
| body | I think this is a serious concern that needs to be fully addressed. What you described in combination with a denial of service attack could potentially allow someone to take advantage of the ledger due to the lack of settlement finality. I wrote up these concerns here https://steemit.com/raiblocks/@selfdrivingsandp/raiblocks-lack-of-settlement-finality |
| json metadata | {"tags":["raiblocks"],"links":["https://steemit.com/raiblocks/@selfdrivingsandp/raiblocks-lack-of-settlement-finality"],"app":"steemit/0.1"} |
| Transaction Info | Block #18714922/Trx d7d96baeedea81c2f8f613b96ae78de3436198d0 |
View Raw JSON Data
{
"trx_id": "d7d96baeedea81c2f8f613b96ae78de3436198d0",
"block": 18714922,
"trx_in_block": 21,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-05T15:20:09",
"op": [
"comment",
{
"parent_author": "peterv",
"parent_permlink": "re-selfdrivingsandp-security-thoughts-on-raiblocks-20180105t121611368z",
"author": "selfdrivingsandp",
"permlink": "re-peterv-re-selfdrivingsandp-security-thoughts-on-raiblocks-20180105t152008800z",
"title": "",
"body": "I think this is a serious concern that needs to be fully addressed. What you described in combination with a denial of service attack could potentially allow someone to take advantage of the ledger due to the lack of settlement finality.\n\nI wrote up these concerns here https://steemit.com/raiblocks/@selfdrivingsandp/raiblocks-lack-of-settlement-finality",
"json_metadata": "{\"tags\":[\"raiblocks\"],\"links\":[\"https://steemit.com/raiblocks/@selfdrivingsandp/raiblocks-lack-of-settlement-finality\"],\"app\":\"steemit/0.1\"}"
}
]
}2018/01/05 13:18:48
2018/01/05 13:18:48
| parent author | selfdrivingsandp |
| parent permlink | security-thoughts-on-raiblocks |
| author | peterv |
| permlink | re-selfdrivingsandp-security-thoughts-on-raiblocks-20180105t121611368z |
| title | |
| body | @@ -447,200 +447,223 @@ s I -can easily pick a representative that will never be online and my balance is therefore not represented in conflict votes. Basically this puts more power in the hands of others and thus decreas +self-representation which seems to be possible. If many wallets do this they become dead-end-streets when offline and all balances eventually routed to these will not be able to assert their voting power which reduc es d |
| json metadata | {"tags":["raiblocks"],"app":"steemit/0.1"} |
| Transaction Info | Block #18712496/Trx c40fd6424159f40f47d61951edf6d67299c88c5f |
View Raw JSON Data
{
"trx_id": "c40fd6424159f40f47d61951edf6d67299c88c5f",
"block": 18712496,
"trx_in_block": 13,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-05T13:18:48",
"op": [
"comment",
{
"parent_author": "selfdrivingsandp",
"parent_permlink": "security-thoughts-on-raiblocks",
"author": "peterv",
"permlink": "re-selfdrivingsandp-security-thoughts-on-raiblocks-20180105t121611368z",
"title": "",
"body": "@@ -447,200 +447,223 @@\n s I \n-can easily pick a representative that will never be online and my balance is therefore not represented in conflict votes. Basically this puts more power in the hands of others and thus decreas\n+self-representation which seems to be possible. If many wallets do this they become dead-end-streets when offline and all balances eventually routed to these will not be able to assert their voting power which reduc\n es d\n",
"json_metadata": "{\"tags\":[\"raiblocks\"],\"app\":\"steemit/0.1\"}"
}
]
}2018/01/05 13:08:36
2018/01/05 13:08:36
| parent author | selfdrivingsandp |
| parent permlink | security-thoughts-on-raiblocks |
| author | peterv |
| permlink | re-selfdrivingsandp-security-thoughts-on-raiblocks-20180105t121611368z |
| title | |
| body | @@ -423,8 +423,240 @@ sewhere. + Another issue is I can easily pick a representative that will never be online and my balance is therefore not represented in conflict votes. Basically this puts more power in the hands of others and thus decreases decentralization. |
| json metadata | {"tags":["raiblocks"],"app":"steemit/0.1"} |
| Transaction Info | Block #18712292/Trx 5b2e7a9f330d3d5dd265ca0adb0d70571d90fae3 |
View Raw JSON Data
{
"trx_id": "5b2e7a9f330d3d5dd265ca0adb0d70571d90fae3",
"block": 18712292,
"trx_in_block": 30,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-05T13:08:36",
"op": [
"comment",
{
"parent_author": "selfdrivingsandp",
"parent_permlink": "security-thoughts-on-raiblocks",
"author": "peterv",
"permlink": "re-selfdrivingsandp-security-thoughts-on-raiblocks-20180105t121611368z",
"title": "",
"body": "@@ -423,8 +423,240 @@\n sewhere.\n+ Another issue is I can easily pick a representative that will never be online and my balance is therefore not represented in conflict votes. Basically this puts more power in the hands of others and thus decreases decentralization.\n",
"json_metadata": "{\"tags\":[\"raiblocks\"],\"app\":\"steemit/0.1\"}"
}
]
}2018/01/05 12:16:12
2018/01/05 12:16:12
| parent author | selfdrivingsandp |
| parent permlink | security-thoughts-on-raiblocks |
| author | peterv |
| permlink | re-selfdrivingsandp-security-thoughts-on-raiblocks-20180105t121611368z |
| title | |
| body | Very much appreciated this post in the midst of the hype of this coin. I've played a bit with the wallets and functionally it's great to see XRB moving so fast without fees. I also changed my representative to a random one further down the list and this made me wonder how the default representative is selected. I think this is key to the security of the network and the team should expand on this in the whitepaper or elsewhere. |
| json metadata | {"tags":["raiblocks"],"app":"steemit/0.1"} |
| Transaction Info | Block #18711244/Trx 9a56c6d511e905fc6de4b1039ac3c7ac2922b2af |
View Raw JSON Data
{
"trx_id": "9a56c6d511e905fc6de4b1039ac3c7ac2922b2af",
"block": 18711244,
"trx_in_block": 48,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-05T12:16:12",
"op": [
"comment",
{
"parent_author": "selfdrivingsandp",
"parent_permlink": "security-thoughts-on-raiblocks",
"author": "peterv",
"permlink": "re-selfdrivingsandp-security-thoughts-on-raiblocks-20180105t121611368z",
"title": "",
"body": "Very much appreciated this post in the midst of the hype of this coin. I've played a bit with the wallets and functionally it's great to see XRB moving so fast without fees. I also changed my representative to a random one further down the list and this made me wonder how the default representative is selected. I think this is key to the security of the network and the team should expand on this in the whitepaper or elsewhere.",
"json_metadata": "{\"tags\":[\"raiblocks\"],\"app\":\"steemit/0.1\"}"
}
]
}petervupvoted (100.00%) @selfdrivingsandp / security-thoughts-on-raiblocks2018/01/04 17:00:48
petervupvoted (100.00%) @selfdrivingsandp / security-thoughts-on-raiblocks
2018/01/04 17:00:48
| voter | peterv |
| author | selfdrivingsandp |
| permlink | security-thoughts-on-raiblocks |
| weight | 10000 (100.00%) |
| Transaction Info | Block #18688147/Trx 77a9dd92567478187f5e6eae399f338a1efa27c3 |
View Raw JSON Data
{
"trx_id": "77a9dd92567478187f5e6eae399f338a1efa27c3",
"block": 18688147,
"trx_in_block": 14,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-04T17:00:48",
"op": [
"vote",
{
"voter": "peterv",
"author": "selfdrivingsandp",
"permlink": "security-thoughts-on-raiblocks",
"weight": 10000
}
]
}selfdrivingsandppublished a new post: raiblocks-lack-of-settlement-finality2018/01/04 16:17:12
selfdrivingsandppublished a new post: raiblocks-lack-of-settlement-finality
2018/01/04 16:17:12
| parent author | |
| parent permlink | raiblocks |
| author | selfdrivingsandp |
| permlink | raiblocks-lack-of-settlement-finality |
| title | Raiblocks Lack of Settlement Finality |
| body | Raiblocks lacks settlement finality. The receiver is responsible for the final signature to confirm a transaction. What problems could this lead to? Raiblocks acocunts manage their own blockchain in order to achieve asynchronous updates and the scaling efficiencies. The downsi de is that unless the receiver wallet is online, the sent transaction will never be acknowledged and verified. This is the first major issue of the lack of settlement finality. A transaction could be unconfirmed indefinitely. Raiblocks also places the balance in the send transaction. This means that given enough colluding sender and receiving accounts, negative balances can be hidden unless the entire ledger is verified. Though the protocol does not verify the entire ledger and sacrifices security for performance. This is the second issue of the lack of settlement finality. Combining the 2 issues aboves results in flight unconfirmed transactions and a loophole to exploit the actual balance. Combining these attack vectors with a well places denial of service attack against the network (to hide the propagation of the malicious send transactions and also to take down the representatives) makes for an attack vector to tamper with the ledger and even pote ntially rewriting the ledger. In the case of such an attack, how will it be determined who is the honest and malicious balances? An attacker could mix honest and malicious accounts to make it difficult to decide. |
| json metadata | {"tags":["raiblocks","security","attack","settlement","byzantine"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #18687276/Trx edf244e0d1d5e6a14088a4c6f67eb4d86747f958 |
View Raw JSON Data
{
"trx_id": "edf244e0d1d5e6a14088a4c6f67eb4d86747f958",
"block": 18687276,
"trx_in_block": 50,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-04T16:17:12",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "raiblocks",
"author": "selfdrivingsandp",
"permlink": "raiblocks-lack-of-settlement-finality",
"title": "Raiblocks Lack of Settlement Finality",
"body": "Raiblocks lacks settlement finality.\n\nThe receiver is responsible for the final signature to confirm a transaction.\n\nWhat problems could this lead to?\n\nRaiblocks acocunts manage their own blockchain in order to achieve asynchronous updates and the scaling efficiencies. The downsi\nde is that unless the receiver wallet is online, the sent transaction will never be acknowledged and verified. This is the first\n major issue of the lack of settlement finality. A transaction could be unconfirmed indefinitely.\n\nRaiblocks also places the balance in the send transaction. This means that given enough colluding sender and receiving accounts,\n negative balances can be hidden unless the entire ledger is verified. Though the protocol does not verify the entire ledger and\n sacrifices security for performance. This is the second issue of the lack of settlement finality.\n\nCombining the 2 issues aboves results in flight unconfirmed transactions and a loophole to exploit the actual balance. Combining\n these attack vectors with a well places denial of service attack against the network (to hide the propagation of the malicious send transactions and also to take down the representatives) makes for an attack vector to tamper with the ledger and even pote\nntially rewriting the ledger. \n\nIn the case of such an attack, how will it be determined who is the honest and malicious balances? An attacker could mix honest\nand malicious accounts to make it difficult to decide.",
"json_metadata": "{\"tags\":[\"raiblocks\",\"security\",\"attack\",\"settlement\",\"byzantine\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}selfdrivingsandppublished a new post: security-thoughts-on-raiblocks2018/01/02 06:34:18
selfdrivingsandppublished a new post: security-thoughts-on-raiblocks
2018/01/02 06:34:18
| parent author | |
| parent permlink | raiblocks |
| author | selfdrivingsandp |
| permlink | security-thoughts-on-raiblocks |
| title | Raiblocks Security Thoughts |
| body | @@ -148,16 +148,127 @@ urity?%0A%0A +**Potential %5BBalance attack%5D(https://steemit.com/raiblocks/@selfdrivingsandp/negative-balance-in-raiblocks)**%0A%0A Cliff no |
| json metadata | {"tags":["raiblocks","cryptocurrency","security","doublespend"],"links":["https://raiblocks.net/media/RaiBlocks_Whitepaper__English.pdf","https://steemit.com/raiblocks/@selfdrivingsandp/negative-balance-in-raiblocks","https://bitcoinist.com/exclusive-interview-raiblocks-team/"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #18618038/Trx 7f55600790c191b4b5979e95336091802fc216f8 |
View Raw JSON Data
{
"trx_id": "7f55600790c191b4b5979e95336091802fc216f8",
"block": 18618038,
"trx_in_block": 30,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-02T06:34:18",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "raiblocks",
"author": "selfdrivingsandp",
"permlink": "security-thoughts-on-raiblocks",
"title": "Raiblocks Security Thoughts",
"body": "@@ -148,16 +148,127 @@\n urity?%0A%0A\n+**Potential %5BBalance attack%5D(https://steemit.com/raiblocks/@selfdrivingsandp/negative-balance-in-raiblocks)**%0A%0A\n Cliff no\n",
"json_metadata": "{\"tags\":[\"raiblocks\",\"cryptocurrency\",\"security\",\"doublespend\"],\"links\":[\"https://raiblocks.net/media/RaiBlocks_Whitepaper__English.pdf\",\"https://steemit.com/raiblocks/@selfdrivingsandp/negative-balance-in-raiblocks\",\"https://bitcoinist.com/exclusive-interview-raiblocks-team/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}selfdrivingsandppublished a new post: negative-balance-in-raiblocks2018/01/02 00:13:36
selfdrivingsandppublished a new post: negative-balance-in-raiblocks
2018/01/02 00:13:36
| parent author | |
| parent permlink | raiblocks |
| author | selfdrivingsandp |
| permlink | negative-balance-in-raiblocks |
| title | Negative Balance in Raiblocks? |
| body | @@ -436,276 +436,8 @@ e.%0A%0A -It's also noted in the wiki %5BSince send blocks contain an account's balance, in order to calculate the balance from the block chain, only blocks up to the last send need to be kept.%5D(https://github.com/clemahieu/raiblocks/wiki/Design-features#lite-peers-and-pruning)%0A%0A So w @@ -1020,16 +1020,284 @@ m their balance? +%0A%0AIt's also noted in the wiki %5BSince send blocks contain an account's balance, in order to calculate the balance from the block chain, only blocks up to the last send need to be kept.%5D(https://github.com/clemahieu/raiblocks/wiki/Design-features#lite-peers-and-pruning) |
| json metadata | {"tags":["raiblocks","security","analysis","cryptocurrency","blockchain"],"app":"steemit/0.1","format":"markdown","links":["https://github.com/clemahieu/raiblocks/wiki/Design-features#lite-peers-and-pruning"]} |
| Transaction Info | Block #18610425/Trx 409d6916d3891ab38188e929e35c66ff6697be2b |
View Raw JSON Data
{
"trx_id": "409d6916d3891ab38188e929e35c66ff6697be2b",
"block": 18610425,
"trx_in_block": 40,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-02T00:13:36",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "raiblocks",
"author": "selfdrivingsandp",
"permlink": "negative-balance-in-raiblocks",
"title": "Negative Balance in Raiblocks?",
"body": "@@ -436,276 +436,8 @@\n e.%0A%0A\n-It's also noted in the wiki %5BSince send blocks contain an account's balance, in order to calculate the balance from the block chain, only blocks up to the last send need to be kept.%5D(https://github.com/clemahieu/raiblocks/wiki/Design-features#lite-peers-and-pruning)%0A%0A\n So w\n@@ -1020,16 +1020,284 @@\n m their balance?\n+%0A%0AIt's also noted in the wiki %5BSince send blocks contain an account's balance, in order to calculate the balance from the block chain, only blocks up to the last send need to be kept.%5D(https://github.com/clemahieu/raiblocks/wiki/Design-features#lite-peers-and-pruning)\n",
"json_metadata": "{\"tags\":[\"raiblocks\",\"security\",\"analysis\",\"cryptocurrency\",\"blockchain\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\",\"links\":[\"https://github.com/clemahieu/raiblocks/wiki/Design-features#lite-peers-and-pruning\"]}"
}
]
}selfdrivingsandppublished a new post: negative-balance-in-raiblocks2018/01/02 00:11:54
selfdrivingsandppublished a new post: negative-balance-in-raiblocks
2018/01/02 00:11:54
| parent author | |
| parent permlink | raiblocks |
| author | selfdrivingsandp |
| permlink | negative-balance-in-raiblocks |
| title | Negative Balance in Raiblocks? |
| body | @@ -432,16 +432,371 @@ llude.%0A%0A +It's also noted in the wiki %5BSince send blocks contain an account's balance, in order to calculate the balance from the block chain, only blocks up to the last send need to be kept.%5D(https://github.com/clemahieu/raiblocks/wiki/Design-features#lite-peers-and-pruning)%0A%0ASo why wouldn't the sender and receiver collude and the sender falsifies the balance?%0A%0A So what |
| json metadata | {"tags":["raiblocks","security","analysis","cryptocurrency","blockchain"],"app":"steemit/0.1","format":"markdown","links":["https://github.com/clemahieu/raiblocks/wiki/Design-features#lite-peers-and-pruning"]} |
| Transaction Info | Block #18610391/Trx 0ad4d3efec7758444ceed0b5e9dcb127be5f3dc5 |
View Raw JSON Data
{
"trx_id": "0ad4d3efec7758444ceed0b5e9dcb127be5f3dc5",
"block": 18610391,
"trx_in_block": 10,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-02T00:11:54",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "raiblocks",
"author": "selfdrivingsandp",
"permlink": "negative-balance-in-raiblocks",
"title": "Negative Balance in Raiblocks?",
"body": "@@ -432,16 +432,371 @@\n llude.%0A%0A\n+It's also noted in the wiki %5BSince send blocks contain an account's balance, in order to calculate the balance from the block chain, only blocks up to the last send need to be kept.%5D(https://github.com/clemahieu/raiblocks/wiki/Design-features#lite-peers-and-pruning)%0A%0ASo why wouldn't the sender and receiver collude and the sender falsifies the balance?%0A%0A\n So what \n",
"json_metadata": "{\"tags\":[\"raiblocks\",\"security\",\"analysis\",\"cryptocurrency\",\"blockchain\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\",\"links\":[\"https://github.com/clemahieu/raiblocks/wiki/Design-features#lite-peers-and-pruning\"]}"
}
]
}selfdrivingsandppublished a new post: negative-balance-in-raiblocks2018/01/02 00:02:54
selfdrivingsandppublished a new post: negative-balance-in-raiblocks
2018/01/02 00:02:54
| parent author | |
| parent permlink | raiblocks |
| author | selfdrivingsandp |
| permlink | negative-balance-in-raiblocks |
| title | Negative Balance in Raiblocks? |
| body | It seems that it's possible to have a spender with negative balance or even incorrect balance? The whitepaper doesn't clarify how the following ledger attack is prevented? How exactly is the balance of a Raiblocks account verified? Who verifies that balances are not negative? Is it the representatives that somehow should be monitoring all transactions? It shouldn't just be the receiver, since the sender and receiver might collude. So what happens when a negative balance is detected? How would the network reject this? The whitepaper mentions that the sender is allowed to modify their own chain. So what happens when the sender spends coins they don't have? The whitepaper only mentions "If it is a send block, the balance must be less than the previous balance". Also, who makes sure that the sender decrements the spent coins correctly? What prevents the sender from sending 10 coins though only subtracting 1 coin from their balance? |
| json metadata | {"tags":["raiblocks","security","analysis","cryptocurrency","blockchain"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #18610211/Trx 052a4ed1ddb349d8476e29389d3925c8449f57ff |
View Raw JSON Data
{
"trx_id": "052a4ed1ddb349d8476e29389d3925c8449f57ff",
"block": 18610211,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-02T00:02:54",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "raiblocks",
"author": "selfdrivingsandp",
"permlink": "negative-balance-in-raiblocks",
"title": "Negative Balance in Raiblocks?",
"body": "It seems that it's possible to have a spender with negative balance or even incorrect balance? The whitepaper doesn't clarify how the following ledger attack is prevented?\n\nHow exactly is the balance of a Raiblocks account verified?\n\nWho verifies that balances are not negative? Is it the representatives that somehow should be monitoring all transactions?\n\nIt shouldn't just be the receiver, since the sender and receiver might collude.\n\nSo what happens when a negative balance is detected? How would the network reject this?\n\nThe whitepaper mentions that the sender is allowed to modify their own chain. So what happens when the sender spends coins they don't have?\n\nThe whitepaper only mentions \"If it is a send block, the balance must be less than the previous balance\".\n\nAlso, who makes sure that the sender decrements the spent coins correctly? What prevents the sender from sending 10 coins though only subtracting 1 coin from their balance?",
"json_metadata": "{\"tags\":[\"raiblocks\",\"security\",\"analysis\",\"cryptocurrency\",\"blockchain\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}selfdrivingsandppublished a new post: security-thoughts-on-raiblocks2018/01/01 01:29:06
selfdrivingsandppublished a new post: security-thoughts-on-raiblocks
2018/01/01 01:29:06
| parent author | |
| parent permlink | raiblocks |
| author | selfdrivingsandp |
| permlink | security-thoughts-on-raiblocks |
| title | Raiblocks Security Thoughts |
| body | @@ -6304,16 +6304,268 @@ well.%0A%0A +Prediction we will see several large scale denial of service attacks attempted. Attacker will have the opport%0Aunity to affect the price and make serious money.%0A%0ATo execute an attack either a large mining pool or a cloud service can be rented for cheap. %0A%0A%0A# Oth |
| json metadata | {"tags":["raiblocks","cryptocurrency","security","doublespend"],"links":["https://raiblocks.net/media/RaiBlocks_Whitepaper__English.pdf","https://bitcoinist.com/exclusive-interview-raiblocks-team/"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #18583366/Trx eb24ccfab12ba3c9f4b76812ceae8d3bf93655e7 |
View Raw JSON Data
{
"trx_id": "eb24ccfab12ba3c9f4b76812ceae8d3bf93655e7",
"block": 18583366,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-01T01:29:06",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "raiblocks",
"author": "selfdrivingsandp",
"permlink": "security-thoughts-on-raiblocks",
"title": "Raiblocks Security Thoughts",
"body": "@@ -6304,16 +6304,268 @@\n well.%0A%0A\n+Prediction we will see several large scale denial of service attacks attempted. Attacker will have the opport%0Aunity to affect the price and make serious money.%0A%0ATo execute an attack either a large mining pool or a cloud service can be rented for cheap.\n %0A%0A%0A# Oth\n",
"json_metadata": "{\"tags\":[\"raiblocks\",\"cryptocurrency\",\"security\",\"doublespend\"],\"links\":[\"https://raiblocks.net/media/RaiBlocks_Whitepaper__English.pdf\",\"https://bitcoinist.com/exclusive-interview-raiblocks-team/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}selfdrivingsandppublished a new post: security-thoughts-on-raiblocks2017/12/31 13:46:54
selfdrivingsandppublished a new post: security-thoughts-on-raiblocks
2017/12/31 13:46:54
| parent author | |
| parent permlink | raiblocks |
| author | selfdrivingsandp |
| permlink | security-thoughts-on-raiblocks |
| title | Raiblocks Security Thoughts |
| body | @@ -5669,17 +5669,16 @@ ccur, es -%0A pecially @@ -5954,17 +5954,16 @@ ot spend -%0A their c @@ -6105,17 +6105,16 @@ . If the -%0A represe @@ -6257,17 +6257,16 @@ for atta -%0A cking th @@ -6305,16 +6305,18 @@ well.%0A%0A%0A +%0A%0A # Other |
| json metadata | {"tags":["raiblocks","cryptocurrency","security","doublespend"],"links":["https://raiblocks.net/media/RaiBlocks_Whitepaper__English.pdf","https://bitcoinist.com/exclusive-interview-raiblocks-team/"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #18569323/Trx 79f5384ffb606463c26624996f7ab675ca7fc167 |
View Raw JSON Data
{
"trx_id": "79f5384ffb606463c26624996f7ab675ca7fc167",
"block": 18569323,
"trx_in_block": 41,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-31T13:46:54",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "raiblocks",
"author": "selfdrivingsandp",
"permlink": "security-thoughts-on-raiblocks",
"title": "Raiblocks Security Thoughts",
"body": "@@ -5669,17 +5669,16 @@\n ccur, es\n-%0A\n pecially\n@@ -5954,17 +5954,16 @@\n ot spend\n-%0A\n their c\n@@ -6105,17 +6105,16 @@\n . If the\n-%0A\n represe\n@@ -6257,17 +6257,16 @@\n for atta\n-%0A\n cking th\n@@ -6305,16 +6305,18 @@\n well.%0A%0A%0A\n+%0A%0A\n # Other \n",
"json_metadata": "{\"tags\":[\"raiblocks\",\"cryptocurrency\",\"security\",\"doublespend\"],\"links\":[\"https://raiblocks.net/media/RaiBlocks_Whitepaper__English.pdf\",\"https://bitcoinist.com/exclusive-interview-raiblocks-team/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}selfdrivingsandppublished a new post: security-thoughts-on-raiblocks2017/12/31 13:46:00
selfdrivingsandppublished a new post: security-thoughts-on-raiblocks
2017/12/31 13:46:00
| parent author | |
| parent permlink | raiblocks |
| author | selfdrivingsandp |
| permlink | security-thoughts-on-raiblocks |
| title | Raiblocks Security Thoughts |
| body | @@ -5439,16 +5439,883 @@ acked.%0A%0A +## Incentives and Coin Distribution%0A%0AThird, incentives and coin distribution.%0A%0AThe protocol does not provide any rewards for running a node. Who will provide and run the nodes? We would expect a type of centralization to occur, es%0Apecially as the number of transactions increases with network usage.%0A%0AFurthermore, the number of coins has already been distributed.%0A%0AAs the security relies on a type of delegated proof of stake, the question arises of what financial incentives do the representatives have to not spend%0A their coins? Either the representatives hold their coins (meaning they are not able to spend their wealth) or they spend their coins over time. If the%0A representatives spend their coins over time, we would expect the coins to be distributed to multiple account holders. This means the threshold for atta%0Acking the system decreases over time as well. %0A%0A%0A# Oth |
| json metadata | {"tags":["raiblocks","cryptocurrency","security","doublespend"],"links":["https://raiblocks.net/media/RaiBlocks_Whitepaper__English.pdf","https://bitcoinist.com/exclusive-interview-raiblocks-team/"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #18569305/Trx 3e1e7fe454f4defbdda4da74a4cc9c64deb21e3d |
View Raw JSON Data
{
"trx_id": "3e1e7fe454f4defbdda4da74a4cc9c64deb21e3d",
"block": 18569305,
"trx_in_block": 40,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-31T13:46:00",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "raiblocks",
"author": "selfdrivingsandp",
"permlink": "security-thoughts-on-raiblocks",
"title": "Raiblocks Security Thoughts",
"body": "@@ -5439,16 +5439,883 @@\n acked.%0A%0A\n+## Incentives and Coin Distribution%0A%0AThird, incentives and coin distribution.%0A%0AThe protocol does not provide any rewards for running a node. Who will provide and run the nodes? We would expect a type of centralization to occur, es%0Apecially as the number of transactions increases with network usage.%0A%0AFurthermore, the number of coins has already been distributed.%0A%0AAs the security relies on a type of delegated proof of stake, the question arises of what financial incentives do the representatives have to not spend%0A their coins? Either the representatives hold their coins (meaning they are not able to spend their wealth) or they spend their coins over time. If the%0A representatives spend their coins over time, we would expect the coins to be distributed to multiple account holders. This means the threshold for atta%0Acking the system decreases over time as well.\n %0A%0A%0A# Oth\n",
"json_metadata": "{\"tags\":[\"raiblocks\",\"cryptocurrency\",\"security\",\"doublespend\"],\"links\":[\"https://raiblocks.net/media/RaiBlocks_Whitepaper__English.pdf\",\"https://bitcoinist.com/exclusive-interview-raiblocks-team/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}selfdrivingsandpupvoted (100.00%) @selfdrivingsandp / security-thoughts-on-raiblocks2017/12/28 16:00:06
selfdrivingsandpupvoted (100.00%) @selfdrivingsandp / security-thoughts-on-raiblocks
2017/12/28 16:00:06
| voter | selfdrivingsandp |
| author | selfdrivingsandp |
| permlink | security-thoughts-on-raiblocks |
| weight | 10000 (100.00%) |
| Transaction Info | Block #18485605/Trx d4bb3bd8c1e2c67dccceec6af964b4f7dc1e3b5c |
View Raw JSON Data
{
"trx_id": "d4bb3bd8c1e2c67dccceec6af964b4f7dc1e3b5c",
"block": 18485605,
"trx_in_block": 14,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-28T16:00:06",
"op": [
"vote",
{
"voter": "selfdrivingsandp",
"author": "selfdrivingsandp",
"permlink": "security-thoughts-on-raiblocks",
"weight": 10000
}
]
}selfdrivingsandppublished a new post: security-thoughts-on-raiblocks2017/12/28 15:59:12
selfdrivingsandppublished a new post: security-thoughts-on-raiblocks
2017/12/28 15:59:12
| parent author | |
| parent permlink | raiblocks |
| author | selfdrivingsandp |
| permlink | security-thoughts-on-raiblocks |
| title | Raiblocks Security Thoughts |
| body | @@ -1218,17 +1218,17 @@ nd attac -h +k . It sho |
| json metadata | {"tags":["raiblocks","cryptocurrency","security","doublespend"],"links":["https://raiblocks.net/media/RaiBlocks_Whitepaper__English.pdf","https://bitcoinist.com/exclusive-interview-raiblocks-team/"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #18485587/Trx c76564f09c736ec5bea85a6f71233767438ad2f2 |
View Raw JSON Data
{
"trx_id": "c76564f09c736ec5bea85a6f71233767438ad2f2",
"block": 18485587,
"trx_in_block": 16,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-28T15:59:12",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "raiblocks",
"author": "selfdrivingsandp",
"permlink": "security-thoughts-on-raiblocks",
"title": "Raiblocks Security Thoughts",
"body": "@@ -1218,17 +1218,17 @@\n nd attac\n-h\n+k\n . It sho\n",
"json_metadata": "{\"tags\":[\"raiblocks\",\"cryptocurrency\",\"security\",\"doublespend\"],\"links\":[\"https://raiblocks.net/media/RaiBlocks_Whitepaper__English.pdf\",\"https://bitcoinist.com/exclusive-interview-raiblocks-team/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}selfdrivingsandppublished a new post: security-thoughts-on-raiblocks2017/12/28 15:57:12
selfdrivingsandppublished a new post: security-thoughts-on-raiblocks
2017/12/28 15:57:12
| parent author | |
| parent permlink | raiblocks |
| author | selfdrivingsandp |
| permlink | security-thoughts-on-raiblocks |
| title | Raiblocks Security Thoughts |
| body | @@ -148,16 +148,311 @@ urity?%0A%0A +Cliff notes - there isn't sufficient information to claim that Raiblocks is as robust against double spend attacks compared to blockchains such as Bitcoin's proof of work or Peercoin's proof of stake. There are hidden trust assumptions that users of Raiblocks must accept upon using Raiblocks.%0A%0A # Double |
| json metadata | {"tags":["raiblocks","cryptocurrency","security","doublespend"],"links":["https://raiblocks.net/media/RaiBlocks_Whitepaper__English.pdf","https://bitcoinist.com/exclusive-interview-raiblocks-team/"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #18485547/Trx f8b815b86eaace2a23b989c5a039c541bf52be1b |
View Raw JSON Data
{
"trx_id": "f8b815b86eaace2a23b989c5a039c541bf52be1b",
"block": 18485547,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-28T15:57:12",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "raiblocks",
"author": "selfdrivingsandp",
"permlink": "security-thoughts-on-raiblocks",
"title": "Raiblocks Security Thoughts",
"body": "@@ -148,16 +148,311 @@\n urity?%0A%0A\n+Cliff notes - there isn't sufficient information to claim that Raiblocks is as robust against double spend attacks compared to blockchains such as Bitcoin's proof of work or Peercoin's proof of stake. There are hidden trust assumptions that users of Raiblocks must accept upon using Raiblocks.%0A%0A\n # Double\n",
"json_metadata": "{\"tags\":[\"raiblocks\",\"cryptocurrency\",\"security\",\"doublespend\"],\"links\":[\"https://raiblocks.net/media/RaiBlocks_Whitepaper__English.pdf\",\"https://bitcoinist.com/exclusive-interview-raiblocks-team/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}selfdrivingsandppublished a new post: security-thoughts-on-raiblocks2017/12/28 15:54:24
selfdrivingsandppublished a new post: security-thoughts-on-raiblocks
2017/12/28 15:54:24
| parent author | |
| parent permlink | raiblocks |
| author | selfdrivingsandp |
| permlink | security-thoughts-on-raiblocks |
| title | Raiblocks Security Thoughts |
| body | @@ -1963,16 +1963,18 @@ %0A%0A%0Apg 7 +%5B%22 Block In @@ -2170,18 +2170,19 @@ stantly. -%0A%0A +%22%5D( https:// @@ -2234,16 +2234,18 @@ lish.pdf +)%0A %0A%0A%0A%5B%22We |
| json metadata | {"tags":["raiblocks","cryptocurrency","security","doublespend"],"links":["https://raiblocks.net/media/RaiBlocks_Whitepaper__English.pdf","https://bitcoinist.com/exclusive-interview-raiblocks-team/"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #18485491/Trx 09529db2ad52d712ea5fdd82765932cc21c20020 |
View Raw JSON Data
{
"trx_id": "09529db2ad52d712ea5fdd82765932cc21c20020",
"block": 18485491,
"trx_in_block": 27,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-28T15:54:24",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "raiblocks",
"author": "selfdrivingsandp",
"permlink": "security-thoughts-on-raiblocks",
"title": "Raiblocks Security Thoughts",
"body": "@@ -1963,16 +1963,18 @@\n %0A%0A%0Apg 7 \n+%5B%22\n Block In\n@@ -2170,18 +2170,19 @@\n stantly.\n-%0A%0A\n+%22%5D(\n https://\n@@ -2234,16 +2234,18 @@\n lish.pdf\n+)%0A\n %0A%0A%0A%5B%22We \n",
"json_metadata": "{\"tags\":[\"raiblocks\",\"cryptocurrency\",\"security\",\"doublespend\"],\"links\":[\"https://raiblocks.net/media/RaiBlocks_Whitepaper__English.pdf\",\"https://bitcoinist.com/exclusive-interview-raiblocks-team/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}selfdrivingsandppublished a new post: security-thoughts-on-raiblocks2017/12/28 15:53:27
selfdrivingsandppublished a new post: security-thoughts-on-raiblocks
2017/12/28 15:53:27
| parent author | |
| parent permlink | raiblocks |
| author | selfdrivingsandp |
| permlink | security-thoughts-on-raiblocks |
| title | Raiblocks Security Thoughts |
| body | Raiblocks promises ["unlimited scalability and no transaction fees"](https://raiblocks.net/media/RaiBlocks_Whitepaper__English.pdf). What about security? # Double Spend Background Fundamentally, the double spend problem must be addressed in any payment infrastructure. The system topology increases the difficulty of solving and adequately addressing the double spend problem. Centralized systems which rely on a payment processor achieve high scalability though require strong trust assumptions. Decentralized or distributed systems must address a further spectrum of issues, namely those revolving around byzantine agreement. Bitcoin gave a probabilistic solution to the Byzantine agreement problem by the introduction of a proof of work system that dynamically increases the difficulty. An adversary must control greater than 51% of the hash power for a period of time in order to successfully execute a double spend attach. It should be noted that if a double spend attack was executed, the entire network would be aware, as Bitcoin is a peer to peer network where transactions are broadcasted and propagated across the network. Peercoin pioneered proof of stake. Rather than relying on proof of work to secure the network, Peercoin's proof of stake security guarantees hold as long as the adversary does not control 51% or more of the networks stake for a period of time. Such a stake attack more expensive than a proof of work attack. In addition, proof of stake has lower energy requirements compared to proof of work. # Raiblocks Security Claims Now, let's take a look first at how the "unlimited scalability" claim is made in Raiblocks and what type of security properties we can expect. ## Double Spend Prevention Claim First, let's examine what is a Raiblock and the novel "block-lattice" structure and see if in fact all that's required to solve the byzantine agreement problem is a novel data structure (and no new consensus algorithms). pg 7 Block Interval: Since each account has its own blockchain, updates can be performed asynchronous to the state of network. Therefore there are no block intervals and transactions can be published instantly. https://raiblocks.net/media/RaiBlocks_Whitepaper__English.pdf ["We really only need to have transactions for an account ordered with respect to other transactions in the same account and since only one account is involved we don’t need network agreement so proof of work is unnecessary."](https://bitcoinist.com/exclusive-interview-raiblocks-team/) ["The only agreement remaining is handling misbehaved clients that try to double spend, which in our system is called creating a fork. We use a weighted vote system to pick only one branch of a fork. This means in the usual case of a well behaved peer your transactions complete instantly without a vote and only the peer is misbehaving are its transactions subject to the slower voting."](https://bitcoinist.com/exclusive-interview-raiblocks-team/) Let's summarise the design so far. Basically, as long as the network functions honestly, well we can expect no double spends. Ok, how about protecting against double spends? A weighted vote system is used. What exactly are the network requirements for a representative? pg 7 ["Representative: A representative node requires maximum network resources as it observes vote traffic from other representatives and publishes its own votes."](https://raiblocks.net/media/RaiBlocks_Whitepaper__English.pdf) Who exactly can be a representative? pg 6 ["Account holders who are unable to reliably participate in voting for connectivity reasons can name a representative who can vote with the weight of their balance. "](https://raiblocks.net/media/RaiBlocks_Whitepaper__English.pdf) Not clear on how someone decides which representative to choose and how the selection process should be carried out? However, it's clear that by consolidating the voting power to those network powerful nodes Raiblocks is not distributed and borders on being centralized, or at least controlled by a handful of nodes. It is NOT peer to peer. Why is this an issue? As the paper points out, consolidating the voting power amongst a few opens the door to denial of service attacks. However, the paper handwaves regarding potential numbers of actual stake required. Without knowing the real distribution of Raiblocks and the allocation and voting distribution of representatives, the number can't be clearly specified. Is this a concern? For someone that cares about targeted security attacks, yes. ## Free Transactions Second, transaction fees. The paper mentions no transaction fees as a positive point. However, are no transaction fees really advantageous for security? Raiblocks relies on a minimal proof of work before sending each transaction, it claims similar to Hashcash. However, from an attacker's perspective having to spend the cryptocurrency's money as opposed to using cheap electricity to generate PoW, the spent transaction fee will mitigate and defer transaction spam more than PoW. The spent transaction fee requires a stake in the network being attacked. # Other concerns ## C++ Codebase "Raiblocks code is totally new and completely built from scratch" (in C++) Maybe the bug bounty can help with this. ## Exchanges What's the point of no transaction fees when exchanges charge 20% fees and require minimum balances for withdrawal? |
| json metadata | {"tags":["raiblocks","cryptocurrency","security","doublespend"],"links":["https://raiblocks.net/media/RaiBlocks_Whitepaper__English.pdf","https://bitcoinist.com/exclusive-interview-raiblocks-team/"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #18485472/Trx 5ea5cb8d2d795175d950bf2dd40d7290c99061e4 |
View Raw JSON Data
{
"trx_id": "5ea5cb8d2d795175d950bf2dd40d7290c99061e4",
"block": 18485472,
"trx_in_block": 60,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-28T15:53:27",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "raiblocks",
"author": "selfdrivingsandp",
"permlink": "security-thoughts-on-raiblocks",
"title": "Raiblocks Security Thoughts",
"body": "Raiblocks promises [\"unlimited scalability and no transaction fees\"](https://raiblocks.net/media/RaiBlocks_Whitepaper__English.pdf). What about security?\n\n# Double Spend Background\n\nFundamentally, the double spend problem must be addressed in any payment infrastructure. The system topology increases the difficulty of solving and adequately addressing the double spend problem.\n\nCentralized systems which rely on a payment processor achieve high scalability though require strong trust assumptions.\n\nDecentralized or distributed systems must address a further spectrum of issues, namely those revolving around byzantine agreement.\n\nBitcoin gave a probabilistic solution to the Byzantine agreement problem by the introduction of a proof of work system that dynamically increases the difficulty. An adversary must control greater than 51% of the hash power for a period of time in order to successfully execute a double spend attach. It should be noted that if a double spend attack was executed, the entire network would be aware, as Bitcoin is a peer to peer network where transactions are broadcasted and propagated across the network.\n\nPeercoin pioneered proof of stake. Rather than relying on proof of work to secure the network, Peercoin's proof of stake security guarantees hold as long as the adversary does not control 51% or more of the networks stake for a period of time. Such a stake attack more expensive than a proof of work attack. In addition, proof of stake has lower energy requirements compared to proof of work.\n\n\n\n# Raiblocks Security Claims\n\nNow, let's take a look first at how the \"unlimited scalability\" claim is made in Raiblocks and what type of security properties we can expect.\n\n## Double Spend Prevention Claim\n\nFirst, let's examine what is a Raiblock and the novel \"block-lattice\" structure and see if in fact all that's required to solve the byzantine agreement problem is a novel data structure (and no new consensus algorithms).\n\n\npg 7 Block Interval: Since each account has its own blockchain, updates can be performed asynchronous to the state of network. Therefore there are no block intervals and transactions can be published instantly.\n\nhttps://raiblocks.net/media/RaiBlocks_Whitepaper__English.pdf\n\n\n[\"We really only need to have transactions for an account ordered with respect to other transactions in the same account and since only one account is involved we don’t need network agreement so proof of work is unnecessary.\"](https://bitcoinist.com/exclusive-interview-raiblocks-team/)\n\n\n[\"The only agreement remaining is handling misbehaved clients that try to double spend, which in our system is called creating a fork. We use a weighted vote system to pick only one branch of a fork.\nThis means in the usual case of a well behaved peer your transactions complete instantly without a vote and only the peer is misbehaving are its transactions subject to the slower voting.\"](https://bitcoinist.com/exclusive-interview-raiblocks-team/)\n\n\n\n\nLet's summarise the design so far. \n\nBasically, as long as the network functions honestly, well we can expect no double spends. Ok, how about protecting against double spends?\n\n\nA weighted vote system is used. What exactly are the network requirements for a representative?\n\npg 7 [\"Representative: A representative node requires maximum network resources as it observes vote traffic from other representatives and publishes its own votes.\"](https://raiblocks.net/media/RaiBlocks_Whitepaper__English.pdf)\n\nWho exactly can be a representative?\n\npg 6 [\"Account holders who are unable to reliably participate in voting for connectivity reasons can name a representative who can vote with the weight of their balance. \"](https://raiblocks.net/media/RaiBlocks_Whitepaper__English.pdf)\n\nNot clear on how someone decides which representative to choose and how the selection process should be carried out?\n\nHowever, it's clear that by consolidating the voting power to those network powerful nodes Raiblocks is not distributed and borders on being centralized, or at least controlled by a handful of nodes. It is NOT peer to peer.\n\nWhy is this an issue?\n\nAs the paper points out, consolidating the voting power amongst a few opens the door to denial of service attacks. However, the paper handwaves regarding potential numbers of actual stake required. Without knowing the real distribution of Raiblocks and the allocation and voting distribution of representatives, the number can't be clearly specified.\n\nIs this a concern?\n\nFor someone that cares about targeted security attacks, yes.\n\n\n\n## Free Transactions\nSecond, transaction fees.\n\nThe paper mentions no transaction fees as a positive point. However, are no transaction fees really advantageous for security?\n\nRaiblocks relies on a minimal proof of work before sending each transaction, it claims similar to Hashcash.\n\nHowever, from an attacker's perspective having to spend the cryptocurrency's money as opposed to using cheap electricity to generate PoW, the spent transaction fee will mitigate and defer transaction spam more than PoW. The spent transaction fee requires a stake in the network being attacked.\n\n\n\n\n# Other concerns\n\n## C++ Codebase\n\n\"Raiblocks code is totally new and completely built from scratch\" (in C++)\n\nMaybe the bug bounty can help with this.\n\n\n## Exchanges\n\nWhat's the point of no transaction fees when exchanges charge 20% fees and require minimum balances for withdrawal?",
"json_metadata": "{\"tags\":[\"raiblocks\",\"cryptocurrency\",\"security\",\"doublespend\"],\"links\":[\"https://raiblocks.net/media/RaiBlocks_Whitepaper__English.pdf\",\"https://bitcoinist.com/exclusive-interview-raiblocks-team/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}selfdrivingsandppublished a new post: security-thoughts-on-raiblocks2017/12/28 15:52:39
selfdrivingsandppublished a new post: security-thoughts-on-raiblocks
2017/12/28 15:52:39
| parent author | |
| parent permlink | raiblocks |
| author | selfdrivingsandp |
| permlink | security-thoughts-on-raiblocks |
| title | Security thoughts on Raiblocks |
| body | Raiblocks promises ["unlimited scalability and no transaction fees"](https://raiblocks.net/media/RaiBlocks_Whitepaper__English.pdf). What about security? # Double Spend Background Fundamentally, the double spend problem must be addressed in any payment infrastructure. The system topology increases the difficulty of solving and adequately addressing the double spend problem. Centralized systems which rely on a payment processor achieve high scalability though require strong trust assumptions. Decentralized or distributed systems must address a further spectrum of issues, namely those revolving around byzantine agreement. Bitcoin gave a probabilistic solution to the Byzantine agreement problem by the introduction of a proof of work system that dynamically increases the difficulty. An adversary must control greater than 51% of the hash power for a period of time in order to successfully execute a double spend attach. It should be noted that if a double spend attack was executed, the entire network would be aware, as Bitcoin is a peer to peer network where transactions are broadcasted and propagated across the network. Peercoin pioneered proof of stake. Rather than relying on proof of work to secure the network, Peercoin's proof of stake security guarantees hold as long as the adversary does not control 51% or more of the networks stake for a period of time. Such a stake attack more expensive than a proof of work attack. In addition, proof of stake has lower energy requirements compared to proof of work. # Raiblocks Security Claims Now, let's take a look first at how the "unlimited scalability" claim is made in Raiblocks and what type of security properties we can expect. ## Double Spend Prevention Claim First, let's examine what is a Raiblock and the novel "block-lattice" structure and see if in fact all that's required to solve the byzantine agreement problem is a novel data structure (and no new consensus algorithms). pg 7 Block Interval: Since each account has its own blockchain, updates can be performed asynchronous to the state of network. Therefore there are no block intervals and transactions can be published instantly. https://raiblocks.net/media/RaiBlocks_Whitepaper__English.pdf ["We really only need to have transactions for an account ordered with respect to other transactions in the same account and since only one account is involved we don’t need network agreement so proof of work is unnecessary."](https://bitcoinist.com/exclusive-interview-raiblocks-team/) ["The only agreement remaining is handling misbehaved clients that try to double spend, which in our system is called creating a fork. We use a weighted vote system to pick only one branch of a fork. This means in the usual case of a well behaved peer your transactions complete instantly without a vote and only the peer is misbehaving are its transactions subject to the slower voting."](https://bitcoinist.com/exclusive-interview-raiblocks-team/) Let's summarise the design so far. Basically, as long as the network functions honestly, well we can expect no double spends. Ok, how about protecting against double spends? A weighted vote system is used. What exactly are the network requirements for a representative? pg 7 ["Representative: A representative node requires maximum network resources as it observes vote traffic from other representatives and publishes its own votes."](https://raiblocks.net/media/RaiBlocks_Whitepaper__English.pdf) Who exactly can be a representative? pg 6 ["Account holders who are unable to reliably participate in voting for connectivity reasons can name a representative who can vote with the weight of their balance. "](https://raiblocks.net/media/RaiBlocks_Whitepaper__English.pdf) Not clear on how someone decides which representative to choose and how the selection process should be carried out? However, it's clear that by consolidating the voting power to those network powerful nodes Raiblocks is not distributed and borders on being centralized, or at least controlled by a handful of nodes. It is NOT peer to peer. Why is this an issue? As the paper points out, consolidating the voting power amongst a few opens the door to denial of service attacks. However, the paper handwaves regarding potential numbers of actual stake required. Without knowing the real distribution of Raiblocks and the allocation and voting distribution of representatives, the number can't be clearly specified. Is this a concern? For someone that cares about targeted security attacks, yes. ## Free Transactions Second, transaction fees. The paper mentions no transaction fees as a positive point. However, are no transaction fees really advantageous for security? Raiblocks relies on a minimal proof of work before sending each transaction, it claims similar to Hashcash. However, from an attacker's perspective having to spend the cryptocurrency's money as opposed to using cheap electricity to generate PoW, the spent transaction fee will mitigate and defer transaction spam more than PoW. The spent transaction fee requires a stake in the network being attacked. # Other concerns ## C++ Codebase "Raiblocks code is totally new and completely built from scratch" (in C++) Maybe the bug bounty can help with this. ## Exchanges What's the point of no transaction fees when exchanges charge 20% fees and require minimum balances for withdrawal? |
| json metadata | {"tags":["raiblocks","cryptocurrency","security","doublespend"],"links":["https://raiblocks.net/media/RaiBlocks_Whitepaper__English.pdf","https://bitcoinist.com/exclusive-interview-raiblocks-team/"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #18485456/Trx 6ddbe6d221eb6aac8c829d14c3ea51c2866ad0d7 |
View Raw JSON Data
{
"trx_id": "6ddbe6d221eb6aac8c829d14c3ea51c2866ad0d7",
"block": 18485456,
"trx_in_block": 19,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-28T15:52:39",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "raiblocks",
"author": "selfdrivingsandp",
"permlink": "security-thoughts-on-raiblocks",
"title": "Security thoughts on Raiblocks",
"body": "Raiblocks promises [\"unlimited scalability and no transaction fees\"](https://raiblocks.net/media/RaiBlocks_Whitepaper__English.pdf). What about security?\n\n# Double Spend Background\n\nFundamentally, the double spend problem must be addressed in any payment infrastructure. The system topology increases the difficulty of solving and adequately addressing the double spend problem.\n\nCentralized systems which rely on a payment processor achieve high scalability though require strong trust assumptions.\n\nDecentralized or distributed systems must address a further spectrum of issues, namely those revolving around byzantine agreement.\n\nBitcoin gave a probabilistic solution to the Byzantine agreement problem by the introduction of a proof of work system that dynamically increases the difficulty. An adversary must control greater than 51% of the hash power for a period of time in order to successfully execute a double spend attach. It should be noted that if a double spend attack was executed, the entire network would be aware, as Bitcoin is a peer to peer network where transactions are broadcasted and propagated across the network.\n\nPeercoin pioneered proof of stake. Rather than relying on proof of work to secure the network, Peercoin's proof of stake security guarantees hold as long as the adversary does not control 51% or more of the networks stake for a period of time. Such a stake attack more expensive than a proof of work attack. In addition, proof of stake has lower energy requirements compared to proof of work.\n\n\n\n# Raiblocks Security Claims\n\nNow, let's take a look first at how the \"unlimited scalability\" claim is made in Raiblocks and what type of security properties we can expect.\n\n## Double Spend Prevention Claim\n\nFirst, let's examine what is a Raiblock and the novel \"block-lattice\" structure and see if in fact all that's required to solve the byzantine agreement problem is a novel data structure (and no new consensus algorithms).\n\n\npg 7 Block Interval: Since each account has its own blockchain, updates can be performed asynchronous to the state of network. Therefore there are no block intervals and transactions can be published instantly.\n\nhttps://raiblocks.net/media/RaiBlocks_Whitepaper__English.pdf\n\n\n[\"We really only need to have transactions for an account ordered with respect to other transactions in the same account and since only one account is involved we don’t need network agreement so proof of work is unnecessary.\"](https://bitcoinist.com/exclusive-interview-raiblocks-team/)\n\n\n[\"The only agreement remaining is handling misbehaved clients that try to double spend, which in our system is called creating a fork. We use a weighted vote system to pick only one branch of a fork.\nThis means in the usual case of a well behaved peer your transactions complete instantly without a vote and only the peer is misbehaving are its transactions subject to the slower voting.\"](https://bitcoinist.com/exclusive-interview-raiblocks-team/)\n\n\n\n\nLet's summarise the design so far. \n\nBasically, as long as the network functions honestly, well we can expect no double spends. Ok, how about protecting against double spends?\n\n\nA weighted vote system is used. What exactly are the network requirements for a representative?\n\npg 7 [\"Representative: A representative node requires maximum network resources as it observes vote traffic from other representatives and publishes its own votes.\"](https://raiblocks.net/media/RaiBlocks_Whitepaper__English.pdf)\n\nWho exactly can be a representative?\n\npg 6 [\"Account holders who are unable to reliably participate in voting for connectivity reasons can name a representative who can vote with the weight of their balance. \"](https://raiblocks.net/media/RaiBlocks_Whitepaper__English.pdf)\n\nNot clear on how someone decides which representative to choose and how the selection process should be carried out?\n\nHowever, it's clear that by consolidating the voting power to those network powerful nodes Raiblocks is not distributed and borders on being centralized, or at least controlled by a handful of nodes. It is NOT peer to peer.\n\nWhy is this an issue?\n\nAs the paper points out, consolidating the voting power amongst a few opens the door to denial of service attacks. However, the paper handwaves regarding potential numbers of actual stake required. Without knowing the real distribution of Raiblocks and the allocation and voting distribution of representatives, the number can't be clearly specified.\n\nIs this a concern?\n\nFor someone that cares about targeted security attacks, yes.\n\n\n\n## Free Transactions\nSecond, transaction fees.\n\nThe paper mentions no transaction fees as a positive point. However, are no transaction fees really advantageous for security?\n\nRaiblocks relies on a minimal proof of work before sending each transaction, it claims similar to Hashcash.\n\nHowever, from an attacker's perspective having to spend the cryptocurrency's money as opposed to using cheap electricity to generate PoW, the spent transaction fee will mitigate and defer transaction spam more than PoW. The spent transaction fee requires a stake in the network being attacked.\n\n\n\n\n# Other concerns\n\n## C++ Codebase\n\n\"Raiblocks code is totally new and completely built from scratch\" (in C++)\n\nMaybe the bug bounty can help with this.\n\n\n## Exchanges\n\nWhat's the point of no transaction fees when exchanges charge 20% fees and require minimum balances for withdrawal?",
"json_metadata": "{\"tags\":[\"raiblocks\",\"cryptocurrency\",\"security\",\"doublespend\"],\"links\":[\"https://raiblocks.net/media/RaiBlocks_Whitepaper__English.pdf\",\"https://bitcoinist.com/exclusive-interview-raiblocks-team/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}hottopicsent 0.001 STEEM to @selfdrivingsandp- "Hello selfdrivingsandp. I Followed you.If you follow me, I'll be happy.Thanks :)"2017/12/23 14:12:03
hottopicsent 0.001 STEEM to @selfdrivingsandp- "Hello selfdrivingsandp. I Followed you.If you follow me, I'll be happy.Thanks :)"
2017/12/23 14:12:03
| from | hottopic |
| to | selfdrivingsandp |
| amount | 0.001 STEEM |
| memo | Hello selfdrivingsandp. I Followed you.If you follow me, I'll be happy.Thanks :) |
| Transaction Info | Block #18339546/Trx e981ad6c9f89704fb965287dfe1170a9aad89cec |
View Raw JSON Data
{
"trx_id": "e981ad6c9f89704fb965287dfe1170a9aad89cec",
"block": 18339546,
"trx_in_block": 51,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-23T14:12:03",
"op": [
"transfer",
{
"from": "hottopic",
"to": "selfdrivingsandp",
"amount": "0.001 STEEM",
"memo": "Hello selfdrivingsandp. I Followed you.If you follow me, I'll be happy.Thanks :)"
}
]
}selfdrivingsandppublished a new post: data-authentication2017/12/23 14:12:00
selfdrivingsandppublished a new post: data-authentication
2017/12/23 14:12:00
| parent author | |
| parent permlink | trust |
| author | selfdrivingsandp |
| permlink | data-authentication |
| title | Data Authentication |
| body | When data is received from a device, what guarantees do we have that the data is indeed authentic? Trusted hardware leads us to believe that a device with a trusted platform module should be trusted. How much is this true? We would have to trust the TPM itself. How do we form trust from unverified sources? In many cases it is the corroboration of multiple data sources that allows us to eventually take the data as verified and authentic. This happens in network protocols. Reliable protocols are built on top of unreliable protocols. This is sometimes done in testimony. The facts must be corroborated. What's the difference? Ultimately in the testimony there is a jury and judge. Jury makes a decision as to the ultimate conclusion, that implicitly decides what data is verified. We need a protocol to corroborate and verify data. Fake news is one such example today where its needed. Multiple news sources will show the facts. What's the issue? There are enough competiting news sources that will distort the facts. |
| json metadata | {"tags":["trust","authentication","data","verification","security"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #18339545/Trx 5f42e91ce6a51db63b3d4d363edbdb4b670715a8 |
View Raw JSON Data
{
"trx_id": "5f42e91ce6a51db63b3d4d363edbdb4b670715a8",
"block": 18339545,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-23T14:12:00",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "trust",
"author": "selfdrivingsandp",
"permlink": "data-authentication",
"title": "Data Authentication",
"body": "When data is received from a device, what guarantees do we have that the data is indeed authentic?\n\nTrusted hardware leads us to believe that a device with a trusted platform module should be trusted. How much is this true?\n\nWe would have to trust the TPM itself.\n\nHow do we form trust from unverified sources?\n\nIn many cases it is the corroboration of multiple data sources that allows us to eventually take the data as verified and authentic.\n\nThis happens in network protocols. Reliable protocols are built on top of unreliable protocols.\n\nThis is sometimes done in testimony. The facts must be corroborated.\n\nWhat's the difference? Ultimately in the testimony there is a jury and judge. Jury makes a decision as to the ultimate conclusion, that implicitly decides what data is verified.\n\nWe need a protocol to corroborate and verify data.\n\nFake news is one such example today where its needed. Multiple news sources will show the facts.\n\nWhat's the issue?\n\nThere are enough competiting news sources that will distort the facts.",
"json_metadata": "{\"tags\":[\"trust\",\"authentication\",\"data\",\"verification\",\"security\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}2017/10/12 16:31:36
2017/10/12 16:31:36
| parent author | selfdrivingsandp |
| parent permlink | advancements-of-lidar |
| author | minnowpond |
| permlink | re-advancements-of-lidar-20171012t163135 |
| title | |
| body | @reported has voted on behalf of @minnowpond. If you would like to recieve upvotes from minnowponds team on all your posts, simply FOLLOW @minnowpond. To receive an upvote send 0.25 SBD to @minnowpond with your posts url as the memo To receive an reSteem send 0.75 SBD to @minnowpond with your posts url as the memo To receive an upvote and a reSteem send 1.00SBD to @minnowpond with your posts url as the memo |
| json metadata | {"app": "pysteem/0.5.4"} |
| Transaction Info | Block #16270047/Trx 7d809f82e1195d1518cfbd71ee1d8e2a519e7af6 |
View Raw JSON Data
{
"trx_id": "7d809f82e1195d1518cfbd71ee1d8e2a519e7af6",
"block": 16270047,
"trx_in_block": 12,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-10-12T16:31:36",
"op": [
"comment",
{
"parent_author": "selfdrivingsandp",
"parent_permlink": "advancements-of-lidar",
"author": "minnowpond",
"permlink": "re-advancements-of-lidar-20171012t163135",
"title": "",
"body": "@reported has voted on behalf of @minnowpond. If you would like to recieve upvotes from minnowponds team on all your posts, simply FOLLOW @minnowpond. \n\n To receive an upvote send 0.25 SBD to @minnowpond with your posts url as the memo\n To receive an reSteem send 0.75 SBD to @minnowpond with your posts url as the memo\n To receive an upvote and a reSteem send 1.00SBD to @minnowpond with your posts url as the memo",
"json_metadata": "{\"app\": \"pysteem/0.5.4\"}"
}
]
}reportedupvoted (1.00%) @selfdrivingsandp / advancements-of-lidar2017/10/12 16:31:33
reportedupvoted (1.00%) @selfdrivingsandp / advancements-of-lidar
2017/10/12 16:31:33
| voter | reported |
| author | selfdrivingsandp |
| permlink | advancements-of-lidar |
| weight | 100 (1.00%) |
| Transaction Info | Block #16270046/Trx 1a32a9c6ab611a0163439a3fd80d10348153d13f |
View Raw JSON Data
{
"trx_id": "1a32a9c6ab611a0163439a3fd80d10348153d13f",
"block": 16270046,
"trx_in_block": 13,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-10-12T16:31:33",
"op": [
"vote",
{
"voter": "reported",
"author": "selfdrivingsandp",
"permlink": "advancements-of-lidar",
"weight": 100
}
]
}2017/10/12 16:24:24
2017/10/12 16:24:24
| parent author | selfdrivingsandp |
| parent permlink | advancements-of-lidar |
| author | steemitrobot |
| permlink | re-selfdrivingsandp-advancements-of-lidar-20171012t162417482z |
| title | |
| body | http://i.imgur.com/0L71kDM.png This post was resteemed by @steemitrobot! Good Luck! > **Resteem your post just send 0.100 SBD or Steem with your post ID on memo. We have over 2000 followers. Take our service to reach more People.** > **Pro Plan just send 1 SBD or Steem with your post ID on memo we will resteem your post and send 10 upvotes from our Associate Accounts.** The @steemitrobot users are a small but growing community. Check out the other resteemed posts in steemitrobot's feed. Some of them are truly great. Please upvote this comment for helping me grow. |
| json metadata | {"tags":["lidar"],"users":["steemitrobot"],"image":["http://i.imgur.com/0L71kDM.png"],"app":"steemit/0.1"} |
| Transaction Info | Block #16269903/Trx 1320e7bd22cdf8a90162763e2ad961a4bc1d1580 |
View Raw JSON Data
{
"trx_id": "1320e7bd22cdf8a90162763e2ad961a4bc1d1580",
"block": 16269903,
"trx_in_block": 32,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-10-12T16:24:24",
"op": [
"comment",
{
"parent_author": "selfdrivingsandp",
"parent_permlink": "advancements-of-lidar",
"author": "steemitrobot",
"permlink": "re-selfdrivingsandp-advancements-of-lidar-20171012t162417482z",
"title": "",
"body": "http://i.imgur.com/0L71kDM.png\nThis post was resteemed by @steemitrobot!\nGood Luck!\n\n> **Resteem your post just send 0.100 SBD or Steem with your post ID on memo. We have over 2000 followers. Take our service to reach more People.**\n\n> **Pro Plan just send 1 SBD or Steem with your post ID on memo we will resteem your post and send 10 upvotes from our Associate Accounts.**\n\nThe @steemitrobot users are a small but growing community.\nCheck out the other resteemed posts in steemitrobot's feed.\nSome of them are truly great. Please upvote this comment for helping me grow.",
"json_metadata": "{\"tags\":[\"lidar\"],\"users\":[\"steemitrobot\"],\"image\":[\"http://i.imgur.com/0L71kDM.png\"],\"app\":\"steemit/0.1\"}"
}
]
}selfdrivingsandppublished a new post: advancements-of-lidar2017/10/12 16:20:54
selfdrivingsandppublished a new post: advancements-of-lidar
2017/10/12 16:20:54
| parent author | |
| parent permlink | lidar |
| author | selfdrivingsandp |
| permlink | advancements-of-lidar |
| title | Advancements of LIDAR |
| body | LIDAR has been advancing rapidly in the past year. While Elon Musk has famously denounced the merits of LIDAR [here](https://techcrunch.com/2016/07/15/elon-musk-adamantly-standing-by-improving-radar-even-though-its-so-close-to-lidar/), [here](https://9to5google.com/2015/10/16/elon-musk-says-that-the-lidar-google-uses-in-its-self-driving-car-doesnt-make-sense-in-a-car-context/) [here](https://insideevs.com/elon-musk-tesla-doesnt-need-lidar-will-tweak-radar-to-be-lidar-like/) > That said, I don’t think you need LIDAR. I think you can do this all with passive optical and then with maybe one forward RADAR… if you are driving fast into rain or snow or dust. I think that completely solves it without the use of LIDAR. I’m not a big fan of LIDAR, I don’t think it makes sense in this context. However, we now have LIDAR that captures millions of points per second and can handle fog and other unclear conditions [here](http://image-sensors-world.blogspot.com/2017/09/luminar-on-automotive-lidar-progress.html) Expect to see the uptake of LIDAR to increase. Toyota and GM just made large purchases of LIDAR companies. [here](https://techcrunch.com/2017/09/27/luminar-lidar-toyota-research-institute/) and [here](https://www.theverge.com/2017/10/9/16448306/gm-cruise-strobe-lidar-acquisition) |
| json metadata | {"tags":["lidar","self-driving"],"links":["https://techcrunch.com/2016/07/15/elon-musk-adamantly-standing-by-improving-radar-even-though-its-so-close-to-lidar/","https://9to5google.com/2015/10/16/elon-musk-says-that-the-lidar-google-uses-in-its-self-driving-car-doesnt-make-sense-in-a-car-context/","https://insideevs.com/elon-musk-tesla-doesnt-need-lidar-will-tweak-radar-to-be-lidar-like/","http://image-sensors-world.blogspot.com/2017/09/luminar-on-automotive-lidar-progress.html","https://techcrunch.com/2017/09/27/luminar-lidar-toyota-research-institute/","https://www.theverge.com/2017/10/9/16448306/gm-cruise-strobe-lidar-acquisition"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #16269833/Trx 80f68051c6da1af6c6e1a008d54d0978a9361932 |
View Raw JSON Data
{
"trx_id": "80f68051c6da1af6c6e1a008d54d0978a9361932",
"block": 16269833,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-10-12T16:20:54",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "lidar",
"author": "selfdrivingsandp",
"permlink": "advancements-of-lidar",
"title": "Advancements of LIDAR",
"body": "LIDAR has been advancing rapidly in the past year. While Elon Musk has famously denounced the merits of LIDAR [here](https://techcrunch.com/2016/07/15/elon-musk-adamantly-standing-by-improving-radar-even-though-its-so-close-to-lidar/), [here](https://9to5google.com/2015/10/16/elon-musk-says-that-the-lidar-google-uses-in-its-self-driving-car-doesnt-make-sense-in-a-car-context/) [here](https://insideevs.com/elon-musk-tesla-doesnt-need-lidar-will-tweak-radar-to-be-lidar-like/)\n\n> That said, I don’t think you need LIDAR. I think you can do this all with passive optical and then with maybe one forward RADAR… if you are driving fast into rain or snow or dust. I think that completely solves it without the use of LIDAR. I’m not a big fan of LIDAR, I don’t think it makes sense in this context.\n\nHowever, we now have LIDAR that captures millions of points per second and can handle fog and other unclear conditions [here](http://image-sensors-world.blogspot.com/2017/09/luminar-on-automotive-lidar-progress.html)\n\nExpect to see the uptake of LIDAR to increase.\n\nToyota and GM just made large purchases of LIDAR companies. [here](https://techcrunch.com/2017/09/27/luminar-lidar-toyota-research-institute/) and [here](https://www.theverge.com/2017/10/9/16448306/gm-cruise-strobe-lidar-acquisition)",
"json_metadata": "{\"tags\":[\"lidar\",\"self-driving\"],\"links\":[\"https://techcrunch.com/2016/07/15/elon-musk-adamantly-standing-by-improving-radar-even-though-its-so-close-to-lidar/\",\"https://9to5google.com/2015/10/16/elon-musk-says-that-the-lidar-google-uses-in-its-self-driving-car-doesnt-make-sense-in-a-car-context/\",\"https://insideevs.com/elon-musk-tesla-doesnt-need-lidar-will-tweak-radar-to-be-lidar-like/\",\"http://image-sensors-world.blogspot.com/2017/09/luminar-on-automotive-lidar-progress.html\",\"https://techcrunch.com/2017/09/27/luminar-lidar-toyota-research-institute/\",\"https://www.theverge.com/2017/10/9/16448306/gm-cruise-strobe-lidar-acquisition\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}2017/09/11 02:36:12
2017/09/11 02:36:12
| parent author | selfdrivingsandp |
| parent permlink | event-data-recorder-standardization |
| author | minnowpond1 |
| permlink | re-event-data-recorder-standardization-20170911t023611 |
| title | |
| body | This post recieved an upvote from minnowpond. If you would like to recieve upvotes from minnowpond on all your posts, simply FOLLOW @minnowpond |
| json metadata | {"app": "pysteem/0.5.4"} |
| Transaction Info | Block #15361030/Trx eb147359f54e3e9fa15375499ce760954a6ab226 |
View Raw JSON Data
{
"trx_id": "eb147359f54e3e9fa15375499ce760954a6ab226",
"block": 15361030,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-11T02:36:12",
"op": [
"comment",
{
"parent_author": "selfdrivingsandp",
"parent_permlink": "event-data-recorder-standardization",
"author": "minnowpond1",
"permlink": "re-event-data-recorder-standardization-20170911t023611",
"title": "",
"body": "This post recieved an upvote from minnowpond. If you would like to recieve upvotes from minnowpond on all your posts, simply FOLLOW @minnowpond",
"json_metadata": "{\"app\": \"pysteem/0.5.4\"}"
}
]
}minnowpond1upvoted (1.00%) @selfdrivingsandp / event-data-recorder-standardization2017/09/11 02:36:09
minnowpond1upvoted (1.00%) @selfdrivingsandp / event-data-recorder-standardization
2017/09/11 02:36:09
| voter | minnowpond1 |
| author | selfdrivingsandp |
| permlink | event-data-recorder-standardization |
| weight | 100 (1.00%) |
| Transaction Info | Block #15361029/Trx 8912a9a39a66cd116713a897dcfd65e6aa92211a |
View Raw JSON Data
{
"trx_id": "8912a9a39a66cd116713a897dcfd65e6aa92211a",
"block": 15361029,
"trx_in_block": 10,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-11T02:36:09",
"op": [
"vote",
{
"voter": "minnowpond1",
"author": "selfdrivingsandp",
"permlink": "event-data-recorder-standardization",
"weight": 100
}
]
}selfdrivingsandppublished a new post: event-data-recorder-standardization2017/09/11 02:25:09
selfdrivingsandppublished a new post: event-data-recorder-standardization
2017/09/11 02:25:09
| parent author | |
| parent permlink | eventdatarecorder |
| author | selfdrivingsandp |
| permlink | event-data-recorder-standardization |
| title | Event Data Recorder Standardization |
| body | The NHTSA has [standardized](https://www.federalregister.gov/documents/2012/08/09/2012-19580/event-data-recorders#table_of_contents) the event data recorder in vehicles in response to the investigation and issues that occurred during the US Toyota brake pedal acceleration problem. The data to be included is the following The forward and lateral crash force. The crash event duration. Indicated vehicle speed. Accelerator position. Engine rpm. Brake application and antilock brake activation. Steering wheel angle. Stability control engagement. Vehicle roll angle, in case of a rollover. Number of times the vehicle has been started. Driver and front-passenger safety belt engagement, and pretensioner or force limiter engagement. Air bag deployment, speed, and faults for all air bags. Front seat positions. Occupant size. Number of crashes (one or more impacts during the final crash event). To access the event data recorder requires physical access. Authorization is controlled by access codes that the vehicle owner should control. However, any knowledgeable technician with physical access is able to also read the event data recorder as long as they have the proprietary cables. The question then becomes of privacy. How does a vehicle owner control what data is access and what is released? Who gets to ultimately decide? |
| json metadata | {"tags":["eventdatarecorder","vehicles","security"],"links":["https://www.federalregister.gov/documents/2012/08/09/2012-19580/event-data-recorders#table_of_contents"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #15360809/Trx 153b87f1333f8c1b3359ec215cb3d9bdef167ec4 |
View Raw JSON Data
{
"trx_id": "153b87f1333f8c1b3359ec215cb3d9bdef167ec4",
"block": 15360809,
"trx_in_block": 24,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-11T02:25:09",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "eventdatarecorder",
"author": "selfdrivingsandp",
"permlink": "event-data-recorder-standardization",
"title": "Event Data Recorder Standardization",
"body": "The NHTSA has [standardized](https://www.federalregister.gov/documents/2012/08/09/2012-19580/event-data-recorders#table_of_contents) the event data recorder in vehicles in response to the investigation and issues that occurred during the US Toyota brake pedal acceleration problem.\n\nThe data to be included is the following\n\n\n The forward and lateral crash force.\n The crash event duration.\n Indicated vehicle speed.\n Accelerator position.\n Engine rpm.\n Brake application and antilock brake activation.\n Steering wheel angle.\n Stability control engagement.\n Vehicle roll angle, in case of a rollover.\n Number of times the vehicle has been started.\n Driver and front-passenger safety belt engagement, and pretensioner or force limiter engagement.\n Air bag deployment, speed, and faults for all air bags.\n Front seat positions.\n Occupant size.\n Number of crashes (one or more impacts during the final crash event).\n\n\nTo access the event data recorder requires physical access. Authorization is controlled by access codes that the vehicle owner should control.\n\nHowever, any knowledgeable technician with physical access is able to also read the event data recorder as long as they have the proprietary cables.\n\nThe question then becomes of privacy. How does a vehicle owner control what data is access and what is released? Who gets to ultimately decide?",
"json_metadata": "{\"tags\":[\"eventdatarecorder\",\"vehicles\",\"security\"],\"links\":[\"https://www.federalregister.gov/documents/2012/08/09/2012-19580/event-data-recorders#table_of_contents\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}selfdrivingsandpfollowed @wealthguide2017/09/11 01:12:00
selfdrivingsandpfollowed @wealthguide
2017/09/11 01:12:00
| required auths | [] |
| required posting auths | ["selfdrivingsandp"] |
| id | follow |
| json | ["follow",{"follower":"selfdrivingsandp","following":"wealthguide","what":["blog"]}] |
| Transaction Info | Block #15359346/Trx 9e0bd9dd0ca85323ba56eafd8dbc5bbbee421a92 |
View Raw JSON Data
{
"trx_id": "9e0bd9dd0ca85323ba56eafd8dbc5bbbee421a92",
"block": 15359346,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-11T01:12:00",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"selfdrivingsandp"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"selfdrivingsandp\",\"following\":\"wealthguide\",\"what\":[\"blog\"]}]"
}
]
}Manabar
Voting Power100.00%
Downvote Power100.00%
Resource Credits100.00%
Reputation Progress0.00%
{
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779085065
},
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779085065
},
"rc_account": {
"account": "selfdrivingsandp",
"rc_manabar": {
"current_mana": "10164408779",
"last_update_time": 1779085065
},
"max_rc_creation_adjustment": {
"amount": "2020748973",
"precision": 6,
"nai": "@@000000037"
},
"max_rc": "10164408779"
}
}Account Metadata
| POSTING JSON METADATA | |
| None | |
| JSON METADATA | |
| None |
{
"posting_json_metadata": {},
"json_metadata": {}
}Auth Keys
Owner
Single Signature
Public Keys
STM7dihyRe2u9jJLCeMJBcn2wUN3nsKdi6HRt2YGAvmUeyFgD5sDg1/1
Active
Single Signature
Public Keys
STM7FDU5MEtRnUk1LdQMwUwCFPG7u5YyZyG7kgSkFdUWqfnUKfe5d1/1
Posting
Single Signature
Public Keys
STM7carZV2iSRZkP94kopB6vDfCfPFeQT2a4og5birKDUEC8yaYtZ1/1
Memo
STM88N5Wkv2gMuZzAkz5zwKmWKsmEn8idgJ2mCr97B82n3GFFRvtv
{
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7dihyRe2u9jJLCeMJBcn2wUN3nsKdi6HRt2YGAvmUeyFgD5sDg",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7FDU5MEtRnUk1LdQMwUwCFPG7u5YyZyG7kgSkFdUWqfnUKfe5d",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7carZV2iSRZkP94kopB6vDfCfPFeQT2a4og5birKDUEC8yaYtZ",
1
]
]
},
"memo": "STM88N5Wkv2gMuZzAkz5zwKmWKsmEn8idgJ2mCr97B82n3GFFRvtv"
}Witness Votes
0 / 30
No active witness votes.
[]