@thomasoss
36Computer Scientist, software architect, Java programmer, mainframe specialist, project manager
steemit.com/@thomasossVOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS41.18%
Net Worth
3.059USD
STEEM
0.635STEEM
SBD
0.001SBD
Own SP
52.092SP
Detailed Balance
| STEEM | ||
| balance | 0.635STEEM | STEEM |
| market_balance | 0.000STEEM | STEEM |
| savings_balance | 0.000STEEM | STEEM |
| reward_steem_balance | 0.000STEEM | STEEM |
| STEEM POWER | ||
| Own SP | 52.092SP | SP |
| Delegated Out | 0.000SP | SP |
| Delegation In | 0.000SP | SP |
| Effective Power | 52.092SP | SP |
| Reward SP (pending) | 0.000SP | SP |
| SBD | ||
| sbd_balance | 0.001SBD | 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.635 STEEM",
"savings_balance": "0.000 STEEM",
"reward_steem_balance": "0.000 STEEM",
"vesting_shares": "84723.693953 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "0.000000 VESTS",
"sbd_balance": "0.001 SBD",
"savings_sbd_balance": "0.000 SBD",
"reward_sbd_balance": "0.000 SBD",
"conversions": []
}Account Info
| name | thomasoss |
| id | 126674 |
| rank | 33,421 |
| reputation | 18534464147 |
| created | 2017-01-15T16:57:39 |
| recovery_account | steem |
| proxy | None |
| post_count | 14 |
| comment_count | 0 |
| lifetime_vote_count | 0 |
| witnesses_voted_for | 0 |
| last_post | 2022-04-13T05:43:42 |
| last_root_post | 2020-03-07T07:35:51 |
| last_vote_time | 2022-04-13T05:45:42 |
| proxied_vsf_votes | 0, 0, 0, 0 |
| can_vote | 1 |
| voting_power | 9,799 |
| delayed_votes | 0 |
| balance | 0.635 STEEM |
| savings_balance | 0.000 STEEM |
| sbd_balance | 0.001 SBD |
| savings_sbd_balance | 0.000 SBD |
| vesting_shares | 84723.693953 VESTS |
| delegated_vesting_shares | 0.000000 VESTS |
| received_vesting_shares | 0.000000 VESTS |
| reward_vesting_balance | 0.000000 VESTS |
| vesting_balance | 0.000 STEEM |
| vesting_withdraw_rate | 0.000000 VESTS |
| next_vesting_withdrawal | 1969-12-31T23:59:59 |
| withdrawn | 0 |
| to_withdraw | 0 |
| withdraw_routes | 0 |
| savings_withdraw_requests | 0 |
| last_account_recovery | 1970-01-01T00:00:00 |
| reset_account | null |
| last_owner_update | 1970-01-01T00:00:00 |
| last_account_update | 2019-08-03T14:23:48 |
| 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": [
[
"STM63WeGsis3XyiHWozNZc8khRLBV4MjUujdn58gienX8mEdSJztv",
1
]
],
"weight_threshold": 1
},
"balance": "0.635 STEEM",
"can_vote": true,
"comment_count": 0,
"created": "2017-01-15T16:57:39",
"curation_rewards": 3,
"delegated_vesting_shares": "0.000000 VESTS",
"downvote_manabar": {
"current_mana": "21180923488",
"last_update_time": 1649828742
},
"guest_bloggers": [],
"id": 126674,
"json_metadata": "{\"profile\":{\"name\":\"Thomas\",\"about\":\"Computer Scientist, software architect, Java programmer, mainframe specialist, project manager\",\"location\":\"Munich, Germany\",\"cover_image\":\"https://steemitimages.com/0x0/http://i.imgur.com/wHMAhxy.jpg\",\"profile_image\":\"https://cdn.steemitimages.com/DQmYcL4i2C3q5yqGH6avREovheJvHzkjF2ibkaELQyqPDAR/P1080321.JPG\"}}",
"last_account_recovery": "1970-01-01T00:00:00",
"last_account_update": "2019-08-03T14:23:48",
"last_owner_update": "1970-01-01T00:00:00",
"last_post": "2022-04-13T05:43:42",
"last_root_post": "2020-03-07T07:35:51",
"last_vote_time": "2022-04-13T05:45:42",
"lifetime_vote_count": 0,
"market_history": [],
"memo_key": "STM84nXo7phwufo1t7T6KepGrJvRWWMDHcxtSemMD62V1HGEkmRN1",
"mined": false,
"name": "thomasoss",
"next_vesting_withdrawal": "1969-12-31T23:59:59",
"other_history": [],
"owner": {
"account_auths": [],
"key_auths": [
[
"STM5szVtUx4nfZq9pjwqTxsPHMpGyFLSsKoNE2zNjAyefF2tWpszb",
1
]
],
"weight_threshold": 1
},
"pending_claimed_accounts": 0,
"post_bandwidth": 0,
"post_count": 14,
"post_history": [],
"posting": {
"account_auths": [],
"key_auths": [
[
"STM7N4TaktJpumgXobB2t2ofthdpG1umy35KAi35rv7SPHz73R1cr",
1
]
],
"weight_threshold": 1
},
"posting_json_metadata": "{\"profile\":{\"name\":\"Thomas\",\"about\":\"Computer Scientist, software architect, Java programmer, mainframe specialist, project manager\",\"location\":\"Munich, Germany\",\"cover_image\":\"https://steemitimages.com/0x0/http://i.imgur.com/wHMAhxy.jpg\",\"profile_image\":\"https://cdn.steemitimages.com/DQmYcL4i2C3q5yqGH6avREovheJvHzkjF2ibkaELQyqPDAR/P1080321.JPG\"}}",
"posting_rewards": 1273,
"proxied_vsf_votes": [
0,
0,
0,
0
],
"proxy": "",
"received_vesting_shares": "0.000000 VESTS",
"recovery_account": "steem",
"reputation": "18534464147",
"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.001 SBD",
"sbd_last_interest_payment": "1970-01-01T00:00:00",
"sbd_seconds": "0",
"sbd_seconds_last_update": "2020-03-07T07:43:12",
"tags_usage": [],
"to_withdraw": 0,
"transfer_history": [],
"vesting_balance": "0.000 STEEM",
"vesting_shares": "84723.693953 VESTS",
"vesting_withdraw_rate": "0.000000 VESTS",
"vote_history": [],
"voting_manabar": {
"current_mana": "83029220073",
"last_update_time": 1649828742
},
"voting_power": 9799,
"withdraw_routes": 0,
"withdrawn": 0,
"witness_votes": [],
"witnesses_voted_for": 0,
"rank": 33421
}Withdraw Routes
| Incoming | Outgoing |
|---|---|
Empty | Empty |
{
"incoming": [],
"outgoing": []
}From Date
To Date
ph-supportsent 0.001 STEEM to @thomasoss2022/08/17 15:38:00
ph-supportsent 0.001 STEEM to @thomasoss
2022/08/17 15:38:00
| amount | 0.001 STEEM |
| from | ph-support |
| memo | |
| to | thomasoss |
| Transaction Info | Block #66885484/Trx 932604d8c8d916be58af3381af1a8ec56f35e004 |
View Raw JSON Data
{
"block": 66885484,
"op": [
"transfer",
{
"amount": "0.001 STEEM",
"from": "ph-support",
"memo": "",
"to": "thomasoss"
}
],
"op_in_trx": 0,
"timestamp": "2022-08-17T15:38:00",
"trx_id": "932604d8c8d916be58af3381af1a8ec56f35e004",
"trx_in_block": 0,
"virtual_op": 0
}thomasossupvoted (100.00%) @mintymile / rajiuc2022/05/22 14:44:21
thomasossupvoted (100.00%) @mintymile / rajiuc
2022/05/22 14:44:21
| author | mintymile |
| permlink | rajiuc |
| voter | thomasoss |
| weight | 10000 (100.00%) |
| Transaction Info | Block #64393802/Trx cc02017b952e3be57103f5818b509947a61b0e55 |
View Raw JSON Data
{
"block": 64393802,
"op": [
"vote",
{
"author": "mintymile",
"permlink": "rajiuc",
"voter": "thomasoss",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2022-05-22T14:44:21",
"trx_id": "cc02017b952e3be57103f5818b509947a61b0e55",
"trx_in_block": 1,
"virtual_op": 0
}mintymilereplied to @thomasoss / rajiuc2022/04/18 14:56:36
mintymilereplied to @thomasoss / rajiuc
2022/04/18 14:56:36
| author | mintymile |
| body | @thomasoss, I did not know all this, thanks for the clarifiation. ALthough I have to understand what you explained again much better, to comment on t=it. Thankyou for reading and this insightful detail!! |
| json metadata | {"users":["thomasoss"],"app":"steemit/0.2"} |
| parent author | thomasoss |
| parent permlink | ra9jwr |
| permlink | rajiuc |
| title | |
| Transaction Info | Block #63419782/Trx 6ed9e9d29dd71dcd08a90bab3c0d350338dd5a1d |
View Raw JSON Data
{
"block": 63419782,
"op": [
"comment",
{
"author": "mintymile",
"body": "@thomasoss, I did not know all this, thanks for the clarifiation. ALthough I have to understand what you explained again much better, to comment on t=it.\n\nThankyou for reading and this insightful detail!!",
"json_metadata": "{\"users\":[\"thomasoss\"],\"app\":\"steemit/0.2\"}",
"parent_author": "thomasoss",
"parent_permlink": "ra9jwr",
"permlink": "rajiuc",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2022-04-18T14:56:36",
"trx_id": "6ed9e9d29dd71dcd08a90bab3c0d350338dd5a1d",
"trx_in_block": 6,
"virtual_op": 0
}mintymileupvoted (100.00%) @thomasoss / ra9jwr2022/04/18 14:53:33
mintymileupvoted (100.00%) @thomasoss / ra9jwr
2022/04/18 14:53:33
| author | thomasoss |
| permlink | ra9jwr |
| voter | mintymile |
| weight | 10000 (100.00%) |
| Transaction Info | Block #63419721/Trx cf347028868146f3ee8f263768692a24c28a3485 |
View Raw JSON Data
{
"block": 63419721,
"op": [
"vote",
{
"author": "thomasoss",
"permlink": "ra9jwr",
"voter": "mintymile",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2022-04-18T14:53:33",
"trx_id": "cf347028868146f3ee8f263768692a24c28a3485",
"trx_in_block": 5,
"virtual_op": 0
}thomasosscustom json: notify2022/04/14 09:27:57
thomasosscustom json: notify
2022/04/14 09:27:57
| id | notify |
| json | ["setLastRead",{"date":"2022-04-14T09:27:56"}] |
| required auths | [] |
| required posting auths | ["thomasoss"] |
| Transaction Info | Block #63298486/Trx 434c00a388e613552dbe23546de67df0a05f844b |
View Raw JSON Data
{
"block": 63298486,
"op": [
"custom_json",
{
"id": "notify",
"json": "[\"setLastRead\",{\"date\":\"2022-04-14T09:27:56\"}]",
"required_auths": [],
"required_posting_auths": [
"thomasoss"
]
}
],
"op_in_trx": 0,
"timestamp": "2022-04-14T09:27:57",
"trx_id": "434c00a388e613552dbe23546de67df0a05f844b",
"trx_in_block": 2,
"virtual_op": 0
}thomasossreplied to @mintymile / ra9jwr2022/04/14 09:27:27
thomasossreplied to @mintymile / ra9jwr
2022/04/14 09:27:27
| author | thomasoss |
| body | @@ -657,10 +657,10 @@ in I -F P +F S or |
| json metadata | {"app":"steemit/0.2"} |
| parent author | mintymile |
| parent permlink | nfts-can-empower-journalism-to-stay-independent-free-from-government-s-coercion |
| permlink | ra9jwr |
| title | |
| Transaction Info | Block #63298476/Trx b51c08007daac770b53d5ff80a66684bb85d6e27 |
View Raw JSON Data
{
"block": 63298476,
"op": [
"comment",
{
"author": "thomasoss",
"body": "@@ -657,10 +657,10 @@\n in I\n-F\n P\n+F\n S or\n",
"json_metadata": "{\"app\":\"steemit/0.2\"}",
"parent_author": "mintymile",
"parent_permlink": "nfts-can-empower-journalism-to-stay-independent-free-from-government-s-coercion",
"permlink": "ra9jwr",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2022-04-14T09:27:27",
"trx_id": "b51c08007daac770b53d5ff80a66684bb85d6e27",
"trx_in_block": 0,
"virtual_op": 0
}2022/04/13 05:45:42
2022/04/13 05:45:42
| author | mintymile |
| permlink | nfts-can-empower-journalism-to-stay-independent-free-from-government-s-coercion |
| voter | thomasoss |
| weight | 10000 (100.00%) |
| Transaction Info | Block #63265372/Trx 7f5f6eb4595b51b63243ed8224ce9ccf695e3ed9 |
View Raw JSON Data
{
"block": 63265372,
"op": [
"vote",
{
"author": "mintymile",
"permlink": "nfts-can-empower-journalism-to-stay-independent-free-from-government-s-coercion",
"voter": "thomasoss",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2022-04-13T05:45:42",
"trx_id": "7f5f6eb4595b51b63243ed8224ce9ccf695e3ed9",
"trx_in_block": 3,
"virtual_op": 0
}thomasossreplied to @mintymile / ra9jwr2022/04/13 05:45:06
thomasossreplied to @mintymile / ra9jwr
2022/04/13 05:45:06
| author | thomasoss |
| body | @@ -795,17 +795,17 @@ he minin -t +g of the |
| json metadata | {"app":"steemit/0.2"} |
| parent author | mintymile |
| parent permlink | nfts-can-empower-journalism-to-stay-independent-free-from-government-s-coercion |
| permlink | ra9jwr |
| title | |
| Transaction Info | Block #63265360/Trx e95d865adc6fff6ed9eaa02f6dd00cdf31c156d7 |
View Raw JSON Data
{
"block": 63265360,
"op": [
"comment",
{
"author": "thomasoss",
"body": "@@ -795,17 +795,17 @@\n he minin\n-t\n+g\n of the \n",
"json_metadata": "{\"app\":\"steemit/0.2\"}",
"parent_author": "mintymile",
"parent_permlink": "nfts-can-empower-journalism-to-stay-independent-free-from-government-s-coercion",
"permlink": "ra9jwr",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2022-04-13T05:45:06",
"trx_id": "e95d865adc6fff6ed9eaa02f6dd00cdf31c156d7",
"trx_in_block": 5,
"virtual_op": 0
}executive-boardsent 0.001 STEEM to @thomasoss- "❗ Hello thomasoss, great that you are using the STEEM blockchain. The Executive Board is publishing insider infos at https://discord.gg/KyBbmhh on how you will be earning the most coins. It's easy, ju..."2022/04/13 05:45:06
executive-boardsent 0.001 STEEM to @thomasoss- "❗ Hello thomasoss, great that you are using the STEEM blockchain. The Executive Board is publishing insider infos at https://discord.gg/KyBbmhh on how you will be earning the most coins. It's easy, ju..."
2022/04/13 05:45:06
| amount | 0.001 STEEM |
| from | executive-board |
| memo | ❗ Hello thomasoss, great that you are using the STEEM blockchain. The Executive Board is publishing insider infos at https://discord.gg/KyBbmhh on how you will be earning the most coins. It's easy, just follow the instructions. THE 1000X BOOSTER KEY is already waiting for you over there too. 😉 Warm regards, The Executive Board. |
| to | thomasoss |
| Transaction Info | Block #63265360/Trx 4b37ff589969016004e46c9786856349dba14ef9 |
View Raw JSON Data
{
"block": 63265360,
"op": [
"transfer",
{
"amount": "0.001 STEEM",
"from": "executive-board",
"memo": "❗ Hello thomasoss, great that you are using the STEEM blockchain. The Executive Board is publishing insider infos at https://discord.gg/KyBbmhh on how you will be earning the most coins. It's easy, just follow the instructions. THE 1000X BOOSTER KEY is already waiting for you over there too. 😉 Warm regards, The Executive Board.",
"to": "thomasoss"
}
],
"op_in_trx": 0,
"timestamp": "2022-04-13T05:45:06",
"trx_id": "4b37ff589969016004e46c9786856349dba14ef9",
"trx_in_block": 1,
"virtual_op": 0
}thomasossreplied to @mintymile / ra9jwr2022/04/13 05:44:33
thomasossreplied to @mintymile / ra9jwr
2022/04/13 05:44:33
| author | thomasoss |
| body | @@ -568,17 +568,17 @@ thing is -. +: The dig |
| json metadata | {"app":"steemit/0.2"} |
| parent author | mintymile |
| parent permlink | nfts-can-empower-journalism-to-stay-independent-free-from-government-s-coercion |
| permlink | ra9jwr |
| title | |
| Transaction Info | Block #63265349/Trx 4e3a163561524f3251c27fda047f25e63bccc5ae |
View Raw JSON Data
{
"block": 63265349,
"op": [
"comment",
{
"author": "thomasoss",
"body": "@@ -568,17 +568,17 @@\n thing is\n-.\n+:\n The dig\n",
"json_metadata": "{\"app\":\"steemit/0.2\"}",
"parent_author": "mintymile",
"parent_permlink": "nfts-can-empower-journalism-to-stay-independent-free-from-government-s-coercion",
"permlink": "ra9jwr",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2022-04-13T05:44:33",
"trx_id": "4e3a163561524f3251c27fda047f25e63bccc5ae",
"trx_in_block": 0,
"virtual_op": 0
}thomasossreplied to @mintymile / ra9jwr2022/04/13 05:43:42
thomasossreplied to @mintymile / ra9jwr
2022/04/13 05:43:42
| author | thomasoss |
| body | Hello, good article. I like it ;-) But one remark. You wrote " Obviously, as these NFTs will be stored in Blockchain, it’s immutable and will exist to be viewed by the public forever." This is not the full truth. You cannot store all the material on the blockchain. For example to burn a picture into a NFT you take the hash value of the image an burn it into the NFT. This way you can proove that the image existed at the point of time the NFT was created. You could even take an image and an addtional description und take the hash value representing both. But the thing is. The digital asset you took the hash from must be stored somewhere. For example in IFPS or on some server or on some optical medium. The blockchain helps to proove that the digital asset existed at the point of time the minint of the NFT happend. But the blockchain cannot guarantee that the picture is still accessable or even exists in 10, 20 or more years. |
| json metadata | {"app":"steemit/0.2"} |
| parent author | mintymile |
| parent permlink | nfts-can-empower-journalism-to-stay-independent-free-from-government-s-coercion |
| permlink | ra9jwr |
| title | |
| Transaction Info | Block #63265332/Trx 38dc7ef6def00d56e489ee4ffbd84a62627d2b7b |
View Raw JSON Data
{
"block": 63265332,
"op": [
"comment",
{
"author": "thomasoss",
"body": "Hello, good article. I like it ;-) But one remark. You wrote \" Obviously, as these NFTs will be stored in Blockchain, it’s immutable and will exist to be viewed by the public forever.\" This is not the full truth. You cannot store all the material on the blockchain. For example to burn a picture into a NFT you take the hash value of the image an burn it into the NFT. This way you can proove that the image existed at the point of time the NFT was created. You could even take an image and an addtional description und take the hash value representing both. But the thing is. The digital asset you took the hash from must be stored somewhere. For example in IFPS or on some server or on some optical medium. The blockchain helps to proove that the digital asset existed at the point of time the minint of the NFT happend. But the blockchain cannot guarantee that the picture is still accessable or even exists in 10, 20 or more years.",
"json_metadata": "{\"app\":\"steemit/0.2\"}",
"parent_author": "mintymile",
"parent_permlink": "nfts-can-empower-journalism-to-stay-independent-free-from-government-s-coercion",
"permlink": "ra9jwr",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2022-04-13T05:43:42",
"trx_id": "38dc7ef6def00d56e489ee4ffbd84a62627d2b7b",
"trx_in_block": 0,
"virtual_op": 0
}thomasosscustom json: community2022/04/13 05:30:48
thomasosscustom json: community
2022/04/13 05:30:48
| id | community |
| json | ["subscribe",{"community":"hive-108451"}] |
| required auths | [] |
| required posting auths | ["thomasoss"] |
| Transaction Info | Block #63265077/Trx 530fda55cee692c925afadae8550414ea33063e1 |
View Raw JSON Data
{
"block": 63265077,
"op": [
"custom_json",
{
"id": "community",
"json": "[\"subscribe\",{\"community\":\"hive-108451\"}]",
"required_auths": [],
"required_posting_auths": [
"thomasoss"
]
}
],
"op_in_trx": 0,
"timestamp": "2022-04-13T05:30:48",
"trx_id": "530fda55cee692c925afadae8550414ea33063e1",
"trx_in_block": 7,
"virtual_op": 0
}thomasosscustom json: community2020/08/31 11:27:24
thomasosscustom json: community
2020/08/31 11:27:24
| id | community |
| json | ["subscribe",{"community":"hive-184714"}] |
| required auths | [] |
| required posting auths | ["thomasoss"] |
| Transaction Info | Block #46463105/Trx 9b9a4addcf248fc80763ca170b8dfb12ff3abf44 |
View Raw JSON Data
{
"block": 46463105,
"op": [
"custom_json",
{
"id": "community",
"json": "[\"subscribe\",{\"community\":\"hive-184714\"}]",
"required_auths": [],
"required_posting_auths": [
"thomasoss"
]
}
],
"op_in_trx": 0,
"timestamp": "2020-08-31T11:27:24",
"trx_id": "9b9a4addcf248fc80763ca170b8dfb12ff3abf44",
"trx_in_block": 7,
"virtual_op": 0
}thomasossupvoted (100.00%) @profitgenerator / what-is-the-rewards2020/03/08 08:48:57
thomasossupvoted (100.00%) @profitgenerator / what-is-the-rewards
2020/03/08 08:48:57
| author | profitgenerator |
| permlink | what-is-the-rewards |
| voter | thomasoss |
| weight | 10000 (100.00%) |
| Transaction Info | Block #41467552/Trx e09d63eae054dfe55e0ad8e1267d87c22b1a6a9e |
View Raw JSON Data
{
"block": 41467552,
"op": [
"vote",
{
"author": "profitgenerator",
"permlink": "what-is-the-rewards",
"voter": "thomasoss",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2020-03-08T08:48:57",
"trx_id": "e09d63eae054dfe55e0ad8e1267d87c22b1a6a9e",
"trx_in_block": 3,
"virtual_op": 0
}thomasossupvoted (100.00%) @steemitboard / steemitboard-notify-thomasoss-20200115t175951000z2020/03/07 08:03:57
thomasossupvoted (100.00%) @steemitboard / steemitboard-notify-thomasoss-20200115t175951000z
2020/03/07 08:03:57
| author | steemitboard |
| permlink | steemitboard-notify-thomasoss-20200115t175951000z |
| voter | thomasoss |
| weight | 10000 (100.00%) |
| Transaction Info | Block #41437922/Trx 1af864679c62c2967842fede258cbed711599255 |
View Raw JSON Data
{
"block": 41437922,
"op": [
"vote",
{
"author": "steemitboard",
"permlink": "steemitboard-notify-thomasoss-20200115t175951000z",
"voter": "thomasoss",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2020-03-07T08:03:57",
"trx_id": "1af864679c62c2967842fede258cbed711599255",
"trx_in_block": 0,
"virtual_op": 0
}thomasossclaimed reward balance: 0.630 STEEM, 0.001 SBD, 0.780 SP2020/03/07 07:43:12
thomasossclaimed reward balance: 0.630 STEEM, 0.001 SBD, 0.780 SP
2020/03/07 07:43:12
| account | thomasoss |
| reward sbd | 0.001 SBD |
| reward steem | 0.630 STEEM |
| reward vests | 1268.827968 VESTS |
| Transaction Info | Block #41437509/Trx a0106da9415eee5af33d93f3622815a59b8b0521 |
View Raw JSON Data
{
"block": 41437509,
"op": [
"claim_reward_balance",
{
"account": "thomasoss",
"reward_sbd": "0.001 SBD",
"reward_steem": "0.630 STEEM",
"reward_vests": "1268.827968 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2020-03-07T07:43:12",
"trx_id": "a0106da9415eee5af33d93f3622815a59b8b0521",
"trx_in_block": 19,
"virtual_op": 0
}2020/03/07 07:39:24
2020/03/07 07:39:24
| author | thomasoss |
| permlink | blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture |
| voter | anomaly |
| weight | 100 (1.00%) |
| Transaction Info | Block #41437433/Trx c3d24992d6b37faddc5950847d9cb4880954acfa |
View Raw JSON Data
{
"block": 41437433,
"op": [
"vote",
{
"author": "thomasoss",
"permlink": "blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture",
"voter": "anomaly",
"weight": 100
}
],
"op_in_trx": 0,
"timestamp": "2020-03-07T07:39:24",
"trx_id": "c3d24992d6b37faddc5950847d9cb4880954acfa",
"trx_in_block": 19,
"virtual_op": 0
}2020/03/07 07:38:33
2020/03/07 07:38:33
| author | thomasoss |
| body | @@ -1446,16 +1446,159 @@ gnature) +%0A- %5BPart 8: Seed (Random Seed) and HD Wallet%5D(https://steemit.com/seed/@thomasoss/blockchain-foundations-part-7-seed-random-seed-and-hd-wallet) %0A%0AThe ne |
| json metadata | {"tags":["centralized","decentralized","distributed","architecture"],"image":["https://cdn.steemitimages.com/DQmekyCqN6aKDZTeZF1f8LeWdd8U7jXNUn4KbRgnfCHHzat/image.png","https://cdn.steemitimages.com/DQmZyts7uG8WFYFrFosC6igcPkNtUK4Rphv7jktj1WhKk4x/image.png","https://cdn.steemitimages.com/DQmWs3aueu5cwZECx7hugNQRgur1ctXWjbHJsMXeFvyGkt3/image.png"],"app":"steemit/0.2","format":"markdown","links":["https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-2-peer-to-peer-architecture-and-hybrid-computer-system-architecture","https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-5-1-5-how-the-architecture-affects-the-internet-user","https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-4-hash-function","https://steemit.com/merkle/@thomasoss/blockchain-foundations-part-5-merkle-tree-and-merkle-root","https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-6-radix-tree-patricia-trie","https://steemit.com/ecdsa/@thomasoss/blockchain-foundations-part-7-encryption-and-digital-signature","https://steemit.com/seed/@thomasoss/blockchain-foundations-part-7-seed-random-seed-and-hd-wallet"]} |
| parent author | |
| parent permlink | blockchain |
| permlink | blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture |
| title | Blockchain Foundations Part 1: Distributed, Decentralized and Centralized Computer Architecture |
| Transaction Info | Block #41437416/Trx 82fb786fed66901a52077538dc8bac7278b089b9 |
View Raw JSON Data
{
"block": 41437416,
"op": [
"comment",
{
"author": "thomasoss",
"body": "@@ -1446,16 +1446,159 @@\n gnature)\n+%0A- %5BPart 8: Seed (Random Seed) and HD Wallet%5D(https://steemit.com/seed/@thomasoss/blockchain-foundations-part-7-seed-random-seed-and-hd-wallet)\n %0A%0AThe ne\n",
"json_metadata": "{\"tags\":[\"centralized\",\"decentralized\",\"distributed\",\"architecture\"],\"image\":[\"https://cdn.steemitimages.com/DQmekyCqN6aKDZTeZF1f8LeWdd8U7jXNUn4KbRgnfCHHzat/image.png\",\"https://cdn.steemitimages.com/DQmZyts7uG8WFYFrFosC6igcPkNtUK4Rphv7jktj1WhKk4x/image.png\",\"https://cdn.steemitimages.com/DQmWs3aueu5cwZECx7hugNQRgur1ctXWjbHJsMXeFvyGkt3/image.png\"],\"app\":\"steemit/0.2\",\"format\":\"markdown\",\"links\":[\"https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-2-peer-to-peer-architecture-and-hybrid-computer-system-architecture\",\"https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-5-1-5-how-the-architecture-affects-the-internet-user\",\"https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-4-hash-function\",\"https://steemit.com/merkle/@thomasoss/blockchain-foundations-part-5-merkle-tree-and-merkle-root\",\"https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-6-radix-tree-patricia-trie\",\"https://steemit.com/ecdsa/@thomasoss/blockchain-foundations-part-7-encryption-and-digital-signature\",\"https://steemit.com/seed/@thomasoss/blockchain-foundations-part-7-seed-random-seed-and-hd-wallet\"]}",
"parent_author": "",
"parent_permlink": "blockchain",
"permlink": "blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture",
"title": "Blockchain Foundations Part 1: Distributed, Decentralized and Centralized Computer Architecture"
}
],
"op_in_trx": 0,
"timestamp": "2020-03-07T07:38:33",
"trx_id": "82fb786fed66901a52077538dc8bac7278b089b9",
"trx_in_block": 15,
"virtual_op": 0
}laissez-faireupvoted (100.00%) @thomasoss / blockchain-foundations-part-7-seed-random-seed-and-hd-wallet2020/03/07 07:37:09
laissez-faireupvoted (100.00%) @thomasoss / blockchain-foundations-part-7-seed-random-seed-and-hd-wallet
2020/03/07 07:37:09
| author | thomasoss |
| permlink | blockchain-foundations-part-7-seed-random-seed-and-hd-wallet |
| voter | laissez-faire |
| weight | 10000 (100.00%) |
| Transaction Info | Block #41437388/Trx c7183a6d35cc2be144da0d18e4f410397d3ec9ee |
View Raw JSON Data
{
"block": 41437388,
"op": [
"vote",
{
"author": "thomasoss",
"permlink": "blockchain-foundations-part-7-seed-random-seed-and-hd-wallet",
"voter": "laissez-faire",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2020-03-07T07:37:09",
"trx_id": "c7183a6d35cc2be144da0d18e4f410397d3ec9ee",
"trx_in_block": 1,
"virtual_op": 0
}2020/03/07 07:37:03
2020/03/07 07:37:03
| author | thomasoss |
| permlink | blockchain-foundations-part-7-seed-random-seed-and-hd-wallet |
| voter | anomaly |
| weight | 100 (1.00%) |
| Transaction Info | Block #41437386/Trx 060e441f7bf65b2a45d11b48c9c3334c0107f25c |
View Raw JSON Data
{
"block": 41437386,
"op": [
"vote",
{
"author": "thomasoss",
"permlink": "blockchain-foundations-part-7-seed-random-seed-and-hd-wallet",
"voter": "anomaly",
"weight": 100
}
],
"op_in_trx": 0,
"timestamp": "2020-03-07T07:37:03",
"trx_id": "060e441f7bf65b2a45d11b48c9c3334c0107f25c",
"trx_in_block": 6,
"virtual_op": 0
}beemenginesent 0.001 STEEM to @thomasoss- "💎 Awesome Community Offer: auto booster with 10x extra votes, passive curation earnings and more. Checkout https://www.steembeem.com 🤙 or try it for one month with ONLY 1 STEEM 🤯 to @beemengine wit..."2020/03/07 07:37:03
beemenginesent 0.001 STEEM to @thomasoss- "💎 Awesome Community Offer: auto booster with 10x extra votes, passive curation earnings and more. Checkout https://www.steembeem.com 🤙 or try it for one month with ONLY 1 STEEM 🤯 to @beemengine wit..."
2020/03/07 07:37:03
| amount | 0.001 STEEM |
| from | beemengine |
| memo | 💎 Awesome Community Offer: auto booster with 10x extra votes, passive curation earnings and more. Checkout https://www.steembeem.com 🤙 or try it for one month with ONLY 1 STEEM 🤯 to @beemengine with memo: subscribe |
| to | thomasoss |
| Transaction Info | Block #41437386/Trx ceeeff4b0cb4b217fb1a8ffc4ca5e4d3885fe893 |
View Raw JSON Data
{
"block": 41437386,
"op": [
"transfer",
{
"amount": "0.001 STEEM",
"from": "beemengine",
"memo": "💎 Awesome Community Offer: auto booster with 10x extra votes, passive curation earnings and more. Checkout https://www.steembeem.com 🤙 or try it for one month with ONLY 1 STEEM 🤯 to @beemengine with memo: subscribe",
"to": "thomasoss"
}
],
"op_in_trx": 0,
"timestamp": "2020-03-07T07:37:03",
"trx_id": "ceeeff4b0cb4b217fb1a8ffc4ca5e4d3885fe893",
"trx_in_block": 1,
"virtual_op": 0
}thomasosspublished a new post: blockchain-foundations-part-7-seed-random-seed-and-hd-wallet2020/03/07 07:36:21
thomasosspublished a new post: blockchain-foundations-part-7-seed-random-seed-and-hd-wallet
2020/03/07 07:36:21
| author | thomasoss |
| body | This article is about seeds. A seed can help you organizing the great number of public/privat key pairs you may need. The article is part of a series starting with this article: [Blockchain Foundations Part 1: Distributed, Decentralized and Centralized Computer Architecture](https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture) The articles are drawn from my book "Blockchain and Crypto Currencies Easy to Understand for Everyone, Thomas Bauer". Please refer to the [part 1 article](https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture) for a introduction to the blockchain foundations series. # Seed When using crypto currencies, then we quickly need to deal with a growing number of public/private key pairs. With a seed (random seed) we can avoid remembering all the used key pairs. A seed is a character string, for example: "a90dcxvuw34df74cxl246o345qweratwemzesdfseszdfw332843sfmsacx" Nobody can keep in mind such a character string. Hence we use a mnemonic like: "dog cat elephant first ape third Jim horse salamander ninth mouse rat" From such a mnemonic we derive a seed. For example, by calculating a hash value from this character string. Now we have a seed. We use this seed and an additional number, let's take "1", as base number when creating a key pair. Another key pair we create bases on the seed and the number "2". And so on. This way we could, for example, create 100 key pairs. We do not need to remember the created key pairs. Neither the public nor the private keys. Both we can recreate from the seed and the numbers 1 to 100. And the seed we can derive from the mnemonic. We only need to remember the mnemonic. Instead of simply incrementing a number in practice some more complicate algorithm are used. For example, we could derive some number or string from the aimed intended use of the key pair. This result and the seed and maybe again incrementing numbers lead to our key pairs. Sometime this procedure is called a derivation path. The application of a seed is described in the next chapter. # HD Wallet A HD wallet (hierarchical deterministic wallet) is not really a wallet but a technique to be used together with one of the different forms of wallets. With a HD wallet we can create key pairs based on a seed phrase. These key pairs we then use to receive cryptocurrency. Example: If we want to receive Bitcoins using the Bitcoin Core wallet we must create a new pair of public address and private key each time. The public address we tell the sender of the Bitcoins. We should make a backup of the private key instantly. We also could generate 100 pairs of public addresses and private keys at once. These we could use sequentially. Then we only need to make a backup of the keys after generating the 100 keys. But we still have to backup every used key. With a HD wallet this is easier. A HD wallet generates the keys for us. And we do not need to memorize or note all private keys. We only need to memorize a seed phrase. From this seed phrase the HD wallet generates the private keys. The needed private keys we can import in our wallet. A HD wallet usually is a hardware wallet. |
| json metadata | {"tags":["hd","wallet","privat","key","blockchain"],"links":["https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture"],"app":"steemit/0.2","format":"markdown"} |
| parent author | |
| parent permlink | seed |
| permlink | blockchain-foundations-part-7-seed-random-seed-and-hd-wallet |
| title | Blockchain Foundations Part 8: Seed (Random Seed) and HD Wallet |
| Transaction Info | Block #41437372/Trx 77fcac309d47cd9d8ff26160926e08760548e63f |
View Raw JSON Data
{
"block": 41437372,
"op": [
"comment",
{
"author": "thomasoss",
"body": "This article is about seeds. A seed can help you organizing the great number of public/privat key pairs you may need.\n\nThe article is part of a series starting with this article: [Blockchain Foundations Part 1: Distributed, Decentralized and Centralized Computer Architecture](https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture)\n\nThe articles are drawn from my book \"Blockchain and Crypto Currencies Easy to Understand for Everyone, Thomas Bauer\". Please refer to the [part 1 article](https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture) for a introduction to the blockchain foundations series.\n\n# Seed\n\nWhen using crypto currencies, then we quickly need to deal with a growing number of public/private key pairs. With a seed (random seed) we can avoid remembering all the used key pairs. \n\nA seed is a character string, for example:\n\"a90dcxvuw34df74cxl246o345qweratwemzesdfseszdfw332843sfmsacx\"\n\nNobody can keep in mind such a character string. Hence we use a mnemonic like:\n\"dog cat elephant first ape third Jim horse salamander ninth mouse rat\"\n\nFrom such a mnemonic we derive a seed. For example, by calculating a hash value from this character string. \n\nNow we have a seed. We use this seed and an additional number, let's take \"1\", as base number when creating a key pair. Another key pair we create bases on the seed and the number \"2\". And so on. This way we could, for example, create 100 key pairs. We do not need to remember the created key pairs. Neither the public nor the private keys. Both we can recreate from the seed and the numbers 1 to 100. And the seed we can derive from the mnemonic. We only need to remember the mnemonic.\n\nInstead of simply incrementing a number in practice some more complicate algorithm are used. For example, we could derive some number or string from the aimed intended use of the key pair. This result and the seed and maybe again incrementing numbers lead to our key pairs. Sometime this procedure is called a derivation path.\n\nThe application of a seed is described in the next chapter.\n\n# HD Wallet\n\nA HD wallet (hierarchical deterministic wallet) is not really a wallet but a technique to be used together with one of the different forms of wallets. With a HD wallet we can create key pairs based on a seed phrase. These key pairs we then use to receive cryptocurrency. \n\nExample: If we want to receive Bitcoins using the Bitcoin Core wallet we must create a new pair of public address and private key each time. The public address we tell the sender of the Bitcoins. We should make a backup of the private key instantly. We also could generate 100 pairs of public addresses and private keys at once. These we could use sequentially. Then we only need to make a backup of the keys after generating the 100 keys. But we still have to backup every used key. \n\nWith a HD wallet this is easier. A HD wallet generates the keys for us. And we do not need to memorize or note all private keys. We only need to memorize a seed phrase. From this seed phrase the HD wallet generates the private keys. The needed private keys we can import in our wallet. \n\nA HD wallet usually is a hardware wallet.",
"json_metadata": "{\"tags\":[\"hd\",\"wallet\",\"privat\",\"key\",\"blockchain\"],\"links\":[\"https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture\"],\"app\":\"steemit/0.2\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "seed",
"permlink": "blockchain-foundations-part-7-seed-random-seed-and-hd-wallet",
"title": "Blockchain Foundations Part 8: Seed (Random Seed) and HD Wallet"
}
],
"op_in_trx": 0,
"timestamp": "2020-03-07T07:36:21",
"trx_id": "77fcac309d47cd9d8ff26160926e08760548e63f",
"trx_in_block": 10,
"virtual_op": 0
}thomasosspublished a new post: blockchain-foundations-part-7-seed-random-seed-and-hd-wallet2020/03/07 07:35:51
thomasosspublished a new post: blockchain-foundations-part-7-seed-random-seed-and-hd-wallet
2020/03/07 07:35:51
| author | thomasoss |
| body | This article is about seeds. A seed can help you organizing the great number of public/privat key pairs you may need. The article is part of a series starting with this article: [Blockchain Foundations Part 1: Distributed, Decentralized and Centralized Computer Architecture](https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture) The articles are drawn from my book "Blockchain and Crypto Currencies Easy to Understand for Everyone, Thomas Bauer". Please refer to the [part 1 article](https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture) for a introduction to the blockchain foundations series. # Seed When using crypto currencies, then we quickly need to deal with a growing number of public/private key pairs. With a seed (random seed) we can avoid remembering all the used key pairs. A seed is a character string, for example: "a90dcxvuw34df74cxl246o345qweratwemzesdfseszdfw332843sfmsacx" Nobody can keep in mind such a character string. Hence we use a mnemonic like: "dog cat elephant first ape third Jim horse salamander ninth mouse rat" From such a mnemonic we derive a seed. For example, by calculating a hash value from this character string. Now we have a seed. We use this seed and an additional number, let's take "1", as base number when creating a key pair. Another key pair we create bases on the seed and the number "2". And so on. This way we could, for example, create 100 key pairs. We do not need to remember the created key pairs. Neither the public nor the private keys. Both we can recreate from the seed and the numbers 1 to 100. And the seed we can derive from the mnemonic. We only need to remember the mnemonic. Instead of simply incrementing a number in practice some more complicate algorithm are used. For example, we could derive some number or string from the aimed intended use of the key pair. This result and the seed and maybe again incrementing numbers lead to our key pairs. Sometime this procedure is called a derivation path. The application of a seed is described in the next chapter. # HD Wallet A HD wallet (hierarchical deterministic wallet) is not really a wallet but a technique to be used together with one of the different forms of wallets. With a HD wallet we can create key pairs based on a seed phrase. These key pairs we then use to receive cryptocurrency. Example: If we want to receive Bitcoins using the Bitcoin Core wallet we must create a new pair of public address and private key each time. The public address we tell the sender of the Bitcoins. We should make a backup of the private key instantly. We also could generate 100 pairs of public addresses and private keys at once. These we could use sequentially. Then we only need to make a backup of the keys after generating the 100 keys. But we still have to backup every used key. With a HD wallet this is easier. A HD wallet generates the keys for us. And we do not need to memorize or note all private keys. We only need to memorize a seed phrase. From this seed phrase the HD wallet generates the private keys. The needed private keys we can import in our wallet. A HD wallet usually is a hardware wallet. |
| json metadata | {"tags":["seed","hd","wallet","privat","key","blockchain"],"links":["https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture"],"app":"steemit/0.2","format":"markdown"} |
| parent author | |
| parent permlink | seed |
| permlink | blockchain-foundations-part-7-seed-random-seed-and-hd-wallet |
| title | Blockchain Foundations Part 7: Seed (Random Seed) and HD Wallet |
| Transaction Info | Block #41437362/Trx 33040a14974b6f151422d1dc0574fd374ebdacb8 |
View Raw JSON Data
{
"block": 41437362,
"op": [
"comment",
{
"author": "thomasoss",
"body": "This article is about seeds. A seed can help you organizing the great number of public/privat key pairs you may need.\n\nThe article is part of a series starting with this article: [Blockchain Foundations Part 1: Distributed, Decentralized and Centralized Computer Architecture](https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture)\n\nThe articles are drawn from my book \"Blockchain and Crypto Currencies Easy to Understand for Everyone, Thomas Bauer\". Please refer to the [part 1 article](https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture) for a introduction to the blockchain foundations series.\n\n# Seed\n\nWhen using crypto currencies, then we quickly need to deal with a growing number of public/private key pairs. With a seed (random seed) we can avoid remembering all the used key pairs. \n\nA seed is a character string, for example:\n\"a90dcxvuw34df74cxl246o345qweratwemzesdfseszdfw332843sfmsacx\"\n\nNobody can keep in mind such a character string. Hence we use a mnemonic like:\n\"dog cat elephant first ape third Jim horse salamander ninth mouse rat\"\n\nFrom such a mnemonic we derive a seed. For example, by calculating a hash value from this character string. \n\nNow we have a seed. We use this seed and an additional number, let's take \"1\", as base number when creating a key pair. Another key pair we create bases on the seed and the number \"2\". And so on. This way we could, for example, create 100 key pairs. We do not need to remember the created key pairs. Neither the public nor the private keys. Both we can recreate from the seed and the numbers 1 to 100. And the seed we can derive from the mnemonic. We only need to remember the mnemonic.\n\nInstead of simply incrementing a number in practice some more complicate algorithm are used. For example, we could derive some number or string from the aimed intended use of the key pair. This result and the seed and maybe again incrementing numbers lead to our key pairs. Sometime this procedure is called a derivation path.\n\nThe application of a seed is described in the next chapter.\n\n# HD Wallet\n\nA HD wallet (hierarchical deterministic wallet) is not really a wallet but a technique to be used together with one of the different forms of wallets. With a HD wallet we can create key pairs based on a seed phrase. These key pairs we then use to receive cryptocurrency. \n\nExample: If we want to receive Bitcoins using the Bitcoin Core wallet we must create a new pair of public address and private key each time. The public address we tell the sender of the Bitcoins. We should make a backup of the private key instantly. We also could generate 100 pairs of public addresses and private keys at once. These we could use sequentially. Then we only need to make a backup of the keys after generating the 100 keys. But we still have to backup every used key. \n\nWith a HD wallet this is easier. A HD wallet generates the keys for us. And we do not need to memorize or note all private keys. We only need to memorize a seed phrase. From this seed phrase the HD wallet generates the private keys. The needed private keys we can import in our wallet. \n\nA HD wallet usually is a hardware wallet.",
"json_metadata": "{\"tags\":[\"seed\",\"hd\",\"wallet\",\"privat\",\"key\",\"blockchain\"],\"links\":[\"https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture\"],\"app\":\"steemit/0.2\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "seed",
"permlink": "blockchain-foundations-part-7-seed-random-seed-and-hd-wallet",
"title": "Blockchain Foundations Part 7: Seed (Random Seed) and HD Wallet"
}
],
"op_in_trx": 0,
"timestamp": "2020-03-07T07:35:51",
"trx_id": "33040a14974b6f151422d1dc0574fd374ebdacb8",
"trx_in_block": 11,
"virtual_op": 0
}2020/01/15 17:59:51
2020/01/15 17:59:51
| author | steemitboard |
| body | Congratulations @thomasoss! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@thomasoss/birthday3.png</td><td>Happy Birthday! - You are on the Steem blockchain for 3 years!</td></tr></table> <sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@thomasoss) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=thomasoss)_</sub> ###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| parent author | thomasoss |
| parent permlink | blockchain-foundations-part-7-encryption-and-digital-signature |
| permlink | steemitboard-notify-thomasoss-20200115t175951000z |
| title | |
| Transaction Info | Block #39956310/Trx 611a1322a6f6a546b22b1474b9baabaff72e0bd4 |
View Raw JSON Data
{
"block": 39956310,
"op": [
"comment",
{
"author": "steemitboard",
"body": "Congratulations @thomasoss! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@thomasoss/birthday3.png</td><td>Happy Birthday! - You are on the Steem blockchain for 3 years!</td></tr></table>\n\n<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@thomasoss) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=thomasoss)_</sub>\n\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}",
"parent_author": "thomasoss",
"parent_permlink": "blockchain-foundations-part-7-encryption-and-digital-signature",
"permlink": "steemitboard-notify-thomasoss-20200115t175951000z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2020-01-15T17:59:51",
"trx_id": "611a1322a6f6a546b22b1474b9baabaff72e0bd4",
"trx_in_block": 6,
"virtual_op": 0
}2019/12/07 07:05:15
2019/12/07 07:05:15
| author | thomasoss |
| body | @@ -1478,27 +1478,11 @@ ing -weekly or more ofte +soo n) w |
| json metadata | {"tags":["centralized","decentralized","distributed","architecture"],"image":["https://cdn.steemitimages.com/DQmekyCqN6aKDZTeZF1f8LeWdd8U7jXNUn4KbRgnfCHHzat/image.png","https://cdn.steemitimages.com/DQmZyts7uG8WFYFrFosC6igcPkNtUK4Rphv7jktj1WhKk4x/image.png","https://cdn.steemitimages.com/DQmWs3aueu5cwZECx7hugNQRgur1ctXWjbHJsMXeFvyGkt3/image.png"],"app":"steemit/0.1","format":"markdown","links":["https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-2-peer-to-peer-architecture-and-hybrid-computer-system-architecture","https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-5-1-5-how-the-architecture-affects-the-internet-user","https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-4-hash-function","https://steemit.com/merkle/@thomasoss/blockchain-foundations-part-5-merkle-tree-and-merkle-root","https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-6-radix-tree-patricia-trie","https://steemit.com/ecdsa/@thomasoss/blockchain-foundations-part-7-encryption-and-digital-signature"]} |
| parent author | |
| parent permlink | blockchain |
| permlink | blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture |
| title | Blockchain Foundations Part 1: Distributed, Decentralized and Centralized Computer Architecture |
| Transaction Info | Block #38822128/Trx 7a51b4ddc074881686dd196a14502afeffa9c92c |
View Raw JSON Data
{
"block": 38822128,
"op": [
"comment",
{
"author": "thomasoss",
"body": "@@ -1478,27 +1478,11 @@\n ing \n-weekly or more ofte\n+soo\n n) w\n",
"json_metadata": "{\"tags\":[\"centralized\",\"decentralized\",\"distributed\",\"architecture\"],\"image\":[\"https://cdn.steemitimages.com/DQmekyCqN6aKDZTeZF1f8LeWdd8U7jXNUn4KbRgnfCHHzat/image.png\",\"https://cdn.steemitimages.com/DQmZyts7uG8WFYFrFosC6igcPkNtUK4Rphv7jktj1WhKk4x/image.png\",\"https://cdn.steemitimages.com/DQmWs3aueu5cwZECx7hugNQRgur1ctXWjbHJsMXeFvyGkt3/image.png\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\",\"links\":[\"https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-2-peer-to-peer-architecture-and-hybrid-computer-system-architecture\",\"https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-5-1-5-how-the-architecture-affects-the-internet-user\",\"https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-4-hash-function\",\"https://steemit.com/merkle/@thomasoss/blockchain-foundations-part-5-merkle-tree-and-merkle-root\",\"https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-6-radix-tree-patricia-trie\",\"https://steemit.com/ecdsa/@thomasoss/blockchain-foundations-part-7-encryption-and-digital-signature\"]}",
"parent_author": "",
"parent_permlink": "blockchain",
"permlink": "blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture",
"title": "Blockchain Foundations Part 1: Distributed, Decentralized and Centralized Computer Architecture"
}
],
"op_in_trx": 0,
"timestamp": "2019-12-07T07:05:15",
"trx_id": "7a51b4ddc074881686dd196a14502afeffa9c92c",
"trx_in_block": 18,
"virtual_op": 0
}2019/12/07 07:05:12
2019/12/07 07:05:12
| author | thomasoss |
| permlink | blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture |
| voter | anomaly |
| weight | 100 (1.00%) |
| Transaction Info | Block #38822127/Trx c495bf0f3e289349db9bbe5c853d202e68bb2736 |
View Raw JSON Data
{
"block": 38822127,
"op": [
"vote",
{
"author": "thomasoss",
"permlink": "blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture",
"voter": "anomaly",
"weight": 100
}
],
"op_in_trx": 0,
"timestamp": "2019-12-07T07:05:12",
"trx_id": "c495bf0f3e289349db9bbe5c853d202e68bb2736",
"trx_in_block": 5,
"virtual_op": 0
}2019/12/07 07:04:18
2019/12/07 07:04:18
| author | thomasoss |
| body | @@ -1300,16 +1300,162 @@ ia-trie) +%0A- %5BPart 7: Encryption and Digital Signature%5D(https://steemit.com/ecdsa/@thomasoss/blockchain-foundations-part-7-encryption-and-digital-signature) %0A%0AThe ne @@ -1514,33 +1514,8 @@ out%0A -- Signature%0A- Encryption%0A - Bl |
| json metadata | {"tags":["centralized","decentralized","distributed","architecture"],"image":["https://cdn.steemitimages.com/DQmekyCqN6aKDZTeZF1f8LeWdd8U7jXNUn4KbRgnfCHHzat/image.png","https://cdn.steemitimages.com/DQmZyts7uG8WFYFrFosC6igcPkNtUK4Rphv7jktj1WhKk4x/image.png","https://cdn.steemitimages.com/DQmWs3aueu5cwZECx7hugNQRgur1ctXWjbHJsMXeFvyGkt3/image.png"],"app":"steemit/0.1","format":"markdown","links":["https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-2-peer-to-peer-architecture-and-hybrid-computer-system-architecture","https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-5-1-5-how-the-architecture-affects-the-internet-user","https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-4-hash-function","https://steemit.com/merkle/@thomasoss/blockchain-foundations-part-5-merkle-tree-and-merkle-root","https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-6-radix-tree-patricia-trie","https://steemit.com/ecdsa/@thomasoss/blockchain-foundations-part-7-encryption-and-digital-signature"]} |
| parent author | |
| parent permlink | blockchain |
| permlink | blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture |
| title | Blockchain Foundations Part 1: Distributed, Decentralized and Centralized Computer Architecture |
| Transaction Info | Block #38822109/Trx 6c96a0702146466fae91b7250f6de36adcd74291 |
View Raw JSON Data
{
"block": 38822109,
"op": [
"comment",
{
"author": "thomasoss",
"body": "@@ -1300,16 +1300,162 @@\n ia-trie)\n+%0A- %5BPart 7: Encryption and Digital Signature%5D(https://steemit.com/ecdsa/@thomasoss/blockchain-foundations-part-7-encryption-and-digital-signature)\n %0A%0AThe ne\n@@ -1514,33 +1514,8 @@\n out%0A\n-- Signature%0A- Encryption%0A\n - Bl\n",
"json_metadata": "{\"tags\":[\"centralized\",\"decentralized\",\"distributed\",\"architecture\"],\"image\":[\"https://cdn.steemitimages.com/DQmekyCqN6aKDZTeZF1f8LeWdd8U7jXNUn4KbRgnfCHHzat/image.png\",\"https://cdn.steemitimages.com/DQmZyts7uG8WFYFrFosC6igcPkNtUK4Rphv7jktj1WhKk4x/image.png\",\"https://cdn.steemitimages.com/DQmWs3aueu5cwZECx7hugNQRgur1ctXWjbHJsMXeFvyGkt3/image.png\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\",\"links\":[\"https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-2-peer-to-peer-architecture-and-hybrid-computer-system-architecture\",\"https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-5-1-5-how-the-architecture-affects-the-internet-user\",\"https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-4-hash-function\",\"https://steemit.com/merkle/@thomasoss/blockchain-foundations-part-5-merkle-tree-and-merkle-root\",\"https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-6-radix-tree-patricia-trie\",\"https://steemit.com/ecdsa/@thomasoss/blockchain-foundations-part-7-encryption-and-digital-signature\"]}",
"parent_author": "",
"parent_permlink": "blockchain",
"permlink": "blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture",
"title": "Blockchain Foundations Part 1: Distributed, Decentralized and Centralized Computer Architecture"
}
],
"op_in_trx": 0,
"timestamp": "2019-12-07T07:04:18",
"trx_id": "6c96a0702146466fae91b7250f6de36adcd74291",
"trx_in_block": 5,
"virtual_op": 0
}2019/12/07 07:02:57
2019/12/07 07:02:57
| author | thomasoss |
| permlink | blockchain-foundations-part-7-encryption-and-digital-signature |
| voter | laissez-faire |
| weight | 10000 (100.00%) |
| Transaction Info | Block #38822082/Trx 60a06671e6d5b0f304a4ff5c26cfb0bbffbd6dbd |
View Raw JSON Data
{
"block": 38822082,
"op": [
"vote",
{
"author": "thomasoss",
"permlink": "blockchain-foundations-part-7-encryption-and-digital-signature",
"voter": "laissez-faire",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2019-12-07T07:02:57",
"trx_id": "60a06671e6d5b0f304a4ff5c26cfb0bbffbd6dbd",
"trx_in_block": 11,
"virtual_op": 0
}2019/12/07 07:02:51
2019/12/07 07:02:51
| author | thomasoss |
| permlink | blockchain-foundations-part-7-encryption-and-digital-signature |
| voter | anomaly |
| weight | 100 (1.00%) |
| Transaction Info | Block #38822080/Trx ef19439e875a8e45c36c12a2a41087beed0e228f |
View Raw JSON Data
{
"block": 38822080,
"op": [
"vote",
{
"author": "thomasoss",
"permlink": "blockchain-foundations-part-7-encryption-and-digital-signature",
"voter": "anomaly",
"weight": 100
}
],
"op_in_trx": 0,
"timestamp": "2019-12-07T07:02:51",
"trx_id": "ef19439e875a8e45c36c12a2a41087beed0e228f",
"trx_in_block": 14,
"virtual_op": 0
}thomasosspublished a new post: blockchain-foundations-part-7-encryption-and-digital-signature2019/12/07 07:01:45
thomasosspublished a new post: blockchain-foundations-part-7-encryption-and-digital-signature
2019/12/07 07:01:45
| author | thomasoss |
| body | Encryption and digital signature are important foundations of the blockchain concept. This article explains the asymetric encryption and the digital signature used with blockchains. The article is part of a series starting with this article: [Blockchain Foundations Part 1: Distributed, Decentralized and Centralized Computer Architecture](https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture) The articles are drawn from my book "Blockchain and Crypto Currencies Easy to Understand for Everyone, Thomas Bauer". Please refer to the [part 1 article](https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture) for a introduction to the blockchain foundations series. # Encryption and Digital Signature Blockchain uses asymmetric encryption. There are different terms like asymmetric cryptography, public key cryptography or public/private key cryptography. These all address the approach explained now: * Hans wants to send a message to Katja. He wants to ensure only Katja to read the message. * First, they need to agree on an encryption method. This encryption method must be able to encrypt a message using the public key and to allow only the holder of the private key to decrypt the message. And the method must be able to generate the needed key pairs consisting of a public and a private key. * Usually the encryption method is given by the used application. * Katja generates a key pair and publishes her public key. The private key she keeps a secret. For the key generation a random private key is created first. The public key will be derived from the private key by a one-way function. To derive the private key from the public key is practically impossible. * Hans uses Katja's public key to encrypt the message and sends the encrypted message to Katja. * Katja receives the encrypted message and uses her private key to decrypt the message. We can encrypt a message using the public key of someone else and only the holder of the matching private key is able to decrypt this message. Vice versa we can sign a message using our private key and anyone else can check the message for being unchanged by using our public key. Blockchain uses asymmetric encryption for example for crypto currencies. This time Hans wants to send 0,25 Bitcoin to Katja instead of the text message. * The encryption technique used for Bitcoin is Elliptic Curve Digital Signature Algorithm (ECDSA). It is not important to understand the algorithm itself. Hence the algorithm is not explained in this book. For us is important that it is a cryptographic one-way algorithm. It derives a public key from a private key and it is not possible to derive the private key from the public key. * Katja generates a key pair. This way she gets a public Bitcoin address and the corresponding private key. This public Bitcoin address is not derived directly from the private key. It is an address resulting from the public key derived from the private key and further processing. * Her public Bitcoin address she sends to Hans. * Hans now sends the Bitcoins to this public Bitcoin address. * Hans sends a message to Katja to tell her that he transferred the Bitcoin amount to the Bitcoin address she told him. Or Katja checks her Bitcoin address to find out if the Bitcoin amount already has been booked on this address. * The only one who can use the Bitcoin amount available on this public Bitcoin address is the holder of the corresponding private key. In this case this is Katja. To transfer these Bitcoins to someone else she needs to sign the transaction with her private key. With this signature and the corresponding public key, for the blockchain software it is possible to check if it is the holder of the private key who tries to use the Bitcoins. This way nobody else can use the Bitcoins tied to this Bitcoin address. This was a simplified explanation. Effectively Hans creates a Bitcoin transaction sending the Bitcoins to an address. This information then is available in the blockchain and everyone can see it. But Katja is the only one being able to use the Bitcoins bound to this address. She owns the necessary private key for doing this. This private key she may not really see but it is stored in a wallet and the wallet uses the private key to sign the transaction that uses the Bitcoins. It is important to know that we send our crypto coins to a public address and only the owner of the corresponding private key can use the Bitcoin bound to this address. Check digits at the end of the address help to avoid typing errors when sending crypto coins to an address. In detail each crypto currency has an own procedure and differently structured address. If we are going to deal with a cryptocurrency then we should find out how the encryption and addressing is designed for this currency. |
| json metadata | {"tags":["ecdsa","encryption","public","private","key","signature"],"links":["https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | ecdsa |
| permlink | blockchain-foundations-part-7-encryption-and-digital-signature |
| title | Blockchain Foundations Part 7: Encryption and Digital Signature |
| Transaction Info | Block #38822058/Trx ff371f2663c48be3e59ba26bb701074933923046 |
View Raw JSON Data
{
"block": 38822058,
"op": [
"comment",
{
"author": "thomasoss",
"body": "Encryption and digital signature are important foundations of the blockchain concept. This article explains the asymetric encryption and the digital signature used with blockchains.\n\nThe article is part of a series starting with this article: [Blockchain Foundations Part 1: Distributed, Decentralized and Centralized Computer Architecture](https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture)\n\nThe articles are drawn from my book \"Blockchain and Crypto Currencies Easy to Understand for Everyone, Thomas Bauer\". Please refer to the [part 1 article](https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture) for a introduction to the blockchain foundations series.\n\n# Encryption and Digital Signature\n\nBlockchain uses asymmetric encryption. There are different terms like asymmetric cryptography, public key cryptography or public/private key cryptography. These all address the approach explained now:\n* Hans wants to send a message to Katja. He wants to ensure only Katja to read the message.\n* First, they need to agree on an encryption method. This encryption method must be able to encrypt a message using the public key and to allow only the holder of the private key to decrypt the message. And the method must be able to generate the needed key pairs consisting of a public and a private key.\n* Usually the encryption method is given by the used application.\n* Katja generates a key pair and publishes her public key. The private key she keeps a secret. For the key generation a random private key is created first. The public key will be derived from the private key by a one-way function. To derive the private key from the public key is practically impossible.\n* Hans uses Katja's public key to encrypt the message and sends the encrypted message to Katja.\n* Katja receives the encrypted message and uses her private key to decrypt the message. \n\nWe can encrypt a message using the public key of someone else and only the holder of the matching private key is able to decrypt this message. Vice versa we can sign a message using our private key and anyone else can check the message for being unchanged by using our public key.\n\nBlockchain uses asymmetric encryption for example for crypto currencies.\n\nThis time Hans wants to send 0,25 Bitcoin to Katja instead of the text message. \n* The encryption technique used for Bitcoin is Elliptic Curve Digital Signature Algorithm (ECDSA). It is not important to understand the algorithm itself. Hence the algorithm is not explained in this book. For us is important that it is a cryptographic one-way algorithm. It derives a public key from a private key and it is not possible to derive the private key from the public key. \n* Katja generates a key pair. This way she gets a public Bitcoin address and the corresponding private key. This public Bitcoin address is not derived directly from the private key. It is an address resulting from the public key derived from the private key and further processing. \n* Her public Bitcoin address she sends to Hans. \n* Hans now sends the Bitcoins to this public Bitcoin address.\n* Hans sends a message to Katja to tell her that he transferred the Bitcoin amount to the Bitcoin address she told him. Or Katja checks her Bitcoin address to find out if the Bitcoin amount already has been booked on this address.\n* The only one who can use the Bitcoin amount available on this public Bitcoin address is the holder of the corresponding private key. In this case this is Katja. To transfer these Bitcoins to someone else she needs to sign the transaction with her private key. With this signature and the corresponding public key, for the blockchain software it is possible to check if it is the holder of the private key who tries to use the Bitcoins. This way nobody else can use the Bitcoins tied to this Bitcoin address. \n\nThis was a simplified explanation. Effectively Hans creates a Bitcoin transaction sending the Bitcoins to an address. This information then is available in the blockchain and everyone can see it. But Katja is the only one being able to use the Bitcoins bound to this address. She owns the necessary private key for doing this. This private key she may not really see but it is stored in a wallet and the wallet uses the private key to sign the transaction that uses the Bitcoins. \n\nIt is important to know that we send our crypto coins to a public address and only the owner of the corresponding private key can use the Bitcoin bound to this address. Check digits at the end of the address help to avoid typing errors when sending crypto coins to an address. \n\nIn detail each crypto currency has an own procedure and differently structured address. If we are going to deal with a cryptocurrency then we should find out how the encryption and addressing is designed for this currency.",
"json_metadata": "{\"tags\":[\"ecdsa\",\"encryption\",\"public\",\"private\",\"key\",\"signature\"],\"links\":[\"https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "ecdsa",
"permlink": "blockchain-foundations-part-7-encryption-and-digital-signature",
"title": "Blockchain Foundations Part 7: Encryption and Digital Signature"
}
],
"op_in_trx": 0,
"timestamp": "2019-12-07T07:01:45",
"trx_id": "ff371f2663c48be3e59ba26bb701074933923046",
"trx_in_block": 11,
"virtual_op": 0
}dtubesent 0.001 STEEM to @thomasoss- "DTube Coin Round #1 is live! Visit https://token.d.tube for more information"2019/09/20 20:54:45
dtubesent 0.001 STEEM to @thomasoss- "DTube Coin Round #1 is live! Visit https://token.d.tube for more information"
2019/09/20 20:54:45
| amount | 0.001 STEEM |
| from | dtube |
| memo | DTube Coin Round #1 is live! Visit https://token.d.tube for more information |
| to | thomasoss |
| Transaction Info | Block #36596712/Trx 0124a0eadc57c620c982387a75e1677cfb384bfe |
View Raw JSON Data
{
"block": 36596712,
"op": [
"transfer",
{
"amount": "0.001 STEEM",
"from": "dtube",
"memo": "DTube Coin Round #1 is live! Visit https://token.d.tube for more information",
"to": "thomasoss"
}
],
"op_in_trx": 0,
"timestamp": "2019-09-20T20:54:45",
"trx_id": "0124a0eadc57c620c982387a75e1677cfb384bfe",
"trx_in_block": 28,
"virtual_op": 0
}2019/09/03 18:59:21
2019/09/03 18:59:21
| author | steemitboard |
| body | Congratulations @thomasoss! You have completed the following achievement on the Steem blockchain and have been rewarded with new badge(s) : <table><tr><td><img src="https://steemitimages.com/60x60/http://steemitboard.com/img/notifications/firstpayout.png"></td><td>You got your First payout</td></tr> </table> <sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@thomasoss) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=thomasoss)_</sub> <sub>_If you no longer want to receive notifications, reply to this comment with the word_ `STOP`</sub> ###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| parent author | thomasoss |
| parent permlink | blockchain-foundations-part-6-radix-tree-patricia-trie |
| permlink | steemitboard-notify-thomasoss-20190903t185923000z |
| title | |
| Transaction Info | Block #36106478/Trx f53278f82039c547a912941c087c1cbcf389e8d9 |
View Raw JSON Data
{
"block": 36106478,
"op": [
"comment",
{
"author": "steemitboard",
"body": "Congratulations @thomasoss! You have completed the following achievement on the Steem blockchain and have been rewarded with new badge(s) :\n\n<table><tr><td><img src=\"https://steemitimages.com/60x60/http://steemitboard.com/img/notifications/firstpayout.png\"></td><td>You got your First payout</td></tr>\n</table>\n\n<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@thomasoss) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=thomasoss)_</sub>\n<sub>_If you no longer want to receive notifications, reply to this comment with the word_ `STOP`</sub>\n\n\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}",
"parent_author": "thomasoss",
"parent_permlink": "blockchain-foundations-part-6-radix-tree-patricia-trie",
"permlink": "steemitboard-notify-thomasoss-20190903t185923000z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2019-09-03T18:59:21",
"trx_id": "f53278f82039c547a912941c087c1cbcf389e8d9",
"trx_in_block": 39,
"virtual_op": 0
}dtubesent 0.001 STEEM to @thomasoss- "Final call to claim your DTube account! It takes only 5 minutes. Go now to https://d.tube"2019/09/03 18:10:48
dtubesent 0.001 STEEM to @thomasoss- "Final call to claim your DTube account! It takes only 5 minutes. Go now to https://d.tube"
2019/09/03 18:10:48
| amount | 0.001 STEEM |
| from | dtube |
| memo | Final call to claim your DTube account! It takes only 5 minutes. Go now to https://d.tube |
| to | thomasoss |
| Transaction Info | Block #36105514/Trx 56160ec3f3d54b76bf12bb2a0026e89ffab1b4bc |
View Raw JSON Data
{
"block": 36105514,
"op": [
"transfer",
{
"amount": "0.001 STEEM",
"from": "dtube",
"memo": "Final call to claim your DTube account! It takes only 5 minutes. Go now to https://d.tube",
"to": "thomasoss"
}
],
"op_in_trx": 0,
"timestamp": "2019-09-03T18:10:48",
"trx_id": "56160ec3f3d54b76bf12bb2a0026e89ffab1b4bc",
"trx_in_block": 6,
"virtual_op": 0
}thomasossupvoted (100.00%) @xawi / oi-chat-connect-users-across-blockchains2019/09/03 16:36:48
thomasossupvoted (100.00%) @xawi / oi-chat-connect-users-across-blockchains
2019/09/03 16:36:48
| author | xawi |
| permlink | oi-chat-connect-users-across-blockchains |
| voter | thomasoss |
| weight | 10000 (100.00%) |
| Transaction Info | Block #36103652/Trx dcb4f09853cf4f80616586e12efdf70b2659afda |
View Raw JSON Data
{
"block": 36103652,
"op": [
"vote",
{
"author": "xawi",
"permlink": "oi-chat-connect-users-across-blockchains",
"voter": "thomasoss",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2019-09-03T16:36:48",
"trx_id": "dcb4f09853cf4f80616586e12efdf70b2659afda",
"trx_in_block": 4,
"virtual_op": 0
}2019/09/03 16:24:09
2019/09/03 16:24:09
| author | thomasoss |
| permlink | blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture |
| voter | anomaly |
| weight | 100 (1.00%) |
| Transaction Info | Block #36103404/Trx 5481795e177a906ec33ed2e3349788935d29665b |
View Raw JSON Data
{
"block": 36103404,
"op": [
"vote",
{
"author": "thomasoss",
"permlink": "blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture",
"voter": "anomaly",
"weight": 100
}
],
"op_in_trx": 0,
"timestamp": "2019-09-03T16:24:09",
"trx_id": "5481795e177a906ec33ed2e3349788935d29665b",
"trx_in_block": 35,
"virtual_op": 0
}2019/09/03 16:23:09
2019/09/03 16:23:09
| author | thomasoss |
| body | @@ -1163,16 +1163,153 @@ le-root) +%0A- %5BPart 6: Radix tree (PATRICIA trie)%5D(https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-6-radix-tree-patricia-trie) %0A%0AThe ne |
| json metadata | {"tags":["blockchain","centralized","decentralized","distributed","architecture"],"image":["https://cdn.steemitimages.com/DQmekyCqN6aKDZTeZF1f8LeWdd8U7jXNUn4KbRgnfCHHzat/image.png","https://cdn.steemitimages.com/DQmZyts7uG8WFYFrFosC6igcPkNtUK4Rphv7jktj1WhKk4x/image.png","https://cdn.steemitimages.com/DQmWs3aueu5cwZECx7hugNQRgur1ctXWjbHJsMXeFvyGkt3/image.png"],"app":"steemit/0.1","format":"markdown","links":["https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-2-peer-to-peer-architecture-and-hybrid-computer-system-architecture","https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-5-1-5-how-the-architecture-affects-the-internet-user","https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-4-hash-function","https://steemit.com/merkle/@thomasoss/blockchain-foundations-part-5-merkle-tree-and-merkle-root","https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-6-radix-tree-patricia-trie"]} |
| parent author | |
| parent permlink | blockchain |
| permlink | blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture |
| title | Blockchain Foundations Part 1: Distributed, Decentralized and Centralized Computer Architecture |
| Transaction Info | Block #36103384/Trx 8ece15cc27dfa4a28a7c24a7b48690a7213fce07 |
View Raw JSON Data
{
"block": 36103384,
"op": [
"comment",
{
"author": "thomasoss",
"body": "@@ -1163,16 +1163,153 @@\n le-root)\n+%0A- %5BPart 6: Radix tree (PATRICIA trie)%5D(https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-6-radix-tree-patricia-trie)\n %0A%0AThe ne\n",
"json_metadata": "{\"tags\":[\"blockchain\",\"centralized\",\"decentralized\",\"distributed\",\"architecture\"],\"image\":[\"https://cdn.steemitimages.com/DQmekyCqN6aKDZTeZF1f8LeWdd8U7jXNUn4KbRgnfCHHzat/image.png\",\"https://cdn.steemitimages.com/DQmZyts7uG8WFYFrFosC6igcPkNtUK4Rphv7jktj1WhKk4x/image.png\",\"https://cdn.steemitimages.com/DQmWs3aueu5cwZECx7hugNQRgur1ctXWjbHJsMXeFvyGkt3/image.png\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\",\"links\":[\"https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-2-peer-to-peer-architecture-and-hybrid-computer-system-architecture\",\"https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-5-1-5-how-the-architecture-affects-the-internet-user\",\"https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-4-hash-function\",\"https://steemit.com/merkle/@thomasoss/blockchain-foundations-part-5-merkle-tree-and-merkle-root\",\"https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-6-radix-tree-patricia-trie\"]}",
"parent_author": "",
"parent_permlink": "blockchain",
"permlink": "blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture",
"title": "Blockchain Foundations Part 1: Distributed, Decentralized and Centralized Computer Architecture"
}
],
"op_in_trx": 0,
"timestamp": "2019-09-03T16:23:09",
"trx_id": "8ece15cc27dfa4a28a7c24a7b48690a7213fce07",
"trx_in_block": 3,
"virtual_op": 0
}thomasosspublished a new post: blockchain-foundations-part-6-radix-tree-patricia-trie2019/09/03 16:20:21
thomasosspublished a new post: blockchain-foundations-part-6-radix-tree-patricia-trie
2019/09/03 16:20:21
| author | thomasoss |
| body | This article focuses the radix tree (radix trie, PATRICIA trie). The concept is used for example in Ethereum to store the state. The article is part of a series starting with this article: [Blockchain Foundations Part 1: Distributed, Decentralized and Centralized Computer Architecture](https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture) The articles are drawn from my book "Blockchain and Crypto Currencies Easy to Understand for Everyone, Thomas Bauer". Please refer to the [part 1 article](https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture) for a introduction to the blockchain foundations series. # Radix Tree (PATRICIA trie) A radix tree (radix trie, prefix tree, PATRICIA trie) is a search tree and an ordered data structure. Common prefixes are stored only once. Hence data stored in a radix tree is compressed. The subsequent figure shows edges and nodes. Each edge represents a character. Starting at root strings are stored this way. Characters of strings starting with the same characters are stored only once.  Figure 8: Trie (prefix tree) A radix tree is a more compact form of this search tree. We can see it in the subsequent figure. The number of edges is reduced distinctly.  Figure 9: Radix tree (PATRICIA trie) The term trie is derived from information retrieval. Often tree is used instead of trie. PATRICIA is an acronym for Practical Algorithm to Retrieve Information Coded in Alphanumeric. Ethereum uses the radix tree to store the state. This is explained later in this article series. |
| json metadata | {"tags":["blockchain","radix","patricia","ethereum","foundations"],"image":["https://cdn.steemitimages.com/DQmaKYiGD8o81MNrcTLcHL1iAHWa4Gvupiq7MptEgJRJ9FF/image.png","https://cdn.steemitimages.com/DQmPYNKNiFA8XzvSdtSbLPkGvcR7tC2XySPEudSWDddzTFF/image.png"],"links":["https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | blockchain |
| permlink | blockchain-foundations-part-6-radix-tree-patricia-trie |
| title | Blockchain Foundations Part 6: Radix Tree (PATRICIA Trie) |
| Transaction Info | Block #36103329/Trx 42eb0d9b5c4db68a747a7127687051e2f7ebfe51 |
View Raw JSON Data
{
"block": 36103329,
"op": [
"comment",
{
"author": "thomasoss",
"body": "This article focuses the radix tree (radix trie, PATRICIA trie). The concept is used for example in Ethereum to store the state.\n\nThe article is part of a series starting with this article: [Blockchain Foundations Part 1: Distributed, Decentralized and Centralized Computer Architecture](https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture)\n\nThe articles are drawn from my book \"Blockchain and Crypto Currencies Easy to Understand for Everyone, Thomas Bauer\". Please refer to the [part 1 article](https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture) for a introduction to the blockchain foundations series.\n\n# Radix Tree (PATRICIA trie)\n\nA radix tree (radix trie, prefix tree, PATRICIA trie) is a search tree and an ordered data structure. Common prefixes are stored only once. Hence data stored in a radix tree is compressed. \n\nThe subsequent figure shows edges and nodes. Each edge represents a character. Starting at root strings are stored this way. Characters of strings starting with the same characters are stored only once.\n\n\nFigure 8: Trie (prefix tree)\n\nA radix tree is a more compact form of this search tree. We can see it in the subsequent figure. The number of edges is reduced distinctly.\n\n\nFigure 9: Radix tree (PATRICIA trie)\n\nThe term trie is derived from information retrieval. Often tree is used instead of trie. PATRICIA is an acronym for Practical Algorithm to Retrieve Information Coded in Alphanumeric.\n\nEthereum uses the radix tree to store the state. This is explained later in this article series.",
"json_metadata": "{\"tags\":[\"blockchain\",\"radix\",\"patricia\",\"ethereum\",\"foundations\"],\"image\":[\"https://cdn.steemitimages.com/DQmaKYiGD8o81MNrcTLcHL1iAHWa4Gvupiq7MptEgJRJ9FF/image.png\",\"https://cdn.steemitimages.com/DQmPYNKNiFA8XzvSdtSbLPkGvcR7tC2XySPEudSWDddzTFF/image.png\"],\"links\":[\"https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "blockchain",
"permlink": "blockchain-foundations-part-6-radix-tree-patricia-trie",
"title": "Blockchain Foundations Part 6: Radix Tree (PATRICIA Trie)"
}
],
"op_in_trx": 0,
"timestamp": "2019-09-03T16:20:21",
"trx_id": "42eb0d9b5c4db68a747a7127687051e2f7ebfe51",
"trx_in_block": 39,
"virtual_op": 0
}2019/08/26 00:15:21
2019/08/26 00:15:21
| comment author | boosta |
| comment permlink | pwgjdl |
| curator | thomasoss |
| reward | 5.947524 VESTS |
| Transaction Info | Block #35875370/Virtual Operation #7 |
View Raw JSON Data
{
"block": 35875370,
"op": [
"curation_reward",
{
"comment_author": "boosta",
"comment_permlink": "pwgjdl",
"curator": "thomasoss",
"reward": "5.947524 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2019-08-26T00:15:21",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": 7
}thomasossreceived 0.630 STEEM, 0.001 SBD, 0.776 SP author reward for @thomasoss / pwfztk2019/08/25 17:12:57
thomasossreceived 0.630 STEEM, 0.001 SBD, 0.776 SP author reward for @thomasoss / pwfztk
2019/08/25 17:12:57
| author | thomasoss |
| permlink | pwfztk |
| sbd payout | 0.001 SBD |
| steem payout | 0.630 STEEM |
| vesting payout | 1262.880444 VESTS |
| Transaction Info | Block #35866935/Virtual Operation #3 |
View Raw JSON Data
{
"block": 35866935,
"op": [
"author_reward",
{
"author": "thomasoss",
"permlink": "pwfztk",
"sbd_payout": "0.001 SBD",
"steem_payout": "0.630 STEEM",
"vesting_payout": "1262.880444 VESTS"
}
],
"op_in_trx": 0,
"timestamp": "2019-08-25T17:12:57",
"trx_id": "0000000000000000000000000000000000000000",
"trx_in_block": 4294967295,
"virtual_op": 3
}thomasossfollowed @steeminfobot2019/08/24 06:04:36
thomasossfollowed @steeminfobot
2019/08/24 06:04:36
| id | follow |
| json | ["follow",{"follower":"thomasoss","following":"steeminfobot","what":["blog"]}] |
| required auths | [] |
| required posting auths | ["thomasoss"] |
| Transaction Info | Block #35824833/Trx 32dbeb84a8ffef6c987eb9b2caaaf19fec559978 |
View Raw JSON Data
{
"block": 35824833,
"op": [
"custom_json",
{
"id": "follow",
"json": "[\"follow\",{\"follower\":\"thomasoss\",\"following\":\"steeminfobot\",\"what\":[\"blog\"]}]",
"required_auths": [],
"required_posting_auths": [
"thomasoss"
]
}
],
"op_in_trx": 0,
"timestamp": "2019-08-24T06:04:36",
"trx_id": "32dbeb84a8ffef6c987eb9b2caaaf19fec559978",
"trx_in_block": 18,
"virtual_op": 0
}2019/08/24 06:04:21
2019/08/24 06:04:21
| author | steeminfobot |
| permlink | title-how-to-powerup-your-blog-action-4-powerup-other-channels-slideshare |
| voter | thomasoss |
| weight | 10000 (100.00%) |
| Transaction Info | Block #35824828/Trx 24ea42ab672d6765256cb7aa10afaef576642728 |
View Raw JSON Data
{
"block": 35824828,
"op": [
"vote",
{
"author": "steeminfobot",
"permlink": "title-how-to-powerup-your-blog-action-4-powerup-other-channels-slideshare",
"voter": "thomasoss",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2019-08-24T06:04:21",
"trx_id": "24ea42ab672d6765256cb7aa10afaef576642728",
"trx_in_block": 0,
"virtual_op": 0
}2019/08/24 06:01:06
2019/08/24 06:01:06
| id | follow |
| json | ["follow",{"follower":"thomasoss","following":"nin4i","what":["blog"]}] |
| required auths | [] |
| required posting auths | ["thomasoss"] |
| Transaction Info | Block #35824763/Trx 35e7c0a219f5435411723b980fc15126687d15fd |
View Raw JSON Data
{
"block": 35824763,
"op": [
"custom_json",
{
"id": "follow",
"json": "[\"follow\",{\"follower\":\"thomasoss\",\"following\":\"nin4i\",\"what\":[\"blog\"]}]",
"required_auths": [],
"required_posting_auths": [
"thomasoss"
]
}
],
"op_in_trx": 0,
"timestamp": "2019-08-24T06:01:06",
"trx_id": "35e7c0a219f5435411723b980fc15126687d15fd",
"trx_in_block": 24,
"virtual_op": 0
}thomasossupvoted (100.00%) @nin4i / actifit-nin4i-20190811t200528501z2019/08/24 06:00:54
thomasossupvoted (100.00%) @nin4i / actifit-nin4i-20190811t200528501z
2019/08/24 06:00:54
| author | nin4i |
| permlink | actifit-nin4i-20190811t200528501z |
| voter | thomasoss |
| weight | 10000 (100.00%) |
| Transaction Info | Block #35824759/Trx 35cfa591bb6d8b2f3ccf0993e2e2aaa9bacb1aa4 |
View Raw JSON Data
{
"block": 35824759,
"op": [
"vote",
{
"author": "nin4i",
"permlink": "actifit-nin4i-20190811t200528501z",
"voter": "thomasoss",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2019-08-24T06:00:54",
"trx_id": "35cfa591bb6d8b2f3ccf0993e2e2aaa9bacb1aa4",
"trx_in_block": 21,
"virtual_op": 0
}2019/08/24 05:59:48
2019/08/24 05:59:48
| author | thomasoss |
| body | @@ -1027,16 +1027,152 @@ unction) +%0A- %5BPart 5: Merkle Tree an Merkle Root%5D(https://steemit.com/merkle/@thomasoss/blockchain-foundations-part-5-merkle-tree-and-merkle-root) %0A%0AThe ne |
| json metadata | {"tags":["blockchain","centralized","decentralized","distributed","architecture"],"image":["https://cdn.steemitimages.com/DQmekyCqN6aKDZTeZF1f8LeWdd8U7jXNUn4KbRgnfCHHzat/image.png","https://cdn.steemitimages.com/DQmZyts7uG8WFYFrFosC6igcPkNtUK4Rphv7jktj1WhKk4x/image.png","https://cdn.steemitimages.com/DQmWs3aueu5cwZECx7hugNQRgur1ctXWjbHJsMXeFvyGkt3/image.png"],"app":"steemit/0.1","format":"markdown","links":["https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-2-peer-to-peer-architecture-and-hybrid-computer-system-architecture","https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-5-1-5-how-the-architecture-affects-the-internet-user","https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-4-hash-function","https://steemit.com/merkle/@thomasoss/blockchain-foundations-part-5-merkle-tree-and-merkle-root"]} |
| parent author | |
| parent permlink | blockchain |
| permlink | blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture |
| title | Blockchain Foundations Part 1: Distributed, Decentralized and Centralized Computer Architecture |
| Transaction Info | Block #35824737/Trx 048d002cf45c2484448af668beed9cdc98fde0e8 |
View Raw JSON Data
{
"block": 35824737,
"op": [
"comment",
{
"author": "thomasoss",
"body": "@@ -1027,16 +1027,152 @@\n unction)\n+%0A- %5BPart 5: Merkle Tree an Merkle Root%5D(https://steemit.com/merkle/@thomasoss/blockchain-foundations-part-5-merkle-tree-and-merkle-root)\n %0A%0AThe ne\n",
"json_metadata": "{\"tags\":[\"blockchain\",\"centralized\",\"decentralized\",\"distributed\",\"architecture\"],\"image\":[\"https://cdn.steemitimages.com/DQmekyCqN6aKDZTeZF1f8LeWdd8U7jXNUn4KbRgnfCHHzat/image.png\",\"https://cdn.steemitimages.com/DQmZyts7uG8WFYFrFosC6igcPkNtUK4Rphv7jktj1WhKk4x/image.png\",\"https://cdn.steemitimages.com/DQmWs3aueu5cwZECx7hugNQRgur1ctXWjbHJsMXeFvyGkt3/image.png\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\",\"links\":[\"https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-2-peer-to-peer-architecture-and-hybrid-computer-system-architecture\",\"https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-5-1-5-how-the-architecture-affects-the-internet-user\",\"https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-4-hash-function\",\"https://steemit.com/merkle/@thomasoss/blockchain-foundations-part-5-merkle-tree-and-merkle-root\"]}",
"parent_author": "",
"parent_permlink": "blockchain",
"permlink": "blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture",
"title": "Blockchain Foundations Part 1: Distributed, Decentralized and Centralized Computer Architecture"
}
],
"op_in_trx": 0,
"timestamp": "2019-08-24T05:59:48",
"trx_id": "048d002cf45c2484448af668beed9cdc98fde0e8",
"trx_in_block": 21,
"virtual_op": 0
}nin4iupvoted (100.00%) @thomasoss / blockchain-foundations-part-5-merkle-tree-and-merkle-root2019/08/24 05:59:24
nin4iupvoted (100.00%) @thomasoss / blockchain-foundations-part-5-merkle-tree-and-merkle-root
2019/08/24 05:59:24
| author | thomasoss |
| permlink | blockchain-foundations-part-5-merkle-tree-and-merkle-root |
| voter | nin4i |
| weight | 10000 (100.00%) |
| Transaction Info | Block #35824729/Trx c1366ffda7ae105ab1ecc4c9774215ce5390de63 |
View Raw JSON Data
{
"block": 35824729,
"op": [
"vote",
{
"author": "thomasoss",
"permlink": "blockchain-foundations-part-5-merkle-tree-and-merkle-root",
"voter": "nin4i",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2019-08-24T05:59:24",
"trx_id": "c1366ffda7ae105ab1ecc4c9774215ce5390de63",
"trx_in_block": 18,
"virtual_op": 0
}2019/08/24 05:56:39
2019/08/24 05:56:39
| author | cheetah |
| body | Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in: http://www.omnisecu.com/tcpip/what-are-hash-values-important-hash-value-algorithms.php |
| json metadata | |
| parent author | thomasoss |
| parent permlink | blockchain-foundations-part-5-merkle-tree-and-merkle-root |
| permlink | cheetah-re-thomasossblockchain-foundations-part-5-merkle-tree-and-merkle-root |
| title | |
| Transaction Info | Block #35824674/Trx 414496d6f670fe893e03578ef97c17c9c194d399 |
View Raw JSON Data
{
"block": 35824674,
"op": [
"comment",
{
"author": "cheetah",
"body": "Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in:\nhttp://www.omnisecu.com/tcpip/what-are-hash-values-important-hash-value-algorithms.php",
"json_metadata": "",
"parent_author": "thomasoss",
"parent_permlink": "blockchain-foundations-part-5-merkle-tree-and-merkle-root",
"permlink": "cheetah-re-thomasossblockchain-foundations-part-5-merkle-tree-and-merkle-root",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2019-08-24T05:56:39",
"trx_id": "414496d6f670fe893e03578ef97c17c9c194d399",
"trx_in_block": 13,
"virtual_op": 0
}cheetahupvoted (0.08%) @thomasoss / blockchain-foundations-part-5-merkle-tree-and-merkle-root2019/08/24 05:56:36
cheetahupvoted (0.08%) @thomasoss / blockchain-foundations-part-5-merkle-tree-and-merkle-root
2019/08/24 05:56:36
| author | thomasoss |
| permlink | blockchain-foundations-part-5-merkle-tree-and-merkle-root |
| voter | cheetah |
| weight | 8 (0.08%) |
| Transaction Info | Block #35824673/Trx a68fc4c38cad632f14283405a267802c79389cd5 |
View Raw JSON Data
{
"block": 35824673,
"op": [
"vote",
{
"author": "thomasoss",
"permlink": "blockchain-foundations-part-5-merkle-tree-and-merkle-root",
"voter": "cheetah",
"weight": 8
}
],
"op_in_trx": 0,
"timestamp": "2019-08-24T05:56:36",
"trx_id": "a68fc4c38cad632f14283405a267802c79389cd5",
"trx_in_block": 10,
"virtual_op": 0
}thomasosspublished a new post: blockchain-foundations-part-5-merkle-tree-and-merkle-root2019/08/24 05:56:27
thomasosspublished a new post: blockchain-foundations-part-5-merkle-tree-and-merkle-root
2019/08/24 05:56:27
| author | thomasoss |
| body | This article talks about Merkle Tree and Merkle Root. The concept is used in many blockchains, for example in the Ethereum or Bitcoin blockchain. Merkle tree is often mentioned when talking about blockchain, Bitcoin or similar topics. Hence it is useful to know what a Merkle tree is The article is part of a series starting with this article: [Blockchain Foundations Part 1: Distributed, Decentralized and Centralized Computer Architecture](https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture) The articles are drawn from my book "Blockchain and Crypto Currencies Easy to Understand for Everyone, Thomas Bauer". Please refer to the [part 1 article](https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture) for a introduction to the blockchain foundations series. # Merkle Tree and Merkle Root The Merkle tree is a hash tree. Ralph Merkle specified it in 1979. It is a tree consisting of hash values. - All leaves of the tree represent the hash values of data blocks - All intersections of the tree represent the hash value derived from 2 to n subjacent hash values. In a binary hash tree an intersection hash value always is derived from exactly 2 subjacent hash values For building the Merkle tree in the subsequent example in the first step of all strings (like "A sends 0,01 BTC to C") on the lowest level the SHA-256 hash value was derived. To build the nodes the hash value for each node was derived from the concatenated two hash values below the node.  Figure 5: Merkle tree What to do if there are not exactly 4, 8, 16, … transactions? There are different methods. One method for a node with only one leave is to duplicate the existing leave. That is the way Bitcoin does it.  Figure 6: Merkle tree with an uneven number of leaves We use the Merkle tree to check data blocks being unchanged since they have been stored. For this we only need to store the root hash value. A new calculation of the Merkle tree bases on the stored data blocks will lead to the same root hash value, if the data blocks are unchanged. With a Merkle tree we can check data blocks with little costs. Assume we want to check data block 4 shown in the figure above for being unchanged. Then we need for the check beside data block 4 and its corresponding hash value only the hash value of data block 3, the hash value 12 and the hash value 5555. The hash values 34, 1234 and 12345555 we calculate from these inputs to check for data block 4 being unchanged. If we add a new data block to a Merkle tree, we do not need to recalculate the whole tree. We only need to recalculate the hash value of the new data block and the hash values of the nodes above the new data block. Then our Merkle tree is consistent once again.  Figure 7: Do a change to a Merkle tree In the figure the light blue elements (data block 6 and hash value data block 6) where added and calculated. The yellow elements (hash values 56, 5656 and 12345656) we need to recalculate. All the other elements with the white background remain unchanged. Blockchain uses Merkle tree for example for: - For storing the transactions within a block as Merkle tree - Bitcoin calculates a hash value for each block. Because the transactions are stored in a Merkle tree the Merkle root hash value represents all transactions in the block. Hence for the calculation of the block hash value it is not necessary to derive a hash value from all the data contained in the block. It is enough to derive the block hash value from the block header containing the root hash value of the Merkle Tree Merkle tree is often mentioned when talking about blockchain, Bitcoin or similar topics. Hence it is useful to know what a Merkle tree is. On the other hand, Merkle tree is located deep in the details of implementation. You will understand blockchain without knowing details about the Merkle tree or even knowing how to build one. It is enough to know that a Merkle root hash can unambiguously represent the complete data structure it stands for. |
| json metadata | {"tags":["merkle","ethereum","bitcoin","hash","blockchain"],"image":["https://cdn.steemitimages.com/DQmRGq22MGCByLJaaRiL95FrhWtrU5deGUo8TnfJftoBU5P/image.png","https://cdn.steemitimages.com/DQmf7TiaWQSGfxJzSFCHGkJVQx1hjPt7ZgnS6fUTeWzm4Cu/image.png","https://cdn.steemitimages.com/DQmTkJyGacUqjhocGQZGUxUg1ZENQhBAdyBV5uMJm2rRifw/image.png"],"links":["https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | merkle |
| permlink | blockchain-foundations-part-5-merkle-tree-and-merkle-root |
| title | Blockchain Foundations Part 5: Merkle Tree and Merkle Root |
| Transaction Info | Block #35824670/Trx 464be6fe53ed8e6647042a8afc0d66e7ff29618c |
View Raw JSON Data
{
"block": 35824670,
"op": [
"comment",
{
"author": "thomasoss",
"body": "This article talks about Merkle Tree and Merkle Root. The concept is used in many blockchains, for example in the Ethereum or Bitcoin blockchain. Merkle tree is often mentioned when talking about blockchain, Bitcoin or similar topics. Hence it is useful to know what a Merkle tree is\n\nThe article is part of a series starting with this article: [Blockchain Foundations Part 1: Distributed, Decentralized and Centralized Computer Architecture](https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture)\n\nThe articles are drawn from my book \"Blockchain and Crypto Currencies Easy to Understand for Everyone, Thomas Bauer\". Please refer to the [part 1 article](https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture) for a introduction to the blockchain foundations series.\n\n# Merkle Tree and Merkle Root\n\nThe Merkle tree is a hash tree. Ralph Merkle specified it in 1979. It is a tree consisting of hash values. \n- All leaves of the tree represent the hash values of data blocks\n- All intersections of the tree represent the hash value derived from 2 to n subjacent hash values. In a binary hash tree an intersection hash value always is derived from exactly 2 subjacent hash values\n\nFor building the Merkle tree in the subsequent example in the first step of all strings (like \"A sends 0,01 BTC to C\") on the lowest level the SHA-256 hash value was derived. To build the nodes the hash value for each node was derived from the concatenated two hash values below the node.\n\n\nFigure 5: Merkle tree\n\nWhat to do if there are not exactly 4, 8, 16, … transactions? There are different methods. One method for a node with only one leave is to duplicate the existing leave. That is the way Bitcoin does it. \n\n\nFigure 6: Merkle tree with an uneven number of leaves\n\nWe use the Merkle tree to check data blocks being unchanged since they have been stored. For this we only need to store the root hash value. A new calculation of the Merkle tree bases on the stored data blocks will lead to the same root hash value, if the data blocks are unchanged. \n\nWith a Merkle tree we can check data blocks with little costs. Assume we want to check data block 4 shown in the figure above for being unchanged. Then we need for the check beside data block 4 and its corresponding hash value only the hash value of data block 3, the hash value 12 and the hash value 5555. The hash values 34, 1234 and 12345555 we calculate from these inputs to check for data block 4 being unchanged.\n\nIf we add a new data block to a Merkle tree, we do not need to recalculate the whole tree. We only need to recalculate the hash value of the new data block and the hash values of the nodes above the new data block. Then our Merkle tree is consistent once again.\n\n\nFigure 7: Do a change to a Merkle tree\n\nIn the figure the light blue elements (data block 6 and hash value data block 6) where added and calculated. The yellow elements (hash values 56, 5656 and 12345656) we need to recalculate. All the other elements with the white background remain unchanged.\n\nBlockchain uses Merkle tree for example for:\n- For storing the transactions within a block as Merkle tree\n- Bitcoin calculates a hash value for each block. Because the transactions are stored in a Merkle tree the Merkle root hash value represents all transactions in the block. Hence for the calculation of the block hash value it is not necessary to derive a hash value from all the data contained in the block. It is enough to derive the block hash value from the block header containing the root hash value of the Merkle Tree\n\nMerkle tree is often mentioned when talking about blockchain, Bitcoin or similar topics. Hence it is useful to know what a Merkle tree is. On the other hand, Merkle tree is located deep in the details of implementation. You will understand blockchain without knowing details about the Merkle tree or even knowing how to build one. It is enough to know that a Merkle root hash can unambiguously represent the complete data structure it stands for.",
"json_metadata": "{\"tags\":[\"merkle\",\"ethereum\",\"bitcoin\",\"hash\",\"blockchain\"],\"image\":[\"https://cdn.steemitimages.com/DQmRGq22MGCByLJaaRiL95FrhWtrU5deGUo8TnfJftoBU5P/image.png\",\"https://cdn.steemitimages.com/DQmf7TiaWQSGfxJzSFCHGkJVQx1hjPt7ZgnS6fUTeWzm4Cu/image.png\",\"https://cdn.steemitimages.com/DQmTkJyGacUqjhocGQZGUxUg1ZENQhBAdyBV5uMJm2rRifw/image.png\"],\"links\":[\"https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "merkle",
"permlink": "blockchain-foundations-part-5-merkle-tree-and-merkle-root",
"title": "Blockchain Foundations Part 5: Merkle Tree and Merkle Root"
}
],
"op_in_trx": 0,
"timestamp": "2019-08-24T05:56:27",
"trx_id": "464be6fe53ed8e6647042a8afc0d66e7ff29618c",
"trx_in_block": 6,
"virtual_op": 0
}thomasosspublished a new post: blockchain-foundations-part-4-hash-function2019/08/22 06:11:39
thomasosspublished a new post: blockchain-foundations-part-4-hash-function
2019/08/22 06:11:39
| author | thomasoss |
| body | @@ -20,16 +20,17 @@ ns basic +s about h @@ -41,16 +41,17 @@ function +s .%0A%0AThe a |
| json metadata | {"tags":["blockchain","hash","foundations","encryption"],"links":["https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | blockchain |
| permlink | blockchain-foundations-part-4-hash-function |
| title | Blockchain Foundations Part 4: Hash Function |
| Transaction Info | Block #35767464/Trx 30d1064886e52561861ce0e0e24e8aa71dea7c76 |
View Raw JSON Data
{
"block": 35767464,
"op": [
"comment",
{
"author": "thomasoss",
"body": "@@ -20,16 +20,17 @@\n ns basic\n+s\n about h\n@@ -41,16 +41,17 @@\n function\n+s\n .%0A%0AThe a\n",
"json_metadata": "{\"tags\":[\"blockchain\",\"hash\",\"foundations\",\"encryption\"],\"links\":[\"https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "blockchain",
"permlink": "blockchain-foundations-part-4-hash-function",
"title": "Blockchain Foundations Part 4: Hash Function"
}
],
"op_in_trx": 0,
"timestamp": "2019-08-22T06:11:39",
"trx_id": "30d1064886e52561861ce0e0e24e8aa71dea7c76",
"trx_in_block": 13,
"virtual_op": 0
}thomasossfollowed @ethsensei2019/08/21 18:00:27
thomasossfollowed @ethsensei
2019/08/21 18:00:27
| id | follow |
| json | ["follow",{"follower":"thomasoss","following":"ethsensei","what":["blog"]}] |
| required auths | [] |
| required posting auths | ["thomasoss"] |
| Transaction Info | Block #35752860/Trx 292e8d08bef5d5861131b279258c1f4199a3c24f |
View Raw JSON Data
{
"block": 35752860,
"op": [
"custom_json",
{
"id": "follow",
"json": "[\"follow\",{\"follower\":\"thomasoss\",\"following\":\"ethsensei\",\"what\":[\"blog\"]}]",
"required_auths": [],
"required_posting_auths": [
"thomasoss"
]
}
],
"op_in_trx": 0,
"timestamp": "2019-08-21T18:00:27",
"trx_id": "292e8d08bef5d5861131b279258c1f4199a3c24f",
"trx_in_block": 18,
"virtual_op": 0
}thomasossupvoted (100.00%) @ethsensei / why-ethereum-will-never-reach-another-ath2019/08/21 17:59:57
thomasossupvoted (100.00%) @ethsensei / why-ethereum-will-never-reach-another-ath
2019/08/21 17:59:57
| author | ethsensei |
| permlink | why-ethereum-will-never-reach-another-ath |
| voter | thomasoss |
| weight | 10000 (100.00%) |
| Transaction Info | Block #35752850/Trx ade2ad5815e135bd0856f037001ccf2fd71c249f |
View Raw JSON Data
{
"block": 35752850,
"op": [
"vote",
{
"author": "ethsensei",
"permlink": "why-ethereum-will-never-reach-another-ath",
"voter": "thomasoss",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2019-08-21T17:59:57",
"trx_id": "ade2ad5815e135bd0856f037001ccf2fd71c249f",
"trx_in_block": 4,
"virtual_op": 0
}thomasossupvoted (100.00%) @lunaticpandora / playing-boardgames-on-the-saito-blockchain2019/08/21 17:54:15
thomasossupvoted (100.00%) @lunaticpandora / playing-boardgames-on-the-saito-blockchain
2019/08/21 17:54:15
| author | lunaticpandora |
| permlink | playing-boardgames-on-the-saito-blockchain |
| voter | thomasoss |
| weight | 10000 (100.00%) |
| Transaction Info | Block #35752737/Trx 8c4c6d4348c99b5fd735e12e56a6ef139aecc3f7 |
View Raw JSON Data
{
"block": 35752737,
"op": [
"vote",
{
"author": "lunaticpandora",
"permlink": "playing-boardgames-on-the-saito-blockchain",
"voter": "thomasoss",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2019-08-21T17:54:15",
"trx_id": "8c4c6d4348c99b5fd735e12e56a6ef139aecc3f7",
"trx_in_block": 34,
"virtual_op": 0
}laissez-faireupvoted (100.00%) @thomasoss / blockchain-foundations-part-4-hash-function2019/08/21 17:52:48
laissez-faireupvoted (100.00%) @thomasoss / blockchain-foundations-part-4-hash-function
2019/08/21 17:52:48
| author | thomasoss |
| permlink | blockchain-foundations-part-4-hash-function |
| voter | laissez-faire |
| weight | 10000 (100.00%) |
| Transaction Info | Block #35752708/Trx fbcc71d3c341e50d06ab85c13a23ad193a944f26 |
View Raw JSON Data
{
"block": 35752708,
"op": [
"vote",
{
"author": "thomasoss",
"permlink": "blockchain-foundations-part-4-hash-function",
"voter": "laissez-faire",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2019-08-21T17:52:48",
"trx_id": "fbcc71d3c341e50d06ab85c13a23ad193a944f26",
"trx_in_block": 21,
"virtual_op": 0
}thomasossupvoted (100.00%) @hatu / a-programmable-internet-faster-content-consumption-at-lower-costs2019/08/21 17:50:33
thomasossupvoted (100.00%) @hatu / a-programmable-internet-faster-content-consumption-at-lower-costs
2019/08/21 17:50:33
| author | hatu |
| permlink | a-programmable-internet-faster-content-consumption-at-lower-costs |
| voter | thomasoss |
| weight | 10000 (100.00%) |
| Transaction Info | Block #35752663/Trx 8c82249bd6918c9c51755e45845af068d3f0f3b1 |
View Raw JSON Data
{
"block": 35752663,
"op": [
"vote",
{
"author": "hatu",
"permlink": "a-programmable-internet-faster-content-consumption-at-lower-costs",
"voter": "thomasoss",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2019-08-21T17:50:33",
"trx_id": "8c82249bd6918c9c51755e45845af068d3f0f3b1",
"trx_in_block": 14,
"virtual_op": 0
}thomasosspublished a new post: blockchain-foundations-part-4-hash-function2019/08/21 17:42:09
thomasosspublished a new post: blockchain-foundations-part-4-hash-function
2019/08/21 17:42:09
| author | thomasoss |
| body | @@ -1924,16 +1924,511 @@ b8816e%0A%0A +The hash values shown in the table (for the case they are not shown in full length in the table column)%0A6b86b273ff34fce19d6b804eff5a3f5747ada4eaa22f1d49c01e52ddb7875b4b%0Ad4735e3a265e16eee03f59718b9b5d03019c07d8b6c51f90da3a666eec13ab35%0Acf7e66b7c62562fb697576c1592a0787dffa4e542b770e28d330ca623f26c381%0A151471b8dcd8d9e7f93282172c3fdab0d356cc6d32944253d062a8df31a5c59e%0Acdb72b05832ff97ffe86f6cf716d45dcd50fbb3b5c4999b6dbd182a8c3ffd0e9%0A3b54c614f29d96ef8a3250fb56d581d96f19568659f9ee20ff0f660e21b8816e%0A%0A We see t |
| json metadata | {"tags":["blockchain","hash","foundations","encryption"],"links":["https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | blockchain |
| permlink | blockchain-foundations-part-4-hash-function |
| title | Blockchain Foundations Part 4: Hash Function |
| Transaction Info | Block #35752495/Trx 1fa28b49352ec4bea0ee11125300fddb225b48c3 |
View Raw JSON Data
{
"block": 35752495,
"op": [
"comment",
{
"author": "thomasoss",
"body": "@@ -1924,16 +1924,511 @@\n b8816e%0A%0A\n+The hash values shown in the table (for the case they are not shown in full length in the table column)%0A6b86b273ff34fce19d6b804eff5a3f5747ada4eaa22f1d49c01e52ddb7875b4b%0Ad4735e3a265e16eee03f59718b9b5d03019c07d8b6c51f90da3a666eec13ab35%0Acf7e66b7c62562fb697576c1592a0787dffa4e542b770e28d330ca623f26c381%0A151471b8dcd8d9e7f93282172c3fdab0d356cc6d32944253d062a8df31a5c59e%0Acdb72b05832ff97ffe86f6cf716d45dcd50fbb3b5c4999b6dbd182a8c3ffd0e9%0A3b54c614f29d96ef8a3250fb56d581d96f19568659f9ee20ff0f660e21b8816e%0A%0A\n We see t\n",
"json_metadata": "{\"tags\":[\"blockchain\",\"hash\",\"foundations\",\"encryption\"],\"links\":[\"https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "blockchain",
"permlink": "blockchain-foundations-part-4-hash-function",
"title": "Blockchain Foundations Part 4: Hash Function"
}
],
"op_in_trx": 0,
"timestamp": "2019-08-21T17:42:09",
"trx_id": "1fa28b49352ec4bea0ee11125300fddb225b48c3",
"trx_in_block": 28,
"virtual_op": 0
}2019/08/21 17:38:39
2019/08/21 17:38:39
| author | thomasoss |
| body | @@ -307,16 +307,176 @@ shed are +%0A%0A**Distributed, Decentralized and Centralized Computer Architecture**%0A- Part 1: Distributed, Decentralized and Centralized Computer Architecture (this article) %0A- %5BPart @@ -871,16 +871,174 @@ -user)%0A%0A +**Signature, Encryption and Hash Function**%0A- %5BPart 4: Hash Function%5D(https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-4-hash-function)%0A%0A The next @@ -1094,33 +1094,34 @@ bout%0A- Signature -, +%0A- Encryption and @@ -1115,34 +1115,16 @@ cryption - and Hash Function %0A- Block |
| json metadata | {"tags":["blockchain","centralized","decentralized","distributed","architecture"],"image":["https://cdn.steemitimages.com/DQmekyCqN6aKDZTeZF1f8LeWdd8U7jXNUn4KbRgnfCHHzat/image.png","https://cdn.steemitimages.com/DQmZyts7uG8WFYFrFosC6igcPkNtUK4Rphv7jktj1WhKk4x/image.png","https://cdn.steemitimages.com/DQmWs3aueu5cwZECx7hugNQRgur1ctXWjbHJsMXeFvyGkt3/image.png"],"app":"steemit/0.1","format":"markdown","links":["https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-2-peer-to-peer-architecture-and-hybrid-computer-system-architecture","https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-5-1-5-how-the-architecture-affects-the-internet-user","https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-4-hash-function"]} |
| parent author | |
| parent permlink | blockchain |
| permlink | blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture |
| title | Blockchain Foundations Part 1: Distributed, Decentralized and Centralized Computer Architecture |
| Transaction Info | Block #35752425/Trx c9eca5f754e07b680650bd91bb93eb9a94f7f4d0 |
View Raw JSON Data
{
"block": 35752425,
"op": [
"comment",
{
"author": "thomasoss",
"body": "@@ -307,16 +307,176 @@\n shed are\n+%0A%0A**Distributed, Decentralized and Centralized Computer Architecture**%0A- Part 1: Distributed, Decentralized and Centralized Computer Architecture (this article)\n %0A- %5BPart\n@@ -871,16 +871,174 @@\n -user)%0A%0A\n+**Signature, Encryption and Hash Function**%0A- %5BPart 4: Hash Function%5D(https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-4-hash-function)%0A%0A\n The next\n@@ -1094,33 +1094,34 @@\n bout%0A- Signature\n-,\n+%0A-\n Encryption and \n@@ -1115,34 +1115,16 @@\n cryption\n- and Hash Function\n %0A- Block\n",
"json_metadata": "{\"tags\":[\"blockchain\",\"centralized\",\"decentralized\",\"distributed\",\"architecture\"],\"image\":[\"https://cdn.steemitimages.com/DQmekyCqN6aKDZTeZF1f8LeWdd8U7jXNUn4KbRgnfCHHzat/image.png\",\"https://cdn.steemitimages.com/DQmZyts7uG8WFYFrFosC6igcPkNtUK4Rphv7jktj1WhKk4x/image.png\",\"https://cdn.steemitimages.com/DQmWs3aueu5cwZECx7hugNQRgur1ctXWjbHJsMXeFvyGkt3/image.png\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\",\"links\":[\"https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-2-peer-to-peer-architecture-and-hybrid-computer-system-architecture\",\"https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-5-1-5-how-the-architecture-affects-the-internet-user\",\"https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-4-hash-function\"]}",
"parent_author": "",
"parent_permlink": "blockchain",
"permlink": "blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture",
"title": "Blockchain Foundations Part 1: Distributed, Decentralized and Centralized Computer Architecture"
}
],
"op_in_trx": 0,
"timestamp": "2019-08-21T17:38:39",
"trx_id": "c9eca5f754e07b680650bd91bb93eb9a94f7f4d0",
"trx_in_block": 3,
"virtual_op": 0
}anomalyupvoted (1.00%) @thomasoss / blockchain-foundations-part-4-hash-function2019/08/21 17:37:42
anomalyupvoted (1.00%) @thomasoss / blockchain-foundations-part-4-hash-function
2019/08/21 17:37:42
| author | thomasoss |
| permlink | blockchain-foundations-part-4-hash-function |
| voter | anomaly |
| weight | 100 (1.00%) |
| Transaction Info | Block #35752406/Trx 8562c622c6b0c70a683bdbea0d65fde53b2ae258 |
View Raw JSON Data
{
"block": 35752406,
"op": [
"vote",
{
"author": "thomasoss",
"permlink": "blockchain-foundations-part-4-hash-function",
"voter": "anomaly",
"weight": 100
}
],
"op_in_trx": 0,
"timestamp": "2019-08-21T17:37:42",
"trx_id": "8562c622c6b0c70a683bdbea0d65fde53b2ae258",
"trx_in_block": 14,
"virtual_op": 0
}thomasosspublished a new post: blockchain-foundations-part-4-hash-function2019/08/21 17:36:39
thomasosspublished a new post: blockchain-foundations-part-4-hash-function
2019/08/21 17:36:39
| author | thomasoss |
| body | This article contains basic about hash function. The article is part of a series starting with this article: [Blockchain Foundations Part 1: Distributed, Decentralized and Centralized Computer Architecture](https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture) The articles are drawn from my book "Blockchain and Crypto Currencies Easy to Understand for Everyone, Thomas Bauer". Please refer to the [part 1 article](https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture) for a introduction to the blockchain foundations series. # Hash Function From the point of view of its user a hash function is something very simple. We take any algorithm being able to calculate the so-called hash value from an arbitrary row of bits. This algorithm is free of any random. A certain row of bits always leads to the same hash value, as long we use the same hash algorithm. If the input is not an already existing file but readable text we have to watch for the encoding (UTF-8, ASCII, …) of the input. If we change only one bit of the bit row the algorithm will lead to a completely different hash value. For example, the Bitcoin blockchain uses the SHA-256 (SHA = secure hash algorithm). input value (UTF-8 encoded) | SHA 256 hash value (hexadecimal) ------------ | ------------- 1 | 6b86b273ff34fce19d6b804eff5a3f5747ada4eaa22f1d49c01e52ddb7875b4b 2 | d4735e3a265e16eee03f59718b9b5d03019c07d8b6c51f90da3a666eec13ab35 I am an example | cf7e66b7c62562fb697576c1592a0787dffa4e542b770e28d330ca623f26c381 I am an exampl | 151471b8dcd8d9e7f93282172c3fdab0d356cc6d32944253d062a8df31a5c59e 3000000000000000000000000 | cdb72b05832ff97ffe86f6cf716d45dcd50fbb3b5c4999b6dbd182a8c3ffd0e9 3000000000000000000000001 | 3b54c614f29d96ef8a3250fb56d581d96f19568659f9ee20ff0f660e21b8816e We see that nearly similar input values lead to totally different hash values. The resulting hash value always has the same length independent of the input value length. SHA-256 always delivers a 256 bits hash value. A SHA-256 hash value of the complete Oxford English Dictionary has the same length as the SHA-256 hash value of the number 1. It is important to know that the same input always leads to the same hash value. The hash algorithm is very sensible to every difference of the input value. But it will be deterministic if the input value is the unchanged. A hash value we can derive from everything which can be represented by bit row of any length consisting of 0-values and 1-values: pure text, encrypted text, pictures, file with tax information, pdf file, word file and much more. If we derive a hash value from a content and store the hash value we later can use the hash value to check the content to unchanged. To do the check we again derive the hash value from the value and with an unchanged content we get the same hash value. A hash function is a one-way function. It is not possible to calculate the input value from the hash value. We may find the input value by trial and error. If we knew the input value being a number between 1 and 9, then we could derive the hash value for each of the numbers until we get one identically to the hash value we are searching the input value for. Practically impossible is it to derive the input value from the hash value for example if the input value is a picture. Assumptions about the content are not possible. We even do not know the length of the picture file. There is a chance to find the input value to a hash value if the input is a short row of bits or if we know some details about the input value reducing the possible range of input values considerably. If we do know little about the input value, it is practically impossible to find the input value to a hash value by try and error. A hash value may be derived from a single digit or from the complete Oxford English Dictionary. Of course, small input values may be hacked faster. If the input value for the hash function is three bytes long and a hacker tries out every possible bit combination starting with 0, 1, 00, 01, 11, 000 … then at the latest with reaching 111111111111111111111111 (24 times 1) the hacker will have found the input value. These 24 times 1's equal to decimal 16.777.215. Hence the hacker needs at most about 16,8 million tries for 3 bytes input value. But with a 6 bytes input value we have already about 281 trillion (281.474.976.710.655) possible input values. Another feature of hash functions is important for the blockchain. We cannot predict how a change to an existing bit row will affect the resulting hash value. As described in a later article of this series the Bitcoin mining "puzzle" is nothing else than finding a hash value derived from a block starting with a given number of zeros. The hash value must be the hash of the block content (the transactions enclosed and additional stuff) and an additional field. To this additional field we add a binary 1 until the resulting hash value meets the requirements. The rest of the block remains unchanged. Because there is no way to calculate which value of the additional number leads to a hash value with the required number of leading zeros, we need to add a binary 1 to this additional number until we find a matching hash value. Less important for understanding blockchain is how the hash value is calculated. Hence this is not described in this article series. We only need to know which algorithm is used in each environment. For example, Bitcoin uses among others the SHA-256 hash algorithm. We need to know with which hash algorithm a hash value was calculated in the past if we want to use the hash value to check a content being unchanged. |
| json metadata | {"tags":["blockchain","hash","foundations","encryption"],"links":["https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | blockchain |
| permlink | blockchain-foundations-part-4-hash-function |
| title | Blockchain Foundations Part 4: Hash Function |
| Transaction Info | Block #35752385/Trx 74c7bad627a9c6bd292ea3280e19cfb47b44891b |
View Raw JSON Data
{
"block": 35752385,
"op": [
"comment",
{
"author": "thomasoss",
"body": "This article contains basic about hash function.\n\nThe article is part of a series starting with this article: [Blockchain Foundations Part 1: Distributed, Decentralized and Centralized Computer Architecture](https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture)\n\nThe articles are drawn from my book \"Blockchain and Crypto Currencies Easy to Understand for Everyone, Thomas Bauer\". Please refer to the [part 1 article](https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture) for a introduction to the blockchain foundations series.\n\n# Hash Function\nFrom the point of view of its user a hash function is something very simple. We take any algorithm being able to calculate the so-called hash value from an arbitrary row of bits. This algorithm is free of any random. A certain row of bits always leads to the same hash value, as long we use the same hash algorithm. If the input is not an already existing file but readable text we have to watch for the encoding (UTF-8, ASCII, …) of the input. \n\nIf we change only one bit of the bit row the algorithm will lead to a completely different hash value. \n\nFor example, the Bitcoin blockchain uses the SHA-256 (SHA = secure hash algorithm).\n\ninput value (UTF-8 encoded) | SHA 256 hash value (hexadecimal)\n------------ | -------------\n1 | 6b86b273ff34fce19d6b804eff5a3f5747ada4eaa22f1d49c01e52ddb7875b4b\n2 | d4735e3a265e16eee03f59718b9b5d03019c07d8b6c51f90da3a666eec13ab35\nI am an example | cf7e66b7c62562fb697576c1592a0787dffa4e542b770e28d330ca623f26c381\nI am an exampl | 151471b8dcd8d9e7f93282172c3fdab0d356cc6d32944253d062a8df31a5c59e\n3000000000000000000000000 | cdb72b05832ff97ffe86f6cf716d45dcd50fbb3b5c4999b6dbd182a8c3ffd0e9\n3000000000000000000000001 | 3b54c614f29d96ef8a3250fb56d581d96f19568659f9ee20ff0f660e21b8816e\n\nWe see that nearly similar input values lead to totally different hash values. The resulting hash value always has the same length independent of the input value length. SHA-256 always delivers a 256 bits hash value. A SHA-256 hash value of the complete Oxford English Dictionary has the same length as the SHA-256 hash value of the number 1.\n\nIt is important to know that the same input always leads to the same hash value. The hash algorithm is very sensible to every difference of the input value. But it will be deterministic if the input value is the unchanged. \n\nA hash value we can derive from everything which can be represented by bit row of any length consisting of 0-values and 1-values: pure text, encrypted text, pictures, file with tax information, pdf file, word file and much more.\n\nIf we derive a hash value from a content and store the hash value we later can use the hash value to check the content to unchanged. To do the check we again derive the hash value from the value and with an unchanged content we get the same hash value. \n\nA hash function is a one-way function. It is not possible to calculate the input value from the hash value. We may find the input value by trial and error. If we knew the input value being a number between 1 and 9, then we could derive the hash value for each of the numbers until we get one identically to the hash value we are searching the input value for. \n\nPractically impossible is it to derive the input value from the hash value for example if the input value is a picture. Assumptions about the content are not possible. We even do not know the length of the picture file. \n\nThere is a chance to find the input value to a hash value if the input is a short row of bits or if we know some details about the input value reducing the possible range of input values considerably.\n\nIf we do know little about the input value, it is practically impossible to find the input value to a hash value by try and error. A hash value may be derived from a single digit or from the complete Oxford English Dictionary. \n\nOf course, small input values may be hacked faster. If the input value for the hash function is three bytes long and a hacker tries out every possible bit combination starting with 0, 1, 00, 01, 11, 000 … then at the latest with reaching 111111111111111111111111 (24 times 1) the hacker will have found the input value. These 24 times 1's equal to decimal 16.777.215. Hence the hacker needs at most about 16,8 million tries for 3 bytes input value. But with a 6 bytes input value we have already about 281 trillion (281.474.976.710.655) possible input values. \n\nAnother feature of hash functions is important for the blockchain. We cannot predict how a change to an existing bit row will affect the resulting hash value. As described in a later article of this series the Bitcoin mining \"puzzle\" is nothing else than finding a hash value derived from a block starting with a given number of zeros. The hash value must be the hash of the block content (the transactions enclosed and additional stuff) and an additional field. To this additional field we add a binary 1 until the resulting hash value meets the requirements. The rest of the block remains unchanged. Because there is no way to calculate which value of the additional number leads to a hash value with the required number of leading zeros, we need to add a binary 1 to this additional number until we find a matching hash value.\n\nLess important for understanding blockchain is how the hash value is calculated. Hence this is not described in this article series. We only need to know which algorithm is used in each environment. For example, Bitcoin uses among others the SHA-256 hash algorithm. \n\nWe need to know with which hash algorithm a hash value was calculated in the past if we want to use the hash value to check a content being unchanged.",
"json_metadata": "{\"tags\":[\"blockchain\",\"hash\",\"foundations\",\"encryption\"],\"links\":[\"https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "blockchain",
"permlink": "blockchain-foundations-part-4-hash-function",
"title": "Blockchain Foundations Part 4: Hash Function"
}
],
"op_in_trx": 0,
"timestamp": "2019-08-21T17:36:39",
"trx_id": "74c7bad627a9c6bd292ea3280e19cfb47b44891b",
"trx_in_block": 9,
"virtual_op": 0
}2019/08/19 05:07:21
2019/08/19 05:07:21
| author | boosta |
| permlink | pwgjdl |
| voter | thomasoss |
| weight | 10000 (100.00%) |
| Transaction Info | Block #35679913/Trx 0e46e5479eb6464f66552e90ae9cda6828ef4050 |
View Raw JSON Data
{
"block": 35679913,
"op": [
"vote",
{
"author": "boosta",
"permlink": "pwgjdl",
"voter": "thomasoss",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2019-08-19T05:07:21",
"trx_id": "0e46e5479eb6464f66552e90ae9cda6828ef4050",
"trx_in_block": 0,
"virtual_op": 0
}boostareplied to @thomasoss / pwgjdl2019/08/19 00:15:21
boostareplied to @thomasoss / pwgjdl
2019/08/19 00:15:21
| author | boosta |
| body | Is that your thinking? I agree with everything you said. |
| json metadata | {"tags":["blockchain"],"app":"steemit/0.1"} |
| parent author | thomasoss |
| parent permlink | pwfztk |
| permlink | pwgjdl |
| title | |
| Transaction Info | Block #35674084/Trx 68e8122a286956834949332455e4aa9932570c40 |
View Raw JSON Data
{
"block": 35674084,
"op": [
"comment",
{
"author": "boosta",
"body": "Is that your thinking? I agree with everything you said.",
"json_metadata": "{\"tags\":[\"blockchain\"],\"app\":\"steemit/0.1\"}",
"parent_author": "thomasoss",
"parent_permlink": "pwfztk",
"permlink": "pwgjdl",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2019-08-19T00:15:21",
"trx_id": "68e8122a286956834949332455e4aa9932570c40",
"trx_in_block": 13,
"virtual_op": 0
}2019/08/18 20:52:39
2019/08/18 20:52:39
| author | steemitboard |
| body | Congratulations @thomasoss! You have completed the following achievement on the Steem blockchain and have been rewarded with new badge(s) : <table><tr><td><img src="https://steemitimages.com/60x70/http://steemitboard.com/@thomasoss/voted.png?201908182009"></td><td>You received more than 10 upvotes. Your next target is to reach 50 upvotes.</td></tr> </table> <sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@thomasoss) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=thomasoss)_</sub> <sub>_If you no longer want to receive notifications, reply to this comment with the word_ `STOP`</sub> ###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| parent author | thomasoss |
| parent permlink | blockchain-foundations-part-1-5-1-5-how-the-architecture-affects-the-internet-user |
| permlink | steemitboard-notify-thomasoss-20190818t205241000z |
| title | |
| Transaction Info | Block #35670036/Trx a4adfea121ca1a4a28c325457fd2be1a43af9296 |
View Raw JSON Data
{
"block": 35670036,
"op": [
"comment",
{
"author": "steemitboard",
"body": "Congratulations @thomasoss! You have completed the following achievement on the Steem blockchain and have been rewarded with new badge(s) :\n\n<table><tr><td><img src=\"https://steemitimages.com/60x70/http://steemitboard.com/@thomasoss/voted.png?201908182009\"></td><td>You received more than 10 upvotes. Your next target is to reach 50 upvotes.</td></tr>\n</table>\n\n<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@thomasoss) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=thomasoss)_</sub>\n<sub>_If you no longer want to receive notifications, reply to this comment with the word_ `STOP`</sub>\n\n\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}",
"parent_author": "thomasoss",
"parent_permlink": "blockchain-foundations-part-1-5-1-5-how-the-architecture-affects-the-internet-user",
"permlink": "steemitboard-notify-thomasoss-20190818t205241000z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2019-08-18T20:52:39",
"trx_id": "a4adfea121ca1a4a28c325457fd2be1a43af9296",
"trx_in_block": 23,
"virtual_op": 0
}boostaupvoted (5.00%) @thomasoss / pwfztk2019/08/18 18:47:48
boostaupvoted (5.00%) @thomasoss / pwfztk
2019/08/18 18:47:48
| author | thomasoss |
| permlink | pwfztk |
| voter | boosta |
| weight | 500 (5.00%) |
| Transaction Info | Block #35667546/Trx b094ed18a9838cf175ed414ce3da827651961c6d |
View Raw JSON Data
{
"block": 35667546,
"op": [
"vote",
{
"author": "thomasoss",
"permlink": "pwfztk",
"voter": "boosta",
"weight": 500
}
],
"op_in_trx": 0,
"timestamp": "2019-08-18T18:47:48",
"trx_id": "b094ed18a9838cf175ed414ce3da827651961c6d",
"trx_in_block": 29,
"virtual_op": 0
}thomasossupvoted (100.00%) @fleetinuance / does-up-voting-something-cost-you-money2019/08/18 17:38:27
thomasossupvoted (100.00%) @fleetinuance / does-up-voting-something-cost-you-money
2019/08/18 17:38:27
| author | fleetinuance |
| permlink | does-up-voting-something-cost-you-money |
| voter | thomasoss |
| weight | 10000 (100.00%) |
| Transaction Info | Block #35666164/Trx fe9befb697d1466ac3c3df82929b472e487ac52c |
View Raw JSON Data
{
"block": 35666164,
"op": [
"vote",
{
"author": "fleetinuance",
"permlink": "does-up-voting-something-cost-you-money",
"voter": "thomasoss",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2019-08-18T17:38:27",
"trx_id": "fe9befb697d1466ac3c3df82929b472e487ac52c",
"trx_in_block": 7,
"virtual_op": 0
}thomasossupvoted (100.00%) @boosta / blockchain-no-bicycle-chain2019/08/18 17:37:12
thomasossupvoted (100.00%) @boosta / blockchain-no-bicycle-chain
2019/08/18 17:37:12
| author | boosta |
| permlink | blockchain-no-bicycle-chain |
| voter | thomasoss |
| weight | 10000 (100.00%) |
| Transaction Info | Block #35666139/Trx 40d0fc56f3f54fe0f3e495459927db786a937d59 |
View Raw JSON Data
{
"block": 35666139,
"op": [
"vote",
{
"author": "boosta",
"permlink": "blockchain-no-bicycle-chain",
"voter": "thomasoss",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2019-08-18T17:37:12",
"trx_id": "40d0fc56f3f54fe0f3e495459927db786a937d59",
"trx_in_block": 24,
"virtual_op": 0
}2019/08/18 17:14:54
2019/08/18 17:14:54
| author | thomasoss |
| body | @@ -520,18 +520,19 @@ future. -An +The blockch |
| json metadata | {"tags":["blockchain"],"app":"steemit/0.1"} |
| parent author | boosta |
| parent permlink | blockchain-no-bicycle-chain |
| permlink | pwfztk |
| title | |
| Transaction Info | Block #35665693/Trx 03a823a317e80d8aa656c7b7ff8e50b511356fdd |
View Raw JSON Data
{
"block": 35665693,
"op": [
"comment",
{
"author": "thomasoss",
"body": "@@ -520,18 +520,19 @@\n future. \n-An\n+The\n blockch\n",
"json_metadata": "{\"tags\":[\"blockchain\"],\"app\":\"steemit/0.1\"}",
"parent_author": "boosta",
"parent_permlink": "blockchain-no-bicycle-chain",
"permlink": "pwfztk",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2019-08-18T17:14:54",
"trx_id": "03a823a317e80d8aa656c7b7ff8e50b511356fdd",
"trx_in_block": 9,
"virtual_op": 0
}2019/08/18 17:14:30
2019/08/18 17:14:30
| author | thomasoss |
| body | @@ -502,16 +502,18 @@ process +es is the |
| json metadata | {"tags":["blockchain"],"app":"steemit/0.1"} |
| parent author | boosta |
| parent permlink | blockchain-no-bicycle-chain |
| permlink | pwfztk |
| title | |
| Transaction Info | Block #35665685/Trx 2212a9224e18649c131be4412bf5800a3734ae29 |
View Raw JSON Data
{
"block": 35665685,
"op": [
"comment",
{
"author": "thomasoss",
"body": "@@ -502,16 +502,18 @@\n process\n+es\n is the \n",
"json_metadata": "{\"tags\":[\"blockchain\"],\"app\":\"steemit/0.1\"}",
"parent_author": "boosta",
"parent_permlink": "blockchain-no-bicycle-chain",
"permlink": "pwfztk",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2019-08-18T17:14:30",
"trx_id": "2212a9224e18649c131be4412bf5800a3734ae29",
"trx_in_block": 14,
"virtual_op": 0
}2019/08/18 17:14:03
2019/08/18 17:14:03
| author | thomasoss |
| body | @@ -387,17 +387,19 @@ y needs -a +the blockch @@ -401,16 +401,23 @@ ockchain + itself . But ev |
| json metadata | {"tags":["blockchain"],"app":"steemit/0.1"} |
| parent author | boosta |
| parent permlink | blockchain-no-bicycle-chain |
| permlink | pwfztk |
| title | |
| Transaction Info | Block #35665676/Trx 1d0d6a7acbd86553071087fcd83dfbbca702fd64 |
View Raw JSON Data
{
"block": 35665676,
"op": [
"comment",
{
"author": "thomasoss",
"body": "@@ -387,17 +387,19 @@\n y needs \n-a\n+the\n blockch\n@@ -401,16 +401,23 @@\n ockchain\n+ itself\n . But ev\n",
"json_metadata": "{\"tags\":[\"blockchain\"],\"app\":\"steemit/0.1\"}",
"parent_author": "boosta",
"parent_permlink": "blockchain-no-bicycle-chain",
"permlink": "pwfztk",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2019-08-18T17:14:03",
"trx_id": "1d0d6a7acbd86553071087fcd83dfbbca702fd64",
"trx_in_block": 27,
"virtual_op": 0
}2019/08/18 17:12:57
2019/08/18 17:12:57
| author | thomasoss |
| body | I think today everything is faster. The information amount you have to deal with daily is immense. And 5 years is a mega step in technology. 66 years like in your example is more than the business live of a human being. Of course, blockchain will be faster. And if the concept will not lead to the promised - it will disappeare as fast as it got a hype. But, this will not happen. Nobody needs a blockchain. But everybody knows that the digitalization and tokenizing of inter-company business process is the future. An blockchain is one important concept to support this. By the way, good concepts are stable over decades. Most of the basic concepts of computer science have been the fundament of the digitalization for decades now. And these concepts are still unchanged and valid. For me, Blockchain is another fundamental concept. |
| json metadata | {"tags":["blockchain"],"app":"steemit/0.1"} |
| parent author | boosta |
| parent permlink | blockchain-no-bicycle-chain |
| permlink | pwfztk |
| title | |
| Transaction Info | Block #35665654/Trx 3827008b0d8d1747b74952d0ea7b42c8c00636a6 |
View Raw JSON Data
{
"block": 35665654,
"op": [
"comment",
{
"author": "thomasoss",
"body": "I think today everything is faster. The information amount you have to deal with daily is immense. And 5 years is a mega step in technology. 66 years like in your example is more than the business live of a human being. Of course, blockchain will be faster. And if the concept will not lead to the promised - it will disappeare as fast as it got a hype. But, this will not happen. Nobody needs a blockchain. But everybody knows that the digitalization and tokenizing of inter-company business process is the future. An blockchain is one important concept to support this. By the way, good concepts are stable over decades. Most of the basic concepts of computer science have been the fundament of the digitalization for decades now. And these concepts are still unchanged and valid. For me, Blockchain is another fundamental concept.",
"json_metadata": "{\"tags\":[\"blockchain\"],\"app\":\"steemit/0.1\"}",
"parent_author": "boosta",
"parent_permlink": "blockchain-no-bicycle-chain",
"permlink": "pwfztk",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2019-08-18T17:12:57",
"trx_id": "3827008b0d8d1747b74952d0ea7b42c8c00636a6",
"trx_in_block": 22,
"virtual_op": 0
}thomasossfollowed @bitsignal2019/08/18 16:56:00
thomasossfollowed @bitsignal
2019/08/18 16:56:00
| id | follow |
| json | ["follow",{"follower":"thomasoss","following":"bitsignal","what":["blog"]}] |
| required auths | [] |
| required posting auths | ["thomasoss"] |
| Transaction Info | Block #35665316/Trx c02522c032c30b071fc68320a6fad2e157865655 |
View Raw JSON Data
{
"block": 35665316,
"op": [
"custom_json",
{
"id": "follow",
"json": "[\"follow\",{\"follower\":\"thomasoss\",\"following\":\"bitsignal\",\"what\":[\"blog\"]}]",
"required_auths": [],
"required_posting_auths": [
"thomasoss"
]
}
],
"op_in_trx": 0,
"timestamp": "2019-08-18T16:56:00",
"trx_id": "c02522c032c30b071fc68320a6fad2e157865655",
"trx_in_block": 0,
"virtual_op": 0
}thomasossupvoted (100.00%) @bitsignal / bismuth-blockchain-tech-team-progress-report-august-16-20192019/08/18 16:55:42
thomasossupvoted (100.00%) @bitsignal / bismuth-blockchain-tech-team-progress-report-august-16-2019
2019/08/18 16:55:42
| author | bitsignal |
| permlink | bismuth-blockchain-tech-team-progress-report-august-16-2019 |
| voter | thomasoss |
| weight | 10000 (100.00%) |
| Transaction Info | Block #35665310/Trx b3f1bd7b9aab82407513741a7c5ecab4771ab49f |
View Raw JSON Data
{
"block": 35665310,
"op": [
"vote",
{
"author": "bitsignal",
"permlink": "bismuth-blockchain-tech-team-progress-report-august-16-2019",
"voter": "thomasoss",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2019-08-18T16:55:42",
"trx_id": "b3f1bd7b9aab82407513741a7c5ecab4771ab49f",
"trx_in_block": 18,
"virtual_op": 0
}2019/08/16 22:03:06
2019/08/16 22:03:06
| author | aekraj |
| body | Welcome to the STEEM!! I hope you having a great day.I am also new to steemit and learning about steem too. Here is something that will help you to get more steem and make it easy to use Partiko Partiko is an app which is very fast, and you can earn partiko points too. if you wanna give it a go then here is a link to download the Partiko app https://partiko.app/referral/aekraj You will get extra 3500 partiko points which you can transfer to steem. 2nd is Actifit app it helps you to track exercise and daily activity and get an upvote, here is a link to download the actifit app https://actifit.io/signup?referrer=aekraj 3rd is steemsmart where you can deligate your power, votes and get more steem https://smartsteem.com?r=aekraj If you want to get upvotes everyday then join curation trail of @sharingiscaring1 at steemauto.com here is the link for setup https://bit.ly/2Z4VvuQ The official FAQ can be found here https://steemit.com/faq.html and it has lots of information. If you need any help I'm just a message away. let me know if you got any helpful app/article Thank you @aekraj If Follow me = get more random upvotes @aekraj Posted using [Partiko Android](https://partiko.app/referral/aekraj) |
| json metadata | {"app":"partiko","client":"android"} |
| parent author | thomasoss |
| parent permlink | blockchain-foundations-part-1-5-1-5-how-the-architecture-affects-the-internet-user |
| permlink | aekraj-re-thomasoss-blockchain-foundations-part-1-5-1-5-how-the-architecture-affects-the-internet-user-20190816t220304792z |
| title | |
| Transaction Info | Block #35613957/Trx 0015f8399d06839f4dbcb394602fc7cb1ec80b51 |
View Raw JSON Data
{
"block": 35613957,
"op": [
"comment",
{
"author": "aekraj",
"body": "Welcome to the STEEM!!\n\nI hope you having a great day.I am also new to steemit and learning about steem too. Here is something that will help you to get more steem and make it easy to use\n\n\nPartiko\nPartiko is an app which is very fast, and you can earn partiko points too. if you wanna give it a go then here is a link to download the Partiko app https://partiko.app/referral/aekraj\nYou will get extra 3500 partiko points which you can transfer to steem.\n\n\n2nd is Actifit app it helps you to track exercise and daily activity and get an upvote,\nhere is a link to download the actifit app https://actifit.io/signup?referrer=aekraj\n\n3rd is steemsmart where you can deligate your power, votes and get more steem https://smartsteem.com?r=aekraj\n\nIf you want to get upvotes everyday then join curation trail of @sharingiscaring1 at steemauto.com\nhere is the link for setup https://bit.ly/2Z4VvuQ\n\nThe official FAQ can be found here https://steemit.com/faq.html and it has lots of information. \n\nIf you need any help I'm just a message away.\n\nlet me know if you got any helpful app/article\n\nThank you\n@aekraj\n\nIf Follow me = get more random upvotes @aekraj\n\nPosted using [Partiko Android](https://partiko.app/referral/aekraj)",
"json_metadata": "{\"app\":\"partiko\",\"client\":\"android\"}",
"parent_author": "thomasoss",
"parent_permlink": "blockchain-foundations-part-1-5-1-5-how-the-architecture-affects-the-internet-user",
"permlink": "aekraj-re-thomasoss-blockchain-foundations-part-1-5-1-5-how-the-architecture-affects-the-internet-user-20190816t220304792z",
"title": ""
}
],
"op_in_trx": 0,
"timestamp": "2019-08-16T22:03:06",
"trx_id": "0015f8399d06839f4dbcb394602fc7cb1ec80b51",
"trx_in_block": 2,
"virtual_op": 0
}thomasossremoved vote from (0.00%) @blockchainbeach / howblockchainisassistingtheenergysector-m5ba7j60662019/08/15 07:56:21
thomasossremoved vote from (0.00%) @blockchainbeach / howblockchainisassistingtheenergysector-m5ba7j6066
2019/08/15 07:56:21
| author | blockchainbeach |
| permlink | howblockchainisassistingtheenergysector-m5ba7j6066 |
| voter | thomasoss |
| weight | 0 (0.00%) |
| Transaction Info | Block #35568296/Trx 05b436a443fb4505ff0b682994354adfeb03deb8 |
View Raw JSON Data
{
"block": 35568296,
"op": [
"vote",
{
"author": "blockchainbeach",
"permlink": "howblockchainisassistingtheenergysector-m5ba7j6066",
"voter": "thomasoss",
"weight": 0
}
],
"op_in_trx": 0,
"timestamp": "2019-08-15T07:56:21",
"trx_id": "05b436a443fb4505ff0b682994354adfeb03deb8",
"trx_in_block": 23,
"virtual_op": 0
}thomasossupvoted (100.00%) @blockchainbeach / howblockchainisassistingtheenergysector-m5ba7j60662019/08/15 07:55:27
thomasossupvoted (100.00%) @blockchainbeach / howblockchainisassistingtheenergysector-m5ba7j6066
2019/08/15 07:55:27
| author | blockchainbeach |
| permlink | howblockchainisassistingtheenergysector-m5ba7j6066 |
| voter | thomasoss |
| weight | 10000 (100.00%) |
| Transaction Info | Block #35568278/Trx 3757221d78d59a5ecc06e14514632e511b9fca2f |
View Raw JSON Data
{
"block": 35568278,
"op": [
"vote",
{
"author": "blockchainbeach",
"permlink": "howblockchainisassistingtheenergysector-m5ba7j6066",
"voter": "thomasoss",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2019-08-15T07:55:27",
"trx_id": "3757221d78d59a5ecc06e14514632e511b9fca2f",
"trx_in_block": 15,
"virtual_op": 0
}thomasossupvoted (100.00%) @thebitcoinnews / bikicomgatewaytoglobalization-kt06sn54dd2019/08/15 07:53:00
thomasossupvoted (100.00%) @thebitcoinnews / bikicomgatewaytoglobalization-kt06sn54dd
2019/08/15 07:53:00
| author | thebitcoinnews |
| permlink | bikicomgatewaytoglobalization-kt06sn54dd |
| voter | thomasoss |
| weight | 10000 (100.00%) |
| Transaction Info | Block #35568229/Trx 059b5a570d27cfe9580fbb1a7bb019c96ab22b7d |
View Raw JSON Data
{
"block": 35568229,
"op": [
"vote",
{
"author": "thebitcoinnews",
"permlink": "bikicomgatewaytoglobalization-kt06sn54dd",
"voter": "thomasoss",
"weight": 10000
}
],
"op_in_trx": 0,
"timestamp": "2019-08-15T07:53:00",
"trx_id": "059b5a570d27cfe9580fbb1a7bb019c96ab22b7d",
"trx_in_block": 4,
"virtual_op": 0
}2019/08/15 07:51:06
2019/08/15 07:51:06
| author | thomasoss |
| body | This article is about peer-to-peer architecture and hyprid computer system architecture. The article is part of a series starting with this article: [Blockchain Foundations Part 1: Distributed, Decentralized and Centralized Computer Architecture](https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture) The articles are drawn from my book "Blockchain and Crypto Currencies Easy to Understand for Everyone, Thomas Bauer". Please refer to the [part 1 article](https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture) for a introduction to the blockchain foundations series. # Blockchain is a Peer-to-Peer Architecture Bitcoin is a peer-to-peer application. Each participant of the network with his or her computer or mobile is a peer. Each peer can do all the tasks necessary to run the application: User Interface, application logic, storage of data. Each peer is equal in a transaction, it may be the server or the client. As server, the peer provides services to other peers. As client, the peer uses services provided by other peers. From the point of view of the end user all together appears to be one single system. For using a service provided by another peer no intermediary is needed. In a "pure" blockchain each peer is hosting the same software and the complete database on its computer. Or to say it in "blockchain": On each peer are the same smart contracts, the same ledger and the same state. The explanation of these terms you will find, if you continue reading this article series. Such a peer-to-peer computer system is a decentralized distributed computer system. Programs and data are not hold on central system but in fact each peer holds all the programs and all the data. Practically certain users of a blockchain application take over the role of hosting all the programs and data. In Bitcoin, they are called full nodes. Another alternative are service providers hosting the data. All other participants of the community access those full nodes or the service provider and do not need to keep all programs and data on their own computer. But, at the end for each community member it should be possible to load all programs and data on its computer. And there must be enough peers who do so. Only with a high number of peers holding all programs and data a decentralized distributed computer system provides a high resilience and fraud-resistance and a high protection against data loss. In the subsequent figure we see a pure peer-to-peer system on the left side. On the right side we see a architecture with a service provider hosting a peer on its computer system to be used by users who do not want to hold a full peer on their computer or mobile. The figure shows a lot of connections. In one transaction, usually only two or a few peers take part. But in a blockchain huge traffic takes place through mining and validating transactions and through distributing new mined and validated blocks to every peer. We will learn more about this later in this article series.  Figure 4: Pure peer-to-peer computer system and a variation with a peer service provider (schematically) Again, it is important what point of view we have. If we drill down into a peer-to-peer-computer system layer by layer we won't find a pure peer-to-peer system on each layer. The telecommunication service provider for example is an intermediary necessary to run our peer-to-peer system. But in the point of view of the blockchain user we see a peer-to-peer application. Each user of the Bitcoin blockchain for example can exchange Bitcoins with each other person on the world without an intermediary in the middle. And everyone is free to do mining or validating jobs within the Bitcoin network. Of course, it is not as simple as that. For example for Bitcoin mining you must provide suitable hardware. You cannot do it from your mobile. # Hybrid Computer System Architectures Nearly every computer system is a mix of centralized and decentralized distributed architecture. And we always should consider the point of view we are looking from at the architecture. Look at a pure centralized computer center of a trading platform that is distributed over three locations. Technically this is a decentralized distributed computer system. But from the point of view of a user of the platform it is a pure centralized structure, because all the programs und data are stored at the trading platform's computer system. The well-known client server computer system is a centralized distributed computer system. All shared data and programs are located on a central server. The clients may hold additional data and programs. And they may have copies of data and programs lying on the central server. But the central server is always right. A client always must take over the date and programs from the server and not the other way around. |
| json metadata | {"tags":["blockchain","introduction","architecture","decentralized","peer"],"image":["https://cdn.steemitimages.com/DQmUPDqudzXfykwfCfZ12nstqnK6P4tYwCL68kudGmQk6yJ/image.png"],"links":["https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture"],"app":"steemit/0.1","format":"markdown"} |
| parent author | |
| parent permlink | blockchain |
| permlink | blockchain-foundations-part-2-peer-to-peer-architecture-and-hybrid-computer-system-architecture |
| title | Blockchain Foundations Part 2: Peer-to-Peer Architecture and Hybrid Computer System Architecture |
| Transaction Info | Block #35568191/Trx e3dddd306fd6b592134aa06b6177f85808c26bbf |
View Raw JSON Data
{
"block": 35568191,
"op": [
"comment",
{
"author": "thomasoss",
"body": "This article is about peer-to-peer architecture and hyprid computer system architecture.\n\nThe article is part of a series starting with this article: [Blockchain Foundations Part 1: Distributed, Decentralized and Centralized Computer Architecture](https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture)\n\nThe articles are drawn from my book \"Blockchain and Crypto Currencies Easy to Understand for Everyone, Thomas Bauer\". Please refer to the [part 1 article](https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture) for a introduction to the blockchain foundations series.\n\n# Blockchain is a Peer-to-Peer Architecture\n\nBitcoin is a peer-to-peer application. Each participant of the network with his or her computer or mobile is a peer. Each peer can do all the tasks necessary to run the application: User Interface, application logic, storage of data.\n\nEach peer is equal in a transaction, it may be the server or the client. As server, the peer provides services to other peers. As client, the peer uses services provided by other peers. From the point of view of the end user all together appears to be one single system.\n\nFor using a service provided by another peer no intermediary is needed.\n\nIn a \"pure\" blockchain each peer is hosting the same software and the complete database on its computer. Or to say it in \"blockchain\": On each peer are the same smart contracts, the same ledger and the same state. The explanation of these terms you will find, if you continue reading this article series.\n\nSuch a peer-to-peer computer system is a decentralized distributed computer system. Programs and data are not hold on central system but in fact each peer holds all the programs and all the data.\n\nPractically certain users of a blockchain application take over the role of hosting all the programs and data. In Bitcoin, they are called full nodes. Another alternative are service providers hosting the data. All other participants of the community access those full nodes or the service provider and do not need to keep all programs and data on their own computer. But, at the end for each community member it should be possible to load all programs and data on its computer. And there must be enough peers who do so. Only with a high number of peers holding all programs and data a decentralized distributed computer system provides a high resilience and fraud-resistance and a high protection against data loss.\n\nIn the subsequent figure we see a pure peer-to-peer system on the left side. On the right side we see a architecture with a service provider hosting a peer on its computer system to be used by users who do not want to hold a full peer on their computer or mobile. The figure shows a lot of connections. In one transaction, usually only two or a few peers take part. But in a blockchain huge traffic takes place through mining and validating transactions and through distributing new mined and validated blocks to every peer. We will learn more about this later in this article series. \n\n\nFigure 4: Pure peer-to-peer computer system and a variation with a peer service provider (schematically)\n\nAgain, it is important what point of view we have. If we drill down into a peer-to-peer-computer system layer by layer we won't find a pure peer-to-peer system on each layer. The telecommunication service provider for example is an intermediary necessary to run our peer-to-peer system. But in the point of view of the blockchain user we see a peer-to-peer application. Each user of the Bitcoin blockchain for example can exchange Bitcoins with each other person on the world without an intermediary in the middle. And everyone is free to do mining or validating jobs within the Bitcoin network. Of course, it is not as simple as that. For example for Bitcoin mining you must provide suitable hardware. You cannot do it from your mobile.\n\n# Hybrid Computer System Architectures\n\nNearly every computer system is a mix of centralized and decentralized distributed architecture. And we always should consider the point of view we are looking from at the architecture.\n\nLook at a pure centralized computer center of a trading platform that is distributed over three locations. Technically this is a decentralized distributed computer system. But from the point of view of a user of the platform it is a pure centralized structure, because all the programs und data are stored at the trading platform's computer system.\n\nThe well-known client server computer system is a centralized distributed computer system. All shared data and programs are located on a central server. The clients may hold additional data and programs. And they may have copies of data and programs lying on the central server. But the central server is always right. A client always must take over the date and programs from the server and not the other way around.",
"json_metadata": "{\"tags\":[\"blockchain\",\"introduction\",\"architecture\",\"decentralized\",\"peer\"],\"image\":[\"https://cdn.steemitimages.com/DQmUPDqudzXfykwfCfZ12nstqnK6P4tYwCL68kudGmQk6yJ/image.png\"],\"links\":[\"https://steemit.com/blockchain/@thomasoss/blockchain-foundations-part-1-distributed-decentralized-and-centralized-computer-architecture\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
"parent_author": "",
"parent_permlink": "blockchain",
"permlink": "blockchain-foundations-part-2-peer-to-peer-architecture-and-hybrid-computer-system-architecture",
"title": "Blockchain Foundations Part 2: Peer-to-Peer Architecture and Hybrid Computer System Architecture"
}
],
"op_in_trx": 0,
"timestamp": "2019-08-15T07:51:06",
"trx_id": "e3dddd306fd6b592134aa06b6177f85808c26bbf",
"trx_in_block": 15,
"virtual_op": 0
}Manabar
Voting Power100.00%
Downvote Power100.00%
Resource Credits100.00%
Reputation Progress41.18%
{
"voting_manabar": {
"current_mana": "83029220073",
"last_update_time": 1649828742
},
"downvote_manabar": {
"current_mana": "21180923488",
"last_update_time": 1649828742
},
"rc_account": {
"account": "thomasoss",
"max_rc": "86744442926",
"max_rc_creation_adjustment": {
"amount": "2020748973",
"nai": "@@000000037",
"precision": 6
},
"rc_manabar": {
"current_mana": "86677080388",
"last_update_time": 1653230661
}
}
}Account Metadata
| POSTING JSON METADATA | |
| profile | {"name":"Thomas","about":"Computer Scientist, software architect, Java programmer, mainframe specialist, project manager","location":"Munich, Germany","cover_image":"https://steemitimages.com/0x0/http://i.imgur.com/wHMAhxy.jpg","profile_image":"https://cdn.steemitimages.com/DQmYcL4i2C3q5yqGH6avREovheJvHzkjF2ibkaELQyqPDAR/P1080321.JPG"} |
| JSON METADATA | |
| profile | {"name":"Thomas","about":"Computer Scientist, software architect, Java programmer, mainframe specialist, project manager","location":"Munich, Germany","cover_image":"https://steemitimages.com/0x0/http://i.imgur.com/wHMAhxy.jpg","profile_image":"https://cdn.steemitimages.com/DQmYcL4i2C3q5yqGH6avREovheJvHzkjF2ibkaELQyqPDAR/P1080321.JPG"} |
{
"posting_json_metadata": {
"profile": {
"name": "Thomas",
"about": "Computer Scientist, software architect, Java programmer, mainframe specialist, project manager",
"location": "Munich, Germany",
"cover_image": "https://steemitimages.com/0x0/http://i.imgur.com/wHMAhxy.jpg",
"profile_image": "https://cdn.steemitimages.com/DQmYcL4i2C3q5yqGH6avREovheJvHzkjF2ibkaELQyqPDAR/P1080321.JPG"
}
},
"json_metadata": {
"profile": {
"name": "Thomas",
"about": "Computer Scientist, software architect, Java programmer, mainframe specialist, project manager",
"location": "Munich, Germany",
"cover_image": "https://steemitimages.com/0x0/http://i.imgur.com/wHMAhxy.jpg",
"profile_image": "https://cdn.steemitimages.com/DQmYcL4i2C3q5yqGH6avREovheJvHzkjF2ibkaELQyqPDAR/P1080321.JPG"
}
}
}Auth Keys
Owner
Single Signature
Public Keys
STM5szVtUx4nfZq9pjwqTxsPHMpGyFLSsKoNE2zNjAyefF2tWpszb1/1
Active
Single Signature
Public Keys
STM63WeGsis3XyiHWozNZc8khRLBV4MjUujdn58gienX8mEdSJztv1/1
Posting
Single Signature
Public Keys
STM7N4TaktJpumgXobB2t2ofthdpG1umy35KAi35rv7SPHz73R1cr1/1
Memo
STM84nXo7phwufo1t7T6KepGrJvRWWMDHcxtSemMD62V1HGEkmRN1
{
"owner": {
"account_auths": [],
"key_auths": [
[
"STM5szVtUx4nfZq9pjwqTxsPHMpGyFLSsKoNE2zNjAyefF2tWpszb",
1
]
],
"weight_threshold": 1
},
"active": {
"account_auths": [],
"key_auths": [
[
"STM63WeGsis3XyiHWozNZc8khRLBV4MjUujdn58gienX8mEdSJztv",
1
]
],
"weight_threshold": 1
},
"posting": {
"account_auths": [],
"key_auths": [
[
"STM7N4TaktJpumgXobB2t2ofthdpG1umy35KAi35rv7SPHz73R1cr",
1
]
],
"weight_threshold": 1
},
"memo": "STM84nXo7phwufo1t7T6KepGrJvRWWMDHcxtSemMD62V1HGEkmRN1"
}Witness Votes
0 / 30
No active witness votes.
[]