VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS0.00%
Net Worth
0.036USD
STEEM
0.000STEEM
SBD
0.000SBD
Effective Power
5.007SP
├── Own SP
0.629SP
└── Incoming DelegationsDeleg
+4.378SP
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.629SP | SP |
| Delegated Out | 0.000SP | SP |
| Delegation In | 4.378SP | 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": "1023.143218 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "7120.516588 VESTS",
"sbd_balance": "0.000 SBD",
"savings_sbd_balance": "0.000 SBD",
"reward_sbd_balance": "0.000 SBD",
"conversions": []
}Account Info
| name | romeozor |
| id | 675201 |
| rank | 267,537 |
| reputation | 2139956 |
| created | 2018-01-29T11:49:24 |
| recovery_account | steem |
| proxy | None |
| post_count | 3 |
| comment_count | 0 |
| lifetime_vote_count | 0 |
| witnesses_voted_for | 0 |
| last_post | 2018-03-20T10:14:00 |
| last_root_post | 2018-03-20T10:14:00 |
| last_vote_time | 1970-01-01T00:00:00 |
| 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 | 1023.143218 VESTS |
| delegated_vesting_shares | 0.000000 VESTS |
| received_vesting_shares | 7120.516588 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": 675201,
"name": "romeozor",
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5kx8yi5KbmTwLgDDQU5QvzrF1sMekdhPJ5NuCadeS2QaE9bZ4v",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7V1ajHmbdBvjUwfdUNzeExtK3iDbdKL8bwzqs55xHcaZnvjUTM",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5kfMYMaeLxd8Lxe1m6PF4hGex2XWakWEh5jG5yb3vpjro6kSfM",
1
]
]
},
"memo_key": "STM7ghaauD9sEWg4SMhQQA6t9fcKEgwWFz2i1ZNejCbU5i3bMJr3K",
"json_metadata": "",
"posting_json_metadata": "",
"proxy": "",
"last_owner_update": "1970-01-01T00:00:00",
"last_account_update": "1970-01-01T00:00:00",
"created": "2018-01-29T11:49:24",
"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": 3,
"can_vote": true,
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779083508
},
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779083508
},
"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": "1023.143218 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "7120.516588 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": "2018-03-20T10:14:00",
"last_root_post": "2018-03-20T10:14:00",
"last_vote_time": "1970-01-01T00:00:00",
"post_bandwidth": 0,
"pending_claimed_accounts": 0,
"vesting_balance": "0.000 STEEM",
"reputation": 2139956,
"transfer_history": [],
"market_history": [],
"post_history": [],
"vote_history": [],
"other_history": [],
"witness_votes": [],
"tags_usage": [],
"guest_bloggers": [],
"rank": 267537
}Withdraw Routes
| Incoming | Outgoing |
|---|---|
Empty | Empty |
{
"incoming": [],
"outgoing": []
}From Date
To Date
2026/05/18 05:51:48
2026/05/18 05:51:48
| delegatee | romeozor |
| delegator | steem |
| vesting shares | 7120.516588 VESTS |
| Transaction Info | Block #106150150/Trx 4d53ce74f1c93343cef50a7b563e3f7ec07ac999 |
View Raw JSON Data
{
"block": 106150150,
"op": [
"delegate_vesting_shares",
{
"delegatee": "romeozor",
"delegator": "steem",
"vesting_shares": "7120.516588 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2026-05-18T05:51:48",
"trx_id": "4d53ce74f1c93343cef50a7b563e3f7ec07ac999",
"trx_in_block": 1,
"virtual_op": 0
}2026/05/13 02:37:51
2026/05/13 02:37:51
| delegatee | romeozor |
| delegator | steem |
| vesting shares | 4408.306183 VESTS |
| Transaction Info | Block #106002997/Trx ccd4ec82f074096808d33c60faf183b32af7640d |
View Raw JSON Data
{
"block": 106002997,
"op": [
"delegate_vesting_shares",
{
"delegatee": "romeozor",
"delegator": "steem",
"vesting_shares": "4408.306183 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2026-05-13T02:37:51",
"trx_id": "ccd4ec82f074096808d33c60faf183b32af7640d",
"trx_in_block": 1,
"virtual_op": 0
}2026/04/26 05:04:09
2026/04/26 05:04:09
| delegatee | romeozor |
| delegator | steem |
| vesting shares | 7133.032344 VESTS |
| Transaction Info | Block #105517646/Trx 2b76720b3cb934083f46e3169441460adc317331 |
View Raw JSON Data
{
"block": 105517646,
"op": [
"delegate_vesting_shares",
{
"delegatee": "romeozor",
"delegator": "steem",
"vesting_shares": "7133.032344 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2026-04-26T05:04:09",
"trx_id": "2b76720b3cb934083f46e3169441460adc317331",
"trx_in_block": 0,
"virtual_op": 0
}2026/01/23 22:53:15
2026/01/23 22:53:15
| delegatee | romeozor |
| delegator | steem |
| vesting shares | 4449.853002 VESTS |
| Transaction Info | Block #102869883/Trx ec019de45d51ce5fe5b6e647f4ee4491308b270a |
View Raw JSON Data
{
"block": 102869883,
"op": [
"delegate_vesting_shares",
{
"delegatee": "romeozor",
"delegator": "steem",
"vesting_shares": "4449.853002 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2026-01-23T22:53:15",
"trx_id": "ec019de45d51ce5fe5b6e647f4ee4491308b270a",
"trx_in_block": 1,
"virtual_op": 0
}2024/12/17 18:03:45
2024/12/17 18:03:45
| delegatee | romeozor |
| delegator | steem |
| vesting shares | 4614.072199 VESTS |
| Transaction Info | Block #91316106/Trx 9daa2a2715e1e425910c70d82a129b0c8ae8d822 |
View Raw JSON Data
{
"block": 91316106,
"op": [
"delegate_vesting_shares",
{
"delegatee": "romeozor",
"delegator": "steem",
"vesting_shares": "4614.072199 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2024-12-17T18:03:45",
"trx_id": "9daa2a2715e1e425910c70d82a129b0c8ae8d822",
"trx_in_block": 2,
"virtual_op": 0
}2023/11/14 09:45:00
2023/11/14 09:45:00
| delegatee | romeozor |
| delegator | steem |
| vesting shares | 4783.205731 VESTS |
| Transaction Info | Block #79870258/Trx f615b5ca6c255e662cf69a9cd8c63379c8de7d8f |
View Raw JSON Data
{
"block": 79870258,
"op": [
"delegate_vesting_shares",
{
"delegatee": "romeozor",
"delegator": "steem",
"vesting_shares": "4783.205731 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2023-11-14T09:45:00",
"trx_id": "f615b5ca6c255e662cf69a9cd8c63379c8de7d8f",
"trx_in_block": 0,
"virtual_op": 0
}2023/09/22 09:53:21
2023/09/22 09:53:21
| delegatee | romeozor |
| delegator | steem |
| vesting shares | 7720.114517 VESTS |
| Transaction Info | Block #78362263/Trx 3428dcf2e081e726b0ff58c35cfbbd5aac58de4e |
View Raw JSON Data
{
"block": 78362263,
"op": [
"delegate_vesting_shares",
{
"delegatee": "romeozor",
"delegator": "steem",
"vesting_shares": "7720.114517 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2023-09-22T09:53:21",
"trx_id": "3428dcf2e081e726b0ff58c35cfbbd5aac58de4e",
"trx_in_block": 1,
"virtual_op": 0
}2022/11/03 17:24:54
2022/11/03 17:24:54
| delegatee | romeozor |
| delegator | steem |
| vesting shares | 7942.165955 VESTS |
| Transaction Info | Block #69120083/Trx e4865b1b2ab0778fd21c5b3c778c426b2b9929f7 |
View Raw JSON Data
{
"block": 69120083,
"op": [
"delegate_vesting_shares",
{
"delegatee": "romeozor",
"delegator": "steem",
"vesting_shares": "7942.165955 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2022-11-03T17:24:54",
"trx_id": "e4865b1b2ab0778fd21c5b3c778c426b2b9929f7",
"trx_in_block": 2,
"virtual_op": 0
}2022/01/17 22:39:21
2022/01/17 22:39:21
| delegatee | romeozor |
| delegator | steem |
| vesting shares | 8162.273556 VESTS |
| Transaction Info | Block #60823382/Trx 19be26a4f4c54fbc3560d37e7f9c45e9191ba6ad |
View Raw JSON Data
{
"block": 60823382,
"op": [
"delegate_vesting_shares",
{
"delegatee": "romeozor",
"delegator": "steem",
"vesting_shares": "8162.273556 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2022-01-17T22:39:21",
"trx_id": "19be26a4f4c54fbc3560d37e7f9c45e9191ba6ad",
"trx_in_block": 32,
"virtual_op": 0
}2021/06/14 05:51:24
2021/06/14 05:51:24
| delegatee | romeozor |
| delegator | steem |
| vesting shares | 8346.467844 VESTS |
| Transaction Info | Block #54613731/Trx a7d32eb55837efba684ee599639d42c0469d634b |
View Raw JSON Data
{
"block": 54613731,
"op": [
"delegate_vesting_shares",
{
"delegatee": "romeozor",
"delegator": "steem",
"vesting_shares": "8346.467844 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2021-06-14T05:51:24",
"trx_id": "a7d32eb55837efba684ee599639d42c0469d634b",
"trx_in_block": 2,
"virtual_op": 0
}2020/12/11 16:04:12
2020/12/11 16:04:12
| delegatee | romeozor |
| delegator | steem |
| vesting shares | 8533.889818 VESTS |
| Transaction Info | Block #49361009/Trx 103b1eaaa43759e166796dde8b2692ad24834815 |
View Raw JSON Data
{
"block": 49361009,
"op": [
"delegate_vesting_shares",
{
"delegatee": "romeozor",
"delegator": "steem",
"vesting_shares": "8533.889818 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-12-11T16:04:12",
"trx_id": "103b1eaaa43759e166796dde8b2692ad24834815",
"trx_in_block": 3,
"virtual_op": 0
}2020/12/06 09:39:57
2020/12/06 09:39:57
| delegatee | romeozor |
| delegator | steem |
| vesting shares | 1912.543513 VESTS |
| Transaction Info | Block #49212534/Trx 1ed65f2fcd2b4b173f8f494913e2d95d1a71ed16 |
View Raw JSON Data
{
"block": 49212534,
"op": [
"delegate_vesting_shares",
{
"delegatee": "romeozor",
"delegator": "steem",
"vesting_shares": "1912.543513 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-12-06T09:39:57",
"trx_id": "1ed65f2fcd2b4b173f8f494913e2d95d1a71ed16",
"trx_in_block": 3,
"virtual_op": 0
}2020/12/05 19:41:57
2020/12/05 19:41:57
| delegatee | romeozor |
| delegator | steem |
| vesting shares | 8540.097672 VESTS |
| Transaction Info | Block #49196091/Trx ea3286867020c2baf94e5b32162bf1e8b8f07fa8 |
View Raw JSON Data
{
"block": 49196091,
"op": [
"delegate_vesting_shares",
{
"delegatee": "romeozor",
"delegator": "steem",
"vesting_shares": "8540.097672 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-12-05T19:41:57",
"trx_id": "ea3286867020c2baf94e5b32162bf1e8b8f07fa8",
"trx_in_block": 6,
"virtual_op": 0
}2020/11/03 01:56:30
2020/11/03 01:56:30
| delegatee | romeozor |
| delegator | steem |
| vesting shares | 1920.017158 VESTS |
| Transaction Info | Block #48269932/Trx 75b48a61d47c0ffd7a6b8492a9bc777fab8c2fd5 |
View Raw JSON Data
{
"block": 48269932,
"op": [
"delegate_vesting_shares",
{
"delegatee": "romeozor",
"delegator": "steem",
"vesting_shares": "1920.017158 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-11-03T01:56:30",
"trx_id": "75b48a61d47c0ffd7a6b8492a9bc777fab8c2fd5",
"trx_in_block": 0,
"virtual_op": 0
}2020/05/09 10:42:36
2020/05/09 10:42:36
| delegatee | romeozor |
| delegator | steem |
| vesting shares | 8742.903031 VESTS |
| Transaction Info | Block #43222856/Trx 0e0e85f9f88356af97b7769075feb9d38b5e8afa |
View Raw JSON Data
{
"block": 43222856,
"op": [
"delegate_vesting_shares",
{
"delegatee": "romeozor",
"delegator": "steem",
"vesting_shares": "8742.903031 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-05-09T10:42:36",
"trx_id": "0e0e85f9f88356af97b7769075feb9d38b5e8afa",
"trx_in_block": 6,
"virtual_op": 0
}2020/05/08 15:03:33
2020/05/08 15:03:33
| delegatee | romeozor |
| delegator | steem |
| vesting shares | 1953.311140 VESTS |
| Transaction Info | Block #43199835/Trx 26fc909d292bae83ddde51d2485ba09043a61254 |
View Raw JSON Data
{
"block": 43199835,
"op": [
"delegate_vesting_shares",
{
"delegatee": "romeozor",
"delegator": "steem",
"vesting_shares": "1953.311140 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-05-08T15:03:33",
"trx_id": "26fc909d292bae83ddde51d2485ba09043a61254",
"trx_in_block": 0,
"virtual_op": 0
}2020/01/29 13:24:00
2020/01/29 13:24:00
| author | steemitboard |
| body | Congratulations @romeozor! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@romeozor/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/@romeozor) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=romeozor)_</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 | romeozor |
| parent permlink | quantstamp-as-a-metric-of-ico-quality |
| permlink | steemitboard-notify-romeozor-20200129t132359000z |
| title | |
| Transaction Info | Block #40353208/Trx cee953f189311083b0dc47c843ecb820af7f28f0 |
View Raw JSON Data
{
"block": 40353208,
"op": [
"comment",
{
"author": "steemitboard",
"body": "Congratulations @romeozor! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@romeozor/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/@romeozor) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=romeozor)_</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": "romeozor",
"parent_permlink": "quantstamp-as-a-metric-of-ico-quality",
"permlink": "steemitboard-notify-romeozor-20200129t132359000z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2020-01-29T13:24:00",
"trx_id": "cee953f189311083b0dc47c843ecb820af7f28f0",
"trx_in_block": 4,
"virtual_op": 0
}2019/06/11 18:12:09
2019/06/11 18:12:09
| delegatee | romeozor |
| delegator | steem |
| vesting shares | 8933.958041 VESTS |
| Transaction Info | Block #33712621/Trx 42863890c759bb43380bc82c22fde817faee5557 |
View Raw JSON Data
{
"block": 33712621,
"op": [
"delegate_vesting_shares",
{
"delegatee": "romeozor",
"delegator": "steem",
"vesting_shares": "8933.958041 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2019-06-11T18:12:09",
"trx_id": "42863890c759bb43380bc82c22fde817faee5557",
"trx_in_block": 26,
"virtual_op": 0
}2019/01/29 13:21:36
2019/01/29 13:21:36
| author | steemitboard |
| body | Congratulations @romeozor! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@romeozor/birthday1.png</td><td>Happy Birthday! - You are on the Steem blockchain for 1 year!</td></tr></table> <sub>_[Click here to view your Board](https://steemitboard.com/@romeozor)_</sub> > Support [SteemitBoard's project](https://steemit.com/@steemitboard)! **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| parent author | romeozor |
| parent permlink | quantstamp-as-a-metric-of-ico-quality |
| permlink | steemitboard-notify-romeozor-20190129t132135000z |
| title | |
| Transaction Info | Block #29880781/Trx 5b0e6de33e5a06005e59aa08a1f8323ad47a33a7 |
View Raw JSON Data
{
"block": 29880781,
"op": [
"comment",
{
"author": "steemitboard",
"body": "Congratulations @romeozor! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@romeozor/birthday1.png</td><td>Happy Birthday! - You are on the Steem blockchain for 1 year!</td></tr></table>\n\n<sub>_[Click here to view your Board](https://steemitboard.com/@romeozor)_</sub>\n\n\n> Support [SteemitBoard's project](https://steemit.com/@steemitboard)! **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}",
"parent_author": "romeozor",
"parent_permlink": "quantstamp-as-a-metric-of-ico-quality",
"permlink": "steemitboard-notify-romeozor-20190129t132135000z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2019-01-29T13:21:36",
"trx_id": "5b0e6de33e5a06005e59aa08a1f8323ad47a33a7",
"trx_in_block": 6,
"virtual_op": 0
}2018/06/19 16:06:15
2018/06/19 16:06:15
| delegatee | romeozor |
| delegator | steem |
| vesting shares | 9133.103185 VESTS |
| Transaction Info | Block #23462865/Trx 98597631c760553ab260171cf2cc1db0bf1066f3 |
View Raw JSON Data
{
"block": 23462865,
"op": [
"delegate_vesting_shares",
{
"delegatee": "romeozor",
"delegator": "steem",
"vesting_shares": "9133.103185 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2018-06-19T16:06:15",
"trx_id": "98597631c760553ab260171cf2cc1db0bf1066f3",
"trx_in_block": 52,
"virtual_op": 0
}2018/05/18 20:44:39
2018/05/18 20:44:39
| delegatee | romeozor |
| delegator | steem |
| vesting shares | 29496.376707 VESTS |
| Transaction Info | Block #22547984/Trx 702612ebd36a32ff8ab53d0dd6dac773f902efc6 |
View Raw JSON Data
{
"block": 22547984,
"op": [
"delegate_vesting_shares",
{
"delegatee": "romeozor",
"delegator": "steem",
"vesting_shares": "29496.376707 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2018-05-18T20:44:39",
"trx_id": "702612ebd36a32ff8ab53d0dd6dac773f902efc6",
"trx_in_block": 36,
"virtual_op": 0
}romeozorpublished a new post: quantstamp-as-a-metric-of-ico-quality2018/03/20 15:30:36
romeozorpublished a new post: quantstamp-as-a-metric-of-ico-quality
2018/03/20 15:30:36
| author | romeozor |
| body |  Crypto **I**nitial **C**oin **O**fferings (ICO's) are popping up like mushrooms, fighting for the rankings to increase potential investor trust. Some are well-established, some don't have experience nor guidance to solidify their vision as something worthwhile investing in. People devised different aspects to rate ICO's such as: maturity of team, viability of project, token metadata, existence of [Minimum Viable Product](https://en.wikipedia.org/wiki/Minimum_viable_product), even the project name, etc. **Quantstamp could be incorporated as a new means to increase the perceived value of an ICO.** A lot of ICO's request funds to be deposited with the help of smart contracts with different policies (min/max amount, returns and refunds). Since Quantstamp's goal is to audit smart contracts, it's easy to see how a project that does this simple gesture could benefit from an increase of trustworthiness. Quantstamp could be used as a "seal of approval" that the smart contract is indeed free of issues, increasing user confidence that the project cares about the quality of the ICO. Check out [Quantstamp](https://quantstamp.com/) and their [audits](https://app.quantstamp.com/public-reports). |
| json metadata | {"tags":["quantstamp","quantsamp","ico","cryptocurrency"],"app":"steemit/0.1","format":"markdown","links":["https://en.wikipedia.org/wiki/Minimum_viable_product","https://quantstamp.com/","https://app.quantstamp.com/public-reports"],"image":["https://steemitimages.com/DQmcQWDjwhG9SWQfYu3YVPUgxjp8aGvY8kB7gEPJMSDC3CA/quantstamp_header.png"]} |
| parent author | |
| parent permlink | quantsamp |
| permlink | quantstamp-as-a-metric-of-ico-quality |
| title | Quantstamp as a metric of ICO quality |
| Transaction Info | Block #20844261/Trx e5652bd94a60442b708e85cc7112903dd0bbbe35 |
View Raw JSON Data
{
"block": 20844261,
"op": [
"comment",
{
"author": "romeozor",
"body": "\n\nCrypto **I**nitial **C**oin **O**fferings (ICO's) are popping up like mushrooms, fighting for the rankings to increase potential investor trust. Some are well-established, some don't have experience nor guidance to solidify their vision as something worthwhile investing in.\n\nPeople devised different aspects to rate ICO's such as: maturity of team, viability of project, token metadata, existence of [Minimum Viable Product](https://en.wikipedia.org/wiki/Minimum_viable_product), even the project name, etc. **Quantstamp could be incorporated as a new means to increase the perceived value of an ICO.**\n\nA lot of ICO's request funds to be deposited with the help of smart contracts with different policies (min/max amount, returns and refunds). Since Quantstamp's goal is to audit smart contracts, it's easy to see how a project that does this simple gesture could benefit from an increase of trustworthiness.\n\nQuantstamp could be used as a \"seal of approval\" that the smart contract is indeed free of issues, increasing user confidence that the project cares about the quality of the ICO.\n\nCheck out [Quantstamp](https://quantstamp.com/) and their [audits](https://app.quantstamp.com/public-reports).",
"json_metadata": "{\"tags\":[\"quantstamp\",\"quantsamp\",\"ico\",\"cryptocurrency\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\",\"links\":[\"https://en.wikipedia.org/wiki/Minimum_viable_product\",\"https://quantstamp.com/\",\"https://app.quantstamp.com/public-reports\"],\"image\":[\"https://steemitimages.com/DQmcQWDjwhG9SWQfYu3YVPUgxjp8aGvY8kB7gEPJMSDC3CA/quantstamp_header.png\"]}",
"parent_author": "",
"parent_permlink": "quantsamp",
"permlink": "quantstamp-as-a-metric-of-ico-quality",
"title": "Quantstamp as a metric of ICO quality"
}
],
"op_in_trx": 0,
"timestamp": "2018-03-20T15:30:36",
"trx_id": "e5652bd94a60442b708e85cc7112903dd0bbbe35",
"trx_in_block": 17,
"virtual_op": 0
}romeozorpublished a new post: quantstamp-as-a-metric-of-ico-quality2018/03/20 15:30:21
romeozorpublished a new post: quantstamp-as-a-metric-of-ico-quality
2018/03/20 15:30:21
| author | romeozor |
| body |  Crypto **I**nitial **C**oin **O**fferings (ICO's) are popping up like mushrooms, fighting for the rankings to increase potential investor trust. Some are well-established, some don't have experience nor guidance to solidify their vision as something worthwhile investing in. People devised different aspects to rate ICO's such as: maturity of team, viability of project, token metadata, existence of [Minimum Viable Product](https://en.wikipedia.org/wiki/Minimum_viable_product), even the project name, etc. **Quantstamp could be incorporated as a new means to increase the perceived value of an ICO.** A lot of ICO's request funds to be deposited with the help of smart contracts with different policies (min/max amount, returns and refunds). Since Quantstamp's goal is to audit smart contracts, it's easy to see how a project that does this simple gesture could benefit from an increase of trustworthiness. Quantstamp could be used as a "seal of approval" that the smart contract is indeed free of issues, increasing user confidence that the project cares about the quality of the ICO. Check out [Quantstamp](https://quantstamp.com/) and their [audits](https://app.quantstamp.com/public-reports). |
| json metadata | {"tags":["quantstamp","ico","cryptocurrency","quantsamp"],"app":"steemit/0.1","format":"markdown","links":["https://en.wikipedia.org/wiki/Minimum_viable_product","https://quantstamp.com/","https://app.quantstamp.com/public-reports"],"image":["https://steemitimages.com/DQmcQWDjwhG9SWQfYu3YVPUgxjp8aGvY8kB7gEPJMSDC3CA/quantstamp_header.png"]} |
| parent author | |
| parent permlink | quantsamp |
| permlink | quantstamp-as-a-metric-of-ico-quality |
| title | Quantstamp as a metric of ICO quality |
| Transaction Info | Block #20844256/Trx f33e9ea16b33af9e7aaf3af0b571f4c7a71366e9 |
View Raw JSON Data
{
"block": 20844256,
"op": [
"comment",
{
"author": "romeozor",
"body": "\n\nCrypto **I**nitial **C**oin **O**fferings (ICO's) are popping up like mushrooms, fighting for the rankings to increase potential investor trust. Some are well-established, some don't have experience nor guidance to solidify their vision as something worthwhile investing in.\n\nPeople devised different aspects to rate ICO's such as: maturity of team, viability of project, token metadata, existence of [Minimum Viable Product](https://en.wikipedia.org/wiki/Minimum_viable_product), even the project name, etc. **Quantstamp could be incorporated as a new means to increase the perceived value of an ICO.**\n\nA lot of ICO's request funds to be deposited with the help of smart contracts with different policies (min/max amount, returns and refunds). Since Quantstamp's goal is to audit smart contracts, it's easy to see how a project that does this simple gesture could benefit from an increase of trustworthiness.\n\nQuantstamp could be used as a \"seal of approval\" that the smart contract is indeed free of issues, increasing user confidence that the project cares about the quality of the ICO.\n\nCheck out [Quantstamp](https://quantstamp.com/) and their [audits](https://app.quantstamp.com/public-reports).",
"json_metadata": "{\"tags\":[\"quantstamp\",\"ico\",\"cryptocurrency\",\"quantsamp\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\",\"links\":[\"https://en.wikipedia.org/wiki/Minimum_viable_product\",\"https://quantstamp.com/\",\"https://app.quantstamp.com/public-reports\"],\"image\":[\"https://steemitimages.com/DQmcQWDjwhG9SWQfYu3YVPUgxjp8aGvY8kB7gEPJMSDC3CA/quantstamp_header.png\"]}",
"parent_author": "",
"parent_permlink": "quantsamp",
"permlink": "quantstamp-as-a-metric-of-ico-quality",
"title": "Quantstamp as a metric of ICO quality"
}
],
"op_in_trx": 0,
"timestamp": "2018-03-20T15:30:21",
"trx_id": "f33e9ea16b33af9e7aaf3af0b571f4c7a71366e9",
"trx_in_block": 4,
"virtual_op": 0
}romeozorpublished a new post: quantstamp-as-a-metric-of-ico-quality2018/03/20 15:29:51
romeozorpublished a new post: quantstamp-as-a-metric-of-ico-quality
2018/03/20 15:29:51
| author | romeozor |
| body |  Crypto **I**nitial **C**oin **O**fferings (ICO's) are popping up like mushrooms, fighting for the rankings to increase potential investor trust. Some are well-established, some don't have experience nor guidance to solidify their vision as something worthwhile investing in. People devised different aspects to rate ICO's such as: maturity of team, viability of project, token metadata, existence of [Minimum Viable Product](https://en.wikipedia.org/wiki/Minimum_viable_product), even the project name, etc. **Quantstamp could be incorporated as a new means to increase the perceived value of an ICO.** A lot of ICO's request funds to be deposited with the help of smart contracts with different policies (min/max amount, returns and refunds). Since Quantstamp's goal is to audit smart contracts, it's easy to see how a project that does this simple gesture could benefit from an increase of trustworthiness. Quantstamp could be used as a "seal of approval" that the smart contract is indeed free of issues, increasing user confidence that the project cares about the quality of the ICO. Check out [Quantstamp](https://quantstamp.com/) and their [audits](https://app.quantstamp.com/public-reports). |
| json metadata | {"tags":["quantstamp","ico","cryptocurrency","quantsamp"],"app":"steemit/0.1","format":"markdown","links":["https://en.wikipedia.org/wiki/Minimum_viable_product","https://quantstamp.com/","https://app.quantstamp.com/public-reports"],"image":["https://steemitimages.com/DQmcQWDjwhG9SWQfYu3YVPUgxjp8aGvY8kB7gEPJMSDC3CA/quantstamp_header.png"]} |
| parent author | |
| parent permlink | quantsamp |
| permlink | quantstamp-as-a-metric-of-ico-quality |
| title | Quantstamp as a metric of ICO quality |
| Transaction Info | Block #20844246/Trx e61a2c5555a3a72368662defa0feb7906da6af3c |
View Raw JSON Data
{
"block": 20844246,
"op": [
"comment",
{
"author": "romeozor",
"body": "\n\nCrypto **I**nitial **C**oin **O**fferings (ICO's) are popping up like mushrooms, fighting for the rankings to increase potential investor trust. Some are well-established, some don't have experience nor guidance to solidify their vision as something worthwhile investing in.\n\nPeople devised different aspects to rate ICO's such as: maturity of team, viability of project, token metadata, existence of [Minimum Viable Product](https://en.wikipedia.org/wiki/Minimum_viable_product), even the project name, etc. **Quantstamp could be incorporated as a new means to increase the perceived value of an ICO.**\n\nA lot of ICO's request funds to be deposited with the help of smart contracts with different policies (min/max amount, returns and refunds). Since Quantstamp's goal is to audit smart contracts, it's easy to see how a project that does this simple gesture could benefit from an increase of trustworthiness.\n\nQuantstamp could be used as a \"seal of approval\" that the smart contract is indeed free of issues, increasing user confidence that the project cares about the quality of the ICO.\n\nCheck out [Quantstamp](https://quantstamp.com/) and their [audits](https://app.quantstamp.com/public-reports).",
"json_metadata": "{\"tags\":[\"quantstamp\",\"ico\",\"cryptocurrency\",\"quantsamp\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\",\"links\":[\"https://en.wikipedia.org/wiki/Minimum_viable_product\",\"https://quantstamp.com/\",\"https://app.quantstamp.com/public-reports\"],\"image\":[\"https://steemitimages.com/DQmcQWDjwhG9SWQfYu3YVPUgxjp8aGvY8kB7gEPJMSDC3CA/quantstamp_header.png\"]}",
"parent_author": "",
"parent_permlink": "quantsamp",
"permlink": "quantstamp-as-a-metric-of-ico-quality",
"title": "Quantstamp as a metric of ICO quality"
}
],
"op_in_trx": 0,
"timestamp": "2018-03-20T15:29:51",
"trx_id": "e61a2c5555a3a72368662defa0feb7906da6af3c",
"trx_in_block": 42,
"virtual_op": 0
}romeozorpublished a new post: quantstamp-as-a-metric-of-ico-quality2018/03/20 12:42:06
romeozorpublished a new post: quantstamp-as-a-metric-of-ico-quality
2018/03/20 12:42:06
| author | romeozor |
| body | @@ -1202,12 +1202,124 @@ of the ICO. +%0A%0ACheck out %5BQuantstamp%5D(https://quantstamp.com/) and their %5Baudits%5D(https://app.quantstamp.com/public-reports). |
| json metadata | {"tags":["quantsamp","ico","cryptocurrency"],"app":"steemit/0.1","format":"markdown","links":["https://en.wikipedia.org/wiki/Minimum_viable_product","https://quantstamp.com/","https://app.quantstamp.com/public-reports"],"image":["https://steemitimages.com/DQmcQWDjwhG9SWQfYu3YVPUgxjp8aGvY8kB7gEPJMSDC3CA/quantstamp_header.png"]} |
| parent author | |
| parent permlink | quantsamp |
| permlink | quantstamp-as-a-metric-of-ico-quality |
| title | Quantstamp as a metric of ICO quality |
| Transaction Info | Block #20840904/Trx 80ddecb147d59ea99fd9d41f20d8e59950ffc7bf |
View Raw JSON Data
{
"block": 20840904,
"op": [
"comment",
{
"author": "romeozor",
"body": "@@ -1202,12 +1202,124 @@\n of the ICO.\n+%0A%0ACheck out %5BQuantstamp%5D(https://quantstamp.com/) and their %5Baudits%5D(https://app.quantstamp.com/public-reports).\n",
"json_metadata": "{\"tags\":[\"quantsamp\",\"ico\",\"cryptocurrency\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\",\"links\":[\"https://en.wikipedia.org/wiki/Minimum_viable_product\",\"https://quantstamp.com/\",\"https://app.quantstamp.com/public-reports\"],\"image\":[\"https://steemitimages.com/DQmcQWDjwhG9SWQfYu3YVPUgxjp8aGvY8kB7gEPJMSDC3CA/quantstamp_header.png\"]}",
"parent_author": "",
"parent_permlink": "quantsamp",
"permlink": "quantstamp-as-a-metric-of-ico-quality",
"title": "Quantstamp as a metric of ICO quality"
}
],
"op_in_trx": 0,
"timestamp": "2018-03-20T12:42:06",
"trx_id": "80ddecb147d59ea99fd9d41f20d8e59950ffc7bf",
"trx_in_block": 22,
"virtual_op": 0
}romeozorpublished a new post: quantstamp-as-a-metric-of-ico-quality2018/03/20 12:39:18
romeozorpublished a new post: quantstamp-as-a-metric-of-ico-quality
2018/03/20 12:39:18
| author | romeozor |
| body | @@ -1,8 +1,131 @@ +!%5Bquantstamp_header.png%5D(https://steemitimages.com/DQmcQWDjwhG9SWQfYu3YVPUgxjp8aGvY8kB7gEPJMSDC3CA/quantstamp_header.png)%0A%0A Crypto * |
| json metadata | {"tags":["quantsamp","ico","cryptocurrency"],"app":"steemit/0.1","format":"markdown","links":["https://en.wikipedia.org/wiki/Minimum_viable_product"],"image":["https://steemitimages.com/DQmcQWDjwhG9SWQfYu3YVPUgxjp8aGvY8kB7gEPJMSDC3CA/quantstamp_header.png"]} |
| parent author | |
| parent permlink | quantsamp |
| permlink | quantstamp-as-a-metric-of-ico-quality |
| title | Quantstamp as a metric of ICO quality |
| Transaction Info | Block #20840849/Trx 036faea7b3232bbe4593e03d69770d1ef9d71788 |
View Raw JSON Data
{
"block": 20840849,
"op": [
"comment",
{
"author": "romeozor",
"body": "@@ -1,8 +1,131 @@\n+!%5Bquantstamp_header.png%5D(https://steemitimages.com/DQmcQWDjwhG9SWQfYu3YVPUgxjp8aGvY8kB7gEPJMSDC3CA/quantstamp_header.png)%0A%0A\n Crypto *\n",
"json_metadata": "{\"tags\":[\"quantsamp\",\"ico\",\"cryptocurrency\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\",\"links\":[\"https://en.wikipedia.org/wiki/Minimum_viable_product\"],\"image\":[\"https://steemitimages.com/DQmcQWDjwhG9SWQfYu3YVPUgxjp8aGvY8kB7gEPJMSDC3CA/quantstamp_header.png\"]}",
"parent_author": "",
"parent_permlink": "quantsamp",
"permlink": "quantstamp-as-a-metric-of-ico-quality",
"title": "Quantstamp as a metric of ICO quality"
}
],
"op_in_trx": 0,
"timestamp": "2018-03-20T12:39:18",
"trx_id": "036faea7b3232bbe4593e03d69770d1ef9d71788",
"trx_in_block": 51,
"virtual_op": 0
}romeozorpublished a new post: quantstamp-as-a-metric-of-ico-quality2018/03/20 12:33:36
romeozorpublished a new post: quantstamp-as-a-metric-of-ico-quality
2018/03/20 12:33:36
| author | romeozor |
| body | @@ -1,20 +1,57 @@ Crypto +**I**nitial **C**oin **O**fferings ( ICO's +) are pop @@ -112,16 +112,26 @@ ncrease +potential investor @@ -495,17 +495,117 @@ ect name -. +, etc. **Quantstamp could be incorporated as a new means to increase the perceived value of an ICO.** %0A%0AA lot @@ -738,16 +738,181 @@ efunds). + Since Quantstamp's goal is to audit smart contracts, it's easy to see how a project that does this simple gesture could benefit from an increase of trustworthiness. %0A%0AQuants |
| json metadata | {"tags":["quantsamp","ico","cryptocurrency"],"app":"steemit/0.1","format":"markdown","links":["https://en.wikipedia.org/wiki/Minimum_viable_product"]} |
| parent author | |
| parent permlink | quantsamp |
| permlink | quantstamp-as-a-metric-of-ico-quality |
| title | Quantstamp as a metric of ICO quality |
| Transaction Info | Block #20840735/Trx edb528682fc05a4e04455cf87635981e6ef6e59c |
View Raw JSON Data
{
"block": 20840735,
"op": [
"comment",
{
"author": "romeozor",
"body": "@@ -1,20 +1,57 @@\n Crypto \n+**I**nitial **C**oin **O**fferings (\n ICO's\n+)\n are pop\n@@ -112,16 +112,26 @@\n ncrease \n+potential \n investor\n@@ -495,17 +495,117 @@\n ect name\n-.\n+, etc. **Quantstamp could be incorporated as a new means to increase the perceived value of an ICO.**\n %0A%0AA lot \n@@ -738,16 +738,181 @@\n efunds).\n+ Since Quantstamp's goal is to audit smart contracts, it's easy to see how a project that does this simple gesture could benefit from an increase of trustworthiness.\n %0A%0AQuants\n",
"json_metadata": "{\"tags\":[\"quantsamp\",\"ico\",\"cryptocurrency\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\",\"links\":[\"https://en.wikipedia.org/wiki/Minimum_viable_product\"]}",
"parent_author": "",
"parent_permlink": "quantsamp",
"permlink": "quantstamp-as-a-metric-of-ico-quality",
"title": "Quantstamp as a metric of ICO quality"
}
],
"op_in_trx": 0,
"timestamp": "2018-03-20T12:33:36",
"trx_id": "edb528682fc05a4e04455cf87635981e6ef6e59c",
"trx_in_block": 44,
"virtual_op": 0
}romeozorpublished a new post: quantstamp-as-a-metric-of-ico-quality2018/03/20 11:06:57
romeozorpublished a new post: quantstamp-as-a-metric-of-ico-quality
2018/03/20 11:06:57
| author | romeozor |
| body | @@ -351,11 +351,86 @@ of -MVP +%5BMinimum Viable Product%5D(https://en.wikipedia.org/wiki/Minimum_viable_product) , ev |
| json metadata | {"tags":["quantsamp","ico","cryptocurrency"],"app":"steemit/0.1","format":"markdown","links":["https://en.wikipedia.org/wiki/Minimum_viable_product"]} |
| parent author | |
| parent permlink | quantsamp |
| permlink | quantstamp-as-a-metric-of-ico-quality |
| title | Quantstamp as a metric of ICO quality |
| Transaction Info | Block #20839004/Trx 9752f64bb8b05b92fd7158fc4de4aa73e2173aa7 |
View Raw JSON Data
{
"block": 20839004,
"op": [
"comment",
{
"author": "romeozor",
"body": "@@ -351,11 +351,86 @@\n of \n-MVP\n+%5BMinimum Viable Product%5D(https://en.wikipedia.org/wiki/Minimum_viable_product)\n , ev\n",
"json_metadata": "{\"tags\":[\"quantsamp\",\"ico\",\"cryptocurrency\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\",\"links\":[\"https://en.wikipedia.org/wiki/Minimum_viable_product\"]}",
"parent_author": "",
"parent_permlink": "quantsamp",
"permlink": "quantstamp-as-a-metric-of-ico-quality",
"title": "Quantstamp as a metric of ICO quality"
}
],
"op_in_trx": 0,
"timestamp": "2018-03-20T11:06:57",
"trx_id": "9752f64bb8b05b92fd7158fc4de4aa73e2173aa7",
"trx_in_block": 10,
"virtual_op": 0
}romeozorpublished a new post: quantstamp-as-a-metric-of-ico-quality2018/03/20 10:14:00
romeozorpublished a new post: quantstamp-as-a-metric-of-ico-quality
2018/03/20 10:14:00
| author | romeozor |
| body | Crypto ICO's are popping up like mushrooms, fighting for the rankings to increase investor trust. Some are well-established, some don't have experience nor guidance to solidify their vision as something worthwhile investing in. People devised different aspects to rate ICO's such as: maturity of team, viability of project, token metadata, existence of MVP, even the project name. A lot of ICO's request funds to be deposited with the help of smart contracts with different policies (min/max amount, returns and refunds). Quantstamp could be used as a "seal of approval" that the smart contract is indeed free of issues, increasing user confidence that the project cares about the quality of the ICO. |
| json metadata | {"tags":["quantsamp","ico","cryptocurrency"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | quantsamp |
| permlink | quantstamp-as-a-metric-of-ico-quality |
| title | Quantstamp as a metric of ICO quality |
| Transaction Info | Block #20837945/Trx 6c6eb7a3fa6979d7086664106f530f15048ecb2c |
View Raw JSON Data
{
"block": 20837945,
"op": [
"comment",
{
"author": "romeozor",
"body": "Crypto ICO's are popping up like mushrooms, fighting for the rankings to increase investor trust. Some are well-established, some don't have experience nor guidance to solidify their vision as something worthwhile investing in.\n\nPeople devised different aspects to rate ICO's such as: maturity of team, viability of project, token metadata, existence of MVP, even the project name.\n\nA lot of ICO's request funds to be deposited with the help of smart contracts with different policies (min/max amount, returns and refunds).\n\nQuantstamp could be used as a \"seal of approval\" that the smart contract is indeed free of issues, increasing user confidence that the project cares about the quality of the ICO.",
"json_metadata": "{\"tags\":[\"quantsamp\",\"ico\",\"cryptocurrency\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "quantsamp",
"permlink": "quantstamp-as-a-metric-of-ico-quality",
"title": "Quantstamp as a metric of ICO quality"
}
],
"op_in_trx": 0,
"timestamp": "2018-03-20T10:14:00",
"trx_id": "6c6eb7a3fa6979d7086664106f530f15048ecb2c",
"trx_in_block": 52,
"virtual_op": 0
}romeozormuted @birdchain2018/03/02 08:50:24
romeozormuted @birdchain
2018/03/02 08:50:24
| id | follow |
| json | ["follow",{"follower":"romeozor","following":"birdchain","what":["ignore"]}] |
| required auths | [] |
| required posting auths | ["romeozor"] |
| Transaction Info | Block #20318406/Trx 0ade88334d0486bc2eed7e29e06b5c69131edefd |
View Raw JSON Data
{
"block": 20318406,
"op": [
"custom_json",
{
"id": "follow",
"json": "[\"follow\",{\"follower\":\"romeozor\",\"following\":\"birdchain\",\"what\":[\"ignore\"]}]",
"required_auths": [],
"required_posting_auths": [
"romeozor"
]
}
],
"op_in_trx": 0,
"timestamp": "2018-03-02T08:50:24",
"trx_id": "0ade88334d0486bc2eed7e29e06b5c69131edefd",
"trx_in_block": 38,
"virtual_op": 0
}narkidkaupvoted (100.00%) @romeozor / seele-ico-whitelist-mishaps2018/02/18 06:36:45
narkidkaupvoted (100.00%) @romeozor / seele-ico-whitelist-mishaps
2018/02/18 06:36:45
| author | romeozor |
| permlink | seele-ico-whitelist-mishaps |
| voter | narkidka |
| weight | 10000 (100.00%) |
| Transaction Info | Block #19970400/Trx c09ff3071570bba3ba991a5dc5207193d8ad6dce |
View Raw JSON Data
{
"block": 19970400,
"op": [
"vote",
{
"author": "romeozor",
"permlink": "seele-ico-whitelist-mishaps",
"voter": "narkidka",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-02-18T06:36:45",
"trx_id": "c09ff3071570bba3ba991a5dc5207193d8ad6dce",
"trx_in_block": 55,
"virtual_op": 0
}zapperupvoted (1.00%) @romeozor / seele-ico-whitelist-mishaps2018/02/17 20:39:51
zapperupvoted (1.00%) @romeozor / seele-ico-whitelist-mishaps
2018/02/17 20:39:51
| author | romeozor |
| permlink | seele-ico-whitelist-mishaps |
| voter | zapper |
| weight | 100 (1.00%) |
| Transaction Info | Block #19958462/Trx 09651d1de09dba7733082696cd4b370c3d304810 |
View Raw JSON Data
{
"block": 19958462,
"op": [
"vote",
{
"author": "romeozor",
"permlink": "seele-ico-whitelist-mishaps",
"voter": "zapper",
"weight": 100
}
],
"op_in_trx": 0,
"timestamp": "2018-02-17T20:39:51",
"trx_id": "09651d1de09dba7733082696cd4b370c3d304810",
"trx_in_block": 30,
"virtual_op": 0
}romeozorpublished a new post: seele-ico-whitelist-mishaps2018/02/17 20:38:57
romeozorpublished a new post: seele-ico-whitelist-mishaps
2018/02/17 20:38:57
| author | romeozor |
| body | @@ -189,17 +189,17 @@ tion%0AThe -t +r e were m @@ -1685,12 +1685,1008 @@ eele offers. +%0A%0A### Take a breath%0AYou also need to chill out a bit. Remember that coming up with blockchain 4.0 and running an ICO are two very different things, they require totally different skill sets. ICO popularity has risen exponentially in the past months, everyone wants to get into the next big thing as soon as possible. On top of this, Seele was having a whitelist tied to an exam, to make sure people who only want to dump their share on exchanges are kept to a minimum. There is not much experience out there for this kind of whitelisting. Obviously the people in charge had no experience in measuring the community interest and did not research how many people Google can handle. %0A%0AIf you are shaken by the unfortunate whitelisting, you need to look at it from a technical perspective and not an emotional one. The people who came up with *Neural Consensus*, *VTP* and *VHTTP* were not responsible for it. The two are separate. **The values and ideas proposed in the whitepaper are still there**! |
| json metadata | {"tags":["seele","ico","whitelist"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | seele |
| permlink | seele-ico-whitelist-mishaps |
| title | Seele ICO whitelist mishaps |
| Transaction Info | Block #19958444/Trx 4581ae63759dd7d8416bdf1bcf4edf1c82d9ba7e |
View Raw JSON Data
{
"block": 19958444,
"op": [
"comment",
{
"author": "romeozor",
"body": "@@ -189,17 +189,17 @@\n tion%0AThe\n-t\n+r\n e were m\n@@ -1685,12 +1685,1008 @@\n eele offers.\n+%0A%0A### Take a breath%0AYou also need to chill out a bit. Remember that coming up with blockchain 4.0 and running an ICO are two very different things, they require totally different skill sets. ICO popularity has risen exponentially in the past months, everyone wants to get into the next big thing as soon as possible. On top of this, Seele was having a whitelist tied to an exam, to make sure people who only want to dump their share on exchanges are kept to a minimum. There is not much experience out there for this kind of whitelisting. Obviously the people in charge had no experience in measuring the community interest and did not research how many people Google can handle. %0A%0AIf you are shaken by the unfortunate whitelisting, you need to look at it from a technical perspective and not an emotional one. The people who came up with *Neural Consensus*, *VTP* and *VHTTP* were not responsible for it. The two are separate. **The values and ideas proposed in the whitepaper are still there**!\n",
"json_metadata": "{\"tags\":[\"seele\",\"ico\",\"whitelist\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "seele",
"permlink": "seele-ico-whitelist-mishaps",
"title": "Seele ICO whitelist mishaps"
}
],
"op_in_trx": 0,
"timestamp": "2018-02-17T20:38:57",
"trx_id": "4581ae63759dd7d8416bdf1bcf4edf1c82d9ba7e",
"trx_in_block": 49,
"virtual_op": 0
}2018/02/17 20:05:09
2018/02/17 20:05:09
| author | luckypower |
| body | We can take out a good learn from your blog.It is an educative value. Big thanks !!! |
| json metadata | {"tags":["seele"],"app":"steemit/0.1"} |
| parent author | romeozor |
| parent permlink | seele-ico-whitelist-mishaps |
| permlink | re-romeozor-seele-ico-whitelist-mishaps-20180217t200508549z |
| title | |
| Transaction Info | Block #19957769/Trx ac2f76606dd8dfe57224808e638da3a8350b67c3 |
View Raw JSON Data
{
"block": 19957769,
"op": [
"comment",
{
"author": "luckypower",
"body": "We can take out a good learn from your blog.It is an educative value. Big thanks !!!",
"json_metadata": "{\"tags\":[\"seele\"],\"app\":\"steemit/0.1\"}",
"parent_author": "romeozor",
"parent_permlink": "seele-ico-whitelist-mishaps",
"permlink": "re-romeozor-seele-ico-whitelist-mishaps-20180217t200508549z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2018-02-17T20:05:09",
"trx_id": "ac2f76606dd8dfe57224808e638da3a8350b67c3",
"trx_in_block": 25,
"virtual_op": 0
}luckypowerupvoted (100.00%) @romeozor / seele-ico-whitelist-mishaps2018/02/17 20:04:57
luckypowerupvoted (100.00%) @romeozor / seele-ico-whitelist-mishaps
2018/02/17 20:04:57
| author | romeozor |
| permlink | seele-ico-whitelist-mishaps |
| voter | luckypower |
| weight | 10000 (100.00%) |
| Transaction Info | Block #19957765/Trx 4838b61d5501f0b8ece9a57c71240f087f41877c |
View Raw JSON Data
{
"block": 19957765,
"op": [
"vote",
{
"author": "romeozor",
"permlink": "seele-ico-whitelist-mishaps",
"voter": "luckypower",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-02-17T20:04:57",
"trx_id": "4838b61d5501f0b8ece9a57c71240f087f41877c",
"trx_in_block": 29,
"virtual_op": 0
}romeozorpublished a new post: seele-ico-whitelist-mishaps2018/02/17 20:04:18
romeozorpublished a new post: seele-ico-whitelist-mishaps
2018/02/17 20:04:18
| author | romeozor |
| body | On Feb. 15th, Seele was set to open its ICO and as we all witnessed, it didn’t turn out well. I think it can be summarized as a poor attempt, caused by panic reactions. ### Poor preparation Thete were many signs of the high demand surrounding the project. ICODrops rated its hype as High. Telegram had close to 30k users in the official group. These are low hanging fruit, but not very representative. Google Analytics could’ve been used to measure the number of users interacting with their site more accurately. Although many use ad blockers that also kills GA, but it still gives valuable numbers. ### Poor execution and reaction to user frustration A poor decision was to give the Google docs link out before the actual website countdown finished. The explanation was they wanted to prevent scammers promoting malicious links. Since it was announced on every possible channel to be vigilant, this is a poor excuse. It’s easy to get scammed when a lot of people are in the sate of FOMO, but your integrity is far more valuable in my opinion. After everything started to go downhill, there was no response from the admins for a very long time. “Very long time” is relative, but for an angry mob looking at a generic error screen, every second feels like an eternity. ### Takeaway It is clear that if you want a successful ICO, you need to pay attention to the technical aspects. Weather if it’s keeping your Telegram group check, or opening the floodgates to your whitelist, you need technical expertise. Seele promises a lot of innovation in the Blockchain ecosystem, but if they don’t get their act together, people will move on to project that inevitably copy what Seele offers. |
| json metadata | {"tags":["seele","ico","whitelist"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | seele |
| permlink | seele-ico-whitelist-mishaps |
| title | Seele ICO whitelist mishaps |
| Transaction Info | Block #19957752/Trx c46fe817485db4b5d4e94a4a15548e10efa14a31 |
View Raw JSON Data
{
"block": 19957752,
"op": [
"comment",
{
"author": "romeozor",
"body": "On Feb. 15th, Seele was set to open its ICO and as we all witnessed, it didn’t turn out well. \n\nI think it can be summarized as a poor attempt, caused by panic reactions.\n\n### Poor preparation\nThete were many signs of the high demand surrounding the project. ICODrops rated its hype as High. Telegram had close to 30k users in the official group. These are low hanging fruit, but not very representative. \n\nGoogle Analytics could’ve been used to measure the number of users interacting with their site more accurately. Although many use ad blockers that also kills GA, but it still gives valuable numbers. \n\n\n### Poor execution and reaction to user frustration\nA poor decision was to give the Google docs link out before the actual website countdown finished. The explanation was they wanted to prevent scammers promoting malicious links. Since it was announced on every possible channel to be vigilant, this is a poor excuse. It’s easy to get scammed when a lot of people are in the sate of FOMO, but your integrity is far more valuable in my opinion. \n\nAfter everything started to go downhill, there was no response from the admins for a very long time. “Very long time” is relative, but for an angry mob looking at a generic error screen, every second feels like an eternity. \n\n### Takeaway\nIt is clear that if you want a successful ICO, you need to pay attention to the technical aspects. Weather if it’s keeping your Telegram group check, or opening the floodgates to your whitelist, you need technical expertise.\n\nSeele promises a lot of innovation in the Blockchain ecosystem, but if they don’t get their act together, people will move on to project that inevitably copy what Seele offers.",
"json_metadata": "{\"tags\":[\"seele\",\"ico\",\"whitelist\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "seele",
"permlink": "seele-ico-whitelist-mishaps",
"title": "Seele ICO whitelist mishaps"
}
],
"op_in_trx": 0,
"timestamp": "2018-02-17T20:04:18",
"trx_id": "c46fe817485db4b5d4e94a4a15548e10efa14a31",
"trx_in_block": 8,
"virtual_op": 0
}romeozorpublished a new post: arcblock-the-backend-of-the-blockchain-3-02018/01/29 20:59:27
romeozorpublished a new post: arcblock-the-backend-of-the-blockchain-3-0
2018/01/29 20:59:27
| author | romeozor |
| body | To understand the proposal of ArcBlock, one must understand the cloud. Let's recap. Disclaimer: this has been written for the bounty program. ##### What's the problem with servers? Running a server is hard. A person needs years of training to be able to set up, run, and maintain a server efficiently and securely. The cost of a reliable admin or training one is very high, and then we didn't think of the cost of hardware and software. If you're a small business, you can't afford all this, but you still need a secure server and reliable hosting. Availability? Reach? Backups? Scalability? The list goes on. ##### How does the cloud solve this? Hosting is pretty obvious. They host whatever you need, how you need it, you just pay after the usage. If you want, you can still babysit a full-blown virtual machine in the could, but why would you do that if you only need a couple of specific features? Host a website, a database, speech recognition, or an AI bot service, and never lose sleep over how it all maintained behind the curtains. ###### What problem does Serverless solve? Nothing new, really. It's just a paradoxical buzzword. How can something run on the internet if there's no server? Even the cloud has servers, so what's the deal? Imagine a phone app that requires you to register and also provide proof of identity in the form of a scanned passport, plus a selfie holding the passport. The app directly talks to a database running in Microsoft Azure, while facial recognition runs in Amazon AWS, and the app itself is hosted in one of the app stores. If your app gets popular, the services just scale up. Your things are running in the cloud, but also... You are running serverless! ###### What is a microservice? A microservice is a small unit of code that is designed to solve typically one problem only. These are designed to be light-weight and easily scalable. Microservices can also talk to other microservices. ##### How does ArcBlock leverage all this **If you're thinking of building something based on a blockchain**, you need to make a choice which one. Some are massively popular but slow, others are fast, but too new to have a solid backing. In the software industry, it is incredibly valuable when you don't have to solve a problem, because someone already solved it for you. **ArcBlock wants to give you the opportunity to not have to worry about which one to pick**. ###### It's all about abstractions The way the cloud abstracts the hassle of managing your servers, ArcBlock abstracts the hassle of learning how each blockchain works. The API provided by their microservices called **Blocklets remove the pain of figuring out how to integrate blockchains into your business**. Blocklets sit on the top and manage the underlying infrastructure from the business functions all the way down to the blockchains. ##### Financial opportunities, ABT tokens ArcBlock doesn't do *mining* in the classical sense. Being a decentralized system, it requires servers everywhere to run on. If you happen to have a server somewhere, **you can offer your hardware or cloud instance** to participate in the Blockchain as a Service (BaaS) platform. **Your compensation** for the resources used **will be ABT tokens**. I think there are exciting opportunities both in developing countries, and countries where cloud services couldn't get a foothold yet. Established cloud data center locations are the usual suspects with all the major players: USA, UK, Germany, China. However, there's usually a huge gap right around where Russia is, also Poland or Turkey. If you want to run a blockchain app off the cloud in Istanbul, odds are your data will need to travel all the way to Germany. I can also see festivals picking up this kind of technology. If you look at the festivals and events in the last 2-3 years, you'll see an increase in the use of virtual currency on the festival grounds. You want a beer, or a slice of pizza? You'll need to exchange your money to the local tokens. Secure and fast transactions are crucial. ###### Worth for developers, too The way Blocklets communicate with blockchains is not trivial. There's no universal language that both sides understand. Adapters are required to create a link between the two sides. Chain adapters are required, just like the driver for your video card, which need to be written by developers. ArcBlock plans to compensate devs who write such adapters and make them available for the public. Although there doesn't need to be a 100 different adapters for a given blockchain, this is the aspect that intrigues me the most being a developer myself. Check out ArcBlock on their [site](https://www.arcblock.io/) and read their [whitepaper](https://www.arcblock.io/file/whitepaper/WhitePaperEnV2_en-US.pdf?v=4). My Bitcointalk [profile](https://bitcointalk.org/index.php?action=profile;u=1715458). [Via my blog](https://lurkingcode.com/2018/01/20/arcblock-the-backend-of-the-blockchain-3/) |
| json metadata | {"tags":["arcblock","blockchain","blocklet","serverless","microservice"],"links":["https://www.arcblock.io/","https://www.arcblock.io/file/whitepaper/WhitePaperEnV2_en-US.pdf?v=4","https://bitcointalk.org/index.php?action=profile;u=1715458","https://lurkingcode.com/2018/01/20/arcblock-the-backend-of-the-blockchain-3/"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | arcblock |
| permlink | arcblock-the-backend-of-the-blockchain-3-0 |
| title | ArcBlock, the backend of the Blockchain 3.0 |
| Transaction Info | Block #19412439/Trx 5d80ff64670696223df10aa0c554eb90d54764d1 |
View Raw JSON Data
{
"block": 19412439,
"op": [
"comment",
{
"author": "romeozor",
"body": "To understand the proposal of ArcBlock, one must understand the cloud. Let's recap.\nDisclaimer: this has been written for the bounty program.\n\n##### What's the problem with servers?\nRunning a server is hard. A person needs years of training to be able to set up, run, and maintain a server efficiently and securely. The cost of a reliable admin or training one is very high, and then we didn't think of the cost of hardware and software. If you're a small business, you can't afford all this, but you still need a secure server and reliable hosting. Availability? Reach? Backups? Scalability? The list goes on.\n\n##### How does the cloud solve this?\nHosting is pretty obvious. They host whatever you need, how you need it, you just pay after the usage. If you want, you can still babysit a full-blown virtual machine in the could, but why would you do that if you only need a couple of specific features? Host a website, a database, speech recognition, or an AI bot service, and never lose sleep over how it all maintained behind the curtains.\n\n###### What problem does Serverless solve?\nNothing new, really. It's just a paradoxical buzzword. How can something run on the internet if there's no server? Even the cloud has servers, so what's the deal?\n\nImagine a phone app that requires you to register and also provide proof of identity in the form of a scanned passport, plus a selfie holding the passport. The app directly talks to a database running in Microsoft Azure, while facial recognition runs in Amazon AWS, and the app itself is hosted in one of the app stores. If your app gets popular, the services just scale up. Your things are running in the cloud, but also...\n\nYou are running serverless!\n\n###### What is a microservice?\nA microservice is a small unit of code that is designed to solve typically one problem only. These are designed to be light-weight and easily scalable. Microservices can also talk to other microservices.\n\n##### How does ArcBlock leverage all this\n**If you're thinking of building something based on a blockchain**, you need to make a choice which one. Some are massively popular but slow, others are fast, but too new to have a solid backing. \n\nIn the software industry, it is incredibly valuable when you don't have to solve a problem, because someone already solved it for you. **ArcBlock wants to give you the opportunity to not have to worry about which one to pick**.\n\n###### It's all about abstractions\nThe way the cloud abstracts the hassle of managing your servers, ArcBlock abstracts the hassle of learning how each blockchain works. The API provided by their microservices called **Blocklets remove the pain of figuring out how to integrate blockchains into your business**. Blocklets sit on the top and manage the underlying infrastructure from the business functions all the way down to the blockchains.\n\n##### Financial opportunities, ABT tokens\nArcBlock doesn't do *mining* in the classical sense. Being a decentralized system, it requires servers everywhere to run on. If you happen to have a server somewhere, **you can offer your hardware or cloud instance** to participate in the Blockchain as a Service (BaaS) platform. **Your compensation** for the resources used **will be ABT tokens**.\n\nI think there are exciting opportunities both in developing countries, and countries where cloud services couldn't get a foothold yet. Established cloud data center locations are the usual suspects with all the major players: USA, UK, Germany, China. However, there's usually a huge gap right around where Russia is, also Poland or Turkey. If you want to run a blockchain app off the cloud in Istanbul, odds are your data will need to travel all the way to Germany.\n\nI can also see festivals picking up this kind of technology. If you look at the festivals and events in the last 2-3 years, you'll see an increase in the use of virtual currency on the festival grounds. You want a beer, or a slice of pizza? You'll need to exchange your money to the local tokens. Secure and fast transactions are crucial.\n\n###### Worth for developers, too\nThe way Blocklets communicate with blockchains is not trivial. There's no universal language that both sides understand. Adapters are required to create a link between the two sides. Chain adapters are required, just like the driver for your video card, which need to be written by developers. ArcBlock plans to compensate devs who write such adapters and make them available for the public. Although there doesn't need to be a 100 different adapters for a given blockchain, this is the aspect that intrigues me the most being a developer myself.\n\nCheck out ArcBlock on their [site](https://www.arcblock.io/) and read their [whitepaper](https://www.arcblock.io/file/whitepaper/WhitePaperEnV2_en-US.pdf?v=4). My Bitcointalk [profile](https://bitcointalk.org/index.php?action=profile;u=1715458).\n\n[Via my blog](https://lurkingcode.com/2018/01/20/arcblock-the-backend-of-the-blockchain-3/)",
"json_metadata": "{\"tags\":[\"arcblock\",\"blockchain\",\"blocklet\",\"serverless\",\"microservice\"],\"links\":[\"https://www.arcblock.io/\",\"https://www.arcblock.io/file/whitepaper/WhitePaperEnV2_en-US.pdf?v=4\",\"https://bitcointalk.org/index.php?action=profile;u=1715458\",\"https://lurkingcode.com/2018/01/20/arcblock-the-backend-of-the-blockchain-3/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "arcblock",
"permlink": "arcblock-the-backend-of-the-blockchain-3-0",
"title": "ArcBlock, the backend of the Blockchain 3.0"
}
],
"op_in_trx": 0,
"timestamp": "2018-01-29T20:59:27",
"trx_id": "5d80ff64670696223df10aa0c554eb90d54764d1",
"trx_in_block": 24,
"virtual_op": 0
}2018/01/29 11:49:24
2018/01/29 11:49:24
| active | {"account_auths":[],"key_auths":[["STM7V1ajHmbdBvjUwfdUNzeExtK3iDbdKL8bwzqs55xHcaZnvjUTM",1]],"weight_threshold":1} |
| creator | steem |
| delegation | 29700.000000 VESTS |
| extensions | [] |
| fee | 0.500 STEEM |
| json metadata | |
| memo key | STM7ghaauD9sEWg4SMhQQA6t9fcKEgwWFz2i1ZNejCbU5i3bMJr3K |
| new account name | romeozor |
| owner | {"account_auths":[],"key_auths":[["STM5kx8yi5KbmTwLgDDQU5QvzrF1sMekdhPJ5NuCadeS2QaE9bZ4v",1]],"weight_threshold":1} |
| posting | {"account_auths":[],"key_auths":[["STM5kfMYMaeLxd8Lxe1m6PF4hGex2XWakWEh5jG5yb3vpjro6kSfM",1]],"weight_threshold":1} |
| Transaction Info | Block #19401445/Trx 128423c0c3d30b224e23ce710909084934cc76be |
View Raw JSON Data
{
"block": 19401445,
"op": [
"account_create_with_delegation",
{
"active": {
"account_auths": [],
"key_auths": [
[
"STM7V1ajHmbdBvjUwfdUNzeExtK3iDbdKL8bwzqs55xHcaZnvjUTM",
1
]
],
"weight_threshold": 1
},
"creator": "steem",
"delegation": "29700.000000 VESTS",
"extensions": [],
"fee": "0.500 STEEM",
"json_metadata": "",
"memo_key": "STM7ghaauD9sEWg4SMhQQA6t9fcKEgwWFz2i1ZNejCbU5i3bMJr3K",
"new_account_name": "romeozor",
"owner": {
"account_auths": [],
"key_auths": [
[
"STM5kx8yi5KbmTwLgDDQU5QvzrF1sMekdhPJ5NuCadeS2QaE9bZ4v",
1
]
],
"weight_threshold": 1
},
"posting": {
"account_auths": [],
"key_auths": [
[
"STM5kfMYMaeLxd8Lxe1m6PF4hGex2XWakWEh5jG5yb3vpjro6kSfM",
1
]
],
"weight_threshold": 1
}
}
],
"op_in_trx": 0,
"timestamp": "2018-01-29T11:49:24",
"trx_id": "128423c0c3d30b224e23ce710909084934cc76be",
"trx_in_block": 15,
"virtual_op": 0
}Manabar
Voting Power100.00%
Downvote Power100.00%
Resource Credits100.00%
Reputation Progress0.00%
{
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779083508
},
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779083508
},
"rc_account": {
"account": "romeozor",
"rc_manabar": {
"current_mana": "10164408779",
"last_update_time": 1779083508
},
"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
STM5kx8yi5KbmTwLgDDQU5QvzrF1sMekdhPJ5NuCadeS2QaE9bZ4v1/1
Active
Single Signature
Public Keys
STM7V1ajHmbdBvjUwfdUNzeExtK3iDbdKL8bwzqs55xHcaZnvjUTM1/1
Posting
Single Signature
Public Keys
STM5kfMYMaeLxd8Lxe1m6PF4hGex2XWakWEh5jG5yb3vpjro6kSfM1/1
Memo
STM7ghaauD9sEWg4SMhQQA6t9fcKEgwWFz2i1ZNejCbU5i3bMJr3K
{
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5kx8yi5KbmTwLgDDQU5QvzrF1sMekdhPJ5NuCadeS2QaE9bZ4v",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7V1ajHmbdBvjUwfdUNzeExtK3iDbdKL8bwzqs55xHcaZnvjUTM",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5kfMYMaeLxd8Lxe1m6PF4hGex2XWakWEh5jG5yb3vpjro6kSfM",
1
]
]
},
"memo": "STM7ghaauD9sEWg4SMhQQA6t9fcKEgwWFz2i1ZNejCbU5i3bMJr3K"
}Witness Votes
0 / 30
No active witness votes.
[]