Topic: [ANN] Joinmarket - Coinjoin that people will actually use - page 4. (Read 85018 times)
Wonder how Zcash will affect these types of services.
I have noticed blockr.io being slow lately too because I was using them for testnet.
Can u still use it (Coinjoin) without downloading anything to your HD?Is the IRC room still working? How do we access the irc chat? I've never used irc before.
You have to download joinmarket itself but its only a few kb. You need to download and install some dependencies like libsecp256k1 and libsodium, they're not too large either.
If you're talking about downloading the blockchain, you get much better privacy if you run a full node. If you enable blockchain pruning you don't need to store it on your hard disk so your disk usage is much lower.
Hmmm very interesting. Is there any simpler guide to using CoinJoin or something? I'd very much like to use this
All the user tutorials are on the wiki
https://github.com/joinmarket-org/joinmarket/wiki
Hmmm very interesting. Is there any simpler guide to using CoinJoin or something? I'd very much like to use this
It is an interesting concept and one I have not heard of yet before. I am glad I read about this. I see there are some devs that dont just copy another Dev. 
Good to know and also nice that you can make an investment here.
Good to know and also nice that you can make an investment here. I have noticed blockr.io being slow lately too because I was using them for testnet.
Can u still use it (Coinjoin) without downloading anything to your HD?Is the IRC room still working? How do we access the irc chat? I've never used irc before.
An article on JoinMarket, although I would have preferred it if the final article mentioned joinmarket in the title
https://cointelegraph.com/news/mixing-your-bitcoin-with-other-peoples-btc-brings-risks-and-possibilities
Feedback / criticism welcome.
https://cointelegraph.com/news/mixing-your-bitcoin-with-other-peoples-btc-brings-risks-and-possibilities
Feedback / criticism welcome.
I have noticed blockr.io being slow lately too because I was using them for testnet.
When I run wallet-tool.py, it takes an insanely long time to give me the results.
This wasn't the case a week back. Has something changed at blockr.io's end in the past 1 week?
Or is it a problem just with my internet connection?
How does the speed vary with increase in number of addresses in your wallet?
This wasn't the case a week back. Has something changed at blockr.io's end in the past 1 week?
Or is it a problem just with my internet connection?
How does the speed vary with increase in number of addresses in your wallet?
In the case of Core, there is --fast to speed it up, but in the case of blockr.io it may indeed be some kind of connection problem to them. The only other possibility is if you've done a large number of transactions, which will slow it down for sure, but hopefully not "insane"-ly.
I am not using core. I have done a large number of transactions (the address count is in the 1000s - mostly used).
It takes me ~half an hour to get the output. This was not the case last week....
When I run wallet-tool.py, it takes an insanely long time to give me the results.
This wasn't the case a week back. Has something changed at blockr.io's end in the past 1 week?
Or is it a problem just with my internet connection?
How does the speed vary with increase in number of addresses in your wallet?
This wasn't the case a week back. Has something changed at blockr.io's end in the past 1 week?
Or is it a problem just with my internet connection?
How does the speed vary with increase in number of addresses in your wallet?
In the case of Core, there is --fast to speed it up, but in the case of blockr.io it may indeed be some kind of connection problem to them. The only other possibility is if you've done a large number of transactions, which will slow it down for sure, but hopefully not "insane"-ly.
When I run wallet-tool.py, it takes an insanely long time to give me the results.
This wasn't the case a week back. Has something changed at blockr.io's end in the past 1 week?
Or is it a problem just with my internet connection?
How does the speed vary with increase in number of addresses in your wallet?
This wasn't the case a week back. Has something changed at blockr.io's end in the past 1 week?
Or is it a problem just with my internet connection?
How does the speed vary with increase in number of addresses in your wallet?
New release version 0.2.2
================
This is a minor release, but highly recommended with new features and bugfixes. See the release notes: https://github.com/JoinMarket-Org/joinmarket/blob/master/doc/release-notes-0.2.2.md
Latest version is always at https://github.com/JoinMarket-Org/joinmarket/releases/
Biggest thing is providing a feature that makes failure-to-complete transactions less likely, but there are other useful things, release notes summarizes these.
Thanks!
================
This is a minor release, but highly recommended with new features and bugfixes. See the release notes: https://github.com/JoinMarket-Org/joinmarket/blob/master/doc/release-notes-0.2.2.md
Latest version is always at https://github.com/JoinMarket-Org/joinmarket/releases/
Biggest thing is providing a feature that makes failure-to-complete transactions less likely, but there are other useful things, release notes summarizes these.
Thanks!
Question on the electrum plugin....
https://github.com/AdamISZ/electrum-joinmarket-plugin
Are there any changes to this (including bugfix mentioned in step 4)?
The plugin talks about Electrum 2.6.4
The wallet file format has changed with Electrum 2.7......
https://github.com/AdamISZ/electrum-joinmarket-plugin
Are there any changes to this (including bugfix mentioned in step 4)?
The plugin talks about Electrum 2.6.4
The wallet file format has changed with Electrum 2.7......
1. The plugin has not been updated for the new version of JM, so is not usable right now.
2. The new version of Electrum fixes the bug that had to be manually fixed in those install instructions, but for now this is irrelevant because of 1.
3. I am overwhelmed with working on Joinmarket itself, so I have no time to update this, I expect it will be a couple of months before this is re-addressed, and when it is, I'm not sure in what way. If someone else wants to do more work on it I'd be happy to answer questions.
4. I don't know about wallet file format changes; the plugin as-was was only supporting "Standard" wallets fwiw.
Question on the electrum plugin....
https://github.com/AdamISZ/electrum-joinmarket-plugin
Are there any changes to this (including bugfix mentioned in step 4)?
The plugin talks about Electrum 2.6.4
The wallet file format has changed with Electrum 2.7......
https://github.com/AdamISZ/electrum-joinmarket-plugin
Are there any changes to this (including bugfix mentioned in step 4)?
The plugin talks about Electrum 2.6.4
The wallet file format has changed with Electrum 2.7......
JoinMarket talk at Scaling Bitcoin 2016: https://www.youtube.com/watch?v=8BLWUUPfh2Q&feature=youtu.be&t=2196
transcript: https://scalingbitcoin.org/transcript/milan2016/joinmarket
transcript: https://scalingbitcoin.org/transcript/milan2016/joinmarket
New release version 0.2.1
================
This is a bugfix release. See the release notes: https://github.com/JoinMarket-Org/joinmarket/blob/master/doc/release-notes-0.2.1.md
Latest version is always at https://github.com/JoinMarket-Org/joinmarket/releases/
The most important fixes are for Windows; the secp256k1 binding was broken for obscure reasons and didn't allow bots to run correctly. But there are a couple of other fixes that are important dependent on your exact use-case, so update ASAP.
Most important: if you haven't yet updated from pre-0.2, follow the upgrading instructions in the 0.2.0 (see previous post). If you are already on 0.2.0, you just need to git pull or download the new zip.
Thanks!
================
This is a bugfix release. See the release notes: https://github.com/JoinMarket-Org/joinmarket/blob/master/doc/release-notes-0.2.1.md
Latest version is always at https://github.com/JoinMarket-Org/joinmarket/releases/
The most important fixes are for Windows; the secp256k1 binding was broken for obscure reasons and didn't allow bots to run correctly. But there are a couple of other fixes that are important dependent on your exact use-case, so update ASAP.
Most important: if you haven't yet updated from pre-0.2, follow the upgrading instructions in the 0.2.0 (see previous post). If you are already on 0.2.0, you just need to git pull or download the new zip.
Thanks!
New release version 0.2.0
================
Best place to start is the release notes - in particular for existing users, please read up to and including "Notable changes".
Then follow the installation/upgrade guide on the frontpage/readmewhich has of course changed a bit. The most notable change is that the libsecp256k1 binding is now required, not optional.
In terms of how the experience of Joinmarket changes, this section is the most important, giving a short summary of what changes for Makers and Takers, and the wiki article linked inside gives more details, for Takers (that's sendpayment or tumbler basically). In short, they will have to change their wallet funding behaviour a bit, and in some cases be more patient (or use more expert tools).
There are some superficial changes (like nicknames) that are there to support using multiple IRC servers. Currently CgAn is kept as the default, but you can add other IRC servers if you like. If the community of users can come up with another fully Tor-supporting and stable IRC server that will allow Joinmarket usage, we could come to a general agreement on that. The code now happily supports at least 3 different servers simultaneously, probably more although I haven't tried. The idea of this is to improve censorship-resistance and reliability, but for now we just have the one default still.
This is a breaking change in the protocol, unlike previous releases - that means, while old and new bots can happily live on the same channel, they will ignore each other. So please upgrade as soon as you can, and don't be surprised if there is some disruption in the meanwhile.
Lastly, there are now only two yield generator bots offered within the codebase - yield-generator-basic.py and yg-pe.py (short for privacy enhancement). The rationale for removing the others I've mentioned elsewhere, but will repeat here:
"it's a combination of 3 things i guess; 1/it's too much work trying to support them 2/there is nothing wrong with them being used and maintained separately 3/i'd quite like to prod people towards running just the simple two versions mentioned for the new version, as those simpler ones are giving away less info to snoopers; but that last point is up for discussion"
A final overall point - this is a substantial, disruptive change and not one that makes usage easier. But, let's not forget that the existing Joinmarket is fundamentally broken in as much as there is no realistic privacy guarantee in any mode of usage. While this change intends to ameliorate this problem, it most likely will not remove it entirely, and its best benefits will only be seen if the level of usage increases considerably, which is likely a way off. So I hope people can be patient!
Please feel free to ask questions here or preferably on reddit (it's easier to keep track of one location). Or IRC of course.
================
Best place to start is the release notes - in particular for existing users, please read up to and including "Notable changes".
Then follow the installation/upgrade guide on the frontpage/readmewhich has of course changed a bit. The most notable change is that the libsecp256k1 binding is now required, not optional.
In terms of how the experience of Joinmarket changes, this section is the most important, giving a short summary of what changes for Makers and Takers, and the wiki article linked inside gives more details, for Takers (that's sendpayment or tumbler basically). In short, they will have to change their wallet funding behaviour a bit, and in some cases be more patient (or use more expert tools).
There are some superficial changes (like nicknames) that are there to support using multiple IRC servers. Currently CgAn is kept as the default, but you can add other IRC servers if you like. If the community of users can come up with another fully Tor-supporting and stable IRC server that will allow Joinmarket usage, we could come to a general agreement on that. The code now happily supports at least 3 different servers simultaneously, probably more although I haven't tried. The idea of this is to improve censorship-resistance and reliability, but for now we just have the one default still.
This is a breaking change in the protocol, unlike previous releases - that means, while old and new bots can happily live on the same channel, they will ignore each other. So please upgrade as soon as you can, and don't be surprised if there is some disruption in the meanwhile.
Lastly, there are now only two yield generator bots offered within the codebase - yield-generator-basic.py and yg-pe.py (short for privacy enhancement). The rationale for removing the others I've mentioned elsewhere, but will repeat here:
"it's a combination of 3 things i guess; 1/it's too much work trying to support them 2/there is nothing wrong with them being used and maintained separately 3/i'd quite like to prod people towards running just the simple two versions mentioned for the new version, as those simpler ones are giving away less info to snoopers; but that last point is up for discussion"
A final overall point - this is a substantial, disruptive change and not one that makes usage easier. But, let's not forget that the existing Joinmarket is fundamentally broken in as much as there is no realistic privacy guarantee in any mode of usage. While this change intends to ameliorate this problem, it most likely will not remove it entirely, and its best benefits will only be seen if the level of usage increases considerably, which is likely a way off. So I hope people can be patient!
Please feel free to ask questions here or preferably on reddit (it's easier to keep track of one location). Or IRC of course.
Using create-unsigned-tx.py I get a
"TypeError: Non-hexadecimal digit found"
after I input the corresponding private key for the auth UTXO.
Code:
Traceback (most recent call last):
File "create-unsigned-tx.py", line 300, in
main()
File "create-unsigned-tx.py", line 262, in main
magicbyte=get_p2pk_vbyte()):
File "/home/mint/Desktop/joinmarket-0.1.4/bitcoin/secp256k1_main.py", line 18, in privkey_to_address
return pubkey_to_address(privkey_to_pubkey(priv, from_hex), magicbyte)
File "/home/mint/Desktop/joinmarket-0.1.4/bitcoin/secp256k1_main.py", line 269, in privkey_to_pubkey
return privkey_to_pubkey_inner(priv, usehex)
File "/home/mint/Desktop/joinmarket-0.1.4/bitcoin/secp256k1_main.py", line 228, in func_wrapper
newargs += [arg.decode('hex')]
File "/usr/lib/python2.7/encodings/hex_codec.py", line 42, in hex_decode
output = binascii.a2b_hex(input)
TypeError: Non-hexadecimal digit found
File "create-unsigned-tx.py", line 300, in
main()
File "create-unsigned-tx.py", line 262, in main
magicbyte=get_p2pk_vbyte()):
File "/home/mint/Desktop/joinmarket-0.1.4/bitcoin/secp256k1_main.py", line 18, in privkey_to_address
return pubkey_to_address(privkey_to_pubkey(priv, from_hex), magicbyte)
File "/home/mint/Desktop/joinmarket-0.1.4/bitcoin/secp256k1_main.py", line 269, in privkey_to_pubkey
return privkey_to_pubkey_inner(priv, usehex)
File "/home/mint/Desktop/joinmarket-0.1.4/bitcoin/secp256k1_main.py", line 228, in func_wrapper
newargs += [arg.decode('hex')]
File "/usr/lib/python2.7/encodings/hex_codec.py", line 42, in hex_decode
output = binascii.a2b_hex(input)
TypeError: Non-hexadecimal digit found
Also tried using the testnet example from the github wiki and got the same error.
https://www.reddit.com/r/joinmarket/comments/4x7jqp/who_is_not_using_the_secp256k1_binding/ (response there rather than here is preferred, I visit there more often).
ABISprotocol, thanks.
Some links:
https://joinmarket.me/blog/blog/racing-against-snoopers-in-joinmarket-02/ this is to help people to understand the complicated situation re: the privacy attack and what we're trying to do to defend it. There are two previous posts on the blog (https://joinmarket.me/blog/blog/poodle/ and https://joinmarket.me/blog/blog/joinmarket-020-changes/) but bear in mind they dive into nitty gritty which most people probably won't want to read all of.
Testnet pit orderbook at: https://joinmarket.me/obtest/ .. I'm hoping that some more people with join so we can get more realistic tests. Things seem to be working OK for now but that's just basic functionality, to test the defence requires more bots.
For those more development oriented, progress is being logged here: https://github.com/JoinMarket-Org/joinmarket/issues/171 on the branch https://github.com/JoinMarket-Org/joinmarket/tree/0.2.0 . It seems like the protocol updates are basically finished now, there is a protocol description here https://gist.github.com/AdamISZ/baf93ce2589854a7992383b3c69fae13
Some links:
https://joinmarket.me/blog/blog/racing-against-snoopers-in-joinmarket-02/ this is to help people to understand the complicated situation re: the privacy attack and what we're trying to do to defend it. There are two previous posts on the blog (https://joinmarket.me/blog/blog/poodle/ and https://joinmarket.me/blog/blog/joinmarket-020-changes/) but bear in mind they dive into nitty gritty which most people probably won't want to read all of.
Testnet pit orderbook at: https://joinmarket.me/obtest/ .. I'm hoping that some more people with join so we can get more realistic tests. Things seem to be working OK for now but that's just basic functionality, to test the defence requires more bots.
For those more development oriented, progress is being logged here: https://github.com/JoinMarket-Org/joinmarket/issues/171 on the branch https://github.com/JoinMarket-Org/joinmarket/tree/0.2.0 . It seems like the protocol updates are basically finished now, there is a protocol description here https://gist.github.com/AdamISZ/baf93ce2589854a7992383b3c69fae13
In the spirit of "Coinjoin that people will actually use", I'm wondering if any of the regular bitcoin wallets have integrated joinmarket, or have announced any plans to do so?
Along these lines...
Is there a joinmarket API that would make it straightforward for a wallet to integrate?
Has any effort been made to approach wallet makers?
If not, perhaps we should open issues requesting joinmarket support on their respective github pages.
Along these lines...
Is there a joinmarket API that would make it straightforward for a wallet to integrate?
Has any effort been made to approach wallet makers?
If not, perhaps we should open issues requesting joinmarket support on their respective github pages.
IMO joinmarket is at too early of a stage for this, there are still a few problems that would be nice to fix before anything happens.
Right now it seems most of the adoption comes from people using the tumbler script.
First, for danda, it's worth noting that this has been very extensively investigated/discussed for more than a year. Also worth noting is that, to the surprise of no one, when Joinmarket was first widely announced in public, the most common response was "please make this appear in my wallet, or at least in some wallet". Again, I emphasize: to the surprise of no one, we know that that's what people prefer.
Second, w.r.t belcher's "too early a stage": it's difficult to make a general statement. It's true that there are aspects of how joinmarket works that can make it awkward to integrate it into a wallet; things like, HD structure (mixdepths, see below), approach to E2E encryption of messages, code language, packaging etc. But I don't think there's some fundamental problem making it impossible, especially if you restrict the scope, and especially if the wallet code has its own model for integration.
Which brings me to:
For those reading who are interested in such things (wallet integrations), let me point you at: https://www.reddit.com/r/joinmarket/comments/4m1b7r/requesting_linux_testers_for_an_experimental/ which links to an Electrum plugin for testing. Install is multi-step (but not complex) for reasons described in the post, but if anyone here's willing to give it a test would appreciate it. It allows the creation of coinjoins (sendpayments) directly from your Electrum wallet (only "Standard" type).
I've gotten only 1 person so far after more than a week who even installed it, which is disappointing after *so* many requests in the early days to do an Electrum plugin.
Electrum accounts within a standard BIP32 HD wallet are exactly like Joinmarket mixdepths, so a natural extension to that plugin (which for now just does sendpayment) is to implement that, and eventually I'd hope, something like tumbler could be programmed (mixdepths->accounts). Obviating the need for any separate wallet management for *users* of Joinmarket (takers). Providers, i.e. makers, should be using Core and joinmarket's own wallet and script set up probably (although there is the dream of passively acting as maker from your own wallet, maybe that's possible too).
So... I just heard about this (the electrum joinmarket plugin to help people do the CoinJoin (JoinMarket) more easily):
https://github.com/AdamISZ/electrum-joinmarket-plugin
Thank you, and I'm going to try this very soon (within the next few days).
I've also just posted it to my diaspora: https://diasp.org/posts/5743008
-ABISprotocol
Just saw this -- https://www.reddit.com/r/joinmarket/comments/4vm2h9/volunteers_for_testnet_testing_of_020_version/ which appears to be a way to test the new version to fix the privacy concerns and issues that have been recently raised! I definitely encourage people to participate in this testing, and am posting this to my diaspora..
https://diasp.org/posts/5743008
Jump to: