@josephd
54btc : 16rxpgZNV9nAMbtPNtfqW2mfnW7eN6oomZ LTC: LUDxnSnKvgKddZ9XD5ivrCjQDhP19qYEZS
steemit.com/@josephdVOTING POWER97.28%
DOWNVOTE POWER0.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS52.57%
Net Worth
0.107USD
STEEM
1.384STEEM
SBD
0.065SBD
Own SP
0.000SP
Detailed Balance
| STEEM | ||
| balance | 1.384STEEM | STEEM |
| market_balance | 0.000STEEM | STEEM |
| savings_balance | 0.000STEEM | STEEM |
| reward_steem_balance | 0.000STEEM | STEEM |
| STEEM POWER | ||
| Own SP | 0.000SP | SP |
| Delegated Out | 0.000SP | SP |
| Delegation In | 0.000SP | SP |
| Effective Power | 0.000SP | SP |
| Reward SP (pending) | 0.000SP | SP |
| SBD | ||
| sbd_balance | 0.065SBD | 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": "1.384 STEEM",
"savings_balance": "0.000 STEEM",
"reward_steem_balance": "0.000 STEEM",
"vesting_shares": "0.000000 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "0.000000 VESTS",
"sbd_balance": "0.065 SBD",
"savings_sbd_balance": "0.000 SBD",
"reward_sbd_balance": "0.000 SBD",
"conversions": []
}Account Info
| name | josephd |
| id | 125922 |
| rank | 1,938,567 |
| reputation | 1477494490230 |
| created | 2017-01-12T18:14:09 |
| recovery_account | steem |
| proxy | None |
| post_count | 833 |
| comment_count | 0 |
| lifetime_vote_count | 0 |
| witnesses_voted_for | 1 |
| last_post | 2022-07-10T07:15:27 |
| last_root_post | 2022-07-10T07:15:27 |
| last_vote_time | 2017-12-02T08:55:03 |
| proxied_vsf_votes | 0, 0, 0, 0 |
| can_vote | 1 |
| voting_power | 9,728 |
| delayed_votes | 0 |
| balance | 1.384 STEEM |
| savings_balance | 0.000 STEEM |
| sbd_balance | 0.065 SBD |
| savings_sbd_balance | 0.000 SBD |
| vesting_shares | 0.000000 VESTS |
| delegated_vesting_shares | 0.000000 VESTS |
| received_vesting_shares | 0.000000 VESTS |
| reward_vesting_balance | 0.000000 VESTS |
| vesting_balance | 0.000 STEEM |
| vesting_withdraw_rate | 0.000000 VESTS |
| next_vesting_withdrawal | 1969-12-31T23:59:59 |
| withdrawn | 2817382854 |
| to_withdraw | 2817382854 |
| withdraw_routes | 0 |
| savings_withdraw_requests | 0 |
| last_account_recovery | 1970-01-01T00:00:00 |
| reset_account | null |
| last_owner_update | 1970-01-01T00:00:00 |
| last_account_update | 2017-10-27T19:31:54 |
| mined | No |
| sbd_seconds | 0 |
| sbd_last_interest_payment | 2017-12-22T19:22:12 |
| savings_sbd_last_interest_payment | 1970-01-01T00:00:00 |
{
"id": 125922,
"name": "josephd",
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM8caGk5Y6JSnapz7XkBfTyY76jh41v6TUMVrd4VGwVSdpwiApbu",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM783dyp3SWSUDgtPCRwz9AeuKhbj9YyBGWW4XN9iaioFVXzyTRQ",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7LkgfjnRvNgWcdm4kRRts6bETLupK6obaBBdBHausLzv3vseHf",
1
]
]
},
"memo_key": "STM57b4jjHv4XdxJw9WT84p2dANkh9rDkAaBjhsh3zcE8c1mLdCnK",
"json_metadata": "{\"profile\":{\"name\":\"Joseph\",\"about\":\"btc : 16rxpgZNV9nAMbtPNtfqW2mfnW7eN6oomZ LTC: LUDxnSnKvgKddZ9XD5ivrCjQDhP19qYEZS\",\"profile_image\":\"http://i.imgur.com/GhmlxX0.jpg\"}}",
"posting_json_metadata": "{\"profile\":{\"name\":\"Joseph\",\"about\":\"btc : 16rxpgZNV9nAMbtPNtfqW2mfnW7eN6oomZ LTC: LUDxnSnKvgKddZ9XD5ivrCjQDhP19qYEZS\",\"profile_image\":\"http://i.imgur.com/GhmlxX0.jpg\"}}",
"proxy": "",
"last_owner_update": "1970-01-01T00:00:00",
"last_account_update": "2017-10-27T19:31:54",
"created": "2017-01-12T18:14:09",
"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": 833,
"can_vote": true,
"voting_manabar": {
"current_mana": 9728,
"last_update_time": 1512204903
},
"downvote_manabar": {
"current_mana": 0,
"last_update_time": 1484244849
},
"voting_power": 9728,
"balance": "1.384 STEEM",
"savings_balance": "0.000 STEEM",
"sbd_balance": "0.065 SBD",
"sbd_seconds": "0",
"sbd_seconds_last_update": "2017-12-22T19:22:12",
"sbd_last_interest_payment": "2017-12-22T19:22:12",
"savings_sbd_balance": "0.000 SBD",
"savings_sbd_seconds": "0",
"savings_sbd_seconds_last_update": "1970-01-01T00:00:00",
"savings_sbd_last_interest_payment": "1970-01-01T00:00:00",
"savings_withdraw_requests": 0,
"reward_sbd_balance": "0.000 SBD",
"reward_steem_balance": "0.000 STEEM",
"reward_vesting_balance": "0.000000 VESTS",
"reward_vesting_steem": "0.000 STEEM",
"vesting_shares": "0.000000 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "0.000000 VESTS",
"vesting_withdraw_rate": "0.000000 VESTS",
"next_vesting_withdrawal": "1969-12-31T23:59:59",
"withdrawn": 2817382854,
"to_withdraw": 2817382854,
"withdraw_routes": 0,
"curation_rewards": 1944,
"posting_rewards": 199988,
"proxied_vsf_votes": [
0,
0,
0,
0
],
"witnesses_voted_for": 1,
"last_post": "2022-07-10T07:15:27",
"last_root_post": "2022-07-10T07:15:27",
"last_vote_time": "2017-12-02T08:55:03",
"post_bandwidth": 10000,
"pending_claimed_accounts": 0,
"vesting_balance": "0.000 STEEM",
"reputation": "1477494490230",
"transfer_history": [],
"market_history": [],
"post_history": [],
"vote_history": [],
"other_history": [],
"witness_votes": [
"dragosroua"
],
"tags_usage": [],
"guest_bloggers": [],
"rank": 1938567
}Withdraw Routes
| Incoming | Outgoing |
|---|---|
Empty | Empty |
{
"incoming": [],
"outgoing": []
}From Date
To Date
josephdcustom json: follow2022/07/10 07:18:12
josephdcustom json: follow
2022/07/10 07:18:12
| required auths | [] |
| required posting auths | ["josephd"] |
| id | follow |
| json | ["reblog",{"account":"josephd","author":"josephd","permlink":"on-bitcoin-private-keys-ownership-transactions-and-more"}] |
| Transaction Info | Block #65787658/Trx 10458228aa6fba92f76f41d07903864864c787d6 |
View Raw JSON Data
{
"trx_id": "10458228aa6fba92f76f41d07903864864c787d6",
"block": 65787658,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2022-07-10T07:18:12",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"josephd"
],
"id": "follow",
"json": "[\"reblog\",{\"account\":\"josephd\",\"author\":\"josephd\",\"permlink\":\"on-bitcoin-private-keys-ownership-transactions-and-more\"}]"
}
]
}josephdcustom json: follow2022/07/10 07:18:12
josephdcustom json: follow
2022/07/10 07:18:12
| required auths | [] |
| required posting auths | ["josephd"] |
| id | follow |
| json | ["reblog",{"account":"josephd","author":"josephd","permlink":"most-promising-coin-i-ve-seen-after-eth-chainlink"}] |
| Transaction Info | Block #65787658/Trx 856b5263b789db7a7b375c8b0f4a77841dd0edac |
View Raw JSON Data
{
"trx_id": "856b5263b789db7a7b375c8b0f4a77841dd0edac",
"block": 65787658,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2022-07-10T07:18:12",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"josephd"
],
"id": "follow",
"json": "[\"reblog\",{\"account\":\"josephd\",\"author\":\"josephd\",\"permlink\":\"most-promising-coin-i-ve-seen-after-eth-chainlink\"}]"
}
]
}josephdcustom json: follow2022/07/10 07:18:09
josephdcustom json: follow
2022/07/10 07:18:09
| required auths | [] |
| required posting auths | ["josephd"] |
| id | follow |
| json | ["reblog",{"account":"josephd","author":"josephd","permlink":"5speev-more-on-intelligence-meta"}] |
| Transaction Info | Block #65787657/Trx bf08b571c55891a6c2c39d9ae9c35ac76a8caaa8 |
View Raw JSON Data
{
"trx_id": "bf08b571c55891a6c2c39d9ae9c35ac76a8caaa8",
"block": 65787657,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2022-07-10T07:18:09",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"josephd"
],
"id": "follow",
"json": "[\"reblog\",{\"account\":\"josephd\",\"author\":\"josephd\",\"permlink\":\"5speev-more-on-intelligence-meta\"}]"
}
]
}josephdremoved vote from (0.00%) @josephd / what-should-you-do-if-you-don-t-have-a-ledger-or-trezor-right-now2022/07/10 07:18:03
josephdremoved vote from (0.00%) @josephd / what-should-you-do-if-you-don-t-have-a-ledger-or-trezor-right-now
2022/07/10 07:18:03
| voter | josephd |
| author | josephd |
| permlink | what-should-you-do-if-you-don-t-have-a-ledger-or-trezor-right-now |
| weight | 0 (0.00%) |
| Transaction Info | Block #65787655/Trx ba3fb23a57d547b63234e26b5598d958f218abc9 |
View Raw JSON Data
{
"trx_id": "ba3fb23a57d547b63234e26b5598d958f218abc9",
"block": 65787655,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2022-07-10T07:18:03",
"op": [
"vote",
{
"voter": "josephd",
"author": "josephd",
"permlink": "what-should-you-do-if-you-don-t-have-a-ledger-or-trezor-right-now",
"weight": 0
}
]
}josephdremoved vote from (0.00%) @josephd / what-should-you-do-if-you-don-t-have-a-ledger-or-trezor-right-now2022/07/10 07:17:54
josephdremoved vote from (0.00%) @josephd / what-should-you-do-if-you-don-t-have-a-ledger-or-trezor-right-now
2022/07/10 07:17:54
| voter | josephd |
| author | josephd |
| permlink | what-should-you-do-if-you-don-t-have-a-ledger-or-trezor-right-now |
| weight | 0 (0.00%) |
| Transaction Info | Block #65787652/Trx eca464cca0f1dc42ab6a1267bd4dd17b64eb9869 |
View Raw JSON Data
{
"trx_id": "eca464cca0f1dc42ab6a1267bd4dd17b64eb9869",
"block": 65787652,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2022-07-10T07:17:54",
"op": [
"vote",
{
"voter": "josephd",
"author": "josephd",
"permlink": "what-should-you-do-if-you-don-t-have-a-ledger-or-trezor-right-now",
"weight": 0
}
]
}executive-boardsent 0.001 STEEM to @josephd- "❗ Hello josephd, great that you are using the STEEM blockchain. The Executive Board is publishing insider infos at https://discord.gg/KyBbmhh on how you will be earning the most coins. It's easy, just..."2022/07/10 07:17:03
executive-boardsent 0.001 STEEM to @josephd- "❗ Hello josephd, great that you are using the STEEM blockchain. The Executive Board is publishing insider infos at https://discord.gg/KyBbmhh on how you will be earning the most coins. It's easy, just..."
2022/07/10 07:17:03
| from | executive-board |
| to | josephd |
| amount | 0.001 STEEM |
| memo | ❗ Hello josephd, great that you are using the STEEM blockchain. The Executive Board is publishing insider infos at https://discord.gg/KyBbmhh on how you will be earning the most coins. It's easy, just follow the instructions. THE 1000X BOOSTER KEY is already waiting for you over there too. 😉 Warm regards, The Executive Board. |
| Transaction Info | Block #65787636/Trx 335b494addb188bca855ffa2c772c352ea373c0a |
View Raw JSON Data
{
"trx_id": "335b494addb188bca855ffa2c772c352ea373c0a",
"block": 65787636,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2022-07-10T07:17:03",
"op": [
"transfer",
{
"from": "executive-board",
"to": "josephd",
"amount": "0.001 STEEM",
"memo": "❗ Hello josephd, great that you are using the STEEM blockchain. The Executive Board is publishing insider infos at https://discord.gg/KyBbmhh on how you will be earning the most coins. It's easy, just follow the instructions. THE 1000X BOOSTER KEY is already waiting for you over there too. 😉 Warm regards, The Executive Board."
}
]
}2022/07/10 07:15:27
2022/07/10 07:15:27
| parent author | |
| parent permlink | test |
| author | josephd |
| permlink | test |
| title | test |
| body | test |
| json metadata | {"tags":["test"],"app":"steemit/0.2","format":"markdown"} |
| Transaction Info | Block #65787604/Trx 0d41296216e9e885ab303a3a4d83a3edb184b806 |
View Raw JSON Data
{
"trx_id": "0d41296216e9e885ab303a3a4d83a3edb184b806",
"block": 65787604,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2022-07-10T07:15:27",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "test",
"author": "josephd",
"permlink": "test",
"title": "test",
"body": "test",
"json_metadata": "{\"tags\":[\"test\"],\"app\":\"steemit/0.2\",\"format\":\"markdown\"}"
}
]
}2020/01/12 19:52:21
2020/01/12 19:52:21
| parent author | josephd |
| parent permlink | what-should-you-do-if-you-don-t-have-a-ledger-or-trezor-right-now |
| author | steemitboard |
| permlink | steemitboard-notify-josephd-20200112t195221000z |
| title | |
| body | Congratulations @josephd! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@josephd/birthday3.png</td><td>Happy Birthday! - You are on the Steem blockchain for 3 years!</td></tr></table> <sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@josephd) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=josephd)_</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 #39872332/Trx 9c1fe0923df16bb3d0f93dfec5e1689345a5bbdb |
View Raw JSON Data
{
"trx_id": "9c1fe0923df16bb3d0f93dfec5e1689345a5bbdb",
"block": 39872332,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-01-12T19:52:21",
"op": [
"comment",
{
"parent_author": "josephd",
"parent_permlink": "what-should-you-do-if-you-don-t-have-a-ledger-or-trezor-right-now",
"author": "steemitboard",
"permlink": "steemitboard-notify-josephd-20200112t195221000z",
"title": "",
"body": "Congratulations @josephd! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@josephd/birthday3.png</td><td>Happy Birthday! - You are on the Steem blockchain for 3 years!</td></tr></table>\n\n<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@josephd) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=josephd)_</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\"]}"
}
]
}steemdetectivesent 0.001 STEEM to @josephd- "Hy @josephd check out https://steemdetective.com"2019/05/13 09:26:33
steemdetectivesent 0.001 STEEM to @josephd- "Hy @josephd check out https://steemdetective.com"
2019/05/13 09:26:33
| from | steemdetective |
| to | josephd |
| amount | 0.001 STEEM |
| memo | Hy @josephd check out https://steemdetective.com |
| Transaction Info | Block #32867724/Trx a74033258441bca19de8a6e35802f0e901471e96 |
View Raw JSON Data
{
"trx_id": "a74033258441bca19de8a6e35802f0e901471e96",
"block": 32867724,
"trx_in_block": 20,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-05-13T09:26:33",
"op": [
"transfer",
{
"from": "steemdetective",
"to": "josephd",
"amount": "0.001 STEEM",
"memo": "Hy @josephd check out https://steemdetective.com"
}
]
}naglfar94upvoted (100.00%) @josephd / america-s-age-of-consent-is-higher-than-it-needs-to-be2019/02/24 01:28:06
naglfar94upvoted (100.00%) @josephd / america-s-age-of-consent-is-higher-than-it-needs-to-be
2019/02/24 01:28:06
| voter | naglfar94 |
| author | josephd |
| permlink | america-s-age-of-consent-is-higher-than-it-needs-to-be |
| weight | 10000 (100.00%) |
| Transaction Info | Block #30614740/Trx a88bdd1cc6fba9c83b139b0281cf8f789cd8fc72 |
View Raw JSON Data
{
"trx_id": "a88bdd1cc6fba9c83b139b0281cf8f789cd8fc72",
"block": 30614740,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-02-24T01:28:06",
"op": [
"vote",
{
"voter": "naglfar94",
"author": "josephd",
"permlink": "america-s-age-of-consent-is-higher-than-it-needs-to-be",
"weight": 10000
}
]
}2019/02/14 03:25:42
2019/02/14 03:25:42
| parent author | josephd |
| parent permlink | tips-for-trading-alt-coins-for-noobs |
| author | niel96 |
| permlink | re-josephd-tips-for-trading-alt-coins-for-noobs-20190214t032540396z |
| title | |
| body | Hi, when you want to receive profitable trading ideas for free then follow the million dollar challenge: https://steemit.com/trading/@niel96/million-dollar-trading-challenge-is-coming-soon |
| json metadata | {"tags":["cryptocurrency"],"links":["https://steemit.com/trading/@niel96/million-dollar-trading-challenge-is-coming-soon"],"app":"steemit/0.1"} |
| Transaction Info | Block #30329297/Trx 0b1fcf1b17dc7b884cc4355704afc0744f7535aa |
View Raw JSON Data
{
"trx_id": "0b1fcf1b17dc7b884cc4355704afc0744f7535aa",
"block": 30329297,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-02-14T03:25:42",
"op": [
"comment",
{
"parent_author": "josephd",
"parent_permlink": "tips-for-trading-alt-coins-for-noobs",
"author": "niel96",
"permlink": "re-josephd-tips-for-trading-alt-coins-for-noobs-20190214t032540396z",
"title": "",
"body": "Hi, \n\nwhen you want to receive profitable trading ideas for free then follow the million dollar challenge:\n\nhttps://steemit.com/trading/@niel96/million-dollar-trading-challenge-is-coming-soon",
"json_metadata": "{\"tags\":[\"cryptocurrency\"],\"links\":[\"https://steemit.com/trading/@niel96/million-dollar-trading-challenge-is-coming-soon\"],\"app\":\"steemit/0.1\"}"
}
]
}2019/01/12 19:07:48
2019/01/12 19:07:48
| parent author | josephd |
| parent permlink | what-should-you-do-if-you-don-t-have-a-ledger-or-trezor-right-now |
| author | steemitboard |
| permlink | steemitboard-notify-josephd-20190112t190747000z |
| title | |
| body | Congratulations @josephd! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@josephd/birthday2.png</td><td>2 Years on Steemit</td></tr></table> <sub>_[Click here to view your Board](https://steemitboard.com/@josephd)_</sub> **Do not miss the last post from @steemitboard:** <table><tr><td><a href="https://steemit.com/steem/@steemitboard/steemwhales-has-officially-moved-to-steemitboard-ranking"><img src="https://steemitimages.com/64x128/https://cdn.steemitimages.com/DQmfRVpHQhLDhnjDtqck8GPv9NPvNKPfMsDaAFDE1D9Er2Z/header_ranking.png"></a></td><td><a href="https://steemit.com/steem/@steemitboard/steemwhales-has-officially-moved-to-steemitboard-ranking">SteemWhales has officially moved to SteemitBoard Ranking</a></td></tr><tr><td><a href="https://steemit.com/steemitboard/@steemitboard/steemitboard-witness-update-2019-01-07"><img src="https://steemitimages.com/64x128/http://i.cubeupload.com/7CiQEO.png"></a></td><td><a href="https://steemit.com/steemitboard/@steemitboard/steemitboard-witness-update-2019-01-07">SteemitBoard - Witness Update</a></td></tr></table> > Support [SteemitBoard's project](https://steemit.com/@steemitboard)! **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| Transaction Info | Block #29398623/Trx a3fa5cbdabfae002b5cba7044811c7ace6d4065f |
View Raw JSON Data
{
"trx_id": "a3fa5cbdabfae002b5cba7044811c7ace6d4065f",
"block": 29398623,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-01-12T19:07:48",
"op": [
"comment",
{
"parent_author": "josephd",
"parent_permlink": "what-should-you-do-if-you-don-t-have-a-ledger-or-trezor-right-now",
"author": "steemitboard",
"permlink": "steemitboard-notify-josephd-20190112t190747000z",
"title": "",
"body": "Congratulations @josephd! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@josephd/birthday2.png</td><td>2 Years on Steemit</td></tr></table>\n\n<sub>_[Click here to view your Board](https://steemitboard.com/@josephd)_</sub>\n\n\n**Do not miss the last post from @steemitboard:**\n<table><tr><td><a href=\"https://steemit.com/steem/@steemitboard/steemwhales-has-officially-moved-to-steemitboard-ranking\"><img src=\"https://steemitimages.com/64x128/https://cdn.steemitimages.com/DQmfRVpHQhLDhnjDtqck8GPv9NPvNKPfMsDaAFDE1D9Er2Z/header_ranking.png\"></a></td><td><a href=\"https://steemit.com/steem/@steemitboard/steemwhales-has-officially-moved-to-steemitboard-ranking\">SteemWhales has officially moved to SteemitBoard Ranking</a></td></tr><tr><td><a href=\"https://steemit.com/steemitboard/@steemitboard/steemitboard-witness-update-2019-01-07\"><img src=\"https://steemitimages.com/64x128/http://i.cubeupload.com/7CiQEO.png\"></a></td><td><a href=\"https://steemit.com/steemitboard/@steemitboard/steemitboard-witness-update-2019-01-07\">SteemitBoard - Witness Update</a></td></tr></table>\n\n> Support [SteemitBoard's project](https://steemit.com/@steemitboard)! **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}"
}
]
}2018/12/10 00:47:45
2018/12/10 00:47:45
| parent author | josephd |
| parent permlink | tips-for-trading-alt-coins-for-noobs |
| author | acuminousfeet95 |
| permlink | re-josephd-tips-for-trading-alt-coins-for-noobs-20181210t004748127z |
| title | |
| body | thanks for posting this mate! Now i know how can i trade my iog now i can apply it in this IOG trading competition lol https://www.kucoin.com/#/rank/IOG |
| json metadata | {"tags":["cryptocurrency"],"links":["https://www.kucoin.com/#/rank/IOG"],"app":"steemit/0.1"} |
| Transaction Info | Block #28426926/Trx 6766eef3b1aed403b46eede5913072682274f460 |
View Raw JSON Data
{
"trx_id": "6766eef3b1aed403b46eede5913072682274f460",
"block": 28426926,
"trx_in_block": 9,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-12-10T00:47:45",
"op": [
"comment",
{
"parent_author": "josephd",
"parent_permlink": "tips-for-trading-alt-coins-for-noobs",
"author": "acuminousfeet95",
"permlink": "re-josephd-tips-for-trading-alt-coins-for-noobs-20181210t004748127z",
"title": "",
"body": "thanks for posting this mate! Now i know how can i trade my iog now i can apply it in this IOG trading competition lol https://www.kucoin.com/#/rank/IOG",
"json_metadata": "{\"tags\":[\"cryptocurrency\"],\"links\":[\"https://www.kucoin.com/#/rank/IOG\"],\"app\":\"steemit/0.1\"}"
}
]
}2018/11/14 13:18:42
2018/11/14 13:18:42
| parent author | josephd |
| parent permlink | tips-for-trading-alt-coins-for-noobs |
| author | rcapollo9 |
| permlink | re-josephd-tips-for-trading-alt-coins-for-noobs-20181114t131818491z |
| title | |
| body | Lucky that i found this kind of article its a great opportunity for ppl that is new in crypto to know more about altcoins. I also found something that is also related with altcoins https://twitter.com/Sophia_TX_/status/1061954296953163777 |
| json metadata | {"tags":["cryptocurrency"],"links":["https://twitter.com/Sophia_TX_/status/1061954296953163777"],"app":"steemit/0.1"} |
| Transaction Info | Block #27693521/Trx 900a6284c34ca0755f9ea74b6ad9394a8c6008d7 |
View Raw JSON Data
{
"trx_id": "900a6284c34ca0755f9ea74b6ad9394a8c6008d7",
"block": 27693521,
"trx_in_block": 25,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-11-14T13:18:42",
"op": [
"comment",
{
"parent_author": "josephd",
"parent_permlink": "tips-for-trading-alt-coins-for-noobs",
"author": "rcapollo9",
"permlink": "re-josephd-tips-for-trading-alt-coins-for-noobs-20181114t131818491z",
"title": "",
"body": "Lucky that i found this kind of article its a great opportunity for ppl that is new in crypto to know more about altcoins. I also found something that is also related with altcoins https://twitter.com/Sophia_TX_/status/1061954296953163777",
"json_metadata": "{\"tags\":[\"cryptocurrency\"],\"links\":[\"https://twitter.com/Sophia_TX_/status/1061954296953163777\"],\"app\":\"steemit/0.1\"}"
}
]
}2018/08/21 11:28:54
2018/08/21 11:28:54
| voter | pocketechange |
| author | josephd |
| permlink | re-neoxian-secret-tips-how-to-get-on-the-trending-page-20170702t205506505z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #25260632/Trx c73c34db8fc88a0e1f952dc5c6ebc9f13baf61a7 |
View Raw JSON Data
{
"trx_id": "c73c34db8fc88a0e1f952dc5c6ebc9f13baf61a7",
"block": 25260632,
"trx_in_block": 31,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-08-21T11:28:54",
"op": [
"vote",
{
"voter": "pocketechange",
"author": "josephd",
"permlink": "re-neoxian-secret-tips-how-to-get-on-the-trending-page-20170702t205506505z",
"weight": 10000
}
]
}2018/07/13 00:10:00
2018/07/13 00:10:00
| parent author | josephd |
| parent permlink | most-promising-coin-i-ve-seen-after-eth-chainlink |
| author | memeinventor |
| permlink | re-josephd-most-promising-coin-i-ve-seen-after-eth-chainlink-20180713t001001020z |
| title | |
| body | future rich guy right here |
| json metadata | {"tags":["crypto"],"app":"steemit/0.1"} |
| Transaction Info | Block #24124846/Trx 9a70ee3024bcbd8dc6a9dbcb90451ca4995458b8 |
View Raw JSON Data
{
"trx_id": "9a70ee3024bcbd8dc6a9dbcb90451ca4995458b8",
"block": 24124846,
"trx_in_block": 27,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-07-13T00:10:00",
"op": [
"comment",
{
"parent_author": "josephd",
"parent_permlink": "most-promising-coin-i-ve-seen-after-eth-chainlink",
"author": "memeinventor",
"permlink": "re-josephd-most-promising-coin-i-ve-seen-after-eth-chainlink-20180713t001001020z",
"title": "",
"body": "future rich guy right here",
"json_metadata": "{\"tags\":[\"crypto\"],\"app\":\"steemit/0.1\"}"
}
]
}2018/07/04 19:14:57
2018/07/04 19:14:57
| parent author | josephd |
| parent permlink | new-to-steemit-who-to-follow |
| author | christpaquin |
| permlink | re-josephd-new-to-steemit-who-to-follow-20180704t191501532z |
| title | |
| body | Great post! I follow you, you know what you are talking about! |
| json metadata | {"tags":["steemit"],"app":"steemit/0.1"} |
| Transaction Info | Block #23888657/Trx a70c3408529c85df6c6f9090aed88b4b3b88cf10 |
View Raw JSON Data
{
"trx_id": "a70c3408529c85df6c6f9090aed88b4b3b88cf10",
"block": 23888657,
"trx_in_block": 32,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-07-04T19:14:57",
"op": [
"comment",
{
"parent_author": "josephd",
"parent_permlink": "new-to-steemit-who-to-follow",
"author": "christpaquin",
"permlink": "re-josephd-new-to-steemit-who-to-follow-20180704t191501532z",
"title": "",
"body": "Great post! I follow you, you know what you are talking about!",
"json_metadata": "{\"tags\":[\"steemit\"],\"app\":\"steemit/0.1\"}"
}
]
}christpaquinupvoted (100.00%) @josephd / new-to-steemit-who-to-follow2018/07/04 19:13:18
christpaquinupvoted (100.00%) @josephd / new-to-steemit-who-to-follow
2018/07/04 19:13:18
| voter | christpaquin |
| author | josephd |
| permlink | new-to-steemit-who-to-follow |
| weight | 10000 (100.00%) |
| Transaction Info | Block #23888624/Trx 984660ed00faa178ce10a31fea3fcca236f19660 |
View Raw JSON Data
{
"trx_id": "984660ed00faa178ce10a31fea3fcca236f19660",
"block": 23888624,
"trx_in_block": 13,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-07-04T19:13:18",
"op": [
"vote",
{
"voter": "christpaquin",
"author": "josephd",
"permlink": "new-to-steemit-who-to-follow",
"weight": 10000
}
]
}2018/06/05 05:48:45
2018/06/05 05:48:45
| voter | churchmoney |
| author | josephd |
| permlink | re-renzoarg-re-josephd-new-to-steemit-who-to-follow-20170623t103726955z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #23047977/Trx bb9222e712d346a1e7361015048509d341170607 |
View Raw JSON Data
{
"trx_id": "bb9222e712d346a1e7361015048509d341170607",
"block": 23047977,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-05T05:48:45",
"op": [
"vote",
{
"voter": "churchmoney",
"author": "josephd",
"permlink": "re-renzoarg-re-josephd-new-to-steemit-who-to-follow-20170623t103726955z",
"weight": 10000
}
]
}josephdreceived 0.106 STEEM from power down installment (0.133 SP)2018/05/04 14:50:57
josephdreceived 0.106 STEEM from power down installment (0.133 SP)
2018/05/04 14:50:57
| from account | josephd |
| to account | josephd |
| withdrawn | 216.721758 VESTS |
| deposited | 0.106 STEEM |
| Transaction Info | Block #22137788/Virtual Operation #15 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 22137788,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 15,
"timestamp": "2018-05-04T14:50:57",
"op": [
"fill_vesting_withdraw",
{
"from_account": "josephd",
"to_account": "josephd",
"withdrawn": "216.721758 VESTS",
"deposited": "0.106 STEEM"
}
]
}josephdreceived 0.106 STEEM from power down installment (0.133 SP)2018/04/27 14:50:57
josephdreceived 0.106 STEEM from power down installment (0.133 SP)
2018/04/27 14:50:57
| from account | josephd |
| to account | josephd |
| withdrawn | 216.721758 VESTS |
| deposited | 0.106 STEEM |
| Transaction Info | Block #21936231/Virtual Operation #7 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 21936231,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 7,
"timestamp": "2018-04-27T14:50:57",
"op": [
"fill_vesting_withdraw",
{
"from_account": "josephd",
"to_account": "josephd",
"withdrawn": "216.721758 VESTS",
"deposited": "0.106 STEEM"
}
]
}josephdreceived 0.106 STEEM from power down installment (0.133 SP)2018/04/20 14:50:57
josephdreceived 0.106 STEEM from power down installment (0.133 SP)
2018/04/20 14:50:57
| from account | josephd |
| to account | josephd |
| withdrawn | 216.721758 VESTS |
| deposited | 0.106 STEEM |
| Transaction Info | Block #21735314/Virtual Operation #30 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 21735314,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 30,
"timestamp": "2018-04-20T14:50:57",
"op": [
"fill_vesting_withdraw",
{
"from_account": "josephd",
"to_account": "josephd",
"withdrawn": "216.721758 VESTS",
"deposited": "0.106 STEEM"
}
]
}crocknifeflagged (-100.00%) @josephd / america-s-age-of-consent-is-higher-than-it-needs-to-be2018/04/17 03:28:24
crocknifeflagged (-100.00%) @josephd / america-s-age-of-consent-is-higher-than-it-needs-to-be
2018/04/17 03:28:24
| voter | crocknife |
| author | josephd |
| permlink | america-s-age-of-consent-is-higher-than-it-needs-to-be |
| weight | -10000 (-100.00%) |
| Transaction Info | Block #21635280/Trx aaaae0e45638f89e60c0e5870878b8a1f07ddaa8 |
View Raw JSON Data
{
"trx_id": "aaaae0e45638f89e60c0e5870878b8a1f07ddaa8",
"block": 21635280,
"trx_in_block": 9,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-17T03:28:24",
"op": [
"vote",
{
"voter": "crocknife",
"author": "josephd",
"permlink": "america-s-age-of-consent-is-higher-than-it-needs-to-be",
"weight": -10000
}
]
}josephdreceived 0.106 STEEM from power down installment (0.133 SP)2018/04/13 14:50:57
josephdreceived 0.106 STEEM from power down installment (0.133 SP)
2018/04/13 14:50:57
| from account | josephd |
| to account | josephd |
| withdrawn | 216.721758 VESTS |
| deposited | 0.106 STEEM |
| Transaction Info | Block #21533748/Virtual Operation #12 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 21533748,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 12,
"timestamp": "2018-04-13T14:50:57",
"op": [
"fill_vesting_withdraw",
{
"from_account": "josephd",
"to_account": "josephd",
"withdrawn": "216.721758 VESTS",
"deposited": "0.106 STEEM"
}
]
}vladlenterezheupvoted (100.00%) @josephd / most-promising-coin-i-ve-seen-after-eth-chainlink2018/04/09 07:58:18
vladlenterezheupvoted (100.00%) @josephd / most-promising-coin-i-ve-seen-after-eth-chainlink
2018/04/09 07:58:18
| voter | vladlenterezhe |
| author | josephd |
| permlink | most-promising-coin-i-ve-seen-after-eth-chainlink |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21410312/Trx 00f2fdc0311a829c8fc72a9096753c97d82cdcef |
View Raw JSON Data
{
"trx_id": "00f2fdc0311a829c8fc72a9096753c97d82cdcef",
"block": 21410312,
"trx_in_block": 45,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-09T07:58:18",
"op": [
"vote",
{
"voter": "vladlenterezhe",
"author": "josephd",
"permlink": "most-promising-coin-i-ve-seen-after-eth-chainlink",
"weight": 10000
}
]
}josephdreceived 0.106 STEEM from power down installment (0.133 SP)2018/04/06 14:50:57
josephdreceived 0.106 STEEM from power down installment (0.133 SP)
2018/04/06 14:50:57
| from account | josephd |
| to account | josephd |
| withdrawn | 216.721758 VESTS |
| deposited | 0.106 STEEM |
| Transaction Info | Block #21332168/Virtual Operation #14 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 21332168,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 14,
"timestamp": "2018-04-06T14:50:57",
"op": [
"fill_vesting_withdraw",
{
"from_account": "josephd",
"to_account": "josephd",
"withdrawn": "216.721758 VESTS",
"deposited": "0.106 STEEM"
}
]
}josephdupvoted (100.00%) @lukestokes / re-dan-in-defense-of-consortium-blockchains-20171118t165442903z2018/04/01 15:27:54
josephdupvoted (100.00%) @lukestokes / re-dan-in-defense-of-consortium-blockchains-20171118t165442903z
2018/04/01 15:27:54
| voter | josephd |
| author | lukestokes |
| permlink | re-dan-in-defense-of-consortium-blockchains-20171118t165442903z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21188930/Trx b64bfcf671ddb74fe05b0cfa4803b5bb9b2b9561 |
View Raw JSON Data
{
"trx_id": "b64bfcf671ddb74fe05b0cfa4803b5bb9b2b9561",
"block": 21188930,
"trx_in_block": 53,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-01T15:27:54",
"op": [
"vote",
{
"voter": "josephd",
"author": "lukestokes",
"permlink": "re-dan-in-defense-of-consortium-blockchains-20171118t165442903z",
"weight": 10000
}
]
}josephdreceived 0.106 STEEM from power down installment (0.133 SP)2018/03/30 14:50:57
josephdreceived 0.106 STEEM from power down installment (0.133 SP)
2018/03/30 14:50:57
| from account | josephd |
| to account | josephd |
| withdrawn | 216.721758 VESTS |
| deposited | 0.106 STEEM |
| Transaction Info | Block #21130605/Virtual Operation #22 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 21130605,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 22,
"timestamp": "2018-03-30T14:50:57",
"op": [
"fill_vesting_withdraw",
{
"from_account": "josephd",
"to_account": "josephd",
"withdrawn": "216.721758 VESTS",
"deposited": "0.106 STEEM"
}
]
}josephdreceived 0.106 STEEM from power down installment (0.133 SP)2018/03/23 14:50:57
josephdreceived 0.106 STEEM from power down installment (0.133 SP)
2018/03/23 14:50:57
| from account | josephd |
| to account | josephd |
| withdrawn | 216.721758 VESTS |
| deposited | 0.106 STEEM |
| Transaction Info | Block #20929072/Virtual Operation #20 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 20929072,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 20,
"timestamp": "2018-03-23T14:50:57",
"op": [
"fill_vesting_withdraw",
{
"from_account": "josephd",
"to_account": "josephd",
"withdrawn": "216.721758 VESTS",
"deposited": "0.106 STEEM"
}
]
}activist-newssent 0.005 STEEM to @josephd- "A gift. 😊"2018/03/17 21:46:21
activist-newssent 0.005 STEEM to @josephd- "A gift. 😊"
2018/03/17 21:46:21
| from | activist-news |
| to | josephd |
| amount | 0.005 STEEM |
| memo | A gift. 😊 |
| Transaction Info | Block #20765422/Trx 015f0425e08da10a2d7eb9bf3eff5663ac616a87 |
View Raw JSON Data
{
"trx_id": "015f0425e08da10a2d7eb9bf3eff5663ac616a87",
"block": 20765422,
"trx_in_block": 18,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-17T21:46:21",
"op": [
"transfer",
{
"from": "activist-news",
"to": "josephd",
"amount": "0.005 STEEM",
"memo": "A gift. 😊"
}
]
}josephdreceived 0.106 STEEM from power down installment (0.133 SP)2018/03/16 14:50:57
josephdreceived 0.106 STEEM from power down installment (0.133 SP)
2018/03/16 14:50:57
| from account | josephd |
| to account | josephd |
| withdrawn | 216.721758 VESTS |
| deposited | 0.106 STEEM |
| Transaction Info | Block #20728325/Virtual Operation #13 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 20728325,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 13,
"timestamp": "2018-03-16T14:50:57",
"op": [
"fill_vesting_withdraw",
{
"from_account": "josephd",
"to_account": "josephd",
"withdrawn": "216.721758 VESTS",
"deposited": "0.106 STEEM"
}
]
}josephdreceived 0.106 STEEM from power down installment (0.133 SP)2018/03/09 14:50:57
josephdreceived 0.106 STEEM from power down installment (0.133 SP)
2018/03/09 14:50:57
| from account | josephd |
| to account | josephd |
| withdrawn | 216.721758 VESTS |
| deposited | 0.106 STEEM |
| Transaction Info | Block #20527035/Virtual Operation #17 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 20527035,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 17,
"timestamp": "2018-03-09T14:50:57",
"op": [
"fill_vesting_withdraw",
{
"from_account": "josephd",
"to_account": "josephd",
"withdrawn": "216.721758 VESTS",
"deposited": "0.106 STEEM"
}
]
}nick97upvoted (100.00%) @josephd / new-to-steemit-who-to-follow2018/03/03 23:25:51
nick97upvoted (100.00%) @josephd / new-to-steemit-who-to-follow
2018/03/03 23:25:51
| voter | nick97 |
| author | josephd |
| permlink | new-to-steemit-who-to-follow |
| weight | 10000 (100.00%) |
| Transaction Info | Block #20364703/Trx bd5ee7068628778e16f857d26d8febfb3f8ee863 |
View Raw JSON Data
{
"trx_id": "bd5ee7068628778e16f857d26d8febfb3f8ee863",
"block": 20364703,
"trx_in_block": 53,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-03T23:25:51",
"op": [
"vote",
{
"voter": "nick97",
"author": "josephd",
"permlink": "new-to-steemit-who-to-follow",
"weight": 10000
}
]
}josephdreceived 0.106 STEEM from power down installment (0.133 SP)2018/03/02 14:50:57
josephdreceived 0.106 STEEM from power down installment (0.133 SP)
2018/03/02 14:50:57
| from account | josephd |
| to account | josephd |
| withdrawn | 216.721758 VESTS |
| deposited | 0.106 STEEM |
| Transaction Info | Block #20325612/Virtual Operation #10 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 20325612,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 10,
"timestamp": "2018-03-02T14:50:57",
"op": [
"fill_vesting_withdraw",
{
"from_account": "josephd",
"to_account": "josephd",
"withdrawn": "216.721758 VESTS",
"deposited": "0.106 STEEM"
}
]
}josephdreceived 0.106 STEEM from power down installment (0.133 SP)2018/02/23 14:50:57
josephdreceived 0.106 STEEM from power down installment (0.133 SP)
2018/02/23 14:50:57
| from account | josephd |
| to account | josephd |
| withdrawn | 216.721758 VESTS |
| deposited | 0.106 STEEM |
| Transaction Info | Block #20124241/Virtual Operation #31 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 20124241,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 31,
"timestamp": "2018-02-23T14:50:57",
"op": [
"fill_vesting_withdraw",
{
"from_account": "josephd",
"to_account": "josephd",
"withdrawn": "216.721758 VESTS",
"deposited": "0.106 STEEM"
}
]
}josephdreceived 0.106 STEEM from power down installment (0.133 SP)2018/02/16 14:50:57
josephdreceived 0.106 STEEM from power down installment (0.133 SP)
2018/02/16 14:50:57
| from account | josephd |
| to account | josephd |
| withdrawn | 216.721758 VESTS |
| deposited | 0.106 STEEM |
| Transaction Info | Block #19922705/Virtual Operation #13 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 19922705,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 13,
"timestamp": "2018-02-16T14:50:57",
"op": [
"fill_vesting_withdraw",
{
"from_account": "josephd",
"to_account": "josephd",
"withdrawn": "216.721758 VESTS",
"deposited": "0.106 STEEM"
}
]
}josephdreceived 0.105 STEEM from power down installment (0.133 SP)2018/02/09 14:50:57
josephdreceived 0.105 STEEM from power down installment (0.133 SP)
2018/02/09 14:50:57
| from account | josephd |
| to account | josephd |
| withdrawn | 216.721758 VESTS |
| deposited | 0.105 STEEM |
| Transaction Info | Block #19721281/Virtual Operation #38 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 19721281,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 38,
"timestamp": "2018-02-09T14:50:57",
"op": [
"fill_vesting_withdraw",
{
"from_account": "josephd",
"to_account": "josephd",
"withdrawn": "216.721758 VESTS",
"deposited": "0.105 STEEM"
}
]
}josephdstarted power down of 1.730 SP2018/02/02 14:50:57
josephdstarted power down of 1.730 SP
2018/02/02 14:50:57
| account | josephd |
| vesting shares | 2817.382854 VESTS |
| Transaction Info | Block #19520125/Trx 7fd8e84dc96a1b3025d9c916bbc6dc22c33ab73b |
View Raw JSON Data
{
"trx_id": "7fd8e84dc96a1b3025d9c916bbc6dc22c33ab73b",
"block": 19520125,
"trx_in_block": 34,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-02T14:50:57",
"op": [
"withdraw_vesting",
{
"account": "josephd",
"vesting_shares": "2817.382854 VESTS"
}
]
}hawknismoupvoted (100.00%) @josephd / new-to-steemit-who-to-follow2018/01/25 11:50:39
hawknismoupvoted (100.00%) @josephd / new-to-steemit-who-to-follow
2018/01/25 11:50:39
| voter | hawknismo |
| author | josephd |
| permlink | new-to-steemit-who-to-follow |
| weight | 10000 (100.00%) |
| Transaction Info | Block #19286332/Trx fcc383b9e240f200c1cc4174a7c417023ec46faf |
View Raw JSON Data
{
"trx_id": "fcc383b9e240f200c1cc4174a7c417023ec46faf",
"block": 19286332,
"trx_in_block": 28,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-25T11:50:39",
"op": [
"vote",
{
"voter": "hawknismo",
"author": "josephd",
"permlink": "new-to-steemit-who-to-follow",
"weight": 10000
}
]
}2018/01/12 18:42:18
2018/01/12 18:42:18
| voter | filipdascalu |
| author | josephd |
| permlink | re-filipdascalu-bitcoin-and-alts-in-the-cryptocurrency-market-20171025t122736414z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #18920376/Trx 8e54443410c5be6f9c7f9b89d4b35b16ad1e005c |
View Raw JSON Data
{
"trx_id": "8e54443410c5be6f9c7f9b89d4b35b16ad1e005c",
"block": 18920376,
"trx_in_block": 8,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-12T18:42:18",
"op": [
"vote",
{
"voter": "filipdascalu",
"author": "josephd",
"permlink": "re-filipdascalu-bitcoin-and-alts-in-the-cryptocurrency-market-20171025t122736414z",
"weight": 10000
}
]
}gustavoaca1997upvoted (100.00%) @josephd / new-to-steemit-who-to-follow2018/01/02 19:42:45
gustavoaca1997upvoted (100.00%) @josephd / new-to-steemit-who-to-follow
2018/01/02 19:42:45
| voter | gustavoaca1997 |
| author | josephd |
| permlink | new-to-steemit-who-to-follow |
| weight | 10000 (100.00%) |
| Transaction Info | Block #18633803/Trx ba76b7c5449f4168124f018b7ab6f794e1c8b88c |
View Raw JSON Data
{
"trx_id": "ba76b7c5449f4168124f018b7ab6f794e1c8b88c",
"block": 18633803,
"trx_in_block": 27,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-02T19:42:45",
"op": [
"vote",
{
"voter": "gustavoaca1997",
"author": "josephd",
"permlink": "new-to-steemit-who-to-follow",
"weight": 10000
}
]
}2017/12/28 23:57:42
2017/12/28 23:57:42
| voter | daneshbaetabrizi |
| author | josephd |
| permlink | re-sherlock2-re-cryptohustlin-re-papa-pepper-re-darthnava-re-papa-pepper-re-darthnava-re-papa-pepper-re-darthnava-fellow-steemers-i-need-help-as-my-mri-results-are-not-encouraging-20170607t004851947z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #18495149/Trx 7446bc7e66e380547308195fc548996bbe9abf63 |
View Raw JSON Data
{
"trx_id": "7446bc7e66e380547308195fc548996bbe9abf63",
"block": 18495149,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-28T23:57:42",
"op": [
"vote",
{
"voter": "daneshbaetabrizi",
"author": "josephd",
"permlink": "re-sherlock2-re-cryptohustlin-re-papa-pepper-re-darthnava-re-papa-pepper-re-darthnava-re-papa-pepper-re-darthnava-fellow-steemers-i-need-help-as-my-mri-results-are-not-encouraging-20170607t004851947z",
"weight": 10000
}
]
}josephdclaimed reward balance: 0.044 SBD, 0.034 SP2017/12/22 19:22:12
josephdclaimed reward balance: 0.044 SBD, 0.034 SP
2017/12/22 19:22:12
| account | josephd |
| reward steem | 0.000 STEEM |
| reward sbd | 0.044 SBD |
| reward vests | 55.391043 VESTS |
| Transaction Info | Block #18316956/Trx 4209032dde01797579efb7c4e824ca8fb43eafe6 |
View Raw JSON Data
{
"trx_id": "4209032dde01797579efb7c4e824ca8fb43eafe6",
"block": 18316956,
"trx_in_block": 22,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-22T19:22:12",
"op": [
"claim_reward_balance",
{
"account": "josephd",
"reward_steem": "0.000 STEEM",
"reward_sbd": "0.044 SBD",
"reward_vests": "55.391043 VESTS"
}
]
}antonderegtupvoted (100.00%) @josephd / new-to-steemit-who-to-follow2017/12/18 15:47:36
antonderegtupvoted (100.00%) @josephd / new-to-steemit-who-to-follow
2017/12/18 15:47:36
| voter | antonderegt |
| author | josephd |
| permlink | new-to-steemit-who-to-follow |
| weight | 10000 (100.00%) |
| Transaction Info | Block #18197493/Trx 5bf0d1663b292c190a4ace131e44d12cb8efac06 |
View Raw JSON Data
{
"trx_id": "5bf0d1663b292c190a4ace131e44d12cb8efac06",
"block": 18197493,
"trx_in_block": 23,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-18T15:47:36",
"op": [
"vote",
{
"voter": "antonderegt",
"author": "josephd",
"permlink": "new-to-steemit-who-to-follow",
"weight": 10000
}
]
}2017/12/16 03:16:51
2017/12/16 03:16:51
| parent author | josephd |
| parent permlink | re-finance2nomad-travel-stories-2-north-korea-dprk-how-to-get-to-north-korea-2-nk-20170616t183528518z |
| author | sheecko |
| permlink | re-josephd-re-finance2nomad-travel-stories-2-north-korea-dprk-how-to-get-to-north-korea-2-nk-20171216t031650991z |
| title | |
| body | A different place, a different regime, a lot of things to explore from inside.. I went there last November and it was one of the best experiences of my life (even not being an enthusiast of the communism). |
| json metadata | {"tags":["travel"],"app":"steemit/0.1"} |
| Transaction Info | Block #18124887/Trx 7640604b53e0c167fec5b96fccd8281aa8983971 |
View Raw JSON Data
{
"trx_id": "7640604b53e0c167fec5b96fccd8281aa8983971",
"block": 18124887,
"trx_in_block": 21,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-16T03:16:51",
"op": [
"comment",
{
"parent_author": "josephd",
"parent_permlink": "re-finance2nomad-travel-stories-2-north-korea-dprk-how-to-get-to-north-korea-2-nk-20170616t183528518z",
"author": "sheecko",
"permlink": "re-josephd-re-finance2nomad-travel-stories-2-north-korea-dprk-how-to-get-to-north-korea-2-nk-20171216t031650991z",
"title": "",
"body": "A different place, a different regime, a lot of things to explore from inside.. I went there last November and it was one of the best experiences of my life (even not being an enthusiast of the communism).",
"json_metadata": "{\"tags\":[\"travel\"],\"app\":\"steemit/0.1\"}"
}
]
}mindsportsioupvoted (1.00%) @josephd / most-promising-coin-i-ve-seen-after-eth-chainlink2017/12/12 10:15:51
mindsportsioupvoted (1.00%) @josephd / most-promising-coin-i-ve-seen-after-eth-chainlink
2017/12/12 10:15:51
| voter | mindsportsio |
| author | josephd |
| permlink | most-promising-coin-i-ve-seen-after-eth-chainlink |
| weight | 100 (1.00%) |
| Transaction Info | Block #18018109/Trx 180c4b123bcbee59811748eac86cf02618ae7832 |
View Raw JSON Data
{
"trx_id": "180c4b123bcbee59811748eac86cf02618ae7832",
"block": 18018109,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-12T10:15:51",
"op": [
"vote",
{
"voter": "mindsportsio",
"author": "josephd",
"permlink": "most-promising-coin-i-ve-seen-after-eth-chainlink",
"weight": 100
}
]
}mindsportsioupvoted (1.00%) @josephd / most-promising-coin-i-ve-seen-after-eth-chainlink2017/12/12 10:15:45
mindsportsioupvoted (1.00%) @josephd / most-promising-coin-i-ve-seen-after-eth-chainlink
2017/12/12 10:15:45
| voter | mindsportsio |
| author | josephd |
| permlink | most-promising-coin-i-ve-seen-after-eth-chainlink |
| weight | 100 (1.00%) |
| Transaction Info | Block #18018107/Trx b658c8a82df1ad8c5f9d36882d0141116d065bc7 |
View Raw JSON Data
{
"trx_id": "b658c8a82df1ad8c5f9d36882d0141116d065bc7",
"block": 18018107,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-12T10:15:45",
"op": [
"vote",
{
"voter": "mindsportsio",
"author": "josephd",
"permlink": "most-promising-coin-i-ve-seen-after-eth-chainlink",
"weight": 100
}
]
}mindsportsioupvoted (1.00%) @josephd / most-promising-coin-i-ve-seen-after-eth-chainlink2017/12/12 10:15:42
mindsportsioupvoted (1.00%) @josephd / most-promising-coin-i-ve-seen-after-eth-chainlink
2017/12/12 10:15:42
| voter | mindsportsio |
| author | josephd |
| permlink | most-promising-coin-i-ve-seen-after-eth-chainlink |
| weight | 100 (1.00%) |
| Transaction Info | Block #18018106/Trx 8fd65959e29d089bf61776c81eb4ec5d82d7d9f4 |
View Raw JSON Data
{
"trx_id": "8fd65959e29d089bf61776c81eb4ec5d82d7d9f4",
"block": 18018106,
"trx_in_block": 24,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-12T10:15:42",
"op": [
"vote",
{
"voter": "mindsportsio",
"author": "josephd",
"permlink": "most-promising-coin-i-ve-seen-after-eth-chainlink",
"weight": 100
}
]
}mindsportsioupvoted (1.00%) @josephd / most-promising-coin-i-ve-seen-after-eth-chainlink2017/12/12 10:15:42
mindsportsioupvoted (1.00%) @josephd / most-promising-coin-i-ve-seen-after-eth-chainlink
2017/12/12 10:15:42
| voter | mindsportsio |
| author | josephd |
| permlink | most-promising-coin-i-ve-seen-after-eth-chainlink |
| weight | 100 (1.00%) |
| Transaction Info | Block #18018106/Trx 9125b71687638d81d5b4e3209fda06aefe55d8a2 |
View Raw JSON Data
{
"trx_id": "9125b71687638d81d5b4e3209fda06aefe55d8a2",
"block": 18018106,
"trx_in_block": 10,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-12T10:15:42",
"op": [
"vote",
{
"voter": "mindsportsio",
"author": "josephd",
"permlink": "most-promising-coin-i-ve-seen-after-eth-chainlink",
"weight": 100
}
]
}mindsportsioupvoted (1.00%) @josephd / most-promising-coin-i-ve-seen-after-eth-chainlink2017/12/12 10:15:39
mindsportsioupvoted (1.00%) @josephd / most-promising-coin-i-ve-seen-after-eth-chainlink
2017/12/12 10:15:39
| voter | mindsportsio |
| author | josephd |
| permlink | most-promising-coin-i-ve-seen-after-eth-chainlink |
| weight | 100 (1.00%) |
| Transaction Info | Block #18018105/Trx d9238f7d19b4c37916c6973b745f1ad602d3945b |
View Raw JSON Data
{
"trx_id": "d9238f7d19b4c37916c6973b745f1ad602d3945b",
"block": 18018105,
"trx_in_block": 15,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-12T10:15:39",
"op": [
"vote",
{
"voter": "mindsportsio",
"author": "josephd",
"permlink": "most-promising-coin-i-ve-seen-after-eth-chainlink",
"weight": 100
}
]
}mindsportsioupvoted (1.00%) @josephd / most-promising-coin-i-ve-seen-after-eth-chainlink2017/12/12 10:15:39
mindsportsioupvoted (1.00%) @josephd / most-promising-coin-i-ve-seen-after-eth-chainlink
2017/12/12 10:15:39
| voter | mindsportsio |
| author | josephd |
| permlink | most-promising-coin-i-ve-seen-after-eth-chainlink |
| weight | 100 (1.00%) |
| Transaction Info | Block #18018105/Trx ea185d2a07333bc89b9c5146a3760da16d0d3573 |
View Raw JSON Data
{
"trx_id": "ea185d2a07333bc89b9c5146a3760da16d0d3573",
"block": 18018105,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-12T10:15:39",
"op": [
"vote",
{
"voter": "mindsportsio",
"author": "josephd",
"permlink": "most-promising-coin-i-ve-seen-after-eth-chainlink",
"weight": 100
}
]
}josephdreceived 0.044 SBD, 0.034 SP author reward for @josephd / on-bitcoin-private-keys-ownership-transactions-and-more2017/12/09 05:00:42
josephdreceived 0.044 SBD, 0.034 SP author reward for @josephd / on-bitcoin-private-keys-ownership-transactions-and-more
2017/12/09 05:00:42
| author | josephd |
| permlink | on-bitcoin-private-keys-ownership-transactions-and-more |
| sbd payout | 0.044 SBD |
| steem payout | 0.000 STEEM |
| vesting payout | 55.391043 VESTS |
| Transaction Info | Block #17925424/Virtual Operation #5 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 17925424,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 5,
"timestamp": "2017-12-09T05:00:42",
"op": [
"author_reward",
{
"author": "josephd",
"permlink": "on-bitcoin-private-keys-ownership-transactions-and-more",
"sbd_payout": "0.044 SBD",
"steem_payout": "0.000 STEEM",
"vesting_payout": "55.391043 VESTS"
}
]
}2017/12/02 09:45:21
2017/12/02 09:45:21
| voter | kaneseyeonthesky |
| author | josephd |
| permlink | what-should-you-do-if-you-don-t-have-a-ledger-or-trezor-right-now |
| weight | 10000 (100.00%) |
| Transaction Info | Block #17729659/Trx 1242f3f1f508fc07b2fef4763a9cefcd2abaf607 |
View Raw JSON Data
{
"trx_id": "1242f3f1f508fc07b2fef4763a9cefcd2abaf607",
"block": 17729659,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-02T09:45:21",
"op": [
"vote",
{
"voter": "kaneseyeonthesky",
"author": "josephd",
"permlink": "what-should-you-do-if-you-don-t-have-a-ledger-or-trezor-right-now",
"weight": 10000
}
]
}2017/12/02 08:55:03
2017/12/02 08:55:03
| voter | josephd |
| author | lexiconical |
| permlink | re-themarkymark-how-to-milk-the-reward-pool-with-complete-freedom-20171128t174717268z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #17728653/Trx 5ade91c111f0252e4b7e2cca6a6032b19009cd5c |
View Raw JSON Data
{
"trx_id": "5ade91c111f0252e4b7e2cca6a6032b19009cd5c",
"block": 17728653,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-02T08:55:03",
"op": [
"vote",
{
"voter": "josephd",
"author": "lexiconical",
"permlink": "re-themarkymark-how-to-milk-the-reward-pool-with-complete-freedom-20171128t174717268z",
"weight": 10000
}
]
}2017/12/02 08:46:21
2017/12/02 08:46:21
| parent author | acidyo |
| parent permlink | i-need-to-fix-my-sleep-rhythm |
| author | josephd |
| permlink | re-acidyo-i-need-to-fix-my-sleep-rhythm-20171202t084620162z |
| title | |
| body | what alt coins are u buying outside of the top 20 |
| json metadata | {"tags":["blog"],"app":"steemit/0.1"} |
| Transaction Info | Block #17728479/Trx 297196401d52afc8269d1f11eb1d212635150256 |
View Raw JSON Data
{
"trx_id": "297196401d52afc8269d1f11eb1d212635150256",
"block": 17728479,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-02T08:46:21",
"op": [
"comment",
{
"parent_author": "acidyo",
"parent_permlink": "i-need-to-fix-my-sleep-rhythm",
"author": "josephd",
"permlink": "re-acidyo-i-need-to-fix-my-sleep-rhythm-20171202t084620162z",
"title": "",
"body": "what alt coins are u buying outside of the top 20",
"json_metadata": "{\"tags\":[\"blog\"],\"app\":\"steemit/0.1\"}"
}
]
}2017/12/02 08:43:12
2017/12/02 08:43:12
| required auths | [] |
| required posting auths | ["josephd"] |
| id | follow |
| json | ["follow",{"follower":"josephd","following":"bitgeek","what":[]}] |
| Transaction Info | Block #17728416/Trx f91f17573a0a2c59e39cec774751f7fe87d2641a |
View Raw JSON Data
{
"trx_id": "f91f17573a0a2c59e39cec774751f7fe87d2641a",
"block": 17728416,
"trx_in_block": 12,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-02T08:43:12",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"josephd"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"josephd\",\"following\":\"bitgeek\",\"what\":[]}]"
}
]
}josephdclaimed reward balance: 0.021 SBD, 0.030 SP2017/12/02 08:14:48
josephdclaimed reward balance: 0.021 SBD, 0.030 SP
2017/12/02 08:14:48
| account | josephd |
| reward steem | 0.000 STEEM |
| reward sbd | 0.021 SBD |
| reward vests | 49.269084 VESTS |
| Transaction Info | Block #17727848/Trx 1e365fbb7836df9c1f092792d7b49ce70a48c73c |
View Raw JSON Data
{
"trx_id": "1e365fbb7836df9c1f092792d7b49ce70a48c73c",
"block": 17727848,
"trx_in_block": 12,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-02T08:14:48",
"op": [
"claim_reward_balance",
{
"account": "josephd",
"reward_steem": "0.000 STEEM",
"reward_sbd": "0.021 SBD",
"reward_vests": "49.269084 VESTS"
}
]
}2017/12/02 07:03:03
2017/12/02 07:03:03
| voter | crypto-trail |
| author | josephd |
| permlink | what-should-you-do-if-you-don-t-have-a-ledger-or-trezor-right-now |
| weight | 10000 (100.00%) |
| Transaction Info | Block #17726413/Trx 3c4f4e537a275209f5fcfc34b8c63127a8958a7f |
View Raw JSON Data
{
"trx_id": "3c4f4e537a275209f5fcfc34b8c63127a8958a7f",
"block": 17726413,
"trx_in_block": 20,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-02T07:03:03",
"op": [
"vote",
{
"voter": "crypto-trail",
"author": "josephd",
"permlink": "what-should-you-do-if-you-don-t-have-a-ledger-or-trezor-right-now",
"weight": 10000
}
]
}dajohns1420upvoted (31.00%) @josephd / on-bitcoin-private-keys-ownership-transactions-and-more2017/12/02 05:49:48
dajohns1420upvoted (31.00%) @josephd / on-bitcoin-private-keys-ownership-transactions-and-more
2017/12/02 05:49:48
| voter | dajohns1420 |
| author | josephd |
| permlink | on-bitcoin-private-keys-ownership-transactions-and-more |
| weight | 3100 (31.00%) |
| Transaction Info | Block #17724948/Trx c890ea0db4572bd7e6830ce17e23aae77977cf10 |
View Raw JSON Data
{
"trx_id": "c890ea0db4572bd7e6830ce17e23aae77977cf10",
"block": 17724948,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-02T05:49:48",
"op": [
"vote",
{
"voter": "dajohns1420",
"author": "josephd",
"permlink": "on-bitcoin-private-keys-ownership-transactions-and-more",
"weight": 3100
}
]
}kevlar42upvoted (100.00%) @josephd / on-bitcoin-private-keys-ownership-transactions-and-more2017/12/02 05:32:57
kevlar42upvoted (100.00%) @josephd / on-bitcoin-private-keys-ownership-transactions-and-more
2017/12/02 05:32:57
| voter | kevlar42 |
| author | josephd |
| permlink | on-bitcoin-private-keys-ownership-transactions-and-more |
| weight | 10000 (100.00%) |
| Transaction Info | Block #17724611/Trx 7e3792e0d6030ee16cb3dafc8e0913c6f9210594 |
View Raw JSON Data
{
"trx_id": "7e3792e0d6030ee16cb3dafc8e0913c6f9210594",
"block": 17724611,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-02T05:32:57",
"op": [
"vote",
{
"voter": "kevlar42",
"author": "josephd",
"permlink": "on-bitcoin-private-keys-ownership-transactions-and-more",
"weight": 10000
}
]
}tomiscuriousupvoted (3.00%) @josephd / on-bitcoin-private-keys-ownership-transactions-and-more2017/12/02 05:32:36
tomiscuriousupvoted (3.00%) @josephd / on-bitcoin-private-keys-ownership-transactions-and-more
2017/12/02 05:32:36
| voter | tomiscurious |
| author | josephd |
| permlink | on-bitcoin-private-keys-ownership-transactions-and-more |
| weight | 300 (3.00%) |
| Transaction Info | Block #17724604/Trx a78cbe12914c6ca34491d45a69c0b957a7040b5a |
View Raw JSON Data
{
"trx_id": "a78cbe12914c6ca34491d45a69c0b957a7040b5a",
"block": 17724604,
"trx_in_block": 10,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-02T05:32:36",
"op": [
"vote",
{
"voter": "tomiscurious",
"author": "josephd",
"permlink": "on-bitcoin-private-keys-ownership-transactions-and-more",
"weight": 300
}
]
}steffenixupvoted (100.00%) @josephd / on-bitcoin-private-keys-ownership-transactions-and-more2017/12/02 05:30:54
steffenixupvoted (100.00%) @josephd / on-bitcoin-private-keys-ownership-transactions-and-more
2017/12/02 05:30:54
| voter | steffenix |
| author | josephd |
| permlink | on-bitcoin-private-keys-ownership-transactions-and-more |
| weight | 10000 (100.00%) |
| Transaction Info | Block #17724570/Trx b796fe643a8952741822d4524916a59f3028d89c |
View Raw JSON Data
{
"trx_id": "b796fe643a8952741822d4524916a59f3028d89c",
"block": 17724570,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-02T05:30:54",
"op": [
"vote",
{
"voter": "steffenix",
"author": "josephd",
"permlink": "on-bitcoin-private-keys-ownership-transactions-and-more",
"weight": 10000
}
]
}josephdupvoted (100.00%) @josephd / what-should-you-do-if-you-don-t-have-a-ledger-or-trezor-right-now2017/12/02 05:20:48
josephdupvoted (100.00%) @josephd / what-should-you-do-if-you-don-t-have-a-ledger-or-trezor-right-now
2017/12/02 05:20:48
| voter | josephd |
| author | josephd |
| permlink | what-should-you-do-if-you-don-t-have-a-ledger-or-trezor-right-now |
| weight | 10000 (100.00%) |
| Transaction Info | Block #17724368/Trx f4cd9d1d7ec1f29d9b1b4cd1102470f372a6710d |
View Raw JSON Data
{
"trx_id": "f4cd9d1d7ec1f29d9b1b4cd1102470f372a6710d",
"block": 17724368,
"trx_in_block": 10,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-02T05:20:48",
"op": [
"vote",
{
"voter": "josephd",
"author": "josephd",
"permlink": "what-should-you-do-if-you-don-t-have-a-ledger-or-trezor-right-now",
"weight": 10000
}
]
}josephdpublished a new post: what-should-you-do-if-you-don-t-have-a-ledger-or-trezor-right-now2017/12/02 05:11:36
josephdpublished a new post: what-should-you-do-if-you-don-t-have-a-ledger-or-trezor-right-now
2017/12/02 05:11:36
| parent author | |
| parent permlink | crypto |
| author | josephd |
| permlink | what-should-you-do-if-you-don-t-have-a-ledger-or-trezor-right-now |
| title | What should you do if you don't have a ledger or trezor right now? |
| body |  - create a USB bootable Linux tails os , you'll need two drives for the installation process, only one of them will be your bootable drive (other one has some intermediate installation data) - os is really secure, even basic commands like sudo, make, apt-get are disabled by default for security. Extremely difficult to install shit, and you wouldn't want to tweak settings to make installation possible as it's not recommended if security and privacy is your main goal - electrum Wallet is present by default, although you might need to update (run latest version from source) - keep the wallet in "persistent" folder if you want to save the files for next reboot , everything else outside this folder is stored in the ram, and gets erased after powering off - create wallet while offline , you can type the private key seed on a .txt, right click, encrypt it with a passphrase (uses pgp encryption) and send it to yourself While some may argue saving your private key digitally is risky, and that paper is the way to go, but I don't see any way someone can steal your keys if you do it like this. You just have to trust that there are no hardware keyloggers on your machine, or a compromised firmware - both extremely unlikely - you can use my ether wallet offline and do the same for ETH - when you want to see the private key, you can either log in to a tails session, or even decrypt it on windows using CMD (this doesn't create any file with your private key, just displays it in the cmd ; making it pretty safe, although less safer than using tails to view the keys - you could still be screencapped or something by a good enough s/w keylogger) use this command for decryption : gpg --batch --passphrase-fd 0 --armor --decrypt filename.pgp <b> This setup is like building your own hardware wallet, almost as good as ledger or trezor. ALMOST . PS: I'm still getting a Ledger ! </b> |
| json metadata | {"tags":["crypto","security","bitcoin","ethereum"],"image":["https://steemitimages.com/DQmWJEayPywBxMKnxFwiL5ding7GGjim2atVFY5HR7UNjB7/image.png"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #17724184/Trx 0787fa1309533fd4bc8b511251d7ccfd8d30aaf0 |
View Raw JSON Data
{
"trx_id": "0787fa1309533fd4bc8b511251d7ccfd8d30aaf0",
"block": 17724184,
"trx_in_block": 22,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-02T05:11:36",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "crypto",
"author": "josephd",
"permlink": "what-should-you-do-if-you-don-t-have-a-ledger-or-trezor-right-now",
"title": "What should you do if you don't have a ledger or trezor right now?",
"body": "\n\n\n - create a USB bootable Linux tails os , you'll need two drives for the installation process, only one of them will be your bootable drive (other one has some intermediate installation data)\n\n- os is really secure, even basic commands like sudo, make, apt-get are disabled by default for security. Extremely difficult to install shit, and you wouldn't want to tweak settings to make installation possible as it's not recommended if security and privacy is your main goal\n\n- electrum Wallet is present by default, although you might need to update (run latest version from source)\n\n- keep the wallet in \"persistent\" folder if you want to save the files for next reboot , everything else outside this folder is stored in the ram, and gets erased after powering off\n\n- create wallet while offline , you can type the private key seed on a .txt, right click, encrypt it with a passphrase (uses pgp encryption) and send it to yourself\n\nWhile some may argue saving your private key digitally is risky, and that paper is the way to go, but I don't see any way someone can steal your keys if you do it like this. You just have to trust that there are no hardware keyloggers on your machine, or a compromised firmware - both extremely unlikely\n\n- you can use my ether wallet offline and do the same for ETH\n\n- when you want to see the private key, you can either log in to a tails session, or even decrypt it on windows using CMD (this doesn't create any file with your private key, just displays it in the cmd ; making it pretty safe, although less safer than using tails to view the keys - you could still be screencapped or something by a good enough s/w keylogger)\n\nuse this command for decryption : \n\n gpg --batch --passphrase-fd 0 --armor --decrypt filename.pgp\n\n<b> This setup is like building your own hardware wallet, almost as good as ledger or trezor. ALMOST . PS: I'm still getting a Ledger ! </b>",
"json_metadata": "{\"tags\":[\"crypto\",\"security\",\"bitcoin\",\"ethereum\"],\"image\":[\"https://steemitimages.com/DQmWJEayPywBxMKnxFwiL5ding7GGjim2atVFY5HR7UNjB7/image.png\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}josephdpublished a new post: what-should-you-do-if-you-don-t-have-a-ledger-or-trezor-right-now2017/12/02 05:11:06
josephdpublished a new post: what-should-you-do-if-you-don-t-have-a-ledger-or-trezor-right-now
2017/12/02 05:11:06
| parent author | |
| parent permlink | crypto |
| author | josephd |
| permlink | what-should-you-do-if-you-don-t-have-a-ledger-or-trezor-right-now |
| title | what should you do if you don't have a ledger or trezor right now? |
| body | @@ -1745,16 +1745,115 @@ ogger)%0A%0A +use this command for decryption : %0A%0A gpg --batch --passphrase-fd 0 --armor --decrypt filename.pgp%0A%0A %3Cb%3E This |
| json metadata | {"tags":["crypto","security","bitcoin","ethereum"],"image":["https://steemitimages.com/DQmWJEayPywBxMKnxFwiL5ding7GGjim2atVFY5HR7UNjB7/image.png"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #17724174/Trx d7615e309440fee430ba1e536f1f64d402b25abe |
View Raw JSON Data
{
"trx_id": "d7615e309440fee430ba1e536f1f64d402b25abe",
"block": 17724174,
"trx_in_block": 9,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-02T05:11:06",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "crypto",
"author": "josephd",
"permlink": "what-should-you-do-if-you-don-t-have-a-ledger-or-trezor-right-now",
"title": "what should you do if you don't have a ledger or trezor right now?",
"body": "@@ -1745,16 +1745,115 @@\n ogger)%0A%0A\n+use this command for decryption : %0A%0A gpg --batch --passphrase-fd 0 --armor --decrypt filename.pgp%0A%0A\n %3Cb%3E This\n",
"json_metadata": "{\"tags\":[\"crypto\",\"security\",\"bitcoin\",\"ethereum\"],\"image\":[\"https://steemitimages.com/DQmWJEayPywBxMKnxFwiL5ding7GGjim2atVFY5HR7UNjB7/image.png\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}josephdpublished a new post: what-should-you-do-if-you-don-t-have-a-ledger-or-trezor-right-now2017/12/02 05:08:36
josephdpublished a new post: what-should-you-do-if-you-don-t-have-a-ledger-or-trezor-right-now
2017/12/02 05:08:36
| parent author | |
| parent permlink | crypto |
| author | josephd |
| permlink | what-should-you-do-if-you-don-t-have-a-ledger-or-trezor-right-now |
| title | what should you do if you don't have a ledger or trezor right now? |
| body |  - create a USB bootable Linux tails os , you'll need two drives for the installation process, only one of them will be your bootable drive (other one has some intermediate installation data) - os is really secure, even basic commands like sudo, make, apt-get are disabled by default for security. Extremely difficult to install shit, and you wouldn't want to tweak settings to make installation possible as it's not recommended if security and privacy is your main goal - electrum Wallet is present by default, although you might need to update (run latest version from source) - keep the wallet in "persistent" folder if you want to save the files for next reboot , everything else outside this folder is stored in the ram, and gets erased after powering off - create wallet while offline , you can type the private key seed on a .txt, right click, encrypt it with a passphrase (uses pgp encryption) and send it to yourself While some may argue saving your private key digitally is risky, and that paper is the way to go, but I don't see any way someone can steal your keys if you do it like this. You just have to trust that there are no hardware keyloggers on your machine, or a compromised firmware - both extremely unlikely - you can use my ether wallet offline and do the same for ETH - when you want to see the private key, you can either log in to a tails session, or even decrypt it on windows using CMD (this doesn't create any file with your private key, just displays it in the cmd ; making it pretty safe, although less safer than using tails to view the keys - you could still be screencapped or something by a good enough s/w keylogger) <b> This setup is like building your own hardware wallet, almost as good as ledger or trezor. ALMOST . PS: I'm still getting a Ledger ! </b> |
| json metadata | {"tags":["crypto","security","bitcoin","ethereum"],"image":["https://steemitimages.com/DQmWJEayPywBxMKnxFwiL5ding7GGjim2atVFY5HR7UNjB7/image.png"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #17724124/Trx 31f11bd6e784c47f6a914ab893d90a32c364e2e3 |
View Raw JSON Data
{
"trx_id": "31f11bd6e784c47f6a914ab893d90a32c364e2e3",
"block": 17724124,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-02T05:08:36",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "crypto",
"author": "josephd",
"permlink": "what-should-you-do-if-you-don-t-have-a-ledger-or-trezor-right-now",
"title": "what should you do if you don't have a ledger or trezor right now?",
"body": "\n\n\n - create a USB bootable Linux tails os , you'll need two drives for the installation process, only one of them will be your bootable drive (other one has some intermediate installation data)\n\n- os is really secure, even basic commands like sudo, make, apt-get are disabled by default for security. Extremely difficult to install shit, and you wouldn't want to tweak settings to make installation possible as it's not recommended if security and privacy is your main goal\n\n- electrum Wallet is present by default, although you might need to update (run latest version from source)\n\n- keep the wallet in \"persistent\" folder if you want to save the files for next reboot , everything else outside this folder is stored in the ram, and gets erased after powering off\n\n- create wallet while offline , you can type the private key seed on a .txt, right click, encrypt it with a passphrase (uses pgp encryption) and send it to yourself\n\nWhile some may argue saving your private key digitally is risky, and that paper is the way to go, but I don't see any way someone can steal your keys if you do it like this. You just have to trust that there are no hardware keyloggers on your machine, or a compromised firmware - both extremely unlikely\n\n- you can use my ether wallet offline and do the same for ETH\n\n- when you want to see the private key, you can either log in to a tails session, or even decrypt it on windows using CMD (this doesn't create any file with your private key, just displays it in the cmd ; making it pretty safe, although less safer than using tails to view the keys - you could still be screencapped or something by a good enough s/w keylogger)\n\n<b> This setup is like building your own hardware wallet, almost as good as ledger or trezor. ALMOST . PS: I'm still getting a Ledger ! </b>",
"json_metadata": "{\"tags\":[\"crypto\",\"security\",\"bitcoin\",\"ethereum\"],\"image\":[\"https://steemitimages.com/DQmWJEayPywBxMKnxFwiL5ding7GGjim2atVFY5HR7UNjB7/image.png\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}2017/12/02 05:04:24
2017/12/02 05:04:24
| parent author | cheetah |
| parent permlink | cheetah-re-josephdon-bitcoin-private-keys-ownership-transactions-and-more |
| author | josephd |
| permlink | re-cheetah-cheetah-re-josephdon-bitcoin-private-keys-ownership-transactions-and-more-20171202t050425679z |
| title | |
| body | i have evaluated this blogpost myself and deemed it worthy of being read |
| json metadata | {"tags":["crypto"],"app":"steemit/0.1"} |
| Transaction Info | Block #17724040/Trx bce68a752dbeda4a47bdd5a5fc5876bc057be769 |
View Raw JSON Data
{
"trx_id": "bce68a752dbeda4a47bdd5a5fc5876bc057be769",
"block": 17724040,
"trx_in_block": 19,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-02T05:04:24",
"op": [
"comment",
{
"parent_author": "cheetah",
"parent_permlink": "cheetah-re-josephdon-bitcoin-private-keys-ownership-transactions-and-more",
"author": "josephd",
"permlink": "re-cheetah-cheetah-re-josephdon-bitcoin-private-keys-ownership-transactions-and-more-20171202t050425679z",
"title": "",
"body": "i have evaluated this blogpost myself and deemed it worthy of being read",
"json_metadata": "{\"tags\":[\"crypto\"],\"app\":\"steemit/0.1\"}"
}
]
}2017/12/02 05:02:15
2017/12/02 05:02:15
| parent author | cheetah |
| parent permlink | cheetah-re-josephdon-bitcoin-private-keys-ownership-transactions-and-more |
| author | josephd |
| permlink | re-cheetah-cheetah-re-josephdon-bitcoin-private-keys-ownership-transactions-and-more-20171202t050215093z |
| title | |
| body | yes |
| json metadata | {"tags":["crypto"],"app":"steemit/0.1"} |
| Transaction Info | Block #17723997/Trx aa7d2d9c16a98f98a04915691a7887c1fb29c200 |
View Raw JSON Data
{
"trx_id": "aa7d2d9c16a98f98a04915691a7887c1fb29c200",
"block": 17723997,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-02T05:02:15",
"op": [
"comment",
{
"parent_author": "cheetah",
"parent_permlink": "cheetah-re-josephdon-bitcoin-private-keys-ownership-transactions-and-more",
"author": "josephd",
"permlink": "re-cheetah-cheetah-re-josephdon-bitcoin-private-keys-ownership-transactions-and-more-20171202t050215093z",
"title": "",
"body": "yes",
"json_metadata": "{\"tags\":[\"crypto\"],\"app\":\"steemit/0.1\"}"
}
]
}josephdpublished a new post: on-bitcoin-private-keys-ownership-transactions-and-more2017/12/02 05:01:42
josephdpublished a new post: on-bitcoin-private-keys-ownership-transactions-and-more
2017/12/02 05:01:42
| parent author | |
| parent permlink | crypto |
| author | josephd |
| permlink | on-bitcoin-private-keys-ownership-transactions-and-more |
| title | On Bitcoin private keys, ownership, transactions and more |
| body |  Private keys have been an integral component of Bitcoin since its first description in 2008. Wallet software often attempts to shield users from the need to understand what private keys are and how they work. Even so, most users eventually come face to face with private keys, too often with unpleasant results. A basic understanding of private keys can help prevent loss of funds and other mishaps, but it can also offer useful insights into how Bitcoin works. This guide outlines the most important private key concepts for effectively using Bitcoin. Bitcoin: A Secure Messaging System Although Bitcoin is best known as a payment system, underneath it all runs a secure messaging system built on the Internet. Instead of relaying emails, texts, or web pages, the Bitcoin network processes value-transfer messages called transactions. Private keys play a central role in verifying these messages, identifying senders and receivers, and in securing the network. An example helps illustrate the problems that private keys solve. Imagine Alice wants to pay Bob 10 bitcoin (BTC). She begins by creating a transaction identifying Bob as the payee and 10 BTC as the amount to be transferred. Alice then broadcasts this transaction to all users of the Bitcoin network. Simple Transaction. Alice’s transaction paying Bob 10 bitcoin. As it stands, Alice has no way to identify herself or Bob, nor does she have any assurance the transaction won’t be forged or tampered with. In using this system, Alice faces two fundamental problems. First, she needs a way to identify both herself and Bob in the transaction. Alice can’t employ a central authority such as a government registry or email provider because that would create a central point of control and failure — the very thing Bitcoin was created to eliminate. Second, Alice needs a way to prevent others from changing her transaction and forging transactions in her name. Bitcoin solves these problems through a system called public key cryptography. This system uses two pieces of information to authenticate messages. A public key identifies a sender or recipient, and can be distributed to others. A private key is used together with the public key to create an unforgeable message signature. The private key must be kept secret. Public and private keys are mathematically linked. Alice Signs Transaction. Alice signs a transaction to Bob with her private key. Bob will later use Alice’s public key to verify Alice’s signature. With this overview in mind, here are six things about private keys to keep in mind as you use Bitcoin. <h2> 1. A Private Key is Just a Number </h2> A Bitcoin private key is simply an integer between one and about 1077. This may not seem like much of a selection, but for practical purposes it’s essentially infinite. If you could process one trillion private keys per second, it would take more than one million times the age of the universe to count them all. Even worse, just enumerating these keys would consume more than the total energy output of the sun for 32 years. This vast keyspace plays a fundamental role in securing the Bitcoin network. Because private keys contain many digits when expressed as decimal numbers, an alternative called Wallet Import Format (WIF) has been devised. This format begins with the number “5” and contains a sequence of letters and numbers. For example, here’s a private key represented in WIF format: 5KJvsngHeMpm884wtkJNzQGaCEui9HJBGFsvd3VyK5qMZXj3hS <h2> 2. Transactions are Messages Signed with a Private Key </h2> To prevent forgery, Bitcoin requires that each transaction bear a digital signature. This signature, like a private key, is just a number selected from a very large range. Wallet software generates a signature by mathematically processing a transaction together with the correct private key. This system works because anyone with a transaction and its signature can verify the authenticity of a message. However, a transaction signature is practically impossible to fake. The only way to produce a valid signature for a particular transaction is to use the correct private key. Two transactions from Alice to Bob. The first transfers 10 BTC, and the second transfers 2 BTC. The same private key leads to a unique, unguessable signature for each transaction. Unlike a physical signature you might write on a check, a transaction signature changes if the transaction changes even slightly. The way the signature will change is unpredictable, ensuring that only a person in possession of a private key can provide the correct signature. <h2> 3. Anyone Who Knows Your Private Key Can Steal Your Funds </h2> Any transaction bearing a valid signature will be accepted by the Bitcoin network. At the same time, any person in possession of a private key can create a valid transaction. These two facts taken together mean that someone knowing only your private key can steal from you. Many avenues are open to thieves who steal private keys. Two of the most popular are storage media and communications channels. For this reason, extreme caution must be taken whenever storing or transmitting private keys. Software wallets usually store private keys in a “wallet file” on the main hard drive. Wallets often place this file in a standard, well-known directory, making it an ideal target bitcoin-specific malware. To counter this threat, software wallets offer an option to encrypt the wallet file. Any attacker gaining access to your wallet file would then need to decrypt it. The difficulty of doing so depends on the quality of the encryption and strength of the password being used. Wallet files can be encrypted on many software wallets by adding a password. Although wallet backups are a good idea, they can potentially leak private keys. For example, it may be tempting to save a backup of your software wallet to a cloud storage service such as Dropbox. However, anyone capable of viewing this backup online (which could be a surprisingly long list of people) would be in a position to steal some or all of your funds. A similar problem could arise through emailing backups to yourself or leaving a paper wallet around the house. Encryption can reduce the risk, but not eliminate it altogether. Preventing the accidental release of private keys is the main purpose of “cold storage.” For more information, see A Gentle Introduction to Bitcoin Cold Storage. <h2> 4. Addresses are Derived from Public Keys, Which are Themselves Derived from Private Keys </h2> A Bitcoin public key is obtained by applying a well-defined set of mathematical operations, defined through Elliptic Curve Cryptography (ECC), to a private key. Like a private key, a public key is simply a very large number. SVG Image Private Key to Address. A private key, which is just a number such as 42, can be transformed mathematically into a public key. A public key is then transformed into an address. Each step is irreversible. The relationship between private keys and public keys is an example of a mathematical trapdoor - a function that’s easy to perform in one direction, but practically impossible to perform in the opposite direction. This unidirectionality lies at the center of Bitcoin’s security model. Just as private keys can be shortened to make them more usable with displays and keyboards, so too can public keys. An address results from applying a multi-step transformation to a public key. This produces a string of text and digits, usually starting with the number “1”. Notice that no network is needed at any point in the generation of a private key or the corresponding address. Every computer on the Bitcoin network knows about the mathematical relationship between public and private keys. This enables each participant to select private keys and sign transactions independently of the Bitcoin network. The enormous private keyspace ensures that any properly-selected key will be unique. <h2>5. Security Depends on Choosing a Good Private Key </h2> Knowledge of a private key is the only verification needed to spend funds from a Bitcoin address. Private keys should therefore be kept secret. However, careless selection of a private key can lead to theft just as easily as its accidental release. For example, imagine that we want to use a private key that’s easy to remember. The number 1 is both easy to remember and a valid Bitcoin private key. But how secure would it be? The private key 1 generates this address: 1EHNa6Q4Jz2uvNExL497mE43ikXhwF6kZm If you follow the link, you’ll notice that the address has already been involved in over 1,000 transactions for a total of over 7 BTC within the last few years. If you wanted, you could easily spend any available funds at this address because the private key is known to you. Now imagine you’re a thief determined to steal bitcoin. One strategy might be to compile a list of easy-to-remember private keys. Next, generate the addresses for these keys and monitor the Bitcoin network for incoming payments to one of them. When one arrives, immediately sign a transaction moving the funds to another address you control. Contrast the ease of this scheme with a situation in which a private key was chosen by a perfect random number generator. With no clue what the key might be, brute force iteration would be the only option. As we’ve already seen, carrying out this plan is physically impossible. What would happen if the random number generator were not quite random? For example, what if all output private keys were clustered about a constant value within a narrow range? Private Keyspace. Random private key distribution (left) versus one that is clustered (right). The clustered distribution limits the search space, favoring an attacker. Any attacker aware of such a defect could drastically reduce the necessary search space. Under the right conditions, it would become practical to monitor all of the addresses based on the faulty random number generator and steal funds from any one of them at will. The need to select a good private key becomes especially important with brain wallets. One method to create a brain wallet starts with a passphrase such as “to be or not to be”, then applies a mathematical function to convert this text to a private key. Applying the most popular conversion algorithm (SHA-256) to this passphrase generates the address: 1J3m4nneGFppRjx6qv92qyz7EsMVdLfr8R If you go to blockexplorerer and search this address, you can see that this address was used recently to store funds, which were immediately withdrawn. Unfortunately, it’s not always easy to tell what qualifies as an insecure brain wallet passphrase and what doesn’t. Attackers can exploit this uncertainty and the inexperience of new users to steal funds. For example, a thief might compile an enormous database of common phrases and passwords. Such a database might number in the trillions of entries or more, but would still be searchable in its entirety with little computational effort. Compare this situation to the one with website passwords. If you register for a web service using a password someone else happens to have chosen, you don’t take over their account because your username must be unique. Bitcoin private keys are different in that they serve the dual role of user identification (via address generation) and authentication (via digital signatures). Secure private keys are generated with a high degree of unpredictability so they can’t be guessed before or after the fact. <h2>6. Private Keys are (Somewhat) Portable </h2> For the most part, wallet software hides the process of generating, using, and storing private keys. However, private keys can become visible from time to time. When this happens, understanding private keys and how they interact with your specific software becomes important. Paper wallets present the most common route by which private keys show up outside of software wallets. Although they come in a multitude of formats, the essential feature of any paper wallet is a printed private key. Support for using externally-generated private keys varies greatly across wallet applications. For example, private keys imported into Armory are not preserved in future backup recoveries using the most common and recommended procedure. Likewise, importing private keys into MultiBit changes the behavior of that wallet with respect to change addresses. Should one wallet application begin to malfunction, its private keys can be imported into another application. This rescue procedure provides the second main route through which private keys become visible to end users. A closely-related procedure consists of restoring the state of a software wallet through a backup file. Before losing funds due to preventable mistakes, understand how your software treats externally-created private keys — before importing them. Regardless of the specific wallet application being use, private keys kept or maintained outside of a software wallet need to be handled with care to prevent loss and theft. Conclusions Bitcoin can be thought of as an open messaging system secured by public key cryptography. In contrast to other systems protected by username and password logins, Bitcoin is secured through digital message signatures created with a unique private key. This single point of access places a very high value on the secure generation, use, and storage of private keys. |
| json metadata | {"tags":["crypto","ethereum","bitcoin"],"image":["https://steemitimages.com/DQmP2qryJKW3wKt26VqqcZ8FnybbQo2Mmnut2pCr7NR6cfe/image.png"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #17723986/Trx d6f1ab63b38220b21e62f5983cdc0591b813abdf |
View Raw JSON Data
{
"trx_id": "d6f1ab63b38220b21e62f5983cdc0591b813abdf",
"block": 17723986,
"trx_in_block": 9,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-02T05:01:42",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "crypto",
"author": "josephd",
"permlink": "on-bitcoin-private-keys-ownership-transactions-and-more",
"title": "On Bitcoin private keys, ownership, transactions and more",
"body": "\n\nPrivate keys have been an integral component of Bitcoin since its first description in 2008. Wallet software often attempts to shield users from the need to understand what private keys are and how they work. Even so, most users eventually come face to face with private keys, too often with unpleasant results.\n\nA basic understanding of private keys can help prevent loss of funds and other mishaps, but it can also offer useful insights into how Bitcoin works. This guide outlines the most important private key concepts for effectively using Bitcoin.\nBitcoin: A Secure Messaging System\n\nAlthough Bitcoin is best known as a payment system, underneath it all runs a secure messaging system built on the Internet. Instead of relaying emails, texts, or web pages, the Bitcoin network processes value-transfer messages called transactions. Private keys play a central role in verifying these messages, identifying senders and receivers, and in securing the network.\n\nAn example helps illustrate the problems that private keys solve. Imagine Alice wants to pay Bob 10 bitcoin (BTC). She begins by creating a transaction identifying Bob as the payee and 10 BTC as the amount to be transferred. Alice then broadcasts this transaction to all users of the Bitcoin network.\n\nSimple Transaction. Alice’s transaction paying Bob 10 bitcoin. As it stands, Alice has no way to identify herself or Bob, nor does she have any assurance the transaction won’t be forged or tampered with.\n\nIn using this system, Alice faces two fundamental problems. First, she needs a way to identify both herself and Bob in the transaction. Alice can’t employ a central authority such as a government registry or email provider because that would create a central point of control and failure — the very thing Bitcoin was created to eliminate. Second, Alice needs a way to prevent others from changing her transaction and forging transactions in her name.\n\nBitcoin solves these problems through a system called public key cryptography. This system uses two pieces of information to authenticate messages. A public key identifies a sender or recipient, and can be distributed to others. A private key is used together with the public key to create an unforgeable message signature. The private key must be kept secret. Public and private keys are mathematically linked.\n\nAlice Signs Transaction. Alice signs a transaction to Bob with her private key. Bob will later use Alice’s public key to verify Alice’s signature.\n\nWith this overview in mind, here are six things about private keys to keep in mind as you use Bitcoin.\n\n<h2> 1. A Private Key is Just a Number </h2>\n\nA Bitcoin private key is simply an integer between one and about 1077. This may not seem like much of a selection, but for practical purposes it’s essentially infinite.\n\nIf you could process one trillion private keys per second, it would take more than one million times the age of the universe to count them all. Even worse, just enumerating these keys would consume more than the total energy output of the sun for 32 years. This vast keyspace plays a fundamental role in securing the Bitcoin network.\n\nBecause private keys contain many digits when expressed as decimal numbers, an alternative called Wallet Import Format (WIF) has been devised. This format begins with the number “5” and contains a sequence of letters and numbers. For example, here’s a private key represented in WIF format:\n\n5KJvsngHeMpm884wtkJNzQGaCEui9HJBGFsvd3VyK5qMZXj3hS\n\n<h2> 2. Transactions are Messages Signed with a Private Key </h2>\n\nTo prevent forgery, Bitcoin requires that each transaction bear a digital signature. This signature, like a private key, is just a number selected from a very large range. Wallet software generates a signature by mathematically processing a transaction together with the correct private key.\n\nThis system works because anyone with a transaction and its signature can verify the authenticity of a message. However, a transaction signature is practically impossible to fake. The only way to produce a valid signature for a particular transaction is to use the correct private key.\n\nTwo transactions from Alice to Bob. The first transfers 10 BTC, and the second transfers 2 BTC. The same private key leads to a unique, unguessable signature for each transaction.\n\nUnlike a physical signature you might write on a check, a transaction signature changes if the transaction changes even slightly. The way the signature will change is unpredictable, ensuring that only a person in possession of a private key can provide the correct signature.\n\n<h2> 3. Anyone Who Knows Your Private Key Can Steal Your Funds </h2>\n\nAny transaction bearing a valid signature will be accepted by the Bitcoin network. At the same time, any person in possession of a private key can create a valid transaction. These two facts taken together mean that someone knowing only your private key can steal from you.\n\nMany avenues are open to thieves who steal private keys. Two of the most popular are storage media and communications channels. For this reason, extreme caution must be taken whenever storing or transmitting private keys.\n\nSoftware wallets usually store private keys in a “wallet file” on the main hard drive. Wallets often place this file in a standard, well-known directory, making it an ideal target bitcoin-specific malware.\n\nTo counter this threat, software wallets offer an option to encrypt the wallet file. Any attacker gaining access to your wallet file would then need to decrypt it. The difficulty of doing so depends on the quality of the encryption and strength of the password being used. Wallet files can be encrypted on many software wallets by adding a password.\n\n\nAlthough wallet backups are a good idea, they can potentially leak private keys. For example, it may be tempting to save a backup of your software wallet to a cloud storage service such as Dropbox. However, anyone capable of viewing this backup online (which could be a surprisingly long list of people) would be in a position to steal some or all of your funds. A similar problem could arise through emailing backups to yourself or leaving a paper wallet around the house. Encryption can reduce the risk, but not eliminate it altogether.\n\nPreventing the accidental release of private keys is the main purpose of “cold storage.” For more information, see A Gentle Introduction to Bitcoin Cold Storage.\n\n<h2> 4. Addresses are Derived from Public Keys, Which are Themselves Derived from Private Keys </h2>\n\nA Bitcoin public key is obtained by applying a well-defined set of mathematical operations, defined through Elliptic Curve Cryptography (ECC), to a private key. Like a private key, a public key is simply a very large number.\nSVG Image\nPrivate Key to Address. A private key, which is just a number such as 42, can be transformed mathematically into a public key. A public key is then transformed into an address. Each step is irreversible.\n\nThe relationship between private keys and public keys is an example of a mathematical trapdoor - a function that’s easy to perform in one direction, but practically impossible to perform in the opposite direction. This unidirectionality lies at the center of Bitcoin’s security model.\n\nJust as private keys can be shortened to make them more usable with displays and keyboards, so too can public keys. An address results from applying a multi-step transformation to a public key. This produces a string of text and digits, usually starting with the number “1”.\n\nNotice that no network is needed at any point in the generation of a private key or the corresponding address. Every computer on the Bitcoin network knows about the mathematical relationship between public and private keys. This enables each participant to select private keys and sign transactions independently of the Bitcoin network. The enormous private keyspace ensures that any properly-selected key will be unique.\n\n<h2>5. Security Depends on Choosing a Good Private Key </h2>\n\nKnowledge of a private key is the only verification needed to spend funds from a Bitcoin address. Private keys should therefore be kept secret. However, careless selection of a private key can lead to theft just as easily as its accidental release.\n\nFor example, imagine that we want to use a private key that’s easy to remember. The number 1 is both easy to remember and a valid Bitcoin private key. But how secure would it be?\n\nThe private key 1 generates this address:\n\n1EHNa6Q4Jz2uvNExL497mE43ikXhwF6kZm\n\nIf you follow the link, you’ll notice that the address has already been involved in over 1,000 transactions for a total of over 7 BTC within the last few years. If you wanted, you could easily spend any available funds at this address because the private key is known to you.\n\nNow imagine you’re a thief determined to steal bitcoin. One strategy might be to compile a list of easy-to-remember private keys. Next, generate the addresses for these keys and monitor the Bitcoin network for incoming payments to one of them. When one arrives, immediately sign a transaction moving the funds to another address you control.\n\nContrast the ease of this scheme with a situation in which a private key was chosen by a perfect random number generator. With no clue what the key might be, brute force iteration would be the only option. As we’ve already seen, carrying out this plan is physically impossible.\n\nWhat would happen if the random number generator were not quite random? For example, what if all output private keys were clustered about a constant value within a narrow range?\n\nPrivate Keyspace. Random private key distribution (left) versus one that is clustered (right). The clustered distribution limits the search space, favoring an attacker.\n\nAny attacker aware of such a defect could drastically reduce the necessary search space. Under the right conditions, it would become practical to monitor all of the addresses based on the faulty random number generator and steal funds from any one of them at will.\n\nThe need to select a good private key becomes especially important with brain wallets. One method to create a brain wallet starts with a passphrase such as “to be or not to be”, then applies a mathematical function to convert this text to a private key. Applying the most popular conversion algorithm (SHA-256) to this passphrase generates the address:\n\n1J3m4nneGFppRjx6qv92qyz7EsMVdLfr8R\n\nIf you go to blockexplorerer and search this address, you can see that this address was used recently to store funds, which were immediately withdrawn.\n\nUnfortunately, it’s not always easy to tell what qualifies as an insecure brain wallet passphrase and what doesn’t. Attackers can exploit this uncertainty and the inexperience of new users to steal funds. For example, a thief might compile an enormous database of common phrases and passwords. Such a database might number in the trillions of entries or more, but would still be searchable in its entirety with little computational effort.\n\nCompare this situation to the one with website passwords. If you register for a web service using a password someone else happens to have chosen, you don’t take over their account because your username must be unique. Bitcoin private keys are different in that they serve the dual role of user identification (via address generation) and authentication (via digital signatures).\n\nSecure private keys are generated with a high degree of unpredictability so they can’t be guessed before or after the fact.\n\n<h2>6. Private Keys are (Somewhat) Portable </h2>\n\nFor the most part, wallet software hides the process of generating, using, and storing private keys. However, private keys can become visible from time to time. When this happens, understanding private keys and how they interact with your specific software becomes important.\n\nPaper wallets present the most common route by which private keys show up outside of software wallets. Although they come in a multitude of formats, the essential feature of any paper wallet is a printed private key.\n\nSupport for using externally-generated private keys varies greatly across wallet applications. For example, private keys imported into Armory are not preserved in future backup recoveries using the most common and recommended procedure. Likewise, importing private keys into MultiBit changes the behavior of that wallet with respect to change addresses.\n\nShould one wallet application begin to malfunction, its private keys can be imported into another application. This rescue procedure provides the second main route through which private keys become visible to end users. A closely-related procedure consists of restoring the state of a software wallet through a backup file.\n\nBefore losing funds due to preventable mistakes, understand how your software treats externally-created private keys — before importing them. Regardless of the specific wallet application being use, private keys kept or maintained outside of a software wallet need to be handled with care to prevent loss and theft.\nConclusions\n\nBitcoin can be thought of as an open messaging system secured by public key cryptography. In contrast to other systems protected by username and password logins, Bitcoin is secured through digital message signatures created with a unique private key. This single point of access places a very high value on the secure generation, use, and storage of private keys.",
"json_metadata": "{\"tags\":[\"crypto\",\"ethereum\",\"bitcoin\"],\"image\":[\"https://steemitimages.com/DQmP2qryJKW3wKt26VqqcZ8FnybbQo2Mmnut2pCr7NR6cfe/image.png\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}josephdupvoted (100.00%) @josephd / on-bitcoin-private-keys-ownership-transactions-and-more2017/12/02 05:01:18
josephdupvoted (100.00%) @josephd / on-bitcoin-private-keys-ownership-transactions-and-more
2017/12/02 05:01:18
| voter | josephd |
| author | josephd |
| permlink | on-bitcoin-private-keys-ownership-transactions-and-more |
| weight | 10000 (100.00%) |
| Transaction Info | Block #17723978/Trx 77aa091970aab3b5566173789e2a2defcf252b26 |
View Raw JSON Data
{
"trx_id": "77aa091970aab3b5566173789e2a2defcf252b26",
"block": 17723978,
"trx_in_block": 9,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-02T05:01:18",
"op": [
"vote",
{
"voter": "josephd",
"author": "josephd",
"permlink": "on-bitcoin-private-keys-ownership-transactions-and-more",
"weight": 10000
}
]
}2017/12/02 05:01:06
2017/12/02 05:01:06
| parent author | josephd |
| parent permlink | on-bitcoin-private-keys-ownership-transactions-and-more |
| author | cheetah |
| permlink | cheetah-re-josephdon-bitcoin-private-keys-ownership-transactions-and-more |
| title | |
| body | Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in: https://bitzuma.com/posts/six-things-bitcoin-users-should-know-about-private-keys/ |
| json metadata | |
| Transaction Info | Block #17723974/Trx 1ae2b53dfb455c0b6d984b791e4f50d28da222d0 |
View Raw JSON Data
{
"trx_id": "1ae2b53dfb455c0b6d984b791e4f50d28da222d0",
"block": 17723974,
"trx_in_block": 10,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-02T05:01:06",
"op": [
"comment",
{
"parent_author": "josephd",
"parent_permlink": "on-bitcoin-private-keys-ownership-transactions-and-more",
"author": "cheetah",
"permlink": "cheetah-re-josephdon-bitcoin-private-keys-ownership-transactions-and-more",
"title": "",
"body": "Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in:\nhttps://bitzuma.com/posts/six-things-bitcoin-users-should-know-about-private-keys/",
"json_metadata": ""
}
]
}cheetahupvoted (0.08%) @josephd / on-bitcoin-private-keys-ownership-transactions-and-more2017/12/02 05:01:03
cheetahupvoted (0.08%) @josephd / on-bitcoin-private-keys-ownership-transactions-and-more
2017/12/02 05:01:03
| voter | cheetah |
| author | josephd |
| permlink | on-bitcoin-private-keys-ownership-transactions-and-more |
| weight | 8 (0.08%) |
| Transaction Info | Block #17723973/Trx 4558cae40966ed0d95b9e5c293701aa11aa5bff2 |
View Raw JSON Data
{
"trx_id": "4558cae40966ed0d95b9e5c293701aa11aa5bff2",
"block": 17723973,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-02T05:01:03",
"op": [
"vote",
{
"voter": "cheetah",
"author": "josephd",
"permlink": "on-bitcoin-private-keys-ownership-transactions-and-more",
"weight": 8
}
]
}josephdpublished a new post: on-bitcoin-private-keys-ownership-transactions-and-more2017/12/02 05:00:42
josephdpublished a new post: on-bitcoin-private-keys-ownership-transactions-and-more
2017/12/02 05:00:42
| parent author | |
| parent permlink | crypto |
| author | josephd |
| permlink | on-bitcoin-private-keys-ownership-transactions-and-more |
| title | On Bitcoin private keys, ownership, transactions and more |
| body |  Private keys have been an integral component of Bitcoin since its first description in 2008. Wallet software often attempts to shield users from the need to understand what private keys are and how they work. Even so, most users eventually come face to face with private keys, too often with unpleasant results. A basic understanding of private keys can help prevent loss of funds and other mishaps, but it can also offer useful insights into how Bitcoin works. This guide outlines the most important private key concepts for effectively using Bitcoin. Bitcoin: A Secure Messaging System Although Bitcoin is best known as a payment system, underneath it all runs a secure messaging system built on the Internet. Instead of relaying emails, texts, or web pages, the Bitcoin network processes value-transfer messages called transactions. Private keys play a central role in verifying these messages, identifying senders and receivers, and in securing the network. An example helps illustrate the problems that private keys solve. Imagine Alice wants to pay Bob 10 bitcoin (BTC). She begins by creating a transaction identifying Bob as the payee and 10 BTC as the amount to be transferred. Alice then broadcasts this transaction to all users of the Bitcoin network. Simple Transaction. Alice’s transaction paying Bob 10 bitcoin. As it stands, Alice has no way to identify herself or Bob, nor does she have any assurance the transaction won’t be forged or tampered with. In using this system, Alice faces two fundamental problems. First, she needs a way to identify both herself and Bob in the transaction. Alice can’t employ a central authority such as a government registry or email provider because that would create a central point of control and failure — the very thing Bitcoin was created to eliminate. Second, Alice needs a way to prevent others from changing her transaction and forging transactions in her name. Bitcoin solves these problems through a system called public key cryptography. This system uses two pieces of information to authenticate messages. A public key identifies a sender or recipient, and can be distributed to others. A private key is used together with the public key to create an unforgeable message signature. The private key must be kept secret. Public and private keys are mathematically linked. Alice Signs Transaction. Alice signs a transaction to Bob with her private key. Bob will later use Alice’s public key to verify Alice’s signature. With this overview in mind, here are six things about private keys to keep in mind as you use Bitcoin. <h2> 1. A Private Key is Just a Number </h2> A Bitcoin private key is simply an integer between one and about 1077. This may not seem like much of a selection, but for practical purposes it’s essentially infinite. If you could process one trillion private keys per second, it would take more than one million times the age of the universe to count them all. Even worse, just enumerating these keys would consume more than the total energy output of the sun for 32 years. This vast keyspace plays a fundamental role in securing the Bitcoin network. Because private keys contain many digits when expressed as decimal numbers, an alternative called Wallet Import Format (WIF) has been devised. This format begins with the number “5” and contains a sequence of letters and numbers. For example, here’s a private key represented in WIF format: 5KJvsngHeMpm884wtkJNzQGaCEui9HJBGFsvd3VyK5qMZXj3hS <h2> 2. Transactions are Messages Signed with a Private Key </h2> To prevent forgery, Bitcoin requires that each transaction bear a digital signature. This signature, like a private key, is just a number selected from a very large range. Wallet software generates a signature by mathematically processing a transaction together with the correct private key. This system works because anyone with a transaction and its signature can verify the authenticity of a message. However, a transaction signature is practically impossible to fake. The only way to produce a valid signature for a particular transaction is to use the correct private key. Two transactions from Alice to Bob. The first transfers 10 BTC, and the second transfers 2 BTC. The same private key leads to a unique, unguessable signature for each transaction. Unlike a physical signature you might write on a check, a transaction signature changes if the transaction changes even slightly. The way the signature will change is unpredictable, ensuring that only a person in possession of a private key can provide the correct signature. <h2> 3. Anyone Who Knows Your Private Key Can Steal Your Funds </h2> Any transaction bearing a valid signature will be accepted by the Bitcoin network. At the same time, any person in possession of a private key can create a valid transaction. These two facts taken together mean that someone knowing only your private key can steal from you. Many avenues are open to thieves who steal private keys. Two of the most popular are storage media and communications channels. For this reason, extreme caution must be taken whenever storing or transmitting private keys. Software wallets usually store private keys in a “wallet file” on the main hard drive. Wallets often place this file in a standard, well-known directory, making it an ideal target bitcoin-specific malware. To counter this threat, software wallets offer an option to encrypt the wallet file. Any attacker gaining access to your wallet file would then need to decrypt it. The difficulty of doing so depends on the quality of the encryption and strength of the password being used. Wallet files can be encrypted on many software wallets by adding a password. Although wallet backups are a good idea, they can potentially leak private keys. For example, it may be tempting to save a backup of your software wallet to a cloud storage service such as Dropbox. However, anyone capable of viewing this backup online (which could be a surprisingly long list of people) would be in a position to steal some or all of your funds. A similar problem could arise through emailing backups to yourself or leaving a paper wallet around the house. Encryption can reduce the risk, but not eliminate it altogether. Preventing the accidental release of private keys is the main purpose of “cold storage.” For more information, see A Gentle Introduction to Bitcoin Cold Storage. <h2> 4. Addresses are Derived from Public Keys, Which are Themselves Derived from Private Keys </h2> A Bitcoin public key is obtained by applying a well-defined set of mathematical operations, defined through Elliptic Curve Cryptography (ECC), to a private key. Like a private key, a public key is simply a very large number. SVG Image Private Key to Address. A private key, which is just a number such as 42, can be transformed mathematically into a public key. A public key is then transformed into an address. Each step is irreversible. The relationship between private keys and public keys is an example of a mathematical trapdoor - a function that’s easy to perform in one direction, but practically impossible to perform in the opposite direction. This unidirectionality lies at the center of Bitcoin’s security model. Just as private keys can be shortened to make them more usable with displays and keyboards, so too can public keys. An address results from applying a multi-step transformation to a public key. This produces a string of text and digits, usually starting with the number “1”. Notice that no network is needed at any point in the generation of a private key or the corresponding address. Every computer on the Bitcoin network knows about the mathematical relationship between public and private keys. This enables each participant to select private keys and sign transactions independently of the Bitcoin network. The enormous private keyspace ensures that any properly-selected key will be unique. <h2>5. Security Depends on Choosing a Good Private Key </h2> Knowledge of a private key is the only verification needed to spend funds from a Bitcoin address. Private keys should therefore be kept secret. However, careless selection of a private key can lead to theft just as easily as its accidental release. For example, imagine that we want to use a private key that’s easy to remember. The number 1 is both easy to remember and a valid Bitcoin private key. But how secure would it be? The private key 1 generates this address: 1EHNa6Q4Jz2uvNExL497mE43ikXhwF6kZm If you follow the link, you’ll notice that the address has already been involved in over 1,000 transactions for a total of over 7 BTC within the last few years. If you wanted, you could easily spend any available funds at this address because the private key is known to you. Now imagine you’re a thief determined to steal bitcoin. One strategy might be to compile a list of easy-to-remember private keys. Next, generate the addresses for these keys and monitor the Bitcoin network for incoming payments to one of them. When one arrives, immediately sign a transaction moving the funds to another address you control. Contrast the ease of this scheme with a situation in which a private key was chosen by a perfect random number generator. With no clue what the key might be, brute force iteration would be the only option. As we’ve already seen, carrying out this plan is physically impossible. What would happen if the random number generator were not quite random? For example, what if all output private keys were clustered about a constant value within a narrow range? Private Keyspace. Random private key distribution (left) versus one that is clustered (right). The clustered distribution limits the search space, favoring an attacker. Any attacker aware of such a defect could drastically reduce the necessary search space. Under the right conditions, it would become practical to monitor all of the addresses based on the faulty random number generator and steal funds from any one of them at will. The need to select a good private key becomes especially important with brain wallets. One method to create a brain wallet starts with a passphrase such as “to be or not to be”, then applies a mathematical function to convert this text to a private key. Applying the most popular conversion algorithm (SHA-256) to this passphrase generates the address: 1J3m4nneGFppRjx6qv92qyz7EsMVdLfr8R If you go to blockexplorerer and search this address, you can see that this address was used recently to store funds, which were immediately withdrawn. Unfortunately, it’s not always easy to tell what qualifies as an insecure brain wallet passphrase and what doesn’t. Attackers can exploit this uncertainty and the inexperience of new users to steal funds. For example, a thief might compile an enormous database of common phrases and passwords. Such a database might number in the trillions of entries or more, but would still be searchable in its entirety with little computational effort. Compare this situation to the one with website passwords. If you register for a web service using a password someone else happens to have chosen, you don’t take over their account because your username must be unique. Bitcoin private keys are different in that they serve the dual role of user identification (via address generation) and authentication (via digital signatures). Secure private keys are generated with a high degree of unpredictability so they can’t be guessed before or after the fact. <h2>6. Private Keys are (Somewhat) Portable </h2> For the most part, wallet software hides the process of generating, using, and storing private keys. However, private keys can become visible from time to time. When this happens, understanding private keys and how they interact with your specific software becomes important. Paper wallets present the most common route by which private keys show up outside of software wallets. Although they come in a multitude of formats, the essential feature of any paper wallet is a printed private key. Support for using externally-generated private keys varies greatly across wallet applications. For example, private keys imported into Armory are not preserved in future backup recoveries using the most common and recommended procedure. Likewise, importing private keys into MultiBit changes the behavior of that wallet with respect to change addresses. Should one wallet application begin to malfunction, its private keys can be imported into another application. This rescue procedure provides the second main route through which private keys become visible to end users. A closely-related procedure consists of restoring the state of a software wallet through a backup file. Before losing funds due to preventable mistakes, understand how your software treats externally-created private keys — before importing them. Regardless of the specific wallet application being use, private keys kept or maintained outside of a software wallet need to be handled with care to prevent loss and theft. Conclusions Bitcoin can be thought of as an open messaging system secured by public key cryptography. In contrast to other systems protected by username and password logins, Bitcoin is secured through digital message signatures created with a unique private key. This single point of access places a very high value on the secure generation, use, and storage of private keys. |
| json metadata | {"tags":["crypto","ethereum"],"image":["https://steemitimages.com/DQmP2qryJKW3wKt26VqqcZ8FnybbQo2Mmnut2pCr7NR6cfe/image.png"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #17723966/Trx 5a6964246896d79302361f936415efb08e657e51 |
View Raw JSON Data
{
"trx_id": "5a6964246896d79302361f936415efb08e657e51",
"block": 17723966,
"trx_in_block": 9,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-02T05:00:42",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "crypto",
"author": "josephd",
"permlink": "on-bitcoin-private-keys-ownership-transactions-and-more",
"title": "On Bitcoin private keys, ownership, transactions and more",
"body": "\n\nPrivate keys have been an integral component of Bitcoin since its first description in 2008. Wallet software often attempts to shield users from the need to understand what private keys are and how they work. Even so, most users eventually come face to face with private keys, too often with unpleasant results.\n\nA basic understanding of private keys can help prevent loss of funds and other mishaps, but it can also offer useful insights into how Bitcoin works. This guide outlines the most important private key concepts for effectively using Bitcoin.\nBitcoin: A Secure Messaging System\n\nAlthough Bitcoin is best known as a payment system, underneath it all runs a secure messaging system built on the Internet. Instead of relaying emails, texts, or web pages, the Bitcoin network processes value-transfer messages called transactions. Private keys play a central role in verifying these messages, identifying senders and receivers, and in securing the network.\n\nAn example helps illustrate the problems that private keys solve. Imagine Alice wants to pay Bob 10 bitcoin (BTC). She begins by creating a transaction identifying Bob as the payee and 10 BTC as the amount to be transferred. Alice then broadcasts this transaction to all users of the Bitcoin network.\n\nSimple Transaction. Alice’s transaction paying Bob 10 bitcoin. As it stands, Alice has no way to identify herself or Bob, nor does she have any assurance the transaction won’t be forged or tampered with.\n\nIn using this system, Alice faces two fundamental problems. First, she needs a way to identify both herself and Bob in the transaction. Alice can’t employ a central authority such as a government registry or email provider because that would create a central point of control and failure — the very thing Bitcoin was created to eliminate. Second, Alice needs a way to prevent others from changing her transaction and forging transactions in her name.\n\nBitcoin solves these problems through a system called public key cryptography. This system uses two pieces of information to authenticate messages. A public key identifies a sender or recipient, and can be distributed to others. A private key is used together with the public key to create an unforgeable message signature. The private key must be kept secret. Public and private keys are mathematically linked.\n\nAlice Signs Transaction. Alice signs a transaction to Bob with her private key. Bob will later use Alice’s public key to verify Alice’s signature.\n\nWith this overview in mind, here are six things about private keys to keep in mind as you use Bitcoin.\n\n<h2> 1. A Private Key is Just a Number </h2>\n\nA Bitcoin private key is simply an integer between one and about 1077. This may not seem like much of a selection, but for practical purposes it’s essentially infinite.\n\nIf you could process one trillion private keys per second, it would take more than one million times the age of the universe to count them all. Even worse, just enumerating these keys would consume more than the total energy output of the sun for 32 years. This vast keyspace plays a fundamental role in securing the Bitcoin network.\n\nBecause private keys contain many digits when expressed as decimal numbers, an alternative called Wallet Import Format (WIF) has been devised. This format begins with the number “5” and contains a sequence of letters and numbers. For example, here’s a private key represented in WIF format:\n\n5KJvsngHeMpm884wtkJNzQGaCEui9HJBGFsvd3VyK5qMZXj3hS\n\n<h2> 2. Transactions are Messages Signed with a Private Key </h2>\n\nTo prevent forgery, Bitcoin requires that each transaction bear a digital signature. This signature, like a private key, is just a number selected from a very large range. Wallet software generates a signature by mathematically processing a transaction together with the correct private key.\n\nThis system works because anyone with a transaction and its signature can verify the authenticity of a message. However, a transaction signature is practically impossible to fake. The only way to produce a valid signature for a particular transaction is to use the correct private key.\n\nTwo transactions from Alice to Bob. The first transfers 10 BTC, and the second transfers 2 BTC. The same private key leads to a unique, unguessable signature for each transaction.\n\nUnlike a physical signature you might write on a check, a transaction signature changes if the transaction changes even slightly. The way the signature will change is unpredictable, ensuring that only a person in possession of a private key can provide the correct signature.\n\n<h2> 3. Anyone Who Knows Your Private Key Can Steal Your Funds </h2>\n\nAny transaction bearing a valid signature will be accepted by the Bitcoin network. At the same time, any person in possession of a private key can create a valid transaction. These two facts taken together mean that someone knowing only your private key can steal from you.\n\nMany avenues are open to thieves who steal private keys. Two of the most popular are storage media and communications channels. For this reason, extreme caution must be taken whenever storing or transmitting private keys.\n\nSoftware wallets usually store private keys in a “wallet file” on the main hard drive. Wallets often place this file in a standard, well-known directory, making it an ideal target bitcoin-specific malware.\n\nTo counter this threat, software wallets offer an option to encrypt the wallet file. Any attacker gaining access to your wallet file would then need to decrypt it. The difficulty of doing so depends on the quality of the encryption and strength of the password being used. Wallet files can be encrypted on many software wallets by adding a password.\n\n\nAlthough wallet backups are a good idea, they can potentially leak private keys. For example, it may be tempting to save a backup of your software wallet to a cloud storage service such as Dropbox. However, anyone capable of viewing this backup online (which could be a surprisingly long list of people) would be in a position to steal some or all of your funds. A similar problem could arise through emailing backups to yourself or leaving a paper wallet around the house. Encryption can reduce the risk, but not eliminate it altogether.\n\nPreventing the accidental release of private keys is the main purpose of “cold storage.” For more information, see A Gentle Introduction to Bitcoin Cold Storage.\n\n<h2> 4. Addresses are Derived from Public Keys, Which are Themselves Derived from Private Keys </h2>\n\nA Bitcoin public key is obtained by applying a well-defined set of mathematical operations, defined through Elliptic Curve Cryptography (ECC), to a private key. Like a private key, a public key is simply a very large number.\nSVG Image\nPrivate Key to Address. A private key, which is just a number such as 42, can be transformed mathematically into a public key. A public key is then transformed into an address. Each step is irreversible.\n\nThe relationship between private keys and public keys is an example of a mathematical trapdoor - a function that’s easy to perform in one direction, but practically impossible to perform in the opposite direction. This unidirectionality lies at the center of Bitcoin’s security model.\n\nJust as private keys can be shortened to make them more usable with displays and keyboards, so too can public keys. An address results from applying a multi-step transformation to a public key. This produces a string of text and digits, usually starting with the number “1”.\n\nNotice that no network is needed at any point in the generation of a private key or the corresponding address. Every computer on the Bitcoin network knows about the mathematical relationship between public and private keys. This enables each participant to select private keys and sign transactions independently of the Bitcoin network. The enormous private keyspace ensures that any properly-selected key will be unique.\n\n<h2>5. Security Depends on Choosing a Good Private Key </h2>\n\nKnowledge of a private key is the only verification needed to spend funds from a Bitcoin address. Private keys should therefore be kept secret. However, careless selection of a private key can lead to theft just as easily as its accidental release.\n\nFor example, imagine that we want to use a private key that’s easy to remember. The number 1 is both easy to remember and a valid Bitcoin private key. But how secure would it be?\n\nThe private key 1 generates this address:\n\n1EHNa6Q4Jz2uvNExL497mE43ikXhwF6kZm\n\nIf you follow the link, you’ll notice that the address has already been involved in over 1,000 transactions for a total of over 7 BTC within the last few years. If you wanted, you could easily spend any available funds at this address because the private key is known to you.\n\nNow imagine you’re a thief determined to steal bitcoin. One strategy might be to compile a list of easy-to-remember private keys. Next, generate the addresses for these keys and monitor the Bitcoin network for incoming payments to one of them. When one arrives, immediately sign a transaction moving the funds to another address you control.\n\nContrast the ease of this scheme with a situation in which a private key was chosen by a perfect random number generator. With no clue what the key might be, brute force iteration would be the only option. As we’ve already seen, carrying out this plan is physically impossible.\n\nWhat would happen if the random number generator were not quite random? For example, what if all output private keys were clustered about a constant value within a narrow range?\n\nPrivate Keyspace. Random private key distribution (left) versus one that is clustered (right). The clustered distribution limits the search space, favoring an attacker.\n\nAny attacker aware of such a defect could drastically reduce the necessary search space. Under the right conditions, it would become practical to monitor all of the addresses based on the faulty random number generator and steal funds from any one of them at will.\n\nThe need to select a good private key becomes especially important with brain wallets. One method to create a brain wallet starts with a passphrase such as “to be or not to be”, then applies a mathematical function to convert this text to a private key. Applying the most popular conversion algorithm (SHA-256) to this passphrase generates the address:\n\n1J3m4nneGFppRjx6qv92qyz7EsMVdLfr8R\n\nIf you go to blockexplorerer and search this address, you can see that this address was used recently to store funds, which were immediately withdrawn.\n\nUnfortunately, it’s not always easy to tell what qualifies as an insecure brain wallet passphrase and what doesn’t. Attackers can exploit this uncertainty and the inexperience of new users to steal funds. For example, a thief might compile an enormous database of common phrases and passwords. Such a database might number in the trillions of entries or more, but would still be searchable in its entirety with little computational effort.\n\nCompare this situation to the one with website passwords. If you register for a web service using a password someone else happens to have chosen, you don’t take over their account because your username must be unique. Bitcoin private keys are different in that they serve the dual role of user identification (via address generation) and authentication (via digital signatures).\n\nSecure private keys are generated with a high degree of unpredictability so they can’t be guessed before or after the fact.\n\n<h2>6. Private Keys are (Somewhat) Portable </h2>\n\nFor the most part, wallet software hides the process of generating, using, and storing private keys. However, private keys can become visible from time to time. When this happens, understanding private keys and how they interact with your specific software becomes important.\n\nPaper wallets present the most common route by which private keys show up outside of software wallets. Although they come in a multitude of formats, the essential feature of any paper wallet is a printed private key.\n\nSupport for using externally-generated private keys varies greatly across wallet applications. For example, private keys imported into Armory are not preserved in future backup recoveries using the most common and recommended procedure. Likewise, importing private keys into MultiBit changes the behavior of that wallet with respect to change addresses.\n\nShould one wallet application begin to malfunction, its private keys can be imported into another application. This rescue procedure provides the second main route through which private keys become visible to end users. A closely-related procedure consists of restoring the state of a software wallet through a backup file.\n\nBefore losing funds due to preventable mistakes, understand how your software treats externally-created private keys — before importing them. Regardless of the specific wallet application being use, private keys kept or maintained outside of a software wallet need to be handled with care to prevent loss and theft.\nConclusions\n\nBitcoin can be thought of as an open messaging system secured by public key cryptography. In contrast to other systems protected by username and password logins, Bitcoin is secured through digital message signatures created with a unique private key. This single point of access places a very high value on the secure generation, use, and storage of private keys.",
"json_metadata": "{\"tags\":[\"crypto\",\"ethereum\"],\"image\":[\"https://steemitimages.com/DQmP2qryJKW3wKt26VqqcZ8FnybbQo2Mmnut2pCr7NR6cfe/image.png\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}robertouetiupvoted (100.00%) @josephd / why-use-steemit2017/11/30 11:46:09
robertouetiupvoted (100.00%) @josephd / why-use-steemit
2017/11/30 11:46:09
| voter | robertoueti |
| author | josephd |
| permlink | why-use-steemit |
| weight | 10000 (100.00%) |
| Transaction Info | Block #17674483/Trx aa0c3470b0e87c208514eab7267a04fa507ac537 |
View Raw JSON Data
{
"trx_id": "aa0c3470b0e87c208514eab7267a04fa507ac537",
"block": 17674483,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-11-30T11:46:09",
"op": [
"vote",
{
"voter": "robertoueti",
"author": "josephd",
"permlink": "why-use-steemit",
"weight": 10000
}
]
}josephdreceived 0.012 SBD, 0.018 SP author reward for @josephd / most-promising-coin-i-ve-seen-after-eth-chainlink2017/11/26 13:12:51
josephdreceived 0.012 SBD, 0.018 SP author reward for @josephd / most-promising-coin-i-ve-seen-after-eth-chainlink
2017/11/26 13:12:51
| author | josephd |
| permlink | most-promising-coin-i-ve-seen-after-eth-chainlink |
| sbd payout | 0.012 SBD |
| steem payout | 0.000 STEEM |
| vesting payout | 28.739765 VESTS |
| Transaction Info | Block #17561073/Virtual Operation #7 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 17561073,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 7,
"timestamp": "2017-11-26T13:12:51",
"op": [
"author_reward",
{
"author": "josephd",
"permlink": "most-promising-coin-i-ve-seen-after-eth-chainlink",
"sbd_payout": "0.012 SBD",
"steem_payout": "0.000 STEEM",
"vesting_payout": "28.739765 VESTS"
}
]
}Manabar
Voting Power97.28%
Downvote Power0.00%
Resource Credits100.00%
Reputation Progress52.57%
{
"voting_manabar": {
"current_mana": 9728,
"last_update_time": 1512204903
},
"downvote_manabar": {
"current_mana": 0,
"last_update_time": 1484244849
},
"rc_account": {
"account": "josephd",
"rc_manabar": {
"current_mana": 203771010,
"last_update_time": 1657437492
},
"max_rc_creation_adjustment": {
"amount": "2020748973",
"precision": 6,
"nai": "@@000000037"
},
"max_rc": 2020748973
}
}Account Metadata
| POSTING JSON METADATA | |
| profile | {"name":"Joseph","about":"btc : 16rxpgZNV9nAMbtPNtfqW2mfnW7eN6oomZ LTC: LUDxnSnKvgKddZ9XD5ivrCjQDhP19qYEZS","profile_image":"http://i.imgur.com/GhmlxX0.jpg"} |
| JSON METADATA | |
| profile | {"name":"Joseph","about":"btc : 16rxpgZNV9nAMbtPNtfqW2mfnW7eN6oomZ LTC: LUDxnSnKvgKddZ9XD5ivrCjQDhP19qYEZS","profile_image":"http://i.imgur.com/GhmlxX0.jpg"} |
{
"posting_json_metadata": {
"profile": {
"name": "Joseph",
"about": "btc : 16rxpgZNV9nAMbtPNtfqW2mfnW7eN6oomZ LTC: LUDxnSnKvgKddZ9XD5ivrCjQDhP19qYEZS",
"profile_image": "http://i.imgur.com/GhmlxX0.jpg"
}
},
"json_metadata": {
"profile": {
"name": "Joseph",
"about": "btc : 16rxpgZNV9nAMbtPNtfqW2mfnW7eN6oomZ LTC: LUDxnSnKvgKddZ9XD5ivrCjQDhP19qYEZS",
"profile_image": "http://i.imgur.com/GhmlxX0.jpg"
}
}
}Auth Keys
Owner
Single Signature
Public Keys
STM8caGk5Y6JSnapz7XkBfTyY76jh41v6TUMVrd4VGwVSdpwiApbu1/1
Active
Single Signature
Public Keys
STM783dyp3SWSUDgtPCRwz9AeuKhbj9YyBGWW4XN9iaioFVXzyTRQ1/1
Posting
Single Signature
Public Keys
STM7LkgfjnRvNgWcdm4kRRts6bETLupK6obaBBdBHausLzv3vseHf1/1
Memo
STM57b4jjHv4XdxJw9WT84p2dANkh9rDkAaBjhsh3zcE8c1mLdCnK
{
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM8caGk5Y6JSnapz7XkBfTyY76jh41v6TUMVrd4VGwVSdpwiApbu",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM783dyp3SWSUDgtPCRwz9AeuKhbj9YyBGWW4XN9iaioFVXzyTRQ",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7LkgfjnRvNgWcdm4kRRts6bETLupK6obaBBdBHausLzv3vseHf",
1
]
]
},
"memo": "STM57b4jjHv4XdxJw9WT84p2dANkh9rDkAaBjhsh3zcE8c1mLdCnK"
}Witness Votes
1 / 30
01.dragosroua |
[ "dragosroua" ]