VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS0.00%
Net Worth
0.037USD
STEEM
0.000STEEM
SBD
0.000SBD
Effective Power
5.007SP
├── Own SP
0.632SP
└── Incoming DelegationsDeleg
+4.375SP
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.632SP | SP |
| Delegated Out | 0.000SP | SP |
| Delegation In | 4.375SP | SP |
| Effective Power | 5.007SP | SP |
| Reward SP (pending) | 0.000SP | SP |
| SBD | ||
| sbd_balance | 0.000SBD | SBD |
| sbd_conversions | 0.000SBD | SBD |
| sbd_market_balance | 0.000SBD | SBD |
| savings_sbd_balance | 0.000SBD | SBD |
| reward_sbd_balance | 0.000SBD | SBD |
{
"balance": "0.000 STEEM",
"savings_balance": "0.000 STEEM",
"reward_steem_balance": "0.000 STEEM",
"vesting_shares": "1028.351697 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "7115.308109 VESTS",
"sbd_balance": "0.000 SBD",
"savings_sbd_balance": "0.000 SBD",
"reward_sbd_balance": "0.000 SBD",
"conversions": []
}Account Info
| name | ravishankarhass |
| id | 416140 |
| rank | 847,247 |
| reputation | 76790500 |
| created | 2017-10-20T19:38:24 |
| recovery_account | steem |
| proxy | None |
| post_count | 1 |
| comment_count | 0 |
| lifetime_vote_count | 0 |
| witnesses_voted_for | 0 |
| last_post | 2017-11-08T22:48:42 |
| last_root_post | 2017-11-08T22:48:42 |
| last_vote_time | 2017-11-08T23:36:36 |
| 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 | 1028.351697 VESTS |
| delegated_vesting_shares | 0.000000 VESTS |
| received_vesting_shares | 7115.308109 VESTS |
| reward_vesting_balance | 0.000000 VESTS |
| vesting_balance | 0.000 STEEM |
| vesting_withdraw_rate | 0.000000 VESTS |
| next_vesting_withdrawal | 1969-12-31T23:59:59 |
| withdrawn | 0 |
| to_withdraw | 0 |
| withdraw_routes | 0 |
| savings_withdraw_requests | 0 |
| last_account_recovery | 1970-01-01T00:00:00 |
| reset_account | null |
| last_owner_update | 1970-01-01T00:00:00 |
| last_account_update | 1970-01-01T00:00:00 |
| mined | No |
| sbd_seconds | 0 |
| sbd_last_interest_payment | 1970-01-01T00:00:00 |
| savings_sbd_last_interest_payment | 1970-01-01T00:00:00 |
{
"active": {
"account_auths": [],
"key_auths": [
[
"STM5vq6RnnnLtnKoTHTCHxEByVjmKLGUZLh6HEfJctW7rjGiRDcHu",
1
]
],
"weight_threshold": 1
},
"balance": "0.000 STEEM",
"can_vote": true,
"comment_count": 0,
"created": "2017-10-20T19:38:24",
"curation_rewards": 0,
"delegated_vesting_shares": "0.000000 VESTS",
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779082344
},
"guest_bloggers": [],
"id": 416140,
"json_metadata": "",
"last_account_recovery": "1970-01-01T00:00:00",
"last_account_update": "1970-01-01T00:00:00",
"last_owner_update": "1970-01-01T00:00:00",
"last_post": "2017-11-08T22:48:42",
"last_root_post": "2017-11-08T22:48:42",
"last_vote_time": "2017-11-08T23:36:36",
"lifetime_vote_count": 0,
"market_history": [],
"memo_key": "STM6pKm1DdwfriAdeLeDZWSn2DziYQBvwAZAkDeUnvXjEC4CXNFmV",
"mined": false,
"name": "ravishankarhass",
"next_vesting_withdrawal": "1969-12-31T23:59:59",
"other_history": [],
"owner": {
"account_auths": [],
"key_auths": [
[
"STM6xbDwDjXHWh5K1znabhVng6Dz1h1ZDRQJgdb9ccTCjQkstA1sq",
1
]
],
"weight_threshold": 1
},
"pending_claimed_accounts": 0,
"post_bandwidth": 0,
"post_count": 1,
"post_history": [],
"posting": {
"account_auths": [],
"key_auths": [
[
"STM6rBFmkPwXQUMJ2gwjTUf2DMmMpFQdKTSqcaPwHsthhtdMVQpsg",
1
]
],
"weight_threshold": 1
},
"posting_json_metadata": "",
"posting_rewards": 0,
"proxied_vsf_votes": [
0,
0,
0,
0
],
"proxy": "",
"received_vesting_shares": "7115.308109 VESTS",
"recovery_account": "steem",
"reputation": 76790500,
"reset_account": "null",
"reward_sbd_balance": "0.000 SBD",
"reward_steem_balance": "0.000 STEEM",
"reward_vesting_balance": "0.000000 VESTS",
"reward_vesting_steem": "0.000 STEEM",
"savings_balance": "0.000 STEEM",
"savings_sbd_balance": "0.000 SBD",
"savings_sbd_last_interest_payment": "1970-01-01T00:00:00",
"savings_sbd_seconds": "0",
"savings_sbd_seconds_last_update": "1970-01-01T00:00:00",
"savings_withdraw_requests": 0,
"sbd_balance": "0.000 SBD",
"sbd_last_interest_payment": "1970-01-01T00:00:00",
"sbd_seconds": "0",
"sbd_seconds_last_update": "1970-01-01T00:00:00",
"tags_usage": [],
"to_withdraw": 0,
"transfer_history": [],
"vesting_balance": "0.000 STEEM",
"vesting_shares": "1028.351697 VESTS",
"vesting_withdraw_rate": "0.000000 VESTS",
"vote_history": [],
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779082344
},
"voting_power": 0,
"withdraw_routes": 0,
"withdrawn": 0,
"witness_votes": [],
"witnesses_voted_for": 0,
"rank": 847247
}Withdraw Routes
| Incoming | Outgoing |
|---|---|
Empty | Empty |
{
"incoming": [],
"outgoing": []
}From Date
To Date
steemdelegated 4.375 SP to @ravishankarhass2026/05/18 05:32:24
steemdelegated 4.375 SP to @ravishankarhass
2026/05/18 05:32:24
| delegatee | ravishankarhass |
| delegator | steem |
| vesting shares | 7115.308109 VESTS |
| Transaction Info | Block #106149763/Trx d07784126d507b52a15666fb9a9ff104c0cf0363 |
View Raw JSON Data
{
"block": 106149763,
"op": [
"delegate_vesting_shares",
{
"delegatee": "ravishankarhass",
"delegator": "steem",
"vesting_shares": "7115.308109 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2026-05-18T05:32:24",
"trx_id": "d07784126d507b52a15666fb9a9ff104c0cf0363",
"trx_in_block": 1,
"virtual_op": 0
}steemdelegated 2.707 SP to @ravishankarhass2026/05/13 01:20:24
steemdelegated 2.707 SP to @ravishankarhass
2026/05/13 01:20:24
| delegatee | ravishankarhass |
| delegator | steem |
| vesting shares | 4403.097704 VESTS |
| Transaction Info | Block #106001453/Trx d6d4be1028e8fc3f6a41042cbe818082fed2f7a5 |
View Raw JSON Data
{
"block": 106001453,
"op": [
"delegate_vesting_shares",
{
"delegatee": "ravishankarhass",
"delegator": "steem",
"vesting_shares": "4403.097704 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2026-05-13T01:20:24",
"trx_id": "d6d4be1028e8fc3f6a41042cbe818082fed2f7a5",
"trx_in_block": 4,
"virtual_op": 0
}steemdelegated 4.383 SP to @ravishankarhass2026/04/26 04:45:15
steemdelegated 4.383 SP to @ravishankarhass
2026/04/26 04:45:15
| delegatee | ravishankarhass |
| delegator | steem |
| vesting shares | 7127.823865 VESTS |
| Transaction Info | Block #105517270/Trx 1b688a1c69969427c6eb300e2941c1aaccca5603 |
View Raw JSON Data
{
"block": 105517270,
"op": [
"delegate_vesting_shares",
{
"delegatee": "ravishankarhass",
"delegator": "steem",
"vesting_shares": "7127.823865 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2026-04-26T04:45:15",
"trx_id": "1b688a1c69969427c6eb300e2941c1aaccca5603",
"trx_in_block": 4,
"virtual_op": 0
}steemdelegated 2.733 SP to @ravishankarhass2026/01/23 22:01:51
steemdelegated 2.733 SP to @ravishankarhass
2026/01/23 22:01:51
| delegatee | ravishankarhass |
| delegator | steem |
| vesting shares | 4444.644523 VESTS |
| Transaction Info | Block #102868859/Trx b32a13379143e887186022c705d584204921f7ae |
View Raw JSON Data
{
"block": 102868859,
"op": [
"delegate_vesting_shares",
{
"delegatee": "ravishankarhass",
"delegator": "steem",
"vesting_shares": "4444.644523 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2026-01-23T22:01:51",
"trx_id": "b32a13379143e887186022c705d584204921f7ae",
"trx_in_block": 0,
"virtual_op": 0
}steemdelegated 2.834 SP to @ravishankarhass2024/12/17 17:12:27
steemdelegated 2.834 SP to @ravishankarhass
2024/12/17 17:12:27
| delegatee | ravishankarhass |
| delegator | steem |
| vesting shares | 4608.863720 VESTS |
| Transaction Info | Block #91315084/Trx 19dda9edc31360f2ccb6308182e2ca39c570410f |
View Raw JSON Data
{
"block": 91315084,
"op": [
"delegate_vesting_shares",
{
"delegatee": "ravishankarhass",
"delegator": "steem",
"vesting_shares": "4608.863720 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2024-12-17T17:12:27",
"trx_id": "19dda9edc31360f2ccb6308182e2ca39c570410f",
"trx_in_block": 0,
"virtual_op": 0
}steemdelegated 2.938 SP to @ravishankarhass2023/11/14 08:54:06
steemdelegated 2.938 SP to @ravishankarhass
2023/11/14 08:54:06
| delegatee | ravishankarhass |
| delegator | steem |
| vesting shares | 4777.997252 VESTS |
| Transaction Info | Block #79869242/Trx 236abd6f441b554e26604a50f92dd45239cb6218 |
View Raw JSON Data
{
"block": 79869242,
"op": [
"delegate_vesting_shares",
{
"delegatee": "ravishankarhass",
"delegator": "steem",
"vesting_shares": "4777.997252 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2023-11-14T08:54:06",
"trx_id": "236abd6f441b554e26604a50f92dd45239cb6218",
"trx_in_block": 4,
"virtual_op": 0
}steemdelegated 4.744 SP to @ravishankarhass2023/09/22 09:30:36
steemdelegated 4.744 SP to @ravishankarhass
2023/09/22 09:30:36
| delegatee | ravishankarhass |
| delegator | steem |
| vesting shares | 7714.906038 VESTS |
| Transaction Info | Block #78361810/Trx 36e04006864b96e5e1d429cf447977414eddada8 |
View Raw JSON Data
{
"block": 78361810,
"op": [
"delegate_vesting_shares",
{
"delegatee": "ravishankarhass",
"delegator": "steem",
"vesting_shares": "7714.906038 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2023-09-22T09:30:36",
"trx_id": "36e04006864b96e5e1d429cf447977414eddada8",
"trx_in_block": 1,
"virtual_op": 0
}steemdelegated 4.880 SP to @ravishankarhass2022/11/03 17:04:48
steemdelegated 4.880 SP to @ravishankarhass
2022/11/03 17:04:48
| delegatee | ravishankarhass |
| delegator | steem |
| vesting shares | 7936.957476 VESTS |
| Transaction Info | Block #69119681/Trx 737d51ab478d337d3ba57f3844b3ffebb3a9fb97 |
View Raw JSON Data
{
"block": 69119681,
"op": [
"delegate_vesting_shares",
{
"delegatee": "ravishankarhass",
"delegator": "steem",
"vesting_shares": "7936.957476 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2022-11-03T17:04:48",
"trx_id": "737d51ab478d337d3ba57f3844b3ffebb3a9fb97",
"trx_in_block": 2,
"virtual_op": 0
}steemdelegated 5.016 SP to @ravishankarhass2022/01/17 22:21:09
steemdelegated 5.016 SP to @ravishankarhass
2022/01/17 22:21:09
| delegatee | ravishankarhass |
| delegator | steem |
| vesting shares | 8157.065077 VESTS |
| Transaction Info | Block #60823018/Trx 6fd5ae4eee9324d5be3b548b69a3ec9cbf085eb7 |
View Raw JSON Data
{
"block": 60823018,
"op": [
"delegate_vesting_shares",
{
"delegatee": "ravishankarhass",
"delegator": "steem",
"vesting_shares": "8157.065077 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2022-01-17T22:21:09",
"trx_id": "6fd5ae4eee9324d5be3b548b69a3ec9cbf085eb7",
"trx_in_block": 1,
"virtual_op": 0
}steemdelegated 5.129 SP to @ravishankarhass2021/06/14 05:34:00
steemdelegated 5.129 SP to @ravishankarhass
2021/06/14 05:34:00
| delegatee | ravishankarhass |
| delegator | steem |
| vesting shares | 8341.259365 VESTS |
| Transaction Info | Block #54613385/Trx e03b47337c13150dee18196f56d3865c81f525ab |
View Raw JSON Data
{
"block": 54613385,
"op": [
"delegate_vesting_shares",
{
"delegatee": "ravishankarhass",
"delegator": "steem",
"vesting_shares": "8341.259365 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2021-06-14T05:34:00",
"trx_id": "e03b47337c13150dee18196f56d3865c81f525ab",
"trx_in_block": 2,
"virtual_op": 0
}steemdelegated 5.244 SP to @ravishankarhass2020/12/11 15:46:54
steemdelegated 5.244 SP to @ravishankarhass
2020/12/11 15:46:54
| delegatee | ravishankarhass |
| delegator | steem |
| vesting shares | 8528.681339 VESTS |
| Transaction Info | Block #49360670/Trx 2ed9c43f95f04225b273963d43af493f94385cc7 |
View Raw JSON Data
{
"block": 49360670,
"op": [
"delegate_vesting_shares",
{
"delegatee": "ravishankarhass",
"delegator": "steem",
"vesting_shares": "8528.681339 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-12-11T15:46:54",
"trx_id": "2ed9c43f95f04225b273963d43af493f94385cc7",
"trx_in_block": 2,
"virtual_op": 0
}steemdelegated 1.176 SP to @ravishankarhass2020/12/06 09:22:54
steemdelegated 1.176 SP to @ravishankarhass
2020/12/06 09:22:54
| delegatee | ravishankarhass |
| delegator | steem |
| vesting shares | 1912.543513 VESTS |
| Transaction Info | Block #49212199/Trx ed16251552a03a5a61da5763860d1338dbdb9398 |
View Raw JSON Data
{
"block": 49212199,
"op": [
"delegate_vesting_shares",
{
"delegatee": "ravishankarhass",
"delegator": "steem",
"vesting_shares": "1912.543513 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-12-06T09:22:54",
"trx_id": "ed16251552a03a5a61da5763860d1338dbdb9398",
"trx_in_block": 6,
"virtual_op": 0
}steemdelegated 5.248 SP to @ravishankarhass2020/12/05 19:24:51
steemdelegated 5.248 SP to @ravishankarhass
2020/12/05 19:24:51
| delegatee | ravishankarhass |
| delegator | steem |
| vesting shares | 8534.889193 VESTS |
| Transaction Info | Block #49195756/Trx 0f88ed4ff8de09b6e7bfb15132149a20cc9fe24c |
View Raw JSON Data
{
"block": 49195756,
"op": [
"delegate_vesting_shares",
{
"delegatee": "ravishankarhass",
"delegator": "steem",
"vesting_shares": "8534.889193 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-12-05T19:24:51",
"trx_id": "0f88ed4ff8de09b6e7bfb15132149a20cc9fe24c",
"trx_in_block": 9,
"virtual_op": 0
}steemdelegated 1.181 SP to @ravishankarhass2020/11/03 01:16:03
steemdelegated 1.181 SP to @ravishankarhass
2020/11/03 01:16:03
| delegatee | ravishankarhass |
| delegator | steem |
| vesting shares | 1920.017158 VESTS |
| Transaction Info | Block #48269141/Trx 4d785e016a680484128768146d3f9f515ee6f092 |
View Raw JSON Data
{
"block": 48269141,
"op": [
"delegate_vesting_shares",
{
"delegatee": "ravishankarhass",
"delegator": "steem",
"vesting_shares": "1920.017158 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-11-03T01:16:03",
"trx_id": "4d785e016a680484128768146d3f9f515ee6f092",
"trx_in_block": 3,
"virtual_op": 0
}steemdelegated 5.373 SP to @ravishankarhass2020/05/09 10:25:15
steemdelegated 5.373 SP to @ravishankarhass
2020/05/09 10:25:15
| delegatee | ravishankarhass |
| delegator | steem |
| vesting shares | 8737.694552 VESTS |
| Transaction Info | Block #43222517/Trx e9095882b3094851d397154fff9faec2db696ce7 |
View Raw JSON Data
{
"block": 43222517,
"op": [
"delegate_vesting_shares",
{
"delegatee": "ravishankarhass",
"delegator": "steem",
"vesting_shares": "8737.694552 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-05-09T10:25:15",
"trx_id": "e9095882b3094851d397154fff9faec2db696ce7",
"trx_in_block": 3,
"virtual_op": 0
}steemdelegated 1.201 SP to @ravishankarhass2020/05/08 14:43:21
steemdelegated 1.201 SP to @ravishankarhass
2020/05/08 14:43:21
| delegatee | ravishankarhass |
| delegator | steem |
| vesting shares | 1953.311140 VESTS |
| Transaction Info | Block #43199441/Trx 742962daf1fe3e67c25fe579a30129010b0c62b1 |
View Raw JSON Data
{
"block": 43199441,
"op": [
"delegate_vesting_shares",
{
"delegatee": "ravishankarhass",
"delegator": "steem",
"vesting_shares": "1953.311140 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-05-08T14:43:21",
"trx_id": "742962daf1fe3e67c25fe579a30129010b0c62b1",
"trx_in_block": 17,
"virtual_op": 0
}steemdelegated 5.380 SP to @ravishankarhass2020/04/16 02:51:21
steemdelegated 5.380 SP to @ravishankarhass
2020/04/16 02:51:21
| delegatee | ravishankarhass |
| delegator | steem |
| vesting shares | 8750.582000 VESTS |
| Transaction Info | Block #42568642/Trx 8b2afbbdd033422d92531e6347436c951127206b |
View Raw JSON Data
{
"block": 42568642,
"op": [
"delegate_vesting_shares",
{
"delegatee": "ravishankarhass",
"delegator": "steem",
"vesting_shares": "8750.582000 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-04-16T02:51:21",
"trx_id": "8b2afbbdd033422d92531e6347436c951127206b",
"trx_in_block": 18,
"virtual_op": 0
}2019/10/20 20:43:51
2019/10/20 20:43:51
| author | steemitboard |
| body | Congratulations @ravishankarhass! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@ravishankarhass/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/@ravishankarhass) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=ravishankarhass)_</sub> **Do not miss the last post from @steemitboard:** <table><tr><td><a href="https://steemit.com/steemfest/@steemitboard/steemfest-commemorative-badge-refactored"><img src="https://steemitimages.com/64x128/https://files.steempeak.com/file/steempeak/arcange/YqQV5Tbj-image.png"></a></td><td><a href="https://steemit.com/steemfest/@steemitboard/steemfest-commemorative-badge-refactored">SteemFest⁴ commemorative badge refactored</a></td></tr></table> ###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| parent author | ravishankarhass |
| parent permlink | comparison-of-various-dlt-a-k-a-block-chains |
| permlink | steemitboard-notify-ravishankarhass-20191020t204350000z |
| title | |
| Transaction Info | Block #37458703/Trx d4a47eaf03125fbd8d4166571c9f12460f4938cc |
View Raw JSON Data
{
"block": 37458703,
"op": [
"comment",
{
"author": "steemitboard",
"body": "Congratulations @ravishankarhass! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@ravishankarhass/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/@ravishankarhass) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=ravishankarhass)_</sub>\n\n\n**Do not miss the last post from @steemitboard:**\n<table><tr><td><a href=\"https://steemit.com/steemfest/@steemitboard/steemfest-commemorative-badge-refactored\"><img src=\"https://steemitimages.com/64x128/https://files.steempeak.com/file/steempeak/arcange/YqQV5Tbj-image.png\"></a></td><td><a href=\"https://steemit.com/steemfest/@steemitboard/steemfest-commemorative-badge-refactored\">SteemFest⁴ commemorative badge refactored</a></td></tr></table>\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}",
"parent_author": "ravishankarhass",
"parent_permlink": "comparison-of-various-dlt-a-k-a-block-chains",
"permlink": "steemitboard-notify-ravishankarhass-20191020t204350000z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2019-10-20T20:43:51",
"trx_id": "d4a47eaf03125fbd8d4166571c9f12460f4938cc",
"trx_in_block": 0,
"virtual_op": 0
}steemdelegated 5.501 SP to @ravishankarhass2019/05/12 19:58:24
steemdelegated 5.501 SP to @ravishankarhass
2019/05/12 19:58:24
| delegatee | ravishankarhass |
| delegator | steem |
| vesting shares | 8946.198813 VESTS |
| Transaction Info | Block #32851569/Trx a600aff6dd5b09b44cd8f560b4a098ef8bfbc634 |
View Raw JSON Data
{
"block": 32851569,
"op": [
"delegate_vesting_shares",
{
"delegatee": "ravishankarhass",
"delegator": "steem",
"vesting_shares": "8946.198813 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2019-05-12T19:58:24",
"trx_id": "a600aff6dd5b09b44cd8f560b4a098ef8bfbc634",
"trx_in_block": 11,
"virtual_op": 0
}2018/10/21 02:34:54
2018/10/21 02:34:54
| author | steemitboard |
| body | Congratulations @ravishankarhass! You have received a personal award! [](http://steemitboard.com/@ravishankarhass) 1 Year on Steemit <sub>_Click on the badge to view your Board of Honor._</sub> **Do not miss the last post from @steemitboard:** <table><tr><td><a href="https://steemit.com/steemitboard/@steemitboard/steemitboard-ranking-update-resteem-and-resteemed-added"><img src="https://steemitimages.com/64x128/https://cdn.steemitimages.com/DQmfRVpHQhLDhnjDtqck8GPv9NPvNKPfMsDaAFDE1D9Er2Z/header_ranking.png"></a></td><td><a href="https://steemit.com/steemitboard/@steemitboard/steemitboard-ranking-update-resteem-and-resteemed-added">SteemitBoard Ranking update - Resteem and Resteemed added</a></td></tr></table> > Support [SteemitBoard's project](https://steemit.com/@steemitboard)! **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| parent author | ravishankarhass |
| parent permlink | comparison-of-various-dlt-a-k-a-block-chains |
| permlink | steemitboard-notify-ravishankarhass-20181021t023455000z |
| title | |
| Transaction Info | Block #26989963/Trx c10b1717864b8b8dca1753f11ffe0e272919dae9 |
View Raw JSON Data
{
"block": 26989963,
"op": [
"comment",
{
"author": "steemitboard",
"body": "Congratulations @ravishankarhass! You have received a personal award!\n\n[](http://steemitboard.com/@ravishankarhass) 1 Year on Steemit\n<sub>_Click on the badge to view your Board of Honor._</sub>\n\n\n**Do not miss the last post from @steemitboard:**\n<table><tr><td><a href=\"https://steemit.com/steemitboard/@steemitboard/steemitboard-ranking-update-resteem-and-resteemed-added\"><img src=\"https://steemitimages.com/64x128/https://cdn.steemitimages.com/DQmfRVpHQhLDhnjDtqck8GPv9NPvNKPfMsDaAFDE1D9Er2Z/header_ranking.png\"></a></td><td><a href=\"https://steemit.com/steemitboard/@steemitboard/steemitboard-ranking-update-resteem-and-resteemed-added\">SteemitBoard Ranking update - Resteem and Resteemed added</a></td></tr></table>\n\n> Support [SteemitBoard's project](https://steemit.com/@steemitboard)! **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}",
"parent_author": "ravishankarhass",
"parent_permlink": "comparison-of-various-dlt-a-k-a-block-chains",
"permlink": "steemitboard-notify-ravishankarhass-20181021t023455000z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2018-10-21T02:34:54",
"trx_id": "c10b1717864b8b8dca1753f11ffe0e272919dae9",
"trx_in_block": 8,
"virtual_op": 0
}steemdelegated 5.623 SP to @ravishankarhass2018/05/16 23:54:24
steemdelegated 5.623 SP to @ravishankarhass
2018/05/16 23:54:24
| delegatee | ravishankarhass |
| delegator | steem |
| vesting shares | 9145.809681 VESTS |
| Transaction Info | Block #22494189/Trx 4b0e3aac64042785d81761e7f63f4a5f96583f48 |
View Raw JSON Data
{
"block": 22494189,
"op": [
"delegate_vesting_shares",
{
"delegatee": "ravishankarhass",
"delegator": "steem",
"vesting_shares": "9145.809681 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2018-05-16T23:54:24",
"trx_id": "4b0e3aac64042785d81761e7f63f4a5f96583f48",
"trx_in_block": 23,
"virtual_op": 0
}steemdelegated 18.159 SP to @ravishankarhass2018/04/21 20:51:09
steemdelegated 18.159 SP to @ravishankarhass
2018/04/21 20:51:09
| delegatee | ravishankarhass |
| delegator | steem |
| vesting shares | 29533.816251 VESTS |
| Transaction Info | Block #21771311/Trx d51f531689ec78674e1ec03b9307a19a7d4a41dc |
View Raw JSON Data
{
"block": 21771311,
"op": [
"delegate_vesting_shares",
{
"delegatee": "ravishankarhass",
"delegator": "steem",
"vesting_shares": "29533.816251 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2018-04-21T20:51:09",
"trx_id": "d51f531689ec78674e1ec03b9307a19a7d4a41dc",
"trx_in_block": 17,
"virtual_op": 0
}steemdelegated 18.285 SP to @ravishankarhass2017/12/12 22:23:21
steemdelegated 18.285 SP to @ravishankarhass
2017/12/12 22:23:21
| delegatee | ravishankarhass |
| delegator | steem |
| vesting shares | 29737.648303 VESTS |
| Transaction Info | Block #18032650/Trx de4decb2058bca2e7f1cdaa4268b02e59ba5b555 |
View Raw JSON Data
{
"block": 18032650,
"op": [
"delegate_vesting_shares",
{
"delegatee": "ravishankarhass",
"delegator": "steem",
"vesting_shares": "29737.648303 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2017-12-12T22:23:21",
"trx_id": "de4decb2058bca2e7f1cdaa4268b02e59ba5b555",
"trx_in_block": 27,
"virtual_op": 0
}rahulbasuupvoted (100.00%) @ravishankarhass / comparison-of-various-dlt-a-k-a-block-chains2017/11/09 11:05:03
rahulbasuupvoted (100.00%) @ravishankarhass / comparison-of-various-dlt-a-k-a-block-chains
2017/11/09 11:05:03
| author | ravishankarhass |
| permlink | comparison-of-various-dlt-a-k-a-block-chains |
| voter | rahulbasu |
| weight | 10000 (100.00%) |
| Transaction Info | Block #17069084/Trx d51921dc31caa75c438a052163686bac0709ed2f |
View Raw JSON Data
{
"block": 17069084,
"op": [
"vote",
{
"author": "ravishankarhass",
"permlink": "comparison-of-various-dlt-a-k-a-block-chains",
"voter": "rahulbasu",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-11-09T11:05:03",
"trx_id": "d51921dc31caa75c438a052163686bac0709ed2f",
"trx_in_block": 21,
"virtual_op": 0
}ravishankarhasspublished a new post: comparison-of-various-dlt-a-k-a-block-chains2017/11/09 11:01:36
ravishankarhasspublished a new post: comparison-of-various-dlt-a-k-a-block-chains
2017/11/09 11:01:36
| author | ravishankarhass |
| body | @@ -521,17 +521,17 @@ y water -%5B +* The reas @@ -642,10 +642,9 @@ ment -%5D. +* %0A%0AL |
| json metadata | {"tags":["cyrptocurrency","blockchain","dlt"],"app":"steemit/0.1","format":"markdown","links":["http://explore-ip.com/2017_Comparison-of-Ethereum-Hyperledger-Corda.pdf"]} |
| parent author | |
| parent permlink | cyrptocurrency |
| permlink | comparison-of-various-dlt-a-k-a-block-chains |
| title | Comparison of Various DLT A.K.A Block chains |
| Transaction Info | Block #17069015/Trx 1c28d7a1126a67fa83c64eacd78ec5c5353efae9 |
View Raw JSON Data
{
"block": 17069015,
"op": [
"comment",
{
"author": "ravishankarhass",
"body": "@@ -521,17 +521,17 @@\n y water \n-%5B\n+*\n The reas\n@@ -642,10 +642,9 @@\n ment\n-%5D.\n+*\n %0A%0AL\n",
"json_metadata": "{\"tags\":[\"cyrptocurrency\",\"blockchain\",\"dlt\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\",\"links\":[\"http://explore-ip.com/2017_Comparison-of-Ethereum-Hyperledger-Corda.pdf\"]}",
"parent_author": "",
"parent_permlink": "cyrptocurrency",
"permlink": "comparison-of-various-dlt-a-k-a-block-chains",
"title": "Comparison of Various DLT A.K.A Block chains"
}
],
"op_in_trx": 0,
"timestamp": "2017-11-09T11:01:36",
"trx_id": "1c28d7a1126a67fa83c64eacd78ec5c5353efae9",
"trx_in_block": 8,
"virtual_op": 0
}ravishankarhasspublished a new post: comparison-of-various-dlt-a-k-a-block-chains2017/11/09 10:57:27
ravishankarhasspublished a new post: comparison-of-various-dlt-a-k-a-block-chains
2017/11/09 10:57:27
| author | ravishankarhass |
| body | @@ -915,17 +915,17 @@ of the B -o +i g Player |
| json metadata | {"tags":["cyrptocurrency","blockchain","dlt"],"app":"steemit/0.1","format":"markdown","links":["http://explore-ip.com/2017_Comparison-of-Ethereum-Hyperledger-Corda.pdf"]} |
| parent author | |
| parent permlink | cyrptocurrency |
| permlink | comparison-of-various-dlt-a-k-a-block-chains |
| title | Comparison of Various DLT A.K.A Block chains |
| Transaction Info | Block #17068932/Trx 89f35a967a2f59982f63b01016881bb64b8584b0 |
View Raw JSON Data
{
"block": 17068932,
"op": [
"comment",
{
"author": "ravishankarhass",
"body": "@@ -915,17 +915,17 @@\n of the B\n-o\n+i\n g Player\n",
"json_metadata": "{\"tags\":[\"cyrptocurrency\",\"blockchain\",\"dlt\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\",\"links\":[\"http://explore-ip.com/2017_Comparison-of-Ethereum-Hyperledger-Corda.pdf\"]}",
"parent_author": "",
"parent_permlink": "cyrptocurrency",
"permlink": "comparison-of-various-dlt-a-k-a-block-chains",
"title": "Comparison of Various DLT A.K.A Block chains"
}
],
"op_in_trx": 0,
"timestamp": "2017-11-09T10:57:27",
"trx_id": "89f35a967a2f59982f63b01016881bb64b8584b0",
"trx_in_block": 13,
"virtual_op": 0
}ravishankarhasspublished a new post: comparison-of-various-dlt-a-k-a-block-chains2017/11/09 10:56:51
ravishankarhasspublished a new post: comparison-of-various-dlt-a-k-a-block-chains
2017/11/09 10:56:51
| author | ravishankarhass |
| body | @@ -1388,20 +1388,94 @@ .%0A%0AThis -post +%5BPDF%5D(http://explore-ip.com/2017_Comparison-of-Ethereum-Hyperledger-Corda.pdf) will he @@ -1584,232 +1584,4 @@ ces. -%0A%0A### Three different frameworks %0A%0A_*Comparison of Ethereum, Hyperledger Fabric and Corda*_%0A%0A!%5B1-voQMw5mxBcw0buGe17xoKQ.png%5D(https://steemitimages.com/DQmda6xbFSjaVrce74cNBwUGgeGGgqo41fyrCPRmRgmBZAj/1-voQMw5mxBcw0buGe17xoKQ.png) |
| json metadata | {"tags":["cyrptocurrency","blockchain","dlt"],"app":"steemit/0.1","format":"markdown","links":["http://explore-ip.com/2017_Comparison-of-Ethereum-Hyperledger-Corda.pdf"]} |
| parent author | |
| parent permlink | cyrptocurrency |
| permlink | comparison-of-various-dlt-a-k-a-block-chains |
| title | Comparison of Various DLT A.K.A Block chains |
| Transaction Info | Block #17068920/Trx a6146c1551f2f9d0b99208e81d59f16d90970fb0 |
View Raw JSON Data
{
"block": 17068920,
"op": [
"comment",
{
"author": "ravishankarhass",
"body": "@@ -1388,20 +1388,94 @@\n .%0A%0AThis \n-post\n+%5BPDF%5D(http://explore-ip.com/2017_Comparison-of-Ethereum-Hyperledger-Corda.pdf)\n will he\n@@ -1584,232 +1584,4 @@\n ces.\n-%0A%0A### Three different frameworks %0A%0A_*Comparison of Ethereum, Hyperledger Fabric and Corda*_%0A%0A!%5B1-voQMw5mxBcw0buGe17xoKQ.png%5D(https://steemitimages.com/DQmda6xbFSjaVrce74cNBwUGgeGGgqo41fyrCPRmRgmBZAj/1-voQMw5mxBcw0buGe17xoKQ.png)\n",
"json_metadata": "{\"tags\":[\"cyrptocurrency\",\"blockchain\",\"dlt\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\",\"links\":[\"http://explore-ip.com/2017_Comparison-of-Ethereum-Hyperledger-Corda.pdf\"]}",
"parent_author": "",
"parent_permlink": "cyrptocurrency",
"permlink": "comparison-of-various-dlt-a-k-a-block-chains",
"title": "Comparison of Various DLT A.K.A Block chains"
}
],
"op_in_trx": 0,
"timestamp": "2017-11-09T10:56:51",
"trx_id": "a6146c1551f2f9d0b99208e81d59f16d90970fb0",
"trx_in_block": 1,
"virtual_op": 0
}ravishankarhasspublished a new post: comparison-of-various-dlt-a-k-a-block-chains2017/11/09 10:53:33
ravishankarhasspublished a new post: comparison-of-various-dlt-a-k-a-block-chains
2017/11/09 10:53:33
| author | ravishankarhass |
| body | @@ -297,22 +297,8 @@ ent -:simple_smile: If @@ -369,15 +369,8 @@ elf -:smirk: %0A%0AHa @@ -557,12 +557,8 @@ nce -its the |
| json metadata | {"tags":["cyrptocurrency","blockchain","dlt"],"image":["https://steemitimages.com/DQmda6xbFSjaVrce74cNBwUGgeGGgqo41fyrCPRmRgmBZAj/1-voQMw5mxBcw0buGe17xoKQ.png"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | cyrptocurrency |
| permlink | comparison-of-various-dlt-a-k-a-block-chains |
| title | Comparison of Various DLT A.K.A Block chains |
| Transaction Info | Block #17068855/Trx c86547f826c8635bb2fa7a484b979dc30c0fd865 |
View Raw JSON Data
{
"block": 17068855,
"op": [
"comment",
{
"author": "ravishankarhass",
"body": "@@ -297,22 +297,8 @@\n ent \n-:simple_smile:\n If \n@@ -369,15 +369,8 @@\n elf \n-:smirk:\n %0A%0AHa\n@@ -557,12 +557,8 @@\n nce \n-its \n the \n",
"json_metadata": "{\"tags\":[\"cyrptocurrency\",\"blockchain\",\"dlt\"],\"image\":[\"https://steemitimages.com/DQmda6xbFSjaVrce74cNBwUGgeGGgqo41fyrCPRmRgmBZAj/1-voQMw5mxBcw0buGe17xoKQ.png\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "cyrptocurrency",
"permlink": "comparison-of-various-dlt-a-k-a-block-chains",
"title": "Comparison of Various DLT A.K.A Block chains"
}
],
"op_in_trx": 0,
"timestamp": "2017-11-09T10:53:33",
"trx_id": "c86547f826c8635bb2fa7a484b979dc30c0fd865",
"trx_in_block": 6,
"virtual_op": 0
}2017/11/09 01:54:06
2017/11/09 01:54:06
| author | steemitboard |
| body | Congratulations @ravishankarhass! You have completed some achievement on Steemit and have been rewarded with new badge(s) : [](http://steemitboard.com/@ravishankarhass) You published your First Post [](http://steemitboard.com/@ravishankarhass) You made your First Vote [](http://steemitboard.com/@ravishankarhass) You got a First Vote Click on any badge to view your own Board of Honor on SteemitBoard. For more information about SteemitBoard, click [here](https://steemit.com/@steemitboard) If you no longer want to receive notifications, reply to this comment with the word `STOP` > By upvoting this notification, you can help all Steemit users. Learn how [here](https://steemit.com/steemitboard/@steemitboard/http-i-cubeupload-com-7ciqeo-png)! |
| json metadata | {"image":["https://steemitboard.com/img/notifications.png"]} |
| parent author | ravishankarhass |
| parent permlink | comparison-of-various-dlt-a-k-a-block-chains |
| permlink | steemitboard-notify-ravishankarhass-20171109t015405000z |
| title | |
| Transaction Info | Block #17058086/Trx e9196766900743fdc052120388361b0418b5b66e |
View Raw JSON Data
{
"block": 17058086,
"op": [
"comment",
{
"author": "steemitboard",
"body": "Congratulations @ravishankarhass! You have completed some achievement on Steemit and have been rewarded with new badge(s) :\n\n[](http://steemitboard.com/@ravishankarhass) You published your First Post\n[](http://steemitboard.com/@ravishankarhass) You made your First Vote\n[](http://steemitboard.com/@ravishankarhass) You got a First Vote\n\nClick on any badge to view your own Board of Honor on SteemitBoard.\nFor more information about SteemitBoard, click [here](https://steemit.com/@steemitboard)\n\nIf you no longer want to receive notifications, reply to this comment with the word `STOP`\n\n> By upvoting this notification, you can help all Steemit users. Learn how [here](https://steemit.com/steemitboard/@steemitboard/http-i-cubeupload-com-7ciqeo-png)!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notifications.png\"]}",
"parent_author": "ravishankarhass",
"parent_permlink": "comparison-of-various-dlt-a-k-a-block-chains",
"permlink": "steemitboard-notify-ravishankarhass-20171109t015405000z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2017-11-09T01:54:06",
"trx_id": "e9196766900743fdc052120388361b0418b5b66e",
"trx_in_block": 0,
"virtual_op": 0
}ravishankarhasspublished a new post: comparison-of-various-dlt-a-k-a-block-chains2017/11/08 23:37:24
ravishankarhasspublished a new post: comparison-of-various-dlt-a-k-a-block-chains
2017/11/08 23:37:24
| author | ravishankarhass |
| body | @@ -1570,906 +1570,8 @@ s %0A%0A -From the white papers of Hyperledger Fabric, R3 Corda (in the following only referred to as Fabric and Corda, respectively) and Ethereum it becomes obvious that these frameworks have very different visions in mind with respect to possible fields of application. Development of both Fabric and Corda is driven by concrete use cases, whereas Corda%E2%80%99s use cases are drawn from the financial services industry. Consequently, this is where Corda sees its main field of application. In contrast, Fabric intends to provide a modular and extendable architecture that can be employed in various industries, from banking and healthcare over to supply chains. Ethereum also presents itself as utterly independent of any specific field of application. However, in contrast to Fabric, it is not modularity that stands out but the provision of a generic platform for all kinds of transactions and applications. %0A%0A _*Co |
| json metadata | {"tags":["cyrptocurrency","blockchain","dlt"],"image":["https://steemitimages.com/DQmda6xbFSjaVrce74cNBwUGgeGGgqo41fyrCPRmRgmBZAj/1-voQMw5mxBcw0buGe17xoKQ.png"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | cyrptocurrency |
| permlink | comparison-of-various-dlt-a-k-a-block-chains |
| title | Comparison of Various DLT A.K.A Block chains |
| Transaction Info | Block #17055353/Trx eddc39333821e83f0ba59d5fa21f2bac7a319b75 |
View Raw JSON Data
{
"block": 17055353,
"op": [
"comment",
{
"author": "ravishankarhass",
"body": "@@ -1570,906 +1570,8 @@\n s %0A%0A\n-From the white papers of Hyperledger Fabric, R3 Corda (in the following only referred to as Fabric and Corda, respectively) and Ethereum it becomes obvious that these frameworks have very different visions in mind with respect to possible fields of application. Development of both Fabric and Corda is driven by concrete use cases, whereas Corda%E2%80%99s use cases are drawn from the financial services industry. Consequently, this is where Corda sees its main field of application. In contrast, Fabric intends to provide a modular and extendable architecture that can be employed in various industries, from banking and healthcare over to supply chains. Ethereum also presents itself as utterly independent of any specific field of application. However, in contrast to Fabric, it is not modularity that stands out but the provision of a generic platform for all kinds of transactions and applications. %0A%0A\n _*Co\n",
"json_metadata": "{\"tags\":[\"cyrptocurrency\",\"blockchain\",\"dlt\"],\"image\":[\"https://steemitimages.com/DQmda6xbFSjaVrce74cNBwUGgeGGgqo41fyrCPRmRgmBZAj/1-voQMw5mxBcw0buGe17xoKQ.png\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "cyrptocurrency",
"permlink": "comparison-of-various-dlt-a-k-a-block-chains",
"title": "Comparison of Various DLT A.K.A Block chains"
}
],
"op_in_trx": 0,
"timestamp": "2017-11-08T23:37:24",
"trx_id": "eddc39333821e83f0ba59d5fa21f2bac7a319b75",
"trx_in_block": 8,
"virtual_op": 0
}2017/11/08 23:36:36
2017/11/08 23:36:36
| author | cheetah |
| permlink | cheetah-re-ravishankarhasscomparison-of-various-dlt-a-k-a-block-chains |
| voter | ravishankarhass |
| weight | 10000 (100.00%) |
| Transaction Info | Block #17055337/Trx bbdf246616a57a458b37a0f160f116d15cf43f3c |
View Raw JSON Data
{
"block": 17055337,
"op": [
"vote",
{
"author": "cheetah",
"permlink": "cheetah-re-ravishankarhasscomparison-of-various-dlt-a-k-a-block-chains",
"voter": "ravishankarhass",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-11-08T23:36:36",
"trx_id": "bbdf246616a57a458b37a0f160f116d15cf43f3c",
"trx_in_block": 6,
"virtual_op": 0
}ravishankarhasspublished a new post: comparison-of-various-dlt-a-k-a-block-chains2017/11/08 23:34:57
ravishankarhasspublished a new post: comparison-of-various-dlt-a-k-a-block-chains
2017/11/08 23:34:57
| author | ravishankarhass |
| body | Currently at the time of writing this post (08-Nov-2017) Block Chain technologies A.K.A Distributed Ledger Technologies (DLT) are relatively new and are in the early stage but still they managed to disrupt the entire world with their power and use case. Do you need a proof to support my statement :simple_smile: If you are not convinced then look at Bitcoin. It will talk for itself :smirk: Having said that at the moment, there are lots of big players who are trying to roll of their sleeves and get their hands dirtied to test the muddy water [The reason I refer Muddy since its the whole technology space is in the beginning stage and not very clear at the moment]. Lots of experiments, Proof Of Concepts (PoC), Prototypes are being worked upon by Big players and also by commons technology enthusiastic and Start up Business Entrepreneurs to use this amazing technology and create a better living society for the man kind. Most of the Bog Players are targeting the Financial institutions across the world to gain the No 1 Position and quickly cash out the maximum Profit in the early stage by striking deals and to re brand them as leaders in this Space. Where as commons technology enthusiastic and Start up Business Entrepreneurs are trying to solve our daily day to day real life problems using Block Chain technologies A.K.A Distributed Ledger Technologies in a efficient and cheaper solutions. This post will help the readers to understand about the currently available or evolving Block chains and their differences. ### Three different frameworks From the white papers of Hyperledger Fabric, R3 Corda (in the following only referred to as Fabric and Corda, respectively) and Ethereum it becomes obvious that these frameworks have very different visions in mind with respect to possible fields of application. Development of both Fabric and Corda is driven by concrete use cases, whereas Corda’s use cases are drawn from the financial services industry. Consequently, this is where Corda sees its main field of application. In contrast, Fabric intends to provide a modular and extendable architecture that can be employed in various industries, from banking and healthcare over to supply chains. Ethereum also presents itself as utterly independent of any specific field of application. However, in contrast to Fabric, it is not modularity that stands out but the provision of a generic platform for all kinds of transactions and applications. _*Comparison of Ethereum, Hyperledger Fabric and Corda*_  |
| json metadata | {"tags":["cyrptocurrency","blockchain","dlt"],"image":["https://steemitimages.com/DQmda6xbFSjaVrce74cNBwUGgeGGgqo41fyrCPRmRgmBZAj/1-voQMw5mxBcw0buGe17xoKQ.png"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | cyrptocurrency |
| permlink | comparison-of-various-dlt-a-k-a-block-chains |
| title | Comparison of Various DLT A.K.A Block chains |
| Transaction Info | Block #17055304/Trx cbbd4124c35fa668076af839f92ffc5469ffb983 |
View Raw JSON Data
{
"block": 17055304,
"op": [
"comment",
{
"author": "ravishankarhass",
"body": "Currently at the time of writing this post (08-Nov-2017) Block Chain technologies A.K.A Distributed Ledger Technologies (DLT) are relatively new and are in the early stage but still they managed to disrupt the entire world with their power and use case.\n\nDo you need a proof to support my statement :simple_smile: If you are not convinced then look at Bitcoin. It will talk for itself :smirk:\n\nHaving said that at the moment, there are lots of big players who are trying to roll of their sleeves and get their hands dirtied to test the muddy water [The reason I refer Muddy since its the whole technology space is in the beginning stage and not very clear at the moment]. \n\nLots of experiments, Proof Of Concepts (PoC), Prototypes are being worked upon by Big players and also by commons technology enthusiastic and Start up Business Entrepreneurs to use this amazing technology and create a better living society for the man kind.\n\nMost of the Bog Players are targeting the Financial institutions across the world to gain the No 1 Position and quickly cash out the maximum Profit in the early stage by striking deals and to re brand them as leaders in this Space.\n\nWhere as commons technology enthusiastic and Start up Business Entrepreneurs are trying to solve our daily day to day real life problems using Block Chain technologies A.K.A Distributed Ledger Technologies in a efficient and cheaper solutions.\n\nThis post will help the readers to understand about the currently available or evolving Block chains and their differences.\n\n### Three different frameworks \n\nFrom the white papers of Hyperledger Fabric, R3 Corda (in the following only referred to as Fabric and Corda, respectively) and Ethereum it becomes obvious that these frameworks have very different visions in mind with respect to possible fields of application. Development of both Fabric and Corda is driven by concrete use cases, whereas Corda’s use cases are drawn from the financial services industry. Consequently, this is where Corda sees its main field of application. In contrast, Fabric intends to provide a modular and extendable architecture that can be employed in various industries, from banking and healthcare over to supply chains. Ethereum also presents itself as utterly independent of any specific field of application. However, in contrast to Fabric, it is not modularity that stands out but the provision of a generic platform for all kinds of transactions and applications. \n\n_*Comparison of Ethereum, Hyperledger Fabric and Corda*_\n\n",
"json_metadata": "{\"tags\":[\"cyrptocurrency\",\"blockchain\",\"dlt\"],\"image\":[\"https://steemitimages.com/DQmda6xbFSjaVrce74cNBwUGgeGGgqo41fyrCPRmRgmBZAj/1-voQMw5mxBcw0buGe17xoKQ.png\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "cyrptocurrency",
"permlink": "comparison-of-various-dlt-a-k-a-block-chains",
"title": "Comparison of Various DLT A.K.A Block chains"
}
],
"op_in_trx": 0,
"timestamp": "2017-11-08T23:34:57",
"trx_id": "cbbd4124c35fa668076af839f92ffc5469ffb983",
"trx_in_block": 13,
"virtual_op": 0
}anomalyupvoted (1.00%) @ravishankarhass / comparison-of-various-dlt-a-k-a-block-chains2017/11/08 22:49:51
anomalyupvoted (1.00%) @ravishankarhass / comparison-of-various-dlt-a-k-a-block-chains
2017/11/08 22:49:51
| author | ravishankarhass |
| permlink | comparison-of-various-dlt-a-k-a-block-chains |
| voter | anomaly |
| weight | 100 (1.00%) |
| Transaction Info | Block #17054402/Trx e80571c7d9a2815b9bc2b6a60f8d0d4877a1dc3c |
View Raw JSON Data
{
"block": 17054402,
"op": [
"vote",
{
"author": "ravishankarhass",
"permlink": "comparison-of-various-dlt-a-k-a-block-chains",
"voter": "anomaly",
"weight": 100
}
],
"op_in_trx": 0,
"timestamp": "2017-11-08T22:49:51",
"trx_id": "e80571c7d9a2815b9bc2b6a60f8d0d4877a1dc3c",
"trx_in_block": 15,
"virtual_op": 0
}2017/11/08 22:49:27
2017/11/08 22:49:27
| author | cheetah |
| body | Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in: https://medium.com/@philippsandner/comparison-of-ethereum-hyperledger-fabric-and-corda-21c1bb9442f6 |
| json metadata | |
| parent author | ravishankarhass |
| parent permlink | comparison-of-various-dlt-a-k-a-block-chains |
| permlink | cheetah-re-ravishankarhasscomparison-of-various-dlt-a-k-a-block-chains |
| title | |
| Transaction Info | Block #17054394/Trx 046cbabbe8a9626ff1f476d59094fa4357c5112d |
View Raw JSON Data
{
"block": 17054394,
"op": [
"comment",
{
"author": "cheetah",
"body": "Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in:\nhttps://medium.com/@philippsandner/comparison-of-ethereum-hyperledger-fabric-and-corda-21c1bb9442f6",
"json_metadata": "",
"parent_author": "ravishankarhass",
"parent_permlink": "comparison-of-various-dlt-a-k-a-block-chains",
"permlink": "cheetah-re-ravishankarhasscomparison-of-various-dlt-a-k-a-block-chains",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2017-11-08T22:49:27",
"trx_id": "046cbabbe8a9626ff1f476d59094fa4357c5112d",
"trx_in_block": 0,
"virtual_op": 0
}cheetahupvoted (0.50%) @ravishankarhass / comparison-of-various-dlt-a-k-a-block-chains2017/11/08 22:48:57
cheetahupvoted (0.50%) @ravishankarhass / comparison-of-various-dlt-a-k-a-block-chains
2017/11/08 22:48:57
| author | ravishankarhass |
| permlink | comparison-of-various-dlt-a-k-a-block-chains |
| voter | cheetah |
| weight | 50 (0.50%) |
| Transaction Info | Block #17054384/Trx 3df429d9278accb790896030d62f2424abb44241 |
View Raw JSON Data
{
"block": 17054384,
"op": [
"vote",
{
"author": "ravishankarhass",
"permlink": "comparison-of-various-dlt-a-k-a-block-chains",
"voter": "cheetah",
"weight": 50
}
],
"op_in_trx": 0,
"timestamp": "2017-11-08T22:48:57",
"trx_id": "3df429d9278accb790896030d62f2424abb44241",
"trx_in_block": 6,
"virtual_op": 0
}ravishankarhassupvoted (100.00%) @ravishankarhass / comparison-of-various-dlt-a-k-a-block-chains2017/11/08 22:48:42
ravishankarhassupvoted (100.00%) @ravishankarhass / comparison-of-various-dlt-a-k-a-block-chains
2017/11/08 22:48:42
| author | ravishankarhass |
| permlink | comparison-of-various-dlt-a-k-a-block-chains |
| voter | ravishankarhass |
| weight | 10000 (100.00%) |
| Transaction Info | Block #17054379/Trx c56c3e12eb00be09d8ea727a58345fa352168712 |
View Raw JSON Data
{
"block": 17054379,
"op": [
"vote",
{
"author": "ravishankarhass",
"permlink": "comparison-of-various-dlt-a-k-a-block-chains",
"voter": "ravishankarhass",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2017-11-08T22:48:42",
"trx_id": "c56c3e12eb00be09d8ea727a58345fa352168712",
"trx_in_block": 0,
"virtual_op": 0
}ravishankarhasspublished a new post: comparison-of-various-dlt-a-k-a-block-chains2017/11/08 22:48:42
ravishankarhasspublished a new post: comparison-of-various-dlt-a-k-a-block-chains
2017/11/08 22:48:42
| author | ravishankarhass |
| body | Currently at the time of writing this post (08-Nov-2017) Block Chain technologies A.K.A Distributed Ledger Technologies (DLT) are relatively new and are in the early stage but still they managed to disrupt the entire world with their power and use case. Do you need a proof to support my statement :simple_smile: If you are not convinced then look at Bitcoin. It will talk for itself :smirk: Having said that at the moment, there are lots of big players who are trying to roll of their sleeves and get their hands dirtied to test the muddy water [The reason I refer Muddy since its the whole technology space is in the beginning stage and not very clear at the moment]. Lots of experiments, Proof Of Concepts (PoC), Prototypes are being worked upon by Big players and also by commons technology enthusiastic and Start up Business Entrepreneurs to use this amazing technology and create a better living society for the man kind. Most of the Bog Players are targeting the Financial institutions across the world to gain the No 1 Position and quickly cash out the maximum Profit in the early stage by striking deals and to re brand them as leaders in this Space. Where as commons technology enthusiastic and Start up Business Entrepreneurs are trying to solve our daily day to day real life problems using Block Chain technologies A.K.A Distributed Ledger Technologies in a efficient and cheaper solutions. This post will help the readers to understand about the currently available or evolving Block chains and their differences. ### Three different frameworks From the white papers of Hyperledger Fabric, R3 Corda (in the following only referred to as Fabric and Corda, respectively) and Ethereum it becomes obvious that these frameworks have very different visions in mind with respect to possible fields of application. Development of both Fabric and Corda is driven by concrete use cases, whereas Corda’s use cases are drawn from the financial services industry. Consequently, this is where Corda sees its main field of application. In contrast, Fabric intends to provide a modular and extendable architecture that can be employed in various industries, from banking and healthcare over to supply chains. Ethereum also presents itself as utterly independent of any specific field of application. However, in contrast to Fabric, it is not modularity that stands out but the provision of a generic platform for all kinds of transactions and applications. _*Comparison of Ethereum, Hyperledger Fabric and Corda*_  ### Participation of peers With conventional central data storage, only a single entity, the owner, keeps a copy of the underlying database, e.g. a ledger. Consequently, this entity controls what data is contributed and what other entities are permitted to contribute. With the advent of DLT this radically changes in favor of distributed data storage where multiple entities hold a copy of the underlying database and are naturally permitted to contribute. All entities that participate in distributed data storage form a network of so-called nodes or peers. Due to distributed data storage, the difficulty arises to ensure that all nodes agree upon a common truth, e.g. the correctness of a ledger, as changes made by one node have to be propagated to all other peer nodes in the network. The result of arriving at a common truth is called consensus among nodes and is described below. With respect to participating to consensus, there are two modes of operation: *permissionless and permissioned.* If participation is permissionless, anybody is allowed to participate in the network. This mode is true for Ethereum as a public blockchain. On the other hand, if participation is permissioned, participants are selected in advance and access to the network is restricted to these only. This is true for Fabric and Corda. The mode of participation, permissionless or permissioned, has a profound impact on how consensus is reached. ### Consensus _Ethereum_. With Ethereum, all participants have to reach consensus over the order of all transactions that have taken place, irrespectively of whether a participant has taken part in a particular transaction or not. The order of the transactions is crucial for the consistent state of the ledger. If a definitive order of transactions cannot be established there is a chance that double-spends might have occurred, that is, two parallel transactions transfer the same coin to different recipients, thus making money out of thin air. As the network might involve mutually distrusting and anonymous parties, a consensus mechanism has to be employed that protects the ledger against fraudulent or adverse participants that attempt double-spends. In the current implementation of Ethereum, this mechanism is established by mining based on the proof-of-work (PoW) scheme. All participants have to agree upon a common ledger and all participants have access to all entries ever recorded. The consequences are that PoW unfavorably affects the performance of transactions processing. Concerning the data stored on the ledger, even though records are anonymized, they are nevertheless accessible to all participants, which is problematic for applications that require a higher degree of privacy. In contrast to Ethereum, Fabric’s and Corda’s interpretation of consensus is more refined and does not merely boil down to mining based on PoW or a derivative thereof. Due to operating in a permissioned mode, Fabric and Corda provide a more fine-grained access control to records and thus enhance privacy. Furthermore, a gain in performance is achieved as only parties taking part in a transaction have to reach consensus. _Fabric._ Fabric’s understanding of consensus is broad and encompasses the whole transaction flow, starting from proposing a transaction to the network to committing it to the ledger. Furthermore, nodes assume different roles and tasks in the process of reaching consensus. This contrasts to Ethereum where roles and tasks of nodes participating in reaching consensus are identical. Within Fabric, nodes are differentiated based on whether they are clients, peers or orderers. A client acts on behalf of an end-user and creates and thereby invokes transactions. They communicate with both peers and orderers. Peers maintain the ledger and receive ordered update messages from orderers for committing new transactions to the ledger. Endorsers are a special type of peer, whereas their task is to endorse a transaction by checking whether they fulfill necessary and sufficient conditions (e.g. the provision of required signatures). Orderers provide a communication channel to clients and peers over which messages containing transactions can be broadcasted. With respect to consensus in particular, the channels ensure that all connected peers are delivered exactly the same messages with exactly the same logical order. _*The mode of Participation permissioned or permissionless has a profound impact on how consensus is reached.*_ At this point, the problem arises that there might occur faults in the delivery of messages when many mutually untrusting orderers are employed. As a consequence, a consensus algorithm has to be used in order to reach consensus despite faults, e.g. inconsistent order of messages, thus making the replication of the distributed ledger faults tolerant. With Fabric, the algorithm employed is “pluggable”, meaning that depending on application-specific requirements various algorithms can be used. For example, in order to deal with random or malicious replication faults as outlined above a variant of the Byzantine fault-tolerant (BFT) algorithms could be used. Furthermore, channels partition message flows, meaning that clients only see the messages and associated transactions of the channels they are connected to and are unaware of other channels. This way, access to transactions is restricted to involved parties only with the consequence that consensus has only to be reached at transaction level and not at ledger level as with Ethereum. The roles of nodes outlined above are now described in the context of the transaction flow: A client sends a transaction to connected endorsers in order to initiate an update of the ledger. All endorsers have to agree upon the proposed transaction, thus some sort of consensus has to be reached regarding the proposed ledger update. The client now successively collects approval of all endorsers. The approved transaction is now sent to connected orderers which again reach consensus. Subsequently, the transaction is forwarded to peers holding the ledger for committing the transaction. Without going further into detail, it becomes clear that Fabric allows fine-grained control over consensus and restricted access to transactions which results in improved performance scalability and privacy. _Corda._ Similar to Fabric, consensus in Corda is also reached at transaction level by involving parties only. Subject to consensus is transaction validity and transaction uniqueness. Validity is ensured by running the smart contract code (smart contracts are described in detail below) associated with a transaction, by checking for all required signatures and by assuring that any transactions that are referred to are also valid. Uniqueness concerns the input states of a transaction. Specifically, it has to be ensured that the transaction in question is the unique consumer of all its input states. In other words, there exists no other transaction that consumes any of the same states. The reason for this is to avoid double-spends. Consensus over uniqueness is reached among participants called notary nodes, whereas the employed algorithm is “pluggable” as with Fabric. So once again a BFT algorithm might be used. ### Smart contracts The term “smart contract” causes considerable misunderstanding when first encountered as it evokes the idea of some sort of contract that intelligently acts on one’s behalf. The contract’s nature, however, remains vague, but intuitively appears to be linked to legal matters. That said, focal contracts are neither smart in the sense that they are e.g. driven by artificial intelligence, at least not yet, nor do they generally encode obligations and rights that are legally binding. Clark and colleagues provide a useful terminology by highlighting two different ways the term “smart contracts” is commonly used. The first refers to smart contract code, the second to smart legal contracts, two distinctions that prove to be beneficial in the context of this comparison. Smart contract code simply denotes software written in a programming language. It acts as a software agent or delegate of the party that employed it with the intention that it fulfills certain obligations, exercises rights and may take control of assets within a distributed ledger in an automated way. Thus, it takes on tasks and responsibilities in the distributed ledger world by executing code that models or emulates contract logic in the real world, though its legal justification may be unclear. *Smart contract code simple denotes software written in a programming language* All DLTs feature smart contracts in the sense of smart contract code that can be written in Go or Java for Fabric, in Solidity for Ethereum and in Java or Kotlin for Corda. In Fabric, the term “chaincode” is used as a synonym for smart contract. As an illustrative example, the reader is reminded of the usage of a smart contract code in the consensus mechanism of Corda in order to ensure transaction validity. However, there is a notable difference between Fabric and Ethereum on the one hand and Corda on the other that is connected to the second way the “smart contracts” term is used. In Corda, smart contracts not only consist of code but additionally are allowed to contain legal prose. Thus above smart legal contracts are legal prose that are formulated in a way that they can be expressed and implemented in smart contract code. The rationale behind this is to give the code legitimacy that is rooted in the associated legal prose. Such a construct is called Ricardian Contract. At this point, it again becomes clear that Corda was explicitly designed to account for the highly regulated environment of the financial services industry. Both Fabric and Ethereum lack this feature. ### Built-in currency Another noteworthy difference is that Ethereum features a build-in cryptocurrency called Ether. It is used to pay rewards to nodes that contribute to reach consensus by mining blocks as well as to pay transaction fees. Therefore decentralized apps (DApps) can be built for Ethereum that allow monetary transactions. Furthermore, a digital token for custom use cases can be created by deploying a smart contract that conforms to a pre-defined standard. This way, own currencies or assets can be defined. Fabric and Corda do not require a build-in cryptocurrency as consensus is not reached via mining. With Fabric, however, it is possible to develop a native currency or a digital token with chaincode. With Corda, a creation of digital currencies or tokens is not intended. ### Summary: customized vs. generic platform To sum up, the examined DLTs span a continuum. On the one side, there is Fabric and Ethereum. They both are highly flexible, but in different aspects. Ethereum’s powerful smart contracts engine makes it a generic platform for literally any kind of application. However, Ethereum’s permissionless mode of operation and its total transparency comes at the cost of performance scalability and privacy. Fabric solves performance scalability and privacy issues by permissioned mode of operation and specifically by using a BFT algorithm and fine-grained access control. Further, the modular architecture allows Fabric to be customized to a multitude of applications. An analogy to a versatile toolbox can be drawn. Corda is located at the other end. It has been consciously designed as DLT for the financial services industry. Most notably, it takes the highly regulated environment into account by augmenting smart contracts with legal prose. Apparently, Corda’s focus solely on financial services transactions simplified its architectural design compared to Fabric. Therefore, it might offer a more out-of-the-box experience. However, it might be possible that Fabric, due to its modularity, can be tailored to resemble Corda’s feature set. Efforts exist that seek to integrate Corda into the Hyperledger project. Corda therefore cannot be seen as a competitor to Fabric but more as a complement. |
| json metadata | {"tags":["cyrptocurrency","blockchain","dlt"],"image":["https://steemitimages.com/DQmda6xbFSjaVrce74cNBwUGgeGGgqo41fyrCPRmRgmBZAj/1-voQMw5mxBcw0buGe17xoKQ.png"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | cyrptocurrency |
| permlink | comparison-of-various-dlt-a-k-a-block-chains |
| title | Comparison of Various DLT A.K.A Block chains |
| Transaction Info | Block #17054379/Trx c56c3e12eb00be09d8ea727a58345fa352168712 |
View Raw JSON Data
{
"block": 17054379,
"op": [
"comment",
{
"author": "ravishankarhass",
"body": "Currently at the time of writing this post (08-Nov-2017) Block Chain technologies A.K.A Distributed Ledger Technologies (DLT) are relatively new and are in the early stage but still they managed to disrupt the entire world with their power and use case.\n\nDo you need a proof to support my statement :simple_smile: If you are not convinced then look at Bitcoin. It will talk for itself :smirk:\n\nHaving said that at the moment, there are lots of big players who are trying to roll of their sleeves and get their hands dirtied to test the muddy water [The reason I refer Muddy since its the whole technology space is in the beginning stage and not very clear at the moment]. \n\nLots of experiments, Proof Of Concepts (PoC), Prototypes are being worked upon by Big players and also by commons technology enthusiastic and Start up Business Entrepreneurs to use this amazing technology and create a better living society for the man kind.\n\nMost of the Bog Players are targeting the Financial institutions across the world to gain the No 1 Position and quickly cash out the maximum Profit in the early stage by striking deals and to re brand them as leaders in this Space.\n\nWhere as commons technology enthusiastic and Start up Business Entrepreneurs are trying to solve our daily day to day real life problems using Block Chain technologies A.K.A Distributed Ledger Technologies in a efficient and cheaper solutions.\n\nThis post will help the readers to understand about the currently available or evolving Block chains and their differences.\n\n### Three different frameworks \n\nFrom the white papers of Hyperledger Fabric, R3 Corda (in the following only referred to as Fabric and Corda, respectively) and Ethereum it becomes obvious that these frameworks have very different visions in mind with respect to possible fields of application. Development of both Fabric and Corda is driven by concrete use cases, whereas Corda’s use cases are drawn from the financial services industry. Consequently, this is where Corda sees its main field of application. In contrast, Fabric intends to provide a modular and extendable architecture that can be employed in various industries, from banking and healthcare over to supply chains. Ethereum also presents itself as utterly independent of any specific field of application. However, in contrast to Fabric, it is not modularity that stands out but the provision of a generic platform for all kinds of transactions and applications. \n\n_*Comparison of Ethereum, Hyperledger Fabric and Corda*_\n\n\n\n### Participation of peers\n\nWith conventional central data storage, only a single entity, the owner, keeps a copy of the underlying database, e.g. a ledger. Consequently, this entity controls what data is contributed and what other entities are permitted to contribute. With the advent of DLT this radically changes in favor of distributed data storage where multiple entities hold a copy of the underlying database and are naturally permitted to contribute. All entities that participate in distributed data storage form a network of so-called nodes or peers. Due to distributed data storage, the difficulty arises to ensure that all nodes agree upon a common truth, e.g. the correctness of a ledger, as changes made by one node have to be propagated to all other peer nodes in the network. The result of arriving at a common truth is called consensus among nodes and is described below.\n\nWith respect to participating to consensus, there are two modes of operation: *permissionless and permissioned.*\n\nIf participation is permissionless, anybody is allowed to participate in the network. This mode is true for Ethereum as a public blockchain. On the other hand, if participation is permissioned, participants are selected in advance and access to the network is restricted to these only. This is true for Fabric and Corda. The mode of participation, permissionless or permissioned, has a profound impact on how consensus is reached.\n\n### Consensus\n\n_Ethereum_. With Ethereum, all participants have to reach consensus over the order of all transactions that have taken place, irrespectively of whether a participant has taken part in a particular transaction or not. The order of the transactions is crucial for the consistent state of the ledger. If a definitive order of transactions cannot be established there is a chance that double-spends might have occurred, that is, two parallel transactions transfer the same coin to different recipients, thus making money out of thin air. As the network might involve mutually distrusting and anonymous parties, a consensus mechanism has to be employed that protects the ledger against fraudulent or adverse participants that attempt double-spends. In the current implementation of Ethereum, this mechanism is established by mining based on the proof-of-work (PoW) scheme. All participants have to agree upon a common ledger and all participants have access to all entries ever recorded. The consequences are that PoW unfavorably affects the performance of transactions processing. Concerning the data stored on the ledger, even though records are anonymized, they are nevertheless accessible to all participants, which is problematic for applications that require a higher degree of privacy.\n\nIn contrast to Ethereum, Fabric’s and Corda’s interpretation of consensus is more refined and does not merely boil down to mining based on PoW or a derivative thereof. Due to operating in a permissioned mode, Fabric and Corda provide a more fine-grained access control to records and thus enhance privacy. Furthermore, a gain in performance is achieved as only parties taking part in a transaction have to reach consensus.\n\n_Fabric._ Fabric’s understanding of consensus is broad and encompasses the whole transaction flow, starting from proposing a transaction to the network to committing it to the ledger. Furthermore, nodes assume different roles and tasks in the process of reaching consensus. This contrasts to Ethereum where roles and tasks of nodes participating in reaching consensus are identical.\n\nWithin Fabric, nodes are differentiated based on whether they are clients, peers or orderers. A client acts on behalf of an end-user and creates and thereby invokes transactions. They communicate with both peers and orderers. Peers maintain the ledger and receive ordered update messages from orderers for committing new transactions to the ledger. Endorsers are a special type of peer, whereas their task is to endorse a transaction by checking whether they fulfill necessary and sufficient conditions (e.g. the provision of required signatures). Orderers provide a communication channel to clients and peers over which messages containing transactions can be broadcasted. With respect to consensus in particular, the channels ensure that all connected peers are delivered exactly the same messages with exactly the same logical order.\n\n_*The mode of Participation permissioned or permissionless has a profound impact on how consensus is reached.*_ \n\nAt this point, the problem arises that there might occur faults in the delivery of messages when many mutually untrusting orderers are employed. As a consequence, a consensus algorithm has to be used in order to reach consensus despite faults, e.g. inconsistent order of messages, thus making the replication of the distributed ledger faults tolerant. With Fabric, the algorithm employed is “pluggable”, meaning that depending on application-specific requirements various algorithms can be used. For example, in order to deal with random or malicious replication faults as outlined above a variant of the Byzantine fault-tolerant (BFT) algorithms could be used. Furthermore, channels partition message flows, meaning that clients only see the messages and associated transactions of the channels they are connected to and are unaware of other channels. This way, access to transactions is restricted to involved parties only with the consequence that consensus has only to be reached at transaction level and not at ledger level as with Ethereum.\nThe roles of nodes outlined above are now described in the context of the transaction flow: A client sends a transaction to connected endorsers in order to initiate an update of the ledger. All endorsers have to agree upon the proposed transaction, thus some sort of consensus has to be reached regarding the proposed ledger update. The client now successively collects approval of all endorsers. The approved transaction is now sent to connected orderers which again reach consensus. Subsequently, the transaction is forwarded to peers holding the ledger for committing the transaction.\nWithout going further into detail, it becomes clear that Fabric allows fine-grained control over consensus and restricted access to transactions which results in improved performance scalability and privacy.\n\n_Corda._ Similar to Fabric, consensus in Corda is also reached at transaction level by involving parties only. Subject to consensus is transaction validity and transaction uniqueness. Validity is ensured by running the smart contract code (smart contracts are described in detail below) associated with a transaction, by checking for all required signatures and by assuring that any transactions that are referred to are also valid. Uniqueness concerns the input states of a transaction. Specifically, it has to be ensured that the transaction in question is the unique consumer of all its input states. In other words, there exists no other transaction that consumes any of the same states. The reason for this is to avoid double-spends. Consensus over uniqueness is reached among participants called notary nodes, whereas the employed algorithm is “pluggable” as with Fabric. So once again a BFT algorithm might be used.\n\n### Smart contracts\n\nThe term “smart contract” causes considerable misunderstanding when first encountered as it evokes the idea of some sort of contract that intelligently acts on one’s behalf. The contract’s nature, however, remains vague, but intuitively appears to be linked to legal matters. That said, focal contracts are neither smart in the sense that they are e.g. driven by artificial intelligence, at least not yet, nor do they generally encode obligations and rights that are legally binding. Clark and colleagues provide a useful terminology by highlighting two different ways the term “smart contracts” is commonly used. The first refers to smart contract code, the second to smart legal contracts, two distinctions that prove to be beneficial in the context of this comparison.\n\nSmart contract code simply denotes software written in a programming language. It acts as a software agent or delegate of the party that employed it with the intention that it fulfills certain obligations, exercises rights and may take control of assets within a distributed ledger in an automated way. Thus, it takes on tasks and responsibilities in the distributed ledger world by executing code that models or emulates contract logic in the real world, though its legal justification may be unclear.\n\n*Smart contract code simple denotes software written in a programming language*\n\nAll DLTs feature smart contracts in the sense of smart contract code that can be written in Go or Java for Fabric, in Solidity for Ethereum and in Java or Kotlin for Corda. In Fabric, the term “chaincode” is used as a synonym for smart contract. As an illustrative example, the reader is reminded of the usage of a smart contract code in the consensus mechanism of Corda in order to ensure transaction validity. However, there is a notable difference between Fabric and Ethereum on the one hand and Corda on the other that is connected to the second way the “smart contracts” term is used.\n\nIn Corda, smart contracts not only consist of code but additionally are allowed to contain legal prose. Thus above smart legal contracts are legal prose that are formulated in a way that they can be expressed and implemented in smart contract code. The rationale behind this is to give the code legitimacy that is rooted in the associated legal prose. Such a construct is called Ricardian Contract. At this point, it again becomes clear that Corda was explicitly designed to account for the highly regulated environment of the financial services industry. Both Fabric and Ethereum lack this feature.\n\n### Built-in currency\n\nAnother noteworthy difference is that Ethereum features a build-in cryptocurrency called Ether. It is used to pay rewards to nodes that contribute to reach consensus by mining blocks as well as to pay transaction fees. Therefore decentralized apps (DApps) can be built for Ethereum that allow monetary transactions. Furthermore, a digital token for custom use cases can be created by deploying a smart contract that conforms to a pre-defined standard. This way, own currencies or assets can be defined.\n\nFabric and Corda do not require a build-in cryptocurrency as consensus is not reached via mining. With Fabric, however, it is possible to develop a native currency or a digital token with chaincode. With Corda, a creation of digital currencies or tokens is not intended.\n\n### Summary: customized vs. generic platform\n\nTo sum up, the examined DLTs span a continuum. On the one side, there is Fabric and Ethereum. They both are highly flexible, but in different aspects. Ethereum’s powerful smart contracts engine makes it a generic platform for literally any kind of application. However, Ethereum’s permissionless mode of operation and its total transparency comes at the cost of performance scalability and privacy.\n\nFabric solves performance scalability and privacy issues by permissioned mode of operation and specifically by using a BFT algorithm and fine-grained access control. Further, the modular architecture allows Fabric to be customized to a multitude of applications. An analogy to a versatile toolbox can be drawn.\n\nCorda is located at the other end. It has been consciously designed as DLT for the financial services industry. Most notably, it takes the highly regulated environment into account by augmenting smart contracts with legal prose.\nApparently, Corda’s focus solely on financial services transactions simplified its architectural design compared to Fabric. Therefore, it might offer a more out-of-the-box experience. However, it might be possible that Fabric, due to its modularity, can be tailored to resemble Corda’s feature set. Efforts exist that seek to integrate Corda into the Hyperledger project. Corda therefore cannot be seen as a competitor to Fabric but more as a complement.",
"json_metadata": "{\"tags\":[\"cyrptocurrency\",\"blockchain\",\"dlt\"],\"image\":[\"https://steemitimages.com/DQmda6xbFSjaVrce74cNBwUGgeGGgqo41fyrCPRmRgmBZAj/1-voQMw5mxBcw0buGe17xoKQ.png\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "cyrptocurrency",
"permlink": "comparison-of-various-dlt-a-k-a-block-chains",
"title": "Comparison of Various DLT A.K.A Block chains"
}
],
"op_in_trx": 0,
"timestamp": "2017-11-08T22:48:42",
"trx_id": "c56c3e12eb00be09d8ea727a58345fa352168712",
"trx_in_block": 0,
"virtual_op": 0
}ravishankarhassfollowed @shrenik2017/10/20 19:57:21
ravishankarhassfollowed @shrenik
2017/10/20 19:57:21
| id | follow |
| json | ["follow",{"follower":"ravishankarhass","following":"shrenik","what":["blog"]}] |
| required auths | [] |
| required posting auths | ["ravishankarhass"] |
| Transaction Info | Block #16504057/Trx a6e7c0407e34e98e1329750599a053dd46628b9a |
View Raw JSON Data
{
"block": 16504057,
"op": [
"custom_json",
{
"id": "follow",
"json": "[\"follow\",{\"follower\":\"ravishankarhass\",\"following\":\"shrenik\",\"what\":[\"blog\"]}]",
"required_auths": [],
"required_posting_auths": [
"ravishankarhass"
]
}
],
"op_in_trx": 0,
"timestamp": "2017-10-20T19:57:21",
"trx_id": "a6e7c0407e34e98e1329750599a053dd46628b9a",
"trx_in_block": 9,
"virtual_op": 0
}ravishankarhassfollowed @sanjayrai2017/10/20 19:56:42
ravishankarhassfollowed @sanjayrai
2017/10/20 19:56:42
| id | follow |
| json | ["follow",{"follower":"ravishankarhass","following":"sanjayrai","what":["blog"]}] |
| required auths | [] |
| required posting auths | ["ravishankarhass"] |
| Transaction Info | Block #16504044/Trx 884e875c59162a31b04009842d593b216c17d5df |
View Raw JSON Data
{
"block": 16504044,
"op": [
"custom_json",
{
"id": "follow",
"json": "[\"follow\",{\"follower\":\"ravishankarhass\",\"following\":\"sanjayrai\",\"what\":[\"blog\"]}]",
"required_auths": [],
"required_posting_auths": [
"ravishankarhass"
]
}
],
"op_in_trx": 0,
"timestamp": "2017-10-20T19:56:42",
"trx_id": "884e875c59162a31b04009842d593b216c17d5df",
"trx_in_block": 5,
"virtual_op": 0
}ravishankarhassfollowed @rahulbasu2017/10/20 19:55:33
ravishankarhassfollowed @rahulbasu
2017/10/20 19:55:33
| id | follow |
| json | ["follow",{"follower":"ravishankarhass","following":"rahulbasu","what":["blog"]}] |
| required auths | [] |
| required posting auths | ["ravishankarhass"] |
| Transaction Info | Block #16504021/Trx 43bbe09337b2e6907859a5a58e238f7791b88c7e |
View Raw JSON Data
{
"block": 16504021,
"op": [
"custom_json",
{
"id": "follow",
"json": "[\"follow\",{\"follower\":\"ravishankarhass\",\"following\":\"rahulbasu\",\"what\":[\"blog\"]}]",
"required_auths": [],
"required_posting_auths": [
"ravishankarhass"
]
}
],
"op_in_trx": 0,
"timestamp": "2017-10-20T19:55:33",
"trx_id": "43bbe09337b2e6907859a5a58e238f7791b88c7e",
"trx_in_block": 0,
"virtual_op": 0
}steemcreated a new account: @ravishankarhass2017/10/20 19:38:24
steemcreated a new account: @ravishankarhass
2017/10/20 19:38:24
| active | {"account_auths":[],"key_auths":[["STM5vq6RnnnLtnKoTHTCHxEByVjmKLGUZLh6HEfJctW7rjGiRDcHu",1]],"weight_threshold":1} |
| creator | steem |
| delegation | 57000.000000 VESTS |
| extensions | [] |
| fee | 0.500 STEEM |
| json metadata | |
| memo key | STM6pKm1DdwfriAdeLeDZWSn2DziYQBvwAZAkDeUnvXjEC4CXNFmV |
| new account name | ravishankarhass |
| owner | {"account_auths":[],"key_auths":[["STM6xbDwDjXHWh5K1znabhVng6Dz1h1ZDRQJgdb9ccTCjQkstA1sq",1]],"weight_threshold":1} |
| posting | {"account_auths":[],"key_auths":[["STM6rBFmkPwXQUMJ2gwjTUf2DMmMpFQdKTSqcaPwHsthhtdMVQpsg",1]],"weight_threshold":1} |
| Transaction Info | Block #16503678/Trx 09b158330e8dd30e7ab811adfb4d3ab39a06af44 |
View Raw JSON Data
{
"block": 16503678,
"op": [
"account_create_with_delegation",
{
"active": {
"account_auths": [],
"key_auths": [
[
"STM5vq6RnnnLtnKoTHTCHxEByVjmKLGUZLh6HEfJctW7rjGiRDcHu",
1
]
],
"weight_threshold": 1
},
"creator": "steem",
"delegation": "57000.000000 VESTS",
"extensions": [],
"fee": "0.500 STEEM",
"json_metadata": "",
"memo_key": "STM6pKm1DdwfriAdeLeDZWSn2DziYQBvwAZAkDeUnvXjEC4CXNFmV",
"new_account_name": "ravishankarhass",
"owner": {
"account_auths": [],
"key_auths": [
[
"STM6xbDwDjXHWh5K1znabhVng6Dz1h1ZDRQJgdb9ccTCjQkstA1sq",
1
]
],
"weight_threshold": 1
},
"posting": {
"account_auths": [],
"key_auths": [
[
"STM6rBFmkPwXQUMJ2gwjTUf2DMmMpFQdKTSqcaPwHsthhtdMVQpsg",
1
]
],
"weight_threshold": 1
}
}
],
"op_in_trx": 0,
"timestamp": "2017-10-20T19:38:24",
"trx_id": "09b158330e8dd30e7ab811adfb4d3ab39a06af44",
"trx_in_block": 12,
"virtual_op": 0
}Manabar
Voting Power100.00%
Downvote Power100.00%
Resource Credits100.00%
Reputation Progress0.00%
{
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779082344
},
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779082344
},
"rc_account": {
"account": "ravishankarhass",
"max_rc": "10164408779",
"max_rc_creation_adjustment": {
"amount": "2020748973",
"nai": "@@000000037",
"precision": 6
},
"rc_manabar": {
"current_mana": "10164408779",
"last_update_time": 1779082344
}
}
}Account Metadata
| POSTING JSON METADATA | |
| None | |
| JSON METADATA | |
| None |
{
"posting_json_metadata": {},
"json_metadata": {}
}Auth Keys
Owner
Single Signature
Public Keys
STM6xbDwDjXHWh5K1znabhVng6Dz1h1ZDRQJgdb9ccTCjQkstA1sq1/1
Active
Single Signature
Public Keys
STM5vq6RnnnLtnKoTHTCHxEByVjmKLGUZLh6HEfJctW7rjGiRDcHu1/1
Posting
Single Signature
Public Keys
STM6rBFmkPwXQUMJ2gwjTUf2DMmMpFQdKTSqcaPwHsthhtdMVQpsg1/1
Memo
STM6pKm1DdwfriAdeLeDZWSn2DziYQBvwAZAkDeUnvXjEC4CXNFmV
{
"owner": {
"account_auths": [],
"key_auths": [
[
"STM6xbDwDjXHWh5K1znabhVng6Dz1h1ZDRQJgdb9ccTCjQkstA1sq",
1
]
],
"weight_threshold": 1
},
"active": {
"account_auths": [],
"key_auths": [
[
"STM5vq6RnnnLtnKoTHTCHxEByVjmKLGUZLh6HEfJctW7rjGiRDcHu",
1
]
],
"weight_threshold": 1
},
"posting": {
"account_auths": [],
"key_auths": [
[
"STM6rBFmkPwXQUMJ2gwjTUf2DMmMpFQdKTSqcaPwHsthhtdMVQpsg",
1
]
],
"weight_threshold": 1
},
"memo": "STM6pKm1DdwfriAdeLeDZWSn2DziYQBvwAZAkDeUnvXjEC4CXNFmV"
}Witness Votes
0 / 30
No active witness votes.
[]