[ANN][LSK] Lisk | Blockchain Application Platform for JavaScript Developers

[cointrader83]

BTC is going to rally so all altcoins going down now. In the weekend all will go up as I think.

[bctacc32]

Does anyone know what's wrong with the blockchain?
Transactions appear/disappear randomly, balances are shown wrongly, withdrawal from Polo doesn't work (txid not found), Bittrex wallet under maintenance..

 

[LiskHQ]

Does anyone know what's wrong with the blockchain?
Transactions appear/disappear randomly, balances are shown wrongly, withdrawal from Polo doesn't work (txid not found), Bittrex wallet under maintenance..

 

The explorer nodes forked. We will restart them as soon as possible.

[bctacc32]

Does anyone know what's wrong with the blockchain?
Transactions appear/disappear randomly, balances are shown wrongly, withdrawal from Polo doesn't work (txid not found), Bittrex wallet under maintenance..

 

The explorer nodes forked. We will restart them as soon as possible.

Ah, okay.
I'm interested, under what circumstances can this happen?
I guess, for example, when a few nodes don't receive transactions for a while (go offline etc.) and after they're online again, consensus is impaired?
(But wouldn't they just resync then?)

[LiskHQ]

Does anyone know what's wrong with the blockchain?
Transactions appear/disappear randomly, balances are shown wrongly, withdrawal from Polo doesn't work (txid not found), Bittrex wallet under maintenance..

 

The explorer nodes forked. We will restart them as soon as possible.

Ah, okay.
I'm interested, under what circumstances can this happen?
I guess, for example, when a few nodes don't receive transactions for a while (go offline etc.) and after they're online again, consensus is impaired?
(But wouldn't they just resync then?)

One reason for example was (which is now fixed in the next release update) a logic problem in block processing. This resulted in a CPU spike when processing a block while there are many transactions on the network at the same time. During that time where the CPU spiked to 100% the node couldn't do anything else, so he fall behind / starved. I.e. chances are high he lands on a fork.

[tomkat]

Does anyone know what's wrong with the blockchain?
Transactions appear/disappear randomly, balances are shown wrongly, withdrawal from Polo doesn't work (txid not found), Bittrex wallet under maintenance..

 

The explorer nodes forked. We will restart them as soon as possible.

Ah, okay.
I'm interested, under what circumstances can this happen?
I guess, for example, when a few nodes don't receive transactions for a while (go offline etc.) and after they're online again, consensus is impaired?
(But wouldn't they just resync then?)

One reason for example was (which is now fixed in the next release update) a logic problem in block processing. This resulted in a CPU spike when processing a block while there are many transactions on the network at the same time. During that time where the CPU spiked to 100% the node couldn't do anything else, so he fall behind / starved. I.e. chances are high he lands on a fork.

Is this something that you can resolve, or such issues are correctly identified by RISE team as a major flaw? See quote from RISE thread below

...
As you all probably have assumed, we have encountered numerous issues with the delegate system, and the security of the rise-core code base. A couple of highlights:

• Slow system speed - 10> Transactions per second - Above this causes forks
• DDoS Vulnerabilities in multiple core system packages that require significant updates to resolve
• Spotty delegate communication
• High resource usage for nodes

The above issues are difficult to resolve in the current code base (As evidenced by the original developers lack of resolution up until this point).

In order to find a solution for this, we are going back to the drawing board, and designing an entirely new architecture for the system, not based on anything that is currently in existence. We will be writing a new codebase from scratch.
...

[LiskHQ]

Does anyone know what's wrong with the blockchain?
Transactions appear/disappear randomly, balances are shown wrongly, withdrawal from Polo doesn't work (txid not found), Bittrex wallet under maintenance..

 

The explorer nodes forked. We will restart them as soon as possible.

Ah, okay.
I'm interested, under what circumstances can this happen?
I guess, for example, when a few nodes don't receive transactions for a while (go offline etc.) and after they're online again, consensus is impaired?
(But wouldn't they just resync then?)

One reason for example was (which is now fixed in the next release update) a logic problem in block processing. This resulted in a CPU spike when processing a block while there are many transactions on the network at the same time. During that time where the CPU spiked to 100% the node couldn't do anything else, so he fall behind / starved. I.e. chances are high he lands on a fork.

Is this something that you can resolve, or such issues are correctly identified by RISE team as a major flaw? See quote from RISE thread below

...
As you all probably have assumed, we have encountered numerous issues with the delegate system, and the security of the rise-core code base. A couple of highlights:

• Slow system speed - 10> Transactions per second - Above this causes forks
• DDoS Vulnerabilities in multiple core system packages that require significant updates to resolve
• Spotty delegate communication
• High resource usage for nodes

The above issues are difficult to resolve in the current code base (As evidenced by the original developers lack of resolution up until this point).

In order to find a solution for this, we are going back to the drawing board, and designing an entirely new architecture for the system, not based on anything that is currently in existence. We will be writing a new codebase from scratch.
...

I already answered your question. The latest test results look very promising. Come to our chat to find out more regarding testing.

[LiskHQ]

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.


Continue reading..


Also check out our new sub page on Lisk.io regarding community delegates.

[tomkat]

Does anyone know what's wrong with the blockchain?
Transactions appear/disappear randomly, balances are shown wrongly, withdrawal from Polo doesn't work (txid not found), Bittrex wallet under maintenance..

 

The explorer nodes forked. We will restart them as soon as possible.

Ah, okay.
I'm interested, under what circumstances can this happen?
I guess, for example, when a few nodes don't receive transactions for a while (go offline etc.) and after they're online again, consensus is impaired?
(But wouldn't they just resync then?)

One reason for example was (which is now fixed in the next release update) a logic problem in block processing. This resulted in a CPU spike when processing a block while there are many transactions on the network at the same time. During that time where the CPU spiked to 100% the node couldn't do anything else, so he fall behind / starved. I.e. chances are high he lands on a fork.

Is this something that you can resolve, or such issues are correctly identified by RISE team as a major flaw? See quote from RISE thread below

...
As you all probably have assumed, we have encountered numerous issues with the delegate system, and the security of the rise-core code base. A couple of highlights:

• Slow system speed - 10> Transactions per second - Above this causes forks
• DDoS Vulnerabilities in multiple core system packages that require significant updates to resolve
• Spotty delegate communication
• High resource usage for nodes

The above issues are difficult to resolve in the current code base (As evidenced by the original developers lack of resolution up until this point).

In order to find a solution for this, we are going back to the drawing board, and designing an entirely new architecture for the system, not based on anything that is currently in existence. We will be writing a new codebase from scratch.
...

I already answered your question. The latest test results look very promising. Come to our chat to find out more regarding testing.

Max, I must have overlooked your answer, and can't find it now. Could you quote it here, or just indicate a page number, if it's not a problem, please?

[LiskHQ]

Does anyone know what's wrong with the blockchain?
Transactions appear/disappear randomly, balances are shown wrongly, withdrawal from Polo doesn't work (txid not found), Bittrex wallet under maintenance..

 

The explorer nodes forked. We will restart them as soon as possible.

Ah, okay.
I'm interested, under what circumstances can this happen?
I guess, for example, when a few nodes don't receive transactions for a while (go offline etc.) and after they're online again, consensus is impaired?
(But wouldn't they just resync then?)

One reason for example was (which is now fixed in the next release update) a logic problem in block processing. This resulted in a CPU spike when processing a block while there are many transactions on the network at the same time. During that time where the CPU spiked to 100% the node couldn't do anything else, so he fall behind / starved. I.e. chances are high he lands on a fork.

Is this something that you can resolve, or such issues are correctly identified by RISE team as a major flaw? See quote from RISE thread below

...
As you all probably have assumed, we have encountered numerous issues with the delegate system, and the security of the rise-core code base. A couple of highlights:

• Slow system speed - 10> Transactions per second - Above this causes forks
• DDoS Vulnerabilities in multiple core system packages that require significant updates to resolve
• Spotty delegate communication
• High resource usage for nodes

The above issues are difficult to resolve in the current code base (As evidenced by the original developers lack of resolution up until this point).

In order to find a solution for this, we are going back to the drawing board, and designing an entirely new architecture for the system, not based on anything that is currently in existence. We will be writing a new codebase from scratch.
...

I already answered your question. The latest test results look very promising. Come to our chat to find out more regarding testing.

Max, I must have overlooked your answer, and can't find it now. Could you quote it here, or just indicate a page number, if it's not a problem, please?

If you think, that this was only one reason and there might be thousand others. With the next update we are going to achieve our first milestone. That means the issues will mostly be fixed, might require another update for adjustments. However, in principle it will work quite good. That means we can allow community forging and the forging rewards.

[tomkat]

Does anyone know what's wrong with the blockchain?
Transactions appear/disappear randomly, balances are shown wrongly, withdrawal from Polo doesn't work (txid not found), Bittrex wallet under maintenance..

 

The explorer nodes forked. We will restart them as soon as possible.

Ah, okay.
I'm interested, under what circumstances can this happen?
I guess, for example, when a few nodes don't receive transactions for a while (go offline etc.) and after they're online again, consensus is impaired?
(But wouldn't they just resync then?)

One reason for example was (which is now fixed in the next release update) a logic problem in block processing. This resulted in a CPU spike when processing a block while there are many transactions on the network at the same time. During that time where the CPU spiked to 100% the node couldn't do anything else, so he fall behind / starved. I.e. chances are high he lands on a fork.

Is this something that you can resolve, or such issues are correctly identified by RISE team as a major flaw? See quote from RISE thread below

...
As you all probably have assumed, we have encountered numerous issues with the delegate system, and the security of the rise-core code base. A couple of highlights:

• Slow system speed - 10> Transactions per second - Above this causes forks
• DDoS Vulnerabilities in multiple core system packages that require significant updates to resolve
• Spotty delegate communication
• High resource usage for nodes

The above issues are difficult to resolve in the current code base (As evidenced by the original developers lack of resolution up until this point).

In order to find a solution for this, we are going back to the drawing board, and designing an entirely new architecture for the system, not based on anything that is currently in existence. We will be writing a new codebase from scratch.
...

I already answered your question. The latest test results look very promising. Come to our chat to find out more regarding testing.

Max, I must have overlooked your answer, and can't find it now. Could you quote it here, or just indicate a page number, if it's not a problem, please?

If you think, that this was only one reason and there might be thousand others. With the next update we are going to achieve our first milestone. That means the issues will mostly be fixed, might require another update for adjustments. However, in principle it will work quite good. That means we can allow community forging and the forging rewards.

Ah, that's what you meant.
Well, I thought you addressed the issues reported by RISE team somewhere earlier (since I quoted their statement few pages back, and now quoted it partially again).
Thanks anyway...

[szachta]

Every vote is cost i can vote for if vote cost 5 lisk i can vote for 10 lisk if you are looking vote.

[spendawgs]

Rise seems to be an exact copy of Lisk.  They dont deserve it because its not their idea

[Ullu-Ka-Patha]

Where is the whitepaper?

[cointrader83]

Where is the whitepaper?

"The Lisk white paper will be published Q1 2017."

[Ullu-Ka-Patha]

Where is the whitepaper?

"The Lisk white paper will be published Q1 2017."

like the way it i was published in july than august and than q4 2016?

[YNWA2806]

Where is the whitepaper?

"The Lisk white paper will be published Q1 2017."

like the way it i was published in july than august and than q4 2016?

Never lose hope......

[LiskHQ]

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.


Continue reading..


Also check out our new sub page on Lisk.io regarding community delegates.

Win up to $800 for writing a proposal and registering a Lisk delegate!

[Antioxidant]

Win up to $800 for writing a proposal and registering a Lisk delegate!

are you serious?

[sxafir]

Pay me lisk and i wil be voting for anyone.