[bisq-network/bisq] Add ISSUANCE_LIMIT param and check for max issuance per cycle (#2584)

[Manfred Karrer]

We limit the possible max. issuance (including reimbursements) to the
valued defined in the ISSUANCE_LIMIT param.
In case we exceed that limit the whole cycle becomes invalid.

The main reason for that feature is limitation of max.
damage in case that an attacker manages to create unjustified issuance.

For valid cases we consider such a case as social consensus problem as
the majority of voters should be aware of that limit before they
accept such a high issuance. If known in advance that an extraordinary
high issuance is expected the DAO parameter can be changed.
You can view, comment on, or merge this pull request online at:

  https://github.com/bisq-network/bisq/pull/2584

-- Commit Summary --

  * Add ISSUANCE_LIMIT param and check for max issuance per cycle

-- File Changes --

    M core/src/main/java/bisq/core/dao/governance/param/Param.java (1)
    M core/src/main/java/bisq/core/dao/governance/voteresult/VoteResultService.java (27)
    M core/src/main/resources/i18n/displayStrings.properties (2)

-- Patch Links --

https://github.com/bisq-network/bisq/pull/2584.patch
https://github.com/bisq-network/bisq/pull/2584.diff

-- 
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/bisq/pull/2584
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20190325/435c118a/attachment.html>