I have been thinking about this for a little while, but I am not an expert in radio and am relatively new to the field so I could use some help from people who know what they are doing.

As we know, not everyone in the world has access to the internet, has a decently fast connection, or has a connection that isn't blocked. To get around these problems, I propose that we should, as a community, create a radio network that allows the relaying of blocks and transactions without relying on internet connections which we have no control over. It would facilitate the use of full nodes and the accessibility to the Bitcoin network especially to third world countries where the internet is not available. Such a network would also help in places where there is a lot of internet censorship like in China. It would be able to bypass internet filters since those inside the country would still be able to pick up signals originating in neighboring countries.

Ideally this radio network would be on a frequency that can carry a lot of data, has a wide range, has little interference, and is legal to use worldwide. It should also be able to be broadcast to and from space so that we can have satellites that operate as full nodes and can further connect nodes to each other.

Part of the problem is finding a frequency that can be used for this. We could use CB frequencies but those are not able to carry a lot of data. Higher frequencies would require having an amateur radio license and may also be crowded and thus we would have interference. The best case would be to buy spectrum specifically for Bitcoin radio use only.

To transfer data, we could use already existing technologies. We could use the existing Packet Radio stuff and use the de-facto packet radio standard, AX.25. With this we could wrap blocks and transactions in a special message and send the packets with packet radio in order to propagate those blocks and transactions.

I will be working on this project to develop a Bitcoin radio network on and off. Currently I do not have the equipment for implementing or testing any of this, the proper licences, or the experience and knowledge. If anyone is more knowledgeable in radio, specifically packet radio, then the help would be appreciated.

Let me know what you guys think of this idea.

Update: It was not Satoshi.

This is spoofed.

Code:

    Received: from mail.vistomail.com (cpe-104-231-205-87.wi.res.rr.com
    	[104.231.205.87])         
    	by smtp1.linuxfoundation.org (Postfix) with SMTP id 01BCADF
    	for <bitcoin-dev@lists.linuxfoundation.org>;
    	Thu, 10 Dec 2015 06:53:42 +0000 (UTC)

104.231.205.87 is not mail.vistomail.com. It's some residential IP, cpe-104-231-205-87.wi.res.rr.com.

I feel like the mailing list must be seriously misconfigured to allow this sort of spoofing... You could exploit this to send mail "from" any of the devs, for example.

See for more details: https://www.reddit.com/r/Bitcoin/comments/3w6vy4/i_am_not_craig_wright_we_are_all_satoshi_satoshi/cxu7blm

I just saw this in the bitcoin Dev mailing list

I am not Craig Wright. We are all Satoshi.

http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-December/011936.html

I have no idea if this is legitimate, but it was sent (supposedly) by satoshi@vistomail.com, which is the first email address that he used to post about bitcoin.

Is there any way to see if I have already reported a post yet? Can I see what posts I have already reported? It would be nice to know so that I don't accidentally report a post twice.

Anyone watching this lunar eclipse and want to share some pics of it? It is really cloudy where I am so I can barely see it, if at all.

4 remaining.

I have 5 keybase.io invites I can give away. I will only give these to high ranking members that give a good reason as to why they need keybase (e.g your are an escrow and need to use keybase to protect against impersonators.)

You can post in this thread or pm me.

[How CoinJoin Works]

I am providing a new service to anonymize your Bitcoin. Unlike most mixers and anonymizers, my service requires no trust in me and your Bitcoin will always stay in your hands. The CoinJoin process prevents a third party from stealing your Bitcoin while anonymizing your Bitcoin.

THIS SERVICE DOES NOT ANONYMIZE IMMEDIATELY. PLEASE DO NOT USE IF YOU NEED YOUR BITCOIN ANONYMIZED IMMEDIATELY

How CoinJoin Works
CoinJoin utilizes Bitcoin's ability to spend multiple inputs to multiple outputs. It is a transaction that includes inputs from many different addresses, and spends them to different addresses. The key part of this is that the outputs are all of the same amount. This way, people following your transactions will no longer know which of the addresses is yours. This works even better when there are many people participating in the CoinJoin. For further reading, check out https://bitcointalk.org/index.php?topic=279249.msg2983902#msg2983902

How This Service Works
Those who would like to use my service can reply to this thread using the format described below. Included in your post should be the output address(es), input transaction ids, and amount. THE AMOUNTS ACCEPTED ARE 0.1, 0.5, and 1 BTC. You can also provide the change address and the amount to go there. At the end of each round, which begins and ends at 5 PM Eastern Time, I will review all of the posts for that round, sort them into 0.1, 0.5, and 1 BTC output categories, and create transactions for each. Each transaction will include all of the inputs and outputs for the round. Once the transaction is created, it will be sent to each member of the round and each person MUST SIGN THE TRANSACTION. Once everyone has signed it, I will broadcast the transaction and your Bitcoin will be anonymized.

Rules for participation
1. Post your request in the format described below
2. All outputs besides change outputs which are not necessary must be 0.1, 0.5, or 1 BTC outputs
3. All users MUST BE ONLINE FROM 5 - 7 PM Eastern Time in order to be included in the transaction. Anyone not online will not be included in the transaction.     
4. Those who do not provide their inputs will pay a fee of 0.025 BTC to me. I will include this fee in the transaction.
5. Any change that is not specified to a particular address will be sent to the address it came from.
6. At least 3 people must participate in each round otherwise the round will be extended to the next day.

Request Format
For your privacy, I recommend that you encrypt your request and post the encrypted data here. My PGP key can be found here: https://keybase.io/achow101/key.asc A simple tool for encrypting the data can be found here: https://keybase.io/encrypt. Simply enter "achow101" in the recipient box, enter your request data, and click encrypt. Then copy and paste the data contained within the secret message box to a post in this thread.
The Format:

Code:

Username:
Input TXIDs:
    <txid here>
    <txid here>
    ...
Output addresses:
    <output address here>
    <output address here>
    ...
Output amount: <amount here>
Change Address: <address here>

Tips are greatly appreciated and can be sent to 1At6EhbjN8BLCJz4pVAjsFcNzhzxQmXrwZ

Round 1 extended to 7/3/15

Does anyone have a keybase.io invite that they would be willing to give to me? I intend on offering a service here that will make heavy use of PGP and keybase is a very simple way for my users to encrypt and verify messages both to and from me.

...

I've created a modification of Bitcoin core that is like getaddr.bitnodes.io, but is a full node. It records the ip address from an addr message and then connects to each node in the list. However, I have had some problems and need some help diagnosing the issues. The source is here: https://github.com/achow101/fully-connected-bitcoin.

I have three problems currently:
1) Every so often, about 20-ish hours, the node will abort and give some error about "Unable to Open the Database" (I will update this post with the exact error next time it happens).

2) When I run getnetworkinfo from bitcoin-cli, I get this:
 

Code:

{
    "version" : 109900,
    "subversion" : "/Satoshi:0.10.99/",
    "protocolversion" : 70002,
    "localservices" : "0000000000000001",
    "timeoffset" : -1,
    "connections" : 646,
    "networks" : [
        {
            "name" : "ipv4",
            "limited" : false,
            "reachable" : false,
            "proxy" : "",
            "proxy_randomize_credentials" : false
        },
        {
            "name" : "ipv6",
            "limited" : false,
            "reachable" : false,
            "proxy" : "",
            "proxy_randomize_credentials" : false
        },
        {
            "name" : "onion",
            "limited" : false,
            "reachable" : false,
            "proxy" : "",
            "proxy_randomize_credentials" : false
        }
    ],
    "relayfee" : 0.00001000,
    "localaddresses" : [
    ]
}

It should have reachable in ipv4 as true and localaddresses should have atleast one ip address.

3) I have this on Travis-CI with Bitcoin core's default travis.yml file. It always errors everytime Travis builds it, and I don't know why. The travis page is here: https://travis-ci.org/achow101/fully-connected-bitcoin

Help would be greatly appreciated for any of these three issues.

Also, the software is being run on two Ubuntu 15.04 VMs, one at home with 3 cores and 4 GB of RAM, the other on Google cloud with 2 cores and 7.5 GB RAM. I am building and running bitcoind from terminal.

Coinbase recently announced their second Bitcoin Hackathon competetion. There are up to $70,000 of prizes for applications that use bitcoin and/or blockchain technology. The competetion ends on May 19th, 2015 at 11:59 PST. You can check out the full details here: https://developers.coinbase.com/bithack

Note: I am not affiliated with Coinbase. I thought that I should just let everyone know about this new competetion.

Every few days, bitcoind.exe will stop working when I start armory and to fix it, I have to manually start bitcoin core and rebuild the databases. Rebuilding always takes a long time, during which I cannot use my wallet. Is there some way to fix this so that bitcoind does not keep crashing?

I am running armory 0.93.1 and bitcoin core 0.10.0 64-bit on Windows 7 64-bit