bisq-network / bisq-network/events
Keybase meeting Thursday, April 22nd 21h00 UTC
- Dominant language
- No language data
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
[Previous meeting discussion](https://github.com/bisq-network/bisq/discussions/5378)
## Topics for the next meeting:
With @sqqrm working on a [new mode for trading involving a single transaction](https://github.com/bisq-network/proposals/issues/279) it makes sense to discuss some of the current problems with BSQ, it's privacy and the model we use for receiving trading fees in BTC and later redistribute it.
### A. BSQ privacy
[Video summary](https://arxiv.org/abs/2007.07048)
[Paper](https://www.youtube.com/watch?v=VRr-aWQpAWA)
**Summary** - BSQ inherits bitcoins bad privacy and adds to it. The constructions allowed are very limited and it's trivial to track down ownership. Plus the implementation itself distinguishes between different types of BSQ transactions to further break down fungibility.
### B. Better way to gather the trading fees and get rid of the Burning Man role
Bisq generates revenue by mainly charging fees for traders to make and take offers. A great part of these fees are still paid in BTC which leads to an undesirable entity having custody of them and the creation of lots of small amount UTXOs that become later [very expensive to spend](https://github.com/bisq-network/roles/issues/80#issuecomment-767497176).
Related proposals
[#304 - Make burning man a tradebot and add BSQ auction market ](https://github.com/bisq-network/proposals/issues/304)
[#316 - Distribute trade fee in BTC to DAO stakeholders by using locked up BSQ](https://github.com/bisq-network/proposals/issues/316)
[#317 - Distribute trade fee in BTC by using proof of burn](https://github.com/bisq-network/proposals/issues/317)
[Replace Burning Man with Burning Woman ](https://github.com/bisq-network/bisq/discussions/5418)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the previous meeting discussion, then review the linked BSQ privacy summary and paper and the related proposals about trading-fee distribution. The issue provides an agenda for a Keybase meeting rather than naming files, tests, or a code change; done is not defined beyond discussing these topics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- blockchain
- Domain
- blockchain
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100