I am rebroadcasting it every 30 minutes, let me know when its confirmed. Raw TX: 01000000035f7857b1bb5de999714b3fc3791aa0569825e5fe57d4c4ddd937ac4278bf0198000000006b483045022100a647f7ffe4c76cb9b0d4c0160915b4370e81251b9f8fba3d2d729e9023ef69f002201c374dcf4a953721e23c40ba11c63e4833543f8e7dad30f59b672664ae9ed55c012103d20289f78e459c52ade29f67da903b374ff5314a9421475d09c7c36aa1c787f3ffffffff23901e261b5edaca6714ca86f9b678a5fd65cf737031019a35cb6b44625fe0db000000006b4830450221008cd169289bbb5f017dbcf25eea9dc6e2326aff30a75c18ef5d7fff672c985d14022025596c65cf2df414bf47368245dad18697bd0ce4ac3bd0013dadf0fef0c90970012102890d978c0948ff7a1d5a3bd2be15b23a7d35cd71faff0bb0a4442144a19f3e32ffffffff0a1a227eef429357a64a9eae1b439f056719225b02fb87fb4ad9937690fbf4ef010000006a47304402206367d7145939d26b9ea6bd5dce8d38d7e84dd1f8da687e3955d46d02c85ec99902205750649c2435cd9edcf1b0673a13a3c56d5c817356945face38ebc3deaa706220121034f4b289ed261fffc5d254d735e97cb651517e74c3204ddcbc952d2565f5abdb2ffffffff015b381b00000000001976a9144eb5429756c6c8e5acf3df6f1a8b92789adec45488ac00000000
|
|
|
I am rebroadcasting it every 30 minutes, let me know when its confirmed.
|
|
|
I'll pay you $200 or 0.5BTC if you want just to include this transaction in a block; I can't wait
PM me if you have this possibility
You can send me the TX if you want, but an easier solution for this would be to set a 0.5 BTC fee. It goes to the miners after all.
|
|
|
From what was reported here, that claim makes no sense. It looks like the attack is just to request blocks over and over again. That is not a "DNS amplification". Im not even sure how its a (D)DoS attack at all as I suspect that core/classic/any other fork will limit the number of requests to their own capabilities. It will hardly crash the nodes, if anything it will result in the node no longer accepting external connections, which could be seen as a partial DoS.
|
|
|
Danke für die raschen Antworten @fronti & @Lutpin So ganz habe ich das noch nicht verstanden. Ich hatte mir drei der 20 Adressen bezeichnet ( also einfach als BTC-1, BTC-2, BTC-3 ). Da sendete ich von Poloniex einen Betrag an die erste Adresse. Einen Tag später bzw. heute habe ich diesen Betrag an einen Freund geschickt - und nun fehlt mir diese Adresse in der Auflistung ![Roll Eyes](https://bitcointalk.org/Smileys/default/rolleyes.gif) Gut, daß ich mehrfach empfangen kann, scheint klar. Die fehlen nicht, die sind nur versteckt. Wenn Du bei "used" auf das kleine - drückst, tauchen die benutzten Adressen wieder auf.
![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2F2CB40AI.png&t=663&c=uAs3thiopa2Qzg)
|
|
|
What exactly is the goal here? Double spend the original TX or keep sending it? It looks like the network pretty much forgot about your TX, so either is easily possible. -zapwallettxes removes unconfirmed TX from your wallet. Im not entirely sure what you mean with "I already used... -zapwallettxed". If you did you can just create a new TX. so I'm at hour 76 now..
@TigerMart: this perfectly looks like my transaction.. this is my only transaction for about 1 week..
any ideas how to solve? I already used -rescan, -zapwallettx etc.. desperate here -.-
I'm not an expert (just learning the technical aspect myself) but maybe you could: - search witch addresses contain coins - dumpprivkey - close the wallet, don't open it again - wait untill the network forgets about your transaction - sweep the private keys directly into blockchain (since you seem to want to use an online wallet). (-maybe you can import the keys into electrum, and create a double spend with a higher fee?) As i said before: i'm no expert... Maybe Shorena or somebody else with loads of knowledge can confirm/deny this method? I'd personally never use an online wallet to hold 0.9 BTC, but each to his own. If OP wants to replace the original TX and use an online wallet this is sound advice. I would however keep the key in core and just remove the TX with zapwallettxes.
|
|
|
Thanks to censorship, a 100% consensus has been reached in order to activate an effective block size decrease to 0.5MB on 1.4.2016
This highly anticipated fee event will boost miner revenues and serve as a bold warning to the illuminati behind the stress test.
After a successfull activation, the censorship on all social media will be lifted. This will cause a new consensus to be reached, for an urgent block size increase.
The subsequent massive block size increase will allow us to raise block size by 200%. This means, that the block cap will grow from 0.5 MB to 1 MB.
We expect that this massive increase will have a huge effect on the public image of Bitcoin, on the social media and will trigger a new major wave of adoption.
Can you cite your source? Herp Derp.
|
|
|
So mein Node läuft ja nun, zwar nicht als dienst aber ich starte ihn derzeit manuell... Im Log steht folgendes 2016-02-29 16:28:22 ERROR: AcceptToMemoryPool: free transaction rejected by rate limiter 2016-02-29 16:28:45 ERROR: AcceptToMemoryPool: free transaction rejected by rate limiter 2016-02-29 16:29:09 ERROR: AcceptToMemoryPool: free transaction rejected by rate limiter 2016-02-29 16:29:18 ERROR: AcceptToMemoryPool: free transaction rejected by rate limiter 2016-02-29 16:29:29 ERROR: AcceptToMemoryPool: free transaction rejected by rate limiter 2016-02-29 16:29:31 ERROR: AcceptToMemoryPool: free transaction rejected by rate limiter 2016-02-29 16:29:32 ERROR: AcceptToMemoryPool: free transaction rejected by rate limiter 2016-02-29 16:29:49 ERROR: AcceptToMemoryPool: free transaction rejected by rate limiter 2016-02-29 16:29:51 ERROR: AcceptToMemoryPool: free transaction rejected by rate limiter 2016-02-29 16:29:55 ERROR: AcceptToMemoryPool: free transaction rejected by rate limiter 2016-02-29 16:30:00 ERROR: AcceptToMemoryPool: free transaction rejected by rate limiter 2016-02-29 16:30:02 ERROR: AcceptToMemoryPool: free transaction rejected by rate limiter 2016-02-29 16:30:03 ERROR: AcceptToMemoryPool: free transaction rejected by rate limiter 2016-02-29 16:30:04 ERROR: AcceptToMemoryPool: free transaction rejected by rate limiter 2016-02-29 16:30:06 ERROR: AcceptToMemoryPool: free transaction rejected by rate limiter was bedeutet das? Das Dein Node eine Transaktion nicht akzeptiert hat weil die Gebühr die bezahlt wird zu gering ist und damit als "keine Gebühr" gilt. Für diese gibt es ein Limit um Spam einzudämmen und damit dem Node nicht der Arbeitsspeicher ausgeht. Die Grenze für eine Gebühr die zu klein ist soweit ich informiert bin 0.00001*5 pro kbyte bzw. 5 satoshi pro byte. Du kannst das mit folgender Option über die bitcoin.conf ändern. Der Text ist noch aus einer älteren Version, daher *5 # Minimum transaction relay fee minrelaytxfee, which defaults to 0.00001. This will cause transactions # with fewer BTC/kB fee to be rejected, and thus fewer transactions entering the mempool. # The minimum setting is 100 satoshi, modify limitfreerelay if needed. minrelaytxfee=0.000001
Weiterhin kannst Du die Anzahl der "keine Gebühr" TX einstellen. Eingestellt werden die Kilobyte pro Minute die akzeptable sind. # This option sets the number of kB/minute at which free transactions (with enough priority) # will be accepted. It defaults to 15. Reducing this number reduces the speed at which the # mempool can grow due to free transactions. limitfreerelay=150000
Mit meinen Einstellung versuch ich möglichst alles zu akzeptieren.
|
|
|
I wish I knew why mine were stuck. Verified addresses, transaction fees, they should do right through. But they have been stuck almost a day.
I imagine you have the same problem as everyone else. the tx fees is not high enough to get your tx through the currently flooding mempool. (btw I think you're kind of hijacking someone's thread.) Sorry, same issue... Waiting!! If you post the TX ID I can rebroadcast the transaction, it might help a bit.
|
|
|
![Undecided](https://bitcointalk.org/Smileys/default/undecided.gif) Crap. Well I tried warning as soon as I received the PM from OgNasty Edit: Not to rub salt on the wound but it'd be funny if the trolls said that the negative was given solely on suspicion actually I think shorena successfully helped OP double spend the tx (using his node). I had help. ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
@Intermediary I really hope you are online and read your PMs.
|
|
|
super werde ich auf meinem Node gleich implementieren ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) Fettes DANKE! Kurze OT Frage wenns erlaubt ist: Auf was hast du deine Node laufen? Bin auch am überlegen einen Raspberry als Node zu bereiben oder mir einen VPS dafür zuzulegen. Geht im moment primär ums unterstürzen des Netzwerkes. Hab mir grad den hier für 12 Monate bestellt -> https://www.netcup.de/bestellen/produkt.php?produkt=1102100 EUR für n Jahr find ich ok, ansonsten läuft über die Hausleitung auch einer mit, aber der Rechner ist nicht konstant an.
|
|
|
super werde ich auf meinem Node gleich implementieren ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) Fettes DANKE! Bidde. Keine Ahnung wie man das noch "anschieben" könnte. Zurzeit sind mal wieder über 11.000 unbestätigte Transaktionen in der Pipeline.
Da ist einiges in der Warteschlange, yop. ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FJtwU70t.png&t=663&c=ani-vJKwVoIDXw)
|
|
|
Alle 30 Minuten wiederholen, einmal schubsen bringt nix. Windows .bat Datei: @echo off :start echo --- "c:\Program Files\Bitcoin\daemon\bitcoin-cli.exe" sendrawtransaction <rawtxhere> echo --- echo Time: %time% waiting 30 minutes timeout /t 1800 /nobreak > NUL goto start
für Linux n cronjob einrichten der bitcoin-cli sendrawtransaction <rawtxhere> (kann natürlich auch in ner ausführbaren Datei stehen) alle 30 Minuten ausführt. Ausstellen/cronjob entfernen nicht vergessen wenn die TX bestätigt ist. .bat in Aktion: >willi9974.bat --- aebe2bb6343331d410f4106392f861258d69c5410334acdc0bba2c0ea142b4ec --- Time: 16:32:17,16 waiting 30 minutes
|
|
|
I have a possibly dumb question that might have been answered (there isn't a way to show all posts in the thread that would make it feasible to properly search), but my girlfriend and I can't add each other on the Steam network because neither of us have spent any money on games (we have only played free games so far - essentially warface & batla). Are your codes or products considered gifts in the eyes of Steam? I.E. Will my account have gotten credit for spending something? If this isn't the case, is there any way of working something out where the purchase shows as such?
Gifted games do not remove the limit. See here[1] you need to spend 5 USD on steam in order to get the restrictions removed, gifted games do not counter toward that limit. You could however add 5 USD to your steam wallet without spending them. [1] https://support.steampowered.com/kb_article.php?ref=3330-IAGK-7663&l=english
|
|
|
I'm very sorry if it seems so; i'm seriously confused right now and have a very silly question:
where to find sending adress?
edit: part of the btc lost i received via
17xCC21F3JKXby4kZwBw55tLf2e5txNQn1
QT/core does not just forget about a transaction, you have to tell it to do so. #1 close core/qt (if you are still on "qt" you should update to 0.12 btw) #2 make sure its fully closed #3 start with -zapwallettxes, e.g. on windows you: #3.1 hit win+r (to open run) #3.2 enter: c:\Program Files\Bitcoin\bitcoin-qt.exe -zapwallettxes (modify path if needed) and confirm with ok #4 let core do its thing, it might take a few minutes to a few hours depending on your overal system speed (CPU, disk mainly)
|
|
|
1KATWALSHTHECuz5DFHoNqJax6hnDbL6KN (I can sign with it if you want)
Any vanity pubkeys category? If so, I win:
0200000000000000000000003b78ce563f89a0ed9414f5aa28ad0d96d6795f9c63
14 letters ![Shocked](https://bitcointalk.org/Smileys/default/shocked.gif) what are you searching with? and uh... what exactly is KATWALSHTHECuz? It's not the longest pronounceable or the longest real-word (not that I can see anyway - is it English or another language?) Maybe a different category? KATWALSH must pe the guy's nickname or something... Greg Maxwell's hidden identity is revealed -> https://twitter.com/mindspillage
|
|
|
Is there a forget 14 day ban after, let's say 6 months or so? Since otherwise the risk that another ban might be a permaban sounds pretty high. And the longer someone is a member on here the higher the chance would rise to get another one. Is there something like that?
You get 3 strikes after which you are perma banned(with no "time limit" after which it is "forgotten"). Next one is temp ban of ~30-60 days I'd say, so yup, be careful about posting with a sig Edit: Anyway, too much pessimism for a post. Welcome back AFAIK this only applies if you are banned for the same reason.
|
|
|
|