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!
EVM compatibility upgrade and governance proposal process
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.@ClaudioxBarros hopefully this answers your question too
Just FYI, testnet validators with these monikers have missed quite a few blocks, not too sure if its just downtime or because you forgot to upgrade your nodes. If so and you would like to unjail them, please do so.
ok, will take note. @l4zyboi@FrenchXCore. thought you might want to try out certain processes like upgrading the node and running other tests in a sandbox (testnet), but shouldn’t really be a problem for you 2.
If the Testnet Explorer shows correctly, we’ve today 12 Testnet validators being Inactive/jailed (including one of mine), is something particular happened?
Got some crash errors such as:
panic: failed to write batch: leveldb/table: Writer: keys are not in increasing order: “s/k:slashing/n’IjbT\xb5B\xbf\x91\xc5sqsl\xe6\x97\xf5A\xb9șh\x9b\u007f\xd0\xc7|\xdb\x18av\x1b\x00\xe4\x80I3\x00\x00\x00”, “s/k:slashing/n’I\f\x01\x00\x14\xa8\f\x97Z^\xa4r\xc8\x02<i\x87Cx\x1e\xb2]\xe9"H\a\xfbi\r\x00’\x00[\xcdB2\x00\x00\x00”
and it keeps crashing like the database has been corrupted (reported on GitHub as well).
It seems I’ve to set it up from scratch. Anybody got similar problems?
Did you upgrade your code to reflect the update in EVM compatibility?
I believe most of the original testnet validators have already converted their services to either sentry nodes or mainnet validator nodes so they have discontinued any testnet nodes.
My blindgotchi has been deliberately jailed because im running some tests
We have added in a gitbook tutorial guide for metamask for EVM
With the rest of the guides like using Remix or truffle and hardhat, you will be able to deploy your own smart contracts and ERC20 tokens. You can give the Remix tutorial a go and mint your own ERC20 tokens.
Hi guys,
I want to make a validator node but now the spots are full. Can someone tell me if it’s ok to create it now or wait until the spots reach the new 100 limit? I really want to get a spot next time and it doesn’t matter if I have to run it for a period without getting any rewards.
more can be created, the stronger 50 get to be validating blocks, there are some team nodes there if you see still have very little delegations, if you set up a node and have more delegations the lowest one will just become inactive, the team won’t mind it brings on more decentralisation.
One of the validators is retiring due to personal and a career change, and he won’t be able to maintain with his new job. So to add to your clear info, he will be amongst the 50 validators and can build up slowly.
Also note once the validators node reaches 100fx its in active state, meaning creating blocks, only then not before. The minimum fx needed to start the node is only 100fx self bonded.