VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS0.55%
Net Worth
0.755USD
STEEM
4.742STEEM
SBD
0.814SBD
Effective Power
5.007SP
├── Own SP
1.533SP
└── Incoming DelegationsDeleg
+3.475SP
Detailed Balance
| STEEM | ||
| balance | 4.742STEEM | STEEM |
| market_balance | 0.000STEEM | STEEM |
| savings_balance | 0.000STEEM | STEEM |
| reward_steem_balance | 0.000STEEM | STEEM |
| STEEM POWER | ||
| Own SP | 1.533SP | SP |
| Delegated Out | 0.000SP | SP |
| Delegation In | 3.475SP | SP |
| Effective Power | 5.007SP | SP |
| Reward SP (pending) | 0.000SP | SP |
| SBD | ||
| sbd_balance | 0.814SBD | 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": "4.742 STEEM",
"savings_balance": "0.000 STEEM",
"reward_steem_balance": "0.000 STEEM",
"vesting_shares": "2492.601692 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "5651.058114 VESTS",
"sbd_balance": "0.814 SBD",
"savings_sbd_balance": "0.000 SBD",
"reward_sbd_balance": "0.000 SBD",
"conversions": []
}Account Info
| name | cryptotrader-ug |
| id | 415247 |
| rank | 847,983 |
| reputation | 12933783889 |
| created | 2017-10-20T15:15:45 |
| recovery_account | steem |
| proxy | None |
| post_count | 4 |
| comment_count | 0 |
| lifetime_vote_count | 0 |
| witnesses_voted_for | 0 |
| last_post | 2017-11-11T23:48:24 |
| last_root_post | 2017-11-11T23:48:24 |
| last_vote_time | 2017-11-17T20:59:36 |
| proxied_vsf_votes | 0, 0, 0, 0 |
| can_vote | 1 |
| voting_power | 0 |
| delayed_votes | 0 |
| balance | 4.742 STEEM |
| savings_balance | 0.000 STEEM |
| sbd_balance | 0.814 SBD |
| savings_sbd_balance | 0.000 SBD |
| vesting_shares | 2492.601692 VESTS |
| delegated_vesting_shares | 0.000000 VESTS |
| received_vesting_shares | 5651.058114 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 | 2018-05-24T07:12:39 |
| savings_sbd_last_interest_payment | 1970-01-01T00:00:00 |
{
"active": {
"account_auths": [],
"key_auths": [
[
"STM5oqSSkWCDsHTb1xjHxkd41axm6vJ2u62UVcoFvdECaZnyoZQb8",
1
]
],
"weight_threshold": 1
},
"balance": "4.742 STEEM",
"can_vote": true,
"comment_count": 0,
"created": "2017-10-20T15:15:45",
"curation_rewards": 2,
"delegated_vesting_shares": "0.000000 VESTS",
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779058995
},
"guest_bloggers": [],
"id": 415247,
"json_metadata": "",
"last_account_recovery": "1970-01-01T00:00:00",
"last_account_update": "1970-01-01T00:00:00",
"last_owner_update": "1970-01-01T00:00:00",
"last_post": "2017-11-11T23:48:24",
"last_root_post": "2017-11-11T23:48:24",
"last_vote_time": "2017-11-17T20:59:36",
"lifetime_vote_count": 0,
"market_history": [],
"memo_key": "STM5xMHYHjHJyc2d2ViXjZnXaCSWqu6zLTRkYcgtx4dnYozy6MVED",
"mined": false,
"name": "cryptotrader-ug",
"next_vesting_withdrawal": "1969-12-31T23:59:59",
"other_history": [],
"owner": {
"account_auths": [],
"key_auths": [
[
"STM7FBmTQuwEweCcJDX2ZAhgNeCzzPXoyF5wJHEcxtpSy5HFtUwo3",
1
]
],
"weight_threshold": 1
},
"pending_claimed_accounts": 0,
"post_bandwidth": 0,
"post_count": 4,
"post_history": [],
"posting": {
"account_auths": [],
"key_auths": [
[
"STM7W9cv1PxqcoZyN1GUMgi4rzZwnDx4UYvk2d9U2b3rcGUu23w5u",
1
]
],
"weight_threshold": 1
},
"posting_json_metadata": "",
"posting_rewards": 1422,
"proxied_vsf_votes": [
0,
0,
0,
0
],
"proxy": "",
"received_vesting_shares": "5651.058114 VESTS",
"recovery_account": "steem",
"reputation": "12933783889",
"reset_account": "null",
"reward_sbd_balance": "0.000 SBD",
"reward_steem_balance": "0.000 STEEM",
"reward_vesting_balance": "0.000000 VESTS",
"reward_vesting_steem": "0.000 STEEM",
"savings_balance": "0.000 STEEM",
"savings_sbd_balance": "0.000 SBD",
"savings_sbd_last_interest_payment": "1970-01-01T00:00:00",
"savings_sbd_seconds": "0",
"savings_sbd_seconds_last_update": "1970-01-01T00:00:00",
"savings_withdraw_requests": 0,
"sbd_balance": "0.814 SBD",
"sbd_last_interest_payment": "2018-05-24T07:12:39",
"sbd_seconds": "0",
"sbd_seconds_last_update": "2018-05-24T07:12:39",
"tags_usage": [],
"to_withdraw": 0,
"transfer_history": [],
"vesting_balance": "0.000 STEEM",
"vesting_shares": "2492.601692 VESTS",
"vesting_withdraw_rate": "0.000000 VESTS",
"vote_history": [],
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779058995
},
"voting_power": 0,
"withdraw_routes": 0,
"withdrawn": 0,
"witness_votes": [],
"witnesses_voted_for": 0,
"rank": 847983
}Withdraw Routes
| Incoming | Outgoing |
|---|---|
Empty | Empty |
{
"incoming": [],
"outgoing": []
}From Date
To Date
steemdelegated 3.475 SP to @cryptotrader-ug2026/05/17 23:03:15
steemdelegated 3.475 SP to @cryptotrader-ug
2026/05/17 23:03:15
| delegatee | cryptotrader-ug |
| delegator | steem |
| vesting shares | 5651.058114 VESTS |
| Transaction Info | Block #106142016/Trx 0608b75d573cfa5da02fe0ac50ad9bde85dbff14 |
View Raw JSON Data
{
"block": 106142016,
"op": [
"delegate_vesting_shares",
{
"delegatee": "cryptotrader-ug",
"delegator": "steem",
"vesting_shares": "5651.058114 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2026-05-17T23:03:15",
"trx_id": "0608b75d573cfa5da02fe0ac50ad9bde85dbff14",
"trx_in_block": 1,
"virtual_op": 0
}steemdelegated 1.807 SP to @cryptotrader-ug2026/05/11 23:01:39
steemdelegated 1.807 SP to @cryptotrader-ug
2026/05/11 23:01:39
| delegatee | cryptotrader-ug |
| delegator | steem |
| vesting shares | 2938.847709 VESTS |
| Transaction Info | Block #105969948/Trx 016ff910c1ddd3e676a8afdd4f9177352b691b0b |
View Raw JSON Data
{
"block": 105969948,
"op": [
"delegate_vesting_shares",
{
"delegatee": "cryptotrader-ug",
"delegator": "steem",
"vesting_shares": "2938.847709 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2026-05-11T23:01:39",
"trx_id": "016ff910c1ddd3e676a8afdd4f9177352b691b0b",
"trx_in_block": 1,
"virtual_op": 0
}steemdelegated 3.482 SP to @cryptotrader-ug2026/04/25 22:26:09
steemdelegated 3.482 SP to @cryptotrader-ug
2026/04/25 22:26:09
| delegatee | cryptotrader-ug |
| delegator | steem |
| vesting shares | 5663.573870 VESTS |
| Transaction Info | Block #105509703/Trx 8cbcc5c44d89baaedb418b4dcc898fba4cbfa33e |
View Raw JSON Data
{
"block": 105509703,
"op": [
"delegate_vesting_shares",
{
"delegatee": "cryptotrader-ug",
"delegator": "steem",
"vesting_shares": "5663.573870 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2026-04-25T22:26:09",
"trx_id": "8cbcc5c44d89baaedb418b4dcc898fba4cbfa33e",
"trx_in_block": 0,
"virtual_op": 0
}steemdelegated 1.833 SP to @cryptotrader-ug2026/01/23 04:36:33
steemdelegated 1.833 SP to @cryptotrader-ug
2026/01/23 04:36:33
| delegatee | cryptotrader-ug |
| delegator | steem |
| vesting shares | 2980.394528 VESTS |
| Transaction Info | Block #102847987/Trx 6e3e1046c6948be8f6aa4a0c130d05f40d4e9021 |
View Raw JSON Data
{
"block": 102847987,
"op": [
"delegate_vesting_shares",
{
"delegatee": "cryptotrader-ug",
"delegator": "steem",
"vesting_shares": "2980.394528 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2026-01-23T04:36:33",
"trx_id": "6e3e1046c6948be8f6aa4a0c130d05f40d4e9021",
"trx_in_block": 1,
"virtual_op": 0
}steemdelegated 1.934 SP to @cryptotrader-ug2024/12/16 23:55:48
steemdelegated 1.934 SP to @cryptotrader-ug
2024/12/16 23:55:48
| delegatee | cryptotrader-ug |
| delegator | steem |
| vesting shares | 3144.613725 VESTS |
| Transaction Info | Block #91294396/Trx fbbab5bee820649e8e4a6ad167a7a066f6cbdc7a |
View Raw JSON Data
{
"block": 91294396,
"op": [
"delegate_vesting_shares",
{
"delegatee": "cryptotrader-ug",
"delegator": "steem",
"vesting_shares": "3144.613725 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2024-12-16T23:55:48",
"trx_id": "fbbab5bee820649e8e4a6ad167a7a066f6cbdc7a",
"trx_in_block": 7,
"virtual_op": 0
}steemdelegated 2.038 SP to @cryptotrader-ug2023/11/13 15:40:06
steemdelegated 2.038 SP to @cryptotrader-ug
2023/11/13 15:40:06
| delegatee | cryptotrader-ug |
| delegator | steem |
| vesting shares | 3313.747257 VESTS |
| Transaction Info | Block #79848638/Trx beb4a0a79028703a794de6edbbaa8622a6cca6b6 |
View Raw JSON Data
{
"block": 79848638,
"op": [
"delegate_vesting_shares",
{
"delegatee": "cryptotrader-ug",
"delegator": "steem",
"vesting_shares": "3313.747257 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2023-11-13T15:40:06",
"trx_id": "beb4a0a79028703a794de6edbbaa8622a6cca6b6",
"trx_in_block": 1,
"virtual_op": 0
}steemdelegated 3.844 SP to @cryptotrader-ug2023/09/21 20:25:42
steemdelegated 3.844 SP to @cryptotrader-ug
2023/09/21 20:25:42
| delegatee | cryptotrader-ug |
| delegator | steem |
| vesting shares | 6251.026043 VESTS |
| Transaction Info | Block #78346154/Trx 2ed74ad0e5efe16ed97fb6670bb4d05942ac5adf |
View Raw JSON Data
{
"block": 78346154,
"op": [
"delegate_vesting_shares",
{
"delegatee": "cryptotrader-ug",
"delegator": "steem",
"vesting_shares": "6251.026043 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2023-09-21T20:25:42",
"trx_id": "2ed74ad0e5efe16ed97fb6670bb4d05942ac5adf",
"trx_in_block": 1,
"virtual_op": 0
}steemdelegated 3.980 SP to @cryptotrader-ug2022/11/03 10:23:45
steemdelegated 3.980 SP to @cryptotrader-ug
2022/11/03 10:23:45
| delegatee | cryptotrader-ug |
| delegator | steem |
| vesting shares | 6472.707481 VESTS |
| Transaction Info | Block #69111700/Trx c9e61b9c4a397216fbf0ef96fc8006a77a506a6c |
View Raw JSON Data
{
"block": 69111700,
"op": [
"delegate_vesting_shares",
{
"delegatee": "cryptotrader-ug",
"delegator": "steem",
"vesting_shares": "6472.707481 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2022-11-03T10:23:45",
"trx_id": "c9e61b9c4a397216fbf0ef96fc8006a77a506a6c",
"trx_in_block": 3,
"virtual_op": 0
}steemdelegated 4.115 SP to @cryptotrader-ug2022/01/17 09:46:09
steemdelegated 4.115 SP to @cryptotrader-ug
2022/01/17 09:46:09
| delegatee | cryptotrader-ug |
| delegator | steem |
| vesting shares | 6693.240712 VESTS |
| Transaction Info | Block #60807997/Trx 38e9c98f03e853b22fa6a18c58fc78817748c2d1 |
View Raw JSON Data
{
"block": 60807997,
"op": [
"delegate_vesting_shares",
{
"delegatee": "cryptotrader-ug",
"delegator": "steem",
"vesting_shares": "6693.240712 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2022-01-17T09:46:09",
"trx_id": "38e9c98f03e853b22fa6a18c58fc78817748c2d1",
"trx_in_block": 37,
"virtual_op": 0
}steemdelegated 4.228 SP to @cryptotrader-ug2021/06/13 23:44:06
steemdelegated 4.228 SP to @cryptotrader-ug
2021/06/13 23:44:06
| delegatee | cryptotrader-ug |
| delegator | steem |
| vesting shares | 6877.009370 VESTS |
| Transaction Info | Block #54606443/Trx ea6a14fbe118d6aea01ea1285b9c878286a8e758 |
View Raw JSON Data
{
"block": 54606443,
"op": [
"delegate_vesting_shares",
{
"delegatee": "cryptotrader-ug",
"delegator": "steem",
"vesting_shares": "6877.009370 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2021-06-13T23:44:06",
"trx_id": "ea6a14fbe118d6aea01ea1285b9c878286a8e758",
"trx_in_block": 5,
"virtual_op": 0
}steemdelegated 4.344 SP to @cryptotrader-ug2020/12/11 10:04:45
steemdelegated 4.344 SP to @cryptotrader-ug
2020/12/11 10:04:45
| delegatee | cryptotrader-ug |
| delegator | steem |
| vesting shares | 7064.431344 VESTS |
| Transaction Info | Block #49353948/Trx f6d4abb17b0a0d7b44f5a0b16647ac8577e88ac3 |
View Raw JSON Data
{
"block": 49353948,
"op": [
"delegate_vesting_shares",
{
"delegatee": "cryptotrader-ug",
"delegator": "steem",
"vesting_shares": "7064.431344 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-12-11T10:04:45",
"trx_id": "f6d4abb17b0a0d7b44f5a0b16647ac8577e88ac3",
"trx_in_block": 0,
"virtual_op": 0
}steemdelegated 1.176 SP to @cryptotrader-ug2020/12/06 03:41:54
steemdelegated 1.176 SP to @cryptotrader-ug
2020/12/06 03:41:54
| delegatee | cryptotrader-ug |
| delegator | steem |
| vesting shares | 1912.543513 VESTS |
| Transaction Info | Block #49205512/Trx e4f4a8b746925e509b60295f872023ded168308e |
View Raw JSON Data
{
"block": 49205512,
"op": [
"delegate_vesting_shares",
{
"delegatee": "cryptotrader-ug",
"delegator": "steem",
"vesting_shares": "1912.543513 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-12-06T03:41:54",
"trx_id": "e4f4a8b746925e509b60295f872023ded168308e",
"trx_in_block": 0,
"virtual_op": 0
}steemdelegated 4.348 SP to @cryptotrader-ug2020/12/05 11:39:09
steemdelegated 4.348 SP to @cryptotrader-ug
2020/12/05 11:39:09
| delegatee | cryptotrader-ug |
| delegator | steem |
| vesting shares | 7070.797983 VESTS |
| Transaction Info | Block #49186619/Trx 7a607f2a6876d58915b4b01975b989c83a6664b3 |
View Raw JSON Data
{
"block": 49186619,
"op": [
"delegate_vesting_shares",
{
"delegatee": "cryptotrader-ug",
"delegator": "steem",
"vesting_shares": "7070.797983 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-12-05T11:39:09",
"trx_id": "7a607f2a6876d58915b4b01975b989c83a6664b3",
"trx_in_block": 5,
"virtual_op": 0
}steemdelegated 1.181 SP to @cryptotrader-ug2020/11/02 13:18:15
steemdelegated 1.181 SP to @cryptotrader-ug
2020/11/02 13:18:15
| delegatee | cryptotrader-ug |
| delegator | steem |
| vesting shares | 1920.017158 VESTS |
| Transaction Info | Block #48255056/Trx 97ac695ae41dab9164bc97e43ded9e821a86c263 |
View Raw JSON Data
{
"block": 48255056,
"op": [
"delegate_vesting_shares",
{
"delegatee": "cryptotrader-ug",
"delegator": "steem",
"vesting_shares": "1920.017158 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-11-02T13:18:15",
"trx_id": "97ac695ae41dab9164bc97e43ded9e821a86c263",
"trx_in_block": 10,
"virtual_op": 0
}steemdelegated 4.472 SP to @cryptotrader-ug2020/05/09 04:38:09
steemdelegated 4.472 SP to @cryptotrader-ug
2020/05/09 04:38:09
| delegatee | cryptotrader-ug |
| delegator | steem |
| vesting shares | 7273.444557 VESTS |
| Transaction Info | Block #43215744/Trx 071994538e189d4c08b2931bf46056598e7d6243 |
View Raw JSON Data
{
"block": 43215744,
"op": [
"delegate_vesting_shares",
{
"delegatee": "cryptotrader-ug",
"delegator": "steem",
"vesting_shares": "7273.444557 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-05-09T04:38:09",
"trx_id": "071994538e189d4c08b2931bf46056598e7d6243",
"trx_in_block": 5,
"virtual_op": 0
}steemdelegated 1.201 SP to @cryptotrader-ug2020/05/08 08:04:36
steemdelegated 1.201 SP to @cryptotrader-ug
2020/05/08 08:04:36
| delegatee | cryptotrader-ug |
| delegator | steem |
| vesting shares | 1953.311140 VESTS |
| Transaction Info | Block #43191650/Trx 6790674b9b1d21e669d89dec343f0d9751604c86 |
View Raw JSON Data
{
"block": 43191650,
"op": [
"delegate_vesting_shares",
{
"delegatee": "cryptotrader-ug",
"delegator": "steem",
"vesting_shares": "1953.311140 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-05-08T08:04:36",
"trx_id": "6790674b9b1d21e669d89dec343f0d9751604c86",
"trx_in_block": 13,
"virtual_op": 0
}2019/10/20 16:45:57
2019/10/20 16:45:57
| author | steemitboard |
| body | Congratulations @cryptotrader-ug! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@cryptotrader-ug/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/@cryptotrader-ug) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=cryptotrader-ug)_</sub> **Do not miss the last post from @steemitboard:** <table><tr><td><a href="https://steemit.com/steemfest/@steemitboard/steemfest-commemorative-badge-refactored"><img src="https://steemitimages.com/64x128/https://files.steempeak.com/file/steempeak/arcange/YqQV5Tbj-image.png"></a></td><td><a href="https://steemit.com/steemfest/@steemitboard/steemfest-commemorative-badge-refactored">SteemFest⁴ commemorative badge refactored</a></td></tr></table> ###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| parent author | cryptotrader-ug |
| parent permlink | 48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds |
| permlink | steemitboard-notify-cryptotrader-ug-20191020t164556000z |
| title | |
| Transaction Info | Block #37453955/Trx 8e025cee654bffe2faa5f9b4b9ac90f8a6ab115d |
View Raw JSON Data
{
"block": 37453955,
"op": [
"comment",
{
"author": "steemitboard",
"body": "Congratulations @cryptotrader-ug! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@cryptotrader-ug/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/@cryptotrader-ug) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=cryptotrader-ug)_</sub>\n\n\n**Do not miss the last post from @steemitboard:**\n<table><tr><td><a href=\"https://steemit.com/steemfest/@steemitboard/steemfest-commemorative-badge-refactored\"><img src=\"https://steemitimages.com/64x128/https://files.steempeak.com/file/steempeak/arcange/YqQV5Tbj-image.png\"></a></td><td><a href=\"https://steemit.com/steemfest/@steemitboard/steemfest-commemorative-badge-refactored\">SteemFest⁴ commemorative badge refactored</a></td></tr></table>\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}",
"parent_author": "cryptotrader-ug",
"parent_permlink": "48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds",
"permlink": "steemitboard-notify-cryptotrader-ug-20191020t164556000z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2019-10-20T16:45:57",
"trx_id": "8e025cee654bffe2faa5f9b4b9ac90f8a6ab115d",
"trx_in_block": 6,
"virtual_op": 0
}steemdelegated 4.569 SP to @cryptotrader-ug2019/08/08 06:24:48
steemdelegated 4.569 SP to @cryptotrader-ug
2019/08/08 06:24:48
| delegatee | cryptotrader-ug |
| delegator | steem |
| vesting shares | 7430.476631 VESTS |
| Transaction Info | Block #35365260/Trx 62e7e55c21dfb59a763e96fc9b69ef043ed9dbdc |
View Raw JSON Data
{
"block": 35365260,
"op": [
"delegate_vesting_shares",
{
"delegatee": "cryptotrader-ug",
"delegator": "steem",
"vesting_shares": "7430.476631 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2019-08-08T06:24:48",
"trx_id": "62e7e55c21dfb59a763e96fc9b69ef043ed9dbdc",
"trx_in_block": 18,
"virtual_op": 0
}2018/10/20 23:58:57
2018/10/20 23:58:57
| author | steemitboard |
| body | Congratulations @cryptotrader-ug! You have received a personal award! [](http://steemitboard.com/@cryptotrader-ug) 1 Year on Steemit <sub>_Click on the badge to view your Board of Honor._</sub> **Do not miss the last post from @steemitboard:** <table><tr><td><a href="https://steemit.com/steemitboard/@steemitboard/steemitboard-ranking-update-resteem-and-resteemed-added"><img src="https://steemitimages.com/64x128/https://cdn.steemitimages.com/DQmfRVpHQhLDhnjDtqck8GPv9NPvNKPfMsDaAFDE1D9Er2Z/header_ranking.png"></a></td><td><a href="https://steemit.com/steemitboard/@steemitboard/steemitboard-ranking-update-resteem-and-resteemed-added">SteemitBoard Ranking update - Resteem and Resteemed added</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"]} |
| parent author | cryptotrader-ug |
| parent permlink | 48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds |
| permlink | steemitboard-notify-cryptotrader-ug-20181020t235856000z |
| title | |
| Transaction Info | Block #26986845/Trx a5cc1d4a49fd205225f023b83c35750bb637de68 |
View Raw JSON Data
{
"block": 26986845,
"op": [
"comment",
{
"author": "steemitboard",
"body": "Congratulations @cryptotrader-ug! You have received a personal award!\n\n[](http://steemitboard.com/@cryptotrader-ug) 1 Year on Steemit\n<sub>_Click on the badge to view your Board of Honor._</sub>\n\n\n**Do not miss the last post from @steemitboard:**\n<table><tr><td><a href=\"https://steemit.com/steemitboard/@steemitboard/steemitboard-ranking-update-resteem-and-resteemed-added\"><img src=\"https://steemitimages.com/64x128/https://cdn.steemitimages.com/DQmfRVpHQhLDhnjDtqck8GPv9NPvNKPfMsDaAFDE1D9Er2Z/header_ranking.png\"></a></td><td><a href=\"https://steemit.com/steemitboard/@steemitboard/steemitboard-ranking-update-resteem-and-resteemed-added\">SteemitBoard Ranking update - Resteem and Resteemed added</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\"]}",
"parent_author": "cryptotrader-ug",
"parent_permlink": "48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds",
"permlink": "steemitboard-notify-cryptotrader-ug-20181020t235856000z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2018-10-20T23:58:57",
"trx_id": "a5cc1d4a49fd205225f023b83c35750bb637de68",
"trx_in_block": 8,
"virtual_op": 0
}steemdelegated 4.691 SP to @cryptotrader-ug2018/08/23 07:20:09
steemdelegated 4.691 SP to @cryptotrader-ug
2018/08/23 07:20:09
| delegatee | cryptotrader-ug |
| delegator | steem |
| vesting shares | 7628.971838 VESTS |
| Transaction Info | Block #25313246/Trx bdf32542ae047fdf4ab49bc70b00bf2fa9f53bc1 |
View Raw JSON Data
{
"block": 25313246,
"op": [
"delegate_vesting_shares",
{
"delegatee": "cryptotrader-ug",
"delegator": "steem",
"vesting_shares": "7628.971838 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2018-08-23T07:20:09",
"trx_id": "bdf32542ae047fdf4ab49bc70b00bf2fa9f53bc1",
"trx_in_block": 8,
"virtual_op": 0
}steemdelegated 17.227 SP to @cryptotrader-ug2018/05/24 09:34:06
steemdelegated 17.227 SP to @cryptotrader-ug
2018/05/24 09:34:06
| delegatee | cryptotrader-ug |
| delegator | steem |
| vesting shares | 28017.989354 VESTS |
| Transaction Info | Block #22707236/Trx 168e0405fca4094884f42033daacaeeb08dfc9e0 |
View Raw JSON Data
{
"block": 22707236,
"op": [
"delegate_vesting_shares",
{
"delegatee": "cryptotrader-ug",
"delegator": "steem",
"vesting_shares": "28017.989354 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2018-05-24T09:34:06",
"trx_id": "168e0405fca4094884f42033daacaeeb08dfc9e0",
"trx_in_block": 0,
"virtual_op": 0
}cryptotrader-ugclaimed reward balance: 0.653 SBD, 0.900 SP2018/05/24 07:12:39
cryptotrader-ugclaimed reward balance: 0.653 SBD, 0.900 SP
2018/05/24 07:12:39
| account | cryptotrader-ug |
| reward sbd | 0.653 SBD |
| reward steem | 0.000 STEEM |
| reward vests | 1464.240395 VESTS |
| Transaction Info | Block #22704506/Trx 685f11eb9daa2c5867d1ef49d6b18b35d422cc26 |
View Raw JSON Data
{
"block": 22704506,
"op": [
"claim_reward_balance",
{
"account": "cryptotrader-ug",
"reward_sbd": "0.653 SBD",
"reward_steem": "0.000 STEEM",
"reward_vests": "1464.240395 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2018-05-24T07:12:39",
"trx_id": "685f11eb9daa2c5867d1ef49d6b18b35d422cc26",
"trx_in_block": 40,
"virtual_op": 0
}steemdelegated 5.623 SP to @cryptotrader-ug2018/05/16 20:12:24
steemdelegated 5.623 SP to @cryptotrader-ug
2018/05/16 20:12:24
| delegatee | cryptotrader-ug |
| delegator | steem |
| vesting shares | 9145.837611 VESTS |
| Transaction Info | Block #22489749/Trx bc8277ceaed3cfe0249ef2df25b0c24ed1753374 |
View Raw JSON Data
{
"block": 22489749,
"op": [
"delegate_vesting_shares",
{
"delegatee": "cryptotrader-ug",
"delegator": "steem",
"vesting_shares": "9145.837611 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2018-05-16T20:12:24",
"trx_id": "bc8277ceaed3cfe0249ef2df25b0c24ed1753374",
"trx_in_block": 5,
"virtual_op": 0
}steemdelegated 18.159 SP to @cryptotrader-ug2018/04/21 20:41:00
steemdelegated 18.159 SP to @cryptotrader-ug
2018/04/21 20:41:00
| delegatee | cryptotrader-ug |
| delegator | steem |
| vesting shares | 29533.806651 VESTS |
| Transaction Info | Block #21771108/Trx dfca13e90a674d7ed33058db3026ba49b2fba71b |
View Raw JSON Data
{
"block": 21771108,
"op": [
"delegate_vesting_shares",
{
"delegatee": "cryptotrader-ug",
"delegator": "steem",
"vesting_shares": "29533.806651 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2018-04-21T20:41:00",
"trx_id": "dfca13e90a674d7ed33058db3026ba49b2fba71b",
"trx_in_block": 14,
"virtual_op": 0
}steemdelegated 18.285 SP to @cryptotrader-ug2017/12/12 22:23:33
steemdelegated 18.285 SP to @cryptotrader-ug
2017/12/12 22:23:33
| delegatee | cryptotrader-ug |
| delegator | steem |
| vesting shares | 29737.638703 VESTS |
| Transaction Info | Block #18032654/Trx 22dcceafcfd2a90e0eee740a090795baa8c33bfe |
View Raw JSON Data
{
"block": 18032654,
"op": [
"delegate_vesting_shares",
{
"delegatee": "cryptotrader-ug",
"delegator": "steem",
"vesting_shares": "29737.638703 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2017-12-12T22:23:33",
"trx_id": "22dcceafcfd2a90e0eee740a090795baa8c33bfe",
"trx_in_block": 8,
"virtual_op": 0
}2017/12/01 06:30:57
2017/12/01 06:30:57
| author | steemitboard |
| body | Congratulations @cryptotrader-ug! You have completed some achievement on Steemit and have been rewarded with new badge(s) : [](http://steemitboard.com/@cryptotrader-ug) You got your First payout Click on any badge to view your own Board of Honor on SteemitBoard. For more information about SteemitBoard, click [here](https://steemit.com/@steemitboard) If you no longer want to receive notifications, reply to this comment with the word `STOP` > By upvoting this notification, you can help all Steemit users. Learn how [here](https://steemit.com/steemitboard/@steemitboard/http-i-cubeupload-com-7ciqeo-png)! |
| json metadata | {"image":["https://steemitboard.com/img/notifications.png"]} |
| parent author | cryptotrader-ug |
| parent permlink | 48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds |
| permlink | steemitboard-notify-cryptotrader-ug-20171201t063059000z |
| title | |
| Transaction Info | Block #17696975/Trx 25ed2fba7436955559b26382e90fd4c267170ca2 |
View Raw JSON Data
{
"block": 17696975,
"op": [
"comment",
{
"author": "steemitboard",
"body": "Congratulations @cryptotrader-ug! You have completed some achievement on Steemit and have been rewarded with new badge(s) :\n\n[](http://steemitboard.com/@cryptotrader-ug) You got your First payout\n\nClick on any badge to view your own Board of Honor on SteemitBoard.\nFor more information about SteemitBoard, click [here](https://steemit.com/@steemitboard)\n\nIf you no longer want to receive notifications, reply to this comment with the word `STOP`\n\n> By upvoting this notification, you can help all Steemit users. Learn how [here](https://steemit.com/steemitboard/@steemitboard/http-i-cubeupload-com-7ciqeo-png)!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notifications.png\"]}",
"parent_author": "cryptotrader-ug",
"parent_permlink": "48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds",
"permlink": "steemitboard-notify-cryptotrader-ug-20171201t063059000z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2017-12-01T06:30:57",
"trx_id": "25ed2fba7436955559b26382e90fd4c267170ca2",
"trx_in_block": 28,
"virtual_op": 0
}2017/12/01 04:21:33
2017/12/01 04:21:33
| author | cryptotrader-ug |
| permlink | 48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds |
| voter | mindsportsio |
| weight | 100 (1.00%) |
| Transaction Info | Block #17694388/Trx 6baabc5056fd5208961bf06d03004a6c2c923936 |
View Raw JSON Data
{
"block": 17694388,
"op": [
"vote",
{
"author": "cryptotrader-ug",
"permlink": "48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds",
"voter": "mindsportsio",
"weight": 100
}
],
"op_in_trx": 0,
"timestamp": "2017-12-01T04:21:33",
"trx_id": "6baabc5056fd5208961bf06d03004a6c2c923936",
"trx_in_block": 13,
"virtual_op": 0
}2017/12/01 04:21:33
2017/12/01 04:21:33
| author | cryptotrader-ug |
| permlink | 48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds |
| voter | mindsportsio |
| weight | 100 (1.00%) |
| Transaction Info | Block #17694388/Trx 318322eb0b10200d0124eebd748f30b2b5d14c78 |
View Raw JSON Data
{
"block": 17694388,
"op": [
"vote",
{
"author": "cryptotrader-ug",
"permlink": "48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds",
"voter": "mindsportsio",
"weight": 100
}
],
"op_in_trx": 0,
"timestamp": "2017-12-01T04:21:33",
"trx_id": "318322eb0b10200d0124eebd748f30b2b5d14c78",
"trx_in_block": 4,
"virtual_op": 0
}cryptotrader-ugreceived 0.653 SBD, 0.898 SP author reward for @cryptotrader-ug / 48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds2017/11/18 23:48:24
cryptotrader-ugreceived 0.653 SBD, 0.898 SP author reward for @cryptotrader-ug / 48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds
2017/11/18 23:48:24
| author | cryptotrader-ug |
| permlink | 48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds |
| sbd payout | 0.653 SBD |
| steem payout | 0.000 STEEM |
| vesting payout | 1460.133129 VESTS |
| Transaction Info | Block #17343486/Virtual Operation #8 |
View Raw JSON Data
{
"block": 17343486,
"op": [
"author_reward",
{
"author": "cryptotrader-ug",
"permlink": "48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds",
"sbd_payout": "0.653 SBD",
"steem_payout": "0.000 STEEM",
"vesting_payout": "1460.133129 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2017-11-18T23:48:24",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": 8
}cryptotrader-ugreceived 0.003 SP curation reward for @cryptotrader-ug / 48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds2017/11/18 23:48:24
cryptotrader-ugreceived 0.003 SP curation reward for @cryptotrader-ug / 48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds
2017/11/18 23:48:24
| comment author | cryptotrader-ug |
| comment permlink | 48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds |
| curator | cryptotrader-ug |
| reward | 4.107266 VESTS |
| Transaction Info | Block #17343486/Virtual Operation #4 |
View Raw JSON Data
{
"block": 17343486,
"op": [
"curation_reward",
{
"comment_author": "cryptotrader-ug",
"comment_permlink": "48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds",
"curator": "cryptotrader-ug",
"reward": "4.107266 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2017-11-18T23:48:24",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": 4
}2017/11/17 20:59:36
2017/11/17 20:59:36
| author | kingscrown |
| permlink | neo-and-gas-prices-going-up-there-is-big-news-to-be-released-in-3-days |
| voter | cryptotrader-ug |
| weight | 10000 (100.00%) |
| Transaction Info | Block #17311314/Trx 1a04da11deab86476c1c3ad8d1e2c4803eeaf55d |
View Raw JSON Data
{
"block": 17311314,
"op": [
"vote",
{
"author": "kingscrown",
"permlink": "neo-and-gas-prices-going-up-there-is-big-news-to-be-released-in-3-days",
"voter": "cryptotrader-ug",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-11-17T20:59:36",
"trx_id": "1a04da11deab86476c1c3ad8d1e2c4803eeaf55d",
"trx_in_block": 9,
"virtual_op": 0
}cryptotrader-ugupvoted (100.00%) @kingscrown / bitcoin-went-to-8000usd-which-alts-stayed-alive2017/11/17 20:59:12
cryptotrader-ugupvoted (100.00%) @kingscrown / bitcoin-went-to-8000usd-which-alts-stayed-alive
2017/11/17 20:59:12
| author | kingscrown |
| permlink | bitcoin-went-to-8000usd-which-alts-stayed-alive |
| voter | cryptotrader-ug |
| weight | 10000 (100.00%) |
| Transaction Info | Block #17311306/Trx 46ad9512f8f37988e8af85df801c59e55a176673 |
View Raw JSON Data
{
"block": 17311306,
"op": [
"vote",
{
"author": "kingscrown",
"permlink": "bitcoin-went-to-8000usd-which-alts-stayed-alive",
"voter": "cryptotrader-ug",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-11-17T20:59:12",
"trx_id": "46ad9512f8f37988e8af85df801c59e55a176673",
"trx_in_block": 12,
"virtual_op": 0
}cryptotrader-ugcustom json: follow2017/11/17 20:59:09
cryptotrader-ugcustom json: follow
2017/11/17 20:59:09
| id | follow |
| json | ["reblog",{"account":"cryptotrader-ug","author":"kingscrown","permlink":"bitcoin-went-to-8000usd-which-alts-stayed-alive"}] |
| required auths | [] |
| required posting auths | ["cryptotrader-ug"] |
| Transaction Info | Block #17311305/Trx 77e81193a12cabce2518ace5e2e297467db894c6 |
View Raw JSON Data
{
"block": 17311305,
"op": [
"custom_json",
{
"id": "follow",
"json": "[\"reblog\",{\"account\":\"cryptotrader-ug\",\"author\":\"kingscrown\",\"permlink\":\"bitcoin-went-to-8000usd-which-alts-stayed-alive\"}]",
"required_auths": [],
"required_posting_auths": [
"cryptotrader-ug"
]
}
],
"op_in_trx": 0,
"timestamp": "2017-11-17T20:59:09",
"trx_id": "77e81193a12cabce2518ace5e2e297467db894c6",
"trx_in_block": 22,
"virtual_op": 0
}2017/11/16 21:15:09
2017/11/16 21:15:09
| author | cryptotrader-ug |
| permlink | 48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds |
| voter | raybilson |
| weight | 10000 (100.00%) |
| Transaction Info | Block #17282832/Trx 2bb3d6b1d47dfcb11297ac944ad508a37a3dc289 |
View Raw JSON Data
{
"block": 17282832,
"op": [
"vote",
{
"author": "cryptotrader-ug",
"permlink": "48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds",
"voter": "raybilson",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-11-16T21:15:09",
"trx_id": "2bb3d6b1d47dfcb11297ac944ad508a37a3dc289",
"trx_in_block": 18,
"virtual_op": 0
}2017/11/16 17:54:51
2017/11/16 17:54:51
| author | cryptotrader-ug |
| permlink | 48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds |
| voter | smartonelegal |
| weight | 100 (1.00%) |
| Transaction Info | Block #17278827/Trx 0a6c857f65e6191017eef4ccb9bf0e3fabd181f4 |
View Raw JSON Data
{
"block": 17278827,
"op": [
"vote",
{
"author": "cryptotrader-ug",
"permlink": "48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds",
"voter": "smartonelegal",
"weight": 100
}
],
"op_in_trx": 0,
"timestamp": "2017-11-16T17:54:51",
"trx_id": "0a6c857f65e6191017eef4ccb9bf0e3fabd181f4",
"trx_in_block": 16,
"virtual_op": 0
}2017/11/16 12:35:54
2017/11/16 12:35:54
| author | cryptotrader-ug |
| body | @@ -1927,15 +1927,19 @@ g a +~~ Bitcoin +~~ Rai @@ -2356,16 +2356,18 @@ ne on a +~~ Parity b @@ -2369,16 +2369,18 @@ ity boat +~~ boat. J @@ -2430,16 +2430,18 @@ y hit a +~~ buggy co @@ -2442,16 +2442,18 @@ ggy code +~~ big sto @@ -2689,16 +2689,18 @@ lid and +~~ instead @@ -2713,16 +2713,18 @@ ard fork +~~ they co |
| json metadata | {"tags":["cryptocurrency","ethereum","hardfork","bitcoin","parity"],"image":["https://steemitimages.com/DQmUHFcKF4g2Qugkt4QLTPvz6MW2phkBBCa5hEKgkyey5xh/image.png"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | cryptocurrency |
| permlink | 48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds |
| title | To Fork or not to Fork? Lessons from the past: The case of the frozen Parity funds |
| Transaction Info | Block #17272448/Trx f466c24b65f17d280025a4be24b50c3de83d7e14 |
View Raw JSON Data
{
"block": 17272448,
"op": [
"comment",
{
"author": "cryptotrader-ug",
"body": "@@ -1927,15 +1927,19 @@\n g a \n+~~\n Bitcoin\n+~~\n Rai\n@@ -2356,16 +2356,18 @@\n ne on a \n+~~\n Parity b\n@@ -2369,16 +2369,18 @@\n ity boat\n+~~\n boat. J\n@@ -2430,16 +2430,18 @@\n y hit a \n+~~\n buggy co\n@@ -2442,16 +2442,18 @@\n ggy code\n+~~\n big sto\n@@ -2689,16 +2689,18 @@\n lid and \n+~~\n instead \n@@ -2713,16 +2713,18 @@\n ard fork\n+~~\n they co\n",
"json_metadata": "{\"tags\":[\"cryptocurrency\",\"ethereum\",\"hardfork\",\"bitcoin\",\"parity\"],\"image\":[\"https://steemitimages.com/DQmUHFcKF4g2Qugkt4QLTPvz6MW2phkBBCa5hEKgkyey5xh/image.png\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "cryptocurrency",
"permlink": "48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds",
"title": "To Fork or not to Fork? Lessons from the past: The case of the frozen Parity funds"
}
],
"op_in_trx": 0,
"timestamp": "2017-11-16T12:35:54",
"trx_id": "f466c24b65f17d280025a4be24b50c3de83d7e14",
"trx_in_block": 3,
"virtual_op": 0
}2017/11/14 05:12:00
2017/11/14 05:12:00
| author | cryptotrader-ug |
| permlink | 48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds |
| voter | mindsportsio |
| weight | 100 (1.00%) |
| Transaction Info | Block #17205982/Trx 534d26cf9c718220645b96fce55206dfbe32b148 |
View Raw JSON Data
{
"block": 17205982,
"op": [
"vote",
{
"author": "cryptotrader-ug",
"permlink": "48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds",
"voter": "mindsportsio",
"weight": 100
}
],
"op_in_trx": 0,
"timestamp": "2017-11-14T05:12:00",
"trx_id": "534d26cf9c718220645b96fce55206dfbe32b148",
"trx_in_block": 17,
"virtual_op": 0
}cryptotrader-ugupvoted (100.00%) @boxmining / daily-bitcoin-cash-flippening-conspiracy2017/11/13 12:28:09
cryptotrader-ugupvoted (100.00%) @boxmining / daily-bitcoin-cash-flippening-conspiracy
2017/11/13 12:28:09
| author | boxmining |
| permlink | daily-bitcoin-cash-flippening-conspiracy |
| voter | cryptotrader-ug |
| weight | 10000 (100.00%) |
| Transaction Info | Block #17185906/Trx 885fb333047a72b30aff42a8db55d30a15de23fb |
View Raw JSON Data
{
"block": 17185906,
"op": [
"vote",
{
"author": "boxmining",
"permlink": "daily-bitcoin-cash-flippening-conspiracy",
"voter": "cryptotrader-ug",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-11-13T12:28:09",
"trx_id": "885fb333047a72b30aff42a8db55d30a15de23fb",
"trx_in_block": 16,
"virtual_op": 0
}2017/11/12 21:08:42
2017/11/12 21:08:42
| author | cryptotrader-ug |
| permlink | 48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds |
| voter | promoted |
| weight | 2500 (25.00%) |
| Transaction Info | Block #17167518/Trx 55dc633f5065f5dd0feda1c87d0ac218f6349336 |
View Raw JSON Data
{
"block": 17167518,
"op": [
"vote",
{
"author": "cryptotrader-ug",
"permlink": "48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds",
"voter": "promoted",
"weight": 2500
}
],
"op_in_trx": 0,
"timestamp": "2017-11-12T21:08:42",
"trx_id": "55dc633f5065f5dd0feda1c87d0ac218f6349336",
"trx_in_block": 15,
"virtual_op": 0
}cryptotrader-ugsent 5.000 SBD to @null- "@cryptotrader-ug/48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds"2017/11/12 21:08:33
cryptotrader-ugsent 5.000 SBD to @null- "@cryptotrader-ug/48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds"
2017/11/12 21:08:33
| amount | 5.000 SBD |
| from | cryptotrader-ug |
| memo | @cryptotrader-ug/48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds |
| to | null |
| Transaction Info | Block #17167515/Trx bfe61d9721013e7fc639bf76b37bcff4dc8f89b7 |
View Raw JSON Data
{
"block": 17167515,
"op": [
"transfer",
{
"amount": "5.000 SBD",
"from": "cryptotrader-ug",
"memo": "@cryptotrader-ug/48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds",
"to": "null"
}
],
"op_in_trx": 0,
"timestamp": "2017-11-12T21:08:33",
"trx_id": "bfe61d9721013e7fc639bf76b37bcff4dc8f89b7",
"trx_in_block": 25,
"virtual_op": 0
}blocktradessent 5.161 SBD to @cryptotrader-ug2017/11/12 21:06:09
blocktradessent 5.161 SBD to @cryptotrader-ug
2017/11/12 21:06:09
| amount | 5.161 SBD |
| from | blocktrades |
| memo | |
| to | cryptotrader-ug |
| Transaction Info | Block #17167467/Trx 8f9d66cb6347e3418fb35fea5588bc4427fa514d |
View Raw JSON Data
{
"block": 17167467,
"op": [
"transfer",
{
"amount": "5.161 SBD",
"from": "blocktrades",
"memo": "",
"to": "cryptotrader-ug"
}
],
"op_in_trx": 0,
"timestamp": "2017-11-12T21:06:09",
"trx_id": "8f9d66cb6347e3418fb35fea5588bc4427fa514d",
"trx_in_block": 13,
"virtual_op": 0
}cryptotrader-ugsent 6.000 STEEM to @blocktrades- "ed3d4550-6a52-493a-8ca8-a2880274c1b6"2017/11/12 21:05:54
cryptotrader-ugsent 6.000 STEEM to @blocktrades- "ed3d4550-6a52-493a-8ca8-a2880274c1b6"
2017/11/12 21:05:54
| amount | 6.000 STEEM |
| from | cryptotrader-ug |
| memo | ed3d4550-6a52-493a-8ca8-a2880274c1b6 |
| to | blocktrades |
| Transaction Info | Block #17167462/Trx 734c9f7010e071bd5cafdc87ef8a880911ea5f80 |
View Raw JSON Data
{
"block": 17167462,
"op": [
"transfer",
{
"amount": "6.000 STEEM",
"from": "cryptotrader-ug",
"memo": "ed3d4550-6a52-493a-8ca8-a2880274c1b6",
"to": "blocktrades"
}
],
"op_in_trx": 0,
"timestamp": "2017-11-12T21:05:54",
"trx_id": "734c9f7010e071bd5cafdc87ef8a880911ea5f80",
"trx_in_block": 2,
"virtual_op": 0
}blocktradessent 7.149 STEEM to @cryptotrader-ug2017/11/12 20:41:51
blocktradessent 7.149 STEEM to @cryptotrader-ug
2017/11/12 20:41:51
| amount | 7.149 STEEM |
| from | blocktrades |
| memo | |
| to | cryptotrader-ug |
| Transaction Info | Block #17166981/Trx 87738ee949ea9e11a7780e74a74391a1ff41d1a9 |
View Raw JSON Data
{
"block": 17166981,
"op": [
"transfer",
{
"amount": "7.149 STEEM",
"from": "blocktrades",
"memo": "",
"to": "cryptotrader-ug"
}
],
"op_in_trx": 0,
"timestamp": "2017-11-12T20:41:51",
"trx_id": "87738ee949ea9e11a7780e74a74391a1ff41d1a9",
"trx_in_block": 16,
"virtual_op": 0
}blocktradessent 3.593 STEEM to @cryptotrader-ug2017/11/12 20:34:42
blocktradessent 3.593 STEEM to @cryptotrader-ug
2017/11/12 20:34:42
| amount | 3.593 STEEM |
| from | blocktrades |
| memo | |
| to | cryptotrader-ug |
| Transaction Info | Block #17166838/Trx 2dcc9c881dba908114dc74000516de075b197303 |
View Raw JSON Data
{
"block": 17166838,
"op": [
"transfer",
{
"amount": "3.593 STEEM",
"from": "blocktrades",
"memo": "",
"to": "cryptotrader-ug"
}
],
"op_in_trx": 0,
"timestamp": "2017-11-12T20:34:42",
"trx_id": "2dcc9c881dba908114dc74000516de075b197303",
"trx_in_block": 18,
"virtual_op": 0
}2017/11/12 04:57:12
2017/11/12 04:57:12
| author | steemitboard |
| body | Congratulations @cryptotrader-ug! You have completed some achievement on Steemit and have been rewarded with new badge(s) : [](http://steemitboard.com/@cryptotrader-ug) Award for the number of upvotes received Click on any badge to view your own Board of Honor on SteemitBoard. For more information about SteemitBoard, click [here](https://steemit.com/@steemitboard) If you no longer want to receive notifications, reply to this comment with the word `STOP` > By upvoting this notification, you can help all Steemit users. Learn how [here](https://steemit.com/steemitboard/@steemitboard/http-i-cubeupload-com-7ciqeo-png)! |
| json metadata | {"image":["https://steemitboard.com/img/notifications.png"]} |
| parent author | cryptotrader-ug |
| parent permlink | 48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds |
| permlink | steemitboard-notify-cryptotrader-ug-20171112t045712000z |
| title | |
| Transaction Info | Block #17148088/Trx 0e533a2e4d1d57131f4b8306c1773ae30b660efe |
View Raw JSON Data
{
"block": 17148088,
"op": [
"comment",
{
"author": "steemitboard",
"body": "Congratulations @cryptotrader-ug! You have completed some achievement on Steemit and have been rewarded with new badge(s) :\n\n[](http://steemitboard.com/@cryptotrader-ug) Award for the number of upvotes received\n\nClick on any badge to view your own Board of Honor on SteemitBoard.\nFor more information about SteemitBoard, click [here](https://steemit.com/@steemitboard)\n\nIf you no longer want to receive notifications, reply to this comment with the word `STOP`\n\n> By upvoting this notification, you can help all Steemit users. Learn how [here](https://steemit.com/steemitboard/@steemitboard/http-i-cubeupload-com-7ciqeo-png)!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notifications.png\"]}",
"parent_author": "cryptotrader-ug",
"parent_permlink": "48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds",
"permlink": "steemitboard-notify-cryptotrader-ug-20171112t045712000z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2017-11-12T04:57:12",
"trx_id": "0e533a2e4d1d57131f4b8306c1773ae30b660efe",
"trx_in_block": 5,
"virtual_op": 0
}2017/11/12 02:34:12
2017/11/12 02:34:12
| author | cryptotrader-ug |
| permlink | 48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds |
| voter | samaraj |
| weight | 10000 (100.00%) |
| Transaction Info | Block #17145229/Trx 4e5c079fce476d0d4eff09af2a6e3b04f258d96b |
View Raw JSON Data
{
"block": 17145229,
"op": [
"vote",
{
"author": "cryptotrader-ug",
"permlink": "48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds",
"voter": "samaraj",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-11-12T02:34:12",
"trx_id": "4e5c079fce476d0d4eff09af2a6e3b04f258d96b",
"trx_in_block": 4,
"virtual_op": 0
}2017/11/12 02:34:09
2017/11/12 02:34:09
| author | cryptotrader-ug |
| permlink | 48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds |
| voter | vorochagin |
| weight | 10000 (100.00%) |
| Transaction Info | Block #17145228/Trx fcafcf397b090556d3baab5134fb92dd41a07eb8 |
View Raw JSON Data
{
"block": 17145228,
"op": [
"vote",
{
"author": "cryptotrader-ug",
"permlink": "48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds",
"voter": "vorochagin",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-11-12T02:34:09",
"trx_id": "fcafcf397b090556d3baab5134fb92dd41a07eb8",
"trx_in_block": 6,
"virtual_op": 0
}2017/11/12 02:27:15
2017/11/12 02:27:15
| author | steemitboard |
| body | Congratulations @cryptotrader-ug! You have completed some achievement on Steemit and have been rewarded with new badge(s) : [](http://steemitboard.com/@cryptotrader-ug) You published your First Post [](http://steemitboard.com/@cryptotrader-ug) You got a First Vote [](http://steemitboard.com/@cryptotrader-ug) You published 4 posts in one day Click on any badge to view your own Board of Honor on SteemitBoard. For more information about SteemitBoard, click [here](https://steemit.com/@steemitboard) If you no longer want to receive notifications, reply to this comment with the word `STOP` > By upvoting this notification, you can help all Steemit users. Learn how [here](https://steemit.com/steemitboard/@steemitboard/http-i-cubeupload-com-7ciqeo-png)! |
| json metadata | {"image":["https://steemitboard.com/img/notifications.png"]} |
| parent author | cryptotrader-ug |
| parent permlink | 48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds |
| permlink | steemitboard-notify-cryptotrader-ug-20171112t022717000z |
| title | |
| Transaction Info | Block #17145090/Trx 485a8d18e0a6b4707ce16235bcdf9d3af5cdc75b |
View Raw JSON Data
{
"block": 17145090,
"op": [
"comment",
{
"author": "steemitboard",
"body": "Congratulations @cryptotrader-ug! You have completed some achievement on Steemit and have been rewarded with new badge(s) :\n\n[](http://steemitboard.com/@cryptotrader-ug) You published your First Post\n[](http://steemitboard.com/@cryptotrader-ug) You got a First Vote\n[](http://steemitboard.com/@cryptotrader-ug) You published 4 posts in one day\n\nClick on any badge to view your own Board of Honor on SteemitBoard.\nFor more information about SteemitBoard, click [here](https://steemit.com/@steemitboard)\n\nIf you no longer want to receive notifications, reply to this comment with the word `STOP`\n\n> By upvoting this notification, you can help all Steemit users. Learn how [here](https://steemit.com/steemitboard/@steemitboard/http-i-cubeupload-com-7ciqeo-png)!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notifications.png\"]}",
"parent_author": "cryptotrader-ug",
"parent_permlink": "48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds",
"permlink": "steemitboard-notify-cryptotrader-ug-20171112t022717000z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2017-11-12T02:27:15",
"trx_id": "485a8d18e0a6b4707ce16235bcdf9d3af5cdc75b",
"trx_in_block": 16,
"virtual_op": 0
}2017/11/12 02:07:24
2017/11/12 02:07:24
| author | cryptotrader-ug |
| permlink | 4jtpfy-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds |
| voter | aarroni |
| weight | 10000 (100.00%) |
| Transaction Info | Block #17144693/Trx 37641c02717d4cc717b2dbe6e2e48743eb3c0d7c |
View Raw JSON Data
{
"block": 17144693,
"op": [
"vote",
{
"author": "cryptotrader-ug",
"permlink": "4jtpfy-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds",
"voter": "aarroni",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-11-12T02:07:24",
"trx_id": "37641c02717d4cc717b2dbe6e2e48743eb3c0d7c",
"trx_in_block": 0,
"virtual_op": 0
}2017/11/12 02:07:21
2017/11/12 02:07:21
| author | cryptotrader-ug |
| permlink | 4jtpfy-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds |
| voter | lpndinar |
| weight | 10000 (100.00%) |
| Transaction Info | Block #17144692/Trx 810e65723ea758f1cf9005734ce78f94394a83dd |
View Raw JSON Data
{
"block": 17144692,
"op": [
"vote",
{
"author": "cryptotrader-ug",
"permlink": "4jtpfy-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds",
"voter": "lpndinar",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-11-12T02:07:21",
"trx_id": "810e65723ea758f1cf9005734ce78f94394a83dd",
"trx_in_block": 11,
"virtual_op": 0
}2017/11/12 02:07:21
2017/11/12 02:07:21
| author | cryptotrader-ug |
| permlink | 4jtpfy-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds |
| voter | lqera |
| weight | 10000 (100.00%) |
| Transaction Info | Block #17144692/Trx 261bf2dbd08229735bc7e8b2764be5a5908fb2cc |
View Raw JSON Data
{
"block": 17144692,
"op": [
"vote",
{
"author": "cryptotrader-ug",
"permlink": "4jtpfy-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds",
"voter": "lqera",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-11-12T02:07:21",
"trx_id": "261bf2dbd08229735bc7e8b2764be5a5908fb2cc",
"trx_in_block": 6,
"virtual_op": 0
}2017/11/12 02:07:21
2017/11/12 02:07:21
| author | cryptotrader-ug |
| permlink | 4jtpfy-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds |
| voter | kaktuz515 |
| weight | 10000 (100.00%) |
| Transaction Info | Block #17144692/Trx 4ce06e211e309edb410430fade65b4f0bafe725d |
View Raw JSON Data
{
"block": 17144692,
"op": [
"vote",
{
"author": "cryptotrader-ug",
"permlink": "4jtpfy-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds",
"voter": "kaktuz515",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-11-12T02:07:21",
"trx_id": "4ce06e211e309edb410430fade65b4f0bafe725d",
"trx_in_block": 3,
"virtual_op": 0
}2017/11/12 02:07:21
2017/11/12 02:07:21
| author | cryptotrader-ug |
| permlink | 4jtpfy-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds |
| voter | varloi |
| weight | 10000 (100.00%) |
| Transaction Info | Block #17144692/Trx 351627493a85583a76c70716634612df60f78a32 |
View Raw JSON Data
{
"block": 17144692,
"op": [
"vote",
{
"author": "cryptotrader-ug",
"permlink": "4jtpfy-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds",
"voter": "varloi",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-11-12T02:07:21",
"trx_id": "351627493a85583a76c70716634612df60f78a32",
"trx_in_block": 0,
"virtual_op": 0
}2017/11/12 02:07:18
2017/11/12 02:07:18
| author | cryptotrader-ug |
| permlink | 4jtpfy-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds |
| voter | ninochka |
| weight | 10000 (100.00%) |
| Transaction Info | Block #17144691/Trx e642da8c4688327c69b7a516ce19158fb5f76fd6 |
View Raw JSON Data
{
"block": 17144691,
"op": [
"vote",
{
"author": "cryptotrader-ug",
"permlink": "4jtpfy-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds",
"voter": "ninochka",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-11-12T02:07:18",
"trx_id": "e642da8c4688327c69b7a516ce19158fb5f76fd6",
"trx_in_block": 3,
"virtual_op": 0
}2017/11/12 00:52:36
2017/11/12 00:52:36
| author | cryptotrader-ug |
| body | Sometimes as a community, we have to take a moment and look at the past in order to find a solution for our present day troubles because history always repeats itself. Take the case of the Parity “hack” which saw 280 million dollars worth of ether frozen due to the “unintentional” exploit that was caused by a crypto newbie. The exploit was a kill switch that deleted the code library which corresponded with the affected Parity wallets. This rendered the software useless and left many crypto start-ups without funds. This event has quickly created a divide within the Ether community due to the different options that have been suggested as remedies to rectify the issue and help out the affected companies. The most controversial suggestion has been a hardfork of the Ethereum network in order to unlock the frozen funds. However, this suggestion has not gone down well with many members of the community. We can easily find a correlation between this event and an event that occurred hundreds of years ago to the Yapese on the island of Yap. The Yapese are a society that used large lime stone disks as their official currency. Centuries ago, Yapese explorers journeyed across the ocean in bamboo canoes to the island of Palau, where they encountered limestone for the first time. After negotiations with the people of Palau, the Yapese established a quarry and used shell tools to carve disc-shaped stones that they named “Rai.” The stones varied in diameter from a few inches to 12 feet and weighed up to 4 tons. A hole punched into the centre of each disc allowed the explorers to carry the larger stones (Rai) to their bamboo canoes using poles. Manoeuvring the Rai into the boats and keeping afloat during the long journey home, was a much more treacherous undertaking.  Due to the difficulty associated with obtaining a Bitcoin Rai, its value within the community increased and the people of Yap decided to have it as a medium of exchange and a store of value (money). The Rai was really valuable and one wouldn't use it for everyday purchases but instead use it for big occasions such as weddings, political deals and such. One time, according to the island's oral tradition, an expedition was returning to the island with a giant Rai stone on a Parity boat boat. Just before they got back to the island, they hit a buggy code big storm which froze flipped the boat and the stone wound up at the bottom of the ocean. The crew made it back to the island and told everybody what happened. The Yapese then decided that the Rai at the bottom of the ocean was still valid and instead of a hard fork they continued acknowledging it during trade deals, even though it was at the bottom of the ocean. Till this day, someone still owns a stake in this submerged piece of Rai, even though it has not been seen for hundreds of years. Taking a leaf from the Yapese, I suggest we keep things simple and avoid implementing a hard fork in order to recover the lost funds. I believe it would be much simpler to create an official token pegged to and backed by the funds in the Parity wallet 1-to-1. These tokens would be issued to the affected parties in order for them to continue business as usual. The fact is that we all know the funds still exist and we can verify the total amount in the multisig wallet. This information can be used to confirm the total circulating supply. The token can be named the “Parity Frozen Funds Token” (PFFT) or Parity Lost Funds Token (PLFT). The token can also have a futures market before its release because of course, it’s not a “good proposal” if it does not have pre-launch hype. I mean, how hard can this be? If the Yapese could do it hundreds of years ago, why can’t we with all our “high-tech” internet stuff? This proposed solution can also be used across other use cases such as events where a hodler passes on before sharing their private keys with their heir. |
| json metadata | {"tags":["cryptocurrency","ethereum","hardfork","bitcoin","parity"],"image":["https://steemitimages.com/DQmUHFcKF4g2Qugkt4QLTPvz6MW2phkBBCa5hEKgkyey5xh/image.png"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | cryptocurrency |
| permlink | 48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds |
| title | To Fork or not to Fork? Lessons from the past: The case of the frozen Parity funds |
| Transaction Info | Block #17143197/Trx b1eef9d6b9267586aa56ea30ef4dd42300be90ca |
View Raw JSON Data
{
"block": 17143197,
"op": [
"comment",
{
"author": "cryptotrader-ug",
"body": "Sometimes as a community, we have to take a moment and look at the past in order to find a solution for our present day troubles because history always repeats itself. \n\nTake the case of the Parity “hack” which saw 280 million dollars worth of ether frozen due to the “unintentional” exploit that was caused by a crypto newbie. The exploit was a kill switch that deleted the code library which corresponded with the affected Parity wallets. This rendered the software useless and left many crypto start-ups without funds. This event has quickly created a divide within the Ether community due to the different options that have been suggested as remedies to rectify the issue and help out the affected companies. The most controversial suggestion has been a hardfork of the Ethereum network in order to unlock the frozen funds. However, this suggestion has not gone down well with many members of the community. \n\nWe can easily find a correlation between this event and an event that occurred hundreds of years ago to the Yapese on the island of Yap. The Yapese are a society that used large lime stone disks as their official currency.\nCenturies ago, Yapese explorers journeyed across the ocean in bamboo canoes to the island of Palau, where they encountered limestone for the first time. After negotiations with the people of Palau, the Yapese established a quarry and used shell tools to carve disc-shaped stones that they named “Rai.” \n\nThe stones varied in diameter from a few inches to 12 feet and weighed up to 4 tons. A hole punched into the centre of each disc allowed the explorers to carry the larger stones (Rai) to their bamboo canoes using poles. Manoeuvring the Rai into the boats and keeping afloat during the long journey home, was a much more treacherous undertaking. \n\n \n\nDue to the difficulty associated with obtaining a Bitcoin Rai, its value within the community increased and the people of Yap decided to have it as a medium of exchange and a store of value (money). The Rai was really valuable and one wouldn't use it for everyday purchases but instead use it for big occasions such as weddings, political deals and such. \nOne time, according to the island's oral tradition, an expedition was returning to the island with a giant Rai stone on a Parity boat boat. Just before they got back to the island, they hit a buggy code big storm which froze flipped the boat and the stone wound up at the bottom of the ocean. The crew made it back to the island and told everybody what happened. The Yapese then decided that the Rai at the bottom of the ocean was still valid and instead of a hard fork they continued acknowledging it during trade deals, even though it was at the bottom of the ocean.\nTill this day, someone still owns a stake in this submerged piece of Rai, even though it has not been seen for hundreds of years.\n\nTaking a leaf from the Yapese, I suggest we keep things simple and avoid implementing a hard fork in order to recover the lost funds. I believe it would be much simpler to create an official token pegged to and backed by the funds in the Parity wallet 1-to-1. These tokens would be issued to the affected parties in order for them to continue business as usual. \n\nThe fact is that we all know the funds still exist and we can verify the total amount in the multisig wallet. This information can be used to confirm the total circulating supply. The token can be named the “Parity Frozen Funds Token” (PFFT) or Parity Lost Funds Token (PLFT). The token can also have a futures market before its release because of course, it’s not a “good proposal” if it does not have pre-launch hype. I mean, how hard can this be? If the Yapese could do it hundreds of years ago, why can’t we with all our “high-tech” internet stuff? \n\nThis proposed solution can also be used across other use cases such as events where a hodler passes on before sharing their private keys with their heir.",
"json_metadata": "{\"tags\":[\"cryptocurrency\",\"ethereum\",\"hardfork\",\"bitcoin\",\"parity\"],\"image\":[\"https://steemitimages.com/DQmUHFcKF4g2Qugkt4QLTPvz6MW2phkBBCa5hEKgkyey5xh/image.png\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "cryptocurrency",
"permlink": "48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds",
"title": "To Fork or not to Fork? Lessons from the past: The case of the frozen Parity funds"
}
],
"op_in_trx": 0,
"timestamp": "2017-11-12T00:52:36",
"trx_id": "b1eef9d6b9267586aa56ea30ef4dd42300be90ca",
"trx_in_block": 1,
"virtual_op": 0
}cryptotrader-ugfollowed @boxmining2017/11/12 00:21:06
cryptotrader-ugfollowed @boxmining
2017/11/12 00:21:06
| id | follow |
| json | ["follow",{"follower":"cryptotrader-ug","following":"boxmining","what":["blog"]}] |
| required auths | [] |
| required posting auths | ["cryptotrader-ug"] |
| Transaction Info | Block #17142567/Trx 53887ab4a07954a9ee13c222a9a04408ecae10b6 |
View Raw JSON Data
{
"block": 17142567,
"op": [
"custom_json",
{
"id": "follow",
"json": "[\"follow\",{\"follower\":\"cryptotrader-ug\",\"following\":\"boxmining\",\"what\":[\"blog\"]}]",
"required_auths": [],
"required_posting_auths": [
"cryptotrader-ug"
]
}
],
"op_in_trx": 0,
"timestamp": "2017-11-12T00:21:06",
"trx_id": "53887ab4a07954a9ee13c222a9a04408ecae10b6",
"trx_in_block": 20,
"virtual_op": 0
}cryptotrader-ugupvoted (100.00%) @anomaly / mining-is-profitable-again2017/11/12 00:19:06
cryptotrader-ugupvoted (100.00%) @anomaly / mining-is-profitable-again
2017/11/12 00:19:06
| author | anomaly |
| permlink | mining-is-profitable-again |
| voter | cryptotrader-ug |
| weight | 10000 (100.00%) |
| Transaction Info | Block #17142527/Trx 50a6393c578d1d5bd86d2efe27832a87b06704b8 |
View Raw JSON Data
{
"block": 17142527,
"op": [
"vote",
{
"author": "anomaly",
"permlink": "mining-is-profitable-again",
"voter": "cryptotrader-ug",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-11-12T00:19:06",
"trx_id": "50a6393c578d1d5bd86d2efe27832a87b06704b8",
"trx_in_block": 17,
"virtual_op": 0
}2017/11/11 23:56:54
2017/11/11 23:56:54
| author | cryptotrader-ug |
| body | . |
| json metadata | {"tags":["cryptocurrency"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | cryptocurrency |
| permlink | 4jtpfy-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds |
| title | . |
| Transaction Info | Block #17142083/Trx 8ea644a6b51517472285e422ccdfa51d20fb81d1 |
View Raw JSON Data
{
"block": 17142083,
"op": [
"comment",
{
"author": "cryptotrader-ug",
"body": ".",
"json_metadata": "{\"tags\":[\"cryptocurrency\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "cryptocurrency",
"permlink": "4jtpfy-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds",
"title": "."
}
],
"op_in_trx": 0,
"timestamp": "2017-11-11T23:56:54",
"trx_id": "8ea644a6b51517472285e422ccdfa51d20fb81d1",
"trx_in_block": 0,
"virtual_op": 0
}2017/11/11 23:55:42
2017/11/11 23:55:42
| author | cryptotrader-ug |
| permlink | 48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds |
| voter | cryptotrader-ug |
| weight | 10000 (100.00%) |
| Transaction Info | Block #17142059/Trx 815a91e3e66f6a340399cfa8d256c381f54d19ca |
View Raw JSON Data
{
"block": 17142059,
"op": [
"vote",
{
"author": "cryptotrader-ug",
"permlink": "48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds",
"voter": "cryptotrader-ug",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-11-11T23:55:42",
"trx_id": "815a91e3e66f6a340399cfa8d256c381f54d19ca",
"trx_in_block": 4,
"virtual_op": 0
}cryptotrader-ugdeleted a comment or post2017/11/11 23:55:00
cryptotrader-ugdeleted a comment or post
2017/11/11 23:55:00
| author | cryptotrader-ug |
| permlink | 4t1j7f-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds |
| Transaction Info | Block #17142045/Trx 831a2b8bedf6cd0d5e92348bc97a68a3b8e2fe28 |
View Raw JSON Data
{
"block": 17142045,
"op": [
"delete_comment",
{
"author": "cryptotrader-ug",
"permlink": "4t1j7f-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds"
}
],
"op_in_trx": 0,
"timestamp": "2017-11-11T23:55:00",
"trx_id": "831a2b8bedf6cd0d5e92348bc97a68a3b8e2fe28",
"trx_in_block": 21,
"virtual_op": 0
}cryptotrader-ugdeleted a comment or post2017/11/11 23:53:39
cryptotrader-ugdeleted a comment or post
2017/11/11 23:53:39
| author | cryptotrader-ug |
| permlink | to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds |
| Transaction Info | Block #17142018/Trx 26279cd73e27c0f554eac13655d60a0b09873221 |
View Raw JSON Data
{
"block": 17142018,
"op": [
"delete_comment",
{
"author": "cryptotrader-ug",
"permlink": "to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds"
}
],
"op_in_trx": 0,
"timestamp": "2017-11-11T23:53:39",
"trx_id": "26279cd73e27c0f554eac13655d60a0b09873221",
"trx_in_block": 7,
"virtual_op": 0
}2017/11/11 23:52:09
2017/11/11 23:52:09
| author | cryptotrader-ug |
| permlink | 48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds |
| voter | gcryptg |
| weight | 10000 (100.00%) |
| Transaction Info | Block #17141988/Trx 5ccf6fde7e563f8bb733885a20d37b2eeeec362c |
View Raw JSON Data
{
"block": 17141988,
"op": [
"vote",
{
"author": "cryptotrader-ug",
"permlink": "48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds",
"voter": "gcryptg",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-11-11T23:52:09",
"trx_id": "5ccf6fde7e563f8bb733885a20d37b2eeeec362c",
"trx_in_block": 6,
"virtual_op": 0
}2017/11/11 23:52:09
2017/11/11 23:52:09
| author | cryptotrader-ug |
| permlink | 4jtpfy-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds |
| voter | cryptotrader-ug |
| weight | 10000 (100.00%) |
| Transaction Info | Block #17141988/Trx 25bd8b11a92553d653812de89ec40763c98b2f5f |
View Raw JSON Data
{
"block": 17141988,
"op": [
"vote",
{
"author": "cryptotrader-ug",
"permlink": "4jtpfy-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds",
"voter": "cryptotrader-ug",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-11-11T23:52:09",
"trx_id": "25bd8b11a92553d653812de89ec40763c98b2f5f",
"trx_in_block": 0,
"virtual_op": 0
}2017/11/11 23:52:03
2017/11/11 23:52:03
| author | gcryptg |
| body | Who has openly come out and stated that they are affected by this issue? Did startups come out and say that they have lost funds? |
| json metadata | {"tags":["cryptocurrency"],"app":"steemit/0.1"} |
| parent author | cryptotrader-ug |
| parent permlink | 48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds |
| permlink | re-cryptotrader-ug-48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds-20171111t235231242z |
| title | |
| Transaction Info | Block #17141986/Trx eb33d07130833839926917d42dc9d2c3ddec217e |
View Raw JSON Data
{
"block": 17141986,
"op": [
"comment",
{
"author": "gcryptg",
"body": "Who has openly come out and stated that they are affected by this issue? Did startups come out and say that they have lost funds?",
"json_metadata": "{\"tags\":[\"cryptocurrency\"],\"app\":\"steemit/0.1\"}",
"parent_author": "cryptotrader-ug",
"parent_permlink": "48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds",
"permlink": "re-cryptotrader-ug-48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds-20171111t235231242z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2017-11-11T23:52:03",
"trx_id": "eb33d07130833839926917d42dc9d2c3ddec217e",
"trx_in_block": 21,
"virtual_op": 0
}2017/11/11 23:48:24
2017/11/11 23:48:24
| author | cryptotrader-ug |
| body | Sometimes as a community, we have to take a moment and look at the past in order to find a solution for our present day troubles because history always repeats itself. Take the case of the Parity “hack” which saw 280 million dollars worth of ether frozen due to the “unintentional” exploit that was caused by a crypto newbie. The exploit was a kill switch that deleted the code library which corresponded with the affected Parity wallets. This rendered the software useless and left many crypto start-ups without funds. This event has quickly created a divide within the Ether community due to the different options that have been suggested as remedies to rectify the issue and help out the affected companies. The most controversial suggestion has been a hardfork of the Ethereum network in order to unlock the frozen funds. However, this suggestion has not gone down well with many members of the community. We can easily find a correlation between this event and an event that occurred hundreds of years ago to the Yapese on the island of Yap. The Yapese are a society that used large lime stone disks as their official currency. Centuries ago, Yapese explorers journeyed across the ocean in bamboo canoes to the island of Palau, where they encountered limestone for the first time. After negotiations with the people of Palau, the Yapese established a quarry and used shell tools to carve disc-shaped stones that they named “Rai.” The stones varied in diameter from a few inches to 12 feet and weighed up to 4 tons. A hole punched into the centre of each disc allowed the explorers to carry the larger stones (Rai) to their bamboo canoes using poles. Manoeuvring the Rai into the boats and keeping afloat during the long journey home, was a much more treacherous undertaking.  Due to the difficulty associated with obtaining a Bitcoin Rai, its value within the community increased and the people of Yap decided to have it as a medium of exchange and a store of value (money). The Rai was really valuable and one wouldn't use it for everyday purchases but instead use it for big occasions such as weddings, political deals and such. One time, according to the island's oral tradition, an expedition was returning to the island with a giant Rai stone on a Parity boat boat. Just before they got back to the island, they hit a buggy code big storm which froze flipped the boat and the stone wound up at the bottom of the ocean. The crew made it back to the island and told everybody what happened. The Yapese then decided that the Rai at the bottom of the ocean was still valid and instead of a hard fork they continued acknowledging it during trade deals, even though it was at the bottom of the ocean. Till this day, someone still owns a stake in this submerged piece of Rai, even though it has not been seen for hundreds of years. Taking a leaf from the Yapese, I suggest we keep things simple and avoid implementing a hard fork in order to recover the lost funds. I believe it would be much simpler to create an official token pegged to and backed by the funds in the Parity wallet 1-to-1. These tokens would be issued to the affected parties in order for them to continue business as usual. The fact is that we all know the funds still exist and we can verify the total amount in the multisig wallet. This information can be used to confirm the total circulating supply. The token can be named the “Parity Frozen Funds Token” (PFFT) or Parity Lost Funds Token (PLFT). The token can also have a futures market before its release because of course, it’s not a “good proposal” if it does not have pre-launch hype. I mean, how hard can this be? If the Yapese could do it hundreds of years ago, why can’t we with all our “high-tech” internet stuff? This proposed solution can also be used across other use cases such as events where a hodler passes on before sharing their private keys with their heir. |
| json metadata | {"tags":["cryptocurrency","ethereum","hardfork","bitcoin","parity"],"image":["https://steemitimages.com/DQmUHFcKF4g2Qugkt4QLTPvz6MW2phkBBCa5hEKgkyey5xh/image.png"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | cryptocurrency |
| permlink | 48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds |
| title | To fork or not to fork? Lessons from the past: The case of the frozen Parity funds |
| Transaction Info | Block #17141913/Trx 9c0bd3fc34159ba83c3c09fe5384300ddf3a39f7 |
View Raw JSON Data
{
"block": 17141913,
"op": [
"comment",
{
"author": "cryptotrader-ug",
"body": "Sometimes as a community, we have to take a moment and look at the past in order to find a solution for our present day troubles because history always repeats itself. \n\nTake the case of the Parity “hack” which saw 280 million dollars worth of ether frozen due to the “unintentional” exploit that was caused by a crypto newbie. The exploit was a kill switch that deleted the code library which corresponded with the affected Parity wallets. This rendered the software useless and left many crypto start-ups without funds. This event has quickly created a divide within the Ether community due to the different options that have been suggested as remedies to rectify the issue and help out the affected companies. The most controversial suggestion has been a hardfork of the Ethereum network in order to unlock the frozen funds. However, this suggestion has not gone down well with many members of the community. \n\nWe can easily find a correlation between this event and an event that occurred hundreds of years ago to the Yapese on the island of Yap. The Yapese are a society that used large lime stone disks as their official currency.\nCenturies ago, Yapese explorers journeyed across the ocean in bamboo canoes to the island of Palau, where they encountered limestone for the first time. After negotiations with the people of Palau, the Yapese established a quarry and used shell tools to carve disc-shaped stones that they named “Rai.” \n\nThe stones varied in diameter from a few inches to 12 feet and weighed up to 4 tons. A hole punched into the centre of each disc allowed the explorers to carry the larger stones (Rai) to their bamboo canoes using poles. Manoeuvring the Rai into the boats and keeping afloat during the long journey home, was a much more treacherous undertaking. \n\n \n\nDue to the difficulty associated with obtaining a Bitcoin Rai, its value within the community increased and the people of Yap decided to have it as a medium of exchange and a store of value (money). The Rai was really valuable and one wouldn't use it for everyday purchases but instead use it for big occasions such as weddings, political deals and such. \nOne time, according to the island's oral tradition, an expedition was returning to the island with a giant Rai stone on a Parity boat boat. Just before they got back to the island, they hit a buggy code big storm which froze flipped the boat and the stone wound up at the bottom of the ocean. The crew made it back to the island and told everybody what happened. The Yapese then decided that the Rai at the bottom of the ocean was still valid and instead of a hard fork they continued acknowledging it during trade deals, even though it was at the bottom of the ocean.\nTill this day, someone still owns a stake in this submerged piece of Rai, even though it has not been seen for hundreds of years.\n\nTaking a leaf from the Yapese, I suggest we keep things simple and avoid implementing a hard fork in order to recover the lost funds. I believe it would be much simpler to create an official token pegged to and backed by the funds in the Parity wallet 1-to-1. These tokens would be issued to the affected parties in order for them to continue business as usual. \n\nThe fact is that we all know the funds still exist and we can verify the total amount in the multisig wallet. This information can be used to confirm the total circulating supply. The token can be named the “Parity Frozen Funds Token” (PFFT) or Parity Lost Funds Token (PLFT). The token can also have a futures market before its release because of course, it’s not a “good proposal” if it does not have pre-launch hype. I mean, how hard can this be? If the Yapese could do it hundreds of years ago, why can’t we with all our “high-tech” internet stuff? \n\nThis proposed solution can also be used across other use cases such as events where a hodler passes on before sharing their private keys with their heir.",
"json_metadata": "{\"tags\":[\"cryptocurrency\",\"ethereum\",\"hardfork\",\"bitcoin\",\"parity\"],\"image\":[\"https://steemitimages.com/DQmUHFcKF4g2Qugkt4QLTPvz6MW2phkBBCa5hEKgkyey5xh/image.png\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "cryptocurrency",
"permlink": "48hajo-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds",
"title": "To fork or not to fork? Lessons from the past: The case of the frozen Parity funds"
}
],
"op_in_trx": 0,
"timestamp": "2017-11-11T23:48:24",
"trx_id": "9c0bd3fc34159ba83c3c09fe5384300ddf3a39f7",
"trx_in_block": 5,
"virtual_op": 0
}2017/11/11 23:38:30
2017/11/11 23:38:30
| author | cryptotrader-ug |
| body | Sometimes as a community, we have to take a moment and look at the past in order to find a solution for our present day troubles because history always repeats itself. Take the case of the Parity “hack” which saw 280 million dollars worth of ether frozen due to the “unintentional” exploit that was caused by a crypto newbie. The exploit was a kill switch that deleted the code library which corresponded with the affected Parity wallets. This rendered the software useless and left many crypto start-ups without funds. This event has quickly created a divide within the Ether community due to the different options that have been suggested as remedies to rectify the issue and help out the affected companies. The most controversial suggestion has been a hardfork of the Ethereum network in order to unlock the frozen funds. However, this suggestion has not gone down well with many members of the community. We can easily find a correlation between this event and an event that occurred hundreds of years ago to the Yapese on the island of Yap. The Yapese are a society that used large lime stone disks as their official currency. Centuries ago, Yapese explorers journeyed across the ocean in bamboo canoes to the island of Palau, where they encountered limestone for the first time. After negotiations with the people of Palau, the Yapese established a quarry and used shell tools to carve disc-shaped stones that they named “Rai.” The stones varied in diameter from a few inches to 12 feet and weighed up to 4 tons. A hole punched into the centre of each disc allowed the explorers to carry the larger stones (Rai) to their bamboo canoes using poles. Manoeuvring the Rai into the boats and keeping afloat during the long journey home, was a much more treacherous undertaking.  Due to the difficulty associated with obtaining a Bitcoin Rai, its value within the community increased and the people of Yap decided to have it as a medium of exchange and a store of value (money). The Rai was really valuable and one wouldn't use it for everyday purchases but instead use it for big occasions such as weddings, political deals and such. One time, according to the island's oral tradition, an expedition was returning to the island with a giant Rai stone on a Parity boat boat. Just before they got back to the island, they hit a buggy code big storm which froze flipped the boat and the stone wound up at the bottom of the ocean. The crew made it back to the island and told everybody what happened. The Yapese then decided that the Rai at the bottom of the ocean was still valid and instead of a hard fork they continued acknowledging it during trade deals, even though it was at the bottom of the ocean. Till this day, someone still owns a stake in this submerged piece of Rai, even though it has not been seen for hundreds of years. Taking a leaf from the Yapese, I suggest we keep things simple and avoid implementing a hard fork in order to recover the lost funds. I believe it would be much simpler to create an official token pegged to and backed by the funds in the Parity wallet 1-to-1. These tokens would be issued to the affected parties in order for them to continue business as usual. The fact is that we all know the funds still exist and we can verify the total amount in the multisig wallet. This information can be used to confirm the total circulating supply. The token can be named the “Parity Frozen Funds Token” (PFFT) or Parity Lost Funds Token (PLFT). The token can also have a futures market before its release because of course, it’s not a “good proposal” if it does not have pre-launch hype. I mean, how hard can this be? If the Yapese could do it hundreds of years ago, why can’t we with all our “high-tech” internet stuff? This proposed solution can also be used across other use cases such as events where a hodler passes on before sharing their private keys with their heir. |
| json metadata | {"tags":["cryptocurrency","ethereum","hardfork","bitcoin","parity"],"image":["https://steemitimages.com/DQmUHFcKF4g2Qugkt4QLTPvz6MW2phkBBCa5hEKgkyey5xh/image.png"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | cryptocurrency |
| permlink | 4t1j7f-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds |
| title | To fork or not to fork? Lessons from the past: The case of the frozen Parity funds |
| Transaction Info | Block #17141715/Trx 1cc821cec347f7952f3ac46f000867fe8e7eb67e |
View Raw JSON Data
{
"block": 17141715,
"op": [
"comment",
{
"author": "cryptotrader-ug",
"body": "Sometimes as a community, we have to take a moment and look at the past in order to find a solution for our present day troubles because history always repeats itself. \n\nTake the case of the Parity “hack” which saw 280 million dollars worth of ether frozen due to the “unintentional” exploit that was caused by a crypto newbie. The exploit was a kill switch that deleted the code library which corresponded with the affected Parity wallets. This rendered the software useless and left many crypto start-ups without funds. This event has quickly created a divide within the Ether community due to the different options that have been suggested as remedies to rectify the issue and help out the affected companies. The most controversial suggestion has been a hardfork of the Ethereum network in order to unlock the frozen funds. However, this suggestion has not gone down well with many members of the community. \n\nWe can easily find a correlation between this event and an event that occurred hundreds of years ago to the Yapese on the island of Yap. The Yapese are a society that used large lime stone disks as their official currency.\nCenturies ago, Yapese explorers journeyed across the ocean in bamboo canoes to the island of Palau, where they encountered limestone for the first time. After negotiations with the people of Palau, the Yapese established a quarry and used shell tools to carve disc-shaped stones that they named “Rai.” \n\nThe stones varied in diameter from a few inches to 12 feet and weighed up to 4 tons. A hole punched into the centre of each disc allowed the explorers to carry the larger stones (Rai) to their bamboo canoes using poles. Manoeuvring the Rai into the boats and keeping afloat during the long journey home, was a much more treacherous undertaking. \n\n \n\nDue to the difficulty associated with obtaining a Bitcoin Rai, its value within the community increased and the people of Yap decided to have it as a medium of exchange and a store of value (money). The Rai was really valuable and one wouldn't use it for everyday purchases but instead use it for big occasions such as weddings, political deals and such. \nOne time, according to the island's oral tradition, an expedition was returning to the island with a giant Rai stone on a Parity boat boat. Just before they got back to the island, they hit a buggy code big storm which froze flipped the boat and the stone wound up at the bottom of the ocean. The crew made it back to the island and told everybody what happened. The Yapese then decided that the Rai at the bottom of the ocean was still valid and instead of a hard fork they continued acknowledging it during trade deals, even though it was at the bottom of the ocean.\nTill this day, someone still owns a stake in this submerged piece of Rai, even though it has not been seen for hundreds of years.\n\nTaking a leaf from the Yapese, I suggest we keep things simple and avoid implementing a hard fork in order to recover the lost funds. I believe it would be much simpler to create an official token pegged to and backed by the funds in the Parity wallet 1-to-1. These tokens would be issued to the affected parties in order for them to continue business as usual. \n\nThe fact is that we all know the funds still exist and we can verify the total amount in the multisig wallet. This information can be used to confirm the total circulating supply. The token can be named the “Parity Frozen Funds Token” (PFFT) or Parity Lost Funds Token (PLFT). The token can also have a futures market before its release because of course, it’s not a “good proposal” if it does not have pre-launch hype. I mean, how hard can this be? If the Yapese could do it hundreds of years ago, why can’t we with all our “high-tech” internet stuff? \n\nThis proposed solution can also be used across other use cases such as events where a hodler passes on before sharing their private keys with their heir.",
"json_metadata": "{\"tags\":[\"cryptocurrency\",\"ethereum\",\"hardfork\",\"bitcoin\",\"parity\"],\"image\":[\"https://steemitimages.com/DQmUHFcKF4g2Qugkt4QLTPvz6MW2phkBBCa5hEKgkyey5xh/image.png\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "cryptocurrency",
"permlink": "4t1j7f-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds",
"title": "To fork or not to fork? Lessons from the past: The case of the frozen Parity funds"
}
],
"op_in_trx": 0,
"timestamp": "2017-11-11T23:38:30",
"trx_id": "1cc821cec347f7952f3ac46f000867fe8e7eb67e",
"trx_in_block": 16,
"virtual_op": 0
}2017/11/11 23:22:54
2017/11/11 23:22:54
| author | cryptotrader-ug |
| permlink | 4jtpfy-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds |
| voter | anomaly |
| weight | 100 (1.00%) |
| Transaction Info | Block #17141403/Trx 25bb327d8db59cf572c82f34941177aa977ca6ea |
View Raw JSON Data
{
"block": 17141403,
"op": [
"vote",
{
"author": "cryptotrader-ug",
"permlink": "4jtpfy-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds",
"voter": "anomaly",
"weight": 100
}
],
"op_in_trx": 0,
"timestamp": "2017-11-11T23:22:54",
"trx_id": "25bb327d8db59cf572c82f34941177aa977ca6ea",
"trx_in_block": 1,
"virtual_op": 0
}2017/11/11 23:21:30
2017/11/11 23:21:30
| author | cryptotrader-ug |
| body | Sometimes as a community, we have to take a moment and look at the past in order to find a solution for our present day troubles because history always repeats itself. Take the case of the Parity “hack” which saw 280 million dollars worth of ether frozen due to the “unintentional” exploit that was caused by a crypto newbie. The exploit was a kill switch that deleted the code library which corresponded with the affected Parity wallets. This rendered the software useless and left many crypto start-ups without funds. This event has quickly created a divide within the Ether community due to the different options that have been suggested as remedies to rectify the issue and help out the affected companies. The most controversial suggestion has been a hardfork of the Ethereum network in order to unlock the frozen funds. However, this suggestion has not gone down well with many members of the community. We can easily find a correlation between this event and an event that occurred hundreds of years ago to the Yapese on the island of Yap. The Yapese are a society that used large lime stone disks as their official currency. Centuries ago, Yapese explorers journeyed across the ocean in bamboo canoes to the island of Palau, where they encountered limestone for the first time. After negotiations with the people of Palau, the Yapese established a quarry and used shell tools to carve disc-shaped stones that they named “Rai.” The stones varied in diameter from a few inches to 12 feet and weighed up to 4 tons. A hole punched into the centre of each disc allowed the explorers to carry the larger stones (Rai) to their bamboo canoes using poles. Manoeuvring the Rai into the boats and keeping afloat during the long journey home, was a much more treacherous undertaking.  Due to the difficulty associated with obtaining a Bitcoin Rai, its value within the community increased and the people of Yap decided to have it as a medium of exchange and a store of value (money). The Rai was really valuable and one wouldn't use it for everyday purchases but instead use it for big occasions such as weddings, political deals and such. One time, according to the island's oral tradition, an expedition was returning to the island with a giant Rai stone on a Parity boat boat. Just before they got back to the island, they hit a buggy code big storm which froze flipped the boat and the stone wound up at the bottom of the ocean. The crew made it back to the island and told everybody what happened. The Yapese then decided that the Rai at the bottom of the ocean was still valid and instead of a hard fork they continued acknowledging it during trade deals, even though it was at the bottom of the ocean. Till this day, someone still owns a stake in this submerged piece of Rai, even though it has not been seen for hundreds of years. Taking a leaf from the Yapese, I suggest we keep things simple and avoid implementing a hard fork in order to recover the lost funds. I believe it would be much simpler to create an official token pegged to and backed by the funds in the Parity wallet 1-to-1. These tokens would be issued to the affected parties in order for them to continue business as usual. The fact is that we all know the funds still exist and we can verify the total amount in the multisig wallet. This information can be used to confirm the total circulating supply. The token can be named the “Parity Frozen Funds Token” (PFFT) or Parity Lost Funds Token (PLFT). The token can also have a futures market before its release because of course, it’s not a “good proposal” if it does not have pre-launch hype. I mean, how hard can this be? If the Yapese could do it hundreds of years ago, why can’t we with all our “high-tech” internet stuff? This proposed solution can also be used across other use cases such as events where a hodler passes on before sharing their private keys with their heir. |
| json metadata | {"tags":["cryptocurrency","ethereum","hardfork","bitcoin","parity"],"image":["https://steemitimages.com/DQmUHFcKF4g2Qugkt4QLTPvz6MW2phkBBCa5hEKgkyey5xh/image.png"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | cryptocurrency |
| permlink | 4jtpfy-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds |
| title | To fork or not to fork? Lessons from the past: The case of the frozen Parity funds |
| Transaction Info | Block #17141375/Trx a549c61ff09c5cc90723d248646c452cb4663fb6 |
View Raw JSON Data
{
"block": 17141375,
"op": [
"comment",
{
"author": "cryptotrader-ug",
"body": "Sometimes as a community, we have to take a moment and look at the past in order to find a solution for our present day troubles because history always repeats itself. \n\nTake the case of the Parity “hack” which saw 280 million dollars worth of ether frozen due to the “unintentional” exploit that was caused by a crypto newbie. The exploit was a kill switch that deleted the code library which corresponded with the affected Parity wallets. This rendered the software useless and left many crypto start-ups without funds. This event has quickly created a divide within the Ether community due to the different options that have been suggested as remedies to rectify the issue and help out the affected companies. The most controversial suggestion has been a hardfork of the Ethereum network in order to unlock the frozen funds. However, this suggestion has not gone down well with many members of the community. \n\nWe can easily find a correlation between this event and an event that occurred hundreds of years ago to the Yapese on the island of Yap. The Yapese are a society that used large lime stone disks as their official currency.\nCenturies ago, Yapese explorers journeyed across the ocean in bamboo canoes to the island of Palau, where they encountered limestone for the first time. After negotiations with the people of Palau, the Yapese established a quarry and used shell tools to carve disc-shaped stones that they named “Rai.” \n\nThe stones varied in diameter from a few inches to 12 feet and weighed up to 4 tons. A hole punched into the centre of each disc allowed the explorers to carry the larger stones (Rai) to their bamboo canoes using poles. Manoeuvring the Rai into the boats and keeping afloat during the long journey home, was a much more treacherous undertaking. \n\n \n\nDue to the difficulty associated with obtaining a Bitcoin Rai, its value within the community increased and the people of Yap decided to have it as a medium of exchange and a store of value (money). The Rai was really valuable and one wouldn't use it for everyday purchases but instead use it for big occasions such as weddings, political deals and such. \nOne time, according to the island's oral tradition, an expedition was returning to the island with a giant Rai stone on a Parity boat boat. Just before they got back to the island, they hit a buggy code big storm which froze flipped the boat and the stone wound up at the bottom of the ocean. The crew made it back to the island and told everybody what happened. The Yapese then decided that the Rai at the bottom of the ocean was still valid and instead of a hard fork they continued acknowledging it during trade deals, even though it was at the bottom of the ocean.\nTill this day, someone still owns a stake in this submerged piece of Rai, even though it has not been seen for hundreds of years.\n\nTaking a leaf from the Yapese, I suggest we keep things simple and avoid implementing a hard fork in order to recover the lost funds. I believe it would be much simpler to create an official token pegged to and backed by the funds in the Parity wallet 1-to-1. These tokens would be issued to the affected parties in order for them to continue business as usual. \n\nThe fact is that we all know the funds still exist and we can verify the total amount in the multisig wallet. This information can be used to confirm the total circulating supply. The token can be named the “Parity Frozen Funds Token” (PFFT) or Parity Lost Funds Token (PLFT). The token can also have a futures market before its release because of course, it’s not a “good proposal” if it does not have pre-launch hype. I mean, how hard can this be? If the Yapese could do it hundreds of years ago, why can’t we with all our “high-tech” internet stuff? \n\nThis proposed solution can also be used across other use cases such as events where a hodler passes on before sharing their private keys with their heir.",
"json_metadata": "{\"tags\":[\"cryptocurrency\",\"ethereum\",\"hardfork\",\"bitcoin\",\"parity\"],\"image\":[\"https://steemitimages.com/DQmUHFcKF4g2Qugkt4QLTPvz6MW2phkBBCa5hEKgkyey5xh/image.png\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "cryptocurrency",
"permlink": "4jtpfy-to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds",
"title": "To fork or not to fork? Lessons from the past: The case of the frozen Parity funds"
}
],
"op_in_trx": 0,
"timestamp": "2017-11-11T23:21:30",
"trx_id": "a549c61ff09c5cc90723d248646c452cb4663fb6",
"trx_in_block": 17,
"virtual_op": 0
}2017/11/11 23:09:54
2017/11/11 23:09:54
| author | cryptotrader-ug |
| body | Sometimes as a community, we have to take a moment and look at the past in order to find a solution for our present day troubles because history always repeats itself. Take the case of the Parity “hack” which saw 280 million dollars worth of ether frozen due to the “unintentional” exploit that was caused by a crypto newbie. The exploit was a kill switch that deleted the code library which corresponded with the affected Parity wallets. This rendered the software useless and left many crypto start-ups without funds. This event has quickly created a divide within the Ether community due to the different options that have been suggested as remedies to rectify the issue and help out the affected companies. The most controversial suggestion has been a hardfork of the Ethereum network in order to unlock the frozen funds. However, this suggestion has not gone down well with many members of the community. We can easily find a correlation between this event and an event that occurred hundreds of years ago to the Yapese on the island of Yap. The Yapese are a society that used large lime stone disks as their official currency. Centuries ago, Yapese explorers journeyed across the ocean in bamboo canoes to the island of Palau, where they encountered limestone for the first time. After negotiations with the people of Palau, the Yapese established a quarry and used shell tools to carve disc-shaped stones that they named “Rai.” The stones varied in diameter from a few inches to 12 feet and weighed up to 4 tons. A hole punched into the centre of each disc allowed the explorers to carry the larger stones (Rai) to their bamboo canoes using poles. Manoeuvring the Rai into the boats and keeping afloat during the long journey home, was a much more treacherous undertaking.  Due to the difficulty associated with obtaining a Bitcoin Rai, its value within the community increased and the people of Yap decided to have it as a medium of exchange and a store of value (money). The Rai was really valuable and one wouldn't use it for everyday purchases but instead use it for big occasions such as weddings, political deals and such. One time, according to the island's oral tradition, an expedition was returning to the island with a giant Rai stone on a Parity boat boat. Just before they got back to the island, they hit a buggy code big storm which froze flipped the boat and the stone wound up at the bottom of the ocean. The crew made it back to the island and told everybody what happened. The Yapese then decided that the Rai at the bottom of the ocean was still valid and instead of a hard fork they continued acknowledging it during trade deals, even though it was at the bottom of the ocean. Till this day, someone still owns a stake in this submerged piece of Rai, even though it has not been seen for hundreds of years. Taking a leaf from the Yapese, I suggest we keep things simple and avoid implementing a hard fork in order to recover the lost funds. I believe it would be much simpler to create an official token pegged to and backed by the funds in the Parity wallet 1-to-1. These tokens would be issued to the affected parties in order for them to continue business as usual. The fact is that we all know the funds still exist and we can verify the total amount in the multisig wallet. This information can be used to confirm the total circulating supply. The token can be named the “Parity Frozen Funds Token” (PFFT) or Parity Lost Funds Token (PLFT). The token can also have a futures market before its release because of course, it’s not a “good proposal” if it does not have pre-launch hype. I mean, how hard can this be? If the Yapese could do it hundreds of years ago, why can’t we with all our “high-tech” internet stuff? This proposed solution can also be used across other use cases such as events where a hodler passes on before sharing their private keys with their heir. |
| json metadata | {"tags":["cryptocurrency","ethereum","hardfork","bitcoin","parity"],"image":["https://steemitimages.com/DQmUHFcKF4g2Qugkt4QLTPvz6MW2phkBBCa5hEKgkyey5xh/image.png"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | cryptocurrency |
| permlink | to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds |
| title | To fork or not to fork? Lessons from the past: The case of the frozen Parity funds |
| Transaction Info | Block #17141143/Trx 434e2c7158c356bc3b866b64a19e21bd84afe831 |
View Raw JSON Data
{
"block": 17141143,
"op": [
"comment",
{
"author": "cryptotrader-ug",
"body": "Sometimes as a community, we have to take a moment and look at the past in order to find a solution for our present day troubles because history always repeats itself. \n\nTake the case of the Parity “hack” which saw 280 million dollars worth of ether frozen due to the “unintentional” exploit that was caused by a crypto newbie. The exploit was a kill switch that deleted the code library which corresponded with the affected Parity wallets. This rendered the software useless and left many crypto start-ups without funds. This event has quickly created a divide within the Ether community due to the different options that have been suggested as remedies to rectify the issue and help out the affected companies. The most controversial suggestion has been a hardfork of the Ethereum network in order to unlock the frozen funds. However, this suggestion has not gone down well with many members of the community. \n\nWe can easily find a correlation between this event and an event that occurred hundreds of years ago to the Yapese on the island of Yap. The Yapese are a society that used large lime stone disks as their official currency.\nCenturies ago, Yapese explorers journeyed across the ocean in bamboo canoes to the island of Palau, where they encountered limestone for the first time. After negotiations with the people of Palau, the Yapese established a quarry and used shell tools to carve disc-shaped stones that they named “Rai.” \n\nThe stones varied in diameter from a few inches to 12 feet and weighed up to 4 tons. A hole punched into the centre of each disc allowed the explorers to carry the larger stones (Rai) to their bamboo canoes using poles. Manoeuvring the Rai into the boats and keeping afloat during the long journey home, was a much more treacherous undertaking. \n\n \n\nDue to the difficulty associated with obtaining a Bitcoin Rai, its value within the community increased and the people of Yap decided to have it as a medium of exchange and a store of value (money). The Rai was really valuable and one wouldn't use it for everyday purchases but instead use it for big occasions such as weddings, political deals and such. \nOne time, according to the island's oral tradition, an expedition was returning to the island with a giant Rai stone on a Parity boat boat. Just before they got back to the island, they hit a buggy code big storm which froze flipped the boat and the stone wound up at the bottom of the ocean. The crew made it back to the island and told everybody what happened. The Yapese then decided that the Rai at the bottom of the ocean was still valid and instead of a hard fork they continued acknowledging it during trade deals, even though it was at the bottom of the ocean.\nTill this day, someone still owns a stake in this submerged piece of Rai, even though it has not been seen for hundreds of years.\n\nTaking a leaf from the Yapese, I suggest we keep things simple and avoid implementing a hard fork in order to recover the lost funds. I believe it would be much simpler to create an official token pegged to and backed by the funds in the Parity wallet 1-to-1. These tokens would be issued to the affected parties in order for them to continue business as usual. \n\nThe fact is that we all know the funds still exist and we can verify the total amount in the multisig wallet. This information can be used to confirm the total circulating supply. The token can be named the “Parity Frozen Funds Token” (PFFT) or Parity Lost Funds Token (PLFT). The token can also have a futures market before its release because of course, it’s not a “good proposal” if it does not have pre-launch hype. I mean, how hard can this be? If the Yapese could do it hundreds of years ago, why can’t we with all our “high-tech” internet stuff? \n\nThis proposed solution can also be used across other use cases such as events where a hodler passes on before sharing their private keys with their heir.",
"json_metadata": "{\"tags\":[\"cryptocurrency\",\"ethereum\",\"hardfork\",\"bitcoin\",\"parity\"],\"image\":[\"https://steemitimages.com/DQmUHFcKF4g2Qugkt4QLTPvz6MW2phkBBCa5hEKgkyey5xh/image.png\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "cryptocurrency",
"permlink": "to-fork-or-not-to-fork-lessons-from-the-past-the-case-of-the-frozen-parity-funds",
"title": "To fork or not to fork? Lessons from the past: The case of the frozen Parity funds"
}
],
"op_in_trx": 0,
"timestamp": "2017-11-11T23:09:54",
"trx_id": "434e2c7158c356bc3b866b64a19e21bd84afe831",
"trx_in_block": 17,
"virtual_op": 0
}2017/11/09 09:47:45
2017/11/09 09:47:45
| author | maxnachamkin |
| permlink | how-to-create-your-own-ethereum-token-in-an-hour-erc20-verified |
| voter | cryptotrader-ug |
| weight | 10000 (100.00%) |
| Transaction Info | Block #17067541/Trx 4317fdff8d83d189e64330dc6008d547b513c30f |
View Raw JSON Data
{
"block": 17067541,
"op": [
"vote",
{
"author": "maxnachamkin",
"permlink": "how-to-create-your-own-ethereum-token-in-an-hour-erc20-verified",
"voter": "cryptotrader-ug",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-11-09T09:47:45",
"trx_id": "4317fdff8d83d189e64330dc6008d547b513c30f",
"trx_in_block": 9,
"virtual_op": 0
}steemcreated a new account: @cryptotrader-ug2017/10/20 15:15:45
steemcreated a new account: @cryptotrader-ug
2017/10/20 15:15:45
| active | {"account_auths":[],"key_auths":[["STM5oqSSkWCDsHTb1xjHxkd41axm6vJ2u62UVcoFvdECaZnyoZQb8",1]],"weight_threshold":1} |
| creator | steem |
| delegation | 57000.000000 VESTS |
| extensions | [] |
| fee | 0.500 STEEM |
| json metadata | |
| memo key | STM5xMHYHjHJyc2d2ViXjZnXaCSWqu6zLTRkYcgtx4dnYozy6MVED |
| new account name | cryptotrader-ug |
| owner | {"account_auths":[],"key_auths":[["STM7FBmTQuwEweCcJDX2ZAhgNeCzzPXoyF5wJHEcxtpSy5HFtUwo3",1]],"weight_threshold":1} |
| posting | {"account_auths":[],"key_auths":[["STM7W9cv1PxqcoZyN1GUMgi4rzZwnDx4UYvk2d9U2b3rcGUu23w5u",1]],"weight_threshold":1} |
| Transaction Info | Block #16498433/Trx 7f52a926b0c25b56e02ea6702fdb05e99020ed28 |
View Raw JSON Data
{
"block": 16498433,
"op": [
"account_create_with_delegation",
{
"active": {
"account_auths": [],
"key_auths": [
[
"STM5oqSSkWCDsHTb1xjHxkd41axm6vJ2u62UVcoFvdECaZnyoZQb8",
1
]
],
"weight_threshold": 1
},
"creator": "steem",
"delegation": "57000.000000 VESTS",
"extensions": [],
"fee": "0.500 STEEM",
"json_metadata": "",
"memo_key": "STM5xMHYHjHJyc2d2ViXjZnXaCSWqu6zLTRkYcgtx4dnYozy6MVED",
"new_account_name": "cryptotrader-ug",
"owner": {
"account_auths": [],
"key_auths": [
[
"STM7FBmTQuwEweCcJDX2ZAhgNeCzzPXoyF5wJHEcxtpSy5HFtUwo3",
1
]
],
"weight_threshold": 1
},
"posting": {
"account_auths": [],
"key_auths": [
[
"STM7W9cv1PxqcoZyN1GUMgi4rzZwnDx4UYvk2d9U2b3rcGUu23w5u",
1
]
],
"weight_threshold": 1
}
}
],
"op_in_trx": 0,
"timestamp": "2017-10-20T15:15:45",
"trx_id": "7f52a926b0c25b56e02ea6702fdb05e99020ed28",
"trx_in_block": 5,
"virtual_op": 0
}Manabar
Voting Power100.00%
Downvote Power100.00%
Resource Credits100.00%
Reputation Progress0.55%
{
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779058995
},
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779058995
},
"rc_account": {
"account": "cryptotrader-ug",
"max_rc": "10164408779",
"max_rc_creation_adjustment": {
"amount": "2020748973",
"nai": "@@000000037",
"precision": 6
},
"rc_manabar": {
"current_mana": "10164408779",
"last_update_time": 1779058995
}
}
}Account Metadata
| POSTING JSON METADATA | |
| None | |
| JSON METADATA | |
| None |
{
"posting_json_metadata": {},
"json_metadata": {}
}Auth Keys
Owner
Single Signature
Public Keys
STM7FBmTQuwEweCcJDX2ZAhgNeCzzPXoyF5wJHEcxtpSy5HFtUwo31/1
Active
Single Signature
Public Keys
STM5oqSSkWCDsHTb1xjHxkd41axm6vJ2u62UVcoFvdECaZnyoZQb81/1
Posting
Single Signature
Public Keys
STM7W9cv1PxqcoZyN1GUMgi4rzZwnDx4UYvk2d9U2b3rcGUu23w5u1/1
Memo
STM5xMHYHjHJyc2d2ViXjZnXaCSWqu6zLTRkYcgtx4dnYozy6MVED
{
"owner": {
"account_auths": [],
"key_auths": [
[
"STM7FBmTQuwEweCcJDX2ZAhgNeCzzPXoyF5wJHEcxtpSy5HFtUwo3",
1
]
],
"weight_threshold": 1
},
"active": {
"account_auths": [],
"key_auths": [
[
"STM5oqSSkWCDsHTb1xjHxkd41axm6vJ2u62UVcoFvdECaZnyoZQb8",
1
]
],
"weight_threshold": 1
},
"posting": {
"account_auths": [],
"key_auths": [
[
"STM7W9cv1PxqcoZyN1GUMgi4rzZwnDx4UYvk2d9U2b3rcGUu23w5u",
1
]
],
"weight_threshold": 1
},
"memo": "STM5xMHYHjHJyc2d2ViXjZnXaCSWqu6zLTRkYcgtx4dnYozy6MVED"
}Witness Votes
0 / 30
No active witness votes.
[]