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

well, it would be damn tough to go back to the ICO price in that I got 6,259 (i think) lisk for 1 BTC that was $475 (if i remember correctly)

thus the power of the older ICO's like LISK and ETH that were not scams

so no....it goes back to that price for LISK we are beyond doomed

brad

Are there any projects made on Lisk platform?  If not, are they in progress?

You think LISK will go back to ICO price? I missed buying at ICO. With the bear market lasting a few years now it seems, like it was from 2013-2015, hoping most altcoins goes back to ICO price to make an entry for the 2020 run.

What you are witnessing is actual software development rather than marketeers deluding you into thinking that their new Chinese ICO'd ERC20 token is the Ethereum Killer based on the contents of a flashy white paper that'll mention 10 million TPS and scalability through decentralized quantum sharding.

Does anyone know if there have been any announcements or anything for price breakout or anything like that ....

I think that DPoS algorithm is fast and reliable and it is one of the key element in Lisk ecosystem.

In my opinion, this project will definitely be one of the most successful projects for sure.

the f@ck this update post all about? I'm a little confused, the post of no post? or the post for the next post on update to Version 1.0.0 Beta 9? this is getting ridiculous!

Seems to be a nice project. Definitely worth exploring.

You're right. You lost money faster with a car than with Lisk... 

Thats my man   Now is a great time to accumulate,80,90 dollars in a year is a sure thing, 1000 percent profit, man I"m thinking of selling my car to stock up on lisk and drive a bicycle for a year    

Lisk is still one of my favorite crypto projects. I follow and support this coin since the very beginning. I bought my coins at the ICO and didn´t sell one of them yet.

What is going wrong actually with Lisk ?

The price make me sick 

What do you think on what other major exchanges we"ll be next? I think that after the core 1.0 there will be some huge exchange listings announcements.

Hello everybody. Such a coin deserves to be only on large exchanges. At the moment it is a very powerful ecosystem. I wish everyone good luck.

I checked the Twitter account of Lisk right now and there was a news about the release of the Core 0.9.16.  version. It makes me happy that the team is working so hard.

Do you know that the Core 1.0 will pave the way of sidechains and a fully functional al SDK ? On the config.json of the current 0.9.15 version, there are some informations about Dapps etc, like charest name and unique ID. So Yes, Core 1.0 is a big thing but when it will pop out, everyone will go crazy.

https://blog.lisk.io/further-details-regarding-june-2-network-interruption-7c8f4abdc4fe
Further Details Regarding June 2 Network Interruption


On Saturday, June 2, the Lisk network experienced a temporary halt. Despite the fact that the issue was identified and resolved within several hours, we believe the situation warrants a more thorough explanation of precisely what happened to the Lisk network.

Lisk Core uses PostgreSQL, a relational database. Blocks are stored as rows in a `blocks` table. This table has a foreign key constraint requiring that each block contain the ID of the previous block — the constraint here being that the previous block must already exist in the database. Insert operations which do not conform to the constraint will fail and not be saved. Similar to that, transactions are stored as rows in a `transactions` table, with the different parameters of a transaction, like a timestamp, sender, recipient, and amount, being saved in columns.

In the early hours of last Saturday morning, an anonymous individual broadcasted a transaction to the Lisk network with a timestamp of -3704634000, which comes out to be 1898–12–31 13:00:00 CEST. This requires a manually created and signed transaction, which is how we know it was intentional. The timestamp column in the `transactions` table will only accept a 32-bit integer value (a value between -2,147,483,648 and 2,147,483,647) — the timestamp used exceeded this range. Therefore, the transaction can be described as malformed and malicious; this resulted in the transaction not being inserted into the database. When a block is saved to the database, the block and its corresponding transactions are written as one atomic database operation; if a transaction-insert operation failed, the entire block-insert operation will fail as well. Thus, the whole block with the malformed transaction did not get inserted into the database. All subsequent attempts at block-insertions referenced the block ID of this nonexistent block and failed to insert due to the previous block foreign key constraint. This, in turn, halted all transaction and block-insertions into the database. That is the described security measure we reported on Saturday.