VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS23.64%
Net Worth
0.456USD
STEEM
0.005STEEM
SBD
0.034SBD
Own SP
8.105SP
Detailed Balance
| STEEM | ||
| balance | 0.005STEEM | STEEM |
| market_balance | 0.000STEEM | STEEM |
| savings_balance | 0.000STEEM | STEEM |
| reward_steem_balance | 0.000STEEM | STEEM |
| STEEM POWER | ||
| Own SP | 8.105SP | SP |
| Delegated Out | 0.000SP | SP |
| Delegation In | 0.000SP | SP |
| Effective Power | 8.105SP | SP |
| Reward SP (pending) | 0.000SP | SP |
| SBD | ||
| sbd_balance | 0.034SBD | 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.005 STEEM",
"savings_balance": "0.000 STEEM",
"reward_steem_balance": "0.000 STEEM",
"vesting_shares": "13198.167288 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "0.000000 VESTS",
"sbd_balance": "0.034 SBD",
"savings_sbd_balance": "0.000 SBD",
"reward_sbd_balance": "0.000 SBD",
"conversions": []
}Account Info
| name | sweetwilliam |
| id | 401329 |
| rank | 145,745 |
| reputation | 106234033682 |
| created | 2017-10-08T16:37:21 |
| recovery_account | steem |
| proxy | None |
| post_count | 9 |
| comment_count | 0 |
| lifetime_vote_count | 0 |
| witnesses_voted_for | 0 |
| last_post | 2018-05-09T19:01:57 |
| last_root_post | 2018-05-09T19:01:57 |
| last_vote_time | 2018-05-10T15:33:09 |
| proxied_vsf_votes | 0, 0, 0, 0 |
| can_vote | 1 |
| voting_power | 0 |
| delayed_votes | 0 |
| balance | 0.005 STEEM |
| savings_balance | 0.000 STEEM |
| sbd_balance | 0.034 SBD |
| savings_sbd_balance | 0.000 SBD |
| vesting_shares | 13198.167288 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 | 2017-10-13T13:18:51 |
| mined | No |
| sbd_seconds | 0 |
| sbd_last_interest_payment | 2018-06-30T19:28:24 |
| savings_sbd_last_interest_payment | 1970-01-01T00:00:00 |
{
"id": 401329,
"name": "sweetwilliam",
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5DKurwofXtEMzrRyBppLW4BZNBqmz1WHjriqHsjFqpeg4dgvCJ",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM6K4qMtvkEswM5ZtuU43PuKqfc7kDMdpZ6YQyaFeoyzu4kcgU6P",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7TScX1JAr93Dr6xLyczvDbBZYhgujK7Gd1YQ68CFrem17ZWzV5",
1
]
]
},
"memo_key": "STM5bVSmKzPAHHQF4EL1VEKJjUazHDoyS2VetoodcHZpfbWWbtbz7",
"json_metadata": "{\"profile\":{\"location\":\"Planet Earth\",\"about\":\"alien, crypto enthusiast, vipassana meditator\",\"profile_image\":\"https://s1.postimg.org/4u0w6z63db/profile6.jpg\",\"cover_image\":\"https://s1.postimg.org/8wdwalrwxr/cover11.jpg\"}}",
"posting_json_metadata": "{\"profile\":{\"location\":\"Planet Earth\",\"about\":\"alien, crypto enthusiast, vipassana meditator\",\"profile_image\":\"https://s1.postimg.org/4u0w6z63db/profile6.jpg\",\"cover_image\":\"https://s1.postimg.org/8wdwalrwxr/cover11.jpg\"}}",
"proxy": "",
"last_owner_update": "1970-01-01T00:00:00",
"last_account_update": "2017-10-13T13:18:51",
"created": "2017-10-08T16:37:21",
"mined": false,
"recovery_account": "steem",
"last_account_recovery": "1970-01-01T00:00:00",
"reset_account": "null",
"comment_count": 0,
"lifetime_vote_count": 0,
"post_count": 9,
"can_vote": true,
"voting_manabar": {
"current_mana": "13198167288",
"last_update_time": 1588954767
},
"downvote_manabar": {
"current_mana": 3299541822,
"last_update_time": 1588954767
},
"voting_power": 0,
"balance": "0.005 STEEM",
"savings_balance": "0.000 STEEM",
"sbd_balance": "0.034 SBD",
"sbd_seconds": "0",
"sbd_seconds_last_update": "2018-06-30T19:28:24",
"sbd_last_interest_payment": "2018-06-30T19:28:24",
"savings_sbd_balance": "0.000 SBD",
"savings_sbd_seconds": "0",
"savings_sbd_seconds_last_update": "1970-01-01T00:00:00",
"savings_sbd_last_interest_payment": "1970-01-01T00:00:00",
"savings_withdraw_requests": 0,
"reward_sbd_balance": "0.000 SBD",
"reward_steem_balance": "0.000 STEEM",
"reward_vesting_balance": "0.000000 VESTS",
"reward_vesting_steem": "0.000 STEEM",
"vesting_shares": "13198.167288 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "0.000000 VESTS",
"vesting_withdraw_rate": "0.000000 VESTS",
"next_vesting_withdrawal": "1969-12-31T23:59:59",
"withdrawn": 0,
"to_withdraw": 0,
"withdraw_routes": 0,
"curation_rewards": 1,
"posting_rewards": 11831,
"proxied_vsf_votes": [
0,
0,
0,
0
],
"witnesses_voted_for": 0,
"last_post": "2018-05-09T19:01:57",
"last_root_post": "2018-05-09T19:01:57",
"last_vote_time": "2018-05-10T15:33:09",
"post_bandwidth": 0,
"pending_claimed_accounts": 0,
"vesting_balance": "0.000 STEEM",
"reputation": "106234033682",
"transfer_history": [],
"market_history": [],
"post_history": [],
"vote_history": [],
"other_history": [],
"witness_votes": [],
"tags_usage": [],
"guest_bloggers": [],
"rank": 145745
}Withdraw Routes
| Incoming | Outgoing |
|---|---|
Empty | Empty |
{
"incoming": [],
"outgoing": []
}From Date
To Date
steemdelegated 0.000 SP to @sweetwilliam2020/05/08 16:19:27
steemdelegated 0.000 SP to @sweetwilliam
2020/05/08 16:19:27
| delegator | steem |
| delegatee | sweetwilliam |
| vesting shares | 0.000000 VESTS |
| Transaction Info | Block #43201318/Trx e5ca005bbb167924e263c937403504628f5f4490 |
View Raw JSON Data
{
"trx_id": "e5ca005bbb167924e263c937403504628f5f4490",
"block": 43201318,
"trx_in_block": 10,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-05-08T16:19:27",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sweetwilliam",
"vesting_shares": "0.000000 VESTS"
}
]
}2019/10/08 17:44:24
2019/10/08 17:44:24
| parent author | sweetwilliam |
| parent permlink | the-bitcoin-paper-a-reader-s-companion |
| author | steemitboard |
| permlink | steemitboard-notify-sweetwilliam-20191008t174424000z |
| title | |
| body | Congratulations @sweetwilliam! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@sweetwilliam/birthday2.png</td><td>Happy Birthday! - You are on the Steem blockchain for 2 years!</td></tr></table> <sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@sweetwilliam) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=sweetwilliam)_</sub> **Do not miss the last post from @steemitboard:** <table><tr><td><a href="https://steemit.com/steemfest/@steemitboard/the-new-steemfest-badge-is-ready"><img src="https://steemitimages.com/64x128/https://cdn.steemitimages.com/DQmRUkELn2Fd13pWFkmWU2wBMMx39EBX5V3cHBEZ2d7f3Ve/image.png"></a></td><td><a href="https://steemit.com/steemfest/@steemitboard/the-new-steemfest-badge-is-ready">The new SteemFest⁴ badge is ready</a></td></tr></table> ###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| Transaction Info | Block #37110239/Trx efa93a549cf52f14c39422f5a1ca16a8f902385e |
View Raw JSON Data
{
"trx_id": "efa93a549cf52f14c39422f5a1ca16a8f902385e",
"block": 37110239,
"trx_in_block": 18,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-10-08T17:44:24",
"op": [
"comment",
{
"parent_author": "sweetwilliam",
"parent_permlink": "the-bitcoin-paper-a-reader-s-companion",
"author": "steemitboard",
"permlink": "steemitboard-notify-sweetwilliam-20191008t174424000z",
"title": "",
"body": "Congratulations @sweetwilliam! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@sweetwilliam/birthday2.png</td><td>Happy Birthday! - You are on the Steem blockchain for 2 years!</td></tr></table>\n\n<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@sweetwilliam) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=sweetwilliam)_</sub>\n\n\n**Do not miss the last post from @steemitboard:**\n<table><tr><td><a href=\"https://steemit.com/steemfest/@steemitboard/the-new-steemfest-badge-is-ready\"><img src=\"https://steemitimages.com/64x128/https://cdn.steemitimages.com/DQmRUkELn2Fd13pWFkmWU2wBMMx39EBX5V3cHBEZ2d7f3Ve/image.png\"></a></td><td><a href=\"https://steemit.com/steemfest/@steemitboard/the-new-steemfest-badge-is-ready\">The new SteemFest⁴ badge is ready</a></td></tr></table>\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}"
}
]
}steemdetectivesent 0.001 STEEM to @sweetwilliam- "Hy @sweetwilliam check out https://steemdetective.com"2019/04/09 12:12:30
steemdetectivesent 0.001 STEEM to @sweetwilliam- "Hy @sweetwilliam check out https://steemdetective.com"
2019/04/09 12:12:30
| from | steemdetective |
| to | sweetwilliam |
| amount | 0.001 STEEM |
| memo | Hy @sweetwilliam check out https://steemdetective.com |
| Transaction Info | Block #31893603/Trx 1c35a831c909bcf7c73c950c0faf414157a8fe27 |
View Raw JSON Data
{
"trx_id": "1c35a831c909bcf7c73c950c0faf414157a8fe27",
"block": 31893603,
"trx_in_block": 27,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-04-09T12:12:30",
"op": [
"transfer",
{
"from": "steemdetective",
"to": "sweetwilliam",
"amount": "0.001 STEEM",
"memo": "Hy @sweetwilliam check out https://steemdetective.com"
}
]
}steemdelegated 1.240 SP to @sweetwilliam2018/10/08 19:15:33
steemdelegated 1.240 SP to @sweetwilliam
2018/10/08 19:15:33
| delegator | steem |
| delegatee | sweetwilliam |
| vesting shares | 2019.336318 VESTS |
| Transaction Info | Block #26635834/Trx 000471a04098a14a84cc1353bf608699a3e0b255 |
View Raw JSON Data
{
"trx_id": "000471a04098a14a84cc1353bf608699a3e0b255",
"block": 26635834,
"trx_in_block": 11,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-10-08T19:15:33",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sweetwilliam",
"vesting_shares": "2019.336318 VESTS"
}
]
}sweetwilliamclaimed reward balance: 0.027 SBD, 0.011 SP2018/06/30 19:28:24
sweetwilliamclaimed reward balance: 0.027 SBD, 0.011 SP
2018/06/30 19:28:24
| account | sweetwilliam |
| reward steem | 0.000 STEEM |
| reward sbd | 0.027 SBD |
| reward vests | 18.313737 VESTS |
| Transaction Info | Block #23783586/Trx 92b010ace7b847214511f606b71fca65ab9b6077 |
View Raw JSON Data
{
"trx_id": "92b010ace7b847214511f606b71fca65ab9b6077",
"block": 23783586,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-30T19:28:24",
"op": [
"claim_reward_balance",
{
"account": "sweetwilliam",
"reward_steem": "0.000 STEEM",
"reward_sbd": "0.027 SBD",
"reward_vests": "18.313737 VESTS"
}
]
}steemdelegated 10.618 SP to @sweetwilliam2018/06/18 12:44:21
steemdelegated 10.618 SP to @sweetwilliam
2018/06/18 12:44:21
| delegator | steem |
| delegatee | sweetwilliam |
| vesting shares | 17290.683079 VESTS |
| Transaction Info | Block #23430034/Trx 79bee00289f749850f814b36b40c86a63f01ade5 |
View Raw JSON Data
{
"trx_id": "79bee00289f749850f814b36b40c86a63f01ade5",
"block": 23430034,
"trx_in_block": 24,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-06-18T12:44:21",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sweetwilliam",
"vesting_shares": "17290.683079 VESTS"
}
]
}sweetwilliamreceived 0.027 SBD, 0.011 SP author reward for @sweetwilliam / the-bitcoin-paper-a-reader-s-companion2018/05/16 19:01:57
sweetwilliamreceived 0.027 SBD, 0.011 SP author reward for @sweetwilliam / the-bitcoin-paper-a-reader-s-companion
2018/05/16 19:01:57
| author | sweetwilliam |
| permlink | the-bitcoin-paper-a-reader-s-companion |
| sbd payout | 0.027 SBD |
| steem payout | 0.000 STEEM |
| vesting payout | 18.313737 VESTS |
| Transaction Info | Block #22488341/Virtual Operation #4 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 22488341,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 4,
"timestamp": "2018-05-16T19:01:57",
"op": [
"author_reward",
{
"author": "sweetwilliam",
"permlink": "the-bitcoin-paper-a-reader-s-companion",
"sbd_payout": "0.027 SBD",
"steem_payout": "0.000 STEEM",
"vesting_payout": "18.313737 VESTS"
}
]
}sweetwilliamsent 0.340 SBD to @null- "@sweetwilliam/the-bitcoin-paper-a-reader-s-companion"2018/05/12 11:36:18
sweetwilliamsent 0.340 SBD to @null- "@sweetwilliam/the-bitcoin-paper-a-reader-s-companion"
2018/05/12 11:36:18
| from | sweetwilliam |
| to | null |
| amount | 0.340 SBD |
| memo | @sweetwilliam/the-bitcoin-paper-a-reader-s-companion |
| Transaction Info | Block #22364240/Trx 9c7179ff2c3d428ee4836e92bd702955af101c5e |
View Raw JSON Data
{
"trx_id": "9c7179ff2c3d428ee4836e92bd702955af101c5e",
"block": 22364240,
"trx_in_block": 16,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-12T11:36:18",
"op": [
"transfer",
{
"from": "sweetwilliam",
"to": "null",
"amount": "0.340 SBD",
"memo": "@sweetwilliam/the-bitcoin-paper-a-reader-s-companion"
}
]
}sweetwilliamsent 0.100 SBD to @null- "@sweetwilliam/the-bitcoin-paper-a-reader-s-companion"2018/05/11 17:49:39
sweetwilliamsent 0.100 SBD to @null- "@sweetwilliam/the-bitcoin-paper-a-reader-s-companion"
2018/05/11 17:49:39
| from | sweetwilliam |
| to | null |
| amount | 0.100 SBD |
| memo | @sweetwilliam/the-bitcoin-paper-a-reader-s-companion |
| Transaction Info | Block #22342908/Trx 8c4951331b4e5d59b327d82730f47415284ddbb9 |
View Raw JSON Data
{
"trx_id": "8c4951331b4e5d59b327d82730f47415284ddbb9",
"block": 22342908,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-11T17:49:39",
"op": [
"transfer",
{
"from": "sweetwilliam",
"to": "null",
"amount": "0.100 SBD",
"memo": "@sweetwilliam/the-bitcoin-paper-a-reader-s-companion"
}
]
}sweetwilliampublished a new post: the-bitcoin-paper-a-reader-s-companion2018/05/10 17:38:42
sweetwilliampublished a new post: the-bitcoin-paper-a-reader-s-companion
2018/05/10 17:38:42
| parent author | |
| parent permlink | bitcoin |
| author | sweetwilliam |
| permlink | the-bitcoin-paper-a-reader-s-companion |
| title | The Bitcoin Paper - A Reader's Companion |
| body | @@ -409,16 +409,23 @@ tity of +author Satoshi @@ -1312,225 +1312,8 @@ oxes -, and highlight to define or further explain. On first reading the paper can seem sparse and obtuse, but with sufficient context and understanding I hope to demonstrate to you it's elegance, and momentous implications . Th @@ -1684,16 +1684,189 @@ entives. + On first reading the paper can seem sparse and obtuse, but with sufficient context and understanding I hope to demonstrate to you it's elegance, and momentous implications. %0A%0A#### L @@ -2017,16 +2017,32 @@ to.html%22 + target=%22_blank%22 %3ECypherp @@ -4784,21 +4784,32 @@ be -provided by a +represented by a bank or fin @@ -4981,245 +4981,8 @@ t.%0A%0A -%3Cdiv style=%22margin-left: auto;margin-right: auto;text-align: justify;-ms-text-justify: distribute-all-lines;text-justify: distribute-all-lines;%22%3E%0A %3Ca style=%22vertical-align:top; display:inline-block; *display:inline; zoom:1;%22%3E%0A %3Cimg @@ -5105,32 +5105,24 @@ n:0 auto;%22%3E%0A - %3Cp style=%22di @@ -5203,108 +5203,8 @@ /p%3E%0A - %3C/a%3E%0A %3Ca style=%22vertical-align:top; display:inline-block; *display:inline; zoom:1;%22%3E%0A %3Cimg @@ -5331,24 +5331,16 @@ auto;%22%3E%0A - %3Cp style @@ -5421,23 +5421,8 @@ /p%3E%0A - %3C/a%3E%0A%3C/div%3E %0A%3C/p @@ -6913,21 +6913,23 @@ by hand - that +, which binds t @@ -10466,24 +10466,153 @@ utorial%3C/a%3E%0A +* %3Ca href=%22https://www.youtube.com/watch?v=RIckQ6RBt5E%22 target=%22_blank%22%3EDigital Signatures explained by Andreas Antonopoulos%3C/a%3E%0A * %3Ca href=%22h @@ -17376,17 +17376,16 @@ wnership -, + there i @@ -18980,16 +18980,538 @@ ledger. - +%0A%0AThe gruesome analogy that comes to mind here is how a kidnapper might use a photo of their victim with that day's newspaper in order to authenticate that as of a certain date given by the publication of a newspaper the victim is still alive. Similarly by using a timestampped server we can authenticate that a transaction has been included in a block at a certain time and cannot be made again later. These blocks are the heartbeat of the network where information is assimilated on the ledger and a state agreed upon.%0A%0A When you @@ -23931,15 +23931,11 @@ und -is also +has inc @@ -23940,16 +23940,57 @@ ncreased + from 10 at block 0 to 11 at block 100000 . Adjust @@ -24485,17 +24485,16 @@ eb2919%0A%0A -%0A When a m @@ -24673,12 +24673,135 @@ Bit -ocin +coin, if other miners agree that the block is valid they will start working to compile the next block... so the cycle continues .%0A%0AT @@ -31274,22 +31274,43 @@ ver time -, in a +. This reduction happens in halving @@ -31315,16 +31315,24 @@ ng event +s, where approxi @@ -31351,17 +31351,67 @@ 4 years -, + the number of Bitcoins mined in each block reduces from 50 @@ -31412,18 +31412,22 @@ rom 50 B -TC +itcoin per blo @@ -31437,18 +31437,22 @@ to 25 B -TC +itcoin , to 12. @@ -31458,10 +31458,15 @@ .5 B -TC +itcoin etc @@ -31656,17 +31656,17 @@ nger min -t +e new Bit @@ -39070,16 +39070,68 @@ are -recorded +visible, but the identity of the address owners is not known . By @@ -39367,16 +39367,26 @@ ense of +increased computat @@ -39500,24 +39500,187 @@ privacy%3C/a%3E +%0A* %3Ca href=%22https://cseweb.ucsd.edu/~smeiklejohn/files/imc13.pdf%22 target=%22_blank%22%3EPaper: A Fistful of Bitcoins: Characterizing Payments Among Men with No Names%3C/a%3E %0A%0A## 11. Cal @@ -46549,136 +46549,1738 @@ net. - That is not to say that it has not had its fair sh +%0A%0ASince the release of this paper the network has evolved and adapted, in ways that would have been difficult to predict in 2008. Due to the incentives in mining and how potentially lucrative it is mining has gone from being done on CPUs, to more parallelisable GPUs. Then companies started designing custom Application-specific integrated circuit (ASIC) chips. That is to say chips especially designed to perform the proof-of-work required by Bitcoin. Developments in ASIC technology are highly secretive and very competitive. Meaning that for a single user to start mining on their PC it is no longer profitable. Large companies have gained significant mining power in the network, mainly operating in countries or places like China with subsidised electricity and cheap hardware. Another change has been the development of mining pools where users can group together and donate their computational resources in return for some fraction of mining reward. Both of these developments in l ar +g e -of challenges and drama, but this remarkable peer-to-peer electronic cash +mining companies and mining pools have lead to increasing centralisation of the netwok. %0A%0ABitcoin has also deviated from the original vision of the paper in the fact that its use as a means of payment for low value goods is becoming rarer. That is to say it is increasingly being thought of as a kind of digital gold asset rather than an electronic cash, this is due to the high transaction fees and price volatility. However, as mentioned before additional protocol layers are being built on top of the Bitcoin network in the hope that it can again be used as a kind of electronic cash. %0A%0ADespite these challenges, and plenty of drama along the way, this remarkable peer-to-peer electronic money continues to evolve and ten years later is @@ -48300,16 +48300,17 @@ trong!%0A%0A +%0A #### Fur @@ -50642,8 +50642,223 @@ here ;-) - +%0A%0A%3Cbr%3EFinally, if you are looking for a more indepth explanation of Bitcoin I highly recommend %3Ca href=%22https://github.com/bitcoinbook/bitcoinbook%22 target=%22_blank%22%3EAndreas Antonopoulos' book %22Mastering Bitcoin%22%3C/a%3E. |
| json metadata | {"tags":["bitcoin","cryptocurrency","blog","writing","technology"],"image":["https://steemitimages.com/DQmetns4LHAMmPDnCtXSzT7Ff9v3fFuYaucbai9TPPXCeJx/c2s.png","https://steemitimages.com/DQmeEnnfQqyyP4iot7YuKvioqQjSTmS8dDCgV1x9ceAKmHd/p2p.png","https://steemitimages.com/DQmXe235tK6mruNcqWBJ3JsPTUFxERwqi5ZYqkjePTnwurR/digital_signatures.png","https://steemitimages.com/DQmV1fvCbeAuXPc7N5HM2BAyzfvhDDVEEvA4GauA6qrJHFk/transactions.png","https://steemitimages.com/DQmTza1XMZNVLyTxCk366sD1xqQZos4n2bQsmsTtzKBi31t/timestamp_server.png","https://steemitimages.com/DQmVsXjFwceGQ3qKpjNWbUgvRimgMuVPgQ4nyAWr1KVUor9/proof_of_work.png","https://steemitimages.com/DQmP3871pXHsUe5sR1WLeYmNN96CShLLMGt4qnyn2QsfFax/merkle.png","https://steemitimages.com/DQmWLopYBYqrYxGRJoby6Sib29RW2WbW6G14CUMjRDQgXV8/spv.png","https://steemitimages.com/DQmbgDQ82GCAo5gPFvmZFBXv7rgqo2YiJLX59yqrJjzZQqi/utxo.png","https://steemitimages.com/DQmTmxcTK1zUHvRLJGJaTfSM37HAHykhGYUHU7jLnGrYxCD/privacy.png","https://steemitimages.com/DQmcwZwezcs4nK5rLcimQX3fLR3z3AeWXrDDoBVospw3q7T/equation1.png","https://steemitimages.com/DQmdsRSkrU8Hs7ZXW3CWDwUT3pPRENXzRjy1SCVrCQ414S2/equation2.png","https://steemitimages.com/DQmXaTaRpNvEvyvV8aUPhvv4hncP1sfwuXBehdbZscjpb8Y/equation3.png","https://steemitimages.com/DQmWdLjgjP14o55xKJ7SjY2GhLiJoUUXtVLmoPDeSoX8Ubj/equation4.png"],"links":["https://bitcoin.org/en/","https://bitcoin.org/bitcoin.pdf","https://www.activism.net/cypherpunk/manifesto.html","#fn1","#fn2","#fn3","#fn4","#fn5","https://www.plagiarismtoday.com/2017/06/01/the-long-slow-decline-of-bittorrent/","https://en.wikipedia.org/wiki/Cryptographic_hash_function","https://www.tutorialspoint.com/cryptography/cryptography_digital_signatures.htm","https://www.youtube.com/watch?v=RIckQ6RBt5E","http://groups.csail.mit.edu/mac/classes/6.805/student-papers/fall97-papers/fillingham-sig.html","https://www.youtube.com/watch?v=NF1pwjL9-DE","#fn6","https://lightning.network/","https://en.wikipedia.org/wiki/Lightning_Network","#ref1","#fn7","#ref2","#ref3","#ref4","#ref5","https://en.wikipedia.org/wiki/Blockchain","https://link.springer.com/article/10.1007%2FBF00196791","#ref6","https://www.youtube.com/watch?v=r0pcpGduaJw","https://en.wikipedia.org/wiki/Proof-of-work_system","https://en.bitcoin.it/wiki/Full_node","https://en.bitcoin.it/wiki/Controlled_supply","https://blockchain.info/charts/total-bitcoins?timespan=all","#fn9","#ref7","https://en.wikipedia.org/wiki/Merkle_tree","https://en.bitcoin.it/wiki/Thin_Client_Security","https://pascalpares.gitbooks.io/implementation-of-the-bitcoin-system/content/1-transaction-4-structure.html","https://medium.com/@aalim.khan/bitcoin-transactions-scripts-and-digital-signatures-506688e1630a","https://bitcoin.org/en/protect-your-privacy","https://cseweb.ucsd.edu/~smeiklejohn/files/imc13.pdf","#ref8","https://en.bitcoin.it/wiki/Weaknesses","https://www.youtube.com/watch?v=DjYbsq3FXfM","http://www.weidai.com/bmoney.txt","http://nakamotoinstitute.org/literature/secure-timestamping-service/","https://link.springer.com/article/10.1007/BF00196791","https://link.springer.com/chapter/10.1007/978-1-4613-9323-8_24","http://nakamotoinstitute.org/static/docs/secure-names-bit-strings.pdf","http://www.hashcash.org/papers/hashcash.pdf","http://ieeexplore.ieee.org/document/6233691","https://www.wiley.com/en-us/An+Introduction+to+Probability+Theory+and+Its+Applications%2C+Volume+2%2C+2nd+Edition-p-9780471257097","https://github.com/bitcoinbook/bitcoinbook"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #22313889/Trx 9ddd7cf2afd6ea50293aefa8c6dac62f181ef881 |
View Raw JSON Data
{
"trx_id": "9ddd7cf2afd6ea50293aefa8c6dac62f181ef881",
"block": 22313889,
"trx_in_block": 40,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-10T17:38:42",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "bitcoin",
"author": "sweetwilliam",
"permlink": "the-bitcoin-paper-a-reader-s-companion",
"title": "The Bitcoin Paper - A Reader's Companion",
"body": "@@ -409,16 +409,23 @@\n tity of \n+author \n Satoshi \n@@ -1312,225 +1312,8 @@\n oxes\n-, and highlight to define or further explain. On first reading the paper can seem sparse and obtuse, but with sufficient context and understanding I hope to demonstrate to you it's elegance, and momentous implications\n . Th\n@@ -1684,16 +1684,189 @@\n entives.\n+ On first reading the paper can seem sparse and obtuse, but with sufficient context and understanding I hope to demonstrate to you it's elegance, and momentous implications.\n %0A%0A#### L\n@@ -2017,16 +2017,32 @@\n to.html%22\n+ target=%22_blank%22\n %3ECypherp\n@@ -4784,21 +4784,32 @@\n be \n-provided by a\n+represented by a bank or\n fin\n@@ -4981,245 +4981,8 @@\n t.%0A%0A\n-%3Cdiv style=%22margin-left: auto;margin-right: auto;text-align: justify;-ms-text-justify: distribute-all-lines;text-justify: distribute-all-lines;%22%3E%0A %3Ca style=%22vertical-align:top; display:inline-block; *display:inline; zoom:1;%22%3E%0A \n %3Cimg\n@@ -5105,32 +5105,24 @@\n n:0 auto;%22%3E%0A\n- \n %3Cp style=%22di\n@@ -5203,108 +5203,8 @@\n /p%3E%0A\n- %3C/a%3E%0A %3Ca style=%22vertical-align:top; display:inline-block; *display:inline; zoom:1;%22%3E%0A \n %3Cimg\n@@ -5331,24 +5331,16 @@\n auto;%22%3E%0A\n- \n %3Cp style\n@@ -5421,23 +5421,8 @@\n /p%3E%0A\n- %3C/a%3E%0A%3C/div%3E\n %0A%3C/p\n@@ -6913,21 +6913,23 @@\n by hand\n- that\n+, which\n binds t\n@@ -10466,24 +10466,153 @@\n utorial%3C/a%3E%0A\n+* %3Ca href=%22https://www.youtube.com/watch?v=RIckQ6RBt5E%22 target=%22_blank%22%3EDigital Signatures explained by Andreas Antonopoulos%3C/a%3E%0A\n * %3Ca href=%22h\n@@ -17376,17 +17376,16 @@\n wnership\n-,\n \n+\n there i\n@@ -18980,16 +18980,538 @@\n ledger. \n-\n \n+%0A%0AThe gruesome analogy that comes to mind here is how a kidnapper might use a photo of their victim with that day's newspaper in order to authenticate that as of a certain date given by the publication of a newspaper the victim is still alive. Similarly by using a timestampped server we can authenticate that a transaction has been included in a block at a certain time and cannot be made again later. These blocks are the heartbeat of the network where information is assimilated on the ledger and a state agreed upon.%0A%0A\n When you\n@@ -23931,15 +23931,11 @@\n und \n-is also\n+has\n inc\n@@ -23940,16 +23940,57 @@\n ncreased\n+ from 10 at block 0 to 11 at block 100000\n . Adjust\n@@ -24485,17 +24485,16 @@\n eb2919%0A%0A\n-%0A\n When a m\n@@ -24673,12 +24673,135 @@\n Bit\n-ocin\n+coin, if other miners agree that the block is valid they will start working to compile the next block... so the cycle continues\n .%0A%0AT\n@@ -31274,22 +31274,43 @@\n ver time\n-, in a\n+. This reduction happens in\n halving\n@@ -31315,16 +31315,24 @@\n ng event\n+s, where\n approxi\n@@ -31351,17 +31351,67 @@\n 4 years\n-,\n+ the number of Bitcoins mined in each block reduces\n from 50\n@@ -31412,18 +31412,22 @@\n rom 50 B\n-TC\n+itcoin\n per blo\n@@ -31437,18 +31437,22 @@\n to 25 B\n-TC\n+itcoin\n , to 12.\n@@ -31458,10 +31458,15 @@\n .5 B\n-TC\n+itcoin \n etc\n@@ -31656,17 +31656,17 @@\n nger min\n-t\n+e\n new Bit\n@@ -39070,16 +39070,68 @@\n are \n-recorded\n+visible, but the identity of the address owners is not known\n . By\n@@ -39367,16 +39367,26 @@\n ense of \n+increased \n computat\n@@ -39500,24 +39500,187 @@\n privacy%3C/a%3E\n+%0A* %3Ca href=%22https://cseweb.ucsd.edu/~smeiklejohn/files/imc13.pdf%22 target=%22_blank%22%3EPaper: A Fistful of Bitcoins: Characterizing Payments Among Men with No Names%3C/a%3E\n %0A%0A## 11. Cal\n@@ -46549,136 +46549,1738 @@\n net.\n- That is not to say that it has not had its fair sh\n+%0A%0ASince the release of this paper the network has evolved and adapted, in ways that would have been difficult to predict in 2008. Due to the incentives in mining and how potentially lucrative it is mining has gone from being done on CPUs, to more parallelisable GPUs. Then companies started designing custom Application-specific integrated circuit (ASIC) chips. That is to say chips especially designed to perform the proof-of-work required by Bitcoin. Developments in ASIC technology are highly secretive and very competitive. Meaning that for a single user to start mining on their PC it is no longer profitable. Large companies have gained significant mining power in the network, mainly operating in countries or places like China with subsidised electricity and cheap hardware. Another change has been the development of mining pools where users can group together and donate their computational resources in return for some fraction of mining reward. Both of these developments in l\n ar\n+g\n e \n-of challenges and drama, but this remarkable peer-to-peer electronic cash\n+mining companies and mining pools have lead to increasing centralisation of the netwok. %0A%0ABitcoin has also deviated from the original vision of the paper in the fact that its use as a means of payment for low value goods is becoming rarer. That is to say it is increasingly being thought of as a kind of digital gold asset rather than an electronic cash, this is due to the high transaction fees and price volatility. However, as mentioned before additional protocol layers are being built on top of the Bitcoin network in the hope that it can again be used as a kind of electronic cash. %0A%0ADespite these challenges, and plenty of drama along the way, this remarkable peer-to-peer electronic money continues to evolve and ten years later\n is \n@@ -48300,16 +48300,17 @@\n trong!%0A%0A\n+%0A\n #### Fur\n@@ -50642,8 +50642,223 @@\n here ;-)\n-\n \n+%0A%0A%3Cbr%3EFinally, if you are looking for a more indepth explanation of Bitcoin I highly recommend %3Ca href=%22https://github.com/bitcoinbook/bitcoinbook%22 target=%22_blank%22%3EAndreas Antonopoulos' book %22Mastering Bitcoin%22%3C/a%3E.\n",
"json_metadata": "{\"tags\":[\"bitcoin\",\"cryptocurrency\",\"blog\",\"writing\",\"technology\"],\"image\":[\"https://steemitimages.com/DQmetns4LHAMmPDnCtXSzT7Ff9v3fFuYaucbai9TPPXCeJx/c2s.png\",\"https://steemitimages.com/DQmeEnnfQqyyP4iot7YuKvioqQjSTmS8dDCgV1x9ceAKmHd/p2p.png\",\"https://steemitimages.com/DQmXe235tK6mruNcqWBJ3JsPTUFxERwqi5ZYqkjePTnwurR/digital_signatures.png\",\"https://steemitimages.com/DQmV1fvCbeAuXPc7N5HM2BAyzfvhDDVEEvA4GauA6qrJHFk/transactions.png\",\"https://steemitimages.com/DQmTza1XMZNVLyTxCk366sD1xqQZos4n2bQsmsTtzKBi31t/timestamp_server.png\",\"https://steemitimages.com/DQmVsXjFwceGQ3qKpjNWbUgvRimgMuVPgQ4nyAWr1KVUor9/proof_of_work.png\",\"https://steemitimages.com/DQmP3871pXHsUe5sR1WLeYmNN96CShLLMGt4qnyn2QsfFax/merkle.png\",\"https://steemitimages.com/DQmWLopYBYqrYxGRJoby6Sib29RW2WbW6G14CUMjRDQgXV8/spv.png\",\"https://steemitimages.com/DQmbgDQ82GCAo5gPFvmZFBXv7rgqo2YiJLX59yqrJjzZQqi/utxo.png\",\"https://steemitimages.com/DQmTmxcTK1zUHvRLJGJaTfSM37HAHykhGYUHU7jLnGrYxCD/privacy.png\",\"https://steemitimages.com/DQmcwZwezcs4nK5rLcimQX3fLR3z3AeWXrDDoBVospw3q7T/equation1.png\",\"https://steemitimages.com/DQmdsRSkrU8Hs7ZXW3CWDwUT3pPRENXzRjy1SCVrCQ414S2/equation2.png\",\"https://steemitimages.com/DQmXaTaRpNvEvyvV8aUPhvv4hncP1sfwuXBehdbZscjpb8Y/equation3.png\",\"https://steemitimages.com/DQmWdLjgjP14o55xKJ7SjY2GhLiJoUUXtVLmoPDeSoX8Ubj/equation4.png\"],\"links\":[\"https://bitcoin.org/en/\",\"https://bitcoin.org/bitcoin.pdf\",\"https://www.activism.net/cypherpunk/manifesto.html\",\"#fn1\",\"#fn2\",\"#fn3\",\"#fn4\",\"#fn5\",\"https://www.plagiarismtoday.com/2017/06/01/the-long-slow-decline-of-bittorrent/\",\"https://en.wikipedia.org/wiki/Cryptographic_hash_function\",\"https://www.tutorialspoint.com/cryptography/cryptography_digital_signatures.htm\",\"https://www.youtube.com/watch?v=RIckQ6RBt5E\",\"http://groups.csail.mit.edu/mac/classes/6.805/student-papers/fall97-papers/fillingham-sig.html\",\"https://www.youtube.com/watch?v=NF1pwjL9-DE\",\"#fn6\",\"https://lightning.network/\",\"https://en.wikipedia.org/wiki/Lightning_Network\",\"#ref1\",\"#fn7\",\"#ref2\",\"#ref3\",\"#ref4\",\"#ref5\",\"https://en.wikipedia.org/wiki/Blockchain\",\"https://link.springer.com/article/10.1007%2FBF00196791\",\"#ref6\",\"https://www.youtube.com/watch?v=r0pcpGduaJw\",\"https://en.wikipedia.org/wiki/Proof-of-work_system\",\"https://en.bitcoin.it/wiki/Full_node\",\"https://en.bitcoin.it/wiki/Controlled_supply\",\"https://blockchain.info/charts/total-bitcoins?timespan=all\",\"#fn9\",\"#ref7\",\"https://en.wikipedia.org/wiki/Merkle_tree\",\"https://en.bitcoin.it/wiki/Thin_Client_Security\",\"https://pascalpares.gitbooks.io/implementation-of-the-bitcoin-system/content/1-transaction-4-structure.html\",\"https://medium.com/@aalim.khan/bitcoin-transactions-scripts-and-digital-signatures-506688e1630a\",\"https://bitcoin.org/en/protect-your-privacy\",\"https://cseweb.ucsd.edu/~smeiklejohn/files/imc13.pdf\",\"#ref8\",\"https://en.bitcoin.it/wiki/Weaknesses\",\"https://www.youtube.com/watch?v=DjYbsq3FXfM\",\"http://www.weidai.com/bmoney.txt\",\"http://nakamotoinstitute.org/literature/secure-timestamping-service/\",\"https://link.springer.com/article/10.1007/BF00196791\",\"https://link.springer.com/chapter/10.1007/978-1-4613-9323-8_24\",\"http://nakamotoinstitute.org/static/docs/secure-names-bit-strings.pdf\",\"http://www.hashcash.org/papers/hashcash.pdf\",\"http://ieeexplore.ieee.org/document/6233691\",\"https://www.wiley.com/en-us/An+Introduction+to+Probability+Theory+and+Its+Applications%2C+Volume+2%2C+2nd+Edition-p-9780471257097\",\"https://github.com/bitcoinbook/bitcoinbook\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}2018/05/10 15:33:09
2018/05/10 15:33:09
| voter | sweetwilliam |
| author | toni.crypto |
| permlink | re-sweetwilliam-the-bitcoin-paper-a-reader-s-companion-20180510t064100303z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #22311379/Trx 052a6b18db199da1f04407a3c055550a1164bc57 |
View Raw JSON Data
{
"trx_id": "052a6b18db199da1f04407a3c055550a1164bc57",
"block": 22311379,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-10T15:33:09",
"op": [
"vote",
{
"voter": "sweetwilliam",
"author": "toni.crypto",
"permlink": "re-sweetwilliam-the-bitcoin-paper-a-reader-s-companion-20180510t064100303z",
"weight": 10000
}
]
}sweetwilliamupvoted (100.00%) @steemitboard / steemitboard-notify-sweetwilliam-20180510t052717000z2018/05/10 15:32:57
sweetwilliamupvoted (100.00%) @steemitboard / steemitboard-notify-sweetwilliam-20180510t052717000z
2018/05/10 15:32:57
| voter | sweetwilliam |
| author | steemitboard |
| permlink | steemitboard-notify-sweetwilliam-20180510t052717000z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #22311375/Trx 666297e44f04db9b3d729b562e4fddabae11e490 |
View Raw JSON Data
{
"trx_id": "666297e44f04db9b3d729b562e4fddabae11e490",
"block": 22311375,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-10T15:32:57",
"op": [
"vote",
{
"voter": "sweetwilliam",
"author": "steemitboard",
"permlink": "steemitboard-notify-sweetwilliam-20180510t052717000z",
"weight": 10000
}
]
}2018/05/10 06:41:00
2018/05/10 06:41:00
| parent author | sweetwilliam |
| parent permlink | the-bitcoin-paper-a-reader-s-companion |
| author | toni.crypto |
| permlink | re-sweetwilliam-the-bitcoin-paper-a-reader-s-companion-20180510t064100303z |
| title | |
| body | Hello! Good article! I'm interested in the them of ICO and crypto-currency, I'll subscribe to your channel. I hope you will also like my content and reviews of the most profitable bounties and ICO, subscribe to me @toni.crypto There will be a lot of interesting! |
| json metadata | {"tags":["bitcoin"],"users":["toni.crypto"],"app":"steemit/0.1"} |
| Transaction Info | Block #22300745/Trx 846d34dcdc80b9b3be1adfb4bd12091526484d7a |
View Raw JSON Data
{
"trx_id": "846d34dcdc80b9b3be1adfb4bd12091526484d7a",
"block": 22300745,
"trx_in_block": 12,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-10T06:41:00",
"op": [
"comment",
{
"parent_author": "sweetwilliam",
"parent_permlink": "the-bitcoin-paper-a-reader-s-companion",
"author": "toni.crypto",
"permlink": "re-sweetwilliam-the-bitcoin-paper-a-reader-s-companion-20180510t064100303z",
"title": "",
"body": "Hello! Good article! I'm interested in the them of ICO and crypto-currency, I'll subscribe to your channel. I hope you will also like my content and reviews of the most profitable bounties and ICO, subscribe to me @toni.crypto\nThere will be a lot of interesting!",
"json_metadata": "{\"tags\":[\"bitcoin\"],\"users\":[\"toni.crypto\"],\"app\":\"steemit/0.1\"}"
}
]
}steemitboardupvoted (1.00%) @sweetwilliam / the-bitcoin-paper-a-reader-s-companion2018/05/10 05:27:18
steemitboardupvoted (1.00%) @sweetwilliam / the-bitcoin-paper-a-reader-s-companion
2018/05/10 05:27:18
| voter | steemitboard |
| author | sweetwilliam |
| permlink | the-bitcoin-paper-a-reader-s-companion |
| weight | 100 (1.00%) |
| Transaction Info | Block #22299272/Trx 27466f8ef1f885b21888ab870d169b2b4bf78cc4 |
View Raw JSON Data
{
"trx_id": "27466f8ef1f885b21888ab870d169b2b4bf78cc4",
"block": 22299272,
"trx_in_block": 10,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-10T05:27:18",
"op": [
"vote",
{
"voter": "steemitboard",
"author": "sweetwilliam",
"permlink": "the-bitcoin-paper-a-reader-s-companion",
"weight": 100
}
]
}2018/05/10 05:27:15
2018/05/10 05:27:15
| parent author | sweetwilliam |
| parent permlink | the-bitcoin-paper-a-reader-s-companion |
| author | steemitboard |
| permlink | steemitboard-notify-sweetwilliam-20180510t052717000z |
| title | |
| body | Congratulations @sweetwilliam! You have completed some achievement on Steemit and have been rewarded with new badge(s) : [](http://steemitboard.com/@sweetwilliam) Award for the number of upvotes received Click on any badge to view your own Board of Honor on SteemitBoard. To support your work, I also upvoted your post! For more information about SteemitBoard, click [here](https://steemit.com/@steemitboard) If you no longer want to receive notifications, reply to this comment with the word `STOP` > Upvote this notification to help all Steemit users. Learn why [here](https://steemit.com/steemitboard/@steemitboard/http-i-cubeupload-com-7ciqeo-png)! |
| json metadata | {"image":["https://steemitboard.com/img/notifications.png"]} |
| Transaction Info | Block #22299271/Trx 7f3e61e0e746f153c5792a83d60b39b2a82997cc |
View Raw JSON Data
{
"trx_id": "7f3e61e0e746f153c5792a83d60b39b2a82997cc",
"block": 22299271,
"trx_in_block": 49,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-10T05:27:15",
"op": [
"comment",
{
"parent_author": "sweetwilliam",
"parent_permlink": "the-bitcoin-paper-a-reader-s-companion",
"author": "steemitboard",
"permlink": "steemitboard-notify-sweetwilliam-20180510t052717000z",
"title": "",
"body": "Congratulations @sweetwilliam! You have completed some achievement on Steemit and have been rewarded with new badge(s) :\n\n[](http://steemitboard.com/@sweetwilliam) Award for the number of upvotes received\n\nClick on any badge to view your own Board of Honor on SteemitBoard.\n\nTo support your work, I also upvoted your post!\nFor more information about SteemitBoard, click [here](https://steemit.com/@steemitboard)\n\nIf you no longer want to receive notifications, reply to this comment with the word `STOP`\n\n> Upvote this notification to help all Steemit users. Learn why [here](https://steemit.com/steemitboard/@steemitboard/http-i-cubeupload-com-7ciqeo-png)!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notifications.png\"]}"
}
]
}moby-dickupvoted (100.00%) @sweetwilliam / the-bitcoin-paper-a-reader-s-companion2018/05/09 19:45:00
moby-dickupvoted (100.00%) @sweetwilliam / the-bitcoin-paper-a-reader-s-companion
2018/05/09 19:45:00
| voter | moby-dick |
| author | sweetwilliam |
| permlink | the-bitcoin-paper-a-reader-s-companion |
| weight | 10000 (100.00%) |
| Transaction Info | Block #22287627/Trx 9972f44cf8ec39659763025a713e406b570929e3 |
View Raw JSON Data
{
"trx_id": "9972f44cf8ec39659763025a713e406b570929e3",
"block": 22287627,
"trx_in_block": 37,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-09T19:45:00",
"op": [
"vote",
{
"voter": "moby-dick",
"author": "sweetwilliam",
"permlink": "the-bitcoin-paper-a-reader-s-companion",
"weight": 10000
}
]
}lionindayardupvoted (0.85%) @sweetwilliam / the-bitcoin-paper-a-reader-s-companion2018/05/09 19:30:57
lionindayardupvoted (0.85%) @sweetwilliam / the-bitcoin-paper-a-reader-s-companion
2018/05/09 19:30:57
| voter | lionindayard |
| author | sweetwilliam |
| permlink | the-bitcoin-paper-a-reader-s-companion |
| weight | 85 (0.85%) |
| Transaction Info | Block #22287346/Trx 936b7bae72e908ab5542ce8c4bbabcbf93726c44 |
View Raw JSON Data
{
"trx_id": "936b7bae72e908ab5542ce8c4bbabcbf93726c44",
"block": 22287346,
"trx_in_block": 89,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-09T19:30:57",
"op": [
"vote",
{
"voter": "lionindayard",
"author": "sweetwilliam",
"permlink": "the-bitcoin-paper-a-reader-s-companion",
"weight": 85
}
]
}marketstackupvoted (0.85%) @sweetwilliam / the-bitcoin-paper-a-reader-s-companion2018/05/09 19:30:54
marketstackupvoted (0.85%) @sweetwilliam / the-bitcoin-paper-a-reader-s-companion
2018/05/09 19:30:54
| voter | marketstack |
| author | sweetwilliam |
| permlink | the-bitcoin-paper-a-reader-s-companion |
| weight | 85 (0.85%) |
| Transaction Info | Block #22287345/Trx 5738745419fd386a14cee5765719457237e7a1bb |
View Raw JSON Data
{
"trx_id": "5738745419fd386a14cee5765719457237e7a1bb",
"block": 22287345,
"trx_in_block": 10,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-09T19:30:54",
"op": [
"vote",
{
"voter": "marketstack",
"author": "sweetwilliam",
"permlink": "the-bitcoin-paper-a-reader-s-companion",
"weight": 85
}
]
}dick.sledgeupvoted (0.85%) @sweetwilliam / the-bitcoin-paper-a-reader-s-companion2018/05/09 19:30:48
dick.sledgeupvoted (0.85%) @sweetwilliam / the-bitcoin-paper-a-reader-s-companion
2018/05/09 19:30:48
| voter | dick.sledge |
| author | sweetwilliam |
| permlink | the-bitcoin-paper-a-reader-s-companion |
| weight | 85 (0.85%) |
| Transaction Info | Block #22287343/Trx 635a1d99f80249457f647e72fc44d7d83ddd1d63 |
View Raw JSON Data
{
"trx_id": "635a1d99f80249457f647e72fc44d7d83ddd1d63",
"block": 22287343,
"trx_in_block": 52,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-09T19:30:48",
"op": [
"vote",
{
"voter": "dick.sledge",
"author": "sweetwilliam",
"permlink": "the-bitcoin-paper-a-reader-s-companion",
"weight": 85
}
]
}sweetwilliamupvoted (100.00%) @sweetwilliam / the-bitcoin-paper-a-reader-s-companion2018/05/09 19:06:42
sweetwilliamupvoted (100.00%) @sweetwilliam / the-bitcoin-paper-a-reader-s-companion
2018/05/09 19:06:42
| voter | sweetwilliam |
| author | sweetwilliam |
| permlink | the-bitcoin-paper-a-reader-s-companion |
| weight | 10000 (100.00%) |
| Transaction Info | Block #22286861/Trx 919e2dd8475cc781517543f63e0e07a0ad5cf0a0 |
View Raw JSON Data
{
"trx_id": "919e2dd8475cc781517543f63e0e07a0ad5cf0a0",
"block": 22286861,
"trx_in_block": 29,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-09T19:06:42",
"op": [
"vote",
{
"voter": "sweetwilliam",
"author": "sweetwilliam",
"permlink": "the-bitcoin-paper-a-reader-s-companion",
"weight": 10000
}
]
}ubgupvoted (1.00%) @sweetwilliam / the-bitcoin-paper-a-reader-s-companion2018/05/09 19:02:57
ubgupvoted (1.00%) @sweetwilliam / the-bitcoin-paper-a-reader-s-companion
2018/05/09 19:02:57
| voter | ubg |
| author | sweetwilliam |
| permlink | the-bitcoin-paper-a-reader-s-companion |
| weight | 100 (1.00%) |
| Transaction Info | Block #22286786/Trx 15006693954eb16ce82372d36be2580ee2272e66 |
View Raw JSON Data
{
"trx_id": "15006693954eb16ce82372d36be2580ee2272e66",
"block": 22286786,
"trx_in_block": 15,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-09T19:02:57",
"op": [
"vote",
{
"voter": "ubg",
"author": "sweetwilliam",
"permlink": "the-bitcoin-paper-a-reader-s-companion",
"weight": 100
}
]
}sweetwilliampublished a new post: the-bitcoin-paper-a-reader-s-companion2018/05/09 19:01:57
sweetwilliampublished a new post: the-bitcoin-paper-a-reader-s-companion
2018/05/09 19:01:57
| parent author | |
| parent permlink | bitcoin |
| author | sweetwilliam |
| permlink | the-bitcoin-paper-a-reader-s-companion |
| title | The Bitcoin Paper - A Reader's Companion |
| body | <em>Bitcoin is open-source; its design is public, nobody owns or controls Bitcoin and everyone can take part.</em> <a href="https://bitcoin.org/en/"> - bitcoin.org</a> <b>Background</b>: the Bitcoin white paper was released under the pseudo-name Satoshi Nakamoto on 2008-10-31, poignantly this was a time when the traditional banking system was in turmoil at the onset of a global financial crisis. The identity of Satoshi Nakamoto is not known, with some speculating that Satoshi is actually a group rather than an individual. Satoshi circulated the Bitcoin paper on an internet mailing list for Cypherpunks, a group of activists that advocate the use of cryptography and privacy enhancing technologies as a route to social and political change. Creating a digital money independent of the traditional banking system for use on the internet had been a long term aspiration of the libertarian minded Cypherpunks. Ironically, much of the cryptography underpinning the sometimes lofty idealism of the Cypherpunk movement was developed in the 1970s within government intelligence agencies the NSA (USA) and GCHQ (UK). <b>Motivation</b>: in this post I will give additional commentary on the Bitcoin white paper, as well as definitions, and links to resources. I will quote the paper verbatim in the grey boxes, and highlight to define or further explain. On first reading the paper can seem sparse and obtuse, but with sufficient context and understanding I hope to demonstrate to you it's elegance, and momentous implications. The paper mainly describes the technical mechanisms underpinning the Bitcoin blockchain, but also touches on issues in banking, monetary policy, and incentive structures. The brilliance of the Bitcoin protocol is in the design of a system combining cryptographic techniques in a peer-to-peer network that has a concept of memory, with a self-regulating system of incentives. #### Links: * <a href="https://bitcoin.org/bitcoin.pdf" target="_blank">Bitcoin white paper</a> * <a href="https://www.activism.net/cypherpunk/manifesto.html">Cypherpunk Manifesto</a> ## Abstract --- <blockquote style="background:#f5f5f5;"> A purely <a href="#fn1">peer-to-peer</a> version of electronic cash would allow online payments to be sent directly from one party to another without going through a financial institution. <a href="#fn2">Digital signatures</a> provide part of the solution, but the main benefits are lost if a trusted third party is still required to prevent <a href="#fn3">double-spending</a>. We propose a solution to the double-spending problem using a peer-to-peer network. The network timestamps transactions by <a href="#fn4">hashing</a> them into an ongoing chain of hash-based proof-of-work, forming a record that cannot be changed without redoing the proof-of-work. The longest chain not only serves as proof of the sequence of events witnessed, but proof that it came from the largest pool of CPU power. As long as a majority of CPU power is controlled by nodes that are not cooperating to attack the network, they'll generate the longest chain and outpace attackers. The network itself requires minimal structure. Messages are broadcast on a <a href="#fn5">best effort</a> basis, and nodes can leave and rejoin the network at will, accepting the longest proof-of-work chain as proof of what happened while they were gone. </blockquote> Bitcoin is introduced as a peer-to-peer electronic cash using digital signatures to trace transactions, which overcomes the double-spending problem without relying on a trusted third party. The double-spending problem is overcome using a hash-based proof-of-work system. Some of the main properties of the Bitcoin network are that: * double-spending is prevented with a peer-to-peer network, * there is no mint or other trusted parties, * participants can be pseudo-anonymous, * new coins are made from Hashcash style proof-of-work, and * the proof-of-work for new coin generation also powers the network to prevent double-spending. Don't worry if this doesn't make sense to you at this stage, I recommend getting familiar with the following cryptographic and networking concepts, and then re-reading the abstract. Note proof-of-work is not introduced here since since it is discussed at length later. <p id="fn1"><b>Peer-to-peer</b>: a fundamental design feature of Bitcoin is that it is built as a peer-to-peer (P2P) network, as opposed to a client-server network. In a client-server architecture communication is usually to and from a central server providing resources. A P2P network is a distributed architecture, in which nodes are both conumers and suppliers of resources, removing the need for a centralised authority. In the case of Bitcoin a network designed for the transfer of value a centralised authority would be provided by a financial institution. The use of P2P networks first became widely popular with music sharing applications such as Napster, and then through file sharing with BitTorrent. <div style="margin-left: auto;margin-right: auto;text-align: justify;-ms-text-justify: distribute-all-lines;text-justify: distribute-all-lines;"> <a style="vertical-align:top; display:inline-block; *display:inline; zoom:1;"> <img src="https://steemitimages.com/DQmetns4LHAMmPDnCtXSzT7Ff9v3fFuYaucbai9TPPXCeJx/c2s.png" style="display:block; margin:0 auto;"> <p style="display:block; width:100%; text-align:center; color:black">client-to-server</p> </a> <a style="vertical-align:top; display:inline-block; *display:inline; zoom:1;"> <img src="https://steemitimages.com/DQmeEnnfQqyyP4iot7YuKvioqQjSTmS8dDCgV1x9ceAKmHd/p2p.png" style="display:block; margin:0 auto;"> <p style="display:block; width:100%; text-align:center; color:black">peer-to-peer</p> </a> </div> </p> <p id="fn4"><b>Hashing</b>: cryptographic hash functions are mathematical functions that can take any data and turn it into a fixed length output hash, where the same input data will reliably give the same output hash, if the data is even slightly modified then the hash will completely change. A hash function is a one way function, meaning if <em>f</em> is the hashing function, calculating <em>f(x)</em> is easy and fast, but trying to obtain <em>x</em> again is hard and infeasible due to the computational complexity. Hash functions are used, in digital signatures, message authentication codes, manipulation detection, fingerprints, checksums (message integrity check), hash tables, password storage and much more. Hashes are large numbers, usually written in hexadecimal. Bitcoin uses secure hash algorithm 2 (SHA-256), which returns a 256 bit hash string (represented as hexadecimal below), here is an example of sha256 hashing in python: In [1]: import hashlib In [2]: hashlib.sha256(b"here is a bytestring to be hashed").hexdigest() Out[2]: '7b02d50f844957522e4f1bb4514c0a76bd043eb87b290d43f21ca2508ea19e6b' In [3]: hashlib.sha256(b"here is another bytestring to be hashed").hexdigest() Out[3]: '1dbb72fc530b143d450fe3709c6c35d193fa8e1f6110acfdac6f2769f8eec7ce' </p> <p id="fn2"><b>Digital signatures</b>: a digital signature binds a person/entity to digital data, in a way that can be verified by a receiver or third party. This is analagous to signing a document by hand that binds the signatory to a message. In order to have a purely digital replacement for physical paper signatures, each user must be able to produce a message whose authenticity can be checked by anyone, but which could not have been produced by anyone else. In Bitcoin digital signatures provide a way to ensure that all transactions are only made by the rightful owners of that coin. Digital signatures are based on public key cryptography, a form of asymmetric cryptography. A public key algorithm such as RSA (Rivest–Shamir–Adleman) is commonly used, although Bitcoin and many cryptocurrencies use the more secure elliptic curve digital signature algorithm (ECDSA). In public key cryptography one can generate two keys that are mathematically linked, one private and one public. A digital signature is created by hashing a one-way hash of electronic data to be signed. The private key is then used to encrypt the hash. The encrypted hash along with extra information including the hashing algorithm is the digital signature. The hash is encrypted instead of the entire message since the hash is usually much shorter, saving time and computation. <div align="center"> <img src="https://steemitimages.com/DQmXe235tK6mruNcqWBJ3JsPTUFxERwqi5ZYqkjePTnwurR/digital_signatures.png" alt="digital signatures" style="max-width: 600px;"> </div> The hash value is unique to the input data, and any change in input data will result in a different hash value. Given this property others can validate the integrity of the data using the signer's public key to decrypt the hash. If the hash decrypted with the public key matches a second computed hash of the same data, it proves that the data has not been altered since signing. If the two hashes are not equal it is either a problem of integrity or authentication, that is to say that either the data has been tampered with, or the signature was created with a private key that does not correspond to the public key. Digital signatures can be used with any kind of message to check the sender's identity and to validate the message was not tampered with.</p> <p id="fn3"><b>Double-spending</b>: The double-spending problem is a potential flaw in a digital monetary system in which the same token can be replicated and spent more than once, thereby causing inflation and destroying trust in the system. Double-spending exists in cash based financial systems as money counterfeiting, but with digital data it is potentially much easier to replicate and distribute money. A central authority can be used to overcome this problem and validate all transactions, but it is harder in a distributed system like Bitcoin. Bitcoin is the first successful distributed system that overcomes the double-spending problem.</p> <p id="fn5"><b>Best effort basis</b>: Best effort basis is an agreement that something will be attempted without any guarantee provided that it will succeed. In terms of a network best-effort delivery describes a network service in which the network does not provide any guarantee that data is delivered or that delivery meets any quality of service.</p> #### Further reading: * <a href="https://www.plagiarismtoday.com/2017/06/01/the-long-slow-decline-of-bittorrent/" target="_blank">The long slow decline of bittorent</a> * <a href="https://en.wikipedia.org/wiki/Cryptographic_hash_function" target="_blank">Cryptographic hash function wikipedia</a> * <a href="https://www.tutorialspoint.com/cryptography/cryptography_digital_signatures.htm" target="_blank">Digital Signatures tutorial</a> * <a href="http://groups.csail.mit.edu/mac/classes/6.805/student-papers/fall97-papers/fillingham-sig.html" target="_blank">A Comparison of Digital and Handwritten Signatures</a> * <a href="https://www.youtube.com/watch?v=NF1pwjL9-DE" target="_blank">Video explaining elliptic curve cryptography</a> ## 1. Introduction --- <blockquote style="background:#f5f5f5;"> Commerce on the Internet has come to rely almost exclusively on financial institutions serving as trusted third parties to process electronic payments. While the system works well enough for most transactions, it still suffers from the inherent weaknesses of the trust based model. Completely non-reversible transactions are not really possible, since financial institutions cannot avoid mediating disputes. The cost of mediation increases transaction costs, limiting the minimum practical transaction size and cutting off the possibility for small casual transactions, and there is a broader cost in the loss of ability to make non-reversible payments for non-reversible services. With the possibility of reversal, the need for trust spreads. Merchants must be wary of their customers, hassling them for more information than they would otherwise need. A certain percentage of fraud is accepted as unavoidable. These costs and payment uncertainties can be avoided in person by using physical currency, but no mechanism exists to make payments over a communications channel without a trusted party. What is needed is an electronic payment system based on cryptographic proof instead of trust, allowing any two willing parties to transact directly with each other without the need for a trusted third party. Transactions that are computationally impractical to reverse would protect sellers from fraud, and routine <a href="#fn6">escrow mechanisms</a> could easily be implemented to protect buyers. In this paper, we propose a solution to the double-spending problem using a peer-to-peer distributed timestamp server to generate computational proof of the chronological order of transactions. The system is secure as long as honest nodes collectively control more CPU power than any cooperating group of attacker nodes. </blockquote> It is interesting to note that since publication in 2008 the original use case presented of Bitcoin has changed, due to constraints on the number of transactions the network can process. Transactions are throttled by the size and frequency of blocks in the blockchain. The original intention of Bitcoin was to facilitate low value non-reversible transactions, with the idea that the cost is reduced since no third party is required to mediate disputes. However, as the network has grown and the number of transactions has increased the fees to use network have also increased. This increase in fees makes small value transactions uneconomical. Engineers are now working on so called 'layer 2' solutions to the scalability problem such as the lightning network that take transactions off-chain, thus reducing transaction fees and congestion on the Bitcoin network. <br><p id="fn6"><b>Escrow mechanisms</b>: An escrow is a contractual arrangement in which a third party receives and disburses money or documents for the primary transacting parties, with the disbursement dependent on conditions agreed to by the transacting parties, or an account established by a broker for holding funds on behalf of the broker's principal or some other person until the consummation or termination of a transaction. An escrow mechanism can be used for example to release funds once an item bought online has been received. </p> #### Further reading: * <a href="https://lightning.network/" target="_blank">Lightning network website</a> * <a href="https://en.wikipedia.org/wiki/Lightning_Network" target="_blank">Lightning network wiki</a> ## 2. Transactions --- <blockquote style="background:#f5f5f5;"> We define an electronic coin as a chain of digital signatures. Each owner transfers the coin to the next by digitally signing a hash of the previous transaction and the public key of the next owner and adding these to the end of the coin. A payee can verify the signatures to verify the chain of ownership. <div align="center"> <img src="https://steemitimages.com/DQmV1fvCbeAuXPc7N5HM2BAyzfvhDDVEEvA4GauA6qrJHFk/transactions.png" alt="transactions" style="max-width:200px; padding-right:80px;"> </div> The problem of course is the payee can't verify that one of the owners did not double-spend the coin. A common solution is to introduce a trusted central authority, or mint, that checks every transaction for double spending. After each transaction, the coin must be returned to the mint to issue a new coin, and only coins issued directly from the mint are trusted not to be double-spent. The problem with this solution is that the fate of the entire money system depends on the company running the mint, with every transaction having to go through them, just like a bank. <br><br>We need a way for the payee to know that the previous owners did not sign any earlier transactions. For our purposes, the earliest transaction is the one that counts, so we don't care about later attempts to double-spend. The only way to confirm the absence of a transaction is to be aware of all transactions. In the mint based model, the mint was aware of all transactions and decided which arrived first. To accomplish this without a trusted party, transactions must be publicly announced <a href="#ref1">[1]</a>, and we need a system for participants to agree on a single history of the order in which they were received. The payee needs proof that at the time of each transaction, the majority of nodes agreed it was the first received. </blockquote> This section describes how Bitcoin are moved through the system using a sequence of transfers made with digital signatures. The history of each and every Bitcoin transaction leads back to the point where the bitcoins were first produced. Be aware that the transaction mechanism shown here is not the same as the concept of a blockchain, which is discussed later, but rather how money is traced and transferred through the network. The important part here is to understand the figure, showing how at each stage the owner is a person/entity holding the private key that gives them the ability to spend/transfer that money. When a transaction is broadcast other users can validate based on the public key of the signer, to ensure they have sufficient funds to make the transaction. This is facilitated by the asymmetry of the public-private key pair, whereby anyone can decrypt the signature and verify the transaction but only the owner can encrypt and sign to create another transaction. Although this is a useful way to keep track of ownership, there is nothing to stop somebody spending their coins more than once, i.e. the double-spending problem. ## 3. Timestamp Server --- <blockquote style="background:#f5f5f5;"> The solution we propose begins with a timestamp server. A timestamp server works by taking a hash of a block of items to be timestamped and widely publishing the hash, such as in a newspaper or <a href="#fn7">Usenet post</a> <a href="#ref2">[2,</a> <a href="#ref3"> 3,</a> <a href="#ref4"> 4,</a> <a href="#ref5"> 5]</a>. The timestamp proves that the data must have existed at the time, obviously, in order to get into the hash. Each timestamp includes the previous timestamp in its hash, forming a chain, with each additional timestamp reinforcing the ones before it. <div align="center"> <img src="https://steemitimages.com/DQmTza1XMZNVLyTxCk366sD1xqQZos4n2bQsmsTtzKBi31t/timestamp_server.png" alt="transactions" style="max-width:500px; padding-right:80px;"> </div> </blockquote> At this point Satoshi introduces the concept of a chain of timestamped blocks, also known as the blockchain. The first work on a cryptographically secured chain of blocks was described in 1991 by Stuart Haber and W. Scott Stornetta for time stamping digital documents. The idea here is to group transactions into blocks to verify that a transaction existed at a certain time, in this way we can overcome the double-spending problem by knowing whether coins have already been spent at a certain time, since these blocks are broadcast to the network, and the most recent block on the longest chain accepted as the current state of the ledger. When you sign a transaction and broadcast to the network, it is not immediately assimilated into the blockchain. But depending on the transaction fee and load on the network it will be compiled into a block. As more blocks are added to the chain the transaction becomes ossified in the history, since it would require increasing proof-of-work to go back and change the record. <p id="fn7"><b>Usenet</b>: An early peer-to-peer architecture mentioned in the Bitcoin paper is USENET, a distributed messaging system developed in 1979. Users read and post messages (called articles or posts, and collectively termed news) to one or more categories, known as newsgroups.</p> #### Further reading: * <a href="https://en.wikipedia.org/wiki/Blockchain" target="_blank">Blockchain wiki</a> * <a href="https://link.springer.com/article/10.1007%2FBF00196791" target="_blank">How to time-stamp a digital document</a> ## 4. Proof-of-Work --- <blockquote style="background:#f5f5f5;"> To implement a distributed timestamp server on a peer-to-peer basis, we will need to use a proof-of-work system similar to Adam Back's <a href="#fn7">Hashcash</a> <a href="#ref6">[6]</a>, rather than newspaper or Usenet posts. The proof-of-work involves scanning for a value that when hashed, such as with SHA-256, the hash begins with a number of zero bits. The average work required is exponential in the number of zero bits required and can be verified by executing a single hash. <br><br>For our timestamp network, we implement the proof-of-work by incrementing a nonce in the block until a value is found that gives the block's hash the required zero bits. Once the CPU effort has been expended to make it satisfy the proof-of-work, the block cannot be changed without redoing the work. As later blocks are chained after it, the work to change the block would include redoing all the blocks after it. <div align="center"> <img src="https://steemitimages.com/DQmVsXjFwceGQ3qKpjNWbUgvRimgMuVPgQ4nyAWr1KVUor9/proof_of_work.png" style="max-width:500px; padding-right:80px;"> </div> The proof-of-work also solves the problem of determining representation in majority decision making. If the majority were based on one-IP-address-one-vote, it could be subverted by anyone able to allocate many IPs. Proof-of-work is essentially one-CPU-one-vote. The majority decision is represented by the longest chain, which has the greatest proof-of-work effort invested in it. If a majority of CPU power is controlled by honest nodes, the honest chain will grow the fastest and outpace any competing chains. To modify a past block, an attacker would have to redo the proof-of-work of the block and all blocks after it and then catch up with and surpass the work of the honest nodes. We will show later that the probability of a slower attacker catching up diminishes exponentially as subsequent blocks are added. <br><br>To compensate for increasing hardware speed and varying interest in running nodes over time, the proof-of-work difficulty is determined by a moving average targeting an average number of blocks per hour. If they're generated too fast, the difficulty increases. </blockquote> The proof-of-work system is a kind of puzzle that miners on the network compete to solve first. Miners will first combine transactions into a block according to the rules of the network. They use the block header and a nonce value to to generate a hash, if the hash is less than a target value they win. This is done by randomly or pseudo-randomly changing a nonce value in the block until a hash is achieved with sufficient number of leading zeros. The more zeroes the more rare the hash is. A good hash' outcome is not predictable, and so you have to try a lot of times to find a good nonce. The amount of zeroes are based on how difficult it is supposed to be to find a block. In Bitcoin it adjusts to have a new block every 10 minutes (on average, given the rate at which previous blocks are found). So for example the first hash ever found was the following, note the previous block is all zeros since there was no previous block! Block 0 Hash 000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f Previous Block 0000000000000000000000000000000000000000000000000000000000000000 As you can see by block 100000, as more miners have joined the network the hashing power has increased, and the number of leading zeros in the hash to be found is also increased. Adjusting the number of leading zeros is how the system regulates the blocktime. Block 100000 Hash 000000000003ba27aa200b1cecaad478d2b00432346c3f1f3986da1afd33e506 Previous Block 000000000002d01c1fccc21636b607dfd930d31d01c3a62104612a1719011250 Again by block 500000 the difficult has increased again (more leading zeros). Block 500000 Hash 00000000000000000024fb37364cbf81fd49cc2d51c09c75c35433c3a1945d04 Previous Block 0000000000000000007962066dcd6675830883516bcf40047d42740a85eb2919 When a miner finds a hash with enough leading zeros, you can think of it as them winning that competition. They can then propagate the block to the network and mint themselves some Bitocin. This distributed proof-of-work system is how Bitcoin obtains consensus. In order to achieve this the system has to overcome the Byzantine General's Problem, a classic problem faced by any distributed computer system network. The Byzantine General's problem is explained through a scenario in which multiple divisions of an army are laying seige to a city. Each division has a general, that can communicate to other generals via a messenger. A majority have to agree to attack or to defend, but the difficulty arises since some of the generals or messengers may be untrustworthy. A networked system is Byzantine Fault Tolerant if the system is dependable, where components may fail and there is imperfect information on whether a component is failed. So if one or more generals decide to go rogue and ignore the other generals then so long as they are not a majority the system will tolerate it. The bitcoin network works in parallel to generate a chain of Hashcash style proof-of-work. The proof-of-work chain is the key to overcome Byzantine failures and to reach a coherent global view of the system state. When a miner has done sufficient work to obtain a hash they are incentivised to obey the rules of the network and generate a valid block and claim their reward in Bitcoins. This overcomes the Byzantine General's problem since it becomes very expensive to become a bad actor and attack the network. It also makes it extremely computationally expensive to rewrite historical transactions on the network since the proof-of-work has to be done again for all blocks since the transaction. Proof-of-work is not the only mechanism for achieving a consensus, other approaches such as proof-of-stake, and delegated proof-of-stake are being used. These are advantageous in their lower energy consumption. Attempts have also been made by cryptocurrencies like Primecoin which requires clients to find unknown prime numbers of certain types, which can have useful side-applications. <p id="fn8"><b>Hashcash</b>: is a proof-of-work system used to limit email spam and denial-of-service attacks. The idea was to require that some computational work be done in order to send an e-mail, the receiver can then verify that work has been done. This would make it expensive to send spam e-mails to thousands of addresses.</p> #### Further reading: * <a href="https://www.youtube.com/watch?v=r0pcpGduaJw" target="_blank">Jackson Palmer (Dogecoin) describes consensus mechanisms</a> * <a href="https://en.wikipedia.org/wiki/Proof-of-work_system" target="_blank">Proof-of-work wiki</a> ## 5. Network --- <blockquote style="background:#f5f5f5;"> The steps to run the network are as follows: <ol> <li>New transactions are broadcast to all nodes.</li> <li>Each node collects new transactions into a block.</li> <li>Each node works on finding a difficult proof-of-work for its block.</li> <li>When a node finds a proof-of-work, it broadcasts the block to all nodes.</li> <li>Nodes accept the block only if all transactions in it are valid and not already spent.</li> <li>Nodes express their acceptance of the block by working on creating the next block in the chain, using the hash of the accepted block as the previous hash.</li> </ol> Nodes always consider the longest chain to be the correct one and will keep working on extending it. If two nodes broadcast different versions of the next block simultaneously, some nodes may receive one or the other first. In that case, they work on the first one they received, but save the other branch in case it becomes longer. The tie will be broken when the next proof-of-work is found and one branch becomes longer; the nodes that were working on the other branch will then switch to the longer one. <br><br>New transaction broadcasts do not necessarily need to reach all nodes. As long as they reach many nodes, they will get into a block before long. Block broadcasts are also tolerant of dropped messages. If a node does not receive a block, it will request it when it receives the next block and realizes it missed one. </blockquote> For a bit of clarity any computer that connects to the Bitcoin network is called a node. Nodes that fully verify all of the rules of Bitcoin are called full nodes. Full nodes in the Bitcoin network have a complete copy of the blockchain and are able to verify all transactions since the genesis block at the start of the network. Basically, the miner works on transactions by coming up with the best combination to store that information. Miners spend about 10 minutes working on a problem, but nodes keep that result forever after in the database and verify it with others. Miners don't need to know about prior blocks (except for the prior one) with very few exceptions. #### Further reading: * <a href="https://en.bitcoin.it/wiki/Full_node" target="_blank">Bitcoin full node wiki</a> ## 6. Incentive --- <blockquote style="background:#f5f5f5;"> By convention, the first transaction in a block is a special transaction that starts a new coin owned by the creator of the block. This adds an incentive for nodes to support the network, and provides a way to initially distribute coins into circulation, since there is no central authority to issue them. The steady addition of a constant of amount of new coins is analogous to gold miners expending resources to add gold to circulation. In our case, it is CPU time and electricity that is expended. <br><br>The incentive can also be funded with transaction fees. If the output value of a transaction is less than its input value, the difference is a transaction fee that is added to the incentive value of the block containing the transaction. Once a predetermined number of coins have entered circulation, the incentive can transition entirely to transaction fees and be completely inflation free. <br><br>The incentive may help encourage nodes to stay honest. If a greedy attacker is able to assemble more CPU power than all the honest nodes, he would have to choose between using it to defraud people by stealing back his payments, or using it to generate new coins. He ought to find it more profitable to play by the rules, such rules that favour him with more new coins than everyone else combined, than to undermine the system and the validity of his own wealth. </blockquote> The total number of Bitcoins that can be mined is slightly less than 21 million, with the rate at which Bitcoins can be mined reducing over time, in a halving event approximately every 4 years, from 50 BTC per block, to 25 BTC, to 12.5 BTC etc. This leads to a deflationary currency, since the rate of increase in supply is reducing over time and will reach a stable number of coins around the year 2140. When miners can no longer mint new Bitcoins the network will sustain only on transaction fees alone. #### Further reading: * <a href="https://en.bitcoin.it/wiki/Controlled_supply" target="_blank">Bitcoin supply wiki</a> * <a href="https://blockchain.info/charts/total-bitcoins?timespan=all" target="_blank">Graph of Bitcoin's mined</a> ## 7. Reclaiming Disk Space --- <blockquote style="background:#f5f5f5;"> Once the latest transaction in a coin is buried under enough blocks, the spent transactions before it can be discarded to save disk space. To facilitate this without breaking the block's hash, transactions are hashed in a <a href="#fn9">Merkle Tree</a> <a href="#ref7">[7,</a> <a href="#ref2"> 2,</a> <a href="#ref5"> 5]</a>, with only the root included in the block's hash. Old blocks can then be compacted by stubbing off branches of the tree. The interior hashes do not need to be stored. <div align="center"> <img src="https://steemitimages.com/DQmP3871pXHsUe5sR1WLeYmNN96CShLLMGt4qnyn2QsfFax/merkle.png" style="max-width:500px; padding-right:80px;"> </div> A block header with no transactions would be about 80 bytes. If we suppose blocks are generated every 10 minutes, 80 bytes * 6 * 24 * 365 = 4.2MB per year. With computer systems typically selling with 2GB of RAM as of 2008, and Moore's Law predicting current growth of 1.2GB per year, storage should not be a problem even if the block headers must be kept in memory. </blockquote> <p id="fn9"><b>Merkle Tree</b>: a Merkle tree is a hash-based data structure that is a generalisation of the hash list. It is a tree structure in which each leaf node is a hash of a block of data, and each non-leaf node is a hash of its children. Typically, Merkle trees have a branching factor of 2, meaning that each node has up to 2 children. Hash trees can be used to verify any kind of data stored, handled and transferred in and between computers. They can help ensure that data blocks received from other peers in a peer-to-peer network are received undamaged and unaltered, and even to check that the other peers do not lie and send fake blocks. </p> #### Further reading: * <a href="https://en.wikipedia.org/wiki/Merkle_tree" target="_blank">Merkle tree wiki</a> ## 8. Simplified Payment Verification --- <blockquote style="background:#f5f5f5;"> Once the latest transaction in a coin is buried under enough blocks, the spent transactions before it can be discarded to save disk space. To facilitate this without breaking the block's hash, transactions are hashed in a Merkle Tree <a href="#ref7">[7,</a> <a href="#ref2"> 2,</a> <a href="#ref5"> 5]</a>, with only the root included in the block's hash. Old blocks can then be compacted by stubbing off branches of the tree. The interior hashes do not need to be stored. <div align="center"> <img src="https://steemitimages.com/DQmWLopYBYqrYxGRJoby6Sib29RW2WbW6G14CUMjRDQgXV8/spv.png" style="width:80%"> </div> As such, the verification is reliable as long as honest nodes control the network, but is more vulnerable if the network is overpowered by an attacker. While network nodes can verify transactions for themselves, the simplified method can be fooled by an attacker's fabricated transactions for as long as the attacker can continue to overpower the network. One strategy to protect against this would be to accept alerts from network nodes when they detect an invalid block, prompting the user's software to download the full block and alerted transactions to confirm the inconsistency. Businesses that receive frequent payments will probably still want to run their own nodes for more independent security and quicker verification. <br><br>A block header with no transactions would be about 80 bytes. If we suppose blocks are generated every 10 minutes, 80 bytes * 6 * 24 * 365 = 4.2MB per year. With computer systems typically selling with 2GB of RAM as of 2008, and Moore's Law predicting current growth of 1.2GB per year, storage should not be a problem even if the block headers must be kept in memory. </blockquote> Simplified payment verification is a method for verifying if particular transactions are included in a block without downloading the entire block. The method is used by some lightweight Bitcoin clients. The simplified verification verification client only needs download the block headers, which are much smaller than the full blocks. To verify that a transaction is in a block, a simplified verification client requests a proof of inclusion, in the form of a Merkle branch. #### Further reading: * <a href="https://en.bitcoin.it/wiki/Thin_Client_Security" target="_blank">Thin Client Security</a> ## 9. Combining and Splitting Value --- <blockquote style="background:#f5f5f5;"> Although it would be possible to handle coins individually, it would be unwieldy to make a separate transaction for every cent in a transfer. To allow value to be split and combined, transactions contain multiple inputs and outputs. Normally there will be either a single input from a larger previous transaction or multiple inputs combining smaller amounts, and at most two outputs: one for the payment, and one returning the change, if any, back to the sender. <div align="center"> <img src="https://steemitimages.com/DQmbgDQ82GCAo5gPFvmZFBXv7rgqo2YiJLX59yqrJjzZQqi/utxo.png" style="max-width:300px; padding-right:80px;"> </div> It should be noted that fan-out, where a transaction depends on several transactions, and those transactions depend on many more, is not a problem here. There is never the need to extract a complete standalone copy of a transaction's history. </blockquote> #### Further reading: * <a href="https://pascalpares.gitbooks.io/implementation-of-the-bitcoin-system/content/1-transaction-4-structure.html" target="_blank">Information on transaction structure</a> * <a href="https://medium.com/@aalim.khan/bitcoin-transactions-scripts-and-digital-signatures-506688e1630a" target="_blank">Bitcoin transactions, scripts and digital signatures</a> ## 10. Privacy --- <blockquote style="background:#f5f5f5;"> The traditional banking model achieves a level of privacy by limiting access to information to the parties involved and the trusted third party. The necessity to announce all transactions publicly precludes this method, but privacy can still be maintained by breaking the flow of information in another place: by keeping public keys anonymous. The public can see that someone is sending an amount to someone else, but without information linking the transaction to anyone. This is similar to the level of information released by stock exchanges, where the time and size of individual trades, the "tape", is made public, but without telling who the parties were. <div align="center"> <img src="https://steemitimages.com/DQmTmxcTK1zUHvRLJGJaTfSM37HAHykhGYUHU7jLnGrYxCD/privacy.png" style="max-width:600px; padding-right:80px;"> </div> As an additional firewall, a new key pair should be used for each transaction to keep them from being linked to a common owner. Some linking is still unavoidable with multi-input transactions, which necessarily reveal that their inputs were owned by the same owner. The risk is that if the owner of a key is revealed, linking could reveal other transactions that belonged to the same owner. </blockquote> Bitcoin is often perceived as an anonymous payment network, but in actuality it is very transparent since all transactions are recorded. By combining transactions and through analysing groups of transactions the anonymity of Bitcoin can be compromised. Other cryptocurrencies such as Monero, and Zcash attempt to provide a more anonymous payment method, but at the expense of computation. #### Further reading: * <a href="https://bitcoin.org/en/protect-your-privacy" target="_blank">Bitcoin privacy</a> ## 11. Calculations --- <blockquote style="background:#f5f5f5;"> We consider the scenario of an attacker trying to generate an alternate chain faster than the honest chain. Even if this is accomplished, it does not throw the system open to arbitrary changes, such as creating value out of thin air or taking money that never belonged to the attacker. Nodes are not going to accept an invalid transaction as payment, and honest nodes will never accept a block containing them. An attacker can only try to change one of his own transactions to take back money he recently spent. <br><br>The race between the honest chain and an attacker chain can be characterized as a Binomial Random Walk. The success event is the honest chain being extended by one block, increasing its lead by +1, and the failure event is the attacker's chain being extended by one block, reducing the gap by -1. The probability of an attacker catching up from a given deficit is analogous to a Gambler's Ruin problem. Suppose a gambler with unlimited credit starts at a deficit and plays potentially an infinite number of trials to try to reach breakeven. We can calculate the probability he ever reaches breakeven, or that an attacker ever catches up with the honest chain, as follows <a href="#ref8">[8]</a>: <br> <br> p = probability an honest node finds the next block <br> q = probability the attacker finds the next block <br> q<sub>z</sub> = probability the attacker will ever catch up from z blocks behind <div align="center"> <img src="https://steemitimages.com/DQmcwZwezcs4nK5rLcimQX3fLR3z3AeWXrDDoBVospw3q7T/equation1.png" style="max-width:300px; padding-right:80px;"> </div> Given our assumption that p > q, the probability drops exponentially as the number of blocks the attacker has to catch up with increases. With the odds against him, if he doesn't make a lucky lunge forward early on, his chances become vanishingly small as he falls further behind. <br><br>We now consider how long the recipient of a new transaction needs to wait before being sufficiently certain the sender can't change the transaction. We assume the sender is an attacker who wants to make the recipient believe he paid him for a while, then switch it to pay back to himself after some time has passed. The receiver will be alerted when that happens, but the sender hopes it will be too late. <br><br>The receiver generates a new key pair and gives the public key to the sender shortly before signing. This prevents the sender from preparing a chain of blocks ahead of time by working on it continuously until he is lucky enough to get far enough ahead, then executing the transaction at that moment. Once the transaction is sent, the dishonest sender starts working in secret on a parallel chain containing an alternate version of his transaction. <br><br>The recipient waits until the transaction has been added to a block and z blocks have been linked after it. He doesn't know the exact amount of progress the attacker has made, but assuming the honest blocks took the average expected time per block, the attacker's potential progress will be a Poisson distribution with expected value: <div align="center"> <img src="https://steemitimages.com/DQmdsRSkrU8Hs7ZXW3CWDwUT3pPRENXzRjy1SCVrCQ414S2/equation2.png" style="max-width:400px; padding-right:80px;"> </div> To get the probability the attacker could still catch up now, we multiply the Poisson density for each amount of progress he could have made by the probability he could catch up from that point: <div align="center"> <img src="https://steemitimages.com/DQmXaTaRpNvEvyvV8aUPhvv4hncP1sfwuXBehdbZscjpb8Y/equation3.png" style="max-width:400px; padding-right:80px;"> </div> Rearranging to avoid summing the infinite tail of the distribution... <div align="center"> <img src="https://steemitimages.com/DQmWdLjgjP14o55xKJ7SjY2GhLiJoUUXtVLmoPDeSoX8Ubj/equation4.png" style="max-width:400px; padding-right:80px;"> </div> Converting to C code... include math.h double AttackerSuccessProbability(double q, int z) { double p = 1.0 - q; double lambda = z * (q / p); double sum = 1.0; int i, k; for (k = 0; k <= z; k++) { double poisson = exp(-lambda); for (i = 1; i <= k; i++) poisson *= lambda / i; sum -= poisson * (1 - pow(q / p, z - k)); } return sum; } Running some results, we can see the probability drop off exponentially with z. q=0.1 z=0 P=1.0000000 z=1 P=0.2045873 z=2 P=0.0509779 z=3 P=0.0131722 z=4 P=0.0034552 z=5 P=0.0009137 z=6 P=0.0002428 z=7 P=0.0000647 z=8 P=0.0000173 z=9 P=0.0000046 z=10 P=0.0000012 q=0.3 z=0 P=1.0000000 z=5 P=0.1773523 z=10 P=0.0416605 z=15 P=0.0101008 z=20 P=0.0024804 z=25 P=0.0006132 z=30 P=0.0001522 z=35 P=0.0000379 z=40 P=0.0000095 z=45 P=0.0000024 z=50 P=0.0000006 Solving for P less than 0.1%... P less than 0.001 q=0.10 z=5 q=0.15 z=8 q=0.20 z=11 q=0.25 z=15 q=0.30 z=24 q=0.35 z=41 q=0.40 z=89 q=0.45 z=340 </blockquote> #### Further reading: * <a href="https://en.bitcoin.it/wiki/Weaknesses" target="_blank">Bitcoin weaknesses</a> ## 12. Conclusion --- <blockquote style="background:#f5f5f5;"> We have proposed a system for electronic transactions without relying on trust. We started with the usual framework of coins made from digital signatures, which provides strong control of ownership, but is incomplete without a way to prevent double-spending. To solve this, we proposed a peer-to-peer network using proof-of-work to record a public history of transactions that quickly becomes computationally impractical for an attacker to change if honest nodes control a majority of CPU power. The network is robust in its unstructured simplicity. Nodes work all at once with little coordination. They do not need to be identified, since messages are not routed to any particular place and only need to be delivered on a best effort basis. Nodes can leave and rejoin the network at will, accepting the proof-of-work chain as proof of what happened while they were gone. They vote with their CPU power, expressing their acceptance of valid blocks by working on extending them and rejecting invalid blocks by refusing to work on them. Any needed rules and incentives can be enforced with this consensus mechanism. </blockquote> Et voila! This paper did not cause much of a stir on release, but Satoshi worked to build a minimum implementation. At a couple of points in its early history the Bitcoin project was almost completely abandoned. However, over time a core team of devoted developers emerged and the Bitcoin protocol and ecosystem has flourished since, opening a pandora's box of innovation in distributed transfer of value over the internet. That is not to say that it has not had its fair share of challenges and drama, but this remarkable peer-to-peer electronic cash is still going strong! #### Further reading: * <a href="https://www.youtube.com/watch?v=DjYbsq3FXfM" target="_blank">Visualisation of Bitcoin development on github</a> ## References --- <blockquote style="background:#f5f5f5;"> <p id="ref1"> [1] W. Dai, "<a href="http://www.weidai.com/bmoney.txt" target="_blank">b-money</a>," http://www.weidai.com/bmoney.txt, 1998. </p> <p id="ref2"> [2] H. Massias, X.S. Avila, and J.-J. Quisquater, "<a href="http://nakamotoinstitute.org/literature/secure-timestamping-service/" target="_blank">Design of a secure timestamping service with minimal trust requirements,</a>" In 20th Symposium on Information Theory in the Benelux, May 1999. </p> <p id="ref3"> [3] S. Haber, W.S. Stornetta, "<a href="https://link.springer.com/article/10.1007/BF00196791" target="_blank">How to time-stamp a digital document,</a>." In Journal of Cryptology, vol 3, no2, pages 99-111, 1991. </p> <p id="ref4"> [4] D. Bayer, S. Haber, W.S. Stornetta, "<a href="https://link.springer.com/chapter/10.1007/978-1-4613-9323-8_24" target="_blank">Improving the efficiency and reliability of digital time-stamping,</a>" In Sequences II: Methods in Communication, Security and Computer Science, pages 329-334, 1993. </p> <p id="ref5"> [5] S. Haber, W.S. Stornetta, "<a href="http://nakamotoinstitute.org/static/docs/secure-names-bit-strings.pdf" target="_blank">Secure names for bit-strings,</a>" In Proceedings of the 4th ACM Conference on Computer and Communications Security, pages 28-35, April 1997. </p> <p id="ref5"> [6] A. Back, "<a href="http://www.hashcash.org/papers/hashcash.pdf" target="_blank">Hashcash - a denial of service counter-measure,</a>" http://www.hashcash.org/papers/hashcash.pdf, 2002. </p> <p id="ref5"> [7] R.C. Merkle, "<a href="http://ieeexplore.ieee.org/document/6233691" target="_blank">Protocols for public key cryptosystems,</a>" In Proc. 1980 Symposium on Security and Privacy, IEEE Computer Society, pages 122-133, April 1980. </p> <p id="ref5"> [8] W. Feller, "<a href="https://www.wiley.com/en-us/An+Introduction+to+Probability+Theory+and+Its+Applications%2C+Volume+2%2C+2nd+Edition-p-9780471257097" target="_blank">An introduction to probability theory and its applications,</a>" 1957. </p> </blockquote> It is interesting to note the pioneering Nick Szabo's work on systems such as bit gold is not referenced here ;-) |
| json metadata | {"tags":["bitcoin","cryptocurrency","blog","writing","technology"],"image":["https://steemitimages.com/DQmetns4LHAMmPDnCtXSzT7Ff9v3fFuYaucbai9TPPXCeJx/c2s.png","https://steemitimages.com/DQmeEnnfQqyyP4iot7YuKvioqQjSTmS8dDCgV1x9ceAKmHd/p2p.png","https://steemitimages.com/DQmXe235tK6mruNcqWBJ3JsPTUFxERwqi5ZYqkjePTnwurR/digital_signatures.png","https://steemitimages.com/DQmV1fvCbeAuXPc7N5HM2BAyzfvhDDVEEvA4GauA6qrJHFk/transactions.png","https://steemitimages.com/DQmTza1XMZNVLyTxCk366sD1xqQZos4n2bQsmsTtzKBi31t/timestamp_server.png","https://steemitimages.com/DQmVsXjFwceGQ3qKpjNWbUgvRimgMuVPgQ4nyAWr1KVUor9/proof_of_work.png","https://steemitimages.com/DQmP3871pXHsUe5sR1WLeYmNN96CShLLMGt4qnyn2QsfFax/merkle.png","https://steemitimages.com/DQmWLopYBYqrYxGRJoby6Sib29RW2WbW6G14CUMjRDQgXV8/spv.png","https://steemitimages.com/DQmbgDQ82GCAo5gPFvmZFBXv7rgqo2YiJLX59yqrJjzZQqi/utxo.png","https://steemitimages.com/DQmTmxcTK1zUHvRLJGJaTfSM37HAHykhGYUHU7jLnGrYxCD/privacy.png","https://steemitimages.com/DQmcwZwezcs4nK5rLcimQX3fLR3z3AeWXrDDoBVospw3q7T/equation1.png","https://steemitimages.com/DQmdsRSkrU8Hs7ZXW3CWDwUT3pPRENXzRjy1SCVrCQ414S2/equation2.png","https://steemitimages.com/DQmXaTaRpNvEvyvV8aUPhvv4hncP1sfwuXBehdbZscjpb8Y/equation3.png","https://steemitimages.com/DQmWdLjgjP14o55xKJ7SjY2GhLiJoUUXtVLmoPDeSoX8Ubj/equation4.png"],"links":["https://bitcoin.org/en/","https://bitcoin.org/bitcoin.pdf","https://www.activism.net/cypherpunk/manifesto.html","#fn1","#fn2","#fn3","#fn4","#fn5","https://www.plagiarismtoday.com/2017/06/01/the-long-slow-decline-of-bittorrent/","https://en.wikipedia.org/wiki/Cryptographic_hash_function","https://www.tutorialspoint.com/cryptography/cryptography_digital_signatures.htm","http://groups.csail.mit.edu/mac/classes/6.805/student-papers/fall97-papers/fillingham-sig.html","https://www.youtube.com/watch?v=NF1pwjL9-DE","#fn6","https://lightning.network/","https://en.wikipedia.org/wiki/Lightning_Network","#ref1","#fn7","#ref2","#ref3","#ref4","#ref5","https://en.wikipedia.org/wiki/Blockchain","https://link.springer.com/article/10.1007%2FBF00196791","#ref6","https://www.youtube.com/watch?v=r0pcpGduaJw","https://en.wikipedia.org/wiki/Proof-of-work_system","https://en.bitcoin.it/wiki/Full_node","https://en.bitcoin.it/wiki/Controlled_supply","https://blockchain.info/charts/total-bitcoins?timespan=all","#fn9","#ref7","https://en.wikipedia.org/wiki/Merkle_tree","https://en.bitcoin.it/wiki/Thin_Client_Security","https://pascalpares.gitbooks.io/implementation-of-the-bitcoin-system/content/1-transaction-4-structure.html","https://medium.com/@aalim.khan/bitcoin-transactions-scripts-and-digital-signatures-506688e1630a","https://bitcoin.org/en/protect-your-privacy","#ref8","https://en.bitcoin.it/wiki/Weaknesses","https://www.youtube.com/watch?v=DjYbsq3FXfM","http://www.weidai.com/bmoney.txt","http://nakamotoinstitute.org/literature/secure-timestamping-service/","https://link.springer.com/article/10.1007/BF00196791","https://link.springer.com/chapter/10.1007/978-1-4613-9323-8_24","http://nakamotoinstitute.org/static/docs/secure-names-bit-strings.pdf","http://www.hashcash.org/papers/hashcash.pdf","http://ieeexplore.ieee.org/document/6233691","https://www.wiley.com/en-us/An+Introduction+to+Probability+Theory+and+Its+Applications%2C+Volume+2%2C+2nd+Edition-p-9780471257097"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #22286766/Trx b2491d325a976e9fb8c479ed6334b291ebecb4f7 |
View Raw JSON Data
{
"trx_id": "b2491d325a976e9fb8c479ed6334b291ebecb4f7",
"block": 22286766,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-09T19:01:57",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "bitcoin",
"author": "sweetwilliam",
"permlink": "the-bitcoin-paper-a-reader-s-companion",
"title": "The Bitcoin Paper - A Reader's Companion",
"body": "<em>Bitcoin is open-source; its design is public, nobody owns or controls Bitcoin and everyone can take part.</em> <a href=\"https://bitcoin.org/en/\"> - bitcoin.org</a>\n\n<b>Background</b>: the Bitcoin white paper was released under the pseudo-name Satoshi Nakamoto on 2008-10-31, poignantly this was a time when the traditional banking system was in turmoil at the onset of a global financial crisis. The identity of Satoshi Nakamoto is not known, with some speculating that Satoshi is actually a group rather than an individual. Satoshi circulated the Bitcoin paper on an internet mailing list for Cypherpunks, a group of activists that advocate the use of cryptography and privacy enhancing technologies as a route to social and political change. Creating a digital money independent of the traditional banking system for use on the internet had been a long term aspiration of the libertarian minded Cypherpunks. Ironically, much of the cryptography underpinning the sometimes lofty idealism of the Cypherpunk movement was developed in the 1970s within government intelligence agencies the NSA (USA) and GCHQ (UK).\n\n<b>Motivation</b>: in this post I will give additional commentary on the Bitcoin white paper, as well as definitions, and links to resources. I will quote the paper verbatim in the grey boxes, and highlight to define or further explain. On first reading the paper can seem sparse and obtuse, but with sufficient context and understanding I hope to demonstrate to you it's elegance, and momentous implications. The paper mainly describes the technical mechanisms underpinning the Bitcoin blockchain, but also touches on issues in banking, monetary policy, and incentive structures. The brilliance of the Bitcoin protocol is in the design of a system combining cryptographic techniques in a peer-to-peer network that has a concept of memory, with a self-regulating system of incentives.\n\n#### Links:\n* <a href=\"https://bitcoin.org/bitcoin.pdf\" target=\"_blank\">Bitcoin white paper</a>\n* <a href=\"https://www.activism.net/cypherpunk/manifesto.html\">Cypherpunk Manifesto</a>\n\n## Abstract\n---\n<blockquote style=\"background:#f5f5f5;\">\nA purely <a href=\"#fn1\">peer-to-peer</a> version of electronic cash would allow online\npayments to be sent directly from one party to another without going through a\nfinancial institution. <a href=\"#fn2\">Digital signatures</a> provide part of the solution, but the main\nbenefits are lost if a trusted third party is still required to prevent <a href=\"#fn3\">double-spending</a>.\nWe propose a solution to the double-spending problem using a peer-to-peer network.\nThe network timestamps transactions by <a href=\"#fn4\">hashing</a> them into an ongoing chain of\nhash-based proof-of-work, forming a record that cannot be changed without redoing\nthe proof-of-work. The longest chain not only serves as proof of the sequence of\nevents witnessed, but proof that it came from the largest pool of CPU power. As\nlong as a majority of CPU power is controlled by nodes that are not cooperating to\nattack the network, they'll generate the longest chain and outpace attackers. The\nnetwork itself requires minimal structure. Messages are broadcast on a <a href=\"#fn5\">best effort</a>\nbasis, and nodes can leave and rejoin the network at will, accepting the longest\nproof-of-work chain as proof of what happened while they were gone.\n</blockquote>\n\nBitcoin is introduced as a peer-to-peer electronic cash using digital signatures to trace transactions, which overcomes the double-spending problem without relying on a trusted third party. The double-spending problem is overcome using a hash-based proof-of-work system. Some of the main properties of the Bitcoin network are that:\n* double-spending is prevented with a peer-to-peer network,\n* there is no mint or other trusted parties,\n* participants can be pseudo-anonymous,\n* new coins are made from Hashcash style proof-of-work, and \n* the proof-of-work for new coin generation also powers the network to prevent double-spending.\n\nDon't worry if this doesn't make sense to you at this stage, I recommend getting familiar with the following cryptographic and networking concepts, and then re-reading the abstract. Note proof-of-work is not introduced here since since it is discussed at length later.\n\n<p id=\"fn1\"><b>Peer-to-peer</b>: a fundamental design feature of Bitcoin is that it is built as a peer-to-peer (P2P) network, as opposed to a client-server network. In a client-server architecture communication is usually to and from a central server providing resources. A P2P network is a distributed architecture, in which nodes are both conumers and suppliers of resources, removing the need for a centralised authority. In the case of Bitcoin a network designed for the transfer of value a centralised authority would be provided by a financial institution. The use of P2P networks first became widely popular with music sharing applications such as Napster, and then through file sharing with BitTorrent.\n\n<div style=\"margin-left: auto;margin-right: auto;text-align: justify;-ms-text-justify: distribute-all-lines;text-justify: distribute-all-lines;\">\n <a style=\"vertical-align:top; display:inline-block; *display:inline; zoom:1;\">\n <img src=\"https://steemitimages.com/DQmetns4LHAMmPDnCtXSzT7Ff9v3fFuYaucbai9TPPXCeJx/c2s.png\" style=\"display:block; margin:0 auto;\">\n <p style=\"display:block; width:100%; text-align:center; color:black\">client-to-server</p>\n </a>\n <a style=\"vertical-align:top; display:inline-block; *display:inline; zoom:1;\">\n <img src=\"https://steemitimages.com/DQmeEnnfQqyyP4iot7YuKvioqQjSTmS8dDCgV1x9ceAKmHd/p2p.png\" style=\"display:block; margin:0 auto;\">\n <p style=\"display:block; width:100%; text-align:center; color:black\">peer-to-peer</p>\n </a>\n</div>\n</p>\n<p id=\"fn4\"><b>Hashing</b>: cryptographic hash functions are mathematical functions that can take any data and turn it into a fixed length output hash, where the same input data will reliably give the same output hash, if the data is even slightly modified then the hash will completely change. A hash function is a one way function, meaning if <em>f</em> is the hashing function, calculating <em>f(x)</em> is easy and fast, but trying to obtain <em>x</em> again is hard and infeasible due to the computational complexity. Hash functions are used, in digital signatures, message authentication codes, manipulation detection, fingerprints, checksums (message integrity check), hash tables, password storage and much more.\n\nHashes are large numbers, usually written in hexadecimal. Bitcoin uses secure hash algorithm 2 (SHA-256), which returns a 256 bit hash string (represented as hexadecimal below), here is an example of sha256 hashing in python:\n\nIn [1]: import hashlib\n\nIn [2]: hashlib.sha256(b\"here is a bytestring to be hashed\").hexdigest() \nOut[2]: '7b02d50f844957522e4f1bb4514c0a76bd043eb87b290d43f21ca2508ea19e6b'\n\nIn [3]: hashlib.sha256(b\"here is another bytestring to be hashed\").hexdigest()\nOut[3]: '1dbb72fc530b143d450fe3709c6c35d193fa8e1f6110acfdac6f2769f8eec7ce'\n\n</p>\n\n<p id=\"fn2\"><b>Digital signatures</b>: a digital signature binds a person/entity to digital data, in a way that can be verified by a receiver or third party. This is analagous to signing a document by hand that binds the signatory to a message. In order to have a purely digital replacement for physical paper signatures, each user must be able to produce a message whose authenticity can be checked by anyone, but which could not have been produced by anyone else. In Bitcoin digital signatures provide a way to ensure that all transactions are only made by the rightful owners of that coin.\n\nDigital signatures are based on public key cryptography, a form of asymmetric cryptography. A public key algorithm such as RSA (Rivest–Shamir–Adleman) is commonly used, although Bitcoin and many cryptocurrencies use the more secure elliptic curve digital signature algorithm (ECDSA). In public key cryptography one can generate two keys that are mathematically linked, one private and one public. A digital signature is created by hashing a one-way hash of electronic data to be signed. The private key is then used to encrypt the hash. The encrypted hash along with extra information including the hashing algorithm is the digital signature. The hash is encrypted instead of the entire message since the hash is usually much shorter, saving time and computation.\n\n<div align=\"center\">\n <img src=\"https://steemitimages.com/DQmXe235tK6mruNcqWBJ3JsPTUFxERwqi5ZYqkjePTnwurR/digital_signatures.png\" alt=\"digital signatures\" style=\"max-width: 600px;\">\n</div>\n\nThe hash value is unique to the input data, and any change in input data will result in a different hash value. Given this property others can validate the integrity of the data using the signer's public key to decrypt the hash. If the hash decrypted with the public key matches a second computed hash of the same data, it proves that the data has not been altered since signing. If the two hashes are not equal it is either a problem of integrity or authentication, that is to say that either the data has been tampered with, or the signature was created with a private key that does not correspond to the public key. Digital signatures can be used with any kind of message to check the sender's identity and to validate the message was not tampered with.</p>\n\n<p id=\"fn3\"><b>Double-spending</b>: The double-spending problem is a potential flaw in a digital monetary system in which the same token can be replicated and spent more than once, thereby causing inflation and destroying trust in the system. Double-spending exists in cash based financial systems as money counterfeiting, but with digital data it is potentially much easier to replicate and distribute money. A central authority can be used to overcome this problem and validate all transactions, but it is harder in a distributed system like Bitcoin. Bitcoin is the first successful distributed system that overcomes the double-spending problem.</p>\n\n<p id=\"fn5\"><b>Best effort basis</b>: Best effort basis is an agreement that something will be attempted without any guarantee provided that it will succeed. In terms of a network best-effort delivery describes a network service in which the network does not provide any guarantee that data is delivered or that delivery meets any quality of service.</p>\n\n#### Further reading:\n* <a href=\"https://www.plagiarismtoday.com/2017/06/01/the-long-slow-decline-of-bittorrent/\" target=\"_blank\">The long slow decline of bittorent</a>\n* <a href=\"https://en.wikipedia.org/wiki/Cryptographic_hash_function\" target=\"_blank\">Cryptographic hash function wikipedia</a>\n* <a href=\"https://www.tutorialspoint.com/cryptography/cryptography_digital_signatures.htm\" target=\"_blank\">Digital Signatures tutorial</a>\n* <a href=\"http://groups.csail.mit.edu/mac/classes/6.805/student-papers/fall97-papers/fillingham-sig.html\" target=\"_blank\">A Comparison of Digital and Handwritten Signatures</a>\n* <a href=\"https://www.youtube.com/watch?v=NF1pwjL9-DE\" target=\"_blank\">Video explaining elliptic curve cryptography</a>\n\n## 1. Introduction\n---\n<blockquote style=\"background:#f5f5f5;\">\nCommerce on the Internet has come to rely almost exclusively on financial institutions serving as trusted third parties to process electronic payments. While the system works well enough for most transactions, it still suffers from the inherent weaknesses of the trust based model. Completely non-reversible transactions are not really possible, since financial institutions cannot avoid mediating disputes. The cost of mediation increases transaction costs, limiting the minimum practical transaction size and cutting off the possibility for small casual transactions, and there is a broader cost in the loss of ability to make non-reversible payments for non-reversible services. With the possibility of reversal, the need for trust spreads. Merchants must be wary of their customers, hassling them for more information than they would otherwise need. A certain percentage of fraud is accepted as unavoidable. These costs and payment uncertainties can be avoided in person by using physical currency, but no mechanism exists to make payments over a communications channel without a trusted party.\n\nWhat is needed is an electronic payment system based on cryptographic proof instead of trust, allowing any two willing parties to transact directly with each other without the need for a trusted third party. Transactions that are computationally impractical to reverse would protect sellers from fraud, and routine <a href=\"#fn6\">escrow mechanisms</a> could easily be implemented to protect buyers. In this paper, we propose a solution to the double-spending problem using a peer-to-peer distributed timestamp server to generate computational proof of the chronological order of transactions. The system is secure as long as honest nodes collectively control more CPU power than any cooperating group of attacker nodes.\n</blockquote>\nIt is interesting to note that since publication in 2008 the original use case presented of Bitcoin has changed, due to constraints on the number of transactions the network can process. Transactions are throttled by the size and frequency of blocks in the blockchain. The original intention of Bitcoin was to facilitate low value non-reversible transactions, with the idea that the cost is reduced since no third party is required to mediate disputes. However, as the network has grown and the number of transactions has increased the fees to use network have also increased. This increase in fees makes small value transactions uneconomical. Engineers are now working on so called 'layer 2' solutions to the scalability problem such as the lightning network that take transactions off-chain, thus reducing transaction fees and congestion on the Bitcoin network.\n\n \n<br><p id=\"fn6\"><b>Escrow mechanisms</b>: An escrow is a contractual arrangement in which a third party receives and disburses money or documents for the primary transacting parties, with the disbursement dependent on conditions agreed to by the transacting parties, or an account established by a broker for holding funds on behalf of the broker's principal or some other person until the consummation or termination of a transaction. An escrow mechanism can be used for example to release funds once an item bought online has been received.\n</p>\n\n#### Further reading:\n* <a href=\"https://lightning.network/\" target=\"_blank\">Lightning network website</a>\n* <a href=\"https://en.wikipedia.org/wiki/Lightning_Network\" target=\"_blank\">Lightning network wiki</a>\n\n\n## 2. Transactions\n---\n<blockquote style=\"background:#f5f5f5;\">\nWe define an electronic coin as a chain of digital signatures. Each owner transfers the coin to the next by digitally signing a hash of the previous transaction and the public key of the next owner and adding these to the end of the coin. A payee can verify the signatures to verify the chain of ownership.\n<div align=\"center\">\n <img src=\"https://steemitimages.com/DQmV1fvCbeAuXPc7N5HM2BAyzfvhDDVEEvA4GauA6qrJHFk/transactions.png\" alt=\"transactions\" style=\"max-width:200px; padding-right:80px;\">\n</div>\nThe problem of course is the payee can't verify that one of the owners did not double-spend the coin. A common solution is to introduce a trusted central authority, or mint, that checks every transaction for double spending. After each transaction, the coin must be returned to the mint to issue a new coin, and only coins issued directly from the mint are trusted not to be double-spent. The problem with this solution is that the fate of the entire money system depends on the company running the mint, with every transaction having to go through them, just like a bank.\n<br><br>We need a way for the payee to know that the previous owners did not sign any earlier transactions. For our purposes, the earliest transaction is the one that counts, so we don't care about later attempts to double-spend. The only way to confirm the absence of a transaction is to be aware of all transactions. In the mint based model, the mint was aware of all transactions and decided which arrived first. To accomplish this without a trusted party, transactions must be publicly announced <a href=\"#ref1\">[1]</a>, and we need a system for participants to agree on a single history of the order in which they were received. The payee needs proof that at the time of each transaction, the majority of nodes agreed it was the first received.\n</blockquote>\nThis section describes how Bitcoin are moved through the system using a sequence of transfers made with digital signatures. The history of each and every Bitcoin transaction leads back to the point where the bitcoins were first produced. Be aware that the transaction mechanism shown here is not the same as the concept of a blockchain, which is discussed later, but rather how money is traced and transferred through the network.\n\nThe important part here is to understand the figure, showing how at each stage the owner is a person/entity holding the private key that gives them the ability to spend/transfer that money. When a transaction is broadcast other users can validate based on the public key of the signer, to ensure they have sufficient funds to make the transaction. This is facilitated by the asymmetry of the public-private key pair, whereby anyone can decrypt the signature and verify the transaction but only the owner can encrypt and sign to create another transaction. Although this is a useful way to keep track of ownership, there is nothing to stop somebody spending their coins more than once, i.e. the double-spending problem. \n\n## 3. Timestamp Server\n---\n<blockquote style=\"background:#f5f5f5;\">\nThe solution we propose begins with a timestamp server. A timestamp server works by taking a hash of a block of items to be timestamped and widely publishing the hash, such as in a newspaper or <a href=\"#fn7\">Usenet post</a> <a href=\"#ref2\">[2,</a> <a href=\"#ref3\"> 3,</a> <a href=\"#ref4\"> 4,</a> <a href=\"#ref5\"> 5]</a>. The timestamp proves that the data must have existed at the time, obviously, in order to get into the hash. Each timestamp includes the previous timestamp in its hash, forming a chain, with each additional timestamp reinforcing the ones before it.\n<div align=\"center\">\n <img src=\"https://steemitimages.com/DQmTza1XMZNVLyTxCk366sD1xqQZos4n2bQsmsTtzKBi31t/timestamp_server.png\" alt=\"transactions\" style=\"max-width:500px; padding-right:80px;\">\n</div>\n</blockquote>\nAt this point Satoshi introduces the concept of a chain of timestamped blocks, also known as the blockchain. The first work on a cryptographically secured chain of blocks was described in 1991 by Stuart Haber and W. Scott Stornetta for time stamping digital documents. The idea here is to group transactions into blocks to verify that a transaction existed at a certain time, in this way we can overcome the double-spending problem by knowing whether coins have already been spent at a certain time, since these blocks are broadcast to the network, and the most recent block on the longest chain accepted as the current state of the ledger. When you sign a transaction and broadcast to the network, it is not immediately assimilated into the blockchain. But depending on the transaction fee and load on the network it will be compiled into a block. As more blocks are added to the chain the transaction becomes ossified in the history, since it would require increasing proof-of-work to go back and change the record.\n \n<p id=\"fn7\"><b>Usenet</b>: An early peer-to-peer architecture mentioned in the Bitcoin paper is USENET, a distributed messaging system developed in 1979. Users read and post messages (called articles or posts, and collectively termed news) to one or more categories, known as newsgroups.</p>\n\n#### Further reading:\n* <a href=\"https://en.wikipedia.org/wiki/Blockchain\" target=\"_blank\">Blockchain wiki</a>\n* <a href=\"https://link.springer.com/article/10.1007%2FBF00196791\" target=\"_blank\">How to time-stamp a digital document</a>\n\n## 4. Proof-of-Work\n---\n<blockquote style=\"background:#f5f5f5;\">\nTo implement a distributed timestamp server on a peer-to-peer basis, we will need to use a proof-of-work system similar to Adam Back's <a href=\"#fn7\">Hashcash</a> <a href=\"#ref6\">[6]</a>, rather than newspaper or Usenet posts. The proof-of-work involves scanning for a value that when hashed, such as with SHA-256, the hash begins with a number of zero bits. The average work required is exponential in the number of zero bits required and can be verified by executing a single hash.\n<br><br>For our timestamp network, we implement the proof-of-work by incrementing a nonce in the block until a value is found that gives the block's hash the required zero bits. Once the CPU effort has been expended to make it satisfy the proof-of-work, the block cannot be changed without redoing the work. As later blocks are chained after it, the work to change the block would include redoing all the blocks after it.\n\n<div align=\"center\">\n <img src=\"https://steemitimages.com/DQmVsXjFwceGQ3qKpjNWbUgvRimgMuVPgQ4nyAWr1KVUor9/proof_of_work.png\" style=\"max-width:500px; padding-right:80px;\">\n</div>\n\nThe proof-of-work also solves the problem of determining representation in majority decision making. If the majority were based on one-IP-address-one-vote, it could be subverted by anyone able to allocate many IPs. Proof-of-work is essentially one-CPU-one-vote. The majority decision is represented by the longest chain, which has the greatest proof-of-work effort invested in it. If a majority of CPU power is controlled by honest nodes, the honest chain will grow the fastest and outpace any competing chains. To modify a past block, an attacker would have to redo the proof-of-work of the block and all blocks after it and then catch up with and surpass the work of the honest nodes. We will show later that the probability of a slower attacker catching up diminishes exponentially as subsequent blocks are added.\n<br><br>To compensate for increasing hardware speed and varying interest in running nodes over time, the proof-of-work difficulty is determined by a moving average targeting an average number of blocks per hour. If they're generated too fast, the difficulty increases.\n</blockquote>\nThe proof-of-work system is a kind of puzzle that miners on the network compete to solve first. Miners will first combine transactions into a block according to the rules of the network. They use the block header and a nonce value to to generate a hash, if the hash is less than a target value they win. This is done by randomly or pseudo-randomly changing a nonce value in the block until a hash is achieved with sufficient number of leading zeros. The more zeroes the more rare the hash is. A good hash' outcome is not predictable, and so you have to try a lot of times to find a good nonce. The amount of zeroes are based on how difficult it is supposed to be to find a block. In Bitcoin it adjusts to have a new block every 10 minutes (on average, given the rate at which previous blocks are found).\n\nSo for example the first hash ever found was the following, note the previous block is all zeros since there was no previous block!\n\n\nBlock 0\nHash 000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f\nPrevious Block 0000000000000000000000000000000000000000000000000000000000000000\n\n\nAs you can see by block 100000, as more miners have joined the network the hashing power has increased, and the number of leading zeros in the hash to be found is also increased. Adjusting the number of leading zeros is how the system regulates the blocktime. \n\n\nBlock 100000\nHash 000000000003ba27aa200b1cecaad478d2b00432346c3f1f3986da1afd33e506\nPrevious Block 000000000002d01c1fccc21636b607dfd930d31d01c3a62104612a1719011250\n\n\nAgain by block 500000 the difficult has increased again (more leading zeros).\n\n\nBlock 500000\nHash 00000000000000000024fb37364cbf81fd49cc2d51c09c75c35433c3a1945d04\nPrevious Block 0000000000000000007962066dcd6675830883516bcf40047d42740a85eb2919\n\n\nWhen a miner finds a hash with enough leading zeros, you can think of it as them winning that competition. They can then propagate the block to the network and mint themselves some Bitocin.\n\nThis distributed proof-of-work system is how Bitcoin obtains consensus. In order to achieve this the system has to overcome the Byzantine General's Problem, a classic problem faced by any distributed computer system network. The Byzantine General's problem is explained through a scenario in which multiple divisions of an army are laying seige to a city. Each division has a general, that can communicate to other generals via a messenger. A majority have to agree to attack or to defend, but the difficulty arises since some of the generals or messengers may be untrustworthy.\n\nA networked system is Byzantine Fault Tolerant if the system is dependable, where components may fail and there is imperfect information on whether a component is failed. So if one or more generals decide to go rogue and ignore the other generals then so long as they are not a majority the system will tolerate it. The bitcoin network works in parallel to generate a chain of Hashcash style proof-of-work. The proof-of-work chain is the key to overcome Byzantine failures and to reach a coherent global view of the system state. When a miner has done sufficient work to obtain a hash they are incentivised to obey the rules of the network and generate a valid block and claim their reward in Bitcoins. This overcomes the Byzantine General's problem since it becomes very expensive to become a bad actor and attack the network. It also makes it extremely computationally expensive to rewrite historical transactions on the network since the proof-of-work has to be done again for all blocks since the transaction.\n\nProof-of-work is not the only mechanism for achieving a consensus, other approaches such as proof-of-stake, and delegated proof-of-stake are being used. These are advantageous in their lower energy consumption. Attempts have also been made by cryptocurrencies like Primecoin which requires clients to find unknown prime numbers of certain types, which can have useful side-applications.\n\n<p id=\"fn8\"><b>Hashcash</b>: is a proof-of-work system used to limit email spam and denial-of-service attacks. The idea was to require that some computational work be done in order to send an e-mail, the receiver can then verify that work has been done. This would make it expensive to send spam e-mails to thousands of addresses.</p>\n\n#### Further reading:\n* <a href=\"https://www.youtube.com/watch?v=r0pcpGduaJw\" target=\"_blank\">Jackson Palmer (Dogecoin) describes consensus mechanisms</a>\n* <a href=\"https://en.wikipedia.org/wiki/Proof-of-work_system\" target=\"_blank\">Proof-of-work wiki</a>\n\n## 5. Network\n---\n<blockquote style=\"background:#f5f5f5;\">\nThe steps to run the network are as follows:\n<ol>\n <li>New transactions are broadcast to all nodes.</li>\n <li>Each node collects new transactions into a block.</li>\n <li>Each node works on finding a difficult proof-of-work for its block.</li>\n <li>When a node finds a proof-of-work, it broadcasts the block to all nodes.</li>\n <li>Nodes accept the block only if all transactions in it are valid and not already spent.</li>\n <li>Nodes express their acceptance of the block by working on creating the next block in the chain, using the hash of the accepted block as the previous hash.</li>\n</ol>\nNodes always consider the longest chain to be the correct one and will keep working on extending it. If two nodes broadcast different versions of the next block simultaneously, some nodes may receive one or the other first. In that case, they work on the first one they received, but save the other branch in case it becomes longer. The tie will be broken when the next proof-of-work is found and one branch becomes longer; the nodes that were working on the other branch will then switch to the longer one.\n<br><br>New transaction broadcasts do not necessarily need to reach all nodes. As long as they reach many nodes, they will get into a block before long. Block broadcasts are also tolerant of dropped messages. If a node does not receive a block, it will request it when it receives the next block and realizes it missed one.\n</blockquote>\n\nFor a bit of clarity any computer that connects to the Bitcoin network is called a node. Nodes that fully verify all of the rules of Bitcoin are called full nodes. Full nodes in the Bitcoin network have a complete copy of the blockchain and are able to verify all transactions since the genesis block at the start of the network. Basically, the miner works on transactions by coming up with the best combination to store that information. Miners spend about 10 minutes working on a problem, but nodes keep that result forever after in the database and verify it with others. Miners don't need to know about prior blocks (except for the prior one) with very few exceptions.\n\n#### Further reading:\n* <a href=\"https://en.bitcoin.it/wiki/Full_node\" target=\"_blank\">Bitcoin full node wiki</a>\n\n## 6. Incentive\n---\n<blockquote style=\"background:#f5f5f5;\">\nBy convention, the first transaction in a block is a special transaction that starts a new coin owned by the creator of the block. This adds an incentive for nodes to support the network, and provides a way to initially distribute coins into circulation, since there is no central authority to issue them. The steady addition of a constant of amount of new coins is analogous to gold miners expending resources to add gold to circulation. In our case, it is CPU time and electricity that is expended.\n<br><br>The incentive can also be funded with transaction fees. If the output value of a transaction is less than its input value, the difference is a transaction fee that is added to the incentive value of the block containing the transaction. Once a predetermined number of coins have entered circulation, the incentive can transition entirely to transaction fees and be completely inflation free.\n<br><br>The incentive may help encourage nodes to stay honest. If a greedy attacker is able to assemble more CPU power than all the honest nodes, he would have to choose between using it to defraud people by stealing back his payments, or using it to generate new coins. He ought to find it more profitable to play by the rules, such rules that favour him with more new coins than everyone else combined, than to undermine the system and the validity of his own wealth.\n</blockquote>\n\nThe total number of Bitcoins that can be mined is slightly less than 21 million, with the rate at which Bitcoins can be mined reducing over time, in a halving event approximately every 4 years, from 50 BTC per block, to 25 BTC, to 12.5 BTC etc. This leads to a deflationary currency, since the rate of increase in supply is reducing over time and will reach a stable number of coins around the year 2140. When miners can no longer mint new Bitcoins the network will sustain only on transaction fees alone.\n\n#### Further reading:\n* <a href=\"https://en.bitcoin.it/wiki/Controlled_supply\" target=\"_blank\">Bitcoin supply wiki</a>\n* <a href=\"https://blockchain.info/charts/total-bitcoins?timespan=all\" target=\"_blank\">Graph of Bitcoin's mined</a>\n\n## 7. Reclaiming Disk Space\n---\n<blockquote style=\"background:#f5f5f5;\">\nOnce the latest transaction in a coin is buried under enough blocks, the spent transactions before it can be discarded to save disk space. To facilitate this without breaking the block's hash, transactions are hashed in a <a href=\"#fn9\">Merkle Tree</a> <a href=\"#ref7\">[7,</a> <a href=\"#ref2\"> 2,</a> <a href=\"#ref5\"> 5]</a>, with only the root included in the block's hash. Old blocks can then be compacted by stubbing off branches of the tree. The interior hashes do not need to be stored.\n<div align=\"center\">\n <img src=\"https://steemitimages.com/DQmP3871pXHsUe5sR1WLeYmNN96CShLLMGt4qnyn2QsfFax/merkle.png\" style=\"max-width:500px; padding-right:80px;\">\n</div>\nA block header with no transactions would be about 80 bytes. If we suppose blocks are generated every 10 minutes, 80 bytes * 6 * 24 * 365 = 4.2MB per year. With computer systems typically selling with 2GB of RAM as of 2008, and Moore's Law predicting current growth of 1.2GB per year, storage should not be a problem even if the block headers must be kept in memory.\n</blockquote>\n<p id=\"fn9\"><b>Merkle Tree</b>: a Merkle tree is a hash-based data structure that is a generalisation of the hash list. It is a tree structure in which each leaf node is a hash of a block of data, and each non-leaf node is a hash of its children. Typically, Merkle trees have a branching factor of 2, meaning that each node has up to 2 children. Hash trees can be used to verify any kind of data stored, handled and transferred in and between computers. They can help ensure that data blocks received from other peers in a peer-to-peer network are received undamaged and unaltered, and even to check that the other peers do not lie and send fake blocks.\n</p>\n\n#### Further reading:\n* <a href=\"https://en.wikipedia.org/wiki/Merkle_tree\" target=\"_blank\">Merkle tree wiki</a>\n\n\n## 8. Simplified Payment Verification\n---\n<blockquote style=\"background:#f5f5f5;\">\nOnce the latest transaction in a coin is buried under enough blocks, the spent transactions before it can be discarded to save disk space. To facilitate this without breaking the block's hash, transactions are hashed in a Merkle Tree <a href=\"#ref7\">[7,</a> <a href=\"#ref2\"> 2,</a> <a href=\"#ref5\"> 5]</a>, with only the root included in the block's hash. Old blocks can then be compacted by stubbing off branches of the tree. The interior hashes do not need to be stored.\n<div align=\"center\">\n <img src=\"https://steemitimages.com/DQmWLopYBYqrYxGRJoby6Sib29RW2WbW6G14CUMjRDQgXV8/spv.png\" style=\"width:80%\">\n</div>\nAs such, the verification is reliable as long as honest nodes control the network, but is more vulnerable if the network is overpowered by an attacker. While network nodes can verify transactions for themselves, the simplified method can be fooled by an attacker's fabricated transactions for as long as the attacker can continue to overpower the network. One strategy to protect against this would be to accept alerts from network nodes when they detect an invalid block, prompting the user's software to download the full block and alerted transactions to confirm the inconsistency. Businesses that receive frequent payments will probably still want to run their own nodes for more independent security and quicker verification.\n\n<br><br>A block header with no transactions would be about 80 bytes. If we suppose blocks are generated every 10 minutes, 80 bytes * 6 * 24 * 365 = 4.2MB per year. With computer systems typically selling with 2GB of RAM as of 2008, and Moore's Law predicting current growth of 1.2GB per year, storage should not be a problem even if the block headers must be kept in memory.\n</blockquote>\n\nSimplified payment verification is a method for verifying if particular transactions are included in a block without downloading the entire block. The method is used by some lightweight Bitcoin clients. The simplified verification verification client only needs download the block headers, which are much smaller than the full blocks. To verify that a transaction is in a block, a simplified verification client requests a proof of inclusion, in the form of a Merkle branch.\n\n#### Further reading:\n* <a href=\"https://en.bitcoin.it/wiki/Thin_Client_Security\" target=\"_blank\">Thin Client Security</a>\n\n## 9. Combining and Splitting Value\n---\n<blockquote style=\"background:#f5f5f5;\">\nAlthough it would be possible to handle coins individually, it would be unwieldy to make a separate transaction for every cent in a transfer. To allow value to be split and combined, transactions contain multiple inputs and outputs. Normally there will be either a single input from a larger previous transaction or multiple inputs combining smaller amounts, and at most two outputs: one for the payment, and one returning the change, if any, back to the sender.\n<div align=\"center\">\n <img src=\"https://steemitimages.com/DQmbgDQ82GCAo5gPFvmZFBXv7rgqo2YiJLX59yqrJjzZQqi/utxo.png\" style=\"max-width:300px; padding-right:80px;\">\n</div>\nIt should be noted that fan-out, where a transaction depends on several transactions, and those transactions depend on many more, is not a problem here. There is never the need to extract a complete standalone copy of a transaction's history.\n</blockquote>\n\n#### Further reading:\n* <a href=\"https://pascalpares.gitbooks.io/implementation-of-the-bitcoin-system/content/1-transaction-4-structure.html\" target=\"_blank\">Information on transaction structure</a>\n* <a href=\"https://medium.com/@aalim.khan/bitcoin-transactions-scripts-and-digital-signatures-506688e1630a\" target=\"_blank\">Bitcoin transactions, scripts and digital signatures</a>\n\n## 10. Privacy\n---\n<blockquote style=\"background:#f5f5f5;\">\nThe traditional banking model achieves a level of privacy by limiting access to information to the parties involved and the trusted third party. The necessity to announce all transactions publicly precludes this method, but privacy can still be maintained by breaking the flow of information in another place: by keeping public keys anonymous. The public can see that someone is sending an amount to someone else, but without information linking the transaction to anyone. This is similar to the level of information released by stock exchanges, where the time and size of individual trades, the \"tape\", is made public, but without telling who the parties were.\n<div align=\"center\">\n <img src=\"https://steemitimages.com/DQmTmxcTK1zUHvRLJGJaTfSM37HAHykhGYUHU7jLnGrYxCD/privacy.png\" style=\"max-width:600px; padding-right:80px;\">\n</div>\nAs an additional firewall, a new key pair should be used for each transaction to keep them from being linked to a common owner. Some linking is still unavoidable with multi-input transactions, which necessarily reveal that their inputs were owned by the same owner. The risk is that if the owner of a key is revealed, linking could reveal other transactions that belonged to the same owner.\n</blockquote>\nBitcoin is often perceived as an anonymous payment network, but in actuality it is very transparent since all transactions are recorded. By combining transactions and through analysing groups of transactions the anonymity of Bitcoin can be compromised. Other cryptocurrencies such as Monero, and Zcash attempt to provide a more anonymous payment method, but at the expense of computation.\n\n#### Further reading:\n* <a href=\"https://bitcoin.org/en/protect-your-privacy\" target=\"_blank\">Bitcoin privacy</a>\n\n## 11. Calculations\n---\n<blockquote style=\"background:#f5f5f5;\">\nWe consider the scenario of an attacker trying to generate an alternate chain faster than the honest chain. Even if this is accomplished, it does not throw the system open to arbitrary changes, such as creating value out of thin air or taking money that never belonged to the attacker. Nodes are not going to accept an invalid transaction as payment, and honest nodes will never accept a block containing them. An attacker can only try to change one of his own transactions to take back money he recently spent.\n\n<br><br>The race between the honest chain and an attacker chain can be characterized as a Binomial Random Walk. The success event is the honest chain being extended by one block, increasing its lead by +1, and the failure event is the attacker's chain being extended by one block, reducing the gap by -1. The probability of an attacker catching up from a given deficit is analogous to a Gambler's Ruin problem. Suppose a gambler with unlimited credit starts at a deficit and plays potentially an infinite number of trials to try to reach breakeven. We can calculate the probability he ever reaches breakeven, or that an attacker ever catches up with the honest chain, as follows <a href=\"#ref8\">[8]</a>: \n<br>\n<br> p = probability an honest node finds the next block\n<br> q = probability the attacker finds the next block\n<br> q<sub>z</sub> = probability the attacker will ever catch up from z blocks behind\n<div align=\"center\">\n <img src=\"https://steemitimages.com/DQmcwZwezcs4nK5rLcimQX3fLR3z3AeWXrDDoBVospw3q7T/equation1.png\" style=\"max-width:300px; padding-right:80px;\">\n</div>\nGiven our assumption that p > q, the probability drops exponentially as the number of blocks the attacker has to catch up with increases. With the odds against him, if he doesn't make a lucky lunge forward early on, his chances become vanishingly small as he falls further behind.\n\n<br><br>We now consider how long the recipient of a new transaction needs to wait before being sufficiently certain the sender can't change the transaction. We assume the sender is an attacker who wants to make the recipient believe he paid him for a while, then switch it to pay back to himself after some time has passed. The receiver will be alerted when that happens, but the sender hopes it will be too late.\n\n<br><br>The receiver generates a new key pair and gives the public key to the sender shortly before signing. This prevents the sender from preparing a chain of blocks ahead of time by working on it continuously until he is lucky enough to get far enough ahead, then executing the transaction at that moment. Once the transaction is sent, the dishonest sender starts working in secret on a parallel chain containing an alternate version of his transaction.\n\n<br><br>The recipient waits until the transaction has been added to a block and z blocks have been linked after it. He doesn't know the exact amount of progress the attacker has made, but assuming the honest blocks took the average expected time per block, the attacker's potential progress will be a Poisson distribution with expected value:\n<div align=\"center\">\n <img src=\"https://steemitimages.com/DQmdsRSkrU8Hs7ZXW3CWDwUT3pPRENXzRjy1SCVrCQ414S2/equation2.png\" style=\"max-width:400px; padding-right:80px;\">\n</div>\n\nTo get the probability the attacker could still catch up now, we multiply the Poisson density for each amount of progress he could have made by the probability he could catch up from that point:\n\n<div align=\"center\">\n <img src=\"https://steemitimages.com/DQmXaTaRpNvEvyvV8aUPhvv4hncP1sfwuXBehdbZscjpb8Y/equation3.png\" style=\"max-width:400px; padding-right:80px;\">\n</div>\n\nRearranging to avoid summing the infinite tail of the distribution...\n\n<div align=\"center\">\n <img src=\"https://steemitimages.com/DQmWdLjgjP14o55xKJ7SjY2GhLiJoUUXtVLmoPDeSoX8Ubj/equation4.png\" style=\"max-width:400px; padding-right:80px;\">\n</div>\n\nConverting to C code...\n\n\ninclude math.h\ndouble AttackerSuccessProbability(double q, int z)\n{\n double p = 1.0 - q;\n double lambda = z * (q / p);\n double sum = 1.0;\n int i, k;\n for (k = 0; k <= z; k++)\n {\n double poisson = exp(-lambda);\n for (i = 1; i <= k; i++)\n poisson *= lambda / i;\n sum -= poisson * (1 - pow(q / p, z - k));\n }\n return sum;\n}\n\nRunning some results, we can see the probability drop off exponentially with z.\n\n\nq=0.1 \nz=0 P=1.0000000\nz=1 P=0.2045873\nz=2 P=0.0509779\nz=3 P=0.0131722\nz=4 P=0.0034552\nz=5 P=0.0009137\nz=6 P=0.0002428\nz=7 P=0.0000647\nz=8 P=0.0000173\nz=9 P=0.0000046\nz=10 P=0.0000012\n\nq=0.3 \nz=0 P=1.0000000\nz=5 P=0.1773523\nz=10 P=0.0416605\nz=15 P=0.0101008\nz=20 P=0.0024804\nz=25 P=0.0006132\nz=30 P=0.0001522\nz=35 P=0.0000379\nz=40 P=0.0000095\nz=45 P=0.0000024\nz=50 P=0.0000006\n\n\nSolving for P less than 0.1%...\n\n\nP less than 0.001\nq=0.10 z=5\nq=0.15 z=8\nq=0.20 z=11\nq=0.25 z=15\nq=0.30 z=24\nq=0.35 z=41\nq=0.40 z=89\nq=0.45 z=340\n\n\n</blockquote>\n\n#### Further reading:\n* <a href=\"https://en.bitcoin.it/wiki/Weaknesses\" target=\"_blank\">Bitcoin weaknesses</a>\n\n## 12. Conclusion\n---\n<blockquote style=\"background:#f5f5f5;\">\nWe have proposed a system for electronic transactions without relying on trust. We started with the usual framework of coins made from digital signatures, which provides strong control of ownership, but is incomplete without a way to prevent double-spending. To solve this, we proposed a peer-to-peer network using proof-of-work to record a public history of transactions that quickly becomes computationally impractical for an attacker to change if honest nodes control a majority of CPU power. The network is robust in its unstructured simplicity. Nodes work all at once with little coordination. They do not need to be identified, since messages are not routed to any particular place and only need to be delivered on a best effort basis. Nodes can leave and rejoin the network at will, accepting the proof-of-work chain as proof of what happened while they were gone. They vote with their CPU power, expressing their acceptance of valid blocks by working on extending them and rejecting invalid blocks by refusing to work on them. Any needed rules and incentives can be enforced with this consensus mechanism.\n</blockquote>\nEt voila! This paper did not cause much of a stir on release, but Satoshi worked to build a minimum implementation. At a couple of points in its early history the Bitcoin project was almost completely abandoned. However, over time a core team of devoted developers emerged and the Bitcoin protocol and ecosystem has flourished since, opening a pandora's box of innovation in distributed transfer of value over the internet. That is not to say that it has not had its fair share of challenges and drama, but this remarkable peer-to-peer electronic cash is still going strong!\n\n#### Further reading:\n* <a href=\"https://www.youtube.com/watch?v=DjYbsq3FXfM\" target=\"_blank\">Visualisation of Bitcoin development on github</a>\n\n## References\n---\n<blockquote style=\"background:#f5f5f5;\">\n<p id=\"ref1\">\n[1] W. Dai, \"<a href=\"http://www.weidai.com/bmoney.txt\" target=\"_blank\">b-money</a>,\" http://www.weidai.com/bmoney.txt, 1998.\n</p>\n<p id=\"ref2\">\n[2] H. Massias, X.S. Avila, and J.-J. Quisquater, \"<a href=\"http://nakamotoinstitute.org/literature/secure-timestamping-service/\" target=\"_blank\">Design of a secure timestamping service with minimal trust requirements,</a>\" In 20th Symposium on Information Theory in the Benelux, May 1999.\n</p>\n<p id=\"ref3\">\n[3] S. Haber, W.S. Stornetta, \"<a href=\"https://link.springer.com/article/10.1007/BF00196791\" target=\"_blank\">How to time-stamp a digital document,</a>.\" In Journal of Cryptology, vol 3, no2, pages 99-111, 1991.\n</p>\n<p id=\"ref4\">\n[4] D. Bayer, S. Haber, W.S. Stornetta, \"<a href=\"https://link.springer.com/chapter/10.1007/978-1-4613-9323-8_24\" target=\"_blank\">Improving the efficiency and reliability of digital time-stamping,</a>\" In Sequences II: Methods in Communication, Security and Computer Science, pages 329-334, 1993.\n</p>\n<p id=\"ref5\">\n[5] S. Haber, W.S. Stornetta, \"<a href=\"http://nakamotoinstitute.org/static/docs/secure-names-bit-strings.pdf\" target=\"_blank\">Secure names for bit-strings,</a>\" In Proceedings of the 4th ACM Conference on Computer and Communications Security, pages 28-35, April 1997.\n</p>\n<p id=\"ref5\">\n[6] A. Back, \"<a href=\"http://www.hashcash.org/papers/hashcash.pdf\" target=\"_blank\">Hashcash - a denial of service counter-measure,</a>\" http://www.hashcash.org/papers/hashcash.pdf, 2002.\n</p>\n<p id=\"ref5\">\n[7] R.C. Merkle, \"<a href=\"http://ieeexplore.ieee.org/document/6233691\" target=\"_blank\">Protocols for public key cryptosystems,</a>\" In Proc. 1980 Symposium on Security and\nPrivacy, IEEE Computer Society, pages 122-133, April 1980.\n</p>\n<p id=\"ref5\">\n[8] W. Feller, \"<a href=\"https://www.wiley.com/en-us/An+Introduction+to+Probability+Theory+and+Its+Applications%2C+Volume+2%2C+2nd+Edition-p-9780471257097\" target=\"_blank\">An introduction to probability theory and its applications,</a>\" 1957.\n</p>\n</blockquote>\nIt is interesting to note the pioneering Nick Szabo's work on systems such as bit gold is not referenced here ;-)",
"json_metadata": "{\"tags\":[\"bitcoin\",\"cryptocurrency\",\"blog\",\"writing\",\"technology\"],\"image\":[\"https://steemitimages.com/DQmetns4LHAMmPDnCtXSzT7Ff9v3fFuYaucbai9TPPXCeJx/c2s.png\",\"https://steemitimages.com/DQmeEnnfQqyyP4iot7YuKvioqQjSTmS8dDCgV1x9ceAKmHd/p2p.png\",\"https://steemitimages.com/DQmXe235tK6mruNcqWBJ3JsPTUFxERwqi5ZYqkjePTnwurR/digital_signatures.png\",\"https://steemitimages.com/DQmV1fvCbeAuXPc7N5HM2BAyzfvhDDVEEvA4GauA6qrJHFk/transactions.png\",\"https://steemitimages.com/DQmTza1XMZNVLyTxCk366sD1xqQZos4n2bQsmsTtzKBi31t/timestamp_server.png\",\"https://steemitimages.com/DQmVsXjFwceGQ3qKpjNWbUgvRimgMuVPgQ4nyAWr1KVUor9/proof_of_work.png\",\"https://steemitimages.com/DQmP3871pXHsUe5sR1WLeYmNN96CShLLMGt4qnyn2QsfFax/merkle.png\",\"https://steemitimages.com/DQmWLopYBYqrYxGRJoby6Sib29RW2WbW6G14CUMjRDQgXV8/spv.png\",\"https://steemitimages.com/DQmbgDQ82GCAo5gPFvmZFBXv7rgqo2YiJLX59yqrJjzZQqi/utxo.png\",\"https://steemitimages.com/DQmTmxcTK1zUHvRLJGJaTfSM37HAHykhGYUHU7jLnGrYxCD/privacy.png\",\"https://steemitimages.com/DQmcwZwezcs4nK5rLcimQX3fLR3z3AeWXrDDoBVospw3q7T/equation1.png\",\"https://steemitimages.com/DQmdsRSkrU8Hs7ZXW3CWDwUT3pPRENXzRjy1SCVrCQ414S2/equation2.png\",\"https://steemitimages.com/DQmXaTaRpNvEvyvV8aUPhvv4hncP1sfwuXBehdbZscjpb8Y/equation3.png\",\"https://steemitimages.com/DQmWdLjgjP14o55xKJ7SjY2GhLiJoUUXtVLmoPDeSoX8Ubj/equation4.png\"],\"links\":[\"https://bitcoin.org/en/\",\"https://bitcoin.org/bitcoin.pdf\",\"https://www.activism.net/cypherpunk/manifesto.html\",\"#fn1\",\"#fn2\",\"#fn3\",\"#fn4\",\"#fn5\",\"https://www.plagiarismtoday.com/2017/06/01/the-long-slow-decline-of-bittorrent/\",\"https://en.wikipedia.org/wiki/Cryptographic_hash_function\",\"https://www.tutorialspoint.com/cryptography/cryptography_digital_signatures.htm\",\"http://groups.csail.mit.edu/mac/classes/6.805/student-papers/fall97-papers/fillingham-sig.html\",\"https://www.youtube.com/watch?v=NF1pwjL9-DE\",\"#fn6\",\"https://lightning.network/\",\"https://en.wikipedia.org/wiki/Lightning_Network\",\"#ref1\",\"#fn7\",\"#ref2\",\"#ref3\",\"#ref4\",\"#ref5\",\"https://en.wikipedia.org/wiki/Blockchain\",\"https://link.springer.com/article/10.1007%2FBF00196791\",\"#ref6\",\"https://www.youtube.com/watch?v=r0pcpGduaJw\",\"https://en.wikipedia.org/wiki/Proof-of-work_system\",\"https://en.bitcoin.it/wiki/Full_node\",\"https://en.bitcoin.it/wiki/Controlled_supply\",\"https://blockchain.info/charts/total-bitcoins?timespan=all\",\"#fn9\",\"#ref7\",\"https://en.wikipedia.org/wiki/Merkle_tree\",\"https://en.bitcoin.it/wiki/Thin_Client_Security\",\"https://pascalpares.gitbooks.io/implementation-of-the-bitcoin-system/content/1-transaction-4-structure.html\",\"https://medium.com/@aalim.khan/bitcoin-transactions-scripts-and-digital-signatures-506688e1630a\",\"https://bitcoin.org/en/protect-your-privacy\",\"#ref8\",\"https://en.bitcoin.it/wiki/Weaknesses\",\"https://www.youtube.com/watch?v=DjYbsq3FXfM\",\"http://www.weidai.com/bmoney.txt\",\"http://nakamotoinstitute.org/literature/secure-timestamping-service/\",\"https://link.springer.com/article/10.1007/BF00196791\",\"https://link.springer.com/chapter/10.1007/978-1-4613-9323-8_24\",\"http://nakamotoinstitute.org/static/docs/secure-names-bit-strings.pdf\",\"http://www.hashcash.org/papers/hashcash.pdf\",\"http://ieeexplore.ieee.org/document/6233691\",\"https://www.wiley.com/en-us/An+Introduction+to+Probability+Theory+and+Its+Applications%2C+Volume+2%2C+2nd+Edition-p-9780471257097\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}theblockcafeupvoted (100.00%) @sweetwilliam / re-theblockcafe-the-block-cafe-20180305t184640459z2018/04/03 14:26:57
theblockcafeupvoted (100.00%) @sweetwilliam / re-theblockcafe-the-block-cafe-20180305t184640459z
2018/04/03 14:26:57
| voter | theblockcafe |
| author | sweetwilliam |
| permlink | re-theblockcafe-the-block-cafe-20180305t184640459z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #21245302/Trx 18662e6aa322eb9445303823861c461c3df77678 |
View Raw JSON Data
{
"trx_id": "18662e6aa322eb9445303823861c461c3df77678",
"block": 21245302,
"trx_in_block": 38,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-04-03T14:26:57",
"op": [
"vote",
{
"voter": "theblockcafe",
"author": "sweetwilliam",
"permlink": "re-theblockcafe-the-block-cafe-20180305t184640459z",
"weight": 10000
}
]
}cryptofysent 0.001 STEEM to @sweetwilliam- "A gift. 😊"2018/03/17 20:54:39
cryptofysent 0.001 STEEM to @sweetwilliam- "A gift. 😊"
2018/03/17 20:54:39
| from | cryptofy |
| to | sweetwilliam |
| amount | 0.001 STEEM |
| memo | A gift. 😊 |
| Transaction Info | Block #20764389/Trx 3fb8ed81a4a6b1bfbbc1be65cab9c5d82244f9d8 |
View Raw JSON Data
{
"trx_id": "3fb8ed81a4a6b1bfbbc1be65cab9c5d82244f9d8",
"block": 20764389,
"trx_in_block": 35,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-17T20:54:39",
"op": [
"transfer",
{
"from": "cryptofy",
"to": "sweetwilliam",
"amount": "0.001 STEEM",
"memo": "A gift. 😊"
}
]
}sweetwilliamfollowed @manuellevi2018/03/05 18:57:33
sweetwilliamfollowed @manuellevi
2018/03/05 18:57:33
| required auths | [] |
| required posting auths | ["sweetwilliam"] |
| id | follow |
| json | ["follow",{"follower":"sweetwilliam","following":"manuellevi","what":["blog"]}] |
| Transaction Info | Block #20416919/Trx 9b5b12b896fb4286482ef079d220f209bb4f5b2b |
View Raw JSON Data
{
"trx_id": "9b5b12b896fb4286482ef079d220f209bb4f5b2b",
"block": 20416919,
"trx_in_block": 39,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-05T18:57:33",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"sweetwilliam"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"sweetwilliam\",\"following\":\"manuellevi\",\"what\":[\"blog\"]}]"
}
]
}2018/03/05 18:46:42
2018/03/05 18:46:42
| parent author | theblockcafe |
| parent permlink | the-block-cafe |
| author | sweetwilliam |
| permlink | re-theblockcafe-the-block-cafe-20180305t184640459z |
| title | |
| body | just want to commend you all for this, wonderful idea and space! |
| json metadata | {"tags":["lisboa"],"app":"steemit/0.1"} |
| Transaction Info | Block #20416702/Trx 4760f84f3652682d467ddbe50b58d3e769df992d |
View Raw JSON Data
{
"trx_id": "4760f84f3652682d467ddbe50b58d3e769df992d",
"block": 20416702,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-05T18:46:42",
"op": [
"comment",
{
"parent_author": "theblockcafe",
"parent_permlink": "the-block-cafe",
"author": "sweetwilliam",
"permlink": "re-theblockcafe-the-block-cafe-20180305t184640459z",
"title": "",
"body": "just want to commend you all for this, wonderful idea and space!",
"json_metadata": "{\"tags\":[\"lisboa\"],\"app\":\"steemit/0.1\"}"
}
]
}sweetwilliamupvoted (100.00%) @theblockcafe / the-block-cafe2018/03/05 18:44:12
sweetwilliamupvoted (100.00%) @theblockcafe / the-block-cafe
2018/03/05 18:44:12
| voter | sweetwilliam |
| author | theblockcafe |
| permlink | the-block-cafe |
| weight | 10000 (100.00%) |
| Transaction Info | Block #20416652/Trx 046c17db4f17010e140f2649a828059d8024b618 |
View Raw JSON Data
{
"trx_id": "046c17db4f17010e140f2649a828059d8024b618",
"block": 20416652,
"trx_in_block": 13,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-05T18:44:12",
"op": [
"vote",
{
"voter": "sweetwilliam",
"author": "theblockcafe",
"permlink": "the-block-cafe",
"weight": 10000
}
]
}postresteemsent 0.001 STEEM to @sweetwilliam- "Hi @sweetwilliam! Follow this account for the chance to have your post resteemed! This bot randomly selects a follower's post every hour to be resteemed! Good luck!"2018/03/01 23:15:21
postresteemsent 0.001 STEEM to @sweetwilliam- "Hi @sweetwilliam! Follow this account for the chance to have your post resteemed! This bot randomly selects a follower's post every hour to be resteemed! Good luck!"
2018/03/01 23:15:21
| from | postresteem |
| to | sweetwilliam |
| amount | 0.001 STEEM |
| memo | Hi @sweetwilliam! Follow this account for the chance to have your post resteemed! This bot randomly selects a follower's post every hour to be resteemed! Good luck! |
| Transaction Info | Block #20306906/Trx 922f487ec84984a74eba91e89fe708397dbd29a2 |
View Raw JSON Data
{
"trx_id": "922f487ec84984a74eba91e89fe708397dbd29a2",
"block": 20306906,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-03-01T23:15:21",
"op": [
"transfer",
{
"from": "postresteem",
"to": "sweetwilliam",
"amount": "0.001 STEEM",
"memo": "Hi @sweetwilliam! Follow this account for the chance to have your post resteemed! This bot randomly selects a follower's post every hour to be resteemed! Good luck!"
}
]
}sweetwilliamfollowed @mountassir2018/02/27 14:03:06
sweetwilliamfollowed @mountassir
2018/02/27 14:03:06
| required auths | [] |
| required posting auths | ["sweetwilliam"] |
| id | follow |
| json | ["follow",{"follower":"sweetwilliam","following":"mountassir","what":["blog"]}] |
| Transaction Info | Block #20238303/Trx 1f9da30560caf60943b60bb92046512b5b78d29d |
View Raw JSON Data
{
"trx_id": "1f9da30560caf60943b60bb92046512b5b78d29d",
"block": 20238303,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-27T14:03:06",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"sweetwilliam"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"sweetwilliam\",\"following\":\"mountassir\",\"what\":[\"blog\"]}]"
}
]
}talhadogansent 0.001 SBD to @sweetwilliam- "Resteem to 4.950+ Follower . Send 0.2 SBD or STEEM to @talhadogan ( URL as memo ) Service Active"2018/02/11 20:11:00
talhadogansent 0.001 SBD to @sweetwilliam- "Resteem to 4.950+ Follower . Send 0.2 SBD or STEEM to @talhadogan ( URL as memo ) Service Active"
2018/02/11 20:11:00
| from | talhadogan |
| to | sweetwilliam |
| amount | 0.001 SBD |
| memo | Resteem to 4.950+ Follower . Send 0.2 SBD or STEEM to @talhadogan ( URL as memo ) Service Active |
| Transaction Info | Block #19785238/Trx 8f98fcb306625762a9cfdbb1933a175363eb02b3 |
View Raw JSON Data
{
"trx_id": "8f98fcb306625762a9cfdbb1933a175363eb02b3",
"block": 19785238,
"trx_in_block": 8,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-11T20:11:00",
"op": [
"transfer",
{
"from": "talhadogan",
"to": "sweetwilliam",
"amount": "0.001 SBD",
"memo": "Resteem to 4.950+ Follower . Send 0.2 SBD or STEEM to @talhadogan ( URL as memo ) Service Active"
}
]
}steemdelegated 10.743 SP to @sweetwilliam2018/02/11 15:06:27
steemdelegated 10.743 SP to @sweetwilliam
2018/02/11 15:06:27
| delegator | steem |
| delegatee | sweetwilliam |
| vesting shares | 17493.867029 VESTS |
| Transaction Info | Block #19779155/Trx 6f864d37675502d3516354bc4ad947ad137cf10b |
View Raw JSON Data
{
"trx_id": "6f864d37675502d3516354bc4ad947ad137cf10b",
"block": 19779155,
"trx_in_block": 24,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-11T15:06:27",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "sweetwilliam",
"vesting_shares": "17493.867029 VESTS"
}
]
}sweetwilliamfollowed @resteem.bot2018/02/11 13:22:30
sweetwilliamfollowed @resteem.bot
2018/02/11 13:22:30
| required auths | [] |
| required posting auths | ["sweetwilliam"] |
| id | follow |
| json | ["follow",{"follower":"sweetwilliam","following":"resteem.bot","what":["blog"]}] |
| Transaction Info | Block #19777079/Trx e46f0f9555342b9a6c7f920c97bd2a3dfa201775 |
View Raw JSON Data
{
"trx_id": "e46f0f9555342b9a6c7f920c97bd2a3dfa201775",
"block": 19777079,
"trx_in_block": 28,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-11T13:22:30",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"sweetwilliam"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"sweetwilliam\",\"following\":\"resteem.bot\",\"what\":[\"blog\"]}]"
}
]
}sweetwilliamfollowed @resteembot2018/02/11 13:22:27
sweetwilliamfollowed @resteembot
2018/02/11 13:22:27
| required auths | [] |
| required posting auths | ["sweetwilliam"] |
| id | follow |
| json | ["follow",{"follower":"sweetwilliam","following":"resteembot","what":["blog"]}] |
| Transaction Info | Block #19777078/Trx 54c4e399be608fe48f7587dba85c5224f1b97c14 |
View Raw JSON Data
{
"trx_id": "54c4e399be608fe48f7587dba85c5224f1b97c14",
"block": 19777078,
"trx_in_block": 30,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-11T13:22:27",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"sweetwilliam"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"sweetwilliam\",\"following\":\"resteembot\",\"what\":[\"blog\"]}]"
}
]
}sweetwilliamsent 0.047 SBD to @resteem.bot- "https://steemit.com/travel/@sweetwilliam/morocco-fez-and-chefchaouen"2018/02/11 13:21:51
sweetwilliamsent 0.047 SBD to @resteem.bot- "https://steemit.com/travel/@sweetwilliam/morocco-fez-and-chefchaouen"
2018/02/11 13:21:51
| from | sweetwilliam |
| to | resteem.bot |
| amount | 0.047 SBD |
| memo | https://steemit.com/travel/@sweetwilliam/morocco-fez-and-chefchaouen |
| Transaction Info | Block #19777066/Trx 03bb62c5138def81e8f9ee0ba53c79142a815b7c |
View Raw JSON Data
{
"trx_id": "03bb62c5138def81e8f9ee0ba53c79142a815b7c",
"block": 19777066,
"trx_in_block": 25,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-11T13:21:51",
"op": [
"transfer",
{
"from": "sweetwilliam",
"to": "resteem.bot",
"amount": "0.047 SBD",
"memo": "https://steemit.com/travel/@sweetwilliam/morocco-fez-and-chefchaouen"
}
]
}2018/02/11 13:13:06
2018/02/11 13:13:06
| voter | sweetwilliam |
| author | raclariu |
| permlink | comprehensive-list-of-paid-voting-bots-resteem-bots-and-bidding-bots |
| weight | 10000 (100.00%) |
| Transaction Info | Block #19776891/Trx f495527c8734cdda9e75f9938c6c052f75dafc7c |
View Raw JSON Data
{
"trx_id": "f495527c8734cdda9e75f9938c6c052f75dafc7c",
"block": 19776891,
"trx_in_block": 19,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-11T13:13:06",
"op": [
"vote",
{
"voter": "sweetwilliam",
"author": "raclariu",
"permlink": "comprehensive-list-of-paid-voting-bots-resteem-bots-and-bidding-bots",
"weight": 10000
}
]
}resteembotsent 0.047 SBD to @sweetwilliam- "sweetwilliam is not a follower, or 3 hours haven't passed since following"2018/02/11 13:12:15
resteembotsent 0.047 SBD to @sweetwilliam- "sweetwilliam is not a follower, or 3 hours haven't passed since following"
2018/02/11 13:12:15
| from | resteembot |
| to | sweetwilliam |
| amount | 0.047 SBD |
| memo | sweetwilliam is not a follower, or 3 hours haven't passed since following |
| Transaction Info | Block #19776874/Trx e11a2ea2c4d824790c5cdb1bded209facae058f4 |
View Raw JSON Data
{
"trx_id": "e11a2ea2c4d824790c5cdb1bded209facae058f4",
"block": 19776874,
"trx_in_block": 41,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-11T13:12:15",
"op": [
"transfer",
{
"from": "resteembot",
"to": "sweetwilliam",
"amount": "0.047 SBD",
"memo": "sweetwilliam is not a follower, or 3 hours haven't passed since following"
}
]
}sweetwilliamsent 0.047 SBD to @resteembot- "https://steemit.com/travel/@sweetwilliam/morocco-fez-and-chefchaouen"2018/02/11 13:11:39
sweetwilliamsent 0.047 SBD to @resteembot- "https://steemit.com/travel/@sweetwilliam/morocco-fez-and-chefchaouen"
2018/02/11 13:11:39
| from | sweetwilliam |
| to | resteembot |
| amount | 0.047 SBD |
| memo | https://steemit.com/travel/@sweetwilliam/morocco-fez-and-chefchaouen |
| Transaction Info | Block #19776862/Trx 77af9eba9754a0a758e41c23b7f717674a2058f2 |
View Raw JSON Data
{
"trx_id": "77af9eba9754a0a758e41c23b7f717674a2058f2",
"block": 19776862,
"trx_in_block": 14,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-11T13:11:39",
"op": [
"transfer",
{
"from": "sweetwilliam",
"to": "resteembot",
"amount": "0.047 SBD",
"memo": "https://steemit.com/travel/@sweetwilliam/morocco-fez-and-chefchaouen"
}
]
}sweetwilliamclaimed reward balance: 0.493 SBD, 0.220 SP2018/02/11 13:03:24
sweetwilliamclaimed reward balance: 0.493 SBD, 0.220 SP
2018/02/11 13:03:24
| account | sweetwilliam |
| reward steem | 0.000 STEEM |
| reward sbd | 0.493 SBD |
| reward vests | 358.628895 VESTS |
| Transaction Info | Block #19776697/Trx 9a1c7940a4f490413bd9def8f51d845da5fffa23 |
View Raw JSON Data
{
"trx_id": "9a1c7940a4f490413bd9def8f51d845da5fffa23",
"block": 19776697,
"trx_in_block": 22,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-11T13:03:24",
"op": [
"claim_reward_balance",
{
"account": "sweetwilliam",
"reward_steem": "0.000 STEEM",
"reward_sbd": "0.493 SBD",
"reward_vests": "358.628895 VESTS"
}
]
}sweetwilliamfollowed @joydip81162018/02/11 13:00:42
sweetwilliamfollowed @joydip8116
2018/02/11 13:00:42
| required auths | [] |
| required posting auths | ["sweetwilliam"] |
| id | follow |
| json | ["follow",{"follower":"sweetwilliam","following":"joydip8116","what":["blog"]}] |
| Transaction Info | Block #19776643/Trx b78950ab719c3fe6da243decf658abc3e8f22847 |
View Raw JSON Data
{
"trx_id": "b78950ab719c3fe6da243decf658abc3e8f22847",
"block": 19776643,
"trx_in_block": 39,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-11T13:00:42",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"sweetwilliam"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"sweetwilliam\",\"following\":\"joydip8116\",\"what\":[\"blog\"]}]"
}
]
}sweetwilliamupvoted (100.00%) @sweetwilliam / lake-michigan-road-trip2018/02/11 09:43:36
sweetwilliamupvoted (100.00%) @sweetwilliam / lake-michigan-road-trip
2018/02/11 09:43:36
| voter | sweetwilliam |
| author | sweetwilliam |
| permlink | lake-michigan-road-trip |
| weight | 10000 (100.00%) |
| Transaction Info | Block #19772702/Trx bf266ff055a783928673067bc60052a8802a2dff |
View Raw JSON Data
{
"trx_id": "bf266ff055a783928673067bc60052a8802a2dff",
"block": 19772702,
"trx_in_block": 14,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-11T09:43:36",
"op": [
"vote",
{
"voter": "sweetwilliam",
"author": "sweetwilliam",
"permlink": "lake-michigan-road-trip",
"weight": 10000
}
]
}sweetwilliamupvoted (100.00%) @sweetwilliam / morocco-fez-and-chefchaouen2018/02/10 13:57:18
sweetwilliamupvoted (100.00%) @sweetwilliam / morocco-fez-and-chefchaouen
2018/02/10 13:57:18
| voter | sweetwilliam |
| author | sweetwilliam |
| permlink | morocco-fez-and-chefchaouen |
| weight | 10000 (100.00%) |
| Transaction Info | Block #19748991/Trx 2e0b399d3600df1bd53a5f7a1b5ee72436026848 |
View Raw JSON Data
{
"trx_id": "2e0b399d3600df1bd53a5f7a1b5ee72436026848",
"block": 19748991,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-10T13:57:18",
"op": [
"vote",
{
"voter": "sweetwilliam",
"author": "sweetwilliam",
"permlink": "morocco-fez-and-chefchaouen",
"weight": 10000
}
]
}sensationupvoted (100.00%) @sweetwilliam / morocco-fez-and-chefchaouen2018/02/09 23:53:03
sensationupvoted (100.00%) @sweetwilliam / morocco-fez-and-chefchaouen
2018/02/09 23:53:03
| voter | sensation |
| author | sweetwilliam |
| permlink | morocco-fez-and-chefchaouen |
| weight | 10000 (100.00%) |
| Transaction Info | Block #19732114/Trx 2f0d976bf74a886504ef071c1491ef0d7607fd8d |
View Raw JSON Data
{
"trx_id": "2f0d976bf74a886504ef071c1491ef0d7607fd8d",
"block": 19732114,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-09T23:53:03",
"op": [
"vote",
{
"voter": "sensation",
"author": "sweetwilliam",
"permlink": "morocco-fez-and-chefchaouen",
"weight": 10000
}
]
}steemfuzzysent 0.001 STEEM to @sweetwilliam- "Thank you for visiting my blog -- @steemfuzzy. Please upvote and follow me."2018/02/09 22:35:06
steemfuzzysent 0.001 STEEM to @sweetwilliam- "Thank you for visiting my blog -- @steemfuzzy. Please upvote and follow me."
2018/02/09 22:35:06
| from | steemfuzzy |
| to | sweetwilliam |
| amount | 0.001 STEEM |
| memo | Thank you for visiting my blog -- @steemfuzzy. Please upvote and follow me. |
| Transaction Info | Block #19730556/Trx a2921f979ff5907a3447b614fafd61c759d02a72 |
View Raw JSON Data
{
"trx_id": "a2921f979ff5907a3447b614fafd61c759d02a72",
"block": 19730556,
"trx_in_block": 21,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-09T22:35:06",
"op": [
"transfer",
{
"from": "steemfuzzy",
"to": "sweetwilliam",
"amount": "0.001 STEEM",
"memo": "Thank you for visiting my blog -- @steemfuzzy. Please upvote and follow me."
}
]
}sweetwilliampublished a new post: morocco-fez-and-chefchaouen2018/02/09 22:30:39
sweetwilliampublished a new post: morocco-fez-and-chefchaouen
2018/02/09 22:30:39
| parent author | |
| parent permlink | travel |
| author | sweetwilliam |
| permlink | morocco-fez-and-chefchaouen |
| title | Morocco: Fez and Chefchaouen |
| body |  Morocco is a dazzling country, travelling in it one can appreciate many experiences, from trekking the Atlas mountains, seeing the stars in the Sahara, haggling in ancient bazaars, relaxing in palatial riads, or simply taking it easy with a mint tea. In this journey we barely scratched the surface of what Morocco has to offer.  ## The geography Morocco is the westernmost frontier of the Arab world, sheltered from the rest of Africa by the mighty Sahara, and the towering Atlas Mountains. It is similar in size to California or Spain, with a population of 33 million, and a unique climate and history straddling the Mediterranean and Saharan Africa. The luscious northern highlands of Morocco are in stark contrast to the dunes and desert of the south.  Morocco has a fortunate location and close proximity to Europe, with Spain just 15 miles over the Strait of Gibraltar, as well as access to both the Mediterranean Ocean and the Atlantic Ocean. 🙋 *Fun fact: France and Spain are the only other two countries bordering both the Mediterranean and Atlantic Oceans.*  ## The history Morocco is an intriguing blend of cultural influences primarily from Islamic, Berber, and European cultures. A rich civilisation and distinct culture has emerged through the successive migrations and invasions of people from all over the world. > 1. Human activity in Morocco can be traced back between 90 and 125,000 years. > 2. The predominant **Berber population** thought to be descendants of ancient Egyptians, established their tribal strongholds about 3,000 years ago. > 3. From the east the **Phonencians** started to arrive in Morocco around 800 BC. > 4. **Carthaginians** arrived around 200 BC, before falling to **Roman** rule in 146 BC. > 5. As the Roman empire fell into decline Morocco was invaded by the **Germanic Vandals tribe**. > 6. **Arabs** arrived in 700 AD bringing Islam, and a spate of ruling dynasties including: the **Idrissids**, the **Almoravids**, and the **Almohads**. > 7. By the 15<sup>th</sup> century **Spain** and **Portugal** began to intrude into Morocco, after having expelled the Moors from their own lands. > 8. By the middle of the 19<sup>th</sup> century Morocco's strategic importance had become evident to all of the European powers, and they engaged in a protracted struggle for possession of the country. > 9. In 1911, **France** was formally acknowledged as protector of the greater part of the country, with **Spain** receiving a number of isolated regions. > 10. French rule came to an end in 1953. > 11. Today, the country is ruled by **King Mohammed VI**. He appears to be leading Morocco toward both long-term stability and a greater degree of economic prosperity.  🙋 *Fun fact: Romans began making wine in Morocco over 2,000 years ago. This practice was abolished with the establishment of Islam in the 7th century AD. Under the French Protectorate, the Moroccan vineyards were revived and, in 1956, passed into state control. The Gris de Boulaouane, a rosé with an orange tint, is one of the best Moroccan wines.* Today, the complex history of Morocco is reflected by the varied ethnic groups, diverse architecture, unique cuisine, and multiple languages. The two official languages are Arabic and Amazigh (Berber), but French is also well known yet considered an aristocratic language. In the northern areas of Morocco Spanish is commonly spoken. English has also gained a presence in the country since it was introduced to the public school system in 2002.  ## The Western Sahara Western Sahara is a disputed territory south of Morocco, slightly larger than the size of the United Kingdom. This area is some of the most arid, inhospitable, sparsely populated land on the planet. Since the withdrawal of the colonial ruler Spain in 1975 the region has been claimed by Morocco, Mauritania, and the self-proclaimed Sahrwai Arab Democratic Republic. The Polisario Front arose to fight for independence and the establishment of the Sahrwai Arab Democratic Republic, they fought a bloody 16 year long war, ending in a UN coordinated cease-fire in 1991. The cease-fire was agreed on the promise of a referendum for the Sahrwai people to determine their sovereignty. A referendum never happened and today the region is 80% controlled and administered by Morocco, with the Polisario Front controlling the remaining land. The area has a strong military presence and demonstrations criticising the Moroccan authorities occur regularly, with periodic ethnic tensions between the native Sahrawi population and Moroccan immigrants. The Morocco controlled region of Western Sahara contains more than 72% of the worlds Phosphate. This phosphate is a key element in fertilisers and is therefore a vital global commodity. Fertilisers made from phosphate rich rocks are necessary to grow nearly every crop, without which humanity’s growing population would not be able to feed itself. As other country’s domestic reserves of phosphate are depleted the in the coming decades, this disputed region could be essential for meeting global demand.  🙋 *Fun fact: the longest converyor belt in the world runs from the Bou Craa phosphate mine in Western Sahara 61 miles across the desert to Port El Aaiún, where massive ships transport its contents across the globe.* To find out more about Western Sahara phosphate production read this [article](https://www.theatlantic.com/science/archive/2016/11/the-desert-rock-that-feeds-the-world/508853/), and to better understand the complex political situation in the Western Sahara watch this [video](https://www.youtube.com/watch?v=4SakRNO_SMY).  ## The food Moroccan cuisine is a delight! A mixture of Mediterranean, Arabic, Andalusian, and most importantly, Berber cuisine with a tiny European and Subsaharian influence. In the below image you can see a Chefchaouen goat's cheese salad, chickpea soup, a Moroccan dinner, vegetable tagine, mint tea, and tagines cooking.  Tagines are ubiquitous slow-cooked Moroccan stews, which take their name from the conical clay or ceramic dish that its cooked in. 🙋 *Fun fact: the national drink tea was first introduced to Morocco in 1854 when blockaded British merchants uploaded large quantities of tea at major Moroccan ports. Thé à la Menthe (Green Mint Tea) is Chinese green tea brewed with a handful of mint leaves and liberally loaded with sugar.* ## Fez Fez is an ancient walled city founded by Idris I in 789. The central medina area is a [UNESCOworld heritage site](http://whc.unesco.org/en/list/170) of narrow maze like alleys jam packed with small shops and traders. Walking around the medina is enthralling and sometimes overwhelming. Yet, there are plenty of peaceful rooftop cafes and relaxing restaurants to slip into, of which [cafe clock](http://fez.cafeclock.com/) comes highly recommended (the date smoothie is highly recommended).  🙋 *Fun fact: Fez el-bali (Old Fez) is the world’s largest active medieval city and car free zone.* There are also some unique accommodation options available in Fez such as staying in [Palais El Mokri](http://www.vivtravel.com/palais-el-mokri-hidden-palace-fez/). A crumbling yet magnificent palace still in the family of [Muhammad al-Muqri](https://en.wikipedia.org/wiki/Muhammad_al-Muqri).  ## Chefchaouen The wonderful mountainous city of Chefchaouen in the northern part of Morocco was founded in 1471 as a fortress city to defend against Portuguese invasions.  Almost every building is painted blue with theories abounding as to the reason for this. Some say it to keep mosquito's away, whilst others say that Jews when fleeing Hitler in the 1930s introduced it as a reminder of sky, heaven and leading a spiritual life.  🙋 *Fun fact: a popular garment amoungst Berber's of the Atlas mountains is the djellaba. A long cotton or woolen hooded robe. Traditionally the colour of a djellaba indicates the marital status of the wearer, with light colours for married people.* Chefchaouen is a very refreshing and relaxing place to spend some time enjoying the fine mountain air and pleasant scenery. There are also some wonderful handicraft shops and handmade carpets to purchase.  ## Final words Morocco is absolutely stupendous and has much to explore and experience. If you are lucky enough to visit the best advice I can pass on is wherever you go remember to 'notice the patterns'.  |
| json metadata | {"tags":["travel","photography","morocco","africa","life"],"image":["https://steemitimages.com/DQmbSFdn15U4wuwQABopq8aLgKLdq6rifVu6fMos738sgG9/tiles4.png","https://steemitimages.com/DQmcfy4G6APcbHrCCSTQshj64XKuYVJZBYH6EcJNVkNfRAg/tiles7.png","https://steemitimages.com/DQmNqStHuLR2hTKy6YaQuSU2pCyxKUGkLgaQ9B1snjhhczH/morocco.jpg","https://steemitimages.com/DQmaGc6ctUH4adR8WeRpgaHWtU7BfRYgNmikY5KgZhxgiu2/collage.jpg","https://steemitimages.com/DQmP95DxSj9Qt38Q1usCBc4P3xuGSsEnmNP6tAy7zjQWVcN/collage.jpg","https://steemitimages.com/DQmYcfLYFE6PM17DtpgiEdHr492Bg9eExdM52H3WCg7ysKj/collage.jpg","https://steemitimages.com/DQmZkoV7o7kopxjPVKfG5icx2Bf5dLeXf51E2rhs6dfXCaB/collage.jpg","https://steemitimages.com/DQmSJMZiG6AiTsCAMvwSyUrwH2n13rM4EJtJYcL9LEJ1gGw/DSCF4762.JPG","https://steemitimages.com/DQmR8L3vrm5q7VEsm4kuayepBERPCkJdNsyHUzvmBfBjL7V/collage.jpg","https://steemitimages.com/DQmZpcHEHqyt1pd9siEioWgkQnmUcFianffEhNa5PY9TwRf/DSCF4782.JPG"],"links":["https://www.theatlantic.com/science/archive/2016/11/the-desert-rock-that-feeds-the-world/508853/","https://www.youtube.com/watch?v=4SakRNO_SMY","http://whc.unesco.org/en/list/170","http://fez.cafeclock.com/","http://www.vivtravel.com/palais-el-mokri-hidden-palace-fez/","https://en.wikipedia.org/wiki/Muhammad_al-Muqri"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #19730467/Trx c22461926f109d79364ca3351049be75cfdabd86 |
View Raw JSON Data
{
"trx_id": "c22461926f109d79364ca3351049be75cfdabd86",
"block": 19730467,
"trx_in_block": 40,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-09T22:30:39",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "travel",
"author": "sweetwilliam",
"permlink": "morocco-fez-and-chefchaouen",
"title": "Morocco: Fez and Chefchaouen",
"body": "\n\nMorocco is a dazzling country, travelling in it one can appreciate many experiences, from trekking the Atlas mountains, seeing the stars in the Sahara, haggling in ancient bazaars, relaxing in palatial riads, or simply taking it easy with a mint tea.\n\nIn this journey we barely scratched the surface of what Morocco has to offer.\n\n\n## The geography\nMorocco is the westernmost frontier of the Arab world, sheltered from the rest of Africa by the mighty Sahara, and the towering Atlas Mountains. It is similar in size to California or Spain, with a population of 33 million, and a unique climate and history straddling the Mediterranean and Saharan Africa. The luscious northern highlands of Morocco are in stark contrast to the dunes and desert of the south. \n\n\n\nMorocco has a fortunate location and close proximity to Europe, with Spain just 15 miles over the Strait of Gibraltar, as well as access to both the Mediterranean Ocean and the Atlantic Ocean.\n\n🙋 *Fun fact: France and Spain are the only other two countries bordering both the Mediterranean and Atlantic Oceans.*\n\n\n## The history\nMorocco is an intriguing blend of cultural influences primarily from Islamic, Berber, and European cultures. A rich civilisation and distinct culture has emerged through the successive migrations and invasions of people from all over the world. \n\n> 1. Human activity in Morocco can be traced back between 90 and 125,000 years. \n> 2. The predominant **Berber population** thought to be descendants of ancient Egyptians, established their tribal strongholds about 3,000 years ago.\n> 3. From the east the **Phonencians** started to arrive in Morocco around 800 BC.\n> 4. **Carthaginians** arrived around 200 BC, before falling to **Roman** rule in 146 BC.\n> 5. As the Roman empire fell into decline Morocco was invaded by the **Germanic Vandals tribe**.\n> 6. **Arabs** arrived in 700 AD bringing Islam, and a spate of ruling dynasties including: the **Idrissids**, the **Almoravids**, and the **Almohads**.\n> 7. By the 15<sup>th</sup> century **Spain** and **Portugal** began to intrude into Morocco, after having expelled the Moors from their own lands. \n> 8. By the middle of the 19<sup>th</sup> century Morocco's strategic importance had become evident to all of the European powers, and they engaged in a protracted struggle for possession of the country. \n> 9. In 1911, **France** was formally acknowledged as protector of the greater part of the country, with **Spain** receiving a number of isolated regions. \n> 10. French rule came to an end in 1953.\n> 11. Today, the country is ruled by **King Mohammed VI**. He appears to be leading Morocco toward both long-term stability and a greater degree of economic prosperity. \n\n\n\n🙋 *Fun fact: Romans began making wine in Morocco over 2,000 years ago. This practice was abolished with the establishment of Islam in the 7th century AD. Under the French Protectorate, the Moroccan vineyards were revived and, in 1956, passed into state control. The Gris de Boulaouane, a rosé with an orange tint, is one of the best Moroccan wines.*\n\n\nToday, the complex history of Morocco is reflected by the varied ethnic groups, diverse architecture, unique cuisine, and multiple languages. The two official languages are Arabic and Amazigh (Berber), but French is also well known yet considered an aristocratic language. In the northern areas of Morocco Spanish is commonly spoken. English has also gained a presence in the country since it was introduced to the public school system in 2002. \n\n\n## The Western Sahara\nWestern Sahara is a disputed territory south of Morocco, slightly larger than the size of the United Kingdom. This area is some of the most arid, inhospitable, sparsely populated land on the planet.\n\nSince the withdrawal of the colonial ruler Spain in 1975 the region has been claimed by Morocco, Mauritania, and the self-proclaimed Sahrwai Arab Democratic Republic. The Polisario Front arose to fight for independence and the establishment of the Sahrwai Arab Democratic Republic, they fought a bloody 16 year long war, ending in a UN coordinated cease-fire in 1991.\n\nThe cease-fire was agreed on the promise of a referendum for the Sahrwai people to determine their sovereignty. A referendum never happened and today the region is 80% controlled and administered by Morocco, with the Polisario Front controlling the remaining land. The area has a strong military presence and demonstrations criticising the Moroccan authorities occur regularly, with periodic ethnic tensions between the native Sahrawi population and Moroccan immigrants.\n\nThe Morocco controlled region of Western Sahara contains more than 72% of the worlds Phosphate. This phosphate is a key element in fertilisers and is therefore a vital global commodity. Fertilisers made from phosphate rich rocks are necessary to grow nearly every crop, without which humanity’s growing population would not be able to feed itself. As other country’s domestic reserves of phosphate are depleted the in the coming decades, this disputed region could be essential for meeting global demand.\n\n\n\n🙋 *Fun fact: the longest converyor belt in the world runs from the Bou Craa phosphate mine in Western Sahara 61 miles across the desert to Port El Aaiún, where massive ships transport its contents across the globe.*\n\nTo find out more about Western Sahara phosphate production read this [article](https://www.theatlantic.com/science/archive/2016/11/the-desert-rock-that-feeds-the-world/508853/), and to better understand the complex political situation in the Western Sahara watch this [video](https://www.youtube.com/watch?v=4SakRNO_SMY).\n\n\n## The food\nMoroccan cuisine is a delight! A mixture of Mediterranean, Arabic, Andalusian, and most importantly, Berber cuisine with a tiny European and Subsaharian influence. In the below image you can see a Chefchaouen goat's cheese salad, chickpea soup, a Moroccan dinner, vegetable tagine, mint tea, and tagines cooking.\n\n\n\nTagines are ubiquitous slow-cooked Moroccan stews, which take their name from the conical clay or ceramic dish that its cooked in.\n\n🙋 *Fun fact: the national drink tea was first introduced to Morocco in 1854 when blockaded British merchants uploaded large quantities of tea at major Moroccan ports. Thé à la Menthe (Green Mint Tea) is Chinese green tea brewed with a handful of mint leaves and liberally loaded with sugar.*\n\n## Fez\nFez is an ancient walled city founded by Idris I in 789. The central medina area is a [UNESCOworld heritage site](http://whc.unesco.org/en/list/170) of narrow maze like alleys jam packed with small shops and traders. Walking around the medina is enthralling and sometimes overwhelming. Yet, there are plenty of peaceful rooftop cafes and relaxing restaurants to slip into, of which [cafe clock](http://fez.cafeclock.com/) comes highly recommended (the date smoothie is highly recommended).\n\n\n\n🙋 *Fun fact: Fez el-bali (Old Fez) is the world’s largest active medieval city and car free zone.*\n\nThere are also some unique accommodation options available in Fez such as staying in [Palais El Mokri](http://www.vivtravel.com/palais-el-mokri-hidden-palace-fez/). A crumbling yet magnificent palace still in the family of [Muhammad al-Muqri](https://en.wikipedia.org/wiki/Muhammad_al-Muqri).\n\n\n## Chefchaouen\nThe wonderful mountainous city of Chefchaouen in the northern part of Morocco was founded in 1471 as a fortress city to defend against Portuguese invasions.\n\n\n\nAlmost every building is painted blue with theories abounding as to the reason for this. Some say it to keep mosquito's away, whilst others say that Jews when fleeing Hitler in the 1930s introduced it as a reminder of sky, heaven and leading a spiritual life.\n\n\n\n🙋 *Fun fact: a popular garment amoungst Berber's of the Atlas mountains is the djellaba. A long cotton or woolen hooded robe. Traditionally the colour of a djellaba indicates the marital status of the wearer, with light colours for married people.*\n\nChefchaouen is a very refreshing and relaxing place to spend some time enjoying the fine mountain air and pleasant scenery. There are also some wonderful handicraft shops and handmade carpets to purchase.\n\n\n## Final words\nMorocco is absolutely stupendous and has much to explore and experience. If you are lucky enough to visit the best advice I can pass on is wherever you go remember to 'notice the patterns'.\n\n",
"json_metadata": "{\"tags\":[\"travel\",\"photography\",\"morocco\",\"africa\",\"life\"],\"image\":[\"https://steemitimages.com/DQmbSFdn15U4wuwQABopq8aLgKLdq6rifVu6fMos738sgG9/tiles4.png\",\"https://steemitimages.com/DQmcfy4G6APcbHrCCSTQshj64XKuYVJZBYH6EcJNVkNfRAg/tiles7.png\",\"https://steemitimages.com/DQmNqStHuLR2hTKy6YaQuSU2pCyxKUGkLgaQ9B1snjhhczH/morocco.jpg\",\"https://steemitimages.com/DQmaGc6ctUH4adR8WeRpgaHWtU7BfRYgNmikY5KgZhxgiu2/collage.jpg\",\"https://steemitimages.com/DQmP95DxSj9Qt38Q1usCBc4P3xuGSsEnmNP6tAy7zjQWVcN/collage.jpg\",\"https://steemitimages.com/DQmYcfLYFE6PM17DtpgiEdHr492Bg9eExdM52H3WCg7ysKj/collage.jpg\",\"https://steemitimages.com/DQmZkoV7o7kopxjPVKfG5icx2Bf5dLeXf51E2rhs6dfXCaB/collage.jpg\",\"https://steemitimages.com/DQmSJMZiG6AiTsCAMvwSyUrwH2n13rM4EJtJYcL9LEJ1gGw/DSCF4762.JPG\",\"https://steemitimages.com/DQmR8L3vrm5q7VEsm4kuayepBERPCkJdNsyHUzvmBfBjL7V/collage.jpg\",\"https://steemitimages.com/DQmZpcHEHqyt1pd9siEioWgkQnmUcFianffEhNa5PY9TwRf/DSCF4782.JPG\"],\"links\":[\"https://www.theatlantic.com/science/archive/2016/11/the-desert-rock-that-feeds-the-world/508853/\",\"https://www.youtube.com/watch?v=4SakRNO_SMY\",\"http://whc.unesco.org/en/list/170\",\"http://fez.cafeclock.com/\",\"http://www.vivtravel.com/palais-el-mokri-hidden-palace-fez/\",\"https://en.wikipedia.org/wiki/Muhammad_al-Muqri\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}sweetwilliamreceived 0.022 SBD, 0.011 SP author reward for @sweetwilliam / re-hotsauceislethal-re-sweetwilliam-why-would-anyone-use-bitcoin-20171223t204912187z2017/12/30 20:49:12
sweetwilliamreceived 0.022 SBD, 0.011 SP author reward for @sweetwilliam / re-hotsauceislethal-re-sweetwilliam-why-would-anyone-use-bitcoin-20171223t204912187z
2017/12/30 20:49:12
| author | sweetwilliam |
| permlink | re-hotsauceislethal-re-sweetwilliam-why-would-anyone-use-bitcoin-20171223t204912187z |
| sbd payout | 0.022 SBD |
| steem payout | 0.000 STEEM |
| vesting payout | 18.443733 VESTS |
| Transaction Info | Block #18548971/Virtual Operation #37 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 18548971,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 37,
"timestamp": "2017-12-30T20:49:12",
"op": [
"author_reward",
{
"author": "sweetwilliam",
"permlink": "re-hotsauceislethal-re-sweetwilliam-why-would-anyone-use-bitcoin-20171223t204912187z",
"sbd_payout": "0.022 SBD",
"steem_payout": "0.000 STEEM",
"vesting_payout": "18.443733 VESTS"
}
]
}sweetwilliamreceived 0.471 SBD, 0.208 SP author reward for @sweetwilliam / why-would-anyone-use-bitcoin2017/12/30 19:44:45
sweetwilliamreceived 0.471 SBD, 0.208 SP author reward for @sweetwilliam / why-would-anyone-use-bitcoin
2017/12/30 19:44:45
| author | sweetwilliam |
| permlink | why-would-anyone-use-bitcoin |
| sbd payout | 0.471 SBD |
| steem payout | 0.000 STEEM |
| vesting payout | 338.135854 VESTS |
| Transaction Info | Block #18547682/Virtual Operation #8 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 18547682,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 8,
"timestamp": "2017-12-30T19:44:45",
"op": [
"author_reward",
{
"author": "sweetwilliam",
"permlink": "why-would-anyone-use-bitcoin",
"sbd_payout": "0.471 SBD",
"steem_payout": "0.000 STEEM",
"vesting_payout": "338.135854 VESTS"
}
]
}sweetwilliamreceived 0.001 SP curation reward for @sweetwilliam / why-would-anyone-use-bitcoin2017/12/30 19:44:45
sweetwilliamreceived 0.001 SP curation reward for @sweetwilliam / why-would-anyone-use-bitcoin
2017/12/30 19:44:45
| curator | sweetwilliam |
| reward | 2.049308 VESTS |
| comment author | sweetwilliam |
| comment permlink | why-would-anyone-use-bitcoin |
| Transaction Info | Block #18547682/Virtual Operation #7 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 18547682,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 7,
"timestamp": "2017-12-30T19:44:45",
"op": [
"curation_reward",
{
"curator": "sweetwilliam",
"reward": "2.049308 VESTS",
"comment_author": "sweetwilliam",
"comment_permlink": "why-would-anyone-use-bitcoin"
}
]
}docsmithupvoted (100.00%) @sweetwilliam / why-would-anyone-use-bitcoin2017/12/29 22:41:48
docsmithupvoted (100.00%) @sweetwilliam / why-would-anyone-use-bitcoin
2017/12/29 22:41:48
| voter | docsmith |
| author | sweetwilliam |
| permlink | why-would-anyone-use-bitcoin |
| weight | 10000 (100.00%) |
| Transaction Info | Block #18522428/Trx 98016a34b484a6a857ae94938ade140ed07caa2a |
View Raw JSON Data
{
"trx_id": "98016a34b484a6a857ae94938ade140ed07caa2a",
"block": 18522428,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-29T22:41:48",
"op": [
"vote",
{
"voter": "docsmith",
"author": "sweetwilliam",
"permlink": "why-would-anyone-use-bitcoin",
"weight": 10000
}
]
}rushofwavesremoved vote from (0.00%) @sweetwilliam / why-would-anyone-use-bitcoin2017/12/29 17:42:24
rushofwavesremoved vote from (0.00%) @sweetwilliam / why-would-anyone-use-bitcoin
2017/12/29 17:42:24
| voter | rushofwaves |
| author | sweetwilliam |
| permlink | why-would-anyone-use-bitcoin |
| weight | 0 (0.00%) |
| Transaction Info | Block #18516440/Trx 4f73d32bd1f344bf78ed46b4253ffbedc64b1d3e |
View Raw JSON Data
{
"trx_id": "4f73d32bd1f344bf78ed46b4253ffbedc64b1d3e",
"block": 18516440,
"trx_in_block": 17,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-29T17:42:24",
"op": [
"vote",
{
"voter": "rushofwaves",
"author": "sweetwilliam",
"permlink": "why-would-anyone-use-bitcoin",
"weight": 0
}
]
}rushofwavesupvoted (100.00%) @sweetwilliam / why-would-anyone-use-bitcoin2017/12/29 17:42:06
rushofwavesupvoted (100.00%) @sweetwilliam / why-would-anyone-use-bitcoin
2017/12/29 17:42:06
| voter | rushofwaves |
| author | sweetwilliam |
| permlink | why-would-anyone-use-bitcoin |
| weight | 10000 (100.00%) |
| Transaction Info | Block #18516434/Trx 997ed20c27e5e6902b6dd948fc992296eb06efbb |
View Raw JSON Data
{
"trx_id": "997ed20c27e5e6902b6dd948fc992296eb06efbb",
"block": 18516434,
"trx_in_block": 14,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-29T17:42:06",
"op": [
"vote",
{
"voter": "rushofwaves",
"author": "sweetwilliam",
"permlink": "why-would-anyone-use-bitcoin",
"weight": 10000
}
]
}pampermenetworkupvoted (100.00%) @sweetwilliam / why-would-anyone-use-bitcoin2017/12/29 00:36:39
pampermenetworkupvoted (100.00%) @sweetwilliam / why-would-anyone-use-bitcoin
2017/12/29 00:36:39
| voter | pampermenetwork |
| author | sweetwilliam |
| permlink | why-would-anyone-use-bitcoin |
| weight | 10000 (100.00%) |
| Transaction Info | Block #18495927/Trx 27fc9a29440c1c5b4bf5899dbb65e999f33deea9 |
View Raw JSON Data
{
"trx_id": "27fc9a29440c1c5b4bf5899dbb65e999f33deea9",
"block": 18495927,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-29T00:36:39",
"op": [
"vote",
{
"voter": "pampermenetwork",
"author": "sweetwilliam",
"permlink": "why-would-anyone-use-bitcoin",
"weight": 10000
}
]
}sweetwilliamupvoted (100.00%) @ura-soul / stunning-scenes-from-the-english-welsh-hills-over-xmas2017/12/28 12:56:39
sweetwilliamupvoted (100.00%) @ura-soul / stunning-scenes-from-the-english-welsh-hills-over-xmas
2017/12/28 12:56:39
| voter | sweetwilliam |
| author | ura-soul |
| permlink | stunning-scenes-from-the-english-welsh-hills-over-xmas |
| weight | 10000 (100.00%) |
| Transaction Info | Block #18481937/Trx bca6fb2eeb9c8cf1f6e00851380324fa1d63b4d7 |
View Raw JSON Data
{
"trx_id": "bca6fb2eeb9c8cf1f6e00851380324fa1d63b4d7",
"block": 18481937,
"trx_in_block": 10,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-28T12:56:39",
"op": [
"vote",
{
"voter": "sweetwilliam",
"author": "ura-soul",
"permlink": "stunning-scenes-from-the-english-welsh-hills-over-xmas",
"weight": 10000
}
]
}2017/12/28 09:28:45
2017/12/28 09:28:45
| parent author | sweetwilliam |
| parent permlink | why-would-anyone-use-bitcoin |
| author | ansarmehmood |
| permlink | re-sweetwilliam-why-would-anyone-use-bitcoin-20171228t092728098z |
| title | |
| body | Wow really amazing.I am new here so please guide me follow me. As will as wish you. |
| json metadata | {"tags":["bitcoin"],"app":"steemit/0.1"} |
| Transaction Info | Block #18477782/Trx c8c834dd6e3f79418028c3d0fe44a39f71295cea |
View Raw JSON Data
{
"trx_id": "c8c834dd6e3f79418028c3d0fe44a39f71295cea",
"block": 18477782,
"trx_in_block": 10,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-28T09:28:45",
"op": [
"comment",
{
"parent_author": "sweetwilliam",
"parent_permlink": "why-would-anyone-use-bitcoin",
"author": "ansarmehmood",
"permlink": "re-sweetwilliam-why-would-anyone-use-bitcoin-20171228t092728098z",
"title": "",
"body": "Wow really amazing.I am new here so please guide me follow me. As will as wish you.",
"json_metadata": "{\"tags\":[\"bitcoin\"],\"app\":\"steemit/0.1\"}"
}
]
}uknowjpbitcoinupvoted (100.00%) @sweetwilliam / why-would-anyone-use-bitcoin2017/12/28 05:15:00
uknowjpbitcoinupvoted (100.00%) @sweetwilliam / why-would-anyone-use-bitcoin
2017/12/28 05:15:00
| voter | uknowjpbitcoin |
| author | sweetwilliam |
| permlink | why-would-anyone-use-bitcoin |
| weight | 10000 (100.00%) |
| Transaction Info | Block #18472709/Trx a6295547db5167c0213393b60d7010951b757eb3 |
View Raw JSON Data
{
"trx_id": "a6295547db5167c0213393b60d7010951b757eb3",
"block": 18472709,
"trx_in_block": 10,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-28T05:15:00",
"op": [
"vote",
{
"voter": "uknowjpbitcoin",
"author": "sweetwilliam",
"permlink": "why-would-anyone-use-bitcoin",
"weight": 10000
}
]
}dre87upvoted (100.00%) @sweetwilliam / why-would-anyone-use-bitcoin2017/12/28 03:46:39
dre87upvoted (100.00%) @sweetwilliam / why-would-anyone-use-bitcoin
2017/12/28 03:46:39
| voter | dre87 |
| author | sweetwilliam |
| permlink | why-would-anyone-use-bitcoin |
| weight | 10000 (100.00%) |
| Transaction Info | Block #18470942/Trx 60403a82f05ad6c5bc61af175e60f45b3e671574 |
View Raw JSON Data
{
"trx_id": "60403a82f05ad6c5bc61af175e60f45b3e671574",
"block": 18470942,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-28T03:46:39",
"op": [
"vote",
{
"voter": "dre87",
"author": "sweetwilliam",
"permlink": "why-would-anyone-use-bitcoin",
"weight": 10000
}
]
}usmanjuttupvoted (100.00%) @sweetwilliam / why-would-anyone-use-bitcoin2017/12/27 18:22:36
usmanjuttupvoted (100.00%) @sweetwilliam / why-would-anyone-use-bitcoin
2017/12/27 18:22:36
| voter | usmanjutt |
| author | sweetwilliam |
| permlink | why-would-anyone-use-bitcoin |
| weight | 10000 (100.00%) |
| Transaction Info | Block #18459666/Trx 0bf9a4b850c98bf5c9de95a2e1590d90c46ce137 |
View Raw JSON Data
{
"trx_id": "0bf9a4b850c98bf5c9de95a2e1590d90c46ce137",
"block": 18459666,
"trx_in_block": 48,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-27T18:22:36",
"op": [
"vote",
{
"voter": "usmanjutt",
"author": "sweetwilliam",
"permlink": "why-would-anyone-use-bitcoin",
"weight": 10000
}
]
}abangace99upvoted (100.00%) @sweetwilliam / why-would-anyone-use-bitcoin2017/12/26 18:46:27
abangace99upvoted (100.00%) @sweetwilliam / why-would-anyone-use-bitcoin
2017/12/26 18:46:27
| voter | abangace99 |
| author | sweetwilliam |
| permlink | why-would-anyone-use-bitcoin |
| weight | 10000 (100.00%) |
| Transaction Info | Block #18431348/Trx 5f7a0482a0a1249370bcbae613983b29d9a062f8 |
View Raw JSON Data
{
"trx_id": "5f7a0482a0a1249370bcbae613983b29d9a062f8",
"block": 18431348,
"trx_in_block": 18,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-26T18:46:27",
"op": [
"vote",
{
"voter": "abangace99",
"author": "sweetwilliam",
"permlink": "why-would-anyone-use-bitcoin",
"weight": 10000
}
]
}egtechupvoted (100.00%) @sweetwilliam / why-would-anyone-use-bitcoin2017/12/26 18:45:18
egtechupvoted (100.00%) @sweetwilliam / why-would-anyone-use-bitcoin
2017/12/26 18:45:18
| voter | egtech |
| author | sweetwilliam |
| permlink | why-would-anyone-use-bitcoin |
| weight | 10000 (100.00%) |
| Transaction Info | Block #18431325/Trx 7c91e441d329d2c6354626582e6432825c54d52b |
View Raw JSON Data
{
"trx_id": "7c91e441d329d2c6354626582e6432825c54d52b",
"block": 18431325,
"trx_in_block": 21,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-26T18:45:18",
"op": [
"vote",
{
"voter": "egtech",
"author": "sweetwilliam",
"permlink": "why-would-anyone-use-bitcoin",
"weight": 10000
}
]
}paappaupvoted (100.00%) @sweetwilliam / why-would-anyone-use-bitcoin2017/12/26 15:02:09
paappaupvoted (100.00%) @sweetwilliam / why-would-anyone-use-bitcoin
2017/12/26 15:02:09
| voter | paappa |
| author | sweetwilliam |
| permlink | why-would-anyone-use-bitcoin |
| weight | 10000 (100.00%) |
| Transaction Info | Block #18426865/Trx b1e58c973fb6de4eadd53d0ebd239242f9199684 |
View Raw JSON Data
{
"trx_id": "b1e58c973fb6de4eadd53d0ebd239242f9199684",
"block": 18426865,
"trx_in_block": 50,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-26T15:02:09",
"op": [
"vote",
{
"voter": "paappa",
"author": "sweetwilliam",
"permlink": "why-would-anyone-use-bitcoin",
"weight": 10000
}
]
}beld0nupvoted (100.00%) @sweetwilliam / why-would-anyone-use-bitcoin2017/12/26 10:18:15
beld0nupvoted (100.00%) @sweetwilliam / why-would-anyone-use-bitcoin
2017/12/26 10:18:15
| voter | beld0n |
| author | sweetwilliam |
| permlink | why-would-anyone-use-bitcoin |
| weight | 10000 (100.00%) |
| Transaction Info | Block #18421189/Trx e79fce3ce84d8dba83312987621b67b05cd9d62a |
View Raw JSON Data
{
"trx_id": "e79fce3ce84d8dba83312987621b67b05cd9d62a",
"block": 18421189,
"trx_in_block": 34,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-26T10:18:15",
"op": [
"vote",
{
"voter": "beld0n",
"author": "sweetwilliam",
"permlink": "why-would-anyone-use-bitcoin",
"weight": 10000
}
]
}rajivkhanupvoted (100.00%) @sweetwilliam / why-would-anyone-use-bitcoin2017/12/26 06:42:12
rajivkhanupvoted (100.00%) @sweetwilliam / why-would-anyone-use-bitcoin
2017/12/26 06:42:12
| voter | rajivkhan |
| author | sweetwilliam |
| permlink | why-would-anyone-use-bitcoin |
| weight | 10000 (100.00%) |
| Transaction Info | Block #18416871/Trx bb4182114084ebba858cd12e5c4b3a714e302686 |
View Raw JSON Data
{
"trx_id": "bb4182114084ebba858cd12e5c4b3a714e302686",
"block": 18416871,
"trx_in_block": 30,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-26T06:42:12",
"op": [
"vote",
{
"voter": "rajivkhan",
"author": "sweetwilliam",
"permlink": "why-would-anyone-use-bitcoin",
"weight": 10000
}
]
}2017/12/25 14:57:12
2017/12/25 14:57:12
| voter | sweetwilliam |
| author | wesleybos |
| permlink | re-sweetwilliam-why-would-anyone-use-bitcoin-20171225t132055228z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #18397998/Trx ef5065023c102986096a1c0b22805ce809fcb9e4 |
View Raw JSON Data
{
"trx_id": "ef5065023c102986096a1c0b22805ce809fcb9e4",
"block": 18397998,
"trx_in_block": 47,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-25T14:57:12",
"op": [
"vote",
{
"voter": "sweetwilliam",
"author": "wesleybos",
"permlink": "re-sweetwilliam-why-would-anyone-use-bitcoin-20171225t132055228z",
"weight": 10000
}
]
}2017/12/25 13:20:54
2017/12/25 13:20:54
| parent author | sweetwilliam |
| parent permlink | why-would-anyone-use-bitcoin |
| author | wesleybos |
| permlink | re-sweetwilliam-why-would-anyone-use-bitcoin-20171225t132055228z |
| title | |
| body | Very interesting read, I have never thought of it like this before. Thanks a lot for sharing! |
| json metadata | {"tags":["bitcoin"],"app":"steemit/0.1"} |
| Transaction Info | Block #18396075/Trx 76b10022bd6fbd5c3a1a4e891e6cd0f673d16ee8 |
View Raw JSON Data
{
"trx_id": "76b10022bd6fbd5c3a1a4e891e6cd0f673d16ee8",
"block": 18396075,
"trx_in_block": 24,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-25T13:20:54",
"op": [
"comment",
{
"parent_author": "sweetwilliam",
"parent_permlink": "why-would-anyone-use-bitcoin",
"author": "wesleybos",
"permlink": "re-sweetwilliam-why-would-anyone-use-bitcoin-20171225t132055228z",
"title": "",
"body": "Very interesting read, I have never thought of it like this before. Thanks a lot for sharing!",
"json_metadata": "{\"tags\":[\"bitcoin\"],\"app\":\"steemit/0.1\"}"
}
]
}wesleybosupvoted (50.00%) @sweetwilliam / why-would-anyone-use-bitcoin2017/12/25 13:20:30
wesleybosupvoted (50.00%) @sweetwilliam / why-would-anyone-use-bitcoin
2017/12/25 13:20:30
| voter | wesleybos |
| author | sweetwilliam |
| permlink | why-would-anyone-use-bitcoin |
| weight | 5000 (50.00%) |
| Transaction Info | Block #18396067/Trx 7ea881495e0bcdfa19f18e543be2f9e076cfc746 |
View Raw JSON Data
{
"trx_id": "7ea881495e0bcdfa19f18e543be2f9e076cfc746",
"block": 18396067,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-25T13:20:30",
"op": [
"vote",
{
"voter": "wesleybos",
"author": "sweetwilliam",
"permlink": "why-would-anyone-use-bitcoin",
"weight": 5000
}
]
}cofriupvoted (100.00%) @sweetwilliam / why-would-anyone-use-bitcoin2017/12/25 11:21:00
cofriupvoted (100.00%) @sweetwilliam / why-would-anyone-use-bitcoin
2017/12/25 11:21:00
| voter | cofri |
| author | sweetwilliam |
| permlink | why-would-anyone-use-bitcoin |
| weight | 10000 (100.00%) |
| Transaction Info | Block #18393681/Trx a04a0531c6fcc3064e0ad0e8506ae0094ae3b547 |
View Raw JSON Data
{
"trx_id": "a04a0531c6fcc3064e0ad0e8506ae0094ae3b547",
"block": 18393681,
"trx_in_block": 11,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-25T11:21:00",
"op": [
"vote",
{
"voter": "cofri",
"author": "sweetwilliam",
"permlink": "why-would-anyone-use-bitcoin",
"weight": 10000
}
]
}hakan0356upvoted (100.00%) @sweetwilliam / why-would-anyone-use-bitcoin2017/12/25 10:07:51
hakan0356upvoted (100.00%) @sweetwilliam / why-would-anyone-use-bitcoin
2017/12/25 10:07:51
| voter | hakan0356 |
| author | sweetwilliam |
| permlink | why-would-anyone-use-bitcoin |
| weight | 10000 (100.00%) |
| Transaction Info | Block #18392220/Trx 543ae09a56b1a37b133105f47682ff0b1ea3ece9 |
View Raw JSON Data
{
"trx_id": "543ae09a56b1a37b133105f47682ff0b1ea3ece9",
"block": 18392220,
"trx_in_block": 9,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-25T10:07:51",
"op": [
"vote",
{
"voter": "hakan0356",
"author": "sweetwilliam",
"permlink": "why-would-anyone-use-bitcoin",
"weight": 10000
}
]
}2017/12/25 06:53:24
2017/12/25 06:53:24
| parent author | sweetwilliam |
| parent permlink | re-inthearena-bitcoin-s-lightning-network-what-is-it-and-how-to-test-it-20171224t191326605z |
| author | inthearena |
| permlink | re-sweetwilliam-re-inthearena-bitcoin-s-lightning-network-what-is-it-and-how-to-test-it-20171224t223409420z |
| title | |
| body | @@ -1119,17 +1119,17 @@ . Before -%0A + this tra @@ -1216,17 +1216,17 @@ posit to -%0A + both par |
| json metadata | {"tags":["bitcoin"],"links":["https://lightning.network/lightning-network-summary.pdf","https://lightning.network/lightning-network-technical-summary.pdf"],"app":"steemit/0.1"} |
| Transaction Info | Block #18388337/Trx 9d7339b03128c307e2f5413e506282ac4c7da745 |
View Raw JSON Data
{
"trx_id": "9d7339b03128c307e2f5413e506282ac4c7da745",
"block": 18388337,
"trx_in_block": 10,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-25T06:53:24",
"op": [
"comment",
{
"parent_author": "sweetwilliam",
"parent_permlink": "re-inthearena-bitcoin-s-lightning-network-what-is-it-and-how-to-test-it-20171224t191326605z",
"author": "inthearena",
"permlink": "re-sweetwilliam-re-inthearena-bitcoin-s-lightning-network-what-is-it-and-how-to-test-it-20171224t223409420z",
"title": "",
"body": "@@ -1119,17 +1119,17 @@\n . Before\n-%0A\n+ \n this tra\n@@ -1216,17 +1216,17 @@\n posit to\n-%0A\n+ \n both par\n",
"json_metadata": "{\"tags\":[\"bitcoin\"],\"links\":[\"https://lightning.network/lightning-network-summary.pdf\",\"https://lightning.network/lightning-network-technical-summary.pdf\"],\"app\":\"steemit/0.1\"}"
}
]
}alexurso13upvoted (100.00%) @sweetwilliam / why-would-anyone-use-bitcoin2017/12/25 04:10:57
alexurso13upvoted (100.00%) @sweetwilliam / why-would-anyone-use-bitcoin
2017/12/25 04:10:57
| voter | alexurso13 |
| author | sweetwilliam |
| permlink | why-would-anyone-use-bitcoin |
| weight | 10000 (100.00%) |
| Transaction Info | Block #18385093/Trx 7764cb563a22b654c1457f889b3535a4add96584 |
View Raw JSON Data
{
"trx_id": "7764cb563a22b654c1457f889b3535a4add96584",
"block": 18385093,
"trx_in_block": 17,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-25T04:10:57",
"op": [
"vote",
{
"voter": "alexurso13",
"author": "sweetwilliam",
"permlink": "why-would-anyone-use-bitcoin",
"weight": 10000
}
]
}2017/12/24 22:34:09
2017/12/24 22:34:09
| parent author | sweetwilliam |
| parent permlink | re-inthearena-bitcoin-s-lightning-network-what-is-it-and-how-to-test-it-20171224t191326605z |
| author | inthearena |
| permlink | re-sweetwilliam-re-inthearena-bitcoin-s-lightning-network-what-is-it-and-how-to-test-it-20171224t223409420z |
| title | |
| body | Hi Sweetwilliam, It's a really good (and interesting) question. Essentially you are correct. The funds are set aside in some form of holding account - similar to the way a checking account is separate from a savings account. The two parties send one on chain transaction into a "multi-signature address". The balance between the two parties is sorted out at a later date. A general summary of how this works is found [here](https://lightning.network/lightning-network-summary.pdf) >Funds are placed into a two-party, multisignature "channel" bitcoin address. This channel is represented as an entry on the bitcoin public ledger. In order to spend funds from the channel, both parties must agree on the new balance. The more technical/specific explanation of how it works is [here](https://lightning.network/lightning-network-technical-summary.pdf) >Two parties send an initial amount of Bitcoin into a multisignature transaction with a local consensus on the current balance allocated between the two participants. > One onblockchain transaction is made to deposit the funds into a multisignature output. Before this transaction is made, a refund transaction is created, which returns the original deposit to both parties.... In effect, they have created numerous "double spends" from an onblockchain transaction, but have elected not to broadcast the spend until either party wants to redeem their funds onchain. |
| json metadata | {"tags":["bitcoin"],"links":["https://lightning.network/lightning-network-summary.pdf","https://lightning.network/lightning-network-technical-summary.pdf"],"app":"steemit/0.1"} |
| Transaction Info | Block #18378358/Trx 0a85c99b7bc0399c9f3209ba44c387e991c76d9a |
View Raw JSON Data
{
"trx_id": "0a85c99b7bc0399c9f3209ba44c387e991c76d9a",
"block": 18378358,
"trx_in_block": 31,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-24T22:34:09",
"op": [
"comment",
{
"parent_author": "sweetwilliam",
"parent_permlink": "re-inthearena-bitcoin-s-lightning-network-what-is-it-and-how-to-test-it-20171224t191326605z",
"author": "inthearena",
"permlink": "re-sweetwilliam-re-inthearena-bitcoin-s-lightning-network-what-is-it-and-how-to-test-it-20171224t223409420z",
"title": "",
"body": "Hi Sweetwilliam,\n\nIt's a really good (and interesting) question. Essentially you are correct. The funds are set aside in some form of holding account - similar to the way a checking account is separate from a savings account. \n\nThe two parties send one on chain transaction into a \"multi-signature address\". The balance between the two parties is sorted out at a later date. \n\nA general summary of how this works is found [here](https://lightning.network/lightning-network-summary.pdf)\n\n>Funds are placed into a two-party, multisignature \"channel\" bitcoin address. This channel is represented as an entry on the bitcoin public ledger. In order to spend funds from the channel, both parties must agree on the new balance. \n\nThe more technical/specific explanation of how it works is [here](https://lightning.network/lightning-network-technical-summary.pdf)\n \n>Two parties send an initial amount of Bitcoin into a multisignature transaction with a local consensus on the current balance allocated between the two participants. \n\n> One onblockchain transaction is made to deposit the funds into a multisignature output. Before\nthis transaction is made, a refund transaction is created, which returns the original deposit to\nboth parties.... In effect, they have created numerous \"double spends\" from an onblockchain transaction, but have elected not to broadcast the spend until either party wants to redeem their funds onchain.",
"json_metadata": "{\"tags\":[\"bitcoin\"],\"links\":[\"https://lightning.network/lightning-network-summary.pdf\",\"https://lightning.network/lightning-network-technical-summary.pdf\"],\"app\":\"steemit/0.1\"}"
}
]
}2017/12/24 22:00:18
2017/12/24 22:00:18
| voter | inthearena |
| author | sweetwilliam |
| permlink | re-inthearena-bitcoin-s-lightning-network-what-is-it-and-how-to-test-it-20171224t191326605z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #18377681/Trx 893076597173392e55c0aca0ed3fe7e5e7b14adb |
View Raw JSON Data
{
"trx_id": "893076597173392e55c0aca0ed3fe7e5e7b14adb",
"block": 18377681,
"trx_in_block": 42,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-24T22:00:18",
"op": [
"vote",
{
"voter": "inthearena",
"author": "sweetwilliam",
"permlink": "re-inthearena-bitcoin-s-lightning-network-what-is-it-and-how-to-test-it-20171224t191326605z",
"weight": 10000
}
]
}skytroniaupvoted (100.00%) @sweetwilliam / why-would-anyone-use-bitcoin2017/12/24 21:21:39
skytroniaupvoted (100.00%) @sweetwilliam / why-would-anyone-use-bitcoin
2017/12/24 21:21:39
| voter | skytronia |
| author | sweetwilliam |
| permlink | why-would-anyone-use-bitcoin |
| weight | 10000 (100.00%) |
| Transaction Info | Block #18376909/Trx e7cf3b21651cf3fc246503d7b65e98b3bced654f |
View Raw JSON Data
{
"trx_id": "e7cf3b21651cf3fc246503d7b65e98b3bced654f",
"block": 18376909,
"trx_in_block": 18,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-24T21:21:39",
"op": [
"vote",
{
"voter": "skytronia",
"author": "sweetwilliam",
"permlink": "why-would-anyone-use-bitcoin",
"weight": 10000
}
]
}sweetwilliamupvoted (100.00%) @borderedge / places-you-should-visit-part-3-agdz-morocco2017/12/24 19:42:39
sweetwilliamupvoted (100.00%) @borderedge / places-you-should-visit-part-3-agdz-morocco
2017/12/24 19:42:39
| voter | sweetwilliam |
| author | borderedge |
| permlink | places-you-should-visit-part-3-agdz-morocco |
| weight | 10000 (100.00%) |
| Transaction Info | Block #18374930/Trx b08050ab64a0d1098c8e662c70b4725e41ac3ce7 |
View Raw JSON Data
{
"trx_id": "b08050ab64a0d1098c8e662c70b4725e41ac3ce7",
"block": 18374930,
"trx_in_block": 44,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-24T19:42:39",
"op": [
"vote",
{
"voter": "sweetwilliam",
"author": "borderedge",
"permlink": "places-you-should-visit-part-3-agdz-morocco",
"weight": 10000
}
]
}sweetwilliamupvoted (100.00%) @imadbisdaoune / tourism-in-morocco2017/12/24 19:38:12
sweetwilliamupvoted (100.00%) @imadbisdaoune / tourism-in-morocco
2017/12/24 19:38:12
| voter | sweetwilliam |
| author | imadbisdaoune |
| permlink | tourism-in-morocco |
| weight | 10000 (100.00%) |
| Transaction Info | Block #18374841/Trx b79d656c875fdd495c1c658562479190882d83b8 |
View Raw JSON Data
{
"trx_id": "b79d656c875fdd495c1c658562479190882d83b8",
"block": 18374841,
"trx_in_block": 9,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-24T19:38:12",
"op": [
"vote",
{
"voter": "sweetwilliam",
"author": "imadbisdaoune",
"permlink": "tourism-in-morocco",
"weight": 10000
}
]
}quennofandalsupvoted (100.00%) @sweetwilliam / why-would-anyone-use-bitcoin2017/12/24 19:15:30
quennofandalsupvoted (100.00%) @sweetwilliam / why-would-anyone-use-bitcoin
2017/12/24 19:15:30
| voter | quennofandals |
| author | sweetwilliam |
| permlink | why-would-anyone-use-bitcoin |
| weight | 10000 (100.00%) |
| Transaction Info | Block #18374387/Trx e31e4ff77a91859d00abf69c9694ff17709173fc |
View Raw JSON Data
{
"trx_id": "e31e4ff77a91859d00abf69c9694ff17709173fc",
"block": 18374387,
"trx_in_block": 28,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-24T19:15:30",
"op": [
"vote",
{
"voter": "quennofandals",
"author": "sweetwilliam",
"permlink": "why-would-anyone-use-bitcoin",
"weight": 10000
}
]
}ceyksparrowupvoted (100.00%) @sweetwilliam / why-would-anyone-use-bitcoin2017/12/24 19:14:12
ceyksparrowupvoted (100.00%) @sweetwilliam / why-would-anyone-use-bitcoin
2017/12/24 19:14:12
| voter | ceyksparrow |
| author | sweetwilliam |
| permlink | why-would-anyone-use-bitcoin |
| weight | 10000 (100.00%) |
| Transaction Info | Block #18374361/Trx 229ba7fdb53a963bbf28da0f73db50826c97f2c6 |
View Raw JSON Data
{
"trx_id": "229ba7fdb53a963bbf28da0f73db50826c97f2c6",
"block": 18374361,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-12-24T19:14:12",
"op": [
"vote",
{
"voter": "ceyksparrow",
"author": "sweetwilliam",
"permlink": "why-would-anyone-use-bitcoin",
"weight": 10000
}
]
}Manabar
Voting Power100.00%
Downvote Power100.00%
Resource Credits100.00%
Reputation Progress23.64%
{
"voting_manabar": {
"current_mana": "13198167288",
"last_update_time": 1588954767
},
"downvote_manabar": {
"current_mana": 3299541822,
"last_update_time": 1588954767
},
"rc_account": {
"account": "sweetwilliam",
"rc_manabar": {
"current_mana": "17238252579",
"last_update_time": 1588954767
},
"max_rc_creation_adjustment": {
"amount": "2020748973",
"precision": 6,
"nai": "@@000000037"
},
"max_rc": "15218916261"
}
}Account Metadata
| POSTING JSON METADATA | |
| profile | {"location":"Planet Earth","about":"alien, crypto enthusiast, vipassana meditator","profile_image":"https://s1.postimg.org/4u0w6z63db/profile6.jpg","cover_image":"https://s1.postimg.org/8wdwalrwxr/cover11.jpg"} |
| JSON METADATA | |
| profile | {"location":"Planet Earth","about":"alien, crypto enthusiast, vipassana meditator","profile_image":"https://s1.postimg.org/4u0w6z63db/profile6.jpg","cover_image":"https://s1.postimg.org/8wdwalrwxr/cover11.jpg"} |
{
"posting_json_metadata": {
"profile": {
"location": "Planet Earth",
"about": "alien, crypto enthusiast, vipassana meditator",
"profile_image": "https://s1.postimg.org/4u0w6z63db/profile6.jpg",
"cover_image": "https://s1.postimg.org/8wdwalrwxr/cover11.jpg"
}
},
"json_metadata": {
"profile": {
"location": "Planet Earth",
"about": "alien, crypto enthusiast, vipassana meditator",
"profile_image": "https://s1.postimg.org/4u0w6z63db/profile6.jpg",
"cover_image": "https://s1.postimg.org/8wdwalrwxr/cover11.jpg"
}
}
}Auth Keys
Owner
Single Signature
Public Keys
STM5DKurwofXtEMzrRyBppLW4BZNBqmz1WHjriqHsjFqpeg4dgvCJ1/1
Active
Single Signature
Public Keys
STM6K4qMtvkEswM5ZtuU43PuKqfc7kDMdpZ6YQyaFeoyzu4kcgU6P1/1
Posting
Single Signature
Public Keys
STM7TScX1JAr93Dr6xLyczvDbBZYhgujK7Gd1YQ68CFrem17ZWzV51/1
Memo
STM5bVSmKzPAHHQF4EL1VEKJjUazHDoyS2VetoodcHZpfbWWbtbz7
{
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM5DKurwofXtEMzrRyBppLW4BZNBqmz1WHjriqHsjFqpeg4dgvCJ",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM6K4qMtvkEswM5ZtuU43PuKqfc7kDMdpZ6YQyaFeoyzu4kcgU6P",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7TScX1JAr93Dr6xLyczvDbBZYhgujK7Gd1YQ68CFrem17ZWzV5",
1
]
]
},
"memo": "STM5bVSmKzPAHHQF4EL1VEKJjUazHDoyS2VetoodcHZpfbWWbtbz7"
}Witness Votes
0 / 30
No active witness votes.
[]