Genau, das ist das tolle an HD wallets. Da reicht es den Seed einmal zu sichern. Bei MBHD ist sind das halt die 12/18/24 Wörter und der Date-Stamp. Allerdings sollte das auch niemand zu gesicht bekommen.

0.10.0 is estimating the fee, but as you said yourself you set up such that it uses a very low fee. Updating to 0.11 would not change that. If you are tech savvy or know someone trustworth that is you can remove the transaction from your local wallet with the tool pywallet (make sure you have a backup in case you mess it up). That way you can create a new TX with a higher fee after 6-24 hours. If you just keep your wallet software closed for x days it will rebroadcast the TX once you opened it again.

Thanks for letting us know, see you in two weeks.

Nope.

You need:

#1 the network to forget about your transaction. If Mycelium is rebroadcasting this means to not use it at all for at least 24 hours. The question came up recently in another thread, but I dont know how Myceliums reacts when a TX does not get confirmed. You should research a definit answer for this to improve your chances of a double spend.
#2 the wallet to forget the TX existed in the first place. I have no clue if thats even possible with Mycelium. If its not possible to modify it with external tools, you have to export the private key into a different wallet. Keep in mind that exporting a private key is always a risk to leak it.

While these two things are difficult, once you managed them you can just create a new TX and set a higher fee.

Traffic rose indeed. Even though the node has to stay up with only 2 GB of ram, it did not crash. Its certainly at its limit though as it dropped connections even durring the tests.

Not sure if that counts, but I would convert to CLAM and invest in just-dice. Why? Because its the only thing I have ever been invested in with bitcoin (or alts) and forgot about. Its not that I dont know I am invested there, but its not constantly nagging me to check whether my funds and the site is still around. This feeling of "I dont have to worry about it" is worth more than a slightly higher ROI that might be available elsewhere.

Its not wise to put all eggs into one basket though, so I would suggest you make different investments each with a part of what you want to invest.

I agree, my server is running out of diskspace and I will soon limit it to ~40 GB. That will last for a few more weeks/months/..., but eventually it will not longer store a full copy.

Known "bug": minrelaytxfee does not accept 0 (or 0.00000000). Its already on git[1] and its somewhat intentional as free TX are handled differently, according to git it will be "fixed" regardless. Setting it to 1 satoshi works fine.


[1] https://github.com/bitcoin/bitcoin/issues/2673

Maybe. Currently its just that one of the many blockchain explorers is not showing it.

When its confirmed the person receiving it can spend it. When the network forgets about it before it can get confirmed the person sending it can spend it again.

AFAIK blockchain.info stops rebroadcasting the TX after 2 or 3 days, their support should be able to tell you. I dont know how mycelium handles this. Rebroadcasting would never change the data, but just send them again as LaudaM already said.

Keep in mind that "increasing the fee in hindsight" is a double spend attack on your transaction as the network does not understand your motives. It just sees a 2nd transaction that tries to spend the same inputs as a TX that is already known. You can only achieve this if very few nodes (or even none at all) remember your 1st transaction. Otherwise nodes will reject the TX and you will have problems reaching a miner no matter how high you set the fee.

Yes, you can wait, but people will "cut the line" while you do. Many have already increased the fees when creating a transaction in order to get it to confirm fast. They will jump ahead in the queue in front of you and increase the time you have to wait to increase. Some miners also used the blocks they find to remove some of the inputs created by the spam, which is good for the network, but also means that the block will not confirm any other transactions. This also increases your time (as well as everyone elses) waiting time in the queue.

Unfortunately its that you have a certain position within the queue, e.g. spot 423593 and once the 423592 transactions in front of you are confirmed its your turn. Its more complicated and if the spammers can afford to spam the network for the next 3 months you will have to sit this out.

The alternative is to remove the TX from your bitcoin core so it does not longer rebroadcast it, wait for ~6-18 hours to make sure the network forgets about the transaction and create a double spend with a higher fee.


Nothing we currently experience with bitcoin should be considered normal. The network is under attack and we can certainly adapt to the situation should this become normal, but Id like to hope that we return to the usual waiting queue of 0-6k transactions soon.

We dont know, it all depends on the amount of coins the spammers want to waste.


Why do you think you received payment on that address? Was it confirmed? Which wallet software/service do you use? Do you have a transaction id?

AFAIK you just need a(ny) full node running bitcoin core. You can try mine[1] if you want.

Other than that you cant just use the wallet file from mSIGNA with another software. You would have to export the private keys and import them into the other software. Electrum 2 does no longer allow to import private keys AFAIK as that would defeat the purpose of a HD wallet and the easy backup via seed.

[1] 213.165.91.169

It will be confirmed once the spam[1] is cleared. It is unknown how long this will take. Your fee is enough considering normal circumstances, which we do not have currently.

[1] there are currently ~48k transactions waiting for a confirmation.

It all depends on the client you use. Bitcoin core will rebroadcast your transaction from time to time and thus it will get confirmed eventually as long as you keep the client open at least from time to time. Other clients will not do so and thus might get your coins stuck unless you can manually remove the TX from the clients memory.

Hatte vor ner Weile für die Werbung gemacht und eine geschenkt bekommen. Sprich sonst mal Mitchell[1] an der macht viele Verkaufthreads für die auf bitcointalk. Ich weiß das die ersten auf je 100 begrenzt waren, aber meines Wissens nach wollten die auch Nachschub produzieren.




[1] ehem. "bitcoininformation" https://bitcointalk.org/index.php?action=profile;u=113670

Ja, kann man. Die Frage ist welche Rückschlüssel gezogen werden können und was man damit anfangen kann.

Eine Transaktion besteht aus Ein- und Ausgängen. Eingänge sind alte Transaktionen über die du verfügen kannst. Ausgänge erzeugst du entweder für dich selber oder für jemand anderen. Je nach dem welche Eingänge benutzt werden kann man Annehmen das bestimmte Adressen der selben Person gehören.

Wenn du mit einer einzigen Transaktion Bitcoin an unterschiedliche Menschen schickst dann können die ebenfalls sehen das du mehrere Ausgänge erzeugt hast. Es ist aber oft nicht klar ob der Ausgang für eine andere Person ist oder z.B. Wechselgeld für dich selbst.

Genauso ist es nicht klar wer hinter welcher Adresse steht und das wird nochmal schwerer wenn man sich für alle empfangenen Bitcoin eine neue Adresse erzeugt. Dann muss man ein bisschen beim ausgeben aufpassen das man da nicht wild kombiniert und somit wieder zusammenhänge erzeugt. Dafür ist Multibit HD nicht so gut geeignet weil es die Eingänge für dich bestimmt und du keine Wahl hast welche genommen werden. Das geht soweit ich weiß zur Zeit nur mit bitcoin core und coin control.

Kurz gesagt: Bitcoin ist nicht anonym, egal mit welcher Walletsoftware (ggf. ist Darkwallet eine Ausnahme) sondern pseudonym. Es ist aber durchaus möglich das keine Rückschlüssel möglich sind zu:
- dir als Person
- deinem Gesamtvermögen
- deinen Handelspartnern

The fee is fine under normal circumstances. Once the spam[1] is cleared (whenever that is) your TX will get confirmed. Bitcoin core will keep broadcasting it until its confirmed.


No, when the network has forgotten your wallet has not. Bitcoin core will just rebroadcast it. You have to manually delete it from your local wallet with tools like pywallet.

[1] there are currently 40k TX waiting for a confirmation

Gern, wenn Du magst schreib hier wies ausgegangen ist.

We talked about it in the german section and OP did request coins from someone else to the address of a mixing service, thus the private key is indeed not under their control. OP used the address book feature from multibit to select an address, which is filled with addresses from other people. AFAIK OP tries to contact the mixing service now. My guess is that they will return the coins as this would otherwise be very damaging for their reputation.