VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS0.00%
Net Worth
0.071USD
STEEM
0.000STEEM
SBD
0.074SBD
Effective Power
5.001SP
├── Own SP
0.636SP
└── Incoming DelegationsDeleg
+4.365SP
Detailed Balance
| STEEM | ||
| balance | 0.000STEEM | STEEM |
| market_balance | 0.000STEEM | STEEM |
| savings_balance | 0.000STEEM | STEEM |
| reward_steem_balance | 0.000STEEM | STEEM |
| STEEM POWER | ||
| Own SP | 0.636SP | SP |
| Delegated Out | 0.000SP | SP |
| Delegation In | 4.365SP | SP |
| Effective Power | 5.001SP | SP |
| Reward SP (pending) | 0.039SP | SP |
| SBD | ||
| sbd_balance | 0.000SBD | SBD |
| sbd_conversions | 0.000SBD | SBD |
| sbd_market_balance | 0.000SBD | SBD |
| savings_sbd_balance | 0.000SBD | SBD |
| reward_sbd_balance | 0.074SBD | SBD |
{
"balance": "0.000 STEEM",
"savings_balance": "0.000 STEEM",
"reward_steem_balance": "0.000 STEEM",
"vesting_shares": "1035.432918 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "7108.226888 VESTS",
"sbd_balance": "0.000 SBD",
"savings_sbd_balance": "0.000 SBD",
"reward_sbd_balance": "0.074 SBD",
"conversions": []
}Account Info
| name | crypticorn |
| id | 185024 |
| rank | 692,913 |
| reputation | 206928994 |
| created | 2017-06-12T18:10:03 |
| recovery_account | steem |
| proxy | None |
| post_count | 15 |
| comment_count | 0 |
| lifetime_vote_count | 0 |
| witnesses_voted_for | 0 |
| last_post | 2018-02-28T10:22:03 |
| last_root_post | 2018-02-28T10:22:03 |
| last_vote_time | 2018-02-28T13:22:09 |
| proxied_vsf_votes | 0, 0, 0, 0 |
| can_vote | 1 |
| voting_power | 0 |
| delayed_votes | 0 |
| balance | 0.000 STEEM |
| savings_balance | 0.000 STEEM |
| sbd_balance | 0.000 SBD |
| savings_sbd_balance | 0.000 SBD |
| vesting_shares | 1035.432918 VESTS |
| delegated_vesting_shares | 0.000000 VESTS |
| received_vesting_shares | 7108.226888 VESTS |
| reward_vesting_balance | 80.639459 VESTS |
| vesting_balance | 0.000 STEEM |
| vesting_withdraw_rate | 0.000000 VESTS |
| next_vesting_withdrawal | 1969-12-31T23:59:59 |
| withdrawn | 0 |
| to_withdraw | 0 |
| withdraw_routes | 0 |
| savings_withdraw_requests | 0 |
| last_account_recovery | 1970-01-01T00:00:00 |
| reset_account | null |
| last_owner_update | 1970-01-01T00:00:00 |
| last_account_update | 2017-06-16T12:00:12 |
| mined | No |
| sbd_seconds | 0 |
| sbd_last_interest_payment | 1970-01-01T00:00:00 |
| savings_sbd_last_interest_payment | 1970-01-01T00:00:00 |
{
"id": 185024,
"name": "crypticorn",
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5fe6ukdkNRBcxpgWSr1PfFJ3acBdpTLqS2SCyom7yp64HaRnvj",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM8B5fgRpBMSdpoc9cgYHVE4iJzjFd2diQQs5QoLGJHeanqXsjBm",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM4xazHgMV8g5h5XX1bqTkW1iV2apMyEbivPKaN7TUmyZjn1JTFn",
1
]
]
},
"memo_key": "STM58Bq9UbEV3WWtgau8A4rSimcQgFVZ8fBYtbrcQJ9mymS6Pg62k",
"json_metadata": "{\"profile\":{\"profile_image\":\"https://pbs.twimg.com/profile_images/875667011656970240/jebzlX8R_400x400.jpg\"}}",
"posting_json_metadata": "{\"profile\":{\"profile_image\":\"https://pbs.twimg.com/profile_images/875667011656970240/jebzlX8R_400x400.jpg\"}}",
"proxy": "",
"last_owner_update": "1970-01-01T00:00:00",
"last_account_update": "2017-06-16T12:00:12",
"created": "2017-06-12T18:10:03",
"mined": false,
"recovery_account": "steem",
"last_account_recovery": "1970-01-01T00:00:00",
"reset_account": "null",
"comment_count": 0,
"lifetime_vote_count": 0,
"post_count": 15,
"can_vote": true,
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779058668
},
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779058668
},
"voting_power": 0,
"balance": "0.000 STEEM",
"savings_balance": "0.000 STEEM",
"sbd_balance": "0.000 SBD",
"sbd_seconds": "0",
"sbd_seconds_last_update": "1970-01-01T00:00:00",
"sbd_last_interest_payment": "1970-01-01T00:00:00",
"savings_sbd_balance": "0.000 SBD",
"savings_sbd_seconds": "0",
"savings_sbd_seconds_last_update": "1970-01-01T00:00:00",
"savings_sbd_last_interest_payment": "1970-01-01T00:00:00",
"savings_withdraw_requests": 0,
"reward_sbd_balance": "0.074 SBD",
"reward_steem_balance": "0.000 STEEM",
"reward_vesting_balance": "80.639459 VESTS",
"reward_vesting_steem": "0.039 STEEM",
"vesting_shares": "1035.432918 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "7108.226888 VESTS",
"vesting_withdraw_rate": "0.000000 VESTS",
"next_vesting_withdrawal": "1969-12-31T23:59:59",
"withdrawn": 0,
"to_withdraw": 0,
"withdraw_routes": 0,
"curation_rewards": 5,
"posting_rewards": 67,
"proxied_vsf_votes": [
0,
0,
0,
0
],
"witnesses_voted_for": 0,
"last_post": "2018-02-28T10:22:03",
"last_root_post": "2018-02-28T10:22:03",
"last_vote_time": "2018-02-28T13:22:09",
"post_bandwidth": 0,
"pending_claimed_accounts": 0,
"vesting_balance": "0.000 STEEM",
"reputation": 206928994,
"transfer_history": [],
"market_history": [],
"post_history": [],
"vote_history": [],
"other_history": [],
"witness_votes": [],
"tags_usage": [],
"guest_bloggers": [],
"rank": 692913
}Withdraw Routes
| Incoming | Outgoing |
|---|---|
Empty | Empty |
{
"incoming": [],
"outgoing": []
}From Date
To Date
steemdelegated 4.365 SP to @crypticorn2026/05/17 22:57:48
steemdelegated 4.365 SP to @crypticorn
2026/05/17 22:57:48
| delegator | steem |
| delegatee | crypticorn |
| vesting shares | 7108.226888 VESTS |
| Transaction Info | Block #106141908/Trx 1c16121d53187c9ff91cb94eff2722097e2f4b8b |
View Raw JSON Data
{
"trx_id": "1c16121d53187c9ff91cb94eff2722097e2f4b8b",
"block": 106141908,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-05-17T22:57:48",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "crypticorn",
"vesting_shares": "7108.226888 VESTS"
}
]
}steemdelegated 2.700 SP to @crypticorn2026/05/11 22:42:30
steemdelegated 2.700 SP to @crypticorn
2026/05/11 22:42:30
| delegator | steem |
| delegatee | crypticorn |
| vesting shares | 4396.016483 VESTS |
| Transaction Info | Block #105969565/Trx 6b5a495c26842cac082e3274cd835178b2741213 |
View Raw JSON Data
{
"trx_id": "6b5a495c26842cac082e3274cd835178b2741213",
"block": 105969565,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-05-11T22:42:30",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "crypticorn",
"vesting_shares": "4396.016483 VESTS"
}
]
}steemdelegated 4.373 SP to @crypticorn2026/04/25 22:20:48
steemdelegated 4.373 SP to @crypticorn
2026/04/25 22:20:48
| delegator | steem |
| delegatee | crypticorn |
| vesting shares | 7120.742644 VESTS |
| Transaction Info | Block #105509596/Trx dc98a74c20fb0ead971b11f82542636aca74821d |
View Raw JSON Data
{
"trx_id": "dc98a74c20fb0ead971b11f82542636aca74821d",
"block": 105509596,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-04-25T22:20:48",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "crypticorn",
"vesting_shares": "7120.742644 VESTS"
}
]
}steemdelegated 2.725 SP to @crypticorn2026/01/23 04:23:42
steemdelegated 2.725 SP to @crypticorn
2026/01/23 04:23:42
| delegator | steem |
| delegatee | crypticorn |
| vesting shares | 4437.563302 VESTS |
| Transaction Info | Block #102847731/Trx 9cf48469d17b1e05405cab0217cccf02966cb432 |
View Raw JSON Data
{
"trx_id": "9cf48469d17b1e05405cab0217cccf02966cb432",
"block": 102847731,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-01-23T04:23:42",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "crypticorn",
"vesting_shares": "4437.563302 VESTS"
}
]
}steemdelegated 2.826 SP to @crypticorn2024/12/16 23:42:45
steemdelegated 2.826 SP to @crypticorn
2024/12/16 23:42:45
| delegator | steem |
| delegatee | crypticorn |
| vesting shares | 4601.782499 VESTS |
| Transaction Info | Block #91294135/Trx eeb438428b8a2395ec9eabd7b3ab97197309f641 |
View Raw JSON Data
{
"trx_id": "eeb438428b8a2395ec9eabd7b3ab97197309f641",
"block": 91294135,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2024-12-16T23:42:45",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "crypticorn",
"vesting_shares": "4601.782499 VESTS"
}
]
}steemdelegated 2.930 SP to @crypticorn2023/11/13 15:27:15
steemdelegated 2.930 SP to @crypticorn
2023/11/13 15:27:15
| delegator | steem |
| delegatee | crypticorn |
| vesting shares | 4770.916031 VESTS |
| Transaction Info | Block #79848382/Trx dc3f1b7ac738cf3f87814b93818b819387df3038 |
View Raw JSON Data
{
"trx_id": "dc3f1b7ac738cf3f87814b93818b819387df3038",
"block": 79848382,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2023-11-13T15:27:15",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "crypticorn",
"vesting_shares": "4770.916031 VESTS"
}
]
}steemdelegated 4.733 SP to @crypticorn2023/09/21 20:19:45
steemdelegated 4.733 SP to @crypticorn
2023/09/21 20:19:45
| delegator | steem |
| delegatee | crypticorn |
| vesting shares | 7708.194817 VESTS |
| Transaction Info | Block #78346036/Trx a26682d819b80d2ff751118505e0b5593fe1aa5a |
View Raw JSON Data
{
"trx_id": "a26682d819b80d2ff751118505e0b5593fe1aa5a",
"block": 78346036,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2023-09-21T20:19:45",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "crypticorn",
"vesting_shares": "7708.194817 VESTS"
}
]
}steemdelegated 4.870 SP to @crypticorn2022/11/03 10:18:06
steemdelegated 4.870 SP to @crypticorn
2022/11/03 10:18:06
| delegator | steem |
| delegatee | crypticorn |
| vesting shares | 7929.876255 VESTS |
| Transaction Info | Block #69111589/Trx 8f6ee7629d50e9badae3acd3b4cd78c72743464d |
View Raw JSON Data
{
"trx_id": "8f6ee7629d50e9badae3acd3b4cd78c72743464d",
"block": 69111589,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2022-11-03T10:18:06",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "crypticorn",
"vesting_shares": "7929.876255 VESTS"
}
]
}steemdelegated 5.005 SP to @crypticorn2022/01/17 09:40:48
steemdelegated 5.005 SP to @crypticorn
2022/01/17 09:40:48
| delegator | steem |
| delegatee | crypticorn |
| vesting shares | 8150.409486 VESTS |
| Transaction Info | Block #60807890/Trx 334f092678127294359b7b1e0026e3b749187435 |
View Raw JSON Data
{
"trx_id": "334f092678127294359b7b1e0026e3b749187435",
"block": 60807890,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2022-01-17T09:40:48",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "crypticorn",
"vesting_shares": "8150.409486 VESTS"
}
]
}steemdelegated 5.118 SP to @crypticorn2021/06/13 23:38:51
steemdelegated 5.118 SP to @crypticorn
2021/06/13 23:38:51
| delegator | steem |
| delegatee | crypticorn |
| vesting shares | 8334.178144 VESTS |
| Transaction Info | Block #54606338/Trx 490acc5d42eebd5b58b6a15098e82206e4fbcf5e |
View Raw JSON Data
{
"trx_id": "490acc5d42eebd5b58b6a15098e82206e4fbcf5e",
"block": 54606338,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2021-06-13T23:38:51",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "crypticorn",
"vesting_shares": "8334.178144 VESTS"
}
]
}steemdelegated 5.233 SP to @crypticorn2020/12/11 09:59:33
steemdelegated 5.233 SP to @crypticorn
2020/12/11 09:59:33
| delegator | steem |
| delegatee | crypticorn |
| vesting shares | 8521.600118 VESTS |
| Transaction Info | Block #49353845/Trx ec469c24945db5267a3e1549ff1f01089a890a41 |
View Raw JSON Data
{
"trx_id": "ec469c24945db5267a3e1549ff1f01089a890a41",
"block": 49353845,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-12-11T09:59:33",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "crypticorn",
"vesting_shares": "8521.600118 VESTS"
}
]
}steemdelegated 1.174 SP to @crypticorn2020/12/06 03:36:42
steemdelegated 1.174 SP to @crypticorn
2020/12/06 03:36:42
| delegator | steem |
| delegatee | crypticorn |
| vesting shares | 1912.543513 VESTS |
| Transaction Info | Block #49205410/Trx fd6ea49ef6f40a6bfd66c50286cdcfdbb5686ddc |
View Raw JSON Data
{
"trx_id": "fd6ea49ef6f40a6bfd66c50286cdcfdbb5686ddc",
"block": 49205410,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-12-06T03:36:42",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "crypticorn",
"vesting_shares": "1912.543513 VESTS"
}
]
}steemdelegated 5.237 SP to @crypticorn2020/12/05 11:33:54
steemdelegated 5.237 SP to @crypticorn
2020/12/05 11:33:54
| delegator | steem |
| delegatee | crypticorn |
| vesting shares | 8527.966757 VESTS |
| Transaction Info | Block #49186517/Trx 83232b6351b8e9085706f8921e1d62cbc13b2a21 |
View Raw JSON Data
{
"trx_id": "83232b6351b8e9085706f8921e1d62cbc13b2a21",
"block": 49186517,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-12-05T11:33:54",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "crypticorn",
"vesting_shares": "8527.966757 VESTS"
}
]
}steemdelegated 1.179 SP to @crypticorn2020/11/02 13:07:36
steemdelegated 1.179 SP to @crypticorn
2020/11/02 13:07:36
| delegator | steem |
| delegatee | crypticorn |
| vesting shares | 1920.017158 VESTS |
| Transaction Info | Block #48254846/Trx edd8bf520f31dea9c71d624799c71fca677249fc |
View Raw JSON Data
{
"trx_id": "edd8bf520f31dea9c71d624799c71fca677249fc",
"block": 48254846,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-11-02T13:07:36",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "crypticorn",
"vesting_shares": "1920.017158 VESTS"
}
]
}steemdelegated 5.361 SP to @crypticorn2020/05/09 04:32:54
steemdelegated 5.361 SP to @crypticorn
2020/05/09 04:32:54
| delegator | steem |
| delegatee | crypticorn |
| vesting shares | 8730.613331 VESTS |
| Transaction Info | Block #43215644/Trx c78b97e592f95af9901f8a33c1206b8e1888214d |
View Raw JSON Data
{
"trx_id": "c78b97e592f95af9901f8a33c1206b8e1888214d",
"block": 43215644,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-05-09T04:32:54",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "crypticorn",
"vesting_shares": "8730.613331 VESTS"
}
]
}steemdelegated 1.200 SP to @crypticorn2020/05/08 07:58:48
steemdelegated 1.200 SP to @crypticorn
2020/05/08 07:58:48
| delegator | steem |
| delegatee | crypticorn |
| vesting shares | 1953.311140 VESTS |
| Transaction Info | Block #43191536/Trx a1d0961b7cb6221d93082d96b70ef3d150da2cb4 |
View Raw JSON Data
{
"trx_id": "a1d0961b7cb6221d93082d96b70ef3d150da2cb4",
"block": 43191536,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-05-08T07:58:48",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "crypticorn",
"vesting_shares": "1953.311140 VESTS"
}
]
}steemdelegated 5.365 SP to @crypticorn2020/04/28 17:01:03
steemdelegated 5.365 SP to @crypticorn
2020/04/28 17:01:03
| delegator | steem |
| delegatee | crypticorn |
| vesting shares | 8736.554943 VESTS |
| Transaction Info | Block #42921172/Trx 492eb9fba5e58e877cf55f2065d174dd187627a8 |
View Raw JSON Data
{
"trx_id": "492eb9fba5e58e877cf55f2065d174dd187627a8",
"block": 42921172,
"trx_in_block": 13,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-28T17:01:03",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "crypticorn",
"vesting_shares": "8736.554943 VESTS"
}
]
}2019/06/12 23:18:33
2019/06/12 23:18:33
| parent author | crypticorn |
| parent permlink | iota-report-decoding-the-tangle-part-2-4-the-known-and-unknown-history-of-the-iota-project |
| author | steemitboard |
| permlink | steemitboard-notify-crypticorn-20190612t231832000z |
| title | |
| body | Congratulations @crypticorn! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@crypticorn/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/@crypticorn) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=crypticorn)_</sub> ###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| Transaction Info | Block #33747507/Trx 6dc51855e458800a9b129940679cc1f2a81d7c89 |
View Raw JSON Data
{
"trx_id": "6dc51855e458800a9b129940679cc1f2a81d7c89",
"block": 33747507,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-06-12T23:18:33",
"op": [
"comment",
{
"parent_author": "crypticorn",
"parent_permlink": "iota-report-decoding-the-tangle-part-2-4-the-known-and-unknown-history-of-the-iota-project",
"author": "steemitboard",
"permlink": "steemitboard-notify-crypticorn-20190612t231832000z",
"title": "",
"body": "Congratulations @crypticorn! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@crypticorn/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/@crypticorn) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=crypticorn)_</sub>\n\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}"
}
]
}steemdelegated 5.485 SP to @crypticorn2019/05/24 20:07:06
steemdelegated 5.485 SP to @crypticorn
2019/05/24 20:07:06
| delegator | steem |
| delegatee | crypticorn |
| vesting shares | 8932.029586 VESTS |
| Transaction Info | Block #33197114/Trx 26f1a5982d7b5d4f508a2a30ba07a5206f3a3aeb |
View Raw JSON Data
{
"trx_id": "26f1a5982d7b5d4f508a2a30ba07a5206f3a3aeb",
"block": 33197114,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-05-24T20:07:06",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "crypticorn",
"vesting_shares": "8932.029586 VESTS"
}
]
}2018/06/12 19:00:39
2018/06/12 19:00:39
| parent author | crypticorn |
| parent permlink | iota-report-decoding-the-tangle-part-2-4-the-known-and-unknown-history-of-the-iota-project |
| author | steemitboard |
| permlink | steemitboard-notify-crypticorn-20180612t190038000z |
| title | |
| body | Congratulations @crypticorn! You have received a personal award! [](http://steemitboard.com/@crypticorn) 1 Year on Steemit <sub>_Click on the badge to view your Board of Honor._</sub> **Do not miss the [last announcement](https://steemit.com/steemitboard/@steemitboard/steemitboard-witness-update-2018-06-12) from @steemitboard!** > Do you like [SteemitBoard's project](https://steemit.com/@steemitboard)? Then **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| Transaction Info | Block #23264790/Trx bd9f7e3efee7770e1d7b98b2269bdd5b04f76de6 |
View Raw JSON Data
{
"trx_id": "bd9f7e3efee7770e1d7b98b2269bdd5b04f76de6",
"block": 23264790,
"trx_in_block": 8,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-12T19:00:39",
"op": [
"comment",
{
"parent_author": "crypticorn",
"parent_permlink": "iota-report-decoding-the-tangle-part-2-4-the-known-and-unknown-history-of-the-iota-project",
"author": "steemitboard",
"permlink": "steemitboard-notify-crypticorn-20180612t190038000z",
"title": "",
"body": "Congratulations @crypticorn! You have received a personal award!\n\n[](http://steemitboard.com/@crypticorn) 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 announcement](https://steemit.com/steemitboard/@steemitboard/steemitboard-witness-update-2018-06-12) from @steemitboard!**\n\n> Do you like [SteemitBoard's project](https://steemit.com/@steemitboard)? Then **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}"
}
]
}steemdelegated 5.607 SP to @crypticorn2018/05/30 18:08:18
steemdelegated 5.607 SP to @crypticorn
2018/05/30 18:08:18
| delegator | steem |
| delegatee | crypticorn |
| vesting shares | 9131.398869 VESTS |
| Transaction Info | Block #22890031/Trx fb249348edd551fc4e201997b54a700660f7dccd |
View Raw JSON Data
{
"trx_id": "fb249348edd551fc4e201997b54a700660f7dccd",
"block": 22890031,
"trx_in_block": 38,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-30T18:08:18",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "crypticorn",
"vesting_shares": "9131.398869 VESTS"
}
]
}steemdelegated 18.106 SP to @crypticorn2018/05/18 19:03:39
steemdelegated 18.106 SP to @crypticorn
2018/05/18 19:03:39
| delegator | steem |
| delegatee | crypticorn |
| vesting shares | 29484.087007 VESTS |
| Transaction Info | Block #22545965/Trx fdc3510f0f7fc902b70c8045ff6198f467a7941a |
View Raw JSON Data
{
"trx_id": "fdc3510f0f7fc902b70c8045ff6198f467a7941a",
"block": 22545965,
"trx_in_block": 40,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-18T19:03:39",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "crypticorn",
"vesting_shares": "29484.087007 VESTS"
}
]
}crypticornreceived 0.010 SBD, 0.004 SP author reward for @crypticorn / iota-report-decoding-the-tangle-part-1-how-iota-works-in-a-nutshell2018/03/07 09:46:00
crypticornreceived 0.010 SBD, 0.004 SP author reward for @crypticorn / iota-report-decoding-the-tangle-part-1-how-iota-works-in-a-nutshell
2018/03/07 09:46:00
| author | crypticorn |
| permlink | iota-report-decoding-the-tangle-part-1-how-iota-works-in-a-nutshell |
| sbd payout | 0.010 SBD |
| steem payout | 0.000 STEEM |
| vesting payout | 6.127089 VESTS |
| Transaction Info | Block #20463406/Virtual Operation #5 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 20463406,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 5,
"timestamp": "2018-03-07T09:46:00",
"op": [
"author_reward",
{
"author": "crypticorn",
"permlink": "iota-report-decoding-the-tangle-part-1-how-iota-works-in-a-nutshell",
"sbd_payout": "0.010 SBD",
"steem_payout": "0.000 STEEM",
"vesting_payout": "6.127089 VESTS"
}
]
}2018/02/28 13:22:09
2018/02/28 13:22:09
| voter | crypticorn |
| author | crypticorn |
| permlink | iota-report-decoding-the-tangle-part-1-how-iota-works-in-a-nutshell |
| weight | 10000 (100.00%) |
| Transaction Info | Block #20266281/Trx 779314a9ade3c9046c7234bb7375bdc497c71dba |
View Raw JSON Data
{
"trx_id": "779314a9ade3c9046c7234bb7375bdc497c71dba",
"block": 20266281,
"trx_in_block": 18,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-28T13:22:09",
"op": [
"vote",
{
"voter": "crypticorn",
"author": "crypticorn",
"permlink": "iota-report-decoding-the-tangle-part-1-how-iota-works-in-a-nutshell",
"weight": 10000
}
]
}2018/02/28 13:22:06
2018/02/28 13:22:06
| voter | crypticorn |
| author | crypticorn |
| permlink | iota-report-decoding-the-tangle-part-2-4-the-known-and-unknown-history-of-the-iota-project |
| weight | 10000 (100.00%) |
| Transaction Info | Block #20266280/Trx 947187263265bd1262c7e874de1cbdc776fa4675 |
View Raw JSON Data
{
"trx_id": "947187263265bd1262c7e874de1cbdc776fa4675",
"block": 20266280,
"trx_in_block": 34,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-28T13:22:06",
"op": [
"vote",
{
"voter": "crypticorn",
"author": "crypticorn",
"permlink": "iota-report-decoding-the-tangle-part-2-4-the-known-and-unknown-history-of-the-iota-project",
"weight": 10000
}
]
}2018/02/28 11:55:09
2018/02/28 11:55:09
| voter | sensation |
| author | crypticorn |
| permlink | iota-report-decoding-the-tangle-part-2-4-the-known-and-unknown-history-of-the-iota-project |
| weight | 10000 (100.00%) |
| Transaction Info | Block #20264541/Trx 5314e105f0a11b66cfb60961d3819b1fc49412f7 |
View Raw JSON Data
{
"trx_id": "5314e105f0a11b66cfb60961d3819b1fc49412f7",
"block": 20264541,
"trx_in_block": 19,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-28T11:55:09",
"op": [
"vote",
{
"voter": "sensation",
"author": "crypticorn",
"permlink": "iota-report-decoding-the-tangle-part-2-4-the-known-and-unknown-history-of-the-iota-project",
"weight": 10000
}
]
}hilmarupvoted (100.00%) @crypticorn / iota-report-decoding-the-tangle-part-1-how-iota-works-in-a-nutshell2018/02/28 10:53:42
hilmarupvoted (100.00%) @crypticorn / iota-report-decoding-the-tangle-part-1-how-iota-works-in-a-nutshell
2018/02/28 10:53:42
| voter | hilmar |
| author | crypticorn |
| permlink | iota-report-decoding-the-tangle-part-1-how-iota-works-in-a-nutshell |
| weight | 10000 (100.00%) |
| Transaction Info | Block #20263312/Trx c1f23773c5ad52f2b708fc48389b3f51af27fe9d |
View Raw JSON Data
{
"trx_id": "c1f23773c5ad52f2b708fc48389b3f51af27fe9d",
"block": 20263312,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-28T10:53:42",
"op": [
"vote",
{
"voter": "hilmar",
"author": "crypticorn",
"permlink": "iota-report-decoding-the-tangle-part-1-how-iota-works-in-a-nutshell",
"weight": 10000
}
]
}2018/02/28 10:53:12
2018/02/28 10:53:12
| parent author | crypticorn |
| parent permlink | iota-report-decoding-the-tangle-part-2-4-the-known-and-unknown-history-of-the-iota-project |
| author | hilmar |
| permlink | re-crypticorn-iota-report-decoding-the-tangle-part-2-4-the-known-and-unknown-history-of-the-iota-project-20180228t105312088z |
| title | |
| body | great! |
| json metadata | {"tags":["iota"],"app":"steemit/0.1"} |
| Transaction Info | Block #20263302/Trx 2f404a9a394ab4711e02bd57cd910d98755af123 |
View Raw JSON Data
{
"trx_id": "2f404a9a394ab4711e02bd57cd910d98755af123",
"block": 20263302,
"trx_in_block": 22,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-28T10:53:12",
"op": [
"comment",
{
"parent_author": "crypticorn",
"parent_permlink": "iota-report-decoding-the-tangle-part-2-4-the-known-and-unknown-history-of-the-iota-project",
"author": "hilmar",
"permlink": "re-crypticorn-iota-report-decoding-the-tangle-part-2-4-the-known-and-unknown-history-of-the-iota-project-20180228t105312088z",
"title": "",
"body": "great!",
"json_metadata": "{\"tags\":[\"iota\"],\"app\":\"steemit/0.1\"}"
}
]
}2018/02/28 10:52:51
2018/02/28 10:52:51
| voter | hilmar |
| author | crypticorn |
| permlink | iota-report-decoding-the-tangle-part-2-4-the-known-and-unknown-history-of-the-iota-project |
| weight | 10000 (100.00%) |
| Transaction Info | Block #20263295/Trx 4c69912c759d42300cfa9be698f18511f484e0df |
View Raw JSON Data
{
"trx_id": "4c69912c759d42300cfa9be698f18511f484e0df",
"block": 20263295,
"trx_in_block": 29,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-28T10:52:51",
"op": [
"vote",
{
"voter": "hilmar",
"author": "crypticorn",
"permlink": "iota-report-decoding-the-tangle-part-2-4-the-known-and-unknown-history-of-the-iota-project",
"weight": 10000
}
]
}2018/02/28 10:52:12
2018/02/28 10:52:12
| voter | sensation |
| author | crypticorn |
| permlink | iota-report-decoding-the-tangle-part-1-how-iota-works-in-a-nutshell |
| weight | 10000 (100.00%) |
| Transaction Info | Block #20263282/Trx b25d94cefb7dbd12bbcd92118fa08ab4994d46f6 |
View Raw JSON Data
{
"trx_id": "b25d94cefb7dbd12bbcd92118fa08ab4994d46f6",
"block": 20263282,
"trx_in_block": 27,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-28T10:52:12",
"op": [
"vote",
{
"voter": "sensation",
"author": "crypticorn",
"permlink": "iota-report-decoding-the-tangle-part-1-how-iota-works-in-a-nutshell",
"weight": 10000
}
]
}2018/02/28 10:30:39
2018/02/28 10:30:39
| voter | memekings |
| author | crypticorn |
| permlink | iota-report-decoding-the-tangle-part-1-how-iota-works-in-a-nutshell |
| weight | 10000 (100.00%) |
| Transaction Info | Block #20262851/Trx 58321e3469ddaa639b1c91b6b58b4e42f114f943 |
View Raw JSON Data
{
"trx_id": "58321e3469ddaa639b1c91b6b58b4e42f114f943",
"block": 20262851,
"trx_in_block": 13,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-28T10:30:39",
"op": [
"vote",
{
"voter": "memekings",
"author": "crypticorn",
"permlink": "iota-report-decoding-the-tangle-part-1-how-iota-works-in-a-nutshell",
"weight": 10000
}
]
}2018/02/28 10:30:33
2018/02/28 10:30:33
| voter | memekings |
| author | crypticorn |
| permlink | iota-report-decoding-the-tangle-part-2-4-the-known-and-unknown-history-of-the-iota-project |
| weight | 10000 (100.00%) |
| Transaction Info | Block #20262849/Trx 32bb2966a7cfbeb165cc2b90bf07690309167c2e |
View Raw JSON Data
{
"trx_id": "32bb2966a7cfbeb165cc2b90bf07690309167c2e",
"block": 20262849,
"trx_in_block": 72,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-28T10:30:33",
"op": [
"vote",
{
"voter": "memekings",
"author": "crypticorn",
"permlink": "iota-report-decoding-the-tangle-part-2-4-the-known-and-unknown-history-of-the-iota-project",
"weight": 10000
}
]
}2018/02/28 10:25:00
2018/02/28 10:25:00
| parent author | crypticorn |
| parent permlink | iota-report-decoding-the-tangle-part-2-4-the-known-and-unknown-history-of-the-iota-project |
| author | cheetah |
| permlink | cheetah-re-crypticorniota-report-decoding-the-tangle-part-2-4-the-known-and-unknown-history-of-the-iota-project |
| title | |
| body | Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in: https://iota-news.com/iota-report-decoding-the-tangle-part-2-4/ |
| json metadata | |
| Transaction Info | Block #20262738/Trx 692584f8c7f36eb1d42e1aaaf56ee2ad6dff746a |
View Raw JSON Data
{
"trx_id": "692584f8c7f36eb1d42e1aaaf56ee2ad6dff746a",
"block": 20262738,
"trx_in_block": 14,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-28T10:25:00",
"op": [
"comment",
{
"parent_author": "crypticorn",
"parent_permlink": "iota-report-decoding-the-tangle-part-2-4-the-known-and-unknown-history-of-the-iota-project",
"author": "cheetah",
"permlink": "cheetah-re-crypticorniota-report-decoding-the-tangle-part-2-4-the-known-and-unknown-history-of-the-iota-project",
"title": "",
"body": "Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in:\nhttps://iota-news.com/iota-report-decoding-the-tangle-part-2-4/",
"json_metadata": ""
}
]
}2018/02/28 10:22:03
2018/02/28 10:22:03
| parent author | |
| parent permlink | iota |
| author | crypticorn |
| permlink | iota-report-decoding-the-tangle-part-2-4-the-known-and-unknown-history-of-the-iota-project |
| title | IOTA Report: Decoding the Tangle Part (2/4) The Known and Unknown History of the IOTA Project |
| body |  **The original report can be found on Medium:** https://medium.com/konfid-io-blockchain-reports/iota-report-decoding-the-tangle-part-2-the-known-and-unknown-history-of-the-iota-project-3db9f5f3cfa3 # IOTA Report Overview ## Introduction This four-part series aims to provide an in-depth analysis of IOTA. We further discussed the purpose of this series in our first part: https://medium.com/konfid-io-blockchain-reports/iota-report-decoding-the-tangle-part-1-a7705c458583 In the remaining three articles, we outline the history of the IOTA project (Part 2), analyze the tech (Part 3), and evaluate its possibilities & limitations (Part 4). ## Summary / TL;DR * IOTA as a project was formed by Sergey Ivancheglo, Serguei Popov and David Sønstebø back in 2015. Dominik Schiener joined later and formed the official Foundation together with Sønstebø in 2017. * IOTA was preceded by Jinn, a project with the goal of developing ternary hardware processors. * JINN tokens were sold during a crowdfunding campaign at the end of 2014. The IOTA crowdsale took place roughly on year later, at the end of 2015. * JINN token holders were able to swap their tokens for IOTA during the crowdsale. * The IOTA protocol lacks full audibility and transparency in its provision of past transaction history. There are no verifiable sources providing the necessary information to reconstruct the transaction history of the entire Tangle back to its genesis. This means that users cannot go back to the beginning in order to access and verify the transactions that took place at the start of the IOTA protocol. * Further information on the genesis state of the Tangle are required to allow for an in-depth evaluation of the verifiable initial distribution of IOTA tokens. * The IOTA Foundation is well funded and is capable to incentivize developers and the community to further work on the project. * Despite the initial push for IOTA to be a fully community run project, it appears that a large amount of power and influence over IOTA has been centralized in the IOTA Foundation. * While the distribution of IOTA is becoming more decentralized, the Top 10 addresses account for a growing share of the supply. # Part (2/4): The Known and Unknown History of the IOTA Project ## The Team The founders of the IOTA project are Sergey Ivancheglo, Serguei Popov, and David Sønstebø as well as Dominik Schiener, who joined the team later as a Co-Founder. While Sergey Ivancheglo and Serguei Popov are the main developers of the IOTA protocol, they are very conservative about their public appearances making Dominik Schiener and David Sønstebø the two public faces of the project. Sergey Ivancheglo is credited with being one of the lead developers behind the NXT project, a blockchain platform which was one the first of its kind, allowing developers to create fungible crypto assets without having to build an underlying protocol, similar to what Ethereum offers with its ERC20 standard. Before NXT, Ivancheglo stated he has worked in game development starting in 1997 and came up with a formal version of his hardware startup Jinn, discussed in more detail later, in 2014. Serguei Popov is an academic who has a PhD in Mathematics from the Moscow State University and is currently a Professor at the University of Campinas in Brazil. He is credited with being the author of the IOTA Tangle Whitepaper and according to his personal website participated in the writing of 68 academic papers since 1994. For Dominik Schiener and David Sønstebø, the two main public faces of IOTA, very little background information is available in regards to their experience within the distributed ledger / blockchain industry and outside of it. Dominik Schiener co-founded a fiat crypto exchange in Zug, Switzerland in 2014, which he described as a failure in a German interview. He then went on to win a Blockchain Hackathon in Shanghai in early 2016 with a concept called CargoChain, an Ethereum based Trade Finance Platform. David Sønstebø co-founded Jinn with Sergey Ivancheglo and Sergei Popov, focusing on business and marketing, a role which he continues to fulfill in the IOTA Foundation. Schiener later joined the project, but we were not able to determine when he joined the project nor how exactly he became involved. ## JINN Token sale Before Ivancheglo, Popov and Sønstebø focused on developing and promoting the IOTA project, they pursued another endeavour called ‘Jinn’. The aim of Jinn was to fulfill Ivancheglo’s vision to build “the first modern ternary general purpose processor”, described as “something between Intel’s CPU and Nvidia’s GPU”, with the purpose of allowing for “ultra-low energy distributed computing” that makes computations for IoT devices more efficient. After announcing the project in September 2014, the team planned to finance the research and development of the hardware through a crowdfunding campaign. They created a cryptoasset called JINN on the NXT platform that represented a share in the profits of a company founded by Sønstebø and Ivancheglo around the same time. We have not been able to find any public records of a JINN company founded by Sønstebø. The only public records we were able to find regarding a company founded by David Sønstebø are those for IOTA AS, which was founded in November 2015 directly prior to the IOTA crowdsale. Nevertheless, the profit sharing assets were sold as JINN tokens on the NXT Asset Exchange in a Dutch Auction to interested buyers in September 2014. In the crowdsale, 100.000 (10%) of the 1.000.000 JINN tokens that were created were sold. The founders retained the remaining 900.000 (90%). Being one of NXT’s most active members, Sergey Ivancheglo’s announcement of Jinn received a lot of attention in the community which helped the project raise 8,500,000 NXT, valued at approximately $250,000 at the time (assuming an average price of around $0.03 per NXT), enabling the team to start the development of the proposed ternary general purpose processor in Q4 2014. The sale of an asset that represents a share of the profits and promises divides from actual hardware sales of a real company raises questions regarding the potential classification of the token as a security. To our knowledge the JINN crowdsale occurred without any formal KYC & AML processes. Securities regulators have been increasingly stating in public their intent to investigate ICOs which they believe qualify as a security. We however know of no statements or actions regarding the classification or status of the JINN token crowdsale. The founding team, however, seem to be aware of the need to address the structural and legal complexity of such a profit-participating token based on a conversation that David Sønstebø had with a JINN token holder in the IOTA slack channel in March 2017. In the conversation, Sønstebø discussed the need to resolve a full legal contract of ownership of JINN tokens holders. We have not been able to find details of their full approach around this issue.  In November 2015, roughly one year after the team started working on Jinn, they announced a new project called IOTA. The founders pursued a token sale for the IOTA project as well, but instead of issuing a profit sharing token like JINN, the IOTA team aimed to issue utility tokens that can solely be used to transact on the newly created platform. Additionally, the founders allowed participants in the IOTA crowdsale to buy IOTA tokens using JINN tokens at a fixed exchange rate. In the time since the IOTA project was announced, we have not been able to find substantive public information on, or evidence of, the activities of the JINN company, in particular around the development of the ternary general purpose processor. The website jinnlabs.com has not been active since 2014 (based on archive.org), and there were only three tweets from the JINN Labs twitter account all September-October 2014. We have included this section in the report due to the lack of public information regarding the status and activity of Jinn. # IOTA Token sale The IOTA crowdsale was advertised as: *“A brand new and novel micro-transaction crypto token optimized for the Internet-of-Things (IoT). Unlike the complex and heavy blockchains of Bitcoin and the like, which were designed with other uses in mind, IOTA is created to be as lightweight as possible, hence the name ‘Iota’ with emphasis on the ‘IoT’ part”* The shift from Jinn to IOTA was a logical step in the eyes of Sønstebø: *“IOTA spawned as a necessity for our vision of the Jinn project, so it only makes sense to first introduce IOTA and then Jinn afterwards”* Investors were able to purchase IOTA’s using Bitcoin, or by swapping JINN for IOTA at a fixed exchange rate of 0.0063BTC per Jinn, which corresponds to roughly the same price of JINN tokens per USD at the ICO.  ## No pre-mine at genesis What differentiated the IOTA token sale from other crowdsales (e.g. Ethereum) was that the founding team repeatedly stated that there was no official pre-mine or pre-sale, which means the development team did not retain any tokens at the inception of the protocol for themselves. They mentioned that their objective from the start was to create a fully community-driven project, not reliant on a single group of people. By contrast, the Ethereum Foundation did retain a significant proportion (12%) of newly created tokens, with individuals like Vitalik Buterin receiving around 0.7% of the total supply, personally. # Lack of usable Transaction History Our team attempted to verify the statements of the founders regarding the IOTA crowdsale through analyzing the history of the tangle backwards to the genesis block. However, the full history of the tangle back to its inception is not publicly accessible. Additionally, we were not able to find sources or statements on the structure of the **IOTA Tangle’s genesis state** apart from those made publicly by the ## Problem 1: Finding the transaction history before each snapshot The difficulty to assess the early history of the tangle, is a result of the fact that the publicly accessible transaction history is erased regularly and only non-zero addresses being retained after certain events called _**‘Snapshots’**_ (discussed in part 3 of this report). This means that the transaction history of the Tangle gets erased on a regular basis in order to keep the Tangle lightweight and prevent it from expanding too much in size. To be able to fully reconstruct the entire history of the protocol would hence require someone having all of the historical records from before each snapshot plus the ability to link pre- and post-snapshop versions of the Tangle. One potential source of the erased transaction history of Tangle before the respective Snapshots is provided by IOTA core developer Alon Elmaliah via ‘pre-snapshot’ files. However, the dates on the pre-snapshot files do not uniformly match up with the known official snapshot dates. For example, the first official snapshot date was in October 2016 and the first ‘pre-snapshot’ record by Emaliah was in September 2016. The lack of an official record or documentation from the IOTA Foundation or core developers on how to reconstruct the history of the Tangle creates extra complexity for identification of the transaction history. ## Problem 2: Finding & verifying the genesis transaction More importantly, we were not able to access in a usable manner the data provided by Elmaliah from before the *very first Snapshot* by using the software libraries provided by the IOTA foundation for viewing historical Tangle records. The current tools cannot restore the required data (e.g. timestamps or the value of a transaction) from the hash values made available by the IOTA Foundation. To retrieve transaction data from before a snapshot, one can insert the transaction hash into an online tangle explorer, such as TheTangle.org or IOTAsearch. However, the tangle explorers are also unable to access records for a transaction hash from the before the first Snapshot. When a user puts such a transaction into the tangle explorers no data is retrieved. This can easily be verified by doing the following steps.  **Step 1:** Insert a transaction hash from the pre-snapshot file dated at Nov. 24th 2016 (e.g. HRDVCRZMCWTLRYJSLRXMHIYSGFDXYVHUFYOQPFTYJJHMIZXKHKM99YVOHENDAK9HN9GMBOYOHBZ999999) into a tangle explorer. **Result:** We are able to obtain the transaction data.  **Step 2:** Insert a transaction hash from the file containing the transaction hashes **before the first Snapshot** file (e.g. YJWXVPWVKVDQPBNXENXEIVBTJEZ9EWSBAPNBAFAFXWR9LGEW9ZBOPY9CUPGBIXLGKHNZCIBTBBLTC9999) into the tangle explorer. **Result:** No data is being retrieved. On January 30th we reached out to the aforementioned core developer of IOTA, Alon Elmaliah, if he can help us to decrypt the transactions. We found out that he has not done it himself as he replied that he *“added an issue + help wanted”* on Github. As seen in the picture below, up to this day, the Github issue is still open. While it may be possible to reconstruct this pre-snapshot, the publicly available tooling is currently insufficient and would likely require an individual to have a high level of technical knowledge combined with understanding of the IOTA schema structures.  Github issue opened by IOTA Core Developer Alon Elmaliah ## Why is important to have the transaction history of a distributed ledger protocol openly available for the public to see? It is important because otherwise users cannot easily verify the entire history of the ledger, meaning that every transaction that occurred prior the first Snapshot could have been subject to a double spend or any of the potential attacks of DAG based systems, which we will outline in the 3rd part of this series. In other words, it limits the ability of IOTA users to have full transparency and auditability of the Tangle. Such auditability is one of the most important features of most blockchain-based systems, such as Bitcoin or Ethereum. We have no reason to doubt the public statements of the founders regarding the correct execution of the IOTA crowdsale and the following transactions that occured pre-first Snapshot. However, we do find it concerning that there is no ability to independently and accurately see the history of the tangle back to its genesis. Such a capability is one of the key foundations of having inherent trust in a decentralized cryptocurrency or cryptoasset, as it allows anyone to be able to verify the truth of the protocols history without needing to rely on the public statements of others or a centralized authority. The number of IOTA to be created at the genesis of the Tangle was shifted from the 1,000,000,000 from the initial token sale to 2,779,530,283,277,761. According to IOTA documentation, this number is more suitable for ternary processing and the *“high supply makes IOTA optimal for tiny nano transactions while still keeping efficiency in mind”*. However, we could not find any information about how exactly these newly added tokens were distributed, nor why exactly the developers went through the trouble of changing the supply post token sale, other then the reasons outlined above. ## Call for transparency We believe it would be in the communities interest to have an independently verifiable source show the genesis state of the Tangle. Additionally, we also believe it would be in the communities interest to have transparency from the founding team regarding the amount of IOTA they purchased or have received by other means during or after the initial token sale. Such information is valuable to understand the incentives and participation of the different members of the founding team in the ongoing development of IOTA as a technical protocol and a community. # IOTA Foundation Since the IOTA crowdsale at the end of 2015, the founders have referred to themselves as the ‘Foundation’. Shortly after the token sale, the founders started to collect donations from IOTA token holders to provide resources beyond the $526k in BTC raised in the initial token sale, to further the development of the IOTA protocol as they anticipated that the funds raised would not suffice to fulfill the long development roadmap that was ahead of them. At the end of May 2016, the official IOTA wallet, created by the founders, included a request to donate IOTA to support the Foundation. The formation of the IOTA Foundation as a legal entity in Germany occurred in October 2017 and was announced in a blog post by David Sønstebø. According to Dominik Schiener, as of November 2017, the IOTA Foundation owns around 142Ti ($255 million) as foundation funds, 22Ti ($22 million) in the ecosystem fund which is used to incentivize IOTA developers and enthusiasts to enhance the community and 20Ti ($20 million) of unclaimed IOTA from the crowdsale. Note: These $ dollar values are based on the exchange rate ($1.79) on February 23rd, 2018. The Foundation, both as a concept prior to its actual formation and now as a legal entity, look to play a critical and central role in the IOTA protocol. One such role, is the operation of the IOTA ‘Coordinator’ which has been operated by the Foundation since the inception of the protocol, including prior to the October 2017 founding of the Foundation. The coordinator plays a core technical role in the IOTA protocol, as it is currently one of the major factor that contribute to the networks centralization problem. The details of the coordinator will be further discussed in Part 3 of this series. Despite the initial push for IOTA to be a fully community run project, it appears that a large amount of power and influence over IOTA has been centralized in the IOTA Foundation. Additionally, based on reviewing the publicly available foundation documents (‘Stiftungsatzung’) for the IOTA Foundation, it looks as though Dominik Schiener and David Sønstebø have appointed themselves to life-long positions in control of the Foundation. As our team are not experts in German foundations or structures, we are not able to assess the extent of control that the two have over the Foundation nor if this is a normal set-up for such an entity. However, this level of control seems to indicate that the success or failure of IOTA will be largely dependent on the vision and leadership of both David Schiener and Dominik Sønstebø. We believe that it is important for the community to understand this and to use their own judgement as to its impact on the future of IOTA. # Evolution of Supply and Distribution of the Token  Left: IOTA token distribution at genesis (12/2015), Right: IOTA token distribution in January 2018 Note: •The genesis distribution is based on the file uploaded by Sergey Ivancheglo on the IOTA bitcointalk forum on March 6th 2016 and it is not technically verified by our research team for the reasons described above regarding access to the history of the Tangle.*  Overall there has been an increasing broader distribution of the IOTA tokens. However, there has been an increasing concentration amongst the largest IOTA wallets. The relevance of this comes from the ability for those having holdings to have an outsized impact on the market price of the token. The source of this concentration at the top does not look to be particularly unusual, and is likely driven at least in part by the IOTA Foundation now holding around 5% of all tokens as well as exchanges potentially aggregating user deposits into single wallets. As a result, we believe it is worth being aware of, but not a major concern.  # Whats Next In the next article, we are going to dive deep into the technology deployed by the IOTA project, the differences between the protocol as described in the Whitepaper and the actual implementation, and proposed future improvements to the protocol. In the last part of our four part series, we are going to evaluate the possibilities and limitations of IOTA and analyze past controversies around the IOTA Foundation.  # Editor’s Note At Konfid.io we composed a detailed report about the IOTA project for which we provide a condensed but informative four-part summary on Medium, aimed to give an overview about IOTA for entrepreneurs and companies that are planning to build on the protocol, as well as for developers and crypto-enthusiasts that are interested in the Tangle. # What is Konfid.io? Konfid.io is a technology consultancy and venture studio based in Berlin that focuses on Blockchain technology to build decentralized applications in private as well as public distributed systems. We constantly research the practical usability of distributed ledger projects and like to share our findings with the wider community. Co-Authors: Len Seitter, Hilmar M Orth, Galen Evans Based on the Research by: Len Seitter, Hilmar M Orth, Galen Evans, Rick Dudley, Ivan Ripamonti & Leo Zeitler _**Disclosure: Dr. Mervyn G. Maistry, CEO & Founder of Konfid.io, is an early supporter of DLTs since 2014 and a strong believer in the potential of DAGs as a technology. He was an advisor to IOTA and personally to Dominik Schiener and David Sonstebo, advocating for setting up a transparent and corruption-free foundation in Germany and introducing them to a number of Fortune 500 and Dax 30 clients . Since June 2017, there has been no communication and no business relationship between Dr. Mervyn G. Maistry and the IOTA foundation, its founders or any of its functionaries.**_ |
| json metadata | {"tags":["iota","tangle","nano","raiblocks","dag"],"image":["https://steemitimages.com/DQmQDaLfrGxPchQX1h9Jryq8nwwm3Ut9nbNVV7X6TrMXaSo/1_2io-7NVw5utVpMT2kHrJDA.png","https://steemitimages.com/DQmTbve7zgBiWfCZoXSpu3RaqD5A6fTErGZixQtijxx2WJ6/1_XUrzNaOgunCcYmZyHzlMnw.jpeg","https://steemitimages.com/DQmYq4ursM2wGwrCf9Sp1J7LoiNjJ5k2KQvvw264V6KNyqy/0_tBNlAcFSSiwJ4SCl.png","https://steemitimages.com/DQmbEcE7WvNUyNxYeDqrgLU9FV8KHUVTAzXgkywUvQJ1K2X/1_1lJfNAhynrkmI0z3nea9EA.png","https://steemitimages.com/DQmXvoESmp8tLFRyKXAra8m1UCmzXjdiDPHJEkvyQ9wuyGz/1_WevGtn1bCcLn2aSj4y248w.png","https://steemitimages.com/DQmdJrsvqih9ARUwYkEeTUhgKhGbb9WtsYzLyciVhkkhE9k/1_OLw9AhLPRJpOqBZ6_7_D8g.png","https://steemitimages.com/DQmbfkVSNKWvsk29XZSWPGuQb3UMHnPirkzNtXjqGNtwjNp/1_6ayRTvRkGXLMtMVdi1_GNQ.png","https://steemitimages.com/DQmZTa9dmaFVgFPSZKUXUEWGt1Jr1dN78bWqpiUgBEb8PXN/1_jlsebGqMl43KhrjRcflVeg.png","https://steemitimages.com/DQmT4KZPJNYWcgKMqKDGbAFsfPWpkrrVZqc88x6keWPdsr7/1_uZ8nrqS23unDKhC_DrdkjA.png","https://steemitimages.com/DQmad89k6meYSjNvkAYtvTwA9awteVaJNri4DqP9NYVJf9o/1_GSegJvEIn_UytvqUzPV2PA.png"],"links":["https://medium.com/konfid-io-blockchain-reports/iota-report-decoding-the-tangle-part-2-the-known-and-unknown-history-of-the-iota-project-3db9f5f3cfa3","https://medium.com/konfid-io-blockchain-reports/iota-report-decoding-the-tangle-part-1-a7705c458583"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #20262679/Trx 28415c6f72abb1cc3dfc121f51332bd0f13d8206 |
View Raw JSON Data
{
"trx_id": "28415c6f72abb1cc3dfc121f51332bd0f13d8206",
"block": 20262679,
"trx_in_block": 49,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-28T10:22:03",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "iota",
"author": "crypticorn",
"permlink": "iota-report-decoding-the-tangle-part-2-4-the-known-and-unknown-history-of-the-iota-project",
"title": "IOTA Report: Decoding the Tangle Part (2/4) The Known and Unknown History of the IOTA Project",
"body": "\n\n**The original report can be found on Medium:** https://medium.com/konfid-io-blockchain-reports/iota-report-decoding-the-tangle-part-2-the-known-and-unknown-history-of-the-iota-project-3db9f5f3cfa3\n\n# IOTA Report Overview\n## Introduction\nThis four-part series aims to provide an in-depth analysis of IOTA. We further discussed the purpose of this series in our first part: https://medium.com/konfid-io-blockchain-reports/iota-report-decoding-the-tangle-part-1-a7705c458583\n\nIn the remaining three articles, we outline the history of the IOTA project (Part 2), analyze the tech (Part 3), and evaluate its possibilities & limitations (Part 4).\n\n## Summary / TL;DR\n* IOTA as a project was formed by Sergey Ivancheglo, Serguei Popov and David Sønstebø back in 2015. Dominik Schiener joined later and formed the official Foundation together with Sønstebø in 2017.\n* IOTA was preceded by Jinn, a project with the goal of developing ternary hardware processors.\n* JINN tokens were sold during a crowdfunding campaign at the end of 2014. The IOTA crowdsale took place roughly on year later, at the end of 2015.\n* JINN token holders were able to swap their tokens for IOTA during the crowdsale.\n* The IOTA protocol lacks full audibility and transparency in its provision of past transaction history. There are no verifiable sources providing the necessary information to reconstruct the transaction history of the entire Tangle back to its genesis. This means that users cannot go back to the beginning in order to access and verify the transactions that took place at the start of the IOTA protocol.\n* Further information on the genesis state of the Tangle are required to allow for an in-depth evaluation of the verifiable initial distribution of IOTA tokens.\n* The IOTA Foundation is well funded and is capable to incentivize developers and the community to further work on the project.\n* Despite the initial push for IOTA to be a fully community run project, it appears that a large amount of power and influence over IOTA has been centralized in the IOTA Foundation.\n* While the distribution of IOTA is becoming more decentralized, the Top 10 addresses account for a growing share of the supply.\n\n# Part (2/4): The Known and Unknown History of the IOTA Project\n\n## The Team \nThe founders of the IOTA project are Sergey Ivancheglo, Serguei Popov, and David Sønstebø as well as Dominik Schiener, who joined the team later as a Co-Founder. While Sergey Ivancheglo and Serguei Popov are the main developers of the IOTA protocol, they are very conservative about their public appearances making Dominik Schiener and David Sønstebø the two public faces of the project.\n\nSergey Ivancheglo is credited with being one of the lead developers behind the NXT project, a blockchain platform which was one the first of its kind, allowing developers to create fungible crypto assets without having to build an underlying protocol, similar to what Ethereum offers with its ERC20 standard. Before NXT, Ivancheglo stated he has worked in game development starting in 1997 and came up with a formal version of his hardware startup Jinn, discussed in more detail later, in 2014.\n\nSerguei Popov is an academic who has a PhD in Mathematics from the Moscow State University and is currently a Professor at the University of Campinas in Brazil. He is credited with being the author of the IOTA Tangle Whitepaper and according to his personal website participated in the writing of 68 academic papers since 1994.\n\nFor Dominik Schiener and David Sønstebø, the two main public faces of IOTA, very little background information is available in regards to their experience within the distributed ledger / blockchain industry and outside of it. Dominik Schiener co-founded a fiat crypto exchange in Zug, Switzerland in 2014, which he described as a failure in a German interview. He then went on to win a Blockchain Hackathon in Shanghai in early 2016 with a concept called CargoChain, an Ethereum based Trade Finance Platform.\n\nDavid Sønstebø co-founded Jinn with Sergey Ivancheglo and Sergei Popov, focusing on business and marketing, a role which he continues to fulfill in the IOTA Foundation. Schiener later joined the project, but we were not able to determine when he joined the project nor how exactly he became involved.\n\n## JINN Token sale\nBefore Ivancheglo, Popov and Sønstebø focused on developing and promoting the IOTA project, they pursued another endeavour called ‘Jinn’. The aim of Jinn was to fulfill Ivancheglo’s vision to build “the first modern ternary general purpose processor”, described as “something between Intel’s CPU and Nvidia’s GPU”, with the purpose of allowing for “ultra-low energy distributed computing” that makes computations for IoT devices more efficient.\n\nAfter announcing the project in September 2014, the team planned to finance the research and development of the hardware through a crowdfunding campaign. They created a cryptoasset called JINN on the NXT platform that represented a share in the profits of a company founded by Sønstebø and Ivancheglo around the same time.\n\nWe have not been able to find any public records of a JINN company founded by Sønstebø. The only public records we were able to find regarding a company founded by David Sønstebø are those for IOTA AS, which was founded in November 2015 directly prior to the IOTA crowdsale.\n\nNevertheless, the profit sharing assets were sold as JINN tokens on the NXT Asset Exchange in a Dutch Auction to interested buyers in September 2014. In the crowdsale, 100.000 (10%) of the 1.000.000 JINN tokens that were created were sold. The founders retained the remaining 900.000 (90%).\n\nBeing one of NXT’s most active members, Sergey Ivancheglo’s announcement of Jinn received a lot of attention in the community which helped the project raise 8,500,000 NXT, valued at approximately $250,000 at the time (assuming an average price of around $0.03 per NXT), enabling the team to start the development of the proposed ternary general purpose processor in Q4 2014.\n\nThe sale of an asset that represents a share of the profits and promises divides from actual hardware sales of a real company raises questions regarding the potential classification of the token as a security. To our knowledge the JINN crowdsale occurred without any formal KYC & AML processes. Securities regulators have been increasingly stating in public their intent to investigate ICOs which they believe qualify as a security. We however know of no statements or actions regarding the classification or status of the JINN token crowdsale.\n\nThe founding team, however, seem to be aware of the need to address the structural and legal complexity of such a profit-participating token based on a conversation that David Sønstebø had with a JINN token holder in the IOTA slack channel in March 2017. In the conversation, Sønstebø discussed the need to resolve a full legal contract of ownership of JINN tokens holders. We have not been able to find details of their full approach around this issue.\n\n\nIn November 2015, roughly one year after the team started working on Jinn, they announced a new project called IOTA. The founders pursued a token sale for the IOTA project as well, but instead of issuing a profit sharing token like JINN, the IOTA team aimed to issue utility tokens that can solely be used to transact on the newly created platform. Additionally, the founders allowed participants in the IOTA crowdsale to buy IOTA tokens using JINN tokens at a fixed exchange rate.\n\nIn the time since the IOTA project was announced, we have not been able to find substantive public information on, or evidence of, the activities of the JINN company, in particular around the development of the ternary general purpose processor. The website jinnlabs.com has not been active since 2014 (based on archive.org), and there were only three tweets from the JINN Labs twitter account all September-October 2014. We have included this section in the report due to the lack of public information regarding the status and activity of Jinn.\n\n# IOTA Token sale\nThe IOTA crowdsale was advertised as:\n\n*“A brand new and novel micro-transaction crypto token optimized for the Internet-of-Things (IoT). Unlike the complex and heavy blockchains of Bitcoin and the like, which were designed with other uses in mind, IOTA is created to be as lightweight as possible, hence the name ‘Iota’ with emphasis on the ‘IoT’ part”*\n\nThe shift from Jinn to IOTA was a logical step in the eyes of Sønstebø:\n\n*“IOTA spawned as a necessity for our vision of the Jinn project, so it only makes sense to first introduce IOTA and then Jinn afterwards”*\n\nInvestors were able to purchase IOTA’s using Bitcoin, or by swapping JINN for IOTA at a fixed exchange rate of 0.0063BTC per Jinn, which corresponds to roughly the same price of JINN tokens per USD at the ICO.\n\n\n\n## No pre-mine at genesis\nWhat differentiated the IOTA token sale from other crowdsales (e.g. Ethereum) was that the founding team repeatedly stated that there was no official pre-mine or pre-sale, which means the development team did not retain any tokens at the inception of the protocol for themselves. They mentioned that their objective from the start was to create a fully community-driven project, not reliant on a single group of people. By contrast, the Ethereum Foundation did retain a significant proportion (12%) of newly created tokens, with individuals like Vitalik Buterin receiving around 0.7% of the total supply, personally.\n\n# Lack of usable Transaction History\nOur team attempted to verify the statements of the founders regarding the IOTA crowdsale through analyzing the history of the tangle backwards to the genesis block. However, the full history of the tangle back to its inception is not publicly accessible. Additionally, we were not able to find sources or statements on the structure of the **IOTA Tangle’s genesis state** apart from those made publicly by the \n\n## Problem 1: Finding the transaction history before each snapshot\nThe difficulty to assess the early history of the tangle, is a result of the fact that the publicly accessible transaction history is erased regularly and only non-zero addresses being retained after certain events called _**‘Snapshots’**_ (discussed in part 3 of this report). This means that the transaction history of the Tangle gets erased on a regular basis in order to keep the Tangle lightweight and prevent it from expanding too much in size.\n\nTo be able to fully reconstruct the entire history of the protocol would hence require someone having all of the historical records from before each snapshot plus the ability to link pre- and post-snapshop versions of the Tangle.\n\nOne potential source of the erased transaction history of Tangle before the respective Snapshots is provided by IOTA core developer Alon Elmaliah via ‘pre-snapshot’ files. However, the dates on the pre-snapshot files do not uniformly match up with the known official snapshot dates. For example, the first official snapshot date was in October 2016 and the first ‘pre-snapshot’ record by Emaliah was in September 2016. The lack of an official record or documentation from the IOTA Foundation or core developers on how to reconstruct the history of the Tangle creates extra complexity for identification of the transaction history.\n\n## Problem 2: Finding & verifying the genesis transaction\nMore importantly, we were not able to access in a usable manner the data provided by Elmaliah from before the *very first Snapshot* by using the software libraries provided by the IOTA foundation for viewing historical Tangle records. The current tools cannot restore the required data (e.g. timestamps or the value of a transaction) from the hash values made available by the IOTA Foundation.\n\nTo retrieve transaction data from before a snapshot, one can insert the transaction hash into an online tangle explorer, such as TheTangle.org or IOTAsearch. However, the tangle explorers are also unable to access records for a transaction hash from the before the first Snapshot. When a user puts such a transaction into the tangle explorers no data is retrieved. This can easily be verified by doing the following steps.\n\n\n\n**Step 1:** Insert a transaction hash from the pre-snapshot file dated at Nov. 24th 2016 (e.g. HRDVCRZMCWTLRYJSLRXMHIYSGFDXYVHUFYOQPFTYJJHMIZXKHKM99YVOHENDAK9HN9GMBOYOHBZ999999) into a tangle explorer.\n\n**Result:** We are able to obtain the transaction data.\n\n\n\n**Step 2:** Insert a transaction hash from the file containing the transaction hashes **before the first Snapshot** file (e.g. YJWXVPWVKVDQPBNXENXEIVBTJEZ9EWSBAPNBAFAFXWR9LGEW9ZBOPY9CUPGBIXLGKHNZCIBTBBLTC9999) into the tangle explorer.\n\n**Result:** No data is being retrieved.\n\nOn January 30th we reached out to the aforementioned core developer of IOTA, Alon Elmaliah, if he can help us to decrypt the transactions. We found out that he has not done it himself as he replied that he *“added an issue + help wanted”* on Github. As seen in the picture below, up to this day, the Github issue is still open. While it may be possible to reconstruct this pre-snapshot, the publicly available tooling is currently insufficient and would likely require an individual to have a high level of technical knowledge combined with understanding of the IOTA schema structures.\n\n\nGithub issue opened by IOTA Core Developer Alon Elmaliah\n\n## Why is important to have the transaction history of a distributed ledger protocol openly available for the public to see?\n\nIt is important because otherwise users cannot easily verify the entire history of the ledger, meaning that every transaction that occurred prior the first Snapshot could have been subject to a double spend or any of the potential attacks of DAG based systems, which we will outline in the 3rd part of this series.\n\nIn other words, it limits the ability of IOTA users to have full transparency and auditability of the Tangle. Such auditability is one of the most important features of most blockchain-based systems, such as Bitcoin or Ethereum.\n\nWe have no reason to doubt the public statements of the founders regarding the correct execution of the IOTA crowdsale and the following transactions that occured pre-first Snapshot. However, we do find it concerning that there is no ability to independently and accurately see the history of the tangle back to its genesis. Such a capability is one of the key foundations of having inherent trust in a decentralized cryptocurrency or cryptoasset, as it allows anyone to be able to verify the truth of the protocols history without needing to rely on the public statements of others or a centralized authority.\n\nThe number of IOTA to be created at the genesis of the Tangle was shifted from the 1,000,000,000 from the initial token sale to 2,779,530,283,277,761. According to IOTA documentation, this number is more suitable for ternary processing and the *“high supply makes IOTA optimal for tiny nano transactions while still keeping efficiency in mind”*. However, we could not find any information about how exactly these newly added tokens were distributed, nor why exactly the developers went through the trouble of changing the supply post token sale, other then the reasons outlined above.\n\n## Call for transparency\nWe believe it would be in the communities interest to have an independently verifiable source show the genesis state of the Tangle. Additionally, we also believe it would be in the communities interest to have transparency from the founding team regarding the amount of IOTA they purchased or have received by other means during or after the initial token sale. Such information is valuable to understand the incentives and participation of the different members of the founding team in the ongoing development of IOTA as a technical protocol and a community.\n\n# IOTA Foundation\n\nSince the IOTA crowdsale at the end of 2015, the founders have referred to themselves as the ‘Foundation’. Shortly after the token sale, the founders started to collect donations from IOTA token holders to provide resources beyond the $526k in BTC raised in the initial token sale, to further the development of the IOTA protocol as they anticipated that the funds raised would not suffice to fulfill the long development roadmap that was ahead of them. At the end of May 2016, the official IOTA wallet, created by the founders, included a request to donate IOTA to support the Foundation.\n\nThe formation of the IOTA Foundation as a legal entity in Germany occurred in October 2017 and was announced in a blog post by David Sønstebø. According to Dominik Schiener, as of November 2017, the IOTA Foundation owns around 142Ti ($255 million) as foundation funds, 22Ti ($22 million) in the ecosystem fund which is used to incentivize IOTA developers and enthusiasts to enhance the community and 20Ti ($20 million) of unclaimed IOTA from the crowdsale. Note: These $ dollar values are based on the exchange rate ($1.79) on February 23rd, 2018.\n\nThe Foundation, both as a concept prior to its actual formation and now as a legal entity, look to play a critical and central role in the IOTA protocol. One such role, is the operation of the IOTA ‘Coordinator’ which has been operated by the Foundation since the inception of the protocol, including prior to the October 2017 founding of the Foundation. The coordinator plays a core technical role in the IOTA protocol, as it is currently one of the major factor that contribute to the networks centralization problem. The details of the coordinator will be further discussed in Part 3 of this series.\n\nDespite the initial push for IOTA to be a fully community run project, it appears that a large amount of power and influence over IOTA has been centralized in the IOTA Foundation. Additionally, based on reviewing the publicly available foundation documents (‘Stiftungsatzung’) for the IOTA Foundation, it looks as though Dominik Schiener and David Sønstebø have appointed themselves to life-long positions in control of the Foundation. As our team are not experts in German foundations or structures, we are not able to assess the extent of control that the two have over the Foundation nor if this is a normal set-up for such an entity. However, this level of control seems to indicate that the success or failure of IOTA will be largely dependent on the vision and leadership of both David Schiener and Dominik Sønstebø. We believe that it is important for the community to understand this and to use their own judgement as to its impact on the future of IOTA.\n\n# Evolution of Supply and Distribution of the Token\n\n\n\nLeft: IOTA token distribution at genesis (12/2015), Right: IOTA token distribution in January 2018\n\nNote: •The genesis distribution is based on the file uploaded by Sergey Ivancheglo on the IOTA bitcointalk forum on March 6th 2016 and it is not technically verified by our research team for the reasons described above regarding access to the history of the Tangle.*\n\n\n\nOverall there has been an increasing broader distribution of the IOTA tokens. However, there has been an increasing concentration amongst the largest IOTA wallets. The relevance of this comes from the ability for those having holdings to have an outsized impact on the market price of the token. The source of this concentration at the top does not look to be particularly unusual, and is likely driven at least in part by the IOTA Foundation now holding around 5% of all tokens as well as exchanges potentially aggregating user deposits into single wallets. As a result, we believe it is worth being aware of, but not a major concern.\n\n\n\n# Whats Next\nIn the next article, we are going to dive deep into the technology deployed by the IOTA project, the differences between the protocol as described in the Whitepaper and the actual implementation, and proposed future improvements to the protocol. In the last part of our four part series, we are going to evaluate the possibilities and limitations of IOTA and analyze past controversies around the IOTA Foundation.\n\n\n\n# Editor’s Note\nAt Konfid.io we composed a detailed report about the IOTA project for which we provide a condensed but informative four-part summary on Medium, aimed to give an overview about IOTA for entrepreneurs and companies that are planning to build on the protocol, as well as for developers and crypto-enthusiasts that are interested in the Tangle.\n\n# What is Konfid.io?\nKonfid.io is a technology consultancy and venture studio based in Berlin that focuses on Blockchain technology to build decentralized applications in private as well as public distributed systems. We constantly research the practical usability of distributed ledger projects and like to share our findings with the wider community.\n\nCo-Authors: Len Seitter, Hilmar M Orth, Galen Evans\n\nBased on the Research by: Len Seitter, Hilmar M Orth, Galen Evans, Rick Dudley, Ivan Ripamonti & Leo Zeitler\n\n_**Disclosure: Dr. Mervyn G. Maistry, CEO & Founder of Konfid.io, is an early supporter of DLTs since 2014 and a strong believer in the potential of DAGs as a technology. He was an advisor to IOTA and personally to Dominik Schiener and David Sonstebo, advocating for setting up a transparent and corruption-free foundation in Germany and introducing them to a number of Fortune 500 and Dax 30 clients . Since June 2017, there has been no communication and no business relationship between Dr. Mervyn G. Maistry and the IOTA foundation, its founders or any of its functionaries.**_",
"json_metadata": "{\"tags\":[\"iota\",\"tangle\",\"nano\",\"raiblocks\",\"dag\"],\"image\":[\"https://steemitimages.com/DQmQDaLfrGxPchQX1h9Jryq8nwwm3Ut9nbNVV7X6TrMXaSo/1_2io-7NVw5utVpMT2kHrJDA.png\",\"https://steemitimages.com/DQmTbve7zgBiWfCZoXSpu3RaqD5A6fTErGZixQtijxx2WJ6/1_XUrzNaOgunCcYmZyHzlMnw.jpeg\",\"https://steemitimages.com/DQmYq4ursM2wGwrCf9Sp1J7LoiNjJ5k2KQvvw264V6KNyqy/0_tBNlAcFSSiwJ4SCl.png\",\"https://steemitimages.com/DQmbEcE7WvNUyNxYeDqrgLU9FV8KHUVTAzXgkywUvQJ1K2X/1_1lJfNAhynrkmI0z3nea9EA.png\",\"https://steemitimages.com/DQmXvoESmp8tLFRyKXAra8m1UCmzXjdiDPHJEkvyQ9wuyGz/1_WevGtn1bCcLn2aSj4y248w.png\",\"https://steemitimages.com/DQmdJrsvqih9ARUwYkEeTUhgKhGbb9WtsYzLyciVhkkhE9k/1_OLw9AhLPRJpOqBZ6_7_D8g.png\",\"https://steemitimages.com/DQmbfkVSNKWvsk29XZSWPGuQb3UMHnPirkzNtXjqGNtwjNp/1_6ayRTvRkGXLMtMVdi1_GNQ.png\",\"https://steemitimages.com/DQmZTa9dmaFVgFPSZKUXUEWGt1Jr1dN78bWqpiUgBEb8PXN/1_jlsebGqMl43KhrjRcflVeg.png\",\"https://steemitimages.com/DQmT4KZPJNYWcgKMqKDGbAFsfPWpkrrVZqc88x6keWPdsr7/1_uZ8nrqS23unDKhC_DrdkjA.png\",\"https://steemitimages.com/DQmad89k6meYSjNvkAYtvTwA9awteVaJNri4DqP9NYVJf9o/1_GSegJvEIn_UytvqUzPV2PA.png\"],\"links\":[\"https://medium.com/konfid-io-blockchain-reports/iota-report-decoding-the-tangle-part-2-the-known-and-unknown-history-of-the-iota-project-3db9f5f3cfa3\",\"https://medium.com/konfid-io-blockchain-reports/iota-report-decoding-the-tangle-part-1-a7705c458583\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}2018/02/28 09:47:09
2018/02/28 09:47:09
| parent author | crypticorn |
| parent permlink | iota-report-decoding-the-tangle-part-1-how-iota-works-in-a-nutshell |
| author | cheetah |
| permlink | cheetah-re-crypticorniota-report-decoding-the-tangle-part-1-how-iota-works-in-a-nutshell |
| title | |
| body | Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in: https://medium.com/konfid-io-blockchain-reports/iota-report-decoding-the-tangle-part-1-a7705c458583 |
| json metadata | |
| Transaction Info | Block #20261981/Trx 5fef88c2fe7d8234a16023cdd9c762c667878d50 |
View Raw JSON Data
{
"trx_id": "5fef88c2fe7d8234a16023cdd9c762c667878d50",
"block": 20261981,
"trx_in_block": 9,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-28T09:47:09",
"op": [
"comment",
{
"parent_author": "crypticorn",
"parent_permlink": "iota-report-decoding-the-tangle-part-1-how-iota-works-in-a-nutshell",
"author": "cheetah",
"permlink": "cheetah-re-crypticorniota-report-decoding-the-tangle-part-1-how-iota-works-in-a-nutshell",
"title": "",
"body": "Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in:\nhttps://medium.com/konfid-io-blockchain-reports/iota-report-decoding-the-tangle-part-1-a7705c458583",
"json_metadata": ""
}
]
}2018/02/28 09:47:03
2018/02/28 09:47:03
| voter | cheetah |
| author | crypticorn |
| permlink | iota-report-decoding-the-tangle-part-1-how-iota-works-in-a-nutshell |
| weight | 8 (0.08%) |
| Transaction Info | Block #20261979/Trx 711e2329778c0d85d393df3c1445a09e81ffaebe |
View Raw JSON Data
{
"trx_id": "711e2329778c0d85d393df3c1445a09e81ffaebe",
"block": 20261979,
"trx_in_block": 58,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-28T09:47:03",
"op": [
"vote",
{
"voter": "cheetah",
"author": "crypticorn",
"permlink": "iota-report-decoding-the-tangle-part-1-how-iota-works-in-a-nutshell",
"weight": 8
}
]
}crypticornpublished a new post: iota-report-decoding-the-tangle-part-1-how-iota-works-in-a-nutshell2018/02/28 09:46:00
crypticornpublished a new post: iota-report-decoding-the-tangle-part-1-how-iota-works-in-a-nutshell
2018/02/28 09:46:00
| parent author | |
| parent permlink | iota |
| author | crypticorn |
| permlink | iota-report-decoding-the-tangle-part-1-how-iota-works-in-a-nutshell |
| title | IOTA Report: Decoding the Tangle — Part 1 How IOTA works in a nutshell |
| body |  The original report can be found on Medium: https://medium.com/konfid-io-blockchain-reports/iota-report-decoding-the-tangle-part-1-a7705c458583 IOTA Report: Overview Introduction This four-part series aims to provide an in-depth analysis of IOTA. The project is looking to disrupt traditional blockchain systems by utilizing a new type of distributed ledger technology to enable a scalable, trustless, and feeless network suitable for microtransactions in the Internet-of-Things (IoT) industry. We aim to provide an objective overview of the project and how it works (Part 1), the history of the IOTA token, the Foundation and the token distribution (Part 2), the tech and the protocol (Part 3), and its possibilities & limitations (Part 4). Why IOTA? The value of the tradable token of the IOTA protocol, MIOTA, peaked at $5.66 on December 19th, accounting for a market cap of over $15 billion, and trading volumes north of $1 billion per day. Although there are several open questions about the practical usability and several controversies in the past, the IOTA project established itself as one of the biggest names in the crypto space as of today. Abstract: Part 1 In the first part we briefly discuss the basics of IOTA, how it works, its vision, which technology it utilizes, how it differs from blockchain protocols like Bitcoin, why it uses ternary logic, and the process of publishing transactions onto the ledger. Part 1: How IOTA works in a nutshell What is IOTA ? IOTA is a new transaction settlement and data transfer layer for the Internet of Things (IoT). It’s based on a newly designed distributed ledger, the Tangle, which aims to overcome the inefficiencies of current Blockchain protocols by introducing a new way of reaching consensus in a decentralized peer-to-peer system. IOTAs Vision The project promises to deliver a scalable, decentralized, trustless, partition tolerant network that allows for feeless micropayment transactions. By doing so, internet-connected devices can make transactions with each other without any kind of human intervention. IOTA is experimenting with a blockless architecture and novel verification method to achieve consensus. To execute on its vision, IOTA must overcome hurdles such as becoming fully decentralized, establishing trust in its novel cryptography, and creating a network that can viably be supported by small IoT devices with limited resources. Brief Summary of the Technology How IOTA differs from Blockchains In comparison to blockchains, which employ a system where two distinct parties (transaction issuers & miners) are needed to generate and verify transactions on a distributed ledger, the Tangle introduces a more homogeneous approach. The IOTA network consists of nodes that do both, as they “issue and validate transactions” simultaneously (IOTA Whitepaper, p.2). In order to add a transaction to the Tangle, nodes have to approve two previous transactions. This leads to a data structure called directed acyclic graph (DAG) (as seen in Figure 1), which notably differs from the linear data structure of a blockchain. IOTA is using a DAG as a distributed ledger because it is trying to move away from the restrictions of traditional blockchain architectures, which have seen a notable increase in transaction fees due to scaling limitations of having each node process every transaction that is broadcasted to the network.  In Figure 1 (time since genesis on the horizontal axis), the green transaction directly or indirectly references all red ones including the genesis transaction at the far left. Similarly, the green transaction itself is referenced directly or indirectly by all blue ones on the right. The Tangle As described in the Whitepaper, the Tangle is a data structure which uses “a directed acyclic graph (DAG) for storing transactions” (WP p.1). A transaction is also known a site. A site may be added to the Tangle by referencing and verifying two previous sites. As sites are added, the Tangle grows but always references the genesis site created by the Foundation at the beginning of 2016 which contains the original transaction from a single address to all crowdfunding participants. Unfortunately it is not practical to go back in time and look at the genesis transaction, as the IOTA Foundation shortens the history of the network on a regular basis, which will be discussed in more depth in the following parts. Approving Transactions The IOTA protocol demands no explicit fees to submit a transaction to the network. However, in practice IoT devices must verify two previous transactions and solve a minuscule PoW problem. Both these processes require computational resources, and therefore represent a cost. Publishing Transactions to the Ledger Submitting a transaction to the tangle is conducted in the following manner:  Steps involved in publishing transactions 1. Signing A node first signs its transaction with its private key. 2. Tip selection The node randomly chooses two unapproved transactions (‘tips’) according to a specific algorithm. A tip is a newly created transaction that is waiting for approval by other transactions. The Whitepaper states that the creators “do not impose any rules for choosing which transactions a node will approve” (WP, p.3). However, it suggests using the Markov Chain Monte Carlo (MCMC) tip selection algorithm, an algorithm used to select tips randomly based on the size of their cumulative transaction weights. The MCMC is used by most clients to create some reference rules for transactions on how to choose which previous transactions they should validate. 3. Validation After selecting the tips, the node has to check “if the two transactions are not conflicting” (WP, p.3) and select new tips if they are. In addition, it has to verify that those two transactions performed appropriate Proof-of-Work on their part. If one of the previous transactions verified an invalid transaction, then that transaction will not be verified. 4. Proof-of-Work (PoW) In order to issue a valid transaction, the Whitepaper states that “the node must solve a cryptography puzzle similar to those in the Bitcoin blockchain” (WP, p.3). Unlike Bitcoin’s PoW, IOTA nodes do not compete for block rewards and the difficulty remains unchanged as the needed computation simply acts as a spam protection. 5. Publishing Once steps 1-4 are completed by the node, the transaction is published to the Tangle. These significant differences in the approach of how transactions are published on the ledger were designed with the intention of overcoming some of the drawbacks of traditional blockchain protocols like Bitcoin which include high hardware requirements of full nodes and its corresponding scalability issues for the network. Ternary Hardware The IOTA protocol is using a rather unconventional approach, as the protocol is based on ternary logic. “Ternary logic is more efficient than binary logic”, claims IOTA founder David Sønstebø in an interview beginning of 2018. He argues that ternary computation is important for enabling the creation of what he calls the “mbit market” consisting of small micro controllers or sensors that are deployed in the open field and are expected to run for 15 to 20 years straight. Making devices just fractionally more energy efficient using ternary is hence seen by Sønstebø as significant in terms of resource savings over time. At the moment, only a fraction of nodes on the Tangle use ternary hardware, because wide adoption has not yet occurred on a global scale. We will briefly discuss the impact of using ternary hardware in todays world in the last part of this series.  Summary IOTA is a distributed ledger for the internet of things (IoT). IOTA employs the Tangle which is a distributed ledger protocol based on ‘Directed Acyclic Graphs’ (DAGs). The Tangle aims at providing a scalable, decentralized, feeless, trustless, partition tolerant network. The Tangle tries to compensate the drawbacks of PoW/PoS systems associated with many blockchains. Issuing transactions demand no explicit fee. A transaction is also called a site. A verification of two previous sites validates a transaction. Ternary logic is used for efficiency reasons, but will only be successful if ternary hardware can overcome the lack of adoption and replace the binary hardware that is currently in use. Whats Next To get a better insight whether this different approach of employing a DAG based distributed ledger can compete with its competitors for the adoption in the IoT industry and if the project brought any revolutionary change into the cryptoeconomy, we have to evaluate the history of the project and its founders, what essential role JINN tokens played in the formation of IOTA and how the tokens are distributed. After that we will dive deep into the promises of IOTA’s technology, its current practical limitations, the future roadmap and what our opinion on the success of the IOTA protocol will be. All these topics will be revealed in the next articles of this series.  Editor’s Note At Konfid.io we composed a detailed report about the IOTA project for which we provide a condensed but informative four-part summary on Medium, aimed to give an overview about IOTA for entrepreneurs and companies that are planning to build on the protocol, as well as for developers and crypto-enthusiasts that are interested in the Tangle. What is Konfid.io? Konfid.io is a technology consultancy and venture studio based in Berlin that focuses on Blockchain technology to build decentralized applications in private as well as public distributed systems. We constantly research the practical usability of distributed ledger projects and like to share our findings with the wider community. |
| json metadata | {"tags":["iota","nano","tangle","blockchain","dag"],"image":["https://steemitimages.com/DQmQDaLfrGxPchQX1h9Jryq8nwwm3Ut9nbNVV7X6TrMXaSo/1_2io-7NVw5utVpMT2kHrJDA.png","https://steemitimages.com/DQmT8UnG6zThE79sqstvVVC2D7PQiYit3B1CMfFiVhjkqgR/0_A4xHVzhZ0ysTdScX.png","https://steemitimages.com/DQmeB7tV3f8fED7EckH1c8SJ1Lmx6DDznsf1LYmxLQy6tCb/1_lW14XqNroiXOucf44_zwuQ.png","https://steemitimages.com/DQmZmbBRhNeT34mM4g4EbAL6YumnQqjGrUfoadJx2AeafoW/1_NKk6-QwOcgvp82jwTMsg0Q.jpeg","https://steemitimages.com/DQmad89k6meYSjNvkAYtvTwA9awteVaJNri4DqP9NYVJf9o/1_GSegJvEIn_UytvqUzPV2PA.png"],"links":["https://medium.com/konfid-io-blockchain-reports/iota-report-decoding-the-tangle-part-1-a7705c458583"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #20261958/Trx 3eda0b0a65339eb042dafabbb08ee0581658b5e2 |
View Raw JSON Data
{
"trx_id": "3eda0b0a65339eb042dafabbb08ee0581658b5e2",
"block": 20261958,
"trx_in_block": 30,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-28T09:46:00",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "iota",
"author": "crypticorn",
"permlink": "iota-report-decoding-the-tangle-part-1-how-iota-works-in-a-nutshell",
"title": "IOTA Report: Decoding the Tangle — Part 1 How IOTA works in a nutshell",
"body": "\n\nThe original report can be found on Medium: https://medium.com/konfid-io-blockchain-reports/iota-report-decoding-the-tangle-part-1-a7705c458583\n\nIOTA Report: Overview\n\nIntroduction\nThis four-part series aims to provide an in-depth analysis of IOTA. The project is looking to disrupt traditional blockchain systems by utilizing a new type of distributed ledger technology to enable a scalable, trustless, and feeless network suitable for microtransactions in the Internet-of-Things (IoT) industry. We aim to provide an objective overview of the project and how it works (Part 1), the history of the IOTA token, the Foundation and the token distribution (Part 2), the tech and the protocol (Part 3), and its possibilities & limitations (Part 4).\n\nWhy IOTA?\nThe value of the tradable token of the IOTA protocol, MIOTA, peaked at $5.66 on December 19th, accounting for a market cap of over $15 billion, and trading volumes north of $1 billion per day. Although there are several open questions about the practical usability and several controversies in the past, the IOTA project established itself as one of the biggest names in the crypto space as of today.\n\nAbstract: Part 1\nIn the first part we briefly discuss the basics of IOTA, how it works, its vision, which technology it utilizes, how it differs from blockchain protocols like Bitcoin, why it uses ternary logic, and the process of publishing transactions onto the ledger.\n\nPart 1: How IOTA works in a nutshell\nWhat is IOTA ?\nIOTA is a new transaction settlement and data transfer layer for the Internet of Things (IoT). It’s based on a newly designed distributed ledger, the Tangle, which aims to overcome the inefficiencies of current Blockchain protocols by introducing a new way of reaching consensus in a decentralized peer-to-peer system.\n\nIOTAs Vision\nThe project promises to deliver a scalable, decentralized, trustless, partition tolerant network that allows for feeless micropayment transactions. By doing so, internet-connected devices can make transactions with each other without any kind of human intervention. IOTA is experimenting with a blockless architecture and novel verification method to achieve consensus.\n\nTo execute on its vision, IOTA must overcome hurdles such as becoming fully decentralized, establishing trust in its novel cryptography, and creating a network that can viably be supported by small IoT devices with limited resources.\n\nBrief Summary of the Technology\nHow IOTA differs from Blockchains\nIn comparison to blockchains, which employ a system where two distinct parties (transaction issuers & miners) are needed to generate and verify transactions on a distributed ledger, the Tangle introduces a more homogeneous approach. The IOTA network consists of nodes that do both, as they “issue and validate transactions” simultaneously (IOTA Whitepaper, p.2).\n\nIn order to add a transaction to the Tangle, nodes have to approve two previous transactions. This leads to a data structure called directed acyclic graph (DAG) (as seen in Figure 1), which notably differs from the linear data structure of a blockchain. IOTA is using a DAG as a distributed ledger because it is trying to move away from the restrictions of traditional blockchain architectures, which have seen a notable increase in transaction fees due to scaling limitations of having each node process every transaction that is broadcasted to the network.\n\n\n\n\nIn Figure 1 (time since genesis on the horizontal axis), the green transaction directly or indirectly references all red ones including the genesis transaction at the far left. Similarly, the green transaction itself is referenced directly or indirectly by all blue ones on the right.\n\n\nThe Tangle\nAs described in the Whitepaper, the Tangle is a data structure which uses “a directed acyclic graph (DAG) for storing transactions” (WP p.1). A transaction is also known a site. A site may be added to the Tangle by referencing and verifying two previous sites. As sites are added, the Tangle grows but always references the genesis site created by the Foundation at the beginning of 2016 which contains the original transaction from a single address to all crowdfunding participants. Unfortunately it is not practical to go back in time and look at the genesis transaction, as the IOTA Foundation shortens the history of the network on a regular basis, which will be discussed in more depth in the following parts.\n\nApproving Transactions\nThe IOTA protocol demands no explicit fees to submit a transaction to the network. However, in practice IoT devices must verify two previous transactions and solve a minuscule PoW problem. Both these processes require computational resources, and therefore represent a cost.\n\nPublishing Transactions to the Ledger\nSubmitting a transaction to the tangle is conducted in the following manner:\n\n\nSteps involved in publishing transactions\n\n1. Signing\n\nA node first signs its transaction with its private key.\n\n2. Tip selection\n\nThe node randomly chooses two unapproved transactions (‘tips’) according to a specific algorithm. A tip is a newly created transaction that is waiting for approval by other transactions. The Whitepaper states that the creators “do not impose any rules for choosing which transactions a node will approve” (WP, p.3). However, it suggests using the Markov Chain Monte Carlo (MCMC) tip selection algorithm, an algorithm used to select tips randomly based on the size of their cumulative transaction weights. The MCMC is used by most clients to create some reference rules for transactions on how to choose which previous transactions they should validate.\n\n3. Validation\n\nAfter selecting the tips, the node has to check “if the two transactions are not conflicting” (WP, p.3) and select new tips if they are. In addition, it has to verify that those two transactions performed appropriate Proof-of-Work on their part. If one of the previous transactions verified an invalid transaction, then that transaction will not be verified.\n\n4. Proof-of-Work (PoW)\n\nIn order to issue a valid transaction, the Whitepaper states that “the node must solve a cryptography puzzle similar to those in the Bitcoin blockchain” (WP, p.3). Unlike Bitcoin’s PoW, IOTA nodes do not compete for block rewards and the difficulty remains unchanged as the needed computation simply acts as a spam protection.\n\n5. Publishing\n\nOnce steps 1-4 are completed by the node, the transaction is published to the Tangle.\n\nThese significant differences in the approach of how transactions are published on the ledger were designed with the intention of overcoming some of the drawbacks of traditional blockchain protocols like Bitcoin which include high hardware requirements of full nodes and its corresponding scalability issues for the network.\n\nTernary Hardware\nThe IOTA protocol is using a rather unconventional approach, as the protocol is based on ternary logic. “Ternary logic is more efficient than binary logic”, claims IOTA founder David Sønstebø in an interview beginning of 2018. He argues that ternary computation is important for enabling the creation of what he calls the “mbit market” consisting of small micro controllers or sensors that are deployed in the open field and are expected to run for 15 to 20 years straight. Making devices just fractionally more energy efficient using ternary is hence seen by Sønstebø as significant in terms of resource savings over time.\n\nAt the moment, only a fraction of nodes on the Tangle use ternary hardware, because wide adoption has not yet occurred on a global scale. We will briefly discuss the impact of using ternary hardware in todays world in the last part of this series.\n\n\n\n\nSummary\nIOTA is a distributed ledger for the internet of things (IoT).\nIOTA employs the Tangle which is a distributed ledger protocol based on ‘Directed Acyclic Graphs’ (DAGs).\nThe Tangle aims at providing a scalable, decentralized, feeless, trustless, partition tolerant network.\nThe Tangle tries to compensate the drawbacks of PoW/PoS systems associated with many blockchains.\nIssuing transactions demand no explicit fee.\nA transaction is also called a site. A verification of two previous sites validates a transaction.\nTernary logic is used for efficiency reasons, but will only be successful if ternary hardware can overcome the lack of adoption and replace the binary hardware that is currently in use.\nWhats Next\nTo get a better insight whether this different approach of employing a DAG based distributed ledger can compete with its competitors for the adoption in the IoT industry and if the project brought any revolutionary change into the cryptoeconomy, we have to evaluate the history of the project and its founders, what essential role JINN tokens played in the formation of IOTA and how the tokens are distributed. After that we will dive deep into the promises of IOTA’s technology, its current practical limitations, the future roadmap and what our opinion on the success of the IOTA protocol will be. All these topics will be revealed in the next articles of this series.\n\n\n\n\nEditor’s Note\nAt Konfid.io we composed a detailed report about the IOTA project for which we provide a condensed but informative four-part summary on Medium, aimed to give an overview about IOTA for entrepreneurs and companies that are planning to build on the protocol, as well as for developers and crypto-enthusiasts that are interested in the Tangle.\n\nWhat is Konfid.io?\nKonfid.io is a technology consultancy and venture studio based in Berlin that focuses on Blockchain technology to build decentralized applications in private as well as public distributed systems. We constantly research the practical usability of distributed ledger projects and like to share our findings with the wider community.",
"json_metadata": "{\"tags\":[\"iota\",\"nano\",\"tangle\",\"blockchain\",\"dag\"],\"image\":[\"https://steemitimages.com/DQmQDaLfrGxPchQX1h9Jryq8nwwm3Ut9nbNVV7X6TrMXaSo/1_2io-7NVw5utVpMT2kHrJDA.png\",\"https://steemitimages.com/DQmT8UnG6zThE79sqstvVVC2D7PQiYit3B1CMfFiVhjkqgR/0_A4xHVzhZ0ysTdScX.png\",\"https://steemitimages.com/DQmeB7tV3f8fED7EckH1c8SJ1Lmx6DDznsf1LYmxLQy6tCb/1_lW14XqNroiXOucf44_zwuQ.png\",\"https://steemitimages.com/DQmZmbBRhNeT34mM4g4EbAL6YumnQqjGrUfoadJx2AeafoW/1_NKk6-QwOcgvp82jwTMsg0Q.jpeg\",\"https://steemitimages.com/DQmad89k6meYSjNvkAYtvTwA9awteVaJNri4DqP9NYVJf9o/1_GSegJvEIn_UytvqUzPV2PA.png\"],\"links\":[\"https://medium.com/konfid-io-blockchain-reports/iota-report-decoding-the-tangle-part-1-a7705c458583\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}steemdelegated 18.232 SP to @crypticorn2018/01/09 06:36:33
steemdelegated 18.232 SP to @crypticorn
2018/01/09 06:36:33
| delegator | steem |
| delegatee | crypticorn |
| vesting shares | 29689.756374 VESTS |
| Transaction Info | Block #18819531/Trx faaf78433ed3fb08be469dae4a4d1b3624068e31 |
View Raw JSON Data
{
"trx_id": "faaf78433ed3fb08be469dae4a4d1b3624068e31",
"block": 18819531,
"trx_in_block": 22,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-09T06:36:33",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "crypticorn",
"vesting_shares": "29689.756374 VESTS"
}
]
}shakem3dupvoted (100.00%) @crypticorn / lisk2017/12/12 09:33:15
shakem3dupvoted (100.00%) @crypticorn / lisk
2017/12/12 09:33:15
| voter | shakem3d |
| author | crypticorn |
| permlink | lisk |
| weight | 10000 (100.00%) |
| Transaction Info | Block #18017257/Trx ea92993ebcb16b1a3227976f415bf861c2f0761d |
View Raw JSON Data
{
"trx_id": "ea92993ebcb16b1a3227976f415bf861c2f0761d",
"block": 18017257,
"trx_in_block": 9,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-12T09:33:15",
"op": [
"vote",
{
"voter": "shakem3d",
"author": "crypticorn",
"permlink": "lisk",
"weight": 10000
}
]
}2017/08/23 14:10:45
2017/08/23 14:10:45
| parent author | dantheman |
| parent permlink | dpos-consensus-algorithm-this-missing-white-paper |
| author | crypticorn |
| permlink | re-dantheman-dpos-consensus-algorithm-this-missing-white-paper-20170823t141043776z |
| title | |
| body | Hi Dan, you mention TaPoS in the end, but do not make any mention of the cons to it. Why would you not simply build your protocol to enforce a TaPoS standard to begin with? |
| json metadata | {"tags":["dpos"],"app":"steemit/0.1"} |
| Transaction Info | Block #14827991/Trx 718b0ab4556258749648c56386a9174c71d36631 |
View Raw JSON Data
{
"trx_id": "718b0ab4556258749648c56386a9174c71d36631",
"block": 14827991,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-08-23T14:10:45",
"op": [
"comment",
{
"parent_author": "dantheman",
"parent_permlink": "dpos-consensus-algorithm-this-missing-white-paper",
"author": "crypticorn",
"permlink": "re-dantheman-dpos-consensus-algorithm-this-missing-white-paper-20170823t141043776z",
"title": "",
"body": "Hi Dan, you mention TaPoS in the end, but do not make any mention of the cons to it. Why would you not simply build your protocol to enforce a TaPoS standard to begin with?",
"json_metadata": "{\"tags\":[\"dpos\"],\"app\":\"steemit/0.1\"}"
}
]
}crypticornfollowed @dan2017/08/11 08:34:57
crypticornfollowed @dan
2017/08/11 08:34:57
| required auths | [] |
| required posting auths | ["crypticorn"] |
| id | follow |
| json | ["follow",{"follower":"crypticorn","following":"dan","what":["blog"]}] |
| Transaction Info | Block #14476578/Trx 063a5ea552f8e646cf001b652b3cfd9dae49b204 |
View Raw JSON Data
{
"trx_id": "063a5ea552f8e646cf001b652b3cfd9dae49b204",
"block": 14476578,
"trx_in_block": 15,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-08-11T08:34:57",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"crypticorn"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"crypticorn\",\"following\":\"dan\",\"what\":[\"blog\"]}]"
}
]
}crypticornfollowed @dantheman2017/08/07 09:56:24
crypticornfollowed @dantheman
2017/08/07 09:56:24
| required auths | [] |
| required posting auths | ["crypticorn"] |
| id | follow |
| json | ["follow",{"follower":"crypticorn","following":"dantheman","what":["blog"]}] |
| Transaction Info | Block #14363138/Trx a38d4a1e8b7a23b944a9c3c20009baa371dffd8c |
View Raw JSON Data
{
"trx_id": "a38d4a1e8b7a23b944a9c3c20009baa371dffd8c",
"block": 14363138,
"trx_in_block": 10,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-08-07T09:56:24",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"crypticorn"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"crypticorn\",\"following\":\"dantheman\",\"what\":[\"blog\"]}]"
}
]
}steemdelegated 18.386 SP to @crypticorn2017/08/04 05:19:36
steemdelegated 18.386 SP to @crypticorn
2017/08/04 05:19:36
| delegator | steem |
| delegatee | crypticorn |
| vesting shares | 29940.567082 VESTS |
| Transaction Info | Block #14271468/Trx 35de497c45d69226ed2fb83f2abf9b65c1058faf |
View Raw JSON Data
{
"trx_id": "35de497c45d69226ed2fb83f2abf9b65c1058faf",
"block": 14271468,
"trx_in_block": 13,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-08-04T05:19:36",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "crypticorn",
"vesting_shares": "29940.567082 VESTS"
}
]
}crypticornfollowed @crypto-investor2017/07/30 17:58:06
crypticornfollowed @crypto-investor
2017/07/30 17:58:06
| required auths | [] |
| required posting auths | ["crypticorn"] |
| id | follow |
| json | ["follow",{"follower":"crypticorn","following":"crypto-investor","what":["blog"]}] |
| Transaction Info | Block #14142751/Trx 4d84e807dadc65217ea2a882bdd59c3549f423aa |
View Raw JSON Data
{
"trx_id": "4d84e807dadc65217ea2a882bdd59c3549f423aa",
"block": 14142751,
"trx_in_block": 9,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-07-30T17:58:06",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"crypticorn"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"crypticorn\",\"following\":\"crypto-investor\",\"what\":[\"blog\"]}]"
}
]
}crypticornupvoted (100.00%) @ivanli / programmer-explains-bitcoin-cash-practical-tips2017/07/30 17:57:21
crypticornupvoted (100.00%) @ivanli / programmer-explains-bitcoin-cash-practical-tips
2017/07/30 17:57:21
| voter | crypticorn |
| author | ivanli |
| permlink | programmer-explains-bitcoin-cash-practical-tips |
| weight | 10000 (100.00%) |
| Transaction Info | Block #14142736/Trx c43f4a6a7ca6a95e16410cd6d1902306f8e12ec4 |
View Raw JSON Data
{
"trx_id": "c43f4a6a7ca6a95e16410cd6d1902306f8e12ec4",
"block": 14142736,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-07-30T17:57:21",
"op": [
"vote",
{
"voter": "crypticorn",
"author": "ivanli",
"permlink": "programmer-explains-bitcoin-cash-practical-tips",
"weight": 10000
}
]
}crypticornfollowed @iang2017/07/29 15:14:45
crypticornfollowed @iang
2017/07/29 15:14:45
| required auths | [] |
| required posting auths | ["crypticorn"] |
| id | follow |
| json | ["follow",{"follower":"crypticorn","following":"iang","what":["blog"]}] |
| Transaction Info | Block #14110692/Trx 0f56042f6087ca8820001e5e1703ad66321bd855 |
View Raw JSON Data
{
"trx_id": "0f56042f6087ca8820001e5e1703ad66321bd855",
"block": 14110692,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-07-29T15:14:45",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"crypticorn"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"crypticorn\",\"following\":\"iang\",\"what\":[\"blog\"]}]"
}
]
}2017/07/29 15:14:33
2017/07/29 15:14:33
| parent author | iang |
| parent permlink | eos-an-introduction |
| author | crypticorn |
| permlink | re-iang-eos-an-introduction-20170729t151434054z |
| title | |
| body | Great article! Thanks for helping me understand what EOS does and might do in the future. |
| json metadata | {"tags":["eos"],"app":"steemit/0.1"} |
| Transaction Info | Block #14110688/Trx 29f1ac95df85413bfd160c8ef93065eb9d3e0df2 |
View Raw JSON Data
{
"trx_id": "29f1ac95df85413bfd160c8ef93065eb9d3e0df2",
"block": 14110688,
"trx_in_block": 20,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-07-29T15:14:33",
"op": [
"comment",
{
"parent_author": "iang",
"parent_permlink": "eos-an-introduction",
"author": "crypticorn",
"permlink": "re-iang-eos-an-introduction-20170729t151434054z",
"title": "",
"body": "Great article! Thanks for helping me understand what EOS does and might do in the future.",
"json_metadata": "{\"tags\":[\"eos\"],\"app\":\"steemit/0.1\"}"
}
]
}crypticornupvoted (100.00%) @iang / eos-an-introduction2017/07/29 15:13:21
crypticornupvoted (100.00%) @iang / eos-an-introduction
2017/07/29 15:13:21
| voter | crypticorn |
| author | iang |
| permlink | eos-an-introduction |
| weight | 10000 (100.00%) |
| Transaction Info | Block #14110664/Trx 96945313a2b73d0f3552c7c998fd509a20417bfa |
View Raw JSON Data
{
"trx_id": "96945313a2b73d0f3552c7c998fd509a20417bfa",
"block": 14110664,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-07-29T15:13:21",
"op": [
"vote",
{
"voter": "crypticorn",
"author": "iang",
"permlink": "eos-an-introduction",
"weight": 10000
}
]
}crypticornfollowed @eosio2017/07/28 13:47:15
crypticornfollowed @eosio
2017/07/28 13:47:15
| required auths | [] |
| required posting auths | ["crypticorn"] |
| id | follow |
| json | ["follow",{"follower":"crypticorn","following":"eosio","what":["blog"]}] |
| Transaction Info | Block #14080161/Trx 00de76afb0058659264cf01d96364add656d004d |
View Raw JSON Data
{
"trx_id": "00de76afb0058659264cf01d96364add656d004d",
"block": 14080161,
"trx_in_block": 16,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-07-28T13:47:15",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"crypticorn"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"crypticorn\",\"following\":\"eosio\",\"what\":[\"blog\"]}]"
}
]
}crypticornpublished a new post: do-your-bit-run-a-bitcoin-node-poster-d-d2017/07/26 19:00:48
crypticornpublished a new post: do-your-bit-run-a-bitcoin-node-poster-d-d
2017/07/26 19:00:48
| parent author | |
| parent permlink | bitcoin |
| author | crypticorn |
| permlink | do-your-bit-run-a-bitcoin-node-poster-d-d |
| title | DO YOUR BIT - RUN A BITCOIN NODE Poster :D :D |
| body |  |
| json metadata | {"tags":["bitcoin","segwit","bip91","bip148","bip141"],"image":["https://steemitimages.com/DQmTJmmoa7UeqVvVAjFbcEspXwsKPieCzijkWwjTgN4apj6/Screen%20Shot%202017-07-26%20at%2020.56.24.png"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #14028843/Trx e7499d1aac8b89a31cef1e4592242760abe3d212 |
View Raw JSON Data
{
"trx_id": "e7499d1aac8b89a31cef1e4592242760abe3d212",
"block": 14028843,
"trx_in_block": 31,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-07-26T19:00:48",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "bitcoin",
"author": "crypticorn",
"permlink": "do-your-bit-run-a-bitcoin-node-poster-d-d",
"title": "DO YOUR BIT - RUN A BITCOIN NODE Poster :D :D",
"body": "",
"json_metadata": "{\"tags\":[\"bitcoin\",\"segwit\",\"bip91\",\"bip148\",\"bip141\"],\"image\":[\"https://steemitimages.com/DQmTJmmoa7UeqVvVAjFbcEspXwsKPieCzijkWwjTgN4apj6/Screen%20Shot%202017-07-26%20at%2020.56.24.png\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}2017/07/25 16:11:33
2017/07/25 16:11:33
| voter | crypticorn |
| author | ivanli |
| permlink | are-you-too-old-to-learn-programming-at-30-practical-tips-programmer-explains |
| weight | 10000 (100.00%) |
| Transaction Info | Block #13996670/Trx d8984aa318d96a0c2c93b4d368821c2e6e395a99 |
View Raw JSON Data
{
"trx_id": "d8984aa318d96a0c2c93b4d368821c2e6e395a99",
"block": 13996670,
"trx_in_block": 24,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-07-25T16:11:33",
"op": [
"vote",
{
"voter": "crypticorn",
"author": "ivanli",
"permlink": "are-you-too-old-to-learn-programming-at-30-practical-tips-programmer-explains",
"weight": 10000
}
]
}crypticornupvoted (100.00%) @ivanli / how-i-got-into-programming-story-about-runescape2017/07/25 16:11:30
crypticornupvoted (100.00%) @ivanli / how-i-got-into-programming-story-about-runescape
2017/07/25 16:11:30
| voter | crypticorn |
| author | ivanli |
| permlink | how-i-got-into-programming-story-about-runescape |
| weight | 10000 (100.00%) |
| Transaction Info | Block #13996669/Trx 9f85547471f13014f54088ea0296220d51250b73 |
View Raw JSON Data
{
"trx_id": "9f85547471f13014f54088ea0296220d51250b73",
"block": 13996669,
"trx_in_block": 34,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-07-25T16:11:30",
"op": [
"vote",
{
"voter": "crypticorn",
"author": "ivanli",
"permlink": "how-i-got-into-programming-story-about-runescape",
"weight": 10000
}
]
}2017/07/25 16:11:27
2017/07/25 16:11:27
| voter | crypticorn |
| author | ivanli |
| permlink | ethereum-and-crypto-bloodbath-price-and-technology-disconnect-programmer-explains |
| weight | 10000 (100.00%) |
| Transaction Info | Block #13996668/Trx 23e3e18085a4c3ffb105c1e22bc9f7c2c1a70a68 |
View Raw JSON Data
{
"trx_id": "23e3e18085a4c3ffb105c1e22bc9f7c2c1a70a68",
"block": 13996668,
"trx_in_block": 20,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-07-25T16:11:27",
"op": [
"vote",
{
"voter": "crypticorn",
"author": "ivanli",
"permlink": "ethereum-and-crypto-bloodbath-price-and-technology-disconnect-programmer-explains",
"weight": 10000
}
]
}2017/07/25 16:11:21
2017/07/25 16:11:21
| voter | crypticorn |
| author | ivanli |
| permlink | github-can-help-you-as-crypto-investor-chaincoin-weakness-programmer-expalins |
| weight | 10000 (100.00%) |
| Transaction Info | Block #13996666/Trx 2c337677f0fc39038f1d11c5c3c647f1a8cee86c |
View Raw JSON Data
{
"trx_id": "2c337677f0fc39038f1d11c5c3c647f1a8cee86c",
"block": 13996666,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-07-25T16:11:21",
"op": [
"vote",
{
"voter": "crypticorn",
"author": "ivanli",
"permlink": "github-can-help-you-as-crypto-investor-chaincoin-weakness-programmer-expalins",
"weight": 10000
}
]
}crypticornupvoted (100.00%) @ivanli / ethereum-usd30m-hack-bad-code-explained-programmer-explains2017/07/25 16:11:12
crypticornupvoted (100.00%) @ivanli / ethereum-usd30m-hack-bad-code-explained-programmer-explains
2017/07/25 16:11:12
| voter | crypticorn |
| author | ivanli |
| permlink | ethereum-usd30m-hack-bad-code-explained-programmer-explains |
| weight | 10000 (100.00%) |
| Transaction Info | Block #13996663/Trx 563628491c237fe9b28140b03dc6698f7008c707 |
View Raw JSON Data
{
"trx_id": "563628491c237fe9b28140b03dc6698f7008c707",
"block": 13996663,
"trx_in_block": 14,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-07-25T16:11:12",
"op": [
"vote",
{
"voter": "crypticorn",
"author": "ivanli",
"permlink": "ethereum-usd30m-hack-bad-code-explained-programmer-explains",
"weight": 10000
}
]
}torontorobupvoted (100.00%) @crypticorn / lisk2017/07/13 04:00:15
torontorobupvoted (100.00%) @crypticorn / lisk
2017/07/13 04:00:15
| voter | torontorob |
| author | crypticorn |
| permlink | lisk |
| weight | 10000 (100.00%) |
| Transaction Info | Block #13636802/Trx e2b29fdeca81b406f839d12023f74bbf714ad742 |
View Raw JSON Data
{
"trx_id": "e2b29fdeca81b406f839d12023f74bbf714ad742",
"block": 13636802,
"trx_in_block": 28,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-07-13T04:00:15",
"op": [
"vote",
{
"voter": "torontorob",
"author": "crypticorn",
"permlink": "lisk",
"weight": 10000
}
]
}crypticornreceived 0.001 SP curation reward for @ivanli / threats-to-ethereum-programmer-explains2017/06/23 17:49:12
crypticornreceived 0.001 SP curation reward for @ivanli / threats-to-ethereum-programmer-explains
2017/06/23 17:49:12
| curator | crypticorn |
| reward | 2.069648 VESTS |
| comment author | ivanli |
| comment permlink | threats-to-ethereum-programmer-explains |
| Transaction Info | Block #13078486/Virtual Operation #40 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 13078486,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 40,
"timestamp": "2017-06-23T17:49:12",
"op": [
"curation_reward",
{
"curator": "crypticorn",
"reward": "2.069648 VESTS",
"comment_author": "ivanli",
"comment_permlink": "threats-to-ethereum-programmer-explains"
}
]
}crypticornreceived 0.010 SBD, 0.008 SP author reward for @crypticorn / ethereum-memes-are-killer-d-d2017/06/23 16:47:12
crypticornreceived 0.010 SBD, 0.008 SP author reward for @crypticorn / ethereum-memes-are-killer-d-d
2017/06/23 16:47:12
| author | crypticorn |
| permlink | ethereum-memes-are-killer-d-d |
| sbd payout | 0.010 SBD |
| steem payout | 0.000 STEEM |
| vesting payout | 12.417918 VESTS |
| Transaction Info | Block #13077246/Virtual Operation #4 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 13077246,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 4,
"timestamp": "2017-06-23T16:47:12",
"op": [
"author_reward",
{
"author": "crypticorn",
"permlink": "ethereum-memes-are-killer-d-d",
"sbd_payout": "0.010 SBD",
"steem_payout": "0.000 STEEM",
"vesting_payout": "12.417918 VESTS"
}
]
}crypticornreceived 0.001 SP curation reward for @pawos / re-crypticorn-re-pawos-re-crypticorn-re-pawos-re-crypticorn-this-guy-keeps-messaging-me-claiming-to-be-satoshi-nakamoto-d-20170616t101408426z2017/06/23 10:14:09
crypticornreceived 0.001 SP curation reward for @pawos / re-crypticorn-re-pawos-re-crypticorn-re-pawos-re-crypticorn-this-guy-keeps-messaging-me-claiming-to-be-satoshi-nakamoto-d-20170616t101408426z
2017/06/23 10:14:09
| curator | crypticorn |
| reward | 2.069683 VESTS |
| comment author | pawos |
| comment permlink | re-crypticorn-re-pawos-re-crypticorn-re-pawos-re-crypticorn-this-guy-keeps-messaging-me-claiming-to-be-satoshi-nakamoto-d-20170616t101408426z |
| Transaction Info | Block #13069389/Virtual Operation #3 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 13069389,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 3,
"timestamp": "2017-06-23T10:14:09",
"op": [
"curation_reward",
{
"curator": "crypticorn",
"reward": "2.069683 VESTS",
"comment_author": "pawos",
"comment_permlink": "re-crypticorn-re-pawos-re-crypticorn-re-pawos-re-crypticorn-this-guy-keeps-messaging-me-claiming-to-be-satoshi-nakamoto-d-20170616t101408426z"
}
]
}crypticornreceived 0.001 SP curation reward for @pawos / re-crypticorn-re-pawos-re-crypticorn-this-guy-keeps-messaging-me-claiming-to-be-satoshi-nakamoto-d-20170616t100609504z2017/06/23 10:06:09
crypticornreceived 0.001 SP curation reward for @pawos / re-crypticorn-re-pawos-re-crypticorn-this-guy-keeps-messaging-me-claiming-to-be-satoshi-nakamoto-d-20170616t100609504z
2017/06/23 10:06:09
| curator | crypticorn |
| reward | 2.069684 VESTS |
| comment author | pawos |
| comment permlink | re-crypticorn-re-pawos-re-crypticorn-this-guy-keeps-messaging-me-claiming-to-be-satoshi-nakamoto-d-20170616t100609504z |
| Transaction Info | Block #13069229/Virtual Operation #3 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 13069229,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 3,
"timestamp": "2017-06-23T10:06:09",
"op": [
"curation_reward",
{
"curator": "crypticorn",
"reward": "2.069684 VESTS",
"comment_author": "pawos",
"comment_permlink": "re-crypticorn-re-pawos-re-crypticorn-this-guy-keeps-messaging-me-claiming-to-be-satoshi-nakamoto-d-20170616t100609504z"
}
]
}crypticornreceived 0.003 SP curation reward for @pawos / re-crypticorn-this-guy-keeps-messaging-me-claiming-to-be-satoshi-nakamoto-d-20170616t100013695z2017/06/23 10:00:33
crypticornreceived 0.003 SP curation reward for @pawos / re-crypticorn-this-guy-keeps-messaging-me-claiming-to-be-satoshi-nakamoto-d-20170616t100013695z
2017/06/23 10:00:33
| curator | crypticorn |
| reward | 4.139368 VESTS |
| comment author | pawos |
| comment permlink | re-crypticorn-this-guy-keeps-messaging-me-claiming-to-be-satoshi-nakamoto-d-20170616t100013695z |
| Transaction Info | Block #13069117/Virtual Operation #4 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 13069117,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 4,
"timestamp": "2017-06-23T10:00:33",
"op": [
"curation_reward",
{
"curator": "crypticorn",
"reward": "4.139368 VESTS",
"comment_author": "pawos",
"comment_permlink": "re-crypticorn-this-guy-keeps-messaging-me-claiming-to-be-satoshi-nakamoto-d-20170616t100013695z"
}
]
}crypticornreceived 0.010 SBD, 0.006 SP author reward for @crypticorn / this-guy-keeps-messaging-me-claiming-to-be-satoshi-nakamoto-d2017/06/23 09:59:24
crypticornreceived 0.010 SBD, 0.006 SP author reward for @crypticorn / this-guy-keeps-messaging-me-claiming-to-be-satoshi-nakamoto-d
2017/06/23 09:59:24
| author | crypticorn |
| permlink | this-guy-keeps-messaging-me-claiming-to-be-satoshi-nakamoto-d |
| sbd payout | 0.010 SBD |
| steem payout | 0.000 STEEM |
| vesting payout | 10.348422 VESTS |
| Transaction Info | Block #13069094/Virtual Operation #2 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 13069094,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 2,
"timestamp": "2017-06-23T09:59:24",
"op": [
"author_reward",
{
"author": "crypticorn",
"permlink": "this-guy-keeps-messaging-me-claiming-to-be-satoshi-nakamoto-d",
"sbd_payout": "0.010 SBD",
"steem_payout": "0.000 STEEM",
"vesting_payout": "10.348422 VESTS"
}
]
}crypticornreceived 0.044 SBD, 0.025 SP author reward for @crypticorn / lisk2017/06/21 15:15:06
crypticornreceived 0.044 SBD, 0.025 SP author reward for @crypticorn / lisk
2017/06/21 15:15:06
| author | crypticorn |
| permlink | lisk |
| sbd payout | 0.044 SBD |
| steem payout | 0.000 STEEM |
| vesting payout | 41.397647 VESTS |
| Transaction Info | Block #13017827/Virtual Operation #7 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 13017827,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 7,
"timestamp": "2017-06-21T15:15:06",
"op": [
"author_reward",
{
"author": "crypticorn",
"permlink": "lisk",
"sbd_payout": "0.044 SBD",
"steem_payout": "0.000 STEEM",
"vesting_payout": "41.397647 VESTS"
}
]
}crypticornupvoted (100.00%) @ivanli / threats-to-ethereum-programmer-explains2017/06/16 19:19:42
crypticornupvoted (100.00%) @ivanli / threats-to-ethereum-programmer-explains
2017/06/16 19:19:42
| voter | crypticorn |
| author | ivanli |
| permlink | threats-to-ethereum-programmer-explains |
| weight | 10000 (100.00%) |
| Transaction Info | Block #12879063/Trx 32579d2d296eff16a1150340ea9f21f024bd3bd9 |
View Raw JSON Data
{
"trx_id": "32579d2d296eff16a1150340ea9f21f024bd3bd9",
"block": 12879063,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-06-16T19:19:42",
"op": [
"vote",
{
"voter": "crypticorn",
"author": "ivanli",
"permlink": "threats-to-ethereum-programmer-explains",
"weight": 10000
}
]
}joshdomskyupvoted (100.00%) @crypticorn / ethereum-memes-are-killer-d-d2017/06/16 18:04:30
joshdomskyupvoted (100.00%) @crypticorn / ethereum-memes-are-killer-d-d
2017/06/16 18:04:30
| voter | joshdomsky |
| author | crypticorn |
| permlink | ethereum-memes-are-killer-d-d |
| weight | 10000 (100.00%) |
| Transaction Info | Block #12877559/Trx 9dbba1bb2892a3f811e88cf9e6eff0b26788f9a7 |
View Raw JSON Data
{
"trx_id": "9dbba1bb2892a3f811e88cf9e6eff0b26788f9a7",
"block": 12877559,
"trx_in_block": 14,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-06-16T18:04:30",
"op": [
"vote",
{
"voter": "joshdomsky",
"author": "crypticorn",
"permlink": "ethereum-memes-are-killer-d-d",
"weight": 10000
}
]
}crypticornfollowed @hilmar2017/06/16 17:30:57
crypticornfollowed @hilmar
2017/06/16 17:30:57
| required auths | [] |
| required posting auths | ["crypticorn"] |
| id | follow |
| json | ["follow",{"follower":"crypticorn","following":"hilmar","what":["blog"]}] |
| Transaction Info | Block #12876889/Trx ddffb450f701d4f7f41d16c7fa46e96425bd1382 |
View Raw JSON Data
{
"trx_id": "ddffb450f701d4f7f41d16c7fa46e96425bd1382",
"block": 12876889,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-06-16T17:30:57",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"crypticorn"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"crypticorn\",\"following\":\"hilmar\",\"what\":[\"blog\"]}]"
}
]
}crypticorncustom json: follow2017/06/16 16:48:48
crypticorncustom json: follow
2017/06/16 16:48:48
| required auths | [] |
| required posting auths | ["crypticorn"] |
| id | follow |
| json | ["reblog",{"account":"crypticorn","author":"roelandp","permlink":"steemfest-updates-hotel-s-booking-site-now-available"}] |
| Transaction Info | Block #12876046/Trx 190f9f873375887b2407dfac5532c3090a5b3338 |
View Raw JSON Data
{
"trx_id": "190f9f873375887b2407dfac5532c3090a5b3338",
"block": 12876046,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-06-16T16:48:48",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"crypticorn"
],
"id": "follow",
"json": "[\"reblog\",{\"account\":\"crypticorn\",\"author\":\"roelandp\",\"permlink\":\"steemfest-updates-hotel-s-booking-site-now-available\"}]"
}
]
}crypticornupvoted (100.00%) @roelandp / steemfest-updates-hotel-s-booking-site-now-available2017/06/16 16:48:33
crypticornupvoted (100.00%) @roelandp / steemfest-updates-hotel-s-booking-site-now-available
2017/06/16 16:48:33
| voter | crypticorn |
| author | roelandp |
| permlink | steemfest-updates-hotel-s-booking-site-now-available |
| weight | 10000 (100.00%) |
| Transaction Info | Block #12876041/Trx 4b0cb7dd17c0e6f14524ca0b874f53c45edde6c9 |
View Raw JSON Data
{
"trx_id": "4b0cb7dd17c0e6f14524ca0b874f53c45edde6c9",
"block": 12876041,
"trx_in_block": 20,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-06-16T16:48:33",
"op": [
"vote",
{
"voter": "crypticorn",
"author": "roelandp",
"permlink": "steemfest-updates-hotel-s-booking-site-now-available",
"weight": 10000
}
]
}gbonikzupvoted (100.00%) @crypticorn / ethereum-memes-are-killer-d-d2017/06/16 16:47:18
gbonikzupvoted (100.00%) @crypticorn / ethereum-memes-are-killer-d-d
2017/06/16 16:47:18
| voter | gbonikz |
| author | crypticorn |
| permlink | ethereum-memes-are-killer-d-d |
| weight | 10000 (100.00%) |
| Transaction Info | Block #12876016/Trx 07fb3ab437d2d93a0c3945c8c0e95b16cc99e639 |
View Raw JSON Data
{
"trx_id": "07fb3ab437d2d93a0c3945c8c0e95b16cc99e639",
"block": 12876016,
"trx_in_block": 11,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-06-16T16:47:18",
"op": [
"vote",
{
"voter": "gbonikz",
"author": "crypticorn",
"permlink": "ethereum-memes-are-killer-d-d",
"weight": 10000
}
]
}crypticornupvoted (100.00%) @crypticorn / ethereum-memes-are-killer-d-d2017/06/16 16:47:12
crypticornupvoted (100.00%) @crypticorn / ethereum-memes-are-killer-d-d
2017/06/16 16:47:12
| voter | crypticorn |
| author | crypticorn |
| permlink | ethereum-memes-are-killer-d-d |
| weight | 10000 (100.00%) |
| Transaction Info | Block #12876014/Trx a78d392f64628b0c66318c01a5987a4f6f628c3a |
View Raw JSON Data
{
"trx_id": "a78d392f64628b0c66318c01a5987a4f6f628c3a",
"block": 12876014,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-06-16T16:47:12",
"op": [
"vote",
{
"voter": "crypticorn",
"author": "crypticorn",
"permlink": "ethereum-memes-are-killer-d-d",
"weight": 10000
}
]
}crypticornpublished a new post: ethereum-memes-are-killer-d-d2017/06/16 16:47:12
crypticornpublished a new post: ethereum-memes-are-killer-d-d
2017/06/16 16:47:12
| parent author | |
| parent permlink | ethereum |
| author | crypticorn |
| permlink | ethereum-memes-are-killer-d-d |
| title | Ethereum Memes are killer! :D :D |
| body |  |
| json metadata | {"tags":["ethereum","ether","cryptotrading","buterin","bitcoin"],"image":["https://steemitimages.com/DQmayMuPfV9GFgouLtcsAmb5Gz619fFkMifKDyZZPqBeqfy/IMG_0529.JPG"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #12876014/Trx a78d392f64628b0c66318c01a5987a4f6f628c3a |
View Raw JSON Data
{
"trx_id": "a78d392f64628b0c66318c01a5987a4f6f628c3a",
"block": 12876014,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-06-16T16:47:12",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "ethereum",
"author": "crypticorn",
"permlink": "ethereum-memes-are-killer-d-d",
"title": "Ethereum Memes are killer! :D :D",
"body": "",
"json_metadata": "{\"tags\":[\"ethereum\",\"ether\",\"cryptotrading\",\"buterin\",\"bitcoin\"],\"image\":[\"https://steemitimages.com/DQmayMuPfV9GFgouLtcsAmb5Gz619fFkMifKDyZZPqBeqfy/IMG_0529.JPG\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}gbonikzupvoted (100.00%) @crypticorn / hodl2017/06/16 15:57:30
gbonikzupvoted (100.00%) @crypticorn / hodl
2017/06/16 15:57:30
| voter | gbonikz |
| author | crypticorn |
| permlink | hodl |
| weight | 10000 (100.00%) |
| Transaction Info | Block #12875022/Trx a79d6547af0bd0422bded3347afb49936e90297c |
View Raw JSON Data
{
"trx_id": "a79d6547af0bd0422bded3347afb49936e90297c",
"block": 12875022,
"trx_in_block": 8,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-06-16T15:57:30",
"op": [
"vote",
{
"voter": "gbonikz",
"author": "crypticorn",
"permlink": "hodl",
"weight": 10000
}
]
}crypticornupvoted (100.00%) @crypticorn / hodl2017/06/16 15:24:51
crypticornupvoted (100.00%) @crypticorn / hodl
2017/06/16 15:24:51
| voter | crypticorn |
| author | crypticorn |
| permlink | hodl |
| weight | 10000 (100.00%) |
| Transaction Info | Block #12874369/Trx ea99dd66cf2a9cfb1f07534df5bff2e51abb9803 |
View Raw JSON Data
{
"trx_id": "ea99dd66cf2a9cfb1f07534df5bff2e51abb9803",
"block": 12874369,
"trx_in_block": 11,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-06-16T15:24:51",
"op": [
"vote",
{
"voter": "crypticorn",
"author": "crypticorn",
"permlink": "hodl",
"weight": 10000
}
]
}crypticornpublished a new post: hodl2017/06/16 15:24:51
crypticornpublished a new post: hodl
2017/06/16 15:24:51
| parent author | |
| parent permlink | ethereum |
| author | crypticorn |
| permlink | hodl |
| title | HODL! |
| body | https://www.facebook.com/groups/Ethereum/permalink/1219051948220850/?comment_id=1219091591550219¬if_t=group_comment_mention¬if_id=1497621369745298 |
| json metadata | {"tags":["ethereum","hodl","ether","cryptocurrency","bitcoin"],"links":["https://www.facebook.com/groups/Ethereum/permalink/1219051948220850/?comment_id=1219091591550219&notif_t=group_comment_mention&notif_id=1497621369745298"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #12874369/Trx ea99dd66cf2a9cfb1f07534df5bff2e51abb9803 |
View Raw JSON Data
{
"trx_id": "ea99dd66cf2a9cfb1f07534df5bff2e51abb9803",
"block": 12874369,
"trx_in_block": 11,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-06-16T15:24:51",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "ethereum",
"author": "crypticorn",
"permlink": "hodl",
"title": "HODL!",
"body": "https://www.facebook.com/groups/Ethereum/permalink/1219051948220850/?comment_id=1219091591550219¬if_t=group_comment_mention¬if_id=1497621369745298",
"json_metadata": "{\"tags\":[\"ethereum\",\"hodl\",\"ether\",\"cryptocurrency\",\"bitcoin\"],\"links\":[\"https://www.facebook.com/groups/Ethereum/permalink/1219051948220850/?comment_id=1219091591550219&notif_t=group_comment_mention&notif_id=1497621369745298\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}crypticornupdated their account properties2017/06/16 12:00:12
crypticornupdated their account properties
2017/06/16 12:00:12
| account | crypticorn |
| memo key | STM58Bq9UbEV3WWtgau8A4rSimcQgFVZ8fBYtbrcQJ9mymS6Pg62k |
| json metadata | {"profile":{"profile_image":"https://pbs.twimg.com/profile_images/875667011656970240/jebzlX8R_400x400.jpg"}} |
| Transaction Info | Block #12870281/Trx 925620326e8784b5e6e6bdc9ee3aec6c030b03f7 |
View Raw JSON Data
{
"trx_id": "925620326e8784b5e6e6bdc9ee3aec6c030b03f7",
"block": 12870281,
"trx_in_block": 15,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-06-16T12:00:12",
"op": [
"account_update",
{
"account": "crypticorn",
"memo_key": "STM58Bq9UbEV3WWtgau8A4rSimcQgFVZ8fBYtbrcQJ9mymS6Pg62k",
"json_metadata": "{\"profile\":{\"profile_image\":\"https://pbs.twimg.com/profile_images/875667011656970240/jebzlX8R_400x400.jpg\"}}"
}
]
}Manabar
Voting Power100.00%
Downvote Power100.00%
Resource Credits100.00%
Reputation Progress0.00%
{
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779058668
},
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779058668
},
"rc_account": {
"account": "crypticorn",
"rc_manabar": {
"current_mana": "10164408779",
"last_update_time": 1779058668
},
"max_rc_creation_adjustment": {
"amount": "2020748973",
"precision": 6,
"nai": "@@000000037"
},
"max_rc": "10164408779"
}
}Account Metadata
| POSTING JSON METADATA | |
| profile | {"profile_image":"https://pbs.twimg.com/profile_images/875667011656970240/jebzlX8R_400x400.jpg"} |
| JSON METADATA | |
| profile | {"profile_image":"https://pbs.twimg.com/profile_images/875667011656970240/jebzlX8R_400x400.jpg"} |
{
"posting_json_metadata": {
"profile": {
"profile_image": "https://pbs.twimg.com/profile_images/875667011656970240/jebzlX8R_400x400.jpg"
}
},
"json_metadata": {
"profile": {
"profile_image": "https://pbs.twimg.com/profile_images/875667011656970240/jebzlX8R_400x400.jpg"
}
}
}Auth Keys
Owner
Single Signature
Public Keys
STM5fe6ukdkNRBcxpgWSr1PfFJ3acBdpTLqS2SCyom7yp64HaRnvj1/1
Active
Single Signature
Public Keys
STM8B5fgRpBMSdpoc9cgYHVE4iJzjFd2diQQs5QoLGJHeanqXsjBm1/1
Posting
Single Signature
Public Keys
STM4xazHgMV8g5h5XX1bqTkW1iV2apMyEbivPKaN7TUmyZjn1JTFn1/1
Memo
STM58Bq9UbEV3WWtgau8A4rSimcQgFVZ8fBYtbrcQJ9mymS6Pg62k
{
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5fe6ukdkNRBcxpgWSr1PfFJ3acBdpTLqS2SCyom7yp64HaRnvj",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM8B5fgRpBMSdpoc9cgYHVE4iJzjFd2diQQs5QoLGJHeanqXsjBm",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM4xazHgMV8g5h5XX1bqTkW1iV2apMyEbivPKaN7TUmyZjn1JTFn",
1
]
]
},
"memo": "STM58Bq9UbEV3WWtgau8A4rSimcQgFVZ8fBYtbrcQJ9mymS6Pg62k"
}Witness Votes
0 / 30
No active witness votes.
[]