https://bisq.wiki/api.php?action=feedcontributions&feedformat=atom&user=Flix21 2026-05-08T19:41:28Z User contributions MediaWiki 1.34.0 https://bisq.wiki/index.php?title=How_to_do_arbitrage_on_Bisq&diff=4089 2025-12-04T12:50:49Z

<p>Flix21: /* Payment Method Arbitrage */</p> <hr /> <div>'''Arbitrage''' is the practice of simultaneously buying and selling an asset in different markets (or in different forms within the same market) to profit from a temporary price difference. In inefficient or less liquid markets, like many peer-to-peer environments, arbitrage opportunities can arise more frequently.<br /> <br /> [[How to be a market maker on Bisq|Arbitrageurs]] play a necessary role by taking advantage of these inefficiencies. In doing so, they not only profit but also help improve market liquidity and price discovery, making the market more efficient for everyone. Bisq currently provides many arbitrage opportunities.<br /> <br /> {{Admonition_Note|'''Version Context:''' The examples and considerations on this page primarily relate to arbitrage involving the classic '''[[Bisq 1|Bisq v1]]''' trading protocol. Arbitrage mechanics may differ significantly with the newer '''[[Bisq 2|Bisq Easy]]''' protocol (detailed on the [[Bisq 2]] page), which is not the focus of this guide.}}<br /> <br /> {{Admonition_Warn|'''Disclaimer:''' The price examples below are purely illustrative using hypothetical market conditions (approx. €80,000-€90,000 BTC/EUR) and plausible spreads. Real prices and spreads fluctuate constantly. Successful arbitrage requires accounting for all fees (trading, mining, payment method) and risks.}}<br /> <br /> __TOC__<br /> <br /> == Types of Arbitrage on Bisq ==<br /> <br /> You can perform two main types of arbitrage involving Bisq:<br /> <br /> === Inter-Exchange Arbitrage ===<br /> <br /> This involves finding price differences between Bisq and another exchange or market (Market X).<br /> <br /> '''Example:'''<br /> # You observe that the lowest price to '''SELL''' Bitcoin on Bisq's EUR/BTC market is currently '''€86,000'''.<br /> # Simultaneously, you find you can '''BUY''' Bitcoin on Market X (e.g., a centralized exchange) for '''€85,000'''.<br /> # You execute both trades at roughly the same time: '''Buy''' 1 BTC on Market X for €85,000 and '''Sell''' 1 BTC on Bisq for €86,000.<br /> # Assuming successful execution, this yields a potential profit of '''€1000''' per BTC, '''before''' accounting for any fees (trading, withdrawal, mining, payment method).<br /> <br /> (The reverse is also possible: buying cheaper on Bisq and selling higher elsewhere).<br /> <br /> === Intra-Exchange Arbitrage ===<br /> <br /> This involves exploiting price differences *within* the Bisq platform itself. This can happen between different currency markets or different payment methods within the same currency market.<br /> <br /> ==== Cross-Currency Arbitrage ====<br /> <br /> If the implied cross-rate between two fiat currencies (e.g., USD and EUR) differs from the prevailing market rate, an opportunity might exist.<br /> <br /> '''Example:'''<br /> # You notice the relative price in Bisq's USD/BTC market (e.g., equivalent to €86,000) is higher than in Bisq's EUR/BTC market (e.g., €85,000).<br /> # You simultaneously '''SELL''' BTC for USD (at the higher relative price) and '''BUY''' BTC for EUR (at the lower relative price) on Bisq.<br /> # If done correctly with sufficient volume, you can lock in a profit based on the temporary price discrepancy between the two Bisq markets (factoring in fees and the actual EUR/USD exchange rate).<br /> # Repeat as long as the profitable spread exists.<br /> <br /> ==== Payment Method Arbitrage ====<br /> <br /> Different payment methods within the same currency market (e.g., EUR) might have different prices due to varying user preferences, risks, or settlement times associated with those methods.<br /> <br /> '''Example:'''<br /> # You see offers available to '''BUY''' Bitcoin using [[SEPA]] priced relatively low (e.g., at €85,000).<br /> # At the same time, you see offers available to '''SELL''' Bitcoin receiving payment via Revolut priced higher (e.g., at €86,000).<br /> # You simultaneously execute both: '''BUY''' 1 BTC using [[SEPA]] for €85,000 and '''SELL''' 1 BTC receiving Revolut for €86,000.<br /> # This yields a potential profit of '''€1000''' per BTC arbitraged between the two payment methods on Bisq, '''before''' accounting for fees.<br /> # Repeat as long as the profitable spread exists.<br /> <br /> == Risks and Considerations ==<br /> <br /> While arbitrage aims to be low-risk by locking in profits from existing price differences, several practical factors introduce risk and complexity, especially on a P2P platform like Bisq:<br /> <br /> * '''Execution Risk:''' Prices can change quickly. Delay in executing one leg of the arbitrage (e.g., your external market buy fills but your Bisq sell offer gets taken by someone else before you can place it, or vice-versa) can erase the profit or lead to a loss. Getting both sides filled simultaneously at the desired prices can be challenging.<br /> * '''Fees:''' Remember to account for all fees:<br /> * Bisq [[Trading fees|trading fees]] (maker/taker, paid in BTC or BSQ).<br /> * Bitcoin [[mining fees]] (for deposit and payout transactions in Bisq v1).<br /> * Fees associated with the specific [[Payment methods|payment methods]] used (both on Bisq and external exchanges).<br /> * Fees on the external exchange (Market X).<br /> * '''Capital Requirements:''' You need sufficient capital available on both platforms/payment methods simultaneously to execute both legs of the trade (BTC and/or fiat).<br /> * '''Counterparty Risk (Bisq v1):''' While [[Security deposit|security deposits]] mitigate risk, trades can still go to [[Dispute_Resolution_in_Bisq_1|dispute resolution]], potentially tying up your funds (including deposits) for some time. Ensure you understand the risks associated with the specific payment methods and trade protocol.<br /> * '''Settlement Times:''' Fiat payment methods have varying settlement times. An arbitrage might require managing cash flow across methods that settle at different speeds.<br /> <br /> Successful arbitrage requires careful calculation, quick execution, and a good understanding of the platforms and payment methods involved.<br /> <br /> *For more short guides see [[Howto]]. You can also find support on '''[https://bisq.chat Matrix]'''.<br /> <br /> [[Category:Guides]]<br /> [[Category:Trading]]</div>

Flix21 https://bisq.wiki/index.php?title=How_to_do_arbitrage_on_Bisq&diff=4088 2025-12-04T12:48:36Z

<p>Flix21: /* Inter-Exchange Arbitrage */</p> <hr /> <div>'''Arbitrage''' is the practice of simultaneously buying and selling an asset in different markets (or in different forms within the same market) to profit from a temporary price difference. In inefficient or less liquid markets, like many peer-to-peer environments, arbitrage opportunities can arise more frequently.<br /> <br /> [[How to be a market maker on Bisq|Arbitrageurs]] play a necessary role by taking advantage of these inefficiencies. In doing so, they not only profit but also help improve market liquidity and price discovery, making the market more efficient for everyone. Bisq currently provides many arbitrage opportunities.<br /> <br /> {{Admonition_Note|'''Version Context:''' The examples and considerations on this page primarily relate to arbitrage involving the classic '''[[Bisq 1|Bisq v1]]''' trading protocol. Arbitrage mechanics may differ significantly with the newer '''[[Bisq 2|Bisq Easy]]''' protocol (detailed on the [[Bisq 2]] page), which is not the focus of this guide.}}<br /> <br /> {{Admonition_Warn|'''Disclaimer:''' The price examples below are purely illustrative using hypothetical market conditions (approx. €80,000-€90,000 BTC/EUR) and plausible spreads. Real prices and spreads fluctuate constantly. Successful arbitrage requires accounting for all fees (trading, mining, payment method) and risks.}}<br /> <br /> __TOC__<br /> <br /> == Types of Arbitrage on Bisq ==<br /> <br /> You can perform two main types of arbitrage involving Bisq:<br /> <br /> === Inter-Exchange Arbitrage ===<br /> <br /> This involves finding price differences between Bisq and another exchange or market (Market X).<br /> <br /> '''Example:'''<br /> # You observe that the lowest price to '''SELL''' Bitcoin on Bisq's EUR/BTC market is currently '''€86,000'''.<br /> # Simultaneously, you find you can '''BUY''' Bitcoin on Market X (e.g., a centralized exchange) for '''€85,000'''.<br /> # You execute both trades at roughly the same time: '''Buy''' 1 BTC on Market X for €85,000 and '''Sell''' 1 BTC on Bisq for €86,000.<br /> # Assuming successful execution, this yields a potential profit of '''€1000''' per BTC, '''before''' accounting for any fees (trading, withdrawal, mining, payment method).<br /> <br /> (The reverse is also possible: buying cheaper on Bisq and selling higher elsewhere).<br /> <br /> === Intra-Exchange Arbitrage ===<br /> <br /> This involves exploiting price differences *within* the Bisq platform itself. This can happen between different currency markets or different payment methods within the same currency market.<br /> <br /> ==== Cross-Currency Arbitrage ====<br /> <br /> If the implied cross-rate between two fiat currencies (e.g., USD and EUR) differs from the prevailing market rate, an opportunity might exist.<br /> <br /> '''Example:'''<br /> # You notice the relative price in Bisq's USD/BTC market (e.g., equivalent to €86,000) is higher than in Bisq's EUR/BTC market (e.g., €85,000).<br /> # You simultaneously '''SELL''' BTC for USD (at the higher relative price) and '''BUY''' BTC for EUR (at the lower relative price) on Bisq.<br /> # If done correctly with sufficient volume, you can lock in a profit based on the temporary price discrepancy between the two Bisq markets (factoring in fees and the actual EUR/USD exchange rate).<br /> # Repeat as long as the profitable spread exists.<br /> <br /> ==== Payment Method Arbitrage ====<br /> <br /> Different payment methods within the same currency market (e.g., EUR) might have different prices due to varying user preferences, risks, or settlement times associated with those methods.<br /> <br /> '''Example:'''<br /> # You see offers available to '''BUY''' Bitcoin using [[SEPA]] priced relatively low (e.g., at €85,200).<br /> # At the same time, you see offers available to '''SELL''' Bitcoin receiving payment via Revolut priced higher (e.g., at €85,800).<br /> # You simultaneously execute both: '''BUY''' 1 BTC using [[SEPA]] for €85,200 and '''SELL''' 1 BTC receiving Revolut for €85,800.<br /> # This yields a potential profit of '''€600''' per BTC arbitraged between the two payment methods on Bisq, '''before''' accounting for fees.<br /> # Repeat as long as the profitable spread exists.<br /> <br /> == Risks and Considerations ==<br /> <br /> While arbitrage aims to be low-risk by locking in profits from existing price differences, several practical factors introduce risk and complexity, especially on a P2P platform like Bisq:<br /> <br /> * '''Execution Risk:''' Prices can change quickly. Delay in executing one leg of the arbitrage (e.g., your external market buy fills but your Bisq sell offer gets taken by someone else before you can place it, or vice-versa) can erase the profit or lead to a loss. Getting both sides filled simultaneously at the desired prices can be challenging.<br /> * '''Fees:''' Remember to account for all fees:<br /> * Bisq [[Trading fees|trading fees]] (maker/taker, paid in BTC or BSQ).<br /> * Bitcoin [[mining fees]] (for deposit and payout transactions in Bisq v1).<br /> * Fees associated with the specific [[Payment methods|payment methods]] used (both on Bisq and external exchanges).<br /> * Fees on the external exchange (Market X).<br /> * '''Capital Requirements:''' You need sufficient capital available on both platforms/payment methods simultaneously to execute both legs of the trade (BTC and/or fiat).<br /> * '''Counterparty Risk (Bisq v1):''' While [[Security deposit|security deposits]] mitigate risk, trades can still go to [[Dispute_Resolution_in_Bisq_1|dispute resolution]], potentially tying up your funds (including deposits) for some time. Ensure you understand the risks associated with the specific payment methods and trade protocol.<br /> * '''Settlement Times:''' Fiat payment methods have varying settlement times. An arbitrage might require managing cash flow across methods that settle at different speeds.<br /> <br /> Successful arbitrage requires careful calculation, quick execution, and a good understanding of the platforms and payment methods involved.<br /> <br /> *For more short guides see [[Howto]]. You can also find support on '''[https://bisq.chat Matrix]'''.<br /> <br /> [[Category:Guides]]<br /> [[Category:Trading]]</div>

Flix21 https://bisq.wiki/index.php?title=How_to_do_arbitrage_on_Bisq&diff=4087 2025-12-04T12:47:51Z

<p>Flix21: /* Inter-Exchange Arbitrage */</p> <hr /> <div>'''Arbitrage''' is the practice of simultaneously buying and selling an asset in different markets (or in different forms within the same market) to profit from a temporary price difference. In inefficient or less liquid markets, like many peer-to-peer environments, arbitrage opportunities can arise more frequently.<br /> <br /> [[How to be a market maker on Bisq|Arbitrageurs]] play a necessary role by taking advantage of these inefficiencies. In doing so, they not only profit but also help improve market liquidity and price discovery, making the market more efficient for everyone. Bisq currently provides many arbitrage opportunities.<br /> <br /> {{Admonition_Note|'''Version Context:''' The examples and considerations on this page primarily relate to arbitrage involving the classic '''[[Bisq 1|Bisq v1]]''' trading protocol. Arbitrage mechanics may differ significantly with the newer '''[[Bisq 2|Bisq Easy]]''' protocol (detailed on the [[Bisq 2]] page), which is not the focus of this guide.}}<br /> <br /> {{Admonition_Warn|'''Disclaimer:''' The price examples below are purely illustrative using hypothetical market conditions (approx. €80,000-€90,000 BTC/EUR) and plausible spreads. Real prices and spreads fluctuate constantly. Successful arbitrage requires accounting for all fees (trading, mining, payment method) and risks.}}<br /> <br /> __TOC__<br /> <br /> == Types of Arbitrage on Bisq ==<br /> <br /> You can perform two main types of arbitrage involving Bisq:<br /> <br /> === Inter-Exchange Arbitrage ===<br /> <br /> This involves finding price differences between Bisq and another exchange or market (Market X).<br /> <br /> '''Example:'''<br /> # You observe that the lowest price to '''SELL''' Bitcoin on Bisq's EUR/BTC market is currently '''€85,500'''.<br /> # Simultaneously, you find you can '''BUY''' Bitcoin on Market X (e.g., a centralized exchange) for '''€85,000'''.<br /> # You execute both trades at roughly the same time: '''Buy''' 1 BTC on Market X for €85,000 and '''Sell''' 1 BTC on Bisq for €85,500.<br /> # Assuming successful execution, this yields a potential profit of '''€500''' per BTC, '''before''' accounting for any fees (trading, withdrawal, mining, payment method).<br /> <br /> (The reverse is also possible: buying cheaper on Bisq and selling higher elsewhere).<br /> <br /> === Intra-Exchange Arbitrage ===<br /> <br /> This involves exploiting price differences *within* the Bisq platform itself. This can happen between different currency markets or different payment methods within the same currency market.<br /> <br /> ==== Cross-Currency Arbitrage ====<br /> <br /> If the implied cross-rate between two fiat currencies (e.g., USD and EUR) differs from the prevailing market rate, an opportunity might exist.<br /> <br /> '''Example:'''<br /> # You notice the relative price in Bisq's USD/BTC market (e.g., equivalent to €86,000) is higher than in Bisq's EUR/BTC market (e.g., €85,000).<br /> # You simultaneously '''SELL''' BTC for USD (at the higher relative price) and '''BUY''' BTC for EUR (at the lower relative price) on Bisq.<br /> # If done correctly with sufficient volume, you can lock in a profit based on the temporary price discrepancy between the two Bisq markets (factoring in fees and the actual EUR/USD exchange rate).<br /> # Repeat as long as the profitable spread exists.<br /> <br /> ==== Payment Method Arbitrage ====<br /> <br /> Different payment methods within the same currency market (e.g., EUR) might have different prices due to varying user preferences, risks, or settlement times associated with those methods.<br /> <br /> '''Example:'''<br /> # You see offers available to '''BUY''' Bitcoin using [[SEPA]] priced relatively low (e.g., at €85,200).<br /> # At the same time, you see offers available to '''SELL''' Bitcoin receiving payment via Revolut priced higher (e.g., at €85,800).<br /> # You simultaneously execute both: '''BUY''' 1 BTC using [[SEPA]] for €85,200 and '''SELL''' 1 BTC receiving Revolut for €85,800.<br /> # This yields a potential profit of '''€600''' per BTC arbitraged between the two payment methods on Bisq, '''before''' accounting for fees.<br /> # Repeat as long as the profitable spread exists.<br /> <br /> == Risks and Considerations ==<br /> <br /> While arbitrage aims to be low-risk by locking in profits from existing price differences, several practical factors introduce risk and complexity, especially on a P2P platform like Bisq:<br /> <br /> * '''Execution Risk:''' Prices can change quickly. Delay in executing one leg of the arbitrage (e.g., your external market buy fills but your Bisq sell offer gets taken by someone else before you can place it, or vice-versa) can erase the profit or lead to a loss. Getting both sides filled simultaneously at the desired prices can be challenging.<br /> * '''Fees:''' Remember to account for all fees:<br /> * Bisq [[Trading fees|trading fees]] (maker/taker, paid in BTC or BSQ).<br /> * Bitcoin [[mining fees]] (for deposit and payout transactions in Bisq v1).<br /> * Fees associated with the specific [[Payment methods|payment methods]] used (both on Bisq and external exchanges).<br /> * Fees on the external exchange (Market X).<br /> * '''Capital Requirements:''' You need sufficient capital available on both platforms/payment methods simultaneously to execute both legs of the trade (BTC and/or fiat).<br /> * '''Counterparty Risk (Bisq v1):''' While [[Security deposit|security deposits]] mitigate risk, trades can still go to [[Dispute_Resolution_in_Bisq_1|dispute resolution]], potentially tying up your funds (including deposits) for some time. Ensure you understand the risks associated with the specific payment methods and trade protocol.<br /> * '''Settlement Times:''' Fiat payment methods have varying settlement times. An arbitrage might require managing cash flow across methods that settle at different speeds.<br /> <br /> Successful arbitrage requires careful calculation, quick execution, and a good understanding of the platforms and payment methods involved.<br /> <br /> *For more short guides see [[Howto]]. You can also find support on '''[https://bisq.chat Matrix]'''.<br /> <br /> [[Category:Guides]]<br /> [[Category:Trading]]</div>

Flix21 https://bisq.wiki/index.php?title=Bitcoin_holidays&diff=4027 2025-05-22T12:16:28Z

<p>Flix21: spend</p> <hr /> <div>This page highlights significant dates and events in the Bitcoin ecosystem, often observed by the community.<br /> <br /> * '''January 3rd''' - '''Proof of Keys Day:''' On this day, Bitcoiners are encouraged to practice and celebrate '''self-custody''' by withdrawing their bitcoin from third-party services, reinforcing Bitcoin as a sovereign '''store of value'''.<br /> <br /> * '''April 5th''' - '''Satoshi's Birthday:''' This date is recognized by some as Satoshi Nakamoto's listed birthday. Bitcoiners may honor Satoshi's creation by contributing to '''[[FOSS|Free and Open Source Software]]''' projects, including Bitcoin and Bisq.<br /> <br /> * '''May 22nd''' - '''Bitcoin Pizza Day:''' Commemorates the first documented real-world purchase using Bitcoin (for two pizzas in 2010). On this day, users celebrate Bitcoin as a '''medium of exchange''' by spending bitcoin.<br /> <br /> * '''August 15th''' - '''Nixon Shock Day:''' Marks the anniversary of the US decoupling the dollar from gold in 1971, highlighting the nature of fiat currency. This day serves to celebrate Bitcoin's fixed supply of 21 million units, emphasizing its role as a potential '''unit of account'''.<br /> <br /> * '''October 31st''' - '''White Paper Day:''' Celebrates the publication date of the [https://bitcoin.org/bitcoin.pdf Bitcoin White Paper] in 2008. It's a day to appreciate the foundational concepts and share knowledge about Bitcoin's design.<br /> <br /> * '''December 23rd''' - '''Decentralization Day:''' Commemorates the signing of the US Federal Reserve Act in 1913, contrasting centralized banking with Bitcoin's core principle. Users celebrate by strengthening the network's decentralization, often by '''[[Installing your own Bitcoin node|running a node]]'''.<br /> <br /> * '''The Halving''' - '''Halving Day:''' Occurring approximately every four years (every 210,000 blocks), this event reduces the block reward for miners by half. Halving Day celebrates the programmed scarcity of Bitcoin and the crucial role of '''Bitcoin miners''' in securing the network. Past halving dates include:<br /> ** November 28, 2012 (Block 210,000: 50 → 25 BTC reward)<br /> ** July 9, 2016 (Block 420,000: 25 → 12.5 BTC reward)<br /> ** May 11, 2020 (Block 630,000: 12.5 → 6.25 BTC reward)<br /> ** April 20, 2024 (Block 840,000: 6.25 → 3.125 BTC reward)</div>

Flix21 https://bisq.wiki/index.php?title=Bitcoin_units&diff=4026 2025-05-19T15:39:19Z

<p>Flix21: /* Bitcoin unit names */</p> <hr /> <div>==Bitcoin unit names==<br /> <br /> Some names have been proposed for different denominations of bitcoin for everyday use. One syllable words are preferred. Capital letter symbols for multiples of Bitcoin, lower case for fractions. Homage to the devs and other influences on the creation of Bitcoin.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |+ Bitcoin unit names and symbols<br /> |-<br /> ! Bitcoin !! Satoshis !! Unit name !! Symbol<br /> |-<br /> | 1,000,000.00000000 || 100,000,000,000,000 || Nakamoto || M<br /> |-<br /> | 100,000.00000000 || 10,000,000,000,000 || Fin || F<br /> |-<br /> | 10,000.00000000 || 1,000,000,000,000 || wei || W<br /> |-<br /> | 1,000.00000000 || 100,000,000,000 || thou || T<br /> |-<br /> | 100.00000000 || 10,000,000,000 || Cot || C<br /> |-<br /> | 10.00000000 || 1,000,000,000 || dex || X<br /> |-<br /> | 1.00000000 || 100,000,000 || Bitcoin || ₿<br /> |-<br /> | 0.10000000 || 10,000,000 || nick || n<br /> |-<br /> | 0.01000000 || 1,000,000 || cent || c<br /> |-<br /> | 0.00100000 || 100,000 || hal || h<br /> |-<br /> | 0.00010000 || 10,000 || den || d<br /> |-<br /> | 0.00001000 || 1,000 || mil || m<br /> |-<br /> | 0.00000100 || 100 || bit || b<br /> |-<br /> | 0.00000010 || 10 || ten || x<br /> |-<br /> | 0.00000001 || 1 || satoshi || s<br /> |-<br /> | 0.000000001000 || 0.1 || shi || ds<br /> |-<br /> | 0.000000000100 || 0.01 || back || cs<br /> |-<br /> | 0.000000000010 || 0.001 || millisat || ms<br /> |-<br /> | 0.000000000001 || 0.0001 || nak || ns<br /> |}</div>

Flix21 https://bisq.wiki/index.php?title=Bitcoin_units&diff=4025 2025-05-19T10:11:14Z

<p>Flix21: /* Bitcoin unit names */</p> <hr /> <div>==Bitcoin unit names==<br /> <br /> Some names have been proposed for different denominations of bitcoin for everyday use. One syllable words are preferred. Capital letter symbols for multiples of Bitcoin, lower case for fractions. Homage to the devs and other influences on the creation of Bitcoin.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |+ Caption text<br /> |-<br /> ! Bitcoin !! Satoshis !! Unit name !! Symbol<br /> |-<br /> | 1,000,000.00000000 || 100,000,000,000,000 || Nakamoto || M<br /> |-<br /> | 100,000.00000000 || 10,000,000,000,000 || Fin || F<br /> |-<br /> | 10,000.00000000 || 1,000,000,000,000 || wei || W<br /> |-<br /> | 1,000.00000000 || 100,000,000,000 || thou || T<br /> |-<br /> | 100.00000000 || 10,000,000,000 || Cot || C<br /> |-<br /> | 10.00000000 || 1,000,000,000 || dex || X<br /> |-<br /> | 1.00000000 || 100,000,000 || Bitcoin || ₿<br /> |-<br /> | 0.10000000 || 10,000,000 || nick || n<br /> |-<br /> | 0.01000000 || 1,000,000 || cent || c<br /> |-<br /> | 0.00100000 || 100,000 || hal || h<br /> |-<br /> | 0.00010000 || 10,000 || den || d<br /> |-<br /> | 0.00001000 || 1,000 || mil || m<br /> |-<br /> | 0.00000100 || 100 || bit || b<br /> |-<br /> | 0.00000010 || 10 || ten || x<br /> |-<br /> | 0.00000001 || 1 || satoshi || s<br /> |-<br /> | 0.000000001000 || 0.1 || shi || ds<br /> |-<br /> | 0.000000000100 || 0.01 || back || cs<br /> |-<br /> | 0.000000000010 || 0.001 || millisat || ms<br /> |-<br /> | 0.000000000001 || 0.0001 || nak || ns<br /> |}</div>

Flix21 https://bisq.wiki/index.php?title=Bitcoin_units&diff=4024 2025-05-19T10:10:56Z

<p>Flix21: /* Bitcoin unit names */</p> <hr /> <div>==Bitcoin unit names==<br /> <br /> Some names have been proposed for different denominations of bitcoin for everyday use. One syllable words are preferred. Capital letter symbols for multiples of Bitcoin, lower case for fractions. Homage to the devs and other influences on the creation of Bitcoin.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |+ Caption text<br /> |-<br /> ! Bitcoin !! Satoshis !! Unit name !! Symbol<br /> |-<br /> | 1,000,000.00000000 || 100,000,000,000,000 || Nakamoto || M<br /> |-<br /> | 100,000.00000000 || 10,000,000,000,000 || Fin || F<br /> |-<br /> | 10,000.00000000 || 1,000,000,000,000 || wei || W<br /> |-<br /> | 1,000.00000000 || 100,000,000,000 || thou || T<br /> |-<br /> | 100.00000000 || 10,000,000,000 || bot || B<br /> |-<br /> | 10.00000000 || 1,000,000,000 || dex || X<br /> |-<br /> | 1.00000000 || 100,000,000 || Bitcoin || ₿<br /> |-<br /> | 0.10000000 || 10,000,000 || nick || n<br /> |-<br /> | 0.01000000 || 1,000,000 || cent || c<br /> |-<br /> | 0.00100000 || 100,000 || hal || h<br /> |-<br /> | 0.00010000 || 10,000 || den || d<br /> |-<br /> | 0.00001000 || 1,000 || mil || m<br /> |-<br /> | 0.00000100 || 100 || bit || b<br /> |-<br /> | 0.00000010 || 10 || ten || x<br /> |-<br /> | 0.00000001 || 1 || satoshi || s<br /> |-<br /> | 0.000000001000 || 0.1 || shi || ds<br /> |-<br /> | 0.000000000100 || 0.01 || back || cs<br /> |-<br /> | 0.000000000010 || 0.001 || millisat || ms<br /> |-<br /> | 0.000000000001 || 0.0001 || nak || ns<br /> |}</div>

Flix21 https://bisq.wiki/index.php?title=Bitcoin_units&diff=4023 2025-05-19T10:00:51Z

<p>Flix21: /* Bitcoin unit names */</p> <hr /> <div>==Bitcoin unit names==<br /> <br /> Some names have been proposed for different denominations of bitcoin for everyday use. One syllable words are preferred. Capital letter symbols for multiples of Bitcoin, lower case for fractions. Homage to the devs and other influences on the creation of Bitcoin.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |+ Caption text<br /> |-<br /> ! Bitcoin !! Satoshis !! Unit name !! Symbol<br /> |-<br /> | 1,000,000.00000000 || 100,000,000,000,000 || Nakamoto || M<br /> |-<br /> | 100,000.00000000 || 10,000,000,000,000 || Fin || F<br /> |-<br /> | 10,000.00000000 || 1,000,000,000,000 || wei || W<br /> |-<br /> | 1,000.00000000 || 100,000,000,000 || thou || T<br /> |-<br /> | 100.00000000 || 10,000,000,000 || bot || B<br /> |-<br /> | 10.00000000 || 1,000,000,000 || dex || X<br /> |-<br /> | 1.00000000 || 100,000,000 || Bitcoin || BTC<br /> |-<br /> | 0.10000000 || 10,000,000 || nick || n<br /> |-<br /> | 0.01000000 || 1,000,000 || cent || c<br /> |-<br /> | 0.00100000 || 100,000 || hal || h<br /> |-<br /> | 0.00010000 || 10,000 || den || d<br /> |-<br /> | 0.00001000 || 1,000 || mil || m<br /> |-<br /> | 0.00000100 || 100 || bit || b<br /> |-<br /> | 0.00000010 || 10 || ten || x<br /> |-<br /> | 0.00000001 || 1 || satoshi || s<br /> |-<br /> | 0.000000001000 || 0.1 || shi || ds<br /> |-<br /> | 0.000000000100 || 0.01 || back || cs<br /> |-<br /> | 0.000000000010 || 0.001 || millisat || ms<br /> |-<br /> | 0.000000000001 || 0.0001 || nak || ns<br /> |}</div>

Flix21 https://bisq.wiki/index.php?title=Bitcoin_units&diff=4022 2025-05-19T09:58:25Z

<p>Flix21: /* Bitcoin units */</p> <hr /> <div>==Bitcoin unit names==<br /> <br /> Some names have been proposed for different denominations of bitcoin for everyday use. <br /> <br /> {| class=&quot;wikitable&quot;<br /> |+ Caption text<br /> |-<br /> ! Bitcoin !! Satoshis !! Unit name !! Symbol<br /> |-<br /> | 1,000,000.00000000 || 100,000,000,000,000 || Nakamoto || M<br /> |-<br /> | 100,000.00000000 || 10,000,000,000,000 || Fin || F<br /> |-<br /> | 10,000.00000000 || 1,000,000,000,000 || wei || W<br /> |-<br /> | 1,000.00000000 || 100,000,000,000 || thou || T<br /> |-<br /> | 100.00000000 || 10,000,000,000 || bot || B<br /> |-<br /> | 10.00000000 || 1,000,000,000 || dex || X<br /> |-<br /> | 1.00000000 || 100,000,000 || Bitcoin || BTC<br /> |-<br /> | 0.10000000 || 10,000,000 || nick || n<br /> |-<br /> | 0.01000000 || 1,000,000 || cent || c<br /> |-<br /> | 0.00100000 || 100,000 || hal || h<br /> |-<br /> | 0.00010000 || 10,000 || den || d<br /> |-<br /> | 0.00001000 || 1,000 || mil || m<br /> |-<br /> | 0.00000100 || 100 || bit || b<br /> |-<br /> | 0.00000010 || 10 || ten || x<br /> |-<br /> | 0.00000001 || 1 || satoshi || s<br /> |-<br /> | 0.000000001000 || 0.1 || shi || ds<br /> |-<br /> | 0.000000000100 || 0.01 || back || cs<br /> |-<br /> | 0.000000000010 || 0.001 || millisat || ms<br /> |-<br /> | 0.000000000001 || 0.0001 || nak || ns<br /> |}</div>

Flix21 https://bisq.wiki/index.php?title=Bitcoin_units&diff=4021 2025-05-19T09:58:09Z

<p>Flix21: Created page with &quot;==Bitcoin units== Some names have been proposed for different denominations of bitcoin for everyday use. {| class=&quot;wikitable&quot; |+ Caption text |- ! Bitcoin !! Satoshis !! Un...&quot;</p> <hr /> <div>==Bitcoin units==<br /> <br /> Some names have been proposed for different denominations of bitcoin for everyday use. <br /> <br /> {| class=&quot;wikitable&quot;<br /> |+ Caption text<br /> |-<br /> ! Bitcoin !! Satoshis !! Unit name !! Symbol<br /> |-<br /> | 1,000,000.00000000 || 100,000,000,000,000 || Nakamoto || M<br /> |-<br /> | 100,000.00000000 || 10,000,000,000,000 || Fin || F<br /> |-<br /> | 10,000.00000000 || 1,000,000,000,000 || wei || W<br /> |-<br /> | 1,000.00000000 || 100,000,000,000 || thou || T<br /> |-<br /> | 100.00000000 || 10,000,000,000 || bot || B<br /> |-<br /> | 10.00000000 || 1,000,000,000 || dex || X<br /> |-<br /> | 1.00000000 || 100,000,000 || Bitcoin || BTC<br /> |-<br /> | 0.10000000 || 10,000,000 || nick || n<br /> |-<br /> | 0.01000000 || 1,000,000 || cent || c<br /> |-<br /> | 0.00100000 || 100,000 || hal || h<br /> |-<br /> | 0.00010000 || 10,000 || den || d<br /> |-<br /> | 0.00001000 || 1,000 || mil || m<br /> |-<br /> | 0.00000100 || 100 || bit || b<br /> |-<br /> | 0.00000010 || 10 || ten || x<br /> |-<br /> | 0.00000001 || 1 || satoshi || s<br /> |-<br /> | 0.000000001000 || 0.1 || shi || ds<br /> |-<br /> | 0.000000000100 || 0.01 || back || cs<br /> |-<br /> | 0.000000000010 || 0.001 || millisat || ms<br /> |-<br /> | 0.000000000001 || 0.0001 || nak || ns<br /> |}</div>

Flix21 https://bisq.wiki/index.php?title=CBDC&diff=3655 2024-07-15T18:44:16Z

<p>Flix21: </p> <hr /> <div>CBDC (Central Bank Digital Currency) is the final and most insidious form of [[fiat]] money, since as programmable money it allows a much higher degree of control, including geofencing, time limits, restrictions on saving, blacklisting, censorship, etc. It can potentially lead to [[ubiquitous law enforcement]] and facilitate social credit systems.<br /> <br /> == CBDC programs around the world ==<br /> A large number of governments around the world are working on developing a CBDC. 3 have launched. 36 are in the pilot stage and 30 are in development. These are some of the most relevant.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |+ CBDC<br /> |-<br /> ! Country !! Stage !! Tech !! FOSS !! Privacy !! Transparency !! Issuance Limit !! Users (M) !! Name !! Dev. co !! DB leak !! Hacked<br /> |-<br /> | China || Pilot || . || . || . || . || . || 250 || e-CNY || . || . || <br /> |-<br /> | Nigeria || Live || Fabric || NO || . || . || . || 12 || e-Naira || Bitt Inc || . ||<br /> |-<br /> | Jamaica || Live || NZIA || NO || . || . || . || 0.120 || Sand Dollar || NZIA || . ||<br /> |-<br /> | Bahamas || Live || . || . || . || . || . || . || . || . || . ||<br /> |-<br /> | USA || Development || . || . || . || . || . || . || . || . || . ||<br /> |-<br /> | EU || Development || . || . || . || . || . || . || Digital euro || . || . ||<br /> |-<br /> | India || Pilot || . || . || . || . || . || 5 || Digital Rupee || . || . ||<br /> |-<br /> | UK || Development || . || . || . || . || . || . || . || . || . ||<br /> |-<br /> | Brazil || Pilot || . || . || . || . || . || . || Drex || . || . ||<br /> |-<br /> | Russia || Pilot || . || . || . || . || . || . || . || . || . ||<br /> |-<br /> | Ukraine || Pilot || Stellar || . || . || . || . || . || . || Bitt Inc || . ||<br /> |}<br /> <br /> == External links ==<br /> <br /> *CBDCtracker [https://www.atlanticcouncil.org/cbdctracker/ cbdctracker] lets you see how CBDC implementation around the world is advancing.<br /> *HRF [https://cbdctracker.hrf.org/home HRF CBDCtracker]. The Human Rights Foundation is also keeping a critical eye on CBDC progress around the world.</div>

Flix21 https://bisq.wiki/index.php?title=CBDC&diff=3654 2024-07-15T18:43:58Z

<p>Flix21: </p> <hr /> <div>CBDC (Central Bank Digital Currency) is the final and most insidious form of [[fiat]] money, since as programmable money it allows a much higher degree of control, including geofencing, time limits, restrictions on saving, blacklisting, censorship, etc. It can potentially lead to [[ubiquitous law enforcement]] and facilitate social credit systems.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |+ CBDC<br /> |-<br /> ! Country !! Stage !! Tech !! FOSS !! Privacy !! Transparency !! Issuance Limit !! Users (M) !! Name !! Dev. co !! DB leak !! Hacked<br /> |-<br /> | China || Pilot || . || . || . || . || . || 250 || e-CNY || . || . || <br /> |-<br /> | Nigeria || Live || Fabric || NO || . || . || . || 12 || e-Naira || Bitt Inc || . ||<br /> |-<br /> | Jamaica || Live || NZIA || NO || . || . || . || 0.120 || Sand Dollar || NZIA || . ||<br /> |-<br /> | Bahamas || Live || . || . || . || . || . || . || . || . || . ||<br /> |-<br /> | USA || Development || . || . || . || . || . || . || . || . || . ||<br /> |-<br /> | EU || Development || . || . || . || . || . || . || Digital euro || . || . ||<br /> |-<br /> | India || Pilot || . || . || . || . || . || 5 || Digital Rupee || . || . ||<br /> |-<br /> | UK || Development || . || . || . || . || . || . || . || . || . ||<br /> |-<br /> | Brazil || Pilot || . || . || . || . || . || . || Drex || . || . ||<br /> |-<br /> | Russia || Pilot || . || . || . || . || . || . || . || . || . ||<br /> |-<br /> | Ukraine || Pilot || Stellar || . || . || . || . || . || . || Bitt Inc || . ||<br /> |}<br /> <br /> == External links ==<br /> <br /> *CBDCtracker [https://www.atlanticcouncil.org/cbdctracker/ cbdctracker] lets you see how CBDC implementation around the world is advancing.<br /> *HRF [https://cbdctracker.hrf.org/home HRF CBDCtracker]. The Human Rights Foundation is also keeping a critical eye on CBDC progress around the world.</div>

Flix21 https://bisq.wiki/index.php?title=CBDC&diff=3653 2024-07-15T18:43:26Z

<p>Flix21: /* External links */</p> <hr /> <div>CBDC (Central Bank Digital Currency) is the final and most insidious form of [[fiat]] money, since as programmable money it allows a much higher degree of control, including geofencing, time limits, restrictions on saving, blacklisting, censorship, etc. It can potentially lead to [[ubiquitous law enforcement]] and facilitate social credit systems.<br /> <br /> <br /> == External links ==<br /> <br /> *CBDCtracker [https://www.atlanticcouncil.org/cbdctracker/ cbdctracker] lets you see how CBDC implementation around the world is advancing.<br /> *HRF [https://cbdctracker.hrf.org/home HRF CBDCtracker]. The Human Rights Foundation is also keeping a critical eye on CBDC progress around the world.</div>

Flix21 https://bisq.wiki/index.php?title=Bitcoin_holidays&diff=3599 2024-05-22T10:53:04Z

<p>Flix21: </p> <hr /> <div>*'''January 3rd''' is [[Proof of keys day]]. On proof of keys day we exercise '''self-custody''' to celebrate Bitcoin as a '''store of value'''.<br /> *'''April 5''' is [[Satoshis birthday]]. On this day bitcoiners honour Satoshi by contributing to '''Free Open Source Software''' (FOSS).<br /> *'''May 22nd''' is [[Bitcoin pizza day]]. On pizza day we '''spend''' Bitcoin to celebrate Bitcoin as a '''medium of exchange'''.<br /> *'''August 15th''' is [[Nixon shock day]]. On this day we remember the birth of unrestrained fiat money, celebrate Bitcoin as '''unit of account''' with 21 million units.<br /> *'''October 31st''' 2008 the Bitcoin White Paper was published.<br /> *'''December 23rd''' is [[decentralisation day]]. We remember the creation of the Federal Reserve and celebrate decentralisation by '''running a node'''.<br /> *The '''Halving''' is every 4 years or every 210,000 blocks. On Halving day we celebrate Bitcoin '''miners'''.</div>

Flix21 https://bisq.wiki/index.php?title=Bitcoin_holidays&diff=3598 2024-05-22T09:56:22Z

<p>Flix21: Bitcoin holidays</p> <hr /> <div>*'''January 3rd''' is [[Proof of keys day]]. On proof of keys day we exercise '''self-custody''' to celebrate Bitcoin as a '''store of value'''.<br /> *'''April 5''' is [[Satoshis birthday]]. On this day bitcoiners honour Satoshi by contributing to '''Free Open Source Software''' (FOSS).<br /> *'''May 22nd''' is [[Bitcoin pizza day]]. On pizza day we '''spend''' Bitcoin to celebrate Bitcoin as a '''medium of exchange'''.<br /> *'''August 15th''' is [[Nixon shock day]]. On this day we remember the birth of unrestrained fiat money, celebrate Bitcoin as '''unit of account''' with 21 million units.<br /> *'''December 23rd''' is [[decentralisation day]]. We remember the creation of the Federal Reserve and celebrate decentralisation by '''running a node'''.<br /> *The '''Halving''' is every 4 years or every 210,000 blocks. On Halving day we celebrate Bitcoin '''miners'''.</div>

Flix21 https://bisq.wiki/index.php?title=Trade_Protocols&diff=3534 2024-03-17T17:54:09Z

<p>Flix21: /* Submarine Swaps */</p> <hr /> <div>[[Bisq 2]] will offer users the choice of multiple trade protocols.<br /> <br /> A trade protocol serves as the fundamental framework for trading Bitcoin in a secure way. Each trade protocol presents its own set of advantages and trade-offs including:<br /> <br /> * Trade fees<br /> * Mining fees<br /> * Security mechanisms<br /> * Dispute mechanisms<br /> * Security deposit requirements <br /> * Privacy benefits / trade-offs<br /> * Convenience<br /> <br /> Bisq 2 offers users the flexibility to select the optimal protocol aligning with their requirements and preferences.<br /> <br /> All trade protocols will be able to be accessed from the Bisq 2 application independently. Users will be able to switch between trade protocols for different trades should they wish.<br /> <br /> As of now, Bisq Easy stands as the sole implemented protocol, tailored for novice Bitcoin users and suitable for smaller trade amounts.<br /> <br /> == Bisq Easy ==<br /> <br /> Bisq Easy will be the first trade protocol for Bisq 2. It will be accessible on the launch of Bisq 2. It is an easy to use chat based trade protocol for buying and selling bitcoin for fiat. The security is based on reputation of the sellers.<br /> <br /> See here for more information about [[Bisq_Easy|Bisq Easy]].<br /> <br /> == Future Trade Protocols ==<br /> <br /> Bisq is planning on adding more trade protocols available on Bisq 2. Explore the upcoming trade protocols. Keep an eye out for updates if any of the upcoming protocols catch your interest.<br /> <br /> === Bisq Lightning ===<br /> <br /> Escrow based trade protocol on the Lightning network using multi-party computation cryptography.<br /> <br /> === Bisq Multisig ===<br /> <br /> Bisq 1 currently uses a 2-of-2 multisig as its main trade protocol. This involves the buyer and seller putting down a [[security deposit]] that is locked in a multisig until the trade completes. At some point this protocol will be moved over to Bisq 2.<br /> <br /> === BSQ swaps ===<br /> <br /> This allows users to swap from BSQ to BTC and vice versa via atomic swaps, instantaneously and secure.<br /> <br /> === Liquid Swaps ===<br /> <br /> Trade any Liquid based assets like USDT and BTC-L with an atomic swap on the Liquid network.<br /> <br /> === Monero Swaps ===<br /> <br /> Trade Bitcoin and Monero using an atomic cross chain swap.<br /> <br /> === Liquid Multisig ===<br /> <br /> This trade protocol will use the same trade protocol as the 2-of-2 multisig but it will replace Bitcoin (BTC) with Liquid Bitcoin (L-BTC). The advantage to this is fees will be lower, and users will get more privacy with their trades. The disadvantage is that users will not be trading native bitcoin so will have to be comfortable holding LBTC and consider the costs of converting BTC to LBTC and back again. <br /> <br /> === Submarine Swaps ===<br /> <br /> This trade protocol allows users to swap between Bitcoin on Lightning network to on-chain Bitcoin.<br /> <br /> === Stablecoin Swaps ===<br /> <br /> Atomic swaps between Bitcoin and USD stablecoin. Just the same as BSQ swaps, but with a Bitcoin coloured coin built on the same tech.<br /> <br /> === Multisig Options ===<br /> <br /> This trade protocol would allow the creation of P2P put and call options with the buyer and seller blocking BTC in a multisig on-chain transaction. 2 PSBT would be created sending the BTC to the buyer or seller depending on the result of a binary event. On expiry a blind oracle would trigger the correct transaction to be broadcast to the Bitcoin network.<br /> <br /> === Multisig open contracts===<br /> <br /> This trade protocol will allow user defined conditional payments. Any simple contract can be created by locking funds in a multisig 2-of-3 transaction with an arbitrator holding the third key and deciding if the condition was met in case of dispute. This is similar to the old Bisq 1 2-of-3 multisig model, but open to any type of contract than can be easily verified.<br /> <br /> == Adding Trade Protocols to Bisq 2 ==<br /> <br /> Trade protocols are designed to be modular so more trade protocols can be added in the future. Anyone with ideas for new trade protocols should join the discussion on [[Matrix_bisq.chat|Bisq's Matrix chat]].</div>

Flix21 https://bisq.wiki/index.php?title=Trade_Protocols&diff=3533 2024-03-17T17:32:39Z

<p>Flix21: /* Multisig Options */</p> <hr /> <div>[[Bisq 2]] will offer users the choice of multiple trade protocols.<br /> <br /> A trade protocol serves as the fundamental framework for trading Bitcoin in a secure way. Each trade protocol presents its own set of advantages and trade-offs including:<br /> <br /> * Trade fees<br /> * Mining fees<br /> * Security mechanisms<br /> * Dispute mechanisms<br /> * Security deposit requirements <br /> * Privacy benefits / trade-offs<br /> * Convenience<br /> <br /> Bisq 2 offers users the flexibility to select the optimal protocol aligning with their requirements and preferences.<br /> <br /> All trade protocols will be able to be accessed from the Bisq 2 application independently. Users will be able to switch between trade protocols for different trades should they wish.<br /> <br /> As of now, Bisq Easy stands as the sole implemented protocol, tailored for novice Bitcoin users and suitable for smaller trade amounts.<br /> <br /> == Bisq Easy ==<br /> <br /> Bisq Easy will be the first trade protocol for Bisq 2. It will be accessible on the launch of Bisq 2. It is an easy to use chat based trade protocol for buying and selling bitcoin for fiat. The security is based on reputation of the sellers.<br /> <br /> See here for more information about [[Bisq_Easy|Bisq Easy]].<br /> <br /> == Future Trade Protocols ==<br /> <br /> Bisq is planning on adding more trade protocols available on Bisq 2. Explore the upcoming trade protocols. Keep an eye out for updates if any of the upcoming protocols catch your interest.<br /> <br /> === Bisq Lightning ===<br /> <br /> Escrow based trade protocol on the Lightning network using multi-party computation cryptography.<br /> <br /> === Bisq Multisig ===<br /> <br /> Bisq 1 currently uses a 2-of-2 multisig as its main trade protocol. This involves the buyer and seller putting down a [[security deposit]] that is locked in a multisig until the trade completes. At some point this protocol will be moved over to Bisq 2.<br /> <br /> === BSQ swaps ===<br /> <br /> This allows users to swap from BSQ to BTC and vice versa via atomic swaps, instantaneously and secure.<br /> <br /> === Liquid Swaps ===<br /> <br /> Trade any Liquid based assets like USDT and BTC-L with an atomic swap on the Liquid network.<br /> <br /> === Monero Swaps ===<br /> <br /> Trade Bitcoin and Monero using an atomic cross chain swap.<br /> <br /> === Liquid Multisig ===<br /> <br /> This trade protocol will use the same trade protocol as the 2-of-2 multisig but it will replace Bitcoin (BTC) with Liquid Bitcoin (L-BTC). The advantage to this is fees will be lower, and users will get more privacy with their trades. The disadvantage is that users will not be trading native bitcoin so will have to be comfortable holding LBTC and consider the costs of converting BTC to LBTC and back again. <br /> <br /> === Submarine Swaps ===<br /> <br /> This trade protocol allows users to swap between Bitcoin on Lightning network to on-chain Bitcoin.<br /> <br /> === Multisig Options ===<br /> <br /> This trade protocol would allow the creation of P2P put and call options with the buyer and seller blocking BTC in a multisig on-chain transaction. 2 PSBT would be created sending the BTC to the buyer or seller depending on the result of a binary event. On expiry a blind oracle would trigger the correct transaction to be broadcast to the Bitcoin network.<br /> <br /> === Multisig open contracts===<br /> <br /> This trade protocol will allow user defined conditional payments. Any simple contract can be created by locking funds in a multisig 2-of-3 transaction with an arbitrator holding the third key and deciding if the condition was met in case of dispute. This is similar to the old Bisq 1 2-of-3 multisig model, but open to any type of contract than can be easily verified.<br /> <br /> == Adding Trade Protocols to Bisq 2 ==<br /> <br /> Trade protocols are designed to be modular so more trade protocols can be added in the future. Anyone with ideas for new trade protocols should join the discussion on [[Matrix_bisq.chat|Bisq's Matrix chat]].</div>

Flix21 https://bisq.wiki/index.php?title=Trade_Protocols&diff=3532 2024-03-17T17:14:20Z

<p>Flix21: /* Multisig Options */</p> <hr /> <div>[[Bisq 2]] will offer users the choice of multiple trade protocols.<br /> <br /> A trade protocol serves as the fundamental framework for trading Bitcoin in a secure way. Each trade protocol presents its own set of advantages and trade-offs including:<br /> <br /> * Trade fees<br /> * Mining fees<br /> * Security mechanisms<br /> * Dispute mechanisms<br /> * Security deposit requirements <br /> * Privacy benefits / trade-offs<br /> * Convenience<br /> <br /> Bisq 2 offers users the flexibility to select the optimal protocol aligning with their requirements and preferences.<br /> <br /> All trade protocols will be able to be accessed from the Bisq 2 application independently. Users will be able to switch between trade protocols for different trades should they wish.<br /> <br /> As of now, Bisq Easy stands as the sole implemented protocol, tailored for novice Bitcoin users and suitable for smaller trade amounts.<br /> <br /> == Bisq Easy ==<br /> <br /> Bisq Easy will be the first trade protocol for Bisq 2. It will be accessible on the launch of Bisq 2. It is an easy to use chat based trade protocol for buying and selling bitcoin for fiat. The security is based on reputation of the sellers.<br /> <br /> See here for more information about [[Bisq_Easy|Bisq Easy]].<br /> <br /> == Future Trade Protocols ==<br /> <br /> Bisq is planning on adding more trade protocols available on Bisq 2. Explore the upcoming trade protocols. Keep an eye out for updates if any of the upcoming protocols catch your interest.<br /> <br /> === Bisq Lightning ===<br /> <br /> Escrow based trade protocol on the Lightning network using multi-party computation cryptography.<br /> <br /> === Bisq Multisig ===<br /> <br /> Bisq 1 currently uses a 2-of-2 multisig as its main trade protocol. This involves the buyer and seller putting down a [[security deposit]] that is locked in a multisig until the trade completes. At some point this protocol will be moved over to Bisq 2.<br /> <br /> === BSQ swaps ===<br /> <br /> This allows users to swap from BSQ to BTC and vice versa via atomic swaps, instantaneously and secure.<br /> <br /> === Liquid Swaps ===<br /> <br /> Trade any Liquid based assets like USDT and BTC-L with an atomic swap on the Liquid network.<br /> <br /> === Monero Swaps ===<br /> <br /> Trade Bitcoin and Monero using an atomic cross chain swap.<br /> <br /> === Liquid Multisig ===<br /> <br /> This trade protocol will use the same trade protocol as the 2-of-2 multisig but it will replace Bitcoin (BTC) with Liquid Bitcoin (L-BTC). The advantage to this is fees will be lower, and users will get more privacy with their trades. The disadvantage is that users will not be trading native bitcoin so will have to be comfortable holding LBTC and consider the costs of converting BTC to LBTC and back again. <br /> <br /> === Submarine Swaps ===<br /> <br /> This trade protocol allows users to swap between Bitcoin on Lightning network to on-chain Bitcoin.<br /> <br /> === Multisig Options ===<br /> <br /> This trade protocol would allow the creation of P2P put and call options with the buyer and seller blocking BTC in a multisig on-chain transaction. 2 PSBT would be created sending the BTC to the buyer or seller depending on the result of a binary event. On expiry a blind oracle would trigger the correct transaction to be broadcast to the Bitcoin network.<br /> <br /> == Adding Trade Protocols to Bisq 2 ==<br /> <br /> Trade protocols are designed to be modular so more trade protocols can be added in the future. Anyone with ideas for new trade protocols should join the discussion on [[Matrix_bisq.chat|Bisq's Matrix chat]].</div>

Flix21 https://bisq.wiki/index.php?title=Trade_Protocols&diff=3531 2024-03-17T17:13:37Z

<p>Flix21: /* Submarine Swaps */</p> <hr /> <div>[[Bisq 2]] will offer users the choice of multiple trade protocols.<br /> <br /> A trade protocol serves as the fundamental framework for trading Bitcoin in a secure way. Each trade protocol presents its own set of advantages and trade-offs including:<br /> <br /> * Trade fees<br /> * Mining fees<br /> * Security mechanisms<br /> * Dispute mechanisms<br /> * Security deposit requirements <br /> * Privacy benefits / trade-offs<br /> * Convenience<br /> <br /> Bisq 2 offers users the flexibility to select the optimal protocol aligning with their requirements and preferences.<br /> <br /> All trade protocols will be able to be accessed from the Bisq 2 application independently. Users will be able to switch between trade protocols for different trades should they wish.<br /> <br /> As of now, Bisq Easy stands as the sole implemented protocol, tailored for novice Bitcoin users and suitable for smaller trade amounts.<br /> <br /> == Bisq Easy ==<br /> <br /> Bisq Easy will be the first trade protocol for Bisq 2. It will be accessible on the launch of Bisq 2. It is an easy to use chat based trade protocol for buying and selling bitcoin for fiat. The security is based on reputation of the sellers.<br /> <br /> See here for more information about [[Bisq_Easy|Bisq Easy]].<br /> <br /> == Future Trade Protocols ==<br /> <br /> Bisq is planning on adding more trade protocols available on Bisq 2. Explore the upcoming trade protocols. Keep an eye out for updates if any of the upcoming protocols catch your interest.<br /> <br /> === Bisq Lightning ===<br /> <br /> Escrow based trade protocol on the Lightning network using multi-party computation cryptography.<br /> <br /> === Bisq Multisig ===<br /> <br /> Bisq 1 currently uses a 2-of-2 multisig as its main trade protocol. This involves the buyer and seller putting down a [[security deposit]] that is locked in a multisig until the trade completes. At some point this protocol will be moved over to Bisq 2.<br /> <br /> === BSQ swaps ===<br /> <br /> This allows users to swap from BSQ to BTC and vice versa via atomic swaps, instantaneously and secure.<br /> <br /> === Liquid Swaps ===<br /> <br /> Trade any Liquid based assets like USDT and BTC-L with an atomic swap on the Liquid network.<br /> <br /> === Monero Swaps ===<br /> <br /> Trade Bitcoin and Monero using an atomic cross chain swap.<br /> <br /> === Liquid Multisig ===<br /> <br /> This trade protocol will use the same trade protocol as the 2-of-2 multisig but it will replace Bitcoin (BTC) with Liquid Bitcoin (L-BTC). The advantage to this is fees will be lower, and users will get more privacy with their trades. The disadvantage is that users will not be trading native bitcoin so will have to be comfortable holding LBTC and consider the costs of converting BTC to LBTC and back again. <br /> <br /> === Submarine Swaps ===<br /> <br /> This trade protocol allows users to swap between Bitcoin on Lightning network to on-chain Bitcoin.<br /> <br /> === Multisig Options ===<br /> <br /> This trade protocol would allow the creation of P2P put and call options with the buyer and seller blocking BTC in a multisig on-chain transaction. 2 PSBT would be created sending the BTC to the buyer or seller depending on the result of a binary event. A blind oracle would trigger the correct transaction to be broadcast to the Bitcoin network.<br /> <br /> == Adding Trade Protocols to Bisq 2 ==<br /> <br /> Trade protocols are designed to be modular so more trade protocols can be added in the future. Anyone with ideas for new trade protocols should join the discussion on [[Matrix_bisq.chat|Bisq's Matrix chat]].</div>

Flix21 https://bisq.wiki/index.php?title=Teams&diff=3520 2024-02-02T13:23:42Z

<p>Flix21: /* Limits on growth */</p> <hr /> <div>[[File:Teams.jpg|thumb]]<br /> <br /> Bisq is a [[FOSS]] project. Governance is decentralised through the [[DAO]]. Work is coordinated through a number of teams with some core members and other external contributors working with a particular team on a project basis. A Team Lead coordinates, assigns work and proposes new projects, always subject to DAO approval and funding. Horizontal control means that each Team Lead is controlled by his peers and the DAO. There is no CEO. True Names are not required. Anonymous and pseudonymous contributors are welcome.<br /> <br /> <br /> == List of Teams ==<br /> <br /> * 1. [[Ops Team]] is responsible for operating Bisq infrastructure nodes and other services with high availability, decentralized and censorship-resistant.<br /> * 2. [[Dev Team]] focused on developing and launching new Bisq releases.<br /> * 3. [[Support Team]] is responsible for providing support for Bisq users.<br /> * 4. [[Growth Team]] focused on promoting and growing Bisq, engaging with current and potential users to improve Bisq. <br /> * 5. [[Security Team]] is responsible for keeping an eye on Bisq's needs for security - hunt bugs, design counter measures...<br /> * 6. [[Infrastructure Team]] is responsable for scaling infrastructure.<br /> * 7. [[Product Team]] focused on launching new products, frontends, etc.<br /> * 8. [[UX Team]] responsible for improving user experience and making Bisq easy to use.<br /> * 9. [[Projects Team]] coordinates projects developed by external contributors, creates bounties, etc.<br /> * 10. [[Decentralization Team]] guides the DAO to be more decentralised, guard against corporate capture, automate governance.<br /> * 11. [[Defense Team]] focused on legal, regulatory, privacy and other risks to contributors and the DAO.<br /> * 12. [[Financial Team]] is responsible for keeping the DAO profitable and markets liquid.<br /> <br /> == Limits on growth ==<br /> <br /> To avoid the bureaucratic decay that many startups and FOSS projects fall into once they exceed the '''Dunbar Number''' (~150) and horizontal communications become difficult, Bisq will limit the number of teams to a maximum of 12 and will make efforts to outsource as much work as possible to external contributors. This can be done on a per-project basis for some types of work, through bounties for one-off tasks or by opening it up to the market in an automatic way following the model of Bitcoin miners. Ideally 90% of work will require only in-team coordination and only a small part will require team leads to coordinate between them. In theory each team could behave as an external contractor, being assigned work by the DAO and then presenting a compensation request when the work is completed, just as an external contractor would present the bill for services rendered.<br /> <br /> == Privacy and security ==<br /> <br /> Anonymity and pseudonymity are welcome at Bisq. Bisq is global and many countries have unfriendly regulations for Bitcoin, exchanges, DEX, FOSS, etc. Many countries do not respect [[Free Speech]] or [[Private Property]]. Contributors should be able to work for the Bisq DAO without requiring to endanger their privacy. This is another important reason to decentralise work and rely on external contributors that can complete a project, get paid and leave. [[Proof of work]] should be the standard for compensation and merit.<br /> <br /> == Control and Recruitment ==<br /> <br /> Team leads are responsible for control of team members, external contributors and outsourced workers. They can exercise this control by approving their compensation requests every cycle (see [[Compensation|Team Lead review]]). They can also recruit more members and greenlight projects, subject to final DAO approval. Team leads are controlled horizontally by their peers and by the DAO.<br /> <br /> When a new team lead position has multiple candidates the recruitment process must adhere to Bisq principles being open and public.</div>

Flix21 https://bisq.wiki/index.php?title=Teams&diff=3519 2024-02-02T13:11:20Z

<p>Flix21: /* Control and Recruitment */</p> <hr /> <div>[[File:Teams.jpg|thumb]]<br /> <br /> Bisq is a [[FOSS]] project. Governance is decentralised through the [[DAO]]. Work is coordinated through a number of teams with some core members and other external contributors working with a particular team on a project basis. A Team Lead coordinates, assigns work and proposes new projects, always subject to DAO approval and funding. Horizontal control means that each Team Lead is controlled by his peers and the DAO. There is no CEO. True Names are not required. Anonymous and pseudonymous contributors are welcome.<br /> <br /> <br /> == List of Teams ==<br /> <br /> * 1. [[Ops Team]] is responsible for operating Bisq infrastructure nodes and other services with high availability, decentralized and censorship-resistant.<br /> * 2. [[Dev Team]] focused on developing and launching new Bisq releases.<br /> * 3. [[Support Team]] is responsible for providing support for Bisq users.<br /> * 4. [[Growth Team]] focused on promoting and growing Bisq, engaging with current and potential users to improve Bisq. <br /> * 5. [[Security Team]] is responsible for keeping an eye on Bisq's needs for security - hunt bugs, design counter measures...<br /> * 6. [[Infrastructure Team]] is responsable for scaling infrastructure.<br /> * 7. [[Product Team]] focused on launching new products, frontends, etc.<br /> * 8. [[UX Team]] responsible for improving user experience and making Bisq easy to use.<br /> * 9. [[Projects Team]] coordinates projects developed by external contributors, creates bounties, etc.<br /> * 10. [[Decentralization Team]] guides the DAO to be more decentralised, guard against corporate capture, automate governance.<br /> * 11. [[Defense Team]] focused on legal, regulatory, privacy and other risks to contributors and the DAO.<br /> * 12. [[Financial Team]] is responsible for keeping the DAO profitable and markets liquid.<br /> <br /> == Limits on growth ==<br /> <br /> To avoid the bureaucratic decay that many startups and FOSS projects fall into once they exceed the Dunbar Number (~150) and horizontal communications become difficult, Bisq will limit the number of teams to a maximum of 12 and will make efforts to outsource as much work as possible to external contributors. This can be done on a per-project basis for some types of work, through bounties for one-off tasks or by opening it up to the market in an automatic way following the model of Bitcoin miners. Ideally 90% of work will require only in-team coordination and only a small part will require team leads to coordinate between them. In theory each team could behave as an external contractor, being assigned work by the DAO and then presenting a compensation request when the work is completed, just as an external contractor would present the bill for services rendered.<br /> <br /> == Privacy and security ==<br /> <br /> Anonymity and pseudonymity are welcome at Bisq. Bisq is global and many countries have unfriendly regulations for Bitcoin, exchanges, DEX, FOSS, etc. Many countries do not respect [[Free Speech]] or [[Private Property]]. Contributors should be able to work for the Bisq DAO without requiring to endanger their privacy. This is another important reason to decentralise work and rely on external contributors that can complete a project, get paid and leave. [[Proof of work]] should be the standard for compensation and merit.<br /> <br /> == Control and Recruitment ==<br /> <br /> Team leads are responsible for control of team members, external contributors and outsourced workers. They can exercise this control by approving their compensation requests every cycle (see [[Compensation|Team Lead review]]). They can also recruit more members and greenlight projects, subject to final DAO approval. Team leads are controlled horizontally by their peers and by the DAO.<br /> <br /> When a new team lead position has multiple candidates the recruitment process must adhere to Bisq principles being open and public.</div>

Flix21 https://bisq.wiki/index.php?title=Teams&diff=3518 2024-01-05T19:32:00Z

<p>Flix21: /* Control and Recruitment */</p> <hr /> <div>[[File:Teams.jpg|thumb]]<br /> <br /> Bisq is a [[FOSS]] project. Governance is decentralised through the [[DAO]]. Work is coordinated through a number of teams with some core members and other external contributors working with a particular team on a project basis. A Team Lead coordinates, assigns work and proposes new projects, always subject to DAO approval and funding. Horizontal control means that each Team Lead is controlled by his peers and the DAO. There is no CEO. True Names are not required. Anonymous and pseudonymous contributors are welcome.<br /> <br /> <br /> == List of Teams ==<br /> <br /> * 1. [[Ops Team]] is responsible for operating Bisq infrastructure nodes and other services with high availability, decentralized and censorship-resistant.<br /> * 2. [[Dev Team]] focused on developing and launching new Bisq releases.<br /> * 3. [[Support Team]] is responsible for providing support for Bisq users.<br /> * 4. [[Growth Team]] focused on promoting and growing Bisq, engaging with current and potential users to improve Bisq. <br /> * 5. [[Security Team]] is responsible for keeping an eye on Bisq's needs for security - hunt bugs, design counter measures...<br /> * 6. [[Infrastructure Team]] is responsable for scaling infrastructure.<br /> * 7. [[Product Team]] focused on launching new products, frontends, etc.<br /> * 8. [[UX Team]] responsible for improving user experience and making Bisq easy to use.<br /> * 9. [[Projects Team]] coordinates projects developed by external contributors, creates bounties, etc.<br /> * 10. [[Decentralization Team]] guides the DAO to be more decentralised, guard against corporate capture, automate governance.<br /> * 11. [[Defense Team]] focused on legal, regulatory, privacy and other risks to contributors and the DAO.<br /> * 12. [[Financial Team]] is responsible for keeping the DAO profitable and markets liquid.<br /> <br /> == Limits on growth ==<br /> <br /> To avoid the bureaucratic decay that many startups and FOSS projects fall into once they exceed the Dunbar Number (~150) and horizontal communications become difficult, Bisq will limit the number of teams to a maximum of 12 and will make efforts to outsource as much work as possible to external contributors. This can be done on a per-project basis for some types of work, through bounties for one-off tasks or by opening it up to the market in an automatic way following the model of Bitcoin miners. Ideally 90% of work will require only in-team coordination and only a small part will require team leads to coordinate between them. In theory each team could behave as an external contractor, being assigned work by the DAO and then presenting a compensation request when the work is completed, just as an external contractor would present the bill for services rendered.<br /> <br /> == Privacy and security ==<br /> <br /> Anonymity and pseudonymity are welcome at Bisq. Bisq is global and many countries have unfriendly regulations for Bitcoin, exchanges, DEX, FOSS, etc. Many countries do not respect [[Free Speech]] or [[Private Property]]. Contributors should be able to work for the Bisq DAO without requiring to endanger their privacy. This is another important reason to decentralise work and rely on external contributors that can complete a project, get paid and leave. [[Proof of work]] should be the standard for compensation and merit.<br /> <br /> == Control and Recruitment ==<br /> <br /> Team leads are responsible for control of team members, external contributors and outsourced workers. They can exercise this control by approving their compensation requests every cycle (see [[Compensation|Team Lead review]]). They can also recruit more members and greenlight projects, subject to final DAO approval. Team leads are controlled horizontally by their peers and by the DAO.<br /> <br /> When a new team lead position has multiple candidates the recruitment process must adhere to Bisq principles being open and public.<br /> <br /> For example:<br /> <br /> 1. Contributor interested in Team Lead position formally applies on the relevant github issue (https://github.com/bisq-network/roles/issues/100), detailing their plan for the team, the work they expect to do, how many hours a day they can work on this, the compensation they will ask for, the goals that they hope to achieve. Links to previous work. Details of BSQ bond if bonded role.<br /> <br /> 2. Other contributors and team leads give feedback, ask questions, demand more details from candidates.<br /> <br /> 3. If decision is clear (contributor consensus on preferred candidate) this should be obvious on github issue.<br /> <br /> 4. If doubt persists, ask for an explicit vote on github.<br /> <br /> 5. If there is a tie or issues with voting (sybil attack?), put it to a DAO vote.</div>

Flix21 https://bisq.wiki/index.php?title=Teams&diff=3517 2024-01-05T19:06:42Z

<p>Flix21: /* List of Teams */</p> <hr /> <div>[[File:Teams.jpg|thumb]]<br /> <br /> Bisq is a [[FOSS]] project. Governance is decentralised through the [[DAO]]. Work is coordinated through a number of teams with some core members and other external contributors working with a particular team on a project basis. A Team Lead coordinates, assigns work and proposes new projects, always subject to DAO approval and funding. Horizontal control means that each Team Lead is controlled by his peers and the DAO. There is no CEO. True Names are not required. Anonymous and pseudonymous contributors are welcome.<br /> <br /> <br /> == List of Teams ==<br /> <br /> * 1. [[Ops Team]] is responsible for operating Bisq infrastructure nodes and other services with high availability, decentralized and censorship-resistant.<br /> * 2. [[Dev Team]] focused on developing and launching new Bisq releases.<br /> * 3. [[Support Team]] is responsible for providing support for Bisq users.<br /> * 4. [[Growth Team]] focused on promoting and growing Bisq, engaging with current and potential users to improve Bisq. <br /> * 5. [[Security Team]] is responsible for keeping an eye on Bisq's needs for security - hunt bugs, design counter measures...<br /> * 6. [[Infrastructure Team]] is responsable for scaling infrastructure.<br /> * 7. [[Product Team]] focused on launching new products, frontends, etc.<br /> * 8. [[UX Team]] responsible for improving user experience and making Bisq easy to use.<br /> * 9. [[Projects Team]] coordinates projects developed by external contributors, creates bounties, etc.<br /> * 10. [[Decentralization Team]] guides the DAO to be more decentralised, guard against corporate capture, automate governance.<br /> * 11. [[Defense Team]] focused on legal, regulatory, privacy and other risks to contributors and the DAO.<br /> * 12. [[Financial Team]] is responsible for keeping the DAO profitable and markets liquid.<br /> <br /> == Limits on growth ==<br /> <br /> To avoid the bureaucratic decay that many startups and FOSS projects fall into once they exceed the Dunbar Number (~150) and horizontal communications become difficult, Bisq will limit the number of teams to a maximum of 12 and will make efforts to outsource as much work as possible to external contributors. This can be done on a per-project basis for some types of work, through bounties for one-off tasks or by opening it up to the market in an automatic way following the model of Bitcoin miners. Ideally 90% of work will require only in-team coordination and only a small part will require team leads to coordinate between them. In theory each team could behave as an external contractor, being assigned work by the DAO and then presenting a compensation request when the work is completed, just as an external contractor would present the bill for services rendered.<br /> <br /> == Privacy and security ==<br /> <br /> Anonymity and pseudonymity are welcome at Bisq. Bisq is global and many countries have unfriendly regulations for Bitcoin, exchanges, DEX, FOSS, etc. Many countries do not respect [[Free Speech]] or [[Private Property]]. Contributors should be able to work for the Bisq DAO without requiring to endanger their privacy. This is another important reason to decentralise work and rely on external contributors that can complete a project, get paid and leave. [[Proof of work]] should be the standard for compensation and merit.<br /> <br /> == Control and Recruitment ==<br /> <br /> Team leads are responsible for control of team members, external contributors and outsourced workers. They can exercise this control by approving their compensation requests every cycle. They can also recruit more members and greenlight projects, subject to final DAO approval. Team leads are controlled horizontally by their peers and by the DAO.<br /> <br /> When a new team lead position has multiple candidates the recruitment process must adhere to Bisq principles being open and public.<br /> <br /> For example:<br /> <br /> 1. Contributor interested in Team Lead position formally applies on the relevant github issue (https://github.com/bisq-network/roles/issues/100), detailing their plan for the team, the work they expect to do, how many hours a day they can work on this, the compensation they will ask for, the goals that they hope to achieve. Links to previous work. Details of BSQ bond if bonded role.<br /> <br /> 2. Other contributors and team leads give feedback, ask questions, demand more details from candidates.<br /> <br /> 3. If decision is clear (contributor consensus on preferred candidate) this should be obvious on github issue.<br /> <br /> 4. If doubt persists, ask for an explicit vote on github.<br /> <br /> 5. If there is a tie or issues with voting (sybil attack?), put it to a DAO vote.</div>

Flix21 https://bisq.wiki/index.php?title=Teams&diff=3516 2024-01-05T18:43:30Z

<p>Flix21: /* Control and Recruitment */</p> <hr /> <div>[[File:Teams.jpg|thumb]]<br /> <br /> Bisq is a [[FOSS]] project. Governance is decentralised through the [[DAO]]. Work is coordinated through a number of teams with some core members and other external contributors working with a particular team on a project basis. A Team Lead coordinates, assigns work and proposes new projects, always subject to DAO approval and funding. Horizontal control means that each Team Lead is controlled by his peers and the DAO. There is no CEO. True Names are not required. Anonymous and pseudonymous contributors are welcome.<br /> <br /> <br /> == List of Teams ==<br /> <br /> * 1. [[Ops Team]] is responsible for operating Bisq infrastructure nodes and other services with high availability, decentralized and censorship-resistant.<br /> * 2. [[Dev Team]] focused on developing and launching new Bisq releases.<br /> * 3. [[Support Team]] is responsible for providing support for Bisq users.<br /> * 4. [[Growth Team]] focused on promoting and growing Bisq, engaging with current and potential users to improve Bisq. <br /> * 5. [[Security Team]] is responsible for keeping an eye on Bisq's needs for security - hunt bugs, design counter measures...<br /> * 6. [[Infrastructure Team]] is responsable for scaling infrastructure.<br /> * 7. [[Product Team]] focused on launching new products, frontends, etc.<br /> * 8. [[UX Team]] responsible for improving user experience and making Bisq easy to use.<br /> * 9. [[Projects Team]] coordinates projects developed by external contributors, creates bounties, etc.<br /> * 10. [[Decentralization Team]] guides the DAO to be more decentralised, guards against risks of corporate capture.<br /> * 11. [[Defense Team]] focused on legal, regulatory, privacy and other risks to contributors and the DAO.<br /> * 12. [[Financial Team]] is responsible for keeping the DAO profitable and markets liquid.<br /> <br /> == Limits on growth ==<br /> <br /> To avoid the bureaucratic decay that many startups and FOSS projects fall into once they exceed the Dunbar Number (~150) and horizontal communications become difficult, Bisq will limit the number of teams to a maximum of 12 and will make efforts to outsource as much work as possible to external contributors. This can be done on a per-project basis for some types of work, through bounties for one-off tasks or by opening it up to the market in an automatic way following the model of Bitcoin miners. Ideally 90% of work will require only in-team coordination and only a small part will require team leads to coordinate between them. In theory each team could behave as an external contractor, being assigned work by the DAO and then presenting a compensation request when the work is completed, just as an external contractor would present the bill for services rendered.<br /> <br /> == Privacy and security ==<br /> <br /> Anonymity and pseudonymity are welcome at Bisq. Bisq is global and many countries have unfriendly regulations for Bitcoin, exchanges, DEX, FOSS, etc. Many countries do not respect [[Free Speech]] or [[Private Property]]. Contributors should be able to work for the Bisq DAO without requiring to endanger their privacy. This is another important reason to decentralise work and rely on external contributors that can complete a project, get paid and leave. [[Proof of work]] should be the standard for compensation and merit.<br /> <br /> == Control and Recruitment ==<br /> <br /> Team leads are responsible for control of team members, external contributors and outsourced workers. They can exercise this control by approving their compensation requests every cycle. They can also recruit more members and greenlight projects, subject to final DAO approval. Team leads are controlled horizontally by their peers and by the DAO.<br /> <br /> When a new team lead position has multiple candidates the recruitment process must adhere to Bisq principles being open and public.<br /> <br /> For example:<br /> <br /> 1. Contributor interested in Team Lead position formally applies on the relevant github issue (https://github.com/bisq-network/roles/issues/100), detailing their plan for the team, the work they expect to do, how many hours a day they can work on this, the compensation they will ask for, the goals that they hope to achieve. Links to previous work. Details of BSQ bond if bonded role.<br /> <br /> 2. Other contributors and team leads give feedback, ask questions, demand more details from candidates.<br /> <br /> 3. If decision is clear (contributor consensus on preferred candidate) this should be obvious on github issue.<br /> <br /> 4. If doubt persists, ask for an explicit vote on github.<br /> <br /> 5. If there is a tie or issues with voting (sybil attack?), put it to a DAO vote.</div>

Flix21 https://bisq.wiki/index.php?title=Teams&diff=3515 2024-01-05T18:37:14Z

<p>Flix21: /* Recruitment */</p> <hr /> <div>[[File:Teams.jpg|thumb]]<br /> <br /> Bisq is a [[FOSS]] project. Governance is decentralised through the [[DAO]]. Work is coordinated through a number of teams with some core members and other external contributors working with a particular team on a project basis. A Team Lead coordinates, assigns work and proposes new projects, always subject to DAO approval and funding. Horizontal control means that each Team Lead is controlled by his peers and the DAO. There is no CEO. True Names are not required. Anonymous and pseudonymous contributors are welcome.<br /> <br /> <br /> == List of Teams ==<br /> <br /> * 1. [[Ops Team]] is responsible for operating Bisq infrastructure nodes and other services with high availability, decentralized and censorship-resistant.<br /> * 2. [[Dev Team]] focused on developing and launching new Bisq releases.<br /> * 3. [[Support Team]] is responsible for providing support for Bisq users.<br /> * 4. [[Growth Team]] focused on promoting and growing Bisq, engaging with current and potential users to improve Bisq. <br /> * 5. [[Security Team]] is responsible for keeping an eye on Bisq's needs for security - hunt bugs, design counter measures...<br /> * 6. [[Infrastructure Team]] is responsable for scaling infrastructure.<br /> * 7. [[Product Team]] focused on launching new products, frontends, etc.<br /> * 8. [[UX Team]] responsible for improving user experience and making Bisq easy to use.<br /> * 9. [[Projects Team]] coordinates projects developed by external contributors, creates bounties, etc.<br /> * 10. [[Decentralization Team]] guides the DAO to be more decentralised, guards against risks of corporate capture.<br /> * 11. [[Defense Team]] focused on legal, regulatory, privacy and other risks to contributors and the DAO.<br /> * 12. [[Financial Team]] is responsible for keeping the DAO profitable and markets liquid.<br /> <br /> == Limits on growth ==<br /> <br /> To avoid the bureaucratic decay that many startups and FOSS projects fall into once they exceed the Dunbar Number (~150) and horizontal communications become difficult, Bisq will limit the number of teams to a maximum of 12 and will make efforts to outsource as much work as possible to external contributors. This can be done on a per-project basis for some types of work, through bounties for one-off tasks or by opening it up to the market in an automatic way following the model of Bitcoin miners. Ideally 90% of work will require only in-team coordination and only a small part will require team leads to coordinate between them. In theory each team could behave as an external contractor, being assigned work by the DAO and then presenting a compensation request when the work is completed, just as an external contractor would present the bill for services rendered.<br /> <br /> == Privacy and security ==<br /> <br /> Anonymity and pseudonymity are welcome at Bisq. Bisq is global and many countries have unfriendly regulations for Bitcoin, exchanges, DEX, FOSS, etc. Many countries do not respect [[Free Speech]] or [[Private Property]]. Contributors should be able to work for the Bisq DAO without requiring to endanger their privacy. This is another important reason to decentralise work and rely on external contributors that can complete a project, get paid and leave. [[Proof of work]] should be the standard for compensation and merit.<br /> <br /> == Control and Recruitment ==<br /> <br /> Team leads are responsible for control of team members, external contributors and outsourced workers. They can exercise this control by approving their compensation requests every cycle. They can also recruit more members and greenlight projects, subject to final DAO approval. Team leads are controlled horizontally by their peers and by the DAO.<br /> <br /> When a new team lead position has multiple candidates the recruitment process must adhere to Bisq principles being open and public.<br /> <br /> For example:<br /> <br /> 1. Contributor interested in Team Lead position formally applies on the relevant github issue (https://github.com/bisq-network/roles/issues/100), detailing their plan for the team, the work they expect to do, the compensation they expect to ask for, the goals that they hope to achieve. Links to previous work. Details of BSQ bond if bonded role.<br /> <br /> 2. Other contributors and team leads give feedback, ask questions, demand more details from candidates.<br /> <br /> 3. If decision is clear (contributor consensus on preferred candidate) this should be obvious on github issue.<br /> <br /> 4. If doubt persists, ask for an explicit vote on github.<br /> <br /> 5. If there is a tie or issues with voting (sybil attack?), put it to a DAO vote.</div>

Flix21 https://bisq.wiki/index.php?title=Teams&diff=3514 2024-01-05T18:36:26Z

<p>Flix21: /* Recruitment */</p> <hr /> <div>[[File:Teams.jpg|thumb]]<br /> <br /> Bisq is a [[FOSS]] project. Governance is decentralised through the [[DAO]]. Work is coordinated through a number of teams with some core members and other external contributors working with a particular team on a project basis. A Team Lead coordinates, assigns work and proposes new projects, always subject to DAO approval and funding. Horizontal control means that each Team Lead is controlled by his peers and the DAO. There is no CEO. True Names are not required. Anonymous and pseudonymous contributors are welcome.<br /> <br /> <br /> == List of Teams ==<br /> <br /> * 1. [[Ops Team]] is responsible for operating Bisq infrastructure nodes and other services with high availability, decentralized and censorship-resistant.<br /> * 2. [[Dev Team]] focused on developing and launching new Bisq releases.<br /> * 3. [[Support Team]] is responsible for providing support for Bisq users.<br /> * 4. [[Growth Team]] focused on promoting and growing Bisq, engaging with current and potential users to improve Bisq. <br /> * 5. [[Security Team]] is responsible for keeping an eye on Bisq's needs for security - hunt bugs, design counter measures...<br /> * 6. [[Infrastructure Team]] is responsable for scaling infrastructure.<br /> * 7. [[Product Team]] focused on launching new products, frontends, etc.<br /> * 8. [[UX Team]] responsible for improving user experience and making Bisq easy to use.<br /> * 9. [[Projects Team]] coordinates projects developed by external contributors, creates bounties, etc.<br /> * 10. [[Decentralization Team]] guides the DAO to be more decentralised, guards against risks of corporate capture.<br /> * 11. [[Defense Team]] focused on legal, regulatory, privacy and other risks to contributors and the DAO.<br /> * 12. [[Financial Team]] is responsible for keeping the DAO profitable and markets liquid.<br /> <br /> == Limits on growth ==<br /> <br /> To avoid the bureaucratic decay that many startups and FOSS projects fall into once they exceed the Dunbar Number (~150) and horizontal communications become difficult, Bisq will limit the number of teams to a maximum of 12 and will make efforts to outsource as much work as possible to external contributors. This can be done on a per-project basis for some types of work, through bounties for one-off tasks or by opening it up to the market in an automatic way following the model of Bitcoin miners. Ideally 90% of work will require only in-team coordination and only a small part will require team leads to coordinate between them. In theory each team could behave as an external contractor, being assigned work by the DAO and then presenting a compensation request when the work is completed, just as an external contractor would present the bill for services rendered.<br /> <br /> == Privacy and security ==<br /> <br /> Anonymity and pseudonymity are welcome at Bisq. Bisq is global and many countries have unfriendly regulations for Bitcoin, exchanges, DEX, FOSS, etc. Many countries do not respect [[Free Speech]] or [[Private Property]]. Contributors should be able to work for the Bisq DAO without requiring to endanger their privacy. This is another important reason to decentralise work and rely on external contributors that can complete a project, get paid and leave. [[Proof of work]] should be the standard for compensation and merit.<br /> <br /> == Recruitment ==<br /> <br /> Team leads are responsible for control of team members, external contributors and outsourced workers. They can exercise this control by approving their compensation requests every cycle. They can also recruit more members and greenlight projects, subject to final DAO approval. Team leads are controlled horizontally by their peers and by the DAO.<br /> <br /> When a new team lead position has multiple candidates the recruitment process must adhere to Bisq principles being open and public.<br /> <br /> For example:<br /> <br /> 1. Contributor interested in Team Lead position formally applies on the relevant github issue (https://github.com/bisq-network/roles/issues/100), detailing their plan for the team, the work they expect to do, the compensation they expect to ask for, the goals that they hope to achieve. Links to previous work. Details of BSQ bond if bonded role.<br /> 2. Other contributors and team leads give feedback, ask questions, demand more details from candidates.<br /> 3. If decision is clear (overwhelming majority of contributors have a preferred candidate) this should be obvious on github issue.<br /> 4. If doubt persists, ask for an explicit vote on github.<br /> 5. If there is a tie or issues with voting (sybil attack?), put it to a DAO vote.</div>

Flix21 https://bisq.wiki/index.php?title=Teams&diff=3513 2024-01-05T18:33:00Z

<p>Flix21: /* Privacy and security */</p> <hr /> <div>[[File:Teams.jpg|thumb]]<br /> <br /> Bisq is a [[FOSS]] project. Governance is decentralised through the [[DAO]]. Work is coordinated through a number of teams with some core members and other external contributors working with a particular team on a project basis. A Team Lead coordinates, assigns work and proposes new projects, always subject to DAO approval and funding. Horizontal control means that each Team Lead is controlled by his peers and the DAO. There is no CEO. True Names are not required. Anonymous and pseudonymous contributors are welcome.<br /> <br /> <br /> == List of Teams ==<br /> <br /> * 1. [[Ops Team]] is responsible for operating Bisq infrastructure nodes and other services with high availability, decentralized and censorship-resistant.<br /> * 2. [[Dev Team]] focused on developing and launching new Bisq releases.<br /> * 3. [[Support Team]] is responsible for providing support for Bisq users.<br /> * 4. [[Growth Team]] focused on promoting and growing Bisq, engaging with current and potential users to improve Bisq. <br /> * 5. [[Security Team]] is responsible for keeping an eye on Bisq's needs for security - hunt bugs, design counter measures...<br /> * 6. [[Infrastructure Team]] is responsable for scaling infrastructure.<br /> * 7. [[Product Team]] focused on launching new products, frontends, etc.<br /> * 8. [[UX Team]] responsible for improving user experience and making Bisq easy to use.<br /> * 9. [[Projects Team]] coordinates projects developed by external contributors, creates bounties, etc.<br /> * 10. [[Decentralization Team]] guides the DAO to be more decentralised, guards against risks of corporate capture.<br /> * 11. [[Defense Team]] focused on legal, regulatory, privacy and other risks to contributors and the DAO.<br /> * 12. [[Financial Team]] is responsible for keeping the DAO profitable and markets liquid.<br /> <br /> == Limits on growth ==<br /> <br /> To avoid the bureaucratic decay that many startups and FOSS projects fall into once they exceed the Dunbar Number (~150) and horizontal communications become difficult, Bisq will limit the number of teams to a maximum of 12 and will make efforts to outsource as much work as possible to external contributors. This can be done on a per-project basis for some types of work, through bounties for one-off tasks or by opening it up to the market in an automatic way following the model of Bitcoin miners. Ideally 90% of work will require only in-team coordination and only a small part will require team leads to coordinate between them. In theory each team could behave as an external contractor, being assigned work by the DAO and then presenting a compensation request when the work is completed, just as an external contractor would present the bill for services rendered.<br /> <br /> == Privacy and security ==<br /> <br /> Anonymity and pseudonymity are welcome at Bisq. Bisq is global and many countries have unfriendly regulations for Bitcoin, exchanges, DEX, FOSS, etc. Many countries do not respect [[Free Speech]] or [[Private Property]]. Contributors should be able to work for the Bisq DAO without requiring to endanger their privacy. This is another important reason to decentralise work and rely on external contributors that can complete a project, get paid and leave. [[Proof of work]] should be the standard for compensation and merit.<br /> <br /> == Recruitment ==<br /> <br /> Team leads are responsible for control of team members, external contributors and outsourced workers. They can exercise this control by approving their compensation requests every cycle. They can also recruit more members and greenlight projects, subject to final DAO approval.</div>

Flix21 https://bisq.wiki/index.php?title=Teams&diff=3511 2023-12-29T17:02:25Z

<p>Flix21: /* Privacy and security */</p> <hr /> <div>[[File:Teams.jpg|thumb]]<br /> <br /> Bisq is a [[FOSS]] project. Governance is decentralised through the [[DAO]]. Work is coordinated through a number of teams with some core members and other external contributors working with a particular team on a project basis. A Team Lead coordinates, assigns work and proposes new projects, always subject to DAO approval and funding. Horizontal control means that each Team Lead is controlled by his peers and the DAO. There is no CEO. True Names are not required. Anonymous and pseudonymous contributors are welcome.<br /> <br /> <br /> == List of Teams ==<br /> <br /> * 1. [[Ops Team]] is responsible for operating Bisq infrastructure nodes and other services with high availability, decentralized and censorship-resistant.<br /> * 2. [[Dev Team]] focused on developing and launching new Bisq releases.<br /> * 3. [[Support Team]] is responsible for providing support for Bisq users.<br /> * 4. [[Growth Team]] focused on promoting and growing Bisq, engaging with current and potential users to improve Bisq. <br /> * 5. [[Security Team]] is responsible for keeping an eye on Bisq's needs for security - hunt bugs, design counter measures...<br /> * 6. [[Infrastructure Team]] is responsable for scaling infrastructure.<br /> * 7. [[Product Team]] focused on launching new products, frontends, etc.<br /> * 8. [[UX Team]] responsible for improving user experience and making Bisq easy to use.<br /> * 9. [[Projects Team]] coordinates projects developed by external contributors, creates bounties, etc.<br /> * 10. [[Decentralization Team]] guides the DAO to be more decentralised, guards against risks of corporate capture.<br /> * 11. [[Defense Team]] focused on legal, regulatory, privacy and other risks to contributors and the DAO.<br /> * 12. [[Financial Team]] is responsible for keeping the DAO profitable and markets liquid.<br /> <br /> == Limits on growth ==<br /> <br /> To avoid the bureaucratic decay that many startups and FOSS projects fall into once they exceed the Dunbar Number (~150) and horizontal communications become difficult, Bisq will limit the number of teams to a maximum of 12 and will make efforts to outsource as much work as possible to external contributors. This can be done on a per-project basis for some types of work, through bounties for one-off tasks or by opening it up to the market in an automatic way following the model of Bitcoin miners. Ideally 90% of work will require only in-team coordination and only a small part will require team leads to coordinate between them. In theory each team could behave as an external contractor, being assigned work by the DAO and then presenting a compensation request when the work is completed, just as an external contractor would present the bill for services rendered.<br /> <br /> == Privacy and security ==<br /> <br /> Anonymity and pseudonymity are welcome at Bisq. Bisq is global and many countries have unfriendly regulations for Bitcoin, exchanges, DEX, FOSS, etc. Many countries do not respect [[Free Speech]] or [[Private Property]]. Contributors should be able to work for the Bisq DAO without requiring to endanger their privacy. This is another important reason to decentralise work and rely on external contributors that can complete a project, get paid and leave. [[Proof of work]] should be the standard for compensation and merit.</div>

Flix21 https://bisq.wiki/index.php?title=Teams&diff=3510 2023-12-29T17:01:51Z

<p>Flix21: /* Privacy and security */</p> <hr /> <div>[[File:Teams.jpg|thumb]]<br /> <br /> Bisq is a [[FOSS]] project. Governance is decentralised through the [[DAO]]. Work is coordinated through a number of teams with some core members and other external contributors working with a particular team on a project basis. A Team Lead coordinates, assigns work and proposes new projects, always subject to DAO approval and funding. Horizontal control means that each Team Lead is controlled by his peers and the DAO. There is no CEO. True Names are not required. Anonymous and pseudonymous contributors are welcome.<br /> <br /> <br /> == List of Teams ==<br /> <br /> * 1. [[Ops Team]] is responsible for operating Bisq infrastructure nodes and other services with high availability, decentralized and censorship-resistant.<br /> * 2. [[Dev Team]] focused on developing and launching new Bisq releases.<br /> * 3. [[Support Team]] is responsible for providing support for Bisq users.<br /> * 4. [[Growth Team]] focused on promoting and growing Bisq, engaging with current and potential users to improve Bisq. <br /> * 5. [[Security Team]] is responsible for keeping an eye on Bisq's needs for security - hunt bugs, design counter measures...<br /> * 6. [[Infrastructure Team]] is responsable for scaling infrastructure.<br /> * 7. [[Product Team]] focused on launching new products, frontends, etc.<br /> * 8. [[UX Team]] responsible for improving user experience and making Bisq easy to use.<br /> * 9. [[Projects Team]] coordinates projects developed by external contributors, creates bounties, etc.<br /> * 10. [[Decentralization Team]] guides the DAO to be more decentralised, guards against risks of corporate capture.<br /> * 11. [[Defense Team]] focused on legal, regulatory, privacy and other risks to contributors and the DAO.<br /> * 12. [[Financial Team]] is responsible for keeping the DAO profitable and markets liquid.<br /> <br /> == Limits on growth ==<br /> <br /> To avoid the bureaucratic decay that many startups and FOSS projects fall into once they exceed the Dunbar Number (~150) and horizontal communications become difficult, Bisq will limit the number of teams to a maximum of 12 and will make efforts to outsource as much work as possible to external contributors. This can be done on a per-project basis for some types of work, through bounties for one-off tasks or by opening it up to the market in an automatic way following the model of Bitcoin miners. Ideally 90% of work will require only in-team coordination and only a small part will require team leads to coordinate between them. In theory each team could behave as an external contractor, being assigned work by the DAO and then presenting a compensation request when the work is completed, just as an external contractor would present the bill for services rendered.<br /> <br /> == Privacy and security ==<br /> <br /> Anonymity and pseudonymity are welcome at Bisq. Bisq is global and many countries have unfriendly regulations for Bitcoin, exchanges, DEX, FOSS, etc. Many countries do not respect [[Free Speech]] or [[Private Property]]. Contributors should be able to work for the Bisq DAO without requiring to endanger their privacy. This is another important reason to decentralise work and rely on external contributors that can complete a project, get paid and leave. Proof of work should be the standard for compensation.</div>

Flix21 https://bisq.wiki/index.php?title=Teams&diff=3509 2023-12-29T16:59:58Z

<p>Flix21: /* Limits on growth */</p> <hr /> <div>[[File:Teams.jpg|thumb]]<br /> <br /> Bisq is a [[FOSS]] project. Governance is decentralised through the [[DAO]]. Work is coordinated through a number of teams with some core members and other external contributors working with a particular team on a project basis. A Team Lead coordinates, assigns work and proposes new projects, always subject to DAO approval and funding. Horizontal control means that each Team Lead is controlled by his peers and the DAO. There is no CEO. True Names are not required. Anonymous and pseudonymous contributors are welcome.<br /> <br /> <br /> == List of Teams ==<br /> <br /> * 1. [[Ops Team]] is responsible for operating Bisq infrastructure nodes and other services with high availability, decentralized and censorship-resistant.<br /> * 2. [[Dev Team]] focused on developing and launching new Bisq releases.<br /> * 3. [[Support Team]] is responsible for providing support for Bisq users.<br /> * 4. [[Growth Team]] focused on promoting and growing Bisq, engaging with current and potential users to improve Bisq. <br /> * 5. [[Security Team]] is responsible for keeping an eye on Bisq's needs for security - hunt bugs, design counter measures...<br /> * 6. [[Infrastructure Team]] is responsable for scaling infrastructure.<br /> * 7. [[Product Team]] focused on launching new products, frontends, etc.<br /> * 8. [[UX Team]] responsible for improving user experience and making Bisq easy to use.<br /> * 9. [[Projects Team]] coordinates projects developed by external contributors, creates bounties, etc.<br /> * 10. [[Decentralization Team]] guides the DAO to be more decentralised, guards against risks of corporate capture.<br /> * 11. [[Defense Team]] focused on legal, regulatory, privacy and other risks to contributors and the DAO.<br /> * 12. [[Financial Team]] is responsible for keeping the DAO profitable and markets liquid.<br /> <br /> == Limits on growth ==<br /> <br /> To avoid the bureaucratic decay that many startups and FOSS projects fall into once they exceed the Dunbar Number (~150) and horizontal communications become difficult, Bisq will limit the number of teams to a maximum of 12 and will make efforts to outsource as much work as possible to external contributors. This can be done on a per-project basis for some types of work, through bounties for one-off tasks or by opening it up to the market in an automatic way following the model of Bitcoin miners. Ideally 90% of work will require only in-team coordination and only a small part will require team leads to coordinate between them. In theory each team could behave as an external contractor, being assigned work by the DAO and then presenting a compensation request when the work is completed, just as an external contractor would present the bill for services rendered.<br /> <br /> == Privacy and security ==<br /> <br /> Anonymity and pseudonymity are welcome at Bisq. Bisq is global and many countries have unfriendly regulations for Bitcoin, exchanges, DEX, FOSS, etc. Many countries do not respect [[Free Speech]] or [[Private Property]]. Contributors should be able to work for the Bisq DAO without requiring to endanger their privacy.</div>

Flix21 https://bisq.wiki/index.php?title=Teams&diff=3508 2023-12-29T16:55:22Z

<p>Flix21: </p> <hr /> <div>[[File:Teams.jpg|thumb]]<br /> <br /> Bisq is a [[FOSS]] project. Governance is decentralised through the [[DAO]]. Work is coordinated through a number of teams with some core members and other external contributors working with a particular team on a project basis. A Team Lead coordinates, assigns work and proposes new projects, always subject to DAO approval and funding. Horizontal control means that each Team Lead is controlled by his peers and the DAO. There is no CEO. True Names are not required. Anonymous and pseudonymous contributors are welcome.<br /> <br /> <br /> == List of Teams ==<br /> <br /> * 1. [[Ops Team]] is responsible for operating Bisq infrastructure nodes and other services with high availability, decentralized and censorship-resistant.<br /> * 2. [[Dev Team]] focused on developing and launching new Bisq releases.<br /> * 3. [[Support Team]] is responsible for providing support for Bisq users.<br /> * 4. [[Growth Team]] focused on promoting and growing Bisq, engaging with current and potential users to improve Bisq. <br /> * 5. [[Security Team]] is responsible for keeping an eye on Bisq's needs for security - hunt bugs, design counter measures...<br /> * 6. [[Infrastructure Team]] is responsable for scaling infrastructure.<br /> * 7. [[Product Team]] focused on launching new products, frontends, etc.<br /> * 8. [[UX Team]] responsible for improving user experience and making Bisq easy to use.<br /> * 9. [[Projects Team]] coordinates projects developed by external contributors, creates bounties, etc.<br /> * 10. [[Decentralization Team]] guides the DAO to be more decentralised, guards against risks of corporate capture.<br /> * 11. [[Defense Team]] focused on legal, regulatory, privacy and other risks to contributors and the DAO.<br /> * 12. [[Financial Team]] is responsible for keeping the DAO profitable and markets liquid.<br /> <br /> == Limits on growth ==<br /> <br /> To avoid the bureaucratic decay that many startups and FOSS projects fall into once they exceed the Dunbar Number (~150) and horizontal communications become difficult, Bisq will limit the number of teams to a maximum of 12 and will make efforts to outsource as much work as possible to external contributors. This can be done on a per-project basis for some types of work, through bounties for one-off tasks or by opening it up to the market in an automatic way following the model of Bitcoin miners. Ideally 90% of work will require only in-team coordination and only a small part will require team leads to coordinate between them. In theory each team could behave as an external contractor, being assigned work by the DAO and then presenting a compensation request when the work is completed, just as an external contractor would present the bill for services rendered.</div>

Flix21 https://bisq.wiki/index.php?title=Teams&diff=3507 2023-12-29T16:46:41Z

<p>Flix21: </p> <hr /> <div>[[File:Teams.jpg|thumb]]<br /> <br /> Bisq is a [[FOSS]] project. Governance is decentralised through the [[DAO]]. Work is coordinated through a number of teams with some core members and other external contributors working with a particular team on a project basis. A Team Lead coordinates, assigns work and proposes new projects, always subject to DAO approval and funding. Horizontal control means that each Team Lead is controlled by his peers and the DAO. There is no CEO. True Names are not required. Anonymous and pseudonymous contributors are welcome.<br /> <br /> <br /> == List of Teams ==<br /> <br /> * 1. [[Ops Team]] is responsible for operating Bisq infrastructure nodes and other services with high availability, decentralized and censorship-resistant.<br /> * 2. [[Dev Team]] focused on developing and launching new Bisq releases.<br /> * 3. [[Support Team]] is responsible for providing support for Bisq users.<br /> * 4. [[Growth Team]] focused on promoting and growing Bisq, engaging with current and potential users to improve Bisq. <br /> * 5. [[Security Team]] is responsible for keeping an eye on Bisq's needs for security - hunt bugs, design counter measures...<br /> * 6. [[Infrastructure Team]] is responsable for scaling infrastructure.<br /> * 7. [[Product Team]] focused on launching new products, frontends, etc.<br /> * 8. [[UX Team]] responsible for improving user experience and making Bisq easy to use.<br /> * 9. [[Projects Team]] coordinates projects developed by external contributors, creates bounties, etc.<br /> * 10. [[Decentralization Team]] guides the DAO to be more decentralised, guards against risks of corporate capture.<br /> * 11. [[Defense Team]] focused on legal, regulatory, privacy and other risks to contributors and the DAO.<br /> * 12. [[Financial Team]] is responsible for keeping the DAO profitable and markets liquid.</div>

Flix21 https://bisq.wiki/index.php?title=Teams&diff=3506 2023-12-29T16:42:05Z

<p>Flix21: /* List of Teams */</p> <hr /> <div>[[File:Teams.jpg|thumb]]<br /> <br /> Bisq is a [[FOSS]] project. Governance is decentralised through the [[DAO]]. Work is coordinated through a number of teams with some core members and other external contributors working with a particular team on a project basis. A Team Lead coordinates, assigns work and proposes new projects, always subject to DAO approval and funding. Horizontal control between peers means that each Team Lead is controlled by his peers. There is no CEO. True Names are not required. Anonymous and pseudonymous contributors are welcome.<br /> <br /> <br /> == List of Teams ==<br /> <br /> * 1. [[Ops Team]] is responsible for operating Bisq infrastructure nodes and other services with high availability, decentralized and censorship-resistant.<br /> * 2. [[Dev Team]] focused on developing and launching new Bisq releases.<br /> * 3. [[Support Team]] is responsible for providing support for Bisq users.<br /> * 4. [[Growth Team]] focused on promoting and growing Bisq, engaging with current and potential users to improve Bisq. <br /> * 5. [[Security Team]] is responsible for keeping an eye on Bisq's needs for security - hunt bugs, design counter measures...<br /> * 6. [[Infrastructure Team]] is responsable for scaling infrastructure.<br /> * 7. [[Product Team]] focused on launching new products, frontends, etc.<br /> * 8. [[UX Team]] responsible for improving user experience and making Bisq easy to use.<br /> * 9. [[Projects Team]] coordinates projects developed by external contributors, creates bounties, etc.<br /> * 10. [[Decentralization Team]] guides the DAO to be more decentralised, guards against risks of corporate capture.<br /> * 11. [[Defense Team]] focused on legal, regulatory, privacy and other risks to contributors and the DAO.<br /> * 12. [[Financial Team]] is responsible for keeping the DAO profitable and markets liquid.</div>

Flix21 https://bisq.wiki/index.php?title=Teams&diff=3505 2023-12-29T16:35:58Z

<p>Flix21: /* List of Teams */</p> <hr /> <div>[[File:Teams.jpg|thumb]]<br /> <br /> Bisq is a [[FOSS]] project. Governance is decentralised through the [[DAO]]. Work is coordinated through a number of teams with some core members and other external contributors working with a particular team on a project basis. A Team Lead coordinates, assigns work and proposes new projects, always subject to DAO approval and funding. Horizontal control between peers means that each Team Lead is controlled by his peers. There is no CEO. True Names are not required. Anonymous and pseudonymous contributors are welcome.<br /> <br /> <br /> == List of Teams ==<br /> <br /> * 1. [[Ops Team]] is responsible for operating Bisq infrastructure nodes and other services with high availability, decentralized and censorship-resistant.<br /> * 2. [[Dev Team]] focused on developing and launching new Bisq releases.<br /> * 3. [[Support Team]] is responsible for providing support for Bisq users.<br /> * 4. [[Growth Team]] Focused on promoting and growing Bisq, engaging with current and potential users to improve Bisq. <br /> * 5. [[Security Team]] is responsible for keeping an eye on Bisq's needs for security - hunt bugs, design counter measures...<br /> * 6. [[Infrastructure Team]]<br /> * 7. [[Product Team]]<br /> * 8. [[UX Team]]<br /> * 9. [[Projects Team]]<br /> * 10. [[Decentralization Team]]<br /> * 11. [[Defense Team]]<br /> * 12. [[Financial Team]]</div>

Flix21 https://bisq.wiki/index.php?title=Teams&diff=3504 2023-12-29T16:33:16Z

<p>Flix21: /* List of Teams */</p> <hr /> <div>[[File:Teams.jpg|thumb]]<br /> <br /> Bisq is a [[FOSS]] project. Governance is decentralised through the [[DAO]]. Work is coordinated through a number of teams with some core members and other external contributors working with a particular team on a project basis. A Team Lead coordinates, assigns work and proposes new projects, always subject to DAO approval and funding. Horizontal control between peers means that each Team Lead is controlled by his peers. There is no CEO. True Names are not required. Anonymous and pseudonymous contributors are welcome.<br /> <br /> <br /> == List of Teams ==<br /> <br /> * 1. [[Ops Team]] is responsible for operating Bisq infrastructure nodes and other services with high availability, decentralized and censorship-resistant.<br /> * 2. [[Dev Team]] focused on developing and launching new Bisq releases.<br /> * 3. [[Support Team]] is responsible for providing support for Bisq users.<br /> * 4. [[Growth Team]] Focused on promoting and growing Bisq, engaging with current and potential users to improve Bisq. <br /> * 5. [[Security Team]] is responsible for keeping an eye on Bisq's needs for security - hunt bugs, design counter measures...<br /> * 6. <br /> * 7. <br /> * 8. <br /> * 9. <br /> * 10. <br /> * 11.<br /> * 12.</div>

Flix21 https://bisq.wiki/index.php?title=Teams&diff=3503 2023-12-29T16:31:19Z

<p>Flix21: </p> <hr /> <div>[[File:Teams.jpg|thumb]]<br /> <br /> Bisq is a [[FOSS]] project. Governance is decentralised through the [[DAO]]. Work is coordinated through a number of teams with some core members and other external contributors working with a particular team on a project basis. A Team Lead coordinates, assigns work and proposes new projects, always subject to DAO approval and funding. Horizontal control between peers means that each Team Lead is controlled by his peers. There is no CEO. True Names are not required. Anonymous and pseudonymous contributors are welcome.<br /> <br /> <br /> == List of Teams ==<br /> <br /> * [[Ops Team]] is responsible for operating Bisq infrastructure nodes and other Bisq services with high availability, in a decentralized and censorship-resistant manner.<br /> * [[Dev Team]] focused on developing and launching new Bisq releases.<br /> * [[Support Team]] is responsible for providing support for Bisq users.<br /> * [[Growth Team]] Focused on promoting and growing Bisq, engaging with current and potential users to improve Bisq. <br /> * [[Security Team]] is responsible for keeping an eye on Bisq's needs for security - hunt bugs, design counter measures...</div>

Flix21 https://bisq.wiki/index.php?title=Teams&diff=3502 2023-12-29T16:30:56Z

<p>Flix21: /* List of Teams */</p> <hr /> <div>Bisq is a [[FOSS]] project. Governance is decentralised through the [[DAO]]. Work is coordinated through a number of teams with some core members and other external contributors working with a particular team on a project basis. A Team Lead coordinates, assigns work and proposes new projects, always subject to DAO approval and funding. Horizontal control between peers means that each Team Lead is controlled by his peers. There is no CEO. True Names are not required. Anonymous and pseudonymous contributors are welcome.<br /> <br /> [[File:Teams.jpg|thumb]]<br /> <br /> <br /> == List of Teams ==<br /> <br /> * [[Ops Team]] is responsible for operating Bisq infrastructure nodes and other Bisq services with high availability, in a decentralized and censorship-resistant manner.<br /> * [[Dev Team]] focused on developing and launching new Bisq releases.<br /> * [[Support Team]] is responsible for providing support for Bisq users.<br /> * [[Growth Team]] Focused on promoting and growing Bisq, engaging with current and potential users to improve Bisq. <br /> * [[Security Team]] is responsible for keeping an eye on Bisq's needs for security - hunt bugs, design counter measures...</div>

Flix21 https://bisq.wiki/index.php?title=Teams&diff=3501 2023-12-29T16:27:40Z

<p>Flix21: /* List of Teams */</p> <hr /> <div>Bisq is a [[FOSS]] project. Governance is decentralised through the [[DAO]]. Work is coordinated through a number of teams with some core members and other external contributors working with a particular team on a project basis. A Team Lead coordinates, assigns work and proposes new projects, always subject to DAO approval and funding. Horizontal control between peers means that each Team Lead is controlled by his peers. There is no CEO. True Names are not required. Anonymous and pseudonymous contributors are welcome.<br /> <br /> [[File:Teams.jpg|thumb]]<br /> <br /> <br /> == List of Teams ==<br /> <br /> * Ops<br /> * Dev<br /> * Support<br /> * [[Growth Team]] Focused on promoting and growing Bisq, engaging with current and potential users to improve Bisq. <br /> * Security</div>

Flix21 https://bisq.wiki/index.php?title=Teams&diff=3500 2023-12-29T16:26:14Z

<p>Flix21: </p> <hr /> <div>Bisq is a [[FOSS]] project. Governance is decentralised through the [[DAO]]. Work is coordinated through a number of teams with some core members and other external contributors working with a particular team on a project basis. A Team Lead coordinates, assigns work and proposes new projects, always subject to DAO approval and funding. Horizontal control between peers means that each Team Lead is controlled by his peers. There is no CEO. True Names are not required. Anonymous and pseudonymous contributors are welcome.<br /> <br /> [[File:Teams.jpg|thumb]]<br /> <br /> <br /> == List of Teams ==<br /> <br /> *<br /> *<br /> *<br /> *<br /> *</div>

Flix21 https://bisq.wiki/index.php?title=Teams&diff=3499 2023-12-29T16:23:22Z

<p>Flix21: </p> <hr /> <div>Bisq is a [[FOSS]] project. Governance is decentralised through the [[DAO]]. Work is coordinated through a number of teams with some core members and other external contributors working with a particular team on a project basis. A Team Lead coordinates, assigns work and proposes new projects, always subject to DAO approval and funding. Horizontal control between peers means that each Team Lead is controlled by his peers. There is no CEO.<br /> <br /> <br /> <br /> <br /> <br /> <br /> [[File:Teams.jpg|thumb]]</div>

Flix21 https://bisq.wiki/index.php?title=Teams&diff=3498 2023-12-29T16:18:22Z

<p>Flix21: test</p> <hr /> <div>[[File:Teams.jpg|thumb]]</div>

Flix21 https://bisq.wiki/index.php?title=File:Teams.jpg&diff=3497 2023-12-29T16:18:12Z

<p>Flix21: </p> <hr /> <div>Bisq DAO structure</div>

Flix21 https://bisq.wiki/index.php?title=How_to_be_a_market_maker_on_Bisq&diff=3202 2023-06-14T09:22:53Z

<p>Flix21: </p> <hr /> <div>Markets need liquidity to be useful. A '''market maker''' provides liquidity by creating offers and earns a profit for this very useful service. By publishing offers on Bisq, a market maker makes sure that when other traders come to market to buy or sell, they always have an option to do so immediately.<br /> <br /> Some markets on Bisq have few or no offers available. This means that new users see that market empty, they are discouraged and leave without trading. A market maker can bridge that coordination gap, helping kickstart a new market, while at the same time earning some Bitcoin.<br /> <br /> <br /> Here's a simple way to perform the market maker function:<br /> <br /> 1. Find a market with few or no offers available. <br /> <br /> 2. Create an offer to BUY Bitcoin at 3% below market price. (For example see [[How to create an offer to buy BTC with EUR]])<br /> <br /> 3. Create an offer to SELL Bitcoin at 3% above market price. (For example see [[How to create an offer to sell BTC with EUR]])<br /> <br /> 4. Stay online and keep Bisq running so that your offers are available.<br /> <br /> 5. When one of your offers is taken, complete the trade and create a new one to replace it.<br /> <br /> 6. Tell people about it! Let people from that market know that you are trying to kickstart it.<br /> <br /> <br /> In the example above if both your offers are taken you will have sold at 103 and bought at 97, making a profit of 6. You will also be performing a very valuable service for other Bisq users who don't have the time to stay online and just want to be able to take an offer quickly. Offer takers will be happy to pay a small % for the convenience of buying or selling when they want. Some markets are less liquid and you can charge more for your service, others have many more offers and will pay less for the convenience.<br /> <br /> <br /> <br /> *For more short guides see [[Howto]]. You can also find support on '''[https://bisq.chat Matrix]'''.</div>

Flix21 https://bisq.wiki/index.php?title=Atomic_swap&diff=3188 2023-04-17T14:07:08Z

<p>Flix21: </p> <hr /> <div>Bisq has pioneered Bitcoin based atomic swaps. It is currently possible to exchange Bitcoin to BSQ atomically. BSQ is Bisq's native token built as a Bitcoin coloured coin.<br /> <br /> The atomic swap protocol used by the Bisq DEX goes one step further in reducing counterparty risk: not only are users not exposed to exchange counterparty risk (since DEX holds no user funds) but it also eliminates the possibility of a buyer or seller failing to pay. The transaction is instant, automatic and final (once confirmed in a Bitcoin blockchain block).<br /> <br /> Currently only BSQ to BTC is available, but this type of swap could be done with any Bitcoin coloured coin.</div>

Flix21 https://bisq.wiki/index.php?title=Atomic_swap&diff=3187 2023-04-17T14:06:05Z

<p>Flix21: </p> <hr /> <div>Bisq has pioneered Bitcoin based atomic swaps. It is currently possible to exchange Bitcoin to BSQ atomically. BSQ is Bisq's native token built as a Bitcoin coloured coin.<br /> <br /> The atomic swap protocol used by the Bisq DEX goes one step further in reducing counterparty risk: not only are users not exposed to exchange counterparty risk (since DEX holds no user funds) but it also eliminates the possibility of a buyer or seller failing to pay. The transaction is instant, automatic and final (once confirmed in a Bitcoin blockchain block).<br /> <br /> This type of swap could be done with any Bitcoin coloured coin.<br /> <br /> Currently only BSQ to BTC is available.</div>

Flix21 https://bisq.wiki/index.php?title=Howto&diff=3171 2023-02-20T12:47:59Z

<p>Flix21: </p> <hr /> <div>List of short how-to guides for new Bisq users:<br /> <br /> 1. Getting started<br /> <br /> *[[How to back up your Bisq wallet seed]]<br /> *[[Set up a Revolut payment account]] <br /> *[[Set up a SEPA payment account]] (EUR)<br /> *[[Set up a Zelle payment account]] (USD)<br /> *[[Set up a INTERAC e-tranfer payment account]] (CAD)<br /> *[[Set up a UK Faster Payments account]] (GBP)<br /> *[[Set up a National bank transfer account]] (BRL)<br /> *How to back up your payment accounts on Bisq<br /> <br /> 2. Trade<br /> <br /> *[[How to buy BSQ on Bisq]]<br /> *[[How to buy BTC on Bisq with EUR]]<br /> *[[How to buy BTC on Bisq with CAD]]<br /> *How to buy BTC on Bisq with USD<br /> *[[How to buy ETH on Bisq]]<br /> *[[How to buy USDT on Bisq]]<br /> *[[How to buy XMR on Bisq]]<br /> *[[How to buy BTC on Bisq with CNY]]<br /> *[[How to buy BTC on Bisq with NGN]]<br /> *[[How to buy BTC on Bisq with INR]]<br /> *[[How to buy BTC on Bisq with ARS]]<br /> *[[How to sell BSQ on Bisq]]<br /> *[[How to sell BTC on Bisq with EUR]]<br /> *How to sell BTC on Bisq with USD<br /> *[[How to sell USDT on Bisq]]<br /> *[[How to sell XMR on Bisq]]<br /> *[[How to create an offer to buy BTC with EUR]]<br /> *[[How to create an offer to sell BTC with EUR]]<br /> <br /> 3. Contribute<br /> *[[How to be a market maker on Bisq]]<br /> *[[How to do arbitrage on Bisq]]<br /> *[[How to do remittance on Bisq]]<br /> *Educational resources<br /> *Marketing<br /> *How to be a developer on Bisq<br /> *How to make a compensation request on Bisq<br /> <br /> 4. DAO<br /> *How to vote on the Bisq DAO<br /> *How to make a proposal on the Bisq DAO<br /> <br /> ==Bitcoin Wisdom==<br /> *DON'T TRUST. VERIFY.<br /> *Trusted Third Parties are security holes.<br /> *Not your keys, not your coins.<br /> *Vires in numeris.</div>

Flix21 https://bisq.wiki/index.php?title=Ubiquitous_law_enforcement&diff=3129 2023-01-24T12:51:18Z

<p>Flix21: </p> <hr /> <div>Ubiquitous law enforcement is a system that embeds government code into every connected appliance, hardware, vehicle, etc. It allows the highest degree imaginable of totalitarian rule. It allows for the complete suppression of individual rights and the instant subordination of every single person under it to the decrees of authoritarian rulers. It facilitates total surveillance of the population as every single piece of hardware and software becomes a government spy and enforcer.<br /> <br /> Similarly to previous historical attempts at totalitarian rule it eventually leads to societal collapse as even the most advanced AI cannot solve the [[economic calculation problem]]. The decentralised nature of information in society requires bottom-up feedback mechanisms which are severely impeded by [[central economic planning]].<br /> <br /> == See Also ==<br /> *[[UBI]]<br /> *[[social credit system]]<br /> *[[CBDC]]<br /> *[[surveillance]]</div>

Flix21 https://bisq.wiki/index.php?title=CBDC&diff=3128 2023-01-24T12:47:19Z

<p>Flix21: </p> <hr /> <div>CBDC (Central Bank Digital Currency) is the final and most insidious form of [[fiat]] money, since as programmable money it allows a much higher degree of control, including geofencing, time limits, restrictions on saving, blacklisting, censorship, etc. It can potentially lead to [[ubiquitous law enforcement]] and facilitate social credit systems.<br /> <br /> <br /> == External links ==<br /> <br /> *CBDCtracker [https://www.atlanticcouncil.org/cbdctracker/ cbdctracker] lets you see how CBDC implementation around the world is advancing.</div>

Flix21 https://bisq.wiki/index.php?title=CBDC&diff=3127 2023-01-24T12:46:31Z

<p>Flix21: </p> <hr /> <div>CBDC (Central Bank Digital Currency) is the final and most insidious form of [[fiat]] money, since as programmable money it allows a much higher degree of control, including geofencing, time limits, restrictions on saving, blacklisting, etc. It can potentially lead to [[ubiquitous law enforcement]] and facilitate social credit systems.<br /> <br /> <br /> == External links ==<br /> <br /> *CBDCtracker [https://www.atlanticcouncil.org/cbdctracker/ cbdctracker] lets you see how CBDC implementation around the world is advancing.</div>

Flix21 https://bisq.wiki/index.php?title=FOSS&diff=3105 2023-01-17T15:04:49Z

<p>Flix21: </p> <hr /> <div>Free and open-source software (FOSS) is a term used to refer to groups of software consisting of both free software and open-source software where anyone is freely licensed to use, copy, study, and change the software in any way, and the source code is openly shared so that people are encouraged to voluntarily improve the design of the software. This is in contrast to proprietary software, where the software is under restrictive copyright licensing and the source code is usually hidden from the users.<br /> <br /> [[Bitcoin]] and [[Linux]] are examples of successful FOSS projects.<br /> <br /> Bisq is FOSS.</div>

Flix21