Ecoer Logo

@jonklinger

59

Jonathan Klinger is a cryptolawyer. He is a Master of Law (2007) and teaches Cyberlaw. He blogs about privacy, copyright, and technolegal interfaces

steemit.com/@jonklinger
VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS8.13%
Net Worth
0.304USD
STEEM
0.000STEEM
SBD
0.005SBD
Own SP
5.205SP

Detailed Balance

STEEM
balance
0.000STEEM
market_balance
0.000STEEM
savings_balance
0.000STEEM
reward_steem_balance
0.000STEEM
STEEM POWER
Own SP
5.205SP
Delegated Out
0.000SP
Delegation In
0.000SP
Effective Power
5.205SP
Reward SP (pending)
0.000SP
SBD
sbd_balance
0.005SBD
sbd_conversions
0.000SBD
sbd_market_balance
0.000SBD
savings_sbd_balance
0.000SBD
reward_sbd_balance
0.000SBD
{
  "balance": "0.000 STEEM",
  "savings_balance": "0.000 STEEM",
  "reward_steem_balance": "0.000 STEEM",
  "vesting_shares": "8466.268010 VESTS",
  "delegated_vesting_shares": "0.000000 VESTS",
  "received_vesting_shares": "0.000000 VESTS",
  "sbd_balance": "0.005 SBD",
  "savings_sbd_balance": "0.000 SBD",
  "reward_sbd_balance": "0.000 SBD",
  "conversions": []
}

Account Info

namejonklinger
id641642
rank215,935
reputation6120884754286
created2018-01-23T14:24:54
recovery_accountsteem
proxyNone
post_count53
comment_count0
lifetime_vote_count0
witnesses_voted_for2
last_post2021-02-27T09:57:24
last_root_post2021-02-27T09:57:24
last_vote_time2019-08-20T20:13:12
proxied_vsf_votes0, 0, 0, 0
can_vote1
voting_power0
delayed_votes0
balance0.000 STEEM
savings_balance0.000 STEEM
sbd_balance0.005 SBD
savings_sbd_balance0.000 SBD
vesting_shares8466.268010 VESTS
delegated_vesting_shares0.000000 VESTS
received_vesting_shares0.000000 VESTS
reward_vesting_balance0.000000 VESTS
vesting_balance0.000 STEEM
vesting_withdraw_rate0.000000 VESTS
next_vesting_withdrawal1969-12-31T23:59:59
withdrawn440960852426
to_withdraw440960852426
withdraw_routes0
savings_withdraw_requests0
last_account_recovery1970-01-01T00:00:00
reset_accountnull
last_owner_update1970-01-01T00:00:00
last_account_update2018-04-03T14:00:24
minedNo
sbd_seconds0
sbd_last_interest_payment2024-12-02T09:29:42
savings_sbd_last_interest_payment2020-04-28T09:08:39
{
  "id": 641642,
  "name": "jonklinger",
  "owner": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM6nXrxcgLpN7bG4FXsQvPMtSUknU71UZSeYjYgjjtcbmbbJ6VvS",
        1
      ]
    ]
  },
  "active": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM4uyptDJ3dcWMSmWoVceQpyaRDJmNQo6TXeWCYnyXSBrvrAcnAj",
        1
      ]
    ]
  },
  "posting": {
    "weight_threshold": 1,
    "account_auths": [
      [
        "utopian.app",
        1
      ]
    ],
    "key_auths": [
      [
        "STM5QXJ4jviwK6ZN66RKcdfgf51KQxe2fkBaddPLRY6CX3a5LxVgh",
        1
      ]
    ]
  },
  "memo_key": "STM6UWe6HC2g6A2uLZ2k23Bcmtq2GAiVwyqoLXnBkvGZbaZ4agMQD",
  "json_metadata": "{\"profile\":{\"profile_image\":\"https://pbs.twimg.com/profile_images/951159743825043456/loWpoLq4_400x400.jpg\",\"cover_image\":\"https://scontent.fsdv1-1.fna.fbcdn.net/v/t1.0-9/21752332_10155023946186295_3086871474418016518_n.jpg?oh=bec1ce5e7cc90b3f3a0bdcba5edd9c0a&oe=5AF11AE0\",\"name\":\"jonklinger\",\"about\":\"Jonathan Klinger is a cryptolawyer. He is a Master of Law (2007) and teaches Cyberlaw. He blogs about privacy, copyright, and technolegal interfaces\",\"location\":\"Tel-Aviv, Israel\",\"website\":\"http://2jk.org/english/\"}}",
  "posting_json_metadata": "{\"profile\":{\"profile_image\":\"https://pbs.twimg.com/profile_images/951159743825043456/loWpoLq4_400x400.jpg\",\"cover_image\":\"https://scontent.fsdv1-1.fna.fbcdn.net/v/t1.0-9/21752332_10155023946186295_3086871474418016518_n.jpg?oh=bec1ce5e7cc90b3f3a0bdcba5edd9c0a&oe=5AF11AE0\",\"name\":\"jonklinger\",\"about\":\"Jonathan Klinger is a cryptolawyer. He is a Master of Law (2007) and teaches Cyberlaw. He blogs about privacy, copyright, and technolegal interfaces\",\"location\":\"Tel-Aviv, Israel\",\"website\":\"http://2jk.org/english/\"}}",
  "proxy": "",
  "last_owner_update": "1970-01-01T00:00:00",
  "last_account_update": "2018-04-03T14:00:24",
  "created": "2018-01-23T14:24:54",
  "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": 53,
  "can_vote": true,
  "voting_manabar": {
    "current_mana": "449427120436",
    "last_update_time": 1733131782
  },
  "downvote_manabar": {
    "current_mana": "112356780108",
    "last_update_time": 1733131782
  },
  "voting_power": 0,
  "balance": "0.000 STEEM",
  "savings_balance": "0.000 STEEM",
  "sbd_balance": "0.005 SBD",
  "sbd_seconds": "0",
  "sbd_seconds_last_update": "2024-12-02T09:29:42",
  "sbd_last_interest_payment": "2024-12-02T09:29:42",
  "savings_sbd_balance": "0.000 SBD",
  "savings_sbd_seconds": "0",
  "savings_sbd_seconds_last_update": "2020-04-28T09:08:39",
  "savings_sbd_last_interest_payment": "2020-04-28T09:08:39",
  "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": "8466.268010 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": "440960852426",
  "to_withdraw": "440960852426",
  "withdraw_routes": 0,
  "curation_rewards": 47,
  "posting_rewards": 445114,
  "proxied_vsf_votes": [
    0,
    0,
    0,
    0
  ],
  "witnesses_voted_for": 2,
  "last_post": "2021-02-27T09:57:24",
  "last_root_post": "2021-02-27T09:57:24",
  "last_vote_time": "2019-08-20T20:13:12",
  "post_bandwidth": 0,
  "pending_claimed_accounts": 0,
  "vesting_balance": "0.000 STEEM",
  "reputation": "6120884754286",
  "transfer_history": [],
  "market_history": [],
  "post_history": [],
  "vote_history": [],
  "other_history": [],
  "witness_votes": [
    "utopian-io",
    "windforce"
  ],
  "tags_usage": [],
  "guest_bloggers": [],
  "rank": 215935
}

Withdraw Routes

IncomingOutgoing
Empty
Empty
{
  "incoming": [],
  "outgoing": []
}
From Date
To Date
jonklingersent 260.810 STEEM to @polo-wallet-01- "H3PJF9x327"
2025/01/21 11:49:12
fromjonklinger
topolo-wallet-01
amount260.810 STEEM
memoH3PJF9x327
Transaction InfoBlock #92314237/Trx 9a698afe75284dd099f29ae714400ef667e14109
View Raw JSON Data
{
  "trx_id": "9a698afe75284dd099f29ae714400ef667e14109",
  "block": 92314237,
  "trx_in_block": 3,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2025-01-21T11:49:12",
  "op": [
    "transfer",
    {
      "from": "jonklinger",
      "to": "polo-wallet-01",
      "amount": "260.810 STEEM",
      "memo": "H3PJF9x327"
    }
  ]
}
jonklingerreceived 65.251 STEEM from power down installment (67.774 SP)
2024/12/30 09:29:51
from accountjonklinger
to accountjonklinger
withdrawn110240.213105 VESTS
deposited65.251 STEEM
Transaction InfoBlock #91679300/Virtual Operation #2
View Raw JSON Data
{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 91679300,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 2,
  "timestamp": "2024-12-30T09:29:51",
  "op": [
    "fill_vesting_withdraw",
    {
      "from_account": "jonklinger",
      "to_account": "jonklinger",
      "withdrawn": "110240.213105 VESTS",
      "deposited": "65.251 STEEM"
    }
  ]
}
jonklingerreceived 65.217 STEEM from power down installment (67.774 SP)
2024/12/23 09:29:51
from accountjonklinger
to accountjonklinger
withdrawn110240.213107 VESTS
deposited65.217 STEEM
Transaction InfoBlock #91478189/Virtual Operation #2
View Raw JSON Data
{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 91478189,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 2,
  "timestamp": "2024-12-23T09:29:51",
  "op": [
    "fill_vesting_withdraw",
    {
      "from_account": "jonklinger",
      "to_account": "jonklinger",
      "withdrawn": "110240.213107 VESTS",
      "deposited": "65.217 STEEM"
    }
  ]
}
jonklingerreceived 65.184 STEEM from power down installment (67.774 SP)
2024/12/16 09:29:51
from accountjonklinger
to accountjonklinger
withdrawn110240.213107 VESTS
deposited65.184 STEEM
Transaction InfoBlock #91277116/Virtual Operation #2
View Raw JSON Data
{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 91277116,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 2,
  "timestamp": "2024-12-16T09:29:51",
  "op": [
    "fill_vesting_withdraw",
    {
      "from_account": "jonklinger",
      "to_account": "jonklinger",
      "withdrawn": "110240.213107 VESTS",
      "deposited": "65.184 STEEM"
    }
  ]
}
jonklingerreceived 65.151 STEEM from power down installment (67.774 SP)
2024/12/09 09:29:51
from accountjonklinger
to accountjonklinger
withdrawn110240.213107 VESTS
deposited65.151 STEEM
Transaction InfoBlock #91075986/Virtual Operation #3
View Raw JSON Data
{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 91075986,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 3,
  "timestamp": "2024-12-09T09:29:51",
  "op": [
    "fill_vesting_withdraw",
    {
      "from_account": "jonklinger",
      "to_account": "jonklinger",
      "withdrawn": "110240.213107 VESTS",
      "deposited": "65.151 STEEM"
    }
  ]
}
jonklingerstarted power down of 271.098 SP
2024/12/02 09:29:51
accountjonklinger
vesting shares440960.852426 VESTS
Transaction InfoBlock #90874882/Trx d1109a531c6c0d084a4a3db856f0244a3c613c9d
View Raw JSON Data
{
  "trx_id": "d1109a531c6c0d084a4a3db856f0244a3c613c9d",
  "block": 90874882,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2024-12-02T09:29:51",
  "op": [
    "withdraw_vesting",
    {
      "account": "jonklinger",
      "vesting_shares": "440960.852426 VESTS"
    }
  ]
}
jonklingerclaimed reward balance: 0.005 SBD, 0.015 SP
2024/12/02 09:29:42
accountjonklinger
reward steem0.000 STEEM
reward sbd0.005 SBD
reward vests24.618394 VESTS
Transaction InfoBlock #90874879/Trx 3b6699dbc730f9cc09937b0b4ae5bd4d7ce5ecc1
View Raw JSON Data
{
  "trx_id": "3b6699dbc730f9cc09937b0b4ae5bd4d7ce5ecc1",
  "block": 90874879,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2024-12-02T09:29:42",
  "op": [
    "claim_reward_balance",
    {
      "account": "jonklinger",
      "reward_steem": "0.000 STEEM",
      "reward_sbd": "0.005 SBD",
      "reward_vests": "24.618394 VESTS"
    }
  ]
}
steemeggsent 0.001 STEEM to @jonklinger- "Free Upvotes Await!!!, Vote @se-witness for one of your 30 witness votes. Once you do so, you will start accumulating free upvotes every 6 hours automatically. Please check my latests posts for more ..."
2022/12/27 00:25:54
fromsteemegg
tojonklinger
amount0.001 STEEM
memoFree Upvotes Await!!!, Vote @se-witness for one of your 30 witness votes. Once you do so, you will start accumulating free upvotes every 6 hours automatically. Please check my latests posts for more info. Thanks!
Transaction InfoBlock #70644935/Trx 0ea19d4dc1086a951ac9a47a7317111ce52e2eaf
View Raw JSON Data
{
  "trx_id": "0ea19d4dc1086a951ac9a47a7317111ce52e2eaf",
  "block": 70644935,
  "trx_in_block": 21,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-12-27T00:25:54",
  "op": [
    "transfer",
    {
      "from": "steemegg",
      "to": "jonklinger",
      "amount": "0.001 STEEM",
      "memo": "Free Upvotes Await!!!, Vote @se-witness for one of your 30 witness votes. Once you do so, you will start accumulating free upvotes every 6 hours automatically.  Please check my latests posts for more info.  Thanks!"
    }
  ]
}
ph-supportsent 0.003 STEEM to @jonklinger- "Hi there @jonklinger. We hope that you don't mind this little memo as we would love to bring your attention to small PASSIVE INCOME opportunity here on Steemit. Allow us to share with you link to our ..."
2022/08/19 03:45:18
fromph-support
tojonklinger
amount0.003 STEEM
memoHi there @jonklinger. We hope that you don't mind this little memo as we would love to bring your attention to small PASSIVE INCOME opportunity here on Steemit. Allow us to share with you link to our new delegation program. Perhaps you will find it worth your time and hopefully you will decide that our efforts bring value to Steemit and are worth your support. We would also greatly appreciate if you could RESTEEM this post and help us bring more traffic. Link: // https://steemit.com/hive-175254/@ph-support/check-out-our-passive-income-delegation-program-run-by-project-hope
Transaction InfoBlock #66928545/Trx 3fd286b6157ea931a0e9d1edd4b3428975ccc2a0
View Raw JSON Data
{
  "trx_id": "3fd286b6157ea931a0e9d1edd4b3428975ccc2a0",
  "block": 66928545,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-08-19T03:45:18",
  "op": [
    "transfer",
    {
      "from": "ph-support",
      "to": "jonklinger",
      "amount": "0.003 STEEM",
      "memo": "Hi there @jonklinger. We hope that you don't mind this little memo as we would love to bring your attention to small PASSIVE INCOME opportunity here on Steemit. Allow us to share with you link to our new delegation program. Perhaps you will find it worth your time and hopefully you will decide that our efforts bring value to Steemit and are worth your support. We would also greatly appreciate if you could RESTEEM this post and help us bring more traffic. Link: // https://steemit.com/hive-175254/@ph-support/check-out-our-passive-income-delegation-program-run-by-project-hope"
    }
  ]
}
ph-supportsent 0.001 STEEM to @jonklinger
2022/08/17 04:40:45
fromph-support
tojonklinger
amount0.001 STEEM
memo
Transaction InfoBlock #66872425/Trx 5eb0137cf64a6bf2fda5860605f3928f6c7a8cca
View Raw JSON Data
{
  "trx_id": "5eb0137cf64a6bf2fda5860605f3928f6c7a8cca",
  "block": 66872425,
  "trx_in_block": 6,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-08-17T04:40:45",
  "op": [
    "transfer",
    {
      "from": "ph-support",
      "to": "jonklinger",
      "amount": "0.001 STEEM",
      "memo": ""
    }
  ]
}
2021/05/27 21:41:57
parent authorjonklinger
parent permlinki-read-initiativeq-s-privacy-policy-so-that-you-won-t-have-to
authorrapshmelth
permlinkre-jonklinger-i-read-initiativeq-s-privacy-policy-so-that-you-won-t-have-to-20180825t223751175z
title
bodyI completely agree with you.
json metadata{"app":"steemit/0.2"}
Transaction InfoBlock #54118056/Trx 2b1d6328aadf933d55b4f03b16565c4fd04c7249
View Raw JSON Data
{
  "trx_id": "2b1d6328aadf933d55b4f03b16565c4fd04c7249",
  "block": 54118056,
  "trx_in_block": 5,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-05-27T21:41:57",
  "op": [
    "comment",
    {
      "parent_author": "jonklinger",
      "parent_permlink": "i-read-initiativeq-s-privacy-policy-so-that-you-won-t-have-to",
      "author": "rapshmelth",
      "permlink": "re-jonklinger-i-read-initiativeq-s-privacy-policy-so-that-you-won-t-have-to-20180825t223751175z",
      "title": "",
      "body": "I completely agree with you.",
      "json_metadata": "{\"app\":\"steemit/0.2\"}"
    }
  ]
}
2021/03/06 09:57:24
authorjonklinger
permlinkwhy-phishing-crypto-seed-scamso-work-if-you-re-reading-this-you-re-basically-not-the-target-audience
sbd payout0.005 SBD
steem payout0.000 STEEM
vesting payout24.618394 VESTS
Transaction InfoBlock #51770484/Virtual Operation #3
View Raw JSON Data
{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 51770484,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 3,
  "timestamp": "2021-03-06T09:57:24",
  "op": [
    "author_reward",
    {
      "author": "jonklinger",
      "permlink": "why-phishing-crypto-seed-scamso-work-if-you-re-reading-this-you-re-basically-not-the-target-audience",
      "sbd_payout": "0.005 SBD",
      "steem_payout": "0.000 STEEM",
      "vesting_payout": "24.618394 VESTS"
    }
  ]
}
2021/02/27 14:56:30
voterelifeldman
authorjonklinger
permlinkwhy-phishing-crypto-seed-scamso-work-if-you-re-reading-this-you-re-basically-not-the-target-audience
weight10000 (100.00%)
Transaction InfoBlock #51577922/Trx dc29771af63592207fed7f1ed9c577df465ddffe
View Raw JSON Data
{
  "trx_id": "dc29771af63592207fed7f1ed9c577df465ddffe",
  "block": 51577922,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-02-27T14:56:30",
  "op": [
    "vote",
    {
      "voter": "elifeldman",
      "author": "jonklinger",
      "permlink": "why-phishing-crypto-seed-scamso-work-if-you-re-reading-this-you-re-basically-not-the-target-audience",
      "weight": 10000
    }
  ]
}
executive-boardsent 0.001 STEEM to @jonklinger- "❗ Hello jonklinger, 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, j..."
2021/02/27 11:40:09
fromexecutive-board
tojonklinger
amount0.001 STEEM
memo❗ Hello jonklinger, 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 InfoBlock #51574041/Trx 46b7fadb7c93260a0a14d3665c858a7beac3e200
View Raw JSON Data
{
  "trx_id": "46b7fadb7c93260a0a14d3665c858a7beac3e200",
  "block": 51574041,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-02-27T11:40:09",
  "op": [
    "transfer",
    {
      "from": "executive-board",
      "to": "jonklinger",
      "amount": "0.001 STEEM",
      "memo": "❗ Hello jonklinger, 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."
    }
  ]
}
2021/02/27 11:39:03
parent author
parent permlinkhardware-wallets
authorjonklinger
permlinkwhy-phishing-crypto-seed-scamso-work-if-you-re-reading-this-you-re-basically-not-the-target-audience
titleWhy phishing crypto seed scams work: If you're reading this you're basically not the target audience.
body[A post on reddit]( https://steemit.com/death/@jonklinger/be-prepared-how-to-manage-your-digital-assets-when-you-re-gone ) triggered my will to explain this. TL;DR: some random person's bitcoins and ethers were stolen; he says he "never" provided his seed (I'll explain later) to anyone and he is not a victim of phishing. After answering a few comments, the truth is discovered: he downloaded a fake app that requested that he provide it with the seed, the seed was sent to hackers, all hope is gone. So; how did this happen? in order for this to happen, several failures had to occur. The first is the seed. Now, what is a seed? A seed is a 24-word passphrase that is basically a backup of your bitcoin wallet. I [wrote about it]( https://steemit.com/death/@jonklinger/be-prepared-how-to-manage-your-digital-assets-when-you-re-gone ) when explaining how to backup your wallet. In [BIP-39]( https://iancoleman.io/bip39/ ) an improvement to the bitcoin protocol was implemented: each wallet has an "easy to store" seed, comprising of 24 words, that generate the private key. These words should be kept safe in storage, and only used to restore the wallet. I use [cryptosteel]( https://cryptosteel.com/product/cryptosteel/ ) (not an affiliate link) in order to backup my seed. Now, the first thing that a hardware wallet tells you is to never put this seed on a computer. It should always be typed into the hardware wallet itself ([there's something a bit different on Trezor One]( https://wiki.trezor.io/User_manual:Advanced_recovery ) ). This is the first rule of recovering a wallet: never, but never, I mean **never** type your seed on a PC. So, the poor chap that had his coins stolen broke this rule. Why did he break the rule? because he saw an error message that said "please restore your wallet". Now, this is one of the reasons that you always need to question authority. Even when software prompts for a password, you need to stop and think on what you're doing. Is this the right site or app? Why is it asking this. ![image.png](https://cdn.steemitimages.com/DQmPYmeiKHApvKQ3htUkAcbB4GabMggN8kw9JrwdBMJQZ7w/image.png) I've just finished Ira Winkler's "[You CAN stop stupid]( https://www.amazon.com/gp/product/B08JSB5CHG )", a book about security, cybersecurity and the human factor. Ira keeps repeating a large percentage of people fall for phishing scams no matter what we do ([and he's right]( https://www.computerweekly.com/news/252476845/A-quarter-of-users-will-fall-for-basic-phishing-attacks ) ). **So; if we know that the vector is to make people type their seed into a PC, we know what we need to stop**. When the first hardware wallets were planned, there were multiple vectors they envisioned, and had safeguards to stop them: the first was a **man in the middle** attack. Meaning, someone would gain control over the PC (or phone, but when I say PC I mean the device that is connected to the network) or the network connection and then, when I try to send my coins, it will send the hardware wallet a different transaction. This is why there's a double verification in these wallets. When you send a transaction (or receive, BTW), you're prompted twice: once on your PC and once on the device, and you need to verify the transaction. The second vector was a **keylogger**; this means that someone has a listening device on your PC. This was neutralized by doing all the important stuff on your hardware wallet: the PIN is programmed there, the seed is programmed there and the transaction needs to verify there. This means that even if someone has control over your PC, without pushing the actual buttons on the hardware wallet, they can't take away your coins. But the fact is, that having such a good device still has the STUPID vector: people giving away their seed backup. The seed is the central point of failure: if it gets lost, you lose access to your coins, if it gets stolen, you lose access to your coins, if someone corrupts your seed, you lose access to your coins. Now, add to this that Ledger, one of the major players in the hardware wallet industry [suffered a severe hack](https://www.investopedia.com/hackers-leak-customer-info-from-crypto-wallet-ledger-5093577 ) that exposed email addresses. This means that if you were on this list, you most likely receive a dozen phishing emails per day. This is how they act. First, you receive a message which is meant to scare you: there is something wrong with your device; please log in. ![image.png](https://cdn.steemitimages.com/DQmegPxpV1KN5rAZ5e8gi5pG8XW3k9nTfWj2yMCpGoD9Z9a/image.png) Then, when you click this link, you will be transferred to a page where fake software would be downloaded. So what do you have to do in order to have better seed protection? the first is a backup; this means that you mitigate the risk of losing your seed. The new Trezor wallets have a [Shamir Backup]( https://trezor.io/shamir/ ) that provides excellent protection and recovery. The second is doing something in order to avoid having the seed written down on any PC. But you want to mitigate the risk of people entering their seed on a computer. In order to do this, you need to make sure it would be extremely difficult to enter the seed on a PC, while it would be extremely easy to do so on a hardware wallet. **The BIP-39 mnemonic is extremely easy on a PC compared to a recovery on a hardware wallet**. If we want to go from there to a new implementation, we need to use non-standard characters that are unique to the hardware wallet. Something like the [Klingon alphabet]( https://omniglot.com/conscripts/klingon.htm) or [Ugarit]( https://en.wikipedia.org/wiki/Ugaritic ). These are theoretically existent on a PC, but if some phishing software would request the 24-word seed, then a person typing it would need to install an Ugarit keyboard. In this case, if we're a hardware wallet company, we can purchase ads on the Google search for Ugarit keyboard, saying something like "did a software ask for your 24-word seed and you're looking for an Ugarit keyboard? you're being scammed". Adding this stage would increase security. Now; the problem is that the 24-word vector is the most used one, and the one that most people fall to. It is increased due to the recent hack to the Ledger database that caused targeted phishing scams. So in order to mitigate this, you need to reduce both the motivation and the ability of hackers to target people. Google is doing a great job with identifying phishing emails; but that's not good enough. Some people still fall to this scam. We, as a community need to better explain to people, again, how important is the 24 word seed; but we still need to understand that people will fall to this scam.
json metadata{"tags":["scams","phshing","crypto","bitcoin","ledger","trezor"],"image":["https://cdn.steemitimages.com/DQmPYmeiKHApvKQ3htUkAcbB4GabMggN8kw9JrwdBMJQZ7w/image.png","https://cdn.steemitimages.com/DQmegPxpV1KN5rAZ5e8gi5pG8XW3k9nTfWj2yMCpGoD9Z9a/image.png"],"links":["https://steemit.com/death/@jonklinger/be-prepared-how-to-manage-your-digital-assets-when-you-re-gone","https://iancoleman.io/bip39/","https://cryptosteel.com/product/cryptosteel/","https://wiki.trezor.io/User_manual:Advanced_recovery","https://www.amazon.com/gp/product/B08JSB5CHG","https://www.computerweekly.com/news/252476845/A-quarter-of-users-will-fall-for-basic-phishing-attacks","https://www.investopedia.com/hackers-leak-customer-info-from-crypto-wallet-ledger-5093577","https://trezor.io/shamir/","https://omniglot.com/conscripts/klingon.htm","https://en.wikipedia.org/wiki/Ugaritic"],"app":"steemit/0.2","format":"markdown"}
Transaction InfoBlock #51574019/Trx 081f199a847332196aeaaf3424576158969bb6bd
View Raw JSON Data
{
  "trx_id": "081f199a847332196aeaaf3424576158969bb6bd",
  "block": 51574019,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-02-27T11:39:03",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "hardware-wallets",
      "author": "jonklinger",
      "permlink": "why-phishing-crypto-seed-scamso-work-if-you-re-reading-this-you-re-basically-not-the-target-audience",
      "title": "Why phishing crypto seed scams work: If you're reading this you're basically not the target audience.",
      "body": "[A post on reddit]( https://steemit.com/death/@jonklinger/be-prepared-how-to-manage-your-digital-assets-when-you-re-gone )  triggered my will to explain this. TL;DR: some random person's bitcoins and ethers were stolen; he says he \"never\" provided his seed (I'll explain later) to anyone and he is not a victim of phishing. After answering a few comments, the truth is discovered: he downloaded a fake app that requested that he provide it with the seed, the seed was sent to hackers, all hope is gone.\n\nSo; how did this happen? in order for this to happen, several failures had to occur. The first is the seed. Now, what is a seed? A seed is a 24-word passphrase that is basically a backup of your bitcoin wallet. I [wrote about it]( https://steemit.com/death/@jonklinger/be-prepared-how-to-manage-your-digital-assets-when-you-re-gone ) when explaining how to backup your wallet. In [BIP-39]( https://iancoleman.io/bip39/ ) an improvement to the bitcoin protocol was implemented: each wallet has an \"easy to store\" seed, comprising of 24 words, that generate the private key. These words should be kept safe in storage, and only used to restore the wallet. I use [cryptosteel]( https://cryptosteel.com/product/cryptosteel/ ) (not an affiliate link) in order to backup my seed. \n\nNow, the first thing that a hardware wallet tells you is to never put this seed on a computer. It should always be typed into the hardware wallet itself ([there's something a bit different on Trezor One]( https://wiki.trezor.io/User_manual:Advanced_recovery ) ). This is the first rule of recovering a wallet: never, but never, I mean **never** type your seed on a PC.\n\nSo, the poor chap that had his coins stolen broke this rule. Why did he break the rule? because he saw an error message that said \"please restore your wallet\". Now, this is one of the reasons that you always need to question authority. Even when software prompts for a password, you need to stop and think on what you're doing. Is this the right site or app? Why is it asking this.\n\n\n![image.png](https://cdn.steemitimages.com/DQmPYmeiKHApvKQ3htUkAcbB4GabMggN8kw9JrwdBMJQZ7w/image.png)\n\n\nI've just finished Ira Winkler's \"[You CAN stop stupid]( https://www.amazon.com/gp/product/B08JSB5CHG )\", a book about security, cybersecurity and the human factor. Ira keeps repeating a large percentage of people fall for phishing scams no matter what we do ([and he's right]( https://www.computerweekly.com/news/252476845/A-quarter-of-users-will-fall-for-basic-phishing-attacks ) ). \n\n**So; if we know that the vector is to make people type their seed into a PC, we know what we need to stop**. When the first hardware wallets were planned, there were multiple vectors they envisioned, and had safeguards to stop them: the first was a **man in the middle** attack. Meaning, someone would gain control over the PC (or phone, but when I say PC I mean the device that is connected to the network) or the network connection and then, when I try to send my coins, it will send the hardware wallet a different transaction. This is why there's a double verification in these wallets. When you send a transaction (or receive, BTW), you're prompted twice: once on your PC and once on the device, and you need to verify the transaction.\n\nThe second vector was a **keylogger**; this means that someone has a listening device on your PC. This was neutralized by doing all the important stuff on your hardware wallet: the PIN is programmed there, the seed is programmed there and the transaction needs to verify there. This means that even if someone has control over your PC, without pushing the actual buttons on the hardware wallet, they can't take away your coins.\n\nBut the fact is, that having such a good device still has the STUPID vector: people giving away their seed backup. The seed is the central point of failure: if it gets lost, you lose access to your coins, if it gets stolen, you lose access to your coins, if someone corrupts your seed, you lose access to your coins.\n\nNow, add to this that Ledger, one of the major players in the hardware wallet industry [suffered a severe hack](https://www.investopedia.com/hackers-leak-customer-info-from-crypto-wallet-ledger-5093577 ) that exposed email addresses. This means that if you were on this list, you most likely receive a dozen phishing emails per day. This is how they act. \n\nFirst, you receive a message which is meant to scare you: there is something wrong with your device; please log in.\n\n\n![image.png](https://cdn.steemitimages.com/DQmegPxpV1KN5rAZ5e8gi5pG8XW3k9nTfWj2yMCpGoD9Z9a/image.png)\n\nThen, when you click this link, you will be transferred to a page where fake software would be downloaded. \n\nSo what do you have to do in order to have better seed protection? the first is a backup; this means that you mitigate the risk of losing your seed. The new Trezor wallets have a [Shamir Backup]( https://trezor.io/shamir/ ) that provides excellent protection and recovery.  The second is doing something in order to avoid having the seed written down on any PC. \n\nBut you want to mitigate the risk of people entering their seed on a computer. In order to do this, you need to make sure it would be extremely difficult to enter the seed on a PC, while it would be extremely easy to do so on a hardware wallet. \n\n**The BIP-39 mnemonic is extremely easy on a PC compared to a recovery on a hardware wallet**. If we want to go from there to a new implementation, we need to use non-standard characters that are unique to the hardware wallet. Something like the [Klingon alphabet]( https://omniglot.com/conscripts/klingon.htm) or [Ugarit]( https://en.wikipedia.org/wiki/Ugaritic ). These are theoretically existent on a PC, but if some phishing software would request the 24-word seed, then a person typing it would need to install an Ugarit keyboard.\n\nIn this case, if we're a hardware wallet company, we can purchase ads on the Google search for Ugarit keyboard, saying something like \"did a software ask for your 24-word seed and you're looking for an Ugarit keyboard? you're being scammed\".\n\nAdding this stage would increase security. \n\nNow; the problem is that the 24-word vector is the most used one, and the one that most people fall to. It is increased due to the recent hack to the Ledger database that caused targeted phishing scams. So in order to mitigate this, you need to reduce both the motivation and the ability of hackers to target people. Google is doing a great job with identifying phishing emails; but that's not good enough. Some people still fall to this scam. \n\nWe, as a community need to better explain to people, again, how important is the 24 word seed; but we still need to understand that people will fall to this scam.",
      "json_metadata": "{\"tags\":[\"scams\",\"phshing\",\"crypto\",\"bitcoin\",\"ledger\",\"trezor\"],\"image\":[\"https://cdn.steemitimages.com/DQmPYmeiKHApvKQ3htUkAcbB4GabMggN8kw9JrwdBMJQZ7w/image.png\",\"https://cdn.steemitimages.com/DQmegPxpV1KN5rAZ5e8gi5pG8XW3k9nTfWj2yMCpGoD9Z9a/image.png\"],\"links\":[\"https://steemit.com/death/@jonklinger/be-prepared-how-to-manage-your-digital-assets-when-you-re-gone\",\"https://iancoleman.io/bip39/\",\"https://cryptosteel.com/product/cryptosteel/\",\"https://wiki.trezor.io/User_manual:Advanced_recovery\",\"https://www.amazon.com/gp/product/B08JSB5CHG\",\"https://www.computerweekly.com/news/252476845/A-quarter-of-users-will-fall-for-basic-phishing-attacks\",\"https://www.investopedia.com/hackers-leak-customer-info-from-crypto-wallet-ledger-5093577\",\"https://trezor.io/shamir/\",\"https://omniglot.com/conscripts/klingon.htm\",\"https://en.wikipedia.org/wiki/Ugaritic\"],\"app\":\"steemit/0.2\",\"format\":\"markdown\"}"
    }
  ]
}
2021/02/27 11:38:36
parent author
parent permlinkhardware-wallets
authorjonklinger
permlinkwhy-phishing-crypto-seed-scamso-work-if-you-re-reading-this-you-re-basically-not-the-target-audience
titleWhy phishing crypto seed scam work: If you're reading this you're basically not the target audience.
body[A post on reddit]( https://steemit.com/death/@jonklinger/be-prepared-how-to-manage-your-digital-assets-when-you-re-gone ) triggered my will to explain this. TL;DR: some random person's bitcoins and ethers were stolen; he says he "never" provided his seed (I'll explain later) to anyone and he is not a victim of phishing. After answering a few comments, the truth is discovered: he downloaded a fake app that requested that he provide it with the seed, the seed was sent to hackers, all hope is gone. So; how did this happen? in order for this to happen, several failures had to occur. The first is the seed. Now, what is a seed? A seed is a 24-word passphrase that is basically a backup of your bitcoin wallet. I [wrote about it]( https://steemit.com/death/@jonklinger/be-prepared-how-to-manage-your-digital-assets-when-you-re-gone ) when explaining how to backup your wallet. In [BIP-39]( https://iancoleman.io/bip39/ ) an improvement to the bitcoin protocol was implemented: each wallet has an "easy to store" seed, comprising of 24 words, that generate the private key. These words should be kept safe in storage, and only used to restore the wallet. I use [cryptosteel]( https://cryptosteel.com/product/cryptosteel/ ) (not an affiliate link) in order to backup my seed. Now, the first thing that a hardware wallet tells you is to never put this seed on a computer. It should always be typed into the hardware wallet itself ([there's something a bit different on Trezor One]( https://wiki.trezor.io/User_manual:Advanced_recovery ) ). This is the first rule of recovering a wallet: never, but never, I mean **never** type your seed on a PC. So, the poor chap that had his coins stolen broke this rule. Why did he break the rule? because he saw an error message that said "please restore your wallet". Now, this is one of the reasons that you always need to question authority. Even when software prompts for a password, you need to stop and think on what you're doing. Is this the right site or app? Why is it asking this. ![image.png](https://cdn.steemitimages.com/DQmPYmeiKHApvKQ3htUkAcbB4GabMggN8kw9JrwdBMJQZ7w/image.png) I've just finished Ira Winkler's "[You CAN stop stupid]( https://www.amazon.com/gp/product/B08JSB5CHG )", a book about security, cybersecurity and the human factor. Ira keeps repeating a large percentage of people fall for phishing scams no matter what we do ([and he's right]( https://www.computerweekly.com/news/252476845/A-quarter-of-users-will-fall-for-basic-phishing-attacks ) ). **So; if we know that the vector is to make people type their seed into a PC, we know what we need to stop**. When the first hardware wallets were planned, there were multiple vectors they envisioned, and had safeguards to stop them: the first was a **man in the middle** attack. Meaning, someone would gain control over the PC (or phone, but when I say PC I mean the device that is connected to the network) or the network connection and then, when I try to send my coins, it will send the hardware wallet a different transaction. This is why there's a double verification in these wallets. When you send a transaction (or receive, BTW), you're prompted twice: once on your PC and once on the device, and you need to verify the transaction. The second vector was a **keylogger**; this means that someone has a listening device on your PC. This was neutralized by doing all the important stuff on your hardware wallet: the PIN is programmed there, the seed is programmed there and the transaction needs to verify there. This means that even if someone has control over your PC, without pushing the actual buttons on the hardware wallet, they can't take away your coins. But the fact is, that having such a good device still has the STUPID vector: people giving away their seed backup. The seed is the central point of failure: if it gets lost, you lose access to your coins, if it gets stolen, you lose access to your coins, if someone corrupts your seed, you lose access to your coins. Now, add to this that Ledger, one of the major players in the hardware wallet industry [suffered a severe hack](https://www.investopedia.com/hackers-leak-customer-info-from-crypto-wallet-ledger-5093577 ) that exposed email addresses. This means that if you were on this list, you most likely receive a dozen phishing emails per day. This is how they act. First, you receive a message which is meant to scare you: there is something wrong with your device; please log in. ![image.png](https://cdn.steemitimages.com/DQmegPxpV1KN5rAZ5e8gi5pG8XW3k9nTfWj2yMCpGoD9Z9a/image.png) Then, when you click this link, you will be transferred to a page where fake software would be downloaded. So what do you have to do in order to have better seed protection? the first is a backup; this means that you mitigate the risk of losing your seed. The new Trezor wallets have a [Shamir Backup]( https://trezor.io/shamir/ ) that provides excellent protection and recovery. The second is doing something in order to avoid having the seed written down on any PC. But you want to mitigate the risk of people entering their seed on a computer. In order to do this, you need to make sure it would be extremely difficult to enter the seed on a PC, while it would be extremely easy to do so on a hardware wallet. **The BIP-39 mnemonic is extremely easy on a PC compared to a recovery on a hardware wallet**. If we want to go from there to a new implementation, we need to use non-standard characters that are unique to the hardware wallet. Something like the [Klingon alphabet]( https://omniglot.com/conscripts/klingon.htm) or [Ugarit]( https://en.wikipedia.org/wiki/Ugaritic ). These are theoretically existent on a PC, but if some phishing software would request the 24-word seed, then a person typing it would need to install an Ugarit keyboard. In this case, if we're a hardware wallet company, we can purchase ads on the Google search for Ugarit keyboard, saying something like "did a software ask for your 24-word seed and you're looking for an Ugarit keyboard? you're being scammed". Adding this stage would increase security. Now; the problem is that the 24-word vector is the most used one, and the one that most people fall to. It is increased due to the recent hack to the Ledger database that caused targeted phishing scams. So in order to mitigate this, you need to reduce both the motivation and the ability of hackers to target people. Google is doing a great job with identifying phishing emails; but that's not good enough. Some people still fall to this scam. We, as a community need to better explain to people, again, how important is the 24 word seed; but we still need to understand that people will fall to this scam.
json metadata{"tags":["scams","phshing","crypto","bitcoin","ledger","trezor"],"image":["https://cdn.steemitimages.com/DQmPYmeiKHApvKQ3htUkAcbB4GabMggN8kw9JrwdBMJQZ7w/image.png","https://cdn.steemitimages.com/DQmegPxpV1KN5rAZ5e8gi5pG8XW3k9nTfWj2yMCpGoD9Z9a/image.png"],"links":["https://steemit.com/death/@jonklinger/be-prepared-how-to-manage-your-digital-assets-when-you-re-gone","https://iancoleman.io/bip39/","https://cryptosteel.com/product/cryptosteel/","https://wiki.trezor.io/User_manual:Advanced_recovery","https://www.amazon.com/gp/product/B08JSB5CHG","https://www.computerweekly.com/news/252476845/A-quarter-of-users-will-fall-for-basic-phishing-attacks","https://www.investopedia.com/hackers-leak-customer-info-from-crypto-wallet-ledger-5093577","https://trezor.io/shamir/","https://omniglot.com/conscripts/klingon.htm","https://en.wikipedia.org/wiki/Ugaritic"],"app":"steemit/0.2","format":"markdown"}
Transaction InfoBlock #51574010/Trx 12a21953ee6a37a5fc6b381f08cf530417b43201
View Raw JSON Data
{
  "trx_id": "12a21953ee6a37a5fc6b381f08cf530417b43201",
  "block": 51574010,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-02-27T11:38:36",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "hardware-wallets",
      "author": "jonklinger",
      "permlink": "why-phishing-crypto-seed-scamso-work-if-you-re-reading-this-you-re-basically-not-the-target-audience",
      "title": "Why phishing crypto seed scam work: If you're reading this you're basically not the target audience.",
      "body": "[A post on reddit]( https://steemit.com/death/@jonklinger/be-prepared-how-to-manage-your-digital-assets-when-you-re-gone )  triggered my will to explain this. TL;DR: some random person's bitcoins and ethers were stolen; he says he \"never\" provided his seed (I'll explain later) to anyone and he is not a victim of phishing. After answering a few comments, the truth is discovered: he downloaded a fake app that requested that he provide it with the seed, the seed was sent to hackers, all hope is gone.\n\nSo; how did this happen? in order for this to happen, several failures had to occur. The first is the seed. Now, what is a seed? A seed is a 24-word passphrase that is basically a backup of your bitcoin wallet. I [wrote about it]( https://steemit.com/death/@jonklinger/be-prepared-how-to-manage-your-digital-assets-when-you-re-gone ) when explaining how to backup your wallet. In [BIP-39]( https://iancoleman.io/bip39/ ) an improvement to the bitcoin protocol was implemented: each wallet has an \"easy to store\" seed, comprising of 24 words, that generate the private key. These words should be kept safe in storage, and only used to restore the wallet. I use [cryptosteel]( https://cryptosteel.com/product/cryptosteel/ ) (not an affiliate link) in order to backup my seed. \n\nNow, the first thing that a hardware wallet tells you is to never put this seed on a computer. It should always be typed into the hardware wallet itself ([there's something a bit different on Trezor One]( https://wiki.trezor.io/User_manual:Advanced_recovery ) ). This is the first rule of recovering a wallet: never, but never, I mean **never** type your seed on a PC.\n\nSo, the poor chap that had his coins stolen broke this rule. Why did he break the rule? because he saw an error message that said \"please restore your wallet\". Now, this is one of the reasons that you always need to question authority. Even when software prompts for a password, you need to stop and think on what you're doing. Is this the right site or app? Why is it asking this.\n\n\n![image.png](https://cdn.steemitimages.com/DQmPYmeiKHApvKQ3htUkAcbB4GabMggN8kw9JrwdBMJQZ7w/image.png)\n\n\nI've just finished Ira Winkler's \"[You CAN stop stupid]( https://www.amazon.com/gp/product/B08JSB5CHG )\", a book about security, cybersecurity and the human factor. Ira keeps repeating a large percentage of people fall for phishing scams no matter what we do ([and he's right]( https://www.computerweekly.com/news/252476845/A-quarter-of-users-will-fall-for-basic-phishing-attacks ) ). \n\n**So; if we know that the vector is to make people type their seed into a PC, we know what we need to stop**. When the first hardware wallets were planned, there were multiple vectors they envisioned, and had safeguards to stop them: the first was a **man in the middle** attack. Meaning, someone would gain control over the PC (or phone, but when I say PC I mean the device that is connected to the network) or the network connection and then, when I try to send my coins, it will send the hardware wallet a different transaction. This is why there's a double verification in these wallets. When you send a transaction (or receive, BTW), you're prompted twice: once on your PC and once on the device, and you need to verify the transaction.\n\nThe second vector was a **keylogger**; this means that someone has a listening device on your PC. This was neutralized by doing all the important stuff on your hardware wallet: the PIN is programmed there, the seed is programmed there and the transaction needs to verify there. This means that even if someone has control over your PC, without pushing the actual buttons on the hardware wallet, they can't take away your coins.\n\nBut the fact is, that having such a good device still has the STUPID vector: people giving away their seed backup. The seed is the central point of failure: if it gets lost, you lose access to your coins, if it gets stolen, you lose access to your coins, if someone corrupts your seed, you lose access to your coins.\n\nNow, add to this that Ledger, one of the major players in the hardware wallet industry [suffered a severe hack](https://www.investopedia.com/hackers-leak-customer-info-from-crypto-wallet-ledger-5093577 ) that exposed email addresses. This means that if you were on this list, you most likely receive a dozen phishing emails per day. This is how they act. \n\nFirst, you receive a message which is meant to scare you: there is something wrong with your device; please log in.\n\n\n![image.png](https://cdn.steemitimages.com/DQmegPxpV1KN5rAZ5e8gi5pG8XW3k9nTfWj2yMCpGoD9Z9a/image.png)\n\nThen, when you click this link, you will be transferred to a page where fake software would be downloaded. \n\nSo what do you have to do in order to have better seed protection? the first is a backup; this means that you mitigate the risk of losing your seed. The new Trezor wallets have a [Shamir Backup]( https://trezor.io/shamir/ ) that provides excellent protection and recovery.  The second is doing something in order to avoid having the seed written down on any PC. \n\nBut you want to mitigate the risk of people entering their seed on a computer. In order to do this, you need to make sure it would be extremely difficult to enter the seed on a PC, while it would be extremely easy to do so on a hardware wallet. \n\n**The BIP-39 mnemonic is extremely easy on a PC compared to a recovery on a hardware wallet**. If we want to go from there to a new implementation, we need to use non-standard characters that are unique to the hardware wallet. Something like the [Klingon alphabet]( https://omniglot.com/conscripts/klingon.htm) or [Ugarit]( https://en.wikipedia.org/wiki/Ugaritic ). These are theoretically existent on a PC, but if some phishing software would request the 24-word seed, then a person typing it would need to install an Ugarit keyboard.\n\nIn this case, if we're a hardware wallet company, we can purchase ads on the Google search for Ugarit keyboard, saying something like \"did a software ask for your 24-word seed and you're looking for an Ugarit keyboard? you're being scammed\".\n\nAdding this stage would increase security. \n\nNow; the problem is that the 24-word vector is the most used one, and the one that most people fall to. It is increased due to the recent hack to the Ledger database that caused targeted phishing scams. So in order to mitigate this, you need to reduce both the motivation and the ability of hackers to target people. Google is doing a great job with identifying phishing emails; but that's not good enough. Some people still fall to this scam. \n\nWe, as a community need to better explain to people, again, how important is the 24 word seed; but we still need to understand that people will fall to this scam.",
      "json_metadata": "{\"tags\":[\"scams\",\"phshing\",\"crypto\",\"bitcoin\",\"ledger\",\"trezor\"],\"image\":[\"https://cdn.steemitimages.com/DQmPYmeiKHApvKQ3htUkAcbB4GabMggN8kw9JrwdBMJQZ7w/image.png\",\"https://cdn.steemitimages.com/DQmegPxpV1KN5rAZ5e8gi5pG8XW3k9nTfWj2yMCpGoD9Z9a/image.png\"],\"links\":[\"https://steemit.com/death/@jonklinger/be-prepared-how-to-manage-your-digital-assets-when-you-re-gone\",\"https://iancoleman.io/bip39/\",\"https://cryptosteel.com/product/cryptosteel/\",\"https://wiki.trezor.io/User_manual:Advanced_recovery\",\"https://www.amazon.com/gp/product/B08JSB5CHG\",\"https://www.computerweekly.com/news/252476845/A-quarter-of-users-will-fall-for-basic-phishing-attacks\",\"https://www.investopedia.com/hackers-leak-customer-info-from-crypto-wallet-ledger-5093577\",\"https://trezor.io/shamir/\",\"https://omniglot.com/conscripts/klingon.htm\",\"https://en.wikipedia.org/wiki/Ugaritic\"],\"app\":\"steemit/0.2\",\"format\":\"markdown\"}"
    }
  ]
}
2021/02/27 09:59:24
votertechslut
authorjonklinger
permlinkwhy-phishing-crypto-seed-scamso-work-if-you-re-reading-this-you-re-basically-not-the-target-audience
weight10000 (100.00%)
Transaction InfoBlock #51572045/Trx 38155ed05ad84954cd9e3e7c8bcbc9e9c009186b
View Raw JSON Data
{
  "trx_id": "38155ed05ad84954cd9e3e7c8bcbc9e9c009186b",
  "block": 51572045,
  "trx_in_block": 3,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-02-27T09:59:24",
  "op": [
    "vote",
    {
      "voter": "techslut",
      "author": "jonklinger",
      "permlink": "why-phishing-crypto-seed-scamso-work-if-you-re-reading-this-you-re-basically-not-the-target-audience",
      "weight": 10000
    }
  ]
}
2021/02/27 09:57:24
parent author
parent permlinkhardware-wallets
authorjonklinger
permlinkwhy-phishing-crypto-seed-scamso-work-if-you-re-reading-this-you-re-basically-not-the-target-audience
titleWhy phishing crypto seed scamso work: If you're reading this you're basically not the target audience.
body[A post on reddit]( https://steemit.com/death/@jonklinger/be-prepared-how-to-manage-your-digital-assets-when-you-re-gone ) triggered my will to explain this. TL;DR: some random person's bitcoins and ethers were stolen; he says he "never" provided his seed (I'll explain later) to anyone and he is not a victim of phishing. After answering a few comments, the truth is discovered: he downloaded a fake app that requested that he provide it with the seed, the seed was sent to hackers, all hope is gone. So; how did this happen? in order for this to happen, several failures had to occur. The first is the seed. Now, what is a seed? A seed is a 24-word passphrase that is basically a backup of your bitcoin wallet. I [wrote about it]( https://steemit.com/death/@jonklinger/be-prepared-how-to-manage-your-digital-assets-when-you-re-gone ) when explaining how to backup your wallet. In [BIP-39]( https://iancoleman.io/bip39/ ) an improvement to the bitcoin protocol was implemented: each wallet has an "easy to store" seed, comprising of 24 words, that generate the private key. These words should be kept safe in storage, and only used to restore the wallet. I use [cryptosteel]( https://cryptosteel.com/product/cryptosteel/ ) (not an affiliate link) in order to backup my seed. Now, the first thing that a hardware wallet tells you is to never put this seed on a computer. It should always be typed into the hardware wallet itself ([there's something a bit different on Trezor One]( https://wiki.trezor.io/User_manual:Advanced_recovery ) ). This is the first rule of recovering a wallet: never, but never, I mean **never** type your seed on a PC. So, the poor chap that had his coins stolen broke this rule. Why did he break the rule? because he saw an error message that said "please restore your wallet". Now, this is one of the reasons that you always need to question authority. Even when software prompts for a password, you need to stop and think on what you're doing. Is this the right site or app? Why is it asking this. ![image.png](https://cdn.steemitimages.com/DQmPYmeiKHApvKQ3htUkAcbB4GabMggN8kw9JrwdBMJQZ7w/image.png) I've just finished Ira Winkler's "[You CAN stop stupid]( https://www.amazon.com/gp/product/B08JSB5CHG )", a book about security, cybersecurity and the human factor. Ira keeps repeating a large percentage of people fall for phishing scams no matter what we do ([and he's right]( https://www.computerweekly.com/news/252476845/A-quarter-of-users-will-fall-for-basic-phishing-attacks ) ). **So; if we know that the vector is to make people type their seed into a PC, we know what we need to stop**. When the first hardware wallets were planned, there were multiple vectors they envisioned, and had safeguards to stop them: the first was a **man in the middle** attack. Meaning, someone would gain control over the PC (or phone, but when I say PC I mean the device that is connected to the network) or the network connection and then, when I try to send my coins, it will send the hardware wallet a different transaction. This is why there's a double verification in these wallets. When you send a transaction (or receive, BTW), you're prompted twice: once on your PC and once on the device, and you need to verify the transaction. The second vector was a **keylogger**; this means that someone has a listening device on your PC. This was neutralized by doing all the important stuff on your hardware wallet: the PIN is programmed there, the seed is programmed there and the transaction needs to verify there. This means that even if someone has control over your PC, without pushing the actual buttons on the hardware wallet, they can't take away your coins. But the fact is, that having such a good device still has the STUPID vector: people giving away their seed backup. The seed is the central point of failure: if it gets lost, you lose access to your coins, if it gets stolen, you lose access to your coins, if someone corrupts your seed, you lose access to your coins. Now, add to this that Ledger, one of the major players in the hardware wallet industry [suffered a severe hack](https://www.investopedia.com/hackers-leak-customer-info-from-crypto-wallet-ledger-5093577 ) that exposed email addresses. This means that if you were on this list, you most likely receive a dozen phishing emails per day. This is how they act. First, you receive a message which is meant to scare you: there is something wrong with your device; please log in. ![image.png](https://cdn.steemitimages.com/DQmegPxpV1KN5rAZ5e8gi5pG8XW3k9nTfWj2yMCpGoD9Z9a/image.png) Then, when you click this link, you will be transferred to a page where fake software would be downloaded. So what do you have to do in order to have better seed protection? the first is a backup; this means that you mitigate the risk of losing your seed. The new Trezor wallets have a [Shamir Backup]( https://trezor.io/shamir/ ) that provides excellent protection and recovery. The second is doing something in order to avoid having the seed written down on any PC. But you want to mitigate the risk of people entering their seed on a computer. In order to do this, you need to make sure it would be extremely difficult to enter the seed on a PC, while it would be extremely easy to do so on a hardware wallet. **The BIP-39 mnemonic is extremely easy on a PC compared to a recovery on a hardware wallet**. If we want to go from there to a new implementation, we need to use non-standard characters that are unique to the hardware wallet. Something like the [Klingon alphabet]( https://omniglot.com/conscripts/klingon.htm) or [Ugarit]( https://en.wikipedia.org/wiki/Ugaritic ). These are theoretically existent on a PC, but if some phishing software would request the 24-word seed, then a person typing it would need to install an Ugarit keyboard. In this case, if we're a hardware wallet company, we can purchase ads on the Google search for Ugarit keyboard, saying something like "did a software ask for your 24-word seed and you're looking for an Ugarit keyboard? you're being scammed". Adding this stage would increase security. Now; the problem is that the 24-word vector is the most used one, and the one that most people fall to. It is increased due to the recent hack to the Ledger database that caused targeted phishing scams. So in order to mitigate this, you need to reduce both the motivation and the ability of hackers to target people. Google is doing a great job with identifying phishing emails; but that's not good enough. Some people still fall to this scam. We, as a community need to better explain to people, again, how important is the 24 word seed; but we still need to understand that people will fall to this scam.
json metadata{"tags":["hardware-wallets","scams","phshing","crypto","bitcoin","ledger","trezor"],"image":["https://cdn.steemitimages.com/DQmPYmeiKHApvKQ3htUkAcbB4GabMggN8kw9JrwdBMJQZ7w/image.png","https://cdn.steemitimages.com/DQmegPxpV1KN5rAZ5e8gi5pG8XW3k9nTfWj2yMCpGoD9Z9a/image.png"],"links":["https://steemit.com/death/@jonklinger/be-prepared-how-to-manage-your-digital-assets-when-you-re-gone","https://iancoleman.io/bip39/","https://cryptosteel.com/product/cryptosteel/","https://wiki.trezor.io/User_manual:Advanced_recovery","https://www.amazon.com/gp/product/B08JSB5CHG","https://www.computerweekly.com/news/252476845/A-quarter-of-users-will-fall-for-basic-phishing-attacks","https://www.investopedia.com/hackers-leak-customer-info-from-crypto-wallet-ledger-5093577","https://trezor.io/shamir/","https://omniglot.com/conscripts/klingon.htm","https://en.wikipedia.org/wiki/Ugaritic"],"app":"steemit/0.2","format":"markdown"}
Transaction InfoBlock #51572006/Trx 27261cc87f04b6762e6852f2b032627f3098831c
View Raw JSON Data
{
  "trx_id": "27261cc87f04b6762e6852f2b032627f3098831c",
  "block": 51572006,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-02-27T09:57:24",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "hardware-wallets",
      "author": "jonklinger",
      "permlink": "why-phishing-crypto-seed-scamso-work-if-you-re-reading-this-you-re-basically-not-the-target-audience",
      "title": "Why phishing crypto seed scamso work: If you're reading this you're basically not the target audience.",
      "body": "[A post on reddit]( https://steemit.com/death/@jonklinger/be-prepared-how-to-manage-your-digital-assets-when-you-re-gone )  triggered my will to explain this. TL;DR: some random person's bitcoins and ethers were stolen; he says he \"never\" provided his seed (I'll explain later) to anyone and he is not a victim of phishing. After answering a few comments, the truth is discovered: he downloaded a fake app that requested that he provide it with the seed, the seed was sent to hackers, all hope is gone.\n\nSo; how did this happen? in order for this to happen, several failures had to occur. The first is the seed. Now, what is a seed? A seed is a 24-word passphrase that is basically a backup of your bitcoin wallet. I [wrote about it]( https://steemit.com/death/@jonklinger/be-prepared-how-to-manage-your-digital-assets-when-you-re-gone ) when explaining how to backup your wallet. In [BIP-39]( https://iancoleman.io/bip39/ ) an improvement to the bitcoin protocol was implemented: each wallet has an \"easy to store\" seed, comprising of 24 words, that generate the private key. These words should be kept safe in storage, and only used to restore the wallet. I use [cryptosteel]( https://cryptosteel.com/product/cryptosteel/ ) (not an affiliate link) in order to backup my seed. \n\nNow, the first thing that a hardware wallet tells you is to never put this seed on a computer. It should always be typed into the hardware wallet itself ([there's something a bit different on Trezor One]( https://wiki.trezor.io/User_manual:Advanced_recovery ) ). This is the first rule of recovering a wallet: never, but never, I mean **never** type your seed on a PC.\n\nSo, the poor chap that had his coins stolen broke this rule. Why did he break the rule? because he saw an error message that said \"please restore your wallet\". Now, this is one of the reasons that you always need to question authority. Even when software prompts for a password, you need to stop and think on what you're doing. Is this the right site or app? Why is it asking this.\n\n\n![image.png](https://cdn.steemitimages.com/DQmPYmeiKHApvKQ3htUkAcbB4GabMggN8kw9JrwdBMJQZ7w/image.png)\n\n\nI've just finished Ira Winkler's \"[You CAN stop stupid]( https://www.amazon.com/gp/product/B08JSB5CHG )\", a book about security, cybersecurity and the human factor. Ira keeps repeating a large percentage of people fall for phishing scams no matter what we do ([and he's right]( https://www.computerweekly.com/news/252476845/A-quarter-of-users-will-fall-for-basic-phishing-attacks ) ). \n\n**So; if we know that the vector is to make people type their seed into a PC, we know what we need to stop**. When the first hardware wallets were planned, there were multiple vectors they envisioned, and had safeguards to stop them: the first was a **man in the middle** attack. Meaning, someone would gain control over the PC (or phone, but when I say PC I mean the device that is connected to the network) or the network connection and then, when I try to send my coins, it will send the hardware wallet a different transaction. This is why there's a double verification in these wallets. When you send a transaction (or receive, BTW), you're prompted twice: once on your PC and once on the device, and you need to verify the transaction.\n\nThe second vector was a **keylogger**; this means that someone has a listening device on your PC. This was neutralized by doing all the important stuff on your hardware wallet: the PIN is programmed there, the seed is programmed there and the transaction needs to verify there. This means that even if someone has control over your PC, without pushing the actual buttons on the hardware wallet, they can't take away your coins.\n\nBut the fact is, that having such a good device still has the STUPID vector: people giving away their seed backup. The seed is the central point of failure: if it gets lost, you lose access to your coins, if it gets stolen, you lose access to your coins, if someone corrupts your seed, you lose access to your coins.\n\nNow, add to this that Ledger, one of the major players in the hardware wallet industry [suffered a severe hack](https://www.investopedia.com/hackers-leak-customer-info-from-crypto-wallet-ledger-5093577 ) that exposed email addresses. This means that if you were on this list, you most likely receive a dozen phishing emails per day. This is how they act. \n\nFirst, you receive a message which is meant to scare you: there is something wrong with your device; please log in.\n\n\n![image.png](https://cdn.steemitimages.com/DQmegPxpV1KN5rAZ5e8gi5pG8XW3k9nTfWj2yMCpGoD9Z9a/image.png)\n\nThen, when you click this link, you will be transferred to a page where fake software would be downloaded. \n\nSo what do you have to do in order to have better seed protection? the first is a backup; this means that you mitigate the risk of losing your seed. The new Trezor wallets have a [Shamir Backup]( https://trezor.io/shamir/ ) that provides excellent protection and recovery.  The second is doing something in order to avoid having the seed written down on any PC. \n\nBut you want to mitigate the risk of people entering their seed on a computer. In order to do this, you need to make sure it would be extremely difficult to enter the seed on a PC, while it would be extremely easy to do so on a hardware wallet. \n\n**The BIP-39 mnemonic is extremely easy on a PC compared to a recovery on a hardware wallet**. If we want to go from there to a new implementation, we need to use non-standard characters that are unique to the hardware wallet. Something like the [Klingon alphabet]( https://omniglot.com/conscripts/klingon.htm) or [Ugarit]( https://en.wikipedia.org/wiki/Ugaritic ). These are theoretically existent on a PC, but if some phishing software would request the 24-word seed, then a person typing it would need to install an Ugarit keyboard.\n\nIn this case, if we're a hardware wallet company, we can purchase ads on the Google search for Ugarit keyboard, saying something like \"did a software ask for your 24-word seed and you're looking for an Ugarit keyboard? you're being scammed\".\n\nAdding this stage would increase security. \n\nNow; the problem is that the 24-word vector is the most used one, and the one that most people fall to. It is increased due to the recent hack to the Ledger database that caused targeted phishing scams. So in order to mitigate this, you need to reduce both the motivation and the ability of hackers to target people. Google is doing a great job with identifying phishing emails; but that's not good enough. Some people still fall to this scam. \n\nWe, as a community need to better explain to people, again, how important is the 24 word seed; but we still need to understand that people will fall to this scam.",
      "json_metadata": "{\"tags\":[\"hardware-wallets\",\"scams\",\"phshing\",\"crypto\",\"bitcoin\",\"ledger\",\"trezor\"],\"image\":[\"https://cdn.steemitimages.com/DQmPYmeiKHApvKQ3htUkAcbB4GabMggN8kw9JrwdBMJQZ7w/image.png\",\"https://cdn.steemitimages.com/DQmegPxpV1KN5rAZ5e8gi5pG8XW3k9nTfWj2yMCpGoD9Z9a/image.png\"],\"links\":[\"https://steemit.com/death/@jonklinger/be-prepared-how-to-manage-your-digital-assets-when-you-re-gone\",\"https://iancoleman.io/bip39/\",\"https://cryptosteel.com/product/cryptosteel/\",\"https://wiki.trezor.io/User_manual:Advanced_recovery\",\"https://www.amazon.com/gp/product/B08JSB5CHG\",\"https://www.computerweekly.com/news/252476845/A-quarter-of-users-will-fall-for-basic-phishing-attacks\",\"https://www.investopedia.com/hackers-leak-customer-info-from-crypto-wallet-ledger-5093577\",\"https://trezor.io/shamir/\",\"https://omniglot.com/conscripts/klingon.htm\",\"https://en.wikipedia.org/wiki/Ugaritic\"],\"app\":\"steemit/0.2\",\"format\":\"markdown\"}"
    }
  ]
}
2021/01/16 22:18:30
parent authorjonklinger
parent permlinkbe-prepared-how-to-manage-your-digital-assets-when-you-re-gone
authorschmidtj2
permlinkqn1smr
title
bodyWhat happens when your attorney retires to Mexico, your brother dies, and your friend from college that nobody else knows changes his phone number and email address? Yikes. Great article with lots of good thoughts, and i loved reading it. seems like there are still plenty of opportunities for that money to evaporate if one or two requisite elements aren't quite there
json metadata{"app":"steemit/0.2"}
Transaction InfoBlock #50391984/Trx 254918ba9c54965a69502a009667c0ddc56db3cb
View Raw JSON Data
{
  "trx_id": "254918ba9c54965a69502a009667c0ddc56db3cb",
  "block": 50391984,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-01-16T22:18:30",
  "op": [
    "comment",
    {
      "parent_author": "jonklinger",
      "parent_permlink": "be-prepared-how-to-manage-your-digital-assets-when-you-re-gone",
      "author": "schmidtj2",
      "permlink": "qn1smr",
      "title": "",
      "body": "What happens when your attorney retires to Mexico, your brother dies, and your friend from college that nobody else knows changes his phone number and email address?  Yikes.  Great article with lots of good thoughts, and i loved reading it.  seems like there are still plenty of opportunities for that money to evaporate if one or two requisite elements aren't quite there",
      "json_metadata": "{\"app\":\"steemit/0.2\"}"
    }
  ]
}
blurtofficialsent 0.001 STEEM to @jonklinger- "CONGRATS! You have a 1:1 BLURT AIRDROP of 0.000 BLURT and 230.244000 BLURT POWER waiting for you. Check out https://blurtwallet.com/@jonklinger and https://blurt.blog/ TODAY!"
2020/12/17 00:40:06
fromblurtofficial
tojonklinger
amount0.001 STEEM
memoCONGRATS! You have a 1:1 BLURT AIRDROP of 0.000 BLURT and 230.244000 BLURT POWER waiting for you. Check out https://blurtwallet.com/@jonklinger and https://blurt.blog/ TODAY!
Transaction InfoBlock #49512543/Trx e4f771905c8f3a6ebf39fae4a356de51829c482d
View Raw JSON Data
{
  "trx_id": "e4f771905c8f3a6ebf39fae4a356de51829c482d",
  "block": 49512543,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-12-17T00:40:06",
  "op": [
    "transfer",
    {
      "from": "blurtofficial",
      "to": "jonklinger",
      "amount": "0.001 STEEM",
      "memo": "CONGRATS! You have a 1:1 BLURT AIRDROP of 0.000 BLURT and 230.244000 BLURT POWER waiting for you. Check out https://blurtwallet.com/@jonklinger and https://blurt.blog/ TODAY!"
    }
  ]
}
jonklingercustom json: notify
2020/07/19 20:17:48
required auths[]
required posting auths["jonklinger"]
idnotify
json["setLastRead",{"date":"2020-07-19T20:17:46"}]
Transaction InfoBlock #45249844/Trx 48bc1a3d7bfdd478e9f5024126a2a7d4edfb503d
View Raw JSON Data
{
  "trx_id": "48bc1a3d7bfdd478e9f5024126a2a7d4edfb503d",
  "block": 45249844,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-07-19T20:17:48",
  "op": [
    "custom_json",
    {
      "required_auths": [],
      "required_posting_auths": [
        "jonklinger"
      ],
      "id": "notify",
      "json": "[\"setLastRead\",{\"date\":\"2020-07-19T20:17:46\"}]"
    }
  ]
}
jonklingersent 98.288 STEEM to @silly-einstein- "c1520c3b-98f4-4cc4-a7db-bf204941c7ac"
2020/05/03 10:00:51
fromjonklinger
tosilly-einstein
amount98.288 STEEM
memoc1520c3b-98f4-4cc4-a7db-bf204941c7ac
Transaction InfoBlock #43053412/Trx 4d79a9664cf26e56445e99799e689756616ae6f4
View Raw JSON Data
{
  "trx_id": "4d79a9664cf26e56445e99799e689756616ae6f4",
  "block": 43053412,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-05-03T10:00:51",
  "op": [
    "transfer",
    {
      "from": "jonklinger",
      "to": "silly-einstein",
      "amount": "98.288 STEEM",
      "memo": "c1520c3b-98f4-4cc4-a7db-bf204941c7ac"
    }
  ]
}
jonklingerblockchain operation: limit order create
2020/05/03 09:08:54
ownerjonklinger
orderid1588496928
amount to sell17.586 SBD
min to receive98.288 STEEM
fill or killfalse
expiration2020-05-30T09:08:37
Transaction InfoBlock #43052399/Trx f5ec3e8a207fddeb7df79da02ac69ded4389407a
View Raw JSON Data
{
  "trx_id": "f5ec3e8a207fddeb7df79da02ac69ded4389407a",
  "block": 43052399,
  "trx_in_block": 7,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-05-03T09:08:54",
  "op": [
    "limit_order_create",
    {
      "owner": "jonklinger",
      "orderid": 1588496928,
      "amount_to_sell": "17.586 SBD",
      "min_to_receive": "98.288 STEEM",
      "fill_or_kill": false,
      "expiration": "2020-05-30T09:08:37"
    }
  ]
}
jonklingerbought 98.288 STEEM for 17.586 SBD from @bnk
2020/05/03 09:08:54
current ownerjonklinger
current orderid1588496928
current pays17.586 SBD
open ownerbnk
open orderid9807276
open pays98.288 STEEM
Transaction InfoBlock #43052399/Trx f5ec3e8a207fddeb7df79da02ac69ded4389407a
View Raw JSON Data
{
  "trx_id": "f5ec3e8a207fddeb7df79da02ac69ded4389407a",
  "block": 43052399,
  "trx_in_block": 7,
  "op_in_trx": 0,
  "virtual_op": 1,
  "timestamp": "2020-05-03T09:08:54",
  "op": [
    "fill_order",
    {
      "current_owner": "jonklinger",
      "current_orderid": 1588496928,
      "current_pays": "17.586 SBD",
      "open_owner": "bnk",
      "open_orderid": 9807276,
      "open_pays": "98.288 STEEM"
    }
  ]
}
jonklingerblockchain operation: fill transfer from savings
2020/05/01 09:08:39
fromjonklinger
tojonklinger
amount17.586 SBD
request id1588064914
memo
Transaction InfoBlock #42996210/Virtual Operation #6
View Raw JSON Data
{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 42996210,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 6,
  "timestamp": "2020-05-01T09:08:39",
  "op": [
    "fill_transfer_from_savings",
    {
      "from": "jonklinger",
      "to": "jonklinger",
      "amount": "17.586 SBD",
      "request_id": 1588064914,
      "memo": ""
    }
  ]
}
jonklingerblockchain operation: transfer from savings
2020/04/28 09:08:39
fromjonklinger
request id1588064914
tojonklinger
amount17.586 SBD
memo
Transaction InfoBlock #42911969/Trx 6b33dc21f609d76e5c6a4b9340c0234a8e4b34a6
View Raw JSON Data
{
  "trx_id": "6b33dc21f609d76e5c6a4b9340c0234a8e4b34a6",
  "block": 42911969,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-04-28T09:08:39",
  "op": [
    "transfer_from_savings",
    {
      "from": "jonklinger",
      "request_id": 1588064914,
      "to": "jonklinger",
      "amount": "17.586 SBD",
      "memo": ""
    }
  ]
}
jonklingerblockchain operation: transfer to savings
2020/04/28 08:59:57
fromjonklinger
tojonklinger
amount17.586 SBD
memo
Transaction InfoBlock #42911798/Trx b447904612e38637f808954a32a4ad9024311830
View Raw JSON Data
{
  "trx_id": "b447904612e38637f808954a32a4ad9024311830",
  "block": 42911798,
  "trx_in_block": 9,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-04-28T08:59:57",
  "op": [
    "transfer_to_savings",
    {
      "from": "jonklinger",
      "to": "jonklinger",
      "amount": "17.586 SBD",
      "memo": ""
    }
  ]
}
jonklingersent 40.335 STEEM to @silly-einstein- "9ef27be4-ce9d-4ede-bbd3-52142d453552"
2020/04/28 08:59:18
fromjonklinger
tosilly-einstein
amount40.335 STEEM
memo9ef27be4-ce9d-4ede-bbd3-52142d453552
Transaction InfoBlock #42911785/Trx bc33377f3fb8843753dc2158707bb68b5bbe27fd
View Raw JSON Data
{
  "trx_id": "bc33377f3fb8843753dc2158707bb68b5bbe27fd",
  "block": 42911785,
  "trx_in_block": 17,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-04-28T08:59:18",
  "op": [
    "transfer",
    {
      "from": "jonklinger",
      "to": "silly-einstein",
      "amount": "40.335 STEEM",
      "memo": "9ef27be4-ce9d-4ede-bbd3-52142d453552"
    }
  ]
}
jonklingerclaimed reward balance: 0.104 STEEM, 0.009 SBD, 0.201 SP
2020/04/26 13:25:03
accountjonklinger
reward steem0.104 STEEM
reward sbd0.009 SBD
reward vests326.493665 VESTS
Transaction InfoBlock #42860834/Trx ba7247a20e721792227551658dd0c9cba219442b
View Raw JSON Data
{
  "trx_id": "ba7247a20e721792227551658dd0c9cba219442b",
  "block": 42860834,
  "trx_in_block": 16,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-04-26T13:25:03",
  "op": [
    "claim_reward_balance",
    {
      "account": "jonklinger",
      "reward_steem": "0.104 STEEM",
      "reward_sbd": "0.009 SBD",
      "reward_vests": "326.493665 VESTS"
    }
  ]
}
jonklingerreceived 0.104 STEEM, 0.009 SBD, 0.201 SP author reward for @jonklinger / i-wrote-a-book-about-working-from-home
2020/04/23 08:04:33
authorjonklinger
permlinki-wrote-a-book-about-working-from-home
sbd payout0.009 SBD
steem payout0.104 STEEM
vesting payout326.493665 VESTS
Transaction InfoBlock #42770478/Virtual Operation #4
View Raw JSON Data
{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 42770478,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 4,
  "timestamp": "2020-04-23T08:04:33",
  "op": [
    "author_reward",
    {
      "author": "jonklinger",
      "permlink": "i-wrote-a-book-about-working-from-home",
      "sbd_payout": "0.009 SBD",
      "steem_payout": "0.104 STEEM",
      "vesting_payout": "326.493665 VESTS"
    }
  ]
}
2020/04/16 09:32:33
voterfilipino
authorjonklinger
permlinki-wrote-a-book-about-working-from-home
weight1000 (10.00%)
Transaction InfoBlock #42576406/Trx 33ad8a81a51c61607455cf8399ea19658ddc3e8a
View Raw JSON Data
{
  "trx_id": "33ad8a81a51c61607455cf8399ea19658ddc3e8a",
  "block": 42576406,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-04-16T09:32:33",
  "op": [
    "vote",
    {
      "voter": "filipino",
      "author": "jonklinger",
      "permlink": "i-wrote-a-book-about-working-from-home",
      "weight": 1000
    }
  ]
}
2020/04/16 09:09:12
voterpaullifefit
authorjonklinger
permlinki-wrote-a-book-about-working-from-home
weight9000 (90.00%)
Transaction InfoBlock #42575951/Trx f44268725d7dd857dceb421c47d6155277686ec7
View Raw JSON Data
{
  "trx_id": "f44268725d7dd857dceb421c47d6155277686ec7",
  "block": 42575951,
  "trx_in_block": 9,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-04-16T09:09:12",
  "op": [
    "vote",
    {
      "voter": "paullifefit",
      "author": "jonklinger",
      "permlink": "i-wrote-a-book-about-working-from-home",
      "weight": 9000
    }
  ]
}
2020/04/16 08:08:51
votertechslut
authorjonklinger
permlinki-wrote-a-book-about-working-from-home
weight10000 (100.00%)
Transaction InfoBlock #42574781/Trx 0085b9b92a0dc0cc5bb8abfdaf254bd96d7fe818
View Raw JSON Data
{
  "trx_id": "0085b9b92a0dc0cc5bb8abfdaf254bd96d7fe818",
  "block": 42574781,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-04-16T08:08:51",
  "op": [
    "vote",
    {
      "voter": "techslut",
      "author": "jonklinger",
      "permlink": "i-wrote-a-book-about-working-from-home",
      "weight": 10000
    }
  ]
}
2020/04/16 08:05:03
parent author
parent permlinkwfh
authorjonklinger
permlinki-wrote-a-book-about-working-from-home
titleDefaulting to Meetings (a chapter from my book)
body<a href="https://www.amazon.com/Homework-Ultimate-Guide-Working-Home-ebook/dp/B0873BLNMN/ref=cm_cr_arp_d_product_top?ie=UTF8">![mockup.jpg](https://cdn.steemitimages.com/DQmZJPJuAmvuKgkE686d5HvQnsLxvLMz3xB2YJp2RMQ5kTS/mockup.jpg)</a> During the recent crisis, I had the time to write a book about working from home with [Revital Salomon]( http://thesharklady.com ). The book gives you tips and tricks about productivity and working from home. I'm attaching one of the chapters here, which is about what we hate the most, **Meetings**. You can buy the book [here on Amazon]( https://www.amazon.com/Homework-Ultimate-Guide-Working-Home-ebook/dp/B0873BLNMN/ref=cm_cr_arp_d_product_top?ie=UTF8). In Malcolm Gladwell's book, ["Talking To Strangers"]( https://www.amazon.com/Talking-Strangers-Should-about-People/dp/0316478520 ), he writes about "*defaulting to truth*". It's an interesting concept: when someone presents a story, and you don't have any indication that he is lying, you default to the truth. It's easier for people to assume that you are not lying, unless they have an indication you actually are, or unless they have a specific job that requires them to be suspicious, like a police officer. The business world defaults to meetings. Why? Because, for some odd reason and against all proof, meetings are considered a way to solve problems, when in fact, what they mostly do is delay decision making. Unlike yourself, most people avoid making decisions because decisions mean being confrontational. More than that, making a decision means that you might be wrong, and you may need to accept blame if you chose poorly. Finally, making a decision means allocating resources, and who wants to do that? No one wants to make a decision. So they stall by having a meeting where "decisions were made" (to die). Productivity is on a scale. At the top is writing a document (or coding, designing, creating), whichever is your most productive and creative time. Exchanging an email with a client or service provider is a step below, a phone call is even lower, a video meeting is underneath that, and at the bottom, wallowing in their own dirt, we have the meeting and the unholy multi-personal meeting. Productivity, in this case, is defined by how much actual work is done, and not how much time is billed. If you ever want to see a low productivity meeting, schedule one with a top-tier law firm. To every meeting they send a partner, an associate and an intern, at least. This is to increase billables, not productivity. This scale of productivity should be your guide. Try to keep at least 75% of your time productive, dedicated to doing actual work and not just discussing the concept of work. [Jonathan: I worked on a few big projects as part of a team. One of these projects required that we have a follow-up meeting every day. This was the least productive part of our day. For two hours we discussed what we've done, instead of just having reporting tools. A quarter of our day was unproductive by default.] **Meetings: The Last Resort** When was your last productive meeting? A meeting in which you actually created something of value. Can you even recall something like that? Most people default to meetings because they don't know how to deal with their dead time, or just because "that's the way it's done". When you are working from home, a meeting takes a hell of a lot more time than you want it to. Time works differently for you now. You need to drive, commute or walk to the meeting and back. A one-hour meeting comes at the costly price of three hours if you have an hour of traffic to and from the meeting. Time is your most precious asset, remember? Meetings should be a last resort. Meetings will only be held if you have failed to resolve all the issues at hand by other means available on the scale of productivity. **The Agenda** Every interaction which requires your entire attention (meetings, phone calls and video calls are such interactions) should include an AGENDA. Agendum are items that are to be discussed and resolved within the meeting, and include relevant reading material. A general request like "Can we meet?" should be emphatically refused. A meeting will only be held when issues cannot be resolved otherwise. This means that it should include the requested agendum and decisions. Usually, people come, talk and have no decisions. Each party can just repeat his side over and over until he wears the other participants out. If you have an agenda, you know exactly what to talk about. In order to be prepared, it is best that every participant that has something relating to this agendum prepares a document to support it. For example, if the purpose of the meeting is to decide and finalize the website design, the designer should provide a few options before the meeting, and during the meeting the participants should decide on the optimal functionality. **Video Conference** There is one, and only one, justification for video conferencing, even in the age of Covid-19. The only reason to have a video conference is if someone needs to display something to other participants. Any other reason is really "I just want to see that all other people are busy with this call and are not playing with their phones while talking to me". Feel free to open your video display only in order to display your screen if you are working on a shared document or want to present something. No one needs to see your facial expressions or whatever it is you're doing when having work-related conversations. Be adamant about it and don't be afraid to stand your ground. A perfectly productive conversation can be held without you showing your face. **Calls** Phone calls should be planned in advance. Unless issues are super-urgent, don't call people without asking for the right time to call, and allot general time to answer your clients' phone calls. The reason is both productivity (calls break your train of thought) and billing (if you bill per hour). You need to list all calls with your clients in order to bill them for that time at the end of the month. Timing your calls also means you can mute your phone and establish that you'll get back to people later. Talking to a client on the phone will be done only when you have the time for it. People who are trying to broadcast an air of extra-productivity and availability will usually say "call me whenever". This is nonsense. They are abusing both their time and yours. They don't plan ahead and expect you to dump whatever it is you're doing when they call. These sort of people are usually not doing anything of importance, or they simply don't appreciate anyone else's time.
json metadata{"tags":["productivity","books"],"image":["https://cdn.steemitimages.com/DQmZJPJuAmvuKgkE686d5HvQnsLxvLMz3xB2YJp2RMQ5kTS/mockup.jpg"],"links":["https://www.amazon.com/Homework-Ultimate-Guide-Working-Home-ebook/dp/B0873BLNMN/ref=cm_cr_arp_d_product_top?ie=UTF8","http://thesharklady.com","https://www.amazon.com/Talking-Strangers-Should-about-People/dp/0316478520"],"app":"steemit/0.2","format":"markdown"}
Transaction InfoBlock #42574709/Trx b8fea4f55f309abd0530875e7e054808884abe06
View Raw JSON Data
{
  "trx_id": "b8fea4f55f309abd0530875e7e054808884abe06",
  "block": 42574709,
  "trx_in_block": 7,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-04-16T08:05:03",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "wfh",
      "author": "jonklinger",
      "permlink": "i-wrote-a-book-about-working-from-home",
      "title": "Defaulting to Meetings (a chapter from my book)",
      "body": "<a href=\"https://www.amazon.com/Homework-Ultimate-Guide-Working-Home-ebook/dp/B0873BLNMN/ref=cm_cr_arp_d_product_top?ie=UTF8\">![mockup.jpg](https://cdn.steemitimages.com/DQmZJPJuAmvuKgkE686d5HvQnsLxvLMz3xB2YJp2RMQ5kTS/mockup.jpg)</a>\n\nDuring the recent crisis, I had the time to write a book about working from home with [Revital Salomon]( http://thesharklady.com ). The book gives you tips and tricks about productivity and working from home. I'm attaching one of the chapters here, which is about what we hate the most, **Meetings**.\n\nYou can buy the book [here on Amazon]( https://www.amazon.com/Homework-Ultimate-Guide-Working-Home-ebook/dp/B0873BLNMN/ref=cm_cr_arp_d_product_top?ie=UTF8).\n\nIn Malcolm Gladwell's book, [\"Talking To Strangers\"]( https://www.amazon.com/Talking-Strangers-Should-about-People/dp/0316478520 ), he writes about \"*defaulting to truth*\". It's an interesting concept: when someone presents a story, and you don't have any indication that he is lying, you default to the truth. It's easier for people to assume that you are not lying, unless they have an indication you actually are, or unless they have a specific job that requires them to be suspicious, like a police officer.\n\nThe business world defaults to meetings. Why? Because, for some odd reason and against all proof, meetings are considered a way to solve problems, when in fact, what they mostly do is delay decision making. Unlike yourself, most people avoid making decisions because decisions mean being confrontational. More than that, making a decision means that you might be wrong, and you may need to accept blame if you chose poorly. Finally, making a decision means allocating resources, and who wants to do that?\n\nNo one wants to make a decision. So they stall by having a meeting where \"decisions were made\" (to die).\n\nProductivity is on a scale. At the top is writing a document (or coding, designing, creating), whichever is your most productive and creative time. Exchanging an email with a client or service provider is a step below, a phone call is even lower, a video meeting is underneath that, and at the bottom, wallowing in their own dirt, we have the meeting and the unholy multi-personal meeting.\n\nProductivity, in this case, is defined by how much actual work is done, and not how much time is billed. If you ever want to see a low productivity meeting, schedule one with a top-tier law firm. To every meeting they send a partner, an associate and an intern, at least. This is to increase billables, not productivity.\n\nThis scale of productivity should be your guide. Try to keep at least 75% of your time productive, dedicated to doing actual work and not just discussing the concept of work. \n\n[Jonathan: I worked on a few big projects as part of a team. One of these projects required that we have a follow-up meeting every day. This was the least productive part of our day. For two hours we discussed what we've done, instead of just having reporting tools. A quarter of our day was unproductive by default.]\n\n**Meetings: The Last Resort**\n\nWhen was your last productive meeting? A meeting in which you actually created something of value. Can you even recall something like that? Most people default to meetings because they don't know how to deal with their dead time, or just because \"that's the way it's done\". When you are working from home, a meeting takes a hell of a lot more time than you want it to. Time works differently for you now. You need to drive, commute or walk to the meeting and back. A one-hour meeting comes at the costly price of three hours if you have an hour of traffic to and from the meeting. Time is your most precious asset, remember?\n\nMeetings should be a last resort. Meetings will only be held if you have failed to resolve all the issues at hand by other means available on the scale of productivity.\n\n**The Agenda**\n\nEvery interaction which requires your entire attention (meetings, phone calls and video calls are such interactions) should include an AGENDA. Agendum are items that are to be discussed and resolved within the meeting, and include relevant reading material.\n\nA general request like \"Can we meet?\" should be emphatically refused. A meeting will only be held when issues cannot be resolved otherwise. This means that it should include the requested agendum and decisions. Usually, people come, talk and have no decisions. Each party can just repeat his side over and over until he wears the other participants out.\n\nIf you have an agenda, you know exactly what to talk about. In order to be prepared, it is best that every participant that has something relating to this agendum prepares a document to support it. \n\nFor example, if the purpose of the meeting is to decide and finalize the website design, the designer should provide a few options before the meeting, and during the meeting the participants should decide on the optimal functionality.\n\n**Video Conference**\n\nThere is one, and only one, justification for video conferencing, even in the age of Covid-19. The only reason to have a video conference is if someone needs to display something to other participants. Any other reason is really \"I just want to see that all other people are busy with this call and are not playing with their phones while talking to me\". \n\nFeel free to open your video display only in order to display your screen if you are working on a shared document or want to present something. No one needs to see your facial expressions or whatever it is you're doing when having work-related conversations. Be adamant about it and don't be afraid to stand your ground. A perfectly productive conversation can be held without you showing your face.\n\n**Calls**\n\nPhone calls should be planned in advance. Unless issues are super-urgent, don't call people without asking for the right time to call, and allot general time to answer your clients' phone calls. The reason is both productivity (calls break your train of thought) and billing (if you bill per hour). You need to list all calls with your clients in order to bill them for that time at the end of the month.\n\nTiming your calls also means you can mute your phone and establish that you'll get back to people later. Talking to a client on the phone will be done only when you have the time for it.\n\nPeople who are trying to broadcast an air of extra-productivity and availability will usually say \"call me whenever\". This is nonsense. They are abusing both their time and yours. They don't plan ahead and expect you to dump whatever it is you're doing when they call. These sort of people are usually not doing anything of importance, or they simply don't appreciate anyone else's time.",
      "json_metadata": "{\"tags\":[\"productivity\",\"books\"],\"image\":[\"https://cdn.steemitimages.com/DQmZJPJuAmvuKgkE686d5HvQnsLxvLMz3xB2YJp2RMQ5kTS/mockup.jpg\"],\"links\":[\"https://www.amazon.com/Homework-Ultimate-Guide-Working-Home-ebook/dp/B0873BLNMN/ref=cm_cr_arp_d_product_top?ie=UTF8\",\"http://thesharklady.com\",\"https://www.amazon.com/Talking-Strangers-Should-about-People/dp/0316478520\"],\"app\":\"steemit/0.2\",\"format\":\"markdown\"}"
    }
  ]
}
2020/04/16 08:04:33
parent author
parent permlinkwfh
authorjonklinger
permlinki-wrote-a-book-about-working-from-home
titleI wrote a book about working from home.
body<a href="https://www.amazon.com/Homework-Ultimate-Guide-Working-Home-ebook/dp/B0873BLNMN/ref=cm_cr_arp_d_product_top?ie=UTF8">![mockup.jpg](https://cdn.steemitimages.com/DQmZJPJuAmvuKgkE686d5HvQnsLxvLMz3xB2YJp2RMQ5kTS/mockup.jpg)</a> During the recent crisis, I had the time to write a book about working from home with [Revital Salomon]( http://thesharklady.com ). The book gives you tips and tricks about productivity and working from home. I'm attaching one of the chapters here, which is about what we hate the most, **Meetings**. You can buy the book [here on Amazon]( https://www.amazon.com/Homework-Ultimate-Guide-Working-Home-ebook/dp/B0873BLNMN/ref=cm_cr_arp_d_product_top?ie=UTF8). In Malcolm Gladwell's book, ["Talking To Strangers"]( https://www.amazon.com/Talking-Strangers-Should-about-People/dp/0316478520 ), he writes about "*defaulting to truth*". It's an interesting concept: when someone presents a story, and you don't have any indication that he is lying, you default to the truth. It's easier for people to assume that you are not lying, unless they have an indication you actually are, or unless they have a specific job that requires them to be suspicious, like a police officer. The business world defaults to meetings. Why? Because, for some odd reason and against all proof, meetings are considered a way to solve problems, when in fact, what they mostly do is delay decision making. Unlike yourself, most people avoid making decisions because decisions mean being confrontational. More than that, making a decision means that you might be wrong, and you may need to accept blame if you chose poorly. Finally, making a decision means allocating resources, and who wants to do that? No one wants to make a decision. So they stall by having a meeting where "decisions were made" (to die). Productivity is on a scale. At the top is writing a document (or coding, designing, creating), whichever is your most productive and creative time. Exchanging an email with a client or service provider is a step below, a phone call is even lower, a video meeting is underneath that, and at the bottom, wallowing in their own dirt, we have the meeting and the unholy multi-personal meeting. Productivity, in this case, is defined by how much actual work is done, and not how much time is billed. If you ever want to see a low productivity meeting, schedule one with a top-tier law firm. To every meeting they send a partner, an associate and an intern, at least. This is to increase billables, not productivity. This scale of productivity should be your guide. Try to keep at least 75% of your time productive, dedicated to doing actual work and not just discussing the concept of work. [Jonathan: I worked on a few big projects as part of a team. One of these projects required that we have a follow-up meeting every day. This was the least productive part of our day. For two hours we discussed what we've done, instead of just having reporting tools. A quarter of our day was unproductive by default.] **Meetings: The Last Resort** When was your last productive meeting? A meeting in which you actually created something of value. Can you even recall something like that? Most people default to meetings because they don't know how to deal with their dead time, or just because "that's the way it's done". When you are working from home, a meeting takes a hell of a lot more time than you want it to. Time works differently for you now. You need to drive, commute or walk to the meeting and back. A one-hour meeting comes at the costly price of three hours if you have an hour of traffic to and from the meeting. Time is your most precious asset, remember? Meetings should be a last resort. Meetings will only be held if you have failed to resolve all the issues at hand by other means available on the scale of productivity. **The Agenda** Every interaction which requires your entire attention (meetings, phone calls and video calls are such interactions) should include an AGENDA. Agendum are items that are to be discussed and resolved within the meeting, and include relevant reading material. A general request like "Can we meet?" should be emphatically refused. A meeting will only be held when issues cannot be resolved otherwise. This means that it should include the requested agendum and decisions. Usually, people come, talk and have no decisions. Each party can just repeat his side over and over until he wears the other participants out. If you have an agenda, you know exactly what to talk about. In order to be prepared, it is best that every participant that has something relating to this agendum prepares a document to support it. For example, if the purpose of the meeting is to decide and finalize the website design, the designer should provide a few options before the meeting, and during the meeting the participants should decide on the optimal functionality. **Video Conference** There is one, and only one, justification for video conferencing, even in the age of Covid-19. The only reason to have a video conference is if someone needs to display something to other participants. Any other reason is really "I just want to see that all other people are busy with this call and are not playing with their phones while talking to me". Feel free to open your video display only in order to display your screen if you are working on a shared document or want to present something. No one needs to see your facial expressions or whatever it is you're doing when having work-related conversations. Be adamant about it and don't be afraid to stand your ground. A perfectly productive conversation can be held without you showing your face. **Calls** Phone calls should be planned in advance. Unless issues are super-urgent, don't call people without asking for the right time to call, and allot general time to answer your clients' phone calls. The reason is both productivity (calls break your train of thought) and billing (if you bill per hour). You need to list all calls with your clients in order to bill them for that time at the end of the month. Timing your calls also means you can mute your phone and establish that you'll get back to people later. Talking to a client on the phone will be done only when you have the time for it. People who are trying to broadcast an air of extra-productivity and availability will usually say "call me whenever". This is nonsense. They are abusing both their time and yours. They don't plan ahead and expect you to dump whatever it is you're doing when they call. These sort of people are usually not doing anything of importance, or they simply don't appreciate anyone else's time.
json metadata{"tags":["wfh","productivity","books"],"image":["https://cdn.steemitimages.com/DQmZJPJuAmvuKgkE686d5HvQnsLxvLMz3xB2YJp2RMQ5kTS/mockup.jpg"],"links":["https://www.amazon.com/Homework-Ultimate-Guide-Working-Home-ebook/dp/B0873BLNMN/ref=cm_cr_arp_d_product_top?ie=UTF8","http://thesharklady.com","https://www.amazon.com/Talking-Strangers-Should-about-People/dp/0316478520"],"app":"steemit/0.2","format":"markdown"}
Transaction InfoBlock #42574699/Trx 5b023d035b141014f91c10fe6b11656b5fe7cdfa
View Raw JSON Data
{
  "trx_id": "5b023d035b141014f91c10fe6b11656b5fe7cdfa",
  "block": 42574699,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-04-16T08:04:33",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "wfh",
      "author": "jonklinger",
      "permlink": "i-wrote-a-book-about-working-from-home",
      "title": "I wrote a book about working from home.",
      "body": "<a href=\"https://www.amazon.com/Homework-Ultimate-Guide-Working-Home-ebook/dp/B0873BLNMN/ref=cm_cr_arp_d_product_top?ie=UTF8\">![mockup.jpg](https://cdn.steemitimages.com/DQmZJPJuAmvuKgkE686d5HvQnsLxvLMz3xB2YJp2RMQ5kTS/mockup.jpg)</a>\n\nDuring the recent crisis, I had the time to write a book about working from home with [Revital Salomon]( http://thesharklady.com ). The book gives you tips and tricks about productivity and working from home. I'm attaching one of the chapters here, which is about what we hate the most, **Meetings**.\n\nYou can buy the book [here on Amazon]( https://www.amazon.com/Homework-Ultimate-Guide-Working-Home-ebook/dp/B0873BLNMN/ref=cm_cr_arp_d_product_top?ie=UTF8).\n\nIn Malcolm Gladwell's book, [\"Talking To Strangers\"]( https://www.amazon.com/Talking-Strangers-Should-about-People/dp/0316478520 ), he writes about \"*defaulting to truth*\". It's an interesting concept: when someone presents a story, and you don't have any indication that he is lying, you default to the truth. It's easier for people to assume that you are not lying, unless they have an indication you actually are, or unless they have a specific job that requires them to be suspicious, like a police officer.\n\nThe business world defaults to meetings. Why? Because, for some odd reason and against all proof, meetings are considered a way to solve problems, when in fact, what they mostly do is delay decision making. Unlike yourself, most people avoid making decisions because decisions mean being confrontational. More than that, making a decision means that you might be wrong, and you may need to accept blame if you chose poorly. Finally, making a decision means allocating resources, and who wants to do that?\n\nNo one wants to make a decision. So they stall by having a meeting where \"decisions were made\" (to die).\n\nProductivity is on a scale. At the top is writing a document (or coding, designing, creating), whichever is your most productive and creative time. Exchanging an email with a client or service provider is a step below, a phone call is even lower, a video meeting is underneath that, and at the bottom, wallowing in their own dirt, we have the meeting and the unholy multi-personal meeting.\n\nProductivity, in this case, is defined by how much actual work is done, and not how much time is billed. If you ever want to see a low productivity meeting, schedule one with a top-tier law firm. To every meeting they send a partner, an associate and an intern, at least. This is to increase billables, not productivity.\n\nThis scale of productivity should be your guide. Try to keep at least 75% of your time productive, dedicated to doing actual work and not just discussing the concept of work. \n\n[Jonathan: I worked on a few big projects as part of a team. One of these projects required that we have a follow-up meeting every day. This was the least productive part of our day. For two hours we discussed what we've done, instead of just having reporting tools. A quarter of our day was unproductive by default.]\n\n**Meetings: The Last Resort**\n\nWhen was your last productive meeting? A meeting in which you actually created something of value. Can you even recall something like that? Most people default to meetings because they don't know how to deal with their dead time, or just because \"that's the way it's done\". When you are working from home, a meeting takes a hell of a lot more time than you want it to. Time works differently for you now. You need to drive, commute or walk to the meeting and back. A one-hour meeting comes at the costly price of three hours if you have an hour of traffic to and from the meeting. Time is your most precious asset, remember?\n\nMeetings should be a last resort. Meetings will only be held if you have failed to resolve all the issues at hand by other means available on the scale of productivity.\n\n**The Agenda**\n\nEvery interaction which requires your entire attention (meetings, phone calls and video calls are such interactions) should include an AGENDA. Agendum are items that are to be discussed and resolved within the meeting, and include relevant reading material.\n\nA general request like \"Can we meet?\" should be emphatically refused. A meeting will only be held when issues cannot be resolved otherwise. This means that it should include the requested agendum and decisions. Usually, people come, talk and have no decisions. Each party can just repeat his side over and over until he wears the other participants out.\n\nIf you have an agenda, you know exactly what to talk about. In order to be prepared, it is best that every participant that has something relating to this agendum prepares a document to support it. \n\nFor example, if the purpose of the meeting is to decide and finalize the website design, the designer should provide a few options before the meeting, and during the meeting the participants should decide on the optimal functionality.\n\n**Video Conference**\n\nThere is one, and only one, justification for video conferencing, even in the age of Covid-19. The only reason to have a video conference is if someone needs to display something to other participants. Any other reason is really \"I just want to see that all other people are busy with this call and are not playing with their phones while talking to me\". \n\nFeel free to open your video display only in order to display your screen if you are working on a shared document or want to present something. No one needs to see your facial expressions or whatever it is you're doing when having work-related conversations. Be adamant about it and don't be afraid to stand your ground. A perfectly productive conversation can be held without you showing your face.\n\n**Calls**\n\nPhone calls should be planned in advance. Unless issues are super-urgent, don't call people without asking for the right time to call, and allot general time to answer your clients' phone calls. The reason is both productivity (calls break your train of thought) and billing (if you bill per hour). You need to list all calls with your clients in order to bill them for that time at the end of the month.\n\nTiming your calls also means you can mute your phone and establish that you'll get back to people later. Talking to a client on the phone will be done only when you have the time for it.\n\nPeople who are trying to broadcast an air of extra-productivity and availability will usually say \"call me whenever\". This is nonsense. They are abusing both their time and yours. They don't plan ahead and expect you to dump whatever it is you're doing when they call. These sort of people are usually not doing anything of importance, or they simply don't appreciate anyone else's time.",
      "json_metadata": "{\"tags\":[\"wfh\",\"productivity\",\"books\"],\"image\":[\"https://cdn.steemitimages.com/DQmZJPJuAmvuKgkE686d5HvQnsLxvLMz3xB2YJp2RMQ5kTS/mockup.jpg\"],\"links\":[\"https://www.amazon.com/Homework-Ultimate-Guide-Working-Home-ebook/dp/B0873BLNMN/ref=cm_cr_arp_d_product_top?ie=UTF8\",\"http://thesharklady.com\",\"https://www.amazon.com/Talking-Strangers-Should-about-People/dp/0316478520\"],\"app\":\"steemit/0.2\",\"format\":\"markdown\"}"
    }
  ]
}
2020/03/11 16:32:57
voterfminerten
authorjonklinger
permlinkfacebookland-why-libra-is-not-a-cryptocurrency
weight3700 (37.00%)
Transaction InfoBlock #41563043/Trx 5a5d2167e43bffe8aec65fcc4fb16656fcf6f3d4
View Raw JSON Data
{
  "trx_id": "5a5d2167e43bffe8aec65fcc4fb16656fcf6f3d4",
  "block": 41563043,
  "trx_in_block": 12,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-03-11T16:32:57",
  "op": [
    "vote",
    {
      "voter": "fminerten",
      "author": "jonklinger",
      "permlink": "facebookland-why-libra-is-not-a-cryptocurrency",
      "weight": 3700
    }
  ]
}
2020/03/11 16:32:48
votersteempty
authorjonklinger
permlinkfacebookland-why-libra-is-not-a-cryptocurrency
weight3700 (37.00%)
Transaction InfoBlock #41563040/Trx f518a0f5e69f361c7f52b98bbbd8f0e95f8a51e0
View Raw JSON Data
{
  "trx_id": "f518a0f5e69f361c7f52b98bbbd8f0e95f8a51e0",
  "block": 41563040,
  "trx_in_block": 14,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-03-11T16:32:48",
  "op": [
    "vote",
    {
      "voter": "steempty",
      "author": "jonklinger",
      "permlink": "facebookland-why-libra-is-not-a-cryptocurrency",
      "weight": 3700
    }
  ]
}
2020/03/11 16:32:48
voterfminerten
authorjonklinger
permlinkthe-problem-of-data-processing-agreements-compliance-by-paperwork
weight3700 (37.00%)
Transaction InfoBlock #41563040/Trx 42955ee3205dfead4fe40d32c48569312817ae04
View Raw JSON Data
{
  "trx_id": "42955ee3205dfead4fe40d32c48569312817ae04",
  "block": 41563040,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-03-11T16:32:48",
  "op": [
    "vote",
    {
      "voter": "fminerten",
      "author": "jonklinger",
      "permlink": "the-problem-of-data-processing-agreements-compliance-by-paperwork",
      "weight": 3700
    }
  ]
}
2020/03/11 16:32:39
votersteempty
authorjonklinger
permlinkthe-problem-of-data-processing-agreements-compliance-by-paperwork
weight3700 (37.00%)
Transaction InfoBlock #41563037/Trx 02bd91fad747c6153ccced27e6fdd2eaff1d2bf9
View Raw JSON Data
{
  "trx_id": "02bd91fad747c6153ccced27e6fdd2eaff1d2bf9",
  "block": 41563037,
  "trx_in_block": 19,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-03-11T16:32:39",
  "op": [
    "vote",
    {
      "voter": "steempty",
      "author": "jonklinger",
      "permlink": "the-problem-of-data-processing-agreements-compliance-by-paperwork",
      "weight": 3700
    }
  ]
}
2020/03/11 16:32:36
voterfminerten
authorjonklinger
permlinkwhat-sacha-baron-cohen-doesn-t-get-about-230-and-how-to-solve-online-hate-speech
weight3700 (37.00%)
Transaction InfoBlock #41563036/Trx e7d727696845250797318a4aee1788f973ee5533
View Raw JSON Data
{
  "trx_id": "e7d727696845250797318a4aee1788f973ee5533",
  "block": 41563036,
  "trx_in_block": 26,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-03-11T16:32:36",
  "op": [
    "vote",
    {
      "voter": "fminerten",
      "author": "jonklinger",
      "permlink": "what-sacha-baron-cohen-doesn-t-get-about-230-and-how-to-solve-online-hate-speech",
      "weight": 3700
    }
  ]
}
2020/03/11 16:32:30
votersteempty
authorjonklinger
permlinkwhat-sacha-baron-cohen-doesn-t-get-about-230-and-how-to-solve-online-hate-speech
weight3700 (37.00%)
Transaction InfoBlock #41563034/Trx 7527e742c61de617561bfaf14a4c54e57a806615
View Raw JSON Data
{
  "trx_id": "7527e742c61de617561bfaf14a4c54e57a806615",
  "block": 41563034,
  "trx_in_block": 7,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-03-11T16:32:30",
  "op": [
    "vote",
    {
      "voter": "steempty",
      "author": "jonklinger",
      "permlink": "what-sacha-baron-cohen-doesn-t-get-about-230-and-how-to-solve-online-hate-speech",
      "weight": 3700
    }
  ]
}
2020/03/11 16:19:06
voterfminerten
authorjonklinger
permlinkfacebookland-why-libra-is-not-a-cryptocurrency
weight3700 (37.00%)
Transaction InfoBlock #41562766/Trx 5c73cc2166d5e5cb5467844becf06b104f229599
View Raw JSON Data
{
  "trx_id": "5c73cc2166d5e5cb5467844becf06b104f229599",
  "block": 41562766,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-03-11T16:19:06",
  "op": [
    "vote",
    {
      "voter": "fminerten",
      "author": "jonklinger",
      "permlink": "facebookland-why-libra-is-not-a-cryptocurrency",
      "weight": 3700
    }
  ]
}
2020/03/11 16:18:57
votersteempty
authorjonklinger
permlinkfacebookland-why-libra-is-not-a-cryptocurrency
weight3700 (37.00%)
Transaction InfoBlock #41562763/Trx 28e3d6851120a43021ba89271164f4a3055e60d3
View Raw JSON Data
{
  "trx_id": "28e3d6851120a43021ba89271164f4a3055e60d3",
  "block": 41562763,
  "trx_in_block": 19,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-03-11T16:18:57",
  "op": [
    "vote",
    {
      "voter": "steempty",
      "author": "jonklinger",
      "permlink": "facebookland-why-libra-is-not-a-cryptocurrency",
      "weight": 3700
    }
  ]
}
2020/03/11 16:18:54
voterfminerten
authorjonklinger
permlinkthe-problem-of-data-processing-agreements-compliance-by-paperwork
weight3700 (37.00%)
Transaction InfoBlock #41562762/Trx ffd551fab1ec0385d808bed35ae82be32d0be0e0
View Raw JSON Data
{
  "trx_id": "ffd551fab1ec0385d808bed35ae82be32d0be0e0",
  "block": 41562762,
  "trx_in_block": 24,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-03-11T16:18:54",
  "op": [
    "vote",
    {
      "voter": "fminerten",
      "author": "jonklinger",
      "permlink": "the-problem-of-data-processing-agreements-compliance-by-paperwork",
      "weight": 3700
    }
  ]
}
2020/03/11 16:18:48
votersteempty
authorjonklinger
permlinkthe-problem-of-data-processing-agreements-compliance-by-paperwork
weight3700 (37.00%)
Transaction InfoBlock #41562760/Trx ef87b523a8d58d57fa7326bc98559c1f76f4243b
View Raw JSON Data
{
  "trx_id": "ef87b523a8d58d57fa7326bc98559c1f76f4243b",
  "block": 41562760,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-03-11T16:18:48",
  "op": [
    "vote",
    {
      "voter": "steempty",
      "author": "jonklinger",
      "permlink": "the-problem-of-data-processing-agreements-compliance-by-paperwork",
      "weight": 3700
    }
  ]
}
2020/03/11 16:18:45
voterfminerten
authorjonklinger
permlinkwhat-sacha-baron-cohen-doesn-t-get-about-230-and-how-to-solve-online-hate-speech
weight3700 (37.00%)
Transaction InfoBlock #41562759/Trx 3ca519bd6b246efcd4bd248cec04b754069efdaa
View Raw JSON Data
{
  "trx_id": "3ca519bd6b246efcd4bd248cec04b754069efdaa",
  "block": 41562759,
  "trx_in_block": 19,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-03-11T16:18:45",
  "op": [
    "vote",
    {
      "voter": "fminerten",
      "author": "jonklinger",
      "permlink": "what-sacha-baron-cohen-doesn-t-get-about-230-and-how-to-solve-online-hate-speech",
      "weight": 3700
    }
  ]
}
2020/03/11 16:18:39
votersteempty
authorjonklinger
permlinkwhat-sacha-baron-cohen-doesn-t-get-about-230-and-how-to-solve-online-hate-speech
weight3700 (37.00%)
Transaction InfoBlock #41562757/Trx 1310de57337f8ca48d9337fe4bc3c27e4f18168e
View Raw JSON Data
{
  "trx_id": "1310de57337f8ca48d9337fe4bc3c27e4f18168e",
  "block": 41562757,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-03-11T16:18:39",
  "op": [
    "vote",
    {
      "voter": "steempty",
      "author": "jonklinger",
      "permlink": "what-sacha-baron-cohen-doesn-t-get-about-230-and-how-to-solve-online-hate-speech",
      "weight": 3700
    }
  ]
}
2020/03/11 16:05:09
voterfminerten
authorjonklinger
permlinkfacebookland-why-libra-is-not-a-cryptocurrency
weight3700 (37.00%)
Transaction InfoBlock #41562487/Trx 91d64899123a9a5c8b85c7db939c72f91429297f
View Raw JSON Data
{
  "trx_id": "91d64899123a9a5c8b85c7db939c72f91429297f",
  "block": 41562487,
  "trx_in_block": 37,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-03-11T16:05:09",
  "op": [
    "vote",
    {
      "voter": "fminerten",
      "author": "jonklinger",
      "permlink": "facebookland-why-libra-is-not-a-cryptocurrency",
      "weight": 3700
    }
  ]
}
2020/03/11 16:05:03
votersteempty
authorjonklinger
permlinkfacebookland-why-libra-is-not-a-cryptocurrency
weight3700 (37.00%)
Transaction InfoBlock #41562485/Trx b6176a8a726567bf533bbed18b6a4e586dbcedd9
View Raw JSON Data
{
  "trx_id": "b6176a8a726567bf533bbed18b6a4e586dbcedd9",
  "block": 41562485,
  "trx_in_block": 18,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-03-11T16:05:03",
  "op": [
    "vote",
    {
      "voter": "steempty",
      "author": "jonklinger",
      "permlink": "facebookland-why-libra-is-not-a-cryptocurrency",
      "weight": 3700
    }
  ]
}
2020/03/11 16:05:00
voterfminerten
authorjonklinger
permlinkthe-problem-of-data-processing-agreements-compliance-by-paperwork
weight3700 (37.00%)
Transaction InfoBlock #41562484/Trx 86d10b8a1e608346e72ef90c430d70a35c696b88
View Raw JSON Data
{
  "trx_id": "86d10b8a1e608346e72ef90c430d70a35c696b88",
  "block": 41562484,
  "trx_in_block": 32,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-03-11T16:05:00",
  "op": [
    "vote",
    {
      "voter": "fminerten",
      "author": "jonklinger",
      "permlink": "the-problem-of-data-processing-agreements-compliance-by-paperwork",
      "weight": 3700
    }
  ]
}
2020/03/11 16:04:54
votersteempty
authorjonklinger
permlinkthe-problem-of-data-processing-agreements-compliance-by-paperwork
weight3700 (37.00%)
Transaction InfoBlock #41562482/Trx bf98f32615bdba7ee615ec758d928ed2cf279ae5
View Raw JSON Data
{
  "trx_id": "bf98f32615bdba7ee615ec758d928ed2cf279ae5",
  "block": 41562482,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-03-11T16:04:54",
  "op": [
    "vote",
    {
      "voter": "steempty",
      "author": "jonklinger",
      "permlink": "the-problem-of-data-processing-agreements-compliance-by-paperwork",
      "weight": 3700
    }
  ]
}
2020/03/11 16:04:51
voterfminerten
authorjonklinger
permlinkwhat-sacha-baron-cohen-doesn-t-get-about-230-and-how-to-solve-online-hate-speech
weight3700 (37.00%)
Transaction InfoBlock #41562481/Trx cc1db2e0ed49f68b402a4d5a57ed99502b5b5187
View Raw JSON Data
{
  "trx_id": "cc1db2e0ed49f68b402a4d5a57ed99502b5b5187",
  "block": 41562481,
  "trx_in_block": 10,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-03-11T16:04:51",
  "op": [
    "vote",
    {
      "voter": "fminerten",
      "author": "jonklinger",
      "permlink": "what-sacha-baron-cohen-doesn-t-get-about-230-and-how-to-solve-online-hate-speech",
      "weight": 3700
    }
  ]
}
2020/03/11 16:04:45
votersteempty
authorjonklinger
permlinkwhat-sacha-baron-cohen-doesn-t-get-about-230-and-how-to-solve-online-hate-speech
weight3700 (37.00%)
Transaction InfoBlock #41562479/Trx bbd8f6a759bf81322da90d4a3e042a1194c1902b
View Raw JSON Data
{
  "trx_id": "bbd8f6a759bf81322da90d4a3e042a1194c1902b",
  "block": 41562479,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-03-11T16:04:45",
  "op": [
    "vote",
    {
      "voter": "steempty",
      "author": "jonklinger",
      "permlink": "what-sacha-baron-cohen-doesn-t-get-about-230-and-how-to-solve-online-hate-speech",
      "weight": 3700
    }
  ]
}
2020/03/11 15:51:09
voterfminerten
authorjonklinger
permlinkfacebookland-why-libra-is-not-a-cryptocurrency
weight3700 (37.00%)
Transaction InfoBlock #41562208/Trx 4d1ce8797c2fbe9a9bc40b024258a58cc65e8931
View Raw JSON Data
{
  "trx_id": "4d1ce8797c2fbe9a9bc40b024258a58cc65e8931",
  "block": 41562208,
  "trx_in_block": 35,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-03-11T15:51:09",
  "op": [
    "vote",
    {
      "voter": "fminerten",
      "author": "jonklinger",
      "permlink": "facebookland-why-libra-is-not-a-cryptocurrency",
      "weight": 3700
    }
  ]
}
2020/03/11 15:51:00
votersteempty
authorjonklinger
permlinkfacebookland-why-libra-is-not-a-cryptocurrency
weight3700 (37.00%)
Transaction InfoBlock #41562205/Trx 59215a525e8ceda093cb38039ec44c6d00d08b35
View Raw JSON Data
{
  "trx_id": "59215a525e8ceda093cb38039ec44c6d00d08b35",
  "block": 41562205,
  "trx_in_block": 6,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-03-11T15:51:00",
  "op": [
    "vote",
    {
      "voter": "steempty",
      "author": "jonklinger",
      "permlink": "facebookland-why-libra-is-not-a-cryptocurrency",
      "weight": 3700
    }
  ]
}
2020/03/11 15:50:57
voterfminerten
authorjonklinger
permlinkthe-problem-of-data-processing-agreements-compliance-by-paperwork
weight3700 (37.00%)
Transaction InfoBlock #41562204/Trx adbe54a1136c0448725cead29934b7cb00306989
View Raw JSON Data
{
  "trx_id": "adbe54a1136c0448725cead29934b7cb00306989",
  "block": 41562204,
  "trx_in_block": 40,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-03-11T15:50:57",
  "op": [
    "vote",
    {
      "voter": "fminerten",
      "author": "jonklinger",
      "permlink": "the-problem-of-data-processing-agreements-compliance-by-paperwork",
      "weight": 3700
    }
  ]
}
2020/03/11 15:50:51
votersteempty
authorjonklinger
permlinkthe-problem-of-data-processing-agreements-compliance-by-paperwork
weight3700 (37.00%)
Transaction InfoBlock #41562202/Trx 470ba94a31c77362dca8023e988c59f52b386640
View Raw JSON Data
{
  "trx_id": "470ba94a31c77362dca8023e988c59f52b386640",
  "block": 41562202,
  "trx_in_block": 6,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-03-11T15:50:51",
  "op": [
    "vote",
    {
      "voter": "steempty",
      "author": "jonklinger",
      "permlink": "the-problem-of-data-processing-agreements-compliance-by-paperwork",
      "weight": 3700
    }
  ]
}
2020/03/11 15:50:48
voterfminerten
authorjonklinger
permlinkwhat-sacha-baron-cohen-doesn-t-get-about-230-and-how-to-solve-online-hate-speech
weight3700 (37.00%)
Transaction InfoBlock #41562201/Trx 77b91be32218cd635cd9dad9245adf120b49595b
View Raw JSON Data
{
  "trx_id": "77b91be32218cd635cd9dad9245adf120b49595b",
  "block": 41562201,
  "trx_in_block": 23,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-03-11T15:50:48",
  "op": [
    "vote",
    {
      "voter": "fminerten",
      "author": "jonklinger",
      "permlink": "what-sacha-baron-cohen-doesn-t-get-about-230-and-how-to-solve-online-hate-speech",
      "weight": 3700
    }
  ]
}
2020/03/11 15:50:42
votersteempty
authorjonklinger
permlinkwhat-sacha-baron-cohen-doesn-t-get-about-230-and-how-to-solve-online-hate-speech
weight3700 (37.00%)
Transaction InfoBlock #41562199/Trx ed2caa966a8da9307b28dca5872cb15b56d13149
View Raw JSON Data
{
  "trx_id": "ed2caa966a8da9307b28dca5872cb15b56d13149",
  "block": 41562199,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-03-11T15:50:42",
  "op": [
    "vote",
    {
      "voter": "steempty",
      "author": "jonklinger",
      "permlink": "what-sacha-baron-cohen-doesn-t-get-about-230-and-how-to-solve-online-hate-speech",
      "weight": 3700
    }
  ]
}
2020/03/11 15:37:06
voterfminerten
authorjonklinger
permlinkfacebookland-why-libra-is-not-a-cryptocurrency
weight3700 (37.00%)
Transaction InfoBlock #41561927/Trx 808630c7c4059e602b026b4da78884020038cb6f
View Raw JSON Data
{
  "trx_id": "808630c7c4059e602b026b4da78884020038cb6f",
  "block": 41561927,
  "trx_in_block": 29,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-03-11T15:37:06",
  "op": [
    "vote",
    {
      "voter": "fminerten",
      "author": "jonklinger",
      "permlink": "facebookland-why-libra-is-not-a-cryptocurrency",
      "weight": 3700
    }
  ]
}
2020/03/11 15:37:00
votersteempty
authorjonklinger
permlinkfacebookland-why-libra-is-not-a-cryptocurrency
weight3700 (37.00%)
Transaction InfoBlock #41561925/Trx 630f506160cfcc840eede4e629c2b4cbf90b720f
View Raw JSON Data
{
  "trx_id": "630f506160cfcc840eede4e629c2b4cbf90b720f",
  "block": 41561925,
  "trx_in_block": 16,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-03-11T15:37:00",
  "op": [
    "vote",
    {
      "voter": "steempty",
      "author": "jonklinger",
      "permlink": "facebookland-why-libra-is-not-a-cryptocurrency",
      "weight": 3700
    }
  ]
}
2020/03/11 15:36:57
voterfminerten
authorjonklinger
permlinkthe-problem-of-data-processing-agreements-compliance-by-paperwork
weight3700 (37.00%)
Transaction InfoBlock #41561924/Trx a9a94bd00440327cf5ca2253f383a179f8b2cd10
View Raw JSON Data
{
  "trx_id": "a9a94bd00440327cf5ca2253f383a179f8b2cd10",
  "block": 41561924,
  "trx_in_block": 23,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-03-11T15:36:57",
  "op": [
    "vote",
    {
      "voter": "fminerten",
      "author": "jonklinger",
      "permlink": "the-problem-of-data-processing-agreements-compliance-by-paperwork",
      "weight": 3700
    }
  ]
}
2020/03/11 15:36:51
votersteempty
authorjonklinger
permlinkthe-problem-of-data-processing-agreements-compliance-by-paperwork
weight3700 (37.00%)
Transaction InfoBlock #41561922/Trx a1946f45df614c68026a7b6e827765a784db2519
View Raw JSON Data
{
  "trx_id": "a1946f45df614c68026a7b6e827765a784db2519",
  "block": 41561922,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-03-11T15:36:51",
  "op": [
    "vote",
    {
      "voter": "steempty",
      "author": "jonklinger",
      "permlink": "the-problem-of-data-processing-agreements-compliance-by-paperwork",
      "weight": 3700
    }
  ]
}
2020/03/11 15:36:48
voterfminerten
authorjonklinger
permlinkwhat-sacha-baron-cohen-doesn-t-get-about-230-and-how-to-solve-online-hate-speech
weight3700 (37.00%)
Transaction InfoBlock #41561921/Trx 820d296470aa6f70c262cabfceb409fa3181197e
View Raw JSON Data
{
  "trx_id": "820d296470aa6f70c262cabfceb409fa3181197e",
  "block": 41561921,
  "trx_in_block": 13,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-03-11T15:36:48",
  "op": [
    "vote",
    {
      "voter": "fminerten",
      "author": "jonklinger",
      "permlink": "what-sacha-baron-cohen-doesn-t-get-about-230-and-how-to-solve-online-hate-speech",
      "weight": 3700
    }
  ]
}
2020/03/11 15:36:42
votersteempty
authorjonklinger
permlinkwhat-sacha-baron-cohen-doesn-t-get-about-230-and-how-to-solve-online-hate-speech
weight3700 (37.00%)
Transaction InfoBlock #41561919/Trx fb1b75a32c3dcd21b7bd2d920540193dcc778b2e
View Raw JSON Data
{
  "trx_id": "fb1b75a32c3dcd21b7bd2d920540193dcc778b2e",
  "block": 41561919,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-03-11T15:36:42",
  "op": [
    "vote",
    {
      "voter": "steempty",
      "author": "jonklinger",
      "permlink": "what-sacha-baron-cohen-doesn-t-get-about-230-and-how-to-solve-online-hate-speech",
      "weight": 3700
    }
  ]
}
2020/03/11 15:23:15
voterfminerten
authorjonklinger
permlinkfacebookland-why-libra-is-not-a-cryptocurrency
weight3700 (37.00%)
Transaction InfoBlock #41561650/Trx a701c8e96508f6da94d1f01dd763e22ce2f14123
View Raw JSON Data
{
  "trx_id": "a701c8e96508f6da94d1f01dd763e22ce2f14123",
  "block": 41561650,
  "trx_in_block": 43,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-03-11T15:23:15",
  "op": [
    "vote",
    {
      "voter": "fminerten",
      "author": "jonklinger",
      "permlink": "facebookland-why-libra-is-not-a-cryptocurrency",
      "weight": 3700
    }
  ]
}
2020/03/11 15:23:09
votersteempty
authorjonklinger
permlinkfacebookland-why-libra-is-not-a-cryptocurrency
weight3700 (37.00%)
Transaction InfoBlock #41561648/Trx 2ea59f4c5ea75942dac29c0fd5fc06e2872a0c62
View Raw JSON Data
{
  "trx_id": "2ea59f4c5ea75942dac29c0fd5fc06e2872a0c62",
  "block": 41561648,
  "trx_in_block": 15,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-03-11T15:23:09",
  "op": [
    "vote",
    {
      "voter": "steempty",
      "author": "jonklinger",
      "permlink": "facebookland-why-libra-is-not-a-cryptocurrency",
      "weight": 3700
    }
  ]
}
2020/03/11 15:23:06
voterfminerten
authorjonklinger
permlinkthe-problem-of-data-processing-agreements-compliance-by-paperwork
weight3700 (37.00%)
Transaction InfoBlock #41561647/Trx d97452533e4eda436b3a7500f7ad898dfe5ea90c
View Raw JSON Data
{
  "trx_id": "d97452533e4eda436b3a7500f7ad898dfe5ea90c",
  "block": 41561647,
  "trx_in_block": 24,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-03-11T15:23:06",
  "op": [
    "vote",
    {
      "voter": "fminerten",
      "author": "jonklinger",
      "permlink": "the-problem-of-data-processing-agreements-compliance-by-paperwork",
      "weight": 3700
    }
  ]
}
2020/03/11 15:22:57
votersteempty
authorjonklinger
permlinkthe-problem-of-data-processing-agreements-compliance-by-paperwork
weight3700 (37.00%)
Transaction InfoBlock #41561644/Trx e6b70d307e9484e9731d1305c5d06cbb3a27c46f
View Raw JSON Data
{
  "trx_id": "e6b70d307e9484e9731d1305c5d06cbb3a27c46f",
  "block": 41561644,
  "trx_in_block": 32,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-03-11T15:22:57",
  "op": [
    "vote",
    {
      "voter": "steempty",
      "author": "jonklinger",
      "permlink": "the-problem-of-data-processing-agreements-compliance-by-paperwork",
      "weight": 3700
    }
  ]
}
2020/03/11 15:22:57
voterfminerten
authorjonklinger
permlinkwhat-sacha-baron-cohen-doesn-t-get-about-230-and-how-to-solve-online-hate-speech
weight3700 (37.00%)
Transaction InfoBlock #41561644/Trx f245ad27cef769c7ca1a67c3bc88155e0bfc6c33
View Raw JSON Data
{
  "trx_id": "f245ad27cef769c7ca1a67c3bc88155e0bfc6c33",
  "block": 41561644,
  "trx_in_block": 11,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-03-11T15:22:57",
  "op": [
    "vote",
    {
      "voter": "fminerten",
      "author": "jonklinger",
      "permlink": "what-sacha-baron-cohen-doesn-t-get-about-230-and-how-to-solve-online-hate-speech",
      "weight": 3700
    }
  ]
}
2020/03/11 15:22:48
votersteempty
authorjonklinger
permlinkwhat-sacha-baron-cohen-doesn-t-get-about-230-and-how-to-solve-online-hate-speech
weight3700 (37.00%)
Transaction InfoBlock #41561641/Trx 6bd14d8286dc1d3d039034c9923ce780de8958de
View Raw JSON Data
{
  "trx_id": "6bd14d8286dc1d3d039034c9923ce780de8958de",
  "block": 41561641,
  "trx_in_block": 20,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-03-11T15:22:48",
  "op": [
    "vote",
    {
      "voter": "steempty",
      "author": "jonklinger",
      "permlink": "what-sacha-baron-cohen-doesn-t-get-about-230-and-how-to-solve-online-hate-speech",
      "weight": 3700
    }
  ]
}
2020/03/11 15:09:24
voterfminerten
authorjonklinger
permlinkfacebookland-why-libra-is-not-a-cryptocurrency
weight3700 (37.00%)
Transaction InfoBlock #41561373/Trx 77b1c6fc3f79919783bd8283abb9c27e3fe03930
View Raw JSON Data
{
  "trx_id": "77b1c6fc3f79919783bd8283abb9c27e3fe03930",
  "block": 41561373,
  "trx_in_block": 36,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-03-11T15:09:24",
  "op": [
    "vote",
    {
      "voter": "fminerten",
      "author": "jonklinger",
      "permlink": "facebookland-why-libra-is-not-a-cryptocurrency",
      "weight": 3700
    }
  ]
}
2020/03/11 15:09:18
votersteempty
authorjonklinger
permlinkfacebookland-why-libra-is-not-a-cryptocurrency
weight3700 (37.00%)
Transaction InfoBlock #41561371/Trx ec87f7796461c2780166f56cae6c1afa1e3d865b
View Raw JSON Data
{
  "trx_id": "ec87f7796461c2780166f56cae6c1afa1e3d865b",
  "block": 41561371,
  "trx_in_block": 15,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-03-11T15:09:18",
  "op": [
    "vote",
    {
      "voter": "steempty",
      "author": "jonklinger",
      "permlink": "facebookland-why-libra-is-not-a-cryptocurrency",
      "weight": 3700
    }
  ]
}
2020/03/11 15:09:15
voterfminerten
authorjonklinger
permlinkthe-problem-of-data-processing-agreements-compliance-by-paperwork
weight3700 (37.00%)
Transaction InfoBlock #41561370/Trx 97d9f8ce6aff669309517e573cd6345e47d29f8f
View Raw JSON Data
{
  "trx_id": "97d9f8ce6aff669309517e573cd6345e47d29f8f",
  "block": 41561370,
  "trx_in_block": 17,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-03-11T15:09:15",
  "op": [
    "vote",
    {
      "voter": "fminerten",
      "author": "jonklinger",
      "permlink": "the-problem-of-data-processing-agreements-compliance-by-paperwork",
      "weight": 3700
    }
  ]
}
2020/03/11 15:09:09
votersteempty
authorjonklinger
permlinkthe-problem-of-data-processing-agreements-compliance-by-paperwork
weight3700 (37.00%)
Transaction InfoBlock #41561368/Trx e9b4aee885ca40260f6407374d29d7c02271ac41
View Raw JSON Data
{
  "trx_id": "e9b4aee885ca40260f6407374d29d7c02271ac41",
  "block": 41561368,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-03-11T15:09:09",
  "op": [
    "vote",
    {
      "voter": "steempty",
      "author": "jonklinger",
      "permlink": "the-problem-of-data-processing-agreements-compliance-by-paperwork",
      "weight": 3700
    }
  ]
}

Account Metadata

POSTING JSON METADATA
profile{"profile_image":"https://pbs.twimg.com/profile_images/951159743825043456/loWpoLq4_400x400.jpg","cover_image":"https://scontent.fsdv1-1.fna.fbcdn.net/v/t1.0-9/21752332_10155023946186295_3086871474418016518_n.jpg?oh=bec1ce5e7cc90b3f3a0bdcba5edd9c0a&oe=5AF11AE0","name":"jonklinger","about":"Jonathan Klinger is a cryptolawyer. He is a Master of Law (2007) and teaches Cyberlaw. He blogs about privacy, copyright, and technolegal interfaces","location":"Tel-Aviv, Israel","website":"http://2jk.org/english/"}
JSON METADATA
profile{"profile_image":"https://pbs.twimg.com/profile_images/951159743825043456/loWpoLq4_400x400.jpg","cover_image":"https://scontent.fsdv1-1.fna.fbcdn.net/v/t1.0-9/21752332_10155023946186295_3086871474418016518_n.jpg?oh=bec1ce5e7cc90b3f3a0bdcba5edd9c0a&oe=5AF11AE0","name":"jonklinger","about":"Jonathan Klinger is a cryptolawyer. He is a Master of Law (2007) and teaches Cyberlaw. He blogs about privacy, copyright, and technolegal interfaces","location":"Tel-Aviv, Israel","website":"http://2jk.org/english/"}
{
  "posting_json_metadata": {
    "profile": {
      "profile_image": "https://pbs.twimg.com/profile_images/951159743825043456/loWpoLq4_400x400.jpg",
      "cover_image": "https://scontent.fsdv1-1.fna.fbcdn.net/v/t1.0-9/21752332_10155023946186295_3086871474418016518_n.jpg?oh=bec1ce5e7cc90b3f3a0bdcba5edd9c0a&oe=5AF11AE0",
      "name": "jonklinger",
      "about": "Jonathan Klinger is a cryptolawyer. He is a Master of Law (2007) and teaches Cyberlaw. He blogs about privacy, copyright, and technolegal interfaces",
      "location": "Tel-Aviv, Israel",
      "website": "http://2jk.org/english/"
    }
  },
  "json_metadata": {
    "profile": {
      "profile_image": "https://pbs.twimg.com/profile_images/951159743825043456/loWpoLq4_400x400.jpg",
      "cover_image": "https://scontent.fsdv1-1.fna.fbcdn.net/v/t1.0-9/21752332_10155023946186295_3086871474418016518_n.jpg?oh=bec1ce5e7cc90b3f3a0bdcba5edd9c0a&oe=5AF11AE0",
      "name": "jonklinger",
      "about": "Jonathan Klinger is a cryptolawyer. He is a Master of Law (2007) and teaches Cyberlaw. He blogs about privacy, copyright, and technolegal interfaces",
      "location": "Tel-Aviv, Israel",
      "website": "http://2jk.org/english/"
    }
  }
}

Auth Keys

Owner
Single Signature
Public Keys
STM6nXrxcgLpN7bG4FXsQvPMtSUknU71UZSeYjYgjjtcbmbbJ6VvS1/1
Active
Single Signature
Public Keys
STM4uyptDJ3dcWMSmWoVceQpyaRDJmNQo6TXeWCYnyXSBrvrAcnAj1/1
Posting
Single Signature
Public Keys
STM5QXJ4jviwK6ZN66RKcdfgf51KQxe2fkBaddPLRY6CX3a5LxVgh1/1
App Permissions
Memo
STM6UWe6HC2g6A2uLZ2k23Bcmtq2GAiVwyqoLXnBkvGZbaZ4agMQD
{
  "owner": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM6nXrxcgLpN7bG4FXsQvPMtSUknU71UZSeYjYgjjtcbmbbJ6VvS",
        1
      ]
    ]
  },
  "active": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM4uyptDJ3dcWMSmWoVceQpyaRDJmNQo6TXeWCYnyXSBrvrAcnAj",
        1
      ]
    ]
  },
  "posting": {
    "weight_threshold": 1,
    "account_auths": [
      [
        "utopian.app",
        1
      ]
    ],
    "key_auths": [
      [
        "STM5QXJ4jviwK6ZN66RKcdfgf51KQxe2fkBaddPLRY6CX3a5LxVgh",
        1
      ]
    ]
  },
  "memo": "STM6UWe6HC2g6A2uLZ2k23Bcmtq2GAiVwyqoLXnBkvGZbaZ4agMQD"
}

Witness Votes

2 / 30
[
  "utopian-io",
  "windforce"
]