Bisq DAO Cycle 12

The figures on this page are compiled from data files generated by the Bisq software. You can verify everything yourself by running these scripts on GitHub.

Cycle Started27 Mar 2020 / Block 623227

Cycle Ended27 Apr 2020 / Block 627906

Supply Change+ 19,529

Governance29 of 35 proposals accepted

Network Funds Transfers

BSQ Amount # of transactions
 Proof-of-burn¹ 153,400 4
 Trading fees² 10,135 2,386
 Compensation request fees 56 28
 Blind vote fees 46 23
 Asset listing fees 31 1
 Proposal fees 10 5
 Reimbursement request fees 4 2
Total Burn 163,682 2,615
 Compensation³ 182,735
 Reimbursements⁴ 476
Total Issuance 183,211
Net BSQ Supply Change⁵ +19,529

¹ Proof-of-burn includes trading fees paid in BTC and disputed BTC deposits for trades that went to arbitration (see docs for more details). Funds may be accrued and burned in different cycles, so proof-of-burn figures do not map directly to activity in their cycles.

² BSQ trading fees only. BTC trading fees are included in proof-of-burn.

³ See more details on GitHub.

⁴ Over time, the net impact of reimbursement issuances on BSQ supply is close to zero, as corresponding amounts of BTC are burned through proof-of-burn (see docs for more details).

⁵ Decreases in BSQ supply are good.


Parameter change proposal for REIMBURSEMENT_MAX_AMOUNT


This parameter change increased the maximum reimbursement amount from 10,000 to 20,000.

The goal is to increase this parameter to 100,000 over the next 3 cycles (it cannot be increased to 100,000 at once because the maximum single change allowed for this parameters is 200%).

Before Cycle 12, the upper limit for a compensation request was 100,000 BSQ while the upper limit for a reimbursement request was only 10,000 BSQ. As a result, because the arbitrator’s reimbursement requests would often be rather large, they had to make compensation requests instead of reimbursement requests.

Generic proposal


This proposal specified a framework for paying back the 6 victims from the April security incident. Funds will be paid back as quickly as possible from BTC trading fees. A filter-based mechanism to distribute repayments is currently under review, and a basic reporting mechanism to track payments has also been devised.

Notably, this proposal did not specify whether the total repayment would be the USD value of the funds at the time they were lost, or if the total would be the BTC total of the funds lost. This point remains to be addressed in a separate proposal to be submitted for consideration in a subsequent cycle.

Bonded role proposal for GITHUB_ADMIN


Bonded role proposal for DOMAIN_NAME_HOLDER


Bonded role proposal for DNS_ADMIN


< See more DAO data on the Dashboard