|
If it is still syncing, then you won't see the transaction until it has synced past the time that the transaction was sent. If you lookup the transaction in Blockchain.info, then the coins were sent and you just need to wait for everything to become synced.
|
|
|
|
however I still don't understand why people don't like to buy accounts with ID on them . (it's not their so not sure why do they care really) .
It is illegal to be using someone else's ID. I guess they don't want to get in any legal trouble if they use the account for legitimate purposes. |
|
|
|
|
People buy localbitcoins accounts because ones with trade and reputation already makes it easier to buy and sell Bitcoin. It is similar to account trading on this forum, it seems like you are more reputable than you actually are. With those accounts, it is easier to buy and sell using more risky methods such as Paypal without having to do several hundreds of dollars in trades beforehand. A lot of times though, localbitcoins accounts are probably for scamming people.
Virwox makes it easier to buy and sell Bitcoin with paypal and credit cards, but with massive fees. With buying those accounts, the limits are higher than new accounts and the first buy doesn't need to wait 48 hours before the withdrawal will go through.
|
|
|
|
Bitcoin is at a breaking point, yet the core developers are too wound up in petty arguments to create the required modifications for long term sustainability. If nothing is done, Bitcoin will never be anything more than a costly science project. By stress testing the system, we hope to make a clear case for the increased block size by demonstrating the simplicity of a large scale spam attack on the network.
They aren't in petty arguments. There is consensus among the developers that something needs to be done to increase scalability. They all agree that the block size should be raised, but they disagree how much and how it should be done.
The plan - We have setup 10 Bitcoin servers that will send approximately 2 transactions per second each - Each of these transactions will be approximately 3kb in size and will each spend to 10-20 addresses - The outputs will then be combined to create large 15-30kb transactions automatically pointing back to the original Bitcoin servers.
When will the large transactions be sent? How often? The target will be to generate 1mb worth of transaction data every 5 minutes. At a cost of 0.0001 per kb (as per standard fees) this stress test will cost approximately 0.1 BTC every five minutes. Another way to look at the cost is 0.1 BTC per full block that we generate. We have allocated 20 BTC for this test, and therefore will be able to single handedly fill 100 blocks, or 32 hours worth of blocks. However, we will stop pushing transactions after 24 hours at 13:00 GMT Tuesday June 23.
100 blocks is not 32 hours worth of blocks, it is only 16.67 hours. 144 blocks are generated daily, so this number is incorrect. This is an interesting experiment, but it can and probably will disrupt a lot of trade going on through bitcoin right now. Also, since your transactions are pretty much dust and microtransactions, I think that miners will drop a lot of them and ignore your spam. Can you show us the results from your other tests? |
|
|
|
Corrections below:- snip - Now IFF right after you swipe your wallet, and walk out before you have any confirmations at all, someone picks up the wallet and trys to spend it, the following happens. OTHER: 1) someone imports the private key from the paper wallet they saw you discard. 2) someone creates a transaction to spend the outputs associated with that key. 3) someone signs thier transaction and sends it to whatever node / nodes they are connected to. 4) If the nodes they are connected to have already seen YOUR transaction, then they simply ignore this new transaction.5) if any nodes they are connected to have not yet seen YOUR transaction, then they send this new transaction to every node they are connected to6) if those nodes have already seen YOUR transaction, then they simply ignore this new transaction.7) if there are enough nodes in the system that have not seen YOUR transaction, then eventually a miner sees their tx and scoops it up into whatever block it is mining. 8 ) various miners around the world may do this if your transaction did not relay across the network quickly enough till a miner who finds the magic nonce does so with a block containing one of the two transactions. 9) this miner then submits his nonce (with someones tx) and , if the block contained the the other transaction, you now have been robbed. Whoever gets to #9 first gets the money. As you can see, as long as your transaction includes a large enough fee to be properly relayed, and enough seconds have passed for most of the network to have seen your transaction, there is a risk before confirmation but it is very low. If you want to avoid that risk completely, simply wait for a confirmation or two.If you are really paranoid about it, and the address is somehow associated with your identity (such as being used publicly on a discussion forum), then just be all James Bond and burn the paper wallet after you spend  There. I fixed that for you. Also, if the other person gets sends the transaction with a larger fee, nodes and miners who have implemented replace-by-fee (RBF) will discard your transaction and relay and mine the other one with the larger transaction fee. |
|
|
|
|
How, exactly, would such a change roll out? There is actually no point in the code (that I could find) that specifically imposes such a cap. The only thing that this cap comes from is the method which the block reward comes from, simply dividing by two. There is a point where the rounding used in the code simply returned zero, and that was when the block reward went to zero. This just so happens to be just under 21 million Bitcoin, which is likely just a coincidence, not a specifically hard coded thing.
|
|
|
|
I did
./configure
and it failed giving DB errors....
Google to the rescue hopefully?
Still moving forward and learning
THANK YOU
Can you post what the errors are? |
|
|
|
the .configure with all the extras worked however make command left me with loads of errors
going to do some google searching.... right now unsure where to start.....
Just do normal configure without options. |
|
|
|
I found it will post what I did in a few.... THANK YOU ALL
Next guess make a wallet and a pool account...
You already have a wallet, that was what you just compiled. To run it, just go into the folder you built it in and enter into the terminal. |
|
|
|
Now I have thos error -
checking into it....
libdb_cxx headers missing, Bitcoin Core requires this library for wallet functionality
Follow the instructions for Berkley DB in the link I gave you. It is near the bottom. |
|
|
|
You shouldn't build from the master branch, it can be unstable and might break. You should build and use the 0.10 branch. That will build you the latest stable version 0.10.2. You also need to install libtool. Just follow the instructions here: https://github.com/bitcoin/bitcoin/blob/0.10/doc/build-unix.md They should work for a raspberry pi, just ignore the stuff about Debian or Ubuntu. |
|
|
|
|
What is the address that sent the funds?
|
|
|
|
|
Bitcoin Core no longer supports IRC bootstrapping. The functionality was removed in version 0.8.2 and it was disabled by default in version 0.6. However this concern is still valid for altcoins that forked Bitcoin prior to this change. Obviously something was not good about IRC bootstrapping in Bitcoin Core, be it possibility of attacks or something else, so it was removed. I would assume that the IRC server the client connected to by default was trusted because it was run by the developer(s) of the coin, although they could be malicious also.
You also mention that IP addresses will be public. By virtue of running a full node, and by being on the internet in general, your IP address will be publicly known.
Good luck on your research, looks like good stuff. Also, can you put code that you find in code brackets? It will make these easier to follow and the post won't be as long.
|
|
|
|
Great.....!but I still cant boot the program....I get the error message (See screen shot in last message)....how do I get the software to open....
Can you post a screenshot of the report when you click report? I think the solution would be to just reinstall Bitcoin Core. Reinstalling will not delete the blockchain you already downloaded previously, nor will it delete your wallet. Just to be safe though, before reinstalling, copy the wallet.dat file to a safe location. |
|
|
|
|
1) It is sound, and a lot of people here do that. You should also have them include the date and time in the message.
2) I don't think that there is a limit, but ask them to keep the message short just in case.
3) Most web wallets do not actually give their users full control of the keys. If they are using a web wallet, then they won't be able to sign a message. One of the exceptions is blockchain.info's wallet.
Also, what key do they need to forward to you? You only need the message, signature, and address used to sign it.
|
|
|
|
|
You cannot. CompactFlash is for storing data, not processing data. There is a tiny little microprocessor on the card that could possibly mine, but the amount of time and effort to reprogram that chip is not worth it and furthermore, that chip is probably specifically designed to do one thing, so you could not change it to mine at all.
|
|
|
|
It has been over 12 hours. It's gone and nothing on blockchain.
Does blockchain show that you still have the 1 BTC that was spent? If it does, that means the network "forgot" the transaction, e.g. you will still have the Bitcoin and can still spend it. |
|
|
|
That is not a hacking attempt, that is a node on the Bitcoin network trying to make a connection to your node. You should click "allow" so that you have a connection to the Bitcoin network and can fully sync the blockchain. |
|
|
|
|
Find the address you made that transaction from and look it up in Blockchain.info. If you see the transaction there, then that means it was broadcast to the network and your multibit database is corrupted. However, if you don't see it, that means that your transaction was "forgotten" by the network. A transaction will be "forgotten" after several hours of being unconfirmed if it is not continuously broadcast. The only node that will continuously broadcast an unconfirmed transaction is the one that sent it, and if you turned off your computer or closed Multibit for the night, then it will stop broadcasting that transaction and the network will have "forgotten" it.
|
|
|
|
Each tutorial says you need to create a wallet and pool account but they do not show you how to do either. At least the ones I have found so far.
A wallet is to store your Bitcoin. Choose a wallet from this site here: https://bitcoin.org/en/choose-your-wallet I personally recommend you use Bitcoin Core if you want a full node, or Multibit or electrum if you don't want to run a node. Mining Pools allow you to mine Bitcoin more cost effectively. They guarantee a payout, but with a USB miner, you probably won't get too much. Here is a comparison of mining pools from the Bitcoin wiki: https://en.bitcoin.it/wiki/Comparison_of_mining_pools You can also look in the Mining > Mining Pools subforum for more stuff about pools. To make an account, just go to the website of whatever pool you like and register an account. They all have instructions on how to setup accounts and mine. |
|
|
|
|
Show Posts
