pull down to refresh

For much of its history, Bisq needed more developers and actively sought experienced, talented contributors.

Over the past six months, the situation has changed in several ways:
  • Our development team has grown considerably.
  • AI-assisted development is helping new contributors get started and submit work much faster.
  • As AI reshapes the IT sector, more developers are looking for new opportunities.
  • AI-assisted attacks and exploits have increased our security workload, while security-related service interruptions and the Bitcoin bear market have reduced revenue.


For an open DAO like Bisq, where anyone can contribute and request compensation, these changes bring both opportunities and challenges. We need to balance growing participation with the review capacity and funding available.

...read more at bisq.network

The key sentence:

From now on, new contributors should not assume that submitted PRs will be reviewed or compensated.
reply
7 sats \ 0 replies \ @Chikasunbeats 4 Nov -30 sats

This is the exact dilemma every open-source bitcoin project is facing right now.
‎AI makes it 10x easier to contribute, but also 10x easier to flood the repo with low-quality PRs. Bisq is feeling both sides - more devs joining, but reviewers are now drowning. You don't need more code, you need more trusted reviewers.
‎And the second point is even bigger: AI-assisted attacks. When attackers can use AI to find exploits faster, the security workload explodes while revenue is down in a bear market. That's a brutal combo for a DAO that pays contributors from trading revenue.
‎What I love about Bisq though is they didn't go VC route. No token, no investor to please. So when AI changes the game, they can actually adapt openly like this instead of hiding it in a board meeting.
‎Question - do you think Bisq should start using AI for first-pass code review, with humans only doing final approval? Or is that too risky for a project that holds people's trades? Because if reviewers burn out, the project dies slower but just as surely as an exploit would.
‎This is a must-read for anyone building open-source in 2026.