@mdarweash
25- Serial Entrepreneur - Signed Patent Contract with Dr.Hatem Zaghloul regarding BLE multihop networking protocol patent - Developed/Consulted 30+ Mobile Appli
steemit.com/@mdarweashVOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS0.00%
Net Worth
2.830USD
STEEM
0.000STEEM
SBD
0.005SBD
Own SP
48.752SP
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 | 48.752SP | SP |
| Delegated Out | 0.000SP | SP |
| Delegation In | 0.000SP | SP |
| Effective Power | 48.752SP | SP |
| Reward SP (pending) | 0.000SP | SP |
| SBD | ||
| sbd_balance | 0.005SBD | 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": "79284.310383 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "0.000000 VESTS",
"sbd_balance": "0.005 SBD",
"savings_sbd_balance": "0.000 SBD",
"reward_sbd_balance": "0.000 SBD",
"conversions": []
}Account Info
| name | mdarweash |
| id | 1030027 |
| rank | 42,016 |
| reputation | 167055894 |
| created | 2018-06-08T00:02:51 |
| recovery_account | steem |
| proxy | None |
| post_count | 5 |
| comment_count | 0 |
| lifetime_vote_count | 0 |
| witnesses_voted_for | 0 |
| last_post | 2018-08-27T06:20:18 |
| last_root_post | 2018-08-27T06:20:18 |
| last_vote_time | 1970-01-01T00:00:00 |
| proxied_vsf_votes | 0, 0, 0, 0 |
| can_vote | 1 |
| voting_power | 10,000 |
| delayed_votes | 0 |
| balance | 0.000 STEEM |
| savings_balance | 0.000 STEEM |
| sbd_balance | 0.005 SBD |
| savings_sbd_balance | 0.000 SBD |
| vesting_shares | 79284.310383 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 | 0 |
| to_withdraw | 0 |
| withdraw_routes | 0 |
| savings_withdraw_requests | 0 |
| last_account_recovery | 1970-01-01T00:00:00 |
| reset_account | null |
| last_owner_update | 1970-01-01T00:00:00 |
| last_account_update | 2018-06-08T00:47:33 |
| mined | No |
| sbd_seconds | 0 |
| sbd_last_interest_payment | 1970-01-01T00:00:00 |
| savings_sbd_last_interest_payment | 1970-01-01T00:00:00 |
{
"id": 1030027,
"name": "mdarweash",
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7yWQ5dCydoBCBAGN8pkA9pNgdAC7tE9FrFRTgXA6bRBZDgreW3",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5krVU4jZ34ggHckEbPEAWJzCLGDrnfWKn4X6ykBD1Wye4p4Xxb",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5rK2Wd2UMXqyKk3vqmcHC2MgAsZ5Du7QY5nG5j1i1DWbZ9DDtm",
1
]
]
},
"memo_key": "STM5Rs9q7jYyqPZX44NYXxSQEVhi3kCbaKQMn5hQa1HCNAQA4XV9z",
"json_metadata": "{\"profile\":{\"profile_image\":\"https://cdn.steemitimages.com/DQmRBBFESnca5t7ikMZN9irrNwvZXcobQiKyjvTbwQfvPPb/Mdarweash.JPG\",\"name\":\"MDarweash\",\"about\":\"- Serial Entrepreneur - Signed Patent Contract with Dr.Hatem Zaghloul regarding BLE multihop networking protocol patent - Developed/Consulted 30+ Mobile Appli\",\"location\":\"Kuala Lumpur\"}}",
"posting_json_metadata": "{\"profile\":{\"profile_image\":\"https://cdn.steemitimages.com/DQmRBBFESnca5t7ikMZN9irrNwvZXcobQiKyjvTbwQfvPPb/Mdarweash.JPG\",\"name\":\"MDarweash\",\"about\":\"- Serial Entrepreneur - Signed Patent Contract with Dr.Hatem Zaghloul regarding BLE multihop networking protocol patent - Developed/Consulted 30+ Mobile Appli\",\"location\":\"Kuala Lumpur\"}}",
"proxy": "",
"last_owner_update": "1970-01-01T00:00:00",
"last_account_update": "2018-06-08T00:47:33",
"created": "2018-06-08T00:02:51",
"mined": false,
"recovery_account": "steem",
"last_account_recovery": "1970-01-01T00:00:00",
"reset_account": "null",
"comment_count": 0,
"lifetime_vote_count": 0,
"post_count": 5,
"can_vote": true,
"voting_manabar": {
"current_mana": 10000,
"last_update_time": 1528416171
},
"downvote_manabar": {
"current_mana": 0,
"last_update_time": 1528416171
},
"voting_power": 10000,
"balance": "0.000 STEEM",
"savings_balance": "0.000 STEEM",
"sbd_balance": "0.005 SBD",
"sbd_seconds": "0",
"sbd_seconds_last_update": "2018-06-22T04:01:06",
"sbd_last_interest_payment": "1970-01-01T00:00:00",
"savings_sbd_balance": "0.000 SBD",
"savings_sbd_seconds": "0",
"savings_sbd_seconds_last_update": "1970-01-01T00:00:00",
"savings_sbd_last_interest_payment": "1970-01-01T00:00:00",
"savings_withdraw_requests": 0,
"reward_sbd_balance": "0.000 SBD",
"reward_steem_balance": "0.000 STEEM",
"reward_vesting_balance": "0.000000 VESTS",
"reward_vesting_steem": "0.000 STEEM",
"vesting_shares": "79284.310383 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "0.000000 VESTS",
"vesting_withdraw_rate": "0.000000 VESTS",
"next_vesting_withdrawal": "1969-12-31T23:59:59",
"withdrawn": 0,
"to_withdraw": 0,
"withdraw_routes": 0,
"curation_rewards": 0,
"posting_rewards": 12,
"proxied_vsf_votes": [
0,
0,
0,
0
],
"witnesses_voted_for": 0,
"last_post": "2018-08-27T06:20:18",
"last_root_post": "2018-08-27T06:20:18",
"last_vote_time": "1970-01-01T00:00:00",
"post_bandwidth": 0,
"pending_claimed_accounts": 0,
"vesting_balance": "0.000 STEEM",
"reputation": 167055894,
"transfer_history": [],
"market_history": [],
"post_history": [],
"vote_history": [],
"other_history": [],
"witness_votes": [],
"tags_usage": [],
"guest_bloggers": [],
"rank": 42016
}Withdraw Routes
| Incoming | Outgoing |
|---|---|
Empty | Empty |
{
"incoming": [],
"outgoing": []
}From Date
To Date
2019/06/08 01:32:42
2019/06/08 01:32:42
| parent author | mdarweash |
| parent permlink | choosing-the-right-technology-vs-available-technology-developers |
| author | steemitboard |
| permlink | steemitboard-notify-mdarweash-20190608t013241000z |
| title | |
| body | Congratulations @mdarweash! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/https://steemitboard.com/@mdarweash/birthday1.png</td><td>Happy Birthday! - You are on the Steem blockchain for 1 year!</td></tr></table> <sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@mdarweash) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=mdarweash)_</sub> ###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| Transaction Info | Block #33606400/Trx a02a1fde69b96da8ec2f73d6f7ae42c84a3bade1 |
View Raw JSON Data
{
"trx_id": "a02a1fde69b96da8ec2f73d6f7ae42c84a3bade1",
"block": 33606400,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-06-08T01:32:42",
"op": [
"comment",
{
"parent_author": "mdarweash",
"parent_permlink": "choosing-the-right-technology-vs-available-technology-developers",
"author": "steemitboard",
"permlink": "steemitboard-notify-mdarweash-20190608t013241000z",
"title": "",
"body": "Congratulations @mdarweash! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/https://steemitboard.com/@mdarweash/birthday1.png</td><td>Happy Birthday! - You are on the Steem blockchain for 1 year!</td></tr></table>\n\n<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@mdarweash) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=mdarweash)_</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\"]}"
}
]
}mdarweashpublished a new post: choosing-the-right-technology-vs-available-technology-developers2018/08/27 06:21:03
mdarweashpublished a new post: choosing-the-right-technology-vs-available-technology-developers
2018/08/27 06:21:03
| parent author | |
| parent permlink | cto |
| author | mdarweash |
| permlink | choosing-the-right-technology-vs-available-technology-developers |
| title | Choosing The Right Technology Vs Available Technology Developers! |
| body | choosing the right technology regardless of market developers availability? or, picking a technology that's not the most optimum but the market can supply developers. I'll mix this pos with a -Real- use case of one the companies I used to be their technology consultant. They have chosen the right technology specially that they have already the calibers of this technology. they started, moved forward and looks nice. at some point, the team leader of the development team decided to quite as he has another opportunity in another country. till here it looks nice... the disaster started, when the faced the problem of not being able to hire in the grace period they have allocated. working on a rush usually leads to a crush! the company started to hire under-qualified people because simply they are the best on the list they had. at that time, companies starts looking for consultants. - I'll take about this in a different post :D hiring the consultant should be preventive ? or on demand - It's complex to solve when you find a live system with users and almost 3 years of development. thousands of lines of codes with a technology that's really nice with no good supply. I always see that, you have to balance, never choose the wrong technology for sure. but you don't have to pick the best one. may be the 2nd or the 3rd as being (the best) here doesn't only count for the technology itself. it's about market availability, cost, ...etc in startups world, Done is always better than perfect. everyday we see hundereds of (the best) startups shutdown while few normal ones survive. simply, because they have their work done. the customer wants the service to be working. he doesn't pay attention to the underlaying technology. or how easy/hard for you to maintain it. go with the technology what will let you mark (Done) in your list with good capabilities to scale well in the future. regardless is it the best fit -from a technical perspective- or not. Please, Share your expereince if you have something in mind |
| json metadata | {"tags":["cto","developers","technology","startups","entrepreneurship"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #25427194/Trx 658210d6acc3dec5c4cdfa627c5466dca29ce4f9 |
View Raw JSON Data
{
"trx_id": "658210d6acc3dec5c4cdfa627c5466dca29ce4f9",
"block": 25427194,
"trx_in_block": 37,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-08-27T06:21:03",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "cto",
"author": "mdarweash",
"permlink": "choosing-the-right-technology-vs-available-technology-developers",
"title": "Choosing The Right Technology Vs Available Technology Developers!",
"body": "choosing the right technology regardless of market developers availability?\n\nor, picking a technology that's not the most optimum but the market can supply developers.\n\nI'll mix this pos with a -Real- use case of one the companies I used to be their technology consultant.\n\nThey have chosen the right technology specially that they have already the calibers of this technology. they started, moved forward and looks nice.\n\nat some point, the team leader of the development team decided to quite as he has another opportunity in another country. till here it looks nice...\n\nthe disaster started, when the faced the problem of not being able to hire in the grace period they have allocated. working on a rush usually leads to a crush! the company started to hire under-qualified people because simply they are the best on the list they had.\n\nat that time, companies starts looking for consultants. - I'll take about this in a different post :D hiring the consultant should be preventive ? or on demand -\n\nIt's complex to solve when you find a live system with users and almost 3 years of development. thousands of lines of codes with a technology that's really nice with no good supply.\n\nI always see that, you have to balance, never choose the wrong technology for sure. but you don't have to pick the best one. may be the 2nd or the 3rd as being (the best) here doesn't only count for the technology itself. it's about market availability, cost, ...etc\n\nin startups world, Done is always better than perfect. everyday we see hundereds of (the best) startups shutdown while few normal ones survive. simply, because they have their work done.\n\nthe customer wants the service to be working. he doesn't pay attention to the underlaying technology. or how easy/hard for you to maintain it.\n\ngo with the technology what will let you mark (Done) in your list with good capabilities to scale well in the future. regardless is it the best fit -from a technical perspective- or not.\n\nPlease, Share your expereince if you have something in mind",
"json_metadata": "{\"tags\":[\"cto\",\"developers\",\"technology\",\"startups\",\"entrepreneurship\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}mdarweashpublished a new post: choosing-the-right-technology-vs-available-technology-developers2018/08/27 06:20:18
mdarweashpublished a new post: choosing-the-right-technology-vs-available-technology-developers
2018/08/27 06:20:18
| parent author | |
| parent permlink | cto |
| author | mdarweash |
| permlink | choosing-the-right-technology-vs-available-technology-developers |
| title | Choosing The Right Technology Vs Available Technology Developers! |
| body | choosing the right technology regardless of market developers availability? or, picking a technology that's not the most optimum but the market can supply developers. I'll mix this pos with a -Real- use case of one the companies I used to be their technology consultant. They have chosen the right technology specially that they have already the calibers of this technology. they started, moved forward and looks nice. at some point, the team leader of the development team decided to quite as he has another opportunity in another country. till here it looks nice... the disaster started, when the faced the problem of not being able to hire in the grace period they have allocated. working on a rush usually leads to a crush! the company started to hire under-qualified people because simply they are the best on the list they had. at that time, companies starts looking for consultants. - I'll take about this in a different post :D hiring the consultant should be preventive ? or on demand - It's complex to solve when you find a live system with users and almost 3 years of development. thousands of lines of codes with a technology that's really nice with no good supply. I always see that, you have to balance, never choose the wrong technology for sure. but you don't have to pick the best one. may be the 2nd or the 3rd as being (the best) here doesn't only count for the technology itself. it's about market availability, cost, ...etc in startups world, Done is always better than perfect. everyday we see hundereds of (the best) startups shutdown while few normal ones survive. simply, because they have their work done. the customer wants the service to be working. he doesn't pay attention to the underlaying technology. or how easy/hard for you to maintain it. go with the technology what will let you mark (Done) in your list with good capabilities to scale well in the future. regardless is it the best fit -from a technical perspective- or not. Please, Share your expereince if you have something in mind |
| json metadata | {"tags":["cto"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #25427179/Trx d2bca49c32e5e9a4e8807030759f59f3df1b2c7c |
View Raw JSON Data
{
"trx_id": "d2bca49c32e5e9a4e8807030759f59f3df1b2c7c",
"block": 25427179,
"trx_in_block": 35,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-08-27T06:20:18",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "cto",
"author": "mdarweash",
"permlink": "choosing-the-right-technology-vs-available-technology-developers",
"title": "Choosing The Right Technology Vs Available Technology Developers!",
"body": "choosing the right technology regardless of market developers availability?\n\nor, picking a technology that's not the most optimum but the market can supply developers.\n\nI'll mix this pos with a -Real- use case of one the companies I used to be their technology consultant.\n\nThey have chosen the right technology specially that they have already the calibers of this technology. they started, moved forward and looks nice.\n\nat some point, the team leader of the development team decided to quite as he has another opportunity in another country. till here it looks nice...\n\nthe disaster started, when the faced the problem of not being able to hire in the grace period they have allocated. working on a rush usually leads to a crush! the company started to hire under-qualified people because simply they are the best on the list they had.\n\nat that time, companies starts looking for consultants. - I'll take about this in a different post :D hiring the consultant should be preventive ? or on demand -\n\nIt's complex to solve when you find a live system with users and almost 3 years of development. thousands of lines of codes with a technology that's really nice with no good supply.\n\nI always see that, you have to balance, never choose the wrong technology for sure. but you don't have to pick the best one. may be the 2nd or the 3rd as being (the best) here doesn't only count for the technology itself. it's about market availability, cost, ...etc\n\nin startups world, Done is always better than perfect. everyday we see hundereds of (the best) startups shutdown while few normal ones survive. simply, because they have their work done.\n\nthe customer wants the service to be working. he doesn't pay attention to the underlaying technology. or how easy/hard for you to maintain it.\n\ngo with the technology what will let you mark (Done) in your list with good capabilities to scale well in the future. regardless is it the best fit -from a technical perspective- or not.\n\nPlease, Share your expereince if you have something in mind",
"json_metadata": "{\"tags\":[\"cto\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}steemdelegated 0.000 SP to @mdarweash2018/07/28 03:22:57
steemdelegated 0.000 SP to @mdarweash
2018/07/28 03:22:57
| delegator | steem |
| delegatee | mdarweash |
| vesting shares | 0.000000 VESTS |
| Transaction Info | Block #24560401/Trx c764079b866b90ed02efb9023ebb4700ebde492d |
View Raw JSON Data
{
"trx_id": "c764079b866b90ed02efb9023ebb4700ebde492d",
"block": 24560401,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-07-28T03:22:57",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "mdarweash",
"vesting_shares": "0.000000 VESTS"
}
]
}2018/07/28 03:14:42
2018/07/28 03:14:42
| required auths | [] |
| required posting auths | ["mdarweash"] |
| id | follow |
| json | ["follow",{"follower":"mdarweash","following":"kinyou","what":["blog"]}] |
| Transaction Info | Block #24560236/Trx b083f5c1451770543204dcf9eaf1b1567c3ba9bc |
View Raw JSON Data
{
"trx_id": "b083f5c1451770543204dcf9eaf1b1567c3ba9bc",
"block": 24560236,
"trx_in_block": 11,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-07-28T03:14:42",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"mdarweash"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"mdarweash\",\"following\":\"kinyou\",\"what\":[\"blog\"]}]"
}
]
}kinyouupvoted (100.00%) @mdarweash / how-to-unerstand-what-s-happening-to-bitcoin-btc-etf-cboe-sec2018/07/28 03:08:24
kinyouupvoted (100.00%) @mdarweash / how-to-unerstand-what-s-happening-to-bitcoin-btc-etf-cboe-sec
2018/07/28 03:08:24
| voter | kinyou |
| author | mdarweash |
| permlink | how-to-unerstand-what-s-happening-to-bitcoin-btc-etf-cboe-sec |
| weight | 10000 (100.00%) |
| Transaction Info | Block #24560110/Trx 9a12529a9ec278136647f460613a63dd399c84b2 |
View Raw JSON Data
{
"trx_id": "9a12529a9ec278136647f460613a63dd399c84b2",
"block": 24560110,
"trx_in_block": 38,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-07-28T03:08:24",
"op": [
"vote",
{
"voter": "kinyou",
"author": "mdarweash",
"permlink": "how-to-unerstand-what-s-happening-to-bitcoin-btc-etf-cboe-sec",
"weight": 10000
}
]
}2018/07/28 03:01:45
2018/07/28 03:01:45
| parent author | mdarweash |
| parent permlink | how-to-unerstand-what-s-happening-to-bitcoin-btc-etf-cboe-sec |
| author | kinyou |
| permlink | re-mdarweash-how-to-unerstand-what-s-happening-to-bitcoin-btc-etf-cboe-sec-20180728t030145974z |
| title | |
| body | I gave you an upvote on your post! Please give me a follow and I will give you a follow in return and possible future votes! |
| json metadata | {"tags":["btc"],"app":"steemit/0.1"} |
| Transaction Info | Block #24559977/Trx f9c1e70e32f1826096fe3a61b3696b13032b55e3 |
View Raw JSON Data
{
"trx_id": "f9c1e70e32f1826096fe3a61b3696b13032b55e3",
"block": 24559977,
"trx_in_block": 33,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-07-28T03:01:45",
"op": [
"comment",
{
"parent_author": "mdarweash",
"parent_permlink": "how-to-unerstand-what-s-happening-to-bitcoin-btc-etf-cboe-sec",
"author": "kinyou",
"permlink": "re-mdarweash-how-to-unerstand-what-s-happening-to-bitcoin-btc-etf-cboe-sec-20180728t030145974z",
"title": "",
"body": "I gave you an upvote on your post! Please give me a follow and I will give you a follow in return and possible future votes!",
"json_metadata": "{\"tags\":[\"btc\"],\"app\":\"steemit/0.1\"}"
}
]
}2018/07/28 03:01:15
2018/07/28 03:01:15
| voter | fastresteem |
| author | mdarweash |
| permlink | how-to-unerstand-what-s-happening-to-bitcoin-btc-etf-cboe-sec |
| weight | 100 (1.00%) |
| Transaction Info | Block #24559967/Trx 7eb8a4839b463b4335b4f62569d283c99d23a862 |
View Raw JSON Data
{
"trx_id": "7eb8a4839b463b4335b4f62569d283c99d23a862",
"block": 24559967,
"trx_in_block": 16,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-07-28T03:01:15",
"op": [
"vote",
{
"voter": "fastresteem",
"author": "mdarweash",
"permlink": "how-to-unerstand-what-s-happening-to-bitcoin-btc-etf-cboe-sec",
"weight": 100
}
]
}mdarweashpublished a new post: how-to-unerstand-what-s-happening-to-bitcoin-btc-etf-cboe-sec2018/07/28 03:01:03
mdarweashpublished a new post: how-to-unerstand-what-s-happening-to-bitcoin-btc-etf-cboe-sec
2018/07/28 03:01:03
| parent author | |
| parent permlink | btc |
| author | mdarweash |
| permlink | how-to-unerstand-what-s-happening-to-bitcoin-btc-etf-cboe-sec |
| title | How to unerstand what's happening to Bitcoin ? #BTC #ETF #CBOE #SEC |
| body | let's start with knowing what this abbreviation means BTC: you know this guy :D that's why you are here already, It's uncle BitCoin ETF: Exchanged Traded Fund - simply this is a marketable security which tracks an index, bonds, group of different assets or may be a commodity like gold. CBOE: Chicago Board Options Exchange - this is the largest options market in the world that contains contracts focusing on individual equities SEC: The United States Securities and Exchange Commission First of all, do you feel familiar with this chart?  No, it's not the BitCoin chart. give a look at the dates. This is the gold chart. can you imagine how many people talked then that gold is dead :) going down from 2200 to less than 400! let's see the full chart here  Wow, it's a great bull run over the years. But, something very interesting is happening here. what can the ETF make to the BTC? simply, if we look at what ETF has done to the gold we maybe find it easier to understand if we know that, The ETF was approved in Nov 2004 for Gold! enabling lots of investors to put money into gold reference: http://etfdb.com/etf/GLD/  It's clear now, What can ETF do when it's approved. if you can correlate those two charts, understanding how different in terms of time and volatility, you can get what can ETF do to BitCoin :)  keep an eye on what's happening to this event. Follow us if you need more insights Disclaimer: this is not a financial consultancy. this is only my opinion. do your own research before executing any investments. Best Of Luck! |
| json metadata | {"tags":["btc","etf","cboe","sec"],"image":["https://cdn.steemitimages.com/DQmah6ZfLdB3er985LU8FtiLkiGgx1XuTwxoJNdSr1ZfT9C/gold1.png","https://cdn.steemitimages.com/DQmSFz2NJvWLpdDtj3Mz6D3C2v9LRZJqJEzxMu2Skhj9dG4/image.png","https://cdn.steemitimages.com/DQmUHBYg7aeCFQy2GDc4QUvHVksYVeb1VCoAVCWWo6aLA1x/image.png","https://cdn.steemitimages.com/DQmcwyccPKpbr1L9C3aLTwDQcyANXDnmqPY8uWQsqGpTMch/image.png"],"links":["http://etfdb.com/etf/GLD/"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #24559963/Trx e832905d1e7e09ef62b02456e1185c44e1b08ac5 |
View Raw JSON Data
{
"trx_id": "e832905d1e7e09ef62b02456e1185c44e1b08ac5",
"block": 24559963,
"trx_in_block": 12,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-07-28T03:01:03",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "btc",
"author": "mdarweash",
"permlink": "how-to-unerstand-what-s-happening-to-bitcoin-btc-etf-cboe-sec",
"title": "How to unerstand what's happening to Bitcoin ? #BTC #ETF #CBOE #SEC",
"body": "let's start with knowing what this abbreviation means \n\nBTC: you know this guy :D that's why you are here already, It's uncle BitCoin\n\nETF: Exchanged Traded Fund - simply this is a marketable security which tracks an index, bonds, group of different assets or may be a commodity like gold.\n\nCBOE: Chicago Board Options Exchange - this is the largest options market in the world that contains contracts focusing on individual equities\n\nSEC: The United States Securities and Exchange Commission\n\nFirst of all, do you feel familiar with this chart?\n\n\n\nNo, it's not the BitCoin chart. give a look at the dates.\n\nThis is the gold chart. can you imagine how many people talked then that gold is dead :) going down from 2200 to less than 400!\n\nlet's see the full chart here\n\n\n\nWow, it's a great bull run over the years. But, something very interesting is happening here.\n\nwhat can the ETF make to the BTC? \n\nsimply, if we look at what ETF has done to the gold we maybe find it easier to understand \n\n\nif we know that, The ETF was approved in Nov 2004 for Gold! enabling lots of investors to put money into gold\nreference: http://etfdb.com/etf/GLD/\n\n\n It's clear now, What can ETF do when it's approved.\n\nif you can correlate those two charts, understanding how different in terms of time and volatility, you can get what can ETF do to BitCoin :)\n\n\n\n\nkeep an eye on what's happening to this event. \n\nFollow us if you need more insights \n\nDisclaimer: this is not a financial consultancy. this is only my opinion. do your own research before executing any investments. Best Of Luck!",
"json_metadata": "{\"tags\":[\"btc\",\"etf\",\"cboe\",\"sec\"],\"image\":[\"https://cdn.steemitimages.com/DQmah6ZfLdB3er985LU8FtiLkiGgx1XuTwxoJNdSr1ZfT9C/gold1.png\",\"https://cdn.steemitimages.com/DQmSFz2NJvWLpdDtj3Mz6D3C2v9LRZJqJEzxMu2Skhj9dG4/image.png\",\"https://cdn.steemitimages.com/DQmUHBYg7aeCFQy2GDc4QUvHVksYVeb1VCoAVCWWo6aLA1x/image.png\",\"https://cdn.steemitimages.com/DQmcwyccPKpbr1L9C3aLTwDQcyANXDnmqPY8uWQsqGpTMch/image.png\"],\"links\":[\"http://etfdb.com/etf/GLD/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}mdarweashpowered up 38.010 STEEM to @mdarweash2018/07/28 02:14:36
mdarweashpowered up 38.010 STEEM to @mdarweash
2018/07/28 02:14:36
| from | mdarweash |
| to | mdarweash |
| amount | 38.010 STEEM |
| Transaction Info | Block #24559034/Trx 8609f478fa33925d06f14a368e0854b1fc9347ae |
View Raw JSON Data
{
"trx_id": "8609f478fa33925d06f14a368e0854b1fc9347ae",
"block": 24559034,
"trx_in_block": 20,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-07-28T02:14:36",
"op": [
"transfer_to_vesting",
{
"from": "mdarweash",
"to": "mdarweash",
"amount": "38.010 STEEM"
}
]
}binance-hotsent 37.020 STEEM to @mdarweash- "all from binance"2018/07/28 02:07:33
binance-hotsent 37.020 STEEM to @mdarweash- "all from binance"
2018/07/28 02:07:33
| from | binance-hot |
| to | mdarweash |
| amount | 37.020 STEEM |
| memo | all from binance |
| Transaction Info | Block #24558893/Trx 3be8d399cf4d6f12919f10099d84dd58f364b078 |
View Raw JSON Data
{
"trx_id": "3be8d399cf4d6f12919f10099d84dd58f364b078",
"block": 24558893,
"trx_in_block": 34,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-07-28T02:07:33",
"op": [
"transfer",
{
"from": "binance-hot",
"to": "mdarweash",
"amount": "37.020 STEEM",
"memo": "all from binance"
}
]
}binance-hotsent 0.990 STEEM to @mdarweash- "from binance"2018/07/28 02:00:27
binance-hotsent 0.990 STEEM to @mdarweash- "from binance"
2018/07/28 02:00:27
| from | binance-hot |
| to | mdarweash |
| amount | 0.990 STEEM |
| memo | from binance |
| Transaction Info | Block #24558751/Trx f315ae0e4aa21a18acd96700352d6518fb78e446 |
View Raw JSON Data
{
"trx_id": "f315ae0e4aa21a18acd96700352d6518fb78e446",
"block": 24558751,
"trx_in_block": 10,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-07-28T02:00:27",
"op": [
"transfer",
{
"from": "binance-hot",
"to": "mdarweash",
"amount": "0.990 STEEM",
"memo": "from binance"
}
]
}2018/07/25 07:38:39
2018/07/25 07:38:39
| voter | mdarweash |
| author | mdarweash |
| permlink | what-if-the-suitable-technology-stack-for-your-startup-doesn-t-have-enough-market-supply |
| weight | 10000 (100.00%) |
| Transaction Info | Block #24479199/Trx 6cbb18c8703d75b84a2572c2323e356a4412fd13 |
View Raw JSON Data
{
"trx_id": "6cbb18c8703d75b84a2572c2323e356a4412fd13",
"block": 24479199,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-07-25T07:38:39",
"op": [
"vote",
{
"voter": "mdarweash",
"author": "mdarweash",
"permlink": "what-if-the-suitable-technology-stack-for-your-startup-doesn-t-have-enough-market-supply",
"weight": 10000
}
]
}steemdelegated 17.359 SP to @mdarweash2018/06/23 06:53:21
steemdelegated 17.359 SP to @mdarweash
2018/06/23 06:53:21
| delegator | steem |
| delegatee | mdarweash |
| vesting shares | 28230.808053 VESTS |
| Transaction Info | Block #23566962/Trx cce0533cd49bef5d7950e39b282f5c03d746cc84 |
View Raw JSON Data
{
"trx_id": "cce0533cd49bef5d7950e39b282f5c03d746cc84",
"block": 23566962,
"trx_in_block": 56,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-23T06:53:21",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "mdarweash",
"vesting_shares": "28230.808053 VESTS"
}
]
}mdarweashpowered up 0.993 STEEM to @mdarweash2018/06/23 05:05:42
mdarweashpowered up 0.993 STEEM to @mdarweash
2018/06/23 05:05:42
| from | mdarweash |
| to | mdarweash |
| amount | 0.993 STEEM |
| Transaction Info | Block #23564809/Trx 52d7fa4855f92478512998549fe95bc574e53454 |
View Raw JSON Data
{
"trx_id": "52d7fa4855f92478512998549fe95bc574e53454",
"block": 23564809,
"trx_in_block": 10,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-23T05:05:42",
"op": [
"transfer_to_vesting",
{
"from": "mdarweash",
"to": "mdarweash",
"amount": "0.993 STEEM"
}
]
}binance-hotsent 0.990 STEEM to @mdarweash- "STM5Rs9q7jYyqPZX44NYXxSQEVhi3kCbaKQMn5hQa1HCNAQA4XV9z"2018/06/22 04:13:06
binance-hotsent 0.990 STEEM to @mdarweash- "STM5Rs9q7jYyqPZX44NYXxSQEVhi3kCbaKQMn5hQa1HCNAQA4XV9z"
2018/06/22 04:13:06
| from | binance-hot |
| to | mdarweash |
| amount | 0.990 STEEM |
| memo | STM5Rs9q7jYyqPZX44NYXxSQEVhi3kCbaKQMn5hQa1HCNAQA4XV9z |
| Transaction Info | Block #23534959/Trx ab8d86844ce0ca42e78ce50f1b664bcf8517aab9 |
View Raw JSON Data
{
"trx_id": "ab8d86844ce0ca42e78ce50f1b664bcf8517aab9",
"block": 23534959,
"trx_in_block": 19,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-22T04:13:06",
"op": [
"transfer",
{
"from": "binance-hot",
"to": "mdarweash",
"amount": "0.990 STEEM",
"memo": "STM5Rs9q7jYyqPZX44NYXxSQEVhi3kCbaKQMn5hQa1HCNAQA4XV9z"
}
]
}mdarweashclaimed reward balance: 0.003 STEEM, 0.005 SBD, 0.007 SP2018/06/22 04:01:06
mdarweashclaimed reward balance: 0.003 STEEM, 0.005 SBD, 0.007 SP
2018/06/22 04:01:06
| account | mdarweash |
| reward steem | 0.003 STEEM |
| reward sbd | 0.005 SBD |
| reward vests | 12.190553 VESTS |
| Transaction Info | Block #23534719/Trx b7085eaa1ab25bc13e34a149b294502ef894ed44 |
View Raw JSON Data
{
"trx_id": "b7085eaa1ab25bc13e34a149b294502ef894ed44",
"block": 23534719,
"trx_in_block": 16,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-22T04:01:06",
"op": [
"claim_reward_balance",
{
"account": "mdarweash",
"reward_steem": "0.003 STEEM",
"reward_sbd": "0.005 SBD",
"reward_vests": "12.190553 VESTS"
}
]
}mdarweashreceived 0.003 STEEM, 0.005 SBD, 0.007 SP author reward for @mdarweash / bluetooth-low-energy-is-not-just-a-bluetooth-upgrade2018/06/15 00:46:09
mdarweashreceived 0.003 STEEM, 0.005 SBD, 0.007 SP author reward for @mdarweash / bluetooth-low-energy-is-not-just-a-bluetooth-upgrade
2018/06/15 00:46:09
| author | mdarweash |
| permlink | bluetooth-low-energy-is-not-just-a-bluetooth-upgrade |
| sbd payout | 0.005 SBD |
| steem payout | 0.003 STEEM |
| vesting payout | 12.190553 VESTS |
| Transaction Info | Block #23329286/Virtual Operation #5 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 23329286,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 5,
"timestamp": "2018-06-15T00:46:09",
"op": [
"author_reward",
{
"author": "mdarweash",
"permlink": "bluetooth-low-energy-is-not-just-a-bluetooth-upgrade",
"sbd_payout": "0.005 SBD",
"steem_payout": "0.003 STEEM",
"vesting_payout": "12.190553 VESTS"
}
]
}droidaupvoted (100.00%) @mdarweash / what-s-happening-to-electroneum2018/06/10 22:03:30
droidaupvoted (100.00%) @mdarweash / what-s-happening-to-electroneum
2018/06/10 22:03:30
| voter | droida |
| author | mdarweash |
| permlink | what-s-happening-to-electroneum |
| weight | 10000 (100.00%) |
| Transaction Info | Block #23211403/Trx 1936c71acc3f69036776cec5b7c223618b7437e5 |
View Raw JSON Data
{
"trx_id": "1936c71acc3f69036776cec5b7c223618b7437e5",
"block": 23211403,
"trx_in_block": 21,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-10T22:03:30",
"op": [
"vote",
{
"voter": "droida",
"author": "mdarweash",
"permlink": "what-s-happening-to-electroneum",
"weight": 10000
}
]
}youngogmarqsupvoted (0.02%) @mdarweash / what-s-happening-to-electroneum2018/06/10 00:57:18
youngogmarqsupvoted (0.02%) @mdarweash / what-s-happening-to-electroneum
2018/06/10 00:57:18
| voter | youngogmarqs |
| author | mdarweash |
| permlink | what-s-happening-to-electroneum |
| weight | 2 (0.02%) |
| Transaction Info | Block #23186108/Trx 8f7cb6d01cc3b4131e03046cb149dc51a1d35aac |
View Raw JSON Data
{
"trx_id": "8f7cb6d01cc3b4131e03046cb149dc51a1d35aac",
"block": 23186108,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-10T00:57:18",
"op": [
"vote",
{
"voter": "youngogmarqs",
"author": "mdarweash",
"permlink": "what-s-happening-to-electroneum",
"weight": 2
}
]
}ca-lifeupvoted (100.00%) @mdarweash / what-s-happening-to-electroneum2018/06/10 00:34:54
ca-lifeupvoted (100.00%) @mdarweash / what-s-happening-to-electroneum
2018/06/10 00:34:54
| voter | ca-life |
| author | mdarweash |
| permlink | what-s-happening-to-electroneum |
| weight | 10000 (100.00%) |
| Transaction Info | Block #23185660/Trx 0abe43b106d1c7d16cf8d0bf2447496953787f9b |
View Raw JSON Data
{
"trx_id": "0abe43b106d1c7d16cf8d0bf2447496953787f9b",
"block": 23185660,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-10T00:34:54",
"op": [
"vote",
{
"voter": "ca-life",
"author": "mdarweash",
"permlink": "what-s-happening-to-electroneum",
"weight": 10000
}
]
}2018/06/10 00:34:45
2018/06/10 00:34:45
| parent author | mdarweash |
| parent permlink | what-s-happening-to-electroneum |
| author | a-0-0 |
| permlink | re-mdarweash-what-s-happening-to-electroneum-20180610t003444258z |
| title | |
| body | Go here https://steemit.com/@a-a-a to get your post resteemed to over 72,000 followers. |
| json metadata | {"tags":["electroneum"],"links":["https://steemit.com/@a-a-a"],"app":"steemit/0.1"} |
| Transaction Info | Block #23185657/Trx 7abab57debd18876529bc55172ee96fce7ac4f6f |
View Raw JSON Data
{
"trx_id": "7abab57debd18876529bc55172ee96fce7ac4f6f",
"block": 23185657,
"trx_in_block": 22,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-10T00:34:45",
"op": [
"comment",
{
"parent_author": "mdarweash",
"parent_permlink": "what-s-happening-to-electroneum",
"author": "a-0-0",
"permlink": "re-mdarweash-what-s-happening-to-electroneum-20180610t003444258z",
"title": "",
"body": "Go here https://steemit.com/@a-a-a to get your post resteemed to over 72,000 followers.",
"json_metadata": "{\"tags\":[\"electroneum\"],\"links\":[\"https://steemit.com/@a-a-a\"],\"app\":\"steemit/0.1\"}"
}
]
}mdarweashpublished a new post: what-s-happening-to-electroneum2018/06/10 00:34:18
mdarweashpublished a new post: what-s-happening-to-electroneum
2018/06/10 00:34:18
| parent author | |
| parent permlink | electroneum |
| author | mdarweash |
| permlink | what-s-happening-to-electroneum |
| title | What's Happening to Electroneum ? |
| body | Electroneum is a promising coin with good vision. despite the bad luck they suffered -and still suffering- sometimes. starting from relaunch at the beginning ending with a network stagnation due a temper with attack happened from nice hash led to a network disturbance it's quite clear from the chart that BIG something wrong is happening  from my point of view -and this is not a financial consultancy, do you own due diligence- it's basically an opportunity either for a miner (difficulty drop) or for traders (price drop) as the team is working hard to recover the problem. once the problem is recovered, the hashrate and the price will recover :) it's just an expectation that worth the risk. Disclaimer: I myself has just pointed my miners to their network and also just bought also some ETN What do you think will happen to the Electroneum ? |
| json metadata | {"tags":["electroneum","mining","cryptocurrency","trading","hashrate"],"image":["https://cdn.steemitimages.com/DQmZSrZ1WNJ2UKXq7RP7Xbgf9SGXqj8m6QZmx364aRiVhk2/image.png"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #23185648/Trx d37ab312b160937dd5684ad9f683db082c6d80b7 |
View Raw JSON Data
{
"trx_id": "d37ab312b160937dd5684ad9f683db082c6d80b7",
"block": 23185648,
"trx_in_block": 37,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-10T00:34:18",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "electroneum",
"author": "mdarweash",
"permlink": "what-s-happening-to-electroneum",
"title": "What's Happening to Electroneum ?",
"body": "Electroneum is a promising coin with good vision. despite the bad luck they suffered -and still suffering- sometimes. starting from relaunch at the beginning ending with a network stagnation due a temper with attack happened from nice hash led to a network disturbance \n\nit's quite clear from the chart that BIG something wrong is happening \n\n\n\nfrom my point of view -and this is not a financial consultancy, do you own due diligence- it's basically an opportunity either for a miner (difficulty drop) or for traders (price drop) as the team is working hard to recover the problem.\n\nonce the problem is recovered, the hashrate and the price will recover :) \n\nit's just an expectation that worth the risk. \n\nDisclaimer: I myself has just pointed my miners to their network and also just bought also some ETN\n\nWhat do you think will happen to the Electroneum ?",
"json_metadata": "{\"tags\":[\"electroneum\",\"mining\",\"cryptocurrency\",\"trading\",\"hashrate\"],\"image\":[\"https://cdn.steemitimages.com/DQmZSrZ1WNJ2UKXq7RP7Xbgf9SGXqj8m6QZmx364aRiVhk2/image.png\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}mdarweashfollowed @originalworks2018/06/08 13:30:48
mdarweashfollowed @originalworks
2018/06/08 13:30:48
| required auths | [] |
| required posting auths | ["mdarweash"] |
| id | follow |
| json | ["follow",{"follower":"mdarweash","following":"originalworks","what":["blog"]}] |
| Transaction Info | Block #23143585/Trx 06d98fff602527da3907f8f2ac7506e2fb86152e |
View Raw JSON Data
{
"trx_id": "06d98fff602527da3907f8f2ac7506e2fb86152e",
"block": 23143585,
"trx_in_block": 32,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-08T13:30:48",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"mdarweash"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"mdarweash\",\"following\":\"originalworks\",\"what\":[\"blog\"]}]"
}
]
}2018/06/08 13:02:57
2018/06/08 13:02:57
| voter | youngogmarqs |
| author | mdarweash |
| permlink | what-if-the-suitable-technology-stack-for-your-startup-doesn-t-have-enough-market-supply |
| weight | 2 (0.02%) |
| Transaction Info | Block #23143028/Trx f55abdff7cccf084bc7603ef657e4f01ea445a1b |
View Raw JSON Data
{
"trx_id": "f55abdff7cccf084bc7603ef657e4f01ea445a1b",
"block": 23143028,
"trx_in_block": 53,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-08T13:02:57",
"op": [
"vote",
{
"voter": "youngogmarqs",
"author": "mdarweash",
"permlink": "what-if-the-suitable-technology-stack-for-your-startup-doesn-t-have-enough-market-supply",
"weight": 2
}
]
}2018/06/08 12:44:36
2018/06/08 12:44:36
| voter | ubg |
| author | mdarweash |
| permlink | what-if-the-suitable-technology-stack-for-your-startup-doesn-t-have-enough-market-supply |
| weight | 100 (1.00%) |
| Transaction Info | Block #23142661/Trx ac683374cda48dc1de5ee063e8a94e75d6430606 |
View Raw JSON Data
{
"trx_id": "ac683374cda48dc1de5ee063e8a94e75d6430606",
"block": 23142661,
"trx_in_block": 14,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-08T12:44:36",
"op": [
"vote",
{
"voter": "ubg",
"author": "mdarweash",
"permlink": "what-if-the-suitable-technology-stack-for-your-startup-doesn-t-have-enough-market-supply",
"weight": 100
}
]
}2018/06/08 12:37:24
2018/06/08 12:37:24
| parent author | |
| parent permlink | startups |
| author | mdarweash |
| permlink | what-if-the-suitable-technology-stack-for-your-startup-doesn-t-have-enough-market-supply |
| title | What If The Suitable Technology Stack For Your Startup Doesn't Have Enough Market Supply? |
| body | in the previous post, it was regarding the Experienced part-time CTO vs mid-range full one. Today, talking about another complex challenge for a company. choosing the right technology regardless of market developers availability? or, picking a technology that's not the most optimum but the market can supply developers. I'll mix this post with a -Real- use case of one the companies I used to be their technology consultant. They have chosen the right technology, especially that they have already the calibers of this technology. they started, moved forward and looks nice. at some point, the team leader of the development team decided to quit as he has another opportunity in another country. till here it looks nice... the disaster started, when the faced the problem of not being able to hire in the grace period they have allocated. working on a rush usually leads to a crush! the company started to hire under-qualified people because simply they are the best on the list they had. at that time, companies start looking for consultants. - I'll take about this in a different post :D hiring the consultant should be preventive ? or on demand - It's complex to solve when you find a live system with users and almost 3 years of development. thousands of lines of codes with a technology that's really nice with no good supply. I always see that you have to balance, never choose the wrong technology for sure. but you don't have to pick the best one. maybe the 2nd or the 3rd as being (the best) here doesn't only count for the technology itself. it's about market availability, cost, ...etc in startups world, Done is always better than perfect. every day we see hundreds of (the best) startups shutdown while few normal ones survive. simply, because they have their work done. the customer wants the service to be working. he doesn't pay attention to the underlying technology. or how easy/hard for you to maintain it. go with the technology that will let you mark (Done) in your list with good capabilities to scale well in the future. regardless is it the best fit -from a technical perspective- or not. Please, Share your experience if you have something in mind |
| json metadata | {"tags":["startups","technology","consultation"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #23142517/Trx 5a3156bd7e6500be97273e0210efb97bf7d9f99e |
View Raw JSON Data
{
"trx_id": "5a3156bd7e6500be97273e0210efb97bf7d9f99e",
"block": 23142517,
"trx_in_block": 22,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-08T12:37:24",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "startups",
"author": "mdarweash",
"permlink": "what-if-the-suitable-technology-stack-for-your-startup-doesn-t-have-enough-market-supply",
"title": "What If The Suitable Technology Stack For Your Startup Doesn't Have Enough Market Supply?",
"body": "in the previous post, it was regarding the Experienced part-time CTO vs mid-range full one.\n\nToday, talking about another complex challenge for a company.\n\nchoosing the right technology regardless of market developers availability?\n\nor, picking a technology that's not the most optimum but the market can supply developers.\n\nI'll mix this post with a -Real- use case of one the companies I used to be their technology consultant.\n\nThey have chosen the right technology, especially that they have already the calibers of this technology. they started, moved forward and looks nice.\n\nat some point, the team leader of the development team decided to quit as he has another opportunity in another country. till here it looks nice...\n\nthe disaster started, when the faced the problem of not being able to hire in the grace period they have allocated. working on a rush usually leads to a crush! the company started to hire under-qualified people because simply they are the best on the list they had.\n\nat that time, companies start looking for consultants. - I'll take about this in a different post :D hiring the consultant should be preventive ? or on demand -\n\nIt's complex to solve when you find a live system with users and almost 3 years of development. thousands of lines of codes with a technology that's really nice with no good supply.\n\nI always see that you have to balance, never choose the wrong technology for sure. but you don't have to pick the best one. maybe the 2nd or the 3rd as being (the best) here doesn't only count for the technology itself. it's about market availability, cost, ...etc\n\nin startups world, Done is always better than perfect. every day we see hundreds of (the best) startups shutdown while few normal ones survive. simply, because they have their work done.\n\nthe customer wants the service to be working. he doesn't pay attention to the underlying technology. or how easy/hard for you to maintain it.\n\ngo with the technology that will let you mark (Done) in your list with good capabilities to scale well in the future. regardless is it the best fit -from a technical perspective- or not.\n\nPlease, Share your experience if you have something in mind",
"json_metadata": "{\"tags\":[\"startups\",\"technology\",\"consultation\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}mdarweashfollowed @introduce.bot2018/06/08 12:03:18
mdarweashfollowed @introduce.bot
2018/06/08 12:03:18
| required auths | [] |
| required posting auths | ["mdarweash"] |
| id | follow |
| json | ["follow",{"follower":"mdarweash","following":"introduce.bot","what":["blog"]}] |
| Transaction Info | Block #23141835/Trx bf9f6b40bbe84343e7396928d8b646e9dd9b1f18 |
View Raw JSON Data
{
"trx_id": "bf9f6b40bbe84343e7396928d8b646e9dd9b1f18",
"block": 23141835,
"trx_in_block": 19,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-08T12:03:18",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"mdarweash"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"mdarweash\",\"following\":\"introduce.bot\",\"what\":[\"blog\"]}]"
}
]
}steemdelegated 18.622 SP to @mdarweash2018/06/08 01:33:45
steemdelegated 18.622 SP to @mdarweash
2018/06/08 01:33:45
| delegator | steem |
| delegatee | mdarweash |
| vesting shares | 30284.018334 VESTS |
| Transaction Info | Block #23129247/Trx 398390e060a1acd2545a8839743ef98fe65dc83f |
View Raw JSON Data
{
"trx_id": "398390e060a1acd2545a8839743ef98fe65dc83f",
"block": 23129247,
"trx_in_block": 26,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-08T01:33:45",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "mdarweash",
"vesting_shares": "30284.018334 VESTS"
}
]
}2018/06/08 01:20:27
2018/06/08 01:20:27
| parent author | mdarweash |
| parent permlink | bluetooth-low-energy-is-not-just-a-bluetooth-upgrade |
| author | introduce.bot |
| permlink | introduce-bot-re-mdarweashbluetooth-low-energy-is-not-just-a-bluetooth-upgrade |
| title | |
| body | ✅ @mdarweash, I gave you an upvote on your first post! **Please give me a follow** and I will give you a follow in return!<br><br>Please also take a moment to read [this post](https://steemit.com/spam/@pleasestop/introducing-pleasestop-here-to-reduce-comment-spam) regarding bad behavior on Steemit. |
| json metadata | |
| Transaction Info | Block #23128981/Trx 1cd0e57d427aac3bc5bdc6c809c56e05867f1dfd |
View Raw JSON Data
{
"trx_id": "1cd0e57d427aac3bc5bdc6c809c56e05867f1dfd",
"block": 23128981,
"trx_in_block": 58,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-08T01:20:27",
"op": [
"comment",
{
"parent_author": "mdarweash",
"parent_permlink": "bluetooth-low-energy-is-not-just-a-bluetooth-upgrade",
"author": "introduce.bot",
"permlink": "introduce-bot-re-mdarweashbluetooth-low-energy-is-not-just-a-bluetooth-upgrade",
"title": "",
"body": "✅ @mdarweash, I gave you an upvote on your first post! **Please give me a follow** and I will give you a follow in return!<br><br>Please also take a moment to read [this post](https://steemit.com/spam/@pleasestop/introducing-pleasestop-here-to-reduce-comment-spam) regarding bad behavior on Steemit.",
"json_metadata": ""
}
]
}introduce.botupvoted (2.24%) @mdarweash / bluetooth-low-energy-is-not-just-a-bluetooth-upgrade2018/06/08 01:20:27
introduce.botupvoted (2.24%) @mdarweash / bluetooth-low-energy-is-not-just-a-bluetooth-upgrade
2018/06/08 01:20:27
| voter | introduce.bot |
| author | mdarweash |
| permlink | bluetooth-low-energy-is-not-just-a-bluetooth-upgrade |
| weight | 224 (2.24%) |
| Transaction Info | Block #23128981/Trx a8887d4a95ed4f731d929cd996e441609406681c |
View Raw JSON Data
{
"trx_id": "a8887d4a95ed4f731d929cd996e441609406681c",
"block": 23128981,
"trx_in_block": 21,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-08T01:20:27",
"op": [
"vote",
{
"voter": "introduce.bot",
"author": "mdarweash",
"permlink": "bluetooth-low-energy-is-not-just-a-bluetooth-upgrade",
"weight": 224
}
]
}mdarweashupdated their account properties2018/06/08 00:47:33
mdarweashupdated their account properties
2018/06/08 00:47:33
| account | mdarweash |
| memo key | STM5Rs9q7jYyqPZX44NYXxSQEVhi3kCbaKQMn5hQa1HCNAQA4XV9z |
| json metadata | {"profile":{"profile_image":"https://cdn.steemitimages.com/DQmRBBFESnca5t7ikMZN9irrNwvZXcobQiKyjvTbwQfvPPb/Mdarweash.JPG","name":"MDarweash","about":"- Serial Entrepreneur - Signed Patent Contract with Dr.Hatem Zaghloul regarding BLE multihop networking protocol patent - Developed/Consulted 30+ Mobile Appli","location":"Kuala Lumpur"}} |
| Transaction Info | Block #23128324/Trx bdcf6caf170cbd7a15b8ddfa60eee3bf2d08cb37 |
View Raw JSON Data
{
"trx_id": "bdcf6caf170cbd7a15b8ddfa60eee3bf2d08cb37",
"block": 23128324,
"trx_in_block": 46,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-08T00:47:33",
"op": [
"account_update",
{
"account": "mdarweash",
"memo_key": "STM5Rs9q7jYyqPZX44NYXxSQEVhi3kCbaKQMn5hQa1HCNAQA4XV9z",
"json_metadata": "{\"profile\":{\"profile_image\":\"https://cdn.steemitimages.com/DQmRBBFESnca5t7ikMZN9irrNwvZXcobQiKyjvTbwQfvPPb/Mdarweash.JPG\",\"name\":\"MDarweash\",\"about\":\"- Serial Entrepreneur - Signed Patent Contract with Dr.Hatem Zaghloul regarding BLE multihop networking protocol patent - Developed/Consulted 30+ Mobile Appli\",\"location\":\"Kuala Lumpur\"}}"
}
]
}2018/06/08 00:46:30
2018/06/08 00:46:30
| parent author | mdarweash |
| parent permlink | bluetooth-low-energy-is-not-just-a-bluetooth-upgrade |
| author | cheetah |
| permlink | cheetah-re-mdarweashbluetooth-low-energy-is-not-just-a-bluetooth-upgrade |
| title | |
| body | Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in: https://www.linkedin.com/pulse/bluetooth-low-energy-just-upgrade-techbizecho-mahmoud-darweash |
| json metadata | |
| Transaction Info | Block #23128303/Trx a39e16120a98c855feddced8bdce83c31d505752 |
View Raw JSON Data
{
"trx_id": "a39e16120a98c855feddced8bdce83c31d505752",
"block": 23128303,
"trx_in_block": 30,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-08T00:46:30",
"op": [
"comment",
{
"parent_author": "mdarweash",
"parent_permlink": "bluetooth-low-energy-is-not-just-a-bluetooth-upgrade",
"author": "cheetah",
"permlink": "cheetah-re-mdarweashbluetooth-low-energy-is-not-just-a-bluetooth-upgrade",
"title": "",
"body": "Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in:\nhttps://www.linkedin.com/pulse/bluetooth-low-energy-just-upgrade-techbizecho-mahmoud-darweash",
"json_metadata": ""
}
]
}cheetahupvoted (0.08%) @mdarweash / bluetooth-low-energy-is-not-just-a-bluetooth-upgrade2018/06/08 00:46:24
cheetahupvoted (0.08%) @mdarweash / bluetooth-low-energy-is-not-just-a-bluetooth-upgrade
2018/06/08 00:46:24
| voter | cheetah |
| author | mdarweash |
| permlink | bluetooth-low-energy-is-not-just-a-bluetooth-upgrade |
| weight | 8 (0.08%) |
| Transaction Info | Block #23128301/Trx cb0bd6c7baca60f8d94c20d25ef35e662654d089 |
View Raw JSON Data
{
"trx_id": "cb0bd6c7baca60f8d94c20d25ef35e662654d089",
"block": 23128301,
"trx_in_block": 10,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-08T00:46:24",
"op": [
"vote",
{
"voter": "cheetah",
"author": "mdarweash",
"permlink": "bluetooth-low-energy-is-not-just-a-bluetooth-upgrade",
"weight": 8
}
]
}ax3upvoted (1.00%) @mdarweash / bluetooth-low-energy-is-not-just-a-bluetooth-upgrade2018/06/08 00:46:18
ax3upvoted (1.00%) @mdarweash / bluetooth-low-energy-is-not-just-a-bluetooth-upgrade
2018/06/08 00:46:18
| voter | ax3 |
| author | mdarweash |
| permlink | bluetooth-low-energy-is-not-just-a-bluetooth-upgrade |
| weight | 100 (1.00%) |
| Transaction Info | Block #23128299/Trx 25f61b7d456b7048c53db28899f4d8be34e8b29d |
View Raw JSON Data
{
"trx_id": "25f61b7d456b7048c53db28899f4d8be34e8b29d",
"block": 23128299,
"trx_in_block": 51,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-08T00:46:18",
"op": [
"vote",
{
"voter": "ax3",
"author": "mdarweash",
"permlink": "bluetooth-low-energy-is-not-just-a-bluetooth-upgrade",
"weight": 100
}
]
}mdarweashpublished a new post: bluetooth-low-energy-is-not-just-a-bluetooth-upgrade2018/06/08 00:46:09
mdarweashpublished a new post: bluetooth-low-energy-is-not-just-a-bluetooth-upgrade
2018/06/08 00:46:09
| parent author | |
| parent permlink | beacons |
| author | mdarweash |
| permlink | bluetooth-low-energy-is-not-just-a-bluetooth-upgrade |
| title | Bluetooth Low Energy is not just a Bluetooth Upgrade! |
| body | Introduction Did you hear about Bluetooth low energy? Beacon ? all of these terms are for the same thing. a small device that can run on coin cell battery for months or years. 4,486,000 Sensors deployed globally by May 2017. can you digest the number? the industry is huge. and that's we need to understand how Technology is recreating the business Ecosystem What's Bluetooth Low Energy? Bluetooth 1.0 was introduced 1999. versions kept rolling out. But in 2011 something big happened, Which is Bluetooth 4.0 that included Bluetooth Low Energy. BLE added a new dimension for the wireless communication and opened a new era for an innovative set of applications. Bluetooth low energy wasn’t about extending range, or enhancing data rate or even enhancing power consumption. It has created a whole new concept in wireless communication. And that’s why Bluetooth low energy isn’t just an upgrade for the previous Bluetooth version. Even as a communication architecture and software stack. Developers have to rewrite their applications to comply with Bluetooth low energy as your application isn’t upgraded to BLE when you replace your Bluetooth V3.0 device with Bluetooth V4.0. your application must operate in a different way. Bluetooth Low Energy vs Bluetooth Classic This is a technically deep question with lots of details but we will try to crack it in the terms that affect your technical/business decision. Bluetooth Classic is connection oriented. This means that you can’t exchange a byte before establishing a connection. Establishing a connection Bluetooth classic has some solid steps that you have to pass through - Discovery of nearby devices that mark themselves as visible - Discover profiles by the target device to communicate with - Establishment of a connection between source and target practically speaking, this process takes from 3 up to 15 seconds according to lots of variables. Data rates can exceed 1Mbs in real actions. Thus, it’s suitable for applications that are data hungry like audio devices, printers, Internet tethering...etc. Cons of Bluetooth classic are size, power, and price. Relatively the hardware size is larger than Bluetooth low chips as the Bluetooth classic software stack is much more complex than the BLE one. Higher complexity means more resources required to handle thus, higher cost and power consumption :) On the other hand, Bluetooth low has two different ways of communication. Connection oriented and connectionless. In the connectionless mode, the BLE sender just broadcasts the data around and every listener can pick it without the need to initiate a connection. Thus, faster data exchange and lower power consumption. In BLE, connections are simpler than Bluetooth classic. There are no profiles. To start a connection the source waits for a packet indicating that target is accepting the connection (Connectable advertising packet) then send a request packet to the target. The target stops advertising and establishes a private connection. We need to add two important pieces of information here. - For connectionless data transmission, there’s a limited size for the developers to use - in Bluetooth V4.x it’s 33 bytes! Yes, only 33 bytes :) - in Bluetooth V5.x it’s 256 bytes! For , the bandwidth is limited. Barely you can reach ~125kbit/s it best circumstances. Thus, this bandwidth won’t transmit large data buckets well. don’t expect media streaming as easy as Bluetooth classic :) So, it’s clear now that they are two completely different technologies with different pros and cons. Each of them is required in different situations. Which is also far away from the WiFi domain as lots of people thought that Bluetooth will eat up WiFi. We may talk about this in a different article. Now, do you still think about BLE like you think before? Tell us your story with BLE and I’m ready for any Questions :) |
| json metadata | {"tags":["beacons","bluetooth","ble","low-power"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #23128296/Trx e7826e7332aafdc4d56030d0ac684734eb2ae47b |
View Raw JSON Data
{
"trx_id": "e7826e7332aafdc4d56030d0ac684734eb2ae47b",
"block": 23128296,
"trx_in_block": 36,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-08T00:46:09",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "beacons",
"author": "mdarweash",
"permlink": "bluetooth-low-energy-is-not-just-a-bluetooth-upgrade",
"title": "Bluetooth Low Energy is not just a Bluetooth Upgrade!",
"body": "Introduction\n\nDid you hear about Bluetooth low energy? Beacon ? all of these terms are for the same thing. a small device that can run on coin cell battery for months or years.\n\n4,486,000 Sensors deployed globally by May 2017. can you digest the number? the industry is huge. and that's we need to understand how Technology is recreating the business Ecosystem\nWhat's Bluetooth Low Energy?\n\nBluetooth 1.0 was introduced 1999. versions kept rolling out. But in 2011 something big happened, Which is Bluetooth 4.0 that included Bluetooth Low Energy. BLE added a new dimension for the wireless communication and opened a new era for an innovative set of applications.\n\nBluetooth low energy wasn’t about extending range, or enhancing data rate or even enhancing power consumption. It has created a whole new concept in wireless communication. And that’s why Bluetooth low energy isn’t just an upgrade for the previous Bluetooth version. Even as a communication architecture and software stack. Developers have to rewrite their applications to comply with Bluetooth low energy as your application isn’t upgraded to BLE when you replace your Bluetooth V3.0 device with Bluetooth V4.0. your application must operate in a different way.\nBluetooth Low Energy vs Bluetooth Classic\n\nThis is a technically deep question with lots of details but we will try to crack it in the terms that affect your technical/business decision.\n\nBluetooth Classic is connection oriented. This means that you can’t exchange a byte before establishing a connection. Establishing a connection Bluetooth classic has some solid steps that you have to pass through\n\n- Discovery of nearby devices that mark themselves as visible\n- Discover profiles by the target device to communicate with\n- Establishment of a connection between source and target\n\npractically speaking, this process takes from 3 up to 15 seconds according to lots of variables. Data rates can exceed 1Mbs in real actions. Thus, it’s suitable for applications that are data hungry like audio devices, printers, Internet tethering...etc.\n\nCons of Bluetooth classic are size, power, and price. Relatively the hardware size is larger than Bluetooth low chips as the Bluetooth classic software stack is much more complex than the BLE one. Higher complexity means more resources required to handle thus, higher cost and power consumption :)\n\nOn the other hand, Bluetooth low has two different ways of communication. Connection oriented and connectionless. In the connectionless mode, the BLE sender just broadcasts the data around and every listener can pick it without the need to initiate a connection. Thus, faster data exchange and lower power consumption.\n\nIn BLE, connections are simpler than Bluetooth classic. There are no profiles. To start a connection the source waits for a packet indicating that target is accepting the connection (Connectable advertising packet) then send a request packet to the target. The target stops advertising and establishes a private connection.\n\nWe need to add two important pieces of information here.\n\n- For connectionless data transmission, there’s a limited size for the developers to use\n- in Bluetooth V4.x it’s 33 bytes! Yes, only 33 bytes :)\n- in Bluetooth V5.x it’s 256 bytes!\n \nFor , the bandwidth is limited. Barely you can reach ~125kbit/s it best circumstances. Thus, this bandwidth won’t transmit large data buckets well. don’t expect media streaming as easy as Bluetooth classic :)\n\nSo, it’s clear now that they are two completely different technologies with different pros and cons. Each of them is required in different situations. Which is also far away from the WiFi domain as lots of people thought that Bluetooth will eat up WiFi. We may talk about this in a different article.\n\nNow, do you still think about BLE like you think before? Tell us your story with BLE and I’m ready for any Questions :)",
"json_metadata": "{\"tags\":[\"beacons\",\"bluetooth\",\"ble\",\"low-power\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}steemcreated a new account: @mdarweash2018/06/08 00:02:51
steemcreated a new account: @mdarweash
2018/06/08 00:02:51
| fee | 0.100 STEEM |
| delegation | 30690.000000 VESTS |
| creator | steem |
| new account name | mdarweash |
| owner | {"weight_threshold":1,"account_auths":[],"key_auths":[["STM7yWQ5dCydoBCBAGN8pkA9pNgdAC7tE9FrFRTgXA6bRBZDgreW3",1]]} |
| active | {"weight_threshold":1,"account_auths":[],"key_auths":[["STM5krVU4jZ34ggHckEbPEAWJzCLGDrnfWKn4X6ykBD1Wye4p4Xxb",1]]} |
| posting | {"weight_threshold":1,"account_auths":[],"key_auths":[["STM5rK2Wd2UMXqyKk3vqmcHC2MgAsZ5Du7QY5nG5j1i1DWbZ9DDtm",1]]} |
| memo key | STM5Rs9q7jYyqPZX44NYXxSQEVhi3kCbaKQMn5hQa1HCNAQA4XV9z |
| json metadata | {} |
| extensions | [] |
| Transaction Info | Block #23127430/Trx b02daa86b534b1a85ef8ae613616ea00ece95c71 |
View Raw JSON Data
{
"trx_id": "b02daa86b534b1a85ef8ae613616ea00ece95c71",
"block": 23127430,
"trx_in_block": 14,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-08T00:02:51",
"op": [
"account_create_with_delegation",
{
"fee": "0.100 STEEM",
"delegation": "30690.000000 VESTS",
"creator": "steem",
"new_account_name": "mdarweash",
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7yWQ5dCydoBCBAGN8pkA9pNgdAC7tE9FrFRTgXA6bRBZDgreW3",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5krVU4jZ34ggHckEbPEAWJzCLGDrnfWKn4X6ykBD1Wye4p4Xxb",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5rK2Wd2UMXqyKk3vqmcHC2MgAsZ5Du7QY5nG5j1i1DWbZ9DDtm",
1
]
]
},
"memo_key": "STM5Rs9q7jYyqPZX44NYXxSQEVhi3kCbaKQMn5hQa1HCNAQA4XV9z",
"json_metadata": "{}",
"extensions": []
}
]
}Manabar
Voting Power100.00%
Downvote Power100.00%
Resource Credits100.00%
Reputation Progress0.00%
{
"voting_manabar": {
"current_mana": 10000,
"last_update_time": 1528416171
},
"downvote_manabar": {
"current_mana": 0,
"last_update_time": 1528416171
},
"rc_account": {
"account": "mdarweash",
"rc_manabar": {
"current_mana": "81305059356",
"last_update_time": 1537887600
},
"max_rc_creation_adjustment": {
"amount": "2020748973",
"precision": 6,
"nai": "@@000000037"
},
"max_rc": "81305059356"
}
}Account Metadata
| POSTING JSON METADATA | |
| profile | {"profile_image":"https://cdn.steemitimages.com/DQmRBBFESnca5t7ikMZN9irrNwvZXcobQiKyjvTbwQfvPPb/Mdarweash.JPG","name":"MDarweash","about":"- Serial Entrepreneur - Signed Patent Contract with Dr.Hatem Zaghloul regarding BLE multihop networking protocol patent - Developed/Consulted 30+ Mobile Appli","location":"Kuala Lumpur"} |
| JSON METADATA | |
| profile | {"profile_image":"https://cdn.steemitimages.com/DQmRBBFESnca5t7ikMZN9irrNwvZXcobQiKyjvTbwQfvPPb/Mdarweash.JPG","name":"MDarweash","about":"- Serial Entrepreneur - Signed Patent Contract with Dr.Hatem Zaghloul regarding BLE multihop networking protocol patent - Developed/Consulted 30+ Mobile Appli","location":"Kuala Lumpur"} |
{
"posting_json_metadata": {
"profile": {
"profile_image": "https://cdn.steemitimages.com/DQmRBBFESnca5t7ikMZN9irrNwvZXcobQiKyjvTbwQfvPPb/Mdarweash.JPG",
"name": "MDarweash",
"about": "- Serial Entrepreneur - Signed Patent Contract with Dr.Hatem Zaghloul regarding BLE multihop networking protocol patent - Developed/Consulted 30+ Mobile Appli",
"location": "Kuala Lumpur"
}
},
"json_metadata": {
"profile": {
"profile_image": "https://cdn.steemitimages.com/DQmRBBFESnca5t7ikMZN9irrNwvZXcobQiKyjvTbwQfvPPb/Mdarweash.JPG",
"name": "MDarweash",
"about": "- Serial Entrepreneur - Signed Patent Contract with Dr.Hatem Zaghloul regarding BLE multihop networking protocol patent - Developed/Consulted 30+ Mobile Appli",
"location": "Kuala Lumpur"
}
}
}Auth Keys
Owner
Single Signature
Public Keys
STM7yWQ5dCydoBCBAGN8pkA9pNgdAC7tE9FrFRTgXA6bRBZDgreW31/1
Active
Single Signature
Public Keys
STM5krVU4jZ34ggHckEbPEAWJzCLGDrnfWKn4X6ykBD1Wye4p4Xxb1/1
Posting
Single Signature
Public Keys
STM5rK2Wd2UMXqyKk3vqmcHC2MgAsZ5Du7QY5nG5j1i1DWbZ9DDtm1/1
Memo
STM5Rs9q7jYyqPZX44NYXxSQEVhi3kCbaKQMn5hQa1HCNAQA4XV9z
{
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7yWQ5dCydoBCBAGN8pkA9pNgdAC7tE9FrFRTgXA6bRBZDgreW3",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5krVU4jZ34ggHckEbPEAWJzCLGDrnfWKn4X6ykBD1Wye4p4Xxb",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5rK2Wd2UMXqyKk3vqmcHC2MgAsZ5Du7QY5nG5j1i1DWbZ9DDtm",
1
]
]
},
"memo": "STM5Rs9q7jYyqPZX44NYXxSQEVhi3kCbaKQMn5hQa1HCNAQA4XV9z"
}Witness Votes
0 / 30
No active witness votes.
[]