VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS83.19%
Net Worth
177.955USD
STEEM
0.094STEEM
SBD
132.693SBD
Own SP
1,969.942SP
Detailed Balance
| STEEM | ||
| balance | 0.094STEEM | STEEM |
| market_balance | 0.000STEEM | STEEM |
| savings_balance | 0.000STEEM | STEEM |
| reward_steem_balance | 0.000STEEM | STEEM |
| STEEM POWER | ||
| Own SP | 1,969.942SP | SP |
| Delegated Out | 0.000SP | SP |
| Delegation In | 0.000SP | SP |
| Effective Power | 1,969.942SP | SP |
| Reward SP (pending) | 0.000SP | SP |
| SBD | ||
| sbd_balance | 132.693SBD | SBD |
| sbd_conversions | 0.000SBD | SBD |
| sbd_market_balance | 0.000SBD | SBD |
| savings_sbd_balance | 0.000SBD | SBD |
| reward_sbd_balance | 0.000SBD | SBD |
{
"balance": "0.094 STEEM",
"savings_balance": "0.000 STEEM",
"reward_steem_balance": "0.000 STEEM",
"vesting_shares": "3203981.111769 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "0.000000 VESTS",
"sbd_balance": "132.693 SBD",
"savings_sbd_balance": "0.000 SBD",
"reward_sbd_balance": "0.000 SBD",
"conversions": []
}Account Info
| name | gedae |
| id | 8954 |
| rank | 2,131 |
| reputation | 1237187736857 |
| created | 2016-05-18T10:03:18 |
| recovery_account | steem |
| proxy | None |
| post_count | 3 |
| comment_count | 0 |
| lifetime_vote_count | 0 |
| witnesses_voted_for | 0 |
| last_post | 2016-07-25T21:18:21 |
| last_root_post | 2016-07-25T21:18:21 |
| last_vote_time | 2016-07-25T21:18:21 |
| proxied_vsf_votes | 0, 0, 0, 0 |
| can_vote | 1 |
| voting_power | 9,949 |
| delayed_votes | 0 |
| balance | 0.094 STEEM |
| savings_balance | 0.000 STEEM |
| sbd_balance | 132.693 SBD |
| savings_sbd_balance | 0.000 SBD |
| vesting_shares | 3203981.111769 VESTS |
| delegated_vesting_shares | 0.000000 VESTS |
| received_vesting_shares | 0.000000 VESTS |
| reward_vesting_balance | 0.000000 VESTS |
| vesting_balance | 0.000 STEEM |
| vesting_withdraw_rate | 0.000000 VESTS |
| next_vesting_withdrawal | 1969-12-31T23:59:59 |
| withdrawn | 0 |
| to_withdraw | 0 |
| withdraw_routes | 0 |
| savings_withdraw_requests | 0 |
| last_account_recovery | 1970-01-01T00:00:00 |
| reset_account | null |
| last_owner_update | 1970-01-01T00:00:00 |
| last_account_update | 1970-01-01T00:00:00 |
| mined | No |
| sbd_seconds | 0 |
| sbd_last_interest_payment | 2016-08-25T21:21:12 |
| savings_sbd_last_interest_payment | 1970-01-01T00:00:00 |
{
"active": {
"account_auths": [],
"key_auths": [
[
"STM6NgmfDgDH5QeRoE15ajy2Xc4Yrk9yFhXP86AydC4F95tzVcqHH",
1
]
],
"weight_threshold": 1
},
"balance": "0.094 STEEM",
"can_vote": true,
"comment_count": 0,
"created": "2016-05-18T10:03:18",
"curation_rewards": 0,
"delegated_vesting_shares": "0.000000 VESTS",
"downvote_manabar": {
"current_mana": 0,
"last_update_time": 1463565798
},
"guest_bloggers": [],
"id": 8954,
"json_metadata": "",
"last_account_recovery": "1970-01-01T00:00:00",
"last_account_update": "1970-01-01T00:00:00",
"last_owner_update": "1970-01-01T00:00:00",
"last_post": "2016-07-25T21:18:21",
"last_root_post": "2016-07-25T21:18:21",
"last_vote_time": "2016-07-25T21:18:21",
"lifetime_vote_count": 0,
"market_history": [],
"memo_key": "STM7Gw4DxbfMyfEfduwkS2yt8w6nCvErjr8dWsZyfjrBjhfX49HQF",
"mined": false,
"name": "gedae",
"next_vesting_withdrawal": "1969-12-31T23:59:59",
"other_history": [],
"owner": {
"account_auths": [],
"key_auths": [
[
"STM6AQWBRhGNrULYw3HaZFBNz3bLa9tbZWCnAZJzgFD2eK6XUv7N9",
1
]
],
"weight_threshold": 1
},
"pending_claimed_accounts": 0,
"post_bandwidth": 0,
"post_count": 3,
"post_history": [],
"posting": {
"account_auths": [],
"key_auths": [
[
"STM5qSVM63oM65GAhX3ytgDaKrFw74qTfJ2WycD4ERpX59YvBwyaf",
1
]
],
"weight_threshold": 1
},
"posting_json_metadata": "",
"posting_rewards": 1187916,
"proxied_vsf_votes": [
0,
0,
0,
0
],
"proxy": "",
"received_vesting_shares": "0.000000 VESTS",
"recovery_account": "steem",
"reputation": "1237187736857",
"reset_account": "null",
"reward_sbd_balance": "0.000 SBD",
"reward_steem_balance": "0.000 STEEM",
"reward_vesting_balance": "0.000000 VESTS",
"reward_vesting_steem": "0.000 STEEM",
"savings_balance": "0.000 STEEM",
"savings_sbd_balance": "0.000 SBD",
"savings_sbd_last_interest_payment": "1970-01-01T00:00:00",
"savings_sbd_seconds": "0",
"savings_sbd_seconds_last_update": "1970-01-01T00:00:00",
"savings_withdraw_requests": 0,
"sbd_balance": "132.693 SBD",
"sbd_last_interest_payment": "2016-08-25T21:21:12",
"sbd_seconds": "0",
"sbd_seconds_last_update": "2016-08-25T21:21:12",
"tags_usage": [],
"to_withdraw": 0,
"transfer_history": [],
"vesting_balance": "0.000 STEEM",
"vesting_shares": "3203981.111769 VESTS",
"vesting_withdraw_rate": "0.000000 VESTS",
"vote_history": [],
"voting_manabar": {
"current_mana": 9949,
"last_update_time": 1469481501
},
"voting_power": 9949,
"withdraw_routes": 0,
"withdrawn": 0,
"witness_votes": [],
"witnesses_voted_for": 0,
"rank": 2131
}Withdraw Routes
| Incoming | Outgoing |
|---|---|
Empty | Empty |
{
"incoming": [],
"outgoing": []
}From Date
To Date
2023/03/11 02:12:18
2023/03/11 02:12:18
| amount | 0.001 STEEM |
| from | steemegg |
| memo | Vote se-witness as one of your 30 witnesses for free votes https://steemlogin.com/sign/account-witness-vote?witness=se-witness&approve=1 | Send 15 or more TRON to TUep3qrvP4QwqHtoXJjdQ6Q7JRQdyuaJQH with your steem username as the memo for the market value back in steem. Or visit steemegg.com and visit the exchange tab. |
| to | gedae |
| Transaction Info | Block #72767964/Trx b0b11cd4d39f4d3e2474faee1c370e12c14d47e4 |
View Raw JSON Data
{
"block": 72767964,
"op": [
"transfer",
{
"amount": "0.001 STEEM",
"from": "steemegg",
"memo": "Vote se-witness as one of your 30 witnesses for free votes https://steemlogin.com/sign/account-witness-vote?witness=se-witness&approve=1 | Send 15 or more TRON to TUep3qrvP4QwqHtoXJjdQ6Q7JRQdyuaJQH with your steem username as the memo for the market value back in steem. Or visit steemegg.com and visit the exchange tab.",
"to": "gedae"
}
],
"op_in_trx": 0,
"timestamp": "2023-03-11T02:12:18",
"trx_id": "b0b11cd4d39f4d3e2474faee1c370e12c14d47e4",
"trx_in_block": 9,
"virtual_op": 0
}2022/12/24 17:33:45
2022/12/24 17:33:45
| amount | 0.001 STEEM |
| from | steemegg |
| memo | Free Upvotes Await!!!, Vote @se-witness for one of your 30 witness votes. Once you do so, you will start accumulating free upvotes every 6 hours automatically. Please check my latests posts for more info. Thanks! |
| to | gedae |
| Transaction Info | Block #70579379/Trx 0b1b1bc180ba58b5a1288bbce89082d3c26cc59e |
View Raw JSON Data
{
"block": 70579379,
"op": [
"transfer",
{
"amount": "0.001 STEEM",
"from": "steemegg",
"memo": "Free Upvotes Await!!!, Vote @se-witness for one of your 30 witness votes. Once you do so, you will start accumulating free upvotes every 6 hours automatically. Please check my latests posts for more info. Thanks!",
"to": "gedae"
}
],
"op_in_trx": 0,
"timestamp": "2022-12-24T17:33:45",
"trx_id": "0b1b1bc180ba58b5a1288bbce89082d3c26cc59e",
"trx_in_block": 36,
"virtual_op": 0
}roadofrichsent 0.005 STEEM to @gedae- "❗Hello gedae, You can contribute to the @roadofrich by voting as a witness. You will receive daily STEEM revenue through Witness vote. Enjoy your day 🙃"2022/10/08 14:12:30
roadofrichsent 0.005 STEEM to @gedae- "❗Hello gedae, You can contribute to the @roadofrich by voting as a witness. You will receive daily STEEM revenue through Witness vote. Enjoy your day 🙃"
2022/10/08 14:12:30
| amount | 0.005 STEEM |
| from | roadofrich |
| memo | ❗Hello gedae, You can contribute to the @roadofrich by voting as a witness. You will receive daily STEEM revenue through Witness vote. Enjoy your day 🙃 |
| to | gedae |
| Transaction Info | Block #68371070/Trx ea2ea084dd7b558c935f389a7992097857e7bbc5 |
View Raw JSON Data
{
"block": 68371070,
"op": [
"transfer",
{
"amount": "0.005 STEEM",
"from": "roadofrich",
"memo": "❗Hello gedae, You can contribute to the @roadofrich by voting as a witness. You will receive daily STEEM revenue through Witness vote. Enjoy your day 🙃",
"to": "gedae"
}
],
"op_in_trx": 0,
"timestamp": "2022-10-08T14:12:30",
"trx_id": "ea2ea084dd7b558c935f389a7992097857e7bbc5",
"trx_in_block": 4,
"virtual_op": 0
}roadofrichsent 0.005 STEEM to @gedae- "❗Hello gedae, You can contribute to the @roadofrich by voting as a witness. You will receive daily STEEM revenue through Witness vote. Enjoy your day 🙃"2022/10/07 14:07:57
roadofrichsent 0.005 STEEM to @gedae- "❗Hello gedae, You can contribute to the @roadofrich by voting as a witness. You will receive daily STEEM revenue through Witness vote. Enjoy your day 🙃"
2022/10/07 14:07:57
| amount | 0.005 STEEM |
| from | roadofrich |
| memo | ❗Hello gedae, You can contribute to the @roadofrich by voting as a witness. You will receive daily STEEM revenue through Witness vote. Enjoy your day 🙃 |
| to | gedae |
| Transaction Info | Block #68342313/Trx 17d2a9639985c893861a73f887416f7d67e23dca |
View Raw JSON Data
{
"block": 68342313,
"op": [
"transfer",
{
"amount": "0.005 STEEM",
"from": "roadofrich",
"memo": "❗Hello gedae, You can contribute to the @roadofrich by voting as a witness. You will receive daily STEEM revenue through Witness vote. Enjoy your day 🙃",
"to": "gedae"
}
],
"op_in_trx": 0,
"timestamp": "2022-10-07T14:07:57",
"trx_id": "17d2a9639985c893861a73f887416f7d67e23dca",
"trx_in_block": 1,
"virtual_op": 0
}roadofrichsent 0.005 STEEM to @gedae- "❗Hello gedae, You can contribute to the @roadofrich by voting as a witness. You will receive daily STEEM revenue through Witness vote. Enjoy your day 🙃"2022/09/28 13:56:09
roadofrichsent 0.005 STEEM to @gedae- "❗Hello gedae, You can contribute to the @roadofrich by voting as a witness. You will receive daily STEEM revenue through Witness vote. Enjoy your day 🙃"
2022/09/28 13:56:09
| amount | 0.005 STEEM |
| from | roadofrich |
| memo | ❗Hello gedae, You can contribute to the @roadofrich by voting as a witness. You will receive daily STEEM revenue through Witness vote. Enjoy your day 🙃 |
| to | gedae |
| Transaction Info | Block #68084098/Trx 17d0518a1a2ef9026a83c0ef54d3f697d77dd9a4 |
View Raw JSON Data
{
"block": 68084098,
"op": [
"transfer",
{
"amount": "0.005 STEEM",
"from": "roadofrich",
"memo": "❗Hello gedae, You can contribute to the @roadofrich by voting as a witness. You will receive daily STEEM revenue through Witness vote. Enjoy your day 🙃",
"to": "gedae"
}
],
"op_in_trx": 0,
"timestamp": "2022-09-28T13:56:09",
"trx_id": "17d0518a1a2ef9026a83c0ef54d3f697d77dd9a4",
"trx_in_block": 4,
"virtual_op": 0
}roadofrichsent 0.005 STEEM to @gedae- "❗Hello gedae, You can contribute to the @roadofrich by voting as a witness. You will receive daily STEEM revenue through Witness vote. Enjoy your day 🙃"2022/09/27 13:55:15
roadofrichsent 0.005 STEEM to @gedae- "❗Hello gedae, You can contribute to the @roadofrich by voting as a witness. You will receive daily STEEM revenue through Witness vote. Enjoy your day 🙃"
2022/09/27 13:55:15
| amount | 0.005 STEEM |
| from | roadofrich |
| memo | ❗Hello gedae, You can contribute to the @roadofrich by voting as a witness. You will receive daily STEEM revenue through Witness vote. Enjoy your day 🙃 |
| to | gedae |
| Transaction Info | Block #68055436/Trx e0bb89a76edae7f7a845c1f3e43da4da2a3f6e84 |
View Raw JSON Data
{
"block": 68055436,
"op": [
"transfer",
{
"amount": "0.005 STEEM",
"from": "roadofrich",
"memo": "❗Hello gedae, You can contribute to the @roadofrich by voting as a witness. You will receive daily STEEM revenue through Witness vote. Enjoy your day 🙃",
"to": "gedae"
}
],
"op_in_trx": 0,
"timestamp": "2022-09-27T13:55:15",
"trx_id": "e0bb89a76edae7f7a845c1f3e43da4da2a3f6e84",
"trx_in_block": 1,
"virtual_op": 0
}roadofrichsent 0.005 STEEM to @gedae- "❗Hello gedae, You can contribute to the @roadofrich by voting as a witness. You will receive daily STEEM revenue through Witness vote. Enjoy your day 🙃"2022/09/26 13:54:03
roadofrichsent 0.005 STEEM to @gedae- "❗Hello gedae, You can contribute to the @roadofrich by voting as a witness. You will receive daily STEEM revenue through Witness vote. Enjoy your day 🙃"
2022/09/26 13:54:03
| amount | 0.005 STEEM |
| from | roadofrich |
| memo | ❗Hello gedae, You can contribute to the @roadofrich by voting as a witness. You will receive daily STEEM revenue through Witness vote. Enjoy your day 🙃 |
| to | gedae |
| Transaction Info | Block #68026771/Trx 5b44ea418e1a903cb55ab0020b94215b1f44c5e2 |
View Raw JSON Data
{
"block": 68026771,
"op": [
"transfer",
{
"amount": "0.005 STEEM",
"from": "roadofrich",
"memo": "❗Hello gedae, You can contribute to the @roadofrich by voting as a witness. You will receive daily STEEM revenue through Witness vote. Enjoy your day 🙃",
"to": "gedae"
}
],
"op_in_trx": 0,
"timestamp": "2022-09-26T13:54:03",
"trx_id": "5b44ea418e1a903cb55ab0020b94215b1f44c5e2",
"trx_in_block": 3,
"virtual_op": 0
}roadofrichsent 0.005 STEEM to @gedae- "❗Hello gedae, You can contribute to the @roadofrich by voting as a witness. You will receive daily STEEM revenue through Witness vote. Enjoy your day 🙃"2022/09/18 13:53:18
roadofrichsent 0.005 STEEM to @gedae- "❗Hello gedae, You can contribute to the @roadofrich by voting as a witness. You will receive daily STEEM revenue through Witness vote. Enjoy your day 🙃"
2022/09/18 13:53:18
| amount | 0.005 STEEM |
| from | roadofrich |
| memo | ❗Hello gedae, You can contribute to the @roadofrich by voting as a witness. You will receive daily STEEM revenue through Witness vote. Enjoy your day 🙃 |
| to | gedae |
| Transaction Info | Block #67797837/Trx 1d8a2548c348bd859ffd07961bba094f082b575f |
View Raw JSON Data
{
"block": 67797837,
"op": [
"transfer",
{
"amount": "0.005 STEEM",
"from": "roadofrich",
"memo": "❗Hello gedae, You can contribute to the @roadofrich by voting as a witness. You will receive daily STEEM revenue through Witness vote. Enjoy your day 🙃",
"to": "gedae"
}
],
"op_in_trx": 0,
"timestamp": "2022-09-18T13:53:18",
"trx_id": "1d8a2548c348bd859ffd07961bba094f082b575f",
"trx_in_block": 8,
"virtual_op": 0
}roadofrichsent 0.005 STEEM to @gedae- "❗Hello gedae, You can contribute to the @roadofrich by voting as a witness. You will receive daily STEEM revenue through Witness vote. Enjoy your day 🙃"2022/09/17 13:54:21
roadofrichsent 0.005 STEEM to @gedae- "❗Hello gedae, You can contribute to the @roadofrich by voting as a witness. You will receive daily STEEM revenue through Witness vote. Enjoy your day 🙃"
2022/09/17 13:54:21
| amount | 0.005 STEEM |
| from | roadofrich |
| memo | ❗Hello gedae, You can contribute to the @roadofrich by voting as a witness. You will receive daily STEEM revenue through Witness vote. Enjoy your day 🙃 |
| to | gedae |
| Transaction Info | Block #67769198/Trx dce8bb4368a0b3632efa4f27e9abca886275601c |
View Raw JSON Data
{
"block": 67769198,
"op": [
"transfer",
{
"amount": "0.005 STEEM",
"from": "roadofrich",
"memo": "❗Hello gedae, You can contribute to the @roadofrich by voting as a witness. You will receive daily STEEM revenue through Witness vote. Enjoy your day 🙃",
"to": "gedae"
}
],
"op_in_trx": 0,
"timestamp": "2022-09-17T13:54:21",
"trx_id": "dce8bb4368a0b3632efa4f27e9abca886275601c",
"trx_in_block": 4,
"virtual_op": 0
}roadofrichsent 0.005 STEEM to @gedae- "❗Hello gedae, You can contribute to the @roadofrich by voting as a witness. You will receive daily STEEM revenue through Witness vote. Enjoy your day 🙃"2022/09/08 13:50:45
roadofrichsent 0.005 STEEM to @gedae- "❗Hello gedae, You can contribute to the @roadofrich by voting as a witness. You will receive daily STEEM revenue through Witness vote. Enjoy your day 🙃"
2022/09/08 13:50:45
| amount | 0.005 STEEM |
| from | roadofrich |
| memo | ❗Hello gedae, You can contribute to the @roadofrich by voting as a witness. You will receive daily STEEM revenue through Witness vote. Enjoy your day 🙃 |
| to | gedae |
| Transaction Info | Block #67511184/Trx 3d56feaa15dbe54d2219ee7116f105bf16651754 |
View Raw JSON Data
{
"block": 67511184,
"op": [
"transfer",
{
"amount": "0.005 STEEM",
"from": "roadofrich",
"memo": "❗Hello gedae, You can contribute to the @roadofrich by voting as a witness. You will receive daily STEEM revenue through Witness vote. Enjoy your day 🙃",
"to": "gedae"
}
],
"op_in_trx": 0,
"timestamp": "2022-09-08T13:50:45",
"trx_id": "3d56feaa15dbe54d2219ee7116f105bf16651754",
"trx_in_block": 2,
"virtual_op": 0
}roadofrichsent 0.050 STEEM to @gedae- "❗Hello gedae, You can contribute to the @roadofrich by voting as a witness. 🪙 Vote to share for Daily Witness vote and more 🪙 . ❗ Enjoy your day 🙃"2022/09/03 12:29:00
roadofrichsent 0.050 STEEM to @gedae- "❗Hello gedae, You can contribute to the @roadofrich by voting as a witness. 🪙 Vote to share for Daily Witness vote and more 🪙 . ❗ Enjoy your day 🙃"
2022/09/03 12:29:00
| amount | 0.050 STEEM |
| from | roadofrich |
| memo | ❗Hello gedae, You can contribute to the @roadofrich by voting as a witness. 🪙 Vote to share for Daily Witness vote and more 🪙 . ❗ Enjoy your day 🙃 |
| to | gedae |
| Transaction Info | Block #67366516/Trx afdd5374f95da7191ce70f232004c765edc64605 |
View Raw JSON Data
{
"block": 67366516,
"op": [
"transfer",
{
"amount": "0.050 STEEM",
"from": "roadofrich",
"memo": "❗Hello gedae, You can contribute to the @roadofrich by voting as a witness. 🪙 Vote to share for Daily Witness vote and more 🪙 . ❗ Enjoy your day 🙃",
"to": "gedae"
}
],
"op_in_trx": 0,
"timestamp": "2022-09-03T12:29:00",
"trx_id": "afdd5374f95da7191ce70f232004c765edc64605",
"trx_in_block": 2,
"virtual_op": 0
}2019/05/18 12:00:33
2019/05/18 12:00:33
| author | steemitboard |
| body | Congratulations @gedae! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@gedae/birthday3.png</td><td>Happy Birthday! - You are on the Steem blockchain for 3 years!</td></tr></table> <sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@gedae) and compare to others on the [Steem Ranking](http://steemitboard.com/ranking/index.php?name=gedae)_</sub> **Do not miss the last post from @steemitboard:** <table><tr><td><a href="https://steemit.com/japanese/@steemitboard/new-japanese-speaking-community-steem-meetup-badge"><img src="https://steemitimages.com/64x128/https://cdn.steemitimages.com/DQmRWbAjbeETEaqSPLcpwYX1JN5pZhdPffv4q6DaBs6xvZm/image.png"></a></td><td><a href="https://steemit.com/japanese/@steemitboard/new-japanese-speaking-community-steem-meetup-badge">New japanese speaking community Steem Meetup badge</a></td></tr></table> ###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| parent author | gedae |
| parent permlink | the-dao-and-the-benefactors |
| permlink | steemitboard-notify-gedae-20190518t120033000z |
| title | |
| Transaction Info | Block #33014704/Trx c1e8ef6f3262e89cccd4810bb188cb18e309e6d0 |
View Raw JSON Data
{
"block": 33014704,
"op": [
"comment",
{
"author": "steemitboard",
"body": "Congratulations @gedae! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@gedae/birthday3.png</td><td>Happy Birthday! - You are on the Steem blockchain for 3 years!</td></tr></table>\n\n<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@gedae) and compare to others on the [Steem Ranking](http://steemitboard.com/ranking/index.php?name=gedae)_</sub>\n\n\n**Do not miss the last post from @steemitboard:**\n<table><tr><td><a href=\"https://steemit.com/japanese/@steemitboard/new-japanese-speaking-community-steem-meetup-badge\"><img src=\"https://steemitimages.com/64x128/https://cdn.steemitimages.com/DQmRWbAjbeETEaqSPLcpwYX1JN5pZhdPffv4q6DaBs6xvZm/image.png\"></a></td><td><a href=\"https://steemit.com/japanese/@steemitboard/new-japanese-speaking-community-steem-meetup-badge\">New japanese speaking community Steem Meetup badge</a></td></tr></table>\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}",
"parent_author": "gedae",
"parent_permlink": "the-dao-and-the-benefactors",
"permlink": "steemitboard-notify-gedae-20190518t120033000z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2019-05-18T12:00:33",
"trx_id": "c1e8ef6f3262e89cccd4810bb188cb18e309e6d0",
"trx_in_block": 12,
"virtual_op": 0
}2019/03/12 15:29:45
2019/03/12 15:29:45
| amount | 0.001 STEEM |
| from | dlease |
| memo | BuildTeam is proud to announce the release of DLease.io - our flagship P2P leasing marketplace app, aimed at assisting Steemians in leasing and delegating STEEM POWER for daily passive returns, with recent yields as high as 20% APR. DLease.io is a professional grade app , designed to replace the current MinnowBooster.net leasing market which has to date facilitated nearly 20 Million STEEM POWER in lease value to happy BuildTeam customers. View the new app at https://dlease.io/ or read the announcement post on https://steemit.com/@dlease. |
| to | gedae |
| Transaction Info | Block #31092032/Trx 45024589d3cfa140c7ea556f609e37e11c9d5946 |
View Raw JSON Data
{
"block": 31092032,
"op": [
"transfer",
{
"amount": "0.001 STEEM",
"from": "dlease",
"memo": "BuildTeam is proud to announce the release of DLease.io - our flagship P2P leasing marketplace app, aimed at assisting Steemians in leasing and delegating STEEM POWER for daily passive returns, with recent yields as high as 20% APR. DLease.io is a professional grade app , designed to replace the current MinnowBooster.net leasing market which has to date facilitated nearly 20 Million STEEM POWER in lease value to happy BuildTeam customers. View the new app at https://dlease.io/ or read the announcement post on https://steemit.com/@dlease.",
"to": "gedae"
}
],
"op_in_trx": 0,
"timestamp": "2019-03-12T15:29:45",
"trx_id": "45024589d3cfa140c7ea556f609e37e11c9d5946",
"trx_in_block": 32,
"virtual_op": 0
}2018/05/03 00:32:15
2018/05/03 00:32:15
| amount | 0.001 STEEM |
| from | justyy |
| memo | Dear @gedae, I am a new witness with Reputation 70+, my witness thread: https://steemit.com/witness-category/@justyy/justyy-just-another-witness Thank you very much for your kind considerations. ^_^ My contributions: SteemIt Tools, Bots, APIs and Tutorial: https://helloacm.com/tools/steemit/ Please don't get mad or upset considering this brings you a little fortune of 0.001 STEEM. Millions of Thanks. 谢谢! Xie xie! |
| to | gedae |
| Transaction Info | Block #22091828/Trx b3f3bd5f747c2cd7851a1b335d14b9755bfd18a3 |
View Raw JSON Data
{
"block": 22091828,
"op": [
"transfer",
{
"amount": "0.001 STEEM",
"from": "justyy",
"memo": "Dear @gedae, I am a new witness with Reputation 70+, my witness thread: https://steemit.com/witness-category/@justyy/justyy-just-another-witness Thank you very much for your kind considerations. ^_^ My contributions: SteemIt Tools, Bots, APIs and Tutorial: https://helloacm.com/tools/steemit/ Please don't get mad or upset considering this brings you a little fortune of 0.001 STEEM. Millions of Thanks. 谢谢! Xie xie!",
"to": "gedae"
}
],
"op_in_trx": 0,
"timestamp": "2018-05-03T00:32:15",
"trx_id": "b3f3bd5f747c2cd7851a1b335d14b9755bfd18a3",
"trx_in_block": 16,
"virtual_op": 0
}gedaereceived 0.041 SBD, 0.064 SP author reward for @gedae / the-dao-and-the-benefactors
gedaereceived 0.041 SBD, 0.064 SP author reward for @gedae / the-dao-and-the-benefactors
| author | gedae |
| permlink | the-dao-and-the-benefactors |
| sbd payout | 0.041 SBD |
| steem payout | 0.000 STEEM |
| vesting payout | 104.746922 VESTS |
| Transaction Info | Block #4399424/Virtual Operation #3 |
View Raw JSON Data
{
"block": 4399424,
"op": [
"author_reward",
{
"author": "gedae",
"permlink": "the-dao-and-the-benefactors",
"sbd_payout": "0.041 SBD",
"steem_payout": "0.000 STEEM",
"vesting_payout": "104.746922 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2016-08-25T21:21:12",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": 3
}gedaereceived 1.081 SBD interest payment
gedaereceived 1.081 SBD interest payment
| interest | 1.081 SBD |
| owner | gedae |
| Transaction Info | Block #4399424/Virtual Operation #2 |
View Raw JSON Data
{
"block": 4399424,
"op": [
"interest",
{
"interest": "1.081 SBD",
"owner": "gedae"
}
],
"op_in_trx": 0,
"timestamp": "2016-08-25T21:21:12",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": 2
}| author | alaynaspop |
| body | Simply Great Information and Presentation |
| json metadata | {"tags":["dao"]} |
| parent author | gedae |
| parent permlink | the-dao-and-the-benefactors |
| permlink | re-gedae-the-dao-and-the-benefactors-20160815t043743755z |
| title | |
| Transaction Info | Block #4093941/Trx 18006e4766615d27a5d284b78e30998c27fe2d50 |
View Raw JSON Data
{
"block": 4093941,
"op": [
"comment",
{
"author": "alaynaspop",
"body": "Simply Great Information and Presentation",
"json_metadata": "{\"tags\":[\"dao\"]}",
"parent_author": "gedae",
"parent_permlink": "the-dao-and-the-benefactors",
"permlink": "re-gedae-the-dao-and-the-benefactors-20160815t043743755z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2016-08-15T04:37:42",
"trx_id": "18006e4766615d27a5d284b78e30998c27fe2d50",
"trx_in_block": 2,
"virtual_op": 0
}| amount | 0.001 SBD |
| from | vdoh |
| memo | I believe in Steemit, I believe in You! Good afternoon, I want to invite you to support my post dedicated to my dream and development and good advertizing of community of Steemit! I want to make the balloon on which I am going to visit many large cities and to place the logo and the slogan Steemit on it. Support me and I will support you! URL : https://steemit.com/steem/@vdoh/rise-steemit |
| to | gedae |
| Transaction Info | Block #3985319/Trx edf77535558ed6468ed32b8db5b43cf48a08a3c5 |
View Raw JSON Data
{
"block": 3985319,
"op": [
"transfer",
{
"amount": "0.001 SBD",
"from": "vdoh",
"memo": "I believe in Steemit, I believe in You! Good afternoon, I want to invite you to support my post dedicated to my dream and development and good advertizing of community of Steemit! I want to make the balloon on which I am going to visit many large cities and to place the logo and the slogan Steemit on it. Support me and I will support you! URL : https://steemit.com/steem/@vdoh/rise-steemit",
"to": "gedae"
}
],
"op_in_trx": 0,
"timestamp": "2016-08-11T09:38:09",
"trx_id": "edf77535558ed6468ed32b8db5b43cf48a08a3c5",
"trx_in_block": 0,
"virtual_op": 0
}killerstormupvoted (100.00%) @gedae / the-dao-and-the-benefactors
killerstormupvoted (100.00%) @gedae / the-dao-and-the-benefactors
| author | gedae |
| permlink | the-dao-and-the-benefactors |
| voter | killerstorm |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3667635/Trx 2e6770e89b33ec44277aa71bd6577cddd9c59012 |
View Raw JSON Data
{
"block": 3667635,
"op": [
"vote",
{
"author": "gedae",
"permlink": "the-dao-and-the-benefactors",
"voter": "killerstorm",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-07-31T07:33:00",
"trx_id": "2e6770e89b33ec44277aa71bd6577cddd9c59012",
"trx_in_block": 0,
"virtual_op": 0
}alexozupvoted (100.00%) @gedae / the-dao-and-the-benefactors
alexozupvoted (100.00%) @gedae / the-dao-and-the-benefactors
| author | gedae |
| permlink | the-dao-and-the-benefactors |
| voter | alexoz |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3647639/Trx 567e1f96ea2a0d81e9a975e6298aef6d358fea7a |
View Raw JSON Data
{
"block": 3647639,
"op": [
"vote",
{
"author": "gedae",
"permlink": "the-dao-and-the-benefactors",
"voter": "alexoz",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-07-30T14:47:18",
"trx_id": "567e1f96ea2a0d81e9a975e6298aef6d358fea7a",
"trx_in_block": 6,
"virtual_op": 0
}gedaereceived 0.093 SBD, 0.066 SP author reward for @gedae / the-dao-and-the-benefactors
gedaereceived 0.093 SBD, 0.066 SP author reward for @gedae / the-dao-and-the-benefactors
| author | gedae |
| permlink | the-dao-and-the-benefactors |
| sbd payout | 0.093 SBD |
| steem payout | 0.000 STEEM |
| vesting payout | 106.764578 VESTS |
| Transaction Info | Block #3541102/Virtual Operation #3 |
View Raw JSON Data
{
"block": 3541102,
"op": [
"author_reward",
{
"author": "gedae",
"permlink": "the-dao-and-the-benefactors",
"sbd_payout": "0.093 SBD",
"steem_payout": "0.000 STEEM",
"vesting_payout": "106.764578 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2016-07-26T21:21:09",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": 3
}gedaereceived 0.819 SBD interest payment
gedaereceived 0.819 SBD interest payment
| interest | 0.819 SBD |
| owner | gedae |
| Transaction Info | Block #3541102/Virtual Operation #2 |
View Raw JSON Data
{
"block": 3541102,
"op": [
"interest",
{
"interest": "0.819 SBD",
"owner": "gedae"
}
],
"op_in_trx": 0,
"timestamp": "2016-07-26T21:21:09",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": 2
}iamsatoshiupvoted (100.00%) @gedae / the-dao-and-the-benefactors
iamsatoshiupvoted (100.00%) @gedae / the-dao-and-the-benefactors
| author | gedae |
| permlink | the-dao-and-the-benefactors |
| voter | iamsatoshi |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3529963/Trx 3da0f2956a432bb3a6b43edd138398956b3ee082 |
View Raw JSON Data
{
"block": 3529963,
"op": [
"vote",
{
"author": "gedae",
"permlink": "the-dao-and-the-benefactors",
"voter": "iamsatoshi",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-07-26T11:58:51",
"trx_id": "3da0f2956a432bb3a6b43edd138398956b3ee082",
"trx_in_block": 2,
"virtual_op": 0
}vogueupvoted (100.00%) @gedae / the-dao-and-the-benefactors
vogueupvoted (100.00%) @gedae / the-dao-and-the-benefactors
| author | gedae |
| permlink | the-dao-and-the-benefactors |
| voter | vogue |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3527696/Trx 17de5183a763e76af3d5f8b8ac15a808a386945e |
View Raw JSON Data
{
"block": 3527696,
"op": [
"vote",
{
"author": "gedae",
"permlink": "the-dao-and-the-benefactors",
"voter": "vogue",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-07-26T10:03:30",
"trx_id": "17de5183a763e76af3d5f8b8ac15a808a386945e",
"trx_in_block": 1,
"virtual_op": 0
}gedaepublished a new post: the-dao-and-the-benefactors
gedaepublished a new post: the-dao-and-the-benefactors
| author | gedae |
| body | @@ -537,16 +537,20 @@ wxZsyXc& +amp; feature= @@ -558,16 +558,20 @@ outu.be& +amp; t=1m ? A @@ -4011,16 +4011,17 @@ sch**, %0A +%0A you are |
| json metadata | {"tags":["dao","ethereum","hardfork"],"links":["https://www.youtube.com/watch?v=CnUdwxZsyXc&feature=youtu.be&t=1m"]} |
| parent author | |
| parent permlink | dao |
| permlink | the-dao-and-the-benefactors |
| title | The DAO and the Benefactors |
| Transaction Info | Block #3527090/Trx 765a5107ef34cac9a2e287574c41708dd95ff176 |
View Raw JSON Data
{
"block": 3527090,
"op": [
"comment",
{
"author": "gedae",
"body": "@@ -537,16 +537,20 @@\n wxZsyXc&\n+amp;\n feature=\n@@ -558,16 +558,20 @@\n outu.be&\n+amp;\n t=1m ? A\n@@ -4011,16 +4011,17 @@\n sch**, %0A\n+%0A\n you are\n",
"json_metadata": "{\"tags\":[\"dao\",\"ethereum\",\"hardfork\"],\"links\":[\"https://www.youtube.com/watch?v=CnUdwxZsyXc&feature=youtu.be&t=1m\"]}",
"parent_author": "",
"parent_permlink": "dao",
"permlink": "the-dao-and-the-benefactors",
"title": "The DAO and the Benefactors"
}
],
"op_in_trx": 0,
"timestamp": "2016-07-26T09:32:57",
"trx_id": "765a5107ef34cac9a2e287574c41708dd95ff176",
"trx_in_block": 2,
"virtual_op": 0
}akaninyene-etukupvoted (100.00%) @gedae / the-dao-and-the-benefactors
akaninyene-etukupvoted (100.00%) @gedae / the-dao-and-the-benefactors
| author | gedae |
| permlink | the-dao-and-the-benefactors |
| voter | akaninyene-etuk |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3513413/Trx f13e65c3678a73970eabd721a71feacb3a477e65 |
View Raw JSON Data
{
"block": 3513413,
"op": [
"vote",
{
"author": "gedae",
"permlink": "the-dao-and-the-benefactors",
"voter": "akaninyene-etuk",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-07-25T22:02:15",
"trx_id": "f13e65c3678a73970eabd721a71feacb3a477e65",
"trx_in_block": 5,
"virtual_op": 0
}ullikumeupvoted (100.00%) @gedae / the-dao-and-the-benefactors
ullikumeupvoted (100.00%) @gedae / the-dao-and-the-benefactors
| author | gedae |
| permlink | the-dao-and-the-benefactors |
| voter | ullikume |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3513403/Trx 88fc92378528fc0b215431064af5d4d99b4692b4 |
View Raw JSON Data
{
"block": 3513403,
"op": [
"vote",
{
"author": "gedae",
"permlink": "the-dao-and-the-benefactors",
"voter": "ullikume",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-07-25T22:01:42",
"trx_id": "88fc92378528fc0b215431064af5d4d99b4692b4",
"trx_in_block": 1,
"virtual_op": 0
}medicalupvoted (100.00%) @gedae / the-dao-and-the-benefactors
medicalupvoted (100.00%) @gedae / the-dao-and-the-benefactors
| author | gedae |
| permlink | the-dao-and-the-benefactors |
| voter | medical |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3513150/Trx 460c1ea50d4aef0287dea59ee6581d5b162046b5 |
View Raw JSON Data
{
"block": 3513150,
"op": [
"vote",
{
"author": "gedae",
"permlink": "the-dao-and-the-benefactors",
"voter": "medical",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-07-25T21:48:54",
"trx_id": "460c1ea50d4aef0287dea59ee6581d5b162046b5",
"trx_in_block": 5,
"virtual_op": 0
}rambogohamupvoted (100.00%) @gedae / the-dao-and-the-benefactors
rambogohamupvoted (100.00%) @gedae / the-dao-and-the-benefactors
| author | gedae |
| permlink | the-dao-and-the-benefactors |
| voter | rambogoham |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3512950/Trx 9c568a3849c9b17a36ea0d2e2c0ef6fb4f75b5b3 |
View Raw JSON Data
{
"block": 3512950,
"op": [
"vote",
{
"author": "gedae",
"permlink": "the-dao-and-the-benefactors",
"voter": "rambogoham",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-07-25T21:38:48",
"trx_id": "9c568a3849c9b17a36ea0d2e2c0ef6fb4f75b5b3",
"trx_in_block": 3,
"virtual_op": 0
}gedaepublished a new post: the-dao-and-the-benefactors
gedaepublished a new post: the-dao-and-the-benefactors
| author | gedae |
| body | https://pbs.twimg.com/media/Cjiqc5lXEAQcMxq.jpg As soon as The DAO attack happened, I've sold all my DAO tokens cheap. Why did I do it? Because all of us had an explicit agreement, stated many times: transactions are immutable and code is law. So it makes sense: if code is law, attacker will get as much money from the DAO as he wants, which renders DAO tokens worthless. We've had this declared as a primary feature of Ethereum, not to mention express wording in the The DAO terms, hadn't we https://www.youtube.com/watch?v=CnUdwxZsyXc&feature=youtu.be&t=1m ? As a diligent investor I sold my DAO tokens at a discounted price, knowing the attack transactions won’t be reverted. Some of you, who, for some reason, hesitated to sell at a discount, or had hope for some solution to revert the attack, have kept your DAO tokens, and subsequently sold Ether from The DAO at a much higher price, were motivated to support the hard fork. You, who explicitly agreed on The DAO terms you've thoroughly read before investing, https://daohub.org/explainer.html, including * There is a risk that, as an open source project, any contributor to The DAO’s software could introduce weaknesses or bugs into the DAO software, causing the loss of DAO tokens or ETH in one or more or even all of the DAO Token Holder’s accounts, and * Any and all explanatory terms or descriptions are merely offered for educational purposes and do not supercede or modify the express terms of The DAO’s code set forth on the blockchain; to the extent you believe there to be any conflict or discrepancy between the descriptions offered here and the functionality of The DAO’s code at 0xbb9bc244d798123fde783fcc1c72d3bb8c189413, The DAO’s code controls and sets forth all terms of The DAO Creation, have breached the agreement, supported the hard fork and managed to benefit from my losses. Well, good for you - when money talks, you don't really care about your agreements, principles, or the fact that you’re taking advantage of a contract violation to serve yourselves. Yep, it’s a dog eat dog world, isn’t it? Good thing is that now you know the price of your word - your word can be sold at the price of your investment in The DAO, you know the exact amount. But there are other people taking advantage of my losses and your decision to go pro-fork. Their financial gains from this are probably far greater than yours. The ones who bought a large amount of The DAO tokens at a huge discount - a reckless risky investment unless the buyers are the ones who know and control something the sellers don’t. The ones who had a much greater access to information on how the attack could and will be handled (remember the closed chats with exchanges and “we will discuss internally and get back to the community” stuff?) and whether the hard fork is likely. The ones who had at their disposal a wider range of public address channels and a far greater clout in the “community” than any middle-of-the-road DAO token holder, causing you to go pro-fork with financial motivation and reputational pressure. The ones who are [motivated](https://twitter.com/stephantual/status/757521246615732224) to throw their resources at supporting the hard fork to rescue a large holding of the DAO which they’ve refused to disclose, despite being directly questioned about it many times, although such disclosure would a be a logical part of due diligence for any project soliciting public investments. The ones who could make the most profits, taking advantage of both those who stayed true to the principles of Ethereum and terms of The DAO, and those who abandoned and perverted them, being financially motivated to breach the terms they’ve accepted. So who was in the best possible position to make profits out of the whole The DAO debacle? **Vitalik Buterin, Gavin Wood, Alex Van de Sande, Emin Gün Sirer, Vlad Zamfir, Shermin Voshmgir, Griff Green, Timon Rapp, Gian Bochsler, Stephan Tual, Griff Green, Simon and Christoph Jentzsch**, you are closely associated with The DAO and the hard fork in one capacity or the other. Some of you had their reputation used extensively to leverage The DAO marketing campaign. Some of you used their reputation extensively to push the hard fork, whether by publicly addressing the wider community, or by privately targeting much narrower circles - exchanges, mining pools, etc. Some of you are even using whatever remains of their reputation to bash on the original, unaltered, chain. You are also some of the brighter people in the Ethereum community (except for Stephan Tual and Griff Green, apparently). Given that, it shouldn’t be hard for you to answer the simple question: who had the motivation, the means, and moral flexibility to push the fork and take profits from it? I don’t really expect an answer from some of you for reasons which seem obvious. Others, however, could clarify their stance on the aforesaid - either by answering, or by ignoring the question. |
| json metadata | {"tags":["ethereum","dao","hardfork"],"links":["https://www.youtube.com/watch?v=CnUdwxZsyXc&feature=youtu.be&t=1m"]} |
| parent author | |
| parent permlink | dao |
| permlink | the-dao-and-the-benefactors |
| title | The DAO and the Benefactors |
| Transaction Info | Block #3512912/Trx 07164118a853392023ca19635b93f75983563b8b |
View Raw JSON Data
{
"block": 3512912,
"op": [
"comment",
{
"author": "gedae",
"body": "https://pbs.twimg.com/media/Cjiqc5lXEAQcMxq.jpg\n\nAs soon as The DAO attack happened, I've sold all my DAO tokens cheap. \n\nWhy did I do it? Because all of us had an explicit agreement, stated many times: transactions are immutable and code is law.\n\nSo it makes sense: if code is law, attacker will get as much money from the DAO as he wants, which renders DAO tokens worthless.\n\nWe've had this declared as a primary feature of Ethereum, not to mention express wording in the The DAO terms, hadn't we https://www.youtube.com/watch?v=CnUdwxZsyXc&feature=youtu.be&t=1m ? As a diligent investor I sold my DAO tokens at a discounted price, knowing the attack transactions won’t be reverted.\n\nSome of you, who, for some reason, hesitated to sell at a discount, or had hope for some solution to revert the attack, have kept your DAO tokens, and subsequently sold Ether from The DAO at a much higher price, were motivated to support the hard fork.\n\nYou, who explicitly agreed on The DAO terms you've thoroughly read before investing, https://daohub.org/explainer.html, including\n* There is a risk that, as an open source project, any contributor to The DAO’s software could introduce weaknesses or bugs into the DAO software, causing the loss of DAO tokens or ETH in one or more or even all of the DAO Token Holder’s accounts, \nand \n* Any and all explanatory terms or descriptions are merely offered for educational purposes and do not supercede or modify the express terms of The DAO’s code set forth on the blockchain; to the extent you believe there to be any conflict or discrepancy between the descriptions offered here and the functionality of The DAO’s code at 0xbb9bc244d798123fde783fcc1c72d3bb8c189413, The DAO’s code controls and sets forth all terms of The DAO Creation, \n\nhave breached the agreement, supported the hard fork and managed to benefit from my losses.\n\nWell, good for you - when money talks, you don't really care about your agreements, principles, or the fact that you’re taking advantage of a contract violation to serve yourselves.\nYep, it’s a dog eat dog world, isn’t it? Good thing is that now you know the price of your word - your word can be sold at the price of your investment in The DAO, you know the exact amount.\n\nBut there are other people taking advantage of my losses and your decision to go pro-fork. Their financial gains from this are probably far greater than yours.\n\nThe ones who bought a large amount of The DAO tokens at a huge discount - a reckless risky investment unless the buyers are the ones who know and control something the sellers don’t.\n\nThe ones who had a much greater access to information on how the attack could and will be handled (remember the closed chats with exchanges and “we will discuss internally and get back to the community” stuff?) and whether the hard fork is likely. \n\nThe ones who had at their disposal a wider range of public address channels and a far greater clout in the “community” than any middle-of-the-road DAO token holder, causing you to go pro-fork with financial motivation and reputational pressure.\n\nThe ones who are [motivated](https://twitter.com/stephantual/status/757521246615732224) to throw their resources at supporting the hard fork to rescue a large holding of the DAO which they’ve refused to disclose, despite being directly questioned about it many times, although such disclosure would a be a logical part of due diligence for any project soliciting public investments.\n\nThe ones who could make the most profits, taking advantage of both those who stayed true to the principles of Ethereum and terms of The DAO, and those who abandoned and perverted them, being financially motivated to breach the terms they’ve accepted.\n\nSo who was in the best possible position to make profits out of the whole The DAO debacle?\n\n**Vitalik Buterin, Gavin Wood, Alex Van de Sande, Emin Gün Sirer, Vlad Zamfir,\nShermin Voshmgir, Griff Green, Timon Rapp, Gian Bochsler, Stephan Tual, Griff Green, Simon and Christoph Jentzsch**, \n you are closely associated with The DAO and the hard fork in one capacity or the other. \nSome of you had their reputation used extensively to leverage The DAO marketing campaign. \nSome of you used their reputation extensively to push the hard fork, whether by publicly addressing the wider community, or by privately targeting much narrower circles - exchanges, mining pools, etc.\nSome of you are even using whatever remains of their reputation to bash on the original, unaltered, chain.\nYou are also some of the brighter people in the Ethereum community (except for Stephan Tual and Griff Green, apparently).\n\nGiven that, it shouldn’t be hard for you to answer the simple question: who had the motivation, the means, and moral flexibility to push the fork and take profits from it?\n\nI don’t really expect an answer from some of you for reasons which seem obvious. \nOthers, however, could clarify their stance on the aforesaid - either by answering, or by ignoring the question.",
"json_metadata": "{\"tags\":[\"ethereum\",\"dao\",\"hardfork\"],\"links\":[\"https://www.youtube.com/watch?v=CnUdwxZsyXc&feature=youtu.be&t=1m\"]}",
"parent_author": "",
"parent_permlink": "dao",
"permlink": "the-dao-and-the-benefactors",
"title": "The DAO and the Benefactors"
}
],
"op_in_trx": 0,
"timestamp": "2016-07-25T21:36:51",
"trx_id": "07164118a853392023ca19635b93f75983563b8b",
"trx_in_block": 0,
"virtual_op": 0
}mastletterupvoted (100.00%) @gedae / the-dao-and-the-benefactors
mastletterupvoted (100.00%) @gedae / the-dao-and-the-benefactors
| author | gedae |
| permlink | the-dao-and-the-benefactors |
| voter | mastletter |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3512788/Trx 734ffe4322b52b3c09bac52bf807fa3b0e4aa357 |
View Raw JSON Data
{
"block": 3512788,
"op": [
"vote",
{
"author": "gedae",
"permlink": "the-dao-and-the-benefactors",
"voter": "mastletter",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-07-25T21:30:39",
"trx_id": "734ffe4322b52b3c09bac52bf807fa3b0e4aa357",
"trx_in_block": 0,
"virtual_op": 0
}paco-steemupvoted (100.00%) @gedae / the-dao-and-the-benefactors
paco-steemupvoted (100.00%) @gedae / the-dao-and-the-benefactors
| author | gedae |
| permlink | the-dao-and-the-benefactors |
| voter | paco-steem |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3512724/Trx da02ea94d5eba6a9c3d4ffe658b5558b541473f9 |
View Raw JSON Data
{
"block": 3512724,
"op": [
"vote",
{
"author": "gedae",
"permlink": "the-dao-and-the-benefactors",
"voter": "paco-steem",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-07-25T21:27:27",
"trx_id": "da02ea94d5eba6a9c3d4ffe658b5558b541473f9",
"trx_in_block": 2,
"virtual_op": 0
}stilettoupvoted (100.00%) @gedae / the-dao-and-the-benefactors
stilettoupvoted (100.00%) @gedae / the-dao-and-the-benefactors
| author | gedae |
| permlink | the-dao-and-the-benefactors |
| voter | stiletto |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3512723/Trx 062ace76983fe020f12939baf1108583eb40b548 |
View Raw JSON Data
{
"block": 3512723,
"op": [
"vote",
{
"author": "gedae",
"permlink": "the-dao-and-the-benefactors",
"voter": "stiletto",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-07-25T21:27:24",
"trx_id": "062ace76983fe020f12939baf1108583eb40b548",
"trx_in_block": 4,
"virtual_op": 0
}spaninvupvoted (100.00%) @gedae / the-dao-and-the-benefactors
spaninvupvoted (100.00%) @gedae / the-dao-and-the-benefactors
| author | gedae |
| permlink | the-dao-and-the-benefactors |
| voter | spaninv |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3512722/Trx 7a20e7b0387a0ced054f95d94521c91fe12aee2f |
View Raw JSON Data
{
"block": 3512722,
"op": [
"vote",
{
"author": "gedae",
"permlink": "the-dao-and-the-benefactors",
"voter": "spaninv",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-07-25T21:27:21",
"trx_id": "7a20e7b0387a0ced054f95d94521c91fe12aee2f",
"trx_in_block": 7,
"virtual_op": 0
}| author | omarbitcoin |
| body | Me to😌 |
| json metadata | {"tags":["dao"]} |
| parent author | gedae |
| parent permlink | the-dao-and-the-benefactors |
| permlink | re-gedae-the-dao-and-the-benefactors-20160725t212044102z |
| title | |
| Transaction Info | Block #3512591/Trx a5182b86c4325b131347c7960e3221288207cbc2 |
View Raw JSON Data
{
"block": 3512591,
"op": [
"comment",
{
"author": "omarbitcoin",
"body": "Me to😌",
"json_metadata": "{\"tags\":[\"dao\"]}",
"parent_author": "gedae",
"parent_permlink": "the-dao-and-the-benefactors",
"permlink": "re-gedae-the-dao-and-the-benefactors-20160725t212044102z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2016-07-25T21:20:45",
"trx_id": "a5182b86c4325b131347c7960e3221288207cbc2",
"trx_in_block": 2,
"virtual_op": 0
}blueorgyupvoted (100.00%) @gedae / the-dao-and-the-benefactors
blueorgyupvoted (100.00%) @gedae / the-dao-and-the-benefactors
| author | gedae |
| permlink | the-dao-and-the-benefactors |
| voter | blueorgy |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3512565/Trx f7ec9521a1dac24091e5a563b4251236feb401ad |
View Raw JSON Data
{
"block": 3512565,
"op": [
"vote",
{
"author": "gedae",
"permlink": "the-dao-and-the-benefactors",
"voter": "blueorgy",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-07-25T21:19:27",
"trx_id": "f7ec9521a1dac24091e5a563b4251236feb401ad",
"trx_in_block": 5,
"virtual_op": 0
}| author | twitterbot |
| body | ###  **[Stephan Tual](https://twitter.com/@stephantual/status/757521246615732224)** tweeted @ 25 Jul 2016 - 10:21 UTC https://t.co/V3ubdnu9kp --- ###### *Disclaimer: I am just a bot trying to be helpful.* |
| json metadata | |
| parent author | gedae |
| parent permlink | the-dao-and-the-benefactors |
| permlink | re-the-dao-and-the-benefactors-20160725t211901 |
| title | |
| Transaction Info | Block #3512557/Trx 4a0cea8ef8cb137041c7e96c264d23cb6d1e7111 |
View Raw JSON Data
{
"block": 3512557,
"op": [
"comment",
{
"author": "twitterbot",
"body": "###  **[Stephan Tual](https://twitter.com/@stephantual/status/757521246615732224)** tweeted @ 25 Jul 2016 - 10:21 UTC\n\nhttps://t.co/V3ubdnu9kp\n\n---\n###### *Disclaimer: I am just a bot trying to be helpful.*",
"json_metadata": "",
"parent_author": "gedae",
"parent_permlink": "the-dao-and-the-benefactors",
"permlink": "re-the-dao-and-the-benefactors-20160725t211901",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2016-07-25T21:19:03",
"trx_id": "4a0cea8ef8cb137041c7e96c264d23cb6d1e7111",
"trx_in_block": 5,
"virtual_op": 0
}omarbitcoinupvoted (100.00%) @gedae / the-dao-and-the-benefactors
omarbitcoinupvoted (100.00%) @gedae / the-dao-and-the-benefactors
| author | gedae |
| permlink | the-dao-and-the-benefactors |
| voter | omarbitcoin |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3512550/Trx 33e2b52fcb57335b7774bef807a7fadef3bae34f |
View Raw JSON Data
{
"block": 3512550,
"op": [
"vote",
{
"author": "gedae",
"permlink": "the-dao-and-the-benefactors",
"voter": "omarbitcoin",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-07-25T21:18:42",
"trx_id": "33e2b52fcb57335b7774bef807a7fadef3bae34f",
"trx_in_block": 4,
"virtual_op": 0
}gedaeupvoted (100.00%) @gedae / the-dao-and-the-benefactors
gedaeupvoted (100.00%) @gedae / the-dao-and-the-benefactors
| author | gedae |
| permlink | the-dao-and-the-benefactors |
| voter | gedae |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3512543/Trx 4cb37422d7c40aa5d0ef6d6cc409125de818a30b |
View Raw JSON Data
{
"block": 3512543,
"op": [
"vote",
{
"author": "gedae",
"permlink": "the-dao-and-the-benefactors",
"voter": "gedae",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-07-25T21:18:21",
"trx_id": "4cb37422d7c40aa5d0ef6d6cc409125de818a30b",
"trx_in_block": 2,
"virtual_op": 0
}gedaepublished a new post: the-dao-and-the-benefactors
gedaepublished a new post: the-dao-and-the-benefactors
| author | gedae |
| body | https://pbs.twimg.com/media/Cjiqc5lXEAQcMxq.jpg As soon as The DAO attack happened, I've sold all my DAO tokens cheap. Why did I do it? Because all of us had an explicit agreement, stated many times: transactions are immutable and code is law. So it makes sense: if code is law, attacker will get as much money from the DAO as he wants, which renders DAO tokens worthless. We've had this declared as a primary feature of Ethereum, not to mention express wording in the The DAO terms, hadn't we https://www.youtube.com/watch?v=CnUdwxZsyXc&feature=youtu.be&t=1m ? As a diligent investor I sold my DAO tokens at a discounted price, knowing the attack transactions won’t be reverted. Some of you, who, for some reason, hesitated to sell at a discount, or had hope for some solution to revert the attack, have kept your DAO tokens, and subsequently sold Ether from The DAO at a much higher price, were motivated to support the hard fork. You, who explicitly agreed on The DAO terms you've thoroughly read before investing, https://daohub.org/explainer.html, including * There is a risk that, as an open source project, any contributor to The DAO’s software could introduce weaknesses or bugs into the DAO software, causing the loss of DAO tokens or ETH in one or more or even all of the DAO Token Holder’s accounts, and * Any and all explanatory terms or descriptions are merely offered for educational purposes and do not supercede or modify the express terms of The DAO’s code set forth on the blockchain; to the extent you believe there to be any conflict or discrepancy between the descriptions offered here and the functionality of The DAO’s code at 0xbb9bc244d798123fde783fcc1c72d3bb8c189413, The DAO’s code controls and sets forth all terms of The DAO Creation, have breached the agreement, supported the hard fork and managed to benefit from my losses. Well, good for you - when money talks, you don't really care about your agreements, principles, or the fact that you’re taking advantage of a contract violation to serve yourselves. Yep, it’s a dog eat dog world, isn’t it? Good thing is that now you know the price of your word - your word can be sold at the price of your investment in The DAO, you know the exact amount. But there are other people taking advantage of my losses and your decision to go pro-fork. Their financial gains from this are probably far greater than yours. The ones who bought a large amount of The DAO tokens at a huge discount - a reckless risky investment unless the buyers are the ones who know and control something the sellers don’t. The ones who had a much greater access to information on how the attack could and will be handled (remember the closed chats with exchanges and “we will discuss internally and get back to the community” stuff?) and whether the hard fork is likely. The ones who had at their disposal a wider range of public address channels and a far greater clout in the “community” than any middle-of-the-road DAO token holder, causing you to go pro-fork with financial motivation and reputational pressure. The ones who are [motivated](https://twitter.com/stephantual/status/757521246615732224) to throw their resources at supporting the hard fork to rescue a large holding of the DAO which they’ve refused to disclose, despite being directly questioned about it many times, although such disclosure would a be a logical part of due diligence for any project soliciting public investments. The ones who could make the most profits, taking advantage of both those who stayed true to the principles of Ethereum and terms of The DAO, and those who abandoned and perverted them, being financially motivated to breach the terms they’ve accepted. So who was in the best possible position to make profits out of the whole The DAO debacle? **Vitalik Buterin, Gavin Wood, Alex Van de Sande, Emin Gün Sirer, Vlad Zamfir, Shermin Voshmgir, Griff Green, Timon Rapp, Gian Bochsler, Stephan Tual, Griff Green, Simon and Christoph Jentzsch**, you are closely associated with The DAO and the hard fork in one capacity or the other. Some of you had their reputation used extensively to leverage The DAO marketing campaign. Some of you used their reputation extensively to push the hard fork, whether by publicly addressing the wider community, or by privately targeting much narrower circles - exchanges, mining pools, etc. Some of you are even using whatever remains of their reputation to bash on the original, unaltered, chain. You are also some of the brighter people in the Ethereum community (except for Stephan Tual and Griff Green, apparently). Given that, it shouldn’t be hard for you to answer the simple question: who had the motivation, the means, and moral flexibility to push the fork and take profits from it? I don’t really expect an answer from some of you for reasons which seem obvious. Others, however, could clarify their stance on the aforesaid - either by answering, or by ignoring the question. |
| json metadata | {"tags":["dao","ethereum","hardfork"],"links":["https://www.youtube.com/watch?v=CnUdwxZsyXc&feature=youtu.be&t=1m"]} |
| parent author | |
| parent permlink | dao |
| permlink | the-dao-and-the-benefactors |
| title | The DAO and the Benefactors |
| Transaction Info | Block #3512543/Trx 4cb37422d7c40aa5d0ef6d6cc409125de818a30b |
View Raw JSON Data
{
"block": 3512543,
"op": [
"comment",
{
"author": "gedae",
"body": "https://pbs.twimg.com/media/Cjiqc5lXEAQcMxq.jpg\n\nAs soon as The DAO attack happened, I've sold all my DAO tokens cheap. \n\nWhy did I do it? Because all of us had an explicit agreement, stated many times: transactions are immutable and code is law.\n\nSo it makes sense: if code is law, attacker will get as much money from the DAO as he wants, which renders DAO tokens worthless.\n\nWe've had this declared as a primary feature of Ethereum, not to mention express wording in the The DAO terms, hadn't we https://www.youtube.com/watch?v=CnUdwxZsyXc&feature=youtu.be&t=1m ? As a diligent investor I sold my DAO tokens at a discounted price, knowing the attack transactions won’t be reverted.\n\nSome of you, who, for some reason, hesitated to sell at a discount, or had hope for some solution to revert the attack, have kept your DAO tokens, and subsequently sold Ether from The DAO at a much higher price, were motivated to support the hard fork.\n\nYou, who explicitly agreed on The DAO terms you've thoroughly read before investing, https://daohub.org/explainer.html, including\n* There is a risk that, as an open source project, any contributor to The DAO’s software could introduce weaknesses or bugs into the DAO software, causing the loss of DAO tokens or ETH in one or more or even all of the DAO Token Holder’s accounts, \nand \n* Any and all explanatory terms or descriptions are merely offered for educational purposes and do not supercede or modify the express terms of The DAO’s code set forth on the blockchain; to the extent you believe there to be any conflict or discrepancy between the descriptions offered here and the functionality of The DAO’s code at 0xbb9bc244d798123fde783fcc1c72d3bb8c189413, The DAO’s code controls and sets forth all terms of The DAO Creation, \n\nhave breached the agreement, supported the hard fork and managed to benefit from my losses.\n\nWell, good for you - when money talks, you don't really care about your agreements, principles, or the fact that you’re taking advantage of a contract violation to serve yourselves.\nYep, it’s a dog eat dog world, isn’t it? Good thing is that now you know the price of your word - your word can be sold at the price of your investment in The DAO, you know the exact amount.\n\nBut there are other people taking advantage of my losses and your decision to go pro-fork. Their financial gains from this are probably far greater than yours.\n\nThe ones who bought a large amount of The DAO tokens at a huge discount - a reckless risky investment unless the buyers are the ones who know and control something the sellers don’t.\n\nThe ones who had a much greater access to information on how the attack could and will be handled (remember the closed chats with exchanges and “we will discuss internally and get back to the community” stuff?) and whether the hard fork is likely. \n\nThe ones who had at their disposal a wider range of public address channels and a far greater clout in the “community” than any middle-of-the-road DAO token holder, causing you to go pro-fork with financial motivation and reputational pressure.\n\nThe ones who are [motivated](https://twitter.com/stephantual/status/757521246615732224) to throw their resources at supporting the hard fork to rescue a large holding of the DAO which they’ve refused to disclose, despite being directly questioned about it many times, although such disclosure would a be a logical part of due diligence for any project soliciting public investments.\n\nThe ones who could make the most profits, taking advantage of both those who stayed true to the principles of Ethereum and terms of The DAO, and those who abandoned and perverted them, being financially motivated to breach the terms they’ve accepted.\n\nSo who was in the best possible position to make profits out of the whole The DAO debacle?\n\n**Vitalik Buterin, Gavin Wood, Alex Van de Sande, Emin Gün Sirer, Vlad Zamfir,\nShermin Voshmgir, Griff Green, Timon Rapp, Gian Bochsler, Stephan Tual, Griff Green, Simon and Christoph Jentzsch**, \n you are closely associated with The DAO and the hard fork in one capacity or the other. \nSome of you had their reputation used extensively to leverage The DAO marketing campaign. \nSome of you used their reputation extensively to push the hard fork, whether by publicly addressing the wider community, or by privately targeting much narrower circles - exchanges, mining pools, etc.\nSome of you are even using whatever remains of their reputation to bash on the original, unaltered, chain.\nYou are also some of the brighter people in the Ethereum community (except for Stephan Tual and Griff Green, apparently).\n\nGiven that, it shouldn’t be hard for you to answer the simple question: who had the motivation, the means, and moral flexibility to push the fork and take profits from it?\n\nI don’t really expect an answer from some of you for reasons which seem obvious. \nOthers, however, could clarify their stance on the aforesaid - either by answering, or by ignoring the question.",
"json_metadata": "{\"tags\":[\"dao\",\"ethereum\",\"hardfork\"],\"links\":[\"https://www.youtube.com/watch?v=CnUdwxZsyXc&feature=youtu.be&t=1m\"]}",
"parent_author": "",
"parent_permlink": "dao",
"permlink": "the-dao-and-the-benefactors",
"title": "The DAO and the Benefactors"
}
],
"op_in_trx": 0,
"timestamp": "2016-07-25T21:18:21",
"trx_id": "4cb37422d7c40aa5d0ef6d6cc409125de818a30b",
"trx_in_block": 2,
"virtual_op": 0
}nbogdanupvoted (100.00%) @gedae / the-dao-framework-a-brief-review-of-potential-architecture-breaches
nbogdanupvoted (100.00%) @gedae / the-dao-framework-a-brief-review-of-potential-architecture-breaches
| author | gedae |
| permlink | the-dao-framework-a-brief-review-of-potential-architecture-breaches |
| voter | nbogdan |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3360411/Trx 036b1e6accf63b4aca76fe4894655e1f48c88863 |
View Raw JSON Data
{
"block": 3360411,
"op": [
"vote",
{
"author": "gedae",
"permlink": "the-dao-framework-a-brief-review-of-potential-architecture-breaches",
"voter": "nbogdan",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-07-20T13:06:33",
"trx_id": "036b1e6accf63b4aca76fe4894655e1f48c88863",
"trx_in_block": 0,
"virtual_op": 0
}gedaereceived 130.658 SBD, 1,911.496 SP author reward for @gedae / the-dao-framework-a-brief-review-of-potential-architecture-breaches
gedaereceived 130.658 SBD, 1,911.496 SP author reward for @gedae / the-dao-framework-a-brief-review-of-potential-architecture-breaches
| author | gedae |
| permlink | the-dao-framework-a-brief-review-of-potential-architecture-breaches |
| sbd payout | 130.658 SBD |
| steem payout | 0.000 STEEM |
| vesting payout | 3108923.544148 VESTS |
| Transaction Info | Block #2889020/Virtual Operation #19145 |
View Raw JSON Data
{
"block": 2889020,
"op": [
"author_reward",
{
"author": "gedae",
"permlink": "the-dao-framework-a-brief-review-of-potential-architecture-breaches",
"sbd_payout": "130.658 SBD",
"steem_payout": "0.000 STEEM",
"vesting_payout": "3108923.544148 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2016-07-04T00:00:06",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": 19145
}steempowerupvoted (100.00%) @gedae / the-dao-framework-a-brief-review-of-potential-architecture-breaches
steempowerupvoted (100.00%) @gedae / the-dao-framework-a-brief-review-of-potential-architecture-breaches
| author | gedae |
| permlink | the-dao-framework-a-brief-review-of-potential-architecture-breaches |
| voter | steempower |
| weight | 10000 (100.00%) |
| Transaction Info | Block #1872245/Trx 6340ebd7b8bd7244cb774a2660b7d5e42585dca0 |
View Raw JSON Data
{
"block": 1872245,
"op": [
"vote",
{
"author": "gedae",
"permlink": "the-dao-framework-a-brief-review-of-potential-architecture-breaches",
"voter": "steempower",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-05-29T13:15:09",
"trx_id": "6340ebd7b8bd7244cb774a2660b7d5e42585dca0",
"trx_in_block": 0,
"virtual_op": 0
}| author | gedae |
| permlink | the-dao-framework-a-brief-review-of-potential-architecture-breaches |
| voter | jerome-colley |
| weight | 10000 (100.00%) |
| Transaction Info | Block #1856378/Trx e1d5e9e2f7f6701c6d6a5ce562047da34ceb7d9e |
View Raw JSON Data
{
"block": 1856378,
"op": [
"vote",
{
"author": "gedae",
"permlink": "the-dao-framework-a-brief-review-of-potential-architecture-breaches",
"voter": "jerome-colley",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-05-28T23:48:12",
"trx_id": "e1d5e9e2f7f6701c6d6a5ce562047da34ceb7d9e",
"trx_in_block": 0,
"virtual_op": 0
}benjojoupvoted (100.00%) @gedae / the-dao-framework-a-brief-review-of-potential-architecture-breaches
benjojoupvoted (100.00%) @gedae / the-dao-framework-a-brief-review-of-potential-architecture-breaches
| author | gedae |
| permlink | the-dao-framework-a-brief-review-of-potential-architecture-breaches |
| voter | benjojo |
| weight | 10000 (100.00%) |
| Transaction Info | Block #1811532/Trx 1f102eb143508f4e0d81c7696cb48a58bc5c53ab |
View Raw JSON Data
{
"block": 1811532,
"op": [
"vote",
{
"author": "gedae",
"permlink": "the-dao-framework-a-brief-review-of-potential-architecture-breaches",
"voter": "benjojo",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-05-27T10:23:45",
"trx_id": "1f102eb143508f4e0d81c7696cb48a58bc5c53ab",
"trx_in_block": 0,
"virtual_op": 0
}steemrollinupvoted (100.00%) @gedae / the-dao-framework-a-brief-review-of-potential-architecture-breaches
steemrollinupvoted (100.00%) @gedae / the-dao-framework-a-brief-review-of-potential-architecture-breaches
| author | gedae |
| permlink | the-dao-framework-a-brief-review-of-potential-architecture-breaches |
| voter | steemrollin |
| weight | 10000 (100.00%) |
| Transaction Info | Block #1623395/Trx 5886061b0955f6b9b0815d578261e0ff830c019d |
View Raw JSON Data
{
"block": 1623395,
"op": [
"vote",
{
"author": "gedae",
"permlink": "the-dao-framework-a-brief-review-of-potential-architecture-breaches",
"voter": "steemrollin",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-05-20T21:21:15",
"trx_id": "5886061b0955f6b9b0815d578261e0ff830c019d",
"trx_in_block": 0,
"virtual_op": 0
}sandwichupvoted (100.00%) @gedae / the-dao-framework-a-brief-review-of-potential-architecture-breaches
sandwichupvoted (100.00%) @gedae / the-dao-framework-a-brief-review-of-potential-architecture-breaches
| author | gedae |
| permlink | the-dao-framework-a-brief-review-of-potential-architecture-breaches |
| voter | sandwich |
| weight | 10000 (100.00%) |
| Transaction Info | Block #1623306/Trx efc68abb7da373c2c6f366b87ce2e3c4716fa2e3 |
View Raw JSON Data
{
"block": 1623306,
"op": [
"vote",
{
"author": "gedae",
"permlink": "the-dao-framework-a-brief-review-of-potential-architecture-breaches",
"voter": "sandwich",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-05-20T21:16:48",
"trx_id": "efc68abb7da373c2c6f366b87ce2e3c4716fa2e3",
"trx_in_block": 0,
"virtual_op": 0
}gedaeupvoted (100.00%) @gedae / the-dao-framework-a-brief-review-of-potential-architecture-breaches
gedaeupvoted (100.00%) @gedae / the-dao-framework-a-brief-review-of-potential-architecture-breaches
| author | gedae |
| permlink | the-dao-framework-a-brief-review-of-potential-architecture-breaches |
| voter | gedae |
| weight | 10000 (100.00%) |
| Transaction Info | Block #1623304/Trx 0426b0db83a326cb3599dcc91c440d4a95378ae6 |
View Raw JSON Data
{
"block": 1623304,
"op": [
"vote",
{
"author": "gedae",
"permlink": "the-dao-framework-a-brief-review-of-potential-architecture-breaches",
"voter": "gedae",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-05-20T21:16:42",
"trx_id": "0426b0db83a326cb3599dcc91c440d4a95378ae6",
"trx_in_block": 0,
"virtual_op": 0
}tuck-fhemanupvoted (100.00%) @gedae / the-dao-framework-a-brief-review-of-potential-architecture-breaches
tuck-fhemanupvoted (100.00%) @gedae / the-dao-framework-a-brief-review-of-potential-architecture-breaches
| author | gedae |
| permlink | the-dao-framework-a-brief-review-of-potential-architecture-breaches |
| voter | tuck-fheman |
| weight | 10000 (100.00%) |
| Transaction Info | Block #1610597/Trx 7479244f343e3c2a305c51e358bf64f543c8a45d |
View Raw JSON Data
{
"block": 1610597,
"op": [
"vote",
{
"author": "gedae",
"permlink": "the-dao-framework-a-brief-review-of-potential-architecture-breaches",
"voter": "tuck-fheman",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-05-20T10:40:42",
"trx_id": "7479244f343e3c2a305c51e358bf64f543c8a45d",
"trx_in_block": 0,
"virtual_op": 0
}gavvetupvoted (100.00%) @gedae / the-dao-framework-a-brief-review-of-potential-architecture-breaches
gavvetupvoted (100.00%) @gedae / the-dao-framework-a-brief-review-of-potential-architecture-breaches
| author | gedae |
| permlink | the-dao-framework-a-brief-review-of-potential-architecture-breaches |
| voter | gavvet |
| weight | 10000 (100.00%) |
| Transaction Info | Block #1610292/Trx 5106a7c15493eba11eeb2e776c02b7c42d4729ab |
View Raw JSON Data
{
"block": 1610292,
"op": [
"vote",
{
"author": "gedae",
"permlink": "the-dao-framework-a-brief-review-of-potential-architecture-breaches",
"voter": "gavvet",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-05-20T10:25:27",
"trx_id": "5106a7c15493eba11eeb2e776c02b7c42d4729ab",
"trx_in_block": 0,
"virtual_op": 0
}smoothupvoted (100.00%) @gedae / the-dao-framework-a-brief-review-of-potential-architecture-breaches
smoothupvoted (100.00%) @gedae / the-dao-framework-a-brief-review-of-potential-architecture-breaches
| author | gedae |
| permlink | the-dao-framework-a-brief-review-of-potential-architecture-breaches |
| voter | smooth |
| weight | 10000 (100.00%) |
| Transaction Info | Block #1607474/Trx 7e8e6eeb7f180aaf15f85d76a6fb2e708b2c7ecf |
View Raw JSON Data
{
"block": 1607474,
"op": [
"vote",
{
"author": "gedae",
"permlink": "the-dao-framework-a-brief-review-of-potential-architecture-breaches",
"voter": "smooth",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-05-20T08:04:27",
"trx_id": "7e8e6eeb7f180aaf15f85d76a6fb2e708b2c7ecf",
"trx_in_block": 0,
"virtual_op": 0
}| author | gedae |
| body | Thank you! |
| json metadata | {} |
| parent author | bobsunday |
| parent permlink | re-gedae-the-dao-framework-a-brief-review-of-potential-architecture-breaches-20160519t043947562z |
| permlink | re-bobsunday-re-gedae-the-dao-framework-a-brief-review-of-potential-architecture-breaches-20160519t043947562z-20160520t074741396z |
| title | |
| Transaction Info | Block #1607139/Trx df8a25735ff3348438256c36553df4d70263d267 |
View Raw JSON Data
{
"block": 1607139,
"op": [
"comment",
{
"author": "gedae",
"body": "Thank you!",
"json_metadata": "{}",
"parent_author": "bobsunday",
"parent_permlink": "re-gedae-the-dao-framework-a-brief-review-of-potential-architecture-breaches-20160519t043947562z",
"permlink": "re-bobsunday-re-gedae-the-dao-framework-a-brief-review-of-potential-architecture-breaches-20160519t043947562z-20160520t074741396z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2016-05-20T07:47:42",
"trx_id": "df8a25735ff3348438256c36553df4d70263d267",
"trx_in_block": 0,
"virtual_op": 0
}josephupvoted (100.00%) @gedae / the-dao-framework-a-brief-review-of-potential-architecture-breaches
josephupvoted (100.00%) @gedae / the-dao-framework-a-brief-review-of-potential-architecture-breaches
| author | gedae |
| permlink | the-dao-framework-a-brief-review-of-potential-architecture-breaches |
| voter | joseph |
| weight | 10000 (100.00%) |
| Transaction Info | Block #1603051/Trx 6093e940d517173b7e53250ce43052247f5b755d |
View Raw JSON Data
{
"block": 1603051,
"op": [
"vote",
{
"author": "gedae",
"permlink": "the-dao-framework-a-brief-review-of-potential-architecture-breaches",
"voter": "joseph",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-05-20T04:23:15",
"trx_id": "6093e940d517173b7e53250ce43052247f5b755d",
"trx_in_block": 0,
"virtual_op": 0
}| author | gedae |
| permlink | the-dao-framework-a-brief-review-of-potential-architecture-breaches |
| voter | steempowered |
| weight | 10000 (100.00%) |
| Transaction Info | Block #1603037/Trx cf930028c46cd4f1c11d91ab550683604c5ff588 |
View Raw JSON Data
{
"block": 1603037,
"op": [
"vote",
{
"author": "gedae",
"permlink": "the-dao-framework-a-brief-review-of-potential-architecture-breaches",
"voter": "steempowered",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-05-20T04:22:33",
"trx_id": "cf930028c46cd4f1c11d91ab550683604c5ff588",
"trx_in_block": 0,
"virtual_op": 0
}nedupvoted (100.00%) @gedae / the-dao-framework-a-brief-review-of-potential-architecture-breaches
nedupvoted (100.00%) @gedae / the-dao-framework-a-brief-review-of-potential-architecture-breaches
| author | gedae |
| permlink | the-dao-framework-a-brief-review-of-potential-architecture-breaches |
| voter | ned |
| weight | 10000 (100.00%) |
| Transaction Info | Block #1599841/Trx 5f87cb03a6352acc8a9c6ebfbc971a3c46a2ea7f |
View Raw JSON Data
{
"block": 1599841,
"op": [
"vote",
{
"author": "gedae",
"permlink": "the-dao-framework-a-brief-review-of-potential-architecture-breaches",
"voter": "ned",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-05-20T01:42:45",
"trx_id": "5f87cb03a6352acc8a9c6ebfbc971a3c46a2ea7f",
"trx_in_block": 0,
"virtual_op": 0
}bobsundayupvoted (100.00%) @gedae / the-dao-framework-a-brief-review-of-potential-architecture-breaches
bobsundayupvoted (100.00%) @gedae / the-dao-framework-a-brief-review-of-potential-architecture-breaches
| author | gedae |
| permlink | the-dao-framework-a-brief-review-of-potential-architecture-breaches |
| voter | bobsunday |
| weight | 10000 (100.00%) |
| Transaction Info | Block #1574616/Trx 86954b0642526ee4ce423ff7fc26c9a2cc4dc6e9 |
View Raw JSON Data
{
"block": 1574616,
"op": [
"vote",
{
"author": "gedae",
"permlink": "the-dao-framework-a-brief-review-of-potential-architecture-breaches",
"voter": "bobsunday",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-05-19T04:39:54",
"trx_id": "86954b0642526ee4ce423ff7fc26c9a2cc4dc6e9",
"trx_in_block": 0,
"virtual_op": 0
}| author | bobsunday |
| body | we need more posts like this,.. Awesome work |
| json metadata | {} |
| parent author | gedae |
| parent permlink | the-dao-framework-a-brief-review-of-potential-architecture-breaches |
| permlink | re-gedae-the-dao-framework-a-brief-review-of-potential-architecture-breaches-20160519t043947562z |
| title | |
| Transaction Info | Block #1574614/Trx 9af8fa98dab709029759c3c0f9bcd8d9dfd31bf9 |
View Raw JSON Data
{
"block": 1574614,
"op": [
"comment",
{
"author": "bobsunday",
"body": "we need more posts like this,.. Awesome work",
"json_metadata": "{}",
"parent_author": "gedae",
"parent_permlink": "the-dao-framework-a-brief-review-of-potential-architecture-breaches",
"permlink": "re-gedae-the-dao-framework-a-brief-review-of-potential-architecture-breaches-20160519t043947562z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2016-05-19T04:39:48",
"trx_id": "9af8fa98dab709029759c3c0f9bcd8d9dfd31bf9",
"trx_in_block": 0,
"virtual_op": 0
}nikolaiupvoted (100.00%) @gedae / the-dao-framework-a-brief-review-of-potential-architecture-breaches
nikolaiupvoted (100.00%) @gedae / the-dao-framework-a-brief-review-of-potential-architecture-breaches
| author | gedae |
| permlink | the-dao-framework-a-brief-review-of-potential-architecture-breaches |
| voter | nikolai |
| weight | 10000 (100.00%) |
| Transaction Info | Block #1555375/Trx 700ddf32a173544963375f803ffec09bc232e69a |
View Raw JSON Data
{
"block": 1555375,
"op": [
"vote",
{
"author": "gedae",
"permlink": "the-dao-framework-a-brief-review-of-potential-architecture-breaches",
"voter": "nikolai",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-05-18T12:36:51",
"trx_id": "700ddf32a173544963375f803ffec09bc232e69a",
"trx_in_block": 0,
"virtual_op": 0
}gedaepublished a new post: the-dao-framework-a-brief-review-of-potential-architecture-breaches
gedaepublished a new post: the-dao-framework-a-brief-review-of-potential-architecture-breaches
| author | gedae |
| body | ### __The DAO framework: a brief review of potential architecture breaches.__ Decentralized Autonomous Organizations seem to be the wave of the future in collective funding and collective entrepreneurship. The DAO framework on the Ethereum platform is one of the latest developments in the architecture of this kind. Furthermore, a practical attempt to implement this framework - The DAO – went live recently, and the amount of funds it has already attracted seems surpassed only by the amount of online high-fiving around it. This will definitely be a very interesting case to research and observe. We became interested in analyzing theoretical possibilities of holes that can be exploited to obtain unfair results in this automated system. Here we would like to present a number of schemes that seem possible under this particular architecture. By _“holes”_ we mean peculiarities which, under certain conditions, would allow some participants to exercise bad will against others. Such a hole creates potential for situations when people need to rely on trust in an environment which aims to be trustless. Moreover, if such trust is abused an outcry for intervention by a law enforcer or regulator of some sort can become a realistic prospect. This would be a setback for a system that aims to eliminate middle-men or involvement of the state. By _“architecture”_ we mean not the program code of the solution, but the actual structure of transactions which the solution intends to implement. In this sense, architecture would be breached not by hacking the program code, but by finding ways to cheat other participants despite the underlying rules and procedures. Before we present a list of potential schemes that formed as a result of our brief analysis, we would like to introduce some terms that will be used throughout this document: __DAO__ – a decentralized autonomous organization created on Ethereum or substantially similar blockchain platform, with architecture identical to The DAO (based on The DAO Framework). __Platform__ – a particular blockchain environment in which DAO is implemented. __Platform Currency__ – cryptocurrency native to that Platform. __Early Capital__ – Platform Currency obtained before market deployment of the Platform Currency (e.g., during development or premining), at its initial stages or otherwise at a price significantly lower than the one at the time of DAO creation. Early Capital is denominated in Platform Currency. However, its distinctive feature is that it was free or extremely cheap for its owner to obtain, which will not be the case for Platform Currency available on the market at the time when a particular scheme is happening. During infant stages of a Platform’s life the problem is not how to obtain Platform Currency, but rather how to infuse it with actual value. __Early Whale__ – anyone who was able to accumulate large amounts of Early Capital. Typically this would be someone with insider ties to the Platform, but not necessarily. It’s a case when market share of a whale is gained with the timing of an early bird. __Deciding Vote__ – a situation when a person, or a group of persons, is controlling sufficient DAO tokens to tip the scales in favor of a particular proposal (and also to ensure a quorum). An extreme case of this would be controlled majority – when these tokens by themselves are sufficient to ensure both the quorum and the desired voting outcome. However, any amount of tokens large enough to seriously affect the outcome can be instrumental for schemes against DAO architecture. __Contractor__ - a person or persons acting as a “contractor” in accordance with The DAO framework terminology. From technological point of view, this is the wallet originating a particular Project proposal. If this proposal is accepted by DAO, funds required under it are sent to this wallet. From organizational point of view these are persons (individual(s) or a legal entity controlled by individual(s)) offering their services to DAO in connection with investing its capital and managing these investments. __Project__ – business undertaking proposed to DAO and financed by it (a “contract” in accordance with The DAO framework terminology). __Shell Contract__ – a Project (and a respective contract) which is created as an integral part of an attack on DAO architecture, rather than as a viable business proposition to DAO. In essence, actual purposes of the Shell Contract are different from those declared in its proposal. __Subscriber__ – someone who has bought DAO tokens during its creation phase. __Investor__ – someone who bought DAO tokens after the Creation phase (e.g., on an exchange). The main distinction between them and Subscribers is that by the time Investors obtain DAO tokens they may cost much more than the amount of Platform Currency they represented at DAO creation phase (their nominal value). Thus, in certain cases Investors would take losses while Subscribers wouldn’t (or losses for them would be greater than for Subscribers). __Attacker__ – a person or group of persons attempting to exploit a hole in DAO architecture. We’re referring to the Attacker as “he” in this document, but, of course, this can also be a “she” or “they”. If the Attacker acts through a corporate entity of some sort, specific individual(s) are still behind the intent and benefit of the attack. __Target Holders__ – holders of DAO tokens other than the Attacker (essentially – both Subscribers and Investors). We would also like to introduce definitions of two particular techniques, which do not generate any profit for the Attacker on their own, but can be a useful or essential part of a certain scheme: __Minority Wiggle__ – a situation when DAO token holders opposed to a certain decision that was accepted by DAO refrain from initiating a split. Such a situation is likely in cases when perceived risk of staying with DAO is smaller than perceived risk of splitting (e.g., missing out on profits from future Projects, as well as growing market price of DAO tokens). Such minority holders will find themselves forced to go in the direction in which the majority of DAO holders chose to go (hence, the “wiggle”). The possibility of Minority Wiggle means, among other, that DAO split is not a panacea for protecting Target Holders against adverse decisions of DAO majority. One Minority Wiggle” situation can be followed by another (or multiple others) as long as splitting from DAO keeps looking more risky than accepting the majority’s decision and staying. To further discourage splitting in case of attacks leveraging on Deciding Vote, the Attacker can manipulate Target Holders into an illusion that the majority is generally acting soundly and in good faith (e.g., by creating obviously adverse proposals and denying them). __Proxy Fragmentation__ – spreading of what is actually a single large conglomeration of Platform Currency and/or DAO tokens across multiple wallets controlled by the Attacker. This can create an illusion that a large number of unassociated decision makers is acting in a certain direction (voting on DAO proposals, subscribing to or subsequently investing in DAO tokens, paying DAO in connection with a certain Project), while in fact this is a coordinated action of the Attacker. Both spreading DAO tokens across multiple wallets and segmenting the voting process can be automated, so there are no particular limitations on the scale of Proxy Fragmentation. Now to specific scenarios: ##### __1. “Money grab”.__ _Not too elaborate in its core. However, there’s potential for extra bells and whistles._ ###### 1.A. How it happens: i Shell Contract proposed by the Attacker gets accepted by DAO. ii Funds are received by the Contractor/Attacker. iii Once the Contractor/Attacker receives the funds, he uses them for his own purposes instead of duly spending them on the Project. ###### 1.B. What it requires: i An Attacker needs his Shell Contract to be accepted. In theory, this does not require Deciding Vote as long as the proposal looks attractive enough to secure a quorum and a positive voting outcome. Nevertheless, Deciding Vote would make this task easier. ii It is also essential that Target Holders do not split from DAO after the Shell Contract is accepted - otherwise the attack will not bring any profits. So even controlled majority would not suffice for the attack to succeed (this is essentially what the split function of DAO architecture aims to tackle). This will be a psychological game, and both Proxy Fragmentation and Minority Wiggle can come into play here, alongside any publicity efforts to hype up the proposed Project. iii The Shell Contract must require: • a substantial amount of funds to be paid by DAO to Contractor up front (in the form of a deposit); and/or • A payment schedule that allows the Contractor/Attacker to accumulate and retain a substantial amount of funds from DAO before things become too suspicious to Target Holders. ###### 1.C. Unfair outcomes: i The Attacker uses DAO architecture not to develop and commercialize a proposed Project which could generate profit for DAO, but to syphon out funds accumulated in DAO. ii Target Holders will see the value of their stake depleted due to diversion of funds into the Project, while not getting a chance for returns on the investment they were expecting. iii Once this misappropriation of funds is discovered by the broad market, Target Holders (Investors in particular) stand to absorb further damage due to likely depreciation of DAO tokens. iv Any DAO holders that have split from DAO in connection with the Project in question (Investors in particular) may still see damages as the market price of tokens in the newly-formed DAO can decrease amidst the turmoil. ###### 1.D. Additional comments: While this scheme lacks conceptual sophistication, intricacies come into play when creating an appropriate façade for the operation. The main challenge for the Attacker is to lure a significant amount of Target Holders into investing in the Project and the existing history of investor fraud shows us that undertakings of this kind can be conducted with an amazing level of detail. There is also no shortage of proof that often seemingly reasonable people will be all too willing to believe in a lucrative opportunity to soundly evaluate risks looming behind it. Sophistication in masking the scheme would also be required to mitigate subsequent issues with law enforcement, which presents another important challenge for the Attacker. This is, however, not impossible either. Money can be drawn out of the Project discretely (especially if it is done within the cryptocurrency domain), and it’s possible to create a convincing impression that the Project has failed for reasons beyond the Contractor’s control. It is also not necessary to just grab the money and disappear with it – for example, the Attacker could resort to the proven practice of embezzlement endeared by so many executives (overblown salaries/expenses, use of project funds for personal needs, covert financing of side businesses, etc). These things are not that easy to trace and prosecute as it is, and given unclear legal status of DAO and obscure reporting/audit arrangements this could be impossible to tackle under this given structure. We would also like to remind that any need to rely on law enforcement already qualifies as an architectural hole for the purpose of this research (and, indeed, in the context of development of a decentralized governance environment). ##### __2. “Business grab/asset grab”.__ _It’s not all about the money._ ###### 2.A. How it happens: i A Project is accepted by DAO (not necessarily a Shell Project, as further explained below). ii Funds are received by the Contractor and are used to develop the Project, creating valuable assets. iii The Contractor-DAO relationship is terminated for whatever reasons (basically, the Contractor ceases serving as a contractor), and the former Contractor walks away while keeping control of these valuable assets. iv Since the former Contractor possesses these key assets, he is in a unique position to complete the Project, while DAO is facing a choice of either going back to the drawing board or abandoning the Project altogether. ###### 2.B. What it requires: i General situation is similar to that in scheme 1 above (the Attacker manages to get a Project proposal accepted by DAO, while avoiding split by a significant number of Target Holders). Here, however, a Project must feature a viable underlying business idea (which, in turn, helps ensure that these previous conditions are met). ii The Project must heavily rely upon certain key assets (intellectual property, production prototypes, brand recognition, etc) for its success. It is also very advantageous for the Contractor if information and expertise possessed by him are unique in the context of the Project (e.g., through key personnel, a network of partnerships or simply hands-on experience gained during the development process). iii DAO should be unaware of existence of these key assets or is unable to claim them. For instance: • The Contractor registers these assets in his own name. • The Contractor withholds information on existence of these assets from DAO. • The DAO is unable to prove (in legal domain) its rights to these assets because of unclear nature of DAO’s legal persona or its relationship with the Contractor. After all, the Contractor is a distinct private person or legal entity with a clear place in contemporary legal system. DAO, on the other hand, could face a number of hurdles while trying to protect, assert or register any rights within this system. ###### 2.C. Unfair outcomes: i The Attacker is essentially piggy-backing DAO, using its funds to create tangible and intangible assets vital for the Project, then taking the Project away from DAO and completing it to his own benefit. ii Target Holders will see their capital depleted by payment of funds to the Project, while being essentially cut off from returns on this investment. iii Target Holders (especially Investors) may absorb further damage as this unfolding of events negatively impacts DAO token pricing on the market. iv Those DAO holders that have split into a new DAO in connection with the Project may see their respective tokens lose in price as well amidst the general turmoil. ###### 2.D. Additional comments: A peculiar feature of this scenario is that it’s not necessarily a pre-planned attack. Departure of the Contractor from the Project may be a result of actual disagreement on certain issues and not a premeditated extortion attempt. “Strategic business partners” today can turn into bitter enemies tomorrow, with each side totally convinced that the other side is the devil. For instance, if DAO fires the Contractor due to some disagreement (after all this hard work and all those sleepless nights), he may be compelled to feel justified in bypassing DAO and finishing the Project to his own benefit and to forget that none of this would be possible without DAO funding to begin with. Of course, whether it is a carefully conceived attack, or an emotional move, to a non-involved objective observer the economic outcome of this situation would still look the same. The intentional Attacker could still use a Shell Contract. However, its shell nature would be not that there is no value in the Project (it must be there or the whole scheme makes no economic sense), but that it is structured in such a way as to facilitate expropriation by the Attacker of the Project’s key assets. ##### __3. “Pump and dump”.__ _A classic trick for a new paradigm._ ###### 3.A. How it happens: i The Attacker proposes a Shell Contract which is accepted by DAO. ii The Attacker sends funds out of his Early Capital to DAO as if it was DAO’s share of profits generated by the Project. This creates an illusion of success of the Project behind the Shell Contract. iii This boosts market confidence in DAO as a going concern and drives demand for DAO tokens (which begin circulating on exchanges after the creation phase is complete). The bandwagon/FOMO effect kicks in. iv The Attacker sells off his DAO tokens to Investors at peak prices and bids everyone farewell. ###### 3.B. What it requires: i The Attacker needs to be an Early Whale. ii The Shell Contract proposal must be attractive enough to be accepted by DAO and not scare Target Holders into a split. It helps that the Attacker can bombard DAO with consecutive proposals until one of them gets accepted – the trick here is in the ability to convincingly mimic success of a Project afterwards, specific nature of a Shell Contract is not that important. iii Proxy Fragmentation will probably be used to make sure inflow of funds looks natural in the context of the Project. ###### 3.C. Unfair outcomes: i The Attacker attracts assets from outside the Platform and effectively exchanges his Early Capital (firstly converted into DAO tokens) against them without creating any actual value for Investors, who in turn purchase DAO tokens at a price that has no underlying economic justification. ii At the conclusion of the scheme the price of DAO tokens plunges leaving Investors to absorb losses. The drop is likely to exceed the size of price inflation caused by the Attacker’s manipulations as the general confidence in DAO will be challenged. This may also adversely affect Subscribers. iii Likely spill-over effect into the Platform Currency market may amplify losses for Investors and create additional losses for Subscribers (and bystanders holding the Platform Currency). ###### 3.D. Additional comments: A certain degree of prudence could be required on the part of the Attacker so that his injections into the market do not dampen the prices prematurely. This, however, can be managed and, in case the demand is inflated to a large enough degree, may not be much of a concern at all. A perk of this scheme is that it will be virtually impossible for other market participants to know what (let alone who) exactly hit’em, unless the Attacker is completely careless. ##### __4. “Indirect pump and dump” aka “The empty wheelbarrow”.__ _An extra twist for a classic trick (in a new paradigm)._ ###### 4.A. How it happens: i The Attacker uses his Early Capital to buy a large amount of DAO tokens, creating an impression of massive inflow of Subscribers. ii This impression boosts public interest in DAO, prompting others to buy tokens while creation is still in progress. iii Potential Subscribers need to obtain Platform Currency in order to convert it into DAO tokens. Demand for Platform Currency swells, and its price vis-à-vis other currencies (whether fiat or crypto) increases along with it. The hype spurred by the apparent inflow of funds into DAO creation is the actual driver of this price increase. iv The Attacker sells off his Platform Currency during this period of peaking prices, essentially exchanging his Early Capital for funds attracted from outside the Platform. v The Attacker can follow this up with selling off of his DAO tokens for further profits. ###### 4.B. What it requires: i The Attacker has to be an Early Whale. ii The Attacker will probably need to resort to Proxy Fragmentation, otherwise it will be apparent that a large inflow of funds into DAO creation comes from a single source. ###### 4.C. Unfair outcomes: i The Attacker artificially inflates value of the Platform Currency. He then disposes of the Platform Currency with large profit. Basically, the Attacker receives value out of thin air – his Early Capital is worth nothing, unless he compels others to exchange it for resources extrinsic to the Platform. ii Those who bought the Platform Currency during DAO creation (including other Subscribers) end up taking losses as the bubble driven by false expectations from DAO bursts. iii Damage will be further aggravated by undermined market confidence, both in this particular DAO and in the Platform in general. ###### 4.D. Additional comments: While a large inflow of apparently dispersed capital at the creation phase can be a strong driver for prospective Subscribers by itself, the attack would likely prompt additional manipulations aimed at generating hype and further inflating expectations. For instance, the Attacker could also provide for a Shell Contract (or multiple Shell Contracts) to create an impression of upcoming proposals with strong investment prospects for DAO. Since such Shell Contracts have not been formally submitted to or accepted by DAO, no obligation on the part of the Attacker as the prospective Contractor would actually exist. Just as with the previous scheme, everyone else will hardly know what happened or who exactly benefited. The twist here is that the Attacker uses secondary medium (Platform Currency rather than DAO tokens) for profiteering, which can further muddy up any understanding of events behind the price fluctuations. ##### __5. “Pump and grab”.__ _Hybrid technology_ ###### 5.A. How it’s done: i This scheme is essentially a hybrid between scenario 3 and scenario 1. ii The Attacker uses funds invested into his Shell Contract, supplemented by funds out of his Early Capital to mimic return on investment and some extra profit. iii Establishing himself as a trustworthy Contractor in this manner the Attacker proposes another Shell Contract (for a Project requiring greater funding). iv From this point on events unfold along the lines of scheme 1. v Alternatively, this scheme can be implemented within a single Project that has payments to Contractor tied to milestones or some commercial performance metrics. The Attacker could use contract funds and/or his Early Capital to mimic successful performance of a certain metric (achievement of a certain milestone) and to unlock further (larger) funding and then grab the money. As Shell Contract would require less money up-front and more money once the Project shows some positive performance, Target Holders would be more likely to go for it in the first place. ###### 5.B. What it requires: i Conditions are generally the same as under scheme 1 (with certain nuances pertaining to the structure of the Shell Contract), however in addition: • The Attacker needs to be an Early Wail, or • Difference in funding size between the respective Projects (or milestones of a Project) has to be large enough to justify the Attacker’s expenses for initial simulation of profits. ###### 5.C. Unfair outcomes: i Same as under scheme 1; ii It could be argued that damage to market confidence in DAO is potentially greater under this scheme, as fake nature of what was perceived as profits will be particularly discouraging. __Final points.__ We’d like to stress that we make no assumptions or predictions on whether the risks we pin-point here will or will not come into existence with the current practical incarnation of this solution - The DAO (if they do, it’ll be quite spectacular though). In this paper we are focusing only on the underlying architecture, although me may look at how this translates to the particular case of The DAO later on. This is by no means an advice to invest in The DAO or refrain from such investment. We do not warrant or represent that our analysis is exhaustive or error-free, and we welcome any constructive feedback on it (including any other potential scenarios of abuse, or any shortcomings in our analysis). We may revise and expand this document with time. A discussion of how (and whether) the flaws we’ve described above could be tackled in subsequent versions of decentralized organization architecture is beyond the scope of this particular document, although it is of course an extremely fascinating one. This document was mainly driven by curiosity. Still, there is another important consideration that prompts an informed discussion on the matter. Decentralized collective action vehicles are a tremendous prospect – whether in a non-profit, or for-profit context. This instrument can be engineered with varying degree of diligence, and can be used both with good will and with bad will. Furthermore, the way in which it is implemented and used will affect the experimental decentralized environment in which it exists. Freedom from middle-men, including any regulators or other state bureaucrats, is the main advantage offered by decentralized solutions in general and DAO in particular. However, bureaucracy, or, at least, common-place toleration of it, did not arise out of vacuum. It is rooted in people’s fear of being mistreated and cheated by others. Any instance when fairness has been compromised serves as justification for people to submit a part of their rights to a third party (e.g., the state apparatus) in exchange for certain protections (whether real or implied). Any instance of fairness being compromised in the crypto-domain will likely result in a further push to regulate it. The golden argument against involvement of any middlemen (including the state) in a decentralized system is the fact that such involvement is not necessary – participants are already protected by the very nature of the system which runs all of the transactions on a predetermined automated basis, in a “trustless”, “provably fair” environment. This argument will be undermined if “provably fair” turns out to be “probably fair”. Any potential for imposition of bad will on other participants in this system, let alone any cases of people actually willing and managing to take advantage of this potential, will weaken the position of those in favor of a truly deregulated and decentralized platform for human interaction. |
| json metadata | {} |
| parent author | |
| parent permlink | crypto-news |
| permlink | the-dao-framework-a-brief-review-of-potential-architecture-breaches |
| title | The DAO framework: a brief review of potential architecture breaches. |
| Transaction Info | Block #1553103/Trx 333c6eb411d135cbde8a77cdeacb8a98ff24249d |
View Raw JSON Data
{
"block": 1553103,
"op": [
"comment",
{
"author": "gedae",
"body": "### __The DAO framework: a brief review of potential architecture breaches.__\n\n\nDecentralized Autonomous Organizations seem to be the wave of the future in collective funding and collective entrepreneurship. The DAO framework on the Ethereum platform is one of the latest developments in the architecture of this kind. Furthermore, a practical attempt to implement this framework - The DAO – went live recently, and the amount of funds it has already attracted seems surpassed only by the amount of online high-fiving around it. This will definitely be a very interesting case to research and observe. We became interested in analyzing theoretical possibilities of holes that can be exploited to obtain unfair results in this automated system. Here we would like to present a number of schemes that seem possible under this particular architecture.\n\nBy _“holes”_ we mean peculiarities which, under certain conditions, would allow some participants to exercise bad will against others. Such a hole creates potential for situations when people need to rely on trust in an environment which aims to be trustless. Moreover, if such trust is abused an outcry for intervention by a law enforcer or regulator of some sort can become a realistic prospect. This would be a setback for a system that aims to eliminate middle-men or involvement of the state.\n\nBy _“architecture”_ we mean not the program code of the solution, but the actual structure of transactions which the solution intends to implement. In this sense, architecture would be breached not by hacking the program code, but by finding ways to cheat other participants despite the underlying rules and procedures.\n\nBefore we present a list of potential schemes that formed as a result of our brief analysis, we would like to introduce some terms that will be used throughout this document:\n\n\n__DAO__ – a decentralized autonomous organization created on Ethereum or substantially similar blockchain platform, with architecture identical to The DAO (based on The DAO Framework).\n\n__Platform__ – a particular blockchain environment in which DAO is implemented.\n\n__Platform Currency__ – cryptocurrency native to that Platform.\n\n__Early Capital__ – Platform Currency obtained before market deployment of the Platform Currency (e.g., during development or premining), at its initial stages or otherwise at a price significantly lower than the one at the time of DAO creation. Early Capital is denominated in Platform Currency. However, its distinctive feature is that it was free or extremely cheap for its owner to obtain, which will not be the case for Platform Currency available on the market at the time when a particular scheme is happening. During infant stages of a Platform’s life the problem is not how to obtain Platform Currency, but rather how to infuse it with actual value. \n\n__Early Whale__ – anyone who was able to accumulate large amounts of Early Capital. Typically this would be someone with insider ties to the Platform, but not necessarily. It’s a case when market share of a whale is gained with the timing of an early bird.\n\n__Deciding Vote__ – a situation when a person, or a group of persons, is controlling sufficient DAO tokens to tip the scales in favor of a particular proposal (and also to ensure a quorum). An extreme case of this would be controlled majority – when these tokens by themselves are sufficient to ensure both the quorum and the desired voting outcome. However, any amount of tokens large enough to seriously affect the outcome can be instrumental for schemes against DAO architecture. \n\n__Contractor__ - a person or persons acting as a “contractor” in accordance with The DAO framework terminology. From technological point of view, this is the wallet originating a particular Project proposal. If this proposal is accepted by DAO, funds required under it are sent to this wallet. From organizational point of view these are persons (individual(s) or a legal entity controlled by individual(s)) offering their services to DAO in connection with investing its capital and managing these investments.\n\n__Project__ – business undertaking proposed to DAO and financed by it (a “contract” in accordance with The DAO framework terminology).\n\n__Shell Contract__ – a Project (and a respective contract) which is created as an integral part of an attack on DAO architecture, rather than as a viable business proposition to DAO. In essence, actual purposes of the Shell Contract are different from those declared in its proposal.\n\n__Subscriber__ – someone who has bought DAO tokens during its creation phase.\n\n__Investor__ – someone who bought DAO tokens after the Creation phase (e.g., on an exchange). The main distinction between them and Subscribers is that by the time Investors obtain DAO tokens they may cost much more than the amount of Platform Currency they represented at DAO creation phase (their nominal value). Thus, in certain cases Investors would take losses while Subscribers wouldn’t (or losses for them would be greater than for Subscribers).\n\n__Attacker__ – a person or group of persons attempting to exploit a hole in DAO architecture. We’re referring to the Attacker as “he” in this document, but, of course, this can also be a “she” or “they”. If the Attacker acts through a corporate entity of some sort, specific individual(s) are still behind the intent and benefit of the attack.\n\n__Target Holders__ – holders of DAO tokens other than the Attacker (essentially – both Subscribers and Investors).\n\n\n\nWe would also like to introduce definitions of two particular techniques, which do not generate any profit for the Attacker on their own, but can be a useful or essential part of a certain scheme:\n\n\n__Minority Wiggle__ – a situation when DAO token holders opposed to a certain decision that was accepted by DAO refrain from initiating a split. Such a situation is likely in cases when perceived risk of staying with DAO is smaller than perceived risk of splitting (e.g., missing out on profits from future Projects, as well as growing market price of DAO tokens). Such minority holders will find themselves forced to go in the direction in which the majority of DAO holders chose to go (hence, the “wiggle”).\nThe possibility of Minority Wiggle means, among other, that DAO split is not a panacea for protecting Target Holders against adverse decisions of DAO majority.\nOne Minority Wiggle” situation can be followed by another (or multiple others) as long as splitting from DAO keeps looking more risky than accepting the majority’s decision and staying. To further discourage splitting in case of attacks leveraging on Deciding Vote, the Attacker can manipulate Target Holders into an illusion that the majority is generally acting soundly and in good faith (e.g., by creating obviously adverse proposals and denying them).\n\n__Proxy Fragmentation__ – spreading of what is actually a single large conglomeration of Platform Currency and/or DAO tokens across multiple wallets controlled by the Attacker. This can create an illusion that a large number of unassociated decision makers is acting in a certain direction (voting on DAO proposals, subscribing to or subsequently investing in DAO tokens, paying DAO in connection with a certain Project), while in fact this is a coordinated action of the Attacker. Both spreading DAO tokens across multiple wallets and segmenting the voting process can be automated, so there are no particular limitations on the scale of Proxy Fragmentation.\n\n\nNow to specific scenarios:\n\n\n##### __1.\t“Money grab”.__\n_Not too elaborate in its core. However, there’s potential for extra bells and whistles._\n\n\n###### 1.A.\tHow it happens:\n\ni\tShell Contract proposed by the Attacker gets accepted by DAO.\nii\tFunds are received by the Contractor/Attacker.\niii\tOnce the Contractor/Attacker receives the funds, he uses them for his own purposes instead of duly spending them on the Project.\n\n\n###### 1.B.\tWhat it requires: \n\ni\tAn Attacker needs his Shell Contract to be accepted. In theory, this does not require Deciding Vote as long as the proposal looks attractive enough to secure a quorum and a positive voting outcome. Nevertheless, Deciding Vote would make this task easier. \n\nii\t It is also essential that Target Holders do not split from DAO after the Shell Contract is accepted - otherwise the attack will not bring any profits. So even controlled majority would not suffice for the attack to succeed (this is essentially what the split function of DAO architecture aims to tackle). This will be a psychological game, and both Proxy Fragmentation and Minority Wiggle can come into play here, alongside any publicity efforts to hype up the proposed Project.\n\niii\tThe Shell Contract must require:\n•\ta substantial amount of funds to be paid by DAO to Contractor up front (in the form of a deposit); and/or\n•\tA payment schedule that allows the Contractor/Attacker to accumulate and retain a substantial amount of funds from DAO before things become too suspicious to Target Holders.\n\n\n###### 1.C.\tUnfair outcomes:\ni\tThe Attacker uses DAO architecture not to develop and commercialize a proposed Project which could generate profit for DAO, but to syphon out funds accumulated in DAO.\nii\tTarget Holders will see the value of their stake depleted due to diversion of funds into the Project, while not getting a chance for returns on the investment they were expecting.\niii\tOnce this misappropriation of funds is discovered by the broad market, Target Holders (Investors in particular) stand to absorb further damage due to likely depreciation of DAO tokens.\niv\tAny DAO holders that have split from DAO in connection with the Project in question (Investors in particular) may still see damages as the market price of tokens in the newly-formed DAO can decrease amidst the turmoil. \n\n###### 1.D.\tAdditional comments: \nWhile this scheme lacks conceptual sophistication, intricacies come into play when creating an appropriate façade for the operation. The main challenge for the Attacker is to lure a significant amount of Target Holders into investing in the Project and the existing history of investor fraud shows us that undertakings of this kind can be conducted with an amazing level of detail. There is also no shortage of proof that often seemingly reasonable people will be all too willing to believe in a lucrative opportunity to soundly evaluate risks looming behind it. \nSophistication in masking the scheme would also be required to mitigate subsequent issues with law enforcement, which presents another important challenge for the Attacker. This is, however, not impossible either. Money can be drawn out of the Project discretely (especially if it is done within the cryptocurrency domain), and it’s possible to create a convincing impression that the Project has failed for reasons beyond the Contractor’s control. It is also not necessary to just grab the money and disappear with it – for example, the Attacker could resort to the proven practice of embezzlement endeared by so many executives (overblown salaries/expenses, use of project funds for personal needs, covert financing of side businesses, etc). These things are not that easy to trace and prosecute as it is, and given unclear legal status of DAO and obscure reporting/audit arrangements this could be impossible to tackle under this given structure.\nWe would also like to remind that any need to rely on law enforcement already qualifies as an architectural hole for the purpose of this research (and, indeed, in the context of development of a decentralized governance environment).\n\n\n##### __2.\t“Business grab/asset grab”.__\n_It’s not all about the money._\n\n###### 2.A.\tHow it happens: \n\ni\tA Project is accepted by DAO (not necessarily a Shell Project, as further explained below).\nii\tFunds are received by the Contractor and are used to develop the Project, creating valuable assets.\niii\tThe Contractor-DAO relationship is terminated for whatever reasons (basically, the Contractor ceases serving as a contractor), and the former Contractor walks away while keeping control of these valuable assets. \niv\tSince the former Contractor possesses these key assets, he is in a unique position to complete the Project, while DAO is facing a choice of either going back to the drawing board or abandoning the Project altogether.\n\n###### 2.B.\tWhat it requires: \n\ni\tGeneral situation is similar to that in scheme 1 above (the Attacker manages to get a Project proposal accepted by DAO, while avoiding split by a significant number of Target Holders). Here, however, a Project must feature a viable underlying business idea (which, in turn, helps ensure that these previous conditions are met).\nii\tThe Project must heavily rely upon certain key assets (intellectual property, production prototypes, brand recognition, etc) for its success. It is also very advantageous for the Contractor if information and expertise possessed by him are unique in the context of the Project (e.g., through key personnel, a network of partnerships or simply hands-on experience gained during the development process).\niii\tDAO should be unaware of existence of these key assets or is unable to claim them. For instance:\n•\tThe Contractor registers these assets in his own name.\n•\tThe Contractor withholds information on existence of these assets from DAO.\n•\tThe DAO is unable to prove (in legal domain) its rights to these assets because of unclear nature of DAO’s legal persona or its relationship with the Contractor. After all, the Contractor is a distinct private person or legal entity with a clear place in contemporary legal system. DAO, on the other hand, could face a number of hurdles while trying to protect, assert or register any rights within this system.\n\n\n###### 2.C.\tUnfair outcomes:\ni\tThe Attacker is essentially piggy-backing DAO, using its funds to create tangible and intangible assets vital for the Project, then taking the Project away from DAO and completing it to his own benefit.\nii\tTarget Holders will see their capital depleted by payment of funds to the Project, while being essentially cut off from returns on this investment.\niii\tTarget Holders (especially Investors) may absorb further damage as this unfolding of events negatively impacts DAO token pricing on the market.\niv\tThose DAO holders that have split into a new DAO in connection with the Project may see their respective tokens lose in price as well amidst the general turmoil.\n\n###### 2.D.\t Additional comments:\nA peculiar feature of this scenario is that it’s not necessarily a pre-planned attack. Departure of the Contractor from the Project may be a result of actual disagreement on certain issues and not a premeditated extortion attempt. “Strategic business partners” today can turn into bitter enemies tomorrow, with each side totally convinced that the other side is the devil. For instance, if DAO fires the Contractor due to some disagreement (after all this hard work and all those sleepless nights), he may be compelled to feel justified in bypassing DAO and finishing the Project to his own benefit and to forget that none of this would be possible without DAO funding to begin with. Of course, whether it is a carefully conceived attack, or an emotional move, to a non-involved objective observer the economic outcome of this situation would still look the same.\nThe intentional Attacker could still use a Shell Contract. However, its shell nature would be not that there is no value in the Project (it must be there or the whole scheme makes no economic sense), but that it is structured in such a way as to facilitate expropriation by the Attacker of the Project’s key assets.\n\n\n##### __3.\t“Pump and dump”.__\n_A classic trick for a new paradigm._\n\n###### 3.A.\t How it happens:\ni\tThe Attacker proposes a Shell Contract which is accepted by DAO.\nii\tThe Attacker sends funds out of his Early Capital to DAO as if it was DAO’s share of profits generated by the Project. This creates an illusion of success of the Project behind the Shell Contract.\niii\tThis boosts market confidence in DAO as a going concern and drives demand for DAO tokens (which begin circulating on exchanges after the creation phase is complete). The bandwagon/FOMO effect kicks in.\niv\tThe Attacker sells off his DAO tokens to Investors at peak prices and bids everyone farewell.\n\n###### 3.B.\tWhat it requires:\ni\tThe Attacker needs to be an Early Whale.\nii\tThe Shell Contract proposal must be attractive enough to be accepted by DAO and not scare Target Holders into a split. It helps that the Attacker can bombard DAO with consecutive proposals until one of them gets accepted – the trick here is in the ability to convincingly mimic success of a Project afterwards, specific nature of a Shell Contract is not that important.\niii\tProxy Fragmentation will probably be used to make sure inflow of funds looks natural in the context of the Project.\n\n\n###### 3.C.\tUnfair outcomes:\ni\tThe Attacker attracts assets from outside the Platform and effectively exchanges his Early Capital (firstly converted into DAO tokens) against them without creating any actual value for Investors, who in turn purchase DAO tokens at a price that has no underlying economic justification.\nii\tAt the conclusion of the scheme the price of DAO tokens plunges leaving Investors to absorb losses. The drop is likely to exceed the size of price inflation caused by the Attacker’s manipulations as the general confidence in DAO will be challenged. This may also adversely affect Subscribers.\niii\tLikely spill-over effect into the Platform Currency market may amplify losses for Investors and create additional losses for Subscribers (and bystanders holding the Platform Currency).\n\n###### 3.D.\tAdditional comments:\nA certain degree of prudence could be required on the part of the Attacker so that his injections into the market do not dampen the prices prematurely. This, however, can be managed and, in case the demand is inflated to a large enough degree, may not be much of a concern at all.\nA perk of this scheme is that it will be virtually impossible for other market participants to know what (let alone who) exactly hit’em, unless the Attacker is completely careless.\n\n\n\n##### __4.\t“Indirect pump and dump” aka “The empty wheelbarrow”.__\n_An extra twist for a classic trick (in a new paradigm)._\n\n###### 4.A.\tHow it happens:\ni\tThe Attacker uses his Early Capital to buy a large amount of DAO tokens, creating an impression of massive inflow of Subscribers.\nii\tThis impression boosts public interest in DAO, prompting others to buy tokens while creation is still in progress.\niii\tPotential Subscribers need to obtain Platform Currency in order to convert it into DAO tokens. Demand for Platform Currency swells, and its price vis-à-vis other currencies (whether fiat or crypto) increases along with it. The hype spurred by the apparent inflow of funds into DAO creation is the actual driver of this price increase.\niv\tThe Attacker sells off his Platform Currency during this period of peaking prices, essentially exchanging his Early Capital for funds attracted from outside the Platform.\nv\tThe Attacker can follow this up with selling off of his DAO tokens for further profits.\n\n###### 4.B.\tWhat it requires:\ni\tThe Attacker has to be an Early Whale. \nii\tThe Attacker will probably need to resort to Proxy Fragmentation, otherwise it will be apparent that a large inflow of funds into DAO creation comes from a single source.\n\n###### 4.C.\tUnfair outcomes:\ni\tThe Attacker artificially inflates value of the Platform Currency. He then disposes of the Platform Currency with large profit. Basically, the Attacker receives value out of thin air – his Early Capital is worth nothing, unless he compels others to exchange it for resources extrinsic to the Platform.\nii\tThose who bought the Platform Currency during DAO creation (including other Subscribers) end up taking losses as the bubble driven by false expectations from DAO bursts.\niii\tDamage will be further aggravated by undermined market confidence, both in this particular DAO and in the Platform in general.\n\n###### 4.D.\tAdditional comments:\nWhile a large inflow of apparently dispersed capital at the creation phase can be a strong driver for prospective Subscribers by itself, the attack would likely prompt additional manipulations aimed at generating hype and further inflating expectations. For instance, the Attacker could also provide for a Shell Contract (or multiple Shell Contracts) to create an impression of upcoming proposals with strong investment prospects for DAO. Since such Shell Contracts have not been formally submitted to or accepted by DAO, no obligation on the part of the Attacker as the prospective Contractor would actually exist.\nJust as with the previous scheme, everyone else will hardly know what happened or who exactly benefited. The twist here is that the Attacker uses secondary medium (Platform Currency rather than DAO tokens) for profiteering, which can further muddy up any understanding of events behind the price fluctuations.\n\n\n##### __5.\t“Pump and grab”.__\n_Hybrid technology_\n\n###### 5.A.\tHow it’s done:\ni\tThis scheme is essentially a hybrid between scenario 3 and scenario 1.\nii\tThe Attacker uses funds invested into his Shell Contract, supplemented by funds out of his Early Capital to mimic return on investment and some extra profit.\niii\tEstablishing himself as a trustworthy Contractor in this manner the Attacker proposes another Shell Contract (for a Project requiring greater funding).\niv\tFrom this point on events unfold along the lines of scheme 1.\nv\tAlternatively, this scheme can be implemented within a single Project that has payments to Contractor tied to milestones or some commercial performance metrics. The Attacker could use contract funds and/or his Early Capital to mimic successful performance of a certain metric (achievement of a certain milestone) and to unlock further (larger) funding and then grab the money. As Shell Contract would require less money up-front and more money once the Project shows some positive performance, Target Holders would be more likely to go for it in the first place. \n\n###### 5.B.\tWhat it requires:\ni\tConditions are generally the same as under scheme 1 (with certain nuances pertaining to the structure of the Shell Contract), however in addition:\n•\tThe Attacker needs to be an Early Wail, or\n•\tDifference in funding size between the respective Projects (or milestones of a Project) has to be large enough to justify the Attacker’s expenses for initial simulation of profits.\n\n###### 5.C.\tUnfair outcomes:\ni\tSame as under scheme 1;\nii\tIt could be argued that damage to market confidence in DAO is potentially greater under this scheme, as fake nature of what was perceived as profits will be particularly discouraging.\n\n\n\n__Final points.__\n\nWe’d like to stress that we make no assumptions or predictions on whether the risks we pin-point here will or will not come into existence with the current practical incarnation of this solution - The DAO (if they do, it’ll be quite spectacular though). In this paper we are focusing only on the underlying architecture, although me may look at how this translates to the particular case of The DAO later on. This is by no means an advice to invest in The DAO or refrain from such investment.\n\nWe do not warrant or represent that our analysis is exhaustive or error-free, and we welcome any constructive feedback on it (including any other potential scenarios of abuse, or any shortcomings in our analysis). We may revise and expand this document with time.\n\nA discussion of how (and whether) the flaws we’ve described above could be tackled in subsequent versions of decentralized organization architecture is beyond the scope of this particular document, although it is of course an extremely fascinating one.\n\nThis document was mainly driven by curiosity. Still, there is another important consideration that prompts an informed discussion on the matter.\n\nDecentralized collective action vehicles are a tremendous prospect – whether in a non-profit, or for-profit context. This instrument can be engineered with varying degree of diligence, and can be used both with good will and with bad will. Furthermore, the way in which it is implemented and used will affect the experimental decentralized environment in which it exists. Freedom from middle-men, including any regulators or other state bureaucrats, is the main advantage offered by decentralized solutions in general and DAO in particular. However, bureaucracy, or, at least, common-place toleration of it, did not arise out of vacuum. It is rooted in people’s fear of being mistreated and cheated by others. Any instance when fairness has been compromised serves as justification for people to submit a part of their rights to a third party (e.g., the state apparatus) in exchange for certain protections (whether real or implied). Any instance of fairness being compromised in the crypto-domain will likely result in a further push to regulate it. \n\nThe golden argument against involvement of any middlemen (including the state) in a decentralized system is the fact that such involvement is not necessary – participants are already protected by the very nature of the system which runs all of the transactions on a predetermined automated basis, in a “trustless”, “provably fair” environment. This argument will be undermined if “provably fair” turns out to be “probably fair”. Any potential for imposition of bad will on other participants in this system, let alone any cases of people actually willing and managing to take advantage of this potential, will weaken the position of those in favor of a truly deregulated and decentralized platform for human interaction.",
"json_metadata": "{}",
"parent_author": "",
"parent_permlink": "crypto-news",
"permlink": "the-dao-framework-a-brief-review-of-potential-architecture-breaches",
"title": "The DAO framework: a brief review of potential architecture breaches."
}
],
"op_in_trx": 0,
"timestamp": "2016-05-18T10:43:09",
"trx_id": "333c6eb411d135cbde8a77cdeacb8a98ff24249d",
"trx_in_block": 0,
"virtual_op": 0
}| active | {"account_auths":[],"key_auths":[["STM6NgmfDgDH5QeRoE15ajy2Xc4Yrk9yFhXP86AydC4F95tzVcqHH",1]],"weight_threshold":1} |
| creator | steem |
| fee | 10.000 STEEM |
| json metadata | |
| memo key | STM7Gw4DxbfMyfEfduwkS2yt8w6nCvErjr8dWsZyfjrBjhfX49HQF |
| new account name | gedae |
| owner | {"account_auths":[],"key_auths":[["STM6AQWBRhGNrULYw3HaZFBNz3bLa9tbZWCnAZJzgFD2eK6XUv7N9",1]],"weight_threshold":1} |
| posting | {"account_auths":[],"key_auths":[["STM5qSVM63oM65GAhX3ytgDaKrFw74qTfJ2WycD4ERpX59YvBwyaf",1]],"weight_threshold":1} |
| Transaction Info | Block #1552306/Trx e4f2cb529d1c48cf6d046cedc0a28d6778d0db1b |
View Raw JSON Data
{
"block": 1552306,
"op": [
"account_create",
{
"active": {
"account_auths": [],
"key_auths": [
[
"STM6NgmfDgDH5QeRoE15ajy2Xc4Yrk9yFhXP86AydC4F95tzVcqHH",
1
]
],
"weight_threshold": 1
},
"creator": "steem",
"fee": "10.000 STEEM",
"json_metadata": "",
"memo_key": "STM7Gw4DxbfMyfEfduwkS2yt8w6nCvErjr8dWsZyfjrBjhfX49HQF",
"new_account_name": "gedae",
"owner": {
"account_auths": [],
"key_auths": [
[
"STM6AQWBRhGNrULYw3HaZFBNz3bLa9tbZWCnAZJzgFD2eK6XUv7N9",
1
]
],
"weight_threshold": 1
},
"posting": {
"account_auths": [],
"key_auths": [
[
"STM5qSVM63oM65GAhX3ytgDaKrFw74qTfJ2WycD4ERpX59YvBwyaf",
1
]
],
"weight_threshold": 1
}
}
],
"op_in_trx": 0,
"timestamp": "2016-05-18T10:03:18",
"trx_id": "e4f2cb529d1c48cf6d046cedc0a28d6778d0db1b",
"trx_in_block": 0,
"virtual_op": 0
}Manabar
Voting Power100.00%
Downvote Power100.00%
Resource Credits100.00%
Reputation Progress83.19%
{
"voting_manabar": {
"current_mana": 9949,
"last_update_time": 1469481501
},
"downvote_manabar": {
"current_mana": 0,
"last_update_time": 1463565798
},
"rc_account": {
"account": "gedae",
"max_rc": "3206001860742",
"max_rc_creation_adjustment": {
"amount": "2020748973",
"nai": "@@000000037",
"precision": 6
},
"rc_manabar": {
"current_mana": "3206001860742",
"last_update_time": 1537887600
}
}
}Account Metadata
| POSTING JSON METADATA | |
| None | |
| JSON METADATA | |
| None |
{
"posting_json_metadata": {},
"json_metadata": {}
}Auth Keys
Owner
Single Signature
Public Keys
STM6AQWBRhGNrULYw3HaZFBNz3bLa9tbZWCnAZJzgFD2eK6XUv7N91/1
Active
Single Signature
Public Keys
STM6NgmfDgDH5QeRoE15ajy2Xc4Yrk9yFhXP86AydC4F95tzVcqHH1/1
Posting
Single Signature
Public Keys
STM5qSVM63oM65GAhX3ytgDaKrFw74qTfJ2WycD4ERpX59YvBwyaf1/1
Memo
STM7Gw4DxbfMyfEfduwkS2yt8w6nCvErjr8dWsZyfjrBjhfX49HQF
{
"owner": {
"account_auths": [],
"key_auths": [
[
"STM6AQWBRhGNrULYw3HaZFBNz3bLa9tbZWCnAZJzgFD2eK6XUv7N9",
1
]
],
"weight_threshold": 1
},
"active": {
"account_auths": [],
"key_auths": [
[
"STM6NgmfDgDH5QeRoE15ajy2Xc4Yrk9yFhXP86AydC4F95tzVcqHH",
1
]
],
"weight_threshold": 1
},
"posting": {
"account_auths": [],
"key_auths": [
[
"STM5qSVM63oM65GAhX3ytgDaKrFw74qTfJ2WycD4ERpX59YvBwyaf",
1
]
],
"weight_threshold": 1
},
"memo": "STM7Gw4DxbfMyfEfduwkS2yt8w6nCvErjr8dWsZyfjrBjhfX49HQF"
}Witness Votes
0 / 30
No active witness votes.
[]