f(x)Core Mainnet Validator Updates

Developers Function X Validators
21

Thank you for information Claudio

1 Like
22

The community has spoken and we have listened. Therefore, we will be increasing the commission rate of the top 5 validators to 5%.

Reason:

  1. By increasing the top 5 validators to 5%, this will hopefully change the dynamics of delegations in the ecosystem and result in the outflow of delegations from validators with higher commission rate to those with lower commission rate. We hope that in doing so, delegations to the top 5 validators will redelegate some of their FX to public validators.
  2. This increment will also give existing validators a chance to increase their own commission rate.

Plan:

  • We plan to do this in stages because of parameter limits ie maxratechange parameter is only 1% per day.
  • And also we want to monitor if there are any drastic changes to the ecosystem especially with regards to the outflow of money from the network so we will slowly increase the commission rate to 5% by next weekend if there are no drastic changes to the network.

Message to public validators:

  • This of course comes as great news but also do take note that we want to promote the correct behaviour in that we want each validator to be secure and stable. The narrative has not changed and our goal is still network security and decentralization.

  • I do implore any new public validators to try setting up on the testnet first before deploying a validator on the mainnet. This will ensure you know how to do the setup, test out certain commands and features. There will be support and help.

  • For existing validators, do yourselves a favour and promote your validator. Provide more transparency like how you monitor your nodes, what is your track record, do you have any programming background (better still if you have a Github as stacked as @kenob), implement and show how you will reward delegators who have staked with you for a long period of time, implement and show how you have contingency plans in case your validator runs into some down time

  • Additionally for those who have gone through the testnet phase with me and would like my endorsement, kindly let me know where and how and I will do it

  • This is a perfect competition market, we can do what we can from our side, but we want you to set up secure nodes with contingency plans and ways to incentivize your delegators to join you!

10 Likes
23

Awesome. True decentralization on the way. Just redelegated my stash into public validators.

1 Like
24

What do you mean as ā€˜endorsementā€™ ?

1 Like
25

you may market and promote your validator node however you want. you can come up with innovative incentive programmes, or you can showcase your security. or to showcase your governance. for now i see most of you just have a twitter handle linked for the webpage.

you can create your own custom web profile, maybe create an avatar or something or link it to a validator resume page and show what youve accomplished like gone through testnet phase (if its on social media i can help you confirm this), set up validator monitoring deviceā€¦ its really up to you and youre only limited by your own imagination :smiley:

so be creative and have fun and see how you can attract more delegators!

1 Like
26

Good idea, showcasing their security.

Like an example, a real-life video of their setups, how they organize them, their backups, etc on Twitter or Forum.

Basically showing reassurance to delegators and future hodlers.

1 Like
27

New proposal: Making f(x)Core EVM compatible for Testnet

The process will be as such:

  • The team will initiate a proposal on 9 DEC 2021 at 11:00am (GMT+8).
  • For Testnet, the proposal voting period is 48 hours.
  • By the end of the voting period, a tutorial on how to upgrade your nodes to be EVM compatible will be up
  • The nodes will need to complete upgrading by 13 DEC 2021, 10:00am (GMT+8) i.e. block height 408000
  • There will be another proposal on 13 DEC 2021, 10:00am (GMT+8) to confirm this change and to initialize EVM compatibility.
  • The nodes who have not upgraded by then will not be part of the consensus and if your validator node experiences too long a downtime, it will be jailed and slashed (more on this you may refer to here ā€œWhat are the slashing conditions?ā€)
  • This entire process will be very similar to how an upgrade will be on the Mainnet so do try it out on Testnet!
16 Likes
28

just to let you know, the first governance for an upgrade in code is optional. iā€™d like to hear your thoughts on this

1 Like
29

Does this mean if voting goes well, this could be ready to launch and used around the end of the year?

1 Like
30

Great. Would you publish a detailed guide to upgrade test node ?

1 Like
31

Update: New Tutorial Document
Hi Everyone, do checkout the latest guide on EVM Upgrade Tutorial

1 Like
32

I have published the guide, as for how detailed it is, ill leave it to you to decide :smiley: you may give me a score from 1-5, (5 being the most detailed) and any fraction in between :innocent:

1 Like
33

I tried, but must have done something wrong, only get error returned when trying any fxcored commands

34

I think it will be nice if fxwallet have costumize themes

35

Hello Richard and everyone

how can i change logo on my validator ?
is that available for change logo?

Thank you

36

Updates 10 Dec 21

  • Grafana security notice: Grafana is vulnerable to directory traversal, allowing access to local files. More information can be found in the the release notes.

  • I have added in a guide in the Node Monitoring Device tutorial under the section ā€œUpdating Node Monitoring Servicesā€

  • The top 5 validators have increased their commission rate to 5%

1 Like
37

@ClaudioxBarros Iā€™ve added in the ports in the Validator Security Notice document

2 Likes
38

Updates 13 Dec 21

  • We have launched a governance proposal on the testnet and this will be for initializing all the nodes to be EVM compatible.
  • Only after this proposal passes, will your nodes be EVM compatible
  • After this proposal is passed, the EVM module will automatically start to run, and the EVM corresponding port number 8545 service will also automatically start.
  • Validators will not need to do anything at this point except maybe vote for the proposal to go through if you want it to

I would like everyone here to be familiar with this entire process because this is how it will be like on mainnet.

  • With regards to retweeting and helping you publicize your validator, I believe @FrenchXCore has tweeted a screenshot of her validator monitoring. if you would like us to retweet about that, just tweet and tag us.

  • Also I have added a more comprehensive tutorial on sentry nodes in so do take a look if you havenā€™t already set up one.

39

I suppose we need to open that 8545 port, then ?

40

Thank you. just one more question about this, all ports are tcp ? for node or for monitoring, for what i saw, all are tcp , no udp