Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BTC donation address owner ("Burningman") #80

Open
ManfredKarrer opened this issue Mar 18, 2019 · 200 comments
Open

BTC donation address owner ("Burningman") #80

ManfredKarrer opened this issue Mar 18, 2019 · 200 comments
Assignees

Comments

@ManfredKarrer
Copy link
Member

@ManfredKarrer ManfredKarrer commented Mar 18, 2019

Docs: https://bisq.wiki/Donation_Address_Owner
Team: @bisq-network/donation-address-owners

@wiz
Copy link
Member

@wiz wiz commented Oct 18, 2019

@burning2019 can you please make your monthly report? also, I checked the current DAO parameter for recipient BTC address 3EtUWqsGThPtjwUczw27YCo6EWvQdaPUyp and it seems there are no transactions there?? https://blockstream.info/address/3EtUWqsGThPtjwUczw27YCo6EWvQdaPUyp

@ripcurlx
Copy link
Member

@ripcurlx ripcurlx commented Oct 21, 2019

@burning2019 can you please make your monthly report? also, I checked the current DAO parameter for recipient BTC address 3EtUWqsGThPtjwUczw27YCo6EWvQdaPUyp and it seems there are no transactions there?? https://blockstream.info/address/3EtUWqsGThPtjwUczw27YCo6EWvQdaPUyp

This will be relevant when the new trade protocol is live. Until then there won't be any transactions.

@gordonel
Copy link

@gordonel gordonel commented Nov 1, 2019

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

@wiz
Copy link
Member

@wiz wiz commented Nov 1, 2019

@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.

@gordonel
Copy link

@gordonel gordonel commented Nov 1, 2019

@wiz
Copy link
Member

@wiz wiz commented Nov 1, 2019

Bisq doesn't hold any user funds. They're always stored in your own wallet, on your own keys, on your own hardware.

@gordonel
Copy link

@gordonel gordonel commented Nov 1, 2019

I know that, @wiz. I'm an oldie (more than a year) on Bisq. Asking because this thread really got me thinking:
https://bisq.community/t/bisq-donation-address-huge-risk/8618/9

@wiz
Copy link
Member

@wiz wiz commented Nov 1, 2019

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

@burning2019
Copy link

@burning2019 burning2019 commented Dec 4, 2019

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
in transaction: bf863cef33fb1cef44c430b9b7c685bf59545a4e02aacff5415fbeaa9969f0bb

Burning.3 I burnt 34950 BSQ in a transaction fe115185937... having preimage qqrr giving the hash in the OP_RETURN
I also burnt 31230 BSQ in transaction dadc281a772... having preimage pobuk giving the hash in the OP_RETURN.

The BTC were sent from the donation address to 14HiewybGjEWVatSm1WPzdpmxyJq4QJRJQ in four installments:

-2.25826040 | b5628ef69f31722ed818ad482380bf87c40a174123d62811d624a29ad5c763e4
-0.01011660 | 27b52e38de262bf3ae60c95551da1ed8175ed5d0b44c151f534724b4a25a24b7
-2.15934260 | f7c76df1f041b5b66840538fec634d126746a2baaec815159797ffc2a9ed119d
-0.50648780 | 761cd370582e56f3fc3192480c78c2d66d7ac73a6758e7136132362ea35d751f

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
which is the hash of the preimage: 13768

The BTC were sent from the donation address to 14HiewybGjEWVatSm1WPzdpmxyJq4QJRJQ in two installments:

-0.57872371 | dae43fd564683bf68da4d4a18a9f2d5842365be6b739f8e7d8af2a4df5cbcee2
-2.00000509 | 9fcd6d22f3a4b48efb5f847d689aa88850fe008bc3f50a3af717db027703f5ce

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:

9d17826e62a74aa926732274e50d1714b624275625ea075e482be3e0f3c05c28
674c0eae8f49721e20d80c521aa16b2accc57118243bd925df5ec9fcec13a085
46067ce5b158d62cc52dcbb1c11372ef8966ee50dc3b7c1b974c5abeeb3ca2b2
5e710ec30fc5b0d189cfd814ef724e3de043bfa6bd0b93f59ff66ceb06d548cf
90c6ae5d96f33a0c2c9d4910ea28b6f8673f7e78c5cce365102547bc81d69334

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 burnt amount can be seen in the Bisq application.

The OP_RETURN contains the number 694aa8a44cec8206a0e49f191c875d1279bf2b8f
which is the hash of the preimage: Burning.1
Only I could know the preimage.

The BTC were sent from the donation address to 14HiewybGjEWVatSm1WPzdpmxyJq4QJRJQ in several instalments (due to technical issues) as follows:

-0.00876779 | 6871ab282994e1b39906e491693b4fe568da1e3c25d20a15643202be7d4e4a2e
-0.01004809 | fbb6025dc9867d33d2c65ede8779f8270bba0f314daa8831135c98d1be3fc743
-0.01092012 | 012773cbe33da53fed484ae67c505627cb881e25bd1286a70179c0467fb4a55d
-0.01002642 | 4e74d201fb78840114a1b91f6a395f0bd67b266ac6fb84b52662917573ec8754
-0.01093398 | b0f92cac67bc8a3f48f9f320e54c6575a3610ea1af2bf6ee82d0a555ba93b217
-0.02080280 | 782a487fba40df1c10564b56729ba4f2a8695103ad4f708db6ad32a5df16b91d
-0.05000000 | f779431bf378afa5620cd1e93a47acbfb1d6c36b0f5910b4e6c5e2ef0e007aaf
-0.30216574 | 19362cbcc7543ead594fae52e576085fc6958e14e94e9bd759fa1e1cc4c73124
-0.40000427 | b59604541295152cdc23633499a35a5af13ddb2669f822d8ed17ae142c613001
-0.40000427 | 45a429c11890c1ffd0b6d36d528b0d6c5cd452cd15b87dbba6e6af57d6c52b9c
-0.40000427 | 388b431d681250b5129e761bca0432b2c20e682b45cb31d73c31b84e0f96fb4e
-0.40000427 | 4ba08a81d1ff0718219a2ecaa42fb8aaf4cc5797f4ba6fa2ee85b53da33a2543
-0.40000427 | 487bec212d8948f045675bca30921aacb501ac02ffb434a6671153389b2b715b
-0.40102720 | 1d434183dff441ee4b06c5e34a4c2bd0470d7016a65a3b0376a563cc3fe73e60
-0.50011900 | 7cd9e34bab8a32f9853ba06107620a0dc5fa3969e99ae32fd0d4a7a3ab852b5c
-0.50000000 | b7fcc355bb3d1c0453b884c664932d0f150c799612cd01ea12f9d34178e4c021
-0.01000860 | cf4fcd917cfa9a7a2ade0b8c52ee93465eab3a03acc71d80ad3c6ef9446260cc

where the first column is the amount of BTC and the second column is the transaction ID.
This were subsequently used to buy BSQ on the market. 0.26195067 BTC remains to be used to buy BSQ in my Bisq application out of 3.82607221 BTC received.

@ghost
Copy link

@ghost ghost commented Dec 5, 2019

@burning2019 wrote :

The OP_RETURN contains the number 694aa8a44cec8206a0e49f191c875d1279bf2b8f
which is the hash of the preimage: Burning.1

Hello,
Could you please give more details about how you obtain this hash ?
What exact command(s) did you use in the CLI ?
Thanks

@wiz
Copy link
Member

@wiz wiz commented Dec 6, 2019

@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?

@devinbileck
Copy link
Member

@devinbileck devinbileck commented Dec 6, 2019

@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

To actually verify, a signature is needed.

@ghost
Copy link

@ghost ghost commented Dec 7, 2019

Thanks @wiz and @devinbileck ,
My Bisq appli was unable to connect yesterday for the whole morning, so I couldn't do anything.
I'll retry.

@wiz
Copy link
Member

@wiz wiz commented Dec 7, 2019

To actually verify, a signature is needed.

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

@wiz
Copy link
Member

@wiz wiz commented Dec 7, 2019

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.

Screen Shot 2019-12-07 at 18 14 01

@ghost
Copy link

@ghost ghost commented Dec 7, 2019

I tried to verify the hash from my CLI.
I tried several shaxxxsum functions, but none returns the showed hash.
Does somebody know which hash function is used ?
(Bisq appli is running today, issues must have been related to seed nodes yesterday morning).

@chimp1984
Copy link

@chimp1984 chimp1984 commented Dec 9, 2019

I tried to verify the hash from my CLI.
I tried several shaxxxsum functions, but none returns the showed hash.
Does somebody know which hash function is used ?
(Bisq appli is running today, issues must have been related to seed nodes yesterday morning).

Sha256 + Ripemd160

@ripcurlx
Copy link
Member

@ripcurlx ripcurlx commented Dec 10, 2019

caf7410187735ac013a3fec0ae6566ee1c9dd2dcf974f0d92d75bb9d22feba6c

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)

@chimp1984
Copy link

@chimp1984 chimp1984 commented Dec 11, 2019

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....

@wiz
Copy link
Member

@wiz wiz commented Dec 13, 2019

@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

@burningman2
Copy link

@burningman2 burningman2 commented Dec 22, 2019

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.

See bisq-network/proposals#149

@burningman2
Copy link

@burningman2 burningman2 commented Dec 28, 2019

Report Dec. 28th 2019

Moved 0.12448339 BTC from cold storage to trade app with tx ID: 7ea3e8a13fe5ebb0b05635c71f5aa196a89a81b6d1b21053dca30322199cc3c8 (miner fee 0.00055521 BTC)
Bought 1235.96 BSQ with 0.11 BTC at price 0.000089 BSQ/BTC by taking best offer.
Remaining BTC balance for next trade event: 0.01490359 BTC

Burned 1220 BSQ with tx ID: 2f3e9059804107d3d9578badc92ff86ae4f857653c425638d3878339c7ad6ae1
Pre-image for burning: GZxyV4rgmXeUJrqkx
Hash: 9bf57db339274b1c6e7267a3b0112840e4dbc858
Signed tx ID 2f3e9059804107d3d9578badc92ff86ae4f857653c425638d3878339c7ad6ae1
Signature: HwdDqFAziMTyrl3wER8MN83ZPpW9/wFfZ/Ew5lVIu6z8O3WUJxRsFxfn5WPSnVFgRTIVdi0miaYr1vsLuUV2l6M=

Remaining BSQ balance: 15.96 BSQ (proof of burn requires a change output)

Next trade event Jan. 4th, 5th 2020.

Trade:
Screen Shot 2019-12-28 at 13 16 37

Transactions:
Screen Shot 2019-12-28 at 13 16 25

Burn BSQ:
Screen Shot 2019-12-28 at 13 16 14

BSQ transactions:
Screen Shot 2019-12-28 at 13 15 58

Sign tx id:
Screen Shot 2019-12-28 at 13 20 57

Signature verification:
Screen Shot 2019-12-28 at 13 21 10

@burningman2
Copy link

@burningman2 burningman2 commented Jan 4, 2020

Report Jan. 5th 2020

Moved 0.26472266 BTC from cold storage to trade app with tx ID: b7769725de388c4ace331920a123eb2448517d9a5aebe6cb350f7f58a347949c (miner fee 0.00061041 BTC)

  • Bought 3229.97 BSQ with 0.25 BTC at price 0.0000774 BSQ/BTC by taking best offer (could not take instant offer as I was not sure if I can complete trade in 1 hour, other better offer had too high amount).
  • Bought 137.67 BSQ with 0.011 BTC at price 0.0000799 BSQ/BTC by taking best offer (other offers with better prices had too high amounts).

Remaining BTC balance for next trade event: 0.02104337 BTC

Burned 3350 BSQ with tx ID: e69ff42cf6f360ba85338782adef7b69f5201efecc7a52c6c88f6e9793a7d907
Pre-image for burning: DfRr9CHXvL4hMp
Hash: 36d75054c56f2ebdf7aa8df1eaaf72c1ff06f928
Signed tx ID e69ff42cf6f360ba85338782adef7b69f5201efecc7a52c6c88f6e9793a7d907
Signature: IJTvra8B9pQr1ejybZL6OLXMUrF4ZkpndpNi2GBpTjx2Knb5FC+Uba/zh0xQgRPUIaLafpM00UGKb41y3IkfR6k=

Remaining BSQ balance: 25.77 BSQ (proof of burn requires a change output)

Next trade event Jan. 11th, 12th 2020.

Trade:
Screen Shot 2020-01-05 at 00 41 14

Transactions:
Screen Shot 2020-01-05 at 00 41 39

Burn BSQ:
Screen Shot 2020-01-05 at 00 50 47

BSQ transactions:
Screen Shot 2020-01-05 at 00 46 45

Sign tx id:
Screen Shot 2020-01-05 at 00 47 32

Signature verification:
Screen Shot 2020-01-05 at 00 47 54

@burningman3
Copy link

@burningman3 burningman3 commented May 15, 2021

I will buy BSQ Sunday, May 16, between 15:00 CET and 17:00 CET if fees are low enough.

@burningman3
Copy link

@burningman3 burningman3 commented May 22, 2021

I will buy BSQ Sunday, May 23, between 15:00 CET and 17:00 CET if fees are low enough.

@burningman3
Copy link

@burningman3 burningman3 commented May 29, 2021

BSQ Burning 2021-05-23

BSQ burnt: 77000
preimage: NIdbfjPc
hash: 766647e8f09b51aef22dbd9eb6f991e530489dba
message: p7OZOyylhHL7LkqyLTi37mDjb3Yuv-d7
signature: IDgGJFw06uRQIeSv1WFK88tX2T4JIibKp4I+zPcKbkY/QRUwFlkv5/QuRGvkFW7EsY5zGlCL1bSsBquC9k/g/bE=

@burningman3
Copy link

@burningman3 burningman3 commented May 29, 2021

I will buy BSQ Sunday, May 30, between 15:00 CET and 17:00 CET.

@burningman3
Copy link

@burningman3 burningman3 commented Jun 5, 2021

I will buy BSQ Sunday, Jun 6, between 15:00 CET and 17:00 CET.

@burningman3
Copy link

@burningman3 burningman3 commented Jun 12, 2021

I will buy BSQ Sunday, Jun 13, between 15:00 CET and 17:00 CET.

@burningman3
Copy link

@burningman3 burningman3 commented Jun 19, 2021

I won't buy BSQ this week.

@burningman3
Copy link

@burningman3 burningman3 commented Jun 26, 2021

I will buy BSQ Sunday, Jun 27, between 15:00 CET and 17:00 CET.

@burningman3
Copy link

@burningman3 burningman3 commented Jul 3, 2021

I will buy BSQ Sunday, Jul 04, between 15:00 CET and 17:00 CET.

@burningman3
Copy link

@burningman3 burningman3 commented Jul 10, 2021

I will buy BSQ Sunday, Jul 11, between 15:00 CET and 17:00 CET.

@burningman3
Copy link

@burningman3 burningman3 commented Jul 11, 2021

BSQ Burning 2021-07-11

BSQ burnt: 41000
preimage: v3RO9fge
hash: 599dc7ffe960a612fda8110cbe6219681502d70f
message: vL01fYUaDAd1esvyBxRGcZ7qe0rDeJzQ
signature: H+DuhCOgyuI9YLA2jCIjmjEbjHurMS8LvmbGwqIogv9EGnJiPulZ+2m8/Nv4FvWsQVEVjNj+OfsRPNJtQVUZgnc=

@burningman3
Copy link

@burningman3 burningman3 commented Jul 17, 2021

I won't buy BSQ this week.

@burningman3
Copy link

@burningman3 burningman3 commented Jul 20, 2021

Report Jul 20 2021 - Cycle 26

Trades since last report. The first new trade is highlighted.
trades-20210720

Trade history in csv format
tradeHistory.txt

Burning

As noted in separate posts

@burningman3
Copy link

@burningman3 burningman3 commented Jul 24, 2021

I will buy BSQ Sunday, Jul 25, between 15:00 CET and 17:00 CET.

@burningman3
Copy link

@burningman3 burningman3 commented Jul 31, 2021

I will buy BSQ Sunday, Aug 1, between 15:00 CET and 17:00 CET.

@burningman3
Copy link

@burningman3 burningman3 commented Aug 2, 2021

BSQ Burning 2021-08-02

BSQ burnt: 59000
preimage: 6esBS8ur
hash: 3680e1a58f8fb6b9a74b18a65a73f4a64e2b7e84
message: eFCbGIu9dUMCa7VoG4iKu9cXe22m6pK_
signature: IEO/iPEGt7DSZndry0B3pBds9HaaQnnTwKAYcYXW2ERGcm9uMGehKysTv5EvkPHGdRIrnDxrW+yyDy/2SPpW4h8=

@burningman3
Copy link

@burningman3 burningman3 commented Aug 7, 2021

I will buy BSQ Sunday, Aug 8, between 15:00 CET and 17:00 CET.

@burningman3
Copy link

@burningman3 burningman3 commented Aug 14, 2021

I will buy BSQ Sunday, Aug 15, between 15:00 CET and 17:00 CET.

@burningman3
Copy link

@burningman3 burningman3 commented Aug 21, 2021

I will buy BSQ Sunday, Aug 22, between 16:00 CET and 18:00 CET.

@burningman3
Copy link

@burningman3 burningman3 commented Aug 21, 2021

Report Aug 21 2021 - Cycle 27

Trades since last report. The first new trade is highlighted.
trades-20210821

Trade history in csv format
tradeHistory.txt

Burning

As noted in separate posts

@burningman3
Copy link

@burningman3 burningman3 commented Aug 28, 2021

I will buy BSQ Sunday, Aug 29, between 15:00 CET and 17:00 CET.

@burningman3
Copy link

@burningman3 burningman3 commented Sep 4, 2021

I will buy BSQ Sunday, Sep 5, between 15:00 CET and 17:00 CET.

@burningman3
Copy link

@burningman3 burningman3 commented Sep 11, 2021

I will buy BSQ Sunday, Sep 12, between 15:00 CET and 18:00 CET.

@burningman3
Copy link

@burningman3 burningman3 commented Sep 18, 2021

I will buy BSQ Sunday, Sep 19, between 15:00 CET and 18:00 CET.

@burningman3
Copy link

@burningman3 burningman3 commented Sep 19, 2021

Report Sep 19 2021 - Cycle 28

Trades since last report. The first new trade is highlighted.
trades-20210919

Trade history in csv format
tradeHistory.txt

BSQ Burning 2021-09-19

BSQ burnt: 37000
preimage: rRIqGLpk
hash: aebf67a9fe80326e956dee5b373b438df58c95f6
message: oFAVGZCITFtW1OJBk93uawP8KLpigUfu
signature: IFh7eOug8VcXfQEl5T/g/EH/3s8BU9CfK8mpVToXYQl7FC1xfwrVdIgLi9HxI0g4CoLDp+I4djUgU18N4QqA1dg=

@burningman3
Copy link

@burningman3 burningman3 commented Sep 25, 2021

I will buy BSQ Sunday, Sep 26, between 15:00 CET and 18:00 CET.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet