Topic: [ANN][LSK] Lisk | Blockchain Application Platform for JavaScript Developers - page 644. (Read 3074310 times)

Hi Max, we completely agree with your viewpoint that lisk platform should be strengthened before community forging start or before building blockchain apps but platform strengthening should have been carried out in the fastest way possible and to save time more developers need to work on it.

LiskHQ has not hired any new developer since June (after Ricarrdo), this is my concern. I know you are actively finding suitable candidates for the job but this has taken too long.

If there would have been two-three additional developers to help Oliver then Mainchain Stabilisation might have been either completed by now or very close to completion. Hope you hire some developers soon.

I love Lisk, again, don't get me wrong. It's just that at the moment there were fanatics making bad rap for Lisk.
Max is a good guy. It's the community that drove me away.

Max hears thousands words of criticism every day and he should grow-up like an anticriticism bulletproof vest. Why no love for Max and his Lisk?

I really never meant to bash. Your community drove me away from Lisk.
I was and always am a supporter. You don't seem to take criticism well do you?

Stop spreading lies. Below is the change log of Lisk v0.4.0 which was released 13 days ago. Currently Lisk v0.5.0a is already on the testnet. Our GitHub has over 1500 commits on the core repository only.


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 undefined resp.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.



Imagine you are sitting in a bus. You want to drive from France to Portugal. What you are saying is, "why are you driving through Spain, when you can be in Portugal directly?". Well, you can't. You have to concentrate on the foundation first, once this is solid, you can concentrate on the SDK. The docs are early alpha examples.

Btw. Emerge, welcome back. You could have notified me that you are posting a bashing article on Lisk, go away for a few months, not even say me that you are not interested anymore in being an ambassador, and now come back to bash Lisk on the forums.

Anyway, your bashing doesn't work. We are hard at work here and our platform is progressing very nicely.

what happend to the lisk price?
the dev should update some news!

How could you say you're focusing on the platform if you're not immersing developers in creating blockchain apps?
The docs are so application specific, even if they followed it they'd basically be creating just 1 type of thing.

How long will it take before this idiot will do something with his coin? Spending all our money on travelling, drinks, hookers, but not on developing the coin maybe it is time to take some legal action against LSK. Walking away with several millions...

Lisk is just what it is . no other development as of the moment . Stagnant asset is not so good investment.

Lisk down and up,down and up to 0.02 BTC.

Lol, everyday dump again) Soon will find a new bottom) 26k sat.

Lol. Well, Lisk's price performance in the last months was more like the Virtual Boy console with Atari's E.T. playing on it. 

So PS4 that charges micro transactions, only those with nothing to do and money can get to play. PS4 is a ripoff, in that case who is Nintendo Switch that anyone can use and is more user friendly?

A fork of ETH? 

Who is PS4 pro?

Understood, but you have to understand that without no games you can't sell any consoles.
And right now Eth is the PS4.

The ICO price was 9 cents. We are now at 19 cent.

https://twitter.com/LiskHQ/status/789747365917954049

Testnet v0.5.0a available for download:
https://downloads.lisk.io/lisk/test/0.5.0a/

One more step towards mainchain stabilization... go, go Lisk 

Lisk is so much valuable coin in the market....

Personally, I'm buying and holding as the price drops. For now the price seems to have stabilised at 29k. I can't see it getting as low as you speculate, we may be lucky to see IPO price again. But never say never.