lol just received this email about our coinjoin server. we are running nothing except tor and our own software (checked processes).

-----Original Message-----

From: abuse@hetzner.de
Sent: 30 August 2013 07:54
To: XXX
Subject: Abuse Message [AbuseID:0D0482:15]: AbuseNormal: 22-102567054 Notice of
Unauthorized Use of Paramount Pictures Corporation Property

Dear Mr XXX,

We received information about spam or abuse from paramount@copyright-compliance.com.
Please take all necessary measures to avoid this in the future.

Furthermore we request that you send a short response within 24 hours to us and to
the complainant. This response should contain information about how this could
happen and what you intend to do about it.

How to proceed:
-       Solve the problem
-       Send a response to us: Use the following link:
http://abuse.hetzner.de/statements/?token=gdfsdfggdghhdddghhdg
-       Send a response by email to the complainant

A technician will check the data and coordinate further proceeding. If we received
multiple complaints, the situation can lead to a server blocking.

Important note:
When you reply to us, please leave the abuse ID [AbuseID:djkdfkdgfsf] unchanged in the
subject line.


Best regards,

Sandra Betz

Hetzner Online AG
Stuttgarter Str. 1
91710 Gunzenhausen
Tel: +49

• 9831 610061

Fax: +49

• 9831 610062

abuse@hetzner.de
www.hetzner.de

Register Court: Registergericht Ansbach, HRB 3204
Management Board: Dipl. Ing. (FH) Martin Hetzner
Chairwoman of the Supervisory Board: Diana Rothhan

----- attachment -----

Return-path: <paramount@copyright-compliance.com>
Envelope-to: abuse@hetzner.de
Delivery-date: Thu, 29 Aug 2013 17:52:21 +0200
Received: from [67.128.96.38] (helo=newpop2.baytsp.com)
        by lms.your-server.de with esmtp (Exim 4.74)
        (envelope-from <paramount@copyright-compliance.com>)
        id 1VF4WC-0005Im-FE
        for abuse@hetzner.de; Thu, 29 Aug 2013 17:52:21 +0200
Received: from portalmail2.baytsp.com ([10.243.1.48])
        by newpop2.baytsp.com (8.14.4/8.14.4) with ESMTP id r7TFq9cU019137
        for <abuse@hetzner.de>; Thu, 29 Aug 2013 15:52:10 GMT
Date: Thu, 29 Aug 2013 15:52:09 GMT
From: "paramount@copyright-compliance.com" <paramount@copyright-compliance.com>
To: abuse@hetzner.de
Message-ID: <12570450.32906.1377791529817.JavaMail.dc@portalmail2>
Subject: 22-102567054 Notice of Unauthorized Use of Paramount Pictures
 Corporation Property
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: Clear (ClamAV 0.97.6/17768/Thu Aug 29 16:10:58 2013)
X-Spam-Score: 1.5 (+)
Delivered-To: he1-abuse@hetzner.de

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Notice ID: 22-102567054
Notice Date: 29 Aug 2013 15:52:08 GMT

Hetzner Online AG

Dear Sir or Madam:

Irdeto USA, Inc. (hereinafter referred to as "Irdeto") swears under penalty of
perjury that Paramount Pictures Corporation ("Paramount") has authorized Irdeto to
act as its non-exclusive agent for copyright infringement notification.  Irdeto's
search of the protocol listed below has detected infringements of Paramount's
copyright interests on your IP addresses as detailed in the below report.

Irdeto has reasonable good faith belief that use of the material in the manner
complained of in the below report is not authorized by Paramount, its agents, or the
law.  The information provided herein is accurate to the best of our knowledge.
Therefore, this letter is an official notification to effect removal of the detected
infringement listed in the below report.  The Berne Convention for the Protection of
Literary and Artistic Works, the Universal Copyright Convention, as well as
bilateral treaties with other countries allow for protection of client's copyrighted
work even beyond U.S. borders.  The below documentation specifies the exact location
of the infringement.

We hereby request that you immediately remove or block access to the infringing
material, as specified in the copyright laws, and insure the user refrains from
using or sharing with others unauthorized Paramount's materials in the future.

Further, we believe that the entire Internet community benefits when these matters
are resolved cooperatively.  We urge you to take immediate action to stop this
infringing activity and inform us of the results of your actions.  We appreciate
your efforts toward this common goal.

Please send us a prompt response indicating the actions you have taken to resolve
this matter, making sure to reference the Notice ID number above in your response.

If you do not wish to reply by email, please use our Web Interface by clicking on
the following link:
http://webreply.copyright-compliance.com/WebReply?webreplyhash=a1fd4ac345b02bfd8ccde04dafbefbb2

Nothing in this letter shall serve as a waiver of any rights or remedies of
Paramount with respect to the alleged infringement, all of which are expressly
reserved.  Should you need to contact me, I may be reached at the below address.

Regards,

Andrew Beck
Irdeto USA, Inc.
3255-3 Scott Blvd. Suite 101 Santa Clara, CA 95054
Phone: 408-492-8500  fax: 408-727-6743
paramount@copyright-compliance.com

*pgp public key is available on the key server at http://pgp.mit.edu

Note: The information transmitted in this Notice is intended only for the person or
entity to which it is addressed and may contain confidential and/or privileged
material.  Any review, reproduction, retransmission, dissemination or other use of,
or taking of any action in reliance upon, this information by persons or entities
other than the intended recipient is prohibited.  If you received this in error,
please contact the sender and delete the material from all computers.

This infringement notice contains an XML tag that can be used to automate the
processing of this data.  If you would like more information on how to use this tag
please contact Irdeto.

Evidentiary Information:

Notice ID: 22-102567054
Initial Infringement Timestamp: 29 Aug 2013 15:39:19 GMT
Recent Infringement Timestamp: 29 Aug 2013 15:39:19 GMT
Infringers IP Address: 46.4.92.107
Protocol: BitTorrent
Infringed Work: Jack Reacher
Infringing File Name: Jack.Reacher.2012.FRENCH.BDRip.XviD-AYMO.avi
Infringing File Size: 1464350720
Bay ID: 5166dd04b34ac587893959274914e9a782d8c375|1464350720
Port ID: 40670
Infringer's User Name:

- - ---Start ACNS XML
<?xml version="1.0" encoding="UTF-8"?>
<Infringement xmlns="http://www.acns.net/ACNS"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.acns.net/ACNS
http://www.acns.net/v1.2/ACNS2v1_2.xsd">
    <Case>
        <ID>22-102567054</ID>
        <Status>Open</Status>
    </Case>
    <Complainant>
        <Entity>Irdeto USA, Inc</Entity>
        <Contact>Andrew Beck</Contact>
        <Address>3255-3 Scott Blvd. Suite 101, Santa Clara, California 95054 United
States of America</Address>
        <Phone>408-492-8500,408-727-6743</Phone>
        <Email>paramount@copyright-compliance.com</Email>
    </Complainant>
    <Service_Provider>
        <Entity>Hetzner Online AG</Entity>
        <Email>abuse@hetzner.de</Email>
    </Service_Provider>
    <Source>
        <TimeStamp>2013-08-29T15:39:19.000Z</TimeStamp>
        <IP_Address>46.4.92.107</IP_Address>
        <Port>40670</Port>
        <Type>BitTorrent</Type>
        <UserName></UserName>
        <Number_Files>1</Number_Files>
        <Deja_Vu>No</Deja_Vu>
    </Source>
    <Content>
        <Item>
            <TimeStamp>2013-08-29T15:39:19.000Z</TimeStamp>
            <Title>Jack Reacher</Title>
            <FileName>Jack.Reacher.2012.FRENCH.BDRip.XviD-AYMO.avi</FileName>
            <FileSize>1464350720</FileSize>
            <URL></URL>
        </Item>
    </Content>
</Infringement>
- - ---End ACNS XML
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)

iQEcBAEBAgAGBQJSH24pAAoJEPbLkHDojX/o54sH/3xKVr2nWY17u26+ulU16T6i
gsrEizaKOnWqC+FSALnQUuDE+eUUyCtRJb/Ce21kPmn5xiaHv96EzwzbvRPCsnBg
ecKo/MKEUJfzTgwwgoMCKHRePhNwJikToH1Daj5xOJEWw3KXHCUN4IkfBMlfttkW
yH5hH0+AE5weD86TjApW35bzxgcjXoC3YNKzNXw6lgFaHv+SrK4A24Jh4UEJxo8+
qa4Ca7eN7gXvu10fy6TH6rW9eunsYkdA5Za6pEUUkPhKACPJHY6ORvIPGRhuSma7
RNwv+uJ9srgV/W54SniuUyU3jfgyW2OHH6Nej5ONC9oJg1GMo+mG3Jm5kCw7Sss=
=sF8x
-----END PGP SIGNATURE-----

Just an idea - what if we moved the mixing service to miners as a part of the job they do?

- users would broadcast special half-baked transaction (just inputs)
- miners would somehow form the queue of unsigned inputs into mixing "batches" and provide a way how to query current batches
- users would broadcast their signatures of the batch
- when the batch is signed by all parties, its moved by miner into the current block, if after some timeout it is not signed (few blocks?), its dumped

This would reuse existing Bitcoin p2p network and add new message type(s). The transaction will remain the same, no need for fork. It will allow easy integration into existing clients.

Not copied, my own ramblings. Which thread?

That has two weaknesses:

1. All transactions must be the same amount.

2. The participants have to be trusted to produce uniformly distributed keys. I think this means it isn't secure?

So if my understanding is correct, a ring signature is comprised of the N public keys and N + 1 large random values (N + 3 for ECDSA), for each signer so (N + 1)^2 plus the N public keys total if each participant is only sending to one output. In practice, they will send to more than one output to hide correlation of input and output amounts.

Yet if my thinking is correct, these large signatures don't need to be stored in the blockchain permanently. This signature only needs to be shown as evidence to all near-term PoW peers for what goes permanently into the blockchain, which are spends for each input to a special public key (which can't spend any other way) which has "spends" corresponding to each output in the signature. So it appears this would require a soft-fork of Bitcoin, because the participants can't send to a normal public key.

Can anyone comment on whether my understanding is correct or not?

If there exists a secure proof (the group signature, plus the spend transactions signed by all participants) that total of inputs match the total of outputs and all peers have agreed on this by accepting the block, then we don't need to keep that proof around in the blockchain. We can just keep the spend transactions to a key and spends from that key to the outputs. This would be a special key that the miner can not spend any other way than to providing the matching secure proof. If you disagree, please kindly explain why and not just assert I am wrong without any explanation. I assume you are correct, but I need to see why? Thank you in advance for helping me to understand.


Yes, but I am explaining how I am thinking we can use the miner to help out in a special way as I have described upthread.


How so? The participants sign to a special key that can't be spent any other way (blockchain will forbid it).


Upthread, I described a divide-n-conquer strategy for identifying the adversarial DoS participant.

I just pulled up the first thing on Google, not sure if it is applicable, Anonymous signcryption in ring signature scheme
over elliptic curve cryptosystem

Thanks for the reply.

I pushed the beginnings of a framework for a CoinJoin implementation using RSA blinded signature operations. It's written in Python and under the MIT license:

https://github.com/maaku/coinjoin

So far it's a storage layer for the various objects and message involved in the protocol, some simple primitives for the blinding operations, and a few utilities for pulling outputs from JSON-RPC. I'm working on more primitives that I will probably add next week, including tools for creating messages at various stages, and eventually getting this running over BitMessage.

Patches welcome.

I sold bitcoins today to a forex trader, and we had a long discussion about Bitcoin and the effects it could have on global finance.

At one point in the conversation I brought up CoinJoin and what it makes possible and his immediate reaction was, "That will have to be stopped."

I replied, "What is the US government going to do; tell Chinese, European, and Russian bitcoin miners what transactions they are and are not allowed to include in blocks?"

When I said that his eyes widened and his facial expressions had "Oh, shit" written all over it.

I rather enjoyed that part of the conversation.

And even there may be a solution to this 51% attack that enables the miners spending the coins. We keep a merkel hash of these signatures forever, so the spenders (or bitarchive.org ... does it exist?) can keep copies of the signatures and later prove if the miners have cheated. This would serve for rebuilding the blockchain manually, because with a 51% attack, the Bitcoin world is fubar anyway.