VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS29.36%
Net Worth
0.062USD
STEEM
0.007STEEM
SBD
0.111SBD
Effective Power
5.001SP
├── Own SP
0.125SP
└── Incoming DelegationsDeleg
+4.876SP
Detailed Balance
| STEEM | ||
| balance | 0.000STEEM | STEEM |
| market_balance | 0.000STEEM | STEEM |
| savings_balance | 0.000STEEM | STEEM |
| reward_steem_balance | 0.007STEEM | STEEM |
| STEEM POWER | ||
| Own SP | 0.125SP | SP |
| Delegated Out | 0.000SP | SP |
| Delegation In | 4.876SP | SP |
| Effective Power | 5.001SP | SP |
| Reward SP (pending) | 0.068SP | SP |
| SBD | ||
| sbd_balance | 0.000SBD | SBD |
| sbd_conversions | 0.000SBD | SBD |
| sbd_market_balance | 0.000SBD | SBD |
| savings_sbd_balance | 0.000SBD | SBD |
| reward_sbd_balance | 0.111SBD | SBD |
{
"balance": "0.000 STEEM",
"savings_balance": "0.000 STEEM",
"reward_steem_balance": "0.007 STEEM",
"vesting_shares": "204.033334 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "7939.626472 VESTS",
"sbd_balance": "0.000 SBD",
"savings_sbd_balance": "0.000 SBD",
"reward_sbd_balance": "0.111 SBD",
"conversions": []
}Account Info
| name | blockencryptor |
| id | 882515 |
| rank | 297,261 |
| reputation | 1798222234 |
| created | 2018-03-26T05:04:54 |
| recovery_account | steem |
| proxy | None |
| post_count | 7 |
| comment_count | 0 |
| lifetime_vote_count | 0 |
| witnesses_voted_for | 0 |
| last_post | 2018-04-06T20:06:09 |
| last_root_post | 2018-04-06T20:06:09 |
| last_vote_time | 2018-04-23T14:08:18 |
| proxied_vsf_votes | 0, 0, 0, 0 |
| can_vote | 1 |
| voting_power | 0 |
| delayed_votes | 0 |
| balance | 0.000 STEEM |
| savings_balance | 0.000 STEEM |
| sbd_balance | 0.000 SBD |
| savings_sbd_balance | 0.000 SBD |
| vesting_shares | 204.033334 VESTS |
| delegated_vesting_shares | 0.000000 VESTS |
| received_vesting_shares | 7939.626472 VESTS |
| reward_vesting_balance | 138.616726 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 | 2018-03-29T16:21:42 |
| mined | No |
| sbd_seconds | 0 |
| sbd_last_interest_payment | 1970-01-01T00:00:00 |
| savings_sbd_last_interest_payment | 1970-01-01T00:00:00 |
{
"id": 882515,
"name": "blockencryptor",
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7snatHsfsZkvuRnjUCFwkiEpCEM9iwPGwF4K5r6fbPcof7pUPV",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM76s9aeXtQeSKYerABJ4uQXDzE3R6mV8gt42CTYAPyjr6saYNKD",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM8DoKV1RzLjMCZmCEzaZFm6KSBsmGMFai9ko5V1DcCC4oucJpSu",
1
]
]
},
"memo_key": "STM5WYi3Ue8AUJDcfz4g4HQme2SdHy86w6DZTEniZk3KgnJGgcGbt",
"json_metadata": "{\"profile\":{\"profile_image\":\"https://i.imgur.com/syrwB3l.png\",\"cover_image\":\"https://i.imgur.com/MolvVbq.png\"}}",
"posting_json_metadata": "{\"profile\":{\"profile_image\":\"https://i.imgur.com/syrwB3l.png\",\"cover_image\":\"https://i.imgur.com/MolvVbq.png\"}}",
"proxy": "",
"last_owner_update": "1970-01-01T00:00:00",
"last_account_update": "2018-03-29T16:21:42",
"created": "2018-03-26T05:04:54",
"mined": false,
"recovery_account": "steem",
"last_account_recovery": "1970-01-01T00:00:00",
"reset_account": "null",
"comment_count": 0,
"lifetime_vote_count": 0,
"post_count": 7,
"can_vote": true,
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779055857
},
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779055857
},
"voting_power": 0,
"balance": "0.000 STEEM",
"savings_balance": "0.000 STEEM",
"sbd_balance": "0.000 SBD",
"sbd_seconds": "0",
"sbd_seconds_last_update": "1970-01-01T00:00:00",
"sbd_last_interest_payment": "1970-01-01T00:00:00",
"savings_sbd_balance": "0.000 SBD",
"savings_sbd_seconds": "0",
"savings_sbd_seconds_last_update": "1970-01-01T00:00:00",
"savings_sbd_last_interest_payment": "1970-01-01T00:00:00",
"savings_withdraw_requests": 0,
"reward_sbd_balance": "0.111 SBD",
"reward_steem_balance": "0.007 STEEM",
"reward_vesting_balance": "138.616726 VESTS",
"reward_vesting_steem": "0.068 STEEM",
"vesting_shares": "204.033334 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "7939.626472 VESTS",
"vesting_withdraw_rate": "0.000000 VESTS",
"next_vesting_withdrawal": "1969-12-31T23:59:59",
"withdrawn": 0,
"to_withdraw": 0,
"withdraw_routes": 0,
"curation_rewards": 0,
"posting_rewards": 135,
"proxied_vsf_votes": [
0,
0,
0,
0
],
"witnesses_voted_for": 0,
"last_post": "2018-04-06T20:06:09",
"last_root_post": "2018-04-06T20:06:09",
"last_vote_time": "2018-04-23T14:08:18",
"post_bandwidth": 0,
"pending_claimed_accounts": 0,
"vesting_balance": "0.000 STEEM",
"reputation": 1798222234,
"transfer_history": [],
"market_history": [],
"post_history": [],
"vote_history": [],
"other_history": [],
"witness_votes": [],
"tags_usage": [],
"guest_bloggers": [],
"rank": 297261
}Withdraw Routes
| Incoming | Outgoing |
|---|---|
Empty | Empty |
{
"incoming": [],
"outgoing": []
}From Date
To Date
steemdelegated 4.876 SP to @blockencryptor2026/05/17 22:10:57
steemdelegated 4.876 SP to @blockencryptor
2026/05/17 22:10:57
| delegator | steem |
| delegatee | blockencryptor |
| vesting shares | 7939.626472 VESTS |
| Transaction Info | Block #106140974/Trx d620f4e836a807f92d4bfd8839268631d1f8e398 |
View Raw JSON Data
{
"trx_id": "d620f4e836a807f92d4bfd8839268631d1f8e398",
"block": 106140974,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-05-17T22:10:57",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "blockencryptor",
"vesting_shares": "7939.626472 VESTS"
}
]
}steemdelegated 3.210 SP to @blockencryptor2026/05/11 19:45:15
steemdelegated 3.210 SP to @blockencryptor
2026/05/11 19:45:15
| delegator | steem |
| delegatee | blockencryptor |
| vesting shares | 5227.416067 VESTS |
| Transaction Info | Block #105966036/Trx 1ec69670a6a95973a5d16081f67254d256623e94 |
View Raw JSON Data
{
"trx_id": "1ec69670a6a95973a5d16081f67254d256623e94",
"block": 105966036,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-05-11T19:45:15",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "blockencryptor",
"vesting_shares": "5227.416067 VESTS"
}
]
}steemdelegated 4.883 SP to @blockencryptor2026/04/25 21:35:03
steemdelegated 4.883 SP to @blockencryptor
2026/04/25 21:35:03
| delegator | steem |
| delegatee | blockencryptor |
| vesting shares | 7952.142228 VESTS |
| Transaction Info | Block #105508685/Trx f31b878b7a995478f9b8b1943aca191de55ea3b7 |
View Raw JSON Data
{
"trx_id": "f31b878b7a995478f9b8b1943aca191de55ea3b7",
"block": 105508685,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-04-25T21:35:03",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "blockencryptor",
"vesting_shares": "7952.142228 VESTS"
}
]
}steemdelegated 3.236 SP to @blockencryptor2026/01/23 02:21:12
steemdelegated 3.236 SP to @blockencryptor
2026/01/23 02:21:12
| delegator | steem |
| delegatee | blockencryptor |
| vesting shares | 5268.962886 VESTS |
| Transaction Info | Block #102845290/Trx e7eaa295c94d9d369fc4320f203492414dc05ea1 |
View Raw JSON Data
{
"trx_id": "e7eaa295c94d9d369fc4320f203492414dc05ea1",
"block": 102845290,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-01-23T02:21:12",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "blockencryptor",
"vesting_shares": "5268.962886 VESTS"
}
]
}steemdelegated 3.336 SP to @blockencryptor2024/12/16 21:40:45
steemdelegated 3.336 SP to @blockencryptor
2024/12/16 21:40:45
| delegator | steem |
| delegatee | blockencryptor |
| vesting shares | 5433.182083 VESTS |
| Transaction Info | Block #91291701/Trx 0ef254d5263d66f869f5fe9beb2e09adcd7eb525 |
View Raw JSON Data
{
"trx_id": "0ef254d5263d66f869f5fe9beb2e09adcd7eb525",
"block": 91291701,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2024-12-16T21:40:45",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "blockencryptor",
"vesting_shares": "5433.182083 VESTS"
}
]
}steemdelegated 3.440 SP to @blockencryptor2023/11/13 13:25:57
steemdelegated 3.440 SP to @blockencryptor
2023/11/13 13:25:57
| delegator | steem |
| delegatee | blockencryptor |
| vesting shares | 5602.315615 VESTS |
| Transaction Info | Block #79845965/Trx 4cde67a9ba6476dff344fcbbd7655a3a1611ee5c |
View Raw JSON Data
{
"trx_id": "4cde67a9ba6476dff344fcbbd7655a3a1611ee5c",
"block": 79845965,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2023-11-13T13:25:57",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "blockencryptor",
"vesting_shares": "5602.315615 VESTS"
}
]
}steemdelegated 5.244 SP to @blockencryptor2023/09/21 19:25:45
steemdelegated 5.244 SP to @blockencryptor
2023/09/21 19:25:45
| delegator | steem |
| delegatee | blockencryptor |
| vesting shares | 8539.594401 VESTS |
| Transaction Info | Block #78344961/Trx d7e2e61fcbf5250cc8987442735f952b2e0ec1ed |
View Raw JSON Data
{
"trx_id": "d7e2e61fcbf5250cc8987442735f952b2e0ec1ed",
"block": 78344961,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2023-09-21T19:25:45",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "blockencryptor",
"vesting_shares": "8539.594401 VESTS"
}
]
}steemdelegated 5.380 SP to @blockencryptor2022/11/03 09:29:30
steemdelegated 5.380 SP to @blockencryptor
2022/11/03 09:29:30
| delegator | steem |
| delegatee | blockencryptor |
| vesting shares | 8761.275839 VESTS |
| Transaction Info | Block #69110619/Trx 82a5c33ae47603bc0b9f2f4954f5589c71a0a1bd |
View Raw JSON Data
{
"trx_id": "82a5c33ae47603bc0b9f2f4954f5589c71a0a1bd",
"block": 69110619,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2022-11-03T09:29:30",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "blockencryptor",
"vesting_shares": "8761.275839 VESTS"
}
]
}steemdelegated 5.516 SP to @blockencryptor2022/01/17 08:56:03
steemdelegated 5.516 SP to @blockencryptor
2022/01/17 08:56:03
| delegator | steem |
| delegatee | blockencryptor |
| vesting shares | 8981.809070 VESTS |
| Transaction Info | Block #60807005/Trx 5bfd76e1e6ad318189291830f6476ed37fcf2127 |
View Raw JSON Data
{
"trx_id": "5bfd76e1e6ad318189291830f6476ed37fcf2127",
"block": 60807005,
"trx_in_block": 25,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2022-01-17T08:56:03",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "blockencryptor",
"vesting_shares": "8981.809070 VESTS"
}
]
}steemdelegated 5.628 SP to @blockencryptor2021/06/13 22:56:12
steemdelegated 5.628 SP to @blockencryptor
2021/06/13 22:56:12
| delegator | steem |
| delegatee | blockencryptor |
| vesting shares | 9165.577728 VESTS |
| Transaction Info | Block #54605489/Trx b3828fd3c2dc0a4a6df979e23856759c9e752a74 |
View Raw JSON Data
{
"trx_id": "b3828fd3c2dc0a4a6df979e23856759c9e752a74",
"block": 54605489,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2021-06-13T22:56:12",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "blockencryptor",
"vesting_shares": "9165.577728 VESTS"
}
]
}steemdelegated 5.744 SP to @blockencryptor2020/12/11 09:17:45
steemdelegated 5.744 SP to @blockencryptor
2020/12/11 09:17:45
| delegator | steem |
| delegatee | blockencryptor |
| vesting shares | 9352.999702 VESTS |
| Transaction Info | Block #49353021/Trx 531c205d99a8905950fe461f6c0a8d3726fd4450 |
View Raw JSON Data
{
"trx_id": "531c205d99a8905950fe461f6c0a8d3726fd4450",
"block": 49353021,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-12-11T09:17:45",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "blockencryptor",
"vesting_shares": "9352.999702 VESTS"
}
]
}steemdelegated 1.174 SP to @blockencryptor2020/12/06 02:55:12
steemdelegated 1.174 SP to @blockencryptor
2020/12/06 02:55:12
| delegator | steem |
| delegatee | blockencryptor |
| vesting shares | 1912.543513 VESTS |
| Transaction Info | Block #49204594/Trx a8a4d8225be195c6bfe2c2282cce8564ec025247 |
View Raw JSON Data
{
"trx_id": "a8a4d8225be195c6bfe2c2282cce8564ec025247",
"block": 49204594,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-12-06T02:55:12",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "blockencryptor",
"vesting_shares": "1912.543513 VESTS"
}
]
}steemdelegated 5.747 SP to @blockencryptor2020/12/05 10:52:09
steemdelegated 5.747 SP to @blockencryptor
2020/12/05 10:52:09
| delegator | steem |
| delegatee | blockencryptor |
| vesting shares | 9359.366341 VESTS |
| Transaction Info | Block #49185698/Trx ddf12c941e24799de9f3510ea840d72cd60c286d |
View Raw JSON Data
{
"trx_id": "ddf12c941e24799de9f3510ea840d72cd60c286d",
"block": 49185698,
"trx_in_block": 19,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-12-05T10:52:09",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "blockencryptor",
"vesting_shares": "9359.366341 VESTS"
}
]
}steemdelegated 1.179 SP to @blockencryptor2020/11/02 11:40:36
steemdelegated 1.179 SP to @blockencryptor
2020/11/02 11:40:36
| delegator | steem |
| delegatee | blockencryptor |
| vesting shares | 1920.017158 VESTS |
| Transaction Info | Block #48253140/Trx a4d27588be74aee4fc709e81bb56bf9d51558112 |
View Raw JSON Data
{
"trx_id": "a4d27588be74aee4fc709e81bb56bf9d51558112",
"block": 48253140,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-11-02T11:40:36",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "blockencryptor",
"vesting_shares": "1920.017158 VESTS"
}
]
}steemdelegated 5.872 SP to @blockencryptor2020/05/09 03:50:24
steemdelegated 5.872 SP to @blockencryptor
2020/05/09 03:50:24
| delegator | steem |
| delegatee | blockencryptor |
| vesting shares | 9562.012915 VESTS |
| Transaction Info | Block #43214810/Trx 8d5927e43b03a50083c1662edf9ebfb92e6b477f |
View Raw JSON Data
{
"trx_id": "8d5927e43b03a50083c1662edf9ebfb92e6b477f",
"block": 43214810,
"trx_in_block": 11,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-05-09T03:50:24",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "blockencryptor",
"vesting_shares": "9562.012915 VESTS"
}
]
}steemdelegated 1.200 SP to @blockencryptor2020/05/08 07:09:39
steemdelegated 1.200 SP to @blockencryptor
2020/05/08 07:09:39
| delegator | steem |
| delegatee | blockencryptor |
| vesting shares | 1953.311140 VESTS |
| Transaction Info | Block #43190577/Trx 53e59963bbe3e6f380c21e142b7a93225d51e34f |
View Raw JSON Data
{
"trx_id": "53e59963bbe3e6f380c21e142b7a93225d51e34f",
"block": 43190577,
"trx_in_block": 10,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-05-08T07:09:39",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "blockencryptor",
"vesting_shares": "1953.311140 VESTS"
}
]
}steemdelegated 5.978 SP to @blockencryptor2019/07/12 05:09:36
steemdelegated 5.978 SP to @blockencryptor
2019/07/12 05:09:36
| delegator | steem |
| delegatee | blockencryptor |
| vesting shares | 9735.375457 VESTS |
| Transaction Info | Block #34588504/Trx a6a4153661bb255b867c1dac16ae9022c46fbdb5 |
View Raw JSON Data
{
"trx_id": "a6a4153661bb255b867c1dac16ae9022c46fbdb5",
"block": 34588504,
"trx_in_block": 29,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-07-12T05:09:36",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "blockencryptor",
"vesting_shares": "9735.375457 VESTS"
}
]
}2019/03/26 06:41:03
2019/03/26 06:41:03
| parent author | blockencryptor |
| parent permlink | deeponion-consequences-of-a-mining-algorithm-change |
| author | steemitboard |
| permlink | steemitboard-notify-blockencryptor-20190326t064103000z |
| title | |
| body | Congratulations @blockencryptor! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@blockencryptor/birthday1.png</td><td>Happy Birthday! - You are on the Steem blockchain for 1 year!</td></tr></table> <sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@blockencryptor) and compare to others on the [Steem Ranking](http://steemitboard.com/ranking/index.php?name=blockencryptor)_</sub> **Do not miss the last post from @steemitboard:** <table><tr><td><a href="https://steemit.com/steem/@steemitboard/3-years-on-steem-happy-birthday-the-distribution-of-commemorative-badges-has-begun"><img src="https://steemitimages.com/64x128/http://u.cubeupload.com/arcange/BG6u6k.png"></a></td><td><a href="https://steemit.com/steem/@steemitboard/3-years-on-steem-happy-birthday-the-distribution-of-commemorative-badges-has-begun">3 years on Steem - The distribution of commemorative badges has begun!</a></td></tr><tr><td><a href="https://steemit.com/steem/@steemitboard/happy-birthday-the-steem-blockchain-is-running-for-3-years"><img src="https://steemitimages.com/64x128/http://u.cubeupload.com/arcange/BG6u6k.png"></a></td><td><a href="https://steemit.com/steem/@steemitboard/happy-birthday-the-steem-blockchain-is-running-for-3-years">Happy Birthday! The Steem blockchain is running for 3 years.</a></td></tr></table> ###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| Transaction Info | Block #31484388/Trx 966f11368f412119cb6de95dc3f66bb16b6acb43 |
View Raw JSON Data
{
"trx_id": "966f11368f412119cb6de95dc3f66bb16b6acb43",
"block": 31484388,
"trx_in_block": 12,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-03-26T06:41:03",
"op": [
"comment",
{
"parent_author": "blockencryptor",
"parent_permlink": "deeponion-consequences-of-a-mining-algorithm-change",
"author": "steemitboard",
"permlink": "steemitboard-notify-blockencryptor-20190326t064103000z",
"title": "",
"body": "Congratulations @blockencryptor! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@blockencryptor/birthday1.png</td><td>Happy Birthday! - You are on the Steem blockchain for 1 year!</td></tr></table>\n\n<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@blockencryptor) and compare to others on the [Steem Ranking](http://steemitboard.com/ranking/index.php?name=blockencryptor)_</sub>\n\n\n**Do not miss the last post from @steemitboard:**\n<table><tr><td><a href=\"https://steemit.com/steem/@steemitboard/3-years-on-steem-happy-birthday-the-distribution-of-commemorative-badges-has-begun\"><img src=\"https://steemitimages.com/64x128/http://u.cubeupload.com/arcange/BG6u6k.png\"></a></td><td><a href=\"https://steemit.com/steem/@steemitboard/3-years-on-steem-happy-birthday-the-distribution-of-commemorative-badges-has-begun\">3 years on Steem - The distribution of commemorative badges has begun!</a></td></tr><tr><td><a href=\"https://steemit.com/steem/@steemitboard/happy-birthday-the-steem-blockchain-is-running-for-3-years\"><img src=\"https://steemitimages.com/64x128/http://u.cubeupload.com/arcange/BG6u6k.png\"></a></td><td><a href=\"https://steemit.com/steem/@steemitboard/happy-birthday-the-steem-blockchain-is-running-for-3-years\">Happy Birthday! The Steem blockchain is running for 3 years.</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\"]}"
}
]
}steemdelegated 6.100 SP to @blockencryptor2018/07/23 14:09:12
steemdelegated 6.100 SP to @blockencryptor
2018/07/23 14:09:12
| delegator | steem |
| delegatee | blockencryptor |
| vesting shares | 9934.166913 VESTS |
| Transaction Info | Block #24429429/Trx bed89abba0caaef9254a3c7a72c077bf73171d42 |
View Raw JSON Data
{
"trx_id": "bed89abba0caaef9254a3c7a72c077bf73171d42",
"block": 24429429,
"trx_in_block": 25,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-07-23T14:09:12",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "blockencryptor",
"vesting_shares": "9934.166913 VESTS"
}
]
}2018/04/23 16:52:45
2018/04/23 16:52:45
| parent author | blockencryptor |
| parent permlink | deeponion-consequences-of-a-mining-algorithm-change |
| author | steemitboard |
| permlink | steemitboard-notify-blockencryptor-20180423t165245000z |
| title | |
| body | Congratulations @blockencryptor! You have completed some achievement on Steemit and have been rewarded with new badge(s) : [](http://steemitboard.com/@blockencryptor) You made your First Vote Click on any badge to view your own Board of Honor on SteemitBoard. For more information about SteemitBoard, click [here](https://steemit.com/@steemitboard) If you no longer want to receive notifications, reply to this comment with the word `STOP` > Upvote this notification to help all Steemit users. Learn why [here](https://steemit.com/steemitboard/@steemitboard/http-i-cubeupload-com-7ciqeo-png)! |
| json metadata | {"image":["https://steemitboard.com/img/notifications.png"]} |
| Transaction Info | Block #21824112/Trx 2db104636ffc862d83ef3a79c5d73bf77e272058 |
View Raw JSON Data
{
"trx_id": "2db104636ffc862d83ef3a79c5d73bf77e272058",
"block": 21824112,
"trx_in_block": 9,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-23T16:52:45",
"op": [
"comment",
{
"parent_author": "blockencryptor",
"parent_permlink": "deeponion-consequences-of-a-mining-algorithm-change",
"author": "steemitboard",
"permlink": "steemitboard-notify-blockencryptor-20180423t165245000z",
"title": "",
"body": "Congratulations @blockencryptor! You have completed some achievement on Steemit and have been rewarded with new badge(s) :\n\n[](http://steemitboard.com/@blockencryptor) You made your First Vote\n\nClick on any badge to view your own Board of Honor on SteemitBoard.\nFor more information about SteemitBoard, click [here](https://steemit.com/@steemitboard)\n\nIf you no longer want to receive notifications, reply to this comment with the word `STOP`\n\n> Upvote this notification to help all Steemit users. Learn why [here](https://steemit.com/steemitboard/@steemitboard/http-i-cubeupload-com-7ciqeo-png)!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notifications.png\"]}"
}
]
}2018/04/23 14:08:18
2018/04/23 14:08:18
| voter | blockencryptor |
| author | cryptosteve |
| permlink | re-andhovesyan-deeponion-the-real-game-is-starting-20180421t133926014z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21820848/Trx 59b165601f3c0e320db6221d5ef22a5601b566a9 |
View Raw JSON Data
{
"trx_id": "59b165601f3c0e320db6221d5ef22a5601b566a9",
"block": 21820848,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-23T14:08:18",
"op": [
"vote",
{
"voter": "blockencryptor",
"author": "cryptosteve",
"permlink": "re-andhovesyan-deeponion-the-real-game-is-starting-20180421t133926014z",
"weight": 10000
}
]
}2018/04/23 14:08:15
2018/04/23 14:08:15
| voter | blockencryptor |
| author | noelnada |
| permlink | re-andhovesyan-deeponion-the-real-game-is-starting-20180422t140504140z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21820847/Trx 74cfc8cf3192be15044ceb35e9afb69dd2f4a7da |
View Raw JSON Data
{
"trx_id": "74cfc8cf3192be15044ceb35e9afb69dd2f4a7da",
"block": 21820847,
"trx_in_block": 32,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-23T14:08:15",
"op": [
"vote",
{
"voter": "blockencryptor",
"author": "noelnada",
"permlink": "re-andhovesyan-deeponion-the-real-game-is-starting-20180422t140504140z",
"weight": 10000
}
]
}blockencryptorcustom json: follow2018/04/23 14:06:39
blockencryptorcustom json: follow
2018/04/23 14:06:39
| required auths | [] |
| required posting auths | ["blockencryptor"] |
| id | follow |
| json | ["reblog",{"account":"blockencryptor","author":"andhovesyan","permlink":"deeponion-the-real-game-is-starting"}] |
| Transaction Info | Block #21820815/Trx 4fa5f66339d1caaefb7949ff163f1b91f5deabfc |
View Raw JSON Data
{
"trx_id": "4fa5f66339d1caaefb7949ff163f1b91f5deabfc",
"block": 21820815,
"trx_in_block": 66,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-23T14:06:39",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"blockencryptor"
],
"id": "follow",
"json": "[\"reblog\",{\"account\":\"blockencryptor\",\"author\":\"andhovesyan\",\"permlink\":\"deeponion-the-real-game-is-starting\"}]"
}
]
}blockencryptorupvoted (100.00%) @andhovesyan / deeponion-the-real-game-is-starting2018/04/23 14:06:30
blockencryptorupvoted (100.00%) @andhovesyan / deeponion-the-real-game-is-starting
2018/04/23 14:06:30
| voter | blockencryptor |
| author | andhovesyan |
| permlink | deeponion-the-real-game-is-starting |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21820812/Trx b07dab7c614ca47f394cf2c5d73898b11c5adb7b |
View Raw JSON Data
{
"trx_id": "b07dab7c614ca47f394cf2c5d73898b11c5adb7b",
"block": 21820812,
"trx_in_block": 54,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-23T14:06:30",
"op": [
"vote",
{
"voter": "blockencryptor",
"author": "andhovesyan",
"permlink": "deeponion-the-real-game-is-starting",
"weight": 10000
}
]
}blockencryptorreceived 0.003 STEEM, 0.057 SBD, 0.043 SP author reward for @blockencryptor / deeponion-consequences-of-a-mining-algorithm-change2018/04/13 20:06:09
blockencryptorreceived 0.003 STEEM, 0.057 SBD, 0.043 SP author reward for @blockencryptor / deeponion-consequences-of-a-mining-algorithm-change
2018/04/13 20:06:09
| author | blockencryptor |
| permlink | deeponion-consequences-of-a-mining-algorithm-change |
| sbd payout | 0.057 SBD |
| steem payout | 0.003 STEEM |
| vesting payout | 69.303687 VESTS |
| Transaction Info | Block #21540044/Virtual Operation #6 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 21540044,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 6,
"timestamp": "2018-04-13T20:06:09",
"op": [
"author_reward",
{
"author": "blockencryptor",
"permlink": "deeponion-consequences-of-a-mining-algorithm-change",
"sbd_payout": "0.057 SBD",
"steem_payout": "0.003 STEEM",
"vesting_payout": "69.303687 VESTS"
}
]
}paukerinupvoted (100.00%) @blockencryptor / i-created-a-cold-storage-wallet2018/04/12 13:57:27
paukerinupvoted (100.00%) @blockencryptor / i-created-a-cold-storage-wallet
2018/04/12 13:57:27
| voter | paukerin |
| author | blockencryptor |
| permlink | i-created-a-cold-storage-wallet |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21503884/Trx 173647bf5699d43a364ad453f6ff6830f868b6a8 |
View Raw JSON Data
{
"trx_id": "173647bf5699d43a364ad453f6ff6830f868b6a8",
"block": 21503884,
"trx_in_block": 12,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-12T13:57:27",
"op": [
"vote",
{
"voter": "paukerin",
"author": "blockencryptor",
"permlink": "i-created-a-cold-storage-wallet",
"weight": 10000
}
]
}aitorp6upvoted (100.00%) @blockencryptor / i-created-a-cold-storage-wallet2018/04/12 09:56:09
aitorp6upvoted (100.00%) @blockencryptor / i-created-a-cold-storage-wallet
2018/04/12 09:56:09
| voter | aitorp6 |
| author | blockencryptor |
| permlink | i-created-a-cold-storage-wallet |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21499059/Trx 4dff5e5b443fb917aa7e498afe04f4c41182bcb0 |
View Raw JSON Data
{
"trx_id": "4dff5e5b443fb917aa7e498afe04f4c41182bcb0",
"block": 21499059,
"trx_in_block": 33,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-12T09:56:09",
"op": [
"vote",
{
"voter": "aitorp6",
"author": "blockencryptor",
"permlink": "i-created-a-cold-storage-wallet",
"weight": 10000
}
]
}blockencryptorreceived 0.004 STEEM, 0.054 SBD, 0.043 SP author reward for @blockencryptor / i-created-a-cold-storage-wallet2018/04/11 06:24:36
blockencryptorreceived 0.004 STEEM, 0.054 SBD, 0.043 SP author reward for @blockencryptor / i-created-a-cold-storage-wallet
2018/04/11 06:24:36
| author | blockencryptor |
| permlink | i-created-a-cold-storage-wallet |
| sbd payout | 0.054 SBD |
| steem payout | 0.004 STEEM |
| vesting payout | 69.313039 VESTS |
| Transaction Info | Block #21466033/Virtual Operation #20 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 21466033,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 20,
"timestamp": "2018-04-11T06:24:36",
"op": [
"author_reward",
{
"author": "blockencryptor",
"permlink": "i-created-a-cold-storage-wallet",
"sbd_payout": "0.054 SBD",
"steem_payout": "0.004 STEEM",
"vesting_payout": "69.313039 VESTS"
}
]
}ubgupvoted (1.00%) @blockencryptor / deeponion-consequences-of-a-mining-algorithm-change2018/04/06 20:38:51
ubgupvoted (1.00%) @blockencryptor / deeponion-consequences-of-a-mining-algorithm-change
2018/04/06 20:38:51
| voter | ubg |
| author | blockencryptor |
| permlink | deeponion-consequences-of-a-mining-algorithm-change |
| weight | 100 (1.00%) |
| Transaction Info | Block #21339127/Trx 22a2e79537bd2a69895bb4a0be66bde6f15ef362 |
View Raw JSON Data
{
"trx_id": "22a2e79537bd2a69895bb4a0be66bde6f15ef362",
"block": 21339127,
"trx_in_block": 34,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-06T20:38:51",
"op": [
"vote",
{
"voter": "ubg",
"author": "blockencryptor",
"permlink": "deeponion-consequences-of-a-mining-algorithm-change",
"weight": 100
}
]
}hr1upvoted (0.02%) @blockencryptor / deeponion-consequences-of-a-mining-algorithm-change2018/04/06 20:36:06
hr1upvoted (0.02%) @blockencryptor / deeponion-consequences-of-a-mining-algorithm-change
2018/04/06 20:36:06
| voter | hr1 |
| author | blockencryptor |
| permlink | deeponion-consequences-of-a-mining-algorithm-change |
| weight | 2 (0.02%) |
| Transaction Info | Block #21339072/Trx 5032b548abbe662d8a3f94be52e611528ab27e8b |
View Raw JSON Data
{
"trx_id": "5032b548abbe662d8a3f94be52e611528ab27e8b",
"block": 21339072,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-06T20:36:06",
"op": [
"vote",
{
"voter": "hr1",
"author": "blockencryptor",
"permlink": "deeponion-consequences-of-a-mining-algorithm-change",
"weight": 2
}
]
}blockencryptorpublished a new post: deeponion-consequences-of-a-mining-algorithm-change2018/04/06 20:06:27
blockencryptorpublished a new post: deeponion-consequences-of-a-mining-algorithm-change
2018/04/06 20:06:27
| parent author | |
| parent permlink | deeponion |
| author | blockencryptor |
| permlink | deeponion-consequences-of-a-mining-algorithm-change |
| title | DeepOnion: Consequences of a mining algorithm change |
| body | @@ -5064,12 +5064,104 @@ le: -TODO +https://deeponion.org/community/threads/article-consequences-of-a-mining-algorithm-change.34688/ %0A%0A-- |
| json metadata | {"tags":["deeponion","mining","pow","algorithm","x13"],"image":["https://steemitimages.com/DQmTZKu3Gpsakji6R8pYULLEYPNCnz8sJhQf3nZeBc9zY5K/image.png","https://steemitimages.com/DQmSYhp3y7KnTRRFWkfBGueaSC3tpD6Vnq1eQNSSidkH6D2/image.png"],"links":["https://www.reddit.com/r/CryptoCurrency/comments/23iail/is_it_possible_for_a_altcoin_to_change_its/","https://pixabay.com/photo-1808082/","https://medium.com/@mycoralhealth/code-your-own-blockchain-mining-algorithm-in-go-82c6a71aba1f","https://bitcoingold.org/","https://news.bitcoin.com/bitcoin-developers-changing-proof-work-algorithm/","https://themerkle.com/scrypt-vs-x11-vs-sha-256/","https://deeponion.org/community/threads/a-fork-to-make-deeponion-free-again.34534/","https://deeponion.org/community/threads/article-consequences-of-a-mining-algorithm-change.34688/","https://twitter.com/BlockEncryptor"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #21338479/Trx 066df29ff88652375b1638d1c74dff7d501f1505 |
View Raw JSON Data
{
"trx_id": "066df29ff88652375b1638d1c74dff7d501f1505",
"block": 21338479,
"trx_in_block": 31,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-06T20:06:27",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "deeponion",
"author": "blockencryptor",
"permlink": "deeponion-consequences-of-a-mining-algorithm-change",
"title": "DeepOnion: Consequences of a mining algorithm change",
"body": "@@ -5064,12 +5064,104 @@\n le: \n-TODO\n+https://deeponion.org/community/threads/article-consequences-of-a-mining-algorithm-change.34688/\n %0A%0A--\n",
"json_metadata": "{\"tags\":[\"deeponion\",\"mining\",\"pow\",\"algorithm\",\"x13\"],\"image\":[\"https://steemitimages.com/DQmTZKu3Gpsakji6R8pYULLEYPNCnz8sJhQf3nZeBc9zY5K/image.png\",\"https://steemitimages.com/DQmSYhp3y7KnTRRFWkfBGueaSC3tpD6Vnq1eQNSSidkH6D2/image.png\"],\"links\":[\"https://www.reddit.com/r/CryptoCurrency/comments/23iail/is_it_possible_for_a_altcoin_to_change_its/\",\"https://pixabay.com/photo-1808082/\",\"https://medium.com/@mycoralhealth/code-your-own-blockchain-mining-algorithm-in-go-82c6a71aba1f\",\"https://bitcoingold.org/\",\"https://news.bitcoin.com/bitcoin-developers-changing-proof-work-algorithm/\",\"https://themerkle.com/scrypt-vs-x11-vs-sha-256/\",\"https://deeponion.org/community/threads/a-fork-to-make-deeponion-free-again.34534/\",\"https://deeponion.org/community/threads/article-consequences-of-a-mining-algorithm-change.34688/\",\"https://twitter.com/BlockEncryptor\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}blockencryptorpublished a new post: deeponion-consequences-of-a-mining-algorithm-change2018/04/06 20:06:09
blockencryptorpublished a new post: deeponion-consequences-of-a-mining-algorithm-change
2018/04/06 20:06:09
| parent author | |
| parent permlink | deeponion |
| author | blockencryptor |
| permlink | deeponion-consequences-of-a-mining-algorithm-change |
| title | DeepOnion: Consequences of a mining algorithm change |
| body | A few days ago I stumbled upon a thread about changing the mining algorithm of DeepOnion. According to the whitepaper it currently uses the X13 algorithm, which was designed to be ASIC resistant but this lasted not long. So, with this algorithm the only profitable way to mine $onions is with a dedicated mining hardware, a so called ASIC (Application-Specific Integrated Circuit). Inspired from this thread on the DeepOnion forum I was curious about the consequences of an algorithm change. After a short google search I found on reddit a few comments that it should be possible and maybe even without a fork. This should depend on the current implementation. [[1](https://www.reddit.com/r/CryptoCurrency/comments/23iail/is_it_possible_for_a_altcoin_to_change_its/)] I thought if there is a way to change the algorithm, this will be a topic on vote central. <center>  Photo by markusspiske on pixabay ([Link](https://pixabay.com/photo-1808082/)) </center> ### Basic knowledge Every blockchain that implements Proof of Work needs an algorithm for their miners. The most popular one is SHA-256 which is used by bitcoin. The purpose of such algorithms is to control the release of new blocks and verify the solution sent by the miners. Therefore it makes use of hash functions which are also called one-way functions, because it's easy to verify the output but extremely hard to guess the input. You can't reverse the function, you can only bruteforce the input. [[2](https://medium.com/@mycoralhealth/code-your-own-blockchain-mining-algorithm-in-go-82c6a71aba1f)] `Random Input -> 3e36dcdd7da2e73f5a51463985909395e904305af1f7fed6b066e64b1838dece` A small change on the input produces a completely different output. `random Input -> 10bb614a3e738f5bb96fe74ebd3df94e74af2e0f00adfda6b363aa988b3d2dec` The first one who finds the correct input generates a new block and receives the reward. The more people are mining the harder the input will be. This is required to throttle the block generation and meet the required block time. With that basic knowledge we can now come to the actual question. ## What are the consequences of changing the mining algorithm for DeepOnion? From a technical point of view there should be no real consequences when changing the algorithm. One drop of bitterness would be the required hard fork. Even on bitcoin an algorithm change was possible. The creators of bitcoin gold made a hard fork of bitcoin and changed the algorithm to Equihash in order to decentralize the mining again. [[3](https://bitcoingold.org/)] There was also a controversial discussion about changing Bitcoin's PoW consensus mechanism. It's more than just a technical decision. Miners want to secure their investments, Enthusiasts don't want changes on one of the core components and Holders want to prevent a hard fork. [[4](https://news.bitcoin.com/bitcoin-developers-changing-proof-work-algorithm/)] Depending on the new algorithm there are also many advantages. More decentralization or the prevention of asic miners, just to name a few examples. ## Which algorithm is the best for DeepOnion? Depending on whom you ask you will get different answers. * Holders of baikal miners will prefer to keep the current X13 algorithm. They have dedicated and exclusive hardware to mine DeepOnion. With this algorithm you can't mine profitable with any GPU * Bitcoin miner would probably want to switch to SHA-256 to use their purchased hardware * The CPU mining community would vote for cryptonight * AMD holders for equihash Personally I would prefer a energy-efficient, more decentralized and asic resistant algorithm. But this is not as easy as it sounds. X11, the predecessor of X13, was initially designed as ASCI-resistant algorithm. Shortly after the first manufacturers developed dedicated devices. [[4](https://themerkle.com/scrypt-vs-x11-vs-sha-256/)] There are a few other properties which can be used to characterize mining algorithms. How energy -efficient is it, how much memory is required, is it dual mine compatible, just to name a few examples. ## Conclusion In conclusion I would not change the mining algorithm of DeepOnion. In my opinion it is not a relevant factor for the success of DeepOnion and therefore the team should focus on more important tasks. It might even be possible to eliminate Proof of Work and change it to a Proof of Stake only. Has someone a different view on this topic? I would appreciate to exchange vies on this topic as there are not much well presented information on the internet. --- #### Sources [1] https://www.reddit.com/r/CryptoCurrency/comments/23iail/is_it_possible_for_a_altcoin_to_change_its/ [2] https://medium.com/@mycoralhealth/code-your-own-blockchain-mining-algorithm-in-go-82c6a71aba1f [3] https://bitcoingold.org/ [4] https://themerkle.com/scrypt-vs-x11-vs-sha-256/ --- #### Links Muse article: https://deeponion.org/community/threads/a-fork-to-make-deeponion-free-again.34534/ DeepOnion article: TODO --- Follow me on twitter for the newest updates and giveaways. https://twitter.com/BlockEncryptor <center>  </center> |
| json metadata | {"tags":["deeponion","mining","pow","algorithm","x13"],"image":["https://steemitimages.com/DQmTZKu3Gpsakji6R8pYULLEYPNCnz8sJhQf3nZeBc9zY5K/image.png","https://steemitimages.com/DQmSYhp3y7KnTRRFWkfBGueaSC3tpD6Vnq1eQNSSidkH6D2/image.png"],"links":["https://www.reddit.com/r/CryptoCurrency/comments/23iail/is_it_possible_for_a_altcoin_to_change_its/","https://pixabay.com/photo-1808082/","https://medium.com/@mycoralhealth/code-your-own-blockchain-mining-algorithm-in-go-82c6a71aba1f","https://bitcoingold.org/","https://news.bitcoin.com/bitcoin-developers-changing-proof-work-algorithm/","https://themerkle.com/scrypt-vs-x11-vs-sha-256/","https://deeponion.org/community/threads/a-fork-to-make-deeponion-free-again.34534/","https://twitter.com/BlockEncryptor"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #21338473/Trx 128cdfb02eada46ae0f9d8acc1241cffd17ad5e8 |
View Raw JSON Data
{
"trx_id": "128cdfb02eada46ae0f9d8acc1241cffd17ad5e8",
"block": 21338473,
"trx_in_block": 18,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-06T20:06:09",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "deeponion",
"author": "blockencryptor",
"permlink": "deeponion-consequences-of-a-mining-algorithm-change",
"title": "DeepOnion: Consequences of a mining algorithm change",
"body": "A few days ago I stumbled upon a thread about changing the mining algorithm of DeepOnion. According to the whitepaper it currently uses the X13 algorithm, which was designed to be ASIC resistant but this lasted not long. So, with this algorithm the only profitable way to mine $onions is with a dedicated mining hardware, a so called ASIC (Application-Specific Integrated Circuit). \n\nInspired from this thread on the DeepOnion forum I was curious about the consequences of an algorithm change. After a short google search I found on reddit a few comments that it should be possible and maybe even without a fork. This should depend on the current implementation. [[1](https://www.reddit.com/r/CryptoCurrency/comments/23iail/is_it_possible_for_a_altcoin_to_change_its/)] I thought if there is a way to change the algorithm, this will be a topic on vote central.\n\n<center>\n\nPhoto by markusspiske on pixabay ([Link](https://pixabay.com/photo-1808082/))\n</center>\n\n### Basic knowledge\nEvery blockchain that implements Proof of Work needs an algorithm for their miners. The most popular one is SHA-256 which is used by bitcoin. The purpose of such algorithms is to control the release of new blocks and verify the solution sent by the miners. Therefore it makes use of hash functions which are also called one-way functions, because it's easy to verify the output but extremely hard to guess the input. You can't reverse the function, you can only bruteforce the input. [[2](https://medium.com/@mycoralhealth/code-your-own-blockchain-mining-algorithm-in-go-82c6a71aba1f)]\n`Random Input -> 3e36dcdd7da2e73f5a51463985909395e904305af1f7fed6b066e64b1838dece`\n\nA small change on the input produces a completely different output.\n`random Input -> 10bb614a3e738f5bb96fe74ebd3df94e74af2e0f00adfda6b363aa988b3d2dec`\n\nThe first one who finds the correct input generates a new block and receives the reward. The more people are mining the harder the input will be. This is required to throttle the block generation and meet the required block time.\n\nWith that basic knowledge we can now come to the actual question.\n\n## What are the consequences of changing the mining algorithm for DeepOnion?\nFrom a technical point of view there should be no real consequences when changing the algorithm. One drop of bitterness would be the required hard fork.\n\nEven on bitcoin an algorithm change was possible. The creators of bitcoin gold made a hard fork of bitcoin and changed the algorithm to Equihash in order to decentralize the mining again. [[3](https://bitcoingold.org/)]\n\nThere was also a controversial discussion about changing Bitcoin's PoW consensus mechanism. It's more than just a technical decision. Miners want to secure their investments, Enthusiasts don't want changes on one of the core components and Holders want to prevent a hard fork. [[4](https://news.bitcoin.com/bitcoin-developers-changing-proof-work-algorithm/)] \n\nDepending on the new algorithm there are also many advantages. More decentralization or the prevention of asic miners, just to name a few examples.\n\n## Which algorithm is the best for DeepOnion?\nDepending on whom you ask you will get different answers. \n* Holders of baikal miners will prefer to keep the current X13 algorithm. They have dedicated and exclusive hardware to mine DeepOnion. With this algorithm you can't mine profitable with any GPU\n* Bitcoin miner would probably want to switch to SHA-256 to use their purchased hardware\n* The CPU mining community would vote for cryptonight\n* AMD holders for equihash\n\nPersonally I would prefer a energy-efficient, more decentralized and asic resistant algorithm. But this is not as easy as it sounds. X11, the predecessor of X13, was initially designed as ASCI-resistant algorithm. Shortly after the first manufacturers developed dedicated devices. [[4](https://themerkle.com/scrypt-vs-x11-vs-sha-256/)]\n\nThere are a few other properties which can be used to characterize mining algorithms. How energy -efficient is it, how much memory is required, is it dual mine compatible, just to name a few examples.\n\n## Conclusion\nIn conclusion I would not change the mining algorithm of DeepOnion. In my opinion it is not a relevant factor for the success of DeepOnion and therefore the team should focus on more important tasks. It might even be possible to eliminate Proof of Work and change it to a Proof of Stake only. \n\nHas someone a different view on this topic? I would appreciate to exchange vies on this topic as there are not much well presented information on the internet.\n\n\n\n---\n#### Sources\n[1] https://www.reddit.com/r/CryptoCurrency/comments/23iail/is_it_possible_for_a_altcoin_to_change_its/\n[2] https://medium.com/@mycoralhealth/code-your-own-blockchain-mining-algorithm-in-go-82c6a71aba1f\n[3] https://bitcoingold.org/\n[4] https://themerkle.com/scrypt-vs-x11-vs-sha-256/\n\n---\n#### Links\nMuse article: https://deeponion.org/community/threads/a-fork-to-make-deeponion-free-again.34534/\nDeepOnion article: TODO\n\n---\n\nFollow me on twitter for the newest updates and giveaways.\nhttps://twitter.com/BlockEncryptor\n\n<center>\n\n</center>",
"json_metadata": "{\"tags\":[\"deeponion\",\"mining\",\"pow\",\"algorithm\",\"x13\"],\"image\":[\"https://steemitimages.com/DQmTZKu3Gpsakji6R8pYULLEYPNCnz8sJhQf3nZeBc9zY5K/image.png\",\"https://steemitimages.com/DQmSYhp3y7KnTRRFWkfBGueaSC3tpD6Vnq1eQNSSidkH6D2/image.png\"],\"links\":[\"https://www.reddit.com/r/CryptoCurrency/comments/23iail/is_it_possible_for_a_altcoin_to_change_its/\",\"https://pixabay.com/photo-1808082/\",\"https://medium.com/@mycoralhealth/code-your-own-blockchain-mining-algorithm-in-go-82c6a71aba1f\",\"https://bitcoingold.org/\",\"https://news.bitcoin.com/bitcoin-developers-changing-proof-work-algorithm/\",\"https://themerkle.com/scrypt-vs-x11-vs-sha-256/\",\"https://deeponion.org/community/threads/a-fork-to-make-deeponion-free-again.34534/\",\"https://twitter.com/BlockEncryptor\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}blockencryptorpublished a new post: deeponion-pos-proof-of-stake-only2018/04/05 08:02:48
blockencryptorpublished a new post: deeponion-pos-proof-of-stake-only
2018/04/05 08:02:48
| parent author | |
| parent permlink | deeponion |
| author | blockencryptor |
| permlink | deeponion-pos-proof-of-stake-only |
| title | DeepOnion: PoS (Proof of Stake) only? |
| body | @@ -3646,16 +3646,175 @@ y%0A%0A---%0A%0A +I published this article also on the DeepOnion community forum.%0Ahttps://deeponion.org/community/threads/article-deeponion-pos-proof-of-stake-only.34540/%0A%0A---%0A%0A Follow m |
| json metadata | {"tags":["deeponion","pow","pos","comparison","mining"],"users":["cryptomaster"],"image":["https://steemitimages.com/DQmShmoSSTtjSTNzSeroSG4eKRJ4yezUYQkcbKYyygmAgkV/image.png","https://steemitimages.com/DQmSYhp3y7KnTRRFWkfBGueaSC3tpD6Vnq1eQNSSidkH6D2/image.png"],"links":["https://digiconomist.net/bitcoin-energy-consumption","https://deeponion.org/White-Paper.pdf","https://deeponion.org/community/threads/article-deeponions-upcoming-vote-central-where-community-matters.26150/","https://deeponion.org/community","https://deeponion.org/community/threads/article-deeponion-pos-proof-of-stake-only.34540/","https://twitter.com/BlockEncryptor"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #21295209/Trx 56f3c57e4bfab1f8a73d19abc5c063809ede43bb |
View Raw JSON Data
{
"trx_id": "56f3c57e4bfab1f8a73d19abc5c063809ede43bb",
"block": 21295209,
"trx_in_block": 27,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-05T08:02:48",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "deeponion",
"author": "blockencryptor",
"permlink": "deeponion-pos-proof-of-stake-only",
"title": "DeepOnion: PoS (Proof of Stake) only?",
"body": "@@ -3646,16 +3646,175 @@\n y%0A%0A---%0A%0A\n+I published this article also on the DeepOnion community forum.%0Ahttps://deeponion.org/community/threads/article-deeponion-pos-proof-of-stake-only.34540/%0A%0A---%0A%0A\n Follow m\n",
"json_metadata": "{\"tags\":[\"deeponion\",\"pow\",\"pos\",\"comparison\",\"mining\"],\"users\":[\"cryptomaster\"],\"image\":[\"https://steemitimages.com/DQmShmoSSTtjSTNzSeroSG4eKRJ4yezUYQkcbKYyygmAgkV/image.png\",\"https://steemitimages.com/DQmSYhp3y7KnTRRFWkfBGueaSC3tpD6Vnq1eQNSSidkH6D2/image.png\"],\"links\":[\"https://digiconomist.net/bitcoin-energy-consumption\",\"https://deeponion.org/White-Paper.pdf\",\"https://deeponion.org/community/threads/article-deeponions-upcoming-vote-central-where-community-matters.26150/\",\"https://deeponion.org/community\",\"https://deeponion.org/community/threads/article-deeponion-pos-proof-of-stake-only.34540/\",\"https://twitter.com/BlockEncryptor\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}modemserupvoted (1.00%) @blockencryptor / deeponion-pos-proof-of-stake-only2018/04/05 07:55:45
modemserupvoted (1.00%) @blockencryptor / deeponion-pos-proof-of-stake-only
2018/04/05 07:55:45
| voter | modemser |
| author | blockencryptor |
| permlink | deeponion-pos-proof-of-stake-only |
| weight | 100 (1.00%) |
| Transaction Info | Block #21295068/Trx ad9a2e80ed2df84a326e2767ad05a83aa46a77d1 |
View Raw JSON Data
{
"trx_id": "ad9a2e80ed2df84a326e2767ad05a83aa46a77d1",
"block": 21295068,
"trx_in_block": 63,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-05T07:55:45",
"op": [
"vote",
{
"voter": "modemser",
"author": "blockencryptor",
"permlink": "deeponion-pos-proof-of-stake-only",
"weight": 100
}
]
}blockencryptorpublished a new post: deeponion-pos-proof-of-stake-only2018/04/05 07:54:45
blockencryptorpublished a new post: deeponion-pos-proof-of-stake-only
2018/04/05 07:54:45
| parent author | |
| parent permlink | deeponion |
| author | blockencryptor |
| permlink | deeponion-pos-proof-of-stake-only |
| title | DeepOnion: PoS (Proof of Stake) only? |
| body | @@ -144,17 +144,16 @@ ns in it -' s own bl |
| json metadata | {"tags":["deeponion","pow","pos","comparison","mining"],"users":["cryptomaster"],"image":["https://steemitimages.com/DQmShmoSSTtjSTNzSeroSG4eKRJ4yezUYQkcbKYyygmAgkV/image.png","https://steemitimages.com/DQmSYhp3y7KnTRRFWkfBGueaSC3tpD6Vnq1eQNSSidkH6D2/image.png"],"links":["https://digiconomist.net/bitcoin-energy-consumption","https://deeponion.org/White-Paper.pdf","https://deeponion.org/community/threads/article-deeponions-upcoming-vote-central-where-community-matters.26150/","https://deeponion.org/community","https://twitter.com/BlockEncryptor"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #21295048/Trx 813f6014d208e26daa60c2def84db5bd398a1e10 |
View Raw JSON Data
{
"trx_id": "813f6014d208e26daa60c2def84db5bd398a1e10",
"block": 21295048,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-05T07:54:45",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "deeponion",
"author": "blockencryptor",
"permlink": "deeponion-pos-proof-of-stake-only",
"title": "DeepOnion: PoS (Proof of Stake) only?",
"body": "@@ -144,17 +144,16 @@\n ns in it\n-'\n s own bl\n",
"json_metadata": "{\"tags\":[\"deeponion\",\"pow\",\"pos\",\"comparison\",\"mining\"],\"users\":[\"cryptomaster\"],\"image\":[\"https://steemitimages.com/DQmShmoSSTtjSTNzSeroSG4eKRJ4yezUYQkcbKYyygmAgkV/image.png\",\"https://steemitimages.com/DQmSYhp3y7KnTRRFWkfBGueaSC3tpD6Vnq1eQNSSidkH6D2/image.png\"],\"links\":[\"https://digiconomist.net/bitcoin-energy-consumption\",\"https://deeponion.org/White-Paper.pdf\",\"https://deeponion.org/community/threads/article-deeponions-upcoming-vote-central-where-community-matters.26150/\",\"https://deeponion.org/community\",\"https://twitter.com/BlockEncryptor\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}grammarnaziupvoted (50.00%) @blockencryptor / deeponion-pos-proof-of-stake-only2018/04/05 07:54:21
grammarnaziupvoted (50.00%) @blockencryptor / deeponion-pos-proof-of-stake-only
2018/04/05 07:54:21
| voter | grammarnazi |
| author | blockencryptor |
| permlink | deeponion-pos-proof-of-stake-only |
| weight | 5000 (50.00%) |
| Transaction Info | Block #21295040/Trx b964317e91b62e60d0048a313610b83f36ce032b |
View Raw JSON Data
{
"trx_id": "b964317e91b62e60d0048a313610b83f36ce032b",
"block": 21295040,
"trx_in_block": 71,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-05T07:54:21",
"op": [
"vote",
{
"voter": "grammarnazi",
"author": "blockencryptor",
"permlink": "deeponion-pos-proof-of-stake-only",
"weight": 5000
}
]
}2018/04/05 07:54:18
2018/04/05 07:54:18
| parent author | blockencryptor |
| parent permlink | deeponion-pos-proof-of-stake-only |
| author | grammarnazi |
| permlink | re-blockencryptor-deeponion-pos-proof-of-stake-only-20180405t075423862z |
| title | Minor Correction |
| body | You have a minor grammatical mistake in the following sentence: <blockquote>According to their Whitepaper, DeepOnion uses a combined PoW (Proof-of-Work) and PoS (Proof-of-Stake) consensus algorithm to confirm transactions in it's own blockchain.</blockquote> It should be <i>its own</i> instead of <i>it's own</i>. |
| json metadata | {"app":"steemit"} |
| Transaction Info | Block #21295039/Trx 4ee7c9a555a374332b0bdcffa94c7c6e36ee15c0 |
View Raw JSON Data
{
"trx_id": "4ee7c9a555a374332b0bdcffa94c7c6e36ee15c0",
"block": 21295039,
"trx_in_block": 14,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-05T07:54:18",
"op": [
"comment",
{
"parent_author": "blockencryptor",
"parent_permlink": "deeponion-pos-proof-of-stake-only",
"author": "grammarnazi",
"permlink": "re-blockencryptor-deeponion-pos-proof-of-stake-only-20180405t075423862z",
"title": "Minor Correction",
"body": "You have a minor grammatical mistake in the following sentence: <blockquote>According to their Whitepaper, DeepOnion uses a combined PoW (Proof-of-Work) and PoS (Proof-of-Stake) consensus algorithm to confirm transactions in it's own blockchain.</blockquote> It should be <i>its own</i> instead of <i>it's own</i>.",
"json_metadata": "{\"app\":\"steemit\"}"
}
]
}blockencryptorpublished a new post: deeponion-pos-proof-of-stake-only2018/04/05 07:54:15
blockencryptorpublished a new post: deeponion-pos-proof-of-stake-only
2018/04/05 07:54:15
| parent author | |
| parent permlink | deeponion |
| author | blockencryptor |
| permlink | deeponion-pos-proof-of-stake-only |
| title | DeepOnion: PoS (Proof of Stake) only? |
| body | According to their Whitepaper, DeepOnion uses a combined PoW (Proof-of-Work) and PoS (Proof-of-Stake) consensus algorithm to confirm transactions in it's own blockchain. Recently there were many discussions on the DeepOnion community board about switching to a PoS only coin, so I assume this will be a topic on vote central (DeepOnion's voting platform) in the near future. This is an important topic and I wrote this article to summarize the main advantages of both mining types and the combination of them. I want to help to get more qualified votes. <center>  DeepOnion Hybrid PoW/PoS Overview (Credits to @Cryptomaster) </center> Let me first clear up what the purpose of these algorithms are. Mining is required in decentralized systems to validate your transactions, generate new blocks and achieve distributed consensus. The classic Proof of Work mining process requires computation power. Basically you have to brute force a solution for a mathematical task and compete with others to be the first one and get the reward. Proof of Stake uses a more eco-friendly way to achieve a distributed consensus over all nodes. It depends on a random selection and the amount or stake on an address. Depending on the implementation there is also a factor called 'coin age' where you can only stake after a defined amount of time after you received your funds on an address. ### What are the advantages Proof of Work? * Established The most famous cryptocurrency, bitcoin, uses PoW for a few years and the algorithm is matured and widely used. * Encourages the use of the currency Miners need to invest in hardware and electricity to get rewards from their activity. This encourages the miners to sell the currency to reach their break even point * Cold storage Compared to PoS there is no need to use a wallet which is connected to the internet. You can just create your addresses offline and send your coins to it. ### What are the advantages Proof of Stake? * Eco friendly This is the main advantage of Proof of Stake. You don't need computation power to achieve consensus. Bitcoin's estimated annual energy consumption is about 60 TWh for 2018 according to this site. https://digiconomist.net/bitcoin-energy-consumption * Interests Everyone holding DeepOnion can receive staking rewards based on their amount. Stakers will receive about 10% in the first year, 5% in the second year and afterwards 1% per year when they help to secure the network and have a running and staking wallet. * Demand Other to PoW you are required to have coins to get rewards from mining and therefore this contributes to a higher demand of the coin. ### What are the advantages of a Hybrid? There is one major disadvantage of PoS coins. On a hard fork you can easily mine both forks without any additional effort. If you want to mine both forks in a PoW coin, you would need more hashing power to achieve it. Summarized I would say DeepOnion made the right choice with its hybrid coin. They have the advantages of a PoS coin and the backup of the PoW miners. They can motivate miners to upgrade to the newer consensus rules, prevent 51% attacks and have an eco-friendly coin. I hope I have covered the most important points on this topic. If you have any additions or comments, please reply to this article. --- ### Links DeepOnion Whitepaper: https://deeponion.org/White-Paper.pdf Vote central: https://deeponion.org/community/threads/article-deeponions-upcoming-vote-central-where-community-matters.26150/ DeepOnion community board: https://deeponion.org/community --- Follow me on twitter for the newest updates and giveaways. https://twitter.com/BlockEncryptor <center>  </center> |
| json metadata | {"tags":["deeponion","pow","pos","comparison","mining"],"users":["cryptomaster"],"image":["https://steemitimages.com/DQmShmoSSTtjSTNzSeroSG4eKRJ4yezUYQkcbKYyygmAgkV/image.png","https://steemitimages.com/DQmSYhp3y7KnTRRFWkfBGueaSC3tpD6Vnq1eQNSSidkH6D2/image.png"],"links":["https://digiconomist.net/bitcoin-energy-consumption","https://deeponion.org/White-Paper.pdf","https://deeponion.org/community/threads/article-deeponions-upcoming-vote-central-where-community-matters.26150/","https://deeponion.org/community","https://twitter.com/BlockEncryptor"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #21295038/Trx e6bebc6fc63d25770442618f18c1474b775f0faa |
View Raw JSON Data
{
"trx_id": "e6bebc6fc63d25770442618f18c1474b775f0faa",
"block": 21295038,
"trx_in_block": 20,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-05T07:54:15",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "deeponion",
"author": "blockencryptor",
"permlink": "deeponion-pos-proof-of-stake-only",
"title": "DeepOnion: PoS (Proof of Stake) only?",
"body": "According to their Whitepaper, DeepOnion uses a combined PoW (Proof-of-Work) and PoS (Proof-of-Stake) consensus algorithm to confirm transactions in it's own blockchain. Recently there were many discussions on the DeepOnion community board about switching to a PoS only coin, so I assume this will be a topic on vote central (DeepOnion's voting platform) in the near future.\n\nThis is an important topic and I wrote this article to summarize the main advantages of both mining types and the combination of them. I want to help to get more qualified votes. \n\n<center>\n\nDeepOnion Hybrid PoW/PoS Overview (Credits to @Cryptomaster)\n</center>\n\nLet me first clear up what the purpose of these algorithms are. Mining is required in decentralized systems to validate your transactions, generate new blocks and achieve distributed consensus. The classic Proof of Work mining process requires computation power. Basically you have to brute force a solution for a mathematical task and compete with others to be the first one and get the reward. \n\nProof of Stake uses a more eco-friendly way to achieve a distributed consensus over all nodes. It depends on a random selection and the amount or stake on an address. Depending on the implementation there is also a factor called 'coin age' where you can only stake after a defined amount of time after you received your funds on an address.\n\n### What are the advantages Proof of Work?\n* Established\nThe most famous cryptocurrency, bitcoin, uses PoW for a few years and the algorithm is matured and widely used.\n* Encourages the use of the currency\nMiners need to invest in hardware and electricity to get rewards from their activity. This encourages the miners to sell the currency to reach their break even point\n* Cold storage \nCompared to PoS there is no need to use a wallet which is connected to the internet. You can just create your addresses offline and send your coins to it.\n\n### What are the advantages Proof of Stake?\n* Eco friendly\nThis is the main advantage of Proof of Stake. You don't need computation power to achieve consensus. Bitcoin's estimated annual energy consumption is about 60 TWh for 2018 according to this site.\nhttps://digiconomist.net/bitcoin-energy-consumption\n* Interests\nEveryone holding DeepOnion can receive staking rewards based on their amount. Stakers will receive about 10% in the first year, 5% in the second year and afterwards 1% per year when they help to secure the network and have a running and staking wallet.\n* Demand\nOther to PoW you are required to have coins to get rewards from mining and therefore this contributes to a higher demand of the coin.\n\n### What are the advantages of a Hybrid?\nThere is one major disadvantage of PoS coins. On a hard fork you can easily mine both forks without any additional effort. If you want to mine both forks in a PoW coin, you would need more hashing power to achieve it.\n\nSummarized I would say DeepOnion made the right choice with its hybrid coin. They have the advantages of a PoS coin and the backup of the PoW miners. They can motivate miners to upgrade to the newer consensus rules, prevent 51% attacks and have an eco-friendly coin.\n\nI hope I have covered the most important points on this topic. If you have any additions or comments, please reply to this article.\n\n---\n### Links\nDeepOnion Whitepaper: https://deeponion.org/White-Paper.pdf\nVote central: https://deeponion.org/community/threads/article-deeponions-upcoming-vote-central-where-community-matters.26150/\nDeepOnion community board: https://deeponion.org/community\n\n---\n\nFollow me on twitter for the newest updates and giveaways.\nhttps://twitter.com/BlockEncryptor\n\n<center>\n\n</center>",
"json_metadata": "{\"tags\":[\"deeponion\",\"pow\",\"pos\",\"comparison\",\"mining\"],\"users\":[\"cryptomaster\"],\"image\":[\"https://steemitimages.com/DQmShmoSSTtjSTNzSeroSG4eKRJ4yezUYQkcbKYyygmAgkV/image.png\",\"https://steemitimages.com/DQmSYhp3y7KnTRRFWkfBGueaSC3tpD6Vnq1eQNSSidkH6D2/image.png\"],\"links\":[\"https://digiconomist.net/bitcoin-energy-consumption\",\"https://deeponion.org/White-Paper.pdf\",\"https://deeponion.org/community/threads/article-deeponions-upcoming-vote-central-where-community-matters.26150/\",\"https://deeponion.org/community\",\"https://twitter.com/BlockEncryptor\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}emreugurupvoted (100.00%) @blockencryptor / determining-the-best-input-size-for-staking2018/04/04 19:59:06
emreugurupvoted (100.00%) @blockencryptor / determining-the-best-input-size-for-staking
2018/04/04 19:59:06
| voter | emreugur |
| author | blockencryptor |
| permlink | determining-the-best-input-size-for-staking |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21280739/Trx 89b3b349811968bc33af4f8dde835b3293669115 |
View Raw JSON Data
{
"trx_id": "89b3b349811968bc33af4f8dde835b3293669115",
"block": 21280739,
"trx_in_block": 9,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-04T19:59:06",
"op": [
"vote",
{
"voter": "emreugur",
"author": "blockencryptor",
"permlink": "determining-the-best-input-size-for-staking",
"weight": 10000
}
]
}hr1upvoted (0.02%) @blockencryptor / i-created-a-cold-storage-wallet2018/04/04 06:54:27
hr1upvoted (0.02%) @blockencryptor / i-created-a-cold-storage-wallet
2018/04/04 06:54:27
| voter | hr1 |
| author | blockencryptor |
| permlink | i-created-a-cold-storage-wallet |
| weight | 2 (0.02%) |
| Transaction Info | Block #21265049/Trx 9124d3075dd4f019bdfba7040d6c971210e0472d |
View Raw JSON Data
{
"trx_id": "9124d3075dd4f019bdfba7040d6c971210e0472d",
"block": 21265049,
"trx_in_block": 30,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-04T06:54:27",
"op": [
"vote",
{
"voter": "hr1",
"author": "blockencryptor",
"permlink": "i-created-a-cold-storage-wallet",
"weight": 2
}
]
}blockencryptorpublished a new post: i-created-a-cold-storage-wallet2018/04/04 06:39:03
blockencryptorpublished a new post: i-created-a-cold-storage-wallet
2018/04/04 06:39:03
| parent author | |
| parent permlink | deeponion |
| author | blockencryptor |
| permlink | i-created-a-cold-storage-wallet |
| title | I created a 'cold storage' (wallet) |
| body | @@ -615,32 +615,63 @@ ld as my Wallet%0A +(Photo by Rob Bye on Unsplash)%0A %3C/center%3E%0A%0A### A @@ -5234,12 +5234,378 @@ dumpwallet. +%0A%0A---%0A%0AI also published this article on the DeepOnion community forum.%0Ahttps://deeponion.org/community/threads/article-i-created-a-cold-storage-wallet.34444/%0A%0A---%0A%0AFollow me on twitter for the newest updates and giveaways.%0Ahttps://twitter.com/BlockEncryptor%0A%0A%3Ccenter%3E%0A!%5B%5D(https://steemitimages.com/DQmSYhp3y7KnTRRFWkfBGueaSC3tpD6Vnq1eQNSSidkH6D2/image.png)%0A%3C/center%3E |
| json metadata | {"tags":["deeponion","wallet","coldstorage"],"image":["https://steemitimages.com/DQmPjUoVZmnso1iwZyN1pxLxaiygswsBKyRSzriPG8WnREd/image.png","https://steemitimages.com/DQmW3Mpfk9NYQ2YKeWpsMb8xB9whSRA8UZqkVrGUTb8rBZC/image.png","https://steemitimages.com/DQmWP7eKS1vB8pvBEQHMGiPpALL2nvSQWE3e1cbGxL3kMx4/image.png","https://steemitimages.com/DQmSYrRDjNKPW4F3tbzng3y2A9p6ug2s7UjewbQ2LMLXKMx/image.png","https://steemitimages.com/DQmSYhp3y7KnTRRFWkfBGueaSC3tpD6Vnq1eQNSSidkH6D2/image.png"],"links":["https://deeponion.org/community/threads/tutorial-how-to-send-from-an-offline-wallet-cold-storage-without-exposing-your-private-keys.23806/","https://deeponion.org/community/threads/tutorial-how-to-move-your-deeponion-appdata-folder-to-a-different-drive.23630","https://deeponion.org/community/threads/tutorial-how-to-obfuscate-your-password-inputs-with-keepass.26317/","https://deeponion.org/community/threads/article-i-created-a-cold-storage-wallet.34444/","https://twitter.com/BlockEncryptor"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #21264741/Trx 074f724ccf8ecae839d783f06d3df0ae324e84e4 |
View Raw JSON Data
{
"trx_id": "074f724ccf8ecae839d783f06d3df0ae324e84e4",
"block": 21264741,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-04T06:39:03",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "deeponion",
"author": "blockencryptor",
"permlink": "i-created-a-cold-storage-wallet",
"title": "I created a 'cold storage' (wallet)",
"body": "@@ -615,32 +615,63 @@\n ld as my Wallet%0A\n+(Photo by Rob Bye on Unsplash)%0A\n %3C/center%3E%0A%0A### A\n@@ -5234,12 +5234,378 @@\n dumpwallet.\n+%0A%0A---%0A%0AI also published this article on the DeepOnion community forum.%0Ahttps://deeponion.org/community/threads/article-i-created-a-cold-storage-wallet.34444/%0A%0A---%0A%0AFollow me on twitter for the newest updates and giveaways.%0Ahttps://twitter.com/BlockEncryptor%0A%0A%3Ccenter%3E%0A!%5B%5D(https://steemitimages.com/DQmSYhp3y7KnTRRFWkfBGueaSC3tpD6Vnq1eQNSSidkH6D2/image.png)%0A%3C/center%3E\n",
"json_metadata": "{\"tags\":[\"deeponion\",\"wallet\",\"coldstorage\"],\"image\":[\"https://steemitimages.com/DQmPjUoVZmnso1iwZyN1pxLxaiygswsBKyRSzriPG8WnREd/image.png\",\"https://steemitimages.com/DQmW3Mpfk9NYQ2YKeWpsMb8xB9whSRA8UZqkVrGUTb8rBZC/image.png\",\"https://steemitimages.com/DQmWP7eKS1vB8pvBEQHMGiPpALL2nvSQWE3e1cbGxL3kMx4/image.png\",\"https://steemitimages.com/DQmSYrRDjNKPW4F3tbzng3y2A9p6ug2s7UjewbQ2LMLXKMx/image.png\",\"https://steemitimages.com/DQmSYhp3y7KnTRRFWkfBGueaSC3tpD6Vnq1eQNSSidkH6D2/image.png\"],\"links\":[\"https://deeponion.org/community/threads/tutorial-how-to-send-from-an-offline-wallet-cold-storage-without-exposing-your-private-keys.23806/\",\"https://deeponion.org/community/threads/tutorial-how-to-move-your-deeponion-appdata-folder-to-a-different-drive.23630\",\"https://deeponion.org/community/threads/tutorial-how-to-obfuscate-your-password-inputs-with-keepass.26317/\",\"https://deeponion.org/community/threads/article-i-created-a-cold-storage-wallet.34444/\",\"https://twitter.com/BlockEncryptor\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}khansa-alifahupvoted (100.00%) @blockencryptor / i-created-a-cold-storage-wallet2018/04/04 06:28:18
khansa-alifahupvoted (100.00%) @blockencryptor / i-created-a-cold-storage-wallet
2018/04/04 06:28:18
| voter | khansa-alifah |
| author | blockencryptor |
| permlink | i-created-a-cold-storage-wallet |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21264526/Trx 2122aa45dccc97ba418be48c65bee8fdb6550345 |
View Raw JSON Data
{
"trx_id": "2122aa45dccc97ba418be48c65bee8fdb6550345",
"block": 21264526,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-04T06:28:18",
"op": [
"vote",
{
"voter": "khansa-alifah",
"author": "blockencryptor",
"permlink": "i-created-a-cold-storage-wallet",
"weight": 10000
}
]
}blockencryptorpublished a new post: i-created-a-cold-storage-wallet2018/04/04 06:25:27
blockencryptorpublished a new post: i-created-a-cold-storage-wallet
2018/04/04 06:25:27
| parent author | |
| parent permlink | deeponion |
| author | blockencryptor |
| permlink | i-created-a-cold-storage-wallet |
| title | I created a 'cold storage' (wallet) |
| body | I have planned to buy more $onions at the end of the airdrop and therefore I wanted a secure wallet, a real cold wallet. I assume the most people just download the wallet software on their main computer and create their wallet.dat there. But there are always risks when creating a wallet on an online computer. The computer could be infected with malware or attackers could sniff the network. I am a long term holder and didn't want to worry about my wallet. I wanted a **secure cold storage**. <center>  A Frozen Lake - Cold as my Wallet </center> ### Approach My approach to achieve this was to create a wallet on an offline machine and encrypt it there. Then I would test it, create a few backups and send my funds to it which I want to store long term. Not the easiest way to set up a new wallet, but the advantage is that the private keys are never exposed to the internet. No one without physical access will be able to steal the funds. That's a safe feeling. ### Practical Implementation First of all I needed an offline device. Fortunately I had an old laptop which I didn't use anymore. I reinstalled windows and disabled all network devices to make sure that it is disconnected. In the next step I downloaded the newest from the DeepOnion website and moved it via an USB stick to the laptop. Now I started the wallet and checked for new folders and files under %appdata%. Everything worked as expected. I had a new DeepOnion folder and in it my cold wallet.dat. The wallet software is of course out of sync and will not show any values. <center>  Offline Generated DeepOnion Wallet </center> ### Testing the wallet After I had encrypted the wallet file, it was time to test that I can send from the wallet. It's very unlikely that there could be any issues, but I prefer to ensure that all is working fine. The idea is to create everything offline and only move the encrypted wallet.dat to an online computer. It isn't required to unlock it there, it's just used to list all unspent inputs and prepare an outgoing transaction, which is then signed offline. I needed to sign a transaction from the offline wallet. Fortunately I had this already tested a while ago and wrote a tutorial about it. https://deeponion.org/community/threads/tutorial-how-to-send-from-an-offline-wallet-cold-storage-without-exposing-your-private-keys.23806/ First I created the raw transaction on the online wallet. <center>  Creation of an raw Transaction </center> Then I moved this to the offline computer and signed it there. <center>  Signing a raw Transaction </center> Everything worked on the first try. Now, I am quite sure that everything works and that it's nearly impossible to steal funds from this address. I own now a wallet where the private keys were never exposed on a computer which is connected to the internet. As there is currently no hardware wallet available for DeepOnion, this is a good alternative to create a secure wallet. ### Usability improvements Of course it's not convenient to create a raw transaction every time I want to send funds. Therefore I moved the entire DeepOnion folder to a USB stick and created a symbolic link on the online machine as described in this post. https://deeponion.org/community/threads/tutorial-how-to-move-your-deeponion-appdata-folder-to-a-different-drive.23630 Now it's only possible to send funds when I connect my USB stick to the machine. There were still one problem. How can I unlock my wallet without risking to lose my password? KeePass provides an easy way to obfuscate your password entries, you just have to set one checkbox and it will partly auto-type and partly paste from the clipboard. https://deeponion.org/community/threads/tutorial-how-to-obfuscate-your-password-inputs-with-keepass.26317/ ### Outlook It is possible to create a cold storage for DeepOnion and you just need a computer which is not connected to the internet and an USB stick. Depending on the requirements it's possible to never expose anything to the internet, which makes it a real secure storage. ##### Further cooling If you are serious about the wallet and don't want anything exposed, you can also download the entire blockchain on an online computer and move the data to the offline machine. Then you can there list the unspent inputs, create the transaction and just broadcast it on an online machine. You would not be required to use anything online. ##### Open risks * Bruteforce the wallet.dat Someone could steal the wallet.dat from the computer and just test different passwords against it. As long as the password is strong enough and there is no security vulnerability, it will unsuccessful with the today's computing power. * Physical access No real risk when the wallet.dat is also encrypted on the offline computer. It's recommended to use an encrypted hard disk when using dumpwallet. |
| json metadata | {"tags":["deeponion","wallet","coldstorage"],"image":["https://steemitimages.com/DQmPjUoVZmnso1iwZyN1pxLxaiygswsBKyRSzriPG8WnREd/image.png","https://steemitimages.com/DQmW3Mpfk9NYQ2YKeWpsMb8xB9whSRA8UZqkVrGUTb8rBZC/image.png","https://steemitimages.com/DQmWP7eKS1vB8pvBEQHMGiPpALL2nvSQWE3e1cbGxL3kMx4/image.png","https://steemitimages.com/DQmSYrRDjNKPW4F3tbzng3y2A9p6ug2s7UjewbQ2LMLXKMx/image.png"],"links":["https://deeponion.org/community/threads/tutorial-how-to-send-from-an-offline-wallet-cold-storage-without-exposing-your-private-keys.23806/","https://deeponion.org/community/threads/tutorial-how-to-move-your-deeponion-appdata-folder-to-a-different-drive.23630","https://deeponion.org/community/threads/tutorial-how-to-obfuscate-your-password-inputs-with-keepass.26317/"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #21264469/Trx 2cb04e17c372149ff6e12ed13c95cc89e81d6a2f |
View Raw JSON Data
{
"trx_id": "2cb04e17c372149ff6e12ed13c95cc89e81d6a2f",
"block": 21264469,
"trx_in_block": 94,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-04T06:25:27",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "deeponion",
"author": "blockencryptor",
"permlink": "i-created-a-cold-storage-wallet",
"title": "I created a 'cold storage' (wallet)",
"body": "I have planned to buy more $onions at the end of the airdrop and therefore I wanted a secure wallet, a real cold wallet. I assume the most people just download the wallet software on their main computer and create their wallet.dat there. But there are always risks when creating a wallet on an online computer. The computer could be infected with malware or attackers could sniff the network.\n\nI am a long term holder and didn't want to worry about my wallet. I wanted a **secure cold storage**. \n\n<center>\n\nA Frozen Lake - Cold as my Wallet\n</center>\n\n### Approach\nMy approach to achieve this was to create a wallet on an offline machine and encrypt it there. Then I would test it, create a few backups and send my funds to it which I want to store long term.\n\nNot the easiest way to set up a new wallet, but the advantage is that the private keys are never exposed to the internet. No one without physical access will be able to steal the funds. That's a safe feeling.\n\n### Practical Implementation\nFirst of all I needed an offline device. Fortunately I had an old laptop which I didn't use anymore. I reinstalled windows and disabled all network devices to make sure that it is disconnected.\n\nIn the next step I downloaded the newest from the DeepOnion website and moved it via an USB stick to the laptop. Now I started the wallet and checked for new folders and files under %appdata%. Everything worked as expected. I had a new DeepOnion folder and in it my cold wallet.dat. The wallet software is of course out of sync and will not show any values.\n\n<center>\n\nOffline Generated DeepOnion Wallet\n</center>\n\n### Testing the wallet\nAfter I had encrypted the wallet file, it was time to test that I can send from the wallet. It's very unlikely that there could be any issues, but I prefer to ensure that all is working fine.\n\nThe idea is to create everything offline and only move the encrypted wallet.dat to an online computer. It isn't required to unlock it there, it's just used to list all unspent inputs and prepare an outgoing transaction, which is then signed offline.\n\nI needed to sign a transaction from the offline wallet. Fortunately I had this already tested a while ago and wrote a tutorial about it.\nhttps://deeponion.org/community/threads/tutorial-how-to-send-from-an-offline-wallet-cold-storage-without-exposing-your-private-keys.23806/\n\nFirst I created the raw transaction on the online wallet.\n<center>\n\nCreation of an raw Transaction\n</center>\n\nThen I moved this to the offline computer and signed it there.\n<center>\n\nSigning a raw Transaction\n</center>\n\nEverything worked on the first try. Now, I am quite sure that everything works and that it's nearly impossible to steal funds from this address. \n\nI own now a wallet where the private keys were never exposed on a computer which is connected to the internet. As there is currently no hardware wallet available for DeepOnion, this is a good alternative to create a secure wallet. \n\n### Usability improvements\nOf course it's not convenient to create a raw transaction every time I want to send funds. Therefore I moved the entire DeepOnion folder to a USB stick and created a symbolic link on the online machine as described in this post.\nhttps://deeponion.org/community/threads/tutorial-how-to-move-your-deeponion-appdata-folder-to-a-different-drive.23630\n\nNow it's only possible to send funds when I connect my USB stick to the machine. There were still one problem. How can I unlock my wallet without risking to lose my password? KeePass provides an easy way to obfuscate your password entries, you just have to set one checkbox and it will partly auto-type and partly paste from the clipboard.\nhttps://deeponion.org/community/threads/tutorial-how-to-obfuscate-your-password-inputs-with-keepass.26317/\n\n### Outlook\nIt is possible to create a cold storage for DeepOnion and you just need a computer which is not connected to the internet and an USB stick. Depending on the requirements it's possible to never expose anything to the internet, which makes it a real secure storage. \n\n##### Further cooling\nIf you are serious about the wallet and don't want anything exposed, you can also download the entire blockchain on an online computer and move the data to the offline machine. Then you can there list the unspent inputs, create the transaction and just broadcast it on an online machine. You would not be required to use anything online.\n\n##### Open risks\n* Bruteforce the wallet.dat\nSomeone could steal the wallet.dat from the computer and just test different passwords against it. As long as the password is strong enough and there is no security vulnerability, it will unsuccessful with the today's computing power.\n\n* Physical access\nNo real risk when the wallet.dat is also encrypted on the offline computer. It's recommended to use an encrypted hard disk when using dumpwallet.",
"json_metadata": "{\"tags\":[\"deeponion\",\"wallet\",\"coldstorage\"],\"image\":[\"https://steemitimages.com/DQmPjUoVZmnso1iwZyN1pxLxaiygswsBKyRSzriPG8WnREd/image.png\",\"https://steemitimages.com/DQmW3Mpfk9NYQ2YKeWpsMb8xB9whSRA8UZqkVrGUTb8rBZC/image.png\",\"https://steemitimages.com/DQmWP7eKS1vB8pvBEQHMGiPpALL2nvSQWE3e1cbGxL3kMx4/image.png\",\"https://steemitimages.com/DQmSYrRDjNKPW4F3tbzng3y2A9p6ug2s7UjewbQ2LMLXKMx/image.png\"],\"links\":[\"https://deeponion.org/community/threads/tutorial-how-to-send-from-an-offline-wallet-cold-storage-without-exposing-your-private-keys.23806/\",\"https://deeponion.org/community/threads/tutorial-how-to-move-your-deeponion-appdata-folder-to-a-different-drive.23630\",\"https://deeponion.org/community/threads/tutorial-how-to-obfuscate-your-password-inputs-with-keepass.26317/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}blockencryptorpublished a new post: i-created-a-cold-storage-wallet2018/04/04 06:24:36
blockencryptorpublished a new post: i-created-a-cold-storage-wallet
2018/04/04 06:24:36
| parent author | |
| parent permlink | deeponion |
| author | blockencryptor |
| permlink | i-created-a-cold-storage-wallet |
| title | I created a 'cold storage' wallet |
| body | I have planned to buy more $onions at the end of the airdrop and therefore I wanted a secure wallet, a real cold wallet. I assume the most people just download the wallet software on their main computer and create their wallet.dat there. But there are always risks when creating a wallet on an online computer. The computer could be infected with malware or attackers could sniff the network. I am a long term holder and didn't want to worry about my wallet. I wanted a **secure cold storage**. <center>  A Frozen Lake - Cold as my Wallet </center> ### Approach My approach to achieve this was to create a wallet on an offline machine and encrypt it there. Then I would test it, create a few backups and send my funds to it which I want to store long term. Not the easiest way to set up a new wallet, but the advantage is that the private keys are never exposed to the internet. No one without physical access will be able to steal the funds. That's a safe feeling. ### Practical Implementation First of all I needed an offline device. Fortunately I had an old laptop which I didn't use anymore. I reinstalled windows and disabled all network devices to make sure that it is disconnected. In the next step I downloaded the newest from the DeepOnion website and moved it via an USB stick to the laptop. Now I started the wallet and checked for new folders and files under %appdata%. Everything worked as expected. I had a new DeepOnion folder and in it my cold wallet.dat. The wallet software is of course out of sync and will not show any values. <center>  Offline Generated DeepOnion Wallet </center> ### Testing the wallet After I had encrypted the wallet file, it was time to test that I can send from the wallet. It's very unlikely that there could be any issues, but I prefer to ensure that all is working fine. The idea is to create everything offline and only move the encrypted wallet.dat to an online computer. It isn't required to unlock it there, it's just used to list all unspent inputs and prepare an outgoing transaction, which is then signed offline. I needed to sign a transaction from the offline wallet. Fortunately I had this already tested a while ago and wrote a tutorial about it. https://deeponion.org/community/threads/tutorial-how-to-send-from-an-offline-wallet-cold-storage-without-exposing-your-private-keys.23806/ First I created the raw transaction on the online wallet. <center>  Creation of an raw Transaction </center> Then I moved this to the offline computer and signed it there. <center>  Signing a raw Transaction </center> Everything worked on the first try. Now, I am quite sure that everything works and that it's nearly impossible to steal funds from this address. I own now a wallet where the private keys were never exposed on a computer which is connected to the internet. As there is currently no hardware wallet available for DeepOnion, this is a good alternative to create a secure wallet. ### Usability improvements Of course it's not convenient to create a raw transaction every time I want to send funds. Therefore I moved the entire DeepOnion folder to a USB stick and created a symbolic link on the online machine as described in this post. https://deeponion.org/community/threads/tutorial-how-to-move-your-deeponion-appdata-folder-to-a-different-drive.23630 Now it's only possible to send funds when I connect my USB stick to the machine. There were still one problem. How can I unlock my wallet without risking to lose my password? KeePass provides an easy way to obfuscate your password entries, you just have to set one checkbox and it will partly auto-type and partly paste from the clipboard. https://deeponion.org/community/threads/tutorial-how-to-obfuscate-your-password-inputs-with-keepass.26317/ ### Outlook It is possible to create a cold storage for DeepOnion and you just need a computer which is not connected to the internet and an USB stick. Depending on the requirements it's possible to never expose anything to the internet, which makes it a real secure storage. ##### Further cooling If you are serious about the wallet and don't want anything exposed, you can also download the entire blockchain on an online computer and move the data to the offline machine. Then you can there list the unspent inputs, create the transaction and just broadcast it on an online machine. You would not be required to use anything online. ##### Open risks * Bruteforce the wallet.dat Someone could steal the wallet.dat from the computer and just test different passwords against it. As long as the password is strong enough and there is no security vulnerability, it will unsuccessful with the today's computing power. * Physical access No real risk when the wallet.dat is also encrypted on the offline computer. It's recommended to use an encrypted hard disk when using dumpwallet. |
| json metadata | {"tags":["deeponion","wallet","coldstorage"],"image":["https://steemitimages.com/DQmPjUoVZmnso1iwZyN1pxLxaiygswsBKyRSzriPG8WnREd/image.png","https://steemitimages.com/DQmW3Mpfk9NYQ2YKeWpsMb8xB9whSRA8UZqkVrGUTb8rBZC/image.png","https://steemitimages.com/DQmWP7eKS1vB8pvBEQHMGiPpALL2nvSQWE3e1cbGxL3kMx4/image.png","https://steemitimages.com/DQmSYrRDjNKPW4F3tbzng3y2A9p6ug2s7UjewbQ2LMLXKMx/image.png"],"links":["https://deeponion.org/community/threads/tutorial-how-to-send-from-an-offline-wallet-cold-storage-without-exposing-your-private-keys.23806/","https://deeponion.org/community/threads/tutorial-how-to-move-your-deeponion-appdata-folder-to-a-different-drive.23630","https://deeponion.org/community/threads/tutorial-how-to-obfuscate-your-password-inputs-with-keepass.26317/"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #21264452/Trx 12546c17facbf6dc2af757f7f67d46172f5c9c4d |
View Raw JSON Data
{
"trx_id": "12546c17facbf6dc2af757f7f67d46172f5c9c4d",
"block": 21264452,
"trx_in_block": 66,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-04T06:24:36",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "deeponion",
"author": "blockencryptor",
"permlink": "i-created-a-cold-storage-wallet",
"title": "I created a 'cold storage' wallet",
"body": "I have planned to buy more $onions at the end of the airdrop and therefore I wanted a secure wallet, a real cold wallet. I assume the most people just download the wallet software on their main computer and create their wallet.dat there. But there are always risks when creating a wallet on an online computer. The computer could be infected with malware or attackers could sniff the network.\n\nI am a long term holder and didn't want to worry about my wallet. I wanted a **secure cold storage**. \n\n<center>\n\nA Frozen Lake - Cold as my Wallet\n</center>\n\n### Approach\nMy approach to achieve this was to create a wallet on an offline machine and encrypt it there. Then I would test it, create a few backups and send my funds to it which I want to store long term.\n\nNot the easiest way to set up a new wallet, but the advantage is that the private keys are never exposed to the internet. No one without physical access will be able to steal the funds. That's a safe feeling.\n\n### Practical Implementation\nFirst of all I needed an offline device. Fortunately I had an old laptop which I didn't use anymore. I reinstalled windows and disabled all network devices to make sure that it is disconnected.\n\nIn the next step I downloaded the newest from the DeepOnion website and moved it via an USB stick to the laptop. Now I started the wallet and checked for new folders and files under %appdata%. Everything worked as expected. I had a new DeepOnion folder and in it my cold wallet.dat. The wallet software is of course out of sync and will not show any values.\n\n<center>\n\nOffline Generated DeepOnion Wallet\n</center>\n\n### Testing the wallet\nAfter I had encrypted the wallet file, it was time to test that I can send from the wallet. It's very unlikely that there could be any issues, but I prefer to ensure that all is working fine.\n\nThe idea is to create everything offline and only move the encrypted wallet.dat to an online computer. It isn't required to unlock it there, it's just used to list all unspent inputs and prepare an outgoing transaction, which is then signed offline.\n\nI needed to sign a transaction from the offline wallet. Fortunately I had this already tested a while ago and wrote a tutorial about it.\nhttps://deeponion.org/community/threads/tutorial-how-to-send-from-an-offline-wallet-cold-storage-without-exposing-your-private-keys.23806/\n\nFirst I created the raw transaction on the online wallet.\n<center>\n\nCreation of an raw Transaction\n</center>\n\nThen I moved this to the offline computer and signed it there.\n<center>\n\nSigning a raw Transaction\n</center>\n\nEverything worked on the first try. Now, I am quite sure that everything works and that it's nearly impossible to steal funds from this address. \n\nI own now a wallet where the private keys were never exposed on a computer which is connected to the internet. As there is currently no hardware wallet available for DeepOnion, this is a good alternative to create a secure wallet. \n\n### Usability improvements\nOf course it's not convenient to create a raw transaction every time I want to send funds. Therefore I moved the entire DeepOnion folder to a USB stick and created a symbolic link on the online machine as described in this post.\nhttps://deeponion.org/community/threads/tutorial-how-to-move-your-deeponion-appdata-folder-to-a-different-drive.23630\n\nNow it's only possible to send funds when I connect my USB stick to the machine. There were still one problem. How can I unlock my wallet without risking to lose my password? KeePass provides an easy way to obfuscate your password entries, you just have to set one checkbox and it will partly auto-type and partly paste from the clipboard.\nhttps://deeponion.org/community/threads/tutorial-how-to-obfuscate-your-password-inputs-with-keepass.26317/\n\n### Outlook\nIt is possible to create a cold storage for DeepOnion and you just need a computer which is not connected to the internet and an USB stick. Depending on the requirements it's possible to never expose anything to the internet, which makes it a real secure storage. \n\n##### Further cooling\nIf you are serious about the wallet and don't want anything exposed, you can also download the entire blockchain on an online computer and move the data to the offline machine. Then you can there list the unspent inputs, create the transaction and just broadcast it on an online machine. You would not be required to use anything online.\n\n##### Open risks\n* Bruteforce the wallet.dat\nSomeone could steal the wallet.dat from the computer and just test different passwords against it. As long as the password is strong enough and there is no security vulnerability, it will unsuccessful with the today's computing power.\n\n* Physical access\nNo real risk when the wallet.dat is also encrypted on the offline computer. It's recommended to use an encrypted hard disk when using dumpwallet.",
"json_metadata": "{\"tags\":[\"deeponion\",\"wallet\",\"coldstorage\"],\"image\":[\"https://steemitimages.com/DQmPjUoVZmnso1iwZyN1pxLxaiygswsBKyRSzriPG8WnREd/image.png\",\"https://steemitimages.com/DQmW3Mpfk9NYQ2YKeWpsMb8xB9whSRA8UZqkVrGUTb8rBZC/image.png\",\"https://steemitimages.com/DQmWP7eKS1vB8pvBEQHMGiPpALL2nvSQWE3e1cbGxL3kMx4/image.png\",\"https://steemitimages.com/DQmSYrRDjNKPW4F3tbzng3y2A9p6ug2s7UjewbQ2LMLXKMx/image.png\"],\"links\":[\"https://deeponion.org/community/threads/tutorial-how-to-send-from-an-offline-wallet-cold-storage-without-exposing-your-private-keys.23806/\",\"https://deeponion.org/community/threads/tutorial-how-to-move-your-deeponion-appdata-folder-to-a-different-drive.23630\",\"https://deeponion.org/community/threads/tutorial-how-to-obfuscate-your-password-inputs-with-keepass.26317/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}blockencryptorpublished a new post: deeponion-wallet-distribution2018/04/02 15:50:57
blockencryptorpublished a new post: deeponion-wallet-distribution
2018/04/02 15:50:57
| parent author | |
| parent permlink | deeponion |
| author | blockencryptor |
| permlink | deeponion-wallet-distribution |
| title | DeepOnion Wallet Distribution |
| body | @@ -1238,16 +1238,324 @@ enter%3E%0A%0A +%3Ccenter%3E%0A!%5B%5D(https://steemitimages.com/DQmbpPJomJ5ojRbysP3Xx3guNSJitTUPVPPHEUYU1h8N4dQ/image.png)%0A DeepOnion Wallet Distribution (01.04.2018)%E2%80%8B%0A%3C/center%3E%0A%0A%3Ccenter%3E%0A!%5B%5D(https://steemitimages.com/DQmbyrejYAaYtrBgg1TMX3TQ6m4q4neQgp8qDKs2DQ57jhy/image.png)%0A DeepOnion Wallet Distribution (02.04.2018)%E2%80%8B%0A%3C/center%3E%0A%0A The abov |
| json metadata | {"tags":["deeponion","wallet","distribution","upgrade","deepprotocol"],"image":["https://steemitimages.com/DQmaSPmcwqf184WjeBoJcUUEYQJ15wqHdTkaAp9REQSB8x5/image.png","https://steemitimages.com/DQmZxZMvAnZUPB4H3Nfj6pBV5E3jn4BfHNYJ1gx5gdThWNA/image.png","https://steemitimages.com/DQmfKdooj9qH27aGfoWcZrJs5aFL66ddac6vi1ae999u5bR/image.png","https://steemitimages.com/DQmbpPJomJ5ojRbysP3Xx3guNSJitTUPVPPHEUYU1h8N4dQ/image.png","https://steemitimages.com/DQmbyrejYAaYtrBgg1TMX3TQ6m4q4neQgp8qDKs2DQ57jhy/image.png"],"links":["http://onionexplorer.youngwebsolutions.com:3001/","http://explorer.deeponion.org","https://deeponion.org/community/threads/deeponion-v-1-6-1-released-important-upgrade-mandatory-upgrade.33401/","https://deeponion.org/community/threads/article-deeponion-hard-fork-faq.33079/","https://deeponion.org/community/threads/article-deeponion-wallet-distribution.33972/"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #21218186/Trx b3cf2182fd386587894a444f14656756fd914d26 |
View Raw JSON Data
{
"trx_id": "b3cf2182fd386587894a444f14656756fd914d26",
"block": 21218186,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-02T15:50:57",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "deeponion",
"author": "blockencryptor",
"permlink": "deeponion-wallet-distribution",
"title": "DeepOnion Wallet Distribution",
"body": "@@ -1238,16 +1238,324 @@\n enter%3E%0A%0A\n+%3Ccenter%3E%0A!%5B%5D(https://steemitimages.com/DQmbpPJomJ5ojRbysP3Xx3guNSJitTUPVPPHEUYU1h8N4dQ/image.png)%0A DeepOnion Wallet Distribution (01.04.2018)%E2%80%8B%0A%3C/center%3E%0A%0A%3Ccenter%3E%0A!%5B%5D(https://steemitimages.com/DQmbyrejYAaYtrBgg1TMX3TQ6m4q4neQgp8qDKs2DQ57jhy/image.png)%0A DeepOnion Wallet Distribution (02.04.2018)%E2%80%8B%0A%3C/center%3E%0A%0A\n The abov\n",
"json_metadata": "{\"tags\":[\"deeponion\",\"wallet\",\"distribution\",\"upgrade\",\"deepprotocol\"],\"image\":[\"https://steemitimages.com/DQmaSPmcwqf184WjeBoJcUUEYQJ15wqHdTkaAp9REQSB8x5/image.png\",\"https://steemitimages.com/DQmZxZMvAnZUPB4H3Nfj6pBV5E3jn4BfHNYJ1gx5gdThWNA/image.png\",\"https://steemitimages.com/DQmfKdooj9qH27aGfoWcZrJs5aFL66ddac6vi1ae999u5bR/image.png\",\"https://steemitimages.com/DQmbpPJomJ5ojRbysP3Xx3guNSJitTUPVPPHEUYU1h8N4dQ/image.png\",\"https://steemitimages.com/DQmbyrejYAaYtrBgg1TMX3TQ6m4q4neQgp8qDKs2DQ57jhy/image.png\"],\"links\":[\"http://onionexplorer.youngwebsolutions.com:3001/\",\"http://explorer.deeponion.org\",\"https://deeponion.org/community/threads/deeponion-v-1-6-1-released-important-upgrade-mandatory-upgrade.33401/\",\"https://deeponion.org/community/threads/article-deeponion-hard-fork-faq.33079/\",\"https://deeponion.org/community/threads/article-deeponion-wallet-distribution.33972/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}blockencryptorpublished a new post: determining-the-best-input-size-for-staking2018/04/02 15:32:24
blockencryptorpublished a new post: determining-the-best-input-size-for-staking
2018/04/02 15:32:24
| parent author | |
| parent permlink | deeponion |
| author | blockencryptor |
| permlink | determining-the-best-input-size-for-staking |
| title | Determining the best input size for staking |
| body | @@ -3378,16 +3378,351 @@ enter%3E%0A%0A +I checked the results again and except of the small inputs, all wallets received similar rewards. It seems that the actual input doesn't have a high impact as long as their big enough. %0A%0A%3Ccenter%3E%0A!%5B%5D(https://steemitimages.com/DQmdJba5Zc1WVQTuT4bKZL4Nipce2hCffr8FbfjwYRPfpJh/image.png)%0AIntermediate Results 01.04.2018 17:27%E2%80%8B%0A%3C/center%3E%0A%0A %3Ccenter%3E |
| json metadata | {"tags":["deeponion","wallet","staking","rewards","inputs"],"image":["https://steemitimages.com/DQmatqCAsCdmbDeZ8G1e8rWnzLjM1yzMD394Lk3uyrFW2w4/image.png","https://steemitimages.com/DQmcet1r4hzNo4FQjgntXkuZZ9zUkrzhCvTDigApKeAYX7Z/image.png","https://steemitimages.com/DQmY1J4JZG1g3eCW8cBT5kkjDsN5J8EkT6gDucNXrWKmcGF/image.png","https://steemitimages.com/DQmZr3Gjwo91sTJ5gFVTmm4p9EoVkkVviff1JpuuXPTjEFQ/image.png","https://steemitimages.com/DQmPFir8E49G7x2XqUyBzLnybWHmWUhQtnsFmaGcBjU14eY/image.png","https://steemitimages.com/DQmSrdxuK18a9nMNeSVQa13URXZY7rJQoVx3LqqyTsoXNi7/image.png","https://steemitimages.com/DQmdJba5Zc1WVQTuT4bKZL4Nipce2hCffr8FbfjwYRPfpJh/image.png","https://steemitimages.com/DQmPXZp6x45STwHKacuQ6wBgsAYWzerHqkGg8UiWLPkTdTm/image.png","https://steemitimages.com/DQmb6i1zKxLgWAqh3zScNkYadYKzk3X6G7r3g7hgHuzZ4R3/image.png","https://steemitimages.com/DQmSYhp3y7KnTRRFWkfBGueaSC3tpD6Vnq1eQNSSidkH6D2/image.png"],"links":["https://deeponion.org/community/threads/tutorial-how-to-send-rpc-commands-to-your-deeponion-qt-wallet.24421","https://deeponion.org/community/threads/article-determining-the-best-input-size-for-staking.34189/","https://twitter.com/BlockEncryptor"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #21217815/Trx 4c6421e45cd3236dcdef5faf57ce922443f4a859 |
View Raw JSON Data
{
"trx_id": "4c6421e45cd3236dcdef5faf57ce922443f4a859",
"block": 21217815,
"trx_in_block": 46,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-02T15:32:24",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "deeponion",
"author": "blockencryptor",
"permlink": "determining-the-best-input-size-for-staking",
"title": "Determining the best input size for staking",
"body": "@@ -3378,16 +3378,351 @@\n enter%3E%0A%0A\n+I checked the results again and except of the small inputs, all wallets received similar rewards. It seems that the actual input doesn't have a high impact as long as their big enough. %0A%0A%3Ccenter%3E%0A!%5B%5D(https://steemitimages.com/DQmdJba5Zc1WVQTuT4bKZL4Nipce2hCffr8FbfjwYRPfpJh/image.png)%0AIntermediate Results 01.04.2018 17:27%E2%80%8B%0A%3C/center%3E%0A%0A\n %3Ccenter%3E\n",
"json_metadata": "{\"tags\":[\"deeponion\",\"wallet\",\"staking\",\"rewards\",\"inputs\"],\"image\":[\"https://steemitimages.com/DQmatqCAsCdmbDeZ8G1e8rWnzLjM1yzMD394Lk3uyrFW2w4/image.png\",\"https://steemitimages.com/DQmcet1r4hzNo4FQjgntXkuZZ9zUkrzhCvTDigApKeAYX7Z/image.png\",\"https://steemitimages.com/DQmY1J4JZG1g3eCW8cBT5kkjDsN5J8EkT6gDucNXrWKmcGF/image.png\",\"https://steemitimages.com/DQmZr3Gjwo91sTJ5gFVTmm4p9EoVkkVviff1JpuuXPTjEFQ/image.png\",\"https://steemitimages.com/DQmPFir8E49G7x2XqUyBzLnybWHmWUhQtnsFmaGcBjU14eY/image.png\",\"https://steemitimages.com/DQmSrdxuK18a9nMNeSVQa13URXZY7rJQoVx3LqqyTsoXNi7/image.png\",\"https://steemitimages.com/DQmdJba5Zc1WVQTuT4bKZL4Nipce2hCffr8FbfjwYRPfpJh/image.png\",\"https://steemitimages.com/DQmPXZp6x45STwHKacuQ6wBgsAYWzerHqkGg8UiWLPkTdTm/image.png\",\"https://steemitimages.com/DQmb6i1zKxLgWAqh3zScNkYadYKzk3X6G7r3g7hgHuzZ4R3/image.png\",\"https://steemitimages.com/DQmSYhp3y7KnTRRFWkfBGueaSC3tpD6Vnq1eQNSSidkH6D2/image.png\"],\"links\":[\"https://deeponion.org/community/threads/tutorial-how-to-send-rpc-commands-to-your-deeponion-qt-wallet.24421\",\"https://deeponion.org/community/threads/article-determining-the-best-input-size-for-staking.34189/\",\"https://twitter.com/BlockEncryptor\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}blockencryptorpublished a new post: determining-the-best-input-size-for-staking2018/04/01 05:34:48
blockencryptorpublished a new post: determining-the-best-input-size-for-staking
2018/04/01 05:34:48
| parent author | |
| parent permlink | deeponion |
| author | blockencryptor |
| permlink | determining-the-best-input-size-for-staking |
| title | Determining the best input size for staking |
| body | @@ -4289,16 +4289,152 @@ ll get. +From the above results the best input amount was also the highest with 500 $onions and it seems that the rewards could be even higher.%0A%0A One impo |
| json metadata | {"tags":["deeponion","wallet","staking","rewards","inputs"],"image":["https://steemitimages.com/DQmatqCAsCdmbDeZ8G1e8rWnzLjM1yzMD394Lk3uyrFW2w4/image.png","https://steemitimages.com/DQmcet1r4hzNo4FQjgntXkuZZ9zUkrzhCvTDigApKeAYX7Z/image.png","https://steemitimages.com/DQmY1J4JZG1g3eCW8cBT5kkjDsN5J8EkT6gDucNXrWKmcGF/image.png","https://steemitimages.com/DQmZr3Gjwo91sTJ5gFVTmm4p9EoVkkVviff1JpuuXPTjEFQ/image.png","https://steemitimages.com/DQmPFir8E49G7x2XqUyBzLnybWHmWUhQtnsFmaGcBjU14eY/image.png","https://steemitimages.com/DQmSrdxuK18a9nMNeSVQa13URXZY7rJQoVx3LqqyTsoXNi7/image.png","https://steemitimages.com/DQmPXZp6x45STwHKacuQ6wBgsAYWzerHqkGg8UiWLPkTdTm/image.png","https://steemitimages.com/DQmb6i1zKxLgWAqh3zScNkYadYKzk3X6G7r3g7hgHuzZ4R3/image.png","https://steemitimages.com/DQmSYhp3y7KnTRRFWkfBGueaSC3tpD6Vnq1eQNSSidkH6D2/image.png"],"links":["https://deeponion.org/community/threads/tutorial-how-to-send-rpc-commands-to-your-deeponion-qt-wallet.24421","https://deeponion.org/community/threads/article-determining-the-best-input-size-for-staking.34189/","https://twitter.com/BlockEncryptor"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #21177071/Trx 73cbd61f040205c5dde6cea0a74a0d1e35e08ac3 |
View Raw JSON Data
{
"trx_id": "73cbd61f040205c5dde6cea0a74a0d1e35e08ac3",
"block": 21177071,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-01T05:34:48",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "deeponion",
"author": "blockencryptor",
"permlink": "determining-the-best-input-size-for-staking",
"title": "Determining the best input size for staking",
"body": "@@ -4289,16 +4289,152 @@\n ll get. \n+From the above results the best input amount was also the highest with 500 $onions and it seems that the rewards could be even higher.%0A%0A\n One impo\n",
"json_metadata": "{\"tags\":[\"deeponion\",\"wallet\",\"staking\",\"rewards\",\"inputs\"],\"image\":[\"https://steemitimages.com/DQmatqCAsCdmbDeZ8G1e8rWnzLjM1yzMD394Lk3uyrFW2w4/image.png\",\"https://steemitimages.com/DQmcet1r4hzNo4FQjgntXkuZZ9zUkrzhCvTDigApKeAYX7Z/image.png\",\"https://steemitimages.com/DQmY1J4JZG1g3eCW8cBT5kkjDsN5J8EkT6gDucNXrWKmcGF/image.png\",\"https://steemitimages.com/DQmZr3Gjwo91sTJ5gFVTmm4p9EoVkkVviff1JpuuXPTjEFQ/image.png\",\"https://steemitimages.com/DQmPFir8E49G7x2XqUyBzLnybWHmWUhQtnsFmaGcBjU14eY/image.png\",\"https://steemitimages.com/DQmSrdxuK18a9nMNeSVQa13URXZY7rJQoVx3LqqyTsoXNi7/image.png\",\"https://steemitimages.com/DQmPXZp6x45STwHKacuQ6wBgsAYWzerHqkGg8UiWLPkTdTm/image.png\",\"https://steemitimages.com/DQmb6i1zKxLgWAqh3zScNkYadYKzk3X6G7r3g7hgHuzZ4R3/image.png\",\"https://steemitimages.com/DQmSYhp3y7KnTRRFWkfBGueaSC3tpD6Vnq1eQNSSidkH6D2/image.png\"],\"links\":[\"https://deeponion.org/community/threads/tutorial-how-to-send-rpc-commands-to-your-deeponion-qt-wallet.24421\",\"https://deeponion.org/community/threads/article-determining-the-best-input-size-for-staking.34189/\",\"https://twitter.com/BlockEncryptor\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}blockencryptorpublished a new post: determining-the-best-input-size-for-staking2018/04/01 05:29:51
blockencryptorpublished a new post: determining-the-best-input-size-for-staking
2018/04/01 05:29:51
| parent author | |
| parent permlink | deeponion |
| author | blockencryptor |
| permlink | determining-the-best-input-size-for-staking |
| title | Determining the best input size for staking |
| body | @@ -3530,110 +3530,20 @@ r%3E%0A%0A -To summarize, currently it looks like the higher the input amounts are the more rewards you will get.%0A +### Findings %0AAft @@ -3996,16 +3996,507 @@ enter%3E%0A%0A +### Summary%0AIt should be kept in mind that there are not many people stake on the testnet and therefore the network weight is quite small to the mainnet. But basically the same results should apply for the mainnet%0A%0AIt looks like the higher the input amounts are the more rewards you will get. One important point to remember is the input halving after a successful stake. So, it could be an advantage to combine them from time to time (this will cause a reset of the coin age).%0A%0A### Lookout%0A I will u @@ -4551,24 +4551,25 @@ results. I + have also pl |
| json metadata | {"tags":["deeponion","wallet","staking","rewards","inputs"],"image":["https://steemitimages.com/DQmatqCAsCdmbDeZ8G1e8rWnzLjM1yzMD394Lk3uyrFW2w4/image.png","https://steemitimages.com/DQmcet1r4hzNo4FQjgntXkuZZ9zUkrzhCvTDigApKeAYX7Z/image.png","https://steemitimages.com/DQmY1J4JZG1g3eCW8cBT5kkjDsN5J8EkT6gDucNXrWKmcGF/image.png","https://steemitimages.com/DQmZr3Gjwo91sTJ5gFVTmm4p9EoVkkVviff1JpuuXPTjEFQ/image.png","https://steemitimages.com/DQmPFir8E49G7x2XqUyBzLnybWHmWUhQtnsFmaGcBjU14eY/image.png","https://steemitimages.com/DQmSrdxuK18a9nMNeSVQa13URXZY7rJQoVx3LqqyTsoXNi7/image.png","https://steemitimages.com/DQmPXZp6x45STwHKacuQ6wBgsAYWzerHqkGg8UiWLPkTdTm/image.png","https://steemitimages.com/DQmb6i1zKxLgWAqh3zScNkYadYKzk3X6G7r3g7hgHuzZ4R3/image.png","https://steemitimages.com/DQmSYhp3y7KnTRRFWkfBGueaSC3tpD6Vnq1eQNSSidkH6D2/image.png"],"links":["https://deeponion.org/community/threads/tutorial-how-to-send-rpc-commands-to-your-deeponion-qt-wallet.24421","https://deeponion.org/community/threads/article-determining-the-best-input-size-for-staking.34189/","https://twitter.com/BlockEncryptor"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #21176972/Trx 85762ed9d8c2d8b0c22ebd83945c0447d5e3cde7 |
View Raw JSON Data
{
"trx_id": "85762ed9d8c2d8b0c22ebd83945c0447d5e3cde7",
"block": 21176972,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-01T05:29:51",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "deeponion",
"author": "blockencryptor",
"permlink": "determining-the-best-input-size-for-staking",
"title": "Determining the best input size for staking",
"body": "@@ -3530,110 +3530,20 @@\n r%3E%0A%0A\n-To summarize, currently it looks like the higher the input amounts are the more rewards you will get.%0A\n+### Findings\n %0AAft\n@@ -3996,16 +3996,507 @@\n enter%3E%0A%0A\n+### Summary%0AIt should be kept in mind that there are not many people stake on the testnet and therefore the network weight is quite small to the mainnet. But basically the same results should apply for the mainnet%0A%0AIt looks like the higher the input amounts are the more rewards you will get. One important point to remember is the input halving after a successful stake. So, it could be an advantage to combine them from time to time (this will cause a reset of the coin age).%0A%0A### Lookout%0A\n I will u\n@@ -4551,24 +4551,25 @@\n results. I \n+ \n have also pl\n",
"json_metadata": "{\"tags\":[\"deeponion\",\"wallet\",\"staking\",\"rewards\",\"inputs\"],\"image\":[\"https://steemitimages.com/DQmatqCAsCdmbDeZ8G1e8rWnzLjM1yzMD394Lk3uyrFW2w4/image.png\",\"https://steemitimages.com/DQmcet1r4hzNo4FQjgntXkuZZ9zUkrzhCvTDigApKeAYX7Z/image.png\",\"https://steemitimages.com/DQmY1J4JZG1g3eCW8cBT5kkjDsN5J8EkT6gDucNXrWKmcGF/image.png\",\"https://steemitimages.com/DQmZr3Gjwo91sTJ5gFVTmm4p9EoVkkVviff1JpuuXPTjEFQ/image.png\",\"https://steemitimages.com/DQmPFir8E49G7x2XqUyBzLnybWHmWUhQtnsFmaGcBjU14eY/image.png\",\"https://steemitimages.com/DQmSrdxuK18a9nMNeSVQa13URXZY7rJQoVx3LqqyTsoXNi7/image.png\",\"https://steemitimages.com/DQmPXZp6x45STwHKacuQ6wBgsAYWzerHqkGg8UiWLPkTdTm/image.png\",\"https://steemitimages.com/DQmb6i1zKxLgWAqh3zScNkYadYKzk3X6G7r3g7hgHuzZ4R3/image.png\",\"https://steemitimages.com/DQmSYhp3y7KnTRRFWkfBGueaSC3tpD6Vnq1eQNSSidkH6D2/image.png\"],\"links\":[\"https://deeponion.org/community/threads/tutorial-how-to-send-rpc-commands-to-your-deeponion-qt-wallet.24421\",\"https://deeponion.org/community/threads/article-determining-the-best-input-size-for-staking.34189/\",\"https://twitter.com/BlockEncryptor\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}blockencryptorpublished a new post: determining-the-best-input-size-for-staking2018/04/01 05:16:33
blockencryptorpublished a new post: determining-the-best-input-size-for-staking
2018/04/01 05:16:33
| parent author | |
| parent permlink | deeponion |
| author | blockencryptor |
| permlink | determining-the-best-input-size-for-staking |
| title | Determining the best input size for staking |
| body | @@ -4453,8 +4453,217 @@ g.34189/ +%0A%0A---%0A%0AFollow me on twitter for the newest updates and giveaways.%0Ahttps://twitter.com/BlockEncryptor%0A%0A%3Ccenter%3E%0A!%5B%5D(https://steemitimages.com/DQmSYhp3y7KnTRRFWkfBGueaSC3tpD6Vnq1eQNSSidkH6D2/image.png)%0A%3C/center%3E |
| json metadata | {"tags":["deeponion","wallet","staking","rewards","inputs"],"image":["https://steemitimages.com/DQmatqCAsCdmbDeZ8G1e8rWnzLjM1yzMD394Lk3uyrFW2w4/image.png","https://steemitimages.com/DQmcet1r4hzNo4FQjgntXkuZZ9zUkrzhCvTDigApKeAYX7Z/image.png","https://steemitimages.com/DQmY1J4JZG1g3eCW8cBT5kkjDsN5J8EkT6gDucNXrWKmcGF/image.png","https://steemitimages.com/DQmZr3Gjwo91sTJ5gFVTmm4p9EoVkkVviff1JpuuXPTjEFQ/image.png","https://steemitimages.com/DQmPFir8E49G7x2XqUyBzLnybWHmWUhQtnsFmaGcBjU14eY/image.png","https://steemitimages.com/DQmSrdxuK18a9nMNeSVQa13URXZY7rJQoVx3LqqyTsoXNi7/image.png","https://steemitimages.com/DQmPXZp6x45STwHKacuQ6wBgsAYWzerHqkGg8UiWLPkTdTm/image.png","https://steemitimages.com/DQmb6i1zKxLgWAqh3zScNkYadYKzk3X6G7r3g7hgHuzZ4R3/image.png","https://steemitimages.com/DQmSYhp3y7KnTRRFWkfBGueaSC3tpD6Vnq1eQNSSidkH6D2/image.png"],"links":["https://deeponion.org/community/threads/tutorial-how-to-send-rpc-commands-to-your-deeponion-qt-wallet.24421","https://deeponion.org/community/threads/article-determining-the-best-input-size-for-staking.34189/","https://twitter.com/BlockEncryptor"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #21176706/Trx 2bb0a396447c469797807f7f9d867e51d2739bc6 |
View Raw JSON Data
{
"trx_id": "2bb0a396447c469797807f7f9d867e51d2739bc6",
"block": 21176706,
"trx_in_block": 37,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-01T05:16:33",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "deeponion",
"author": "blockencryptor",
"permlink": "determining-the-best-input-size-for-staking",
"title": "Determining the best input size for staking",
"body": "@@ -4453,8 +4453,217 @@\n g.34189/\n+%0A%0A---%0A%0AFollow me on twitter for the newest updates and giveaways.%0Ahttps://twitter.com/BlockEncryptor%0A%0A%3Ccenter%3E%0A!%5B%5D(https://steemitimages.com/DQmSYhp3y7KnTRRFWkfBGueaSC3tpD6Vnq1eQNSSidkH6D2/image.png)%0A%3C/center%3E\n",
"json_metadata": "{\"tags\":[\"deeponion\",\"wallet\",\"staking\",\"rewards\",\"inputs\"],\"image\":[\"https://steemitimages.com/DQmatqCAsCdmbDeZ8G1e8rWnzLjM1yzMD394Lk3uyrFW2w4/image.png\",\"https://steemitimages.com/DQmcet1r4hzNo4FQjgntXkuZZ9zUkrzhCvTDigApKeAYX7Z/image.png\",\"https://steemitimages.com/DQmY1J4JZG1g3eCW8cBT5kkjDsN5J8EkT6gDucNXrWKmcGF/image.png\",\"https://steemitimages.com/DQmZr3Gjwo91sTJ5gFVTmm4p9EoVkkVviff1JpuuXPTjEFQ/image.png\",\"https://steemitimages.com/DQmPFir8E49G7x2XqUyBzLnybWHmWUhQtnsFmaGcBjU14eY/image.png\",\"https://steemitimages.com/DQmSrdxuK18a9nMNeSVQa13URXZY7rJQoVx3LqqyTsoXNi7/image.png\",\"https://steemitimages.com/DQmPXZp6x45STwHKacuQ6wBgsAYWzerHqkGg8UiWLPkTdTm/image.png\",\"https://steemitimages.com/DQmb6i1zKxLgWAqh3zScNkYadYKzk3X6G7r3g7hgHuzZ4R3/image.png\",\"https://steemitimages.com/DQmSYhp3y7KnTRRFWkfBGueaSC3tpD6Vnq1eQNSSidkH6D2/image.png\"],\"links\":[\"https://deeponion.org/community/threads/tutorial-how-to-send-rpc-commands-to-your-deeponion-qt-wallet.24421\",\"https://deeponion.org/community/threads/article-determining-the-best-input-size-for-staking.34189/\",\"https://twitter.com/BlockEncryptor\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}thetroublenotesupvoted (3.00%) @blockencryptor / determining-the-best-input-size-for-staking2018/04/01 05:16:03
thetroublenotesupvoted (3.00%) @blockencryptor / determining-the-best-input-size-for-staking
2018/04/01 05:16:03
| voter | thetroublenotes |
| author | blockencryptor |
| permlink | determining-the-best-input-size-for-staking |
| weight | 300 (3.00%) |
| Transaction Info | Block #21176696/Trx e748aa8d68fd8bdf771bfcdbc35f4d7d21611fec |
View Raw JSON Data
{
"trx_id": "e748aa8d68fd8bdf771bfcdbc35f4d7d21611fec",
"block": 21176696,
"trx_in_block": 12,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-01T05:16:03",
"op": [
"vote",
{
"voter": "thetroublenotes",
"author": "blockencryptor",
"permlink": "determining-the-best-input-size-for-staking",
"weight": 300
}
]
}blockencryptorpublished a new post: determining-the-best-input-size-for-staking2018/04/01 05:15:09
blockencryptorpublished a new post: determining-the-best-input-size-for-staking
2018/04/01 05:15:09
| parent author | |
| parent permlink | deeponion |
| author | blockencryptor |
| permlink | determining-the-best-input-size-for-staking |
| title | Determining the best input size for staking |
| body | @@ -2988,16 +2988,394 @@ Results + 31.03.2018 19:50%E2%80%8B%0A%3C/center%3E%0A%0ABelow are the results after about 35 hours. The first and last place didn't change, but the other wallets with higher inputs catching up. I assume this is caused through the splitting of the 500 $onions blocks.%0A%0A%3Ccenter%3E%0A!%5B%5D(https://steemitimages.com/DQmSrdxuK18a9nMNeSVQa13URXZY7rJQoVx3LqqyTsoXNi7/image.png)%0AIntermediate Results 01.04.2018 07:00%E2%80%8B %0A%3C/cente @@ -4151,16 +4151,149 @@ results. + I have also planned to repeat this evaluation with higher inputs as it turned out that the higher the inputs the higher the rewards. %0A%0A---%0A%0AI |
| json metadata | {"tags":["deeponion","wallet","staking","rewards","inputs"],"image":["https://steemitimages.com/DQmatqCAsCdmbDeZ8G1e8rWnzLjM1yzMD394Lk3uyrFW2w4/image.png","https://steemitimages.com/DQmcet1r4hzNo4FQjgntXkuZZ9zUkrzhCvTDigApKeAYX7Z/image.png","https://steemitimages.com/DQmY1J4JZG1g3eCW8cBT5kkjDsN5J8EkT6gDucNXrWKmcGF/image.png","https://steemitimages.com/DQmZr3Gjwo91sTJ5gFVTmm4p9EoVkkVviff1JpuuXPTjEFQ/image.png","https://steemitimages.com/DQmPFir8E49G7x2XqUyBzLnybWHmWUhQtnsFmaGcBjU14eY/image.png","https://steemitimages.com/DQmSrdxuK18a9nMNeSVQa13URXZY7rJQoVx3LqqyTsoXNi7/image.png","https://steemitimages.com/DQmPXZp6x45STwHKacuQ6wBgsAYWzerHqkGg8UiWLPkTdTm/image.png","https://steemitimages.com/DQmb6i1zKxLgWAqh3zScNkYadYKzk3X6G7r3g7hgHuzZ4R3/image.png"],"links":["https://deeponion.org/community/threads/tutorial-how-to-send-rpc-commands-to-your-deeponion-qt-wallet.24421","https://deeponion.org/community/threads/article-determining-the-best-input-size-for-staking.34189/"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #21176678/Trx 51d9863c76d0721b02548e96ab9a8b3e49cf0801 |
View Raw JSON Data
{
"trx_id": "51d9863c76d0721b02548e96ab9a8b3e49cf0801",
"block": 21176678,
"trx_in_block": 21,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-01T05:15:09",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "deeponion",
"author": "blockencryptor",
"permlink": "determining-the-best-input-size-for-staking",
"title": "Determining the best input size for staking",
"body": "@@ -2988,16 +2988,394 @@\n Results\n+ 31.03.2018 19:50%E2%80%8B%0A%3C/center%3E%0A%0ABelow are the results after about 35 hours. The first and last place didn't change, but the other wallets with higher inputs catching up. I assume this is caused through the splitting of the 500 $onions blocks.%0A%0A%3Ccenter%3E%0A!%5B%5D(https://steemitimages.com/DQmSrdxuK18a9nMNeSVQa13URXZY7rJQoVx3LqqyTsoXNi7/image.png)%0AIntermediate Results 01.04.2018 07:00%E2%80%8B\n %0A%3C/cente\n@@ -4151,16 +4151,149 @@\n results.\n+ I have also planned to repeat this evaluation with higher inputs as it turned out that the higher the inputs the higher the rewards.\n %0A%0A---%0A%0AI\n",
"json_metadata": "{\"tags\":[\"deeponion\",\"wallet\",\"staking\",\"rewards\",\"inputs\"],\"image\":[\"https://steemitimages.com/DQmatqCAsCdmbDeZ8G1e8rWnzLjM1yzMD394Lk3uyrFW2w4/image.png\",\"https://steemitimages.com/DQmcet1r4hzNo4FQjgntXkuZZ9zUkrzhCvTDigApKeAYX7Z/image.png\",\"https://steemitimages.com/DQmY1J4JZG1g3eCW8cBT5kkjDsN5J8EkT6gDucNXrWKmcGF/image.png\",\"https://steemitimages.com/DQmZr3Gjwo91sTJ5gFVTmm4p9EoVkkVviff1JpuuXPTjEFQ/image.png\",\"https://steemitimages.com/DQmPFir8E49G7x2XqUyBzLnybWHmWUhQtnsFmaGcBjU14eY/image.png\",\"https://steemitimages.com/DQmSrdxuK18a9nMNeSVQa13URXZY7rJQoVx3LqqyTsoXNi7/image.png\",\"https://steemitimages.com/DQmPXZp6x45STwHKacuQ6wBgsAYWzerHqkGg8UiWLPkTdTm/image.png\",\"https://steemitimages.com/DQmb6i1zKxLgWAqh3zScNkYadYKzk3X6G7r3g7hgHuzZ4R3/image.png\"],\"links\":[\"https://deeponion.org/community/threads/tutorial-how-to-send-rpc-commands-to-your-deeponion-qt-wallet.24421\",\"https://deeponion.org/community/threads/article-determining-the-best-input-size-for-staking.34189/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}blockencryptorpublished a new post: determining-the-best-input-size-for-staking2018/03/31 14:35:33
blockencryptorpublished a new post: determining-the-best-input-size-for-staking
2018/03/31 14:35:33
| parent author | |
| parent permlink | deeponion |
| author | blockencryptor |
| permlink | determining-the-best-input-size-for-staking |
| title | Determining the best input size for staking |
| body | @@ -3251,16 +3251,473 @@ l get.%0A%0A +After a while of staking it was interesting to note that after every stake the locked amount is splitted into two parts of the same size. So, the longer you don't touch your blocks the smaller are your available input transactions. The screenshot below shows the wallet with the initial 500 $onion input transactions.%0A%0A%3Ccenter%3E%0A!%5B%5D(https://steemitimages.com/DQmb6i1zKxLgWAqh3zScNkYadYKzk3X6G7r3g7hgHuzZ4R3/image.png)%0ASplitted Block after Staking%0A%3C/center%3E%0A%0A I will u |
| json metadata | {"tags":["deeponion","wallet","staking","rewards","inputs"],"image":["https://steemitimages.com/DQmatqCAsCdmbDeZ8G1e8rWnzLjM1yzMD394Lk3uyrFW2w4/image.png","https://steemitimages.com/DQmcet1r4hzNo4FQjgntXkuZZ9zUkrzhCvTDigApKeAYX7Z/image.png","https://steemitimages.com/DQmY1J4JZG1g3eCW8cBT5kkjDsN5J8EkT6gDucNXrWKmcGF/image.png","https://steemitimages.com/DQmZr3Gjwo91sTJ5gFVTmm4p9EoVkkVviff1JpuuXPTjEFQ/image.png","https://steemitimages.com/DQmPFir8E49G7x2XqUyBzLnybWHmWUhQtnsFmaGcBjU14eY/image.png","https://steemitimages.com/DQmPXZp6x45STwHKacuQ6wBgsAYWzerHqkGg8UiWLPkTdTm/image.png","https://steemitimages.com/DQmb6i1zKxLgWAqh3zScNkYadYKzk3X6G7r3g7hgHuzZ4R3/image.png"],"links":["https://deeponion.org/community/threads/tutorial-how-to-send-rpc-commands-to-your-deeponion-qt-wallet.24421","https://deeponion.org/community/threads/article-determining-the-best-input-size-for-staking.34189/"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #21159090/Trx aae3268dd75ea22111437219ce2ec040fa5739cb |
View Raw JSON Data
{
"trx_id": "aae3268dd75ea22111437219ce2ec040fa5739cb",
"block": 21159090,
"trx_in_block": 69,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-31T14:35:33",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "deeponion",
"author": "blockencryptor",
"permlink": "determining-the-best-input-size-for-staking",
"title": "Determining the best input size for staking",
"body": "@@ -3251,16 +3251,473 @@\n l get.%0A%0A\n+After a while of staking it was interesting to note that after every stake the locked amount is splitted into two parts of the same size. So, the longer you don't touch your blocks the smaller are your available input transactions. The screenshot below shows the wallet with the initial 500 $onion input transactions.%0A%0A%3Ccenter%3E%0A!%5B%5D(https://steemitimages.com/DQmb6i1zKxLgWAqh3zScNkYadYKzk3X6G7r3g7hgHuzZ4R3/image.png)%0ASplitted Block after Staking%0A%3C/center%3E%0A%0A\n I will u\n",
"json_metadata": "{\"tags\":[\"deeponion\",\"wallet\",\"staking\",\"rewards\",\"inputs\"],\"image\":[\"https://steemitimages.com/DQmatqCAsCdmbDeZ8G1e8rWnzLjM1yzMD394Lk3uyrFW2w4/image.png\",\"https://steemitimages.com/DQmcet1r4hzNo4FQjgntXkuZZ9zUkrzhCvTDigApKeAYX7Z/image.png\",\"https://steemitimages.com/DQmY1J4JZG1g3eCW8cBT5kkjDsN5J8EkT6gDucNXrWKmcGF/image.png\",\"https://steemitimages.com/DQmZr3Gjwo91sTJ5gFVTmm4p9EoVkkVviff1JpuuXPTjEFQ/image.png\",\"https://steemitimages.com/DQmPFir8E49G7x2XqUyBzLnybWHmWUhQtnsFmaGcBjU14eY/image.png\",\"https://steemitimages.com/DQmPXZp6x45STwHKacuQ6wBgsAYWzerHqkGg8UiWLPkTdTm/image.png\",\"https://steemitimages.com/DQmb6i1zKxLgWAqh3zScNkYadYKzk3X6G7r3g7hgHuzZ4R3/image.png\"],\"links\":[\"https://deeponion.org/community/threads/tutorial-how-to-send-rpc-commands-to-your-deeponion-qt-wallet.24421\",\"https://deeponion.org/community/threads/article-determining-the-best-input-size-for-staking.34189/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}blockencryptorpublished a new post: determining-the-best-input-size-for-staking2018/03/31 14:09:24
blockencryptorpublished a new post: determining-the-best-input-size-for-staking
2018/03/31 14:09:24
| parent author | |
| parent permlink | deeponion |
| author | blockencryptor |
| permlink | determining-the-best-input-size-for-staking |
| title | Determining the best input size for staking |
| body | @@ -3308,16 +3308,185 @@ newest results. +%0A%0A---%0A%0AI also published this article on the DeepOnion community forum.%0Ahttps://deeponion.org/community/threads/article-determining-the-best-input-size-for-staking.34189/ |
| json metadata | {"tags":["deeponion","wallet","staking","rewards","inputs"],"image":["https://steemitimages.com/DQmatqCAsCdmbDeZ8G1e8rWnzLjM1yzMD394Lk3uyrFW2w4/image.png","https://steemitimages.com/DQmcet1r4hzNo4FQjgntXkuZZ9zUkrzhCvTDigApKeAYX7Z/image.png","https://steemitimages.com/DQmY1J4JZG1g3eCW8cBT5kkjDsN5J8EkT6gDucNXrWKmcGF/image.png","https://steemitimages.com/DQmZr3Gjwo91sTJ5gFVTmm4p9EoVkkVviff1JpuuXPTjEFQ/image.png","https://steemitimages.com/DQmPFir8E49G7x2XqUyBzLnybWHmWUhQtnsFmaGcBjU14eY/image.png","https://steemitimages.com/DQmPXZp6x45STwHKacuQ6wBgsAYWzerHqkGg8UiWLPkTdTm/image.png"],"links":["https://deeponion.org/community/threads/tutorial-how-to-send-rpc-commands-to-your-deeponion-qt-wallet.24421","https://deeponion.org/community/threads/article-determining-the-best-input-size-for-staking.34189/"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #21158568/Trx 555bd5b85693786eab9c9a3934b7c4622380bda9 |
View Raw JSON Data
{
"trx_id": "555bd5b85693786eab9c9a3934b7c4622380bda9",
"block": 21158568,
"trx_in_block": 33,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-31T14:09:24",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "deeponion",
"author": "blockencryptor",
"permlink": "determining-the-best-input-size-for-staking",
"title": "Determining the best input size for staking",
"body": "@@ -3308,16 +3308,185 @@\n newest results.\n+%0A%0A---%0A%0AI also published this article on the DeepOnion community forum.%0Ahttps://deeponion.org/community/threads/article-determining-the-best-input-size-for-staking.34189/\n",
"json_metadata": "{\"tags\":[\"deeponion\",\"wallet\",\"staking\",\"rewards\",\"inputs\"],\"image\":[\"https://steemitimages.com/DQmatqCAsCdmbDeZ8G1e8rWnzLjM1yzMD394Lk3uyrFW2w4/image.png\",\"https://steemitimages.com/DQmcet1r4hzNo4FQjgntXkuZZ9zUkrzhCvTDigApKeAYX7Z/image.png\",\"https://steemitimages.com/DQmY1J4JZG1g3eCW8cBT5kkjDsN5J8EkT6gDucNXrWKmcGF/image.png\",\"https://steemitimages.com/DQmZr3Gjwo91sTJ5gFVTmm4p9EoVkkVviff1JpuuXPTjEFQ/image.png\",\"https://steemitimages.com/DQmPFir8E49G7x2XqUyBzLnybWHmWUhQtnsFmaGcBjU14eY/image.png\",\"https://steemitimages.com/DQmPXZp6x45STwHKacuQ6wBgsAYWzerHqkGg8UiWLPkTdTm/image.png\"],\"links\":[\"https://deeponion.org/community/threads/tutorial-how-to-send-rpc-commands-to-your-deeponion-qt-wallet.24421\",\"https://deeponion.org/community/threads/article-determining-the-best-input-size-for-staking.34189/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}blockencryptorpublished a new post: determining-the-best-input-size-for-staking2018/03/31 14:08:00
blockencryptorpublished a new post: determining-the-best-input-size-for-staking
2018/03/31 14:08:00
| parent author | |
| parent permlink | deeponion |
| author | blockencryptor |
| permlink | determining-the-best-input-size-for-staking |
| title | Determining the best input size for staking |
| body | What is the best input size to maximize your staking rewards? This is an intensely discussed topic and there are many opinions about this. I have read a few threads about staking and how to optimize your rewards, but couldn't find a satisfying answer. The most common guess is about 200 $onions per input, but I wanted to be certain about this and decided to evaluate it. ### Approach My approach was to set up multiple wallets and send 1000 $onions to each wallet. Every wallet will receive transactions with different amounts, but in total they will all start with 1000 $onions. <center>  Test Setup - Running Wallets </center> The wallet with the smallest input amounts will receive 200 transactions with five $onions each. The wallet on the other end will receive two transactions with 500 $onions and one wallet will receive random amounts between 0 and 150 $onions. <center>  Coin Distribution </center> Due to the lack of $onions I created this setup on the testnet. Another advantage there is the low network weight, so I will receive staking rewards shortly after I funded the wallets. ### Setup It was time for the setup. I needed six running wallets for this evaluation. Therefore I created six DeepOnion testnet folders under roaming (right) and six shortcuts with custom ports (left). This is required that they don't block each others connection. <center>  Wallet Setup </center> To save unnecessary work I created a script to start the wallets in the correct order. Just a few lines of PowerShell. ### Sending I needed to fund the wallets. This wasn't as easy as I thought. Especially for the smaller input transactions I had to automate this due to the high number of transactions. I connected the standard bitcoin-cli to my sender wallet as described in this article. https://deeponion.org/community/threads/tutorial-how-to-send-rpc-commands-to-your-deeponion-qt-wallet.24421 Then I sent all $onions to the dedicated wallets via scripts. It took about 20 minutes until all transactions were sent. <center>  Sample script to send $onions </center> ### Results The evaluation is still running, but I wanted to publish the intermediate results. I started the tests on 31.03.2018 19:50 and 20 hours later the wallet with the largest inputs leads. The wallet with the smallest inputs only received one reward and is far behind. Other than I thought, it looks like the wallet only uses exactly one input transaction and doesn't combine them. So the rewards for the smaller inputs are always low. <center>  Intermediate Results </center> <center>  Intermediate Result - Overview Wallets </center> To summarize, currently it looks like the higher the input amounts are the more rewards you will get. I will update this article in a few days with the newest results. |
| json metadata | {"tags":["deeponion","wallet","staking","rewards","inputs"],"image":["https://steemitimages.com/DQmatqCAsCdmbDeZ8G1e8rWnzLjM1yzMD394Lk3uyrFW2w4/image.png","https://steemitimages.com/DQmcet1r4hzNo4FQjgntXkuZZ9zUkrzhCvTDigApKeAYX7Z/image.png","https://steemitimages.com/DQmY1J4JZG1g3eCW8cBT5kkjDsN5J8EkT6gDucNXrWKmcGF/image.png","https://steemitimages.com/DQmZr3Gjwo91sTJ5gFVTmm4p9EoVkkVviff1JpuuXPTjEFQ/image.png","https://steemitimages.com/DQmPFir8E49G7x2XqUyBzLnybWHmWUhQtnsFmaGcBjU14eY/image.png","https://steemitimages.com/DQmPXZp6x45STwHKacuQ6wBgsAYWzerHqkGg8UiWLPkTdTm/image.png"],"links":["https://deeponion.org/community/threads/tutorial-how-to-send-rpc-commands-to-your-deeponion-qt-wallet.24421"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #21158540/Trx 4713a6cb5cd95832a085cb73d4a0f335b99403b9 |
View Raw JSON Data
{
"trx_id": "4713a6cb5cd95832a085cb73d4a0f335b99403b9",
"block": 21158540,
"trx_in_block": 9,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-31T14:08:00",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "deeponion",
"author": "blockencryptor",
"permlink": "determining-the-best-input-size-for-staking",
"title": "Determining the best input size for staking",
"body": "What is the best input size to maximize your staking rewards? This is an intensely discussed topic and there are many opinions about this. I have read a few threads about staking and how to optimize your rewards, but couldn't find a satisfying answer. The most common guess is about 200 $onions per input, but I wanted to be certain about this and decided to evaluate it.\n\n### Approach\nMy approach was to set up multiple wallets and send 1000 $onions to each wallet. Every wallet will receive transactions with different amounts, but in total they will all start with 1000 $onions.\n\n<center>\n\nTest Setup - Running Wallets\n</center>\n\nThe wallet with the smallest input amounts will receive 200 transactions with five $onions each. The wallet on the other end will receive two transactions with 500 $onions and one wallet will receive random amounts between 0 and 150 $onions.\n\n<center>\n\nCoin Distribution\n</center>\n\nDue to the lack of $onions I created this setup on the testnet. Another advantage there is the low network weight, so I will receive staking rewards shortly after I funded the wallets.\n\n### Setup\nIt was time for the setup. I needed six running wallets for this evaluation. Therefore I created six DeepOnion testnet folders under roaming (right) and six shortcuts with custom ports (left). This is required that they don't block each others connection.\n\n<center>\n\nWallet Setup\n</center>\n\nTo save unnecessary work I created a script to start the wallets in the correct order. Just a few lines of PowerShell.\n\n### Sending\nI needed to fund the wallets. This wasn't as easy as I thought. Especially for the smaller input transactions I had to automate this due to the high number of transactions. \n\nI connected the standard bitcoin-cli to my sender wallet as described in this article. \nhttps://deeponion.org/community/threads/tutorial-how-to-send-rpc-commands-to-your-deeponion-qt-wallet.24421\n\nThen I sent all $onions to the dedicated wallets via scripts. It took about 20 minutes until all transactions were sent.\n\n<center>\n\nSample script to send $onions\n</center>\n\n### Results\nThe evaluation is still running, but I wanted to publish the intermediate results. \n\nI started the tests on 31.03.2018 19:50 and 20 hours later the wallet with the largest inputs leads. The wallet with the smallest inputs only received one reward and is far behind. Other than I thought, it looks like the wallet only uses exactly one input transaction and doesn't combine them. So the rewards for the smaller inputs are always low.\n\n<center>\n\nIntermediate Results\n</center>\n\n<center>\n\nIntermediate Result - Overview Wallets\n</center>\n\nTo summarize, currently it looks like the higher the input amounts are the more rewards you will get.\n\nI will update this article in a few days with the newest results.",
"json_metadata": "{\"tags\":[\"deeponion\",\"wallet\",\"staking\",\"rewards\",\"inputs\"],\"image\":[\"https://steemitimages.com/DQmatqCAsCdmbDeZ8G1e8rWnzLjM1yzMD394Lk3uyrFW2w4/image.png\",\"https://steemitimages.com/DQmcet1r4hzNo4FQjgntXkuZZ9zUkrzhCvTDigApKeAYX7Z/image.png\",\"https://steemitimages.com/DQmY1J4JZG1g3eCW8cBT5kkjDsN5J8EkT6gDucNXrWKmcGF/image.png\",\"https://steemitimages.com/DQmZr3Gjwo91sTJ5gFVTmm4p9EoVkkVviff1JpuuXPTjEFQ/image.png\",\"https://steemitimages.com/DQmPFir8E49G7x2XqUyBzLnybWHmWUhQtnsFmaGcBjU14eY/image.png\",\"https://steemitimages.com/DQmPXZp6x45STwHKacuQ6wBgsAYWzerHqkGg8UiWLPkTdTm/image.png\"],\"links\":[\"https://deeponion.org/community/threads/tutorial-how-to-send-rpc-commands-to-your-deeponion-qt-wallet.24421\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}dragononcryptoupvoted (100.00%) @blockencryptor / deeponion-qt-basic-technical-terms-reference-material2018/03/31 11:39:33
dragononcryptoupvoted (100.00%) @blockencryptor / deeponion-qt-basic-technical-terms-reference-material
2018/03/31 11:39:33
| voter | dragononcrypto |
| author | blockencryptor |
| permlink | deeponion-qt-basic-technical-terms-reference-material |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21155572/Trx 57879627bca882d949c1ef44bc408173b5f3cf1f |
View Raw JSON Data
{
"trx_id": "57879627bca882d949c1ef44bc408173b5f3cf1f",
"block": 21155572,
"trx_in_block": 20,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-31T11:39:33",
"op": [
"vote",
{
"voter": "dragononcrypto",
"author": "blockencryptor",
"permlink": "deeponion-qt-basic-technical-terms-reference-material",
"weight": 10000
}
]
}2018/03/31 11:38:57
2018/03/31 11:38:57
| parent author | blockencryptor |
| parent permlink | deeponion-wallet-distribution |
| author | dragononcrypto |
| permlink | re-blockencryptor-deeponion-wallet-distribution-20180331t113856397z |
| title | |
| body | Only just found your Steemit backup. Nice :D |
| json metadata | {"tags":["deeponion"],"app":"steemit/0.1"} |
| Transaction Info | Block #21155560/Trx 8b82e5d903d793d4306810c6427ff714681e0915 |
View Raw JSON Data
{
"trx_id": "8b82e5d903d793d4306810c6427ff714681e0915",
"block": 21155560,
"trx_in_block": 19,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-31T11:38:57",
"op": [
"comment",
{
"parent_author": "blockencryptor",
"parent_permlink": "deeponion-wallet-distribution",
"author": "dragononcrypto",
"permlink": "re-blockencryptor-deeponion-wallet-distribution-20180331t113856397z",
"title": "",
"body": "Only just found your Steemit backup. Nice :D",
"json_metadata": "{\"tags\":[\"deeponion\"],\"app\":\"steemit/0.1\"}"
}
]
}dragononcryptoupvoted (100.00%) @blockencryptor / deeponion-wallet-distribution2018/03/31 11:38:39
dragononcryptoupvoted (100.00%) @blockencryptor / deeponion-wallet-distribution
2018/03/31 11:38:39
| voter | dragononcrypto |
| author | blockencryptor |
| permlink | deeponion-wallet-distribution |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21155554/Trx f3baf39702e870312ceb0dd4ae19da0ce579cbb0 |
View Raw JSON Data
{
"trx_id": "f3baf39702e870312ceb0dd4ae19da0ce579cbb0",
"block": 21155554,
"trx_in_block": 22,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-31T11:38:39",
"op": [
"vote",
{
"voter": "dragononcrypto",
"author": "blockencryptor",
"permlink": "deeponion-wallet-distribution",
"weight": 10000
}
]
}blockencryptorpublished a new post: deeponion-wallet-distribution2018/03/31 10:16:57
blockencryptorpublished a new post: deeponion-wallet-distribution
2018/03/31 10:16:57
| parent author | |
| parent permlink | deeponion |
| author | blockencryptor |
| permlink | deeponion-wallet-distribution |
| title | DeepOnion Wallet Distribution |
| body | @@ -1085,16 +1085,169 @@ enter%3E%0A%0A +%3Ccenter%3E%0A!%5B%5D(https://steemitimages.com/DQmfKdooj9qH27aGfoWcZrJs5aFL66ddac6vi1ae999u5bR/image.png)%0ADeepOnion Wallet Distribution (31.03.2018)%E2%80%8B%0A%3C/center%3E%0A%0A The abov |
| json metadata | {"tags":["deeponion","wallet","distribution","upgrade","deepprotocol"],"image":["https://steemitimages.com/DQmaSPmcwqf184WjeBoJcUUEYQJ15wqHdTkaAp9REQSB8x5/image.png","https://steemitimages.com/DQmZxZMvAnZUPB4H3Nfj6pBV5E3jn4BfHNYJ1gx5gdThWNA/image.png","https://steemitimages.com/DQmfKdooj9qH27aGfoWcZrJs5aFL66ddac6vi1ae999u5bR/image.png"],"links":["http://onionexplorer.youngwebsolutions.com:3001/","http://explorer.deeponion.org","https://deeponion.org/community/threads/deeponion-v-1-6-1-released-important-upgrade-mandatory-upgrade.33401/","https://deeponion.org/community/threads/article-deeponion-hard-fork-faq.33079/","https://deeponion.org/community/threads/article-deeponion-wallet-distribution.33972/"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #21153921/Trx 7f9e866cbd2882b74b660e96006279d8aec42fee |
View Raw JSON Data
{
"trx_id": "7f9e866cbd2882b74b660e96006279d8aec42fee",
"block": 21153921,
"trx_in_block": 29,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-31T10:16:57",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "deeponion",
"author": "blockencryptor",
"permlink": "deeponion-wallet-distribution",
"title": "DeepOnion Wallet Distribution",
"body": "@@ -1085,16 +1085,169 @@\n enter%3E%0A%0A\n+%3Ccenter%3E%0A!%5B%5D(https://steemitimages.com/DQmfKdooj9qH27aGfoWcZrJs5aFL66ddac6vi1ae999u5bR/image.png)%0ADeepOnion Wallet Distribution (31.03.2018)%E2%80%8B%0A%3C/center%3E%0A%0A\n The abov\n",
"json_metadata": "{\"tags\":[\"deeponion\",\"wallet\",\"distribution\",\"upgrade\",\"deepprotocol\"],\"image\":[\"https://steemitimages.com/DQmaSPmcwqf184WjeBoJcUUEYQJ15wqHdTkaAp9REQSB8x5/image.png\",\"https://steemitimages.com/DQmZxZMvAnZUPB4H3Nfj6pBV5E3jn4BfHNYJ1gx5gdThWNA/image.png\",\"https://steemitimages.com/DQmfKdooj9qH27aGfoWcZrJs5aFL66ddac6vi1ae999u5bR/image.png\"],\"links\":[\"http://onionexplorer.youngwebsolutions.com:3001/\",\"http://explorer.deeponion.org\",\"https://deeponion.org/community/threads/deeponion-v-1-6-1-released-important-upgrade-mandatory-upgrade.33401/\",\"https://deeponion.org/community/threads/article-deeponion-hard-fork-faq.33079/\",\"https://deeponion.org/community/threads/article-deeponion-wallet-distribution.33972/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}steemdelegated 18.664 SP to @blockencryptor2018/03/30 19:06:42
steemdelegated 18.664 SP to @blockencryptor
2018/03/30 19:06:42
| delegator | steem |
| delegatee | blockencryptor |
| vesting shares | 30393.575669 VESTS |
| Transaction Info | Block #21135720/Trx c25b60cf4164d66956b843ed6b15b5fd3c4b19c5 |
View Raw JSON Data
{
"trx_id": "c25b60cf4164d66956b843ed6b15b5fd3c4b19c5",
"block": 21135720,
"trx_in_block": 59,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-30T19:06:42",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "blockencryptor",
"vesting_shares": "30393.575669 VESTS"
}
]
}blockencryptorpublished a new post: deeponion-wallet-distribution2018/03/30 05:23:33
blockencryptorpublished a new post: deeponion-wallet-distribution
2018/03/30 05:23:33
| parent author | |
| parent permlink | deeponion |
| author | blockencryptor |
| permlink | deeponion-wallet-distribution |
| title | DeepOnion Wallet Distribution |
| body | @@ -827,52 +827,204 @@ /DQm -PycEQdnAd31qdRBV597NpB94ncyeoBVr97jKy8B7NJiV +aSPmcwqf184WjeBoJcUUEYQJ15wqHdTkaAp9REQSB8x5/image.png)%0ADeepOnion Wallet Distribution (29.03.2018)%0A%3C/center%3E%0A%0A%3Ccenter%3E%0A!%5B%5D(https://steemitimages.com/DQmZxZMvAnZUPB4H3Nfj6pBV5E3jn4BfHNYJ1gx5gdThWNA /ima @@ -1054,34 +1054,34 @@ t Distribution ( -29 +30 .03.2018)%0A%3C/cent |
| json metadata | {"tags":["deeponion","wallet","distribution","upgrade","deepprotocol"],"image":["https://steemitimages.com/DQmaSPmcwqf184WjeBoJcUUEYQJ15wqHdTkaAp9REQSB8x5/image.png","https://steemitimages.com/DQmZxZMvAnZUPB4H3Nfj6pBV5E3jn4BfHNYJ1gx5gdThWNA/image.png"],"links":["http://onionexplorer.youngwebsolutions.com:3001/","http://explorer.deeponion.org","https://deeponion.org/community/threads/deeponion-v-1-6-1-released-important-upgrade-mandatory-upgrade.33401/","https://deeponion.org/community/threads/article-deeponion-hard-fork-faq.33079/","https://deeponion.org/community/threads/article-deeponion-wallet-distribution.33972/"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #21119261/Trx 69f51c6e76432e8d2eb386d42a78776b54d2ab7c |
View Raw JSON Data
{
"trx_id": "69f51c6e76432e8d2eb386d42a78776b54d2ab7c",
"block": 21119261,
"trx_in_block": 23,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-30T05:23:33",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "deeponion",
"author": "blockencryptor",
"permlink": "deeponion-wallet-distribution",
"title": "DeepOnion Wallet Distribution",
"body": "@@ -827,52 +827,204 @@\n /DQm\n-PycEQdnAd31qdRBV597NpB94ncyeoBVr97jKy8B7NJiV\n+aSPmcwqf184WjeBoJcUUEYQJ15wqHdTkaAp9REQSB8x5/image.png)%0ADeepOnion Wallet Distribution (29.03.2018)%0A%3C/center%3E%0A%0A%3Ccenter%3E%0A!%5B%5D(https://steemitimages.com/DQmZxZMvAnZUPB4H3Nfj6pBV5E3jn4BfHNYJ1gx5gdThWNA\n /ima\n@@ -1054,34 +1054,34 @@\n t Distribution (\n-29\n+30\n .03.2018)%0A%3C/cent\n",
"json_metadata": "{\"tags\":[\"deeponion\",\"wallet\",\"distribution\",\"upgrade\",\"deepprotocol\"],\"image\":[\"https://steemitimages.com/DQmaSPmcwqf184WjeBoJcUUEYQJ15wqHdTkaAp9REQSB8x5/image.png\",\"https://steemitimages.com/DQmZxZMvAnZUPB4H3Nfj6pBV5E3jn4BfHNYJ1gx5gdThWNA/image.png\"],\"links\":[\"http://onionexplorer.youngwebsolutions.com:3001/\",\"http://explorer.deeponion.org\",\"https://deeponion.org/community/threads/deeponion-v-1-6-1-released-important-upgrade-mandatory-upgrade.33401/\",\"https://deeponion.org/community/threads/article-deeponion-hard-fork-faq.33079/\",\"https://deeponion.org/community/threads/article-deeponion-wallet-distribution.33972/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}blockencryptorupdated their account properties2018/03/29 16:21:42
blockencryptorupdated their account properties
2018/03/29 16:21:42
| account | blockencryptor |
| memo key | STM5WYi3Ue8AUJDcfz4g4HQme2SdHy86w6DZTEniZk3KgnJGgcGbt |
| json metadata | {"profile":{"profile_image":"https://i.imgur.com/syrwB3l.png","cover_image":"https://i.imgur.com/MolvVbq.png"}} |
| Transaction Info | Block #21103628/Trx 814547f6635bb57e93b481a8978e3b59c07f2c35 |
View Raw JSON Data
{
"trx_id": "814547f6635bb57e93b481a8978e3b59c07f2c35",
"block": 21103628,
"trx_in_block": 14,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-29T16:21:42",
"op": [
"account_update",
{
"account": "blockencryptor",
"memo_key": "STM5WYi3Ue8AUJDcfz4g4HQme2SdHy86w6DZTEniZk3KgnJGgcGbt",
"json_metadata": "{\"profile\":{\"profile_image\":\"https://i.imgur.com/syrwB3l.png\",\"cover_image\":\"https://i.imgur.com/MolvVbq.png\"}}"
}
]
}blockencryptorupdated their account properties2018/03/29 16:19:51
blockencryptorupdated their account properties
2018/03/29 16:19:51
| account | blockencryptor |
| memo key | STM5WYi3Ue8AUJDcfz4g4HQme2SdHy86w6DZTEniZk3KgnJGgcGbt |
| json metadata | {"profile":{"profile_image":"https://i.imgur.com/Eourx03.png","cover_image":"https://i.imgur.com/MolvVbq.png"}} |
| Transaction Info | Block #21103591/Trx 8529a08bacce3e2236cc5ae8b09e99252811da55 |
View Raw JSON Data
{
"trx_id": "8529a08bacce3e2236cc5ae8b09e99252811da55",
"block": 21103591,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-29T16:19:51",
"op": [
"account_update",
{
"account": "blockencryptor",
"memo_key": "STM5WYi3Ue8AUJDcfz4g4HQme2SdHy86w6DZTEniZk3KgnJGgcGbt",
"json_metadata": "{\"profile\":{\"profile_image\":\"https://i.imgur.com/Eourx03.png\",\"cover_image\":\"https://i.imgur.com/MolvVbq.png\"}}"
}
]
}blockencryptorupdated their account properties2018/03/29 11:01:51
blockencryptorupdated their account properties
2018/03/29 11:01:51
| account | blockencryptor |
| memo key | STM5WYi3Ue8AUJDcfz4g4HQme2SdHy86w6DZTEniZk3KgnJGgcGbt |
| json metadata | {"profile":{"profile_image":"https://i.imgur.com/syrwB3l.png","cover_image":"https://i.imgur.com/MolvVbq.png"}} |
| Transaction Info | Block #21097235/Trx b22dd61926947b53639410ae611b6a49d9f47737 |
View Raw JSON Data
{
"trx_id": "b22dd61926947b53639410ae611b6a49d9f47737",
"block": 21097235,
"trx_in_block": 51,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-29T11:01:51",
"op": [
"account_update",
{
"account": "blockencryptor",
"memo_key": "STM5WYi3Ue8AUJDcfz4g4HQme2SdHy86w6DZTEniZk3KgnJGgcGbt",
"json_metadata": "{\"profile\":{\"profile_image\":\"https://i.imgur.com/syrwB3l.png\",\"cover_image\":\"https://i.imgur.com/MolvVbq.png\"}}"
}
]
}blockencryptorpublished a new post: deeponion-wallet-distribution2018/03/29 07:26:09
blockencryptorpublished a new post: deeponion-wallet-distribution
2018/03/29 07:26:09
| parent author | |
| parent permlink | deeponion |
| author | blockencryptor |
| permlink | deeponion-wallet-distribution |
| title | DeepOnion Wallet Distribution |
| body | @@ -1648,8 +1648,93 @@ y forum. +%0Ahttps://deeponion.org/community/threads/article-deeponion-wallet-distribution.33972/ |
| json metadata | {"tags":["deeponion","wallet","distribution","upgrade","deepprotocol"],"image":["https://steemitimages.com/DQmPycEQdnAd31qdRBV597NpB94ncyeoBVr97jKy8B7NJiV/image.png"],"links":["http://onionexplorer.youngwebsolutions.com:3001/","http://explorer.deeponion.org","https://deeponion.org/community/threads/deeponion-v-1-6-1-released-important-upgrade-mandatory-upgrade.33401/","https://deeponion.org/community/threads/article-deeponion-hard-fork-faq.33079/","https://deeponion.org/community/threads/article-deeponion-wallet-distribution.33972/"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #21092924/Trx 1b12619cde82581b853792a53539b641d5cce4d5 |
View Raw JSON Data
{
"trx_id": "1b12619cde82581b853792a53539b641d5cce4d5",
"block": 21092924,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-29T07:26:09",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "deeponion",
"author": "blockencryptor",
"permlink": "deeponion-wallet-distribution",
"title": "DeepOnion Wallet Distribution",
"body": "@@ -1648,8 +1648,93 @@\n y forum.\n+%0Ahttps://deeponion.org/community/threads/article-deeponion-wallet-distribution.33972/\n",
"json_metadata": "{\"tags\":[\"deeponion\",\"wallet\",\"distribution\",\"upgrade\",\"deepprotocol\"],\"image\":[\"https://steemitimages.com/DQmPycEQdnAd31qdRBV597NpB94ncyeoBVr97jKy8B7NJiV/image.png\"],\"links\":[\"http://onionexplorer.youngwebsolutions.com:3001/\",\"http://explorer.deeponion.org\",\"https://deeponion.org/community/threads/deeponion-v-1-6-1-released-important-upgrade-mandatory-upgrade.33401/\",\"https://deeponion.org/community/threads/article-deeponion-hard-fork-faq.33079/\",\"https://deeponion.org/community/threads/article-deeponion-wallet-distribution.33972/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}blockencryptorpublished a new post: deeponion-wallet-distribution2018/03/29 07:25:36
blockencryptorpublished a new post: deeponion-wallet-distribution
2018/03/29 07:25:36
| parent author | |
| parent permlink | deeponion |
| author | blockencryptor |
| permlink | deeponion-wallet-distribution |
| title | DeepOnion Wallet Distribution |
| body | The upcoming DeepOnion hard fork requires all user to upgrade their wallets. The newest version is v1.6.1 and at least v1.6.0 is necessary to stay on the main chain and send transactions over the network. This mandatory upgrade was a precondition for the new DeepProtocol, which introduces Stealth Adresses where the receiver can publish only one address and still stay anonymous. For that reason a regularly updated overview of the wallet distribution could be helpful to monitor the progress of the upgrade. The following charts show the distribution of the wallets that are connected to the two main explorers of DeepOnion. The nodes were fetched via the api. * Community Explorer: http://onionexplorer.youngwebsolutions.com:3001/ * Official Explorer: http://explorer.deeponion.org <center>  DeepOnion Wallet Distribution (29.03.2018) </center> The above chart shows that there are many wallets still running on the old version. It is necessary to upgrade the wallets before block 460 000 (approximate 02.04.2018) to prevent a possible chain split. Please update your old wallets. You can find all information required for the upgrade on the official announcement. https://deeponion.org/community/threads/deeponion-v-1-6-1-released-important-upgrade-mandatory-upgrade.33401/ If you don't know what a hard fork is or if you have further questions, you can find more details on this 'DeepOnion Hard Fork FAQ'. https://deeponion.org/community/threads/article-deeponion-hard-fork-faq.33079/ --- I also published this article on the DeepOnion Community forum. |
| json metadata | {"tags":["deeponion","wallet","distribution","upgrade","deepprotocol"],"image":["https://steemitimages.com/DQmPycEQdnAd31qdRBV597NpB94ncyeoBVr97jKy8B7NJiV/image.png"],"links":["http://onionexplorer.youngwebsolutions.com:3001/","http://explorer.deeponion.org","https://deeponion.org/community/threads/deeponion-v-1-6-1-released-important-upgrade-mandatory-upgrade.33401/","https://deeponion.org/community/threads/article-deeponion-hard-fork-faq.33079/"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #21092913/Trx 2ecc1fbb65c502dfe936d5bba22bcc1177149629 |
View Raw JSON Data
{
"trx_id": "2ecc1fbb65c502dfe936d5bba22bcc1177149629",
"block": 21092913,
"trx_in_block": 17,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-29T07:25:36",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "deeponion",
"author": "blockencryptor",
"permlink": "deeponion-wallet-distribution",
"title": "DeepOnion Wallet Distribution",
"body": "The upcoming DeepOnion hard fork requires all user to upgrade their wallets. The newest version is v1.6.1 and at least v1.6.0 is necessary to stay on the main chain and send transactions over the network. This mandatory upgrade was a precondition for the new DeepProtocol, which introduces Stealth Adresses where the receiver can publish only one address and still stay anonymous.\n\nFor that reason a regularly updated overview of the wallet distribution could be helpful to monitor the progress of the upgrade. The following charts show the distribution of the wallets that are connected to the two main explorers of DeepOnion. The nodes were fetched via the api.\n\n* Community Explorer: http://onionexplorer.youngwebsolutions.com:3001/\n* Official Explorer: http://explorer.deeponion.org\n\n<center>\n\nDeepOnion Wallet Distribution (29.03.2018)\n</center>\n\nThe above chart shows that there are many wallets still running on the old version. It is necessary to upgrade the wallets before block 460 000 (approximate 02.04.2018) to prevent a possible chain split. Please update your old wallets. You can find all information required for the upgrade on the official announcement.\nhttps://deeponion.org/community/threads/deeponion-v-1-6-1-released-important-upgrade-mandatory-upgrade.33401/\n\nIf you don't know what a hard fork is or if you have further questions, you can find more details on this 'DeepOnion Hard Fork FAQ'.\nhttps://deeponion.org/community/threads/article-deeponion-hard-fork-faq.33079/\n\n\n\n\n\n---\nI also published this article on the DeepOnion Community forum.",
"json_metadata": "{\"tags\":[\"deeponion\",\"wallet\",\"distribution\",\"upgrade\",\"deepprotocol\"],\"image\":[\"https://steemitimages.com/DQmPycEQdnAd31qdRBV597NpB94ncyeoBVr97jKy8B7NJiV/image.png\"],\"links\":[\"http://onionexplorer.youngwebsolutions.com:3001/\",\"http://explorer.deeponion.org\",\"https://deeponion.org/community/threads/deeponion-v-1-6-1-released-important-upgrade-mandatory-upgrade.33401/\",\"https://deeponion.org/community/threads/article-deeponion-hard-fork-faq.33079/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}2018/03/28 12:17:03
2018/03/28 12:17:03
| parent author | blockencryptor |
| parent permlink | deeponion-what-happens-to-your-usdonions-after-the-hard-fork |
| author | dragononcrypto |
| permlink | re-blockencryptor-deeponion-what-happens-to-your-usdonions-after-the-hard-fork-20180328t121503170z |
| title | |
| body | @@ -69,20 +69,26 @@ hobias%22 -over +related to loosing |
| json metadata | {"tags":["deeponion"],"image":["https://steemitimages.com/DQmWNPF74UYfq9PkLcjStfiZqFsusAgiw2hNyGwSv5ALHkn/deeponion-fork-1.6.1.jpg"],"links":["https://steemit.com/deeponion/@dragononcrypto/deeponion-hard-fork-infographic"],"app":"steemit/0.1"} |
| Transaction Info | Block #21069957/Trx 3de3e8dd11400c625b6ecfb70e28fa3a434de75b |
View Raw JSON Data
{
"trx_id": "3de3e8dd11400c625b6ecfb70e28fa3a434de75b",
"block": 21069957,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-28T12:17:03",
"op": [
"comment",
{
"parent_author": "blockencryptor",
"parent_permlink": "deeponion-what-happens-to-your-usdonions-after-the-hard-fork",
"author": "dragononcrypto",
"permlink": "re-blockencryptor-deeponion-what-happens-to-your-usdonions-after-the-hard-fork-20180328t121503170z",
"title": "",
"body": "@@ -69,20 +69,26 @@\n hobias%22 \n-over\n+related to\n loosing\n",
"json_metadata": "{\"tags\":[\"deeponion\"],\"image\":[\"https://steemitimages.com/DQmWNPF74UYfq9PkLcjStfiZqFsusAgiw2hNyGwSv5ALHkn/deeponion-fork-1.6.1.jpg\"],\"links\":[\"https://steemit.com/deeponion/@dragononcrypto/deeponion-hard-fork-infographic\"],\"app\":\"steemit/0.1\"}"
}
]
}2018/03/28 12:16:48
2018/03/28 12:16:48
| parent author | blockencryptor |
| parent permlink | deeponion-what-happens-to-your-usdonions-after-the-hard-fork |
| author | dragononcrypto |
| permlink | re-blockencryptor-deeponion-what-happens-to-your-usdonions-after-the-hard-fork-20180328t121503170z |
| title | |
| body | @@ -64,12 +64,14 @@ ork -fear +phobia s%22 o |
| json metadata | {"tags":["deeponion"],"image":["https://steemitimages.com/DQmWNPF74UYfq9PkLcjStfiZqFsusAgiw2hNyGwSv5ALHkn/deeponion-fork-1.6.1.jpg"],"links":["https://steemit.com/deeponion/@dragononcrypto/deeponion-hard-fork-infographic"],"app":"steemit/0.1"} |
| Transaction Info | Block #21069952/Trx 510991807946481a5d0f14f8abe0924f385fccfb |
View Raw JSON Data
{
"trx_id": "510991807946481a5d0f14f8abe0924f385fccfb",
"block": 21069952,
"trx_in_block": 46,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-28T12:16:48",
"op": [
"comment",
{
"parent_author": "blockencryptor",
"parent_permlink": "deeponion-what-happens-to-your-usdonions-after-the-hard-fork",
"author": "dragononcrypto",
"permlink": "re-blockencryptor-deeponion-what-happens-to-your-usdonions-after-the-hard-fork-20180328t121503170z",
"title": "",
"body": "@@ -64,12 +64,14 @@\n ork \n-fear\n+phobia\n s%22 o\n",
"json_metadata": "{\"tags\":[\"deeponion\"],\"image\":[\"https://steemitimages.com/DQmWNPF74UYfq9PkLcjStfiZqFsusAgiw2hNyGwSv5ALHkn/deeponion-fork-1.6.1.jpg\"],\"links\":[\"https://steemit.com/deeponion/@dragononcrypto/deeponion-hard-fork-infographic\"],\"app\":\"steemit/0.1\"}"
}
]
}2018/03/28 12:16:33
2018/03/28 12:16:33
| parent author | blockencryptor |
| parent permlink | deeponion-what-happens-to-your-usdonions-after-the-hard-fork |
| author | dragononcrypto |
| permlink | re-blockencryptor-deeponion-what-happens-to-your-usdonions-after-the-hard-fork-20180328t121503170z |
| title | |
| body | @@ -47,16 +47,24 @@ le over +common %22 fork fea @@ -65,16 +65,36 @@ rk fears +%22 over loosing funds . If peo |
| json metadata | {"tags":["deeponion"],"image":["https://steemitimages.com/DQmWNPF74UYfq9PkLcjStfiZqFsusAgiw2hNyGwSv5ALHkn/deeponion-fork-1.6.1.jpg"],"links":["https://steemit.com/deeponion/@dragononcrypto/deeponion-hard-fork-infographic"],"app":"steemit/0.1"} |
| Transaction Info | Block #21069947/Trx c2a95ee7d5eafb5ebb5e223a2f0eb325d964e859 |
View Raw JSON Data
{
"trx_id": "c2a95ee7d5eafb5ebb5e223a2f0eb325d964e859",
"block": 21069947,
"trx_in_block": 35,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-28T12:16:33",
"op": [
"comment",
{
"parent_author": "blockencryptor",
"parent_permlink": "deeponion-what-happens-to-your-usdonions-after-the-hard-fork",
"author": "dragononcrypto",
"permlink": "re-blockencryptor-deeponion-what-happens-to-your-usdonions-after-the-hard-fork-20180328t121503170z",
"title": "",
"body": "@@ -47,16 +47,24 @@\n le over \n+common %22\n fork fea\n@@ -65,16 +65,36 @@\n rk fears\n+%22 over loosing funds\n . If peo\n",
"json_metadata": "{\"tags\":[\"deeponion\"],\"image\":[\"https://steemitimages.com/DQmWNPF74UYfq9PkLcjStfiZqFsusAgiw2hNyGwSv5ALHkn/deeponion-fork-1.6.1.jpg\"],\"links\":[\"https://steemit.com/deeponion/@dragononcrypto/deeponion-hard-fork-infographic\"],\"app\":\"steemit/0.1\"}"
}
]
}2018/03/28 12:15:57
2018/03/28 12:15:57
| parent author | blockencryptor |
| parent permlink | deeponion-what-happens-to-your-usdonions-after-the-hard-fork |
| author | dragononcrypto |
| permlink | re-blockencryptor-deeponion-what-happens-to-your-usdonions-after-the-hard-fork-20180328t121503170z |
| title | |
| body | @@ -179,16 +179,8 @@ -)%0A%0A -%3Ccenter%3E %5B!%5Bd @@ -387,13 +387,4 @@ hic) -%3C/center%3E |
| json metadata | {"tags":["deeponion"],"image":["https://steemitimages.com/DQmWNPF74UYfq9PkLcjStfiZqFsusAgiw2hNyGwSv5ALHkn/deeponion-fork-1.6.1.jpg"],"links":["https://steemit.com/deeponion/@dragononcrypto/deeponion-hard-fork-infographic"],"app":"steemit/0.1"} |
| Transaction Info | Block #21069935/Trx fe7fe6c2ab1e264b6b710bc9b26409c6140b082e |
View Raw JSON Data
{
"trx_id": "fe7fe6c2ab1e264b6b710bc9b26409c6140b082e",
"block": 21069935,
"trx_in_block": 12,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-28T12:15:57",
"op": [
"comment",
{
"parent_author": "blockencryptor",
"parent_permlink": "deeponion-what-happens-to-your-usdonions-after-the-hard-fork",
"author": "dragononcrypto",
"permlink": "re-blockencryptor-deeponion-what-happens-to-your-usdonions-after-the-hard-fork-20180328t121503170z",
"title": "",
"body": "@@ -179,16 +179,8 @@\n -)%0A%0A\n-%3Ccenter%3E\n %5B!%5Bd\n@@ -387,13 +387,4 @@\n hic)\n-%3C/center%3E\n",
"json_metadata": "{\"tags\":[\"deeponion\"],\"image\":[\"https://steemitimages.com/DQmWNPF74UYfq9PkLcjStfiZqFsusAgiw2hNyGwSv5ALHkn/deeponion-fork-1.6.1.jpg\"],\"links\":[\"https://steemit.com/deeponion/@dragononcrypto/deeponion-hard-fork-infographic\"],\"app\":\"steemit/0.1\"}"
}
]
}2018/03/28 12:15:39
2018/03/28 12:15:39
| parent author | blockencryptor |
| parent permlink | deeponion-what-happens-to-your-usdonions-after-the-hard-fork |
| author | dragononcrypto |
| permlink | re-blockencryptor-deeponion-what-happens-to-your-usdonions-after-the-hard-fork-20180328t121503170z |
| title | |
| body | @@ -9,16 +9,67 @@ ticle, i +t's important to reassure people over fork fears. I f people @@ -174,31 +174,11 @@ ead -to calm the fork fears. +:-) %0A%0A%3Cc |
| json metadata | {"tags":["deeponion"],"image":["https://steemitimages.com/DQmWNPF74UYfq9PkLcjStfiZqFsusAgiw2hNyGwSv5ALHkn/deeponion-fork-1.6.1.jpg"],"links":["https://steemit.com/deeponion/@dragononcrypto/deeponion-hard-fork-infographic"],"app":"steemit/0.1"} |
| Transaction Info | Block #21069929/Trx bd7b4cb871969477bb466d4fa5c4e31a590d4699 |
View Raw JSON Data
{
"trx_id": "bd7b4cb871969477bb466d4fa5c4e31a590d4699",
"block": 21069929,
"trx_in_block": 15,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-28T12:15:39",
"op": [
"comment",
{
"parent_author": "blockencryptor",
"parent_permlink": "deeponion-what-happens-to-your-usdonions-after-the-hard-fork",
"author": "dragononcrypto",
"permlink": "re-blockencryptor-deeponion-what-happens-to-your-usdonions-after-the-hard-fork-20180328t121503170z",
"title": "",
"body": "@@ -9,16 +9,67 @@\n ticle, i\n+t's important to reassure people over fork fears. I\n f people\n@@ -174,31 +174,11 @@\n ead \n-to calm the fork fears.\n+:-)\n %0A%0A%3Cc\n",
"json_metadata": "{\"tags\":[\"deeponion\"],\"image\":[\"https://steemitimages.com/DQmWNPF74UYfq9PkLcjStfiZqFsusAgiw2hNyGwSv5ALHkn/deeponion-fork-1.6.1.jpg\"],\"links\":[\"https://steemit.com/deeponion/@dragononcrypto/deeponion-hard-fork-infographic\"],\"app\":\"steemit/0.1\"}"
}
]
}2018/03/28 12:15:06
2018/03/28 12:15:06
| parent author | blockencryptor |
| parent permlink | deeponion-what-happens-to-your-usdonions-after-the-hard-fork |
| author | dragononcrypto |
| permlink | re-blockencryptor-deeponion-what-happens-to-your-usdonions-after-the-hard-fork-20180328t121503170z |
| title | |
| body | Great article, if people for whatever reason don't want to (or are unable to) upgrade then can just take a chill pill instead to calm the fork fears. <center>[](https://steemit.com/deeponion/@dragononcrypto/deeponion-hard-fork-infographic)</center> |
| json metadata | {"tags":["deeponion"],"image":["https://steemitimages.com/DQmWNPF74UYfq9PkLcjStfiZqFsusAgiw2hNyGwSv5ALHkn/deeponion-fork-1.6.1.jpg"],"links":["https://steemit.com/deeponion/@dragononcrypto/deeponion-hard-fork-infographic"],"app":"steemit/0.1"} |
| Transaction Info | Block #21069918/Trx d32deab48bfc97f718c61d2971d1aec17396dd65 |
View Raw JSON Data
{
"trx_id": "d32deab48bfc97f718c61d2971d1aec17396dd65",
"block": 21069918,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-28T12:15:06",
"op": [
"comment",
{
"parent_author": "blockencryptor",
"parent_permlink": "deeponion-what-happens-to-your-usdonions-after-the-hard-fork",
"author": "dragononcrypto",
"permlink": "re-blockencryptor-deeponion-what-happens-to-your-usdonions-after-the-hard-fork-20180328t121503170z",
"title": "",
"body": "Great article, if people for whatever reason don't want to (or are unable to) upgrade then can just take a chill pill instead to calm the fork fears.\n\n<center>[](https://steemit.com/deeponion/@dragononcrypto/deeponion-hard-fork-infographic)</center>",
"json_metadata": "{\"tags\":[\"deeponion\"],\"image\":[\"https://steemitimages.com/DQmWNPF74UYfq9PkLcjStfiZqFsusAgiw2hNyGwSv5ALHkn/deeponion-fork-1.6.1.jpg\"],\"links\":[\"https://steemit.com/deeponion/@dragononcrypto/deeponion-hard-fork-infographic\"],\"app\":\"steemit/0.1\"}"
}
]
}2018/03/28 12:08:48
2018/03/28 12:08:48
| voter | dragononcrypto |
| author | blockencryptor |
| permlink | deeponion-what-happens-to-your-usdonions-after-the-hard-fork |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21069792/Trx 59c3124a02cee5a7de0309a0606a83eb07c4c625 |
View Raw JSON Data
{
"trx_id": "59c3124a02cee5a7de0309a0606a83eb07c4c625",
"block": 21069792,
"trx_in_block": 77,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-28T12:08:48",
"op": [
"vote",
{
"voter": "dragononcrypto",
"author": "blockencryptor",
"permlink": "deeponion-what-happens-to-your-usdonions-after-the-hard-fork",
"weight": 10000
}
]
}bramggupvoted (100.00%) @blockencryptor / deeponion-what-happens-to-your-usdonions-after-the-hard-fork2018/03/28 12:08:30
bramggupvoted (100.00%) @blockencryptor / deeponion-what-happens-to-your-usdonions-after-the-hard-fork
2018/03/28 12:08:30
| voter | bramgg |
| author | blockencryptor |
| permlink | deeponion-what-happens-to-your-usdonions-after-the-hard-fork |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21069786/Trx 8d401933f37763edef99ace3e7608a4dbd77497a |
View Raw JSON Data
{
"trx_id": "8d401933f37763edef99ace3e7608a4dbd77497a",
"block": 21069786,
"trx_in_block": 9,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-28T12:08:30",
"op": [
"vote",
{
"voter": "bramgg",
"author": "blockencryptor",
"permlink": "deeponion-what-happens-to-your-usdonions-after-the-hard-fork",
"weight": 10000
}
]
}blockencryptorpublished a new post: deeponion-what-happens-to-your-usdonions-after-the-hard-fork2018/03/28 12:04:03
blockencryptorpublished a new post: deeponion-what-happens-to-your-usdonions-after-the-hard-fork
2018/03/28 12:04:03
| parent author | |
| parent permlink | deeponion |
| author | blockencryptor |
| permlink | deeponion-what-happens-to-your-usdonions-after-the-hard-fork |
| title | DeepOnion: What happens to my $onions after the hard fork? |
| body | @@ -138,21 +138,20 @@ onions? -There +What is a ha @@ -1328,22 +1328,22 @@ Optimal -h +H ard -f +F ork with @@ -1346,17 +1346,17 @@ without -c +C hainspli @@ -1676,16 +1676,100 @@ value. +Furthermore the old chain will not be maintained and not be available after a while. %0A%0ADespit @@ -2190,16 +2190,16 @@ people.%0A - https:// @@ -2248,8 +2248,178 @@ elp.107/ +%0A%0A---%0A%0AI also published this article on the DeepOnion community forum%0Ahttps://deeponion.org/community/threads/article-what-happens-to-my-onions-after-the-hard-fork.33906/ |
| json metadata | {"tags":["deeponion","hardfork","chainsplit","wallet"],"image":["https://steemitimages.com/DQmZ3rNnkGVkqETCEHJZJiciWt26uP8F2QzEx4ENZ5z8dyw/image.png","https://steemitimages.com/DQmWJtvzkDcAnz5cE1WuBqFdAJiDVvs413pjxUiQgVrSMA1/image.png"],"links":["https://deeponion.org/community/threads/deeponion-v-1-6-1-released-important-upgrade-mandatory-upgrade.33401/","https://deeponion.org/community/forums/beginners-help.107/","https://deeponion.org/community/threads/article-what-happens-to-my-onions-after-the-hard-fork.33906/"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #21069697/Trx c90f9491bf94ce0bf7ad1ec8d96eb717ab66022c |
View Raw JSON Data
{
"trx_id": "c90f9491bf94ce0bf7ad1ec8d96eb717ab66022c",
"block": 21069697,
"trx_in_block": 23,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-28T12:04:03",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "deeponion",
"author": "blockencryptor",
"permlink": "deeponion-what-happens-to-your-usdonions-after-the-hard-fork",
"title": "DeepOnion: What happens to my $onions after the hard fork?",
"body": "@@ -138,21 +138,20 @@\n onions? \n-There\n+What\n is a ha\n@@ -1328,22 +1328,22 @@\n Optimal \n-h\n+H\n ard \n-f\n+F\n ork with\n@@ -1346,17 +1346,17 @@\n without \n-c\n+C\n hainspli\n@@ -1676,16 +1676,100 @@\n value. \n+Furthermore the old chain will not be maintained and not be available after a while.\n %0A%0ADespit\n@@ -2190,16 +2190,16 @@\n people.%0A\n-\n https://\n@@ -2248,8 +2248,178 @@\n elp.107/\n+%0A%0A---%0A%0AI also published this article on the DeepOnion community forum%0Ahttps://deeponion.org/community/threads/article-what-happens-to-my-onions-after-the-hard-fork.33906/\n",
"json_metadata": "{\"tags\":[\"deeponion\",\"hardfork\",\"chainsplit\",\"wallet\"],\"image\":[\"https://steemitimages.com/DQmZ3rNnkGVkqETCEHJZJiciWt26uP8F2QzEx4ENZ5z8dyw/image.png\",\"https://steemitimages.com/DQmWJtvzkDcAnz5cE1WuBqFdAJiDVvs413pjxUiQgVrSMA1/image.png\"],\"links\":[\"https://deeponion.org/community/threads/deeponion-v-1-6-1-released-important-upgrade-mandatory-upgrade.33401/\",\"https://deeponion.org/community/forums/beginners-help.107/\",\"https://deeponion.org/community/threads/article-what-happens-to-my-onions-after-the-hard-fork.33906/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}blockencryptorpublished a new post: deeponion-what-happens-to-your-usdonions-after-the-hard-fork2018/03/28 11:58:27
blockencryptorpublished a new post: deeponion-what-happens-to-your-usdonions-after-the-hard-fork
2018/03/28 11:58:27
| parent author | |
| parent permlink | deeponion |
| author | blockencryptor |
| permlink | deeponion-what-happens-to-your-usdonions-after-the-hard-fork |
| title | DeepOnion: What happens to your $onions after the hard fork? |
| body | There were many questions about the consequences of old wallets after the hard fork occurred. What happens to my wallet? Will I lose my $onions? There is a hard fork? This article aims to clear things up and calm people down. Especially not technically versed people are nervous about such changes although there is no reason for this. Of course the general principle of creating backups for your wallet also applies here. Back to the topic, what happens on a hard fork? The underlying code base changes and therefore the old wallets cannot process the blocks from the newer wallets, which could cause a chain split. <center>  Planned DeepOnion Hard Fork </center> In the above screenshot there are two chains. The above one where the blocks are generated from the old wallets and the newer one from the wallets (> v1.6.0) with the new consensus rules. This chain split happens when not all wallets are upgraded in time. It's an unpleasant situation an therefore everyone should try to upgrade before the feature are activated. On a perfect hard fork, there is no block 460 001 on the old chain, because everyone has upgraded in time. <center>  Optimal hard fork without chainsplit </center> ### What are the consequences for the user of not upgraded wallets? There are no real consequences for the user. The $onions are safe, even if they are sent on the wrong chain. Actually the user have the same amount of $onions on both chains, but the ones on the old chain aren't supposed to have any value. Despite the nonexistent risks for your funds, it is also recommended to create backups of your private keys. ### What's next? Please help to maintain the new chain and upgrade your wallet. https://deeponion.org/community/threads/deeponion-v-1-6-1-released-important-upgrade-mandatory-upgrade.33401/ If you have any problems, please ask in the DeepOnion community forum. There are many motivated, friendly and helpful people. https://deeponion.org/community/forums/beginners-help.107/ |
| json metadata | {"tags":["deeponion","hardfork","chainsplit"],"image":["https://steemitimages.com/DQmZ3rNnkGVkqETCEHJZJiciWt26uP8F2QzEx4ENZ5z8dyw/image.png","https://steemitimages.com/DQmWJtvzkDcAnz5cE1WuBqFdAJiDVvs413pjxUiQgVrSMA1/image.png"],"links":["https://deeponion.org/community/threads/deeponion-v-1-6-1-released-important-upgrade-mandatory-upgrade.33401/","https://deeponion.org/community/forums/beginners-help.107/"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #21069585/Trx 17a120f3ca0d5e394c978f5194996ef132e6d0bc |
View Raw JSON Data
{
"trx_id": "17a120f3ca0d5e394c978f5194996ef132e6d0bc",
"block": 21069585,
"trx_in_block": 48,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-28T11:58:27",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "deeponion",
"author": "blockencryptor",
"permlink": "deeponion-what-happens-to-your-usdonions-after-the-hard-fork",
"title": "DeepOnion: What happens to your $onions after the hard fork?",
"body": "There were many questions about the consequences of old wallets after the hard fork occurred. What happens to my wallet? Will I lose my $onions? There is a hard fork?\n\nThis article aims to clear things up and calm people down. Especially not technically versed people are nervous about such changes although there is no reason for this. Of course the general principle of creating backups for your wallet also applies here.\n\nBack to the topic, what happens on a hard fork? The underlying code base changes and therefore the old wallets cannot process the blocks from the newer wallets, which could cause a chain split.\n\n<center>\n\nPlanned DeepOnion Hard Fork\n</center>\n\nIn the above screenshot there are two chains. The above one where the blocks are generated from the old wallets and the newer one from the wallets (> v1.6.0) with the new consensus rules. This chain split happens when not all wallets are upgraded in time. It's an unpleasant situation an therefore everyone should try to upgrade before the feature are activated.\n\nOn a perfect hard fork, there is no block 460 001 on the old chain, because everyone has upgraded in time. \n\n<center>\n\nOptimal hard fork without chainsplit\n</center>\n\n### What are the consequences for the user of not upgraded wallets?\nThere are no real consequences for the user. The $onions are safe, even if they are sent on the wrong chain. Actually the user have the same amount of $onions on both chains, but the ones on the old chain aren't supposed to have any value. \n\nDespite the nonexistent risks for your funds, it is also recommended to create backups of your private keys.\n\n### What's next?\nPlease help to maintain the new chain and upgrade your wallet. \nhttps://deeponion.org/community/threads/deeponion-v-1-6-1-released-important-upgrade-mandatory-upgrade.33401/\n\nIf you have any problems, please ask in the DeepOnion community forum. There are many motivated, friendly and helpful people.\nhttps://deeponion.org/community/forums/beginners-help.107/",
"json_metadata": "{\"tags\":[\"deeponion\",\"hardfork\",\"chainsplit\"],\"image\":[\"https://steemitimages.com/DQmZ3rNnkGVkqETCEHJZJiciWt26uP8F2QzEx4ENZ5z8dyw/image.png\",\"https://steemitimages.com/DQmWJtvzkDcAnz5cE1WuBqFdAJiDVvs413pjxUiQgVrSMA1/image.png\"],\"links\":[\"https://deeponion.org/community/threads/deeponion-v-1-6-1-released-important-upgrade-mandatory-upgrade.33401/\",\"https://deeponion.org/community/forums/beginners-help.107/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}Manabar
Voting Power100.00%
Downvote Power100.00%
Resource Credits100.00%
Reputation Progress29.36%
{
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779055857
},
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779055857
},
"rc_account": {
"account": "blockencryptor",
"rc_manabar": {
"current_mana": "10164408779",
"last_update_time": 1779055857
},
"max_rc_creation_adjustment": {
"amount": "2020748973",
"precision": 6,
"nai": "@@000000037"
},
"max_rc": "10164408779"
}
}Account Metadata
| POSTING JSON METADATA | |
| profile | {"profile_image":"https://i.imgur.com/syrwB3l.png","cover_image":"https://i.imgur.com/MolvVbq.png"} |
| JSON METADATA | |
| profile | {"profile_image":"https://i.imgur.com/syrwB3l.png","cover_image":"https://i.imgur.com/MolvVbq.png"} |
{
"posting_json_metadata": {
"profile": {
"profile_image": "https://i.imgur.com/syrwB3l.png",
"cover_image": "https://i.imgur.com/MolvVbq.png"
}
},
"json_metadata": {
"profile": {
"profile_image": "https://i.imgur.com/syrwB3l.png",
"cover_image": "https://i.imgur.com/MolvVbq.png"
}
}
}Auth Keys
Owner
Single Signature
Public Keys
STM7snatHsfsZkvuRnjUCFwkiEpCEM9iwPGwF4K5r6fbPcof7pUPV1/1
Active
Single Signature
Public Keys
STM76s9aeXtQeSKYerABJ4uQXDzE3R6mV8gt42CTYAPyjr6saYNKD1/1
Posting
Single Signature
Public Keys
STM8DoKV1RzLjMCZmCEzaZFm6KSBsmGMFai9ko5V1DcCC4oucJpSu1/1
Memo
STM5WYi3Ue8AUJDcfz4g4HQme2SdHy86w6DZTEniZk3KgnJGgcGbt
{
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7snatHsfsZkvuRnjUCFwkiEpCEM9iwPGwF4K5r6fbPcof7pUPV",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM76s9aeXtQeSKYerABJ4uQXDzE3R6mV8gt42CTYAPyjr6saYNKD",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM8DoKV1RzLjMCZmCEzaZFm6KSBsmGMFai9ko5V1DcCC4oucJpSu",
1
]
]
},
"memo": "STM5WYi3Ue8AUJDcfz4g4HQme2SdHy86w6DZTEniZk3KgnJGgcGbt"
}Witness Votes
0 / 30
No active witness votes.
[]