What happens when someone decides to spam the network with large fees? What if someone figures out a fee that is large enough to be considered high priority and has enough money just to keep spamming the network? Does that mean that in order to get my transaction confirmed I have to pay an even higher fee? That could be an attack on the network where someone could either drive up fees, prevent anyone else's transactions through their high fee spam, or make it too cost prohibitive to use Bitcoin at all.
If it costs you 10k every 10min to spam the network.. have fun bro lets see how long you can burn money. If you are a government, you have tons of money at your disposal. They can just keep burning money. Even better, if a miner is doing it, he can just keep recycling the same Bitcoin and do it over again. Your populs is going to get pretty pissed you're burning money for no reason. Not true unless they have 51% of the mining network and at that point there are other issues. Other miners will take those BTC from them via fees. Not going to get into an argument about this. I'm just saying that it is not infeasible for someone with a ton of money to attempt to do this to the network. |
|
|
|
|
It is not normal to have to wait that long, however someone was recently spamming the network so the number of unconfirmed transactions is quite large and there is a large backlog on transactions. Just wait some longer and your transactions will eventually be confirmed.
|
|
|
|
What happens when someone decides to spam the network with large fees? What if someone figures out a fee that is large enough to be considered high priority and has enough money just to keep spamming the network? Does that mean that in order to get my transaction confirmed I have to pay an even higher fee? That could be an attack on the network where someone could either drive up fees, prevent anyone else's transactions through their high fee spam, or make it too cost prohibitive to use Bitcoin at all.
If it costs you 10k every 10min to spam the network.. have fun bro lets see how long you can burn money. If you are a government, you have tons of money at your disposal. They can just keep burning money. Even better, if a miner is doing it, he can just keep recycling the same Bitcoin and do it over again. |
|
|
|
knightdk, you simply did not understand what I was suggesting about TX PoW. All your replies were ill formed and overly pessimistic without understanding my idea. If you are a troll, then I would like to have you vaporized.
Ok. Perhaps I did not understand. Perhaps you can inform me. I will re-read your posts and see if my understanding changes. TX "mining" can be done without impact on devices that have less computing power.
How so? Distinguishing between nodes can be done without linking them to the IP. For example, you can do it based on the signing public key.
Even when done with public keys, if the spammer has setup a ton of nodes and each one has the exact same wallet but different signing keys and ip addresses, each node could send a couple of transactions per second yet when all of the nodes are combined, it is still spamming the network. This solution still wouldn't work. Nodes could filter based on addresses, but even that could still be circumvented. |
|
|
|
wasn't there a dust threshold that prevented tx spam like this? or did they patch it out?
It is still there. If you look in the debug.log, you will see a lot of lines that look like this ERROR: AcceptToMemoryPool : nonstandard transaction: dust This means that dust transactions are being dropped by standard clients. However, some places do not do this, such as tradeblock. They will say that the mempool is much larger than what nodes and miners see because they _do_not_ drop dust transactions. |
|
|
|
|
It can also take a long time depending on your internet speed and bandwidth. Since it must download almost 40 Gb of data, having a slow network speed can make this download much much longer.
|
|
|
|
I think bitcoin-core should start discarding unconfirmed TXs if they start to consume too much memory. TXs with the lowest priority should be discarded first. Also, individual TXs should contain a proof of work in addition to the fee. The proof of work should be optional and should increase the priority of the TX so that it would not be discarded so easily.
Most of the dust transactions that are spamming the network are being dropped by most node's mempools. It is primarily these dust transactions that cause the mepool to grow so large. For example, let's say the network is under attack. The nodes would not be able to distinguish between malicious TXs and honest TXs. However, a honest node would attach a proof of work to the TX so that honest TXs would be favoured by the network since their proof of work has more zeroes in front of the hash than the malicious TXs. When the attacker chooses to attach their own PoW the priority of the malicious TXs rises naturally to the point that it could push out the honest TXs. However, because the client can freely choose the difficulty of the PoW, it will notice that their TX is not accepted by other nodes so the client increases the difficulty, calculates a new PoW and resends the honest TX. That way, the bitcoin network would become super resilient to the given attacks.
So you are suggesting that we must mine txs in order to have it be accepted and confirmed? What if the malicious spammer has an ASIC that can calculate these PoWs faster than everyone else and makes them more difficult? That means that he just raised the difficulty of his transactions, thereby increasing his priority. This causes other people to have a lower difficulty than the majority and thus their priority is lower. So what happens to those people that don't have sufficient computing power to calculate a PoW more difficult than the spammers? Does this make their transaction have a lower priority and they are essentially locked out of making transactions? We could start identifying TXs by the nodes where the TX initiated. That way, a honest node would only have to calculate the PoW once during its existence. The calculation should be difficult. When other nodes detect TX flood from a single node they would revoke the PoW and not relay those TXs any more until a new PoW is attached.
If a PoW calculation is difficult, what happens if my computer does not have the computing power to calculate a sufficiently difficult PoW? Is it rejected and blocked from the network? Does that mean I will have to wait even longer for Bitcoin Core to start the first time so that it can generate a PoW that identifies the node as me? How are developers responding to this severe limitation of Bitcoin's usage. There are currently 72000 (!) unconfirmed transactions but it seems they don't really want to acknowledge it.
Perhaps set a limit of tx/s to discourage spamming the mempool and block malicious nodes.
While there may be 72000 unconfirmed transactions, the standard mempool and standard Bitcoin Core software drops certain transactions. The site, tradeblock, where you are getting this number from, records the transactions differently. They record all transactions broadcasted, which will include all of the dust and spam transactions that other nodes and miners will drop from their mempools. The 72000 number is not an accurate representation of what the actual number of transactions in the mempool is. Edit: Take 2, because apparently the first one was wrong. |
|
|
|
|
What happens when someone decides to spam the network with large fees? What if someone figures out a fee that is large enough to be considered high priority and has enough money just to keep spamming the network? Does that mean that in order to get my transaction confirmed I have to pay an even higher fee? That could be an attack on the network where someone could either drive up fees, prevent anyone else's transactions through their high fee spam, or make it too cost prohibitive to use Bitcoin at all.
|
|
|
|
|
Since you already made the transaction to them before the 12 hrs was up, you should be able to still get your Bitcoin back. Once there are 3 confirmations, you will receive your Bitcoin as you specified.
|
|
|
|
That is correct. Q2) What is the next step? I am guessing I have to load Animazing's public key into Kleopatra somehow, is that correct?
Thanks guys
Download Animazing's PGP key Open up Kleopatra and go to File > Decrypt/Verify Files ... Select the the electrum-2.3.2-setup.exe.asc. Check the box for detached signature. Click the button next to the first text box and select the setup exe file. Click Decrypt/Verify and it will verify the signature. |
|
|
|
You can download the signed hash file and their signing key from the downloads page here: https://bitcoinarmory.com/download/. Using GPG, you can verify the signed file and take to checksums of the other downloads and see if they match the hashes that they signed. |
|
|
|
They are somewhere on bitcoin.org. Here is some of them down to 0.8.6 https://bitcoin.org/bin/ I don't know where the rest are. |
|
|
|
I would recommend that you use Qt. It is very widely used and Bitcoin itself uses Qt for the gui. You can find out more about Qt at www.qt.io |
|
|
|
|
The unconfirmed transactions will disappear after a few days. The network will "forget" them and you can essentially double spend the transactions. If you look up the transactions in a block explorer, you can see whether your transactions are confirmed or not.
|
|
|
|
|
Pretty much all of those transactions are spam and dust transactions created and sent by whoever decided to spam the blockchain yesterday.
|
|
|
|
signrawtransaction '0100000001cdba95b552d24a50182208816179578544d6d623fb0ca1dfbec4e6c845e6a9300100000000ffffffff01f09aeb0b000000001976a9145bd898bbe4a000cda4418c1fd28178ec99cd653e88ac00000000'
'[{"txid":"30a9e645c8e6c4bedfa10cfb23d6d6448557796181082218504ad252b595bacd","vout":1,"scriptPubKey":"76a9145bd898bbe4a000cda4418c1fd28178ec99cd653e88ac",
"redeemScript":"5241045e8385118c8b77a044390364dd5fb8c4864d138491fc788948be81f6842f45bc6b6c9401a90f8479b2af8191b7a6a7735053f2724668cf8af8a2c30d853b801141042cb46c5cfa2a5af18effd8296e7aeda287d407ccc2e42cc15bb7d27c6f84e4a78ade99d1aa7e8efa2fd63f8573548ec1a33f53e0135ccbe15bc5c9eb0d6e0cfd4104d109b4e95fd48162e5424fe71d769c9cb4bc8cb40224ab6b8d1e9fac6f6925c34c902d38caebebf2703a7685bf788adfee83bffa637f95d3c782c3d4bb0120f553ae"}]'
'["5K9T8VGcAztUQs5rSRGnf6oEwymY4k8YJV7MBfU5T3LD4H3wK2E"]' what is wrong ? Also tried to use this example 2 of 3 https://gist.github.com/gavinandresen/3966071The error message same 10:42:00  Invalid private key (code -5) What should I change ? BR! You are using the wrong private key. Since this is a testnet transaction, you must sign it using a private key in testnet format. The private key that you posted above is for the mainnet. Testnet private keys start with either '9' or 'c'. BTW, you should never post your private keys online. Also, I don't think you included the scriptpubkey or the redeemscript in the createrawtransaction. Be sure to do that. Follow Gavin's instructions in the link. |
|
|
|
|
You can enter a label if you like. This helps you keep track of your addresses. You shouldn't be able to type anything into the Address box, so just click "OK" and you will see the address with the label if you had one.
For sending transactions:
1. Go to the send tab
2. in the "Pay To" text box, enter the address of the recipient
3. In the "Amount" box, enter the amount that you wish to send. Bear in mind that you will have to pay a transaction fee, so don't send all of your Bitcoin because you won't be able to send.
4. Click "Send" It will open up another dialog box. Review your transaction and make sure you like it. There will be a transaction fee, usually very small. Click OK to send the transaction.
|
|
|
|
|
Is your code for this open source or available for people to download and run themselves? If so, where can I get a copy.
|
|
|
|
2. Either tradeblock.com or statoshi.info are behind this. They always show by far the largest values (tx/s and mempool size) and thus are always the sites that are referenced during these tests. It is a tremendous publicity for them.
I highly doubt that statoshi.info is behind this because the guy that runs the site probably doesn't have the money or infracstructure to carry out this prolonged spam attack. Possibly tradeblock, but still a stretch. Why would they want to anyways? Also, I think statoshi's data is more reliable than tradeblock's because it reflects the mempool of miners. Tradeblock's seems to be every unconfirmed transaction broadcasted which will include transactions that are dropped by nodes and miners. |
|
|
|
|
Show Posts
