VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS0.00%
Net Worth
0.037USD
STEEM
0.000STEEM
SBD
0.000SBD
Effective Power
5.007SP
├── Own SP
0.634SP
└── Incoming DelegationsDeleg
+4.373SP
Detailed Balance
| STEEM | ||
| balance | 0.000STEEM | STEEM |
| market_balance | 0.000STEEM | STEEM |
| savings_balance | 0.000STEEM | STEEM |
| reward_steem_balance | 0.000STEEM | STEEM |
| STEEM POWER | ||
| Own SP | 0.634SP | SP |
| Delegated Out | 0.000SP | SP |
| Delegation In | 4.373SP | SP |
| Effective Power | 5.007SP | SP |
| Reward SP (pending) | 0.000SP | 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.000SBD | SBD |
{
"balance": "0.000 STEEM",
"savings_balance": "0.000 STEEM",
"reward_steem_balance": "0.000 STEEM",
"vesting_shares": "1031.905087 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "7111.754719 VESTS",
"sbd_balance": "0.000 SBD",
"savings_sbd_balance": "0.000 SBD",
"reward_sbd_balance": "0.000 SBD",
"conversions": []
}Account Info
| name | robmay |
| id | 314340 |
| rank | 1,353,149 |
| reputation | 57439148 |
| created | 2017-08-15T20:55:18 |
| recovery_account | steem |
| proxy | None |
| post_count | 2 |
| comment_count | 0 |
| lifetime_vote_count | 0 |
| witnesses_voted_for | 0 |
| last_post | 2017-11-14T18:04:33 |
| last_root_post | 2017-11-14T18:04:33 |
| last_vote_time | 2017-11-14T18:04:33 |
| proxied_vsf_votes | 0, 0, 0, 0 |
| can_vote | 1 |
| voting_power | 0 |
| delayed_votes | 0 |
| balance | 0.000 STEEM |
| savings_balance | 0.000 STEEM |
| sbd_balance | 0.000 SBD |
| savings_sbd_balance | 0.000 SBD |
| vesting_shares | 1031.905087 VESTS |
| delegated_vesting_shares | 0.000000 VESTS |
| received_vesting_shares | 7111.754719 VESTS |
| reward_vesting_balance | 0.000000 VESTS |
| vesting_balance | 0.000 STEEM |
| vesting_withdraw_rate | 0.000000 VESTS |
| next_vesting_withdrawal | 1969-12-31T23:59:59 |
| withdrawn | 0 |
| to_withdraw | 0 |
| withdraw_routes | 0 |
| savings_withdraw_requests | 0 |
| last_account_recovery | 1970-01-01T00:00:00 |
| reset_account | null |
| last_owner_update | 1970-01-01T00:00:00 |
| last_account_update | 1970-01-01T00:00:00 |
| mined | No |
| sbd_seconds | 0 |
| sbd_last_interest_payment | 1970-01-01T00:00:00 |
| savings_sbd_last_interest_payment | 1970-01-01T00:00:00 |
{
"id": 314340,
"name": "robmay",
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7zPZYbcbgehyXi26stp4E3oUA79YwZMgYZcTehmQZjsQCCCbzP",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7zXCGg7AYgjjQ8xUCp8w1GQianRR1wpRatf98xDPpcftCMi2Hg",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7b3UCGayg6j6uPbBCfnUFktQ2Ygp3jqznqZp4migkSLidXQ8qa",
1
]
]
},
"memo_key": "STM5UUenwm1ow1Q2pcK9szVxmFQobXeUu6pnU23ZTwGVz8ujjEF82",
"json_metadata": "",
"posting_json_metadata": "",
"proxy": "",
"last_owner_update": "1970-01-01T00:00:00",
"last_account_update": "1970-01-01T00:00:00",
"created": "2017-08-15T20:55:18",
"mined": false,
"recovery_account": "steem",
"last_account_recovery": "1970-01-01T00:00:00",
"reset_account": "null",
"comment_count": 0,
"lifetime_vote_count": 0,
"post_count": 2,
"can_vote": true,
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779083328
},
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779083328
},
"voting_power": 0,
"balance": "0.000 STEEM",
"savings_balance": "0.000 STEEM",
"sbd_balance": "0.000 SBD",
"sbd_seconds": "0",
"sbd_seconds_last_update": "1970-01-01T00:00:00",
"sbd_last_interest_payment": "1970-01-01T00:00:00",
"savings_sbd_balance": "0.000 SBD",
"savings_sbd_seconds": "0",
"savings_sbd_seconds_last_update": "1970-01-01T00:00:00",
"savings_sbd_last_interest_payment": "1970-01-01T00:00:00",
"savings_withdraw_requests": 0,
"reward_sbd_balance": "0.000 SBD",
"reward_steem_balance": "0.000 STEEM",
"reward_vesting_balance": "0.000000 VESTS",
"reward_vesting_steem": "0.000 STEEM",
"vesting_shares": "1031.905087 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "7111.754719 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": 0,
"proxied_vsf_votes": [
0,
0,
0,
0
],
"witnesses_voted_for": 0,
"last_post": "2017-11-14T18:04:33",
"last_root_post": "2017-11-14T18:04:33",
"last_vote_time": "2017-11-14T18:04:33",
"post_bandwidth": 0,
"pending_claimed_accounts": 0,
"vesting_balance": "0.000 STEEM",
"reputation": 57439148,
"transfer_history": [],
"market_history": [],
"post_history": [],
"vote_history": [],
"other_history": [],
"witness_votes": [],
"tags_usage": [],
"guest_bloggers": [],
"rank": 1353149
}Withdraw Routes
| Incoming | Outgoing |
|---|---|
Empty | Empty |
{
"incoming": [],
"outgoing": []
}From Date
To Date
2026/05/18 05:48:48
2026/05/18 05:48:48
| delegatee | robmay |
| delegator | steem |
| vesting shares | 7111.754719 VESTS |
| Transaction Info | Block #106150090/Trx f58bac9624d8262c17cab693e59d45f3ad05c453 |
View Raw JSON Data
{
"block": 106150090,
"op": [
"delegate_vesting_shares",
{
"delegatee": "robmay",
"delegator": "steem",
"vesting_shares": "7111.754719 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2026-05-18T05:48:48",
"trx_id": "f58bac9624d8262c17cab693e59d45f3ad05c453",
"trx_in_block": 0,
"virtual_op": 0
}2026/05/13 02:25:48
2026/05/13 02:25:48
| delegatee | robmay |
| delegator | steem |
| vesting shares | 4399.544314 VESTS |
| Transaction Info | Block #106002757/Trx 158372a578e752249c59c5780cf0ebb2da0bca23 |
View Raw JSON Data
{
"block": 106002757,
"op": [
"delegate_vesting_shares",
{
"delegatee": "robmay",
"delegator": "steem",
"vesting_shares": "4399.544314 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2026-05-13T02:25:48",
"trx_id": "158372a578e752249c59c5780cf0ebb2da0bca23",
"trx_in_block": 1,
"virtual_op": 0
}2026/04/26 05:01:12
2026/04/26 05:01:12
| delegatee | robmay |
| delegator | steem |
| vesting shares | 7124.270475 VESTS |
| Transaction Info | Block #105517587/Trx 500bb20d3529e3646025079edeb713a68850143d |
View Raw JSON Data
{
"block": 105517587,
"op": [
"delegate_vesting_shares",
{
"delegatee": "robmay",
"delegator": "steem",
"vesting_shares": "7124.270475 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2026-04-26T05:01:12",
"trx_id": "500bb20d3529e3646025079edeb713a68850143d",
"trx_in_block": 0,
"virtual_op": 0
}2026/01/23 22:45:03
2026/01/23 22:45:03
| delegatee | robmay |
| delegator | steem |
| vesting shares | 4441.091133 VESTS |
| Transaction Info | Block #102869720/Trx 35f4870bdd78147a21b3e86f0372b8cdd0db0891 |
View Raw JSON Data
{
"block": 102869720,
"op": [
"delegate_vesting_shares",
{
"delegatee": "robmay",
"delegator": "steem",
"vesting_shares": "4441.091133 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2026-01-23T22:45:03",
"trx_id": "35f4870bdd78147a21b3e86f0372b8cdd0db0891",
"trx_in_block": 3,
"virtual_op": 0
}2024/12/17 17:55:48
2024/12/17 17:55:48
| delegatee | robmay |
| delegator | steem |
| vesting shares | 4605.310330 VESTS |
| Transaction Info | Block #91315948/Trx 1ed0c76fd9ad7a3a7dfdb40f6df960dce51ab898 |
View Raw JSON Data
{
"block": 91315948,
"op": [
"delegate_vesting_shares",
{
"delegatee": "robmay",
"delegator": "steem",
"vesting_shares": "4605.310330 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2024-12-17T17:55:48",
"trx_id": "1ed0c76fd9ad7a3a7dfdb40f6df960dce51ab898",
"trx_in_block": 0,
"virtual_op": 0
}2023/11/14 09:37:03
2023/11/14 09:37:03
| delegatee | robmay |
| delegator | steem |
| vesting shares | 4774.443862 VESTS |
| Transaction Info | Block #79870100/Trx 3f6cf2338d73c1e2b49ef5a3c30a718bed1f04c0 |
View Raw JSON Data
{
"block": 79870100,
"op": [
"delegate_vesting_shares",
{
"delegatee": "robmay",
"delegator": "steem",
"vesting_shares": "4774.443862 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2023-11-14T09:37:03",
"trx_id": "3f6cf2338d73c1e2b49ef5a3c30a718bed1f04c0",
"trx_in_block": 10,
"virtual_op": 0
}2023/09/22 09:49:51
2023/09/22 09:49:51
| delegatee | robmay |
| delegator | steem |
| vesting shares | 7711.352648 VESTS |
| Transaction Info | Block #78362194/Trx 27a4f70b95d3959e746cc2703c890e88a74e7fc0 |
View Raw JSON Data
{
"block": 78362194,
"op": [
"delegate_vesting_shares",
{
"delegatee": "robmay",
"delegator": "steem",
"vesting_shares": "7711.352648 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2023-09-22T09:49:51",
"trx_id": "27a4f70b95d3959e746cc2703c890e88a74e7fc0",
"trx_in_block": 4,
"virtual_op": 0
}2022/11/03 17:21:45
2022/11/03 17:21:45
| delegatee | robmay |
| delegator | steem |
| vesting shares | 7933.404086 VESTS |
| Transaction Info | Block #69120020/Trx ee4bd5f5d99aedc83d52a3554ce28f5890b4242c |
View Raw JSON Data
{
"block": 69120020,
"op": [
"delegate_vesting_shares",
{
"delegatee": "robmay",
"delegator": "steem",
"vesting_shares": "7933.404086 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2022-11-03T17:21:45",
"trx_id": "ee4bd5f5d99aedc83d52a3554ce28f5890b4242c",
"trx_in_block": 2,
"virtual_op": 0
}2022/01/17 22:36:30
2022/01/17 22:36:30
| delegatee | robmay |
| delegator | steem |
| vesting shares | 8153.511687 VESTS |
| Transaction Info | Block #60823325/Trx dcc2e44626ea329c4f383f852329134285d1f3da |
View Raw JSON Data
{
"block": 60823325,
"op": [
"delegate_vesting_shares",
{
"delegatee": "robmay",
"delegator": "steem",
"vesting_shares": "8153.511687 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2022-01-17T22:36:30",
"trx_id": "dcc2e44626ea329c4f383f852329134285d1f3da",
"trx_in_block": 18,
"virtual_op": 0
}2021/06/14 05:48:42
2021/06/14 05:48:42
| delegatee | robmay |
| delegator | steem |
| vesting shares | 8337.705975 VESTS |
| Transaction Info | Block #54613677/Trx 41176aa631706417cd1c501b719a939971977519 |
View Raw JSON Data
{
"block": 54613677,
"op": [
"delegate_vesting_shares",
{
"delegatee": "robmay",
"delegator": "steem",
"vesting_shares": "8337.705975 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2021-06-14T05:48:42",
"trx_id": "41176aa631706417cd1c501b719a939971977519",
"trx_in_block": 1,
"virtual_op": 0
}2020/12/11 16:01:18
2020/12/11 16:01:18
| delegatee | robmay |
| delegator | steem |
| vesting shares | 8525.127949 VESTS |
| Transaction Info | Block #49360951/Trx 41de7d29ddfc521b9d747c5dce472921728f36a0 |
View Raw JSON Data
{
"block": 49360951,
"op": [
"delegate_vesting_shares",
{
"delegatee": "robmay",
"delegator": "steem",
"vesting_shares": "8525.127949 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-12-11T16:01:18",
"trx_id": "41de7d29ddfc521b9d747c5dce472921728f36a0",
"trx_in_block": 1,
"virtual_op": 0
}2020/12/06 09:37:15
2020/12/06 09:37:15
| delegatee | robmay |
| delegator | steem |
| vesting shares | 1912.543513 VESTS |
| Transaction Info | Block #49212482/Trx 5097494342e419d50934272829b72edc99f6d9b7 |
View Raw JSON Data
{
"block": 49212482,
"op": [
"delegate_vesting_shares",
{
"delegatee": "robmay",
"delegator": "steem",
"vesting_shares": "1912.543513 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-12-06T09:37:15",
"trx_id": "5097494342e419d50934272829b72edc99f6d9b7",
"trx_in_block": 0,
"virtual_op": 0
}2020/12/05 19:39:18
2020/12/05 19:39:18
| delegatee | robmay |
| delegator | steem |
| vesting shares | 8531.335803 VESTS |
| Transaction Info | Block #49196038/Trx a023e548f85aa35cb07d8bb882bcb3f77f5498dd |
View Raw JSON Data
{
"block": 49196038,
"op": [
"delegate_vesting_shares",
{
"delegatee": "robmay",
"delegator": "steem",
"vesting_shares": "8531.335803 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-12-05T19:39:18",
"trx_id": "a023e548f85aa35cb07d8bb882bcb3f77f5498dd",
"trx_in_block": 2,
"virtual_op": 0
}2020/11/03 01:50:57
2020/11/03 01:50:57
| delegatee | robmay |
| delegator | steem |
| vesting shares | 1920.017158 VESTS |
| Transaction Info | Block #48269823/Trx d44461424af3726e2a54500276aec84bfee07a8b |
View Raw JSON Data
{
"block": 48269823,
"op": [
"delegate_vesting_shares",
{
"delegatee": "robmay",
"delegator": "steem",
"vesting_shares": "1920.017158 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-11-03T01:50:57",
"trx_id": "d44461424af3726e2a54500276aec84bfee07a8b",
"trx_in_block": 5,
"virtual_op": 0
}2020/05/09 10:39:54
2020/05/09 10:39:54
| delegatee | robmay |
| delegator | steem |
| vesting shares | 8734.141162 VESTS |
| Transaction Info | Block #43222803/Trx e4e291dd88d0ed9e03be0cda731560d7fec3d17f |
View Raw JSON Data
{
"block": 43222803,
"op": [
"delegate_vesting_shares",
{
"delegatee": "robmay",
"delegator": "steem",
"vesting_shares": "8734.141162 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-05-09T10:39:54",
"trx_id": "e4e291dd88d0ed9e03be0cda731560d7fec3d17f",
"trx_in_block": 9,
"virtual_op": 0
}2020/05/08 15:00:24
2020/05/08 15:00:24
| delegatee | robmay |
| delegator | steem |
| vesting shares | 1953.311140 VESTS |
| Transaction Info | Block #43199773/Trx c63166ffd188fecbc1f87f2908cd025026ed66ac |
View Raw JSON Data
{
"block": 43199773,
"op": [
"delegate_vesting_shares",
{
"delegatee": "robmay",
"delegator": "steem",
"vesting_shares": "1953.311140 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-05-08T15:00:24",
"trx_id": "c63166ffd188fecbc1f87f2908cd025026ed66ac",
"trx_in_block": 17,
"virtual_op": 0
}2020/04/16 03:00:36
2020/04/16 03:00:36
| delegatee | robmay |
| delegator | steem |
| vesting shares | 8747.028610 VESTS |
| Transaction Info | Block #42568822/Trx 4ca5517ab6a14fcd046dfcb690edd2be48f712cd |
View Raw JSON Data
{
"block": 42568822,
"op": [
"delegate_vesting_shares",
{
"delegatee": "robmay",
"delegator": "steem",
"vesting_shares": "8747.028610 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-04-16T03:00:36",
"trx_id": "4ca5517ab6a14fcd046dfcb690edd2be48f712cd",
"trx_in_block": 40,
"virtual_op": 0
}2019/08/15 21:24:39
2019/08/15 21:24:39
| author | steemitboard |
| body | Congratulations @robmay! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@robmay/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/@robmay) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=robmay)_</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"]} |
| parent author | robmay |
| parent permlink | fuck-the-whitepaper-how-to-really-evaluate-new-networks-and-tokens |
| permlink | steemitboard-notify-robmay-20190815t212438000z |
| title | |
| Transaction Info | Block #35584438/Trx c3e3fa5a51c509bda2cbe876f565c9c6d83bb878 |
View Raw JSON Data
{
"block": 35584438,
"op": [
"comment",
{
"author": "steemitboard",
"body": "Congratulations @robmay! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@robmay/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/@robmay) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=robmay)_</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\"]}",
"parent_author": "robmay",
"parent_permlink": "fuck-the-whitepaper-how-to-really-evaluate-new-networks-and-tokens",
"permlink": "steemitboard-notify-robmay-20190815t212438000z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2019-08-15T21:24:39",
"trx_id": "c3e3fa5a51c509bda2cbe876f565c9c6d83bb878",
"trx_in_block": 5,
"virtual_op": 0
}2019/05/12 20:07:42
2019/05/12 20:07:42
| delegatee | robmay |
| delegator | steem |
| vesting shares | 8942.645423 VESTS |
| Transaction Info | Block #32851755/Trx 8be3e26c74dfd4cdf0ca3b7845294512a30d7daa |
View Raw JSON Data
{
"block": 32851755,
"op": [
"delegate_vesting_shares",
{
"delegatee": "robmay",
"delegator": "steem",
"vesting_shares": "8942.645423 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2019-05-12T20:07:42",
"trx_id": "8be3e26c74dfd4cdf0ca3b7845294512a30d7daa",
"trx_in_block": 27,
"virtual_op": 0
}2018/05/17 00:03:15
2018/05/17 00:03:15
| delegatee | robmay |
| delegator | steem |
| vesting shares | 9142.256291 VESTS |
| Transaction Info | Block #22494366/Trx 259cd6f5e7fce7a942113ce8ce668af6b0f37759 |
View Raw JSON Data
{
"block": 22494366,
"op": [
"delegate_vesting_shares",
{
"delegatee": "robmay",
"delegator": "steem",
"vesting_shares": "9142.256291 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2018-05-17T00:03:15",
"trx_id": "259cd6f5e7fce7a942113ce8ce668af6b0f37759",
"trx_in_block": 12,
"virtual_op": 0
}2018/02/22 12:28:45
2018/02/22 12:28:45
| delegatee | robmay |
| delegator | steem |
| vesting shares | 29624.218822 VESTS |
| Transaction Info | Block #20092603/Trx 4f85809cf1f0c6a29b90fc177d98593095da733a |
View Raw JSON Data
{
"block": 20092603,
"op": [
"delegate_vesting_shares",
{
"delegatee": "robmay",
"delegator": "steem",
"vesting_shares": "29624.218822 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2018-02-22T12:28:45",
"trx_id": "4f85809cf1f0c6a29b90fc177d98593095da733a",
"trx_in_block": 11,
"virtual_op": 0
}2017/11/27 05:26:03
2017/11/27 05:26:03
| author | robmay |
| permlink | fuck-the-whitepaper-how-to-really-evaluate-new-networks-and-tokens |
| voter | smartonelegal |
| weight | 100 (1.00%) |
| Transaction Info | Block #17580536/Trx d5ee6c1c7eaca291325f64546f893d2e544ae491 |
View Raw JSON Data
{
"block": 17580536,
"op": [
"vote",
{
"author": "robmay",
"permlink": "fuck-the-whitepaper-how-to-really-evaluate-new-networks-and-tokens",
"voter": "smartonelegal",
"weight": 100
}
],
"op_in_trx": 0,
"timestamp": "2017-11-27T05:26:03",
"trx_id": "d5ee6c1c7eaca291325f64546f893d2e544ae491",
"trx_in_block": 3,
"virtual_op": 0
}2017/11/24 12:42:45
2017/11/24 12:42:45
| author | robmay |
| permlink | fuck-the-whitepaper-how-to-really-evaluate-new-networks-and-tokens |
| voter | mindsportsio |
| weight | 100 (1.00%) |
| Transaction Info | Block #17502876/Trx 07d64f5e1a9b2527f9a1b857dc6a5f733ae13603 |
View Raw JSON Data
{
"block": 17502876,
"op": [
"vote",
{
"author": "robmay",
"permlink": "fuck-the-whitepaper-how-to-really-evaluate-new-networks-and-tokens",
"voter": "mindsportsio",
"weight": 100
}
],
"op_in_trx": 0,
"timestamp": "2017-11-24T12:42:45",
"trx_id": "07d64f5e1a9b2527f9a1b857dc6a5f733ae13603",
"trx_in_block": 5,
"virtual_op": 0
}2017/11/19 22:28:33
2017/11/19 22:28:33
| author | robmay |
| permlink | talla-announces-botchain-a-blockchain-security-and-compliance-solution-for-autonomous-agents |
| voter | wendt |
| weight | 10000 (100.00%) |
| Transaction Info | Block #17370672/Trx ce151e93719b18d9ccf94a13ad07cbb8e4163fe4 |
View Raw JSON Data
{
"block": 17370672,
"op": [
"vote",
{
"author": "robmay",
"permlink": "talla-announces-botchain-a-blockchain-security-and-compliance-solution-for-autonomous-agents",
"voter": "wendt",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-11-19T22:28:33",
"trx_id": "ce151e93719b18d9ccf94a13ad07cbb8e4163fe4",
"trx_in_block": 13,
"virtual_op": 0
}robmayupvoted (100.00%) @robmay / fuck-the-whitepaper-how-to-really-evaluate-new-networks-and-tokens2017/11/14 18:04:33
robmayupvoted (100.00%) @robmay / fuck-the-whitepaper-how-to-really-evaluate-new-networks-and-tokens
2017/11/14 18:04:33
| author | robmay |
| permlink | fuck-the-whitepaper-how-to-really-evaluate-new-networks-and-tokens |
| voter | robmay |
| weight | 10000 (100.00%) |
| Transaction Info | Block #17221429/Trx 5c676ab4540731051a2974d8a1cbbe7e32a59055 |
View Raw JSON Data
{
"block": 17221429,
"op": [
"vote",
{
"author": "robmay",
"permlink": "fuck-the-whitepaper-how-to-really-evaluate-new-networks-and-tokens",
"voter": "robmay",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-11-14T18:04:33",
"trx_id": "5c676ab4540731051a2974d8a1cbbe7e32a59055",
"trx_in_block": 12,
"virtual_op": 0
}robmaypublished a new post: fuck-the-whitepaper-how-to-really-evaluate-new-networks-and-tokens2017/11/14 18:04:33
robmaypublished a new post: fuck-the-whitepaper-how-to-really-evaluate-new-networks-and-tokens
2017/11/14 18:04:33
| author | robmay |
| body | If you have spent any time in the cryptocurrency space, or looking into ICOs, you know that the process revolves around “the white paper.” The white paper is a document that lays out facts about the blockchain, protocol, or dapp that is being built, and describes how the tokens will work. Sometimes it is a deeply technical document. Other times it is mostly marketing. I think it is mostly irrelevant. Cryptoinvestors love white papers, although, I’m not sure they really read them. Mostly they skim them and then ask “why can’t you do this with a database instead of a blockchain?” It’s a valid question. Of course, it’s also a valid question why you even need a database. You could use a spreadsheet instead, or even a comma delimited file. Or you could in fact chisel your ledger on stone tablets too. Most cryptoinvestors don’t ask good questions. In fact, most crypto forums are filled with posts of people asking the same thing over and over, or issuing the same 3 or 4 criticisms of blockchains that they read somewhere else. But blockchains, and the general concept of decentralized systems, unlock a lot of new cool possibilities. And the way to understand those isn’t to evaluate the technical merits of a blockchain via the whitepaper. It’s like evaluating Amazon’s e-commerce capabilities based on their low level server infrastructure design. Blockchain technology is early, and as such, it should be evaluated more like the way startups are evaluated. And focusing on the underlying technology via the whitepaper is akin to looking primarily at a startup’s architecture diagrams to decide if you should invest. It makes no sense. It’s one small data point out of many. The thing token buyers are missing when they look at a whitepaper is that the blockchain under consideration will almost certainly change. Why? Because technology changes. Use cases will expand. Other blockchains will compete for attention. In other words, innovation happens and there is no reason to think it won’t happen to blockchains. What you really want to think about then, is how that happens for the dapp/blockchain/network you are evaluating. I think it is much much better to evaluate a blockchain the way you evaluate a startup — you assume the starting point is a starting point, not an end point. Crypto buyers seem to me to evaluate a white paper like a final product, and that is where they go wrong. When I look at crypto deals, I think about a different set of things. I think about where they are starting and where they are likely to be in a decade, and the path to get there. If you want to evaluate opportunities that way, here are 4things to consider: Team — This is what I look at first. Building a network is HARD. Can this team attract partners and participants? Most of the ones I see are doubtful. I look for a team that isn’t just a bunch of super techie blockchain dudes. I want to see business people who understand marketing and evangelizing. Vision — Where is this network going? What are the possibilities past the first use case? The more a network can do long term, the more valuable it will be. Scope — How broad or narrowly defined are the use cases for this blockchain? This is a hard one, and it is similar to how one might evaluate a new software application. Too broad and the messaging/positioning get diluted. The tool gets eaten alive by more focused competitors. Too narrow and targeted and the tool owns a small niche and never grows out of it. Scope of a blockchain’s use cases is a major criteria for me. New vs Existing Market — I know my opinion here is in the minority but, I just don’t believe blockchains are going to disrupt most existing markets. I think they are going to enable new markets where trust was difficult before, and now it is possible. I’m down on blockchains for things like real estate. So, the next time you look at a token or a network, just skim the whitepaper. Make it a secondary factor in your decision, not the primary thing you buy on. Spend your time instead looking at the team, understanding the big vision, researching the market opportunity, and thinking counterfactually about the possible futures of the network. You’ll make better decisions. |
| json metadata | {"tags":["cryptocurrency","blockchain"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | cryptocurrency |
| permlink | fuck-the-whitepaper-how-to-really-evaluate-new-networks-and-tokens |
| title | Fuck The Whitepaper: How To Really Evaluate New Networks and Tokens |
| Transaction Info | Block #17221429/Trx 5c676ab4540731051a2974d8a1cbbe7e32a59055 |
View Raw JSON Data
{
"block": 17221429,
"op": [
"comment",
{
"author": "robmay",
"body": "If you have spent any time in the cryptocurrency space, or looking into ICOs, you know that the process revolves around “the white paper.” The white paper is a document that lays out facts about the blockchain, protocol, or dapp that is being built, and describes how the tokens will work. Sometimes it is a deeply technical document. Other times it is mostly marketing. I think it is mostly irrelevant.\n\nCryptoinvestors love white papers, although, I’m not sure they really read them. Mostly they skim them and then ask “why can’t you do this with a database instead of a blockchain?” It’s a valid question. Of course, it’s also a valid question why you even need a database. You could use a spreadsheet instead, or even a comma delimited file. Or you could in fact chisel your ledger on stone tablets too.\n\nMost cryptoinvestors don’t ask good questions. In fact, most crypto forums are filled with posts of people asking the same thing over and over, or issuing the same 3 or 4 criticisms of blockchains that they read somewhere else. But blockchains, and the general concept of decentralized systems, unlock a lot of new cool possibilities. And the way to understand those isn’t to evaluate the technical merits of a blockchain via the whitepaper. It’s like evaluating Amazon’s e-commerce capabilities based on their low level server infrastructure design.\n\nBlockchain technology is early, and as such, it should be evaluated more like the way startups are evaluated. And focusing on the underlying technology via the whitepaper is akin to looking primarily at a startup’s architecture diagrams to decide if you should invest. It makes no sense. It’s one small data point out of many.\n\nThe thing token buyers are missing when they look at a whitepaper is that the blockchain under consideration will almost certainly change. Why? Because technology changes. Use cases will expand. Other blockchains will compete for attention. In other words, innovation happens and there is no reason to think it won’t happen to blockchains. What you really want to think about then, is how that happens for the dapp/blockchain/network you are evaluating.\n\nI think it is much much better to evaluate a blockchain the way you evaluate a startup — you assume the starting point is a starting point, not an end point. Crypto buyers seem to me to evaluate a white paper like a final product, and that is where they go wrong. When I look at crypto deals, I think about a different set of things. I think about where they are starting and where they are likely to be in a decade, and the path to get there.\n\nIf you want to evaluate opportunities that way, here are 4things to consider:\n\nTeam — This is what I look at first. Building a network is HARD. Can this team attract partners and participants? Most of the ones I see are doubtful. I look for a team that isn’t just a bunch of super techie blockchain dudes. I want to see business people who understand marketing and evangelizing.\n\nVision — Where is this network going? What are the possibilities past the first use case? The more a network can do long term, the more valuable it will be.\n\nScope — How broad or narrowly defined are the use cases for this blockchain? This is a hard one, and it is similar to how one might evaluate a new software application. Too broad and the messaging/positioning get diluted. The tool gets eaten alive by more focused competitors. Too narrow and targeted and the tool owns a small niche and never grows out of it. Scope of a blockchain’s use cases is a major criteria for me.\n\nNew vs Existing Market — I know my opinion here is in the minority but, I just don’t believe blockchains are going to disrupt most existing markets. I think they are going to enable new markets where trust was difficult before, and now it is possible. I’m down on blockchains for things like real estate.\n\nSo, the next time you look at a token or a network, just skim the whitepaper. Make it a secondary factor in your decision, not the primary thing you buy on. Spend your time instead looking at the team, understanding the big vision, researching the market opportunity, and thinking counterfactually about the possible futures of the network. You’ll make better decisions.",
"json_metadata": "{\"tags\":[\"cryptocurrency\",\"blockchain\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "cryptocurrency",
"permlink": "fuck-the-whitepaper-how-to-really-evaluate-new-networks-and-tokens",
"title": "Fuck The Whitepaper: How To Really Evaluate New Networks and Tokens"
}
],
"op_in_trx": 0,
"timestamp": "2017-11-14T18:04:33",
"trx_id": "5c676ab4540731051a2974d8a1cbbe7e32a59055",
"trx_in_block": 12,
"virtual_op": 0
}2017/10/13 16:18:33
2017/10/13 16:18:33
| delegatee | robmay |
| delegator | steem |
| vesting shares | 29829.094913 VESTS |
| Transaction Info | Block #16298553/Trx c528522eae837d6f3c7f2a97b606f67bf8f4e970 |
View Raw JSON Data
{
"block": 16298553,
"op": [
"delegate_vesting_shares",
{
"delegatee": "robmay",
"delegator": "steem",
"vesting_shares": "29829.094913 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2017-10-13T16:18:33",
"trx_id": "c528522eae837d6f3c7f2a97b606f67bf8f4e970",
"trx_in_block": 4,
"virtual_op": 0
}2017/09/13 22:34:00
2017/09/13 22:34:00
| author | robmay |
| permlink | talla-announces-botchain-a-blockchain-security-and-compliance-solution-for-autonomous-agents |
| voter | willmurphy |
| weight | 10000 (100.00%) |
| Transaction Info | Block #15442498/Trx 4f1cce176c286bb294cbb252ac4b65c0a14d76fb |
View Raw JSON Data
{
"block": 15442498,
"op": [
"vote",
{
"author": "robmay",
"permlink": "talla-announces-botchain-a-blockchain-security-and-compliance-solution-for-autonomous-agents",
"voter": "willmurphy",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-09-13T22:34:00",
"trx_id": "4f1cce176c286bb294cbb252ac4b65c0a14d76fb",
"trx_in_block": 0,
"virtual_op": 0
}robmayupvoted (100.00%) @jrcornel / is-it-possible-to-find-bitcoin-s-intrinsic-value2017/09/13 20:47:24
robmayupvoted (100.00%) @jrcornel / is-it-possible-to-find-bitcoin-s-intrinsic-value
2017/09/13 20:47:24
| author | jrcornel |
| permlink | is-it-possible-to-find-bitcoin-s-intrinsic-value |
| voter | robmay |
| weight | 10000 (100.00%) |
| Transaction Info | Block #15440368/Trx acf64037ae4da45abcd8da47580a76da857411d4 |
View Raw JSON Data
{
"block": 15440368,
"op": [
"vote",
{
"author": "jrcornel",
"permlink": "is-it-possible-to-find-bitcoin-s-intrinsic-value",
"voter": "robmay",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-09-13T20:47:24",
"trx_id": "acf64037ae4da45abcd8da47580a76da857411d4",
"trx_in_block": 6,
"virtual_op": 0
}2017/09/13 18:03:03
2017/09/13 18:03:03
| author | robmay |
| permlink | talla-announces-botchain-a-blockchain-security-and-compliance-solution-for-autonomous-agents |
| voter | ubg |
| weight | 100 (1.00%) |
| Transaction Info | Block #15437081/Trx e8e8c3437c915c55b8a6e7e0dc65b85f1256d76c |
View Raw JSON Data
{
"block": 15437081,
"op": [
"vote",
{
"author": "robmay",
"permlink": "talla-announces-botchain-a-blockchain-security-and-compliance-solution-for-autonomous-agents",
"voter": "ubg",
"weight": 100
}
],
"op_in_trx": 0,
"timestamp": "2017-09-13T18:03:03",
"trx_id": "e8e8c3437c915c55b8a6e7e0dc65b85f1256d76c",
"trx_in_block": 10,
"virtual_op": 0
}2017/09/13 17:33:21
2017/09/13 17:33:21
| author | robmay |
| permlink | talla-announces-botchain-a-blockchain-security-and-compliance-solution-for-autonomous-agents |
| voter | robmay |
| weight | 10000 (100.00%) |
| Transaction Info | Block #15436487/Trx d4df566ea264fa0affd7128efc84ff92de8b6118 |
View Raw JSON Data
{
"block": 15436487,
"op": [
"vote",
{
"author": "robmay",
"permlink": "talla-announces-botchain-a-blockchain-security-and-compliance-solution-for-autonomous-agents",
"voter": "robmay",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-09-13T17:33:21",
"trx_id": "d4df566ea264fa0affd7128efc84ff92de8b6118",
"trx_in_block": 18,
"virtual_op": 0
}2017/09/13 17:33:03
2017/09/13 17:33:03
| author | robmay |
| body | Today I’m excited to announce the private beta program for a new concept — the botchain. As bots proliferate in the enterprise, the problem arises of how to create trust between agent and human, or agent to agent. The botchain allows an autonomous agent to be verified so that bots can be spoofed or spam. It allows an autonomous agent to create a hash of it's current environment (neural model, timestamp, owner, etc) and attach a digital certificate to each task it completes that is immutable on the blockchain. It also allows two autonomous A.I. agents to record transactions between them on an immutable decentralized ledger, and to enforce policies on individual bots to set the limits of their responsibilities. We believe this is a necessity to enable the enterprise bot ecosystem to move forward, and so I have taken some time below to explain why this necessary and what it entails. Talla is nearly two years old now, and from the very early days, we started talking about how the enterprise bot world would progress. As Talla grew in functionality, many of our customers began asking if we could split the product into multiple bots depending on use case. We quickly realized that if the world starts going this way, there will be a lot of scenarios where enterprise bots need to talk to each other. And since bots are autonomous programs that can learn, make decisions, and will do even more over time - that presents some problems. The botchain is designed to work on several use cases, on behalf of companies (not consumers) when they need their agents to do something. (We don’t intend to deal with customer to company interactions, but stay B2B focused). The roadmap here is long, and will be detailed in a couple of weeks when we launch our whitepaper, but, here are three things we think are valuable reasons that a botchain should exist. **Audit and Legal Trails** — Let’s say I send you an invoice for $500,000. You send it back and say you didn’t buy my service. I say yes, and present you with a contract signed by John Smith at your office. You show it to John Smith, who says he never signed that. I sue you in court for $500,000. How does this get resolved? In most cases, we turn to email archives, which is why email archiving systems exist. Now, as bots start to make simple decisions for us, there will end up being many times when we want to dig in and understand why the decision was made, how the conversation happened, or possibly share the transaction with an auditor, lawyer, or other. While we could build a bot message archiver without a blockchain, we think that since blockchains are essentially a decentralized trust mechanism, that an immutable decentralized ledger of these types of communications is a valuable thing to the ecosystem, and a better way to do it. On a similar note, what happens when autonomous agents, doing work on behalf of humans, deal with HIPAA data, or have to be part of a SOC2 compliance program - how do you verify what they did? **Bot Identity, Privacy, and Policy** — As two autonomous agents transact, how do we know what they are allowed to do? How do we know the bot we are dealing with is really the right bot, and that is has the permission to engage in the transaction it is proposing? A decentralized identity verification mechanism for bots and bot policy makes a lot of sense. **Marketplace For Bot Add-Ons, and Code Enforcement **— As artificial intelligence progresses and bots get more complex, there will be opportunities for third parties to release skill and knowledge modules that can upgrade a bot’s brain. We think it dangerous to have one single company control such a marketplace, but given what we have seen in other ecosystems like mobile and social, it is a likely outcome if the marketplace doesn’t live on a blockchain. Today, APIs deal with program to program communication via clear rules. What happens as they become more intelligent, and the rules are probabilistic? When you deploy a reinforcement learning model to an API endpoint (which is one way to look at an intelligent agent) how do you know what it did, and if it did the right thing? We will open up a larger beta once the botchain supports use case s #1 and #2. We will also announce the details soon of a token generation event, where the tokens will be a universal unit of access and payment across the botchain. For now, you can keep tabs on the botchain, or get more information at https://talla.com/botchain. We decided to make this announcement first here on Steemit, because we've bought in to the blockchain, and we think the community here can provide the best feedback to help us shape the future of autonomous agents on the blockchain. We are currently targeting Ethereum and Swirlds for this project, but we welcome your ideas. |
| json metadata | {"tags":["ai","blockchain","nlp","ico"],"links":["https://talla.com/botchain"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | ai |
| permlink | talla-announces-botchain-a-blockchain-security-and-compliance-solution-for-autonomous-agents |
| title | Talla Announces Botchain: A Blockchain Security and Compliance Solution For Autonomous Agents |
| Transaction Info | Block #15436481/Trx 91a78b6abd6fe3b45e74a23b9999300f98fd4aa5 |
View Raw JSON Data
{
"block": 15436481,
"op": [
"comment",
{
"author": "robmay",
"body": "Today I’m excited to announce the private beta program for a new concept — the botchain. As bots proliferate in the enterprise, the problem arises of how to create trust between agent and human, or agent to agent. The botchain allows an autonomous agent to be verified so that bots can be spoofed or spam. It allows an autonomous agent to create a hash of it's current environment (neural model, timestamp, owner, etc) and attach a digital certificate to each task it completes that is immutable on the blockchain. It also allows two autonomous A.I. agents to record transactions between them on an immutable decentralized ledger, and to enforce policies on individual bots to set the limits of their responsibilities. We believe this is a necessity to enable the enterprise bot ecosystem to move forward, and so I have taken some time below to explain why this necessary and what it entails.\n\nTalla is nearly two years old now, and from the very early days, we started talking about how the enterprise bot world would progress. As Talla grew in functionality, many of our customers began asking if we could split the product into multiple bots depending on use case. We quickly realized that if the world starts going this way, there will be a lot of scenarios where enterprise bots need to talk to each other. And since bots are autonomous programs that can learn, make decisions, and will do even more over time - that presents some problems. \n\nThe botchain is designed to work on several use cases, on behalf of companies (not consumers) when they need their agents to do something. (We don’t intend to deal with customer to company interactions, but stay B2B focused). The roadmap here is long, and will be detailed in a couple of weeks when we launch our whitepaper, but, here are three things we think are valuable reasons that a botchain should exist. \n\n**Audit and Legal Trails** — Let’s say I send you an invoice for $500,000. You send it back and say you didn’t buy my service. I say yes, and present you with a contract signed by John Smith at your office. You show it to John Smith, who says he never signed that. I sue you in court for $500,000. How does this get resolved? In most cases, we turn to email archives, which is why email archiving systems exist. Now, as bots start to make simple decisions for us, there will end up being many times when we want to dig in and understand why the decision was made, how the conversation happened, or possibly share the transaction with an auditor, lawyer, or other. While we could build a bot message archiver without a blockchain, we think that since blockchains are essentially a decentralized trust mechanism, that an immutable decentralized ledger of these types of communications is a valuable thing to the ecosystem, and a better way to do it.\n\nOn a similar note, what happens when autonomous agents, doing work on behalf of humans, deal with HIPAA data, or have to be part of a SOC2 compliance program - how do you verify what they did?\n\n**Bot Identity, Privacy, and Policy** — As two autonomous agents transact, how do we know what they are allowed to do? How do we know the bot we are dealing with is really the right bot, and that is has the permission to engage in the transaction it is proposing? A decentralized identity verification mechanism for bots and bot policy makes a lot of sense.\n\n**Marketplace For Bot Add-Ons, and Code Enforcement **— As artificial intelligence progresses and bots get more complex, there will be opportunities for third parties to release skill and knowledge modules that can upgrade a bot’s brain. We think it dangerous to have one single company control such a marketplace, but given what we have seen in other ecosystems like mobile and social, it is a likely outcome if the marketplace doesn’t live on a blockchain. \n\nToday, APIs deal with program to program communication via clear rules. What happens as they become more intelligent, and the rules are probabilistic? When you deploy a reinforcement learning model to an API endpoint (which is one way to look at an intelligent agent) how do you know what it did, and if it did the right thing? \n\nWe will open up a larger beta once the botchain supports use case s #1 and #2. We will also announce the details soon of a token generation event, where the tokens will be a universal unit of access and payment across the botchain. For now, you can keep tabs on the botchain, or get more information at https://talla.com/botchain.\n\nWe decided to make this announcement first here on Steemit, because we've bought in to the blockchain, and we think the community here can provide the best feedback to help us shape the future of autonomous agents on the blockchain. We are currently targeting Ethereum and Swirlds for this project, but we welcome your ideas.",
"json_metadata": "{\"tags\":[\"ai\",\"blockchain\",\"nlp\",\"ico\"],\"links\":[\"https://talla.com/botchain\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "ai",
"permlink": "talla-announces-botchain-a-blockchain-security-and-compliance-solution-for-autonomous-agents",
"title": "Talla Announces Botchain: A Blockchain Security and Compliance Solution For Autonomous Agents"
}
],
"op_in_trx": 0,
"timestamp": "2017-09-13T17:33:03",
"trx_id": "91a78b6abd6fe3b45e74a23b9999300f98fd4aa5",
"trx_in_block": 22,
"virtual_op": 0
}2017/08/22 00:52:27
2017/08/22 00:52:27
| author | kingscrown |
| permlink | steem-exchange-that-almost-always-have-deposits-and-withdrawals-working |
| voter | robmay |
| weight | 10000 (100.00%) |
| Transaction Info | Block #14783239/Trx 545673c12da28d67ee95c14db7852ef7c8a156aa |
View Raw JSON Data
{
"block": 14783239,
"op": [
"vote",
{
"author": "kingscrown",
"permlink": "steem-exchange-that-almost-always-have-deposits-and-withdrawals-working",
"voter": "robmay",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-08-22T00:52:27",
"trx_id": "545673c12da28d67ee95c14db7852ef7c8a156aa",
"trx_in_block": 15,
"virtual_op": 0
}robmayupvoted (100.00%) @cryptohustlin / steemit-advertising-campaign-part-222017/08/16 12:16:57
robmayupvoted (100.00%) @cryptohustlin / steemit-advertising-campaign-part-22
2017/08/16 12:16:57
| author | cryptohustlin |
| permlink | steemit-advertising-campaign-part-22 |
| voter | robmay |
| weight | 10000 (100.00%) |
| Transaction Info | Block #14624276/Trx 6b2ae5af40b26221ba361af9c8546c7b8c6250ac |
View Raw JSON Data
{
"block": 14624276,
"op": [
"vote",
{
"author": "cryptohustlin",
"permlink": "steemit-advertising-campaign-part-22",
"voter": "robmay",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-08-16T12:16:57",
"trx_id": "6b2ae5af40b26221ba361af9c8546c7b8c6250ac",
"trx_in_block": 11,
"virtual_op": 0
}2017/08/15 20:55:18
2017/08/15 20:55:18
| active | {"account_auths":[],"key_auths":[["STM7zXCGg7AYgjjQ8xUCp8w1GQianRR1wpRatf98xDPpcftCMi2Hg",1]],"weight_threshold":1} |
| creator | steem |
| delegation | 57000.000000 VESTS |
| extensions | [] |
| fee | 0.500 STEEM |
| json metadata | |
| memo key | STM5UUenwm1ow1Q2pcK9szVxmFQobXeUu6pnU23ZTwGVz8ujjEF82 |
| new account name | robmay |
| owner | {"account_auths":[],"key_auths":[["STM7zPZYbcbgehyXi26stp4E3oUA79YwZMgYZcTehmQZjsQCCCbzP",1]],"weight_threshold":1} |
| posting | {"account_auths":[],"key_auths":[["STM7b3UCGayg6j6uPbBCfnUFktQ2Ygp3jqznqZp4migkSLidXQ8qa",1]],"weight_threshold":1} |
| Transaction Info | Block #14605849/Trx bf9f512cc028653e1c361238c9aec6f31f993b54 |
View Raw JSON Data
{
"block": 14605849,
"op": [
"account_create_with_delegation",
{
"active": {
"account_auths": [],
"key_auths": [
[
"STM7zXCGg7AYgjjQ8xUCp8w1GQianRR1wpRatf98xDPpcftCMi2Hg",
1
]
],
"weight_threshold": 1
},
"creator": "steem",
"delegation": "57000.000000 VESTS",
"extensions": [],
"fee": "0.500 STEEM",
"json_metadata": "",
"memo_key": "STM5UUenwm1ow1Q2pcK9szVxmFQobXeUu6pnU23ZTwGVz8ujjEF82",
"new_account_name": "robmay",
"owner": {
"account_auths": [],
"key_auths": [
[
"STM7zPZYbcbgehyXi26stp4E3oUA79YwZMgYZcTehmQZjsQCCCbzP",
1
]
],
"weight_threshold": 1
},
"posting": {
"account_auths": [],
"key_auths": [
[
"STM7b3UCGayg6j6uPbBCfnUFktQ2Ygp3jqznqZp4migkSLidXQ8qa",
1
]
],
"weight_threshold": 1
}
}
],
"op_in_trx": 0,
"timestamp": "2017-08-15T20:55:18",
"trx_id": "bf9f512cc028653e1c361238c9aec6f31f993b54",
"trx_in_block": 17,
"virtual_op": 0
}Manabar
Voting Power100.00%
Downvote Power100.00%
Resource Credits100.00%
Reputation Progress0.00%
{
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779083328
},
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779083328
},
"rc_account": {
"account": "robmay",
"max_rc": "10164408779",
"max_rc_creation_adjustment": {
"amount": "2020748973",
"nai": "@@000000037",
"precision": 6
},
"rc_manabar": {
"current_mana": "10164408779",
"last_update_time": 1779083328
}
}
}Account Metadata
| POSTING JSON METADATA | |
| None | |
| JSON METADATA | |
| None |
{
"posting_json_metadata": {},
"json_metadata": {}
}Auth Keys
Owner
Single Signature
Public Keys
STM7zPZYbcbgehyXi26stp4E3oUA79YwZMgYZcTehmQZjsQCCCbzP1/1
Active
Single Signature
Public Keys
STM7zXCGg7AYgjjQ8xUCp8w1GQianRR1wpRatf98xDPpcftCMi2Hg1/1
Posting
Single Signature
Public Keys
STM7b3UCGayg6j6uPbBCfnUFktQ2Ygp3jqznqZp4migkSLidXQ8qa1/1
Memo
STM5UUenwm1ow1Q2pcK9szVxmFQobXeUu6pnU23ZTwGVz8ujjEF82
{
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7zPZYbcbgehyXi26stp4E3oUA79YwZMgYZcTehmQZjsQCCCbzP",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7zXCGg7AYgjjQ8xUCp8w1GQianRR1wpRatf98xDPpcftCMi2Hg",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7b3UCGayg6j6uPbBCfnUFktQ2Ygp3jqznqZp4migkSLidXQ8qa",
1
]
]
},
"memo": "STM5UUenwm1ow1Q2pcK9szVxmFQobXeUu6pnU23ZTwGVz8ujjEF82"
}Witness Votes
0 / 30
No active witness votes.
[]