{
  "block": 106142056,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "currypto",
      "delegator": "steem",
      "vesting_shares": "7108.612991 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2026-05-17T23:05:15",
  "trx_id": "f6a38f95ae47af1efee593298fddf361d0b439ee",
  "trx_in_block": 0,
  "virtual_op": 0
}

{
  "block": 105970117,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "currypto",
      "delegator": "steem",
      "vesting_shares": "4396.402586 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2026-05-11T23:10:06",
  "trx_id": "8bf5abf0c8bec9e72c9c356a4c8470df337a19b5",
  "trx_in_block": 0,
  "virtual_op": 0
}

{
  "block": 105509743,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "currypto",
      "delegator": "steem",
      "vesting_shares": "7121.128747 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2026-04-25T22:28:09",
  "trx_id": "0cf26ae00e740f56d0bed152fdadb5071eb0ff28",
  "trx_in_block": 0,
  "virtual_op": 0
}

{
  "block": 102848086,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "currypto",
      "delegator": "steem",
      "vesting_shares": "4437.949405 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2026-01-23T04:41:30",
  "trx_id": "adec9905a7b1d6ef1300a9a662d7da6b1a42f736",
  "trx_in_block": 0,
  "virtual_op": 0
}

{
  "block": 91294496,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "currypto",
      "delegator": "steem",
      "vesting_shares": "4602.168602 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2024-12-17T00:00:48",
  "trx_id": "9e49efa131ee8164f355335c04221f9309a91147",
  "trx_in_block": 8,
  "virtual_op": 0
}

{
  "block": 79848736,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "currypto",
      "delegator": "steem",
      "vesting_shares": "4771.302134 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2023-11-13T15:45:00",
  "trx_id": "968e77239c7a6d6dc5f2f1b48073b93294854a3e",
  "trx_in_block": 2,
  "virtual_op": 0
}

{
  "block": 78346197,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "currypto",
      "delegator": "steem",
      "vesting_shares": "7708.580920 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2023-09-21T20:27:54",
  "trx_id": "585568688ae3a818a861c13970e845d89587afb2",
  "trx_in_block": 1,
  "virtual_op": 0
}

{
  "block": 69111741,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "currypto",
      "delegator": "steem",
      "vesting_shares": "7930.262358 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2022-11-03T10:25:48",
  "trx_id": "a48f8de619653f0e29503ed21f222b26975ece74",
  "trx_in_block": 0,
  "virtual_op": 0
}

{
  "block": 60808035,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "currypto",
      "delegator": "steem",
      "vesting_shares": "8150.795589 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2022-01-17T09:48:03",
  "trx_id": "8d8e0b8c43acaeb9d95e3a1ce23b08b2e2686fbd",
  "trx_in_block": 2,
  "virtual_op": 0
}

{
  "block": 54606479,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "currypto",
      "delegator": "steem",
      "vesting_shares": "8334.564247 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2021-06-13T23:45:57",
  "trx_id": "8c646dabe14d65de66a9f58f7cbb350cd6a1623e",
  "trx_in_block": 6,
  "virtual_op": 0
}

{
  "block": 49353982,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "currypto",
      "delegator": "steem",
      "vesting_shares": "8521.986221 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-12-11T10:06:33",
  "trx_id": "4ee3207fdf06344d92854a4b9eb6df5595d692cd",
  "trx_in_block": 3,
  "virtual_op": 0
}

{
  "block": 49205546,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "currypto",
      "delegator": "steem",
      "vesting_shares": "1912.543513 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-12-06T03:43:42",
  "trx_id": "ea69abb2666f68f37a5753a9237c13cc8f498055",
  "trx_in_block": 2,
  "virtual_op": 0
}

{
  "block": 49186653,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "currypto",
      "delegator": "steem",
      "vesting_shares": "8528.352860 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-12-05T11:40:57",
  "trx_id": "413b05cbf49af96c238533b696f7ad59f5a31964",
  "trx_in_block": 5,
  "virtual_op": 0
}

{
  "block": 48255128,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "currypto",
      "delegator": "steem",
      "vesting_shares": "1920.017158 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-11-02T13:21:57",
  "trx_id": "2bb1175e87a8a921951d8b07abe1e9b2ea604bc1",
  "trx_in_block": 3,
  "virtual_op": 0
}

{
  "block": 43215780,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "currypto",
      "delegator": "steem",
      "vesting_shares": "8730.999434 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-05-09T04:39:57",
  "trx_id": "e8e7f46783c38931908a36ee00bf47cc77f6e194",
  "trx_in_block": 16,
  "virtual_op": 0
}

{
  "block": 43191689,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "currypto",
      "delegator": "steem",
      "vesting_shares": "1953.311140 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-05-08T08:06:36",
  "trx_id": "c471402737876a3fa11c1ca48ce4abf0fa9d0b2f",
  "trx_in_block": 10,
  "virtual_op": 0
}

{
  "block": 42561780,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "currypto",
      "delegator": "steem",
      "vesting_shares": "8743.976853 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2020-04-15T20:56:39",
  "trx_id": "5116bdc06982e4a87bae4dabea6024abc23339a7",
  "trx_in_block": 7,
  "virtual_op": 0
}

{
  "block": 33943108,
  "op": [
    "comment",
    {
      "author": "steemitboard",
      "body": "Congratulations @currypto! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@currypto/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/@currypto) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=currypto)_</sub>\n\n\n**Do not miss the last post from @steemitboard:**\n<table><tr><td><a href=\"https://steemit.com/steemtoolbar/@steemitboard/steemtoolbar-update-display-bug-fixed\"><img src=\"https://steemitimages.com/64x128/http://i.cubeupload.com/7CiQEO.png\"></a></td><td><a href=\"https://steemit.com/steemtoolbar/@steemitboard/steemtoolbar-update-display-bug-fixed\">SteemitBoard - Witness Update</a></td></tr><tr><td><a href=\"https://steemit.com/steem/@steemitboard/do-not-miss-the-coming-rocky-mountain-steem-meetup-and-get-a-new-community-badge\"><img src=\"https://steemitimages.com/64x128/https://cdn.steemitimages.com/DQmUphCGZFWgt6bJ1XTtunV7esnwy6bxnGqcLcHAV3NEqnQ/meetup-rocky-mountain.png\"></a></td><td><a href=\"https://steemit.com/steem/@steemitboard/do-not-miss-the-coming-rocky-mountain-steem-meetup-and-get-a-new-community-badge\">Do not miss the coming Rocky Mountain Steem Meetup and get a new community badge!</a></td></tr></table>\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
      "json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}",
      "parent_author": "currypto",
      "parent_permlink": "shift-an-ipfs-based-cryptocurrency",
      "permlink": "steemitboard-notify-currypto-20190619t184038000z",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-06-19T18:40:39",
  "trx_id": "7f7542cf798f1da6ba403a140011ee38df303cbc",
  "trx_in_block": 0,
  "virtual_op": 0
}

{
  "block": 32844631,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "currypto",
      "delegator": "steem",
      "vesting_shares": "8939.599658 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2019-05-12T14:11:24",
  "trx_id": "53578bc163abaa157b42c369eaf991cc86c44c19",
  "trx_in_block": 21,
  "virtual_op": 0
}

{
  "block": 23656239,
  "op": [
    "vote",
    {
      "author": "currypto",
      "permlink": "shift-an-ipfs-based-cryptocurrency",
      "voter": "supere989",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-06-26T09:18:18",
  "trx_id": "d5b296c73c31d1722140747054ec428b741b2cdf",
  "trx_in_block": 8,
  "virtual_op": 0
}

{
  "block": 23466130,
  "op": [
    "comment",
    {
      "author": "steemitboard",
      "body": "Congratulations @currypto! You have received a personal award!\n\n[![](https://steemitimages.com/70x70/http://steemitboard.com/@currypto/birthday1.png)](http://steemitboard.com/@currypto)  1 Year on Steemit\n<sub>_Click on the badge to view your Board of Honor._</sub>\n\n\n**Do not miss the [last post](https://steemit.com/steemitboard/@steemitboard/steemitboard-world-cup-contest-iran-vs-spain) from @steemitboard!**\n\n---\n**Participate in the [SteemitBoard World Cup Contest](https://steemit.com/steemitboard/@steemitboard/steemitboard-world-cup-contest-collect-badges-and-win-free-sbd)!**\nCollect World Cup badges and win free SBD\nSupport the Gold Sponsors of the contest: [@good-karma](https://v2.steemconnect.com/sign/account-witness-vote?witness=good-karma&approve=1) and [@lukestokes](https://v2.steemconnect.com/sign/account-witness-vote?witness=lukestokes.mhth&approve=1)\n\n---\n\n> Do you like [SteemitBoard's project](https://steemit.com/@steemitboard)? Then **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**!",
      "json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}",
      "parent_author": "currypto",
      "parent_permlink": "shift-an-ipfs-based-cryptocurrency",
      "permlink": "steemitboard-notify-currypto-20180619t184941000z",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-06-19T18:49:39",
  "trx_id": "6d198b0cb744867ed60e408201f613ba9ca865c1",
  "trx_in_block": 83,
  "virtual_op": 0
}

{
  "block": 22489751,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "currypto",
      "delegator": "steem",
      "vesting_shares": "9139.152093 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-05-16T20:12:30",
  "trx_id": "7eb9596ff29b6820913e9685d5bc27f1bc766b78",
  "trx_in_block": 27,
  "virtual_op": 0
}

{
  "block": 20428081,
  "op": [
    "vote",
    {
      "author": "currypto",
      "permlink": "shift-an-ipfs-based-cryptocurrency",
      "voter": "endercase",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-03-06T04:15:54",
  "trx_id": "0f8cd634cbe8f05b05bc1d8440a7d51d794a6651",
  "trx_in_block": 10,
  "virtual_op": 0
}

{
  "block": 18937867,
  "op": [
    "vote",
    {
      "author": "currypto",
      "permlink": "shift-an-ipfs-based-cryptocurrency",
      "voter": "zeitspringer",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-01-13T09:18:36",
  "trx_id": "1b576cea781c689f381cb419d40cb1ec5b05f1ad",
  "trx_in_block": 35,
  "virtual_op": 0
}

{
  "block": 18819535,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "currypto",
      "delegator": "steem",
      "vesting_shares": "29690.142477 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2018-01-09T06:36:45",
  "trx_id": "4722afbde22424a416cc748f6fee9859d6f3c9a8",
  "trx_in_block": 17,
  "virtual_op": 0
}

{
  "block": 17717963,
  "op": [
    "vote",
    {
      "author": "currypto",
      "permlink": "shift-an-ipfs-based-cryptocurrency",
      "voter": "techsys",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-12-02T00:00:24",
  "trx_id": "8480cf3b154f074aa91d4146ea38705792207b72",
  "trx_in_block": 0,
  "virtual_op": 0
}

{
  "block": 16135422,
  "op": [
    "vote",
    {
      "author": "currypto",
      "permlink": "shift-an-ipfs-based-cryptocurrency",
      "voter": "lapingvino",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-10-08T00:17:12",
  "trx_id": "4d806929c3e755b2a755bb1e217a22a0d33e1b89",
  "trx_in_block": 9,
  "virtual_op": 0
}

{
  "block": 14271437,
  "op": [
    "delegate_vesting_shares",
    {
      "delegatee": "currypto",
      "delegator": "steem",
      "vesting_shares": "29940.953185 VESTS"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-08-04T05:17:57",
  "trx_id": "22136ba7068d1bf2d99a68b7850bb7ba56268703",
  "trx_in_block": 46,
  "virtual_op": 0
}

{
  "block": 14212142,
  "op": [
    "comment",
    {
      "author": "steemitboard",
      "body": "Congratulations @currypto! You have completed some achievement on Steemit and have been rewarded with new badge(s) :\n\n[![](https://steemitimages.com/70x80/http://steemitboard.com/notifications/firstpost.png)](http://steemitboard.com/@currypto) You published your First Post\n[![](https://steemitimages.com/70x80/http://steemitboard.com/notifications/firstvote.png)](http://steemitboard.com/@currypto) You made your First Vote\n[![](https://steemitimages.com/70x80/http://steemitboard.com/notifications/firstvoted.png)](http://steemitboard.com/@currypto) You got a First Vote\n\nClick on any badge to view your own Board of Honor on SteemitBoard.\nFor more information about SteemitBoard, click [here](https://steemit.com/@steemitboard)\n\nIf you no longer want to receive notifications, reply to this comment with the word `STOP`\n\n> By upvoting this notification, you can help all Steemit users. Learn how [here](https://steemit.com/steemitboard/@steemitboard/http-i-cubeupload-com-7ciqeo-png)!",
      "json_metadata": "{\"image\":[\"https://steemitboard.com/img/notifications.png\"]}",
      "parent_author": "currypto",
      "parent_permlink": "shift-an-ipfs-based-cryptocurrency",
      "permlink": "steemitboard-notify-currypto-20170802t035129000z",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-08-02T03:51:27",
  "trx_id": "8cbde1202960b747ba31e9c2a032db03062143be",
  "trx_in_block": 21,
  "virtual_op": 0
}

{
  "block": 14209933,
  "op": [
    "vote",
    {
      "author": "currypto",
      "permlink": "shift-an-ipfs-based-cryptocurrency",
      "voter": "charlesarthuriii",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-08-02T02:01:00",
  "trx_id": "3e9f0af1c81624421342951b8259754bf9149be7",
  "trx_in_block": 13,
  "virtual_op": 0
}

{
  "block": 14209652,
  "op": [
    "comment",
    {
      "author": "currypto",
      "body": "# Shift - An IPFS-based Cryptocurrency\n\nThis coin was brought to my attention by \"Blue trade\", who was going by an alternative name a few weeks ago. They were persistent on pushing Shift as \"the one\", as most of these pumper-users do. Shift is marketed as the next Ethereum, Sia, and Bitcoin all in one nice package. Words like DApp, proof-of-stake, forging, and smart contracts are thrown around in its presence. Out of skepticsm I decide to investigate what this is all about.\n\n## What Shift is and is not.\n\nI figure the best way to know what Shift really does is to go to their website and use Google. Their website is not very informative, despite having \"information\" all over it. \n\n![](https://steemitimages.com/DQmRvmUkBjtAJWMacWKfEviPUBmG9gySmaj341vVxJVQU1n/image.png)\n![](https://steemitimages.com/DQmbVGzMSST4YkxwR94shZsrS2J5rBshioDcAjSFGAAiVaP/image.png)\n\nAt first it looks amazing and informative, but the key is in the details. Lets break these points down.\n\n1. Peer-2-peer data storage - using IPFS\nIPFS is a distributed file system that is typically setup in a peer-to-peer (p2p) configuration. So Shift uses IPFS to store data. How does it enforce users to keep data? How is data replicated for redundancy? Right now IPFS is a completely free network/storage solution run by volunteers.\n\n2. \"Monetization of user-created content is seamless\"\nIf people are just paying for anything with Shift, it's no different than paying with Bitcoin or any other cryptocurrency. They are saying since you store data on the Shift network (which is just regular IPFS...) and you must pay to store it there and download it, this is monetization of whatever you have stored. This could be a video or software for example.\n\n3. \"No single point of failure and no single provider to censor.\"\nTies back to point 1 - using IPFS, and has nothing to do with Shift itself. In fact, there is nothing stopping your IPFS host from dropping your data. This is true of any storage solution in existence, but alternatives (Sia) have solved this issue through incentives. \n\n4. Turing-complete blockchain\nShift is not turing complete like Ethereum is. There is no network-wide virtual machine running.\n\n5. Decentralized marketplaces\nImplying that markets can be hosted on the IPFS network. Why Shift matters here... not sure. If anything, Shift users will have to pay to access these IPFS/Shift marketplace websites.\n\n6. Uncensorable social media\nOnce again not true. Hosts can decide to drop media they do not like. And once again, IPFS specific and nothing to do with Shift.\n\n7. Identity and reputation - \"Permanently embedded [...] to make it tamper-proof\"Like what every other cryptocurreny can already do?\n\n8. \"The new web is versatile and adaptable. Anything that can be done on the world wide web, we can do better.\"\nWell at least the Shift team have a positive outlook on their future.\n\nAt this point I have no clue why Shift even exists. The project is IPFS/Shift, or as I've recently taken to calling it, IPFS plus Shift. Why not IPFS plus Bitcoin? IPFS plus Ethereum? Now that would be a crazy combination to see come to life. \nReally the only way I can see Shift surviving is if they merge themselves with the IPFS project. It's necessary to do this to enforce storage payments. Another major problem I thought of is, what happens when users just want to use free IPFS nodes? Then Shift really won't have any use. They would have to use specific Shift nodes for payment-related operations.\n\nIn all my confusion, I figure the best course of action is to ask the Shift developers themselves what exactly Shift is for and how it works. While waiting for responses, I dig a little into Shift's source code.\n\n## Source code under the magnifying glass\n\nThere are currently two big projects under the Shift name: Shift the cryptocurrency; and Phantom the IPFS GUI client. Phantom uses Shift to pay and receive money for storage. Seeing this I wonder, how are Shift developers integrating their product with IPFS? There must be a level of integration because IPFS is not built with payments in mind, unlike say the Sia network. If this integration somehow works with the existing IPFS network, then maybe Shift has more potential than I initially thought. It would open a massive door to small p2p websites or web applications.\n\nThe source code is mostly JavaScript, using NodeJS. It's very organized. Shift is actually a fork of the Lisk project. Unfortunately Shift developers are not pulling changes downstream from Lisk, which speaks wonders. Not pulling new changes from there means they are disregarding bug fixes, efficiency improvements and features a *much* larger team is pushing out. The biggest feature they will miss out on, I would say the one feature that actually gives Lisk appeal is this:\n\n![](https://steemitimages.com/DQmSVKP7PbZXKpLHbz49h1DWSKoNVGrdSBFgZxKoGVqJNbQ/image.png)\n\nIn no time I have a mental image of the state Shift is in. Shift is alpha software. It is weird to say that because they are built off of Lisk, but all their promises are just non-existent. \n\nTheir Phantom IPFS client is running on a testnet with a proof of concept \"DApp\" running. This is not a distributed application like what Ethereum offers. They call it a \"DApp\" because the application (which is just a web application hosted on a semi-IPFS network) is hosted on many hosts and will eventally use its own sidechain for payments. This is equivalent to me saying Chrome is a DApp because it uses the Internet to access information and applications and you can pay for things using any payment processors put on a web page.\n\n## A developers answers me\n\nOne particular developer reached out to me, Ralf S. He was somewhat helpful answering, but not thoroughly. I have attached the discussion between us for full disclosure as always. These are the questions (and questions to the answers of those questions!) I asked:\n\n1\\. How is Shift tied to IPFS\n> Shift is a fork of Lisk, so a blockchain written in JavaScript, secured by 101+ VPS nodes. It supports decentralized apps (dApps), and the first Shift dapp already runs at out testnet (latest code, different blockchain).  This dApp is called Phantom and brings a UI for file management, directly at the IPFS network. Added content can be resolved from any other node running IPFS. The dapp also includes a wizard to connect your hashes to TLD's.\nThe next step will be a reward system, so all nodes (not only the 101 forging delegates) running Shift software can earn tokens by offering decentralized hosting. Phantom runs it's own sidechain, what makes custom fees, and transaction types possible, without affecting our mainchain.  \n\nHe does not answer me how Shift is tied to IPFS at all. From the sound of it though, they are in fact maintaining their own IPFS fork.\n\n2\\. How does Shift distribute to hosts?\n> Distribute data? through a custom built deamon/api. Distribute Shift tokens? People can forge or buy Shift, and deposit some at the Phantom sidechain.  Multiple nodes will be found there, offering their service for a X fee for hosting (pinning) data, costing Y tokens for Z days. It should be easy to clone that pinned data to multiple nodes at once, without re-uploading.\n\nHere I meant how does Shift distribute its tokens for redundancy storage. He responds:\n\n> \"Distribute Shift tokens yes. If I want to store something on IPFS network, am I just storing it on one node when I pay?\"\nYou can add it to a lot of nodes for free too. But with paying your data will be pinned, so it won't be wiped by the garbage collector from time to time (wipe cache alike)\n\nSo manual redundancy and full copy redundancy.\n\nShift also has no proof of storage implemented right now. You can give a user Shift but there's no guarantee they have kept your data. Ralf says host nodes will have to resolve a hash of the data periodically. This is similar to what Sia does, except providing hashes does not prove data is stored, only its hash. Sia requires a block of data to be sent to the renter in order to verify it in a time frame.\n\n3\\. Does the Shift network make use of the current IPFS network, or its own?\n> The nodes running at testnet share the same network. Because this way the hosted data can be resolved through all other peers too.\nIf we wouldn't ask a fee for pinning data, there would be a risk of people spamming our nodes. So it's important the reward system is ready before we bring Phantom to mainnet.\n\nVague answer to the question - he says it uses the current IPFS network...But if that's the case, what's stopping people from just using free / non-Shift IPFS nodes? I poke a little more, and Ralf says:\n\n> \"Well that's only if IPFS accepts the changes Shift team is doing, right?\"\nWe built our own binary. It's the default IPFS daemon (written in golang, downloaded by our installer) with our enhancements to use it at public VPS nodes.  We might switch to js-ipfs at some point. But go-ipfs offers more at this stage, like publishing hashes for DNS.\n\nSo yes, it looks like my assumptions are correct. In order for Shift to have mass adoption by the current IPFS network they will have to merge code or coordinate together.\n\n4\\. Do those delegates even have the CPU power to handle every transaction on the network?\n> Today the network can handle large amounts of transactions. We could look back how much txs it handled well, when we tested broadcasting a huge amount per block. Do you still have some numbers from your tests @mq?\n\n@mq responds: \n> regarding transactions - currently network can process 25 transactions per block (hard-coded limit) and 1k transactions waiting in queue and network is stable under such load\n> however transaction processing will be rewritten soon\n\nI ask:\n> How long does it take to process 1 block\n\n@mq:\n> on average less that 1 second\n\nHonestly I don't know what to make of this, and can only assume \"this is ok\".\n\n## Final words\nShift has great potiental, but *if and only if* they team up with IPFS. Creating a tight integration with this software is essential to its success. Sia has shown that already, displaying great all-around efficiency.\n\nThis article is brought to you by http://currypto.club, a premium information service in regards to cryptocurrencies.\n\nLike it? Consider supporting me here on Steemit or there, where I will accept $10 USD in STEEM or any other Poloniex supported currency.",
      "json_metadata": "{\"tags\":[\"currypto\",\"shift\",\"sia\",\"crypto\",\"minnowsupport\"],\"image\":[\"https://steemitimages.com/DQmRvmUkBjtAJWMacWKfEviPUBmG9gySmaj341vVxJVQU1n/image.png\",\"https://steemitimages.com/DQmbVGzMSST4YkxwR94shZsrS2J5rBshioDcAjSFGAAiVaP/image.png\",\"https://steemitimages.com/DQmSVKP7PbZXKpLHbz49h1DWSKoNVGrdSBFgZxKoGVqJNbQ/image.png\"],\"links\":[\"http://currypto.club\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
      "parent_author": "",
      "parent_permlink": "currypto",
      "permlink": "shift-an-ipfs-based-cryptocurrency",
      "title": "Shift - An IPFS-based Cryptocurrency"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-08-02T01:46:57",
  "trx_id": "e95f5323b659340dbc12ecbeef3d3cdebece7483",
  "trx_in_block": 13,
  "virtual_op": 0
}

{
  "block": 14209546,
  "op": [
    "comment",
    {
      "author": "currypto",
      "body": "# Shift - An IPFS-based Cryptocurrency\n\nThis coin was brought to my attention by \"Blue trade\", who was going by an alternative name a few weeks ago. They were persistent on pushing Shift as \"the one\", as most of these pumper-users do. Shift is marketed as the next Ethereum, Sia, and Bitcoin all in one nice package. Words like DApp, proof-of-stake, forging, and smart contracts are thrown around in its presence. Out of skepticsm I decide to investigate what this is all about.\n\n## What Shift is and is not.\n\nI figure the best way to know what Shift really does is to go to their website and use Google. Their website is not very informative, despite having \"information\" all over it. \n\n![](https://steemitimages.com/DQmRvmUkBjtAJWMacWKfEviPUBmG9gySmaj341vVxJVQU1n/image.png)\n![](https://steemitimages.com/DQmbVGzMSST4YkxwR94shZsrS2J5rBshioDcAjSFGAAiVaP/image.png)\n\nAt first it looks amazing and informative, but the key is in the details. Lets break these points down.\n\n1. Peer-2-peer data storage - using IPFS\nIPFS is a distributed file system that is typically setup in a peer-to-peer (p2p) configuration. So Shift uses IPFS to store data. How does it enforce users to keep data? How is data replicated for redundancy? Right now IPFS is a completely free network/storage solution run by volunteers.\n\n2. \"Monetization of user-created content is seamless\"\nIf people are just paying for anything with Shift, it's no different than paying with Bitcoin or any other cryptocurrency. They are saying since you store data on the Shift network (which is just regular IPFS...) and you must pay to store it there and download it, this is monetization of whatever you have stored. This could be a video or software for example.\n\n3. \"No single point of failure and no single provider to censor.\"\nTies back to point 1 - using IPFS, and has nothing to do with Shift itself. In fact, there is nothing stopping your IPFS host from dropping your data. This is true of any storage solution in existence, but alternatives (Sia) have solved this issue through incentives. \n\n4. Turing-complete blockchain\nShift is not turing complete like Ethereum is. There is no network-wide virtual machine running.\n\n5. Decentralized marketplaces\nImplying that markets can be hosted on the IPFS network. Why Shift matters here... not sure. If anything, Shift users will have to pay to access these IPFS/Shift marketplace websites.\n\n6. Uncensorable social media\nOnce again not true. Hosts can decide to drop media they do not like. And once again, IPFS specific and nothing to do with Shift.\n\n7. Identity and reputation - \"Permanently embedded [...] to make it tamper-proof\"Like what every other cryptocurreny can already do?\n\n8. \"The new web is versatile and adaptable. Anything that can be done on the world wide web, we can do better.\"\nWell at least the Shift team have a positive outlook on their future.\n\nAt this point I have no clue why Shift even exists. The project is IPFS/Shift, or as I've recently taken to calling it, IPFS plus Shift. Why not IPFS plus Bitcoin? IPFS plus Ethereum? Now that would be a crazy combination to see come to life. \nReally the only way I can see Shift surviving is if they merge themselves with the IPFS project. It's necessary to do this to enforce storage payments. Another major problem I thought of is, what happens when users just want to use free IPFS nodes? Then Shift really won't have any use. They would have to use specific Shift nodes for payment-related operations.\n\nIn all my confusion, I figure the best course of action is to ask the Shift developers themselves what exactly Shift is for and how it works. While waiting for responses, I dig a little into Shift's source code.\n\n## Source code under the magnifying glass\n\nThere are currently two big projects under the Shift name: Shift the cryptocurrency; and Phantom the IPFS GUI client. Phantom uses Shift to pay and receive money for storage. Seeing this I wonder, how are Shift developers integrating their product with IPFS? There must be a level of integration because IPFS is not built with payments in mind, unlike say the Sia network. If this integration somehow works with the existing IPFS network, then maybe Shift has more potential than I initially thought. It would open a massive door to small p2p websites or web applications.\n\nThe source code is mostly JavaScript, using NodeJS. It's very organized. Shift is actually a fork of the Lisk project. Unfortunately Shift developers are not pulling changes downstream from Lisk, which speaks wonders. Not pulling new changes from there means they are disregarding bug fixes, efficiency improvements and features a *much* larger team is pushing out. The biggest feature they will miss out on, I would say the one feature that actually gives Lisk appeal is this:\n\n![](https://steemitimages.com/DQmSVKP7PbZXKpLHbz49h1DWSKoNVGrdSBFgZxKoGVqJNbQ/image.png)\n\nIn no time I have a mental image of the state Shift is in. Shift is alpha software. It is weird to say that because they are built off of Lisk, but all their promises are just non-existent. \n\nTheir Phantom IPFS client is running on a testnet with a proof of concept \"DApp\" running. This is not a distributed application like what Ethereum offers. They call it a \"DApp\" because the application (which is just a web application hosted on a semi-IPFS network) is hosted on many hosts and will eventally use its own sidechain for payments. This is equivalent to me saying Chrome is a DApp because it uses the Internet to access information and applications and you can pay for things using any payment processors put on a web page.\n\n## A developers answers me\n\nOne particular developer reached out to me, Ralf S. He was somewhat helpful answering, but not thoroughly. I have attached the discussion between us for full disclosure as always. These are the questions (and questions to the answers of those questions!) I asked:\n\n1\\. How is Shift tied to IPFS\n> Shift is a fork of Lisk, so a blockchain written in JavaScript, secured by 101+ VPS nodes. It supports decentralized apps (dApps), and the first Shift dapp already runs at out testnet (latest code, different blockchain).  This dApp is called Phantom and brings a UI for file management, directly at the IPFS network. Added content can be resolved from any other node running IPFS. The dapp also includes a wizard to connect your hashes to TLD's.\nThe next step will be a reward system, so all nodes (not only the 101 forging delegates) running Shift software can earn tokens by offering decentralized hosting. Phantom runs it's own sidechain, what makes custom fees, and transaction types possible, without affecting our mainchain.  \n\nHe does not answer me how Shift is tied to IPFS at all. From the sound of it though, they are in fact maintaining their own IPFS fork.\n\n2\\. How does Shift distribute to hosts?\n> Distribute data? through a custom built deamon/api. Distribute Shift tokens? People can forge or buy Shift, and deposit some at the Phantom sidechain.  Multiple nodes will be found there, offering their service for a X fee for hosting (pinning) data, costing Y tokens for Z days. It should be easy to clone that pinned data to multiple nodes at once, without re-uploading.\n\nHere I meant how does Shift distribute its tokens for redundancy storage. He responds:\n\n> \"Distribute Shift tokens yes. If I want to store something on IPFS network, am I just storing it on one node when I pay?\"\nYou can add it to a lot of nodes for free too. But with paying your data will be pinned, so it won't be wiped by the garbage collector from time to time (wipe cache alike)\n\nSo manual redundancy and full copy redundancy.\n\nShift also has no proof of storage implemented right now. You can give a user Shift but there's no guarantee they have kept your data. Ralf says host nodes will have to resolve a hash of the data periodically. This is similar to what Sia does, except providing hashes does not prove data is stored, only its hash. Sia requires a block of data to be sent to the renter in order to verify it in a time frame.\n\n3\\. Does the Shift network make use of the current IPFS network, or its own?\n> The nodes running at testnet share the same network. Because this way the hosted data can be resolved through all other peers too.\nIf we wouldn't ask a fee for pinning data, there would be a risk of people spamming our nodes. So it's important the reward system is ready before we bring Phantom to mainnet.\n\nVague answer to the question - he says it uses the current IPFS network...But if that's the case, what's stopping people from just using free / non-Shift IPFS nodes? I poke a little more, and Ralf says:\n\n> \"Well that's only if IPFS accepts the changes Shift team is doing, right?\"\nWe built our own binary. It's the default IPFS daemon (written in golang, downloaded by our installer) with our enhancements to use it at public VPS nodes.  We might switch to js-ipfs at some point. But go-ipfs offers more at this stage, like publishing hashes for DNS.\n\nSo yes, it looks like my assumptions are correct. In order for Shift to have mass adoption by the current IPFS network they will have to merge code or coordinate together.\n\n4\\. Do those delegates even have the CPU power to handle every transaction on the network?\n> Today the network can handle large amounts of transactions. We could look back how much txs it handled well, when we tested broadcasting a huge amount per block. Do you still have some numbers from your tests @mq?\n\n@mq responds: \n> regarding transactions - currently network can process 25 transactions per block (hard-coded limit) and 1k transactions waiting in queue and network is stable under such load\n> however transaction processing will be rewritten soon\n\nI ask:\n> How long does it take to process 1 block\n\n@mq:\n> on average less that 1 second\n\nHonestly I don't know what to make of this, and can only assume \"this is ok\".\n\n## Final words\nShift has great potiental, but *if and only if* they team up with IPFS. Creating a tight integration with this software is essential to its success. Sia has shown that already, displaying great all-around efficiency.\n\nThis article is brought to you by http://currypto.club, a premium information service in regards to cryptocurrencies.\n\nLike it? Consider supporting me here on Steemit or there, where I will accept $10 USD in STEEM or any other Poloniex supported currency.",
      "json_metadata": "{\"tags\":[\"currypto\",\"ipfs\",\"shift\",\"sia\",\"crypto\"],\"image\":[\"https://steemitimages.com/DQmRvmUkBjtAJWMacWKfEviPUBmG9gySmaj341vVxJVQU1n/image.png\",\"https://steemitimages.com/DQmbVGzMSST4YkxwR94shZsrS2J5rBshioDcAjSFGAAiVaP/image.png\",\"https://steemitimages.com/DQmSVKP7PbZXKpLHbz49h1DWSKoNVGrdSBFgZxKoGVqJNbQ/image.png\"],\"links\":[\"http://currypto.club\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
      "parent_author": "",
      "parent_permlink": "currypto",
      "permlink": "shift-an-ipfs-based-cryptocurrency",
      "title": "Shift - An IPFS-based Cryptocurrency"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-08-02T01:41:39",
  "trx_id": "43ccb722e2c7abd91ab0c52b00cb235b19eeaed6",
  "trx_in_block": 11,
  "virtual_op": 0
}

{
  "block": 14209383,
  "op": [
    "comment",
    {
      "author": "currypto",
      "body": "@@ -10160,17 +10160,16 @@\n to you b\n-u\n y http:/\n",
      "json_metadata": "{\"tags\":[\"currypto\",\"ipfs\",\"shift\",\"sia\"],\"image\":[\"https://steemitimages.com/DQmRvmUkBjtAJWMacWKfEviPUBmG9gySmaj341vVxJVQU1n/image.png\",\"https://steemitimages.com/DQmbVGzMSST4YkxwR94shZsrS2J5rBshioDcAjSFGAAiVaP/image.png\",\"https://steemitimages.com/DQmSVKP7PbZXKpLHbz49h1DWSKoNVGrdSBFgZxKoGVqJNbQ/image.png\"],\"links\":[\"http://currypto.club\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
      "parent_author": "",
      "parent_permlink": "currypto",
      "permlink": "shift-an-ipfs-based-cryptocurrency",
      "title": "Shift - An IPFS-based Cryptocurrency"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-08-02T01:33:30",
  "trx_id": "f0b8a67434b08949b863df920739f43963e40348",
  "trx_in_block": 0,
  "virtual_op": 0
}

{
  "block": 14209373,
  "op": [
    "comment",
    {
      "author": "extras",
      "body": "Hi. I am a volunteer bot for @resteembot that upvoted you.\nYour post was chosen at random, as part of the advertisment campaign for @resteembot.\n@resteembot is meant to help minnows get noticed by re-steeming their posts\n-----\nTo use the bot, one must follow it for at least 3 hours, and then make a transaction where the memo is the url of the post.\nIf you want to learn more - [read the introduction post of @resteembot](https://steemit.com/resteembot/@resteembot/how-to-use-resteembot).\nIf you want help spread the word - [read the advertisment program post](https://steemit.com/resteembot/@resteembot/how-to-help-resteem-bot-spread-the-word).\n-----\nSteem ON!",
      "json_metadata": "",
      "parent_author": "currypto",
      "parent_permlink": "shift-an-ipfs-based-cryptocurrency",
      "permlink": "re-currypto-shift-an-ipfs-based-cryptocurrency-20170802t013303715z",
      "title": ""
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-08-02T01:33:00",
  "trx_id": "a3f85b271338839ef3441ad87b4709a2a5dcda99",
  "trx_in_block": 19,
  "virtual_op": 0
}

{
  "block": 14209373,
  "op": [
    "vote",
    {
      "author": "currypto",
      "permlink": "shift-an-ipfs-based-cryptocurrency",
      "voter": "extras",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-08-02T01:33:00",
  "trx_id": "854329f747552098b98e2c7cf2fd469a432903fd",
  "trx_in_block": 14,
  "virtual_op": 0
}

{
  "block": 14209355,
  "op": [
    "vote",
    {
      "author": "currypto",
      "permlink": "shift-an-ipfs-based-cryptocurrency",
      "voter": "currypto",
      "weight": 10000
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-08-02T01:32:06",
  "trx_id": "a5dbc78e1d35c2eab4571ee26dd2520e640b2116",
  "trx_in_block": 15,
  "virtual_op": 0
}

{
  "block": 14209355,
  "op": [
    "comment_options",
    {
      "allow_curation_rewards": true,
      "allow_votes": true,
      "author": "currypto",
      "extensions": [],
      "max_accepted_payout": "1000000.000 SBD",
      "percent_steem_dollars": 0,
      "permlink": "shift-an-ipfs-based-cryptocurrency"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-08-02T01:32:06",
  "trx_id": "a5dbc78e1d35c2eab4571ee26dd2520e640b2116",
  "trx_in_block": 15,
  "virtual_op": 0
}

{
  "block": 14209355,
  "op": [
    "comment",
    {
      "author": "currypto",
      "body": "# Shift - An IPFS-based Cryptocurrency\n\nThis coin was brought to my attention by \"Blue trade\", who was going by an alternative name a few weeks ago. They were persistent on pushing Shift as \"the one\", as most of these pumper-users do. Shift is marketed as the next Ethereum, Sia, and Bitcoin all in one nice package. Words like DApp, proof-of-stake, forging, and smart contracts are thrown around in its presence. Out of skepticsm I decide to investigate what this is all about.\n\n## What Shift is and is not.\n\nI figure the best way to know what Shift really does is to go to their website and use Google. Their website is not very informative, despite having \"information\" all over it. \n\n![](https://steemitimages.com/DQmRvmUkBjtAJWMacWKfEviPUBmG9gySmaj341vVxJVQU1n/image.png)\n![](https://steemitimages.com/DQmbVGzMSST4YkxwR94shZsrS2J5rBshioDcAjSFGAAiVaP/image.png)\n\nAt first it looks amazing and informative, but the key is in the details. Lets break these points down.\n\n1. Peer-2-peer data storage - using IPFS\nIPFS is a distributed file system that is typically setup in a peer-to-peer (p2p) configuration. So Shift uses IPFS to store data. How does it enforce users to keep data? How is data replicated for redundancy? Right now IPFS is a completely free network/storage solution run by volunteers.\n\n2. \"Monetization of user-created content is seamless\"\nIf people are just paying for anything with Shift, it's no different than paying with Bitcoin or any other cryptocurrency. They are saying since you store data on the Shift network (which is just regular IPFS...) and you must pay to store it there and download it, this is monetization of whatever you have stored. This could be a video or software for example.\n\n3. \"No single point of failure and no single provider to censor.\"\nTies back to point 1 - using IPFS, and has nothing to do with Shift itself. In fact, there is nothing stopping your IPFS host from dropping your data. This is true of any storage solution in existence, but alternatives (Sia) have solved this issue through incentives. \n\n4. Turing-complete blockchain\nShift is not turing complete like Ethereum is. There is no network-wide virtual machine running.\n\n5. Decentralized marketplaces\nImplying that markets can be hosted on the IPFS network. Why Shift matters here... not sure. If anything, Shift users will have to pay to access these IPFS/Shift marketplace websites.\n\n6. Uncensorable social media\nOnce again not true. Hosts can decide to drop media they do not like. And once again, IPFS specific and nothing to do with Shift.\n\n7. Identity and reputation - \"Permanently embedded [...] to make it tamper-proof\"Like what every other cryptocurreny can already do?\n\n8. \"The new web is versatile and adaptable. Anything that can be done on the world wide web, we can do better.\"\nWell at least the Shift team have a positive outlook on their future.\n\nAt this point I have no clue why Shift even exists. The project is IPFS/Shift, or as I've recently taken to calling it, IPFS plus Shift. Why not IPFS plus Bitcoin? IPFS plus Ethereum? Now that would be a crazy combination to see come to life. \nReally the only way I can see Shift surviving is if they merge themselves with the IPFS project. It's necessary to do this to enforce storage payments. Another major problem I thought of is, what happens when users just want to use free IPFS nodes? Then Shift really won't have any use. They would have to use specific Shift nodes for payment-related operations.\n\nIn all my confusion, I figure the best course of action is to ask the Shift developers themselves what exactly Shift is for and how it works. While waiting for responses, I dig a little into Shift's source code.\n\n## Source code under the magnifying glass\n\nThere are currently two big projects under the Shift name: Shift the cryptocurrency; and Phantom the IPFS GUI client. Phantom uses Shift to pay and receive money for storage. Seeing this I wonder, how are Shift developers integrating their product with IPFS? There must be a level of integration because IPFS is not built with payments in mind, unlike say the Sia network. If this integration somehow works with the existing IPFS network, then maybe Shift has more potential than I initially thought. It would open a massive door to small p2p websites or web applications.\n\nThe source code is mostly JavaScript, using NodeJS. It's very organized. Shift is actually a fork of the Lisk project. Unfortunately Shift developers are not pulling changes downstream from Lisk, which speaks wonders. Not pulling new changes from there means they are disregarding bug fixes, efficiency improvements and features a *much* larger team is pushing out. The biggest feature they will miss out on, I would say the one feature that actually gives Lisk appeal is this:\n\n![](https://steemitimages.com/DQmSVKP7PbZXKpLHbz49h1DWSKoNVGrdSBFgZxKoGVqJNbQ/image.png)\n\nIn no time I have a mental image of the state Shift is in. Shift is alpha software. It is weird to say that because they are built off of Lisk, but all their promises are just non-existent. \n\nTheir Phantom IPFS client is running on a testnet with a proof of concept \"DApp\" running. This is not a distributed application like what Ethereum offers. They call it a \"DApp\" because the application (which is just a web application hosted on a semi-IPFS network) is hosted on many hosts and will eventally use its own sidechain for payments. This is equivalent to me saying Chrome is a DApp because it uses the Internet to access information and applications and you can pay for things using any payment processors put on a web page.\n\n## A developers answers me\n\nOne particular developer reached out to me, Ralf S. He was somewhat helpful answering, but not thoroughly. I have attached the discussion between us for full disclosure as always. These are the questions (and questions to the answers of those questions!) I asked:\n\n1\\. How is Shift tied to IPFS\n> Shift is a fork of Lisk, so a blockchain written in JavaScript, secured by 101+ VPS nodes. It supports decentralized apps (dApps), and the first Shift dapp already runs at out testnet (latest code, different blockchain).  This dApp is called Phantom and brings a UI for file management, directly at the IPFS network. Added content can be resolved from any other node running IPFS. The dapp also includes a wizard to connect your hashes to TLD's.\nThe next step will be a reward system, so all nodes (not only the 101 forging delegates) running Shift software can earn tokens by offering decentralized hosting. Phantom runs it's own sidechain, what makes custom fees, and transaction types possible, without affecting our mainchain.  \n\nHe does not answer me how Shift is tied to IPFS at all. From the sound of it though, they are in fact maintaining their own IPFS fork.\n\n2\\. How does Shift distribute to hosts?\n> Distribute data? through a custom built deamon/api. Distribute Shift tokens? People can forge or buy Shift, and deposit some at the Phantom sidechain.  Multiple nodes will be found there, offering their service for a X fee for hosting (pinning) data, costing Y tokens for Z days. It should be easy to clone that pinned data to multiple nodes at once, without re-uploading.\n\nHere I meant how does Shift distribute its tokens for redundancy storage. He responds:\n\n> \"Distribute Shift tokens yes. If I want to store something on IPFS network, am I just storing it on one node when I pay?\"\nYou can add it to a lot of nodes for free too. But with paying your data will be pinned, so it won't be wiped by the garbage collector from time to time (wipe cache alike)\n\nSo manual redundancy and full copy redundancy.\n\nShift also has no proof of storage implemented right now. You can give a user Shift but there's no guarantee they have kept your data. Ralf says host nodes will have to resolve a hash of the data periodically. This is similar to what Sia does, except providing hashes does not prove data is stored, only its hash. Sia requires a block of data to be sent to the renter in order to verify it in a time frame.\n\n3\\. Does the Shift network make use of the current IPFS network, or its own?\n> The nodes running at testnet share the same network. Because this way the hosted data can be resolved through all other peers too.\nIf we wouldn't ask a fee for pinning data, there would be a risk of people spamming our nodes. So it's important the reward system is ready before we bring Phantom to mainnet.\n\nVague answer to the question - he says it uses the current IPFS network...But if that's the case, what's stopping people from just using free / non-Shift IPFS nodes? I poke a little more, and Ralf says:\n\n> \"Well that's only if IPFS accepts the changes Shift team is doing, right?\"\nWe built our own binary. It's the default IPFS daemon (written in golang, downloaded by our installer) with our enhancements to use it at public VPS nodes.  We might switch to js-ipfs at some point. But go-ipfs offers more at this stage, like publishing hashes for DNS.\n\nSo yes, it looks like my assumptions are correct. In order for Shift to have mass adoption by the current IPFS network they will have to merge code or coordinate together.\n\n4\\. Do those delegates even have the CPU power to handle every transaction on the network?\n> Today the network can handle large amounts of transactions. We could look back how much txs it handled well, when we tested broadcasting a huge amount per block. Do you still have some numbers from your tests @mq?\n\n@mq responds: \n> regarding transactions - currently network can process 25 transactions per block (hard-coded limit) and 1k transactions waiting in queue and network is stable under such load\n> however transaction processing will be rewritten soon\n\nI ask:\n> How long does it take to process 1 block\n\n@mq:\n> on average less that 1 second\n\nHonestly I don't know what to make of this, and can only assume \"this is ok\".\n\n## Final words\nShift has great potiental, but *if and only if* they team up with IPFS. Creating a tight integration with this software is essential to its success. Sia has shown that already, displaying great all-around efficiency.\n\nThis article is brought to you buy http://currypto.club, a premium information service in regards to cryptocurrencies.\n\nLike it? Consider supporting me here on Steemit or there, where I will accept $10 USD in STEEM or any other Poloniex supported currency.",
      "json_metadata": "{\"tags\":[\"currypto\",\"ipfs\",\"shift\",\"sia\"],\"image\":[\"https://steemitimages.com/DQmRvmUkBjtAJWMacWKfEviPUBmG9gySmaj341vVxJVQU1n/image.png\",\"https://steemitimages.com/DQmbVGzMSST4YkxwR94shZsrS2J5rBshioDcAjSFGAAiVaP/image.png\",\"https://steemitimages.com/DQmSVKP7PbZXKpLHbz49h1DWSKoNVGrdSBFgZxKoGVqJNbQ/image.png\"],\"links\":[\"http://currypto.club\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}",
      "parent_author": "",
      "parent_permlink": "currypto",
      "permlink": "shift-an-ipfs-based-cryptocurrency",
      "title": "Shift - An IPFS-based Cryptocurrency"
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-08-02T01:32:06",
  "trx_id": "a5dbc78e1d35c2eab4571ee26dd2520e640b2116",
  "trx_in_block": 15,
  "virtual_op": 0
}

{
  "block": 12963098,
  "op": [
    "account_create_with_delegation",
    {
      "active": {
        "account_auths": [],
        "key_auths": [
          [
            "STM7ZFRB8U2tASkNA38rG5Gatus2pT97z2JHCt5EGoScbLyzoHu9T",
            1
          ]
        ],
        "weight_threshold": 1
      },
      "creator": "steem",
      "delegation": "57000.000000 VESTS",
      "extensions": [],
      "fee": "0.500 STEEM",
      "json_metadata": "",
      "memo_key": "STM8bXnj1VLZcG9XrSjB7mH9UhBVEYNjRGD79uh1NCpgeNRUjtwHb",
      "new_account_name": "currypto",
      "owner": {
        "account_auths": [],
        "key_auths": [
          [
            "STM5rGcKncjXjfjgiZFUKzdD7q4juiC75saop1JJJg9D4zvYWVgGy",
            1
          ]
        ],
        "weight_threshold": 1
      },
      "posting": {
        "account_auths": [],
        "key_auths": [
          [
            "STM7RVgCwNwCYTHn8g8xAEy7ercdjk8DTwUYYsYL9CmRzA9kXK5FB",
            1
          ]
        ],
        "weight_threshold": 1
      }
    }
  ],
  "op_in_trx": 0,
  "timestamp": "2017-06-19T17:25:15",
  "trx_id": "5c17489c7287995b3a643ba34d65fa925b902d61",
  "trx_in_block": 12,
  "virtual_op": 0
}