Pages:
Author

Topic: [ANN] Joinmarket - Coinjoin that people will actually use - page 6. (Read 84864 times)

sr. member
Activity: 469
Merit: 253
The JoinMarket IRC channel so far was hosted on freenode, which is very unfriendly to tor users.

So I've set up an IRC relaying bot between the freenode channel and a channel on cyberguerrilla which is far more friendly to tor.

Tor Details:

Code:
channel = #joinmarket
host = 6dvj6v5imhny3anf.onion
port = 6697
ssl enabled

Just for clarification: this is referring to the IRC channel we use to *chat*, not the IRC channel(s) we use for joinmarket orders/joining activity (what we call the "pit" like trading pit).
sr. member
Activity: 261
Merit: 518
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.



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.
full member
Activity: 201
Merit: 157
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.

newbie
Activity: 19
Merit: 0
Looks like  alot of the bumps are getting smoothed out along with more volume. Steep learning curve but im catching on.
sr. member
Activity: 261
Merit: 518
The JoinMarket IRC channel so far was hosted on freenode, which is very unfriendly to tor users.

So I've set up an IRC relaying bot between the freenode channel and a channel on cyberguerrilla which is far more friendly to tor.

Tor Details:

Code:
channel = #joinmarket
host = 6dvj6v5imhny3anf.onion
port = 6697
ssl enabled
full member
Activity: 201
Merit: 157
Hi, I found the output of wallet-tool.py hard to read so I made a patch that formats the output into text tables with borders.

Here's a very basic example:

Code:
+-----------+---------------+
| Mix Depth | Balance       |
+-----------+---------------+
|         0 | 0.34898343btc |
|         1 | 0.23468934btc |
|         2 | 0.23123434btc |
|         3 | 0.82397493btc |
|         4 | 0.22356223btc |
+-----------+---------------+
| total:    | 1.84839232btc |
+-----------+---------------+

Wallet addrs and history are also in tables.

Pull request is here:  
https://github.com/JoinMarket-Org/joinmarket/pull/539

If anyone wishes to try it before the pull request is approved, you could clone from my repo at:
https://github.com/dan-da/joinmarket
sr. member
Activity: 261
Merit: 518
JoinMarket v0.1.4 has a new feature that calculates your effective interest rate from running a yield generator, as though it was a bank account.

https://github.com/JoinMarket-Org/joinmarket/blob/master/doc/release-notes-0.1.4.md#wallet-history

To use, configure JoinMarket to use a Bitcoin node as a method of accessing the blockchain and run:

Code:
python wallet-tool.py wallet.json history

It takes into account all your deposits and withdrawals, so it should calculate the rate even if you were adding to your wallet or spending from it.

For my own yield generator wallet the figure is 0.67% per annum. I've been running it since the very start including when very few people used JoinMarket, so you can expect my yield to be on the low end.

grubles tried this and got 3.2% as an effective interest rate. I assume he's been running it for less time.

Whats your yield ?



https://www.reddit.com/r/joinmarket/comments/4hwwa0/calculate_your_yield_generators_perannum_return/

I'm aiming to get more people running yield generators.

Riding the pump-and-dump rollercoaster of Eth/TheDAO and similar is ultra high risk/reward, JoinMarket is more aiming for the slow and steady winning the race.

Earning about 1% per annum in a deflationary currency with basically zero risk where you can withdraw your money at any time must be unique in the cryptocurrency space.
sr. member
Activity: 469
Merit: 253
Joinmarket-Qt update to the new version: https://github.com/JoinMarket-Org/JMBinary/releases

, plus some bits and pieces mentioned in the reddit comment here:

https://www.reddit.com/r/joinmarket/comments/4hsaz9/joinmarket_v014_released/d2u4xv8
full member
Activity: 138
Merit: 102
Maker broadcast, Bitcoin crypto, will surely join some join.
legendary
Activity: 2128
Merit: 1120
 
Congrats for the new version.
sr. member
Activity: 261
Merit: 518
JoinMarket v0.1.4 released!

https://github.com/JoinMarket-Org/joinmarket/blob/master/doc/release-notes-0.1.4.md


We will be signing our git commits.

You can check them like this link

Import my GPG public key (do the same for other developers like waxwing)

Clone the repository and verify

Code:
    $ git clone https://github.com/JoinMarket-Org/joinmarket.git my-joinmarket-folder
    $ cd my-joinmarket-folder
    $ git log --show-signature

It should show

Code:
    commit f169351c1dc8e9b485f4b00366fc8f94b1773e0a
    gpg: Signature made Wed 04 May 2016 01:50:53 BST using RSA key ID 77F31129
    gpg: Good signature from "Chris Belcher "
    Merge: d1092f5 809b654
    Author: chris-belcher
    Date:   Wed May 4 01:50:45 2016 +0100

git commits are a chain of hashes, so one signed commit at the top is enough to verify all the ones below it.
sr. member
Activity: 261
Merit: 518
Please complete this questionnaire on how you use JoinMarket. (Should take only 60 seconds)

http://surveynuts.com/surveys/take?id=57841&c=716997053JRPF

The results are here:

https://surveynuts.com/surveys/admin?id=57841&stoken=8933114612517§ion=results

Thanks to everyone who answered!
member
Activity: 63
Merit: 14

I had the same issue some time ago - the short answer is that the JoinMarket protocol requires you to have the target address of a join in your wallet.  I. e., patientsendpayment only works if you send to yourself, and then only if you import the target address into your JoinMarket wallet.  I think there is some incentive to change the protocol to make it work as originally envisioned, but I don't think that actual work is already done on that.

Thanks, that's good to know.

I've also talked to belcher about this error from bitcoind's debug.log:

Quote
2016-04-17 11:41:45 AddToWallet   update
2016-04-17 11:41:45 runCommand error: system(curl -sI --connect-timeout 1 http://localhost:62602/walletnotify?) returned 1792

This occurs when a new transaction is detected, which was sent externally (e.g. not part of a joinmarket-transaction) to the joinmarket-wallet. This error can safely be ignored. If a yield-generator is running, he won't see the funds though until restarted.
legendary
Activity: 1135
Merit: 1161
My patientsendpayments seems to crash every time someone actually tries to initiate a transaction.
First I assumed there might have been some communication problem, but now this has happend two times in a row making that reason unlikely.

I had the same issue some time ago - the short answer is that the JoinMarket protocol requires you to have the target address of a join in your wallet.  I. e., patientsendpayment only works if you send to yourself, and then only if you import the target address into your JoinMarket wallet.  I think there is some incentive to change the protocol to make it work as originally envisioned, but I don't think that actual work is already done on that.

In my case, this was not much of an issue, since I wanted to use that for internal wallet restructuring and sent to myself.  Importing the target address' private key into JoinMarket made it work.  Not sure if that is an option for you, though.
member
Activity: 63
Merit: 14
My patientsendpayments seems to crash every time someone actually tries to initiate a transaction.
First I assumed there might have been some communication problem, but now this has happend two times in a row making that reason unlikely.

Running Debian Jessy, Joinmarket with bitcoind, both over TOR. Start command:
python patientsendpayment.py -f 5000 -w 48 -c 5000 wallet.json 1000000

There's >0.1btc in mixing level 0 of the wallet, the payment to be sent was 0.01 btc.

Debug log:

Code:
2016-04-17 10:45:42,171 [MainThread  ] [DEBUG]  new cjorder nick=TakerNickName oid=0 amount=279749
2016-04-17 10:45:42,171 [MainThread  ] [DEBUG]  get_utxos_by_mixdepth =
{0: {u':1': {'address': u'',
                                                                             'value': 12000000}}}
2016-04-17 10:45:42,171 [MainThread  ] [DEBUG]  for mixdepth=0 amount=279749 selected:
2016-04-17 10:45:42,171 [MainThread  ] [DEBUG]  [{'utxo': u':1',
  'value': 15000000}]
2016-04-17 10:45:42,196 [MainThread  ] [DEBUG]  maker utxos = {u':1': {'address': u'',
                                                                         'value': 12000000}}
2016-04-17 10:45:42,362 [MainThread  ] [DEBUG]  >>privmsg nick=TakerNickName cmd=pubkey msg=
2016-04-17 10:45:45,301 [MainThread  ] [DEBUG]  <2016-04-17 10:45:45,317 [MainThread  ] [DEBUG]  CRASHING, DUMPING EVERYTHING
2016-04-17 10:45:45,317 [MainThread  ] [DEBUG]  Class debug dump, name:Wallet
2016-04-17 10:45:45,317 [MainThread  ] [DEBUG]  key=unspent
2016-04-17 10:45:45,317 [MainThread  ] [DEBUG]  {u':1': {'address': u'',
                                                                         'value': 12000000}}
2016-04-17 10:45:45,317 [MainThread  ] [DEBUG]  key=gaplimit
2016-04-17 10:45:45,318 [MainThread  ] [DEBUG]  6
2016-04-17 10:45:45,318 [MainThread  ] [DEBUG]  key=index
2016-04-17 10:45:45,318 [MainThread  ] [DEBUG]  [[2, 1]]
2016-04-17 10:45:45,318 [MainThread  ] [DEBUG]  key=index_cache
2016-04-17 10:45:45,318 [MainThread  ] [DEBUG]  [[2, 1]]
2016-04-17 10:45:45,318 [MainThread  ] [DEBUG]  key=spent_utxos
2016-04-17 10:45:45,318 [MainThread  ] [DEBUG]  []
2016-04-17 10:45:45,318 [MainThread  ] [DEBUG]  key=utxo_selector
2016-04-17 10:45:45,318 [MainThread  ] [DEBUG]  
2016-04-17 10:45:45,318 [MainThread  ] [DEBUG]  key=path
2016-04-17 10:45:45,318 [MainThread  ] [DEBUG]  string: len:19
2016-04-17 10:45:45,318 [MainThread  ] [DEBUG]  wallets/wallet.json
2016-04-17 10:45:45,319 [MainThread  ] [DEBUG]  key=storepassword
2016-04-17 10:45:45,319 [MainThread  ] [DEBUG]  False
2016-04-17 10:45:45,319 [MainThread  ] [DEBUG]  key=max_mix_depth
2016-04-17 10:45:45,319 [MainThread  ] [DEBUG]  1
2016-04-17 10:45:45,319 [MainThread  ] [DEBUG]  key=imported_privkeys
2016-04-17 10:45:45,319 [MainThread  ] [DEBUG]  {}
Traceback (most recent call last):
  File "patientsendpayment.py", line 241, in main
    irc.run()
  File "/home/username/joinmarket-develop/joinmarket/irc.py", line 657, in run
    self.__handle_line(line)
  File "/home/username/joinmarket-develop/joinmarket/irc.py", line 540, in __handle_line
    self.__handle_privmsg(_chunks[0], _chunks[2], get_irc_text(line))
  File "/home/username/joinmarket-develop/joinmarket/irc.py", line 491, in __handle_privmsg
    self.__on_privmsg(nick, parsed)
  File "/home/username/joinmarket-develop/joinmarket/irc.py", line 377, in __on_privmsg
    self.on_seen_auth(nick, i_utxo_pubkey, btc_sig)
  File "/home/username/joinmarket-develop/joinmarket/maker.py", line 253, in on_seen_auth
    self.active_orders[nick].auth_counterparty(nick, pubkey, sig)
  File "/home/username/joinmarket-develop/joinmarket/maker.py", line 96, in auth_counterparty
    btc_pub = btc.privtopub(btc_key)
  File "/home/username/joinmarket-develop/bitcoin/main.py", line 280, in privkey_to_pubkey
    f = get_privkey_format(privkey)
  File "/home/username/joinmarket-develop/bitcoin/main.py", line 191, in get_privkey_format
    elif len(priv) == 32: return 'bin'
TypeError: object of type 'NoneType' has no len()
done


Edit:
New entries in the bitcoind-debug.log as well. This I've also not seen before I I started using Joinmarkt... google didnt help with that error message:
Code:
2016-04-17 11:41:45 AddToWallet   update
2016-04-17 11:41:45 runCommand error: system(curl -sI --connect-timeout 1 http://localhost:62602/walletnotify?) returned 1792
legendary
Activity: 1862
Merit: 1105
WalletScrutiny.com
3% per year? I could just invest in a S&P mutual fund tracker if I wanted to make that much.

I wonder how you can track bitcoin and S&P at the same time though. For me, selling bitcoins to put them into whatever other economic opportunity feels stupid for me, as I'm so bullish on Bitcoin. Earning 3% on bitcoin savings though sounds great.
hero member
Activity: 630
Merit: 767
BTC⇆⚡⇄BTC
Low risk <--> Low return

No exceptions here...
full member
Activity: 224
Merit: 100
There is this script I've been working on that works out your historical effective interest rate.
https://github.com/JoinMarket-Org/joinmarket/pull/484

Me and some people who've been running for a long time get a value of about 0.7% per annum, but people who started more recently (presumably when transaction volume rose) report values of 3% or so. Also that script has bugs I can't seem to figure out so the real values might be different.

But yes if you want a get-rich-quick scheme of 100% earned per week guaranteed Wink , then JoinMarket is not for you.

3% per year? I could just invest in a S&P mutual fund tracker if I wanted to make that much.
legendary
Activity: 2940
Merit: 1330
as far as i understood one of your biggest aims in order to help people is to make their transaction fees a bit lower

Joinmarket is not at all about reducing transaction fees.

Take your off-topic big-block propaganda elsewhere please.
full member
Activity: 179
Merit: 100
thats a pretty great service i think but as far as i understood one of your biggest aims in order to help people is to make their transaction fees a bit lower, though i dont think there will be a need to do that if there will be a block size increase, in this way the fees would go down once again to normal rates
Pages:
Jump to: