VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS31.34%
Net Worth
0.034USD
STEEM
0.000STEEM
SBD
0.000SBD
Effective Power
5.001SP
├── Own SP
0.633SP
└── Incoming DelegationsDeleg
+4.368SP
Detailed Balance
| STEEM | ||
| balance | 0.000STEEM | STEEM |
| market_balance | 0.000STEEM | STEEM |
| savings_balance | 0.000STEEM | STEEM |
| reward_steem_balance | 0.000STEEM | STEEM |
| STEEM POWER | ||
| Own SP | 0.633SP | SP |
| Delegated Out | 0.000SP | SP |
| Delegation In | 4.368SP | SP |
| Effective Power | 5.001SP | SP |
| Reward SP (pending) | 0.000SP | SP |
| SBD | ||
| sbd_balance | 0.000SBD | SBD |
| sbd_conversions | 0.000SBD | SBD |
| sbd_market_balance | 0.000SBD | SBD |
| savings_sbd_balance | 0.000SBD | SBD |
| reward_sbd_balance | 0.000SBD | SBD |
{
"balance": "0.000 STEEM",
"savings_balance": "0.000 STEEM",
"reward_steem_balance": "0.000 STEEM",
"vesting_shares": "1030.603779 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "7113.056027 VESTS",
"sbd_balance": "0.000 SBD",
"savings_sbd_balance": "0.000 SBD",
"reward_sbd_balance": "0.000 SBD",
"conversions": []
}Account Info
| name | shapoy |
| id | 359911 |
| rank | 1,426,934 |
| reputation | 6495229856 |
| created | 2017-09-08T18:06:42 |
| recovery_account | steem |
| proxy | None |
| post_count | 9 |
| comment_count | 0 |
| lifetime_vote_count | 0 |
| witnesses_voted_for | 0 |
| last_post | 2017-09-20T09:56:12 |
| last_root_post | 2017-09-19T17:46:36 |
| last_vote_time | 2017-11-10T11:36:33 |
| proxied_vsf_votes | 0, 0, 0, 0 |
| can_vote | 1 |
| voting_power | 0 |
| delayed_votes | 0 |
| balance | 0.000 STEEM |
| savings_balance | 0.000 STEEM |
| sbd_balance | 0.000 SBD |
| savings_sbd_balance | 0.000 SBD |
| vesting_shares | 1030.603779 VESTS |
| delegated_vesting_shares | 0.000000 VESTS |
| received_vesting_shares | 7113.056027 VESTS |
| reward_vesting_balance | 0.000000 VESTS |
| vesting_balance | 0.000 STEEM |
| vesting_withdraw_rate | 0.000000 VESTS |
| next_vesting_withdrawal | 1969-12-31T23:59:59 |
| withdrawn | 0 |
| to_withdraw | 0 |
| withdraw_routes | 0 |
| savings_withdraw_requests | 0 |
| last_account_recovery | 1970-01-01T00:00:00 |
| reset_account | null |
| last_owner_update | 1970-01-01T00:00:00 |
| last_account_update | 2017-09-09T17:13:36 |
| 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": 359911,
"name": "shapoy",
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM8PCoaWx4ZtQdBgfAA2kCoGvJQPhyrWsdRG115gPewzNo3kdbaQ",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM4tx9mDgD6dpbPDXLpmFG6QTGwTZyxWc8vmDgEhmHTdy28mR6um",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7DKjN6iNAxFhE2xrENKo8CrvVq6ZWyH7MBZ83vqNbiARSoMwvd",
1
]
]
},
"memo_key": "STM6bNYAxL2GNuguzk7dBKAiohqHyr3Ceop5eD9YjFLiL6SUBcs7u",
"json_metadata": "{\"profile\":{\"profile_image\":\"http://media.zenfs.com/en-US/video/video.pd2upload.com/video.yahoofinance.com@8dfea102-b1a8-362e-9e14-5554f85eab4c_FULL.jpg\",\"cover_image\":\"https://www.bitcoinnews.ch/wp-content/uploads/2013/11/bitcoin.jpg\"}}",
"posting_json_metadata": "{\"profile\":{\"profile_image\":\"http://media.zenfs.com/en-US/video/video.pd2upload.com/video.yahoofinance.com@8dfea102-b1a8-362e-9e14-5554f85eab4c_FULL.jpg\",\"cover_image\":\"https://www.bitcoinnews.ch/wp-content/uploads/2013/11/bitcoin.jpg\"}}",
"proxy": "",
"last_owner_update": "1970-01-01T00:00:00",
"last_account_update": "2017-09-09T17:13:36",
"created": "2017-09-08T18:06:42",
"mined": false,
"recovery_account": "steem",
"last_account_recovery": "1970-01-01T00:00:00",
"reset_account": "null",
"comment_count": 0,
"lifetime_vote_count": 0,
"post_count": 9,
"can_vote": true,
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779085464
},
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779085464
},
"voting_power": 0,
"balance": "0.000 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": "1030.603779 VESTS",
"delegated_vesting_shares": "0.000000 VESTS",
"received_vesting_shares": "7113.056027 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": "2017-09-20T09:56:12",
"last_root_post": "2017-09-19T17:46:36",
"last_vote_time": "2017-11-10T11:36:33",
"post_bandwidth": 0,
"pending_claimed_accounts": 0,
"vesting_balance": "0.000 STEEM",
"reputation": "6495229856",
"transfer_history": [],
"market_history": [],
"post_history": [],
"vote_history": [],
"other_history": [],
"witness_votes": [],
"tags_usage": [],
"guest_bloggers": [],
"rank": 1426934
}Withdraw Routes
| Incoming | Outgoing |
|---|---|
Empty | Empty |
{
"incoming": [],
"outgoing": []
}From Date
To Date
2026/05/18 06:24:24
2026/05/18 06:24:24
| delegator | steem |
| delegatee | shapoy |
| vesting shares | 7113.056027 VESTS |
| Transaction Info | Block #106150800/Trx d9014862b6f39a8b542c44eef58d55ae1080721f |
View Raw JSON Data
{
"trx_id": "d9014862b6f39a8b542c44eef58d55ae1080721f",
"block": 106150800,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-05-18T06:24:24",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "shapoy",
"vesting_shares": "7113.056027 VESTS"
}
]
}2026/05/13 04:53:00
2026/05/13 04:53:00
| delegator | steem |
| delegatee | shapoy |
| vesting shares | 4400.845622 VESTS |
| Transaction Info | Block #106005691/Trx 8100d59bf338b0daa6e67223aae335a84cea7bf8 |
View Raw JSON Data
{
"trx_id": "8100d59bf338b0daa6e67223aae335a84cea7bf8",
"block": 106005691,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-05-13T04:53:00",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "shapoy",
"vesting_shares": "4400.845622 VESTS"
}
]
}2026/04/26 05:35:57
2026/04/26 05:35:57
| delegator | steem |
| delegatee | shapoy |
| vesting shares | 7125.571783 VESTS |
| Transaction Info | Block #105518280/Trx 37fa9fe977b5202dabb8a6d8a5851f9b77440fb0 |
View Raw JSON Data
{
"trx_id": "37fa9fe977b5202dabb8a6d8a5851f9b77440fb0",
"block": 105518280,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-04-26T05:35:57",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "shapoy",
"vesting_shares": "7125.571783 VESTS"
}
]
}2026/01/24 00:22:57
2026/01/24 00:22:57
| delegator | steem |
| delegatee | shapoy |
| vesting shares | 4442.392441 VESTS |
| Transaction Info | Block #102871672/Trx 132cc3a92b379569154c3bd0571cefa414937a7f |
View Raw JSON Data
{
"trx_id": "132cc3a92b379569154c3bd0571cefa414937a7f",
"block": 102871672,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2026-01-24T00:22:57",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "shapoy",
"vesting_shares": "4442.392441 VESTS"
}
]
}2024/12/17 19:32:48
2024/12/17 19:32:48
| delegator | steem |
| delegatee | shapoy |
| vesting shares | 4606.611638 VESTS |
| Transaction Info | Block #91317884/Trx da000b5fbe985fc6a8ca68b2b6302aed68cda3a0 |
View Raw JSON Data
{
"trx_id": "da000b5fbe985fc6a8ca68b2b6302aed68cda3a0",
"block": 91317884,
"trx_in_block": 12,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2024-12-17T19:32:48",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "shapoy",
"vesting_shares": "4606.611638 VESTS"
}
]
}2023/11/14 11:13:51
2023/11/14 11:13:51
| delegator | steem |
| delegatee | shapoy |
| vesting shares | 4775.745170 VESTS |
| Transaction Info | Block #79872029/Trx 977145f02d414cf9c5ae733214ae16e7e86f4710 |
View Raw JSON Data
{
"trx_id": "977145f02d414cf9c5ae733214ae16e7e86f4710",
"block": 79872029,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2023-11-14T11:13:51",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "shapoy",
"vesting_shares": "4775.745170 VESTS"
}
]
}2023/09/22 10:32:39
2023/09/22 10:32:39
| delegator | steem |
| delegatee | shapoy |
| vesting shares | 7712.653956 VESTS |
| Transaction Info | Block #78363048/Trx b2090c5c2bd2c0dfdd97684eeef0e6b760e08701 |
View Raw JSON Data
{
"trx_id": "b2090c5c2bd2c0dfdd97684eeef0e6b760e08701",
"block": 78363048,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2023-09-22T10:32:39",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "shapoy",
"vesting_shares": "7712.653956 VESTS"
}
]
}2022/11/03 17:58:45
2022/11/03 17:58:45
| delegator | steem |
| delegatee | shapoy |
| vesting shares | 7934.705394 VESTS |
| Transaction Info | Block #69120756/Trx 3f6526554190123e06407302f85178e11ef0b732 |
View Raw JSON Data
{
"trx_id": "3f6526554190123e06407302f85178e11ef0b732",
"block": 69120756,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2022-11-03T17:58:45",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "shapoy",
"vesting_shares": "7934.705394 VESTS"
}
]
}2022/01/17 23:10:00
2022/01/17 23:10:00
| delegator | steem |
| delegatee | shapoy |
| vesting shares | 8154.812995 VESTS |
| Transaction Info | Block #60823993/Trx b9cb571f4d0ad590c9b32b6af4905c51b1ddc3bd |
View Raw JSON Data
{
"trx_id": "b9cb571f4d0ad590c9b32b6af4905c51b1ddc3bd",
"block": 60823993,
"trx_in_block": 43,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2022-01-17T23:10:00",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "shapoy",
"vesting_shares": "8154.812995 VESTS"
}
]
}2021/06/14 06:20:30
2021/06/14 06:20:30
| delegator | steem |
| delegatee | shapoy |
| vesting shares | 8339.007283 VESTS |
| Transaction Info | Block #54614308/Trx 4cdf8fb37e6d66a464ac9db94b127f8aaa5ce4f8 |
View Raw JSON Data
{
"trx_id": "4cdf8fb37e6d66a464ac9db94b127f8aaa5ce4f8",
"block": 54614308,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2021-06-14T06:20:30",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "shapoy",
"vesting_shares": "8339.007283 VESTS"
}
]
}2020/12/11 16:32:30
2020/12/11 16:32:30
| delegator | steem |
| delegatee | shapoy |
| vesting shares | 8526.429257 VESTS |
| Transaction Info | Block #49361565/Trx 6275babaaa0bb96d586ef53ffadb1ec5b13bcf45 |
View Raw JSON Data
{
"trx_id": "6275babaaa0bb96d586ef53ffadb1ec5b13bcf45",
"block": 49361565,
"trx_in_block": 1,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-12-11T16:32:30",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "shapoy",
"vesting_shares": "8526.429257 VESTS"
}
]
}2020/12/06 10:08:12
2020/12/06 10:08:12
| delegator | steem |
| delegatee | shapoy |
| vesting shares | 1912.543513 VESTS |
| Transaction Info | Block #49213086/Trx e0d4704a7809d7daee739fce5c8f4e1ce7726322 |
View Raw JSON Data
{
"trx_id": "e0d4704a7809d7daee739fce5c8f4e1ce7726322",
"block": 49213086,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-12-06T10:08:12",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "shapoy",
"vesting_shares": "1912.543513 VESTS"
}
]
}2020/12/05 20:10:24
2020/12/05 20:10:24
| delegator | steem |
| delegatee | shapoy |
| vesting shares | 8532.637111 VESTS |
| Transaction Info | Block #49196651/Trx 01f28bdc86bf35ef5c695bfbc4f53f41bc44fbd6 |
View Raw JSON Data
{
"trx_id": "01f28bdc86bf35ef5c695bfbc4f53f41bc44fbd6",
"block": 49196651,
"trx_in_block": 8,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-12-05T20:10:24",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "shapoy",
"vesting_shares": "8532.637111 VESTS"
}
]
}2020/11/03 02:51:21
2020/11/03 02:51:21
| delegator | steem |
| delegatee | shapoy |
| vesting shares | 1920.017158 VESTS |
| Transaction Info | Block #48271008/Trx 046bf40a4e7d002ec19ed30de9b4db682e7faeae |
View Raw JSON Data
{
"trx_id": "046bf40a4e7d002ec19ed30de9b4db682e7faeae",
"block": 48271008,
"trx_in_block": 11,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-11-03T02:51:21",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "shapoy",
"vesting_shares": "1920.017158 VESTS"
}
]
}2020/05/09 11:11:24
2020/05/09 11:11:24
| delegator | steem |
| delegatee | shapoy |
| vesting shares | 8735.442470 VESTS |
| Transaction Info | Block #43223417/Trx 391b9630d51db6e557897f947510005589cb443b |
View Raw JSON Data
{
"trx_id": "391b9630d51db6e557897f947510005589cb443b",
"block": 43223417,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-05-09T11:11:24",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "shapoy",
"vesting_shares": "8735.442470 VESTS"
}
]
}2020/05/08 15:36:33
2020/05/08 15:36:33
| delegator | steem |
| delegatee | shapoy |
| vesting shares | 1953.311140 VESTS |
| Transaction Info | Block #43200477/Trx 43c89db09f9bf32f94d8fcc5db0aa06b82ccc477 |
View Raw JSON Data
{
"trx_id": "43c89db09f9bf32f94d8fcc5db0aa06b82ccc477",
"block": 43200477,
"trx_in_block": 17,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-05-08T15:36:33",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "shapoy",
"vesting_shares": "1953.311140 VESTS"
}
]
}2020/04/16 03:20:24
2020/04/16 03:20:24
| delegator | steem |
| delegatee | shapoy |
| vesting shares | 8748.329918 VESTS |
| Transaction Info | Block #42569206/Trx a2b9ff3530df81e014c1fed1cc7ec645a3441ac2 |
View Raw JSON Data
{
"trx_id": "a2b9ff3530df81e014c1fed1cc7ec645a3441ac2",
"block": 42569206,
"trx_in_block": 9,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2020-04-16T03:20:24",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "shapoy",
"vesting_shares": "8748.329918 VESTS"
}
]
}2019/09/08 18:33:00
2019/09/08 18:33:00
| parent author | shapoy |
| parent permlink | cryptocurrency-vs-world |
| author | steemitboard |
| permlink | steemitboard-notify-shapoy-20190908t183300000z |
| title | |
| body | Congratulations @shapoy! You received a personal award! <table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@shapoy/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/@shapoy) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=shapoy)_</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 #36249251/Trx 2dcdb741412a514ed936f0b70ac17363ae4c369f |
View Raw JSON Data
{
"trx_id": "2dcdb741412a514ed936f0b70ac17363ae4c369f",
"block": 36249251,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-09-08T18:33:00",
"op": [
"comment",
{
"parent_author": "shapoy",
"parent_permlink": "cryptocurrency-vs-world",
"author": "steemitboard",
"permlink": "steemitboard-notify-shapoy-20190908t183300000z",
"title": "",
"body": "Congratulations @shapoy! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@shapoy/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/@shapoy) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=shapoy)_</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\"]}"
}
]
}2019/05/12 20:27:27
2019/05/12 20:27:27
| delegator | steem |
| delegatee | shapoy |
| vesting shares | 8943.946731 VESTS |
| Transaction Info | Block #32852150/Trx 3a9bbd111cde4722c92b678cf64c55fd8a5fc64b |
View Raw JSON Data
{
"trx_id": "3a9bbd111cde4722c92b678cf64c55fd8a5fc64b",
"block": 32852150,
"trx_in_block": 18,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2019-05-12T20:27:27",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "shapoy",
"vesting_shares": "8943.946731 VESTS"
}
]
}sanfteupvoted (100.00%) @shapoy / rivetz-with-a-huge-potential2018/05/17 13:34:48
sanfteupvoted (100.00%) @shapoy / rivetz-with-a-huge-potential
2018/05/17 13:34:48
| voter | sanfte |
| author | shapoy |
| permlink | rivetz-with-a-huge-potential |
| weight | 10000 (100.00%) |
| Transaction Info | Block #22510593/Trx ac2abb04ef11dbebf3d12519308e87ab44168e78 |
View Raw JSON Data
{
"trx_id": "ac2abb04ef11dbebf3d12519308e87ab44168e78",
"block": 22510593,
"trx_in_block": 36,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-17T13:34:48",
"op": [
"vote",
{
"voter": "sanfte",
"author": "shapoy",
"permlink": "rivetz-with-a-huge-potential",
"weight": 10000
}
]
}2018/05/17 02:45:51
2018/05/17 02:45:51
| delegator | steem |
| delegatee | shapoy |
| vesting shares | 9143.461823 VESTS |
| Transaction Info | Block #22497617/Trx 0087e31f2c66f971a383b1adc4417cc4fb6dc4f7 |
View Raw JSON Data
{
"trx_id": "0087e31f2c66f971a383b1adc4417cc4fb6dc4f7",
"block": 22497617,
"trx_in_block": 121,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-05-17T02:45:51",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "shapoy",
"vesting_shares": "9143.461823 VESTS"
}
]
}dtubixreplied to @shapoy / re-cryptocurrency-vs-world-2652018/02/26 00:08:00
dtubixreplied to @shapoy / re-cryptocurrency-vs-world-265
2018/02/26 00:08:00
| parent author | shapoy |
| parent permlink | cryptocurrency-vs-world |
| author | dtubix |
| permlink | re-cryptocurrency-vs-world-265 |
| title | |
| body | Nice post! I will follow you from now on. |
| json metadata | |
| Transaction Info | Block #20192968/Trx a6c82dded6f9f070b06c96aff9f1d97f9dc8a6c8 |
View Raw JSON Data
{
"trx_id": "a6c82dded6f9f070b06c96aff9f1d97f9dc8a6c8",
"block": 20192968,
"trx_in_block": 74,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-26T00:08:00",
"op": [
"comment",
{
"parent_author": "shapoy",
"parent_permlink": "cryptocurrency-vs-world",
"author": "dtubix",
"permlink": "re-cryptocurrency-vs-world-265",
"title": "",
"body": "Nice post! I will follow you from now on. ",
"json_metadata": ""
}
]
}2018/02/22 12:29:39
2018/02/22 12:29:39
| delegator | steem |
| delegatee | shapoy |
| vesting shares | 29625.520130 VESTS |
| Transaction Info | Block #20092621/Trx d572b923211dd9051e2929ac732a00d4bfb779c0 |
View Raw JSON Data
{
"trx_id": "d572b923211dd9051e2929ac732a00d4bfb779c0",
"block": 20092621,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-22T12:29:39",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "shapoy",
"vesting_shares": "29625.520130 VESTS"
}
]
}2018/02/02 05:51:21
2018/02/02 05:51:21
| parent author | shapoy |
| parent permlink | the-next-bitcoin |
| author | shlw |
| permlink | re-shapoy-the-next-bitcoin-20180202t055127914z |
| title | |
| body | I know that IOTA will really go up and I have already bought them. Hopefully it will give us a good profit. |
| json metadata | {"tags":["bitcoin"],"app":"steemit/0.1"} |
| Transaction Info | Block #19509347/Trx 4a3fe3afd850a62399cc8574c616eaa27424e43b |
View Raw JSON Data
{
"trx_id": "4a3fe3afd850a62399cc8574c616eaa27424e43b",
"block": 19509347,
"trx_in_block": 16,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-02T05:51:21",
"op": [
"comment",
{
"parent_author": "shapoy",
"parent_permlink": "the-next-bitcoin",
"author": "shlw",
"permlink": "re-shapoy-the-next-bitcoin-20180202t055127914z",
"title": "",
"body": "I know that IOTA will really go up and I have already bought them. Hopefully it will give us a good profit.",
"json_metadata": "{\"tags\":[\"bitcoin\"],\"app\":\"steemit/0.1\"}"
}
]
}2018/02/02 05:10:57
2018/02/02 05:10:57
| parent author | shapoy |
| parent permlink | the-next-bitcoin |
| author | dwcp |
| permlink | re-shapoy-the-next-bitcoin-20180202t051104276z |
| title | |
| body | I learned a lot from your post.Thanks a lot. |
| json metadata | {"tags":["bitcoin"],"app":"steemit/0.1"} |
| Transaction Info | Block #19508540/Trx 78ef378ffcdf097275ffe0a76a621c4519831607 |
View Raw JSON Data
{
"trx_id": "78ef378ffcdf097275ffe0a76a621c4519831607",
"block": 19508540,
"trx_in_block": 48,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-02-02T05:10:57",
"op": [
"comment",
{
"parent_author": "shapoy",
"parent_permlink": "the-next-bitcoin",
"author": "dwcp",
"permlink": "re-shapoy-the-next-bitcoin-20180202t051104276z",
"title": "",
"body": "I learned a lot from your post.Thanks a lot.",
"json_metadata": "{\"tags\":[\"bitcoin\"],\"app\":\"steemit/0.1\"}"
}
]
}shapoyfollowed @dana-edwards2018/01/22 23:43:15
shapoyfollowed @dana-edwards
2018/01/22 23:43:15
| required auths | [] |
| required posting auths | ["shapoy"] |
| id | follow |
| json | ["follow",{"follower":"shapoy","following":"dana-edwards","what":["blog"]}] |
| Transaction Info | Block #19214214/Trx 8f357dbb823516edc05eafd960bbdea27a3d7551 |
View Raw JSON Data
{
"trx_id": "8f357dbb823516edc05eafd960bbdea27a3d7551",
"block": 19214214,
"trx_in_block": 14,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-22T23:43:15",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"shapoy"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"shapoy\",\"following\":\"dana-edwards\",\"what\":[\"blog\"]}]"
}
]
}2018/01/04 20:18:18
2018/01/04 20:18:18
| parent author | shapoy |
| parent permlink | etherparty-10-facher-gewinn-10-bagger |
| author | sogehts |
| permlink | re-shapoy-etherparty-10-facher-gewinn-10-bagger-20180104t201817092z |
| title | |
| body | Geht hoch mit etherparty! |
| json metadata | {"tags":["cryptocurrency"],"app":"steemit/0.1"} |
| Transaction Info | Block #18692093/Trx bfb2387cdd70e041c2c3af255382fca4abfad161 |
View Raw JSON Data
{
"trx_id": "bfb2387cdd70e041c2c3af255382fca4abfad161",
"block": 18692093,
"trx_in_block": 21,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-04T20:18:18",
"op": [
"comment",
{
"parent_author": "shapoy",
"parent_permlink": "etherparty-10-facher-gewinn-10-bagger",
"author": "sogehts",
"permlink": "re-shapoy-etherparty-10-facher-gewinn-10-bagger-20180104t201817092z",
"title": "",
"body": "Geht hoch mit etherparty!",
"json_metadata": "{\"tags\":[\"cryptocurrency\"],\"app\":\"steemit/0.1\"}"
}
]
}sogehtsupvoted (100.00%) @shapoy / etherparty-10-facher-gewinn-10-bagger2018/01/04 20:16:42
sogehtsupvoted (100.00%) @shapoy / etherparty-10-facher-gewinn-10-bagger
2018/01/04 20:16:42
| voter | sogehts |
| author | shapoy |
| permlink | etherparty-10-facher-gewinn-10-bagger |
| weight | 10000 (100.00%) |
| Transaction Info | Block #18692061/Trx f8b4ae7631182be6ba3dae708269c1e066e16370 |
View Raw JSON Data
{
"trx_id": "f8b4ae7631182be6ba3dae708269c1e066e16370",
"block": 18692061,
"trx_in_block": 50,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2018-01-04T20:16:42",
"op": [
"vote",
{
"voter": "sogehts",
"author": "shapoy",
"permlink": "etherparty-10-facher-gewinn-10-bagger",
"weight": 10000
}
]
}shapoyupvoted (100.00%) @minexsystems / minexcoin-park-the-volatility2017/11/10 11:36:33
shapoyupvoted (100.00%) @minexsystems / minexcoin-park-the-volatility
2017/11/10 11:36:33
| voter | shapoy |
| author | minexsystems |
| permlink | minexcoin-park-the-volatility |
| weight | 10000 (100.00%) |
| Transaction Info | Block #17098480/Trx 9d4255d274585299d4298e01cbe5336d42ea549f |
View Raw JSON Data
{
"trx_id": "9d4255d274585299d4298e01cbe5336d42ea549f",
"block": 17098480,
"trx_in_block": 19,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-11-10T11:36:33",
"op": [
"vote",
{
"voter": "shapoy",
"author": "minexsystems",
"permlink": "minexcoin-park-the-volatility",
"weight": 10000
}
]
}2017/10/13 16:04:00
2017/10/13 16:04:00
| delegator | steem |
| delegatee | shapoy |
| vesting shares | 29830.396221 VESTS |
| Transaction Info | Block #16298264/Trx 6d60e89d406b39dd840d76cff7196e80ef886d2a |
View Raw JSON Data
{
"trx_id": "6d60e89d406b39dd840d76cff7196e80ef886d2a",
"block": 16298264,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-10-13T16:04:00",
"op": [
"delegate_vesting_shares",
{
"delegator": "steem",
"delegatee": "shapoy",
"vesting_shares": "29830.396221 VESTS"
}
]
}2017/10/01 13:13:21
2017/10/01 13:13:21
| parent author | shapoy |
| parent permlink | rivetz-with-a-huge-potential |
| author | alexleehamilton |
| permlink | re-shapoy-rivetz-with-a-huge-potential-20171001t131252769z |
| title | |
| body | The project is amazing. I really believe that cyber security is key in this new blockchain era. After viewing the website I must say that the team looks legit! Strong. When will the product be released? |
| json metadata | {"tags":["cryptocurrency"],"app":"steemit/0.1"} |
| Transaction Info | Block #15949523/Trx ed65a1b853087c28864d4c7887d1af5f0f33d8fa |
View Raw JSON Data
{
"trx_id": "ed65a1b853087c28864d4c7887d1af5f0f33d8fa",
"block": 15949523,
"trx_in_block": 2,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-10-01T13:13:21",
"op": [
"comment",
{
"parent_author": "shapoy",
"parent_permlink": "rivetz-with-a-huge-potential",
"author": "alexleehamilton",
"permlink": "re-shapoy-rivetz-with-a-huge-potential-20171001t131252769z",
"title": "",
"body": "The project is amazing. I really believe that cyber security is key in this new blockchain era. \n\nAfter viewing the website I must say that the team looks legit! Strong. \n\nWhen will the product be released?",
"json_metadata": "{\"tags\":[\"cryptocurrency\"],\"app\":\"steemit/0.1\"}"
}
]
}alexleehamiltonupvoted (100.00%) @shapoy / rivetz-with-a-huge-potential2017/10/01 13:11:03
alexleehamiltonupvoted (100.00%) @shapoy / rivetz-with-a-huge-potential
2017/10/01 13:11:03
| voter | alexleehamilton |
| author | shapoy |
| permlink | rivetz-with-a-huge-potential |
| weight | 10000 (100.00%) |
| Transaction Info | Block #15949477/Trx 0c87ccd0286c95f2668f5ba8a012e84e397f8a55 |
View Raw JSON Data
{
"trx_id": "0c87ccd0286c95f2668f5ba8a012e84e397f8a55",
"block": 15949477,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-10-01T13:11:03",
"op": [
"vote",
{
"voter": "alexleehamilton",
"author": "shapoy",
"permlink": "rivetz-with-a-huge-potential",
"weight": 10000
}
]
}sovereignfinupvoted (100.00%) @shapoy / rivetz-with-a-huge-potential2017/09/28 10:46:30
sovereignfinupvoted (100.00%) @shapoy / rivetz-with-a-huge-potential
2017/09/28 10:46:30
| voter | sovereignfin |
| author | shapoy |
| permlink | rivetz-with-a-huge-potential |
| weight | 10000 (100.00%) |
| Transaction Info | Block #15860214/Trx 6453ca66b8c55430fdf26505b5a3ef655f5e72b1 |
View Raw JSON Data
{
"trx_id": "6453ca66b8c55430fdf26505b5a3ef655f5e72b1",
"block": 15860214,
"trx_in_block": 20,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-28T10:46:30",
"op": [
"vote",
{
"voter": "sovereignfin",
"author": "shapoy",
"permlink": "rivetz-with-a-huge-potential",
"weight": 10000
}
]
}shapoyfollowed @knozaki20152017/09/26 17:00:21
shapoyfollowed @knozaki2015
2017/09/26 17:00:21
| required auths | [] |
| required posting auths | ["shapoy"] |
| id | follow |
| json | ["follow",{"follower":"shapoy","following":"knozaki2015","what":["blog"]}] |
| Transaction Info | Block #15810119/Trx 1c6b543aab76431159844c9bb895eca50b3c5622 |
View Raw JSON Data
{
"trx_id": "1c6b543aab76431159844c9bb895eca50b3c5622",
"block": 15810119,
"trx_in_block": 21,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-26T17:00:21",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"shapoy"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"shapoy\",\"following\":\"knozaki2015\",\"what\":[\"blog\"]}]"
}
]
}2017/09/26 16:38:30
2017/09/26 16:38:30
| required auths | [] |
| required posting auths | ["shapoy"] |
| id | follow |
| json | ["follow",{"follower":"shapoy","following":"lumining","what":["blog"]}] |
| Transaction Info | Block #15809682/Trx 490f169ac9fffea8c82b1be1bae72afbc687d3b0 |
View Raw JSON Data
{
"trx_id": "490f169ac9fffea8c82b1be1bae72afbc687d3b0",
"block": 15809682,
"trx_in_block": 26,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-26T16:38:30",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"shapoy"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"shapoy\",\"following\":\"lumining\",\"what\":[\"blog\"]}]"
}
]
}shapoyremoved vote from (0.00%) @zeartul / welcome-to-the-future-okcash-cryptocurrency2017/09/21 07:23:39
shapoyremoved vote from (0.00%) @zeartul / welcome-to-the-future-okcash-cryptocurrency
2017/09/21 07:23:39
| voter | shapoy |
| author | zeartul |
| permlink | welcome-to-the-future-okcash-cryptocurrency |
| weight | 0 (0.00%) |
| Transaction Info | Block #15654613/Trx e95530de4c69b010f84981f5f971548a7948311d |
View Raw JSON Data
{
"trx_id": "e95530de4c69b010f84981f5f971548a7948311d",
"block": 15654613,
"trx_in_block": 18,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-21T07:23:39",
"op": [
"vote",
{
"voter": "shapoy",
"author": "zeartul",
"permlink": "welcome-to-the-future-okcash-cryptocurrency",
"weight": 0
}
]
}shapoyupvoted (100.00%) @inber / ship-in-a-starry-night-original-art-in-watercolor-and-ink-process-inside2017/09/20 10:04:39
shapoyupvoted (100.00%) @inber / ship-in-a-starry-night-original-art-in-watercolor-and-ink-process-inside
2017/09/20 10:04:39
| voter | shapoy |
| author | inber |
| permlink | ship-in-a-starry-night-original-art-in-watercolor-and-ink-process-inside |
| weight | 10000 (100.00%) |
| Transaction Info | Block #15629048/Trx 24aba32ab907541afd32a3b270d641f3fc3e964d |
View Raw JSON Data
{
"trx_id": "24aba32ab907541afd32a3b270d641f3fc3e964d",
"block": 15629048,
"trx_in_block": 11,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-20T10:04:39",
"op": [
"vote",
{
"voter": "shapoy",
"author": "inber",
"permlink": "ship-in-a-starry-night-original-art-in-watercolor-and-ink-process-inside",
"weight": 10000
}
]
}shapoyremoved vote from (0.00%) @foodnature / how-i-earned-17-000usd-in-2-month-with-cryptocurrency2017/09/20 10:03:24
shapoyremoved vote from (0.00%) @foodnature / how-i-earned-17-000usd-in-2-month-with-cryptocurrency
2017/09/20 10:03:24
| voter | shapoy |
| author | foodnature |
| permlink | how-i-earned-17-000usd-in-2-month-with-cryptocurrency |
| weight | 0 (0.00%) |
| Transaction Info | Block #15629023/Trx d18d0117a6b1fcc02b927d28d705ded93a7bb317 |
View Raw JSON Data
{
"trx_id": "d18d0117a6b1fcc02b927d28d705ded93a7bb317",
"block": 15629023,
"trx_in_block": 10,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-20T10:03:24",
"op": [
"vote",
{
"voter": "shapoy",
"author": "foodnature",
"permlink": "how-i-earned-17-000usd-in-2-month-with-cryptocurrency",
"weight": 0
}
]
}shapoyupvoted (100.00%) @foodnature / how-i-earned-17-000usd-in-2-month-with-cryptocurrency2017/09/20 10:03:09
shapoyupvoted (100.00%) @foodnature / how-i-earned-17-000usd-in-2-month-with-cryptocurrency
2017/09/20 10:03:09
| voter | shapoy |
| author | foodnature |
| permlink | how-i-earned-17-000usd-in-2-month-with-cryptocurrency |
| weight | 10000 (100.00%) |
| Transaction Info | Block #15629018/Trx e4aad703dd7808e26e3a6202354d88a5ae64a079 |
View Raw JSON Data
{
"trx_id": "e4aad703dd7808e26e3a6202354d88a5ae64a079",
"block": 15629018,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-20T10:03:09",
"op": [
"vote",
{
"voter": "shapoy",
"author": "foodnature",
"permlink": "how-i-earned-17-000usd-in-2-month-with-cryptocurrency",
"weight": 10000
}
]
}shapoyupvoted (100.00%) @fadlie / colorchallenge-wednesday-yellow-wedding-guards-2017920t17158720z2017/09/20 10:02:30
shapoyupvoted (100.00%) @fadlie / colorchallenge-wednesday-yellow-wedding-guards-2017920t17158720z
2017/09/20 10:02:30
| voter | shapoy |
| author | fadlie |
| permlink | colorchallenge-wednesday-yellow-wedding-guards-2017920t17158720z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #15629005/Trx 346fc049a3d8f13ccbe447cf2c9ad6125f069307 |
View Raw JSON Data
{
"trx_id": "346fc049a3d8f13ccbe447cf2c9ad6125f069307",
"block": 15629005,
"trx_in_block": 14,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-20T10:02:30",
"op": [
"vote",
{
"voter": "shapoy",
"author": "fadlie",
"permlink": "colorchallenge-wednesday-yellow-wedding-guards-2017920t17158720z",
"weight": 10000
}
]
}shapoyupvoted (100.00%) @julianti / beauty-2017920t17132202z2017/09/20 10:02:21
shapoyupvoted (100.00%) @julianti / beauty-2017920t17132202z
2017/09/20 10:02:21
| voter | shapoy |
| author | julianti |
| permlink | beauty-2017920t17132202z |
| weight | 10000 (100.00%) |
| Transaction Info | Block #15629002/Trx 84b0fa9c160ea6a5a943a1388fc132f5420b46f5 |
View Raw JSON Data
{
"trx_id": "84b0fa9c160ea6a5a943a1388fc132f5420b46f5",
"block": 15629002,
"trx_in_block": 5,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-20T10:02:21",
"op": [
"vote",
{
"voter": "shapoy",
"author": "julianti",
"permlink": "beauty-2017920t17132202z",
"weight": 10000
}
]
}shapoyupvoted (100.00%) @zeartul / welcome-to-the-future-okcash-cryptocurrency2017/09/20 09:56:24
shapoyupvoted (100.00%) @zeartul / welcome-to-the-future-okcash-cryptocurrency
2017/09/20 09:56:24
| voter | shapoy |
| author | zeartul |
| permlink | welcome-to-the-future-okcash-cryptocurrency |
| weight | 10000 (100.00%) |
| Transaction Info | Block #15628883/Trx 9bffecbde259ab5d8745ea61ae93b49c0b3fc494 |
View Raw JSON Data
{
"trx_id": "9bffecbde259ab5d8745ea61ae93b49c0b3fc494",
"block": 15628883,
"trx_in_block": 11,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-20T09:56:24",
"op": [
"vote",
{
"voter": "shapoy",
"author": "zeartul",
"permlink": "welcome-to-the-future-okcash-cryptocurrency",
"weight": 10000
}
]
}2017/09/20 09:56:12
2017/09/20 09:56:12
| parent author | zeartul |
| parent permlink | welcome-to-the-future-okcash-cryptocurrency |
| author | shapoy |
| permlink | re-zeartul-welcome-to-the-future-okcash-cryptocurrency-20170920t095611840z |
| title | |
| body | Great Info. I discovered Okcash a few weeks ago, when it was $0.08. There was a big jump already, but I'm sure it will rise to $1-$2 short-/midterm when the dev-team leaks its full potential ;) |
| json metadata | {"tags":["okcash"],"app":"steemit/0.1"} |
| Transaction Info | Block #15628879/Trx af8601fde77d467bb00f4ae880777a528974c3e0 |
View Raw JSON Data
{
"trx_id": "af8601fde77d467bb00f4ae880777a528974c3e0",
"block": 15628879,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-20T09:56:12",
"op": [
"comment",
{
"parent_author": "zeartul",
"parent_permlink": "welcome-to-the-future-okcash-cryptocurrency",
"author": "shapoy",
"permlink": "re-zeartul-welcome-to-the-future-okcash-cryptocurrency-20170920t095611840z",
"title": "",
"body": "Great Info. I discovered Okcash a few weeks ago, when it was $0.08. There was a big jump already, but I'm sure it will rise to $1-$2 short-/midterm when the dev-team leaks its full potential ;)",
"json_metadata": "{\"tags\":[\"okcash\"],\"app\":\"steemit/0.1\"}"
}
]
}marcfariupvoted (100.00%) @shapoy / cryptocurrency-vs-world2017/09/20 01:59:03
marcfariupvoted (100.00%) @shapoy / cryptocurrency-vs-world
2017/09/20 01:59:03
| voter | marcfari |
| author | shapoy |
| permlink | cryptocurrency-vs-world |
| weight | 10000 (100.00%) |
| Transaction Info | Block #15619341/Trx a7a5befa8791a2eb003215f525360b50cf92c87a |
View Raw JSON Data
{
"trx_id": "a7a5befa8791a2eb003215f525360b50cf92c87a",
"block": 15619341,
"trx_in_block": 8,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-20T01:59:03",
"op": [
"vote",
{
"voter": "marcfari",
"author": "shapoy",
"permlink": "cryptocurrency-vs-world",
"weight": 10000
}
]
}craigcryptokingupvoted (100.00%) @shapoy / cryptocurrency-vs-world2017/09/19 17:49:24
craigcryptokingupvoted (100.00%) @shapoy / cryptocurrency-vs-world
2017/09/19 17:49:24
| voter | craigcryptoking |
| author | shapoy |
| permlink | cryptocurrency-vs-world |
| weight | 10000 (100.00%) |
| Transaction Info | Block #15609550/Trx 070615004c5b1215f8fc01eae841855a63e01576 |
View Raw JSON Data
{
"trx_id": "070615004c5b1215f8fc01eae841855a63e01576",
"block": 15609550,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-19T17:49:24",
"op": [
"vote",
{
"voter": "craigcryptoking",
"author": "shapoy",
"permlink": "cryptocurrency-vs-world",
"weight": 10000
}
]
}rahmatidhamiupvoted (100.00%) @shapoy / cryptocurrency-vs-world2017/09/19 17:47:51
rahmatidhamiupvoted (100.00%) @shapoy / cryptocurrency-vs-world
2017/09/19 17:47:51
| voter | rahmatidhami |
| author | shapoy |
| permlink | cryptocurrency-vs-world |
| weight | 10000 (100.00%) |
| Transaction Info | Block #15609519/Trx 5ebba1119ea71785ab64295a4b3126dbff966a92 |
View Raw JSON Data
{
"trx_id": "5ebba1119ea71785ab64295a4b3126dbff966a92",
"block": 15609519,
"trx_in_block": 12,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-19T17:47:51",
"op": [
"vote",
{
"voter": "rahmatidhami",
"author": "shapoy",
"permlink": "cryptocurrency-vs-world",
"weight": 10000
}
]
}shapoyupdated options for cryptocurrency-vs-world2017/09/19 17:46:36
shapoyupdated options for cryptocurrency-vs-world
2017/09/19 17:46:36
| author | shapoy |
| permlink | cryptocurrency-vs-world |
| max accepted payout | 1000000.000 SBD |
| percent steem dollars | 0 |
| allow votes | true |
| allow curation rewards | true |
| extensions | [] |
| Transaction Info | Block #15609494/Trx 979dacdc0a2e188e661326fb0e7ff4cd1a0d80fe |
View Raw JSON Data
{
"trx_id": "979dacdc0a2e188e661326fb0e7ff4cd1a0d80fe",
"block": 15609494,
"trx_in_block": 31,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-19T17:46:36",
"op": [
"comment_options",
{
"author": "shapoy",
"permlink": "cryptocurrency-vs-world",
"max_accepted_payout": "1000000.000 SBD",
"percent_steem_dollars": 0,
"allow_votes": true,
"allow_curation_rewards": true,
"extensions": []
}
]
}shapoypublished a new post: cryptocurrency-vs-world2017/09/19 17:46:36
shapoypublished a new post: cryptocurrency-vs-world
2017/09/19 17:46:36
| parent author | |
| parent permlink | cryptocurrency |
| author | shapoy |
| permlink | cryptocurrency-vs-world |
| title | Cryptocurrency vs World |
| body |  |
| json metadata | {"tags":["cryptocurrency","iota","bitcoin","altcoins"],"image":["https://steemitimages.com/DQmTVHF4gC5pbUhtTE9F7zCjiELtMs3ZQBu229k6jfuC7X4/tx9ziLP.jpg"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #15609494/Trx 979dacdc0a2e188e661326fb0e7ff4cd1a0d80fe |
View Raw JSON Data
{
"trx_id": "979dacdc0a2e188e661326fb0e7ff4cd1a0d80fe",
"block": 15609494,
"trx_in_block": 31,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-19T17:46:36",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "cryptocurrency",
"author": "shapoy",
"permlink": "cryptocurrency-vs-world",
"title": "Cryptocurrency vs World",
"body": "",
"json_metadata": "{\"tags\":[\"cryptocurrency\",\"iota\",\"bitcoin\",\"altcoins\"],\"image\":[\"https://steemitimages.com/DQmTVHF4gC5pbUhtTE9F7zCjiELtMs3ZQBu229k6jfuC7X4/tx9ziLP.jpg\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}2017/09/19 12:45:21
2017/09/19 12:45:21
| parent author | shapoy |
| parent permlink | iota-dag-tangle |
| author | ridwant |
| permlink | re-shapoy-iota-dag-tangle-20170919t124521985z |
| title | |
| body | @shapoy I happy you come to my place. thank you. |
| json metadata | {"tags":["iota"],"users":["shapoy"],"app":"steemit/0.1"} |
| Transaction Info | Block #15603471/Trx 61ffd8eb1776369726f002ae5dd3e5ac5dc0d966 |
View Raw JSON Data
{
"trx_id": "61ffd8eb1776369726f002ae5dd3e5ac5dc0d966",
"block": 15603471,
"trx_in_block": 18,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-19T12:45:21",
"op": [
"comment",
{
"parent_author": "shapoy",
"parent_permlink": "iota-dag-tangle",
"author": "ridwant",
"permlink": "re-shapoy-iota-dag-tangle-20170919t124521985z",
"title": "",
"body": "@shapoy I happy you come to my place. thank you.",
"json_metadata": "{\"tags\":[\"iota\"],\"users\":[\"shapoy\"],\"app\":\"steemit/0.1\"}"
}
]
}2017/09/19 08:43:09
2017/09/19 08:43:09
| parent author | shapoy |
| parent permlink | iota-dag-tangle |
| author | ridwant |
| permlink | re-shapoy-iota-dag-tangle-20170919t084308009z |
| title | |
| body | @shapoy thank you |
| json metadata | {"tags":["iota"],"users":["shapoy"],"app":"steemit/0.1"} |
| Transaction Info | Block #15598627/Trx e0088fc9ec9208a066e128bd5957ff93fbaae614 |
View Raw JSON Data
{
"trx_id": "e0088fc9ec9208a066e128bd5957ff93fbaae614",
"block": 15598627,
"trx_in_block": 9,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-19T08:43:09",
"op": [
"comment",
{
"parent_author": "shapoy",
"parent_permlink": "iota-dag-tangle",
"author": "ridwant",
"permlink": "re-shapoy-iota-dag-tangle-20170919t084308009z",
"title": "",
"body": "@shapoy thank you",
"json_metadata": "{\"tags\":[\"iota\"],\"users\":[\"shapoy\"],\"app\":\"steemit/0.1\"}"
}
]
}shapoyupvoted (100.00%) @karensuestudios / weekend-getaway-adventures-in-chicago2017/09/19 08:23:36
shapoyupvoted (100.00%) @karensuestudios / weekend-getaway-adventures-in-chicago
2017/09/19 08:23:36
| voter | shapoy |
| author | karensuestudios |
| permlink | weekend-getaway-adventures-in-chicago |
| weight | 10000 (100.00%) |
| Transaction Info | Block #15598236/Trx 014b8ad9814a8e077d67dc7057f2051e91dcdd07 |
View Raw JSON Data
{
"trx_id": "014b8ad9814a8e077d67dc7057f2051e91dcdd07",
"block": 15598236,
"trx_in_block": 37,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-19T08:23:36",
"op": [
"vote",
{
"voter": "shapoy",
"author": "karensuestudios",
"permlink": "weekend-getaway-adventures-in-chicago",
"weight": 10000
}
]
}shapoyupvoted (100.00%) @kingscrown / china-bans-exchanges-japan-takesover2017/09/19 08:21:15
shapoyupvoted (100.00%) @kingscrown / china-bans-exchanges-japan-takesover
2017/09/19 08:21:15
| voter | shapoy |
| author | kingscrown |
| permlink | china-bans-exchanges-japan-takesover |
| weight | 10000 (100.00%) |
| Transaction Info | Block #15598189/Trx 6a186272b480aee144578696c678a01b0c92399c |
View Raw JSON Data
{
"trx_id": "6a186272b480aee144578696c678a01b0c92399c",
"block": 15598189,
"trx_in_block": 17,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-19T08:21:15",
"op": [
"vote",
{
"voter": "shapoy",
"author": "kingscrown",
"permlink": "china-bans-exchanges-japan-takesover",
"weight": 10000
}
]
}shapoyupvoted (100.00%) @ridwant / how-to-get-follower-in-steemit-building-foundation-with-follower2017/09/19 08:18:27
shapoyupvoted (100.00%) @ridwant / how-to-get-follower-in-steemit-building-foundation-with-follower
2017/09/19 08:18:27
| voter | shapoy |
| author | ridwant |
| permlink | how-to-get-follower-in-steemit-building-foundation-with-follower |
| weight | 10000 (100.00%) |
| Transaction Info | Block #15598133/Trx 5c1674a6813f5a2bc8ed214ee66975d2adbb7ee0 |
View Raw JSON Data
{
"trx_id": "5c1674a6813f5a2bc8ed214ee66975d2adbb7ee0",
"block": 15598133,
"trx_in_block": 11,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-19T08:18:27",
"op": [
"vote",
{
"voter": "shapoy",
"author": "ridwant",
"permlink": "how-to-get-follower-in-steemit-building-foundation-with-follower",
"weight": 10000
}
]
}shapoyremoved vote from (0.00%) @sanevys / when-was-tom-and-jerry-made2017/09/19 08:16:03
shapoyremoved vote from (0.00%) @sanevys / when-was-tom-and-jerry-made
2017/09/19 08:16:03
| voter | shapoy |
| author | sanevys |
| permlink | when-was-tom-and-jerry-made |
| weight | 0 (0.00%) |
| Transaction Info | Block #15598085/Trx 48918302887f895c24d06e673f90c5a122d39c21 |
View Raw JSON Data
{
"trx_id": "48918302887f895c24d06e673f90c5a122d39c21",
"block": 15598085,
"trx_in_block": 9,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-19T08:16:03",
"op": [
"vote",
{
"voter": "shapoy",
"author": "sanevys",
"permlink": "when-was-tom-and-jerry-made",
"weight": 0
}
]
}shapoyupvoted (100.00%) @sanevys / when-was-tom-and-jerry-made2017/09/19 08:15:39
shapoyupvoted (100.00%) @sanevys / when-was-tom-and-jerry-made
2017/09/19 08:15:39
| voter | shapoy |
| author | sanevys |
| permlink | when-was-tom-and-jerry-made |
| weight | 10000 (100.00%) |
| Transaction Info | Block #15598077/Trx a447a6753aa97996393da98021cacf27df6d942c |
View Raw JSON Data
{
"trx_id": "a447a6753aa97996393da98021cacf27df6d942c",
"block": 15598077,
"trx_in_block": 3,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-19T08:15:39",
"op": [
"vote",
{
"voter": "shapoy",
"author": "sanevys",
"permlink": "when-was-tom-and-jerry-made",
"weight": 10000
}
]
}shapoyremoved vote from (0.00%) @unbeaten / bitcoin-usd25-000-former-jp-morgan-strategist-tom-lee-on-cnbc2017/09/19 08:13:39
shapoyremoved vote from (0.00%) @unbeaten / bitcoin-usd25-000-former-jp-morgan-strategist-tom-lee-on-cnbc
2017/09/19 08:13:39
| voter | shapoy |
| author | unbeaten |
| permlink | bitcoin-usd25-000-former-jp-morgan-strategist-tom-lee-on-cnbc |
| weight | 0 (0.00%) |
| Transaction Info | Block #15598037/Trx fd06bf6bb95fb49a856311733a19d803f1b3ed06 |
View Raw JSON Data
{
"trx_id": "fd06bf6bb95fb49a856311733a19d803f1b3ed06",
"block": 15598037,
"trx_in_block": 36,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-19T08:13:39",
"op": [
"vote",
{
"voter": "shapoy",
"author": "unbeaten",
"permlink": "bitcoin-usd25-000-former-jp-morgan-strategist-tom-lee-on-cnbc",
"weight": 0
}
]
}shapoyupvoted (100.00%) @unbeaten / bitcoin-usd25-000-former-jp-morgan-strategist-tom-lee-on-cnbc2017/09/19 08:13:30
shapoyupvoted (100.00%) @unbeaten / bitcoin-usd25-000-former-jp-morgan-strategist-tom-lee-on-cnbc
2017/09/19 08:13:30
| voter | shapoy |
| author | unbeaten |
| permlink | bitcoin-usd25-000-former-jp-morgan-strategist-tom-lee-on-cnbc |
| weight | 10000 (100.00%) |
| Transaction Info | Block #15598034/Trx 9149a790ec6fba07388df3b266f74d6bd3ea4de5 |
View Raw JSON Data
{
"trx_id": "9149a790ec6fba07388df3b266f74d6bd3ea4de5",
"block": 15598034,
"trx_in_block": 20,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-19T08:13:30",
"op": [
"vote",
{
"voter": "shapoy",
"author": "unbeaten",
"permlink": "bitcoin-usd25-000-former-jp-morgan-strategist-tom-lee-on-cnbc",
"weight": 10000
}
]
}tomiscuriousupvoted (8.00%) @shapoy / excerpt-from-zcoinofficial-no-rewards2017/09/18 16:33:00
tomiscuriousupvoted (8.00%) @shapoy / excerpt-from-zcoinofficial-no-rewards
2017/09/18 16:33:00
| voter | tomiscurious |
| author | shapoy |
| permlink | excerpt-from-zcoinofficial-no-rewards |
| weight | 800 (8.00%) |
| Transaction Info | Block #15579241/Trx e142fb11edb8fa99c7b7f5b699bdc73e13e0b3d8 |
View Raw JSON Data
{
"trx_id": "e142fb11edb8fa99c7b7f5b699bdc73e13e0b3d8",
"block": 15579241,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-18T16:33:00",
"op": [
"vote",
{
"voter": "tomiscurious",
"author": "shapoy",
"permlink": "excerpt-from-zcoinofficial-no-rewards",
"weight": 800
}
]
}2017/09/18 16:26:12
2017/09/18 16:26:12
| required auths | [] |
| required posting auths | ["shapoy"] |
| id | follow |
| json | ["follow",{"follower":"shapoy","following":"cheetah","what":[]}] |
| Transaction Info | Block #15579111/Trx 0346c250ffc4c7521168d675495ea79228a7bd52 |
View Raw JSON Data
{
"trx_id": "0346c250ffc4c7521168d675495ea79228a7bd52",
"block": 15579111,
"trx_in_block": 6,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-18T16:26:12",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"shapoy"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"shapoy\",\"following\":\"cheetah\",\"what\":[]}]"
}
]
}shapoypublished a new post: iota-dag-tangle2017/09/18 16:25:54
shapoypublished a new post: iota-dag-tangle
2017/09/18 16:25:54
| parent author | |
| parent permlink | iota |
| author | shapoy |
| permlink | iota-dag-tangle |
| title | IOTA DAG Tangle |
| body | @@ -10514,8 +10514,170 @@ devices. +%0A%0Arelink: https://medium.com/@cstoecker/implementing-first-industry-4-0-use-cases-with-iota-dag-tangle-machine-tagging-for-digital-twins-baf1943c499d%0A(no rewards) |
| json metadata | {"tags":["iota","cryptocurrencies","bitcoin","altcoin","sleeper"],"image":["https://steemitimages.com/DQmR9B1T7M6ZsMDpBrymsYaComWVLXwfSxqAVCTDFA1xfhN/internet-of-things-analytics.jpg","https://steemitimages.com/DQmbGcqjeDfXUan5JYtfTuyyiuHJR5iZqsN7J94irZxTkDG/1*s0Da8mqgARZW9QtREjH6ag.png","https://steemitimages.com/DQmdb9QDnZAeihUPUUg9X3uutsJMPZZgU3rR2r5oSiiCb11/1*Pig9XwK3wXrznImQtt8oMA.png"],"app":"steemit/0.1","format":"markdown","links":["https://medium.com/@cstoecker/implementing-first-industry-4-0-use-cases-with-iota-dag-tangle-machine-tagging-for-digital-twins-baf1943c499d"]} |
| Transaction Info | Block #15579105/Trx b1945341d6eb5ef3212187e9025f7f5012a20bff |
View Raw JSON Data
{
"trx_id": "b1945341d6eb5ef3212187e9025f7f5012a20bff",
"block": 15579105,
"trx_in_block": 37,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-18T16:25:54",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "iota",
"author": "shapoy",
"permlink": "iota-dag-tangle",
"title": "IOTA DAG Tangle",
"body": "@@ -10514,8 +10514,170 @@\n devices.\n+%0A%0Arelink: https://medium.com/@cstoecker/implementing-first-industry-4-0-use-cases-with-iota-dag-tangle-machine-tagging-for-digital-twins-baf1943c499d%0A(no rewards)\n",
"json_metadata": "{\"tags\":[\"iota\",\"cryptocurrencies\",\"bitcoin\",\"altcoin\",\"sleeper\"],\"image\":[\"https://steemitimages.com/DQmR9B1T7M6ZsMDpBrymsYaComWVLXwfSxqAVCTDFA1xfhN/internet-of-things-analytics.jpg\",\"https://steemitimages.com/DQmbGcqjeDfXUan5JYtfTuyyiuHJR5iZqsN7J94irZxTkDG/1*s0Da8mqgARZW9QtREjH6ag.png\",\"https://steemitimages.com/DQmdb9QDnZAeihUPUUg9X3uutsJMPZZgU3rR2r5oSiiCb11/1*Pig9XwK3wXrznImQtt8oMA.png\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\",\"links\":[\"https://medium.com/@cstoecker/implementing-first-industry-4-0-use-cases-with-iota-dag-tangle-machine-tagging-for-digital-twins-baf1943c499d\"]}"
}
]
}2017/09/18 16:25:15
2017/09/18 16:25:15
| required auths | [] |
| required posting auths | ["shapoy"] |
| id | follow |
| json | ["follow",{"follower":"shapoy","following":"cheetah","what":["ignore"]}] |
| Transaction Info | Block #15579092/Trx 61ded246fa0ec7508e726840a11377f9a18794f7 |
View Raw JSON Data
{
"trx_id": "61ded246fa0ec7508e726840a11377f9a18794f7",
"block": 15579092,
"trx_in_block": 4,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-18T16:25:15",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"shapoy"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"shapoy\",\"following\":\"cheetah\",\"what\":[\"ignore\"]}]"
}
]
}shapoypublished a new post: iota-dag-tangle2017/09/18 16:23:39
shapoypublished a new post: iota-dag-tangle
2017/09/18 16:23:39
| parent author | |
| parent permlink | iota |
| author | shapoy |
| permlink | iota-dag-tangle |
| title | IOTA DAG Tangle |
| body | @@ -230,16 +230,161 @@ heres.%0A%0A +!%5Binternet-of-things-analytics.jpg%5D(https://steemitimages.com/DQmR9B1T7M6ZsMDpBrymsYaComWVLXwfSxqAVCTDFA1xfhN/internet-of-things-analytics.jpg)%0A%0A A variet |
| json metadata | {"tags":["iota","cryptocurrencies","bitcoin","altcoin","sleeper"],"image":["https://steemitimages.com/DQmR9B1T7M6ZsMDpBrymsYaComWVLXwfSxqAVCTDFA1xfhN/internet-of-things-analytics.jpg","https://steemitimages.com/DQmbGcqjeDfXUan5JYtfTuyyiuHJR5iZqsN7J94irZxTkDG/1*s0Da8mqgARZW9QtREjH6ag.png","https://steemitimages.com/DQmdb9QDnZAeihUPUUg9X3uutsJMPZZgU3rR2r5oSiiCb11/1*Pig9XwK3wXrznImQtt8oMA.png"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #15579062/Trx 07fbcb8e1376f51ea9aa90ce687b0d682b23b842 |
View Raw JSON Data
{
"trx_id": "07fbcb8e1376f51ea9aa90ce687b0d682b23b842",
"block": 15579062,
"trx_in_block": 25,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-18T16:23:39",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "iota",
"author": "shapoy",
"permlink": "iota-dag-tangle",
"title": "IOTA DAG Tangle",
"body": "@@ -230,16 +230,161 @@\n heres.%0A%0A\n+!%5Binternet-of-things-analytics.jpg%5D(https://steemitimages.com/DQmR9B1T7M6ZsMDpBrymsYaComWVLXwfSxqAVCTDFA1xfhN/internet-of-things-analytics.jpg)%0A%0A\n A variet\n",
"json_metadata": "{\"tags\":[\"iota\",\"cryptocurrencies\",\"bitcoin\",\"altcoin\",\"sleeper\"],\"image\":[\"https://steemitimages.com/DQmR9B1T7M6ZsMDpBrymsYaComWVLXwfSxqAVCTDFA1xfhN/internet-of-things-analytics.jpg\",\"https://steemitimages.com/DQmbGcqjeDfXUan5JYtfTuyyiuHJR5iZqsN7J94irZxTkDG/1*s0Da8mqgARZW9QtREjH6ag.png\",\"https://steemitimages.com/DQmdb9QDnZAeihUPUUg9X3uutsJMPZZgU3rR2r5oSiiCb11/1*Pig9XwK3wXrznImQtt8oMA.png\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}shapoypublished a new post: excerpt-from-zcoinofficial-no-rewards2017/09/18 16:21:09
shapoypublished a new post: excerpt-from-zcoinofficial-no-rewards
2017/09/18 16:21:09
| parent author | |
| parent permlink | zcash |
| author | shapoy |
| permlink | excerpt-from-zcoinofficial-no-rewards |
| title | Excerpt from zcoinofficial (Resteem) |
| body | @@ -204,16 +204,147 @@ ks up.%0A%0A +!%5Bmonero-zcash-bitcoin2.jpg%5D(https://steemitimages.com/DQmPB8kAtfqsXoDKFmiPr1X3ReXdbRCSxwzTnJW2cq5rxP4/monero-zcash-bitcoin2.jpg)%0A%0A Blockcha |
| json metadata | {"tags":["zcash","zcoin","monero","dash","pivx"],"image":["https://steemitimages.com/DQmPB8kAtfqsXoDKFmiPr1X3ReXdbRCSxwzTnJW2cq5rxP4/monero-zcash-bitcoin2.jpg","https://steemitimages.com/DQmR4on6itWrZ9MQA8Tixp7Arx2PtWYxYTDDfeUf5aMgEoX/DQmR4on6itWrZ9MQA8Tixp7Arx2PtWYxYTDDfeUf5aMgEoX.png","https://steemitimages.com/DQmZD6uFVKUwFMBNn4ES6pTrXowqABEc8Db5SJD9CNQhXTQ/DQmQwh4mGVxBUo5tDLa9bAVdfKCzJ71c9nNzDFsG4q4SxRi_1680x8400.png","https://steemitimages.com/DQmPp4F2aQvEHxkjnNGhSWd5DDMwUH7osSbyLravx5fgp7C/DQmPp4F2aQvEHxkjnNGhSWd5DDMwUH7osSbyLravx5fgp7C.png","https://steemitimages.com/DQmT8bXNZMELAB2h6BBUyPLPLYyCaB71EEJu4CJ4fJLuF9J/DQmTibdjA6WiaHHDV7UC4ePnAFBovWea8tUa94wEBZLBKum_1680x8400.png","https://steemitimages.com/DQmSzx5YBZicFZWZfS39P946J3M4AA36GW6itFoE5LW3ze4/DQmSzx5YBZicFZWZfS39P946J3M4AA36GW6itFoE5LW3ze4.png","https://steemitimages.com/DQmWk8hgcp8xU9t8URvNWQEswGXvD3yksk7u3Jjmiwxz2Lf/DQmSzRp3XQCXwQ1Y14jTNLcBw1XQ9rZ6oNz1XbnZxHomME3_1680x8400.png"],"links":["https://arxiv.org/pdf/1708.04748.pdf","https://eprint.iacr.org/2017/338"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #15579015/Trx faaf1bf29e2e9d6b54ac62c32b60405a816254b1 |
View Raw JSON Data
{
"trx_id": "faaf1bf29e2e9d6b54ac62c32b60405a816254b1",
"block": 15579015,
"trx_in_block": 9,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-18T16:21:09",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "zcash",
"author": "shapoy",
"permlink": "excerpt-from-zcoinofficial-no-rewards",
"title": "Excerpt from zcoinofficial (Resteem)",
"body": "@@ -204,16 +204,147 @@\n ks up.%0A%0A\n+!%5Bmonero-zcash-bitcoin2.jpg%5D(https://steemitimages.com/DQmPB8kAtfqsXoDKFmiPr1X3ReXdbRCSxwzTnJW2cq5rxP4/monero-zcash-bitcoin2.jpg)%0A%0A\n Blockcha\n",
"json_metadata": "{\"tags\":[\"zcash\",\"zcoin\",\"monero\",\"dash\",\"pivx\"],\"image\":[\"https://steemitimages.com/DQmPB8kAtfqsXoDKFmiPr1X3ReXdbRCSxwzTnJW2cq5rxP4/monero-zcash-bitcoin2.jpg\",\"https://steemitimages.com/DQmR4on6itWrZ9MQA8Tixp7Arx2PtWYxYTDDfeUf5aMgEoX/DQmR4on6itWrZ9MQA8Tixp7Arx2PtWYxYTDDfeUf5aMgEoX.png\",\"https://steemitimages.com/DQmZD6uFVKUwFMBNn4ES6pTrXowqABEc8Db5SJD9CNQhXTQ/DQmQwh4mGVxBUo5tDLa9bAVdfKCzJ71c9nNzDFsG4q4SxRi_1680x8400.png\",\"https://steemitimages.com/DQmPp4F2aQvEHxkjnNGhSWd5DDMwUH7osSbyLravx5fgp7C/DQmPp4F2aQvEHxkjnNGhSWd5DDMwUH7osSbyLravx5fgp7C.png\",\"https://steemitimages.com/DQmT8bXNZMELAB2h6BBUyPLPLYyCaB71EEJu4CJ4fJLuF9J/DQmTibdjA6WiaHHDV7UC4ePnAFBovWea8tUa94wEBZLBKum_1680x8400.png\",\"https://steemitimages.com/DQmSzx5YBZicFZWZfS39P946J3M4AA36GW6itFoE5LW3ze4/DQmSzx5YBZicFZWZfS39P946J3M4AA36GW6itFoE5LW3ze4.png\",\"https://steemitimages.com/DQmWk8hgcp8xU9t8URvNWQEswGXvD3yksk7u3Jjmiwxz2Lf/DQmSzRp3XQCXwQ1Y14jTNLcBw1XQ9rZ6oNz1XbnZxHomME3_1680x8400.png\"],\"links\":[\"https://arxiv.org/pdf/1708.04748.pdf\",\"https://eprint.iacr.org/2017/338\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}shapoyunfollowed @hichamoun2017/09/18 16:16:00
shapoyunfollowed @hichamoun
2017/09/18 16:16:00
| required auths | [] |
| required posting auths | ["shapoy"] |
| id | follow |
| json | ["follow",{"follower":"shapoy","following":"hichamoun","what":[]}] |
| Transaction Info | Block #15578917/Trx fcf26ff5e07f0be6e9cd18039bf32453d65256e2 |
View Raw JSON Data
{
"trx_id": "fcf26ff5e07f0be6e9cd18039bf32453d65256e2",
"block": 15578917,
"trx_in_block": 12,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-18T16:16:00",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"shapoy"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"shapoy\",\"following\":\"hichamoun\",\"what\":[]}]"
}
]
}2017/09/18 16:14:36
2017/09/18 16:14:36
| required auths | [] |
| required posting auths | ["shapoy"] |
| id | follow |
| json | ["follow",{"follower":"shapoy","following":"cheetah","what":["blog"]}] |
| Transaction Info | Block #15578890/Trx 5554c21cca6272be209c0930bc7d9746567f90a6 |
View Raw JSON Data
{
"trx_id": "5554c21cca6272be209c0930bc7d9746567f90a6",
"block": 15578890,
"trx_in_block": 21,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-18T16:14:36",
"op": [
"custom_json",
{
"required_auths": [],
"required_posting_auths": [
"shapoy"
],
"id": "follow",
"json": "[\"follow\",{\"follower\":\"shapoy\",\"following\":\"cheetah\",\"what\":[\"blog\"]}]"
}
]
}fminer05upvoted (100.00%) @shapoy / excerpt-from-zcoinofficial-no-rewards2017/09/18 16:11:48
fminer05upvoted (100.00%) @shapoy / excerpt-from-zcoinofficial-no-rewards
2017/09/18 16:11:48
| voter | fminer05 |
| author | shapoy |
| permlink | excerpt-from-zcoinofficial-no-rewards |
| weight | 10000 (100.00%) |
| Transaction Info | Block #15578837/Trx 5cf46f0dcdca42c66156374501de109f577103d7 |
View Raw JSON Data
{
"trx_id": "5cf46f0dcdca42c66156374501de109f577103d7",
"block": 15578837,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-18T16:11:48",
"op": [
"vote",
{
"voter": "fminer05",
"author": "shapoy",
"permlink": "excerpt-from-zcoinofficial-no-rewards",
"weight": 10000
}
]
}shapoypublished a new post: excerpt-from-zcoinofficial-no-rewards2017/09/18 16:11:09
shapoypublished a new post: excerpt-from-zcoinofficial-no-rewards
2017/09/18 16:11:09
| parent author | |
| parent permlink | zcash |
| author | shapoy |
| permlink | excerpt-from-zcoinofficial-no-rewards |
| title | Excerpt from zcoinofficial (Resteem) |
| body | This post will hopefully give you a brief overview of the major blockchain privacy mechanisms that are implemented in cryptocurrencies today and in particular how the Zerocoin protocol used in Zcoin stacks up. Blockchain privacy is a particularly difficult thing to achieve as a public blockchain is designed so that all transactions are transparent and the supply of coins can be publicly verified. Privacy mechanisms have to ensure that these elements are preserved so it’s a conflicting mix of protecting privacy while maintaining public verifiability. To understand the innovation behind Zerocoin, we need to examine the history of blockchain privacy. ## Cryptocurrency Tumblers and Coinjoin ### As used in: Dash, PIVX ### Pros: #### - Works on top of most cryptocurrencies without the need for specific consensus rules - Relatively simple to implement - Lightweight ### Cons: #### - Basic anonymity - Requires mixers to be online - Earlier implementations involve trust in a third party mixer ### One of the first methods people sought to achieve this was through the use of cryptocurrency tumblers. They work by mixing funds with others by sending your coins to other people and then giving their coins to you. An easy way to visualize this is a group of people each putting the same number of coins into a common pot, mixing it up and then taking the same amount of coins back from which you started with. The idea is that it is now hard to prove whose coin originally belonged to who thus providing some degree of privacy. This comes with several drawbacks, foremost that you need to trust the tumbler not to steal your coins. Coinjoin is an improvement of this mixing idea and removes the possibility for the tumbler to steal the coins, it was popularly used in Darkcoin (now known as Dash). However there are still many drawbacks with Coinjoin.  - You need to trust the tumbler for your anonymity as the mixer can log identifiable information and knows how the mix is happening along with each user’s input address and the address they are receiving coins to. This issue can be avoided by using blind digital signatures but then the anonymity of coinjoin relies strongly on the possibility to connect to the tumbler in an anonymous manner, e.g., via the Tor network. - It requires people involved in the mixing to be online for a mixing transaction to happen. If no one wants to mix for the right denominations, your mix can be delayed. - The anonymity is limited by the amount of people you mix with. A typical round of Dash’s privatesend mixing involves 3 participants only though this can be repeated. - Even with multiple rounds of CoinJoin mixing, recent research (https://arxiv.org/pdf/1708.04748.pdf) shows that a user’s wallet can be identified if they are not careful with browser cookies when making payments because mixing only obscures the transaction links between addresses but does not break them completely. - It is easy to disrupt a run of Coinjoin and delay the completion of the coinjoin transaction for the other participants. Other improvements to CoinJoin such as CoinShuffle++ removed the need for a trusted third party but are still subject to the other drawbacks of CoinJoin namely a limited anonymity set and the requirement that participants are online. The main benefit of Coinjoin type schemes is that they are relatively simple and work on top of the cryptocurrency without the need to use specific consensus rules. With appropriate precautions, CoinJoin can provide a basic degree of anonymity. ## Cryptonote and Ring Signatures ### As used in: Monero ### Pros: #### - No need for a mixer and mixing is done automatically - Can be implemented with privacy on by default - Anonymity increases as time passes as outputs become the new inputs of new mixes - Hides transaction amounts when implemented with RingCT - Well researched cryptography ### Cons: #### - Scalability issues because of large transaction sizes and a non prunable blockchain - Risks of blockchain being deanonymized in the future or through incorrect implementations - Cannot take advantage of existing Bitcoin ecosystem and requires separate integration work - Ring size is practically limited ### The next anonymity scheme we will explore is ring signatures as used in Cryptonote currencies such as Monero which greatly improves anonymity over Coinjoin type schemes. A ring signature works by proving someone signed the transaction from a group of people without revealing which person it was. One common proposed use case of ring signatures is for it to be used to provide an anonymous signature from a “high ranking White House official” without revealing which official signed the message. Cryptonote uses ring signatures in a way whereby a user can craft a transaction and use the outputs of other similar transactions on the blockchain automatically to form the inputs to a ring signature transaction so that it is unclear which input belongs to the person actually doing the transaction. It does this automatically without requiring other users to specify that they wish to mix and does not need to wait for other people to provide funds since it’s just scanning the blockchain for those outputs to use. As there is no mixer, there’s no mixer you need to trust. Monero also recently implemented RingCT (Ring Confidential Transactions) which hides transaction amounts as well.  The main drawback of Cryptonote is that its transactions especially with RingCT are very large occupying several kilobytes and this greatly increases the amount of storage space required to store the blockchain. There currently isn’t any way to prune spend outputs in a Cryptonote blockchain like in Bitcoin. Using an entirely different codebase than Bitcoin also means third parties have to do more work to integrate Cryptonote into their existing ecosystems. Ring signatures as currently implemented in Cryptonote currencies also have limitations in terms of practical ring size (the number of other outputs you are taking) as the size of a transaction grows linearly as the ring size increases. This is why by default Monero has a relatively small default ring size of 4. In fact, using a different ring size then the default might unintentionally deanonymize you by highlighting it. This means on a per transaction basis, the anonymity is limited by the number of participants in the ring. Blockchain analysts although they might not be able to prove transactions are linked, they can calculate the odds that they are. Another criticism of Cryptonote is that if there’s a weakness in its ring signature implementation or a reasonably powerful quantum computer becomes feasible, the entire blockchain history is deanonymized and retroactively exposed. This cannot be fixed after the fact. In fact, a flawed implementation in a Cryptonote currency called Shadowcash allowed for its blockchain to be deanonymized in its entirety. It is also to be noted that with RingCT which hides transaction amounts, this sacrifices supply auditability. Supply auditability means the ability to verify that no new coins are being secretly generated and to know exactly how many coins exist at a point in time. In Monero’s implementation of RingCT, someone who breaks the discrete logarithm that underpins RingCT can forge coins without anyone knowing it, granted it is probably very hard to do so with current knowledge and technology. Despite these drawbacks, Cryptonote today has proven itself to be one of the better and well reviewed privacy technologies out there and the only instances where it has been publicly deanonymized arose from improper implementation such as the Shadowcash fiasco or through the use of mixin-0 transaction in Monero which resulted in a cascade effect that rendered 87% of inputs traceable (https://eprint.iacr.org/2017/338) (which were subsequently mitigated for newer transactions). Cryptonote solves many of the problems of cryptocurrency tumblers and offers good anonymity at the cost of scalability with large transaction sizes and a non prunable blockchain. ## Zerocoin and Zcoin ### As used in: Zcoin ### Pros: #### - No need for a mixer - Very high anonymity in the many thousands (if not more) with a single mint and spend transaction and completely breaks transaction links between addresses. - Retains supply auditability - Uses well researched cryptography ### Cons: #### - Proof sizes are currently large - Requires a trusted setup - Incorrect implementation or leakage of trusted setup parameters can lead to forgery of coins. - Some care is required when doing Zerocoin mints and spends. ### We now come to Zerocoin as implemented in Zcoin. Unlike the previous anonymity schemes which involve obscuring the real transactions with other inputs or transactions, the Zerocoin protocol completely breaks the transaction links between coins through the use of zero knowledge proofs. In simple terms, a zero knowledge proof is a proof you did something or know something without revealing any other information other than you did it. For example, proving that you know a password without actually revealing the password. Zerocoin works by allowing you to burn coins up (otherwise known a Zerocoin mint) and then later redeem an equivalent number of brand new coins (known as a Zerocoin spend). These coins appear with no prior transaction history and are similar to newly mined coins. The zk-proof is used to prove that you indeed burnt coins without revealing the specific coins that you burnt and therefore are entitled to redeem an equivalent number of new clean coins.  This means that unlike in Coinjoin and Cryptonote where the anonymity set is limited by either the number of participants or the ring size, Zerocoin would allow you an anonymity set of every other person who has done a Zerocoin mint of a particular denomination and achieve this immediately. This allows the anonymity set to scale into the many thousands with a single Zerocoin mint and spend cycle. Also the coins truly have their transaction links broken as they appear as completely brand new coins compared to merely being obscured through previous methods. This anonymity scheme is not without some drawbacks. In return for the huge anonymity set and breaking of transaction links, Zerocoin requires a one time trusted setup to generate initial parameters. In Zerocoin these are two very large prime numbers that need to be destroyed. Knowledge of these two large prime numbers would allow someone to forge Zerocoin spends and create coins out of thin air. To mitigate this, Zcoin uses parameters from the RSA Factoring Challenge held in 1991 where they took special steps to destroy the prime numbers and had a USD200,000 bounty to successfully factor it for 16 years before the challenge was ended. Till today the RSA-2048 parameters used remain to the best of our knowledge unfactored and 2048 bit RSA remains widely used today having stood the test of time at least until the advent of quantum computing.  It is worth noting that the knowledge of these two primes or successful factoring will not compromise the anonymity of Zerocoin merely allowing the forging of coins. Additionally this is mitigated that Zcoin’s supply is auditable so the forging of coins can be detected. In fact due to a bug in the implementation (and not from the breaking of RSA), the forging of coins actually happened to Zcoin but was thankfully detected and stopped. It goes to show how in zero knowledge proof coins which involve some form of burning and creation of new coins, supply auditability is particularly important. Another limitation of Zerocoin is that fixed denominations need to be used for minting and spending and the zero knowledge proof sizes for a Zerocoin spend are relatively large at 25 kb, comparable to a RingCT transaction. It is to be noted that unlike in Cryptonote whereby all transactions are to be of this size, only Zerocoin spend transactions occupy this amount of space with normal transactions occupying the same size as Bitcoin transactions. Zerocoin spend transactions are also comparatively computationally intensive to verify taking about half a second to do so. Also incorrect use or predictable use of Zerocoin mint and spend transactions such as always minting and spending at regular intervals or using the same IP address for a mint and spend can possibly compromise anonymity thus some care is required. Summing up, Zerocoin offers very strong anonymity with a huge anonymity set with no transaction linking but currently requires a trusted setup, additional storage on the blockchain and additional computational resources to verify. Despite this, there is research that show that removing trusted setup and reducing proof sizes are possible with Zerocoin through the use of the Sigma protocol and the Zcoin team are currently researching and evaluating its use further. ## Zerocash and Zcash ### As used in: Zcash, Zencash, Komodo ### Pros: #### - Potentially the best anonymity set encompassing all coins minted and breaks transaction links between addresses. - Proof sizes are small and fast to verify - Hides transaction amounts - No need for conversion to a base coin and anonymized coins can be sent directly to each other. ### Cons: #### - Private transactions take a while to generate (almost a minute on a decently powerful computer) - Complicated trusted setup that has to be done by the developers. - Incorrect implementation or leakage of trusted setup parameters can lead to forgery of coins. - Supply cannot be audited therefore forgery can be very difficult to detect. - Uses relatively new cryptography ### The final anonymity scheme we will consider is the Zerocash protocol as used in ZCash. Zerocash builds on the work of Zerocoin and seeks to address the perceived shortcomings of Zerocoin. With Zerocash and its use of zkSNARKs, proof sizes are now only 1 kb and are very fast to verify. Furthermore, all transaction amounts are hidden and there is no longer a need to use fixed denominations when doing a minting transaction. Zerocash also allows people to transfer Zerocash’s equivalent of ‘Zerocoins’ to each other without the need to convert back into the base coin. Its anonymity set is also the largest among all previous anonymity schemes involving all minted coins regardless of denomination on the blockchain. A cursory glance at this would make it seem that Zerocash makes Zerocoin obsolete. However to achieve this, it had to trade off certain benefits that Zerocoin has. First of all Zerocash lacks supply auditability. Like Zerocoin, Zerocash requires a trusted setup but Zerocash’s setup is much more complicated. Zcash utilized a multi party ceremony involving 6 people setup in a way that the only way these parameters could be leaked is if all 6 in the ceremony colluded to retain the keys. In other words you have to trust any of these 6 people that they destroyed the initial parameters and also trust that the ceremony was carried out correctly.  If there is a bug in the code, or a cryptographic flaw or an issue with the multi party trusted setup, an attacker can possibly generate unlimited Zcash and unlike in Zerocoin, this additional supply cannot be detected. Especially in a system that operates on similar principles with Zerocoin that allows the creation of new coins, supply auditability becomes increasingly important. Another trade off is the use of new cryptography called zkSNARKs which are effectively only used in Zerocash. There is a lot less scrutiny on it and therefore is not as battle tested as RSA which has been in use and reviewed for many years and continues to be widely used. The other main drawback of Zerocash is that due to the complex math required, the generation of a private transaction takes significantly longer than any of the previous privacy schemes approaching a minute on a powerful computer and much longer for lesser systems. This makes it less likely for people to use its privacy features and also may exclude less powerful systems such as mobile devices. So although Zerocash offers potentially the highest anonymity, it does this at the cost of supply auditability combined with a complicated trusted setup, the use of new cryptography and a long generation time to create private transactions. ## Summary Every anonymity scheme has its own sets of benefits and trade-offs and we believe that continuous exploration and research of these privacy schemes can only serve to improve blockchain privacy as a whole. We at Zcoin strongly believe that the Zerocoin protocol compares very favorably to other anonymity schemes by providing a very well rounded anonymity package, giving very strong anonymity using proven cryptography while remaining scalable and auditable. We continue to research into ways to further improve Zerocoin.  I hope this article gives you a much better understanding of how various privacy tech works on the blockchain! |
| json metadata | {"tags":["zcash","zcoin","monero","dash","pivx"],"image":["https://steemitimages.com/DQmR4on6itWrZ9MQA8Tixp7Arx2PtWYxYTDDfeUf5aMgEoX/DQmR4on6itWrZ9MQA8Tixp7Arx2PtWYxYTDDfeUf5aMgEoX.png","https://steemitimages.com/DQmZD6uFVKUwFMBNn4ES6pTrXowqABEc8Db5SJD9CNQhXTQ/DQmQwh4mGVxBUo5tDLa9bAVdfKCzJ71c9nNzDFsG4q4SxRi_1680x8400.png","https://steemitimages.com/DQmPp4F2aQvEHxkjnNGhSWd5DDMwUH7osSbyLravx5fgp7C/DQmPp4F2aQvEHxkjnNGhSWd5DDMwUH7osSbyLravx5fgp7C.png","https://steemitimages.com/DQmT8bXNZMELAB2h6BBUyPLPLYyCaB71EEJu4CJ4fJLuF9J/DQmTibdjA6WiaHHDV7UC4ePnAFBovWea8tUa94wEBZLBKum_1680x8400.png","https://steemitimages.com/DQmSzx5YBZicFZWZfS39P946J3M4AA36GW6itFoE5LW3ze4/DQmSzx5YBZicFZWZfS39P946J3M4AA36GW6itFoE5LW3ze4.png","https://steemitimages.com/DQmWk8hgcp8xU9t8URvNWQEswGXvD3yksk7u3Jjmiwxz2Lf/DQmSzRp3XQCXwQ1Y14jTNLcBw1XQ9rZ6oNz1XbnZxHomME3_1680x8400.png"],"links":["https://arxiv.org/pdf/1708.04748.pdf","https://eprint.iacr.org/2017/338"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #15578825/Trx 3c7eed6ab25c5d54ef0cf1b0043f1cf36dbf4198 |
View Raw JSON Data
{
"trx_id": "3c7eed6ab25c5d54ef0cf1b0043f1cf36dbf4198",
"block": 15578825,
"trx_in_block": 25,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-18T16:11:09",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "zcash",
"author": "shapoy",
"permlink": "excerpt-from-zcoinofficial-no-rewards",
"title": "Excerpt from zcoinofficial (Resteem)",
"body": "This post will hopefully give you a brief overview of the major blockchain privacy mechanisms that are implemented in cryptocurrencies today and in particular how the Zerocoin protocol used in Zcoin stacks up.\n\nBlockchain privacy is a particularly difficult thing to achieve as a public blockchain is designed so that all transactions are transparent and the supply of coins can be publicly verified. Privacy mechanisms have to ensure that these elements are preserved so it’s a conflicting mix of protecting privacy while maintaining public verifiability. To understand the innovation behind Zerocoin, we need to examine the history of blockchain privacy.\n\n## Cryptocurrency Tumblers and Coinjoin\n### As used in: Dash, PIVX\n\n### Pros:\n#### \n- Works on top of most cryptocurrencies without the need for specific consensus rules\n- Relatively simple to implement\n- Lightweight\n\n### Cons:\n#### \n- Basic anonymity\n- Requires mixers to be online\n- Earlier implementations involve trust in a third party mixer\n### \nOne of the first methods people sought to achieve this was through the use of cryptocurrency tumblers. They work by mixing funds with others by sending your coins to other people and then giving their coins to you. An easy way to visualize this is a group of people each putting the same number of coins into a common pot, mixing it up and then taking the same amount of coins back from which you started with. The idea is that it is now hard to prove whose coin originally belonged to who thus providing some degree of privacy. This comes with several drawbacks, foremost that you need to trust the tumbler not to steal your coins.\n\nCoinjoin is an improvement of this mixing idea and removes the possibility for the tumbler to steal the coins, it was popularly used in Darkcoin (now known as Dash). However there are still many drawbacks with Coinjoin.\n\n\n\n- You need to trust the tumbler for your anonymity as the mixer can log identifiable information and knows how the mix is happening along with each user’s input address and the address they are receiving coins to. This issue can be avoided by using blind digital signatures but then the anonymity of coinjoin relies strongly on the possibility to connect to the tumbler in an anonymous manner, e.g., via the Tor network.\n- It requires people involved in the mixing to be online for a mixing transaction to happen. If no one wants to mix for the right denominations, your mix can be delayed.\n- The anonymity is limited by the amount of people you mix with. A typical round of Dash’s privatesend mixing involves 3 participants only though this can be repeated.\n- Even with multiple rounds of CoinJoin mixing, recent research (https://arxiv.org/pdf/1708.04748.pdf) shows that a user’s wallet can be identified if they are not careful with browser cookies when making payments because mixing only obscures the transaction links between addresses but does not break them completely.\n- It is easy to disrupt a run of Coinjoin and delay the completion of the coinjoin transaction for the other participants.\nOther improvements to CoinJoin such as CoinShuffle++ removed the need for a trusted third party but are still subject to the other drawbacks of CoinJoin namely a limited anonymity set and the requirement that participants are online.\n\nThe main benefit of Coinjoin type schemes is that they are relatively simple and work on top of the cryptocurrency without the need to use specific consensus rules. With appropriate precautions, CoinJoin can provide a basic degree of anonymity.\n\n## Cryptonote and Ring Signatures\n### As used in: Monero\n\n### Pros:\n#### \n- No need for a mixer and mixing is done automatically\n- Can be implemented with privacy on by default\n- Anonymity increases as time passes as outputs become the new inputs of new mixes\n- Hides transaction amounts when implemented with RingCT\n- Well researched cryptography\n\n### Cons:\n#### \n- Scalability issues because of large transaction sizes and a non prunable blockchain\n- Risks of blockchain being deanonymized in the future or through incorrect implementations\n- Cannot take advantage of existing Bitcoin ecosystem and requires separate integration work\n- Ring size is practically limited\n### \nThe next anonymity scheme we will explore is ring signatures as used in Cryptonote currencies such as Monero which greatly improves anonymity over Coinjoin type schemes. A ring signature works by proving someone signed the transaction from a group of people without revealing which person it was. One common proposed use case of ring signatures is for it to be used to provide an anonymous signature from a “high ranking White House official” without revealing which official signed the message.\n\nCryptonote uses ring signatures in a way whereby a user can craft a transaction and use the outputs of other similar transactions on the blockchain automatically to form the inputs to a ring signature transaction so that it is unclear which input belongs to the person actually doing the transaction. It does this automatically without requiring other users to specify that they wish to mix and does not need to wait for other people to provide funds since it’s just scanning the blockchain for those outputs to use. As there is no mixer, there’s no mixer you need to trust. Monero also recently implemented RingCT (Ring Confidential Transactions) which hides transaction amounts as well.\n\n\n\nThe main drawback of Cryptonote is that its transactions especially with RingCT are very large occupying several kilobytes and this greatly increases the amount of storage space required to store the blockchain. There currently isn’t any way to prune spend outputs in a Cryptonote blockchain like in Bitcoin. Using an entirely different codebase than Bitcoin also means third parties have to do more work to integrate Cryptonote into their existing ecosystems.\n\nRing signatures as currently implemented in Cryptonote currencies also have limitations in terms of practical ring size (the number of other outputs you are taking) as the size of a transaction grows linearly as the ring size increases. This is why by default Monero has a relatively small default ring size of 4. In fact, using a different ring size then the default might unintentionally deanonymize you by highlighting it. This means on a per transaction basis, the anonymity is limited by the number of participants in the ring. Blockchain analysts although they might not be able to prove transactions are linked, they can calculate the odds that they are.\n\nAnother criticism of Cryptonote is that if there’s a weakness in its ring signature implementation or a reasonably powerful quantum computer becomes feasible, the entire blockchain history is deanonymized and retroactively exposed. This cannot be fixed after the fact. In fact, a flawed implementation in a Cryptonote currency called Shadowcash allowed for its blockchain to be deanonymized in its entirety.\n\nIt is also to be noted that with RingCT which hides transaction amounts, this sacrifices supply auditability. Supply auditability means the ability to verify that no new coins are being secretly generated and to know exactly how many coins exist at a point in time. In Monero’s implementation of RingCT, someone who breaks the discrete logarithm that underpins RingCT can forge coins without anyone knowing it, granted it is probably very hard to do so with current knowledge and technology.\n\nDespite these drawbacks, Cryptonote today has proven itself to be one of the better and well reviewed privacy technologies out there and the only instances where it has been publicly deanonymized arose from improper implementation such as the Shadowcash fiasco or through the use of mixin-0 transaction in Monero which resulted in a cascade effect that rendered 87% of inputs traceable (https://eprint.iacr.org/2017/338) (which were subsequently mitigated for newer transactions). Cryptonote solves many of the problems of cryptocurrency tumblers and offers good anonymity at the cost of scalability with large transaction sizes and a non prunable blockchain.\n\n## Zerocoin and Zcoin\n### As used in: Zcoin\n\n### Pros:\n#### \n- No need for a mixer\n- Very high anonymity in the many thousands (if not more) with a single mint and spend transaction and completely breaks transaction links between addresses.\n- Retains supply auditability\n- Uses well researched cryptography\n### Cons:\n#### \n- Proof sizes are currently large\n- Requires a trusted setup\n- Incorrect implementation or leakage of trusted setup parameters can lead to forgery of coins.\n- Some care is required when doing Zerocoin mints and spends.\n### \nWe now come to Zerocoin as implemented in Zcoin. Unlike the previous anonymity schemes which involve obscuring the real transactions with other inputs or transactions, the Zerocoin protocol completely breaks the transaction links between coins through the use of zero knowledge proofs.\n\nIn simple terms, a zero knowledge proof is a proof you did something or know something without revealing any other information other than you did it. For example, proving that you know a password without actually revealing the password.\n\nZerocoin works by allowing you to burn coins up (otherwise known a Zerocoin mint) and then later redeem an equivalent number of brand new coins (known as a Zerocoin spend). These coins appear with no prior transaction history and are similar to newly mined coins. The zk-proof is used to prove that you indeed burnt coins without revealing the specific coins that you burnt and therefore are entitled to redeem an equivalent number of new clean coins.\n\n\n\nThis means that unlike in Coinjoin and Cryptonote where the anonymity set is limited by either the number of participants or the ring size, Zerocoin would allow you an anonymity set of every other person who has done a Zerocoin mint of a particular denomination and achieve this immediately. This allows the anonymity set to scale into the many thousands with a single Zerocoin mint and spend cycle. Also the coins truly have their transaction links broken as they appear as completely brand new coins compared to merely being obscured through previous methods.\n\nThis anonymity scheme is not without some drawbacks. In return for the huge anonymity set and breaking of transaction links, Zerocoin requires a one time trusted setup to generate initial parameters. In Zerocoin these are two very large prime numbers that need to be destroyed. Knowledge of these two large prime numbers would allow someone to forge Zerocoin spends and create coins out of thin air. To mitigate this, Zcoin uses parameters from the RSA Factoring Challenge held in 1991 where they took special steps to destroy the prime numbers and had a USD200,000 bounty to successfully factor it for 16 years before the challenge was ended. Till today the RSA-2048 parameters used remain to the best of our knowledge unfactored and 2048 bit RSA remains widely used today having stood the test of time at least until the advent of quantum computing.\n\n\n\nIt is worth noting that the knowledge of these two primes or successful factoring will not compromise the anonymity of Zerocoin merely allowing the forging of coins. Additionally this is mitigated that Zcoin’s supply is auditable so the forging of coins can be detected. In fact due to a bug in the implementation (and not from the breaking of RSA), the forging of coins actually happened to Zcoin but was thankfully detected and stopped. It goes to show how in zero knowledge proof coins which involve some form of burning and creation of new coins, supply auditability is particularly important.\n\nAnother limitation of Zerocoin is that fixed denominations need to be used for minting and spending and the zero knowledge proof sizes for a Zerocoin spend are relatively large at 25 kb, comparable to a RingCT transaction. It is to be noted that unlike in Cryptonote whereby all transactions are to be of this size, only Zerocoin spend transactions occupy this amount of space with normal transactions occupying the same size as Bitcoin transactions. Zerocoin spend transactions are also comparatively computationally intensive to verify taking about half a second to do so.\n\nAlso incorrect use or predictable use of Zerocoin mint and spend transactions such as always minting and spending at regular intervals or using the same IP address for a mint and spend can possibly compromise anonymity thus some care is required.\n\nSumming up, Zerocoin offers very strong anonymity with a huge anonymity set with no transaction linking but currently requires a trusted setup, additional storage on the blockchain and additional computational resources to verify. Despite this, there is research that show that removing trusted setup and reducing proof sizes are possible with Zerocoin through the use of the Sigma protocol and the Zcoin team are currently researching and evaluating its use further.\n\n## Zerocash and Zcash\n### As used in: Zcash, Zencash, Komodo\n\n### Pros:\n#### \n- Potentially the best anonymity set encompassing all coins minted and breaks transaction links between addresses.\n- Proof sizes are small and fast to verify\n- Hides transaction amounts\n- No need for conversion to a base coin and anonymized coins can be sent directly to each other.\n### Cons:\n#### \n- Private transactions take a while to generate (almost a minute on a decently powerful computer)\n- Complicated trusted setup that has to be done by the developers.\n- Incorrect implementation or leakage of trusted setup parameters can lead to forgery of coins.\n- Supply cannot be audited therefore forgery can be very difficult to detect.\n- Uses relatively new cryptography\n### \nThe final anonymity scheme we will consider is the Zerocash protocol as used in ZCash. Zerocash builds on the work of Zerocoin and seeks to address the perceived shortcomings of Zerocoin. With Zerocash and its use of zkSNARKs, proof sizes are now only 1 kb and are very fast to verify. Furthermore, all transaction amounts are hidden and there is no longer a need to use fixed denominations when doing a minting transaction. Zerocash also allows people to transfer Zerocash’s equivalent of ‘Zerocoins’ to each other without the need to convert back into the base coin. Its anonymity set is also the largest among all previous anonymity schemes involving all minted coins regardless of denomination on the blockchain.\n\nA cursory glance at this would make it seem that Zerocash makes Zerocoin obsolete. However to achieve this, it had to trade off certain benefits that Zerocoin has.\n\nFirst of all Zerocash lacks supply auditability. Like Zerocoin, Zerocash requires a trusted setup but Zerocash’s setup is much more complicated. Zcash utilized a multi party ceremony involving 6 people setup in a way that the only way these parameters could be leaked is if all 6 in the ceremony colluded to retain the keys. In other words you have to trust any of these 6 people that they destroyed the initial parameters and also trust that the ceremony was carried out correctly.\n\n\n\nIf there is a bug in the code, or a cryptographic flaw or an issue with the multi party trusted setup, an attacker can possibly generate unlimited Zcash and unlike in Zerocoin, this additional supply cannot be detected. Especially in a system that operates on similar principles with Zerocoin that allows the creation of new coins, supply auditability becomes increasingly important.\n\nAnother trade off is the use of new cryptography called zkSNARKs which are effectively only used in Zerocash. There is a lot less scrutiny on it and therefore is not as battle tested as RSA which has been in use and reviewed for many years and continues to be widely used.\n\nThe other main drawback of Zerocash is that due to the complex math required, the generation of a private transaction takes significantly longer than any of the previous privacy schemes approaching a minute on a powerful computer and much longer for lesser systems. This makes it less likely for people to use its privacy features and also may exclude less powerful systems such as mobile devices.\n\nSo although Zerocash offers potentially the highest anonymity, it does this at the cost of supply auditability combined with a complicated trusted setup, the use of new cryptography and a long generation time to create private transactions.\n\n## Summary\nEvery anonymity scheme has its own sets of benefits and trade-offs and we believe that continuous exploration and research of these privacy schemes can only serve to improve blockchain privacy as a whole. We at Zcoin strongly believe that the Zerocoin protocol compares very favorably to other anonymity schemes by providing a very well rounded anonymity package, giving very strong anonymity using proven cryptography while remaining scalable and auditable. We continue to research into ways to further improve Zerocoin.\n\n\n\nI hope this article gives you a much better understanding of how various privacy tech works on the blockchain!",
"json_metadata": "{\"tags\":[\"zcash\",\"zcoin\",\"monero\",\"dash\",\"pivx\"],\"image\":[\"https://steemitimages.com/DQmR4on6itWrZ9MQA8Tixp7Arx2PtWYxYTDDfeUf5aMgEoX/DQmR4on6itWrZ9MQA8Tixp7Arx2PtWYxYTDDfeUf5aMgEoX.png\",\"https://steemitimages.com/DQmZD6uFVKUwFMBNn4ES6pTrXowqABEc8Db5SJD9CNQhXTQ/DQmQwh4mGVxBUo5tDLa9bAVdfKCzJ71c9nNzDFsG4q4SxRi_1680x8400.png\",\"https://steemitimages.com/DQmPp4F2aQvEHxkjnNGhSWd5DDMwUH7osSbyLravx5fgp7C/DQmPp4F2aQvEHxkjnNGhSWd5DDMwUH7osSbyLravx5fgp7C.png\",\"https://steemitimages.com/DQmT8bXNZMELAB2h6BBUyPLPLYyCaB71EEJu4CJ4fJLuF9J/DQmTibdjA6WiaHHDV7UC4ePnAFBovWea8tUa94wEBZLBKum_1680x8400.png\",\"https://steemitimages.com/DQmSzx5YBZicFZWZfS39P946J3M4AA36GW6itFoE5LW3ze4/DQmSzx5YBZicFZWZfS39P946J3M4AA36GW6itFoE5LW3ze4.png\",\"https://steemitimages.com/DQmWk8hgcp8xU9t8URvNWQEswGXvD3yksk7u3Jjmiwxz2Lf/DQmSzRp3XQCXwQ1Y14jTNLcBw1XQ9rZ6oNz1XbnZxHomME3_1680x8400.png\"],\"links\":[\"https://arxiv.org/pdf/1708.04748.pdf\",\"https://eprint.iacr.org/2017/338\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}2017/09/18 16:11:03
2017/09/18 16:11:03
| parent author | shapoy |
| parent permlink | excerpt-from-zcoinofficial-no-rewards |
| author | cheetah |
| permlink | cheetah-re-shapoyexcerpt-from-zcoinofficial-no-rewards |
| title | |
| body | Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in: https://zcoin.io/zcoins-privacy-technology-compares-competition/ |
| json metadata | |
| Transaction Info | Block #15578823/Trx 4213328aa4707819ef5225d0aac2d688f1e53f10 |
View Raw JSON Data
{
"trx_id": "4213328aa4707819ef5225d0aac2d688f1e53f10",
"block": 15578823,
"trx_in_block": 26,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-18T16:11:03",
"op": [
"comment",
{
"parent_author": "shapoy",
"parent_permlink": "excerpt-from-zcoinofficial-no-rewards",
"author": "cheetah",
"permlink": "cheetah-re-shapoyexcerpt-from-zcoinofficial-no-rewards",
"title": "",
"body": "Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in:\nhttps://zcoin.io/zcoins-privacy-technology-compares-competition/",
"json_metadata": ""
}
]
}cheetahupvoted (0.50%) @shapoy / excerpt-from-zcoinofficial-no-rewards2017/09/18 16:11:00
cheetahupvoted (0.50%) @shapoy / excerpt-from-zcoinofficial-no-rewards
2017/09/18 16:11:00
| voter | cheetah |
| author | shapoy |
| permlink | excerpt-from-zcoinofficial-no-rewards |
| weight | 50 (0.50%) |
| Transaction Info | Block #15578822/Trx 2a0061279088e90efc2613add04d09a07d734363 |
View Raw JSON Data
{
"trx_id": "2a0061279088e90efc2613add04d09a07d734363",
"block": 15578822,
"trx_in_block": 0,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-18T16:11:00",
"op": [
"vote",
{
"voter": "cheetah",
"author": "shapoy",
"permlink": "excerpt-from-zcoinofficial-no-rewards",
"weight": 50
}
]
}shapoyupdated options for excerpt-from-zcoinofficial-no-rewards2017/09/18 16:10:27
shapoyupdated options for excerpt-from-zcoinofficial-no-rewards
2017/09/18 16:10:27
| author | shapoy |
| permlink | excerpt-from-zcoinofficial-no-rewards |
| max accepted payout | 0.000 SBD |
| percent steem dollars | 10000 |
| allow votes | true |
| allow curation rewards | true |
| extensions | [] |
| Transaction Info | Block #15578811/Trx a894e70013f239d93b25cd8e418d78446d2e7fa6 |
View Raw JSON Data
{
"trx_id": "a894e70013f239d93b25cd8e418d78446d2e7fa6",
"block": 15578811,
"trx_in_block": 14,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-18T16:10:27",
"op": [
"comment_options",
{
"author": "shapoy",
"permlink": "excerpt-from-zcoinofficial-no-rewards",
"max_accepted_payout": "0.000 SBD",
"percent_steem_dollars": 10000,
"allow_votes": true,
"allow_curation_rewards": true,
"extensions": []
}
]
}shapoypublished a new post: excerpt-from-zcoinofficial-no-rewards2017/09/18 16:10:27
shapoypublished a new post: excerpt-from-zcoinofficial-no-rewards
2017/09/18 16:10:27
| parent author | |
| parent permlink | zcash |
| author | shapoy |
| permlink | excerpt-from-zcoinofficial-no-rewards |
| title | Excerpt from zcoinofficial (no rewards) |
| body | This post will hopefully give you a brief overview of the major blockchain privacy mechanisms that are implemented in cryptocurrencies today and in particular how the Zerocoin protocol used in Zcoin stacks up. Blockchain privacy is a particularly difficult thing to achieve as a public blockchain is designed so that all transactions are transparent and the supply of coins can be publicly verified. Privacy mechanisms have to ensure that these elements are preserved so it’s a conflicting mix of protecting privacy while maintaining public verifiability. To understand the innovation behind Zerocoin, we need to examine the history of blockchain privacy. ## Cryptocurrency Tumblers and Coinjoin ### As used in: Dash, PIVX ### Pros: #### - Works on top of most cryptocurrencies without the need for specific consensus rules - Relatively simple to implement - Lightweight ### Cons: #### - Basic anonymity - Requires mixers to be online - Earlier implementations involve trust in a third party mixer ### One of the first methods people sought to achieve this was through the use of cryptocurrency tumblers. They work by mixing funds with others by sending your coins to other people and then giving their coins to you. An easy way to visualize this is a group of people each putting the same number of coins into a common pot, mixing it up and then taking the same amount of coins back from which you started with. The idea is that it is now hard to prove whose coin originally belonged to who thus providing some degree of privacy. This comes with several drawbacks, foremost that you need to trust the tumbler not to steal your coins. Coinjoin is an improvement of this mixing idea and removes the possibility for the tumbler to steal the coins, it was popularly used in Darkcoin (now known as Dash). However there are still many drawbacks with Coinjoin.  - You need to trust the tumbler for your anonymity as the mixer can log identifiable information and knows how the mix is happening along with each user’s input address and the address they are receiving coins to. This issue can be avoided by using blind digital signatures but then the anonymity of coinjoin relies strongly on the possibility to connect to the tumbler in an anonymous manner, e.g., via the Tor network. - It requires people involved in the mixing to be online for a mixing transaction to happen. If no one wants to mix for the right denominations, your mix can be delayed. - The anonymity is limited by the amount of people you mix with. A typical round of Dash’s privatesend mixing involves 3 participants only though this can be repeated. - Even with multiple rounds of CoinJoin mixing, recent research (https://arxiv.org/pdf/1708.04748.pdf) shows that a user’s wallet can be identified if they are not careful with browser cookies when making payments because mixing only obscures the transaction links between addresses but does not break them completely. - It is easy to disrupt a run of Coinjoin and delay the completion of the coinjoin transaction for the other participants. Other improvements to CoinJoin such as CoinShuffle++ removed the need for a trusted third party but are still subject to the other drawbacks of CoinJoin namely a limited anonymity set and the requirement that participants are online. The main benefit of Coinjoin type schemes is that they are relatively simple and work on top of the cryptocurrency without the need to use specific consensus rules. With appropriate precautions, CoinJoin can provide a basic degree of anonymity. ## Cryptonote and Ring Signatures ### As used in: Monero ### Pros: #### - No need for a mixer and mixing is done automatically - Can be implemented with privacy on by default - Anonymity increases as time passes as outputs become the new inputs of new mixes - Hides transaction amounts when implemented with RingCT - Well researched cryptography ### Cons: #### - Scalability issues because of large transaction sizes and a non prunable blockchain - Risks of blockchain being deanonymized in the future or through incorrect implementations - Cannot take advantage of existing Bitcoin ecosystem and requires separate integration work - Ring size is practically limited ### The next anonymity scheme we will explore is ring signatures as used in Cryptonote currencies such as Monero which greatly improves anonymity over Coinjoin type schemes. A ring signature works by proving someone signed the transaction from a group of people without revealing which person it was. One common proposed use case of ring signatures is for it to be used to provide an anonymous signature from a “high ranking White House official” without revealing which official signed the message. Cryptonote uses ring signatures in a way whereby a user can craft a transaction and use the outputs of other similar transactions on the blockchain automatically to form the inputs to a ring signature transaction so that it is unclear which input belongs to the person actually doing the transaction. It does this automatically without requiring other users to specify that they wish to mix and does not need to wait for other people to provide funds since it’s just scanning the blockchain for those outputs to use. As there is no mixer, there’s no mixer you need to trust. Monero also recently implemented RingCT (Ring Confidential Transactions) which hides transaction amounts as well.  The main drawback of Cryptonote is that its transactions especially with RingCT are very large occupying several kilobytes and this greatly increases the amount of storage space required to store the blockchain. There currently isn’t any way to prune spend outputs in a Cryptonote blockchain like in Bitcoin. Using an entirely different codebase than Bitcoin also means third parties have to do more work to integrate Cryptonote into their existing ecosystems. Ring signatures as currently implemented in Cryptonote currencies also have limitations in terms of practical ring size (the number of other outputs you are taking) as the size of a transaction grows linearly as the ring size increases. This is why by default Monero has a relatively small default ring size of 4. In fact, using a different ring size then the default might unintentionally deanonymize you by highlighting it. This means on a per transaction basis, the anonymity is limited by the number of participants in the ring. Blockchain analysts although they might not be able to prove transactions are linked, they can calculate the odds that they are. Another criticism of Cryptonote is that if there’s a weakness in its ring signature implementation or a reasonably powerful quantum computer becomes feasible, the entire blockchain history is deanonymized and retroactively exposed. This cannot be fixed after the fact. In fact, a flawed implementation in a Cryptonote currency called Shadowcash allowed for its blockchain to be deanonymized in its entirety. It is also to be noted that with RingCT which hides transaction amounts, this sacrifices supply auditability. Supply auditability means the ability to verify that no new coins are being secretly generated and to know exactly how many coins exist at a point in time. In Monero’s implementation of RingCT, someone who breaks the discrete logarithm that underpins RingCT can forge coins without anyone knowing it, granted it is probably very hard to do so with current knowledge and technology. Despite these drawbacks, Cryptonote today has proven itself to be one of the better and well reviewed privacy technologies out there and the only instances where it has been publicly deanonymized arose from improper implementation such as the Shadowcash fiasco or through the use of mixin-0 transaction in Monero which resulted in a cascade effect that rendered 87% of inputs traceable (https://eprint.iacr.org/2017/338) (which were subsequently mitigated for newer transactions). Cryptonote solves many of the problems of cryptocurrency tumblers and offers good anonymity at the cost of scalability with large transaction sizes and a non prunable blockchain. ## Zerocoin and Zcoin ### As used in: Zcoin ### Pros: #### - No need for a mixer - Very high anonymity in the many thousands (if not more) with a single mint and spend transaction and completely breaks transaction links between addresses. - Retains supply auditability - Uses well researched cryptography ### Cons: #### - Proof sizes are currently large - Requires a trusted setup - Incorrect implementation or leakage of trusted setup parameters can lead to forgery of coins. - Some care is required when doing Zerocoin mints and spends. ### We now come to Zerocoin as implemented in Zcoin. Unlike the previous anonymity schemes which involve obscuring the real transactions with other inputs or transactions, the Zerocoin protocol completely breaks the transaction links between coins through the use of zero knowledge proofs. In simple terms, a zero knowledge proof is a proof you did something or know something without revealing any other information other than you did it. For example, proving that you know a password without actually revealing the password. Zerocoin works by allowing you to burn coins up (otherwise known a Zerocoin mint) and then later redeem an equivalent number of brand new coins (known as a Zerocoin spend). These coins appear with no prior transaction history and are similar to newly mined coins. The zk-proof is used to prove that you indeed burnt coins without revealing the specific coins that you burnt and therefore are entitled to redeem an equivalent number of new clean coins.  This means that unlike in Coinjoin and Cryptonote where the anonymity set is limited by either the number of participants or the ring size, Zerocoin would allow you an anonymity set of every other person who has done a Zerocoin mint of a particular denomination and achieve this immediately. This allows the anonymity set to scale into the many thousands with a single Zerocoin mint and spend cycle. Also the coins truly have their transaction links broken as they appear as completely brand new coins compared to merely being obscured through previous methods. This anonymity scheme is not without some drawbacks. In return for the huge anonymity set and breaking of transaction links, Zerocoin requires a one time trusted setup to generate initial parameters. In Zerocoin these are two very large prime numbers that need to be destroyed. Knowledge of these two large prime numbers would allow someone to forge Zerocoin spends and create coins out of thin air. To mitigate this, Zcoin uses parameters from the RSA Factoring Challenge held in 1991 where they took special steps to destroy the prime numbers and had a USD200,000 bounty to successfully factor it for 16 years before the challenge was ended. Till today the RSA-2048 parameters used remain to the best of our knowledge unfactored and 2048 bit RSA remains widely used today having stood the test of time at least until the advent of quantum computing.  It is worth noting that the knowledge of these two primes or successful factoring will not compromise the anonymity of Zerocoin merely allowing the forging of coins. Additionally this is mitigated that Zcoin’s supply is auditable so the forging of coins can be detected. In fact due to a bug in the implementation (and not from the breaking of RSA), the forging of coins actually happened to Zcoin but was thankfully detected and stopped. It goes to show how in zero knowledge proof coins which involve some form of burning and creation of new coins, supply auditability is particularly important. Another limitation of Zerocoin is that fixed denominations need to be used for minting and spending and the zero knowledge proof sizes for a Zerocoin spend are relatively large at 25 kb, comparable to a RingCT transaction. It is to be noted that unlike in Cryptonote whereby all transactions are to be of this size, only Zerocoin spend transactions occupy this amount of space with normal transactions occupying the same size as Bitcoin transactions. Zerocoin spend transactions are also comparatively computationally intensive to verify taking about half a second to do so. Also incorrect use or predictable use of Zerocoin mint and spend transactions such as always minting and spending at regular intervals or using the same IP address for a mint and spend can possibly compromise anonymity thus some care is required. Summing up, Zerocoin offers very strong anonymity with a huge anonymity set with no transaction linking but currently requires a trusted setup, additional storage on the blockchain and additional computational resources to verify. Despite this, there is research that show that removing trusted setup and reducing proof sizes are possible with Zerocoin through the use of the Sigma protocol and the Zcoin team are currently researching and evaluating its use further. ## Zerocash and Zcash ### As used in: Zcash, Zencash, Komodo ### Pros: #### - Potentially the best anonymity set encompassing all coins minted and breaks transaction links between addresses. - Proof sizes are small and fast to verify - Hides transaction amounts - No need for conversion to a base coin and anonymized coins can be sent directly to each other. ### Cons: #### - Private transactions take a while to generate (almost a minute on a decently powerful computer) - Complicated trusted setup that has to be done by the developers. - Incorrect implementation or leakage of trusted setup parameters can lead to forgery of coins. - Supply cannot be audited therefore forgery can be very difficult to detect. - Uses relatively new cryptography ### The final anonymity scheme we will consider is the Zerocash protocol as used in ZCash. Zerocash builds on the work of Zerocoin and seeks to address the perceived shortcomings of Zerocoin. With Zerocash and its use of zkSNARKs, proof sizes are now only 1 kb and are very fast to verify. Furthermore, all transaction amounts are hidden and there is no longer a need to use fixed denominations when doing a minting transaction. Zerocash also allows people to transfer Zerocash’s equivalent of ‘Zerocoins’ to each other without the need to convert back into the base coin. Its anonymity set is also the largest among all previous anonymity schemes involving all minted coins regardless of denomination on the blockchain. A cursory glance at this would make it seem that Zerocash makes Zerocoin obsolete. However to achieve this, it had to trade off certain benefits that Zerocoin has. First of all Zerocash lacks supply auditability. Like Zerocoin, Zerocash requires a trusted setup but Zerocash’s setup is much more complicated. Zcash utilized a multi party ceremony involving 6 people setup in a way that the only way these parameters could be leaked is if all 6 in the ceremony colluded to retain the keys. In other words you have to trust any of these 6 people that they destroyed the initial parameters and also trust that the ceremony was carried out correctly.  If there is a bug in the code, or a cryptographic flaw or an issue with the multi party trusted setup, an attacker can possibly generate unlimited Zcash and unlike in Zerocoin, this additional supply cannot be detected. Especially in a system that operates on similar principles with Zerocoin that allows the creation of new coins, supply auditability becomes increasingly important. Another trade off is the use of new cryptography called zkSNARKs which are effectively only used in Zerocash. There is a lot less scrutiny on it and therefore is not as battle tested as RSA which has been in use and reviewed for many years and continues to be widely used. The other main drawback of Zerocash is that due to the complex math required, the generation of a private transaction takes significantly longer than any of the previous privacy schemes approaching a minute on a powerful computer and much longer for lesser systems. This makes it less likely for people to use its privacy features and also may exclude less powerful systems such as mobile devices. So although Zerocash offers potentially the highest anonymity, it does this at the cost of supply auditability combined with a complicated trusted setup, the use of new cryptography and a long generation time to create private transactions. ## Summary Every anonymity scheme has its own sets of benefits and trade-offs and we believe that continuous exploration and research of these privacy schemes can only serve to improve blockchain privacy as a whole. We at Zcoin strongly believe that the Zerocoin protocol compares very favorably to other anonymity schemes by providing a very well rounded anonymity package, giving very strong anonymity using proven cryptography while remaining scalable and auditable. We continue to research into ways to further improve Zerocoin.  I hope this article gives you a much better understanding of how various privacy tech works on the blockchain! |
| json metadata | {"tags":["zcash","zcoin","monero","dash","pivx"],"image":["https://steemitimages.com/DQmR4on6itWrZ9MQA8Tixp7Arx2PtWYxYTDDfeUf5aMgEoX/DQmR4on6itWrZ9MQA8Tixp7Arx2PtWYxYTDDfeUf5aMgEoX.png","https://steemitimages.com/DQmZD6uFVKUwFMBNn4ES6pTrXowqABEc8Db5SJD9CNQhXTQ/DQmQwh4mGVxBUo5tDLa9bAVdfKCzJ71c9nNzDFsG4q4SxRi_1680x8400.png","https://steemitimages.com/DQmPp4F2aQvEHxkjnNGhSWd5DDMwUH7osSbyLravx5fgp7C/DQmPp4F2aQvEHxkjnNGhSWd5DDMwUH7osSbyLravx5fgp7C.png","https://steemitimages.com/DQmT8bXNZMELAB2h6BBUyPLPLYyCaB71EEJu4CJ4fJLuF9J/DQmTibdjA6WiaHHDV7UC4ePnAFBovWea8tUa94wEBZLBKum_1680x8400.png","https://steemitimages.com/DQmSzx5YBZicFZWZfS39P946J3M4AA36GW6itFoE5LW3ze4/DQmSzx5YBZicFZWZfS39P946J3M4AA36GW6itFoE5LW3ze4.png","https://steemitimages.com/DQmWk8hgcp8xU9t8URvNWQEswGXvD3yksk7u3Jjmiwxz2Lf/DQmSzRp3XQCXwQ1Y14jTNLcBw1XQ9rZ6oNz1XbnZxHomME3_1680x8400.png"],"links":["https://arxiv.org/pdf/1708.04748.pdf","https://eprint.iacr.org/2017/338"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #15578811/Trx a894e70013f239d93b25cd8e418d78446d2e7fa6 |
View Raw JSON Data
{
"trx_id": "a894e70013f239d93b25cd8e418d78446d2e7fa6",
"block": 15578811,
"trx_in_block": 14,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-18T16:10:27",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "zcash",
"author": "shapoy",
"permlink": "excerpt-from-zcoinofficial-no-rewards",
"title": "Excerpt from zcoinofficial (no rewards)",
"body": "This post will hopefully give you a brief overview of the major blockchain privacy mechanisms that are implemented in cryptocurrencies today and in particular how the Zerocoin protocol used in Zcoin stacks up.\n\nBlockchain privacy is a particularly difficult thing to achieve as a public blockchain is designed so that all transactions are transparent and the supply of coins can be publicly verified. Privacy mechanisms have to ensure that these elements are preserved so it’s a conflicting mix of protecting privacy while maintaining public verifiability. To understand the innovation behind Zerocoin, we need to examine the history of blockchain privacy.\n\n## Cryptocurrency Tumblers and Coinjoin\n### As used in: Dash, PIVX\n\n### Pros:\n#### \n- Works on top of most cryptocurrencies without the need for specific consensus rules\n- Relatively simple to implement\n- Lightweight\n\n### Cons:\n#### \n- Basic anonymity\n- Requires mixers to be online\n- Earlier implementations involve trust in a third party mixer\n### \nOne of the first methods people sought to achieve this was through the use of cryptocurrency tumblers. They work by mixing funds with others by sending your coins to other people and then giving their coins to you. An easy way to visualize this is a group of people each putting the same number of coins into a common pot, mixing it up and then taking the same amount of coins back from which you started with. The idea is that it is now hard to prove whose coin originally belonged to who thus providing some degree of privacy. This comes with several drawbacks, foremost that you need to trust the tumbler not to steal your coins.\n\nCoinjoin is an improvement of this mixing idea and removes the possibility for the tumbler to steal the coins, it was popularly used in Darkcoin (now known as Dash). However there are still many drawbacks with Coinjoin.\n\n\n\n- You need to trust the tumbler for your anonymity as the mixer can log identifiable information and knows how the mix is happening along with each user’s input address and the address they are receiving coins to. This issue can be avoided by using blind digital signatures but then the anonymity of coinjoin relies strongly on the possibility to connect to the tumbler in an anonymous manner, e.g., via the Tor network.\n- It requires people involved in the mixing to be online for a mixing transaction to happen. If no one wants to mix for the right denominations, your mix can be delayed.\n- The anonymity is limited by the amount of people you mix with. A typical round of Dash’s privatesend mixing involves 3 participants only though this can be repeated.\n- Even with multiple rounds of CoinJoin mixing, recent research (https://arxiv.org/pdf/1708.04748.pdf) shows that a user’s wallet can be identified if they are not careful with browser cookies when making payments because mixing only obscures the transaction links between addresses but does not break them completely.\n- It is easy to disrupt a run of Coinjoin and delay the completion of the coinjoin transaction for the other participants.\nOther improvements to CoinJoin such as CoinShuffle++ removed the need for a trusted third party but are still subject to the other drawbacks of CoinJoin namely a limited anonymity set and the requirement that participants are online.\n\nThe main benefit of Coinjoin type schemes is that they are relatively simple and work on top of the cryptocurrency without the need to use specific consensus rules. With appropriate precautions, CoinJoin can provide a basic degree of anonymity.\n\n## Cryptonote and Ring Signatures\n### As used in: Monero\n\n### Pros:\n#### \n- No need for a mixer and mixing is done automatically\n- Can be implemented with privacy on by default\n- Anonymity increases as time passes as outputs become the new inputs of new mixes\n- Hides transaction amounts when implemented with RingCT\n- Well researched cryptography\n\n### Cons:\n#### \n- Scalability issues because of large transaction sizes and a non prunable blockchain\n- Risks of blockchain being deanonymized in the future or through incorrect implementations\n- Cannot take advantage of existing Bitcoin ecosystem and requires separate integration work\n- Ring size is practically limited\n### \nThe next anonymity scheme we will explore is ring signatures as used in Cryptonote currencies such as Monero which greatly improves anonymity over Coinjoin type schemes. A ring signature works by proving someone signed the transaction from a group of people without revealing which person it was. One common proposed use case of ring signatures is for it to be used to provide an anonymous signature from a “high ranking White House official” without revealing which official signed the message.\n\nCryptonote uses ring signatures in a way whereby a user can craft a transaction and use the outputs of other similar transactions on the blockchain automatically to form the inputs to a ring signature transaction so that it is unclear which input belongs to the person actually doing the transaction. It does this automatically without requiring other users to specify that they wish to mix and does not need to wait for other people to provide funds since it’s just scanning the blockchain for those outputs to use. As there is no mixer, there’s no mixer you need to trust. Monero also recently implemented RingCT (Ring Confidential Transactions) which hides transaction amounts as well.\n\n\n\nThe main drawback of Cryptonote is that its transactions especially with RingCT are very large occupying several kilobytes and this greatly increases the amount of storage space required to store the blockchain. There currently isn’t any way to prune spend outputs in a Cryptonote blockchain like in Bitcoin. Using an entirely different codebase than Bitcoin also means third parties have to do more work to integrate Cryptonote into their existing ecosystems.\n\nRing signatures as currently implemented in Cryptonote currencies also have limitations in terms of practical ring size (the number of other outputs you are taking) as the size of a transaction grows linearly as the ring size increases. This is why by default Monero has a relatively small default ring size of 4. In fact, using a different ring size then the default might unintentionally deanonymize you by highlighting it. This means on a per transaction basis, the anonymity is limited by the number of participants in the ring. Blockchain analysts although they might not be able to prove transactions are linked, they can calculate the odds that they are.\n\nAnother criticism of Cryptonote is that if there’s a weakness in its ring signature implementation or a reasonably powerful quantum computer becomes feasible, the entire blockchain history is deanonymized and retroactively exposed. This cannot be fixed after the fact. In fact, a flawed implementation in a Cryptonote currency called Shadowcash allowed for its blockchain to be deanonymized in its entirety.\n\nIt is also to be noted that with RingCT which hides transaction amounts, this sacrifices supply auditability. Supply auditability means the ability to verify that no new coins are being secretly generated and to know exactly how many coins exist at a point in time. In Monero’s implementation of RingCT, someone who breaks the discrete logarithm that underpins RingCT can forge coins without anyone knowing it, granted it is probably very hard to do so with current knowledge and technology.\n\nDespite these drawbacks, Cryptonote today has proven itself to be one of the better and well reviewed privacy technologies out there and the only instances where it has been publicly deanonymized arose from improper implementation such as the Shadowcash fiasco or through the use of mixin-0 transaction in Monero which resulted in a cascade effect that rendered 87% of inputs traceable (https://eprint.iacr.org/2017/338) (which were subsequently mitigated for newer transactions). Cryptonote solves many of the problems of cryptocurrency tumblers and offers good anonymity at the cost of scalability with large transaction sizes and a non prunable blockchain.\n\n## Zerocoin and Zcoin\n### As used in: Zcoin\n\n### Pros:\n#### \n- No need for a mixer\n- Very high anonymity in the many thousands (if not more) with a single mint and spend transaction and completely breaks transaction links between addresses.\n- Retains supply auditability\n- Uses well researched cryptography\n### Cons:\n#### \n- Proof sizes are currently large\n- Requires a trusted setup\n- Incorrect implementation or leakage of trusted setup parameters can lead to forgery of coins.\n- Some care is required when doing Zerocoin mints and spends.\n### \nWe now come to Zerocoin as implemented in Zcoin. Unlike the previous anonymity schemes which involve obscuring the real transactions with other inputs or transactions, the Zerocoin protocol completely breaks the transaction links between coins through the use of zero knowledge proofs.\n\nIn simple terms, a zero knowledge proof is a proof you did something or know something without revealing any other information other than you did it. For example, proving that you know a password without actually revealing the password.\n\nZerocoin works by allowing you to burn coins up (otherwise known a Zerocoin mint) and then later redeem an equivalent number of brand new coins (known as a Zerocoin spend). These coins appear with no prior transaction history and are similar to newly mined coins. The zk-proof is used to prove that you indeed burnt coins without revealing the specific coins that you burnt and therefore are entitled to redeem an equivalent number of new clean coins.\n\n\n\nThis means that unlike in Coinjoin and Cryptonote where the anonymity set is limited by either the number of participants or the ring size, Zerocoin would allow you an anonymity set of every other person who has done a Zerocoin mint of a particular denomination and achieve this immediately. This allows the anonymity set to scale into the many thousands with a single Zerocoin mint and spend cycle. Also the coins truly have their transaction links broken as they appear as completely brand new coins compared to merely being obscured through previous methods.\n\nThis anonymity scheme is not without some drawbacks. In return for the huge anonymity set and breaking of transaction links, Zerocoin requires a one time trusted setup to generate initial parameters. In Zerocoin these are two very large prime numbers that need to be destroyed. Knowledge of these two large prime numbers would allow someone to forge Zerocoin spends and create coins out of thin air. To mitigate this, Zcoin uses parameters from the RSA Factoring Challenge held in 1991 where they took special steps to destroy the prime numbers and had a USD200,000 bounty to successfully factor it for 16 years before the challenge was ended. Till today the RSA-2048 parameters used remain to the best of our knowledge unfactored and 2048 bit RSA remains widely used today having stood the test of time at least until the advent of quantum computing.\n\n\n\nIt is worth noting that the knowledge of these two primes or successful factoring will not compromise the anonymity of Zerocoin merely allowing the forging of coins. Additionally this is mitigated that Zcoin’s supply is auditable so the forging of coins can be detected. In fact due to a bug in the implementation (and not from the breaking of RSA), the forging of coins actually happened to Zcoin but was thankfully detected and stopped. It goes to show how in zero knowledge proof coins which involve some form of burning and creation of new coins, supply auditability is particularly important.\n\nAnother limitation of Zerocoin is that fixed denominations need to be used for minting and spending and the zero knowledge proof sizes for a Zerocoin spend are relatively large at 25 kb, comparable to a RingCT transaction. It is to be noted that unlike in Cryptonote whereby all transactions are to be of this size, only Zerocoin spend transactions occupy this amount of space with normal transactions occupying the same size as Bitcoin transactions. Zerocoin spend transactions are also comparatively computationally intensive to verify taking about half a second to do so.\n\nAlso incorrect use or predictable use of Zerocoin mint and spend transactions such as always minting and spending at regular intervals or using the same IP address for a mint and spend can possibly compromise anonymity thus some care is required.\n\nSumming up, Zerocoin offers very strong anonymity with a huge anonymity set with no transaction linking but currently requires a trusted setup, additional storage on the blockchain and additional computational resources to verify. Despite this, there is research that show that removing trusted setup and reducing proof sizes are possible with Zerocoin through the use of the Sigma protocol and the Zcoin team are currently researching and evaluating its use further.\n\n## Zerocash and Zcash\n### As used in: Zcash, Zencash, Komodo\n\n### Pros:\n#### \n- Potentially the best anonymity set encompassing all coins minted and breaks transaction links between addresses.\n- Proof sizes are small and fast to verify\n- Hides transaction amounts\n- No need for conversion to a base coin and anonymized coins can be sent directly to each other.\n### Cons:\n#### \n- Private transactions take a while to generate (almost a minute on a decently powerful computer)\n- Complicated trusted setup that has to be done by the developers.\n- Incorrect implementation or leakage of trusted setup parameters can lead to forgery of coins.\n- Supply cannot be audited therefore forgery can be very difficult to detect.\n- Uses relatively new cryptography\n### \nThe final anonymity scheme we will consider is the Zerocash protocol as used in ZCash. Zerocash builds on the work of Zerocoin and seeks to address the perceived shortcomings of Zerocoin. With Zerocash and its use of zkSNARKs, proof sizes are now only 1 kb and are very fast to verify. Furthermore, all transaction amounts are hidden and there is no longer a need to use fixed denominations when doing a minting transaction. Zerocash also allows people to transfer Zerocash’s equivalent of ‘Zerocoins’ to each other without the need to convert back into the base coin. Its anonymity set is also the largest among all previous anonymity schemes involving all minted coins regardless of denomination on the blockchain.\n\nA cursory glance at this would make it seem that Zerocash makes Zerocoin obsolete. However to achieve this, it had to trade off certain benefits that Zerocoin has.\n\nFirst of all Zerocash lacks supply auditability. Like Zerocoin, Zerocash requires a trusted setup but Zerocash’s setup is much more complicated. Zcash utilized a multi party ceremony involving 6 people setup in a way that the only way these parameters could be leaked is if all 6 in the ceremony colluded to retain the keys. In other words you have to trust any of these 6 people that they destroyed the initial parameters and also trust that the ceremony was carried out correctly.\n\n\n\nIf there is a bug in the code, or a cryptographic flaw or an issue with the multi party trusted setup, an attacker can possibly generate unlimited Zcash and unlike in Zerocoin, this additional supply cannot be detected. Especially in a system that operates on similar principles with Zerocoin that allows the creation of new coins, supply auditability becomes increasingly important.\n\nAnother trade off is the use of new cryptography called zkSNARKs which are effectively only used in Zerocash. There is a lot less scrutiny on it and therefore is not as battle tested as RSA which has been in use and reviewed for many years and continues to be widely used.\n\nThe other main drawback of Zerocash is that due to the complex math required, the generation of a private transaction takes significantly longer than any of the previous privacy schemes approaching a minute on a powerful computer and much longer for lesser systems. This makes it less likely for people to use its privacy features and also may exclude less powerful systems such as mobile devices.\n\nSo although Zerocash offers potentially the highest anonymity, it does this at the cost of supply auditability combined with a complicated trusted setup, the use of new cryptography and a long generation time to create private transactions.\n\n## Summary\nEvery anonymity scheme has its own sets of benefits and trade-offs and we believe that continuous exploration and research of these privacy schemes can only serve to improve blockchain privacy as a whole. We at Zcoin strongly believe that the Zerocoin protocol compares very favorably to other anonymity schemes by providing a very well rounded anonymity package, giving very strong anonymity using proven cryptography while remaining scalable and auditable. We continue to research into ways to further improve Zerocoin.\n\n\n\nI hope this article gives you a much better understanding of how various privacy tech works on the blockchain!",
"json_metadata": "{\"tags\":[\"zcash\",\"zcoin\",\"monero\",\"dash\",\"pivx\"],\"image\":[\"https://steemitimages.com/DQmR4on6itWrZ9MQA8Tixp7Arx2PtWYxYTDDfeUf5aMgEoX/DQmR4on6itWrZ9MQA8Tixp7Arx2PtWYxYTDDfeUf5aMgEoX.png\",\"https://steemitimages.com/DQmZD6uFVKUwFMBNn4ES6pTrXowqABEc8Db5SJD9CNQhXTQ/DQmQwh4mGVxBUo5tDLa9bAVdfKCzJ71c9nNzDFsG4q4SxRi_1680x8400.png\",\"https://steemitimages.com/DQmPp4F2aQvEHxkjnNGhSWd5DDMwUH7osSbyLravx5fgp7C/DQmPp4F2aQvEHxkjnNGhSWd5DDMwUH7osSbyLravx5fgp7C.png\",\"https://steemitimages.com/DQmT8bXNZMELAB2h6BBUyPLPLYyCaB71EEJu4CJ4fJLuF9J/DQmTibdjA6WiaHHDV7UC4ePnAFBovWea8tUa94wEBZLBKum_1680x8400.png\",\"https://steemitimages.com/DQmSzx5YBZicFZWZfS39P946J3M4AA36GW6itFoE5LW3ze4/DQmSzx5YBZicFZWZfS39P946J3M4AA36GW6itFoE5LW3ze4.png\",\"https://steemitimages.com/DQmWk8hgcp8xU9t8URvNWQEswGXvD3yksk7u3Jjmiwxz2Lf/DQmSzRp3XQCXwQ1Y14jTNLcBw1XQ9rZ6oNz1XbnZxHomME3_1680x8400.png\"],\"links\":[\"https://arxiv.org/pdf/1708.04748.pdf\",\"https://eprint.iacr.org/2017/338\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}cheetahreplied to @shapoy / cheetah-re-shapoyiota-dag-tangle2017/09/18 15:58:12
cheetahreplied to @shapoy / cheetah-re-shapoyiota-dag-tangle
2017/09/18 15:58:12
| parent author | shapoy |
| parent permlink | iota-dag-tangle |
| author | cheetah |
| permlink | cheetah-re-shapoyiota-dag-tangle |
| title | |
| body | Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in: https://medium.com/@cstoecker/implementing-first-industry-4-0-use-cases-with-iota-dag-tangle-machine-tagging-for-digital-twins-baf1943c499d |
| json metadata | |
| Transaction Info | Block #15578571/Trx 805f27f33c87d4648bad5fe32696dab1aff0de6a |
View Raw JSON Data
{
"trx_id": "805f27f33c87d4648bad5fe32696dab1aff0de6a",
"block": 15578571,
"trx_in_block": 26,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-18T15:58:12",
"op": [
"comment",
{
"parent_author": "shapoy",
"parent_permlink": "iota-dag-tangle",
"author": "cheetah",
"permlink": "cheetah-re-shapoyiota-dag-tangle",
"title": "",
"body": "Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in:\nhttps://medium.com/@cstoecker/implementing-first-industry-4-0-use-cases-with-iota-dag-tangle-machine-tagging-for-digital-twins-baf1943c499d",
"json_metadata": ""
}
]
}cheetahupvoted (0.50%) @shapoy / iota-dag-tangle2017/09/18 15:58:09
cheetahupvoted (0.50%) @shapoy / iota-dag-tangle
2017/09/18 15:58:09
| voter | cheetah |
| author | shapoy |
| permlink | iota-dag-tangle |
| weight | 50 (0.50%) |
| Transaction Info | Block #15578570/Trx e88188fa624c29587dfe70d96778040ca4df73c3 |
View Raw JSON Data
{
"trx_id": "e88188fa624c29587dfe70d96778040ca4df73c3",
"block": 15578570,
"trx_in_block": 7,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-18T15:58:09",
"op": [
"vote",
{
"voter": "cheetah",
"author": "shapoy",
"permlink": "iota-dag-tangle",
"weight": 50
}
]
}shapoypublished a new post: iota-dag-tangle2017/09/18 15:57:30
shapoypublished a new post: iota-dag-tangle
2017/09/18 15:57:30
| parent author | |
| parent permlink | iota |
| author | shapoy |
| permlink | iota-dag-tangle |
| title | IOTA DAG Tangle |
| body | Implementing first Industry 4.0 Use Cases with IOTA DAG Tangle — Machine Tagging for Digital Twins Industry 4.0 is powered by the fusion of technologies that are connecting the dots between the physical, digital and biological spheres. A variety of disruptive industry 4.0 technologies are now at their tipping point of being widely adopted in the next years. These technologies include — among others — electric cars, intelligent autonomous machines, decentral energy infrastructure, 3D printers, blockchain and AI/ML. The combination of machines with blockchain and especially the IOTA protocol transforms these machines into economically independent devices that can transact among each other and form the basis of a Machine Economy in the 4th Industrial Revolution. In this blogpost my preferred industry 4.0 use case will be described as a first example where the IOTA protocol can be applied in practice today: IOTA for tagging of physical machines in a digital twin architecture (proof-of-concept). This use case combines some very important decentral technologies such as IPFS, IPLD and BigchainDB for file storage and database layer with the DAG (directed acyclic graph) tangle as well. We decided with this use case to start using IOTA in our project as it is practicable to implement and clearly demonstrates selected very compelling features of the DAG tangle. I will describe how we are exploring IOTA in a second industry 4.0 blogpost about Share & Charge EV car charging (conceptual). ### Digital Twin: Every Product has its own Story One of our main Industry 4.0 innovation projects is the digital twin (or digital product memory). A digital twin is a digital representation of a physical, biological or digital object. Our innogy Digital Twin project “Twin of Things” seeks to give every physical object a story. innogy is now forming an open IoT and supply chain ecosystem to bring this vision into reality.  Connecting the digital, physical and biological spheres with the digital twin concept A digital twin can be created with manufacturing, production and design parameters even before a physical object is even existing telling a manufacturing unit how a physical object needs to be produced. It can store data how the object was assembled, tested, transported, deployed, operated or decommissioned. The digital twin is a key concept for bringing industry 4.0 to life supporting a broad variety of industry domains including Energy, Mobility, Supply Chain, Consumer Goods or Health Care. It provides many technical benefits for different use cases and solves many of today’s problems while fulfilling industry requirements such as batch size 1 manufacturing, back-to-birth-traceability, provenance, authenticity, tracking, optimization, auditing and compliance.  High-level Digital Twin Value Proposition In addition a digital twin enables further innovation by establishing a digital experience among objects and their owners and or by opening up new forms of marketing. Marketing can move from person focused marketing to object marketing. A manufacturer or retail organization selling a handbag for example is trying to get hold of the personal data of a customer at the point of sales. A user is typically offered a loyalty programme to provide the data in return. The manufacturer or the retail store have all what they need to exploit these personal data for their own purposes. Digital Twins in Marketing A physical object with a digital twin will change old fashioned loyality programme marketing dramatically. A manufacturer or retail store do not need the personal data any more. They only need to know the object identity which enables a marketing function to send marketing and sales messages directly into the digital twin. A customer with its registered objects in an App will get an alert whenever a message from a marketing functions arrives in one of its digital twins. And of course a customer can decide to disable the alert or take write access away for the third parties. The object marketing is a very powerful new marketing tool for the customer shifting the balance from corporate marketing functions to customers. In addition, object owner can connect anonymously among each other to share their product experience by sending messages among each digital twins. And of course a customer can disable this community feature as well. In addition a digital twin can store, manipulate and transfer tokens. This includes access tokens, token of value, loyalty tokens or proof of something tokens (e.g. product age smaller 5 years, compliance token, authenticity token). There are a lot more unexplored innovative features within this technology. Technical Implementation As objects are interacting with other entities over their life cycle, ease of interaction with the digital twin and control over object data are key features that can be fulfilled with decentral, blockchain-like solutions. The other key feature is the cryptographically secure tagging of objects. To implement a decentral digital twin solution the respective object data need to be stored in a decentral database, connected with analytics and gathered from a physical object or machine. This leads to the following high-level technical requirements: Ad 1. Data Storage Interoperability along the life cycle Immutability of the data for compliance, trust and auditing GDPR compliant data access management and transfer of assets empowering the object owner’s control over the data and the object Data indexing and queries for analytics We are using BigchainDB as decentral database for storing data in an immutable way and to enable analytics on top of a database. We use BigchainDB Access tokens to for access management giving full control about the data to the owner of the object. A variety of Automakers are starting to explore the potential of a blockchainified database layer. Ad 2. Data Gathering Tagging of objects to provide a cryptographically secure identity Data authenticity of data gathered from an object linked to its IOTA identity Data integrity of data gathered from an object ensuring that a third party has not tampered with the data in the communication layer Data encryption We are testing IOTA for tagging machines and providing a secure and trusted data transaction layer for extracting data out of the machines into the digital twin. IOTA on the Device We start using IOTA to tag physical machines giving machines an identity on the DAG tangle. These identities are then stored in the DAG tangle and in a device registry which, is in our case, on BigchainDB. Digital Twin Architecture In addition to the IOTA device identity further metadata or attributes are stored in the registry describing the device and making it searchable in the indexed database. The IOTA integration with IoT devices provides integrity and authenticity of data gathered from sensors or sent to actuators of a device. To address vulnerabilities inside a machine — e.g. via message injection through a malicious third party — the sensors or actuators receive their own cryptographic identity using methods such as crypto chips or IOTA light nodes on sensor / actuator level. The identities of sensors / actuators are registered in the DAG tangle. All these devices communicate inside a machine with an IOTA gateway note that acts as or it is integrated with a telematics gateway connecting sensors and actuators with systems in the outside world, especially our digital twin platform. A more complex machine can have its own IOTA DAG tangle sub-branch or even clusters of sub-branches validating transactions and dataflow inside the machine. CarPass: Vehicle Telematics Data in a Digital Twin A practicable first application of a digital twin with IOTA is CarPass for vehicles telematics data. The CarPass solution securely captures telematics data (e.g. mileage, trips, environmental, maintenance data) and stores them immutable in the digital twin for private passenger, fleet or commercial vehicles. Working CarPass Implementation This special digital twin enables a vehicle to tell its story where it went, what it did and how it was treated. The car´s history along its lifecycle is captured in the digital twin. This provides many benefits for fleet managers, work shops, processes involving multiple parties, logistics companies or cold chain operators. As the most simple and straightforward benefit this solution provides an auditable and tamper-proof mileage history, preventing odometer fraud in the second hand car market. How was the car driven? Few trips long distance or many trips short distance? How was it maintained? The answer to these questions pretty much determines the value of the car. CarPass can answer these questions in a trusted way. innogy is now piloting IOTA for ensuring this trust in telematics data coming out of a vehicle. We are connecting the IOTA node with a telematics device. A further step might be to integrate IOTA in a telematics device itself. Further integration with sensors and actuators in a vehicle will be evaluated in order to extend the trust into the vhicle infrastructure down to the sensor level. This end-to-end architecture is especially important to eliminate vulnerabilities for tampering via e.g. malicious message injection inside a car. IOTA is a young technology with a not yet fully proven cryptographic foundation, but with a promising potential that deserves adoption for initial use case testing and prototyping. Of course there are real world and cyber security risks in adopting such a technology. We are aware of the risks and the development roadmap of missing features going forward. We believe that building prototypes is a reasonable way to better understand the technology and its underlying risks. In partnership with other enterprises and key teams including the IOTA foundation, innogy gets new ideas to live, in order to demonstrate through concrete examples the capabilities and potentials of blockchain technologies as it relates to physical assets, objects, machines and devices. |
| json metadata | {"tags":["iota","cryptocurrencies","bitcoin","altcoin","sleeper"],"image":["https://steemitimages.com/DQmbGcqjeDfXUan5JYtfTuyyiuHJR5iZqsN7J94irZxTkDG/1*s0Da8mqgARZW9QtREjH6ag.png","https://steemitimages.com/DQmdb9QDnZAeihUPUUg9X3uutsJMPZZgU3rR2r5oSiiCb11/1*Pig9XwK3wXrznImQtt8oMA.png"],"app":"steemit/0.1","format":"markdown"} |
| Transaction Info | Block #15578557/Trx 9f291d09f150833186dfb2878b275a028a92f2c1 |
View Raw JSON Data
{
"trx_id": "9f291d09f150833186dfb2878b275a028a92f2c1",
"block": 15578557,
"trx_in_block": 23,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-18T15:57:30",
"op": [
"comment",
{
"parent_author": "",
"parent_permlink": "iota",
"author": "shapoy",
"permlink": "iota-dag-tangle",
"title": "IOTA DAG Tangle",
"body": "Implementing first Industry 4.0 Use Cases with IOTA DAG Tangle — Machine Tagging for Digital Twins Industry 4.0 is powered by the fusion of technologies that are connecting the dots between the physical, digital and biological spheres.\n\nA variety of disruptive industry 4.0 technologies are now at their tipping point of being widely adopted in the next years. These technologies include — among others — electric cars, intelligent autonomous machines, decentral energy infrastructure, 3D printers, blockchain and AI/ML.\n\nThe combination of machines with blockchain and especially the IOTA protocol transforms these machines into economically independent devices that can transact among each other and form the basis of a Machine Economy in the 4th Industrial Revolution.\n\nIn this blogpost my preferred industry 4.0 use case will be described as a first example where the IOTA protocol can be applied in practice today: IOTA for tagging of physical machines in a digital twin architecture (proof-of-concept). This use case combines some very important decentral technologies such as IPFS, IPLD and BigchainDB for file storage and database layer with the DAG (directed acyclic graph) tangle as well.\n\nWe decided with this use case to start using IOTA in our project as it is practicable to implement and clearly demonstrates selected very compelling features of the DAG tangle.\n\nI will describe how we are exploring IOTA in a second industry 4.0 blogpost about Share & Charge EV car charging (conceptual).\n\n### Digital Twin: Every Product has its own Story\n\nOne of our main Industry 4.0 innovation projects is the digital twin (or digital product memory). A digital twin is a digital representation of a physical, biological or digital object. Our innogy Digital Twin project “Twin of Things” seeks to give every physical object a story. innogy is now forming an open IoT and supply chain ecosystem to bring this vision into reality.\n\n\n\nConnecting the digital, physical and biological spheres with the digital twin concept\nA digital twin can be created with manufacturing, production and design parameters even before a physical object is even existing telling a manufacturing unit how a physical object needs to be produced. It can store data how the object was assembled, tested, transported, deployed, operated or decommissioned.\n\nThe digital twin is a key concept for bringing industry 4.0 to life supporting a broad variety of industry domains including Energy, Mobility, Supply Chain, Consumer Goods or Health Care. It provides many technical benefits for different use cases and solves many of today’s problems while fulfilling industry requirements such as batch size 1 manufacturing, back-to-birth-traceability, provenance, authenticity, tracking, optimization, auditing and compliance.\n\n\n\nHigh-level Digital Twin Value Proposition\nIn addition a digital twin enables further innovation by establishing a digital experience among objects and their owners and or by opening up new forms of marketing.\n\nMarketing can move from person focused marketing to object marketing. A manufacturer or retail organization selling a handbag for example is trying to get hold of the personal data of a customer at the point of sales. A user is typically offered a loyalty programme to provide the data in return. The manufacturer or the retail store have all what they need to exploit these personal data for their own purposes.\n\nDigital Twins in Marketing\nA physical object with a digital twin will change old fashioned loyality programme marketing dramatically. A manufacturer or retail store do not need the personal data any more. They only need to know the object identity which enables a marketing function to send marketing and sales messages directly into the digital twin. A customer with its registered objects in an App will get an alert whenever a message from a marketing functions arrives in one of its digital twins. And of course a customer can decide to disable the alert or take write access away for the third parties.\n\nThe object marketing is a very powerful new marketing tool for the customer shifting the balance from corporate marketing functions to customers. In addition, object owner can connect anonymously among each other to share their product experience by sending messages among each digital twins. And of course a customer can disable this community feature as well.\nIn addition a digital twin can store, manipulate and transfer tokens. This includes access tokens, token of value, loyalty tokens or proof of something tokens (e.g. product age smaller 5 years, compliance token, authenticity token).\nThere are a lot more unexplored innovative features within this technology.\n\nTechnical Implementation\nAs objects are interacting with other entities over their life cycle, ease of interaction with the digital twin and control over object data are key features that can be fulfilled with decentral, blockchain-like solutions. The other key feature is the cryptographically secure tagging of objects.\n\nTo implement a decentral digital twin solution the respective object data need to be stored in a decentral database, connected with analytics and gathered from a physical object or machine.\n\nThis leads to the following high-level technical requirements:\n\nAd 1. Data Storage\nInteroperability along the life cycle\nImmutability of the data for compliance, trust and auditing\nGDPR compliant data access management and transfer of assets empowering the object owner’s control over the data and the object\nData indexing and queries for analytics\nWe are using BigchainDB as decentral database for storing data in an immutable way and to enable analytics on top of a database. We use BigchainDB Access tokens to for access management giving full control about the data to the owner of the object. A variety of Automakers are starting to explore the potential of a blockchainified database layer.\n\nAd 2. Data Gathering\nTagging of objects to provide a cryptographically secure identity\nData authenticity of data gathered from an object linked to its IOTA identity\nData integrity of data gathered from an object ensuring that a third party has not tampered with the data in the communication layer\nData encryption\nWe are testing IOTA for tagging machines and providing a secure and trusted data transaction layer for extracting data out of the machines into the digital twin.\n\nIOTA on the Device\nWe start using IOTA to tag physical machines giving machines an identity on the DAG tangle. These identities are then stored in the DAG tangle and in a device registry which, is in our case, on BigchainDB.\n\nDigital Twin Architecture\nIn addition to the IOTA device identity further metadata or attributes are stored in the registry describing the device and making it searchable in the indexed database.\nThe IOTA integration with IoT devices provides integrity and authenticity of data gathered from sensors or sent to actuators of a device.\n\nTo address vulnerabilities inside a machine — e.g. via message injection through a malicious third party — the sensors or actuators receive their own cryptographic identity using methods such as crypto chips or IOTA light nodes on sensor / actuator level. The identities of sensors / actuators are registered in the DAG tangle.\n\nAll these devices communicate inside a machine with an IOTA gateway note that acts as or it is integrated with a telematics gateway connecting sensors and actuators with systems in the outside world, especially our digital twin platform. A more complex machine can have its own IOTA DAG tangle sub-branch or even clusters of sub-branches validating transactions and dataflow inside the machine.\n\nCarPass: Vehicle Telematics Data in a Digital Twin\nA practicable first application of a digital twin with IOTA is CarPass for vehicles telematics data. The CarPass solution securely captures telematics data (e.g. mileage, trips, environmental, maintenance data) and stores them immutable in the digital twin for private passenger, fleet or commercial vehicles.\n\nWorking CarPass Implementation\nThis special digital twin enables a vehicle to tell its story where it went, what it did and how it was treated. The car´s history along its lifecycle is captured in the digital twin. This provides many benefits for fleet managers, work shops, processes involving multiple parties, logistics companies or cold chain operators.\nAs the most simple and straightforward benefit this solution provides an auditable and tamper-proof mileage history, preventing odometer fraud in the second hand car market.\n\nHow was the car driven? Few trips long distance or many trips short distance? How was it maintained? The answer to these questions pretty much determines the value of the car. CarPass can answer these questions in a trusted way.\n\ninnogy is now piloting IOTA for ensuring this trust in telematics data coming out of a vehicle. We are connecting the IOTA node with a telematics device. A further step might be to integrate IOTA in a telematics device itself. Further integration with sensors and actuators in a vehicle will be evaluated in order to extend the trust into the vhicle infrastructure down to the sensor level.\nThis end-to-end architecture is especially important to eliminate vulnerabilities for tampering via e.g. malicious message injection inside a car.\n\nIOTA is a young technology with a not yet fully proven cryptographic foundation, but with a promising potential that deserves adoption for initial use case testing and prototyping.\n\nOf course there are real world and cyber security risks in adopting such a technology. We are aware of the risks and the development roadmap of missing features going forward. We believe that building prototypes is a reasonable way to better understand the technology and its underlying risks.\n\nIn partnership with other enterprises and key teams including the IOTA foundation, innogy gets new ideas to live, in order to demonstrate through concrete examples the capabilities and potentials of blockchain technologies as it relates to physical assets, objects, machines and devices.",
"json_metadata": "{\"tags\":[\"iota\",\"cryptocurrencies\",\"bitcoin\",\"altcoin\",\"sleeper\"],\"image\":[\"https://steemitimages.com/DQmbGcqjeDfXUan5JYtfTuyyiuHJR5iZqsN7J94irZxTkDG/1*s0Da8mqgARZW9QtREjH6ag.png\",\"https://steemitimages.com/DQmdb9QDnZAeihUPUUg9X3uutsJMPZZgU3rR2r5oSiiCb11/1*Pig9XwK3wXrznImQtt8oMA.png\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
}
]
}2017/09/18 15:26:00
2017/09/18 15:26:00
| voter | shapoy |
| author | zcoinofficial |
| permlink | an-overview-of-blockchain-privacy-mechanisms-and-how-zerocoin-in-zcoin-usdxzc-not-zcash-stacks-up |
| weight | 10000 (100.00%) |
| Transaction Info | Block #15577927/Trx 03076bae8f99208a046ecd152749333e83f998a4 |
View Raw JSON Data
{
"trx_id": "03076bae8f99208a046ecd152749333e83f998a4",
"block": 15577927,
"trx_in_block": 12,
"op_in_trx": 0,
"virtual_op": 0,
"timestamp": "2017-09-18T15:26:00",
"op": [
"vote",
{
"voter": "shapoy",
"author": "zcoinofficial",
"permlink": "an-overview-of-blockchain-privacy-mechanisms-and-how-zerocoin-in-zcoin-usdxzc-not-zcash-stacks-up",
"weight": 10000
}
]
}Manabar
Voting Power100.00%
Downvote Power100.00%
Resource Credits100.00%
Reputation Progress31.34%
{
"voting_manabar": {
"current_mana": "8143659806",
"last_update_time": 1779085464
},
"downvote_manabar": {
"current_mana": 2035914951,
"last_update_time": 1779085464
},
"rc_account": {
"account": "shapoy",
"rc_manabar": {
"current_mana": "10164408779",
"last_update_time": 1779085464
},
"max_rc_creation_adjustment": {
"amount": "2020748973",
"precision": 6,
"nai": "@@000000037"
},
"max_rc": "10164408779"
}
}Account Metadata
| POSTING JSON METADATA | |
| profile | {"profile_image":"http://media.zenfs.com/en-US/video/video.pd2upload.com/video.yahoofinance.com@8dfea102-b1a8-362e-9e14-5554f85eab4c_FULL.jpg","cover_image":"https://www.bitcoinnews.ch/wp-content/uploads/2013/11/bitcoin.jpg"} |
| JSON METADATA | |
| profile | {"profile_image":"http://media.zenfs.com/en-US/video/video.pd2upload.com/video.yahoofinance.com@8dfea102-b1a8-362e-9e14-5554f85eab4c_FULL.jpg","cover_image":"https://www.bitcoinnews.ch/wp-content/uploads/2013/11/bitcoin.jpg"} |
{
"posting_json_metadata": {
"profile": {
"profile_image": "http://media.zenfs.com/en-US/video/video.pd2upload.com/video.yahoofinance.com@8dfea102-b1a8-362e-9e14-5554f85eab4c_FULL.jpg",
"cover_image": "https://www.bitcoinnews.ch/wp-content/uploads/2013/11/bitcoin.jpg"
}
},
"json_metadata": {
"profile": {
"profile_image": "http://media.zenfs.com/en-US/video/video.pd2upload.com/video.yahoofinance.com@8dfea102-b1a8-362e-9e14-5554f85eab4c_FULL.jpg",
"cover_image": "https://www.bitcoinnews.ch/wp-content/uploads/2013/11/bitcoin.jpg"
}
}
}Auth Keys
Owner
Single Signature
Public Keys
STM8PCoaWx4ZtQdBgfAA2kCoGvJQPhyrWsdRG115gPewzNo3kdbaQ1/1
Active
Single Signature
Public Keys
STM4tx9mDgD6dpbPDXLpmFG6QTGwTZyxWc8vmDgEhmHTdy28mR6um1/1
Posting
Single Signature
Public Keys
STM7DKjN6iNAxFhE2xrENKo8CrvVq6ZWyH7MBZ83vqNbiARSoMwvd1/1
Memo
STM6bNYAxL2GNuguzk7dBKAiohqHyr3Ceop5eD9YjFLiL6SUBcs7u
{
"owner": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM8PCoaWx4ZtQdBgfAA2kCoGvJQPhyrWsdRG115gPewzNo3kdbaQ",
1
]
]
},
"active": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM4tx9mDgD6dpbPDXLpmFG6QTGwTZyxWc8vmDgEhmHTdy28mR6um",
1
]
]
},
"posting": {
"weight_threshold": 1,
"account_auths": [],
"key_auths": [
[
"STM7DKjN6iNAxFhE2xrENKo8CrvVq6ZWyH7MBZ83vqNbiARSoMwvd",
1
]
]
},
"memo": "STM6bNYAxL2GNuguzk7dBKAiohqHyr3Ceop5eD9YjFLiL6SUBcs7u"
}Witness Votes
0 / 30
No active witness votes.
[]