What if the devs are ordered by a US judge to include a government backdoor?

[Revelation 22:13]

Let's say the IRS wants to be able to confiscate bitcoins from tax evaders. So they go to the US courts to get this. A judge ends up ordering the bitcoin.org dev team to include a government backdoor so the IRS can take funds away from those who don't pay taxes.

The devs would be forced to comply right?

[1715665361]

1715665361

[1715665361]

1715665361

[1715665361]

1715665361

[tutkarz]

Let's say the IRS wants to be able to confiscate bitcoins from tax evaders. So they go to the US courts to get this. A judge ends up ordering the bitcoin.org dev team to include a government backdoor so the IRS can take funds away from those who don't pay taxes.

The devs would be forced to comply right?

no because most of the world will simply not use such a client.

[Stephen Gornick]

Let's say the IRS wants to be able to confiscate bitcoins from tax evaders. So they go to the US courts to get this. A judge ends up ordering the bitcoin.org dev team to include a government backdoor so the IRS can take funds away from those who don't pay taxes.

The devs would be forced to comply right?

Open source software makes it so that every change is visible.  

Currently the Bitcoin-Qt/bitcoind release is signed by the Bitcoin Foundation ... which means the release won't work for Windows 8 and Mac users (as an update) unless Bitconi Foundation signs it.   This makes it difficult for some other dev team members who are not a party to this hypothetical IRS backdoor demand to be able to release updates to the client without this backdoor themselves.   It would probably have to be a fork with a different name (and signed by some other organization).

But the developers don't have final say as to what changes are accepted for the Bitcoin protocol.  It is the economic majority who decides:
 - http://en.bitcoin.it/wiki/Economic_majority

[Revelation 22:13]

Let's say the IRS wants to be able to confiscate bitcoins from tax evaders. So they go to the US courts to get this. A judge ends up ordering the bitcoin.org dev team to include a government backdoor so the IRS can take funds away from those who don't pay taxes.

The devs would be forced to comply right?

no because most of the world will simply not use such a client.

But bitcoin.org would be forced under court order to offer it?

[tutkarz]

Let's say the IRS wants to be able to confiscate bitcoins from tax evaders. So they go to the US courts to get this. A judge ends up ordering the bitcoin.org dev team to include a government backdoor so the IRS can take funds away from those who don't pay taxes.

The devs would be forced to comply right?

no because most of the world will simply not use such a client.

But bitcoin.org would be forced under court order to offer it?

then someone else will take the lead

[mezzomix]

Let's say the IRS wants to be able to confiscate bitcoins from tax evaders. So they go to the US courts to get this. A judge ends up ordering the bitcoin.org dev team to include a government backdoor so the IRS can take funds away from those who don't pay taxes.

The devs would be forced to comply right?

no because most of the world will simply not use such a client.

But bitcoin.org would be forced under court order to offer it?

then someone else will take the lead

In other cases the people were ordered to not talk about this change. People from unaffected countries have to review the patches, find the backdoor and publish this information.

Signed binaries is a bad idea in this case, because there is a central instance that control a BLOB and is not allowed to talk about the details. Almost no chance for the user of this signed binary to find the backdoor.

[apetersson]

you would not necessarily know that there is a backdoor.

standard procedure is a NSL that prevents you from even mentioning the existence of the order.

the us gov also reserves the right to control the content of all .com/.org/.net domains.

therefore it is essential that the source and corresponding binaries are matching up and as many people as possible are watching the source closely.

also if you see gavin blinking -. ... .-.. that should give you a hint.

[Loozik]

Let's say the IRS wants to be able to confiscate bitcoins from tax evaders. So they go to the US courts to get this. A judge ends up ordering the bitcoin.org dev team to include a government backdoor so the IRS can take funds away from those who don't pay taxes.

The devs would be forced to comply right?

Would the judge pay the devs for the backdoor programming from his own pocket?

[ShadowOfHarbringer]

you would not necessarily know that there is a backdoor.

For an experienced programmer who reviews Bitcoin code on a daily basis it should be trivial to spot such a backdoor.

Git is such an extremely powerful tool to review exactly who does what and when. It will be almost unfeasible to put a backdoor in Bitcoin, currently.

[jackjack]

you would not necessarily know that there is a backdoor.

For an experienced programmer who reviews Bitcoin code on a daily basis it should be trivial to spot such a backdoor.

Git is such an extremely powerful tool to review exactly who does what and when. It will be almost unfeasible to put a backdoor in Bitcoin, currently.

This

[jaywaka2713]

Also, if such a backdoor exists, you would need 51% of the network to upgrade to the bugged software for it to actually be implemented. The bug would be found before then.

[jl2012]

Let's say the IRS wants to be able to confiscate bitcoins from tax evaders. So they go to the US courts to get this. A judge ends up ordering the bitcoin.org dev team to include a government backdoor so the IRS can take funds away from those who don't pay taxes.

The devs would be forced to comply right?

The devs are not forced to comply because they can simply abandon the project. They have no obligation to contribute to the project.

If the government want to add a backdoor, they can always hire a programmer to work on that. They can also confiscate the bitcoin.org and put their version of bitcoin there.

However, people can still contribute to the original bitcoin project anonymously, e.g. through TOR network. In that case, a hardfork will happen: the original bitcoin and censored bitcoin

[drawingthesun]

you would not necessarily know that there is a backdoor.

For an experienced programmer who reviews Bitcoin code on a daily basis it should be trivial to spot such a backdoor.

Git is such an extremely powerful tool to review exactly who does what and when. It will be almost unfeasible to put a backdoor in Bitcoin, currently.

Its less about the source code itself but more about the Bitcoin binary that everyone is downloading. I understand a lot of people watch the code but how many people are comparing the compiled binary to what the code is on Github?

If they put a backdoor into Bitcoin it will be in the binary only and it will never be in the source code. (The binaries are built by people, and are not automatically generated from the Github source.)

Who is comparing the compiled binary to the binary that should exist if compiled from the source code. Does anyone even check this? Is there a chance the binary we all have sitting on our computers is slightly modified from the Github source code?

[e4xit]

Why dont you have a look 

[Sukrim]

Check out gitian and build your own binaries.

[drawingthesun]

Check out gitian and build your own binaries.

But how would I confirm that the official binary is compiled from the source on Github? Little point in running my own binary if 95% of all the nodes are from the official website and have a backdoor.

[jackjack]

Check out gitian and build your own binaries.

But how would I confirm that the official binary is compiled from the source on Github? Little point in running my own binary if 95% of all the nodes are from the official website and have a backdoor.

Build with same versions of g++ and qmake, same architecture, same dependency (if any, I don't know) and compare
Maybe I forget something to check

[scintill]

Check out gitian and build your own binaries.

But how would I confirm that the official binary is compiled from the source on Github? Little point in running my own binary if 95% of all the nodes are from the official website and have a backdoor.

How will you confirm?  With gitian, like he said.  I admit I don't know much about it either, but this is near the the top of the page of the first Google result for "gitian":

Gitian uses a deterministic build process to allow multiple builders to create identical binaries. This allows multiple parties to sign the resulting binaries, guaranteeing that the binaries and tool chain were not tampered with and that the same source was used.

The official binaries are built this way, so you can build your own and verify that you get the exact same binary.  That is how you will know the official binary is really built from the public sources.

[jackjack]

Bitcoin uses gitian? Great

[drawingthesun]

Check out gitian and build your own binaries.

But how would I confirm that the official binary is compiled from the source on Github? Little point in running my own binary if 95% of all the nodes are from the official website and have a backdoor.

How will you confirm?  With gitian, like he said.  I admit I don't know much about it either, but this is near the the top of the page of the first Google result for "gitian":

Gitian uses a deterministic build process to allow multiple builders to create identical binaries. This allows multiple parties to sign the resulting binaries, guaranteeing that the binaries and tool chain were not tampered with and that the same source was used.

The official binaries are built this way, so you can build your own and verify that you get the exact same binary.  That is how you will know the official binary is really built from the public sources.

Ah thanks, so the official binaries are built this way? Thats good to know. If we can verify the binaries then getting a back door in will be extremely hard if not impossible.

Life is good again!