VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS0.00%
Net Worth
0.009USD
STEEM
0.000STEEM
SBD
0.000SBD
Effective Power
5.001SP
├── Own SP
0.170SP
└── Incoming DelegationsDeleg
+4.831SP
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.170SP | SP |
| Delegated Out | 0.000SP | SP |
| Delegation In | 4.831SP | SP |
| Effective Power | 5.001SP | 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": "277.332844 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "7866.326962 VESTS",
"sbd_balance": "0.000 SBD",
"savings_sbd_balance": "0.000 SBD",
"reward_sbd_balance": "0.000 SBD",
"conversions": []
}Account Info
| name | wimpethomas |
| id | 1105605 |
| rank | 239,830 |
| reputation | 755859807 |
| created | 2018-08-14T17:07:12 |
| recovery_account | steem |
| proxy | None |
| post_count | 5 |
| comment_count | 0 |
| lifetime_vote_count | 0 |
| witnesses_voted_for | 0 |
| last_post | 2018-09-30T11:26:42 |
| last_root_post | 2018-09-10T11:50:54 |
| last_vote_time | 2018-09-14T12:11:27 |
| 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 | 277.332844 VESTS |
| delegated_vesting_shares | 0.000000 VESTS |
| received_vesting_shares | 7866.326962 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": 1105605,
"name": "wimpethomas",
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM6TtLp1dTCKPZF4KeSMNTpfyBiv1mKV9XnKc4wGGsaUyzqyW45S",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5zpAQNCeAPzCxPdWzcUhDWG6DvUMurjqBBVegHjRPBd4nPUZKG",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM558Y9pcVPWtfs2xX2gwLv2yfsYfXAVZNXJDtQSJkJnJBM9BaBa",
1
]
]
},
"memo_key": "STM5uthwSYggRTA8j3HDDwDA8v24U6qfTHuDdD3FN7y2MZ78QPuQg",
"json_metadata": "{}",
"posting_json_metadata": "",
"proxy": "",
"last_owner_update": "1970-01-01T00:00:00",
"last_account_update": "1970-01-01T00:00:00",
"created": "2018-08-14T17:07:12",
"mined": false,
"recovery_account": "steem",
"last_account_recovery": "1970-01-01T00:00:00",
"reset_account": "null",
"comment_count": 0,
"lifetime_vote_count": 0,
"post_count": 5,
"can_vote": true,
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779092061
},
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779092061
},
"voting_power": 0,
"balance": "0.000 STEEM",
"savings_balance": "0.000 STEEM",
"sbd_balance": "0.000 SBD",
"sbd_seconds": "0",
"sbd_seconds_last_update": "2018-09-03T10:02:33",
"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": "277.332844 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "7866.326962 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": 38,
"proxied_vsf_votes": [
0,
0,
0,
0
],
"witnesses_voted_for": 0,
"last_post": "2018-09-30T11:26:42",
"last_root_post": "2018-09-10T11:50:54",
"last_vote_time": "2018-09-14T12:11:27",
"post_bandwidth": 0,
"pending_claimed_accounts": 0,
"vesting_balance": "0.000 STEEM",
"reputation": 755859807,
"transfer_history": [],
"market_history": [],
"post_history": [],
"vote_history": [],
"other_history": [],
"witness_votes": [],
"tags_usage": [],
"guest_bloggers": [],
"rank": 239830
}Withdraw Routes
| Incoming | Outgoing |
|---|---|
Empty | Empty |
{
"incoming": [],
"outgoing": []
}From Date
To Date
steemdelegated 4.831 SP to @wimpethomas2026/05/18 08:14:21
steemdelegated 4.831 SP to @wimpethomas
2026/05/18 08:14:21
| delegator | steem |
| delegatee | wimpethomas |
| vesting shares | 7866.326962 VESTS |
| Transaction Info | Block #106152992/Trx 8d3ad91de5c4bf840559305e04eb2e0441d0b6da |
View Raw JSON Data
{
"trx_id": "8d3ad91de5c4bf840559305e04eb2e0441d0b6da",
"block": 106152992,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-05-18T08:14:21",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "wimpethomas",
"vesting_shares": "7866.326962 VESTS"
}
]
}steemdelegated 3.165 SP to @wimpethomas2026/05/13 12:16:12
steemdelegated 3.165 SP to @wimpethomas
2026/05/13 12:16:12
| delegator | steem |
| delegatee | wimpethomas |
| vesting shares | 5154.116557 VESTS |
| Transaction Info | Block #106014537/Trx db7fe17fa581bcdcc1de76964755cb6fd57a67c4 |
View Raw JSON Data
{
"trx_id": "db7fe17fa581bcdcc1de76964755cb6fd57a67c4",
"block": 106014537,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-05-13T12:16:12",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "wimpethomas",
"vesting_shares": "5154.116557 VESTS"
}
]
}steemdelegated 4.838 SP to @wimpethomas2026/04/26 07:23:27
steemdelegated 4.838 SP to @wimpethomas
2026/04/26 07:23:27
| delegator | steem |
| delegatee | wimpethomas |
| vesting shares | 7878.842718 VESTS |
| Transaction Info | Block #105520424/Trx 854ca78a995594868a5594c9d4e31b17dcff7068 |
View Raw JSON Data
{
"trx_id": "854ca78a995594868a5594c9d4e31b17dcff7068",
"block": 105520424,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-04-26T07:23:27",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "wimpethomas",
"vesting_shares": "7878.842718 VESTS"
}
]
}steemdelegated 3.191 SP to @wimpethomas2026/01/24 05:16:30
steemdelegated 3.191 SP to @wimpethomas
2026/01/24 05:16:30
| delegator | steem |
| delegatee | wimpethomas |
| vesting shares | 5195.663376 VESTS |
| Transaction Info | Block #102877524/Trx aee6b453645a3e29126694445c2dec339e725157 |
View Raw JSON Data
{
"trx_id": "aee6b453645a3e29126694445c2dec339e725157",
"block": 102877524,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-01-24T05:16:30",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "wimpethomas",
"vesting_shares": "5195.663376 VESTS"
}
]
}steemdelegated 3.292 SP to @wimpethomas2024/12/18 00:25:21
steemdelegated 3.292 SP to @wimpethomas
2024/12/18 00:25:21
| delegator | steem |
| delegatee | wimpethomas |
| vesting shares | 5359.882573 VESTS |
| Transaction Info | Block #91323721/Trx a059d29087fc72114ad442fb2715c56385bbb818 |
View Raw JSON Data
{
"trx_id": "a059d29087fc72114ad442fb2715c56385bbb818",
"block": 91323721,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2024-12-18T00:25:21",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "wimpethomas",
"vesting_shares": "5359.882573 VESTS"
}
]
}steemdelegated 3.395 SP to @wimpethomas2023/11/14 16:04:15
steemdelegated 3.395 SP to @wimpethomas
2023/11/14 16:04:15
| delegator | steem |
| delegatee | wimpethomas |
| vesting shares | 5529.016105 VESTS |
| Transaction Info | Block #79877813/Trx d9328130c9df3f1dea62b8d6c605f1d1c8f33543 |
View Raw JSON Data
{
"trx_id": "d9328130c9df3f1dea62b8d6c605f1d1c8f33543",
"block": 79877813,
"trx_in_block": 10,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2023-11-14T16:04:15",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "wimpethomas",
"vesting_shares": "5529.016105 VESTS"
}
]
}steemdelegated 5.199 SP to @wimpethomas2023/09/22 12:41:57
steemdelegated 5.199 SP to @wimpethomas
2023/09/22 12:41:57
| delegator | steem |
| delegatee | wimpethomas |
| vesting shares | 8465.924891 VESTS |
| Transaction Info | Block #78365626/Trx a3ec85530770b32fb86547a4798437871983d3b4 |
View Raw JSON Data
{
"trx_id": "a3ec85530770b32fb86547a4798437871983d3b4",
"block": 78365626,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2023-09-22T12:41:57",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "wimpethomas",
"vesting_shares": "8465.924891 VESTS"
}
]
}steemdelegated 5.335 SP to @wimpethomas2022/11/03 19:52:18
steemdelegated 5.335 SP to @wimpethomas
2022/11/03 19:52:18
| delegator | steem |
| delegatee | wimpethomas |
| vesting shares | 8687.976329 VESTS |
| Transaction Info | Block #69123019/Trx 7b4e675fa1aa44a22f42ff56e27a045804b9054e |
View Raw JSON Data
{
"trx_id": "7b4e675fa1aa44a22f42ff56e27a045804b9054e",
"block": 69123019,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2022-11-03T19:52:18",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "wimpethomas",
"vesting_shares": "8687.976329 VESTS"
}
]
}steemdelegated 5.471 SP to @wimpethomas2022/01/18 00:52:48
steemdelegated 5.471 SP to @wimpethomas
2022/01/18 00:52:48
| delegator | steem |
| delegatee | wimpethomas |
| vesting shares | 8908.083930 VESTS |
| Transaction Info | Block #60826039/Trx 7244f056b3f8830fa50b9d6e0e518b8a93e741a0 |
View Raw JSON Data
{
"trx_id": "7244f056b3f8830fa50b9d6e0e518b8a93e741a0",
"block": 60826039,
"trx_in_block": 31,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2022-01-18T00:52:48",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "wimpethomas",
"vesting_shares": "8908.083930 VESTS"
}
]
}steemdelegated 5.584 SP to @wimpethomas2021/06/14 07:58:51
steemdelegated 5.584 SP to @wimpethomas
2021/06/14 07:58:51
| delegator | steem |
| delegatee | wimpethomas |
| vesting shares | 9092.278218 VESTS |
| Transaction Info | Block #54616259/Trx 5edf1c84fd43b9e9ab805be82c6958de7b61c183 |
View Raw JSON Data
{
"trx_id": "5edf1c84fd43b9e9ab805be82c6958de7b61c183",
"block": 54616259,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2021-06-14T07:58:51",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "wimpethomas",
"vesting_shares": "9092.278218 VESTS"
}
]
}steemdelegated 5.699 SP to @wimpethomas2020/12/11 18:09:12
steemdelegated 5.699 SP to @wimpethomas
2020/12/11 18:09:12
| delegator | steem |
| delegatee | wimpethomas |
| vesting shares | 9279.700192 VESTS |
| Transaction Info | Block #49363459/Trx fde6fba9ed7e4730ee852b2f4f4d56ec90ade9b9 |
View Raw JSON Data
{
"trx_id": "fde6fba9ed7e4730ee852b2f4f4d56ec90ade9b9",
"block": 49363459,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-12-11T18:09:12",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "wimpethomas",
"vesting_shares": "9279.700192 VESTS"
}
]
}steemdelegated 1.175 SP to @wimpethomas2020/12/06 11:44:15
steemdelegated 1.175 SP to @wimpethomas
2020/12/06 11:44:15
| delegator | steem |
| delegatee | wimpethomas |
| vesting shares | 1912.543513 VESTS |
| Transaction Info | Block #49214972/Trx d736b1b0c8145d64a620cb9d99d4b9adf5e2e689 |
View Raw JSON Data
{
"trx_id": "d736b1b0c8145d64a620cb9d99d4b9adf5e2e689",
"block": 49214972,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-12-06T11:44:15",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "wimpethomas",
"vesting_shares": "1912.543513 VESTS"
}
]
}steemdelegated 5.703 SP to @wimpethomas2020/12/05 21:47:00
steemdelegated 5.703 SP to @wimpethomas
2020/12/05 21:47:00
| delegator | steem |
| delegatee | wimpethomas |
| vesting shares | 9285.908046 VESTS |
| Transaction Info | Block #49198543/Trx c929f4a1ece51d27c617af489dfa9306c704a297 |
View Raw JSON Data
{
"trx_id": "c929f4a1ece51d27c617af489dfa9306c704a297",
"block": 49198543,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-12-05T21:47:00",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "wimpethomas",
"vesting_shares": "9285.908046 VESTS"
}
]
}steemdelegated 1.179 SP to @wimpethomas2020/11/03 06:13:03
steemdelegated 1.179 SP to @wimpethomas
2020/11/03 06:13:03
| delegator | steem |
| delegatee | wimpethomas |
| vesting shares | 1920.017158 VESTS |
| Transaction Info | Block #48274966/Trx f5f0b4eff910ae40eb57189e139711380e25ceec |
View Raw JSON Data
{
"trx_id": "f5f0b4eff910ae40eb57189e139711380e25ceec",
"block": 48274966,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-11-03T06:13:03",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "wimpethomas",
"vesting_shares": "1920.017158 VESTS"
}
]
}steemdelegated 5.827 SP to @wimpethomas2020/05/09 12:49:09
steemdelegated 5.827 SP to @wimpethomas
2020/05/09 12:49:09
| delegator | steem |
| delegatee | wimpethomas |
| vesting shares | 9488.713405 VESTS |
| Transaction Info | Block #43225331/Trx 36643fe67aa931468cb7ded4db1d27d31b142896 |
View Raw JSON Data
{
"trx_id": "36643fe67aa931468cb7ded4db1d27d31b142896",
"block": 43225331,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-05-09T12:49:09",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "wimpethomas",
"vesting_shares": "9488.713405 VESTS"
}
]
}steemdelegated 1.200 SP to @wimpethomas2020/05/08 17:29:12
steemdelegated 1.200 SP to @wimpethomas
2020/05/08 17:29:12
| delegator | steem |
| delegatee | wimpethomas |
| vesting shares | 1953.311140 VESTS |
| Transaction Info | Block #43202674/Trx 6af380ba7cb15c2425f2621646044bfe75604e00 |
View Raw JSON Data
{
"trx_id": "6af380ba7cb15c2425f2621646044bfe75604e00",
"block": 43202674,
"trx_in_block": 12,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-05-08T17:29:12",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "wimpethomas",
"vesting_shares": "1953.311140 VESTS"
}
]
}steemdelegated 5.881 SP to @wimpethomas2019/12/02 19:58:21
steemdelegated 5.881 SP to @wimpethomas
2019/12/02 19:58:21
| delegator | steem |
| delegatee | wimpethomas |
| vesting shares | 9576.504056 VESTS |
| Transaction Info | Block #38693828/Trx 35de2dcf1719c76eabff7ef5d3bf22abd8c5261b |
View Raw JSON Data
{
"trx_id": "35de2dcf1719c76eabff7ef5d3bf22abd8c5261b",
"block": 38693828,
"trx_in_block": 10,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-12-02T19:58:21",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "wimpethomas",
"vesting_shares": "9576.504056 VESTS"
}
]
}2019/08/14 20:01:06
2019/08/14 20:01:06
| parent author | wimpethomas |
| parent permlink | the-problems-with-byteball |
| author | steemitboard |
| permlink | steemitboard-notify-wimpethomas-20190814t200106000z |
| title | |
| body | Congratulations @wimpethomas! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@wimpethomas/birthday1.png</td><td>Happy Birthday! - You are on the Steem blockchain for 1 year!</td></tr></table> <sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@wimpethomas) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=wimpethomas)_</sub> ###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| Transaction Info | Block #35554015/Trx ae8434362f1aaa18243a90b235f0046414d22bc6 |
View Raw JSON Data
{
"trx_id": "ae8434362f1aaa18243a90b235f0046414d22bc6",
"block": 35554015,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-08-14T20:01:06",
"op": [
"comment",
{
"parent_author": "wimpethomas",
"parent_permlink": "the-problems-with-byteball",
"author": "steemitboard",
"permlink": "steemitboard-notify-wimpethomas-20190814t200106000z",
"title": "",
"body": "Congratulations @wimpethomas! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@wimpethomas/birthday1.png</td><td>Happy Birthday! - You are on the Steem blockchain for 1 year!</td></tr></table>\n\n<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@wimpethomas) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=wimpethomas)_</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\"]}"
}
]
}steemdelegated 6.002 SP to @wimpethomas2018/12/30 13:00:48
steemdelegated 6.002 SP to @wimpethomas
2018/12/30 13:00:48
| delegator | steem |
| delegatee | wimpethomas |
| vesting shares | 9773.635133 VESTS |
| Transaction Info | Block #29017240/Trx 344025695f13f237e9b1e7be4880a9719abec852 |
View Raw JSON Data
{
"trx_id": "344025695f13f237e9b1e7be4880a9719abec852",
"block": 29017240,
"trx_in_block": 29,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-12-30T13:00:48",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "wimpethomas",
"vesting_shares": "9773.635133 VESTS"
}
]
}steemdelegated 18.382 SP to @wimpethomas2018/11/26 20:01:27
steemdelegated 18.382 SP to @wimpethomas
2018/11/26 20:01:27
| delegator | steem |
| delegatee | wimpethomas |
| vesting shares | 29932.429284 VESTS |
| Transaction Info | Block #28046969/Trx fe693ec77fbc492665a0fa6a75721caad4f49d97 |
View Raw JSON Data
{
"trx_id": "fe693ec77fbc492665a0fa6a75721caad4f49d97",
"block": 28046969,
"trx_in_block": 16,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-11-26T20:01:27",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "wimpethomas",
"vesting_shares": "29932.429284 VESTS"
}
]
}wimpethomasfollowed @onasander2018/10/16 12:30:45
wimpethomasfollowed @onasander
2018/10/16 12:30:45
| required auths | [] |
| required posting auths | ["wimpethomas"] |
| id | follow |
| json | ["follow",{"follower":"wimpethomas","following":"onasander","what":["blog"]}] |
| Transaction Info | Block #26857964/Trx 0d92651fcdd1d10c285971f5e0f0bed36412735f |
View Raw JSON Data
{
"trx_id": "0d92651fcdd1d10c285971f5e0f0bed36412735f",
"block": 26857964,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-10-16T12:30:45",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"wimpethomas"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"wimpethomas\",\"following\":\"onasander\",\"what\":[\"blog\"]}]"
}
]
}wimpethomasupvoted (100.00%) @onasander / 2018-stock-market-crash-warning2018/10/16 12:30:27
wimpethomasupvoted (100.00%) @onasander / 2018-stock-market-crash-warning
2018/10/16 12:30:27
| voter | wimpethomas |
| author | onasander |
| permlink | 2018-stock-market-crash-warning |
| weight | 10000 (100.00%) |
| Transaction Info | Block #26857958/Trx 9808b553f4da538e06ffd473e923645a2a3e3fd6 |
View Raw JSON Data
{
"trx_id": "9808b553f4da538e06ffd473e923645a2a3e3fd6",
"block": 26857958,
"trx_in_block": 13,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-10-16T12:30:27",
"op": [
"vote",
{
"voter": "wimpethomas",
"author": "onasander",
"permlink": "2018-stock-market-crash-warning",
"weight": 10000
}
]
}2018/09/30 11:26:42
2018/09/30 11:26:42
| parent author | openpackaging |
| parent permlink | making-order-out-of-chaos-in-the-crazy-world-of-tokens |
| author | wimpethomas |
| permlink | re-openpackaging-making-order-out-of-chaos-in-the-crazy-world-of-tokens-20180930t112639748z |
| title | |
| body | Promising project |
| json metadata | {"tags":["blockchain"],"app":"steemit/0.1"} |
| Transaction Info | Block #26396202/Trx dc683110ce14d0866fd6e0b1c20ef72bc84c5fe2 |
View Raw JSON Data
{
"trx_id": "dc683110ce14d0866fd6e0b1c20ef72bc84c5fe2",
"block": 26396202,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-09-30T11:26:42",
"op": [
"comment",
{
"parent_author": "openpackaging",
"parent_permlink": "making-order-out-of-chaos-in-the-crazy-world-of-tokens",
"author": "wimpethomas",
"permlink": "re-openpackaging-making-order-out-of-chaos-in-the-crazy-world-of-tokens-20180930t112639748z",
"title": "",
"body": "Promising project",
"json_metadata": "{\"tags\":[\"blockchain\"],\"app\":\"steemit/0.1\"}"
}
]
}wimpethomasfollowed @openpackaging2018/09/30 11:26:12
wimpethomasfollowed @openpackaging
2018/09/30 11:26:12
| required auths | [] |
| required posting auths | ["wimpethomas"] |
| id | follow |
| json | ["follow",{"follower":"wimpethomas","following":"openpackaging","what":["blog"]}] |
| Transaction Info | Block #26396192/Trx 46ebd38c68a74eb0418908c07816faf53b1621f0 |
View Raw JSON Data
{
"trx_id": "46ebd38c68a74eb0418908c07816faf53b1621f0",
"block": 26396192,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-09-30T11:26:12",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"wimpethomas"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"wimpethomas\",\"following\":\"openpackaging\",\"what\":[\"blog\"]}]"
}
]
}wimpethomaspowered up 0.018 STEEM to @wimpethomas2018/09/30 11:25:27
wimpethomaspowered up 0.018 STEEM to @wimpethomas
2018/09/30 11:25:27
| from | wimpethomas |
| to | wimpethomas |
| amount | 0.018 STEEM |
| Transaction Info | Block #26396177/Trx 77bb9808171a03b7d857578cd1506c4984175724 |
View Raw JSON Data
{
"trx_id": "77bb9808171a03b7d857578cd1506c4984175724",
"block": 26396177,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-09-30T11:25:27",
"op": [
"transfer_to_vesting",
{
"from": "wimpethomas",
"to": "wimpethomas",
"amount": "0.018 STEEM"
}
]
}tsonkomirchevupvoted (100.00%) @wimpethomas / the-problems-with-byteball2018/09/15 20:11:21
tsonkomirchevupvoted (100.00%) @wimpethomas / the-problems-with-byteball
2018/09/15 20:11:21
| voter | tsonkomirchev |
| author | wimpethomas |
| permlink | the-problems-with-byteball |
| weight | 10000 (100.00%) |
| Transaction Info | Block #25990745/Trx ed57dca3d6f20be2b153829b49156cc47f12c49f |
View Raw JSON Data
{
"trx_id": "ed57dca3d6f20be2b153829b49156cc47f12c49f",
"block": 25990745,
"trx_in_block": 25,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-09-15T20:11:21",
"op": [
"vote",
{
"voter": "tsonkomirchev",
"author": "wimpethomas",
"permlink": "the-problems-with-byteball",
"weight": 10000
}
]
}2018/09/14 12:11:27
2018/09/14 12:11:27
| voter | wimpethomas |
| author | byteball.market |
| permlink | re-wimpethomas-the-problems-with-byteball-20180912t033134839z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #25952349/Trx d066c03fe44ec2ccedc8030c01ce659749b2603e |
View Raw JSON Data
{
"trx_id": "d066c03fe44ec2ccedc8030c01ce659749b2603e",
"block": 25952349,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-09-14T12:11:27",
"op": [
"vote",
{
"voter": "wimpethomas",
"author": "byteball.market",
"permlink": "re-wimpethomas-the-problems-with-byteball-20180912t033134839z",
"weight": 10000
}
]
}altcoinbupvoted (100.00%) @wimpethomas / the-problems-with-byteball2018/09/12 21:40:00
altcoinbupvoted (100.00%) @wimpethomas / the-problems-with-byteball
2018/09/12 21:40:00
| voter | altcoinb |
| author | wimpethomas |
| permlink | the-problems-with-byteball |
| weight | 10000 (100.00%) |
| Transaction Info | Block #25906139/Trx a1cfabb87215c6fb63d30f79047431141edb7104 |
View Raw JSON Data
{
"trx_id": "a1cfabb87215c6fb63d30f79047431141edb7104",
"block": 25906139,
"trx_in_block": 32,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-09-12T21:40:00",
"op": [
"vote",
{
"voter": "altcoinb",
"author": "wimpethomas",
"permlink": "the-problems-with-byteball",
"weight": 10000
}
]
}2018/09/12 15:35:09
2018/09/12 15:35:09
| parent author | wimpethomas |
| parent permlink | re-tarmo888-re-wimpethomas-the-problems-with-byteball-20180911t133811100z |
| author | tarmo888 |
| permlink | re-wimpethomas-re-tarmo888-re-wimpethomas-the-problems-with-byteball-20180911t173720110z |
| title | |
| body | @@ -1209,16 +1209,27 @@ ounts.%0A%0A +2) great.%0A%0A 3) Well, |
| json metadata | {"community":"busy","app":"busy/2.5.6","format":"markdown","tags":["byteball"],"users":[],"links":[],"image":[]} |
| Transaction Info | Block #25898844/Trx f23c29c18c897f6f0a857d6ad98b0c130a8e34ea |
View Raw JSON Data
{
"trx_id": "f23c29c18c897f6f0a857d6ad98b0c130a8e34ea",
"block": 25898844,
"trx_in_block": 28,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-09-12T15:35:09",
"op": [
"comment",
{
"parent_author": "wimpethomas",
"parent_permlink": "re-tarmo888-re-wimpethomas-the-problems-with-byteball-20180911t133811100z",
"author": "tarmo888",
"permlink": "re-wimpethomas-re-tarmo888-re-wimpethomas-the-problems-with-byteball-20180911t173720110z",
"title": "",
"body": "@@ -1209,16 +1209,27 @@\n ounts.%0A%0A\n+2) great.%0A%0A\n 3) Well,\n",
"json_metadata": "{\"community\":\"busy\",\"app\":\"busy/2.5.6\",\"format\":\"markdown\",\"tags\":[\"byteball\"],\"users\":[],\"links\":[],\"image\":[]}"
}
]
}milcsixupvoted (100.00%) @wimpethomas / the-problems-with-byteball2018/09/12 08:03:42
milcsixupvoted (100.00%) @wimpethomas / the-problems-with-byteball
2018/09/12 08:03:42
| voter | milcsix |
| author | wimpethomas |
| permlink | the-problems-with-byteball |
| weight | 10000 (100.00%) |
| Transaction Info | Block #25889820/Trx b873daeb8e4d838c203f76721210e895ef3d65dc |
View Raw JSON Data
{
"trx_id": "b873daeb8e4d838c203f76721210e895ef3d65dc",
"block": 25889820,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-09-12T08:03:42",
"op": [
"vote",
{
"voter": "milcsix",
"author": "wimpethomas",
"permlink": "the-problems-with-byteball",
"weight": 10000
}
]
}2018/09/12 03:31:36
2018/09/12 03:31:36
| parent author | wimpethomas |
| parent permlink | the-problems-with-byteball |
| author | byteball.market |
| permlink | re-wimpethomas-the-problems-with-byteball-20180912t033134839z |
| title | |
| body | First of all, it's great that you tried Byteball and took the time to write a post about it. I totally understand your frustration, however, you have to keep in mind that crypto is in a very early stage and you are an early adopter. Crypto brings a bunch of new concepts a regular user is not familiar with and even though some of the smartest developers work in this space, they are usually not the best at designing user interfaces. Creating an easy to use straightforward product based on a cutting edge technology that is disrupting the current banking and financial systems is extremely difficult. It requires many iterations, probably several years, until it becomes easily adoptable by the mainstream user. I remember when the Internet came in my high school, the IT teachers told us it was not interesting and there was nothing to see :) At that time it was mainly text based, the World Wide Web was in it's early stage and we used a different protocol called Gopher to browse contents available mainly on university servers. It wasn't user friendly at all, but what would have happened if the developers hadn't released those apps and technologies and instead had waited for a time until they could come up with YouTube and Twitter and Instagram to make it consumable to the majority? Very little progress would have been made and probably they would still be working on Netscape 1.0 in their labs and wondering if it was user friendly enough already to release. So I would encourage you to keep experimenting with Byteball and give your feedback to the community and the developers so they can keep iterating and fine tuning the apps to make it more user friendly. That is how progress will be made. |
| json metadata | {"community":"busy","app":"busy/2.5.6","format":"markdown","tags":["byteball"],"users":[],"links":[],"image":[]} |
| Transaction Info | Block #25884378/Trx fa92475d39b6ea69d1dd0c358492da62083e8722 |
View Raw JSON Data
{
"trx_id": "fa92475d39b6ea69d1dd0c358492da62083e8722",
"block": 25884378,
"trx_in_block": 14,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-09-12T03:31:36",
"op": [
"comment",
{
"parent_author": "wimpethomas",
"parent_permlink": "the-problems-with-byteball",
"author": "byteball.market",
"permlink": "re-wimpethomas-the-problems-with-byteball-20180912t033134839z",
"title": "",
"body": "First of all, it's great that you tried Byteball and took the time to write a post about it. I totally understand your frustration, however, you have to keep in mind that crypto is in a very early stage and you are an early adopter. Crypto brings a bunch of new concepts a regular user is not familiar with and even though some of the smartest developers work in this space, they are usually not the best at designing user interfaces.\nCreating an easy to use straightforward product based on a cutting edge technology that is disrupting the current banking and financial systems is extremely difficult. It requires many iterations, probably several years, until it becomes easily adoptable by the mainstream user.\nI remember when the Internet came in my high school, the IT teachers told us it was not interesting and there was nothing to see :) At that time it was mainly text based, the World Wide Web was in it's early stage and we used a different protocol called Gopher to browse contents available mainly on university servers. It wasn't user friendly at all, but what would have happened if the developers hadn't released those apps and technologies and instead had waited for a time until they could come up with YouTube and Twitter and Instagram to make it consumable to the majority? Very little progress would have been made and probably they would still be working on Netscape 1.0 in their labs and wondering if it was user friendly enough already to release.\nSo I would encourage you to keep experimenting with Byteball and give your feedback to the community and the developers so they can keep iterating and fine tuning the apps to make it more user friendly. That is how progress will be made.",
"json_metadata": "{\"community\":\"busy\",\"app\":\"busy/2.5.6\",\"format\":\"markdown\",\"tags\":[\"byteball\"],\"users\":[],\"links\":[],\"image\":[]}"
}
]
}2018/09/11 17:37:21
2018/09/11 17:37:21
| parent author | wimpethomas |
| parent permlink | re-tarmo888-re-wimpethomas-the-problems-with-byteball-20180911t133811100z |
| author | tarmo888 |
| permlink | re-wimpethomas-re-tarmo888-re-wimpethomas-the-problems-with-byteball-20180911t173720110z |
| title | |
| body | 1) These bets don't have to be offered by bots, anybody can offer those odds. but these are not offered by Byteball Foundation, there is no central bookmaker, so anybody can offer any odds they want and if there is nobody offering any better odds then these are the odds they see. Other betting sites can offer odds with small margins because they have lot of volume to cover their risk, but Byteball or any other cryptocurrency betting doesn't have that many users or volume yet. So, yeah, it's like catch-22 issue, but I don't see what is the solution here, how to you motivate more people to risk their money if there is not even enough of volume to cover the risks? I mean, am I been able to convince you to offer odds in bet maker mode? Probably not. And I actually don't understand this thing about the lower odds. If you are so sure that the team is going to win, it shouldn't matter for you if the odds are 1.4 or 1.5, you still going to win 1.4x times the money you had if that is a sure win. Your alternative is to use the regular betting sites and in some cases, you don't have that alternative at all because you might not have access to these sites. Just like a lot of people don't have bank accounts. 3) Well, the way you set up the bet with a person you know is just an example what the platform can do. So yeah, it is for more advanced users who know what they are doing, but that is also a reason why there is Sports Betting bot, which is built on top of it and takes a way all that frustrating part of finding other counterpart and pairing with them. Anybody can build on those features another services that focuses only making bets with friends, but if there isn't enough people for existing Sports Betting bot, there is no motivation to streamline the way to make bets with friends. That feature is for advanced users, everybody is better off using BB Odds and Sports Betting bot. Most likely, new technologies like blockchain will be accepted more buy new generation and they are very familiar with chatting apps (many don't even have computers, just smartphones), but maybe until then, websites like BB Odds need to be built along with the bots. And about that smart-contract thing, that is much easier to read that any Ethereum smart-contract and once you understand it, it is just as easy as scrolling down the Terms of Use page and clicking "I accept". |
| json metadata | {"community":"busy","app":"busy/2.5.6","format":"markdown","tags":["byteball"],"users":[],"links":[],"image":[]} |
| Transaction Info | Block #25872495/Trx 9f4437775b95dd98cd704dcf374b4a5e1df379ad |
View Raw JSON Data
{
"trx_id": "9f4437775b95dd98cd704dcf374b4a5e1df379ad",
"block": 25872495,
"trx_in_block": 16,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-09-11T17:37:21",
"op": [
"comment",
{
"parent_author": "wimpethomas",
"parent_permlink": "re-tarmo888-re-wimpethomas-the-problems-with-byteball-20180911t133811100z",
"author": "tarmo888",
"permlink": "re-wimpethomas-re-tarmo888-re-wimpethomas-the-problems-with-byteball-20180911t173720110z",
"title": "",
"body": "1) These bets don't have to be offered by bots, anybody can offer those odds. but these are not offered by Byteball Foundation, there is no central bookmaker, so anybody can offer any odds they want and if there is nobody offering any better odds then these are the odds they see. Other betting sites can offer odds with small margins because they have lot of volume to cover their risk, but Byteball or any other cryptocurrency betting doesn't have that many users or volume yet. So, yeah, it's like catch-22 issue, but I don't see what is the solution here, how to you motivate more people to risk their money if there is not even enough of volume to cover the risks? I mean, am I been able to convince you to offer odds in bet maker mode? Probably not.\nAnd I actually don't understand this thing about the lower odds. If you are so sure that the team is going to win, it shouldn't matter for you if the odds are 1.4 or 1.5, you still going to win 1.4x times the money you had if that is a sure win. Your alternative is to use the regular betting sites and in some cases, you don't have that alternative at all because you might not have access to these sites. Just like a lot of people don't have bank accounts.\n\n3) Well, the way you set up the bet with a person you know is just an example what the platform can do. So yeah, it is for more advanced users who know what they are doing, but that is also a reason why there is Sports Betting bot, which is built on top of it and takes a way all that frustrating part of finding other counterpart and pairing with them. Anybody can build on those features another services that focuses only making bets with friends, but if there isn't enough people for existing Sports Betting bot, there is no motivation to streamline the way to make bets with friends. That feature is for advanced users, everybody is better off using BB Odds and Sports Betting bot.\nMost likely, new technologies like blockchain will be accepted more buy new generation and they are very familiar with chatting apps (many don't even have computers, just smartphones), but maybe until then, websites like BB Odds need to be built along with the bots. And about that smart-contract thing, that is much easier to read that any Ethereum smart-contract and once you understand it, it is just as easy as scrolling down the Terms of Use page and clicking \"I accept\".",
"json_metadata": "{\"community\":\"busy\",\"app\":\"busy/2.5.6\",\"format\":\"markdown\",\"tags\":[\"byteball\"],\"users\":[],\"links\":[],\"image\":[]}"
}
]
}wimpethomasmuted @steemitboard2018/09/11 13:40:09
wimpethomasmuted @steemitboard
2018/09/11 13:40:09
| required auths | [] |
| required posting auths | ["wimpethomas"] |
| id | follow |
| json | ["follow",{"follower":"wimpethomas","following":"steemitboard","what":["ignore"]}] |
| Transaction Info | Block #25867751/Trx e497141bc5ce66ebf80a662c130c846fa72681d1 |
View Raw JSON Data
{
"trx_id": "e497141bc5ce66ebf80a662c130c846fa72681d1",
"block": 25867751,
"trx_in_block": 12,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-09-11T13:40:09",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"wimpethomas"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"wimpethomas\",\"following\":\"steemitboard\",\"what\":[\"ignore\"]}]"
}
]
}2018/09/11 13:39:36
2018/09/11 13:39:36
| parent author | tarmo888 |
| parent permlink | re-wimpethomas-the-problems-with-byteball-20180911t114416850z |
| author | wimpethomas |
| permlink | re-tarmo888-re-wimpethomas-the-problems-with-byteball-20180911t133811100z |
| title | |
| body | @@ -606,19 +606,18 @@ ontract -are +is way to |
| json metadata | {"tags":["byteball"],"app":"steemit/0.1"} |
| Transaction Info | Block #25867740/Trx 419d91ece499abeeb4380e110598ccd8669e160f |
View Raw JSON Data
{
"trx_id": "419d91ece499abeeb4380e110598ccd8669e160f",
"block": 25867740,
"trx_in_block": 14,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-09-11T13:39:36",
"op": [
"comment",
{
"parent_author": "tarmo888",
"parent_permlink": "re-wimpethomas-the-problems-with-byteball-20180911t114416850z",
"author": "wimpethomas",
"permlink": "re-tarmo888-re-wimpethomas-the-problems-with-byteball-20180911t133811100z",
"title": "",
"body": "@@ -606,19 +606,18 @@\n ontract \n-are\n+is\n way to \n",
"json_metadata": "{\"tags\":[\"byteball\"],\"app\":\"steemit/0.1\"}"
}
]
}2018/09/11 13:38:12
2018/09/11 13:38:12
| parent author | tarmo888 |
| parent permlink | re-wimpethomas-the-problems-with-byteball-20180911t114416850z |
| author | wimpethomas |
| permlink | re-tarmo888-re-wimpethomas-the-problems-with-byteball-20180911t133811100z |
| title | |
| body | Thanks for your reply and some additional insights. 2) I didn't know that these quotes are the results of offered bots (see bullet 3), because for me as a user it is not clear how to make an offer. My point in general is that regular users will abandon the service if quotes - for whatever reason - keep being lower than quotes on other services. Regardless the underlying reasons. 3) Thanks for that info, I didn't know that. I will look into the article. 4) Maybe the chatbot isn't the best example, but let's be honest here. The way to set up a contract (betting offer in this case) and read back the contract are way to difficult for regular users and will scare them of. It's not nitpicking, because I really hope for this platform to succeed and I am more than willing to tolerate shortcomings because of the platforms novelty, but no substantial growth will happen with this user interface. |
| json metadata | {"tags":["byteball"],"app":"steemit/0.1"} |
| Transaction Info | Block #25867712/Trx c66bfeabf11baf60cab4f02fcc9414eb353cb0c4 |
View Raw JSON Data
{
"trx_id": "c66bfeabf11baf60cab4f02fcc9414eb353cb0c4",
"block": 25867712,
"trx_in_block": 16,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-09-11T13:38:12",
"op": [
"comment",
{
"parent_author": "tarmo888",
"parent_permlink": "re-wimpethomas-the-problems-with-byteball-20180911t114416850z",
"author": "wimpethomas",
"permlink": "re-tarmo888-re-wimpethomas-the-problems-with-byteball-20180911t133811100z",
"title": "",
"body": "Thanks for your reply and some additional insights.\n2) I didn't know that these quotes are the results of offered bots (see bullet 3), because for me as a user it is not clear how to make an offer. My point in general is that regular users will abandon the service if quotes - for whatever reason - keep being lower than quotes on other services. Regardless the underlying reasons.\n3) Thanks for that info, I didn't know that. I will look into the article.\n4) Maybe the chatbot isn't the best example, but let's be honest here. The way to set up a contract (betting offer in this case) and read back the contract are way to difficult for regular users and will scare them of. It's not nitpicking, because I really hope for this platform to succeed and I am more than willing to tolerate shortcomings because of the platforms novelty, but no substantial growth will happen with this user interface.",
"json_metadata": "{\"tags\":[\"byteball\"],\"app\":\"steemit/0.1\"}"
}
]
}papabyteupvoted (100.00%) @wimpethomas / the-problems-with-byteball2018/09/11 12:05:18
papabyteupvoted (100.00%) @wimpethomas / the-problems-with-byteball
2018/09/11 12:05:18
| voter | papabyte |
| author | wimpethomas |
| permlink | the-problems-with-byteball |
| weight | 10000 (100.00%) |
| Transaction Info | Block #25865855/Trx 1fd925d74f912a570aeca12ae358eb041246347b |
View Raw JSON Data
{
"trx_id": "1fd925d74f912a570aeca12ae358eb041246347b",
"block": 25865855,
"trx_in_block": 43,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-09-11T12:05:18",
"op": [
"vote",
{
"voter": "papabyte",
"author": "wimpethomas",
"permlink": "the-problems-with-byteball",
"weight": 10000
}
]
}2018/09/11 11:58:39
2018/09/11 11:58:39
| parent author | wimpethomas |
| parent permlink | the-problems-with-byteball |
| author | tarmo888 |
| permlink | re-wimpethomas-the-problems-with-byteball-20180911t114416850z |
| title | |
| body | @@ -241,22 +241,16 @@ et them -can't accept r |
| json metadata | {"community":"busy","app":"busy/2.5.6","format":"markdown","tags":["byteball"],"users":[],"links":["https://www.oddschecker.com/","https://bb-odds.herokuapp.com/","https://bb-odds.herokuapp.com/maker.html","https://medium.com/byteball/new-tool-makes-the-byteball-betting-bot-more-user-friendly-and-enticing-to-both-cryptocurrency-7191f14a7460"],"image":[]} |
| Transaction Info | Block #25865722/Trx 97347edcc3b19eb202148950d89026842a32b176 |
View Raw JSON Data
{
"trx_id": "97347edcc3b19eb202148950d89026842a32b176",
"block": 25865722,
"trx_in_block": 11,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-09-11T11:58:39",
"op": [
"comment",
{
"parent_author": "wimpethomas",
"parent_permlink": "the-problems-with-byteball",
"author": "tarmo888",
"permlink": "re-wimpethomas-the-problems-with-byteball-20180911t114416850z",
"title": "",
"body": "@@ -241,22 +241,16 @@\n et them \n-can't \n accept r\n",
"json_metadata": "{\"community\":\"busy\",\"app\":\"busy/2.5.6\",\"format\":\"markdown\",\"tags\":[\"byteball\"],\"users\":[],\"links\":[\"https://www.oddschecker.com/\",\"https://bb-odds.herokuapp.com/\",\"https://bb-odds.herokuapp.com/maker.html\",\"https://medium.com/byteball/new-tool-makes-the-byteball-betting-bot-more-user-friendly-and-enticing-to-both-cryptocurrency-7191f14a7460\"],\"image\":[]}"
}
]
}2018/09/11 11:44:18
2018/09/11 11:44:18
| parent author | wimpethomas |
| parent permlink | the-problems-with-byteball |
| author | tarmo888 |
| permlink | re-wimpethomas-the-problems-with-byteball-20180911t114416850z |
| title | |
| body | 1) Yes, this is a problem of all cryptocurrencies, but there isn't any good solution for that problem other than adding a support for some stable coin like Tether. Many exchanges do that because they don't have a bank account, which would let them can't accept real fiat money for cryptocurrencies. Maybe some wallets support multiple cryptocurrencies and some of them are stablecoins, but generally, if you need to interact with blockchain of any cryptocurrency, you need to use native currency. For some, it is because that is the only currency there is on that cryptocurrency platform and for others that is a only currency that miners only accept. For example, you can't send ERC20 tokens on Ethereum without paying the fees in ETH. The price volatility is because cryptocurrencies are still too small, there aren't enough people to get it more stable because there is always some people who could dump their coins at low price. Another reason for it could be that it is so easy to do with cryptocurrencies, but so much difficult to do with fiat money. 2) Fees on Byteball are super cheap, usually a transaction cost on Byteball is less than 1000 bytes, which costs around $0.00005. You are not betting against the bot, you are betting against other people who have offered those odds. The odds difference between what is shown on [OddsChecker](https://www.oddschecker.com/) and [BB Odds](https://bb-odds.herokuapp.com/) is not because bot fees, but because these are the odds that other users have offered. Also, the whole premise of blockchain is not cutting the costs, it is to get rid of the middlemen who block you from sending the money or who could deny payout to you even if you won by having the funds in smart-contract, not in hands of middleman. If you think that these odds are horrible (which they aren't) then you could offer better odds yourself, if you were sure that 2.06 was too low odd for Atlanta Braves to lose against Boston Red Sox, you could have gone to [bet maker mode on BB Odds](https://bb-odds.herokuapp.com/maker.html) and offered the odds that you would think are fair, if you have money deposited to bot, next time anybody thinking that Atlanta Braves will win would have taken your offered bet. 3) Betting on Byteball has evolved a lot and what you are describing is the foundation of sports betting and how it can be done with the help of Sports Oracle bot and direct chat with somebody you know. The next layer on top of that was Sports Betting Bot, which takes care of the issue of finding the other counterpart and lets people just put up the odds and anybody could take them via the bot. It is exactly the exchange what you are describing, but it is even better because you don't have to pick any single offer with best odds, it will automatically compose you the smart-contract with the best odds depending on the amount you want to bet on. Third layer is the web interface of BB Odds, which makes using the bot even easier because you can see all the bets at once, you can change the odd formats and lot more, it's basically a gateway to Sports Betting bot bets without the need to navigate in the chatbot. Since you missed the difference of all those 3 things, I guess I can agree that the funnel of directing the users to right services could be better, but if you are interested to read more about the evolution of sports betting on Byteball then you can do it there https://medium.com/byteball/new-tool-makes-the-byteball-betting-bot-more-user-friendly-and-enticing-to-both-cryptocurrency-7191f14a7460 4) This one just feels like you are nitpicking on random things. Do you really think that if the chat response that is in black color and a link color that is blue doesn't make it clear that users can click it? Because that what links do on web and on chats, they are in different color than rest of the text and you can click on them. Also, open up any other chat app and you will see that there is a button(s) next to the text box where you can type and when you click on it, it offers you other stuff that you can insert into the message. Anybody familiar with any chatting app should feel home with Byteball app because it works like rest of the chatting apps. This is one of the core difference from other cryptocurrencies, which build different UI for different services, on Byteball, all apps work similar way, as chatbots. And some like Sports Betting bot even have web interfaces if chatbots are still too revolutionary for you. |
| json metadata | {"community":"busy","app":"busy/2.5.6","format":"markdown","tags":["byteball"],"users":[],"links":["https://www.oddschecker.com/","https://bb-odds.herokuapp.com/","https://bb-odds.herokuapp.com/maker.html","https://medium.com/byteball/new-tool-makes-the-byteball-betting-bot-more-user-friendly-and-enticing-to-both-cryptocurrency-7191f14a7460"],"image":[]} |
| Transaction Info | Block #25865435/Trx a406ac0285730517055716770b847b9f49e73fac |
View Raw JSON Data
{
"trx_id": "a406ac0285730517055716770b847b9f49e73fac",
"block": 25865435,
"trx_in_block": 25,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-09-11T11:44:18",
"op": [
"comment",
{
"parent_author": "wimpethomas",
"parent_permlink": "the-problems-with-byteball",
"author": "tarmo888",
"permlink": "re-wimpethomas-the-problems-with-byteball-20180911t114416850z",
"title": "",
"body": "1) Yes, this is a problem of all cryptocurrencies, but there isn't any good solution for that problem other than adding a support for some stable coin like Tether. Many exchanges do that because they don't have a bank account, which would let them can't accept real fiat money for cryptocurrencies. Maybe some wallets support multiple cryptocurrencies and some of them are stablecoins, but generally, if you need to interact with blockchain of any cryptocurrency, you need to use native currency. For some, it is because that is the only currency there is on that cryptocurrency platform and for others that is a only currency that miners only accept. For example, you can't send ERC20 tokens on Ethereum without paying the fees in ETH. The price volatility is because cryptocurrencies are still too small, there aren't enough people to get it more stable because there is always some people who could dump their coins at low price. Another reason for it could be that it is so easy to do with cryptocurrencies, but so much difficult to do with fiat money.\n\n2) Fees on Byteball are super cheap, usually a transaction cost on Byteball is less than 1000 bytes, which costs around $0.00005. You are not betting against the bot, you are betting against other people who have offered those odds. The odds difference between what is shown on [OddsChecker](https://www.oddschecker.com/) and [BB Odds](https://bb-odds.herokuapp.com/) is not because bot fees, but because these are the odds that other users have offered. Also, the whole premise of blockchain is not cutting the costs, it is to get rid of the middlemen who block you from sending the money or who could deny payout to you even if you won by having the funds in smart-contract, not in hands of middleman. If you think that these odds are horrible (which they aren't) then you could offer better odds yourself, if you were sure that 2.06 was too low odd for Atlanta Braves to lose against Boston Red Sox, you could have gone to [bet maker mode on BB Odds](https://bb-odds.herokuapp.com/maker.html) and offered the odds that you would think are fair, if you have money deposited to bot, next time anybody thinking that Atlanta Braves will win would have taken your offered bet.\n\n3) Betting on Byteball has evolved a lot and what you are describing is the foundation of sports betting and how it can be done with the help of Sports Oracle bot and direct chat with somebody you know. The next layer on top of that was Sports Betting Bot, which takes care of the issue of finding the other counterpart and lets people just put up the odds and anybody could take them via the bot. It is exactly the exchange what you are describing, but it is even better because you don't have to pick any single offer with best odds, it will automatically compose you the smart-contract with the best odds depending on the amount you want to bet on. Third layer is the web interface of BB Odds, which makes using the bot even easier because you can see all the bets at once, you can change the odd formats and lot more, it's basically a gateway to Sports Betting bot bets without the need to navigate in the chatbot. Since you missed the difference of all those 3 things, I guess I can agree that the funnel of directing the users to right services could be better, but if you are interested to read more about the evolution of sports betting on Byteball then you can do it there https://medium.com/byteball/new-tool-makes-the-byteball-betting-bot-more-user-friendly-and-enticing-to-both-cryptocurrency-7191f14a7460\n\n4) This one just feels like you are nitpicking on random things. Do you really think that if the chat response that is in black color and a link color that is blue doesn't make it clear that users can click it? Because that what links do on web and on chats, they are in different color than rest of the text and you can click on them. Also, open up any other chat app and you will see that there is a button(s) next to the text box where you can type and when you click on it, it offers you other stuff that you can insert into the message. Anybody familiar with any chatting app should feel home with Byteball app because it works like rest of the chatting apps. This is one of the core difference from other cryptocurrencies, which build different UI for different services, on Byteball, all apps work similar way, as chatbots. And some like Sports Betting bot even have web interfaces if chatbots are still too revolutionary for you.",
"json_metadata": "{\"community\":\"busy\",\"app\":\"busy/2.5.6\",\"format\":\"markdown\",\"tags\":[\"byteball\"],\"users\":[],\"links\":[\"https://www.oddschecker.com/\",\"https://bb-odds.herokuapp.com/\",\"https://bb-odds.herokuapp.com/maker.html\",\"https://medium.com/byteball/new-tool-makes-the-byteball-betting-bot-more-user-friendly-and-enticing-to-both-cryptocurrency-7191f14a7460\"],\"image\":[]}"
}
]
}nofxupvoted (100.00%) @wimpethomas / the-problems-with-byteball2018/09/11 09:32:21
nofxupvoted (100.00%) @wimpethomas / the-problems-with-byteball
2018/09/11 09:32:21
| voter | nofx |
| author | wimpethomas |
| permlink | the-problems-with-byteball |
| weight | 10000 (100.00%) |
| Transaction Info | Block #25862797/Trx 53a86e2156389fcae2a5b586377eabceb8c93322 |
View Raw JSON Data
{
"trx_id": "53a86e2156389fcae2a5b586377eabceb8c93322",
"block": 25862797,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-09-11T09:32:21",
"op": [
"vote",
{
"voter": "nofx",
"author": "wimpethomas",
"permlink": "the-problems-with-byteball",
"weight": 10000
}
]
}2018/09/10 15:16:54
2018/09/10 15:16:54
| parent author | wimpethomas |
| parent permlink | the-problems-with-byteball |
| author | steemitboard |
| permlink | steemitboard-notify-wimpethomas-20180910t151656000z |
| title | |
| body | Congratulations @wimpethomas! You have completed the following achievement on the Steem blockchain and have been rewarded with new badge(s) : [](http://steemitboard.com/@wimpethomas) You published your First Post <sub>_Click on the badge to view your Board of Honor._</sub> <sub>_If you no longer want to receive notifications, reply to this comment with the word_ `STOP`</sub> **Do not miss the last post from @steemitboard:** <table><tr><td><a href="https://steemit.com/steemitboard/@steemitboard/steemitboard-witness-update-2018-09-07"><img src="https://steemitimages.com/64x128/http://i.cubeupload.com/7CiQEO.png"></a></td><td><a href="https://steemit.com/steemitboard/@steemitboard/steemitboard-witness-update-2018-09-07">SteemitBoard - Witness Update</a></td></tr><tr><td><a href="https://steemit.com/steemfest/@steemitboard/steemfest-steemitboard-support-the-travel-reimbursement-fund"><img src="https://steemitimages.com/64x128/https://cdn.steemitimages.com/DQmawPYDAwfrQM8YU6ejD1f87g64cvsmEFn8RQKHJMs4zxg/image.png"></a></td><td><a href="https://steemit.com/steemfest/@steemitboard/steemfest-steemitboard-support-the-travel-reimbursement-fund">SteemFest³ - SteemitBoard support the Travel Reimbursement Fund.</a></td></tr></table> > 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"]} |
| Transaction Info | Block #25840898/Trx cd6de14285bb7454fb39ff515a9a7198c2d8dcfc |
View Raw JSON Data
{
"trx_id": "cd6de14285bb7454fb39ff515a9a7198c2d8dcfc",
"block": 25840898,
"trx_in_block": 40,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-09-10T15:16:54",
"op": [
"comment",
{
"parent_author": "wimpethomas",
"parent_permlink": "the-problems-with-byteball",
"author": "steemitboard",
"permlink": "steemitboard-notify-wimpethomas-20180910t151656000z",
"title": "",
"body": "Congratulations @wimpethomas! You have completed the following achievement on the Steem blockchain and have been rewarded with new badge(s) :\n\n[](http://steemitboard.com/@wimpethomas) You published your First Post\n\n<sub>_Click on the badge to view your Board of Honor._</sub>\n<sub>_If you no longer want to receive notifications, reply to this comment with the word_ `STOP`</sub>\n\n\n\n**Do not miss the last post from @steemitboard:**\n<table><tr><td><a href=\"https://steemit.com/steemitboard/@steemitboard/steemitboard-witness-update-2018-09-07\"><img src=\"https://steemitimages.com/64x128/http://i.cubeupload.com/7CiQEO.png\"></a></td><td><a href=\"https://steemit.com/steemitboard/@steemitboard/steemitboard-witness-update-2018-09-07\">SteemitBoard - Witness Update</a></td></tr><tr><td><a href=\"https://steemit.com/steemfest/@steemitboard/steemfest-steemitboard-support-the-travel-reimbursement-fund\"><img src=\"https://steemitimages.com/64x128/https://cdn.steemitimages.com/DQmawPYDAwfrQM8YU6ejD1f87g64cvsmEFn8RQKHJMs4zxg/image.png\"></a></td><td><a href=\"https://steemit.com/steemfest/@steemitboard/steemfest-steemitboard-support-the-travel-reimbursement-fund\">SteemFest³ - SteemitBoard support the Travel Reimbursement Fund.</a></td></tr></table>\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\"]}"
}
]
}2018/09/10 13:16:39
2018/09/10 13:16:39
| parent author | ctrl-alt-nwo |
| parent permlink | byteball-reasons-why-it-s-a-good-crypto-and-why-steemians-should-hang-on-to-their-free-bytes |
| author | wimpethomas |
| permlink | re-ctrl-alt-nwo-byteball-reasons-why-it-s-a-good-crypto-and-why-steemians-should-hang-on-to-their-free-bytes-20180910t131637207z |
| title | |
| body | Good article, but I wrote a 'counter' article. I like Byteball, but I think it has some essential flaws, see https://steemit.com/byteball/@wimpethomas/the-problems-with-byteball. Let me know what you think about it. |
| json metadata | {"tags":["byteball"],"links":["https://steemit.com/byteball/@wimpethomas/the-problems-with-byteball"],"app":"steemit/0.1"} |
| Transaction Info | Block #25838494/Trx 985b2601d63facd7f49308df87c7f1cc9bcf63d6 |
View Raw JSON Data
{
"trx_id": "985b2601d63facd7f49308df87c7f1cc9bcf63d6",
"block": 25838494,
"trx_in_block": 12,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-09-10T13:16:39",
"op": [
"comment",
{
"parent_author": "ctrl-alt-nwo",
"parent_permlink": "byteball-reasons-why-it-s-a-good-crypto-and-why-steemians-should-hang-on-to-their-free-bytes",
"author": "wimpethomas",
"permlink": "re-ctrl-alt-nwo-byteball-reasons-why-it-s-a-good-crypto-and-why-steemians-should-hang-on-to-their-free-bytes-20180910t131637207z",
"title": "",
"body": "Good article, but I wrote a 'counter' article. I like Byteball, but I think it has some essential flaws, see https://steemit.com/byteball/@wimpethomas/the-problems-with-byteball. Let me know what you think about it.",
"json_metadata": "{\"tags\":[\"byteball\"],\"links\":[\"https://steemit.com/byteball/@wimpethomas/the-problems-with-byteball\"],\"app\":\"steemit/0.1\"}"
}
]
}steeming-hotupvoted (3.00%) @wimpethomas / the-problems-with-byteball2018/09/10 11:52:18
steeming-hotupvoted (3.00%) @wimpethomas / the-problems-with-byteball
2018/09/10 11:52:18
| voter | steeming-hot |
| author | wimpethomas |
| permlink | the-problems-with-byteball |
| weight | 300 (3.00%) |
| Transaction Info | Block #25836807/Trx c592aa785db69629008d593a86131d67ded02efa |
View Raw JSON Data
{
"trx_id": "c592aa785db69629008d593a86131d67ded02efa",
"block": 25836807,
"trx_in_block": 25,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-09-10T11:52:18",
"op": [
"vote",
{
"voter": "steeming-hot",
"author": "wimpethomas",
"permlink": "the-problems-with-byteball",
"weight": 300
}
]
}fastresteemupvoted (1.00%) @wimpethomas / the-problems-with-byteball2018/09/10 11:51:06
fastresteemupvoted (1.00%) @wimpethomas / the-problems-with-byteball
2018/09/10 11:51:06
| voter | fastresteem |
| author | wimpethomas |
| permlink | the-problems-with-byteball |
| weight | 100 (1.00%) |
| Transaction Info | Block #25836783/Trx 5cda3d3c0227f87af28a9bc7080deac0470c7349 |
View Raw JSON Data
{
"trx_id": "5cda3d3c0227f87af28a9bc7080deac0470c7349",
"block": 25836783,
"trx_in_block": 18,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-09-10T11:51:06",
"op": [
"vote",
{
"voter": "fastresteem",
"author": "wimpethomas",
"permlink": "the-problems-with-byteball",
"weight": 100
}
]
}wimpethomaspublished a new post: the-problems-with-byteball2018/09/10 11:50:54
wimpethomaspublished a new post: the-problems-with-byteball
2018/09/10 11:50:54
| parent author | |
| parent permlink | byteball |
| author | wimpethomas |
| permlink | the-problems-with-byteball |
| title | The problems with Byteball |
| body | Let me begin to say that I really want to like Byteball. I like crypto tokens that are used in a working product that have - more or less - 'usefull' features and solve real problems. And I do agree with most of the points @ctrl-alt-nwo points out in the article https://steemit.com/byteball/@ctrl-alt-nwo/byteball-reasons-why-it-s-a-good-crypto-and-why-steemians-should-hang-on-to-their-free-bytes. But I think the product has some big hurdles to overcome before a significant amount of people will start to use it. The main problems Byteball are facing are in my view: 1) People want to use fiat for crypto services. I know, this is a general problem for cryptocurrencies and also true for Byteball. Easily send or receive money (via text message or 'the regular way'), betting on sport events or insure yourself against flight delays, these are usefull things, but a lot less usefull if you have to use GBYTEs instead of your local currency. And I know that's just psychological, but it is the way 99% of the people see it right now. Dollars and euros are a store of value and unit of accounting, maybe even BTC, but GBYTEs are certainly not. And that is why I don't understand the following is the number one priority for all crypto products right now. Let people use the existing services by paying in their local fiat, let them pay an extra fee for converting to the utility token in question and use the service. So suppose a user can buy a flight delay insurance and can pay in euros. He doesn't have to worry about the GBYTE/EUR price fluctuation and he knows exactly how much he pays for the insurance and what he will receive (in euros) in case of a flight delay. It will mean that the GBYTE token has little value because the demand is limited, but that's only in the beginning. Eventually more and more people will use Byteball and gradually people will see benefit in keeping some GBYTES in their wallet (lower fees) and the price of GBYTES will rise. Most important, it will drive the most important thing for any product or service: user adoption. 2) The features that Byteball offers should be cheaper / more efficient than similar existing products. The current features are neither, although I think the flight delay insurance service is the best shot so far (by the way I think insurances in general is a great use case for decentralized crypto products). Consider the sports betting service. When you bet against the bot the offered quotes are worse than the quotes on any commercial online betting site. So what is the use of the service? The whole premise of blockchain technology is that you can cut the middlemen and thereby reduce costs and be cheaper. So why are these Byteball quotes so terrible?  3) Some feautures are extremely hard to use. For example the peer to peer sports betting. I like the idea in general and was curious to try it out. What I had in mind was a sort of a peer to peer betting exchange where you can offer and accept bets. So you can see per match what bets other people are offering. You can then accept the best offer or you can place a better offer. Something like that. I was wrong and the execution of the p2p betting function is devious. First you have to connect with your peer via the chat feature in a Whatsapp like way (invite and accept). Byteball calls this adding a device. After adding your peer you start a chat and ask your peer to send his wallet adress. You can then click on the adress and make and offer a contract. When making the contract you have to know some things beforhand, which makes the process even more cumbersome. You need to know the feed name and in order to know the feed name you have to search through the sports betting bot first. You also need to have an agreement with your peer about the amount of GBYTES both of you want to bet on, otherwise there is no sense in offering the contract. Finally, when you made it till this stage and you made the bet with your peer, it's also unclear how to collect your GBYTEs when you win the bet. If you are familiar with how smart contracts work you know that a smart contract has it's own wallet and it makes sense that you have to transfer your gains from that wallet to your own wallet. Regular users won't understand this and wonder how they will get their GBYTEs. 4) The user interface is challenging to put it mildly. Let's again take the peer to peer sport betting as example. Below some screenshots about the chat with your peer before starting the bet. Is it for a new user clear that he can insert his wallet adress via the three dots in the left bottom corner? And what about when you receive a wallet adress, how clear is it that you can click the adress to get to the popup and offer a contract?  And then the fun really begins with drawing up the contract! See the next screenshots. The upper part is relatively straightforward to understand, although the way things are formulated are far from dummy proof. But it basically asks for your and your peer's bet deposit and that you can get your deposit back if the peer doesn't make his deposit. The lower part is completely incomprehensable for first time users. What is an oracle, what is a feed name, what is meant by expected value, etc? I understand that this is the general format for any smart contract on the platform, but using these generic terms makes it almost unusable for general users. An existing contract looks like the following contract. Can any non technical user understand what the contract says? Really terrible right?  I know what you might think. The product is in development and these are relatively easy things to improve. That may be but why deliver a product that is practibly unusable for a regular user. What is the point? The developers only scare away the sparse users that actually want to try to use the product. Anyway, I gave up and dropped out. |
| json metadata | {"tags":["byteball","cryptocurrency","blockchain"],"users":["ctrl-alt-nwo"],"image":["https://cdn.steemitimages.com/DQmQWCWmAtD9R5aiAheBg5KmfxPiC5kdWQNGmgDZ6VSKe3E/Betting-compared.jpg","https://cdn.steemitimages.com/DQmS4RVY8ESiqpg6WcAsHRvqpbfeh1MZ5wRz5Fjj3gM1yx3/Chat.jpg","https://cdn.steemitimages.com/DQmZj1os3tQCu1wNUUnz3V9FfgRyaVDyowor6gBqKkB5wyu/Contract.jpg"],"links":["https://steemit.com/byteball/@ctrl-alt-nwo/byteball-reasons-why-it-s-a-good-crypto-and-why-steemians-should-hang-on-to-their-free-bytes"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #25836779/Trx e01ba32e01bf914e557ce42f1c85961ee469ba27 |
View Raw JSON Data
{
"trx_id": "e01ba32e01bf914e557ce42f1c85961ee469ba27",
"block": 25836779,
"trx_in_block": 31,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-09-10T11:50:54",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "byteball",
"author": "wimpethomas",
"permlink": "the-problems-with-byteball",
"title": "The problems with Byteball",
"body": "Let me begin to say that I really want to like Byteball. I like crypto tokens that are used in a working product that have - more or less - 'usefull' features and solve real problems. And I do agree with most of the points @ctrl-alt-nwo points out in the article https://steemit.com/byteball/@ctrl-alt-nwo/byteball-reasons-why-it-s-a-good-crypto-and-why-steemians-should-hang-on-to-their-free-bytes. But I think the product has some big hurdles to overcome before a significant amount of people will start to use it. The main problems Byteball are facing are in my view:\n\n1) People want to use fiat for crypto services. I know, this is a general problem for cryptocurrencies and also true for Byteball. Easily send or receive money (via text message or 'the regular way'), betting on sport events or insure yourself against flight delays, these are usefull things, but a lot less usefull if you have to use GBYTEs instead of your local currency. And I know that's just psychological, but it is the way 99% of the people see it right now. Dollars and euros are a store of value and unit of accounting, maybe even BTC, but GBYTEs are certainly not.\nAnd that is why I don't understand the following is the number one priority for all crypto products right now. Let people use the existing services by paying in their local fiat, let them pay an extra fee for converting to the utility token in question and use the service. So suppose a user can buy a flight delay insurance and can pay in euros. He doesn't have to worry about the GBYTE/EUR price fluctuation and he knows exactly how much he pays for the insurance and what he will receive (in euros) in case of a flight delay. It will mean that the GBYTE token has little value because the demand is limited, but that's only in the beginning. Eventually more and more people will use Byteball and gradually people will see benefit in keeping some GBYTES in their wallet (lower fees) and the price of GBYTES will rise. Most important, it will drive the most important thing for any product or service: user adoption.\n\n2) The features that Byteball offers should be cheaper / more efficient than similar existing products. The current features are neither, although I think the flight delay insurance service is the best shot so far (by the way I think insurances in general is a great use case for decentralized crypto products). Consider the sports betting service. When you bet against the bot the offered quotes are worse than the quotes on any commercial online betting site. So what is the use of the service? The whole premise of blockchain technology is that you can cut the middlemen and thereby reduce costs and be cheaper. So why are these Byteball quotes so terrible?\n\n\n3) Some feautures are extremely hard to use. For example the peer to peer sports betting. I like the idea in general and was curious to try it out. What I had in mind was a sort of a peer to peer betting exchange where you can offer and accept bets. So you can see per match what bets other people are offering. You can then accept the best offer or you can place a better offer. Something like that. I was wrong and the execution of the p2p betting function is devious. First you have to connect with your peer via the chat feature in a Whatsapp like way (invite and accept). Byteball calls this adding a device. After adding your peer you start a chat and ask your peer to send his wallet adress. You can then click on the adress and make and offer a contract. When making the contract you have to know some things beforhand, which makes the process even more cumbersome. You need to know the feed name and in order to know the feed name you have to search through the sports betting bot first. You also need to have an agreement with your peer about the amount of GBYTES both of you want to bet on, otherwise there is no sense in offering the contract. Finally, when you made it till this stage and you made the bet with your peer, it's also unclear how to collect your GBYTEs when you win the bet. If you are familiar with how smart contracts work you know that a smart contract has it's own wallet and it makes sense that you have to transfer your gains from that wallet to your own wallet. Regular users won't understand this and wonder how they will get their GBYTEs.\n\n4) The user interface is challenging to put it mildly. Let's again take the peer to peer sport betting as example. Below some screenshots about the chat with your peer before starting the bet. Is it for a new user clear that he can insert his wallet adress via the three dots in the left bottom corner? And what about when you receive a wallet adress, how clear is it that you can click the adress to get to the popup and offer a contract?  \nAnd then the fun really begins with drawing up the contract! See the next screenshots. The upper part is relatively straightforward to understand, although the way things are formulated are far from dummy proof. But it basically asks for your and your peer's bet deposit and that you can get your deposit back if the peer doesn't make his deposit. The lower part is completely incomprehensable for first time users. What is an oracle, what is a feed name, what is meant by expected value, etc? I understand that this is the general format for any smart contract on the platform, but using these generic terms makes it almost unusable for general users. An existing contract looks like the following contract. Can any non technical user understand what the contract says? Really terrible right? \n\nI know what you might think. The product is in development and these are relatively easy things to improve. That may be but why deliver a product that is practibly unusable for a regular user. What is the point? The developers only scare away the sparse users that actually want to try to use the product. Anyway, I gave up and dropped out.",
"json_metadata": "{\"tags\":[\"byteball\",\"cryptocurrency\",\"blockchain\"],\"users\":[\"ctrl-alt-nwo\"],\"image\":[\"https://cdn.steemitimages.com/DQmQWCWmAtD9R5aiAheBg5KmfxPiC5kdWQNGmgDZ6VSKe3E/Betting-compared.jpg\",\"https://cdn.steemitimages.com/DQmS4RVY8ESiqpg6WcAsHRvqpbfeh1MZ5wRz5Fjj3gM1yx3/Chat.jpg\",\"https://cdn.steemitimages.com/DQmZj1os3tQCu1wNUUnz3V9FfgRyaVDyowor6gBqKkB5wyu/Contract.jpg\"],\"links\":[\"https://steemit.com/byteball/@ctrl-alt-nwo/byteball-reasons-why-it-s-a-good-crypto-and-why-steemians-should-hang-on-to-their-free-bytes\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}wimpethomasfollowed @cryptoindex2018/09/03 21:26:30
wimpethomasfollowed @cryptoindex
2018/09/03 21:26:30
| required auths | [] |
| required posting auths | ["wimpethomas"] |
| id | follow |
| json | ["follow",{"follower":"wimpethomas","following":"cryptoindex","what":["blog"]}] |
| Transaction Info | Block #25646760/Trx b014e2f382d0fac2fe13d3f0a7795de0d0e5ac28 |
View Raw JSON Data
{
"trx_id": "b014e2f382d0fac2fe13d3f0a7795de0d0e5ac28",
"block": 25646760,
"trx_in_block": 16,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-09-03T21:26:30",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"wimpethomas"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"wimpethomas\",\"following\":\"cryptoindex\",\"what\":[\"blog\"]}]"
}
]
}wimpethomassent 0.001 STEEM to @phenom- "X2nXbWURkYuBlP0"2018/09/03 21:24:15
wimpethomassent 0.001 STEEM to @phenom- "X2nXbWURkYuBlP0"
2018/09/03 21:24:15
| from | wimpethomas |
| to | phenom |
| amount | 0.001 STEEM |
| memo | X2nXbWURkYuBlP0 |
| Transaction Info | Block #25646715/Trx 0bff1ea1212591b1dfba0c42efc0cec671f2fa25 |
View Raw JSON Data
{
"trx_id": "0bff1ea1212591b1dfba0c42efc0cec671f2fa25",
"block": 25646715,
"trx_in_block": 12,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-09-03T21:24:15",
"op": [
"transfer",
{
"from": "wimpethomas",
"to": "phenom",
"amount": "0.001 STEEM",
"memo": "X2nXbWURkYuBlP0"
}
]
}2018/09/03 10:52:30
2018/09/03 10:52:30
| voter | wimpethomas |
| author | ctrl-alt-nwo |
| permlink | byteball-reasons-why-it-s-a-good-crypto-and-why-steemians-should-hang-on-to-their-free-bytes |
| weight | 10000 (100.00%) |
| Transaction Info | Block #25634091/Trx 2d948cc25ef4a3576f435aa33a091fe7fbb2f3c6 |
View Raw JSON Data
{
"trx_id": "2d948cc25ef4a3576f435aa33a091fe7fbb2f3c6",
"block": 25634091,
"trx_in_block": 19,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-09-03T10:52:30",
"op": [
"vote",
{
"voter": "wimpethomas",
"author": "ctrl-alt-nwo",
"permlink": "byteball-reasons-why-it-s-a-good-crypto-and-why-steemians-should-hang-on-to-their-free-bytes",
"weight": 10000
}
]
}wimpethomasfollowed @ctrl-alt-nwo2018/09/03 10:52:27
wimpethomasfollowed @ctrl-alt-nwo
2018/09/03 10:52:27
| required auths | [] |
| required posting auths | ["wimpethomas"] |
| id | follow |
| json | ["follow",{"follower":"wimpethomas","following":"ctrl-alt-nwo","what":["blog"]}] |
| Transaction Info | Block #25634090/Trx a7a67da19c9e3c7405376a42f263a392db1e7193 |
View Raw JSON Data
{
"trx_id": "a7a67da19c9e3c7405376a42f263a392db1e7193",
"block": 25634090,
"trx_in_block": 35,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-09-03T10:52:27",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"wimpethomas"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"wimpethomas\",\"following\":\"ctrl-alt-nwo\",\"what\":[\"blog\"]}]"
}
]
}wimpethomasclaimed reward balance: 0.019 STEEM, 0.024 SP2018/09/03 10:02:33
wimpethomasclaimed reward balance: 0.019 STEEM, 0.024 SP
2018/09/03 10:02:33
| account | wimpethomas |
| reward steem | 0.019 STEEM |
| reward sbd | 0.000 SBD |
| reward vests | 38.443408 VESTS |
| Transaction Info | Block #25633094/Trx bda6cc2b359cd0f3ac6bbb9dde89f68f6ebe891e |
View Raw JSON Data
{
"trx_id": "bda6cc2b359cd0f3ac6bbb9dde89f68f6ebe891e",
"block": 25633094,
"trx_in_block": 8,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-09-03T10:02:33",
"op": [
"claim_reward_balance",
{
"account": "wimpethomas",
"reward_steem": "0.019 STEEM",
"reward_sbd": "0.000 SBD",
"reward_vests": "38.443408 VESTS"
}
]
}wimpethomasupvoted (100.00%) @ekeneobi / elastos2018/09/03 10:02:06
wimpethomasupvoted (100.00%) @ekeneobi / elastos
2018/09/03 10:02:06
| voter | wimpethomas |
| author | ekeneobi |
| permlink | elastos |
| weight | 10000 (100.00%) |
| Transaction Info | Block #25633085/Trx 489c3834606659c77671f77eaabef65e43c14fcd |
View Raw JSON Data
{
"trx_id": "489c3834606659c77671f77eaabef65e43c14fcd",
"block": 25633085,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-09-03T10:02:06",
"op": [
"vote",
{
"voter": "wimpethomas",
"author": "ekeneobi",
"permlink": "elastos",
"weight": 10000
}
]
}wimpethomasfollowed @ekeneobi2018/09/03 10:01:51
wimpethomasfollowed @ekeneobi
2018/09/03 10:01:51
| required auths | [] |
| required posting auths | ["wimpethomas"] |
| id | follow |
| json | ["follow",{"follower":"wimpethomas","following":"ekeneobi","what":["blog"]}] |
| Transaction Info | Block #25633080/Trx d550dd60c1a6d0c1847f30b3954a8d4dc327eea2 |
View Raw JSON Data
{
"trx_id": "d550dd60c1a6d0c1847f30b3954a8d4dc327eea2",
"block": 25633080,
"trx_in_block": 12,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-09-03T10:01:51",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"wimpethomas"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"wimpethomas\",\"following\":\"ekeneobi\",\"what\":[\"blog\"]}]"
}
]
}wimpethomasreceived 0.019 STEEM, 0.024 SP author reward for @wimpethomas / re-brothermic-claim-free-steem-now-5-160usd-byteball-airdrop-20180825t111449235z2018/09/01 11:14:51
wimpethomasreceived 0.019 STEEM, 0.024 SP author reward for @wimpethomas / re-brothermic-claim-free-steem-now-5-160usd-byteball-airdrop-20180825t111449235z
2018/09/01 11:14:51
| author | wimpethomas |
| permlink | re-brothermic-claim-free-steem-now-5-160usd-byteball-airdrop-20180825t111449235z |
| sbd payout | 0.000 SBD |
| steem payout | 0.019 STEEM |
| vesting payout | 38.443408 VESTS |
| Transaction Info | Block #25576991/Virtual Operation #3 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 25576991,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 3,
"timestamp": "2018-09-01T11:14:51",
"op": [
"author_reward",
{
"author": "wimpethomas",
"permlink": "re-brothermic-claim-free-steem-now-5-160usd-byteball-airdrop-20180825t111449235z",
"sbd_payout": "0.000 SBD",
"steem_payout": "0.019 STEEM",
"vesting_payout": "38.443408 VESTS"
}
]
}2018/08/25 13:50:00
2018/08/25 13:50:00
| voter | brothermic |
| author | wimpethomas |
| permlink | re-brothermic-claim-free-steem-now-5-160usd-byteball-airdrop-20180825t111449235z |
| weight | 3100 (31.00%) |
| Transaction Info | Block #25378583/Trx 0e29082c672636872ac1a89f7ad769d3bc9e3835 |
View Raw JSON Data
{
"trx_id": "0e29082c672636872ac1a89f7ad769d3bc9e3835",
"block": 25378583,
"trx_in_block": 15,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-08-25T13:50:00",
"op": [
"vote",
{
"voter": "brothermic",
"author": "wimpethomas",
"permlink": "re-brothermic-claim-free-steem-now-5-160usd-byteball-airdrop-20180825t111449235z",
"weight": 3100
}
]
}wimpethomasupvoted (100.00%) @coinmarketcal / elastos-ela-27-august-2018-or-earlier-alpha-release2018/08/25 11:20:42
wimpethomasupvoted (100.00%) @coinmarketcal / elastos-ela-27-august-2018-or-earlier-alpha-release
2018/08/25 11:20:42
| voter | wimpethomas |
| author | coinmarketcal |
| permlink | elastos-ela-27-august-2018-or-earlier-alpha-release |
| weight | 10000 (100.00%) |
| Transaction Info | Block #25375597/Trx f9042d6d8c6114ae0c74e6b490395663a1e270b0 |
View Raw JSON Data
{
"trx_id": "f9042d6d8c6114ae0c74e6b490395663a1e270b0",
"block": 25375597,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-08-25T11:20:42",
"op": [
"vote",
{
"voter": "wimpethomas",
"author": "coinmarketcal",
"permlink": "elastos-ela-27-august-2018-or-earlier-alpha-release",
"weight": 10000
}
]
}wimpethomasupvoted (100.00%) @brothermic / claim-free-steem-now-5-160usd-byteball-airdrop2018/08/25 11:15:06
wimpethomasupvoted (100.00%) @brothermic / claim-free-steem-now-5-160usd-byteball-airdrop
2018/08/25 11:15:06
| voter | wimpethomas |
| author | brothermic |
| permlink | claim-free-steem-now-5-160usd-byteball-airdrop |
| weight | 10000 (100.00%) |
| Transaction Info | Block #25375485/Trx 10d2ac06810fd7b0876921b9d7873ecc32ab3e18 |
View Raw JSON Data
{
"trx_id": "10d2ac06810fd7b0876921b9d7873ecc32ab3e18",
"block": 25375485,
"trx_in_block": 32,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-08-25T11:15:06",
"op": [
"vote",
{
"voter": "wimpethomas",
"author": "brothermic",
"permlink": "claim-free-steem-now-5-160usd-byteball-airdrop",
"weight": 10000
}
]
}2018/08/25 11:14:51
2018/08/25 11:14:51
| parent author | brothermic |
| parent permlink | claim-free-steem-now-5-160usd-byteball-airdrop |
| author | wimpethomas |
| permlink | re-brothermic-claim-free-steem-now-5-160usd-byteball-airdrop-20180825t111449235z |
| title | |
| body | resteemed |
| json metadata | {"tags":["byteball"],"app":"steemit/0.1"} |
| Transaction Info | Block #25375480/Trx 64ec97d959edbbb513f28ec96b8de199268a3770 |
View Raw JSON Data
{
"trx_id": "64ec97d959edbbb513f28ec96b8de199268a3770",
"block": 25375480,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-08-25T11:14:51",
"op": [
"comment",
{
"parent_author": "brothermic",
"parent_permlink": "claim-free-steem-now-5-160usd-byteball-airdrop",
"author": "wimpethomas",
"permlink": "re-brothermic-claim-free-steem-now-5-160usd-byteball-airdrop-20180825t111449235z",
"title": "",
"body": "resteemed",
"json_metadata": "{\"tags\":[\"byteball\"],\"app\":\"steemit/0.1\"}"
}
]
}wimpethomascustom json: follow2018/08/25 11:14:09
wimpethomascustom json: follow
2018/08/25 11:14:09
| required auths | [] |
| required posting auths | ["wimpethomas"] |
| id | follow |
| json | ["reblog",{"account":"wimpethomas","author":"brothermic","permlink":"claim-free-steem-now-5-160usd-byteball-airdrop"}] |
| Transaction Info | Block #25375466/Trx 202fbbde69aad36d9714a0ffe6675c92d3b43ecc |
View Raw JSON Data
{
"trx_id": "202fbbde69aad36d9714a0ffe6675c92d3b43ecc",
"block": 25375466,
"trx_in_block": 10,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-08-25T11:14:09",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"wimpethomas"
],
"id": "follow",
"json": "[\"reblog\",{\"account\":\"wimpethomas\",\"author\":\"brothermic\",\"permlink\":\"claim-free-steem-now-5-160usd-byteball-airdrop\"}]"
}
]
}steemdelegated 18.532 SP to @wimpethomas2018/08/14 17:40:12
steemdelegated 18.532 SP to @wimpethomas
2018/08/14 17:40:12
| delegator | steem |
| delegatee | wimpethomas |
| vesting shares | 30176.326691 VESTS |
| Transaction Info | Block #25066521/Trx c482ec9f6050b69206be7ea2e5cfea97a30bdc08 |
View Raw JSON Data
{
"trx_id": "c482ec9f6050b69206be7ea2e5cfea97a30bdc08",
"block": 25066521,
"trx_in_block": 39,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-08-14T17:40:12",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "wimpethomas",
"vesting_shares": "30176.326691 VESTS"
}
]
}steemcreated a new account: @wimpethomas2018/08/14 17:07:12
steemcreated a new account: @wimpethomas
2018/08/14 17:07:12
| fee | 0.100 STEEM |
| delegation | 30690.000000 VESTS |
| creator | steem |
| new account name | wimpethomas |
| owner | {"weight_threshold":1,"account_auths":[],"key_auths":[["STM6TtLp1dTCKPZF4KeSMNTpfyBiv1mKV9XnKc4wGGsaUyzqyW45S",1]]} |
| active | {"weight_threshold":1,"account_auths":[],"key_auths":[["STM5zpAQNCeAPzCxPdWzcUhDWG6DvUMurjqBBVegHjRPBd4nPUZKG",1]]} |
| posting | {"weight_threshold":1,"account_auths":[],"key_auths":[["STM558Y9pcVPWtfs2xX2gwLv2yfsYfXAVZNXJDtQSJkJnJBM9BaBa",1]]} |
| memo key | STM5uthwSYggRTA8j3HDDwDA8v24U6qfTHuDdD3FN7y2MZ78QPuQg |
| json metadata | {} |
| extensions | [] |
| Transaction Info | Block #25065861/Trx 2c229bd0425e0b21c591cd6cb71d24eb573892e5 |
View Raw JSON Data
{
"trx_id": "2c229bd0425e0b21c591cd6cb71d24eb573892e5",
"block": 25065861,
"trx_in_block": 22,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-08-14T17:07:12",
"op": [
"account_create_with_delegation",
{
"fee": "0.100 STEEM",
"delegation": "30690.000000 VESTS",
"creator": "steem",
"new_account_name": "wimpethomas",
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM6TtLp1dTCKPZF4KeSMNTpfyBiv1mKV9XnKc4wGGsaUyzqyW45S",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5zpAQNCeAPzCxPdWzcUhDWG6DvUMurjqBBVegHjRPBd4nPUZKG",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM558Y9pcVPWtfs2xX2gwLv2yfsYfXAVZNXJDtQSJkJnJBM9BaBa",
1
]
]
},
"memo_key": "STM5uthwSYggRTA8j3HDDwDA8v24U6qfTHuDdD3FN7y2MZ78QPuQg",
"json_metadata": "{}",
"extensions": []
}
]
}Manabar
Voting Power100.00%
Downvote Power100.00%
Resource Credits100.00%
Reputation Progress0.00%
{
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779092061
},
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779092061
},
"rc_account": {
"account": "wimpethomas",
"rc_manabar": {
"current_mana": "10164408779",
"last_update_time": 1779092061
},
"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
STM6TtLp1dTCKPZF4KeSMNTpfyBiv1mKV9XnKc4wGGsaUyzqyW45S1/1
Active
Single Signature
Public Keys
STM5zpAQNCeAPzCxPdWzcUhDWG6DvUMurjqBBVegHjRPBd4nPUZKG1/1
Posting
Single Signature
Public Keys
STM558Y9pcVPWtfs2xX2gwLv2yfsYfXAVZNXJDtQSJkJnJBM9BaBa1/1
Memo
STM5uthwSYggRTA8j3HDDwDA8v24U6qfTHuDdD3FN7y2MZ78QPuQg
{
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM6TtLp1dTCKPZF4KeSMNTpfyBiv1mKV9XnKc4wGGsaUyzqyW45S",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5zpAQNCeAPzCxPdWzcUhDWG6DvUMurjqBBVegHjRPBd4nPUZKG",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM558Y9pcVPWtfs2xX2gwLv2yfsYfXAVZNXJDtQSJkJnJBM9BaBa",
1
]
]
},
"memo": "STM5uthwSYggRTA8j3HDDwDA8v24U6qfTHuDdD3FN7y2MZ78QPuQg"
}Witness Votes
0 / 30
No active witness votes.
[]