VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS86.98%
Net Worth
6.889USD
STEEM
38.849STEEM
SBD
2.351SBD
Own SP
67.059SP
Detailed Balance
| STEEM | ||
| balance | 38.849STEEM | STEEM |
| market_balance | 0.000STEEM | STEEM |
| savings_balance | 0.000STEEM | STEEM |
| reward_steem_balance | 0.000STEEM | STEEM |
| STEEM POWER | ||
| Own SP | 67.059SP | SP |
| Delegated Out | 0.000SP | SP |
| Delegation In | 0.000SP | SP |
| Effective Power | 67.059SP | SP |
| Reward SP (pending) | 0.575SP | SP |
| SBD | ||
| sbd_balance | 2.239SBD | SBD |
| sbd_conversions | 0.000SBD | SBD |
| sbd_market_balance | 0.000SBD | SBD |
| savings_sbd_balance | 0.000SBD | SBD |
| reward_sbd_balance | 0.112SBD | SBD |
{
"balance": "38.849 STEEM",
"savings_balance": "0.000 STEEM",
"reward_steem_balance": "0.000 STEEM",
"vesting_shares": "109199.642474 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "0.000000 VESTS",
"sbd_balance": "2.239 SBD",
"savings_sbd_balance": "0.000 SBD",
"reward_sbd_balance": "0.112 SBD",
"conversions": []
}Account Info
| name | bitgoldwallet |
| id | 299548 |
| rank | 26,805 |
| reputation | 74888984543 |
| created | 2017-08-05T04:05:21 |
| recovery_account | anonsteem |
| proxy | None |
| post_count | 11 |
| comment_count | 0 |
| lifetime_vote_count | 0 |
| witnesses_voted_for | 0 |
| last_post | 2020-04-24T02:36:45 |
| last_root_post | 2020-04-24T02:36:45 |
| last_vote_time | 2020-04-24T03:12:09 |
| proxied_vsf_votes | 0, 0, 0, 0 |
| can_vote | 1 |
| voting_power | 9,799 |
| delayed_votes | 0 |
| balance | 38.849 STEEM |
| savings_balance | 0.000 STEEM |
| sbd_balance | 2.239 SBD |
| savings_sbd_balance | 0.000 SBD |
| vesting_shares | 109199.642474 VESTS |
| delegated_vesting_shares | 0.000000 VESTS |
| received_vesting_shares | 0.000000 VESTS |
| reward_vesting_balance | 1123.659095 VESTS |
| vesting_balance | 0.000 STEEM |
| vesting_withdraw_rate | 0.000000 VESTS |
| next_vesting_withdrawal | 1969-12-31T23:59:59 |
| withdrawn | 100870504109 |
| to_withdraw | 100870504109 |
| withdraw_routes | 0 |
| savings_withdraw_requests | 0 |
| last_account_recovery | 1970-01-01T00:00:00 |
| reset_account | null |
| last_owner_update | 2017-09-08T01:05:24 |
| last_account_update | 2018-03-18T06:07:45 |
| mined | No |
| sbd_seconds | 0 |
| sbd_last_interest_payment | 2020-04-24T02:27:27 |
| savings_sbd_last_interest_payment | 1970-01-01T00:00:00 |
{
"id": 299548,
"name": "bitgoldwallet",
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7d1xDZ2yEPG7WLLCmJjjiMKfcVHqtK8s8chyyagy3KQyjn4qn7",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM6qxaAUAsCXLPv2F8ad7tdqBX2LFMTetQEqMbWguC16uvSvpN8R",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7k5BtZYdg63bTLwhvN3GZT6w7sLz69rTPqthGgAmw2pNJsPH1u",
1
]
]
},
"memo_key": "STM5t2U1TnHxxyhyTUHZpCKpZdt2S1coRHyPorhdMTBsHTMSadCg8",
"json_metadata": "{\"profile\":{\"name\":\"Bitgoldwallet\",\"profile_image\":\"https://s17.postimg.org/6bvt29mxr/ultra_high_res_-_small_square.jpg\"}}",
"posting_json_metadata": "{\"profile\":{\"name\":\"Bitgoldwallet\",\"profile_image\":\"https://s17.postimg.org/6bvt29mxr/ultra_high_res_-_small_square.jpg\"}}",
"proxy": "",
"last_owner_update": "2017-09-08T01:05:24",
"last_account_update": "2018-03-18T06:07:45",
"created": "2017-08-05T04:05:21",
"mined": false,
"recovery_account": "anonsteem",
"last_account_recovery": "1970-01-01T00:00:00",
"reset_account": "null",
"comment_count": 0,
"lifetime_vote_count": 0,
"post_count": 11,
"can_vote": true,
"voting_manabar": {
"current_mana": "107015649624",
"last_update_time": 1587697929
},
"downvote_manabar": {
"current_mana": "27299910618",
"last_update_time": 1587697929
},
"voting_power": 9799,
"balance": "38.849 STEEM",
"savings_balance": "0.000 STEEM",
"sbd_balance": "2.239 SBD",
"sbd_seconds": "0",
"sbd_seconds_last_update": "2020-04-24T02:27:27",
"sbd_last_interest_payment": "2020-04-24T02:27:27",
"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.112 SBD",
"reward_steem_balance": "0.000 STEEM",
"reward_vesting_balance": "1123.659095 VESTS",
"reward_vesting_steem": "0.575 STEEM",
"vesting_shares": "109199.642474 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": "100870504109",
"to_withdraw": "100870504109",
"withdraw_routes": 0,
"curation_rewards": 1,
"posting_rewards": 4694,
"proxied_vsf_votes": [
0,
0,
0,
0
],
"witnesses_voted_for": 0,
"last_post": "2020-04-24T02:36:45",
"last_root_post": "2020-04-24T02:36:45",
"last_vote_time": "2020-04-24T03:12:09",
"post_bandwidth": 0,
"pending_claimed_accounts": 0,
"vesting_balance": "0.000 STEEM",
"reputation": "74888984543",
"transfer_history": [],
"market_history": [],
"post_history": [],
"vote_history": [],
"other_history": [],
"witness_votes": [],
"tags_usage": [],
"guest_bloggers": [],
"rank": 26805
}Withdraw Routes
| Incoming | Outgoing |
|---|---|
Empty | Empty |
{
"incoming": [],
"outgoing": []
}From Date
To Date
blurtofficialsent 0.001 STEEM to @bitgoldwallet- "CONGRATS! You have a 1:1 BLURT AIRDROP of 52.484 BLURT and 55.946000 BLURT POWER waiting for you. Check out https://blurtwallet.com/@bitgoldwallet and https://blurt.blog/ TODAY!"2020/12/15 21:41:39
blurtofficialsent 0.001 STEEM to @bitgoldwallet- "CONGRATS! You have a 1:1 BLURT AIRDROP of 52.484 BLURT and 55.946000 BLURT POWER waiting for you. Check out https://blurtwallet.com/@bitgoldwallet and https://blurt.blog/ TODAY!"
2020/12/15 21:41:39
| from | blurtofficial |
| to | bitgoldwallet |
| amount | 0.001 STEEM |
| memo | CONGRATS! You have a 1:1 BLURT AIRDROP of 52.484 BLURT and 55.946000 BLURT POWER waiting for you. Check out https://blurtwallet.com/@bitgoldwallet and https://blurt.blog/ TODAY! |
| Transaction Info | Block #49480755/Trx 486180d1958d8a8b9770eaf9a38a5cb079a72277 |
View Raw JSON Data
{
"trx_id": "486180d1958d8a8b9770eaf9a38a5cb079a72277",
"block": 49480755,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-12-15T21:41:39",
"op": [
"transfer",
{
"from": "blurtofficial",
"to": "bitgoldwallet",
"amount": "0.001 STEEM",
"memo": "CONGRATS! You have a 1:1 BLURT AIRDROP of 52.484 BLURT and 55.946000 BLURT POWER waiting for you. Check out https://blurtwallet.com/@bitgoldwallet and https://blurt.blog/ TODAY!"
}
]
}crypto.piotrsent 0.002 STEEM to @bitgoldwallet- "Dear @bitgoldwallet, I hope you don't mind this little memo. I would like to introduce you to new "LEARN AND EARN" initiative which I came up together with @hardaeborla. Check out my latest post and h..."2020/05/14 15:38:48
crypto.piotrsent 0.002 STEEM to @bitgoldwallet- "Dear @bitgoldwallet, I hope you don't mind this little memo. I would like to introduce you to new "LEARN AND EARN" initiative which I came up together with @hardaeborla. Check out my latest post and h..."
2020/05/14 15:38:48
| from | crypto.piotr |
| to | bitgoldwallet |
| amount | 0.002 STEEM |
| memo | Dear @bitgoldwallet, I hope you don't mind this little memo. I would like to introduce you to new "LEARN AND EARN" initiative which I came up together with @hardaeborla. Check out my latest post and hopefully you will enjoy our new idea. Obviously I would appreciate every resteem and your feedback. I read all comments. Yours, Piotr // LINK: https://steemit.com/hive-175254/@crypto.piotr/learn-and-earn-our-project-hope-new-awesome-initiative |
| Transaction Info | Block #43369387/Trx 8ac019e7e980af2990e5c7121dd915ab138da682 |
View Raw JSON Data
{
"trx_id": "8ac019e7e980af2990e5c7121dd915ab138da682",
"block": 43369387,
"trx_in_block": 17,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-05-14T15:38:48",
"op": [
"transfer",
{
"from": "crypto.piotr",
"to": "bitgoldwallet",
"amount": "0.002 STEEM",
"memo": "Dear @bitgoldwallet, I hope you don't mind this little memo. I would like to introduce you to new \"LEARN AND EARN\" initiative which I came up together with @hardaeborla. Check out my latest post and hopefully you will enjoy our new idea. Obviously I would appreciate every resteem and your feedback. I read all comments. Yours, Piotr // LINK: https://steemit.com/hive-175254/@crypto.piotr/learn-and-earn-our-project-hope-new-awesome-initiative"
}
]
}bitgoldwalletreceived 0.112 SBD, 0.689 SP author reward for @bitgoldwallet / bitcoin-a-simple-explanation2020/05/01 02:36:45
bitgoldwalletreceived 0.112 SBD, 0.689 SP author reward for @bitgoldwallet / bitcoin-a-simple-explanation
2020/05/01 02:36:45
| author | bitgoldwallet |
| permlink | bitcoin-a-simple-explanation |
| sbd payout | 0.112 SBD |
| steem payout | 0.000 STEEM |
| vesting payout | 1121.704906 VESTS |
| Transaction Info | Block #42988570/Virtual Operation #19 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 42988570,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 19,
"timestamp": "2020-05-01T02:36:45",
"op": [
"author_reward",
{
"author": "bitgoldwallet",
"permlink": "bitcoin-a-simple-explanation",
"sbd_payout": "0.112 SBD",
"steem_payout": "0.000 STEEM",
"vesting_payout": "1121.704906 VESTS"
}
]
}bitgoldwalletreceived 0.001 SP curation reward for @bitgoldwallet / bitcoin-a-simple-explanation2020/05/01 02:36:45
bitgoldwalletreceived 0.001 SP curation reward for @bitgoldwallet / bitcoin-a-simple-explanation
2020/05/01 02:36:45
| curator | bitgoldwallet |
| reward | 1.954189 VESTS |
| comment author | bitgoldwallet |
| comment permlink | bitcoin-a-simple-explanation |
| Transaction Info | Block #42988570/Virtual Operation #12 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 42988570,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 12,
"timestamp": "2020-05-01T02:36:45",
"op": [
"curation_reward",
{
"curator": "bitgoldwallet",
"reward": "1.954189 VESTS",
"comment_author": "bitgoldwallet",
"comment_permlink": "bitcoin-a-simple-explanation"
}
]
}phasewalkerupvoted (1.00%) @bitgoldwallet / bitcoin-a-simple-explanation2020/04/27 17:40:45
phasewalkerupvoted (1.00%) @bitgoldwallet / bitcoin-a-simple-explanation
2020/04/27 17:40:45
| voter | phasewalker |
| author | bitgoldwallet |
| permlink | bitcoin-a-simple-explanation |
| weight | 100 (1.00%) |
| Transaction Info | Block #42893886/Trx 621179d533933d099b7d685f07e3a121c2c4a7c0 |
View Raw JSON Data
{
"trx_id": "621179d533933d099b7d685f07e3a121c2c4a7c0",
"block": 42893886,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-27T17:40:45",
"op": [
"vote",
{
"voter": "phasewalker",
"author": "bitgoldwallet",
"permlink": "bitcoin-a-simple-explanation",
"weight": 100
}
]
}m1alsanupvoted (100.00%) @bitgoldwallet / bitcoin-a-simple-explanation2020/04/27 09:00:39
m1alsanupvoted (100.00%) @bitgoldwallet / bitcoin-a-simple-explanation
2020/04/27 09:00:39
| voter | m1alsan |
| author | bitgoldwallet |
| permlink | bitcoin-a-simple-explanation |
| weight | 10000 (100.00%) |
| Transaction Info | Block #42883749/Trx d656de95f14a6aef8447ffc1ded249fbf08aa974 |
View Raw JSON Data
{
"trx_id": "d656de95f14a6aef8447ffc1ded249fbf08aa974",
"block": 42883749,
"trx_in_block": 14,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-27T09:00:39",
"op": [
"vote",
{
"voter": "m1alsan",
"author": "bitgoldwallet",
"permlink": "bitcoin-a-simple-explanation",
"weight": 10000
}
]
}dedeleymanupvoted (85.00%) @bitgoldwallet / bitcoin-a-simple-explanation2020/04/27 08:55:42
dedeleymanupvoted (85.00%) @bitgoldwallet / bitcoin-a-simple-explanation
2020/04/27 08:55:42
| voter | dedeleyman |
| author | bitgoldwallet |
| permlink | bitcoin-a-simple-explanation |
| weight | 8500 (85.00%) |
| Transaction Info | Block #42883652/Trx 8c30a63348b1610d2200675cfac179915ea4d43d |
View Raw JSON Data
{
"trx_id": "8c30a63348b1610d2200675cfac179915ea4d43d",
"block": 42883652,
"trx_in_block": 23,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-27T08:55:42",
"op": [
"vote",
{
"voter": "dedeleyman",
"author": "bitgoldwallet",
"permlink": "bitcoin-a-simple-explanation",
"weight": 8500
}
]
}bim.scoutingupvoted (100.00%) @bitgoldwallet / bitcoin-a-simple-explanation2020/04/27 08:51:39
bim.scoutingupvoted (100.00%) @bitgoldwallet / bitcoin-a-simple-explanation
2020/04/27 08:51:39
| voter | bim.scouting |
| author | bitgoldwallet |
| permlink | bitcoin-a-simple-explanation |
| weight | 10000 (100.00%) |
| Transaction Info | Block #42883572/Trx 283471a6cb6bc117aace39e8197fa2e395986e7d |
View Raw JSON Data
{
"trx_id": "283471a6cb6bc117aace39e8197fa2e395986e7d",
"block": 42883572,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-27T08:51:39",
"op": [
"vote",
{
"voter": "bim.scouting",
"author": "bitgoldwallet",
"permlink": "bitcoin-a-simple-explanation",
"weight": 10000
}
]
}afifaupvoted (20.00%) @bitgoldwallet / bitcoin-a-simple-explanation2020/04/27 08:50:39
afifaupvoted (20.00%) @bitgoldwallet / bitcoin-a-simple-explanation
2020/04/27 08:50:39
| voter | afifa |
| author | bitgoldwallet |
| permlink | bitcoin-a-simple-explanation |
| weight | 2000 (20.00%) |
| Transaction Info | Block #42883553/Trx 6cf71e487963d76667af4699bda4973a6e15710c |
View Raw JSON Data
{
"trx_id": "6cf71e487963d76667af4699bda4973a6e15710c",
"block": 42883553,
"trx_in_block": 10,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-27T08:50:39",
"op": [
"vote",
{
"voter": "afifa",
"author": "bitgoldwallet",
"permlink": "bitcoin-a-simple-explanation",
"weight": 2000
}
]
}pat9upvoted (100.00%) @bitgoldwallet / bitcoin-a-simple-explanation2020/04/27 08:45:39
pat9upvoted (100.00%) @bitgoldwallet / bitcoin-a-simple-explanation
2020/04/27 08:45:39
| voter | pat9 |
| author | bitgoldwallet |
| permlink | bitcoin-a-simple-explanation |
| weight | 10000 (100.00%) |
| Transaction Info | Block #42883455/Trx 23a103a8ae09da23e02a0dcc5cee93b622e89e7b |
View Raw JSON Data
{
"trx_id": "23a103a8ae09da23e02a0dcc5cee93b622e89e7b",
"block": 42883455,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-27T08:45:39",
"op": [
"vote",
{
"voter": "pat9",
"author": "bitgoldwallet",
"permlink": "bitcoin-a-simple-explanation",
"weight": 10000
}
]
}nigerian-yogagalupvoted (50.00%) @bitgoldwallet / bitcoin-a-simple-explanation2020/04/27 08:30:39
nigerian-yogagalupvoted (50.00%) @bitgoldwallet / bitcoin-a-simple-explanation
2020/04/27 08:30:39
| voter | nigerian-yogagal |
| author | bitgoldwallet |
| permlink | bitcoin-a-simple-explanation |
| weight | 5000 (50.00%) |
| Transaction Info | Block #42883163/Trx 5181ea6a2abdd371d2dcf863cd5f42184bd3096b |
View Raw JSON Data
{
"trx_id": "5181ea6a2abdd371d2dcf863cd5f42184bd3096b",
"block": 42883163,
"trx_in_block": 24,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-27T08:30:39",
"op": [
"vote",
{
"voter": "nigerian-yogagal",
"author": "bitgoldwallet",
"permlink": "bitcoin-a-simple-explanation",
"weight": 5000
}
]
}helixupvoted (100.00%) @bitgoldwallet / bitcoin-a-simple-explanation2020/04/27 08:30:39
helixupvoted (100.00%) @bitgoldwallet / bitcoin-a-simple-explanation
2020/04/27 08:30:39
| voter | helix |
| author | bitgoldwallet |
| permlink | bitcoin-a-simple-explanation |
| weight | 10000 (100.00%) |
| Transaction Info | Block #42883163/Trx 86962d8810411145ffa81818733ade5f2b64557d |
View Raw JSON Data
{
"trx_id": "86962d8810411145ffa81818733ade5f2b64557d",
"block": 42883163,
"trx_in_block": 23,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-27T08:30:39",
"op": [
"vote",
{
"voter": "helix",
"author": "bitgoldwallet",
"permlink": "bitcoin-a-simple-explanation",
"weight": 10000
}
]
}lazovicovupvoted (50.00%) @bitgoldwallet / bitcoin-a-simple-explanation2020/04/27 08:30:39
lazovicovupvoted (50.00%) @bitgoldwallet / bitcoin-a-simple-explanation
2020/04/27 08:30:39
| voter | lazovicov |
| author | bitgoldwallet |
| permlink | bitcoin-a-simple-explanation |
| weight | 5000 (50.00%) |
| Transaction Info | Block #42883163/Trx 499f94d6e6cbe6848729597891290117267fc062 |
View Raw JSON Data
{
"trx_id": "499f94d6e6cbe6848729597891290117267fc062",
"block": 42883163,
"trx_in_block": 22,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-27T08:30:39",
"op": [
"vote",
{
"voter": "lazovicov",
"author": "bitgoldwallet",
"permlink": "bitcoin-a-simple-explanation",
"weight": 5000
}
]
}dynamicryptoupvoted (1.00%) @bitgoldwallet / bitcoin-a-simple-explanation2020/04/27 08:30:39
dynamicryptoupvoted (1.00%) @bitgoldwallet / bitcoin-a-simple-explanation
2020/04/27 08:30:39
| voter | dynamicrypto |
| author | bitgoldwallet |
| permlink | bitcoin-a-simple-explanation |
| weight | 100 (1.00%) |
| Transaction Info | Block #42883163/Trx 5af7b1a6f6afb27bf00d9299b9a3429b64d19599 |
View Raw JSON Data
{
"trx_id": "5af7b1a6f6afb27bf00d9299b9a3429b64d19599",
"block": 42883163,
"trx_in_block": 20,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-27T08:30:39",
"op": [
"vote",
{
"voter": "dynamicrypto",
"author": "bitgoldwallet",
"permlink": "bitcoin-a-simple-explanation",
"weight": 100
}
]
}futileupvoted (100.00%) @bitgoldwallet / bitcoin-a-simple-explanation2020/04/27 08:30:39
futileupvoted (100.00%) @bitgoldwallet / bitcoin-a-simple-explanation
2020/04/27 08:30:39
| voter | futile |
| author | bitgoldwallet |
| permlink | bitcoin-a-simple-explanation |
| weight | 10000 (100.00%) |
| Transaction Info | Block #42883163/Trx ccb595dfc7df67aeb7dfb0e3dfff7aba72489875 |
View Raw JSON Data
{
"trx_id": "ccb595dfc7df67aeb7dfb0e3dfff7aba72489875",
"block": 42883163,
"trx_in_block": 19,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-27T08:30:39",
"op": [
"vote",
{
"voter": "futile",
"author": "bitgoldwallet",
"permlink": "bitcoin-a-simple-explanation",
"weight": 10000
}
]
}cemkeupvoted (80.00%) @bitgoldwallet / bitcoin-a-simple-explanation2020/04/27 08:30:39
cemkeupvoted (80.00%) @bitgoldwallet / bitcoin-a-simple-explanation
2020/04/27 08:30:39
| voter | cemke |
| author | bitgoldwallet |
| permlink | bitcoin-a-simple-explanation |
| weight | 8000 (80.00%) |
| Transaction Info | Block #42883163/Trx dda395cbb524fd005eaba73b15b02c5b79fac5f3 |
View Raw JSON Data
{
"trx_id": "dda395cbb524fd005eaba73b15b02c5b79fac5f3",
"block": 42883163,
"trx_in_block": 18,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-27T08:30:39",
"op": [
"vote",
{
"voter": "cemke",
"author": "bitgoldwallet",
"permlink": "bitcoin-a-simple-explanation",
"weight": 8000
}
]
}oluwashinaayomiupvoted (50.00%) @bitgoldwallet / bitcoin-a-simple-explanation2020/04/27 08:30:39
oluwashinaayomiupvoted (50.00%) @bitgoldwallet / bitcoin-a-simple-explanation
2020/04/27 08:30:39
| voter | oluwashinaayomi |
| author | bitgoldwallet |
| permlink | bitcoin-a-simple-explanation |
| weight | 5000 (50.00%) |
| Transaction Info | Block #42883163/Trx e4f565480cf05d2629a34a26b333d779bf53f83e |
View Raw JSON Data
{
"trx_id": "e4f565480cf05d2629a34a26b333d779bf53f83e",
"block": 42883163,
"trx_in_block": 16,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-27T08:30:39",
"op": [
"vote",
{
"voter": "oluwashinaayomi",
"author": "bitgoldwallet",
"permlink": "bitcoin-a-simple-explanation",
"weight": 5000
}
]
}warjarupvoted (100.00%) @bitgoldwallet / bitcoin-a-simple-explanation2020/04/27 08:30:39
warjarupvoted (100.00%) @bitgoldwallet / bitcoin-a-simple-explanation
2020/04/27 08:30:39
| voter | warjar |
| author | bitgoldwallet |
| permlink | bitcoin-a-simple-explanation |
| weight | 10000 (100.00%) |
| Transaction Info | Block #42883163/Trx b1bf68a09f856364e46987a17def562477394c42 |
View Raw JSON Data
{
"trx_id": "b1bf68a09f856364e46987a17def562477394c42",
"block": 42883163,
"trx_in_block": 15,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-27T08:30:39",
"op": [
"vote",
{
"voter": "warjar",
"author": "bitgoldwallet",
"permlink": "bitcoin-a-simple-explanation",
"weight": 10000
}
]
}travelnepalupvoted (50.00%) @bitgoldwallet / bitcoin-a-simple-explanation2020/04/27 08:30:39
travelnepalupvoted (50.00%) @bitgoldwallet / bitcoin-a-simple-explanation
2020/04/27 08:30:39
| voter | travelnepal |
| author | bitgoldwallet |
| permlink | bitcoin-a-simple-explanation |
| weight | 5000 (50.00%) |
| Transaction Info | Block #42883163/Trx 799367e78cbf0fa35a09342f4348443af0271dd5 |
View Raw JSON Data
{
"trx_id": "799367e78cbf0fa35a09342f4348443af0271dd5",
"block": 42883163,
"trx_in_block": 13,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-27T08:30:39",
"op": [
"vote",
{
"voter": "travelnepal",
"author": "bitgoldwallet",
"permlink": "bitcoin-a-simple-explanation",
"weight": 5000
}
]
}jacksonoskeleupvoted (50.00%) @bitgoldwallet / bitcoin-a-simple-explanation2020/04/27 08:30:39
jacksonoskeleupvoted (50.00%) @bitgoldwallet / bitcoin-a-simple-explanation
2020/04/27 08:30:39
| voter | jacksonoskele |
| author | bitgoldwallet |
| permlink | bitcoin-a-simple-explanation |
| weight | 5000 (50.00%) |
| Transaction Info | Block #42883163/Trx 5c305680cbfa1b1f55de257e17b284a4958a58cf |
View Raw JSON Data
{
"trx_id": "5c305680cbfa1b1f55de257e17b284a4958a58cf",
"block": 42883163,
"trx_in_block": 12,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-27T08:30:39",
"op": [
"vote",
{
"voter": "jacksonoskele",
"author": "bitgoldwallet",
"permlink": "bitcoin-a-simple-explanation",
"weight": 5000
}
]
}amarbirupvoted (50.00%) @bitgoldwallet / bitcoin-a-simple-explanation2020/04/27 08:30:39
amarbirupvoted (50.00%) @bitgoldwallet / bitcoin-a-simple-explanation
2020/04/27 08:30:39
| voter | amarbir |
| author | bitgoldwallet |
| permlink | bitcoin-a-simple-explanation |
| weight | 5000 (50.00%) |
| Transaction Info | Block #42883163/Trx 093bc45222540d2e907d782e155ee116b6431755 |
View Raw JSON Data
{
"trx_id": "093bc45222540d2e907d782e155ee116b6431755",
"block": 42883163,
"trx_in_block": 10,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-27T08:30:39",
"op": [
"vote",
{
"voter": "amarbir",
"author": "bitgoldwallet",
"permlink": "bitcoin-a-simple-explanation",
"weight": 5000
}
]
}psygamblerupvoted (50.00%) @bitgoldwallet / bitcoin-a-simple-explanation2020/04/27 08:30:39
psygamblerupvoted (50.00%) @bitgoldwallet / bitcoin-a-simple-explanation
2020/04/27 08:30:39
| voter | psygambler |
| author | bitgoldwallet |
| permlink | bitcoin-a-simple-explanation |
| weight | 5000 (50.00%) |
| Transaction Info | Block #42883163/Trx 3215c9b710c78632f0484f9aa8c739080cb6be1a |
View Raw JSON Data
{
"trx_id": "3215c9b710c78632f0484f9aa8c739080cb6be1a",
"block": 42883163,
"trx_in_block": 8,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-27T08:30:39",
"op": [
"vote",
{
"voter": "psygambler",
"author": "bitgoldwallet",
"permlink": "bitcoin-a-simple-explanation",
"weight": 5000
}
]
}sezenkeupvoted (100.00%) @bitgoldwallet / bitcoin-a-simple-explanation2020/04/27 08:30:27
sezenkeupvoted (100.00%) @bitgoldwallet / bitcoin-a-simple-explanation
2020/04/27 08:30:27
| voter | sezenke |
| author | bitgoldwallet |
| permlink | bitcoin-a-simple-explanation |
| weight | 10000 (100.00%) |
| Transaction Info | Block #42883159/Trx cad2cb4eb6774d62beccaca92a8d7e957d1a4d93 |
View Raw JSON Data
{
"trx_id": "cad2cb4eb6774d62beccaca92a8d7e957d1a4d93",
"block": 42883159,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-27T08:30:27",
"op": [
"vote",
{
"voter": "sezenke",
"author": "bitgoldwallet",
"permlink": "bitcoin-a-simple-explanation",
"weight": 10000
}
]
}hasenmannupvoted (100.00%) @bitgoldwallet / bitcoin-a-simple-explanation2020/04/24 06:28:06
hasenmannupvoted (100.00%) @bitgoldwallet / bitcoin-a-simple-explanation
2020/04/24 06:28:06
| voter | hasenmann |
| author | bitgoldwallet |
| permlink | bitcoin-a-simple-explanation |
| weight | 10000 (100.00%) |
| Transaction Info | Block #42796637/Trx a0d7ef44e8f94ea9da021b081ec624df10acded2 |
View Raw JSON Data
{
"trx_id": "a0d7ef44e8f94ea9da021b081ec624df10acded2",
"block": 42796637,
"trx_in_block": 30,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-24T06:28:06",
"op": [
"vote",
{
"voter": "hasenmann",
"author": "bitgoldwallet",
"permlink": "bitcoin-a-simple-explanation",
"weight": 10000
}
]
}filipinoupvoted (10.00%) @bitgoldwallet / bitcoin-a-simple-explanation2020/04/24 03:32:30
filipinoupvoted (10.00%) @bitgoldwallet / bitcoin-a-simple-explanation
2020/04/24 03:32:30
| voter | filipino |
| author | bitgoldwallet |
| permlink | bitcoin-a-simple-explanation |
| weight | 1000 (10.00%) |
| Transaction Info | Block #42793218/Trx bd7c148ae2807a7cf05b6347eab2cbdcfa9321c7 |
View Raw JSON Data
{
"trx_id": "bd7c148ae2807a7cf05b6347eab2cbdcfa9321c7",
"block": 42793218,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-24T03:32:30",
"op": [
"vote",
{
"voter": "filipino",
"author": "bitgoldwallet",
"permlink": "bitcoin-a-simple-explanation",
"weight": 1000
}
]
}tongchat27upvoted (100.00%) @bitgoldwallet / bitcoin-a-simple-explanation2020/04/24 03:18:00
tongchat27upvoted (100.00%) @bitgoldwallet / bitcoin-a-simple-explanation
2020/04/24 03:18:00
| voter | tongchat27 |
| author | bitgoldwallet |
| permlink | bitcoin-a-simple-explanation |
| weight | 10000 (100.00%) |
| Transaction Info | Block #42792937/Trx 6623133c008ef4876c945000cf7889d63421ca44 |
View Raw JSON Data
{
"trx_id": "6623133c008ef4876c945000cf7889d63421ca44",
"block": 42792937,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-24T03:18:00",
"op": [
"vote",
{
"voter": "tongchat27",
"author": "bitgoldwallet",
"permlink": "bitcoin-a-simple-explanation",
"weight": 10000
}
]
}bitgoldwalletcustom json: notify2020/04/24 03:15:06
bitgoldwalletcustom json: notify
2020/04/24 03:15:06
| required auths | [] |
| required posting auths | ["bitgoldwallet"] |
| id | notify |
| json | ["setLastRead",{"date":"2020-04-24T03:15:04"}] |
| Transaction Info | Block #42792879/Trx 2449e492da7d86d6e7080e7799f507ab0d4a9b12 |
View Raw JSON Data
{
"trx_id": "2449e492da7d86d6e7080e7799f507ab0d4a9b12",
"block": 42792879,
"trx_in_block": 12,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-24T03:15:06",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"bitgoldwallet"
],
"id": "notify",
"json": "[\"setLastRead\",{\"date\":\"2020-04-24T03:15:04\"}]"
}
]
}bitgoldwalletupvoted (100.00%) @bitgoldwallet / bitcoin-a-simple-explanation2020/04/24 03:12:09
bitgoldwalletupvoted (100.00%) @bitgoldwallet / bitcoin-a-simple-explanation
2020/04/24 03:12:09
| voter | bitgoldwallet |
| author | bitgoldwallet |
| permlink | bitcoin-a-simple-explanation |
| weight | 10000 (100.00%) |
| Transaction Info | Block #42792822/Trx 9530e5fa59ef12c2e0869849e4e8f217a55db0db |
View Raw JSON Data
{
"trx_id": "9530e5fa59ef12c2e0869849e4e8f217a55db0db",
"block": 42792822,
"trx_in_block": 15,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-24T03:12:09",
"op": [
"vote",
{
"voter": "bitgoldwallet",
"author": "bitgoldwallet",
"permlink": "bitcoin-a-simple-explanation",
"weight": 10000
}
]
}bitgoldwalletsent 1.000 STEEM to @sezenke- "https://steemit.com/blockchain/@bitgoldwallet/bitcoin-a-simple-explanation"2020/04/24 03:04:06
bitgoldwalletsent 1.000 STEEM to @sezenke- "https://steemit.com/blockchain/@bitgoldwallet/bitcoin-a-simple-explanation"
2020/04/24 03:04:06
| from | bitgoldwallet |
| to | sezenke |
| amount | 1.000 STEEM |
| memo | https://steemit.com/blockchain/@bitgoldwallet/bitcoin-a-simple-explanation |
| Transaction Info | Block #42792666/Trx 87b2fd5c5a3b96c8bc53915818387f276e5bddeb |
View Raw JSON Data
{
"trx_id": "87b2fd5c5a3b96c8bc53915818387f276e5bddeb",
"block": 42792666,
"trx_in_block": 11,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-24T03:04:06",
"op": [
"transfer",
{
"from": "bitgoldwallet",
"to": "sezenke",
"amount": "1.000 STEEM",
"memo": "https://steemit.com/blockchain/@bitgoldwallet/bitcoin-a-simple-explanation"
}
]
}seat.leonupvoted (100.00%) @bitgoldwallet / bitcoin-a-simple-explanation2020/04/24 02:53:00
seat.leonupvoted (100.00%) @bitgoldwallet / bitcoin-a-simple-explanation
2020/04/24 02:53:00
| voter | seat.leon |
| author | bitgoldwallet |
| permlink | bitcoin-a-simple-explanation |
| weight | 10000 (100.00%) |
| Transaction Info | Block #42792449/Trx fa61198e1565eae8322c9ba0f0b5299979370904 |
View Raw JSON Data
{
"trx_id": "fa61198e1565eae8322c9ba0f0b5299979370904",
"block": 42792449,
"trx_in_block": 15,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-24T02:53:00",
"op": [
"vote",
{
"voter": "seat.leon",
"author": "bitgoldwallet",
"permlink": "bitcoin-a-simple-explanation",
"weight": 10000
}
]
}nadinkaupvoted (100.00%) @bitgoldwallet / bitcoin-a-simple-explanation2020/04/24 02:53:00
nadinkaupvoted (100.00%) @bitgoldwallet / bitcoin-a-simple-explanation
2020/04/24 02:53:00
| voter | nadinka |
| author | bitgoldwallet |
| permlink | bitcoin-a-simple-explanation |
| weight | 10000 (100.00%) |
| Transaction Info | Block #42792449/Trx c079abffed98f85c06bb84d2e6856efaedd1cd3a |
View Raw JSON Data
{
"trx_id": "c079abffed98f85c06bb84d2e6856efaedd1cd3a",
"block": 42792449,
"trx_in_block": 14,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-24T02:53:00",
"op": [
"vote",
{
"voter": "nadinka",
"author": "bitgoldwallet",
"permlink": "bitcoin-a-simple-explanation",
"weight": 10000
}
]
}obakuupvoted (20.00%) @bitgoldwallet / bitcoin-a-simple-explanation2020/04/24 02:53:00
obakuupvoted (20.00%) @bitgoldwallet / bitcoin-a-simple-explanation
2020/04/24 02:53:00
| voter | obaku |
| author | bitgoldwallet |
| permlink | bitcoin-a-simple-explanation |
| weight | 2000 (20.00%) |
| Transaction Info | Block #42792449/Trx 13508bbe11bca6b2017f3f42df6c46916649b5d1 |
View Raw JSON Data
{
"trx_id": "13508bbe11bca6b2017f3f42df6c46916649b5d1",
"block": 42792449,
"trx_in_block": 12,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-24T02:53:00",
"op": [
"vote",
{
"voter": "obaku",
"author": "bitgoldwallet",
"permlink": "bitcoin-a-simple-explanation",
"weight": 2000
}
]
}freetimeupvoted (100.00%) @bitgoldwallet / bitcoin-a-simple-explanation2020/04/24 02:53:00
freetimeupvoted (100.00%) @bitgoldwallet / bitcoin-a-simple-explanation
2020/04/24 02:53:00
| voter | freetime |
| author | bitgoldwallet |
| permlink | bitcoin-a-simple-explanation |
| weight | 10000 (100.00%) |
| Transaction Info | Block #42792449/Trx cdec9794355ff3351a5d6e3109a552b9e040e1d6 |
View Raw JSON Data
{
"trx_id": "cdec9794355ff3351a5d6e3109a552b9e040e1d6",
"block": 42792449,
"trx_in_block": 11,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-24T02:53:00",
"op": [
"vote",
{
"voter": "freetime",
"author": "bitgoldwallet",
"permlink": "bitcoin-a-simple-explanation",
"weight": 10000
}
]
}raise-me-upsent 0.001 STEEM to @bitgoldwallet- "Good luck, your post has been upvoted and resteemed with more than 45,000+ FOLLOWERS. Thanks for using our service. Don't miss our weekly subscription 6 SBD or 8 STEEM"2020/04/24 02:53:00
raise-me-upsent 0.001 STEEM to @bitgoldwallet- "Good luck, your post has been upvoted and resteemed with more than 45,000+ FOLLOWERS. Thanks for using our service. Don't miss our weekly subscription 6 SBD or 8 STEEM"
2020/04/24 02:53:00
| from | raise-me-up |
| to | bitgoldwallet |
| amount | 0.001 STEEM |
| memo | Good luck, your post has been upvoted and resteemed with more than 45,000+ FOLLOWERS. Thanks for using our service. Don't miss our weekly subscription 6 SBD or 8 STEEM |
| Transaction Info | Block #42792449/Trx 2e548486830de0b3877a407bbdf5e104f8e5dd6a |
View Raw JSON Data
{
"trx_id": "2e548486830de0b3877a407bbdf5e104f8e5dd6a",
"block": 42792449,
"trx_in_block": 10,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-24T02:53:00",
"op": [
"transfer",
{
"from": "raise-me-up",
"to": "bitgoldwallet",
"amount": "0.001 STEEM",
"memo": "Good luck, your post has been upvoted and resteemed with more than 45,000+ FOLLOWERS. Thanks for using our service. Don't miss our weekly subscription 6 SBD or 8 STEEM"
}
]
}blikiupvoted (100.00%) @bitgoldwallet / bitcoin-a-simple-explanation2020/04/24 02:53:00
blikiupvoted (100.00%) @bitgoldwallet / bitcoin-a-simple-explanation
2020/04/24 02:53:00
| voter | bliki |
| author | bitgoldwallet |
| permlink | bitcoin-a-simple-explanation |
| weight | 10000 (100.00%) |
| Transaction Info | Block #42792449/Trx ed6231c5ce585b1cb3db4ba52f2e0d47f6694187 |
View Raw JSON Data
{
"trx_id": "ed6231c5ce585b1cb3db4ba52f2e0d47f6694187",
"block": 42792449,
"trx_in_block": 9,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-24T02:53:00",
"op": [
"vote",
{
"voter": "bliki",
"author": "bitgoldwallet",
"permlink": "bitcoin-a-simple-explanation",
"weight": 10000
}
]
}raise-me-upupvoted (100.00%) @bitgoldwallet / bitcoin-a-simple-explanation2020/04/24 02:53:00
raise-me-upupvoted (100.00%) @bitgoldwallet / bitcoin-a-simple-explanation
2020/04/24 02:53:00
| voter | raise-me-up |
| author | bitgoldwallet |
| permlink | bitcoin-a-simple-explanation |
| weight | 10000 (100.00%) |
| Transaction Info | Block #42792449/Trx 532ade5c34489a68cfe1cf4c4c65aa4d73c72827 |
View Raw JSON Data
{
"trx_id": "532ade5c34489a68cfe1cf4c4c65aa4d73c72827",
"block": 42792449,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-24T02:53:00",
"op": [
"vote",
{
"voter": "raise-me-up",
"author": "bitgoldwallet",
"permlink": "bitcoin-a-simple-explanation",
"weight": 10000
}
]
}mazdaesupvoted (100.00%) @bitgoldwallet / bitcoin-a-simple-explanation2020/04/24 02:53:00
mazdaesupvoted (100.00%) @bitgoldwallet / bitcoin-a-simple-explanation
2020/04/24 02:53:00
| voter | mazdaes |
| author | bitgoldwallet |
| permlink | bitcoin-a-simple-explanation |
| weight | 10000 (100.00%) |
| Transaction Info | Block #42792449/Trx 42e3d6cd0133a7400194288238b97daa1816b762 |
View Raw JSON Data
{
"trx_id": "42e3d6cd0133a7400194288238b97daa1816b762",
"block": 42792449,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-24T02:53:00",
"op": [
"vote",
{
"voter": "mazdaes",
"author": "bitgoldwallet",
"permlink": "bitcoin-a-simple-explanation",
"weight": 10000
}
]
}bitgoldwalletsent 2.000 STEEM to @raise-me-up- "https://steemit.com/blockchain/@bitgoldwallet/bitcoin-a-simple-explanation"2020/04/24 02:52:57
bitgoldwalletsent 2.000 STEEM to @raise-me-up- "https://steemit.com/blockchain/@bitgoldwallet/bitcoin-a-simple-explanation"
2020/04/24 02:52:57
| from | bitgoldwallet |
| to | raise-me-up |
| amount | 2.000 STEEM |
| memo | https://steemit.com/blockchain/@bitgoldwallet/bitcoin-a-simple-explanation |
| Transaction Info | Block #42792448/Trx afc333a63fb5eb90bd4dc905c206a5afc27004e9 |
View Raw JSON Data
{
"trx_id": "afc333a63fb5eb90bd4dc905c206a5afc27004e9",
"block": 42792448,
"trx_in_block": 22,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-24T02:52:57",
"op": [
"transfer",
{
"from": "bitgoldwallet",
"to": "raise-me-up",
"amount": "2.000 STEEM",
"memo": "https://steemit.com/blockchain/@bitgoldwallet/bitcoin-a-simple-explanation"
}
]
}bitgoldwalletsent 1.500 STEEM to @raise-me-up- "https://steemit.com/blockchain/@bitgoldwallet/bitcoin-a-simple-explanation"2020/04/24 02:48:57
bitgoldwalletsent 1.500 STEEM to @raise-me-up- "https://steemit.com/blockchain/@bitgoldwallet/bitcoin-a-simple-explanation"
2020/04/24 02:48:57
| from | bitgoldwallet |
| to | raise-me-up |
| amount | 1.500 STEEM |
| memo | https://steemit.com/blockchain/@bitgoldwallet/bitcoin-a-simple-explanation |
| Transaction Info | Block #42792370/Trx 75652303f88c8273e038951051ded9840e065120 |
View Raw JSON Data
{
"trx_id": "75652303f88c8273e038951051ded9840e065120",
"block": 42792370,
"trx_in_block": 10,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-24T02:48:57",
"op": [
"transfer",
{
"from": "bitgoldwallet",
"to": "raise-me-up",
"amount": "1.500 STEEM",
"memo": "https://steemit.com/blockchain/@bitgoldwallet/bitcoin-a-simple-explanation"
}
]
}bitgoldwalletsent 2.000 STEEM to @merlin7- "https://steemit.com/blockchain/@bitgoldwallet/bitcoin-a-simple-explanation"2020/04/24 02:47:00
bitgoldwalletsent 2.000 STEEM to @merlin7- "https://steemit.com/blockchain/@bitgoldwallet/bitcoin-a-simple-explanation"
2020/04/24 02:47:00
| from | bitgoldwallet |
| to | merlin7 |
| amount | 2.000 STEEM |
| memo | https://steemit.com/blockchain/@bitgoldwallet/bitcoin-a-simple-explanation |
| Transaction Info | Block #42792333/Trx ef09bed157c3302700108fd931609528667f0d2b |
View Raw JSON Data
{
"trx_id": "ef09bed157c3302700108fd931609528667f0d2b",
"block": 42792333,
"trx_in_block": 10,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-24T02:47:00",
"op": [
"transfer",
{
"from": "bitgoldwallet",
"to": "merlin7",
"amount": "2.000 STEEM",
"memo": "https://steemit.com/blockchain/@bitgoldwallet/bitcoin-a-simple-explanation"
}
]
}bitgoldwalletsent 1.000 STEEM to @all.cars- "https://steemit.com/blockchain/@bitgoldwallet/bitcoin-a-simple-explanation"2020/04/24 02:45:27
bitgoldwalletsent 1.000 STEEM to @all.cars- "https://steemit.com/blockchain/@bitgoldwallet/bitcoin-a-simple-explanation"
2020/04/24 02:45:27
| from | bitgoldwallet |
| to | all.cars |
| amount | 1.000 STEEM |
| memo | https://steemit.com/blockchain/@bitgoldwallet/bitcoin-a-simple-explanation |
| Transaction Info | Block #42792303/Trx 39466b7d76ab689165f59f364ed9f6c56a3f4696 |
View Raw JSON Data
{
"trx_id": "39466b7d76ab689165f59f364ed9f6c56a3f4696",
"block": 42792303,
"trx_in_block": 17,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-24T02:45:27",
"op": [
"transfer",
{
"from": "bitgoldwallet",
"to": "all.cars",
"amount": "1.000 STEEM",
"memo": "https://steemit.com/blockchain/@bitgoldwallet/bitcoin-a-simple-explanation"
}
]
}bitgoldwalletcustom json: notify2020/04/24 02:42:39
bitgoldwalletcustom json: notify
2020/04/24 02:42:39
| required auths | [] |
| required posting auths | ["bitgoldwallet"] |
| id | notify |
| json | ["setLastRead",{"date":"2020-04-24T02:42:37"}] |
| Transaction Info | Block #42792247/Trx 60e38ac7b4ab586e35f3f2ed5addf7ef19e2d906 |
View Raw JSON Data
{
"trx_id": "60e38ac7b4ab586e35f3f2ed5addf7ef19e2d906",
"block": 42792247,
"trx_in_block": 14,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-24T02:42:39",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"bitgoldwallet"
],
"id": "notify",
"json": "[\"setLastRead\",{\"date\":\"2020-04-24T02:42:37\"}]"
}
]
}statsexpertupvoted (20.00%) @bitgoldwallet / bitcoin-a-simple-explanation2020/04/24 02:40:24
statsexpertupvoted (20.00%) @bitgoldwallet / bitcoin-a-simple-explanation
2020/04/24 02:40:24
| voter | statsexpert |
| author | bitgoldwallet |
| permlink | bitcoin-a-simple-explanation |
| weight | 2000 (20.00%) |
| Transaction Info | Block #42792203/Trx 642cc4ee9bdffcd97d4d751a35a8d5753e45962a |
View Raw JSON Data
{
"trx_id": "642cc4ee9bdffcd97d4d751a35a8d5753e45962a",
"block": 42792203,
"trx_in_block": 10,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-24T02:40:24",
"op": [
"vote",
{
"voter": "statsexpert",
"author": "bitgoldwallet",
"permlink": "bitcoin-a-simple-explanation",
"weight": 2000
}
]
}bitgoldwalletpublished a new post: bitcoin-a-simple-explanation2020/04/24 02:39:21
bitgoldwalletpublished a new post: bitcoin-a-simple-explanation
2020/04/24 02:39:21
| parent author | |
| parent permlink | blockchain |
| author | bitgoldwallet |
| permlink | bitcoin-a-simple-explanation |
| title | BITCOIN: A SIMPLE EXPLANATION |
| body | WWW.BITGOLDWALLET.COM/downloads.html PDF AVAILABLE DOWNLOAD (FROM THE 17 APRIL 2020) Officially published via the website on Friday 17 April 2020 How does bitcoin work? This article will try to explain bitcoin using words and examples which are easy to understand. To achieve this, the explanation may be very slightly inaccurate in some places, however this will make it easier to understand. By the end of this article, you will hopefully have a better understanding of bitcoin. PART 1.1 : BITCOIN PUBLIC ADDRESSES The first basic part of bitcoin which needs to be understood is what bitcoin public addresses are, how they are created, and how they work together with bitcoin private keys. A bitcoin public address is basically like a bank account number which holds people’s bitcoins. An example of what it may look like is: 16er32qQe1Xi5ZEbqxvWJJN4GKC9kYnp1i A real bitcoin public address like the one shown above is made up of capital and lowercase letters, as well as numbers that are arranged in a specific way. In our simple explanation, I will instead give an example where 10 NUMBERS are used to represent a bitcoin public address. So our example bitcoin public address looks like the below: 8104940784 In order to receive bitcoins, you need to have a bitcoin public address which the bitcoin computer wallet program has created. This is the ‘thing’ you give to other people for them to send you the bitcoins. So how are bitcoin public addresses created? PART 1.2: BITCOIN PRIVATE KEYS A bitcoin public address is always created using a bitcoin private key. An example of what a bitcoin private key may look like is: L4iLhJzUAvNfa6x3wyYGV9N6fCR3cMXN7EJ7RiC5ct4dZjmdhSmd A real bitcoin private key like the one shown above is made up of capital and lowercase letters, as well as numbers that are arranged in a specific way. In our explanation, I will instead give an example where 20 NUMBERS are used to represent a bitcoin private key. So our example bitcoin private key looks like the below: 16503429214399795533 To create a bitcoin private key, you would use a bitcoin computer wallet program. This bitcoin private key is like a password to your bitcoin public address that lets you send the bitcoins from the bitcoin public address you currently own to another person’s bitcoin public address. SO HOW ARE BITCOIN PRIVATE KEYS CREATED? This is where the magic starts. All bitcoin private keys start as a very LARGE and very RANDOM number that is created by the bitcoin computer wallet program. This random number might be between 100 – 1000 numbers long or longer*. Think of a number so large that it is impossible for anyone or anything to guess this number. Imagine the entire universe was filled with computers placed side by side, all of them turned on and all of them repeatedly trying to guess this number, for all time and still failing. This is more or less the number that your computer creates. The computer program you use will then convert this random number to a bitcoin private key. To a computer, all data is numbers represented by zeros and ones. So it can be seen that a computer program can easily convert any random number to a bitcoin private key with the correct formatting or structure. The main thing to understand is that the bitcoin private key is infact a completely random set of characters and numbers. No one else on the planet knows the bitcoin private key except you because you created it randomly on your computer. If you created the bitcoin private key and only you know it, then this means you own the bitcoin private key. (Note: in reality, security is a massive issue with the creation of bitcoin private keys due to the risk of this data being stolen and spied on, so many people, including beginners let reputable cryptocurrency exchanges handle the storage and creation of their bitcoin private keys for them). So how is the bitcoin private key converted to the bitcoin public address? The bitcoin computer wallet program does this by using an exact formula known as a SHA256 hash together with other steps. The formula used is one-way, meaning that once the bitcoin public address is created, no one can use the bitcoin public address to work out what the private key was. And the formula is always the same and always gets the same result for the same original character string. In cryptography and in bitcoin, a one way hash like the SHA256 hash shown above is very important and is used a lot. In our explanation, instead of using the SHA256 hash; to make the idea easier to understand, I will use a simple one way formula (or hash) which I have made up so you can see how the one way aspect might work. We will call this hash the MU-hash (Made up hash): Our example MU-hash = 1) Take the first set of numbers, then 2) multiply this by 3141592654, then 3) remove the first 5 numbers from the result, and then 4) repeat this process 1000 times, and then after this is done, 5) only show the first 10 numbers and remove all the other numbers. To simplify this further so that this can actually be done in an example, we will replace 4) repeat this process 1000 times with 4) repeat this process one time. Ok. So to summarize PART 1, the computer wallet program creates: Random number > then creates Bitcoin private key [then uses one way hash] > to create Bitcoin public address OK. So now we can start our example: Start with Bitcoin private key = 16503429214399795533 Then hash this private key with our MU-hash = 1 & 2: 16503429214399795533 x 3141592654 = 51847051985767388665574814582 3: 51847051985767388665574814582 (remove first 5 numbers) = 051985767388665574814582 [take note that it is possible for zeros to be in the front of the number, and that it is rarer for these resulting numbers to have many consecutive zeros in front of it] 4: (repeat this process one time) = 051985767388665574814582 x 3141592654 = 163318104940784532700178223280628 (then remove first 5 numbers) = 8104940784532700178223280628 5: (only show first 10 numbers and remove all the other numbers) = 8104940784 = Bitcoin public address SO we are left with: Bitcoin private key = 16503429214399795533 (and) Bitcoin public address = 8104940784 Every single time we do this one way MU-hash on the same original bitcoin private key we will get the same bitcoin public address. And looking only at the bitcoin public address, it is impossible to calculate or guess what the original bitcoin private key was. For our simple example though with the MU-hash, a powerful computer organization might be able to guess or calculate our bitcoin private key through random guessing (because our numbers are fairly small) but for the real bitcoin private key this would be impossible to do. At its simplest level, this is how bitcoin public addresses and bitcoin private keys work. If you know the bitcoin private key, you can always prove to the network that you own the bitcoin public address which contains the bitcoins and the network will always let you move the bitcoins even though they don’t know who you are. You can see now how anyone on the planet can, in the safety of their own homes, create their own bitcoin public addresses to give to people in order to receive and send bitcoins from. This is part of what makes bitcoin a decentralized digital currency which allows anyone to take part in, and which is hard to restrict or ban. PART 2: THE BITCOIN BLOCKCHAIN So the bitcoin private key and bitcoin public address holds the actual bitcoins. And you can see that these can be created and stored without limit by anyone knowledgeable enough. However, if we only have these, the bitcoins won’t be of any use. We need a payment network which lets you send your bitcoins to different bitcoin addresses. The bitcoin blockchain serves this purpose. The bitcoin blockchain is basically the list (or ledger) of all the transactions and all the used bitcoin public addresses that has ever been made in the bitcoin network. It is maintained by a large number of highly invested people and groups who take part in the network (known as miners)**. The easiest way to understand the bitcoin blockchain is to go back to the very beginning of bitcoin in the year 2009 at Block 0 known as the genesis block and then slowly build up from there. I will only need to describe up to Block 2 for you to get a good enough idea. I want to emphasize that these things didn’t happen as described for the actual bitcoin blockchain but is rather a hypothetical scenario which fairly accurately explains how bitcoin mining and bitcoin transactions work***. BLOCK ZERO – GENESIS BLOCK BLOCK ZERO basically has no transaction data. But it still has data such as the date it was created and some other data. This blockchain data is stored on the computers of individual people who have downloaded and run the original bitcoin wallet program (called nodes and/or miners). In our example we will assume there are only 3 participants which make up all the users in the network: Participants A, B and C. In the future many new participants will join the network. The original bitcoin wallet program and all future variations of the program is free for anyone to download and use. Each of these 3 participants would have had the option to mine bitcoins. And they would have been able to create bitcoin public addresses and private keys like described earlier. When they ran the mining software for the first time at least one bitcoin public address was created by each of them. So assume: Participant A has created bitcoin public address 1EcKp4Cv6QLV5kmCMEezERLXJYTaNVaLgs Participant B has created bitcoin public address 14pP4zDquF3NE3BSjjpNbsCTz9tDs9cSN8 Participant C has created bitcoin public address 1J62KZfV2Z8653zv3ydW88YgjBZySj7CQm Now all 3 Participants activate their mining software. Since there are currently no bitcoins in all the world, BLOCK ONE, the next block of the blockchain will not contain any transactions showing any movement of bitcoins, but it will show a balance of 50 new bitcoins created into one of the 3 bitcoin public addresses shown above owned by Participant A, B or C. New bitcoins enter the world after every mining round. The way the software decides which miner gets the 50 new bitcoins is based on a ‘proof of work’ system. On average new bitcoins enter the world every 10 minutes and this rate is set by the computer software. HOW MINING WORKS So we will assume that all 3 participants turn on their mining software at the same time and everyone is using the exact same type of computer. These 3 miners all have the same copy of the bitcoin blockchain which in its entirety is currently BLOCK ZERO. The mining software now takes the BLOCK ZERO file data and adds the empty BLOCK ONE file data to it and then expresses this file as a number (we will call this the ‘block one computer number’). Remember that all data files on a computer are zeros and ones. Then the software begins the mining process by taking a random number (called a nonce) and adding this random number to the end of the ‘block one computer number’. Then it creates a one way (SHA256) hash of this new number and the result is recorded somewhere. Basically the rules of the program states that if this resulting number (or hash) has a certain number of consecutive zeros in front of it, then it proves that that computer has completed the ‘proof of work’ and the software automatically creates the 50 new bitcoins into that participant miner’s bitcoin public address. If the random number doesn’t lead to the required number of consecutive zeros then the computer tries again until it does find one. The proof of work here lies in the fact that mathematically, it takes a certain number of random hashes by the computer before the computer will find one that meets the difficulty requirement of having a hash-result with the required number of consecutive zeros in front of it. Every 2 weeks this difficulty is automatically adjusted by the bitcoin computer program which all the miners run by adding or reducing the number of consecutive zeros that are needed before new bitcoins can be awarded. The more zeros there are, the more difficult it is to solve****. The difficulty is changed so that on average about every 10 minutes a new block is solved, and this happens regardless of how many or how few computers are mining. In our example each of the 3 miners have an equal chance of finding the correct hash first because everyone is running the same computer type and so each computer will create the same number of hashes per second. In modern day bitcoin mining though, different miners have vastly different hash producing abilities and this will directly impact on how many blocks they will solve compared to other miners. The more hashes they can make compared to the rest of the miners, the more blocks they will solve. Also, in modern day mining the number of hashes required is so huge now that only mining pools or centres with millions and millions of dollars worth of dedicated mining hardware in them can successfully solve new blocks. So we will assume Participant A was the first to solve BLOCK ONE and their bitcoin wallet software now shows 50 bitcoins at address 1EcKp4Cv6QLV5kmCMEezERLXJYTaNVaLgs. Participant A will now broadcast this information to the entire network and Participants B and C will check that Participant A’s hash number is correct by simply checking that the number they used leads to the correct hash in that new block (correct hash = proof that work has been done). If it is correct then their computers will now also show BLOCK ZERO + BLOCK ONE. The bitcoin blockchain has now been updated and will look like the following: BLOCK ZERO (date and time created) + BLOCK ONE (date and time created)(50 NEW BTC at 1EcKp4C… as mining block reward) + Solved HASH of Block one MAKING TRANSACTIONS Lets say that participant A decides to spend their bitcoins right now by sending it to another bitcoin address. Participant C has given Participant A an address for him/her to send the bitcoins to (say address 18yACUJ3PaAWs41GoJU7aDZSTLEqwaBA4b). So Participant A will now create a transaction on their computer. The transaction will be to: SEND 20 BTC from 1EcKp4Cv6QLV5kmCMEezERLXJYTaNVaLgs to 18yACUJ3PaAWs41GoJU7aDZSTLEqwaBA4b and send the CHANGE 29 BTC back to 1EcKp4Cv6QLV5kmCMEezERLXJYTaNVaLgs, and give 1 BTC as the transaction fee to be sent to the miner that solves the next block. This transaction will immediately enter the memory pool (called mempool) which can be picked up by any of the other miners in the network. Now lets assume all three Participants A, B and C continue to try to solve the next block of the bitcoin blockchain called BLOCK TWO. To do this they would take the current blockchain and then add any transactions they like from the mempool to create a new blockchain that includes BLOCK ZERO and BLOCK ONE and BLOCK TWO, which is then expressed as a ‘block two computer number’. They will then attempt to solve the new block like before. None of the miners are required to add any transactions from the mempool and can continue to mine an empty block if they wanted, but they usually want to add transactions because they will receive the transaction fee that Participant A has included in the transaction. So lets now assume this time Participant B successfully solves the next block. The bitcoin blockchain will now look like the following: BLOCK ZERO (date and time created) + BLOCK ONE (date and time created)(50 NEW BTC at 1EcKp4C… as mining block reward) + Solved HASH of Block one + BLOCK TWO (date and time created)(20 BTC at 18yACU…. (1 confirmation) moved from 1EcKp4C…; 29 BTC at 1EcKp4C... (1 confirmation) moved from 1EcKp4C…; 1 BTC at miners address 14pP4zDq… as transaction fee reward moved from 1EcKp4C…; and 50 NEW BTC at miners address 14pP4zDq… as mining block reward) + Solved HASH of Block two A real world example of a ‘Solved HASH of Block #593468’ of the bitcoin blockchain is shown below (it is a hexadecimal base-16 number containing exactly 64 characters): 00000000000000000014fcb29e6e3b0ead3bd2e307d7f619a935f1d5323e9013 There is a lot more to all of this but this is the gist of what bitcoin mining and solving blocks involves. The entire system has been designed to be very secure and very stable and has been in continuous improvement since it started. A point to highlight is that only so many bitcoins can be added at a certain time and the rate of new bitcoins that can be added is halved about every four years. This is where bitcoin’s programmed scarcity comes from and is a major reason why it is so valuable. There will only ever be a certain maximum number of bitcoins on the planet and never anymore. The total number of all the bitcoins in the world is currently over 87% of its maximum possible number. A FINAL LOOK AT TRANSACTIONS When a transaction is created, the software you use will do a number of things. The most important of these is that it will sign the transaction with the bitcoin private key and then it will broadcast the transaction to the network. The way your computer proves to the network that you are the rightful owner of the bitcoins stored at a particular bitcoin public address is by using one way hashes together with your bitcoin private key. And it does this without revealing your bitcoin private key to anyone except yourself. To picture how this is possible, simply go back to our previous example of how your bitcoin private key was hashed to create the bitcoin public address. Now instead of: Random number > then creates Bitcoin private key [then uses one way hash] > to create Bitcoin public address We simply add ONE more hash step in between the bitcoin private key and bitcoin public address so that we have: Random number > then creates Bitcoin private key [then uses one way hash] > to create SIGNATURE [then uses another one way hash] > to create Bitcoin public address Now it is possible to show the network your SIGNATURE without revealing your bitcoin private key while still proving that you are the owner of the bitcoin private key. In practice, there is more to the signing process (such as public keys), and each signature will only work specifically to a particular transaction you have created, but you get the idea. As soon as you have created the transaction and the bitcoin network has checked that it is valid, your transaction will enter the mempool in order to be picked up by a miner, and then eventually added to the next block of the blockchain. Bitcoin transactions therefore can happen securely and discretely, with no need for you trust any particular third party (such as banking institutions). You only need to trust that your own creation, storage and transaction steps used to create and send the bitcoins were secure; and that the network of miners maintaining the network will continue to mine new blocks the way they have always mined them since the very beginning. Written by Bitgoldwallet.com owner Slight inaccuracies explained: * The actual random number only needs to be between 2128 (2 to the power of 128) and 2256 (2 to the power of 256) to meet unbreakable cryptography standards. This is roughly equal to a number containing between 39 and 78 numbers (decimal numbers). ** Not every miner who takes part in the bitcoin network needs to be highly invested. Many smaller miners who work as part of a larger mining pool have not necessarily spent huge amounts of money on their equipment. Many mining groups however are heavily invested and they are located all over the world. *** The real bitcoin blockchain was originally mined mainly by its creator/s (Satoshi Nakamoto) for a period of up to 12 months before any significant number of other participants joined the network. The first block was mined on the 3 Jan 2009 and the first open source bitcoin client (or program) was released to the public on the 9 Jan 2009. The first bitcoin transaction was made on the 12 Jan 2009, about 10 days after the first block was mined. The huge majority of the estimated 1.6 million or so bitcoins which was mined in 2009 have never been moved and it is believed that the private keys to these have been lost. **** The way the actual bitcoin mining difficulty is set is not by requiring the hashed number such as 00000000000000000014fcb29e6e3b0ead3bd2e307d7f619a935f1d5323e9013 to have a certain number of consecutive zeros in front of it, but for it to be smaller than a certain number that happens to have a lot of consecutive zeros in front of it. So for the above example, the hashed number might just need to be a number smaller than say 0000000000000000001500000000000000000000000000000000000000000000. Because of this, the difficulty can be set quite precisely. Colour scheme explained: Green text = real world examples of bitcoin public addresses, private keys and hashes Blue text = made up examples of bitcoin public addresses, private keys, hashes, names and blockchain data used to make explaining how bitcoin works easier to understand End of article |
| json metadata | {"tags":["bitcoin","cryptocurrency","bitgold","bitgoldwallet"],"app":"steemit/0.2","format":"markdown"} |
| Transaction Info | Block #42792182/Trx 440cac147a4accfdb1e72014a08a06d2a8ddf2ce |
View Raw JSON Data
{
"trx_id": "440cac147a4accfdb1e72014a08a06d2a8ddf2ce",
"block": 42792182,
"trx_in_block": 11,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-24T02:39:21",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "blockchain",
"author": "bitgoldwallet",
"permlink": "bitcoin-a-simple-explanation",
"title": "BITCOIN: A SIMPLE EXPLANATION",
"body": "WWW.BITGOLDWALLET.COM/downloads.html PDF AVAILABLE DOWNLOAD (FROM THE 17 APRIL 2020)\n\nOfficially published via the website on Friday 17 April 2020\n\nHow does bitcoin work? This article will try to explain bitcoin using words and examples which are easy to understand. To achieve this, the explanation may be very slightly inaccurate in some places, however this will make it easier to understand. By the end of this article, you will hopefully have a better understanding of bitcoin.\n\nPART 1.1 : BITCOIN PUBLIC ADDRESSES\n\nThe first basic part of bitcoin which needs to be understood is what bitcoin public addresses are, how they are created, and how they work together with bitcoin private keys. A bitcoin public address is basically like a bank account number which holds people’s bitcoins. An example of what it may look like is: \n\n16er32qQe1Xi5ZEbqxvWJJN4GKC9kYnp1i\n\nA real bitcoin public address like the one shown above is made up of capital and lowercase letters, as well as numbers that are arranged in a specific way.\n\nIn our simple explanation, I will instead give an example where 10 NUMBERS are used to represent a bitcoin public address. So our example bitcoin public address looks like the below:\n\n8104940784\n\nIn order to receive bitcoins, you need to have a bitcoin public address which the bitcoin computer wallet program has created. This is the ‘thing’ you give to other people for them to send you the bitcoins. So how are bitcoin public addresses created?\n\nPART 1.2: BITCOIN PRIVATE KEYS \n\nA bitcoin public address is always created using a bitcoin private key. An example of what a bitcoin private key may look like is: \n\nL4iLhJzUAvNfa6x3wyYGV9N6fCR3cMXN7EJ7RiC5ct4dZjmdhSmd\n\nA real bitcoin private key like the one shown above is made up of capital and lowercase letters, as well as numbers that are arranged in a specific way. \n\nIn our explanation, I will instead give an example where 20 NUMBERS are used to represent a bitcoin private key. So our example bitcoin private key looks like the below:\n\n16503429214399795533\n\nTo create a bitcoin private key, you would use a bitcoin computer wallet program. This bitcoin private key is like a password to your bitcoin public address that lets you send the bitcoins from the bitcoin public address you currently own to another person’s bitcoin public address.\n\nSO HOW ARE BITCOIN PRIVATE KEYS CREATED? This is where the magic starts.\n\nAll bitcoin private keys start as a very LARGE and very RANDOM number that is created by the bitcoin computer wallet program. This random number might be between 100 – 1000 numbers long or longer*. Think of a number so large that it is impossible for anyone or anything to guess this number. Imagine the entire universe was filled with computers placed side by side, all of them turned on and all of them repeatedly trying to guess this number, for all time and still failing. This is more or less the number that your computer creates.\n\nThe computer program you use will then convert this random number to a bitcoin private key. To a computer, all data is numbers represented by zeros and ones. So it can be seen that a computer program can easily convert any random number to a bitcoin private key with the correct formatting or structure.\n\nThe main thing to understand is that the bitcoin private key is infact a completely random set of characters and numbers. No one else on the planet knows the bitcoin private key except you because you created it randomly on your computer. If you created the bitcoin private key and only you know it, then this means you own the bitcoin private key.\n\n(Note: in reality, security is a massive issue with the creation of bitcoin private keys due to the risk of this data being stolen and spied on, so many people, including beginners let reputable cryptocurrency exchanges handle the storage and creation of their bitcoin private keys for them).\n\nSo how is the bitcoin private key converted to the bitcoin public address?\n\nThe bitcoin computer wallet program does this by using an exact formula known as a SHA256 hash together with other steps. The formula used is one-way, meaning that once the bitcoin public address is created, no one can use the bitcoin public address to work out what the private key was. And the formula is always the same and always gets the same result for the same original character string.\n\nIn cryptography and in bitcoin, a one way hash like the SHA256 hash shown above is very important and is used a lot.\n\nIn our explanation, instead of using the SHA256 hash; to make the idea easier to understand, I will use a simple one way formula (or hash) which I have made up so you can see how the one way aspect might work. We will call this hash the MU-hash (Made up hash):\n\nOur example MU-hash = \n\n1) Take the first set of numbers, then 2) multiply this by 3141592654, then 3) remove the first 5 numbers from the result, and then 4) repeat this process 1000 times, and then after this is done, 5) only show the first 10 numbers and remove all the other numbers.\n\nTo simplify this further so that this can actually be done in an example, we will replace 4) repeat this process 1000 times with 4) repeat this process one time.\n\nOk. So to summarize PART 1, the computer wallet program creates:\n\nRandom number > then creates Bitcoin private key [then uses one way hash] > to create Bitcoin public address\n\nOK. So now we can start our example:\n\nStart with Bitcoin private key = 16503429214399795533\n\nThen hash this private key with our MU-hash = \n\n1 & 2: 16503429214399795533 x 3141592654 = 51847051985767388665574814582\n\n3: 51847051985767388665574814582 (remove first 5 numbers) = 051985767388665574814582 [take note that it is possible for zeros to be in the front of the number, and that it is rarer for these resulting numbers to have many consecutive zeros in front of it]\n\n4: (repeat this process one time) = 051985767388665574814582 x 3141592654 = 163318104940784532700178223280628 (then remove first 5 numbers) = 8104940784532700178223280628\n\n5: (only show first 10 numbers and remove all the other numbers) = 8104940784 = Bitcoin public address\n\nSO we are left with:\n\nBitcoin private key = 16503429214399795533 (and) \nBitcoin public address = 8104940784\n\nEvery single time we do this one way MU-hash on the same original bitcoin private key we will get the same bitcoin public address. And looking only at the bitcoin public address, it is impossible to calculate or guess what the original bitcoin private key was. For our simple example though with the MU-hash, a powerful computer organization might be able to guess or calculate our bitcoin private key through random guessing (because our numbers are fairly small) but for the real bitcoin private key this would be impossible to do.\n\nAt its simplest level, this is how bitcoin public addresses and bitcoin private keys work. If you know the bitcoin private key, you can always prove to the network that you own the bitcoin public address which contains the bitcoins and the network will always let you move the bitcoins even though they don’t know who you are.\n\nYou can see now how anyone on the planet can, in the safety of their own homes, create their own bitcoin public addresses to give to people in order to receive and send bitcoins from. This is part of what makes bitcoin a decentralized digital currency which allows anyone to take part in, and which is hard to restrict or ban. \n\nPART 2: THE BITCOIN BLOCKCHAIN\n\nSo the bitcoin private key and bitcoin public address holds the actual bitcoins. And you can see that these can be created and stored without limit by anyone knowledgeable enough. However, if we only have these, the bitcoins won’t be of any use. We need a payment network which lets you send your bitcoins to different bitcoin addresses.\n\nThe bitcoin blockchain serves this purpose. The bitcoin blockchain is basically the list (or ledger) of all the transactions and all the used bitcoin public addresses that has ever been made in the bitcoin network. It is maintained by a large number of highly invested people and groups who take part in the network (known as miners)**.\n\nThe easiest way to understand the bitcoin blockchain is to go back to the very beginning of bitcoin in the year 2009 at Block 0 known as the genesis block and then slowly build up from there. I will only need to describe up to Block 2 for you to get a good enough idea. I want to emphasize that these things didn’t happen as described for the actual bitcoin blockchain but is rather a hypothetical scenario which fairly accurately explains how bitcoin mining and bitcoin transactions work***.\n\nBLOCK ZERO – GENESIS BLOCK\n\nBLOCK ZERO basically has no transaction data. But it still has data such as the date it was created and some other data. This blockchain data is stored on the computers of individual people who have downloaded and run the original bitcoin wallet program (called nodes and/or miners). In our example we will assume there are only 3 participants which make up all the users in the network: Participants A, B and C. In the future many new participants will join the network. The original bitcoin wallet program and all future variations of the program is free for anyone to download and use. \n\nEach of these 3 participants would have had the option to mine bitcoins. And they would have been able to create bitcoin public addresses and private keys like described earlier. \n\nWhen they ran the mining software for the first time at least one bitcoin public address was created by each of them. So assume:\n\nParticipant A has created bitcoin public address 1EcKp4Cv6QLV5kmCMEezERLXJYTaNVaLgs\n\nParticipant B has created bitcoin public address \n14pP4zDquF3NE3BSjjpNbsCTz9tDs9cSN8\n\nParticipant C has created bitcoin public address\n1J62KZfV2Z8653zv3ydW88YgjBZySj7CQm\n\nNow all 3 Participants activate their mining software. Since there are currently no bitcoins in all the world, BLOCK ONE, the next block of the blockchain will not contain any transactions showing any movement of bitcoins, but it will show a balance of 50 new bitcoins created into one of the 3 bitcoin public addresses shown above owned by Participant A, B or C. New bitcoins enter the world after every mining round. The way the software decides which miner gets the 50 new bitcoins is based on a ‘proof of work’ system. On average new bitcoins enter the world every 10 minutes and this rate is set by the computer software.\n\nHOW MINING WORKS\n\nSo we will assume that all 3 participants turn on their mining software at the same time and everyone is using the exact same type of computer. These 3 miners all have the same copy of the bitcoin blockchain which in its entirety is currently BLOCK ZERO. The mining software now takes the BLOCK ZERO file data and adds the empty BLOCK ONE file data to it and then expresses this file as a number (we will call this the ‘block one computer number’). Remember that all data files on a computer are zeros and ones. Then the software begins the mining process by taking a random number (called a nonce) and adding this random number to the end of the ‘block one computer number’. Then it creates a one way (SHA256) hash of this new number and the result is recorded somewhere. Basically the rules of the program states that if this resulting number (or hash) has a certain number of consecutive zeros in front of it, then it proves that that computer has completed the ‘proof of work’ and the software automatically creates the 50 new bitcoins into that participant miner’s bitcoin public address. If the random number doesn’t lead to the required number of consecutive zeros then the computer tries again until it does find one. The proof of work here lies in the fact that mathematically, it takes a certain number of random hashes by the computer before the computer will find one that meets the difficulty requirement of having a hash-result with the required number of consecutive zeros in front of it.\n\nEvery 2 weeks this difficulty is automatically adjusted by the bitcoin computer program which all the miners run by adding or reducing the number of consecutive zeros that are needed before new bitcoins can be awarded. The more zeros there are, the more difficult it is to solve****. The difficulty is changed so that on average about every 10 minutes a new block is solved, and this happens regardless of how many or how few computers are mining.\n\nIn our example each of the 3 miners have an equal chance of finding the correct hash first because everyone is running the same computer type and so each computer will create the same number of hashes per second. In modern day bitcoin mining though, different miners have vastly different hash producing abilities and this will directly impact on how many blocks they will solve compared to other miners. The more hashes they can make compared to the rest of the miners, the more blocks they will solve. Also, in modern day mining the number of hashes required is so huge now that only mining pools or centres with millions and millions of dollars worth of dedicated mining hardware in them can successfully solve new blocks. \n\nSo we will assume Participant A was the first to solve BLOCK ONE and their bitcoin wallet software now shows 50 bitcoins at address 1EcKp4Cv6QLV5kmCMEezERLXJYTaNVaLgs. Participant A will now broadcast this information to the entire network and Participants B and C will check that Participant A’s hash number is correct by simply checking that the number they used leads to the correct hash in that new block (correct hash = proof that work has been done). If it is correct then their computers will now also show BLOCK ZERO + BLOCK ONE.\n\nThe bitcoin blockchain has now been updated and will look like the following:\n\nBLOCK ZERO (date and time created) +\n\nBLOCK ONE (date and time created)(50 NEW BTC at 1EcKp4C… as mining block reward) +\nSolved HASH of Block one\n\nMAKING TRANSACTIONS\n\nLets say that participant A decides to spend their bitcoins right now by sending it to another bitcoin address. Participant C has given Participant A an address for him/her to send the bitcoins to (say address 18yACUJ3PaAWs41GoJU7aDZSTLEqwaBA4b).\n\nSo Participant A will now create a transaction on their computer. The transaction will be to:\n\nSEND 20 BTC from 1EcKp4Cv6QLV5kmCMEezERLXJYTaNVaLgs to 18yACUJ3PaAWs41GoJU7aDZSTLEqwaBA4b and send the CHANGE 29 BTC back to 1EcKp4Cv6QLV5kmCMEezERLXJYTaNVaLgs, and give 1 BTC as the transaction fee to be sent to the miner that solves the next block.\n\nThis transaction will immediately enter the memory pool (called mempool) which can be picked up by any of the other miners in the network.\n\nNow lets assume all three Participants A, B and C continue to try to solve the next block of the bitcoin blockchain called BLOCK TWO.\n\nTo do this they would take the current blockchain and then add any transactions they like from the mempool to create a new blockchain that includes BLOCK ZERO and BLOCK ONE and BLOCK TWO, which is then expressed as a ‘block two computer number’. They will then attempt to solve the new block like before. None of the miners are required to add any transactions from the mempool and can continue to mine an empty block if they wanted, but they usually want to add transactions because they will receive the transaction fee that Participant A has included in the transaction.\n\nSo lets now assume this time Participant B successfully solves the next block. \n\nThe bitcoin blockchain will now look like the following:\n\nBLOCK ZERO (date and time created) +\n\nBLOCK ONE (date and time created)(50 NEW BTC at 1EcKp4C… as mining block reward) +\nSolved HASH of Block one +\n\nBLOCK TWO (date and time created)(20 BTC at 18yACU…. (1 confirmation) moved from 1EcKp4C…; 29 BTC at 1EcKp4C... (1 confirmation) moved from 1EcKp4C…; 1 BTC at miners address 14pP4zDq… as transaction fee reward moved from 1EcKp4C…; and 50 NEW BTC at miners address 14pP4zDq… as mining block reward) +\nSolved HASH of Block two\n\nA real world example of a ‘Solved HASH of Block #593468’ of the bitcoin blockchain is shown below (it is a hexadecimal base-16 number containing exactly 64 characters): \n\n00000000000000000014fcb29e6e3b0ead3bd2e307d7f619a935f1d5323e9013\n\nThere is a lot more to all of this but this is the gist of what bitcoin mining and solving blocks involves. The entire system has been designed to be very secure and very stable and has been in continuous improvement since it started. A point to highlight is that only so many bitcoins can be added at a certain time and the rate of new bitcoins that can be added is halved about every four years. This is where bitcoin’s programmed scarcity comes from and is a major reason why it is so valuable. There will only ever be a certain maximum number of bitcoins on the planet and never anymore. The total number of all the bitcoins in the world is currently over 87% of its maximum possible number.\n\nA FINAL LOOK AT TRANSACTIONS\n\nWhen a transaction is created, the software you use will do a number of things. The most important of these is that it will sign the transaction with the bitcoin private key and then it will broadcast the transaction to the network. \n\nThe way your computer proves to the network that you are the rightful owner of the bitcoins stored at a particular bitcoin public address is by using one way hashes together with your bitcoin private key. And it does this without revealing your bitcoin private key to anyone except yourself.\n\nTo picture how this is possible, simply go back to our previous example of how your bitcoin private key was hashed to create the bitcoin public address. Now instead of:\n\nRandom number > then creates Bitcoin private key [then uses one way hash] > to create Bitcoin public address\n\nWe simply add ONE more hash step in between the bitcoin private key and bitcoin public address so that we have:\n\nRandom number > then creates Bitcoin private key [then uses one way hash] > to create SIGNATURE [then uses another one way hash] > to create Bitcoin public address\n\nNow it is possible to show the network your SIGNATURE without revealing your bitcoin private key while still proving that you are the owner of the bitcoin private key. In practice, there is more to the signing process (such as public keys), and each signature will only work specifically to a particular transaction you have created, but you get the idea. \n\nAs soon as you have created the transaction and the bitcoin network has checked that it is valid, your transaction will enter the mempool in order to be picked up by a miner, and then eventually added to the next block of the blockchain.\n\nBitcoin transactions therefore can happen securely and discretely, with no need for you trust any particular third party (such as banking institutions). You only need to trust that your own creation, storage and transaction steps used to create and send the bitcoins were secure; and that the network of miners maintaining the network will continue to mine new blocks the way they have always mined them since the very beginning.\n\n\nWritten by Bitgoldwallet.com owner\n\nSlight inaccuracies explained:\n\n* The actual random number only needs to be between 2128 (2 to the power of 128) and 2256 (2 to the power of 256) to meet unbreakable cryptography standards. This is roughly equal to a number containing between 39 and 78 numbers (decimal numbers).\n\n** Not every miner who takes part in the bitcoin network needs to be highly invested. Many smaller miners who work as part of a larger mining pool have not necessarily spent huge amounts of money on their equipment. Many mining groups however are heavily invested and they are located all over the world.\n\n*** The real bitcoin blockchain was originally mined mainly by its creator/s (Satoshi Nakamoto) for a period of up to 12 months before any significant number of other participants joined the network. The first block was mined on the 3 Jan 2009 and the first open source bitcoin client (or program) was released to the public on the 9 Jan 2009. The first bitcoin transaction was made on the 12 Jan 2009, about 10 days after the first block was mined. The huge majority of the estimated 1.6 million or so bitcoins which was mined in 2009 have never been moved and it is believed that the private keys to these have been lost.\n\n**** The way the actual bitcoin mining difficulty is set is not by requiring the hashed number such as 00000000000000000014fcb29e6e3b0ead3bd2e307d7f619a935f1d5323e9013 to have a certain number of consecutive zeros in front of it, but for it to be smaller than a certain number that happens to have a lot of consecutive zeros in front of it. So for the above example, the hashed number might just need to be a number smaller than say 0000000000000000001500000000000000000000000000000000000000000000. Because of this, the difficulty can be set quite precisely. \n\nColour scheme explained:\n\nGreen text = real world examples of bitcoin public addresses, private keys and hashes\n\nBlue text = made up examples of bitcoin public addresses, private keys, hashes, names and blockchain data used to make explaining how bitcoin works easier to understand\n\nEnd of article",
"json_metadata": "{\"tags\":[\"bitcoin\",\"cryptocurrency\",\"bitgold\",\"bitgoldwallet\"],\"app\":\"steemit/0.2\",\"format\":\"markdown\"}"
}
]
}bitgoldwalletpublished a new post: bitcoin-a-simple-explanation2020/04/24 02:38:00
bitgoldwalletpublished a new post: bitcoin-a-simple-explanation
2020/04/24 02:38:00
| parent author | |
| parent permlink | blockchain |
| author | bitgoldwallet |
| permlink | bitcoin-a-simple-explanation |
| title | BITCOIN: A SIMPLE EXPLANATION |
| body | WWW.BITGOLDWALLET.COM/downloads.html PDF AVAILABLE DOWNLOAD (FROM THE 17 APRIL 2020) Officially published via the website on Friday 17 April 2020 How does bitcoin work? This article will try to explain bitcoin using words and examples which are easy to understand. To achieve this, the explanation may be very slightly inaccurate in some places, however this will make it easier to understand. By the end of this article, you will hopefully have a better understanding of bitcoin. PART 1.1 : BITCOIN PUBLIC ADDRESSES The first basic part of bitcoin which needs to be understood is what bitcoin public addresses are, how they are created, and how they work together with bitcoin private keys. A bitcoin public address is basically like a bank account number which holds people’s bitcoins. An example of what it may look like is: 16er32qQe1Xi5ZEbqxvWJJN4GKC9kYnp1i A real bitcoin public address like the one shown above is made up of capital and lowercase letters, as well as numbers that are arranged in a specific way. In our simple explanation, I will instead give an example where 10 NUMBERS are used to represent a bitcoin public address. So our example bitcoin public address looks like the below: 8104940784 In order to receive bitcoins, you need to have a bitcoin public address which the bitcoin computer wallet program has created. This is the ‘thing’ you give to other people for them to send you the bitcoins. So how are bitcoin public addresses created? PART 1.2: BITCOIN PRIVATE KEYS A bitcoin public address is always created using a bitcoin private key. An example of what a bitcoin private key may look like is: L4iLhJzUAvNfa6x3wyYGV9N6fCR3cMXN7EJ7RiC5ct4dZjmdhSmd A real bitcoin private key like the one shown above is made up of capital and lowercase letters, as well as numbers that are arranged in a specific way. In our explanation, I will instead give an example where 20 NUMBERS are used to represent a bitcoin private key. So our example bitcoin private key looks like the below: 16503429214399795533 To create a bitcoin private key, you would use a bitcoin computer wallet program. This bitcoin private key is like a password to your bitcoin public address that lets you send the bitcoins from the bitcoin public address you currently own to another person’s bitcoin public address. SO HOW ARE BITCOIN PRIVATE KEYS CREATED? This is where the magic starts. All bitcoin private keys start as a very LARGE and very RANDOM number that is created by the bitcoin computer wallet program. This random number might be between 100 – 1000 numbers long or longer*. Think of a number so large that it is impossible for anyone or anything to guess this number. Imagine the entire universe was filled with computers placed side by side, all of them turned on and all of them repeatedly trying to guess this number, for all time and still failing. This is more or less the number that your computer creates. The computer program you use will then convert this random number to a bitcoin private key. To a computer, all data is numbers represented by zeros and ones. So it can be seen that a computer program can easily convert any random number to a bitcoin private key with the correct formatting or structure. The main thing to understand is that the bitcoin private key is infact a completely random set of characters and numbers. No one else on the planet knows the bitcoin private key except you because you created it randomly on your computer. If you created the bitcoin private key and only you know it, then this means you own the bitcoin private key. (Note: in reality, security is a massive issue with the creation of bitcoin private keys due to the risk of this data being stolen and spied on, so many people, including beginners let reputable cryptocurrency exchanges handle the storage and creation of their bitcoin private keys for them). So how is the bitcoin private key converted to the bitcoin public address? The bitcoin computer wallet program does this by using an exact formula known as a SHA256 hash together with other steps. The formula used is one-way, meaning that once the bitcoin public address is created, no one can use the bitcoin public address to work out what the private key was. And the formula is always the same and always gets the same result for the same original character string. In cryptography and in bitcoin, a one way hash like the SHA256 hash shown above is very important and is used a lot. In our explanation, instead of using the SHA256 hash; to make the idea easier to understand, I will use a simple one way formula (or hash) which I have made up so you can see how the one way aspect might work. We will call this hash the MU-hash (Made up hash): Our example MU-hash = 1) Take the first set of numbers, then 2) multiply this by 3141592654, then 3) remove the first 5 numbers from the result, and then 4) repeat this process 1000 times, and then after this is done, 5) only show the first 10 numbers and remove all the other numbers. To simplify this further so that this can actually be done in an example, we will replace 4) repeat this process 1000 times with 4) repeat this process one time. Ok. So to summarize PART 1, the computer wallet program creates: Random number > then creates Bitcoin private key [then uses one way hash] > to create Bitcoin public address OK. So now we can start our example: Start with Bitcoin private key = 16503429214399795533 Then hash this private key with our MU-hash = 1 & 2: 16503429214399795533 x 3141592654 = 51847051985767388665574814582 3: 51847051985767388665574814582 (remove first 5 numbers) = 051985767388665574814582 [take note that it is possible for zeros to be in the front of the number, and that it is rarer for these resulting numbers to have many consecutive zeros in front of it] 4: (repeat this process one time) = 051985767388665574814582 x 3141592654 = 163318104940784532700178223280628 (then remove first 5 numbers) = 8104940784532700178223280628 5: (only show first 10 numbers and remove all the other numbers) = 8104940784 = Bitcoin public address SO we are left with: Bitcoin private key = 16503429214399795533 (and) Bitcoin public address = 8104940784 Every single time we do this one way MU-hash on the same original bitcoin private key we will get the same bitcoin public address. And looking only at the bitcoin public address, it is impossible to calculate or guess what the original bitcoin private key was. For our simple example though with the MU-hash, a powerful computer organization might be able to guess or calculate our bitcoin private key through random guessing (because our numbers are fairly small) but for the real bitcoin private key this would be impossible to do. At its simplest level, this is how bitcoin public addresses and bitcoin private keys work. If you know the bitcoin private key, you can always prove to the network that you own the bitcoin public address which contains the bitcoins and the network will always let you move the bitcoins even though they don’t know who you are. You can see now how anyone on the planet can, in the safety of their own homes, create their own bitcoin public addresses to give to people in order to receive and send bitcoins from. This is part of what makes bitcoin a decentralized digital currency which allows anyone to take part in, and which is hard to restrict or ban. PART 2: THE BITCOIN BLOCKCHAIN So the bitcoin private key and bitcoin public address holds the actual bitcoins. And you can see that these can be created and stored without limit by anyone knowledgeable enough. However, if we only have these, the bitcoins won’t be of any use. We need a payment network which lets you send your bitcoins to different bitcoin addresses. The bitcoin blockchain serves this purpose. The bitcoin blockchain is basically the list (or ledger) of all the transactions and all the used bitcoin public addresses that has ever been made in the bitcoin network. It is maintained by a large number of highly invested people and groups who take part in the network (known as miners)**. The easiest way to understand the bitcoin blockchain is to go back to the very beginning of bitcoin in the year 2009 at Block 0 known as the genesis block and then slowly build up from there. I will only need to describe up to Block 2 for you to get a good enough idea. I want to emphasize that these things didn’t happen as described for the actual bitcoin blockchain but is rather a hypothetical scenario which fairly accurately explains how bitcoin mining and bitcoin transactions work***. BLOCK ZERO – GENESIS BLOCK BLOCK ZERO basically has no transaction data. But it still has data such as the date it was created and some other data. This blockchain data is stored on the computers of individual people who have downloaded and run the original bitcoin wallet program (called nodes and/or miners). In our example we will assume there are only 3 participants which make up all the users in the network: Participants A, B and C. In the future many new participants will join the network. The original bitcoin wallet program and all future variations of the program is free for anyone to download and use. Each of these 3 participants would have had the option to mine bitcoins. And they would have been able to create bitcoin public addresses and private keys like described earlier. When they ran the mining software for the first time at least one bitcoin public address was created by each of them. So assume: Participant A has created bitcoin public address 1EcKp4Cv6QLV5kmCMEezERLXJYTaNVaLgs Participant B has created bitcoin public address 14pP4zDquF3NE3BSjjpNbsCTz9tDs9cSN8 Participant C has created bitcoin public address 1J62KZfV2Z8653zv3ydW88YgjBZySj7CQm Now all 3 Participants activate their mining software. Since there are currently no bitcoins in all the world, BLOCK ONE, the next block of the blockchain will not contain any transactions showing any movement of bitcoins, but it will show a balance of 50 new bitcoins created into one of the 3 bitcoin public addresses shown above owned by Participant A, B or C. New bitcoins enter the world after every mining round. The way the software decides which miner gets the 50 new bitcoins is based on a ‘proof of work’ system. On average new bitcoins enter the world every 10 minutes and this rate is set by the computer software. HOW MINING WORKS So we will assume that all 3 participants turn on their mining software at the same time and everyone is using the exact same type of computer. These 3 miners all have the same copy of the bitcoin blockchain which in its entirety is currently BLOCK ZERO. The mining software now takes the BLOCK ZERO file data and adds the empty BLOCK ONE file data to it and then expresses this file as a number (we will call this the ‘block one computer number’). Remember that all data files on a computer are zeros and ones. Then the software begins the mining process by taking a random number (called a nonce) and adding this random number to the end of the ‘block one computer number’. Then it creates a one way (SHA256) hash of this new number and the result is recorded somewhere. Basically the rules of the program states that if this resulting number (or hash) has a certain number of consecutive zeros in front of it, then it proves that that computer has completed the ‘proof of work’ and the software automatically creates the 50 new bitcoins into that participant miner’s bitcoin public address. If the random number doesn’t lead to the required number of consecutive zeros then the computer tries again until it does find one. The proof of work here lies in the fact that mathematically, it takes a certain number of random hashes by the computer before the computer will find one that meets the difficulty requirement of having a hash-result with the required number of consecutive zeros in front of it. Every 2 weeks this difficulty is automatically adjusted by the bitcoin computer program which all the miners run by adding or reducing the number of consecutive zeros that are needed before new bitcoins can be awarded. The more zeros there are, the more difficult it is to solve****. The difficulty is changed so that on average about every 10 minutes a new block is solved, and this happens regardless of how many or how few computers are mining. In our example each of the 3 miners have an equal chance of finding the correct hash first because everyone is running the same computer type and so each computer will create the same number of hashes per second. In modern day bitcoin mining though, different miners have vastly different hash producing abilities and this will directly impact on how many blocks they will solve compared to other miners. The more hashes they can make compared to the rest of the miners, the more blocks they will solve. Also, in modern day mining the number of hashes required is so huge now that only mining pools or centres with millions and millions of dollars worth of dedicated mining hardware in them can successfully solve new blocks. So we will assume Participant A was the first to solve BLOCK ONE and their bitcoin wallet software now shows 50 bitcoins at address 1EcKp4Cv6QLV5kmCMEezERLXJYTaNVaLgs. Participant A will now broadcast this information to the entire network and Participants B and C will check that Participant A’s hash number is correct by simply checking that the number they used leads to the correct hash in that new block (correct hash = proof that work has been done). If it is correct then their computers will now also show BLOCK ZERO + BLOCK ONE. The bitcoin blockchain has now been updated and will look like the following: BLOCK ZERO (date and time created) + BLOCK ONE (date and time created)(50 NEW BTC at 1EcKp4C… as mining block reward) + Solved HASH of Block one MAKING TRANSACTIONS Lets say that participant A decides to spend their bitcoins right now by sending it to another bitcoin address. Participant C has given Participant A an address for him/her to send the bitcoins to (say address 18yACUJ3PaAWs41GoJU7aDZSTLEqwaBA4b). So Participant A will now create a transaction on their computer. The transaction will be to: SEND 20 BTC from 1EcKp4Cv6QLV5kmCMEezERLXJYTaNVaLgs to 18yACUJ3PaAWs41GoJU7aDZSTLEqwaBA4b and send the CHANGE 29 BTC back to 1EcKp4Cv6QLV5kmCMEezERLXJYTaNVaLgs, and give 1 BTC as the transaction fee to be sent to the miner that solves the next block. This transaction will immediately enter the memory pool (called mempool) which can be picked up by any of the other miners in the network. Now lets assume all three Participants A, B and C continue to try to solve the next block of the bitcoin blockchain called BLOCK TWO. To do this they would take the current blockchain and then add any transactions they like from the mempool to create a new blockchain that includes BLOCK ZERO and BLOCK ONE and BLOCK TWO, which is then expressed as a ‘block two computer number’. They will then attempt to solve the new block like before. None of the miners are required to add any transactions from the mempool and can continue to mine an empty block if they wanted, but they usually want to add transactions because they will receive the transaction fee that Participant A has included in the transaction. So lets now assume this time Participant B successfully solves the next block. The bitcoin blockchain will now look like the following: BLOCK ZERO (date and time created) + BLOCK ONE (date and time created)(50 NEW BTC at 1EcKp4C… as mining block reward) + Solved HASH of Block one + BLOCK TWO (date and time created)(20 BTC at 18yACU…. (1 confirmation) moved from 1EcKp4C…; 29 BTC at 1EcKp4C... (1 confirmation) moved from 1EcKp4C…; 1 BTC at miners address 14pP4zDq… as transaction fee reward moved from 1EcKp4C…; and 50 NEW BTC at miners address 14pP4zDq… as mining block reward) + Solved HASH of Block two A real world example of a ‘Solved HASH of Block #593468’ of the bitcoin blockchain is shown below (it is a hexadecimal base-16 number containing exactly 64 characters): 00000000000000000014fcb29e6e3b0ead3bd2e307d7f619a935f1d5323e9013 There is a lot more to all of this but this is the gist of what bitcoin mining and solving blocks involves. The entire system has been designed to be very secure and very stable and has been in continuous improvement since it started. A point to highlight is that only so many bitcoins can be added at a certain time and the rate of new bitcoins that can be added is halved about every four years. This is where bitcoin’s programmed scarcity comes from and is a major reason why it is so valuable. There will only ever be a certain maximum number of bitcoins on the planet and never anymore. The total number of all the bitcoins in the world is currently over 87% of its maximum possible number. A FINAL LOOK AT TRANSACTIONS When a transaction is created, the software you use will do a number of things. The most important of these is that it will sign the transaction with the bitcoin private key and then it will broadcast the transaction to the network. The way your computer proves to the network that you are the rightful owner of the bitcoins stored at a particular bitcoin public address is by using one way hashes together with your bitcoin private key. And it does this without revealing your bitcoin private key to anyone except yourself. To picture how this is possible, simply go back to our previous example of how your bitcoin private key was hashed to create the bitcoin public address. Now instead of: Random number > then creates Bitcoin private key [then uses one way hash] > to create Bitcoin public address We simply add ONE more hash step in between the bitcoin private key and bitcoin public address so that we have: Random number > then creates Bitcoin private key [then uses one way hash] > to create SIGNATURE [then uses another one way hash] > to create Bitcoin public address Now it is possible to show the network your SIGNATURE without revealing your bitcoin private key while still proving that you are the owner of the bitcoin private key. In practice, there is more to the signing process (such as public keys), and each signature will only work specifically to a particular transaction you have created, but you get the idea. As soon as you have created the transaction and the bitcoin network has checked that it is valid, your transaction will enter the mempool in order to be picked up by a miner, and then eventually added to the next block of the blockchain. Bitcoin transactions therefore can happen securely and discretely, with no need for you trust any particular third party (such as banking institutions). You only need to trust that your own creation, storage and transaction steps used to create and send the bitcoins were secure; and that the network of miners maintaining the network will continue to mine new blocks the way they have always mined them since the very beginning. Written by Bitgoldwallet.com owner Slight inaccuracies explained: * The actual random number only needs to be between 2128 (2 to the power of 128) and 2256 (2 to the power of 256) to meet unbreakable cryptography standards. This is roughly equal to a number containing between 39 and 78 numbers (decimal numbers). ** Not every miner who takes part in the bitcoin network needs to be highly invested. Many smaller miners who work as part of a larger mining pool have not necessarily spent huge amounts of money on their equipment. Many mining groups however are heavily invested and they are located all over the world. *** The real bitcoin blockchain was originally mined mainly by its creator/s (Satoshi Nakamoto) for a period of up to 12 months before any significant number of other participants joined the network. The first block was mined on the 3 Jan 2009 and the first open source bitcoin client (or program) was released to the public on the 9 Jan 2009. The first bitcoin transaction was made on the 12 Jan 2009, about 10 days after the first block was mined. The huge majority of the estimated 1.6 million or so bitcoins which was mined in 2009 have never been moved and it is believed that the private keys to these have been lost. **** The way the actual bitcoin mining difficulty is set is not by requiring the hashed number such as 00000000000000000014fcb29e6e3b0ead3bd2e307d7f619a935f1d5323e9013 to have a certain number of consecutive zeros in front of it, but for it to be smaller than a certain number that happens to have a lot of consecutive zeros in front of it. So for the above example, the hashed number might just need to be a number smaller than say 0000000000000000001500000000000000000000000000000000000000000000. Because of this, the difficulty can be set quite precisely. Colour scheme explained: Green text = real world examples of bitcoin public addresses, private keys and hashes Blue text = made up examples of bitcoin public addresses, private keys, hashes, names and blockchain data used to make explaining how bitcoin works easier to understand End of article |
| json metadata | {"tags":["bitcoin","cryptocurrency","bitgold","bitgoldwallet"],"app":"steemit/0.2","format":"markdown"} |
| Transaction Info | Block #42792155/Trx 3996bb9134b2eb1087bc4fc5d8d1df5610bd48fa |
View Raw JSON Data
{
"trx_id": "3996bb9134b2eb1087bc4fc5d8d1df5610bd48fa",
"block": 42792155,
"trx_in_block": 10,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-24T02:38:00",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "blockchain",
"author": "bitgoldwallet",
"permlink": "bitcoin-a-simple-explanation",
"title": "BITCOIN: A SIMPLE EXPLANATION",
"body": "WWW.BITGOLDWALLET.COM/downloads.html PDF AVAILABLE DOWNLOAD (FROM THE 17 APRIL 2020)\n\nOfficially published via the website on Friday 17 April 2020\n\nHow does bitcoin work? This article will try to explain bitcoin using words and examples which are easy to understand. To achieve this, the explanation may be very slightly inaccurate in some places, however this will make it easier to understand. By the end of this article, you will hopefully have a better understanding of bitcoin.\n\nPART 1.1 : BITCOIN PUBLIC ADDRESSES\n\nThe first basic part of bitcoin which needs to be understood is what bitcoin public addresses are, how they are created, and how they work together with bitcoin private keys. A bitcoin public address is basically like a bank account number which holds people’s bitcoins. An example of what it may look like is: \n\n16er32qQe1Xi5ZEbqxvWJJN4GKC9kYnp1i\n\nA real bitcoin public address like the one shown above is made up of capital and lowercase letters, as well as numbers that are arranged in a specific way.\n\nIn our simple explanation, I will instead give an example where 10 NUMBERS are used to represent a bitcoin public address. So our example bitcoin public address looks like the below:\n\n8104940784\n\nIn order to receive bitcoins, you need to have a bitcoin public address which the bitcoin computer wallet program has created. This is the ‘thing’ you give to other people for them to send you the bitcoins. So how are bitcoin public addresses created?\n\nPART 1.2: BITCOIN PRIVATE KEYS \n\nA bitcoin public address is always created using a bitcoin private key. An example of what a bitcoin private key may look like is: \n\nL4iLhJzUAvNfa6x3wyYGV9N6fCR3cMXN7EJ7RiC5ct4dZjmdhSmd\n\nA real bitcoin private key like the one shown above is made up of capital and lowercase letters, as well as numbers that are arranged in a specific way. \n\nIn our explanation, I will instead give an example where 20 NUMBERS are used to represent a bitcoin private key. So our example bitcoin private key looks like the below:\n\n16503429214399795533\n\nTo create a bitcoin private key, you would use a bitcoin computer wallet program. This bitcoin private key is like a password to your bitcoin public address that lets you send the bitcoins from the bitcoin public address you currently own to another person’s bitcoin public address.\n\nSO HOW ARE BITCOIN PRIVATE KEYS CREATED? This is where the magic starts.\n\nAll bitcoin private keys start as a very LARGE and very RANDOM number that is created by the bitcoin computer wallet program. This random number might be between 100 – 1000 numbers long or longer*. Think of a number so large that it is impossible for anyone or anything to guess this number. Imagine the entire universe was filled with computers placed side by side, all of them turned on and all of them repeatedly trying to guess this number, for all time and still failing. This is more or less the number that your computer creates.\n\nThe computer program you use will then convert this random number to a bitcoin private key. To a computer, all data is numbers represented by zeros and ones. So it can be seen that a computer program can easily convert any random number to a bitcoin private key with the correct formatting or structure.\n\nThe main thing to understand is that the bitcoin private key is infact a completely random set of characters and numbers. No one else on the planet knows the bitcoin private key except you because you created it randomly on your computer. If you created the bitcoin private key and only you know it, then this means you own the bitcoin private key.\n\n(Note: in reality, security is a massive issue with the creation of bitcoin private keys due to the risk of this data being stolen and spied on, so many people, including beginners let reputable cryptocurrency exchanges handle the storage and creation of their bitcoin private keys for them).\n\nSo how is the bitcoin private key converted to the bitcoin public address?\n\nThe bitcoin computer wallet program does this by using an exact formula known as a SHA256 hash together with other steps. The formula used is one-way, meaning that once the bitcoin public address is created, no one can use the bitcoin public address to work out what the private key was. And the formula is always the same and always gets the same result for the same original character string.\n\nIn cryptography and in bitcoin, a one way hash like the SHA256 hash shown above is very important and is used a lot.\n\nIn our explanation, instead of using the SHA256 hash; to make the idea easier to understand, I will use a simple one way formula (or hash) which I have made up so you can see how the one way aspect might work. We will call this hash the MU-hash (Made up hash):\n\nOur example MU-hash = \n\n1) Take the first set of numbers, then 2) multiply this by 3141592654, then 3) remove the first 5 numbers from the result, and then 4) repeat this process 1000 times, and then after this is done, 5) only show the first 10 numbers and remove all the other numbers.\n\nTo simplify this further so that this can actually be done in an example, we will replace 4) repeat this process 1000 times with 4) repeat this process one time.\n\nOk. So to summarize PART 1, the computer wallet program creates:\n\nRandom number > then creates Bitcoin private key [then uses one way hash] > to create Bitcoin public address\n\nOK. So now we can start our example:\n\nStart with Bitcoin private key = 16503429214399795533\n\nThen hash this private key with our MU-hash = \n\n1 & 2: 16503429214399795533 x 3141592654 = 51847051985767388665574814582\n\n3: 51847051985767388665574814582 (remove first 5 numbers) = 051985767388665574814582 [take note that it is possible for zeros to be in the front of the number, and that it is rarer for these resulting numbers to have many consecutive zeros in front of it]\n\n4: (repeat this process one time) = 051985767388665574814582 x 3141592654 = 163318104940784532700178223280628 (then remove first 5 numbers) = 8104940784532700178223280628\n\n5: (only show first 10 numbers and remove all the other numbers) = 8104940784 = Bitcoin public address\n\nSO we are left with:\n\nBitcoin private key = 16503429214399795533 (and) \nBitcoin public address = 8104940784\n\nEvery single time we do this one way MU-hash on the same original bitcoin private key we will get the same bitcoin public address. And looking only at the bitcoin public address, it is impossible to calculate or guess what the original bitcoin private key was. For our simple example though with the MU-hash, a powerful computer organization might be able to guess or calculate our bitcoin private key through random guessing (because our numbers are fairly small) but for the real bitcoin private key this would be impossible to do.\n\nAt its simplest level, this is how bitcoin public addresses and bitcoin private keys work. If you know the bitcoin private key, you can always prove to the network that you own the bitcoin public address which contains the bitcoins and the network will always let you move the bitcoins even though they don’t know who you are.\n\nYou can see now how anyone on the planet can, in the safety of their own homes, create their own bitcoin public addresses to give to people in order to receive and send bitcoins from. This is part of what makes bitcoin a decentralized digital currency which allows anyone to take part in, and which is hard to restrict or ban. \n\nPART 2: THE BITCOIN BLOCKCHAIN\n\nSo the bitcoin private key and bitcoin public address holds the actual bitcoins. And you can see that these can be created and stored without limit by anyone knowledgeable enough. However, if we only have these, the bitcoins won’t be of any use. We need a payment network which lets you send your bitcoins to different bitcoin addresses.\n\nThe bitcoin blockchain serves this purpose. The bitcoin blockchain is basically the list (or ledger) of all the transactions and all the used bitcoin public addresses that has ever been made in the bitcoin network. It is maintained by a large number of highly invested people and groups who take part in the network (known as miners)**.\n\nThe easiest way to understand the bitcoin blockchain is to go back to the very beginning of bitcoin in the year 2009 at Block 0 known as the genesis block and then slowly build up from there. I will only need to describe up to Block 2 for you to get a good enough idea. I want to emphasize that these things didn’t happen as described for the actual bitcoin blockchain but is rather a hypothetical scenario which fairly accurately explains how bitcoin mining and bitcoin transactions work***.\n\nBLOCK ZERO – GENESIS BLOCK\n\nBLOCK ZERO basically has no transaction data. But it still has data such as the date it was created and some other data. This blockchain data is stored on the computers of individual people who have downloaded and run the original bitcoin wallet program (called nodes and/or miners). In our example we will assume there are only 3 participants which make up all the users in the network: Participants A, B and C. In the future many new participants will join the network. The original bitcoin wallet program and all future variations of the program is free for anyone to download and use. \n\nEach of these 3 participants would have had the option to mine bitcoins. And they would have been able to create bitcoin public addresses and private keys like described earlier. \n\nWhen they ran the mining software for the first time at least one bitcoin public address was created by each of them. So assume:\n\nParticipant A has created bitcoin public address 1EcKp4Cv6QLV5kmCMEezERLXJYTaNVaLgs\n\nParticipant B has created bitcoin public address \n14pP4zDquF3NE3BSjjpNbsCTz9tDs9cSN8\n\nParticipant C has created bitcoin public address\n1J62KZfV2Z8653zv3ydW88YgjBZySj7CQm\n\nNow all 3 Participants activate their mining software. Since there are currently no bitcoins in all the world, BLOCK ONE, the next block of the blockchain will not contain any transactions showing any movement of bitcoins, but it will show a balance of 50 new bitcoins created into one of the 3 bitcoin public addresses shown above owned by Participant A, B or C. New bitcoins enter the world after every mining round. The way the software decides which miner gets the 50 new bitcoins is based on a ‘proof of work’ system. On average new bitcoins enter the world every 10 minutes and this rate is set by the computer software.\n\nHOW MINING WORKS\n\nSo we will assume that all 3 participants turn on their mining software at the same time and everyone is using the exact same type of computer. These 3 miners all have the same copy of the bitcoin blockchain which in its entirety is currently BLOCK ZERO. The mining software now takes the BLOCK ZERO file data and adds the empty BLOCK ONE file data to it and then expresses this file as a number (we will call this the ‘block one computer number’). Remember that all data files on a computer are zeros and ones. Then the software begins the mining process by taking a random number (called a nonce) and adding this random number to the end of the ‘block one computer number’. Then it creates a one way (SHA256) hash of this new number and the result is recorded somewhere. Basically the rules of the program states that if this resulting number (or hash) has a certain number of consecutive zeros in front of it, then it proves that that computer has completed the ‘proof of work’ and the software automatically creates the 50 new bitcoins into that participant miner’s bitcoin public address. If the random number doesn’t lead to the required number of consecutive zeros then the computer tries again until it does find one. The proof of work here lies in the fact that mathematically, it takes a certain number of random hashes by the computer before the computer will find one that meets the difficulty requirement of having a hash-result with the required number of consecutive zeros in front of it.\n\nEvery 2 weeks this difficulty is automatically adjusted by the bitcoin computer program which all the miners run by adding or reducing the number of consecutive zeros that are needed before new bitcoins can be awarded. The more zeros there are, the more difficult it is to solve****. The difficulty is changed so that on average about every 10 minutes a new block is solved, and this happens regardless of how many or how few computers are mining.\n\nIn our example each of the 3 miners have an equal chance of finding the correct hash first because everyone is running the same computer type and so each computer will create the same number of hashes per second. In modern day bitcoin mining though, different miners have vastly different hash producing abilities and this will directly impact on how many blocks they will solve compared to other miners. The more hashes they can make compared to the rest of the miners, the more blocks they will solve. Also, in modern day mining the number of hashes required is so huge now that only mining pools or centres with millions and millions of dollars worth of dedicated mining hardware in them can successfully solve new blocks. \n\nSo we will assume Participant A was the first to solve BLOCK ONE and their bitcoin wallet software now shows 50 bitcoins at address 1EcKp4Cv6QLV5kmCMEezERLXJYTaNVaLgs. Participant A will now broadcast this information to the entire network and Participants B and C will check that Participant A’s hash number is correct by simply checking that the number they used leads to the correct hash in that new block (correct hash = proof that work has been done). If it is correct then their computers will now also show BLOCK ZERO + BLOCK ONE.\n\nThe bitcoin blockchain has now been updated and will look like the following:\n\nBLOCK ZERO (date and time created) +\n\nBLOCK ONE (date and time created)(50 NEW BTC at 1EcKp4C… as mining block reward) +\nSolved HASH of Block one\n\nMAKING TRANSACTIONS\n\nLets say that participant A decides to spend their bitcoins right now by sending it to another bitcoin address. Participant C has given Participant A an address for him/her to send the bitcoins to (say address 18yACUJ3PaAWs41GoJU7aDZSTLEqwaBA4b).\n\nSo Participant A will now create a transaction on their computer. The transaction will be to:\n\nSEND 20 BTC from 1EcKp4Cv6QLV5kmCMEezERLXJYTaNVaLgs to 18yACUJ3PaAWs41GoJU7aDZSTLEqwaBA4b and send the CHANGE 29 BTC back to 1EcKp4Cv6QLV5kmCMEezERLXJYTaNVaLgs, and give 1 BTC as the transaction fee to be sent to the miner that solves the next block.\n\nThis transaction will immediately enter the memory pool (called mempool) which can be picked up by any of the other miners in the network.\n\nNow lets assume all three Participants A, B and C continue to try to solve the next block of the bitcoin blockchain called BLOCK TWO.\n\nTo do this they would take the current blockchain and then add any transactions they like from the mempool to create a new blockchain that includes BLOCK ZERO and BLOCK ONE and BLOCK TWO, which is then expressed as a ‘block two computer number’. They will then attempt to solve the new block like before. None of the miners are required to add any transactions from the mempool and can continue to mine an empty block if they wanted, but they usually want to add transactions because they will receive the transaction fee that Participant A has included in the transaction.\n\nSo lets now assume this time Participant B successfully solves the next block. \n\nThe bitcoin blockchain will now look like the following:\n\nBLOCK ZERO (date and time created) +\n\nBLOCK ONE (date and time created)(50 NEW BTC at 1EcKp4C… as mining block reward) +\nSolved HASH of Block one +\n\nBLOCK TWO (date and time created)(20 BTC at 18yACU…. (1 confirmation) moved from 1EcKp4C…; 29 BTC at 1EcKp4C... (1 confirmation) moved from 1EcKp4C…; 1 BTC at miners address 14pP4zDq… as transaction fee reward moved from 1EcKp4C…; and 50 NEW BTC at miners address 14pP4zDq… as mining block reward) +\nSolved HASH of Block two\n\nA real world example of a ‘Solved HASH of Block #593468’ of the bitcoin blockchain is shown below (it is a hexadecimal base-16 number containing exactly 64 characters): \n\n00000000000000000014fcb29e6e3b0ead3bd2e307d7f619a935f1d5323e9013\n\nThere is a lot more to all of this but this is the gist of what bitcoin mining and solving blocks involves. The entire system has been designed to be very secure and very stable and has been in continuous improvement since it started. A point to highlight is that only so many bitcoins can be added at a certain time and the rate of new bitcoins that can be added is halved about every four years. This is where bitcoin’s programmed scarcity comes from and is a major reason why it is so valuable. There will only ever be a certain maximum number of bitcoins on the planet and never anymore. The total number of all the bitcoins in the world is currently over 87% of its maximum possible number.\n\nA FINAL LOOK AT TRANSACTIONS\n\nWhen a transaction is created, the software you use will do a number of things. The most important of these is that it will sign the transaction with the bitcoin private key and then it will broadcast the transaction to the network. \n\nThe way your computer proves to the network that you are the rightful owner of the bitcoins stored at a particular bitcoin public address is by using one way hashes together with your bitcoin private key. And it does this without revealing your bitcoin private key to anyone except yourself.\n\nTo picture how this is possible, simply go back to our previous example of how your bitcoin private key was hashed to create the bitcoin public address. Now instead of:\n\nRandom number > then creates Bitcoin private key [then uses one way hash] > to create Bitcoin public address\n\nWe simply add ONE more hash step in between the bitcoin private key and bitcoin public address so that we have:\n\nRandom number > then creates Bitcoin private key [then uses one way hash] > to create SIGNATURE [then uses another one way hash] > to create Bitcoin public address\n\nNow it is possible to show the network your SIGNATURE without revealing your bitcoin private key while still proving that you are the owner of the bitcoin private key. In practice, there is more to the signing process (such as public keys), and each signature will only work specifically to a particular transaction you have created, but you get the idea. \n\nAs soon as you have created the transaction and the bitcoin network has checked that it is valid, your transaction will enter the mempool in order to be picked up by a miner, and then eventually added to the next block of the blockchain.\n\nBitcoin transactions therefore can happen securely and discretely, with no need for you trust any particular third party (such as banking institutions). You only need to trust that your own creation, storage and transaction steps used to create and send the bitcoins were secure; and that the network of miners maintaining the network will continue to mine new blocks the way they have always mined them since the very beginning.\n\n\nWritten by Bitgoldwallet.com owner\n\nSlight inaccuracies explained:\n\n* The actual random number only needs to be between 2128 (2 to the power of 128) and 2256 (2 to the power of 256) to meet unbreakable cryptography standards. This is roughly equal to a number containing between 39 and 78 numbers (decimal numbers).\n\n** Not every miner who takes part in the bitcoin network needs to be highly invested. Many smaller miners who work as part of a larger mining pool have not necessarily spent huge amounts of money on their equipment. Many mining groups however are heavily invested and they are located all over the world.\n\n*** The real bitcoin blockchain was originally mined mainly by its creator/s (Satoshi Nakamoto) for a period of up to 12 months before any significant number of other participants joined the network. The first block was mined on the 3 Jan 2009 and the first open source bitcoin client (or program) was released to the public on the 9 Jan 2009. The first bitcoin transaction was made on the 12 Jan 2009, about 10 days after the first block was mined. The huge majority of the estimated 1.6 million or so bitcoins which was mined in 2009 have never been moved and it is believed that the private keys to these have been lost.\n\n**** The way the actual bitcoin mining difficulty is set is not by requiring the hashed number such as 00000000000000000014fcb29e6e3b0ead3bd2e307d7f619a935f1d5323e9013 to have a certain number of consecutive zeros in front of it, but for it to be smaller than a certain number that happens to have a lot of consecutive zeros in front of it. So for the above example, the hashed number might just need to be a number smaller than say 0000000000000000001500000000000000000000000000000000000000000000. Because of this, the difficulty can be set quite precisely. \n\nColour scheme explained:\n\nGreen text = real world examples of bitcoin public addresses, private keys and hashes\n\nBlue text = made up examples of bitcoin public addresses, private keys, hashes, names and blockchain data used to make explaining how bitcoin works easier to understand\n\nEnd of article",
"json_metadata": "{\"tags\":[\"bitcoin\",\"cryptocurrency\",\"bitgold\",\"bitgoldwallet\"],\"app\":\"steemit/0.2\",\"format\":\"markdown\"}"
}
]
}2020/04/24 02:36:54
2020/04/24 02:36:54
| parent author | bitgoldwallet |
| parent permlink | bitcoin-a-simple-explanation |
| author | cheetah |
| permlink | cheetah-re-bitgoldwalletbitcoin-a-simple-explanation |
| title | |
| body | Hi! Did you know that steemit.com is now censoring users and posts based on their opinions? All the posts of these users are gone! https://github.com/steemit/condenser/commit/3394af78127bdd8d037c2d49983b7b9491397296 Here's a list of some banned users: ```'roelandp', 'blocktrades', 'anyx', 'ausbitbank', 'gtg', 'themarkymark', 'lukestokes.mhth', 'netuoso', 'innerhive'``` See anyone you recognize? There could be more, they also have a remote IP ban list. Will you be censored next? |
| json metadata | |
| Transaction Info | Block #42792133/Trx d564a315634b3a8453ce4eca8f228ce0552537e2 |
View Raw JSON Data
{
"trx_id": "d564a315634b3a8453ce4eca8f228ce0552537e2",
"block": 42792133,
"trx_in_block": 11,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-24T02:36:54",
"op": [
"comment",
{
"parent_author": "bitgoldwallet",
"parent_permlink": "bitcoin-a-simple-explanation",
"author": "cheetah",
"permlink": "cheetah-re-bitgoldwalletbitcoin-a-simple-explanation",
"title": "",
"body": "Hi! Did you know that steemit.com is now censoring users and posts based on their opinions?\n All the posts of these users are gone!\nhttps://github.com/steemit/condenser/commit/3394af78127bdd8d037c2d49983b7b9491397296 \n\n Here's a list of some banned users:\n```'roelandp', 'blocktrades', 'anyx', 'ausbitbank', 'gtg', 'themarkymark', 'lukestokes.mhth', 'netuoso', 'innerhive'```\nSee anyone you recognize? There could be more, they also have a remote IP ban list.\n\nWill you be censored next?",
"json_metadata": ""
}
]
}bitgoldwalletpublished a new post: bitcoin-a-simple-explanation2020/04/24 02:36:45
bitgoldwalletpublished a new post: bitcoin-a-simple-explanation
2020/04/24 02:36:45
| parent author | |
| parent permlink | blockchain |
| author | bitgoldwallet |
| permlink | bitcoin-a-simple-explanation |
| title | BITCOIN: A SIMPLE EXPLANATION |
| body | WWW.BITGOLDWALLET.COM/downloads.html PDF AVAILABLE DOWNLOAD (FROM THE 17 APRIL 2020) Officially published via the website on Friday 17 April 2020 How does bitcoin work? This article will try to explain bitcoin using words and examples which are easy to understand. To achieve this, the explanation may be very slightly inaccurate in some places, however this will make it easier to understand. By the end of this article, you will hopefully have a better understanding of bitcoin. PART 1.1 : BITCOIN PUBLIC ADDRESSES The first basic part of bitcoin which needs to be understood is what bitcoin public addresses are, how they are created, and how they work together with bitcoin private keys. A bitcoin public address is basically like a bank account number which holds people’s bitcoins. An example of what it may look like is: 16er32qQe1Xi5ZEbqxvWJJN4GKC9kYnp1i A real bitcoin public address like the one shown above is made up of capital and lowercase letters, as well as numbers that are arranged in a specific way. In our simple explanation, I will instead give an example where 10 NUMBERS are used to represent a bitcoin public address. So our example bitcoin public address looks like the below: 8104940784 In order to receive bitcoins, you need to have a bitcoin public address which the bitcoin computer wallet program has created. This is the ‘thing’ you give to other people for them to send you the bitcoins. So how are bitcoin public addresses created? PART 1.2: BITCOIN PRIVATE KEYS A bitcoin public address is always created using a bitcoin private key. An example of what a bitcoin private key may look like is: L4iLhJzUAvNfa6x3wyYGV9N6fCR3cMXN7EJ7RiC5ct4dZjmdhSmd A real bitcoin private key like the one shown above is made up of capital and lowercase letters, as well as numbers that are arranged in a specific way. In our explanation, I will instead give an example where 20 NUMBERS are used to represent a bitcoin private key. So our example bitcoin private key looks like the below: 16503429214399795533 To create a bitcoin private key, you would use a bitcoin computer wallet program. This bitcoin private key is like a password to your bitcoin public address that lets you send the bitcoins from the bitcoin public address you currently own to another person’s bitcoin public address. SO HOW ARE BITCOIN PRIVATE KEYS CREATED? This is where the magic starts. All bitcoin private keys start as a very LARGE and very RANDOM number that is created by the bitcoin computer wallet program. This random number might be between 100 – 1000 numbers long or longer*. Think of a number so large that it is impossible for anyone or anything to guess this number. Imagine the entire universe was filled with computers placed side by side, all of them turned on and all of them repeatedly trying to guess this number, for all time and still failing. This is more or less the number that your computer creates. The computer program you use will then convert this random number to a bitcoin private key. To a computer, all data is numbers represented by zeros and ones. So it can be seen that a computer program can easily convert any random number to a bitcoin private key with the correct formatting or structure. The main thing to understand is that the bitcoin private key is infact a completely random set of characters and numbers. No one else on the planet knows the bitcoin private key except you because you created it randomly on your computer. If you created the bitcoin private key and only you know it, then this means you own the bitcoin private key. (Note: in reality, security is a massive issue with the creation of bitcoin private keys due to the risk of this data being stolen and spied on, so many people, including beginners let reputable cryptocurrency exchanges handle the storage and creation of their bitcoin private keys for them). So how is the bitcoin private key converted to the bitcoin public address? The bitcoin computer wallet program does this by using an exact formula known as a SHA256 hash together with other steps. The formula used is one-way, meaning that once the bitcoin public address is created, no one can use the bitcoin public address to work out what the private key was. And the formula is always the same and always gets the same result for the same original character string. In cryptography and in bitcoin, a one way hash like the SHA256 hash shown above is very important and is used a lot. In our explanation, instead of using the SHA256 hash; to make the idea easier to understand, I will use a simple one way formula (or hash) which I have made up so you can see how the one way aspect might work. We will call this hash the MU-hash (Made up hash): Our example MU-hash = 1) Take the first set of numbers, then 2) multiply this by 3141592654, then 3) remove the first 5 numbers from the result, and then 4) repeat this process 1000 times, and then after this is done, 5) only show the first 10 numbers and remove all the other numbers. To simplify this further so that this can actually be done in an example, we will replace 4) repeat this process 1000 times with 4) repeat this process one time. Ok. So to summarize PART 1, the computer wallet program creates: Random number > then creates Bitcoin private key [then uses one way hash] > to create Bitcoin public address OK. So now we can start our example: Start with Bitcoin private key = 16503429214399795533 Then hash this private key with our MU-hash = 1 & 2: 16503429214399795533 x 3141592654 = 51847051985767388665574814582 3: 51847051985767388665574814582 (remove first 5 numbers) = 051985767388665574814582 [take note that it is possible for zeros to be in the front of the number, and that it is rarer for these resulting numbers to have many consecutive zeros in front of it] 4: (repeat this process one time) = 051985767388665574814582 x 3141592654 = 163318104940784532700178223280628 (then remove first 5 numbers) = 8104940784532700178223280628 5: (only show first 10 numbers and remove all the other numbers) = 8104940784 = Bitcoin public address SO we are left with: Bitcoin private key = 16503429214399795533 (and) Bitcoin public address = 8104940784 Every single time we do this one way MU-hash on the same original bitcoin private key we will get the same bitcoin public address. And looking only at the bitcoin public address, it is impossible to calculate or guess what the original bitcoin private key was. For our simple example though with the MU-hash, a powerful computer organization might be able to guess or calculate our bitcoin private key through random guessing (because our numbers are fairly small) but for the real bitcoin private key this would be impossible to do. At its simplest level, this is how bitcoin public addresses and bitcoin private keys work. If you know the bitcoin private key, you can always prove to the network that you own the bitcoin public address which contains the bitcoins and the network will always let you move the bitcoins even though they don’t know who you are. You can see now how anyone on the planet can, in the safety of their own homes, create their own bitcoin public addresses to give to people in order to receive and send bitcoins from. This is part of what makes bitcoin a decentralized digital currency which allows anyone to take part in, and which is hard to restrict or ban. PART 2: THE BITCOIN BLOCKCHAIN So the bitcoin private key and bitcoin public address holds the actual bitcoins. And you can see that these can be created and stored without limit by anyone knowledgeable enough. However, if we only have these, the bitcoins won’t be of any use. We need a payment network which lets you send your bitcoins to different bitcoin addresses. The bitcoin blockchain serves this purpose. The bitcoin blockchain is basically the list (or ledger) of all the transactions and all the used bitcoin public addresses that has ever been made in the bitcoin network. It is maintained by a large number of highly invested people and groups who take part in the network (known as miners)**. The easiest way to understand the bitcoin blockchain is to go back to the very beginning of bitcoin in the year 2009 at Block 0 known as the genesis block and then slowly build up from there. I will only need to describe up to Block 2 for you to get a good enough idea. I want to emphasize that these things didn’t happen as described for the actual bitcoin blockchain but is rather a hypothetical scenario which fairly accurately explains how bitcoin mining and bitcoin transactions work***. BLOCK ZERO – GENESIS BLOCK BLOCK ZERO basically has no transaction data. But it still has data such as the date it was created and some other data. This blockchain data is stored on the computers of individual people who have downloaded and run the original bitcoin wallet program (called nodes and/or miners). In our example we will assume there are only 3 participants which make up all the users in the network: Participants A, B and C. In the future many new participants will join the network. The original bitcoin wallet program and all future variations of the program is free for anyone to download and use. Each of these 3 participants would have had the option to mine bitcoins. And they would have been able to create bitcoin public addresses and private keys like described earlier. When they ran the mining software for the first time at least one bitcoin public address was created by each of them. So assume: Participant A has created bitcoin public address 1EcKp4Cv6QLV5kmCMEezERLXJYTaNVaLgs Participant B has created bitcoin public address 14pP4zDquF3NE3BSjjpNbsCTz9tDs9cSN8 Participant C has created bitcoin public address 1J62KZfV2Z8653zv3ydW88YgjBZySj7CQm Now all 3 Participants activate their mining software. Since there are currently no bitcoins in all the world, BLOCK ONE, the next block of the blockchain will not contain any transactions showing any movement of bitcoins, but it will show a balance of 50 new bitcoins created into one of the 3 bitcoin public addresses shown above owned by Participant A, B or C. New bitcoins enter the world after every mining round. The way the software decides which miner gets the 50 new bitcoins is based on a ‘proof of work’ system. On average new bitcoins enter the world every 10 minutes and this rate is set by the computer software. HOW MINING WORKS So we will assume that all 3 participants turn on their mining software at the same time and everyone is using the exact same type of computer. These 3 miners all have the same copy of the bitcoin blockchain which in its entirety is currently BLOCK ZERO. The mining software now takes the BLOCK ZERO file data and adds the empty BLOCK ONE file data to it and then expresses this file as a number (we will call this the ‘block one computer number’). Remember that all data files on a computer are zeros and ones. Then the software begins the mining process by taking a random number (called a nonce) and adding this random number to the end of the ‘block one computer number’. Then it creates a one way (SHA256) hash of this new number and the result is recorded somewhere. Basically the rules of the program states that if this resulting number (or hash) has a certain number of consecutive zeros in front of it, then it proves that that computer has completed the ‘proof of work’ and the software automatically creates the 50 new bitcoins into that participant miner’s bitcoin public address. If the random number doesn’t lead to the required number of consecutive zeros then the computer tries again until it does find one. The proof of work here lies in the fact that mathematically, it takes a certain number of random hashes by the computer before the computer will find one that meets the difficulty requirement of having a hash-result with the required number of consecutive zeros in front of it. Every 2 weeks this difficulty is automatically adjusted by the bitcoin computer program which all the miners run by adding or reducing the number of consecutive zeros that are needed before new bitcoins can be awarded. The more zeros there are, the more difficult it is to solve****. The difficulty is changed so that on average about every 10 minutes a new block is solved, and this happens regardless of how many or how few computers are mining. In our example each of the 3 miners have an equal chance of finding the correct hash first because everyone is running the same computer type and so each computer will create the same number of hashes per second. In modern day bitcoin mining though, different miners have vastly different hash producing abilities and this will directly impact on how many blocks they will solve compared to other miners. The more hashes they can make compared to the rest of the miners, the more blocks they will solve. Also, in modern day mining the number of hashes required is so huge now that only mining pools or centres with millions and millions of dollars worth of dedicated mining hardware in them can successfully solve new blocks. So we will assume Participant A was the first to solve BLOCK ONE and their bitcoin wallet software now shows 50 bitcoins at address 1EcKp4Cv6QLV5kmCMEezERLXJYTaNVaLgs. Participant A will now broadcast this information to the entire network and Participants B and C will check that Participant A’s hash number is correct by simply checking that the number they used leads to the correct hash in that new block (correct hash = proof that work has been done). If it is correct then their computers will now also show BLOCK ZERO + BLOCK ONE. The bitcoin blockchain has now been updated and will look like the following: BLOCK ZERO (date and time created) + BLOCK ONE (date and time created)(50 NEW BTC at 1EcKp4C… as mining block reward) + Solved HASH of Block one MAKING TRANSACTIONS Lets say that participant A decides to spend their bitcoins right now by sending it to another bitcoin address. Participant C has given Participant A an address for him/her to send the bitcoins to (say address 18yACUJ3PaAWs41GoJU7aDZSTLEqwaBA4b). So Participant A will now create a transaction on their computer. The transaction will be to: SEND 20 BTC from 1EcKp4Cv6QLV5kmCMEezERLXJYTaNVaLgs to 18yACUJ3PaAWs41GoJU7aDZSTLEqwaBA4b and send the CHANGE 29 BTC back to 1EcKp4Cv6QLV5kmCMEezERLXJYTaNVaLgs, and give 1 BTC as the transaction fee to be sent to the miner that solves the next block. This transaction will immediately enter the memory pool (called mempool) which can be picked up by any of the other miners in the network. Now lets assume all three Participants A, B and C continue to try to solve the next block of the bitcoin blockchain called BLOCK TWO. To do this they would take the current blockchain and then add any transactions they like from the mempool to create a new blockchain that includes BLOCK ZERO and BLOCK ONE and BLOCK TWO, which is then expressed as a ‘block two computer number’. They will then attempt to solve the new block like before. None of the miners are required to add any transactions from the mempool and can continue to mine an empty block if they wanted, but they usually want to add transactions because they will receive the transaction fee that Participant A has included in the transaction. So lets now assume this time Participant B successfully solves the next block. The bitcoin blockchain will now look like the following: BLOCK ZERO (date and time created) + BLOCK ONE (date and time created)(50 NEW BTC at 1EcKp4C… as mining block reward) + Solved HASH of Block one + BLOCK TWO (date and time created)(20 BTC at 18yACU…. (1 confirmation) moved from 1EcKp4C…; 29 BTC at 1EcKp4C... (1 confirmation) moved from 1EcKp4C…; 1 BTC at miners address 14pP4zDq… as transaction fee reward moved from 1EcKp4C…; and 50 NEW BTC at miners address 14pP4zDq… as mining block reward) + Solved HASH of Block two A real world example of a ‘Solved HASH of Block #593468’ of the bitcoin blockchain is shown below (it is a hexadecimal base-16 number containing exactly 64 characters): 00000000000000000014fcb29e6e3b0ead3bd2e307d7f619a935f1d5323e9013 There is a lot more to all of this but this is the gist of what bitcoin mining and solving blocks involves. The entire system has been designed to be very secure and very stable and has been in continuous improvement since it started. A point to highlight is that only so many bitcoins can be added at a certain time and the rate of new bitcoins that can be added is halved about every four years. This is where bitcoin’s programmed scarcity comes from and is a major reason why it is so valuable. There will only ever be a certain maximum number of bitcoins on the planet and never anymore. The total number of all the bitcoins in the world is currently over 87% of its maximum possible number. A FINAL LOOK AT TRANSACTIONS When a transaction is created, the software you use will do a number of things. The most important of these is that it will sign the transaction with the bitcoin private key and then it will broadcast the transaction to the network. The way your computer proves to the network that you are the rightful owner of the bitcoins stored at a particular bitcoin public address is by using one way hashes together with your bitcoin private key. And it does this without revealing your bitcoin private key to anyone except yourself. To picture how this is possible, simply go back to our previous example of how your bitcoin private key was hashed to create the bitcoin public address. Now instead of: Random number > then creates Bitcoin private key [then uses one way hash] > to create Bitcoin public address We simply add ONE more hash step in between the bitcoin private key and bitcoin public address so that we have: Random number > then creates Bitcoin private key [then uses one way hash] > to create SIGNATURE [then uses another one way hash] > to create Bitcoin public address Now it is possible to show the network your SIGNATURE without revealing your bitcoin private key while still proving that you are the owner of the bitcoin private key. In practice, there is more to the signing process (such as public keys), and each signature will only work specifically to a particular transaction you have created, but you get the idea. As soon as you have created the transaction and the bitcoin network has checked that it is valid, your transaction will enter the mempool in order to be picked up by a miner, and then eventually added to the next block of the blockchain. Bitcoin transactions therefore can happen securely and discretely, with no need for you trust any particular third party (such as banking institutions). You only need to trust that your own creation, storage and transaction steps used to create and send the bitcoins were secure; and that the network of miners maintaining the network will continue to mine new blocks the way they have always mined them since the very beginning. Written by Bitgoldwallet.com owner Slight inaccuracies explained: * The actual random number only needs to be between 2128 (2 to the power of 128) and 2256 (2 to the power of 256) to meet unbreakable cryptography standards. This is roughly equal to a number containing between 39 and 78 numbers (decimal numbers). ** Not every miner who takes part in the bitcoin network needs to be highly invested. Many smaller miners who work as part of a larger mining pool have not necessarily spent huge amounts of money on their equipment. Many mining groups however are heavily invested and they are located all over the world. *** The real bitcoin blockchain was originally mined mainly by its creator/s (Satoshi Nakamoto) for a period of up to 12 months before any significant number of other participants joined the network. The first block was mined on the 3 Jan 2009 and the first open source bitcoin client (or program) was released to the public on the 9 Jan 2009. The first bitcoin transaction was made on the 12 Jan 2009, about 10 days after the first block was mined. The huge majority of the estimated 1.6 million or so bitcoins which was mined in 2009 have never been moved and it is believed that the private keys to these have been lost. **** The way the actual bitcoin mining difficulty is set is not by requiring the hashed number such as 00000000000000000014fcb29e6e3b0ead3bd2e307d7f619a935f1d5323e9013 to have a certain number of consecutive zeros in front of it, but for it to be smaller than a certain number that happens to have a lot of consecutive zeros in front of it. So for the above example, the hashed number might just need to be a number smaller than say 0000000000000000001500000000000000000000000000000000000000000000. Because of this, the difficulty can be set quite precisely. Colour scheme explained: Green text = real world examples of bitcoin public addresses, private keys and hashes Blue text = made up examples of bitcoin public addresses, private keys, hashes, names and blockchain data used to make explaining how bitcoin works easier to understand End of article |
| json metadata | {"tags":["blockchain","cryptocurrency","bitgold","bitgoldwallet"],"app":"steemit/0.2","format":"markdown"} |
| Transaction Info | Block #42792130/Trx c80505801b2b411fc59ede6b8b11fefddf2cf77f |
View Raw JSON Data
{
"trx_id": "c80505801b2b411fc59ede6b8b11fefddf2cf77f",
"block": 42792130,
"trx_in_block": 23,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-24T02:36:45",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "blockchain",
"author": "bitgoldwallet",
"permlink": "bitcoin-a-simple-explanation",
"title": "BITCOIN: A SIMPLE EXPLANATION",
"body": "WWW.BITGOLDWALLET.COM/downloads.html PDF AVAILABLE DOWNLOAD (FROM THE 17 APRIL 2020)\n\nOfficially published via the website on Friday 17 April 2020\n\nHow does bitcoin work? This article will try to explain bitcoin using words and examples which are easy to understand. To achieve this, the explanation may be very slightly inaccurate in some places, however this will make it easier to understand. By the end of this article, you will hopefully have a better understanding of bitcoin.\n\nPART 1.1 : BITCOIN PUBLIC ADDRESSES\n\nThe first basic part of bitcoin which needs to be understood is what bitcoin public addresses are, how they are created, and how they work together with bitcoin private keys. A bitcoin public address is basically like a bank account number which holds people’s bitcoins. An example of what it may look like is: \n\n16er32qQe1Xi5ZEbqxvWJJN4GKC9kYnp1i\n\nA real bitcoin public address like the one shown above is made up of capital and lowercase letters, as well as numbers that are arranged in a specific way.\n\nIn our simple explanation, I will instead give an example where 10 NUMBERS are used to represent a bitcoin public address. So our example bitcoin public address looks like the below:\n\n8104940784\n\nIn order to receive bitcoins, you need to have a bitcoin public address which the bitcoin computer wallet program has created. This is the ‘thing’ you give to other people for them to send you the bitcoins. So how are bitcoin public addresses created?\n\nPART 1.2: BITCOIN PRIVATE KEYS \n\nA bitcoin public address is always created using a bitcoin private key. An example of what a bitcoin private key may look like is: \n\nL4iLhJzUAvNfa6x3wyYGV9N6fCR3cMXN7EJ7RiC5ct4dZjmdhSmd\n\nA real bitcoin private key like the one shown above is made up of capital and lowercase letters, as well as numbers that are arranged in a specific way. \n\nIn our explanation, I will instead give an example where 20 NUMBERS are used to represent a bitcoin private key. So our example bitcoin private key looks like the below:\n\n16503429214399795533\n\nTo create a bitcoin private key, you would use a bitcoin computer wallet program. This bitcoin private key is like a password to your bitcoin public address that lets you send the bitcoins from the bitcoin public address you currently own to another person’s bitcoin public address.\n\nSO HOW ARE BITCOIN PRIVATE KEYS CREATED? This is where the magic starts.\n\nAll bitcoin private keys start as a very LARGE and very RANDOM number that is created by the bitcoin computer wallet program. This random number might be between 100 – 1000 numbers long or longer*. Think of a number so large that it is impossible for anyone or anything to guess this number. Imagine the entire universe was filled with computers placed side by side, all of them turned on and all of them repeatedly trying to guess this number, for all time and still failing. This is more or less the number that your computer creates.\n\nThe computer program you use will then convert this random number to a bitcoin private key. To a computer, all data is numbers represented by zeros and ones. So it can be seen that a computer program can easily convert any random number to a bitcoin private key with the correct formatting or structure.\n\nThe main thing to understand is that the bitcoin private key is infact a completely random set of characters and numbers. No one else on the planet knows the bitcoin private key except you because you created it randomly on your computer. If you created the bitcoin private key and only you know it, then this means you own the bitcoin private key.\n\n(Note: in reality, security is a massive issue with the creation of bitcoin private keys due to the risk of this data being stolen and spied on, so many people, including beginners let reputable cryptocurrency exchanges handle the storage and creation of their bitcoin private keys for them).\n\nSo how is the bitcoin private key converted to the bitcoin public address?\n\nThe bitcoin computer wallet program does this by using an exact formula known as a SHA256 hash together with other steps. The formula used is one-way, meaning that once the bitcoin public address is created, no one can use the bitcoin public address to work out what the private key was. And the formula is always the same and always gets the same result for the same original character string.\n\nIn cryptography and in bitcoin, a one way hash like the SHA256 hash shown above is very important and is used a lot.\n\nIn our explanation, instead of using the SHA256 hash; to make the idea easier to understand, I will use a simple one way formula (or hash) which I have made up so you can see how the one way aspect might work. We will call this hash the MU-hash (Made up hash):\n\nOur example MU-hash = \n\n1) Take the first set of numbers, then 2) multiply this by 3141592654, then 3) remove the first 5 numbers from the result, and then 4) repeat this process 1000 times, and then after this is done, 5) only show the first 10 numbers and remove all the other numbers.\n\nTo simplify this further so that this can actually be done in an example, we will replace 4) repeat this process 1000 times with 4) repeat this process one time.\n\nOk. So to summarize PART 1, the computer wallet program creates:\n\nRandom number > then creates Bitcoin private key [then uses one way hash] > to create Bitcoin public address\n\nOK. So now we can start our example:\n\nStart with Bitcoin private key = 16503429214399795533\n\nThen hash this private key with our MU-hash = \n\n1 & 2: 16503429214399795533 x 3141592654 = 51847051985767388665574814582\n\n3: 51847051985767388665574814582 (remove first 5 numbers) = 051985767388665574814582 [take note that it is possible for zeros to be in the front of the number, and that it is rarer for these resulting numbers to have many consecutive zeros in front of it]\n\n4: (repeat this process one time) = 051985767388665574814582 x 3141592654 = 163318104940784532700178223280628 (then remove first 5 numbers) = 8104940784532700178223280628\n\n5: (only show first 10 numbers and remove all the other numbers) = 8104940784 = Bitcoin public address\n\nSO we are left with:\n\nBitcoin private key = 16503429214399795533 (and) \nBitcoin public address = 8104940784\n\nEvery single time we do this one way MU-hash on the same original bitcoin private key we will get the same bitcoin public address. And looking only at the bitcoin public address, it is impossible to calculate or guess what the original bitcoin private key was. For our simple example though with the MU-hash, a powerful computer organization might be able to guess or calculate our bitcoin private key through random guessing (because our numbers are fairly small) but for the real bitcoin private key this would be impossible to do.\n\nAt its simplest level, this is how bitcoin public addresses and bitcoin private keys work. If you know the bitcoin private key, you can always prove to the network that you own the bitcoin public address which contains the bitcoins and the network will always let you move the bitcoins even though they don’t know who you are.\n\nYou can see now how anyone on the planet can, in the safety of their own homes, create their own bitcoin public addresses to give to people in order to receive and send bitcoins from. This is part of what makes bitcoin a decentralized digital currency which allows anyone to take part in, and which is hard to restrict or ban. \n\nPART 2: THE BITCOIN BLOCKCHAIN\n\nSo the bitcoin private key and bitcoin public address holds the actual bitcoins. And you can see that these can be created and stored without limit by anyone knowledgeable enough. However, if we only have these, the bitcoins won’t be of any use. We need a payment network which lets you send your bitcoins to different bitcoin addresses.\n\nThe bitcoin blockchain serves this purpose. The bitcoin blockchain is basically the list (or ledger) of all the transactions and all the used bitcoin public addresses that has ever been made in the bitcoin network. It is maintained by a large number of highly invested people and groups who take part in the network (known as miners)**.\n\nThe easiest way to understand the bitcoin blockchain is to go back to the very beginning of bitcoin in the year 2009 at Block 0 known as the genesis block and then slowly build up from there. I will only need to describe up to Block 2 for you to get a good enough idea. I want to emphasize that these things didn’t happen as described for the actual bitcoin blockchain but is rather a hypothetical scenario which fairly accurately explains how bitcoin mining and bitcoin transactions work***.\n\nBLOCK ZERO – GENESIS BLOCK\n\nBLOCK ZERO basically has no transaction data. But it still has data such as the date it was created and some other data. This blockchain data is stored on the computers of individual people who have downloaded and run the original bitcoin wallet program (called nodes and/or miners). In our example we will assume there are only 3 participants which make up all the users in the network: Participants A, B and C. In the future many new participants will join the network. The original bitcoin wallet program and all future variations of the program is free for anyone to download and use. \n\nEach of these 3 participants would have had the option to mine bitcoins. And they would have been able to create bitcoin public addresses and private keys like described earlier. \n\nWhen they ran the mining software for the first time at least one bitcoin public address was created by each of them. So assume:\n\nParticipant A has created bitcoin public address 1EcKp4Cv6QLV5kmCMEezERLXJYTaNVaLgs\n\nParticipant B has created bitcoin public address \n14pP4zDquF3NE3BSjjpNbsCTz9tDs9cSN8\n\nParticipant C has created bitcoin public address\n1J62KZfV2Z8653zv3ydW88YgjBZySj7CQm\n\nNow all 3 Participants activate their mining software. Since there are currently no bitcoins in all the world, BLOCK ONE, the next block of the blockchain will not contain any transactions showing any movement of bitcoins, but it will show a balance of 50 new bitcoins created into one of the 3 bitcoin public addresses shown above owned by Participant A, B or C. New bitcoins enter the world after every mining round. The way the software decides which miner gets the 50 new bitcoins is based on a ‘proof of work’ system. On average new bitcoins enter the world every 10 minutes and this rate is set by the computer software.\n\nHOW MINING WORKS\n\nSo we will assume that all 3 participants turn on their mining software at the same time and everyone is using the exact same type of computer. These 3 miners all have the same copy of the bitcoin blockchain which in its entirety is currently BLOCK ZERO. The mining software now takes the BLOCK ZERO file data and adds the empty BLOCK ONE file data to it and then expresses this file as a number (we will call this the ‘block one computer number’). Remember that all data files on a computer are zeros and ones. Then the software begins the mining process by taking a random number (called a nonce) and adding this random number to the end of the ‘block one computer number’. Then it creates a one way (SHA256) hash of this new number and the result is recorded somewhere. Basically the rules of the program states that if this resulting number (or hash) has a certain number of consecutive zeros in front of it, then it proves that that computer has completed the ‘proof of work’ and the software automatically creates the 50 new bitcoins into that participant miner’s bitcoin public address. If the random number doesn’t lead to the required number of consecutive zeros then the computer tries again until it does find one. The proof of work here lies in the fact that mathematically, it takes a certain number of random hashes by the computer before the computer will find one that meets the difficulty requirement of having a hash-result with the required number of consecutive zeros in front of it.\n\nEvery 2 weeks this difficulty is automatically adjusted by the bitcoin computer program which all the miners run by adding or reducing the number of consecutive zeros that are needed before new bitcoins can be awarded. The more zeros there are, the more difficult it is to solve****. The difficulty is changed so that on average about every 10 minutes a new block is solved, and this happens regardless of how many or how few computers are mining.\n\nIn our example each of the 3 miners have an equal chance of finding the correct hash first because everyone is running the same computer type and so each computer will create the same number of hashes per second. In modern day bitcoin mining though, different miners have vastly different hash producing abilities and this will directly impact on how many blocks they will solve compared to other miners. The more hashes they can make compared to the rest of the miners, the more blocks they will solve. Also, in modern day mining the number of hashes required is so huge now that only mining pools or centres with millions and millions of dollars worth of dedicated mining hardware in them can successfully solve new blocks. \n\nSo we will assume Participant A was the first to solve BLOCK ONE and their bitcoin wallet software now shows 50 bitcoins at address 1EcKp4Cv6QLV5kmCMEezERLXJYTaNVaLgs. Participant A will now broadcast this information to the entire network and Participants B and C will check that Participant A’s hash number is correct by simply checking that the number they used leads to the correct hash in that new block (correct hash = proof that work has been done). If it is correct then their computers will now also show BLOCK ZERO + BLOCK ONE.\n\nThe bitcoin blockchain has now been updated and will look like the following:\n\nBLOCK ZERO (date and time created) +\n\nBLOCK ONE (date and time created)(50 NEW BTC at 1EcKp4C… as mining block reward) +\nSolved HASH of Block one\n\nMAKING TRANSACTIONS\n\nLets say that participant A decides to spend their bitcoins right now by sending it to another bitcoin address. Participant C has given Participant A an address for him/her to send the bitcoins to (say address 18yACUJ3PaAWs41GoJU7aDZSTLEqwaBA4b).\n\nSo Participant A will now create a transaction on their computer. The transaction will be to:\n\nSEND 20 BTC from 1EcKp4Cv6QLV5kmCMEezERLXJYTaNVaLgs to 18yACUJ3PaAWs41GoJU7aDZSTLEqwaBA4b and send the CHANGE 29 BTC back to 1EcKp4Cv6QLV5kmCMEezERLXJYTaNVaLgs, and give 1 BTC as the transaction fee to be sent to the miner that solves the next block.\n\nThis transaction will immediately enter the memory pool (called mempool) which can be picked up by any of the other miners in the network.\n\nNow lets assume all three Participants A, B and C continue to try to solve the next block of the bitcoin blockchain called BLOCK TWO.\n\nTo do this they would take the current blockchain and then add any transactions they like from the mempool to create a new blockchain that includes BLOCK ZERO and BLOCK ONE and BLOCK TWO, which is then expressed as a ‘block two computer number’. They will then attempt to solve the new block like before. None of the miners are required to add any transactions from the mempool and can continue to mine an empty block if they wanted, but they usually want to add transactions because they will receive the transaction fee that Participant A has included in the transaction.\n\nSo lets now assume this time Participant B successfully solves the next block. \n\nThe bitcoin blockchain will now look like the following:\n\nBLOCK ZERO (date and time created) +\n\nBLOCK ONE (date and time created)(50 NEW BTC at 1EcKp4C… as mining block reward) +\nSolved HASH of Block one +\n\nBLOCK TWO (date and time created)(20 BTC at 18yACU…. (1 confirmation) moved from 1EcKp4C…; 29 BTC at 1EcKp4C... (1 confirmation) moved from 1EcKp4C…; 1 BTC at miners address 14pP4zDq… as transaction fee reward moved from 1EcKp4C…; and 50 NEW BTC at miners address 14pP4zDq… as mining block reward) +\nSolved HASH of Block two\n\nA real world example of a ‘Solved HASH of Block #593468’ of the bitcoin blockchain is shown below (it is a hexadecimal base-16 number containing exactly 64 characters): \n\n00000000000000000014fcb29e6e3b0ead3bd2e307d7f619a935f1d5323e9013\n\nThere is a lot more to all of this but this is the gist of what bitcoin mining and solving blocks involves. The entire system has been designed to be very secure and very stable and has been in continuous improvement since it started. A point to highlight is that only so many bitcoins can be added at a certain time and the rate of new bitcoins that can be added is halved about every four years. This is where bitcoin’s programmed scarcity comes from and is a major reason why it is so valuable. There will only ever be a certain maximum number of bitcoins on the planet and never anymore. The total number of all the bitcoins in the world is currently over 87% of its maximum possible number.\n\nA FINAL LOOK AT TRANSACTIONS\n\nWhen a transaction is created, the software you use will do a number of things. The most important of these is that it will sign the transaction with the bitcoin private key and then it will broadcast the transaction to the network. \n\nThe way your computer proves to the network that you are the rightful owner of the bitcoins stored at a particular bitcoin public address is by using one way hashes together with your bitcoin private key. And it does this without revealing your bitcoin private key to anyone except yourself.\n\nTo picture how this is possible, simply go back to our previous example of how your bitcoin private key was hashed to create the bitcoin public address. Now instead of:\n\nRandom number > then creates Bitcoin private key [then uses one way hash] > to create Bitcoin public address\n\nWe simply add ONE more hash step in between the bitcoin private key and bitcoin public address so that we have:\n\nRandom number > then creates Bitcoin private key [then uses one way hash] > to create SIGNATURE [then uses another one way hash] > to create Bitcoin public address\n\nNow it is possible to show the network your SIGNATURE without revealing your bitcoin private key while still proving that you are the owner of the bitcoin private key. In practice, there is more to the signing process (such as public keys), and each signature will only work specifically to a particular transaction you have created, but you get the idea. \n\nAs soon as you have created the transaction and the bitcoin network has checked that it is valid, your transaction will enter the mempool in order to be picked up by a miner, and then eventually added to the next block of the blockchain.\n\nBitcoin transactions therefore can happen securely and discretely, with no need for you trust any particular third party (such as banking institutions). You only need to trust that your own creation, storage and transaction steps used to create and send the bitcoins were secure; and that the network of miners maintaining the network will continue to mine new blocks the way they have always mined them since the very beginning.\n\n\nWritten by Bitgoldwallet.com owner\n\nSlight inaccuracies explained:\n\n* The actual random number only needs to be between 2128 (2 to the power of 128) and 2256 (2 to the power of 256) to meet unbreakable cryptography standards. This is roughly equal to a number containing between 39 and 78 numbers (decimal numbers).\n\n** Not every miner who takes part in the bitcoin network needs to be highly invested. Many smaller miners who work as part of a larger mining pool have not necessarily spent huge amounts of money on their equipment. Many mining groups however are heavily invested and they are located all over the world.\n\n*** The real bitcoin blockchain was originally mined mainly by its creator/s (Satoshi Nakamoto) for a period of up to 12 months before any significant number of other participants joined the network. The first block was mined on the 3 Jan 2009 and the first open source bitcoin client (or program) was released to the public on the 9 Jan 2009. The first bitcoin transaction was made on the 12 Jan 2009, about 10 days after the first block was mined. The huge majority of the estimated 1.6 million or so bitcoins which was mined in 2009 have never been moved and it is believed that the private keys to these have been lost.\n\n**** The way the actual bitcoin mining difficulty is set is not by requiring the hashed number such as 00000000000000000014fcb29e6e3b0ead3bd2e307d7f619a935f1d5323e9013 to have a certain number of consecutive zeros in front of it, but for it to be smaller than a certain number that happens to have a lot of consecutive zeros in front of it. So for the above example, the hashed number might just need to be a number smaller than say 0000000000000000001500000000000000000000000000000000000000000000. Because of this, the difficulty can be set quite precisely. \n\nColour scheme explained:\n\nGreen text = real world examples of bitcoin public addresses, private keys and hashes\n\nBlue text = made up examples of bitcoin public addresses, private keys, hashes, names and blockchain data used to make explaining how bitcoin works easier to understand\n\nEnd of article",
"json_metadata": "{\"tags\":[\"blockchain\",\"cryptocurrency\",\"bitgold\",\"bitgoldwallet\"],\"app\":\"steemit/0.2\",\"format\":\"markdown\"}"
}
]
}bitgoldwalletclaimed reward balance: 1.351 SBD, 2.195 SP2020/04/24 02:27:27
bitgoldwalletclaimed reward balance: 1.351 SBD, 2.195 SP
2020/04/24 02:27:27
| account | bitgoldwallet |
| reward steem | 0.000 STEEM |
| reward sbd | 1.351 SBD |
| reward vests | 3573.683701 VESTS |
| Transaction Info | Block #42791950/Trx ec193c1ec830948371a2d403711cd40643e1eee7 |
View Raw JSON Data
{
"trx_id": "ec193c1ec830948371a2d403711cd40643e1eee7",
"block": 42791950,
"trx_in_block": 13,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-24T02:27:27",
"op": [
"claim_reward_balance",
{
"account": "bitgoldwallet",
"reward_steem": "0.000 STEEM",
"reward_sbd": "1.351 SBD",
"reward_vests": "3573.683701 VESTS"
}
]
}2019/08/05 05:42:54
2019/08/05 05:42:54
| parent author | bitgoldwallet |
| parent permlink | the-unbreakability-of-bitcoin |
| author | steemitboard |
| permlink | steemitboard-notify-bitgoldwallet-20190805t054253000z |
| title | |
| body | Congratulations @bitgoldwallet! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@bitgoldwallet/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/@bitgoldwallet) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=bitgoldwallet)_</sub> ###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes! |
| json metadata | {"image":["https://steemitboard.com/img/notify.png"]} |
| Transaction Info | Block #35279027/Trx 9bf8817cd1120756ab63c9d78bbe1a75203f742f |
View Raw JSON Data
{
"trx_id": "9bf8817cd1120756ab63c9d78bbe1a75203f742f",
"block": 35279027,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-08-05T05:42:54",
"op": [
"comment",
{
"parent_author": "bitgoldwallet",
"parent_permlink": "the-unbreakability-of-bitcoin",
"author": "steemitboard",
"permlink": "steemitboard-notify-bitgoldwallet-20190805t054253000z",
"title": "",
"body": "Congratulations @bitgoldwallet! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@bitgoldwallet/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/@bitgoldwallet) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=bitgoldwallet)_</sub>\n\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
"json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}"
}
]
}bitgoldwalletreceived 0.000 STEEM from power down installment (0.000 SP)2019/02/01 08:42:03
bitgoldwalletreceived 0.000 STEEM from power down installment (0.000 SP)
2019/02/01 08:42:03
| from account | bitgoldwallet |
| to account | bitgoldwallet |
| withdrawn | 0.000011 VESTS |
| deposited | 0.000 STEEM |
| Transaction Info | Block #29961542/Virtual Operation #7 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 29961542,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 7,
"timestamp": "2019-02-01T08:42:03",
"op": [
"fill_vesting_withdraw",
{
"from_account": "bitgoldwallet",
"to_account": "bitgoldwallet",
"withdrawn": "0.000011 VESTS",
"deposited": "0.000 STEEM"
}
]
}bitgoldwalletreceived 3.865 STEEM from power down installment (4.765 SP)2019/01/25 08:42:03
bitgoldwalletreceived 3.865 STEEM from power down installment (4.765 SP)
2019/01/25 08:42:03
| from account | bitgoldwallet |
| to account | bitgoldwallet |
| withdrawn | 7759.269546 VESTS |
| deposited | 3.865 STEEM |
| Transaction Info | Block #29760110/Virtual Operation #3 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 29760110,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 3,
"timestamp": "2019-01-25T08:42:03",
"op": [
"fill_vesting_withdraw",
{
"from_account": "bitgoldwallet",
"to_account": "bitgoldwallet",
"withdrawn": "7759.269546 VESTS",
"deposited": "3.865 STEEM"
}
]
}bitgoldwalletreceived 3.864 STEEM from power down installment (4.765 SP)2019/01/18 08:42:03
bitgoldwalletreceived 3.864 STEEM from power down installment (4.765 SP)
2019/01/18 08:42:03
| from account | bitgoldwallet |
| to account | bitgoldwallet |
| withdrawn | 7759.269546 VESTS |
| deposited | 3.864 STEEM |
| Transaction Info | Block #29558744/Virtual Operation #20 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 29558744,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 20,
"timestamp": "2019-01-18T08:42:03",
"op": [
"fill_vesting_withdraw",
{
"from_account": "bitgoldwallet",
"to_account": "bitgoldwallet",
"withdrawn": "7759.269546 VESTS",
"deposited": "3.864 STEEM"
}
]
}bitgoldwalletreceived 3.862 STEEM from power down installment (4.765 SP)2019/01/11 08:42:03
bitgoldwalletreceived 3.862 STEEM from power down installment (4.765 SP)
2019/01/11 08:42:03
| from account | bitgoldwallet |
| to account | bitgoldwallet |
| withdrawn | 7759.269546 VESTS |
| deposited | 3.862 STEEM |
| Transaction Info | Block #29357335/Virtual Operation #3 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 29357335,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 3,
"timestamp": "2019-01-11T08:42:03",
"op": [
"fill_vesting_withdraw",
{
"from_account": "bitgoldwallet",
"to_account": "bitgoldwallet",
"withdrawn": "7759.269546 VESTS",
"deposited": "3.862 STEEM"
}
]
}bitgoldwalletreceived 3.860 STEEM from power down installment (4.765 SP)2019/01/04 08:42:03
bitgoldwalletreceived 3.860 STEEM from power down installment (4.765 SP)
2019/01/04 08:42:03
| from account | bitgoldwallet |
| to account | bitgoldwallet |
| withdrawn | 7759.269546 VESTS |
| deposited | 3.860 STEEM |
| Transaction Info | Block #29155889/Virtual Operation #2 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 29155889,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 2,
"timestamp": "2019-01-04T08:42:03",
"op": [
"fill_vesting_withdraw",
{
"from_account": "bitgoldwallet",
"to_account": "bitgoldwallet",
"withdrawn": "7759.269546 VESTS",
"deposited": "3.860 STEEM"
}
]
}bitgoldwalletreceived 3.859 STEEM from power down installment (4.765 SP)2018/12/28 08:42:03
bitgoldwalletreceived 3.859 STEEM from power down installment (4.765 SP)
2018/12/28 08:42:03
| from account | bitgoldwallet |
| to account | bitgoldwallet |
| withdrawn | 7759.269546 VESTS |
| deposited | 3.859 STEEM |
| Transaction Info | Block #28954486/Virtual Operation #4 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 28954486,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 4,
"timestamp": "2018-12-28T08:42:03",
"op": [
"fill_vesting_withdraw",
{
"from_account": "bitgoldwallet",
"to_account": "bitgoldwallet",
"withdrawn": "7759.269546 VESTS",
"deposited": "3.859 STEEM"
}
]
}bitgoldwalletreceived 3.857 STEEM from power down installment (4.765 SP)2018/12/21 08:42:03
bitgoldwalletreceived 3.857 STEEM from power down installment (4.765 SP)
2018/12/21 08:42:03
| from account | bitgoldwallet |
| to account | bitgoldwallet |
| withdrawn | 7759.269546 VESTS |
| deposited | 3.857 STEEM |
| Transaction Info | Block #28752975/Virtual Operation #14 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 28752975,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 14,
"timestamp": "2018-12-21T08:42:03",
"op": [
"fill_vesting_withdraw",
{
"from_account": "bitgoldwallet",
"to_account": "bitgoldwallet",
"withdrawn": "7759.269546 VESTS",
"deposited": "3.857 STEEM"
}
]
}bitgoldwalletreceived 3.856 STEEM from power down installment (4.765 SP)2018/12/14 08:42:03
bitgoldwalletreceived 3.856 STEEM from power down installment (4.765 SP)
2018/12/14 08:42:03
| from account | bitgoldwallet |
| to account | bitgoldwallet |
| withdrawn | 7759.269546 VESTS |
| deposited | 3.856 STEEM |
| Transaction Info | Block #28551513/Virtual Operation #2 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 28551513,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 2,
"timestamp": "2018-12-14T08:42:03",
"op": [
"fill_vesting_withdraw",
{
"from_account": "bitgoldwallet",
"to_account": "bitgoldwallet",
"withdrawn": "7759.269546 VESTS",
"deposited": "3.856 STEEM"
}
]
}bitgoldwalletreceived 3.854 STEEM from power down installment (4.765 SP)2018/12/07 08:42:03
bitgoldwalletreceived 3.854 STEEM from power down installment (4.765 SP)
2018/12/07 08:42:03
| from account | bitgoldwallet |
| to account | bitgoldwallet |
| withdrawn | 7759.269546 VESTS |
| deposited | 3.854 STEEM |
| Transaction Info | Block #28350062/Virtual Operation #3 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 28350062,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 3,
"timestamp": "2018-12-07T08:42:03",
"op": [
"fill_vesting_withdraw",
{
"from_account": "bitgoldwallet",
"to_account": "bitgoldwallet",
"withdrawn": "7759.269546 VESTS",
"deposited": "3.854 STEEM"
}
]
}bitgoldwalletreceived 3.853 STEEM from power down installment (4.765 SP)2018/11/30 08:42:03
bitgoldwalletreceived 3.853 STEEM from power down installment (4.765 SP)
2018/11/30 08:42:03
| from account | bitgoldwallet |
| to account | bitgoldwallet |
| withdrawn | 7759.269546 VESTS |
| deposited | 3.853 STEEM |
| Transaction Info | Block #28148543/Virtual Operation #4 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 28148543,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 4,
"timestamp": "2018-11-30T08:42:03",
"op": [
"fill_vesting_withdraw",
{
"from_account": "bitgoldwallet",
"to_account": "bitgoldwallet",
"withdrawn": "7759.269546 VESTS",
"deposited": "3.853 STEEM"
}
]
}bitgoldwalletreceived 3.851 STEEM from power down installment (4.765 SP)2018/11/23 08:42:03
bitgoldwalletreceived 3.851 STEEM from power down installment (4.765 SP)
2018/11/23 08:42:03
| from account | bitgoldwallet |
| to account | bitgoldwallet |
| withdrawn | 7759.269546 VESTS |
| deposited | 3.851 STEEM |
| Transaction Info | Block #27947049/Virtual Operation #4 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 27947049,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 4,
"timestamp": "2018-11-23T08:42:03",
"op": [
"fill_vesting_withdraw",
{
"from_account": "bitgoldwallet",
"to_account": "bitgoldwallet",
"withdrawn": "7759.269546 VESTS",
"deposited": "3.851 STEEM"
}
]
}kumagai1976upvoted (100.00%) @bitgoldwallet / the-unbreakability-of-bitcoin2018/11/19 19:46:00
kumagai1976upvoted (100.00%) @bitgoldwallet / the-unbreakability-of-bitcoin
2018/11/19 19:46:00
| voter | kumagai1976 |
| author | bitgoldwallet |
| permlink | the-unbreakability-of-bitcoin |
| weight | 10000 (100.00%) |
| Transaction Info | Block #27845163/Trx f5cde0e751f6c699f567890cb881171e1531a1f0 |
View Raw JSON Data
{
"trx_id": "f5cde0e751f6c699f567890cb881171e1531a1f0",
"block": 27845163,
"trx_in_block": 28,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-11-19T19:46:00",
"op": [
"vote",
{
"voter": "kumagai1976",
"author": "bitgoldwallet",
"permlink": "the-unbreakability-of-bitcoin",
"weight": 10000
}
]
}bitgoldwalletreceived 3.850 STEEM from power down installment (4.765 SP)2018/11/16 08:42:03
bitgoldwalletreceived 3.850 STEEM from power down installment (4.765 SP)
2018/11/16 08:42:03
| from account | bitgoldwallet |
| to account | bitgoldwallet |
| withdrawn | 7759.269546 VESTS |
| deposited | 3.850 STEEM |
| Transaction Info | Block #27745523/Virtual Operation #39 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 27745523,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 39,
"timestamp": "2018-11-16T08:42:03",
"op": [
"fill_vesting_withdraw",
{
"from_account": "bitgoldwallet",
"to_account": "bitgoldwallet",
"withdrawn": "7759.269546 VESTS",
"deposited": "3.850 STEEM"
}
]
}all.carssent 0.001 STEEM to @bitgoldwallet- "🔝UpVote + Resteem Service🔝Get 400-1000 Upvotes and Resteem to my 17.000+ followers.Send 1 SBD or more to @all.cars ( Link as memo ). 🔥😈🔥Max post age 2.5 days!"2018/11/12 18:05:33
all.carssent 0.001 STEEM to @bitgoldwallet- "🔝UpVote + Resteem Service🔝Get 400-1000 Upvotes and Resteem to my 17.000+ followers.Send 1 SBD or more to @all.cars ( Link as memo ). 🔥😈🔥Max post age 2.5 days!"
2018/11/12 18:05:33
| from | all.cars |
| to | bitgoldwallet |
| amount | 0.001 STEEM |
| memo | 🔝UpVote + Resteem Service🔝Get 400-1000 Upvotes and Resteem to my 17.000+ followers.Send 1 SBD or more to @all.cars ( Link as memo ). 🔥😈🔥Max post age 2.5 days! |
| Transaction Info | Block #27641690/Trx 9c2d5b4f029ee10994462aa4dbd8e75044c958e2 |
View Raw JSON Data
{
"trx_id": "9c2d5b4f029ee10994462aa4dbd8e75044c958e2",
"block": 27641690,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-11-12T18:05:33",
"op": [
"transfer",
{
"from": "all.cars",
"to": "bitgoldwallet",
"amount": "0.001 STEEM",
"memo": "🔝UpVote + Resteem Service🔝Get 400-1000 Upvotes and Resteem to my 17.000+ followers.Send 1 SBD or more to @all.cars ( Link as memo ). 🔥😈🔥Max post age 2.5 days!"
}
]
}bitgoldwalletreceived 1.351 SBD, 2.195 SP author reward for @bitgoldwallet / the-unbreakability-of-bitcoin2018/11/12 04:48:36
bitgoldwalletreceived 1.351 SBD, 2.195 SP author reward for @bitgoldwallet / the-unbreakability-of-bitcoin
2018/11/12 04:48:36
| author | bitgoldwallet |
| permlink | the-unbreakability-of-bitcoin |
| sbd payout | 1.351 SBD |
| steem payout | 0.000 STEEM |
| vesting payout | 3573.683701 VESTS |
| Transaction Info | Block #27625757/Virtual Operation #12 |
View Raw JSON Data
{
"trx_id": "0000000000000000000000000000000000000000",
"block": 27625757,
"trx_in_block": 4294967295,
"op_in_trx": 0,
"virtual_op": 12,
"timestamp": "2018-11-12T04:48:36",
"op": [
"author_reward",
{
"author": "bitgoldwallet",
"permlink": "the-unbreakability-of-bitcoin",
"sbd_payout": "1.351 SBD",
"steem_payout": "0.000 STEEM",
"vesting_payout": "3573.683701 VESTS"
}
]
}vaultecupvoted (100.00%) @bitgoldwallet / the-unbreakability-of-bitcoin2018/11/11 20:05:00
vaultecupvoted (100.00%) @bitgoldwallet / the-unbreakability-of-bitcoin
2018/11/11 20:05:00
| voter | vaultec |
| author | bitgoldwallet |
| permlink | the-unbreakability-of-bitcoin |
| weight | 10000 (100.00%) |
| Transaction Info | Block #27615302/Trx b4ad602a2ebddf2b39b8501ca0bd6b77b5aa2984 |
View Raw JSON Data
{
"trx_id": "b4ad602a2ebddf2b39b8501ca0bd6b77b5aa2984",
"block": 27615302,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-11-11T20:05:00",
"op": [
"vote",
{
"voter": "vaultec",
"author": "bitgoldwallet",
"permlink": "the-unbreakability-of-bitcoin",
"weight": 10000
}
]
}k3rupvoted (100.00%) @bitgoldwallet / the-unbreakability-of-bitcoin2018/11/11 16:27:36
k3rupvoted (100.00%) @bitgoldwallet / the-unbreakability-of-bitcoin
2018/11/11 16:27:36
| voter | k3r |
| author | bitgoldwallet |
| permlink | the-unbreakability-of-bitcoin |
| weight | 10000 (100.00%) |
| Transaction Info | Block #27610955/Trx fa8eb80b695ac45866b1f7794a5fc0c011b09927 |
View Raw JSON Data
{
"trx_id": "fa8eb80b695ac45866b1f7794a5fc0c011b09927",
"block": 27610955,
"trx_in_block": 9,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-11-11T16:27:36",
"op": [
"vote",
{
"voter": "k3r",
"author": "bitgoldwallet",
"permlink": "the-unbreakability-of-bitcoin",
"weight": 10000
}
]
}2018/11/11 14:28:57
2018/11/11 14:28:57
| parent author | bitgoldwallet |
| parent permlink | the-unbreakability-of-bitcoin |
| author | mathieugagnon |
| permlink | re-bitgoldwallet-the-unbreakability-of-bitcoin-20181111t142857724z |
| title | |
| body | Thanks for this article |
| json metadata | {"tags":["bitcoin"],"app":"steemit/0.1"} |
| Transaction Info | Block #27608585/Trx 2c9fa5163a2cf00e359c47284896af86cafa09eb |
View Raw JSON Data
{
"trx_id": "2c9fa5163a2cf00e359c47284896af86cafa09eb",
"block": 27608585,
"trx_in_block": 22,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-11-11T14:28:57",
"op": [
"comment",
{
"parent_author": "bitgoldwallet",
"parent_permlink": "the-unbreakability-of-bitcoin",
"author": "mathieugagnon",
"permlink": "re-bitgoldwallet-the-unbreakability-of-bitcoin-20181111t142857724z",
"title": "",
"body": "Thanks for this article",
"json_metadata": "{\"tags\":[\"bitcoin\"],\"app\":\"steemit/0.1\"}"
}
]
}mathieugagnonupvoted (100.00%) @bitgoldwallet / the-unbreakability-of-bitcoin2018/11/11 14:28:42
mathieugagnonupvoted (100.00%) @bitgoldwallet / the-unbreakability-of-bitcoin
2018/11/11 14:28:42
| voter | mathieugagnon |
| author | bitgoldwallet |
| permlink | the-unbreakability-of-bitcoin |
| weight | 10000 (100.00%) |
| Transaction Info | Block #27608580/Trx b029ff8c38e1910eab4c2107adf878d8280296c1 |
View Raw JSON Data
{
"trx_id": "b029ff8c38e1910eab4c2107adf878d8280296c1",
"block": 27608580,
"trx_in_block": 8,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-11-11T14:28:42",
"op": [
"vote",
{
"voter": "mathieugagnon",
"author": "bitgoldwallet",
"permlink": "the-unbreakability-of-bitcoin",
"weight": 10000
}
]
}ulullupvoted (100.00%) @bitgoldwallet / the-unbreakability-of-bitcoin2018/11/11 11:37:09
ulullupvoted (100.00%) @bitgoldwallet / the-unbreakability-of-bitcoin
2018/11/11 11:37:09
| voter | ulull |
| author | bitgoldwallet |
| permlink | the-unbreakability-of-bitcoin |
| weight | 10000 (100.00%) |
| Transaction Info | Block #27605152/Trx fe86abf2fdf08f741a13d4911193277b67f03c15 |
View Raw JSON Data
{
"trx_id": "fe86abf2fdf08f741a13d4911193277b67f03c15",
"block": 27605152,
"trx_in_block": 12,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-11-11T11:37:09",
"op": [
"vote",
{
"voter": "ulull",
"author": "bitgoldwallet",
"permlink": "the-unbreakability-of-bitcoin",
"weight": 10000
}
]
}tonysteemupvoted (100.00%) @bitgoldwallet / the-unbreakability-of-bitcoin2018/11/11 11:35:42
tonysteemupvoted (100.00%) @bitgoldwallet / the-unbreakability-of-bitcoin
2018/11/11 11:35:42
| voter | tonysteem |
| author | bitgoldwallet |
| permlink | the-unbreakability-of-bitcoin |
| weight | 10000 (100.00%) |
| Transaction Info | Block #27605123/Trx 6809676b68cd90f3593019a88fafec4cc52b34b5 |
View Raw JSON Data
{
"trx_id": "6809676b68cd90f3593019a88fafec4cc52b34b5",
"block": 27605123,
"trx_in_block": 15,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-11-11T11:35:42",
"op": [
"vote",
{
"voter": "tonysteem",
"author": "bitgoldwallet",
"permlink": "the-unbreakability-of-bitcoin",
"weight": 10000
}
]
}kokbisaupvoted (100.00%) @bitgoldwallet / the-unbreakability-of-bitcoin2018/11/11 11:13:57
kokbisaupvoted (100.00%) @bitgoldwallet / the-unbreakability-of-bitcoin
2018/11/11 11:13:57
| voter | kokbisa |
| author | bitgoldwallet |
| permlink | the-unbreakability-of-bitcoin |
| weight | 10000 (100.00%) |
| Transaction Info | Block #27604688/Trx 4e33dcd95e7e82de118f49ee59e70939f2ea106b |
View Raw JSON Data
{
"trx_id": "4e33dcd95e7e82de118f49ee59e70939f2ea106b",
"block": 27604688,
"trx_in_block": 22,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-11-11T11:13:57",
"op": [
"vote",
{
"voter": "kokbisa",
"author": "bitgoldwallet",
"permlink": "the-unbreakability-of-bitcoin",
"weight": 10000
}
]
}klikdokterupvoted (100.00%) @bitgoldwallet / the-unbreakability-of-bitcoin2018/11/11 11:13:12
klikdokterupvoted (100.00%) @bitgoldwallet / the-unbreakability-of-bitcoin
2018/11/11 11:13:12
| voter | klikdokter |
| author | bitgoldwallet |
| permlink | the-unbreakability-of-bitcoin |
| weight | 10000 (100.00%) |
| Transaction Info | Block #27604673/Trx fe971fb055e54d6bdc13730d8e406fe928b0cb97 |
View Raw JSON Data
{
"trx_id": "fe971fb055e54d6bdc13730d8e406fe928b0cb97",
"block": 27604673,
"trx_in_block": 17,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-11-11T11:13:12",
"op": [
"vote",
{
"voter": "klikdokter",
"author": "bitgoldwallet",
"permlink": "the-unbreakability-of-bitcoin",
"weight": 10000
}
]
}fitrianainggolanupvoted (100.00%) @bitgoldwallet / the-unbreakability-of-bitcoin2018/11/11 11:11:18
fitrianainggolanupvoted (100.00%) @bitgoldwallet / the-unbreakability-of-bitcoin
2018/11/11 11:11:18
| voter | fitrianainggolan |
| author | bitgoldwallet |
| permlink | the-unbreakability-of-bitcoin |
| weight | 10000 (100.00%) |
| Transaction Info | Block #27604635/Trx 84488fa1ebc2d3e4655b1985e5d1bcf6a484c461 |
View Raw JSON Data
{
"trx_id": "84488fa1ebc2d3e4655b1985e5d1bcf6a484c461",
"block": 27604635,
"trx_in_block": 31,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-11-11T11:11:18",
"op": [
"vote",
{
"voter": "fitrianainggolan",
"author": "bitgoldwallet",
"permlink": "the-unbreakability-of-bitcoin",
"weight": 10000
}
]
}jesus15upvoted (100.00%) @bitgoldwallet / the-unbreakability-of-bitcoin2018/11/11 04:03:30
jesus15upvoted (100.00%) @bitgoldwallet / the-unbreakability-of-bitcoin
2018/11/11 04:03:30
| voter | jesus15 |
| author | bitgoldwallet |
| permlink | the-unbreakability-of-bitcoin |
| weight | 10000 (100.00%) |
| Transaction Info | Block #27596085/Trx 792c0531a7ac22b9f1a326e1f9d7fdc4f6b759b6 |
View Raw JSON Data
{
"trx_id": "792c0531a7ac22b9f1a326e1f9d7fdc4f6b759b6",
"block": 27596085,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-11-11T04:03:30",
"op": [
"vote",
{
"voter": "jesus15",
"author": "bitgoldwallet",
"permlink": "the-unbreakability-of-bitcoin",
"weight": 10000
}
]
}depraved.floozyupvoted (100.00%) @bitgoldwallet / the-unbreakability-of-bitcoin2018/11/11 03:24:45
depraved.floozyupvoted (100.00%) @bitgoldwallet / the-unbreakability-of-bitcoin
2018/11/11 03:24:45
| voter | depraved.floozy |
| author | bitgoldwallet |
| permlink | the-unbreakability-of-bitcoin |
| weight | 10000 (100.00%) |
| Transaction Info | Block #27595311/Trx 50335220cca51ef0d2abfbcc5f2158e1a53886d7 |
View Raw JSON Data
{
"trx_id": "50335220cca51ef0d2abfbcc5f2158e1a53886d7",
"block": 27595311,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-11-11T03:24:45",
"op": [
"vote",
{
"voter": "depraved.floozy",
"author": "bitgoldwallet",
"permlink": "the-unbreakability-of-bitcoin",
"weight": 10000
}
]
}Manabar
Voting Power100.00%
Downvote Power100.00%
Resource Credits100.00%
Reputation Progress86.98%
{
"voting_manabar": {
"current_mana": "107015649624",
"last_update_time": 1587697929
},
"downvote_manabar": {
"current_mana": "27299910618",
"last_update_time": 1587697929
},
"rc_account": {
"account": "bitgoldwallet",
"rc_manabar": {
"current_mana": "111220391447",
"last_update_time": 1588300605
},
"max_rc_creation_adjustment": {
"amount": "2020748973",
"precision": 6,
"nai": "@@000000037"
},
"max_rc": "111220391447"
}
}Account Metadata
| POSTING JSON METADATA | |
| profile | {"name":"Bitgoldwallet","profile_image":"https://s17.postimg.org/6bvt29mxr/ultra_high_res_-_small_square.jpg"} |
| JSON METADATA | |
| profile | {"name":"Bitgoldwallet","profile_image":"https://s17.postimg.org/6bvt29mxr/ultra_high_res_-_small_square.jpg"} |
{
"posting_json_metadata": {
"profile": {
"name": "Bitgoldwallet",
"profile_image": "https://s17.postimg.org/6bvt29mxr/ultra_high_res_-_small_square.jpg"
}
},
"json_metadata": {
"profile": {
"name": "Bitgoldwallet",
"profile_image": "https://s17.postimg.org/6bvt29mxr/ultra_high_res_-_small_square.jpg"
}
}
}Auth Keys
Owner
Single Signature
Public Keys
STM7d1xDZ2yEPG7WLLCmJjjiMKfcVHqtK8s8chyyagy3KQyjn4qn71/1
Active
Single Signature
Public Keys
STM6qxaAUAsCXLPv2F8ad7tdqBX2LFMTetQEqMbWguC16uvSvpN8R1/1
Posting
Single Signature
Public Keys
STM7k5BtZYdg63bTLwhvN3GZT6w7sLz69rTPqthGgAmw2pNJsPH1u1/1
Memo
STM5t2U1TnHxxyhyTUHZpCKpZdt2S1coRHyPorhdMTBsHTMSadCg8
{
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7d1xDZ2yEPG7WLLCmJjjiMKfcVHqtK8s8chyyagy3KQyjn4qn7",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM6qxaAUAsCXLPv2F8ad7tdqBX2LFMTetQEqMbWguC16uvSvpN8R",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7k5BtZYdg63bTLwhvN3GZT6w7sLz69rTPqthGgAmw2pNJsPH1u",
1
]
]
},
"memo": "STM5t2U1TnHxxyhyTUHZpCKpZdt2S1coRHyPorhdMTBsHTMSadCg8"
}Witness Votes
0 / 30
No active witness votes.
[]