 Soeben wurde Version 0.4.0a fürs Testnet veröffentlicht. Mit diesem großen Upgrade wurden grundlegende Verbesserungen und Änderungen vorgenommen und somit ist diese Version nicht kompatibel zu vorherigen Versionen. Stoppt Lisk und entfernt die vorherige Version vollständig, inkl. Ordner, bevor Ihr die neue Version installiert (siehe Upgrade-Infos). Fürs Mainnet gibt es noch keine neue Version. Sobald eine neue Version fürs Mainnet kommt, werdet Ihr wie immer schnell informiert. Erst einmal werden wir diese Version ausgiebig testen. Upgrade-InfosEinige Änderungen in Version 0.4.0a- Initial resolution to address collision issue
- Improved block processing logic (for faster syncing over network)
- New peer selection code (for more reliable syncing over network)
- Added ability to snapshot highest round, e.g. --snapshot=highest
- Added optional API rate limiting (for /api and /peer)
- Support for uptime snapshotting
Bitte retweeten: https://twitter.com/Lisk_DE/status/776065731989475328danke, Upgrade klappte tiptop. 0.4.0a ist noch deutlich resourcen hungriger als 0.3.3, allerdings wird sich das in den nächsten Tagen noch deutlich verbessern mit angepassten 0.4.0b und c Versionen |
|
|
|
Dear Developers!
Client crashes after loading,
WHAT IS GOING WRONG?:
make that fixes it |
|
|
|
As written in my proposal http://forum.lisk.io/viewtopic.php?f=6&t=54&hilit=cc001 I want to spend some of my funds for interesting and promising Lisk projects/apps/faucets/.... Please let me know in PM if you run such a project and if you are interested in getting some regular delegate funds from me to run or develop it. I want to actively support the Lisk ecosystem with my delegate income. And please vote for delegate cc001 if you want to support Lisk and a delegate node that is active already since the beginning and has proven to be very reliable, stable and secure |
|
|
|
hey guys, please vote for my strong and secure delegate node cc001 to protect your worthy Lisk. I'll spend a big part of my delegate income for Lisk-Projects and the Lisk-Ecosystem to push Lisk to the moooon  See my setup and donations here: http://forum.lisk.io/viewtopic.php?f=6&t=54 |
|
|
|
any update regarding the network fees ?
Regular transactions
0.1 LISK
Username Registration
100 LISK
Delegate Registration
100 LISK
Add a Contact
1 LISK
Dapp Registration
500 LISK
Second Passphrase Setup
5 LISK
Multi-Signature Registration
5 LISK for each Multi-Signature member
Username registration doesn't exist anymore. Delegate and Dapp registration is new 25 LSK See https://blog.lisk.io/lisk-v0-3-0-release-announcement-5c9b00e68eef#.t1j7mbe8z |
|
|
|
Hey been out sick for past few days so I have missed a lot. So, validating the passphrase is just a step to make sure we have the correct ones saved?
Exactly. The validation is not mandatory but recommended. |
|
|
|
Want to announce my new service here, I have been in crypto for a long time and really like what Lisk is trying to do. I wanted to contribute and develop a fully automated Lisk pool (the first?). LiskPool.comhttps://www.liskpool.comLiskPool will reward all voters with a share of the pool rewards + fees. Atleast 85% of the pool income will be paid to the voters 15% will be used to pay for the servers and future pool development (this might change depending on the Lisk price). All delegates are hosted in datacenters in the EU/US. Payouts are processed automatically when your balance reaches 10 Lisk. Rewards are calculated based on the amount of votes for LiskPool delegates, voting for other delegates (decreases the LiskPool delegate ranking) decreases your payout. All payouts are processed automatically to your Lisk address, all you have to do is vote for the LiskPool delegates. LiskPool aims for multiple delegates but will never run more then 33 delegates. LiskPool is ready now and will be available the moment Lisk launches, until then we will be stress testing our pool on our own Lisk testnet. At launch we will start with 10 forging servers(delegates), all 33 delegate names will be registered at launch to avoid name squatting by someone else. Questions are best asked on the LiskPool thread here: https://forum.lisk.io/viewtopic.php?f=25&t=150I don't like the idea of such a pool because: This is a big centralization problem! The idea of the 101 delegates is to secure the network with 101 independent and different nodes, run by 101 different people. This pool wants to run up to 33% of all delegates. Meaning, they control 33% of the complete network. What stops them to setup 50 or 80 nodes? That is exactly like a bitcoin mining pool with 33% mining power. And everybody agrees that the centralization problem is pretty severe. The pool is buying all his votes with money. The idea of the voting model is to provide good quality service to secure the network to get voted. Not buying votes. You would't want that Trump or Hillary pays 50$ to everybody who votes for them, right? It doesn't help to secure the network. To the contrary. It makes it much more weak. It only help the runner of the pool and it's voters to get more money. I see not one single reason why such a pool should be implemented See here why a lot of different individual nodes and node operators are important to guarantee a secure network: http://forum.lisk.io/viewtopic.php?f=6&t=54#p302 |
|
|
|
# To verify list
PunkRock, bcmine, cc001, techbytes, Splatters, Mrboot, Pinkman12345, Th4o, someonesomeone, Trader19, Cryptomaik, ZenFR, Hollowman338
DevKing, Vega, Simeul, ZenFR, Nuevo, KirPan, Bysup, Grumlin, XIRDO
Hey Gr33nDrag0n You can check me out here http://forum.lisk.io/viewtopic.php?f=6&t=54http://forum.lisk.io/viewtopic.php?f=28&t=47#p108and my bitcointalk posts. I will post more info about me, my delegate node, and my plans how to run the node in the netx two weeks. I don't want to rush things. Running a stable delegate node needs some planning is not done by just promising anything. |
|
|
|
Future features: please propose, I may develop some kind of democratic Dapp to vote, finance and let the community push for their priorities.
hey fixcrypt, your doing a great job, I will vote for you. possible feature for your client: It would be nice to add functionality to distribute funds to multiple addresses (useful to distribute a part of the delegate income) according to specified percentages. I thought about something like that: You can add your forging account (already possible now) then you can add multiple lisk adresses with a percentage value. Like address1: 2%, address2: 3%, address3: 5%, address4: 10%, address5: 80% (your personal savings account) Then, every day or week or month you can choose the amount you forged during the last period, and it will distribute the funds. So, lets say you forged 1000 Lisk last Week, then it will distribute 20 to address1, and 30 to address2, 50 to address3 and 100 to address4 and the rest to account5, your personal savings. Do you understand what I mean? and yes, your address would be the first I would add to distribute some of my forging rewards to. |
|
|
|
MalReynolds... Your post about being a delegate made me think a lot. The wise man is not afraid to admit when he is wrong. And I think that the share of 30% of my delegate earnings between the majors voters is an error. I will update my statement in Lisk forum. It's better to use 100% instead of 60% of funds to pay myself and my team of JS coders. Then, we could update our project status every month in our Lisk community, as a proof of actual work in the dapp development As many of you said, it will create more value to the community in the near future. This way will be better  TRH I like that! |
|
|
|
I have a few questions:
1) Can anyone here keep a list of delegates? It can be on the first page or official website.
2) I have 4 different transactions on the ICO. Can I register as deligate and under what username I must enter in the login.lisk.io page to put my candidacy.
3) What is needed to become a delegate and what responsibilities have a delegate?
4) A delegate may be removed if he fails to doing him responsibility?
5) Can be a delegate to a person who has only buy about 3k LISK on ICO?
Currently the real network is not yet online. login.lisk.io is only a test network. You will have to wait until the start (around 11th of April) to register your username and put your votes. You can use login.lisk.io in the meantime to play around and learn some stuff. |
|
|
|
Firstly I want to agree with anyone who thinks that sharing their forging income with people who voted for you is not the way to go. I'm pretty sure that buying the votes to stay in top 101 in many cases gonna cause laziness in delegates. Although they may keep the node secured, updated and active most of the time, in my opinion that's only a part of the job what ACTIVE Delegate should do..
I would see delegates more like an Ambassadors who gonna actively promote Lisk among JS developers and later even among the potential users of dapps.
I totally agree. You found a place on my voting list Please post here: http://forum.lisk.io/viewforum.php?f=6 |
|
|
|
maybe it gets a little bit misunderstood.
But when you vote for someone who shares te forging rewards means that he also has to have a lot of uptime with his node, thus securing the network.
So basically in my eyes by getting forge rewards you also vote for someone who secures the network.
So a win/win for both parties.
But indeed people choose on who they vote so someone who shares the rewards has to get enough to become top 101.
The only reason of forging/delegate is running/securing the network. The rewards are just an incentive to do so. And the voters should vote for good delegates to secure the network (to protect their valuable coins). Distributing the forging rewards to the voters is IMHO more like "buying votes". Distributing forging rewards to dapp development and marketing is better IMHO. |
|
|
|
It would be nice if there was a way to "vote" rewards to Nodes after each month or quarter and also options to Remove delegates when the liskers think their not adding enough value.
So a much smaller flat payment for being a delegate and then options to reward delegates that we deem added a lot of value.
You can change your votes as often as you want (well, max every 17min), but it costs a fee every time you do so. |
|
|
|
set up a Crypti node as a Standby Delegate for practice.
You even can become an active delegate on your own test network if you login to the genesis account, vote with it for your test node and deselect some of the genesisDelegates. |
|
|
|
I posted the following at the thread above: Hi all, I'm MalReynolds and I would like your vote as a Lisk Active Delegate. There has been a lot of discussion on what makes a good delegate. Enthusiasm. Community activity. Reward Pools. All these things are certainly important. I ran a Crypti node for many months and so I have a pretty good idea of what the job of Active Delegate entails. It's harder than it might seem to be. Let me tell you what I think is important about being a delegate: uptime, updates and upvotes. I will monitor my VPS to keep it online as much as possible. I will install the Lisk updates as they are issued. I will upvote new Standby Delegates as required to keep all 101 Active Delegates productive and forging. Delegated Proof of Stake (DPoS) is harder than it looks to get right as a functioning system. I will discuss weaknesses I see in the DPoS delegate network and work to raise public awareness to correct those weaknesses as they occur. My primary focus is a commitment to making Lisk DPoS work smoothly as a whole. Good Post! I totally agree |
|
|
|
|
Show Posts
