VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS0.00%
Net Worth
0.034USD
STEEM
0.000STEEM
SBD
0.000SBD
Effective Power
5.001SP
├── Own SP
0.635SP
└── Incoming DelegationsDeleg
+4.366SP
Detailed Balance
| STEEM | ||
| balance | 0.000STEEM | STEEM |
| market_balance | 0.000STEEM | STEEM |
| savings_balance | 0.000STEEM | STEEM |
| reward_steem_balance | 0.000STEEM | STEEM |
| STEEM POWER | ||
| Own SP | 0.635SP | SP |
| Delegated Out | 0.000SP | SP |
| Delegation In | 4.366SP | SP |
| Effective Power | 5.001SP | SP |
| Reward SP (pending) | 0.000SP | SP |
| SBD | ||
| sbd_balance | 0.000SBD | SBD |
| sbd_conversions | 0.000SBD | SBD |
| sbd_market_balance | 0.000SBD | SBD |
| savings_sbd_balance | 0.000SBD | SBD |
| reward_sbd_balance | 0.000SBD | SBD |
{
"balance": "0.000 STEEM",
"savings_balance": "0.000 STEEM",
"reward_steem_balance": "0.000 STEEM",
"vesting_shares": "1034.518256 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "7109.141550 VESTS",
"sbd_balance": "0.000 SBD",
"savings_sbd_balance": "0.000 SBD",
"reward_sbd_balance": "0.000 SBD",
"conversions": []
}Account Info
| name | cryptojoy |
| id | 232184 |
| rank | 1,428,420 |
| reputation | 21971128 |
| created | 2017-06-29T06:22:27 |
| recovery_account | steem |
| proxy | None |
| post_count | 3 |
| comment_count | 0 |
| lifetime_vote_count | 0 |
| witnesses_voted_for | 0 |
| last_post | 2019-10-05T06:46:57 |
| last_root_post | 2019-10-05T06:46:57 |
| last_vote_time | 2019-10-05T10:26:00 |
| proxied_vsf_votes | 0, 0, 0, 0 |
| can_vote | 1 |
| voting_power | 0 |
| delayed_votes | 0 |
| balance | 0.000 STEEM |
| savings_balance | 0.000 STEEM |
| sbd_balance | 0.000 SBD |
| savings_sbd_balance | 0.000 SBD |
| vesting_shares | 1034.518256 VESTS |
| delegated_vesting_shares | 0.000000 VESTS |
| received_vesting_shares | 7109.141550 VESTS |
| reward_vesting_balance | 0.000000 VESTS |
| vesting_balance | 0.000 STEEM |
| vesting_withdraw_rate | 0.000000 VESTS |
| next_vesting_withdrawal | 1969-12-31T23:59:59 |
| withdrawn | 0 |
| to_withdraw | 0 |
| withdraw_routes | 0 |
| savings_withdraw_requests | 0 |
| last_account_recovery | 1970-01-01T00:00:00 |
| reset_account | null |
| last_owner_update | 1970-01-01T00:00:00 |
| last_account_update | 1970-01-01T00:00:00 |
| mined | No |
| sbd_seconds | 0 |
| sbd_last_interest_payment | 1970-01-01T00:00:00 |
| savings_sbd_last_interest_payment | 1970-01-01T00:00:00 |
{
"active": {
"account_auths": [],
"key_auths": [
[
"STM85udCa38pY3KUwZ6AQrPX3B9QMHZfp3cCMZqs2s92Jp5sbXiPC",
1
]
],
"weight_threshold": 1
},
"balance": "0.000 STEEM",
"can_vote": true,
"comment_count": 0,
"created": "2017-06-29T06:22:27",
"curation_rewards": 0,
"delegated_vesting_shares": "0.000000 VESTS",
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779058854
},
"guest_bloggers": [],
"id": 232184,
"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": "2019-10-05T06:46:57",
"last_root_post": "2019-10-05T06:46:57",
"last_vote_time": "2019-10-05T10:26:00",
"lifetime_vote_count": 0,
"market_history": [],
"memo_key": "STM6VjWxrAtfr2NtTCRSpVgQXbMqdCadGfGg89L7Hz6PuiA92jyde",
"mined": false,
"name": "cryptojoy",
"next_vesting_withdrawal": "1969-12-31T23:59:59",
"other_history": [],
"owner": {
"account_auths": [],
"key_auths": [
[
"STM4unFJWQhQT7eu2CEyT1Bz8wavb7n685MRD9hGDbgbuVLSpgzrw",
1
]
],
"weight_threshold": 1
},
"pending_claimed_accounts": 0,
"post_bandwidth": 0,
"post_count": 3,
"post_history": [],
"posting": {
"account_auths": [],
"key_auths": [
[
"STM7Hpq6PgwWM6smpRvVxXMvbDaHZoY2e6ED4WEz2RfQLCZeXC4Jw",
1
]
],
"weight_threshold": 1
},
"posting_json_metadata": "",
"posting_rewards": 0,
"proxied_vsf_votes": [
0,
0,
0,
0
],
"proxy": "",
"received_vesting_shares": "7109.141550 VESTS",
"recovery_account": "steem",
"reputation": 21971128,
"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.000 SBD",
"sbd_last_interest_payment": "1970-01-01T00:00:00",
"sbd_seconds": "0",
"sbd_seconds_last_update": "1970-01-01T00:00:00",
"tags_usage": [],
"to_withdraw": 0,
"transfer_history": [],
"vesting_balance": "0.000 STEEM",
"vesting_shares": "1034.518256 VESTS",
"vesting_withdraw_rate": "0.000000 VESTS",
"vote_history": [],
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779058854
},
"voting_power": 0,
"withdraw_routes": 0,
"withdrawn": 0,
"witness_votes": [],
"witnesses_voted_for": 0,
"rank": 1428420
}Withdraw Routes
| Incoming | Outgoing |
|---|---|
Empty | Empty |
{
"incoming": [],
"outgoing": []
}From Date
To Date
steemdelegated 4.366 SP to @cryptojoy2026/05/17 23:00:54
steemdelegated 4.366 SP to @cryptojoy
2026/05/17 23:00:54
| delegatee | cryptojoy |
| delegator | steem |
| vesting shares | 7109.141550 VESTS |
| Transaction Info | Block #106141970/Trx 4f1cba15a3ab23871f9d91a4edfbd6aa47e49574 |
View Raw JSON Data
{
"block": 106141970,
"op": [
"delegate_vesting_shares",
{
"delegatee": "cryptojoy",
"delegator": "steem",
"vesting_shares": "7109.141550 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2026-05-17T23:00:54",
"trx_id": "4f1cba15a3ab23871f9d91a4edfbd6aa47e49574",
"trx_in_block": 3,
"virtual_op": 0
}steemdelegated 2.700 SP to @cryptojoy2026/05/11 22:53:33
steemdelegated 2.700 SP to @cryptojoy
2026/05/11 22:53:33
| delegatee | cryptojoy |
| delegator | steem |
| vesting shares | 4396.931145 VESTS |
| Transaction Info | Block #105969786/Trx 310877edd6905f2aa61b20f2af8a451272f2cb78 |
View Raw JSON Data
{
"block": 105969786,
"op": [
"delegate_vesting_shares",
{
"delegatee": "cryptojoy",
"delegator": "steem",
"vesting_shares": "4396.931145 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2026-05-11T22:53:33",
"trx_id": "310877edd6905f2aa61b20f2af8a451272f2cb78",
"trx_in_block": 1,
"virtual_op": 0
}steemdelegated 4.373 SP to @cryptojoy2026/04/25 22:23:48
steemdelegated 4.373 SP to @cryptojoy
2026/04/25 22:23:48
| delegatee | cryptojoy |
| delegator | steem |
| vesting shares | 7121.657306 VESTS |
| Transaction Info | Block #105509656/Trx 8d2ad59f4d2a30864abd710020b1a4c7986ea32e |
View Raw JSON Data
{
"block": 105509656,
"op": [
"delegate_vesting_shares",
{
"delegatee": "cryptojoy",
"delegator": "steem",
"vesting_shares": "7121.657306 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2026-04-25T22:23:48",
"trx_id": "8d2ad59f4d2a30864abd710020b1a4c7986ea32e",
"trx_in_block": 0,
"virtual_op": 0
}steemdelegated 2.726 SP to @cryptojoy2026/01/23 04:31:00
steemdelegated 2.726 SP to @cryptojoy
2026/01/23 04:31:00
| delegatee | cryptojoy |
| delegator | steem |
| vesting shares | 4438.477964 VESTS |
| Transaction Info | Block #102847876/Trx 765ad1cc66d994614e8cdeaf082dfe15dea5e1d0 |
View Raw JSON Data
{
"block": 102847876,
"op": [
"delegate_vesting_shares",
{
"delegatee": "cryptojoy",
"delegator": "steem",
"vesting_shares": "4438.477964 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2026-01-23T04:31:00",
"trx_id": "765ad1cc66d994614e8cdeaf082dfe15dea5e1d0",
"trx_in_block": 1,
"virtual_op": 0
}steemdelegated 2.827 SP to @cryptojoy2024/12/16 23:50:06
steemdelegated 2.827 SP to @cryptojoy
2024/12/16 23:50:06
| delegatee | cryptojoy |
| delegator | steem |
| vesting shares | 4602.697161 VESTS |
| Transaction Info | Block #91294282/Trx 54748347fafa837ba4a2913206b0aff386ff5ad3 |
View Raw JSON Data
{
"block": 91294282,
"op": [
"delegate_vesting_shares",
{
"delegatee": "cryptojoy",
"delegator": "steem",
"vesting_shares": "4602.697161 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2024-12-16T23:50:06",
"trx_id": "54748347fafa837ba4a2913206b0aff386ff5ad3",
"trx_in_block": 4,
"virtual_op": 0
}steemdelegated 2.930 SP to @cryptojoy2023/11/13 15:34:30
steemdelegated 2.930 SP to @cryptojoy
2023/11/13 15:34:30
| delegatee | cryptojoy |
| delegator | steem |
| vesting shares | 4771.830693 VESTS |
| Transaction Info | Block #79848526/Trx a98426565584699399950b373fb24384b3fc2413 |
View Raw JSON Data
{
"block": 79848526,
"op": [
"delegate_vesting_shares",
{
"delegatee": "cryptojoy",
"delegator": "steem",
"vesting_shares": "4771.830693 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2023-11-13T15:34:30",
"trx_id": "a98426565584699399950b373fb24384b3fc2413",
"trx_in_block": 0,
"virtual_op": 0
}steemdelegated 4.734 SP to @cryptojoy2023/09/21 20:23:06
steemdelegated 4.734 SP to @cryptojoy
2023/09/21 20:23:06
| delegatee | cryptojoy |
| delegator | steem |
| vesting shares | 7709.109479 VESTS |
| Transaction Info | Block #78346102/Trx 69fde71f5cc98481dd63ce63b31dd6f13d09b763 |
View Raw JSON Data
{
"block": 78346102,
"op": [
"delegate_vesting_shares",
{
"delegatee": "cryptojoy",
"delegator": "steem",
"vesting_shares": "7709.109479 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2023-09-21T20:23:06",
"trx_id": "69fde71f5cc98481dd63ce63b31dd6f13d09b763",
"trx_in_block": 1,
"virtual_op": 0
}steemdelegated 4.870 SP to @cryptojoy2022/11/03 10:21:18
steemdelegated 4.870 SP to @cryptojoy
2022/11/03 10:21:18
| delegatee | cryptojoy |
| delegator | steem |
| vesting shares | 7930.790917 VESTS |
| Transaction Info | Block #69111652/Trx 90b2e74d8cd7adf01d4aa7a7501845c2460c380c |
View Raw JSON Data
{
"block": 69111652,
"op": [
"delegate_vesting_shares",
{
"delegatee": "cryptojoy",
"delegator": "steem",
"vesting_shares": "7930.790917 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2022-11-03T10:21:18",
"trx_id": "90b2e74d8cd7adf01d4aa7a7501845c2460c380c",
"trx_in_block": 3,
"virtual_op": 0
}steemdelegated 5.006 SP to @cryptojoy2022/01/17 09:43:48
steemdelegated 5.006 SP to @cryptojoy
2022/01/17 09:43:48
| delegatee | cryptojoy |
| delegator | steem |
| vesting shares | 8151.324148 VESTS |
| Transaction Info | Block #60807950/Trx a04ecdf35f17cfb5560a8e51228b0064f8bcba44 |
View Raw JSON Data
{
"block": 60807950,
"op": [
"delegate_vesting_shares",
{
"delegatee": "cryptojoy",
"delegator": "steem",
"vesting_shares": "8151.324148 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2022-01-17T09:43:48",
"trx_id": "a04ecdf35f17cfb5560a8e51228b0064f8bcba44",
"trx_in_block": 33,
"virtual_op": 0
}steemdelegated 5.119 SP to @cryptojoy2021/06/13 23:41:54
steemdelegated 5.119 SP to @cryptojoy
2021/06/13 23:41:54
| delegatee | cryptojoy |
| delegator | steem |
| vesting shares | 8335.092806 VESTS |
| Transaction Info | Block #54606399/Trx 9cd882058fd3abbd9de2817dfc7bff226c40ce94 |
View Raw JSON Data
{
"block": 54606399,
"op": [
"delegate_vesting_shares",
{
"delegatee": "cryptojoy",
"delegator": "steem",
"vesting_shares": "8335.092806 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2021-06-13T23:41:54",
"trx_id": "9cd882058fd3abbd9de2817dfc7bff226c40ce94",
"trx_in_block": 41,
"virtual_op": 0
}steemdelegated 5.234 SP to @cryptojoy2020/12/11 10:02:30
steemdelegated 5.234 SP to @cryptojoy
2020/12/11 10:02:30
| delegatee | cryptojoy |
| delegator | steem |
| vesting shares | 8522.514780 VESTS |
| Transaction Info | Block #49353903/Trx edc76f76f2abd203596125f50bbd2c7164420abd |
View Raw JSON Data
{
"block": 49353903,
"op": [
"delegate_vesting_shares",
{
"delegatee": "cryptojoy",
"delegator": "steem",
"vesting_shares": "8522.514780 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-12-11T10:02:30",
"trx_id": "edc76f76f2abd203596125f50bbd2c7164420abd",
"trx_in_block": 6,
"virtual_op": 0
}steemdelegated 1.175 SP to @cryptojoy2020/12/06 03:39:36
steemdelegated 1.175 SP to @cryptojoy
2020/12/06 03:39:36
| delegatee | cryptojoy |
| delegator | steem |
| vesting shares | 1912.543513 VESTS |
| Transaction Info | Block #49205467/Trx 2e27eeb5f51178b4a46cd8f633fff16d975231e3 |
View Raw JSON Data
{
"block": 49205467,
"op": [
"delegate_vesting_shares",
{
"delegatee": "cryptojoy",
"delegator": "steem",
"vesting_shares": "1912.543513 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-12-06T03:39:36",
"trx_id": "2e27eeb5f51178b4a46cd8f633fff16d975231e3",
"trx_in_block": 9,
"virtual_op": 0
}steemdelegated 5.238 SP to @cryptojoy2020/12/05 11:36:54
steemdelegated 5.238 SP to @cryptojoy
2020/12/05 11:36:54
| delegatee | cryptojoy |
| delegator | steem |
| vesting shares | 8528.881419 VESTS |
| Transaction Info | Block #49186575/Trx 7dff89f6d0e51a937d164000440a44055ae920cc |
View Raw JSON Data
{
"block": 49186575,
"op": [
"delegate_vesting_shares",
{
"delegatee": "cryptojoy",
"delegator": "steem",
"vesting_shares": "8528.881419 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-12-05T11:36:54",
"trx_id": "7dff89f6d0e51a937d164000440a44055ae920cc",
"trx_in_block": 2,
"virtual_op": 0
}steemdelegated 1.179 SP to @cryptojoy2020/11/02 13:13:18
steemdelegated 1.179 SP to @cryptojoy
2020/11/02 13:13:18
| delegatee | cryptojoy |
| delegator | steem |
| vesting shares | 1920.017158 VESTS |
| Transaction Info | Block #48254958/Trx afc259b10946df50da08d190ccf2013f14b9190c |
View Raw JSON Data
{
"block": 48254958,
"op": [
"delegate_vesting_shares",
{
"delegatee": "cryptojoy",
"delegator": "steem",
"vesting_shares": "1920.017158 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-11-02T13:13:18",
"trx_id": "afc259b10946df50da08d190ccf2013f14b9190c",
"trx_in_block": 5,
"virtual_op": 0
}steemdelegated 5.362 SP to @cryptojoy2020/05/09 04:35:51
steemdelegated 5.362 SP to @cryptojoy
2020/05/09 04:35:51
| delegatee | cryptojoy |
| delegator | steem |
| vesting shares | 8731.527993 VESTS |
| Transaction Info | Block #43215700/Trx 50c75149e3ec19e44f17e69ff5ad2f57e751fa30 |
View Raw JSON Data
{
"block": 43215700,
"op": [
"delegate_vesting_shares",
{
"delegatee": "cryptojoy",
"delegator": "steem",
"vesting_shares": "8731.527993 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-05-09T04:35:51",
"trx_id": "50c75149e3ec19e44f17e69ff5ad2f57e751fa30",
"trx_in_block": 4,
"virtual_op": 0
}steemdelegated 1.200 SP to @cryptojoy2020/05/08 08:02:06
steemdelegated 1.200 SP to @cryptojoy
2020/05/08 08:02:06
| delegatee | cryptojoy |
| delegator | steem |
| vesting shares | 1953.311140 VESTS |
| Transaction Info | Block #43191601/Trx a2482379a0ad739d3d36622d8a9fb482a43ba8ea |
View Raw JSON Data
{
"block": 43191601,
"op": [
"delegate_vesting_shares",
{
"delegatee": "cryptojoy",
"delegator": "steem",
"vesting_shares": "1953.311140 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-05-08T08:02:06",
"trx_id": "a2482379a0ad739d3d36622d8a9fb482a43ba8ea",
"trx_in_block": 6,
"virtual_op": 0
}mayanknupvoted (100.00%) @cryptojoy / fast-download-torrent-files-without-torrent-client2020/04/04 11:18:09
mayanknupvoted (100.00%) @cryptojoy / fast-download-torrent-files-without-torrent-client
2020/04/04 11:18:09
| author | cryptojoy |
| permlink | fast-download-torrent-files-without-torrent-client |
| voter | mayankn |
| weight | 10000 (100.00%) |
| Transaction Info | Block #42241026/Trx efc9ded7a83c790e03a0b8519ae6f0943e905bcf |
View Raw JSON Data
{
"block": 42241026,
"op": [
"vote",
{
"author": "cryptojoy",
"permlink": "fast-download-torrent-files-without-torrent-client",
"voter": "mayankn",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2020-04-04T11:18:09",
"trx_id": "efc9ded7a83c790e03a0b8519ae6f0943e905bcf",
"trx_in_block": 9,
"virtual_op": 0
}steemdelegated 5.404 SP to @cryptojoy2020/01/04 11:30:33
steemdelegated 5.404 SP to @cryptojoy
2020/01/04 11:30:33
| delegatee | cryptojoy |
| delegator | steem |
| vesting shares | 8800.099621 VESTS |
| Transaction Info | Block #39632363/Trx 7539587a31c34f45b0adbdc80b9a0eabf556f77c |
View Raw JSON Data
{
"block": 39632363,
"op": [
"delegate_vesting_shares",
{
"delegatee": "cryptojoy",
"delegator": "steem",
"vesting_shares": "8800.099621 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-01-04T11:30:33",
"trx_id": "7539587a31c34f45b0adbdc80b9a0eabf556f77c",
"trx_in_block": 9,
"virtual_op": 0
}cryptojoyremoved vote from (0.00%) @cryptojoy / fast-download-torrent-files-without-torrent-client2019/10/05 10:26:00
cryptojoyremoved vote from (0.00%) @cryptojoy / fast-download-torrent-files-without-torrent-client
2019/10/05 10:26:00
| author | cryptojoy |
| permlink | fast-download-torrent-files-without-torrent-client |
| voter | cryptojoy |
| weight | 0 (0.00%) |
| Transaction Info | Block #37015257/Trx 2bcbdf1a48de7e5b0ef7c9ebe13707674362d053 |
View Raw JSON Data
{
"block": 37015257,
"op": [
"vote",
{
"author": "cryptojoy",
"permlink": "fast-download-torrent-files-without-torrent-client",
"voter": "cryptojoy",
"weight": 0
}
],
"op_in_trx": 0,
"timestamp": "2019-10-05T10:26:00",
"trx_id": "2bcbdf1a48de7e5b0ef7c9ebe13707674362d053",
"trx_in_block": 13,
"virtual_op": 0
}cryptojoyupvoted (100.00%) @cryptojoy / fast-download-torrent-files-without-torrent-client2019/10/05 10:25:45
cryptojoyupvoted (100.00%) @cryptojoy / fast-download-torrent-files-without-torrent-client
2019/10/05 10:25:45
| author | cryptojoy |
| permlink | fast-download-torrent-files-without-torrent-client |
| voter | cryptojoy |
| weight | 10000 (100.00%) |
| Transaction Info | Block #37015252/Trx 3a85f5dc8f64a2479b7f15018db4857bbd95e559 |
View Raw JSON Data
{
"block": 37015252,
"op": [
"vote",
{
"author": "cryptojoy",
"permlink": "fast-download-torrent-files-without-torrent-client",
"voter": "cryptojoy",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2019-10-05T10:25:45",
"trx_id": "3a85f5dc8f64a2479b7f15018db4857bbd95e559",
"trx_in_block": 2,
"virtual_op": 0
}steemdelegated 17.900 SP to @cryptojoy2019/10/05 07:57:30
steemdelegated 17.900 SP to @cryptojoy
2019/10/05 07:57:30
| delegatee | cryptojoy |
| delegator | steem |
| vesting shares | 29147.953101 VESTS |
| Transaction Info | Block #37012292/Trx 04874bd172dcd2ddc4f52480d0da994747226d87 |
View Raw JSON Data
{
"block": 37012292,
"op": [
"delegate_vesting_shares",
{
"delegatee": "cryptojoy",
"delegator": "steem",
"vesting_shares": "29147.953101 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2019-10-05T07:57:30",
"trx_id": "04874bd172dcd2ddc4f52480d0da994747226d87",
"trx_in_block": 8,
"virtual_op": 0
}cryptojoypublished a new post: fast-download-torrent-files-without-torrent-client2019/10/05 06:51:54
cryptojoypublished a new post: fast-download-torrent-files-without-torrent-client
2019/10/05 06:51:54
| author | cryptojoy |
| body | @@ -1,13 +1,34 @@ -D +Facing difficulty in d ownloading T @@ -26,24 +26,16 @@ loading -Torrent files wi @@ -95,45 +95,12 @@ tc.) - could be messy sometimes. Also, in s +? S ome @@ -171,39 +171,8 @@ is, -Torrent clients don't works and res @@ -208,19 +208,27 @@ les -via +with Torrent + client . So @@ -315,25 +315,23 @@ with - your Web Browser +out any hassles .%0A%0A1 |
| json metadata | {"tags":["seedr","cloud","storage","direct","download","fast","free"],"links":["https://www.seedr.cc/?r=2846615","https://www.seedr.cc/subscription"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | torrent |
| permlink | fast-download-torrent-files-without-torrent-client |
| title | Fast download Torrent files without Torrent Client |
| Transaction Info | Block #37010983/Trx acf91c5ec75e390b52bb8d1b1bedccd3a7efd139 |
View Raw JSON Data
{
"block": 37010983,
"op": [
"comment",
{
"author": "cryptojoy",
"body": "@@ -1,13 +1,34 @@\n-D\n+Facing difficulty in d\n ownloading T\n@@ -26,24 +26,16 @@\n loading \n-Torrent \n files wi\n@@ -95,45 +95,12 @@\n tc.)\n- could be messy sometimes. Also, in s\n+? S\n ome \n@@ -171,39 +171,8 @@\n is, \n-Torrent clients don't works and\n res\n@@ -208,19 +208,27 @@\n les \n-via\n+with\n Torrent\n+ client\n . So\n@@ -315,25 +315,23 @@\n with\n- your Web Browser\n+out any hassles\n .%0A%0A1\n",
"json_metadata": "{\"tags\":[\"seedr\",\"cloud\",\"storage\",\"direct\",\"download\",\"fast\",\"free\"],\"links\":[\"https://www.seedr.cc/?r=2846615\",\"https://www.seedr.cc/subscription\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "torrent",
"permlink": "fast-download-torrent-files-without-torrent-client",
"title": "Fast download Torrent files without Torrent Client"
}
],
"op_in_trx": 0,
"timestamp": "2019-10-05T06:51:54",
"trx_id": "acf91c5ec75e390b52bb8d1b1bedccd3a7efd139",
"trx_in_block": 6,
"virtual_op": 0
}cryptojoypublished a new post: fast-download-torrent-files-without-torrent-client2019/10/05 06:46:57
cryptojoypublished a new post: fast-download-torrent-files-without-torrent-client
2019/10/05 06:46:57
| author | cryptojoy |
| body | Downloading Torrent files with torrent client (like uTorrent, qBittorent Deluge,etc.) could be messy sometimes. Also, in some Wifi networks with firewall protection like those of College Wifis, Torrent clients don't works and restrict you from downloading files via Torrent. So in this post I am going to explain how you can download torrent files directly with your Web Browser. 1. Register on Seedr.cc by clicking <a href="https://www.seedr.cc/?r=2846615">here</a> 2. Login to Seedr.cc 3. Copy magnet URI of the torrent file or any other file and paste it in the field saying "Paste link URL" followed by pressing "+" button and the respective file will soon be downloaded the Seedr cloud. 4. After the file has been successfully downloaded to the cloud the file can be dowloaded directly from your web browser or Download Managers. The cloud storage capacity has been restricted upto 2GB for Non-premium accounts (by default) which can further be extended upto 6GB by doing certain tasks.If you further want to extend the storage capacity beyond 6GB you can check <a href="https://www.seedr.cc/subscription"> Subscription Plans </A> |
| json metadata | {"tags":["torrent","seedr","cloud","storage","direct","download","fast","free"],"links":["https://www.seedr.cc/?r=2846615","https://www.seedr.cc/subscription"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | torrent |
| permlink | fast-download-torrent-files-without-torrent-client |
| title | Fast download Torrent files without Torrent Client |
| Transaction Info | Block #37010884/Trx 1b680eb4d5529386dd3f4a87747a6a2a143521f4 |
View Raw JSON Data
{
"block": 37010884,
"op": [
"comment",
{
"author": "cryptojoy",
"body": "Downloading Torrent files with torrent client (like uTorrent, qBittorent Deluge,etc.) could be messy sometimes. Also, in some Wifi networks with firewall protection like those of College Wifis, Torrent clients don't works and restrict you from downloading files via Torrent. So in this post I am going to explain how you can download torrent files directly with your Web Browser.\n\n1. Register on Seedr.cc by clicking <a href=\"https://www.seedr.cc/?r=2846615\">here</a>\n2. Login to Seedr.cc\n3. Copy magnet URI of the torrent file or any other file and paste it in the field saying \"Paste link URL\" followed by pressing \"+\" button and the respective file will soon be downloaded the Seedr cloud.\n4. After the file has been successfully downloaded to the cloud the file can be dowloaded directly from your web browser or Download Managers.\n\nThe cloud storage capacity has been restricted upto 2GB for Non-premium accounts (by default) which can further be extended upto 6GB by doing certain tasks.If you further want to extend the storage capacity beyond 6GB you can check <a href=\"https://www.seedr.cc/subscription\"> Subscription Plans </A>",
"json_metadata": "{\"tags\":[\"torrent\",\"seedr\",\"cloud\",\"storage\",\"direct\",\"download\",\"fast\",\"free\"],\"links\":[\"https://www.seedr.cc/?r=2846615\",\"https://www.seedr.cc/subscription\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "torrent",
"permlink": "fast-download-torrent-files-without-torrent-client",
"title": "Fast download Torrent files without Torrent Client"
}
],
"op_in_trx": 0,
"timestamp": "2019-10-05T06:46:57",
"trx_id": "1b680eb4d5529386dd3f4a87747a6a2a143521f4",
"trx_in_block": 13,
"virtual_op": 0
}steemdelegated 5.463 SP to @cryptojoy2019/07/26 23:10:00
steemdelegated 5.463 SP to @cryptojoy
2019/07/26 23:10:00
| delegatee | cryptojoy |
| delegator | steem |
| vesting shares | 8896.010686 VESTS |
| Transaction Info | Block #35012441/Trx aa5b689d963cf41208090e0014aad9f85a425713 |
View Raw JSON Data
{
"block": 35012441,
"op": [
"delegate_vesting_shares",
{
"delegatee": "cryptojoy",
"delegator": "steem",
"vesting_shares": "8896.010686 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2019-07-26T23:10:00",
"trx_id": "aa5b689d963cf41208090e0014aad9f85a425713",
"trx_in_block": 16,
"virtual_op": 0
}2019/06/29 07:42:48
2019/06/29 07:42:48
| author | steemitboard |
| body | Congratulations @cryptojoy! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@cryptojoy/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/@cryptojoy) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=cryptojoy)_</sub> ###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| parent author | cryptojoy |
| parent permlink | crypto-airdrop |
| permlink | steemitboard-notify-cryptojoy-20190629t074247000z |
| title | |
| Transaction Info | Block #34217648/Trx 3637ae35e07e741340cb9ef6b3a8d1b25d3586d6 |
View Raw JSON Data
{
"block": 34217648,
"op": [
"comment",
{
"author": "steemitboard",
"body": "Congratulations @cryptojoy! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@cryptojoy/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/@cryptojoy) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=cryptojoy)_</sub>\n\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}",
"parent_author": "cryptojoy",
"parent_permlink": "crypto-airdrop",
"permlink": "steemitboard-notify-cryptojoy-20190629t074247000z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2019-06-29T07:42:48",
"trx_id": "3637ae35e07e741340cb9ef6b3a8d1b25d3586d6",
"trx_in_block": 5,
"virtual_op": 0
}steemdelegated 5.585 SP to @cryptojoy2018/08/09 09:12:30
steemdelegated 5.585 SP to @cryptojoy
2018/08/09 09:12:30
| delegatee | cryptojoy |
| delegator | steem |
| vesting shares | 9094.650816 VESTS |
| Transaction Info | Block #24912413/Trx 6f34f793333332566aa5d526ba88a7e7575b5b7d |
View Raw JSON Data
{
"block": 24912413,
"op": [
"delegate_vesting_shares",
{
"delegatee": "cryptojoy",
"delegator": "steem",
"vesting_shares": "9094.650816 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2018-08-09T09:12:30",
"trx_id": "6f34f793333332566aa5d526ba88a7e7575b5b7d",
"trx_in_block": 15,
"virtual_op": 0
}2018/06/29 09:14:42
2018/06/29 09:14:42
| author | steemitboard |
| body | Congratulations @cryptojoy! You have received a personal award! [](http://steemitboard.com/@cryptojoy) 1 Year on Steemit <sub>_Click on the badge to view your Board of Honor._</sub> **Do not miss the [last post](https://steemit.com/steemitboard/@steemitboard/7mkfjh-steemitboard-world-cup-contest-results-of-day-14) from @steemitboard!** --- **Participate in the [SteemitBoard World Cup Contest](https://steemit.com/steemitboard/@steemitboard/steemitboard-world-cup-contest-collect-badges-and-win-free-sbd)!** Collect World Cup badges and win free SBD Support the Gold Sponsors of the contest: [@good-karma](https://v2.steemconnect.com/sign/account-witness-vote?witness=good-karma&approve=1) and [@lukestokes](https://v2.steemconnect.com/sign/account-witness-vote?witness=lukestokes.mhth&approve=1) --- > Do you like [SteemitBoard's project](https://steemit.com/@steemitboard)? Then **[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 | cryptojoy |
| parent permlink | crypto-airdrop |
| permlink | steemitboard-notify-cryptojoy-20180629t091442000z |
| title | |
| Transaction Info | Block #23742520/Trx 1ad946b70c9d1c36b797666842faa0d17656cb98 |
View Raw JSON Data
{
"block": 23742520,
"op": [
"comment",
{
"author": "steemitboard",
"body": "Congratulations @cryptojoy! You have received a personal award!\n\n[](http://steemitboard.com/@cryptojoy) 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](https://steemit.com/steemitboard/@steemitboard/7mkfjh-steemitboard-world-cup-contest-results-of-day-14) from @steemitboard!**\n\n---\n**Participate in the [SteemitBoard World Cup Contest](https://steemit.com/steemitboard/@steemitboard/steemitboard-world-cup-contest-collect-badges-and-win-free-sbd)!**\nCollect World Cup badges and win free SBD\nSupport the Gold Sponsors of the contest: [@good-karma](https://v2.steemconnect.com/sign/account-witness-vote?witness=good-karma&approve=1) and [@lukestokes](https://v2.steemconnect.com/sign/account-witness-vote?witness=lukestokes.mhth&approve=1)\n\n---\n\n> Do you like [SteemitBoard's project](https://steemit.com/@steemitboard)? Then **[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": "cryptojoy",
"parent_permlink": "crypto-airdrop",
"permlink": "steemitboard-notify-cryptojoy-20180629t091442000z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2018-06-29T09:14:42",
"trx_id": "1ad946b70c9d1c36b797666842faa0d17656cb98",
"trx_in_block": 7,
"virtual_op": 0
}steemdelegated 18.107 SP to @cryptojoy2018/05/18 19:04:36
steemdelegated 18.107 SP to @cryptojoy
2018/05/18 19:04:36
| delegatee | cryptojoy |
| delegator | steem |
| vesting shares | 29485.001669 VESTS |
| Transaction Info | Block #22545984/Trx 45f845963897675839ae5e97c7e2f4eb6a763aa3 |
View Raw JSON Data
{
"block": 22545984,
"op": [
"delegate_vesting_shares",
{
"delegatee": "cryptojoy",
"delegator": "steem",
"vesting_shares": "29485.001669 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2018-05-18T19:04:36",
"trx_id": "45f845963897675839ae5e97c7e2f4eb6a763aa3",
"trx_in_block": 3,
"virtual_op": 0
}cryptojoyupvoted (100.00%) @quarkchain / quarkchain-whitelisting-kyc-process2018/05/10 09:10:18
cryptojoyupvoted (100.00%) @quarkchain / quarkchain-whitelisting-kyc-process
2018/05/10 09:10:18
| author | quarkchain |
| permlink | quarkchain-whitelisting-kyc-process |
| voter | cryptojoy |
| weight | 10000 (100.00%) |
| Transaction Info | Block #22303728/Trx 2be26f53768076405fd65227af983603d7b0a58a |
View Raw JSON Data
{
"block": 22303728,
"op": [
"vote",
{
"author": "quarkchain",
"permlink": "quarkchain-whitelisting-kyc-process",
"voter": "cryptojoy",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-05-10T09:10:18",
"trx_id": "2be26f53768076405fd65227af983603d7b0a58a",
"trx_in_block": 7,
"virtual_op": 0
}2018/02/13 22:55:27
2018/02/13 22:55:27
| author | welovespace |
| body | new website collecting information about Crypto Token Airdrops: www.airdroptracker.co |
| json metadata | {"tags":["cryptocurrency"],"app":"steemit/0.1"} |
| parent author | cryptojoy |
| parent permlink | crypto-airdrop |
| permlink | re-cryptojoy-crypto-airdrop-20180213t225528651z |
| title | |
| Transaction Info | Block #19846079/Trx 532e153d5d85df93db82813bb08b3d63356a11bc |
View Raw JSON Data
{
"block": 19846079,
"op": [
"comment",
{
"author": "welovespace",
"body": "new website collecting information about Crypto Token Airdrops: www.airdroptracker.co",
"json_metadata": "{\"tags\":[\"cryptocurrency\"],\"app\":\"steemit/0.1\"}",
"parent_author": "cryptojoy",
"parent_permlink": "crypto-airdrop",
"permlink": "re-cryptojoy-crypto-airdrop-20180213t225528651z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2018-02-13T22:55:27",
"trx_id": "532e153d5d85df93db82813bb08b3d63356a11bc",
"trx_in_block": 39,
"virtual_op": 0
}2018/02/12 17:13:24
2018/02/12 17:13:24
| author | pssf84 |
| body | Great post! I Upvoted and followed. Do the same and we can support one another. |
| json metadata | {"tags":["cryptocurrency"],"app":"steemit/0.1"} |
| parent author | cryptojoy |
| parent permlink | crypto-airdrop |
| permlink | re-cryptojoy-crypto-airdrop-20180212t171324892z |
| title | |
| Transaction Info | Block #19810469/Trx 5010e3bbc86e1457d4973d55780b3191b6d020a9 |
View Raw JSON Data
{
"block": 19810469,
"op": [
"comment",
{
"author": "pssf84",
"body": "Great post! I Upvoted and followed. Do the same and we can support one another.",
"json_metadata": "{\"tags\":[\"cryptocurrency\"],\"app\":\"steemit/0.1\"}",
"parent_author": "cryptojoy",
"parent_permlink": "crypto-airdrop",
"permlink": "re-cryptojoy-crypto-airdrop-20180212t171324892z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2018-02-12T17:13:24",
"trx_id": "5010e3bbc86e1457d4973d55780b3191b6d020a9",
"trx_in_block": 53,
"virtual_op": 0
}pssf84upvoted (100.00%) @cryptojoy / crypto-airdrop2018/02/12 17:04:39
pssf84upvoted (100.00%) @cryptojoy / crypto-airdrop
2018/02/12 17:04:39
| author | cryptojoy |
| permlink | crypto-airdrop |
| voter | pssf84 |
| weight | 10000 (100.00%) |
| Transaction Info | Block #19810295/Trx 7cbed73a0a4d9bc80cd954da2061e4f1ff31e02b |
View Raw JSON Data
{
"block": 19810295,
"op": [
"vote",
{
"author": "cryptojoy",
"permlink": "crypto-airdrop",
"voter": "pssf84",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-02-12T17:04:39",
"trx_id": "7cbed73a0a4d9bc80cd954da2061e4f1ff31e02b",
"trx_in_block": 15,
"virtual_op": 0
}cryptojoyupdated options for crypto-airdrop2018/02/12 15:32:42
cryptojoyupdated options for crypto-airdrop
2018/02/12 15:32:42
| allow curation rewards | true |
| allow votes | true |
| author | cryptojoy |
| extensions | [] |
| max accepted payout | 1000000.000 SBD |
| percent steem dollars | 0 |
| permlink | crypto-airdrop |
| Transaction Info | Block #19808458/Trx 8c9513f698f33c30c9cded1c356433fd2dbfc69d |
View Raw JSON Data
{
"block": 19808458,
"op": [
"comment_options",
{
"allow_curation_rewards": true,
"allow_votes": true,
"author": "cryptojoy",
"extensions": [],
"max_accepted_payout": "1000000.000 SBD",
"percent_steem_dollars": 0,
"permlink": "crypto-airdrop"
}
],
"op_in_trx": 0,
"timestamp": "2018-02-12T15:32:42",
"trx_id": "8c9513f698f33c30c9cded1c356433fd2dbfc69d",
"trx_in_block": 4,
"virtual_op": 0
}cryptojoypublished a new post: crypto-airdrop2018/02/12 15:32:42
cryptojoypublished a new post: crypto-airdrop
2018/02/12 15:32:42
| author | cryptojoy |
| body | Get free 36 ALP tokens 1 First open this link : http://bit.ly/2G5gfFu 2 Paste your ERC20 compatible ETH address 3 Then follow instructions obtained upon putting ETH address |
| json metadata | {"tags":["cryptocurrency","bitcoin","ethereum","airdrop","giveaway"],"links":["http://bit.ly/2G5gfFu"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | cryptocurrency |
| permlink | crypto-airdrop |
| title | Crypto Airdrop |
| Transaction Info | Block #19808458/Trx 8c9513f698f33c30c9cded1c356433fd2dbfc69d |
View Raw JSON Data
{
"block": 19808458,
"op": [
"comment",
{
"author": "cryptojoy",
"body": "Get free 36 ALP tokens\n\n1 First open this link : http://bit.ly/2G5gfFu\n2 Paste your ERC20 compatible ETH address\n3 Then follow instructions obtained upon putting ETH address",
"json_metadata": "{\"tags\":[\"cryptocurrency\",\"bitcoin\",\"ethereum\",\"airdrop\",\"giveaway\"],\"links\":[\"http://bit.ly/2G5gfFu\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "cryptocurrency",
"permlink": "crypto-airdrop",
"title": "Crypto Airdrop"
}
],
"op_in_trx": 0,
"timestamp": "2018-02-12T15:32:42",
"trx_id": "8c9513f698f33c30c9cded1c356433fd2dbfc69d",
"trx_in_block": 4,
"virtual_op": 0
}steemdelegated 18.233 SP to @cryptojoy2018/01/09 06:36:39
steemdelegated 18.233 SP to @cryptojoy
2018/01/09 06:36:39
| delegatee | cryptojoy |
| delegator | steem |
| vesting shares | 29690.671036 VESTS |
| Transaction Info | Block #18819533/Trx 1ccb079035cc41e8a1cc993459bd3f1ff13eda01 |
View Raw JSON Data
{
"block": 18819533,
"op": [
"delegate_vesting_shares",
{
"delegatee": "cryptojoy",
"delegator": "steem",
"vesting_shares": "29690.671036 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2018-01-09T06:36:39",
"trx_id": "1ccb079035cc41e8a1cc993459bd3f1ff13eda01",
"trx_in_block": 29,
"virtual_op": 0
}2017/10/29 18:25:48
2017/10/29 18:25:48
| author | steemitboard |
| body | Congratulations @cryptojoy! You have completed some achievement on Steemit and have been rewarded with new badge(s) : [](http://steemitboard.com/@cryptojoy) You made your First Vote Click on any badge to view your own Board of Honor on SteemitBoard. For more information about SteemitBoard, click [here](https://steemit.com/@steemitboard) If you no longer want to receive notifications, reply to this comment with the word `STOP` > 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 | cryptojoy |
| parent permlink | a-bitcoin-beginner-s-guide-to-surviving-the-bgold-and-segwit2x-forks |
| permlink | steemitboard-notify-cryptojoy-20171029t182550000z |
| title | |
| Transaction Info | Block #16761276/Trx 34471ae054769dcaf84b2bb80d35cd8e2a1c80bf |
View Raw JSON Data
{
"block": 16761276,
"op": [
"comment",
{
"author": "steemitboard",
"body": "Congratulations @cryptojoy! You have completed some achievement on Steemit and have been rewarded with new badge(s) :\n\n[](http://steemitboard.com/@cryptojoy) You made your First Vote\n\nClick on any badge to view your own Board of Honor on SteemitBoard.\nFor more information about SteemitBoard, click [here](https://steemit.com/@steemitboard)\n\nIf you no longer want to receive notifications, reply to this comment with the word `STOP`\n\n> 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": "cryptojoy",
"parent_permlink": "a-bitcoin-beginner-s-guide-to-surviving-the-bgold-and-segwit2x-forks",
"permlink": "steemitboard-notify-cryptojoy-20171029t182550000z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2017-10-29T18:25:48",
"trx_id": "34471ae054769dcaf84b2bb80d35cd8e2a1c80bf",
"trx_in_block": 38,
"virtual_op": 0
}2017/10/29 05:15:00
2017/10/29 05:15:00
| author | cryptojoy |
| permlink | a-bitcoin-beginner-s-guide-to-surviving-the-bgold-and-segwit2x-forks |
| voter | cryptojoy |
| weight | 10000 (100.00%) |
| Transaction Info | Block #16745460/Trx 105ae8d2aca9997754adff1aa14d1d937526267e |
View Raw JSON Data
{
"block": 16745460,
"op": [
"vote",
{
"author": "cryptojoy",
"permlink": "a-bitcoin-beginner-s-guide-to-surviving-the-bgold-and-segwit2x-forks",
"voter": "cryptojoy",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-10-29T05:15:00",
"trx_id": "105ae8d2aca9997754adff1aa14d1d937526267e",
"trx_in_block": 5,
"virtual_op": 0
}2017/10/18 10:20:54
2017/10/18 10:20:54
| author | cryptojoy |
| permlink | a-bitcoin-beginner-s-guide-to-surviving-the-bgold-and-segwit2x-forks |
| voter | ibrarasp |
| weight | 10000 (100.00%) |
| Transaction Info | Block #16434961/Trx 3eb7b52da5912f1794a10dec16e3c286a2346dee |
View Raw JSON Data
{
"block": 16434961,
"op": [
"vote",
{
"author": "cryptojoy",
"permlink": "a-bitcoin-beginner-s-guide-to-surviving-the-bgold-and-segwit2x-forks",
"voter": "ibrarasp",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-10-18T10:20:54",
"trx_id": "3eb7b52da5912f1794a10dec16e3c286a2346dee",
"trx_in_block": 2,
"virtual_op": 0
}2017/10/18 10:19:48
2017/10/18 10:19:48
| author | cheetah |
| body | Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in: https://bitcoinmagazine.com/articles/bitcoin-beginners-guide-surviving-bgold-and-segwit2x-forks/ |
| json metadata | |
| parent author | cryptojoy |
| parent permlink | a-bitcoin-beginner-s-guide-to-surviving-the-bgold-and-segwit2x-forks |
| permlink | cheetah-re-cryptojoya-bitcoin-beginner-s-guide-to-surviving-the-bgold-and-segwit2x-forks |
| title | |
| Transaction Info | Block #16434939/Trx 4a8b6b4d9070c3093fb5dd9d3990f22dd140b24a |
View Raw JSON Data
{
"block": 16434939,
"op": [
"comment",
{
"author": "cheetah",
"body": "Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in:\nhttps://bitcoinmagazine.com/articles/bitcoin-beginners-guide-surviving-bgold-and-segwit2x-forks/",
"json_metadata": "",
"parent_author": "cryptojoy",
"parent_permlink": "a-bitcoin-beginner-s-guide-to-surviving-the-bgold-and-segwit2x-forks",
"permlink": "cheetah-re-cryptojoya-bitcoin-beginner-s-guide-to-surviving-the-bgold-and-segwit2x-forks",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2017-10-18T10:19:48",
"trx_id": "4a8b6b4d9070c3093fb5dd9d3990f22dd140b24a",
"trx_in_block": 6,
"virtual_op": 0
}2017/10/18 10:19:42
2017/10/18 10:19:42
| author | cryptojoy |
| permlink | a-bitcoin-beginner-s-guide-to-surviving-the-bgold-and-segwit2x-forks |
| voter | cheetah |
| weight | 50 (0.50%) |
| Transaction Info | Block #16434937/Trx 235e97a6751e297086ee8ac4445c43458c37aa5c |
View Raw JSON Data
{
"block": 16434937,
"op": [
"vote",
{
"author": "cryptojoy",
"permlink": "a-bitcoin-beginner-s-guide-to-surviving-the-bgold-and-segwit2x-forks",
"voter": "cheetah",
"weight": 50
}
],
"op_in_trx": 0,
"timestamp": "2017-10-18T10:19:42",
"trx_id": "235e97a6751e297086ee8ac4445c43458c37aa5c",
"trx_in_block": 13,
"virtual_op": 0
}cryptojoyupdated options for a-bitcoin-beginner-s-guide-to-surviving-the-bgold-and-segwit2x-forks2017/10/18 10:19:30
cryptojoyupdated options for a-bitcoin-beginner-s-guide-to-surviving-the-bgold-and-segwit2x-forks
2017/10/18 10:19:30
| allow curation rewards | true |
| allow votes | true |
| author | cryptojoy |
| extensions | [] |
| max accepted payout | 1000000.000 SBD |
| percent steem dollars | 0 |
| permlink | a-bitcoin-beginner-s-guide-to-surviving-the-bgold-and-segwit2x-forks |
| Transaction Info | Block #16434933/Trx 690e50368076018c9c11899bfa14a00c2b933350 |
View Raw JSON Data
{
"block": 16434933,
"op": [
"comment_options",
{
"allow_curation_rewards": true,
"allow_votes": true,
"author": "cryptojoy",
"extensions": [],
"max_accepted_payout": "1000000.000 SBD",
"percent_steem_dollars": 0,
"permlink": "a-bitcoin-beginner-s-guide-to-surviving-the-bgold-and-segwit2x-forks"
}
],
"op_in_trx": 0,
"timestamp": "2017-10-18T10:19:30",
"trx_id": "690e50368076018c9c11899bfa14a00c2b933350",
"trx_in_block": 8,
"virtual_op": 0
}cryptojoypublished a new post: a-bitcoin-beginner-s-guide-to-surviving-the-bgold-and-segwit2x-forks2017/10/18 10:19:30
cryptojoypublished a new post: a-bitcoin-beginner-s-guide-to-surviving-the-bgold-and-segwit2x-forks
2017/10/18 10:19:30
| author | cryptojoy |
| body | <html> <p><code>Source: </code><a href="www.bitcoinmagazine.com"><code>bitcoinmagazine</code></a></p> <p><code>Please upvote the post if you like it.</code></p> <p><img src="https://fs.bitcoinmagazine.com/img/images/coin-split2xgold.width-800.jpg" width="800" height="448"/></p> <h3> It looks as if Bitcoin will experience at least two more “coin-splits” soon, which (more accurately) will result in the creation of new coins. On October 25,<a href="https://bitcoinmagazine.com/articles/bitcoin-gold-about-trial-asic-resistant-bitcoin-fork/"> Bitcoin Gold</a> (Bgold) will split off from Bitcoin to create an ASIC-resistant cryptocurrency. A few weeks later, a significant group of Bitcoin companies wants to hard fork according to the<a href="https://bitcoinmagazine.com/articles/2x-or-no2x-why-some-want-hard-fork-bitcoin-november-and-why-others-dont/"> SegWit2x</a> plan as defined in the “<a href="https://medium.com/@DCGco/bitcoin-scaling-agreement-at-consensus-2017-133521fe9a77">New York Agreement</a>” (NYA), which will probably result in yet another new coin.If this all plays out, there could be three distinct blockchains and three types of coins within about a month of publication of this article. One blockchain would follow the current Bitcoin protocol; for the purpose of this article, that coin will be referred to as “BTC.” The second blockchain will follow the Bgold protocol; in this article, that coin will be referred to as “BTG.” The third blockchain will follow the SegWit2x protocol; that coin will be referred to as “B2X.”The good news is that each BTC will effectively be copied onto both the Bgold and the SegWit2x blockchains. If you hold Bitcoin private keys at the time of the forks, you should be able to access your BTG and B2X coins as well.The bad news is that such forks can be somewhat messy and risky. If you’re not careful, it’s easy to lose your BTC or B2X, and maybe your BTG.This guide will provide you with the basics to keep your funds safe during the upcoming forks and help to ensure you make it to the end of next month with your BTC, BTG and B2X intact.<em>Author’s note: If you want to play the markets as soon as possible and you are fine with taking risks, and/or you really know what you are doing, this article is probably not for you: it's a beginner's guide. Also please note that everything in this article is just advise, based on our best understanding of the situation. Much is still uncertain and subject to change.</em> </h3> <h1> Before the Forks (That’s Now)</h1> <h3> First of all, be aware that coin-splits can be somewhat risky — especially controversial ones like the SegWit2x fork. While it seems unlikely for now, there is a chance some kind of cyber-battle will break out, perhaps even escalating to the point where all exchange rates drop sharply. If you want to make sure not to be caught in any crossfire, it’s best to not hold more value in bitcoin than you are willing to lose.If you do decide to hold on to your bitcoin, make sure you are prepared before October 25, and preferably sooner. This is the day the BTG equivalent will be distributed to all BTC balances. B2X will follow a couple of weeks later, around mid-November (the exact date is not yet known).If you are storing your bitcoins on an exchange, in a custodial service like Coinbase, Circle or Xapo, or on any other service that holds your private keys for you, you may or may not eventually receive BTC, BTG and B2X. This is not yet very clear, and if you want to keep storing your coins on such services, you should at least see if your exchange or custodial service of choice has made an official statement on the forks, perhaps on their company blog. If not, contact them to ask.That said, if you want to be absolutely sure to be able to access your BTC, BTG and B2X, you should really control your private keys yourself. That way you don’t need to rely on any third party.If you’re currently using a custodial service to store your bitcoins, you need to create your own wallet instead. Send or withdraw your bitcoins from the custodial service to this new wallet; this wallet then holds your private keys.What kind of wallet you want to use is up to you. For this specific purpose it’s best to use a wallet that lets you easily access your private keys directly. (Some wallets make this easier for you than others.) But technically, any wallet that lets you control your private keys should be fine.With that in mind, here are some basic solutions:If you don’t care about transacting with BTC, BTG or B2X anytime soon, and really just want to keep all of them as long-term investments, a paper wallet is a good option. It should be noted, however, that this option is only really secure if you follow strict security precautions, which you can find<a href="https://en.bitcoin.it/wiki/Paper_wallet"> here</a>.Regular wallets are about as secure as your computer (or phone). Since most computers and phones are not all that secure, these are not ideal for large amounts. With that in mind, all mobile and desktop wallets listed on <a href="https://bitcoin.org/en/choose-your-wallet">bitcoin.org</a> will store your private keys.<a href="https://electrum.org/#home"> Electrum</a> is a good pick if you want easy access to your private keys directly.A full-node wallet like<a href="https://bitcoincore.org/en/releases/"> Bitcoin Core</a> or<a href="http://bitcoinknots.org/"> Bitcoin Knots</a> is also a good pick, as it’s not too hard to access your private keys with these wallets either. As a bonus, these wallets give you a little extra security on the Bitcoin blockchain (shortly) after the SegWit2X fork, because these wallets enforce all of Bitcoin's current protocol rules. However, these types of wallets are more resource-intensive to use, compared to most other wallets.Another option is to get a hardware wallet. Any of the hardware wallets listed on<a href="https://bitcoin.org/en/choose-your-wallet"> bitcoin.org</a> will keep your private keys secure. However, these wallets typically don’t let you easily access your private keys directly. It’s not clear that all these wallets will let you access BTG in particular, and not all of them have given a guarantee for B2X either. So while these wallets will safely store your private keys, it could be a bit more tricky (but probably not impossible) to get ahold of all three coins later.In any case: Be sure to make backups of your keys! Most wallets require you to do this when installing; don’t skip this step. </h3> <h1> Shortly After the Bitcoin Gold Fork (and Before the SegWit2x Fork)</h1> <h3> The Bitcoin Gold fork is sometimes referred to as a “friendly fork.” This is mainly because it has no intention of claiming to be the “real” Bitcoin, and it plans to implement strong replay protection.In short, this replay protection means that you won’t accidentally send your BTG when you mean to send BTC (or the other way around). So even after you’ve spent your BTC, you can still access your BTG.If you want to transact with your BTC before the SegWit2x fork, it could come in handy later to write down which of your Bitcoin addresses and/or private keys had BTG attributed to them — in other words, which of your Bitcoin addresses had any BTC on them at the time of the Bgold fork on October 25th.But there’s no rush to actually access your BTG. In fact, it will probably take at least a week before this is even possible, and maybe longer. It’s therefore probably best to ignore this fork until after the SegWit2x fork. That way you’ll only need to go through the process of claiming all your new coins once. </h3> <h1> After the SegWit2x Fork</h1> <h3> Unfortunately, the SegWit2x fork could play out a bit more messily.For one, several of the companies backing SegWit2x consider this fork an upgrade of Bitcoin itself. They therefore currently have no intention to adopt a new name for it. Some of them will call or list (what this article refers to as) SegWit2x and B2X, as "Bitcoin" and "BTC". Meanwhile, they might call or list (what this article refers to as) BTC as "B1X", or another ticker.And of course, all coins will command their own exchange rates. So as different exchanges list a different coin as "BTC", the price for "BTC" could differ vastly across exchanges: they're actually different coins! You should therefore not buy or sell <em>any</em> coin listed as "BTC", unless and until you are very sure which coin your exchange lists as "BTC".Additionally, it currently seems SegWit2x will fork without strong <a href="https://bitcoinmagazine.com/articles/segwit2x-and-case-strong-replay-protection-and-why-its-controversial/">replay protection</a>. This means that post-fork, BTC transactions and B2X transactions will look identical and could both be valid on both blockchains.Therefore, spending coins on the BTC blockchain could make you accidentally spend the “equivalent” B2X on the SegWit2x blockchain, and the other way around. Instead of paying someone only BTC, you may unintentionally send B2X as well — or vice versa. The BTCs and B2Xs are initially “stuck together.”To be on the safe side, you should probably not spend an coins after the SegWit2x fork at all. As explained below, you'll first need to "split" your coins.Furthermore, some light wallets (mobile wallets) will display whichever blockchain has more hash power attributed to it. This means that the balance on your screen could be a BTC balance or a B2X balance, and there will be no way to tell the difference. (Even if the wallet says it’s a BTC balance!)To be on the safe side, you should not accept any payments with light wallets, since you could receive B2X when you’re expecting BTC, or the other way around. At the very least, you should make absolutely sure that your wallet displays what you think it displays. (Wallets like <a href="https://electrum.org/#home">Electrum</a> and <a href="https://greenaddress.it/en/">GreenAddress</a> should display BTC as "BTC" regardless of hashpower distribution.) If you use a full-node wallet like <a href="https://bitcoincore.org/en/releases/">Bitcoin Core</a> or <a href="http://bitcoinknots.org/">Bitcoin Knots</a> and you want to accept BTC, that should also be fine.Depending on how much hash power is dedicated to each chain, it is possible that transactions will confirm (significantly) slower than usual for some time and will require higher fees to confirm at all. </h3> <h1> Claiming Your Coins</h1> <h3> If all three chains survive, and you control your private keys, you should be able to access BTC, BTG and B2X around mid-November.Claiming your BTG should be relatively easy, assuming there are wallets available for it. Most likely, you’d simply need to insert your private keys (or private key seed) into such a wallet.However, there are some security and privacy risks in doing so. It’s too soon to tell exactly what these risks will look like as it’s unclear which wallets will support BTG. (It’s not even certain that any wallets will.) But in general, you’ll first want to move your BTC (and B2X) to new addresses or whole new wallets before accessing your BTG.Since there’s no need to rush, it’s probably best just to wait on claiming your BTG until there is more clarity. By that time, Bitcoin Magazine will publish a follow-up article explaining how to do this.Securely accessing and using your B2X (and BTC) might prove a bit more tricky, mostly because of the risk of replay attacks. This requires that the BTC and B2X are split from each other, which will be possible but could prove a bit complex.Some wallets might split the coins for you, but it's too soon to know which wallets will. Additionally, exchanges will likely set up coin-splitting services and take care of most of this complexity behind the screens. You’d then just need to send your BTC or B2X to an exchange, and the exchange will credit your account with both BTC and B2X. (They should even replay the transaction for you to make sure they indeed receive both your coins and can split them for you.) There may also be other solutions to split your coins, but that remains to be seen.By mid-November, there will probably also be dedicated wallets for both BTC and B2X. Of course, you may need to upgrade your existing wallet or download a new wallet. This also remains to be seen.Further specifics on what to do after the forks will be announced on Bitcoin Magazine once the forks have occurred and we have a better understanding of the post-fork situation. </h3> <h1> So, to Recap ...</h1> <h3> 1. It’s best to control your private keys yourself before October 25, and hold on to them until after the SegWit2x fork, mid-November.</h3> <h3>To be on the safe side, avoid buying or selling any "BTC" and don't make any transactions shortly after the SegWit2x fork.</h3> <h3>As the dust settles after the SegWit2x fork, access and split your coins. (How to do this will be explained on Bitcoin Magazine once there is more clarity.</h3> </html> |
| json metadata | {"tags":["cryptocurrency","bitcoin","hardfork","bitcoingold","segwit2x"],"image":["https://fs.bitcoinmagazine.com/img/images/coin-split2xgold.width-800.jpg"],"links":["www.bitcoinmagazine.com","https://bitcoinmagazine.com/articles/bitcoin-gold-about-trial-asic-resistant-bitcoin-fork/","https://bitcoinmagazine.com/articles/2x-or-no2x-why-some-want-hard-fork-bitcoin-november-and-why-others-dont/","https://medium.com/@DCGco/bitcoin-scaling-agreement-at-consensus-2017-133521fe9a77","https://en.bitcoin.it/wiki/Paper_wallet","https://bitcoin.org/en/choose-your-wallet","https://electrum.org/#home","https://bitcoincore.org/en/releases/","http://bitcoinknots.org/","https://bitcoinmagazine.com/articles/segwit2x-and-case-strong-replay-protection-and-why-its-controversial/","https://greenaddress.it/en/"],"app":"steemit/0.1","format":"html"} |
| parent author | |
| parent permlink | cryptocurrency |
| permlink | a-bitcoin-beginner-s-guide-to-surviving-the-bgold-and-segwit2x-forks |
| title | A Bitcoin Beginner’s Guide to Surviving the Bgold and SegWit2x Forks |
| Transaction Info | Block #16434933/Trx 690e50368076018c9c11899bfa14a00c2b933350 |
View Raw JSON Data
{
"block": 16434933,
"op": [
"comment",
{
"author": "cryptojoy",
"body": "<html>\n<p><code>Source: </code><a href=\"www.bitcoinmagazine.com\"><code>bitcoinmagazine</code></a></p>\n<p><code>Please upvote the post if you like it.</code></p>\n<p><img src=\"https://fs.bitcoinmagazine.com/img/images/coin-split2xgold.width-800.jpg\" width=\"800\" height=\"448\"/></p>\n<h3> It looks as if Bitcoin will experience at least two more “coin-splits” soon, which (more accurately) will result in the creation of new coins. On October 25,<a href=\"https://bitcoinmagazine.com/articles/bitcoin-gold-about-trial-asic-resistant-bitcoin-fork/\"> Bitcoin Gold</a> (Bgold) will split off from Bitcoin to create an ASIC-resistant cryptocurrency. A few weeks later, a significant group of Bitcoin companies wants to hard fork according to the<a href=\"https://bitcoinmagazine.com/articles/2x-or-no2x-why-some-want-hard-fork-bitcoin-november-and-why-others-dont/\"> SegWit2x</a> plan as defined in the “<a href=\"https://medium.com/@DCGco/bitcoin-scaling-agreement-at-consensus-2017-133521fe9a77\">New York Agreement</a>” (NYA), which will probably result in yet another new coin.If this all plays out, there could be three distinct blockchains and three types of coins within about a month of publication of this article. One blockchain would follow the current Bitcoin protocol; for the purpose of this article, that coin will be referred to as “BTC.” The second blockchain will follow the Bgold protocol; in this article, that coin will be referred to as “BTG.” The third blockchain will follow the SegWit2x protocol; that coin will be referred to as “B2X.”The good news is that each BTC will effectively be copied onto both the Bgold and the SegWit2x blockchains. If you hold Bitcoin private keys at the time of the forks, you should be able to access your BTG and B2X coins as well.The bad news is that such forks can be somewhat messy and risky. If you’re not careful, it’s easy to lose your BTC or B2X, and maybe your BTG.This guide will provide you with the basics to keep your funds safe during the upcoming forks and help to ensure you make it to the end of next month with your BTC, BTG and B2X intact.<em>Author’s note: If you want to play the markets as soon as possible and you are fine with taking risks, and/or you really know what you are doing, this article is probably not for you: it's a beginner's guide. Also please note that everything in this article is just advise, based on our best understanding of the situation. Much is still uncertain and subject to change.</em> </h3>\n<h1> Before the Forks (That’s Now)</h1>\n<h3> First of all, be aware that coin-splits can be somewhat risky — especially controversial ones like the SegWit2x fork. While it seems unlikely for now, there is a chance some kind of cyber-battle will break out, perhaps even escalating to the point where all exchange rates drop sharply. If you want to make sure not to be caught in any crossfire, it’s best to not hold more value in bitcoin than you are willing to lose.If you do decide to hold on to your bitcoin, make sure you are prepared before October 25, and preferably sooner. This is the day the BTG equivalent will be distributed to all BTC balances. B2X will follow a couple of weeks later, around mid-November (the exact date is not yet known).If you are storing your bitcoins on an exchange, in a custodial service like Coinbase, Circle or Xapo, or on any other service that holds your private keys for you, you may or may not eventually receive BTC, BTG and B2X. This is not yet very clear, and if you want to keep storing your coins on such services, you should at least see if your exchange or custodial service of choice has made an official statement on the forks, perhaps on their company blog. If not, contact them to ask.That said, if you want to be absolutely sure to be able to access your BTC, BTG and B2X, you should really control your private keys yourself. That way you don’t need to rely on any third party.If you’re currently using a custodial service to store your bitcoins, you need to create your own wallet instead. Send or withdraw your bitcoins from the custodial service to this new wallet; this wallet then holds your private keys.What kind of wallet you want to use is up to you. For this specific purpose it’s best to use a wallet that lets you easily access your private keys directly. (Some wallets make this easier for you than others.) But technically, any wallet that lets you control your private keys should be fine.With that in mind, here are some basic solutions:If you don’t care about transacting with BTC, BTG or B2X anytime soon, and really just want to keep all of them as long-term investments, a paper wallet is a good option. It should be noted, however, that this option is only really secure if you follow strict security precautions, which you can find<a href=\"https://en.bitcoin.it/wiki/Paper_wallet\"> here</a>.Regular wallets are about as secure as your computer (or phone). Since most computers and phones are not all that secure, these are not ideal for large amounts. With that in mind, all mobile and desktop wallets listed on <a href=\"https://bitcoin.org/en/choose-your-wallet\">bitcoin.org</a> will store your private keys.<a href=\"https://electrum.org/#home\"> Electrum</a> is a good pick if you want easy access to your private keys directly.A full-node wallet like<a href=\"https://bitcoincore.org/en/releases/\"> Bitcoin Core</a> or<a href=\"http://bitcoinknots.org/\"> Bitcoin Knots</a> is also a good pick, as it’s not too hard to access your private keys with these wallets either. As a bonus, these wallets give you a little extra security on the Bitcoin blockchain (shortly) after the SegWit2X fork, because these wallets enforce all of Bitcoin's current protocol rules. However, these types of wallets are more resource-intensive to use, compared to most other wallets.Another option is to get a hardware wallet. Any of the hardware wallets listed on<a href=\"https://bitcoin.org/en/choose-your-wallet\"> bitcoin.org</a> will keep your private keys secure. However, these wallets typically don’t let you easily access your private keys directly. It’s not clear that all these wallets will let you access BTG in particular, and not all of them have given a guarantee for B2X either. So while these wallets will safely store your private keys, it could be a bit more tricky (but probably not impossible) to get ahold of all three coins later.In any case: Be sure to make backups of your keys! Most wallets require you to do this when installing; don’t skip this step. </h3>\n<h1> Shortly After the Bitcoin Gold Fork (and Before the SegWit2x Fork)</h1>\n<h3> The Bitcoin Gold fork is sometimes referred to as a “friendly fork.” This is mainly because it has no intention of claiming to be the “real” Bitcoin, and it plans to implement strong replay protection.In short, this replay protection means that you won’t accidentally send your BTG when you mean to send BTC (or the other way around). So even after you’ve spent your BTC, you can still access your BTG.If you want to transact with your BTC before the SegWit2x fork, it could come in handy later to write down which of your Bitcoin addresses and/or private keys had BTG attributed to them — in other words, which of your Bitcoin addresses had any BTC on them at the time of the Bgold fork on October 25th.But there’s no rush to actually access your BTG. In fact, it will probably take at least a week before this is even possible, and maybe longer. It’s therefore probably best to ignore this fork until after the SegWit2x fork. That way you’ll only need to go through the process of claiming all your new coins once. </h3>\n<h1> After the SegWit2x Fork</h1>\n<h3> Unfortunately, the SegWit2x fork could play out a bit more messily.For one, several of the companies backing SegWit2x consider this fork an upgrade of Bitcoin itself. They therefore currently have no intention to adopt a new name for it. Some of them will call or list (what this article refers to as) SegWit2x and B2X, as \"Bitcoin\" and \"BTC\". Meanwhile, they might call or list (what this article refers to as) BTC as \"B1X\", or another ticker.And of course, all coins will command their own exchange rates. So as different exchanges list a different coin as \"BTC\", the price for \"BTC\" could differ vastly across exchanges: they're actually different coins! You should therefore not buy or sell <em>any</em> coin listed as \"BTC\", unless and until you are very sure which coin your exchange lists as \"BTC\".Additionally, it currently seems SegWit2x will fork without strong <a href=\"https://bitcoinmagazine.com/articles/segwit2x-and-case-strong-replay-protection-and-why-its-controversial/\">replay protection</a>. This means that post-fork, BTC transactions and B2X transactions will look identical and could both be valid on both blockchains.Therefore, spending coins on the BTC blockchain could make you accidentally spend the “equivalent” B2X on the SegWit2x blockchain, and the other way around. Instead of paying someone only BTC, you may unintentionally send B2X as well — or vice versa. The BTCs and B2Xs are initially “stuck together.”To be on the safe side, you should probably not spend an coins after the SegWit2x fork at all. As explained below, you'll first need to \"split\" your coins.Furthermore, some light wallets (mobile wallets) will display whichever blockchain has more hash power attributed to it. This means that the balance on your screen could be a BTC balance or a B2X balance, and there will be no way to tell the difference. (Even if the wallet says it’s a BTC balance!)To be on the safe side, you should not accept any payments with light wallets, since you could receive B2X when you’re expecting BTC, or the other way around. At the very least, you should make absolutely sure that your wallet displays what you think it displays. (Wallets like <a href=\"https://electrum.org/#home\">Electrum</a> and <a href=\"https://greenaddress.it/en/\">GreenAddress</a> should display BTC as \"BTC\" regardless of hashpower distribution.) If you use a full-node wallet like <a href=\"https://bitcoincore.org/en/releases/\">Bitcoin Core</a> or <a href=\"http://bitcoinknots.org/\">Bitcoin Knots</a> and you want to accept BTC, that should also be fine.Depending on how much hash power is dedicated to each chain, it is possible that transactions will confirm (significantly) slower than usual for some time and will require higher fees to confirm at all. </h3>\n<h1> Claiming Your Coins</h1>\n<h3> If all three chains survive, and you control your private keys, you should be able to access BTC, BTG and B2X around mid-November.Claiming your BTG should be relatively easy, assuming there are wallets available for it. Most likely, you’d simply need to insert your private keys (or private key seed) into such a wallet.However, there are some security and privacy risks in doing so. It’s too soon to tell exactly what these risks will look like as it’s unclear which wallets will support BTG. (It’s not even certain that any wallets will.) But in general, you’ll first want to move your BTC (and B2X) to new addresses or whole new wallets before accessing your BTG.Since there’s no need to rush, it’s probably best just to wait on claiming your BTG until there is more clarity. By that time, Bitcoin Magazine will publish a follow-up article explaining how to do this.Securely accessing and using your B2X (and BTC) might prove a bit more tricky, mostly because of the risk of replay attacks. This requires that the BTC and B2X are split from each other, which will be possible but could prove a bit complex.Some wallets might split the coins for you, but it's too soon to know which wallets will. Additionally, exchanges will likely set up coin-splitting services and take care of most of this complexity behind the screens. You’d then just need to send your BTC or B2X to an exchange, and the exchange will credit your account with both BTC and B2X. (They should even replay the transaction for you to make sure they indeed receive both your coins and can split them for you.) There may also be other solutions to split your coins, but that remains to be seen.By mid-November, there will probably also be dedicated wallets for both BTC and B2X. Of course, you may need to upgrade your existing wallet or download a new wallet. This also remains to be seen.Further specifics on what to do after the forks will be announced on Bitcoin Magazine once the forks have occurred and we have a better understanding of the post-fork situation. </h3>\n<h1> So, to Recap ...</h1>\n<h3> 1. It’s best to control your private keys yourself before October 25, and hold on to them until after the SegWit2x fork, mid-November.</h3>\n<h3>To be on the safe side, avoid buying or selling any \"BTC\" and don't make any transactions shortly after the SegWit2x fork.</h3>\n<h3>As the dust settles after the SegWit2x fork, access and split your coins. (How to do this will be explained on Bitcoin Magazine once there is more clarity.</h3>\n</html>",
"json_metadata": "{\"tags\":[\"cryptocurrency\",\"bitcoin\",\"hardfork\",\"bitcoingold\",\"segwit2x\"],\"image\":[\"https://fs.bitcoinmagazine.com/img/images/coin-split2xgold.width-800.jpg\"],\"links\":[\"www.bitcoinmagazine.com\",\"https://bitcoinmagazine.com/articles/bitcoin-gold-about-trial-asic-resistant-bitcoin-fork/\",\"https://bitcoinmagazine.com/articles/2x-or-no2x-why-some-want-hard-fork-bitcoin-november-and-why-others-dont/\",\"https://medium.com/@DCGco/bitcoin-scaling-agreement-at-consensus-2017-133521fe9a77\",\"https://en.bitcoin.it/wiki/Paper_wallet\",\"https://bitcoin.org/en/choose-your-wallet\",\"https://electrum.org/#home\",\"https://bitcoincore.org/en/releases/\",\"http://bitcoinknots.org/\",\"https://bitcoinmagazine.com/articles/segwit2x-and-case-strong-replay-protection-and-why-its-controversial/\",\"https://greenaddress.it/en/\"],\"app\":\"steemit/0.1\",\"format\":\"html\"}",
"parent_author": "",
"parent_permlink": "cryptocurrency",
"permlink": "a-bitcoin-beginner-s-guide-to-surviving-the-bgold-and-segwit2x-forks",
"title": "A Bitcoin Beginner’s Guide to Surviving the Bgold and SegWit2x Forks"
}
],
"op_in_trx": 0,
"timestamp": "2017-10-18T10:19:30",
"trx_id": "690e50368076018c9c11899bfa14a00c2b933350",
"trx_in_block": 8,
"virtual_op": 0
}steemdelegated 18.387 SP to @cryptojoy2017/08/04 05:16:12
steemdelegated 18.387 SP to @cryptojoy
2017/08/04 05:16:12
| delegatee | cryptojoy |
| delegator | steem |
| vesting shares | 29941.481744 VESTS |
| Transaction Info | Block #14271404/Trx a71d00315a98a717203e216972a24c61197a8f00 |
View Raw JSON Data
{
"block": 14271404,
"op": [
"delegate_vesting_shares",
{
"delegatee": "cryptojoy",
"delegator": "steem",
"vesting_shares": "29941.481744 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2017-08-04T05:16:12",
"trx_id": "a71d00315a98a717203e216972a24c61197a8f00",
"trx_in_block": 2,
"virtual_op": 0
}steemcreated a new account: @cryptojoy2017/06/29 06:22:27
steemcreated a new account: @cryptojoy
2017/06/29 06:22:27
| active | {"account_auths":[],"key_auths":[["STM85udCa38pY3KUwZ6AQrPX3B9QMHZfp3cCMZqs2s92Jp5sbXiPC",1]],"weight_threshold":1} |
| creator | steem |
| delegation | 57000.000000 VESTS |
| extensions | [] |
| fee | 0.500 STEEM |
| json metadata | |
| memo key | STM6VjWxrAtfr2NtTCRSpVgQXbMqdCadGfGg89L7Hz6PuiA92jyde |
| new account name | cryptojoy |
| owner | {"account_auths":[],"key_auths":[["STM4unFJWQhQT7eu2CEyT1Bz8wavb7n685MRD9hGDbgbuVLSpgzrw",1]],"weight_threshold":1} |
| posting | {"account_auths":[],"key_auths":[["STM7Hpq6PgwWM6smpRvVxXMvbDaHZoY2e6ED4WEz2RfQLCZeXC4Jw",1]],"weight_threshold":1} |
| Transaction Info | Block #13237190/Trx d33ce0a33b1df4fec83f6787a536ea1affbd12f5 |
View Raw JSON Data
{
"block": 13237190,
"op": [
"account_create_with_delegation",
{
"active": {
"account_auths": [],
"key_auths": [
[
"STM85udCa38pY3KUwZ6AQrPX3B9QMHZfp3cCMZqs2s92Jp5sbXiPC",
1
]
],
"weight_threshold": 1
},
"creator": "steem",
"delegation": "57000.000000 VESTS",
"extensions": [],
"fee": "0.500 STEEM",
"json_metadata": "",
"memo_key": "STM6VjWxrAtfr2NtTCRSpVgQXbMqdCadGfGg89L7Hz6PuiA92jyde",
"new_account_name": "cryptojoy",
"owner": {
"account_auths": [],
"key_auths": [
[
"STM4unFJWQhQT7eu2CEyT1Bz8wavb7n685MRD9hGDbgbuVLSpgzrw",
1
]
],
"weight_threshold": 1
},
"posting": {
"account_auths": [],
"key_auths": [
[
"STM7Hpq6PgwWM6smpRvVxXMvbDaHZoY2e6ED4WEz2RfQLCZeXC4Jw",
1
]
],
"weight_threshold": 1
}
}
],
"op_in_trx": 0,
"timestamp": "2017-06-29T06:22:27",
"trx_id": "d33ce0a33b1df4fec83f6787a536ea1affbd12f5",
"trx_in_block": 24,
"virtual_op": 0
}Manabar
Voting Power100.00%
Downvote Power100.00%
Resource Credits100.00%
Reputation Progress0.00%
{
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779058854
},
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779058854
},
"rc_account": {
"account": "cryptojoy",
"max_rc": "10164408779",
"max_rc_creation_adjustment": {
"amount": "2020748973",
"nai": "@@000000037",
"precision": 6
},
"rc_manabar": {
"current_mana": "10164408779",
"last_update_time": 1779058854
}
}
}Account Metadata
| POSTING JSON METADATA | |
| None | |
| JSON METADATA | |
| None |
{
"posting_json_metadata": {},
"json_metadata": {}
}Auth Keys
Owner
Single Signature
Public Keys
STM4unFJWQhQT7eu2CEyT1Bz8wavb7n685MRD9hGDbgbuVLSpgzrw1/1
Active
Single Signature
Public Keys
STM85udCa38pY3KUwZ6AQrPX3B9QMHZfp3cCMZqs2s92Jp5sbXiPC1/1
Posting
Single Signature
Public Keys
STM7Hpq6PgwWM6smpRvVxXMvbDaHZoY2e6ED4WEz2RfQLCZeXC4Jw1/1
Memo
STM6VjWxrAtfr2NtTCRSpVgQXbMqdCadGfGg89L7Hz6PuiA92jyde
{
"owner": {
"account_auths": [],
"key_auths": [
[
"STM4unFJWQhQT7eu2CEyT1Bz8wavb7n685MRD9hGDbgbuVLSpgzrw",
1
]
],
"weight_threshold": 1
},
"active": {
"account_auths": [],
"key_auths": [
[
"STM85udCa38pY3KUwZ6AQrPX3B9QMHZfp3cCMZqs2s92Jp5sbXiPC",
1
]
],
"weight_threshold": 1
},
"posting": {
"account_auths": [],
"key_auths": [
[
"STM7Hpq6PgwWM6smpRvVxXMvbDaHZoY2e6ED4WEz2RfQLCZeXC4Jw",
1
]
],
"weight_threshold": 1
},
"memo": "STM6VjWxrAtfr2NtTCRSpVgQXbMqdCadGfGg89L7Hz6PuiA92jyde"
}Witness Votes
0 / 30
No active witness votes.
[]