BTC donation address owner ("Burningman") #80
Comments
|
@burning2019 can you please make your monthly report? also, I checked the current DAO parameter for recipient BTC address |
This will be relevant when the new trade protocol is live. Until then there won't be any transactions. |
|
IMHO, it makes much more sense to make a multisig address and have multiple key owners: two main owners, on or a few keys for arbitrators and for trusted developers. We don't want the address owner getting away with funds or worse, scamming people into failing trades |
|
@gordonel Security for trusted roles in the Bisq DAO is actually pretty well thought out. Of course, the donation address keyholder is a very trusted role, right up there with domain name owner and github admin, but this is why it requires posting such a large bond and requires the accountability with monthly reports. I simply made the mistake thinking the role was already active, when it actually just started a few days ago (check the address on block explorer). If the donation address owner does anything to betray the trust, the DAO can vote to revoke the bond and change the donation address parameter easily. In other words, it would be painful but Bisq is prepared to survive such an attack. |
|
Can this mechanism and DAO guarantee the user funds will be reimbursed if needed? Do we have protocols in place that would detect malicious behaviour before it's too late?
…-------- Original Message --------
On 1 Nov 2019, 15:26, wiz wrote:
***@***.***(https://github.com/gordonel) Security for trusted roles in the Bisq DAO is actually pretty well thought out. Of course, the donation address keyholder is a very trusted role, right up there with domain name owner and github admin, but this is why it requires posting such a large bond and requires the accountability with monthly reports. I simply made the mistake thinking the role was already active, when it actually just started a few days ago (check the address on block explorer).
If the donation address owner does anything to betray the trust, the DAO can vote to revoke the bond and change the donation address parameter easily. In other words, it would be painful but Bisq is prepared to survive such an attack.
—
You are receiving this because you were mentioned.
Reply to this email directly, [view it on GitHub](#80?email_source=notifications&email_token=AKYUTQXZ4SEATI6N5Z6RR4DQRQVARA5CNFSM4G7LBGWKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEC25GMA#issuecomment-548786992), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AKYUTQTNPNYDHE2A3RGO3NLQRQVARANCNFSM4G7LBGWA).
|
|
Bisq doesn't hold any user funds. They're always stored in your own wallet, on your own keys, on your own hardware. |
|
I know that, @wiz. I'm an oldie (more than a year) on Bisq. Asking because this thread really got me thinking: |
|
Well then what are you talking about? This address is only for trading fee revenue which is less than 50K BSQ worth of BTC each cycle |
|
After ending my role as donation address holder I continue to get BTC into the address. Today I send the current balance, 0.19206080 BTC, to burningman2 at address: 3A8Zc1XioE2HRzYfbb5P8iemCS72M6vRJV Burning.3 I burnt 34950 BSQ in a transaction fe115185937... having preimage qqrr giving the hash in the OP_RETURN The BTC were sent from the donation address to 14HiewybGjEWVatSm1WPzdpmxyJq4QJRJQ in four installments:
I have now 0.11503848 BTC in my wallet and 21.21 BSQ. The donation address contains 0.14486820 BTC which will be sent to 14HiewybGjEWVatSm1WPzdpmxyJq4QJRJQ where I will later buy BSQ and burn. I will retire from this role which has been taken over by a different person as soon as I have burnt the rest of the funds. Burning.2 I burnt 30 000 BSQ in transaction: 2452902d1299f36394ad3011a9b8a51e888d594ed3095bc55577091d1ca45ec8 The OP_RETURN contains the number b4f7a135641683aed2312fd2d65d1ae6df750466 The BTC were sent from the donation address to 14HiewybGjEWVatSm1WPzdpmxyJq4QJRJQ in two installments:
where the first column is the amount of BTC and the second column is the transaction ID. I took the best offers unless they were very small and insignificant in the following transactions:
giving an estimated average price of 0.000096 BTC for one BSQ. I now have 92.98 BSQ and 0.14078686 BTC left in my Bisq application. Burning.1: I burnt 36000 BSQ in transaction: caf7410187735ac013a3fec0ae6566ee1c9dd2dcf974f0d92d75bb9d22feba6c The OP_RETURN contains the number 694aa8a44cec8206a0e49f191c875d1279bf2b8f The BTC were sent from the donation address to 14HiewybGjEWVatSm1WPzdpmxyJq4QJRJQ in several instalments (due to technical issues) as follows: -0.00876779 | 6871ab282994e1b39906e491693b4fe568da1e3c25d20a15643202be7d4e4a2e where the first column is the amount of BTC and the second column is the transaction ID. |
|
@burning2019 wrote :
Hello, |
|
@HarryMacfinned go to DAO -> Proof of Burn and you will see the TX, click "verify" and enter the string as the preimage text to verify @burning2019 in the future maybe it's best to also add the average fill rate, for example this cycle was 3.56412154 BTC to buy 36000 BSQ = average rate of 9900 sats per BSQ! why so high? |
To actually verify, a signature is needed. |
|
Thanks @wiz and @devinbileck , |
The fact that the TX appears in the box means it has already been verified by your Bisq app. The burning man could sign additional messages with this key, but instead he disclosed the pre-image so he proved it was him. Nobody else would randomly burn 36K BSQ with a message of "Burning.1" lol |
|
FYI this is how you verify a Proof of Burn. When the Burning Man disclosed the pre-image string, you can type the string in and get the hash. The hash is what appears in the Proof of Burn box, so it matches and verifies. The "verify" button is if the burning man wants to sign additional messages with the same key, but this functionality is not necessary to verify the burn.
|
|
I tried to verify the hash from my CLI. |
Sha256 + Ripemd160 |
Do we have a problem with our explorer right now? When visiting https://explorer.bisq.network/tx.html?tx=caf7410187735ac013a3fec0ae6566ee1c9dd2dcf974f0d92d75bb9d22feba6c to check the burn transaction it doesn't show anything right now. Looking it up in a regular explorer does work (e.g. https://blockstream.info/tx/caf7410187735ac013a3fec0ae6566ee1c9dd2dcf974f0d92d75bb9d22feba6c) |
|
For me it works: https://explorer.bisq.network/tx.html?tx=caf7410187735ac013a3fec0ae6566ee1c9dd2dcf974f0d92d75bb9d22feba6c But yes explorer is pretty unstable and often delayed. Needs some dev love.... |
|
@chimp1984 since we added Bitcoin block explorer into the mempool-space project, it would be pretty easy to tweak that to display BSQ transactions as well, I would just need to modify the Bisq node to insert the BSQ transactions into an indexed DB of some kind |
|
My request to take over the role was accepted by voting. I will start Dec 28th 2019 with first trades and will do it each weekend. |
Report Dec. 28th 2019Moved 0.12448339 BTC from cold storage to trade app with tx ID: Burned 1220 BSQ with tx ID: Remaining BSQ balance: 15.96 BSQ (proof of burn requires a change output) Next trade event Jan. 4th, 5th 2020. Trade: Transactions: Burn BSQ: BSQ transactions: Sign tx id: Signature verification: |
Report Jan. 5th 2020Moved 0.26472266 BTC from cold storage to trade app with tx ID:
Remaining BTC balance for next trade event: 0.02104337 BTC Burned 3350 BSQ with tx ID: Remaining BSQ balance: 25.77 BSQ (proof of burn requires a change output) Next trade event Jan. 11th, 12th 2020. Trade: Transactions: Burn BSQ: BSQ transactions: Sign tx id: Signature verification: |
BSQ Burning 2022-11-13From feesBSQ burnt: 14278 |
|
Another DPT sent to old burningman address 1BVxNn3T12veSK6DgqwU4Hdn7QHcDDRag7 --> a943c7285ad0e4a281255d61125197982bf443019fac7bd7480a5928fa0fad0f @burningman2 Send the funds to 34VLFgtFKAtwTdZ5rengTT2g2zC99sWQLC |
|
Next trade event: Sun Nov 20, between 15:00 - 18:00 CET. |
BSQ Burning 2022-11-21From arbitratorBSQ burnt: 40000 From feesBSQ burnt: 22750 |
|
Next trade event: Sun Nov 27, between 15:00 - 18:00 CET. |
BSQ Burning 2022-11-27From feesBSQ burnt: 14600 |
Report Dec 12 - Cycle 42Trades since last report. The first new trade is highlighted. Trade history in csv format BSQ Burning 2022-12-04From feesBSQ burnt: 13750 |
|
Next trade event: Tue Dec 13, between 15:00 - 18:00 CET. |
|
Next trade event: Sun Dec 18, between 15:00 - 18:00 CET. |
BSQ Burning 2022-12-18From feesBSQ burnt: 8820 From refundsBSQ burnt: 66000 |
|
Next trade event: Mon Jan 2, between 15:00 - 18:00 CET. |
BSQ Burning 2023-01-02From feesBSQ burnt: 19449 |
|
Next trade event: Sun Jan 8, between 15:00 - 18:00 CET. |
Report Jan 8 2023 - Cycle 43Trades since last report. The first new trade is highlighted. Trade history in csv format |
|
Next trade event: Sun Jan 15, between 15:00 - 18:00 CET. |
Report Feb 12 2023 - Cycle 44Trades since last report. The first new trade is highlighted. Trade history in csv format BSQ Burning 2023-02-12From arbitratorBSQ burnt: 14900 |
BSQ Burning 2023-02-26From arbitratorBSQ burnt: 24000 |
Report Mar 12 2023 - Cycle 45This role is no longer needed after distributing it to the DAO contributors. I propose to unlock my bond and stop claiming compensation once the bond is unlocked. Until then I would sell all remaining BTC. Trades since last report. The first new trade is highlighted. Trade history in csv format BSQ Burning 2023-03-12From refundsBSQ burnt: 37691.9 |
|
You might still receive some DPT from users that are late for some reason or bugs, the address from burningman2 was still needed sometimes and even burningman1. |
|
Yes thanks @burningman3 for completing this role, hope you are able contribute to Bisq in other ways. Both addresses will likely receive payments for sometime: 38bZBj5peYS3Husdz7AH3gEUiUbYRD951t They are also included in the Burning Man Proof of Burn to pick up any slack if for any reason the burn target is not reached. Only 2 full cycles so far since the protocol changes so I think it is likely at some point we will see DPT and trade fee payments to this address. There is still a required role for a legacy burning man in the DAO even if means they receive less BTC than previous and maybe they burn less. |
Report Apr 09 2023 - Cycle 46This will be my last report. There are almost no more transactions received in my wallet now, any further funds I receive will be used to burn BSQ as previously but I won't post more reports and I will revoke my bond. Trades since last report. The first new trade is highlighted. Trade history in csv format BSQ Burning 2023-04-09From arbitratorBSQ burnt: 33300 |
|
Thank you for your work |
BSQ Burning 2024-02-21From refundsBSQ burnt: 15735.72 |
and others
Docs: https://bisq.wiki/Donation_Address_Owner
Team: @bisq-network/donation-address-owners
The text was updated successfully, but these errors were encountered: