I don't get many views since the site is super specific to one thing on bitcointalk so I don't make much. But if you make something that a lot of people will use like something just bitcoin specific, then you will probably make more.

I use a-ads.com.

Op codes are part of the scripting in Bitcoin transactions. The blockchain doesn't run those scripts, clients do. The blockchain is essentially just data storage. They way that those scripts work is by putting them in the input and output script of a transaction. All they do is run commands which manipulate the data in the script to result in a true or false. True meaning that the transaction is valid, and false not. Those scripts must be run by any Bitcoin client to verify transactions.

If you want to learn more about the technical and low level stuff with Bitcoin, I suggest that you read the documentation at https://bitcoin.org/en/developer-documentation specifically the reference and the guide.

Create a website that you think people will visit. Maybe make some sort of an automated service. Then just put ads on it and post a thread here announcing said service. People will check out your website and you can make ad money.

For example (also a shameless plug)
I created the website http://www.bctalkaccountpricer.info/ which is a service that checks the price of a bitcointalk account as well as a ton of other details that are useful to know about an account. I posted a thread here about it and people went to the site. Since I have ads on the site, I make some ad revenue.

I still have this problem. I can view the details while the transaction is unconfirmed, but as soon as it receives a confirmation, I can no longer view the details. I still get the error dialog

There are also some bugs with receiving RBF transactions:
I created an RBF transaction and then replaced it. It did not show that replacement as being replaced in Armory but rather it came up as a second transaction. Also it is incorrectly showing the data for the two transactions I created. I am testing this on testnet.

txid of the first one: 1286e1f39c09a01178d9017d2dbfa178ca99c59f0a2893e10db605815560a1d3
What armory shows me:


txid of the replacement: ff03b4ee97778f0e4ccec2b81f5f8a56fc81e1ab667965124676e13353a79763
What armory shows me:


As you can see, something is not right here. Also while the transactions were unconfirmed, spendable funds had some ridiculous number, but that went away before I could screenshot it. It went away when the replacement got a confirmation.

Right now with the replacement having a confirmation, it has it in the transaction ledger as two different entries, the confirmed one where it correctly shows it as receiving but not the right details, and an unconfirmed one where it says that it is sending, again with the wrong details. But the details are identical for both entries.

Also, with the confirmations, the details are shown, unlike with sending RBF transactions where after a confirmation the details are not shown.

It is really strange. If you give me a testnet address, I can show you what is happening by sending you a transaction and then replacing it.

Is the manual entropy supposed to show something in the buttons? All I see is this:

OP did pm me and I helped him over pm. The sweeping transaction worked and it did confirm quickly. His problem has been resolved.

Electrum is still very safe. IMO it is one of the safest wallets out there. It is safe to keep using electrum. Do not switch to using an online wallet; they are significantly less safe than electrum.

You aren't going to be able to find a free vps that is capable of running bitcoind since bitcoind is very cpu and memory intensive.

To install it, just follow the instructions for linux at https://bitcoin.org/en/full-node#linux-instructions. If you want to accept incoming connections, you will need to configure the firewall of your vps provider to allow connections to port 8333.

He isn't doing it on his own box with his own router, it is on a vps. Please stop spamming and actually read the thread, especially short ones like this.

FYI running a full node is as easy as download, install, and run Bitcoin Core and let it do its thing. Contrary to popular belief, you do not need to accept incoming connections to run a full node, you just need connections in general, be it incoming or outgoing. Anyways, Bitcoin Core uses UPNP which should set up port forwarding through your router automatically.

Sweeping creates a new transaction so you have to wait for that new one to confirm. I haven't swept Bitcoin into Electrum in a while so I don't exactly remember what happens after you click Sweep, but I think there should be something about setting a fee, if there isn't fee estimation in Electrum is decent and the default fee should be high enough.. You can check https://bitcoinfees.21.co/ for the optimal fee (it is in satoshis per byte) and set the fee accordingly. Fees are fairly low right now so it shouldn't be long for your transaction to confirm. Higher fees will make a transaction confirm faster.

In Electrum, a wizard that should appear on your first run of the software. If you don't see the wizard for creating a wallet, make sure that you haven't already created a wallet. If you haven't and you don't see the wizard, stop and post back here; something is very wrong.

In the wizard, select the options for "Create new wallet" and "standard wallet"; they should be selected by default. Click next and you will see your wallet seed. DO NOT SHARE THIS WITH ANYONE. Follow the instructions and keep a backup of your seed words in a safe place. Go through the wizard and make sure you set a password. Once you finish it will open up to the main Electrum window.

Once in the main window, go to the top and select Wallet > Private Keys > Sweep. In the next window that opens, enter the private keys that you got, one on each line if you have more than one. Click sweep and it should sweep all of the Bitcoins from your previous addresses into this new wallet and it should be ready to use and spend from once the transaction confirms.

If you want the Unspent Outputs you use listunspent. If you want to find out more data about a transaction, use getrawtransaction. You can use listtransactions to get the transactions for a specific account (and accounts can be made address specific) and then use getrawtransaction for each transaction to get the data of that transaction.

Basically look at all of the commands under the wallet section and use the help <cmd> where <cmd> is the command you want to know about to learn about what each command does.

And be more clear about what you want to do when you ask for help.

What wallet are you using now? What you will need to do is export the private key for your address(es) and sweep (or import the private key but sweeping is better) the Bitcoin into your new wallet. When you export your private key, make sure that you NEVER SHARE IT with anyone, the private key is what gives people the ability to spend Bitcoin associated with an address.

To export your private key, open up Bitcoin Core and go to Help > Debug Window. Then type the following into the textbox at the bottom:
where <address> is your Bitcoin address that you want the private key for. It should give you something that looks like 5HueCGU8rMjxEXxiPuD5BDku4MkFqeZyd4dZ1jvhTVqvbTLvyTJ. That is your private key, NEVER SHARE IT WITH ANYONE. The private key will always start with a 5, K, or L.

Once you have the private key, you will need to sweep the Bitcoin (or import the key) into your new wallet, and further instruction for that will be given once you get there.

There are no "representatives" for Bitcoin Core, just the developers, and they don't hang around these forums a lot except for gmaxwell (although maybe you could consider me a representative since I do marginally participate in Bitcoin Core development and I am one of the gitian builders). However Danny and I among many others including Shorena are several members of the community who have extensive experience with many different Bitcoin clients, including Bitcoin Core, and are willing to help others to solve their problems.

This isn't that hard to do, just enable an advanced user mode and choose which inputs you want to spend. This is easily done in Bitcoin Core and Armory.

There are a few problems here, though not major ones. You are operating under the assumption that change outputs are easily spotted, however that is not the case. If the change is sent to a new address, then that change cannot be easily tracked or identified as change. It can be rather difficult to identify the change outputs especially if both outputs are either outputs with weird uneven values (e.g. 0.3595412) or both are even values (e.g. 0.25). Furthermore, with newly generated change address and newly generated payment addresses, an observer cannot be certain which output is your change and which is someone you are paying.

Additionally, if you have enough inputs, you can create identical outputs which would make it near impossible for an observer to distinguish which output is for whom. That is also achievable by using even output values or uneven output values for all of the outputs.

Another solution which is perhaps better but slightly harder to do is a CoinJoin transaction; it requires coordinating between multiple parties. CoinJoins combine inputs from various people, so you could have a bunch of your own inputs there and no one would know that those were your inputs, for all they know it could be some other person who participated in that CoinJoin. Then the outputs are all the same amount so it is difficult to distinguish which output is for which person.

Kinda. So you would run Bitcoind like this bitcoind -datadir=.bitcoin -port=88888 -rpcport=99999 -rpcallowip=127.0.0.1 -rpcuser=bitcoinrpc -rpcpassword=password -blocknotify=<cmd>
where <cmd> is whatever command you want to run whenever you receive a block.

An Example:
bitcoind -datadir=.bitcoin -port=88888 -rpcport=99999 -rpcallowip=127.0.0.1 -rpcuser=bitcoinrpc -rpcpassword=password -blocknotify="bitcoin-cli getblock %s > block-%s.txt"
%s in the command is replaced by the block hash automatically by this flag so you would literally have %s in the command wherever you need to have the block hash.

I think that should work, although I am testing it right now and will get back to you when that runs. Edit: It works.

LevelDB being stupid is one of the major reasons that people have to reindex on Bitcoin Core crashes. There have been proposals to replace it but so far there are no plans on doing so. However people are working on using different databases in Bitcoin Core and those are being implemented and tested.

You can use the -blocknotify=<cmd> option to run a command every time a new block is received. The command can just be a bash script which can then get the block hash and look up the block through bitcoin-cli and get the JSON to parse it.

Check your port forwarding. With a wired connection instead of wireless it is likely that your ip address has changed so your router port forwarding will need to be changed.

A faucet is a service that gives away tiny amounts of bitcoin. For actually earning anything they are useless. Don't try to earn stuff off of collecting from faucets.

Not necessarily. Look at ckpool. They do full verification of blocks and produce very few empty blocks and have few orphans. With a dedicated server and decent setup and software, the time to verify a block to begin mining on it is negligible.

No. The size of a block does not matter in how quickly the block is solved. A block with no transactions and a full block both have the same probability of being the solution.

In reality the network only handles around 2-3 transactions per second. 7 tps is only a theoretical maximum with optimal conditions; it's a scenario that never happens.

Yes there are plans on increasing this, it's the whole block size/scalability debate that is happening and has been for a while. In Bitcoin Core, the current plan is to implement Segregated Witness which has an effect of essentially doubling the block size limit which will increase the number of transactions the network can handle. Then later there will be additional scaling plans which may also include increasing the block size limit.