Updates 8-3-22 Validator rewards /status info/creation date queries
Hi fellow validators! I’ve wrote a script to query and generate reports for rewards, validator info_status amongst other things.
You can view the repo here. Pardon me that this was done in a rush and its basically running OS commands, returning the data in a json file and filtering the necessary info. Will look at building APIs so that it will be easier to query on-chain data in the future but feel free to use this for now.
Hi Guys. The provider has some network issue.
“We have identified the reason behind the network interruption in our Duesseldorf data center, which is affecting some of our servers in Duesseldorf. The problem is at a construction site at the highway A46. During digging a cable with 288 fibers was cut, but the workers did not recognize and filled up the hole afterwards, so now they have to dig again to find the actual place of damage. No change of given ETA. Next update will be published in 1 hour.”
Update 29-4-22 Validator rewards /status info/creation date queries
hi everyone, ive realized there was too much info in the previous csv file generations so ive filtered the unnecessary info out. just need to run python index.py and youll get the data you need.
it is really not elegant. but the code will do. You can view the repo here
New Monday Product Release Records Board (Monthly)
Great news! if you think the product pipeline had too much info, well there’s something for you!
New view of the monday board in a monthly view.
I read that FX tx fees will be significantly reduced when EIP1559 gets implemented on FXCore mainnet. While this is a good move to try to incentivise more transactions on the network, I like to know how the team intends to further its decentralization efforts, since a reduction in FX tx fees is likely to deter more f(x) Core mainnet validators joining to secure the network, and may even result in validators deciding to drop off from the network due to unsustainable operations.
As it is, community validators are already receiving a disproportionately smaller amount of company delegation as compared to company validators and therefore rewards in fees. A case in point, Validator Singapore, still attracts the highest delegation amongst the 57 mainnet validators, despite charging a 10% fee. My guess is a sizeable amount of delegation to Validator Singapore must be company owned coins.
I have updated the validator earnings report and fixed some errors thrown
Updated the Readme file to explain the different column headers and fixed the typo @kenorb
Generated the May-22 validator earnings report
@MakeTheSwitch
i think there are two seperate issues in discussion here.
With EIP1559 and a reduction of tx fees, it will inadvertently bring in more tx onto the network will actually increase validator earnings. Additionally with EVM and the enablement of smart contracts and Dapps, there will most likely be more on chain tx.
EVM and lower tx fees will most likely attract more users. With more users and hence more fx holders, this will definitely help in the decentralization of the ecosystem
I certainly hope a 8x reduction in tx fees will attract more than 8x increase in tx volume for fx community validators to realize increased earnings.
I don’t think the issue I raised about decentralization efforts of validators (from company to community) was addressed. Maybe you are not the right party to address it. Hopefully the right party can address it.
I have updated the REST API and GRPC gitbook. There are 2 added links for additional request methods. There is also a description and explanation on how to make requests
Quorum of 40% reached!
Just wanted to update everyone that quorum has reached but that does not mean the rest of the validators/delegators should not vote! Show your support and do vote “Yes” if you want the proposal to pass
Gitbook updates
Updated dependencies like Go version requirements of 1.18
Updated hardware requirements of 4 cores 8GB mininum for EVM upgrade
Reformatted documents to segregate further into mainnet/testnet versions
Updated version requirements for f(x)Core and dependencies
Updates
The team has created an upgrade tutorial for ALL VALIDATORS especially for those who did not participate in the last testnet upgrade.
This is so they can experience the upgrade process prior to Mainnet upgrade
f(x)Core mainnet upgrade V2.1.0 was aborted due to unexpected contradictions with working-on updates. V2.1.1 was released to continue the fxv2 upgrade proposed to take place at height 5,713,000.
Validators on f(x)Core Mainnet need to abort the upgrade V2.1.0 and use V2.1.1 for the fxv2 upgrade
