[bisq-network/proposals] BSQ/DAO oracle (#33)

chirhonul notifications at github.com
Wed Jul 25 14:05:26 UTC 2018


I like designing the DAO to allow for support of this feature eventually, as long as that future-flexibility does not increase current complexity too much. The idea of different DAOs being able to "talk to each other" by a generic ask-Bisq-Oracle feature by a user running full nodes for both DAOs does seem like it could be a very powerful idea, even if we can't completely visualize how such features would be used in the boundless future.

Re:
```
There is a hard coded enumeration of such parameters and adding new ones is a hard fork.
All of those parameters (beside the BTC trade fee) has direct effects on BSQ/DAO consensus.
So we are not very flexible with that approach.
```
I believe if we changed the logic to handle unknown / higher valued enum values for the DAO parameters by assuming our code does not understand them, we could be able to support them as a soft fork, if at least majority of BSQ stakeholders upgraded to a version that does understand the new parameters. In such a case maybe we also want to hint to the user that they could be running an old release and can consider upgrading. (Protobuf allows this pseudo-forward compatibility already for new / higher-id fields, which are ignored by clients running old releases without knowledge of those fields.) 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/proposals/issues/33#issuecomment-407765831
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20180725/cf6367dd/attachment.html>


More information about the bisq-github mailing list