VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS0.00%
Net Worth
0.715USD
STEEM
0.000STEEM
SBD
0.000SBD
Own SP
12.334SP
Detailed Balance
| STEEM | ||
| balance | 0.000STEEM | STEEM |
| market_balance | 0.000STEEM | STEEM |
| savings_balance | 0.000STEEM | STEEM |
| reward_steem_balance | 0.000STEEM | STEEM |
| STEEM POWER | ||
| Own SP | 12.334SP | SP |
| Delegated Out | 0.000SP | SP |
| Delegation In | 0.000SP | SP |
| Effective Power | 12.334SP | SP |
| Reward SP (pending) | 0.000SP | SP |
| SBD | ||
| sbd_balance | 0.000SBD | SBD |
| sbd_conversions | 0.000SBD | SBD |
| sbd_market_balance | 0.000SBD | SBD |
| savings_sbd_balance | 0.000SBD | SBD |
| reward_sbd_balance | 0.000SBD | SBD |
{
"balance": "0.000 STEEM",
"savings_balance": "0.000 STEEM",
"reward_steem_balance": "0.000 STEEM",
"vesting_shares": "20060.214340 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "0.000000 VESTS",
"sbd_balance": "0.000 SBD",
"savings_sbd_balance": "0.000 SBD",
"reward_sbd_balance": "0.000 SBD",
"conversions": []
}Account Info
| name | thnass |
| id | 16682 |
| rank | 110,572 |
| reputation | 381162871 |
| created | 2016-07-11T11:35:42 |
| recovery_account | steem |
| proxy | None |
| post_count | 4 |
| comment_count | 0 |
| lifetime_vote_count | 0 |
| witnesses_voted_for | 0 |
| last_post | 2016-11-24T11:48:09 |
| last_root_post | 2016-09-26T18:29:06 |
| last_vote_time | 2019-11-13T12:05:33 |
| proxied_vsf_votes | 0, 0, 0, 0 |
| can_vote | 1 |
| voting_power | 9,249 |
| delayed_votes | 0 |
| balance | 0.000 STEEM |
| savings_balance | 0.000 STEEM |
| sbd_balance | 0.000 SBD |
| savings_sbd_balance | 0.000 SBD |
| vesting_shares | 20060.214340 VESTS |
| delegated_vesting_shares | 0.000000 VESTS |
| received_vesting_shares | 0.000000 VESTS |
| reward_vesting_balance | 0.000000 VESTS |
| vesting_balance | 0.000 STEEM |
| vesting_withdraw_rate | 0.000000 VESTS |
| next_vesting_withdrawal | 1969-12-31T23:59:59 |
| withdrawn | 27941050944 |
| to_withdraw | 27941050944 |
| withdraw_routes | 0 |
| savings_withdraw_requests | 0 |
| last_account_recovery | 1970-01-01T00:00:00 |
| reset_account | null |
| last_owner_update | 1970-01-01T00:00:00 |
| last_account_update | 2018-10-23T21:33:21 |
| mined | No |
| sbd_seconds | 0 |
| sbd_last_interest_payment | 1970-01-01T00:00:00 |
| savings_sbd_last_interest_payment | 1970-01-01T00:00:00 |
{
"active": {
"account_auths": [],
"key_auths": [
[
"STM7nmtoqKMEUWBuxtuWWU3DFUyeUGGGMEqL1PERzdW4G4Rkq6hgx",
1
]
],
"weight_threshold": 1
},
"balance": "0.000 STEEM",
"can_vote": true,
"comment_count": 0,
"created": "2016-07-11T11:35:42",
"curation_rewards": 0,
"delegated_vesting_shares": "0.000000 VESTS",
"downvote_manabar": {
"current_mana": "5015053585",
"last_update_time": 1573646733
},
"guest_bloggers": [],
"id": 16682,
"json_metadata": "",
"last_account_recovery": "1970-01-01T00:00:00",
"last_account_update": "2018-10-23T21:33:21",
"last_owner_update": "1970-01-01T00:00:00",
"last_post": "2016-11-24T11:48:09",
"last_root_post": "2016-09-26T18:29:06",
"last_vote_time": "2019-11-13T12:05:33",
"lifetime_vote_count": 0,
"market_history": [],
"memo_key": "STM64WU3dtcfVXsQUVpRyonUifkbDwSENzkBkb4Y6AXBWgU8eMTgC",
"mined": false,
"name": "thnass",
"next_vesting_withdrawal": "1969-12-31T23:59:59",
"other_history": [],
"owner": {
"account_auths": [],
"key_auths": [
[
"STM5vMwCGwkSfA9Mjq86oGcrHFaLe5yEGjrLCrxe2xvNAec5UsUqU",
1
]
],
"weight_threshold": 1
},
"pending_claimed_accounts": 0,
"post_bandwidth": 19749,
"post_count": 4,
"post_history": [],
"posting": {
"account_auths": [
[
"dtube.app",
1
]
],
"key_auths": [
[
"STM6PosxLZorrCrRKvHQZ178jfDUHxkgTzSq3mnLYcwgf1UdkWsEi",
1
]
],
"weight_threshold": 1
},
"posting_json_metadata": "",
"posting_rewards": 0,
"proxied_vsf_votes": [
0,
0,
0,
0
],
"proxy": "",
"received_vesting_shares": "0.000000 VESTS",
"recovery_account": "steem",
"reputation": 381162871,
"reset_account": "null",
"reward_sbd_balance": "0.000 SBD",
"reward_steem_balance": "0.000 STEEM",
"reward_vesting_balance": "0.000000 VESTS",
"reward_vesting_steem": "0.000 STEEM",
"savings_balance": "0.000 STEEM",
"savings_sbd_balance": "0.000 SBD",
"savings_sbd_last_interest_payment": "1970-01-01T00:00:00",
"savings_sbd_seconds": "0",
"savings_sbd_seconds_last_update": "1970-01-01T00:00:00",
"savings_withdraw_requests": 0,
"sbd_balance": "0.000 SBD",
"sbd_last_interest_payment": "1970-01-01T00:00:00",
"sbd_seconds": "0",
"sbd_seconds_last_update": "1970-01-01T00:00:00",
"tags_usage": [],
"to_withdraw": "27941050944",
"transfer_history": [],
"vesting_balance": "0.000 STEEM",
"vesting_shares": "20060.214340 VESTS",
"vesting_withdraw_rate": "0.000000 VESTS",
"vote_history": [],
"voting_manabar": {
"current_mana": "18555092635",
"last_update_time": 1573646733
},
"voting_power": 9249,
"withdraw_routes": 0,
"withdrawn": "27941050944",
"witness_votes": [],
"witnesses_voted_for": 0,
"rank": 110572
}Withdraw Routes
| Incoming | Outgoing |
|---|---|
Empty | Empty |
{
"incoming": [],
"outgoing": []
}From Date
To Date
2023/11/18 11:03:27
2023/11/18 11:03:27
| author | southcide |
| body | Good day. The modern world is all about connectivity, and T-Mobile plays an important role. With its robust network infrastructure and commitment to expanding coverage, T-Mobile has transformed the way people communicate, connect and access information. The quality of their services is excellent, and the support service, which can be contacted by [tmobile phone number](https://tmobile.pissedconsumer.com/customer-service.html) improves the overall experience of using the company’s services, and therefore the number of their clients is constantly increasing. |
| json metadata | {"links":["https://tmobile.pissedconsumer.com/customer-service.html"],"app":"steemit/0.2"} |
| parent author | thnass |
| parent permlink | connectivity-of-the-internet-of-things |
| permlink | s4bg1q |
| title | |
| Transaction Info | Block #79986591/Trx 4429daca5a34d75063ba5b3fbf13257c7428313f |
View Raw JSON Data
{
"block": 79986591,
"op": [
"comment",
{
"author": "southcide",
"body": "Good day. The modern world is all about connectivity, and T-Mobile plays an important role. With its robust network infrastructure and commitment to expanding coverage, T-Mobile has transformed the way people communicate, connect and access information. The quality of their services is excellent, and the support service, which can be contacted by [tmobile phone number](https://tmobile.pissedconsumer.com/customer-service.html) improves the overall experience of using the company’s services, and therefore the number of their clients is constantly increasing.",
"json_metadata": "{\"links\":[\"https://tmobile.pissedconsumer.com/customer-service.html\"],\"app\":\"steemit/0.2\"}",
"parent_author": "thnass",
"parent_permlink": "connectivity-of-the-internet-of-things",
"permlink": "s4bg1q",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2023-11-18T11:03:27",
"trx_id": "4429daca5a34d75063ba5b3fbf13257c7428313f",
"trx_in_block": 3,
"virtual_op": 0
}thnassupvoted (100.00%) @kingscrown / coinex-chain-mainnet-launched2019/11/13 12:05:33
thnassupvoted (100.00%) @kingscrown / coinex-chain-mainnet-launched
2019/11/13 12:05:33
| author | kingscrown |
| permlink | coinex-chain-mainnet-launched |
| voter | thnass |
| weight | 10000 (100.00%) |
| Transaction Info | Block #38138230/Trx e51a0a29371cb2f983d4e400d44169697f19aa37 |
View Raw JSON Data
{
"block": 38138230,
"op": [
"vote",
{
"author": "kingscrown",
"permlink": "coinex-chain-mainnet-launched",
"voter": "thnass",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2019-11-13T12:05:33",
"trx_id": "e51a0a29371cb2f983d4e400d44169697f19aa37",
"trx_in_block": 24,
"virtual_op": 0
}thnassupvoted (100.00%) @cadawg / a-chat-app-truly-on-steem2019/11/13 12:04:57
thnassupvoted (100.00%) @cadawg / a-chat-app-truly-on-steem
2019/11/13 12:04:57
| author | cadawg |
| permlink | a-chat-app-truly-on-steem |
| voter | thnass |
| weight | 10000 (100.00%) |
| Transaction Info | Block #38138218/Trx f550feca9fa12b5fa0fab8a87acb93e8d072bc2b |
View Raw JSON Data
{
"block": 38138218,
"op": [
"vote",
{
"author": "cadawg",
"permlink": "a-chat-app-truly-on-steem",
"voter": "thnass",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2019-11-13T12:04:57",
"trx_id": "f550feca9fa12b5fa0fab8a87acb93e8d072bc2b",
"trx_in_block": 32,
"virtual_op": 0
}2019/11/13 11:46:27
2019/11/13 11:46:27
| author | anomadsoul |
| permlink | what-the-future-holds-for-steem-or-an-honest-non-shilly-social-analysis-after-steem-fest |
| voter | thnass |
| weight | 10000 (100.00%) |
| Transaction Info | Block #38137849/Trx 4d6b9dac73053f6fbfe3a72a413a857e63557c43 |
View Raw JSON Data
{
"block": 38137849,
"op": [
"vote",
{
"author": "anomadsoul",
"permlink": "what-the-future-holds-for-steem-or-an-honest-non-shilly-social-analysis-after-steem-fest",
"voter": "thnass",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2019-11-13T11:46:27",
"trx_id": "4d6b9dac73053f6fbfe3a72a413a857e63557c43",
"trx_in_block": 3,
"virtual_op": 0
}thnassupvoted (100.00%) @roelandp / steemfest-4-memories-from-a-minivan2019/11/13 11:46:03
thnassupvoted (100.00%) @roelandp / steemfest-4-memories-from-a-minivan
2019/11/13 11:46:03
| author | roelandp |
| permlink | steemfest-4-memories-from-a-minivan |
| voter | thnass |
| weight | 10000 (100.00%) |
| Transaction Info | Block #38137841/Trx 1afcbc799786d39426d87a51b742ddfccff95f79 |
View Raw JSON Data
{
"block": 38137841,
"op": [
"vote",
{
"author": "roelandp",
"permlink": "steemfest-4-memories-from-a-minivan",
"voter": "thnass",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2019-11-13T11:46:03",
"trx_id": "1afcbc799786d39426d87a51b742ddfccff95f79",
"trx_in_block": 5,
"virtual_op": 0
}thnasssent 13.962 STEEM to @deepcrypto8- "106355366"2019/11/13 11:39:48
thnasssent 13.962 STEEM to @deepcrypto8- "106355366"
2019/11/13 11:39:48
| amount | 13.962 STEEM |
| from | thnass |
| memo | 106355366 |
| to | deepcrypto8 |
| Transaction Info | Block #38137717/Trx 7c820d012eabfefc4e022ca7ecba1f5164fcabe9 |
View Raw JSON Data
{
"block": 38137717,
"op": [
"transfer",
{
"amount": "13.962 STEEM",
"from": "thnass",
"memo": "106355366",
"to": "deepcrypto8"
}
],
"op_in_trx": 0,
"timestamp": "2019-11-13T11:39:48",
"trx_id": "7c820d012eabfefc4e022ca7ecba1f5164fcabe9",
"trx_in_block": 33,
"virtual_op": 0
}2019/11/05 22:10:33
2019/11/05 22:10:33
| id | follow |
| json | ["follow",{"follower":"thnass","following":"co-dex","what":["blog"]}] |
| required auths | [] |
| required posting auths | ["thnass"] |
| Transaction Info | Block #37920336/Trx d198bcd7cd95ed23265b64d53306c437b2d52807 |
View Raw JSON Data
{
"block": 37920336,
"op": [
"custom_json",
{
"id": "follow",
"json": "[\"follow\",{\"follower\":\"thnass\",\"following\":\"co-dex\",\"what\":[\"blog\"]}]",
"required_auths": [],
"required_posting_auths": [
"thnass"
]
}
],
"op_in_trx": 0,
"timestamp": "2019-11-05T22:10:33",
"trx_id": "d198bcd7cd95ed23265b64d53306c437b2d52807",
"trx_in_block": 23,
"virtual_op": 0
}2019/07/11 13:08:42
2019/07/11 13:08:42
| author | steemitboard |
| body | Congratulations @thnass! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@thnass/birthday3.png</td><td>Happy Birthday! - You are on the Steem blockchain for 3 years!</td></tr></table> <sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@thnass) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=thnass)_</sub> ###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| parent author | thnass |
| parent permlink | connectivity-of-the-internet-of-things-pt2 |
| permlink | steemitboard-notify-thnass-20190711t130841000z |
| title | |
| Transaction Info | Block #34569302/Trx 959906e7547e9f02d72da577db1aba8200f6c932 |
View Raw JSON Data
{
"block": 34569302,
"op": [
"comment",
{
"author": "steemitboard",
"body": "Congratulations @thnass! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@thnass/birthday3.png</td><td>Happy Birthday! - You are on the Steem blockchain for 3 years!</td></tr></table>\n\n<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@thnass) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=thnass)_</sub>\n\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}",
"parent_author": "thnass",
"parent_permlink": "connectivity-of-the-internet-of-things-pt2",
"permlink": "steemitboard-notify-thnass-20190711t130841000z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2019-07-11T13:08:42",
"trx_id": "959906e7547e9f02d72da577db1aba8200f6c932",
"trx_in_block": 11,
"virtual_op": 0
}thnassreceived 0.000 STEEM from power down installment (0.000 SP)2019/05/15 00:40:00
thnassreceived 0.000 STEEM from power down installment (0.000 SP)
2019/05/15 00:40:00
| deposited | 0.000 STEEM |
| from account | thnass |
| to account | thnass |
| withdrawn | 0.000001 VESTS |
| Transaction Info | Block #32914762/Virtual Operation #4 |
View Raw JSON Data
{
"block": 32914762,
"op": [
"fill_vesting_withdraw",
{
"deposited": "0.000 STEEM",
"from_account": "thnass",
"to_account": "thnass",
"withdrawn": "0.000001 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2019-05-15T00:40:00",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": 4
}thnassreceived 1.077 STEEM from power down installment (1.321 SP)2019/05/08 00:40:00
thnassreceived 1.077 STEEM from power down installment (1.321 SP)
2019/05/08 00:40:00
| deposited | 1.077 STEEM |
| from account | thnass |
| to account | thnass |
| withdrawn | 2149.311611 VESTS |
| Transaction Info | Block #32713250/Virtual Operation #3 |
View Raw JSON Data
{
"block": 32713250,
"op": [
"fill_vesting_withdraw",
{
"deposited": "1.077 STEEM",
"from_account": "thnass",
"to_account": "thnass",
"withdrawn": "2149.311611 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2019-05-08T00:40:00",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": 3
}thnassreceived 1.076 STEEM from power down installment (1.321 SP)2019/05/01 00:40:00
thnassreceived 1.076 STEEM from power down installment (1.321 SP)
2019/05/01 00:40:00
| deposited | 1.076 STEEM |
| from account | thnass |
| to account | thnass |
| withdrawn | 2149.311611 VESTS |
| Transaction Info | Block #32511784/Virtual Operation #4 |
View Raw JSON Data
{
"block": 32511784,
"op": [
"fill_vesting_withdraw",
{
"deposited": "1.076 STEEM",
"from_account": "thnass",
"to_account": "thnass",
"withdrawn": "2149.311611 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2019-05-01T00:40:00",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": 4
}thnassreceived 1.076 STEEM from power down installment (1.321 SP)2019/04/24 00:40:00
thnassreceived 1.076 STEEM from power down installment (1.321 SP)
2019/04/24 00:40:00
| deposited | 1.076 STEEM |
| from account | thnass |
| to account | thnass |
| withdrawn | 2149.311611 VESTS |
| Transaction Info | Block #32310297/Virtual Operation #4 |
View Raw JSON Data
{
"block": 32310297,
"op": [
"fill_vesting_withdraw",
{
"deposited": "1.076 STEEM",
"from_account": "thnass",
"to_account": "thnass",
"withdrawn": "2149.311611 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2019-04-24T00:40:00",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": 4
}thnassreceived 1.075 STEEM from power down installment (1.321 SP)2019/04/17 00:40:00
thnassreceived 1.075 STEEM from power down installment (1.321 SP)
2019/04/17 00:40:00
| deposited | 1.075 STEEM |
| from account | thnass |
| to account | thnass |
| withdrawn | 2149.311611 VESTS |
| Transaction Info | Block #32108807/Virtual Operation #3 |
View Raw JSON Data
{
"block": 32108807,
"op": [
"fill_vesting_withdraw",
{
"deposited": "1.075 STEEM",
"from_account": "thnass",
"to_account": "thnass",
"withdrawn": "2149.311611 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2019-04-17T00:40:00",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": 3
}thnassreceived 1.075 STEEM from power down installment (1.321 SP)2019/04/10 00:40:00
thnassreceived 1.075 STEEM from power down installment (1.321 SP)
2019/04/10 00:40:00
| deposited | 1.075 STEEM |
| from account | thnass |
| to account | thnass |
| withdrawn | 2149.311611 VESTS |
| Transaction Info | Block #31908546/Virtual Operation #4 |
View Raw JSON Data
{
"block": 31908546,
"op": [
"fill_vesting_withdraw",
{
"deposited": "1.075 STEEM",
"from_account": "thnass",
"to_account": "thnass",
"withdrawn": "2149.311611 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2019-04-10T00:40:00",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": 4
}thnassreceived 1.074 STEEM from power down installment (1.321 SP)2019/04/03 00:40:00
thnassreceived 1.074 STEEM from power down installment (1.321 SP)
2019/04/03 00:40:00
| deposited | 1.074 STEEM |
| from account | thnass |
| to account | thnass |
| withdrawn | 2149.311611 VESTS |
| Transaction Info | Block #31707428/Virtual Operation #17 |
View Raw JSON Data
{
"block": 31707428,
"op": [
"fill_vesting_withdraw",
{
"deposited": "1.074 STEEM",
"from_account": "thnass",
"to_account": "thnass",
"withdrawn": "2149.311611 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2019-04-03T00:40:00",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": 17
}thnassreceived 1.074 STEEM from power down installment (1.321 SP)2019/03/27 00:40:00
thnassreceived 1.074 STEEM from power down installment (1.321 SP)
2019/03/27 00:40:00
| deposited | 1.074 STEEM |
| from account | thnass |
| to account | thnass |
| withdrawn | 2149.311611 VESTS |
| Transaction Info | Block #31505953/Virtual Operation #4 |
View Raw JSON Data
{
"block": 31505953,
"op": [
"fill_vesting_withdraw",
{
"deposited": "1.074 STEEM",
"from_account": "thnass",
"to_account": "thnass",
"withdrawn": "2149.311611 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2019-03-27T00:40:00",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": 4
}thnassreceived 1.074 STEEM from power down installment (1.321 SP)2019/03/20 00:40:00
thnassreceived 1.074 STEEM from power down installment (1.321 SP)
2019/03/20 00:40:00
| deposited | 1.074 STEEM |
| from account | thnass |
| to account | thnass |
| withdrawn | 2149.311611 VESTS |
| Transaction Info | Block #31304467/Virtual Operation #6 |
View Raw JSON Data
{
"block": 31304467,
"op": [
"fill_vesting_withdraw",
{
"deposited": "1.074 STEEM",
"from_account": "thnass",
"to_account": "thnass",
"withdrawn": "2149.311611 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2019-03-20T00:40:00",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": 6
}thnassreceived 1.073 STEEM from power down installment (1.321 SP)2019/03/13 00:40:00
thnassreceived 1.073 STEEM from power down installment (1.321 SP)
2019/03/13 00:40:00
| deposited | 1.073 STEEM |
| from account | thnass |
| to account | thnass |
| withdrawn | 2149.311611 VESTS |
| Transaction Info | Block #31103030/Virtual Operation #3 |
View Raw JSON Data
{
"block": 31103030,
"op": [
"fill_vesting_withdraw",
{
"deposited": "1.073 STEEM",
"from_account": "thnass",
"to_account": "thnass",
"withdrawn": "2149.311611 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2019-03-13T00:40:00",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": 3
}thnassreceived 1.073 STEEM from power down installment (1.321 SP)2019/03/06 00:40:00
thnassreceived 1.073 STEEM from power down installment (1.321 SP)
2019/03/06 00:40:00
| deposited | 1.073 STEEM |
| from account | thnass |
| to account | thnass |
| withdrawn | 2149.311611 VESTS |
| Transaction Info | Block #30901566/Virtual Operation #3 |
View Raw JSON Data
{
"block": 30901566,
"op": [
"fill_vesting_withdraw",
{
"deposited": "1.073 STEEM",
"from_account": "thnass",
"to_account": "thnass",
"withdrawn": "2149.311611 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2019-03-06T00:40:00",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": 3
}thnassreceived 1.072 STEEM from power down installment (1.321 SP)2019/02/27 00:40:00
thnassreceived 1.072 STEEM from power down installment (1.321 SP)
2019/02/27 00:40:00
| deposited | 1.072 STEEM |
| from account | thnass |
| to account | thnass |
| withdrawn | 2149.311611 VESTS |
| Transaction Info | Block #30700103/Virtual Operation #3 |
View Raw JSON Data
{
"block": 30700103,
"op": [
"fill_vesting_withdraw",
{
"deposited": "1.072 STEEM",
"from_account": "thnass",
"to_account": "thnass",
"withdrawn": "2149.311611 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2019-02-27T00:40:00",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": 3
}thnassreceived 1.072 STEEM from power down installment (1.321 SP)2019/02/20 00:40:00
thnassreceived 1.072 STEEM from power down installment (1.321 SP)
2019/02/20 00:40:00
| deposited | 1.072 STEEM |
| from account | thnass |
| to account | thnass |
| withdrawn | 2149.311611 VESTS |
| Transaction Info | Block #30498652/Virtual Operation #3 |
View Raw JSON Data
{
"block": 30498652,
"op": [
"fill_vesting_withdraw",
{
"deposited": "1.072 STEEM",
"from_account": "thnass",
"to_account": "thnass",
"withdrawn": "2149.311611 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2019-02-20T00:40:00",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": 3
}thnassreceived 1.071 STEEM from power down installment (1.321 SP)2019/02/13 00:40:00
thnassreceived 1.071 STEEM from power down installment (1.321 SP)
2019/02/13 00:40:00
| deposited | 1.071 STEEM |
| from account | thnass |
| to account | thnass |
| withdrawn | 2149.311611 VESTS |
| Transaction Info | Block #30297209/Virtual Operation #3 |
View Raw JSON Data
{
"block": 30297209,
"op": [
"fill_vesting_withdraw",
{
"deposited": "1.071 STEEM",
"from_account": "thnass",
"to_account": "thnass",
"withdrawn": "2149.311611 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2019-02-13T00:40:00",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": 3
}2019/02/07 12:16:09
2019/02/07 12:16:09
| author | steemitboard |
| body | Congratulations @thnass! You have completed the following achievement on the Steem blockchain and have been rewarded with new badge(s) : <table><tr><td>https://steemitimages.com/60x70/http://steemitboard.com/@thnass/votes.png?201902071132</td><td>You made more than 10 upvotes. Your next target is to reach 50 upvotes.</td></tr> </table> <sub>_[Click here to view your Board](https://steemitboard.com/@thnass)_</sub> <sub>_If you no longer want to receive notifications, reply to this comment with the word_ `STOP`</sub> > Support [SteemitBoard's project](https://steemit.com/@steemitboard)! **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| parent author | thnass |
| parent permlink | connectivity-of-the-internet-of-things-pt2 |
| permlink | steemitboard-notify-thnass-20190207t121608000z |
| title | |
| Transaction Info | Block #30138442/Trx eb05760ad81ee377722482b61a401d2897934e61 |
View Raw JSON Data
{
"block": 30138442,
"op": [
"comment",
{
"author": "steemitboard",
"body": "Congratulations @thnass! You have completed the following achievement on the Steem blockchain and have been rewarded with new badge(s) :\n\n<table><tr><td>https://steemitimages.com/60x70/http://steemitboard.com/@thnass/votes.png?201902071132</td><td>You made more than 10 upvotes. Your next target is to reach 50 upvotes.</td></tr>\n</table>\n\n<sub>_[Click here to view your Board](https://steemitboard.com/@thnass)_</sub>\n<sub>_If you no longer want to receive notifications, reply to this comment with the word_ `STOP`</sub>\n\n\n\n> Support [SteemitBoard's project](https://steemit.com/@steemitboard)! **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}",
"parent_author": "thnass",
"parent_permlink": "connectivity-of-the-internet-of-things-pt2",
"permlink": "steemitboard-notify-thnass-20190207t121608000z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2019-02-07T12:16:09",
"trx_id": "eb05760ad81ee377722482b61a401d2897934e61",
"trx_in_block": 0,
"virtual_op": 0
}thnassupvoted (100.00%) @steemchiller / steemworld-weekly-support-182019/02/07 09:27:03
thnassupvoted (100.00%) @steemchiller / steemworld-weekly-support-18
2019/02/07 09:27:03
| author | steemchiller |
| permlink | steemworld-weekly-support-18 |
| voter | thnass |
| weight | 10000 (100.00%) |
| Transaction Info | Block #30135063/Trx 7022576ce6839635a2104491fb0f19f8c18a15b7 |
View Raw JSON Data
{
"block": 30135063,
"op": [
"vote",
{
"author": "steemchiller",
"permlink": "steemworld-weekly-support-18",
"voter": "thnass",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2019-02-07T09:27:03",
"trx_id": "7022576ce6839635a2104491fb0f19f8c18a15b7",
"trx_in_block": 34,
"virtual_op": 0
}thnassupvoted (100.00%) @steemchiller / steemworld-weekly-support-192019/02/07 09:26:54
thnassupvoted (100.00%) @steemchiller / steemworld-weekly-support-19
2019/02/07 09:26:54
| author | steemchiller |
| permlink | steemworld-weekly-support-19 |
| voter | thnass |
| weight | 10000 (100.00%) |
| Transaction Info | Block #30135060/Trx f886cb72ef21d11b86ba8a4642c7b7ed64dab982 |
View Raw JSON Data
{
"block": 30135060,
"op": [
"vote",
{
"author": "steemchiller",
"permlink": "steemworld-weekly-support-19",
"voter": "thnass",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2019-02-07T09:26:54",
"trx_id": "f886cb72ef21d11b86ba8a4642c7b7ed64dab982",
"trx_in_block": 17,
"virtual_op": 0
}thnassupvoted (100.00%) @steemchiller / steemworld-weekly-support-202019/02/07 09:25:39
thnassupvoted (100.00%) @steemchiller / steemworld-weekly-support-20
2019/02/07 09:25:39
| author | steemchiller |
| permlink | steemworld-weekly-support-20 |
| voter | thnass |
| weight | 10000 (100.00%) |
| Transaction Info | Block #30135035/Trx bf4e1120ee47038e86f009b7d0117519edd91e6e |
View Raw JSON Data
{
"block": 30135035,
"op": [
"vote",
{
"author": "steemchiller",
"permlink": "steemworld-weekly-support-20",
"voter": "thnass",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2019-02-07T09:25:39",
"trx_id": "bf4e1120ee47038e86f009b7d0117519edd91e6e",
"trx_in_block": 18,
"virtual_op": 0
}thnassupvoted (100.00%) @steemchiller / steemworld-weekly-support-212019/02/07 09:22:36
thnassupvoted (100.00%) @steemchiller / steemworld-weekly-support-21
2019/02/07 09:22:36
| author | steemchiller |
| permlink | steemworld-weekly-support-21 |
| voter | thnass |
| weight | 10000 (100.00%) |
| Transaction Info | Block #30134974/Trx 15c6c86a46901d4b6958fe7c24d4ab9f8019aa3f |
View Raw JSON Data
{
"block": 30134974,
"op": [
"vote",
{
"author": "steemchiller",
"permlink": "steemworld-weekly-support-21",
"voter": "thnass",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2019-02-07T09:22:36",
"trx_id": "15c6c86a46901d4b6958fe7c24d4ab9f8019aa3f",
"trx_in_block": 4,
"virtual_op": 0
}thnassstarted power down of 17.179 SP2019/02/06 00:40:00
thnassstarted power down of 17.179 SP
2019/02/06 00:40:00
| account | thnass |
| vesting shares | 27941.050944 VESTS |
| Transaction Info | Block #30095754/Trx 54622967b0a300ae4a551287e440c85c30596417 |
View Raw JSON Data
{
"block": 30095754,
"op": [
"withdraw_vesting",
{
"account": "thnass",
"vesting_shares": "27941.050944 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2019-02-06T00:40:00",
"trx_id": "54622967b0a300ae4a551287e440c85c30596417",
"trx_in_block": 15,
"virtual_op": 0
}thnassupvoted (100.00%) @flauwy / re-broncnutz-69608xek-20181023t003944371z2018/10/23 21:48:51
thnassupvoted (100.00%) @flauwy / re-broncnutz-69608xek-20181023t003944371z
2018/10/23 21:48:51
| author | flauwy |
| permlink | re-broncnutz-69608xek-20181023t003944371z |
| voter | thnass |
| weight | 10000 (100.00%) |
| Transaction Info | Block #27070582/Trx 76fe745ec076f0add1b8d5b7cbcb05726fc2ae59 |
View Raw JSON Data
{
"block": 27070582,
"op": [
"vote",
{
"author": "flauwy",
"permlink": "re-broncnutz-69608xek-20181023t003944371z",
"voter": "thnass",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2018-10-23T21:48:51",
"trx_id": "76fe745ec076f0add1b8d5b7cbcb05726fc2ae59",
"trx_in_block": 22,
"virtual_op": 0
}thnassupdated their account properties2018/10/23 21:33:21
thnassupdated their account properties
2018/10/23 21:33:21
| account | thnass |
| json metadata | |
| memo key | STM64WU3dtcfVXsQUVpRyonUifkbDwSENzkBkb4Y6AXBWgU8eMTgC |
| posting | {"account_auths":[["dtube.app",1]],"key_auths":[["STM6PosxLZorrCrRKvHQZ178jfDUHxkgTzSq3mnLYcwgf1UdkWsEi",1]],"weight_threshold":1} |
| Transaction Info | Block #27070273/Trx 3ecced9600158e3947a7de188c9a0959dac1be04 |
View Raw JSON Data
{
"block": 27070273,
"op": [
"account_update",
{
"account": "thnass",
"json_metadata": "",
"memo_key": "STM64WU3dtcfVXsQUVpRyonUifkbDwSENzkBkb4Y6AXBWgU8eMTgC",
"posting": {
"account_auths": [
[
"dtube.app",
1
]
],
"key_auths": [
[
"STM6PosxLZorrCrRKvHQZ178jfDUHxkgTzSq3mnLYcwgf1UdkWsEi",
1
]
],
"weight_threshold": 1
}
}
],
"op_in_trx": 0,
"timestamp": "2018-10-23T21:33:21",
"trx_id": "3ecced9600158e3947a7de188c9a0959dac1be04",
"trx_in_block": 9,
"virtual_op": 0
}| author | thnass |
| permlink | re-ashaley-famecoin-last-day-of-ico-reasons-why-you-should-invest-20161124t114800659z |
| voter | ashaley |
| weight | 10000 (100.00%) |
| Transaction Info | Block #7003988/Trx cad1a0d59fd87e54b94b39e6120068c4089fca75 |
View Raw JSON Data
{
"block": 7003988,
"op": [
"vote",
{
"author": "thnass",
"permlink": "re-ashaley-famecoin-last-day-of-ico-reasons-why-you-should-invest-20161124t114800659z",
"voter": "ashaley",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-11-24T12:28:03",
"trx_id": "cad1a0d59fd87e54b94b39e6120068c4089fca75",
"trx_in_block": 3,
"virtual_op": 0
}| author | thnass |
| body | Nice, Will put something small here and lets see how it goes . |
| json metadata | {"tags":["famecoin"]} |
| parent author | ashaley |
| parent permlink | famecoin-last-day-of-ico-reasons-why-you-should-invest |
| permlink | re-ashaley-famecoin-last-day-of-ico-reasons-why-you-should-invest-20161124t114800659z |
| title | |
| Transaction Info | Block #7003191/Trx d1e3e02067510ad802c84c7bc38db0666af7af28 |
View Raw JSON Data
{
"block": 7003191,
"op": [
"comment",
{
"author": "thnass",
"body": "Nice, Will put something small here and lets see how it goes .",
"json_metadata": "{\"tags\":[\"famecoin\"]}",
"parent_author": "ashaley",
"parent_permlink": "famecoin-last-day-of-ico-reasons-why-you-should-invest",
"permlink": "re-ashaley-famecoin-last-day-of-ico-reasons-why-you-should-invest-20161124t114800659z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2016-11-24T11:48:09",
"trx_id": "d1e3e02067510ad802c84c7bc38db0666af7af28",
"trx_in_block": 0,
"virtual_op": 0
}thnassupvoted (100.00%) @ashaley / famecoin-last-day-of-ico-reasons-why-you-should-invest
thnassupvoted (100.00%) @ashaley / famecoin-last-day-of-ico-reasons-why-you-should-invest
| author | ashaley |
| permlink | famecoin-last-day-of-ico-reasons-why-you-should-invest |
| voter | thnass |
| weight | 10000 (100.00%) |
| Transaction Info | Block #7003158/Trx c908f670349ff41a68724317dc5f0dca864588a6 |
View Raw JSON Data
{
"block": 7003158,
"op": [
"vote",
{
"author": "ashaley",
"permlink": "famecoin-last-day-of-ico-reasons-why-you-should-invest",
"voter": "thnass",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-11-24T11:46:30",
"trx_id": "c908f670349ff41a68724317dc5f0dca864588a6",
"trx_in_block": 0,
"virtual_op": 0
}| author | thnass |
| permlink | re-steempowerwhale-re-thnass-connectivity-of-the-internet-of-things-pt2-20160926t192642314z |
| voter | thnass |
| weight | 10000 (100.00%) |
| Transaction Info | Block #5321354/Trx cb255954f20cd151ee53224f6ac560b51cfa6fa3 |
View Raw JSON Data
{
"block": 5321354,
"op": [
"vote",
{
"author": "thnass",
"permlink": "re-steempowerwhale-re-thnass-connectivity-of-the-internet-of-things-pt2-20160926t192642314z",
"voter": "thnass",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-09-27T00:48:00",
"trx_id": "cb255954f20cd151ee53224f6ac560b51cfa6fa3",
"trx_in_block": 3,
"virtual_op": 0
}alexgrremoved vote from (0.00%) @thnass / connectivity-of-the-internet-of-things
alexgrremoved vote from (0.00%) @thnass / connectivity-of-the-internet-of-things
| author | thnass |
| permlink | connectivity-of-the-internet-of-things |
| voter | alexgr |
| weight | 0 (0.00%) |
| Transaction Info | Block #5317588/Trx c1537efeb64b2c44e42f3e642936afc460bfda60 |
View Raw JSON Data
{
"block": 5317588,
"op": [
"vote",
{
"author": "thnass",
"permlink": "connectivity-of-the-internet-of-things",
"voter": "alexgr",
"weight": 0
}
],
"op_in_trx": 0,
"timestamp": "2016-09-26T21:39:39",
"trx_id": "c1537efeb64b2c44e42f3e642936afc460bfda60",
"trx_in_block": 2,
"virtual_op": 0
}alexgrremoved vote from (0.00%) @thnass / connectivity-of-the-internet-of-things-pt2
alexgrremoved vote from (0.00%) @thnass / connectivity-of-the-internet-of-things-pt2
| author | thnass |
| permlink | connectivity-of-the-internet-of-things-pt2 |
| voter | alexgr |
| weight | 0 (0.00%) |
| Transaction Info | Block #5317584/Trx 5ff5a9ac1016e14078e489b915c0acf75d0521df |
View Raw JSON Data
{
"block": 5317584,
"op": [
"vote",
{
"author": "thnass",
"permlink": "connectivity-of-the-internet-of-things-pt2",
"voter": "alexgr",
"weight": 0
}
],
"op_in_trx": 0,
"timestamp": "2016-09-26T21:39:27",
"trx_id": "5ff5a9ac1016e14078e489b915c0acf75d0521df",
"trx_in_block": 2,
"virtual_op": 0
}delasageupvoted (100.00%) @thnass / connectivity-of-the-internet-of-things-pt2
delasageupvoted (100.00%) @thnass / connectivity-of-the-internet-of-things-pt2
| author | thnass |
| permlink | connectivity-of-the-internet-of-things-pt2 |
| voter | delasage |
| weight | 10000 (100.00%) |
| Transaction Info | Block #5317443/Trx a1195459c53fad9449cbc429c4ddebf972be6afd |
View Raw JSON Data
{
"block": 5317443,
"op": [
"vote",
{
"author": "thnass",
"permlink": "connectivity-of-the-internet-of-things-pt2",
"voter": "delasage",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-09-26T21:32:24",
"trx_id": "a1195459c53fad9449cbc429c4ddebf972be6afd",
"trx_in_block": 4,
"virtual_op": 0
}| author | thnass |
| permlink | re-steempowerwhale-re-thnass-connectivity-of-the-internet-of-things-pt2-20160926t192642314z |
| voter | delasage |
| weight | 10000 (100.00%) |
| Transaction Info | Block #5317439/Trx a1a7e4f292e78d6e67d5d8ed92638af785bbdfcd |
View Raw JSON Data
{
"block": 5317439,
"op": [
"vote",
{
"author": "thnass",
"permlink": "re-steempowerwhale-re-thnass-connectivity-of-the-internet-of-things-pt2-20160926t192642314z",
"voter": "delasage",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-09-26T21:32:12",
"trx_id": "a1a7e4f292e78d6e67d5d8ed92638af785bbdfcd",
"trx_in_block": 3,
"virtual_op": 0
}| author | steemcleaners |
| body | Source: https://learn.sparkfun.com/tutorials/connectivity-of-the-internet-of-things Copying/Pasting full texts is frowned upon by the community. Sharing content by itself adds no original content and no value. Share content and add value by: - Using a few sentences from your source in “quotes.” Use HTML tags or Markdown. - Linking to your source - Include your own original thoughts and ideas on what you have shared. Repeated copy/paste posts are considered spam. Spam is discouraged by the community, and may result in action from the [cheetah bot](https://steemit.com/steemitabuse/@cheetah/cheetah-bot-explained). Not indicating that the content you copy/paste is not your original work could be seen as [plagiarism](http://www.plagiarism.org/plagiarism-101/what-is-plagiarism/) -- if you are actually the original author, please do reply to let us know! |
| json metadata | {"tags":["internetofthings"],"links":["https://learn.sparkfun.com/tutorials/connectivity-of-the-internet-of-things","https://steemit.com/steemitabuse/@cheetah/cheetah-bot-explained","http://www.plagiarism.org/plagiarism-101/what-is-plagiarism/"]} |
| parent author | thnass |
| parent permlink | connectivity-of-the-internet-of-things-pt2 |
| permlink | re-thnass-connectivity-of-the-internet-of-things-pt2-20160926t203525911z |
| title | |
| Transaction Info | Block #5316304/Trx e86e2278393eb3b48bbefa88891fe3bbc2ecf138 |
View Raw JSON Data
{
"block": 5316304,
"op": [
"comment",
{
"author": "steemcleaners",
"body": "Source: https://learn.sparkfun.com/tutorials/connectivity-of-the-internet-of-things\n\nCopying/Pasting full texts is frowned upon by the community. Sharing content by itself adds no original content and no value.\n\nShare content and add value by:\n- Using a few sentences from your source in “quotes.” Use HTML tags or Markdown. \n- Linking to your source\n- Include your own original thoughts and ideas on what you have shared.\n\nRepeated copy/paste posts are considered spam. Spam is discouraged by the community, and may result in action from the [cheetah bot](https://steemit.com/steemitabuse/@cheetah/cheetah-bot-explained).\n\nNot indicating that the content you copy/paste is not your original work could be seen as [plagiarism](http://www.plagiarism.org/plagiarism-101/what-is-plagiarism/) -- if you are actually the original author, please do reply to let us know!",
"json_metadata": "{\"tags\":[\"internetofthings\"],\"links\":[\"https://learn.sparkfun.com/tutorials/connectivity-of-the-internet-of-things\",\"https://steemit.com/steemitabuse/@cheetah/cheetah-bot-explained\",\"http://www.plagiarism.org/plagiarism-101/what-is-plagiarism/\"]}",
"parent_author": "thnass",
"parent_permlink": "connectivity-of-the-internet-of-things-pt2",
"permlink": "re-thnass-connectivity-of-the-internet-of-things-pt2-20160926t203525911z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2016-09-26T20:35:27",
"trx_id": "e86e2278393eb3b48bbefa88891fe3bbc2ecf138",
"trx_in_block": 0,
"virtual_op": 0
}| author | alexgr |
| body | Welcome aboard... |
| json metadata | {"tags":["inter"]} |
| parent author | thnass |
| parent permlink | connectivity-of-the-internet-of-things |
| permlink | re-thnass-connectivity-of-the-internet-of-things-20160926t195722980z |
| title | |
| Transaction Info | Block #5315543/Trx 7ccd1868d59f3ef52ec3d5c34b8ed2196061ddda |
View Raw JSON Data
{
"block": 5315543,
"op": [
"comment",
{
"author": "alexgr",
"body": "Welcome aboard...",
"json_metadata": "{\"tags\":[\"inter\"]}",
"parent_author": "thnass",
"parent_permlink": "connectivity-of-the-internet-of-things",
"permlink": "re-thnass-connectivity-of-the-internet-of-things-20160926t195722980z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2016-09-26T19:57:24",
"trx_id": "7ccd1868d59f3ef52ec3d5c34b8ed2196061ddda",
"trx_in_block": 2,
"virtual_op": 0
}alexgrupvoted (100.00%) @thnass / connectivity-of-the-internet-of-things-pt2
alexgrupvoted (100.00%) @thnass / connectivity-of-the-internet-of-things-pt2
| author | thnass |
| permlink | connectivity-of-the-internet-of-things-pt2 |
| voter | alexgr |
| weight | 10000 (100.00%) |
| Transaction Info | Block #5315531/Trx 309719b018c1f75f1189c0ea434a22cb75f23c4d |
View Raw JSON Data
{
"block": 5315531,
"op": [
"vote",
{
"author": "thnass",
"permlink": "connectivity-of-the-internet-of-things-pt2",
"voter": "alexgr",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-09-26T19:56:48",
"trx_id": "309719b018c1f75f1189c0ea434a22cb75f23c4d",
"trx_in_block": 3,
"virtual_op": 0
}alexgrupvoted (100.00%) @thnass / connectivity-of-the-internet-of-things
alexgrupvoted (100.00%) @thnass / connectivity-of-the-internet-of-things
| author | thnass |
| permlink | connectivity-of-the-internet-of-things |
| voter | alexgr |
| weight | 10000 (100.00%) |
| Transaction Info | Block #5315524/Trx c45850db62002b86a26c0b81a79da88994da8ba9 |
View Raw JSON Data
{
"block": 5315524,
"op": [
"vote",
{
"author": "thnass",
"permlink": "connectivity-of-the-internet-of-things",
"voter": "alexgr",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-09-26T19:56:27",
"trx_id": "c45850db62002b86a26c0b81a79da88994da8ba9",
"trx_in_block": 3,
"virtual_op": 0
}| author | thnass |
| body | @@ -1804,16 +1804,28 @@ on. eg ( +MSP432 MCU, Arduino, |
| json metadata | {"tags":["internetofthings"]} |
| parent author | steempowerwhale |
| parent permlink | re-thnass-connectivity-of-the-internet-of-things-pt2-20160926t183529917z |
| permlink | re-steempowerwhale-re-thnass-connectivity-of-the-internet-of-things-pt2-20160926t192642314z |
| title | |
| Transaction Info | Block #5314998/Trx 096ffa5b8f09f2bfbf577305d2c04dc229c8ecb6 |
View Raw JSON Data
{
"block": 5314998,
"op": [
"comment",
{
"author": "thnass",
"body": "@@ -1804,16 +1804,28 @@\n on. eg (\n+MSP432 MCU, \n Arduino,\n",
"json_metadata": "{\"tags\":[\"internetofthings\"]}",
"parent_author": "steempowerwhale",
"parent_permlink": "re-thnass-connectivity-of-the-internet-of-things-pt2-20160926t183529917z",
"permlink": "re-steempowerwhale-re-thnass-connectivity-of-the-internet-of-things-pt2-20160926t192642314z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2016-09-26T19:30:09",
"trx_id": "096ffa5b8f09f2bfbf577305d2c04dc229c8ecb6",
"trx_in_block": 4,
"virtual_op": 0
}| author | thnass |
| body | Thanks for the compliment. There are many routers being developed now adays targeting IoT an example and a good one is the OnHub from TP-LINK and Google. But I'll go in for ASUS RT-AC88U due to the fact that it's already ahead in technology with it's MU-MIMO. Multi-User Multiple Input Multiple Output (MU-MIMO) technology The RT-AC88U supports Multi-User Multiple Input Multiple Output (MU-MIMO) technology, which is designed to handle Wi-Fi bandwidth efficiently. MU-MIMO was first introduced with the Qualcomm MU/EFX 802.11AC Wi-Fi chip. The RT-AC88U, however, uses the first Broadcom Wi-Fi chip that supports this technology. Prior to MU-MIMO, all 802.11ac routers treat all Wi-Fi clients the same, regardless of their Wi-Fi power. Since a router typically has more Wi-Fi power than a client, in a particular wireless connection, the router is hardly used at full capacity. For this reason, most Wi-Fi connections are not efficient, where the router wastes its power for lower-tier clients and hence doesn't have enough power to maintain connection quality for multiple clients. With MU-MIMO, multiple simultaneous transmissions of different Wi-Fi tiers are sent to multiple devices at the same time, enabling them to connect at the speed each client needs. In other words, having a MU-MIMO Wi-Fi network is like having multiple wireless routers of different Wi-Fi tiers. Each of these "routers" is dedicated to each tier of devices in the network, so that multiple devices can connect at the same time without slowing one another down. MU-MIMO has been quickly adopted by both routers and clients, and it's predicted that by the end of next year, most, if not all, new Wi-Fi devices will support this technology. For IoT cloud solution, it also depends on the hardware you use in implementation. eg (Arduino, Raspberry pi, etc) But Sierra Wireless has a cloud platform with a lot of tools for app development. |
| json metadata | {"tags":["internetofthings"]} |
| parent author | steempowerwhale |
| parent permlink | re-thnass-connectivity-of-the-internet-of-things-pt2-20160926t183529917z |
| permlink | re-steempowerwhale-re-thnass-connectivity-of-the-internet-of-things-pt2-20160926t192642314z |
| title | |
| Transaction Info | Block #5314930/Trx 4adc6707bc68c8bb71657398156be41ef8f36928 |
View Raw JSON Data
{
"block": 5314930,
"op": [
"comment",
{
"author": "thnass",
"body": "Thanks for the compliment.\nThere are many routers being developed now adays targeting IoT an example and a good one is the OnHub from TP-LINK and Google.\nBut I'll go in for ASUS RT-AC88U due to the fact that it's already ahead in technology with it's MU-MIMO.\n\nMulti-User Multiple Input Multiple Output (MU-MIMO) technology\n\nThe RT-AC88U supports Multi-User Multiple Input Multiple Output (MU-MIMO) technology, which is designed to handle Wi-Fi bandwidth efficiently. MU-MIMO was first introduced with the Qualcomm MU/EFX 802.11AC Wi-Fi chip. The RT-AC88U, however, uses the first Broadcom Wi-Fi chip that supports this technology.\n\nPrior to MU-MIMO, all 802.11ac routers treat all Wi-Fi clients the same, regardless of their Wi-Fi power. Since a router typically has more Wi-Fi power than a client, in a particular wireless connection, the router is hardly used at full capacity. For this reason, most Wi-Fi connections are not efficient, where the router wastes its power for lower-tier clients and hence doesn't have enough power to maintain connection quality for multiple clients.\n\nWith MU-MIMO, multiple simultaneous transmissions of different Wi-Fi tiers are sent to multiple devices at the same time, enabling them to connect at the speed each client needs. In other words, having a MU-MIMO Wi-Fi network is like having multiple wireless routers of different Wi-Fi tiers. Each of these \"routers\" is dedicated to each tier of devices in the network, so that multiple devices can connect at the same time without slowing one another down.\n\nMU-MIMO has been quickly adopted by both routers and clients, and it's predicted that by the end of next year, most, if not all, new Wi-Fi devices will support this technology.\n\nFor IoT cloud solution, it also depends on the hardware you use in implementation. eg (Arduino, Raspberry pi, etc)\nBut Sierra Wireless has a cloud platform with a lot of tools for app development.",
"json_metadata": "{\"tags\":[\"internetofthings\"]}",
"parent_author": "steempowerwhale",
"parent_permlink": "re-thnass-connectivity-of-the-internet-of-things-pt2-20160926t183529917z",
"permlink": "re-steempowerwhale-re-thnass-connectivity-of-the-internet-of-things-pt2-20160926t192642314z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2016-09-26T19:26:45",
"trx_id": "4adc6707bc68c8bb71657398156be41ef8f36928",
"trx_in_block": 2,
"virtual_op": 0
}blendupvoted (100.00%) @thnass / connectivity-of-the-internet-of-things-pt2
blendupvoted (100.00%) @thnass / connectivity-of-the-internet-of-things-pt2
| author | thnass |
| permlink | connectivity-of-the-internet-of-things-pt2 |
| voter | blend |
| weight | 10000 (100.00%) |
| Transaction Info | Block #5314909/Trx 71bab7ff11e86696c9b7a09040cf12e02fc70b9f |
View Raw JSON Data
{
"block": 5314909,
"op": [
"vote",
{
"author": "thnass",
"permlink": "connectivity-of-the-internet-of-things-pt2",
"voter": "blend",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-09-26T19:25:42",
"trx_id": "71bab7ff11e86696c9b7a09040cf12e02fc70b9f",
"trx_in_block": 0,
"virtual_op": 0
}online.vtb24upvoted (100.00%) @thnass / connectivity-of-the-internet-of-things-pt2
online.vtb24upvoted (100.00%) @thnass / connectivity-of-the-internet-of-things-pt2
| author | thnass |
| permlink | connectivity-of-the-internet-of-things-pt2 |
| voter | online.vtb24 |
| weight | 10000 (100.00%) |
| Transaction Info | Block #5314117/Trx b24b3eca6c3d894894d4ffb714e4596d176b2129 |
View Raw JSON Data
{
"block": 5314117,
"op": [
"vote",
{
"author": "thnass",
"permlink": "connectivity-of-the-internet-of-things-pt2",
"voter": "online.vtb24",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-09-26T18:46:06",
"trx_id": "b24b3eca6c3d894894d4ffb714e4596d176b2129",
"trx_in_block": 2,
"virtual_op": 0
}thnasspublished a new post: connectivity-of-the-internet-of-things-pt2
thnasspublished a new post: connectivity-of-the-internet-of-things-pt2
| author | thnass |
| body | @@ -1,12 +1,168 @@ +If you are now visiting this article, please check the previous one on %5B%3E%3EPt1%3C%3C%5D(https://steemit.com/inter/@thnass/connectivity-of-the-internet-of-things)%0A ### WiFi%0Ahtt |
| json metadata | {"tags":["internetofthings","cryptocurrency","technology","beyondbitcoin","electronics"],"image":["https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/WifI-logo.png","http://i68.tinypic.com/2z6wkmf.jpg","https://cdn.sparkfun.com/r/600-600/assets/learn_tutorials/5/3/4/Zigbeelogo.png","https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/Zigbee-topologies.png","https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/ZigbeeWifi_Coexistence.gif","https://cdn.sparkfun.com/r/600-600/assets/learn_tutorials/5/3/4/ZigBee-3.01.png"],"links":["https://steemit.com/inter/@thnass/connectivity-of-the-internet-of-things"]} |
| parent author | |
| parent permlink | internetofthings |
| permlink | connectivity-of-the-internet-of-things-pt2 |
| title | Connectivity of the Internet of Things (Pt2) |
| Transaction Info | Block #5314113/Trx 47db483153438789b3d4cb90ff454e3982c3c514 |
View Raw JSON Data
{
"block": 5314113,
"op": [
"comment",
{
"author": "thnass",
"body": "@@ -1,12 +1,168 @@\n+If you are now visiting this article, please check the previous one on %5B%3E%3EPt1%3C%3C%5D(https://steemit.com/inter/@thnass/connectivity-of-the-internet-of-things)%0A\n ### WiFi%0Ahtt\n",
"json_metadata": "{\"tags\":[\"internetofthings\",\"cryptocurrency\",\"technology\",\"beyondbitcoin\",\"electronics\"],\"image\":[\"https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/WifI-logo.png\",\"http://i68.tinypic.com/2z6wkmf.jpg\",\"https://cdn.sparkfun.com/r/600-600/assets/learn_tutorials/5/3/4/Zigbeelogo.png\",\"https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/Zigbee-topologies.png\",\"https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/ZigbeeWifi_Coexistence.gif\",\"https://cdn.sparkfun.com/r/600-600/assets/learn_tutorials/5/3/4/ZigBee-3.01.png\"],\"links\":[\"https://steemit.com/inter/@thnass/connectivity-of-the-internet-of-things\"]}",
"parent_author": "",
"parent_permlink": "internetofthings",
"permlink": "connectivity-of-the-internet-of-things-pt2",
"title": "Connectivity of the Internet of Things (Pt2)"
}
],
"op_in_trx": 0,
"timestamp": "2016-09-26T18:45:54",
"trx_id": "47db483153438789b3d4cb90ff454e3982c3c514",
"trx_in_block": 2,
"virtual_op": 0
}alina1upvoted (100.00%) @thnass / connectivity-of-the-internet-of-things-pt2
alina1upvoted (100.00%) @thnass / connectivity-of-the-internet-of-things-pt2
| author | thnass |
| permlink | connectivity-of-the-internet-of-things-pt2 |
| voter | alina1 |
| weight | 10000 (100.00%) |
| Transaction Info | Block #5314046/Trx c859481782494b38cea2d0fa96d9ad2b9a71bc3c |
View Raw JSON Data
{
"block": 5314046,
"op": [
"vote",
{
"author": "thnass",
"permlink": "connectivity-of-the-internet-of-things-pt2",
"voter": "alina1",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-09-26T18:42:33",
"trx_id": "c859481782494b38cea2d0fa96d9ad2b9a71bc3c",
"trx_in_block": 3,
"virtual_op": 0
}illuziyaupvoted (100.00%) @thnass / connectivity-of-the-internet-of-things-pt2
illuziyaupvoted (100.00%) @thnass / connectivity-of-the-internet-of-things-pt2
| author | thnass |
| permlink | connectivity-of-the-internet-of-things-pt2 |
| voter | illuziya |
| weight | 10000 (100.00%) |
| Transaction Info | Block #5314019/Trx 4d7e67ca510e5e82d94343bee334a42d495b691d |
View Raw JSON Data
{
"block": 5314019,
"op": [
"vote",
{
"author": "thnass",
"permlink": "connectivity-of-the-internet-of-things-pt2",
"voter": "illuziya",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-09-26T18:41:09",
"trx_id": "4d7e67ca510e5e82d94343bee334a42d495b691d",
"trx_in_block": 0,
"virtual_op": 0
}| author | steempowerwhale |
| body | Great informative post. What routers and cloud solutions would you use for internet of things? |
| json metadata | {"tags":["internetofthings"]} |
| parent author | thnass |
| parent permlink | connectivity-of-the-internet-of-things-pt2 |
| permlink | re-thnass-connectivity-of-the-internet-of-things-pt2-20160926t183529917z |
| title | |
| Transaction Info | Block #5313907/Trx e4467e559a9be18925e15f01555b5a5f7dfc2751 |
View Raw JSON Data
{
"block": 5313907,
"op": [
"comment",
{
"author": "steempowerwhale",
"body": "Great informative post. What routers and cloud solutions would you use for internet of things?",
"json_metadata": "{\"tags\":[\"internetofthings\"]}",
"parent_author": "thnass",
"parent_permlink": "connectivity-of-the-internet-of-things-pt2",
"permlink": "re-thnass-connectivity-of-the-internet-of-things-pt2-20160926t183529917z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2016-09-26T18:35:33",
"trx_id": "e4467e559a9be18925e15f01555b5a5f7dfc2751",
"trx_in_block": 0,
"virtual_op": 0
}steempowerwhaleupvoted (100.00%) @thnass / connectivity-of-the-internet-of-things-pt2
steempowerwhaleupvoted (100.00%) @thnass / connectivity-of-the-internet-of-things-pt2
| author | thnass |
| permlink | connectivity-of-the-internet-of-things-pt2 |
| voter | steempowerwhale |
| weight | 10000 (100.00%) |
| Transaction Info | Block #5313885/Trx 339bef8aa39ccedefcb1133ff38cddee2287ab9a |
View Raw JSON Data
{
"block": 5313885,
"op": [
"vote",
{
"author": "thnass",
"permlink": "connectivity-of-the-internet-of-things-pt2",
"voter": "steempowerwhale",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-09-26T18:34:27",
"trx_id": "339bef8aa39ccedefcb1133ff38cddee2287ab9a",
"trx_in_block": 3,
"virtual_op": 0
}thnasspublished a new post: connectivity-of-the-internet-of-things
thnasspublished a new post: connectivity-of-the-internet-of-things
| author | thnass |
| body | @@ -7843,14 +7843,109 @@ eck +%5B%3E%3E part 2 +%3C%3C%5D(https://steemit.com/internetofthings/@thnass/connectivity-of-the-internet-of-things-pt2) for |
| json metadata | {"tags":["inter","internetofthings","cryptocurrency","technology","beyondbitcoin"],"image":["https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/network-cables-494648_640.jpg","https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/508px-NetworkTopologies.svg.png","https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/StringPhone.jpg","https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/StarNetwork.svg.png","https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/NetworkTopology-FullyConnected__1_.png","https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/network-infrastructure-vs-a.png"],"links":["https://steemit.com/internetofthings/@thnass/connectivity-of-the-internet-of-things-pt2"]} |
| parent author | |
| parent permlink | inter |
| permlink | connectivity-of-the-internet-of-things |
| title | Connectivity of the Internet of Things |
| Transaction Info | Block #5313836/Trx 604b9858a529b220e97cab00eacbd55fa318bf58 |
View Raw JSON Data
{
"block": 5313836,
"op": [
"comment",
{
"author": "thnass",
"body": "@@ -7843,14 +7843,109 @@\n eck \n+%5B%3E%3E\n part 2\n+%3C%3C%5D(https://steemit.com/internetofthings/@thnass/connectivity-of-the-internet-of-things-pt2)\n for\n",
"json_metadata": "{\"tags\":[\"inter\",\"internetofthings\",\"cryptocurrency\",\"technology\",\"beyondbitcoin\"],\"image\":[\"https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/network-cables-494648_640.jpg\",\"https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/508px-NetworkTopologies.svg.png\",\"https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/StringPhone.jpg\",\"https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/StarNetwork.svg.png\",\"https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/NetworkTopology-FullyConnected__1_.png\",\"https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/network-infrastructure-vs-a.png\"],\"links\":[\"https://steemit.com/internetofthings/@thnass/connectivity-of-the-internet-of-things-pt2\"]}",
"parent_author": "",
"parent_permlink": "inter",
"permlink": "connectivity-of-the-internet-of-things",
"title": "Connectivity of the Internet of Things"
}
],
"op_in_trx": 0,
"timestamp": "2016-09-26T18:32:00",
"trx_id": "604b9858a529b220e97cab00eacbd55fa318bf58",
"trx_in_block": 5,
"virtual_op": 0
}alina1upvoted (100.00%) @thnass / connectivity-of-the-internet-of-things
alina1upvoted (100.00%) @thnass / connectivity-of-the-internet-of-things
| author | thnass |
| permlink | connectivity-of-the-internet-of-things |
| voter | alina1 |
| weight | 10000 (100.00%) |
| Transaction Info | Block #5313792/Trx f42a548d888d0341f6125fa9dc991d42bfb3526c |
View Raw JSON Data
{
"block": 5313792,
"op": [
"vote",
{
"author": "thnass",
"permlink": "connectivity-of-the-internet-of-things",
"voter": "alina1",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-09-26T18:29:48",
"trx_id": "f42a548d888d0341f6125fa9dc991d42bfb3526c",
"trx_in_block": 0,
"virtual_op": 0
}thnassupvoted (100.00%) @thnass / connectivity-of-the-internet-of-things-pt2
thnassupvoted (100.00%) @thnass / connectivity-of-the-internet-of-things-pt2
| author | thnass |
| permlink | connectivity-of-the-internet-of-things-pt2 |
| voter | thnass |
| weight | 10000 (100.00%) |
| Transaction Info | Block #5313778/Trx 8ed6e80afa48110c0fff4c90a7832848329b9428 |
View Raw JSON Data
{
"block": 5313778,
"op": [
"vote",
{
"author": "thnass",
"permlink": "connectivity-of-the-internet-of-things-pt2",
"voter": "thnass",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-09-26T18:29:06",
"trx_id": "8ed6e80afa48110c0fff4c90a7832848329b9428",
"trx_in_block": 3,
"virtual_op": 0
}thnasspublished a new post: connectivity-of-the-internet-of-things-pt2
thnasspublished a new post: connectivity-of-the-internet-of-things-pt2
| author | thnass |
| body | ### WiFi https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/WifI-logo.png WiFi is one of the most common communication protocols. You probably couldn’t imagine your life without it. From the comfort of our homes to classrooms, cafés and airports, we see WiFi everywhere. The extent of WiFi’s influence in our lives has been so great that now it harbors a source of good SSID puns like this! (Sometimes, mostly they’re bad.) https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/Network-names_6.png WiFi essentially uses an infrastructure network, which additionally supports ad-hoc networking in infrastructure mode. Infrastructure mode of wireless communication provides a bridge to other networks, medium access control and forwarding. The network handling functions are placed into the access point (router), and the clients can remain simple (in context of network). Also, WiFi is a star-based network. The communication goes from wireless nodes (devices) to a wireless access point (router or network controller). The current standard being used is 802.11ac, which was released in 2013, although the version 802.11n, which was released in 2009, is still prevalent. The 802.11ac offers speeds up to 800Mbit/s whereas 802.11n offered up to 150Mbits/s. You might have also seen devices that have even older standards of 802.11a/b/g, which are now called legacy devices. However, since WiFi has downward compatibility, old devices continue to work with devices that have new standards. The range of your device’s WiFi depends on a few factors: * Which WiFi standard the device is running. The latest standards obviously offer more range than the older versions. * Physical obstructions like walls also play a critical role in determining the range. Therefore, in open spaces the range of the WiFi network would be more than in enclosed spaces with walls and other interfering objects. >To address the weakness of WiFi over other low-powered technologies, an activity was started to standardize low-power WiFi (IEEE 802.11ah). The development of this protocol is being worked on, but its worldwide adaptation is doubtful. One of the main reasons is this is not backward compatible to the existing 802.11bgn networks. ##### Advantages of WiFi: * WiFi has a decent range coverage and can penetrate walls and other obstacles in the way. * Adding and removing devices in a WiFi network is a piece of cake. ##### Disadvantages of WiFi: * Obviously, the lack of wires comes at a cost of lower bandwidth. The radio waves of the network might interfere with other equipment. * Most importantly, security of WiFi is weaker than its wired counterparts Now thinking about your project, WiFi is ideal when we want to set up a quick connection between our device (should be WiFi compatible) and the internet. WiFi is designed around the goal of keeping its power consumption limited, so you can run your project on a dedicated battery as well. WiFi should be used when you do not care much about how and when exactly your device should connect and communicate with your server and all you are looking for is hassle-free connection to the internet. ### Thread Thread is an open standard for reliable, cost-effective, low-power, wireless D2D (device to device) communication. It was designed specifically for connected home applications. It came into existence in 2014, when the Thread Group was formed. It now has big organizations like Google, Samsung, Qualcomm, and ARM to design and develop the Thread protocol. http://i68.tinypic.com/2z6wkmf.jpg Nest uses Thread network for its Thermostat and Nest Cam products. Thread is designed while keeping in mind the home automation space – to have devices set up and connect easily, have low power consumption for longer battery life and be secure! It is based on the standard 802.15.4 (6loWPAN) architecture. The best part about Nest is that it is an open protocol that has Internet Protocol version 6 (IPv6) built in. ##### Devices in Thread The Thread protocol defines the three main types of devices in the network: * Border routers * Routers and router-eligible end devices * Sleepy end devices ##### Border Router Thread has a system with a special type of router called the border router, which provides connectivity from the 802.15.4 network to adjacent networks on different physical layers (e.g., WiFi, ethernet). If one border router fails, another router in the network can assume the role of a border router, ensuring the robustness of the Thread protocol. #####Routers Routers, as the name suggests, provide routing services to the network devices. They are used in commissioning new devices to the network. Generally routers are always active, but they can downgrade to become REEDs (Router-Eligible End Devices). These devices are not used in routing or data transfer in the Thread network but as a redundant end point that can be called to assume the role of a router when needed. ##### Sleepy End Devices These are the end points of a Thread network, also called host devices. Host devices are the individual IP-addressed functional equipment like thermostats, security cameras, heaters, etc. These devices can also be referred to as a sleepy child or sleepy node. The router paired directly to the sleepy device is called the parent. The sleepy devices (end points) spend most of their time in the sleep mode and only wake up to transmit data. They only communicate through the parent device (e.g., the Nest thermostat is a sleepy end device). A typical send cycle for a device might be: * Wake from sleep mode. * Perform any required startup and radio initialization. * Go into receive mode and check if clear to transmit. * Go into transmit mode. * Transmit data. * Get acknowledgment as applicable. * Sleep. In contrast to WiFi, which uses infrastructure mode, Thread uses the ad-hoc mode of networking. ##### Advantages: * IP based, so easier to connect to other IP-based networks. Since it’s based on 802.15.4, existing devices like ZigBee and 6loWPAN can easily migrate to Thread. * No single point of failure by architecture, as it is capable of adjusting to network conditions. It supports full mesh-based network topology. * Low-power operation, as it offers sleeping devices * Secure Note: Although there is no single point of failure by architecture in Thread networks, a single point of failure may exist due to poor network design. ##### Disadvantages: * Not a very DIY-friendly protocol because of its complexity. Aims at the high-volume home-automation market. * Still a very new network protocol that needs time to establish itself As Silicon Labs and NXP are part of the Thread Alliance, they are pushing development boards that support Thread protocol. ### ZigBee https://cdn.sparkfun.com/r/600-600/assets/learn_tutorials/5/3/4/Zigbeelogo.png Zigbee, like thread is an alliance of over 200 companies which have collaborated to develop a robust and simple network for home and industrial automation. #### Zigbee Design Goals Zigbee was created for the sole purpose of serving the home and industrial automation, so the design goals are set in accordance to that: * Low-power * Security * Co-existence with other radio networks which use the ISM band. * Standardization * Low-cost Similar to Thread, ZigBee is built on top of the IEEE 802.15.4 standard. ZigbEE specifications fills in the gap left by the 802.15.4 to create a true mesh network but also supports other topologies like Star and Tree. https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/Zigbee-topologies.png ##### Devices in a Zigbee Network There are three types of devices as defined by the Zigbee protocol: * Zigbee Coordinator * Zigbee Router * Zigbee End Device (Node) ##### Zigbee Coordinator The coordinator is the brains of the Zigbee network, it commissions devices to the network, stores the security keys and also bridges to other networks. There is only one Zigbee Coordinator in any network. #####Zigbee Router Zigbee Networks may have several routers to serve as intermediate routers or to transmit data within the network. ##### Zigbee End Device The end device can only talk to the parent node ( router or coordinator). It cannot talk to other end devices directly. Similar to Thread, these devices are designed by keeping in mind that they spend most of their life times in sleep mode and only wake up to transmit data to the parent. ZigBee assumes the channels from 11-26 in the 2.4GHz radio band used by most radios. The ZigBee channels have been specifically spaced as to co-exist with Wi-Fi channels without interference, if the channel assignments of both the networks are properly. https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/ZigbeeWifi_Coexistence.gif Note: The best spectral usage for both is achieved by setting the Wi-Fi channels to 1, 6, 11 and Zigbee channels to 15, 20, 25. #### Zigbee vs Thread ZigBee standard faced a big challenge when Thread came into existence in 2014. The ZigBee Alliance has then pushed to introduce their newest protocol called the ZigBee 3.0. They have tried to address the areas, where thread and other networks were better alternatives in the home automation space. https://cdn.sparkfun.com/r/600-600/assets/learn_tutorials/5/3/4/ZigBee-3.01.png ZigBee 3.0 came with additional features such as ZigBee RF4CE and ZigBee Green Power. ZigBee RF4CE - was developed to replace the IR remote with radio based remotes. This is aimed at making an universal remote controller that could be used to control your remote and as well as lights, lamps etc. Also this does away with the point and shoot limitation of IR. ZigBee Green Power - was developed as an ultra-low power standard to support energy harvesting devices. It ensures very low power consumption by managing the network as such that these devices can be off for the most time. One major feature that put ZigBee behind thread was IP compatibility. ZigBee 3.0 on the other hand is fully IP compatible. So you can now connect your ZigBee devices to the internet via a router. Advantages: Pretty much the same as thread Disadvantages: Short range, Low data speeds Xbee’s by Digi International are radio communication modules which support the Zigbee Protocol. They can also be loaded with firmwares to support Zigbee Pro and DigiMesh. In the Third and final part, we look into Bluetooth, RFID and NFC. Please check part 3 for continuation. |
| json metadata | {"tags":["internetofthings","cryptocurrency","technology","beyondbitcoin","electronics"],"image":["https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/WifI-logo.png","http://i68.tinypic.com/2z6wkmf.jpg","https://cdn.sparkfun.com/r/600-600/assets/learn_tutorials/5/3/4/Zigbeelogo.png","https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/Zigbee-topologies.png","https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/ZigbeeWifi_Coexistence.gif","https://cdn.sparkfun.com/r/600-600/assets/learn_tutorials/5/3/4/ZigBee-3.01.png"]} |
| parent author | |
| parent permlink | internetofthings |
| permlink | connectivity-of-the-internet-of-things-pt2 |
| title | Connectivity of the Internet of Things (Pt2) |
| Transaction Info | Block #5313778/Trx 8ed6e80afa48110c0fff4c90a7832848329b9428 |
View Raw JSON Data
{
"block": 5313778,
"op": [
"comment",
{
"author": "thnass",
"body": "### WiFi\nhttps://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/WifI-logo.png\nWiFi is one of the most common communication protocols. You probably couldn’t imagine your life without it. From the comfort of our homes to classrooms, cafés and airports, we see WiFi everywhere. The extent of WiFi’s influence in our lives has been so great that now it harbors a source of good SSID puns like this! (Sometimes, mostly they’re bad.)\nhttps://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/Network-names_6.png\nWiFi essentially uses an infrastructure network, which additionally supports ad-hoc networking in infrastructure mode.\n\nInfrastructure mode of wireless communication provides a bridge to other networks, medium access control and forwarding. The network handling functions are placed into the access point (router), and the clients can remain simple (in context of network).\n\nAlso, WiFi is a star-based network. The communication goes from wireless nodes (devices) to a wireless access point (router or network controller).\n\nThe current standard being used is 802.11ac, which was released in 2013, although the version 802.11n, which was released in 2009, is still prevalent. The 802.11ac offers speeds up to 800Mbit/s whereas 802.11n offered up to 150Mbits/s.\n\nYou might have also seen devices that have even older standards of 802.11a/b/g, which are now called legacy devices. However, since WiFi has downward compatibility, old devices continue to work with devices that have new standards.\n\nThe range of your device’s WiFi depends on a few factors:\n\n * Which WiFi standard the device is running. The latest standards obviously offer more range than the older versions.\n * Physical obstructions like walls also play a critical role in determining the range. Therefore, in open spaces the range of the WiFi network would be more than in enclosed spaces with walls and other interfering objects.\n\n>To address the weakness of WiFi over other low-powered technologies, an activity was started to standardize low-power WiFi (IEEE 802.11ah). The development of this protocol is being worked on, but its worldwide adaptation is doubtful. One of the main reasons is this is not backward compatible to the existing 802.11bgn networks.\n\n##### Advantages of WiFi:\n\n * WiFi has a decent range coverage and can penetrate walls and other obstacles in the way.\n * Adding and removing devices in a WiFi network is a piece of cake.\n\n##### Disadvantages of WiFi:\n\n * Obviously, the lack of wires comes at a cost of lower bandwidth. The radio waves of the network might interfere with other equipment.\n * Most importantly, security of WiFi is weaker than its wired counterparts\n\nNow thinking about your project, WiFi is ideal when we want to set up a quick connection between our device (should be WiFi compatible) and the internet. WiFi is designed around the goal of keeping its power consumption limited, so you can run your project on a dedicated battery as well. WiFi should be used when you do not care much about how and when exactly your device should connect and communicate with your server and all you are looking for is hassle-free connection to the internet.\n\n### Thread\n\nThread is an open standard for reliable, cost-effective, low-power, wireless D2D (device to device) communication. It was designed specifically for connected home applications.\n\nIt came into existence in 2014, when the Thread Group was formed. It now has big organizations like Google, Samsung, Qualcomm, and ARM to design and develop the Thread protocol.\n\nhttp://i68.tinypic.com/2z6wkmf.jpg\n\nNest uses Thread network for its Thermostat and Nest Cam products. Thread is designed while keeping in mind the home automation space – to have devices set up and connect easily, have low power consumption for longer battery life and be secure!\n\nIt is based on the standard 802.15.4 (6loWPAN) architecture. The best part about Nest is that it is an open protocol that has Internet Protocol version 6 (IPv6) built in.\n\n##### Devices in Thread\nThe Thread protocol defines the three main types of devices in the network:\n\n * Border routers\n * Routers and router-eligible end devices\n * Sleepy end devices\n\n##### Border Router\nThread has a system with a special type of router called the border router, which provides connectivity from the 802.15.4 network to adjacent networks on different physical layers (e.g., WiFi, ethernet). If one border router fails, another router in the network can assume the role of a border router, ensuring the robustness of the Thread protocol.\n\n#####Routers\nRouters, as the name suggests, provide routing services to the network devices. They are used in commissioning new devices to the network. Generally routers are always active, but they can downgrade to become REEDs (Router-Eligible End Devices). These devices are not used in routing or data transfer in the Thread network but as a redundant end point that can be called to assume the role of a router when needed.\n\n##### Sleepy End Devices\nThese are the end points of a Thread network, also called host devices. Host devices are the individual IP-addressed functional equipment like thermostats, security cameras, heaters, etc. These devices can also be referred to as a sleepy child or sleepy node. The router paired directly to the sleepy device is called the parent. The sleepy devices (end points) spend most of their time in the sleep mode and only wake up to transmit data. They only communicate through the parent device (e.g., the Nest thermostat is a sleepy end device).\nA typical send cycle for a device might be:\n\n * Wake from sleep mode.\n * Perform any required startup and radio initialization.\n * Go into receive mode and check if clear to transmit.\n * Go into transmit mode.\n * Transmit data.\n * Get acknowledgment as applicable.\n * Sleep.\n\nIn contrast to WiFi, which uses infrastructure mode, Thread uses the ad-hoc mode of networking.\n\n##### Advantages:\n * IP based, so easier to connect to other IP-based networks. Since it’s based on 802.15.4, existing devices like ZigBee and 6loWPAN can easily migrate to Thread.\n * No single point of failure by architecture, as it is capable of adjusting to network conditions. It supports full mesh-based network topology.\n * Low-power operation, as it offers sleeping devices\n * Secure\n\nNote: Although there is no single point of failure by architecture in Thread networks, a single point of failure may exist due to poor network design.\n\n##### Disadvantages:\n * Not a very DIY-friendly protocol because of its complexity. Aims at the high-volume home-automation market.\n * Still a very new network protocol that needs time to establish itself\n\nAs Silicon Labs and NXP are part of the Thread Alliance, they are pushing development boards that support Thread protocol.\n\n### ZigBee\nhttps://cdn.sparkfun.com/r/600-600/assets/learn_tutorials/5/3/4/Zigbeelogo.png\nZigbee, like thread is an alliance of over 200 companies which have collaborated to develop a robust and simple network for home and industrial automation.\n\n#### Zigbee Design Goals\n\nZigbee was created for the sole purpose of serving the home and industrial automation, so the design goals are set in accordance to that:\n\n * Low-power\n * Security\n * Co-existence with other radio networks which use the ISM band.\n * Standardization\n * Low-cost\n\nSimilar to Thread, ZigBee is built on top of the IEEE 802.15.4 standard.\n\nZigbEE specifications fills in the gap left by the 802.15.4 to create a true mesh network but also supports other topologies like Star and Tree.\nhttps://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/Zigbee-topologies.png\n\n##### Devices in a Zigbee Network\n\nThere are three types of devices as defined by the Zigbee protocol:\n\n * Zigbee Coordinator\n * Zigbee Router\n * Zigbee End Device (Node)\n\n##### Zigbee Coordinator\n\nThe coordinator is the brains of the Zigbee network, it commissions devices to the network, stores the security keys and also bridges to other networks. There is only one Zigbee Coordinator in any network.\n\n#####Zigbee Router\n\nZigbee Networks may have several routers to serve as intermediate routers or to transmit data within the network.\n\n##### Zigbee End Device\n\nThe end device can only talk to the parent node ( router or coordinator). It cannot talk to other end devices directly. Similar to Thread, these devices are designed by keeping in mind that they spend most of their life times in sleep mode and only wake up to transmit data to the parent.\n\nZigBee assumes the channels from 11-26 in the 2.4GHz radio band used by most radios. The ZigBee channels have been specifically spaced as to co-exist with Wi-Fi channels without interference, if the channel assignments of both the networks are properly.\nhttps://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/ZigbeeWifi_Coexistence.gif\nNote: The best spectral usage for both is achieved by setting the Wi-Fi channels to 1, 6, 11 and Zigbee channels to 15, 20, 25.\n\n#### Zigbee vs Thread\n\nZigBee standard faced a big challenge when Thread came into existence in 2014. The ZigBee Alliance has then pushed to introduce their newest protocol called the ZigBee 3.0. They have tried to address the areas, where thread and other networks were better alternatives in the home automation space.\nhttps://cdn.sparkfun.com/r/600-600/assets/learn_tutorials/5/3/4/ZigBee-3.01.png\n\nZigBee 3.0 came with additional features such as ZigBee RF4CE and ZigBee Green Power.\n\nZigBee RF4CE - was developed to replace the IR remote with radio based remotes. This is aimed at making an universal remote controller that could be used to control your remote and as well as lights, lamps etc. Also this does away with the point and shoot limitation of IR.\n\nZigBee Green Power - was developed as an ultra-low power standard to support energy harvesting devices. It ensures very low power consumption by managing the network as such that these devices can be off for the most time.\n\nOne major feature that put ZigBee behind thread was IP compatibility. ZigBee 3.0 on the other hand is fully IP compatible. So you can now connect your ZigBee devices to the internet via a router.\n\nAdvantages: Pretty much the same as thread\n\nDisadvantages: Short range, Low data speeds\n\nXbee’s by Digi International are radio communication modules which support the Zigbee Protocol. They can also be loaded with firmwares to support Zigbee Pro and DigiMesh.\n\nIn the Third and final part, we look into Bluetooth, RFID and NFC.\nPlease check part 3 for continuation.",
"json_metadata": "{\"tags\":[\"internetofthings\",\"cryptocurrency\",\"technology\",\"beyondbitcoin\",\"electronics\"],\"image\":[\"https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/WifI-logo.png\",\"http://i68.tinypic.com/2z6wkmf.jpg\",\"https://cdn.sparkfun.com/r/600-600/assets/learn_tutorials/5/3/4/Zigbeelogo.png\",\"https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/Zigbee-topologies.png\",\"https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/ZigbeeWifi_Coexistence.gif\",\"https://cdn.sparkfun.com/r/600-600/assets/learn_tutorials/5/3/4/ZigBee-3.01.png\"]}",
"parent_author": "",
"parent_permlink": "internetofthings",
"permlink": "connectivity-of-the-internet-of-things-pt2",
"title": "Connectivity of the Internet of Things (Pt2)"
}
],
"op_in_trx": 0,
"timestamp": "2016-09-26T18:29:06",
"trx_id": "8ed6e80afa48110c0fff4c90a7832848329b9428",
"trx_in_block": 3,
"virtual_op": 0
}jillstein2016upvoted (100.00%) @thnass / connectivity-of-the-internet-of-things
jillstein2016upvoted (100.00%) @thnass / connectivity-of-the-internet-of-things
| author | thnass |
| permlink | connectivity-of-the-internet-of-things |
| voter | jillstein2016 |
| weight | 10000 (100.00%) |
| Transaction Info | Block #5313276/Trx ae0ce2d9ec04350eb5936ad49f059ff00d31d994 |
View Raw JSON Data
{
"block": 5313276,
"op": [
"vote",
{
"author": "thnass",
"permlink": "connectivity-of-the-internet-of-things",
"voter": "jillstein2016",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-09-26T18:04:00",
"trx_id": "ae0ce2d9ec04350eb5936ad49f059ff00d31d994",
"trx_in_block": 4,
"virtual_op": 0
}thnasspublished a new post: connectivity-of-the-internet-of-things
thnasspublished a new post: connectivity-of-the-internet-of-things
| author | thnass |
| body | ## Communication Protocols for Internet of Things https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/network-cables-494648_640.jpg Connectivity, it is one of the main things to keep in mind while developing any Internet-of-Thiongs (IoT) project. The first few questions that pop up in my head when I embark on any new IoT project are: * How do I want it to be connected? * Do I have any power or range constraints? * What would be my data rate? * What network infrastructures are currently available? I am sure a lot of you would have the same questions when starting any IoT project. Sometimes you have an idea about what communication protocol you want to use, but it doesn’t hurt to do your research and make sure that would be the most suitable for your application. Fortunately, there are a bunch of network infrastructures and communication protocols available. Unfortunately, there are so many that they might render you confused. In this tutorial, we will discuss all (well, most) of the popular communication protocols and how to pick the most suitable one for your project. We will also go into detail about the pros and cons of each: 1. WiFi 2. Thread 3. ZigBee 4. Bluetooth 5. RFID and NFC This is not the full list of connection types, but these will help you get started with most any IoT project. ## Network Topology It is important to understand the various network protocols we will mention. Network topology is the way in which various elements are arranged in any network. It defines physically or logically the structure of the network. I like to view it as a pictorial representation of the network elements and how data moves through them. https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/508px-NetworkTopologies.svg.png Again, there are a bunch of possible network topologies, but we will keep our scope limited to the ones you would see most often when dealing with IoT-based communication protocols: 1. Point to Point (P2P) 2. Star 3. Mesh 4. Hybrid #### Point to Point https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/StringPhone.jpg P2P is the simplest topology and has a permanent link between two endpoints. The simplest example of P2P would be the connection in the paper cup-and-string telephones that you might have had fun with as kids, where two nodes (or endpoints) have a dedicated channel for communication. Using switching technologies, P2P can be set up dynamically. Switched P2P topology was the basis of the early telephony. #### Star https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/StarNetwork.svg.png In the star network configuration, every node (endpoint) connects to a single central device. The nodes cannot directly communicate with each other; they communicate through the central device. The central device acts as a server, whereas the nodes act as the clients. This is one of the most common configurations and one of the easiest to set up. It is simple to add and remove devices without disrupting the network. The biggest challenge with this kind of network is it has a single point of failure (i.e., the central computer); if the central computer fails, the network fails. #### Mesh https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/NetworkTopology-FullyConnected__1_.png https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/NetworkTopology-Mesh.svg__1_.png Mesh is the type of network where each node is connected to every other node. A mesh network provides a high amount of redundancy when it comes to network links. Even if one link fails, the nodes can communicate using another link. This is not the most commonly used network topology for obvious reasons of increased costs to establish the redundant links and the complicated nature of the network. #### Hybrid Hybrid networks, as the name suggests, are combinations of two or more basic network topologies. It could be a star-mesh network or a star-ring network. Hybrid networks prove to be more flexible and reliable, as they come with the best of both worlds. But at the same time, they have increased complexity, which makes them expensive to set up and difficult to manage. However, hybrids have their benefits when we require a network with the capabilities of more than one network topology. ## Infrastructure and Ad-hoc Networks Since we are going to talk about wireless networks today, we need to discuss the two basic modes (also referred to as topologies) in which wireless networks operate. ##### Infrastructure and Ad-hoc Networks https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/network-infrastructure-vs-a.png Infrastructure mode is when the wireless network requires a physical structure to support it. This essentially means there should be a medium handling the network functions, creating an infrastructure around which the network sustains. It performs these typical functions: * Providing access to other networks * Forwarding * Medium access control In infrastructure-based wireless networks, the communication takes place between the wireless nodes (i.e., endpoints in the network such as your computer, your phone, etc.) and the access points (i.e., the router) only. There can be more than one access point on the same network handling different wireless nodes. A typical example of an infrastructure network would be cellular phone networks. They have to have a set infrastructure (i.e., network towers) to function. When to use an infrastructure network: * If you can easily add more access points to boost the range * If you want to set up a more permanent network * If you will need to bridge to other types of networks (e.g., you can connect to a wired network if required) > The one major downfall with infrastructure networks is that they are costly and time consuming to set up once. So, if you need your device to operate in remote areas where the infrastructure is weak or nonexistent, you cannot rely on infrastructure networks. Ad-hoc wireless networks, on the other hand, do not require a set infrastructure to work. In ad-hoc networks, each node can communicate with other nodes, so no access point that provides access control is required. Whereas the routing in infrastructure networks is taken care of by the access point, in ad-hoc networks the nodes in the network take care of routing. Routing is to find the best possible path between the source and destination nodes to transfer data. All the individual nodes in an ad-hoc network maintain a routing table, which contains the information about the other nodes. As the nature of the ad-hoc network is dynamic, this results in ever-changing router tables. One important thing to note is that an ad-hoc network is asymmetric by nature, meaning the path of data upload and download between two nodes in the network may be different. A typical example of an ad-hoc network is connecting two or more laptops (or other supported devices) to each other directly without any central access point, either wirelessly or using a cable. When to use an ad-hoc network: * If you want to quickly set up a peer-to-peer (P2P) network between two devices * When creating a quick temporary network * If there is no network infrastructure set up in the area (ad-hoc is the only network mode that can be used in areas like this) As the routing is handled by each node in the network, this uses more resources; as the number of devices connected in an ad-hoc network increases, the network interference increases, which may lead to slower networks. > As the routing is handled by each node in the network, this uses more resources; as the number of devices connected in an ad-hoc network increases, the network interference increases, which may lead to slower networks. In the second part, we look into WIFI, Thread and ZigBee. Please check part 2 for continuation. |
| json metadata | {"tags":["internetofthings","cryptocurrency","technology","beyondbitcoin","inter"],"image":["https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/network-cables-494648_640.jpg","https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/508px-NetworkTopologies.svg.png","https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/StringPhone.jpg","https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/StarNetwork.svg.png","https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/NetworkTopology-FullyConnected__1_.png","https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/network-infrastructure-vs-a.png"]} |
| parent author | |
| parent permlink | inter |
| permlink | connectivity-of-the-internet-of-things |
| title | Connectivity of the Internet of Things |
| Transaction Info | Block #5313110/Trx 2e42cad6bc947b257ca7fe18c4b25d308cf15238 |
View Raw JSON Data
{
"block": 5313110,
"op": [
"comment",
{
"author": "thnass",
"body": "## Communication Protocols for Internet of Things\nhttps://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/network-cables-494648_640.jpg\nConnectivity, it is one of the main things to keep in mind while developing any Internet-of-Thiongs (IoT) project.\nThe first few questions that pop up in my head when I embark on any new IoT project are:\n * How do I want it to be connected?\n * Do I have any power or range constraints?\n * What would be my data rate?\n * What network infrastructures are currently available?\nI am sure a lot of you would have the same questions when starting any IoT project. Sometimes you have an idea about what communication protocol you want to use, but it doesn’t hurt to do your research and make sure that would be the most suitable for your application.\n\nFortunately, there are a bunch of network infrastructures and communication protocols available. Unfortunately, there are so many that they might render you confused.\n\nIn this tutorial, we will discuss all (well, most) of the popular communication protocols and how to pick the most suitable one for your project. We will also go into detail about the pros and cons of each:\n\n 1. WiFi\n 2. Thread\n 3. ZigBee\n 4. Bluetooth\n 5. RFID and NFC\nThis is not the full list of connection types, but these will help you get started with most any IoT project.\n\n## Network Topology\n\nIt is important to understand the various network protocols we will mention.\n\nNetwork topology is the way in which various elements are arranged in any network. It defines physically or logically the structure of the network. I like to view it as a pictorial representation of the network elements and how data moves through them.\nhttps://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/508px-NetworkTopologies.svg.png\nAgain, there are a bunch of possible network topologies, but we will keep our scope limited to the ones you would see most often when dealing with IoT-based communication protocols:\n\n 1. Point to Point (P2P)\n 2. Star\n 3. Mesh\n 4. Hybrid\n\n#### Point to Point\nhttps://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/StringPhone.jpg\nP2P is the simplest topology and has a permanent link between two endpoints. The simplest example of P2P would be the connection in the paper cup-and-string telephones that you might have had fun with as kids, where two nodes (or endpoints) have a dedicated channel for communication. Using switching technologies, P2P can be set up dynamically. Switched P2P topology was the basis of the early telephony.\n\n#### Star\nhttps://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/StarNetwork.svg.png\nIn the star network configuration, every node (endpoint) connects to a single central device. The nodes cannot directly communicate with each other; they communicate through the central device. The central device acts as a server, whereas the nodes act as the clients. This is one of the most common configurations and one of the easiest to set up. It is simple to add and remove devices without disrupting the network. The biggest challenge with this kind of network is it has a single point of failure (i.e., the central computer); if the central computer fails, the network fails.\n\n#### Mesh\nhttps://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/NetworkTopology-FullyConnected__1_.png\nhttps://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/NetworkTopology-Mesh.svg__1_.png\nMesh is the type of network where each node is connected to every other node. A mesh network provides a high amount of redundancy when it comes to network links. Even if one link fails, the nodes can communicate using another link. This is not the most commonly used network topology for obvious reasons of increased costs to establish the redundant links and the complicated nature of the network.\n\n#### Hybrid\n\nHybrid networks, as the name suggests, are combinations of two or more basic network topologies. It could be a star-mesh network or a star-ring network. Hybrid networks prove to be more flexible and reliable, as they come with the best of both worlds. But at the same time, they have increased complexity, which makes them expensive to set up and difficult to manage. However, hybrids have their benefits when we require a network with the capabilities of more than one network topology.\n\n## Infrastructure and Ad-hoc Networks\n\nSince we are going to talk about wireless networks today, we need to discuss the two basic modes (also referred to as topologies) in which wireless networks operate.\n##### Infrastructure and Ad-hoc Networks\nhttps://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/network-infrastructure-vs-a.png\nInfrastructure mode is when the wireless network requires a physical structure to support it. This essentially means there should be a medium handling the network functions, creating an infrastructure around which the network sustains.\n\nIt performs these typical functions:\n\n * Providing access to other networks\n * Forwarding\n * Medium access control\n\nIn infrastructure-based wireless networks, the communication takes place between the wireless nodes (i.e., endpoints in the network such as your computer, your phone, etc.) and the access points (i.e., the router) only.\n\nThere can be more than one access point on the same network handling different wireless nodes.\n\nA typical example of an infrastructure network would be cellular phone networks. They have to have a set infrastructure (i.e., network towers) to function.\n\nWhen to use an infrastructure network:\n\n * If you can easily add more access points to boost the range\n * If you want to set up a more permanent network\n * If you will need to bridge to other types of networks (e.g., you can connect to a wired network if required)\n\n> The one major downfall with infrastructure networks is that they are costly and time consuming to set up once. So, if you need your device to operate in remote areas where the infrastructure is weak or nonexistent, you cannot rely on infrastructure networks.\n\nAd-hoc wireless networks, on the other hand, do not require a set infrastructure to work. In ad-hoc networks, each node can communicate with other nodes, so no access point that provides access control is required.\n\nWhereas the routing in infrastructure networks is taken care of by the access point, in ad-hoc networks the nodes in the network take care of routing.\n\nRouting is to find the best possible path between the source and destination nodes to transfer data.\n\nAll the individual nodes in an ad-hoc network maintain a routing table, which contains the information about the other nodes. As the nature of the ad-hoc network is dynamic, this results in ever-changing router tables. One important thing to note is that an ad-hoc network is asymmetric by nature, meaning the path of data upload and download between two nodes in the network may be different.\n\nA typical example of an ad-hoc network is connecting two or more laptops (or other supported devices) to each other directly without any central access point, either wirelessly or using a cable.\n\nWhen to use an ad-hoc network:\n\n * If you want to quickly set up a peer-to-peer (P2P) network between two devices\n * When creating a quick temporary network\n * If there is no network infrastructure set up in the area (ad-hoc is the only network mode that can be used in areas like this)\n\nAs the routing is handled by each node in the network, this uses more resources; as the number of devices connected in an ad-hoc network increases, the network interference increases, which may lead to slower networks.\n\n> As the routing is handled by each node in the network, this uses more resources; as the number of devices connected in an ad-hoc network increases, the network interference increases, which may lead to slower networks.\n\nIn the second part, we look into WIFI, Thread and ZigBee.\nPlease check part 2 for continuation.",
"json_metadata": "{\"tags\":[\"internetofthings\",\"cryptocurrency\",\"technology\",\"beyondbitcoin\",\"inter\"],\"image\":[\"https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/network-cables-494648_640.jpg\",\"https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/508px-NetworkTopologies.svg.png\",\"https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/StringPhone.jpg\",\"https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/StarNetwork.svg.png\",\"https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/NetworkTopology-FullyConnected__1_.png\",\"https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/network-infrastructure-vs-a.png\"]}",
"parent_author": "",
"parent_permlink": "inter",
"permlink": "connectivity-of-the-internet-of-things",
"title": "Connectivity of the Internet of Things"
}
],
"op_in_trx": 0,
"timestamp": "2016-09-26T17:55:42",
"trx_id": "2e42cad6bc947b257ca7fe18c4b25d308cf15238",
"trx_in_block": 4,
"virtual_op": 0
}thnassupvoted (100.00%) @thnass / connectivity-of-the-internet-of-things
thnassupvoted (100.00%) @thnass / connectivity-of-the-internet-of-things
| author | thnass |
| permlink | connectivity-of-the-internet-of-things |
| voter | thnass |
| weight | 10000 (100.00%) |
| Transaction Info | Block #5313057/Trx 9d297e4c9d77bcb5aa26f4e3398549e22ed1b99d |
View Raw JSON Data
{
"block": 5313057,
"op": [
"vote",
{
"author": "thnass",
"permlink": "connectivity-of-the-internet-of-things",
"voter": "thnass",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-09-26T17:53:03",
"trx_id": "9d297e4c9d77bcb5aa26f4e3398549e22ed1b99d",
"trx_in_block": 7,
"virtual_op": 0
}thnasspublished a new post: connectivity-of-the-internet-of-things
thnasspublished a new post: connectivity-of-the-internet-of-things
| author | thnass |
| body | ## Communication Protocols for Internet of Things https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/network-cables-494648_640.jpg Connectivity, it is one of the main things to keep in mind while developing any Internet-of-Thiongs (IoT) project. The first few questions that pop up in my head when I embark on any new IoT project are: * How do I want it to be connected? * Do I have any power or range constraints? * What would be my data rate? * What network infrastructures are currently available? I am sure a lot of you would have the same questions when starting any IoT project. Sometimes you have an idea about what communication protocol you want to use, but it doesn’t hurt to do your research and make sure that would be the most suitable for your application. Fortunately, there are a bunch of network infrastructures and communication protocols available. Unfortunately, there are so many that they might render you confused. In this tutorial, we will discuss all (well, most) of the popular communication protocols and how to pick the most suitable one for your project. We will also go into detail about the pros and cons of each: 1. WiFi 2. Thread 3. ZigBee 4. Bluetooth 5. RFID and NFC This is not the full list of connection types, but these will help you get started with most any IoT project. ## Network Topology It is important to understand the various network protocols we will mention. Network topology is the way in which various elements are arranged in any network. It defines physically or logically the structure of the network. I like to view it as a pictorial representation of the network elements and how data moves through them. https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/508px-NetworkTopologies.svg.png Again, there are a bunch of possible network topologies, but we will keep our scope limited to the ones you would see most often when dealing with IoT-based communication protocols: 1. Point to Point (P2P) 2. Star 3. Mesh 4. Hybrid #### Point to Point https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/StringPhone.jpg P2P is the simplest topology and has a permanent link between two endpoints. The simplest example of P2P would be the connection in the paper cup-and-string telephones that you might have had fun with as kids, where two nodes (or endpoints) have a dedicated channel for communication. Using switching technologies, P2P can be set up dynamically. Switched P2P topology was the basis of the early telephony. #### Star https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/StarNetwork.svg.png In the star network configuration, every node (endpoint) connects to a single central device. The nodes cannot directly communicate with each other; they communicate through the central device. The central device acts as a server, whereas the nodes act as the clients. This is one of the most common configurations and one of the easiest to set up. It is simple to add and remove devices without disrupting the network. The biggest challenge with this kind of network is it has a single point of failure (i.e., the central computer); if the central computer fails, the network fails. #### Mesh https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/NetworkTopology-FullyConnected__1_.png https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/NetworkTopology-Mesh.svg__1_.png Mesh is the type of network where each node is connected to every other node. A mesh network provides a high amount of redundancy when it comes to network links. Even if one link fails, the nodes can communicate using another link. This is not the most commonly used network topology for obvious reasons of increased costs to establish the redundant links and the complicated nature of the network. #### Hybrid Hybrid networks, as the name suggests, are combinations of two or more basic network topologies. It could be a star-mesh network or a star-ring network. Hybrid networks prove to be more flexible and reliable, as they come with the best of both worlds. But at the same time, they have increased complexity, which makes them expensive to set up and difficult to manage. However, hybrids have their benefits when we require a network with the capabilities of more than one network topology. ## Infrastructure and Ad-hoc Networks Since we are going to talk about wireless networks today, we need to discuss the two basic modes (also referred to as topologies) in which wireless networks operate. ##### Infrastructure and Ad-hoc Networks https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/network-infrastructure-vs-a.png Infrastructure mode is when the wireless network requires a physical structure to support it. This essentially means there should be a medium handling the network functions, creating an infrastructure around which the network sustains. It performs these typical functions: * Providing access to other networks * Forwarding * Medium access control In infrastructure-based wireless networks, the communication takes place between the wireless nodes (i.e., endpoints in the network such as your computer, your phone, etc.) and the access points (i.e., the router) only. There can be more than one access point on the same network handling different wireless nodes. A typical example of an infrastructure network would be cellular phone networks. They have to have a set infrastructure (i.e., network towers) to function. When to use an infrastructure network: * If you can easily add more access points to boost the range * If you want to set up a more permanent network * If you will need to bridge to other types of networks (e.g., you can connect to a wired network if required) > The one major downfall with infrastructure networks is that they are costly and time consuming to set up once. So, if you need your device to operate in remote areas where the infrastructure is weak or nonexistent, you cannot rely on infrastructure networks. Ad-hoc wireless networks, on the other hand, do not require a set infrastructure to work. In ad-hoc networks, each node can communicate with other nodes, so no access point that provides access control is required. Whereas the routing in infrastructure networks is taken care of by the access point, in ad-hoc networks the nodes in the network take care of routing. Routing is to find the best possible path between the source and destination nodes to transfer data. All the individual nodes in an ad-hoc network maintain a routing table, which contains the information about the other nodes. As the nature of the ad-hoc network is dynamic, this results in ever-changing router tables. One important thing to note is that an ad-hoc network is asymmetric by nature, meaning the path of data upload and download between two nodes in the network may be different. A typical example of an ad-hoc network is connecting two or more laptops (or other supported devices) to each other directly without any central access point, either wirelessly or using a cable. When to use an ad-hoc network: * If you want to quickly set up a peer-to-peer (P2P) network between two devices * When creating a quick temporary network * If there is no network infrastructure set up in the area (ad-hoc is the only network mode that can be used in areas like this) As the routing is handled by each node in the network, this uses more resources; as the number of devices connected in an ad-hoc network increases, the network interference increases, which may lead to slower networks. > As the routing is handled by each node in the network, this uses more resources; as the number of devices connected in an ad-hoc network increases, the network interference increases, which may lead to slower networks. In the second part, we look into WIFI, Thread and ZigBee. Please check part 2 for continuation. |
| json metadata | {"tags":["inter"],"image":["https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/network-cables-494648_640.jpg","https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/508px-NetworkTopologies.svg.png","https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/StringPhone.jpg","https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/StarNetwork.svg.png","https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/NetworkTopology-FullyConnected__1_.png","https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/network-infrastructure-vs-a.png"]} |
| parent author | |
| parent permlink | inter |
| permlink | connectivity-of-the-internet-of-things |
| title | Connectivity of the Internet of Things |
| Transaction Info | Block #5313057/Trx 9d297e4c9d77bcb5aa26f4e3398549e22ed1b99d |
View Raw JSON Data
{
"block": 5313057,
"op": [
"comment",
{
"author": "thnass",
"body": "## Communication Protocols for Internet of Things\nhttps://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/network-cables-494648_640.jpg\nConnectivity, it is one of the main things to keep in mind while developing any Internet-of-Thiongs (IoT) project.\nThe first few questions that pop up in my head when I embark on any new IoT project are:\n * How do I want it to be connected?\n * Do I have any power or range constraints?\n * What would be my data rate?\n * What network infrastructures are currently available?\nI am sure a lot of you would have the same questions when starting any IoT project. Sometimes you have an idea about what communication protocol you want to use, but it doesn’t hurt to do your research and make sure that would be the most suitable for your application.\n\nFortunately, there are a bunch of network infrastructures and communication protocols available. Unfortunately, there are so many that they might render you confused.\n\nIn this tutorial, we will discuss all (well, most) of the popular communication protocols and how to pick the most suitable one for your project. We will also go into detail about the pros and cons of each:\n\n 1. WiFi\n 2. Thread\n 3. ZigBee\n 4. Bluetooth\n 5. RFID and NFC\nThis is not the full list of connection types, but these will help you get started with most any IoT project.\n\n## Network Topology\n\nIt is important to understand the various network protocols we will mention.\n\nNetwork topology is the way in which various elements are arranged in any network. It defines physically or logically the structure of the network. I like to view it as a pictorial representation of the network elements and how data moves through them.\nhttps://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/508px-NetworkTopologies.svg.png\nAgain, there are a bunch of possible network topologies, but we will keep our scope limited to the ones you would see most often when dealing with IoT-based communication protocols:\n\n 1. Point to Point (P2P)\n 2. Star\n 3. Mesh\n 4. Hybrid\n\n#### Point to Point\nhttps://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/StringPhone.jpg\nP2P is the simplest topology and has a permanent link between two endpoints. The simplest example of P2P would be the connection in the paper cup-and-string telephones that you might have had fun with as kids, where two nodes (or endpoints) have a dedicated channel for communication. Using switching technologies, P2P can be set up dynamically. Switched P2P topology was the basis of the early telephony.\n\n#### Star\nhttps://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/StarNetwork.svg.png\nIn the star network configuration, every node (endpoint) connects to a single central device. The nodes cannot directly communicate with each other; they communicate through the central device. The central device acts as a server, whereas the nodes act as the clients. This is one of the most common configurations and one of the easiest to set up. It is simple to add and remove devices without disrupting the network. The biggest challenge with this kind of network is it has a single point of failure (i.e., the central computer); if the central computer fails, the network fails.\n\n#### Mesh\nhttps://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/NetworkTopology-FullyConnected__1_.png\nhttps://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/NetworkTopology-Mesh.svg__1_.png\nMesh is the type of network where each node is connected to every other node. A mesh network provides a high amount of redundancy when it comes to network links. Even if one link fails, the nodes can communicate using another link. This is not the most commonly used network topology for obvious reasons of increased costs to establish the redundant links and the complicated nature of the network.\n\n#### Hybrid\n\nHybrid networks, as the name suggests, are combinations of two or more basic network topologies. It could be a star-mesh network or a star-ring network. Hybrid networks prove to be more flexible and reliable, as they come with the best of both worlds. But at the same time, they have increased complexity, which makes them expensive to set up and difficult to manage. However, hybrids have their benefits when we require a network with the capabilities of more than one network topology.\n\n## Infrastructure and Ad-hoc Networks\n\nSince we are going to talk about wireless networks today, we need to discuss the two basic modes (also referred to as topologies) in which wireless networks operate.\n##### Infrastructure and Ad-hoc Networks\nhttps://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/network-infrastructure-vs-a.png\nInfrastructure mode is when the wireless network requires a physical structure to support it. This essentially means there should be a medium handling the network functions, creating an infrastructure around which the network sustains.\n\nIt performs these typical functions:\n\n * Providing access to other networks\n * Forwarding\n * Medium access control\n\nIn infrastructure-based wireless networks, the communication takes place between the wireless nodes (i.e., endpoints in the network such as your computer, your phone, etc.) and the access points (i.e., the router) only.\n\nThere can be more than one access point on the same network handling different wireless nodes.\n\nA typical example of an infrastructure network would be cellular phone networks. They have to have a set infrastructure (i.e., network towers) to function.\n\nWhen to use an infrastructure network:\n\n * If you can easily add more access points to boost the range\n * If you want to set up a more permanent network\n * If you will need to bridge to other types of networks (e.g., you can connect to a wired network if required)\n\n> The one major downfall with infrastructure networks is that they are costly and time consuming to set up once. So, if you need your device to operate in remote areas where the infrastructure is weak or nonexistent, you cannot rely on infrastructure networks.\n\nAd-hoc wireless networks, on the other hand, do not require a set infrastructure to work. In ad-hoc networks, each node can communicate with other nodes, so no access point that provides access control is required.\n\nWhereas the routing in infrastructure networks is taken care of by the access point, in ad-hoc networks the nodes in the network take care of routing.\n\nRouting is to find the best possible path between the source and destination nodes to transfer data.\n\nAll the individual nodes in an ad-hoc network maintain a routing table, which contains the information about the other nodes. As the nature of the ad-hoc network is dynamic, this results in ever-changing router tables. One important thing to note is that an ad-hoc network is asymmetric by nature, meaning the path of data upload and download between two nodes in the network may be different.\n\nA typical example of an ad-hoc network is connecting two or more laptops (or other supported devices) to each other directly without any central access point, either wirelessly or using a cable.\n\nWhen to use an ad-hoc network:\n\n * If you want to quickly set up a peer-to-peer (P2P) network between two devices\n * When creating a quick temporary network\n * If there is no network infrastructure set up in the area (ad-hoc is the only network mode that can be used in areas like this)\n\nAs the routing is handled by each node in the network, this uses more resources; as the number of devices connected in an ad-hoc network increases, the network interference increases, which may lead to slower networks.\n\n> As the routing is handled by each node in the network, this uses more resources; as the number of devices connected in an ad-hoc network increases, the network interference increases, which may lead to slower networks.\n\nIn the second part, we look into WIFI, Thread and ZigBee.\nPlease check part 2 for continuation.",
"json_metadata": "{\"tags\":[\"inter\"],\"image\":[\"https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/network-cables-494648_640.jpg\",\"https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/508px-NetworkTopologies.svg.png\",\"https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/StringPhone.jpg\",\"https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/StarNetwork.svg.png\",\"https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/NetworkTopology-FullyConnected__1_.png\",\"https://cdn.sparkfun.com/assets/learn_tutorials/5/3/4/network-infrastructure-vs-a.png\"]}",
"parent_author": "",
"parent_permlink": "inter",
"permlink": "connectivity-of-the-internet-of-things",
"title": "Connectivity of the Internet of Things"
}
],
"op_in_trx": 0,
"timestamp": "2016-09-26T17:53:03",
"trx_id": "9d297e4c9d77bcb5aa26f4e3398549e22ed1b99d",
"trx_in_block": 7,
"virtual_op": 0
}| author | azguard |
| permlink | pre-ann-fame-famecoin-viral-photo-sharing-on-blockchain-with-tippings-etc |
| voter | thnass |
| weight | 10000 (100.00%) |
| Transaction Info | Block #5131495/Trx 6026e8613cd03e5f08dc1dea072aebac87e188b3 |
View Raw JSON Data
{
"block": 5131495,
"op": [
"vote",
{
"author": "azguard",
"permlink": "pre-ann-fame-famecoin-viral-photo-sharing-on-blockchain-with-tippings-etc",
"voter": "thnass",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-09-20T09:56:03",
"trx_id": "6026e8613cd03e5f08dc1dea072aebac87e188b3",
"trx_in_block": 3,
"virtual_op": 0
}thnassremoved vote from (0.00%) @robrigo / greetings-from-detroit
thnassremoved vote from (0.00%) @robrigo / greetings-from-detroit
| author | robrigo |
| permlink | greetings-from-detroit |
| voter | thnass |
| weight | 0 (0.00%) |
| Transaction Info | Block #3103166/Trx 0547218bc4d9ab22cacce9896e2ae9c21c496d62 |
View Raw JSON Data
{
"block": 3103166,
"op": [
"vote",
{
"author": "robrigo",
"permlink": "greetings-from-detroit",
"voter": "thnass",
"weight": 0
}
],
"op_in_trx": 0,
"timestamp": "2016-07-11T11:39:51",
"trx_id": "0547218bc4d9ab22cacce9896e2ae9c21c496d62",
"trx_in_block": 0,
"virtual_op": 0
}thnassupvoted (100.00%) @robrigo / greetings-from-detroit
thnassupvoted (100.00%) @robrigo / greetings-from-detroit
| author | robrigo |
| permlink | greetings-from-detroit |
| voter | thnass |
| weight | 10000 (100.00%) |
| Transaction Info | Block #3103159/Trx 2ee1cc4d3cbea80ac6dc9e9bef0d58b5ad8590bc |
View Raw JSON Data
{
"block": 3103159,
"op": [
"vote",
{
"author": "robrigo",
"permlink": "greetings-from-detroit",
"voter": "thnass",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2016-07-11T11:39:30",
"trx_id": "2ee1cc4d3cbea80ac6dc9e9bef0d58b5ad8590bc",
"trx_in_block": 2,
"virtual_op": 0
}| active | {"account_auths":[],"key_auths":[["STM7nmtoqKMEUWBuxtuWWU3DFUyeUGGGMEqL1PERzdW4G4Rkq6hgx",1]],"weight_threshold":1} |
| creator | steem |
| fee | 10.000 STEEM |
| json metadata | |
| memo key | STM64WU3dtcfVXsQUVpRyonUifkbDwSENzkBkb4Y6AXBWgU8eMTgC |
| new account name | thnass |
| owner | {"account_auths":[],"key_auths":[["STM5vMwCGwkSfA9Mjq86oGcrHFaLe5yEGjrLCrxe2xvNAec5UsUqU",1]],"weight_threshold":1} |
| posting | {"account_auths":[],"key_auths":[["STM6PosxLZorrCrRKvHQZ178jfDUHxkgTzSq3mnLYcwgf1UdkWsEi",1]],"weight_threshold":1} |
| Transaction Info | Block #3103083/Trx 4af31a24b4315941300149b4e595822733bdb1e0 |
View Raw JSON Data
{
"block": 3103083,
"op": [
"account_create",
{
"active": {
"account_auths": [],
"key_auths": [
[
"STM7nmtoqKMEUWBuxtuWWU3DFUyeUGGGMEqL1PERzdW4G4Rkq6hgx",
1
]
],
"weight_threshold": 1
},
"creator": "steem",
"fee": "10.000 STEEM",
"json_metadata": "",
"memo_key": "STM64WU3dtcfVXsQUVpRyonUifkbDwSENzkBkb4Y6AXBWgU8eMTgC",
"new_account_name": "thnass",
"owner": {
"account_auths": [],
"key_auths": [
[
"STM5vMwCGwkSfA9Mjq86oGcrHFaLe5yEGjrLCrxe2xvNAec5UsUqU",
1
]
],
"weight_threshold": 1
},
"posting": {
"account_auths": [],
"key_auths": [
[
"STM6PosxLZorrCrRKvHQZ178jfDUHxkgTzSq3mnLYcwgf1UdkWsEi",
1
]
],
"weight_threshold": 1
}
}
],
"op_in_trx": 0,
"timestamp": "2016-07-11T11:35:42",
"trx_id": "4af31a24b4315941300149b4e595822733bdb1e0",
"trx_in_block": 0,
"virtual_op": 0
}Manabar
Voting Power100.00%
Downvote Power100.00%
Resource Credits100.00%
Reputation Progress0.00%
{
"voting_manabar": {
"current_mana": "18555092635",
"last_update_time": 1573646733
},
"downvote_manabar": {
"current_mana": "5015053585",
"last_update_time": 1573646733
},
"rc_account": {
"account": "thnass",
"max_rc": "22080963313",
"max_rc_creation_adjustment": {
"amount": "2020748973",
"nai": "@@000000037",
"precision": 6
},
"rc_manabar": {
"current_mana": "21353418487",
"last_update_time": 1573646733
}
}
}Account Metadata
| POSTING JSON METADATA | |
| None | |
| JSON METADATA | |
| None |
{
"posting_json_metadata": {},
"json_metadata": {}
}Auth Keys
Owner
Single Signature
Public Keys
STM5vMwCGwkSfA9Mjq86oGcrHFaLe5yEGjrLCrxe2xvNAec5UsUqU1/1
Active
Single Signature
Public Keys
STM7nmtoqKMEUWBuxtuWWU3DFUyeUGGGMEqL1PERzdW4G4Rkq6hgx1/1
Posting
Single Signature
Public Keys
STM6PosxLZorrCrRKvHQZ178jfDUHxkgTzSq3mnLYcwgf1UdkWsEi1/1
App Permissions
@dtube.app1/1
Memo
STM64WU3dtcfVXsQUVpRyonUifkbDwSENzkBkb4Y6AXBWgU8eMTgC
{
"owner": {
"account_auths": [],
"key_auths": [
[
"STM5vMwCGwkSfA9Mjq86oGcrHFaLe5yEGjrLCrxe2xvNAec5UsUqU",
1
]
],
"weight_threshold": 1
},
"active": {
"account_auths": [],
"key_auths": [
[
"STM7nmtoqKMEUWBuxtuWWU3DFUyeUGGGMEqL1PERzdW4G4Rkq6hgx",
1
]
],
"weight_threshold": 1
},
"posting": {
"account_auths": [
[
"dtube.app",
1
]
],
"key_auths": [
[
"STM6PosxLZorrCrRKvHQZ178jfDUHxkgTzSq3mnLYcwgf1UdkWsEi",
1
]
],
"weight_threshold": 1
},
"memo": "STM64WU3dtcfVXsQUVpRyonUifkbDwSENzkBkb4Y6AXBWgU8eMTgC"
}Witness Votes
0 / 30
No active witness votes.
[]