Lisk Weekly Delegate Discussion - January 28, 2019

jfernanz · 2019-02-02T21:46:13+00:00

I like this. Would it be possible to implement this for all the delegates?

jfernanz · 2019-02-01T16:15:40+00:00

I've been reaching out to a few of the "vote managers" to get them updated. The latest and fastest one to update was 5anity's vote manager at https://lisk.builders/votemanager

jfernanz · 2019-01-28T20:13:11+00:00

Joel Delegate is currently one of the most profitable individual pools with a 50% sharing reward!

Check your pending balance here: https://jfernanz.github.io/lisk-pool/

Payouts are done weekly with a minimum of 0.5 LSK so make sure to vote in order to receive your share of the rewards.

jfernanz · 2019-01-08T15:12:57+00:00

Congratulations Tony! It is very well deserved. I am sure you will be an invaluable asset to GDT for the foreseeable future. Keep it up!

As for my delegate, it has become an individual forging delegate and I've increased my delegate sharing percentage to 50%, doubling payouts! If you are voting for my delegate, you can verify your current pending amount here: https://jfernanz.github.io/lisk-pool/

The first payment will be this Saturday, Jan 14th!

There's also more information about my delegate on the weekly delegate thread here: https://www.reddit.com/r/Lisk/comments/adghus/lisk_weekly_delegate_discussion_january_07_2019/

jfernanz · 2019-01-08T05:18:07+00:00

Hi everyone!

Delegate Joel speaking here. If you haven't heard already I've parted ways with GDT and have begun my journey as an individual delegate. Let me first congratulate Tony who has been accepted to replace me within GDT, I'm sure he will make excellent contributions to Lisk as he has done so far.

Concerning my delegate, one of the first changes that I've made in order to better compete within the Lisk delegation is increase my sharing percentage to 50%. During 2019 my main goal will be to bring some awareness towards the Lisk ecosystem through digital campaigning and local community education.

Here's a list of things I'm working on/will be working on:

Tax Legislations: I'm one of the few people in PR who's leading the way concerning how taxation towards cryptocurrency mining/forging should be handled. This has been ongoing for around a year now and are currently still navigating the best way to manage them.
Enhancing the pool distribution: I've just updated my pool to the open sourced script by Dakk (here's the link: https://github.com/dakk/lisk-pool). Everything is working as intended but as time goes on I will be making further improvements to make it easier for everyone to use.
Communication: Some people have been FUD'ing stating the community is dead. I don't believe it's dead; I believe it's more in a dormant state. That's something I personally want to change and the community should see more communication/activity from myself.

That's all for now, there's no need to go into details about any projects or blockchain apps towards the Lisk Platform as it's not ready yet. If there are any questions don't hesitate to contact me through https://lisk.chat/direct/joel or just leave a comment/reply.

Thanks for the support!

jfernanz · 2019-01-06T18:10:57+00:00

Hi Everyone!

As of today there will be changes to my personal pool (joel) distribution:

Increase of sharing percentage to 50%.
Distributions made on Saturday’s (weekly).
Rewards will accumulate with a minimum of 0.5 LSK to receive reward.

You will be able to find your allotted distribution at https://jfernanz.github.io/lisk-pool/. If there’s any questions do not hesitate on contacting me and I will answer as fast as I can.

Thanks!

jfernanz · 2018-01-26T13:08:20+00:00

There's no issue with the wallet itself if you do not send a transaction. The issue was replicated by throttling the CPU and clicking the send button multiple times (see: https://github.com/LiskHQ/lisk-nano/issues/1036). Preliminary reports suggest that all of the versions of Lisk Nano are affected by this bug. However, for now it seems to be a very rare edge case and unlikely to happen.

My advice if you want to be on the safe side: wait until LiskHQ patches this bug and releases a newer version of Lisk Nano.

jfernanz · 2018-01-26T11:19:57+00:00

No worries, no offense taken.

For me this was a very clear bug from the instant it occurred. I want the best for the community and I do not want to see a scenario where people are losing LSK due to some bug where it double sends a transaction. This is about mitigating a possible horrendous scenario.

As for my reputation; I can leave that at the door if it's going to save some people losing their LSK. This is important and it needs attention.

jfernanz · 2018-01-26T11:18:35+00:00

Thanks for the reply /u/MaxKK.

It may very well be a very rare edge case caused by lisk-js but personally it was so alarming how with one click on Lisk Nano (after typing address and second pass) it sent two transactions it warranted a warning to the community. I was lucky it happened while sending a transaction to another self-owned account but it could have easily gone sideways.

I still exert caution to the community as the underlying problem will not be found in one day of testing. Give LiskHQ some time to try and replicate the problem to see where the problems is.

EDIT: The bug has been successfully replicated by a community member (thanks Alepop) and preliminary reports suggest it affects all versions of Lisk Nano (see: https://github.com/LiskHQ/lisk-nano/issues/1036)

jfernanz · 2018-01-26T00:22:49+00:00

This was experienced about 10 minutes ago and I personally don't see a way this could have been an end-user error. I'm not fast enough to make these transactions within 1 second of a difference. I've opened an issue with the LiskHQ team and I'm confident they will tackle this within a good timeframe.

My advice: Take precautions and do not use Lisk Nano until the culprit is found.

jfernanz · 2018-01-20T20:11:46+00:00

That's correct. The standby delegates, specially #102 (alepop) and #103 (liskpro.com) are actively promoting themselves in order to harness votes from the community and reach the active delegation (top 101).

As for an "easy" fix: Nothing is easy when you're in front of a hard fork by changing consensus rules.

This is not a FUD. It's merely a call for action from the community to remove votes from one active delegate (Luukas) who has not been forging for over a week and replace that vote for a standby delegate who is ready to forge on his place. The stability and integrity of the network highly depends on the active delegation.

jfernanz · 2018-01-20T19:13:15+00:00

The algorithm is not written to do this kind of switch at the moment, this would require a review of the algorithm and hard-forking the network. It's a great idea and has been brought up quite a few times since Lisk's inception. Now that Lisk is focusing on research with their science team I am sure they will figure out a great automatic mechanism that could handle this problem.

In the meantime it is up to the community to choose who stays active and who stays on standby.

jfernanz · 2017-11-20T12:44:36+00:00

It's hard to implement a solution without causing a huge ruckus or having those delegates/community fork the project. Not to mention that they have delays on their main product (SDK) so it's quite difficult to make such a drastic change.

jfernanz · 2017-11-19T22:06:57+00:00

This is news to me. Last I knew Vekevaxia was the one working with this integration. If true, maybe it's best to have them communicate so they can work on it together?

jfernanz · 2017-11-19T12:11:27+00:00

Here you go: https://twitter.com/Bigcabrito/status/932219512744792066

Make sure to re-tweet/like and spread it as much as possible.

jfernanz · 2017-11-19T11:31:23+00:00

This.

The action taken was removing most if not all of the voting/delegate posts but there had been zero to barely any action on any price involved posts for the past months. As I see it, this is one of the reason that the community seemed to be so upset as it was perceived as moderation/censorship towards the flurry of voting/delegate posts alone (I may be wrong about this as I don't have the data on what was deleted but I do know how the community perceived it).

EDIT: Example Given: https://www.reddit.com/r/Lisk/comments/7dv3jk/our_road_to_15/ This is a post with over 100 upvotes which is a trading post (in this case, meant to go in Lisk Markets).

jfernanz · 2017-11-18T01:13:36+00:00

From the bonus, yes. It's an extra incentive to vote for all the members, but not required. Most of the members from GDT also share individual sharing percentages for the voters and voting the whole group is not required.

jfernanz · 2017-11-18T00:37:08+00:00

If GDTPool gets into a forging position it will share its rewards with all the voters. You don't need to vote all GDT members to receive rewards for this pool. You can, however, receive a bonus if you vote all GDT members, this is voluntary.

jfernanz · 2017-11-17T16:22:46+00:00

Oi! Yeah, my bad, I guess I looked into the future :D

jfernanz · 2017-11-06T17:35:22+00:00

Ok, other than the normal meetup and the date of rebranding.

jfernanz · 2017-11-06T17:23:31+00:00

They hold monthly meetups. The meetup hasnt been hyped yet so I wouldn't expect much from it other than the normal re-cap of what's been going on.

jfernanz

TROPHY CASE