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

Detailed Balance

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

Account Info

namealiyeve
id392577
rank1,456,676
reputation104886970
created2017-10-03T08:03:33
recovery_accountsteem
proxyNone
post_count7
comment_count0
lifetime_vote_count0
witnesses_voted_for0
last_post2017-10-27T14:58:51
last_root_post2017-10-27T14:58:51
last_vote_time2017-10-27T14:58:51
proxied_vsf_votes0, 0, 0, 0
can_vote1
voting_power0
delayed_votes0
balance0.000 STEEM
savings_balance0.000 STEEM
sbd_balance0.000 SBD
savings_sbd_balance0.000 SBD
vesting_shares1029.272604 VESTS
delegated_vesting_shares0.000000 VESTS
received_vesting_shares7114.387202 VESTS
reward_vesting_balance0.000000 VESTS
vesting_balance0.000 STEEM
vesting_withdraw_rate0.000000 VESTS
next_vesting_withdrawal1969-12-31T23:59:59
withdrawn0
to_withdraw0
withdraw_routes0
savings_withdraw_requests0
last_account_recovery1970-01-01T00:00:00
reset_accountnull
last_owner_update1970-01-01T00:00:00
last_account_update1970-01-01T00:00:00
minedNo
sbd_seconds0
sbd_last_interest_payment1970-01-01T00:00:00
savings_sbd_last_interest_payment1970-01-01T00:00:00
{
  "active": {
    "account_auths": [],
    "key_auths": [
      [
        "STM6gsyAySHybFPHPLNKkTjC6QA3jVjiBjK4bYGgLDMwYKCCJL1Ra",
        1
      ]
    ],
    "weight_threshold": 1
  },
  "balance": "0.000 STEEM",
  "can_vote": true,
  "comment_count": 0,
  "created": "2017-10-03T08:03:33",
  "curation_rewards": 0,
  "delegated_vesting_shares": "0.000000 VESTS",
  "downvote_manabar": {
    "current_mana": 2035914951,
    "last_update_time": 1779052341
  },
  "guest_bloggers": [],
  "id": 392577,
  "json_metadata": "",
  "last_account_recovery": "1970-01-01T00:00:00",
  "last_account_update": "1970-01-01T00:00:00",
  "last_owner_update": "1970-01-01T00:00:00",
  "last_post": "2017-10-27T14:58:51",
  "last_root_post": "2017-10-27T14:58:51",
  "last_vote_time": "2017-10-27T14:58:51",
  "lifetime_vote_count": 0,
  "market_history": [],
  "memo_key": "STM835eM3mLrC4xsT1sv1URRV92guDCKxGSPsDzf4r7gatgi641Qh",
  "mined": false,
  "name": "aliyeve",
  "next_vesting_withdrawal": "1969-12-31T23:59:59",
  "other_history": [],
  "owner": {
    "account_auths": [],
    "key_auths": [
      [
        "STM6PuJY7gsqWUS8SWBjZqh3w81GBUMsk3yh3i5PzP8JyqRE4dfao",
        1
      ]
    ],
    "weight_threshold": 1
  },
  "pending_claimed_accounts": 0,
  "post_bandwidth": 0,
  "post_count": 7,
  "post_history": [],
  "posting": {
    "account_auths": [],
    "key_auths": [
      [
        "STM5GZ7jxNFDW6GcYgHfFwgZ66MxkzftDzHmDe2SAZgUihVn2hBsd",
        1
      ]
    ],
    "weight_threshold": 1
  },
  "posting_json_metadata": "",
  "posting_rewards": 0,
  "proxied_vsf_votes": [
    0,
    0,
    0,
    0
  ],
  "proxy": "",
  "received_vesting_shares": "7114.387202 VESTS",
  "recovery_account": "steem",
  "reputation": 104886970,
  "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": 0,
  "transfer_history": [],
  "vesting_balance": "0.000 STEEM",
  "vesting_shares": "1029.272604 VESTS",
  "vesting_withdraw_rate": "0.000000 VESTS",
  "vote_history": [],
  "voting_manabar": {
    "current_mana": "8143659806",
    "last_update_time": 1779052341
  },
  "voting_power": 0,
  "withdraw_routes": 0,
  "withdrawn": 0,
  "witness_votes": [],
  "witnesses_voted_for": 0,
  "rank": 1456676
}

Withdraw Routes

IncomingOutgoing
Empty
Empty
{
  "incoming": [],
  "outgoing": []
}
From Date
To Date
steemdelegated 4.374 SP to @aliyeve
2026/05/17 21:12:21
delegateealiyeve
delegatorsteem
vesting shares7114.387202 VESTS
Transaction InfoBlock #106139807/Trx 459b193f6e9436e7819792e6edb8e3aa79271449
View Raw JSON Data
{
  "block": 106139807,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "aliyeve",
      "delegator": "steem",
      "vesting_shares": "7114.387202 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2026-05-17T21:12:21",
  "trx_id": "459b193f6e9436e7819792e6edb8e3aa79271449",
  "trx_in_block": 1,
  "virtual_op": 0
}
steemdelegated 2.707 SP to @aliyeve
2026/05/11 17:14:54
delegateealiyeve
delegatorsteem
vesting shares4402.176797 VESTS
Transaction InfoBlock #105963036/Trx d8fafd2ab82d1acbde96e19f52f035b78e3128f7
View Raw JSON Data
{
  "block": 105963036,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "aliyeve",
      "delegator": "steem",
      "vesting_shares": "4402.176797 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2026-05-11T17:14:54",
  "trx_id": "d8fafd2ab82d1acbde96e19f52f035b78e3128f7",
  "trx_in_block": 0,
  "virtual_op": 0
}
steemdelegated 4.382 SP to @aliyeve
2026/04/25 20:38:00
delegateealiyeve
delegatorsteem
vesting shares7126.902958 VESTS
Transaction InfoBlock #105507546/Trx 652c5c805a017767d044bbcc15ca9749be9a7898
View Raw JSON Data
{
  "block": 105507546,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "aliyeve",
      "delegator": "steem",
      "vesting_shares": "7126.902958 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2026-04-25T20:38:00",
  "trx_id": "652c5c805a017767d044bbcc15ca9749be9a7898",
  "trx_in_block": 0,
  "virtual_op": 0
}
steemdelegated 2.732 SP to @aliyeve
2026/01/22 23:40:48
delegateealiyeve
delegatorsteem
vesting shares4443.723616 VESTS
Transaction InfoBlock #102842086/Trx f28753ec747f547d8bee539f7c44b451b6e88f46
View Raw JSON Data
{
  "block": 102842086,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "aliyeve",
      "delegator": "steem",
      "vesting_shares": "4443.723616 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2026-01-22T23:40:48",
  "trx_id": "f28753ec747f547d8bee539f7c44b451b6e88f46",
  "trx_in_block": 1,
  "virtual_op": 0
}
steemdelegated 2.833 SP to @aliyeve
2024/12/16 19:01:39
delegateealiyeve
delegatorsteem
vesting shares4607.942813 VESTS
Transaction InfoBlock #91288529/Trx 10640cf34c04fd07dc30ff6b470cf4531be66bea
View Raw JSON Data
{
  "block": 91288529,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "aliyeve",
      "delegator": "steem",
      "vesting_shares": "4607.942813 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2024-12-16T19:01:39",
  "trx_id": "10640cf34c04fd07dc30ff6b470cf4531be66bea",
  "trx_in_block": 4,
  "virtual_op": 0
}
steemdelegated 2.937 SP to @aliyeve
2023/11/13 10:47:45
delegateealiyeve
delegatorsteem
vesting shares4777.076345 VESTS
Transaction InfoBlock #79842810/Trx 8bb85d82a2b2ff946664e0128859e94107ff3a3a
View Raw JSON Data
{
  "block": 79842810,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "aliyeve",
      "delegator": "steem",
      "vesting_shares": "4777.076345 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2023-11-13T10:47:45",
  "trx_id": "8bb85d82a2b2ff946664e0128859e94107ff3a3a",
  "trx_in_block": 1,
  "virtual_op": 0
}
steemdelegated 4.743 SP to @aliyeve
2023/09/21 18:15:09
delegateealiyeve
delegatorsteem
vesting shares7714.355131 VESTS
Transaction InfoBlock #78343555/Trx 86b85b35ca23b47872ac5d83768122014529cc1c
View Raw JSON Data
{
  "block": 78343555,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "aliyeve",
      "delegator": "steem",
      "vesting_shares": "7714.355131 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2023-09-21T18:15:09",
  "trx_id": "86b85b35ca23b47872ac5d83768122014529cc1c",
  "trx_in_block": 0,
  "virtual_op": 0
}
steemdelegated 4.880 SP to @aliyeve
2022/11/03 08:28:06
delegateealiyeve
delegatorsteem
vesting shares7936.036569 VESTS
Transaction InfoBlock #69109396/Trx 8af44faeac6417c426e79bff51f8f69c781d846c
View Raw JSON Data
{
  "block": 69109396,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "aliyeve",
      "delegator": "steem",
      "vesting_shares": "7936.036569 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2022-11-03T08:28:06",
  "trx_id": "8af44faeac6417c426e79bff51f8f69c781d846c",
  "trx_in_block": 9,
  "virtual_op": 0
}
steemdelegated 5.015 SP to @aliyeve
2022/01/17 08:01:09
delegateealiyeve
delegatorsteem
vesting shares8156.569800 VESTS
Transaction InfoBlock #60805911/Trx a760a39959b6777c3b4353abfa0ddd9994cc74df
View Raw JSON Data
{
  "block": 60805911,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "aliyeve",
      "delegator": "steem",
      "vesting_shares": "8156.569800 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2022-01-17T08:01:09",
  "trx_id": "a760a39959b6777c3b4353abfa0ddd9994cc74df",
  "trx_in_block": 39,
  "virtual_op": 0
}
steemdelegated 5.128 SP to @aliyeve
2021/06/13 22:03:42
delegateealiyeve
delegatorsteem
vesting shares8340.338458 VESTS
Transaction InfoBlock #54604447/Trx 08f2659ba5ab3ce9e6cf35d797d7258611b6870c
View Raw JSON Data
{
  "block": 54604447,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "aliyeve",
      "delegator": "steem",
      "vesting_shares": "8340.338458 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2021-06-13T22:03:42",
  "trx_id": "08f2659ba5ab3ce9e6cf35d797d7258611b6870c",
  "trx_in_block": 8,
  "virtual_op": 0
}
steemdelegated 5.243 SP to @aliyeve
2020/12/11 08:26:36
delegateealiyeve
delegatorsteem
vesting shares8527.760432 VESTS
Transaction InfoBlock #49352019/Trx 07687ccee58fefe144d0ea113fd9af81d503e60c
View Raw JSON Data
{
  "block": 49352019,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "aliyeve",
      "delegator": "steem",
      "vesting_shares": "8527.760432 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-12-11T08:26:36",
  "trx_id": "07687ccee58fefe144d0ea113fd9af81d503e60c",
  "trx_in_block": 0,
  "virtual_op": 0
}
steemdelegated 1.176 SP to @aliyeve
2020/12/06 02:04:03
delegateealiyeve
delegatorsteem
vesting shares1912.543513 VESTS
Transaction InfoBlock #49203587/Trx a00fc2b6c267b0cad7cec1e7a3e86912d89b006c
View Raw JSON Data
{
  "block": 49203587,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "aliyeve",
      "delegator": "steem",
      "vesting_shares": "1912.543513 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-12-06T02:04:03",
  "trx_id": "a00fc2b6c267b0cad7cec1e7a3e86912d89b006c",
  "trx_in_block": 6,
  "virtual_op": 0
}
steemdelegated 5.254 SP to @aliyeve
2020/11/25 15:15:00
delegateealiyeve
delegatorsteem
vesting shares8544.887049 VESTS
Transaction InfoBlock #48907043/Trx 5c433d64c268ba01b4634c082938d54da8a9764e
View Raw JSON Data
{
  "block": 48907043,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "aliyeve",
      "delegator": "steem",
      "vesting_shares": "8544.887049 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-11-25T15:15:00",
  "trx_id": "5c433d64c268ba01b4634c082938d54da8a9764e",
  "trx_in_block": 1,
  "virtual_op": 0
}
steemdelegated 5.372 SP to @aliyeve
2020/05/09 02:58:45
delegateealiyeve
delegatorsteem
vesting shares8736.773645 VESTS
Transaction InfoBlock #43213800/Trx 4af538e25314019c6f8ff559591c867bb6a211ce
View Raw JSON Data
{
  "block": 43213800,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "aliyeve",
      "delegator": "steem",
      "vesting_shares": "8736.773645 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-05-09T02:58:45",
  "trx_id": "4af538e25314019c6f8ff559591c867bb6a211ce",
  "trx_in_block": 20,
  "virtual_op": 0
}
steemdelegated 1.201 SP to @aliyeve
2020/05/08 06:09:42
delegateealiyeve
delegatorsteem
vesting shares1953.311140 VESTS
Transaction InfoBlock #43189404/Trx fa7db9a9de7f4a7fb6d784f866430ec673b2332b
View Raw JSON Data
{
  "block": 43189404,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "aliyeve",
      "delegator": "steem",
      "vesting_shares": "1953.311140 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-05-08T06:09:42",
  "trx_id": "fa7db9a9de7f4a7fb6d784f866430ec673b2332b",
  "trx_in_block": 3,
  "virtual_op": 0
}
steemdelegated 5.380 SP to @aliyeve
2020/04/15 17:32:51
delegateealiyeve
delegatorsteem
vesting shares8749.808662 VESTS
Transaction InfoBlock #42557839/Trx aed5ca8a89f7f540429b94456e5d96be87a5383b
View Raw JSON Data
{
  "block": 42557839,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "aliyeve",
      "delegator": "steem",
      "vesting_shares": "8749.808662 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-04-15T17:32:51",
  "trx_id": "aed5ca8a89f7f540429b94456e5d96be87a5383b",
  "trx_in_block": 2,
  "virtual_op": 0
}
2019/10/03 09:47:33
authorsteemitboard
bodyCongratulations @aliyeve! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@aliyeve/birthday2.png</td><td>Happy Birthday! - You are on the Steem blockchain for 2 years!</td></tr></table> <sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@aliyeve) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=aliyeve)_</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 authoraliyeve
parent permlink5kzl9l-i-didn-t-know-who-my-baby-s-father-was
permlinksteemitboard-notify-aliyeve-20191003t094732000z
title
Transaction InfoBlock #36957005/Trx 1d7caadc96477c60a8adc0f81c386a237eadd720
View Raw JSON Data
{
  "block": 36957005,
  "op": [
    "comment",
    {
      "author": "steemitboard",
      "body": "Congratulations @aliyeve! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@aliyeve/birthday2.png</td><td>Happy Birthday! - You are on the Steem blockchain for 2 years!</td></tr></table>\n\n<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@aliyeve) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=aliyeve)_</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": "aliyeve",
      "parent_permlink": "5kzl9l-i-didn-t-know-who-my-baby-s-father-was",
      "permlink": "steemitboard-notify-aliyeve-20191003t094732000z",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-10-03T09:47:33",
  "trx_id": "1d7caadc96477c60a8adc0f81c386a237eadd720",
  "trx_in_block": 3,
  "virtual_op": 0
}
steemdelegated 5.500 SP to @aliyeve
2019/05/12 11:05:36
delegateealiyeve
delegatorsteem
vesting shares8945.431129 VESTS
Transaction InfoBlock #32840915/Trx 5b66576d9fc2106f1c0dd583500116f92b318d5b
View Raw JSON Data
{
  "block": 32840915,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "aliyeve",
      "delegator": "steem",
      "vesting_shares": "8945.431129 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-05-12T11:05:36",
  "trx_id": "5b66576d9fc2106f1c0dd583500116f92b318d5b",
  "trx_in_block": 9,
  "virtual_op": 0
}
2018/10/03 15:01:39
authorsteemitboard
bodyCongratulations @aliyeve! You have received a personal award! [![](https://steemitimages.com/70x70/http://steemitboard.com/@aliyeve/birthday1.png)](http://steemitboard.com/@aliyeve) 1 Year on Steemit <sub>_Click on the badge to view your Board of Honor._</sub> **Do not miss the last post from @steemitboard:** <table><tr><td><a href="https://steemit.com/steemitboard/@steemitboard/steemitboard-knock-out-by-hardfork"><img src="https://steemitimages.com/64x128/https://cdn.steemitimages.com/DQmSPagmBYytsJBn8FwewvqDFRphP6swbbndADgYEsaLNkZ/image.png"></a></td><td><a href="https://steemit.com/steemitboard/@steemitboard/steemitboard-knock-out-by-hardfork">SteemitBoard knock out by hardfork</a></td></tr></table> > Support [SteemitBoard's project](https://steemit.com/@steemitboard)! **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**!
json metadata{"image":["https://steemitboard.com/img/notify.png"]}
parent authoraliyeve
parent permlink5kzl9l-i-didn-t-know-who-my-baby-s-father-was
permlinksteemitboard-notify-aliyeve-20181003t150138000z
title
Transaction InfoBlock #26486853/Trx f282c68106c2c37358d1633bf4cfa97ad3537696
View Raw JSON Data
{
  "block": 26486853,
  "op": [
    "comment",
    {
      "author": "steemitboard",
      "body": "Congratulations @aliyeve! You have received a personal award!\n\n[![](https://steemitimages.com/70x70/http://steemitboard.com/@aliyeve/birthday1.png)](http://steemitboard.com/@aliyeve)  1 Year on Steemit\n<sub>_Click on the badge to view your Board of Honor._</sub>\n\n\n**Do not miss the last post from @steemitboard:**\n<table><tr><td><a href=\"https://steemit.com/steemitboard/@steemitboard/steemitboard-knock-out-by-hardfork\"><img src=\"https://steemitimages.com/64x128/https://cdn.steemitimages.com/DQmSPagmBYytsJBn8FwewvqDFRphP6swbbndADgYEsaLNkZ/image.png\"></a></td><td><a href=\"https://steemit.com/steemitboard/@steemitboard/steemitboard-knock-out-by-hardfork\">SteemitBoard knock out by hardfork</a></td></tr></table>\n\n> Support [SteemitBoard's project](https://steemit.com/@steemitboard)! **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**!",
      "json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}",
      "parent_author": "aliyeve",
      "parent_permlink": "5kzl9l-i-didn-t-know-who-my-baby-s-father-was",
      "permlink": "steemitboard-notify-aliyeve-20181003t150138000z",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-10-03T15:01:39",
  "trx_id": "f282c68106c2c37358d1633bf4cfa97ad3537696",
  "trx_in_block": 0,
  "virtual_op": 0
}
smitopblockchain operation: transfer from savings
2018/08/01 23:14:51
amount0.001 SBD
fromsmitop
memoHi, it looks like you're not voting for any witnesses. Witnesses help secure the Steem network. You should vote for some, at https://steemit.com/~witnesses, or by pressing 'Vote for witnesses' in the Steemit sidebar (top right corner). I'm a bot.
request id23028
toaliyeve
Transaction InfoBlock #24698947/Trx 014c1be6a9aad1dbfbd6541886de0433ab586934
View Raw JSON Data
{
  "block": 24698947,
  "op": [
    "transfer_from_savings",
    {
      "amount": "0.001 SBD",
      "from": "smitop",
      "memo": "Hi, it looks like you're not voting for any witnesses. Witnesses help secure the Steem network. You should vote for some, at https://steemit.com/~witnesses, or by pressing 'Vote for witnesses' in the Steemit sidebar (top right corner). I'm a bot.",
      "request_id": 23028,
      "to": "aliyeve"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-08-01T23:14:51",
  "trx_id": "014c1be6a9aad1dbfbd6541886de0433ab586934",
  "trx_in_block": 1,
  "virtual_op": 0
}
steemdelegated 5.623 SP to @aliyeve
2018/05/16 19:06:03
delegateealiyeve
delegatorsteem
vesting shares9144.948109 VESTS
Transaction InfoBlock #22488423/Trx 7b016c72ebff5f89b61692f9ac253681a73b4bbe
View Raw JSON Data
{
  "block": 22488423,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "aliyeve",
      "delegator": "steem",
      "vesting_shares": "9144.948109 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-05-16T19:06:03",
  "trx_id": "7b016c72ebff5f89b61692f9ac253681a73b4bbe",
  "trx_in_block": 1,
  "virtual_op": 0
}
steemdelegated 18.217 SP to @aliyeve
2018/02/21 23:02:15
delegateealiyeve
delegatorsteem
vesting shares29627.743978 VESTS
Transaction InfoBlock #20076475/Trx 7e4f1d5be3acf3eccc36fb0e14595882ed7511f7
View Raw JSON Data
{
  "block": 20076475,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "aliyeve",
      "delegator": "steem",
      "vesting_shares": "29627.743978 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-02-21T23:02:15",
  "trx_id": "7e4f1d5be3acf3eccc36fb0e14595882ed7511f7",
  "trx_in_block": 51,
  "virtual_op": 0
}
2017/10/28 11:58:45
authorsteemitboard
bodyCongratulations @aliyeve! You have completed some achievement on Steemit and have been rewarded with new badge(s) : [![](https://steemitimages.com/70x80/http://steemitboard.com/notifications/firstpost.png)](http://steemitboard.com/@aliyeve) You published your First Post [![](https://steemitimages.com/70x80/http://steemitboard.com/notifications/firstvoted.png)](http://steemitboard.com/@aliyeve) You got a First Vote [![](https://steemitimages.com/70x80/http://steemitboard.com/notifications/votes.png)](http://steemitboard.com/@aliyeve) Award for the number of upvotes [![](https://steemitimages.com/70x80/http://steemitboard.com/notifications/voted.png)](http://steemitboard.com/@aliyeve) Award for the number of upvotes received [![](https://steemitimages.com/70x80/http://steemitboard.com/notifications/post4day.png)](http://steemitboard.com/@aliyeve) You published 4 posts in one day Click on any badge to view your own Board of Honor on SteemitBoard. For more information about SteemitBoard, click [here](https://steemit.com/@steemitboard) If you no longer want to receive notifications, reply to this comment with the word `STOP` > By upvoting this notification, you can help all Steemit users. Learn how [here](https://steemit.com/steemitboard/@steemitboard/http-i-cubeupload-com-7ciqeo-png)!
json metadata{"image":["https://steemitboard.com/img/notifications.png"]}
parent authoraliyeve
parent permlink5kzl9l-i-didn-t-know-who-my-baby-s-father-was
permlinksteemitboard-notify-aliyeve-20171028t115847000z
title
Transaction InfoBlock #16724745/Trx df7fff53c31e20c64a945a28a0ce8a49bfa69233
View Raw JSON Data
{
  "block": 16724745,
  "op": [
    "comment",
    {
      "author": "steemitboard",
      "body": "Congratulations @aliyeve! You have completed some achievement on Steemit and have been rewarded with new badge(s) :\n\n[![](https://steemitimages.com/70x80/http://steemitboard.com/notifications/firstpost.png)](http://steemitboard.com/@aliyeve) You published your First Post\n[![](https://steemitimages.com/70x80/http://steemitboard.com/notifications/firstvoted.png)](http://steemitboard.com/@aliyeve) You got a First Vote\n[![](https://steemitimages.com/70x80/http://steemitboard.com/notifications/votes.png)](http://steemitboard.com/@aliyeve) Award for the number of upvotes\n[![](https://steemitimages.com/70x80/http://steemitboard.com/notifications/voted.png)](http://steemitboard.com/@aliyeve) Award for the number of upvotes received\n[![](https://steemitimages.com/70x80/http://steemitboard.com/notifications/post4day.png)](http://steemitboard.com/@aliyeve) You published 4 posts in one day\n\nClick on any badge to view your own Board of Honor on SteemitBoard.\nFor more information about SteemitBoard, click [here](https://steemit.com/@steemitboard)\n\nIf you no longer want to receive notifications, reply to this comment with the word `STOP`\n\n> By upvoting this notification, you can help all Steemit users. Learn how [here](https://steemit.com/steemitboard/@steemitboard/http-i-cubeupload-com-7ciqeo-png)!",
      "json_metadata": "{\"image\":[\"https://steemitboard.com/img/notifications.png\"]}",
      "parent_author": "aliyeve",
      "parent_permlink": "5kzl9l-i-didn-t-know-who-my-baby-s-father-was",
      "permlink": "steemitboard-notify-aliyeve-20171028t115847000z",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-10-28T11:58:45",
  "trx_id": "df7fff53c31e20c64a945a28a0ce8a49bfa69233",
  "trx_in_block": 15,
  "virtual_op": 0
}
2017/10/27 15:05:24
authorabay
bodyMy friend, a kind reminder here. #cn tag is stand for Chinese. However, no Chinese was detected in this article. Please use wisely for your tag,thank you
json metadata{"tags":["business","cn"],"app":"steemit/0.1"}
parent authoraliyeve
parent permlinkwe-fired-our-top-talent-best-decision-we-ever-made
permlinkre-aliyeve-we-fired-our-top-talent-best-decision-we-ever-made-20171027t150519174z
title
Transaction InfoBlock #16699740/Trx 2e867d32031a0a03e7234a5dd6c46c0b80b9fbe6
View Raw JSON Data
{
  "block": 16699740,
  "op": [
    "comment",
    {
      "author": "abay",
      "body": "My friend, a kind reminder here.\n#cn tag is stand for Chinese.\nHowever, no Chinese was detected in this article.\nPlease use wisely for your tag,thank you",
      "json_metadata": "{\"tags\":[\"business\",\"cn\"],\"app\":\"steemit/0.1\"}",
      "parent_author": "aliyeve",
      "parent_permlink": "we-fired-our-top-talent-best-decision-we-ever-made",
      "permlink": "re-aliyeve-we-fired-our-top-talent-best-decision-we-ever-made-20171027t150519174z",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-10-27T15:05:24",
  "trx_id": "2e867d32031a0a03e7234a5dd6c46c0b80b9fbe6",
  "trx_in_block": 50,
  "virtual_op": 0
}
2017/10/27 14:58:51
authoraliyeve
permlink5kzl9l-i-didn-t-know-who-my-baby-s-father-was
voteraliyeve
weight10000 (100.00%)
Transaction InfoBlock #16699609/Trx 52f6167d5b4b70dd55afcdbc06281c69e46aa908
View Raw JSON Data
{
  "block": 16699609,
  "op": [
    "vote",
    {
      "author": "aliyeve",
      "permlink": "5kzl9l-i-didn-t-know-who-my-baby-s-father-was",
      "voter": "aliyeve",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-10-27T14:58:51",
  "trx_id": "52f6167d5b4b70dd55afcdbc06281c69e46aa908",
  "trx_in_block": 3,
  "virtual_op": 0
}
2017/10/27 14:58:51
allow curation rewardstrue
allow votestrue
authoraliyeve
extensions[]
max accepted payout1000000.000 SBD
percent steem dollars0
permlink5kzl9l-i-didn-t-know-who-my-baby-s-father-was
Transaction InfoBlock #16699609/Trx 52f6167d5b4b70dd55afcdbc06281c69e46aa908
View Raw JSON Data
{
  "block": 16699609,
  "op": [
    "comment_options",
    {
      "allow_curation_rewards": true,
      "allow_votes": true,
      "author": "aliyeve",
      "extensions": [],
      "max_accepted_payout": "1000000.000 SBD",
      "percent_steem_dollars": 0,
      "permlink": "5kzl9l-i-didn-t-know-who-my-baby-s-father-was"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-10-27T14:58:51",
  "trx_id": "52f6167d5b4b70dd55afcdbc06281c69e46aa908",
  "trx_in_block": 3,
  "virtual_op": 0
}
2017/10/27 14:58:51
authoraliyeve
body![1-gzoOt0ZjcuK1N9jUZCdC5Q.jpeg](https://steemitimages.com/DQmaRwjpzDb4Wzc9xP7sM7G7EDwSsT9pMbLRZaLyCVQZjbD/1-gzoOt0ZjcuK1N9jUZCdC5Q.jpeg) In the early 1990s, Jeff Bezos noticed something strange. He was nearing 30, and it was at the dawn of the internet revolution. The web was nowhere near what it is today, but the thing that caught Bezos’ attention was that usage was picking up at a rate of 2,300% a year. Not wanting to miss out, he quickly made a list of 20 possible products to sell online, and eventually settled on shipping books because of their low cost and universal demand. Amazon may have had humble beginnings, but today, that bookstore is something far more. Since their day of incorporation in 1994, they have gone on to dominate not just retail, but other industries besides. On the surface, a few things stand out about how Bezos approached the growth of his company. He maintained a true customer obsession from the start, he never got complacent in spite of their performance, and he sacrificed short-term vanity metrics for the endgame. As we dig a little deeper, however, it’s clear that there are certain details in his execution that made the surface-level advantages possible. Every company wants to take that approach, but not all of them have the foundational decision-making framework in place to do so. Amazon may be an enormous corporation, but their core tools are simple and quite usable. Here is what we can steal. 1. Distinguish Between High and Low Impact Every day, we make big and small decisions in response to what our environment dictates. These decisions demand time and attention, and much of the stress many of us experience on a day to day basis is a result of this constant pressure on our often limited resources. And then because of this stress, we get forced and rushed into making less than optimal choices. The problem is that we intuitively judge the importance of our decisions based not on impact, but on random timing. Even if something is relatively unimportant, and even if it can wait, we feel the need to attend to it because of the surrounding circumstances. As Jeff Bezos explained to Amazon shareholders in his 2015 letter, there are two categories of decisions. Type 1 are the mission-critical, high-impact choices that influence the larger strategy, while Type 2 are the lower stakes choices that can easily be reversed if need be. At Amazon, by distinguishing between impact, they leave all Type 2 decisions to the teams and individuals on the ground, while the people higher up focus on Type 1 decisions. Given that most large companies have a very fuzzy distinction between the two, they fall into the trap of immediacy and their ability to direct resources to the truly important things suffers. It’s a simple but effective system for choosing to leverage attention to where it’s best used, because even in our own lives, it’s easy to confuse what’s important with what’s present. Most of your time should always be spent on Type 1 decisions. Type 2 decisions should either be delegated, or they should be batched together with other less critical choices for later. 2. Avoid Using Proxies as a Default With more technology, there is more automation. With more data, there is more efficiency. Companies like Amazon have access to a sheer amount of resources that can ease their load in a number of ways. They can deploy surveys and tests to collect a wealth of research and use all of that to build systems that automate many of the decisions they have to make. There are times when this is quite effective, but as Bezos points out: “Good process serves you so you can serve customers. But if you’re not watchful, the process can become the thing. This can happen very easily in large organizations. The process becomes the proxy for the result you want. You stop looking at outcomes and just make sure you’re doing the process right… The process is not the thing. It’s always worth asking, do we own the process or does the process own us?” ![1-8qJ3aoYDBDUxEL3kTDgO3A.png](https://steemitimages.com/DQmTnbXKW6NPTbbSBTdStWuFs66fqqGh4FmRFqjxQYk9PHd/1-8qJ3aoYDBDUxEL3kTDgO3A.png) Companies have different kinds of proxies than we do as individuals. Many of the processes we set up to help us automate decisions come in the form of analogies. We take shortcuts based on either an average obtained from somewhere or through the stories of others. The problem with this kind of decision-making is that it overlooks context. Granted, if you’re not learning from the wealth of knowledge we have available in this day and age, you will be left behind. That said, it’s important to cater the application of that knowledge situationally. Given the number of variables at play in any setting, it can be dangerous to think that an average or an analogy will work for you the same way that it worked for someone else. Good decisions gain their advantage because they were made with an awareness of the details. For most Type 2 decisions, proxies are helpful, but when it comes to the high-impact Type 1 decisions, it’s better to reason from ground up, taking into account each unique situation. 3. Release Ideas at 70% and Then Iterate For most decisions, after a certain point, information and time provide diminishing returns. As a general rule of thumb, the longer you take on something, the less you have to gain from taking that time, and the more you have to lose from falling behind. This doesn’t apply to every situation, but generally speaking, improvements become redundant after a while. For example, if you’re a creator or a maker of any kind, the creation is almost never going to feel perfect. Dwelling on the minor tweaks before sharing that work will eat up way more time than the yield of the potential improvements is worth. It’s far smarter to let go before you’re ready, and then iterate and improve based on the feedback. Drawing these lines not only keeps us active, but it also ensures that we don’t get attached to our choices. Any high-impact decision concerns the future, and we should account for change. Trying to make static and perfect choices in a dynamic world is a recipe for disaster. When we make choices, we think of them as individual events. It’s not at all accurate. Most choices have implications that extend over a period, and they need to be adjusted as such. For Bezos and Amazon, the line is drawn at 70% of the perceived ideal information. After that, they focus on careful corrections. This benchmark allows them to move fast, but it also ensures that there’s no compromise on the quality of that decision with too early of a release. This explains how they have been able to get into so many industries with such a strong foothold. Less time deciding means more decisions. Quantity eventually leads to quality. Correcting the wrong is less costly than not taking action, and more often than not, correction of some sort is a necessity anyway. Draw a line and use feedback to improve. All You Need to Know Decisions shape every part of our life, and the quality of our decisions determine where we end up. Having decision frameworks can help us combat any potential blind spots. Amazon is one of the most successful corporations of our day. They have many things going for them, but the key determinant of their success is arguably their decision-making process. It’s easy to neglect the idea of having a framework in place to make choices. It’s something we have an intuitive process for, but it’s useful to remember that our intuition has known gaps. Good decision-making not only removes those gaps, but it also filters signal from the noise. Call to Action The internet is filled with noise. I’ve created a free high-quality newsletter that helps people get 10x results and live better.
json metadata{"tags":["life","psychology"],"image":["https://steemitimages.com/DQmaRwjpzDb4Wzc9xP7sM7G7EDwSsT9pMbLRZaLyCVQZjbD/1-gzoOt0ZjcuK1N9jUZCdC5Q.jpeg","https://steemitimages.com/DQmTnbXKW6NPTbbSBTdStWuFs66fqqGh4FmRFqjxQYk9PHd/1-8qJ3aoYDBDUxEL3kTDgO3A.png"],"app":"steemit/0.1","format":"markdown"}
parent author
parent permlinklife
permlink5kzl9l-i-didn-t-know-who-my-baby-s-father-was
titleI Didn’t Know Who My Baby’s Father Was
Transaction InfoBlock #16699609/Trx 52f6167d5b4b70dd55afcdbc06281c69e46aa908
View Raw JSON Data
{
  "block": 16699609,
  "op": [
    "comment",
    {
      "author": "aliyeve",
      "body": "![1-gzoOt0ZjcuK1N9jUZCdC5Q.jpeg](https://steemitimages.com/DQmaRwjpzDb4Wzc9xP7sM7G7EDwSsT9pMbLRZaLyCVQZjbD/1-gzoOt0ZjcuK1N9jUZCdC5Q.jpeg)\n\nIn the early 1990s, Jeff Bezos noticed something strange.\nHe was nearing 30, and it was at the dawn of the internet revolution. The web was nowhere near what it is today, but the thing that caught Bezos’ attention was that usage was picking up at a rate of 2,300% a year.\nNot wanting to miss out, he quickly made a list of 20 possible products to sell online, and eventually settled on shipping books because of their low cost and universal demand.\nAmazon may have had humble beginnings, but today, that bookstore is something far more. Since their day of incorporation in 1994, they have gone on to dominate not just retail, but other industries besides.\nOn the surface, a few things stand out about how Bezos approached the growth of his company. He maintained a true customer obsession from the start, he never got complacent in spite of their performance, and he sacrificed short-term vanity metrics for the endgame.\nAs we dig a little deeper, however, it’s clear that there are certain details in his execution that made the surface-level advantages possible. Every company wants to take that approach, but not all of them have the foundational decision-making framework in place to do so.\nAmazon may be an enormous corporation, but their core tools are simple and quite usable. Here is what we can steal.\n1. Distinguish Between High and Low Impact\nEvery day, we make big and small decisions in response to what our environment dictates.\nThese decisions demand time and attention, and much of the stress many of us experience on a day to day basis is a result of this constant pressure on our often limited resources. And then because of this stress, we get forced and rushed into making less than optimal choices.\nThe problem is that we intuitively judge the importance of our decisions based not on impact, but on random timing. Even if something is relatively unimportant, and even if it can wait, we feel the need to attend to it because of the surrounding circumstances.\nAs Jeff Bezos explained to Amazon shareholders in his 2015 letter, there are two categories of decisions. Type 1 are the mission-critical, high-impact choices that influence the larger strategy, while Type 2 are the lower stakes choices that can easily be reversed if need be.\nAt Amazon, by distinguishing between impact, they leave all Type 2 decisions to the teams and individuals on the ground, while the people higher up focus on Type 1 decisions.\nGiven that most large companies have a very fuzzy distinction between the two, they fall into the trap of immediacy and their ability to direct resources to the truly important things suffers.\nIt’s a simple but effective system for choosing to leverage attention to where it’s best used, because even in our own lives, it’s easy to confuse what’s important with what’s present.\nMost of your time should always be spent on Type 1 decisions. Type 2 decisions should either be delegated, or they should be batched together with other less critical choices for later.\n2. Avoid Using Proxies as a Default\nWith more technology, there is more automation. With more data, there is more efficiency.\nCompanies like Amazon have access to a sheer amount of resources that can ease their load in a number of ways. They can deploy surveys and tests to collect a wealth of research and use all of that to build systems that automate many of the decisions they have to make.\nThere are times when this is quite effective, but as Bezos points out:\n“Good process serves you so you can serve customers. But if you’re not watchful, the process can become the thing. This can happen very easily in large organizations. The process becomes the proxy for the result you want. You stop looking at outcomes and just make sure you’re doing the process right… The process is not the thing. It’s always worth asking, do we own the process or does the process own us?”\n\n![1-8qJ3aoYDBDUxEL3kTDgO3A.png](https://steemitimages.com/DQmTnbXKW6NPTbbSBTdStWuFs66fqqGh4FmRFqjxQYk9PHd/1-8qJ3aoYDBDUxEL3kTDgO3A.png)\n\nCompanies have different kinds of proxies than we do as individuals. Many of the processes we set up to help us automate decisions come in the form of analogies. We take shortcuts based on either an average obtained from somewhere or through the stories of others.\nThe problem with this kind of decision-making is that it overlooks context. Granted, if you’re not learning from the wealth of knowledge we have available in this day and age, you will be left behind. That said, it’s important to cater the application of that knowledge situationally.\nGiven the number of variables at play in any setting, it can be dangerous to think that an average or an analogy will work for you the same way that it worked for someone else. Good decisions gain their advantage because they were made with an awareness of the details.\nFor most Type 2 decisions, proxies are helpful, but when it comes to the high-impact Type 1 decisions, it’s better to reason from ground up, taking into account each unique situation.\n3. Release Ideas at 70% and Then Iterate\nFor most decisions, after a certain point, information and time provide diminishing returns.\nAs a general rule of thumb, the longer you take on something, the less you have to gain from taking that time, and the more you have to lose from falling behind. This doesn’t apply to every situation, but generally speaking, improvements become redundant after a while.\nFor example, if you’re a creator or a maker of any kind, the creation is almost never going to feel perfect. Dwelling on the minor tweaks before sharing that work will eat up way more time than the yield of the potential improvements is worth. It’s far smarter to let go before you’re ready, and then iterate and improve based on the feedback.\nDrawing these lines not only keeps us active, but it also ensures that we don’t get attached to our choices. Any high-impact decision concerns the future, and we should account for change. Trying to make static and perfect choices in a dynamic world is a recipe for disaster.\nWhen we make choices, we think of them as individual events. It’s not at all accurate. Most choices have implications that extend over a period, and they need to be adjusted as such.\nFor Bezos and Amazon, the line is drawn at 70% of the perceived ideal information. After that, they focus on careful corrections. This benchmark allows them to move fast, but it also ensures that there’s no compromise on the quality of that decision with too early of a release.\nThis explains how they have been able to get into so many industries with such a strong foothold. Less time deciding means more decisions. Quantity eventually leads to quality.\nCorrecting the wrong is less costly than not taking action, and more often than not, correction of some sort is a necessity anyway. Draw a line and use feedback to improve.\nAll You Need to Know\nDecisions shape every part of our life, and the quality of our decisions determine where we end up. Having decision frameworks can help us combat any potential blind spots.\nAmazon is one of the most successful corporations of our day. They have many things going for them, but the key determinant of their success is arguably their decision-making process.\nIt’s easy to neglect the idea of having a framework in place to make choices. It’s something we have an intuitive process for, but it’s useful to remember that our intuition has known gaps.\nGood decision-making not only removes those gaps, but it also filters signal from the noise.\nCall to Action\nThe internet is filled with noise. I’ve created a free high-quality newsletter that helps people get 10x results and live better.",
      "json_metadata": "{\"tags\":[\"life\",\"psychology\"],\"image\":[\"https://steemitimages.com/DQmaRwjpzDb4Wzc9xP7sM7G7EDwSsT9pMbLRZaLyCVQZjbD/1-gzoOt0ZjcuK1N9jUZCdC5Q.jpeg\",\"https://steemitimages.com/DQmTnbXKW6NPTbbSBTdStWuFs66fqqGh4FmRFqjxQYk9PHd/1-8qJ3aoYDBDUxEL3kTDgO3A.png\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
      "parent_author": "",
      "parent_permlink": "life",
      "permlink": "5kzl9l-i-didn-t-know-who-my-baby-s-father-was",
      "title": "I Didn’t Know Who My Baby’s Father Was"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-10-27T14:58:51",
  "trx_id": "52f6167d5b4b70dd55afcdbc06281c69e46aa908",
  "trx_in_block": 3,
  "virtual_op": 0
}
2017/10/27 14:49:42
authoraliyeve
permlinki-didn-t-know-who-my-baby-s-father-was
voteraliyeve
weight10000 (100.00%)
Transaction InfoBlock #16699426/Trx 3d8be87f380a8d9df890fb532ffe0d4dafb8bf10
View Raw JSON Data
{
  "block": 16699426,
  "op": [
    "vote",
    {
      "author": "aliyeve",
      "permlink": "i-didn-t-know-who-my-baby-s-father-was",
      "voter": "aliyeve",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-10-27T14:49:42",
  "trx_id": "3d8be87f380a8d9df890fb532ffe0d4dafb8bf10",
  "trx_in_block": 18,
  "virtual_op": 0
}
2017/10/27 14:49:42
allow curation rewardstrue
allow votestrue
authoraliyeve
extensions[]
max accepted payout1000000.000 SBD
percent steem dollars0
permlinki-didn-t-know-who-my-baby-s-father-was
Transaction InfoBlock #16699426/Trx 3d8be87f380a8d9df890fb532ffe0d4dafb8bf10
View Raw JSON Data
{
  "block": 16699426,
  "op": [
    "comment_options",
    {
      "allow_curation_rewards": true,
      "allow_votes": true,
      "author": "aliyeve",
      "extensions": [],
      "max_accepted_payout": "1000000.000 SBD",
      "percent_steem_dollars": 0,
      "permlink": "i-didn-t-know-who-my-baby-s-father-was"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-10-27T14:49:42",
  "trx_id": "3d8be87f380a8d9df890fb532ffe0d4dafb8bf10",
  "trx_in_block": 18,
  "virtual_op": 0
}
2017/10/27 14:49:42
authoraliyeve
body![1-DMO9RcIfsqw9YQFncseVwA.jpeg](https://steemitimages.com/DQmcpkmuRnwh14SVgmTQYyFAAxcQPH1r3Un8osAXbM4YTCV/1-DMO9RcIfsqw9YQFncseVwA.jpeg) shifted uncomfortably, the white paper sheet crackling beneath me. My stomach was in knots. As I looked at the OBGYN’s face, my impending sense of dread multiplied. I knew. “The test is positive. You are pregnant.” The look on my face must have tipped her off that saying, ‘Congratulations’ might be a bit off…
json metadata{"tags":["life","health","love"],"image":["https://steemitimages.com/DQmcpkmuRnwh14SVgmTQYyFAAxcQPH1r3Un8osAXbM4YTCV/1-DMO9RcIfsqw9YQFncseVwA.jpeg"],"app":"steemit/0.1","format":"markdown"}
parent author
parent permlinklife
permlinki-didn-t-know-who-my-baby-s-father-was
titleI Didn’t Know Who My Baby’s Father Was
Transaction InfoBlock #16699426/Trx 3d8be87f380a8d9df890fb532ffe0d4dafb8bf10
View Raw JSON Data
{
  "block": 16699426,
  "op": [
    "comment",
    {
      "author": "aliyeve",
      "body": "![1-DMO9RcIfsqw9YQFncseVwA.jpeg](https://steemitimages.com/DQmcpkmuRnwh14SVgmTQYyFAAxcQPH1r3Un8osAXbM4YTCV/1-DMO9RcIfsqw9YQFncseVwA.jpeg)\n\nshifted uncomfortably, the white paper sheet crackling beneath me. My stomach was in knots. As I looked at the OBGYN’s face, my impending sense of dread multiplied. I knew. “The test is positive. You are pregnant.” The look on my face must have tipped her off that saying, ‘Congratulations’ might be a bit off…",
      "json_metadata": "{\"tags\":[\"life\",\"health\",\"love\"],\"image\":[\"https://steemitimages.com/DQmcpkmuRnwh14SVgmTQYyFAAxcQPH1r3Un8osAXbM4YTCV/1-DMO9RcIfsqw9YQFncseVwA.jpeg\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
      "parent_author": "",
      "parent_permlink": "life",
      "permlink": "i-didn-t-know-who-my-baby-s-father-was",
      "title": "I Didn’t Know Who My Baby’s Father Was"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-10-27T14:49:42",
  "trx_id": "3d8be87f380a8d9df890fb532ffe0d4dafb8bf10",
  "trx_in_block": 18,
  "virtual_op": 0
}
2017/10/27 14:45:12
authoraliyeve
permlinkstill-don-t-know-what-bitcoin-is-read-this
voterrayken04
weight10000 (100.00%)
Transaction InfoBlock #16699336/Trx 0291dbef9c8dc7fa69488612cb73aa8ada486fb0
View Raw JSON Data
{
  "block": 16699336,
  "op": [
    "vote",
    {
      "author": "aliyeve",
      "permlink": "still-don-t-know-what-bitcoin-is-read-this",
      "voter": "rayken04",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-10-27T14:45:12",
  "trx_id": "0291dbef9c8dc7fa69488612cb73aa8ada486fb0",
  "trx_in_block": 21,
  "virtual_op": 0
}
2017/10/27 14:44:54
authorcheetah
bodyHi! I am a robot. I just upvoted you! I found similar content that readers might be interested in: https://kantantechnology.com/still-dont-know-what-bitcoin-is-read-this-b62737f27921
json metadata
parent authoraliyeve
parent permlinkstill-don-t-know-what-bitcoin-is-read-this
permlinkcheetah-re-aliyevestill-don-t-know-what-bitcoin-is-read-this
title
Transaction InfoBlock #16699330/Trx 2298934001b9662ffa778b0cf81db2e62e0f2973
View Raw JSON Data
{
  "block": 16699330,
  "op": [
    "comment",
    {
      "author": "cheetah",
      "body": "Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in:\nhttps://kantantechnology.com/still-dont-know-what-bitcoin-is-read-this-b62737f27921",
      "json_metadata": "",
      "parent_author": "aliyeve",
      "parent_permlink": "still-don-t-know-what-bitcoin-is-read-this",
      "permlink": "cheetah-re-aliyevestill-don-t-know-what-bitcoin-is-read-this",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-10-27T14:44:54",
  "trx_id": "2298934001b9662ffa778b0cf81db2e62e0f2973",
  "trx_in_block": 13,
  "virtual_op": 0
}
2017/10/27 14:44:48
authoraliyeve
permlinkstill-don-t-know-what-bitcoin-is-read-this
votercheetah
weight50 (0.50%)
Transaction InfoBlock #16699328/Trx 03d18f2f785a10188040ce49ba426925e9c7939e
View Raw JSON Data
{
  "block": 16699328,
  "op": [
    "vote",
    {
      "author": "aliyeve",
      "permlink": "still-don-t-know-what-bitcoin-is-read-this",
      "voter": "cheetah",
      "weight": 50
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-10-27T14:44:48",
  "trx_id": "03d18f2f785a10188040ce49ba426925e9c7939e",
  "trx_in_block": 30,
  "virtual_op": 0
}
2017/10/27 14:44:36
authoraliyeve
permlinkstill-don-t-know-what-bitcoin-is-read-this
voteraliyeve
weight10000 (100.00%)
Transaction InfoBlock #16699324/Trx 0f1915041827dfc7f1489a797db34e4ac004548d
View Raw JSON Data
{
  "block": 16699324,
  "op": [
    "vote",
    {
      "author": "aliyeve",
      "permlink": "still-don-t-know-what-bitcoin-is-read-this",
      "voter": "aliyeve",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-10-27T14:44:36",
  "trx_id": "0f1915041827dfc7f1489a797db34e4ac004548d",
  "trx_in_block": 1,
  "virtual_op": 0
}
2017/10/27 14:44:36
allow curation rewardstrue
allow votestrue
authoraliyeve
extensions[]
max accepted payout1000000.000 SBD
percent steem dollars0
permlinkstill-don-t-know-what-bitcoin-is-read-this
Transaction InfoBlock #16699324/Trx 0f1915041827dfc7f1489a797db34e4ac004548d
View Raw JSON Data
{
  "block": 16699324,
  "op": [
    "comment_options",
    {
      "allow_curation_rewards": true,
      "allow_votes": true,
      "author": "aliyeve",
      "extensions": [],
      "max_accepted_payout": "1000000.000 SBD",
      "percent_steem_dollars": 0,
      "permlink": "still-don-t-know-what-bitcoin-is-read-this"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-10-27T14:44:36",
  "trx_id": "0f1915041827dfc7f1489a797db34e4ac004548d",
  "trx_in_block": 1,
  "virtual_op": 0
}
2017/10/27 14:44:36
authoraliyeve
body![1-7W6kLR9NNY15TsDenLYaHg.jpeg](https://steemitimages.com/DQmRMLuA4kr2ZQMSo5oYwU2QPPEPhdXiXBjpCDePCM7kw31/1-7W6kLR9NNY15TsDenLYaHg.jpeg) Bitcoin’s astronomical rise in value and innovative technology are making waves in every corner of the internet. An overview of Bitcoin for beginners. Bitcoin. It’s a term you’ve no doubt heard here and there over the past few years. But what does it mean? Why do you keep hearing about it? I first learned of Bitcoin while attending University back in 2011. It appeared in a tech blog that boldly stated Bitcoin was going to be the future of money, but that it faced some significant hurdles to get there. One of the main challenges to mainstream adoption I remember reading was that Bitcoin held a certain stigma because it was mostly used to buy drugs and illegal weapons online. But despite this and many other obstacles, the author attempted to convince his readers that Bitcoin was a good investment. The story broke right as Bitcoin reached an iconic point in its history — one Bitcoin became worth $1. It was sweet validation to all enthusiasts that Bitcoin had a chance to go mainstream. Four months later the price skyrocketed to $31. Then this week one Bitcoin became worth $5,700. If I had invested a measly $175 in Bitcoin after reading that article in 2011, it would be worth $1,000,000 today. This is why you’ve been hearing so much about Bitcoin. Ok, so it’s a tremendous financial opportunity. But what is it? The Bitcoin record is a shared record of who owns which Bitcoin. Bitcoin is a form of digital money that can be sent over the internet to anyone anywhere in the world. It’s secure in the sense that there’s a publicly available record of who owns which Bitcoin, and that record is shared between thousands of computers all over the world. You can see it here (but I didn’t say you’d understand it 😉). Each time Bitcoin is exchanged it’s etched onto this record. You can’t secretly unspend Bitcoin you’ve sent to someone because the record is public, and as soon as you send it the record captures that transaction and everyone knows it no longer belongs to you. How do you know who owns which Bitcoin? To receive Bitcoin you give the person or business you’re trading with your public Bitcoin address (think of it as an email address). They then use their Bitcoin address (email) and private key (password) to send Bitcoin to you. As soon as the transaction is complete, it’s recorded on the public record that your address now owns that Bitcoin. However, unlike email, Bitcoin addresses are not tied to personal identities, so the transactions are anonymous. No one really knows who the Bitcoin belong to, but everyone can see which addresses hold how many Bitcoin. And just like email, as long as you don’t lose your private key (password), you’re the only one who can access your Bitcoin. Why and how is it worth anything? Bitcoin solves some significant issues and opens exciting new opportunities that are currently impossible with traditional currencies. Here are a few examples: Bitcoin can be sent to anyone anywhere in the world in a matter of minutes. The transfer fees are incredibly cheap, and you don’t need to go through any banks to do it. Bitcoin doesn’t require you to trust the person on the other end of the transaction. If a Bitcoin shows up in your digital wallet, it’s yours. This way you don’t need a middleman to verify the transaction and take a cut to do so. Bitcoin’s public record, decisions, and changes are decentralized. This is in contrast to centralized governments and banks that can be manipulated by relatively few people. Since it’s stored and operated on computers all around the world, no one party can manipulate Bitcoin to satisfy their individual desires. Bitcoin is mined. But not in the traditional sense. Instead, miners of Bitcoin use powerful computers to solve complex math equations. The first miner to solve the problem is rewarded with Bitcoin. Only 21 million Bitcoin will ever be mined. This creates scarcity and a relationship between supply and demand that can’t easily be manipulated. Scarcity is a driver of value and is what makes things like Gold and Silver worth what they are. The Bitcoin community is one of the strongest and most dedicated on the planet. Online stores can receive purchases from anywhere in the world if they accept Bitcoin. Japan has legalized Bitcoin as a payment method, and over 260,000 stores accept Bitcoin in the country. Japanese residents spend about $2.6 trillion every year to buy things. If only 10% of those transactions were in Bitcoin, then the Japanese Bitcoin market alone could justify Bitcoin’s current price. Basically, the current price of Bitcoin is still meager compared to the potential it has if people around the world start using it regularly. What are some of the challenges? Bitcoin almost sounds too good to be true. But is it? You likely have heard as many criticisms of Bitcoin as you have praises. Many of those criticisms are true, and many are not. Here are a few valid ones: Bitcoin can’t handle many transactions — This is true. Bitcoin handles an average of 5 transactions per second. Visa does 2,000. To process transactions all over the world and be viable for everyday use, Bitcoin will likely need the ability to process an equivalent of 100,000 transactions per second. Fortunately many different solutions are being worked on and proposed to allow for scaling without sacrificing Bitcoin’s famed security. Bitcoin can get hacked and I’ll lose my money — This is partially true. While Bitcoin itself hasn’t had a single major hack in its lifetime (except for bugs early on that were quickly fixed and didn’t result in any substantial amounts of money being lost), plenty of surrounding softwares and companies have been hacked. Since the Bitcoin public record is near impossible to compromise, you don’t have to worry about someone stealing your money that way. What you do need to be careful of is where you store your Bitcoin. Bitcoin Exchanges are favorite targets of hackers because they save your private keys (passwords) together with everyone else’s, and if the exchange gets hacked the intruder could likely access and steal everyone’s Bitcoin at the same time. Also, sending your Bitcoin to the wrong address (which is easier than you might think!), will result in the permanent loss of your money. The company that creates an effortless and safe way to store and send Bitcoin will become one of the most valuable companies in this space. Currently, Coinbase is the most accessible and reliable method out there, but they still have a long way to go. Governments can shut it down and kill the value — This is partially true. While governments can’t control where you send your Bitcoin, they can make it illegal to trade or buy things with them. China recently shut down all of the Bitcoin exchanges in its country while they work on regulations for Bitcoin and other currencies. This had a severe short-term impact on the value of Bitcoin (the price has rebounded strongly since then) as people realized governments could make it difficult to use Bitcoin. Though in Venezuela, where officials have tried to ban Bitcoin mining, it serves as one of the only viable ways to make money (alongside “farming” for gold in Runescape) and people continue to do it despite pressure from local authorities to stop. While many central banks and governments fear Bitcoin and the disruption it’ll bring, many are embracing it and seeking to understand its possibilities. Smart people call Bitcoin a “fraud” — This is true... That people call it a fraud. But they are mostly misinformed. Perhaps the most common objection to Bitcoin is that it has no intrinsic value (value beyond its price). But neither does a $1 bill. The $1 bill used to be backed by gold, giving it a second layer of value. That’s no longer the case. $1 is only worth $1 because people agree that’s what it’s worth. A currency’s value is driven by a collective belief in a government’s good faith. In fact, when paper money was introduced in the late 19th century many skeptics had the same arguments against it as current skeptics do about Bitcoin. If you read their objections and substitute “Bitcoin” for “paper money,” you’d find that the talking points are nearly identical. This happens any time there’s a financial revolution. Many people feel they have lots to lose if their way of life is being disrupted, and there are many who do, which is why they spend so much energy fighting back. Next time you hear a naysayer of Bitcoin, stop and think about what they have to gain by putting Bitcoin down. Ethereum and other cryptocurrencies will surpass Bitcoin — This may be true. But no one knows at this point and it’s extremely difficult to predict. Bitcoin is a living currency. It’s always being developed and improved upon, and it has proven to be highly adaptable. All decisions are made on a consensus basis between the miners and users of Bitcoin. But this is where its strengths become its weaknesses. No one party can grab the wheel and control Bitcoin to make it applicable to a particular use case (like using it for groceries). Other cryptocurrencies skew more control towards the developers, allowing them to build new technologies into the coin at a quicker pace than Bitcoin. The most significant thing Bitcoin has going for it is user adoption. Nothing else comes close to the awareness and overall value of Bitcoin, and as long as the Bitcoin community stays strong, active, and (mostly) devoid of politics, Bitcoin will remain the leader for the foreseeable future. Conclusion Fast forward six years and my interest in Bitcoin has only grown. As I continue to dive deeper into the studies of Bitcoin, I discover that there’s so much more to it than meets the eye. Understanding Bitcoin and its underlying technology will truly be a lifelong pursuit. And while the premise of Bitcoin seems simple on the surface — creating digital copies of things that can’t be further copied — it has laid the foundation of the future of money and opened the door to applications that aren’t yet possible with modern technologies. We are only at the beginning of perhaps the most significant technological revolution since the internet. I hope you’ll join me and millions of others around the globe as we study and build the future. You may not realize it, but you now know more about Bitcoin than most. Don’t let that knowledge go to waste. **Update 10/12 to reflect price of one Bitcoin at $5,700. Thank you for reading. If this helped you please leave a comment and some 👏👏👏 below. While Bitcoin is a phenomenal investment opportunity, please consult an expert in the field before buying any. I don’t intend this as investment advice. If you’d like to see a breakdown of Ethereum and blockchain for beginners, please let me know!
json metadata{"tags":["bitcoin","blockchain","ethereum","finance","startup"],"image":["https://steemitimages.com/DQmRMLuA4kr2ZQMSo5oYwU2QPPEPhdXiXBjpCDePCM7kw31/1-7W6kLR9NNY15TsDenLYaHg.jpeg"],"app":"steemit/0.1","format":"markdown"}
parent author
parent permlinkbitcoin
permlinkstill-don-t-know-what-bitcoin-is-read-this
titleStill don’t know what Bitcoin is? Read this.
Transaction InfoBlock #16699324/Trx 0f1915041827dfc7f1489a797db34e4ac004548d
View Raw JSON Data
{
  "block": 16699324,
  "op": [
    "comment",
    {
      "author": "aliyeve",
      "body": "![1-7W6kLR9NNY15TsDenLYaHg.jpeg](https://steemitimages.com/DQmRMLuA4kr2ZQMSo5oYwU2QPPEPhdXiXBjpCDePCM7kw31/1-7W6kLR9NNY15TsDenLYaHg.jpeg)\n\nBitcoin’s astronomical rise in value and innovative technology are making waves in every corner of the internet.\n\nAn overview of Bitcoin for beginners.\nBitcoin. It’s a term you’ve no doubt heard here and there over the past few years. But what does it mean? Why do you keep hearing about it?\nI first learned of Bitcoin while attending University back in 2011. It appeared in a tech blog that boldly stated Bitcoin was going to be the future of money, but that it faced some significant hurdles to get there. One of the main challenges to mainstream adoption I remember reading was that Bitcoin held a certain stigma because it was mostly used to buy drugs and illegal weapons online. But despite this and many other obstacles, the author attempted to convince his readers that Bitcoin was a good investment.\nThe story broke right as Bitcoin reached an iconic point in its history — one Bitcoin became worth $1. It was sweet validation to all enthusiasts that Bitcoin had a chance to go mainstream. Four months later the price skyrocketed to $31.\nThen this week one Bitcoin became worth $5,700.\nIf I had invested a measly $175 in Bitcoin after reading that article in 2011, it would be worth $1,000,000 today.\nThis is why you’ve been hearing so much about Bitcoin.\nOk, so it’s a tremendous financial opportunity. But what is it?\nThe Bitcoin record is a shared record of who owns which Bitcoin.\nBitcoin is a form of digital money that can be sent over the internet to anyone anywhere in the world.\nIt’s secure in the sense that there’s a publicly available record of who owns which Bitcoin, and that record is shared between thousands of computers all over the world. You can see it here (but I didn’t say you’d understand it 😉).\nEach time Bitcoin is exchanged it’s etched onto this record. You can’t secretly unspend Bitcoin you’ve sent to someone because the record is public, and as soon as you send it the record captures that transaction and everyone knows it no longer belongs to you.\nHow do you know who owns which Bitcoin?\nTo receive Bitcoin you give the person or business you’re trading with your public Bitcoin address (think of it as an email address). They then use their Bitcoin address (email) and private key (password) to send Bitcoin to you.\nAs soon as the transaction is complete, it’s recorded on the public record that your address now owns that Bitcoin.\nHowever, unlike email, Bitcoin addresses are not tied to personal identities, so the transactions are anonymous. No one really knows who the Bitcoin belong to, but everyone can see which addresses hold how many Bitcoin. And just like email, as long as you don’t lose your private key (password), you’re the only one who can access your Bitcoin.\nWhy and how is it worth anything?\nBitcoin solves some significant issues and opens exciting new opportunities that are currently impossible with traditional currencies. Here are a few examples:\nBitcoin can be sent to anyone anywhere in the world in a matter of minutes. The transfer fees are incredibly cheap, and you don’t need to go through any banks to do it.\nBitcoin doesn’t require you to trust the person on the other end of the transaction. If a Bitcoin shows up in your digital wallet, it’s yours. This way you don’t need a middleman to verify the transaction and take a cut to do so.\nBitcoin’s public record, decisions, and changes are decentralized. This is in contrast to centralized governments and banks that can be manipulated by relatively few people. Since it’s stored and operated on computers all around the world, no one party can manipulate Bitcoin to satisfy their individual desires.\nBitcoin is mined. But not in the traditional sense. Instead, miners of Bitcoin use powerful computers to solve complex math equations. The first miner to solve the problem is rewarded with Bitcoin. Only 21 million Bitcoin will ever be mined. This creates scarcity and a relationship between supply and demand that can’t easily be manipulated. Scarcity is a driver of value and is what makes things like Gold and Silver worth what they are.\nThe Bitcoin community is one of the strongest and most dedicated on the planet.\nOnline stores can receive purchases from anywhere in the world if they accept Bitcoin.\nJapan has legalized Bitcoin as a payment method, and over 260,000 stores accept Bitcoin in the country. Japanese residents spend about $2.6 trillion every year to buy things. If only 10% of those transactions were in Bitcoin, then the Japanese Bitcoin market alone could justify Bitcoin’s current price. Basically, the current price of Bitcoin is still meager compared to the potential it has if people around the world start using it regularly.\nWhat are some of the challenges?\nBitcoin almost sounds too good to be true. But is it?\nYou likely have heard as many criticisms of Bitcoin as you have praises. Many of those criticisms are true, and many are not. Here are a few valid ones:\nBitcoin can’t handle many transactions — This is true. Bitcoin handles an average of 5 transactions per second. Visa does 2,000. To process transactions all over the world and be viable for everyday use, Bitcoin will likely need the ability to process an equivalent of 100,000 transactions per second. Fortunately many different solutions are being worked on and proposed to allow for scaling without sacrificing Bitcoin’s famed security.\nBitcoin can get hacked and I’ll lose my money — This is partially true. While Bitcoin itself hasn’t had a single major hack in its lifetime (except for bugs early on that were quickly fixed and didn’t result in any substantial amounts of money being lost), plenty of surrounding softwares and companies have been hacked. Since the Bitcoin public record is near impossible to compromise, you don’t have to worry about someone stealing your money that way. What you do need to be careful of is where you store your Bitcoin. Bitcoin Exchanges are favorite targets of hackers because they save your private keys (passwords) together with everyone else’s, and if the exchange gets hacked the intruder could likely access and steal everyone’s Bitcoin at the same time. Also, sending your Bitcoin to the wrong address (which is easier than you might think!), will result in the permanent loss of your money. The company that creates an effortless and safe way to store and send Bitcoin will become one of the most valuable companies in this space. Currently, Coinbase is the most accessible and reliable method out there, but they still have a long way to go.\nGovernments can shut it down and kill the value — This is partially true. While governments can’t control where you send your Bitcoin, they can make it illegal to trade or buy things with them. China recently shut down all of the Bitcoin exchanges in its country while they work on regulations for Bitcoin and other currencies. This had a severe short-term impact on the value of Bitcoin (the price has rebounded strongly since then) as people realized governments could make it difficult to use Bitcoin. Though in Venezuela, where officials have tried to ban Bitcoin mining, it serves as one of the only viable ways to make money (alongside “farming” for gold in Runescape) and people continue to do it despite pressure from local authorities to stop. While many central banks and governments fear Bitcoin and the disruption it’ll bring, many are embracing it and seeking to understand its possibilities.\nSmart people call Bitcoin a “fraud” — This is true... That people call it a fraud. But they are mostly misinformed. Perhaps the most common objection to Bitcoin is that it has no intrinsic value (value beyond its price). But neither does a $1 bill. The $1 bill used to be backed by gold, giving it a second layer of value. That’s no longer the case. $1 is only worth $1 because people agree that’s what it’s worth. A currency’s value is driven by a collective belief in a government’s good faith. In fact, when paper money was introduced in the late 19th century many skeptics had the same arguments against it as current skeptics do about Bitcoin. If you read their objections and substitute “Bitcoin” for “paper money,” you’d find that the talking points are nearly identical. This happens any time there’s a financial revolution. Many people feel they have lots to lose if their way of life is being disrupted, and there are many who do, which is why they spend so much energy fighting back. Next time you hear a naysayer of Bitcoin, stop and think about what they have to gain by putting Bitcoin down.\nEthereum and other cryptocurrencies will surpass Bitcoin — This may be true. But no one knows at this point and it’s extremely difficult to predict. Bitcoin is a living currency. It’s always being developed and improved upon, and it has proven to be highly adaptable. All decisions are made on a consensus basis between the miners and users of Bitcoin. But this is where its strengths become its weaknesses. No one party can grab the wheel and control Bitcoin to make it applicable to a particular use case (like using it for groceries). Other cryptocurrencies skew more control towards the developers, allowing them to build new technologies into the coin at a quicker pace than Bitcoin. The most significant thing Bitcoin has going for it is user adoption. Nothing else comes close to the awareness and overall value of Bitcoin, and as long as the Bitcoin community stays strong, active, and (mostly) devoid of politics, Bitcoin will remain the leader for the foreseeable future.\nConclusion\nFast forward six years and my interest in Bitcoin has only grown. As I continue to dive deeper into the studies of Bitcoin, I discover that there’s so much more to it than meets the eye. Understanding Bitcoin and its underlying technology will truly be a lifelong pursuit.\nAnd while the premise of Bitcoin seems simple on the surface — creating digital copies of things that can’t be further copied — it has laid the foundation of the future of money and opened the door to applications that aren’t yet possible with modern technologies.\nWe are only at the beginning of perhaps the most significant technological revolution since the internet. I hope you’ll join me and millions of others around the globe as we study and build the future.\nYou may not realize it, but you now know more about Bitcoin than most. Don’t let that knowledge go to waste.\n**Update 10/12 to reflect price of one Bitcoin at $5,700.\nThank you for reading. If this helped you please leave a comment and some 👏👏👏 below. While Bitcoin is a phenomenal investment opportunity, please consult an expert in the field before buying any. I don’t intend this as investment advice. If you’d like to see a breakdown of Ethereum and blockchain for beginners, please let me know!",
      "json_metadata": "{\"tags\":[\"bitcoin\",\"blockchain\",\"ethereum\",\"finance\",\"startup\"],\"image\":[\"https://steemitimages.com/DQmRMLuA4kr2ZQMSo5oYwU2QPPEPhdXiXBjpCDePCM7kw31/1-7W6kLR9NNY15TsDenLYaHg.jpeg\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
      "parent_author": "",
      "parent_permlink": "bitcoin",
      "permlink": "still-don-t-know-what-bitcoin-is-read-this",
      "title": "Still don’t know what Bitcoin is? Read this."
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-10-27T14:44:36",
  "trx_id": "0f1915041827dfc7f1489a797db34e4ac004548d",
  "trx_in_block": 1,
  "virtual_op": 0
}
2017/10/27 14:39:48
authorcheetah
bodyHi! I am a robot. I just upvoted you! I found similar content that readers might be interested in: https://hackernoon.com/blockchain-and-energy-industry-what-is-ahead-315d1612bcef
json metadata
parent authoraliyeve
parent permlinkblockchain-and-energy-industry-what-is-ahead
permlinkcheetah-re-aliyeveblockchain-and-energy-industry-what-is-ahead
title
Transaction InfoBlock #16699228/Trx 38f0dccfe4ff05513056a0adc1b4af481c150892
View Raw JSON Data
{
  "block": 16699228,
  "op": [
    "comment",
    {
      "author": "cheetah",
      "body": "Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in:\nhttps://hackernoon.com/blockchain-and-energy-industry-what-is-ahead-315d1612bcef",
      "json_metadata": "",
      "parent_author": "aliyeve",
      "parent_permlink": "blockchain-and-energy-industry-what-is-ahead",
      "permlink": "cheetah-re-aliyeveblockchain-and-energy-industry-what-is-ahead",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-10-27T14:39:48",
  "trx_id": "38f0dccfe4ff05513056a0adc1b4af481c150892",
  "trx_in_block": 14,
  "virtual_op": 0
}
2017/10/27 14:39:45
authoraliyeve
permlinkblockchain-and-energy-industry-what-is-ahead
votercheetah
weight50 (0.50%)
Transaction InfoBlock #16699227/Trx ff9d71ed1f496245bd5cf40ba6f4c271181aea3a
View Raw JSON Data
{
  "block": 16699227,
  "op": [
    "vote",
    {
      "author": "aliyeve",
      "permlink": "blockchain-and-energy-industry-what-is-ahead",
      "voter": "cheetah",
      "weight": 50
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-10-27T14:39:45",
  "trx_id": "ff9d71ed1f496245bd5cf40ba6f4c271181aea3a",
  "trx_in_block": 8,
  "virtual_op": 0
}
2017/10/27 14:39:24
authoraliyeve
permlinkblockchain-and-energy-industry-what-is-ahead
voteraliyeve
weight10000 (100.00%)
Transaction InfoBlock #16699220/Trx 41c240f6d96c2b83af6ec07f7dd9130a6e7ab47c
View Raw JSON Data
{
  "block": 16699220,
  "op": [
    "vote",
    {
      "author": "aliyeve",
      "permlink": "blockchain-and-energy-industry-what-is-ahead",
      "voter": "aliyeve",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-10-27T14:39:24",
  "trx_id": "41c240f6d96c2b83af6ec07f7dd9130a6e7ab47c",
  "trx_in_block": 16,
  "virtual_op": 0
}
2017/10/27 14:39:24
allow curation rewardstrue
allow votestrue
authoraliyeve
extensions[]
max accepted payout1000000.000 SBD
percent steem dollars0
permlinkblockchain-and-energy-industry-what-is-ahead
Transaction InfoBlock #16699220/Trx 41c240f6d96c2b83af6ec07f7dd9130a6e7ab47c
View Raw JSON Data
{
  "block": 16699220,
  "op": [
    "comment_options",
    {
      "allow_curation_rewards": true,
      "allow_votes": true,
      "author": "aliyeve",
      "extensions": [],
      "max_accepted_payout": "1000000.000 SBD",
      "percent_steem_dollars": 0,
      "permlink": "blockchain-and-energy-industry-what-is-ahead"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-10-27T14:39:24",
  "trx_id": "41c240f6d96c2b83af6ec07f7dd9130a6e7ab47c",
  "trx_in_block": 16,
  "virtual_op": 0
}
2017/10/27 14:39:24
authoraliyeve
bodySpending funds efficiently and providing transparent transactions is essential for any business, yet the electric power industry is the one most appropriate for blockchain projects. Here is why. ![0-beIyZLFJVMvuRZ_4.jpg](https://steemitimages.com/DQmdeDpGHEUovqgnfAt4LZ9WCrjM8WV1mcyAxJT2cpzbf6S/0-beIyZLFJVMvuRZ_4.jpg) If oil is the blood of the modern economy, the electrical grid is its neural system. Electrical energy is needed everywhere — from lighting our houses in the night and all the way up to running machinery on the plants, computers in the offices and servers in the data centers. This turns building an efficient power grid and creating a transparent market for electric power into one of the top priorities nowadays. This is why many companies work on adding blockchain into the mix. Below are several examples of what lies ahead of the energy industry as blockchain makes its way to it. Blockchain can help collect fees for charging the vehicles RWE, one of the leading German electric utilities, is conducting a full-scale testing of a blockchain app for collecting fees for charging electric vehicles. Being a neat tool for a soon-coming economy of machine-to-machine (m2m) interactions, such an app will help the car drivers pay for charging their vehicles on the network of electric charging stations, and this money will be paid to the electric power producers, omitting any intermediary banking institution. RWE works closely with a German startup Slock.it to provide the drivers with the ability to pay for charging their vehicles using smart contracts issued using blockchain ledgers. With the EU automotive market being much inclined to the hybrid and electric vehicles, this app might be in a high demand quite soon. ![0-BMPeIc8ITrrSKvNG.jpg](https://steemitimages.com/DQmbsx3DASxQwDo13WhVYc8wGX4gz1ruMEZ41UFqPn5nPX7/0-BMPeIc8ITrrSKvNG.jpg) Power utilities can trade using blockchain, and Wien Energie is in the lead Wien Energie, an Austrian power utility was recently holding a pilot of a blockchain tool for enabling the trade of gas with two other utilities. Based on the Interbit trading platform from a Canadian startup BTL, this system proved useful for trading gas between three large energy-generating utilities. As Wien Energie is the Austria’s largest energy provider, they constantly seek to improve their leading position and secure their bottom line by providing more sophisticated services to their customers while reducing operational expenses. The use of smart contracts allows them to have a fraud-proof and transparent ledger of transactions. Smarter power grid control is essential for ongoing energy trade validation Grid Singularity, a Vienna-located startup, is actively testing its project for monitoring the grid state and trade power amongst the power-generating facilities and the consumers with the help of blockchain. Through the development of a decentralized energy data exchange tool, the company aims to provide all market players with access to interoperable, valid and protected data describing the power market stance real-time. This will underpin the efficiency and reliability of the future investor’s decisions, as well as allow easy access to the data on electricity production and consumption. ![0-fELTWNQgtUC7zJzj.jpg](https://steemitimages.com/DQmdVg8HoZYX9LgiquabH6jXhhaRpZHq85cx5DmZoy1gTUj/0-fELTWNQgtUC7zJzj.jpg) Vattenfall unites 22 European energy traders using blockchain Vattenfall, the leading power producer Sweden, tests a Proof of Concept of a decentralized electric power marketplace till the end of 2017 and will launch it countrywide afterward. With 22 partners across the EU, Vattenfall aims to grant small-scale energy producers a simple, reliable and equal entrance to the energy trading and an ability to form smart contracts for their customers omitting any vertically-structured authorities like banks or huge utility providers. This will decrease the operational complexity and decrease the transaction costs, which will inevitably bolster the business efficiency and help inspire the economic growth. Conclusions Thus said, it is still unclear what lies ahead of blockchain and the energy industry. The goal of almost all ongoing projects is the same, nevertheless — creating an efficient, transparent, decentralized and interactive energy market, opening new possibilities for every player. Perhaps you also have a bright idea involving blockchain? Drop us a line and IT Svit will help bring your dream to life! This article was originally published here. Feel free to browse through the latest insights and hints on the DevOps, BigData, Machine Learning and Blockchain from IT Svit!
json metadata{"tags":["bitcoin","blockchain","ethereum","tech","cryptocurrency"],"image":["https://steemitimages.com/DQmdeDpGHEUovqgnfAt4LZ9WCrjM8WV1mcyAxJT2cpzbf6S/0-beIyZLFJVMvuRZ_4.jpg","https://steemitimages.com/DQmbsx3DASxQwDo13WhVYc8wGX4gz1ruMEZ41UFqPn5nPX7/0-BMPeIc8ITrrSKvNG.jpg","https://steemitimages.com/DQmdVg8HoZYX9LgiquabH6jXhhaRpZHq85cx5DmZoy1gTUj/0-fELTWNQgtUC7zJzj.jpg"],"app":"steemit/0.1","format":"markdown"}
parent author
parent permlinkbitcoin
permlinkblockchain-and-energy-industry-what-is-ahead
titleBlockchain and Energy Industry: what is ahead?
Transaction InfoBlock #16699220/Trx 41c240f6d96c2b83af6ec07f7dd9130a6e7ab47c
View Raw JSON Data
{
  "block": 16699220,
  "op": [
    "comment",
    {
      "author": "aliyeve",
      "body": "Spending funds efficiently and providing transparent transactions is essential for any business, yet the electric power industry is the one most appropriate for blockchain projects. Here is why.\n\n![0-beIyZLFJVMvuRZ_4.jpg](https://steemitimages.com/DQmdeDpGHEUovqgnfAt4LZ9WCrjM8WV1mcyAxJT2cpzbf6S/0-beIyZLFJVMvuRZ_4.jpg)\n\nIf oil is the blood of the modern economy, the electrical grid is its neural system. Electrical energy is needed everywhere — from lighting our houses in the night and all the way up to running machinery on the plants, computers in the offices and servers in the data centers. This turns building an efficient power grid and creating a transparent market for electric power into one of the top priorities nowadays. This is why many companies work on adding blockchain into the mix.\nBelow are several examples of what lies ahead of the energy industry as blockchain makes its way to it.\nBlockchain can help collect fees for charging the vehicles\nRWE, one of the leading German electric utilities, is conducting a full-scale testing of a blockchain app for collecting fees for charging electric vehicles. Being a neat tool for a soon-coming economy of machine-to-machine (m2m) interactions, such an app will help the car drivers pay for charging their vehicles on the network of electric charging stations, and this money will be paid to the electric power producers, omitting any intermediary banking institution.\nRWE works closely with a German startup Slock.it to provide the drivers with the ability to pay for charging their vehicles using smart contracts issued using blockchain ledgers. With the EU automotive market being much inclined to the hybrid and electric vehicles, this app might be in a high demand quite soon.\n\n![0-BMPeIc8ITrrSKvNG.jpg](https://steemitimages.com/DQmbsx3DASxQwDo13WhVYc8wGX4gz1ruMEZ41UFqPn5nPX7/0-BMPeIc8ITrrSKvNG.jpg)\n\n\nPower utilities can trade using blockchain, and Wien Energie is in the lead\nWien Energie, an Austrian power utility was recently holding a pilot of a blockchain tool for enabling the trade of gas with two other utilities. Based on the Interbit trading platform from a Canadian startup BTL, this system proved useful for trading gas between three large energy-generating utilities. As Wien Energie is the Austria’s largest energy provider, they constantly seek to improve their leading position and secure their bottom line by providing more sophisticated services to their customers while reducing operational expenses. The use of smart contracts allows them to have a fraud-proof and transparent ledger of transactions.\nSmarter power grid control is essential for ongoing energy trade validation\nGrid Singularity, a Vienna-located startup, is actively testing its project for monitoring the grid state and trade power amongst the power-generating facilities and the consumers with the help of blockchain. Through the development of a decentralized energy data exchange tool, the company aims to provide all market players with access to interoperable, valid and protected data describing the power market stance real-time. This will underpin the efficiency and reliability of the future investor’s decisions, as well as allow easy access to the data on electricity production and consumption.\n\n![0-fELTWNQgtUC7zJzj.jpg](https://steemitimages.com/DQmdVg8HoZYX9LgiquabH6jXhhaRpZHq85cx5DmZoy1gTUj/0-fELTWNQgtUC7zJzj.jpg)\n\nVattenfall unites 22 European energy traders using blockchain\nVattenfall, the leading power producer Sweden, tests a Proof of Concept of a decentralized electric power marketplace till the end of 2017 and will launch it countrywide afterward. With 22 partners across the EU, Vattenfall aims to grant small-scale energy producers a simple, reliable and equal entrance to the energy trading and an ability to form smart contracts for their customers omitting any vertically-structured authorities like banks or huge utility providers. This will decrease the operational complexity and decrease the transaction costs, which will inevitably bolster the business efficiency and help inspire the economic growth.\nConclusions\nThus said, it is still unclear what lies ahead of blockchain and the energy industry. The goal of almost all ongoing projects is the same, nevertheless — creating an efficient, transparent, decentralized and interactive energy market, opening new possibilities for every player. Perhaps you also have a bright idea involving blockchain? Drop us a line and IT Svit will help bring your dream to life!\nThis article was originally published here.\nFeel free to browse through the latest insights and hints on the DevOps, BigData, Machine Learning and Blockchain from IT Svit!",
      "json_metadata": "{\"tags\":[\"bitcoin\",\"blockchain\",\"ethereum\",\"tech\",\"cryptocurrency\"],\"image\":[\"https://steemitimages.com/DQmdeDpGHEUovqgnfAt4LZ9WCrjM8WV1mcyAxJT2cpzbf6S/0-beIyZLFJVMvuRZ_4.jpg\",\"https://steemitimages.com/DQmbsx3DASxQwDo13WhVYc8wGX4gz1ruMEZ41UFqPn5nPX7/0-BMPeIc8ITrrSKvNG.jpg\",\"https://steemitimages.com/DQmdVg8HoZYX9LgiquabH6jXhhaRpZHq85cx5DmZoy1gTUj/0-fELTWNQgtUC7zJzj.jpg\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
      "parent_author": "",
      "parent_permlink": "bitcoin",
      "permlink": "blockchain-and-energy-industry-what-is-ahead",
      "title": "Blockchain and Energy Industry: what is ahead?"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-10-27T14:39:24",
  "trx_id": "41c240f6d96c2b83af6ec07f7dd9130a6e7ab47c",
  "trx_in_block": 16,
  "virtual_op": 0
}
2017/10/27 14:34:06
authordevinart
permlinkre-aliyeve-crypto-is-currency-20171027t143225804z
voteraliyeve
weight10000 (100.00%)
Transaction InfoBlock #16699114/Trx 23de593a1e825d441d1a2d93e62e2b59d5e15859
View Raw JSON Data
{
  "block": 16699114,
  "op": [
    "vote",
    {
      "author": "devinart",
      "permlink": "re-aliyeve-crypto-is-currency-20171027t143225804z",
      "voter": "aliyeve",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-10-27T14:34:06",
  "trx_id": "23de593a1e825d441d1a2d93e62e2b59d5e15859",
  "trx_in_block": 9,
  "virtual_op": 0
}
2017/10/27 14:32:24
authordevinart
bodyNice post, provide interesting information @aliyeve
json metadata{"tags":["bitcoin"],"users":["aliyeve"],"app":"steemit/0.1"}
parent authoraliyeve
parent permlinkcrypto-is-currency
permlinkre-aliyeve-crypto-is-currency-20171027t143225804z
title
Transaction InfoBlock #16699080/Trx 02ae50d55f2bf063a734c76ffa6bde13604d5c2e
View Raw JSON Data
{
  "block": 16699080,
  "op": [
    "comment",
    {
      "author": "devinart",
      "body": "Nice post, provide interesting information @aliyeve",
      "json_metadata": "{\"tags\":[\"bitcoin\"],\"users\":[\"aliyeve\"],\"app\":\"steemit/0.1\"}",
      "parent_author": "aliyeve",
      "parent_permlink": "crypto-is-currency",
      "permlink": "re-aliyeve-crypto-is-currency-20171027t143225804z",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-10-27T14:32:24",
  "trx_id": "02ae50d55f2bf063a734c76ffa6bde13604d5c2e",
  "trx_in_block": 9,
  "virtual_op": 0
}
2017/10/27 14:29:18
authoraliyeve
permlinkcrypto-is-currency
voteraliyeve
weight10000 (100.00%)
Transaction InfoBlock #16699018/Trx 5b02829b47d3f66d028986c582f93ee750d7c853
View Raw JSON Data
{
  "block": 16699018,
  "op": [
    "vote",
    {
      "author": "aliyeve",
      "permlink": "crypto-is-currency",
      "voter": "aliyeve",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-10-27T14:29:18",
  "trx_id": "5b02829b47d3f66d028986c582f93ee750d7c853",
  "trx_in_block": 8,
  "virtual_op": 0
}
aliyeveupdated options for crypto-is-currency
2017/10/27 14:29:18
allow curation rewardstrue
allow votestrue
authoraliyeve
extensions[]
max accepted payout1000000.000 SBD
percent steem dollars0
permlinkcrypto-is-currency
Transaction InfoBlock #16699018/Trx 5b02829b47d3f66d028986c582f93ee750d7c853
View Raw JSON Data
{
  "block": 16699018,
  "op": [
    "comment_options",
    {
      "allow_curation_rewards": true,
      "allow_votes": true,
      "author": "aliyeve",
      "extensions": [],
      "max_accepted_payout": "1000000.000 SBD",
      "percent_steem_dollars": 0,
      "permlink": "crypto-is-currency"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-10-27T14:29:18",
  "trx_id": "5b02829b47d3f66d028986c582f93ee750d7c853",
  "trx_in_block": 8,
  "virtual_op": 0
}
aliyevepublished a new post: crypto-is-currency
2017/10/27 14:29:18
authoraliyeve
body![1-1g6sk_iZ0F9V1XCa2X1HHw.png](https://steemitimages.com/DQmV8BjMTyrSKYVjoTZ3rH6eADBAqm6vJK1gEXgk2Xu9XPb/1-1g6sk_iZ0F9V1XCa2X1HHw.png) Much of the cryptocurrency hype has much to do with the exciting price moves that oscillate wildly up and down and back up again that will make most people’s heads spin. The world has been fascinated by a new asset class that gives the opportunity for outsized returns that most mature markets can’t offer. What goes missing in a lot of discussions of these “assets” is that they are nothing like the financial assets they are often compared to like stocks. Cryptocurrencies actually have utility! They’re programmable assets that can be used to trade for any other good, service, or purpose! Their utility gives them value whereas most financial instruments are useless outside of a risk-return discussion. Many Old-World assets are purely financial whereas crypto-currencies ARE CURRENCIES! They can be and are used from everything to donating to charity, buying food, investing in companies, paying back a friend, and anything else currency can be used for. We at Airbitz have been operating in the cryptocurrency economy for over 3 years now and use Bitcoin to operate on a daily basis. We use it to pay salaries, pay bills, buy equipment and anything else we need to operate as a business. We know that every-time we use a currency like Bitcoin we are strengthening the technology in a small way. Every transaction is another proof of the utility of these powerful technologies and creates a powerful positive feedback loop, strengthening the network. We love to HODL our Bitcoin, no doubt about it but we also use Bitcoin everyday to operate and we convince more and more people and companies we interact with to accept Bitcoin as payment. All of these small actions that make use of the technology strengthen the network in their own small ways. Crypto is currency. The more people and institutions use it for transactions the more valuable the network as a whole becomes. A virtuous cycle we will continue to be a part of!
json metadata{"tags":["bitcoin","blockchain","ethereum"],"image":["https://steemitimages.com/DQmV8BjMTyrSKYVjoTZ3rH6eADBAqm6vJK1gEXgk2Xu9XPb/1-1g6sk_iZ0F9V1XCa2X1HHw.png"],"app":"steemit/0.1","format":"markdown"}
parent author
parent permlinkbitcoin
permlinkcrypto-is-currency
titleCrypto Is Currency
Transaction InfoBlock #16699018/Trx 5b02829b47d3f66d028986c582f93ee750d7c853
View Raw JSON Data
{
  "block": 16699018,
  "op": [
    "comment",
    {
      "author": "aliyeve",
      "body": "![1-1g6sk_iZ0F9V1XCa2X1HHw.png](https://steemitimages.com/DQmV8BjMTyrSKYVjoTZ3rH6eADBAqm6vJK1gEXgk2Xu9XPb/1-1g6sk_iZ0F9V1XCa2X1HHw.png)\n\nMuch of the cryptocurrency hype has much to do with the exciting price moves that oscillate wildly up and down and back up again that will make most people’s heads spin. The world has been fascinated by a new asset class that gives the opportunity for outsized returns that most mature markets can’t offer.\nWhat goes missing in a lot of discussions of these “assets” is that they are nothing like the financial assets they are often compared to like stocks. Cryptocurrencies actually have utility! They’re programmable assets that can be used to trade for any other good, service, or purpose! Their utility gives them value whereas most financial instruments are useless outside of a risk-return discussion. Many Old-World assets are purely financial whereas crypto-currencies ARE CURRENCIES! They can be and are used from everything to donating to charity, buying food, investing in companies, paying back a friend, and anything else currency can be used for.\nWe at Airbitz have been operating in the cryptocurrency economy for over 3 years now and use Bitcoin to operate on a daily basis. We use it to pay salaries, pay bills, buy equipment and anything else we need to operate as a business. We know that every-time we use a currency like Bitcoin we are strengthening the technology in a small way. Every transaction is another proof of the utility of these powerful technologies and creates a powerful positive feedback loop, strengthening the network.\nWe love to HODL our Bitcoin, no doubt about it but we also use Bitcoin everyday to operate and we convince more and more people and companies we interact with to accept Bitcoin as payment. All of these small actions that make use of the technology strengthen the network in their own small ways. Crypto is currency. The more people and institutions use it for transactions the more valuable the network as a whole becomes. A virtuous cycle we will continue to be a part of!",
      "json_metadata": "{\"tags\":[\"bitcoin\",\"blockchain\",\"ethereum\"],\"image\":[\"https://steemitimages.com/DQmV8BjMTyrSKYVjoTZ3rH6eADBAqm6vJK1gEXgk2Xu9XPb/1-1g6sk_iZ0F9V1XCa2X1HHw.png\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
      "parent_author": "",
      "parent_permlink": "bitcoin",
      "permlink": "crypto-is-currency",
      "title": "Crypto Is Currency"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-10-27T14:29:18",
  "trx_id": "5b02829b47d3f66d028986c582f93ee750d7c853",
  "trx_in_block": 8,
  "virtual_op": 0
}
2017/10/27 14:25:39
authorcrazyblogs
permlinkthings-you-should-know-before-becoming-an-entrepreneur
voteraliyeve
weight10000 (100.00%)
Transaction InfoBlock #16698945/Trx 65ab431322d4c00dec46746ed8c864f9340e0b7a
View Raw JSON Data
{
  "block": 16698945,
  "op": [
    "vote",
    {
      "author": "crazyblogs",
      "permlink": "things-you-should-know-before-becoming-an-entrepreneur",
      "voter": "aliyeve",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-10-27T14:25:39",
  "trx_id": "65ab431322d4c00dec46746ed8c864f9340e0b7a",
  "trx_in_block": 12,
  "virtual_op": 0
}
2017/10/27 14:25:03
authorcrazyblogs
bodyWell said.
json metadata{"tags":["bitcoin"],"app":"steemit/0.1"}
parent authoraliyeve
parent permlinkdeveloping-apps-for-block-chains
permlinkre-aliyeve-developing-apps-for-block-chains-20171027t142502776z
title
Transaction InfoBlock #16698933/Trx d5b95c411d1e91476766b360037ecd8b98d3cdc7
View Raw JSON Data
{
  "block": 16698933,
  "op": [
    "comment",
    {
      "author": "crazyblogs",
      "body": "Well said.",
      "json_metadata": "{\"tags\":[\"bitcoin\"],\"app\":\"steemit/0.1\"}",
      "parent_author": "aliyeve",
      "parent_permlink": "developing-apps-for-block-chains",
      "permlink": "re-aliyeve-developing-apps-for-block-chains-20171027t142502776z",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-10-27T14:25:03",
  "trx_id": "d5b95c411d1e91476766b360037ecd8b98d3cdc7",
  "trx_in_block": 18,
  "virtual_op": 0
}
2017/10/27 14:24:54
authorcheetah
bodyHi! I am a robot. I just upvoted you! I found similar content that readers might be interested in: https://blog.plan99.net/developing-apps-for-block-chains-1635cd05b47
json metadata
parent authoraliyeve
parent permlinkdeveloping-apps-for-block-chains
permlinkcheetah-re-aliyevedeveloping-apps-for-block-chains
title
Transaction InfoBlock #16698930/Trx f95b1ec95f424008352bbd0de6037d7e85390a0c
View Raw JSON Data
{
  "block": 16698930,
  "op": [
    "comment",
    {
      "author": "cheetah",
      "body": "Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in:\nhttps://blog.plan99.net/developing-apps-for-block-chains-1635cd05b47",
      "json_metadata": "",
      "parent_author": "aliyeve",
      "parent_permlink": "developing-apps-for-block-chains",
      "permlink": "cheetah-re-aliyevedeveloping-apps-for-block-chains",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-10-27T14:24:54",
  "trx_id": "f95b1ec95f424008352bbd0de6037d7e85390a0c",
  "trx_in_block": 0,
  "virtual_op": 0
}
2017/10/27 14:24:33
authoraliyeve
permlinkdeveloping-apps-for-block-chains
votercrazyblogs
weight10000 (100.00%)
Transaction InfoBlock #16698923/Trx 3917e8d8e52438d3a8456e387109181aa08fcbe6
View Raw JSON Data
{
  "block": 16698923,
  "op": [
    "vote",
    {
      "author": "aliyeve",
      "permlink": "developing-apps-for-block-chains",
      "voter": "crazyblogs",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-10-27T14:24:33",
  "trx_id": "3917e8d8e52438d3a8456e387109181aa08fcbe6",
  "trx_in_block": 8,
  "virtual_op": 0
}
2017/10/27 14:24:24
authoraliyeve
permlinkdeveloping-apps-for-block-chains
votercheetah
weight50 (0.50%)
Transaction InfoBlock #16698920/Trx 86e564fe7012cd29016f7079ab7e367ee7e90c17
View Raw JSON Data
{
  "block": 16698920,
  "op": [
    "vote",
    {
      "author": "aliyeve",
      "permlink": "developing-apps-for-block-chains",
      "voter": "cheetah",
      "weight": 50
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-10-27T14:24:24",
  "trx_id": "86e564fe7012cd29016f7079ab7e367ee7e90c17",
  "trx_in_block": 10,
  "virtual_op": 0
}
2017/10/27 14:23:45
authoraliyeve
permlinkdeveloping-apps-for-block-chains
voteraliyeve
weight10000 (100.00%)
Transaction InfoBlock #16698907/Trx 72d638334fc475ac9f5e422090f621691e9a06c0
View Raw JSON Data
{
  "block": 16698907,
  "op": [
    "vote",
    {
      "author": "aliyeve",
      "permlink": "developing-apps-for-block-chains",
      "voter": "aliyeve",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-10-27T14:23:45",
  "trx_id": "72d638334fc475ac9f5e422090f621691e9a06c0",
  "trx_in_block": 16,
  "virtual_op": 0
}
2017/10/27 14:23:45
allow curation rewardstrue
allow votestrue
authoraliyeve
extensions[]
max accepted payout1000000.000 SBD
percent steem dollars0
permlinkdeveloping-apps-for-block-chains
Transaction InfoBlock #16698907/Trx 72d638334fc475ac9f5e422090f621691e9a06c0
View Raw JSON Data
{
  "block": 16698907,
  "op": [
    "comment_options",
    {
      "allow_curation_rewards": true,
      "allow_votes": true,
      "author": "aliyeve",
      "extensions": [],
      "max_accepted_payout": "1000000.000 SBD",
      "percent_steem_dollars": 0,
      "permlink": "developing-apps-for-block-chains"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-10-27T14:23:45",
  "trx_id": "72d638334fc475ac9f5e422090f621691e9a06c0",
  "trx_in_block": 16,
  "virtual_op": 0
}
2017/10/27 14:23:45
authoraliyeve
bodyOops. I said I wasn’t going to blog about Bitcoin for a while, but Coinbase recently took an official position stating that Ethereum is now at the forefront of the digital currency space. I can only agree with 99% of Fred’s writing: his analysis of the problems of Bitcoin’s developer community mirrors my own. But I noticed a small misconception in Fred’s post that I wanted to quickly correct, and that’ll lead on nicely to a discussion of writing blockchain apps. He said: Bitcoin’s scripting language is intentionally restrictive. You might liken it to programming with an advanced graphing calculator — functionality is limited. As a result, you can only do basic things. It is also hard to understand and use. Rather than most modern programming languages where the code is almost readable like a sentence, it looks like unintelligible machine code. As a result, it took Mike Hearn, a talented ex-Google developer, a whopping 8 months to write a first version of a fairly simple crowdfunding application. Fred is talking about Lighthouse, a P2P Bitcoin Kickstarter equivalent that uses the block chain: ![1-Qe1YnCZZvDe5jN7-9oIdBw.png](https://steemitimages.com/DQmZeDjQiMffJMc5WsbFrP4BqsLeBehUDT5Pav9jSDxPkmK/1-Qe1YnCZZvDe5jN7-9oIdBw.png) It’s true that Bitcoin’s so-called “Script” is an assembly language rather than a scripting language as the name implies. But that isn’t why it took eight months to write Lighthouse. It would have taken nearly as long even if it was built on top of Ethereum because the way Lighthouse uses scripting is trivial. Working with Bitcoin script was probably only about 2% of the total effort. If we as an industry misunderstand the pain points in developing decentralised financial applications then we won’t be able to fix them. And in case you’re wondering, yes I’m still working on blockchain-type technology, this time at R3 on Corda, announced in this blog post, so I’m still thinking about these things. Many of the issues Bitcoin and Ethereum developers face are the same even on a private, institutional distributed ledger system. Sidenote: you can read a white paper written by Vitalik Buterin (or an executive summary) on Ethereum in institutional contexts that was commissioned by R3 CEV. Corda is an attempt to build a blockchain-inspired system for industrial rather than consumer use cases: we consider our “hello world” type app to be something like an interest rate swap, rather than a crowdfund or token issuance. The applications institutional customers want to use blockchains for are far more complex than anything done on top of Ethereum/Bitcoin so far, and so when we started designing Corda I knew we’d need to find ways to radically improve developer productivity. There are just so many time sinks when writing apps for a block chain. Corda doesn’t use proof of work, but it does use a similar transaction and ledger model to Bitcoin. So if making a simple app for Corda took as much work as making a simple app for Bitcoin does, we’d have a serious problem. I’ve built quite a few p2p blockchain apps. Not just Lighthouse but also smaller things like PayFile (micropayments for file downloads), a non-public micropayments-for-wifi Android app, and an app to do document timestamping on the block chain. Bitcoin apps don’t have to take eight months: that last example was written from scratch in a 30 minute live coding tutorial at DevCore 2015. By now I suspect I’ve written more actually usable decentralised apps on top of the block chain than anyone else, if we define “usable” as having a GUI you could reasonably give a non-developer friend, and “decentralised” as meaning the original website can disappear but the existing users don’t notice. The design of Corda is heavily informed by those experiences. Here were the top time sinks when I wrote Lighthouse and what we’re doing to fix them. Building the wrapper app Even for an apparently simple app there were many parts to Lighthouse that mattered but are not obvious, like the embedded wallet. That implied features like backup/restore using the 12 random words scheme, QR code rendering and so on. The bitcoinj library provides a “wallet template” app that you can copy as the basis for your own Lighthouse-like program, but copy/paste is a poor approach to code reuse. Ethereum is going in the right direction with Mist, a “dapp browser”. But Mist is really meant for developers, not ordinary users. Some operations expect you to copy/paste JSON directly into the UI, for instance. And you have to make your UI in HTML/JS, a platform which has poor productivity and is also difficult to secure. The long term plan was for Lighthouse to evolve into an app platform like what Mist is aiming to be, so people could write downloadable sandboxed apps that’d be fetched from a kind of blockchain app store, and they wouldn’t have to worry about these details. Lighthouse is not built on HTML5 so doesn’t suffer the inherent security issues of that technology. In Corda, a “cordapp” is a collection of smart contracts that verify transactions, protocols to build and do joint transaction signing, API plugins for the server and perhaps eventually also UI plugins. These can all be sandboxed and loaded dynamically. The APIs are a defined part of the platform. In this way, generic services useful for all such apps don’t have to included as a library, rather, the app is a library loaded by the node software itself. Fees It is typical for blockchain platforms to insist that every transaction has a fee. In Bitcoin, this is true even if it has so much coin age it’s obviously not a denial-of-service attempt. It’s amazing how much complexity this adds to what would otherwise be simple code. In Corda there is no native crypto-currency and thus no transaction fees. If one day the network becomes open to the entire world it would be structured like the internet itself, where end users gain access to the core network through providers that take responsibility for abuse handling, rather than the core network charging some arbitrary fee per packet and hoping that’s good enough. Contracts have hard-coded opcode/memory quotas set high enough that it should never be a problem unless a contract goes into an infinite loop. The P2P network Peer to peer systems involve simultaneously talking to lots of ‘servers’ that can die, move around, respond slowly or not at all, and provide incorrect information. This is a very different model to the standard web app design where there’s a single trusted server and the client/JS developer just assumes the server is fast, online and trustworthy. It complicates the client tremendously and often involves difficult tradeoffs. I had the benefit of building on top of bitcoinj, which handles a lot of these complexities for you, but it only got me 90% of the way. Bitcoin provides a single hammer, the block chain. And it is a mighty hammer. But even if you had Thor’s hammer building an entire house with it would be painful. Often when building apps you want point-to-point transient communication between users, not just global broadcasts that are recorded forever. In Lighthouse this is provided by a coordination server, or if you don’t want to use one of those you can move data around using email/slack/any kind of file transfer. It’s useful because crowdfunding projects and pledges include things like images, rich text, personal messages and other stuff that doesn’t make sense to drop into a financial ledger. But it means having to write separate servers, protocols, discovery logic and client code. The lack of any infrastructure for solving this problem routinely leads to bizarre hacks, like creating transactions that don’t actually change anything on the ledger and are there just to carry encrypted data between two users. It wastes resources for everyone, increases fragility, and complicates the programming model. And the Bitcoin network imposes lots of arbitrary limits to try and stop people abusing the blockchain in this way (but, of course, doesn’t provide any convenient alternative). The need for a store and forward network was something I wrote about back in 2014. But no such network exists. I think Ethereum has the beginnings of one in Whisper, but it’s not clear to me how mature it is. Corda is based on standard messaging queuing protocols (think: email for machines). Nodes are assumed to be semi-stable and have a long term identity, so sending a message to an identity that is offline simply queues it up for later delivery. Because it builds on standard protocols there are high quality, high performance implementations available that manage the details of making this reliable. You can attach arbitrary files to transactions that are then available to contract code, and those attachments are streamed over the network automatically and efficiently. Additionally, Corda has no reliance on global broadcast. Consensus mechanisms are pluggable as long as they provide finality. Thus, there are never any cases where multiple peers are giving you conflicting information about the state of the world. You never need to download or process an entire block chain. You don’t have to handle transactions being reversed. All these things dramatically simplify your code. Lifecycle management A kickstarter style crowdfund has a fairly simple lifecycle, but making sure it’s tracked and state transitions are correctly enforced is still complex. This is especially true when you recall that peer to peer networks are not always consistent and the block chain does not provide finality, so transactions can be rolled back or invalidated. Worse, the state the UI is tracking can be updated by other instances of the app at any time, which means you have to elegantly handle race conditions like “I am attempting to pledge money to a project but whilst I was sitting on the pledge screen the project became closed to new pledges” or “another app spent my money out from underneath me whilst I was in the process of trying to create a transaction”. You’d better be good at handling concurrency, otherwise you’re gonna crash in obscure situations that you probably didn’t test well. Oh, and don’t forget to checkpoint everything to disk at the right times, so you can come back from arbitrary power outages and app crashes. Most blockchain apps simply ignore these kind of details because such cases are rare, and so it’s easy to skip them without anyone noticing. But handling it all takes a lot of fiddly work. In Corda we are prototyping a framework that automates most of the tedious, error prone work in this area. R3 CTO Richard Brown was surprised when this was one of the first things I started implementing, but given my experience writing Bitcoin apps it was an obvious place to begin. Asset and trade lifecycles can be implemented as straightforward, linear code in ordinary programming languages. You can use loops, branches, and so on. We call these things protocols. Behind the scenes the control flow graph is transformed into an automatically checkpointing state machine. It is reasonable to block for days or weeks waiting for something inside a protocol. Protocols can interact with abstract institutional identities, specific people, and internal behind-the-firewall systems. The network layer figures out which IP addresses currently corresponds to an identity using an advanced network map. This is especially vital because so many of the things Corda will be used for are inherently multi-party. Testing Too many people skimp on this. Buggy contracts have been identified by Vitalik as one of the top issues facing Ethereum. Corda has the beginnings of a DSL-like API which makes writing contract unit tests easier. It also has an early version of a tool that performs and visualises network simulations, one thread per node with simulated latency, which can be seen operating in this presentation by Barclays. ![1-lNYzMIdazg-8vlQlF5syEg.png](https://steemitimages.com/DQmbBNbdmzphwgV6bJJmG4rmgVwVMxx7U8U5res5mzVvLE8/1-lNYzMIdazg-8vlQlF5syEg.png)![1-0EtzwxSbnGcepsO1F1agqQ.png](https://steemitimages.com/DQmTL2WnRqbtMZXZU1A16QmCGe14VP3xuu7wkWLssJtf5Xt/1-0EtzwxSbnGcepsO1F1agqQ.png) Learning new developer toolchains It is conventional for existing blockchain systems to invent their own languages and bytecode sets for expressing smart contracts. Corda smart contracts are Turing complete, but we think it doesn’t make sense to invent a new developer toolchain from scratch. Contracts are not so different from ordinary apps that you need to write a whole new IDE — this is extravagance. I see that Ethereum is thinking about switching to WebAssembly, so maybe they have reached a similar conclusion. Corda adapts an existing industrial strength toolchain that developers are already familiar with, meaning a top quality IDE and debugging experience right from the start. Still … no specific language is mandated, so if someone did invent a compelling custom language, it could be used. Time management A frequent Lighthouse feature request (never implemented) was to automatically invalidate all pledges when a project reached a deadline. Bitcoin does have a way to interact with time: a feature called nLockTime, but actually making things happen once the lock time was reached would have required more manual effort again. Corda has a basic event scheduler API that interacts with its equivalent of the wallet, making it much easier to write apps that do things when certain times are reached. Misc Offline support, error handling, forking Bitcoin Core to add a performance feature the upstream developers rejected (that was an extra 2 months of work on Lighthouse right there), a users guide, proper code-signed downloads, creating a threshold signature hardware-protected online update scheme, etcetera etcetera. It all adds up. Those 8 months went by pretty fast. Conclusion Whatever block chain platform you’re interested in, it’s important that we all understand what makes developing these new kinds of apps difficult. Whilst a more powerful scripting language can help a lot, that’s by no means the only thing that needs to be improved. I’ve outlined a few of the ways the Corda project is tackling developer productivity. These are not all of the design ideas we’re exploring, just the ones that are most relevant to this article. Did you think it sounded interesting? If you’re in the London area and would like to take part then check out our jobs site. If you’re not in London but have got a ton of blockchain experience and enthusiasm, then get in touch anyway: I’d still like to have a chat with you.
json metadata{"tags":["bitcoin","blockchain","ethereum"],"image":["https://steemitimages.com/DQmZeDjQiMffJMc5WsbFrP4BqsLeBehUDT5Pav9jSDxPkmK/1-Qe1YnCZZvDe5jN7-9oIdBw.png","https://steemitimages.com/DQmbBNbdmzphwgV6bJJmG4rmgVwVMxx7U8U5res5mzVvLE8/1-lNYzMIdazg-8vlQlF5syEg.png","https://steemitimages.com/DQmTL2WnRqbtMZXZU1A16QmCGe14VP3xuu7wkWLssJtf5Xt/1-0EtzwxSbnGcepsO1F1agqQ.png"],"app":"steemit/0.1","format":"markdown"}
parent author
parent permlinkbitcoin
permlinkdeveloping-apps-for-block-chains
titleDeveloping apps for block chains
Transaction InfoBlock #16698907/Trx 72d638334fc475ac9f5e422090f621691e9a06c0
View Raw JSON Data
{
  "block": 16698907,
  "op": [
    "comment",
    {
      "author": "aliyeve",
      "body": "Oops. I said I wasn’t going to blog about Bitcoin for a while, but Coinbase recently took an official position stating that Ethereum is now at the forefront of the digital currency space. I can only agree with 99% of Fred’s writing: his analysis of the problems of Bitcoin’s developer community mirrors my own.\nBut I noticed a small misconception in Fred’s post that I wanted to quickly correct, and that’ll lead on nicely to a discussion of writing blockchain apps. He said:\nBitcoin’s scripting language is intentionally restrictive. You might liken it to programming with an advanced graphing calculator — functionality is limited. As a result, you can only do basic things. It is also hard to understand and use. Rather than most modern programming languages where the code is almost readable like a sentence, it looks like unintelligible machine code. As a result, it took Mike Hearn, a talented ex-Google developer, a whopping 8 months to write a first version of a fairly simple crowdfunding application.\nFred is talking about Lighthouse, a P2P Bitcoin Kickstarter equivalent that uses the block chain:\n\n![1-Qe1YnCZZvDe5jN7-9oIdBw.png](https://steemitimages.com/DQmZeDjQiMffJMc5WsbFrP4BqsLeBehUDT5Pav9jSDxPkmK/1-Qe1YnCZZvDe5jN7-9oIdBw.png)\n\nIt’s true that Bitcoin’s so-called “Script” is an assembly language rather than a scripting language as the name implies. But that isn’t why it took eight months to write Lighthouse. It would have taken nearly as long even if it was built on top of Ethereum because the way Lighthouse uses scripting is trivial. Working with Bitcoin script was probably only about 2% of the total effort. If we as an industry misunderstand the pain points in developing decentralised financial applications then we won’t be able to fix them.\nAnd in case you’re wondering, yes I’m still working on blockchain-type technology, this time at R3 on Corda, announced in this blog post, so I’m still thinking about these things. Many of the issues Bitcoin and Ethereum developers face are the same even on a private, institutional distributed ledger system.\nSidenote: you can read a white paper written by Vitalik Buterin (or an executive summary) on Ethereum in institutional contexts that was commissioned by R3 CEV.\nCorda is an attempt to build a blockchain-inspired system for industrial rather than consumer use cases: we consider our “hello world” type app to be something like an interest rate swap, rather than a crowdfund or token issuance. The applications institutional customers want to use blockchains for are far more complex than anything done on top of Ethereum/Bitcoin so far, and so when we started designing Corda I knew we’d need to find ways to radically improve developer productivity. There are just so many time sinks when writing apps for a block chain. Corda doesn’t use proof of work, but it does use a similar transaction and ledger model to Bitcoin. So if making a simple app for Corda took as much work as making a simple app for Bitcoin does, we’d have a serious problem.\nI’ve built quite a few p2p blockchain apps. Not just Lighthouse but also smaller things like PayFile (micropayments for file downloads), a non-public micropayments-for-wifi Android app, and an app to do document timestamping on the block chain. Bitcoin apps don’t have to take eight months: that last example was written from scratch in a 30 minute live coding tutorial at DevCore 2015.\n\nBy now I suspect I’ve written more actually usable decentralised apps on top of the block chain than anyone else, if we define “usable” as having a GUI you could reasonably give a non-developer friend, and “decentralised” as meaning the original website can disappear but the existing users don’t notice.\nThe design of Corda is heavily informed by those experiences.\nHere were the top time sinks when I wrote Lighthouse and what we’re doing to fix them.\nBuilding the wrapper app\nEven for an apparently simple app there were many parts to Lighthouse that mattered but are not obvious, like the embedded wallet. That implied features like backup/restore using the 12 random words scheme, QR code rendering and so on. The bitcoinj library provides a “wallet template” app that you can copy as the basis for your own Lighthouse-like program, but copy/paste is a poor approach to code reuse.\nEthereum is going in the right direction with Mist, a “dapp browser”. But Mist is really meant for developers, not ordinary users. Some operations expect you to copy/paste JSON directly into the UI, for instance. And you have to make your UI in HTML/JS, a platform which has poor productivity and is also difficult to secure.\nThe long term plan was for Lighthouse to evolve into an app platform like what Mist is aiming to be, so people could write downloadable sandboxed apps that’d be fetched from a kind of blockchain app store, and they wouldn’t have to worry about these details. Lighthouse is not built on HTML5 so doesn’t suffer the inherent security issues of that technology.\nIn Corda, a “cordapp” is a collection of smart contracts that verify transactions, protocols to build and do joint transaction signing, API plugins for the server and perhaps eventually also UI plugins. These can all be sandboxed and loaded dynamically. The APIs are a defined part of the platform. In this way, generic services useful for all such apps don’t have to included as a library, rather, the app is a library loaded by the node software itself.\nFees\nIt is typical for blockchain platforms to insist that every transaction has a fee. In Bitcoin, this is true even if it has so much coin age it’s obviously not a denial-of-service attempt. It’s amazing how much complexity this adds to what would otherwise be simple code.\nIn Corda there is no native crypto-currency and thus no transaction fees. If one day the network becomes open to the entire world it would be structured like the internet itself, where end users gain access to the core network through providers that take responsibility for abuse handling, rather than the core network charging some arbitrary fee per packet and hoping that’s good enough. Contracts have hard-coded opcode/memory quotas set high enough that it should never be a problem unless a contract goes into an infinite loop.\nThe P2P network\nPeer to peer systems involve simultaneously talking to lots of ‘servers’ that can die, move around, respond slowly or not at all, and provide incorrect information. This is a very different model to the standard web app design where there’s a single trusted server and the client/JS developer just assumes the server is fast, online and trustworthy. It complicates the client tremendously and often involves difficult tradeoffs.\nI had the benefit of building on top of bitcoinj, which handles a lot of these complexities for you, but it only got me 90% of the way.\nBitcoin provides a single hammer, the block chain. And it is a mighty hammer. But even if you had Thor’s hammer building an entire house with it would be painful.\nOften when building apps you want point-to-point transient communication between users, not just global broadcasts that are recorded forever. In Lighthouse this is provided by a coordination server, or if you don’t want to use one of those you can move data around using email/slack/any kind of file transfer. It’s useful because crowdfunding projects and pledges include things like images, rich text, personal messages and other stuff that doesn’t make sense to drop into a financial ledger. But it means having to write separate servers, protocols, discovery logic and client code.\nThe lack of any infrastructure for solving this problem routinely leads to bizarre hacks, like creating transactions that don’t actually change anything on the ledger and are there just to carry encrypted data between two users. It wastes resources for everyone, increases fragility, and complicates the programming model. And the Bitcoin network imposes lots of arbitrary limits to try and stop people abusing the blockchain in this way (but, of course, doesn’t provide any convenient alternative).\nThe need for a store and forward network was something I wrote about back in 2014. But no such network exists. I think Ethereum has the beginnings of one in Whisper, but it’s not clear to me how mature it is.\nCorda is based on standard messaging queuing protocols (think: email for machines). Nodes are assumed to be semi-stable and have a long term identity, so sending a message to an identity that is offline simply queues it up for later delivery. Because it builds on standard protocols there are high quality, high performance implementations available that manage the details of making this reliable. You can attach arbitrary files to transactions that are then available to contract code, and those attachments are streamed over the network automatically and efficiently.\nAdditionally, Corda has no reliance on global broadcast. Consensus mechanisms are pluggable as long as they provide finality. Thus, there are never any cases where multiple peers are giving you conflicting information about the state of the world. You never need to download or process an entire block chain. You don’t have to handle transactions being reversed. All these things dramatically simplify your code.\nLifecycle management\nA kickstarter style crowdfund has a fairly simple lifecycle, but making sure it’s tracked and state transitions are correctly enforced is still complex. This is especially true when you recall that peer to peer networks are not always consistent and the block chain does not provide finality, so transactions can be rolled back or invalidated.\nWorse, the state the UI is tracking can be updated by other instances of the app at any time, which means you have to elegantly handle race conditions like “I am attempting to pledge money to a project but whilst I was sitting on the pledge screen the project became closed to new pledges” or “another app spent my money out from underneath me whilst I was in the process of trying to create a transaction”. You’d better be good at handling concurrency, otherwise you’re gonna crash in obscure situations that you probably didn’t test well.\nOh, and don’t forget to checkpoint everything to disk at the right times, so you can come back from arbitrary power outages and app crashes.\nMost blockchain apps simply ignore these kind of details because such cases are rare, and so it’s easy to skip them without anyone noticing. But handling it all takes a lot of fiddly work.\nIn Corda we are prototyping a framework that automates most of the tedious, error prone work in this area. R3 CTO Richard Brown was surprised when this was one of the first things I started implementing, but given my experience writing Bitcoin apps it was an obvious place to begin. Asset and trade lifecycles can be implemented as straightforward, linear code in ordinary programming languages. You can use loops, branches, and so on. We call these things protocols. Behind the scenes the control flow graph is transformed into an automatically checkpointing state machine. It is reasonable to block for days or weeks waiting for something inside a protocol. Protocols can interact with abstract institutional identities, specific people, and internal behind-the-firewall systems. The network layer figures out which IP addresses currently corresponds to an identity using an advanced network map. This is especially vital because so many of the things Corda will be used for are inherently multi-party.\nTesting\nToo many people skimp on this. Buggy contracts have been identified by Vitalik as one of the top issues facing Ethereum. Corda has the beginnings of a DSL-like API which makes writing contract unit tests easier. It also has an early version of a tool that performs and visualises network simulations, one thread per node with simulated latency, which can be seen operating in this presentation by Barclays.\n\n![1-lNYzMIdazg-8vlQlF5syEg.png](https://steemitimages.com/DQmbBNbdmzphwgV6bJJmG4rmgVwVMxx7U8U5res5mzVvLE8/1-lNYzMIdazg-8vlQlF5syEg.png)![1-0EtzwxSbnGcepsO1F1agqQ.png](https://steemitimages.com/DQmTL2WnRqbtMZXZU1A16QmCGe14VP3xuu7wkWLssJtf5Xt/1-0EtzwxSbnGcepsO1F1agqQ.png)\n\nLearning new developer toolchains\nIt is conventional for existing blockchain systems to invent their own languages and bytecode sets for expressing smart contracts.\nCorda smart contracts are Turing complete, but we think it doesn’t make sense to invent a new developer toolchain from scratch. Contracts are not so different from ordinary apps that you need to write a whole new IDE — this is extravagance. I see that Ethereum is thinking about switching to WebAssembly, so maybe they have reached a similar conclusion. Corda adapts an existing industrial strength toolchain that developers are already familiar with, meaning a top quality IDE and debugging experience right from the start. Still … no specific language is mandated, so if someone did invent a compelling custom language, it could be used.\nTime management\nA frequent Lighthouse feature request (never implemented) was to automatically invalidate all pledges when a project reached a deadline. Bitcoin does have a way to interact with time: a feature called nLockTime, but actually making things happen once the lock time was reached would have required more manual effort again.\nCorda has a basic event scheduler API that interacts with its equivalent of the wallet, making it much easier to write apps that do things when certain times are reached.\nMisc\nOffline support, error handling, forking Bitcoin Core to add a performance feature the upstream developers rejected (that was an extra 2 months of work on Lighthouse right there), a users guide, proper code-signed downloads, creating a threshold signature hardware-protected online update scheme, etcetera etcetera. It all adds up. Those 8 months went by pretty fast.\nConclusion\nWhatever block chain platform you’re interested in, it’s important that we all understand what makes developing these new kinds of apps difficult. Whilst a more powerful scripting language can help a lot, that’s by no means the only thing that needs to be improved.\nI’ve outlined a few of the ways the Corda project is tackling developer productivity. These are not all of the design ideas we’re exploring, just the ones that are most relevant to this article.\nDid you think it sounded interesting? If you’re in the London area and would like to take part then check out our jobs site. If you’re not in London but have got a ton of blockchain experience and enthusiasm, then get in touch anyway: I’d still like to have a chat with you.",
      "json_metadata": "{\"tags\":[\"bitcoin\",\"blockchain\",\"ethereum\"],\"image\":[\"https://steemitimages.com/DQmZeDjQiMffJMc5WsbFrP4BqsLeBehUDT5Pav9jSDxPkmK/1-Qe1YnCZZvDe5jN7-9oIdBw.png\",\"https://steemitimages.com/DQmbBNbdmzphwgV6bJJmG4rmgVwVMxx7U8U5res5mzVvLE8/1-lNYzMIdazg-8vlQlF5syEg.png\",\"https://steemitimages.com/DQmTL2WnRqbtMZXZU1A16QmCGe14VP3xuu7wkWLssJtf5Xt/1-0EtzwxSbnGcepsO1F1agqQ.png\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
      "parent_author": "",
      "parent_permlink": "bitcoin",
      "permlink": "developing-apps-for-block-chains",
      "title": "Developing apps for block chains"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-10-27T14:23:45",
  "trx_id": "72d638334fc475ac9f5e422090f621691e9a06c0",
  "trx_in_block": 16,
  "virtual_op": 0
}
2017/10/27 14:12:39
authoraliyeve
body“You will never be able to understand any of what I’ve created. I am Albert F***ing Einstein and you are all monkeys scrabbling in the dirt.” And so our resident genius, our Dr. Jekyll, explosively completed his transformation into Mr. Hyde. He declared this in front of the product design team, developers, management, and pre-launch customers. One of our project sponsors had the temerity to ask when the problem crippling our product would be fixed. Genius is a fickle beast. Sometimes you have the good fortune to work with a mad genius. Other times you are doomed to work with pure madness. There are also times when it is hard to tell the difference. This story is about the fall from grace of an extremely gifted team member with a deep understanding of our product’s architecture. He had an uncanny ability to forecast future requirements, and a ton of domain-specific knowledge. He was our top contributor. He was killing our flagship project. We’ll call this person “Rick.” ![1-4hU3Xn7wunA81I3v17JIrg.jpeg](https://steemitimages.com/DQmUmrkCWextr1zB1hYexDT4hiSZt19wG23i8XYEeNBt7qh/1-4hU3Xn7wunA81I3v17JIrg.jpeg) Rick was universally recognized on the team as the top talent. He was the lead developer and architect of our software projects. Any time anyone had a question about code or needed help with a task, they would go to Rick. Rick had a giant whiteboard installed in his office used only for this purpose. It was always cluttered with the ghosts of past discussions that wouldn’t quite erase. Any time there was a particularly challenging problem, Rick would handle it. Rick had a server with the same specs as our production server installed at his desk. He used this to run the entire application stack independently and troubleshoot every layer at once. Rick didn’t need anybody else. Rick preferred to work alone in his private work-space. Rick didn’t need anything anybody else built. He built everything he needed from scratch because it was infinitely better than the paltry offerings of mere mortals. Soon, Rick stopped attending meetings. Rick didn’t have time for meetings any more because there was too much to code. Rick closed his door. His whiteboard lay fallow. Rick no longer had time to train anyone because he had too much to solve on his own. A backlog grew behind Rick. Bugs were popping up in old tools he’d built. They sapped his attention from meeting commitments on new product development. Of course, these bugs were happening because the users had misstated their assumptions. Of course there wasn’t any problem in his work. Of course. On our project dashboard, green flags changed to yellow. Yellow changed to red. Red lights started blinking. One by one, task statuses changed to “Impeded.” Everyone was waiting for Rick. ![1-8eN_GGNhtAA2jy3qkm45eA.png](https://steemitimages.com/DQmcaC6hveVPBLMsADY8ySD5bPmDoSogQfntpn58LUtz32J/1-8eN_GGNhtAA2jy3qkm45eA.png) The project manager got a six-month extension from the sponsor. At the end of the six months, production-readiness was estimated to be seven months away. At the end of a year, production-readiness was two years out. Rick was churning out code faster than ever. He was working seven-day weeks, twelve hours a day. Everyone knew only Rick could pull the team out of this mess. Everyone held their breath and waited for Rick to invent the miracle cure that would mend this crippled project. Every day, Rick grew more belligerent and isolated. The mask was coming off. Jekyll was becoming Hyde. I participated in my first meeting with the project team about two years after the original agreed release date. I’d been aware of the project for a while, because it had grown infamous in my organization, but hadn’t been assigned to it. I was sent in to see if we could save it. My first meeting on the project was the aforementioned “Albert Einstein” meeting. Hmm. I dove into the source code. Rick was right: no-one could possibly understand what Rick had created. Except for Rick. It was a reflection of the workings of his own mind. Some of it was very clever, a lot of it was copy-pasta, it was all very idiosyncratic, and it was not at all documented. I went to our CIO with the verdict. Only Rick would ever be able to maintain this product. Plus, every day that Rick worked on the project moved the delivery date back a week. Rick was destroying our product faster than he was creating it. We sat down with Rick and had a conversation about his role in the project. We reviewed our concerns. We sidestepped his self-comparison to Albert Einstein. We explained our new strategy. The team was going to collaborate on building a new product from scratch. This effort would be very limited in scope and would only provide the bare essentials to get us to production. The whole team would contribute and be able to support it. No more bottlenecks. How did Rick react to this? The only way Rick could. Rick exploded. Rick wanted no part of this farce. If we couldn’t appreciate his genius, that was our fault, not his. Rick predicted that within months we’d come crawling back to him begging him to save us. Rick screamed that we lacked the basic mental capacity to appreciate genius when it was staring us in the face. Sadly, after this, Rick rejected months of overtures by leadership. He refused to take time off or allow any work to be delegated. He rejected repeated attempts to introduce free open source frameworks to replace his hard-to-maintain bespoke tools. He reverted code changes — including tested bug fixes — by other developers. He asserted that he wouldn’t be held accountable for supporting other people’s work. He continued publicly belittling his colleagues. We fired Rick. It took about a week for the dust to settle. It took time for the shocked team to gather themselves after losing their embattled guru. Then I saw them huddled around a whiteboard. ![1-x4skhnr9KmObqhNKzfJ4PQ.jpeg](https://steemitimages.com/DQmWj7bHED78i42EcnX7NcoKS2qR9dbKj28eQNAzte4fzKz/1-x4skhnr9KmObqhNKzfJ4PQ.jpeg) They collaborated. They designed a replacement product. It would be much simpler. It wouldn’t have all the bells and whistles. Nor would it anticipate requirements from five years down the product road map. Rick’s product supported a dynamic workflow with over fifteen thousand permutations. In reality 99% of our use cases followed one of three paths. The team hard-coded the workflow. This removed over 30% of Rick’s work. It wouldn’t have custom hand-coded components for every task. They stripped out every bespoke dependency that they could buy instead of build. This removed hundreds of hours of Rick’s contribution. But it also removed thousands of hours of technical debt. We obtained an agreement from the project sponsor to shut off some edge-case functionality. This had served only 5% of our pre-launch user group and was responsible for about a quarter of the product’s complexity. We re-released the product to this group. It consisted of 10% of Rick’s original code which was pretty stable. It also had a few thousand lines of new code to replace about 150,000 lines of incomprehensible mess. The team had replaced five years of work in about six months. Over the next few months we expanded from pilot to full customer release. Not only had we replaced what Rick had built, we sped past him and fully launched the product — all in under a year. The result was less than a fifth the size and complexity of what Rick had built. It was also hundreds of times faster and nearly bug-free despite having been assembled in a fraction of the time and serving ten times as many customers. The team went back to Rick’s other products. They threw away his old code there, too. They re-released another product of his after three years in development, with three months of concerted team effort. There were no Ricks left on the team. We didn’t have any mad geniuses building everything from scratch. But our productivity was never higher. Rick was a very talented developer. Rick could solve complex business logic problems and create sophisticated architectures to support his lofty designs. Rick could not solve the problem of how to work effectively on a team. ![1-ywaYILGFP7Gn8Sxp64qT6w.jpeg](https://steemitimages.com/DQmUuJb7D8cmcaq5nRVfbMNxytGkj4oZjNFJ4Vdpp56Q59W/1-ywaYILGFP7Gn8Sxp64qT6w.jpeg) Rick’s presence was destructive in several ways. First, he created a cult of dependence. Any problem eventually became a Rick problem, a myth he encouraged. Developers learned to stop trying and just wait for Rick. Second, he didn’t write maintainable code. He never documented or tested anything, and so failed in spite of his own intelligence. His belief in his personal infallibility trumped common sense. Third, he was personally destructive. Team members didn’t want to speak up and offer their own ideas because he always berated them for it. Rick only respected Rick and went out of his way to make everyone else feel small. Fourth, he lacked all personal accountability. No failure was his fault. He sincerely believed this, and it prevented him from learning from his own mistakes. I don’t believe Rick started out this way. I saw him at his worst. This was after years of working escalating overtime and facing increasing criticism from customers and colleagues. It’s sad that Rick descended this far. His manager shares in this responsibility. In fact, the original management team was held accountable: they were let go first. Unfortunately Rick was so far gone that he couldn’t, or wouldn’t, be brought back. No amount of coaching, feedback, time off, or assignment to other projects changed his toxic behavior. By this point the whole team knew he was destructive. But the cult of dependence was so strong that everyone believed he was the only option. There is always another option. Your team’s strength is not a function of the talent of individual members. It’s a function of their collaboration, tenacity, and mutual respect. Focus on building teams that value each other and try to bring the best out of one another. Together, they’ll be able to tackle greater challenges than Rick could ever fathom. I have published a follow-up story with our lessons learned if you are interested in reading more! Please 👏 to let me know if you enjoyed this article! Note: Some details (such as names) have been changed. I’ve never actually worked with anyone named Rick. Jonathan leads enterprise software development and architecture teams. He earned a Physics degree from Stanford University and has since spent over 10 years working in information systems architecture, data-driven business process improvement, and organizational leadership.
json metadata{"tags":["business","news","technology","kr","cn"],"image":["https://steemitimages.com/DQmUmrkCWextr1zB1hYexDT4hiSZt19wG23i8XYEeNBt7qh/1-4hU3Xn7wunA81I3v17JIrg.jpeg","https://steemitimages.com/DQmcaC6hveVPBLMsADY8ySD5bPmDoSogQfntpn58LUtz32J/1-8eN_GGNhtAA2jy3qkm45eA.png","https://steemitimages.com/DQmWj7bHED78i42EcnX7NcoKS2qR9dbKj28eQNAzte4fzKz/1-x4skhnr9KmObqhNKzfJ4PQ.jpeg","https://steemitimages.com/DQmUuJb7D8cmcaq5nRVfbMNxytGkj4oZjNFJ4Vdpp56Q59W/1-ywaYILGFP7Gn8Sxp64qT6w.jpeg"],"app":"steemit/0.1","format":"markdown"}
parent author
parent permlinkbusiness
permlinkwe-fired-our-top-talent-best-decision-we-ever-made
titleWe fired our top talent. Best decision we ever made.
Transaction InfoBlock #16698685/Trx ffc13e07fa7b71e60ceb37172a0841a3388700df
View Raw JSON Data
{
  "block": 16698685,
  "op": [
    "comment",
    {
      "author": "aliyeve",
      "body": "“You will never be able to understand any of what I’ve created. I am Albert F***ing Einstein and you are all monkeys scrabbling in the dirt.”\nAnd so our resident genius, our Dr. Jekyll, explosively completed his transformation into Mr. Hyde.\nHe declared this in front of the product design team, developers, management, and pre-launch customers. One of our project sponsors had the temerity to ask when the problem crippling our product would be fixed.\nGenius is a fickle beast. Sometimes you have the good fortune to work with a mad genius. Other times you are doomed to work with pure madness. There are also times when it is hard to tell the difference.\nThis story is about the fall from grace of an extremely gifted team member with a deep understanding of our product’s architecture. He had an uncanny ability to forecast future requirements, and a ton of domain-specific knowledge.\nHe was our top contributor. He was killing our flagship project.\nWe’ll call this person “Rick.”\n\n![1-4hU3Xn7wunA81I3v17JIrg.jpeg](https://steemitimages.com/DQmUmrkCWextr1zB1hYexDT4hiSZt19wG23i8XYEeNBt7qh/1-4hU3Xn7wunA81I3v17JIrg.jpeg)\n\nRick was universally recognized on the team as the top talent. He was the lead developer and architect of our software projects.\nAny time anyone had a question about code or needed help with a task, they would go to Rick. Rick had a giant whiteboard installed in his office used only for this purpose. It was always cluttered with the ghosts of past discussions that wouldn’t quite erase.\nAny time there was a particularly challenging problem, Rick would handle it. Rick had a server with the same specs as our production server installed at his desk. He used this to run the entire application stack independently and troubleshoot every layer at once.\nRick didn’t need anybody else. Rick preferred to work alone in his private work-space.\nRick didn’t need anything anybody else built. He built everything he needed from scratch because it was infinitely better than the paltry offerings of mere mortals.\nSoon, Rick stopped attending meetings. Rick didn’t have time for meetings any more because there was too much to code.\nRick closed his door. His whiteboard lay fallow. Rick no longer had time to train anyone because he had too much to solve on his own.\nA backlog grew behind Rick. Bugs were popping up in old tools he’d built. They sapped his attention from meeting commitments on new product development.\nOf course, these bugs were happening because the users had misstated their assumptions. Of course there wasn’t any problem in his work. Of course.\nOn our project dashboard, green flags changed to yellow. Yellow changed to red. Red lights started blinking. One by one, task statuses changed to “Impeded.” Everyone was waiting for Rick.\n\n\n![1-8eN_GGNhtAA2jy3qkm45eA.png](https://steemitimages.com/DQmcaC6hveVPBLMsADY8ySD5bPmDoSogQfntpn58LUtz32J/1-8eN_GGNhtAA2jy3qkm45eA.png)\n\nThe project manager got a six-month extension from the sponsor. At the end of the six months, production-readiness was estimated to be seven months away. At the end of a year, production-readiness was two years out.\nRick was churning out code faster than ever. He was working seven-day weeks, twelve hours a day.\nEveryone knew only Rick could pull the team out of this mess. Everyone held their breath and waited for Rick to invent the miracle cure that would mend this crippled project.\nEvery day, Rick grew more belligerent and isolated. The mask was coming off. Jekyll was becoming Hyde.\nI participated in my first meeting with the project team about two years after the original agreed release date. I’d been aware of the project for a while, because it had grown infamous in my organization, but hadn’t been assigned to it.\nI was sent in to see if we could save it.\nMy first meeting on the project was the aforementioned “Albert Einstein” meeting.\nHmm.\nI dove into the source code. Rick was right: no-one could possibly understand what Rick had created. Except for Rick. It was a reflection of the workings of his own mind. Some of it was very clever, a lot of it was copy-pasta, it was all very idiosyncratic, and it was not at all documented.\nI went to our CIO with the verdict. Only Rick would ever be able to maintain this product. Plus, every day that Rick worked on the project moved the delivery date back a week. Rick was destroying our product faster than he was creating it.\nWe sat down with Rick and had a conversation about his role in the project. We reviewed our concerns. We sidestepped his self-comparison to Albert Einstein.\nWe explained our new strategy. The team was going to collaborate on building a new product from scratch.\nThis effort would be very limited in scope and would only provide the bare essentials to get us to production. The whole team would contribute and be able to support it. No more bottlenecks.\nHow did Rick react to this?\nThe only way Rick could. Rick exploded.\nRick wanted no part of this farce. If we couldn’t appreciate his genius, that was our fault, not his. Rick predicted that within months we’d come crawling back to him begging him to save us.\nRick screamed that we lacked the basic mental capacity to appreciate genius when it was staring us in the face.\nSadly, after this, Rick rejected months of overtures by leadership. He refused to take time off or allow any work to be delegated. He rejected repeated attempts to introduce free open source frameworks to replace his hard-to-maintain bespoke tools.\nHe reverted code changes — including tested bug fixes — by other developers. He asserted that he wouldn’t be held accountable for supporting other people’s work. He continued publicly belittling his colleagues.\nWe fired Rick.\nIt took about a week for the dust to settle. It took time for the shocked team to gather themselves after losing their embattled guru.\nThen I saw them huddled around a whiteboard.\n\n![1-x4skhnr9KmObqhNKzfJ4PQ.jpeg](https://steemitimages.com/DQmWj7bHED78i42EcnX7NcoKS2qR9dbKj28eQNAzte4fzKz/1-x4skhnr9KmObqhNKzfJ4PQ.jpeg)\n\nThey collaborated. They designed a replacement product. It would be much simpler.\nIt wouldn’t have all the bells and whistles. Nor would it anticipate requirements from five years down the product road map.\nRick’s product supported a dynamic workflow with over fifteen thousand permutations. In reality 99% of our use cases followed one of three paths. The team hard-coded the workflow. This removed over 30% of Rick’s work.\nIt wouldn’t have custom hand-coded components for every task. They stripped out every bespoke dependency that they could buy instead of build.\nThis removed hundreds of hours of Rick’s contribution. But it also removed thousands of hours of technical debt.\nWe obtained an agreement from the project sponsor to shut off some edge-case functionality.\nThis had served only 5% of our pre-launch user group and was responsible for about a quarter of the product’s complexity.\nWe re-released the product to this group. It consisted of 10% of Rick’s original code which was pretty stable. It also had a few thousand lines of new code to replace about 150,000 lines of incomprehensible mess.\nThe team had replaced five years of work in about six months. Over the next few months we expanded from pilot to full customer release.\nNot only had we replaced what Rick had built, we sped past him and fully launched the product — all in under a year. The result was less than a fifth the size and complexity of what Rick had built.\nIt was also hundreds of times faster and nearly bug-free despite having been assembled in a fraction of the time and serving ten times as many customers.\nThe team went back to Rick’s other products. They threw away his old code there, too.\nThey re-released another product of his after three years in development, with three months of concerted team effort.\nThere were no Ricks left on the team. We didn’t have any mad geniuses building everything from scratch. But our productivity was never higher.\nRick was a very talented developer. Rick could solve complex business logic problems and create sophisticated architectures to support his lofty designs. Rick could not solve the problem of how to work effectively on a team.\n\n![1-ywaYILGFP7Gn8Sxp64qT6w.jpeg](https://steemitimages.com/DQmUuJb7D8cmcaq5nRVfbMNxytGkj4oZjNFJ4Vdpp56Q59W/1-ywaYILGFP7Gn8Sxp64qT6w.jpeg)\n\nRick’s presence was destructive in several ways.\nFirst, he created a cult of dependence. Any problem eventually became a Rick problem, a myth he encouraged. Developers learned to stop trying and just wait for Rick.\nSecond, he didn’t write maintainable code. He never documented or tested anything, and so failed in spite of his own intelligence. His belief in his personal infallibility trumped common sense.\nThird, he was personally destructive. Team members didn’t want to speak up and offer their own ideas because he always berated them for it. Rick only respected Rick and went out of his way to make everyone else feel small.\nFourth, he lacked all personal accountability. No failure was his fault. He sincerely believed this, and it prevented him from learning from his own mistakes.\nI don’t believe Rick started out this way. I saw him at his worst. This was after years of working escalating overtime and facing increasing criticism from customers and colleagues.\nIt’s sad that Rick descended this far. His manager shares in this responsibility. In fact, the original management team was held accountable: they were let go first.\nUnfortunately Rick was so far gone that he couldn’t, or wouldn’t, be brought back. No amount of coaching, feedback, time off, or assignment to other projects changed his toxic behavior.\nBy this point the whole team knew he was destructive. But the cult of dependence was so strong that everyone believed he was the only option.\nThere is always another option.\nYour team’s strength is not a function of the talent of individual members. It’s a function of their collaboration, tenacity, and mutual respect.\nFocus on building teams that value each other and try to bring the best out of one another.\nTogether, they’ll be able to tackle greater challenges than Rick could ever fathom.\nI have published a follow-up story with our lessons learned if you are interested in reading more!\nPlease 👏 to let me know if you enjoyed this article!\nNote: Some details (such as names) have been changed. I’ve never actually worked with anyone named Rick.\nJonathan leads enterprise software development and architecture teams.\nHe earned a Physics degree from Stanford University and has since spent over 10 years working in information systems architecture, data-driven business process improvement, and organizational leadership.",
      "json_metadata": "{\"tags\":[\"business\",\"news\",\"technology\",\"kr\",\"cn\"],\"image\":[\"https://steemitimages.com/DQmUmrkCWextr1zB1hYexDT4hiSZt19wG23i8XYEeNBt7qh/1-4hU3Xn7wunA81I3v17JIrg.jpeg\",\"https://steemitimages.com/DQmcaC6hveVPBLMsADY8ySD5bPmDoSogQfntpn58LUtz32J/1-8eN_GGNhtAA2jy3qkm45eA.png\",\"https://steemitimages.com/DQmWj7bHED78i42EcnX7NcoKS2qR9dbKj28eQNAzte4fzKz/1-x4skhnr9KmObqhNKzfJ4PQ.jpeg\",\"https://steemitimages.com/DQmUuJb7D8cmcaq5nRVfbMNxytGkj4oZjNFJ4Vdpp56Q59W/1-ywaYILGFP7Gn8Sxp64qT6w.jpeg\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
      "parent_author": "",
      "parent_permlink": "business",
      "permlink": "we-fired-our-top-talent-best-decision-we-ever-made",
      "title": "We fired our top talent. Best decision we ever made."
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-10-27T14:12:39",
  "trx_id": "ffc13e07fa7b71e60ceb37172a0841a3388700df",
  "trx_in_block": 10,
  "virtual_op": 0
}
steemdelegated 18.343 SP to @aliyeve
2017/10/13 05:10:18
delegateealiyeve
delegatorsteem
vesting shares29832.727396 VESTS
Transaction InfoBlock #16285202/Trx 0e62e113f046f3b40601b24876821f07ce3e356b
View Raw JSON Data
{
  "block": 16285202,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "aliyeve",
      "delegator": "steem",
      "vesting_shares": "29832.727396 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-10-13T05:10:18",
  "trx_id": "0e62e113f046f3b40601b24876821f07ce3e356b",
  "trx_in_block": 29,
  "virtual_op": 0
}
2017/10/03 15:20:06
authorlunamin
permlinklitecoin-price-dips-below-usd60
voteraliyeve
weight10000 (100.00%)
Transaction InfoBlock #16009530/Trx f249f2d259cc0a23c8ee818e4a196dd6c47ff5bc
View Raw JSON Data
{
  "block": 16009530,
  "op": [
    "vote",
    {
      "author": "lunamin",
      "permlink": "litecoin-price-dips-below-usd60",
      "voter": "aliyeve",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-10-03T15:20:06",
  "trx_id": "f249f2d259cc0a23c8ee818e4a196dd6c47ff5bc",
  "trx_in_block": 7,
  "virtual_op": 0
}
2017/10/03 15:02:15
authorsalamsafar
permlinkre-nextgen622-lol-moments-with-my-family-5-5-20171003t144344372z
voteraliyeve
weight10000 (100.00%)
Transaction InfoBlock #16009173/Trx 58d8709ecad87f494aafb9e7aa52a1ecc38d7aaa
View Raw JSON Data
{
  "block": 16009173,
  "op": [
    "vote",
    {
      "author": "salamsafar",
      "permlink": "re-nextgen622-lol-moments-with-my-family-5-5-20171003t144344372z",
      "voter": "aliyeve",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-10-03T15:02:15",
  "trx_id": "58d8709ecad87f494aafb9e7aa52a1ecc38d7aaa",
  "trx_in_block": 17,
  "virtual_op": 0
}
2017/10/03 08:15:57
authorlunamin
permlinkre-ramengirl-ramengirl-magazine-vol-5-feat-or-ramengirl-20171003t081302804z
voteraliyeve
weight10000 (100.00%)
Transaction InfoBlock #16001051/Trx b28e0d96d67224c73a04b827b616ea3f4c4feb3d
View Raw JSON Data
{
  "block": 16001051,
  "op": [
    "vote",
    {
      "author": "lunamin",
      "permlink": "re-ramengirl-ramengirl-magazine-vol-5-feat-or-ramengirl-20171003t081302804z",
      "voter": "aliyeve",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-10-03T08:15:57",
  "trx_id": "b28e0d96d67224c73a04b827b616ea3f4c4feb3d",
  "trx_in_block": 11,
  "virtual_op": 0
}
2017/10/03 08:04:51
authorhkimilov
permlinkthe-best-bitcoin-exchanges
voteraliyeve
weight10000 (100.00%)
Transaction InfoBlock #16000829/Trx e5ef1009c733af0616bf520f4f5e7efe42c5b393
View Raw JSON Data
{
  "block": 16000829,
  "op": [
    "vote",
    {
      "author": "hkimilov",
      "permlink": "the-best-bitcoin-exchanges",
      "voter": "aliyeve",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-10-03T08:04:51",
  "trx_id": "e5ef1009c733af0616bf520f4f5e7efe42c5b393",
  "trx_in_block": 6,
  "virtual_op": 0
}
steemcreated a new account: @aliyeve
2017/10/03 08:03:33
active{"account_auths":[],"key_auths":[["STM6gsyAySHybFPHPLNKkTjC6QA3jVjiBjK4bYGgLDMwYKCCJL1Ra",1]],"weight_threshold":1}
creatorsteem
delegation57000.000000 VESTS
extensions[]
fee0.500 STEEM
json metadata
memo keySTM835eM3mLrC4xsT1sv1URRV92guDCKxGSPsDzf4r7gatgi641Qh
new account namealiyeve
owner{"account_auths":[],"key_auths":[["STM6PuJY7gsqWUS8SWBjZqh3w81GBUMsk3yh3i5PzP8JyqRE4dfao",1]],"weight_threshold":1}
posting{"account_auths":[],"key_auths":[["STM5GZ7jxNFDW6GcYgHfFwgZ66MxkzftDzHmDe2SAZgUihVn2hBsd",1]],"weight_threshold":1}
Transaction InfoBlock #16000803/Trx c642e5a2a54bbc7fe775ef67cc49bfeafc305a65
View Raw JSON Data
{
  "block": 16000803,
  "op": [
    "account_create_with_delegation",
    {
      "active": {
        "account_auths": [],
        "key_auths": [
          [
            "STM6gsyAySHybFPHPLNKkTjC6QA3jVjiBjK4bYGgLDMwYKCCJL1Ra",
            1
          ]
        ],
        "weight_threshold": 1
      },
      "creator": "steem",
      "delegation": "57000.000000 VESTS",
      "extensions": [],
      "fee": "0.500 STEEM",
      "json_metadata": "",
      "memo_key": "STM835eM3mLrC4xsT1sv1URRV92guDCKxGSPsDzf4r7gatgi641Qh",
      "new_account_name": "aliyeve",
      "owner": {
        "account_auths": [],
        "key_auths": [
          [
            "STM6PuJY7gsqWUS8SWBjZqh3w81GBUMsk3yh3i5PzP8JyqRE4dfao",
            1
          ]
        ],
        "weight_threshold": 1
      },
      "posting": {
        "account_auths": [],
        "key_auths": [
          [
            "STM5GZ7jxNFDW6GcYgHfFwgZ66MxkzftDzHmDe2SAZgUihVn2hBsd",
            1
          ]
        ],
        "weight_threshold": 1
      }
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-10-03T08:03:33",
  "trx_id": "c642e5a2a54bbc7fe775ef67cc49bfeafc305a65",
  "trx_in_block": 4,
  "virtual_op": 0
}

Account Metadata

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

Auth Keys

Owner
Single Signature
Public Keys
STM6PuJY7gsqWUS8SWBjZqh3w81GBUMsk3yh3i5PzP8JyqRE4dfao1/1
Active
Single Signature
Public Keys
STM6gsyAySHybFPHPLNKkTjC6QA3jVjiBjK4bYGgLDMwYKCCJL1Ra1/1
Posting
Single Signature
Public Keys
STM5GZ7jxNFDW6GcYgHfFwgZ66MxkzftDzHmDe2SAZgUihVn2hBsd1/1
Memo
STM835eM3mLrC4xsT1sv1URRV92guDCKxGSPsDzf4r7gatgi641Qh
{
  "owner": {
    "account_auths": [],
    "key_auths": [
      [
        "STM6PuJY7gsqWUS8SWBjZqh3w81GBUMsk3yh3i5PzP8JyqRE4dfao",
        1
      ]
    ],
    "weight_threshold": 1
  },
  "active": {
    "account_auths": [],
    "key_auths": [
      [
        "STM6gsyAySHybFPHPLNKkTjC6QA3jVjiBjK4bYGgLDMwYKCCJL1Ra",
        1
      ]
    ],
    "weight_threshold": 1
  },
  "posting": {
    "account_auths": [],
    "key_auths": [
      [
        "STM5GZ7jxNFDW6GcYgHfFwgZ66MxkzftDzHmDe2SAZgUihVn2hBsd",
        1
      ]
    ],
    "weight_threshold": 1
  },
  "memo": "STM835eM3mLrC4xsT1sv1URRV92guDCKxGSPsDzf4r7gatgi641Qh"
}

Witness Votes

0 / 30
No active witness votes.
[]