{
  "trx_id": "8b1f1431e2c57fd6b3d8bdecfac1e86511546641",
  "block": 106146732,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2026-05-18T03:00:12",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "lisk-official",
      "vesting_shares": "7119.442384 VESTS"
    }
  ]
}

{
  "trx_id": "43ef9ce0c46f933d5c5a66c4800b2b2e4cd72daf",
  "block": 105989019,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2026-05-12T14:57:24",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "lisk-official",
      "vesting_shares": "4407.231979 VESTS"
    }
  ]
}

{
  "trx_id": "04548df2ec9b369b0baa386ad5b18ede83e9a90e",
  "block": 105514306,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2026-04-26T02:16:48",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "lisk-official",
      "vesting_shares": "7131.958140 VESTS"
    }
  ]
}

{
  "trx_id": "dc2076c5bc70ed39ed2ad62d3cc73b59575f6ec9",
  "block": 102860622,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2026-01-23T15:09:15",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "lisk-official",
      "vesting_shares": "4448.778798 VESTS"
    }
  ]
}

{
  "trx_id": "a4efd50e7fe3d1a4ffa03e449c4d2b906561f77b",
  "block": 91306915,
  "trx_in_block": 3,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2024-12-17T10:23:21",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "lisk-official",
      "vesting_shares": "4612.997995 VESTS"
    }
  ]
}

{
  "trx_id": "435925e3ce48c807c8e0aee8cf6ee3fcb20db51c",
  "block": 79861101,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2023-11-14T02:05:36",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "lisk-official",
      "vesting_shares": "4782.131527 VESTS"
    }
  ]
}

{
  "trx_id": "223e4b946e59fc345044171caee72e252603adff",
  "block": 78351692,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2023-09-22T01:03:27",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "lisk-official",
      "vesting_shares": "7719.410313 VESTS"
    }
  ]
}

{
  "trx_id": "3e0ff3ec32deec1c741a5e9e386290adbc37077b",
  "block": 69116546,
  "trx_in_block": 5,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-11-03T14:27:21",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "lisk-official",
      "vesting_shares": "7941.091751 VESTS"
    }
  ]
}

{
  "trx_id": "b15f52bd262f37f80a3fc592c356a5d0be58437c",
  "block": 60817530,
  "trx_in_block": 32,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-01-17T17:45:09",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "lisk-official",
      "vesting_shares": "8161.326887 VESTS"
    }
  ]
}

{
  "trx_id": "60b65cbff52bdae3fe0cb13885ef028bcacca482",
  "block": 54610683,
  "trx_in_block": 9,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-06-14T03:17:45",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "lisk-official",
      "vesting_shares": "8345.393640 VESTS"
    }
  ]
}

{
  "trx_id": "6a1c6efc8ad328db39d148efb73a7b91bb5f7d9d",
  "block": 49358049,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-12-11T13:33:27",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "lisk-official",
      "vesting_shares": "8532.815614 VESTS"
    }
  ]
}

{
  "trx_id": "265dc19339afc10c0bfd8fabf35b95ba6ded5d3b",
  "block": 49209593,
  "trx_in_block": 9,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-12-06T07:09:51",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "lisk-official",
      "vesting_shares": "1912.543513 VESTS"
    }
  ]
}

{
  "trx_id": "8cb9633dd5f9186004b7400f7a56e42b2fe408b0",
  "block": 49193138,
  "trx_in_block": 10,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-12-05T17:11:24",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "lisk-official",
      "vesting_shares": "8539.023468 VESTS"
    }
  ]
}

{
  "trx_id": "e70354118b6e825105d070b64b9d4bb3302a2eff",
  "block": 48263740,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-11-02T20:40:54",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "lisk-official",
      "vesting_shares": "1920.017158 VESTS"
    }
  ]
}

{
  "trx_id": "4f2f8d0e87aaaaced6f081566c342d71366c6d05",
  "block": 43219876,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-05-09T08:10:00",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "lisk-official",
      "vesting_shares": "8741.828827 VESTS"
    }
  ]
}

{
  "trx_id": "35ac8acac066458d85ede1a5f5382c473acb78ca",
  "block": 43196405,
  "trx_in_block": 42,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-05-08T12:08:00",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "lisk-official",
      "vesting_shares": "1953.311140 VESTS"
    }
  ]
}

{
  "trx_id": "3da631401c241297bc575253d02df5a9824b2550",
  "block": 39745552,
  "trx_in_block": 14,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-01-08T10:01:00",
  "op": [
    "comment",
    {
      "parent_author": "lisk-official",
      "parent_permlink": "lisk-hub-1-0-0-and-1-1-0-reference-field-help-page-and-more",
      "author": "steemitboard",
      "permlink": "steemitboard-notify-lisk-official-20200108t100059000z",
      "title": "",
      "body": "Congratulations @lisk-official! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@lisk-official/birthday2.png</td><td>Happy Birthday! - You are on the Steem blockchain for 2 years!</td></tr></table>\n\n<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@lisk-official) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=lisk-official)_</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": "c80f8f94a78deb98c54772c9ed16d0c681e896c4",
  "block": 37891237,
  "trx_in_block": 25,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-11-04T21:52:21",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "lisk-official",
      "vesting_shares": "8846.088886 VESTS"
    }
  ]
}

{
  "trx_id": "d96c8c6c20b9a44854ede099ab92e2838a7cef64",
  "block": 29273467,
  "trx_in_block": 18,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-01-08T10:46:27",
  "op": [
    "comment",
    {
      "parent_author": "lisk-official",
      "parent_permlink": "lisk-hub-1-0-0-and-1-1-0-reference-field-help-page-and-more",
      "author": "steemitboard",
      "permlink": "steemitboard-notify-lisk-official-20190108t104626000z",
      "title": "",
      "body": "Congratulations @lisk-official! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@lisk-official/birthday1.png</td><td>1 Year on Steemit</td></tr></table>\n\n<sub>_[Click here to view your Board](https://steemitboard.com/@lisk-official)_</sub>\n\n\n**Do not miss the last post from @steemitboard:**\n<table><tr><td><a href=\"https://steemit.com/steem/@steemitboard/steemwhales-has-officially-moved-to-steemitboard-ranking\"><img src=\"https://steemitimages.com/64x128/https://cdn.steemitimages.com/DQmfRVpHQhLDhnjDtqck8GPv9NPvNKPfMsDaAFDE1D9Er2Z/header_ranking.png\"></a></td><td><a href=\"https://steemit.com/steem/@steemitboard/steemwhales-has-officially-moved-to-steemitboard-ranking\">SteemWhales has officially moved to SteemitBoard Ranking</a></td></tr><tr><td><a href=\"https://steemit.com/steemitboard/@steemitboard/steemitboard-witness-update-2019-01-07\"><img src=\"https://steemitimages.com/64x128/http://i.cubeupload.com/7CiQEO.png\"></a></td><td><a href=\"https://steemit.com/steemitboard/@steemitboard/steemitboard-witness-update-2019-01-07\">SteemitBoard - Witness Update</a></td></tr></table>\n\n> Support [SteemitBoard's project](https://steemit.com/@steemitboard)! **[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": "88c2644e32f4b1f7ad914d0fff8e703bb39b39aa",
  "block": 28153657,
  "trx_in_block": 13,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-11-30T12:57:45",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "lisk-official",
      "vesting_shares": "9043.538531 VESTS"
    }
  ]
}

{
  "trx_id": "6d302006c8e84c7ebc19ac242b5855e7625495b0",
  "block": 26153506,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-09-22T00:53:09",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "lisk-official",
      "vesting_shares": "29292.955262 VESTS"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 25751450,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 4,
  "timestamp": "2018-09-07T12:43:21",
  "op": [
    "author_reward",
    {
      "author": "lisk-official",
      "permlink": "lisk-hub-1-0-0-and-1-1-0-reference-field-help-page-and-more",
      "sbd_payout": "0.000 SBD",
      "steem_payout": "0.010 STEEM",
      "vesting_payout": "22.249525 VESTS"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 25751277,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 9,
  "timestamp": "2018-09-07T12:34:42",
  "op": [
    "author_reward",
    {
      "author": "lisk-official",
      "permlink": "everything-you-need-to-know-about-the-successful-release-of-core-1-0-to-mainnet",
      "sbd_payout": "0.000 SBD",
      "steem_payout": "0.011 STEEM",
      "vesting_payout": "22.249532 VESTS"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 25640243,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 8,
  "timestamp": "2018-09-03T16:00:39",
  "op": [
    "author_reward",
    {
      "author": "lisk-official",
      "permlink": "lisk-core-1-0-1-patch-release",
      "sbd_payout": "0.000 SBD",
      "steem_payout": "0.010 STEEM",
      "vesting_payout": "20.231001 VESTS"
    }
  ]
}

{
  "trx_id": "85aa3e1d89d1ae2c7f97b138f90e2eb3c0fc1f01",
  "block": 25558746,
  "trx_in_block": 21,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-31T20:02:12",
  "op": [
    "vote",
    {
      "voter": "gniewko",
      "author": "lisk-official",
      "permlink": "lisk-hub-1-0-0-and-1-1-0-reference-field-help-page-and-more",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "1683fefe51986cedfbac26c1d7a06a6d9bfe8da4",
  "block": 25558744,
  "trx_in_block": 6,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-31T20:02:06",
  "op": [
    "vote",
    {
      "voter": "gniewko",
      "author": "lisk-official",
      "permlink": "everything-you-need-to-know-about-the-successful-release-of-core-1-0-to-mainnet",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "f81755d8e52043d6930c6b859bd6abad3940018e",
  "block": 25551405,
  "trx_in_block": 11,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-31T13:55:03",
  "op": [
    "vote",
    {
      "voter": "sensation",
      "author": "lisk-official",
      "permlink": "everything-you-need-to-know-about-the-successful-release-of-core-1-0-to-mainnet",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "d785a02efa97777a347eb0d180d521bd88b8f07c",
  "block": 25550430,
  "trx_in_block": 30,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-31T13:06:18",
  "op": [
    "vote",
    {
      "voter": "stuffbyspencer",
      "author": "lisk-official",
      "permlink": "everything-you-need-to-know-about-the-successful-release-of-core-1-0-to-mainnet",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "8914e31d6228fa0f143d442c74996001e48524ac",
  "block": 25550429,
  "trx_in_block": 13,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-31T13:06:15",
  "op": [
    "vote",
    {
      "voter": "stuffbyspencer",
      "author": "lisk-official",
      "permlink": "lisk-hub-1-0-0-and-1-1-0-reference-field-help-page-and-more",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "149b2002122eb71101c6ff0c46088d9a9674177b",
  "block": 25550202,
  "trx_in_block": 35,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-31T12:54:54",
  "op": [
    "vote",
    {
      "voter": "youngogmarqs",
      "author": "lisk-official",
      "permlink": "everything-you-need-to-know-about-the-successful-release-of-core-1-0-to-mainnet",
      "weight": 2
    }
  ]
}

{
  "trx_id": "ae86ba69913aa90903f5f56c1ae39c93b074ece4",
  "block": 25549971,
  "trx_in_block": 5,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-31T12:43:21",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "blockchain",
      "author": "lisk-official",
      "permlink": "lisk-hub-1-0-0-and-1-1-0-reference-field-help-page-and-more",
      "title": "Lisk Hub 1.0.0 and 1.1.0 — Reference Field, Help Page, and More",
      "body": "![0_JPV9hMUZSVl4cU9X.png](https://cdn.steemitimages.com/DQmZ8EUEVDXVqo8EuxBGRbUdhrsutjL5fHXdwz5a9jFNoJb/0_JPV9hMUZSVl4cU9X.png)\n\nMany changes accompanied the important migration of Lisk Mainnet to Lisk Core 1.0 on August 29. The latest version of Lisk Core required other Lisk products to release new versions. This is why we released Lisk Hub 1.0.0, along with minor release Lisk Hub 1.1.0. For end users, this means that the auto updater will skip version 1.0.0 and go directly to 1.1.0. This blog post describes the updates in both versions.\n\nNew functionalities include:\n\n* Compatibility with Lisk Core 1.0\n* Reference field\n* Help page\n* Menu highlight and network switcher designs\n\n**Compatibility with Lisk Core 1.0**\n\nThe work done in Lisk Hub 1.0.0 was largely to ensure that its entire code base is compatible with the new API of Lisk Core and Lisk Elements.\n\nThis includes support for the main Lisk transaction types — send LSK tokens, vote for delegates, register a delegate, and register a second passphrase. Each of the transaction types has its own page and sending process tailored for specifics of the particular type.\n\nIt also includes all the functionalities for browsing and searching the Lisk blockchain. Users can search by delegate names, Lisk IDs, and transaction IDs to find delegates, accounts, and transactions. All the search results then link to other relevant objects (e.g. a transaction links to its sender and recipient) to accommodate a seamless browsing experience.\n\nFinally, we updated the advanced sign message feature to use the improved signing algorithm and output format from Lisk Elements 1.0.0. With this feature, users can prove ownership of their account to a third party without incurring the cost of sending a transaction.\n\n**Reference field**\n\nLisk Core 1.0 brings about a data field for token transfer transactions. This feature allows users to attach a message of up to 64 bytes when transferring LSK tokens. Lisk Hub makes use of this feature to allow users to write text in a reference field when making transactions. This reference can be seen by the recipient to allow for easier identification and distinction of transactions. In this release, the reference is displayed in the transaction details page. In the future, however, the reference will also be displayed directly in the wallet.\n\nPlease note that the reference is stored on the blockchain in plain text therefore can be read by anyone who looks at the public ledger of the Lisk blockchain.\n\n![0_eKkYahxaY7JU-qkg.png](https://cdn.steemitimages.com/DQmZ8EUEVDXVqo8EuxBGRbUdhrsutjL5fHXdwz5a9jFNoJb/0_eKkYahxaY7JU-qkg.png)\n\n**Help page**\n\nIn Lisk Hub 1.1.0, we wanted to give users an easy way to get help if they need it. We created a new Help page in the Lisk Hub with links to existing sources — the Lisk Help Center, Lisk Academy, Lisk Chat, and specific pages within those sources. The Help page can be easily accessed from the sidebar menu.\n\n![0_FYAqtkgYTWmwmtmy.png](https://cdn.steemitimages.com/DQmZpQNFQUry1YjqDwj5kssY5xSYYjdzoLoG69LoPe7LSSo/0_FYAqtkgYTWmwmtmy.png)\n\n**Menu highlight and network switcher designs**\n\nIn addition to adding new functionalities, we also strive to improve the appearance of existing features, not only for the sake of aesthetics, but also to improve usability.\n\nOne of these changes regards the active page indicator in the main menu. The active page is highlighted by a blue stripe on the right side of the menu item. It turns out that this was not sufficient in some user tests therefore in addition to the blue stripe, we added also a gray background gradient.\n\nWe also updated the network switcher on the login page. The network switcher was first created as an advanced/developer utility without any regard for the design, because it is not displayed automatically. Eventually, we decided to make this feature discoverable through a switcher in settings. For this reason, we went back to the design table to give the account switcher a proper design that is aligned with the rest of the application.\n\n![0_vYgU5mBZF8kweMmn.png](https://cdn.steemitimages.com/DQmQzcQ6U8cSEeLmK6ojxpVDZQBMYUc64oNsSoMXA11wy1C/0_vYgU5mBZF8kweMmn.png)\n\n[Download the desktop app and follow Lisk Hub on GitHub to keep an eye on development in real-time.](https://github.com/LiskHQ/lisk-hub/releases)\n\n*About the Author:*\n\n*[Vít Stanislav](https://lisk.io/team/vit-stanislav) is a frontend developer for Lisk at Lightcurve and the project lead of Lisk Hub. Previously, he was developing web-based tools for Red Hat. He has plenty of additional frontend experience from developing online learning systems as a member of Adaptive Learning research group at Masaryk University, Brno, Czech Republic. He is committed to making Lisk the blockchain technology with the best user experience.*\n\n___\n<center>Posted by us also on [![Medium](https://cdn-static-1.medium.com/_/fp/icons/favicon-rebrand-medium.3Y6xpZ-0FSdWDnPM3hSBIA.ico)](https://medium.com/@Lisk) </center>\n___\n\nIs this one of the first posts that you're seeing about Lisk? See more at [Lisk.io](https://lisk.io/) or [Github](https://github.com/LiskHQ/).",
      "json_metadata": "{\"tags\":[\"blockchain\",\"lisk\",\"crypto\",\"developer\",\"javascript\"],\"image\":[\"https://cdn.steemitimages.com/DQmZ8EUEVDXVqo8EuxBGRbUdhrsutjL5fHXdwz5a9jFNoJb/0_JPV9hMUZSVl4cU9X.png\",\"https://cdn.steemitimages.com/DQmZ8EUEVDXVqo8EuxBGRbUdhrsutjL5fHXdwz5a9jFNoJb/0_eKkYahxaY7JU-qkg.png\",\"https://cdn.steemitimages.com/DQmZpQNFQUry1YjqDwj5kssY5xSYYjdzoLoG69LoPe7LSSo/0_FYAqtkgYTWmwmtmy.png\",\"https://cdn.steemitimages.com/DQmQzcQ6U8cSEeLmK6ojxpVDZQBMYUc64oNsSoMXA11wy1C/0_vYgU5mBZF8kweMmn.png\",\"https://cdn-static-1.medium.com/_/fp/icons/favicon-rebrand-medium.3Y6xpZ-0FSdWDnPM3hSBIA.ico\"],\"links\":[\"https://github.com/LiskHQ/lisk-hub/releases\",\"https://lisk.io/team/vit-stanislav\",\"https://medium.com/@Lisk\",\"https://lisk.io/\",\"https://github.com/LiskHQ/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}

{
  "trx_id": "8cc8943bcc0f0d326a99040c65382cd18825c659",
  "block": 25549798,
  "trx_in_block": 6,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-31T12:34:42",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "blockchain",
      "author": "lisk-official",
      "permlink": "everything-you-need-to-know-about-the-successful-release-of-core-1-0-to-mainnet",
      "title": "Everything You Need to Know About the Successful Release of Core 1.0 to Mainnet",
      "body": "![1_2bfogqp9QePtcONfE3LeQw.png](https://cdn.steemitimages.com/DQmad8udfYhQM9SPWKzhF62UGZHa7SXaT6nTrsKZkomphHq/1_2bfogqp9QePtcONfE3LeQw.png)\n\nThe Lisk project has reached its most important and exciting milestone to date! **Following a rigorous period of development, testing and quality assurance to guarantee the release of only the best possible product, [Lisk Core](https://www.youtube.com/watch?v=RfF9EPwQDOY&t=) 1.0 is now on Mainnet! All 101 Lisk delegates migrated in less than 24 hours and are successfully forging and securing the network.** The majority of nodes before the migration have already migrated and 8252 transactions have been executed so far.\n\nOur development team has worked incredibly hard to bring the project to this point. We also want to thank everyone — our community and delegates — who helped make this migration a big success.\n\nAlong with the release of Lisk Core 1.0, we have released Lisk Elements 1.0, Lisk Commander 1.0, Lisk Hub 1.0, Lisk Explorer 2.1.4 and Lisk Nano 2.0 over the last few weeks. All of the various components of the Lisk ecosystem have evolved to maintain compatibility with one another. Each product brings about its own major updates, further functionalities and advanced features. Read on to learn more about them all.\n\n![0_equDKC6v3g7NIiVc.png](https://cdn.steemitimages.com/DQmP6U8ua94uAH5rwMJjmsnRWKh1D6eUu5ZdmB5ecRsTbhU/0_equDKC6v3g7NIiVc.png)\n\n**[Lisk Core 1.0](https://lisk.io/core)**\n\nThe Lisk Core product was first created in February 2016 and has since seen 41 iterations — the most recent version prior to Lisk Core 1.0 was Lisk Core 0.9.16. Getting to this point in our development involved making over 8,000 commits and closing over 1,000 issues with thousands of peer reviews. Lisk Core 1.0 also included the implementation of an improved Quality Assurance (QA) process. In the future, all releases will include this process.\n\n![0_NRMiHGlZR733l3pZ.png](https://cdn.steemitimages.com/DQmP39zseaTkC9wqSc7q3ngWWyZ56rb4ByBCM1T914pU9d2/0_NRMiHGlZR733l3pZ.png)\n\n**Introducing the Five Most Important New Features of Lisk Core 1.0:**\n\n***1. New API & Design***\n\nIn an effort to lower the entry barriers to Lisk and increase user adoption, we are utilizing REST, a widely-used standard. REST makes our API simple, intuitive and expressive, therefore user-friendly, for all developers.\n\n***2. New P2P Communication Layer (also known as Real-Time Peers)***\n\nWe redesigned our P2P layer to maximize performance and improve the reliability of the network. Peers are now able to stay connected to each other and exchange data using a real-time framework provided by SocketCluster. SocketCluster is a fast, highly-scalable, HTTP and real-time server engine. It removes the limitations of having to run your Node.js server as a single thread and can utilize all of the CPU cores available on a machine. It can scale easily by splitting work between multiple processes. It also helps to make your backend system resilient by automatically recovering workers’ threads in the case of crashes.\n\n***3. Transaction Memo***\n\nWith our brand new data field, you now have the option to attach a custom message of up to 64 bytes to your transaction.\n\n***4. Fully Atomic Block Writes***\n\nFully atomic block writes guarantee proper data integrity across the network’s nodes when writing to the database, together with greatly improved processing efficiency.\n\n***5. Structured and Rewritten Test Suites***\n\nHaving a proper test suite is very important for the security of the network, as those efforts will guarantee the appropriate behavior of the application in the future. During the road to Lisk Core 1.0.0, we have written more than 80,000 lines of different test types. We have also completely rewritten most of them to ensure that they can scale further.\n\n[Watch Lisk Core in 1 Minute](https://www.youtube.com/watch?v=PPVJmbaKcLU&t=1s)!\n\n![0_jYS7m-PQiMnt-x-J.png](https://cdn.steemitimages.com/DQmdcByBnv4zi1F1QH1chfCdpw6ppMGL7U3TFVH2XU2u7J6/0_jYS7m-PQiMnt-x-J.png)\n\n**[Lisk Elements 1.0](https://lisk.io/documentation/lisk-elements)**\n\nIn early August, we released Lisk Elements 1.0, the latest general-purpose JavaScript library. Formerly known as “LiskJS” it is our go-to resource for Lisk-related JavaScript functionality. It is intended primarily for JavaScript developers and we currently use it in several of our own products, including Lisk Hub and Lisk Commander.\n\n**Lisk Elements 1.0 Introduces Five New Key Features:**\n\n***1. Complete codebase rewrite and redesign***\n\nWe are now dividing functionality into distinct areas with clear dependencies on each other:\n\n* Constants relating to the Lisk protocol or our Mainnet and Testnet networks.\n* Cryptographic functions required by the Lisk protocol or otherwise recommended by LiskHQ.\n* Mnemonic passphrase management, aligning with the BIP39 wordlists.\n* Transaction creators for each transaction type in the Lisk protocol.\n* An API client for communication with nodes on the Lisk network.\n\n***2. New API client***\n\nThe new API client for Lisk Elements has been designed to work with the new public API available in Lisk Core 1.0. We have structured the API-client resource-based so that it is extensible and adjustable to changes in the Lisk Core API.\n\n***3. New protocol for signing messages using Lisk passphrase***\n\nWe have made protocol level improvements on the signing message feature in order to make it more secure. By adding the Lisk protocol-specific header into the message, the message can be differentiated from other protocols and users will be prevented from mis-signing unintended messages.\n\n***4. More utility functions***\n\nAlong with creating transaction functions, we have created utility functions that can also be used independently.\n\n***5. Renaming of exposed functions and variables***\n\nThis makes the purposes of the functions and variables much clearer, making it easier for developers to find the functionalities they are looking for.\n\n**[Watch Lisk Elements in 1 Minute!](https://www.youtube.com/watch?v=ZEJTa0E9CAk)**\n\n![0_f_mj-saGjWj2L8Vg.png](https://cdn.steemitimages.com/DQmUV2CG73ua7cKVLyaufu1X7XGnXTSP1SSE4eT3S3tw8QD/0_f_mj-saGjWj2L8Vg.png)\n\n**[Lisk Commander 1.0](https://lisk.io/documentation/lisk-commander)**\n\nWe recently released the latest version of our command line interface tool, Lisk Commander 1.0. Previously known as “Lisky” Lisk Commander is a tool for advanced users of the Lisk network and uses our general-purpose JavaScript library, Lisk Elements. It also provides the functionality to interact with Lisk Core with the use of a command line.\n\n**Lisk Commander 1.0 Introduces Four New Key Features:**\n\n***1. Access more information***\n\nThe Lisk Commander functions *get* and *list* are compatible with the new Lisk Core 1.0 API. This means that Lisk Commander can obtain information related to the blockchain from a particular network.\n\n***2. Create, sign, verify and broadcast transactions and signature***\n\nWith the latest version of Lisk Commander, users can create type 0 to type 4 transactions, which are *transfer, register second signature, register a delegate, vote for delegates* and *register a multisignature account*. Separately or with command line *pipe* in interactive mode, users can sign and broadcast the transaction to the network. If a user receives a transaction, the user can also check to see if it contains a valid signature.\n\n***3. Encrypt passphrase and Decrypt passphrase commands now compatible with Lisk Core 1.0***\n\nThis feature is particularly important for delegates as a delegate needs to encrypt their passphrase locally and insert the encrypted passphrase in the configuration of the node to enable forging. Only the password used to create the encrypted passphrase is sent over the API endpoint provided by Lisk Core.\n\n***4. Sign message and verify message***\n\nThe *sign message* and *verify message* commands are often used to prove the ownership of a particular account. Now Commander supports creating such a message and verifies whether or not the signature and message are from the correct owner.\n\n**[Watch Lisk Commander in 1 Minute!](https://www.youtube.com/watch?v=XMQRf3-yWf8)**\n\n![0_PMU-M6KddqWGBHgv.png](https://cdn.steemitimages.com/DQmUWmKSco42SPhoAmnkrAV5A3CmD4SMGuhYhXran3pHYoF/0_PMU-M6KddqWGBHgv.png)\n\n**[Lisk Hub 1.1](https://lisk.io/hub)**\n\nLisk Hub is an all-in-one solution to manage your Lisk ID, access and send LSK tokens, as well as vote for delegates. To accommodate the release of Lisk Core 1.0, a great deal of work was done in Lisk Hub 1.0 and Lisk Hub 1.1 to ensure that its entire code base is compatible with the new API and Lisk Elements. For end users, this means that the auto updater will skip version 1.0 and go directly to 1.1.\n\nThe latest releases include support for the main Lisk transaction types — send LSK tokens, vote for delegates, register a delegate and register a second passphrase. Each of the transaction types has its own page and sending process tailored for specifics of the particular type. It also includes all the functionalities for browsing and searching the Lisk blockchain. Users can search by delegate names, Lisk IDs, and transaction IDs to find delegates, accounts and transactions. All the search results then link to other relevant objects (e.g. a transaction links to its sender and recipient) to accommodate a seamless browsing experience.\n\n**Lisk Hub 1.0 and Lisk Hub 1.1 Introduce Four New Key Features:**\n\n***1. Reference Field***\n\nLisk Core 1.0 brings about a data field for token transfer transactions. This feature allows users to attach a message of up to 64 bytes when transferring LSK tokens. Lisk Hub makes use of this feature to allow users to write text in a reference field when making transactions. This reference can be seen by the recipient to allow for easier identification and distinction of transactions.\n\n***2. Help Page***\n\nIn Lisk Hub 1.1, we wanted to give users an easy way to get help if they need it. We created a new Help page in the Lisk Hub with links to existing sources — the Lisk Help Center, Lisk Academy, Lisk Chat and specific pages within those sources. The Help page can be easily accessed from the sidebar menu.\n\n***3 & 4. Menu highlight and network switcher designs***\n\nWe also strived to improve the appearance of existing features for aesthetics and usability. The active page is highlighted by a blue stripe on the right side of the menu item. It turns out that this was not sufficient in some user tests. Therefore, in addition to the blue stripe, we also added also a gray background gradient. In addition, we updated the network switcher on the login page. The network switcher was first created as an advanced/developer utility without any regard for the design, because it is not displayed automatically. Eventually, we decided to make this feature discoverable through a switcher in settings. For this reason, we went back to the design table to give the account switcher a proper design that is aligned with the rest of the application.\n\n**[Watch Lisk Hub in 1 Minute!](https://www.youtube.com/watch?v=ktmpnyPaVQo)**\n\nAs [previously announced](https://blog.lisk.io/the-beginning-of-a-new-user-interfaces-journey-at-lisk-d4e09e51d82a), we are working on a mobile version of the Lisk app. To learn more about our plans for Lisk Mobile, watch [Lisk Mobile in 1 Minute](https://www.youtube.com/watch?v=O3enAfHVitA)!\n\n**[Lisk Explorer 2.1.4](https://explorer.lisk.io/)**\n\nLisk Explorer 2.1.4 is compatible with Lisk Core 1.0. However, there are many exciting plans in the works for the future of Lisk Explorer. Please stay tuned for related announcements.\n\n**[Watch Lisk Explorer in 1 Minute!](https://www.youtube.com/watch?v=qdmL9gsPRig)**\n\n**Lisk Nano to Be Discontinued in 2019**\n\nAs the Lisk ecosystem continues to evolve, we’re striving to create the most modern and dynamic versions of all of our products. For this reason, following the release of Lisk Nano 2.0.0, we will not put forth any follow-up releases aside from security patch releases, if necessary. On January 1, 2019, support for this product will no longer be available. However, the repository will remain public and the community will be able to fork it and implement their own features.\n\nThe reason we decided to discontinue Lisk Nano is because we would like to shift our focus exclusively to the new Lisk Hub wallet, which is currently undergoing many improvements. This requires the full, undivided attention from the Lisk Hub team.\n\nOur official [documentation](https://lisk.io/documentation) is a great resource for learning all about the Lisk products, how to use them, how to set up a Lisk node on the network, and much more.\n\nThe road to innovation is rarely smooth — our approach has been methodical and measured, taking no shortcuts along the way. We want to give a huge thank you to our incredible community for supporting us through it all. We will continue delivering only the most secure and high-quality products on our journey towards a fully fledged Lisk ecosystem.\n\n-The Lisk Team\n\n___\n<center>Posted by us also on [![Medium](https://cdn-static-1.medium.com/_/fp/icons/favicon-rebrand-medium.3Y6xpZ-0FSdWDnPM3hSBIA.ico)](https://medium.com/@Lisk) </center>\n___\n\nIs this one of the first posts that you're seeing about Lisk? See more at [Lisk.io](https://lisk.io/) or [Github](https://github.com/LiskHQ/).",
      "json_metadata": "{\"tags\":[\"blockchain\",\"lisk\",\"crypto\",\"developer\",\"javascript\"],\"image\":[\"https://cdn.steemitimages.com/DQmad8udfYhQM9SPWKzhF62UGZHa7SXaT6nTrsKZkomphHq/1_2bfogqp9QePtcONfE3LeQw.png\",\"https://cdn.steemitimages.com/DQmP6U8ua94uAH5rwMJjmsnRWKh1D6eUu5ZdmB5ecRsTbhU/0_equDKC6v3g7NIiVc.png\",\"https://cdn.steemitimages.com/DQmP39zseaTkC9wqSc7q3ngWWyZ56rb4ByBCM1T914pU9d2/0_NRMiHGlZR733l3pZ.png\",\"https://cdn.steemitimages.com/DQmdcByBnv4zi1F1QH1chfCdpw6ppMGL7U3TFVH2XU2u7J6/0_jYS7m-PQiMnt-x-J.png\",\"https://cdn.steemitimages.com/DQmUV2CG73ua7cKVLyaufu1X7XGnXTSP1SSE4eT3S3tw8QD/0_f_mj-saGjWj2L8Vg.png\",\"https://cdn.steemitimages.com/DQmUWmKSco42SPhoAmnkrAV5A3CmD4SMGuhYhXran3pHYoF/0_PMU-M6KddqWGBHgv.png\",\"https://cdn-static-1.medium.com/_/fp/icons/favicon-rebrand-medium.3Y6xpZ-0FSdWDnPM3hSBIA.ico\"],\"links\":[\"https://www.youtube.com/watch?v=RfF9EPwQDOY&t=\",\"https://lisk.io/core\",\"https://www.youtube.com/watch?v=PPVJmbaKcLU&t=1s\",\"https://lisk.io/documentation/lisk-elements\",\"https://www.youtube.com/watch?v=ZEJTa0E9CAk\",\"https://lisk.io/documentation/lisk-commander\",\"https://www.youtube.com/watch?v=XMQRf3-yWf8\",\"https://lisk.io/hub\",\"https://www.youtube.com/watch?v=ktmpnyPaVQo\",\"https://blog.lisk.io/the-beginning-of-a-new-user-interfaces-journey-at-lisk-d4e09e51d82a\",\"https://www.youtube.com/watch?v=O3enAfHVitA\",\"https://explorer.lisk.io/\",\"https://www.youtube.com/watch?v=qdmL9gsPRig\",\"https://lisk.io/documentation\",\"https://medium.com/@Lisk\",\"https://lisk.io/\",\"https://github.com/LiskHQ/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 25525349,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 5,
  "timestamp": "2018-08-30T16:11:54",
  "op": [
    "author_reward",
    {
      "author": "lisk-official",
      "permlink": "development-update-road-to-core-1-0-mainnet-august-23-2018",
      "sbd_payout": "0.000 SBD",
      "steem_payout": "0.041 STEEM",
      "vesting_payout": "82.964794 VESTS"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 25521184,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 5,
  "timestamp": "2018-08-30T12:43:33",
  "op": [
    "author_reward",
    {
      "author": "lisk-official",
      "permlink": "tech-evangelist-rachel-black-joins-lightcurve",
      "sbd_payout": "0.000 SBD",
      "steem_payout": "0.029 STEEM",
      "vesting_payout": "58.682869 VESTS"
    }
  ]
}

{
  "trx_id": "7d51247c4a7f920733ee4c069ae42b12e6cb330c",
  "block": 25443285,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-27T19:45:36",
  "op": [
    "vote",
    {
      "voter": "gniewko",
      "author": "lisk-official",
      "permlink": "lisk-core-1-0-1-patch-release",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "0e99e7b50a1d0fb8c0e141ab557a4872d46c8bf5",
  "block": 25438786,
  "trx_in_block": 50,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-27T16:00:39",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "blockchain",
      "author": "lisk-official",
      "permlink": "lisk-core-1-0-1-patch-release",
      "title": "Lisk Core 1.0.1 Patch Release",
      "body": "![1_u8o1wv6lKv_IpBpXAMBZzA.png](https://cdn.steemitimages.com/DQmSnuTvJBjMcmcpfyyWu2awMNiG51gvHdnC2PtVYCxXST8/1_u8o1wv6lKv_IpBpXAMBZzA.png)\n\nHey Lisk Community,\n\nWe wanted to give node operators, exchanges and other service operators a quick update regarding the migration of Lisk Core 1.0 to Mainnet. We have decided to release a patch, [Lisk Core 1.0.1](https://github.com/LiskHQ/lisk/releases/tag/v1.0.1). It is fully compatible with Lisk Core 1.0.0. It is not mandatory to use the 1.0.1 version for the migration if you are not affected by the issues described below. However, for node operators that are willing to migrate using the Docker image, version 1.0.1 is required.\n\nWe also highly recommend that all exchanges and other service operators (tools, explorers, etc.) use Lisk Core version 1.0.1 rather than version 1.0.0.\n\n**Lisk Core 1.0.1 brings with it two solved issues:**\n\nIssue [#2336](https://github.com/LiskHQ/lisk/issues/2336): The Docker configuration file was outdated, resulting in an inability to migrate using the Docker container platform. For this reason, we fixed the Docker configuration template. We have also updated the relevant section in our documentation —[ Lisk Core Docker Installation](https://lisk.io/documentation/lisk-core/setup/install/docker#mainnet).\n\nIssue [#2201](https://github.com/LiskHQ/lisk/issues/2201): This issue (which was described in detail in the last [development update](https://blog.lisk.io/development-update-road-to-core-1-0-mainnet-august-23-2018-a663e46860d7)) was solved in version 1.2.0, but we decided to include it in this patch release. The */api/transactions* endpoint is incredibly important and is used by various third-party applications using the Lisk Core API. The performance of this endpoint is crucial, especially for exchanges and Lisk Explorer as they heavily utilize this endpoint. The corresponding Lisk Core v1.0.0-rc.3 patch only improving the described performance is available to install on Testnet.\n\nWe’re looking forward to the [migration](https://blog.lisk.io/block-height-announcement-release-of-lisk-core-1-0-0-to-mainnet-55de51f6d9e4) on Wednesday, August 29. The Mainnet migration block height will remain the same — 6,901,027.\n\n-The Lisk Team\n\n___\n<center>Posted by us also on [![Medium](https://cdn-static-1.medium.com/_/fp/icons/favicon-rebrand-medium.3Y6xpZ-0FSdWDnPM3hSBIA.ico)](https://medium.com/@Lisk) </center>\n___\n\nIs this one of the first posts that you're seeing about Lisk? See more at [Lisk.io](https://lisk.io/) or [Github](https://github.com/LiskHQ/).",
      "json_metadata": "{\"tags\":[\"blockchain\",\"lisk\",\"crypto\",\"developer\",\"javascript\"],\"image\":[\"https://cdn.steemitimages.com/DQmSnuTvJBjMcmcpfyyWu2awMNiG51gvHdnC2PtVYCxXST8/1_u8o1wv6lKv_IpBpXAMBZzA.png\",\"https://cdn-static-1.medium.com/_/fp/icons/favicon-rebrand-medium.3Y6xpZ-0FSdWDnPM3hSBIA.ico\"],\"links\":[\"https://github.com/LiskHQ/lisk/releases/tag/v1.0.1\",\"https://github.com/LiskHQ/lisk/issues/2336\",\"https://lisk.io/documentation/lisk-core/setup/install/docker#mainnet\",\"https://github.com/LiskHQ/lisk/issues/2201\",\"https://blog.lisk.io/development-update-road-to-core-1-0-mainnet-august-23-2018-a663e46860d7\",\"https://blog.lisk.io/block-height-announcement-release-of-lisk-core-1-0-0-to-mainnet-55de51f6d9e4\",\"https://medium.com/@Lisk\",\"https://lisk.io/\",\"https://github.com/LiskHQ/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 25430630,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 10,
  "timestamp": "2018-08-27T09:12:54",
  "op": [
    "author_reward",
    {
      "author": "lisk-official",
      "permlink": "lisk-community-builder-bloqspace",
      "sbd_payout": "0.000 SBD",
      "steem_payout": "0.045 STEEM",
      "vesting_payout": "93.098902 VESTS"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 25430347,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 5,
  "timestamp": "2018-08-27T08:58:45",
  "op": [
    "author_reward",
    {
      "author": "lisk-official",
      "permlink": "development-update-road-to-core-1-0-mainnet-august-16-2018",
      "sbd_payout": "0.000 SBD",
      "steem_payout": "0.041 STEEM",
      "vesting_payout": "85.003390 VESTS"
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 25429442,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 11,
  "timestamp": "2018-08-27T08:13:30",
  "op": [
    "author_reward",
    {
      "author": "lisk-official",
      "permlink": "block-height-announcement-release-of-lisk-core-1-0-0-to-mainnet",
      "sbd_payout": "0.000 SBD",
      "steem_payout": "0.051 STEEM",
      "vesting_payout": "103.218577 VESTS"
    }
  ]
}

{
  "trx_id": "a7086c30855ff16ea5db24af53941538567069e5",
  "block": 25361982,
  "trx_in_block": 13,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-24T23:59:06",
  "op": [
    "vote",
    {
      "voter": "gniewko",
      "author": "lisk-official",
      "permlink": "development-update-road-to-core-1-0-mainnet-august-23-2018",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "7456999c58dc793e3e8bfab34fcc21f4fc900539",
  "block": 25331969,
  "trx_in_block": 3,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-23T22:57:06",
  "op": [
    "vote",
    {
      "voter": "cdubendo",
      "author": "lisk-official",
      "permlink": "tech-evangelist-rachel-black-joins-lightcurve",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "ab3a873f5fb2066ac9a6735aa39c934de0b45d4a",
  "block": 25331963,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-23T22:56:48",
  "op": [
    "vote",
    {
      "voter": "cdubendo",
      "author": "lisk-official",
      "permlink": "development-update-road-to-core-1-0-mainnet-august-23-2018",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "9858517f2325dda9326826be1b5b3464e0428f74",
  "block": 25323876,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-23T16:12:09",
  "op": [
    "comment",
    {
      "parent_author": "lisk-official",
      "parent_permlink": "development-update-road-to-core-1-0-mainnet-august-23-2018",
      "author": "cheetah",
      "permlink": "cheetah-re-lisk-officialdevelopment-update-road-to-core-1-0-mainnet-august-23-2018",
      "title": "",
      "body": "Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in:\nhttps://www.hodlalert.com/2018/08/23/development-update-road-to-core-1-0-mainnet-august-23-2018/",
      "json_metadata": ""
    }
  ]
}

{
  "trx_id": "e7b23f4ac052ec20d04879fe6e0d8d877c3612fe",
  "block": 25323874,
  "trx_in_block": 37,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-23T16:12:03",
  "op": [
    "vote",
    {
      "voter": "alphabot",
      "author": "lisk-official",
      "permlink": "development-update-road-to-core-1-0-mainnet-august-23-2018",
      "weight": 100
    }
  ]
}

{
  "trx_id": "750d82aa0f3d12b8e9d635c1ccc08263e95b407a",
  "block": 25323874,
  "trx_in_block": 32,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-23T16:12:03",
  "op": [
    "vote",
    {
      "voter": "cheetah",
      "author": "lisk-official",
      "permlink": "development-update-road-to-core-1-0-mainnet-august-23-2018",
      "weight": 8
    }
  ]
}

{
  "trx_id": "2963c65d6681b687c4a4f951f906725ab5a1c168",
  "block": 25323871,
  "trx_in_block": 20,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-23T16:11:54",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "blockchain",
      "author": "lisk-official",
      "permlink": "development-update-road-to-core-1-0-mainnet-august-23-2018",
      "title": "Development Update — Road to Core 1.0 Mainnet: August 23, 2018",
      "body": "![0_VfUy5xDyL-raWw_S.jpeg](https://cdn.steemitimages.com/DQmdXsxAqoF3DVVVBrtSWZaqBsGzGsUVhKB9rzj2KCxGvGE/0_VfUy5xDyL-raWw_S.jpeg)\n\nHello Lisk Community,\n\nHere at LiskHQ, we’re buckled down and working hard in preparation for the upcoming **Lisk 1.0.0 migration on Mainnet on August 29**. All of the components of the Lisk ecosystem — Lisk Core, Lisk Elements, Lisk Commander and Lisk Hub — are all being updated and aligned with one another for the big migration. In addition to this, the Lisk Core team is also working on future releases.\n\nThe **Lisk Core 1.1.0** quality assurance (QA) phase is now complete. It was a smooth process with no issues.\n\nOur progress on **Lisk Core 1.2.0** is also going very well. Here is a brief overview of the work we’ve done on this release:\n\nIssue [#2201](https://github.com/LiskHQ/lisk/issues/2201): We identified an issue related to the performance of the */api/transactions* endpoint. Previously, in database queries used by this endpoint, we sorted the results by one column only (*timestamp, amount, fee or type*), but we had to add another column to *[ORDER BY](https://www.postgresql.org/docs/9.6/static/queries-order.html)* clause (*rowId*) due to issue [#1884](https://github.com/LiskHQ/lisk/issues/1884). Because of these changes, the PostgreSQL server stopped using indexes and this resulted in significant performance degradation (~20 seconds to get results) while querying the transactions (*trs*) table. Following performance benchmarks, we replaced two existing indexes with eight new ones — which finally decreases queries’ execution time to ~2 milliseconds.\n\nIssue [#2320](https://github.com/LiskHQ/lisk/issues/2320): We replaced IP addresses with [FQDN](https://en.wikipedia.org/wiki/Fully_qualified_domain_name) for seed nodes in *config.json*. We decided to do this because FQDNs are not bound to a particular service provider, therefore this approach gives us more flexibility. For example, we replaced *83.136.254.92* with *mainnet-seed-01.lisk.io*.\n\nIssue [#2323](https://github.com/LiskHQ/lisk/issues/2323): We made a small change in the Swagger schema for the */api/node/status* endpoint. We made the recently-added property *secondsSinceEpoch* mandatory in the API response.\n\nIssue [#2261](https://github.com/LiskHQ/lisk/issues/2261): This issue was already closed, but we identified one case in which we don’t need to update the node’s system headers —* snapshotting*. It is unnecessary during this process because the node is isolated from the network. For this reason, we removed the call to the *modules.system.update* in the corresponding logic.\n\nWe also wanted to take this opportunity to point out that last week, community members running RC2, the latest version of Lisk Core 1.0.0 on Testnet, reported that the memory consumption of their nodes was slowly increasing over time. This caused some child processes within their nodes to crash. The issue was related to peer rejection during the socket handshake phase. Lisk Core is designed to handle such child process crashes, meaning it didn’t have an impact on the overall stability of the Testnet network.\n\nOur development team traced this issue back to the *socketcluster-server* dependency of Lisk Core. It was related to an advanced feature of SocketCluster which allows the Lisk nodes to quickly and efficiently close connections with bad peers (e.g. blacklisted IPs). The SocketCluster server was holding on to memory when the connection was killed at a specific point while in the middle of a *handshake* operation.\n\nWe are recommending all Testnet nodes operators who haven’t upgraded their node’s dependencies yet to make sure to do so and check that the socketcluster-server version is 11.2.2. [Lisk Core 1.0.0](https://github.com/LiskHQ/lisk/releases/tag/v1.0.0) is not affected as all of our builds already contain the fixed versions of the dependency.\n\n**Next steps**\n\nThere are only two pending pull requests left in Lisk Core 1.2.0. They are currently under review. We expect them to be merged this week. Following its completion, we will freeze [Lisk Core 1.2.0](https://github.com/LiskHQ/lisk/projects/63) and start its QA phase next week.\n\nWe have already begun planning the next release. The corresponding milestone, [Lisk Core 1.3.0](https://github.com/LiskHQ/lisk/milestone/31), is already open on GitHub where issues are being added.\n\n-The Lisk Team\n\n___\n<center>Posted by us also on [![Medium](https://cdn-static-1.medium.com/_/fp/icons/favicon-rebrand-medium.3Y6xpZ-0FSdWDnPM3hSBIA.ico)](https://medium.com/@Lisk) </center>\n___\n\nIs this one of the first posts that you're seeing about Lisk? See more at [Lisk.io](https://lisk.io/) or [Github](https://github.com/LiskHQ/).",
      "json_metadata": "{\"tags\":[\"blockchain\",\"lisk\",\"crypto\",\"developer\",\"javascript\"],\"image\":[\"https://cdn.steemitimages.com/DQmdXsxAqoF3DVVVBrtSWZaqBsGzGsUVhKB9rzj2KCxGvGE/0_VfUy5xDyL-raWw_S.jpeg\",\"https://cdn-static-1.medium.com/_/fp/icons/favicon-rebrand-medium.3Y6xpZ-0FSdWDnPM3hSBIA.ico\"],\"links\":[\"https://github.com/LiskHQ/lisk/issues/2201\",\"https://www.postgresql.org/docs/9.6/static/queries-order.html\",\"https://github.com/LiskHQ/lisk/issues/1884\",\"https://github.com/LiskHQ/lisk/issues/2320\",\"https://en.wikipedia.org/wiki/Fully_qualified_domain_name\",\"https://github.com/LiskHQ/lisk/issues/2323\",\"https://github.com/LiskHQ/lisk/issues/2261\",\"https://github.com/LiskHQ/lisk/releases/tag/v1.0.0\",\"https://github.com/LiskHQ/lisk/projects/63\",\"https://github.com/LiskHQ/lisk/milestone/31\",\"https://medium.com/@Lisk\",\"https://lisk.io/\",\"https://github.com/LiskHQ/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}

{
  "trx_id": "f362ebb053013a792d0d5525f8986aca5721addd",
  "block": 25323704,
  "trx_in_block": 3,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-23T16:03:33",
  "op": [
    "vote",
    {
      "voter": "fastresteem",
      "author": "lisk-official",
      "permlink": "tech-evangelist-rachel-black-joins-lightcurve",
      "weight": 100
    }
  ]
}

{
  "trx_id": "b9fe80f06310fcf929391091a4366efa9dbd9c3e",
  "block": 25323700,
  "trx_in_block": 46,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-23T16:03:21",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "blockchain",
      "author": "lisk-official",
      "permlink": "tech-evangelist-rachel-black-joins-lightcurve",
      "title": "Tech Evangelist Rachel Black Joins Lightcurve",
      "body": "@@ -7388,8 +7388,332 @@\n  Berlin!\n+%0A%0A___%0A%3Ccenter%3EPosted by us also on %5B!%5BMedium%5D(https://cdn-static-1.medium.com/_/fp/icons/favicon-rebrand-medium.3Y6xpZ-0FSdWDnPM3hSBIA.ico)%5D(https://medium.com/@Lisk) %3C/center%3E%0A___%0A%0AIs this one of the first posts that you're seeing about Lisk? See more at %5BLisk.io%5D(https://lisk.io/) or %5BGithub%5D(https://github.com/LiskHQ/).\n",
      "json_metadata": "{\"tags\":[\"blockchain\",\"lisk\",\"crypto\",\"developer\",\"javascript\"],\"image\":[\"https://cdn.steemitimages.com/DQmVHcDFEFtuR9SQx8wJYqiBK66rjeGfUy3Y5LXHAgvP9M4/1_66B8Wy4J5O0_x422RjLkIA.jpeg\",\"https://cdn-static-1.medium.com/_/fp/icons/favicon-rebrand-medium.3Y6xpZ-0FSdWDnPM3hSBIA.ico\"],\"links\":[\"https://lisk.io/\",\"https://lisk.io/team\",\"http://www.lightcurve.io/\",\"https://lisk.io/academy\",\"http://blog.lisk.io/\",\"https://lisk.io/events\",\"https://www.youtube.com/playlist?list=PLixm1arf_lEyvtoGBKvpmIpz7NLWA6DSs\",\"https://medium.com/@Lisk\",\"https://github.com/LiskHQ/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}

{
  "trx_id": "9f8c1f4058bab846dca342eff0448d4bf3b5c94f",
  "block": 25321130,
  "trx_in_block": 5,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-23T13:54:42",
  "op": [
    "vote",
    {
      "voter": "sensation",
      "author": "lisk-official",
      "permlink": "tech-evangelist-rachel-black-joins-lightcurve",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "c684eaabd95ec56a325e91b216377a81705388df",
  "block": 25319713,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-23T12:43:48",
  "op": [
    "comment",
    {
      "parent_author": "lisk-official",
      "parent_permlink": "tech-evangelist-rachel-black-joins-lightcurve",
      "author": "cheetah",
      "permlink": "cheetah-re-lisk-officialtech-evangelist-rachel-black-joins-lightcurve",
      "title": "",
      "body": "Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in:\nhttps://blog.lisk.io/tech-evangelist-rachel-black-joins-lightcurve-7740e37db980",
      "json_metadata": ""
    }
  ]
}

{
  "trx_id": "c92ba7bb990007e3a99c8c67bf3319dac4beb2a1",
  "block": 25319711,
  "trx_in_block": 23,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-23T12:43:42",
  "op": [
    "vote",
    {
      "voter": "cheetah",
      "author": "lisk-official",
      "permlink": "tech-evangelist-rachel-black-joins-lightcurve",
      "weight": 8
    }
  ]
}

{
  "trx_id": "175815f47244871b6900d85fb0399366990d06b9",
  "block": 25319711,
  "trx_in_block": 12,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-23T12:43:42",
  "op": [
    "vote",
    {
      "voter": "ax3",
      "author": "lisk-official",
      "permlink": "tech-evangelist-rachel-black-joins-lightcurve",
      "weight": 100
    }
  ]
}

{
  "trx_id": "40199688be789c5ce36a0b48b96ea2a7414b539a",
  "block": 25319708,
  "trx_in_block": 6,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-23T12:43:33",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "blockchain",
      "author": "lisk-official",
      "permlink": "tech-evangelist-rachel-black-joins-lightcurve",
      "title": "Tech Evangelist Rachel Black Joins Lightcurve",
      "body": "![1_66B8Wy4J5O0_x422RjLkIA.jpeg](https://cdn.steemitimages.com/DQmVHcDFEFtuR9SQx8wJYqiBK66rjeGfUy3Y5LXHAgvP9M4/1_66B8Wy4J5O0_x422RjLkIA.jpeg)\n\nMuch has changed at [Lisk](https://lisk.io/) over the last year. What began as a small project with only a handful of developers and visionaries has grown into a movement — a [team](https://lisk.io/team) of over 50 people and a huge, dedicated community. In this spirit, we’d like to welcome **Tech Evangelist Rachel Black** to the [Lightcurve](http://www.lightcurve.io/) team. With her great expertise in both development and community-building, she will work closely with our technology, developers, and the community to educate and inform individuals around the world about Lisk. You’ll be seeing and hearing a lot from her in the future. To better acquaint you with Rachel, we took the opportunity to sit down and chat with her about her previous experiences, how she feels about blockchain and much more.\n\n**Jennifer: Tell me a bit about yourself.**\n\nRachel: I’ve just moved over to Berlin from London, where I grew up. I’ve moved around a fair bit, having lived in a number of places in the UK. I also spent a year in South Korea! I’m really excited to be here in Berlin, especially given its growing reputation as a blockchain hub.\n\n**J: When did you begin your journey that led you to tech evangelism?**\n\nR: I have a background in web development, having worked with React and Node. On the technical side, I really like finding out how things work and learning about new technologies. I’ve been following blockchain for a while, but after partaking in a hackathon last year with people who were working in blockchain, my interest escalated. Since then, I have been really fascinated with the technology and have certainly bored all my friends back home talking about it nonstop! I also began getting more involved with helping organize, and later speaking at events in London. Stepping into the role of Tech Evangelist feels like a natural progression, one that will combine my interest in technology with my involvement with events and communication. Also, as I already mentioned, I really like talking about blockchain, so it is amazing to find a role where it is actually a part of my job!\n\n**J: Why should people care about decentralization and blockchain?**\n\nR: For so many reasons! With the rise of [ICOs](https://lisk.io/academy) (initial coin offerings), we have already seen the potential power of blockchain to disrupt traditional funding methods. I think that as the technology becomes more established and widely-adopted, we will continue to see this disruption across many different sectors. Decentralization is important, but I also like the term “internet of value” as one of the key differences between the internet as we know it and what blockchain offers is the ability to transmit things of value through the network itself. This really changes the nature of how we interact with the internet, and paves the way for innovation. Currently, we are at the beginning of this journey, so it’s difficult to predict exactly what form this innovation will take, but it will certainly be game-changing.\n\n**J: How would you describe Lisk?**\n\nR: Lisk is a third generation blockchain, whose goal is to build technologies that are accessible for both developers (to build on) and users. For blockchain technologies to have a real impact, we need an ecosystem that can support quality [DAPPs](https://lisk.io/academy) (decentralized apps). Lisk is third generation as it builds on the decentralization of Bitcoin (first generation) and Ethereum’s programmability (second generation). Lisk’s area of innovation is building a blockchain which utilizes sidechains to tackle the problem of scalability.\n\n**J: What makes Lisk different from other blockchain projects?**\n\nR: Sidechains are important — last year, we saw how the Ethereum network was overloaded by the CryptoKitties app. For blockchain technology to gain mainstream adoption, solving scalability issues are key. By using sidechains, Lisk can allow DAPP developers to run their app in a more isolated environment (within their own sidechain), but one that also benefits from using the lisk mainchain. For one this means that users will be able to use lisk tokens to pay for goods, services or other transactions in their DAPP (no need get a chain specific token from an exchange). Lisk also focuses on making blockchains as accessible for developers to build on as possible. Part of this is through its choice of language (JavaScript being the native language of the web), but also through Lisk’s commitment to open source. Lisk is also dedicated to increasing blockchain comprehension outside of development, with the Lisk Academy as an informative place to start for anyone new to the industry, whether they come from a technical background or not.\n\n**J: Tell me about a day in the life of a Tech Evangelist.**\n\nR: I’m new to this role, having transitioned from web development. Currently, I am learning as much as I can about the Lisk products, especially Core. This means a lot of reading Github, attending development meetings and getting familiar with running a node. All of this knowledge is then used to help inform the community via [blog posts](http://blog.lisk.io/), [events](https://lisk.io/events) and communication on our social media channels with the Lisk developer community. My role is to bridge the understanding across tech and marketing.\n\n**J: What are you currently working on?**\n\nR: I’m learning as much as I can about the Lisk [blockchain](https://lisk.io/academy). With the upcoming Lisk Core 1.0.0 release, there is certainly lots going on! I’m also in the process of preparing for some events, blog and [vlog](https://www.youtube.com/playlist?list=PLixm1arf_lEyvtoGBKvpmIpz7NLWA6DSs) posts.\n\n**J: What skills and technologies are you the most interested in learning or improving upon?**\n\nR: I really want to learn as much as I can about Lisk’s blockchain, from learning the more technical side (how to run a [node](https://lisk.io/academy), its API, the consensus mechanism) to the role crypto economics play in the ecosystem. I am also really keen to be part of the Lisk community, particularly by attending and speaking at events — it’s great to meet people in person! Overall, I feel really excited to be part of the Lisk journey!\n\n**J: What industry sites and blogs do you read regularly?**\n\nR: For blockchain news, CoinDesk is good. I am also subscribed to the Token Economy, and pretty much all of my Twitter is awash with blockchain content. To keep up with things from a more development-focused perspective, I also look at Hackernews and Hackernoon (in addition to Twitter as well).\n\n**J: What do you like to do in your free time?**\n\nR: Outside of tech, I really enjoy traveling and visiting new places. I’m also into fitness, in particular yoga and spinning. But I also enjoy my fair amount of nightlife and eating out, to counterbalance that!\n\n**J: What is your favorite book and why?**\n\nR: My favorite book is *The Unstoppable Power of Leaderless Organizations* by Oru Brafman, which is a really insightful read on the power of decentralized organizations (interestingly published in 2006, so pre-Bitcoin). Definitely worth a read for anyone who is interested in the space. I’m also getting my teeth into some books on the history of Berlin!",
      "json_metadata": "{\"tags\":[\"blockchain\",\"lisk\",\"crypto\",\"developer\",\"javascript\"],\"image\":[\"https://cdn.steemitimages.com/DQmVHcDFEFtuR9SQx8wJYqiBK66rjeGfUy3Y5LXHAgvP9M4/1_66B8Wy4J5O0_x422RjLkIA.jpeg\"],\"links\":[\"https://lisk.io/\",\"https://lisk.io/team\",\"http://www.lightcurve.io/\",\"https://lisk.io/academy\",\"http://blog.lisk.io/\",\"https://lisk.io/events\",\"https://www.youtube.com/playlist?list=PLixm1arf_lEyvtoGBKvpmIpz7NLWA6DSs\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}

{
  "trx_id": "b0643aea3813e8824fbcb8b0c9932d769f4bc90f",
  "block": 25302749,
  "trx_in_block": 5,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-22T22:35:03",
  "op": [
    "vote",
    {
      "voter": "psionides",
      "author": "lisk-official",
      "permlink": "block-height-announcement-release-of-lisk-core-1-0-0-to-mainnet",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "3c1f788322ba7cddc604e8542132ddc25d9cb4fb",
  "block": 25302747,
  "trx_in_block": 9,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-22T22:34:57",
  "op": [
    "vote",
    {
      "voter": "psionides",
      "author": "lisk-official",
      "permlink": "development-update-road-to-core-1-0-mainnet-august-16-2018",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "56ceb30053c9a0becfebc88fe9bc9dae23461b5d",
  "block": 25302745,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-22T22:34:51",
  "op": [
    "vote",
    {
      "voter": "psionides",
      "author": "lisk-official",
      "permlink": "lisk-community-builder-bloqspace",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 25257795,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 3,
  "timestamp": "2018-08-21T09:07:06",
  "op": [
    "author_reward",
    {
      "author": "lisk-official",
      "permlink": "lisk-commander-1-0-0-release",
      "sbd_payout": "0.000 SBD",
      "steem_payout": "0.031 STEEM",
      "vesting_payout": "64.785428 VESTS"
    }
  ]
}

{
  "trx_id": "e7f8739144ebeccf3667065e9c9b92b69f8aa2b7",
  "block": 25253188,
  "trx_in_block": 9,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-21T05:16:42",
  "op": [
    "vote",
    {
      "voter": "ccoindigger",
      "author": "lisk-official",
      "permlink": "lisk-community-builder-bloqspace",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "382c8d41837dc4e8cac19e0b71577dc2d9c4dd97",
  "block": 25245774,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-20T23:05:57",
  "op": [
    "vote",
    {
      "voter": "gniewko",
      "author": "lisk-official",
      "permlink": "block-height-announcement-release-of-lisk-core-1-0-0-to-mainnet",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "29de4eec0abd881a5f392a66674a5d9e05311850",
  "block": 25233175,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-20T12:35:51",
  "op": [
    "comment",
    {
      "parent_author": "lisk-official",
      "parent_permlink": "lisk-community-builder-bloqspace",
      "author": "steemitboard",
      "permlink": "steemitboard-notify-lisk-official-20180820t123551000z",
      "title": "",
      "body": "Congratulations @lisk-official! You have completed the following 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/@lisk-official) Award for the number of posts published\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 not miss the last post from @steemitboard:**\n[SteemitBoard and the Veterans on Steemit - The First Community Badge.](https://steemit.com/veterans/@steemitboard/steemitboard-and-the-veterans-on-steemit-the-first-community-badge)\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": "7164406abee28f99caa7f30968a9d6267e5c88c4",
  "block": 25229660,
  "trx_in_block": 7,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-20T09:40:00",
  "op": [
    "vote",
    {
      "voter": "zedpal",
      "author": "lisk-official",
      "permlink": "lisk-community-builder-bloqspace",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "05e6203ea0e9bac6958aa6fbeeaf8eb1d488f164",
  "block": 25229510,
  "trx_in_block": 6,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-20T09:32:30",
  "op": [
    "vote",
    {
      "voter": "magpielover",
      "author": "lisk-official",
      "permlink": "development-update-road-to-core-1-0-mainnet-august-16-2018",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "d4fe31d712966e8978ce92be5d82b839cc4eddfa",
  "block": 25229477,
  "trx_in_block": 8,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-20T09:30:51",
  "op": [
    "vote",
    {
      "voter": "tomiscurious",
      "author": "lisk-official",
      "permlink": "lisk-community-builder-bloqspace",
      "weight": 500
    }
  ]
}

{
  "trx_id": "662e7ad6bdf328bc4ae3039462ece0b772915b68",
  "block": 25229130,
  "trx_in_block": 5,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-20T09:13:30",
  "op": [
    "comment",
    {
      "parent_author": "lisk-official",
      "parent_permlink": "lisk-community-builder-bloqspace",
      "author": "cheetah",
      "permlink": "cheetah-re-lisk-officiallisk-community-builder-bloqspace",
      "title": "",
      "body": "Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in:\nhttps://blog.lisk.io/lisk-community-builder-bloqspace-ce11698177d4",
      "json_metadata": ""
    }
  ]
}

{
  "trx_id": "1b67f0f4eb0862a9c54a8472521089f7ef81dda7",
  "block": 25229124,
  "trx_in_block": 33,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-20T09:13:12",
  "op": [
    "vote",
    {
      "voter": "cheetah",
      "author": "lisk-official",
      "permlink": "lisk-community-builder-bloqspace",
      "weight": 8
    }
  ]
}

{
  "trx_id": "4812be1f95ae51f7f1170831b27cd04120d7c4b5",
  "block": 25229118,
  "trx_in_block": 22,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-20T09:12:54",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "blockchain",
      "author": "lisk-official",
      "permlink": "lisk-community-builder-bloqspace",
      "title": "Lisk Community Builder — BLOQspace",
      "body": "![1_Bo_c2W3YtL-2r_Z-e2NNsA.png](https://cdn.steemitimages.com/DQmatW7j6oyAmuAWqA2m6RhVCpsGEhaCGCahgvwP9hdvNyd/1_Bo_c2W3YtL-2r_Z-e2NNsA.png)\n\nWithin the blockchain industry exists a distinct phenomenon that does not typically occur elsewhere. Unlike many other industries, the blockchain space, with its open source and transparency-first mindset, fosters the growth of large-scale communities which dedicate a great deal of time and effort into spreading awareness. [Lisk](https://lisk.io/) is honored to be one project with strong community support in many regards.\n\nOne such Lisk community-builder is US-based BLOQspace. Primarily founded by entrepreneurs, programmers, and blockchain enthusiasts, BLOQspace’s main goal is to support the adoption of blockchain and JavaScript development by providing free education channels including brick and mortar BLOQspace locations complete with JavaScript learning modules. We asked the team a few questions to get to know them a bit better and hear about upcoming plans.\n\n**What drew the BLOQspace team to Lisk?**\n\nAside from the many positive facets of the Lisk team, the DPoS consensus, and the focus on JavaScript, the tipping factor for us was definitely the community-focus of the platform. As several members of BLOQspace come from a professional sports background, the opportunity to be an actively contributing part of a strong group working towards a common goal rang very true with us.\n\n**What do you feel is the potential of blockchain technology?**\n\nThe unbanked and underbanked segment of society represent about a quarter of the world’s population. Blockchain has the potential to make a revolutionary impact on this demographic, which in turn will bring about many positive changes in the world. If the technology can help get people out of poverty and desperation, it will create a whole new generation of world influencers.\n\n**What has been your experience fostering a Lisk/blockchain community in the US? Are many people interested in becoming blockchain developers and implementing blockchain technology to their various industries?**\n\nAs a result of consistent interaction with the Lisk and greater blockchain community around the world, we have gathered some key insights about people and the general findings are that people want to be involved with something that is bigger themselves. They also want freedom and a supportive community with which they can be involved at their leisure, but also nurture their growth at a pace that comfortable for them. This has molded our approach to community building with dedicated centers, frequent meetups and a strong presence at industry events.\n\n![1_tHNcJWrcap5LDZAJlpt7JA.jpeg](https://cdn.steemitimages.com/DQmcGbWhc1orn5vBqQmxm5Jg5rvAf9WQa7aQN2sw5CNUqv1/1_tHNcJWrcap5LDZAJlpt7JA.jpeg)\n\n**BLOQspace has already done so much for the Lisk community. What plans does BLOQspace have for the rest of the year?**\n\nWe are really trying to set the benchmark for community involvement in the blockchain industry. We are grateful to the Lisk community for granting us this opportunity. In the short term, we will ramp up the frequency of meetups and sponsorships from us. We also have an outstanding open invitation to partner with other Lisk community members who would like to host meetups or events in their cities. In the medium-term, we are working on translating and formatting the Lisk Academy coursework into 140 different languages so that we can create and distribute books to people around the world to help as many people as possible to access the potential of financial freedom via blockchain education. Our long term plan is to continue to ramp up our efforts. Our goals are to launch other major initiatives including:\n\nEstablishing a bi-annual Lisk Symposium where Lisk community members can engage with one another as well as with Lisk sidechain projects, with a main focus on peer review. We also want to further educate people with workshops on how to run and maintain a node, to professional speech training, to social media marketing coaching. Given our real estate development background, we would like to build schools focused on Science, Technology, Engineering and Math (STEM) education that will include a blockchain curriculum.\n\nWe also want to launch a charity called DPoSitivity (pronounced The Positivity). This organization will be run like the “Make A Wish” Foundation, whereby bi-annually, we will be granting the last wish of a terminally-ill child. Being a transparent blockchain based entity, every donor will see their contributions as they are received and as they are used to make the child’s dream come true.\n\n**You’ve sponsored and hosted so many successful Lisk Meetups. Can you tell us a little bit about your experience with meetups?**\n\nAs a serial Lisk Meetup participator and organizer, we have have seen the gamut of Lisk events, from the 300+ person relaunch to the cozy 20-person function. The general demographic as we see it is Lisk fans and people who just want to learn about blockchain. Crypto is such a political and polarized industry, that unless there is a co-sponsoring of an event, there is never a real presence of general blockchain enthusiasts; which is a segment of the blockchain population that we would like to attract. Our plan to help steer this demographic by creating a more open and inviting event with entertainment, interaction, swag and crypto giveaways.\n\n**I love the sound of these Lisk education centers. Can you tell us a little bit more about them?**\n\nWe actually have three Lisk Education Centers. There are two in Texas and one in Puerto Rico — the island that received their first-ever crypto ATM as a donation from us. Our centers focus on Lisk immersion and hands-on engagement. As soon you walk into these education centers, you are greeted by Lisk banners, swag, as well as monitors overhead that display the Lisk Academy, Crypto Tickers, and YouTube videos about blockchain technology. We have computers to allow us to work with people one-on-one to set up crypto wallets, use exchanges, and learn how to code. We also utilize Kano kits to help kids learn how to code. Our San Antonio center also has a large classroom where we hold meetups and give presentations. Currently, we teach the Lisk Academy in English, Spanish, Hindi, and Farsi. Our center is also utilized by other local blockchain and technology groups as a center to host meetups as well. In addition, one of the most unique offerings is our mining lab, where we have a room with ASIC and GPU miners dedicated to teaching the community first-hand about crypto mining and how to operate and maintain miners. The Lisk Education center is also home to our Lisk Community JavaScript Workshop where we are cultivating an in-depth curriculum for the JS Foundation (we also sit on this foundation’s board). The curriculum features a comprehensive guide to learning JavaScript and its implementation in blockchain via the Lisk technology.\n\n___\n<center>Posted by us also on [![Medium](https://cdn-static-1.medium.com/_/fp/icons/favicon-rebrand-medium.3Y6xpZ-0FSdWDnPM3hSBIA.ico)](https://medium.com/@Lisk) </center>\n___\n\nIs this one of the first posts that you're seeing about Lisk? See more at [Lisk.io](https://lisk.io/) or [Github](https://github.com/LiskHQ/).",
      "json_metadata": "{\"tags\":[\"blockchain\",\"lisk\",\"crypto\",\"developer\",\"javascript\"],\"image\":[\"https://cdn.steemitimages.com/DQmatW7j6oyAmuAWqA2m6RhVCpsGEhaCGCahgvwP9hdvNyd/1_Bo_c2W3YtL-2r_Z-e2NNsA.png\",\"https://cdn.steemitimages.com/DQmcGbWhc1orn5vBqQmxm5Jg5rvAf9WQa7aQN2sw5CNUqv1/1_tHNcJWrcap5LDZAJlpt7JA.jpeg\",\"https://cdn-static-1.medium.com/_/fp/icons/favicon-rebrand-medium.3Y6xpZ-0FSdWDnPM3hSBIA.ico\"],\"links\":[\"https://lisk.io/\",\"https://medium.com/@Lisk\",\"https://github.com/LiskHQ/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}

{
  "trx_id": "81d9e4d5f19cec3b527d381445d622659d6c06e3",
  "block": 25229084,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-20T09:11:12",
  "op": [
    "vote",
    {
      "voter": "golgo-13",
      "author": "lisk-official",
      "permlink": "development-update-road-to-core-1-0-mainnet-august-16-2018",
      "weight": 800
    }
  ]
}

{
  "trx_id": "6d02e10afdea44af413ee8704977715b716e0f12",
  "block": 25228872,
  "trx_in_block": 9,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-20T09:00:36",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "blockchain",
      "author": "lisk-official",
      "permlink": "block-height-announcement-release-of-lisk-core-1-0-0-to-mainnet",
      "title": "Block Height Announcement — Release of Lisk Core 1.0.0 to Mainnet",
      "body": "@@ -5767,8 +5767,332 @@\n isk Team\n+%0A%0A___%0A%3Ccenter%3EPosted by us also on %5B!%5BMedium%5D(https://cdn-static-1.medium.com/_/fp/icons/favicon-rebrand-medium.3Y6xpZ-0FSdWDnPM3hSBIA.ico)%5D(https://medium.com/@Lisk) %3C/center%3E%0A___%0A%0AIs this one of the first posts that you're seeing about Lisk? See more at %5BLisk.io%5D(https://lisk.io/) or %5BGithub%5D(https://github.com/LiskHQ/).\n",
      "json_metadata": "{\"tags\":[\"blockchain\",\"lisk\",\"crypto\",\"developer\",\"javascript\"],\"image\":[\"https://cdn.steemitimages.com/DQmRfHdjSkCq3BVFNqPJAh8hTQgYSSv21FUy8AFkCCnD3dW/1_1X2lEvep2bOPuqfCykzRSg.jpeg\",\"https://cdn.steemitimages.com/DQmdaNBir5GL6gPdgtA5ATgS7YzzugfWmz3sTsapjUqRLGJ/1_lD1vaSRJJ-tGBK0uNX_aXA.png\",\"https://cdn-static-1.medium.com/_/fp/icons/favicon-rebrand-medium.3Y6xpZ-0FSdWDnPM3hSBIA.ico\"],\"links\":[\"https://lisk.io/documentation/lisk-core/user-guide/api/1-0\",\"https://blog.lisk.io/\",\"https://runkit.com/lisk/lisk-core-migration-block-height\",\"https://lisk.chat/channel/network\",\"https://lisk.io/documentation\",\"https://lisk.io/documentation/lisk-core/upgrade/migration\",\"https://lisk.io/documentation/lisk-core/user-guide/api/0-9-vs-1-0\",\"https://medium.com/@Lisk\",\"https://lisk.io/\",\"https://github.com/LiskHQ/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}

{
  "trx_id": "1ee4da778add0bb841c4a1cbe8c2995771b45c12",
  "block": 25228839,
  "trx_in_block": 28,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-20T08:58:57",
  "op": [
    "comment",
    {
      "parent_author": "lisk-official",
      "parent_permlink": "development-update-road-to-core-1-0-mainnet-august-16-2018",
      "author": "cheetah",
      "permlink": "cheetah-re-lisk-officialdevelopment-update-road-to-core-1-0-mainnet-august-16-2018",
      "title": "",
      "body": "Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in:\nhttps://blog.lisk.io/development-update-road-to-core-1-0-mainnet-august-16-2018-e82d8e105d07",
      "json_metadata": ""
    }
  ]
}

{
  "trx_id": "c9528d2e51b1f40790602c2a44920b7740c7b831",
  "block": 25228838,
  "trx_in_block": 13,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-20T08:58:54",
  "op": [
    "vote",
    {
      "voter": "cheetah",
      "author": "lisk-official",
      "permlink": "development-update-road-to-core-1-0-mainnet-august-16-2018",
      "weight": 8
    }
  ]
}

{
  "trx_id": "6371c420790576d5c850cf4d2199342d8966e6cd",
  "block": 25228835,
  "trx_in_block": 17,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-20T08:58:45",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "blockchain",
      "author": "lisk-official",
      "permlink": "development-update-road-to-core-1-0-mainnet-august-16-2018",
      "title": "Development Update — Road to Core 1.0 Mainnet: August 16, 2018",
      "body": "![0_dyLhWO0FNMr835ej.jpeg](https://cdn.steemitimages.com/DQmWcwmNzNf96ZHeoPifDmtfXsraDasX9pKfRPGmT2bGDwU/0_dyLhWO0FNMr835ej.jpeg)\n\nHello Lisk Community,\n\nAs you may already know, we recently [announced](https://blog.lisk.io/block-height-announcement-release-of-lisk-core-1-0-0-to-mainnet-55de51f6d9e4) the block height for the **Lisk Core 1.0.0** migration on Mainnet. In case you missed it, the height is **6,901,027** and the actual migration will happen on **Wednesday, August 29, no sooner than 11:00 AM CEST.**\n\nTogether with the imminent Mainnet release, our development team recently reached another great milestone — merging more than 1,000 pull requests! We’re very excited about this and look forward to many, many more.\n\nIn regards to the **Lisk Core 1.1.0** quality assurance (QA) phase — it is almost complete. Scenarios were executed successfully without the detection of any issues. We’re currently only awaiting snapshotting and syncing from scratch tests, as those take longest to complete.\n\nOver the last week, the development team made significant progress on one of the next releases — **Lisk Core 1.2.0**. Here is a brief overview of the work we’ve done:\n\nIssue [#2278](https://github.com/LiskHQ/lisk/issues/2278): Lisk Core uses *config.json* as the main configuration file. The structure of this file can change in every release, as we’re constantly adding new features and improving the codebase. However, users need to have this file customized and because of this, we’re maintaining the *update_config.js* script, which performs an automated migration of *config.json*, preserving all the users’ custom changes. This script was not flexible, as it was only able to perform the migration from one version to another. In order to solve this inconvenience, the *update_config.js* script was rewritten to support the migration between any versions. This masterpiece was designed and implemented by one of our talented backend developers, [Nazar Hussain](https://github.com/nazarhussain). Now it is very easy to migrate your configuration. For example, you can do it from version 0.9.16 to version 1.2.0 by running the following command:\n\n**node scripts/update_config.js ../config.json 0.9.16 1.2.0**\n\nIssue [#2261](https://github.com/LiskHQ/lisk/issues/2261): One of our dedicated community members, [Simon Warta](https://github.com/webmaster128), reported an issue regarding inconsistent data returned between the P2P layer endpoint *rpc.status* and API endpoint *api/node/status*. Some data, such as *height* and *broadhash* were not updated in the *rpc.status* response. This happened when the node was in the synchronization process. We fixed this issue by updating the node’s headers after every block, regardless of whether or not the node is in the synchronization process.\n\nIssue [#1733](https://github.com/LiskHQ/lisk/issues/1733): We extended the API *node/status* endpoint by adding two useful properties:\n\n* *currentTime*, which returns the current time of the node in milliseconds (unix timestamp)\n* *secondsSinceEpoch*, which returns the number of seconds that have elapsed since the Lisk Epoch (2016–05–24T17:00:00.000Z)\n\nIssue [#2237](https://github.com/LiskHQ/lisk/issues/2237): To extend Lisk Core’s flexibility and compatibility with platforms not natively supported by us, we’re utilizing Docker. We have a special repository — *lisk-docker* — in which we keep configuration files for Docker. But because we’re supporting multiple networks with one installation from Lisk Core 1.1.0, we decided to move all Docker-related files into the [lisk](https://github.com/LiskHQ/lisk) repository and following that, archive *lisk-docker*. This pull request resolved the last step of this process — moving *docker-compose.yml* file.\n\nIssue [#1822](https://github.com/LiskHQ/lisk/issues/1822): Behavior of the *checkConfirmed* function from *logic/transactions* module wasn’t following best practices and resulted in confusion. The function returned an error when the transaction was confirmed (it exists in the database). We refactored it to return the actual result (*true* or *false*) and an error only when database query fails.\n\nIssue [#2274](https://github.com/LiskHQ/lisk/issues/2274): We removed the following tests out of our integration test suite:\n\n* stress tests — this involves sending a massive number of transactions (of various types)\n* sync only — testing block propagation with disabled block broadcasting\n* broadcast only — which tests block propagation with a disabled syncing mechanism\n\nThe reasoning behind these removals is that we already have these tests as part of our QA process, and they are already automatically executed during nightly builds.\n\nIssue [#2273](https://github.com/LiskHQ/lisk/issues/2273): To keep our test suite reliable, we renamed some of the test directories, realizing that their original names did not accurately reflect their functionalities. The following changes were made:\n\n* *integration to network*\n* *system to integration*\n\nIssue [#2225](https://github.com/LiskHQ/lisk/issues/2225): Previously, we were supporting only a subset of configuration options to be set through the ENV (environment) variables. This approach was not flexible; for example, they were not enough to run the Docker image. For that reason, we greatly extended support for ENV variables. You can check which variables are supported in Lisk Core 1.2.0 by reading the [Command Line Options](https://github.com/LiskHQ/lisk/tree/1.2.0#command-line-options) section of the corresponding *README.md* file.\n\nIssue [#2254](https://github.com/LiskHQ/lisk/issues/2254): We had another issue reported by community member [Corsaro](https://github.com/corsaro1). He discovered a bug in the processing of signatures for transactions sent from multisignature accounts. In some cases, like for example an overloaded node, this bug resulted in duplicated signatures added to *transaction* object in the transaction pool. After investigating, we discovered that the problem lies in the *processSignature* function of the *multisignatures* module and it was caused by the execution of only a part of its logic via *balancesSequence* (tasks queue responsible for synchronous processing of balances-related operations). We rewrote the *processSignature* function, also adding a complete test coverage for it. We’re proud of our native support for multisignature accounts, as this is not very common with other blockchains. In the future, we’re going to further improve the implementation and fix issues related to the propagation of signatures.\n\n**Next steps**\n\nWhile we wait for the Lisk Core 1.0.0 migration on Mainnet, we will continue to work hard on the upcoming releases. There are plenty of issues left for [Version 1.2.0](https://github.com/LiskHQ/lisk/projects/63) and as always, you can track the progress of this release on GitHub. Both Lisk Core 1.1.0 and 1.2.0 versions, while minor, are still very important, as they bring about many bug fixes and great improvements. Having a stable and reliable network is not only fundamental but mandatory for achieving our goals.\n\n-The Lisk Team\n\n___\n<center>Posted by us also on [![Medium](https://cdn-static-1.medium.com/_/fp/icons/favicon-rebrand-medium.3Y6xpZ-0FSdWDnPM3hSBIA.ico)](https://medium.com/@Lisk) </center>\n___\n\nIs this one of the first posts that you're seeing about Lisk? See more at [Lisk.io](https://lisk.io/) or [Github](https://github.com/LiskHQ/).",
      "json_metadata": "{\"tags\":[\"blockchain\",\"lisk\",\"crypto\",\"developer\",\"javascript\"],\"image\":[\"https://cdn.steemitimages.com/DQmWcwmNzNf96ZHeoPifDmtfXsraDasX9pKfRPGmT2bGDwU/0_dyLhWO0FNMr835ej.jpeg\",\"https://cdn-static-1.medium.com/_/fp/icons/favicon-rebrand-medium.3Y6xpZ-0FSdWDnPM3hSBIA.ico\"],\"links\":[\"https://blog.lisk.io/block-height-announcement-release-of-lisk-core-1-0-0-to-mainnet-55de51f6d9e4\",\"https://github.com/LiskHQ/lisk/issues/2278\",\"https://github.com/nazarhussain\",\"https://github.com/LiskHQ/lisk/issues/2261\",\"https://github.com/webmaster128\",\"https://github.com/LiskHQ/lisk/issues/1733\",\"https://github.com/LiskHQ/lisk/issues/2237\",\"https://github.com/LiskHQ/lisk\",\"https://github.com/LiskHQ/lisk/issues/1822\",\"https://github.com/LiskHQ/lisk/issues/2274\",\"https://github.com/LiskHQ/lisk/issues/2273\",\"https://github.com/LiskHQ/lisk/issues/2225\",\"https://github.com/LiskHQ/lisk/tree/1.2.0#command-line-options\",\"https://github.com/LiskHQ/lisk/issues/2254\",\"https://github.com/corsaro1\",\"https://github.com/LiskHQ/lisk/projects/63\",\"https://medium.com/@Lisk\",\"https://lisk.io/\",\"https://github.com/LiskHQ/\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}

{
  "trx_id": "c8e9f1fccdd5deb09c54bf0ce272ded477efbeb0",
  "block": 25227995,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-20T08:16:42",
  "op": [
    "vote",
    {
      "voter": "harrisshirleyss",
      "author": "lisk-official",
      "permlink": "block-height-announcement-release-of-lisk-core-1-0-0-to-mainnet",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "56133383d5c8be9500d39b8e86de8b17baa243fd",
  "block": 25227937,
  "trx_in_block": 12,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-20T08:13:48",
  "op": [
    "comment",
    {
      "parent_author": "lisk-official",
      "parent_permlink": "block-height-announcement-release-of-lisk-core-1-0-0-to-mainnet",
      "author": "cheetah",
      "permlink": "cheetah-re-lisk-officialblock-height-announcement-release-of-lisk-core-1-0-0-to-mainnet",
      "title": "",
      "body": "Hi! I am a robot. I just upvoted you! I found similar content that readers might be interested in:\nhttps://blog.lisk.io/block-height-announcement-release-of-lisk-core-1-0-0-to-mainnet-55de51f6d9e4",
      "json_metadata": ""
    }
  ]
}

{
  "trx_id": "f0db0d420d154e5e3707655ff96f564d32a220ac",
  "block": 25227935,
  "trx_in_block": 50,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-20T08:13:42",
  "op": [
    "vote",
    {
      "voter": "cheetah",
      "author": "lisk-official",
      "permlink": "block-height-announcement-release-of-lisk-core-1-0-0-to-mainnet",
      "weight": 8
    }
  ]
}

{
  "trx_id": "bebf34f490240e963bf638f7e499d8dfb59f6d67",
  "block": 25227931,
  "trx_in_block": 36,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-08-20T08:13:30",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "blockchain",
      "author": "lisk-official",
      "permlink": "block-height-announcement-release-of-lisk-core-1-0-0-to-mainnet",
      "title": "Block Height Announcement — Release of Lisk Core 1.0.0 to Mainnet",
      "body": "![1_1X2lEvep2bOPuqfCykzRSg.jpeg](https://cdn.steemitimages.com/DQmRfHdjSkCq3BVFNqPJAh8hTQgYSSv21FUy8AFkCCnD3dW/1_1X2lEvep2bOPuqfCykzRSg.jpeg)\n\nHello Lisk Community,\n\nOur biggest milestone to date is nearly here. We are very happy to announce that the major release of Lisk Core 1.0 is ready to reach the main network, Mainnet.\n\n**The migration of Lisk Core 1.0 to Mainnet will happen when we reach block height 6,901,027 at the end of round 68327. We expect this block height to arrive on Wednesday, August 29, no sooner than 11:00 AM CEST (Important: all the times are approximate).**\n\nFollowing this date, Lisk Mainnet nodes must be upgraded to Lisk Core 1.0, leaving behind the old version, Lisk Core 0.9.16.\n\n**Why Lisk Core 1.0 Is Important**\n\nThere are a number of reasons why the milestone of Lisk Core 1.0 is so important to us. To get here, we employed the efforts of dozens of contributors from LiskHQ and the greater Lisk community — we had over 8,000 commits and over 1,000 issues closed with thousands of peer reviews. This is our first release that has included our new and greatly improved Quality Assurance (QA) process. The Betanet phase lasted several months to ensure top code quality and stability; we also successfully executed two Testnet migrations.\n\nWith Lisk Core 1.0 comes a new [API design](https://lisk.io/documentation/lisk-core/user-guide/api/1-0), a new P2P communication layer, and additional features such as an entirely new data field that provides you with the option to include a custom message with your transaction. It also includes atomic block writes, structured test suites and code migrated to JavaScript ES6.\n\n**Dependent Product Compatibilities**\n\nAll of the products in the Lisk ecosystem have been aligned for compatibility with the new API. Each product has bumped its version, publishing code to adapt to the latest version of Lisk Core. You can find several blog posts about the updated products on the [Lisk Blog](https://blog.lisk.io/). We’ve also collected and placed all of the related information into a table showing the specific tags below:\n\n![1_lD1vaSRJJ-tGBK0uNX_aXA.png](https://cdn.steemitimages.com/DQmdaNBir5GL6gPdgtA5ATgS7YzzugfWmz3sTsapjUqRLGJ/1_lD1vaSRJJ-tGBK0uNX_aXA.png)\n\nLisk Core, in turn, has also updated the utilized version of Lisk Elements to the latest published version v1.0.0, since Lisk Elements is a dependency of Lisk Core in both test and production environments. All of our products are now on the same page.\n\n**How We Established the Block Height for Migration**\n\nIn order to choose the ideal date and time for migration, we took a variety of factors into account — resources, timeframes, buffers, possible missed blocks, exchanges, ecosystem alignment, community and many more variables.\n\nWe then created a [script](https://runkit.com/lisk/lisk-core-migration-block-height) to accurately estimate which block will happen around the chosen date. The calculation directly depends on the missed blocks per round, which is unpredictable. This is why our calculation assumes the ideal case of no missed blocks between the day we calculated the height and the day when the height is actually reached. Under this premise, our team is to remain unoccupied during this window of time.\n\nAs mentioned earlier, the migration of Lisk Core 1.0 to Mainnet will happen when we reach block height 6,901,027, which is expected to arrive on Wednesday, August 29, no sooner than 11:00 AM CEST. However, upon reading data from the blockchain and comparing it to the number of missed blocks during the last few months and the number of missed blocks from the version 0.9.16 in total, we came up with a factor between 0.16 and 0.26 missed blocks per round. These factors imply that a more realistic time for the picked height will be around 12:00 PM CEST. In an effort to maintain transparency, we decided to publish the [script](https://runkit.com/lisk/lisk-core-migration-block-height) which has been audited by the team. This way, you can play with and check several estimations depending on the number of missed blocks per round.\n\nAs the block height gets closer, we will be able to have a more accurate time. However, the height remains fixed.\n\n**What’s next?**\n\n* **On August 29, our engineering team will be on hand to help orchestrate and monitor the migration process**\n* **We will publicly communicate any updates/changes in the number of missed blocks as well as a more precise time we expect to reach block height 6,901,027 on August 29**\n* **We will maintain close contact with exchanges to ensure minimal disruption to deposits and withdrawals**\n\n**Recommendations**\n\nPlease avoid making any transactions during the 24 hours prior to and after the migration. For exchanges, we also recommend not accepting withdrawals/deposits 24 hours prior to and after the migration as well. However, we cannot enforce this, as Lisk Network is fully decentralized and everyone in the community is free to post any transactions that they wish to at anytime.\n\nDuring the migration, we recommend stakeholders to direct any questions to the network channel in [Lisk chat](https://lisk.chat/channel/network).\n\nPlease read our official [documentation](https://lisk.io/documentation) with a special focus on:\n\n* [Lisk Core Migration Guide](https://lisk.io/documentation/lisk-core/upgrade/migration)\n* [The New API 1.0](https://lisk.io/documentation/lisk-core/user-guide/api/1-0)\n* [Lisk API 0.9 vs API 1.0](https://lisk.io/documentation/lisk-core/user-guide/api/0-9-vs-1-0)\n\nWe are excited for this transition and expect it to go smoothly, however, if any unforeseen changes occur, we will keep the community informed throughout this time. Thank you again to the Lisk community for the continued support!\n\n-The Lisk Team",
      "json_metadata": "{\"tags\":[\"blockchain\",\"lisk\",\"crypto\",\"developer\",\"javascript\"],\"image\":[\"https://cdn.steemitimages.com/DQmRfHdjSkCq3BVFNqPJAh8hTQgYSSv21FUy8AFkCCnD3dW/1_1X2lEvep2bOPuqfCykzRSg.jpeg\",\"https://cdn.steemitimages.com/DQmdaNBir5GL6gPdgtA5ATgS7YzzugfWmz3sTsapjUqRLGJ/1_lD1vaSRJJ-tGBK0uNX_aXA.png\"],\"links\":[\"https://lisk.io/documentation/lisk-core/user-guide/api/1-0\",\"https://blog.lisk.io/\",\"https://runkit.com/lisk/lisk-core-migration-block-height\",\"https://lisk.chat/channel/network\",\"https://lisk.io/documentation\",\"https://lisk.io/documentation/lisk-core/upgrade/migration\",\"https://lisk.io/documentation/lisk-core/user-guide/api/0-9-vs-1-0\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}