VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS0.00%
Net Worth
0.000USD
STEEM
0.003STEEM
SBD
0.000SBD
Effective Power
3.365SP
├── Own SP
0.000SP
└── Incoming DelegationsDeleg
+3.365SP
Detailed Balance
| STEEM | ||
| balance | 0.003STEEM | STEEM |
| market_balance | 0.000STEEM | STEEM |
| savings_balance | 0.000STEEM | STEEM |
| reward_steem_balance | 0.000STEEM | STEEM |
| STEEM POWER | ||
| Own SP | 0.000SP | SP |
| Delegated Out | 0.000SP | SP |
| Delegation In | 3.365SP | SP |
| Effective Power | 3.365SP | SP |
| Reward SP (pending) | 0.000SP | SP |
| SBD | ||
| sbd_balance | 0.000SBD | SBD |
| sbd_conversions | 0.000SBD | SBD |
| sbd_market_balance | 0.000SBD | SBD |
| savings_sbd_balance | 0.000SBD | SBD |
| reward_sbd_balance | 0.000SBD | SBD |
{
"balance": "0.003 STEEM",
"savings_balance": "0.000 STEEM",
"reward_steem_balance": "0.000 STEEM",
"vesting_shares": "0.000000 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "5472.996220 VESTS",
"sbd_balance": "0.000 SBD",
"savings_sbd_balance": "0.000 SBD",
"reward_sbd_balance": "0.000 SBD",
"conversions": []
}Account Info
| name | geoglitz |
| id | 1421445 |
| rank | 1,097,707 |
| reputation | 0 |
| created | 2020-09-13T15:34:06 |
| recovery_account | steem |
| proxy | None |
| post_count | 1 |
| comment_count | 0 |
| lifetime_vote_count | 0 |
| witnesses_voted_for | 0 |
| last_post | 2020-09-13T15:55:57 |
| last_root_post | 2020-09-13T15:55:57 |
| last_vote_time | 1970-01-01T00:00:00 |
| proxied_vsf_votes | 0, 0, 0, 0 |
| can_vote | 1 |
| voting_power | 0 |
| delayed_votes | 0 |
| balance | 0.003 STEEM |
| savings_balance | 0.000 STEEM |
| sbd_balance | 0.000 SBD |
| savings_sbd_balance | 0.000 SBD |
| vesting_shares | 0.000000 VESTS |
| delegated_vesting_shares | 0.000000 VESTS |
| received_vesting_shares | 5472.996220 VESTS |
| reward_vesting_balance | 0.000000 VESTS |
| vesting_balance | 0.000 STEEM |
| vesting_withdraw_rate | 0.000000 VESTS |
| next_vesting_withdrawal | 1969-12-31T23:59:59 |
| withdrawn | 0 |
| to_withdraw | 0 |
| withdraw_routes | 0 |
| savings_withdraw_requests | 0 |
| last_account_recovery | 1970-01-01T00:00:00 |
| reset_account | null |
| last_owner_update | 1970-01-01T00:00:00 |
| last_account_update | 1970-01-01T00:00:00 |
| mined | No |
| sbd_seconds | 0 |
| sbd_last_interest_payment | 1970-01-01T00:00:00 |
| savings_sbd_last_interest_payment | 1970-01-01T00:00:00 |
{
"id": 1421445,
"name": "geoglitz",
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7CgKMPwVuaKiG27pZokJGx2VcAsuYPMUsZfWMQWAY7JJyfwumC",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7pZwoZx3VCc6WGgSo2PQCaH8jUEzCpMjLWEApa93HFuWHmGaff",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7eunCKwq7bAHb8581fB7Mi9Rywut3BUdmMr98NLi6u279gbUND",
1
]
]
},
"memo_key": "STM4zR159b1KCsEeH46upuU89r64mHHRR8FE2fvxERNfJ9okzHe7V",
"json_metadata": "{}",
"posting_json_metadata": "",
"proxy": "",
"last_owner_update": "1970-01-01T00:00:00",
"last_account_update": "1970-01-01T00:00:00",
"created": "2020-09-13T15:34:06",
"mined": false,
"recovery_account": "steem",
"last_account_recovery": "1970-01-01T00:00:00",
"reset_account": "null",
"comment_count": 0,
"lifetime_vote_count": 0,
"post_count": 1,
"can_vote": true,
"voting_manabar": {
"current_mana": "5472996220",
"last_update_time": 1769158047
},
"downvote_manabar": {
"current_mana": 1368249055,
"last_update_time": 1769158047
},
"voting_power": 0,
"balance": "0.003 STEEM",
"savings_balance": "0.000 STEEM",
"sbd_balance": "0.000 SBD",
"sbd_seconds": "0",
"sbd_seconds_last_update": "1970-01-01T00:00:00",
"sbd_last_interest_payment": "1970-01-01T00:00:00",
"savings_sbd_balance": "0.000 SBD",
"savings_sbd_seconds": "0",
"savings_sbd_seconds_last_update": "1970-01-01T00:00:00",
"savings_sbd_last_interest_payment": "1970-01-01T00:00:00",
"savings_withdraw_requests": 0,
"reward_sbd_balance": "0.000 SBD",
"reward_steem_balance": "0.000 STEEM",
"reward_vesting_balance": "0.000000 VESTS",
"reward_vesting_steem": "0.000 STEEM",
"vesting_shares": "0.000000 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "5472.996220 VESTS",
"vesting_withdraw_rate": "0.000000 VESTS",
"next_vesting_withdrawal": "1969-12-31T23:59:59",
"withdrawn": 0,
"to_withdraw": 0,
"withdraw_routes": 0,
"curation_rewards": 0,
"posting_rewards": 0,
"proxied_vsf_votes": [
0,
0,
0,
0
],
"witnesses_voted_for": 0,
"last_post": "2020-09-13T15:55:57",
"last_root_post": "2020-09-13T15:55:57",
"last_vote_time": "1970-01-01T00:00:00",
"post_bandwidth": 0,
"pending_claimed_accounts": 0,
"vesting_balance": "0.000 STEEM",
"reputation": 0,
"transfer_history": [],
"market_history": [],
"post_history": [],
"vote_history": [],
"other_history": [],
"witness_votes": [],
"tags_usage": [],
"guest_bloggers": [],
"rank": 1097707
}Withdraw Routes
| Incoming | Outgoing |
|---|---|
Empty | Empty |
{
"incoming": [],
"outgoing": []
}From Date
To Date
2026/01/23 08:47:27
2026/01/23 08:47:27
| delegator | steem |
| delegatee | geoglitz |
| vesting shares | 5472.996220 VESTS |
| Transaction Info | Block #102852995/Trx 19cc996b0a18b83bc321ee6cd2d4244bcd14ee86 |
View Raw JSON Data
{
"trx_id": "19cc996b0a18b83bc321ee6cd2d4244bcd14ee86",
"block": 102852995,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-01-23T08:47:27",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "geoglitz",
"vesting_shares": "5472.996220 VESTS"
}
]
}2024/12/17 04:05:54
2024/12/17 04:05:54
| delegator | steem |
| delegatee | geoglitz |
| vesting shares | 5637.215417 VESTS |
| Transaction Info | Block #91299388/Trx 81513debda832d4c3853a4d4133dd64d4c514279 |
View Raw JSON Data
{
"trx_id": "81513debda832d4c3853a4d4133dd64d4c514279",
"block": 91299388,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2024-12-17T04:05:54",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "geoglitz",
"vesting_shares": "5637.215417 VESTS"
}
]
}2023/11/13 19:49:00
2023/11/13 19:49:00
| delegator | steem |
| delegatee | geoglitz |
| vesting shares | 5806.348949 VESTS |
| Transaction Info | Block #79853593/Trx 60d8590a695f234e68c75a6d657a3cc1225a83be |
View Raw JSON Data
{
"trx_id": "60d8590a695f234e68c75a6d657a3cc1225a83be",
"block": 79853593,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2023-11-13T19:49:00",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "geoglitz",
"vesting_shares": "5806.348949 VESTS"
}
]
}2023/09/21 22:15:45
2023/09/21 22:15:45
| delegator | steem |
| delegatee | geoglitz |
| vesting shares | 8743.627735 VESTS |
| Transaction Info | Block #78348345/Trx 527b59224621394ae4268f389943c6022e35d9b1 |
View Raw JSON Data
{
"trx_id": "527b59224621394ae4268f389943c6022e35d9b1",
"block": 78348345,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2023-09-21T22:15:45",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "geoglitz",
"vesting_shares": "8743.627735 VESTS"
}
]
}2022/11/03 12:00:00
2022/11/03 12:00:00
| delegator | steem |
| delegatee | geoglitz |
| vesting shares | 8965.309173 VESTS |
| Transaction Info | Block #69113616/Trx d96463b4c7822cf3b2b420fb36ea7eb2e5a02a42 |
View Raw JSON Data
{
"trx_id": "d96463b4c7822cf3b2b420fb36ea7eb2e5a02a42",
"block": 69113616,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2022-11-03T12:00:00",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "geoglitz",
"vesting_shares": "8965.309173 VESTS"
}
]
}2021/12/12 11:49:39
2021/12/12 11:49:39
| delegator | steem |
| delegatee | geoglitz |
| vesting shares | 9214.831560 VESTS |
| Transaction Info | Block #59783897/Trx 9e56fa9fc9e4903ce69f9aebed52d8c677da0474 |
View Raw JSON Data
{
"trx_id": "9e56fa9fc9e4903ce69f9aebed52d8c677da0474",
"block": 59783897,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2021-12-12T11:49:39",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "geoglitz",
"vesting_shares": "9214.831560 VESTS"
}
]
}2021/05/14 13:11:42
2021/05/14 13:11:42
| delegator | steem |
| delegatee | geoglitz |
| vesting shares | 9399.149057 VESTS |
| Transaction Info | Block #53736522/Trx 1b1b528c590a68c3a91b99c10c04b1b9f1f6cbab |
View Raw JSON Data
{
"trx_id": "1b1b528c590a68c3a91b99c10c04b1b9f1f6cbab",
"block": 53736522,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2021-05-14T13:11:42",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "geoglitz",
"vesting_shares": "9399.149057 VESTS"
}
]
}2020/11/14 00:11:54
2020/11/14 00:11:54
| delegator | steem |
| delegatee | geoglitz |
| vesting shares | 9587.203470 VESTS |
| Transaction Info | Block #48578629/Trx 59a4a0519ad74252c04613f35df065ab466fbae7 |
View Raw JSON Data
{
"trx_id": "59a4a0519ad74252c04613f35df065ab466fbae7",
"block": 48578629,
"trx_in_block": 21,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-11-14T00:11:54",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "geoglitz",
"vesting_shares": "9587.203470 VESTS"
}
]
}2020/11/10 02:20:15
2020/11/10 02:20:15
| delegator | steem |
| delegatee | geoglitz |
| vesting shares | 28774.751814 VESTS |
| Transaction Info | Block #48468210/Trx 8f245ffd8c5813bbb223e9d7166c6853dbb560d0 |
View Raw JSON Data
{
"trx_id": "8f245ffd8c5813bbb223e9d7166c6853dbb560d0",
"block": 48468210,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-11-10T02:20:15",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "geoglitz",
"vesting_shares": "28774.751814 VESTS"
}
]
}2020/09/13 20:20:27
2020/09/13 20:20:27
| delegator | steem |
| delegatee | geoglitz |
| vesting shares | 28967.525361 VESTS |
| Transaction Info | Block #46843433/Trx 48fa8905e1b4f667abeb5d08929a3d50bfee7890 |
View Raw JSON Data
{
"trx_id": "48fa8905e1b4f667abeb5d08929a3d50bfee7890",
"block": 46843433,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-09-13T20:20:27",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "geoglitz",
"vesting_shares": "28967.525361 VESTS"
}
]
}geoglitzpublished a new post: right-to-be-forgotten-blockchain-and-the-grand-algorand-solution2020/09/13 15:58:24
geoglitzpublished a new post: right-to-be-forgotten-blockchain-and-the-grand-algorand-solution
2020/09/13 15:58:24
| parent author | |
| parent permlink | mark |
| author | geoglitz |
| permlink | right-to-be-forgotten-blockchain-and-the-grand-algorand-solution |
| title | Right to be forgotten; Blockchain and the Grand Algorand Solution |
| body | @@ -333,152 +333,8 @@ t.%0A%0A -%3Ca href=%22https://www.betechwise.com/how-to-recover-your-snapchat-account/%22%3Ehttps://www.betechwise.com/how-to-recover-your-snapchat-account/%3C/a%3E%0A %0AThe @@ -840,16 +840,146 @@ ure now. + And related to %3Ca href=%22https://www.betechwise.com/how-to-recover-your-snapchat-account/%22%3E how to recover a snapchat account%3C/a%3E %0A%0APeople |
| json metadata | {"links":["https://www.betechwise.com/how-to-recover-your-snapchat-account/"],"app":"steemit/0.2","format":"markdown"} |
| Transaction Info | Block #46838255/Trx bd7ce7849230b3eec8f701899eb9295d881300e1 |
View Raw JSON Data
{
"trx_id": "bd7ce7849230b3eec8f701899eb9295d881300e1",
"block": 46838255,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-09-13T15:58:24",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "mark",
"author": "geoglitz",
"permlink": "right-to-be-forgotten-blockchain-and-the-grand-algorand-solution",
"title": "Right to be forgotten; Blockchain and the Grand Algorand Solution",
"body": "@@ -333,152 +333,8 @@\n t.%0A%0A\n-%3Ca href=%22https://www.betechwise.com/how-to-recover-your-snapchat-account/%22%3Ehttps://www.betechwise.com/how-to-recover-your-snapchat-account/%3C/a%3E%0A\n %0AThe\n@@ -840,16 +840,146 @@\n ure now.\n+ And related to %3Ca href=%22https://www.betechwise.com/how-to-recover-your-snapchat-account/%22%3E how to recover a snapchat account%3C/a%3E\n %0A%0APeople\n",
"json_metadata": "{\"links\":[\"https://www.betechwise.com/how-to-recover-your-snapchat-account/\"],\"app\":\"steemit/0.2\",\"format\":\"markdown\"}"
}
]
}beemenginesent 0.001 STEEM to @geoglitz- "🚀 The Best Blockchain Companion, Promoting all your upcoming posts 24/24. Subscribe today and we do all the rest for you, checkout it out on http://beemengine.live"2020/09/13 15:56:57
beemenginesent 0.001 STEEM to @geoglitz- "🚀 The Best Blockchain Companion, Promoting all your upcoming posts 24/24. Subscribe today and we do all the rest for you, checkout it out on http://beemengine.live"
2020/09/13 15:56:57
| from | beemengine |
| to | geoglitz |
| amount | 0.001 STEEM |
| memo | 🚀 The Best Blockchain Companion, Promoting all your upcoming posts 24/24. Subscribe today and we do all the rest for you, checkout it out on http://beemengine.live |
| Transaction Info | Block #46838226/Trx 061f14b075e36112be9d6979866e162ff654af2d |
View Raw JSON Data
{
"trx_id": "061f14b075e36112be9d6979866e162ff654af2d",
"block": 46838226,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-09-13T15:56:57",
"op": [
"transfer",
{
"from": "beemengine",
"to": "geoglitz",
"amount": "0.001 STEEM",
"memo": "🚀 The Best Blockchain Companion, Promoting all your upcoming posts 24/24. Subscribe today and we do all the rest for you, checkout it out on http://beemengine.live"
}
]
}geoglitzpublished a new post: right-to-be-forgotten-blockchain-and-the-grand-algorand-solution2020/09/13 15:55:57
geoglitzpublished a new post: right-to-be-forgotten-blockchain-and-the-grand-algorand-solution
2020/09/13 15:55:57
| parent author | |
| parent permlink | mark |
| author | geoglitz |
| permlink | right-to-be-forgotten-blockchain-and-the-grand-algorand-solution |
| title | Right to be forgotten; Blockchain and the Grand Algorand Solution |
| body | You may have heard of the term ‘Right to Be Forgotten’ or you’ve probably never heard about it before. Either way, this article will help you unravel all the mysteries that lie beyond the phrase as it meaning, importance, how it works, how it does affect the blockchain system, and how Algorand proposes a long-lasting approach to it. <a href="https://www.betechwise.com/how-to-recover-your-snapchat-account/">https://www.betechwise.com/how-to-recover-your-snapchat-account/</a> The phrase ‘right to be forgotten’ also means right to erasure which simply means that it is the right that an individual has to ask an organization, a company, a firm, an internet site or any entity at all that has to with the collection of personal data of different individuals i.e. in layman terms the right to delete my data from your database. This is the type of right that empowers you to go to google and say, I want all my records in your database to be removed completely. You get the picture now. People can ask for their data to be deleted if they feel that their data are being taken advantage of by the holder or if they feel like it isn’t necessary anymore. Also, people ask for data erasure if there are significant errors about them. There are so many reasons why data erasure rights can be exercised. Ever heard a phrase; for every free service, the users are the products. The reality is that a lot of tech companies exploit the data of their users in exchange for commercializing the data for potential ad publishers. However, that is not the focus of this article. In Europe and some other countries around the world, different policies around the world that guide data privacy and protection. The General Data Protection Regulation acts as a guide in which data collection and privacy work in Europe; the GDPR dictates the collection, processing, and erasing of data. Although, it wasn’t until 2014 that the ‘Right to Be Forgotten’ gained a lot of attention and a European Union Court of Justice set the precedents for the right to be forgotten that’s presently contained in the General Data Protection Regulation in article 17. The meaning and primary essence of the Right to erasure of course doesn’t necessarily mean that individuals can just ask for their private records to be erased anytime and the companies would be automatically compelled to do so. In the Data Protection Regulation, there are some terms and conditions that make sure that this right isn’t been taken advantage of. Otherwise, humans will always want to re-write their history. The 65th and 66th recitals in the article 17 of the General Data Protection Regulation clearly state that ‘’The data subject shall have the right to obtain from the controller the erasure of personal data concerning him or her without undue delay and the controller shall have the obligation to erase personal data without undue delay”. The concise truth in this is that a person can request for his or her data to be deleted by the person controlling such data with undue delay. Although undue delay usually takes about 1 month for the data holder to delete such data, in short, there is one month of grace. It is also very important that such a person asking for such data or records to be deleted must be the real owner; necessary verifications must be done to ensure that identity is true and not false represented. This right can only be exercised if the data is no longer necessary or if an organization legally needs the permission of the data owner before the data can be processed. It can also be exercised if the organization is using such data for marketing purposes and the data owner has contrary opinions as regards or if such data is processed unlawfully. The reasons are clearly stated in Article 17 of the General Data Protection Regulation. Although there are so many bases for the right of erasure to be pursued, it is also important to note that the General Data Protection Regulation (article 17) also points out the conditions that void this right. The right to erasure can be overridden if the data is being used to express freedom right, has legal backing, or is being used for public interest or public health purposes. The right of erasure can further be overridden if the data is being used for legal, historical, statistical, or research purposes. It is pertinent to note that the right to be forgotten doesn't apply to non-personal data, for instance, prices and costs of commodities cannot be asked to erase. If you buy a car for $5000 and it was recorded by such a company, of course, you cannot ask for that to be deleted. Some other scenarios that show that the right cannot be exercised, in cases of mortgage and insurance. The purpose of blockchain is to enable the recording and dissemination of digital information, but not editing. Blocks store transaction details such as the date, time; blocks also store information about people that engage in the transactions, however, instead of real names users’ details are more like keys (actually random numbers that you can’t even imagine). Blockchains are open public ledger that is visible to everyone although such information cannot be altered. Unlike other information tech systems such as Google, Facebook, Twitter, etc. that have a database of people’s data and information and handle requests (either approve or disapprove them) quite easily, Blockchains protocols do not work like that. The truth is that trying to remove a piece of the blockchain data can render the whole system useless and who in the world is in charge of deleting data as blockchain is made of different variety of users. Meanwhile, a trusted party can be empowered with the responsibility of carrying out such data such as editing data if blockchain can be centralized; it is however unfortunate that transparency and decentralization are the core foundations of blockchain security and trust. Of course, there are different generations and set of blockchain protocols. Each with its pros and cons, it is the only amazing to notice that there is a Balance Based Blockchain that seems to solve this problem of complying with European Union General Data Protection Regulation and at the same time, ensuring a decentralized blockchain system characterized with a balance of transparency and security. One of the most beautiful features of the Algorand protocol is that there are two categories of participants. The consensus users that generate and validate new blocks and transactions respectively, and the information service providers that make sure that new users can access already generated blocks. The technique applied in Algorand is the separation of erasable and non-erasable data and guarantees the post-erasure of any block by separately storing, although never erasing the hash of any erasable data. In layman terms, the traditional structure of blocks and transactions are being modified. This is a whole new game changer to both finance and the crypto world-at-large. European regulations are met and the integrity of the blockchain is preserved. Algorand continues to bring up innovative ways to solve real-life problems. |
| json metadata | {"tags":["mark"],"links":["https://www.betechwise.com/how-to-recover-your-snapchat-account/"],"app":"steemit/0.2","format":"markdown"} |
| Transaction Info | Block #46838206/Trx 0cc1f70aff751462981dcd5da80eb272fea4de36 |
View Raw JSON Data
{
"trx_id": "0cc1f70aff751462981dcd5da80eb272fea4de36",
"block": 46838206,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-09-13T15:55:57",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "mark",
"author": "geoglitz",
"permlink": "right-to-be-forgotten-blockchain-and-the-grand-algorand-solution",
"title": "Right to be forgotten; Blockchain and the Grand Algorand Solution",
"body": "You may have heard of the term ‘Right to Be Forgotten’ or you’ve probably never heard about it before. Either way, this article will help you unravel all the mysteries that lie beyond the phrase as it meaning, importance, how it works, how it does affect the blockchain system, and how Algorand proposes a long-lasting approach to it.\n\n<a href=\"https://www.betechwise.com/how-to-recover-your-snapchat-account/\">https://www.betechwise.com/how-to-recover-your-snapchat-account/</a>\n\nThe phrase ‘right to be forgotten’ also means right to erasure which simply means that it is the right that an individual has to ask an organization, a company, a firm, an internet site or any entity at all that has to with the collection of personal data of different individuals i.e. in layman terms the right to delete my data from your database. \n\nThis is the type of right that empowers you to go to google and say, I want all my records in your database to be removed completely. You get the picture now.\n\nPeople can ask for their data to be deleted if they feel that their data are being taken advantage of by the holder or if they feel like it isn’t necessary anymore. Also, people ask for data erasure if there are significant errors about them. There are so many reasons why data erasure rights can be exercised. Ever heard a phrase; for every free service, the users are the products. The reality is that a lot of tech companies exploit the data of their users in exchange for commercializing the data for potential ad publishers. However, that is not the focus of this article.\n\nIn Europe and some other countries around the world, different policies around the world that guide data privacy and protection. The General Data Protection Regulation acts as a guide in which data collection and privacy work in Europe; the GDPR dictates the collection, processing, and erasing of data. Although, it wasn’t until 2014 that the ‘Right to Be Forgotten’ gained a lot of attention and a European Union Court of Justice set the precedents for the right to be forgotten that’s presently contained in the General Data Protection Regulation in article 17.\nThe meaning and primary essence of the Right to erasure of course doesn’t necessarily mean that individuals can just ask for their private records to be erased anytime and the companies would be automatically compelled to do so. In the Data Protection Regulation, there are some terms and conditions that make sure that this right isn’t been taken advantage of. Otherwise, humans will always want to re-write their history.\n\nThe 65th and 66th recitals in the article 17 of the General Data Protection Regulation clearly state that ‘’The data subject shall have the right to obtain from the controller the erasure of personal data concerning him or her without undue delay and the controller shall have the obligation to erase personal data without undue delay”. The concise truth in this is that a person can request for his or her data to be deleted by the person controlling such data with undue delay. Although undue delay usually takes about 1 month for the data holder to delete such data, in short, there is one month of grace. It is also very important that such a person asking for such data or records to be deleted must be the real owner; necessary verifications must be done to ensure that identity is true and not false represented.\nThis right can only be exercised if the data is no longer necessary or if an organization legally needs the permission of the data owner before the data can be processed. It can also be exercised if the organization is using such data for marketing purposes and the data owner has contrary opinions as regards or if such data is processed unlawfully. The reasons are clearly stated in Article 17 of the General Data Protection Regulation.\n\nAlthough there are so many bases for the right of erasure to be pursued, it is also important to note that the General Data Protection Regulation (article 17) also points out the conditions that void this right. The right to erasure can be overridden if the data is being used to express freedom right, has legal backing, or is being used for public interest or public health purposes. The right of erasure can further be overridden if the data is being used for legal, historical, statistical, or research purposes.\n\nIt is pertinent to note that the right to be forgotten doesn't apply to non-personal data, for instance, prices and costs of commodities cannot be asked to erase. If you buy a car for $5000 and it was recorded by such a company, of course, you cannot ask for that to be deleted. Some other scenarios that show that the right cannot be exercised, in cases of mortgage and insurance.\nThe purpose of blockchain is to enable the recording and dissemination of digital information, but not editing. Blocks store transaction details such as the date, time; blocks also store information about people that engage in the transactions, however, instead of real names users’ details are more like keys (actually random numbers that you can’t even imagine). Blockchains are open public ledger that is visible to everyone although such information cannot be altered.\nUnlike other information tech systems such as Google, Facebook, Twitter, etc. that have a database of people’s data and information and handle requests (either approve or disapprove them) quite easily, Blockchains protocols do not work like that. The truth is that trying to remove a piece of the blockchain data can render the whole system useless and who in the world is in charge of deleting data as blockchain is made of different variety of users. \n\nMeanwhile, a trusted party can be empowered with the responsibility of carrying out such data such as editing data if blockchain can be centralized; it is however unfortunate that transparency and decentralization are the core foundations of blockchain security and trust.\nOf course, there are different generations and set of blockchain protocols. Each with its pros and cons, it is the only amazing to notice that there is a Balance Based Blockchain that seems to solve this problem of complying with European Union General Data Protection Regulation and at the same time, ensuring a decentralized blockchain system characterized with a balance of transparency and security. \n\nOne of the most beautiful features of the Algorand protocol is that there are two categories of participants. The consensus users that generate and validate new blocks and transactions respectively, and the information service providers that make sure that new users can access already generated blocks. The technique applied in Algorand is the separation of erasable and non-erasable data and guarantees the post-erasure of any block by separately storing, although never erasing the hash of any erasable data. In layman terms, the traditional structure of blocks and transactions are being modified. \n\nThis is a whole new game changer to both finance and the crypto world-at-large. European regulations are met and the integrity of the blockchain is preserved. Algorand continues to bring up innovative ways to solve real-life problems.",
"json_metadata": "{\"tags\":[\"mark\"],\"links\":[\"https://www.betechwise.com/how-to-recover-your-snapchat-account/\"],\"app\":\"steemit/0.2\",\"format\":\"markdown\"}"
}
]
}future.witnesssent 0.001 STEEM to @geoglitz- "⚠️ Please be careful with any website or discord link that you receive from other users, those are mostly phishing attempts."2020/09/13 15:35:54
future.witnesssent 0.001 STEEM to @geoglitz- "⚠️ Please be careful with any website or discord link that you receive from other users, those are mostly phishing attempts."
2020/09/13 15:35:54
| from | future.witness |
| to | geoglitz |
| amount | 0.001 STEEM |
| memo | ⚠️ Please be careful with any website or discord link that you receive from other users, those are mostly phishing attempts. |
| Transaction Info | Block #46837812/Trx 3bc10bd0f8cc23ba2e59abe767092afdcfb0f074 |
View Raw JSON Data
{
"trx_id": "3bc10bd0f8cc23ba2e59abe767092afdcfb0f074",
"block": 46837812,
"trx_in_block": 11,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-09-13T15:35:54",
"op": [
"transfer",
{
"from": "future.witness",
"to": "geoglitz",
"amount": "0.001 STEEM",
"memo": "⚠️ Please be careful with any website or discord link that you receive from other users, those are mostly phishing attempts."
}
]
}executive-boardsent 0.001 STEEM to @geoglitz- "❗ Hello geoglitz, welcome to the STEEM ecosystem. The Executive Board hereby invites you to https://discord.gg/KyBbmhh where you will get some insider infos on how you will earn the most coins. It's e..."2020/09/13 15:35:03
executive-boardsent 0.001 STEEM to @geoglitz- "❗ Hello geoglitz, welcome to the STEEM ecosystem. The Executive Board hereby invites you to https://discord.gg/KyBbmhh where you will get some insider infos on how you will earn the most coins. It's e..."
2020/09/13 15:35:03
| from | executive-board |
| to | geoglitz |
| amount | 0.001 STEEM |
| memo | ❗ Hello geoglitz, welcome to the STEEM ecosystem. The Executive Board hereby invites you to https://discord.gg/KyBbmhh where you will get some insider infos on how you will earn the most coins. It's easy, just follow the instructions. Warm regards, The Executive Board. |
| Transaction Info | Block #46837795/Trx e1eb6a8dbfea9141da4bbc03041909c158f6cbe7 |
View Raw JSON Data
{
"trx_id": "e1eb6a8dbfea9141da4bbc03041909c158f6cbe7",
"block": 46837795,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-09-13T15:35:03",
"op": [
"transfer",
{
"from": "executive-board",
"to": "geoglitz",
"amount": "0.001 STEEM",
"memo": "❗ Hello geoglitz, welcome to the STEEM ecosystem. The Executive Board hereby invites you to https://discord.gg/KyBbmhh where you will get some insider infos on how you will earn the most coins. It's easy, just follow the instructions. Warm regards, The Executive Board."
}
]
}2020/09/13 15:34:06
2020/09/13 15:34:06
| delegator | steem |
| delegatee | geoglitz |
| vesting shares | 30300.000000 VESTS |
| Transaction Info | Block #46837776/Trx 9397e7e3b9cd58c2203936eb3a1e42f38ff93ae5 |
View Raw JSON Data
{
"trx_id": "9397e7e3b9cd58c2203936eb3a1e42f38ff93ae5",
"block": 46837776,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-09-13T15:34:06",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "geoglitz",
"vesting_shares": "30300.000000 VESTS"
}
]
}2020/09/13 15:34:06
2020/09/13 15:34:06
| creator | steem |
| new account name | geoglitz |
| owner | {"weight_threshold":1,"account_auths":[],"key_auths":[["STM7CgKMPwVuaKiG27pZokJGx2VcAsuYPMUsZfWMQWAY7JJyfwumC",1]]} |
| active | {"weight_threshold":1,"account_auths":[],"key_auths":[["STM7pZwoZx3VCc6WGgSo2PQCaH8jUEzCpMjLWEApa93HFuWHmGaff",1]]} |
| posting | {"weight_threshold":1,"account_auths":[],"key_auths":[["STM7eunCKwq7bAHb8581fB7Mi9Rywut3BUdmMr98NLi6u279gbUND",1]]} |
| memo key | STM4zR159b1KCsEeH46upuU89r64mHHRR8FE2fvxERNfJ9okzHe7V |
| json metadata | {} |
| extensions | [] |
| Transaction Info | Block #46837776/Trx 9397e7e3b9cd58c2203936eb3a1e42f38ff93ae5 |
View Raw JSON Data
{
"trx_id": "9397e7e3b9cd58c2203936eb3a1e42f38ff93ae5",
"block": 46837776,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-09-13T15:34:06",
"op": [
"create_claimed_account",
{
"creator": "steem",
"new_account_name": "geoglitz",
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7CgKMPwVuaKiG27pZokJGx2VcAsuYPMUsZfWMQWAY7JJyfwumC",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7pZwoZx3VCc6WGgSo2PQCaH8jUEzCpMjLWEApa93HFuWHmGaff",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7eunCKwq7bAHb8581fB7Mi9Rywut3BUdmMr98NLi6u279gbUND",
1
]
]
},
"memo_key": "STM4zR159b1KCsEeH46upuU89r64mHHRR8FE2fvxERNfJ9okzHe7V",
"json_metadata": "{}",
"extensions": []
}
]
}Manabar
Voting Power100.00%
Downvote Power100.00%
Resource Credits100.00%
Reputation Progress0.00%
{
"voting_manabar": {
"current_mana": "5472996220",
"last_update_time": 1769158047
},
"downvote_manabar": {
"current_mana": 1368249055,
"last_update_time": 1769158047
},
"rc_account": {
"account": "geoglitz",
"rc_manabar": {
"current_mana": "11430783834",
"last_update_time": 1769158047
},
"max_rc_creation_adjustment": {
"amount": "5793568417",
"precision": 6,
"nai": "@@000000037"
},
"max_rc": "11266564637"
}
}Account Metadata
| POSTING JSON METADATA | |
| None | |
| JSON METADATA | |
| None |
{
"posting_json_metadata": {},
"json_metadata": {}
}Auth Keys
Owner
Single Signature
Public Keys
STM7CgKMPwVuaKiG27pZokJGx2VcAsuYPMUsZfWMQWAY7JJyfwumC1/1
Active
Single Signature
Public Keys
STM7pZwoZx3VCc6WGgSo2PQCaH8jUEzCpMjLWEApa93HFuWHmGaff1/1
Posting
Single Signature
Public Keys
STM7eunCKwq7bAHb8581fB7Mi9Rywut3BUdmMr98NLi6u279gbUND1/1
Memo
STM4zR159b1KCsEeH46upuU89r64mHHRR8FE2fvxERNfJ9okzHe7V
{
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7CgKMPwVuaKiG27pZokJGx2VcAsuYPMUsZfWMQWAY7JJyfwumC",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7pZwoZx3VCc6WGgSo2PQCaH8jUEzCpMjLWEApa93HFuWHmGaff",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7eunCKwq7bAHb8581fB7Mi9Rywut3BUdmMr98NLi6u279gbUND",
1
]
]
},
"memo": "STM4zR159b1KCsEeH46upuU89r64mHHRR8FE2fvxERNfJ9okzHe7V"
}Witness Votes
0 / 30
No active witness votes.
[]