Updated Details lisk

  • Features

    Many awesome features we’d like to show you

    Blockchain Applications

    Apps of All Kinds

    Blockchain apps are set to disrupt the whole application market. They are based on blockchain technology resulting in an 100% runtime. At Lisk you can develop your own blockchain apps with modern web technologies like HTML5, CSS3 and JavaScript.

    App Directory

    An aggregation of all blockchain apps published

    on the Lisk network, the App Directory will help you find anything, from games

    over simple tools, to powerful financial apps

    Blockchain Applications


    One Chain for every Blockchain App

    Every blockchain app is running in its own and unique sidechain - a blockchain you can fully customise. Encapsulating the blockchain app sidechains from the main blockchain of Lisk keeps the network lean, efficient, and fast.


    The blockchain app developer has complete control over the sidechain. He can fully customise it to his needs, by default the sidechain is running on our version of Delegated-Proof-of-Stake with a maximum of 101 master nodes.


    Intuitive User Experience

    The Lisk client has been built from the ground

    up to provide an easy to use, intuitive interface. By simplifying the typical

    wallet experience, Lisk provides a user experience that is second to none

    Convenient for Everyone

    Lisk was built with you in mind. By utilizing core apps for user profiles and unique identities, managing your presence in the Lisk network is an intuitive and modern experience.

    See for Yourself



    Second Passphrase

    As an added security measure, Lisk allows users to set a second passphrase on their account. In the event that your first passphrase is compromised, your second passphrase is still required for every transaction.

    Multi-Signature Groups

    To provide maximum security for startups and individual users we implemented multi-signature transaction authentication. You can create a multi-signature group with up to 16 accounts and configure it to your needs.


    Open Source

    The Lisk Team is a strong supporter of open source software. Due to the fact that Lisk is also a financial platform, it is self-evident that the source code is public for everyone. If you want to work on Lisk please get in contact with us, we will gladly integrate you in our development process.

    // Blockchain Application ============

    var sandbox = process.binding('sandbox');


    call: "dapps#receive",

    args: {body: "Hello Lisk!"}


    sandbox.onMessage(function (msg, cb) {

    console.log("receive message from lisk", msg.body);



    // lisk ======================

    var sandbox = new Sandbox("index.js", dappId, function (msg, cb) {

    console.log("receive message from dapp " + dappId, msg.body);


    }, true);

    sandbox.sendMessage({body: "Hello World!"});


    Source Code


    • Block Time: 10 seconds
    • Round Time: ~17 minutes
    • Confirmations for Final Transaction: 6-10
    • Supply: 100 million LISK + Forging Rewards (currently 5 LISK per block)
    • Consensus System: Delegated Proof-of-Stake (DPOS)
    • Lisk's official ticker: LSK
    • Lisk's official currency symbol: Ⱡ


    Lisk v0.3.1

    The full Lisk client for delegates, developers and users alike. Allows delegate forging, provides blockchain download and includes the complete API. At this moment there are only clients for technical users available. One-click clients will follow in the future.


    Please use our Docker Image to install Lisk v0.3.1 on Windows.

    Installation Instructions

    Mac OS X

    • Delegate Support
    • Blockchain download
    • API available

    Installation Instructions


    • Delegate Support
    • Blockchain download
    • API available

    Installation Instructions

    Docker Image

    • For Windows, Mac OS X and Linux
    • All functionality included
    • In one simple Docker Image

    Installation Instructions

    ARM v6

    • For ARM v6 based computers like:
    • Raspberry Pi Zero
    • Raspberry Pi 1

    Installation Instructions

    ARM v7

    • For ARM v7 based computers like:
    • C.H.I.P.
    • Raspberry Pi 2

    Installation Instructions

    Development Tools

    Every Node.js and JavaScript developer can create and deploy his own blockchain application in its own sidechain onto the Lisk network.

    Lisk CLI

    • Lisk Command-Line Interface
    • Develop blockchain apps
    • Create your own local testnet

    More Info

    App SDK

    • Provides basic app structure
    • Used to develop your own app



    • Stand-alone client to access the chat
    • Based on Electron


    Mac OS X

    • Stand-alone client to access the chat
    • Based on Electron



    • Stand-alone client to access the chat
    • Based on Electron


    Old versions

    Please don't use any old version in production.

    Block Explorer:


















    [table][tr][td][url=https://lisk.io][font=Arial Black][size=28pt][color=#111][b]L[color=#222]I[color=#333]S[color=#444]K[/td]
    [td][font=monospace][size=2pt]                 [color=#000000]▄▄   ▄▄[/color]
                    [color=#000000]▄▀ ▀▀█  █[/color]
                   [color=#000000]▄▀     ▀▀[/color]
       [color=#000000]▄▀▄▀              ▀▄▀▄[/color]
      [color=#000000]█  █   [color=red]▄█▄    ▄█▄[/color]   █  █[/color]
       [color=#000000]▀█    [color=red]▀█▀    ▀█▀[/color]    █▀[/color]
        [color=#000000]█                  █[/color]
         [color=#000000]█   ▀▄      ▄▀   █[/color]
          [color=#000000]▀▄   ▀▀▀▀▀▀   ▄▀[/color]
        [color=#32ccfe]▄▀▄              ▄▀▀   ▀▀▄[/color]
        [color=#32ccfe]▀▄ ▀▀▄▄         █     ▄   ▀▀█▀[/color]
          [color=#32ccfe]▀▄▄  ▀▀▄▄     █         █▀[/color]
          [color=#32ccfe]▀▄ ▀     ▀▀▄▄▀         █[/color]
           [color=#32ccfe]▄▀▀▄                  █[/color]
            [color=#32ccfe]▀▄▄                 █[/color]
      [color=#32ccfe]▀█▄▄     ▀▄              █[/color]
        [color=#32ccfe]▀▄▀▀▀▀▀▀         ▄    █[/color]
          [color=#32ccfe]▀▄▄          ▄▀▀ ▄▄▀[/color]
             [color=#32ccfe]▀▀▄▄     ▄▄▄▀▀[/color]
       [color=#000000]▄▄▀▀      ▀▀▄▄[/color]
      [color=#000000]█              █ ▄[/color]
     [color=#000000]█                █ ▀▄[/color]
     [color=#000000]█                █  ▀▄[/color]
      [color=#000000]█              █    █[/color]
    [color=#000000]▄▀ ▄▄          ▄▀    ▄▀[/color]
     [color=#000000]▀▀  ▀▀▄▄▄▄▄▄▀▀      ▀▄[/color]
            [color=#000000]▀▄▄      ▄▄▀▀▄▄▀[/color]
    [td][font=monospace][size=2pt]    [color=#000000]▄▀▄            ▄▀▄[/color]
       [color=#000000]█   █          █   █[/color]
      [color=#000000]█     █ ▄▄▄▄▄▄ █     █[/color]
     [color=#000000]▄▀      ▀      ▀      ▀▄[/color]
     [color=#000000]█                      █[/color]
    [color=#000000]█       ▄▄▄▄▄▄▄▄▄▄       █[/color]
    [color=#000000]█    ▄▀▀          ▀▀▄    █[/color]
    [color=#000000]█   ▄▀   ▄      ▄   ▀▄   █[/color]
     [color=#000000]█  █   ███    ███   █  █[/color]
      [color=#000000]█  █   ▀      ▀   █  █[/color]
       [color=#000000]▀▄ ▀▀▄▄▄▄▄▄▄▄▄▄▀▀ ▄▀[/color]
    [td][url=https://lisk.chat][font=Arial Black][size=28pt][color=#444][b]C[color=#333]H[color=#222]A[color=#111]T[/td]


    [table][tr][td][size=23pt][font=Arial Rounded MT Bold][url=https://lisk.io/][color=#655740][b]Lisk[/b][/color][/url][/font][/size][/td]
    [size=9pt][color=black][font=Lucida Sans Unicode, Arial] Develop [color=#0288d1][b]Decentralized Applications[/b][/color] & [color=#0288d1][b]Sidechains[/b][/color] in [color=#e27200][b]JavaScript[/b][/color] with [color=#0288d1][b]Lisk[/b][/color]!
    [b][url=https://lisk.io]Website[/url] | [url=https://blog.lisk.io]Blog[/url] | [url=https://bitcointalk.org/index.php?topic=1346646]BT... Thread[/url] | [url=https://lisk.chat]Chat

  • Team Member:

    Max Kordek


    Max is a futurist and thoroughbred entrepreneur who is interested in disruptive technologies. Having a rich experience in the blockchain industry and seeing the potential of blockchain-based applications, he co-founded Lisk. A blockchain application platform for JavaScript developers which caused a stir when it collected 14000 BTC in its crowd fund early 2016.

    Oliver Beddows


    Oliver is a full stack developer with over 15 years experience in developing web based e-commerce applications. He joined Crypti (Lisk's predecessor) in early 2015 as a tools developer, and went on to build tools such as the CryptiChain Blockchain Explorer and CryptiKit, a node deployment and management tool. He is a husband, father, amateur time-trialist, open-source advocate, and works tirelessly to build a better future for Lisk everyday.

    François-Xavier Thoorens


    François-Xavier is a full stack developer focusing on innovative solutions ranging from satellite imagery analysis to clinical trials on cancer. In the past he worked for the European Commission as a scientist, advised the Black Sea Commission executive director, collaborated with the Institut Gustave Roussy and co-founded 2 startups. He is a happy husband, father of 5, organist, and music composer.

    Isabella Dell


    Isabella is a Unix and Database specialist with over five years worth of experience in blockchain technology. In her role with Lisk she will secure the blockchain’s present and future by leveraging the unique combination of software it provides. She spends her spare time immersed in antique computers, aquatic life and electronics repair.

    Ricardo Ferro


    Ricardo is a full stack developer with over 15 years of experience in web development. He has worked with a multitude of web technologies, lately his main focus is on JavaScript and NodeJS. Working since 10 years in a traffic monitoring company as a developer and team leader, he has build up an astonishing portfolio of skills. He is a developer at heart and loves NodeJS, that is why he became extremely intrigued by Lisk.

    Joel Fernández


    Joel is a blockchain technology enthusiast, research scientist and aspiring programmer. He spent the last five years avidly researching the radical innovations of crypto-currencies and their role in reducing centralized inefficiencies. As the community manager he will serve as the link between the community and the developers while managing content creation, media marketing and customer relations.

    Social Media

  • Weekly Summary

    Welcome to the third issue of our weekly summary, normally published every Friday. As an exception this week’s summary includes the past two weeks, i.e. from the 17th September until the 2nd October, and is published on a Sunday.

    Please note, we can’t describe every little detail we work on. Below are only the more interesting topics and tasks listed.



    • Released second release candidate Lisk v0.4.0b to Testnet.
    • Released third release candidate Lisk v0.4.0c to Testnet.
    • Conducted community alpha testing on Lisk v0.4.0d release candidate.
    • Released fourth release candidate Lisk v0.4.0d to Testnet. A major step forward towards completing our first mainchain stablisation milestone.
    • Released Lisk v0.3.4 to Mainnet. Fixing a critical transaction signature malleability issue.





    • Reviewed numerous employee profiles from our recruitment agency.
    • Held a meeting with Luiz Chen, Chinese Ambassador, regarding Lisk China.
    • Held a meeting with WachsmanPR for the public relations strategy for October.
    • Held two meetings with a design agency regarding the rebranding.


    • Made preparations for the 33C3 conference in Hamburg.

    Thank you,

    The Lisk Team

  • Lisk v0.4.0 — Release Announcement

    The latest Lisk client v0.4.0 has been released, and is now available for download via our downloads server.

    As part of the current work-in-progress “Mainchain Stablisation” milestone, recently outlined in the Lisk Development Roadmap, we are making huge efforts to overhaul the existing code base and test-suite. Lisk v0.4.0 is a major push into completing the milestone, and includes many bug fixes, efficiency, and stability improvements. All standby delegates and node operators are encourage to update as soon as possible.

    To install or update to Lisk v0.4.0 please read our official documentation

    v0.4.0 Changelog

    Backend — Accounts

    • Closed #197. Improving error messages when account does not have enough funds. Yielding sender address and account balance.
    • Closed #266. Changed behavior of POST /api/accounts/open and POST /api/accounts/generatePublicKey. New accounts are no longer written to mem_accounts. Added one-time migration to delete dormant accounts which have never received or sent funds.
    • Closed #266. Verifying public key type, length and format in Account.prototype.set and Account.prototype.merge.
    • Closed #266. Added virgin column to mem_accounts. Indicating whether an unconfirmed transaction sent from an account has been applied.
    • Closed #266. Added protect_mem_account database trigger. Making address, u_username, username, virgin, publicKey, and secondPublicKey columns immutable once written.
    • Closed #266. Added senderPublicKey exceptions to Transaction.prototype.verify.
    • Added missing address validation to GET /accounts?address=.
    • Fixed error on GET /api/delegates?orderBy=unknown:asc.
    • Fixed error on GET /api/delegates?limit=0.

    Backend — Blocks

    • Closed #163. Adding default orderBy to /api/blocks (height:desc).
    • Merged #210. Block processing rewrite @fix.
    • Preventing data corruption of memory tables after reload or shutdown #213.
    • Closed #222. Fixing block reward calculation within first few blocks after milestone.
    • Closed #258. Detecting numericality of snapshot round. Allowing node app.js —snapshot=foobar to default to the highest round.
    • Closed #260. Removing infinite recursion in Loader.prototype.getNetwork.
    • Closed #276. Finishing snapshot within __private.applyBlock.
    • Closed #289. Prevent sync slowdown after receiving unconfirmed transactions.
    • Conditionally loading blocks from network; when there has been no block “receipts” over network transport, or when last receipt was over 120 seconds ago.
    • Added GET /api/loader/status/ping endpoint @34ro.
    • Added GET /api/blocks/getEpoch endpoint.
    • Added nethash and epoch properties to GET /api/blocks/getStatus.
    • Fixed orphan account check. Excluding mem_accounts with NULL blockId.
    • Fixed invalid type comparison on unapplied rounds.
    • Fixed reported block height when rebuilding blockchain.
    • Improved error logging with JSON dump of affected block.

    Backend — Transactions

    • Closed #265. Fixing “Account not found” error when sending transactions to virgin account using POST /api/transactions.
    • Fixed #279. Removing erroneous unconfirmed transactions.
    • Fixed #279. Removing redundant double spend collection.
    • Fixed undefined is not a function error. After error thrown while verifying transaction bytes.
    • Added verification of transaction assets for all transaction types.
    • Improved error logging with JSON dump of affected transaction.
    • Improved logging of apply / undo of transactions at debug level.
    • Performing sender balance checks using bignum arithmetic.

    Backend — Applications

    • Closed #269. Fixed crash on 404 error for POST /api/dapps/install.
    • Downgraded npm to latest LTS release 2.15.10.

    Backend — Peers

    • Improving peers db efficiency #104. Sequencing peers updates.
    • Improving peers db efficiency #104. Replacing insert / update with single upsert.
    • Improving peers db efficiency #104. Chaining database queries when adding dapp peer.
    • Closed #147. Replacing request with popsicle. Fixing memory leak on large request bodies, e.g. loading blocks from peer.
    • Merged #227. Improved peer discovery using histogram cut selection of “good” peers @fix.
    • Closed #231. Implementing API rate limiter. Individually configurable for both /api and /peer. Disabled by default.
    • Added EHEADERS, ERESPONSE, ENETHASH peer error codes, extending: https://github.com/blakeembrey/popsicle#error-handling.
    • Fixed timers in Loader.prototype.onPeerReady.
    • Only trigger nextLoadBlock if loaded and not already syncing.
    • Fixed halt to nextLoadUnconfirmedTransactions recursion when syncing.
    • Fixed halt to nextLoadSignatures recursion when syncing.
    • Checking nethash for all transport /peer requests.
    • Returning JSON response for POST /peer/blocks.
    • Returning success or error for GET /api/peers/get.
    • Added success property to GET /peer/transactions.
    • Ignoring already processed or confirmed transactions for POST /peer/transactions.
    • Added transactionId property to POST /peer/transactions.
    • Added success property to GET /peer/height.
    • Removing peers which return bad response code.
    • Removing peers with invalid request headers.
    • Removing peers with invalid nethash.
    • Improved logging of peer changes at debug level.
    • Increased default peer timeout to 5000 ms.
    • Fixed unwanted rejection of seed peers due to lack of os, version metadata.
    • Removed unnecessary peer loopback detection.
    • Validating peer headers using zschema only.

    Backend — Refactoring

    • Closed #147. Dramatically improved CPU and memory efficiency.
    • Moved schema validations into separate modules, to eliminate unnecessary continous object creation.
    • Added unique ids to schema validations, to better utilize z-schema schema caching.
    • Nullifying any large objects identified by memory profiling at the earliest opportunity.
    • Decoupled transaction types from modules into separately addressed modules.
    • Defining functions on constructor prototype where possible.
    • Using async for control flow, to remove deep nesting of code.
    • Fully linted code base using jshint to a strict standard.
    • Created database indexes on memory tables.

    Backend — Tests

    • Complete rewrite and abstraction of API tests, for cleaner tests.
    • Massively expanded API test coverage, resulting in many fixes.
    • Added initial unit test coverage, e.g. for block rewards.

    Backend — Configuration

    • Removed unimplemented serveHttpAPI/Wallet options from config.json.
    • Added maxUpdatePeers option to config.json.
    • Added trustProxy setting to config.json.

    Backend — Dependencies

    • Updated all dependencies to latest compatible versions.
    • Replaced underscore, util-extend with lodash.


    • Added Polish language support.
    • Fixating and updating dependency versions.
    • Fixing calls to null u_multisignatures/multisignatures.
    • Fixing call to undefinedresp.data.account.


    • Closed #44. Added timestamp to postgresql logs.
    • Added empty blockchain.db.gz to allow for starting the blockchain from 0.
    • Updating node/lisk-node to 0.12.16.


    • Implemented url flag for lisk.sh to allow remote snapshots to be used with rebuild.
    • Updated rebuild logic to allow for local backups to be reused and to specify file name.
    • Improved lisk startup to display current block height after start or status is issued.
    • Implemented new logic for interactive snapshotting.
    • Added progress bar when downloading snapshots.


    • Implemented lisk_snapshot.sh for automated database backups.
    • Added snapshot.json for configuring lisk_snapshot.sh backups.


    • Removed duplicated block height check already present in lisk.sh.
    • Changed coldstart to use empty blockchain.db.gz.


    • Updated upgrade instructions to use automated upgrade.
    • Updated testnet installation instructions.

    Please join our forum or chat if you have any further questions, or are interested in supporting the network by running a node.

    For reference, you can always track our development progress via GitHub: https://github.com/LiskHQ/lisk

    Kind regards,

    Oliver Beddows

  • HowTo: Install an Auto-Snapshot Server (Updated 2016-10-10)

    # Warning(s)

    • Lisk v0.4.0+ is mandatory. Latest lisk.sh and lisk_snapshot.sh included in this version are required.
    • This guide is assuming that you already are able to build a basic functional Lisk server.
    • The snapshot server need a lisk client instance running and in sync. on the server.
    • The snapshots are made from a second instance running in parallel.
    • Both node instances will share the postgres service.
    • Using the Lisk client as a forging server for delegate on same server not recommended.
    • Do NOT use the Lisk client './public/' directory to host your backups.
    • HTTP (port 80) redirection to HTTPS (port 443) isn't needed. I'll give the recipe with (optional) tag in the guide.

    # Prepare Firewall

    Make sure port 80 is open and without redirection in your firewall.

    (Optional) Make sure port 443 is open and without redirection in your firewall.

    # Users

    I'm using the following users, adjust accordingly to your setup.

    The "lisk" user is the user running lisk client.
    It will need write permission in the target directory where the snapshots will be save.

    The "nginx" user is the user that will run nginx.
    It will need read permission in the target directory where the snapshots will be save.

    # Directories

    I'm using the following directories, adjust accordingly to your setup.
    Do NOT use a sub-directory of Lisk client for 'shared backup directory'.
    This will allow to keep it untouched and keep service online when updating Lisk client.

    Lisk wallet directory ==> /opt/lisk/client/
    Shared backup directory ==> /opt/lisk/backup/
    (Optional) SSL directory ==> /etc/letsencrypt/live/snapshot.lisknode.io/

    If you need help to generate a free SSL certificate, refer to this guide. (You can skip port redirection parts and lisk configuration parts.) ==> HowTo: Free SSL Certificate

    (Optional) Write a Tag file in the shared directory

    Code: Select all

    touch '/opt/lisk/backup/### Vote Gr33nDrag0n ###'

    Nginx Installation and Configuration

    Install nginx

    Code: Select all

    # Ubuntu
    apt-get install nginx
    # CentOS
    yum install nginx

    Backup original nginx configuration file.

    Code: Select all

    cd /etc/nginx
    cp nginx.conf nginx.conf.original

    Open the configuration file.

    Code: Select all

    vi nginx.conf

    Remove all server configuration block.

    Select one of the 2 following examples.

    HTTP Only

    Code: Select all

    server {
    listen 80;
    server_name snapshot.lisknode.io;
    root /opt/lisk/backup;

    location / {
    autoindex on;

    (Optional) HTTP to HTTPS redirection

    Code: Select all

    server {
    listen 80;
    server_name snapshot.lisknode.io;
    return 301 https://snapshot.lisknode.io$request_uri;

    server {
    listen 443;
    server_name snapshot.lisknode.io;
    root /opt/lisk/backup;

    ssl on;
    ssl_certificate /etc/letsencrypt/live/snapshot.lisknode.io/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/snapshot.lisknode.io/privkey.pem;
    ssl_protocols TLSv1.1 TLSv1.2;
    ssl_prefer_server_ciphers on;
    ssl_session_cache shared:SSL:10m;
    ssl_session_timeout 10m;

    location / {
    autoindex on;

    Replace 'snapshot.lisknode.io' by your domain.

    Replace '/opt/lisk/backup' by your backup directory path.

    Save the modified configuration.

    Test Configuration

    Code: Select all

    nginx -t

    Start nginx server

    Code: Select all

    systemctl start nginx

    Test nginx web server is up and running. Using your browser, go to your website URL.

    Enable nginx server at system’s booting time.

    Code: Select all

    systemctl enable nginx

    Stop nginx server (for reference only)

    Code: Select all

    systemctl stop nginx

    Lisk Client - Create snapshot.json

    Install jq using 'apt-get install jq' or 'yum install jq'

    Adjust the path in 'mainconfig' & 'snapshotconfig' and run:

    Code: Select all


    cp $mainconfig $snapshotconfig
    jq '.port=9000' $snapshotconfig > tmp.$$.json && mv -f tmp.$$.json $snapshotconfig
    jq '.version="snapshot"' $snapshotconfig > tmp.$$.json && mv -f tmp.$$.json $snapshotconfig
    jq '.logFileName="logs/snapshot.log"' $snapshotconfig > tmp.$$.json && mv -f tmp.$$.json $snapshotconfig
    jq '.loading.loadPerIteration=101' $snapshotconfig > tmp.$$.json && mv -f tmp.$$.json $snapshotconfig
    jq '.db.database="lisk_snapshot"' $snapshotconfig > tmp.$$.json && mv -f tmp.$$.json $snapshotconfig
    jq '.peers.list=[]' $snapshotconfig > tmp.$$.json && mv -f tmp.$$.json $snapshotconfig
    jq '.ssl.enabled=false' $snapshotconfig > tmp.$$.json && mv -f tmp.$$.json $snapshotconfig

    Test manual snapshot

    I recommend running 1st execution manually to confirm everything work as expected.

    For reference, this is lisk_snapshot.sh usage manual.

    Code: Select all

    Usage: lisk_snapshot.sh [-t <snapshot.json>] [-s <config.json>] [-b <backup directory>] [-d <days to keep>] [-r <round>] [-g]
    -t <snapshot.json> -- config.json to use for validation
    -s <config.json> -- config.json to create target database
    -b <backup directory> -- Backup direcory
    -d <days to keep> -- Days to keep backups
    -r <round> -- Round height to snapshot at
    -g -- Make a copy of backup file named blockchain.db.gz

    For 1st manual execution, I like to work with two different SSH connections.

    # Tab 1 - Adjust the paths and run:

    Code: Select all

    bash /opt/lisk/client/lisk_snapshot.sh -t /opt/lisk/client/snapshot.json -s /opt/lisk/client/config.json -b /opt/lisk/backup -d 3 -r highest -g

    # Tab 2 - Adjust the path and run:

    Code: Select all

    tail -f /opt/lisk/client/logs/snapshot.log

    Test Rebuild for manual snapshot

    Using your browser, go to your website URL.
    Confirm that you see and are able to download your manual snapshot.
    Use the following HowTo with your server URL to test a rebuild from your server.
    HowTo: Coldstart or Rebuild from an Auto-Snapshot Server

    Cronjob creation (Enabling Auto-Snapshot)

    Edit the crontab. The -u is parameter is the user that is running the Lisk client.

    Code: Select all

    sudo crontab -u lisk -e

    Edit and Add the following crontab entry.

    */6 represent 00:00, 06:00, 12:00, 18:00.
    I recommend using a number that can divide 24 equally. I.e. 2, 3, 4, 6, 8, 12.

    The timing must respect the time it took for your manual snapshot to complete.
    I recommend a good buffer because blockchain will always increase in size.

    For example, I personally use on my server */6 on TestNet and */8 on MainNet.
    It take about 4 hours for TestNet and 5.5 hours in MainNet.

    Code: Select all

    0 */6 * * * /usr/bin/bash /opt/lisk/client/lisk_snapshot.sh -t /opt/lisk/client/snapshot.json -s /opt/lisk/client/config.json -b /opt/lisk/backup -d 3 -r highest -g

    Lisk client update/upgrade notes

    Each Lisk client update, some special steps will be needed for the auto-snapshots server.

    • The nginx shared directory can stay online for the whole process.
    • Before update, the cronjob must be disabled.
    • Before update, all instances of Lisk "node" process(es) must be stopped or killed.
    • After update, the snapshot.json file must be re-created.
    • After update, test manual snapshot and take note of the time it take.
    • After update, the cronjob must be re-enabled and timing adjusted if needed based on manual test.


    If you got a question, comment don't be shy to reply to this post.

    If you implemented a auto-snapshot server. Include your URL with a MainNet or TestNet tag.

  • Lisk Nano v0.1.1 — Release Announcement

    The latest Lisk Nano client v0.1.1 has been released, and is now available for download via our download servers.

    Lisk Nano stems from the belief that our users should be able to access their Lisk accounts anywhere, anytime, and from any device in the world. This kind of untethered accessibility is an important factor for the Lisk team but until now there were some obstacles in that regard. Installing the Lisk client on Windows and macOS computers is still quite the complicated task and we still need conduct feasibility research in order to provide native one-click clients.

    Therefore we introduced Lisk Nano, a light-weight, simple, and fully responsive client which allows users to access the very basic Lisk features. It was developed by Ricardo Ferro, our tools developer.

    Starting with this release we make Lisk Nano available online, primary for our mobile users. To try it out, please proceed to https://m.lisk.io/. In the case of a desktop computer we recommend to download the client locally for maximum security.

    v0.1.1 Changelog

    • Add support for second passphrases. Fix #1.
    • Change new account entropy.
    • Auto login after new account is created.
    • Changing validation of BIP39, now allows passphrases with 12, 15, 18, 21 or 24 words. Fix #2.
    • Fix webpack warning.

    With Lisk Nano, there is no need to synchronize with the Lisk blockchain and network, you are simply accessing one of our trusted, official Lisk nodes. As we progress, we would like to add nodes maintained by reputable and trusted community members, or possibly switch to a completely decentralized network-wide node selection.

    Lisk Nano 0.1.1 is available for all major computer platforms (Windows, macOS, Linux) as one-click clients. Just head to our download page on Lisk.io and select the client for your operating system. You may also download the compressed source files from GitHub and open the HTML file with your browser of choice.

    Please keep in mind that Lisk Nano is still in an early version, and is considered beta software. Critical and non-critical bugs found by the community will be fixed accordingly, alongside introducing new features. Starting with the next update all Lisk Nano packages will be officially signed. If you experience any problems installing, please raise a support ticket.

    Kind regards,

    Oliver Beddows

  • Lisk Weekly Summary

    Welcome to the fifth issue of our weekly summary published every Friday. This week’s summary includes the past 7 days, i.e. from the 8th October until the 14th October. Feel free to read our last Weekly Summary.

    Please note, we can’t describe every little detail we work on. Below are only the more interesting topics and tasks listed.



    • Released Lisk v0.4.0 to Mainnet.
    • Continued development work towards the next release cycle.
    • Released Lisk Nano v0.1.1 for Windows, macOS, and Linux.


    • Attended an online marketing session at WeWork.
    • Answered an interview by BTC-echo.de.



    • Made preparations for the new legal direction we chose.
    • Held several meetings with our lawyers.
    • Reviewed new CVs of potential candidates for front and back end developer positions from Nicoll Curtin.
    • Made preparations for the interviews we conducted this week.
    • Interviewed front end and back end developers; two on Skype, one in our office.
    • Held a meeting with WachsmanPR to get them up-to-date.
    • Held the weekly meeting with our advisers.


    • Held meetings with several design agencies.
    • Received branding documents from several design agencies.
    • Made preparations for the Golden Drum conference in Ljubljana.
    • Cancelled the planned WebSummit conference trip due to time constraints.
    • Attended the BXB / Steemit Meetup in Berlin.

    Thank you,

    The Lisk Team

  • Community Meeting  + Questions for meeting— October 28th, 2016

    This upcoming Friday, October 28th, Lisk will be conducting it’s bi-weekly community meeting. For each meeting, a document is created for gathering questions that may be difficult or lengthy to answer during the meeting. The deadline for collecting questions is Wednesday (October 26th). If you believe your question is not difficult, nor lengthy, you may attend the meeting and ask the team to get a direct answer.

    Note: The meetings have changed from the usual Saturday gatherings to Friday. We will continue the community meetings on a two-week basis.

    Questions for Community Meeting
    Collected by the Lisk Community
    Editors: joel, MrV, punkrock, tharude, cc001, densmirnov
    Please reach out to one of the editors for adding questions to this document
    Answers will be published on blog.lisk.io before every Community Meeting


    Delegated Proof of Stake / Algorithm

    Forging rewards / Genesis Delegate-Replacement


    Release-Management / Development-Process


    ICO / Funding



    Node running





    Everyone is encouraged to participate, so if you have any detailed questions for us, please submit them to joel, MrV, densmirnov, tharude, cc001, and/or punkrock within Lisk chat, and they will be added to the document. Alternatively, you can also send the questions through e-mail ([email protected]) During the meeting, the team will address as many questions as possible.The meeting will take place in our Lisk chat, and will be held on October 28th, 2016 at 6:00 PM (GMT +2).

  • Weekly Summary — 006

    Welcome to our weekly summary published every Friday. This week’s summary includes the past 7 days, i.e. from the 15th October until the 21st October. Feel free to read our last Weekly Summary.

    Please note, we can’t describe every little detail we work on. Below are only the more interesting topics and tasks listed.



    • Published Lisk v0.5.0a to Alpha Testers.


    • Fixed a bug on the front page which prevented the price ticker from getting up-to-date values.


    • Had an interview regarding a news article about ICOs.



    • Held several meetings with our lawyers.
    • Reviewed new CVs of potential candidates for front and back end developer positions from Nicoll Curtin.
    • Followed-up on the interviews conducted last week.
    • Interviewed a back end developer in our office.
    • Held a meeting with WachsmanPR to get them up-to-date.
    • Added job descriptions to Angel.co. Back end | Front end
    • Added job descriptions to BerlinStartupJobs.com. Back end | Front end


    • Prepared a summarised explanation of Lisk for our lawyers.

    Thank you,

    The Lisk Team

Log in to reply