go-ethereum VS contract

Read the q&as on GitHub. Total shambles. No plan, few commits. bizarre replies. Coinbase eventually had to submit a Pull Request as all support channels closed/unanswered. Read it and weep. Last post 15hrs ago, the soap-opera continues. https://github.com/ethereumpow/go-ethereum/pull/17

That is what they have claimed for a while now. Their geth fork has yet to actually implement this chain ID, and they actually don't plan to do so until after the merge has occurred. So there will be some initial chaos as the miners sort things out, but presumably at some point the team will provide the proper code to carry out the fork and enough people will run it to establish a stable network. Presumably. I'll believe it when I see it.

This is the Repo where you can see if the chain ID has been updated: https://github.com/ethereumpow/go-ethereum/blob/master/params/config.go

This was pointed out to them multiple times on their Github repository (https://github.com/ethereumpow/go-ethereum/pulls) and a poll was taken to chose a more appropriate ChainID ( https://www.rcv123.org/results/rr6xjagxbmoR8CSKUSobW6/qtGJMHK7pBeugsJ1KFpv3S) which settled on 1111, but has been ignored.

The fun bit is in the pull requests: https://github.com/ethereumpow/go-ethereum/pulls

Also while our smart contract was audited (see the report here) by an independent security expert, be aware you are using it at your own risk! We would suggest not using very large amounts until the contract is more battle tested.

a while ago we introduced our project and our testnet release (arbitrum rinkeby) here in the subreddit. Thanks again to the people who gave feedback - based on which we have made a short video, we managed to get an audit by an independent security expert (report here ), implemented an option to incentivise decentralised closing of positions, launched a (simple) homepage and hopefully will launch on Arbitrum one the coming days/weeks.