Bisq Wiki - User contributions [en]

Bitcointalk Moderator

2020-04-28T15:21:42Z

HunterNyan: Role Superseeded

#REDIRECT [[Community_Manager]]

'''<big>This Role has been superseded by the [[Community_Manager]] as stated in [https://github.com/bisq-network/roles/issues/37#issuecomment-620416643 Bitcointalk Moderator Role Issue] and [https://github.com/bisq-network/roles/issues/95 Community Manager Role]</big>
'''

This article documents the ''Bitcointalk Moderator'' [[role]].

<br><br><br>
__TOC__

== Issue ==

* [https://github.com/bisq-network/roles/issues/37 Bitcointalk Moderator #37]
== Team ==

===github===
* [https://github.com/orgs/bisq-network/teams/bitcointalk-moderators @bisq-network/bitcointalk-moderators]
===wiki===

== Duties ==

* This role is about keeping the [https://bitcointalk.org/index.php?topic=4509053.0 Bisq thread] on the Bitcointalk forum up-to-date.

== Rights ==


== Bonding ==

N/A

[[Category:Roles]]

Category:Operator

2020-04-27T18:34:48Z

HunterNyan: explain Operator Role Type

=Operator=
An Operator is a contributor responsible for keeping a given resource running and functioning normally.

Examples: [[Forum Operator]],[[Pricenode Operator]].

==Operator Duties==
* Keep the given resource online and functioning normally.
* Keep the resource up to date with latest version.
* Maintain backups as appropriate.
* Report on any incidents.

==Operator Rights==
* Administrative access to hosting infrastructure.
* Ownership of any domain name used.

[[Category:Roles]]

Category:Maintainer

2020-04-27T18:33:28Z

HunterNyan: Describe "Maintainer" Role Types

=Maintainer=
A Maintainer is a contributor responsible for enforcing process in a given GitHub repository.

Examples: [[Proposals Maintainer]], [[Compensation maintainer]].

==Maintainer Duties==
* Merging or closing pull requests after sufficient review.
* Tagging releases.
* Triaging incoming issues and keeping them organized over time.
** A Maintainer is not a Developer or a Reviewer
** Submitting and reviewing pull requests is something any contributor can do; neither are maintainer duties per se.
** This is particularly important from a [[Compensation]] perspective. If you are a maintainer, do NOT group your development and review activities together with your maintainer role in your compensation requests. Rather, account for them separately like any other contributor would.
** The goal is to have as many competent contributors developing and reviewing as possible, not to load everything on the maintainer. [https://rfc.unprotocols.org/spec:1/C4/#21-preliminaries C4] is the inspiration here, it’s worth (re-)reading.

==Maintainer Rights==
* Write access to the repository they are responsible for.

[[Category:Roles]]

Category:Roles

2020-04-27T18:26:22Z

HunterNyan: fluff

Anchor point with some categories for helping find roles.

See https://docs.bisq.network/roles.html

[[Category:Teams]]

Category:Teams

2020-04-27T18:23:22Z

HunterNyan: added fluff

Teams are just a management layer for a select group of Roles.

Contributors can have many roles and therefore many teams.

The Team will have a Leader who will be responsible to granting access to resources the contributor needs, as well as to add a layer of efficiency and trust into the decentralised project.

[[Category:DAO]]

Support Team Lead

2020-04-27T18:16:24Z

HunterNyan: removed team category

This article documents the ''Support Team Lead'' [[role]].

__TOC__

== Issue ==
* [https://github.com/bisq-network/roles/issues/102 Support Team Lead #102]

== Team ==
===github===
* [https://github.com/orgs/bisq-network/teams/team-leads Team Leads team]
* [https://github.com/orgs/bisq-network/teams/support Support Team]
===wiki===
* [[Support_Team|Support Team]]

== Duties ==

* Review Team's [[Compensation]] requests as per Process.

== Rights ==


== Bonding ==
N/A

[[Category:Roles]]
[[Category:Admin]]
[[Category:TeamsLeader]]

Category:Processes

2020-04-27T18:12:46Z

HunterNyan: Linked to Template

Please create Processes as per template in the style guide: [[Wiki_style_guidelines/Templates]]

[[Category:DAO]]

Support Team Lead

2020-04-27T18:11:06Z

HunterNyan: Added Duties

Compensation Maintainer

2020-04-27T18:09:04Z

HunterNyan: Fixed link

This article documents the ''Compensation Maintainer'' [[role]].

__TOC__

== Issue ==
* [https://github.com/bisq-network/roles/issues/102 Support Team Lead #102]

== Team ==
===github===
* [https://github.com/orgs/bisq-network/teams/compensation-maintainers Compensation Maintainer]
===wiki===
* [[Compensation_Maintainer|Compensation Maintainer]]

== Duties ==
* Lead the operation of the [[Compensation]] Process.

== Rights ==

* Repo Access: https://github.com/bisq-network/compensation/

== Bonding ==
N/A

[[Category:Roles]]
[[Category:Admin]]
[[Category:Maintainer]]

Compensation Maintainer

2020-04-27T18:08:46Z

HunterNyan: linked duties to process

This article documents the ''Compensation Maintainer'' [[role]].

__TOC__

== Issue ==
* [https://github.com/bisq-network/roles/issues/102 Support Team Lead #102]

== Team ==
===github===
* [https://github.com/orgs/bisq-network/teams/compensation-maintainers Compensation Maintainer]
===wiki===
* [[Compensation_Maintainer|Compensation Maintainer]]

== Duties ==
* Lead the operation of the [Compensation] Process.

== Rights ==

* Repo Access: https://github.com/bisq-network/compensation/

== Bonding ==
N/A

[[Category:Roles]]
[[Category:Admin]]
[[Category:Maintainer]]

Compensation

2020-04-27T18:06:14Z

HunterNyan: Updated to new template :/

'''Compensation'''  The process in which Contributors can be compensated for their work via the DAO.

__TOC__

=Introduction=

* To incentivize further development & operation of Bisq

=Infrastructure=

==GitHub==
* Write Permissions to issues for [https://github.com/bisq-network/compensation/issues compensation repository].

=Roles=

==[[Admin Team]]== 
===[[Compensation Maintainer]]=== 
* Managing the Compensation Requests

==[[BSQ Explorer Team]]==
==[[Dev Team]]==
==[[Growth Team]]==
==[[Ops Team]]==
==[[Support Team]]==
===All Contributors===
* Submit Compensation Requests
===All Team Leads===
* Approve / Review their Team's requests

=Process=
==Step 0==

=== [[Compensation Maintainer]] ===
==== Announce BSQ-USD exchange rate ====
Since proposal [https://github.com/bisq-network/compensation/issues/114 #114], compensation requests should use a 90-day average to calculate a value for BSQ and mitigate its volatility.
At the end of a Bisq DAO Cycle and beginning of a new one, The [[Compensation Maintainer]] should create a pinned issue with the title: <code>BSQ rate for Cycle X is Y.YY USD per 1 BSQ</code> and a screenshot of DAO Dashboard to announce the rates for the ongoing cycle.

==== Announce request submission deadline ====
To give time for team leads to discuss and review Compensation Requests, requests need to be <code>Ready for review</code> one week prior to the end of current cycle's proposal phase. [[File:Compensation_board.png|400px|right|thumb|Compensation board]]The date and reminders will be announced at [https://github.com/orgs/bisq-network/teams/dao/discussions/ @bisq-network/dao], the [https://github.com/orgs/bisq-network/projects/5 Compensation board] and [https://calendar.google.com/calendar/embed?src=adfiuiokq9jtac8t9keomc00b0%40group.calendar.google.com&ctz=Europe%2FMadrid Events Calendar]

==Step 1==


=== Contributor ===
==== Create your compensation request issue ====

If you wish to request compensation for the current [[Glossary#DAO Cycle|cycle]], you should [https://docs.bisq.network/compensation.html#submit-your-compensation-request create a compensation request issue] no later than '''one week prior''' to the end of the current cycle's proposal phase. This is in order to allow time for review by your [[Team Lead]]. Reminders about this deadline are sent every cycle to the [https://github.com/bisq-network/teams/dao @bisq-network/dao] team, so you should make sure you are watching discussions for that team.

WIP (Work in Progress) compensation requests may be submitted with a <code>[WIP]</code> prefix in the title, e.g. <code>[WIP] For Cycle 10</code>. Such WIP requests are assumed not to be ready for review until the WIP prefix is removed. This allows you a convenient way to incrementally add content to a compensation request throughout the course of a cycle without triggering a review prematurely. To indicate that a WIP compensation request is now ready for review, remove the <code>[WIP]</code> prefix from the compensation request issue and add a comment stating ''"This request is ready for review"''. Any compensation request submitted without a WIP prefix will be assumed to be ready for review.

=== Compensation Maintainer ===
==== Triage incoming requests ====

The [[Compensation Maintainer]] watches the [https://github.com/bisq-network/compensation/issues compensation repository] and proceeds to triage:

Incoming issues are classified as <code>Work in progress</code> if they have <code>[WIP]</code> at the beginning of the title or as <code>In Review</code> if they don't. Compensation Maintainer assigns 'In review' issues to the corresponding team leads after looking at the content of the request. When in doubt, Compensation Maintainer should ask in the issue which team leaders are appropriate for the issue.

The Compensation Maintainer should transition reviewed requests with DAO proposals transaction ID submitted to <code>Proposal Submitted</code> column.

Triage is controlled from the Compensation board, drag-and-dropping issues and using "add cards" to triage incoming issues, and directly from the issues, using the "projects" section in the right sidebar.

==Step 2==

=== Team Lead ===
==== Review team member requests ====

When a team lead is assigned to a compensation request issue, they should promptly review it with regard to whether the work meets the definition of delivered, and whether it fits within the team budget. The team lead should add feedback and comments as appropriate, and assign the contributor to the issue to indicate that they are expected to respond to the review.

When the review process is complete, i.e. all team lead feedback has been addressed, the team lead should add a comment asking the contributor to submit their proposal to DAO and to post the resulting TXID in a comment.

=== [[Stakeholder]] ===
==== Review contributor requests ====
Remember that just as stakeholders may vote on any DAO proposal, stakeholders may review any contributor's compensation request. To do so, simply add your review feedback in the form of a comment, and react to the compensation request issue with a thumbs-up, thumbs-down or confused face emoji as appropriate. Note that with the exception of team leads, there is no obligation to perform these reviews, and in general you should only review compensation requests that you are knowledgeable about.

=== Contributor ===
==== Incorporate review feedback for your request ====

When your team lead or other stakeholders review your compensation request, they will provide any feedback or requests for changes in the form of a comment on your request issue. Please respond to it promptly.
When there is no further feedback, your team lead will add a comment asking you to submit this compensation request as a DAO proposal. You may now Procedure to Step 3

==Step 3==
=== Contributor ===
==== Submit your request as a DAO proposal ====

Follow the instructions on how to [https://docs.bisq.network/compensation.html#file-your-compensation-request-in-the-dao file your compensation request as a DAO proposal]. When complete, add a comment to your proposal issue that includes the transaction ID of your proposal.

==Step 4==
=== Compensation Maintainer ===
==== Archive previous cycle requests at the end of the proposal phase ====

At the completion of the current cycle's proposal phase, the Compensation Maintainer should [https://help.github.com/en/github/managing-your-work-on-github/archiving-cards-on-a-project-board archive] all issues in the <code>Done</code> column from the previous phase.

The reason for waiting to archive these issues is so that contributors can easily see how many requests were made in the last phase, to quickly find their own prior request, and to to easily review which ones were accepted and rejected. We archive them at the end of the proposal phase in order to keep the board clean and make room for requests in the current phase to populate the <code>Done</code> column.

==== Close current cycle requests after the vote reveal phase ====
When the reveal vote phase is complete, the Compensation Maintainer should take the following steps:

# Label each compensation request issue as <code>was:accepted</code> or <code>was:rejected</code> according to the vote result
# Close the issue with a comment that reads "Closing as accepted" or "Closing as rejected".

Once closed, the issues will automatically transition to the <code>Done</code> column of the board where they remain for reference until they are archived at the end of the next cycle's proposal phase (as per the section above).

=Evaluation=



=Guidelines=


[[Category:Process]]

Roles template

2020-04-27T17:38:45Z

HunterNyan: Redirected page to Wiki style guidelines/Templates

#REDIRECT [[Wiki_style_guidelines/Templates]]

Category:DAO

2020-04-27T17:15:52Z

HunterNyan: Add som Substance

=What is DAO?=
{{:Template:What_is_DAO}}

For More Infomation check out [[Bisq_DAO:_Governing_Bisq]]

[[Category:Bisq]]

Decentralized autonomous organization

2020-04-27T17:15:14Z

HunterNyan: made template

__TOC__

=Introduction to the Bisq DAO=
Just as the Bisq exchange is decentralized and censorship-resistant, so is its [[governance]] model—and the Bisq DAO and BSQ token are the tools that make it possible.
<br/>
The Bisq founders realized that decentralized software—no matter how technically robust—is no good if it’s still controlled by a single entity. All the software’s technical strength would be worthless if the whole project could be ruined by attacking the single entity that runs it.
<br/>
Thus the need for decentralizing the resources in charge of running Bisq itself. These resources cannot be organized in the form of a company, a nonprofit, or any other traditional organization because a single entity would be a single point of failure. But what to do? How can a project do anything useful without becoming an organization with some kind of structure? How can strategy be determined? How can resources be allocated? How can work get done? How can revenue be earned, and how can it be distributed?
<br/>
https://www.youtube.com/embed/pNvOZlIDYEQ
<br/>
The Bisq project needed infrastructure to provide these functions, and the Bisq DAO is its solution.

=What is a DAO?=
{{What is DAO}}

=The Bisq DAO=
The Bisq DAO forgoes a system where governance is dictated by the rigid rules of software in favour of a self-contained economy where governance is ''guided'' by software but ultimately determined by the collective, subjective judgments([[Voting]]) of its community.

It achieves this by introducing a unit of value called the '''[[BSQ| BSQ token]]''' that enables Bisq [[Stakeholder|stakeholders]]—[[Category:Contributor_Docs|contributors]], [[traders]], or anyone who owns [[BSQ]]—to make subjective value judgments. This token underlies all actions in the DAO.

==BSQ Token==
{{:BSQ#BSQ Token}}

==Overview==
Here’s a graphical overview of how the DAO works at a high level:
[[File:User-dao-diagram.png|thumb|User-dao-diagram]]

Let’s observe some of the dynamics of this system:
* [[Category:Contributor Docs|Contributors]] ''maintain'' Bisq through valuable work
* [[Traders]] ''use'' Bisq to buy and sell bitcoin and other cryptocurrencies
* [[Category:Contributor Docs|Contributors]] ''earn'' BSQ tokens when their compensation requests are approved through voting
* [[Traders]] ''buy'' BSQ tokens in order to pay lower trading fees
* [[Stakeholders]] ''vote'' on compensation requests
* [[Category:Contributor Docs|Contributors]] can ''lock'' a [[bond]] in BSQ to ensure integrity in high-trust [[Category:Roles]]

Now let’s see how these dynamics enable the Bisq DAO to provide 3 core governance functions without any central points of authority.

==Earn and distribute revenue==
Every project needs to be financially sustainable to fund ongoing operations and development. But traditional means of handling revenue and revenue distribution are necessarily centralized—any receiving address or account must be owned by one person, or a small group; determining how much a person should be paid must be determined by one person or a small group; etc.

===Contributors produce, creating BSQ===
In the Bisq DAO, trading fees are collected from traders and distributed to contributors, but there is no central authority to do this. Here’s how it works: after a Bisq contributor does work, they file a '''[[compensation]] request''' in the DAO with a description of what they did and how much BSQ they want in return. Then, stakeholders (who are other contributors, traders, and anyone else with BSQ) vote for/against the request. If the request is approved, the contributor is issued new BSQ in the amount they requested and '''BSQ supply is increased'''.

===Where does new BSQ actually come from?===
Recall that a BSQ token is merely coloured bitcoin. When a contributor makes their compensation request in the DAO, they must also include the tiny amount of bitcoin to be 'coloured' as BSQ ([[Bisq_DAO_technical_overview|the spec]] requires 100 satoshis). So if a contributor requests 1,000 BSQ, they will need to include 100 * 1,000 = 100,000 satoshis with their compensation request—just about 10 USD at a rate of 10,000 USD/BTC.

If their request is approved, those satoshis are 'colored' and recognized as 1,000 valid BSQ tokens on Bisq. Assuming a BSQ market value of 1 USD (exact value will fluctuate), the contributor will have been granted 1,000 USD worth of BSQ for a negligible cost of 10 USD.

===Traders consume, burning BSQ===
Then, a [[trader]] looking for lower trading fees can buy those BSQ tokens from a contributor. When they buy BSQ tokens for BTC, the contributor is paid for their work, and the value transfer from producer to consumer is complete! When a trader pays trading fees with BSQ, those BSQ tokens are burned or "decoloured" and '''BSQ supply is decreased'''. This process of creating and destroying BSQ tokens enables a sort of monetary policy controlled by Bisq stakeholders and traders.

In this way, there is no need for a central entity to collect and distribute revenue: the BSQ token enables a transfer of value from producer to consumer without any single entity controlling any aspect of the decision-making or distribution process.

* The Bisq DAO does not require traders to use BSQ for trading fees. They’re free to pay trading fees directly with BTC, but they will pay higher rates than if they bought BSQ with BTC and paid with BSQ instead.

====Note on BTC revenues====
In the past, before the Bisq DAO launch and before the integration of Bisq’s new trade protocol, trading fees were only collected in BTC and only went to arbitrators. There was no mechanism to distribute them to other contributors. The DAO solves this distribution problem with BSQ through the process outlined above.

But since traders can still pay trading fees with BTC, where do those BTC fees go?

BTC fees go to a bitcoin "donation" address held by a [[Donation_Address_Holder|bonded contributor]], who uses the BTC to buy BSQ on a regular basis to distribute the BTC fees to stakeholders, and the BSQ obtained [https://github.com/bisq-network/proposals/issues/55 is burned].

==Determine strategy==
Another point of centralization in traditional organizations is with strategy. How can a project determine strategy without some form of designated leadership: an executive, manager, or leader to give direction and allocate resources?

The Bisq DAO beats this tradition with collective decision-making on strategy and other matters through '''weighted voting''' based on BSQ stake.

Here’s how it works: any [[stakeholder]] can make a proposal in the DAO. It can be anything: a change in a [[DOA_PARAM|trading parameter]], a new bonded [[Category:Roles|role]], or even something more generic like an adjustment of the overall project strategy. [[Stakeholders]] vote on the proposal, and their voting weight is based on BSQ stake, through a combination of two metrics:
* amount of BSQ committed to a particular vote
* amount of BSQ earned over time through contributions

Taking both metrics into account discourages deep-pocketed whales from suddenly seizing control of the project, while still valuing dedicated stakeholders with consistent contributions over time. It brings about a '''strict meritocracy''' in which people need to somehow buy in to the Bisq project in order to take part in its governance, and the more significant their stake, the stronger their voice.

In this way, there is no need to rely on a single leadership team for direction: the community collectively manages itself.

==Ensure honesty in high-trust roles==
Despite the Bisq project’s attempts to resist concentrating control as much as possible, it’s impossible to avoid in some places. Domain name owners, social account admins, mediators, various node operators: these are all roles that must exist, but necessarily retain significant control and require a high degree of trust.

Part of the benefit of a centralized team of thoroughly-vetted people reliant on a paycheck, as is the case in most companies, is that the risk of trusting people with significant responsibility is lower: they have a lot to lose if the company finds they have violated their integrity and engaged in foul play.

This dynamic can be reproduced—at least partly—in a project without a central authority through bonding. The concept is simple enough: create skin in the game. Require that a person interested in taking on a high-trust role post a [[bond]] that’s high enough to discourage them from engaging in foul play.

But what happens if that person goes rogue? In a project without central authority, who decides when they’ve crossed the line, and what their fate should be?

As with strategy and compensation, the community decides through voting. Anyone who suspects foul play can make a case for confiscating a bond with a new proposal, and stakeholders vote to determine an outcome.

* Confiscating a bond is a harsh penalty which should not be taken lightly. Therefore, the Bisq DAO makes confiscation proposals especially hard to approve: they require a quorum of at least 200,000 BSQ and 85% acceptance to pass (instead of the typical >50%).
In this way, the risk that people in high-trust roles misbehave is minimized, and the community has access to a responsible mechanism for handling such a scenario in cases that warrant it.

=Learn more and stay in touch=
To learn more about the Bisq DAO, please see:
* The [[Category:DAO| DAO Category]]
* Bisq [[DAO user reference]], a doc which offers practical details on the workings of the DAO, along with high-level technical details.
* Bisq [[DAO technical overview]], along with technical details of BSQ tokens, this doc shows example transactions for several DAO functions.
* [[Phase Zero: A plan for bootstrapping the Bisq DAO]], a doc which offers a more comprehensive overview of Bisq and the Bisq DAO.
* [https://www.youtube.com/playlist?list=PLFH5SztL5cYOLdYJj3nQ6-DekbjMTVhCS Bisq DAO Basics], a YouTube video series that covers foundational concepts underlying the DAO such as bitcoin transactions, coloured coins, etc.

Feel free to get in touch with us on [https://twitter.com/bisq_network Twitter], [[Keybase]], or [https://bisq.community/ the forum].

= User Guides =
* [[User Guide: Bisq DAO for Traders]] — Use BSQ to get lower trading fees and compensate contributors
* [[User Guide: Bisq DAO for Contributors]] — Govern Bisq through the DAO by making proposals and voting

[[Category:DAO]]

Template:What is DAO

2020-04-27T17:14:27Z

HunterNyan: Creating Template:What is DAO

Conventional entities such as for-profit and non-profit corporations must be sanctioned by the state: they are legal entities registered in particular jurisdictions. No matter how big or small or virtuous or innovative they are, they cannot operate without state approval. In return for this approval, the entity is endowed with rights (e.g., limited liability) and responsibilities (e.g., taxes).

A '''decentralized autonomous organization''' ([[DAO]]) is just a generic term for a governance model sanctioned by software: code defines conventions for governing the project irrespective of the stance of the state.

* We say a DAO’s governance model must be ''sanctioned'' by software, not necessarily ''controlled'' by software. The Bisq DAO, for example, is not controlled by software: software merely provides a framework for the people involved with the Bisq project to (collectively) manage the software itself. The Bisq DAO operates on the idea that '''code is not law'''. Code is written by humans to provide a service to other humans, so it should be accountable to humans too.

The universe of DAOs is diverse. Just as companies come in many shapes and sizes, and some companies are scammy, fraudulent, or just poorly managed—that’s no reason to assume all companies are the same way. It’s the same with DAOs: some DAOs haven’t worked out so well, but others might turn out differently.

Category:Roles

2020-04-27T17:08:25Z

HunterNyan: moved to teams

See https://docs.bisq.network/roles.html

[[Category:Teams]]

Category:Bisq

2020-04-27T17:04:23Z

HunterNyan: best

==Why Bisq Exists?==
{{:Template:Why Bisq exists}}

Introduction

2020-04-27T17:03:39Z

HunterNyan: test

'''Bisq''' is a '''decentralized bitcoin exchange''' best understood in terms of its major component parts:

# Bisq is a cross-platform '''desktop application''' that allows anyone to buy and sell bitcoin in exchange for national currencies and other cryptocurrencies.
# Bisq is a '''trading protocol''' that enables individuals to exchange directly with one another over the internet, eliminating the need for trusted third party exchange services.
# Bisq is the '''peer-to-peer network''' formed by Bisq applications discovering, connecting to, and working with one another to implement the Bisq trading protocol. The Bisq network is ''''fully'''' peer-to-peer in that it requires no centrally-controlled servers and has no single points of failure.

Bisq is '''not a company'''. Bisq is '''free software released''' under version 3 of the GNU Affero General Public License. Bisq is ''''built'''' by individuals around the world who choose to work together, and Bisq is used by individuals around the world who choose to trade with Bisq over many other exchange alternatives.

== Why Bisq exists ==
{{Why Bisq exists}}

== How Bisq works ==
=== In a nutshell ===
Imagine you want to buy bitcoin (BTC) in exchange for US dollars (USD). In Bisq terminology, you are a ''''buyer'''' of BTC looking for a ''''seller'''' of BTC who will accept USD as payment. To complete such a trade using Bisq, you would follow a series of steps similar to these:

# You download and run the Bisq application on your laptop or desktop computer
# You configure Bisq with your USD payment method details
# You browse Bisq’s offer book for existing offers to sell BTC for USD
# You take an existing offer, agreeing to buy the seller’s BTC for your USD
# You send USD from your bank to the seller’s bank and indicate you have done so in Bisq
# You and the seller wait for your USD payment to arrive at the seller’s bank
# The seller receives your USD and indicates they have done so in Bisq
# You receive the seller’s bitcoin and the trade is complete
For complete instructions on each of the steps above, read [[Getting Started with Bisq]].

These steps can vary in a number of ways depending on whether you wish to buy or sell bitcoin, whether you are the ''''maker'''' or the ''''taker'''' of an offer, which payment methods you have access to, and so on. But in any case, the steps above are rather different than those one would follow to complete a similar trade on a centralized exchange.

=== How trading with Bisq is different ===
Beyond the obvious difference that Bisq is a desktop application and not a browser-based web application, the first difference experienced traders will notice is that there is '''no automatic order matching''' on the Bisq exchange. Rather, Bisq users manually search for and select specific offers they wish to take. This approach enables truly peer-to-peer trade settlement, and ensures that users are in control of which counterparties they trade with.

Bisq is also unique among decentralized bitcoin exchanges in the way it coordinates '''out-of-band fiat payments'''. Bisq does not directly integrate with banks or other national currency payment systems in any way. Rather, Bisq’s trading protocol orchestrates the process of buyer and seller working together to settle fiat payments ''''outside'''' of the Bisq application, as demonstrated in steps 5–7 of the trading example above.

These and other differences result in a key tradeoff for Bisq users—one in which '''trade settlement takes longer''', but '''trading itself is far more secure, private and censorship-resistant'''.

=== How Bisq keeps funds secure ===
* Bisq is '''entirely non-custodial'''; users stay in control of fiat and cryptocurrency funds
* Trades include '''security deposits''' from buyer and seller to prevent fraud
* Trading funds and security deposits are locked in a '''2-of-2 multisig escrow'''
* Disputes are handled through a '''decentralized human mediation and arbitration system'''

=== How Bisq keeps data private ===
* Using Bisq requires '''no registration or centralized identity verification'''
* Every Bisq application is a '''Tor hidden service'''
* Bisq has no '''central servers or databases''' to record data
* '''Data is encrypted''' such that trade details are readable only by counterparties

=== How Bisq resists censorship ===
* Bisq’s network is a '''fully distributed P2P network''', and thus difficult to shut down
* Bisq’s network is '''built on top of Tor''', and thus inherits Tor’s own censorship resistance
* '''Bisq is code''', not a company; it is not incorporated, and it cannot be disincorporated

Category:Bisq

2020-04-27T17:03:27Z

HunterNyan: test

The Root of the Project :)
{{:Template:Why Bisq exists}}

Category:Bisq

2020-04-27T17:01:42Z

HunterNyan: smoler

The Root of the Project :)
{{:Bisq#Why Bisq exists}}

Category:Bisq

2020-04-27T17:00:34Z

HunterNyan: induce the bisq poage?

The Root of the Project :)
{{:Bisq}}

Finding your mediator

2020-04-27T16:57:23Z

HunterNyan: Should be a Use Case

Below we detail current Bisq mediators and their onion addresses, as well as how you can find the mediator for a specific Bisq trade.

== Current mediators and their onion addresses ==

{| class="wikitable"
! Mediator
! Onion Address
|-
| leo816
| sjlho4zwp3gecspf.onion
|-
| wiz
| wizrsmceorm4bisq.onion
|-
| bisq_knight
| apbp7ubuyezav4hy.onion
|}

== How to find the mediator for a trade ==

To find a trade's mediator:

# Go to <code>Portfolio > Open Trades</code>, <code>Portfolio > History</code>, or <code>Portfolio > Failed Trades</code> (depending on the status of your trade)
# Click the <code>i</code> icon next to the trade ID of the trade in question (it's on the very left in the first column)
# In the pop-up that appears, toward the bottom, click <code>View Contract in JSON Format</code>.
# Scroll down and you'll see <code>"mediatorNodeAddress"</code> property with a <code>"hostName"</code> and an onion address.

This is the onion address of the mediator for your trade.

== Get in touch with your mediator ==

'''For open trades, you should be able to get in touch with your mediator through Bisq itself.'''

If you cannot get in touch with your mediator on Bisq, you can get in touch with them on the [https://keybase.io/team/bisq Bisq Keybase group]. Their Keybase handles and addresses are displayed in the headline for the #support channel as well.

[[Category:Use Case]]

Take an offer

2020-04-27T16:56:14Z

HunterNyan: removed category

After setting up a [[Create_a_payment_account|payment account]] you're ready to take your first offer.

== Select an offer ==

First, click on '''BUY BTC''' and click on any of the available '''TAKE OFFER TO BUY BTC''' buttons. Each offer will list the min and max amounts you can buy, the exchange price and the payment method.

[[File:BuyBTC-accountenabled.png|thumb|left|500px]]

<br clear=all>

''' Note on limits for new payment accounts: '''

To secure the network from scammers and other bad actors, unsigned Bisq payment accounts are limited to buying 0.01 BTC until they are signed by another trusted peer.

You can have your new payment account signed by selecting an offer to buy bitcoin from a seller who’s capable of signing your account. - Click [[https://docs.bisq.network/payment-methods.html here]] for info on account signing

'''Just look for an offer with a check mark.'''

== Deposit and fees ==

When taking an offer, Bisq creates a special trade wallet to hold your security deposit and fees. This wallet will be used to pay your taker fee, and will then be used to transfer your security deposit into a multisig escrow transaction together with the seller’s security deposit and the bitcoin being traded.

[[File:FundTrade.png|thumb|left|500px]]

<br clear=all>

Once you and the seller have completed your ends of the trade, you’ll receive the bitcoin you bought along with your security deposit.

There are 2 ways to pay for the deposit and fees:

* If you already have enough bitcoin in your Bisq wallet, click '''Transfer funds from Bisq wallet''' and the funds will be automatically transfered to the trade wallet.
* If not, go ahead and send the amount required '''Funds needed''' to the specified address '''Trade wallet address''' using your personal wallet.

''Click [[https://bisq.wiki/Trading_fees here]] for details on trading fees and the BSQ token.''

== Confirm trade ==

Once you’ve funded your trade wallet, you’ll see a '''Review: Take offer to buy bitcoin button appear.'''

Click it, Bisq will display all details pertaining to your offer.

[[File:ConfirmOffer.png|thumb|left|500px]]

<br clear=all>

'''Make sure these details are correct. After you confirm these details, there's no way to cancel the trade you must follow through or risk losing your deposit.'''

If everything looks correct, go ahead and hit '''Confirm: Take offer to buy bitcoin.'''

Your trade has now officially begun!

== Send payment ==

Now that you’ve taken an offer, it’s almost time to pay the seller.

First, before showing you the seller’s payment details, Bisq will wait for the Bitcoin network to confirm the trade’s transactions. On average, this takes 10 minutes.

Then, you’ll see a pop-up with the seller’s details. Go ahead and pay the seller through the agreed payment method.

[[File:SellersPaymentDetails.png|thumb|left|500px]]

<br clear=all>

'''How long should you wait before sending the payment?'''

Each confirmation makes a bitcoin transaction exponentially harder to reverse. You can wait for as many confirmations as you like before sending payment—just note the remaining time indicator. The seller must receive your payment before that timer runs out.

[[File:Trade-remainingtime.png|thumb|left|500px]]

<br clear=all>

''Learn more about Bitcoin transaction confirmations [[https://en.bitcoin.it/wiki/Confirmation here]]''

== Mark payment as sent ==

'''Important:'''

'''Once you’ve sent your payment, be sure to mark the payment as sent in Bisq by clicking the Payment started button.'''

It’s easy to forget this step, but remember: Bisq doesn’t integrate with national currency payment methods in anyway so Bisq won’t know you’ve sent your payment until you say so.

When you click Payment started, the seller will receive a notification that lets them know the payment is on the way. They’ll be on the lookout for it now.

[[File:PaymentStarted.png|thumb|left|500px]]

<br clear=all>

== Complete trade ==

When the seller receives your payment, they’ll mark it as received in Bisq. Bisq will then complete the trade by releasing the bitcoin you bought to you along with your security deposit.

You can keep your new bitcoin in your built-in Bisq wallet by clicking Move Funds to Bisq Wallet or send it elsewhere by clicking Withdraw to External Wallet.

[[File:Movefundsaftertrade.png|thumb|left|500px]]

<br clear=all>

Congratulations. You’ve just completed your first trade on Bisq!

[[Category:Use Cases]]

Encrypting your wallet

2020-04-27T16:54:32Z

HunterNyan: Category:Use Cases

Before setting a password, your Bisq wallet files are stored on your hard drive unencrypted. That means anyone who gains access to your computer (whether by physically stealing it or by hacking it remotely) can gain access to your private keys and take your bitcoin.

Setting a password encrypts your Bisq wallet files so they’re useless to anyone without the password.

To set a password, go to the '''Wallet password''' section of the '''Account''' screen and enter a strong password. ''' Do not forget this password, it cannot be reset by anyone and will make your wallet unusable.'''

[[File:Password.png|thumb|left|500px]]
<br clear=all>
[[Category:Use Cases]]

Encrypting your wallet

2020-04-27T16:53:36Z

HunterNyan: Creating Encrypt your wallet | split from Protect_your_wallet

Funding your wallet

2020-04-27T16:49:55Z

HunterNyan: remove category

Prior to trading on Bisq users must have enough Bitcoin in their Bisq wallet to cover the security deposit as well as the trading and mining fees.

The security deposits help prevent fraud, therefore, Bisq requires that both the buyers and sellers post one (in Bitcoin) for every trade. On the buyer's side, this is normally 10% of the trade amount.

'''Sellers can specify their preferred deposit percentage when creating an offer to sell bitcoin. The default is 10%, but it’s possible you’ll come across offers that require bigger (or smaller) security deposits.'''

As of this writing, you would need 0.0012 BTC to take an offer to buy 0.01 BTC that requires a 10% security deposit. But please note that mining fees can fluctuate, some sellers may require bigger security deposits, and you’ll need more for bigger trades, so it may be better to acquire more than the bare minimum so you have more flexibility.

== How to obtain Bitcoin ==

If you don’t already own the Bitcoin you need, you’ll need to obtain it. How? You’ve got options. Friends and family are often the best option—simply buy a small amount of bitcoin directly from someone you trust. Otherwise, you can try a [https://coinatmradar.com/ local bitcoin ATM] (many don’t require ID for small transactions), [https://www.meetup.com/topics/bitcoin/ Bitcoin meetups/events], or vouchers.

Once you’ve gotten enough bitcoin for your security deposit and fees, you can move it into Bisq’s built-in wallet. This isn’t strictly required, but it’ll make trading more convenient since the security deposit & fees you need to accept an offer will be readily available when making or taking an offer.

== Sending Bitcoin to your Bisq wallet ==

To send Bitcoin to your Bisq wallet, go to the '''Funds''' screen and click on the '''Receive''' tab. Send your Bitcoin to one of the addresses listed.

[[File:ReceiveFunds.png|thumb|left|500px]]

<br clear=all>
'''If you’d rather not hold any bitcoin in your Bisq wallet, that’s fine, but you’ll need to transfer your security deposit & fees manually when you take an offer.'''

''A note on centralized exchanges:''

Most centralized platforms and exchanges (like Coinbase, Binance, Kraken, etc) track your personal information, putting you at risk by tying your identity to the Bitcoin you buy and sell there. Also, since Bitcoin transactions are public and easily traceable, potentially all of your future transactions involving those Bitcoin could be traced back to you.

Bisq is built from the ground up to avoid this privacy fiasco, so we strongly recommend avoiding centralized exchanges and to get your first Bitcoin through one of the other channels mentioned above.

[[Category:Use Cases]]

Resyncing SPV file

2020-04-27T16:48:18Z

HunterNyan: fixed link

'''Problem'''


The Simplified Payment Verification (SPV) file  may become corrupt  and create Bisq wallet issues, such as a wallet not displaying the correct account balance.

'''Solution'''

Resync the SPV file by deleting it and then rebuilding it from the Bitcoin blockchain. Bisq can then retrieve accurate transaction information.

For more information, refer to [[Resync SPV chain]]

== How to Resync the SPV File ==
<ol>
<li> Open Bisq and click '''Settings'''</li>

[[File:Market tab.png|thumb|left|500px]]

<br clear=all>

<li> In the '''Network Info''' tab click '''Delete SPV File and Resync''' </li>

[[File:Network info.png|thumb|left|500px]]

<br clear=all>

<li> Restart </li>

 After the Resync you are prompted to restart Bisq. The time to restart depends upon the age of your wallet and number of transactions. The CPU usage may be high and the Bisq application may not respond immediately, this is normal.


== Help! I Can't Access the Bisq Settings Screen==

If you can't open Bisq to access the Settings section, you can manually delete the <code>btc_mainnet/wallet/bisq.spvchain</code> from your [[Data_directory|data directory]].

The default data directory locations can be found [[Backup_%26_Recovery|here]]. You will then need to manually restart Bisq '''twice''' to complete the resync.

[[Category:Use Cases]]

Creating a payment account

2020-04-27T16:36:30Z

HunterNyan: fixed links

Before you can buy or sell on Bisq you must create a national currency account if trading Bitcoin or an altcoin account if trading altcoins.

The following steps we'll take you through the process of setting up a national currency account for the purpose of buying Bitcoin.

== Creating a national currency account ==

Since we're looking to buy Bitcoin we would navigate to the '''BUY BTC''' screen on the Bisq application. You'll quickly notice that all the offers are disabled, this is because you have yet to set up an appropriate account. For details on the different types of payment accounts, including trade limits, trading period and regions check out [[Payment methods]].

[[File:BuyBitcoinscreen.png|thumb|left|500px]]

<br clear=all>
We'll now create a Zelle account. You can adapt the instructions that follow to the payment method you choose.

Go to the '''Account''' screen and click on '''National Currency Accounts'''. Under '''Select payment method''' choose '''Zelle''' from the dropdown menu and enter your details.

You’ll need to enter your '''full name''' as registered with your Zelle account as well as the '''email address or mobile phone number''' linked to your Zelle account.

[[File:Accountsetup.png|thumb|left|500px]]

<br clear=all>

You don’t need to edit the Salt field. You can keep the Account name unchanged or change it however you like: this is an internal label that only you will ever see, so there’s no right or wrong value for it.

'''Warning:''' '''It’s crucial that the information you enter here is correct. Your trading partner can only acknowledge your payment if it’s from the account detailed here. Once you’ve created an account, you cannot edit its information (if you need to make a change, you’ll have to delete and add the account again). '''

Once you're done, click on '''Save new account''' and go back to the '''Buy BTC''' screen. Offers requiring the payment method you just configured should now be enabled:

[[File:BuyBTC-accountenabled.png|thumb|left|500px]]

<br clear=all>

'''A few things to keep in mind:'''

''* What if there are no existing offers for the payment method I want to use?''

If you don’t see any offers for the payment method you want to use, consider creating your own offer with the '''Create new offer to buy BTC with USD''' button in the top-right. Just keep in mind that your offer will only be available while your Bisq program is '''online'''.

You can also check back later, as offers come and go as Bisq users around the world go online and offline throughout the day.

''* Where is my payment account data stored?''

On your [[Backup_%26_Recovery|computer]] only (i.e., the computer on which Bisq is installed). Only your trading partner (and your mediator or arbitrator, if there’s a dispute) will ever see your payment details.

[[Category:Use Cases]]

Creating a payment account

2020-04-27T16:34:07Z

HunterNyan: remove guides

Before you can buy or sell on Bisq you must create a national currency account if trading Bitcoin or an altcoin account if trading altcoins.

The following steps we'll take you through the process of setting up a national currency account for the purpose of buying Bitcoin.

== Creating a national currency account ==

Since we're looking to buy Bitcoin we would navigate to the '''BUY BTC''' screen on the Bisq application. You'll quickly notice that all the offers are disabled, this is because you have yet to setup an appropriate account. For details on the different types of payment accounts, including trade limits, trading period and regions [[https://docs.bisq.network/payment-methods.html click here]].

[[File:BuyBitcoinscreen.png|thumb|left|500px]]

<br clear=all>
We'll now create a Zelle account. You can adapt the instructions that follow to the payment method you choose.

Go to the '''Account''' screen and click on '''National Currency Accounts'''. Under '''Select payment method''' choose '''Zelle''' from the dropdown menu and enter your details.

You’ll need to enter your '''full name''' as registered with your Zelle account as well as the '''email address or mobile phone number''' linked to your Zelle account.

[[File:Accountsetup.png|thumb|left|500px]]

<br clear=all>

You don’t need to edit the Salt field. You can keep the Account name unchanged or change it however you like: this is an internal label that only you will ever see, so there’s no right or wrong value for it.

'''Warning:''' '''It’s crucial that the information you enter here is correct. Your trading partner can only acknowledge your payment if it’s from the account detailed here. Once you’ve created an account, you cannot edit its information (if you need to make a change, you’ll have to delete and add the account again). '''

Once you're done, click on '''Save new account''' and go back to the '''Buy BTC''' screen. Offers requiring the payment method you just configured should now be enabled:

[[File:BuyBTC-accountenabled.png|thumb|left|500px]]

<br clear=all>

'''A few things to keep in mind:'''

''* What if there are no existing offers for the payment method I want to use?''

If you don’t see any offers for the payment method you want to use, consider creating your own offer with the '''Create new offer to buy BTC with USD''' button in the top-right. Just keep in mind that your offer will only be available while your Bisq program is '''online'''.

You can also check back later, as offers come and go as Bisq users around the world go online and offline throughout the day.

''* Where is my payment account data stored?''

On your [[https://bisq.wiki/Backup_%26_Recovery computer]] only (i.e., the computer on which Bisq is installed). Only your trading partner (and your mediator or arbitrator, if there’s a dispute) will ever see your payment details.

[[Category:Use Cases]]

Category:Bisq

2020-04-27T16:15:47Z

HunterNyan: test

Self Linking [[Category:Bisq]]<br>
The Root of the Project :)

Category:Client

2020-04-27T16:11:00Z

HunterNyan: test

The Parent Category of the Bisq Client
[[Category:Bisq]]

Category:Bisq

2020-04-27T16:08:11Z

HunterNyan: testing something

The Root of the Project :)

Roles

2020-04-27T13:40:48Z

HunterNyan: The Roles Maintainer role

This article is a stub pending the transcription of https://docs.bisq.network/roles.html here to the wiki. See https://github.com/bisq-network/roles/issues for the canonical list of all current roles and see [[:Category:Roles|Category:Roles]] for a list of all roles documented here on the wiki.

Roles are the way contributors take responsibility for Bisq Network resources and processes.

__TOC__

=Introduction=
There are many resources and processes vital to the operation of the Bisq Network that require ownership by individual contributors. For example, someone must merge pull requests into the ''bisq-desktop'' repository, someone must manage DNS for the ''bisq.network'' domain, someone must conduct monthly stakeholder voting, and so on.

This document defines the system of '''roles''' used within the Bisq DAO to enumerate, define and track each of these responsibilities. The system is designed with two major goals in mind:
# To maximize role owner autonomy in order to achieve Phase Zero decentralization goals.
# To maximize transparency such that DAO stakeholders can effectively review and vote on role owner compensation requests.

=Properties=
The following are properties common to all roles.

==Duties==
'''Duties''' are actions that must be performed for a certain resource or process to function normally.
For example, a repository maintainer’s duties include merging pull requests in a timely fashion, and a website operator’s duties include keeping the site available at all times.

==Rights==
'''Rights''' are special permissions or other access required to perform the Duties of a role.

For example, a repository maintainer’s rights include write permissions to their repository, and a website operator’s rights include administrative access to site hosting infrastructure.

==Owners==
Owners are contributors who have the Rights required to perform the Duties of a role.

One owner is designated as primary and any other owners are designated as secondary.[https://github.com/bisq-network/proposals/issues/12 Propsal Link] The primary is responsible for performing the Duties of the role, while secondaries stand by, ready to take over for the primary at any time.

=Infrastructure=
The following infrastructure is used to define and manage each role.

==Docs==
Each role should be documented at bisq.wiki, in a document of its own, under the Category [[Category:Roles]] and be references sections of larger documents dedicated to a resource or process in question.

For example, there is "[[Proposals Maintainer]]", and in the [[Proposals]] document it pulls it into the Maintainer section within.

Each role’s documentation should enumerate its Duties and Rights and link to its [[Category:Teams]] and Active Issue and Propsoal Issue.

==Team==
Each role has a dedicated GitHub team where each of the role’s Owners are members. The team is used to manage access to GitHub repositories that the role is responsible for and to send notifications to role owners with @mentions in GitHub issues and pull requests.

For example, the [https://github.com/orgs/bisq-network/teams/desktop-maintainers/members @bisq-network/desktop-maintainers] team has write access to the [https://github.com/bisq-network/bisq-desktop bisq-network/bisq-desktop] repository.

*GitHub teams are visible only to GitHub organization members. To join the [https://github.com/bisq-network @bisq-network] org, see the [[Contributor Checklist]].

The primary role owner is also assigned as the '''maintainer''' of their role’s GitHub team, such that they may manage the team without requiring the intervention of a GitHub admin.

==Issue==
Each role has a dedicated GitHub issue in the [[https://github.com/bisq-network/roles/issues bisq-network/roles]] repository, wherein:
* The '''Assignees''' field is used to track role ownership.
* The '''Description''' field is used to link to the role’s Docs, Team and primary Owner.
* '''Comments''' are used for Reporting and feedback.

See the [https://github.com/bisq-network/roles/issues/30 Proposals Maintainer] role issue for an example.

=Types=
Most roles fit into one of the types below.

==Maintainer==
A ''Maintainer'' is a contributor responsible for enforcing process in a given GitHub repository.

Examples: [https://github.com/bisq-network/roles/issues/63 Bisq Desktop Maintainer], [https://github.com/bisq-network/roles/issues/30 Proposals Maintainer].

===Maintainer Duties===
* Merging or closing pull requests after sufficient review.
* Tagging releases.
* Triaging incoming issues and keeping them organized over time.
** A Maintainer is not a Developer or a Reviewer. Submitting and reviewing pull requests is something any contributor can do; neither are maintainer duties per se.
** This is particularly important from a [[Compensation]] perspective. '''If you are a maintainer, do NOT group your development and review activities together with your maintainer role in your compensation requests'''. Rather, account for them separately like any other contributor would.
** The goal is to have as many competent contributors developing and reviewing as possible, not to load everything on the maintainer. [https://rfc.unprotocols.org/spec:1/C4/#21-preliminaries C4] is the inspiration here, it’s worth (re-)reading.

===Maintainer Rights===
Write access to the repository they are responsible for.

==Operator==
An ''Operator'' is a contributor responsible for keeping a given resource running and functioning normally.

Examples: [https://github.com/bisq-network/roles/issues/19 Forum Operator], [https://github.com/bisq-network/roles/issues/14 Bisq Pricenode Operator].

===Operator Duties===
* Keep the given resource online and functioning normally.
* Keep the resource up to date with latest version.
* Maintain backups as appropriate.
* Report on any incidents.

===Operator Rights===
* Administrative access to hosting infrastructure.
* Ownership of any domain name used.

==Administrator==
An ''Administrator'' ('Admin') is a contributor responsible for managing a given resource.

Examples: [https://github.com/bisq-network/roles/issues/16 GitHub Admin], [https://github.com/bisq-network/roles/issues/23 Slack Admin].

===Admin Duties===
Respond to change requests.

===Admin Rights===
Access to the administrative interface of the resource in question.

==Moderator==
A '''Moderator''' is a contributor responsible for enforcing process and standards in a given communications channel.

Examples: [https://github.com/bisq-network/roles/issues/37 Bitcointalk Moderator], [https://github.com/bisq-network/roles/issues/25 Reddit Moderator].

===Moderator Duties===
* Ensure discussions are on topic, civil, etc.
* Post key announcements in a timely fashion.

===Moderator Rights===
Moderator (or equivalent) status in the channel.

=Common duties=
The following duties are common to all roles.

==Reporting==
Primary role Owners should report once a month in the form of a comment on their Issue.[https://github.com/bisq-network/proposals/issues/13 Proposal Link] The report should contain whatever information the owner believes would be valuable to other users, contributors and stakeholders. The comment should be formatted in Markdown as follows:
<nowiki>
## YYYY.MM report

<content>

/cc bisq-network/compensation#<number>
</nowiki>

Where <content> is the content of the report itself, and <number> is the number of that contributor’s monthly compensation request. [https://github.com/bisq-network/proposals/issues/16#issuecomment-393852612 Example].

Some roles may have nothing to report in a given month. In this case, a report should still be written stating that there is "nothing to report". [https://github.com/bisq-network/proposals/issues/18#issuecomment-393217596 Example].

==Documentation==
Primary role Owners should document changes to their role by updating the Role on the wiki [[Category:Roles]].

==Communication==
Primary role Owners should respond in a timely fashion to feedback comments on their role Issue, issues created in their repositories, @mentions of their Team, and questions in their Slack channel.

=Compensation=
Role owners should include a summary line item for each role they own in a monthly [[Compensation#Create_your_compensation_request_issue|compensation request]]. Each summary should include:
# The name of the role,
# a link to the owner’s monthly report for that role, and
# the total amount of BSQ being requested for performing the role’s duties during that month.
<nowiki>
Example 1. Per-role line items in a compensation request
Bisq Desktop Maintainer: bisq-network/roles#63 (comment) (350 BSQ)

Bisq Seednode Operator: bisq-network/roles#15 (comment) (150 BSQ)
</nowiki>

* Secondary role owners should not submit monthly reports or compensation requests for a role unless they actually performed the duties of that role during that month.

The amount of BSQ requested should include any hard costs (e.g. hosting) plus time and effort costs involved in performing the duties of the role. These costs should be detailed in the monthly report as follows:
<nowiki>
Example 2. Monthly report for Bisq Desktop Maintainer
## 2018.07 report

Regular duties (150 BSQ)

Big issue cleanup (200 BSQ)

Total: 350 BSQ

/cc bisq-network/compensation#42
</nowiki>
<nowiki>

Example 3. Monthly report for Bisq Seednode Maintainer
## 2018.07 report

Hosting 2 nodes @ 50 USD/mo on Digital Ocean (100 BSQ)

Upgrade nodes to v0.7.1 (50 BSQ)

Total: 150 BSQ

/cc bisq-network/compensation#42
</nowiki>

The only work items that should be included in role compensation are those Duties that can be performed only by that role’s owner. Everything else should be itemized independently.

For example, as mentioned above in the Maintainer Duties section, a repository maintainer’s main duties are merging pull requests and triaging incoming issues. If the person playing the maintainer role submits their own pull requests, or performs reviews of others' pull requests, that work should NOT be grouped together with regular maintainer duties when putting together a compensation request. Rather, each PR submitted or reviewed should be called out separately as individual contributions.

=Bonding=
Most roles involve special Rights that, if abused, could cause damage to the Bisq Network. For this reason, role owners must put up a ''bond'' in BSQ commensurate with the amount of damage that could be caused. In the event of a role owner turning into a bad actor or being grossly negligent, this bond can be confiscated through a BSQ voting process.

Bonding is currently in a transitional state, the expected bond will be found in the respective Role Page.

=Processes=
The following are some common roles-related processes.

==Proposing a new role==
Typically, proposing a new role is one part of a larger proposal to introduce some new resource or process.

# Discuss the idea informally with other contributors, e.g. via [Keybase].
# Follow the [[Proposals]] process to formally suggest the new resource or process.
# Draft documentation for the new resource or process, including a section about the new role, tagged as [WIP] on the Wiki.

For example, see the [https://github.com/bisq-network/proposals/15 proposal to support Tor Relays] and the resulting [https://github.com/bisq-network/proposals/72 Tor Relay Operator] role issue.

==Adding a secondary role owner==
A primary role owner may add a secondary owner with the following steps:
# Add them as a member of the role’s GitHub Team.
# Add them as an assignee to role’s GitHub Issue.
# Announce the change via a comment on the role’s GitHub Issue.

==Transferring role ownership==
A primary owner may transfer ownership to another with the following steps:
# Grant the ''maintainer'' role to the new primary in the role’s GitHub Team.
# Remove the ''maintainer'' role from yourself.
# Update the role’s GitHub Issue to reflect the new primary owner.
# Announce the change in a comment on the role’s GitHub Issue.

=The Roles Maintainer role=
{{:Roles_Maintainer}}

Main Page

2020-04-27T13:07:31Z

HunterNyan: Creating Template:MainPage Ecosystem

{| id="mp-topbanner" style="width:100%; background:#f6f6f6; margin-top:1.2em; border:1px solid #ddd;"
| style="width:61%; color:#000;" |

{| style="width:100%; border:none; background:none;"
| style="text-align:center; white-space:nowrap; color:#000;" |
<div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;">Welcome to the [[Bisq]] Network Wiki,</div>
<div style="top:+0.2em; font-size:95%;">All Bisq, All the time.</div>
<div id="articlecount" style="width:100%; text-align:center; font-size:85%;">Currently hosting [[Special:Statistics|{{NUMBEROFARTICLES}}]] pages.</div>
<div style="top:+0.2em; font-size:95%;">This wiki is maintained by the [https://bisq.network/community/ Bisq community].</div>
|}

| style="width:39%;" |
{| style="width:100%; border:none; background:none; font-size:120%; font-weight: bold; font-family: 'Ubuntu', sans-serif; text-align: center;"
|<span class="plainlinks">[https://bisq.network/community/ Get Involved!]</span>
|<span class="plainlinks">[https://bisq.network/ The Bisq Network]</span>
|<span class="plainlinks">[[Keybase]]</span>
|}
|}


{| id="mp-upper" style="width: 100%; margin:6px 0 0 0; background:none; border-spacing: 0px;"
| class="MainPageBG" style="width:55%; border:1px solid #cef2e0; background:#f6e5f1; vertical-align:top; color:#000;" |
{| id="mp-left" style="vertical-align:top; background:#f6e5f1;"
! style="padding:2px;" | <h2 id="mp-tfa-h2" style="margin:3px; background:#e9caef; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Bisq</h2>
|-
| style="color:#000;" | <div id="mp-tfa" style="padding:2px 5px">{{MainPage_Intro}}</div>
|-
! style="padding:2px" | <h2 id="mp-dyk-h2" style="margin:3px; background:#e9caef; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Why?</h2>
|-
| style="color:#000;padding:2px 5px 5px" | <div id="mp-dyk">{{MainPage_Reasons}}</div>
|}
| style="border:1px solid transparent;" |

| class="MainPageBG" style="width:45%; border:1px solid #cedff2; background:#f6e5f1; vertical-align:top;"|
{| id="mp-right" style="width:100%; vertical-align:top; background:#f6e5f1;"
! style="padding:2px" | <h2 id="mp-otd-h2" style="margin:3px; background:#efc1e2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">Topic central</h2>
|-
| style="color:#000;padding:2px 5px 5px" | <div id="mp-otd">{{MainPage_Topics}}</div>
|-
! style="padding:2px" | <h2 id="mp-otd-h2" style="margin:3px; background:#efc1e2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">Ecosystem</h2>
|-
| style="color:#000;padding:2px 5px 5px" | <div id="mp-otd"> {{MainPage_Ecosystem}} </div>
|}
|}

== Other pages ==

* '''[[mw:Help:Formatting|Help]]''' - Documentation on wiki editing.
</noinclude>__NOTOC____NOEDITSECTION__

Template:MainPage Ecosystem

2020-04-27T13:06:52Z

HunterNyan: Creating Template:MainPage Ecosystem

* News and Announcements — Stay informed with:
** [https://github.com/bisq-network/proposals/issues/20 the Bisq mailing list]
** [https://twitter.com/bisq_network Twitter]
** [https://www.youtube.com/c/bisq-network YouTube]
** [https://www.facebook.com/bisqnetwork/ Facebook]
* Media and Press — Catch up on [https://twitter.com/bisq_network/status/946723541298360320 talks, interviews, podcasts and articles] about Bisq
* Chat and Discussion — Connect with other users on
** the [https://bisq.community/ Bisq Forum]
** [https://webchat.freenode.net/?channels=bisq IRC]
** [[Keybase]]
* Charts and Data — Explore Bisq
** [https://markets.bisq.network/ Markets]
** [https://bisq.network/volume Global Volume]
** [https://coin.dance/volume/bisq/ Regional Volume]
** [https://bisq.network/release-stats Release Statistics]
* Ratings and Reviews — Read Bisq user experience reports and reviews on sites like
** [https://www.cryptocompare.com/exchanges/bisq/ CryptoCompare]

Main Page

2020-04-27T13:01:51Z

HunterNyan: Ecosystem

{| id="mp-topbanner" style="width:100%; background:#f6f6f6; margin-top:1.2em; border:1px solid #ddd;"
| style="width:61%; color:#000;" |

{| style="width:100%; border:none; background:none;"
| style="text-align:center; white-space:nowrap; color:#000;" |
<div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;">Welcome to the [[Bisq]] Network Wiki,</div>
<div style="top:+0.2em; font-size:95%;">All Bisq, All the time.</div>
<div id="articlecount" style="width:100%; text-align:center; font-size:85%;">Currently hosting [[Special:Statistics|{{NUMBEROFARTICLES}}]] pages.</div>
<div style="top:+0.2em; font-size:95%;">This wiki is maintained by the [https://bisq.network/community/ Bisq community].</div>
|}

| style="width:39%;" |
{| style="width:100%; border:none; background:none; font-size:120%; font-weight: bold; font-family: 'Ubuntu', sans-serif; text-align: center;"
|<span class="plainlinks">[https://bisq.network/community/ Get Involved!]</span>
|<span class="plainlinks">[https://bisq.network/ The Bisq Network]</span>
|<span class="plainlinks">[[Keybase]]</span>
|}
|}


{| id="mp-upper" style="width: 100%; margin:6px 0 0 0; background:none; border-spacing: 0px;"
| class="MainPageBG" style="width:55%; border:1px solid #cef2e0; background:#f6e5f1; vertical-align:top; color:#000;" |
{| id="mp-left" style="vertical-align:top; background:#f6e5f1;"
! style="padding:2px;" | <h2 id="mp-tfa-h2" style="margin:3px; background:#e9caef; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Bisq</h2>
|-
| style="color:#000;" | <div id="mp-tfa" style="padding:2px 5px">{{MainPage_Intro}}</div>
|-
! style="padding:2px" | <h2 id="mp-dyk-h2" style="margin:3px; background:#e9caef; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Why?</h2>
|-
| style="color:#000;padding:2px 5px 5px" | <div id="mp-dyk">{{MainPage_Reasons}}</div>
|}
| style="border:1px solid transparent;" |

| class="MainPageBG" style="width:45%; border:1px solid #cedff2; background:#f6e5f1; vertical-align:top;"|
{| id="mp-right" style="width:100%; vertical-align:top; background:#f6e5f1;"
! style="padding:2px" | <h2 id="mp-otd-h2" style="margin:3px; background:#efc1e2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">Topic central</h2>
|-
| style="color:#000;padding:2px 5px 5px" | <div id="mp-otd">{{MainPage_Topics}}</div>
|-
! style="padding:2px" | <h2 id="mp-otd-h2" style="margin:3px; background:#efc1e2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">Ecosystem</h2>
|-
| style="color:#000;padding:2px 5px 5px" | <div id="mp-otd">{{MainPage_Ecosystem}}</div>
|}
|}

== Other pages ==

* '''[[mw:Help:Formatting|Help]]''' - Documentation on wiki editing.
</noinclude>__NOTOC____NOEDITSECTION__

File:Bsq-block-explorer-voting.png

2020-04-27T12:53:01Z

HunterNyan:

Some BSQ transactions on the BSQ block explorer.

File:Dao-vote-results.png

2020-04-27T12:51:13Z

HunterNyan:

See voting results.

File:Vote-reveal-popup.png

2020-04-27T12:50:10Z

HunterNyan:

Vote reveal pop-up.

File:Vote-submit.png

2020-04-27T12:47:32Z

HunterNyan:

Select voting weight and submit all votes.

File:Vote-proposal.png

2020-04-27T12:46:29Z

HunterNyan:

Cast vote on proposals.

File:Make-dao-proposal.png

2020-04-27T12:45:32Z

HunterNyan:

Make a proposal.

File:Voting-cycle-overview.png

2020-04-27T12:43:44Z

HunterNyan:

Voting cycle overview.

File:Trading-fee-toggle.png

2020-04-27T12:37:36Z

HunterNyan:

Trading fee toggle.

File:Bsq-buy-offers.png

2020-04-27T12:35:29Z

HunterNyan:

Pick a BSQ offer you like and make the trade.

File:Add-new-bsq-account.png

2020-04-27T12:34:53Z

HunterNyan:

Set up BSQ payment account.

File:Bsq-wallet-address.png

2020-04-27T12:33:48Z

HunterNyan:

Where to find your BSQ wallet address.

Decentralized autonomous organization

2020-04-27T12:29:41Z

HunterNyan: User Guides

__TOC__

=Introduction to the Bisq DAO=
Just as the Bisq exchange is decentralized and censorship-resistant, so is its [[governance]] model—and the Bisq DAO and BSQ token are the tools that make it possible.
<br/>
The Bisq founders realized that decentralized software—no matter how technically robust—is no good if it’s still controlled by a single entity. All the software’s technical strength would be worthless if the whole project could be ruined by attacking the single entity that runs it.
<br/>
Thus the need for decentralizing the resources in charge of running Bisq itself. These resources cannot be organized in the form of a company, a nonprofit, or any other traditional organization because a single entity would be a single point of failure. But what to do? How can a project do anything useful without becoming an organization with some kind of structure? How can strategy be determined? How can resources be allocated? How can work get done? How can revenue be earned, and how can it be distributed?
<br/>
https://www.youtube.com/embed/pNvOZlIDYEQ
<br/>
The Bisq project needed infrastructure to provide these functions, and the Bisq DAO is its solution.

=What is a DAO?=
Conventional entities such as for-profit and non-profit corporations must be sanctioned by the state: they are legal entities registered in particular jurisdictions. No matter how big or small or virtuous or innovative they are, they cannot operate without state approval. In return for this approval, the entity is endowed with rights (e.g., limited liability) and responsibilities (e.g., taxes).

A '''decentralized autonomous organization''' ([[DAO]]) is just a generic term for a governance model sanctioned by software: code defines conventions for governing the project irrespective of the stance of the state.

* We say a DAO’s governance model must be ''sanctioned'' by software, not necessarily ''controlled'' by software. The Bisq DAO, for example, is not controlled by software: software merely provides a framework for the people involved with the Bisq project to (collectively) manage the software itself. The Bisq DAO operates on the idea that '''code is not law'''. Code is written by humans to provide a service to other humans, so it should be accountable to humans too.

The universe of DAOs is diverse. Just as companies come in many shapes and sizes, and some companies are scammy, fraudulent, or just poorly managed—that’s no reason to assume all companies are the same way. It’s the same with DAOs: some DAOs haven’t worked out so well, but others might turn out differently.

=The Bisq DAO=
The Bisq DAO forgoes a system where governance is dictated by the rigid rules of software in favour of a self-contained economy where governance is ''guided'' by software but ultimately determined by the collective, subjective judgments([[Voting]]) of its community.

It achieves this by introducing a unit of value called the '''[[BSQ| BSQ token]]''' that enables Bisq [[Stakeholder|stakeholders]]—[[Category:Contributor_Docs|contributors]], [[traders]], or anyone who owns [[BSQ]]—to make subjective value judgments. This token underlies all actions in the DAO.

==BSQ Token==
{{:BSQ#BSQ Token}}

==Overview==
Here’s a graphical overview of how the DAO works at a high level:
[[File:User-dao-diagram.png|thumb|User-dao-diagram]]

Let’s observe some of the dynamics of this system:
* [[Category:Contributor Docs|Contributors]] ''maintain'' Bisq through valuable work
* [[Traders]] ''use'' Bisq to buy and sell bitcoin and other cryptocurrencies
* [[Category:Contributor Docs|Contributors]] ''earn'' BSQ tokens when their compensation requests are approved through voting
* [[Traders]] ''buy'' BSQ tokens in order to pay lower trading fees
* [[Stakeholders]] ''vote'' on compensation requests
* [[Category:Contributor Docs|Contributors]] can ''lock'' a [[bond]] in BSQ to ensure integrity in high-trust [[Category:Roles]]

Now let’s see how these dynamics enable the Bisq DAO to provide 3 core governance functions without any central points of authority.

==Earn and distribute revenue==
Every project needs to be financially sustainable to fund ongoing operations and development. But traditional means of handling revenue and revenue distribution are necessarily centralized—any receiving address or account must be owned by one person, or a small group; determining how much a person should be paid must be determined by one person or a small group; etc.

===Contributors produce, creating BSQ===
In the Bisq DAO, trading fees are collected from traders and distributed to contributors, but there is no central authority to do this. Here’s how it works: after a Bisq contributor does work, they file a '''[[compensation]] request''' in the DAO with a description of what they did and how much BSQ they want in return. Then, stakeholders (who are other contributors, traders, and anyone else with BSQ) vote for/against the request. If the request is approved, the contributor is issued new BSQ in the amount they requested and '''BSQ supply is increased'''.

===Where does new BSQ actually come from?===
Recall that a BSQ token is merely coloured bitcoin. When a contributor makes their compensation request in the DAO, they must also include the tiny amount of bitcoin to be 'coloured' as BSQ ([[Bisq_DAO_technical_overview|the spec]] requires 100 satoshis). So if a contributor requests 1,000 BSQ, they will need to include 100 * 1,000 = 100,000 satoshis with their compensation request—just about 10 USD at a rate of 10,000 USD/BTC.

If their request is approved, those satoshis are 'colored' and recognized as 1,000 valid BSQ tokens on Bisq. Assuming a BSQ market value of 1 USD (exact value will fluctuate), the contributor will have been granted 1,000 USD worth of BSQ for a negligible cost of 10 USD.

===Traders consume, burning BSQ===
Then, a [[trader]] looking for lower trading fees can buy those BSQ tokens from a contributor. When they buy BSQ tokens for BTC, the contributor is paid for their work, and the value transfer from producer to consumer is complete! When a trader pays trading fees with BSQ, those BSQ tokens are burned or "decoloured" and '''BSQ supply is decreased'''. This process of creating and destroying BSQ tokens enables a sort of monetary policy controlled by Bisq stakeholders and traders.

In this way, there is no need for a central entity to collect and distribute revenue: the BSQ token enables a transfer of value from producer to consumer without any single entity controlling any aspect of the decision-making or distribution process.

* The Bisq DAO does not require traders to use BSQ for trading fees. They’re free to pay trading fees directly with BTC, but they will pay higher rates than if they bought BSQ with BTC and paid with BSQ instead.

====Note on BTC revenues====
In the past, before the Bisq DAO launch and before the integration of Bisq’s new trade protocol, trading fees were only collected in BTC and only went to arbitrators. There was no mechanism to distribute them to other contributors. The DAO solves this distribution problem with BSQ through the process outlined above.

But since traders can still pay trading fees with BTC, where do those BTC fees go?

BTC fees go to a bitcoin "donation" address held by a [[Donation_Address_Holder|bonded contributor]], who uses the BTC to buy BSQ on a regular basis to distribute the BTC fees to stakeholders, and the BSQ obtained [https://github.com/bisq-network/proposals/issues/55 is burned].

==Determine strategy==
Another point of centralization in traditional organizations is with strategy. How can a project determine strategy without some form of designated leadership: an executive, manager, or leader to give direction and allocate resources?

The Bisq DAO beats this tradition with collective decision-making on strategy and other matters through '''weighted voting''' based on BSQ stake.

Here’s how it works: any [[stakeholder]] can make a proposal in the DAO. It can be anything: a change in a [[DOA_PARAM|trading parameter]], a new bonded [[Category:Roles|role]], or even something more generic like an adjustment of the overall project strategy. [[Stakeholders]] vote on the proposal, and their voting weight is based on BSQ stake, through a combination of two metrics:
* amount of BSQ committed to a particular vote
* amount of BSQ earned over time through contributions

Taking both metrics into account discourages deep-pocketed whales from suddenly seizing control of the project, while still valuing dedicated stakeholders with consistent contributions over time. It brings about a '''strict meritocracy''' in which people need to somehow buy in to the Bisq project in order to take part in its governance, and the more significant their stake, the stronger their voice.

In this way, there is no need to rely on a single leadership team for direction: the community collectively manages itself.

==Ensure honesty in high-trust roles==
Despite the Bisq project’s attempts to resist concentrating control as much as possible, it’s impossible to avoid in some places. Domain name owners, social account admins, mediators, various node operators: these are all roles that must exist, but necessarily retain significant control and require a high degree of trust.

Part of the benefit of a centralized team of thoroughly-vetted people reliant on a paycheck, as is the case in most companies, is that the risk of trusting people with significant responsibility is lower: they have a lot to lose if the company finds they have violated their integrity and engaged in foul play.

This dynamic can be reproduced—at least partly—in a project without a central authority through bonding. The concept is simple enough: create skin in the game. Require that a person interested in taking on a high-trust role post a [[bond]] that’s high enough to discourage them from engaging in foul play.

But what happens if that person goes rogue? In a project without central authority, who decides when they’ve crossed the line, and what their fate should be?

As with strategy and compensation, the community decides through voting. Anyone who suspects foul play can make a case for confiscating a bond with a new proposal, and stakeholders vote to determine an outcome.

* Confiscating a bond is a harsh penalty which should not be taken lightly. Therefore, the Bisq DAO makes confiscation proposals especially hard to approve: they require a quorum of at least 200,000 BSQ and 85% acceptance to pass (instead of the typical >50%).
In this way, the risk that people in high-trust roles misbehave is minimized, and the community has access to a responsible mechanism for handling such a scenario in cases that warrant it.

=Learn more and stay in touch=
To learn more about the Bisq DAO, please see:
* The [[Category:DAO| DAO Category]]
* Bisq [[DAO user reference]], a doc which offers practical details on the workings of the DAO, along with high-level technical details.
* Bisq [[DAO technical overview]], along with technical details of BSQ tokens, this doc shows example transactions for several DAO functions.
* [[Phase Zero: A plan for bootstrapping the Bisq DAO]], a doc which offers a more comprehensive overview of Bisq and the Bisq DAO.
* [https://www.youtube.com/playlist?list=PLFH5SztL5cYOLdYJj3nQ6-DekbjMTVhCS Bisq DAO Basics], a YouTube video series that covers foundational concepts underlying the DAO such as bitcoin transactions, coloured coins, etc.

Feel free to get in touch with us on [https://twitter.com/bisq_network Twitter], [[Keybase]], or [https://bisq.community/ the forum].

= User Guides =
* [[User Guide: Bisq DAO for Traders]] — Use BSQ to get lower trading fees and compensate contributors
* [[User Guide: Bisq DAO for Contributors]] — Govern Bisq through the DAO by making proposals and voting

[[Category:DAO]]

File:Bisq-dao-data-model.png

2020-04-27T12:03:11Z

HunterNyan:

Bisq-dao-data-model

BSQ

2020-04-27T11:58:34Z

HunterNyan: More About BSQ

BSQ or BSQ tokens are a core function of the Bisq DAO.

=BSQ Token=
A BSQ token is a '''coloured coin''' on the Bitcoin blockchain. More plainly, a BSQ token is merely a few satoshis with some additional properties that identify it as BSQ in Bisq software. Outside Bisq, a BSQ token just looks like a few satoshis. But on Bisq, the additional properties have the following results:

* the satoshis take on the market value of a BSQ token
* the owner of the satoshis is endowed with power to participate in various Bisq governance functions

See it for yourself: [https://blockstream.info/tx/0243f99c848de4f53cb29157d10bf1cdbfcf4219f84e9997dd3cac9244ab7242/ here’s a BSQ transaction on an ordinary block explorer], and here’s [https://explorer.bisq.network/tx.html?tx=0243f99c848de4f53cb29157d10bf1cdbfcf4219f84e9997dd3cac9244ab7242 that same transaction on a BSQ block explorer].

The value of a BSQ token is determined by the market as stakeholders buy and sell tokens to perform various functions in the DAO. Because BSQ tokens are only recognized by Bisq software, BSQ trading can only happen in Bisq software.

* The BSQ token is not associated with any kind of initial coin offering (ICO) or capital-raising initiative. It’s merely a tool to decentralize the governance of the already-functional Bisq exchange service. As of December 2018, Bisq has facilitated over 19,000 trades without major incident since it went into production in April 2016.

You can learn more about coloured coins [https://www.youtube.com/watch?v=68_DU1c0Cac here in this interview] or [https://youtube.com/watch?v=xQTNigsrlO4 here]. Technical details of BSQ tokens are available [[Bisq_DAO_technical_overview|here]].

=More About BSQ=

A single BSQ token is denominated as 100 satoshis (i.e., it’s represented on the Bitcoin blockchain as 0.00000100 BTC). This bitcoin is 'coloured' with additional properties that allow the Bisq software to recognize it as BSQ.

BSQ can only be created in one of two ways:
* through the genesis distribution (detailed below)
* through an issuance transaction (compensation request or reimbursement request)

While BSQ is just bitcoin, it should only be stored in a Bisq wallet.

==Warning==
Please do not try to send BSQ to a non-Bisq wallet, or to otherwise create your own BSQ transactions. The rules to form a valid BSQ transaction are rather complex, and even the slightest error can result in invalid BSQ. Even the [[DAO_technical_overview|technical overview]] does not cover every single detail—the only complete reference is the source code. Also note that future code changes may break custom transactions or implementations. Bisq will NOT provide support for any such cases.
==BSQ Wallet==
BSQ is stored in a Bitcoin wallet, but the Bisq software takes several measures to keep BSQ and BTC separate to prevent mixing the two by accident. On disk, BTC and BSQ wallets are stored in separate files. In the Bisq interface, BSQ wallets are prefixed with a 'B' to prevent users from mistakenly using BSQ as BTC.

As an additional protection measure, Bisq wallets use a special BIP44 derivation path that other wallets won’t understand.

For user convenience, the built-in Bisq wallets for BTC and BSQ share the same seed.

More details are in the [[DAO_technical_overview|technical overview]].

[[Category:DAO]]