VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS0.00%
Net Worth
0.014USD
STEEM
0.001STEEM
SBD
0.015SBD
Effective Power
5.001SP
├── Own SP
0.125SP
└── Incoming DelegationsDeleg
+4.876SP
Detailed Balance
| STEEM | ||
| balance | 0.001STEEM | STEEM |
| market_balance | 0.000STEEM | STEEM |
| savings_balance | 0.000STEEM | STEEM |
| reward_steem_balance | 0.000STEEM | STEEM |
| STEEM POWER | ||
| Own SP | 0.125SP | SP |
| Delegated Out | 0.000SP | SP |
| Delegation In | 4.876SP | SP |
| Effective Power | 5.001SP | SP |
| Reward SP (pending) | 0.007SP | SP |
| SBD | ||
| sbd_balance | 0.000SBD | SBD |
| sbd_conversions | 0.000SBD | SBD |
| sbd_market_balance | 0.000SBD | SBD |
| savings_sbd_balance | 0.000SBD | SBD |
| reward_sbd_balance | 0.015SBD | SBD |
{
"balance": "0.001 STEEM",
"savings_balance": "0.000 STEEM",
"reward_steem_balance": "0.000 STEEM",
"vesting_shares": "204.169953 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "7939.489853 VESTS",
"sbd_balance": "0.000 SBD",
"savings_sbd_balance": "0.000 SBD",
"reward_sbd_balance": "0.015 SBD",
"conversions": []
}Account Info
| name | guesshu |
| id | 850633 |
| rank | 293,794 |
| reputation | 253117884 |
| created | 2018-03-13T11:32:27 |
| recovery_account | steem |
| proxy | None |
| post_count | 5 |
| comment_count | 0 |
| lifetime_vote_count | 0 |
| witnesses_voted_for | 0 |
| last_post | 2019-11-17T08:36:03 |
| last_root_post | 2019-11-17T08:36:03 |
| last_vote_time | 2018-04-15T13:24:06 |
| proxied_vsf_votes | 0, 0, 0, 0 |
| can_vote | 1 |
| voting_power | 0 |
| delayed_votes | 0 |
| balance | 0.001 STEEM |
| savings_balance | 0.000 STEEM |
| sbd_balance | 0.000 SBD |
| savings_sbd_balance | 0.000 SBD |
| vesting_shares | 204.169953 VESTS |
| delegated_vesting_shares | 0.000000 VESTS |
| received_vesting_shares | 7939.489853 VESTS |
| reward_vesting_balance | 14.266608 VESTS |
| vesting_balance | 0.000 STEEM |
| vesting_withdraw_rate | 0.000000 VESTS |
| next_vesting_withdrawal | 1969-12-31T23:59:59 |
| withdrawn | 0 |
| to_withdraw | 0 |
| withdraw_routes | 0 |
| savings_withdraw_requests | 0 |
| last_account_recovery | 1970-01-01T00:00:00 |
| reset_account | null |
| last_owner_update | 1970-01-01T00:00:00 |
| last_account_update | 1970-01-01T00:00:00 |
| mined | No |
| sbd_seconds | 0 |
| sbd_last_interest_payment | 1970-01-01T00:00:00 |
| savings_sbd_last_interest_payment | 1970-01-01T00:00:00 |
{
"id": 850633,
"name": "guesshu",
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7UJ1bARAvyZKtv5o8i7vCUg1omHMTD4ivwCZXVdwVXS1yqh1SB",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5YZcgdwKiZDrwgdGkpShFx1ThBthu5iGkEa89VXginbC1ckLVG",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7sUoVyFS5scdHkrqq2jzaoP9NWcbxUAzw7xRqKZbz8tg6663kr",
1
]
]
},
"memo_key": "STM6v49C9XbNxDEpSocK16s1GrDqfZ8CU7nfbsAnKrBjjDPr9V8DA",
"json_metadata": "{}",
"posting_json_metadata": "",
"proxy": "",
"last_owner_update": "1970-01-01T00:00:00",
"last_account_update": "1970-01-01T00:00:00",
"created": "2018-03-13T11:32:27",
"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": 5,
"can_vote": true,
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779065499
},
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779065499
},
"voting_power": 0,
"balance": "0.001 STEEM",
"savings_balance": "0.000 STEEM",
"sbd_balance": "0.000 SBD",
"sbd_seconds": "0",
"sbd_seconds_last_update": "1970-01-01T00:00:00",
"sbd_last_interest_payment": "1970-01-01T00:00:00",
"savings_sbd_balance": "0.000 SBD",
"savings_sbd_seconds": "0",
"savings_sbd_seconds_last_update": "1970-01-01T00:00:00",
"savings_sbd_last_interest_payment": "1970-01-01T00:00:00",
"savings_withdraw_requests": 0,
"reward_sbd_balance": "0.015 SBD",
"reward_steem_balance": "0.000 STEEM",
"reward_vesting_balance": "14.266608 VESTS",
"reward_vesting_steem": "0.007 STEEM",
"vesting_shares": "204.169953 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "7939.489853 VESTS",
"vesting_withdraw_rate": "0.000000 VESTS",
"next_vesting_withdrawal": "1969-12-31T23:59:59",
"withdrawn": 0,
"to_withdraw": 0,
"withdraw_routes": 0,
"curation_rewards": 0,
"posting_rewards": 13,
"proxied_vsf_votes": [
0,
0,
0,
0
],
"witnesses_voted_for": 0,
"last_post": "2019-11-17T08:36:03",
"last_root_post": "2019-11-17T08:36:03",
"last_vote_time": "2018-04-15T13:24:06",
"post_bandwidth": 0,
"pending_claimed_accounts": 0,
"vesting_balance": "0.000 STEEM",
"reputation": 253117884,
"transfer_history": [],
"market_history": [],
"post_history": [],
"vote_history": [],
"other_history": [],
"witness_votes": [],
"tags_usage": [],
"guest_bloggers": [],
"rank": 293794
}Withdraw Routes
| Incoming | Outgoing |
|---|---|
Empty | Empty |
{
"incoming": [],
"outgoing": []
}From Date
To Date
2026/05/18 00:51:39
2026/05/18 00:51:39
| delegator | steem |
| delegatee | guesshu |
| vesting shares | 7939.489853 VESTS |
| Transaction Info | Block #106144175/Trx b136ca83ba01750381f22ce1af9873332eb88281 |
View Raw JSON Data
{
"trx_id": "b136ca83ba01750381f22ce1af9873332eb88281",
"block": 106144175,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-05-18T00:51:39",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "guesshu",
"vesting_shares": "7939.489853 VESTS"
}
]
}2026/05/12 06:17:45
2026/05/12 06:17:45
| delegator | steem |
| delegatee | guesshu |
| vesting shares | 5227.279448 VESTS |
| Transaction Info | Block #105978650/Trx 3c02b973b13b2f5aa4a091194c5901907538f112 |
View Raw JSON Data
{
"trx_id": "3c02b973b13b2f5aa4a091194c5901907538f112",
"block": 105978650,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-05-12T06:17:45",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "guesshu",
"vesting_shares": "5227.279448 VESTS"
}
]
}2026/04/26 00:11:36
2026/04/26 00:11:36
| delegator | steem |
| delegatee | guesshu |
| vesting shares | 7952.005609 VESTS |
| Transaction Info | Block #105511810/Trx 061ee3e846c9daaca1b5a3ebbcb15fe2f9c4542b |
View Raw JSON Data
{
"trx_id": "061ee3e846c9daaca1b5a3ebbcb15fe2f9c4542b",
"block": 105511810,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-04-26T00:11:36",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "guesshu",
"vesting_shares": "7952.005609 VESTS"
}
]
}2026/01/23 09:25:27
2026/01/23 09:25:27
| delegator | steem |
| delegatee | guesshu |
| vesting shares | 5268.826267 VESTS |
| Transaction Info | Block #102853755/Trx 88e6d98562475581d52273e5a9fbdeffec99076f |
View Raw JSON Data
{
"trx_id": "88e6d98562475581d52273e5a9fbdeffec99076f",
"block": 102853755,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-01-23T09:25:27",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "guesshu",
"vesting_shares": "5268.826267 VESTS"
}
]
}2024/12/17 04:43:45
2024/12/17 04:43:45
| delegator | steem |
| delegatee | guesshu |
| vesting shares | 5433.045464 VESTS |
| Transaction Info | Block #91300142/Trx e4b43d225f3854271a3c1b88bd2cd9a90dfbe0fe |
View Raw JSON Data
{
"trx_id": "e4b43d225f3854271a3c1b88bd2cd9a90dfbe0fe",
"block": 91300142,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2024-12-17T04:43:45",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "guesshu",
"vesting_shares": "5433.045464 VESTS"
}
]
}2023/11/13 20:26:30
2023/11/13 20:26:30
| delegator | steem |
| delegatee | guesshu |
| vesting shares | 5602.178996 VESTS |
| Transaction Info | Block #79854340/Trx 1b83fc59f8c63d2909f7585da65d0909f3289499 |
View Raw JSON Data
{
"trx_id": "1b83fc59f8c63d2909f7585da65d0909f3289499",
"block": 79854340,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2023-11-13T20:26:30",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "guesshu",
"vesting_shares": "5602.178996 VESTS"
}
]
}2023/09/21 22:32:27
2023/09/21 22:32:27
| delegator | steem |
| delegatee | guesshu |
| vesting shares | 8539.457782 VESTS |
| Transaction Info | Block #78348679/Trx 4774f3cc9d5dd33ebaf17fd3a6e92601eeab3ad1 |
View Raw JSON Data
{
"trx_id": "4774f3cc9d5dd33ebaf17fd3a6e92601eeab3ad1",
"block": 78348679,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2023-09-21T22:32:27",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "guesshu",
"vesting_shares": "8539.457782 VESTS"
}
]
}2022/11/03 12:14:48
2022/11/03 12:14:48
| delegator | steem |
| delegatee | guesshu |
| vesting shares | 8761.139220 VESTS |
| Transaction Info | Block #69113911/Trx 6513b831d14dcd4e3ab11b17d9b26c9e8b3b2bfd |
View Raw JSON Data
{
"trx_id": "6513b831d14dcd4e3ab11b17d9b26c9e8b3b2bfd",
"block": 69113911,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2022-11-03T12:14:48",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "guesshu",
"vesting_shares": "8761.139220 VESTS"
}
]
}2022/01/17 11:28:06
2022/01/17 11:28:06
| delegator | steem |
| delegatee | guesshu |
| vesting shares | 8981.672451 VESTS |
| Transaction Info | Block #60810026/Trx 6d3cc2373454d61f720110183b6b93ea0b608a22 |
View Raw JSON Data
{
"trx_id": "6d3cc2373454d61f720110183b6b93ea0b608a22",
"block": 60810026,
"trx_in_block": 16,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2022-01-17T11:28:06",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "guesshu",
"vesting_shares": "8981.672451 VESTS"
}
]
}2021/06/14 01:22:00
2021/06/14 01:22:00
| delegator | steem |
| delegatee | guesshu |
| vesting shares | 9165.441109 VESTS |
| Transaction Info | Block #54608384/Trx a3637ee0b876e70a460fb919afd1e844a7d9e8ed |
View Raw JSON Data
{
"trx_id": "a3637ee0b876e70a460fb919afd1e844a7d9e8ed",
"block": 54608384,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2021-06-14T01:22:00",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "guesshu",
"vesting_shares": "9165.441109 VESTS"
}
]
}2020/12/11 11:40:00
2020/12/11 11:40:00
| delegator | steem |
| delegatee | guesshu |
| vesting shares | 9352.863083 VESTS |
| Transaction Info | Block #49355820/Trx 8f0d141ee490a86bdc7714a1f5fe357f7c6721e0 |
View Raw JSON Data
{
"trx_id": "8f0d141ee490a86bdc7714a1f5fe357f7c6721e0",
"block": 49355820,
"trx_in_block": 13,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-12-11T11:40:00",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "guesshu",
"vesting_shares": "9352.863083 VESTS"
}
]
}2020/12/06 05:17:06
2020/12/06 05:17:06
| delegator | steem |
| delegatee | guesshu |
| vesting shares | 1912.543513 VESTS |
| Transaction Info | Block #49207379/Trx ccb32d696bad52b8333e38430990810bfea2fa1f |
View Raw JSON Data
{
"trx_id": "ccb32d696bad52b8333e38430990810bfea2fa1f",
"block": 49207379,
"trx_in_block": 8,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-12-06T05:17:06",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "guesshu",
"vesting_shares": "1912.543513 VESTS"
}
]
}2020/12/05 15:18:00
2020/12/05 15:18:00
| delegator | steem |
| delegatee | guesshu |
| vesting shares | 9359.070937 VESTS |
| Transaction Info | Block #49190912/Trx 12e496f611af89b818896f453e3716c976a9d787 |
View Raw JSON Data
{
"trx_id": "12e496f611af89b818896f453e3716c976a9d787",
"block": 49190912,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-12-05T15:18:00",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "guesshu",
"vesting_shares": "9359.070937 VESTS"
}
]
}2020/11/02 16:45:54
2020/11/02 16:45:54
| delegator | steem |
| delegatee | guesshu |
| vesting shares | 1920.017158 VESTS |
| Transaction Info | Block #48259126/Trx 1a67b0dcf5f47786821ddb53dc169af4aafa576d |
View Raw JSON Data
{
"trx_id": "1a67b0dcf5f47786821ddb53dc169af4aafa576d",
"block": 48259126,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-11-02T16:45:54",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "guesshu",
"vesting_shares": "1920.017158 VESTS"
}
]
}2020/05/09 06:15:06
2020/05/09 06:15:06
| delegator | steem |
| delegatee | guesshu |
| vesting shares | 9561.876296 VESTS |
| Transaction Info | Block #43217638/Trx 5404353bcffc160f2d83e24ed96ecf5024d3f1d0 |
View Raw JSON Data
{
"trx_id": "5404353bcffc160f2d83e24ed96ecf5024d3f1d0",
"block": 43217638,
"trx_in_block": 9,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-05-09T06:15:06",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "guesshu",
"vesting_shares": "9561.876296 VESTS"
}
]
}2020/05/08 09:56:15
2020/05/08 09:56:15
| delegator | steem |
| delegatee | guesshu |
| vesting shares | 1953.311140 VESTS |
| Transaction Info | Block #43193831/Trx 7a05e8d274867059b049897364557f4dbd867027 |
View Raw JSON Data
{
"trx_id": "7a05e8d274867059b049897364557f4dbd867027",
"block": 43193831,
"trx_in_block": 28,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-05-08T09:56:15",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "guesshu",
"vesting_shares": "1953.311140 VESTS"
}
]
}2020/03/13 12:08:03
2020/03/13 12:08:03
| parent author | guesshu |
| parent permlink | benckmarking-the-known-problem-of-blocking-json-stringify-a-common-bottleneck-for-nodejs-programs |
| author | steemitboard |
| permlink | steemitboard-notify-guesshu-20200313t120802000z |
| title | |
| body | Congratulations @guesshu! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@guesshu/birthday2.png</td><td>Happy Steem 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/@guesshu) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=guesshu)_</sub> **Do not miss the last post from @steemitboard:** <table><tr><td><a href="https://steemit.com/steemitboard/@steemitboard/downvote-challenge-add-up-to-3-funny-badges-to-your-board"><img src="https://steemitimages.com/64x128/https://steemitimages.com/0x0/"></a></td><td><a href="https://steemit.com/steemitboard/@steemitboard/downvote-challenge-add-up-to-3-funny-badges-to-your-board">Downvote challenge - Add up to 3 funny badges to your board</a></td></tr></table> ###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| Transaction Info | Block #41615245/Trx e8dd4b85cb20639d224e902e75bdecadea79dc5e |
View Raw JSON Data
{
"trx_id": "e8dd4b85cb20639d224e902e75bdecadea79dc5e",
"block": 41615245,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-03-13T12:08:03",
"op": [
"comment",
{
"parent_author": "guesshu",
"parent_permlink": "benckmarking-the-known-problem-of-blocking-json-stringify-a-common-bottleneck-for-nodejs-programs",
"author": "steemitboard",
"permlink": "steemitboard-notify-guesshu-20200313t120802000z",
"title": "",
"body": "Congratulations @guesshu! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@guesshu/birthday2.png</td><td>Happy Steem 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/@guesshu) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=guesshu)_</sub>\n\n\n**Do not miss the last post from @steemitboard:**\n<table><tr><td><a href=\"https://steemit.com/steemitboard/@steemitboard/downvote-challenge-add-up-to-3-funny-badges-to-your-board\"><img src=\"https://steemitimages.com/64x128/https://steemitimages.com/0x0/\"></a></td><td><a href=\"https://steemit.com/steemitboard/@steemitboard/downvote-challenge-add-up-to-3-funny-badges-to-your-board\">Downvote challenge - Add up to 3 funny badges to your board</a></td></tr></table>\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}"
}
]
}2020/02/16 10:00:27
2020/02/16 10:00:27
| delegator | steem |
| delegatee | guesshu |
| vesting shares | 9605.350277 VESTS |
| Transaction Info | Block #40866453/Trx 3373b11e161acbc5f6799dc6f61d4633adcb3f37 |
View Raw JSON Data
{
"trx_id": "3373b11e161acbc5f6799dc6f61d4633adcb3f37",
"block": 40866453,
"trx_in_block": 31,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-02-16T10:00:27",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "guesshu",
"vesting_shares": "9605.350277 VESTS"
}
]
}2019/11/17 09:51:39
2019/11/17 09:51:39
| delegator | steem |
| delegatee | guesshu |
| vesting shares | 29486.722890 VESTS |
| Transaction Info | Block #38250489/Trx cb4b5408763c33d69798ebc406f7157b6b90d3fe |
View Raw JSON Data
{
"trx_id": "cb4b5408763c33d69798ebc406f7157b6b90d3fe",
"block": 38250489,
"trx_in_block": 10,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-11-17T09:51:39",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "guesshu",
"vesting_shares": "29486.722890 VESTS"
}
]
}2019/11/17 08:37:51
2019/11/17 08:37:51
| parent author | |
| parent permlink | nodejs |
| author | guesshu |
| permlink | benckmarking-the-known-problem-of-blocking-json-stringify-a-common-bottleneck-for-nodejs-programs |
| title | benckmarking the known problem of blocking JSON.stringify, a common bottleneck for NodeJS programs |
| body | @@ -48,16 +48,73 @@ tives.%0A%0A +use code from https://github.com/CLDH214/cpu-benchmark.%0A%0A A 524.28 |
| json metadata | {"tags":["json","cpu","programming","stringify","software","performance"],"app":"steemit/0.1","format":"markdown","links":["https://github.com/CLDH214/cpu-benchmark"]} |
| Transaction Info | Block #38249014/Trx d3899d7a29fc7c6335887630fdbbf9b64d62bab9 |
View Raw JSON Data
{
"trx_id": "d3899d7a29fc7c6335887630fdbbf9b64d62bab9",
"block": 38249014,
"trx_in_block": 21,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-11-17T08:37:51",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "nodejs",
"author": "guesshu",
"permlink": "benckmarking-the-known-problem-of-blocking-json-stringify-a-common-bottleneck-for-nodejs-programs",
"title": "benckmarking the known problem of blocking JSON.stringify, a common bottleneck for NodeJS programs",
"body": "@@ -48,16 +48,73 @@\n tives.%0A%0A\n+use code from https://github.com/CLDH214/cpu-benchmark.%0A%0A\n A 524.28\n",
"json_metadata": "{\"tags\":[\"json\",\"cpu\",\"programming\",\"stringify\",\"software\",\"performance\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\",\"links\":[\"https://github.com/CLDH214/cpu-benchmark\"]}"
}
]
}2019/11/17 08:37:03
2019/11/17 08:37:03
| from | steembeem |
| to | guesshu |
| amount | 0.001 STEEM |
| memo | ✨ Awesome Auto-Boost Service, with only 1 STEEM per month get all your posts automatically Fully Upvoted! Just send a 1 STEEM with memo 'subscribe', don't be late! find out more on http://www.steembeem.com |
| Transaction Info | Block #38248998/Trx cae81ac2946e707fb14140c6751b9cc8683a0c2a |
View Raw JSON Data
{
"trx_id": "cae81ac2946e707fb14140c6751b9cc8683a0c2a",
"block": 38248998,
"trx_in_block": 10,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-11-17T08:37:03",
"op": [
"transfer",
{
"from": "steembeem",
"to": "guesshu",
"amount": "0.001 STEEM",
"memo": "✨ Awesome Auto-Boost Service, with only 1 STEEM per month get all your posts automatically Fully Upvoted! Just send a 1 STEEM with memo 'subscribe', don't be late! find out more on http://www.steembeem.com"
}
]
}2019/11/17 08:37:00
2019/11/17 08:37:00
| voter | laissez-faire |
| author | guesshu |
| permlink | benckmarking-the-known-problem-of-blocking-json-stringify-a-common-bottleneck-for-nodejs-programs |
| weight | 10000 (100.00%) |
| Transaction Info | Block #38248997/Trx d684a4ca6a136e61a075c640793eff442b36e2be |
View Raw JSON Data
{
"trx_id": "d684a4ca6a136e61a075c640793eff442b36e2be",
"block": 38248997,
"trx_in_block": 25,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-11-17T08:37:00",
"op": [
"vote",
{
"voter": "laissez-faire",
"author": "guesshu",
"permlink": "benckmarking-the-known-problem-of-blocking-json-stringify-a-common-bottleneck-for-nodejs-programs",
"weight": 10000
}
]
}2019/11/17 08:36:57
2019/11/17 08:36:57
| voter | anomaly |
| author | guesshu |
| permlink | benckmarking-the-known-problem-of-blocking-json-stringify-a-common-bottleneck-for-nodejs-programs |
| weight | 100 (1.00%) |
| Transaction Info | Block #38248996/Trx f717052546a9c0891089112dc6bc434471c48773 |
View Raw JSON Data
{
"trx_id": "f717052546a9c0891089112dc6bc434471c48773",
"block": 38248996,
"trx_in_block": 17,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-11-17T08:36:57",
"op": [
"vote",
{
"voter": "anomaly",
"author": "guesshu",
"permlink": "benckmarking-the-known-problem-of-blocking-json-stringify-a-common-bottleneck-for-nodejs-programs",
"weight": 100
}
]
}2019/11/17 08:36:03
2019/11/17 08:36:03
| parent author | |
| parent permlink | nodejs |
| author | guesshu |
| permlink | benckmarking-the-known-problem-of-blocking-json-stringify-a-common-bottleneck-for-nodejs-programs |
| title | benckmarking the known problem of blocking JSON.stringify, a common bottleneck for NodeJS programs |
| body | cpu benchmark on JSON.stringify and its alternatives. A 524.288019 MB JSON string takes up to 100% CPU on my 3.5 GHz Quad-Core Intel Core i5 when it is being stringified with `JSON.stringify`. A half sized (209.715219 MB) JSON string takes up to 100% CPU with the yieldable-json library too. You can replicate normal JSON.stringify by ``` docker build -t sugar/cpu-benchmark . docker run sugar/cpu-benchmark:latest docker stats ``` You can replicate yieldable-json by - (make sure your toggle the Docker>preferences>Advanced memory section to be larger than 8GB first) ``` docker build -f Dockerfile-yieldable -t sugar/cpu-benchmark-yieldable . docker run -m=8g sugar/cpu-benchmark-yieldable:latest docker stats ``` |
| json metadata | {"tags":["nodejs"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #38248978/Trx 5d22d2c393a4ae98415148e85156cd4019765adb |
View Raw JSON Data
{
"trx_id": "5d22d2c393a4ae98415148e85156cd4019765adb",
"block": 38248978,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-11-17T08:36:03",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "nodejs",
"author": "guesshu",
"permlink": "benckmarking-the-known-problem-of-blocking-json-stringify-a-common-bottleneck-for-nodejs-programs",
"title": "benckmarking the known problem of blocking JSON.stringify, a common bottleneck for NodeJS programs",
"body": "cpu benchmark on JSON.stringify and its alternatives.\n\nA 524.288019 MB JSON string takes up to 100% CPU on my 3.5 GHz Quad-Core Intel Core i5 \nwhen it is being stringified with `JSON.stringify`.\n\nA half sized (209.715219 MB) JSON string takes up to 100% CPU with the yieldable-json library too.\n\nYou can replicate normal JSON.stringify by \n```\ndocker build -t sugar/cpu-benchmark .\ndocker run sugar/cpu-benchmark:latest\ndocker stats\n```\n\nYou can replicate yieldable-json by \n- (make sure your toggle the Docker>preferences>Advanced memory section to be larger than 8GB first)\n```\ndocker build -f Dockerfile-yieldable -t sugar/cpu-benchmark-yieldable .\ndocker run -m=8g sugar/cpu-benchmark-yieldable:latest\ndocker stats\n```",
"json_metadata": "{\"tags\":[\"nodejs\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}guesshuupvoted (100.00%) @hatemmkh / steem-and-sbd-and-sp-explained2019/11/10 08:02:30
guesshuupvoted (100.00%) @hatemmkh / steem-and-sbd-and-sp-explained
2019/11/10 08:02:30
| voter | guesshu |
| author | hatemmkh |
| permlink | steem-and-sbd-and-sp-explained |
| weight | 10000 (100.00%) |
| Transaction Info | Block #38047144/Trx 675e98025c574c657963e14000d2a71a145e3f3e |
View Raw JSON Data
{
"trx_id": "675e98025c574c657963e14000d2a71a145e3f3e",
"block": 38047144,
"trx_in_block": 22,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-11-10T08:02:30",
"op": [
"vote",
{
"voter": "guesshu",
"author": "hatemmkh",
"permlink": "steem-and-sbd-and-sp-explained",
"weight": 10000
}
]
}2019/08/21 09:38:03
2019/08/21 09:38:03
| delegator | steem |
| delegatee | guesshu |
| vesting shares | 9710.904647 VESTS |
| Transaction Info | Block #35742826/Trx 964e893e54040c0868fe2a799ea577a441a523c1 |
View Raw JSON Data
{
"trx_id": "964e893e54040c0868fe2a799ea577a441a523c1",
"block": 35742826,
"trx_in_block": 15,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-08-21T09:38:03",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "guesshu",
"vesting_shares": "9710.904647 VESTS"
}
]
}2019/03/13 18:10:51
2019/03/13 18:10:51
| parent author | guesshu |
| parent permlink | dpos-bft-pipelined-byzantine-fault-tolerance |
| author | steemitboard |
| permlink | steemitboard-notify-guesshu-20190313t181050000z |
| title | |
| body | Congratulations @guesshu! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@guesshu/birthday1.png</td><td>Happy Birthday! - You are on the Steem blockchain for 1 year!</td></tr></table> <sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@guesshu) and compare to others on the [Steem Ranking](http://steemitboard.com/ranking/index.php?name=guesshu)_</sub> **Do not miss the last post from @steemitboard:** <table><tr><td><a href="https://steemit.com/drugwars/@steemitboard/drugwars-early-adopter"><img src="https://steemitimages.com/64x128/https://cdn.steemitimages.com/DQmYGN7R653u4hDFyq1hM7iuhr2bdAP1v2ApACDNtecJAZ5/image.png"></a></td><td><a href="https://steemit.com/drugwars/@steemitboard/drugwars-early-adopter">Are you a DrugWars early adopter? Benvenuto in famiglia!</a></td></tr></table> ###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| Transaction Info | Block #31124038/Trx 6f9657ee7b3cc49afa15d8e21fa611698b862ac4 |
View Raw JSON Data
{
"trx_id": "6f9657ee7b3cc49afa15d8e21fa611698b862ac4",
"block": 31124038,
"trx_in_block": 9,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-03-13T18:10:51",
"op": [
"comment",
{
"parent_author": "guesshu",
"parent_permlink": "dpos-bft-pipelined-byzantine-fault-tolerance",
"author": "steemitboard",
"permlink": "steemitboard-notify-guesshu-20190313t181050000z",
"title": "",
"body": "Congratulations @guesshu! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@guesshu/birthday1.png</td><td>Happy Birthday! - You are on the Steem blockchain for 1 year!</td></tr></table>\n\n<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@guesshu) and compare to others on the [Steem Ranking](http://steemitboard.com/ranking/index.php?name=guesshu)_</sub>\n\n\n**Do not miss the last post from @steemitboard:**\n<table><tr><td><a href=\"https://steemit.com/drugwars/@steemitboard/drugwars-early-adopter\"><img src=\"https://steemitimages.com/64x128/https://cdn.steemitimages.com/DQmYGN7R653u4hDFyq1hM7iuhr2bdAP1v2ApACDNtecJAZ5/image.png\"></a></td><td><a href=\"https://steemit.com/drugwars/@steemitboard/drugwars-early-adopter\">Are you a DrugWars early adopter? Benvenuto in famiglia!</a></td></tr></table>\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}"
}
]
}2018/09/07 10:11:51
2018/09/07 10:11:51
| delegator | steem |
| delegatee | guesshu |
| vesting shares | 9909.206913 VESTS |
| Transaction Info | Block #25748422/Trx eff8259c93b4e9424dfc1b585fa7f3ba9ff1b184 |
View Raw JSON Data
{
"trx_id": "eff8259c93b4e9424dfc1b585fa7f3ba9ff1b184",
"block": 25748422,
"trx_in_block": 9,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-09-07T10:11:51",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "guesshu",
"vesting_shares": "9909.206913 VESTS"
}
]
}2018/07/18 14:39:18
2018/07/18 14:39:18
| delegator | steem |
| delegatee | guesshu |
| vesting shares | 30218.441882 VESTS |
| Transaction Info | Block #24286140/Trx 89544a7ef88d6e83cf610b1ff6af7cccc2177800 |
View Raw JSON Data
{
"trx_id": "89544a7ef88d6e83cf610b1ff6af7cccc2177800",
"block": 24286140,
"trx_in_block": 63,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-07-18T14:39:18",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "guesshu",
"vesting_shares": "30218.441882 VESTS"
}
]
}iftttupvoted (100.00%) @guesshu / dpos-bft-pipelined-byzantine-fault-tolerance2018/06/08 12:04:24
iftttupvoted (100.00%) @guesshu / dpos-bft-pipelined-byzantine-fault-tolerance
2018/06/08 12:04:24
| voter | ifttt |
| author | guesshu |
| permlink | dpos-bft-pipelined-byzantine-fault-tolerance |
| weight | 10000 (100.00%) |
| Transaction Info | Block #23141857/Trx 91753d7b63251fa7ab7460532b87260f10bda581 |
View Raw JSON Data
{
"trx_id": "91753d7b63251fa7ab7460532b87260f10bda581",
"block": 23141857,
"trx_in_block": 28,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-08T12:04:24",
"op": [
"vote",
{
"voter": "ifttt",
"author": "guesshu",
"permlink": "dpos-bft-pipelined-byzantine-fault-tolerance",
"weight": 10000
}
]
}sensationupvoted (100.00%) @guesshu / dpos-bft-pipelined-byzantine-fault-tolerance2018/06/08 07:53:21
sensationupvoted (100.00%) @guesshu / dpos-bft-pipelined-byzantine-fault-tolerance
2018/06/08 07:53:21
| voter | sensation |
| author | guesshu |
| permlink | dpos-bft-pipelined-byzantine-fault-tolerance |
| weight | 10000 (100.00%) |
| Transaction Info | Block #23136838/Trx 653613f45c9fb40df1458cfbf56b378abc34d08e |
View Raw JSON Data
{
"trx_id": "653613f45c9fb40df1458cfbf56b378abc34d08e",
"block": 23136838,
"trx_in_block": 19,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-08T07:53:21",
"op": [
"vote",
{
"voter": "sensation",
"author": "guesshu",
"permlink": "dpos-bft-pipelined-byzantine-fault-tolerance",
"weight": 10000
}
]
}moby-dickupvoted (100.00%) @guesshu / dpos-bft-pipelined-byzantine-fault-tolerance2018/06/08 07:43:00
moby-dickupvoted (100.00%) @guesshu / dpos-bft-pipelined-byzantine-fault-tolerance
2018/06/08 07:43:00
| voter | moby-dick |
| author | guesshu |
| permlink | dpos-bft-pipelined-byzantine-fault-tolerance |
| weight | 10000 (100.00%) |
| Transaction Info | Block #23136631/Trx 9c92811eaa11b5c8391677c7b9b24c0a4f1f897c |
View Raw JSON Data
{
"trx_id": "9c92811eaa11b5c8391677c7b9b24c0a4f1f897c",
"block": 23136631,
"trx_in_block": 52,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-08T07:43:00",
"op": [
"vote",
{
"voter": "moby-dick",
"author": "guesshu",
"permlink": "dpos-bft-pipelined-byzantine-fault-tolerance",
"weight": 10000
}
]
}ax3upvoted (1.00%) @guesshu / dpos-bft-pipelined-byzantine-fault-tolerance2018/06/08 07:11:00
ax3upvoted (1.00%) @guesshu / dpos-bft-pipelined-byzantine-fault-tolerance
2018/06/08 07:11:00
| voter | ax3 |
| author | guesshu |
| permlink | dpos-bft-pipelined-byzantine-fault-tolerance |
| weight | 100 (1.00%) |
| Transaction Info | Block #23135991/Trx b762fd7385c9990b0e8e00ee84bf504dbc50ef83 |
View Raw JSON Data
{
"trx_id": "b762fd7385c9990b0e8e00ee84bf504dbc50ef83",
"block": 23135991,
"trx_in_block": 18,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-08T07:11:00",
"op": [
"vote",
{
"voter": "ax3",
"author": "guesshu",
"permlink": "dpos-bft-pipelined-byzantine-fault-tolerance",
"weight": 100
}
]
}guesshupublished a new post: dpos-bft-pipelined-byzantine-fault-tolerance2018/06/08 07:10:48
guesshupublished a new post: dpos-bft-pipelined-byzantine-fault-tolerance
2018/06/08 07:10:48
| parent author | |
| parent permlink | eos |
| author | guesshu |
| permlink | dpos-bft-pipelined-byzantine-fault-tolerance |
| title | DPOS BFT— Pipelined Byzantine Fault Tolerance 委托权益证明 - 管道式的拜占庭容错 |
| body | https://medium.com/eosio/dpos-bft-pipelined-byzantine-fault-tolerance-8a0634a270ba DPOS BFT— Pipelined Byzantine Fault Tolerance 委托权益证明 - 管道式的拜占庭容错 Author/原作者: Dan Larimer https://steemit.com/@dan Translater/翻译: https://steemit.com/@guesshu There are two general blockchain consensus systems: those that produce unambiguous 100% finality given a defined set of validators and those which do not provide 100% finality but instead rely on high probability of finality. 大体上有两类区块链公示系统:一类利用限定的验证者来产生100%的定局;另一类依赖高可能性而不能产生100%的定局; The first generation blockchain consensus algorithms (Proof of Work, Proof of Stake, and BitShares’ Delegated Proof of Stake) only offer high probability of finality that grows with time. In theory someone could pay enough money to mine an alternative “longer” Bitcoin blockchain that goes all the way back to genesis. 第一代的区块链共识算法(工作证明,权益证明和比特股的委托权益证明)只提供了随时间增长的高可能性的定局。理论上,有人可以付出足够的代价来挖出另一条“更长”的一路追溯到创世块的比特币区块链。 More recent consensus algorithms, whether HashGraph, Casper, Tendermint, or DPOS BFT all adopt long-established principles of Paxos and related consensus algorithms. Under these models it is possible to reach unambiguous finality under all network conditions so long as more than ⅔ of participants are honest 近期出现的共识算法,无论HashGraph, Casper, Tendermint或者DPOS BFT也好,都采用了长期受到认可的Paxos和相关的共识算法。只要超过2/3的参与者是诚实的,这些模型们在任何网络条件下都可能达成不模棱两可的定局。 Objective and unambiguous 100% finality is a critical property for all blockchains that wish to support inter-blockchain communication. Absent 100% finality, a reversion on one chain could have irreconcilable ripple effects across all interconnected chains. 客观和不模棱两可的定局是所有想要实现跨链沟通的区块链的关键性质之一。倘若没有100%的确定性,一条链上的(交易)逆转会引发所有相互连接的链之间的不能协调的涟漪效应。 The abstract protocol for these more recent protocols involves: * Propose block * All participants acknowledge block (pre-commitment) * All participants acknowledge when ⅔+ have sent them pre-commitments (commitment) * A block is final once a node has received ⅔+ commitments * Unanimous agreement on finality is guaranteed unless ⅓+ are bad and evidence of bad behavior is available to all 最近出现的这些协议的梗概: 1. 提议一个区块 2. 所有参与者公认收到这个区块(预承诺) 3. 当收到2/3+的参与者发送的预承诺时,所有参与者公认(承诺) 4. 当一个节点收到2/3+的承诺时,一个区块就被认为是确定了的 5. 除非1/3+的参与者是不诚实并且不诚实举动的证明对所有人可见,否则一定可以一致同意达成定局  What makes the various consensus protocols different are: * Deciding when and who gets to propose a block * Deciding how commitments are logged & communicated * How byzantine behavior is documented * Punishment for byzantine behavior 这些共识协议的不同之处在于: 1. 决定何时以及谁可以提议一个区块 2. 决定承诺时如何被记录和沟通的 3. 如何记载拜占庭行为 4. 拜占庭行为的惩罚 Some of these differences are political and some of them are technical in nature. Examples of political differences include: * DPOS elects the set of proposers & validators based upon stake * Casper relies on proof-of-work to determine when and who and when gets to propose and bonded-stake-weight to determine who the validators are * DPOS punishes objective and subjective bad behavior by voting people out * Casper only punishes objective bad behavior by slashing bonds 这些不同点有的是政治上的不同,有的是技术层面的不同。政治不同点的例子包括: 1. DPOS基于权益选拔提议者和验证者 2. Casper靠工作证明去决定谁什么时候可以提议和绑定权益重量来决定谁是验证者【翻译也不懂这是什么意思】 3. DPOS靠投票出局来客观或主观的惩罚恶意行为 4. Casper只靠削减债务来客观的惩罚恶意行为 Under normal conditions, the political differences make no day-to-day impact on the experience of users relying on the consensus mechanism to order and finalize transactions. The threshold for malicious behavior is so high and the penalties so great that for all practical purposes it doesn’t happen. 通常情况下,政治上的区别对日常的依靠共识机制去排序和最终确定交易的用户体验不造成影响。恶意行为的阈值如此之高,对其的惩罚如此之多,以至于实际上不会发生。 It is the technical differences in the protocols that give rise to real-world impact on user experience. This includes things such as latency until finality, degrees of finality, bandwidth, and proof generation / validation overhead. 这些协议的技术层面的区别反而对用户体验有实际的影响。这其中包括定局的延迟性,定局的程度,带宽,产生/验证证明的经常开销。 The simplest possible algorithm has everyone reach consensus on one block before any progress can be made on the next block. This involves every participant sending every other participant two messages per block. In a global network the speed of light limits the practical latency from time of proposal to the time a node receives ⅔+ commit messages to about one second (500ms round trip latency * 2 round-trips). All networks I have observed seem to be in the 2–3 second latency camp. These simple protocols also have a “timer” which introduces a new proposal if no consensus can be reached over the validity of the current proposal. This timer is generally longer than the expected confirmation time. 用可能最简单的算法,每个人需要对一个区块达成共识,才能进行下一个区块。这牵涉到针对每一个区块,每个参与者向每个其他参与者发送两条信息。在一个全球网络上,光的速度限制了由提议到一个区块收到2/3+承诺信息的实际延迟时间为大概1秒(500微秒往返程延迟*2次往返程)。我观察到的所有网络似乎都是有2-3秒的延迟。这些简单的协议也会有一个“计时器”,当现在这个提议在限定时间内达不成共识的时候就会提出一个新的提议。这个时间限定通常会长过确认时间的期望值。 Protocols like Casper attempt to minimize the overhead by relying on proof-of-work for short-term consensus and only reaching finality over every 100th block (checkpoint). This means Casper-based chains reach finality every 20 to 30 minutes. 像Casper这样的协议尝试靠工作量证明达成短期共识来减少经常开销,且只能每100个区块(检查节点)达成定局。这意味着基于Casper的链每20-30分钟才能达成定局。 DPOS BFT Pipeline Consensus 委托权益证明拜占庭容错管道式共识 Modern Delegated Proof of Stake with BFT as implemented in EOSIO uses a pipelined approach to deliver the proposal, pre-commitment, and commitment messages. This means under normal operating conditions, every block advances the finality of one block and this is achieved by only requiring one proposal per time slot. In other words, the cost of DPOS with BFT finality in terms of signature verifications, hash calculations, network bandwidth, etc., is equal to the cost of older DPOS systems that relied upon eventual consistency and the longest chain rule similar to Bitcoin and Ethereum (pre Casper). 摩登的带有拜占庭容错的委托权益证明(如EOSIO的实施)采用管道式的办法去传递提议,预承诺和承诺信息。这意味着在一般的操作条件下,每个区块使一个区块的定局加速,而这是靠每个时间槽只要求一个提议来实现。换句话说,拜占庭容错的委托权益证明的定局成本(包括签名验证,哈希值计算,网络带宽等等),等于旧式的委托权益证明的成本,这些旧式的委托权益证明依靠结果一致性和最长链规则, 类似于比特币和Casper落地之前的以太网。 Only DPOS BFT can efficiently scale to an unlimited number of validators (at cost to latency). Other protocols grow the resource requirements for finality with O(2N) the number of participants as everyone must talk to everyone twice for each block or checkpoint. With more parties involved,more signatures, network overhead, and storage are required and there is greater latency. 只有拜占庭容错委托权益证明可以有效的扩展到无限个验证者的情况(以延迟性为代价)。其他的协议在参与者数量增长的时候对资源的要求增速为O(2N), 因为每个人需要就每个区块或检查节点和其他每个人交谈两次。当越来越的的人参与进来,则需要越来越多的签名,网络经常开销,和存储;并且延迟也会增加。 Assuming DPOS BFT with two second block interval and 21 producers, finality can be reached after 1 minute, but a new block reaches finality every two seconds. This is achieved by pipelining the BFT confirmations. Platforms like EOSIO produce blocks every 500ms, but only rotate proposers every 12 blocks. This means BFT finality takes about 3 minutes based upon pure BFT DPOS block confirmations. The end result is 10x faster than Casper for finality for individual blocks, but a new block reaches finality every two seconds versus every 30 minutes. 假设一个2秒出块和21个出块者的拜占庭容错委托权益证明,定局每1分钟可以达成,但是每一个新的块可以每两秒达成定局。这是靠用管道运输拜占庭容错确认实现的。像EOSIO一样的平台没500微妙出块,但是只在每12个块的时候轮换提议者。这意味着拜占庭容错定局需要3秒,基于纯粹的拜占庭容错区块确认。最终的结果是这比Casper快10倍能达成每个区块的定局,而每2秒而不是每30分钟有一个新的区块达成定局。  DPOS BFT w/ optional Low-Latency Confirmation 拜占庭容错委托权益证明以及选择性的低延迟确认 DPOS Hybrid Pipeline / Realtime BFT 委托权益证明混合管道/实时拜占庭容错 There are many applications where a three minute time for finality is undesirable and/or the DPOS proofs for light clients for a particular block are larger than desired. In this case, a blockchain can make the design choice to do a BFT pre-commit & commit message over every pending block. This gives DPOS-BFT chains finality latency of 1–2 seconds at the expense of the additional network overhead, storage requirements, and CPU usage. Unlike protocols such as Tendermint/Cosmos there can be multiple proposals “in-the pipeline” at the same time. It is even possible that some blocks never receive the “real time” commitment due to network splits, but never the less they are eventually indirectly confirmed. 在很多应用场景中,3分钟的定局时间是不受欢迎的;或者在轻客户端上,某一个特定的区块的委托权益证明的证明(文件大小)过大。应对这些情况,一个区块链可以做出设计上的决定去给每一个未决区块发送拜占庭容错预承诺和承诺信息。这令到拜占庭容错的委托权益证明的定局延迟只有1-2秒,以附加的网络开销,存储需求和CPU用量为代价。有别于Tendermint/Cosmos一类的协议,可以同时有多个提议“在管道里”。甚至有可能的是,有些区块因为网络分裂的原因从未收到“实时”的承诺,但仍然间接的得到了确认。 With the hybrid approach light clients can validate a block with 15 signatures and/or use more advanced cryptographic techniques to merge commit signatures into a single signature. Without the commit messages light clients can still reach BFT finality using a number of consecutive block headers. 混合式的轻客户端可以验证有15个签名的区块或者利用更加先进的密码学方法去合并承诺签名们为一个签名。即使没有承诺信息,轻客户端仍然可以用一连串的区块块头达成拜占庭容错定局。 Degrees of Security 安全程度 It has long been understood that for many applications, such as blog posts and social media voting, waiting for 100% finality is overkill when 99.999% finality can be achieved in less than a second. Protocols like Casper give users the option of relying on Proof of Work confirmations when waiting for the next checkpoint is overkill. 长期以来,人们都能理解像博客文章或者社交媒体投票一类的的用例,当99.99%的定局在1秒内可以达成,那么追求100%的定局是矫枉过正的。像Casper一类的协议让用户依赖工作量证明去等待下一个检查节点也是矫枉过正的。 Some full nodes may not care to process the overhead of all BFT pre-commit/commit messages when all they require is blockchain state. It is enough to know that the block producers (proposers/validators) are reaching real-time consensus and that their blockheaders eventually prove BFT consensus a couple minutes later. 某些只需要区块链状态的完整节点可能并不关心而不去处理所有拜占庭容错预承诺/承诺信息的开销。知道区块制造者(提议者、验证者)在实时达成共识而且他们的区块块头几分钟后最终会证明达成拜占庭容错共识已经足够。 Each consensus algorithm makes certain choices for users and degrades to less-secure variations in different ways. Tendermint/Cosmos/Ripple don’t give users a choice to operate with anything less than full finality. Ethereum gives users a fall-back to proof-of-work, and DPOS-BFT falls back to the original DPOS guarantees. 每个共识机制都会为用户做出一些选择和以不同的方式降级为相对不安全的变种。Tendermint/Cosmos/Ripple并没有给用户任何选择不去按完全的定局去运作。以太坊用户可以倒退为工作量证明,而拜占庭容错委托权益证明可以倒退为原版的委托权益证明保障。 It is even possible to layer the Casper checkpoint algorithm with slashing conditions on top of the DPOS BFT block proposal system. Such an approach would create multiple independent validator sets with both political and economic incentives for good behavior. 在DPOS BFT区块提议系统之上加有削减条件的Casper检查节点算法也是可能的。这样的办法可以促成多个独立的既有政治层面又有技术层面激励的验证者集合。 User Experience 用户体验 Delegated Proof of Stake with BFT optimizes the nominal case while being no-worse in the worst case. Under normal conditions, elected block producers are trusted public figures with legal liabilities and highly reliable nodes. The probability that a produced block will reach finality is already 99.999% which means that the average user gets near-certain finality in under a second. This is reliable enough for almost all day-to-day financial transactions. Larger financial transactions, such as buying a car, merely require the user to wait a few seconds for absolute finality. 拜占庭容错委托权益证明优化象征性的案例而在最坏情况中没有更差。在一般条件下,选出的出块者是受信任的公众人物,在法律上受到约束且高度可靠的节点。产生出来的区块一秒内达成定局的可能性已经是99.999%,这意味着普通用户在一秒内得到近乎肯定的定局。这对几乎所有的日常金融交易都是足够可靠的。更大额度的金融交易,例如买车,只需要用户为了绝对的定局等待几秒。 Each user can decide for themselves how much overhead and/or delay they wish to incur and how big the proofs they want to generate for inter-blockchain communication, whereas other protocols do not give users that choice. 每个用户可以自己决定对于跨链的沟通他们想要多少开销和延迟以及需要多大的证明,而其他协议并没有提供这个选项。 Conclusion 结论 All modern consensus algorithms that follow the BFT consensus principles originally introduced the 1980’s can reach a secure and final state in the worst-case of a partitioned network with ⅓ byzantine participants. Only DPOS BFT and EOSIO is optimized for the 99.999% case of 100% honest nodes without network partitions. DPOS BFT achieves this optimized performance without sacrificing the security guarantees that other protocols provide. 现在所有的追随拜占庭容错共识原则(1980年代提出)的共识算法可以在1/3拜占庭参与者进行网络分裂的最差情况下达到一个安全和最终的状态。只有DPOS BFT和EOSIO优化了没有网络分裂的有100%诚实节点的99.999%案例。DPOS BFT在不牺牲其他协议也提供的安全保障的前提下达到这种优化的表现。 |
| json metadata | {"tags":["eos"],"links":["https://medium.com/eosio/dpos-bft-pipelined-byzantine-fault-tolerance-8a0634a270ba","https://steemit.com/@dan","https://steemit.com/@guesshu"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #23135987/Trx 190823253fb3c4a94b81112d437d3faa6d839590 |
View Raw JSON Data
{
"trx_id": "190823253fb3c4a94b81112d437d3faa6d839590",
"block": 23135987,
"trx_in_block": 48,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-08T07:10:48",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "eos",
"author": "guesshu",
"permlink": "dpos-bft-pipelined-byzantine-fault-tolerance",
"title": "DPOS BFT— Pipelined Byzantine Fault Tolerance 委托权益证明 - 管道式的拜占庭容错",
"body": "https://medium.com/eosio/dpos-bft-pipelined-byzantine-fault-tolerance-8a0634a270ba\nDPOS BFT— Pipelined Byzantine Fault Tolerance\n委托权益证明 - 管道式的拜占庭容错\n\nAuthor/原作者: Dan Larimer https://steemit.com/@dan\nTranslater/翻译: https://steemit.com/@guesshu\n\nThere are two general blockchain consensus systems: those that produce unambiguous 100% finality given a defined set of validators and those which do not provide 100% finality but instead rely on high probability of finality.\n大体上有两类区块链公示系统:一类利用限定的验证者来产生100%的定局;另一类依赖高可能性而不能产生100%的定局;\n\nThe first generation blockchain consensus algorithms (Proof of Work, Proof of Stake, and BitShares’ Delegated Proof of Stake) only offer high probability of finality that grows with time. In theory someone could pay enough money to mine an alternative “longer” Bitcoin blockchain that goes all the way back to genesis.\n第一代的区块链共识算法(工作证明,权益证明和比特股的委托权益证明)只提供了随时间增长的高可能性的定局。理论上,有人可以付出足够的代价来挖出另一条“更长”的一路追溯到创世块的比特币区块链。\n\nMore recent consensus algorithms, whether HashGraph, Casper, Tendermint, or DPOS BFT all adopt long-established principles of Paxos and related consensus algorithms. Under these models it is possible to reach unambiguous finality under all network conditions so long as more than ⅔ of participants are honest\n近期出现的共识算法,无论HashGraph, Casper, Tendermint或者DPOS BFT也好,都采用了长期受到认可的Paxos和相关的共识算法。只要超过2/3的参与者是诚实的,这些模型们在任何网络条件下都可能达成不模棱两可的定局。\n\nObjective and unambiguous 100% finality is a critical property for all blockchains that wish to support inter-blockchain communication. Absent 100% finality, a reversion on one chain could have irreconcilable ripple effects across all interconnected chains.\n客观和不模棱两可的定局是所有想要实现跨链沟通的区块链的关键性质之一。倘若没有100%的确定性,一条链上的(交易)逆转会引发所有相互连接的链之间的不能协调的涟漪效应。\n\nThe abstract protocol for these more recent protocols involves:\n* Propose block\n* All participants acknowledge block (pre-commitment)\n* All participants acknowledge when ⅔+ have sent them pre-commitments (commitment)\n* A block is final once a node has received ⅔+ commitments\n* Unanimous agreement on finality is guaranteed unless ⅓+ are bad and evidence of bad behavior is available to all\n最近出现的这些协议的梗概:\n1. 提议一个区块\n2. 所有参与者公认收到这个区块(预承诺)\n3. 当收到2/3+的参与者发送的预承诺时,所有参与者公认(承诺)\n4. 当一个节点收到2/3+的承诺时,一个区块就被认为是确定了的\n5. 除非1/3+的参与者是不诚实并且不诚实举动的证明对所有人可见,否则一定可以一致同意达成定局\n\n\nWhat makes the various consensus protocols different are:\n* Deciding when and who gets to propose a block\n* Deciding how commitments are logged & communicated\n* How byzantine behavior is documented\n* Punishment for byzantine behavior\n这些共识协议的不同之处在于:\n1. 决定何时以及谁可以提议一个区块\n2. 决定承诺时如何被记录和沟通的\n3. 如何记载拜占庭行为\n4. 拜占庭行为的惩罚\n\nSome of these differences are political and some of them are technical in nature. Examples of political differences include:\n* DPOS elects the set of proposers & validators based upon stake\n* Casper relies on proof-of-work to determine when and who and when gets to propose and bonded-stake-weight to determine who the validators are\n* DPOS punishes objective and subjective bad behavior by voting people out\n* Casper only punishes objective bad behavior by slashing bonds\n这些不同点有的是政治上的不同,有的是技术层面的不同。政治不同点的例子包括:\n1. DPOS基于权益选拔提议者和验证者\n2. Casper靠工作证明去决定谁什么时候可以提议和绑定权益重量来决定谁是验证者【翻译也不懂这是什么意思】\n3. DPOS靠投票出局来客观或主观的惩罚恶意行为\n4. Casper只靠削减债务来客观的惩罚恶意行为\n\nUnder normal conditions, the political differences make no day-to-day impact on the experience of users relying on the consensus mechanism to order and finalize transactions. The threshold for malicious behavior is so high and the penalties so great that for all practical purposes it doesn’t happen.\n通常情况下,政治上的区别对日常的依靠共识机制去排序和最终确定交易的用户体验不造成影响。恶意行为的阈值如此之高,对其的惩罚如此之多,以至于实际上不会发生。\n\nIt is the technical differences in the protocols that give rise to real-world impact on user experience. This includes things such as latency until finality, degrees of finality, bandwidth, and proof generation / validation overhead.\n这些协议的技术层面的区别反而对用户体验有实际的影响。这其中包括定局的延迟性,定局的程度,带宽,产生/验证证明的经常开销。\n\nThe simplest possible algorithm has everyone reach consensus on one block before any progress can be made on the next block. This involves every participant sending every other participant two messages per block. In a global network the speed of light limits the practical latency from time of proposal to the time a node receives ⅔+ commit messages to about one second (500ms round trip latency * 2 round-trips). All networks I have observed seem to be in the 2–3 second latency camp. These simple protocols also have a “timer” which introduces a new proposal if no consensus can be reached over the validity of the current proposal. This timer is generally longer than the expected confirmation time.\n用可能最简单的算法,每个人需要对一个区块达成共识,才能进行下一个区块。这牵涉到针对每一个区块,每个参与者向每个其他参与者发送两条信息。在一个全球网络上,光的速度限制了由提议到一个区块收到2/3+承诺信息的实际延迟时间为大概1秒(500微秒往返程延迟*2次往返程)。我观察到的所有网络似乎都是有2-3秒的延迟。这些简单的协议也会有一个“计时器”,当现在这个提议在限定时间内达不成共识的时候就会提出一个新的提议。这个时间限定通常会长过确认时间的期望值。\n\nProtocols like Casper attempt to minimize the overhead by relying on proof-of-work for short-term consensus and only reaching finality over every 100th block (checkpoint). This means Casper-based chains reach finality every 20 to 30 minutes.\n像Casper这样的协议尝试靠工作量证明达成短期共识来减少经常开销,且只能每100个区块(检查节点)达成定局。这意味着基于Casper的链每20-30分钟才能达成定局。\n\nDPOS BFT Pipeline Consensus\n委托权益证明拜占庭容错管道式共识\n\nModern Delegated Proof of Stake with BFT as implemented in EOSIO uses a pipelined approach to deliver the proposal, pre-commitment, and commitment messages. This means under normal operating conditions, every block advances the finality of one block and this is achieved by only requiring one proposal per time slot. In other words, the cost of DPOS with BFT finality in terms of signature verifications, hash calculations, network bandwidth, etc., is equal to the cost of older DPOS systems that relied upon eventual consistency and the longest chain rule similar to Bitcoin and Ethereum (pre Casper).\n摩登的带有拜占庭容错的委托权益证明(如EOSIO的实施)采用管道式的办法去传递提议,预承诺和承诺信息。这意味着在一般的操作条件下,每个区块使一个区块的定局加速,而这是靠每个时间槽只要求一个提议来实现。换句话说,拜占庭容错的委托权益证明的定局成本(包括签名验证,哈希值计算,网络带宽等等),等于旧式的委托权益证明的成本,这些旧式的委托权益证明依靠结果一致性和最长链规则, 类似于比特币和Casper落地之前的以太网。\n\nOnly DPOS BFT can efficiently scale to an unlimited number of validators (at cost to latency). Other protocols grow the resource requirements for finality with O(2N) the number of participants as everyone must talk to everyone twice for each block or checkpoint. With more parties involved,more signatures, network overhead, and storage are required and there is greater latency.\n只有拜占庭容错委托权益证明可以有效的扩展到无限个验证者的情况(以延迟性为代价)。其他的协议在参与者数量增长的时候对资源的要求增速为O(2N), 因为每个人需要就每个区块或检查节点和其他每个人交谈两次。当越来越的的人参与进来,则需要越来越多的签名,网络经常开销,和存储;并且延迟也会增加。\n\nAssuming DPOS BFT with two second block interval and 21 producers, finality can be reached after 1 minute, but a new block reaches finality every two seconds. This is achieved by pipelining the BFT confirmations. Platforms like EOSIO produce blocks every 500ms, but only rotate proposers every 12 blocks. This means BFT finality takes about 3 minutes based upon pure BFT DPOS block confirmations. The end result is 10x faster than Casper for finality for individual blocks, but a new block reaches finality every two seconds versus every 30 minutes.\n假设一个2秒出块和21个出块者的拜占庭容错委托权益证明,定局每1分钟可以达成,但是每一个新的块可以每两秒达成定局。这是靠用管道运输拜占庭容错确认实现的。像EOSIO一样的平台没500微妙出块,但是只在每12个块的时候轮换提议者。这意味着拜占庭容错定局需要3秒,基于纯粹的拜占庭容错区块确认。最终的结果是这比Casper快10倍能达成每个区块的定局,而每2秒而不是每30分钟有一个新的区块达成定局。\n\n\t\t\t\tDPOS BFT w/ optional Low-Latency Confirmation\n\t\t\t\t拜占庭容错委托权益证明以及选择性的低延迟确认\n\nDPOS Hybrid Pipeline / Realtime BFT\n委托权益证明混合管道/实时拜占庭容错\n\nThere are many applications where a three minute time for finality is undesirable and/or the DPOS proofs for light clients for a particular block are larger than desired. In this case, a blockchain can make the design choice to do a BFT pre-commit & commit message over every pending block. This gives DPOS-BFT chains finality latency of 1–2 seconds at the expense of the additional network overhead, storage requirements, and CPU usage. Unlike protocols such as Tendermint/Cosmos there can be multiple proposals “in-the pipeline” at the same time. It is even possible that some blocks never receive the “real time” commitment due to network splits, but never the less they are eventually indirectly confirmed.\n在很多应用场景中,3分钟的定局时间是不受欢迎的;或者在轻客户端上,某一个特定的区块的委托权益证明的证明(文件大小)过大。应对这些情况,一个区块链可以做出设计上的决定去给每一个未决区块发送拜占庭容错预承诺和承诺信息。这令到拜占庭容错的委托权益证明的定局延迟只有1-2秒,以附加的网络开销,存储需求和CPU用量为代价。有别于Tendermint/Cosmos一类的协议,可以同时有多个提议“在管道里”。甚至有可能的是,有些区块因为网络分裂的原因从未收到“实时”的承诺,但仍然间接的得到了确认。\n\nWith the hybrid approach light clients can validate a block with 15 signatures and/or use more advanced cryptographic techniques to merge commit signatures into a single signature. Without the commit messages light clients can still reach BFT finality using a number of consecutive block headers.\n混合式的轻客户端可以验证有15个签名的区块或者利用更加先进的密码学方法去合并承诺签名们为一个签名。即使没有承诺信息,轻客户端仍然可以用一连串的区块块头达成拜占庭容错定局。\n\nDegrees of Security\n安全程度\n\nIt has long been understood that for many applications, such as blog posts and social media voting, waiting for 100% finality is overkill when 99.999% finality can be achieved in less than a second. Protocols like Casper give users the option of relying on Proof of Work confirmations when waiting for the next checkpoint is overkill.\n长期以来,人们都能理解像博客文章或者社交媒体投票一类的的用例,当99.99%的定局在1秒内可以达成,那么追求100%的定局是矫枉过正的。像Casper一类的协议让用户依赖工作量证明去等待下一个检查节点也是矫枉过正的。\n\nSome full nodes may not care to process the overhead of all BFT pre-commit/commit messages when all they require is blockchain state. It is enough to know that the block producers (proposers/validators) are reaching real-time consensus and that their blockheaders eventually prove BFT consensus a couple minutes later.\n某些只需要区块链状态的完整节点可能并不关心而不去处理所有拜占庭容错预承诺/承诺信息的开销。知道区块制造者(提议者、验证者)在实时达成共识而且他们的区块块头几分钟后最终会证明达成拜占庭容错共识已经足够。\n\nEach consensus algorithm makes certain choices for users and degrades to less-secure variations in different ways. Tendermint/Cosmos/Ripple don’t give users a choice to operate with anything less than full finality. Ethereum gives users a fall-back to proof-of-work, and DPOS-BFT falls back to the original DPOS guarantees.\n每个共识机制都会为用户做出一些选择和以不同的方式降级为相对不安全的变种。Tendermint/Cosmos/Ripple并没有给用户任何选择不去按完全的定局去运作。以太坊用户可以倒退为工作量证明,而拜占庭容错委托权益证明可以倒退为原版的委托权益证明保障。\n\nIt is even possible to layer the Casper checkpoint algorithm with slashing conditions on top of the DPOS BFT block proposal system. Such an approach would create multiple independent validator sets with both political and economic incentives for good behavior.\n在DPOS BFT区块提议系统之上加有削减条件的Casper检查节点算法也是可能的。这样的办法可以促成多个独立的既有政治层面又有技术层面激励的验证者集合。\n\nUser Experience\n用户体验\n\nDelegated Proof of Stake with BFT optimizes the nominal case while being no-worse in the worst case. Under normal conditions, elected block producers are trusted public figures with legal liabilities and highly reliable nodes. The probability that a produced block will reach finality is already 99.999% which means that the average user gets near-certain finality in under a second. This is reliable enough for almost all day-to-day financial transactions. Larger financial transactions, such as buying a car, merely require the user to wait a few seconds for absolute finality.\n拜占庭容错委托权益证明优化象征性的案例而在最坏情况中没有更差。在一般条件下,选出的出块者是受信任的公众人物,在法律上受到约束且高度可靠的节点。产生出来的区块一秒内达成定局的可能性已经是99.999%,这意味着普通用户在一秒内得到近乎肯定的定局。这对几乎所有的日常金融交易都是足够可靠的。更大额度的金融交易,例如买车,只需要用户为了绝对的定局等待几秒。\n\nEach user can decide for themselves how much overhead and/or delay they wish to incur and how big the proofs they want to generate for inter-blockchain communication, whereas other protocols do not give users that choice.\n每个用户可以自己决定对于跨链的沟通他们想要多少开销和延迟以及需要多大的证明,而其他协议并没有提供这个选项。\n\nConclusion\n结论\n\nAll modern consensus algorithms that follow the BFT consensus principles originally introduced the 1980’s can reach a secure and final state in the worst-case of a partitioned network with ⅓ byzantine participants. Only DPOS BFT and EOSIO is optimized for the 99.999% case of 100% honest nodes without network partitions. DPOS BFT achieves this optimized performance without sacrificing the security guarantees that other protocols provide.\n现在所有的追随拜占庭容错共识原则(1980年代提出)的共识算法可以在1/3拜占庭参与者进行网络分裂的最差情况下达到一个安全和最终的状态。只有DPOS BFT和EOSIO优化了没有网络分裂的有100%诚实节点的99.999%案例。DPOS BFT在不牺牲其他协议也提供的安全保障的前提下达到这种优化的表现。",
"json_metadata": "{\"tags\":[\"eos\"],\"links\":[\"https://medium.com/eosio/dpos-bft-pipelined-byzantine-fault-tolerance-8a0634a270ba\",\"https://steemit.com/@dan\",\"https://steemit.com/@guesshu\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}2018/05/06 13:20:03
2018/05/06 13:20:03
| voter | guesshu |
| author | eos-helpguide |
| permlink | so-you-purchased-eos-on-an-exchange-why-you-need-to-register-your-ethereum-wallet-address-at-eos-io-prior-to-the-1-june-2018 |
| weight | 10000 (100.00%) |
| Transaction Info | Block #22193549/Trx 2912109b183006cd8ba68ba55eabf4f00709f81f |
View Raw JSON Data
{
"trx_id": "2912109b183006cd8ba68ba55eabf4f00709f81f",
"block": 22193549,
"trx_in_block": 64,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-06T13:20:03",
"op": [
"vote",
{
"voter": "guesshu",
"author": "eos-helpguide",
"permlink": "so-you-purchased-eos-on-an-exchange-why-you-need-to-register-your-ethereum-wallet-address-at-eos-io-prior-to-the-1-june-2018",
"weight": 10000
}
]
}2018/05/02 06:39:12
2018/05/02 06:39:12
| parent author | guesshu |
| parent permlink | bitmain-asic-ethash-miner-and-community-development-recap-last-update-9-apr-2018 |
| author | guesshu |
| permlink | re-guesshu-bitmain-asic-ethash-miner-and-community-development-recap-last-update-9-apr-2018-20180502t063910198z |
| title | |
| body | 2MayUpdate https://www.etherchain.org/coinvote/poll/34 There is a poll here, express your voice if you care! |
| json metadata | {"tags":["ethereum"],"links":["https://www.etherchain.org/coinvote/poll/34"],"app":"steemit/0.1"} |
| Transaction Info | Block #22070369/Trx f0deb140bfa063865c95c4928b03d61282b87e01 |
View Raw JSON Data
{
"trx_id": "f0deb140bfa063865c95c4928b03d61282b87e01",
"block": 22070369,
"trx_in_block": 17,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-02T06:39:12",
"op": [
"comment",
{
"parent_author": "guesshu",
"parent_permlink": "bitmain-asic-ethash-miner-and-community-development-recap-last-update-9-apr-2018",
"author": "guesshu",
"permlink": "re-guesshu-bitmain-asic-ethash-miner-and-community-development-recap-last-update-9-apr-2018-20180502t063910198z",
"title": "",
"body": "2MayUpdate\n\nhttps://www.etherchain.org/coinvote/poll/34 There is a poll here, express your voice if you care!",
"json_metadata": "{\"tags\":[\"ethereum\"],\"links\":[\"https://www.etherchain.org/coinvote/poll/34\"],\"app\":\"steemit/0.1\"}"
}
]
}guesshureceived 0.015 SBD, 0.009 SP author reward for @guesshu / bitmain-asic-ethash-miner-and-community-development-recap-last-update-9-apr-20182018/04/16 06:05:51
guesshureceived 0.015 SBD, 0.009 SP author reward for @guesshu / bitmain-asic-ethash-miner-and-community-development-recap-last-update-9-apr-2018
2018/04/16 06:05:51
| author | guesshu |
| permlink | bitmain-asic-ethash-miner-and-community-development-recap-last-update-9-apr-2018 |
| sbd payout | 0.015 SBD |
| steem payout | 0.000 STEEM |
| vesting payout | 14.266608 VESTS |
| Transaction Info | Block #21609633/Virtual Operation #7 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 21609633,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 7,
"timestamp": "2018-04-16T06:05:51",
"op": [
"author_reward",
{
"author": "guesshu",
"permlink": "bitmain-asic-ethash-miner-and-community-development-recap-last-update-9-apr-2018",
"sbd_payout": "0.015 SBD",
"steem_payout": "0.000 STEEM",
"vesting_payout": "14.266608 VESTS"
}
]
}2018/04/15 18:47:36
2018/04/15 18:47:36
| parent author | guesshu |
| parent permlink | bitmain-asic-ethash-miner-and-community-development-recap-last-update-9-apr-2018 |
| author | steemitboard |
| permlink | steemitboard-notify-guesshu-20180415t184738000z |
| title | |
| body | Congratulations @guesshu! You have completed some achievement on Steemit and have been rewarded with new badge(s) : [](http://steemitboard.com/@guesshu) You got a First Reply [](http://steemitboard.com/@guesshu) You made your First Vote Click on any badge to view your own Board of Honor on SteemitBoard. For more information about SteemitBoard, click [here](https://steemit.com/@steemitboard) If you no longer want to receive notifications, reply to this comment with the word `STOP` > Upvote this notification to help all Steemit users. Learn why [here](https://steemit.com/steemitboard/@steemitboard/http-i-cubeupload-com-7ciqeo-png)! |
| json metadata | {"image":["https://steemitboard.com/img/notifications.png"]} |
| Transaction Info | Block #21596069/Trx c019e297728754741e794afd5de59a2b9f85eec9 |
View Raw JSON Data
{
"trx_id": "c019e297728754741e794afd5de59a2b9f85eec9",
"block": 21596069,
"trx_in_block": 72,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-15T18:47:36",
"op": [
"comment",
{
"parent_author": "guesshu",
"parent_permlink": "bitmain-asic-ethash-miner-and-community-development-recap-last-update-9-apr-2018",
"author": "steemitboard",
"permlink": "steemitboard-notify-guesshu-20180415t184738000z",
"title": "",
"body": "Congratulations @guesshu! You have completed some achievement on Steemit and have been rewarded with new badge(s) :\n\n[](http://steemitboard.com/@guesshu) You got a First Reply\n[](http://steemitboard.com/@guesshu) You made your First Vote\n\nClick on any badge to view your own Board of Honor on SteemitBoard.\nFor more information about SteemitBoard, click [here](https://steemit.com/@steemitboard)\n\nIf you no longer want to receive notifications, reply to this comment with the word `STOP`\n\n> Upvote this notification to help all Steemit users. Learn why [here](https://steemit.com/steemitboard/@steemitboard/http-i-cubeupload-com-7ciqeo-png)!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notifications.png\"]}"
}
]
}guesshufollowed @dantheman2018/04/15 13:28:57
guesshufollowed @dantheman
2018/04/15 13:28:57
| required auths | [] |
| required posting auths | ["guesshu"] |
| id | follow |
| json | ["follow",{"follower":"guesshu","following":"dantheman","what":["blog"]}] |
| Transaction Info | Block #21589696/Trx a23dd9929ffc7487055f242d2ffc112baca2bbb5 |
View Raw JSON Data
{
"trx_id": "a23dd9929ffc7487055f242d2ffc112baca2bbb5",
"block": 21589696,
"trx_in_block": 10,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-15T13:28:57",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"guesshu"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"guesshu\",\"following\":\"dantheman\",\"what\":[\"blog\"]}]"
}
]
}2018/04/15 13:24:06
2018/04/15 13:24:06
| voter | guesshu |
| author | xebb |
| permlink | re-guesshu-re-xebb-eos-community-testnet-update-with-initial-performance-testing-on-dawn-3-0-0-20180415t124022914z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21589599/Trx 11d27af19485e5ce2178f20cecd712fb933170ff |
View Raw JSON Data
{
"trx_id": "11d27af19485e5ce2178f20cecd712fb933170ff",
"block": 21589599,
"trx_in_block": 30,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-15T13:24:06",
"op": [
"vote",
{
"voter": "guesshu",
"author": "xebb",
"permlink": "re-guesshu-re-xebb-eos-community-testnet-update-with-initial-performance-testing-on-dawn-3-0-0-20180415t124022914z",
"weight": 10000
}
]
}2018/04/15 12:40:39
2018/04/15 12:40:39
| voter | xebb |
| author | guesshu |
| permlink | re-xebb-eos-community-testnet-update-with-initial-performance-testing-on-dawn-3-0-0-20180415t095957928z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21588730/Trx 2dee02a2c7942737af6b68a358becd15dd0d34e6 |
View Raw JSON Data
{
"trx_id": "2dee02a2c7942737af6b68a358becd15dd0d34e6",
"block": 21588730,
"trx_in_block": 32,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-15T12:40:39",
"op": [
"vote",
{
"voter": "xebb",
"author": "guesshu",
"permlink": "re-xebb-eos-community-testnet-update-with-initial-performance-testing-on-dawn-3-0-0-20180415t095957928z",
"weight": 10000
}
]
}2018/04/15 12:40:21
2018/04/15 12:40:21
| parent author | guesshu |
| parent permlink | re-xebb-eos-community-testnet-update-with-initial-performance-testing-on-dawn-3-0-0-20180415t095957928z |
| author | xebb |
| permlink | re-guesshu-re-xebb-eos-community-testnet-update-with-initial-performance-testing-on-dawn-3-0-0-20180415t124022914z |
| title | |
| body | Hello, thanks for the questions! 1. In the "output box" just above "Accepted transactions..." you can see how many transactions that was put into each block (x trxs, I filtered out empty blocks), as well as the block height/number. A block is created every 0.5 second. What I mean with "Accepted transactions" is how many that was actually put into blocks (not dropped). Sorry for being unclear. 2. The problem as I currently see it is that when I try to spam nodeos with transactions (using the client) I can only do x-amount of transactions before nodeos "halts" for a few millisecond (this is where some dropped transactions possibly come in). I believe this is because the nodeos that is accepting the transactions cannot handle more (single threaded). To know what kind of tx/s that will be handled in a more real-life scenario = when we have several 100:s of nodeos accepting transactions from several thousands of clients (and 21 producers) is harder to figure out than one would think at first sight. My plan moving forward is to start testing on the community driven testnets, as well as making sure I add several more nodeos to accept transactions for my own local tests as well. |
| json metadata | {"tags":["eos-blockproducers"],"app":"steemit/0.1"} |
| Transaction Info | Block #21588724/Trx 9f51fe80c3d74410bb98cde03295b4b43c335540 |
View Raw JSON Data
{
"trx_id": "9f51fe80c3d74410bb98cde03295b4b43c335540",
"block": 21588724,
"trx_in_block": 45,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-15T12:40:21",
"op": [
"comment",
{
"parent_author": "guesshu",
"parent_permlink": "re-xebb-eos-community-testnet-update-with-initial-performance-testing-on-dawn-3-0-0-20180415t095957928z",
"author": "xebb",
"permlink": "re-guesshu-re-xebb-eos-community-testnet-update-with-initial-performance-testing-on-dawn-3-0-0-20180415t124022914z",
"title": "",
"body": "Hello,\n\nthanks for the questions!\n\n1. In the \"output box\" just above \"Accepted transactions...\" you can see how many transactions that was put into each block (x trxs, I filtered out empty blocks), as well as the block height/number. A block is created every 0.5 second. \nWhat I mean with \"Accepted transactions\" is how many that was actually put into blocks (not dropped). Sorry for being unclear.\n\n2. The problem as I currently see it is that when I try to spam nodeos with transactions (using the client) I can only do x-amount of transactions before nodeos \"halts\" for a few millisecond (this is where some dropped transactions possibly come in). I believe this is because the nodeos that is accepting the transactions cannot handle more (single threaded). To know what kind of tx/s that will be handled in a more real-life scenario = when we have several 100:s of nodeos accepting transactions from several thousands of clients (and 21 producers) is harder to figure out than one would think at first sight.\n\nMy plan moving forward is to start testing on the community driven testnets, as well as making sure I add several more nodeos to accept transactions for my own local tests as well.",
"json_metadata": "{\"tags\":[\"eos-blockproducers\"],\"app\":\"steemit/0.1\"}"
}
]
}2018/04/15 10:00:00
2018/04/15 10:00:00
| parent author | xebb |
| parent permlink | eos-community-testnet-update-with-initial-performance-testing-on-dawn-3-0-0 |
| author | guesshu |
| permlink | re-xebb-eos-community-testnet-update-with-initial-performance-testing-on-dawn-3-0-0-20180415t095957928z |
| title | |
| body | Very Comprehensive Article! Thanks a lot! I have a few questions: 1) "Accepted transactions: 400" <- means 400 transactions accepted in what time frame? 2) Are you trying not/to test Transaction Per Second? If you are, is there a summary version of the numbers? |
| json metadata | {"tags":["eos-blockproducers"],"app":"steemit/0.1"} |
| Transaction Info | Block #21585517/Trx 228edbb3be7cdf39eae134129708fb3047f04838 |
View Raw JSON Data
{
"trx_id": "228edbb3be7cdf39eae134129708fb3047f04838",
"block": 21585517,
"trx_in_block": 19,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-15T10:00:00",
"op": [
"comment",
{
"parent_author": "xebb",
"parent_permlink": "eos-community-testnet-update-with-initial-performance-testing-on-dawn-3-0-0",
"author": "guesshu",
"permlink": "re-xebb-eos-community-testnet-update-with-initial-performance-testing-on-dawn-3-0-0-20180415t095957928z",
"title": "",
"body": "Very Comprehensive Article! Thanks a lot!\n\nI have a few questions:\n1) \"Accepted transactions: 400\" <- means 400 transactions accepted in what time frame?\n\n2) Are you trying not/to test Transaction Per Second? If you are, is there a summary version of the numbers?",
"json_metadata": "{\"tags\":[\"eos-blockproducers\"],\"app\":\"steemit/0.1\"}"
}
]
}2018/04/09 16:38:18
2018/04/09 16:38:18
| voter | ribooripi |
| author | guesshu |
| permlink | bitmain-asic-ethash-miner-and-community-development-recap-last-update-9-apr-2018 |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21420711/Trx 291448d37d5508a73c40f2cd76208ddb53d17c7f |
View Raw JSON Data
{
"trx_id": "291448d37d5508a73c40f2cd76208ddb53d17c7f",
"block": 21420711,
"trx_in_block": 52,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-09T16:38:18",
"op": [
"vote",
{
"voter": "ribooripi",
"author": "guesshu",
"permlink": "bitmain-asic-ethash-miner-and-community-development-recap-last-update-9-apr-2018",
"weight": 10000
}
]
}2018/04/09 06:35:57
2018/04/09 06:35:57
| voter | introduce.bot |
| author | guesshu |
| permlink | bitmain-asic-ethash-miner-and-community-development-recap-last-update-9-apr-2018 |
| weight | 200 (2.00%) |
| Transaction Info | Block #21408665/Trx 9fe35bd35ab922349c60ef681c994d994971940f |
View Raw JSON Data
{
"trx_id": "9fe35bd35ab922349c60ef681c994d994971940f",
"block": 21408665,
"trx_in_block": 19,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-09T06:35:57",
"op": [
"vote",
{
"voter": "introduce.bot",
"author": "guesshu",
"permlink": "bitmain-asic-ethash-miner-and-community-development-recap-last-update-9-apr-2018",
"weight": 200
}
]
}2018/04/09 06:21:54
2018/04/09 06:21:54
| voter | zapper |
| author | guesshu |
| permlink | bitmain-asic-ethash-miner-and-community-development-recap-last-update-9-apr-2018 |
| weight | 100 (1.00%) |
| Transaction Info | Block #21408384/Trx 54f8a76750bc0fe23072a3bc183423faf4bd6f27 |
View Raw JSON Data
{
"trx_id": "54f8a76750bc0fe23072a3bc183423faf4bd6f27",
"block": 21408384,
"trx_in_block": 22,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-09T06:21:54",
"op": [
"vote",
{
"voter": "zapper",
"author": "guesshu",
"permlink": "bitmain-asic-ethash-miner-and-community-development-recap-last-update-9-apr-2018",
"weight": 100
}
]
}guesshupublished a new post: bitmain-asic-ethash-miner-and-community-development-recap-last-update-9-apr-20182018/04/09 06:09:21
guesshupublished a new post: bitmain-asic-ethash-miner-and-community-development-recap-last-update-9-apr-2018
2018/04/09 06:09:21
| parent author | |
| parent permlink | ethereum |
| author | guesshu |
| permlink | bitmain-asic-ethash-miner-and-community-development-recap-last-update-9-apr-2018 |
| title | Bitmain 'Asic' Ethash Miner and Community Development Recap (Last Update: 9 Apr 2018) |
| body | @@ -1317,8 +1317,151 @@ Minutes +: https://github.com/ethereum/pm/blob/master/All%2520Core%2520Devs%2520Meetings/Meeting%252036.md#eip-958-modify-block-mining-to-be-asic-resistant-3206 |
| json metadata | {"tags":["ethereum","mining","gpu","asic","bitmain"],"links":["https://twitter.com/BITMAINtech/status/981169456411021312","https://github.com/ethereum/EIPs/issues/958","https://github.com/ethereum/pm/blob/master/All%20Core%20Devs%20Meetings/Meeting%2036.md#eip-958-modify-block-mining-to-be-asic-resistant-3206"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #21408133/Trx 4543852d47f40a4e6a1e0dc1b087e72aed9ffc44 |
View Raw JSON Data
{
"trx_id": "4543852d47f40a4e6a1e0dc1b087e72aed9ffc44",
"block": 21408133,
"trx_in_block": 34,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-09T06:09:21",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "ethereum",
"author": "guesshu",
"permlink": "bitmain-asic-ethash-miner-and-community-development-recap-last-update-9-apr-2018",
"title": "Bitmain 'Asic' Ethash Miner and Community Development Recap (Last Update: 9 Apr 2018)",
"body": "@@ -1317,8 +1317,151 @@\n Minutes\n+: https://github.com/ethereum/pm/blob/master/All%2520Core%2520Devs%2520Meetings/Meeting%252036.md#eip-958-modify-block-mining-to-be-asic-resistant-3206\n",
"json_metadata": "{\"tags\":[\"ethereum\",\"mining\",\"gpu\",\"asic\",\"bitmain\"],\"links\":[\"https://twitter.com/BITMAINtech/status/981169456411021312\",\"https://github.com/ethereum/EIPs/issues/958\",\"https://github.com/ethereum/pm/blob/master/All%20Core%20Devs%20Meetings/Meeting%2036.md#eip-958-modify-block-mining-to-be-asic-resistant-3206\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}guesshupublished a new post: bitmain-asic-ethash-miner-and-community-development-recap-last-update-9-apr-20182018/04/09 06:05:51
guesshupublished a new post: bitmain-asic-ethash-miner-and-community-development-recap-last-update-9-apr-2018
2018/04/09 06:05:51
| parent author | |
| parent permlink | ethereum |
| author | guesshu |
| permlink | bitmain-asic-ethash-miner-and-community-development-recap-last-update-9-apr-2018 |
| title | Bitmain 'Asic' Ethash Miner and Community Development Recap (Last Update: 9 Apr 2018) |
| body | On 3 Apr 2018, Bitmain officially released [1] their miner product Antminer E3 for cryptocurrencies with hashing algorithm Ethash. Cryptocurrencies impacted are ETH, ETC, EXP and a bunch of other small coins. Bitmain's batch 1 Antminer E3 miners were selling at 800 USD. Batch 2 released on or before 8 Apr 2018 are selling are 1800 USD. Both batches are expected to be shipped during 16-31 July 2018. Prior to this ASIC miner, ETH and other Ethash coins are mined with Graphic Cards (GPUs). This Bitmain announcement is sort of devastating to the GPU miners because ETH was the most profitable coin to mine with GPUs. When this E3 miner ships, there will be a huge hash power upward swing, making existing GPU miners' share of cake (much) smaller and return on investment lower. The response of the ETH community looked promising for GPU miners when EIP: Modify block mining to be ASIC resistant. #958 [2] was getting traction and scheduled to be discussed in Ethereum Core Devs Meeting on 6 Apr 2018 [3]. However, as of writing (9 Apr 2018), the Ethereum Core Devs decide to take no action and leave the EIP open. [1] Batch 1 of Antminer E3 announced on twitter: https://twitter.com/BITMAINtech/status/981169456411021312 [2] https://github.com/ethereum/EIPs/issues/958 [3] 6 Apr 2018 Ethereum Core Devs Meeting Minutes |
| json metadata | {"tags":["ethereum","mining","gpu","asic","bitmain"],"links":["https://twitter.com/BITMAINtech/status/981169456411021312","https://github.com/ethereum/EIPs/issues/958"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #21408063/Trx f14eb444fa70406b4ed1c65f0d69a33dbb024d28 |
View Raw JSON Data
{
"trx_id": "f14eb444fa70406b4ed1c65f0d69a33dbb024d28",
"block": 21408063,
"trx_in_block": 23,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-09T06:05:51",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "ethereum",
"author": "guesshu",
"permlink": "bitmain-asic-ethash-miner-and-community-development-recap-last-update-9-apr-2018",
"title": "Bitmain 'Asic' Ethash Miner and Community Development Recap (Last Update: 9 Apr 2018)",
"body": "On 3 Apr 2018, Bitmain officially released [1] their miner product Antminer E3 for cryptocurrencies with hashing algorithm Ethash. Cryptocurrencies impacted are ETH, ETC, EXP and a bunch of other small coins. \nBitmain's batch 1 Antminer E3 miners were selling at 800 USD. Batch 2 released on or before 8 Apr 2018 are selling are 1800 USD. Both batches are expected to be shipped during 16-31 July 2018.\nPrior to this ASIC miner, ETH and other Ethash coins are mined with Graphic Cards (GPUs). This Bitmain announcement is sort of devastating to the GPU miners because ETH was the most profitable coin to mine with GPUs. When this E3 miner ships, there will be a huge hash power upward swing, making existing GPU miners' share of cake (much) smaller and return on investment lower.\nThe response of the ETH community looked promising for GPU miners when EIP: Modify block mining to be ASIC resistant. #958 [2] was getting traction and scheduled to be discussed in Ethereum Core Devs Meeting on 6 Apr 2018 [3]. \nHowever, as of writing (9 Apr 2018), the Ethereum Core Devs decide to take no action and leave the EIP open.\n\n\n[1] Batch 1 of Antminer E3 announced on twitter: https://twitter.com/BITMAINtech/status/981169456411021312\n[2] https://github.com/ethereum/EIPs/issues/958\n[3] 6 Apr 2018 Ethereum Core Devs Meeting Minutes",
"json_metadata": "{\"tags\":[\"ethereum\",\"mining\",\"gpu\",\"asic\",\"bitmain\"],\"links\":[\"https://twitter.com/BITMAINtech/status/981169456411021312\",\"https://github.com/ethereum/EIPs/issues/958\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}2018/03/13 12:16:03
2018/03/13 12:16:03
| delegator | steem |
| delegatee | guesshu |
| vesting shares | 30421.281894 VESTS |
| Transaction Info | Block #20638948/Trx 2a787b1f0975c77eb8b4a61d5b0a88ea766d7a1f |
View Raw JSON Data
{
"trx_id": "2a787b1f0975c77eb8b4a61d5b0a88ea766d7a1f",
"block": 20638948,
"trx_in_block": 55,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-13T12:16:03",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "guesshu",
"vesting_shares": "30421.281894 VESTS"
}
]
}2018/03/13 11:32:27
2018/03/13 11:32:27
| fee | 0.100 STEEM |
| delegation | 30690.000000 VESTS |
| creator | steem |
| new account name | guesshu |
| owner | {"weight_threshold":1,"account_auths":[],"key_auths":[["STM7UJ1bARAvyZKtv5o8i7vCUg1omHMTD4ivwCZXVdwVXS1yqh1SB",1]]} |
| active | {"weight_threshold":1,"account_auths":[],"key_auths":[["STM5YZcgdwKiZDrwgdGkpShFx1ThBthu5iGkEa89VXginbC1ckLVG",1]]} |
| posting | {"weight_threshold":1,"account_auths":[],"key_auths":[["STM7sUoVyFS5scdHkrqq2jzaoP9NWcbxUAzw7xRqKZbz8tg6663kr",1]]} |
| memo key | STM6v49C9XbNxDEpSocK16s1GrDqfZ8CU7nfbsAnKrBjjDPr9V8DA |
| json metadata | {} |
| extensions | [] |
| Transaction Info | Block #20638077/Trx feb00ad86a4725ef484adb04e2585fe36618084c |
View Raw JSON Data
{
"trx_id": "feb00ad86a4725ef484adb04e2585fe36618084c",
"block": 20638077,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-13T11:32:27",
"op": [
"account_create_with_delegation",
{
"fee": "0.100 STEEM",
"delegation": "30690.000000 VESTS",
"creator": "steem",
"new_account_name": "guesshu",
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7UJ1bARAvyZKtv5o8i7vCUg1omHMTD4ivwCZXVdwVXS1yqh1SB",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5YZcgdwKiZDrwgdGkpShFx1ThBthu5iGkEa89VXginbC1ckLVG",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7sUoVyFS5scdHkrqq2jzaoP9NWcbxUAzw7xRqKZbz8tg6663kr",
1
]
]
},
"memo_key": "STM6v49C9XbNxDEpSocK16s1GrDqfZ8CU7nfbsAnKrBjjDPr9V8DA",
"json_metadata": "{}",
"extensions": []
}
]
}Manabar
Voting Power100.00%
Downvote Power100.00%
Resource Credits100.00%
Reputation Progress0.00%
{
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779065499
},
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779065499
},
"rc_account": {
"account": "guesshu",
"rc_manabar": {
"current_mana": "10164408779",
"last_update_time": 1779065499
},
"max_rc_creation_adjustment": {
"amount": "2020748973",
"precision": 6,
"nai": "@@000000037"
},
"max_rc": "10164408779"
}
}Account Metadata
| POSTING JSON METADATA | |
| None | |
| JSON METADATA | |
| None |
{
"posting_json_metadata": {},
"json_metadata": {}
}Auth Keys
Owner
Single Signature
Public Keys
STM7UJ1bARAvyZKtv5o8i7vCUg1omHMTD4ivwCZXVdwVXS1yqh1SB1/1
Active
Single Signature
Public Keys
STM5YZcgdwKiZDrwgdGkpShFx1ThBthu5iGkEa89VXginbC1ckLVG1/1
Posting
Single Signature
Public Keys
STM7sUoVyFS5scdHkrqq2jzaoP9NWcbxUAzw7xRqKZbz8tg6663kr1/1
Memo
STM6v49C9XbNxDEpSocK16s1GrDqfZ8CU7nfbsAnKrBjjDPr9V8DA
{
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7UJ1bARAvyZKtv5o8i7vCUg1omHMTD4ivwCZXVdwVXS1yqh1SB",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5YZcgdwKiZDrwgdGkpShFx1ThBthu5iGkEa89VXginbC1ckLVG",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7sUoVyFS5scdHkrqq2jzaoP9NWcbxUAzw7xRqKZbz8tg6663kr",
1
]
]
},
"memo": "STM6v49C9XbNxDEpSocK16s1GrDqfZ8CU7nfbsAnKrBjjDPr9V8DA"
}Witness Votes
0 / 30
No active witness votes.
[]