What would be the easiest way to make this transition, that could work even for newbies who want more privacy? jamapp.org maybe?

This release includes some needed changes to address issues with Tor connections, and for this reason principally, all users should upgrade as soon as possible, and should also recreate their joinmarket.cfg file.

This release also includes corrections to transaction fee estimation for non-standard output types, fixes to sendpayment, and corrections to a few minor bugs.

The release now also includes OTS timestamp files of the gpg signatures provided, that can be verified using the opentimestamps client.

No because the block has to be changed and if you change even a single bit the final hash will be entirely different meaning it will no longer satisfy the target check so it has to be mined again.

I don't think this is intentional. To give a better answer we have to know the client the said node is running which may be acquired if your logs stored the IP address of the node that sent the invalid block. In which case we may be able to connect to that node and see if it sends its useragent and that may give us more information like the client name which we could find on GitHub and report this bug.

Is this something I can extract from my node, and if so, can you tell me how, and I'd be happy to post anything that helps?


Yes, some of the transactions I looked for are missing, but the few I found did come back as being confirmed in the real block 784121, such as these randoms transactions (1) (2) (3) I selected.


It's curious that it's happened more than once over the previous days.  If indeed this is a configuration error, which seems likely, someone is losing a fair amount of mining rewards I think.  I wonder, would it be possible for a competing miner to capture these blocks and insert their own (valid) transactions in place for broadcast?  Maybe a dumb question, lol.  In my log there were several minutes seperation from valid blocks on either side on the bogus block.

What would be the goal or take away from a malicious node broadcasting these intentionally?

Hold on there, buddy. It's important to point out that the use of any click automation bot is strictly prohibited by Freebitco.in. You can risk losing your account and any earnings if you're caught using any form of automated software. Freebitco.in takes the use of click automation bots very seriously and employs strict measures to detect and prevent their use.

Quick question: Was the IRC server down or have trouble yesterday? If so, what happened?

I had my first experience with JoinMarket yesterday morning. I decided to tumble some coins using the tumbler.py script. I started it and went to bed. When i woke up, the script was just trying to reconnect to the IRC server over and over getting a connection timed out error 110. I tried a lot of stuff but nothing worked. I could connect to the IRC server manually with HexChat but none of the scripts would. I checked again this morning and it's back up and running. I'm just curious what happened. I joined the #JoinMarket channel on FreeNode and saw 3 or 4 other people ask if the server was down but no one responded.

Thanks!

The door is made on thick iron bars with an
electronic locking mechanism.
It has a keypad.

It's a full QWERTY keypad.

An iron plated floor.
on which there is a skeleton and some rusted gears

A dusty skeleton, covered in rags.
It's wearing a jacket.

Old rusted gears.

A ratty leather jacket.
It contains a note, a map and a knife.

The note is faded and barely legible but you can make out the message:

I fear I may perish soon. The portal sent me here. Now, I'm trapped with no way out. I think this map holds the key but I can't decipher it.

A chipped and rusty knife.

I have an idea, and guys, let me know if this is decent or crazy or whatever: or if this is already what is being done by JoinMarket, Shuffle, Whatever.

1. I make a website or a server for this purpose.
2. It asks users to create their transactions, and a given time limit, say 30 minutes or 1 hour.
3. Every 30 minutes, or every hour, it gets back to all the users with the giant CoinJoin transaction formed thus far and asks all the people to sign.
4. The site itself takes a fee, and that's some how inserted into the process.
5. Assuming the site is "trustable", then only outsiders are "attackers" and they're not going to learn much except "I see 100 inputs and 200 outputs, and I own 20 of them. I dunno who the other 80 are."
6. Repeat every hour or every whenever. Or every 100 people. Or once a day.
7. Java script or open source client side signing thingy that can sign for you if you're away from your computer so the site doesn't have to wait an hour when it reaches the minimum number of people.

The other idea I had, which I mentioned a long time ago, is like a traditional mixer, in that the mixer site itself has to be trusted, but it does everything internally, and you just send your coins. Instead of the traditional mixing of unrelated inputs and outputs, it's basically a CoinJoin mixer that gets all deposits and spits out the transactions just like a traditional mixer. The only downside is having to trust the site.

This is a normal release, bringing bug fixes and new features.

The secp256k1 library can now be used in JoinMarket. It provides the very well tested and robust code used in Bitcoin for the underlying signing and ECC operations. It is recommended that everyone who is able to use secp256k1 with JoinMarket. In case it cannot be installed, joinmarket should continue to run exactly as before.

Many small bugfixes and features have been added with the aim of making the tumbler script more stable and more likely to complete the entire tumbler job without crashing

In order to help stop spies that sybil attack the bitcoin p2p network in an effort to learn the origin IP address of a transaction, JoinMarket now has a feature to ask a maker to broadcast the coinjoin transaction with their IP.

JoinMarket debug logs are very useful to developers, but because they contain private information users are often unwilling to share them publicly.

For this reason there is now a debug log scrubber script which replaces sensitive information with placeholders that allow debugging but do not ruin privacy.

The history of the internal wallet can now be displayed. For yield-generator users it can work out the effective annual interest rate, as though yield-generator was a savings account.

@CryptoImperator, I've sent you a PM regarding my order a couple of days ago.  When should I expect a response?

I had a full node, i recieved DDoS all weeks... i dont like that mi ip are visible, if i could set on tor ip i could set my node again

I wish I could figure out how to register the node I am running on my spare Windows desktop. I have port 8333 forwarding to the Qt wallet and it shows as being reachable on Bitnodes' site.