VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS0.00%
Net Worth
0.034USD
STEEM
0.001STEEM
SBD
0.000SBD
Effective Power
5.001SP
├── Own SP
0.635SP
└── Incoming DelegationsDeleg
+4.366SP
Detailed Balance
| STEEM | ||
| balance | 0.001STEEM | STEEM |
| market_balance | 0.000STEEM | STEEM |
| savings_balance | 0.000STEEM | STEEM |
| reward_steem_balance | 0.000STEEM | STEEM |
| STEEM POWER | ||
| Own SP | 0.635SP | SP |
| Delegated Out | 0.000SP | SP |
| Delegation In | 4.366SP | SP |
| Effective Power | 5.001SP | SP |
| Reward SP (pending) | 0.002SP | SP |
| SBD | ||
| sbd_balance | 0.000SBD | SBD |
| sbd_conversions | 0.000SBD | SBD |
| sbd_market_balance | 0.000SBD | SBD |
| savings_sbd_balance | 0.000SBD | SBD |
| reward_sbd_balance | 0.000SBD | SBD |
{
"balance": "0.001 STEEM",
"savings_balance": "0.000 STEEM",
"reward_steem_balance": "0.000 STEEM",
"vesting_shares": "1033.975338 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "7109.684468 VESTS",
"sbd_balance": "0.000 SBD",
"savings_sbd_balance": "0.000 SBD",
"reward_sbd_balance": "0.000 SBD",
"conversions": []
}Account Info
| name | sushrest |
| id | 249693 |
| rank | 704,111 |
| reputation | 52820647 |
| created | 2017-07-09T01:58:27 |
| recovery_account | steem |
| proxy | None |
| post_count | 8 |
| comment_count | 0 |
| lifetime_vote_count | 0 |
| witnesses_voted_for | 0 |
| last_post | 2018-08-18T23:40:03 |
| last_root_post | 2018-08-18T23:40:03 |
| last_vote_time | 2018-06-13T07:22:42 |
| proxied_vsf_votes | 0, 0, 0, 0 |
| can_vote | 1 |
| voting_power | 0 |
| delayed_votes | 0 |
| balance | 0.001 STEEM |
| savings_balance | 0.000 STEEM |
| sbd_balance | 0.000 SBD |
| savings_sbd_balance | 0.000 SBD |
| vesting_shares | 1033.975338 VESTS |
| delegated_vesting_shares | 0.000000 VESTS |
| received_vesting_shares | 7109.684468 VESTS |
| reward_vesting_balance | 4.132584 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 | 2017-09-19T10:35:09 |
| last_account_update | 2018-05-23T07:18:06 |
| mined | No |
| sbd_seconds | 0 |
| sbd_last_interest_payment | 1970-01-01T00:00:00 |
| savings_sbd_last_interest_payment | 1970-01-01T00:00:00 |
{
"id": 249693,
"name": "sushrest",
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM6sjkgmqMf1VmNkN4xgeT87mPCFoNe9mAETNCSce9V1murU4SKb",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM6rYQKo9oPiqCqMU4gTRFtV59AvQLrU7KALRfWyENbxiuHPDcLT",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [
[
"dtube.app",
1
]
],
"key_auths": [
[
"STM6j3w66atSfSCqKrmhFcYrFaKK2b2LyvtBmHzvWtBueTpSxEuhV",
1
]
]
},
"memo_key": "STM7dJyhjRjyq1TrgcCSq5w5NPbmUk3B23gV9Rz5nxZ55YwFncTN6",
"json_metadata": "{\"profile\":{\"location\":\"Sydney\",\"website\":\"https://www.sastoramro.com\",\"profile_image\":\"https://steemitimages.com/DQmTWk7F2EtaphSjD7SZHU8P5b8EbYYgdr2zMVFxJ8i8eX5/myAvatar.png\"}}",
"posting_json_metadata": "{\"profile\":{\"location\":\"Sydney\",\"website\":\"https://www.sastoramro.com\",\"profile_image\":\"https://steemitimages.com/DQmTWk7F2EtaphSjD7SZHU8P5b8EbYYgdr2zMVFxJ8i8eX5/myAvatar.png\"}}",
"proxy": "",
"last_owner_update": "2017-09-19T10:35:09",
"last_account_update": "2018-05-23T07:18:06",
"created": "2017-07-09T01:58:27",
"mined": false,
"recovery_account": "steem",
"last_account_recovery": "1970-01-01T00:00:00",
"reset_account": "null",
"comment_count": 0,
"lifetime_vote_count": 0,
"post_count": 8,
"can_vote": true,
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779087888
},
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779087888
},
"voting_power": 0,
"balance": "0.001 STEEM",
"savings_balance": "0.000 STEEM",
"sbd_balance": "0.000 SBD",
"sbd_seconds": "0",
"sbd_seconds_last_update": "1970-01-01T00:00:00",
"sbd_last_interest_payment": "1970-01-01T00:00:00",
"savings_sbd_balance": "0.000 SBD",
"savings_sbd_seconds": "0",
"savings_sbd_seconds_last_update": "1970-01-01T00:00:00",
"savings_sbd_last_interest_payment": "1970-01-01T00:00:00",
"savings_withdraw_requests": 0,
"reward_sbd_balance": "0.000 SBD",
"reward_steem_balance": "0.000 STEEM",
"reward_vesting_balance": "4.132584 VESTS",
"reward_vesting_steem": "0.002 STEEM",
"vesting_shares": "1033.975338 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "7109.684468 VESTS",
"vesting_withdraw_rate": "0.000000 VESTS",
"next_vesting_withdrawal": "1969-12-31T23:59:59",
"withdrawn": 0,
"to_withdraw": 0,
"withdraw_routes": 0,
"curation_rewards": 2,
"posting_rewards": 0,
"proxied_vsf_votes": [
0,
0,
0,
0
],
"witnesses_voted_for": 0,
"last_post": "2018-08-18T23:40:03",
"last_root_post": "2018-08-18T23:40:03",
"last_vote_time": "2018-06-13T07:22:42",
"post_bandwidth": 0,
"pending_claimed_accounts": 0,
"vesting_balance": "0.000 STEEM",
"reputation": 52820647,
"transfer_history": [],
"market_history": [],
"post_history": [],
"vote_history": [],
"other_history": [],
"witness_votes": [],
"tags_usage": [],
"guest_bloggers": [],
"rank": 704111
}Withdraw Routes
| Incoming | Outgoing |
|---|---|
Empty | Empty |
{
"incoming": [],
"outgoing": []
}From Date
To Date
2026/05/18 07:04:48
2026/05/18 07:04:48
| delegator | steem |
| delegatee | sushrest |
| vesting shares | 7109.684468 VESTS |
| Transaction Info | Block #106151606/Trx 84b9945273afde41ba42d3f7433dcd785b71b75b |
View Raw JSON Data
{
"trx_id": "84b9945273afde41ba42d3f7433dcd785b71b75b",
"block": 106151606,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-05-18T07:04:48",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sushrest",
"vesting_shares": "7109.684468 VESTS"
}
]
}2026/05/13 07:35:33
2026/05/13 07:35:33
| delegator | steem |
| delegatee | sushrest |
| vesting shares | 4397.474063 VESTS |
| Transaction Info | Block #106008936/Trx b5a40d85b485a6ba3c05da0fda49168812b8661c |
View Raw JSON Data
{
"trx_id": "b5a40d85b485a6ba3c05da0fda49168812b8661c",
"block": 106008936,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-05-13T07:35:33",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sushrest",
"vesting_shares": "4397.474063 VESTS"
}
]
}2026/04/26 06:15:30
2026/04/26 06:15:30
| delegator | steem |
| delegatee | sushrest |
| vesting shares | 7122.200224 VESTS |
| Transaction Info | Block #105519070/Trx 674783a5d81878ccfc09d73e2fe04231ca5529a7 |
View Raw JSON Data
{
"trx_id": "674783a5d81878ccfc09d73e2fe04231ca5529a7",
"block": 105519070,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-04-26T06:15:30",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sushrest",
"vesting_shares": "7122.200224 VESTS"
}
]
}2026/01/24 02:10:45
2026/01/24 02:10:45
| delegator | steem |
| delegatee | sushrest |
| vesting shares | 4439.020882 VESTS |
| Transaction Info | Block #102873826/Trx 7f647049ca4dcf7ef21d25a8026beb44922f6305 |
View Raw JSON Data
{
"trx_id": "7f647049ca4dcf7ef21d25a8026beb44922f6305",
"block": 102873826,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-01-24T02:10:45",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sushrest",
"vesting_shares": "4439.020882 VESTS"
}
]
}2024/12/17 21:20:06
2024/12/17 21:20:06
| delegator | steem |
| delegatee | sushrest |
| vesting shares | 4603.240079 VESTS |
| Transaction Info | Block #91320028/Trx 54e967ca0f551b21bd1afc79000c6431c64dc2c3 |
View Raw JSON Data
{
"trx_id": "54e967ca0f551b21bd1afc79000c6431c64dc2c3",
"block": 91320028,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2024-12-17T21:20:06",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sushrest",
"vesting_shares": "4603.240079 VESTS"
}
]
}2023/11/14 12:59:42
2023/11/14 12:59:42
| delegator | steem |
| delegatee | sushrest |
| vesting shares | 4772.373611 VESTS |
| Transaction Info | Block #79874137/Trx b4ad36a76ff08a6ea7aa433b9e3cd71d185919b2 |
View Raw JSON Data
{
"trx_id": "b4ad36a76ff08a6ea7aa433b9e3cd71d185919b2",
"block": 79874137,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2023-11-14T12:59:42",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sushrest",
"vesting_shares": "4772.373611 VESTS"
}
]
}2023/09/22 11:19:57
2023/09/22 11:19:57
| delegator | steem |
| delegatee | sushrest |
| vesting shares | 7709.282397 VESTS |
| Transaction Info | Block #78363990/Trx 5109c49d3535714197d9b1ed3e5ee2d7884dd0c1 |
View Raw JSON Data
{
"trx_id": "5109c49d3535714197d9b1ed3e5ee2d7884dd0c1",
"block": 78363990,
"trx_in_block": 13,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2023-09-22T11:19:57",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sushrest",
"vesting_shares": "7709.282397 VESTS"
}
]
}2022/11/03 18:40:48
2022/11/03 18:40:48
| delegator | steem |
| delegatee | sushrest |
| vesting shares | 7931.333835 VESTS |
| Transaction Info | Block #69121593/Trx b240f18ed5db96a2dfc75a4647d3abd54f4e50d2 |
View Raw JSON Data
{
"trx_id": "b240f18ed5db96a2dfc75a4647d3abd54f4e50d2",
"block": 69121593,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2022-11-03T18:40:48",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sushrest",
"vesting_shares": "7931.333835 VESTS"
}
]
}2022/01/17 23:47:51
2022/01/17 23:47:51
| delegator | steem |
| delegatee | sushrest |
| vesting shares | 8151.441436 VESTS |
| Transaction Info | Block #60824748/Trx 460cd590c3cb1aae47a6840571f9aa05bfb87980 |
View Raw JSON Data
{
"trx_id": "460cd590c3cb1aae47a6840571f9aa05bfb87980",
"block": 60824748,
"trx_in_block": 14,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2022-01-17T23:47:51",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sushrest",
"vesting_shares": "8151.441436 VESTS"
}
]
}2021/06/14 06:56:45
2021/06/14 06:56:45
| delegator | steem |
| delegatee | sushrest |
| vesting shares | 8335.635724 VESTS |
| Transaction Info | Block #54615028/Trx cd7352b84751f2a2c256062e43a9072adc1d8b38 |
View Raw JSON Data
{
"trx_id": "cd7352b84751f2a2c256062e43a9072adc1d8b38",
"block": 54615028,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2021-06-14T06:56:45",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sushrest",
"vesting_shares": "8335.635724 VESTS"
}
]
}2020/12/11 17:08:21
2020/12/11 17:08:21
| delegator | steem |
| delegatee | sushrest |
| vesting shares | 8523.057698 VESTS |
| Transaction Info | Block #49362269/Trx b7f8ac745602fad1700b21679e1e433c8a277bc0 |
View Raw JSON Data
{
"trx_id": "b7f8ac745602fad1700b21679e1e433c8a277bc0",
"block": 49362269,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-12-11T17:08:21",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sushrest",
"vesting_shares": "8523.057698 VESTS"
}
]
}2020/12/06 10:43:42
2020/12/06 10:43:42
| delegator | steem |
| delegatee | sushrest |
| vesting shares | 1912.543513 VESTS |
| Transaction Info | Block #49213779/Trx 042274c3de3f6308abb5f8d5af19c7c0dd22b5b9 |
View Raw JSON Data
{
"trx_id": "042274c3de3f6308abb5f8d5af19c7c0dd22b5b9",
"block": 49213779,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-12-06T10:43:42",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sushrest",
"vesting_shares": "1912.543513 VESTS"
}
]
}2020/12/05 20:46:15
2020/12/05 20:46:15
| delegator | steem |
| delegatee | sushrest |
| vesting shares | 8529.265552 VESTS |
| Transaction Info | Block #49197356/Trx 994879df021690f7dfb70a01fcf6110f20965d63 |
View Raw JSON Data
{
"trx_id": "994879df021690f7dfb70a01fcf6110f20965d63",
"block": 49197356,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-12-05T20:46:15",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sushrest",
"vesting_shares": "8529.265552 VESTS"
}
]
}2020/11/03 04:09:42
2020/11/03 04:09:42
| delegator | steem |
| delegatee | sushrest |
| vesting shares | 1920.017158 VESTS |
| Transaction Info | Block #48272546/Trx 5ac0bd8176efa79d56639c09ed62eed09f5eb7a5 |
View Raw JSON Data
{
"trx_id": "5ac0bd8176efa79d56639c09ed62eed09f5eb7a5",
"block": 48272546,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-11-03T04:09:42",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sushrest",
"vesting_shares": "1920.017158 VESTS"
}
]
}2020/05/09 11:47:36
2020/05/09 11:47:36
| delegator | steem |
| delegatee | sushrest |
| vesting shares | 8732.070911 VESTS |
| Transaction Info | Block #43224125/Trx 9f2f61c30d1b3adc9362a4cb3a64f155292d5254 |
View Raw JSON Data
{
"trx_id": "9f2f61c30d1b3adc9362a4cb3a64f155292d5254",
"block": 43224125,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-05-09T11:47:36",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sushrest",
"vesting_shares": "8732.070911 VESTS"
}
]
}2020/05/08 16:18:00
2020/05/08 16:18:00
| delegator | steem |
| delegatee | sushrest |
| vesting shares | 1953.311140 VESTS |
| Transaction Info | Block #43201289/Trx f29ffcdf952954458b2818023c19eb5bb83149c9 |
View Raw JSON Data
{
"trx_id": "f29ffcdf952954458b2818023c19eb5bb83149c9",
"block": 43201289,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-05-08T16:18:00",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sushrest",
"vesting_shares": "1953.311140 VESTS"
}
]
}2019/11/01 09:42:42
2019/11/01 09:42:42
| delegator | steem |
| delegatee | sushrest |
| vesting shares | 8838.469994 VESTS |
| Transaction Info | Block #37790431/Trx 124761c0e5cbbb08c0cf51cb473cbf0fc22a497a |
View Raw JSON Data
{
"trx_id": "124761c0e5cbbb08c0cf51cb473cbf0fc22a497a",
"block": 37790431,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-11-01T09:42:42",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sushrest",
"vesting_shares": "8838.469994 VESTS"
}
]
}2019/08/22 16:53:45
2019/08/22 16:53:45
| from | dtube |
| to | sushrest |
| amount | 0.001 STEEM |
| memo | Time is running out, claim your DTube account now before anyone else can! Login at https://d.tube |
| Transaction Info | Block #35780284/Trx edcfde103f350d9d29546b82df4d988cffecb5af |
View Raw JSON Data
{
"trx_id": "edcfde103f350d9d29546b82df4d988cffecb5af",
"block": 35780284,
"trx_in_block": 14,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-08-22T16:53:45",
"op": [
"transfer",
{
"from": "dtube",
"to": "sushrest",
"amount": "0.001 STEEM",
"memo": "Time is running out, claim your DTube account now before anyone else can! Login at https://d.tube"
}
]
}sushrestupvoted (100.00%) @sushrest / merging-2-repositories-to-preserve-history-using-grafting2019/07/15 06:44:15
sushrestupvoted (100.00%) @sushrest / merging-2-repositories-to-preserve-history-using-grafting
2019/07/15 06:44:15
| voter | sushrest |
| author | sushrest |
| permlink | merging-2-repositories-to-preserve-history-using-grafting |
| weight | 10000 (100.00%) |
| Transaction Info | Block #34676704/Trx 71a76f8137875338fec1143bd81f2f9c51cc3cc2 |
View Raw JSON Data
{
"trx_id": "71a76f8137875338fec1143bd81f2f9c51cc3cc2",
"block": 34676704,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-07-15T06:44:15",
"op": [
"vote",
{
"voter": "sushrest",
"author": "sushrest",
"permlink": "merging-2-repositories-to-preserve-history-using-grafting",
"weight": 10000
}
]
}2019/07/09 03:43:03
2019/07/09 03:43:03
| parent author | sushrest |
| parent permlink | merging-2-repositories-to-preserve-history-using-grafting |
| author | steemitboard |
| permlink | steemitboard-notify-sushrest-20190709t034302000z |
| title | |
| body | Congratulations @sushrest! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@sushrest/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/@sushrest) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=sushrest)_</sub> ###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| Transaction Info | Block #34500454/Trx c0799551216cc59e3b7feff4ca79a23129b0e85f |
View Raw JSON Data
{
"trx_id": "c0799551216cc59e3b7feff4ca79a23129b0e85f",
"block": 34500454,
"trx_in_block": 12,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-07-09T03:43:03",
"op": [
"comment",
{
"parent_author": "sushrest",
"parent_permlink": "merging-2-repositories-to-preserve-history-using-grafting",
"author": "steemitboard",
"permlink": "steemitboard-notify-sushrest-20190709t034302000z",
"title": "",
"body": "Congratulations @sushrest! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@sushrest/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/@sushrest) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=sushrest)_</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\"]}"
}
]
}2018/11/26 19:39:27
2018/11/26 19:39:27
| delegator | steem |
| delegatee | sushrest |
| vesting shares | 9035.945371 VESTS |
| Transaction Info | Block #28046530/Trx 6edd4a50338d08ae31385d74ef81ceb58fcb1db6 |
View Raw JSON Data
{
"trx_id": "6edd4a50338d08ae31385d74ef81ceb58fcb1db6",
"block": 28046530,
"trx_in_block": 25,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-11-26T19:39:27",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sushrest",
"vesting_shares": "9035.945371 VESTS"
}
]
}2018/09/22 01:50:45
2018/09/22 01:50:45
| delegator | steem |
| delegatee | sushrest |
| vesting shares | 29283.197346 VESTS |
| Transaction Info | Block #26154657/Trx 0c8bc80c02ce0c120781526ab9e51135276db9b0 |
View Raw JSON Data
{
"trx_id": "0c8bc80c02ce0c120781526ab9e51135276db9b0",
"block": 26154657,
"trx_in_block": 21,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-09-22T01:50:45",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sushrest",
"vesting_shares": "29283.197346 VESTS"
}
]
}sushrestpublished a new post: merging-2-repositories-to-preserve-history-using-grafting2018/08/19 03:27:54
sushrestpublished a new post: merging-2-repositories-to-preserve-history-using-grafting
2018/08/19 03:27:54
| parent author | |
| parent permlink | git |
| author | sushrest |
| permlink | merging-2-repositories-to-preserve-history-using-grafting |
| title | Merging 2 repositories to preserve history using grafting |
| body | @@ -651,16 +651,17 @@ wing%0A%60%60%60 +%0A legacy g @@ -879,24 +879,32 @@ push)%0A%60%60%60 %0A%0A + %0A Now fetch fi |
| json metadata | {"tags":["git","grafting","merge","preserve","history"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #25193432/Trx e7fd3b5df308ca1e4de728dd26ae74767ca198b1 |
View Raw JSON Data
{
"trx_id": "e7fd3b5df308ca1e4de728dd26ae74767ca198b1",
"block": 25193432,
"trx_in_block": 23,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-08-19T03:27:54",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "git",
"author": "sushrest",
"permlink": "merging-2-repositories-to-preserve-history-using-grafting",
"title": "Merging 2 repositories to preserve history using grafting",
"body": "@@ -651,16 +651,17 @@\n wing%0A%60%60%60\n+%0A\n legacy g\n@@ -879,24 +879,32 @@\n push)%0A%60%60%60 %0A%0A\n+ %0A\n Now fetch fi\n",
"json_metadata": "{\"tags\":[\"git\",\"grafting\",\"merge\",\"preserve\",\"history\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}2018/08/18 23:47:15
2018/08/18 23:47:15
| voter | hackerzizon |
| author | sushrest |
| permlink | merging-2-repositories-to-preserve-history-using-grafting |
| weight | 100 (1.00%) |
| Transaction Info | Block #25189021/Trx 96679090612239413988d13cbf521748697f3e3f |
View Raw JSON Data
{
"trx_id": "96679090612239413988d13cbf521748697f3e3f",
"block": 25189021,
"trx_in_block": 10,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-08-18T23:47:15",
"op": [
"vote",
{
"voter": "hackerzizon",
"author": "sushrest",
"permlink": "merging-2-repositories-to-preserve-history-using-grafting",
"weight": 100
}
]
}sushrestpublished a new post: merging-2-repositories-to-preserve-history-using-grafting2018/08/18 23:45:18
sushrestpublished a new post: merging-2-repositories-to-preserve-history-using-grafting
2018/08/18 23:45:18
| parent author | |
| parent permlink | git |
| author | sushrest |
| permlink | merging-2-repositories-to-preserve-history-using-grafting |
| title | Merging 2 repositories to preserve history using grafting |
| body | @@ -881,16 +881,17 @@ h)%0A%60%60%60 %0A +%0A Now fetc |
| json metadata | {"tags":["git","grafting","merge","preserve","history"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #25188982/Trx 9eed07b22785e5e65a2e11443b6d90f361f6e92c |
View Raw JSON Data
{
"trx_id": "9eed07b22785e5e65a2e11443b6d90f361f6e92c",
"block": 25188982,
"trx_in_block": 17,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-08-18T23:45:18",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "git",
"author": "sushrest",
"permlink": "merging-2-repositories-to-preserve-history-using-grafting",
"title": "Merging 2 repositories to preserve history using grafting",
"body": "@@ -881,16 +881,17 @@\n h)%0A%60%60%60 %0A\n+%0A\n Now fetc\n",
"json_metadata": "{\"tags\":[\"git\",\"grafting\",\"merge\",\"preserve\",\"history\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}sushrestpublished a new post: merging-2-repositories-to-preserve-history-using-grafting2018/08/18 23:44:51
sushrestpublished a new post: merging-2-repositories-to-preserve-history-using-grafting
2018/08/18 23:44:51
| parent author | |
| parent permlink | git |
| author | sushrest |
| permlink | merging-2-repositories-to-preserve-history-using-grafting |
| title | Merging 2 repositories to preserve history using grafting |
| body | ### Why Grafting is usually required on a software project when migrating from one version control system to other preserving the history of all the commit list previously made prior to migration or when merging the two master branches from 2 repositories of the same project. ### Sample Steps to graft using git replace In this case, I will show you how to pull all the history from a legacy repository (legacy-repo.git) to latest repository (latest-repo.git) ```git clone latest-repo.git``` ```cd latest-repo``` ```git remote add legacy legacy-repo.git``` Now check if remote repository has been applied ```git remote -v``` You will see following ```legacy [email protected]:<user>/legacy-repo.git (fetch) legacy [email protected]:<user>/legacy-repo.git (push) origin [email protected]:<user>/latest-repo.git (fetch) origin [email protected]:<user>/latest-repo.git (push) ``` Now fetch files from legacy repository using ```git fetch legacy``` Now Create local legacy branch from the legacy repository ```git checkout -b legacy legacy/master``` Now use git log to find the last commit of the legacy-repo ```git rev-parse --verify origin``` You will see something like below ``` 6ef9179f1d3f1f16a7b5c836365d8b98834f4a7b ``` Now tag this with name 'last' ```git tag last 6ef9179f1d3f1f16a7b5c836365d8b98834f4a7b``` Now checkout latest repo master branch by ```git checkout master``` Get the first commit of the latest repository (latest-repo.git) ```git log --max-parents=0``` You should see something like this ``` commit 4c3e193a473b305857413587845a5c9e722533f4 ``` Now tag it with name first ```git tag first 4c3e193a473b305857413587845a5c9e722533f4``` Now verity tag list ```git tag``` You will see ``` first last ``` Now Graft using git replace ```git replace first last``` Now remove legacy remote url ```git remote rm legacy``` Now verify if the legacy url is removed by ```git remote -v``` You will see only origin with latest-repo.git ``` origin [email protected]:<user>/latest-repo.git (fetch) origin [email protected]:<user>/latest-repo.git (push) ``` Now push the legacy repository with histories to latest repo ```git push --set-upstream origin legacy``` Done! You should see the full history of legacy and current repository on your commit list. |
| json metadata | {"tags":["git","grafting","merge","preserve","history"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #25188973/Trx da8d6505ea17e1c2a5ed41b42f8ad1938b9ef109 |
View Raw JSON Data
{
"trx_id": "da8d6505ea17e1c2a5ed41b42f8ad1938b9ef109",
"block": 25188973,
"trx_in_block": 26,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-08-18T23:44:51",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "git",
"author": "sushrest",
"permlink": "merging-2-repositories-to-preserve-history-using-grafting",
"title": "Merging 2 repositories to preserve history using grafting",
"body": "### Why\nGrafting is usually required on a software project when migrating from one version control system to other preserving the history of all the commit list previously made prior to migration or when merging the two master branches from 2 repositories of the same project.\n\n### Sample Steps to graft using git replace\nIn this case, I will show you how to pull all the history from a legacy repository (legacy-repo.git) to latest repository (latest-repo.git)\n\n```git clone latest-repo.git```\n```cd latest-repo```\n```git remote add legacy legacy-repo.git```\n\nNow check if remote repository has been applied \n```git remote -v``` \n\nYou will see following\n```legacy [email protected]:<user>/legacy-repo.git (fetch) \nlegacy [email protected]:<user>/legacy-repo.git (push) \norigin [email protected]:<user>/latest-repo.git (fetch) \norigin [email protected]:<user>/latest-repo.git (push)\n``` \nNow fetch files from legacy repository using \n```git fetch legacy```\n\nNow Create local legacy branch from the legacy repository \n```git checkout -b legacy legacy/master``` \n\nNow use git log to find the last commit of the legacy-repo\n```git rev-parse --verify origin``` \n\nYou will see something like below \n```\n6ef9179f1d3f1f16a7b5c836365d8b98834f4a7b \n```\nNow tag this with name 'last'\n```git tag last 6ef9179f1d3f1f16a7b5c836365d8b98834f4a7b``` \n\nNow checkout latest repo master branch by \n```git checkout master``` \n\nGet the first commit of the latest repository (latest-repo.git)\n```git log --max-parents=0``` \n\nYou should see something like this\n```\ncommit 4c3e193a473b305857413587845a5c9e722533f4 \n```\nNow tag it with name first \n```git tag first 4c3e193a473b305857413587845a5c9e722533f4``` \n\nNow verity tag list \n```git tag``` \n\nYou will see \n```\nfirst\nlast\n```\n\nNow Graft using git replace\n```git replace first last``` \n\nNow remove legacy remote url \n```git remote rm legacy```\n\nNow verify if the legacy url is removed by \n```git remote -v```\n\nYou will see only origin with latest-repo.git\n```\norigin [email protected]:<user>/latest-repo.git (fetch) \norigin [email protected]:<user>/latest-repo.git (push)\n``` \n\nNow push the legacy repository with histories to latest repo\n```git push --set-upstream origin legacy```\n\nDone! \n\nYou should see the full history of legacy and current repository on your commit list.",
"json_metadata": "{\"tags\":[\"git\",\"grafting\",\"merge\",\"preserve\",\"history\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}alphabotupvoted (1.00%) @sushrest / merging-2-repositories-to-preserve-history-using-grafting2018/08/18 23:40:15
alphabotupvoted (1.00%) @sushrest / merging-2-repositories-to-preserve-history-using-grafting
2018/08/18 23:40:15
| voter | alphabot |
| author | sushrest |
| permlink | merging-2-repositories-to-preserve-history-using-grafting |
| weight | 100 (1.00%) |
| Transaction Info | Block #25188881/Trx 1bf6a04048a6766d6f02b3a9fe34762d6877c301 |
View Raw JSON Data
{
"trx_id": "1bf6a04048a6766d6f02b3a9fe34762d6877c301",
"block": 25188881,
"trx_in_block": 13,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-08-18T23:40:15",
"op": [
"vote",
{
"voter": "alphabot",
"author": "sushrest",
"permlink": "merging-2-repositories-to-preserve-history-using-grafting",
"weight": 100
}
]
}sushrestpublished a new post: merging-2-repositories-to-preserve-history-using-grafting2018/08/18 23:40:03
sushrestpublished a new post: merging-2-repositories-to-preserve-history-using-grafting
2018/08/18 23:40:03
| parent author | |
| parent permlink | git |
| author | sushrest |
| permlink | merging-2-repositories-to-preserve-history-using-grafting |
| title | Merging 2 repositories to preserve history using grafting |
| body | <html> <p>### Why</p> <p>Grafting is usually required on a software project when migrating from one version control system to other preserving the history of all the commit list previously made prior to migration or when merging the two master branches from 2 repositories of the same project.</p> <p><br></p> <p>### Sample Steps to graft using git replace</p> <p>In this case, I will show you how to pull all the history from a legacy repository (legacy-repo.git) to latest repository (latest-repo.git)</p> <p><br></p> <p>```git clone latest-repo.git```</p> <p>```cd latest-repo```</p> <p>```git remote add legacy legacy-repo.git```</p> <p><br></p> <p>Now check if remote repository has been applied </p> <p>```git remote -v``` </p> <p><br></p> <p>You will see following</p> <p>```legacy [email protected]:<user>/legacy-repo.git (fetch) </p> <p>legacy [email protected]:<user>/legacy-repo.git (push) </p> <p>origin [email protected]:<user>/latest-repo.git (fetch) </p> <p>origin [email protected]:<user>/latest-repo.git (push)</p> <p>``` </p> <p>Now fetch files from legacy repository using </p> <p>```git fetch legacy```</p> <p><br></p> <p>Now Create local legacy branch from the legacy repository </p> <p>```git checkout -b legacy legacy/master``` </p> <p><br></p> <p>Now use git log to find the last commit of the legacy-repo</p> <p>```git rev-parse --verify origin``` </p> <p><br></p> <p>You will see something like below </p> <p>```</p> <p>6ef9179f1d3f1f16a7b5c836365d8b98834f4a7b </p> <p>```</p> <p>Now tag this with name 'last'</p> <p>```git tag last 6ef9179f1d3f1f16a7b5c836365d8b98834f4a7b``` </p> <p><br></p> <p>Now checkout latest repo master branch by </p> <p>```git checkout master``` </p> <p><br></p> <p>Get the first commit of the latest repository (latest-repo.git)</p> <p>```git log --max-parents=0``` </p> <p><br></p> <p>You should see something like this</p> <p>```</p> <p>commit 4c3e193a473b305857413587845a5c9e722533f4 </p> <p>```</p> <p>Now tag it with name first </p> <p>```git tag first 4c3e193a473b305857413587845a5c9e722533f4``` </p> <p><br></p> <p>Now verity tag list </p> <p>```git tag``` </p> <p><br></p> <p>You will see </p> <p>```</p> <p>first</p> <p>last</p> <p>```</p> <p><br></p> <p>Now Graft using git replace</p> <p>```git replace first last``` </p> <p><br></p> <p>Now remove legacy remote url </p> <p>```git remote rm legacy```</p> <p><br></p> <p>Now verify if the legacy url is removed by </p> <p>```git remote -v```</p> <p><br></p> <p>You will see only origin with latest-repo.git</p> <p>```</p> <p>origin [email protected]:<user>/latest-repo.git (fetch) </p> <p>origin [email protected]:<user>/latest-repo.git (push)</p> <p>``` </p> <p><br></p> <p>Now push the legacy repository with histories to latest repo</p> <p>```git push --set-upstream origin legacy```</p> <p><br></p> <p>Done! </p> <p><br></p> <p>You should see the full history of legacy and current repository on your commit list.</p> <p><br></p> </html> |
| json metadata | {"tags":["git","grafting","merge","preserve","history"],"app":"steemit/0.1","format":"html"} |
| Transaction Info | Block #25188877/Trx cf0dbdad996f55186783d37c9df18e33206cfb1e |
View Raw JSON Data
{
"trx_id": "cf0dbdad996f55186783d37c9df18e33206cfb1e",
"block": 25188877,
"trx_in_block": 18,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-08-18T23:40:03",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "git",
"author": "sushrest",
"permlink": "merging-2-repositories-to-preserve-history-using-grafting",
"title": "Merging 2 repositories to preserve history using grafting",
"body": "<html>\n<p>### Why</p>\n<p>Grafting is usually required on a software project when migrating from one version control system to other preserving the history of all the commit list previously made prior to migration or when merging the two master branches from 2 repositories of the same project.</p>\n<p><br></p>\n<p>### Sample Steps to graft using git replace</p>\n<p>In this case, I will show you how to pull all the history from a legacy repository (legacy-repo.git) to latest repository (latest-repo.git)</p>\n<p><br></p>\n<p>```git clone latest-repo.git```</p>\n<p>```cd latest-repo```</p>\n<p>```git remote add legacy legacy-repo.git```</p>\n<p><br></p>\n<p>Now check if remote repository has been applied </p>\n<p>```git remote -v``` </p>\n<p><br></p>\n<p>You will see following</p>\n<p>```legacy [email protected]:<user>/legacy-repo.git (fetch) </p>\n<p>legacy [email protected]:<user>/legacy-repo.git (push) </p>\n<p>origin [email protected]:<user>/latest-repo.git (fetch) </p>\n<p>origin [email protected]:<user>/latest-repo.git (push)</p>\n<p>``` </p>\n<p>Now fetch files from legacy repository using </p>\n<p>```git fetch legacy```</p>\n<p><br></p>\n<p>Now Create local legacy branch from the legacy repository </p>\n<p>```git checkout -b legacy legacy/master``` </p>\n<p><br></p>\n<p>Now use git log to find the last commit of the legacy-repo</p>\n<p>```git rev-parse --verify origin``` </p>\n<p><br></p>\n<p>You will see something like below </p>\n<p>```</p>\n<p>6ef9179f1d3f1f16a7b5c836365d8b98834f4a7b </p>\n<p>```</p>\n<p>Now tag this with name 'last'</p>\n<p>```git tag last 6ef9179f1d3f1f16a7b5c836365d8b98834f4a7b``` </p>\n<p><br></p>\n<p>Now checkout latest repo master branch by </p>\n<p>```git checkout master``` </p>\n<p><br></p>\n<p>Get the first commit of the latest repository (latest-repo.git)</p>\n<p>```git log --max-parents=0``` </p>\n<p><br></p>\n<p>You should see something like this</p>\n<p>```</p>\n<p>commit 4c3e193a473b305857413587845a5c9e722533f4 </p>\n<p>```</p>\n<p>Now tag it with name first </p>\n<p>```git tag first 4c3e193a473b305857413587845a5c9e722533f4``` </p>\n<p><br></p>\n<p>Now verity tag list </p>\n<p>```git tag``` </p>\n<p><br></p>\n<p>You will see </p>\n<p>```</p>\n<p>first</p>\n<p>last</p>\n<p>```</p>\n<p><br></p>\n<p>Now Graft using git replace</p>\n<p>```git replace first last``` </p>\n<p><br></p>\n<p>Now remove legacy remote url </p>\n<p>```git remote rm legacy```</p>\n<p><br></p>\n<p>Now verify if the legacy url is removed by </p>\n<p>```git remote -v```</p>\n<p><br></p>\n<p>You will see only origin with latest-repo.git</p>\n<p>```</p>\n<p>origin [email protected]:<user>/latest-repo.git (fetch) </p>\n<p>origin [email protected]:<user>/latest-repo.git (push)</p>\n<p>``` </p>\n<p><br></p>\n<p>Now push the legacy repository with histories to latest repo</p>\n<p>```git push --set-upstream origin legacy```</p>\n<p><br></p>\n<p>Done! </p>\n<p><br></p>\n<p>You should see the full history of legacy and current repository on your commit list.</p>\n<p><br></p>\n</html>",
"json_metadata": "{\"tags\":[\"git\",\"grafting\",\"merge\",\"preserve\",\"history\"],\"app\":\"steemit/0.1\",\"format\":\"html\"}"
}
]
}2018/07/09 03:18:24
2018/07/09 03:18:24
| parent author | sushrest |
| parent permlink | after-nakamoto-concensus-protocol-a-new-protocol-emerged-metastable-consensus-based-on-gossip-protocol |
| author | steemitboard |
| permlink | steemitboard-notify-sushrest-20180709t031826000z |
| title | |
| body | Congratulations @sushrest! You have received a personal award! [](http://steemitboard.com/@sushrest) 1 Year on Steemit <sub>_Click on the badge to view your Board of Honor._</sub> **Do not miss the last post from @steemitboard:** [SteemitBoard World Cup Contest - The semi-finals are coming. Be ready!](https://steemit.com/steemitboard/@steemitboard/steemitboard-world-cup-contest-the-semi-finals-are-coming-be-ready) --- **Participate in the [SteemitBoard World Cup Contest](https://steemit.com/steemitboard/@steemitboard/steemitboard-world-cup-contest-collect-badges-and-win-free-sbd)!** Collect World Cup badges and win free SBD Support the Gold Sponsors of the contest: [@good-karma](https://v2.steemconnect.com/sign/account-witness-vote?witness=good-karma&approve=1) and [@lukestokes](https://v2.steemconnect.com/sign/account-witness-vote?witness=lukestokes.mhth&approve=1) --- > Do you like [SteemitBoard's project](https://steemit.com/@steemitboard)? Then **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| Transaction Info | Block #24013455/Trx fa203b94abdba60d834ee8e985f712eac9af30a0 |
View Raw JSON Data
{
"trx_id": "fa203b94abdba60d834ee8e985f712eac9af30a0",
"block": 24013455,
"trx_in_block": 21,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-07-09T03:18:24",
"op": [
"comment",
{
"parent_author": "sushrest",
"parent_permlink": "after-nakamoto-concensus-protocol-a-new-protocol-emerged-metastable-consensus-based-on-gossip-protocol",
"author": "steemitboard",
"permlink": "steemitboard-notify-sushrest-20180709t031826000z",
"title": "",
"body": "Congratulations @sushrest! You have received a personal award!\n\n[](http://steemitboard.com/@sushrest) 1 Year on Steemit\n<sub>_Click on the badge to view your Board of Honor._</sub>\n\n\n**Do not miss the last post from @steemitboard:**\n[SteemitBoard World Cup Contest - The semi-finals are coming. Be ready!](https://steemit.com/steemitboard/@steemitboard/steemitboard-world-cup-contest-the-semi-finals-are-coming-be-ready)\n\n---\n**Participate in the [SteemitBoard World Cup Contest](https://steemit.com/steemitboard/@steemitboard/steemitboard-world-cup-contest-collect-badges-and-win-free-sbd)!**\nCollect World Cup badges and win free SBD\nSupport the Gold Sponsors of the contest: [@good-karma](https://v2.steemconnect.com/sign/account-witness-vote?witness=good-karma&approve=1) and [@lukestokes](https://v2.steemconnect.com/sign/account-witness-vote?witness=lukestokes.mhth&approve=1)\n\n---\n\n> Do you like [SteemitBoard's project](https://steemit.com/@steemitboard)? Then **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}"
}
]
}2018/06/13 07:22:42
2018/06/13 07:22:42
| voter | sushrest |
| author | crypt0 |
| permlink | tezos-rage-over-kyc-aml-ethereum-classic-on-coinbase-and-binance-coming-psa-crypto-bridge-issues |
| weight | 10000 (100.00%) |
| Transaction Info | Block #23279629/Trx 4a8f0cf2f19d051793655fa38fa9d01455c5ccce |
View Raw JSON Data
{
"trx_id": "4a8f0cf2f19d051793655fa38fa9d01455c5ccce",
"block": 23279629,
"trx_in_block": 10,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-13T07:22:42",
"op": [
"vote",
{
"voter": "sushrest",
"author": "crypt0",
"permlink": "tezos-rage-over-kyc-aml-ethereum-classic-on-coinbase-and-binance-coming-psa-crypto-bridge-issues",
"weight": 10000
}
]
}sushrestremoved vote from (0.00%) @crypt0 / join-me-live-for-an-interview-with-enjin-coin2018/06/13 04:06:15
sushrestremoved vote from (0.00%) @crypt0 / join-me-live-for-an-interview-with-enjin-coin
2018/06/13 04:06:15
| voter | sushrest |
| author | crypt0 |
| permlink | join-me-live-for-an-interview-with-enjin-coin |
| weight | 0 (0.00%) |
| Transaction Info | Block #23275701/Trx 4348e33cd39b7734e840ab148a14d7686eeac1a3 |
View Raw JSON Data
{
"trx_id": "4348e33cd39b7734e840ab148a14d7686eeac1a3",
"block": 23275701,
"trx_in_block": 20,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-13T04:06:15",
"op": [
"vote",
{
"voter": "sushrest",
"author": "crypt0",
"permlink": "join-me-live-for-an-interview-with-enjin-coin",
"weight": 0
}
]
}sushrestupvoted (100.00%) @crypt0 / join-me-live-for-an-interview-with-enjin-coin2018/06/13 04:06:03
sushrestupvoted (100.00%) @crypt0 / join-me-live-for-an-interview-with-enjin-coin
2018/06/13 04:06:03
| voter | sushrest |
| author | crypt0 |
| permlink | join-me-live-for-an-interview-with-enjin-coin |
| weight | 10000 (100.00%) |
| Transaction Info | Block #23275697/Trx 1f5297eec76a0ffa50cf9c1b4fea9041a5285e1f |
View Raw JSON Data
{
"trx_id": "1f5297eec76a0ffa50cf9c1b4fea9041a5285e1f",
"block": 23275697,
"trx_in_block": 31,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-13T04:06:03",
"op": [
"vote",
{
"voter": "sushrest",
"author": "crypt0",
"permlink": "join-me-live-for-an-interview-with-enjin-coin",
"weight": 10000
}
]
}sushrestremoved vote from (0.00%) @hatu / world-bit-bank-a-bank-for-the-global-crypto-communtiy2018/06/07 14:20:18
sushrestremoved vote from (0.00%) @hatu / world-bit-bank-a-bank-for-the-global-crypto-communtiy
2018/06/07 14:20:18
| voter | sushrest |
| author | hatu |
| permlink | world-bit-bank-a-bank-for-the-global-crypto-communtiy |
| weight | 0 (0.00%) |
| Transaction Info | Block #23115790/Trx 1b8153b6eee5cd5d2d6c119d5c25de28a9bc9346 |
View Raw JSON Data
{
"trx_id": "1b8153b6eee5cd5d2d6c119d5c25de28a9bc9346",
"block": 23115790,
"trx_in_block": 27,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-07T14:20:18",
"op": [
"vote",
{
"voter": "sushrest",
"author": "hatu",
"permlink": "world-bit-bank-a-bank-for-the-global-crypto-communtiy",
"weight": 0
}
]
}sushrestupvoted (100.00%) @hatu / world-bit-bank-a-bank-for-the-global-crypto-communtiy2018/06/07 14:20:00
sushrestupvoted (100.00%) @hatu / world-bit-bank-a-bank-for-the-global-crypto-communtiy
2018/06/07 14:20:00
| voter | sushrest |
| author | hatu |
| permlink | world-bit-bank-a-bank-for-the-global-crypto-communtiy |
| weight | 10000 (100.00%) |
| Transaction Info | Block #23115784/Trx 0a4a153146f3beda9ed5e87f105983956302509c |
View Raw JSON Data
{
"trx_id": "0a4a153146f3beda9ed5e87f105983956302509c",
"block": 23115784,
"trx_in_block": 39,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-07T14:20:00",
"op": [
"vote",
{
"voter": "sushrest",
"author": "hatu",
"permlink": "world-bit-bank-a-bank-for-the-global-crypto-communtiy",
"weight": 10000
}
]
}2018/05/29 01:23:12
2018/05/29 01:23:12
| voter | sushrest |
| author | sushrest |
| permlink | after-nakamoto-concensus-protocol-a-new-protocol-emerged-metastable-consensus-based-on-gossip-protocol |
| weight | 10000 (100.00%) |
| Transaction Info | Block #22841133/Trx e65626ee856571ed8f34296a93a36f571513818c |
View Raw JSON Data
{
"trx_id": "e65626ee856571ed8f34296a93a36f571513818c",
"block": 22841133,
"trx_in_block": 17,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-29T01:23:12",
"op": [
"vote",
{
"voter": "sushrest",
"author": "sushrest",
"permlink": "after-nakamoto-concensus-protocol-a-new-protocol-emerged-metastable-consensus-based-on-gossip-protocol",
"weight": 10000
}
]
}2018/05/28 11:04:45
2018/05/28 11:04:45
| parent author | |
| parent permlink | bitcoin |
| author | sushrest |
| permlink | after-nakamoto-concensus-protocol-a-new-protocol-emerged-metastable-consensus-based-on-gossip-protocol |
| title | After Nakamoto concensus protocol a new protocol emerged; Metastable consensus based on gossip protocol |
| body | @@ -4769,16 +4769,17 @@ r second +, Emin an @@ -4872,16 +4872,21 @@ Ethereum +(EVM) . %0A%0A%5BThe |
| json metadata | {"tags":["bitcoin","consensus","protocol","gossip","metastable"],"app":"steemit/0.1","format":"markdown","links":["https://ipfs.io/ipfs/QmUy4jh5mGNZvLkjies1RWM4YuvJh5o2FYopNPVYwrRVGV"]} |
| Transaction Info | Block #22823967/Trx add7a38f9b3140a5e287661919f0781aa3d135d9 |
View Raw JSON Data
{
"trx_id": "add7a38f9b3140a5e287661919f0781aa3d135d9",
"block": 22823967,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-28T11:04:45",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "bitcoin",
"author": "sushrest",
"permlink": "after-nakamoto-concensus-protocol-a-new-protocol-emerged-metastable-consensus-based-on-gossip-protocol",
"title": "After Nakamoto concensus protocol a new protocol emerged; Metastable consensus based on gossip protocol",
"body": "@@ -4769,16 +4769,17 @@\n r second\n+,\n Emin an\n@@ -4872,16 +4872,21 @@\n Ethereum\n+(EVM)\n . %0A%0A%5BThe\n",
"json_metadata": "{\"tags\":[\"bitcoin\",\"consensus\",\"protocol\",\"gossip\",\"metastable\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\",\"links\":[\"https://ipfs.io/ipfs/QmUy4jh5mGNZvLkjies1RWM4YuvJh5o2FYopNPVYwrRVGV\"]}"
}
]
}2018/05/28 10:34:39
2018/05/28 10:34:39
| parent author | |
| parent permlink | bitcoin |
| author | sushrest |
| permlink | after-nakamoto-concensus-protocol-a-new-protocol-emerged-metastable-consensus-based-on-gossip-protocol |
| title | After Nakamoto concensus protocol a new protocol emerged; Metastable consensus based on gossip protocol |
| body | @@ -4086,28 +4086,28 @@ 5 people +, there w -ould +ill be rand @@ -4120,24 +4120,27 @@ iation, and +at the end of t @@ -4168,20 +4168,34 @@ ld have -more +over sampled ether blue or @@ -4286,16 +4286,22 @@ ore blue + nodes , and se @@ -4311,16 +4311,32 @@ d round +we will amplify and the @@ -4420,16 +4420,23 @@ e where +we are either a |
| json metadata | {"tags":["bitcoin","consensus","protocol","gossip"],"app":"steemit/0.1","format":"markdown","links":["https://ipfs.io/ipfs/QmUy4jh5mGNZvLkjies1RWM4YuvJh5o2FYopNPVYwrRVGV"]} |
| Transaction Info | Block #22823365/Trx 6b75efc08d54e6ee9f0011cda88541d14fc83097 |
View Raw JSON Data
{
"trx_id": "6b75efc08d54e6ee9f0011cda88541d14fc83097",
"block": 22823365,
"trx_in_block": 34,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-28T10:34:39",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "bitcoin",
"author": "sushrest",
"permlink": "after-nakamoto-concensus-protocol-a-new-protocol-emerged-metastable-consensus-based-on-gossip-protocol",
"title": "After Nakamoto concensus protocol a new protocol emerged; Metastable consensus based on gossip protocol",
"body": "@@ -4086,28 +4086,28 @@\n 5 people\n+,\n there w\n-ould\n+ill\n be rand\n@@ -4120,24 +4120,27 @@\n iation, and \n+at \n the end of t\n@@ -4168,20 +4168,34 @@\n ld have \n-more\n+over sampled ether\n blue or\n@@ -4286,16 +4286,22 @@\n ore blue\n+ nodes\n , and se\n@@ -4311,16 +4311,32 @@\n d round \n+we will amplify \n and the \n@@ -4420,16 +4420,23 @@\n e where \n+we are \n either a\n",
"json_metadata": "{\"tags\":[\"bitcoin\",\"consensus\",\"protocol\",\"gossip\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\",\"links\":[\"https://ipfs.io/ipfs/QmUy4jh5mGNZvLkjies1RWM4YuvJh5o2FYopNPVYwrRVGV\"]}"
}
]
}2018/05/28 10:19:36
2018/05/28 10:19:36
| parent author | |
| parent permlink | bitcoin |
| author | sushrest |
| permlink | after-nakamoto-concensus-protocol-a-new-protocol-emerged-metastable-consensus-based-on-gossip-protocol |
| title | After Nakamoto concensus protocol a new protocol emerged; Metastable consensus based on gossip protocol |
| body | @@ -4825,24 +4825,25 @@ Ethereum. %0A%0A +%5B The link to @@ -4869,17 +4869,19 @@ in IPFS -%0A +!%5D( https:// @@ -4939,8 +4939,9 @@ VYwrRVGV +) |
| json metadata | {"tags":["bitcoin","consensus","protocol","gossip"],"app":"steemit/0.1","format":"markdown","links":["https://ipfs.io/ipfs/QmUy4jh5mGNZvLkjies1RWM4YuvJh5o2FYopNPVYwrRVGV"]} |
| Transaction Info | Block #22823064/Trx 21df31c6fb73b9f600b31dd4bff459ce55f6cc81 |
View Raw JSON Data
{
"trx_id": "21df31c6fb73b9f600b31dd4bff459ce55f6cc81",
"block": 22823064,
"trx_in_block": 31,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-28T10:19:36",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "bitcoin",
"author": "sushrest",
"permlink": "after-nakamoto-concensus-protocol-a-new-protocol-emerged-metastable-consensus-based-on-gossip-protocol",
"title": "After Nakamoto concensus protocol a new protocol emerged; Metastable consensus based on gossip protocol",
"body": "@@ -4825,24 +4825,25 @@\n Ethereum. %0A%0A\n+%5B\n The link to \n@@ -4869,17 +4869,19 @@\n in IPFS\n-%0A\n+!%5D(\n https://\n@@ -4939,8 +4939,9 @@\n VYwrRVGV\n+)\n",
"json_metadata": "{\"tags\":[\"bitcoin\",\"consensus\",\"protocol\",\"gossip\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\",\"links\":[\"https://ipfs.io/ipfs/QmUy4jh5mGNZvLkjies1RWM4YuvJh5o2FYopNPVYwrRVGV\"]}"
}
]
}2018/05/28 10:18:12
2018/05/28 10:18:12
| parent author | |
| parent permlink | bitcoin |
| author | sushrest |
| permlink | after-nakamoto-concensus-protocol-a-new-protocol-emerged-metastable-consensus-based-on-gossip-protocol |
| title | After Nakamoto concensus protocol a new protocol emerged; Metastable consensus based on gossip protocol |
| body | On 16th of May 2018, an unknown group published a paper claiming a very exciting scientific development called Metastable Consensus protocol. Before this in the past 50 years there have emerged only 2 consensus family called classical consensus protocol and Nakamoto consensus protocol. Emin Gur and his team have been working on this for last 2 years, but sometime around february this year they were contacted by an anonymous group who gave Emin and his team the backbone of this paper they published. They essentially scooped Emin and his team on what they have been trying to do in the past 2 years. He states that the protocol is simple and powerful. It does for distributed system in consensus what gossip protocol did for data dissemination. In the old days when you have something to say and when you wanted to send this across to a bunch of people, you would use what we call a dissemination protocol and again in that time people who built this protocol had rigid structures in mind, more like a distribution tree with different tiers where message flow between different tiers. But this system is inherently fragile where everybody have to know about the tree and everybody have to have to understand where they were on the tree; what their role role was and who their decendents were. At some point at early 90’s people came up with gossip protocol where essentially all you do is you pick a couple of people at random and you tell them what you know and this is an incredibly powerful mechanism for disseminating information. Because this random networks are incredibly robust, you don’t have to know everybody in the system, you just have to know some people and you have to communicate only with them and yet in logarithmic time you get whatever you have to say across to the entire network. So this new consensus protocols known all named after various forms of snow namely: Avalanche, Snow Flakes, Snow Ball. They rely on the randomness and random interaction and yet they ensure that at the end of their interaction everybody has decided on the same thing, and that is a very powerful primitive. At the core of this algorithm there are a series of ideas that they invented that are very powerful, it’s a new way of doing consensus. According to Emin he suggests anyone who is working on anything related to consensus have to stop what they are doing and take a look at this new consensus protocol, as the protocol really promises to revolutionize how one can do consensus for this domain. He is not sure if this will replace proof of work system as he believes that there will be people who really like proof of work system in which case proof of work system can use avalanche protocol for miners to talk to each other and agree on the contents of the next block, whereby making use of avalanche low latency on proof of work ecosystem. The way this works is: If we all were to agree on something for example picking between colors red and blue. In case of Nakamoto consensus we would have miners actually mine before coming to consensus and it would be very costly and as well coin minting would be expensive as a lot of coin needs to be minted to reward the expensive proof of work operation. Whereas if we were to implement a classical consensus protocol where everybody asks everybody else to reach 2/3 plus 1 majority and to reach that majority that node would have to actually know everybody in the system and that these systems are very fragile and that’s why one of the reasons why they have not been deployed at scale. But in the case of this new consensus protocol family what you can do is simply pick some numbers of people for example 5 people, and ask what color they prefer? The node will change its color to what majority in that 5 decided, and this would iterate over and over until a constant number of iteration when all participant nodes end up with the same color, which is quite powerful and quite unexpected. The reason why it works is incredibly simple as well. Imagine a worst case scenario of a network divided 50 50. We all pick 5 people there would be random variation, and the end of the first round we would have more blue or reds. So at the end of the 1st round there would be slightly more red or slightly more blue, and second round and the third and suddenly we will reach a point where we all will fall to one extreme where either all red or all blue. This is what is called Metastable Protocol which means its designed to to not stay balance which is exactly what we want out of consensus protocol and which always fall one side or the other. Because this protocol is light weight with super low latency of around 1-2 secs and many thousand transaction per second Emin and the team is planning to support other existing virtual machines such as Bitcoin and Ethereum. The link to the published paper in IPFS https://ipfs.io/ipfs/QmUy4jh5mGNZvLkjies1RWM4YuvJh5o2FYopNPVYwrRVGV |
| json metadata | {"tags":["bitcoin","consensus","protocol","gossip"],"image":["https://ipfs.io/ipfs/QmUy4jh5mGNZvLkjies1RWM4YuvJh5o2FYopNPVYwrRVGV"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #22823036/Trx 9ff0df40cac1a332819e37afb00c19fb77ecaa0b |
View Raw JSON Data
{
"trx_id": "9ff0df40cac1a332819e37afb00c19fb77ecaa0b",
"block": 22823036,
"trx_in_block": 22,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-28T10:18:12",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "bitcoin",
"author": "sushrest",
"permlink": "after-nakamoto-concensus-protocol-a-new-protocol-emerged-metastable-consensus-based-on-gossip-protocol",
"title": "After Nakamoto concensus protocol a new protocol emerged; Metastable consensus based on gossip protocol",
"body": "On 16th of May 2018, an unknown group published a paper claiming a very exciting scientific development called Metastable Consensus protocol. Before this in the past 50 years there have emerged only 2 consensus family called classical consensus protocol and Nakamoto consensus protocol. \n\nEmin Gur and his team have been working on this for last 2 years, but sometime around february this year they were contacted by an anonymous group who gave Emin and his team the backbone of this paper they published. They essentially scooped Emin and his team on what they have been trying to do in the past 2 years. \n\nHe states that the protocol is simple and powerful. It does for distributed system in consensus what gossip protocol did for data dissemination. In the old days when you have something to say and when you wanted to send this across to a bunch of people, you would use what we call a dissemination protocol and again in that time people who built this protocol had rigid structures in mind, more like a distribution tree with different tiers where message flow between different tiers. But this system is inherently fragile where everybody have to know about the tree and everybody have to have to understand where they were on the tree; what their role role was and who their decendents were.\n\nAt some point at early 90’s people came up with gossip protocol where essentially all you do is you pick a couple of people at random and you tell them what you know and this is an incredibly powerful mechanism for disseminating information. Because this random networks are incredibly robust, you don’t have to know everybody in the system, you just have to know some people and you have to communicate only with them and yet in logarithmic time you get whatever you have to say across to the entire network.\n\nSo this new consensus protocols known all named after various forms of snow namely: Avalanche, Snow Flakes, Snow Ball. They rely on the randomness and random interaction and yet they ensure that at the end of their interaction everybody has decided on the same thing, and that is a very powerful primitive. At the core of this algorithm there are a series of ideas that they invented that are very powerful, it’s a new way of doing consensus. \n\nAccording to Emin he suggests anyone who is working on anything related to consensus have to stop what they are doing and take a look at this new consensus protocol, as the protocol really promises to revolutionize how one can do consensus for this domain. He is not sure if this will replace proof of work system as he believes that there will be people who really like proof of work system in which case proof of work system can use avalanche protocol for miners to talk to each other and agree on the contents of the next block, whereby making use of avalanche low latency on proof of work ecosystem. \n\nThe way this works is:\nIf we all were to agree on something for example picking between colors red and blue. In case of Nakamoto consensus we would have miners actually mine before coming to consensus and it would be very costly and as well coin minting would be expensive as a lot of coin needs to be minted to reward the expensive proof of work operation. Whereas if we were to implement a classical consensus protocol where everybody asks everybody else to reach 2/3 plus 1 majority and to reach that majority that node would have to actually know everybody in the system and that these systems are very fragile and that’s why one of the reasons why they have not been deployed at scale. But in the case of this new consensus protocol family what you can do is simply pick some numbers of people for example 5 people, and ask what color they prefer? The node will change its color to what majority in that 5 decided, and this would iterate over and over until a constant number of iteration when all participant nodes end up with the same color, which is quite powerful and quite unexpected. \nThe reason why it works is incredibly simple as well. Imagine a worst case scenario of a network divided 50 50. We all pick 5 people there would be random variation, and the end of the first round we would have more blue or reds. So at the end of the 1st round there would be slightly more red or slightly more blue, and second round and the third and suddenly we will reach a point where we all will fall to one extreme where either all red or all blue. This is what is called Metastable Protocol which means its designed to to not stay balance which is exactly what we want out of consensus protocol and which always fall one side or the other. \n\nBecause this protocol is light weight with super low latency of around 1-2 secs and many thousand transaction per second Emin and the team is planning to support other existing virtual machines such as Bitcoin and Ethereum. \n\nThe link to the published paper in IPFS\nhttps://ipfs.io/ipfs/QmUy4jh5mGNZvLkjies1RWM4YuvJh5o2FYopNPVYwrRVGV",
"json_metadata": "{\"tags\":[\"bitcoin\",\"consensus\",\"protocol\",\"gossip\"],\"image\":[\"https://ipfs.io/ipfs/QmUy4jh5mGNZvLkjies1RWM4YuvJh5o2FYopNPVYwrRVGV\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}2018/05/28 06:02:03
2018/05/28 06:02:03
| voter | sushrest |
| author | sushrest |
| permlink | o3b8kh1m |
| weight | 10000 (100.00%) |
| Transaction Info | Block #22817914/Trx ee959824cdcb5409414d0dfd1f0557cd271c78e4 |
View Raw JSON Data
{
"trx_id": "ee959824cdcb5409414d0dfd1f0557cd271c78e4",
"block": 22817914,
"trx_in_block": 41,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-28T06:02:03",
"op": [
"vote",
{
"voter": "sushrest",
"author": "sushrest",
"permlink": "o3b8kh1m",
"weight": 10000
}
]
}2018/05/28 05:41:15
2018/05/28 05:41:15
| author | sushrest |
| permlink | o3b8kh1m |
| max accepted payout | 1000000.000 SBD |
| percent steem dollars | 10000 |
| allow votes | true |
| allow curation rewards | true |
| extensions | [[0,{"beneficiaries":[{"account":"dtube","weight":2500}]}]] |
| Transaction Info | Block #22817498/Trx 5802b78c424cd9a335b13841099d075c73d3d4c6 |
View Raw JSON Data
{
"trx_id": "5802b78c424cd9a335b13841099d075c73d3d4c6",
"block": 22817498,
"trx_in_block": 28,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-28T05:41:15",
"op": [
"comment_options",
{
"author": "sushrest",
"permlink": "o3b8kh1m",
"max_accepted_payout": "1000000.000 SBD",
"percent_steem_dollars": 10000,
"allow_votes": true,
"allow_curation_rewards": true,
"extensions": [
[
0,
{
"beneficiaries": [
{
"account": "dtube",
"weight": 2500
}
]
}
]
]
}
]
}2018/05/28 05:41:15
2018/05/28 05:41:15
| parent author | |
| parent permlink | despacito |
| author | sushrest |
| permlink | o3b8kh1m |
| title | Despacito - Luis Fonsi ( Nepali Instrumental Cover by Skin And Bones. Ft. Luwhang ) |
| body | <center><a href='https://d.tube/#!/v/sushrest/o3b8kh1m'><img src='https://ipfs.io/ipfs/QmV9WZRg9DD1Fm547XFYYqbKRuWk7cN2BZmg3nCprU8DUW'></a></center><hr> Despacito - Nepali Instrument Sarangi & Guitar Cover by "Skin and Bones." Sarangi: Manice Gandharva Guitar: Tunna Bell Thapa Arranged, Mixed and Mastered by Tunna Bell Thapa. Dance Performed by Luwhang Vibes Shot/Edit : Deepak Bomjan Video Label : VH Video House Production Nepal Credit & Source: https://www.youtube.com/watch?v=O0wmFe5HUYE <hr><a href='https://d.tube/#!/v/sushrest/o3b8kh1m'> ▶️ DTube</a><br /><a href='https://ipfs.io/ipfs/QmU46PXsNC1rQnkuDy36i4pTxZK7WaT8jnoCCNNhuW7LZL'> ▶️ IPFS</a> |
| json metadata | {"video":{"info":{"title":"Despacito - Luis Fonsi ( Nepali Instrumental Cover by Skin And Bones. Ft. Luwhang )","snaphash":"QmbZMtccqsyUeoC8ZHMJM3rRcJ1Y3KLdYJP9vuabsXQias","author":"sushrest","permlink":"o3b8kh1m","duration":140.016327,"filesize":10595695,"spritehash":"QmeC4eJiaYaaJeUb8Qj96ZRCpFmkhsGmihW1r6Qt1AduJx"},"content":{"videohash":"QmU46PXsNC1rQnkuDy36i4pTxZK7WaT8jnoCCNNhuW7LZL","description":"Despacito - Nepali Instrument Sarangi & Guitar Cover by \"Skin and Bones.\"\n\nSarangi: Manice Gandharva\nGuitar: Tunna Bell Thapa\n\nArranged, Mixed and Mastered by Tunna Bell Thapa.\nDance Performed by Luwhang Vibes\n\nShot/Edit : Deepak Bomjan\nVideo Label : VH Video House Production Nepal \n\nCredit & Source: \nhttps://www.youtube.com/watch?v=O0wmFe5HUYE\n\n","tags":["despacito","nepali","instrumental","skin&bones"],"video480hash":"QmRGtrpSmas4CAATtgD3S6EfuG1ZrnuUfWTpmHhrH1MGh8"}},"tags":["despacito","nepali","instrumental","skin&bones","dtube"],"app":"dtube/0.7"} |
| Transaction Info | Block #22817498/Trx 5802b78c424cd9a335b13841099d075c73d3d4c6 |
View Raw JSON Data
{
"trx_id": "5802b78c424cd9a335b13841099d075c73d3d4c6",
"block": 22817498,
"trx_in_block": 28,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-28T05:41:15",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "despacito",
"author": "sushrest",
"permlink": "o3b8kh1m",
"title": "Despacito - Luis Fonsi ( Nepali Instrumental Cover by Skin And Bones. Ft. Luwhang )",
"body": "<center><a href='https://d.tube/#!/v/sushrest/o3b8kh1m'><img src='https://ipfs.io/ipfs/QmV9WZRg9DD1Fm547XFYYqbKRuWk7cN2BZmg3nCprU8DUW'></a></center><hr>\n\nDespacito - Nepali Instrument Sarangi & Guitar Cover by \"Skin and Bones.\"\n\nSarangi: Manice Gandharva\nGuitar: Tunna Bell Thapa\n\nArranged, Mixed and Mastered by Tunna Bell Thapa.\nDance Performed by Luwhang Vibes\n\nShot/Edit : Deepak Bomjan\nVideo Label : VH Video House Production Nepal \n\nCredit & Source: \nhttps://www.youtube.com/watch?v=O0wmFe5HUYE\n\n<hr><a href='https://d.tube/#!/v/sushrest/o3b8kh1m'> ▶️ DTube</a><br /><a href='https://ipfs.io/ipfs/QmU46PXsNC1rQnkuDy36i4pTxZK7WaT8jnoCCNNhuW7LZL'> ▶️ IPFS</a>",
"json_metadata": "{\"video\":{\"info\":{\"title\":\"Despacito - Luis Fonsi ( Nepali Instrumental Cover by Skin And Bones. Ft. Luwhang )\",\"snaphash\":\"QmbZMtccqsyUeoC8ZHMJM3rRcJ1Y3KLdYJP9vuabsXQias\",\"author\":\"sushrest\",\"permlink\":\"o3b8kh1m\",\"duration\":140.016327,\"filesize\":10595695,\"spritehash\":\"QmeC4eJiaYaaJeUb8Qj96ZRCpFmkhsGmihW1r6Qt1AduJx\"},\"content\":{\"videohash\":\"QmU46PXsNC1rQnkuDy36i4pTxZK7WaT8jnoCCNNhuW7LZL\",\"description\":\"Despacito - Nepali Instrument Sarangi & Guitar Cover by \\\"Skin and Bones.\\\"\\n\\nSarangi: Manice Gandharva\\nGuitar: Tunna Bell Thapa\\n\\nArranged, Mixed and Mastered by Tunna Bell Thapa.\\nDance Performed by Luwhang Vibes\\n\\nShot/Edit : Deepak Bomjan\\nVideo Label : VH Video House Production Nepal \\n\\nCredit & Source: \\nhttps://www.youtube.com/watch?v=O0wmFe5HUYE\\n\\n\",\"tags\":[\"despacito\",\"nepali\",\"instrumental\",\"skin&bones\"],\"video480hash\":\"QmRGtrpSmas4CAATtgD3S6EfuG1ZrnuUfWTpmHhrH1MGh8\"}},\"tags\":[\"despacito\",\"nepali\",\"instrumental\",\"skin&bones\",\"dtube\"],\"app\":\"dtube/0.7\"}"
}
]
}sushrestfollowed @davidvidyasagar2018/05/25 08:37:00
sushrestfollowed @davidvidyasagar
2018/05/25 08:37:00
| required auths | [] |
| required posting auths | ["sushrest"] |
| id | follow |
| json | ["follow",{"follower":"sushrest","following":"davidvidyasagar","what":["blog"]}] |
| Transaction Info | Block #22734628/Trx 3f3e919f419bad881507b6055ffbf458f3e1d305 |
View Raw JSON Data
{
"trx_id": "3f3e919f419bad881507b6055ffbf458f3e1d305",
"block": 22734628,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-25T08:37:00",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"sushrest"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"sushrest\",\"following\":\"davidvidyasagar\",\"what\":[\"blog\"]}]"
}
]
}sushrestpublished a new post: how-to-install-joinmarket-on-mac2018/05/25 06:47:03
sushrestpublished a new post: how-to-install-joinmarket-on-mac
2018/05/25 06:47:03
| parent author | |
| parent permlink | joinmarket |
| author | sushrest |
| permlink | how-to-install-joinmarket-on-mac |
| title | How to install Joinmarket on Mac (Anonymous bitcoin transaction) |
| body | @@ -118,18 +118,16 @@ me for -a help to |
| json metadata | {"tags":["joinmarket","install","mac","bitcoin","anonymous"],"links":["https://docs.docker.com/docker-for-mac/install/","https://download.docker.com/mac/stable/Docker.dmg","https://github.com/JoinMarket-Org/joinmarket/wiki/Sending-payments-with-CoinJoin","https://docs.docker.com/"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #22732430/Trx d8b30573402380b9f39760e7938580c1525ef71d |
View Raw JSON Data
{
"trx_id": "d8b30573402380b9f39760e7938580c1525ef71d",
"block": 22732430,
"trx_in_block": 47,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-25T06:47:03",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "joinmarket",
"author": "sushrest",
"permlink": "how-to-install-joinmarket-on-mac",
"title": "How to install Joinmarket on Mac (Anonymous bitcoin transaction)",
"body": "@@ -118,18 +118,16 @@\n me for \n-a \n help to \n",
"json_metadata": "{\"tags\":[\"joinmarket\",\"install\",\"mac\",\"bitcoin\",\"anonymous\"],\"links\":[\"https://docs.docker.com/docker-for-mac/install/\",\"https://download.docker.com/mac/stable/Docker.dmg\",\"https://github.com/JoinMarket-Org/joinmarket/wiki/Sending-payments-with-CoinJoin\",\"https://docs.docker.com/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}youngogmarqsupvoted (0.02%) @sushrest / how-to-install-joinmarket-on-mac2018/05/24 14:31:12
youngogmarqsupvoted (0.02%) @sushrest / how-to-install-joinmarket-on-mac
2018/05/24 14:31:12
| voter | youngogmarqs |
| author | sushrest |
| permlink | how-to-install-joinmarket-on-mac |
| weight | 2 (0.02%) |
| Transaction Info | Block #22712918/Trx c49059dd9064c71ae14ffdeaae709246da1b75b2 |
View Raw JSON Data
{
"trx_id": "c49059dd9064c71ae14ffdeaae709246da1b75b2",
"block": 22712918,
"trx_in_block": 27,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-24T14:31:12",
"op": [
"vote",
{
"voter": "youngogmarqs",
"author": "sushrest",
"permlink": "how-to-install-joinmarket-on-mac",
"weight": 2
}
]
}sushrestpublished a new post: how-to-install-joinmarket-on-mac2018/05/24 14:30:03
sushrestpublished a new post: how-to-install-joinmarket-on-mac
2018/05/24 14:30:03
| parent author | |
| parent permlink | joinmarket |
| author | sushrest |
| permlink | how-to-install-joinmarket-on-mac |
| title | How to install Joinmarket on Mac (Anonymous bitcoin transaction) |
| body | Installing Joinmarket on Mac can be very tedious, specially for someone who is not tech savvy. A friend of mine asked me for a help to get Joinmarket installed on his Mac as he had a very hard time doing it, So I helped him out. I thought this could help others who are looking to do the same, So thought of doing a SteemIt post. So here are the following steps I took to get Joinmarket installed, total installation time could be around 30-40 mins depending on your internet speed. 1. Install docker by following instruction on following link https://docs.docker.com/docker-for-mac/install/ Or directly download and install https://download.docker.com/mac/stable/Docker.dmg 1. Install ubuntu after installing docker using following command ```docker run -i -t ubuntu /bin/bash``` 1. The above command should install ubuntu and boot it and log you into that OS. 1. Now install joinmarket prerequisites using following command ```apt-get update -y && apt-get upgrade -y && apt-get install python-dev libsodium-dev python-pip -y``` Select Y for Yes 1. Install wget ```apt-get install wget``` Select Y for Yes 1. Install Joinmarket ```wget https://github.com/JoinMarket-Org/joinmarket/archive/v0.2.3.tar.gz -O joinmarket-0.2.3.tar.gz``` 1. Extract with ```tar xzf joinmarket-0.2.3.tar.gz``` and then``` cd joinmarket-0.2.3``` 1. Activate virtualenv ```pip install -r requirements.txt``` Joinmarket should be installed Create internal wallet using ```python wallet-tool.py generate``` It will generate seed words and will ask you for passphrase.. Which eventually will be saved to wallet.json Sending funds can be done by following following doc https://github.com/JoinMarket-Org/joinmarket/wiki/Sending-payments-with-CoinJoin Start Joinmarket ubuntu container ```docker start ubuntu``` In-case of further docker exploration or support https://docs.docker.com/ |
| json metadata | {"tags":["joinmarket","install","mac","bitcoin","anonymous"],"links":["https://docs.docker.com/docker-for-mac/install/","https://download.docker.com/mac/stable/Docker.dmg","https://github.com/JoinMarket-Org/joinmarket/wiki/Sending-payments-with-CoinJoin","https://docs.docker.com/"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #22712895/Trx 2b8d35ccaa7ceb17ce5f500fa5e8ba7eb2294c30 |
View Raw JSON Data
{
"trx_id": "2b8d35ccaa7ceb17ce5f500fa5e8ba7eb2294c30",
"block": 22712895,
"trx_in_block": 28,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-24T14:30:03",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "joinmarket",
"author": "sushrest",
"permlink": "how-to-install-joinmarket-on-mac",
"title": "How to install Joinmarket on Mac (Anonymous bitcoin transaction)",
"body": "Installing Joinmarket on Mac can be very tedious, specially for someone who is not tech savvy. A friend of mine asked me for a help to get Joinmarket installed on his Mac as he had a very hard time doing it, So I helped him out. I thought this could help others who are looking to do the same, So thought of doing a SteemIt post. So here are the following steps I took to get Joinmarket installed, total installation time could be around 30-40 mins depending on your internet speed.\n\n1. Install docker by following instruction on following link\nhttps://docs.docker.com/docker-for-mac/install/\nOr directly download and install https://download.docker.com/mac/stable/Docker.dmg\n1. Install ubuntu after installing docker using following command\n```docker run -i -t ubuntu /bin/bash```\n1. The above command should install ubuntu and boot it and log you into that OS.\n1. Now install joinmarket prerequisites using following command\n```apt-get update -y && apt-get upgrade -y && apt-get install python-dev libsodium-dev python-pip -y```\nSelect Y for Yes\n1. Install wget \n```apt-get install wget```\nSelect Y for Yes\n1. Install Joinmarket \n```wget https://github.com/JoinMarket-Org/joinmarket/archive/v0.2.3.tar.gz -O joinmarket-0.2.3.tar.gz```\n1. Extract with ```tar xzf joinmarket-0.2.3.tar.gz``` and then``` cd joinmarket-0.2.3```\n1. Activate virtualenv ```pip install -r requirements.txt```\n\nJoinmarket should be installed \nCreate internal wallet using \n```python wallet-tool.py generate```\nIt will generate seed words and will ask you for passphrase.. Which eventually will be saved to wallet.json\nSending funds can be done by following following doc\nhttps://github.com/JoinMarket-Org/joinmarket/wiki/Sending-payments-with-CoinJoin\n\nStart Joinmarket ubuntu container\n```docker start ubuntu```\n\nIn-case of further docker exploration or support \nhttps://docs.docker.com/",
"json_metadata": "{\"tags\":[\"joinmarket\",\"install\",\"mac\",\"bitcoin\",\"anonymous\"],\"links\":[\"https://docs.docker.com/docker-for-mac/install/\",\"https://download.docker.com/mac/stable/Docker.dmg\",\"https://github.com/JoinMarket-Org/joinmarket/wiki/Sending-payments-with-CoinJoin\",\"https://docs.docker.com/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}2018/05/23 09:52:00
2018/05/23 09:52:00
| parent author | hatu |
| parent permlink | re-sushrest-how-to-install-joinmarket-on-mac-20180523t074128685z |
| author | sushrest |
| permlink | re-hatu-re-sushrest-how-to-install-joinmarket-on-mac-20180523t095200011z |
| title | |
| body | Thank you. Just did it. :) |
| json metadata | {"tags":["joinmarket"],"app":"steemit/0.1"} |
| Transaction Info | Block #22678899/Trx d6940a2def57de84fb0a4e6ed3e3b4846bd2fa9c |
View Raw JSON Data
{
"trx_id": "d6940a2def57de84fb0a4e6ed3e3b4846bd2fa9c",
"block": 22678899,
"trx_in_block": 52,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-23T09:52:00",
"op": [
"comment",
{
"parent_author": "hatu",
"parent_permlink": "re-sushrest-how-to-install-joinmarket-on-mac-20180523t074128685z",
"author": "sushrest",
"permlink": "re-hatu-re-sushrest-how-to-install-joinmarket-on-mac-20180523t095200011z",
"title": "",
"body": "Thank you. Just did it. :)",
"json_metadata": "{\"tags\":[\"joinmarket\"],\"app\":\"steemit/0.1\"}"
}
]
}2018/05/23 09:51:12
2018/05/23 09:51:12
| required auths | [] |
| required posting auths | ["sushrest"] |
| id | follow |
| json | ["follow",{"follower":"sushrest","following":"hatu","what":["blog"]}] |
| Transaction Info | Block #22678883/Trx 92953139ee5d6b3da4b0270c6386377772af655b |
View Raw JSON Data
{
"trx_id": "92953139ee5d6b3da4b0270c6386377772af655b",
"block": 22678883,
"trx_in_block": 11,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-23T09:51:12",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"sushrest"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"sushrest\",\"following\":\"hatu\",\"what\":[\"blog\"]}]"
}
]
}sushrestupvoted (100.00%) @hatu / re-sushrest-how-to-install-joinmarket-on-mac-20180523t074128685z2018/05/23 09:51:03
sushrestupvoted (100.00%) @hatu / re-sushrest-how-to-install-joinmarket-on-mac-20180523t074128685z
2018/05/23 09:51:03
| voter | sushrest |
| author | hatu |
| permlink | re-sushrest-how-to-install-joinmarket-on-mac-20180523t074128685z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #22678880/Trx f8d017da9a4eaa71d9359ee9086b327d41862f17 |
View Raw JSON Data
{
"trx_id": "f8d017da9a4eaa71d9359ee9086b327d41862f17",
"block": 22678880,
"trx_in_block": 68,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-23T09:51:03",
"op": [
"vote",
{
"voter": "sushrest",
"author": "hatu",
"permlink": "re-sushrest-how-to-install-joinmarket-on-mac-20180523t074128685z",
"weight": 10000
}
]
}hatuupvoted (100.00%) @sushrest / how-to-install-joinmarket-on-mac2018/05/23 07:41:45
hatuupvoted (100.00%) @sushrest / how-to-install-joinmarket-on-mac
2018/05/23 07:41:45
| voter | hatu |
| author | sushrest |
| permlink | how-to-install-joinmarket-on-mac |
| weight | 10000 (100.00%) |
| Transaction Info | Block #22676299/Trx 8cde6da9fc62efb73e5e63e97a7b74cf40e63a93 |
View Raw JSON Data
{
"trx_id": "8cde6da9fc62efb73e5e63e97a7b74cf40e63a93",
"block": 22676299,
"trx_in_block": 23,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-23T07:41:45",
"op": [
"vote",
{
"voter": "hatu",
"author": "sushrest",
"permlink": "how-to-install-joinmarket-on-mac",
"weight": 10000
}
]
}2018/05/23 07:41:36
2018/05/23 07:41:36
| parent author | sushrest |
| parent permlink | how-to-install-joinmarket-on-mac |
| author | hatu |
| permlink | re-sushrest-how-to-install-joinmarket-on-mac-20180523t074128685z |
| title | |
| body | Hi, thank you for contributing to Steemit! I upvoted and followed you; follow back and we can help each other succeed :) P.S.: [My Recent Post](https://steemit.com/cryptocurrency/@hatu/springrole-huge-impact-on-developing-nations-fight-the-lottery-of-birth) |
| json metadata | {"tags":["joinmarket"],"links":["https://steemit.com/cryptocurrency/@hatu/springrole-huge-impact-on-developing-nations-fight-the-lottery-of-birth"],"app":"steemit/0.1"} |
| Transaction Info | Block #22676296/Trx 0ae88dc155eb3797add9e320f7d9f38c0895d4cc |
View Raw JSON Data
{
"trx_id": "0ae88dc155eb3797add9e320f7d9f38c0895d4cc",
"block": 22676296,
"trx_in_block": 49,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-23T07:41:36",
"op": [
"comment",
{
"parent_author": "sushrest",
"parent_permlink": "how-to-install-joinmarket-on-mac",
"author": "hatu",
"permlink": "re-sushrest-how-to-install-joinmarket-on-mac-20180523t074128685z",
"title": "",
"body": "Hi, thank you for contributing to Steemit! \n\nI upvoted and followed you; follow back and we can help each other succeed :) \n\nP.S.: [My Recent Post](https://steemit.com/cryptocurrency/@hatu/springrole-huge-impact-on-developing-nations-fight-the-lottery-of-birth)",
"json_metadata": "{\"tags\":[\"joinmarket\"],\"links\":[\"https://steemit.com/cryptocurrency/@hatu/springrole-huge-impact-on-developing-nations-fight-the-lottery-of-birth\"],\"app\":\"steemit/0.1\"}"
}
]
}swaggerupvoted (0.02%) @sushrest / how-to-install-joinmarket-on-mac2018/05/23 07:26:57
swaggerupvoted (0.02%) @sushrest / how-to-install-joinmarket-on-mac
2018/05/23 07:26:57
| voter | swagger |
| author | sushrest |
| permlink | how-to-install-joinmarket-on-mac |
| weight | 2 (0.02%) |
| Transaction Info | Block #22676004/Trx af843d19a771c2a6b4f6236f051c49fd272dd40e |
View Raw JSON Data
{
"trx_id": "af843d19a771c2a6b4f6236f051c49fd272dd40e",
"block": 22676004,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-23T07:26:57",
"op": [
"vote",
{
"voter": "swagger",
"author": "sushrest",
"permlink": "how-to-install-joinmarket-on-mac",
"weight": 2
}
]
}sushrestupdated their account properties2018/05/23 07:18:06
sushrestupdated their account properties
2018/05/23 07:18:06
| account | sushrest |
| memo key | STM7dJyhjRjyq1TrgcCSq5w5NPbmUk3B23gV9Rz5nxZ55YwFncTN6 |
| json metadata | {"profile":{"location":"Sydney","website":"https://www.sastoramro.com","profile_image":"https://steemitimages.com/DQmTWk7F2EtaphSjD7SZHU8P5b8EbYYgdr2zMVFxJ8i8eX5/myAvatar.png"}} |
| Transaction Info | Block #22675827/Trx bcbc4ba7286960bffa6ea48304f0e305d1938098 |
View Raw JSON Data
{
"trx_id": "bcbc4ba7286960bffa6ea48304f0e305d1938098",
"block": 22675827,
"trx_in_block": 43,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-23T07:18:06",
"op": [
"account_update",
{
"account": "sushrest",
"memo_key": "STM7dJyhjRjyq1TrgcCSq5w5NPbmUk3B23gV9Rz5nxZ55YwFncTN6",
"json_metadata": "{\"profile\":{\"location\":\"Sydney\",\"website\":\"https://www.sastoramro.com\",\"profile_image\":\"https://steemitimages.com/DQmTWk7F2EtaphSjD7SZHU8P5b8EbYYgdr2zMVFxJ8i8eX5/myAvatar.png\"}}"
}
]
}sushrestupdated their account properties2018/05/23 07:13:33
sushrestupdated their account properties
2018/05/23 07:13:33
| account | sushrest |
| memo key | STM7dJyhjRjyq1TrgcCSq5w5NPbmUk3B23gV9Rz5nxZ55YwFncTN6 |
| json metadata | {"profile":{"location":"Sydney","website":"https://www.sastoramro.com"}} |
| Transaction Info | Block #22675736/Trx 9be1eeaa5a8b0b7d4512115d2b0d0f740ef311fd |
View Raw JSON Data
{
"trx_id": "9be1eeaa5a8b0b7d4512115d2b0d0f740ef311fd",
"block": 22675736,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-23T07:13:33",
"op": [
"account_update",
{
"account": "sushrest",
"memo_key": "STM7dJyhjRjyq1TrgcCSq5w5NPbmUk3B23gV9Rz5nxZ55YwFncTN6",
"json_metadata": "{\"profile\":{\"location\":\"Sydney\",\"website\":\"https://www.sastoramro.com\"}}"
}
]
}sushrestpublished a new post: how-to-install-joinmarket-on-mac2018/05/23 07:09:18
sushrestpublished a new post: how-to-install-joinmarket-on-mac
2018/05/23 07:09:18
| parent author | |
| parent permlink | joinmarket |
| author | sushrest |
| permlink | how-to-install-joinmarket-on-mac |
| title | How to install Joinmarket on Mac |
| body | @@ -735,16 +735,19 @@ command%0A +%60%60%60 docker r @@ -771,16 +771,19 @@ bin/bash +%60%60%60 %0A1. The |
| json metadata | {"tags":["joinmarket","install","mac","macos","bitcoin"],"links":["https://docs.docker.com/docker-for-mac/install/","https://download.docker.com/mac/stable/Docker.dmg","https://github.com/JoinMarket-Org/joinmarket/wiki/Sending-payments-with-CoinJoin","https://docs.docker.com/"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #22675652/Trx 2fa7370e80ef0fcb555fcc334dad324faed941e8 |
View Raw JSON Data
{
"trx_id": "2fa7370e80ef0fcb555fcc334dad324faed941e8",
"block": 22675652,
"trx_in_block": 14,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-23T07:09:18",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "joinmarket",
"author": "sushrest",
"permlink": "how-to-install-joinmarket-on-mac",
"title": "How to install Joinmarket on Mac",
"body": "@@ -735,16 +735,19 @@\n command%0A\n+%60%60%60\n docker r\n@@ -771,16 +771,19 @@\n bin/bash\n+%60%60%60\n %0A1. The \n",
"json_metadata": "{\"tags\":[\"joinmarket\",\"install\",\"mac\",\"macos\",\"bitcoin\"],\"links\":[\"https://docs.docker.com/docker-for-mac/install/\",\"https://download.docker.com/mac/stable/Docker.dmg\",\"https://github.com/JoinMarket-Org/joinmarket/wiki/Sending-payments-with-CoinJoin\",\"https://docs.docker.com/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}sushrestupvoted (100.00%) @sushrest / how-to-install-joinmarket-on-mac2018/05/23 07:07:57
sushrestupvoted (100.00%) @sushrest / how-to-install-joinmarket-on-mac
2018/05/23 07:07:57
| voter | sushrest |
| author | sushrest |
| permlink | how-to-install-joinmarket-on-mac |
| weight | 10000 (100.00%) |
| Transaction Info | Block #22675625/Trx 2f03ee0b57362edcee5f52003e780630540e399c |
View Raw JSON Data
{
"trx_id": "2f03ee0b57362edcee5f52003e780630540e399c",
"block": 22675625,
"trx_in_block": 47,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-23T07:07:57",
"op": [
"vote",
{
"voter": "sushrest",
"author": "sushrest",
"permlink": "how-to-install-joinmarket-on-mac",
"weight": 10000
}
]
}ax3upvoted (1.00%) @sushrest / how-to-install-joinmarket-on-mac2018/05/23 07:06:54
ax3upvoted (1.00%) @sushrest / how-to-install-joinmarket-on-mac
2018/05/23 07:06:54
| voter | ax3 |
| author | sushrest |
| permlink | how-to-install-joinmarket-on-mac |
| weight | 100 (1.00%) |
| Transaction Info | Block #22675604/Trx 35e1e10f87b7be60bc18a05b92a7bcf6450fe8fa |
View Raw JSON Data
{
"trx_id": "35e1e10f87b7be60bc18a05b92a7bcf6450fe8fa",
"block": 22675604,
"trx_in_block": 10,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-23T07:06:54",
"op": [
"vote",
{
"voter": "ax3",
"author": "sushrest",
"permlink": "how-to-install-joinmarket-on-mac",
"weight": 100
}
]
}sushrestpublished a new post: how-to-install-joinmarket-on-mac2018/05/23 07:06:42
sushrestpublished a new post: how-to-install-joinmarket-on-mac
2018/05/23 07:06:42
| parent author | |
| parent permlink | joinmarket |
| author | sushrest |
| permlink | how-to-install-joinmarket-on-mac |
| title | How to install Joinmarket on Mac |
| body | Installing Joinmarket on Mac can be very tedious, specially for someone who is not tech savvy. A friend of mine asked me for a help to get Joinmarket installed on his Mac as he had a very hard time doing it, So I helped him out. I thought this could help others who are looking to do the same, So thought of doing a SteemIt post. So here are the following steps I took to get Joinmarket installed, total installation time could be around 30-40 mins depending on your internet speed. 1. Install docker by following instruction on following link https://docs.docker.com/docker-for-mac/install/ Or directly download and install https://download.docker.com/mac/stable/Docker.dmg 1. Install ubuntu after installing docker using following command docker run -i -t ubuntu /bin/bash 1. The above command should install ubuntu and boot it and log you into that OS. 1. Now install joinmarket prerequisites using following command ```apt-get update -y && apt-get upgrade -y && apt-get install python-dev libsodium-dev python-pip -y``` Select Y for Yes 1. Install wget ```apt-get install wget``` Select Y for Yes 1. Install Joinmarket ```wget https://github.com/JoinMarket-Org/joinmarket/archive/v0.2.3.tar.gz -O joinmarket-0.2.3.tar.gz``` 1. Extract with ```tar xzf joinmarket-0.2.3.tar.gz``` and then``` cd joinmarket-0.2.3``` 1. Activate virtualenv ```pip install -r requirements.txt``` Joinmarket should be installed Create internal wallet using ```python wallet-tool.py generate``` It will generate seed words and will ask you for passphrase.. Which eventually will be saved to wallet.json Sending funds can be done by following following doc https://github.com/JoinMarket-Org/joinmarket/wiki/Sending-payments-with-CoinJoin Start Joinmarket ubuntu container ```docker start ubuntu``` In-case of further docker exploration or support https://docs.docker.com/ |
| json metadata | {"tags":["joinmarket","install","mac","macos","bitcoin"],"links":["https://docs.docker.com/docker-for-mac/install/","https://download.docker.com/mac/stable/Docker.dmg","https://github.com/JoinMarket-Org/joinmarket/wiki/Sending-payments-with-CoinJoin","https://docs.docker.com/"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #22675600/Trx a567d35a13549fcdd45daf8a2b2ec9822b2b85cf |
View Raw JSON Data
{
"trx_id": "a567d35a13549fcdd45daf8a2b2ec9822b2b85cf",
"block": 22675600,
"trx_in_block": 23,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-23T07:06:42",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "joinmarket",
"author": "sushrest",
"permlink": "how-to-install-joinmarket-on-mac",
"title": "How to install Joinmarket on Mac",
"body": "Installing Joinmarket on Mac can be very tedious, specially for someone who is not tech savvy. A friend of mine asked me for a help to get Joinmarket installed on his Mac as he had a very hard time doing it, So I helped him out. I thought this could help others who are looking to do the same, So thought of doing a SteemIt post. So here are the following steps I took to get Joinmarket installed, total installation time could be around 30-40 mins depending on your internet speed.\n\n1. Install docker by following instruction on following link\nhttps://docs.docker.com/docker-for-mac/install/\nOr directly download and install https://download.docker.com/mac/stable/Docker.dmg\n1. Install ubuntu after installing docker using following command\ndocker run -i -t ubuntu /bin/bash\n1. The above command should install ubuntu and boot it and log you into that OS.\n1. Now install joinmarket prerequisites using following command\n```apt-get update -y && apt-get upgrade -y && apt-get install python-dev libsodium-dev python-pip -y```\nSelect Y for Yes\n1. Install wget \n```apt-get install wget```\nSelect Y for Yes\n1. Install Joinmarket \n```wget https://github.com/JoinMarket-Org/joinmarket/archive/v0.2.3.tar.gz -O joinmarket-0.2.3.tar.gz```\n1. Extract with ```tar xzf joinmarket-0.2.3.tar.gz``` and then``` cd joinmarket-0.2.3```\n1. Activate virtualenv ```pip install -r requirements.txt```\n\nJoinmarket should be installed \nCreate internal wallet using \n```python wallet-tool.py generate```\nIt will generate seed words and will ask you for passphrase.. Which eventually will be saved to wallet.json\nSending funds can be done by following following doc\nhttps://github.com/JoinMarket-Org/joinmarket/wiki/Sending-payments-with-CoinJoin\n\nStart Joinmarket ubuntu container\n```docker start ubuntu```\n\nIn-case of further docker exploration or support \nhttps://docs.docker.com/",
"json_metadata": "{\"tags\":[\"joinmarket\",\"install\",\"mac\",\"macos\",\"bitcoin\"],\"links\":[\"https://docs.docker.com/docker-for-mac/install/\",\"https://download.docker.com/mac/stable/Docker.dmg\",\"https://github.com/JoinMarket-Org/joinmarket/wiki/Sending-payments-with-CoinJoin\",\"https://docs.docker.com/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}sushrestfollowed @tradingroomapp2018/05/23 06:48:21
sushrestfollowed @tradingroomapp
2018/05/23 06:48:21
| required auths | [] |
| required posting auths | ["sushrest"] |
| id | follow |
| json | ["follow",{"follower":"sushrest","following":"tradingroomapp","what":["blog"]}] |
| Transaction Info | Block #22675233/Trx ba776e1f83da11bcf09c81ce39c6d059f666dd85 |
View Raw JSON Data
{
"trx_id": "ba776e1f83da11bcf09c81ce39c6d059f666dd85",
"block": 22675233,
"trx_in_block": 14,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-23T06:48:21",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"sushrest"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"sushrest\",\"following\":\"tradingroomapp\",\"what\":[\"blog\"]}]"
}
]
}2018/05/23 06:47:57
2018/05/23 06:47:57
| voter | sushrest |
| author | tradingroomapp |
| permlink | the-game-of-crypto-market-manipulations-who-are-the-players-and-how-they-play |
| weight | 10000 (100.00%) |
| Transaction Info | Block #22675225/Trx 550adf0e8050b42eca0298963e89e0ea6c13f8ee |
View Raw JSON Data
{
"trx_id": "550adf0e8050b42eca0298963e89e0ea6c13f8ee",
"block": 22675225,
"trx_in_block": 37,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-23T06:47:57",
"op": [
"vote",
{
"voter": "sushrest",
"author": "tradingroomapp",
"permlink": "the-game-of-crypto-market-manipulations-who-are-the-players-and-how-they-play",
"weight": 10000
}
]
}2018/05/18 21:02:09
2018/05/18 21:02:09
| delegator | steem |
| delegatee | sushrest |
| vesting shares | 29485.544587 VESTS |
| Transaction Info | Block #22548334/Trx 981237b56f582ddf56941c396c36d40d2b69c482 |
View Raw JSON Data
{
"trx_id": "981237b56f582ddf56941c396c36d40d2b69c482",
"block": 22548334,
"trx_in_block": 44,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-18T21:02:09",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sushrest",
"vesting_shares": "29485.544587 VESTS"
}
]
}sushrestupdated their account properties2018/03/24 11:47:39
sushrestupdated their account properties
2018/03/24 11:47:39
| account | sushrest |
| memo key | STM7dJyhjRjyq1TrgcCSq5w5NPbmUk3B23gV9Rz5nxZ55YwFncTN6 |
| json metadata | {"profile":{"profile_image":"https://scontent-syd2-1.xx.fbcdn.net/v/t1.0-9/1149077_717814278239391_22381795_n.jpg?_nc_cat=0&oh=d9d1a03b4b6503d2e1d6fa9780a7bff2&oe=5B3E336F","location":"Sydney","website":"https://www.sastoramro.com"}} |
| Transaction Info | Block #20954203/Trx 3bcb0c338ba3236be92d270336d7a8eaf2e14f02 |
View Raw JSON Data
{
"trx_id": "3bcb0c338ba3236be92d270336d7a8eaf2e14f02",
"block": 20954203,
"trx_in_block": 18,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-24T11:47:39",
"op": [
"account_update",
{
"account": "sushrest",
"memo_key": "STM7dJyhjRjyq1TrgcCSq5w5NPbmUk3B23gV9Rz5nxZ55YwFncTN6",
"json_metadata": "{\"profile\":{\"profile_image\":\"https://scontent-syd2-1.xx.fbcdn.net/v/t1.0-9/1149077_717814278239391_22381795_n.jpg?_nc_cat=0&oh=d9d1a03b4b6503d2e1d6fa9780a7bff2&oe=5B3E336F\",\"location\":\"Sydney\",\"website\":\"https://www.sastoramro.com\"}}"
}
]
}2018/03/16 13:15:36
2018/03/16 13:15:36
| voter | tomarazajcevak |
| author | sushrest |
| permlink | free-tls-ssl-certificate-from-let-s-encrypt-on-centos-6-5-7-and-nginx-in-6-simple-steps |
| weight | 10000 (100.00%) |
| Transaction Info | Block #20726419/Trx d0ff127faefd5f3fd7c15ad9c929680324c0a94b |
View Raw JSON Data
{
"trx_id": "d0ff127faefd5f3fd7c15ad9c929680324c0a94b",
"block": 20726419,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-16T13:15:36",
"op": [
"vote",
{
"voter": "tomarazajcevak",
"author": "sushrest",
"permlink": "free-tls-ssl-certificate-from-let-s-encrypt-on-centos-6-5-7-and-nginx-in-6-simple-steps",
"weight": 10000
}
]
}2018/03/16 02:49:42
2018/03/16 02:49:42
| parent author | |
| parent permlink | nginx |
| author | sushrest |
| permlink | free-tls-ssl-certificate-from-let-s-encrypt-on-centos-6-5-7-and-nginx-in-6-simple-steps |
| title | Free TLS/SSL certificate from Let’s Encrypt on Centos 6.5/7 and nginx in 6 simple steps |
| body | @@ -1266,24 +1266,29 @@ n name.%3Cbr%3E%0A +%3Cbr%3E%0A %3C/li%3E%0A %3Cli%3E @@ -1918,32 +1918,37 @@ 448%22/%3E%3Cbr%3E%0A%3Cbr%3E%0A +%3Cbr%3E%0A %3C/li%3E%0A %3Cli%3ENow @@ -8189,10 +8189,16 @@ oot -%3E%3E +>> /va |
| json metadata | {"tags":["nginx","free","ssl","tls","certificate"],"image":["https://assets.digitalocean.com/articles/AppArmor_Nginx/1.jpg"],"links":["http://www.sastoramro.com","www.sastoramro.com","https://github.com/letsencrypt/letsencrypt","http://do.co/le-nginx-renew"],"app":"steemit/0.1","format":"html"} |
| Transaction Info | Block #20713908/Trx a35e1aaedc94f50989a1d61f8d7c16ea444f544c |
View Raw JSON Data
{
"trx_id": "a35e1aaedc94f50989a1d61f8d7c16ea444f544c",
"block": 20713908,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-16T02:49:42",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "nginx",
"author": "sushrest",
"permlink": "free-tls-ssl-certificate-from-let-s-encrypt-on-centos-6-5-7-and-nginx-in-6-simple-steps",
"title": "Free TLS/SSL certificate from Let’s Encrypt on Centos 6.5/7 and nginx in 6 simple steps",
"body": "@@ -1266,24 +1266,29 @@\n n name.%3Cbr%3E%0A\n+%3Cbr%3E%0A\n %3C/li%3E%0A %3Cli%3E\n@@ -1918,32 +1918,37 @@\n 448%22/%3E%3Cbr%3E%0A%3Cbr%3E%0A\n+%3Cbr%3E%0A\n %3C/li%3E%0A %3Cli%3ENow \n@@ -8189,10 +8189,16 @@\n oot \n-%3E%3E\n+>>\n /va\n",
"json_metadata": "{\"tags\":[\"nginx\",\"free\",\"ssl\",\"tls\",\"certificate\"],\"image\":[\"https://assets.digitalocean.com/articles/AppArmor_Nginx/1.jpg\"],\"links\":[\"http://www.sastoramro.com\",\"www.sastoramro.com\",\"https://github.com/letsencrypt/letsencrypt\",\"http://do.co/le-nginx-renew\"],\"app\":\"steemit/0.1\",\"format\":\"html\"}"
}
]
}2018/03/16 02:48:24
2018/03/16 02:48:24
| parent author | |
| parent permlink | nginx |
| author | sushrest |
| permlink | free-tls-ssl-certificate-from-let-s-encrypt-on-centos-6-5-7-and-nginx-in-6-simple-steps |
| title | Free TLS/SSL certificate from Let’s Encrypt on Centos 6.5/7 and nginx in 6 simple steps |
| body | @@ -661,16 +661,52 @@ . +%3Ca href=%22http://www.sastoramro.com%22%3E www.your @@ -711,32 +711,36 @@ urdomainname.com +%3C/a%3E %3C/l @@ -1719,38 +1719,26 @@ ef=%22 -http://www.yourdomainname +www.sastoramro .com -/ %22%3Eht |
| json metadata | {"tags":["nginx","free","ssl","tls","certificate"],"image":["https://assets.digitalocean.com/articles/AppArmor_Nginx/1.jpg"],"links":["http://www.sastoramro.com","www.sastoramro.com","https://github.com/letsencrypt/letsencrypt","http://do.co/le-nginx-renew"],"app":"steemit/0.1","format":"html"} |
| Transaction Info | Block #20713882/Trx 2eeae93f0d090440a540493dd59f409efac5880b |
View Raw JSON Data
{
"trx_id": "2eeae93f0d090440a540493dd59f409efac5880b",
"block": 20713882,
"trx_in_block": 23,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-16T02:48:24",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "nginx",
"author": "sushrest",
"permlink": "free-tls-ssl-certificate-from-let-s-encrypt-on-centos-6-5-7-and-nginx-in-6-simple-steps",
"title": "Free TLS/SSL certificate from Let’s Encrypt on Centos 6.5/7 and nginx in 6 simple steps",
"body": "@@ -661,16 +661,52 @@\n . \n+%3Ca href=%22http://www.sastoramro.com%22%3E\n www.your\n@@ -711,32 +711,36 @@\n urdomainname.com\n+%3C/a%3E\n %3C/l\n@@ -1719,38 +1719,26 @@\n ef=%22\n-http://www.yourdomainname\n+www.sastoramro\n .com\n-/\n %22%3Eht\n",
"json_metadata": "{\"tags\":[\"nginx\",\"free\",\"ssl\",\"tls\",\"certificate\"],\"image\":[\"https://assets.digitalocean.com/articles/AppArmor_Nginx/1.jpg\"],\"links\":[\"http://www.sastoramro.com\",\"www.sastoramro.com\",\"https://github.com/letsencrypt/letsencrypt\",\"http://do.co/le-nginx-renew\"],\"app\":\"steemit/0.1\",\"format\":\"html\"}"
}
]
}2018/03/16 02:46:12
2018/03/16 02:46:12
| parent author | |
| parent permlink | nginx |
| author | sushrest |
| permlink | free-tls-ssl-certificate-from-let-s-encrypt-on-centos-6-5-7-and-nginx-in-6-simple-steps |
| title | Free TLS/SSL certificate from Let’s Encrypt on Centos 6.5/7 and nginx in 6 simple steps |
| body | @@ -1885,24 +1885,29 @@ 448%22/%3E%3Cbr%3E%0A%3C - +br%3E%0A%3C /li%3E%0A %3Cli%3EN @@ -2444,24 +2444,29 @@ %3C/code%3E%3Cbr%3E%0A +%3Cbr%3E%0A %3C/li%3E%0A %3Cli%3E @@ -2934,17 +2934,16 @@ fferent. - %3Cbr%3E%0AUsu @@ -2976,17 +2976,16 @@ uld work - %3Cbr%3E%0ANow @@ -3142,29 +3142,28 @@ sencrypt - +%3Cbr%3E%0A %3C/code%3E -%3Cbr%3E%0A Use the @@ -3229,33 +3229,32 @@ ollowing command - %3Cbr%3E%0A%3Ccode%3E./let @@ -3287,29 +3287,28 @@ andalone - +%3Cbr%3E%0A %3C/code%3E -%3Cbr%3E%0A At the f @@ -3379,25 +3379,24 @@ s as follows - %3Cbr%3E%0Ayourema @@ -3456,17 +3456,16 @@ name.com - %3Cbr%3E%0AIf @@ -3572,22 +3572,26 @@ months. - %3Cbr%3E%0A +%3Cbr%3E%0A %3C/li%3E%0A @@ -3653,17 +3653,16 @@ icate by - %3Cbr%3E%0A%3Cco @@ -3708,17 +3708,21 @@ /default - +%3Cbr%3E%0A %3C/code%3E%3C @@ -3721,29 +3721,24 @@ %3C/code%3E%3Cbr%3E%0A -%3Cbr%3E%0A Now change t @@ -3861,17 +3861,16 @@ _server; - %3Cbr%3E%0A# l @@ -3910,17 +3910,16 @@ only=on; - %3Cbr%3E%0Alis @@ -3930,17 +3930,21 @@ 443 ssl; - +%3Cbr%3E%0A %3C/code%3E%3C @@ -3939,37 +3939,32 @@ br%3E%0A%3C/code%3E%3Cbr%3E%0A -%3Cbr%3E%0A Now add your dom @@ -4315,17 +4315,16 @@ key.pem; - %3Cbr%3E%0Aroo @@ -4381,17 +4381,16 @@ dex.htm; - %3Cbr%3E%0Assl @@ -4530,17 +4530,21 @@ 56+EDH'; - +%3Cbr%3E%0A %3C/code%3E%3C @@ -4543,29 +4543,24 @@ %3C/code%3E%3Cbr%3E%0A -%3Cbr%3E%0A Now add a se @@ -4663,33 +4663,32 @@ nbsp; %3Cbr%3E%0A - &nbs @@ -4739,33 +4739,32 @@ nbsp; %3Cbr%3E%0A - &nbs @@ -4865,33 +4865,32 @@ nbsp; %3Cbr%3E%0A - &nbs @@ -4974,15 +4974,13 @@ bsp; -%09 %3Cbr%3E%0A - &nbs @@ -5149,17 +5149,16 @@ sp;%3Cbr%3E%0A - &n @@ -5192,24 +5192,27 @@ ; %7D - %3Cbr%3E%0A%7D - +%3Cbr%3E%0A %3C/code%3E%3C @@ -5215,21 +5215,16 @@ de%3E%3Cbr%3E%0A -%3Cbr%3E%0A Now Save @@ -5454,22 +5454,26 @@ in name. - %3Cbr%3E%0A +%3Cbr%3E%0A %3C/li%3E%0A @@ -5568,17 +5568,16 @@ process. - %3Cbr%3E%0AHer @@ -5593,17 +5593,16 @@ ou do it - %3Cbr%3E%0AAdd @@ -5681,17 +5681,16 @@ guration - %3Cbr%3E%0A%3Cco @@ -5729,17 +5729,16 @@ sp;%3Cbr%3E%0A - allow al @@ -5743,16 +5743,19 @@ all; - %3Cbr%3E%0A%7D - +%3Cbr%3E%0A %3C/co @@ -5762,21 +5762,16 @@ de%3E%3Cbr%3E%0A -%3Cbr%3E%0A Next we @@ -5923,17 +5923,16 @@ root.ini - %3Cbr%3E%0A%3Cco @@ -6011,29 +6011,28 @@ root.ini - +%3Cbr%3E%0A %3C/code%3E -%3Cbr%3E%0A Now edit @@ -6141,29 +6141,28 @@ root.ini - +%3Cbr%3E%0A %3C/code%3E -%3Cbr%3E%0A Uncommen @@ -6236,17 +6236,16 @@ ;such as - %3Cbr%3E%0A%3Cco @@ -6277,29 +6277,28 @@ mail.com - +%3Cbr%3E%0A %3C/code%3E -%3Cbr%3E%0A Uncommen @@ -6367,17 +6367,16 @@ e order) - %3Cbr%3E%0A%3Cco @@ -6430,29 +6430,28 @@ name.com - +%3Cbr%3E%0A %3C/code%3E -%3Cbr%3E%0A Then unc @@ -6563,17 +6563,16 @@ follows - %3Cbr%3E%0A%3Cco @@ -6610,29 +6610,28 @@ inx/html - +%3Cbr%3E%0A %3C/code%3E -%3Cbr%3E%0A Now cd i @@ -6717,17 +6717,16 @@ command - %3Cbr%3E%0A%3Cco @@ -6854,29 +6854,28 @@ root.ini - +%3Cbr%3E%0A %3C/code%3E -%3Cbr%3E%0A Assuming @@ -7223,17 +7223,16 @@ ry week. - %3Cbr%3E%0ANow @@ -7446,29 +7446,28 @@ a%3E%3Ccode%3E - +%3Cbr%3E%0A %3C/code%3E -%3Cbr%3E%0A Make it @@ -7476,17 +7476,16 @@ ecutable - %3Cbr%3E%0A%3Cco @@ -7533,29 +7533,28 @@ -webroot - +%3Cbr%3E%0A %3C/code%3E -%3Cbr%3E%0A The le-r @@ -8092,17 +8092,16 @@ ewal.log - %3Cbr%3E%0A%3Cco @@ -8179,17 +8179,21 @@ ewal.log - +%3Cbr%3E%0A %3C/code%3E%3C @@ -8196,21 +8196,16 @@ de%3E%3Cbr%3E%0A -%3Cbr%3E%0A Save and @@ -8224,17 +8224,42 @@ on file. - + %3C/li%3E%0A%3C/ol%3E%0A%3Cp%3E%3Cbr%3E%0A Now your @@ -8362,24 +8362,17 @@ %3C/ -li%3E%0A%3C/ol +p %3E%0A%3C/html |
| json metadata | {"tags":["nginx","free","ssl","tls","certificate"],"image":["https://assets.digitalocean.com/articles/AppArmor_Nginx/1.jpg"],"links":["http://www.yourdomainname.com/","https://github.com/letsencrypt/letsencrypt","http://do.co/le-nginx-renew"],"app":"steemit/0.1","format":"html"} |
| Transaction Info | Block #20713838/Trx 9c9ea6645d927c7947941a78474613acfd963324 |
View Raw JSON Data
{
"trx_id": "9c9ea6645d927c7947941a78474613acfd963324",
"block": 20713838,
"trx_in_block": 38,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-16T02:46:12",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "nginx",
"author": "sushrest",
"permlink": "free-tls-ssl-certificate-from-let-s-encrypt-on-centos-6-5-7-and-nginx-in-6-simple-steps",
"title": "Free TLS/SSL certificate from Let’s Encrypt on Centos 6.5/7 and nginx in 6 simple steps",
"body": "@@ -1885,24 +1885,29 @@\n 448%22/%3E%3Cbr%3E%0A%3C\n-\n \n+br%3E%0A%3C\n /li%3E%0A %3Cli%3EN\n@@ -2444,24 +2444,29 @@\n %3C/code%3E%3Cbr%3E%0A\n+%3Cbr%3E%0A\n %3C/li%3E%0A %3Cli%3E\n@@ -2934,17 +2934,16 @@\n fferent.\n- \n %3Cbr%3E%0AUsu\n@@ -2976,17 +2976,16 @@\n uld work\n- \n %3Cbr%3E%0ANow\n@@ -3142,29 +3142,28 @@\n sencrypt\n- \n+%3Cbr%3E%0A\n %3C/code%3E\n-%3Cbr%3E%0A\n Use the \n@@ -3229,33 +3229,32 @@\n ollowing command\n- \n %3Cbr%3E%0A%3Ccode%3E./let\n@@ -3287,29 +3287,28 @@\n andalone\n- \n+%3Cbr%3E%0A\n %3C/code%3E\n-%3Cbr%3E%0A\n At the f\n@@ -3379,25 +3379,24 @@\n s as follows\n- \n %3Cbr%3E%0Ayourema\n@@ -3456,17 +3456,16 @@\n name.com\n- \n %3Cbr%3E%0AIf \n@@ -3572,22 +3572,26 @@\n months.\n- \n %3Cbr%3E%0A\n+%3Cbr%3E%0A\n %3C/li%3E%0A \n@@ -3653,17 +3653,16 @@\n icate by\n- \n %3Cbr%3E%0A%3Cco\n@@ -3708,17 +3708,21 @@\n /default\n- \n+%3Cbr%3E%0A\n %3C/code%3E%3C\n@@ -3721,29 +3721,24 @@\n %3C/code%3E%3Cbr%3E%0A\n-%3Cbr%3E%0A\n Now change t\n@@ -3861,17 +3861,16 @@\n _server;\n- \n %3Cbr%3E%0A# l\n@@ -3910,17 +3910,16 @@\n only=on;\n- \n %3Cbr%3E%0Alis\n@@ -3930,17 +3930,21 @@\n 443 ssl;\n- \n+%3Cbr%3E%0A\n %3C/code%3E%3C\n@@ -3939,37 +3939,32 @@\n br%3E%0A%3C/code%3E%3Cbr%3E%0A\n-%3Cbr%3E%0A\n Now add your dom\n@@ -4315,17 +4315,16 @@\n key.pem;\n- \n %3Cbr%3E%0Aroo\n@@ -4381,17 +4381,16 @@\n dex.htm;\n- \n %3Cbr%3E%0Assl\n@@ -4530,17 +4530,21 @@\n 56+EDH';\n- \n+%3Cbr%3E%0A\n %3C/code%3E%3C\n@@ -4543,29 +4543,24 @@\n %3C/code%3E%3Cbr%3E%0A\n-%3Cbr%3E%0A\n Now add a se\n@@ -4663,33 +4663,32 @@\n nbsp; %3Cbr%3E%0A\n- \n &nbs\n@@ -4739,33 +4739,32 @@\n nbsp; %3Cbr%3E%0A\n- \n &nbs\n@@ -4865,33 +4865,32 @@\n nbsp; %3Cbr%3E%0A\n- \n &nbs\n@@ -4974,15 +4974,13 @@\n bsp;\n-%09\n %3Cbr%3E%0A\n- \n &nbs\n@@ -5149,17 +5149,16 @@\n sp;%3Cbr%3E%0A\n- \n &n\n@@ -5192,24 +5192,27 @@\n ; %7D\n- \n %3Cbr%3E%0A%7D\n- \n+%3Cbr%3E%0A\n %3C/code%3E%3C\n@@ -5215,21 +5215,16 @@\n de%3E%3Cbr%3E%0A\n-%3Cbr%3E%0A\n Now Save\n@@ -5454,22 +5454,26 @@\n in name.\n- \n %3Cbr%3E%0A\n+%3Cbr%3E%0A\n %3C/li%3E%0A \n@@ -5568,17 +5568,16 @@\n process.\n- \n %3Cbr%3E%0AHer\n@@ -5593,17 +5593,16 @@\n ou do it\n- \n %3Cbr%3E%0AAdd\n@@ -5681,17 +5681,16 @@\n guration\n- \n %3Cbr%3E%0A%3Cco\n@@ -5729,17 +5729,16 @@\n sp;%3Cbr%3E%0A\n- \n allow al\n@@ -5743,16 +5743,19 @@\n all;\n- \n %3Cbr%3E%0A%7D\n- \n+%3Cbr%3E%0A\n %3C/co\n@@ -5762,21 +5762,16 @@\n de%3E%3Cbr%3E%0A\n-%3Cbr%3E%0A\n Next we \n@@ -5923,17 +5923,16 @@\n root.ini\n- \n %3Cbr%3E%0A%3Cco\n@@ -6011,29 +6011,28 @@\n root.ini\n- \n+%3Cbr%3E%0A\n %3C/code%3E\n-%3Cbr%3E%0A\n Now edit\n@@ -6141,29 +6141,28 @@\n root.ini\n- \n+%3Cbr%3E%0A\n %3C/code%3E\n-%3Cbr%3E%0A\n Uncommen\n@@ -6236,17 +6236,16 @@\n ;such as\n- \n %3Cbr%3E%0A%3Cco\n@@ -6277,29 +6277,28 @@\n mail.com\n- \n+%3Cbr%3E%0A\n %3C/code%3E\n-%3Cbr%3E%0A\n Uncommen\n@@ -6367,17 +6367,16 @@\n e order)\n- \n %3Cbr%3E%0A%3Cco\n@@ -6430,29 +6430,28 @@\n name.com\n- \n+%3Cbr%3E%0A\n %3C/code%3E\n-%3Cbr%3E%0A\n Then unc\n@@ -6563,17 +6563,16 @@\n follows\n- \n %3Cbr%3E%0A%3Cco\n@@ -6610,29 +6610,28 @@\n inx/html\n- \n+%3Cbr%3E%0A\n %3C/code%3E\n-%3Cbr%3E%0A\n Now cd i\n@@ -6717,17 +6717,16 @@\n command\n- \n %3Cbr%3E%0A%3Cco\n@@ -6854,29 +6854,28 @@\n root.ini\n- \n+%3Cbr%3E%0A\n %3C/code%3E\n-%3Cbr%3E%0A\n Assuming\n@@ -7223,17 +7223,16 @@\n ry week.\n- \n %3Cbr%3E%0ANow\n@@ -7446,29 +7446,28 @@\n a%3E%3Ccode%3E\n- \n+%3Cbr%3E%0A\n %3C/code%3E\n-%3Cbr%3E%0A\n Make it \n@@ -7476,17 +7476,16 @@\n ecutable\n- \n %3Cbr%3E%0A%3Cco\n@@ -7533,29 +7533,28 @@\n -webroot\n- \n+%3Cbr%3E%0A\n %3C/code%3E\n-%3Cbr%3E%0A\n The le-r\n@@ -8092,17 +8092,16 @@\n ewal.log\n- \n %3Cbr%3E%0A%3Cco\n@@ -8179,17 +8179,21 @@\n ewal.log\n- \n+%3Cbr%3E%0A\n %3C/code%3E%3C\n@@ -8196,21 +8196,16 @@\n de%3E%3Cbr%3E%0A\n-%3Cbr%3E%0A\n Save and\n@@ -8224,17 +8224,42 @@\n on file.\n- \n+ %3C/li%3E%0A%3C/ol%3E%0A%3Cp%3E%3Cbr%3E%0A\n Now your\n@@ -8362,24 +8362,17 @@\n %3C/\n-li%3E%0A%3C/ol\n+p\n %3E%0A%3C/html\n",
"json_metadata": "{\"tags\":[\"nginx\",\"free\",\"ssl\",\"tls\",\"certificate\"],\"image\":[\"https://assets.digitalocean.com/articles/AppArmor_Nginx/1.jpg\"],\"links\":[\"http://www.yourdomainname.com/\",\"https://github.com/letsencrypt/letsencrypt\",\"http://do.co/le-nginx-renew\"],\"app\":\"steemit/0.1\",\"format\":\"html\"}"
}
]
}2018/03/16 02:42:42
2018/03/16 02:42:42
| voter | sushrest |
| author | sushrest |
| permlink | free-tls-ssl-certificate-from-let-s-encrypt-on-centos-6-5-7-and-nginx-in-6-simple-steps |
| weight | 10000 (100.00%) |
| Transaction Info | Block #20713768/Trx 3e0c076c3fe914e00599bb0c26f2760d06dd0474 |
View Raw JSON Data
{
"trx_id": "3e0c076c3fe914e00599bb0c26f2760d06dd0474",
"block": 20713768,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-16T02:42:42",
"op": [
"vote",
{
"voter": "sushrest",
"author": "sushrest",
"permlink": "free-tls-ssl-certificate-from-let-s-encrypt-on-centos-6-5-7-and-nginx-in-6-simple-steps",
"weight": 10000
}
]
}2018/03/16 02:42:42
2018/03/16 02:42:42
| parent author | |
| parent permlink | nginx |
| author | sushrest |
| permlink | free-tls-ssl-certificate-from-let-s-encrypt-on-centos-6-5-7-and-nginx-in-6-simple-steps |
| title | Free TLS/SSL certificate from Let’s Encrypt on Centos 6.5/7 and nginx in 6 simple steps |
| body | <html> <p>Lets Encrypt is a free, automated and open Certificate Authority, an initiative supported by online big companies such as facebook, cisco etc to make web more safe.</p> <p>I will be guiding you to setup Let’s Encrypt on Centos6.5/7 and nginx webserver. The following steps can be modified as according to your environment needs like other linux distros such as ubuntu etc. Setting this up on ubuntu shouldn’t differ much.</p> <p>Here’s what you need to get started </p> <ul> <li>Centos 6.5/7 server where you have SSH access or shell access. (You must have SSH access to be able to use Let’s Encrypt)</li> <li>A registered domain name. www.yourdomainname.com </li> </ul> <p>Steps:</p> <ol> <li>Point domain name to your server <br> You can point your domain name (both version along with www) to your server by configuring the proper A record provided by your web hosting, usually you do this by logging into your domain name account accessing DNS settings where you can enter the DNS settings, these process should be more or less same for various domain name providers. Let’s Encrypt will only issue certificate to a server which is accessible via domain name.<br> </li> <li>Now access your Centos6.5/7 via SSH and install nginx webserver using following commands <br> <code>sudo yum install epel-release <br> sudo yum install nginx </code> <br> Now start nginx <br> <code>sudo systemctl start nginx</code> <br> Now you should be able to go to <a href="http://www.yourdomainname.com/">http://www.yourdomainname.com</a> and you should see something like this<br> <img src="https://assets.digitalocean.com/articles/AppArmor_Nginx/1.jpg" width="596" height="448"/><br> </li> <li>Now Install Let’s Encrypt Client application using git <br> <code>Install git <br> sudo yum install git </code> <br> Clone and Install Let’s Encrypt from official github repository to your server at /opt/letsencrypt by <br> <code>sudo git clone </code><a href="https://github.com/letsencrypt/letsencrypt"><code>https://github.com/letsencrypt/letsencrypt</code></a><code> /opt/letsencrypt </code><br> </li> <li>Request SSL Certificate for yourdomainname.com <br> While running Let’s Encrypt SSL Certificate request script it listens on port 80 for Let’s Encrypt to verify that the domain name belongs to your server, so we need to close any programs that is currently running on port 80. So we need to shutdown our nginx server for now, if your are running on different version of Centos the commands to restart, stop, start nginx could be different. <br> Usually following command should work <br> Now to stop nginx <br> <code>sudo systemctl stop nginx</code> <br> Now Request SSL Certificate <br> <code>cd /opt/letsencrypt </code><br> Use the standalone plugin to request for certificate by executing following command <br> <code>./letsencrypt-auto certonly –standalone </code><br> At the first prompt add your email address and second prompt domain names as follows <br> [email protected] and yourdomainname.com www.yourdomainname.com <br> If everything goes well the script will output a message with your certificate expiry date usually in 3 months. <br> </li> <li>Now configure nginx to use the Let’s Encrypt Certificate by <br> <code>sudo nano /etc/nginx/sites-available/default </code><br> <br> Now change the server block and comment out 2 lines with listen 80 and add listen 443 ssl; for eg:<br> <code># listen 80 default_server; <br> # listen [::]:80 default_server ipv6only=on; <br> listen 443 ssl; </code><br> <br> Now add your domain names and ssl certificate like this <br> <code>server_name yourdomainname.com www.yourdomainname.com; <br> ssl on; <br> ssl_certificate /etc/letsencrypt/live/yourdomainname.com/fullchain.pem; <br> ssl_certificate_key /etc/letsencrypt/live/yourdomainname.com/privkey.pem; <br> root /usr/share/nginx/html; index index.html index.htm; <br> ssl_protocols TLSv1 TLSv1.1 TLSv1.2; <br> ssl_prefer_server_ciphers on; <br> ssl_ciphers 'EECDH+AESGCM:EDH+AES256+EECDH:AES256+EDH'; </code><br> <br> Now add a server block to redirect port 80 traffic to port 443 <br> <code>server { <br> listen 80; <br> server_name yourdomainname.com www.yourdomainname.com; <br> location / { <br> return 301 https://www.yourdomainname.com$request_uri; <br> } <br> } </code><br> <br> Now Save and exit the file and start nginx to put the changes into effect by <br> <code>sudo systemctl start nginx </code> <br> At this point your SSL certificate should be in place and you can test by visiting your domain name. <br> </li> <li>Since Let’s Encrypt Certificate are valid for 90 days you can automate that renewal process. <br> Here’s how you do it <br> Add the following location block under ssl server block on your nginx configuration <br> <code>location ~ /.well-known { <br> allow all; <br> } </code><br> <br> Next we need to setup Let’s Encrypt configuration file for automation of SSL Certificate request. Copy cli.ini to /usr/local/etc/le-renew-webroot.ini <br> <code>sudo cp /opt/letsencrypt/examples/cli.ini /usr/local/etc/le-renew-webroot.ini </code><br> Now edit the configuration file to fit your needs <br> <code>sudo nano /usr/local/etc/le-renew-webroot.ini </code><br> Uncomment line with email and add your email which you entered before such as <br> <code>email = [email protected] </code><br> Uncomment line with domains and add domains as follows (maintaining the order) <br> <code>domains = yourdomainname.com, www.yourdomainname.com </code><br> Then uncomment the webroot path and make sure it matches the webroot path specified in you nginx configuration as follows <br> <code>webroot-path = /usr/share/nginx/html </code><br> Now cd into cd /opt/letsencrypt and test the renewal request script using the following command <br> <code>cd /opt/letsencrypt<br> ./letsencrypt-auto certonly -a webroot --renew-by-default --config /usr/local/etc/le-renew-webroot.ini </code><br> Assuming the configuration are correct the script should output Congratulation message with expiry date of the certificate. If the expiry date is less than 30 days the renewal request will be sent. <br> Now to automate the autorenewal process we will be using a shell script and use a cronjob that will schedule this script to be run every week. <br> Now download the script by using following command <br> <code>sudo curl -L -o /usr/local/sbin/le-renew-webroot </code><a href="http://do.co/le-nginx-renew"><code>http://do.co/le-nginx-renew</code></a><code> </code><br> Make it executable <br> <code>sudo chmod +x /usr/local/sbin/le-renew-webroot </code><br> The le-renew-webroot script takes an argument the domain name whose certificate you want to check for renewal. If the renewal isn’t necessary it will simply output the remaining days to expire with the domain name. <br> Now run a cronjob to execute this script to check for certificate renewal every week by running following command <br> <code>sudo nano -c /etc/crontab </code> <br> Then add this line to execute the script every monday at 1:30 am, the output of the log will be saved on /var/log/le-renewal.log <br> <code>30 1 * * 1 /usr/local/sbin/le-renew-webroot >> /var/log/le-renewal.log </code><br> <br> Save and exit the cron file. Now your domain is using a Free SSL/TLS Certificate from Let’s Encrypt with auto renewal every 3 months. </li> </ol> </html> |
| json metadata | {"tags":["nginx","free","ssl","tls","certificate"],"image":["https://assets.digitalocean.com/articles/AppArmor_Nginx/1.jpg"],"links":["http://www.yourdomainname.com/","https://github.com/letsencrypt/letsencrypt","http://do.co/le-nginx-renew"],"app":"steemit/0.1","format":"html"} |
| Transaction Info | Block #20713768/Trx 3e0c076c3fe914e00599bb0c26f2760d06dd0474 |
View Raw JSON Data
{
"trx_id": "3e0c076c3fe914e00599bb0c26f2760d06dd0474",
"block": 20713768,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-16T02:42:42",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "nginx",
"author": "sushrest",
"permlink": "free-tls-ssl-certificate-from-let-s-encrypt-on-centos-6-5-7-and-nginx-in-6-simple-steps",
"title": "Free TLS/SSL certificate from Let’s Encrypt on Centos 6.5/7 and nginx in 6 simple steps",
"body": "<html>\n<p>Lets Encrypt is a free, automated and open Certificate Authority, an initiative supported by online big companies such as facebook, cisco etc to make web more safe.</p>\n<p>I will be guiding you to setup Let’s Encrypt on Centos6.5/7 and nginx webserver. The following steps can be modified as according to your environment needs like other linux distros such as ubuntu etc. Setting this up on ubuntu shouldn’t differ much.</p>\n<p>Here’s what you need to get started </p>\n<ul>\n <li>Centos 6.5/7 server where you have SSH access or shell access. (You must have SSH access to be able to use Let’s Encrypt)</li>\n <li>A registered domain name. www.yourdomainname.com </li>\n</ul>\n<p>Steps:</p>\n<ol>\n <li>Point domain name to your server <br>\nYou can point your domain name (both version along with www) to your server by configuring the proper A record provided by your web hosting, usually you do this by logging into your domain name account accessing DNS settings where you can enter the DNS settings, these process should be more or less same for various domain name providers. Let’s Encrypt will only issue certificate to a server which is accessible via domain name.<br>\n</li>\n <li>Now access your Centos6.5/7 via SSH and install nginx webserver using following commands <br>\n<code>sudo yum install epel-release <br>\nsudo yum install nginx </code> <br>\nNow start nginx <br>\n<code>sudo systemctl start nginx</code> <br>\nNow you should be able to go to <a href=\"http://www.yourdomainname.com/\">http://www.yourdomainname.com</a> and you should see something like this<br>\n<img src=\"https://assets.digitalocean.com/articles/AppArmor_Nginx/1.jpg\" width=\"596\" height=\"448\"/><br>\n</li>\n <li>Now Install Let’s Encrypt Client application using git <br>\n<code>Install git <br>\nsudo yum install git </code> <br>\nClone and Install Let’s Encrypt from official github repository to your server at /opt/letsencrypt by <br>\n<code>sudo git clone </code><a href=\"https://github.com/letsencrypt/letsencrypt\"><code>https://github.com/letsencrypt/letsencrypt</code></a><code> /opt/letsencrypt </code><br>\n</li>\n <li>Request SSL Certificate for yourdomainname.com <br>\nWhile running Let’s Encrypt SSL Certificate request script it listens on port 80 for Let’s Encrypt to verify that the domain name belongs to your server, so we need to close any programs that is currently running on port 80. So we need to shutdown our nginx server for now, if your are running on different version of Centos the commands to restart, stop, start nginx could be different. <br>\nUsually following command should work <br>\nNow to stop nginx <br>\n<code>sudo systemctl stop nginx</code> <br>\nNow Request SSL Certificate <br>\n<code>cd /opt/letsencrypt </code><br>\nUse the standalone plugin to request for certificate by executing following command <br>\n<code>./letsencrypt-auto certonly –standalone </code><br>\nAt the first prompt add your email address and second prompt domain names as follows <br>\[email protected] and yourdomainname.com www.yourdomainname.com <br>\nIf everything goes well the script will output a message with your certificate expiry date usually in 3 months. <br>\n</li>\n <li>Now configure nginx to use the Let’s Encrypt Certificate by <br>\n<code>sudo nano /etc/nginx/sites-available/default </code><br>\n<br>\nNow change the server block and comment out 2 lines with listen 80 and add listen 443 ssl; for eg:<br>\n<code># listen 80 default_server; <br>\n# listen [::]:80 default_server ipv6only=on; <br>\nlisten 443 ssl; </code><br>\n<br>\nNow add your domain names and ssl certificate like this <br>\n<code>server_name yourdomainname.com www.yourdomainname.com; <br>\nssl on; <br>\nssl_certificate /etc/letsencrypt/live/yourdomainname.com/fullchain.pem; <br>\nssl_certificate_key /etc/letsencrypt/live/yourdomainname.com/privkey.pem; <br>\nroot /usr/share/nginx/html; index index.html index.htm; <br>\nssl_protocols TLSv1 TLSv1.1 TLSv1.2; <br>\nssl_prefer_server_ciphers on; <br>\nssl_ciphers 'EECDH+AESGCM:EDH+AES256+EECDH:AES256+EDH'; </code><br>\n<br>\nNow add a server block to redirect port 80 traffic to port 443 <br>\n<code>server { <br>\n listen 80; <br>\n server_name yourdomainname.com www.yourdomainname.com; <br>\n location / { \t<br>\n return 301 https://www.yourdomainname.com$request_uri; <br>\n } <br>\n} </code><br>\n<br>\nNow Save and exit the file and start nginx to put the changes into effect by <br>\n<code>sudo systemctl start nginx </code> <br>\nAt this point your SSL certificate should be in place and you can test by visiting your domain name. <br>\n</li>\n <li>Since Let’s Encrypt Certificate are valid for 90 days you can automate that renewal process. <br>\nHere’s how you do it <br>\nAdd the following location block under ssl server block on your nginx configuration <br>\n<code>location ~ /.well-known { <br>\n allow all; <br>\n} </code><br>\n<br>\nNext we need to setup Let’s Encrypt configuration file for automation of SSL Certificate request. Copy cli.ini to /usr/local/etc/le-renew-webroot.ini <br>\n<code>sudo cp /opt/letsencrypt/examples/cli.ini /usr/local/etc/le-renew-webroot.ini </code><br>\nNow edit the configuration file to fit your needs <br>\n<code>sudo nano /usr/local/etc/le-renew-webroot.ini </code><br>\nUncomment line with email and add your email which you entered before such as <br>\n<code>email = [email protected] </code><br>\nUncomment line with domains and add domains as follows (maintaining the order) <br>\n<code>domains = yourdomainname.com, www.yourdomainname.com </code><br>\nThen uncomment the webroot path and make sure it matches the webroot path specified in you nginx configuration as follows <br>\n<code>webroot-path = /usr/share/nginx/html </code><br>\nNow cd into cd /opt/letsencrypt and test the renewal request script using the following command <br>\n<code>cd /opt/letsencrypt<br>\n./letsencrypt-auto certonly -a webroot --renew-by-default --config /usr/local/etc/le-renew-webroot.ini </code><br>\nAssuming the configuration are correct the script should output Congratulation message with expiry date of the certificate. If the expiry date is less than 30 days the renewal request will be sent. <br>\nNow to automate the autorenewal process we will be using a shell script and use a cronjob that will schedule this script to be run every week. <br>\nNow download the script by using following command <br>\n<code>sudo curl -L -o /usr/local/sbin/le-renew-webroot </code><a href=\"http://do.co/le-nginx-renew\"><code>http://do.co/le-nginx-renew</code></a><code> </code><br>\nMake it executable <br>\n<code>sudo chmod +x /usr/local/sbin/le-renew-webroot </code><br>\nThe le-renew-webroot script takes an argument the domain name whose certificate you want to check for renewal. If the renewal isn’t necessary it will simply output the remaining days to expire with the domain name. <br>\nNow run a cronjob to execute this script to check for certificate renewal every week by running following command <br>\n<code>sudo nano -c /etc/crontab </code> <br>\nThen add this line to execute the script every monday at 1:30 am, the output of the log will be saved on /var/log/le-renewal.log <br>\n<code>30 1 * * 1 /usr/local/sbin/le-renew-webroot >> /var/log/le-renewal.log </code><br>\n<br>\nSave and exit the cron file. Now your domain is using a Free SSL/TLS Certificate from Let’s Encrypt with auto renewal every 3 months. </li>\n</ol>\n</html>",
"json_metadata": "{\"tags\":[\"nginx\",\"free\",\"ssl\",\"tls\",\"certificate\"],\"image\":[\"https://assets.digitalocean.com/articles/AppArmor_Nginx/1.jpg\"],\"links\":[\"http://www.yourdomainname.com/\",\"https://github.com/letsencrypt/letsencrypt\",\"http://do.co/le-nginx-renew\"],\"app\":\"steemit/0.1\",\"format\":\"html\"}"
}
]
}2018/03/16 00:23:30
2018/03/16 00:23:30
| voter | sushrest |
| author | sushrest |
| permlink | re-jeramyroberts-ethereum-amd-gpu-mining-tutorial-ubuntu-16-04-lts-20180120t002045137z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #20710986/Trx b9c04fceaa14e9a623e75a102b2a479b4234fbb2 |
View Raw JSON Data
{
"trx_id": "b9c04fceaa14e9a623e75a102b2a479b4234fbb2",
"block": 20710986,
"trx_in_block": 11,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-16T00:23:30",
"op": [
"vote",
{
"voter": "sushrest",
"author": "sushrest",
"permlink": "re-jeramyroberts-ethereum-amd-gpu-mining-tutorial-ubuntu-16-04-lts-20180120t002045137z",
"weight": 10000
}
]
}sushrestupdated their account properties2018/03/16 00:10:15
sushrestupdated their account properties
2018/03/16 00:10:15
| account | sushrest |
| memo key | STM7dJyhjRjyq1TrgcCSq5w5NPbmUk3B23gV9Rz5nxZ55YwFncTN6 |
| json metadata | {"profile":{"profile_image":"https://lh3.googleusercontent.com/PUDshGPYiJBgyjLpSu_GQXtBxY1guVjAUEnsYRacaRN2EFLz7YajOnPgfyOujZAx12kBuosP0prI0w=s250-rw-no","location":"Sydney","website":"https://www.sastoramro.com"}} |
| Transaction Info | Block #20710721/Trx 6f4e778f337fbb61e83631a93d5c4fedfea85f09 |
View Raw JSON Data
{
"trx_id": "6f4e778f337fbb61e83631a93d5c4fedfea85f09",
"block": 20710721,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-16T00:10:15",
"op": [
"account_update",
{
"account": "sushrest",
"memo_key": "STM7dJyhjRjyq1TrgcCSq5w5NPbmUk3B23gV9Rz5nxZ55YwFncTN6",
"json_metadata": "{\"profile\":{\"profile_image\":\"https://lh3.googleusercontent.com/PUDshGPYiJBgyjLpSu_GQXtBxY1guVjAUEnsYRacaRN2EFLz7YajOnPgfyOujZAx12kBuosP0prI0w=s250-rw-no\",\"location\":\"Sydney\",\"website\":\"https://www.sastoramro.com\"}}"
}
]
}2018/03/13 22:53:09
2018/03/13 22:53:09
| author | sushrest |
| permlink | 0wmywj62 |
| max accepted payout | 1000000.000 SBD |
| percent steem dollars | 10000 |
| allow votes | true |
| allow curation rewards | true |
| extensions | [[0,{"beneficiaries":[{"account":"dtube","weight":2500}]}]] |
| Transaction Info | Block #20651685/Trx f3f84278311fbf3ba0691aff7832fa2f07e4230e |
View Raw JSON Data
{
"trx_id": "f3f84278311fbf3ba0691aff7832fa2f07e4230e",
"block": 20651685,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-13T22:53:09",
"op": [
"comment_options",
{
"author": "sushrest",
"permlink": "0wmywj62",
"max_accepted_payout": "1000000.000 SBD",
"percent_steem_dollars": 10000,
"allow_votes": true,
"allow_curation_rewards": true,
"extensions": [
[
0,
{
"beneficiaries": [
{
"account": "dtube",
"weight": 2500
}
]
}
]
]
}
]
}2018/03/13 22:53:09
2018/03/13 22:53:09
| parent author | |
| parent permlink | plane |
| author | sushrest |
| permlink | 0wmywj62 |
| title | Bangladesh plane Crash at Kathmandu Nepal March 2018 |
| body | <center><a href='https://d.tube/#!/v/sushrest/0wmywj62'><img src='https://ipfs.io/ipfs/QmU6XG2K8jFSbYizB84izXmYQ8FRtvJsEdXMHqonU1Xj9S'></a></center><hr> Bangladesh plane Crash at Kathmandu Nepal March 2018 <hr><a href='https://d.tube/#!/v/sushrest/0wmywj62'> ▶️ DTube</a><br /><a href='https://ipfs.io/ipfs/QmayCMC7sbKyK7TbCXf2F1KQwjhwFps1Z5v6YN4NYHMnVd'> ▶️ IPFS</a> |
| json metadata | {"video":{"info":{"title":"Bangladesh plane Crash at Kathmandu Nepal March 2018","snaphash":"QmRCjGjdwpD5NHZ4BKX7Q8Zxr7NGsUm5CfYWBnj346zJHM","author":"sushrest","permlink":"0wmywj62","duration":565.474,"filesize":14391531,"spritehash":"QmWqrd66PLrVAhETiGexrdova3xz6oRYmANvxiqLHCaVwo"},"content":{"videohash":"QmayCMC7sbKyK7TbCXf2F1KQwjhwFps1Z5v6YN4NYHMnVd","description":"Bangladesh plane Crash at Kathmandu Nepal March 2018","tags":["plane","crash","nepal"],"video480hash":"QmPCV9UaZx3fgxnh5zdwRzjtm2Y3vMyWo8ifdHQPQqR5AG"}},"tags":["plane","crash","nepal","dtube"],"app":"dtube/0.7"} |
| Transaction Info | Block #20651685/Trx f3f84278311fbf3ba0691aff7832fa2f07e4230e |
View Raw JSON Data
{
"trx_id": "f3f84278311fbf3ba0691aff7832fa2f07e4230e",
"block": 20651685,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-13T22:53:09",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "plane",
"author": "sushrest",
"permlink": "0wmywj62",
"title": "Bangladesh plane Crash at Kathmandu Nepal March 2018",
"body": "<center><a href='https://d.tube/#!/v/sushrest/0wmywj62'><img src='https://ipfs.io/ipfs/QmU6XG2K8jFSbYizB84izXmYQ8FRtvJsEdXMHqonU1Xj9S'></a></center><hr>\n\nBangladesh plane Crash at Kathmandu Nepal March 2018\n\n<hr><a href='https://d.tube/#!/v/sushrest/0wmywj62'> ▶️ DTube</a><br /><a href='https://ipfs.io/ipfs/QmayCMC7sbKyK7TbCXf2F1KQwjhwFps1Z5v6YN4NYHMnVd'> ▶️ IPFS</a>",
"json_metadata": "{\"video\":{\"info\":{\"title\":\"Bangladesh plane Crash at Kathmandu Nepal March 2018\",\"snaphash\":\"QmRCjGjdwpD5NHZ4BKX7Q8Zxr7NGsUm5CfYWBnj346zJHM\",\"author\":\"sushrest\",\"permlink\":\"0wmywj62\",\"duration\":565.474,\"filesize\":14391531,\"spritehash\":\"QmWqrd66PLrVAhETiGexrdova3xz6oRYmANvxiqLHCaVwo\"},\"content\":{\"videohash\":\"QmayCMC7sbKyK7TbCXf2F1KQwjhwFps1Z5v6YN4NYHMnVd\",\"description\":\"Bangladesh plane Crash at Kathmandu Nepal March 2018\",\"tags\":[\"plane\",\"crash\",\"nepal\"],\"video480hash\":\"QmPCV9UaZx3fgxnh5zdwRzjtm2Y3vMyWo8ifdHQPQqR5AG\"}},\"tags\":[\"plane\",\"crash\",\"nepal\",\"dtube\"],\"app\":\"dtube/0.7\"}"
}
]
}2018/03/13 22:08:09
2018/03/13 22:08:09
| required auths | [] |
| required posting auths | ["sushrest"] |
| id | follow |
| json | ["follow",{"follower":"sushrest","following":"dtube","what":["blog"]}] |
| Transaction Info | Block #20650785/Trx a233650e23c3661a52bfaec7ab3bd47757a0cbfd |
View Raw JSON Data
{
"trx_id": "a233650e23c3661a52bfaec7ab3bd47757a0cbfd",
"block": 20650785,
"trx_in_block": 35,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-13T22:08:09",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"sushrest"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"sushrest\",\"following\":\"dtube\",\"what\":[\"blog\"]}]"
}
]
}sushrestupdated their account properties2018/03/13 22:08:03
sushrestupdated their account properties
2018/03/13 22:08:03
| account | sushrest |
| posting | {"weight_threshold":1,"account_auths":[["dtube.app",1]],"key_auths":[["STM6j3w66atSfSCqKrmhFcYrFaKK2b2LyvtBmHzvWtBueTpSxEuhV",1]]} |
| memo key | STM7dJyhjRjyq1TrgcCSq5w5NPbmUk3B23gV9Rz5nxZ55YwFncTN6 |
| json metadata | |
| Transaction Info | Block #20650783/Trx 5881fe75d0d73a1663b0964099c24464237ab6f7 |
View Raw JSON Data
{
"trx_id": "5881fe75d0d73a1663b0964099c24464237ab6f7",
"block": 20650783,
"trx_in_block": 40,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-13T22:08:03",
"op": [
"account_update",
{
"account": "sushrest",
"posting": {
"weight_threshold": 1,
"account_auths": [
[
"dtube.app",
1
]
],
"key_auths": [
[
"STM6j3w66atSfSCqKrmhFcYrFaKK2b2LyvtBmHzvWtBueTpSxEuhV",
1
]
]
},
"memo_key": "STM7dJyhjRjyq1TrgcCSq5w5NPbmUk3B23gV9Rz5nxZ55YwFncTN6",
"json_metadata": ""
}
]
}2018/02/18 07:34:54
2018/02/18 07:34:54
| voter | jeramyroberts |
| author | sushrest |
| permlink | re-jeramyroberts-ethereum-amd-gpu-mining-tutorial-ubuntu-16-04-lts-20180120t002045137z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #19971563/Trx a069b384fddfeafbd4563e83169085712e68e1f4 |
View Raw JSON Data
{
"trx_id": "a069b384fddfeafbd4563e83169085712e68e1f4",
"block": 19971563,
"trx_in_block": 44,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-18T07:34:54",
"op": [
"vote",
{
"voter": "jeramyroberts",
"author": "sushrest",
"permlink": "re-jeramyroberts-ethereum-amd-gpu-mining-tutorial-ubuntu-16-04-lts-20180120t002045137z",
"weight": 10000
}
]
}Manabar
Voting Power100.00%
Downvote Power100.00%
Resource Credits100.00%
Reputation Progress0.00%
{
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779087888
},
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779087888
},
"rc_account": {
"account": "sushrest",
"rc_manabar": {
"current_mana": "10164408779",
"last_update_time": 1779087888
},
"max_rc_creation_adjustment": {
"amount": "2020748973",
"precision": 6,
"nai": "@@000000037"
},
"max_rc": "10164408779"
}
}Account Metadata
| POSTING JSON METADATA | |
| profile | {"location":"Sydney","website":"https://www.sastoramro.com","profile_image":"https://steemitimages.com/DQmTWk7F2EtaphSjD7SZHU8P5b8EbYYgdr2zMVFxJ8i8eX5/myAvatar.png"} |
| JSON METADATA | |
| profile | {"location":"Sydney","website":"https://www.sastoramro.com","profile_image":"https://steemitimages.com/DQmTWk7F2EtaphSjD7SZHU8P5b8EbYYgdr2zMVFxJ8i8eX5/myAvatar.png"} |
{
"posting_json_metadata": {
"profile": {
"location": "Sydney",
"website": "https://www.sastoramro.com",
"profile_image": "https://steemitimages.com/DQmTWk7F2EtaphSjD7SZHU8P5b8EbYYgdr2zMVFxJ8i8eX5/myAvatar.png"
}
},
"json_metadata": {
"profile": {
"location": "Sydney",
"website": "https://www.sastoramro.com",
"profile_image": "https://steemitimages.com/DQmTWk7F2EtaphSjD7SZHU8P5b8EbYYgdr2zMVFxJ8i8eX5/myAvatar.png"
}
}
}Auth Keys
Owner
Single Signature
Public Keys
STM6sjkgmqMf1VmNkN4xgeT87mPCFoNe9mAETNCSce9V1murU4SKb1/1
Active
Single Signature
Public Keys
STM6rYQKo9oPiqCqMU4gTRFtV59AvQLrU7KALRfWyENbxiuHPDcLT1/1
Posting
Single Signature
Public Keys
STM6j3w66atSfSCqKrmhFcYrFaKK2b2LyvtBmHzvWtBueTpSxEuhV1/1
App Permissions
@dtube.app1/1
Memo
STM7dJyhjRjyq1TrgcCSq5w5NPbmUk3B23gV9Rz5nxZ55YwFncTN6
{
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM6sjkgmqMf1VmNkN4xgeT87mPCFoNe9mAETNCSce9V1murU4SKb",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM6rYQKo9oPiqCqMU4gTRFtV59AvQLrU7KALRfWyENbxiuHPDcLT",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [
[
"dtube.app",
1
]
],
"key_auths": [
[
"STM6j3w66atSfSCqKrmhFcYrFaKK2b2LyvtBmHzvWtBueTpSxEuhV",
1
]
]
},
"memo": "STM7dJyhjRjyq1TrgcCSq5w5NPbmUk3B23gV9Rz5nxZ55YwFncTN6"
}Witness Votes
0 / 30
No active witness votes.
[]