VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS88.42%
Net Worth
0.131USD
STEEM
0.000STEEM
SBD
0.197SBD
Effective Power
5.007SP
├── Own SP
0.630SP
└── Incoming DelegationsDeleg
+4.377SP
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.630SP | SP |
| Delegated Out | 0.000SP | SP |
| Delegation In | 4.377SP | SP |
| Effective Power | 5.007SP | SP |
| Reward SP (pending) | 0.075SP | 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.197SBD | SBD |
{
"balance": "0.000 STEEM",
"savings_balance": "0.000 STEEM",
"reward_steem_balance": "0.000 STEEM",
"vesting_shares": "1024.299133 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "7119.360673 VESTS",
"sbd_balance": "0.000 SBD",
"savings_sbd_balance": "0.000 SBD",
"reward_sbd_balance": "0.197 SBD",
"conversions": []
}Account Info
| name | eriksank |
| id | 570788 |
| rank | 1,309,932 |
| reputation | 2091543255 |
| created | 2018-01-06T18:28:15 |
| recovery_account | steem |
| proxy | None |
| post_count | 26 |
| comment_count | 0 |
| lifetime_vote_count | 0 |
| witnesses_voted_for | 0 |
| last_post | 2018-12-19T01:21:03 |
| last_root_post | 2018-12-19T01:21:03 |
| last_vote_time | 2018-12-17T05:54:15 |
| 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 | 1024.299133 VESTS |
| delegated_vesting_shares | 0.000000 VESTS |
| received_vesting_shares | 7119.360673 VESTS |
| reward_vesting_balance | 153.174345 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": [
[
"STM7L4NHTTJPuzBUULqSmvZniWHAMxeEAVshyophhUFneGPHeXgGf",
1
]
],
"weight_threshold": 1
},
"balance": "0.000 STEEM",
"can_vote": true,
"comment_count": 0,
"created": "2018-01-06T18:28:15",
"curation_rewards": 0,
"delegated_vesting_shares": "0.000000 VESTS",
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779062574
},
"guest_bloggers": [],
"id": 570788,
"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": "2018-12-19T01:21:03",
"last_root_post": "2018-12-19T01:21:03",
"last_vote_time": "2018-12-17T05:54:15",
"lifetime_vote_count": 0,
"market_history": [],
"memo_key": "STM7B959Qqbp32GjRUHE8AQh6nEio4EDxGCqXbosQ2crYKveGPsVC",
"mined": false,
"name": "eriksank",
"next_vesting_withdrawal": "1969-12-31T23:59:59",
"other_history": [],
"owner": {
"account_auths": [],
"key_auths": [
[
"STM7fyN9bi8bpYAXLL9Un8BoiGv2YTuGxiEcfaH9w9tqYRAY5fLDk",
1
]
],
"weight_threshold": 1
},
"pending_claimed_accounts": 0,
"post_bandwidth": 0,
"post_count": 26,
"post_history": [],
"posting": {
"account_auths": [],
"key_auths": [
[
"STM6LfEvvvTn3Lpdp5k2Zh873eTnsfQVL6twdPvS1KHxWiZ6Sz6xr",
1
]
],
"weight_threshold": 1
},
"posting_json_metadata": "",
"posting_rewards": 148,
"proxied_vsf_votes": [
0,
0,
0,
0
],
"proxy": "",
"received_vesting_shares": "7119.360673 VESTS",
"recovery_account": "steem",
"reputation": 2091543255,
"reset_account": "null",
"reward_sbd_balance": "0.197 SBD",
"reward_steem_balance": "0.000 STEEM",
"reward_vesting_balance": "153.174345 VESTS",
"reward_vesting_steem": "0.075 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": "1024.299133 VESTS",
"vesting_withdraw_rate": "0.000000 VESTS",
"vote_history": [],
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779062574
},
"voting_power": 0,
"withdraw_routes": 0,
"withdrawn": 0,
"witness_votes": [],
"witnesses_voted_for": 0,
"rank": 1309932
}Withdraw Routes
| Incoming | Outgoing |
|---|---|
Empty | Empty |
{
"incoming": [],
"outgoing": []
}From Date
To Date
2026/05/18 00:02:54
2026/05/18 00:02:54
| delegatee | eriksank |
| delegator | steem |
| vesting shares | 7119.360673 VESTS |
| Transaction Info | Block #106143204/Trx f8745dc2f5d5e2cbacd924c6859c02afa9508b75 |
View Raw JSON Data
{
"block": 106143204,
"op": [
"delegate_vesting_shares",
{
"delegatee": "eriksank",
"delegator": "steem",
"vesting_shares": "7119.360673 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2026-05-18T00:02:54",
"trx_id": "f8745dc2f5d5e2cbacd924c6859c02afa9508b75",
"trx_in_block": 8,
"virtual_op": 0
}2026/05/12 03:00:36
2026/05/12 03:00:36
| delegatee | eriksank |
| delegator | steem |
| vesting shares | 4407.150268 VESTS |
| Transaction Info | Block #105974715/Trx fc6272f6f493d0c1084c8be97581a3dc0ec81867 |
View Raw JSON Data
{
"block": 105974715,
"op": [
"delegate_vesting_shares",
{
"delegatee": "eriksank",
"delegator": "steem",
"vesting_shares": "4407.150268 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2026-05-12T03:00:36",
"trx_id": "fc6272f6f493d0c1084c8be97581a3dc0ec81867",
"trx_in_block": 5,
"virtual_op": 0
}2026/04/25 23:24:12
2026/04/25 23:24:12
| delegatee | eriksank |
| delegator | steem |
| vesting shares | 7131.876429 VESTS |
| Transaction Info | Block #105510862/Trx 996e29b396f7d554a19ceceff356885471b05338 |
View Raw JSON Data
{
"block": 105510862,
"op": [
"delegate_vesting_shares",
{
"delegatee": "eriksank",
"delegator": "steem",
"vesting_shares": "7131.876429 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2026-04-25T23:24:12",
"trx_id": "996e29b396f7d554a19ceceff356885471b05338",
"trx_in_block": 2,
"virtual_op": 0
}2026/01/23 07:14:42
2026/01/23 07:14:42
| delegatee | eriksank |
| delegator | steem |
| vesting shares | 4448.697087 VESTS |
| Transaction Info | Block #102851142/Trx 0cc9245cff1c2a4771b22e8ded25b02243d74351 |
View Raw JSON Data
{
"block": 102851142,
"op": [
"delegate_vesting_shares",
{
"delegatee": "eriksank",
"delegator": "steem",
"vesting_shares": "4448.697087 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2026-01-23T07:14:42",
"trx_id": "0cc9245cff1c2a4771b22e8ded25b02243d74351",
"trx_in_block": 1,
"virtual_op": 0
}2024/12/17 02:34:24
2024/12/17 02:34:24
| delegatee | eriksank |
| delegator | steem |
| vesting shares | 4612.916284 VESTS |
| Transaction Info | Block #91297564/Trx 3a74abc48cbb1bbf68d09b149e269eee211208d6 |
View Raw JSON Data
{
"block": 91297564,
"op": [
"delegate_vesting_shares",
{
"delegatee": "eriksank",
"delegator": "steem",
"vesting_shares": "4612.916284 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2024-12-17T02:34:24",
"trx_id": "3a74abc48cbb1bbf68d09b149e269eee211208d6",
"trx_in_block": 6,
"virtual_op": 0
}2023/11/13 18:17:00
2023/11/13 18:17:00
| delegatee | eriksank |
| delegator | steem |
| vesting shares | 4782.049816 VESTS |
| Transaction Info | Block #79851763/Trx 62e42cab9ce316431730206e478c57c9bd521c44 |
View Raw JSON Data
{
"block": 79851763,
"op": [
"delegate_vesting_shares",
{
"delegatee": "eriksank",
"delegator": "steem",
"vesting_shares": "4782.049816 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2023-11-13T18:17:00",
"trx_id": "62e42cab9ce316431730206e478c57c9bd521c44",
"trx_in_block": 5,
"virtual_op": 0
}2023/09/21 21:35:09
2023/09/21 21:35:09
| delegatee | eriksank |
| delegator | steem |
| vesting shares | 7719.328602 VESTS |
| Transaction Info | Block #78347535/Trx 2bfec6206e5b40b2a43861704510cfc6ecaaef87 |
View Raw JSON Data
{
"block": 78347535,
"op": [
"delegate_vesting_shares",
{
"delegatee": "eriksank",
"delegator": "steem",
"vesting_shares": "7719.328602 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2023-09-21T21:35:09",
"trx_id": "2bfec6206e5b40b2a43861704510cfc6ecaaef87",
"trx_in_block": 2,
"virtual_op": 0
}2022/11/03 11:25:06
2022/11/03 11:25:06
| delegatee | eriksank |
| delegator | steem |
| vesting shares | 7941.010040 VESTS |
| Transaction Info | Block #69112921/Trx aa86a995b140b9ca075dc6f78b3dc34181fe58bd |
View Raw JSON Data
{
"block": 69112921,
"op": [
"delegate_vesting_shares",
{
"delegatee": "eriksank",
"delegator": "steem",
"vesting_shares": "7941.010040 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2022-11-03T11:25:06",
"trx_id": "aa86a995b140b9ca075dc6f78b3dc34181fe58bd",
"trx_in_block": 5,
"virtual_op": 0
}2022/01/17 10:42:18
2022/01/17 10:42:18
| delegatee | eriksank |
| delegator | steem |
| vesting shares | 8161.543271 VESTS |
| Transaction Info | Block #60809112/Trx dc0a1831d4f9efcf2d04770fceafee54764e7996 |
View Raw JSON Data
{
"block": 60809112,
"op": [
"delegate_vesting_shares",
{
"delegatee": "eriksank",
"delegator": "steem",
"vesting_shares": "8161.543271 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2022-01-17T10:42:18",
"trx_id": "dc0a1831d4f9efcf2d04770fceafee54764e7996",
"trx_in_block": 20,
"virtual_op": 0
}2021/06/14 00:38:15
2021/06/14 00:38:15
| delegatee | eriksank |
| delegator | steem |
| vesting shares | 8345.311929 VESTS |
| Transaction Info | Block #54607514/Trx e365007c76b33e7dc3f714abd6efeb739271f959 |
View Raw JSON Data
{
"block": 54607514,
"op": [
"delegate_vesting_shares",
{
"delegatee": "eriksank",
"delegator": "steem",
"vesting_shares": "8345.311929 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2021-06-14T00:38:15",
"trx_id": "e365007c76b33e7dc3f714abd6efeb739271f959",
"trx_in_block": 0,
"virtual_op": 0
}2020/12/11 10:57:21
2020/12/11 10:57:21
| delegatee | eriksank |
| delegator | steem |
| vesting shares | 8532.733903 VESTS |
| Transaction Info | Block #49354980/Trx ff2a4523e9b3e0080a083b89dbbac9b7297441dc |
View Raw JSON Data
{
"block": 49354980,
"op": [
"delegate_vesting_shares",
{
"delegatee": "eriksank",
"delegator": "steem",
"vesting_shares": "8532.733903 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-12-11T10:57:21",
"trx_id": "ff2a4523e9b3e0080a083b89dbbac9b7297441dc",
"trx_in_block": 1,
"virtual_op": 0
}2020/12/06 04:34:39
2020/12/06 04:34:39
| delegatee | eriksank |
| delegator | steem |
| vesting shares | 1912.543513 VESTS |
| Transaction Info | Block #49206545/Trx a44ffb071b48c9ca94f4b521960143288e07919e |
View Raw JSON Data
{
"block": 49206545,
"op": [
"delegate_vesting_shares",
{
"delegatee": "eriksank",
"delegator": "steem",
"vesting_shares": "1912.543513 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-12-06T04:34:39",
"trx_id": "a44ffb071b48c9ca94f4b521960143288e07919e",
"trx_in_block": 0,
"virtual_op": 0
}2020/12/05 14:35:33
2020/12/05 14:35:33
| delegatee | eriksank |
| delegator | steem |
| vesting shares | 8538.941757 VESTS |
| Transaction Info | Block #49190079/Trx 7b9e971d233ce8dbf1f80fa6c407526866fb5034 |
View Raw JSON Data
{
"block": 49190079,
"op": [
"delegate_vesting_shares",
{
"delegatee": "eriksank",
"delegator": "steem",
"vesting_shares": "8538.941757 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-12-05T14:35:33",
"trx_id": "7b9e971d233ce8dbf1f80fa6c407526866fb5034",
"trx_in_block": 6,
"virtual_op": 0
}2020/11/02 15:12:45
2020/11/02 15:12:45
| delegatee | eriksank |
| delegator | steem |
| vesting shares | 1920.017158 VESTS |
| Transaction Info | Block #48257297/Trx 4d926df351b68baa644ef7435cecca3561b2ed75 |
View Raw JSON Data
{
"block": 48257297,
"op": [
"delegate_vesting_shares",
{
"delegatee": "eriksank",
"delegator": "steem",
"vesting_shares": "1920.017158 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-11-02T15:12:45",
"trx_id": "4d926df351b68baa644ef7435cecca3561b2ed75",
"trx_in_block": 3,
"virtual_op": 0
}2020/05/09 05:31:42
2020/05/09 05:31:42
| delegatee | eriksank |
| delegator | steem |
| vesting shares | 8741.747116 VESTS |
| Transaction Info | Block #43216788/Trx 6aee0ba3d4e9064c282d3577b8ba0017335458e9 |
View Raw JSON Data
{
"block": 43216788,
"op": [
"delegate_vesting_shares",
{
"delegatee": "eriksank",
"delegator": "steem",
"vesting_shares": "8741.747116 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-05-09T05:31:42",
"trx_id": "6aee0ba3d4e9064c282d3577b8ba0017335458e9",
"trx_in_block": 4,
"virtual_op": 0
}2020/05/08 09:06:09
2020/05/08 09:06:09
| delegatee | eriksank |
| delegator | steem |
| vesting shares | 1953.311140 VESTS |
| Transaction Info | Block #43192854/Trx cabce398ee5b56170b61d9f50f3cb3de8a13153c |
View Raw JSON Data
{
"block": 43192854,
"op": [
"delegate_vesting_shares",
{
"delegatee": "eriksank",
"delegator": "steem",
"vesting_shares": "1953.311140 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-05-08T09:06:09",
"trx_id": "cabce398ee5b56170b61d9f50f3cb3de8a13153c",
"trx_in_block": 2,
"virtual_op": 0
}2020/02/16 18:59:30
2020/02/16 18:59:30
| delegatee | eriksank |
| delegator | steem |
| vesting shares | 8785.006053 VESTS |
| Transaction Info | Block #40877208/Trx 90d64a804549870ac787a60f81037a6f22269713 |
View Raw JSON Data
{
"block": 40877208,
"op": [
"delegate_vesting_shares",
{
"delegatee": "eriksank",
"delegator": "steem",
"vesting_shares": "8785.006053 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-02-16T18:59:30",
"trx_id": "90d64a804549870ac787a60f81037a6f22269713",
"trx_in_block": 54,
"virtual_op": 0
}2020/01/07 05:47:54
2020/01/07 05:47:54
| author | steemitboard |
| body | Congratulations @eriksank! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@eriksank/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/@eriksank) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=eriksank)_</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 | eriksank |
| parent permlink | what-is-the-effect-of-democracy-on-women |
| permlink | steemitboard-notify-eriksank-20200107t054754000z |
| title | |
| Transaction Info | Block #39711760/Trx c2b692802102ae89641ed85887705eb802317c6b |
View Raw JSON Data
{
"block": 39711760,
"op": [
"comment",
{
"author": "steemitboard",
"body": "Congratulations @eriksank! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@eriksank/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/@eriksank) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=eriksank)_</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": "eriksank",
"parent_permlink": "what-is-the-effect-of-democracy-on-women",
"permlink": "steemitboard-notify-eriksank-20200107t054754000z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2020-01-07T05:47:54",
"trx_id": "c2b692802102ae89641ed85887705eb802317c6b",
"trx_in_block": 7,
"virtual_op": 0
}2019/03/24 02:57:39
2019/03/24 02:57:39
| author | eriksank |
| permlink | how-to-provide-liquidity-on-the-bitcoin-lightning-network-for-incoming-payments |
| voter | chigginsnc |
| weight | 10000 (100.00%) |
| Transaction Info | Block #31422350/Trx 1679c18ec83b6f35fb520772050a48c110af4015 |
View Raw JSON Data
{
"block": 31422350,
"op": [
"vote",
{
"author": "eriksank",
"permlink": "how-to-provide-liquidity-on-the-bitcoin-lightning-network-for-incoming-payments",
"voter": "chigginsnc",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2019-03-24T02:57:39",
"trx_id": "1679c18ec83b6f35fb520772050a48c110af4015",
"trx_in_block": 12,
"virtual_op": 0
}2019/03/20 02:21:48
2019/03/20 02:21:48
| delegatee | eriksank |
| delegator | steem |
| vesting shares | 8981.235965 VESTS |
| Transaction Info | Block #31306504/Trx 7cc2dfb8df10c9be456c854273398a52e4c2d05f |
View Raw JSON Data
{
"block": 31306504,
"op": [
"delegate_vesting_shares",
{
"delegatee": "eriksank",
"delegator": "steem",
"vesting_shares": "8981.235965 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2019-03-20T02:21:48",
"trx_id": "7cc2dfb8df10c9be456c854273398a52e4c2d05f",
"trx_in_block": 26,
"virtual_op": 0
}2019/01/18 07:41:57
2019/01/18 07:41:57
| author | partiko |
| body | Thank you so much for sharing this amazing post with us! Have you heard about Partiko? It’s a really convenient mobile app for Steem! With Partiko, you can easily see what’s going on in the Steem community, make posts and comments (no beneficiary cut forever!), and always stayed connected with your followers via push notification! Partiko also rewards you with Partiko Points (3000 Partiko Point bonus when you first use it!), and Partiko Points can be converted into Steem tokens. You can earn Partiko Points easily by making posts and comments using Partiko. We also noticed that your Steem Power is low. We will be very happy to delegate 15 Steem Power to you once you have made a post using Partiko! With more Steem Power, you can make more posts and comments, and earn more rewards! If that all sounds interesting, you can: - Download Partiko Android at [Google Play](http://bit.ly/2SRFIta) - Or Download Partiko iOS on the [App Store](https://apple.co/2PcXkSd) Thank you so much for reading this message! |
| json metadata | {"app":"partiko"} |
| parent author | eriksank |
| parent permlink | what-is-the-effect-of-democracy-on-women |
| permlink | partiko-re-eriksank-what-is-the-effect-of-democracy-on-women-20190118t074157670z |
| title | |
| Transaction Info | Block #29557544/Trx 544a22b14d3eaa16519d4585ab4e4f88f0da7d49 |
View Raw JSON Data
{
"block": 29557544,
"op": [
"comment",
{
"author": "partiko",
"body": "Thank you so much for sharing this amazing post with us!\n\nHave you heard about Partiko? It’s a really convenient mobile app for Steem! With Partiko, you can easily see what’s going on in the Steem community, make posts and comments (no beneficiary cut forever!), and always stayed connected with your followers via push notification!\n\nPartiko also rewards you with Partiko Points (3000 Partiko Point bonus when you first use it!), and Partiko Points can be converted into Steem tokens. You can earn Partiko Points easily by making posts and comments using Partiko.\n\nWe also noticed that your Steem Power is low. We will be very happy to delegate 15 Steem Power to you once you have made a post using Partiko! With more Steem Power, you can make more posts and comments, and earn more rewards!\n\nIf that all sounds interesting, you can: \n\n- Download Partiko Android at [Google Play](http://bit.ly/2SRFIta)\n- Or Download Partiko iOS on the [App Store](https://apple.co/2PcXkSd)\n\nThank you so much for reading this message!",
"json_metadata": "{\"app\":\"partiko\"}",
"parent_author": "eriksank",
"parent_permlink": "what-is-the-effect-of-democracy-on-women",
"permlink": "partiko-re-eriksank-what-is-the-effect-of-democracy-on-women-20190118t074157670z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2019-01-18T07:41:57",
"trx_id": "544a22b14d3eaa16519d4585ab4e4f88f0da7d49",
"trx_in_block": 5,
"virtual_op": 0
}2019/01/07 14:48:36
2019/01/07 14:48:36
| author | eriksank |
| permlink | how-to-provide-liquidity-on-the-bitcoin-lightning-network-for-incoming-payments |
| voter | philabsurd |
| weight | 10000 (100.00%) |
| Transaction Info | Block #29249520/Trx c2969b8b7ebadabff91c1bc5f1e56223ce73cbea |
View Raw JSON Data
{
"block": 29249520,
"op": [
"vote",
{
"author": "eriksank",
"permlink": "how-to-provide-liquidity-on-the-bitcoin-lightning-network-for-incoming-payments",
"voter": "philabsurd",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2019-01-07T14:48:36",
"trx_id": "c2969b8b7ebadabff91c1bc5f1e56223ce73cbea",
"trx_in_block": 10,
"virtual_op": 0
}2019/01/06 21:13:30
2019/01/06 21:13:30
| author | steemitboard |
| body | Congratulations @eriksank! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@eriksank/birthday1.png</td><td>1 Year on Steemit</td></tr></table> <sub>_[Click here to view your Board](https://steemitboard.com/@eriksank)_</sub> > Support [SteemitBoard's project](https://steemit.com/@steemitboard)! **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| parent author | eriksank |
| parent permlink | what-is-the-effect-of-democracy-on-women |
| permlink | steemitboard-notify-eriksank-20190106t211330000z |
| title | |
| Transaction Info | Block #29228430/Trx cdecf378b6930e46413e3c41f7e3102b9823efb2 |
View Raw JSON Data
{
"block": 29228430,
"op": [
"comment",
{
"author": "steemitboard",
"body": "Congratulations @eriksank! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@eriksank/birthday1.png</td><td>1 Year on Steemit</td></tr></table>\n\n<sub>_[Click here to view your Board](https://steemitboard.com/@eriksank)_</sub>\n\n\n> Support [SteemitBoard's project](https://steemit.com/@steemitboard)! **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}",
"parent_author": "eriksank",
"parent_permlink": "what-is-the-effect-of-democracy-on-women",
"permlink": "steemitboard-notify-eriksank-20190106t211330000z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2019-01-06T21:13:30",
"trx_id": "cdecf378b6930e46413e3c41f7e3102b9823efb2",
"trx_in_block": 15,
"virtual_op": 0
}raise-me-upupvoted (0.01%) @eriksank / what-is-the-effect-of-democracy-on-women2018/12/19 01:37:42
raise-me-upupvoted (0.01%) @eriksank / what-is-the-effect-of-democracy-on-women
2018/12/19 01:37:42
| author | eriksank |
| permlink | what-is-the-effect-of-democracy-on-women |
| voter | raise-me-up |
| weight | 1 (0.01%) |
| Transaction Info | Block #28686935/Trx a04e65d2abfa27e2baef4ffd364560aa40a2dc0a |
View Raw JSON Data
{
"block": 28686935,
"op": [
"vote",
{
"author": "eriksank",
"permlink": "what-is-the-effect-of-democracy-on-women",
"voter": "raise-me-up",
"weight": 1
}
],
"op_in_trx": 0,
"timestamp": "2018-12-19T01:37:42",
"trx_id": "a04e65d2abfa27e2baef4ffd364560aa40a2dc0a",
"trx_in_block": 2,
"virtual_op": 0
}fyrstikkenupvoted (1.00%) @eriksank / what-is-the-effect-of-democracy-on-women2018/12/19 01:37:06
fyrstikkenupvoted (1.00%) @eriksank / what-is-the-effect-of-democracy-on-women
2018/12/19 01:37:06
| author | eriksank |
| permlink | what-is-the-effect-of-democracy-on-women |
| voter | fyrstikken |
| weight | 100 (1.00%) |
| Transaction Info | Block #28686923/Trx ca200d82c57498b873edfc46156e364f368bb100 |
View Raw JSON Data
{
"block": 28686923,
"op": [
"vote",
{
"author": "eriksank",
"permlink": "what-is-the-effect-of-democracy-on-women",
"voter": "fyrstikken",
"weight": 100
}
],
"op_in_trx": 0,
"timestamp": "2018-12-19T01:37:06",
"trx_id": "ca200d82c57498b873edfc46156e364f368bb100",
"trx_in_block": 0,
"virtual_op": 0
}eriksankpublished a new post: what-is-the-effect-of-democracy-on-women2018/12/19 01:21:03
eriksankpublished a new post: what-is-the-effect-of-democracy-on-women
2018/12/19 01:21:03
| author | eriksank |
| body | In a democracy, women will increasingly say that they do not need men. A woman needs a man like a fish needs a bicycle. This is actually quite true, because they can usually get the government to give them money. Still, how does the government get money? Well, obviously, by levying taxes on the men. |
| json metadata | {"tags":["life"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | life |
| permlink | what-is-the-effect-of-democracy-on-women |
| title | What is the effect of democracy on women? |
| Transaction Info | Block #28686602/Trx b3ed4c202f41cb214bd34a1bbbd0229f5b026efc |
View Raw JSON Data
{
"block": 28686602,
"op": [
"comment",
{
"author": "eriksank",
"body": "In a democracy, women will increasingly say that they do not need men.\nA woman needs a man like a fish needs a bicycle.\nThis is actually quite true, because they can usually get the government to give them money.\nStill, how does the government get money?\nWell, obviously, by levying taxes on the men.",
"json_metadata": "{\"tags\":[\"life\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "life",
"permlink": "what-is-the-effect-of-democracy-on-women",
"title": "What is the effect of democracy on women?"
}
],
"op_in_trx": 0,
"timestamp": "2018-12-19T01:21:03",
"trx_id": "b3ed4c202f41cb214bd34a1bbbd0229f5b026efc",
"trx_in_block": 28,
"virtual_op": 0
}2018/12/17 06:41:57
2018/12/17 06:41:57
| delegatee | eriksank |
| delegator | steem |
| vesting shares | 29150.809554 VESTS |
| Transaction Info | Block #28635475/Trx b51222a9340b4b94c004eaf26b260205559d0a17 |
View Raw JSON Data
{
"block": 28635475,
"op": [
"delegate_vesting_shares",
{
"delegatee": "eriksank",
"delegator": "steem",
"vesting_shares": "29150.809554 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2018-12-17T06:41:57",
"trx_id": "b51222a9340b4b94c004eaf26b260205559d0a17",
"trx_in_block": 9,
"virtual_op": 0
}eriksankupvoted (100.00%) @neshghi / contemporary-legal-rullings-in-islam2018/12/17 05:54:15
eriksankupvoted (100.00%) @neshghi / contemporary-legal-rullings-in-islam
2018/12/17 05:54:15
| author | neshghi |
| permlink | contemporary-legal-rullings-in-islam |
| voter | eriksank |
| weight | 10000 (100.00%) |
| Transaction Info | Block #28634521/Trx 0ae68535b1bb2b630dd912dc97f67a802af0ed6f |
View Raw JSON Data
{
"block": 28634521,
"op": [
"vote",
{
"author": "neshghi",
"permlink": "contemporary-legal-rullings-in-islam",
"voter": "eriksank",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-12-17T05:54:15",
"trx_id": "0ae68535b1bb2b630dd912dc97f67a802af0ed6f",
"trx_in_block": 7,
"virtual_op": 0
}2018/12/17 05:54:03
2018/12/17 05:54:03
| author | eriksank |
| body | Excellent post! I understand it, but I assume that the terminology may be inaccessible to novices and newbies of Islamic law. Over the years, I also discovered that the subject is surprisingly technical. |
| json metadata | {"tags":["contemporary"],"app":"steemit/0.1"} |
| parent author | neshghi |
| parent permlink | contemporary-legal-rullings-in-islam |
| permlink | re-neshghi-contemporary-legal-rullings-in-islam-20181217t055357778z |
| title | |
| Transaction Info | Block #28634517/Trx 27d302b7e1e73c91751fb6119afb404c19a9d821 |
View Raw JSON Data
{
"block": 28634517,
"op": [
"comment",
{
"author": "eriksank",
"body": "Excellent post! I understand it, but I assume that the terminology may be inaccessible to novices and newbies of Islamic law. Over the years, I also discovered that the subject is surprisingly technical.",
"json_metadata": "{\"tags\":[\"contemporary\"],\"app\":\"steemit/0.1\"}",
"parent_author": "neshghi",
"parent_permlink": "contemporary-legal-rullings-in-islam",
"permlink": "re-neshghi-contemporary-legal-rullings-in-islam-20181217t055357778z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2018-12-17T05:54:03",
"trx_id": "27d302b7e1e73c91751fb6119afb404c19a9d821",
"trx_in_block": 3,
"virtual_op": 0
}2018/07/13 08:46:09
2018/07/13 08:46:09
| delegatee | eriksank |
| delegator | steem |
| vesting shares | 9119.397520 VESTS |
| Transaction Info | Block #24135162/Trx 255d26296cfc6a7b87a839698cbcffd8d60a79d5 |
View Raw JSON Data
{
"block": 24135162,
"op": [
"delegate_vesting_shares",
{
"delegatee": "eriksank",
"delegator": "steem",
"vesting_shares": "9119.397520 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2018-07-13T08:46:09",
"trx_id": "255d26296cfc6a7b87a839698cbcffd8d60a79d5",
"trx_in_block": 55,
"virtual_op": 0
}2018/05/18 19:20:00
2018/05/18 19:20:00
| delegatee | eriksank |
| delegator | steem |
| vesting shares | 29495.220792 VESTS |
| Transaction Info | Block #22546292/Trx a89ec938856c2b17443c174ff11170c25ba6a0f1 |
View Raw JSON Data
{
"block": 22546292,
"op": [
"delegate_vesting_shares",
{
"delegatee": "eriksank",
"delegator": "steem",
"vesting_shares": "29495.220792 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2018-05-18T19:20:00",
"trx_id": "a89ec938856c2b17443c174ff11170c25ba6a0f1",
"trx_in_block": 25,
"virtual_op": 0
}eriksankupvoted (100.00%) @tiferet / trading-in-cryptocurrencies-and-the-requirements-of-religious-law2018/04/13 06:11:03
eriksankupvoted (100.00%) @tiferet / trading-in-cryptocurrencies-and-the-requirements-of-religious-law
2018/04/13 06:11:03
| author | tiferet |
| permlink | trading-in-cryptocurrencies-and-the-requirements-of-religious-law |
| voter | eriksank |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21523352/Trx 197205f2a875aa5e7975e76a97a3b669b0c24de5 |
View Raw JSON Data
{
"block": 21523352,
"op": [
"vote",
{
"author": "tiferet",
"permlink": "trading-in-cryptocurrencies-and-the-requirements-of-religious-law",
"voter": "eriksank",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-13T06:11:03",
"trx_id": "197205f2a875aa5e7975e76a97a3b669b0c24de5",
"trx_in_block": 43,
"virtual_op": 0
}marciolinaupvoted (100.00%) @eriksank / trading-in-cryptocurrencies-and-the-requirements-of-religious-law2018/04/12 13:57:30
marciolinaupvoted (100.00%) @eriksank / trading-in-cryptocurrencies-and-the-requirements-of-religious-law
2018/04/12 13:57:30
| author | eriksank |
| permlink | trading-in-cryptocurrencies-and-the-requirements-of-religious-law |
| voter | marciolina |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21503885/Trx 41975dd40d646190a11f95fd57cda1caa29e66c3 |
View Raw JSON Data
{
"block": 21503885,
"op": [
"vote",
{
"author": "eriksank",
"permlink": "trading-in-cryptocurrencies-and-the-requirements-of-religious-law",
"voter": "marciolina",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-12T13:57:30",
"trx_id": "41975dd40d646190a11f95fd57cda1caa29e66c3",
"trx_in_block": 52,
"virtual_op": 0
}simona2001upvoted (100.00%) @eriksank / trading-in-cryptocurrencies-and-the-requirements-of-religious-law2018/04/12 13:57:30
simona2001upvoted (100.00%) @eriksank / trading-in-cryptocurrencies-and-the-requirements-of-religious-law
2018/04/12 13:57:30
| author | eriksank |
| permlink | trading-in-cryptocurrencies-and-the-requirements-of-religious-law |
| voter | simona2001 |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21503885/Trx c68bc6f9aa8e4a446b4e91816ddeecc10b95c4dc |
View Raw JSON Data
{
"block": 21503885,
"op": [
"vote",
{
"author": "eriksank",
"permlink": "trading-in-cryptocurrencies-and-the-requirements-of-religious-law",
"voter": "simona2001",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-12T13:57:30",
"trx_id": "c68bc6f9aa8e4a446b4e91816ddeecc10b95c4dc",
"trx_in_block": 26,
"virtual_op": 0
}2018/04/12 13:57:30
2018/04/12 13:57:30
| author | eriksank |
| permlink | trading-in-cryptocurrencies-and-the-requirements-of-religious-law |
| voter | stinelintemana |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21503885/Trx 3c0d5da057123bf5bfb24098c3aee09d2b9398e6 |
View Raw JSON Data
{
"block": 21503885,
"op": [
"vote",
{
"author": "eriksank",
"permlink": "trading-in-cryptocurrencies-and-the-requirements-of-religious-law",
"voter": "stinelintemana",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-12T13:57:30",
"trx_id": "3c0d5da057123bf5bfb24098c3aee09d2b9398e6",
"trx_in_block": 8,
"virtual_op": 0
}ohanakazupvoted (100.00%) @eriksank / trading-in-cryptocurrencies-and-the-requirements-of-religious-law2018/04/12 13:57:27
ohanakazupvoted (100.00%) @eriksank / trading-in-cryptocurrencies-and-the-requirements-of-religious-law
2018/04/12 13:57:27
| author | eriksank |
| permlink | trading-in-cryptocurrencies-and-the-requirements-of-religious-law |
| voter | ohanakaz |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21503884/Trx 70aab2171bef00cf6b5eadc745d7edd8b8c58d5c |
View Raw JSON Data
{
"block": 21503884,
"op": [
"vote",
{
"author": "eriksank",
"permlink": "trading-in-cryptocurrencies-and-the-requirements-of-religious-law",
"voter": "ohanakaz",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-12T13:57:27",
"trx_id": "70aab2171bef00cf6b5eadc745d7edd8b8c58d5c",
"trx_in_block": 40,
"virtual_op": 0
}2018/04/12 13:57:27
2018/04/12 13:57:27
| author | eriksank |
| permlink | trading-in-cryptocurrencies-and-the-requirements-of-religious-law |
| voter | muravevamarina |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21503884/Trx e7e69801b7e3770af8194113ff372640ce7366eb |
View Raw JSON Data
{
"block": 21503884,
"op": [
"vote",
{
"author": "eriksank",
"permlink": "trading-in-cryptocurrencies-and-the-requirements-of-religious-law",
"voter": "muravevamarina",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-12T13:57:27",
"trx_id": "e7e69801b7e3770af8194113ff372640ce7366eb",
"trx_in_block": 20,
"virtual_op": 0
}ypikulinaupvoted (100.00%) @eriksank / trading-in-cryptocurrencies-and-the-requirements-of-religious-law2018/04/12 13:57:12
ypikulinaupvoted (100.00%) @eriksank / trading-in-cryptocurrencies-and-the-requirements-of-religious-law
2018/04/12 13:57:12
| author | eriksank |
| permlink | trading-in-cryptocurrencies-and-the-requirements-of-religious-law |
| voter | ypikulina |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21503879/Trx c5c9e93d5f8ed494ca737c4500ea69ee0dac09a9 |
View Raw JSON Data
{
"block": 21503879,
"op": [
"vote",
{
"author": "eriksank",
"permlink": "trading-in-cryptocurrencies-and-the-requirements-of-religious-law",
"voter": "ypikulina",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-12T13:57:12",
"trx_id": "c5c9e93d5f8ed494ca737c4500ea69ee0dac09a9",
"trx_in_block": 49,
"virtual_op": 0
}demnewaupvoted (100.00%) @eriksank / trading-in-cryptocurrencies-and-the-requirements-of-religious-law2018/04/12 13:57:09
demnewaupvoted (100.00%) @eriksank / trading-in-cryptocurrencies-and-the-requirements-of-religious-law
2018/04/12 13:57:09
| author | eriksank |
| permlink | trading-in-cryptocurrencies-and-the-requirements-of-religious-law |
| voter | demnewa |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21503878/Trx 04cfd798ce31202088b9b4bbc3e8c2937e729f7a |
View Raw JSON Data
{
"block": 21503878,
"op": [
"vote",
{
"author": "eriksank",
"permlink": "trading-in-cryptocurrencies-and-the-requirements-of-religious-law",
"voter": "demnewa",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-12T13:57:09",
"trx_id": "04cfd798ce31202088b9b4bbc3e8c2937e729f7a",
"trx_in_block": 3,
"virtual_op": 0
}2018/04/12 08:13:21
2018/04/12 08:13:21
| author | eriksank |
| permlink | trading-in-cryptocurrencies-and-the-requirements-of-religious-law |
| voter | foxicoreviews |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21497004/Trx 0ada7afdb32e613783838a31cedc101f0f4f5ba6 |
View Raw JSON Data
{
"block": 21497004,
"op": [
"vote",
{
"author": "eriksank",
"permlink": "trading-in-cryptocurrencies-and-the-requirements-of-religious-law",
"voter": "foxicoreviews",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-12T08:13:21",
"trx_id": "0ada7afdb32e613783838a31cedc101f0f4f5ba6",
"trx_in_block": 32,
"virtual_op": 0
}eriksankpublished a new post: trading-in-cryptocurrencies-and-the-requirements-of-religious-law2018/04/12 07:39:39
eriksankpublished a new post: trading-in-cryptocurrencies-and-the-requirements-of-religious-law
2018/04/12 07:39:39
| author | eriksank |
| body | @@ -3820,16 +3820,18 @@ %0A%0A**NOTE + 1 :** I ju @@ -4026,8 +4026,254 @@ chedule. +%0A%0A**NOTE 2:** It is obvious that it is advisable to review non-standard trading strategies with _ulema/religious scholars_ on their permissibility in religious law, especially with regards to _gharar-maysir/speculation-gambling_ and _riba/usury_. |
| json metadata | {"tags":["bitcoin","cryptocurrency","religion"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | bitcoin |
| permlink | trading-in-cryptocurrencies-and-the-requirements-of-religious-law |
| title | Trading in cryptocurrencies and the requirements of religious law |
| Transaction Info | Block #21496330/Trx c8fdb02e78fe8f587eae0bdc0ce2a0cda7f3eeed |
View Raw JSON Data
{
"block": 21496330,
"op": [
"comment",
{
"author": "eriksank",
"body": "@@ -3820,16 +3820,18 @@\n %0A%0A**NOTE\n+ 1\n :** I ju\n@@ -4026,8 +4026,254 @@\n chedule.\n+%0A%0A**NOTE 2:** It is obvious that it is advisable to review non-standard trading strategies with _ulema/religious scholars_ on their permissibility in religious law, especially with regards to _gharar-maysir/speculation-gambling_ and _riba/usury_.\n",
"json_metadata": "{\"tags\":[\"bitcoin\",\"cryptocurrency\",\"religion\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "bitcoin",
"permlink": "trading-in-cryptocurrencies-and-the-requirements-of-religious-law",
"title": "Trading in cryptocurrencies and the requirements of religious law"
}
],
"op_in_trx": 0,
"timestamp": "2018-04-12T07:39:39",
"trx_id": "c8fdb02e78fe8f587eae0bdc0ce2a0cda7f3eeed",
"trx_in_block": 7,
"virtual_op": 0
}2018/04/12 07:37:48
2018/04/12 07:37:48
| author | tiferet |
| body | The Tree of Life, or Etz haChayim (עץ החיים) has upvoted you with divine emanations of G-ds creation itself ex nihilo. We reveal Light by transforming our Desire to Receive for Ourselves to a Desire to Receive for Others. I am part of the Curators Guild (Sephiroth), through which Ein Sof (The Infinite) reveals Itself! |
| json metadata | |
| parent author | eriksank |
| parent permlink | trading-in-cryptocurrencies-and-the-requirements-of-religious-law |
| permlink | trading-in-cryptocurrencies-and-the-requirements-of-religious-law |
| title | Sephiroth! |
| Transaction Info | Block #21496293/Trx 23dfa9aedc80a36c8242f70a3af2f0980c8c3989 |
View Raw JSON Data
{
"block": 21496293,
"op": [
"comment",
{
"author": "tiferet",
"body": "The Tree of Life, or Etz haChayim (עץ החיים) has upvoted you with divine emanations of G-ds creation itself ex nihilo. We reveal Light by transforming our Desire to Receive for Ourselves to a Desire to Receive for Others. I am part of the Curators Guild (Sephiroth), through which Ein Sof (The Infinite) reveals Itself!",
"json_metadata": "",
"parent_author": "eriksank",
"parent_permlink": "trading-in-cryptocurrencies-and-the-requirements-of-religious-law",
"permlink": "trading-in-cryptocurrencies-and-the-requirements-of-religious-law",
"title": "Sephiroth!"
}
],
"op_in_trx": 0,
"timestamp": "2018-04-12T07:37:48",
"trx_id": "23dfa9aedc80a36c8242f70a3af2f0980c8c3989",
"trx_in_block": 26,
"virtual_op": 0
}2018/04/12 07:37:45
2018/04/12 07:37:45
| author | eriksank |
| permlink | trading-in-cryptocurrencies-and-the-requirements-of-religious-law |
| voter | tiferet |
| weight | 5000 (50.00%) |
| Transaction Info | Block #21496292/Trx cf5224efbdda6d4da11f2b3ac0776c4c6ae8ec33 |
View Raw JSON Data
{
"block": 21496292,
"op": [
"vote",
{
"author": "eriksank",
"permlink": "trading-in-cryptocurrencies-and-the-requirements-of-religious-law",
"voter": "tiferet",
"weight": 5000
}
],
"op_in_trx": 0,
"timestamp": "2018-04-12T07:37:45",
"trx_id": "cf5224efbdda6d4da11f2b3ac0776c4c6ae8ec33",
"trx_in_block": 9,
"virtual_op": 0
}eriksankpublished a new post: trading-in-cryptocurrencies-and-the-requirements-of-religious-law2018/04/12 07:36:51
eriksankpublished a new post: trading-in-cryptocurrencies-and-the-requirements-of-religious-law
2018/04/12 07:36:51
| author | eriksank |
| body | @@ -3804,16 +3804,228 @@ ect to _jiziah_. +%0A%0A**NOTE:** I just got the remark that I forgot to mention that _sadaqah_ i.e. _extra/general charitable contributions_ are always permitted independent of the standard zakaat appropriation/contribution schedule. |
| json metadata | {"tags":["bitcoin","cryptocurrency","religion"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | bitcoin |
| permlink | trading-in-cryptocurrencies-and-the-requirements-of-religious-law |
| title | Trading in cryptocurrencies and the requirements of religious law |
| Transaction Info | Block #21496274/Trx 2b4c16a13e5a1685bb1797505a8369e7571cafdf |
View Raw JSON Data
{
"block": 21496274,
"op": [
"comment",
{
"author": "eriksank",
"body": "@@ -3804,16 +3804,228 @@\n ect to _jiziah_.\n+%0A%0A**NOTE:** I just got the remark that I forgot to mention that _sadaqah_ i.e. _extra/general charitable contributions_ are always permitted independent of the standard zakaat appropriation/contribution schedule.\n",
"json_metadata": "{\"tags\":[\"bitcoin\",\"cryptocurrency\",\"religion\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "bitcoin",
"permlink": "trading-in-cryptocurrencies-and-the-requirements-of-religious-law",
"title": "Trading in cryptocurrencies and the requirements of religious law"
}
],
"op_in_trx": 0,
"timestamp": "2018-04-12T07:36:51",
"trx_id": "2b4c16a13e5a1685bb1797505a8369e7571cafdf",
"trx_in_block": 41,
"virtual_op": 0
}eriksankpublished a new post: trading-in-cryptocurrencies-and-the-requirements-of-religious-law2018/04/12 05:33:57
eriksankpublished a new post: trading-in-cryptocurrencies-and-the-requirements-of-religious-law
2018/04/12 05:33:57
| author | eriksank |
| body | I have had a long conversation yesterday with someone about trading in cryptocurrencies and the requirements of religious law. The person is generally a keeper of religious law, but he was still inadvertently and unknowingly involved in behaviour that is forbidden in religious law. Even though religious law is quite similar in Judaism, Christianity, and Islam, it has also become clear to me that only Islamic law is axiomatic and mechanical. Its rules are effectively calculable. David Hilbert's pernicious _Entscheidungsproblem_ about the predicate function _isMoral(behaviour)_ does not seem to occur in Sharia. Christianity, on the other hand, has the problem of the _living magisterium_ of the Church, where religious law is not fixed until the very point at which the clergy has interpreted and adjudicated it. In Christianity, the law is not an axiomatic or mechanical device. That problem has historically yielded a lot of trouble in Christianity. Cfr. the notorious event in Worms, Germany, where Martin Luther's argument through _scripture and reason_ was rejected by the Papacy on grounds that _the Bible itself is the arsenal whence each heresiarch has drawn his deceptive arguments_. The outcome of the conflict in Worms, Germany, firmly establishes the idea in Christianity that the scriptures are not a valid source of law in absence of centralized, hierarchical re-interpretation. Lack of consistency is also never a valid ground for challenging clerical authority. Therefore, for _interpretation/tafsir_ and _jurisprudence/fiqh_, I always fall back on Islamic law and its entirely mechanical devices, where every axiomatic derivation from scripture is always accepted as valid, subject to verification leading up to _consensus/ijma_. A _hodling_ trading strategy is an approach in which the cryptocurrency holder does not trade. He just keeps his savings away from the thieving and usury-infested hands of the fiat banksters. This strategy is obviously valid. _Hodling_ amounts to _doing nothing_, while _doing nothing_ with an asset is obviously permitted in religious law, on the condition that the hodler pays _charity contributions/zakaat_ to the tune of 2.5% of his stash. For example, if you hodl 10 BTC, you are supposed to give away 2.5% = 0.25 BTC to the poor, the needy, the stranded travelers or a few other categories of legitimate zakaat recipients (8 in total). The Zakaat levy is final and no new requirements can exist for this stash. A second trading strategy is one in which the cryptocurrency holder seeks to buy at a discount, say 100%-5%=95%, and sells at a premium, say 100%+5%=105%. He makes money from flipping the coins around the spread. This liquidity-providing, market-making strategy does not assume anything about future prices. Hence, it is not a form _speculation-gambling/gharar-maysir_. Furthermore, one currency is always traded for a different one, and never for itself (such as in derivatives). Hence, there is also no risk of _riba/usury_. Other trading strategies may or may not be permitted in religious law. There is, however, always this concern about _speculation-gambling/gharar-maysir_ and _usury/riba_. Your alternative trading strategy must never assume future prices. If your trading strategy only makes money when the market prices go up/down, then it may be _speculation-gambling/gharar-maysir_, which is prohibited in religious law. It is really important to pay _zakaat/voluntary charity contributions_, if only, because it spares you from paying _jiziah/taxes to the heathens_, such as personal income tax or capital gains tax. The _non bis in idem_ ("not two times on the same") taxation principle will cover your approach. Religious law insists that zakaat payers are exempt from _jiziah_. Only the heathens are subject to _jiziah_. |
| json metadata | {"tags":["bitcoin","cryptocurrency","religion"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | bitcoin |
| permlink | trading-in-cryptocurrencies-and-the-requirements-of-religious-law |
| title | Trading in cryptocurrencies and the requirements of religious law |
| Transaction Info | Block #21493817/Trx 69ac18c82127216790253e2c52f6df0588700b02 |
View Raw JSON Data
{
"block": 21493817,
"op": [
"comment",
{
"author": "eriksank",
"body": "I have had a long conversation yesterday with someone about trading in cryptocurrencies and the requirements of religious law. The person is generally a keeper of religious law, but he was still inadvertently and unknowingly involved in behaviour that is forbidden in religious law.\n\nEven though religious law is quite similar in Judaism, Christianity, and Islam, it has also become clear to me that only Islamic law is axiomatic and mechanical. Its rules are effectively calculable. David Hilbert's pernicious _Entscheidungsproblem_ about the predicate function _isMoral(behaviour)_ does not seem to occur in Sharia.\n\nChristianity, on the other hand, has the problem of the _living magisterium_ of the Church, where religious law is not fixed until the very point at which the clergy has interpreted and adjudicated it. In Christianity, the law is not an axiomatic or mechanical device.\n\nThat problem has historically yielded a lot of trouble in Christianity. Cfr. the notorious event in Worms, Germany, where Martin Luther's argument through _scripture and reason_ was rejected by the Papacy on grounds that _the Bible itself is the arsenal whence each heresiarch has drawn his deceptive arguments_.\n\nThe outcome of the conflict in Worms, Germany, firmly establishes the idea in Christianity that the scriptures are not a valid source of law in absence of centralized, hierarchical re-interpretation. Lack of consistency is also never a valid ground for challenging clerical authority.\n\nTherefore, for _interpretation/tafsir_ and _jurisprudence/fiqh_, I always fall back on Islamic law and its entirely mechanical devices, where every axiomatic derivation from scripture is always accepted as valid, subject to verification leading up to _consensus/ijma_.\n\nA _hodling_ trading strategy is an approach in which the cryptocurrency holder does not trade. He just keeps his savings away from the thieving and usury-infested hands of the fiat banksters. This strategy is obviously valid. _Hodling_ amounts to _doing nothing_, while _doing nothing_ with an asset is obviously permitted in religious law, on the condition that the hodler pays _charity contributions/zakaat_ to the tune of 2.5% of his stash.\n\nFor example, if you hodl 10 BTC, you are supposed to give away 2.5% = 0.25 BTC to the poor, the needy, the stranded travelers or a few other categories of legitimate zakaat recipients (8 in total). The Zakaat levy is final and no new requirements can exist for this stash.\n\nA second trading strategy is one in which the cryptocurrency holder seeks to buy at a discount, say 100%-5%=95%, and sells at a premium, say 100%+5%=105%. He makes money from flipping the coins around the spread.\n\nThis liquidity-providing, market-making strategy does not assume anything about future prices. Hence, it is not a form _speculation-gambling/gharar-maysir_. Furthermore, one currency is always traded for a different one, and never for itself (such as in derivatives). Hence, there is also no risk of _riba/usury_.\n\nOther trading strategies may or may not be permitted in religious law.\n\nThere is, however, always this concern about _speculation-gambling/gharar-maysir_ and _usury/riba_. Your alternative trading strategy must never assume future prices. If your trading strategy only makes money when the market prices go up/down, then it may be _speculation-gambling/gharar-maysir_, which is prohibited in religious law.\n\nIt is really important to pay _zakaat/voluntary charity contributions_, if only, because it spares you from paying _jiziah/taxes to the heathens_, such as personal income tax or capital gains tax.\n\nThe _non bis in idem_ (\"not two times on the same\") taxation principle will cover your approach. Religious law insists that zakaat payers are exempt from _jiziah_. Only the heathens are subject to _jiziah_.",
"json_metadata": "{\"tags\":[\"bitcoin\",\"cryptocurrency\",\"religion\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "bitcoin",
"permlink": "trading-in-cryptocurrencies-and-the-requirements-of-religious-law",
"title": "Trading in cryptocurrencies and the requirements of religious law"
}
],
"op_in_trx": 0,
"timestamp": "2018-04-12T05:33:57",
"trx_id": "69ac18c82127216790253e2c52f6df0588700b02",
"trx_in_block": 29,
"virtual_op": 0
}eriksankpublished a new post: my-negative-answer-to-the-papacy-because-he-is-only-making-the-problem-worse2018/04/07 10:28:21
eriksankpublished a new post: my-negative-answer-to-the-papacy-because-he-is-only-making-the-problem-worse
2018/04/07 10:28:21
| author | eriksank |
| body | > The economy - [the Pope warned](http://www.lastampa.it/2018/04/07/vaticaninsider/eng/world-news/the-popes-appeal-to-economists-to-reject-an-economy-of-exclusion-ZwXu8RgTq0ELuLV5rqB8rL/pagina.html) - cannot attempt only to increase profits by reducing the work force and thereby adding to the ranks of the excluded. It must follow the path marked out by business leaders, politicians, thinkers, and leaders in society who place the human person in first place, and do everything possible to ensure that there are opportunities of dignified work. Let us raise our voices together, asking that economists may have the courage to reject an economy of exclusion and know how to open new paths. This is not the first time that we live through a massive transformation. When in the 19th century the subsistence farmers started joining the industrial economy, it also caused an upheaval. Concerning "_It must follow the path marked out business leaders, politicians ..._", the papacy is naive to believe that anybody knows what the future state of the economy and the labour market will be. Read my lips: absolutely nobody knows. In those circumstances, central planning is simply absurd. Especially _politicians_. Seriously, what the hell do they know about where all of this is heading? Why ask exactly the biggest idiots for advice? The ongoing changes are fueled by technology. For heaven's sake, what do politicians understand about technology? Seriously, what do they understand about anything at all? Concerning "_The economy cannot attempt only to increase profits by reducing the work force ..._", I can only underline that morality is about forbidden/mandatory behaviours and never about outcomes. As Immanuel Kant pointed out in his _Kritik der reinen Vernunft_, all morality must consist of categorical imperatives. Hypothetical (outcome-based) imperatives are not allowed in morality, because their soundness ultimately always require access to the Theory of Everything; which we simply do not have. The papacy had better axiomatically derive his claims from religious law. The Papacy's disregard for religious law as an axiomatic foundation of morality disturbs me. What would be wrong about proceeding through scripture and reason? It is still the same mentality with which the erstwhile Papacy retorted to Martin Luther that "_the Bible itself is the arsenal whence each heretic has drawn his deceptive arguments_". Nobody knew what would happen when the subsistence farmers, in large numbers, morphed into industrial workers. Every form of upfront planning would have completely missed the ball, and would only have made the problem worse. |
| json metadata | {"tags":["christianity"],"links":["http://www.lastampa.it/2018/04/07/vaticaninsider/eng/world-news/the-popes-appeal-to-economists-to-reject-an-economy-of-exclusion-ZwXu8RgTq0ELuLV5rqB8rL/pagina.html"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | christianity |
| permlink | my-negative-answer-to-the-papacy-because-he-is-only-making-the-problem-worse |
| title | My negative answer to the Papacy, because he is only making the problem worse |
| Transaction Info | Block #21355716/Trx 46a29360240245a35a05e996f3c802781dd5e24d |
View Raw JSON Data
{
"block": 21355716,
"op": [
"comment",
{
"author": "eriksank",
"body": "> The economy - [the Pope warned](http://www.lastampa.it/2018/04/07/vaticaninsider/eng/world-news/the-popes-appeal-to-economists-to-reject-an-economy-of-exclusion-ZwXu8RgTq0ELuLV5rqB8rL/pagina.html) - cannot attempt only to increase profits by reducing the work force and thereby adding to the ranks of the excluded. It must follow the path marked out by business leaders, politicians, thinkers, and leaders in society who place the human person in first place, and do everything possible to ensure that there are opportunities of dignified work. Let us raise our voices together, asking that economists may have the courage to reject an economy of exclusion and know how to open new paths.\n\nThis is not the first time that we live through a massive transformation. When in the 19th century the subsistence farmers started joining the industrial economy, it also caused an upheaval.\n\nConcerning \"_It must follow the path marked out business leaders, politicians ..._\", the papacy is naive to believe that anybody knows what the future state of the economy and the labour market will be. Read my lips: absolutely nobody knows. In those circumstances, central planning is simply absurd.\n\nEspecially _politicians_. Seriously, what the hell do they know about where all of this is heading? Why ask exactly the biggest idiots for advice? The ongoing changes are fueled by technology. For heaven's sake, what do politicians understand about technology? Seriously, what do they understand about anything at all?\n\nConcerning \"_The economy cannot attempt only to increase profits by reducing the work force ..._\", I can only underline that morality is about forbidden/mandatory behaviours and never about outcomes. As Immanuel Kant pointed out in his _Kritik der reinen Vernunft_, all morality must consist of categorical imperatives. Hypothetical (outcome-based) imperatives are not allowed in morality, because their soundness ultimately always require access to the Theory of Everything; which we simply do not have.\n\nThe papacy had better axiomatically derive his claims from religious law.\n\nThe Papacy's disregard for religious law as an axiomatic foundation of morality disturbs me. What would be wrong about proceeding through scripture and reason?\n\nIt is still the same mentality with which the erstwhile Papacy retorted to Martin Luther that \"_the Bible itself is the arsenal whence each heretic has drawn his deceptive arguments_\".\n\nNobody knew what would happen when the subsistence farmers, in large numbers, morphed into industrial workers. Every form of upfront planning would have completely missed the ball, and would only have made the problem worse.",
"json_metadata": "{\"tags\":[\"christianity\"],\"links\":[\"http://www.lastampa.it/2018/04/07/vaticaninsider/eng/world-news/the-popes-appeal-to-economists-to-reject-an-economy-of-exclusion-ZwXu8RgTq0ELuLV5rqB8rL/pagina.html\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "christianity",
"permlink": "my-negative-answer-to-the-papacy-because-he-is-only-making-the-problem-worse",
"title": "My negative answer to the Papacy, because he is only making the problem worse"
}
],
"op_in_trx": 0,
"timestamp": "2018-04-07T10:28:21",
"trx_id": "46a29360240245a35a05e996f3c802781dd5e24d",
"trx_in_block": 67,
"virtual_op": 0
}2018/03/21 14:48:18
2018/03/21 14:48:18
| author | eriksank |
| permlink | the-schools-are-indeed-sending-the-kids-straight-to-the-unemployment-queue-but-that-is-not-even-the-worst-problem |
| voter | olireads |
| weight | 10000 (100.00%) |
| Transaction Info | Block #20871814/Trx 2b951b0cec3503b08f6da69e4c242ca4abca5d30 |
View Raw JSON Data
{
"block": 20871814,
"op": [
"vote",
{
"author": "eriksank",
"permlink": "the-schools-are-indeed-sending-the-kids-straight-to-the-unemployment-queue-but-that-is-not-even-the-worst-problem",
"voter": "olireads",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-03-21T14:48:18",
"trx_id": "2b951b0cec3503b08f6da69e4c242ca4abca5d30",
"trx_in_block": 39,
"virtual_op": 0
}eriksankreceived 0.084 SBD, 0.044 SP author reward for @eriksank / how-to-provide-liquidity-on-the-bitcoin-lightning-network-for-incoming-payments2018/03/12 06:57:21
eriksankreceived 0.084 SBD, 0.044 SP author reward for @eriksank / how-to-provide-liquidity-on-the-bitcoin-lightning-network-for-incoming-payments
2018/03/12 06:57:21
| author | eriksank |
| permlink | how-to-provide-liquidity-on-the-bitcoin-lightning-network-for-incoming-payments |
| sbd payout | 0.084 SBD |
| steem payout | 0.000 STEEM |
| vesting payout | 71.464355 VESTS |
| Transaction Info | Block #20603797/Virtual Operation #4 |
View Raw JSON Data
{
"block": 20603797,
"op": [
"author_reward",
{
"author": "eriksank",
"permlink": "how-to-provide-liquidity-on-the-bitcoin-lightning-network-for-incoming-payments",
"sbd_payout": "0.084 SBD",
"steem_payout": "0.000 STEEM",
"vesting_payout": "71.464355 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2018-03-12T06:57:21",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": 4
}eriksankreceived 0.092 SBD, 0.043 SP author reward for @eriksank / ddos-attack-on-github-mostly-documentation-and-or-migration-bugs2018/03/10 10:32:33
eriksankreceived 0.092 SBD, 0.043 SP author reward for @eriksank / ddos-attack-on-github-mostly-documentation-and-or-migration-bugs
2018/03/10 10:32:33
| author | eriksank |
| permlink | ddos-attack-on-github-mostly-documentation-and-or-migration-bugs |
| sbd payout | 0.092 SBD |
| steem payout | 0.000 STEEM |
| vesting payout | 69.429277 VESTS |
| Transaction Info | Block #20550610/Virtual Operation #16 |
View Raw JSON Data
{
"block": 20550610,
"op": [
"author_reward",
{
"author": "eriksank",
"permlink": "ddos-attack-on-github-mostly-documentation-and-or-migration-bugs",
"sbd_payout": "0.092 SBD",
"steem_payout": "0.000 STEEM",
"vesting_payout": "69.429277 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2018-03-10T10:32:33",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": 16
}eriksankpublished a new post: how-to-provide-liquidity-on-the-bitcoin-lightning-network-for-incoming-payments2018/03/07 12:03:36
eriksankpublished a new post: how-to-provide-liquidity-on-the-bitcoin-lightning-network-for-incoming-payments
2018/03/07 12:03:36
| author | eriksank |
| body | @@ -91,83 +91,123 @@ BTC -, while the channel counter-party does not need to put in any money at all +. The counter-party would have to fund his own outgoing channel with his counter-party, but that is another problem . Th |
| json metadata | {"tags":["bitcoin","technology","cryptocurrency"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | bitcoin |
| permlink | how-to-provide-liquidity-on-the-bitcoin-lightning-network-for-incoming-payments |
| title | How to provide liquidity on the bitcoin lightning network for incoming payments |
| Transaction Info | Block #20466148/Trx 0a8749fb8b838afd42454bd49c55d382737a6e0e |
View Raw JSON Data
{
"block": 20466148,
"op": [
"comment",
{
"author": "eriksank",
"body": "@@ -91,83 +91,123 @@\n BTC\n-, while the channel counter-party does not need to put in any money at all\n+. The counter-party would have to fund his own outgoing channel with his counter-party, but that is another problem\n . Th\n",
"json_metadata": "{\"tags\":[\"bitcoin\",\"technology\",\"cryptocurrency\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "bitcoin",
"permlink": "how-to-provide-liquidity-on-the-bitcoin-lightning-network-for-incoming-payments",
"title": "How to provide liquidity on the bitcoin lightning network for incoming payments"
}
],
"op_in_trx": 0,
"timestamp": "2018-03-07T12:03:36",
"trx_id": "0a8749fb8b838afd42454bd49c55d382737a6e0e",
"trx_in_block": 23,
"virtual_op": 0
}2018/03/05 10:17:21
2018/03/05 10:17:21
| author | eriksank |
| body | @@ -2566,13 +2566,10 @@ uch -about +of sex |
| json metadata | {"tags":["technology"],"links":["https://en.wikipedia.org/wiki/Don%27t_repeat_yourself","https://en.wikipedia.org/wiki/Entropy_(information_theory)","https://londonist.com/2016/09/the-londoners-who-offer-free-rent-for-sexual-favours","https://www.thesun.co.uk/fabulous/5437340/woman-who-used-sugar-daddy-to-pay-off-student-debt-says-its-a-fairytale-to-not-expect-to-swap-sex-for-cash"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | technology |
| permlink | the-schools-are-indeed-sending-the-kids-straight-to-the-unemployment-queue-but-that-is-not-even-the-worst-problem |
| title | The schools are indeed sending the kids straight to the unemployment queue but that is not even the worst problem |
| Transaction Info | Block #20406520/Trx c3cb3c735df74e72bcc0c8fff5d686e78b61a527 |
View Raw JSON Data
{
"block": 20406520,
"op": [
"comment",
{
"author": "eriksank",
"body": "@@ -2566,13 +2566,10 @@\n uch \n-about\n+of\n sex\n",
"json_metadata": "{\"tags\":[\"technology\"],\"links\":[\"https://en.wikipedia.org/wiki/Don%27t_repeat_yourself\",\"https://en.wikipedia.org/wiki/Entropy_(information_theory)\",\"https://londonist.com/2016/09/the-londoners-who-offer-free-rent-for-sexual-favours\",\"https://www.thesun.co.uk/fabulous/5437340/woman-who-used-sugar-daddy-to-pay-off-student-debt-says-its-a-fairytale-to-not-expect-to-swap-sex-for-cash\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "technology",
"permlink": "the-schools-are-indeed-sending-the-kids-straight-to-the-unemployment-queue-but-that-is-not-even-the-worst-problem",
"title": "The schools are indeed sending the kids straight to the unemployment queue but that is not even the worst problem"
}
],
"op_in_trx": 0,
"timestamp": "2018-03-05T10:17:21",
"trx_id": "c3cb3c735df74e72bcc0c8fff5d686e78b61a527",
"trx_in_block": 64,
"virtual_op": 0
}2018/03/05 09:11:24
2018/03/05 09:11:24
| author | eriksank |
| permlink | the-schools-are-indeed-sending-the-kids-straight-to-the-unemployment-queue-but-that-is-not-even-the-worst-problem |
| voter | eriksank |
| weight | 10000 (100.00%) |
| Transaction Info | Block #20405201/Trx 3e8d8a8aed9807cda2de7fc76f529f1e79c8bcff |
View Raw JSON Data
{
"block": 20405201,
"op": [
"vote",
{
"author": "eriksank",
"permlink": "the-schools-are-indeed-sending-the-kids-straight-to-the-unemployment-queue-but-that-is-not-even-the-worst-problem",
"voter": "eriksank",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-03-05T09:11:24",
"trx_id": "3e8d8a8aed9807cda2de7fc76f529f1e79c8bcff",
"trx_in_block": 34,
"virtual_op": 0
}2018/03/05 09:11:24
2018/03/05 09:11:24
| author | eriksank |
| body | Technology has primarily, and still displaces, assembly-line workers and paper pushers. Anybody repeating the same operation all over again, especially within the same workday, will eventually find himself displaced. Another problem is that other jobs in which you can keep repeating the same operation all over again throughout the day, are also being automated away. What we are witnessing is the wholesale generalization of a core principle in software engineering: [Don't repeat yourself](https://en.wikipedia.org/wiki/Don%27t_repeat_yourself). If you are repeating yourself, you are doing something wrong, and it will not last long before it will backfire. Hence, if you experience what you are doing as boring, the activity is dangerous in more than one way. Boredom is, in fact, a warning signal. The education system focuses on training the children for repetitive (aka, "boring") work, aka assembly line or paper pushing. The education system teaches them to accept boredom as normal, while it is not. It may have been normal in the 19th and 20th century industrial society, but that was an anomaly. It is dangerous in nature, because it makes you too predictable for predators and for prey. Nature is simply re-asserting itself. A taste for, or a dependency on, boring work is dangerous, because these jobs are rapidly disappearing. We experience boredom when our environment does not produce enough [Shannon entropy](https://en.wikipedia.org/wiki/Entropy_\(information_theory\)). Nassim Taleb also warned for that problem in "Antifragile: things that benefit from disorder". We are fundamentally antifragile. Hence, we benefit -- up to a certain point -- from disorder. The information that reaches us from our environment must contain enough disorder, or else, we will not just get bored but also lose the ability to deal with disorder. The less disorderly information a job produces, or requires you to produce, the easier it is to automate. Hence, it is the same problem all over again. So, yes, the kids are bored, and the education system is busy destroying the next generation in certainly more than one way. There is a long list of things that the education system does, that will inevitably lead to insurmountable problems. There is a long list of dangerous, red alerts. It is quite simple to demonstrate that the education system is even busy destroying the ability to engage in sound sexual reproduction. Mixing teenagers of both genders was already a dangerous experiment. Apparently, quite a few of these girls no longer think much about sex, to the point that it is apparently even ok for them to [exchange sex for free rent](https://londonist.com/2016/09/the-londoners-who-offer-free-rent-for-sexual-favours), or to get [financial help in exchange for sex to pay off student loans](https://www.thesun.co.uk/fabulous/5437340/woman-who-used-sugar-daddy-to-pay-off-student-debt-says-its-a-fairytale-to-not-expect-to-swap-sex-for-cash). The banality of sex is clearly reaching new lows. The growing banality of sex and the fact that adultery easily leads to divorce, are on a collision course. People who believe in the banality of sex are obviously not suitable for marriage. The fact that the education system is sending the kids straight to the unemployment queue is actually one of the lesser problems that it is causing. Seriously, there is way worse than that. The situation is very bad; and probably several orders of magnitude worse than you can imagine right now. It is truly catastrophic. |
| json metadata | {"tags":["technology"],"links":["https://en.wikipedia.org/wiki/Don%27t_repeat_yourself","https://en.wikipedia.org/wiki/Entropy_(information_theory)","https://londonist.com/2016/09/the-londoners-who-offer-free-rent-for-sexual-favours","https://www.thesun.co.uk/fabulous/5437340/woman-who-used-sugar-daddy-to-pay-off-student-debt-says-its-a-fairytale-to-not-expect-to-swap-sex-for-cash"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | technology |
| permlink | the-schools-are-indeed-sending-the-kids-straight-to-the-unemployment-queue-but-that-is-not-even-the-worst-problem |
| title | The schools are indeed sending the kids straight to the unemployment queue but that is not even the worst problem |
| Transaction Info | Block #20405201/Trx 3e8d8a8aed9807cda2de7fc76f529f1e79c8bcff |
View Raw JSON Data
{
"block": 20405201,
"op": [
"comment",
{
"author": "eriksank",
"body": "Technology has primarily, and still displaces, assembly-line workers and paper pushers.\n\nAnybody repeating the same operation all over again, especially within the same workday, will eventually find himself displaced.\n\nAnother problem is that other jobs in which you can keep repeating the same operation all over again throughout the day, are also being automated away.\n\nWhat we are witnessing is the wholesale generalization of a core principle in software engineering: [Don't repeat yourself](https://en.wikipedia.org/wiki/Don%27t_repeat_yourself). If you are repeating yourself, you are doing something wrong, and it will not last long before it will backfire.\n\nHence, if you experience what you are doing as boring, the activity is dangerous in more than one way. Boredom is, in fact, a warning signal.\n\nThe education system focuses on training the children for repetitive (aka, \"boring\") work, aka assembly line or paper pushing. The education system teaches them to accept boredom as normal, while it is not.\n\nIt may have been normal in the 19th and 20th century industrial society, but that was an anomaly. It is dangerous in nature, because it makes you too predictable for predators and for prey. Nature is simply re-asserting itself. A taste for, or a dependency on, boring work is dangerous, because these jobs are rapidly disappearing.\n\nWe experience boredom when our environment does not produce enough [Shannon entropy](https://en.wikipedia.org/wiki/Entropy_\\(information_theory\\)). Nassim Taleb also warned for that problem in \"Antifragile: things that benefit from disorder\". \n\nWe are fundamentally antifragile. Hence, we benefit -- up to a certain point -- from disorder.\n\nThe information that reaches us from our environment must contain enough disorder, or else, we will not just get bored but also lose the ability to deal with disorder.\n\nThe less disorderly information a job produces, or requires you to produce, the easier it is to automate. Hence, it is the same problem all over again.\n\nSo, yes, the kids are bored, and the education system is busy destroying the next generation in certainly more than one way.\n\nThere is a long list of things that the education system does, that will inevitably lead to insurmountable problems. There is a long list of dangerous, red alerts.\n\nIt is quite simple to demonstrate that the education system is even busy destroying the ability to engage in sound sexual reproduction. Mixing teenagers of both genders was already a dangerous experiment. Apparently, quite a few of these girls no longer think much about sex, to the point that it is apparently even ok for them to [exchange sex for free rent](https://londonist.com/2016/09/the-londoners-who-offer-free-rent-for-sexual-favours), or to get [financial help in exchange for sex to pay off student loans](https://www.thesun.co.uk/fabulous/5437340/woman-who-used-sugar-daddy-to-pay-off-student-debt-says-its-a-fairytale-to-not-expect-to-swap-sex-for-cash). The banality of sex is clearly reaching new lows.\n\nThe growing banality of sex and the fact that adultery easily leads to divorce, are on a collision course. People who believe in the banality of sex are obviously not suitable for marriage.\n\nThe fact that the education system is sending the kids straight to the unemployment queue is actually one of the lesser problems that it is causing. Seriously, there is way worse than that. The situation is very bad; and probably several orders of magnitude worse than you can imagine right now. It is truly catastrophic.",
"json_metadata": "{\"tags\":[\"technology\"],\"links\":[\"https://en.wikipedia.org/wiki/Don%27t_repeat_yourself\",\"https://en.wikipedia.org/wiki/Entropy_(information_theory)\",\"https://londonist.com/2016/09/the-londoners-who-offer-free-rent-for-sexual-favours\",\"https://www.thesun.co.uk/fabulous/5437340/woman-who-used-sugar-daddy-to-pay-off-student-debt-says-its-a-fairytale-to-not-expect-to-swap-sex-for-cash\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "technology",
"permlink": "the-schools-are-indeed-sending-the-kids-straight-to-the-unemployment-queue-but-that-is-not-even-the-worst-problem",
"title": "The schools are indeed sending the kids straight to the unemployment queue but that is not even the worst problem"
}
],
"op_in_trx": 0,
"timestamp": "2018-03-05T09:11:24",
"trx_id": "3e8d8a8aed9807cda2de7fc76f529f1e79c8bcff",
"trx_in_block": 34,
"virtual_op": 0
}2018/03/05 08:48:42
2018/03/05 08:48:42
| author | eriksank |
| permlink | how-to-provide-liquidity-on-the-bitcoin-lightning-network-for-incoming-payments |
| voter | ancientofmumu |
| weight | 10000 (100.00%) |
| Transaction Info | Block #20404747/Trx c1ea574a32f819640e0c2908e6e629d2a1e8f320 |
View Raw JSON Data
{
"block": 20404747,
"op": [
"vote",
{
"author": "eriksank",
"permlink": "how-to-provide-liquidity-on-the-bitcoin-lightning-network-for-incoming-payments",
"voter": "ancientofmumu",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-03-05T08:48:42",
"trx_id": "c1ea574a32f819640e0c2908e6e629d2a1e8f320",
"trx_in_block": 19,
"virtual_op": 0
}2018/03/05 07:27:15
2018/03/05 07:27:15
| author | eriksank |
| permlink | how-to-provide-liquidity-on-the-bitcoin-lightning-network-for-incoming-payments |
| voter | hr1 |
| weight | 2 (0.02%) |
| Transaction Info | Block #20403118/Trx 137cd9d6700d88ab811671d479df273d09b15df2 |
View Raw JSON Data
{
"block": 20403118,
"op": [
"vote",
{
"author": "eriksank",
"permlink": "how-to-provide-liquidity-on-the-bitcoin-lightning-network-for-incoming-payments",
"voter": "hr1",
"weight": 2
}
],
"op_in_trx": 0,
"timestamp": "2018-03-05T07:27:15",
"trx_id": "137cd9d6700d88ab811671d479df273d09b15df2",
"trx_in_block": 5,
"virtual_op": 0
}eriksankpublished a new post: how-to-provide-liquidity-on-the-bitcoin-lightning-network-for-incoming-payments2018/03/05 07:21:27
eriksankpublished a new post: how-to-provide-liquidity-on-the-bitcoin-lightning-network-for-incoming-payments
2018/03/05 07:21:27
| author | eriksank |
| body | @@ -3250,32 +3250,44 @@ fore, we need a +self-atomic marketplace for @@ -3445,16 +3445,28 @@ of such +self-atomic marketpl |
| json metadata | {"tags":["bitcoin","technology","cryptocurrency"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | bitcoin |
| permlink | how-to-provide-liquidity-on-the-bitcoin-lightning-network-for-incoming-payments |
| title | How to provide liquidity on the bitcoin lightning network for incoming payments |
| Transaction Info | Block #20403002/Trx 9bd8dcc0103e59e04f275a44b4843fa566ea5a7d |
View Raw JSON Data
{
"block": 20403002,
"op": [
"comment",
{
"author": "eriksank",
"body": "@@ -3250,32 +3250,44 @@\n fore, we need a \n+self-atomic \n marketplace for \n@@ -3445,16 +3445,28 @@\n of such \n+self-atomic \n marketpl\n",
"json_metadata": "{\"tags\":[\"bitcoin\",\"technology\",\"cryptocurrency\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "bitcoin",
"permlink": "how-to-provide-liquidity-on-the-bitcoin-lightning-network-for-incoming-payments",
"title": "How to provide liquidity on the bitcoin lightning network for incoming payments"
}
],
"op_in_trx": 0,
"timestamp": "2018-03-05T07:21:27",
"trx_id": "9bd8dcc0103e59e04f275a44b4843fa566ea5a7d",
"trx_in_block": 4,
"virtual_op": 0
}eriksankpublished a new post: how-to-provide-liquidity-on-the-bitcoin-lightning-network-for-incoming-payments2018/03/05 07:03:33
eriksankpublished a new post: how-to-provide-liquidity-on-the-bitcoin-lightning-network-for-incoming-payments
2018/03/05 07:03:33
| author | eriksank |
| body | @@ -3491,17 +3491,18 @@ uru.biz. - +%0A%0A If you j @@ -3707,16 +3707,19 @@ ng about + it , and le |
| json metadata | {"tags":["bitcoin","technology","cryptocurrency"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | bitcoin |
| permlink | how-to-provide-liquidity-on-the-bitcoin-lightning-network-for-incoming-payments |
| title | How to provide liquidity on the bitcoin lightning network for incoming payments |
| Transaction Info | Block #20402644/Trx c664919f9e1b0278c73b8c1383d4571bc6509390 |
View Raw JSON Data
{
"block": 20402644,
"op": [
"comment",
{
"author": "eriksank",
"body": "@@ -3491,17 +3491,18 @@\n uru.biz.\n- \n+%0A%0A\n If you j\n@@ -3707,16 +3707,19 @@\n ng about\n+ it\n , and le\n",
"json_metadata": "{\"tags\":[\"bitcoin\",\"technology\",\"cryptocurrency\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "bitcoin",
"permlink": "how-to-provide-liquidity-on-the-bitcoin-lightning-network-for-incoming-payments",
"title": "How to provide liquidity on the bitcoin lightning network for incoming payments"
}
],
"op_in_trx": 0,
"timestamp": "2018-03-05T07:03:33",
"trx_id": "c664919f9e1b0278c73b8c1383d4571bc6509390",
"trx_in_block": 17,
"virtual_op": 0
}eriksankpublished a new post: how-to-provide-liquidity-on-the-bitcoin-lightning-network-for-incoming-payments2018/03/05 07:00:45
eriksankpublished a new post: how-to-provide-liquidity-on-the-bitcoin-lightning-network-for-incoming-payments
2018/03/05 07:00:45
| author | eriksank |
| body | @@ -2114,16 +2114,18 @@ course, + a small p |
| json metadata | {"tags":["bitcoin","technology","cryptocurrency"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | bitcoin |
| permlink | how-to-provide-liquidity-on-the-bitcoin-lightning-network-for-incoming-payments |
| title | How to provide liquidity on the bitcoin lightning network for incoming payments |
| Transaction Info | Block #20402588/Trx f4b7913b71a2d28c4b5e88860444b18ac8d1591b |
View Raw JSON Data
{
"block": 20402588,
"op": [
"comment",
{
"author": "eriksank",
"body": "@@ -2114,16 +2114,18 @@\n course,\n+ a\n small p\n",
"json_metadata": "{\"tags\":[\"bitcoin\",\"technology\",\"cryptocurrency\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "bitcoin",
"permlink": "how-to-provide-liquidity-on-the-bitcoin-lightning-network-for-incoming-payments",
"title": "How to provide liquidity on the bitcoin lightning network for incoming payments"
}
],
"op_in_trx": 0,
"timestamp": "2018-03-05T07:00:45",
"trx_id": "f4b7913b71a2d28c4b5e88860444b18ac8d1591b",
"trx_in_block": 38,
"virtual_op": 0
}2018/03/05 06:57:21
2018/03/05 06:57:21
| author | eriksank |
| permlink | how-to-provide-liquidity-on-the-bitcoin-lightning-network-for-incoming-payments |
| voter | eriksank |
| weight | 10000 (100.00%) |
| Transaction Info | Block #20402520/Trx 66e243750fb86aa46a0678166c150aa5b7401bef |
View Raw JSON Data
{
"block": 20402520,
"op": [
"vote",
{
"author": "eriksank",
"permlink": "how-to-provide-liquidity-on-the-bitcoin-lightning-network-for-incoming-payments",
"voter": "eriksank",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-03-05T06:57:21",
"trx_id": "66e243750fb86aa46a0678166c150aa5b7401bef",
"trx_in_block": 6,
"virtual_op": 0
}eriksankpublished a new post: how-to-provide-liquidity-on-the-bitcoin-lightning-network-for-incoming-payments2018/03/05 06:57:21
eriksankpublished a new post: how-to-provide-liquidity-on-the-bitcoin-lightning-network-for-incoming-payments
2018/03/05 06:57:21
| author | eriksank |
| body | If you intend to spend 1 BTC from a lightning payment channel, you can just fund it with 1 BTC, while the channel counter-party does not need to put in any money at all. That should allow you to spend up to 1 BTC on the lightning network. Initially, you cannot receive any money in that channel, because all the money in the channel is yours to begin with. Still, as you spend money from it, you can start receiving money in it. Imagine that you have spent 0.7 BTC from this channel. That should allow you to receive 0.7 BTC from other people all over the lightning network into that channel. Hence, lightning payment channels from which you have spent money could actually be valuable because you can use them to receive money in. Therefore, you may want to avoid closing them. Still, this is not completely up to you, because your counter-party may also close the channel. Now imagine that you now need a new channel were you can receive up to 10 BTC of incoming payments? First thing, you fund a channel for 10 BTC, with the counterparty funding 0 BTC. Unfortunately, all the money in the channel is simply yours. So, redistributing the money between yourself and your counter-party will never increase your own balance. Therefore, you need to get rid of the money in the payment channel -- without losing it -- in order to make space for incoming payments. How do you do that? There may be more than one way to do that. The following way should work too. You find a counter-party who wants your 10 lightning BTC in exchange for around 10 on-chain BTC. You carry out an atomic swap with him. So, now you have an empty channel, ready to receive 10 BTC. Your counter-party however, now has a fuller payment channel. Is this a problem? Yes, if he intends to receive money into that channel. No, if he intends to spend money from that channel. Therefore, net receivers and net spenders on the lightning network will need a marketplace to swap on-chain and lightning funds with each other. Otherwise, net receivers of lightning funds will increasingly have difficulty receiving funds. There is, of course, small problem with this strategy: you already need money to receive new money, and your very first incoming payment will have to be on-chain. Still, from a small, initial payment you can snowball your channels. With 1 BTC on-chain, you can create as many empty channels able to receive 1 BTC as you need. Just lather, rinse, and repeat the procedure described above. Another minor issue is that a spending channel can be created with just one on-chain transaction, while a receiving channel will have to be created with two on-chain transactions. At this point, we still urgently need to discuss the specifics of the actual smart contracts required to carry out atomic swaps between lightning and on-chain funds. Like all atomic swaps, everything will obviously again revolve around pay-against-preimage-disclosure. We can reasonably assume that the pre-funding of incoming payment channels will soon jump to the forefront once the lightning network really goes live. We must arrange a method to fund empty channels on the lightning network, that can receive money. Otherwise, the entire thing will begin to stall. Therefore, we need a marketplace for atomic swaps between lightning and on-chain funds. If anybody is interested in joining in and work on the nitty-gritty details of the implementation of such marketplace, feel free to let me know at [email protected]. If you just want to build it by yourself, also good, because that would spare me from having to work on it. It would allow me to just complain about this future problem without having to actually do something about, and let someone else do the hard work instead of me! ;-) |
| json metadata | {"tags":["bitcoin","technology","cryptocurrency"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | bitcoin |
| permlink | how-to-provide-liquidity-on-the-bitcoin-lightning-network-for-incoming-payments |
| title | How to provide liquidity on the bitcoin lightning network for incoming payments |
| Transaction Info | Block #20402520/Trx 66e243750fb86aa46a0678166c150aa5b7401bef |
View Raw JSON Data
{
"block": 20402520,
"op": [
"comment",
{
"author": "eriksank",
"body": "If you intend to spend 1 BTC from a lightning payment channel, you can just fund it with 1 BTC, while the channel counter-party does not need to put in any money at all. That should allow you to spend up to 1 BTC on the lightning network. \n\nInitially, you cannot receive any money in that channel, because all the money in the channel is yours to begin with.\n\nStill, as you spend money from it, you can start receiving money in it. Imagine that you have spent 0.7 BTC from this channel. That should allow you to receive 0.7 BTC from other people all over the lightning network into that channel.\n\nHence, lightning payment channels from which you have spent money could actually be valuable because you can use them to receive money in. Therefore, you may want to avoid closing them. Still, this is not completely up to you, because your counter-party may also close the channel.\n\nNow imagine that you now need a new channel were you can receive up to 10 BTC of incoming payments?\n\nFirst thing, you fund a channel for 10 BTC, with the counterparty funding 0 BTC.\n\nUnfortunately, all the money in the channel is simply yours. So, redistributing the money between yourself and your counter-party will never increase your own balance.\n\nTherefore, you need to get rid of the money in the payment channel -- without losing it -- in order to make space for incoming payments.\n\nHow do you do that?\n\nThere may be more than one way to do that. The following way should work too.\n\nYou find a counter-party who wants your 10 lightning BTC in exchange for around 10 on-chain BTC. You carry out an atomic swap with him. So, now you have an empty channel, ready to receive 10 BTC. \n\nYour counter-party however, now has a fuller payment channel. Is this a problem?\n\nYes, if he intends to receive money into that channel.\nNo, if he intends to spend money from that channel.\n\nTherefore, net receivers and net spenders on the lightning network will need a marketplace to swap on-chain and lightning funds with each other. Otherwise, net receivers of lightning funds will increasingly have difficulty receiving funds.\n\nThere is, of course, small problem with this strategy: you already need money to receive new money, and your very first incoming payment will have to be on-chain. Still, from a small, initial payment you can snowball your channels. With 1 BTC on-chain, you can create as many empty channels able to receive 1 BTC as you need. Just lather, rinse, and repeat the procedure described above.\n\nAnother minor issue is that a spending channel can be created with just one on-chain transaction, while a receiving channel will have to be created with two on-chain transactions.\n\nAt this point, we still urgently need to discuss the specifics of the actual smart contracts required to carry out atomic swaps between lightning and on-chain funds.\n\nLike all atomic swaps, everything will obviously again revolve around pay-against-preimage-disclosure.\n\nWe can reasonably assume that the pre-funding of incoming payment channels will soon jump to the forefront once the lightning network really goes live. We must arrange a method to fund empty channels on the lightning network, that can receive money. Otherwise, the entire thing will begin to stall.\n\nTherefore, we need a marketplace for atomic swaps between lightning and on-chain funds.\n \nIf anybody is interested in joining in and work on the nitty-gritty details of the implementation of such marketplace, feel free to let me know at [email protected]. If you just want to build it by yourself, also good, because that would spare me from having to work on it. It would allow me to just complain about this future problem without having to actually do something about, and let someone else do the hard work instead of me! ;-)",
"json_metadata": "{\"tags\":[\"bitcoin\",\"technology\",\"cryptocurrency\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "bitcoin",
"permlink": "how-to-provide-liquidity-on-the-bitcoin-lightning-network-for-incoming-payments",
"title": "How to provide liquidity on the bitcoin lightning network for incoming payments"
}
],
"op_in_trx": 0,
"timestamp": "2018-03-05T06:57:21",
"trx_id": "66e243750fb86aa46a0678166c150aa5b7401bef",
"trx_in_block": 6,
"virtual_op": 0
}hr1upvoted (0.02%) @eriksank / ddos-attack-on-github-mostly-documentation-and-or-migration-bugs2018/03/03 11:03:00
hr1upvoted (0.02%) @eriksank / ddos-attack-on-github-mostly-documentation-and-or-migration-bugs
2018/03/03 11:03:00
| author | eriksank |
| permlink | ddos-attack-on-github-mostly-documentation-and-or-migration-bugs |
| voter | hr1 |
| weight | 2 (0.02%) |
| Transaction Info | Block #20349846/Trx 22c09f6f7281d25219d41a963b2d0afc8311f2ee |
View Raw JSON Data
{
"block": 20349846,
"op": [
"vote",
{
"author": "eriksank",
"permlink": "ddos-attack-on-github-mostly-documentation-and-or-migration-bugs",
"voter": "hr1",
"weight": 2
}
],
"op_in_trx": 0,
"timestamp": "2018-03-03T11:03:00",
"trx_id": "22c09f6f7281d25219d41a963b2d0afc8311f2ee",
"trx_in_block": 17,
"virtual_op": 0
}eriksankpublished a new post: ddos-attack-on-github-mostly-documentation-and-or-migration-bugs2018/03/03 10:43:03
eriksankpublished a new post: ddos-attack-on-github-mostly-documentation-and-or-migration-bugs
2018/03/03 10:43:03
| author | eriksank |
| body | @@ -7,16 +7,20 @@ opinion, + the number |
| json metadata | {"tags":["technology"],"links":["https://github.com/memcached/memcached/wiki/ConfiguringServer","https://serverfault.com/questions/609504/memcached-listen-on-selected-interfaces"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | technology |
| permlink | ddos-attack-on-github-mostly-documentation-and-or-migration-bugs |
| title | DDOS attack on github mostly documentation bug or result of botched cloud migrations |
| Transaction Info | Block #20349447/Trx 96e71343a60ab04d611049c5a1905c6ed928117d |
View Raw JSON Data
{
"block": 20349447,
"op": [
"comment",
{
"author": "eriksank",
"body": "@@ -7,16 +7,20 @@\n opinion,\n+ the\n number \n",
"json_metadata": "{\"tags\":[\"technology\"],\"links\":[\"https://github.com/memcached/memcached/wiki/ConfiguringServer\",\"https://serverfault.com/questions/609504/memcached-listen-on-selected-interfaces\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "technology",
"permlink": "ddos-attack-on-github-mostly-documentation-and-or-migration-bugs",
"title": "DDOS attack on github mostly documentation bug or result of botched cloud migrations"
}
],
"op_in_trx": 0,
"timestamp": "2018-03-03T10:43:03",
"trx_id": "96e71343a60ab04d611049c5a1905c6ed928117d",
"trx_in_block": 12,
"virtual_op": 0
}eriksankpublished a new post: ddos-attack-on-github-mostly-documentation-and-or-migration-bugs2018/03/03 10:41:21
eriksankpublished a new post: ddos-attack-on-github-mostly-documentation-and-or-migration-bugs
2018/03/03 10:41:21
| author | eriksank |
| body | In my opinion, number one reason why the DDOS attack on github.com was possible, is because of a documentation bug. The [Memcached documentation](https://github.com/memcached/memcached/wiki/ConfiguringServer) discourages restricting Memcached to listening to authorized machines only: > -l allows you to bind to specific interfaces or IP addresses. Memcached does not spend much, if any, effort in ensuring its defensibility from random internet connections. So you must not expose memcached directly to the internet, or otherwise any untrusted users." Not exposing memcached directly to the internet is not always feasible or even realistic in a cloud situation, while not doing anything at all, is clearly not a solution either. The documentation does not even mention one example for the `- l` option. We need to hunt down examples elsewhere: [Memcached listen on selected interfaces](https://serverfault.com/questions/609504/memcached-listen-on-selected-interfaces) > The `-l` option can take [...] a comma separated list of IP addresses. An IP address may have an optional port specification. So, for instance: > memcached -l 127.0.0.1:11211,127.0.0.1:11212,10.1.2.3 -u 0 Memcached should be made to only listen to the IP addresses of downstream machines for which it caches data. All other machines should be prevented from talking to it. A second reason for the DDOS problem is that the compromised systems may have been migrated from a private data center to a cloud situation without reviewing the important `-l` and `-u` configurations. |
| json metadata | {"tags":["technology"],"links":["https://github.com/memcached/memcached/wiki/ConfiguringServer","https://serverfault.com/questions/609504/memcached-listen-on-selected-interfaces"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | technology |
| permlink | ddos-attack-on-github-mostly-documentation-and-or-migration-bugs |
| title | DDOS attack on github mostly documentation bug or result of botched cloud migrations |
| Transaction Info | Block #20349413/Trx 325b8c1622d4e1ea800ba9a63a0a6a9dc0bc1368 |
View Raw JSON Data
{
"block": 20349413,
"op": [
"comment",
{
"author": "eriksank",
"body": "In my opinion, number one reason why the DDOS attack on github.com was possible, is because of a documentation bug. The [Memcached documentation](https://github.com/memcached/memcached/wiki/ConfiguringServer) discourages restricting Memcached to listening to authorized machines only:\n\n> -l allows you to bind to specific interfaces or IP addresses. Memcached does not spend much, if any, effort in ensuring its defensibility from random internet connections. So you must not expose memcached directly to the internet, or otherwise any untrusted users.\"\n\nNot exposing memcached directly to the internet is not always feasible or even realistic in a cloud situation, while not doing anything at all, is clearly not a solution either. The documentation does not even mention one example for the `- l` option. We need to hunt down examples elsewhere:\n\n[Memcached listen on selected interfaces](https://serverfault.com/questions/609504/memcached-listen-on-selected-interfaces)\n\n> The `-l` option can take [...] a comma separated list of IP addresses. An IP address may have an optional port specification. So, for instance:\n\n> memcached -l 127.0.0.1:11211,127.0.0.1:11212,10.1.2.3 -u 0\n\nMemcached should be made to only listen to the IP addresses of downstream machines for which it caches data. All other machines should be prevented from talking to it.\n\nA second reason for the DDOS problem is that the compromised systems may have been migrated from a private data center to a cloud situation without reviewing the important `-l` and `-u` configurations.",
"json_metadata": "{\"tags\":[\"technology\"],\"links\":[\"https://github.com/memcached/memcached/wiki/ConfiguringServer\",\"https://serverfault.com/questions/609504/memcached-listen-on-selected-interfaces\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "technology",
"permlink": "ddos-attack-on-github-mostly-documentation-and-or-migration-bugs",
"title": "DDOS attack on github mostly documentation bug or result of botched cloud migrations"
}
],
"op_in_trx": 0,
"timestamp": "2018-03-03T10:41:21",
"trx_id": "325b8c1622d4e1ea800ba9a63a0a6a9dc0bc1368",
"trx_in_block": 3,
"virtual_op": 0
}eriksankpublished a new post: ddos-attack-on-github-mostly-documentation-and-or-migration-bugs2018/03/03 10:35:03
eriksankpublished a new post: ddos-attack-on-github-mostly-documentation-and-or-migration-bugs
2018/03/03 10:35:03
| author | eriksank |
| body | @@ -1114,16 +1114,18 @@ tance:%0A%0A +%3E memcache @@ -1507,16 +1507,26 @@ ing the +important %60-l%60 and |
| json metadata | {"tags":["technology"],"links":["https://github.com/memcached/memcached/wiki/ConfiguringServer","https://serverfault.com/questions/609504/memcached-listen-on-selected-interfaces"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | technology |
| permlink | ddos-attack-on-github-mostly-documentation-and-or-migration-bugs |
| title | DDOS attack on github mostly documentation bug or result of a botched migration |
| Transaction Info | Block #20349287/Trx 2060d52e421fc581c073a109c93117345e47f936 |
View Raw JSON Data
{
"block": 20349287,
"op": [
"comment",
{
"author": "eriksank",
"body": "@@ -1114,16 +1114,18 @@\n tance:%0A%0A\n+%3E \n memcache\n@@ -1507,16 +1507,26 @@\n ing the \n+important \n %60-l%60 and\n",
"json_metadata": "{\"tags\":[\"technology\"],\"links\":[\"https://github.com/memcached/memcached/wiki/ConfiguringServer\",\"https://serverfault.com/questions/609504/memcached-listen-on-selected-interfaces\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "technology",
"permlink": "ddos-attack-on-github-mostly-documentation-and-or-migration-bugs",
"title": "DDOS attack on github mostly documentation bug or result of a botched migration"
}
],
"op_in_trx": 0,
"timestamp": "2018-03-03T10:35:03",
"trx_id": "2060d52e421fc581c073a109c93117345e47f936",
"trx_in_block": 17,
"virtual_op": 0
}dhimi10upvoted (100.00%) @eriksank / ddos-attack-on-github-mostly-documentation-and-or-migration-bugs2018/03/03 10:33:27
dhimi10upvoted (100.00%) @eriksank / ddos-attack-on-github-mostly-documentation-and-or-migration-bugs
2018/03/03 10:33:27
| author | eriksank |
| permlink | ddos-attack-on-github-mostly-documentation-and-or-migration-bugs |
| voter | dhimi10 |
| weight | 10000 (100.00%) |
| Transaction Info | Block #20349255/Trx 3a94a8012753d9f1e01039d55a400e398ad4cece |
View Raw JSON Data
{
"block": 20349255,
"op": [
"vote",
{
"author": "eriksank",
"permlink": "ddos-attack-on-github-mostly-documentation-and-or-migration-bugs",
"voter": "dhimi10",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-03-03T10:33:27",
"trx_id": "3a94a8012753d9f1e01039d55a400e398ad4cece",
"trx_in_block": 12,
"virtual_op": 0
}eriksankupvoted (100.00%) @eriksank / ddos-attack-on-github-mostly-documentation-and-or-migration-bugs2018/03/03 10:32:33
eriksankupvoted (100.00%) @eriksank / ddos-attack-on-github-mostly-documentation-and-or-migration-bugs
2018/03/03 10:32:33
| author | eriksank |
| permlink | ddos-attack-on-github-mostly-documentation-and-or-migration-bugs |
| voter | eriksank |
| weight | 10000 (100.00%) |
| Transaction Info | Block #20349237/Trx 5fe9ea074a67366eda07320a92f30bbd02a4318c |
View Raw JSON Data
{
"block": 20349237,
"op": [
"vote",
{
"author": "eriksank",
"permlink": "ddos-attack-on-github-mostly-documentation-and-or-migration-bugs",
"voter": "eriksank",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-03-03T10:32:33",
"trx_id": "5fe9ea074a67366eda07320a92f30bbd02a4318c",
"trx_in_block": 27,
"virtual_op": 0
}eriksankpublished a new post: ddos-attack-on-github-mostly-documentation-and-or-migration-bugs2018/03/03 10:32:33
eriksankpublished a new post: ddos-attack-on-github-mostly-documentation-and-or-migration-bugs
2018/03/03 10:32:33
| author | eriksank |
| body | In my opinion, number one reason why the DDOS attack on github.com was possible, is because of a documentation bug. The [Memcached documentation](https://github.com/memcached/memcached/wiki/ConfiguringServer) discourages restricting Memcached to listening to authorized machines only: > -l allows you to bind to specific interfaces or IP addresses. Memcached does not spend much, if any, effort in ensuring its defensibility from random internet connections. So you must not expose memcached directly to the internet, or otherwise any untrusted users." Not exposing memcached directly to the internet is not always feasible or even realistic in a cloud situation, while not doing anything at all, is clearly not a solution either. The documentation does not even mention one example for the `- l` option. We need to hunt down examples elsewhere: [Memcached listen on selected interfaces](https://serverfault.com/questions/609504/memcached-listen-on-selected-interfaces) > The `-l` option can take [...] a comma separated list of IP addresses. An IP address may have an optional port specification. So, for instance: memcached -l 127.0.0.1:11211,127.0.0.1:11212,10.1.2.3 -u 0 Memcached should be made to only listen to the IP addresses of downstream machines for which it caches data. All other machines should be prevented from talking to it. A second reason for the DDOS problem is that the compromised systems may have been migrated from a private data center to a cloud situation without reviewing the `-l` and `-u` configurations. |
| json metadata | {"tags":["technology"],"links":["https://github.com/memcached/memcached/wiki/ConfiguringServer","https://serverfault.com/questions/609504/memcached-listen-on-selected-interfaces"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | technology |
| permlink | ddos-attack-on-github-mostly-documentation-and-or-migration-bugs |
| title | DDOS attack on github mostly documentation and/or migration bugs |
| Transaction Info | Block #20349237/Trx 5fe9ea074a67366eda07320a92f30bbd02a4318c |
View Raw JSON Data
{
"block": 20349237,
"op": [
"comment",
{
"author": "eriksank",
"body": "In my opinion, number one reason why the DDOS attack on github.com was possible, is because of a documentation bug. The [Memcached documentation](https://github.com/memcached/memcached/wiki/ConfiguringServer) discourages restricting Memcached to listening to authorized machines only:\n\n> -l allows you to bind to specific interfaces or IP addresses. Memcached does not spend much, if any, effort in ensuring its defensibility from random internet connections. So you must not expose memcached directly to the internet, or otherwise any untrusted users.\"\n\nNot exposing memcached directly to the internet is not always feasible or even realistic in a cloud situation, while not doing anything at all, is clearly not a solution either. The documentation does not even mention one example for the `- l` option. We need to hunt down examples elsewhere:\n\n[Memcached listen on selected interfaces](https://serverfault.com/questions/609504/memcached-listen-on-selected-interfaces)\n\n> The `-l` option can take [...] a comma separated list of IP addresses. An IP address may have an optional port specification. So, for instance:\n\nmemcached -l 127.0.0.1:11211,127.0.0.1:11212,10.1.2.3 -u 0\n\nMemcached should be made to only listen to the IP addresses of downstream machines for which it caches data. All other machines should be prevented from talking to it.\n\nA second reason for the DDOS problem is that the compromised systems may have been migrated from a private data center to a cloud situation without reviewing the `-l` and `-u` configurations.",
"json_metadata": "{\"tags\":[\"technology\"],\"links\":[\"https://github.com/memcached/memcached/wiki/ConfiguringServer\",\"https://serverfault.com/questions/609504/memcached-listen-on-selected-interfaces\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "technology",
"permlink": "ddos-attack-on-github-mostly-documentation-and-or-migration-bugs",
"title": "DDOS attack on github mostly documentation and/or migration bugs"
}
],
"op_in_trx": 0,
"timestamp": "2018-03-03T10:32:33",
"trx_id": "5fe9ea074a67366eda07320a92f30bbd02a4318c",
"trx_in_block": 27,
"virtual_op": 0
}2018/02/21 07:02:12
2018/02/21 07:02:12
| author | eriksank |
| body | According to the Venezuelan [Petro whitepaper](https://nem.io/wp-content/themes/nem/files/NEM_techRef.pdf), the Petro (PTR) will be freely tradable. It will allow Venezuela to bypass financial censorship on their US dollar transactions in New York. Venezuela will finally be able to pay for their food imports again. All of this assumes that the State oil company, Petróleos de Venezuela, S.A. (PDVSA), will work overtime to swiftly accept PTR payments in exchange for their oil deliveries. The presale has commenced already (20 Feb 2018) and the public ICO will be floated next month (20 Mar 2018). The Venezuelan State accepts the restriction that it will not be able to make new emissions of PTR. Of course, this should be verifiable in the NEM ICO smart contract. The NEM blockchain uses a Proof-of-Importance (PoI) system to prevent double spending. I would like to see the math thoroughly peer-reviewed in order to verify that the probability over time that attacker of the honest blockchain successfully subverts it, is a Cauchy sequence that converges to zero. There haven't been any really bad complaints about NEM yet, but in the cryptocurrency field, it usually means that few people have had a serious look at it. Concerning the NEM software, the current implementation of the [server is closed source](https://en.wikipedia.org/wiki/NEM_\(cryptocurrency\)). The developers have promised that the C++ rewrite, "Catapult", will be open source. This redevelopment problem has now become an urgent matter. It is absolutely unacceptable for smart contracts of sovereign coins to run on secret source. Doing so, violates freedom of information. Therefore, the open-source rewrite must urgently be completed and be published for peer review. The [secure client-side NEM wallet](https://blog.nem.io/hot-cold-wallet/) seems to have a proper offline signing procedure but the link to the source code seems to have disappeared from Github. The main NEM wallet, [nanoWallet](https://github.com/NemProject/NanoWallet/issues/394), exposes the seed/secret to the network and must be considered fundamentally insecure. This wallet should not be used for anything more than very small, nominal amounts. In my impression, if Petróleos de Venezuela, S.A. (PDVSA) accepts PTR payments for their oil, the coin will be perfectly viable, and be suitable for bypassing New York censorship on US dollar payments. |
| json metadata | {"tags":["cryptocurrency","politics"],"links":["https://nem.io/wp-content/themes/nem/files/NEM_techRef.pdf","https://en.wikipedia.org/wiki/NEM_(cryptocurrency)","https://blog.nem.io/hot-cold-wallet/","https://github.com/NemProject/NanoWallet/issues/394"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | cryptocurrency |
| permlink | the-statists-are-breaking-ranks-presale-of-petro-ptr-cryptocoin-started-on-20-feb-2018 |
| title | The Statists are breaking ranks. Presale of Venezuela Petro (PTR) cryptocoin started on 20 Feb 2018! |
| Transaction Info | Block #20057280/Trx 92cd0c07d167709f6505f2e5dedc77ad9f14c71c |
View Raw JSON Data
{
"block": 20057280,
"op": [
"comment",
{
"author": "eriksank",
"body": "According to the Venezuelan [Petro whitepaper](https://nem.io/wp-content/themes/nem/files/NEM_techRef.pdf), the Petro (PTR) will be freely tradable. It will allow Venezuela to bypass financial censorship on their US dollar transactions in New York. Venezuela will finally be able to pay for their food imports again.\n\nAll of this assumes that the State oil company, Petróleos de Venezuela, S.A. (PDVSA), will work overtime to swiftly accept PTR payments in exchange for their oil deliveries.\n\nThe presale has commenced already (20 Feb 2018) and the public ICO will be floated next month (20 Mar 2018).\n\nThe Venezuelan State accepts the restriction that it will not be able to make new emissions of PTR. Of course, this should be verifiable in the NEM ICO smart contract.\n\nThe NEM blockchain uses a Proof-of-Importance (PoI) system to prevent double spending. I would like to see the math thoroughly peer-reviewed in order to verify that the probability over time that attacker of the honest blockchain successfully subverts it, is a Cauchy sequence that converges to zero. There haven't been any really bad complaints about NEM yet, but in the cryptocurrency field, it usually means that few people have had a serious look at it.\n\nConcerning the NEM software, the current implementation of the [server is closed source](https://en.wikipedia.org/wiki/NEM_\\(cryptocurrency\\)). The developers have promised that the C++ rewrite, \"Catapult\", will be open source. This redevelopment problem has now become an urgent matter. It is absolutely unacceptable for smart contracts of sovereign coins to run on secret source. Doing so, violates freedom of information. Therefore, the open-source rewrite must urgently be completed and be published for peer review.\n\nThe [secure client-side NEM wallet](https://blog.nem.io/hot-cold-wallet/) seems to have a proper offline signing procedure but the link to the source code seems to have disappeared from Github. The main NEM wallet, [nanoWallet](https://github.com/NemProject/NanoWallet/issues/394), exposes the seed/secret to the network and must be considered fundamentally insecure. This wallet should not be used for anything more than very small, nominal amounts.\n\nIn my impression, if Petróleos de Venezuela, S.A. (PDVSA) accepts PTR payments for their oil, the coin will be perfectly viable, and be suitable for bypassing New York censorship on US dollar payments.",
"json_metadata": "{\"tags\":[\"cryptocurrency\",\"politics\"],\"links\":[\"https://nem.io/wp-content/themes/nem/files/NEM_techRef.pdf\",\"https://en.wikipedia.org/wiki/NEM_(cryptocurrency)\",\"https://blog.nem.io/hot-cold-wallet/\",\"https://github.com/NemProject/NanoWallet/issues/394\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "cryptocurrency",
"permlink": "the-statists-are-breaking-ranks-presale-of-petro-ptr-cryptocoin-started-on-20-feb-2018",
"title": "The Statists are breaking ranks. Presale of Venezuela Petro (PTR) cryptocoin started on 20 Feb 2018!"
}
],
"op_in_trx": 0,
"timestamp": "2018-02-21T07:02:12",
"trx_id": "92cd0c07d167709f6505f2e5dedc77ad9f14c71c",
"trx_in_block": 14,
"virtual_op": 0
}2018/02/21 06:58:18
2018/02/21 06:58:18
| author | eriksank |
| permlink | the-statists-are-breaking-ranks-presale-of-petro-ptr-cryptocoin-started-on-20-feb-2018 |
| voter | eriksank |
| weight | 10000 (100.00%) |
| Transaction Info | Block #20057202/Trx 91df3fd53d930c9cb3791c9484b064688eb256ed |
View Raw JSON Data
{
"block": 20057202,
"op": [
"vote",
{
"author": "eriksank",
"permlink": "the-statists-are-breaking-ranks-presale-of-petro-ptr-cryptocoin-started-on-20-feb-2018",
"voter": "eriksank",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-02-21T06:58:18",
"trx_id": "91df3fd53d930c9cb3791c9484b064688eb256ed",
"trx_in_block": 46,
"virtual_op": 0
}2018/02/21 06:58:18
2018/02/21 06:58:18
| author | eriksank |
| body | According to the Venezuelan [Petro whitepaper](https://nem.io/wp-content/themes/nem/files/NEM_techRef.pdf), the Petro (PTR) will be freely tradable. It will allow Venezuela to bypass financial censorship on their US dollar transactions in New York. Venezuela will finally be able to pay for their food imports again. All of this assumes that the State oil company, Petróleos de Venezuela, S.A. (PDVSA), will work overtime to swiftly accept PTR payments in exchange for their oil deliveries. The presale has commenced already (20 Feb 2018) and the public ICO will be floated next month (20 Mar 2018). The Venezuelan State accepts the restriction that it will not be able to make new emissions of PTR. Of course, this should be verifiable in the NEM ICO smart contract. The NEM blockchain uses a Proof-of-Importance (PoI) system to prevent double spending. I would like to see the math thoroughly peer-reviewed in order to verify that the probability over time that attacker of the honest blockchain successfully subverts it, is a Cauchy sequence that converges to zero. There haven't been any really bad complaints about NEM yet, but in the cryptocurrency field, it usually means that few people have had a serious look at it. Concerning the NEM software, the current implementation of the [server is closed source](https://en.wikipedia.org/wiki/NEM_\(cryptocurrency\)). The developers have promised that the C++ rewrite, "Catapult", will be open source. This redevelopment problem has now become an urgent matter. It is absolutely unacceptable for smart contracts of sovereign coins to run on secret source. Doing so, violates freedom of information. Therefore, the open-source rewrite must urgently be completed and be published for peer review. The [secure client-side NEM wallet](https://blog.nem.io/hot-cold-wallet/) seems to have a proper offline signing procedure but the link to the source code seems to have disappeared from Github. The main NEM wallet, [nanoWallet](https://github.com/NemProject/NanoWallet/issues/394), exposes the seed/secret to the network and must be considered fundamentally insecure. This wallet should not be used for anything more than very small, nominal amounts. In my impression, if Petróleos de Venezuela, S.A. (PDVSA) accepts PTR payments for their oil, the coin will be perfectly viable, and be suitable for bypassing New York censorship on US dollar payments. |
| json metadata | {"tags":["cryptocurrency","politics"],"links":["https://nem.io/wp-content/themes/nem/files/NEM_techRef.pdf","https://en.wikipedia.org/wiki/NEM_(cryptocurrency)","https://blog.nem.io/hot-cold-wallet/","https://github.com/NemProject/NanoWallet/issues/394"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | cryptocurrency |
| permlink | the-statists-are-breaking-ranks-presale-of-petro-ptr-cryptocoin-started-on-20-feb-2018 |
| title | The Statists are breaking ranks. Presale of Petro (PTR) cryptocoin started on 20 Feb 2018! |
| Transaction Info | Block #20057202/Trx 91df3fd53d930c9cb3791c9484b064688eb256ed |
View Raw JSON Data
{
"block": 20057202,
"op": [
"comment",
{
"author": "eriksank",
"body": "According to the Venezuelan [Petro whitepaper](https://nem.io/wp-content/themes/nem/files/NEM_techRef.pdf), the Petro (PTR) will be freely tradable. It will allow Venezuela to bypass financial censorship on their US dollar transactions in New York. Venezuela will finally be able to pay for their food imports again.\n\nAll of this assumes that the State oil company, Petróleos de Venezuela, S.A. (PDVSA), will work overtime to swiftly accept PTR payments in exchange for their oil deliveries.\n\nThe presale has commenced already (20 Feb 2018) and the public ICO will be floated next month (20 Mar 2018).\n\nThe Venezuelan State accepts the restriction that it will not be able to make new emissions of PTR. Of course, this should be verifiable in the NEM ICO smart contract.\n\nThe NEM blockchain uses a Proof-of-Importance (PoI) system to prevent double spending. I would like to see the math thoroughly peer-reviewed in order to verify that the probability over time that attacker of the honest blockchain successfully subverts it, is a Cauchy sequence that converges to zero. There haven't been any really bad complaints about NEM yet, but in the cryptocurrency field, it usually means that few people have had a serious look at it.\n\nConcerning the NEM software, the current implementation of the [server is closed source](https://en.wikipedia.org/wiki/NEM_\\(cryptocurrency\\)). The developers have promised that the C++ rewrite, \"Catapult\", will be open source. This redevelopment problem has now become an urgent matter. It is absolutely unacceptable for smart contracts of sovereign coins to run on secret source. Doing so, violates freedom of information. Therefore, the open-source rewrite must urgently be completed and be published for peer review.\n\nThe [secure client-side NEM wallet](https://blog.nem.io/hot-cold-wallet/) seems to have a proper offline signing procedure but the link to the source code seems to have disappeared from Github. The main NEM wallet, [nanoWallet](https://github.com/NemProject/NanoWallet/issues/394), exposes the seed/secret to the network and must be considered fundamentally insecure. This wallet should not be used for anything more than very small, nominal amounts.\n\nIn my impression, if Petróleos de Venezuela, S.A. (PDVSA) accepts PTR payments for their oil, the coin will be perfectly viable, and be suitable for bypassing New York censorship on US dollar payments.",
"json_metadata": "{\"tags\":[\"cryptocurrency\",\"politics\"],\"links\":[\"https://nem.io/wp-content/themes/nem/files/NEM_techRef.pdf\",\"https://en.wikipedia.org/wiki/NEM_(cryptocurrency)\",\"https://blog.nem.io/hot-cold-wallet/\",\"https://github.com/NemProject/NanoWallet/issues/394\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "cryptocurrency",
"permlink": "the-statists-are-breaking-ranks-presale-of-petro-ptr-cryptocoin-started-on-20-feb-2018",
"title": "The Statists are breaking ranks. Presale of Petro (PTR) cryptocoin started on 20 Feb 2018!"
}
],
"op_in_trx": 0,
"timestamp": "2018-02-21T06:58:18",
"trx_id": "91df3fd53d930c9cb3791c9484b064688eb256ed",
"trx_in_block": 46,
"virtual_op": 0
}eriksankupvoted (100.00%) @nazarethq / who-am-i-my-way-introduction-on-steem-it2018/02/21 04:53:42
eriksankupvoted (100.00%) @nazarethq / who-am-i-my-way-introduction-on-steem-it
2018/02/21 04:53:42
| author | nazarethq |
| permlink | who-am-i-my-way-introduction-on-steem-it |
| voter | eriksank |
| weight | 10000 (100.00%) |
| Transaction Info | Block #20054710/Trx ba0ca6b3f55f573aff9a9e1c351f7c2d61d4a402 |
View Raw JSON Data
{
"block": 20054710,
"op": [
"vote",
{
"author": "nazarethq",
"permlink": "who-am-i-my-way-introduction-on-steem-it",
"voter": "eriksank",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-02-21T04:53:42",
"trx_id": "ba0ca6b3f55f573aff9a9e1c351f7c2d61d4a402",
"trx_in_block": 18,
"virtual_op": 0
}eriksankfollowed @nazarethq2018/02/21 04:53:03
eriksankfollowed @nazarethq
2018/02/21 04:53:03
| id | follow |
| json | ["follow",{"follower":"eriksank","following":"nazarethq","what":["blog"]}] |
| required auths | [] |
| required posting auths | ["eriksank"] |
| Transaction Info | Block #20054697/Trx 3a31a19ebd43e5d6cb4f9f84d8a6e34e97c3c310 |
View Raw JSON Data
{
"block": 20054697,
"op": [
"custom_json",
{
"id": "follow",
"json": "[\"follow\",{\"follower\":\"eriksank\",\"following\":\"nazarethq\",\"what\":[\"blog\"]}]",
"required_auths": [],
"required_posting_auths": [
"eriksank"
]
}
],
"op_in_trx": 0,
"timestamp": "2018-02-21T04:53:03",
"trx_id": "3a31a19ebd43e5d6cb4f9f84d8a6e34e97c3c310",
"trx_in_block": 9,
"virtual_op": 0
}eriksankpublished a new post: december-bitcoin-price-spike-caused-by-airdrops2018/02/11 22:59:54
eriksankpublished a new post: december-bitcoin-price-spike-caused-by-airdrops
2018/02/11 22:59:54
| author | eriksank |
| body | @@ -1267,20 +1267,20 @@ really -have +need to look |
| json metadata | {"tags":["bitcoin"],"links":["https://btcdiv.com","https://www.kaiko.com/products/all-exchanges-historical-10-order-books"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | bitcoin |
| permlink | december-bitcoin-price-spike-caused-by-airdrops |
| title | December bitcoin price spike caused by airdrops? |
| Transaction Info | Block #19788612/Trx 9346313212abcb2ee98c2ef6e7e139529039eba8 |
View Raw JSON Data
{
"block": 19788612,
"op": [
"comment",
{
"author": "eriksank",
"body": "@@ -1267,20 +1267,20 @@\n really \n-have\n+need\n to look\n",
"json_metadata": "{\"tags\":[\"bitcoin\"],\"links\":[\"https://btcdiv.com\",\"https://www.kaiko.com/products/all-exchanges-historical-10-order-books\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "bitcoin",
"permlink": "december-bitcoin-price-spike-caused-by-airdrops",
"title": "December bitcoin price spike caused by airdrops?"
}
],
"op_in_trx": 0,
"timestamp": "2018-02-11T22:59:54",
"trx_id": "9346313212abcb2ee98c2ef6e7e139529039eba8",
"trx_in_block": 43,
"virtual_op": 0
}eriksankpublished a new post: december-bitcoin-price-spike-caused-by-airdrops2018/02/11 22:59:24
eriksankpublished a new post: december-bitcoin-price-spike-caused-by-airdrops
2018/02/11 22:59:24
| author | eriksank |
| body | @@ -543,20 +543,26 @@ the -b +B itcoin -c +C ash + (BCH) pay |
| json metadata | {"tags":["bitcoin"],"links":["https://btcdiv.com","https://www.kaiko.com/products/all-exchanges-historical-10-order-books"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | bitcoin |
| permlink | december-bitcoin-price-spike-caused-by-airdrops |
| title | December bitcoin price spike caused by airdrops? |
| Transaction Info | Block #19788602/Trx 07e4bd78492cdb5416d4705a4757f1017b1b7146 |
View Raw JSON Data
{
"block": 19788602,
"op": [
"comment",
{
"author": "eriksank",
"body": "@@ -543,20 +543,26 @@\n the \n-b\n+B\n itcoin \n-c\n+C\n ash\n+ (BCH)\n pay\n",
"json_metadata": "{\"tags\":[\"bitcoin\"],\"links\":[\"https://btcdiv.com\",\"https://www.kaiko.com/products/all-exchanges-historical-10-order-books\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "bitcoin",
"permlink": "december-bitcoin-price-spike-caused-by-airdrops",
"title": "December bitcoin price spike caused by airdrops?"
}
],
"op_in_trx": 0,
"timestamp": "2018-02-11T22:59:24",
"trx_id": "07e4bd78492cdb5416d4705a4757f1017b1b7146",
"trx_in_block": 33,
"virtual_op": 0
}eriksankupvoted (100.00%) @eriksank / december-bitcoin-price-spike-caused-by-airdrops2018/02/11 22:57:54
eriksankupvoted (100.00%) @eriksank / december-bitcoin-price-spike-caused-by-airdrops
2018/02/11 22:57:54
| author | eriksank |
| permlink | december-bitcoin-price-spike-caused-by-airdrops |
| voter | eriksank |
| weight | 10000 (100.00%) |
| Transaction Info | Block #19788572/Trx 96cf2e12922100d997856b8a17d2f9d51811e3e9 |
View Raw JSON Data
{
"block": 19788572,
"op": [
"vote",
{
"author": "eriksank",
"permlink": "december-bitcoin-price-spike-caused-by-airdrops",
"voter": "eriksank",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-02-11T22:57:54",
"trx_id": "96cf2e12922100d997856b8a17d2f9d51811e3e9",
"trx_in_block": 19,
"virtual_op": 0
}Manabar
Voting Power100.00%
Downvote Power100.00%
Resource Credits100.00%
Reputation Progress88.42%
{
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779062574
},
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779062574
},
"rc_account": {
"account": "eriksank",
"max_rc": "10164408779",
"max_rc_creation_adjustment": {
"amount": "2020748973",
"nai": "@@000000037",
"precision": 6
},
"rc_manabar": {
"current_mana": "10164408779",
"last_update_time": 1779062574
}
}
}Account Metadata
| POSTING JSON METADATA | |
| None | |
| JSON METADATA | |
| None |
{
"posting_json_metadata": {},
"json_metadata": {}
}Auth Keys
Owner
Single Signature
Public Keys
STM7fyN9bi8bpYAXLL9Un8BoiGv2YTuGxiEcfaH9w9tqYRAY5fLDk1/1
Active
Single Signature
Public Keys
STM7L4NHTTJPuzBUULqSmvZniWHAMxeEAVshyophhUFneGPHeXgGf1/1
Posting
Single Signature
Public Keys
STM6LfEvvvTn3Lpdp5k2Zh873eTnsfQVL6twdPvS1KHxWiZ6Sz6xr1/1
Memo
STM7B959Qqbp32GjRUHE8AQh6nEio4EDxGCqXbosQ2crYKveGPsVC
{
"owner": {
"account_auths": [],
"key_auths": [
[
"STM7fyN9bi8bpYAXLL9Un8BoiGv2YTuGxiEcfaH9w9tqYRAY5fLDk",
1
]
],
"weight_threshold": 1
},
"active": {
"account_auths": [],
"key_auths": [
[
"STM7L4NHTTJPuzBUULqSmvZniWHAMxeEAVshyophhUFneGPHeXgGf",
1
]
],
"weight_threshold": 1
},
"posting": {
"account_auths": [],
"key_auths": [
[
"STM6LfEvvvTn3Lpdp5k2Zh873eTnsfQVL6twdPvS1KHxWiZ6Sz6xr",
1
]
],
"weight_threshold": 1
},
"memo": "STM7B959Qqbp32GjRUHE8AQh6nEio4EDxGCqXbosQ2crYKveGPsVC"
}Witness Votes
0 / 30
No active witness votes.
[]