Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Thoughts about: no-eth POA bridge #414

Open
okwme opened this issue Oct 6, 2019 · 0 comments
Open

Thoughts about: no-eth POA bridge #414

okwme opened this issue Oct 6, 2019 · 0 comments

Comments

@okwme
Copy link
Member

okwme commented Oct 6, 2019

Summary

  • Could work for user with wallet or without wherein a burner is provided to them
    • If using burner wallet could actually do full on front-run prevention although would have to limit Eth contract to only accept new clovers from POA bridge to fully enforce
    • Also need to consider how burner wallets are stored / recovered
  • Sign a meta-transaction with all the relevant Clover info
  • MetaTX is submitted to server bot
  • Server bot makes new tx to POA network using the MetaTX as parameter
  • Goes to CloversController contract on POA
  • Either full on-chain verification or signature method,,, actually doesn't matter if POA gas costs are really so low... (~0.0001 ETH per POA token so 1Eth = 10,000 POA token and gasPrice is limited to 1Gwei... seems like using the signature method that will pay for.... 24,821,903 Clovers??? lol)
  • Once Clover is verified it should trigger the bridge contract to make a new transaction for mainnet
  • Mainnet transaction should be destined for new CloversController which has public function that confirms sender is bridge and originated from CloversController on POA
  • If those two things check out then Controller should mint new Clover
    • If Clover is meant to be exchanged for reward... then ok, pay out the person...
    • If Clover is meant to be kept, user needs to have enough CC in their account otherwise tx should fail

Potential problems

  • Rate limiting on Bridge network
  • They'll be paying all Eth costs, that can only go on for so long. What happens when they rate limit? Will they ask to be paid back? If so, maybe we could turn them into batch registration where the payout is used to pay back the bridge? This would be very attractive to front run across networks unfortunately. In that case I could force all minting to go through the POA network. This would also allow some Clovers to stay on POA... Although this would need a state transfer from Eth to POA with all previously registered Clovers. Maybe not so expensive but a bit of a hassle.
  • Make sure tx doesn't take more gas than is currently being limited on Bridge network.
  • How should Clover rewards work if gas is no longer a limiting factor to shit clovers?
    • Maybe we transition to bounty system by then so there are no automatic payouts?
    • Maybe we just reduce the automatic payouts to 3x and 5x? Could pretty easily just make a new condition on the reward function that if the uint256 symmetries isn't above some level it's considered 0. Could keep recordingn symmetry types and the 3x diagonals versus 3x perpendiculars could continue to adjust with rarity.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant