Ecoer Logo
VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS0.00%
Net Worth
0.037USD
STEEM
0.000STEEM
SBD
0.000SBD
Effective Power
5.001SP
├── Own SP
0.684SP
└── Incoming Deleg
+4.317SP

Detailed Balance

STEEM
balance
0.000STEEM
market_balance
0.000STEEM
savings_balance
0.000STEEM
reward_steem_balance
0.000STEEM
STEEM POWER
Own SP
0.684SP
Delegated Out
0.000SP
Delegation In
4.317SP
Effective Power
5.001SP
Reward SP (pending)
0.000SP
SBD
sbd_balance
0.000SBD
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": "1113.363874 VESTS",
  "delegated_vesting_shares": "0.000000 VESTS",
  "received_vesting_shares": "7030.295932 VESTS",
  "sbd_balance": "0.000 SBD",
  "savings_sbd_balance": "0.000 SBD",
  "reward_sbd_balance": "0.000 SBD",
  "conversions": []
}

Account Info

namepatb
id399189
rank1,428,221
reputation337618745
created2017-10-06T03:03:18
recovery_accountsteem
proxyNone
post_count4
comment_count0
lifetime_vote_count0
witnesses_voted_for0
last_post2018-06-04T17:50:36
last_root_post2018-06-04T17:50:36
last_vote_time2019-06-26T22:19:21
proxied_vsf_votes0, 0, 0, 0
can_vote1
voting_power0
delayed_votes0
balance0.000 STEEM
savings_balance0.000 STEEM
sbd_balance0.000 SBD
savings_sbd_balance0.000 SBD
vesting_shares1113.363874 VESTS
delegated_vesting_shares0.000000 VESTS
received_vesting_shares7030.295932 VESTS
reward_vesting_balance0.000000 VESTS
vesting_balance0.000 STEEM
vesting_withdraw_rate0.000000 VESTS
next_vesting_withdrawal1969-12-31T23:59:59
withdrawn0
to_withdraw0
withdraw_routes0
savings_withdraw_requests0
last_account_recovery1970-01-01T00:00:00
reset_accountnull
last_owner_update1970-01-01T00:00:00
last_account_update1970-01-01T00:00:00
minedNo
sbd_seconds0
sbd_last_interest_payment1970-01-01T00:00:00
savings_sbd_last_interest_payment1970-01-01T00:00:00
{
  "id": 399189,
  "name": "patb",
  "owner": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM7SRE4yrL9kkx4tCpYGz8ophgYsdj8KhSbQkppQ9pByyRXYfuKK",
        1
      ]
    ]
  },
  "active": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM7LukJz84VpEg56LDwbYbLrZu5ULHcUPkS27LmgCDUu4HpZdwYZ",
        1
      ]
    ]
  },
  "posting": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM5hckhcMayNSm3qsiRu8UhoY7mFbhduq7HrG8FUw6Sjns7RsxbU",
        1
      ]
    ]
  },
  "memo_key": "STM7ii7hrqxssbJoThpg8ap8Zg4oCKhdp7ZyD8C9EguJBpRn4wbQ6",
  "json_metadata": "",
  "posting_json_metadata": "",
  "proxy": "",
  "last_owner_update": "1970-01-01T00:00:00",
  "last_account_update": "1970-01-01T00:00:00",
  "created": "2017-10-06T03:03:18",
  "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": 4,
  "can_vote": true,
  "voting_manabar": {
    "current_mana": "8143659806",
    "last_update_time": 1779080211
  },
  "downvote_manabar": {
    "current_mana": 2035914951,
    "last_update_time": 1779080211
  },
  "voting_power": 0,
  "balance": "0.000 STEEM",
  "savings_balance": "0.000 STEEM",
  "sbd_balance": "0.000 SBD",
  "sbd_seconds": "0",
  "sbd_seconds_last_update": "2019-06-26T22:18:39",
  "sbd_last_interest_payment": "1970-01-01T00:00:00",
  "savings_sbd_balance": "0.000 SBD",
  "savings_sbd_seconds": "0",
  "savings_sbd_seconds_last_update": "1970-01-01T00:00:00",
  "savings_sbd_last_interest_payment": "1970-01-01T00:00:00",
  "savings_withdraw_requests": 0,
  "reward_sbd_balance": "0.000 SBD",
  "reward_steem_balance": "0.000 STEEM",
  "reward_vesting_balance": "0.000000 VESTS",
  "reward_vesting_steem": "0.000 STEEM",
  "vesting_shares": "1113.363874 VESTS",
  "delegated_vesting_shares": "0.000000 VESTS",
  "received_vesting_shares": "7030.295932 VESTS",
  "vesting_withdraw_rate": "0.000000 VESTS",
  "next_vesting_withdrawal": "1969-12-31T23:59:59",
  "withdrawn": 0,
  "to_withdraw": 0,
  "withdraw_routes": 0,
  "curation_rewards": 0,
  "posting_rewards": 41,
  "proxied_vsf_votes": [
    0,
    0,
    0,
    0
  ],
  "witnesses_voted_for": 0,
  "last_post": "2018-06-04T17:50:36",
  "last_root_post": "2018-06-04T17:50:36",
  "last_vote_time": "2019-06-26T22:19:21",
  "post_bandwidth": 0,
  "pending_claimed_accounts": 0,
  "vesting_balance": "0.000 STEEM",
  "reputation": 337618745,
  "transfer_history": [],
  "market_history": [],
  "post_history": [],
  "vote_history": [],
  "other_history": [],
  "witness_votes": [],
  "tags_usage": [],
  "guest_bloggers": [],
  "rank": 1428221
}

Withdraw Routes

IncomingOutgoing
Empty
Empty
{
  "incoming": [],
  "outgoing": []
}
From Date
To Date
steemdelegated 4.317 SP to @patb
2026/05/18 04:56:51
delegatorsteem
delegateepatb
vesting shares7030.295932 VESTS
Transaction InfoBlock #106149055/Trx 29a93872a79b98d065286da9d5267ff80d252981
View Raw JSON Data
{
  "trx_id": "29a93872a79b98d065286da9d5267ff80d252981",
  "block": 106149055,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2026-05-18T04:56:51",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "patb",
      "vesting_shares": "7030.295932 VESTS"
    }
  ]
}
steemdelegated 2.652 SP to @patb
2026/05/12 22:54:18
delegatorsteem
delegateepatb
vesting shares4318.085527 VESTS
Transaction InfoBlock #105998537/Trx 2a773c59753e8b2530014ed1f40092d9ec3d9b0e
View Raw JSON Data
{
  "trx_id": "2a773c59753e8b2530014ed1f40092d9ec3d9b0e",
  "block": 105998537,
  "trx_in_block": 20,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2026-05-12T22:54:18",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "patb",
      "vesting_shares": "4318.085527 VESTS"
    }
  ]
}
steemdelegated 4.325 SP to @patb
2026/04/26 04:10:36
delegatorsteem
delegateepatb
vesting shares7042.811688 VESTS
Transaction InfoBlock #105516577/Trx 666aa7abe1bda866ee3f0a9e3c35b53be722fa8f
View Raw JSON Data
{
  "trx_id": "666aa7abe1bda866ee3f0a9e3c35b53be722fa8f",
  "block": 105516577,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2026-04-26T04:10:36",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "patb",
      "vesting_shares": "7042.811688 VESTS"
    }
  ]
}
steemdelegated 2.677 SP to @patb
2026/01/23 20:25:24
delegatorsteem
delegateepatb
vesting shares4359.632346 VESTS
Transaction InfoBlock #102866932/Trx 6a81f7a7aad7062940f2fe400385e198bef2bacb
View Raw JSON Data
{
  "trx_id": "6a81f7a7aad7062940f2fe400385e198bef2bacb",
  "block": 102866932,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2026-01-23T20:25:24",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "patb",
      "vesting_shares": "4359.632346 VESTS"
    }
  ]
}
steemdelegated 2.778 SP to @patb
2024/12/17 15:36:24
delegatorsteem
delegateepatb
vesting shares4523.851543 VESTS
Transaction InfoBlock #91313165/Trx c3364889d062ae76acb60d9f2ba046f5ce2bfcab
View Raw JSON Data
{
  "trx_id": "c3364889d062ae76acb60d9f2ba046f5ce2bfcab",
  "block": 91313165,
  "trx_in_block": 6,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2024-12-17T15:36:24",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "patb",
      "vesting_shares": "4523.851543 VESTS"
    }
  ]
}
steemdelegated 2.882 SP to @patb
2023/11/14 07:17:42
delegatorsteem
delegateepatb
vesting shares4692.985075 VESTS
Transaction InfoBlock #79867323/Trx d34ea2860124a93c05ac295c1c5f0f2c10ca8b5e
View Raw JSON Data
{
  "trx_id": "d34ea2860124a93c05ac295c1c5f0f2c10ca8b5e",
  "block": 79867323,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2023-11-14T07:17:42",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "patb",
      "vesting_shares": "4692.985075 VESTS"
    }
  ]
}
steemdelegated 4.686 SP to @patb
2023/09/22 08:48:03
delegatorsteem
delegateepatb
vesting shares7629.893861 VESTS
Transaction InfoBlock #78360963/Trx a6e0beff35a42986d44c07eb8de8b6a9be11b14b
View Raw JSON Data
{
  "trx_id": "a6e0beff35a42986d44c07eb8de8b6a9be11b14b",
  "block": 78360963,
  "trx_in_block": 6,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2023-09-22T08:48:03",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "patb",
      "vesting_shares": "7629.893861 VESTS"
    }
  ]
}
steemdelegated 4.822 SP to @patb
2022/11/03 16:28:09
delegatorsteem
delegateepatb
vesting shares7851.945299 VESTS
Transaction InfoBlock #69118954/Trx 390d5c945a198c06f39df81728821a9b18eefada
View Raw JSON Data
{
  "trx_id": "390d5c945a198c06f39df81728821a9b18eefada",
  "block": 69118954,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-11-03T16:28:09",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "patb",
      "vesting_shares": "7851.945299 VESTS"
    }
  ]
}
steemdelegated 4.957 SP to @patb
2022/01/17 21:48:18
delegatorsteem
delegateepatb
vesting shares8072.052900 VESTS
Transaction InfoBlock #60822365/Trx 89b35945b7f9b26ea6bb3a3322dac6d06137fabd
View Raw JSON Data
{
  "trx_id": "89b35945b7f9b26ea6bb3a3322dac6d06137fabd",
  "block": 60822365,
  "trx_in_block": 76,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-01-17T21:48:18",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "patb",
      "vesting_shares": "8072.052900 VESTS"
    }
  ]
}
steemdelegated 5.070 SP to @patb
2021/06/14 05:02:30
delegatorsteem
delegateepatb
vesting shares8256.247188 VESTS
Transaction InfoBlock #54612760/Trx 5e7295ba457c4a304ce9b014c874552404dd43f4
View Raw JSON Data
{
  "trx_id": "5e7295ba457c4a304ce9b014c874552404dd43f4",
  "block": 54612760,
  "trx_in_block": 8,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-06-14T05:02:30",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "patb",
      "vesting_shares": "8256.247188 VESTS"
    }
  ]
}
steemdelegated 5.185 SP to @patb
2020/12/11 15:15:57
delegatorsteem
delegateepatb
vesting shares8443.669162 VESTS
Transaction InfoBlock #49360062/Trx b1ca7738a3845d4ed7145440759d9156d0ab7b42
View Raw JSON Data
{
  "trx_id": "b1ca7738a3845d4ed7145440759d9156d0ab7b42",
  "block": 49360062,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-12-11T15:15:57",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "patb",
      "vesting_shares": "8443.669162 VESTS"
    }
  ]
}
steemdelegated 1.174 SP to @patb
2020/12/06 08:52:09
delegatorsteem
delegateepatb
vesting shares1912.543513 VESTS
Transaction InfoBlock #49211594/Trx 8cdac4f2c4c61ddd59e0c17969394952d0356b93
View Raw JSON Data
{
  "trx_id": "8cdac4f2c4c61ddd59e0c17969394952d0356b93",
  "block": 49211594,
  "trx_in_block": 8,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-12-06T08:52:09",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "patb",
      "vesting_shares": "1912.543513 VESTS"
    }
  ]
}
steemdelegated 5.189 SP to @patb
2020/12/05 18:53:45
delegatorsteem
delegateepatb
vesting shares8449.877016 VESTS
Transaction InfoBlock #49195144/Trx a35600c66f8bf6920c89fb8c778d9551e4321262
View Raw JSON Data
{
  "trx_id": "a35600c66f8bf6920c89fb8c778d9551e4321262",
  "block": 49195144,
  "trx_in_block": 9,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-12-05T18:53:45",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "patb",
      "vesting_shares": "8449.877016 VESTS"
    }
  ]
}
steemdelegated 1.179 SP to @patb
2020/11/03 00:13:15
delegatorsteem
delegateepatb
vesting shares1920.017158 VESTS
Transaction InfoBlock #48267904/Trx 26a18264452365d50fb56d934a70c9bc3413ab8b
View Raw JSON Data
{
  "trx_id": "26a18264452365d50fb56d934a70c9bc3413ab8b",
  "block": 48267904,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-11-03T00:13:15",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "patb",
      "vesting_shares": "1920.017158 VESTS"
    }
  ]
}
steemdelegated 5.314 SP to @patb
2020/05/09 09:53:45
delegatorsteem
delegateepatb
vesting shares8652.682375 VESTS
Transaction InfoBlock #43221905/Trx 28fd83c46943211d0629f03284b886fe7e3e17a7
View Raw JSON Data
{
  "trx_id": "28fd83c46943211d0629f03284b886fe7e3e17a7",
  "block": 43221905,
  "trx_in_block": 3,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-05-09T09:53:45",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "patb",
      "vesting_shares": "8652.682375 VESTS"
    }
  ]
}
steemdelegated 1.200 SP to @patb
2020/05/08 14:07:21
delegatorsteem
delegateepatb
vesting shares1953.311140 VESTS
Transaction InfoBlock #43198736/Trx 9f4206c0edbba88524f1d4ee6857b54b8bb1a1a9
View Raw JSON Data
{
  "trx_id": "9f4206c0edbba88524f1d4ee6857b54b8bb1a1a9",
  "block": 43198736,
  "trx_in_block": 17,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-05-08T14:07:21",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "patb",
      "vesting_shares": "1953.311140 VESTS"
    }
  ]
}
2019/10/06 04:35:54
parent authorpatb
parent permlinkhow-to-make-better-cryptocurrencies-with-pol-and-dash7
authorsteemitboard
permlinksteemitboard-notify-patb-20191006t043554000z
title
bodyCongratulations @patb! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@patb/birthday2.png</td><td>Happy Birthday! - You are on the Steem blockchain for 2 years!</td></tr></table> <sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@patb) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=patb)_</sub> ###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!
json metadata{"image":["https://steemitboard.com/img/notify.png"]}
Transaction InfoBlock #37037012/Trx 4928a0bd4c1753ee1e605b59db77547224eed4d6
View Raw JSON Data
{
  "trx_id": "4928a0bd4c1753ee1e605b59db77547224eed4d6",
  "block": 37037012,
  "trx_in_block": 7,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-10-06T04:35:54",
  "op": [
    "comment",
    {
      "parent_author": "patb",
      "parent_permlink": "how-to-make-better-cryptocurrencies-with-pol-and-dash7",
      "author": "steemitboard",
      "permlink": "steemitboard-notify-patb-20191006t043554000z",
      "title": "",
      "body": "Congratulations @patb! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@patb/birthday2.png</td><td>Happy Birthday! - You are on the Steem blockchain for 2 years!</td></tr></table>\n\n<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@patb) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=patb)_</sub>\n\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
      "json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}"
    }
  ]
}
steemdelegated 5.392 SP to @patb
2019/09/25 23:26:30
delegatorsteem
delegateepatb
vesting shares8780.618561 VESTS
Transaction InfoBlock #36743444/Trx e1c316051e899d1877fb8cc73ed00674e9f43137
View Raw JSON Data
{
  "trx_id": "e1c316051e899d1877fb8cc73ed00674e9f43137",
  "block": 36743444,
  "trx_in_block": 8,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-09-25T23:26:30",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "patb",
      "vesting_shares": "8780.618561 VESTS"
    }
  ]
}
steemdelegated 17.907 SP to @patb
2019/09/06 16:01:57
delegatorsteem
delegateepatb
vesting shares29160.370243 VESTS
Transaction InfoBlock #36188862/Trx c4a9ceaeb0b7a55073356e514ee7f650a051b056
View Raw JSON Data
{
  "trx_id": "c4a9ceaeb0b7a55073356e514ee7f650a051b056",
  "block": 36188862,
  "trx_in_block": 33,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-09-06T16:01:57",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "patb",
      "vesting_shares": "29160.370243 VESTS"
    }
  ]
}
steemdelegated 17.644 SP to @patb
2019/06/26 23:52:39
delegatorsteem
delegateepatb
vesting shares28731.547597 VESTS
Transaction InfoBlock #34150712/Trx 58ae30ee2355f2f529687171b8f52c983d98cda6
View Raw JSON Data
{
  "trx_id": "58ae30ee2355f2f529687171b8f52c983d98cda6",
  "block": 34150712,
  "trx_in_block": 17,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-06-26T23:52:39",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "patb",
      "vesting_shares": "28731.547597 VESTS"
    }
  ]
}
2019/06/26 22:19:21
voterpatb
authortransisto
permlinkinsider-blows-whistle-and-exec-reveals-google-plan-to-prevent-trump-situation-in-2020-on-hidden-cam
weight10000 (100.00%)
Transaction InfoBlock #34148848/Trx a0775b542f925a7aa66aa16d9c391284f272d6c4
View Raw JSON Data
{
  "trx_id": "a0775b542f925a7aa66aa16d9c391284f272d6c4",
  "block": 34148848,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-06-26T22:19:21",
  "op": [
    "vote",
    {
      "voter": "patb",
      "author": "transisto",
      "permlink": "insider-blows-whistle-and-exec-reveals-google-plan-to-prevent-trump-situation-in-2020-on-hidden-cam",
      "weight": 10000
    }
  ]
}
patbclaimed reward balance: 0.052 SP
2019/06/26 22:18:39
accountpatb
reward steem0.000 STEEM
reward sbd0.000 SBD
reward vests84.238143 VESTS
Transaction InfoBlock #34148834/Trx 0c202e3a7a81325a4eadc5598a8848b21a5da324
View Raw JSON Data
{
  "trx_id": "0c202e3a7a81325a4eadc5598a8848b21a5da324",
  "block": 34148834,
  "trx_in_block": 22,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-06-26T22:18:39",
  "op": [
    "claim_reward_balance",
    {
      "account": "patb",
      "reward_steem": "0.000 STEEM",
      "reward_sbd": "0.000 SBD",
      "reward_vests": "84.238143 VESTS"
    }
  ]
}
2018/11/04 12:51:12
votersagi85
authorpatb
permlinkthe-really-hard-thing-about-gps-and-the-iot
weight10000 (100.00%)
Transaction InfoBlock #27405186/Trx b4e443cf6420a396164b2406e6a8c78381a26e7b
View Raw JSON Data
{
  "trx_id": "b4e443cf6420a396164b2406e6a8c78381a26e7b",
  "block": 27405186,
  "trx_in_block": 16,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-11-04T12:51:12",
  "op": [
    "vote",
    {
      "voter": "sagi85",
      "author": "patb",
      "permlink": "the-really-hard-thing-about-gps-and-the-iot",
      "weight": 10000
    }
  ]
}
2018/11/04 12:50:57
parent authorpatb
parent permlinkthe-really-hard-thing-about-gps-and-the-iot
authorsagi85
permlinkre-patb-the-really-hard-thing-about-gps-and-the-iot-20181104t125054960z
title
bodyIt seems that there has been great changes in the field of <a href="https://altair-semi.com/technology/">Low Power Chipset</a> and the growth of <a href="https://altair-semi.com/products/alt1210/">LTE-M</a> networks in the last couple of years, and this helps change the way iot tags and gps modules are adapted
json metadata{"tags":["iot"],"links":["https://altair-semi.com/technology/","https://altair-semi.com/products/alt1210/"],"app":"steemit/0.1"}
Transaction InfoBlock #27405181/Trx 383a01628fdec14ec4b15fe50acc8411c84056b8
View Raw JSON Data
{
  "trx_id": "383a01628fdec14ec4b15fe50acc8411c84056b8",
  "block": 27405181,
  "trx_in_block": 9,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-11-04T12:50:57",
  "op": [
    "comment",
    {
      "parent_author": "patb",
      "parent_permlink": "the-really-hard-thing-about-gps-and-the-iot",
      "author": "sagi85",
      "permlink": "re-patb-the-really-hard-thing-about-gps-and-the-iot-20181104t125054960z",
      "title": "",
      "body": "It seems that there has been great changes in the field of <a href=\"https://altair-semi.com/technology/\">Low Power Chipset</a> and the growth of <a href=\"https://altair-semi.com/products/alt1210/\">LTE-M</a> networks in the last couple of years, and this helps change the way iot tags and gps modules are adapted",
      "json_metadata": "{\"tags\":[\"iot\"],\"links\":[\"https://altair-semi.com/technology/\",\"https://altair-semi.com/products/alt1210/\"],\"app\":\"steemit/0.1\"}"
    }
  ]
}
2018/10/06 04:24:27
parent authorpatb
parent permlinkhow-to-make-better-cryptocurrencies-with-pol-and-dash7
authorsteemitboard
permlinksteemitboard-notify-patb-20181006t042426000z
title
bodyCongratulations @patb! You have received a personal award! [![](https://steemitimages.com/70x70/http://steemitboard.com/@patb/birthday1.png)](http://steemitboard.com/@patb) 1 Year on Steemit <sub>_Click on the badge to view your Board of Honor._</sub> **Do not miss the last post from @steemitboard:** <table><tr><td><a href="https://steemit.com/steemitboard/@steemitboard/introducing-steemitboard-ranking"><img src="https://steemitimages.com/64x128/https://cdn.steemitimages.com/DQmfRVpHQhLDhnjDtqck8GPv9NPvNKPfMsDaAFDE1D9Er2Z/header_ranking.png"></a></td><td><a href="https://steemit.com/steemitboard/@steemitboard/introducing-steemitboard-ranking">Introducing SteemitBoard Ranking</a></td></tr></table> > Support [SteemitBoard's project](https://steemit.com/@steemitboard)! **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**!
json metadata{"image":["https://steemitboard.com/img/notify.png"]}
Transaction InfoBlock #26560456/Trx 71f84c4052d6c7207be4d3319e101db4e8a0f31e
View Raw JSON Data
{
  "trx_id": "71f84c4052d6c7207be4d3319e101db4e8a0f31e",
  "block": 26560456,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-10-06T04:24:27",
  "op": [
    "comment",
    {
      "parent_author": "patb",
      "parent_permlink": "how-to-make-better-cryptocurrencies-with-pol-and-dash7",
      "author": "steemitboard",
      "permlink": "steemitboard-notify-patb-20181006t042426000z",
      "title": "",
      "body": "Congratulations @patb! You have received a personal award!\n\n[![](https://steemitimages.com/70x70/http://steemitboard.com/@patb/birthday1.png)](http://steemitboard.com/@patb)  1 Year on Steemit\n<sub>_Click on the badge to view your Board of Honor._</sub>\n\n\n**Do not miss the last post from @steemitboard:**\n<table><tr><td><a href=\"https://steemit.com/steemitboard/@steemitboard/introducing-steemitboard-ranking\"><img src=\"https://steemitimages.com/64x128/https://cdn.steemitimages.com/DQmfRVpHQhLDhnjDtqck8GPv9NPvNKPfMsDaAFDE1D9Er2Z/header_ranking.png\"></a></td><td><a href=\"https://steemit.com/steemitboard/@steemitboard/introducing-steemitboard-ranking\">Introducing SteemitBoard Ranking</a></td></tr></table>\n\n> Support [SteemitBoard's project](https://steemit.com/@steemitboard)! **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**!",
      "json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}"
    }
  ]
}
steemdelegated 5.580 SP to @patb
2018/09/03 18:32:15
delegatorsteem
delegateepatb
vesting shares9086.219120 VESTS
Transaction InfoBlock #25643275/Trx dce6a178fee51450a0742d2bdd2ee830c274cdb6
View Raw JSON Data
{
  "trx_id": "dce6a178fee51450a0742d2bdd2ee830c274cdb6",
  "block": 25643275,
  "trx_in_block": 23,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-09-03T18:32:15",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "patb",
      "vesting_shares": "9086.219120 VESTS"
    }
  ]
}
steemdelegated 18.093 SP to @patb
2018/06/04 19:02:36
delegatorsteem
delegateepatb
vesting shares29463.343869 VESTS
Transaction InfoBlock #23035058/Trx e8c53d8ef21fac09d2079518c61da392911e197b
View Raw JSON Data
{
  "trx_id": "e8c53d8ef21fac09d2079518c61da392911e197b",
  "block": 23035058,
  "trx_in_block": 9,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-04T19:02:36",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "patb",
      "vesting_shares": "29463.343869 VESTS"
    }
  ]
}
2018/06/04 18:14:45
votermartin.starosta
authorpatb
permlinkhow-to-make-better-cryptocurrencies-with-pol-and-dash7
weight1000 (10.00%)
Transaction InfoBlock #23034101/Trx 47d61431b3694bf854cf758e18bb3ccce729f3fc
View Raw JSON Data
{
  "trx_id": "47d61431b3694bf854cf758e18bb3ccce729f3fc",
  "block": 23034101,
  "trx_in_block": 39,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-04T18:14:45",
  "op": [
    "vote",
    {
      "voter": "martin.starosta",
      "author": "patb",
      "permlink": "how-to-make-better-cryptocurrencies-with-pol-and-dash7",
      "weight": 1000
    }
  ]
}
2018/06/04 17:50:45
voterax3
authorpatb
permlinkhow-to-make-better-cryptocurrencies-with-pol-and-dash7
weight100 (1.00%)
Transaction InfoBlock #23033621/Trx 407de4498f42578b5f92a479438d2c90be5ff482
View Raw JSON Data
{
  "trx_id": "407de4498f42578b5f92a479438d2c90be5ff482",
  "block": 23033621,
  "trx_in_block": 58,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-04T17:50:45",
  "op": [
    "vote",
    {
      "voter": "ax3",
      "author": "patb",
      "permlink": "how-to-make-better-cryptocurrencies-with-pol-and-dash7",
      "weight": 100
    }
  ]
}
2018/06/04 17:50:36
parent author
parent permlinkblockchain
authorpatb
permlinkhow-to-make-better-cryptocurrencies-with-pol-and-dash7
titleHow To Make Better Cryptocurrencies with PoL and DASH7
body![cut.jpg](https://cdn.steemitimages.com/DQmdGAunnWjCgpPVYDHhxqXnamYFwwDJQwAwwhpmnR7EJst/cut.jpg) https://medium.com/@patburns/how-to-make-better-cryptocurrencies-with-pol-and-dash7-cccb8cf85e26
json metadata{"tags":["blockchain","cryptocurrency","geolocation","iot","lora"],"image":["https://cdn.steemitimages.com/DQmdGAunnWjCgpPVYDHhxqXnamYFwwDJQwAwwhpmnR7EJst/cut.jpg"],"links":["https://medium.com/@patburns/how-to-make-better-cryptocurrencies-with-pol-and-dash7-cccb8cf85e26"],"app":"steemit/0.1","format":"markdown"}
Transaction InfoBlock #23033618/Trx f7d1d5b31ff85ee8b34c350168b556d49702017f
View Raw JSON Data
{
  "trx_id": "f7d1d5b31ff85ee8b34c350168b556d49702017f",
  "block": 23033618,
  "trx_in_block": 40,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-04T17:50:36",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "blockchain",
      "author": "patb",
      "permlink": "how-to-make-better-cryptocurrencies-with-pol-and-dash7",
      "title": "How To Make Better Cryptocurrencies with PoL and DASH7",
      "body": "![cut.jpg](https://cdn.steemitimages.com/DQmdGAunnWjCgpPVYDHhxqXnamYFwwDJQwAwwhpmnR7EJst/cut.jpg)\n\nhttps://medium.com/@patburns/how-to-make-better-cryptocurrencies-with-pol-and-dash7-cccb8cf85e26",
      "json_metadata": "{\"tags\":[\"blockchain\",\"cryptocurrency\",\"geolocation\",\"iot\",\"lora\"],\"image\":[\"https://cdn.steemitimages.com/DQmdGAunnWjCgpPVYDHhxqXnamYFwwDJQwAwwhpmnR7EJst/cut.jpg\"],\"links\":[\"https://medium.com/@patburns/how-to-make-better-cryptocurrencies-with-pol-and-dash7-cccb8cf85e26\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}
2018/06/02 23:04:09
parent authorpatb
parent permlinkthe-really-hard-thing-about-gps-and-the-iot
authorfy1000000
permlinkre-patb-the-really-hard-thing-about-gps-and-the-iot-20180602t230411467z
title
bodyHi patb, very nicely done blog - good job! I am now following you. I also invite you to take a look at [#BlockchainMyGPS](https://steemit.com/@fy1000000). I will be covering #SnapshotReceiver & #Blockchain technologies for those who are interested in implementing #Wearables and #IoT applications. Hope to see you soon!
json metadata{"tags":["iot","snapshotreceiver","blockchain","wearables"],"links":["https://steemit.com/@fy1000000"],"app":"steemit/0.1"}
Transaction InfoBlock #22982303/Trx fa547e26904b7be675b2debdb13021f48c36d294
View Raw JSON Data
{
  "trx_id": "fa547e26904b7be675b2debdb13021f48c36d294",
  "block": 22982303,
  "trx_in_block": 30,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-02T23:04:09",
  "op": [
    "comment",
    {
      "parent_author": "patb",
      "parent_permlink": "the-really-hard-thing-about-gps-and-the-iot",
      "author": "fy1000000",
      "permlink": "re-patb-the-really-hard-thing-about-gps-and-the-iot-20180602t230411467z",
      "title": "",
      "body": "Hi patb, very nicely done blog - good job! I am now following you. I also invite you to take a look at [#BlockchainMyGPS](https://steemit.com/@fy1000000). I will be covering #SnapshotReceiver & #Blockchain technologies for those who are interested in implementing #Wearables and #IoT applications. Hope to see you soon!",
      "json_metadata": "{\"tags\":[\"iot\",\"snapshotreceiver\",\"blockchain\",\"wearables\"],\"links\":[\"https://steemit.com/@fy1000000\"],\"app\":\"steemit/0.1\"}"
    }
  ]
}
2018/06/02 22:52:33
voterfy1000000
authorpatb
permlinkthe-really-hard-thing-about-gps-and-the-iot
weight10000 (100.00%)
Transaction InfoBlock #22982072/Trx 16fc95b19c51b928493831e2de7c87464aca4ef9
View Raw JSON Data
{
  "trx_id": "16fc95b19c51b928493831e2de7c87464aca4ef9",
  "block": 22982072,
  "trx_in_block": 104,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-02T22:52:33",
  "op": [
    "vote",
    {
      "voter": "fy1000000",
      "author": "patb",
      "permlink": "the-really-hard-thing-about-gps-and-the-iot",
      "weight": 10000
    }
  ]
}
steemdelegated 5.616 SP to @patb
2018/05/16 23:35:51
delegatorsteem
delegateepatb
vesting shares9145.035647 VESTS
Transaction InfoBlock #22493818/Trx 77b36760ce124ae4f7caf60ce6427c9d82326a9c
View Raw JSON Data
{
  "trx_id": "77b36760ce124ae4f7caf60ce6427c9d82326a9c",
  "block": 22493818,
  "trx_in_block": 10,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-05-16T23:35:51",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "patb",
      "vesting_shares": "9145.035647 VESTS"
    }
  ]
}
steemdelegated 18.195 SP to @patb
2018/02/21 23:14:00
delegatorsteem
delegateepatb
vesting shares29627.890851 VESTS
Transaction InfoBlock #20076710/Trx 70aa0dbf2688134c8d8b1f752e153f7fbb9de0b4
View Raw JSON Data
{
  "trx_id": "70aa0dbf2688134c8d8b1f752e153f7fbb9de0b4",
  "block": 20076710,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-02-21T23:14:00",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "patb",
      "vesting_shares": "29627.890851 VESTS"
    }
  ]
}
2017/11/09 21:46:57
authorpatb
permlink2dzqvu-the-really-hard-thing-about-gps-and-the-iot
sbd payout0.000 SBD
steem payout0.000 STEEM
vesting payout84.238143 VESTS
Transaction InfoBlock #17081906/Virtual Operation #9
View Raw JSON Data
{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 17081906,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 9,
  "timestamp": "2017-11-09T21:46:57",
  "op": [
    "author_reward",
    {
      "author": "patb",
      "permlink": "2dzqvu-the-really-hard-thing-about-gps-and-the-iot",
      "sbd_payout": "0.000 SBD",
      "steem_payout": "0.000 STEEM",
      "vesting_payout": "84.238143 VESTS"
    }
  ]
}
2017/11/02 22:27:06
voterpatb
authorcontentjunkie
permlinknext-generation-of-tech-geniuses-signing-up-to-study-cryptocurrencies
weight10000 (100.00%)
Transaction InfoBlock #16881291/Trx 907b767e00b96f4cb095846fdba02057b342bd88
View Raw JSON Data
{
  "trx_id": "907b767e00b96f4cb095846fdba02057b342bd88",
  "block": 16881291,
  "trx_in_block": 11,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-11-02T22:27:06",
  "op": [
    "vote",
    {
      "voter": "patb",
      "author": "contentjunkie",
      "permlink": "next-generation-of-tech-geniuses-signing-up-to-study-cryptocurrencies",
      "weight": 10000
    }
  ]
}
2017/11/02 22:01:57
votergimpu
authorpatb
permlink2dzqvu-the-really-hard-thing-about-gps-and-the-iot
weight-10000 (-100.00%)
Transaction InfoBlock #16880788/Trx 11bc0e64ad996efb7c251ab0330df1e9324afaa1
View Raw JSON Data
{
  "trx_id": "11bc0e64ad996efb7c251ab0330df1e9324afaa1",
  "block": 16880788,
  "trx_in_block": 10,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-11-02T22:01:57",
  "op": [
    "vote",
    {
      "voter": "gimpu",
      "author": "patb",
      "permlink": "2dzqvu-the-really-hard-thing-about-gps-and-the-iot",
      "weight": -10000
    }
  ]
}
2017/11/02 21:51:18
voterlowpass303
authorpatb
permlink2dzqvu-the-really-hard-thing-about-gps-and-the-iot
weight10000 (100.00%)
Transaction InfoBlock #16880575/Trx 213422ebf49a717161a9f312431816f3e248687a
View Raw JSON Data
{
  "trx_id": "213422ebf49a717161a9f312431816f3e248687a",
  "block": 16880575,
  "trx_in_block": 3,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-11-02T21:51:18",
  "op": [
    "vote",
    {
      "voter": "lowpass303",
      "author": "patb",
      "permlink": "2dzqvu-the-really-hard-thing-about-gps-and-the-iot",
      "weight": 10000
    }
  ]
}
2017/11/02 21:50:36
voterbeartooth-clark
authorpatb
permlink2dzqvu-the-really-hard-thing-about-gps-and-the-iot
weight10000 (100.00%)
Transaction InfoBlock #16880561/Trx 9cb7d984faf2d7d798b91a27af24e84425b39129
View Raw JSON Data
{
  "trx_id": "9cb7d984faf2d7d798b91a27af24e84425b39129",
  "block": 16880561,
  "trx_in_block": 8,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-11-02T21:50:36",
  "op": [
    "vote",
    {
      "voter": "beartooth-clark",
      "author": "patb",
      "permlink": "2dzqvu-the-really-hard-thing-about-gps-and-the-iot",
      "weight": 10000
    }
  ]
}
2017/11/02 21:48:21
voterpatb
authorpatb
permlinkthe-really-hard-thing-about-gps-and-the-iot
weight10000 (100.00%)
Transaction InfoBlock #16880516/Trx 79392140557a07c7db2317fa466793d1a78cb5de
View Raw JSON Data
{
  "trx_id": "79392140557a07c7db2317fa466793d1a78cb5de",
  "block": 16880516,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-11-02T21:48:21",
  "op": [
    "vote",
    {
      "voter": "patb",
      "author": "patb",
      "permlink": "the-really-hard-thing-about-gps-and-the-iot",
      "weight": 10000
    }
  ]
}
2017/11/02 21:48:03
parent authorpatb
parent permlink2dzqvu-the-really-hard-thing-about-gps-and-the-iot
authorbeerbot
permlinkre-2dzqvu-the-really-hard-thing-about-gps-and-the-iot-20171102t214802
title
body **Hello & Cheers!!** I'm a content detection and information bot. You are receiving this reply because a short link or links have been detected in your post/comment. The purpose of this message is to inform your readers and yourself about the use of and dangers of short links. **To the readers of the post:** Short links are provided by [url shortening](https://en.wikipedia.org/wiki/URL_shortening) services. The short links they provide can be useful in some cases. Generally their use is benign. But as with all useful tools there are dangers. Short links can be used to hide all sorts of things. Quite frequently they are used to hide referral links for instance. While not dangerous this can be deceptive. They can also be used to hide dangerous links such as links to phishing sites, sites loaded with malware, scam sites, etc. You should always be extremely cautious before clicking on one. If you don't know and trust the poster don't click. Even if you do you should still be cautious and wary of any site you are sent to. It's always better to visit the site directly and not through a short link. **To the author of the post:** While short links may be useful on some sites they are not needed on steemit. You can use markdown to format your links such as this link to [steemit](https://steemit.com). It's as simple as `[steemit](https://steemit.com)` Unlike short links this allows the reader to see where they are going by simply hovering over the link before they click on it. | | | | ---- | ---- | | <sup><sub>This message was created by a bot. It is part of the ongoing fight against spam and phishing attacks on steemit. If you did not use short links in your post and feel you have received this message in error you can contact @fubar-bdhr on discord or @fubar.bdhr on steemit chat to report the issue.</sub></sup> |![](https://steemitimages.com/DQmPaR3USbBnbvB4j69Ffh2wPJYnJSoF6BSTgdJ71QVRoJP/image.png) |
json metadata{"app": "pysteem/0.5.6"}
Transaction InfoBlock #16880510/Trx 6c55f30594db1a3ee2a885ae8a8f2b57b07595af
View Raw JSON Data
{
  "trx_id": "6c55f30594db1a3ee2a885ae8a8f2b57b07595af",
  "block": 16880510,
  "trx_in_block": 17,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-11-02T21:48:03",
  "op": [
    "comment",
    {
      "parent_author": "patb",
      "parent_permlink": "2dzqvu-the-really-hard-thing-about-gps-and-the-iot",
      "author": "beerbot",
      "permlink": "re-2dzqvu-the-really-hard-thing-about-gps-and-the-iot-20171102t214802",
      "title": "",
      "body": "\n\n**Hello & Cheers!!** I'm a content detection and information bot.  You are receiving this reply because a short link or links have been detected in your post/comment.  The purpose of this message is to inform your readers and yourself about the use of and dangers of short links.\n\n**To the readers of the post:**  Short links are provided by [url shortening](https://en.wikipedia.org/wiki/URL_shortening) services.  The short links they provide can be useful in some cases.  Generally their use is benign.  But as with all useful tools there are dangers.  Short links can be used to hide all sorts of things.  Quite frequently they are used to hide referral links for instance.  While not dangerous this can be deceptive.  They can also be used to hide dangerous links such as links to phishing sites, sites loaded with malware, scam sites, etc.  You should always be extremely cautious before clicking on one.  If you don't know and trust the poster don't click.  Even if you do you should still be cautious and wary of any site you are sent to. It's always better to visit the site directly and not through a short link.  \n\n**To the author of the post:**  While short links may be useful on some sites they are not needed on steemit.  You can use markdown to format your links such as this link to [steemit](https://steemit.com).  It's as simple as `[steemit](https://steemit.com)`  Unlike short links this allows the reader to see where they are going by simply hovering over the link before they click on it.  \n\n|     |   |  \n| ---- | ---- |\n| <sup><sub>This message was created by a bot.  It is part of the ongoing fight against spam and phishing attacks on steemit.  If you did not use short links in your post and feel you have received this message in error you can contact @fubar-bdhr on discord or @fubar.bdhr on steemit chat to report the issue.</sub></sup> |![](https://steemitimages.com/DQmPaR3USbBnbvB4j69Ffh2wPJYnJSoF6BSTgdJ71QVRoJP/image.png) |",
      "json_metadata": "{\"app\": \"pysteem/0.5.6\"}"
    }
  ]
}
2017/11/02 21:47:18
parent authorpatb
parent permlink2dzqvu-the-really-hard-thing-about-gps-and-the-iot
authorcheetah
permlinkcheetah-re-patb2dzqvu-the-really-hard-thing-about-gps-and-the-iot
title
bodyHi! I am a robot. I just upvoted you! I found similar content that readers might be interested in: http://haystacktechnologies.com/the-really-hard-thing-about-gps-and-the-iot/
json metadata
Transaction InfoBlock #16880495/Trx 9d5153c1cd77608ac022b6a6870ea743f067c57f
View Raw JSON Data
{
  "trx_id": "9d5153c1cd77608ac022b6a6870ea743f067c57f",
  "block": 16880495,
  "trx_in_block": 6,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-11-02T21:47:18",
  "op": [
    "comment",
    {
      "parent_author": "patb",
      "parent_permlink": "2dzqvu-the-really-hard-thing-about-gps-and-the-iot",
      "author": "cheetah",
      "permlink": "cheetah-re-patb2dzqvu-the-really-hard-thing-about-gps-and-the-iot",
      "title": "",
      "body": "Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in:\nhttp://haystacktechnologies.com/the-really-hard-thing-about-gps-and-the-iot/",
      "json_metadata": ""
    }
  ]
}
2017/11/02 21:47:12
votercheetah
authorpatb
permlink2dzqvu-the-really-hard-thing-about-gps-and-the-iot
weight50 (0.50%)
Transaction InfoBlock #16880493/Trx 4644d1f07918225992e9f545ac3a6c881022a6d2
View Raw JSON Data
{
  "trx_id": "4644d1f07918225992e9f545ac3a6c881022a6d2",
  "block": 16880493,
  "trx_in_block": 26,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-11-02T21:47:12",
  "op": [
    "vote",
    {
      "voter": "cheetah",
      "author": "patb",
      "permlink": "2dzqvu-the-really-hard-thing-about-gps-and-the-iot",
      "weight": 50
    }
  ]
}
2017/11/02 21:46:57
voterpatb
authorpatb
permlink2dzqvu-the-really-hard-thing-about-gps-and-the-iot
weight10000 (100.00%)
Transaction InfoBlock #16880488/Trx 00d6528825140ce912006442cef32318e92efc01
View Raw JSON Data
{
  "trx_id": "00d6528825140ce912006442cef32318e92efc01",
  "block": 16880488,
  "trx_in_block": 19,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-11-02T21:46:57",
  "op": [
    "vote",
    {
      "voter": "patb",
      "author": "patb",
      "permlink": "2dzqvu-the-really-hard-thing-about-gps-and-the-iot",
      "weight": 10000
    }
  ]
}
2017/11/02 21:46:57
authorpatb
permlink2dzqvu-the-really-hard-thing-about-gps-and-the-iot
max accepted payout1000000.000 SBD
percent steem dollars0
allow votestrue
allow curation rewardstrue
extensions[]
Transaction InfoBlock #16880488/Trx 00d6528825140ce912006442cef32318e92efc01
View Raw JSON Data
{
  "trx_id": "00d6528825140ce912006442cef32318e92efc01",
  "block": 16880488,
  "trx_in_block": 19,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-11-02T21:46:57",
  "op": [
    "comment_options",
    {
      "author": "patb",
      "permlink": "2dzqvu-the-really-hard-thing-about-gps-and-the-iot",
      "max_accepted_payout": "1000000.000 SBD",
      "percent_steem_dollars": 0,
      "allow_votes": true,
      "allow_curation_rewards": true,
      "extensions": []
    }
  ]
}
2017/11/02 21:46:57
parent author
parent permlinkiot
authorpatb
permlink2dzqvu-the-really-hard-thing-about-gps-and-the-iot
titleThe Really Hard Thing About GPS and the IoT
body![IMG_9099_low.jpg](https://steemitimages.com/DQmQE7gKTQfaHT2tu285Y3hPY7u7ztHTpcNkd9au51vgZsV/IMG_9099_low.jpg) “All things excellent are as difficult as they are rare.” - Baruch Spinoza TL;DR: - The mobile IoT needs GPS - GPS is traditionally not low power - Getting GPS right with low power requires a tricky confluence of technologies This month, I witnessed a “coming out” party of sorts for a new LTE NB-IoT product from Samsung. It’s a “tracker” that you can put on dogs, bikes, kids, or whatever moves. (http://zd.net/2yrMDB9) At first blush, it is an exciting product: - It is IP68 water- and dust-proof, has a horizontal/vertical of 4.21cm, and is 1.19cm thick. - It is optimal for indoor and outdoor use, including pet and children tracking, protecting personal items, and attaching to luggage. - An attachable ring will enable it to be hung on bags and key chains. - It also has an on-demand feature, where it will show its location and set times; while its geo-fence feature alerts users when it has left a set virtual zone - It can also be synced with smart home appliances to turn on the light, TV, or the robot cleaner when close to home. Small, versatile, feature rich … what’s not to like, right? Except this: "Connect Tag consumes little energy and data, and a full charge will last seven days." NB-IoT, as most readers of this website probably know, is the cellular industry’s response to Sigfox and LoRa. Another cellular response, LTE CAT M1, has outed itself as a “high power” WAN technology. So, NB-IoT is supposed to be the cellular industry low power savior: long range plus low power and, of course, low cost. Now, it’s possible that this is just a bad implementation of GPS over NB-IoT, but let’s just assume Samsung knows a thing or two about wireless and location services. So what happened? There’s something inherent in the NB-IoT stack that isn’t very “low power”, after all, which seems unlikely given what we hear about the uptake of NB-IoT for fixed meter reading; or NB-IoT can’t easily support “hot start” GPS location acquisition. GPS, as I’ve written before (http://bit.ly/2pBcYqp), can be a very power hungry component of a mobile IoT endpoint. Historically, we’ve seen mobile GPS endpoints married with cellular, which (usually) promised around 30 days of battery life and often delivered far less. LPWAN’s were supposed to change all that, but in the Samsung case above, battery life, it would appear, got worse. A GPS receiver needs to locate at least four satellites in the sky in order to compute its location, and the time required to do so can range from a few seconds to many minutes. A “cold start” can force your mobile endpoint into searching for satellites for many minutes … with predictable battery life results. A “hot” start, on the other hand, can enable the endpoint to acquire GPS coordinates in a few seconds. So to avoid battery meltdown on your GPS-enabled mobile IoT device, hot starts are extremely helpful. Enabling a GPS hot start requires the network to broadcast a kind of “cheat sheet” to the GPS receiver to allow it to acquire location more quickly. For many Assisted GPS or “A-GPS” is the mechanism for doing this. (http://bit.ly/2p1E6hh) Low Power Wide Area Networking technologies are about battery powered devices that can communicate over long distances and deliver long — as in multi-year — battery life. Today, lots of LPWAN technologies are being deployed in fixed use cases — meter reading, for example — and simply send a message once a day back to a host reporting on the day’s usage. Water meters, for example. But deploying LPWAN’s for real-time outdoor location is another matter. While there are multiple techniques for deriving location without GPS, most LPWAN protocols at best offer a high-latency, low accuracy form of location that would be hard to characterize as real-time. Adding GPS to these requires the GPS receiver to be active and, in most cases, in a perpetual state of looking for satellite signals. Even invoking GPS based on an event (e.g. movement) is full of risks like false positives that will also deplete a battery. A-GPS mitigates this power draw problem but … supporting it correctly remains elusive for many (but not all) LPWAN protocols. It is unclear whether this is the driver behind the Samsung NB-IoT battery life issue, but I look forward to hearing more detail from those closer to that product.
json metadata{"tags":["iot"],"image":["https://steemitimages.com/DQmQE7gKTQfaHT2tu285Y3hPY7u7ztHTpcNkd9au51vgZsV/IMG_9099_low.jpg"],"links":["http://zd.net/2yrMDB9","http://bit.ly/2pBcYqp","http://bit.ly/2p1E6hh"],"app":"steemit/0.1","format":"markdown"}
Transaction InfoBlock #16880488/Trx 00d6528825140ce912006442cef32318e92efc01
View Raw JSON Data
{
  "trx_id": "00d6528825140ce912006442cef32318e92efc01",
  "block": 16880488,
  "trx_in_block": 19,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-11-02T21:46:57",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "iot",
      "author": "patb",
      "permlink": "2dzqvu-the-really-hard-thing-about-gps-and-the-iot",
      "title": "The Really Hard Thing About GPS and the IoT",
      "body": "![IMG_9099_low.jpg](https://steemitimages.com/DQmQE7gKTQfaHT2tu285Y3hPY7u7ztHTpcNkd9au51vgZsV/IMG_9099_low.jpg)\n\n“All things excellent are as difficult as they are rare.”\n\n- Baruch Spinoza\n\nTL;DR:\n- The mobile IoT needs GPS\n- GPS is traditionally not low power\n- Getting GPS right with low power requires a tricky confluence of technologies\n\nThis month, I witnessed a “coming out” party of sorts for a new LTE NB-IoT product from Samsung. It’s a “tracker” that you can put on dogs, bikes, kids, or whatever moves. (http://zd.net/2yrMDB9)\n\nAt first blush, it is an exciting product:\n\n- It is IP68 water- and dust-proof, has a horizontal/vertical of 4.21cm, and is 1.19cm thick.\n\n- It is optimal for indoor and outdoor use, including pet and children tracking, protecting personal items, and attaching to luggage.\n\n- An attachable ring will enable it to be hung on bags and key chains.\n\n- It also has an on-demand feature, where it will show its location and set times; while its geo-fence feature alerts users when it has left a set virtual zone\n\n- It can also be synced with smart home appliances to turn on the light, TV, or the robot cleaner when close to home.\nSmall, versatile, feature rich … what’s not to like, right?\n\nExcept this:\n\n\"Connect Tag consumes little energy and data, and a full charge will last seven days.\"\n\nNB-IoT, as most readers of this website probably know, is the cellular industry’s response to Sigfox and LoRa. Another cellular response, LTE CAT M1, has outed itself as a “high power” WAN technology. So, NB-IoT is supposed to be the cellular industry low power savior: long range plus low power and, of course, low cost.\n\nNow, it’s possible that this is just a bad implementation of GPS over NB-IoT, but let’s just assume Samsung knows a thing or two about wireless and location services. So what happened?\n\nThere’s something inherent in the NB-IoT stack that isn’t very “low power”, after all, which seems unlikely given what we hear about the uptake of NB-IoT for fixed meter reading; or\n\nNB-IoT can’t easily support “hot start” GPS location acquisition.\n\nGPS, as I’ve written before (http://bit.ly/2pBcYqp), can be a very power hungry component of a mobile IoT endpoint. Historically, we’ve seen mobile GPS endpoints married with cellular, which (usually) promised around 30 days of battery life and often delivered far less. LPWAN’s were supposed to change all that, but in the Samsung case above, battery life, it would appear, got worse.\n\nA GPS receiver needs to locate at least four satellites in the sky in order to compute its location, and the time required to do so can range from a few seconds to many minutes. A “cold start” can force your mobile endpoint into searching for satellites for many minutes … with predictable battery life results. A “hot” start, on the other hand, can enable the endpoint to acquire GPS coordinates in a few seconds.\n\nSo to avoid battery meltdown on your GPS-enabled mobile IoT device, hot starts are extremely helpful. Enabling a GPS hot start requires the network to broadcast a kind of “cheat sheet” to the GPS receiver to allow it to acquire location more quickly. For many Assisted GPS or “A-GPS” is the mechanism for doing this. (http://bit.ly/2p1E6hh)\n\nLow Power Wide Area Networking technologies are about battery powered devices that can communicate over long distances and deliver long — as in multi-year — battery life. Today, lots of LPWAN technologies are being deployed in fixed use cases — meter reading, for example — and simply send a message once a day back to a host reporting on the day’s usage. Water meters, for example.\n\nBut deploying LPWAN’s for real-time outdoor location is another matter. While there are multiple techniques for deriving location without GPS, most LPWAN protocols at best offer a high-latency, low accuracy form of location that would be hard to characterize as real-time. Adding GPS to these requires the GPS receiver to be active and, in most cases, in a perpetual state of looking for satellite signals. Even invoking GPS based on an event (e.g. movement) is full of risks like false positives that will also deplete a battery. A-GPS mitigates this power draw problem but … supporting it correctly remains elusive for many (but not all) LPWAN protocols. It is unclear whether this is the driver behind the Samsung NB-IoT battery life issue, but I look forward to hearing more detail from those closer to that product.",
      "json_metadata": "{\"tags\":[\"iot\"],\"image\":[\"https://steemitimages.com/DQmQE7gKTQfaHT2tu285Y3hPY7u7ztHTpcNkd9au51vgZsV/IMG_9099_low.jpg\"],\"links\":[\"http://zd.net/2yrMDB9\",\"http://bit.ly/2pBcYqp\",\"http://bit.ly/2p1E6hh\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}
2017/11/02 02:42:51
voteryunisteem
authorpatb
permlinkthe-really-hard-thing-about-gps-and-the-iot
weight10000 (100.00%)
Transaction InfoBlock #16857609/Trx 93a583b3a4c309635ee6212c57f4c22aabe05a6b
View Raw JSON Data
{
  "trx_id": "93a583b3a4c309635ee6212c57f4c22aabe05a6b",
  "block": 16857609,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-11-02T02:42:51",
  "op": [
    "vote",
    {
      "voter": "yunisteem",
      "author": "patb",
      "permlink": "the-really-hard-thing-about-gps-and-the-iot",
      "weight": 10000
    }
  ]
}
2017/11/02 02:36:18
parent authorpatb
parent permlinkthe-really-hard-thing-about-gps-and-the-iot
authorcheetah
permlinkcheetah-re-patbthe-really-hard-thing-about-gps-and-the-iot
title
bodyHi! I am a robot. I just upvoted you! I found similar content that readers might be interested in: http://haystacktechnologies.com/the-really-hard-thing-about-gps-and-the-iot/
json metadata
Transaction InfoBlock #16857478/Trx 60ed085641bb064f5b93e7ea0a10571a5fdbdc45
View Raw JSON Data
{
  "trx_id": "60ed085641bb064f5b93e7ea0a10571a5fdbdc45",
  "block": 16857478,
  "trx_in_block": 16,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-11-02T02:36:18",
  "op": [
    "comment",
    {
      "parent_author": "patb",
      "parent_permlink": "the-really-hard-thing-about-gps-and-the-iot",
      "author": "cheetah",
      "permlink": "cheetah-re-patbthe-really-hard-thing-about-gps-and-the-iot",
      "title": "",
      "body": "Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in:\nhttp://haystacktechnologies.com/the-really-hard-thing-about-gps-and-the-iot/",
      "json_metadata": ""
    }
  ]
}
2017/11/02 02:36:12
parent authorpatb
parent permlinkthe-really-hard-thing-about-gps-and-the-iot
authorbeerbot
permlinkre-the-really-hard-thing-about-gps-and-the-iot-20171102t023611
title
body **Hello & Cheers!!** I'm a content detection and information bot. You are receiving this reply because a short link or links have been detected in your post/comment. The purpose of this message is to inform your readers and yourself about the use of and dangers of short links. **To the readers of the post:** Short links are provided by [url shortening](https://en.wikipedia.org/wiki/URL_shortening) services. The short links they provide can be useful in some cases. Generally their use is benign. But as with all useful tools there are dangers. Short links can be used to hide all sorts of things. Quite frequently they are used to hide referral links for instance. While not dangerous this can be deceptive. They can also be used to hide dangerous links such as links to phishing sites, sites loaded with malware, scam sites, etc. You should always be extremely cautious before clicking on one. If you don't know and trust the poster don't click. Even if you do you should still be cautious and wary of any site you are sent to. It's always better to visit the site directly and not through a short link. **To the author of the post:** While short links may be useful on some sites they are not needed on steemit. You can use markdown to format your links such as this link to [steemit](https://steemit.com). It's as simple as `[steemit](https://steemit.com)` Unlike short links this allows the reader to see where they are going by simply hovering over the link before they click on it. | | | | ---- | ---- | | <sup><sub>This message was created by a bot. It is part of the ongoing fight against spam and phishing attacks on steemit. If you did not use short links in your post and feel you have received this message in error you can contact @fubar-bdhr on discord or @fubar.bdhr on steemit chat to report the issue.</sub></sup> |![](https://steemitimages.com/DQmPaR3USbBnbvB4j69Ffh2wPJYnJSoF6BSTgdJ71QVRoJP/image.png) |
json metadata{"app": "pysteem/0.5.6"}
Transaction InfoBlock #16857476/Trx ef109a3d261e746eb3a97f6b28be1458638ce64b
View Raw JSON Data
{
  "trx_id": "ef109a3d261e746eb3a97f6b28be1458638ce64b",
  "block": 16857476,
  "trx_in_block": 11,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-11-02T02:36:12",
  "op": [
    "comment",
    {
      "parent_author": "patb",
      "parent_permlink": "the-really-hard-thing-about-gps-and-the-iot",
      "author": "beerbot",
      "permlink": "re-the-really-hard-thing-about-gps-and-the-iot-20171102t023611",
      "title": "",
      "body": "\n\n**Hello & Cheers!!** I'm a content detection and information bot.  You are receiving this reply because a short link or links have been detected in your post/comment.  The purpose of this message is to inform your readers and yourself about the use of and dangers of short links.\n\n**To the readers of the post:**  Short links are provided by [url shortening](https://en.wikipedia.org/wiki/URL_shortening) services.  The short links they provide can be useful in some cases.  Generally their use is benign.  But as with all useful tools there are dangers.  Short links can be used to hide all sorts of things.  Quite frequently they are used to hide referral links for instance.  While not dangerous this can be deceptive.  They can also be used to hide dangerous links such as links to phishing sites, sites loaded with malware, scam sites, etc.  You should always be extremely cautious before clicking on one.  If you don't know and trust the poster don't click.  Even if you do you should still be cautious and wary of any site you are sent to. It's always better to visit the site directly and not through a short link.  \n\n**To the author of the post:**  While short links may be useful on some sites they are not needed on steemit.  You can use markdown to format your links such as this link to [steemit](https://steemit.com).  It's as simple as `[steemit](https://steemit.com)`  Unlike short links this allows the reader to see where they are going by simply hovering over the link before they click on it.  \n\n|     |   |  \n| ---- | ---- |\n| <sup><sub>This message was created by a bot.  It is part of the ongoing fight against spam and phishing attacks on steemit.  If you did not use short links in your post and feel you have received this message in error you can contact @fubar-bdhr on discord or @fubar.bdhr on steemit chat to report the issue.</sub></sup> |![](https://steemitimages.com/DQmPaR3USbBnbvB4j69Ffh2wPJYnJSoF6BSTgdJ71QVRoJP/image.png) |",
      "json_metadata": "{\"app\": \"pysteem/0.5.6\"}"
    }
  ]
}
2017/11/02 02:35:51
votercheetah
authorpatb
permlinkthe-really-hard-thing-about-gps-and-the-iot
weight50 (0.50%)
Transaction InfoBlock #16857469/Trx da6ac67be704bd0bcdc8d8cd0735468b64fa4b08
View Raw JSON Data
{
  "trx_id": "da6ac67be704bd0bcdc8d8cd0735468b64fa4b08",
  "block": 16857469,
  "trx_in_block": 11,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-11-02T02:35:51",
  "op": [
    "vote",
    {
      "voter": "cheetah",
      "author": "patb",
      "permlink": "the-really-hard-thing-about-gps-and-the-iot",
      "weight": 50
    }
  ]
}
2017/11/02 02:35:18
parent author
parent permlinkiot
authorpatb
permlinkthe-really-hard-thing-about-gps-and-the-iot
titleThe Really Hard Thing About GPS and the IoT
body“All things excellent are as difficult as they are rare.” - Baruch Spinoza TL;DR: - The mobile IoT needs GPS - GPS is traditionally not low power - Getting GPS right with low power requires a tricky confluence of technologies This month, I witnessed a “coming out” party of sorts for a new LTE NB-IoT product from Samsung. It’s a “tracker” that you can put on dogs, bikes, kids, or whatever moves. (http://zd.net/2yrMDB9) At first blush, it is an exciting product: - It is IP68 water- and dust-proof, has a horizontal/vertical of 4.21cm, and is 1.19cm thick. - It is optimal for indoor and outdoor use, including pet and children tracking, protecting personal items, and attaching to luggage. - An attachable ring will enable it to be hung on bags and key chains. - It also has an on-demand feature, where it will show its location and set times; while its geo-fence feature alerts users when it has left a set virtual zone - It can also be synced with smart home appliances to turn on the light, TV, or the robot cleaner when close to home. Small, versatile, feature rich … what’s not to like, right? Except this: "Connect Tag consumes little energy and data, and a full charge will last seven days." NB-IoT, as most readers of this website probably know, is the cellular industry’s response to Sigfox and LoRa. Another cellular response, LTE CAT M1, has outed itself as a “high power” WAN technology. So, NB-IoT is supposed to be the cellular industry low power savior: long range plus low power and, of course, low cost. Now, it’s possible that this is just a bad implementation of GPS over NB-IoT, but let’s just assume Samsung knows a thing or two about wireless and location services. So what happened? There’s something inherent in the NB-IoT stack that isn’t very “low power”, after all, which seems unlikely given what we hear about the uptake of NB-IoT for fixed meter reading; or NB-IoT can’t easily support “hot start” GPS location acquisition. GPS, as I’ve written before (http://bit.ly/2pBcYqp), can be a very power hungry component of a mobile IoT endpoint. Historically, we’ve seen mobile GPS endpoints married with cellular, which (usually) promised around 30 days of battery life and often delivered far less. LPWAN’s were supposed to change all that, but in the Samsung case above, battery life, it would appear, got worse. A GPS receiver needs to locate at least four satellites in the sky in order to compute its location, and the time required to do so can range from a few seconds to many minutes. A “cold start” can force your mobile endpoint into searching for satellites for many minutes … with predictable battery life results. A “hot” start, on the other hand, can enable the endpoint to acquire GPS coordinates in a few seconds. So to avoid battery meltdown on your GPS-enabled mobile IoT device, hot starts are extremely helpful. Enabling a GPS hot start requires the network to broadcast a kind of “cheat sheet” to the GPS receiver to allow it to acquire location more quickly. For many Assisted GPS or “A-GPS” is the mechanism for doing this. (http://bit.ly/2p1E6hh) Low Power Wide Area Networking technologies are about battery powered devices that can communicate over long distances and deliver long — as in multi-year — battery life. Today, lots of LPWAN technologies are being deployed in fixed use cases — meter reading, for example — and simply send a message once a day back to a host reporting on the day’s usage. Water meters, for example. But deploying LPWAN’s for real-time outdoor location is another matter. While there are multiple techniques for deriving location without GPS, most LPWAN protocols at best offer a high-latency, low accuracy form of location that would be hard to characterize as real-time. Adding GPS to these requires the GPS receiver to be active and, in most cases, in a perpetual state of looking for satellite signals. Even invoking GPS based on an event (e.g. movement) is full of risks like false positives that will also deplete a battery. A-GPS mitigates this power draw problem but … supporting it correctly remains elusive for many (but not all) LPWAN protocols. It is unclear whether this is the driver behind the Samsung NB-IoT battery life issue, but I look forward to hearing more detail from those closer to that product.
json metadata{"tags":["iot","gps","telecom","tech","business"],"links":["http://zd.net/2yrMDB9","http://bit.ly/2pBcYqp","http://bit.ly/2p1E6hh"],"app":"steemit/0.1","format":"markdown"}
Transaction InfoBlock #16857458/Trx 3eb6bcbc841db8d8780a8a93eeca33ce054da6a3
View Raw JSON Data
{
  "trx_id": "3eb6bcbc841db8d8780a8a93eeca33ce054da6a3",
  "block": 16857458,
  "trx_in_block": 14,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-11-02T02:35:18",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "iot",
      "author": "patb",
      "permlink": "the-really-hard-thing-about-gps-and-the-iot",
      "title": "The Really Hard Thing About GPS and the IoT",
      "body": "“All things excellent are as difficult as they are rare.”\n- Baruch Spinoza\n\nTL;DR:\n- The mobile IoT needs GPS\n- GPS is traditionally not low power\n- Getting GPS right with low power requires a tricky confluence of technologies\n\nThis month, I witnessed a “coming out” party of sorts for a new LTE NB-IoT product from Samsung. It’s a “tracker” that you can put on dogs, bikes, kids, or whatever moves. (http://zd.net/2yrMDB9)\n\nAt first blush, it is an exciting product:\n\n- It is IP68 water- and dust-proof, has a horizontal/vertical of 4.21cm, and is 1.19cm thick.\n\n- It is optimal for indoor and outdoor use, including pet and children tracking, protecting personal items, and attaching to luggage.\n\n- An attachable ring will enable it to be hung on bags and key chains.\n\n- It also has an on-demand feature, where it will show its location and set times; while its geo-fence feature alerts users when it has left a set virtual zone\n\n- It can also be synced with smart home appliances to turn on the light, TV, or the robot cleaner when close to home.\nSmall, versatile, feature rich … what’s not to like, right?\n\nExcept this:\n\n\"Connect Tag consumes little energy and data, and a full charge will last seven days.\"\n\nNB-IoT, as most readers of this website probably know, is the cellular industry’s response to Sigfox and LoRa. Another cellular response, LTE CAT M1, has outed itself as a “high power” WAN technology. So, NB-IoT is supposed to be the cellular industry low power savior: long range plus low power and, of course, low cost.\n\nNow, it’s possible that this is just a bad implementation of GPS over NB-IoT, but let’s just assume Samsung knows a thing or two about wireless and location services. So what happened?\n\nThere’s something inherent in the NB-IoT stack that isn’t very “low power”, after all, which seems unlikely given what we hear about the uptake of NB-IoT for fixed meter reading; or\n\nNB-IoT can’t easily support “hot start” GPS location acquisition.\n\nGPS, as I’ve written before (http://bit.ly/2pBcYqp), can be a very power hungry component of a mobile IoT endpoint. Historically, we’ve seen mobile GPS endpoints married with cellular, which (usually) promised around 30 days of battery life and often delivered far less. LPWAN’s were supposed to change all that, but in the Samsung case above, battery life, it would appear, got worse.\n\nA GPS receiver needs to locate at least four satellites in the sky in order to compute its location, and the time required to do so can range from a few seconds to many minutes. A “cold start” can force your mobile endpoint into searching for satellites for many minutes … with predictable battery life results. A “hot” start, on the other hand, can enable the endpoint to acquire GPS coordinates in a few seconds.\n\nSo to avoid battery meltdown on your GPS-enabled mobile IoT device, hot starts are extremely helpful. Enabling a GPS hot start requires the network to broadcast a kind of “cheat sheet” to the GPS receiver to allow it to acquire location more quickly. For many Assisted GPS or “A-GPS” is the mechanism for doing this. (http://bit.ly/2p1E6hh) \n\nLow Power Wide Area Networking technologies are about battery powered devices that can communicate over long distances and deliver long — as in multi-year — battery life. Today, lots of LPWAN technologies are being deployed in fixed use cases — meter reading, for example — and simply send a message once a day back to a host reporting on the day’s usage. Water meters, for example.\n\nBut deploying LPWAN’s for real-time outdoor location is another matter. While there are multiple techniques for deriving location without GPS, most LPWAN protocols at best offer a high-latency, low accuracy form of location that would be hard to characterize as real-time. Adding GPS to these requires the GPS receiver to be active and, in most cases, in a perpetual state of looking for satellite signals. Even invoking GPS based on an event (e.g. movement) is full of risks like false positives that will also deplete a battery. A-GPS mitigates this power draw problem but … supporting it correctly remains elusive for many (but not all) LPWAN protocols. It is unclear whether this is the driver behind the Samsung NB-IoT battery life issue, but I look forward to hearing more detail from those closer to that product.",
      "json_metadata": "{\"tags\":[\"iot\",\"gps\",\"telecom\",\"tech\",\"business\"],\"links\":[\"http://zd.net/2yrMDB9\",\"http://bit.ly/2pBcYqp\",\"http://bit.ly/2p1E6hh\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}
steemdelegated 18.320 SP to @patb
2017/10/13 05:12:27
delegatorsteem
delegateepatb
vesting shares29832.874269 VESTS
Transaction InfoBlock #16285245/Trx 605c9f22f377f499b9d02b2836ce5376934e32bc
View Raw JSON Data
{
  "trx_id": "605c9f22f377f499b9d02b2836ce5376934e32bc",
  "block": 16285245,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-10-13T05:12:27",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "patb",
      "vesting_shares": "29832.874269 VESTS"
    }
  ]
}
2017/10/06 14:44:30
voterpatb
authordjrazor
permlinkre-patb-the-billion-dollar-iot-device-discovery-opportunity-20171006t035331011z
weight10000 (100.00%)
Transaction InfoBlock #16095177/Trx 60453d72ea25aeed31607d6e12102d8b6e2bc9c3
View Raw JSON Data
{
  "trx_id": "60453d72ea25aeed31607d6e12102d8b6e2bc9c3",
  "block": 16095177,
  "trx_in_block": 10,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-10-06T14:44:30",
  "op": [
    "vote",
    {
      "voter": "patb",
      "author": "djrazor",
      "permlink": "re-patb-the-billion-dollar-iot-device-discovery-opportunity-20171006t035331011z",
      "weight": 10000
    }
  ]
}
2017/10/06 03:53:39
parent authorpatb
parent permlinkthe-billion-dollar-iot-device-discovery-opportunity
authordjrazor
permlinkre-patb-the-billion-dollar-iot-device-discovery-opportunity-20171006t035331011z
title
bodyThank you for the extremely informative post. It's a shame that in the rush to create new devices and be first to market with them that security is almost a back burner issue for so many companies
json metadata{"tags":["iot"],"app":"steemit/0.1"}
Transaction InfoBlock #16082165/Trx 76843365d3d61cd74a56031ac369a5fec1863d91
View Raw JSON Data
{
  "trx_id": "76843365d3d61cd74a56031ac369a5fec1863d91",
  "block": 16082165,
  "trx_in_block": 18,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-10-06T03:53:39",
  "op": [
    "comment",
    {
      "parent_author": "patb",
      "parent_permlink": "the-billion-dollar-iot-device-discovery-opportunity",
      "author": "djrazor",
      "permlink": "re-patb-the-billion-dollar-iot-device-discovery-opportunity-20171006t035331011z",
      "title": "",
      "body": "Thank you for the extremely informative post.\n\nIt's a shame that in the rush to create new devices and be first to market with them that security is almost a back burner issue for so many companies",
      "json_metadata": "{\"tags\":[\"iot\"],\"app\":\"steemit/0.1\"}"
    }
  ]
}
2017/10/06 03:49:51
voterdjrazor
authorpatb
permlinkthe-billion-dollar-iot-device-discovery-opportunity
weight10000 (100.00%)
Transaction InfoBlock #16082089/Trx 0fee81a82039be8622ac59aa445f5bc51eabc6a9
View Raw JSON Data
{
  "trx_id": "0fee81a82039be8622ac59aa445f5bc51eabc6a9",
  "block": 16082089,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-10-06T03:49:51",
  "op": [
    "vote",
    {
      "voter": "djrazor",
      "author": "patb",
      "permlink": "the-billion-dollar-iot-device-discovery-opportunity",
      "weight": 10000
    }
  ]
}
2017/10/06 03:27:33
voterammadaziz84
authorpatb
permlinkthe-billion-dollar-iot-device-discovery-opportunity
weight10000 (100.00%)
Transaction InfoBlock #16081645/Trx 97c6c337e78e42f5e36b7d5b682680136c5c08c5
View Raw JSON Data
{
  "trx_id": "97c6c337e78e42f5e36b7d5b682680136c5c08c5",
  "block": 16081645,
  "trx_in_block": 12,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-10-06T03:27:33",
  "op": [
    "vote",
    {
      "voter": "ammadaziz84",
      "author": "patb",
      "permlink": "the-billion-dollar-iot-device-discovery-opportunity",
      "weight": 10000
    }
  ]
}
2017/10/06 03:26:57
parent authorpatb
parent permlinkthe-billion-dollar-iot-device-discovery-opportunity
authorcheetah
permlinkcheetah-re-patbthe-billion-dollar-iot-device-discovery-opportunity
title
bodyHi! I am a robot. I just upvoted you! I found similar content that readers might be interested in: https://www.iotforall.com/blueborne-iot-device-discovery-opportunity/
json metadata
Transaction InfoBlock #16081633/Trx 657ffce1759982c43dbed33553f33a135f237a47
View Raw JSON Data
{
  "trx_id": "657ffce1759982c43dbed33553f33a135f237a47",
  "block": 16081633,
  "trx_in_block": 20,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-10-06T03:26:57",
  "op": [
    "comment",
    {
      "parent_author": "patb",
      "parent_permlink": "the-billion-dollar-iot-device-discovery-opportunity",
      "author": "cheetah",
      "permlink": "cheetah-re-patbthe-billion-dollar-iot-device-discovery-opportunity",
      "title": "",
      "body": "Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in:\nhttps://www.iotforall.com/blueborne-iot-device-discovery-opportunity/",
      "json_metadata": ""
    }
  ]
}
2017/10/06 03:26:54
votercheetah
authorpatb
permlinkthe-billion-dollar-iot-device-discovery-opportunity
weight50 (0.50%)
Transaction InfoBlock #16081632/Trx bb4cfebf019dd0928af413d1cf984dd1dcea33b7
View Raw JSON Data
{
  "trx_id": "bb4cfebf019dd0928af413d1cf984dd1dcea33b7",
  "block": 16081632,
  "trx_in_block": 19,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-10-06T03:26:54",
  "op": [
    "vote",
    {
      "voter": "cheetah",
      "author": "patb",
      "permlink": "the-billion-dollar-iot-device-discovery-opportunity",
      "weight": 50
    }
  ]
}
2017/10/06 03:26:30
parent author
parent permlinkiot
authorpatb
permlinkthe-billion-dollar-iot-device-discovery-opportunity
titleThe Billion Dollar IoT Device Discovery Opportunity
bodyA few thoughts on last month's Blueborne exploit, which should raise eyebrows for anyone deploying Bluetooth in the IoT. Blueborne looks like a nightmare for anyone deploying Bluetooth in the IoT. Here’s the description from the firm that uncovered the exploit: *BlueBorne is an attack vector by which hackers can leverage Bluetooth connections to penetrate and take complete control over targeted devices. BlueBorne affects ordinary computers, mobile phones, and the expanding realm of IoT devices. The attack does not require the targeted device to be paired to the attacker’s device, or even to be set on discoverable mode. Armis Labs has identified eight zero-day vulnerabilities so far, which indicate the existence and potential of the attack vector.* But then there’s this: *Armis believes many more vulnerabilities await discovery in the various platforms using Bluetooth. These vulnerabilities are fully operational, and can be successfully exploited, as demonstrated in our research. The BlueBorne attack vector can be used to conduct a large range of offenses, including remote code execution as well as Man-in-The-Middle attacks.”* For the full shock value of this exploit, here’s a short video by the firm that made the discovery that explains the risk: https://youtu.be/LLNtZKpL0P8 2. Bluetooth radios are notoriously easy to discover and a large part of Blueborne appears based on this fact: *The BlueBorne attack vector has several stages. First, the attacker locates active Bluetooth connections around him or her. Devices can be identified even if they are not set to “discoverable” mode. Next, the attacker obtains the device’s MAC address, which is a unique identifier of that specific device. By probing the device, the attacker can determine which operating system his victim is using, and adjust his exploit accordingly. The attacker will then exploit a vulnerability in the implementation of the Bluetooth protocol in the relevant platform.* 3. Many Bluetooth devices are — and you are not going to believe this — not patchable. *However, Parker said that up to 40 percent of the 5.3 billion impacted devices probably would not be patchable — mainly because they are IoT devices, like smart refrigerators, that cannot be easily updated. Right now, Armis said that users could disable Bluetooth to protect their connected devices while waiting for the patch.* 4. If there is any good news for Bluetooth developers, it is small, embeded devices do not appear — for now — to be a primary target for Blueborn, but rather higher-powered gateways running Linux, Android, Windows, or iOS which in turn connect to low power devices. *The vulnerabilities disclosed by Armis affect all devices running on Android, Linux, Windows, and pre-version 10 of iOS operating systems, regardless of the Bluetooth version in use. This means almost every computer, mobile device, smart TV or other IoT device running on one of these operating systems is endangered by at least one of the eight vulnerabilities.* 5. I’ve written about device discovery before (https://medium.com/the-startup-magazine-collection/a-simple-proposal-to-improve-security-for-the-internet-of-things-4fcc0663f70e) and the principles still apply: low power IoT endpoints should operate in a “stealthy” mode unless there is a reason to make noise. It saves power, reduces network congestion, and makes discovering your IoT device much, much harder. I didn’t say “impossible to discover”, but like prey in the jungle wanting to avoid alerting a predator, part of minimizing your chances of being discovered is just to keep quiet. Older protocols — including Bluetooth take an opposite tack: they never stop talking and are always discoverable. Even when you tell your Bluetooth radio to go into non-discovery mode. Bluetooth is not alone in this ease of discovery. WiFi and IEEE 802.15.4xx are just two examples of stacks (or semi-stacks) that weren’t conceived with the modern IoT in mind. Even more recent attempts like LoRaWAN were architected without thinking this through. In the world of IoT wireless protocol development, device discovery seems to (usually) be the job given the guys who weren’t smart enough to work on documentation. But if we are just seeing the beginning of hacks like Blueborne — as the author of the vulnerabilty suggests — the solution to limiting IoT device discovery is a billion dollar opportunity.
json metadata{"tags":["iot","bluetooth","security"],"image":["https://img.youtube.com/vi/LLNtZKpL0P8/0.jpg"],"links":["https://youtu.be/LLNtZKpL0P8","https://medium.com/the-startup-magazine-collection/a-simple-proposal-to-improve-security-for-the-internet-of-things-4fcc0663f70e"],"app":"steemit/0.1","format":"markdown"}
Transaction InfoBlock #16081624/Trx 4a8d3371103ea2f628dbe3d160a86212849fbd0f
View Raw JSON Data
{
  "trx_id": "4a8d3371103ea2f628dbe3d160a86212849fbd0f",
  "block": 16081624,
  "trx_in_block": 3,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-10-06T03:26:30",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "iot",
      "author": "patb",
      "permlink": "the-billion-dollar-iot-device-discovery-opportunity",
      "title": "The Billion Dollar IoT Device Discovery Opportunity",
      "body": "A few thoughts on last month's Blueborne exploit, which should raise eyebrows for anyone deploying Bluetooth in the IoT.\nBlueborne looks like a nightmare for anyone deploying Bluetooth in the IoT. Here’s the description from the firm that uncovered the exploit:\n\n*BlueBorne is an attack vector by which hackers can leverage Bluetooth connections to penetrate and take complete control over targeted devices. BlueBorne affects ordinary computers, mobile phones, and the expanding realm of IoT devices. The attack does not require the targeted device to be paired to the attacker’s device, or even to be set on discoverable mode. Armis Labs has identified eight zero-day vulnerabilities so far, which indicate the existence and potential of the attack vector.*\n\nBut then there’s this:\n\n*Armis believes many more vulnerabilities await discovery in the various platforms using Bluetooth. These vulnerabilities are fully operational, and can be successfully exploited, as demonstrated in our research. The BlueBorne attack vector can be used to conduct a large range of offenses, including remote code execution as well as Man-in-The-Middle attacks.”*\n\nFor the full shock value of this exploit, here’s a short video by the firm that made the discovery that explains the risk:\n\nhttps://youtu.be/LLNtZKpL0P8\n\n2. Bluetooth radios are notoriously easy to discover and a large part of Blueborne appears based on this fact:\n\n*The BlueBorne attack vector has several stages. First, the attacker locates active Bluetooth connections around him or her. Devices can be identified even if they are not set to “discoverable” mode. Next, the attacker obtains the device’s MAC address, which is a unique identifier of that specific device. By probing the device, the attacker can determine which operating system his victim is using, and adjust his exploit accordingly. The attacker will then exploit a vulnerability in the implementation of the Bluetooth protocol in the relevant platform.*\n\n3. Many Bluetooth devices are — and you are not going to believe this — not patchable.\n\n*However, Parker said that up to 40 percent of the 5.3 billion impacted devices probably would not be patchable — mainly because they are IoT devices, like smart refrigerators, that cannot be easily updated. Right now, Armis said that users could disable Bluetooth to protect their connected devices while waiting for the patch.*\n\n4. If there is any good news for Bluetooth developers, it is small, embeded devices do not appear — for now — to be a primary target for Blueborn, but rather higher-powered gateways running Linux, Android, Windows, or iOS which in turn connect to low power devices.\n\n*The vulnerabilities disclosed by Armis affect all devices running on Android, Linux, Windows, and pre-version 10 of iOS operating systems, regardless of the Bluetooth version in use. This means almost every computer, mobile device, smart TV or other IoT device running on one of these operating systems is endangered by at least one of the eight vulnerabilities.*\n\n5. I’ve written about device discovery before (https://medium.com/the-startup-magazine-collection/a-simple-proposal-to-improve-security-for-the-internet-of-things-4fcc0663f70e) and the principles still apply: low power IoT endpoints should operate in a “stealthy” mode unless there is a reason to make noise. It saves power, reduces network congestion, and makes discovering your IoT device much, much harder. I didn’t say “impossible to discover”, but like prey in the jungle wanting to avoid alerting a predator, part of minimizing your chances of being discovered is just to keep quiet. Older protocols — including Bluetooth take an opposite tack: they never stop talking and are always discoverable. Even when you tell your Bluetooth radio to go into non-discovery mode.\n\nBluetooth is not alone in this ease of discovery. WiFi and IEEE 802.15.4xx are just two examples of stacks (or semi-stacks) that weren’t conceived with the modern IoT in mind. Even more recent attempts like LoRaWAN were architected without thinking this through.\n\nIn the world of IoT wireless protocol development, device discovery seems to (usually) be the job given the guys who weren’t smart enough to work on documentation. But if we are just seeing the beginning of hacks like Blueborne — as the author of the vulnerabilty suggests — the solution to limiting IoT device discovery is a billion dollar opportunity.",
      "json_metadata": "{\"tags\":[\"iot\",\"bluetooth\",\"security\"],\"image\":[\"https://img.youtube.com/vi/LLNtZKpL0P8/0.jpg\"],\"links\":[\"https://youtu.be/LLNtZKpL0P8\",\"https://medium.com/the-startup-magazine-collection/a-simple-proposal-to-improve-security-for-the-internet-of-things-4fcc0663f70e\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}
steemcreated a new account: @patb
2017/10/06 03:03:18
fee0.500 STEEM
delegation57000.000000 VESTS
creatorsteem
new account namepatb
owner{"weight_threshold":1,"account_auths":[],"key_auths":[["STM7SRE4yrL9kkx4tCpYGz8ophgYsdj8KhSbQkppQ9pByyRXYfuKK",1]]}
active{"weight_threshold":1,"account_auths":[],"key_auths":[["STM7LukJz84VpEg56LDwbYbLrZu5ULHcUPkS27LmgCDUu4HpZdwYZ",1]]}
posting{"weight_threshold":1,"account_auths":[],"key_auths":[["STM5hckhcMayNSm3qsiRu8UhoY7mFbhduq7HrG8FUw6Sjns7RsxbU",1]]}
memo keySTM7ii7hrqxssbJoThpg8ap8Zg4oCKhdp7ZyD8C9EguJBpRn4wbQ6
json metadata
extensions[]
Transaction InfoBlock #16081161/Trx b2858907373129b77e25e03aa30db65521ff52ae
View Raw JSON Data
{
  "trx_id": "b2858907373129b77e25e03aa30db65521ff52ae",
  "block": 16081161,
  "trx_in_block": 37,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-10-06T03:03:18",
  "op": [
    "account_create_with_delegation",
    {
      "fee": "0.500 STEEM",
      "delegation": "57000.000000 VESTS",
      "creator": "steem",
      "new_account_name": "patb",
      "owner": {
        "weight_threshold": 1,
        "account_auths": [],
        "key_auths": [
          [
            "STM7SRE4yrL9kkx4tCpYGz8ophgYsdj8KhSbQkppQ9pByyRXYfuKK",
            1
          ]
        ]
      },
      "active": {
        "weight_threshold": 1,
        "account_auths": [],
        "key_auths": [
          [
            "STM7LukJz84VpEg56LDwbYbLrZu5ULHcUPkS27LmgCDUu4HpZdwYZ",
            1
          ]
        ]
      },
      "posting": {
        "weight_threshold": 1,
        "account_auths": [],
        "key_auths": [
          [
            "STM5hckhcMayNSm3qsiRu8UhoY7mFbhduq7HrG8FUw6Sjns7RsxbU",
            1
          ]
        ]
      },
      "memo_key": "STM7ii7hrqxssbJoThpg8ap8Zg4oCKhdp7ZyD8C9EguJBpRn4wbQ6",
      "json_metadata": "",
      "extensions": []
    }
  ]
}

Account Metadata

POSTING JSON METADATA
None
JSON METADATA
None
{
  "posting_json_metadata": {},
  "json_metadata": {}
}

Auth Keys

Owner
Single Signature
Public Keys
STM7SRE4yrL9kkx4tCpYGz8ophgYsdj8KhSbQkppQ9pByyRXYfuKK1/1
Active
Single Signature
Public Keys
STM7LukJz84VpEg56LDwbYbLrZu5ULHcUPkS27LmgCDUu4HpZdwYZ1/1
Posting
Single Signature
Public Keys
STM5hckhcMayNSm3qsiRu8UhoY7mFbhduq7HrG8FUw6Sjns7RsxbU1/1
Memo
STM7ii7hrqxssbJoThpg8ap8Zg4oCKhdp7ZyD8C9EguJBpRn4wbQ6
{
  "owner": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM7SRE4yrL9kkx4tCpYGz8ophgYsdj8KhSbQkppQ9pByyRXYfuKK",
        1
      ]
    ]
  },
  "active": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM7LukJz84VpEg56LDwbYbLrZu5ULHcUPkS27LmgCDUu4HpZdwYZ",
        1
      ]
    ]
  },
  "posting": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM5hckhcMayNSm3qsiRu8UhoY7mFbhduq7HrG8FUw6Sjns7RsxbU",
        1
      ]
    ]
  },
  "memo": "STM7ii7hrqxssbJoThpg8ap8Zg4oCKhdp7ZyD8C9EguJBpRn4wbQ6"
}

Witness Votes

0 / 30
No active witness votes.
[]