You should talk to @bobinson, he worked on Sidechain Operator Node ( SONs ) for PeerPlays so maybe some code could be used for Hive too.
https://peerplays.gitbook.io/community-project-docs/son/son-requirements-specification
You are viewing a single comment's thread from:
Definitely will be reviewing the code they added to peerplays. He mentioned it on my post from the other day. It is awesome if we can reuse any work out there even if its just reusing the theory.
There are a few things in there I don't fully agree with though so maybe they still need to be open ended discussions within the Hive network. For instance, I don't think witnesses (or whatever name we give those running the Atomic Plugins) should get a fee based on number of transfer transactions they sign. This could easily be manipulated with a flood of low value transfers executed when a particular witness is scheduled to sign.
Other than that, the specification you linked pretty much seems to cover a lot of what I envision for swaps on Hive. Mainly thru the use of optional plugins ran by witness users that do not maintain state, but only facilitate transfers.
Thanks @fbslo
This is a very good point.
We are not only considering the number of transactions. We are looking into other parameters like uptime via a "statistics object". The idea is to observe the behavior and extend the parameters - we are running an extended public TESTNET to iron out this.
Further we are limiting/capping the daily rewards so even if someone decides to attack, the transaction fee on Etherium or Bitcoin networks will prevent such an attack. The daily reward limits are changeable and the committee members can do so.
Suggestions welcome. If there are new ideas we can adapt them.
hey , if @someguy123 would get swap.hive on eos liek he had eos steemp, we can have https://alcor.exchange and telos.alcor.exchange list HIVE EOS and HIVE TLOS and we can also use https://transledger.io for ETH STEEM AND HIVE COME talk to Didier PH martin
we have LIQUIDITY POOLS ON ALCOR :)