VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS0.00%
Net Worth
0.062USD
STEEM
0.004STEEM
SBD
0.051SBD
Effective Power
5.001SP
├── Own SP
0.681SP
└── Incoming DelegationsDeleg
+4.320SP
Detailed Balance
| STEEM | ||
| balance | 0.000STEEM | STEEM |
| market_balance | 0.000STEEM | STEEM |
| savings_balance | 0.000STEEM | STEEM |
| reward_steem_balance | 0.004STEEM | STEEM |
| STEEM POWER | ||
| Own SP | 0.681SP | SP |
| Delegated Out | 0.000SP | SP |
| Delegation In | 4.320SP | SP |
| Effective Power | 5.001SP | SP |
| Reward SP (pending) | 0.008SP | SP |
| SBD | ||
| sbd_balance | 0.045SBD | SBD |
| sbd_conversions | 0.000SBD | SBD |
| sbd_market_balance | 0.000SBD | SBD |
| savings_sbd_balance | 0.000SBD | SBD |
| reward_sbd_balance | 0.006SBD | SBD |
{
"balance": "0.000 STEEM",
"savings_balance": "0.000 STEEM",
"reward_steem_balance": "0.004 STEEM",
"vesting_shares": "1109.094445 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "7034.565361 VESTS",
"sbd_balance": "0.045 SBD",
"savings_sbd_balance": "0.000 SBD",
"reward_sbd_balance": "0.006 SBD",
"conversions": []
}Account Info
| name | ernest22 |
| id | 225978 |
| rank | 865,853 |
| reputation | 508841003 |
| created | 2017-06-27T05:34:21 |
| recovery_account | steem |
| proxy | None |
| post_count | 10 |
| comment_count | 0 |
| lifetime_vote_count | 0 |
| witnesses_voted_for | 0 |
| last_post | 2018-06-26T12:29:27 |
| last_root_post | 2018-06-26T12:29:27 |
| last_vote_time | 2018-06-29T08:17:48 |
| 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.045 SBD |
| savings_sbd_balance | 0.000 SBD |
| vesting_shares | 1109.094445 VESTS |
| delegated_vesting_shares | 0.000000 VESTS |
| received_vesting_shares | 7034.565361 VESTS |
| reward_vesting_balance | 16.238471 VESTS |
| vesting_balance | 0.000 STEEM |
| vesting_withdraw_rate | 0.000000 VESTS |
| next_vesting_withdrawal | 1969-12-31T23:59:59 |
| withdrawn | 0 |
| to_withdraw | 0 |
| withdraw_routes | 0 |
| savings_withdraw_requests | 0 |
| last_account_recovery | 1970-01-01T00:00:00 |
| reset_account | null |
| last_owner_update | 1970-01-01T00:00:00 |
| last_account_update | 2017-06-27T13:06:12 |
| 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": 225978,
"name": "ernest22",
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM6eTYiUMttwHSxeHoBFo2kohYWFXeKycMXEzEARMdWrChNFgnvi",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5DvhLRtRmP2sFxHKUwjWtKhGjan7fXyz4Lf9kc1N9BGeMdLfqA",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5YgkK1r9eheU1reGfg5V3bYBkmmLQ6mum1VfiTGuEwQUJt6Gzu",
1
]
]
},
"memo_key": "STM7MGV7adEkrJRx6kCCenm9o5C95RbJGJEd6m3MEhVU7NaidUW4n",
"json_metadata": "{\"profile\":{\"about\":\"Crypto Trader/ Miner\",\"location\":\"Hong Kong\",\"name\":\"Ernest Lau\",\"profile_image\":\"https://blogs-images.forbes.com/erikkain/files/2015/08/dishonored.jpg\"}}",
"posting_json_metadata": "{\"profile\":{\"about\":\"Crypto Trader/ Miner\",\"location\":\"Hong Kong\",\"name\":\"Ernest Lau\",\"profile_image\":\"https://blogs-images.forbes.com/erikkain/files/2015/08/dishonored.jpg\"}}",
"proxy": "",
"last_owner_update": "1970-01-01T00:00:00",
"last_account_update": "2017-06-27T13:06:12",
"created": "2017-06-27T05:34:21",
"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": 10,
"can_vote": true,
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779062595
},
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779062595
},
"voting_power": 0,
"balance": "0.000 STEEM",
"savings_balance": "0.000 STEEM",
"sbd_balance": "0.045 SBD",
"sbd_seconds": "0",
"sbd_seconds_last_update": "2017-08-27T08:05:27",
"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.006 SBD",
"reward_steem_balance": "0.004 STEEM",
"reward_vesting_balance": "16.238471 VESTS",
"reward_vesting_steem": "0.008 STEEM",
"vesting_shares": "1109.094445 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "7034.565361 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": 8,
"posting_rewards": 72,
"proxied_vsf_votes": [
0,
0,
0,
0
],
"witnesses_voted_for": 0,
"last_post": "2018-06-26T12:29:27",
"last_root_post": "2018-06-26T12:29:27",
"last_vote_time": "2018-06-29T08:17:48",
"post_bandwidth": 0,
"pending_claimed_accounts": 0,
"vesting_balance": "0.000 STEEM",
"reputation": 508841003,
"transfer_history": [],
"market_history": [],
"post_history": [],
"vote_history": [],
"other_history": [],
"witness_votes": [],
"tags_usage": [],
"guest_bloggers": [],
"rank": 865853
}Withdraw Routes
| Incoming | Outgoing |
|---|---|
Empty | Empty |
{
"incoming": [],
"outgoing": []
}From Date
To Date
2026/05/18 00:03:15
2026/05/18 00:03:15
| delegator | steem |
| delegatee | ernest22 |
| vesting shares | 7034.565361 VESTS |
| Transaction Info | Block #106143211/Trx dfd282eca3a7109b548fe0d3501e105f15e14519 |
View Raw JSON Data
{
"trx_id": "dfd282eca3a7109b548fe0d3501e105f15e14519",
"block": 106143211,
"trx_in_block": 10,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-05-18T00:03:15",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "ernest22",
"vesting_shares": "7034.565361 VESTS"
}
]
}2026/05/12 03:01:27
2026/05/12 03:01:27
| delegator | steem |
| delegatee | ernest22 |
| vesting shares | 4322.354956 VESTS |
| Transaction Info | Block #105974732/Trx acd17f52446b7cd4dc16c96ab6bc7ef5180421a1 |
View Raw JSON Data
{
"trx_id": "acd17f52446b7cd4dc16c96ab6bc7ef5180421a1",
"block": 105974732,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-05-12T03:01:27",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "ernest22",
"vesting_shares": "4322.354956 VESTS"
}
]
}2026/04/25 23:24:36
2026/04/25 23:24:36
| delegator | steem |
| delegatee | ernest22 |
| vesting shares | 7047.081117 VESTS |
| Transaction Info | Block #105510870/Trx 3623b4c6a1a01d4db44f4f7f0858abafee82f18e |
View Raw JSON Data
{
"trx_id": "3623b4c6a1a01d4db44f4f7f0858abafee82f18e",
"block": 105510870,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-04-25T23:24:36",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "ernest22",
"vesting_shares": "7047.081117 VESTS"
}
]
}2026/01/23 07:15:36
2026/01/23 07:15:36
| delegator | steem |
| delegatee | ernest22 |
| vesting shares | 4363.901775 VESTS |
| Transaction Info | Block #102851160/Trx 08cbdee0df55ad6b5576a97913ddf63014ac76ee |
View Raw JSON Data
{
"trx_id": "08cbdee0df55ad6b5576a97913ddf63014ac76ee",
"block": 102851160,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-01-23T07:15:36",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "ernest22",
"vesting_shares": "4363.901775 VESTS"
}
]
}2024/12/17 02:35:21
2024/12/17 02:35:21
| delegator | steem |
| delegatee | ernest22 |
| vesting shares | 4528.120972 VESTS |
| Transaction Info | Block #91297583/Trx 471e2d2b1c6c8c8b59ae6984f2100a9536ba9ca4 |
View Raw JSON Data
{
"trx_id": "471e2d2b1c6c8c8b59ae6984f2100a9536ba9ca4",
"block": 91297583,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2024-12-17T02:35:21",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "ernest22",
"vesting_shares": "4528.120972 VESTS"
}
]
}2023/11/13 18:17:57
2023/11/13 18:17:57
| delegator | steem |
| delegatee | ernest22 |
| vesting shares | 4697.254504 VESTS |
| Transaction Info | Block #79851782/Trx f1f66953cfc12198f3af16144c0d62a48b40e1a4 |
View Raw JSON Data
{
"trx_id": "f1f66953cfc12198f3af16144c0d62a48b40e1a4",
"block": 79851782,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2023-11-13T18:17:57",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "ernest22",
"vesting_shares": "4697.254504 VESTS"
}
]
}2023/09/21 21:35:36
2023/09/21 21:35:36
| delegator | steem |
| delegatee | ernest22 |
| vesting shares | 7634.533290 VESTS |
| Transaction Info | Block #78347544/Trx e145a1f67a83d057c08794062bcb899e6ca71991 |
View Raw JSON Data
{
"trx_id": "e145a1f67a83d057c08794062bcb899e6ca71991",
"block": 78347544,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2023-09-21T21:35:36",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "ernest22",
"vesting_shares": "7634.533290 VESTS"
}
]
}2022/11/03 11:25:27
2022/11/03 11:25:27
| delegator | steem |
| delegatee | ernest22 |
| vesting shares | 7856.214728 VESTS |
| Transaction Info | Block #69112928/Trx 5d6f0983437dd088b9350688c5452679749c172b |
View Raw JSON Data
{
"trx_id": "5d6f0983437dd088b9350688c5452679749c172b",
"block": 69112928,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2022-11-03T11:25:27",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "ernest22",
"vesting_shares": "7856.214728 VESTS"
}
]
}2022/01/17 10:42:39
2022/01/17 10:42:39
| delegator | steem |
| delegatee | ernest22 |
| vesting shares | 8076.747959 VESTS |
| Transaction Info | Block #60809119/Trx 0bd9cdde1190a11d9dba151b589eeffc3dc58367 |
View Raw JSON Data
{
"trx_id": "0bd9cdde1190a11d9dba151b589eeffc3dc58367",
"block": 60809119,
"trx_in_block": 42,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2022-01-17T10:42:39",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "ernest22",
"vesting_shares": "8076.747959 VESTS"
}
]
}2021/06/14 00:38:33
2021/06/14 00:38:33
| delegator | steem |
| delegatee | ernest22 |
| vesting shares | 8260.516617 VESTS |
| Transaction Info | Block #54607520/Trx 3301f9575a0bd262e1740da0c562063686664b2e |
View Raw JSON Data
{
"trx_id": "3301f9575a0bd262e1740da0c562063686664b2e",
"block": 54607520,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2021-06-14T00:38:33",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "ernest22",
"vesting_shares": "8260.516617 VESTS"
}
]
}2020/12/11 10:57:39
2020/12/11 10:57:39
| delegator | steem |
| delegatee | ernest22 |
| vesting shares | 8447.938591 VESTS |
| Transaction Info | Block #49354986/Trx 121e63ff2f63659f7c06d79e5954c7aba0e60878 |
View Raw JSON Data
{
"trx_id": "121e63ff2f63659f7c06d79e5954c7aba0e60878",
"block": 49354986,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-12-11T10:57:39",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "ernest22",
"vesting_shares": "8447.938591 VESTS"
}
]
}2020/12/06 04:34:54
2020/12/06 04:34:54
| delegator | steem |
| delegatee | ernest22 |
| vesting shares | 1912.543513 VESTS |
| Transaction Info | Block #49206550/Trx e711679df430b5b14eaa79bb476688c7a0be0cf2 |
View Raw JSON Data
{
"trx_id": "e711679df430b5b14eaa79bb476688c7a0be0cf2",
"block": 49206550,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-12-06T04:34:54",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "ernest22",
"vesting_shares": "1912.543513 VESTS"
}
]
}2020/12/05 14:35:51
2020/12/05 14:35:51
| delegator | steem |
| delegatee | ernest22 |
| vesting shares | 8454.146445 VESTS |
| Transaction Info | Block #49190085/Trx 03c0e46134ab6a376a493fae98b5f171d4a980ea |
View Raw JSON Data
{
"trx_id": "03c0e46134ab6a376a493fae98b5f171d4a980ea",
"block": 49190085,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-12-05T14:35:51",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "ernest22",
"vesting_shares": "8454.146445 VESTS"
}
]
}2020/11/02 15:13:18
2020/11/02 15:13:18
| delegator | steem |
| delegatee | ernest22 |
| vesting shares | 1920.017158 VESTS |
| Transaction Info | Block #48257308/Trx 7760be2d832f94aa8479b724b4877297bcc47769 |
View Raw JSON Data
{
"trx_id": "7760be2d832f94aa8479b724b4877297bcc47769",
"block": 48257308,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-11-02T15:13:18",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "ernest22",
"vesting_shares": "1920.017158 VESTS"
}
]
}2020/05/09 05:32:00
2020/05/09 05:32:00
| delegator | steem |
| delegatee | ernest22 |
| vesting shares | 8656.951804 VESTS |
| Transaction Info | Block #43216793/Trx d25d33e6c59f777ac28b91404136b240cdc63afa |
View Raw JSON Data
{
"trx_id": "d25d33e6c59f777ac28b91404136b240cdc63afa",
"block": 43216793,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-05-09T05:32:00",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "ernest22",
"vesting_shares": "8656.951804 VESTS"
}
]
}2020/05/08 09:06:30
2020/05/08 09:06:30
| delegator | steem |
| delegatee | ernest22 |
| vesting shares | 1953.311140 VESTS |
| Transaction Info | Block #43192861/Trx 6eed4905ede1c3c7744611d91a7fecce1148738c |
View Raw JSON Data
{
"trx_id": "6eed4905ede1c3c7744611d91a7fecce1148738c",
"block": 43192861,
"trx_in_block": 15,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-05-08T09:06:30",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "ernest22",
"vesting_shares": "1953.311140 VESTS"
}
]
}2019/09/18 05:04:42
2019/09/18 05:04:42
| delegator | steem |
| delegatee | ernest22 |
| vesting shares | 8789.566234 VESTS |
| Transaction Info | Block #36520271/Trx 47be091fdd163619e3b300938c6487d8e08603de |
View Raw JSON Data
{
"trx_id": "47be091fdd163619e3b300938c6487d8e08603de",
"block": 36520271,
"trx_in_block": 13,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-09-18T05:04:42",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "ernest22",
"vesting_shares": "8789.566234 VESTS"
}
]
}2019/06/27 07:08:33
2019/06/27 07:08:33
| parent author | ernest22 |
| parent permlink | secret-contract-private-smart-contract |
| author | steemitboard |
| permlink | steemitboard-notify-ernest22-20190627t070832000z |
| title | |
| body | Congratulations @ernest22! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@ernest22/birthday2.png</td><td>Happy Birthday! - You are on the Steem blockchain for 2 years!</td></tr></table> <sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@ernest22) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=ernest22)_</sub> ###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| Transaction Info | Block #34159417/Trx 2a5db54e6e7f705d412e18ac236933fe1de77424 |
View Raw JSON Data
{
"trx_id": "2a5db54e6e7f705d412e18ac236933fe1de77424",
"block": 34159417,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-06-27T07:08:33",
"op": [
"comment",
{
"parent_author": "ernest22",
"parent_permlink": "secret-contract-private-smart-contract",
"author": "steemitboard",
"permlink": "steemitboard-notify-ernest22-20190627t070832000z",
"title": "",
"body": "Congratulations @ernest22! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@ernest22/birthday2.png</td><td>Happy Birthday! - You are on the Steem blockchain for 2 years!</td></tr></table>\n\n<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@ernest22) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=ernest22)_</sub>\n\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}"
}
]
}2018/10/08 16:25:30
2018/10/08 16:25:30
| delegator | steem |
| delegatee | ernest22 |
| vesting shares | 8987.587146 VESTS |
| Transaction Info | Block #26632434/Trx 611b0e9701cfd704a0721cd11c690b7eff0d2cd4 |
View Raw JSON Data
{
"trx_id": "611b0e9701cfd704a0721cd11c690b7eff0d2cd4",
"block": 26632434,
"trx_in_block": 10,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-10-08T16:25:30",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "ernest22",
"vesting_shares": "8987.587146 VESTS"
}
]
}ernest22received 0.004 STEEM, 0.006 SBD, 0.010 SP author reward for @ernest22 / secret-contract-private-smart-contract2018/07/03 12:29:27
ernest22received 0.004 STEEM, 0.006 SBD, 0.010 SP author reward for @ernest22 / secret-contract-private-smart-contract
2018/07/03 12:29:27
| author | ernest22 |
| permlink | secret-contract-private-smart-contract |
| sbd payout | 0.006 SBD |
| steem payout | 0.004 STEEM |
| vesting payout | 16.238471 VESTS |
| Transaction Info | Block #23852108/Virtual Operation #4 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 23852108,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 4,
"timestamp": "2018-07-03T12:29:27",
"op": [
"author_reward",
{
"author": "ernest22",
"permlink": "secret-contract-private-smart-contract",
"sbd_payout": "0.006 SBD",
"steem_payout": "0.004 STEEM",
"vesting_payout": "16.238471 VESTS"
}
]
}ernest22upvoted (100.00%) @ernest22 / zencash-secure-nodes2018/06/29 08:17:48
ernest22upvoted (100.00%) @ernest22 / zencash-secure-nodes
2018/06/29 08:17:48
| voter | ernest22 |
| author | ernest22 |
| permlink | zencash-secure-nodes |
| weight | 10000 (100.00%) |
| Transaction Info | Block #23741383/Trx 73c415a9c957bcefcf2a07456e351747633a4abd |
View Raw JSON Data
{
"trx_id": "73c415a9c957bcefcf2a07456e351747633a4abd",
"block": 23741383,
"trx_in_block": 32,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-29T08:17:48",
"op": [
"vote",
{
"voter": "ernest22",
"author": "ernest22",
"permlink": "zencash-secure-nodes",
"weight": 10000
}
]
}ernest22upvoted (100.00%) @ernest22 / secret-contract-private-smart-contract2018/06/27 01:12:42
ernest22upvoted (100.00%) @ernest22 / secret-contract-private-smart-contract
2018/06/27 01:12:42
| voter | ernest22 |
| author | ernest22 |
| permlink | secret-contract-private-smart-contract |
| weight | 10000 (100.00%) |
| Transaction Info | Block #23675326/Trx d6597d7ddfc0a05e3fe93310fcfb7275f5ec9206 |
View Raw JSON Data
{
"trx_id": "d6597d7ddfc0a05e3fe93310fcfb7275f5ec9206",
"block": 23675326,
"trx_in_block": 23,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-27T01:12:42",
"op": [
"vote",
{
"voter": "ernest22",
"author": "ernest22",
"permlink": "secret-contract-private-smart-contract",
"weight": 10000
}
]
}smartcoinsupvoted (10.00%) @ernest22 / secret-contract-private-smart-contract2018/06/26 13:05:48
smartcoinsupvoted (10.00%) @ernest22 / secret-contract-private-smart-contract
2018/06/26 13:05:48
| voter | smartcoins |
| author | ernest22 |
| permlink | secret-contract-private-smart-contract |
| weight | 1000 (10.00%) |
| Transaction Info | Block #23660789/Trx 66521ca6619f930bdc4f2f461069aca4a93b7012 |
View Raw JSON Data
{
"trx_id": "66521ca6619f930bdc4f2f461069aca4a93b7012",
"block": 23660789,
"trx_in_block": 28,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-26T13:05:48",
"op": [
"vote",
{
"voter": "smartcoins",
"author": "ernest22",
"permlink": "secret-contract-private-smart-contract",
"weight": 1000
}
]
}ernest22published a new post: secret-contract-private-smart-contract2018/06/26 12:29:27
ernest22published a new post: secret-contract-private-smart-contract
2018/06/26 12:29:27
| parent author | |
| parent permlink | cryptocurrency |
| author | ernest22 |
| permlink | secret-contract-private-smart-contract |
| title | Secret Contract - Private Smart Contract |
| body | ### Background Blockchain stores all data publicly on it while it offers a open ledger for simple blockchain like Bitcoin, it might not be suitable to show every data publicly for more complicated application. Using smart contracts to interact with the blockchain and other users could expose a lot of sensitive user data in current model. Completely open blockchain is not a practical environment when users have submit sensitive data like bank info and history to the smart contracts. Some dApp provider keeps the actual computation of eligibility centralized, in order to limit the exposure of the sensitive data to the provider itself. However, the dApp retains all of the weaknesses of centralized applications like single point of failure and easy target of attack. ### Enigma Secure Contract The Enigma team design Secret Contract, the smart contract that protects the blockchain correctness through distributed consensus while executed privately. Secret contract can hide the data completely from the nodes. The nodes can execute the contract and receive the eligibility result without being able to observe the user’s transactions. Unlike using Zero-knowledge proofs which a party with access to the data can prove a claim to others without revealing the data to them, secret contracts usually have to outsource computations to execute the contract involving multiple parties that there isn’t a single party can be trusted to know all of the data. For secret contracts, secure computation is used to enable computing over encrypted data. Secure contracts are able to hide its exact data from the nodes in the network while preserving the ability to be executed and validated. ### Development In the first Enigma network release, it will make use of TEEs ( Trusted Execution Environments), the secure area inside any processor to conceal data from the network. In the second release, they will introduce secret contracts that are based on a purely cryptographic solution called secure Multi-Party Computation (MPC). Recently, Enigma has partnered with Intel on research and development efforts to advance development of privacy preserving computation technologies utilizing Intel technology to building a private, scalable, secure solution to power the real world daly usage of smart contracts with personal data. #### References https://blog.enigma.co/defining-secret-contracts-f40ddee67ef2 https://blog.enigma.co/why-enigmas-privacy-protocol-will-power-our-decentralized-future-aedb8c9ee2f6 https://blog.enigma.co/announcing-enigmas-collaboration-with-intel-43bbf73a86a7 https://www.youtube.com/watch?v=wheVhJvuTok |
| json metadata | {"tags":["cryptocurrency","blockchain","enigma","smartcontract","privacy"],"image":["https://img.youtube.com/vi/wheVhJvuTok/0.jpg"],"links":["https://blog.enigma.co/defining-secret-contracts-f40ddee67ef2","https://blog.enigma.co/why-enigmas-privacy-protocol-will-power-our-decentralized-future-aedb8c9ee2f6","https://blog.enigma.co/announcing-enigmas-collaboration-with-intel-43bbf73a86a7","https://www.youtube.com/watch?v=wheVhJvuTok"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #23660062/Trx d3192aee65ef97ff20a56375d54e0e045aaa5324 |
View Raw JSON Data
{
"trx_id": "d3192aee65ef97ff20a56375d54e0e045aaa5324",
"block": 23660062,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-26T12:29:27",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "cryptocurrency",
"author": "ernest22",
"permlink": "secret-contract-private-smart-contract",
"title": "Secret Contract - Private Smart Contract",
"body": "### Background\nBlockchain stores all data publicly on it while it offers a open ledger for simple blockchain like Bitcoin, it might not be suitable to show every data publicly for more complicated application.\n\nUsing smart contracts to interact with the blockchain and other users could expose a lot of sensitive user data in current model. Completely open blockchain is not a practical environment when users have submit sensitive data like bank info and history to the smart contracts.\n\nSome dApp provider keeps the actual computation of eligibility centralized, in order to limit the exposure of the sensitive data to the provider itself. However, the dApp retains all of the weaknesses of centralized applications like single point of failure and easy target of attack.\n\n### Enigma Secure Contract\nThe Enigma team design Secret Contract, the smart contract that protects the blockchain correctness through distributed consensus while executed privately. Secret contract can hide the data completely from the nodes. The nodes can execute the contract and receive the eligibility result without being able to observe the user’s transactions. \n\nUnlike using Zero-knowledge proofs which a party with access to the data can prove a claim to others without revealing the data to them, secret contracts usually have to outsource computations to execute the contract involving multiple parties that there isn’t a single party can be trusted to know all of the data.\n\nFor secret contracts, secure computation is used to enable computing over encrypted data. Secure contracts are able to hide its exact data from the nodes in the network while preserving the ability to be executed and validated. \n\n### Development\nIn the first Enigma network release, it will make use of TEEs ( Trusted Execution Environments), the secure area inside any processor to conceal data from the network. In the second release, they will introduce secret contracts that are based on a purely cryptographic solution called secure Multi-Party Computation (MPC).\n\nRecently, Enigma has partnered with Intel on research and development efforts to advance development of privacy preserving computation technologies utilizing Intel technology to building a private, scalable, secure solution to power the real world daly usage of smart contracts with personal data.\n\n\n#### References\nhttps://blog.enigma.co/defining-secret-contracts-f40ddee67ef2\nhttps://blog.enigma.co/why-enigmas-privacy-protocol-will-power-our-decentralized-future-aedb8c9ee2f6\nhttps://blog.enigma.co/announcing-enigmas-collaboration-with-intel-43bbf73a86a7\nhttps://www.youtube.com/watch?v=wheVhJvuTok",
"json_metadata": "{\"tags\":[\"cryptocurrency\",\"blockchain\",\"enigma\",\"smartcontract\",\"privacy\"],\"image\":[\"https://img.youtube.com/vi/wheVhJvuTok/0.jpg\"],\"links\":[\"https://blog.enigma.co/defining-secret-contracts-f40ddee67ef2\",\"https://blog.enigma.co/why-enigmas-privacy-protocol-will-power-our-decentralized-future-aedb8c9ee2f6\",\"https://blog.enigma.co/announcing-enigmas-collaboration-with-intel-43bbf73a86a7\",\"https://www.youtube.com/watch?v=wheVhJvuTok\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}ninjasnakeupvoted (100.00%) @ernest22 / zencash-secure-nodes2018/06/26 09:47:03
ninjasnakeupvoted (100.00%) @ernest22 / zencash-secure-nodes
2018/06/26 09:47:03
| voter | ninjasnake |
| author | ernest22 |
| permlink | zencash-secure-nodes |
| weight | 10000 (100.00%) |
| Transaction Info | Block #23656814/Trx 7f6cbcaf9d88b47e207486d59bb00fd3186c081c |
View Raw JSON Data
{
"trx_id": "7f6cbcaf9d88b47e207486d59bb00fd3186c081c",
"block": 23656814,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-26T09:47:03",
"op": [
"vote",
{
"voter": "ninjasnake",
"author": "ernest22",
"permlink": "zencash-secure-nodes",
"weight": 10000
}
]
}2018/06/26 02:21:54
2018/06/26 02:21:54
| parent author | ernest22 |
| parent permlink | zencash-secure-nodes |
| author | a-0-1 |
| permlink | re-ernest22-zencash-secure-nodes-20180626t022157289z |
| title | |
| body | https://steemit.com/news/@bible.com/6h36cq |
| json metadata | {"tags":["cryptocurrency"],"links":["https://steemit.com/news/@bible.com/6h36cq"],"app":"steemit/0.1"} |
| Transaction Info | Block #23647911/Trx 78dac7a15c9e5b73cecc29499728ce1e80aa2104 |
View Raw JSON Data
{
"trx_id": "78dac7a15c9e5b73cecc29499728ce1e80aa2104",
"block": 23647911,
"trx_in_block": 41,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-26T02:21:54",
"op": [
"comment",
{
"parent_author": "ernest22",
"parent_permlink": "zencash-secure-nodes",
"author": "a-0-1",
"permlink": "re-ernest22-zencash-secure-nodes-20180626t022157289z",
"title": "",
"body": "https://steemit.com/news/@bible.com/6h36cq",
"json_metadata": "{\"tags\":[\"cryptocurrency\"],\"links\":[\"https://steemit.com/news/@bible.com/6h36cq\"],\"app\":\"steemit/0.1\"}"
}
]
}nkr2222upvoted (100.00%) @ernest22 / zencash-secure-nodes2018/06/26 02:21:51
nkr2222upvoted (100.00%) @ernest22 / zencash-secure-nodes
2018/06/26 02:21:51
| voter | nkr2222 |
| author | ernest22 |
| permlink | zencash-secure-nodes |
| weight | 10000 (100.00%) |
| Transaction Info | Block #23647910/Trx e53b21a1783a80da3f1ee02d156462a89b422945 |
View Raw JSON Data
{
"trx_id": "e53b21a1783a80da3f1ee02d156462a89b422945",
"block": 23647910,
"trx_in_block": 23,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-26T02:21:51",
"op": [
"vote",
{
"voter": "nkr2222",
"author": "ernest22",
"permlink": "zencash-secure-nodes",
"weight": 10000
}
]
}ernest22published a new post: zencash-secure-nodes2018/06/26 02:21:06
ernest22published a new post: zencash-secure-nodes
2018/06/26 02:21:06
| parent author | |
| parent permlink | cryptocurrency |
| author | ernest22 |
| permlink | zencash-secure-nodes |
| title | ZenCash Secure Nodes |
| body | ## ZenCash Secure Nodes ZenCash is a fork of ZClassic which is a also fork of ZCash. Like its origin, ZenCash also has private transaction using zk-SNARKS build on top of bitcoin codebase. ZenCash improves the security and the privacy of the network by introducing secure nodes. Secure nodes are similar to masternodes that can be found in other coins like Dash. However, their main function is not bringing extra features like instandsend into ZenCash, but to secure the whole network and improve censorship resistance. ### Importance of Nodes Network communication among nodes in most of the blockchain network is unencrypted hence it is easily identified on the internet when a user accessing any blockchain data. Governments or attackers can censor or block the data especially for blocking the whole privacy focused blockchain which renders the privacy features inside the network useless. Moreover, the quality of the nodes are not guaranteed as we do not know what kind of machines are they running on or how frequent they are staying online so these nodes might face DDoS attack harming the whole network. Private transaction and communication worldwide is protected by the ZenCash secure nodes by encrypting the network connection and communication among the resilient secure nodes with valid security certificate. 3.5% mining reward is distributed to secure nodes operator to incentify people secure the network instead of relying on nodes ran by volunteer like on bitcoin. Secure nodes have to accept the daily “publish challenge” which nodes prove their hardware and network compatibility by regularly sending the z-transaction within the network. This also improves the privacy of user’s z-transaction as it would be less obvious when it is mixed with all the z-transaction by the secure nodes filled up the network. ### Requirement To run a ZenCash Secure Node, the node operator have to have 42 ZEN (~ 700 USD at current price) deposited and locked into their node transparent t-address just like other masternodes. The machine that the node is running on should have enough processing power and 2.5+ GB of memory to withstand DDoS attacks and process private transactions. 92%+ uptime is also required to deliver a stable network and smooth user experience. ### Development There are 12,000 secure nodes online globally higher than 9600 full nodes of the bitcoin network, showing strong interest and decentralisation of the ZenCash project. The ZenCash Dev Team has actively announced the plans and updated whitepaper to add Super Nodes which introduces more features like side chains to the ZenCash network by the end of 2018. The secure node reward would be raised from 3.5% to 10% of the mining reward, and the super nodes would receive another 10% of the mining reward that can drive up the demand ZenCash. #### References https://zencash.com/securenodes/ https://blog.zencash.com/secure-nodes-why-are-they-important/ https://www.youtube.com/watch?v=pgTPy4D27Yg https://securenodes.eu.zensystem.io/ https://blog.zencash.com/zencash-super-nodes-new-white-paper/ |
| json metadata | {"tags":["cryptocurrency","blockchain","zencash","privacy","node"],"image":["https://img.youtube.com/vi/pgTPy4D27Yg/0.jpg"],"links":["https://zencash.com/securenodes/","https://blog.zencash.com/secure-nodes-why-are-they-important/","https://www.youtube.com/watch?v=pgTPy4D27Yg","https://securenodes.eu.zensystem.io/","https://blog.zencash.com/zencash-super-nodes-new-white-paper/"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #23647895/Trx d1ecc00fb1ca4c6d4cfe7e8eb220a46f39f5f821 |
View Raw JSON Data
{
"trx_id": "d1ecc00fb1ca4c6d4cfe7e8eb220a46f39f5f821",
"block": 23647895,
"trx_in_block": 51,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-26T02:21:06",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "cryptocurrency",
"author": "ernest22",
"permlink": "zencash-secure-nodes",
"title": "ZenCash Secure Nodes",
"body": "## ZenCash Secure Nodes \n\nZenCash is a fork of ZClassic which is a also fork of ZCash. Like its origin, ZenCash also has private transaction using zk-SNARKS build on top of bitcoin codebase. ZenCash improves the security and the privacy of the network by introducing secure nodes.\n\nSecure nodes are similar to masternodes that can be found in other coins like Dash. However, their main function is not bringing extra features like instandsend into ZenCash, but to secure the whole network and improve censorship resistance.\n\n### Importance of Nodes \nNetwork communication among nodes in most of the blockchain network is unencrypted hence it is easily identified on the internet when a user accessing any blockchain data. Governments or attackers can censor or block the data especially for blocking the whole privacy focused blockchain which renders the privacy features inside the network useless. Moreover, the quality of the nodes are not guaranteed as we do not know what kind of machines are they running on or how frequent they are staying online so these nodes might face DDoS attack harming the whole network. \n\nPrivate transaction and communication worldwide is protected by the ZenCash secure nodes by encrypting the network connection and communication among the resilient secure nodes with valid security certificate. 3.5% mining reward is distributed to secure nodes operator to incentify people secure the network instead of relying on nodes ran by volunteer like on bitcoin.\n\nSecure nodes have to accept the daily “publish challenge” which nodes prove their hardware and network compatibility by regularly sending the z-transaction within the network. This also improves the privacy of user’s z-transaction as it would be less obvious when it is mixed with all the z-transaction by the secure nodes filled up the network.\n\n### Requirement \nTo run a ZenCash Secure Node, the node operator have to have 42 ZEN (~ 700 USD at current price) deposited and locked into their node transparent t-address just like other masternodes. \nThe machine that the node is running on should have enough processing power and 2.5+ GB of memory to withstand DDoS attacks and process private transactions. 92%+ uptime is also required to deliver a stable network and smooth user experience. \n\n### Development \nThere are 12,000 secure nodes online globally higher than 9600 full nodes of the bitcoin network, showing strong interest and decentralisation of the ZenCash project. The ZenCash Dev Team has actively announced the plans and updated whitepaper to add Super Nodes which introduces more features like side chains to the ZenCash network by the end of 2018. The secure node reward would be raised from 3.5% to 10% of the mining reward, and the super nodes would receive another 10% of the mining reward that can drive up the demand ZenCash.\n\n#### References\nhttps://zencash.com/securenodes/\nhttps://blog.zencash.com/secure-nodes-why-are-they-important/\nhttps://www.youtube.com/watch?v=pgTPy4D27Yg\nhttps://securenodes.eu.zensystem.io/\nhttps://blog.zencash.com/zencash-super-nodes-new-white-paper/",
"json_metadata": "{\"tags\":[\"cryptocurrency\",\"blockchain\",\"zencash\",\"privacy\",\"node\"],\"image\":[\"https://img.youtube.com/vi/pgTPy4D27Yg/0.jpg\"],\"links\":[\"https://zencash.com/securenodes/\",\"https://blog.zencash.com/secure-nodes-why-are-they-important/\",\"https://www.youtube.com/watch?v=pgTPy4D27Yg\",\"https://securenodes.eu.zensystem.io/\",\"https://blog.zencash.com/zencash-super-nodes-new-white-paper/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}ernest22published a new post: progpow-asic-resistance-algorithm2018/06/22 11:16:30
ernest22published a new post: progpow-asic-resistance-algorithm
2018/06/22 11:16:30
| parent author | |
| parent permlink | blockchain |
| author | ernest22 |
| permlink | progpow-asic-resistance-algorithm |
| title | ProgPoW ASIC resistance algorithm |
| body | @@ -3241,17 +3241,17 @@ efore fu -t +r ther cha |
| json metadata | {"tags":["blockchain","cryptocurrency","ethereum","pow","mining"],"image":["https://img.youtube.com/vi/hzHVNe6jI2I/0.jpg"],"links":["https://github.com/ifdefelse/ProgPOW","https://github.com/ethereum/EIPs/blob/master/EIPS/eip-1057.md","https://github.com/ubiq/UIPs/blob/master/UIPs/uip-1.md","https://steemit.com/mining/@gainer/ubiq-proposes-switch-to-progpow-to-dissuade-mining","https://cryptoslate.com/vitalik-buterin-ethash-asics-ethereum","https://www.youtube.com/watch?v=hzHVNe6jI2I"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #23543427/Trx 907e900bad75bf9054f8d6037618882c0905940b |
View Raw JSON Data
{
"trx_id": "907e900bad75bf9054f8d6037618882c0905940b",
"block": 23543427,
"trx_in_block": 34,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-22T11:16:30",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "blockchain",
"author": "ernest22",
"permlink": "progpow-asic-resistance-algorithm",
"title": "ProgPoW ASIC resistance algorithm",
"body": "@@ -3241,17 +3241,17 @@\n efore fu\n-t\n+r\n ther cha\n",
"json_metadata": "{\"tags\":[\"blockchain\",\"cryptocurrency\",\"ethereum\",\"pow\",\"mining\"],\"image\":[\"https://img.youtube.com/vi/hzHVNe6jI2I/0.jpg\"],\"links\":[\"https://github.com/ifdefelse/ProgPOW\",\"https://github.com/ethereum/EIPs/blob/master/EIPS/eip-1057.md\",\"https://github.com/ubiq/UIPs/blob/master/UIPs/uip-1.md\",\"https://steemit.com/mining/@gainer/ubiq-proposes-switch-to-progpow-to-dissuade-mining\",\"https://cryptoslate.com/vitalik-buterin-ethash-asics-ethereum\",\"https://www.youtube.com/watch?v=hzHVNe6jI2I\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}ernest22published a new post: progpow-asic-resistance-algorithm2018/06/22 10:59:09
ernest22published a new post: progpow-asic-resistance-algorithm
2018/06/22 10:59:09
| parent author | |
| parent permlink | blockchain |
| author | ernest22 |
| permlink | progpow-asic-resistance-algorithm |
| title | ProgPoW ASIC resistance algorithm |
| body | ### Mining Algorithm ProgPoW (Programmatic Proof of Work) is a proof-of-work algorithm designed to close the efficiency gap available to specialized ASICs. Mining algorithm claims to be ASIC resistance generally uses extra parametres or mixing different algorithms to make the ASIC more complicated to be developed. However, ASIC manufacture can eventually develop their workaround with enough economic incentives like the popularity and the price rise of a coin. Ethash has showed the strongest ASIC resistance (least efficiency gain) even Antminer E3 ASIC is released by Bitmain recently. Among ASIC resistant algorithm that has been “cracked” by ASICs like Equihash, CryptoNight, X11 which shows 50-1000x efficiency gain from ASICs, Ethash ASIC actually gains less than 2x efficiency over GPU making it a lot less favorable investment switching from GPU rigs to ASICs with higher risk and not much profit. Even Vitalik did not think the E3 ASIC is a big threat to Ethereum. ProgPoW follows the same general structure of Ethash by having a large size of the DAG file that have to be loaded into the memory during computation, so the mining performance is limited by the memory size and speed which can hardly improve efficiency on as both GPU and ASIC are using memory on same technology level limiting any advantage. ProgPoW improves upon Ethash by making the algorithm fits the hardware design of a GPU natively and efficiently use all the parts in a GPU to limit the efficiency gain of ASIC to maximum 1.1-1.2x. Therefore, the interest of developing an ASIC miner should decrease and GPU miners can still be profitable even there are ASICs in the market. ProgPoW is a programmable algorithm which can be tuned (even periodically) to fight ASIC by tweaking the parameters through a soft fork without a hard fork for algorithm change. ### Dev Team OhGodACompany is the team created the OhGodAnETHlargementPill which is a plugin that successfully boost the performance of GTX1080ti and GTX1080 GPU by 50% mining Ethash. The team has shown strong background in developing and optimizing mining algorithm/software for GPU. ### Why ASIC Resistance? ASIC Resistance does not just help decentralisation and prevent the monopoly of miner manufactures, it also attract more interest and build the community to grow the project. One of the reason that Ethereum became such popular is the growth of the mining community who can participate in the network and get rewarded with just their home computer or even laptops. CPU and GPU mining are more accessible to the masses and bring them to experience cryptocurrency and blockchain before investing with serious money or even understand the technology behind. ProgPoW can be easily implement into Ethash based coins and some other coin community also show strong interest in it. EIP-1057 has been proposed to implement ProgPoW into Ethereum and UIP-1 is proposed for Ubiq. The Ethereum community is not likely to pass the proposal at the moment while the Ubiq community has voted actively and the algorithm change will be implement into the mainnet soon. If Ethereum migration towards PoS does not go well or get delayed, ProgPoW might also be a good option to continue decentralisation before futther changes. #### References https://github.com/ifdefelse/ProgPOW https://github.com/ethereum/EIPs/blob/master/EIPS/eip-1057.md https://github.com/ubiq/UIPs/blob/master/UIPs/uip-1.md https://steemit.com/mining/@gainer/ubiq-proposes-switch-to-progpow-to-dissuade-mining https://cryptoslate.com/vitalik-buterin-ethash-asics-ethereum https://www.youtube.com/watch?v=hzHVNe6jI2I |
| json metadata | {"tags":["blockchain","cryptocurrency","ethereum","pow","mining"],"image":["https://img.youtube.com/vi/hzHVNe6jI2I/0.jpg"],"links":["https://github.com/ifdefelse/ProgPOW","https://github.com/ethereum/EIPs/blob/master/EIPS/eip-1057.md","https://github.com/ubiq/UIPs/blob/master/UIPs/uip-1.md","https://steemit.com/mining/@gainer/ubiq-proposes-switch-to-progpow-to-dissuade-mining","https://cryptoslate.com/vitalik-buterin-ethash-asics-ethereum","https://www.youtube.com/watch?v=hzHVNe6jI2I"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #23543080/Trx 51972284db3ef0ca19237963665f1e70282844dc |
View Raw JSON Data
{
"trx_id": "51972284db3ef0ca19237963665f1e70282844dc",
"block": 23543080,
"trx_in_block": 15,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-22T10:59:09",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "blockchain",
"author": "ernest22",
"permlink": "progpow-asic-resistance-algorithm",
"title": "ProgPoW ASIC resistance algorithm",
"body": "### Mining Algorithm\nProgPoW (Programmatic Proof of Work) is a proof-of-work algorithm designed to close the efficiency gap available to specialized ASICs.\n\nMining algorithm claims to be ASIC resistance generally uses extra parametres or mixing different algorithms to make the ASIC more complicated to be developed. However, ASIC manufacture can eventually develop their workaround with enough economic incentives like the popularity and the price rise of a coin.\n\nEthash has showed the strongest ASIC resistance (least efficiency gain) even Antminer E3 ASIC is released by Bitmain recently. Among ASIC resistant algorithm that has been “cracked” by ASICs like Equihash, CryptoNight, X11 which shows 50-1000x efficiency gain from ASICs, Ethash ASIC actually gains less than 2x efficiency over GPU making it a lot less favorable investment switching from GPU rigs to ASICs with higher risk and not much profit. Even Vitalik did not think the E3 ASIC is a big threat to Ethereum.\n\nProgPoW follows the same general structure of Ethash by having a large size of the DAG file that have to be loaded into the memory during computation, so the mining performance is limited by the memory size and speed which can hardly improve efficiency on as both GPU and ASIC are using memory on same technology level limiting any advantage.\n\n\nProgPoW improves upon Ethash by making the algorithm fits the hardware design of a GPU natively and efficiently use all the parts in a GPU to limit the efficiency gain of ASIC to maximum 1.1-1.2x. Therefore, the interest of developing an ASIC miner should decrease and GPU miners can still be profitable even there are ASICs in the market. ProgPoW is a programmable algorithm which can be tuned (even periodically) to fight ASIC by tweaking the parameters through a soft fork without a hard fork for algorithm change. \n\n### Dev Team\nOhGodACompany is the team created the OhGodAnETHlargementPill which is a plugin that successfully boost the performance of GTX1080ti and GTX1080 GPU by 50% mining Ethash. The team has shown strong background in developing and optimizing mining algorithm/software for GPU.\n\n### Why ASIC Resistance?\nASIC Resistance does not just help decentralisation and prevent the monopoly of miner manufactures, it also attract more interest and build the community to grow the project. One of the reason that Ethereum became such popular is the growth of the mining community who can participate in the network and get rewarded with just their home computer or even laptops. CPU and GPU mining are more accessible to the masses and bring them to experience cryptocurrency and blockchain before investing with serious money or even understand the technology behind.\n \nProgPoW can be easily implement into Ethash based coins and some other coin community also show strong interest in it. EIP-1057 has been proposed to implement ProgPoW into Ethereum and UIP-1 is proposed for Ubiq. The Ethereum community is not likely to pass the proposal at the moment while the Ubiq community has voted actively and the algorithm change will be implement into the mainnet soon. If Ethereum migration towards PoS does not go well or get delayed, ProgPoW might also be a good option to continue decentralisation before futther changes. \n\n\n#### References\nhttps://github.com/ifdefelse/ProgPOW\nhttps://github.com/ethereum/EIPs/blob/master/EIPS/eip-1057.md\nhttps://github.com/ubiq/UIPs/blob/master/UIPs/uip-1.md\nhttps://steemit.com/mining/@gainer/ubiq-proposes-switch-to-progpow-to-dissuade-mining\nhttps://cryptoslate.com/vitalik-buterin-ethash-asics-ethereum\nhttps://www.youtube.com/watch?v=hzHVNe6jI2I",
"json_metadata": "{\"tags\":[\"blockchain\",\"cryptocurrency\",\"ethereum\",\"pow\",\"mining\"],\"image\":[\"https://img.youtube.com/vi/hzHVNe6jI2I/0.jpg\"],\"links\":[\"https://github.com/ifdefelse/ProgPOW\",\"https://github.com/ethereum/EIPs/blob/master/EIPS/eip-1057.md\",\"https://github.com/ubiq/UIPs/blob/master/UIPs/uip-1.md\",\"https://steemit.com/mining/@gainer/ubiq-proposes-switch-to-progpow-to-dissuade-mining\",\"https://cryptoslate.com/vitalik-buterin-ethash-asics-ethereum\",\"https://www.youtube.com/watch?v=hzHVNe6jI2I\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}ernest22upvoted (100.00%) @ernest22 / bitcoin-addresses-and-what-is-bech32-bc12018/06/21 10:13:06
ernest22upvoted (100.00%) @ernest22 / bitcoin-addresses-and-what-is-bech32-bc1
2018/06/21 10:13:06
| voter | ernest22 |
| author | ernest22 |
| permlink | bitcoin-addresses-and-what-is-bech32-bc1 |
| weight | 10000 (100.00%) |
| Transaction Info | Block #23513362/Trx 9af72c4d7bd79749210003185aca1bd405f85b11 |
View Raw JSON Data
{
"trx_id": "9af72c4d7bd79749210003185aca1bd405f85b11",
"block": 23513362,
"trx_in_block": 17,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-21T10:13:06",
"op": [
"vote",
{
"voter": "ernest22",
"author": "ernest22",
"permlink": "bitcoin-addresses-and-what-is-bech32-bc1",
"weight": 10000
}
]
}ernest22published a new post: bitcoin-addresses-and-what-is-bech32-bc12018/06/21 10:07:15
ernest22published a new post: bitcoin-addresses-and-what-is-bech32-bc1
2018/06/21 10:07:15
| parent author | |
| parent permlink | bitcoin |
| author | ernest22 |
| permlink | bitcoin-addresses-and-what-is-bech32-bc1 |
| title | Bitcoin Addresses & What is Bech32 (bc1) |
| body | #### Address validation Rather than just checking for string length, allowed characters (0-9, A-Z, a-z), or that the address starts with a 1, 3 or bc1, a bitcoin address can be validate with a checksum built into the address. For a 25-byte legacy address, the last 4 bytes of the address is actually a checksum which is part of the double SHA-256 hash of the previous 21 bytes in the address. Therefore, with a wallet software that implement such checksum validation function, a mistyped address by user would be recognised and rejected when the checksum was computed by the first 21 bytes and compare with the one existing in the address. #### Bitcoin Address Formats There are currently 3 address formats in use: Legacy Address (P2PKH): begins with the number 1 Segwit & Multisig Address (P2SH): starting with the number 3 (better backward compatibility) Segwit & Multisig Address (Bech32): starting with bc1 (newer native Segwit format) Legacy P2PKH (Pay-to-PubkeyHash) Address simply locks the unspent fund with the redeemer hashed public key and unlock the fund by comparing Pubkey Hash P2SH (Pay-to-Script-Hash) Address allows funds to be locked in conditions like multisig in a basic smart contract way. #### Bech32 Development Bech32 is implemented to bitcoin as BIP173 in late 2017 as an updated P2SH format that is less compatible with older softwares right now but it offers more optimal efficiency and security when more softwares support it. One of the main differences of Bech32 format is that it is not case sensitive (only includes 0-9, a-z in the address), hence it avoids confusion when writing down and is easier to read out. As less characters are needed in the address, the address is encoded in Base 32 instead of the traditional Base 58 which is more convenient and efficient in computation, and also more widely adopted in other computer application. Data can be stored a lot more compactly to in QR code. The double SHA256 checksum with the original Base 58 is slow and has no error-detection guarantees. Bech32 offers higher security with better optimise error detection code to the checksum to minimise the chance of accepting an invalid address. Most of the research on error-detecting codes only applies to Base 32 like formats making Bech32 more mature in security and technology. Currently, only less than 1% of BTC is stored in Bech32 addresses in the whole network but the adoption rate has been growing since Dec 2017. Wallets such as Bitcoin Core, Electrum, Samourai Wallet, Coinomi are now fully supporting Bech32 addresses. Hardware wallets like Trezor and Ledger can use such addresses when pair with Electrum wallet. However, most exchanges and bitcoin ATM are not fully supporting the this format yet and among all the major exchanges only Coinbase supports withdrawal to Bech32 addresses. Although this address format is less popular right now, the adoption rate is rising just like the Segwit adoption by major wallets and exchanges few months before. This address format change is believed to be beneficial to the users to by protecting them from mistakes and confusion. Before we can really see easily readable words address being implemented, Bech32 could boost mass adoption by improving the user experience. ##### References http://rosettacode.org/wiki/Bitcoin/address_validation#C https://medium.com/@hrobeers/p2sh-bitcoin-script-puzzle-explained-26c8cb03ff90 https://github.com/bitcoin/bips/blob/master/bip-0173.mediawiki https://www.youtube.com/watch?v=NqiN9VFE4CU https://p2sh.info/dashboard/db/bech32-statistics?orgId=1 https://en.bitcoin.it/wiki/Bech32_adoption |
| json metadata | {"tags":["bitcoin","blockchain","cryptocurrency","blockstream","bech32"],"image":["https://img.youtube.com/vi/NqiN9VFE4CU/0.jpg"],"links":["http://rosettacode.org/wiki/Bitcoin/address_validation#C","https://medium.com/@hrobeers/p2sh-bitcoin-script-puzzle-explained-26c8cb03ff90","https://github.com/bitcoin/bips/blob/master/bip-0173.mediawiki","https://www.youtube.com/watch?v=NqiN9VFE4CU","https://p2sh.info/dashboard/db/bech32-statistics?orgId=1","https://en.bitcoin.it/wiki/Bech32_adoption"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #23513245/Trx aadfc65c5320638818ff616ddb472771e9dfbca7 |
View Raw JSON Data
{
"trx_id": "aadfc65c5320638818ff616ddb472771e9dfbca7",
"block": 23513245,
"trx_in_block": 22,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-21T10:07:15",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "bitcoin",
"author": "ernest22",
"permlink": "bitcoin-addresses-and-what-is-bech32-bc1",
"title": "Bitcoin Addresses & What is Bech32 (bc1)",
"body": "#### Address validation\nRather than just checking for string length, allowed characters (0-9, A-Z, a-z), or that the address starts with a 1, 3 or bc1, a bitcoin address can be validate with a checksum built into the address. For a 25-byte legacy address, the last 4 bytes of the address is actually a checksum which is part of the double SHA-256 hash of the previous 21 bytes in the address. Therefore, with a wallet software that implement such checksum validation function, a mistyped address by user would be recognised and rejected when the checksum was computed by the first 21 bytes and compare with the one existing in the address.\n\n#### Bitcoin Address Formats\nThere are currently 3 address formats in use:\nLegacy Address (P2PKH): begins with the number 1\nSegwit & Multisig Address (P2SH): starting with the number 3 (better backward compatibility) \nSegwit & Multisig Address (Bech32): starting with bc1 (newer native Segwit format)\n\nLegacy P2PKH (Pay-to-PubkeyHash) Address simply locks the unspent fund with the redeemer hashed public key and unlock the fund by comparing Pubkey Hash\nP2SH (Pay-to-Script-Hash) Address allows funds to be locked in conditions like multisig in a basic smart contract way.\n\n\n#### Bech32 Development\nBech32 is implemented to bitcoin as BIP173 in late 2017 as an updated P2SH format that is less compatible with older softwares right now but it offers more optimal efficiency and security when more softwares support it.\n\nOne of the main differences of Bech32 format is that it is not case sensitive (only includes 0-9, a-z in the address), hence it avoids confusion when writing down and is easier to read out. As less characters are needed in the address, the address is encoded in Base 32 instead of the traditional Base 58 which is more convenient and efficient in computation, and also more widely adopted in other computer application. Data can be stored a lot more compactly to in QR code.\n\nThe double SHA256 checksum with the original Base 58 is slow and has no error-detection guarantees. Bech32 offers higher security with better optimise error detection code to the checksum to minimise the chance of accepting an invalid address. Most of the research on error-detecting codes only applies to Base 32 like formats making Bech32 more mature in security and technology.\n\nCurrently, only less than 1% of BTC is stored in Bech32 addresses in the whole network but the adoption rate has been growing since Dec 2017. Wallets such as Bitcoin Core, Electrum, Samourai Wallet, Coinomi are now fully supporting Bech32 addresses. Hardware wallets like Trezor and Ledger can use such addresses when pair with Electrum wallet. However, most exchanges and bitcoin ATM are not fully supporting the this format yet and among all the major exchanges only Coinbase supports withdrawal to Bech32 addresses. Although this address format is less popular right now, the adoption rate is rising just like the Segwit adoption by major wallets and exchanges few months before. This address format change is believed to be beneficial to the users to by protecting them from mistakes and confusion. Before we can really see easily readable words address being implemented, Bech32 could boost mass adoption by improving the user experience. \n\n\n\n\n##### References\nhttp://rosettacode.org/wiki/Bitcoin/address_validation#C\nhttps://medium.com/@hrobeers/p2sh-bitcoin-script-puzzle-explained-26c8cb03ff90\nhttps://github.com/bitcoin/bips/blob/master/bip-0173.mediawiki\nhttps://www.youtube.com/watch?v=NqiN9VFE4CU\nhttps://p2sh.info/dashboard/db/bech32-statistics?orgId=1\nhttps://en.bitcoin.it/wiki/Bech32_adoption",
"json_metadata": "{\"tags\":[\"bitcoin\",\"blockchain\",\"cryptocurrency\",\"blockstream\",\"bech32\"],\"image\":[\"https://img.youtube.com/vi/NqiN9VFE4CU/0.jpg\"],\"links\":[\"http://rosettacode.org/wiki/Bitcoin/address_validation#C\",\"https://medium.com/@hrobeers/p2sh-bitcoin-script-puzzle-explained-26c8cb03ff90\",\"https://github.com/bitcoin/bips/blob/master/bip-0173.mediawiki\",\"https://www.youtube.com/watch?v=NqiN9VFE4CU\",\"https://p2sh.info/dashboard/db/bech32-statistics?orgId=1\",\"https://en.bitcoin.it/wiki/Bech32_adoption\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}ernest22upvoted (100.00%) @steemitboard / steemitboard-notify-ernest22-20180620t204341000z2018/06/21 01:30:36
ernest22upvoted (100.00%) @steemitboard / steemitboard-notify-ernest22-20180620t204341000z
2018/06/21 01:30:36
| voter | ernest22 |
| author | steemitboard |
| permlink | steemitboard-notify-ernest22-20180620t204341000z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #23502913/Trx 0e26fd6ad4106b2ee3cea16ca128eaca77d5c1b1 |
View Raw JSON Data
{
"trx_id": "0e26fd6ad4106b2ee3cea16ca128eaca77d5c1b1",
"block": 23502913,
"trx_in_block": 25,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-21T01:30:36",
"op": [
"vote",
{
"voter": "ernest22",
"author": "steemitboard",
"permlink": "steemitboard-notify-ernest22-20180620t204341000z",
"weight": 10000
}
]
}2018/06/20 20:43:39
2018/06/20 20:43:39
| parent author | ernest22 |
| parent permlink | schnorr-signatures-for-bitcoin |
| author | steemitboard |
| permlink | steemitboard-notify-ernest22-20180620t204341000z |
| title | |
| body | Congratulations @ernest22! You have completed some achievement on Steemit and have been rewarded with new badge(s) : [](http://steemitboard.com/@ernest22) Award for the number of upvotes received <sub>_Click on the badge to view your Board of Honor._</sub> <sub>_If you no longer want to receive notifications, reply to this comment with the word_ `STOP`</sub> **Do not miss the [last post](https://steemit.com/steemitboard/@steemitboard/steemitboard-world-cup-contest-argentina-vs-croatia) from @steemitboard!** --- **Participate in the [SteemitBoard World Cup Contest](https://steemit.com/steemitboard/@steemitboard/steemitboard-world-cup-contest-collect-badges-and-win-free-sbd)!** Collect World Cup badges and win free SBD Support the Gold Sponsors of the contest: [@good-karma](https://v2.steemconnect.com/sign/account-witness-vote?witness=good-karma&approve=1) and [@lukestokes](https://v2.steemconnect.com/sign/account-witness-vote?witness=lukestokes.mhth&approve=1) --- > Do you like [SteemitBoard's project](https://steemit.com/@steemitboard)? Then **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| Transaction Info | Block #23497175/Trx 5465092b7858ece1cb9a68c636e2b82038675852 |
View Raw JSON Data
{
"trx_id": "5465092b7858ece1cb9a68c636e2b82038675852",
"block": 23497175,
"trx_in_block": 38,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-20T20:43:39",
"op": [
"comment",
{
"parent_author": "ernest22",
"parent_permlink": "schnorr-signatures-for-bitcoin",
"author": "steemitboard",
"permlink": "steemitboard-notify-ernest22-20180620t204341000z",
"title": "",
"body": "Congratulations @ernest22! You have completed some achievement on Steemit and have been rewarded with new badge(s) :\n\n[](http://steemitboard.com/@ernest22) Award for the number of upvotes received\n\n<sub>_Click on the badge to view your Board of Honor._</sub>\n<sub>_If you no longer want to receive notifications, reply to this comment with the word_ `STOP`</sub>\n\n\n\n**Do not miss the [last post](https://steemit.com/steemitboard/@steemitboard/steemitboard-world-cup-contest-argentina-vs-croatia) from @steemitboard!**\n\n---\n**Participate in the [SteemitBoard World Cup Contest](https://steemit.com/steemitboard/@steemitboard/steemitboard-world-cup-contest-collect-badges-and-win-free-sbd)!**\nCollect World Cup badges and win free SBD\nSupport the Gold Sponsors of the contest: [@good-karma](https://v2.steemconnect.com/sign/account-witness-vote?witness=good-karma&approve=1) and [@lukestokes](https://v2.steemconnect.com/sign/account-witness-vote?witness=lukestokes.mhth&approve=1)\n\n---\n\n> Do you like [SteemitBoard's project](https://steemit.com/@steemitboard)? Then **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}"
}
]
}2018/06/20 17:55:45
2018/06/20 17:55:45
| delegator | steem |
| delegatee | ernest22 |
| vesting shares | 29357.865834 VESTS |
| Transaction Info | Block #23493825/Trx 6ca117da5c8a5fddbb53792bc4a485fe2bc61169 |
View Raw JSON Data
{
"trx_id": "6ca117da5c8a5fddbb53792bc4a485fe2bc61169",
"block": 23493825,
"trx_in_block": 22,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-20T17:55:45",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "ernest22",
"vesting_shares": "29357.865834 VESTS"
}
]
}ernest22upvoted (100.00%) @boxmining / 7bbeb370-7493-11e8-97f4-27fc95e090962018/06/20 17:07:15
ernest22upvoted (100.00%) @boxmining / 7bbeb370-7493-11e8-97f4-27fc95e09096
2018/06/20 17:07:15
| voter | ernest22 |
| author | boxmining |
| permlink | 7bbeb370-7493-11e8-97f4-27fc95e09096 |
| weight | 10000 (100.00%) |
| Transaction Info | Block #23492859/Trx 3bc97a2cbba771ec3b870bf7e255c7310fb75589 |
View Raw JSON Data
{
"trx_id": "3bc97a2cbba771ec3b870bf7e255c7310fb75589",
"block": 23492859,
"trx_in_block": 105,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-20T17:07:15",
"op": [
"vote",
{
"voter": "ernest22",
"author": "boxmining",
"permlink": "7bbeb370-7493-11e8-97f4-27fc95e09096",
"weight": 10000
}
]
}ernest22upvoted (100.00%) @ernest22 / schnorr-signatures-for-bitcoin2018/06/20 16:49:15
ernest22upvoted (100.00%) @ernest22 / schnorr-signatures-for-bitcoin
2018/06/20 16:49:15
| voter | ernest22 |
| author | ernest22 |
| permlink | schnorr-signatures-for-bitcoin |
| weight | 10000 (100.00%) |
| Transaction Info | Block #23492500/Trx 027f83338bc3f1f1f61bd97978cb1ec71a9098a5 |
View Raw JSON Data
{
"trx_id": "027f83338bc3f1f1f61bd97978cb1ec71a9098a5",
"block": 23492500,
"trx_in_block": 35,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-20T16:49:15",
"op": [
"vote",
{
"voter": "ernest22",
"author": "ernest22",
"permlink": "schnorr-signatures-for-bitcoin",
"weight": 10000
}
]
}ernest22published a new post: schnorr-signatures-for-bitcoin2018/06/20 16:49:09
ernest22published a new post: schnorr-signatures-for-bitcoin
2018/06/20 16:49:09
| parent author | |
| parent permlink | bitcoin |
| author | ernest22 |
| permlink | schnorr-signatures-for-bitcoin |
| title | Bitcoin Scaling: Schnorr signatures for Bitcoin |
| body | @@ -1,8 +1,12 @@ +### Backgrou @@ -8,16 +8,16 @@ kground%0A - Currentl @@ -747,16 +747,20 @@ ytes. %0A%0A +### Schnorr @@ -770,16 +770,16 @@ natures%0A - Schnorr @@ -1253,16 +1253,20 @@ one. %0A%0A +### Developm @@ -1269,16 +1269,16 @@ lopment%0A - Mu-sig i @@ -1759,16 +1759,20 @@ ature.%0A%0A +### Advantag @@ -1775,16 +1775,16 @@ ntages %0A - Schnorr @@ -2353,16 +2353,21 @@ ivacy.%0A%0A +#### Referenc |
| json metadata | {"tags":["bitcoin","blockchain","cryptocurrency","blockstream","schnorr"],"image":["https://img.youtube.com/vi/oTsjMz3DaLs/0.jpg"],"links":["https://www.coindesk.com/one-mathematicians-mission-boost-bitcoins-privacy-soon/","https://www.coindesk.com/schnorr-signatures-explained-bitcoin-tech/","https://hackernoon.com/excited-for-schnorr-signatures-a00ee467fc5f","http://diyhpl.us/~bryan/papers2/bitcoin/bitcoin-tech-dev-talks-schnorr-signatures.2018-02-01.pdf","https://www.youtube.com/watch?v=oTsjMz3DaLs","https://bitcointechtalk.com/scaling-bitcoin-schnorr-signatures-abe3b5c275d1"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #23492498/Trx a5b4d04214bb662a709e3f6d906d9fc33feae7d7 |
View Raw JSON Data
{
"trx_id": "a5b4d04214bb662a709e3f6d906d9fc33feae7d7",
"block": 23492498,
"trx_in_block": 25,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-20T16:49:09",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "bitcoin",
"author": "ernest22",
"permlink": "schnorr-signatures-for-bitcoin",
"title": "Bitcoin Scaling: Schnorr signatures for Bitcoin",
"body": "@@ -1,8 +1,12 @@\n+### \n Backgrou\n@@ -8,16 +8,16 @@\n kground%0A\n-\n Currentl\n@@ -747,16 +747,20 @@\n ytes. %0A%0A\n+### \n Schnorr \n@@ -770,16 +770,16 @@\n natures%0A\n-\n Schnorr \n@@ -1253,16 +1253,20 @@\n one. %0A%0A\n+### \n Developm\n@@ -1269,16 +1269,16 @@\n lopment%0A\n-\n Mu-sig i\n@@ -1759,16 +1759,20 @@\n ature.%0A%0A\n+### \n Advantag\n@@ -1775,16 +1775,16 @@\n ntages %0A\n-\n Schnorr \n@@ -2353,16 +2353,21 @@\n ivacy.%0A%0A\n+#### \n Referenc\n",
"json_metadata": "{\"tags\":[\"bitcoin\",\"blockchain\",\"cryptocurrency\",\"blockstream\",\"schnorr\"],\"image\":[\"https://img.youtube.com/vi/oTsjMz3DaLs/0.jpg\"],\"links\":[\"https://www.coindesk.com/one-mathematicians-mission-boost-bitcoins-privacy-soon/\",\"https://www.coindesk.com/schnorr-signatures-explained-bitcoin-tech/\",\"https://hackernoon.com/excited-for-schnorr-signatures-a00ee467fc5f\",\"http://diyhpl.us/~bryan/papers2/bitcoin/bitcoin-tech-dev-talks-schnorr-signatures.2018-02-01.pdf\",\"https://www.youtube.com/watch?v=oTsjMz3DaLs\",\"https://bitcointechtalk.com/scaling-bitcoin-schnorr-signatures-abe3b5c275d1\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}ernest22published a new post: schnorr-signatures-for-bitcoin2018/06/20 16:47:33
ernest22published a new post: schnorr-signatures-for-bitcoin
2018/06/20 16:47:33
| parent author | |
| parent permlink | bitcoin |
| author | ernest22 |
| permlink | schnorr-signatures-for-bitcoin |
| title | Bitcoin Scaling: Schnorr signatures for Bitcoin |
| body | Background Currently, Bitcoin Multi-Signature address uses a simple but inefficient way to handle the transactions. Each participant of a Multi-sig (M out of Total N) has to sign separately and these signature would just be simply added up into a scriptSig and included in the transaction. The issue of Multi-Sig transaction size that it grows larger linearly as the number of participants increases, and the issue is apparent as the size occupied by each scriptSig is quite significant relative to the whole transaction size. For example, a simple transaction by a simple address could be 200 bytes while the scriptSig occupies 100 byes, so a transaction by a 3 of 4 multi-sig would be around 400 bytes while the sum of scriptSig being 300 bytes. Schnorr Signatures Schnorr signatures in Bitcoin developed by Pieter Wuille from Blockstream solves this problem by mathematically combining multiple signatures into a single signature. The combined signature has the size of a single signature while providing the authorization of the original separate signatures. Schnorr signature can also be more efficient and compact than a traditional (ECDSA) signature has it has a smaller size of 64 bytes comparing to around 75 bytes of the traditional one. Development Mu-sig is the current and latest implementation of Schnorr Signatures and is being worked on as a BIP that can be activated with a soft fork as Segwit provides versioning for Bitcoin script. Mu-sig removes security and scalability drawbacks from previous implementation. Instead of verifying a signature according to each participants Public Key, Mu-sig will only need the sum of each participants public keys as a single public key so validation would occur on chain with one signature. Advantages Schnorr signatures offers faster validation for each transaction because only one pair of public key and signature is needed to validate through. On-chain transaction size is reduced which space is saved for the blockchain storage. Schnorr signatures cannot bring privacy feature to all transaction on chain but it improves privacy for participants of a Multi-Signature wallet because it will be hidden that the signature is actually derived from multiple Private Keys. Combining with other technology, Schnorr signatures can have great impact on bitcoin scaling and privacy. References https://www.coindesk.com/one-mathematicians-mission-boost-bitcoins-privacy-soon/ https://www.coindesk.com/schnorr-signatures-explained-bitcoin-tech/ https://hackernoon.com/excited-for-schnorr-signatures-a00ee467fc5f http://diyhpl.us/~bryan/papers2/bitcoin/bitcoin-tech-dev-talks-schnorr-signatures.2018-02-01.pdf https://www.youtube.com/watch?v=oTsjMz3DaLs https://bitcointechtalk.com/scaling-bitcoin-schnorr-signatures-abe3b5c275d1 |
| json metadata | {"tags":["bitcoin","blockchain","cryptocurrency","blockstream","schnorr"],"image":["https://img.youtube.com/vi/oTsjMz3DaLs/0.jpg"],"links":["https://www.coindesk.com/one-mathematicians-mission-boost-bitcoins-privacy-soon/","https://www.coindesk.com/schnorr-signatures-explained-bitcoin-tech/","https://hackernoon.com/excited-for-schnorr-signatures-a00ee467fc5f","http://diyhpl.us/~bryan/papers2/bitcoin/bitcoin-tech-dev-talks-schnorr-signatures.2018-02-01.pdf","https://www.youtube.com/watch?v=oTsjMz3DaLs","https://bitcointechtalk.com/scaling-bitcoin-schnorr-signatures-abe3b5c275d1"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #23492466/Trx 160a4d54ed09bf42966ac5fb2b2f86c3c43df6b1 |
View Raw JSON Data
{
"trx_id": "160a4d54ed09bf42966ac5fb2b2f86c3c43df6b1",
"block": 23492466,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-20T16:47:33",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "bitcoin",
"author": "ernest22",
"permlink": "schnorr-signatures-for-bitcoin",
"title": "Bitcoin Scaling: Schnorr signatures for Bitcoin",
"body": "Background\nCurrently, Bitcoin Multi-Signature address uses a simple but inefficient way to handle the transactions. Each participant of a Multi-sig (M out of Total N) has to sign separately and these signature would just be simply added up into a scriptSig and included in the transaction. The issue of Multi-Sig transaction size that it grows larger linearly as the number of participants increases, and the issue is apparent as the size occupied by each scriptSig is quite significant relative to the whole transaction size. For example, a simple transaction by a simple address could be 200 bytes while the scriptSig occupies 100 byes, so a transaction by a 3 of 4 multi-sig would be around 400 bytes while the sum of scriptSig being 300 bytes. \n\nSchnorr Signatures\nSchnorr signatures in Bitcoin developed by Pieter Wuille from Blockstream solves this problem by mathematically combining multiple signatures into a single signature. The combined signature has the size of a single signature while providing the authorization of the original separate signatures. Schnorr signature can also be more efficient and compact than a traditional (ECDSA) signature has it has a smaller size of 64 bytes comparing to around 75 bytes of the traditional one. \n\nDevelopment\nMu-sig is the current and latest implementation of Schnorr Signatures and is being worked on as a BIP that can be activated with a soft fork as Segwit provides versioning for Bitcoin script.\nMu-sig removes security and scalability drawbacks from previous implementation. Instead of verifying a signature according to each participants Public Key, Mu-sig will only need the sum of each participants public keys as a single public key so validation would occur on chain with one signature.\n\nAdvantages \nSchnorr signatures offers faster validation for each transaction because only one pair of public key and signature is needed to validate through. \nOn-chain transaction size is reduced which space is saved for the blockchain storage. Schnorr signatures cannot bring privacy feature to all transaction on chain but it improves privacy for participants of a Multi-Signature wallet because it will be hidden that the signature is actually derived from multiple Private Keys. Combining with other technology, Schnorr signatures can have great impact on bitcoin scaling and privacy.\n\nReferences\nhttps://www.coindesk.com/one-mathematicians-mission-boost-bitcoins-privacy-soon/\nhttps://www.coindesk.com/schnorr-signatures-explained-bitcoin-tech/\nhttps://hackernoon.com/excited-for-schnorr-signatures-a00ee467fc5f\nhttp://diyhpl.us/~bryan/papers2/bitcoin/bitcoin-tech-dev-talks-schnorr-signatures.2018-02-01.pdf\nhttps://www.youtube.com/watch?v=oTsjMz3DaLs\nhttps://bitcointechtalk.com/scaling-bitcoin-schnorr-signatures-abe3b5c275d1",
"json_metadata": "{\"tags\":[\"bitcoin\",\"blockchain\",\"cryptocurrency\",\"blockstream\",\"schnorr\"],\"image\":[\"https://img.youtube.com/vi/oTsjMz3DaLs/0.jpg\"],\"links\":[\"https://www.coindesk.com/one-mathematicians-mission-boost-bitcoins-privacy-soon/\",\"https://www.coindesk.com/schnorr-signatures-explained-bitcoin-tech/\",\"https://hackernoon.com/excited-for-schnorr-signatures-a00ee467fc5f\",\"http://diyhpl.us/~bryan/papers2/bitcoin/bitcoin-tech-dev-talks-schnorr-signatures.2018-02-01.pdf\",\"https://www.youtube.com/watch?v=oTsjMz3DaLs\",\"https://bitcointechtalk.com/scaling-bitcoin-schnorr-signatures-abe3b5c275d1\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}ernest22published a new post: schnorr-signatures-for-bitcoin2018/06/20 16:44:48
ernest22published a new post: schnorr-signatures-for-bitcoin
2018/06/20 16:44:48
| parent author | |
| parent permlink | bitcoin |
| author | ernest22 |
| permlink | schnorr-signatures-for-bitcoin |
| title | Schnorr signatures for Bitcoin |
| body | Background Currently, Bitcoin Multi-Signature address uses a simple but inefficient way to handle the transactions. Each participant of a Multi-sig (M out of Total N) has to sign separately and these signature would just be simply added up into a scriptSig and included in the transaction. The issue of Multi-Sig transaction size that it grows larger linearly as the number of participants increases, and the issue is apparent as the size occupied by each scriptSig is quite significant relative to the whole transaction size. For example, a simple transaction by a simple address could be 200 bytes while the scriptSig occupies 100 byes, so a transaction by a 3 of 4 multi-sig would be around 400 bytes while the sum of scriptSig being 300 bytes. Schnorr Signatures Schnorr signatures in Bitcoin developed by Pieter Wuille from Blockstream solves this problem by mathematically combining multiple signatures into a single signature. The combined signature has the size of a single signature while providing the authorization of the original separate signatures. Schnorr signature can also be more efficient and compact than a traditional (ECDSA) signature has it has a smaller size of 64 bytes comparing to around 75 bytes of the traditional one. Development Mu-sig is the current and latest implementation of Schnorr Signatures and is being worked on as a BIP that can be activated with a soft fork as Segwit provides versioning for Bitcoin script. Mu-sig removes security and scalability drawbacks from previous implementation. Instead of verifying a signature according to each participants Public Key, Mu-sig will only need the sum of each participants public keys as a single public key so validation would occur on chain with one signature. Advantages Schnorr signatures offers faster validation for each transaction because only one pair of public key and signature is needed to validate through. On-chain transaction size is reduced which space is saved for the blockchain storage. Schnorr signatures cannot bring privacy feature to all transaction on chain but it improves privacy for participants of a Multi-Signature wallet because it will be hidden that the signature is actually derived from multiple Private Keys. Combining with other technology, Schnorr signatures can have great impact on bitcoin scaling and privacy. References https://www.coindesk.com/one-mathematicians-mission-boost-bitcoins-privacy-soon/ https://www.coindesk.com/schnorr-signatures-explained-bitcoin-tech/ https://hackernoon.com/excited-for-schnorr-signatures-a00ee467fc5f http://diyhpl.us/~bryan/papers2/bitcoin/bitcoin-tech-dev-talks-schnorr-signatures.2018-02-01.pdf https://www.youtube.com/watch?v=oTsjMz3DaLs https://bitcointechtalk.com/scaling-bitcoin-schnorr-signatures-abe3b5c275d1 |
| json metadata | {"tags":["bitcoin","scaling","cryptocurrency","blockstream","multisig"],"image":["https://img.youtube.com/vi/oTsjMz3DaLs/0.jpg"],"links":["https://www.coindesk.com/one-mathematicians-mission-boost-bitcoins-privacy-soon/","https://www.coindesk.com/schnorr-signatures-explained-bitcoin-tech/","https://hackernoon.com/excited-for-schnorr-signatures-a00ee467fc5f","http://diyhpl.us/~bryan/papers2/bitcoin/bitcoin-tech-dev-talks-schnorr-signatures.2018-02-01.pdf","https://www.youtube.com/watch?v=oTsjMz3DaLs","https://bitcointechtalk.com/scaling-bitcoin-schnorr-signatures-abe3b5c275d1"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #23492411/Trx c5107fec6a7856545c1976ee3ed1018fb1076808 |
View Raw JSON Data
{
"trx_id": "c5107fec6a7856545c1976ee3ed1018fb1076808",
"block": 23492411,
"trx_in_block": 9,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-20T16:44:48",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "bitcoin",
"author": "ernest22",
"permlink": "schnorr-signatures-for-bitcoin",
"title": "Schnorr signatures for Bitcoin",
"body": "Background\nCurrently, Bitcoin Multi-Signature address uses a simple but inefficient way to handle the transactions. Each participant of a Multi-sig (M out of Total N) has to sign separately and these signature would just be simply added up into a scriptSig and included in the transaction. The issue of Multi-Sig transaction size that it grows larger linearly as the number of participants increases, and the issue is apparent as the size occupied by each scriptSig is quite significant relative to the whole transaction size. For example, a simple transaction by a simple address could be 200 bytes while the scriptSig occupies 100 byes, so a transaction by a 3 of 4 multi-sig would be around 400 bytes while the sum of scriptSig being 300 bytes. \n\nSchnorr Signatures\nSchnorr signatures in Bitcoin developed by Pieter Wuille from Blockstream solves this problem by mathematically combining multiple signatures into a single signature. The combined signature has the size of a single signature while providing the authorization of the original separate signatures. Schnorr signature can also be more efficient and compact than a traditional (ECDSA) signature has it has a smaller size of 64 bytes comparing to around 75 bytes of the traditional one. \n\nDevelopment\nMu-sig is the current and latest implementation of Schnorr Signatures and is being worked on as a BIP that can be activated with a soft fork as Segwit provides versioning for Bitcoin script.\nMu-sig removes security and scalability drawbacks from previous implementation. Instead of verifying a signature according to each participants Public Key, Mu-sig will only need the sum of each participants public keys as a single public key so validation would occur on chain with one signature.\n\nAdvantages \nSchnorr signatures offers faster validation for each transaction because only one pair of public key and signature is needed to validate through. \nOn-chain transaction size is reduced which space is saved for the blockchain storage. Schnorr signatures cannot bring privacy feature to all transaction on chain but it improves privacy for participants of a Multi-Signature wallet because it will be hidden that the signature is actually derived from multiple Private Keys. Combining with other technology, Schnorr signatures can have great impact on bitcoin scaling and privacy.\n\nReferences\nhttps://www.coindesk.com/one-mathematicians-mission-boost-bitcoins-privacy-soon/\nhttps://www.coindesk.com/schnorr-signatures-explained-bitcoin-tech/\nhttps://hackernoon.com/excited-for-schnorr-signatures-a00ee467fc5f\nhttp://diyhpl.us/~bryan/papers2/bitcoin/bitcoin-tech-dev-talks-schnorr-signatures.2018-02-01.pdf\nhttps://www.youtube.com/watch?v=oTsjMz3DaLs\nhttps://bitcointechtalk.com/scaling-bitcoin-schnorr-signatures-abe3b5c275d1",
"json_metadata": "{\"tags\":[\"bitcoin\",\"scaling\",\"cryptocurrency\",\"blockstream\",\"multisig\"],\"image\":[\"https://img.youtube.com/vi/oTsjMz3DaLs/0.jpg\"],\"links\":[\"https://www.coindesk.com/one-mathematicians-mission-boost-bitcoins-privacy-soon/\",\"https://www.coindesk.com/schnorr-signatures-explained-bitcoin-tech/\",\"https://hackernoon.com/excited-for-schnorr-signatures-a00ee467fc5f\",\"http://diyhpl.us/~bryan/papers2/bitcoin/bitcoin-tech-dev-talks-schnorr-signatures.2018-02-01.pdf\",\"https://www.youtube.com/watch?v=oTsjMz3DaLs\",\"https://bitcointechtalk.com/scaling-bitcoin-schnorr-signatures-abe3b5c275d1\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}ax3upvoted (3.00%) @ernest22 / schnorr-signatures-for-bitcoin2018/06/20 16:43:51
ax3upvoted (3.00%) @ernest22 / schnorr-signatures-for-bitcoin
2018/06/20 16:43:51
| voter | ax3 |
| author | ernest22 |
| permlink | schnorr-signatures-for-bitcoin |
| weight | 300 (3.00%) |
| Transaction Info | Block #23492392/Trx 9d737bc545b502c484ca6878cab3a6f0acdd45b3 |
View Raw JSON Data
{
"trx_id": "9d737bc545b502c484ca6878cab3a6f0acdd45b3",
"block": 23492392,
"trx_in_block": 37,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-20T16:43:51",
"op": [
"vote",
{
"voter": "ax3",
"author": "ernest22",
"permlink": "schnorr-signatures-for-bitcoin",
"weight": 300
}
]
}ernest22published a new post: schnorr-signatures-for-bitcoin2018/06/20 16:43:42
ernest22published a new post: schnorr-signatures-for-bitcoin
2018/06/20 16:43:42
| parent author | |
| parent permlink | bitcoin |
| author | ernest22 |
| permlink | schnorr-signatures-for-bitcoin |
| title | Schnorr signatures for Bitcoin |
| body | Background Currently, Bitcoin Multi-Signature address uses a simple but inefficient way to handle the transactions. Each participant of a Multi-sig (M out of Total N) has to sign separately and these signature would just be simply added up into a scriptSig and included in the transaction. The issue of Multi-Sig transaction size that it grows larger linearly as the number of participants increases, and the issue is apparent as the size occupied by each scriptSig is quite significant relative to the whole transaction size. For example, a simple transaction by a simple address could be 200 bytes while the scriptSig occupies 100 byes, so a transaction by a 3 of 4 multi-sig would be around 400 bytes while the sum of scriptSig being 300 bytes. Schnorr Signatures Schnorr signatures in Bitcoin developed by Pieter Wuille from Blockstream solves this problem by mathematically combining multiple signatures into a single signature. The combined signature has the size of a single signature while providing the authorization of the original separate signatures. Schnorr signature can also be more efficient and compact than a traditional (ECDSA) signature has it has a smaller size of 64 bytes comparing to around 75 bytes of the traditional one. Development Mu-sig is the current and latest implementation of Schnorr Signatures and is being worked on as a BIP that can be activated with a soft fork as Segwit provides versioning for Bitcoin script. Mu-sig removes security and scalability drawbacks from previous implementation. Instead of verifying a signature according to each participants Public Key, Mu-sig will only need the sum of each participants public keys as a single public key so validation would occur on chain with one signature. Advantages Schnorr signatures offers faster validation for each transaction because only one pair of public key and signature is needed to validate through. On-chain transaction size is reduced which space is saved for the blockchain storage. Schnorr signatures cannot bring privacy feature to all transaction on chain but it improves privacy for participants of a Multi-Signature wallet because it will be hidden that the signature is actually derived from multiple Private Keys. Combining with other technology, Schnorr signatures can have great impact on bitcoin scaling and privacy. References https://www.coindesk.com/one-mathematicians-mission-boost-bitcoins-privacy-soon/ https://www.coindesk.com/schnorr-signatures-explained-bitcoin-tech/ https://hackernoon.com/excited-for-schnorr-signatures-a00ee467fc5f http://diyhpl.us/~bryan/papers2/bitcoin/bitcoin-tech-dev-talks-schnorr-signatures.2018-02-01.pdf https://www.youtube.com/watch?v=oTsjMz3DaLs https://bitcointechtalk.com/scaling-bitcoin-schnorr-signatures-abe3b5c275d1 |
| json metadata | {"tags":["bitcoin"],"image":["https://img.youtube.com/vi/oTsjMz3DaLs/0.jpg"],"links":["https://www.coindesk.com/one-mathematicians-mission-boost-bitcoins-privacy-soon/","https://www.coindesk.com/schnorr-signatures-explained-bitcoin-tech/","https://hackernoon.com/excited-for-schnorr-signatures-a00ee467fc5f","http://diyhpl.us/~bryan/papers2/bitcoin/bitcoin-tech-dev-talks-schnorr-signatures.2018-02-01.pdf","https://www.youtube.com/watch?v=oTsjMz3DaLs","https://bitcointechtalk.com/scaling-bitcoin-schnorr-signatures-abe3b5c275d1"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #23492389/Trx 5f564a35ff3d24f6e95391f4260661ceb8ce537c |
View Raw JSON Data
{
"trx_id": "5f564a35ff3d24f6e95391f4260661ceb8ce537c",
"block": 23492389,
"trx_in_block": 31,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-20T16:43:42",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "bitcoin",
"author": "ernest22",
"permlink": "schnorr-signatures-for-bitcoin",
"title": "Schnorr signatures for Bitcoin",
"body": "Background\nCurrently, Bitcoin Multi-Signature address uses a simple but inefficient way to handle the transactions. Each participant of a Multi-sig (M out of Total N) has to sign separately and these signature would just be simply added up into a scriptSig and included in the transaction. The issue of Multi-Sig transaction size that it grows larger linearly as the number of participants increases, and the issue is apparent as the size occupied by each scriptSig is quite significant relative to the whole transaction size. For example, a simple transaction by a simple address could be 200 bytes while the scriptSig occupies 100 byes, so a transaction by a 3 of 4 multi-sig would be around 400 bytes while the sum of scriptSig being 300 bytes. \n\nSchnorr Signatures\nSchnorr signatures in Bitcoin developed by Pieter Wuille from Blockstream solves this problem by mathematically combining multiple signatures into a single signature. The combined signature has the size of a single signature while providing the authorization of the original separate signatures. Schnorr signature can also be more efficient and compact than a traditional (ECDSA) signature has it has a smaller size of 64 bytes comparing to around 75 bytes of the traditional one. \n\nDevelopment\nMu-sig is the current and latest implementation of Schnorr Signatures and is being worked on as a BIP that can be activated with a soft fork as Segwit provides versioning for Bitcoin script.\nMu-sig removes security and scalability drawbacks from previous implementation. Instead of verifying a signature according to each participants Public Key, Mu-sig will only need the sum of each participants public keys as a single public key so validation would occur on chain with one signature.\n\nAdvantages \nSchnorr signatures offers faster validation for each transaction because only one pair of public key and signature is needed to validate through. \nOn-chain transaction size is reduced which space is saved for the blockchain storage. Schnorr signatures cannot bring privacy feature to all transaction on chain but it improves privacy for participants of a Multi-Signature wallet because it will be hidden that the signature is actually derived from multiple Private Keys. Combining with other technology, Schnorr signatures can have great impact on bitcoin scaling and privacy.\n\nReferences\nhttps://www.coindesk.com/one-mathematicians-mission-boost-bitcoins-privacy-soon/\nhttps://www.coindesk.com/schnorr-signatures-explained-bitcoin-tech/\nhttps://hackernoon.com/excited-for-schnorr-signatures-a00ee467fc5f\nhttp://diyhpl.us/~bryan/papers2/bitcoin/bitcoin-tech-dev-talks-schnorr-signatures.2018-02-01.pdf\nhttps://www.youtube.com/watch?v=oTsjMz3DaLs\nhttps://bitcointechtalk.com/scaling-bitcoin-schnorr-signatures-abe3b5c275d1",
"json_metadata": "{\"tags\":[\"bitcoin\"],\"image\":[\"https://img.youtube.com/vi/oTsjMz3DaLs/0.jpg\"],\"links\":[\"https://www.coindesk.com/one-mathematicians-mission-boost-bitcoins-privacy-soon/\",\"https://www.coindesk.com/schnorr-signatures-explained-bitcoin-tech/\",\"https://hackernoon.com/excited-for-schnorr-signatures-a00ee467fc5f\",\"http://diyhpl.us/~bryan/papers2/bitcoin/bitcoin-tech-dev-talks-schnorr-signatures.2018-02-01.pdf\",\"https://www.youtube.com/watch?v=oTsjMz3DaLs\",\"https://bitcointechtalk.com/scaling-bitcoin-schnorr-signatures-abe3b5c275d1\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}2018/05/16 20:16:21
2018/05/16 20:16:21
| delegator | steem |
| delegatee | ernest22 |
| vesting shares | 9065.104463 VESTS |
| Transaction Info | Block #22489828/Trx d92a841864820125da4c376231b1afde5d4269a2 |
View Raw JSON Data
{
"trx_id": "d92a841864820125da4c376231b1afde5d4269a2",
"block": 22489828,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-16T20:16:21",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "ernest22",
"vesting_shares": "9065.104463 VESTS"
}
]
}2018/01/09 06:37:57
2018/01/09 06:37:57
| delegator | steem |
| delegatee | ernest22 |
| vesting shares | 29616.094847 VESTS |
| Transaction Info | Block #18819559/Trx a796cd3200b00fede32f0ffc1bc95775940f0209 |
View Raw JSON Data
{
"trx_id": "a796cd3200b00fede32f0ffc1bc95775940f0209",
"block": 18819559,
"trx_in_block": 10,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-09T06:37:57",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "ernest22",
"vesting_shares": "29616.094847 VESTS"
}
]
}ernest22upvoted (100.00%) @boxmining / tenx-got-me-the-cash-i-desperately-needed2017/09/23 05:05:51
ernest22upvoted (100.00%) @boxmining / tenx-got-me-the-cash-i-desperately-needed
2017/09/23 05:05:51
| voter | ernest22 |
| author | boxmining |
| permlink | tenx-got-me-the-cash-i-desperately-needed |
| weight | 10000 (100.00%) |
| Transaction Info | Block #15709454/Trx 9fcdb089f38bb931f1cc085c905e04e00025d47e |
View Raw JSON Data
{
"trx_id": "9fcdb089f38bb931f1cc085c905e04e00025d47e",
"block": 15709454,
"trx_in_block": 17,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-23T05:05:51",
"op": [
"vote",
{
"voter": "ernest22",
"author": "boxmining",
"permlink": "tenx-got-me-the-cash-i-desperately-needed",
"weight": 10000
}
]
}ernest22claimed reward balance: 0.045 SBD, 0.046 SP2017/08/27 08:05:27
ernest22claimed reward balance: 0.045 SBD, 0.046 SP
2017/08/27 08:05:27
| account | ernest22 |
| reward steem | 0.000 STEEM |
| reward sbd | 0.045 SBD |
| reward vests | 74.463972 VESTS |
| Transaction Info | Block #14935839/Trx 8f0db78e0811243f15591da6058413719c616a17 |
View Raw JSON Data
{
"trx_id": "8f0db78e0811243f15591da6058413719c616a17",
"block": 14935839,
"trx_in_block": 14,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-08-27T08:05:27",
"op": [
"claim_reward_balance",
{
"account": "ernest22",
"reward_steem": "0.000 STEEM",
"reward_sbd": "0.045 SBD",
"reward_vests": "74.463972 VESTS"
}
]
}ernest22custom json: follow2017/08/27 07:54:15
ernest22custom json: follow
2017/08/27 07:54:15
| required auths | [] |
| required posting auths | ["ernest22"] |
| id | follow |
| json | ["reblog",{"account":"ernest22","author":"zeenobit","permlink":"quick-introduction-to-market-depth-and-whale-anatomy"}] |
| Transaction Info | Block #14935615/Trx 9746865edc875f9a2b261c26521d203f4ea0645d |
View Raw JSON Data
{
"trx_id": "9746865edc875f9a2b261c26521d203f4ea0645d",
"block": 14935615,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-08-27T07:54:15",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"ernest22"
],
"id": "follow",
"json": "[\"reblog\",{\"account\":\"ernest22\",\"author\":\"zeenobit\",\"permlink\":\"quick-introduction-to-market-depth-and-whale-anatomy\"}]"
}
]
}ernest22upvoted (100.00%) @zeenobit / quick-introduction-to-market-depth-and-whale-anatomy2017/08/27 07:54:12
ernest22upvoted (100.00%) @zeenobit / quick-introduction-to-market-depth-and-whale-anatomy
2017/08/27 07:54:12
| voter | ernest22 |
| author | zeenobit |
| permlink | quick-introduction-to-market-depth-and-whale-anatomy |
| weight | 10000 (100.00%) |
| Transaction Info | Block #14935614/Trx cee2f035f1201f2e85b1d32dcb2fa0d517ee4a4e |
View Raw JSON Data
{
"trx_id": "cee2f035f1201f2e85b1d32dcb2fa0d517ee4a4e",
"block": 14935614,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-08-27T07:54:12",
"op": [
"vote",
{
"voter": "ernest22",
"author": "zeenobit",
"permlink": "quick-introduction-to-market-depth-and-whale-anatomy",
"weight": 10000
}
]
}2017/08/20 06:23:30
2017/08/20 06:23:30
| required auths | [] |
| required posting auths | ["ernest22"] |
| id | follow |
| json | ["follow",{"follower":"ernest22","following":"zeenobit","what":["blog"]}] |
| Transaction Info | Block #14732272/Trx e70677ebf3f318225aa9ea64e87b5974cbed38f8 |
View Raw JSON Data
{
"trx_id": "e70677ebf3f318225aa9ea64e87b5974cbed38f8",
"block": 14732272,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-08-20T06:23:30",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"ernest22"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"ernest22\",\"following\":\"zeenobit\",\"what\":[\"blog\"]}]"
}
]
}ernest22custom json: follow2017/08/20 06:23:18
ernest22custom json: follow
2017/08/20 06:23:18
| required auths | [] |
| required posting auths | ["ernest22"] |
| id | follow |
| json | ["reblog",{"account":"ernest22","author":"zeenobit","permlink":"quick-introduction-to-moving-averages"}] |
| Transaction Info | Block #14732268/Trx e5cc5added6503851730a5f4be5addd53587e6e8 |
View Raw JSON Data
{
"trx_id": "e5cc5added6503851730a5f4be5addd53587e6e8",
"block": 14732268,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-08-20T06:23:18",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"ernest22"
],
"id": "follow",
"json": "[\"reblog\",{\"account\":\"ernest22\",\"author\":\"zeenobit\",\"permlink\":\"quick-introduction-to-moving-averages\"}]"
}
]
}ernest22upvoted (100.00%) @zeenobit / quick-introduction-to-moving-averages2017/08/20 06:23:12
ernest22upvoted (100.00%) @zeenobit / quick-introduction-to-moving-averages
2017/08/20 06:23:12
| voter | ernest22 |
| author | zeenobit |
| permlink | quick-introduction-to-moving-averages |
| weight | 10000 (100.00%) |
| Transaction Info | Block #14732266/Trx b4c224c853daca98af4359d11ec689a3ff691f0a |
View Raw JSON Data
{
"trx_id": "b4c224c853daca98af4359d11ec689a3ff691f0a",
"block": 14732266,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-08-20T06:23:12",
"op": [
"vote",
{
"voter": "ernest22",
"author": "zeenobit",
"permlink": "quick-introduction-to-moving-averages",
"weight": 10000
}
]
}2017/08/04 05:16:54
2017/08/04 05:16:54
| delegator | steem |
| delegatee | ernest22 |
| vesting shares | 29941.369527 VESTS |
| Transaction Info | Block #14271417/Trx 8c9c83be9604ff05202cee13ef0e59e011cc1273 |
View Raw JSON Data
{
"trx_id": "8c9c83be9604ff05202cee13ef0e59e011cc1273",
"block": 14271417,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-08-04T05:16:54",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "ernest22",
"vesting_shares": "29941.369527 VESTS"
}
]
}ernest22custom json: follow2017/07/31 09:41:42
ernest22custom json: follow
2017/07/31 09:41:42
| required auths | [] |
| required posting auths | ["ernest22"] |
| id | follow |
| json | ["reblog",{"account":"ernest22","author":"lukeallison","permlink":"future-crypto-a-list-of-projects-with-purpose"}] |
| Transaction Info | Block #14161613/Trx 236c5170473fdf34601ccdf10aefc85ba1987994 |
View Raw JSON Data
{
"trx_id": "236c5170473fdf34601ccdf10aefc85ba1987994",
"block": 14161613,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-07-31T09:41:42",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"ernest22"
],
"id": "follow",
"json": "[\"reblog\",{\"account\":\"ernest22\",\"author\":\"lukeallison\",\"permlink\":\"future-crypto-a-list-of-projects-with-purpose\"}]"
}
]
}ernest22upvoted (100.00%) @lukeallison / future-crypto-a-list-of-projects-with-purpose2017/07/31 09:41:36
ernest22upvoted (100.00%) @lukeallison / future-crypto-a-list-of-projects-with-purpose
2017/07/31 09:41:36
| voter | ernest22 |
| author | lukeallison |
| permlink | future-crypto-a-list-of-projects-with-purpose |
| weight | 10000 (100.00%) |
| Transaction Info | Block #14161611/Trx 22c0adaa346eab46405f0c07a42466c00f87bd5e |
View Raw JSON Data
{
"trx_id": "22c0adaa346eab46405f0c07a42466c00f87bd5e",
"block": 14161611,
"trx_in_block": 19,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-07-31T09:41:36",
"op": [
"vote",
{
"voter": "ernest22",
"author": "lukeallison",
"permlink": "future-crypto-a-list-of-projects-with-purpose",
"weight": 10000
}
]
}ernest22removed vote from (0.00%) @ernest22 / xrp-great-upward-potential2017/07/18 14:28:03
ernest22removed vote from (0.00%) @ernest22 / xrp-great-upward-potential
2017/07/18 14:28:03
| voter | ernest22 |
| author | ernest22 |
| permlink | xrp-great-upward-potential |
| weight | 0 (0.00%) |
| Transaction Info | Block #13793190/Trx e7718ec5f42b08819d0c59adfc0e74f04e9c299a |
View Raw JSON Data
{
"trx_id": "e7718ec5f42b08819d0c59adfc0e74f04e9c299a",
"block": 13793190,
"trx_in_block": 16,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-07-18T14:28:03",
"op": [
"vote",
{
"voter": "ernest22",
"author": "ernest22",
"permlink": "xrp-great-upward-potential",
"weight": 0
}
]
}steeminator3000upvoted (100.00%) @ernest22 / coinsheet2017/07/18 14:26:18
steeminator3000upvoted (100.00%) @ernest22 / coinsheet
2017/07/18 14:26:18
| voter | steeminator3000 |
| author | ernest22 |
| permlink | coinsheet |
| weight | 10000 (100.00%) |
| Transaction Info | Block #13793155/Trx b517347ff237792604d1c34334eae29b8ee5ae83 |
View Raw JSON Data
{
"trx_id": "b517347ff237792604d1c34334eae29b8ee5ae83",
"block": 13793155,
"trx_in_block": 18,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-07-18T14:26:18",
"op": [
"vote",
{
"voter": "steeminator3000",
"author": "ernest22",
"permlink": "coinsheet",
"weight": 10000
}
]
}fixinpcs303upvoted (100.00%) @ernest22 / coinsheet2017/07/18 14:22:06
fixinpcs303upvoted (100.00%) @ernest22 / coinsheet
2017/07/18 14:22:06
| voter | fixinpcs303 |
| author | ernest22 |
| permlink | coinsheet |
| weight | 10000 (100.00%) |
| Transaction Info | Block #13793071/Trx 6065f9ccb1d9a4f4444c0195ad29ea37ab05d8db |
View Raw JSON Data
{
"trx_id": "6065f9ccb1d9a4f4444c0195ad29ea37ab05d8db",
"block": 13793071,
"trx_in_block": 16,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-07-18T14:22:06",
"op": [
"vote",
{
"voter": "fixinpcs303",
"author": "ernest22",
"permlink": "coinsheet",
"weight": 10000
}
]
}2017/07/18 14:18:48
2017/07/18 14:18:48
| parent author | |
| parent permlink | cryptocurrecny |
| author | ernest22 |
| permlink | coinsheet |
| title | CoinSheet |
| body | Check out Coinsheet for all of your daily crypto news !! https://www.coinsheet.org/?mwr=5038-2641a3bd |
| json metadata | {"tags":["cryptocurrecny"],"links":["https://www.coinsheet.org/?mwr=5038-2641a3bd"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #13793005/Trx e7d8387fd784312bb2e6b49383bf8c18c206b5aa |
View Raw JSON Data
{
"trx_id": "e7d8387fd784312bb2e6b49383bf8c18c206b5aa",
"block": 13793005,
"trx_in_block": 11,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-07-18T14:18:48",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "cryptocurrecny",
"author": "ernest22",
"permlink": "coinsheet",
"title": "CoinSheet",
"body": "Check out Coinsheet for all of your daily crypto news !!\n\nhttps://www.coinsheet.org/?mwr=5038-2641a3bd",
"json_metadata": "{\"tags\":[\"cryptocurrecny\"],\"links\":[\"https://www.coinsheet.org/?mwr=5038-2641a3bd\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}ernest22custom json: follow2017/07/17 05:21:00
ernest22custom json: follow
2017/07/17 05:21:00
| required auths | [] |
| required posting auths | ["ernest22"] |
| id | follow |
| json | ["reblog",{"account":"ernest22","author":"kurd","permlink":"how-to-trade-crypto-with-100x-the-amount-you-actually-own-leverage-trading-100x"}] |
| Transaction Info | Block #13753459/Trx 93909999fe5edd9c819e728e86cf9c5a8005091f |
View Raw JSON Data
{
"trx_id": "93909999fe5edd9c819e728e86cf9c5a8005091f",
"block": 13753459,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-07-17T05:21:00",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"ernest22"
],
"id": "follow",
"json": "[\"reblog\",{\"account\":\"ernest22\",\"author\":\"kurd\",\"permlink\":\"how-to-trade-crypto-with-100x-the-amount-you-actually-own-leverage-trading-100x\"}]"
}
]
}2017/07/17 05:16:33
2017/07/17 05:16:33
| voter | ernest22 |
| author | kurd |
| permlink | how-to-trade-crypto-with-100x-the-amount-you-actually-own-leverage-trading-100x |
| weight | 10000 (100.00%) |
| Transaction Info | Block #13753370/Trx 0568ec664fc199e8ab945fa3b249096e2f0a150a |
View Raw JSON Data
{
"trx_id": "0568ec664fc199e8ab945fa3b249096e2f0a150a",
"block": 13753370,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-07-17T05:16:33",
"op": [
"vote",
{
"voter": "ernest22",
"author": "kurd",
"permlink": "how-to-trade-crypto-with-100x-the-amount-you-actually-own-leverage-trading-100x",
"weight": 10000
}
]
}2017/07/09 00:49:06
2017/07/09 00:49:06
| voter | cooperpoole |
| author | ernest22 |
| permlink | re-cryptoindestment-building-my-mining-rig-part-1-construction-the-wooden-computer-20170627t145623289z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #13517913/Trx 5f2e5baea15fb0b84c985bb93ba45df414b058ae |
View Raw JSON Data
{
"trx_id": "5f2e5baea15fb0b84c985bb93ba45df414b058ae",
"block": 13517913,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-07-09T00:49:06",
"op": [
"vote",
{
"voter": "cooperpoole",
"author": "ernest22",
"permlink": "re-cryptoindestment-building-my-mining-rig-part-1-construction-the-wooden-computer-20170627t145623289z",
"weight": 10000
}
]
}2017/07/05 13:00:12
2017/07/05 13:00:12
| voter | ernest22 |
| author | crypt0 |
| permlink | metropolis-bringing-ethereum-to-the-masses-developers-jordi-baylina-griff-green-explain |
| weight | 10000 (100.00%) |
| Transaction Info | Block #13417843/Trx 1c1bce54d329f260fa843bb5eb8c5ec41cce7dab |
View Raw JSON Data
{
"trx_id": "1c1bce54d329f260fa843bb5eb8c5ec41cce7dab",
"block": 13417843,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-07-05T13:00:12",
"op": [
"vote",
{
"voter": "ernest22",
"author": "crypt0",
"permlink": "metropolis-bringing-ethereum-to-the-masses-developers-jordi-baylina-griff-green-explain",
"weight": 10000
}
]
}ernest22received 0.001 SP curation reward for @crypt0 / peyta-ransomware-demands-usd300-in-btc-china-fintech-framework-australia-japan-co-op-crypto-could-pass-5-4-trillion-marketcap2017/07/05 03:55:24
ernest22received 0.001 SP curation reward for @crypt0 / peyta-ransomware-demands-usd300-in-btc-china-fintech-framework-australia-japan-co-op-crypto-could-pass-5-4-trillion-marketcap
2017/07/05 03:55:24
| curator | ernest22 |
| reward | 2.068383 VESTS |
| comment author | crypt0 |
| comment permlink | peyta-ransomware-demands-usd300-in-btc-china-fintech-framework-australia-japan-co-op-crypto-could-pass-5-4-trillion-marketcap |
| Transaction Info | Block #13406952/Virtual Operation #178 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 13406952,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 178,
"timestamp": "2017-07-05T03:55:24",
"op": [
"curation_reward",
{
"curator": "ernest22",
"reward": "2.068383 VESTS",
"comment_author": "crypt0",
"comment_permlink": "peyta-ransomware-demands-usd300-in-btc-china-fintech-framework-australia-japan-co-op-crypto-could-pass-5-4-trillion-marketcap"
}
]
}ernest22received 0.045 SBD, 0.036 SP author reward for @ernest22 / re-cryptoindestment-building-my-mining-rig-part-1-construction-the-wooden-computer-20170627t145623289z2017/07/04 14:56:27
ernest22received 0.045 SBD, 0.036 SP author reward for @ernest22 / re-cryptoindestment-building-my-mining-rig-part-1-construction-the-wooden-computer-20170627t145623289z
2017/07/04 14:56:27
| author | ernest22 |
| permlink | re-cryptoindestment-building-my-mining-rig-part-1-construction-the-wooden-computer-20170627t145623289z |
| sbd payout | 0.045 SBD |
| steem payout | 0.000 STEEM |
| vesting payout | 57.916418 VESTS |
| Transaction Info | Block #13391387/Virtual Operation #3 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 13391387,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 3,
"timestamp": "2017-07-04T14:56:27",
"op": [
"author_reward",
{
"author": "ernest22",
"permlink": "re-cryptoindestment-building-my-mining-rig-part-1-construction-the-wooden-computer-20170627t145623289z",
"sbd_payout": "0.045 SBD",
"steem_payout": "0.000 STEEM",
"vesting_payout": "57.916418 VESTS"
}
]
}ernest22received 0.004 SP curation reward for @elton474 / re-cryptoindestment-building-my-mining-rig-part-1-construction-the-wooden-computer-20170627t143747615z2017/07/04 14:37:54
ernest22received 0.004 SP curation reward for @elton474 / re-cryptoindestment-building-my-mining-rig-part-1-construction-the-wooden-computer-20170627t143747615z
2017/07/04 14:37:54
| curator | ernest22 |
| reward | 6.205334 VESTS |
| comment author | elton474 |
| comment permlink | re-cryptoindestment-building-my-mining-rig-part-1-construction-the-wooden-computer-20170627t143747615z |
| Transaction Info | Block #13391016/Virtual Operation #10 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 13391016,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 10,
"timestamp": "2017-07-04T14:37:54",
"op": [
"curation_reward",
{
"curator": "ernest22",
"reward": "6.205334 VESTS",
"comment_author": "elton474",
"comment_permlink": "re-cryptoindestment-building-my-mining-rig-part-1-construction-the-wooden-computer-20170627t143747615z"
}
]
}ernest22received 0.005 SP curation reward for @goofyu / re-cryptoindestment-building-my-mining-rig-part-1-construction-the-wooden-computer-20170627t113005615z2017/07/04 11:30:06
ernest22received 0.005 SP curation reward for @goofyu / re-cryptoindestment-building-my-mining-rig-part-1-construction-the-wooden-computer-20170627t113005615z
2017/07/04 11:30:06
| curator | ernest22 |
| reward | 8.273837 VESTS |
| comment author | goofyu |
| comment permlink | re-cryptoindestment-building-my-mining-rig-part-1-construction-the-wooden-computer-20170627t113005615z |
| Transaction Info | Block #13387264/Virtual Operation #7 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 13387264,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 7,
"timestamp": "2017-07-04T11:30:06",
"op": [
"curation_reward",
{
"curator": "ernest22",
"reward": "8.273837 VESTS",
"comment_author": "goofyu",
"comment_permlink": "re-cryptoindestment-building-my-mining-rig-part-1-construction-the-wooden-computer-20170627t113005615z"
}
]
}ernest22upvoted (100.00%) @etcmike / genesis-mining-review-my-7-months-of-mining2017/07/03 11:15:21
ernest22upvoted (100.00%) @etcmike / genesis-mining-review-my-7-months-of-mining
2017/07/03 11:15:21
| voter | ernest22 |
| author | etcmike |
| permlink | genesis-mining-review-my-7-months-of-mining |
| weight | 10000 (100.00%) |
| Transaction Info | Block #13358196/Trx e1c4ab15aad85190b0037ce61296a73b42d6d7a1 |
View Raw JSON Data
{
"trx_id": "e1c4ab15aad85190b0037ce61296a73b42d6d7a1",
"block": 13358196,
"trx_in_block": 9,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-07-03T11:15:21",
"op": [
"vote",
{
"voter": "ernest22",
"author": "etcmike",
"permlink": "genesis-mining-review-my-7-months-of-mining",
"weight": 10000
}
]
}2017/07/03 06:17:51
2017/07/03 06:17:51
| parent author | ernest22 |
| parent permlink | xrp-great-upward-potential |
| author | steemitboard |
| permlink | steemitboard-notify-ernest22-20170703t061751000z |
| title | |
| body | Congratulations @ernest22! You have completed some achievement on Steemit and have been rewarded with new badge(s) : [](http://steemitboard.com/@ernest22) You published your First Post Click on any badge to view your own Board of Honnor 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` By upvoting this notification, you can help all Steemit users. Learn how [here](https://steemit.com/steemitboard/@steemitboard/http-i-cubeupload-com-7ciqeo-png)! |
| json metadata | {"image":["https://steemitboard.com/img/notifications.png"]} |
| Transaction Info | Block #13352252/Trx e8f309f44931f9ebdb9fa367bc5da4438e0c3bab |
View Raw JSON Data
{
"trx_id": "e8f309f44931f9ebdb9fa367bc5da4438e0c3bab",
"block": 13352252,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-07-03T06:17:51",
"op": [
"comment",
{
"parent_author": "ernest22",
"parent_permlink": "xrp-great-upward-potential",
"author": "steemitboard",
"permlink": "steemitboard-notify-ernest22-20170703t061751000z",
"title": "",
"body": "Congratulations @ernest22! You have completed some achievement on Steemit and have been rewarded with new badge(s) :\n\n[](http://steemitboard.com/@ernest22) You published your First Post\n\nClick on any badge to view your own Board of Honnor 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\nBy upvoting this notification, you can help all Steemit users. Learn how [here](https://steemit.com/steemitboard/@steemitboard/http-i-cubeupload-com-7ciqeo-png)!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notifications.png\"]}"
}
]
}ernest22published a new post: xrp-great-upward-potential2017/07/03 03:56:33
ernest22published a new post: xrp-great-upward-potential
2017/07/03 03:56:33
| parent author | |
| parent permlink | cryptocurrecny |
| author | ernest22 |
| permlink | xrp-great-upward-potential |
| title | Ripple XRP great upward potential |
| body | https://www.tradingview.com/chart/XRPBTC/iETuxvdy-XRP-LONG/ XRP/BTC hasnt change that much in recent days but XRP/USDT is growing with the BTC/USDT recovery. When the XRP/USDT really breaks out from the triangle, there is a high chance of XRP/BTC having a huge pump too. Be prepare to trade some XRP when the breakout happens! |
| json metadata | {"tags":["cryptocurrecny","trading","ripple","xrp"],"links":["https://www.tradingview.com/chart/XRPBTC/iETuxvdy-XRP-LONG/"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #13349429/Trx 8e318b24354d9ff8f815138b35249dd148023d19 |
View Raw JSON Data
{
"trx_id": "8e318b24354d9ff8f815138b35249dd148023d19",
"block": 13349429,
"trx_in_block": 18,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-07-03T03:56:33",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "cryptocurrecny",
"author": "ernest22",
"permlink": "xrp-great-upward-potential",
"title": "Ripple XRP great upward potential",
"body": "https://www.tradingview.com/chart/XRPBTC/iETuxvdy-XRP-LONG/\n\nXRP/BTC hasnt change that much in recent days but XRP/USDT is growing with the BTC/USDT recovery. When the XRP/USDT really breaks out from the triangle, there is a high chance of XRP/BTC having a huge pump too. Be prepare to trade some XRP when the breakout happens!",
"json_metadata": "{\"tags\":[\"cryptocurrecny\",\"trading\",\"ripple\",\"xrp\"],\"links\":[\"https://www.tradingview.com/chart/XRPBTC/iETuxvdy-XRP-LONG/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}ernest22published a new post: xrp-great-upward-potential2017/07/03 03:54:09
ernest22published a new post: xrp-great-upward-potential
2017/07/03 03:54:09
| parent author | |
| parent permlink | cryptocurrecny |
| author | ernest22 |
| permlink | xrp-great-upward-potential |
| title | Ripple XRP great upward potential |
| body | https://www.tradingview.com/chart/XRPBTC/iETuxvdy-XRP-LONG/ XRP/BTC hasnt change that much in recent days but XRP/USDT is growing with the BTC/USDT recovery. When the XRP/USDT really breaks out from the triangle, there is a high chance of XRP/BTC having a huge pump too. Be prepare to trade some XRP when the breakout happens! |
| json metadata | {"tags":["cryptocurrecny","trading","ripple","xrp"],"links":["https://www.tradingview.com/chart/XRPBTC/iETuxvdy-XRP-LONG/"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #13349381/Trx 74b66c9098b772695959744389891eba9e07c4cd |
View Raw JSON Data
{
"trx_id": "74b66c9098b772695959744389891eba9e07c4cd",
"block": 13349381,
"trx_in_block": 14,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-07-03T03:54:09",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "cryptocurrecny",
"author": "ernest22",
"permlink": "xrp-great-upward-potential",
"title": "Ripple XRP great upward potential",
"body": "https://www.tradingview.com/chart/XRPBTC/iETuxvdy-XRP-LONG/\n\nXRP/BTC hasnt change that much in recent days but XRP/USDT is growing with the BTC/USDT recovery. When the XRP/USDT really breaks out from the triangle, there is a high chance of XRP/BTC having a huge pump too. Be prepare to trade some XRP when the breakout happens!",
"json_metadata": "{\"tags\":[\"cryptocurrecny\",\"trading\",\"ripple\",\"xrp\"],\"links\":[\"https://www.tradingview.com/chart/XRPBTC/iETuxvdy-XRP-LONG/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}ernest22upvoted (100.00%) @ernest22 / xrp-great-upward-potential2017/07/03 03:53:42
ernest22upvoted (100.00%) @ernest22 / xrp-great-upward-potential
2017/07/03 03:53:42
| voter | ernest22 |
| author | ernest22 |
| permlink | xrp-great-upward-potential |
| weight | 10000 (100.00%) |
| Transaction Info | Block #13349372/Trx 4063a55984522de0015b993829c2d9891548bbea |
View Raw JSON Data
{
"trx_id": "4063a55984522de0015b993829c2d9891548bbea",
"block": 13349372,
"trx_in_block": 21,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-07-03T03:53:42",
"op": [
"vote",
{
"voter": "ernest22",
"author": "ernest22",
"permlink": "xrp-great-upward-potential",
"weight": 10000
}
]
}ernest22published a new post: xrp-great-upward-potential2017/07/03 03:53:42
ernest22published a new post: xrp-great-upward-potential
2017/07/03 03:53:42
| parent author | |
| parent permlink | cryptocurrecny |
| author | ernest22 |
| permlink | xrp-great-upward-potential |
| title | XRP great upward potential |
| body | https://www.tradingview.com/chart/XRPBTC/iETuxvdy-XRP-LONG/ XRP/BTC hasnt change that much in recent days but XRP/USDT is growing with the BTC/USDT recovery. When the XRP/USDT really breaks out from the triangle, there is a high chance of XRP/BTC having a huge pump too. Be prepare to trade some XRP when the breakout happens! |
| json metadata | {"tags":["cryptocurrecny","trading","ripple","xrp"],"links":["https://www.tradingview.com/chart/XRPBTC/iETuxvdy-XRP-LONG/"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #13349372/Trx 4063a55984522de0015b993829c2d9891548bbea |
View Raw JSON Data
{
"trx_id": "4063a55984522de0015b993829c2d9891548bbea",
"block": 13349372,
"trx_in_block": 21,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-07-03T03:53:42",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "cryptocurrecny",
"author": "ernest22",
"permlink": "xrp-great-upward-potential",
"title": "XRP great upward potential",
"body": "https://www.tradingview.com/chart/XRPBTC/iETuxvdy-XRP-LONG/\n\nXRP/BTC hasnt change that much in recent days but XRP/USDT is growing with the BTC/USDT recovery. When the XRP/USDT really breaks out from the triangle, there is a high chance of XRP/BTC having a huge pump too. Be prepare to trade some XRP when the breakout happens!",
"json_metadata": "{\"tags\":[\"cryptocurrecny\",\"trading\",\"ripple\",\"xrp\"],\"links\":[\"https://www.tradingview.com/chart/XRPBTC/iETuxvdy-XRP-LONG/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}ernest22upvoted (100.00%) @cryptowallet / steemit-trend2017/07/01 15:51:15
ernest22upvoted (100.00%) @cryptowallet / steemit-trend
2017/07/01 15:51:15
| voter | ernest22 |
| author | cryptowallet |
| permlink | steemit-trend |
| weight | 10000 (100.00%) |
| Transaction Info | Block #13306133/Trx ac570a19daa19efe08890d172b86cd71f31d4333 |
View Raw JSON Data
{
"trx_id": "ac570a19daa19efe08890d172b86cd71f31d4333",
"block": 13306133,
"trx_in_block": 13,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-07-01T15:51:15",
"op": [
"vote",
{
"voter": "ernest22",
"author": "cryptowallet",
"permlink": "steemit-trend",
"weight": 10000
}
]
}ernest22custom json: follow2017/07/01 14:29:45
ernest22custom json: follow
2017/07/01 14:29:45
| required auths | [] |
| required posting auths | ["ernest22"] |
| id | follow |
| json | ["reblog",{"account":"ernest22","author":"thechartguys","permlink":"video-bitcoin-ethereum-litecoin-golem-technical-analysis-chart-6-30-2017"}] |
| Transaction Info | Block #13304506/Trx f92e7805f4cad8e02a2b0e0cc5f2b792dabb7b29 |
View Raw JSON Data
{
"trx_id": "f92e7805f4cad8e02a2b0e0cc5f2b792dabb7b29",
"block": 13304506,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-07-01T14:29:45",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"ernest22"
],
"id": "follow",
"json": "[\"reblog\",{\"account\":\"ernest22\",\"author\":\"thechartguys\",\"permlink\":\"video-bitcoin-ethereum-litecoin-golem-technical-analysis-chart-6-30-2017\"}]"
}
]
}2017/07/01 14:29:42
2017/07/01 14:29:42
| voter | ernest22 |
| author | thechartguys |
| permlink | video-bitcoin-ethereum-litecoin-golem-technical-analysis-chart-6-30-2017 |
| weight | 10000 (100.00%) |
| Transaction Info | Block #13304505/Trx a19780cc96d8a610914c190c7ac45f3a92774994 |
View Raw JSON Data
{
"trx_id": "a19780cc96d8a610914c190c7ac45f3a92774994",
"block": 13304505,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-07-01T14:29:42",
"op": [
"vote",
{
"voter": "ernest22",
"author": "thechartguys",
"permlink": "video-bitcoin-ethereum-litecoin-golem-technical-analysis-chart-6-30-2017",
"weight": 10000
}
]
}Manabar
Voting Power100.00%
Downvote Power100.00%
Resource Credits100.00%
Reputation Progress0.00%
{
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779062595
},
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779062595
},
"rc_account": {
"account": "ernest22",
"rc_manabar": {
"current_mana": "10164408779",
"last_update_time": 1779062595
},
"max_rc_creation_adjustment": {
"amount": "2020748973",
"precision": 6,
"nai": "@@000000037"
},
"max_rc": "10164408779"
}
}Account Metadata
| POSTING JSON METADATA | |
| profile | {"about":"Crypto Trader/ Miner","location":"Hong Kong","name":"Ernest Lau","profile_image":"https://blogs-images.forbes.com/erikkain/files/2015/08/dishonored.jpg"} |
| JSON METADATA | |
| profile | {"about":"Crypto Trader/ Miner","location":"Hong Kong","name":"Ernest Lau","profile_image":"https://blogs-images.forbes.com/erikkain/files/2015/08/dishonored.jpg"} |
{
"posting_json_metadata": {
"profile": {
"about": "Crypto Trader/ Miner",
"location": "Hong Kong",
"name": "Ernest Lau",
"profile_image": "https://blogs-images.forbes.com/erikkain/files/2015/08/dishonored.jpg"
}
},
"json_metadata": {
"profile": {
"about": "Crypto Trader/ Miner",
"location": "Hong Kong",
"name": "Ernest Lau",
"profile_image": "https://blogs-images.forbes.com/erikkain/files/2015/08/dishonored.jpg"
}
}
}Auth Keys
Owner
Single Signature
Public Keys
STM6eTYiUMttwHSxeHoBFo2kohYWFXeKycMXEzEARMdWrChNFgnvi1/1
Active
Single Signature
Public Keys
STM5DvhLRtRmP2sFxHKUwjWtKhGjan7fXyz4Lf9kc1N9BGeMdLfqA1/1
Posting
Single Signature
Public Keys
STM5YgkK1r9eheU1reGfg5V3bYBkmmLQ6mum1VfiTGuEwQUJt6Gzu1/1
Memo
STM7MGV7adEkrJRx6kCCenm9o5C95RbJGJEd6m3MEhVU7NaidUW4n
{
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM6eTYiUMttwHSxeHoBFo2kohYWFXeKycMXEzEARMdWrChNFgnvi",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5DvhLRtRmP2sFxHKUwjWtKhGjan7fXyz4Lf9kc1N9BGeMdLfqA",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5YgkK1r9eheU1reGfg5V3bYBkmmLQ6mum1VfiTGuEwQUJt6Gzu",
1
]
]
},
"memo": "STM7MGV7adEkrJRx6kCCenm9o5C95RbJGJEd6m3MEhVU7NaidUW4n"
}Witness Votes
0 / 30
No active witness votes.
[]