Author

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

legendary
Activity: 2020
Merit: 1041
At $10 a coin, each delegate will actually earn $1.5 million / year (150K x $10)

I don't mind this one bit, because less people will be selling.



It is a problem : the dev team should change this.

that's assuming that it becomes $10.  At a realistic ICO price of you know Fucking 7 cents, it's barley enough to cover what some of us pay in server fees.

Bullshit. at 7 cents you stilll 10k a year, which more than enough for server fees.

https://fdcservers.net/fdc_order/index_5.php?plan_id=726 that one in particular seems to be popular with a few folk.
lol true but so is calculating the value at $10 per lisk

Oh and some people are discussing purchasing $500+ month servers for lisk nodes.

Can you link to the server package your referring to ? if not ill have to call BULLSHIT on that.


https://fdcservers.net/fdc_order/index_5.php?plan_id=726

What part of one time setup fee is unclear to you?
member
Activity: 74
Merit: 10
At $10 a coin, each delegate will actually earn $1.5 million / year (150K x $10)

I don't mind this one bit, because less people will be selling.



It is a problem : the dev team should change this.

that's assuming that it becomes $10.  At a realistic ICO price of you know Fucking 7 cents, it's barley enough to cover what some of us pay in server fees.

Bullshit. at 7 cents you stilll 10k a year, which more than enough for server fees.

https://fdcservers.net/fdc_order/index_5.php?plan_id=726 that one in particular seems to be popular with a few folk.
lol true but so is calculating the value at $10 per lisk

Oh and some people are discussing purchasing $500+ month servers for lisk nodes.

Can you link to the server package your referring to ? if not ill have to call BULLSHIT on that.


https://fdcservers.net/fdc_order/index_5.php?plan_id=726
hero member
Activity: 518
Merit: 501
I think it is good that the delegate reward and motivation is getting a good public discussion.  I am biased because I want to be a delegate.   Because of that bias, I will never say anything negative about those who want to set up nodes that would share their reward with others somehow.  Good luck to you.  

As for more delegates - 1001 instead of 101, to spread the wealth around - that ain't gonna happen.   Lisk has a 10 second blocktime.  There is a limit to how many delegates you can coordinate worldwide in 10 seconds, and that number is around 101.

Here is the key point that needs to be at the center of all delegate reward discussions:

TANSTAAFL = There ain't no such thing as a free lunch.  
TANSTAFFL = The computers that run Lisk have got to be paid for somehow.

If Lisk were a start-up business there would be this huge 500 page IT plan about how many computers to get, and what kind of bandwidth, and what kind of support services to buy, and growth projections, and parts lists, and on and on and on.  And oh, yeah, a budget.

Lisk is not a startup business and there is no master IT plan and no budget.  We are making this up as we go along and we are less than 90 days in.

Initial indications are Lisk is gong to be a BIG DEAL with LOTS OF GROWTH and LOTS OF TRAFFIC.  That means some big-ass computer power in the back room.  That's gonna cost big money.  Big money in year one, and probably bigger money in year five when the rewards are only 20% of what they are in year one.  How much money will be needed to run all these servers and support systems like DDoS firewalls?  Nobody knows.

When you are talking about "delegate rewards", you are talking about "how to pay for the Lisk computers".

Max had to make a wild-ass guess on how much resources / Lisk / money to pay for the Lisk computer / delegates.  He came up with the "150K Lisk rewards per delegate in year one, tapering down to 30K Lisk in years five and beyond" plan.  Will this plan throw too much or too little resources / Lisk / money at the required computers and the people / delegates that run them?  Probably.  Is this a problem?  That depends.  

Community, err on the side of paying delegates too much over too little.  Paying delegates "too much" means the community may grumble, profit-sharing delegates are voted in, and Lisk continues.  Paying delegates "too little" means the delegates quit, the computers stop, and Lisk dies.








"
When you are talking about "delegate rewards", you are talking about "how to pay for the Lisk computers"."

I realize this all to well but whats happening .. is by putting such huge potential rewards on it that we wont have the Best people for the job.
Everyone wants to be a delegate .. people talking about running 10 in a pool style 3 and sharing half of all 3 and ive read a lot more like that .
I would much rather see the Lisk team setup those 101 servers from ICO funds. More secure they wont quit if the price drops to low etc.
The funds collected could all go to marketing or half to marketing and half to holders of lisk I don't care.
But giving 101 spots to random people that have the best potential bullshit story or give the most back is like giving a monkey a loaded gun.
Just look at the elections people don't Vote for someone to make the "world" better they vote for the guy/girl lining their pockets.


Yes it might play out just like that at the beginning but you cannot say for a fact that it will progress like that forever.  People over time will prove themselves and they will start to rack up more votes pushing those who do nothing out of the 101.

101 is not a permanent future,  the instant someone gets more vote power to beat the 101 spot, they become a forging delegate.

If you weren't so busy guessing what might happen, it would have been better if you would have checked out what has happened on the testnet before you start throwing wild guesses out there.

This thread is over 600 pages, we all have talked about this issue before and those who have been testing it can see that it will work.

It's only guys who come in here every 2-3 weeks that just straight talk shit before trying it out and getting some real results instead of just conjecture.
hero member
Activity: 714
Merit: 512
Is there a simple, (ELI5-esque) explaination of the differences between Crypti and Lisk.  I know the brief history of the two.  Specifically, what I want to know is when the original Crypti project was forked, what improvements and changes were made to make Lisk a different coin?

I can prepare one if you want. I would release it shortly before launch. Smiley

Please prepare it, it's important! I'm interested in this as well.

Yes, I'd appreciate that.  Those of us who never paid attention to Crypti could use a good cheatsheet explaining why the two projects are similar but having the Lisk fork was a good idea.

The comparison will only show the difference between the last Crypti version and the latest (launch) Lisk version.

Why it was a good idea to fork:

- A "new" team with a huge motivation.
- Fundings which are sufficient for years.
- A bigger community than Crypti ever had.
- A project with clear leadership, which is utterly important.
- A more rapid development cycle.

That's just the beginning. But I don't want to go too deep into that. I will prepare a feature comparison for launch, so people see the value we are building with Lisk. Smiley



Just do what you have planned ... we believe in you, everything will be fine! Wink

And it is very important to prepare a great and loud start Lisk ... Wink
legendary
Activity: 1526
Merit: 1014
In the forum https://forum.lisk.io/viewforum.php?f=6 you have a list of delegates, information about them, their side projects when MainNet is launched and more.
full member
Activity: 224
Merit: 100
The real project with potential here is Waves.
This is about LISK,not waves. Wink

Everytime someone posts about shitty "Waves" here, simply reply with this 2 facts:

FACT #1:: One person owns 60% of ALL Waves coins. He invested about 3000 BTC in Waves ICO, consecutively WITHIN ONE MINUTE ON 4/12/16 23:26:

Waves ICO address: https://blockchain.info/address/3DWBSSAue32YS8PcW2gLs6m52BCCv3UgDA

date                   description        moneyIn Out   transaction number
4/13/16 2:42   PAYMENT RECEIVED   14   0   cb9f7f367fa4d53c4d4204670c2746fd33fd2a08f3e623e5a81904ad8233b2f7               
4/13/16 2:00   PAYMENT RECEIVED   28   0   832e301fbf286a95f1f9f28f64d76d9baf1b55bb12d3b68a866ba5808c409e5d               
4/13/16 1:51   PAYMENT RECEIVED   2   0   da161f2891d2dd2eb89dc24050e606e2c650922098ca18c46ba6edfab73eec3e               
4/13/16 1:33   PAYMENT RECEIVED   46   0   540d35eccf9d172ec5d78d17975746a6fc0fd6bea3c739384f6255d5640a6fe5               
4/13/16 1:22   PAYMENT RECEIVED   40   0   e3f3e9f1d4bb8e5c24c06ed714ae737d9805d047dd852089b300d70202796557               
4/13/16 1:14   PAYMENT RECEIVED   68   0   b6aa2b0c11c9b14c607610a804f4c4869a0bf1753f45e282f5dffeb5b418990e               
4/13/16 0:45   PAYMENT RECEIVED   21   0   975fa9078a81fc26ac8768c0127d58afc9cb7a772f94b053aba1650c49e92360               
4/13/16 0:20   PAYMENT RECEIVED   33   0   4c0c1d58697677765312ec5eeaf7cd12d96d022763f2662138100f33478ff89d               
4/13/16 0:02   PAYMENT RECEIVED   19   0   efb36fdce4a39f8ed4064417d6dba085d8975713cb3c68dc78721251a8e43cf2               
4/12/16 23:50   PAYMENT RECEIVED   80   0   6a4c888bf5872a8de8762be40e77ae107515e5dede9f47aa4f8e99dd1743517f               
4/12/16 23:40   PAYMENT RECEIVED   1   0   3089f0cfd13010f7205ea602197cbb22dfc5161cd57f895dc50a639a57049c67               
4/12/16 23:40   PAYMENT RECEIVED   1   0   ad247640c3e78877b0d1bb59eca1ffe843e85f9b604ccdf02cf543071e090f86               
4/12/16 23:40   PAYMENT RECEIVED   1   0   2996f4b34d27997b81b9ae131a9450832296a2ec6680cb5d1b2f7a6c8dd3a1c7               
4/12/16 23:40   PAYMENT RECEIVED   1   0   6d0ecc1f26e33cf427c8894fe633caf34ca68aad066812f00d24dc520e57c847               
4/12/16 23:40   PAYMENT RECEIVED   1   0   b383af81beb480f47a6d63441d15041ef54b33a142c7b638a739218c63c4515a               
4/12/16 23:26   PAYMENT RECEIVED   300   0   556d2947f969730a9648be80017fb10610dc8b9273547965be6e7a40cf269b12               
4/12/16 23:26   PAYMENT RECEIVED   759   0   a2e3ec27b874f09eb51b9fb0dd1ec923208cf955dc12037e991ec6eb37e6237e               
4/12/16 23:26   PAYMENT RECEIVED   300   0   ee4c95e34faf4e272c742655f1c672d6b242690d17c2ffdc041bcb46ebfa7a1d               
4/12/16 23:26   PAYMENT RECEIVED   500   0   e9fe2a339fa5accd5b3a73ba236e7ebc792a8455296419b6fe9bf5c95810fa23               
4/12/16 23:26   PAYMENT RECEIVED   500   0   cf0583bf4606670909595ca1047e48c37f8478548750e84d3b8775f8992d75d6   
            
4/12/16 22:54   PAYMENT RECEIVED   1   0   4564ed4e551fd2a29f67c820f86ed0e35b950c507fbe0323a1b9f60101bbce5f               
4/12/16 22:54   PAYMENT RECEIVED   10   0   3a35ca8b2f6048672572c47de0c8d4fe402ef561881b24a5bb273147f66be051               
4/12/16 22:37   PAYMENT RECEIVED   100   0   d0a70bba97781d4687eef6d9ec31781917cf4c10aaa206b81c7c1fe4940a9ca9               
4/12/16 22:01   PAYMENT RECEIVED   1   0   b37988446cb1e4f75bfaef0aa462c6f658377c5cd60b592541302799c91ee048               
4/12/16 21:14   PAYMENT RECEIVED   0.001   0   983d078eec9fc81e43e99fa6573012630e211e4f0493e5948d9bf177164cc6db   
            

FACT #2: Donations to Waves ICO have almost stopped completely after the initial whale who invested on day 1 to create buzz for their ICO.

legendary
Activity: 2020
Merit: 1041
Is there a list of delegates that will be profit sharing? to get votes


thank you for proving my point ..
legendary
Activity: 2020
Merit: 1041
I think it is good that the delegate reward and motivation is getting a good public discussion.  I am biased because I want to be a delegate.   Because of that bias, I will never say anything negative about those who want to set up nodes that would share their reward with others somehow.  Good luck to you.  

As for more delegates - 1001 instead of 101, to spread the wealth around - that ain't gonna happen.   Lisk has a 10 second blocktime.  There is a limit to how many delegates you can coordinate worldwide in 10 seconds, and that number is around 101.

Here is the key point that needs to be at the center of all delegate reward discussions:

TANSTAAFL = There ain't no such thing as a free lunch.  
TANSTAFFL = The computers that run Lisk have got to be paid for somehow.

If Lisk were a start-up business there would be this huge 500 page IT plan about how many computers to get, and what kind of bandwidth, and what kind of support services to buy, and growth projections, and parts lists, and on and on and on.  And oh, yeah, a budget.

Lisk is not a startup business and there is no master IT plan and no budget.  We are making this up as we go along and we are less than 90 days in.

Initial indications are Lisk is gong to be a BIG DEAL with LOTS OF GROWTH and LOTS OF TRAFFIC.  That means some big-ass computer power in the back room.  That's gonna cost big money.  Big money in year one, and probably bigger money in year five when the rewards are only 20% of what they are in year one.  How much money will be needed to run all these servers and support systems like DDoS firewalls?  Nobody knows.

When you are talking about "delegate rewards", you are talking about "how to pay for the Lisk computers".

Max had to make a wild-ass guess on how much resources / Lisk / money to pay for the Lisk computer / delegates.  He came up with the "150K Lisk rewards per delegate in year one, tapering down to 30K Lisk in years five and beyond" plan.  Will this plan throw too much or too little resources / Lisk / money at the required computers and the people / delegates that run them?  Probably.  Is this a problem?  That depends.  

Community, err on the side of paying delegates too much over too little.  Paying delegates "too much" means the community may grumble, profit-sharing delegates are voted in, and Lisk continues.  Paying delegates "too little" means the delegates quit, the computers stop, and Lisk dies.








"
When you are talking about "delegate rewards", you are talking about "how to pay for the Lisk computers"."

I realize this all to well but whats happening .. is by putting such huge potential rewards on it that we wont have the Best people for the job.
Everyone wants to be a delegate .. people talking about running 10 in a pool style 3 and sharing half of all 3 and ive read a lot more like that .
I would much rather see the Lisk team setup those 101 servers from ICO funds. More secure they wont quit if the price drops to low etc.
The funds collected could all go to marketing or half to marketing and half to holders of lisk I don't care.
But giving 101 spots to random people that have the best potential bullshit story or give the most back is like giving a monkey a loaded gun.
Just look at the elections people don't Vote for someone to make the "world" better they vote for the guy/girl lining their pockets.
sr. member
Activity: 302
Merit: 250
Is there a list of delegates that will be profit sharing? to get votes
full member
Activity: 123
Merit: 100
The real project with potential here is Waves.
This is about LISK,not waves. Wink
hero member
Activity: 518
Merit: 501
Sigh.


don't worry dude, those guys understand.  They missed the ICO.
legendary
Activity: 938
Merit: 1000
hero member
Activity: 518
Merit: 501
The real project with potential here is Waves.
potential...For me to POOP on!

hero member
Activity: 868
Merit: 1000
The real project with potential here is Waves.
legendary
Activity: 938
Merit: 1000
I think it is good that the delegate reward and motivation is getting a good public discussion.  I am biased because I want to be a delegate.   Because of that bias, I will never say anything negative about those who want to set up nodes that would share their reward with others somehow.  Good luck to you.  

As for more delegates - 1001 instead of 101, to spread the wealth around - that ain't gonna happen.   Lisk has a 10 second blocktime.  There is a limit to how many delegates you can coordinate worldwide in 10 seconds, and that number is around 101.

Here is the key point that needs to be at the center of all delegate reward discussions:

TANSTAAFL = There ain't no such thing as a free lunch.  
TANSTAFFL = The computers that run Lisk have got to be paid for somehow.

If Lisk were a start-up business there would be this huge 500 page IT plan about how many computers to get, and what kind of bandwidth, and what kind of support services to buy, and growth projections, and parts lists, and on and on and on.  And oh, yeah, a budget.

Lisk is not a startup business and there is no master IT plan and no budget.  We are making this up as we go along and we are less than 90 days in.

Initial indications are Lisk is gong to be a BIG DEAL with LOTS OF GROWTH and LOTS OF TRAFFIC.  That means some big-ass computer power in the back room.  That's gonna cost big money.  Big money in year one, and probably bigger money in year five when the rewards are only 20% of what they are in year one.  How much money will be needed to run all these servers and support systems like DDoS firewalls?  Nobody knows.

When you are talking about "delegate rewards", you are talking about "how to pay for the Lisk computers".

Max had to make a wild-ass guess on how much resources / Lisk / money to pay for the Lisk computer / delegates.  He came up with the "150K Lisk rewards per delegate in year one, tapering down to 30K Lisk in years five and beyond" plan.  Will this plan throw too much or too little resources / Lisk / money at the required computers and the people / delegates that run them?  Probably.  Is this a problem?  That depends.  

Community, err on the side of paying delegates too much over too little.  Paying delegates "too much" means the community may grumble, profit-sharing delegates are voted in, and Lisk continues.  Paying delegates "too little" means the delegates quit, the computers stop, and Lisk dies.






sr. member
Activity: 347
Merit: 258
Founder of PROCOMMERCE.IO
My name is Crilleaz and I am the owner of LiskFaucets.com. https://forum.lisk.io/viewtopic.php?f=25&t=414

I am here to become a delegate. My server is run via Vultr (WON'T use the $5 server when mainnet launches) to ensure the best possible uptime and quality and I am already optimizing the security. SSH keys, firewall and Fail2Ban to start with. I will do everything to ensure a safe environment for Lisk and will work with experts on this field, like wannabe (http://forum.lisk.io/viewtopic.php?f=6&t=403).

What will I do with the funds I receive?
50% will go towards my faucets. It will be my way to give back to the community. Furthermore, 10% will be used for Lisk marketing on this forum. These funds will make it possible to give out higher rewards towards early supporters of Lisk.

Please vote for me now - on the testnet, and when the mainnet launches.

My delegate name is LiskFaucets. My address is 12596390308945516244L. Current rank: 1317.


 i think i found were my vote is going
full member
Activity: 237
Merit: 100
Maybe one delegate could send a percentage (50%?) of it's LISK to a LISK faucet? I would vote for such a delegate.

I will volunteer for that!

This is a good idea to start with and to share revenue as promised from my delegate: https://forum.lisk.io/viewtopic.php?f=6&t=223

This will be my first action and also first use-case. Mark my words! I am always happy to get voted in MainNET, but please dont see this post opportunity as a sneaky way to advertise. Primary objective is to do action, to deliver and to help the project.

Cheers!
hero member
Activity: 546
Merit: 509
Decentralized Application Platform
Is there a simple, (ELI5-esque) explaination of the differences between Crypti and Lisk.  I know the brief history of the two.  Specifically, what I want to know is when the original Crypti project was forked, what improvements and changes were made to make Lisk a different coin?

I can prepare one if you want. I would release it shortly before launch. Smiley

Please prepare it, it's important! I'm interested in this as well.

Yes, I'd appreciate that.  Those of us who never paid attention to Crypti could use a good cheatsheet explaining why the two projects are similar but having the Lisk fork was a good idea.

The comparison will only show the difference between the last Crypti version and the latest (launch) Lisk version.

Why it was a good idea to fork:

- A "new" team with a huge motivation.
- Fundings which are sufficient for years.
- A bigger community than Crypti ever had.
- A project with clear leadership, which is utterly important.
- A more rapid development cycle.

That's just the beginning. But I don't want to go too deep into that. I will prepare a feature comparison for launch, so people see the value we are building with Lisk. Smiley
full member
Activity: 236
Merit: 100
★ Always strive for the best ★
At $10 a coin, each delegate will actually earn $1.5 million / year (150K x $10)

I don't mind this one bit, because less people will be selling.



It is a problem : the dev team should change this.

that's assuming that it becomes $10.  At a realistic ICO price of you know Fucking 7 cents, it's barley enough to cover what some of us pay in server fees.

Bullshit. at 7 cents you stilll 10k a year, which more than enough for server fees.

At the end of the day only delegates that shares profits will be the actives ones
I hope...

They will play a big part indeed  Smiley http://forum.lisk.io/viewtopic.php?f=6&t=415
hero member
Activity: 518
Merit: 501
At $10 a coin, each delegate will actually earn $1.5 million / year (150K x $10)

I don't mind this one bit, because less people will be selling.



It is a problem : the dev team should change this.

that's assuming that it becomes $10.  At a realistic ICO price of you know Fucking 7 cents, it's barley enough to cover what some of us pay in server fees.

Bullshit. at 7 cents you stilll 10k a year, which more than enough for server fees.

lol true but so is calculating the value at $10 per lisk

Oh and some people are discussing purchasing $500+ month servers for lisk nodes.

Can you link to the server package your referring to ? if not ill have to call BULLSHIT on that.



I know you can argue forever on this kind of shit so let's stop now.  It might not be the best deal but it's none the less true.
Jump to: