LISK is doom to fail unless it hires top of the line developers. Look at the current member of LISK
HQ. A 24 year old forum moderator with no programming skills, A bald web designer whose biggest achievement till today is designing LISK logo and a community manager from the jungles of South America. The funniest part is that none of these three clowns ever met each other in life before the establishment of LISK HQ.
You got one thing right. I'm 24 yes, in exactly 1 month I will be 25.  |
|
|
|
Nice to see someone from the same university as me. The blockchain ecosystem evolves in Germany! Congratulations to the IOTA team, we should meet in Berlin! |
|
|
|
So it is actually seed money for future apps? So this can be used of crowdfunding them for example? Same question as jjmv. You guys already have $10000000+ why the need for extra funding? You say The goal of the Community Fund is to collect LSK to guarantee decentralised, long-term development of the Lisk ecosystem. Isn't $10000000+ enough for this? Feels a little greedy to me.... The reaction is natural and I expected it. The LSK in the Community Fund are not for us. It's intended to be used by the community in a decentralised, proposal/voting-based way. A decentralised funding vehicle for the decentralised decision tool mentioned in our roadmap. It basically gives the community power to finance the apps/tools they really want or need. The best thing: It's voluntarily.  It can be, yes. We don't decide on what it will be used for. |
|
|
|
Same question as jjmv. You guys already have $10000000+ why the need for extra funding? You say The goal of the Community Fund is to collect LSK to guarantee decentralised, long-term development of the Lisk ecosystem. Isn't $10000000+ enough for this? Feels a little greedy to me.... Another big LISK holder and admirer, while this fund seems nice incentive it seems a little greedy from my end as well. Wouldn't it be better if community or active delegates would open such fund and not Max or Oliver? Will this fund be used for voting as well? No pun, but Max and Oliver have $10m+ for development (that should last for 5+ years and probably more if properly managed) + they have 8m of their own LISK + bounty fund that could be used as well (probably some other non-named accounts as well, and as such to much voting power as it currently is). Doesn't make any sense to me at least not currently, feels like brining even more power back to LISK team while they would need to focus on decentralizing (LISK in current state is to much centralized for my taste). Why not endorse and leave community for such things. I'll continue to support LISK, but some recent actions are a bit gray at least. Everyone is open to start their own fund. We had this idea with the decentralised voting/proposal app and will follow this path. As you can read in the blog post we are not allowed to initiate a transaction from the account, i.e. we won't vote from it. |
|
|
|
Same question as jjmv. You guys already have $10000000+ why the need for extra funding? You say The goal of the Community Fund is to collect LSK to guarantee decentralised, long-term development of the Lisk ecosystem. Isn't $10000000+ enough for this? Feels a little greedy to me.... The reaction is natural and I expected it. The LSK in the Community Fund are not for us. It's intended to be used by the community in a decentralised, proposal/voting-based way. A decentralised funding vehicle for the decentralised decision tool mentioned in our roadmap. It basically gives the community power to finance the apps/tools they really want or need. The best thing: It's voluntarily. |
|
|
|
Thank you Chin, for distributing our brief statement regarding Bittrex. As I explained in the Lisk chat:The situation is as follows: We advised them to wait for Lisk v0.5.0 to remove an unnecessary administration overhead (i.e. keeping an eye on the servers, logs, internal security measure's, forks etc.). We assumed v0.5.0 will be released a few days earlier. Now it's becoming very clear that it will be released this week (guaranteed!). That however also delayed Bittrex. The situation should become much, much better this week after we have released Lisk v0.5.0. Our brave testers in #testnet can probably confirm it. The best bet is to just keep the LSK on Bittrex for now and withdraw them to a Lisk wallet for long-term "hodling" as soon as the withdrawals/deposits are activated again. Who will gave me free lisk to vote?
Send me your LSK address via PM and I will send you a few LSK to be able to vote for delegates. |
|
|
|
Done! Thanks for the effort. |
|
|
|
Weekly Summary - 010 Welcome to our weekly summary published on Fridays. This week’s summary includes the past 5 days, i.e. from the 14th November until the 18th November. Feel free to read our last Weekly Summary. We put a lot of focus on legal documents, development and testing this week. Please note, we can’t describe every little detail we work on. Below are only the more interesting topics and tasks listed. Continue reading..
|
|
|
|
Win up to $800 for writing a proposal and registering a Lisk delegate!
are you serious? Yes. The biggest amount you can get are 5000 LSK, that's $800. However, that's nothing against what a delegate can earn later on. |
|
|
|
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! |
|
|
|
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. |
|
|
|
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.
|
|
|
|
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. |
|
|
|
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. |
|
|
|
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. |
|
|
|
A New Way in CommunicationsFor 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. Continue reading..
|
|
|
|
Hello everyone,
I just received a very strange message from Joey. I have no idea what he is talking about. He is talking about a Blockchain App which I should have stolen, but I obviously have no intentions to steal/release it at all. Especially not under my name, I asked the person many months ago if he could develop something cool for Lisk, at least 4-5 months before Shift transitioned to our code base. I never "stole" him, it's ridiculous.
Just wanted to share it with the public before nasty lies or FUD appear.
Thanks.
Hi Max, there seems to be something getting lost in communication between the parties involved. I don't know what the message to you was as I haven't spoken Joey yet but our intention is not to spread any lies or fud. Please bear with us as we work to untangle this issue No ill feelings from our side, this is simply a matter of getting the right people in the right room. All resolved, thanks. |
|
|
|
|
Show Posts
