{
  "trx_id": "63adf24d09a4c8f4448282583607665848310aeb",
  "block": 106144676,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2026-05-18T01:16:54",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "hydrogenapi",
      "vesting_shares": "7940.256944 VESTS"
    }
  ]
}

{
  "trx_id": "6ccd8cac17a579b93c9413d84f57f9142e9e90e0",
  "block": 105980712,
  "trx_in_block": 5,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2026-05-12T08:01:00",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "hydrogenapi",
      "vesting_shares": "5228.046539 VESTS"
    }
  ]
}

{
  "trx_id": "3a95e606c105450e24022677c2749be049ab103d",
  "block": 105512297,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2026-04-26T00:36:03",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "hydrogenapi",
      "vesting_shares": "7952.772700 VESTS"
    }
  ]
}

{
  "trx_id": "11ae0d7b90c880e59afcd759996ab4844bf86d3f",
  "block": 102855126,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2026-01-23T10:34:00",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "hydrogenapi",
      "vesting_shares": "5269.593358 VESTS"
    }
  ]
}

{
  "trx_id": "3db3d7fc7432062e688862cadbe55d006ad46db8",
  "block": 91301493,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2024-12-17T05:51:27",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "hydrogenapi",
      "vesting_shares": "5433.812555 VESTS"
    }
  ]
}

{
  "trx_id": "9f6e92ba1f2b8537a6ec308ac4ab9e662ba94a40",
  "block": 79855682,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2023-11-13T21:33:45",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "hydrogenapi",
      "vesting_shares": "5602.946087 VESTS"
    }
  ]
}

{
  "trx_id": "426b977d7ba43725b46d77cd1ee45efa2cbe704e",
  "block": 78349282,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2023-09-21T23:02:39",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "hydrogenapi",
      "vesting_shares": "8540.224873 VESTS"
    }
  ]
}

{
  "trx_id": "48c759c36a324c8e23c0c0450edc71af776f1222",
  "block": 69114426,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-11-03T12:40:45",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "hydrogenapi",
      "vesting_shares": "8761.906311 VESTS"
    }
  ]
}

{
  "trx_id": "dcf15d97e506fe6f1e7fdc74681f374841e74bcf",
  "block": 60810498,
  "trx_in_block": 7,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-01-17T11:51:51",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "hydrogenapi",
      "vesting_shares": "8982.439542 VESTS"
    }
  ]
}

{
  "trx_id": "e9c8956007fa5542985f6567a0f4742547ee0a68",
  "block": 54608831,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-06-14T01:44:30",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "hydrogenapi",
      "vesting_shares": "9166.208200 VESTS"
    }
  ]
}

{
  "trx_id": "24c9cb5bc96a9ca6965b988b5e045c3046b16a29",
  "block": 49356244,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-12-11T12:01:45",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "hydrogenapi",
      "vesting_shares": "9353.630174 VESTS"
    }
  ]
}

{
  "trx_id": "906cf985b8ea45b1754a746c636bae21b25f64cb",
  "block": 49207806,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-12-06T05:38:57",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "hydrogenapi",
      "vesting_shares": "1912.543513 VESTS"
    }
  ]
}

{
  "trx_id": "b2cdface8c1343451c6c18a8ad6ce0d8866b3f7b",
  "block": 49191341,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-12-05T15:39:48",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "hydrogenapi",
      "vesting_shares": "9359.838028 VESTS"
    }
  ]
}

{
  "trx_id": "bfb1a6be1d60a2f9a02eedcbb540825c5517922e",
  "block": 48259981,
  "trx_in_block": 6,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-11-02T17:29:21",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "hydrogenapi",
      "vesting_shares": "1920.017158 VESTS"
    }
  ]
}

{
  "trx_id": "11012636276f1decfad2a149a046665c0e676a5a",
  "block": 43218068,
  "trx_in_block": 21,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-05-09T06:37:06",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "hydrogenapi",
      "vesting_shares": "9562.643387 VESTS"
    }
  ]
}

{
  "trx_id": "0b63edf188b2ab67ef21568c54b591e6c50cdd87",
  "block": 43194325,
  "trx_in_block": 18,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-05-08T10:21:36",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "hydrogenapi",
      "vesting_shares": "1953.311140 VESTS"
    }
  ]
}

{
  "trx_id": "a8a780a34e10ad03db989adbe85760162d1bb978",
  "block": 36167308,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-09-05T21:59:30",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "hydrogenapi",
      "vesting_shares": "9702.690786 VESTS"
    }
  ]
}

{
  "trx_id": "d4ba0b1dedd8d094cc232b4602f44581a83e6cb5",
  "block": 34053857,
  "trx_in_block": 8,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-06-23T15:03:36",
  "op": [
    "vote",
    {
      "voter": "cryptoly",
      "author": "hydrogenapi",
      "permlink": "project-hydro-features-in-depth-look",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "2b78525a36d83b7da62c8155ee07894b281ee116",
  "block": 33188860,
  "trx_in_block": 7,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-05-24T13:14:06",
  "op": [
    "comment",
    {
      "parent_author": "hydrogenapi",
      "parent_permlink": "hydro-weekly-update-6-22-18",
      "author": "steemitboard",
      "permlink": "steemitboard-notify-hydrogenapi-20190524t131406000z",
      "title": "",
      "body": "Congratulations @hydrogenapi! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@hydrogenapi/birthday1.png</td><td>Happy Birthday! - You are on the Steem blockchain for 1 year!</td></tr></table>\n\n<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@hydrogenapi) and compare to others on the [Steem Ranking](http://steemitboard.com/ranking/index.php?name=hydrogenapi)_</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\"]}"
    }
  ]
}

{
  "trx_id": "4d7346236aed980054cb5e2e353a8fed4d9b7514",
  "block": 26231591,
  "trx_in_block": 20,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-09-24T18:00:33",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "hydrogenapi",
      "vesting_shares": "9900.818516 VESTS"
    }
  ]
}

{
  "trx_id": "1216db4a39aa77a8d55b9d9d64af791d6eb52ada",
  "block": 24052975,
  "trx_in_block": 16,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-07-10T12:15:03",
  "op": [
    "vote",
    {
      "voter": "manimit",
      "author": "hydrogenapi",
      "permlink": "ion-weekly-update-6-19-18",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "d41a0cfcbf876941c1eda9551b126dfcfdf80a79",
  "block": 23637355,
  "trx_in_block": 15,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-25T17:33:36",
  "op": [
    "vote",
    {
      "voter": "youngogmarqs",
      "author": "hydrogenapi",
      "permlink": "ion-weekly-update-6-19-18",
      "weight": 2
    }
  ]
}

{
  "trx_id": "32dda573894b277d50e1d049735e19918114dae9",
  "block": 23636641,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-25T16:57:51",
  "op": [
    "vote",
    {
      "voter": "shahjad5974",
      "author": "hydrogenapi",
      "permlink": "hydro-weekly-update-6-22-18",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "1fe885e5aab358890786d7aaca154845c340915d",
  "block": 23636587,
  "trx_in_block": 14,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-25T16:55:09",
  "op": [
    "comment",
    {
      "parent_author": "hydrogenapi",
      "parent_permlink": "hydro-weekly-update-6-22-18",
      "author": "biblegateway",
      "permlink": "re-hydrogenapi-hydro-weekly-update-6-22-18-20180625t165508878z",
      "title": "",
      "body": "# Breaking: https://steemit.com/news/@bible.com/6h36cq",
      "json_metadata": "{\"tags\":[\"bitcoin\"],\"links\":[\"https://steemit.com/news/@bible.com/6h36cq\"],\"app\":\"steemit/0.1\"}"
    }
  ]
}

{
  "trx_id": "3dd2cbe2ee0d5bdd6d5c3f85e744cde163b24274",
  "block": 23636575,
  "trx_in_block": 37,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-25T16:54:33",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "bitcoin",
      "author": "hydrogenapi",
      "permlink": "hydro-weekly-update-6-22-18",
      "title": "Hydro Weekly Update: 6/22/18",
      "body": "<html>\n<p><img src=\"https://cdn-images-1.medium.com/max/800/1*l28hR29RCQlf5EXspE9juA.jpeg\" width=\"800\" height=\"531\"/></p>\n<p>Happy first few days of summer! Here is what we have been working on:</p>\n<ol>\n  <li><strong>Finalizing Snowflake resolvers.</strong> As <a href=\"https://medium.com/@NoahHydro\">Noah</a> talked about in <a href=\"https://medium.com/hydrogen-api/hydro-dev-update-6-15-74c8db2e509b\">last week’s update</a>, resolvers are crucial to the infrastructure of Snowflake. We have finalized three resolvers which we plan to release with the launch of Snowflake. These three resolvers can be seen on <a href=\"https://github.com/hydrogen-dev/smart-contracts/tree/master/snowflake-poc/contracts/resolvers\">GitHub</a>. They handle account ownership, community reputation, and user KYC (know-your-customer). We are also excited to see resolvers developed by the community — there are nearly endless possibilities for useful resolvers. Expect to see some example resolver specs in the HCDP in the near future.</li>\n  <li><strong>Adding tests to Snowflake.</strong> After finalizing our Snowflake resolvers, we felt we were in a good place to make sure that everything is working properly. Noah and I added a large suite of tests to the Snowflake truffle library over the week. We would like to encourage developers out there to take a look at our tests and see if they can find bugs or issues. We intend to be releasing a bug program for Snowflake via the HCDP soon as well.</li>\n  <li><strong>Assessing API vulnerabilities.</strong> Using <a href=\"https://www.sonarqube.org/\">SonarQube</a>, we ran scans of our code base and we very pleased with the results. We found no severe bugs or vulnerabilities. I went through the API and handled the “code smells” that were reported from SonarQube. We plan on running more tests of this nature and static code analysis from other providers going forward.</li>\n  <li><strong>Fixing an issue with multiple transactions in one block on Infura.</strong>While testing our Hydro API, we encountered an unexpected issue with Infura. When handling a high volume of transactions, the API often sends multiple transactions in the same block. Since Infura uses load balancing on their nodes, we ran into scenarios where a node was unaware of pending transactions and would overwrite the nonce of the pending transaction. We worked through several solutions to this and finally decided that the best decision is to move away from Infura. We are now hosting with <a href=\"https://quiknode.io/\">QuikNode</a> and using Infura as a backup.</li>\n</ol>\n<p>Feel free to shoot us messages about any of this stuff, or really anything! We are excited to get the community more involved with Snowflake in the coming weeks as we get closer to launch.<em>We’d love to hear from you! Please get in touch via</em> <a href=\"https://discord.gg/VR6uQRn\"><em>Discord</em></a><em>,</em> <a href=\"http://www.reddit.com/r/projecthydro\"><em>Reddit</em></a><em>, or</em> <a href=\"https://t.me/joinchat/IMnWCE7MpLpRzxFC1L3O-g\"><em>Telegram</em></a><em>.</em></p>\n</html>",
      "json_metadata": "{\"tags\":[\"bitcoin\",\"blockchain\",\"ethereum\",\"devleoper\",\"erc20\"],\"image\":[\"https://cdn-images-1.medium.com/max/800/1*l28hR29RCQlf5EXspE9juA.jpeg\"],\"links\":[\"https://medium.com/@NoahHydro\",\"https://medium.com/hydrogen-api/hydro-dev-update-6-15-74c8db2e509b\",\"https://github.com/hydrogen-dev/smart-contracts/tree/master/snowflake-poc/contracts/resolvers\",\"https://www.sonarqube.org/\",\"https://quiknode.io/\",\"https://discord.gg/VR6uQRn\",\"http://www.reddit.com/r/projecthydro\",\"https://t.me/joinchat/IMnWCE7MpLpRzxFC1L3O-g\"],\"app\":\"steemit/0.1\",\"format\":\"html\"}"
    }
  ]
}

{
  "trx_id": "6f5fbae3803bef4f4150d6707ed56ed0b9c1d58a",
  "block": 23636466,
  "trx_in_block": 37,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-25T16:49:06",
  "op": [
    "comment",
    {
      "parent_author": "hydrogenapi",
      "parent_permlink": "ion-weekly-update-6-19-18",
      "author": "a-0-1",
      "permlink": "re-hydrogenapi-ion-weekly-update-6-19-18-20180625t164907552z",
      "title": "",
      "body": "# Breaking: https://steemit.com/news/@bible.com/6h36cq",
      "json_metadata": "{\"tags\":[\"datascience\"],\"links\":[\"https://steemit.com/news/@bible.com/6h36cq\"],\"app\":\"steemit/0.1\"}"
    }
  ]
}

{
  "trx_id": "1eca691e568ce6477018d16824dc79c578fb18da",
  "block": 23636464,
  "trx_in_block": 47,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-25T16:49:00",
  "op": [
    "vote",
    {
      "voter": "rakesh.raj.ace",
      "author": "hydrogenapi",
      "permlink": "ion-weekly-update-6-19-18",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "a30dfe9daa58242bcf2ff5c1835e2fe3ac4b9ba1",
  "block": 23636454,
  "trx_in_block": 11,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-25T16:48:30",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "datascience",
      "author": "hydrogenapi",
      "permlink": "ion-weekly-update-6-19-18",
      "title": "Ion Weekly Update: 6/19/18",
      "body": "<html>\n<p><img src=\"https://cdn-images-1.medium.com/max/800/1*eWYm3Dm7s0t8lLWYRW4pow.jpeg\" width=\"800\" height=\"599\"/></p>\n<p>Welcome to the first official update from the Ion team!Ion is an AutoML API that has been in development since 2017. It leverages open-source machine learning packages and customized hyper-parameter optimization algorithms to find the machine learning pipeline with the best fit for your data. Currently, the API optimizes machine learning pipelines from H2O.ai and scikit-learn, with Spark ML and others coming soon.Additional things we’ll be working on include:</p>\n<ul>\n  <li>Automated feature extraction capabilities</li>\n  <li>Hyper-parameter optimization and AutoML for time-series models</li>\n  <li>Support for more complex modeling techniques such as Neural Networks and Bayesian modeling</li>\n  <li><em>Ionized</em> products, which are AutoML products built with Ion to solve specific machine learning problems</li>\n</ul>\n<p>Ion is currently in <strong>beta</strong>.&nbsp;</p>\n<p><em>We’d love to hear from you! Please get in touch via</em> <a href=\"https://discord.gg/VR6uQRn\"><em>Discord</em></a><em>,</em> <a href=\"http://www.reddit.com/r/projecthydro\"><em>Reddit</em></a><em>, or</em> <a href=\"https://t.me/joinchat/IMnWCE7MpLpRzxFC1L3O-g\"><em>Telegram</em></a><em>.</em></p>\n</html>",
      "json_metadata": "{\"tags\":[\"datascience\",\"bigdata\",\"data\",\"ai\",\"machinelearning\"],\"image\":[\"https://cdn-images-1.medium.com/max/800/1*eWYm3Dm7s0t8lLWYRW4pow.jpeg\"],\"links\":[\"https://discord.gg/VR6uQRn\",\"http://www.reddit.com/r/projecthydro\",\"https://t.me/joinchat/IMnWCE7MpLpRzxFC1L3O-g\"],\"app\":\"steemit/0.1\",\"format\":\"html\"}"
    }
  ]
}

{
  "trx_id": "2cd304c34045c6640ade2d7ae97c85fffdc2093f",
  "block": 23547946,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-22T15:02:27",
  "op": [
    "vote",
    {
      "voter": "ubg",
      "author": "hydrogenapi",
      "permlink": "we-are-currently-looking-for-pilot-users-to-implement-client-raindrop",
      "weight": 100
    }
  ]
}

{
  "trx_id": "c8512a198ab163d5004f3a0451e023fbc22c26ab",
  "block": 23547168,
  "trx_in_block": 21,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-22T14:23:33",
  "op": [
    "vote",
    {
      "voter": "bilal089",
      "author": "hydrogenapi",
      "permlink": "we-are-currently-looking-for-pilot-users-to-implement-client-raindrop",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "3adb513c74ccf47f25390b14b2887bf7c13d6e95",
  "block": 23547155,
  "trx_in_block": 46,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-22T14:22:54",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "blockchain",
      "author": "hydrogenapi",
      "permlink": "we-are-currently-looking-for-pilot-users-to-implement-client-raindrop",
      "title": "We are currently looking for pilot users to implement Client Raindrop!",
      "body": "<html>\n<p>https://cdn.steemitimages.com/DQmZFEEcFtiDQFYCNqWpkmYvBvYzyfRQFtwiPyrijDq6Li9/Facebook.png</p>\n<p><br></p>\n<p>We are currently looking for pilot users to implement Client Raindrop, if you have a web platform or know someone that does, send us an email to [email protected]! Those who join our pilot program by <strong>June 30th</strong> will be included in our launch press strategy.</p>\n<p><br></p>\n<p>Watch our Client raindrop Demo to learn more: https://www.youtube.com/watch?v=Q9nKb9nTjZU</p>\n<p>and to learn about our project visit our <a href=\"https://www.hydrogenplatform.com/hydro\">website</a> and view our <a href=\"https://github.com/hydrogen-dev/hydro-docs/blob/master/Raindrop/Raindrop.md\">white paper&nbsp;</a></p>\n</html>",
      "json_metadata": "{\"tags\":[\"blockchain\",\"bitcoin\",\"crypto\",\"webdev\",\"ethereum\"],\"image\":[\"https://cdn.steemitimages.com/DQmZFEEcFtiDQFYCNqWpkmYvBvYzyfRQFtwiPyrijDq6Li9/Facebook.png\",\"https://img.youtube.com/vi/Q9nKb9nTjZU/0.jpg\"],\"links\":[\"https://www.youtube.com/watch?v=Q9nKb9nTjZU\",\"https://www.hydrogenplatform.com/hydro\",\"https://github.com/hydrogen-dev/hydro-docs/blob/master/Raindrop/Raindrop.md\"],\"app\":\"steemit/0.1\",\"format\":\"html\"}"
    }
  ]
}

{
  "trx_id": "18690d5a207e15024eb78df9c0f6bb341c68520a",
  "block": 23524385,
  "trx_in_block": 20,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-21T19:24:18",
  "op": [
    "vote",
    {
      "voter": "aarauz",
      "author": "hydrogenapi",
      "permlink": "hydro-dev-update-6-15",
      "weight": 1200
    }
  ]
}

{
  "trx_id": "261e8a7dc3512cc5f5eab082f1db59034219e6bf",
  "block": 23524207,
  "trx_in_block": 32,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-21T19:15:24",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "blockchain",
      "author": "hydrogenapi",
      "permlink": "hydro-dev-update-6-15",
      "title": "Hydro Dev Update 6/15",
      "body": "<html>\n<p><img src=\"https://cdn-images-1.medium.com/max/800/1*P40hgkStX9v2oWoiOhjXzA.jpeg\" width=\"800\" height=\"531\"/></p>\n<p>Hi everyone! We’ve been pursuing a lot of projects this past week:</p>\n<ol>\n  <li><strong>Integrating QR codes into Client Raindrop.</strong> We’re excited about the possibility of adding QR code functionality into our mobile app, SDKs, and implementation guides for Client-Side Raindrop, our blockchain-based MFA solution. We’re even considering using <a href=\"https://medium.com/@branchmetrics\">Branch Metrics</a> or a similar service to go above and beyond typical QR code functionality, and offer native deep linking. Briefly, deep linking allows QR codes to intelligently route users to the correct destination depending on their environment. For example, scanning the code on a mobile device might take existing users directly to our mobile app, whereas new users would be directed to the appropriate app store.</li>\n  <li><strong>Building out Snowflake resolvers.</strong> Resolvers are at the core of our identity protocol. They’re third-party DApps which implement a shared interface, allowing them to seamlessly manage user accounts with Snowflake! <a href=\"https://medium.com/@HydroAndy\">Andy </a>and I have both spent a lot of time developing DApps at work and in our free time, so we’re pretty well-versed in the landscape, and feel very confident in our ability to construct a robust, dev-friendly framework. Current and aspiring DApp developers: look out for resources on how to integrate your smart contracts with Snowflake soon!</li>\n  <li><strong>Revamping our web wallet.</strong> We’re building a wrapper for MetaMask that provides a lot of Hydro functionality above and beyond the basic interface. We’ll be rolling this out on our developer portal soon. It’s been fun to take a break from backend work and implement a wallet UI in Javascript! We’ll be open-sourcing this code soon.</li>\n</ol>\n<p>Thanks for reading, until next week!<em>We’d love to hear from you! Please get in touch via</em> <a href=\"https://discord.gg/VR6uQRn\"><em>Discord</em></a><em>,</em> <a href=\"http://www.reddit.com/r/projecthydro\"><em>Reddit</em></a><em>, or</em> <a href=\"https://t.me/joinchat/IMnWCE7MpLpRzxFC1L3O-g\"><em>Telegram</em></a><em>.</em></p>\n</html>",
      "json_metadata": "{\"tags\":[\"blockchain\",\"developers\",\"update\",\"bitcoin\",\"ethereum\"],\"image\":[\"https://cdn-images-1.medium.com/max/800/1*P40hgkStX9v2oWoiOhjXzA.jpeg\"],\"links\":[\"https://medium.com/@branchmetrics\",\"https://medium.com/@HydroAndy\",\"https://discord.gg/VR6uQRn\",\"http://www.reddit.com/r/projecthydro\",\"https://t.me/joinchat/IMnWCE7MpLpRzxFC1L3O-g\"],\"app\":\"steemit/0.1\",\"format\":\"html\"}"
    }
  ]
}

{
  "trx_id": "f0d84eb0b7af62e2142260b8cd6bfc8d72949563",
  "block": 23523840,
  "trx_in_block": 12,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-21T18:57:03",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "blockchain",
      "author": "hydrogenapi",
      "permlink": "hydro-x-bcm-ama-recap",
      "title": "Hydro x BCM AMA Recap",
      "body": "<html>\n<p><img src=\"https://cdn-images-1.medium.com/max/800/1*Y9dvjm5bPha402i2wEKHOg.png\" width=\"800\" height=\"426\"/></p>\n<p>The Bitcoin Markets slack channel hosted <a href=\"https://medium.com/@anuragangara\">Anurag</a>, <a href=\"https://medium.com/@shane_hydrogen\">Shane</a>, <a href=\"https://medium.com/@NoahHydro\">Noah</a>, <a href=\"https://medium.com/@nyemane1\">Nahom</a>, and me for their first AMA yesterday. As in our previous AMA, we received a lot of important and insightful questions! For those who were unable to participate, here is a recap of the questions and answers. Thank you again to Bitcoin Markets for hosting us, and to our awesome community!</p>\n<p><strong>Q (khonsu):</strong> How does Snowflake relate to other identity protocols out there like Civic and uPort?</p>\n<p><strong>A.1 (Anurag):</strong> We see snowflake existing as a layer below these types of projects. Even without blockchain, identity is a broad term. Different people around the world have different forms of identity (state ID, country ID, social media IDs, etc). Civic, uPort, and other blockchain projects help to build specific types of an on-chain identity for a user; however those IDs are meaningful in different ways to different observers. For instance, imagine that a government or business builds a system that accepts Civic as a form of identity while another government/business only recognizes uPort identities. On top of this, certain systems only care about information tied to a user’s social media profile. A user can maintain one standard Snowflake as a base layer and set each of these different forms of identity as a resolver. Snowflake eliminates the need for global unanimous adoption of a singular identity standard and rather allows systems to build business logic off of identity standards they themselves recognize.</p>\n<p><strong>Follow up Q (khonsu):</strong> thats cool. so its totally depends on the person/ institute utilizing it&nbsp;. One problem I found is how easy its to create fake identities (in their basic system).</p>\n<p><strong>A.2 (Anurag):</strong> Yup! So people can conduct off-chain verifications to prove that you own a snowflake, and then tie an on-chain verification to your Snowflake. This links real-world KYC to your on-chain ID, so sure you could mint another snowflake, but that same party won’t validate it again for you. Anyone who trusts that party would be able to accept their validations, and people who don’t trust that party can rely on a different validator they do trust.</p>\n<p><strong>Q (kat):</strong> How big is the team working specifically on Hydro products? Can we get a numbers breakdown of engineers, biz dev, etc? Do you have plans to scale this team as the Hydro project develops?</p>\n<p><strong>A.1 (Andy):</strong> Our Hydro team is 8 people.Devlopers (Myself and Noah)Product (Anurag and Shane)Community (Nahom)Founders (Mike and Matt)Partnerships/BizDev (Gunjan)The nice thing about Hydrogen though is we have a team of 30 people who we can leverage for different things. For example, Noah and I do not build mobile apps, but we have a front end team that is well versed in mobile app development. So while they are not directly on the Hydro team they do have a direct impact on Hydro.Hydrogen as a company is working to grow pretty rapidly. As we grow we will be filling out more positions in both blockchain and non-blockchain rolls.</p>\n<p><strong>A.2 (Anurag):</strong> To add to Andy’s answer — pretty much everyone working for Hydrogen helps out with Hydro in some way, whether via design, front-end development, API support, business discussion, etc.<a href=\"https://www.hydrogenplatform.com/about\">Here’s our full team</a></p>\n<p><strong>Q (rocket man):</strong> So in the age of ICOs, what motivated your team to not pursue that funding model and instead have a token distribution for developers?</p>\n<p><strong>A (Andy):</strong> This was something that we spent a very long time considering and discussing. We spent a lot of resources (time, money &amp; energy) trying to find the best solution for us going forward. When it was all said and done, we decided on an airdrop because of two main things, getting the token into the hands of people who will actually use it and regulatory concerns.We feel as though our distribution was the fairest approach that allowed for people with actual interest in the Hydro community to get involved. Overall, we have been very pleased with the level of community engagement from people who are interested in the utility of the Hydro token and we feel that a lot of this can be credited to our distribution strategy.</p>\n<p><strong>Q (matheussiq8):</strong> How hydro tokens will be used is still vague in the Snowflake whitepaper draft. Would the amount required to hold depend on the volume of API calls or some other parameter? For example, if I decide to implement raindrop and later snowflake in my small webshop would I need to hold the same amount of tokens as Binance (if they ever implement it of course…)?</p>\n<p><strong>A (Noah):</strong> As always, the permissionlessness of public blockchains is a double-edged sword. smart contracts partially solve the problem by letting us enforce certain things on-chain (minimum token balances, signature validity, etc.), but there are limits. So, regarding your specific question: in raindrop we do not vary the staking requirement across users, because that would necessarily involve value judgements we are not comfortable making as a centralized entity. However, there are two types of staking required for raindrop:1) “institutional staking” requires entities who wish to sign up raindrop users *on their behalf* (i.e. passing new users’ addresses to the smart contract as parameters rather than new users transacting directly from their accounts) to stake a significant amount of hydro. These are the players we want to ensure are acting in the best interests of the community. in this model, hydro is simply one of many institutional stakers (where we sign up users on our kickass mobile app, which will be out soon).2) “user staking” requires individuals who wish to sign up for raindrop on their own, i.e. transact directly with the smart contract, are able to do so by staking a much smaller amount of hydro.What this all means for you, as a potential customer of our API, is that you don’t actually have to worry about the staking requirement or signing up users at all, and can simply use our API in conjunction with the Hydro app.Looking ahead to Snowflake, we have big plans to integrate increasing sophisticated uses of the token into the product. to some extent these are still up in the air, but rest assured that we are very focused on building a strong tokenomics structure. At a high level, the core token mechanism for snowflake will involve depositing tokens into the snowflake smart contract. These deposits will allow native staking/payment/incentive functionality denominated in hydro, without the hassle and worry of using ether with every call.</p>\n<p><strong>Q (Jeff_We_Cannafi):</strong> To piggyback on matheussiq8’s question, how do these identity tokens compare to existing forms of identity authentication, and do you anticipate the tokens themselves will be traded on exchanges?<strong>A (Andy):</strong> In my opinion, the main difference between what we are working towards and others like civic and uport is the scope of what we are aiming to do. We understand the value of having KYC on the blockchain and “One click signup”, but really I think blockchain identity can be so much more than that. We are aiming to create a completely extendable and modular protocol which will allow for people to link anything they desire to their blockchain identity. Other protocols can tend to lean towards centralization (more a fault of current KYC procedures than the projects themselves) and we feel like this doesn’t have to be the case. At least for now, something like KYC needs to have central authorities to verify user information, but why can’t I also link my crypto kitties to my blockchain id or my linkedin profile to my blockchain id?Overall, what we are trying to build will easily allow for other blockchain developers to create robust identity solutions for whatever application they feel fit with Snowflake being at the core of that. We feel that this is crucial to eventually creating a completely open and decentralized identity system. Anyone can join and anyone can add what THEY consider to be an identity, but I only have to accept what I consider to be an identity.As far as trading, Snowflake Identity tokens will never be tradable. We feel that your identity should always be linked to you. This would be a dangerous road to a very easy black market for people’s identities.</p>\n<p><strong>Q (Jrock):</strong> What do you find the hardest part of pitching icos to regular companies?Also what do you think needs to happen for widespread crypto adoption?</p>\n<p><strong>A (Shane):</strong> If you mean pitching Hydro to regular companies (we’re not an ICO), I would say the hardest part is getting the larger companies to move faster than a snail’s pace. There are too many chefs in the kitchen and sometimes there is a lack of top-down strategy on blockchain, and it leaves large enterprises paralyzed sometimes. We try to resolve this by pitching how easy Hydro is to use, and how it connects to our broader Hydrogen ecosystem which can add value in a lot of places.In my opinion, widespread crypto adoption is going to be dependent on how parallelization plays out. If crypto’s only option is to create a new parallel economy, widespread adoption is going to be slow and arduous and will take decades. However, if blockchain is able to be infused or layered on some of the current systems we have in place, the adoption will be much faster and broader. Ultimately this comes down to the usage of private vs public chains— the more private and centralized chains that get implemented, the farther the mainstream adoption will get pushed out.</p>\n<p><strong>Q (Luke):</strong> One aspect of Hydro that is beginning to really intrigue me are the potential use cases and dapps that can be built by external developers ontop of the Hydro protocol layers for each phase.1) Having held various dev meetups and networking at various conferences, how are you finding the process of attracting developers to start building dapps and products in your ecosystem?2) I understand the HCDP is getting updated with various new rules and bounties for dapps to be built, have you approached any developers yet with this new offer, and if so, how has the reception been?3) How else do you intend to attract developers towards building on the Hydro protocols?</p>\n<p><strong>A (Anurag):</strong>1) Through our events, we’re mainly focused on helping expand the blockchain-focused developer community. We help give exposure to projects we find to be doing neat, innovative work in the space and keep ongoing dialogue with these communities.2) In particular, to provide impetus to developers in the Hydro ecosystem, we’ve established the HCDP. The new process will involve putting out specific task requests. In the next week or so we’ll have published specifications for dApps that can be built on top of Snowflake. We ourselves will not be building these dApps (they have nothing to do with Hydrogen’s space as a company). This helps the ecosystem expand outside of Hydrogen-specific use-cases.3) ^^Through the above process to get them started. Eventually, we want the Hydro development process to be community-driven, so people are building on Hydro because it benefits their own programs and applications.</p>\n<p><strong>Q (elmer_FUD):</strong> Hey Hydro Team! Here’s a few question I’ve got for you after checking out the Raindrop and Snowflake whitepapers:How has your experience working in the Ethereum ecosystem been so far?While you are currently focused on the financial sector, would you consider actively marketing to other sectors such as healthcare and education in the future?It seems like both Raindrop and Snowflake would be useful in any environment that processes or stores sensitive data.Do you have plans to release official Raindrop SDK packages in other languages in the future?A bit more of a specific question: Raindrop is looks like a great product to use in a PCI-DSS environment — do you have thoughts on whether or not it the product is ready for primetime and do you think the industry standards and government regulation is prepared to handle these kinds of systems?</p>\n<p><strong>A (Andy):</strong> Overall it has been pretty solid. There is still a ton of room for growth in terms of documentation and stuff like that, but it is miles ahead of basically every other blockchain platform I have worked with. By far the biggest pain has been handling gas costs when considering the user experience. When trying to build actual products that people will want to use we feel that making it user friendly is something that many blockchain projects have not focused on nearly enough.Yeah certainly. We focus on fintech as that is where the rest of our companies APIs focus and that is where we have the most connections, but much of what we are building is much further reaching than that. Just as far as authentication goes, it really can apply to any major field and we intend to market it as such.We currently have Python and JS SDKs and have had a few java ones submitted through our community dev program. We have been revamping that program, but I anticipate we will be putting up more bounties for most major languages. I have considered making a few more myself, but we feel that they could be better suited as community projects.I completely agree. Raindrop and blockchain authentication when handling anything around payments is a great application. I think the biggest thing is actually convincing regulatory bodies that the protocols we have built are secure (since many can still be scared of blockchain). I definitely see this as a direct use case though.</p>\n<p><strong>Q.1 (khonsu):</strong> What kind of banking relations do you have as a company, do they (banks) understand what you are trying to do&nbsp;? Any VCs approached you for funding&nbsp;? explain your business model.</p>\n<p><strong>A.1 (Shane):</strong> Hydrogen has existed since 2009 in the form of Hedgeable. Hedgeable is a consumer-facing online investing app, and the tech behind it eventually spawned the Hydrogen tech platform. The story of how the transition happened goes essentially like this: (1) Hedgeable was disrupting banks &amp; investing firms, (2) banks &amp; investing firms started contacting us and seeing if we would help them digitize &amp; automate their own businesses, (3) we started packaging up our tech and selling it to the banks. There was so much demand for this from financial institutions that we spun out a new company (Hydrogen).So to get back to your original question: we have some long-standing relationships in the banking &amp; finance world, and to this day we have inbound leads from that space coming in every week. The key thing to keep in mind is that these institutions move extremely slowly, but they do understand the core value prop of our platform. Many of these firms are still in the midst of basic digitization efforts (i.e. moving from really slow offline processes to simple digital infrastructure), and that is the primary thing we are helping them with in early stages. But they are also keen on blockchain tech and they will naturally turn to us for that once they reach that point. We do have a few relationships with big financial companies in which Hydro/blockchain are already part of the discussion.We have revenue and don’t need to rely on VCs. It is our general philosophy that building a business sustainably with actual clients and revenue is a good approach, but we would consider working with the right VC if that came to be and we wanted to scale more quickly. Right now, that is not an immediate concern for us.Our business model is in charging developers and enterprises to access the Hydrogen technology platform, which currently consists of products like Atom, Ion, and Hydro. Developers pay a per-user fee to hit our core APIs, while large enterprises negotiate custom (usually multi-year) contracts with us that typically include recurring revenue. Hydro, specifically, is being offered for free right now, as we attempt to gain adoption. But it is important to note that Hydro is just one piece of our ecosystem.</p>\n<p><strong>Q.2 (Joleen):</strong> When you say fee — is this fee HYDRO? And when do you envisage HYDRO to no longer be offered FOC?</p>\n<p><strong>A.2 (Shane):</strong> Sorry if it wasn’t clear, I meant free to use our Hydro tech/APIs. The usage of HYDRO tokens within that is a separate issue — they still need to have HYDRO and we do not give it away for free to clients.</p>\n<p><strong>Q (guacam0le):</strong> Adoption of an identity management solution (etc) would potentially involve a lot of identities. Further, scalability is a hot topic w/ blockchain. Is this a potential bottleneck? What is or might be done to address such?Tackling a competitor like Google or Authy’s 2FA is no small feat. Also, not everyone is yet to embrace blockchain-based solutions. Have you found it difficult to interface with enterprises &amp; get them excited about the idea of an overhaul?</p>\n<p><strong>A (Anurag):</strong> Snowflake is designed to be relatively low-load on the blockchain. A user needs to conduct a single transaction to “mint” their Snowflake. Once this is complete, they would need to complete one-time transactions to set each of their different forms of identities as resolvers as needed. A Snowflake is designed to be built out via resolvers over the duration of a user’s lifetime, so there’s never a need for heavy, frequent transactional capability. Similarly, smart contracts simply need to be set as resolvers by users; they do not themselves transact. Network scalability improvements will increase the range of use-cases for smart contracts that can be tied to Snowflake, but they aren’t a necessary prerequisite to some important early use-cases such as KYC platforms, and a few basic user-interaction platforms.As far as competition, we feel that current adoption of 2FA is, in general far short of where it should be, and any 2FA is generally better than none. Many businesses use text-message based 2FA, etc. In the short-run we are aiming toward pilot implementations with small businesses. To further this, we have put out many integration resources, guides, and documentation and accordingly believe implementation of Raindrop is a more straightforward workflow. As far as large enterprises go, Hydrogen has clients, so it is helpful for our project to have those connections. Large institutions are generally relatively slow-moving, but have expressed interest in using Raindrop, in particular for securing employee accounts. As the product grows, we may eventually move in this direction with Client Raindrop, but resources will always be available for any site that wants to adopt it. Additionally, we are looking into making a wordpress plug-in to make implementation much more accessible for many developers.</p>\n<p><strong>Q (khonsu’s mumaffi):</strong> Ill be honest i have not yet fully read the whitepaper but id like to know other than investor growth do you truly believe there is interest in a model where users have to pay each time for access? How big do u expect this fee to be…for large companies dont you believe this is an unscalable practice? This may be a question more about most technologies built on token based economics too.</p>\n<p><strong>A (Andy):</strong> So we have 2 different authentication protocols. One happens less often and is in the same vein as OAuth. This is called Server-Side Raindrop. This requires tokens to be sent. This protocol would only happen once per day for a business when accessing something like an API. I don’t feel that these values are extremely high for increased security.Our second protocol, Client-Side Raindrop, functions much more like google auth. This logic actually does not require any tokens or even a transaction by the end user. It is 100% free for them to use and they will never have to pay for a transaction. Here the responsibility is on the implementing party to stake tokens. This allows them to onboard users and authenticate them.We felt it was crucial to have an authentication that did not have a cost per user login as it is not scalable.</p>\n<p><strong>Q (ghost):</strong> As a company in the space, do you see the fact that tokens have to be acquired on exchanges as an issue? How would a company that wants to develop with you acquire tokens?</p>\n<p><strong>A (Anurag):</strong> Depends on what they’re developing. dApps developing using Hydro smart contracts to create native functionality to their applications would need to acquire those tokens on their own; however, companies using the Hydrogen API will not. <a href=\"https://medium.com/hydrogen-api/how-to-use-client-raindrop-without-using-the-hydrogen-api-bb04934ae293\">Here’s a detailed article</a> outlining when a developer would need the token for the Client Raindrop smart contract</p>\n<p><strong>Q (khonsu’s mumaffi):</strong> Also do u plan to tokenise atom and ion too and if not covered earlier how big of an impact do the market conditions have on your business</p>\n<p><strong>A (Anurag):</strong> Tough to say we’re going to “tokenize” them since that word can carry a lot of different meanings in different contexts, but we do plan on integrating the entire Hydrogen platform with Hydro. This will most likely take the form of enhancements to systems leveraging Hydro. You can find a more detailed breakdown on our <a href=\"https://medium.com/hydrogen-api/project-hydro-features-in-depth-look-39faa29f0d61\">Hydro roadmap</a>Market conditions don’t really have an impact — we’re still building the same tech on a day-to-day basis.</p>\n<p><strong>Q (jarederaj):</strong> Can you describe your stakeholders and give me a better sense of the exigency of your products? Who are you focused on serving with your platform and why are they motivated to use your platform?</p>\n<p><strong>A (Shane):</strong> The Hydrogen platform serves developers and enterprises who want to build applications. We are specifically targeting the financial services sector, including banks, investing firms, insurance providers, and financial advisors. This includes large enterprises, individual developers, and startups.Our products are Atom (core digital infrastructure &amp; engine for finserv), Ion (AutoML &amp; business intelligence capabilities), and Hydro (blockchain &amp; decentralization layer). Each has a different use case but these products combine to form an ecosystem of tools for developers to build sophisticated applications with.The main pain point we are addressing is the resources required to build, launch, and run a digital financial application. These resources include both time and money.Large enterprises have resources, but they waste years and millions of dollars trying to launch digital platforms (we’ve seen this first-hand), often unsuccessfully. The motivation here is obvious. Startups and smaller developers, on the other hand, do not have access to huge resource pools, so they are forced to look for solutions that make the process more efficient.In the same way that Wordpress makes launching a blog easy and also allows for extended functionality, Hydrogen makes launching fintech applications easy.</p>\n</html>",
      "json_metadata": "{\"tags\":[\"blockchain\",\"bitcoin\",\"ama\",\"etheruem\",\"hydro\"],\"image\":[\"https://cdn-images-1.medium.com/max/800/1*Y9dvjm5bPha402i2wEKHOg.png\"],\"links\":[\"https://medium.com/@anuragangara\",\"https://medium.com/@shane_hydrogen\",\"https://medium.com/@NoahHydro\",\"https://medium.com/@nyemane1\",\"https://www.hydrogenplatform.com/about\",\"https://medium.com/hydrogen-api/how-to-use-client-raindrop-without-using-the-hydrogen-api-bb04934ae293\",\"https://medium.com/hydrogen-api/project-hydro-features-in-depth-look-39faa29f0d61\"],\"app\":\"steemit/0.1\",\"format\":\"html\"}"
    }
  ]
}

{
  "trx_id": "dabef00c2ac5ad1574f8cda92e0069ae57c835f3",
  "block": 23489407,
  "trx_in_block": 50,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-20T14:14:36",
  "op": [
    "vote",
    {
      "voter": "shahjad5974",
      "author": "hydrogenapi",
      "permlink": "hydrogen-semi-finalist-for-the-fintech-awards-luxembourg-2018",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "a3fc8306b951af9e9f5ea035b1509b69f68e8b1e",
  "block": 23489398,
  "trx_in_block": 20,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-20T14:14:09",
  "op": [
    "vote",
    {
      "voter": "shahjad5974",
      "author": "hydrogenapi",
      "permlink": "the-new-and-improved-hydro-community-development-program",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "16dad48862a171d8f0f69c9a2c64322a8c8ebea7",
  "block": 23456864,
  "trx_in_block": 31,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-19T11:06:09",
  "op": [
    "vote",
    {
      "voter": "pahrtenope",
      "author": "hydrogenapi",
      "permlink": "the-new-and-improved-hydro-community-development-program",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "b8f22d01835dc2b09e47db00d02b2b76b5e5467f",
  "block": 23321236,
  "trx_in_block": 13,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-14T18:03:36",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "blockchain",
      "author": "hydrogenapi",
      "permlink": "the-new-and-improved-hydro-community-development-program",
      "title": "The New And Improved Hydro Community Development Program",
      "body": "<html>\n<p><img src=\"https://cdn-images-1.medium.com/max/800/1*05yf1U4rPeUsYYgLnHqv8w.png\" width=\"800\" height=\"518\"/></p>\n<p><br></p>\n<p><strong>**All submissions are now managed through the</strong> <a href=\"https://github.com/hydrogen-dev/hcdp/projects\"><strong>HCDP Github page</strong></a><strong>**</strong></p>\n<p>When we launched the Hydro Community Development Program (HCDP), we aimed to have a different and inclusive approach to community engagement. The program has been a success and — thanks to ongoing feedback from our community — we are making it even better. We are re-positioning HCDP to be more open and decentralized.Any member of the Hydro community can create HCDP tasks to be completed by others. It is the responsibility of the task creator to define the task clearly, enumerate deliverables, manage submissions, and send out HYDRO allocations upon successful completion. Members of the community will also be able to become admins to contribute more to the program over time.</p>\n<h3><strong>Program Details</strong></h3>\n<ul>\n  <li>Tasks created by the core Hydro team will account for a maximum of 10% of the total supply of HYDRO over the lifetime of the ecosystem.</li>\n  <li>Tasks will be developer centric and deliverables will normally include submission of code.</li>\n  <li>Although the Hydro team will initially be a leading task creator, over time this responsibility will be dispersed to a wide range of community members and participants.</li>\n  <li>To prevent plagiarism, once tasks are posted they will <strong>need to be claimed and submitted on time</strong>. If they are not, tasks will become re-eligible for submission from other community members.</li>\n</ul>\n<h3><strong>Tasks</strong></h3>\n<p>The tasks eligible for HCDP fall under 2 general categories: Development and Document Translations. Let’s take a look at what each entails.</p>\n<h4><strong>Development</strong></h4>\n<p>This section is dedicated to tasks regarding the expansion of the Hydro technology ecosystem internally (dealing with core Hydro code) or externally (extending or implementing Hydro code). Below are some examples of Development tasks.<em>SDKs &amp; Code Libraries</em>Code interfaces are important, as they ease the integration of Hydro into existing systems and applications. Tools like these, which enhance the usability of the Hydro ecosystem, are great outcomes for HCDP. For reference, we have released <a href=\"https://github.com/hydrogen-dev/raindrop-sdk-js\">JavaScript</a> and <a href=\"https://github.com/hydrogen-dev/raindrop-sdk-python\">Python</a> SDKs for our Raindrop products:</p>\n<p><em>Bugs &amp; Code Improvements</em></p>\n<p>Finding and diagnosing bugs is a critical part of code development. While core developers strive to ship code that is bug-free, the reality is that some edge cases may not be accounted. As more and more people implement Hydro technology, bug discovery under HCDP will play a key role in fostering a healthy ecosystem and maximizing user experience.<em>Integrations &amp; Expansions</em>While SDKs and Code Libraries facilitate processes within the Hydro ecosystem, integrations and expansions broaden the ecosystem as a whole. An example of this might be a wrapper that connects Hydro smart contracts to systems. For example, <a href=\"https://github.com/rm-gthb/hydroapi.net\">this C# wrapper </a>was created by a community member.</p>\n<p><em>Security Reports</em></p>\n<p>HCDP can also include security reports and audits. Since Hydro is integrated into systems that may hold or transmit sensitive data, vulnerabilities can be catastrophic. Whenever new Hydro code is released, security analyses are instrumental in shoring up any potential holes — the more eyes on the code, the better it will be for the entire community. A good example of a security report would be a smart contract audit.</p>\n<p><strong>Document Translation</strong></p>\n<p>This section will be dedicated to community members who prefer to read our materials in their native language. Hydro strives to make it seamless for developers to incorporate blockchain into their apps, and in order to achieve that goal we need to eliminate as many barriers as possible. Language is a key barrier to be addressed, especially for our community since it spans dozens of countries around the world. HCDP task creator can call on the community to help make documents easier to read, which in turn helps more and more people leverage the Hydro ecosystem. Some examples of documents are:</p>\n<ul>\n  <li>White papers</li>\n  <li>Tweets</li>\n  <li>Blog posts</li>\n  <li>Video transcripts</li>\n</ul>\n<p>We hope that community members will also form sub-communities that can more easily communicate in various native languages! <strong>All submissions must be made on the HCDP</strong> <a href=\"https://github.com/hydrogen-dev/hcdp/projects\"><strong>Github page</strong></a><strong>.</strong> We’re excited for this evolution of the Hydro community, and we can’t wait to work with developers, product managers, and others in the coming months!</p>\n<p><em>For those interested, the original HCDP post is available</em> <a href=\"https://medium.com/hydrogen-api/introducing-the-hydro-community-development-program-d774909c67b8\"><em>here</em></a><em>.</em></p>\n</html>",
      "json_metadata": "{\"tags\":[\"blockchain\",\"api\",\"developer\",\"crypto\",\"ethereum\"],\"image\":[\"https://cdn-images-1.medium.com/max/800/1*05yf1U4rPeUsYYgLnHqv8w.png\"],\"links\":[\"https://github.com/hydrogen-dev/hcdp/projects\",\"https://github.com/hydrogen-dev/raindrop-sdk-js\",\"https://github.com/hydrogen-dev/raindrop-sdk-python\",\"https://github.com/rm-gthb/hydroapi.net\",\"https://medium.com/hydrogen-api/introducing-the-hydro-community-development-program-d774909c67b8\"],\"app\":\"steemit/0.1\",\"format\":\"html\"}"
    }
  ]
}

{
  "trx_id": "fbee49c20703404b636022081fc41798cf17c79b",
  "block": 23320935,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-14T17:48:33",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "blockchain",
      "author": "hydrogenapi",
      "permlink": "hydrogen-semi-finalist-for-the-fintech-awards-luxembourg-2018",
      "title": "Hydrogen Semi-Finalist For The FinTech Awards Luxembourg 2018!",
      "body": "<html>\n<p><img src=\"https://cdn-images-1.medium.com/max/800/1*8epG-DIos-VY8m-7W8hZCQ.png\" width=\"450\" height=\"236\"/></p>\n<p>We are excited to announce our Co-Founder Mike will be in Luxembourg June 20th to present Hydrogen at the FinTech Awards Luxembourg 2018! This prestigious event drew 167 entries from 46 countries, with Hydrogen one of the final 15 selected to compete for the grand prize.Congrats to the other semi-finalists! Mike looks forward to meeting Prime Minister Bettei and all of the other VIPs at the event.</p>\n<p><a href=\"https://www.fintechawards.lu/\"><strong>Fintech Awards Luxembourg</strong></a><br>\n<a href=\"https://www.fintechawards.lu/\"><em>Grand Final on 20 June - We unearth outstanding Fintech startups from around the world, and introduce them to potential…</em>www.fintechawards.lu</a><br>\n</p>\n</html>",
      "json_metadata": "{\"tags\":[\"blockchain\",\"conference\",\"crypto\",\"ethereum\",\"awards\"],\"image\":[\"https://cdn-images-1.medium.com/max/800/1*8epG-DIos-VY8m-7W8hZCQ.png\"],\"links\":[\"https://www.fintechawards.lu/\"],\"app\":\"steemit/0.1\",\"format\":\"html\"}"
    }
  ]
}

{
  "trx_id": "f5a20fc9ddf3356310e3201a24ff766658a32c8a",
  "block": 23230516,
  "trx_in_block": 58,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-11T14:13:24",
  "op": [
    "vote",
    {
      "voter": "deadtrack",
      "author": "hydrogenapi",
      "permlink": "introducing-the-hydro-community-development-program",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "eca305a76a28933892b77cea662dc18b7115569d",
  "block": 23230516,
  "trx_in_block": 10,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-11T14:13:24",
  "op": [
    "vote",
    {
      "voter": "deadtrack",
      "author": "hydrogenapi",
      "permlink": "project-hydro-features-in-depth-look",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "1d8b6ed21c91fdfedd5e94d2b0fc3346cb6e7a21",
  "block": 23230515,
  "trx_in_block": 12,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-11T14:13:21",
  "op": [
    "vote",
    {
      "voter": "deadtrack",
      "author": "hydrogenapi",
      "permlink": "first-look-hydro-snowflake",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "e7cadfd7d49b36e243f7fc949e2174e81bb8845b",
  "block": 23230513,
  "trx_in_block": 23,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-11T14:13:15",
  "op": [
    "vote",
    {
      "voter": "deadtrack",
      "author": "hydrogenapi",
      "permlink": "hydro-dev-update-5-25",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "59e89a1ea3d5a5756cb090781c8ab18d531ed97e",
  "block": 23230511,
  "trx_in_block": 24,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-11T14:13:09",
  "op": [
    "vote",
    {
      "voter": "deadtrack",
      "author": "hydrogenapi",
      "permlink": "examining-hydro-token-dynamics",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "bec561adeeb9ba938547a8c0c86b8057fa7b4df9",
  "block": 23230510,
  "trx_in_block": 15,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-11T14:13:06",
  "op": [
    "vote",
    {
      "voter": "deadtrack",
      "author": "hydrogenapi",
      "permlink": "welcome-hydrogen-client-ci-investments",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "742f30f5c6fbfc5e3038f38d1960c24899ec53e9",
  "block": 23230507,
  "trx_in_block": 11,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-11T14:12:57",
  "op": [
    "vote",
    {
      "voter": "deadtrack",
      "author": "hydrogenapi",
      "permlink": "how-to-use-client-raindrop-without-using-the-hydrogen-api",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "d91285758b526462a1e6092d06829dfd36c0bd05",
  "block": 23230506,
  "trx_in_block": 21,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-11T14:12:54",
  "op": [
    "vote",
    {
      "voter": "deadtrack",
      "author": "hydrogenapi",
      "permlink": "server-side-raindrop-walkthrough",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "604387309df1970be8999679f9a8689c8f172591",
  "block": 23230504,
  "trx_in_block": 52,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-11T14:12:48",
  "op": [
    "vote",
    {
      "voter": "deadtrack",
      "author": "hydrogenapi",
      "permlink": "our-co-founder-featured-on-1-podcast",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "ad077ef2fd5ae539ca4aa717aa4f86fb773d859b",
  "block": 23230490,
  "trx_in_block": 12,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-11T14:12:06",
  "op": [
    "vote",
    {
      "voter": "deadtrack",
      "author": "hydrogenapi",
      "permlink": "hydro-dev-update-6-8",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "39696dff8b670515dcc60adacfc8ccfa0d970bc1",
  "block": 23226543,
  "trx_in_block": 8,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-11T10:54:36",
  "op": [
    "vote",
    {
      "voter": "tekguzel",
      "author": "hydrogenapi",
      "permlink": "welcome-hydrogen-client-ci-investments",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "a8e42b9a3be8086f3f4fa87c298d91e83bde9bf6",
  "block": 23226541,
  "trx_in_block": 14,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-11T10:54:30",
  "op": [
    "vote",
    {
      "voter": "tekguzel",
      "author": "hydrogenapi",
      "permlink": "hydro-dev-update-6-1",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "2b5fd5ae0975532ece7039dfe1770c7e624ce4d2",
  "block": 23226540,
  "trx_in_block": 24,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-11T10:54:27",
  "op": [
    "vote",
    {
      "voter": "tekguzel",
      "author": "hydrogenapi",
      "permlink": "server-side-raindrop-walkthrough",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "890218f0cfe9f47fb3cfab17920919dfedd0723e",
  "block": 23226538,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-11T10:54:21",
  "op": [
    "vote",
    {
      "voter": "tekguzel",
      "author": "hydrogenapi",
      "permlink": "how-to-use-client-raindrop-without-using-the-hydrogen-api",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "f38964c2c0759026c297baf54332a8d9b276013a",
  "block": 23226536,
  "trx_in_block": 10,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-11T10:54:15",
  "op": [
    "vote",
    {
      "voter": "tekguzel",
      "author": "hydrogenapi",
      "permlink": "our-co-founder-featured-on-1-podcast",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "94ee3c4ed38c22e8dc5fe7ac33f3065bfbdf30c2",
  "block": 23226535,
  "trx_in_block": 33,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-11T10:54:12",
  "op": [
    "vote",
    {
      "voter": "tekguzel",
      "author": "hydrogenapi",
      "permlink": "hydro-dev-update-6-8",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "2848ef301b70ca5136a8183dd1c0d36be1f3011b",
  "block": 23163107,
  "trx_in_block": 24,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-09T05:47:03",
  "op": [
    "vote",
    {
      "voter": "developspanish",
      "author": "hydrogenapi",
      "permlink": "hydro-dev-update-6-8",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "cc9cb426eec85f1c488c30faf6ea874840821800",
  "block": 23152755,
  "trx_in_block": 26,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-08T21:09:24",
  "op": [
    "vote",
    {
      "voter": "king-clifford",
      "author": "hydrogenapi",
      "permlink": "hydro-dev-update-6-8",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "41b46b7f119dce09526e3774a5277c4b3a43fd43",
  "block": 23152743,
  "trx_in_block": 9,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-08T21:08:48",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "ethereum",
      "author": "hydrogenapi",
      "permlink": "hydro-dev-update-6-8",
      "title": "Hydro Dev Update 6/8",
      "body": "<html>\n<p><img src=\"https://cdn-images-1.medium.com/max/800/1*l28hR29RCQlf5EXspE9juA.jpeg\" width=\"800\" height=\"531\"/></p>\n<p>This has been a productive week for us at Hydro. <a href=\"https://medium.com/@NoahHydro\">Noah</a> has been working on reducing gas costs in the API and making them more dynamic. The Ethereum network can have large differences in gas pricing at any given time and we will now be much more prepared for that. The API now allows for low, medium and high priority transactions. All of which have a set percentage of the current recommended gas cost. Alongside this, I am working in the API to integrate websockets. We feel that this will help to make the user experience smoother. This is still a work in progress, but will hopefully be done by our next dev update.For our smart contracts, we have finalized our core Snowflake contract and are working on building out a suite of contracts and dApps that all use Snowflake. Our Snowflake Whitepaper can be seen <a href=\"https://github.com/hydrogen-dev/hydro-docs/tree/master/Snowflake\">here</a> and our smart contract code can be seen <a href=\"https://github.com/hydrogen-dev/smart-contracts/tree/master/snowflake-poc/contracts\">here</a>. In the future, we will be adding specific resolvers that we want to see from the community and they will be listed in the HCDP.We have been running lots of user testing for our mobile app and are working hard to implement the feedback given to us. <a href=\"https://medium.com/@reyhaynes\">Reinaldo</a> has also been working to finish up the Android version of the app (which I am very excited about as an android user).</p>\n</html>",
      "json_metadata": "{\"tags\":[\"ethereum\",\"hydro\",\"blockchain\",\"developer\",\"crypto\"],\"image\":[\"https://cdn-images-1.medium.com/max/800/1*l28hR29RCQlf5EXspE9juA.jpeg\"],\"links\":[\"https://medium.com/@NoahHydro\",\"https://github.com/hydrogen-dev/hydro-docs/tree/master/Snowflake\",\"https://github.com/hydrogen-dev/smart-contracts/tree/master/snowflake-poc/contracts\",\"https://medium.com/@reyhaynes\"],\"app\":\"steemit/0.1\",\"format\":\"html\"}"
    }
  ]
}

{
  "trx_id": "6d7a72e2b013a78f3ed1277d8805f00b874220fc",
  "block": 23083131,
  "trx_in_block": 62,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-06T11:06:54",
  "op": [
    "comment",
    {
      "parent_author": "hydrogenapi",
      "parent_permlink": "our-co-founder-featured-on-1-podcast",
      "author": "steemitboard",
      "permlink": "steemitboard-notify-hydrogenapi-20180606t110656000z",
      "title": "",
      "body": "Congratulations @hydrogenapi! 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/posts.png)](http://steemitboard.com/@hydrogenapi) Award for the number of posts published\n[![](https://steemitimages.com/70x70/http://steemitboard.com/notifications/post4day.png)](http://steemitboard.com/@hydrogenapi) You published 4 posts in one day\n\n<sub>_Click on the badge to view your Board of Honor._</sub>\n<sub>_If you no longer want to receive notifications, reply to this comment with the word_ `STOP`</sub>\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\"]}"
    }
  ]
}

{
  "trx_id": "6c0d6f64981062252340032b3f6a8f7d41c9c32e",
  "block": 23064761,
  "trx_in_block": 44,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-05T19:48:15",
  "op": [
    "vote",
    {
      "voter": "bulet08",
      "author": "hydrogenapi",
      "permlink": "our-co-founder-featured-on-1-podcast",
      "weight": 5000
    }
  ]
}

{
  "trx_id": "087d90052bfed0c3f150ab35fb5e01a652e8b14d",
  "block": 23063675,
  "trx_in_block": 66,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-05T18:53:54",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "blockchain",
      "author": "hydrogenapi",
      "permlink": "our-co-founder-featured-on-1-podcast",
      "title": "Our Co-Founder Featured on #1 Podcast!",
      "body": "<html>\n<p><img src=\"https://cdn-images-1.medium.com/max/800/1*H7lPddeZv_QQhjMYDxe8CQ.png\" width=\"557\" height=\"229\"/></p>\n<p>If you are looking for an in depth and substantive discussion of the future of financial technology, blockchain, the Web 3.0 and more, be sure to check out our Co-Founder Mike’s talk this weekend with Craig Cobb.It is the #1 podcast in many markets! The link is below —</p>\n<p>https://shows.pippa.io/the-trader-cobb-crypto-podcast/mike-kane-breathing-hydrogen-into-blockchain</p>\n</html>",
      "json_metadata": "{\"tags\":[\"blockchain\",\"podcast\",\"hydro\",\"developer\",\"ethereum\"],\"image\":[\"https://cdn-images-1.medium.com/max/800/1*H7lPddeZv_QQhjMYDxe8CQ.png\"],\"links\":[\"https://shows.pippa.io/the-trader-cobb-crypto-podcast/mike-kane-breathing-hydrogen-into-blockchain\"],\"app\":\"steemit/0.1\",\"format\":\"html\"}"
    }
  ]
}

{
  "trx_id": "6d77b64405590e923c611420c308238c558f1972",
  "block": 23063491,
  "trx_in_block": 49,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-05T18:44:42",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "blockchain",
      "author": "hydrogenapi",
      "permlink": "server-side-raindrop-walkthrough",
      "title": "Server-Side Raindrop Walkthrough",
      "body": "<html>\n<p><img src=\"https://cdn-images-1.medium.com/max/800/1*v68sItdtEZgUDVRplTk6ag.png\" width=\"800\" height=\"498\"/></p>\n<p>To give people a sense of how easy it is to use Hydro products, I put together a <a href=\"https://www.youtube.com/watch?v=aRgMl6bdde8\">tutorial video explaining and demonstrating the Server-Side Raindrop authentication process from beginning to end</a>. The bullet points below contain some links and comments which will be helpful for those of you following along at home.</p>\n<p>https://www.youtube.com/watch?v=aRgMl6bdde8</p>\n<p>Server-Side Raindrop Walkthrough video</p>\n<ul>\n  <li>The screen with your Hydro API credentials can be accessed through the <a href=\"https://www.hydrogenplatform.com/login\">Hydrogen Platform Developer Portal</a>.</li>\n  <li>To install the official <a href=\"https://github.com/hydrogen-dev/raindrop-sdk-js\">Javascript SDK</a>, simply run: <code>npm install @hydrogenplatform/raindrop</code>. In the video, I also used the (optional) <a href=\"https://github.com/motdotla/dotenv\">dotenv</a> package.</li>\n  <li>The boilerplate code shown in the video is available as a <a href=\"https://gist.github.com/NoahHydro/a7e8a3af1fa00625e40ddc5c21e57b17\">Github gist</a>.</li>\n  <li>The whitelist transaction from the video can be seen <a href=\"https://rinkeby.etherscan.io/tx/0x4e4eed9dccea6342a42cda65f8e8baa37b3ae654984ceeb0da93103dfde2444c\">here</a>.</li>\n  <li>I transacted with the testnet smart contract using <a href=\"https://mycrypto.com/account\">MyCrypto</a> and <a href=\"https://metamask.io/\">MetaMask</a>. The <a href=\"https://www.hydrogenplatform.com/docs/hydro/v1/\">Hydro API Documentation</a> explains this process quite thoroughly.</li>\n  <li>Finally, the authenticate transaction can be seen <a href=\"https://rinkeby.etherscan.io/tx/0xbac609ada5ebc3bf82c809b59c99906ef682f94dd481de939b4de9c8c9584232\">here</a>.</li>\n</ul>\n</html>",
      "json_metadata": "{\"tags\":[\"blockchain\",\"api\",\"howto\",\"developer\",\"ethereum\"],\"image\":[\"https://cdn-images-1.medium.com/max/800/1*v68sItdtEZgUDVRplTk6ag.png\",\"https://img.youtube.com/vi/aRgMl6bdde8/0.jpg\"],\"links\":[\"https://www.youtube.com/watch?v=aRgMl6bdde8\",\"https://www.hydrogenplatform.com/login\",\"https://github.com/hydrogen-dev/raindrop-sdk-js\",\"https://github.com/motdotla/dotenv\",\"https://gist.github.com/NoahHydro/a7e8a3af1fa00625e40ddc5c21e57b17\",\"https://rinkeby.etherscan.io/tx/0x4e4eed9dccea6342a42cda65f8e8baa37b3ae654984ceeb0da93103dfde2444c\",\"https://mycrypto.com/account\",\"https://metamask.io/\",\"https://www.hydrogenplatform.com/docs/hydro/v1/\",\"https://rinkeby.etherscan.io/tx/0xbac609ada5ebc3bf82c809b59c99906ef682f94dd481de939b4de9c8c9584232\"],\"app\":\"steemit/0.1\",\"format\":\"html\"}"
    }
  ]
}

{
  "trx_id": "2e7be0d63a34f9a3b03201bd5e3d8ea98ee26dca",
  "block": 23063266,
  "trx_in_block": 12,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-05T18:33:27",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "blockchain",
      "author": "hydrogenapi",
      "permlink": "how-to-use-client-raindrop-without-using-the-hydrogen-api",
      "title": "How to use Client Raindrop WITHOUT using the Hydrogen API",
      "body": "<html>\n<p><img src=\"https://cdn-images-1.medium.com/max/800/1*H3p0QEe_W3_kaxYp8ArQwA.jpeg\" width=\"800\" height=\"533\"/></p>\n<p>** I have published a <a href=\"https://www.youtube.com/watch?v=sbtRkJKz64c\">video tutorial</a> that follows this blog post step-by-step**To understand this tutorial, it is important to first define some terms.</p>\n<h3>Definitions</h3>\n<p><strong>Hydrogen</strong>: a company that created a product — the Hydro API.</p>\n<p><strong>The Hydro API</strong>: an API that calls functions of Hydro smart contracts. Any other application, just like the Hydro API, can also call functions on Hydro smart contracts, either manually through sites like MyCrypto (as I will do in this tutorial), or programmatically through web3.</p>\n<p><strong>Hydro the Mobile App:</strong> This is a mobile app created by Hydrogen that connects end-users to the Hydrogen API. This creates HydroIDs for users which in turn allows them to manage their interactions with Hydro Smart Contracts. Thanks to the Hydro API, this doesn’t require any blockchain functionality native to the app itself.</p>\n<p><strong>HydroID:</strong> This is an ID generated through the Client-side Raindrop smart contract. Only one HydroID can be created for a given ethereum wallet. This ID is linked to Hydro smart contracts; for instance, when a user creates a Snowflake for personal data management, their unique, non-fungible Snowflake token is linked to their HydroID. The Hydrogen API only creates HydroIDs for wallets in the Hydro mobile app that are not currently meant to hold any funds; however, third-party applications could link HydroIDs to MetaMask wallets, native wallets, or other wallets based on the needs of their applications.</p>\n<p><strong>Hydro the decentralized project</strong>: the Hydro core team writes <a href=\"https://github.com/hydrogen-dev/smart-contracts\">smart contracts </a>that leverage the HYDRO token to add blockchain-enhanced financial services functionality to businesses. Blockchain developers around the world can freely recognize issues, make pull requests, or write their own contracts that also leverage HYDRO to bring blockchain functionality to businesses.</p>\n<p><strong>Hydro the ecosystem</strong>: This consists of developers writing and contributing to Hydro smart contracts, businesses using web3 to directly connect to Hydro smart contracts, and any and all clients these businesses serve.</p>\n<p><strong>Staking HYDRO:</strong> To ensure good actors in the HYDRO ecosystem, certain Hydro smart contracts require developers to maintain a certain balance of HYDRO. The Client Raindrop contract requires a balance of HYDRO for anyone who wants to register users. The owner of the HYDRO token contract (our team) can adjust the required amount of HYDRO staked (so we can reduce the requirement when needed based on scarcity of the token). However, this staking amount <strong>can never</strong> exceed 111,111,111 HYDRO for creating a HydroID on behalf of someone else, and 222,222 for creating a HydroID for yourself. We set this upper limit in order to maintain decentralization, so that if we control a large portion of the total supply, we can’t price out competitors. In the future, we intend to establish a decentralized ownership structure for the Owner contract, even despite its minimal power.</p>\n<h3>Scope of this&nbsp;tutorial</h3>\n<p>As part of Hydro the project, we have written a few smart contracts that leverage the HYDRO token: the server-side raindrop smart contract, the client-side raindrop smart contract, and the snowflake smart contract. We intend to write more contracts <a href=\"https://medium.com/hydrogen-api/project-hydro-features-in-depth-look-39faa29f0d61\">in accordance with our roadmap</a> to make the Hydro token even more dynamic and useful. At the core of all the smart contracts we are creating is the HydroID. The HydroID is generated through our client-raindrop smart contract and creates a permanent, secure link to a user’s wallet that connects that user to the entire Hydro ecosystem.In this tutorial, I will use the client raindrop smart contract to create a HydroID for a user that links to my personal Trust wallet. I will be doing this on the Rinkeby testnet using MyCrypto. A developer could use web3 to call the same functions I am calling and connect it to their own application. For instance, a bank who might want to make Raindrop native to their own mobile app for 2FA and use their own branding rather than making their users download a separate app, might use web3 to call these functions integrated into their own API. Alternatively, someone building a Linked-In style social media platform with native wallet functionality might want to call these functions to generate user HydroIDs that would link to those users’ snowflake non-fungible tokens. The full scope of programmatically interacting with Hydro Smart contracts is up to the imagination of the developer.</p>\n<h3>Acquiring Testnet Ether and&nbsp;Tokens</h3>\n<p>Before you can start, you will need to acquire ETH and HYDRO on the rinkeby testnet. To acquire ETH, follow the steps in this StackExchange answer:<a href=\"https://ethereum.stackexchange.com/questions/34718/how-do-i-buy-tokens-on-the-rinkeby-test-environment\"><strong>How do I \"Buy\" tokens on the Rinkeby (test) environment?</strong></a><br>\n<a href=\"https://ethereum.stackexchange.com/questions/34718/how-do-i-buy-tokens-on-the-rinkeby-test-environment\"><em>RinkedBy official faucet uses 3rd party social network to prevent malicious actors. You only need to go to this page…</em>ethereum.stackexchange.com</a></p>\n<p>Next, you will need to acquire testnet HYDRO tokens. To do this, go to the contracts page of MyCrypto:<a href=\"https://mycrypto.com/contracts/interact\"><strong>MyCrypto</strong></a><br>\n<a href=\"https://mycrypto.com/contracts/interact\"><em>MyCrypto is a free, open-source interface for interacting with the blockchain.</em>mycrypto.com</a></p>\n<p>Connect with a wallet — I just used my MetaMask wallet for this. We will be using the Rinkeby Hydro token contract, which can be found here:<a href=\"https://rinkeby.etherscan.io/address/0x4959c7f62051d6b2ed6eaed3aaee1f961b145f20#code\"><strong>Rinkeby Accounts, Address and Contracts</strong></a><br>\n<a href=\"https://rinkeby.etherscan.io/address/0x4959c7f62051d6b2ed6eaed3aaee1f961b145f20#code\"><em>Source Code Copy Find Similiar Contracts pragma solidity ^0.4.18; /** * @title Ownable * @dev The Ownable contract has…</em>rinkeby.etherscan.io</a>Leave “select existing contract” blank and instead paste the 0x4959c… address in the top left of the etherscan link into the “contract address” field. Paste the contract ABI from etherscan into the “ABI” field. Select the function getMoreTokens, set a gas limit and generate the transaction. Once complete, you should be able to view 10,000 HYDRO tokens from the 0x4959c address in your Rinkeby testnet wallet. If you are following these steps on the Ethereum Main Net, you would need to acquire the HYDRO from a third party.</p>\n<p>While we’ve set the HYDRO main net staking requirement at 222,222 HYDRO, we are keeping the Rinkeby staking requirement at 10,000 HYDRO to make it easy for developers to follow these steps and test.Note* throughout this tutorial, you will not actually <strong>use</strong> these 10,000 HYDRO. You will simply be unable to call these functions unless your wallet <em>maintains a balance</em> of 10,000 HYDRO. Thus, if you ever wanted to stop registering users, you could use your staked HYDRO for other HYDRO smart contracts or give it to other developers or a third party, or just leave them in your account.</p>\n<h3>Registering Users Through the Client-side Raindrop Smart&nbsp;Contract</h3>\n<p>Now that we’re set up, we can begin the actual process of interacting with the Client-side Raindrop Smart Contract. There are two ways to do this: you can either register your own HydroID or delegate someone else to do it on your behalf. Let’s start with the easier one — registering your own HydroID. Registering your own HydroID can be done by calling the signUpUser function of the Client-side Raindrop contract.Return to the contracts page of MyCrypto, except this time paste the Client-side Raindrop contract address starting with 0xb29…. You can find this contract at the top left of the following etherscan page. Take the ABI from here as well:<a href=\"https://rinkeby.etherscan.io/address/0xb29778Cf8abFFF8BF245b9060CD2299ADb358040#code\"><strong>Rinkeby Accounts, Address and Contracts</strong></a><br>\n<a href=\"https://rinkeby.etherscan.io/address/0xb29778Cf8abFFF8BF245b9060CD2299ADb358040#code\"><em>Source Code Copy Find Similiar Contracts pragma solidity ^0.4.23; /** * @title Ownable * @dev The Ownable contract has…</em>rinkeby.etherscan.io</a>Select the signUpDelegatedUser function, which takes the sole parameter casedUserName. Input whatever username you would like to register. Since these usernames are stored on the public blockchain, the HydrogenAPI generates random alphanumeric 7 character strings for this field; however, since I am doing this manually outside of the HydrogenAPI, I will just register a username called AnuragHydro.</p>\n<p>Here, you can see the confirmed transaction:<a href=\"https://rinkeby.etherscan.io/tx/0xae4c95811e3f5616ed3a12b5aea53082c26b5803885b5333fd7a3c0831b8cd49\"><strong>Rinkeby Transaction 0xae4c95811e3f5616ed3a12b5aea53082c26b5803885b5333fd7a3c0831b8cd49</strong></a><br>\n<a href=\"https://rinkeby.etherscan.io/tx/0xae4c95811e3f5616ed3a12b5aea53082c26b5803885b5333fd7a3c0831b8cd49\"><em>Rinkeby (ETH) detailed transaction info for 0xae4c95811e3f5616ed3a12b5aea53082c26b5803885b5333fd7a3c0831b8cd49</em>rinkeby.etherscan.io</a>Now, for the more interesting approach: registering a HydroID on behalf of another user. This will be useful for third-party applications who want to plug their users into the Hydro ecosystem. In order to register someone else as a user, you will need to collect two things from them:</p>\n<ol>\n  <li>a signed message from them — this message must be a keccak 256 hash of “Create RaindropClient Hydro Account”</li>\n  <li>their public address</li>\n</ol>\n<p>In our implementation at Hydrogen, we store a keypair on the user’s mobile device through the Hydro app. This private key signs the message and sends the signed message along with their public address to our API which creates their HydroID.For the purposes of this tutorial and going through the process manually, I will use MyCrypto’s signing functionality. Go to:<a href=\"https://mycrypto.com/sign-and-verify-message/sign\"><strong>MyCrypto</strong></a><br>\n<a href=\"https://mycrypto.com/sign-and-verify-message/sign\"><em>MyCrypto is a free, open-source interface for interacting with the blockchain.</em>mycrypto.com </a>And make sure you’ve signed in with a new and separate ethereum address for which you will be conducting a delegated signup. The public address for mine is 0x3c5… You will need to paste the hash of the message “Create RaindropClient Hydro Account” — you can obtain the hash here:<a href=\"https://emn178.github.io/online-tools/keccak_256.html\"><strong>Keccak-256 Online</strong></a><br>\n<a href=\"https://emn178.github.io/online-tools/keccak_256.html\"><em>Keccak-256 online hash function</em>emn178.github.io</a></p>\n<p>and it should come out looking like this: 96c9259001bd030923ed09cd77ac733c1f82fe843ed92337c2b3953346d5a522. Add a 0x in the front and sign the message:</p>\n<p>Once you’ve done this, the signature should appear below:</p>\n<p>You will need to collect the <a href=\"https://ethereum.stackexchange.com/questions/15766/what-does-v-r-s-in-eth-gettransactionbyhash-mean\">“r” “s” and “v” </a>from this signature. You can do this by pasting the signature into a fixed-width text editor (I use atom) and following these steps:</p>\n<ol>\n  <li>remove the 0x from the start</li>\n  <li>split the resulting string into three lines. Make sure the last line is 2 characters long, and the first and second lines are of equal length.</li>\n  <li>Add 0x to the start of each of the first two lines.</li>\n</ol>\n<p>At this point, the signature should look something like this</p>\n<p>4. the “v” value is currently in hexadecimal format and needs to be converted to decimal format. You can make this conversion here:<a href=\"http://hextodecimal.com/index.php?hex=1c\"><strong>HEX 1C to DECIMAL</strong></a><br>\n<a href=\"http://hextodecimal.com/index.php?hex=1c\"><em>Convert HEX to DECIMAL tables: find the decimal and binary representation of a hexadecimal number, calculate&nbsp;...</em>hextodecimal.com</a></p>\n<p>1c in decimal is 28, so my v value is 28.So now we’ve collected the following from the user we plan on registering:public address = 0x3c5…r = 0x02c9….s = 0x7a5c….v = 28And we’ll name the HydroID for this user AnuragHydro3.0So now we need to return to the Hydro Client-Raindrop smart contract on MyCrypto, except now we will be calling the signUpDelegatedUser function instead of signUpUser function. Enter the parameters you’ve collected above as follows:</p>\n<p>And here’s the successful etherscan confirmation:<a href=\"https://rinkeby.etherscan.io/tx/0x11664ee208cbc94219903fc960fbd27476b90abde6cb0c2cc4a160a86367df6c\"><strong>Rinkeby Transaction 0x11664ee208cbc94219903fc960fbd27476b90abde6cb0c2cc4a160a86367df6c</strong></a><br>\n<a href=\"https://rinkeby.etherscan.io/tx/0x11664ee208cbc94219903fc960fbd27476b90abde6cb0c2cc4a160a86367df6c\"><em>Rinkeby (ETH) detailed transaction info for 0x11664ee208cbc94219903fc960fbd27476b90abde6cb0c2cc4a160a86367df6c</em>rinkeby.etherscan.io</a></p>\n<p>And voila! You’ve manually registered a separate user. Programmatically, you could call all these same functions the same way and register users en-masse.Let me know if you’re able to replicate these steps successfully or integrate this process to be native to your own app! Alternatively, you are always able to have your users download the Hydro mobile app and sign up for the Hydro API via the Hydrogen website and simply connect your app to the Hydro API.<br>\n</p>\n</html>",
      "json_metadata": "{\"tags\":[\"blockchain\",\"howto\",\"api\",\"developers\",\"hydro\"],\"users\":[\"title\",\"dev\"],\"image\":[\"https://cdn-images-1.medium.com/max/800/1*H3p0QEe_W3_kaxYp8ArQwA.jpeg\"],\"links\":[\"https://www.youtube.com/watch?v=sbtRkJKz64c\",\"https://github.com/hydrogen-dev/smart-contracts\",\"https://medium.com/hydrogen-api/project-hydro-features-in-depth-look-39faa29f0d61\",\"https://ethereum.stackexchange.com/questions/34718/how-do-i-buy-tokens-on-the-rinkeby-test-environment\",\"https://mycrypto.com/contracts/interact\",\"https://rinkeby.etherscan.io/address/0x4959c7f62051d6b2ed6eaed3aaee1f961b145f20#code\",\"https://rinkeby.etherscan.io/address/0xb29778Cf8abFFF8BF245b9060CD2299ADb358040#code\",\"https://rinkeby.etherscan.io/tx/0xae4c95811e3f5616ed3a12b5aea53082c26b5803885b5333fd7a3c0831b8cd49\",\"https://mycrypto.com/sign-and-verify-message/sign\",\"https://emn178.github.io/online-tools/keccak_256.html\",\"https://ethereum.stackexchange.com/questions/15766/what-does-v-r-s-in-eth-gettransactionbyhash-mean\",\"http://hextodecimal.com/index.php?hex=1c\",\"https://rinkeby.etherscan.io/tx/0x11664ee208cbc94219903fc960fbd27476b90abde6cb0c2cc4a160a86367df6c\"],\"app\":\"steemit/0.1\",\"format\":\"html\"}"
    }
  ]
}

{
  "trx_id": "51446f22050e3f4d3a5053a31de92ced93d90030",
  "block": 23063129,
  "trx_in_block": 44,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-05T18:26:36",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "blockchain",
      "author": "hydrogenapi",
      "permlink": "hydro-dev-update-6-1",
      "title": "Hydro Dev Update 6/1",
      "body": "<html>\n<p><img src=\"https://cdn-images-1.medium.com/max/800/1*P40hgkStX9v2oWoiOhjXzA.jpeg\" width=\"800\" height=\"531\"/></p>\n<p>This week, <a href=\"https://medium.com/@HydroAndy\">Andy</a> and I settled on the final(ish!) form for our Snowflake smart contracts. After some productive discussions with Mike, <a href=\"https://medium.com/u/5735cf25eb95\">Shane</a>, <a href=\"https://medium.com/@anuragangara\">Anurag</a>, and Nahom, we’ve concluded that Snowflake will consist of 3 interrelated elements:</p>\n<ol>\n  <li>Self-attested data. Anyone will be able to mint a unique, personal Snowflake, and populate it with their name, date of birth, email address, and so on. This data will be encrypted via a (salted) one-way hash function and stored on-chain.</li>\n  <li>Third-party resolvers. These will be smart contracts to which users can link their Snowflakes. These smart contracts will provide additional functionality on top of the core Snowflake protocol.</li>\n  <li>Token deposits. Users, data validators, and other third-party applications will be able to deposit HYDRO tokens to the Snowflake smart contract. This will facilitate staking requirements, payments, and other token functionality that will be integrated seamlessly into the Hydro ecosystem as it develops.</li>\n</ol>\n<p>In addition to working on Snowflake, I made a tutorial video for Server-Side Raindrop (out soon!), and Andy added full CRUD functionality to some parts of the API. We’re also looking forward to next week, when <a href=\"https://medium.com/@reyhaynes\">Reinaldo</a> and the rest of the team are planning to submit the Client Raindrop iOS app to the App Store.</p>\n<p><em>We’d love to hear from you! Please get in touch via</em> <a href=\"https://discord.gg/VR6uQRn\"><em>Discord</em></a><em>,</em> <a href=\"http://www.reddit.com/r/projecthydro\"><em>Reddit</em></a><em>, or</em> <a href=\"https://t.me/joinchat/IMnWCE7MpLpRzxFC1L3O-g\"><em>Telegram</em></a><em>.</em></p>\n</html>",
      "json_metadata": "{\"tags\":[\"blockchain\",\"api\",\"developers\",\"hydro\",\"ethereum\"],\"image\":[\"https://cdn-images-1.medium.com/max/800/1*P40hgkStX9v2oWoiOhjXzA.jpeg\"],\"links\":[\"https://medium.com/@HydroAndy\",\"https://medium.com/u/5735cf25eb95\",\"https://medium.com/@anuragangara\",\"https://medium.com/@reyhaynes\",\"https://discord.gg/VR6uQRn\",\"http://www.reddit.com/r/projecthydro\",\"https://t.me/joinchat/IMnWCE7MpLpRzxFC1L3O-g\"],\"app\":\"steemit/0.1\",\"format\":\"html\"}"
    }
  ]
}

{
  "trx_id": "b4b9088dec2cd4afdb846cd1df287413200698c1",
  "block": 23007371,
  "trx_in_block": 55,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-06-03T19:57:36",
  "op": [
    "vote",
    {
      "voter": "dan31",
      "author": "hydrogenapi",
      "permlink": "welcome-hydrogen-client-ci-investments",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 22948555,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 4,
  "timestamp": "2018-06-01T18:55:42",
  "op": [
    "author_reward",
    {
      "author": "hydrogenapi",
      "permlink": "hydro-dev-update-5-25",
      "sbd_payout": "0.014 SBD",
      "steem_payout": "0.001 STEEM",
      "vesting_payout": "16.265326 VESTS"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 22948094,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 8,
  "timestamp": "2018-06-01T18:32:39",
  "op": [
    "author_reward",
    {
      "author": "hydrogenapi",
      "permlink": "first-look-hydro-snowflake",
      "sbd_payout": "0.011 SBD",
      "steem_payout": "0.001 STEEM",
      "vesting_payout": "14.232172 VESTS"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 22944700,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 15,
  "timestamp": "2018-06-01T15:42:48",
  "op": [
    "author_reward",
    {
      "author": "hydrogenapi",
      "permlink": "project-hydro-features-in-depth-look",
      "sbd_payout": "0.014 SBD",
      "steem_payout": "0.001 STEEM",
      "vesting_payout": "14.232260 VESTS"
    }
  ]
}

{
  "trx_id": "033a928341cff14b2c499d9b2b855e1f81ce52b1",
  "block": 22922114,
  "trx_in_block": 33,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-05-31T20:52:42",
  "op": [
    "comment",
    {
      "parent_author": "hydrogenapi",
      "parent_permlink": "welcome-hydrogen-client-ci-investments",
      "author": "cheetah",
      "permlink": "cheetah-re-hydrogenapiwelcome-hydrogen-client-ci-investments",
      "title": "",
      "body": "Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in:\nhttp://www.ci.com/web/company/aboutus.jsp?lang=ENG",
      "json_metadata": ""
    }
  ]
}

{
  "trx_id": "071f544f454493757fecb7a11e60b58e88fc1b7f",
  "block": 22922113,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-05-31T20:52:39",
  "op": [
    "vote",
    {
      "voter": "cheetah",
      "author": "hydrogenapi",
      "permlink": "welcome-hydrogen-client-ci-investments",
      "weight": 8
    }
  ]
}

{
  "trx_id": "652e92fc646369132bb9e5c45d91f8fd1e3c68bb",
  "block": 22922107,
  "trx_in_block": 3,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-05-31T20:52:21",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "apis",
      "author": "hydrogenapi",
      "permlink": "welcome-hydrogen-client-ci-investments",
      "title": "Welcome Hydrogen Client: CI Investments",
      "body": "<html>\n<p><img src=\"https://cdn-images-1.medium.com/max/1000/1*ld8EX5LJ161fE53LVkRg_Q.png\" width=\"1000\" height=\"372\"/></p>\n<p>We would like to give a warm welcome to <a href=\"http://www.ci.com/web/home.jsp\">CI Investments</a>, the latest Hydrogen Platform client to be publicly disclosed. We look forward to a great relationship with CI, as they work to continually bring awesome financial products to the market!</p>\n<p>Interested in learning more about CI Investments? Here is how they describe themselves (from the CI website):</p>\n<blockquote><em>CI Investments has been managing money on behalf of Canadian investors since 1965. In 1981, CI entered the global fund arena with the introduction of CI Pacific Fund — one of the first funds in Canada devoted to Asian markets. The company became known for its expertise in foreign funds and adopted the name Canadian International Fund Management.</em></blockquote>\n<blockquote><em>Over the years, CI expanded its lineup of funds to provide investors with an increasingly comprehensive offering of Canadian, global and industry funds. This growth was guided by a strategy of seeking the best available portfolio managers.</em></blockquote>\n<blockquote><em>CI is a leader in innovation. The company was, for example, the first to offer tax-efficient funds with the introduction of</em> <a href=\"http://ci.com/corporateclass/index.jsp?lang=ENG\"><em>CI Corporate Class</em></a><em>. CI also was a leader in introducing industry funds and was the first mutual fund company to partner with an insurance company to offer segregated funds.</em></blockquote>\n<blockquote><em>In June 2005, CI adopted the name CI Investments to reflect its diverse lineup of investment options, including mutual funds, segregated funds, asset allocation programs, structured products and other alternative investments.</em></blockquote>\n<blockquote><em>Today, CI Investments is one of Canada’s largest investment fund companies.</em> <em><strong>About two million Canadians</strong></em> <em>trust us to help realize their financial goals.</em></blockquote>\n<blockquote><em>CI is proud to partner with financial advisors across Canada, who offer our funds to their clients. We believe investors are most successful when they follow a sound financial plan developed with the assistance of a qualified advisor.</em></blockquote>\n<blockquote><em>CI is affiliated with two alternative asset management firms, Marret Asset Management Inc. (</em><a href=\"http://www.marret.com/\"><em>www.marret.com</em></a><em>) and Lawrence Park Asset Management (</em><a href=\"http://lawrenceparkam.com/\"><em>lawrenceparkam.com</em></a><em>).</em></blockquote>\n<blockquote><em>CI also serves the institutional investment marketplace through a dedicated division, CI Institutional Asset Management, which is on the Web at</em> <a href=\"http://www.ciinstitutional.com/\"><em>www.ciinstitutional.com</em></a><em>.</em></blockquote>\n<blockquote><em>CI is a subsidiary of</em> <a href=\"http://www.ci.com/cix\"><em>CI Financial Corp.</em></a><em>, which is listed on the Toronto Stock Exchange under the symbol CIX. Information about CI Financial’s assets and financial position is updated monthly and is available by visiting the</em> <a href=\"http://www.cifinancial.com/ci_stats.jsp\"><em>Statistics</em></a><em>section.</em></blockquote>\n</html>",
      "json_metadata": "{\"tags\":[\"apis\",\"client\",\"fintech\"],\"image\":[\"https://cdn-images-1.medium.com/max/1000/1*ld8EX5LJ161fE53LVkRg_Q.png\"],\"links\":[\"http://www.ci.com/web/home.jsp\",\"http://ci.com/corporateclass/index.jsp?lang=ENG\",\"http://www.marret.com/\",\"http://lawrenceparkam.com/\",\"http://www.ciinstitutional.com/\",\"http://www.ci.com/cix\",\"http://www.cifinancial.com/ci_stats.jsp\"],\"app\":\"steemit/0.1\",\"format\":\"html\"}"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 22915616,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 14,
  "timestamp": "2018-05-31T15:27:48",
  "op": [
    "author_reward",
    {
      "author": "hydrogenapi",
      "permlink": "introducing-the-hydro-community-development-program",
      "sbd_payout": "0.030 SBD",
      "steem_payout": "0.002 STEEM",
      "vesting_payout": "32.532598 VESTS"
    }
  ]
}

{
  "trx_id": "927e436fd2868d2215489cb52c6ac25054af0a85",
  "block": 22791609,
  "trx_in_block": 31,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-05-27T08:06:42",
  "op": [
    "vote",
    {
      "voter": "mzg",
      "author": "hydrogenapi",
      "permlink": "examining-hydro-token-dynamics",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "35442cf4edc9be5119a6b887d3ab44f66e761592",
  "block": 22751607,
  "trx_in_block": 40,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-05-25T22:46:15",
  "op": [
    "vote",
    {
      "voter": "starkay",
      "author": "hydrogenapi",
      "permlink": "examining-hydro-token-dynamics",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "666ffc883671a7fbf4354e47a0d53b7becd32b27",
  "block": 22749507,
  "trx_in_block": 38,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-05-25T21:01:12",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "blockchain",
      "author": "hydrogenapi",
      "permlink": "examining-hydro-token-dynamics",
      "title": "Examining Hydro Token Dynamics",
      "body": "<html>\n<p><img src=\"https://cdn-images-1.medium.com/max/800/1*QRR4bhiiCYCtF28UcLw9DQ.png\" width=\"800\" height=\"319\"/></p>\n<p>How do HYDRO tokens work within the greater Hydrogen ecosystem?In this video, we examine how the Hydro token is integral to achieving our mission of building the global financial platform of the Web 3.0.</p>\n<p><br></p>\n<p>https://www.youtube.com/watch?v=UGtoN1EpJA8</p>\n</html>",
      "json_metadata": "{\"tags\":[\"blockchain\",\"hydro\",\"ethereum\",\"developer\"],\"image\":[\"https://cdn-images-1.medium.com/max/800/1*QRR4bhiiCYCtF28UcLw9DQ.png\",\"https://img.youtube.com/vi/UGtoN1EpJA8/0.jpg\"],\"links\":[\"https://www.youtube.com/watch?v=UGtoN1EpJA8\"],\"app\":\"steemit/0.1\",\"format\":\"html\"}"
    }
  ]
}