Beraswap propsoal ideas

BEX
1

Henlo,

I originally posted this in forum.berachain.com only later realizing that there is another forum here where it fits better:

After having played around with beraswap a bit here are some things that I think are problematic and might be changed. For now it is more of a brainstorm to see if others agree with me on something before a real governance proposal, which i wouldn’t know how to write anyway and would rather leave that to professionals who work in the ecosystem.:

  1. ) Publish the source code under a copyleft licence. I think its OK that the berachain company runs the exchange but it should be open source if it is such an integral part of the ecosystem. Otherwise I hope that the foundation would rather choose to prefer another exchange by default that is open source. I doubt that an open sourced beraswap would have any negative economic effects since the attractiveness comes from the fact that it is the largest and central exchange. An open source chain would invite more innovation, be more secure, yada yada, advantages of open source.
  2. ) Use fixed names for LP Pools. Currently LP Pools can be freely named. I think they should be fixed to | | | … currently the pool names can contain illegal and offensive names. Links, advertising etc,… having things open in the internet in my experience only works in small communities. e.g,. The Heil, … Pool
    I’m also a bit concerned that, maybe not through the web interface but, maybe using some encoding not thought off etc. there could be some code injection through the pool names.
  • 2.1. ) Same goes for Reward vaults. Where I already saw the Taiwan Independence token…: Reward Vault | BeraHub
  1. As a direct result of 2) Tokens should be a little bit curated. I would say that there should be clearly defined rules how to get on the berachain default-lists so that basically everyone can get on that list quickly if the token is non controversial, and a governance process to challenge the decision not accept the token. And if that is established the beraswap should only list such pools. That could also prohibit homograph attacks against established tokens e.g. H0NEY vs. HONEY as a stupidly simple example.
  2. Don’t accept additional pools for the default currencies. Well, maybe this is already handled through the whitelisting of reward pools, but since you could currently create pools for e.g. WBERA | HONEY with a 50.0001| 49.9999 Ratio but with lower fees I think you could add confusion, create a “less fee” competion and provide no real value.

Thanks for taking the time to read my ideas. I guess at least the license of beraswap has been discussed at length, if so it would be great if the rationale for having a closed source beraswap is published somewhere.

Best Regards,
Andre

4 Likes