-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bisq Bitcoinj Fork Maintainer #8
Comments
2018.04 reportFollowing roughly the BitcoinJ mailinglist or updates about Segwit. Seems there is still no release in sight. Looking out for a dedicated developer for the Bitcoin part, but so far nobody has showed up. |
2018.05 reportUpdated BitcoinJ to fix a wrong value for dust limit and filter out the confusing alert warning caused by old bitcoin nodes. Followed a bit discussion on the Bitcoin mailing list where they are discussing to fade out support for BIP 37 (bloom filter). |
2018.06 reportBeside a small commit for a log level change nothing to report. |
Update: Acting as @bisq-github-admin-1, I've set up access rights to our Bitcoinj fork, as well as our libdohj and btcd-cli4j forks such that @bisq-network/core-maintainers have write access to the repositories. This was to cut down on creating additional GitHub teams where they're not really necessary, and to reflect the fact that in practice, it is the core maintainers (particularly @ManfredKarrer as primary) who are caring for these forks for the time being. Assuming someone does come along to take care of our Bitcoinj fork, we can set up a dedicated team at that time. The description of this role issue has been updated to reflect. |
2018.07 reportNothing to report. |
2018.08 reportWe reverted a code change done in January to improve the broadcast reliability. As it turned out that change had the opposite effect for unknown reasons. |
2018.09 reportFixed an issue with duplicated peers in case of disconnections and re-connections. |
2018.10 reportNothing to report. |
2018.11 reportNothing to report. |
2018.11 reportCoordinate with @oscarguindzberg update to 0.14.7 and review of Bisq changes. |
2019.01 reportNothing to report. |
2019.02 reportNothing to report. |
2019.03 reportAudits:
Other improvements:
Research/exploratory tasks:
|
2019.04 report
|
I'd be happy to help out with this role. I'm interested in contributing to bisq and think adding support for segwit would be a good first task for me to tackle. |
@bodymindarts glad you are interested, don't forget about the existing bisq fork of bitcoinj (https://github.com/bisq-network/bitcoinj) and the segwit code which is either in a PR or merged. |
@bodymindarts there is a PR for bisq's updated bitcoinj at bisq-network/bisq#2772 |
After discussing with @ManfredKarrer it seems preferable as a long term strategy to reduce the dependency on bitcoinj as much as possible. To accelerate that I am investigating bisq-network/proposals#32 which may enable us to remove large section of wallet functionality. This seems like a better activity for the longterm than putting effort into something that ideally should be removed anyway. |
I've removed @oscarguindzberg as the assignee for this role as there have been no cycle updates since 2019.04 and I'm leaving it unassigned to reflect the reality that no one is owning this role at the current time. I've also re-added the |
@cbeams discussions with the chimp at the time indicated that updating bitcoinj was so arduous and time-consuming (at least for the purpose of supporting segwit) that it didn't make sense to make it a priority given all the other high priorities of the project. The Bisq v2 proposal from that time was also a consideration (i.e., seemed better to spend resources to develop and build that instead of maintaining bitcoinj in Bisq v1). I think 1 or 2 folks had come by expressing interest in the role (not sure how serious) and weren't met with a whole lot of interest. Taking all of this into account, it didn't make sense to keep the role marked as |
This role has been repurposed for Bisq 2 Security Manager |
This role is responsible for maintaining Bisq's fork of bitcoinj at https://github.com/bisq-network/bitcoinj. This includes but is not limited to doing big, valuable work like implementing Bisq's needs around SegWit and integrating that support into Bisq (see bisq-network/bisq#1139).
This role is (or at least can be) more than narrowly bitcoinj-specific: we need one or more contributors to can stay on top of all Bisq's Bitcoin needs, to stay abreast of what's happening at the protocol level, to get proactive about things.
Note that Bisq also maintains a federation of Bitcoin Core nodes as a service to its users for the purpose of mitigating privacy risk caused by bitcoinj's approach to bloom filter-based SPV. The contributor playing this role could also become one of the @bisq-network/btcnode-maintainers (see #66) and help tune settings for all the nodes in our federation, maintain common
bitcoin.conf
files for the set of @bisq-network/btcnode-operators (#67) that run them, etc.Docs: none, other than the above
Team: @bisq-network/core-maintainers
Primary owner: @oscarguindzberg
The text was updated successfully, but these errors were encountered: