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


    Sidechains



    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.


    Customizable


    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.


    Usability


    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


    Usability



    Security


    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.


    Security



    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');

    sandbox.sendMessage({

    call: "dapps#receive",

    args: {body: "Hello Lisk!"}

    });

    sandbox.onMessage(function (msg, cb) {

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

    cb();

    });

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

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

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

    cb();

    }, true);

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

    sandbox.run();

    Source Code


    Specifications

    • 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: Ⱡ


    Download

    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.


    Windows


    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


    Linux


    • 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

    Download

    Windows


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

    Download


    Mac OS X


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

    Download


    Linux


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

    Download


    Old versions


    Please don't use any old version in production.


    Block Explorer:


    https://explorer.lisk.io/


    Github:


    https://github.com/LiskHQ



    Exchange:



    https://poloniex.com/exchange/btc_lsk


    https://yobit.net/en/trade/LSK/BTC

    https://www.livecoin.net/

    https://bittrex.com/Market/Index?MarketName=BTC-LSK

    https://www.bitmex.com/

    https://bloombit.net/trade

    http://chameleonbit.trade/

    https://bitshares.openledger.info/

    https://www.cryptomic.com/trade?c=LSK&p=BTC


    Pool:

    http://www.liskpool.com/

    https://bitmakler.net/Lisk___mining



    Code:

    [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=#1f4b67]▄██▄[/color]
    
            [color=#1f4b67]▄██████▄[/color]
    
          [color=#1f4b67]▄██████████▄[/color]
    
        [color=#1f4b67]▄██████████████▄[/color]
    
        [color=#1f4b67]▀██████████████▀[/color]
    
          [color=#1f4b67]████████████[/color]
    
           [color=#1f4b67]██████████[/color]
    
           [color=#1f4b67]▀████████▀[/color]
    
          [color=#000000]███[color=#1f4b67]██████[/color]███[/color]
    
         [color=#000000]██████████████[/color]
    
          [color=#000000]████████████[/color]
    
            [color=#000000]▀██████▀[/color]
    
    [/td]
    
    [td][center][size=13pt][url=https://bitcointalk.org/index.php?topic=1346646.0][b][color=#2024e6]Bitcointalk[br]thread[/b][/td]
    
    [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=red]▄█▄    ▄█▄[/color]   █  █[/color]
    
       [color=#000000]▀█    [color=red]▀█▀    ▀█▀[/color]    █▀[/color]
    
        [color=#000000]█                  █[/color]
    
         [color=#000000]█   ▀▄      ▄▀   █[/color]
    
          [color=#000000]▀▄   ▀▀▀▀▀▀   ▄▀[/color]
    
            [color=#000000]▀▀▄▄▄▄▄▄▄▄▀▀[/color][/td]
    
    [td][center][size=13pt][url=https://www.reddit.com/r/lisk][color=#BDD62F][b]Reddit[/b][/url]
    
    [center][size=13pt][url=https://twitter.com/LiskHQ][color=#BDD62F][b]Twitter[/b][/url][/td]
    
    [td][font=monospace][size=2pt]
    
                            [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=#32ccfe]▀▀▄▄     ▄▄▄▀▀[/color]
    
                 [color=#32ccfe]▀▀▀▀▀[/color]
    
    [/td]
    
    [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]
    
    [/td]
    
    [td][center][size=13pt][url=https://forum.lisk.io/][color=#BDD62F][b]Forum[/b][/url]
    
    [center][size=13pt][url=https://github.com/LiskHQ][color=#BDD62F][b]Github[/b][/url][/td]
    
    [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]
    
         [color=#000000]▀▀▄▄▄▄▄▄▄▄▄▄▄▄▀▀[/color]
    
    [/td]
    
    [td][url=https://lisk.chat][font=Arial Black][size=28pt][color=#444][b]C[color=#333]H[color=#222]A[color=#111]T[/td]
    
    [/tr][/table]


    Code:



    [table][tr][td][size=23pt][font=Arial Rounded MT Bold][url=https://lisk.io/][color=#655740][b]Lisk[/b][/color][/url][/font][/size][/td]
    [td][size=4pt].[/size]
    [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

    CHIEF EXECUTIVE OFFICER · FOUNDER

    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


    CHIEF TECHNOLOGY OFFICER · FOUNDER

    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

    CORE DEVELOPER

    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

    SYSTEM ARCHITECT

    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

    TOOLS DEVELOPER

    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

    COMMUNITY MANAGER

    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.



    Development


    LiskHQ/lisk

    • 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.


    LiskHQ/lisk-website


    Marketing


    Community


    Management

    • 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.


    Misc

    • 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.

    Frontend

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

    Build

    • 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.

    lisk.sh

    • 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.

    lisk_snapshot.sh

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

    installLisk.sh

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

    Documentation

    • 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_ciphers 'EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH';
    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

    mainconfig='/opt/lisk/client/config.json'
    snapshotconfig='/opt/lisk/client/snapshot.json'

    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.


    Conclusion

    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.





    Development


    LiskHQ/lisk

    • 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.

    Marketing

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

    Community


    Management

    • 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.

    Misc

    • 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

    Communication

    Delegated Proof of Stake / Algorithm

    Forging rewards / Genesis Delegate-Replacement

    Testnet

    Release-Management / Development-Process

    Roadmap

    ICO / Funding

    Team/Developers/Advisors

    Sidechains

    Node running

    Legal

    Clients

    Bounties

    Other


    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.



    Development

    LiskHQ/lisk

    • Published Lisk v0.5.0a to Alpha Testers.

    LiskHQ/lisk-website

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

    Marketing

    • Had an interview regarding a news article about ICOs.

    Community


    Management

    • 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

    Misc

    • Prepared a summarised explanation of Lisk for our lawyers.

    Thank you,

    The Lisk Team





  • Lisk v0.4.1 — Release Announcement


    The latest Lisk client v0.4.1 has been released, and is now available for download via our downloads server. This version patches a number of issues affecting usability, security and stability of the client. All node operators are highly encouraged to update at the earliest opportunity.

    As part of the current work-in-progress “Mainchain Stabilisation” milestone, recently outlined in the Lisk Development Roadmap, we are making huge efforts to overhaul the existing code base and test-suite.

    The first release candidates for Lisk v0.5.0 are soon in operation on testnet. Please go to the #testnet channel on Lisk.Chat if you are interesting in helping us test out new releases.

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


    v0.4.1 Changelog

    Backend

    • Do not apply or undo transaction when syncing (before processing).
    • Fixed #293. Expected type string but found type null @Isabello.
    • Closed #285. Moved TOP=true param to config.json @Isabello.
    • Fixed state filter on GET /api/peers endpoint.
    • Using extend consistently for all object extension.
    • Handling NaN port in Peers.prototype.inspect.
    • Revised and improved schema validations.

    Frontend

    • Merged #79. Fixing cramped high page numbers on blockchain page @slaweet.

    Build

    • Merged #49. Updating md5 command for macOS @Doweig.
    • Improving block height check in lisk.sh to show “Unavailable” when query is empty @Isabello.

    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









  • First milestone in sight: Forging Rewards Activation

    We are happy to announce that the imminent completion of our first milestone named Mainchain stabilisation is in sight. The most important achievement for our user base this year comes with the subsequent activation of community forging. With that, we will also enable forging rewards so that delegates are able to finance community projects, and foster a growing ecosystem.

    This marks a historic turning point for the Lisk project, going forward we can now put the majority of our efforts into our sidechain technology and the Lisk App SDK.



    Lisk is approaching forging rewards activation block 1,451,520 which is expected to be reached early December. Following the fixed rules of our code we will start with 5 LSK per block, being reduced by 1 LSK approximately every year.

    Lisk utilises the Delegated Proof of Stake consensus algorithm with highly efficient delegate nodes. During a dynamic, decentralised and democratic voting process 101 delegates are elected which are generating new blocks whereby they earn forging rewards.

    In preparation for the roll out of the rewards, we released Lisk v0.5.0 to the testnet with improved stabilisation, a focus on increasing block propagation efficiency and reliability, rewriting of the peer to peer transport layer, expanded test coverage, strengthened schema validations for better data integrity, and various mitigations against multiple edge-case fork occurrences.

    We are now continuing our sprint towards Lisk v0.6.0 to be completed at the end of this month. The forthcoming version brings a complete rewrite of all database logic, allowing for faster block processing and atomicity. It will also add further intelligence to the unconfirmed transaction memory pool, which is designed to open the way for larger block sizes.








  • Lisk A New Way in Communications

    For the Lisk team it has always been important to stay transparent and open to the community. We’ve been frequently updating the community through our blog with bi-weekly community meetings, weekly summaries and detailed change-logs for version updates. Moving forward, we are transitioning from our current setup and streamlining it to funnel important information into the blog, repetitive announcements into the forums, day to day community discussions into the Lisk Chat and developer collaborations through Gitter.


    The blog is for important topics only

    Currently, the Lisk blog is being updated regularly with repetitive posts such as weekly summaries, community meetings, version releases, and others. Blog posts tend to get lost which means individuals don’t have an easy overview and are unable to participate in topic-based discussions. Therefore, we are redirecting repetitive blog posts towards their distinctive child board on the official Lisk forums. The blog will be used for important announcements, long-term updates, change of directions, and other personal blog posts from the Lisk team.

    Putting more efforts in the forums

    As stated above we created new child boards in the forum for all repetitive announcements involving Lisk, namely:

    In the forums, anyone will be able to draft and publish their delegate proposals and also participate in discussions pertaining to the Lisk platform. New members will find it easier to navigate through the backlog of summaries, meetings and updates. This is all about bringing individual community members together.

    Day-to-day discussions on Lisk.Chat

    Lisk Chat is one of the largest cryptocurrency related chat platforms in the world. The purpose of the Lisk Chat is a completely open and transparent platform for anyone that wishes to discuss Lisk related topics. If you ever wonder what Lisk is doing, or you just want to have a quick chat with Lisk enthusiasts, just hop into the Lisk chat, it is likely one of our team members will have a conversation with you. The community meetings will keep happening there once a month, the last two for the year on November, 27th and December, 18th.

    Developers collaboration on Gitter

    Moving forward, we want developers to have their own place where they can discuss development of the Lisk platform. In order to satisfy this need we have opened a LiskHQ Gitter account which developers and volunteers can join and openly collaborate with the Lisk developers and between each other. Gitter is directly integrated with LiskHQ GitHub which will make future collaborations and discovery as simple as possible.











  • Community Delegate Contest — Prepare yourself!

    On block 1,451,520 the forging rewards will be activated with the subsequent activation of community forging. The imminent completion of our first milestone Mainchain stabilisation” is a big step forward for Lisk and we are celebrating it with a delegate campaign and a proposal contest.




    For those new to Lisk, delegates represent the backbone of the decentralised Lisk network. Anyone can become a delegate, but only 101 delegates get the opportunity to generate blocks and earn forging rewards. These 101 delegates are elected by every LSK holder by voting, their voting power equals their LSK balance. The more LSK they own, the more voting power they have. The cumulative voting power of all accounts in the network decides who is in the top 101 and who isn’t. Here’s a quick breakdown of a delegate:

    • Passionate about Lisk and the community
    • Support the Lisk ecosystem and Lisk community
    • Good understanding of the underlying blockchain technology
    • Help the community where possible, mainly new incoming members
    • Lower the entry barrier towards new community members
    • Identify opportunities for Lisk and the community
    • Educate their local community and spread awareness

    If you want to know how to deploy a Lisk node, click here!

    Delegate Campaign

    The goal of this campaign is to get as many delegates as possible and for existing delegates to update their proposals so that LSK holders have the information they need to make an informed decision. If you want to become a delegate you need to setup a Lisk node, register a delegate account on the network and collect enough votes to get elected into the top 101 active delegation.

    In order to register a delegate account a fee of 25 LSK is paid to the Lisk network. Additionally it’s recommended that you write a proposal on the Lisk forum to increase your chances to be elected as a forging delegate.

    Until block 1,451,520 is reached we are giving every registered delegate the 25 LSK fee back. The only requirement is to have an up-to-date proposal on the Lisk forums, for which you may receive a bonus of 25 LSK.

    Proposal Contest

    Accompanying the delegate registration campaign, and following block 1,451,520, we are having a contest for proposals submitted and the 13 most interesting proposals will receive a bonus reward and featured in this blog post!

    • Three proposals will receive 5,000 LSK
    • Ten proposals will receive 1,000 LSK

    Proposals will be selected based on the following criteria:

    • Contributions
    • Viability
    • Creativity
    • Transparency
    • Thoroughness
    • Clarity

    Contest Rules

    • The contest begins on November 17th, 2016 and ends on December 5th, 2016.
    • Purchase of 25 LSK necessary; reimbursed once a delegate proposal has been submitted.
    • Delegate proposals must be written on the Proposal child board and follow the given template (viewable upon creating a new topic).
    • If you have already written a proposal and have adopted the Proposal template, contact joel or redsn0w through a forum personal message and they will move your proposal to the adequate board.
    • You will not be eligible for the campaign or the contest if the proposal is not in the correct child board. Bonus of 25 LSK limited to first 200 delegate proposals and one per person during the contest period.

    Participate now!

    Simply head to the Lisk forum and post your proposal!


    Delegate Campaign

    The goal of this campaign is to get as many delegates as possible and

    for existing delegates to update their proposals so that LSK holders

    have the information they need to make an informed decision. If you want

    to become a delegate you need to setup a Lisk node, register a delegate

    account on the network and collect enough votes to get elected into the

    top 101 active delegation.



    In order to register a delegate

    account a fee of 25 LSK is paid to the Lisk network. Additionally it’s

    recommended that you write a proposal on the Lisk forum to increase your

    chances to be elected as a forging delegate.



    Until block 1,451,520 is reached

    we are giving every registered delegate the 25 LSK fee back. The only

    requirement is to have an up-to-date proposal on the Lisk forums, for

    which you may receive a bonus of 25 LSK.

    Proposal Contest:

    • Accompanying the delegate registration campaign, and following block 1,451,520, we are having a contest for proposals submitted and the 13 most interesting proposals will receive a bonus reward and featured on our blog!

      The best three proposals will get 5,000 LSK, while the next 10 proposals will get 1,000 LSK each.
    • Contest Rules The contest begins on November 17th, 2016 and ends on December 5th, 2016.

      Purchase of 25 LSK necessary; reimbursed once a delegate proposal has been submitted.

      Delegate proposals must be written on the Proposal child board and follow the given template (viewable upon creating a new topic).

      If you have already written a proposal and have adopted the Proposal template, contact joel or redsn0w through a forum personal message and they will move your proposal to the adequate board.

      You will not be eligible for the campaign or the contest if the proposal is not in the correct child board. Bonus of 25 LSK limited to first 200 delegate proposals and one per person during the contest period.
    • Participate now!







  • Community Meeting - November 27th, 2016




    On November 27th of 2016, we will be conducting our monthly Community Meeting on Lisk Chat.

    Join us while the Lisk team answers as many questions as possible from

    the community. Make sure to keep track of this forum post as the meeting

    transcript will be included once the meeting is over.



    Following are some topics we would like to discuss with the community:



    • Delegate Campaign and Proposal Contest
    • Mainchain Stabilization Developer Update
    • Network stability, scalability
    • Next Steps in Development

    Everyone is encouraged to participate, so if you have any detailed questions for us, please submit them to Joel (e-mail: [email protected], lisk.chat: joel). During the meeting, we will address as many questions as we possibly can.



    The meeting will take place in our Lisk chat, and will be held on November 27th, 2016 at 6:00 PM (CET).



























  • Distribution of Testnet Bounties

    After a long wait, we are finally announcing a one-time bounty for loyal Testnet supporters. Since May of 2016 we have been tracking the activity of the Test Network and have chosen to reward members of the community who have helped by stabilizing it. In order to be eligible for the bounty, there’s only one criteria that must be met:

    • Testnet Delegate must have forged at least one block

    After reviewing delegates, we have compiled a list of eligible delegates including their Lisk addresses and amount of LSK rewarded. In total, 50,000 LSK were distributed to 129 eligible delegates based on their total forged blocks. The rewards were sent to the same Lisk addresses being used for the Testnet delegates as to ensure proper delivery.

    Running a node on the Test Network was never mandatory, and we thank anyone who has participated. Going forward we believe the community will show support by keeping a Testnet node running.







  • Announcing the Community Fund

    Today, we are introducing the Community Fund, which will act as a decentralised funding vehicle for new blockchain applications, third party tools and core contributions from our community.

    The Community Fund

    The goal of the Community Fund is to collect LSK to guarantee decentralised, long-term development of the Lisk ecosystem. Everyone can voluntarily donate LSK to the Community Fund, however we believe the majority of the donations will come from active delegates. As described in our development roadmap we plan to develop a decentralised voting and proposal mechanism during Eternity. This tool will be utilised for all Community Fund spendings in a decentralised, community-led way.During Eternity, the Community Fund will be controlled by 16 known curators (a mix between team members, community members and public individuals) in a multi-signature account. The curators will be elected through the same decentralised voting mechanism used for decision making.More information will be made public once we are closer to the Eternity phase.


    Community Fund address: 15841793714384967784L

    Legal LiabilityThe Lisk Stiftung in Gründung (Lisk Foundation in establishment), temporary escrow agent for the Community Fund, obligates itself to a binding agreement with the Lisk community to not transfer the collected LSK to the curator’s multi-signature account before the end of 2018.Once the Stiftung (Foundation) is established we will provide a legal document.The Lisk founders make the first stepAs a first step we, the Lisk founders Max Kordek and Oliver Beddows, both donated 50,000 LSK to the fund. We hope that everyone makes a contribution, as small as it may be. Every single LSK can make a difference in the future.Community Fund ContributorsIn Resilience we will rebrand the Lisk ecosystem; during that process we will launch a new website with a dedicated page for the Community Fund in which all contributors will be listed.



  • WEEKLY SUMMARY - 011





    Development

    LiskHQ/lisk

    • Released Lisk 0.5.0d to Testnet.
    • Conducted extensive stress tests with Lisk v0.5.0d on Testnet.
    • Released Lisk 0.5.0e to Testnet.
    • Conducted extensive stress tests with Lisk v0.5.0e on Testnet.
    • Continued work on v0.5.0f.
    • Conducted extensive stress tests with Lisk v0.5.0f on Devnet.


    LiskHQ/lisk-explorer

    • Fixed a bug which affected the sorting on the Delegate Monitor.
    • Fixed a bug which affected the counter of network participants.
    • Added a network hash indicator to the header.
    • Started drafting up a new "Delegate Candidates" page.


    Marketing

    • Published a press release regarding the delegate contest.
    • Appeared in a German interview on BTC-echo.de.
    • Had an interview with a mainstream news outlet.


    Community


    Management

    • Held several meetings with lawyers, accountants, WachsmanPR and our advisers.
    • Reviewed new CVs of potential candidates for front and back end developer positions.
    • Followed-up on two interviews conducted in the past weeks.



    18th November - 25th November




  • Lisk v0.5.0f — Release Candidate (Testnet)



  • WITCH FROM GENESIS DELEGATES TO COMMUNITY DELEGATE


    This forum posts explains how we will make the switch from genesis delegates to community delegates securing the Lisk network.

    1. Releasing Lisk v0.5.0 internally (DONE)

    Oliver will prepare the Lisk v0.5.0 binaries and Isabella will install them on the current 101 genesis delegates, seed nodes, login, and explorer nodes.

    2. Releasing Lisk v0.5.0 to the public (DONE)


    Once all genesis delegates are updated to the latest version and the network behaves normally, we will release Lisk v0.5.0 to the public so that node operators can update to the latest version.

    3. Switching votes step-by-step


    We will stay in contact with all community delegate candidates and confirm that their node is configured and synced. After we confirm the nodes are in good working order, we will remove a vote from a genesis delegate and vote for the respective community delegate. This will be done in batches of 3-5.

    4. Repeat of step 3


    Step 3 will be repeated until we have 101 community delegates in the top. After the community has control of the network, we will step back and let the community vote for each other to determine who shall become an active delegate.

    Important: If your node is configured and synced please post your delegate name, a link to your delegate proposal and a link to your delegate on the blockchain explorer in this thread! We will vote for you as soon as possible.



    max
    User avatar




    CEO


  • LISK V0.5.0 - RELEASE ANNOUNCEMENT





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

    All node operators have to update at the earliest opportunity.

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

    v0.5.0 Changelog
    Backend
    Closed #104. Implementing peer sweeper. Collecting peer changes and sweeping in batches.Closed #294. Loading unconfirmed transactions from "good" peer.Closed #284. Emitting delegates/fork event after forking.Closed #255. Matching genesis block with database.Closed #141. Attempting to load delegates on each cycle.Closed #297. Improved peers/chain selection reliability thanks to new broadhash implementation.Closed #298. Array items are not unique in Loader.prototype.onPeersReady.Closed #259. Mitigating against fork cause 2.
    - Restoring sane API behaviour for POST /peer/transactions.
    ·· Returning error on already processed transaction.
    ·· Returning error on already confirmed transaction.Fixed #253. Adding missing check on transaction.Closed #306. Implemented new transaction pool and broadcast queuing
    - Adding new API endpoints:
    ·· GET /api/transactions/multisignatures/get
    ·· GET /api/transactions/multisignatures
    ·· GET /api/transactions/queued/get
    ·· GET /api/transactions/queuedRewrote and refactored multisignature module.Increased default database connection pool size to 95.Merged #314. Prevent "TypeError: Cannot read property 'network' of undefined @TheGoldenEye.Closed #51. Fixing invalid getGenesis parameter.Closed #244. Adding minimal client version parameter.Closed #91. Validating config.json according to schema.Do not remove peer on ETIMEOUT, only ban for 10 minutes.Returning 500 status code upon incorrect network / version.Correcting ban on peers returning invalid common block request to 10 minutes.Fixed incorrect math operator in __private.checkDelegates.Disabling forced forging for known nethashes.Closed #316. Logging warning when delegate slot skipped.Increased gzip compression level on express middleware.Improved broadcast efficiency. Squashing queued broadcasts from many to one per route. Accepting collection or object on POST /peer/transactions and POST /peer/signatures.Implemented bundled transaction processing. Dramatically speeding up response times for POST /peer/transactions.Closed #307. Implementing auto recovery from forks.
    - Deleting last block on failed chain comparision and poor broadhash efficiency.
    - Deleting losing block in case of received fork 1 and 5.Merged #320. Allowing "+" char in os version check @4miners.Closed #307. Fixing broken backwards round tick.
    - Refactoring code. Adding __private.sumRound function.
    - Fixing property typo in Rounds.prototype.backwardTick.
    - Fixing property typo in Rounds.prototype.tick.
    - Fixing broken round changes on backwards tick.
    - Fixing broken missed blocks on backwards tick.
    - Fixing broken Rounds.prototype.directionSwap.
    - Summing round from blocks on forwards direction.
    - Do not flush round on direction swap.
    - Adding missing direction swaps.
    ·· Before/after Blocks.prototype.deleteLastBlock.
    ·· Before/after Blocks.prototype.deleteBlocksBefore.
    - Marking undone blocks in mem_accounts.
    ·· Excluding marked accounts from orphaned mem_accounts check.Closed #319. Fixing broadhash update reliability.Closed #323. Fixing bad setInterval strategy.Shortening various peer ban times from 60 to 10 minutes.Closes #322. Fixing multisignature processing.
    - Fixing incorrect message bus arguments.
    - Resetting u_multimin, u_multilifetime on startup.
    - Removing nested balancesSequence (causing timeouts).
    - Updating ready state after processing signature.
    - Fixing max keysgroup size check. Adding ability to add exceptions for existing transactions @TheGoldenEye.
    - Fixing erroneous check on account.multisignatures.
    - Determining multisignatures from sender or transaction asset.
    - Pushing senderPublicKey onto multisignatures.
    - Improving check on requester public key.
    - Improving error messages.
    Frontend
    Using jit-grunt to slightly speed up grunt @Alevale.Updating lisk-js dependency.
    Build
    Added PostgreSQL 9.6.x support to installLisk.sh.Added logrotation support for linux in installLisk.sh.Implemented updateConfig.js for automated config.json updates.Improved installLisk.sh installation efficiency.Add rebuild/url support to installLisk.sh for upgrade and install functions.

    Please join our 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.Please take a look at the Community Fund. It's an important project!













Log in to reply