Pages:
Author

Topic: . - page 2. (Read 2985 times)

legendary
Activity: 1232
Merit: 1001
February 11, 2014, 10:28:38 AM
#19
How convenient this issues pop up in masses right now  Roll Eyes

https://bitcointalk.org/index.php?topic=460055.0;topicseen

https://bitcointalk.org/index.php?topic=459990.new#new

although, yes nobodies coins could be stolen this way. It shows there are still issues in the protocol that need to be fixed, before Bitcoin can "go Mainstream".
legendary
Activity: 2394
Merit: 1216
The revolution will be digital
February 11, 2014, 10:14:26 AM
#18
All tonight all my transaction ids are being changed. It's getting annoying.

Dumb fuckers want to prove a point. Probably that fat ass from gox. Fuck him.

Armory is counting them, I wonder how it will handle it when the nodes stop relaying the double spend.

Whoever is doing it, has very fast and well connected nodes. Even a transaction I sent directly into 100s of nodes was overwritten.

I guess this is something related to Bitcoin-QT. BlockChain.info wallets are not facing this problem. Gavin is too bz at CoinBase and no one is there to fix the Bitcoin-QT bug Wink
hero member
Activity: 968
Merit: 547
February 11, 2014, 10:05:58 AM
#17
Quote
Whoever is doing it, has very fast and well connected nodes. Even a transaction I sent directly into 100s of nodes was overwritten.
That is weird. I doubt that the "attacker" was one of the these nodes. Under the assumption that all nodes need the same time to process a transaction and that at least one node is connected to a miner, you are at least one node ahead of the "attacker". So how is he able to be faster?

Where did you send the coins from? Bitcoin-QT?
full member
Activity: 168
Merit: 100
February 11, 2014, 10:05:00 AM
#16
In la you drive around the pot holes.

Bitcoin -- where we don't fix bugs but tell you how to avoid them.

Yes, a bit over the top. But come on, if you spend more time talking about it than fixing it, you might as well fix it.

Don't tell me you are happy with all these duplicate transactions?
legendary
Activity: 2912
Merit: 1060
February 11, 2014, 09:59:21 AM
#15
.
full member
Activity: 168
Merit: 100
February 11, 2014, 09:57:50 AM
#14
hows mean in russia we dont play round big holes at the play ground

My point exactly. Smiley

You fix an issue instead of expecting everyone to work around it.
newbie
Activity: 13
Merit: 0
February 11, 2014, 09:56:45 AM
#13
hows mean in russia we dont play round big holes at the play ground
full member
Activity: 168
Merit: 100
February 11, 2014, 09:46:48 AM
#12
Software that's correctly implemented in the face of transaction malleability will not be bothered by these duplicates.

Yes, so?

If there is a big hole in the yard and everyone should know not to fall into it, it does not mean it is a good idea to leave it there.
legendary
Activity: 1274
Merit: 1004
February 11, 2014, 09:37:17 AM
#11
Well looks like it's happening with the users who are using default bitcoin client or bitcoind (ie some web based wallets)

I have sent some payments via my electrum wallet and nothing happend.
Elo
newbie
Activity: 14
Merit: 0
February 11, 2014, 09:35:35 AM
#10
Anyone who is affected by this issue needs to improve their software, period.

The fact that anyone other than Gox is bothered by this shows that they might have been right in claiming that more than just their implementation is susceptible.

Software that's correctly implemented in the face of transaction malleability will not be bothered by these duplicates.
full member
Activity: 168
Merit: 100
February 11, 2014, 09:16:04 AM
#9
This is fat ass gox

He doesn't want to change their software so he's annoying everyone into changing theirs. Piece of shit.

Well ...

The fact that this can be annoying kinda makes the point that it should be addressed.

It would be sad if it is not addressed just because Mt.Gox wants it.
legendary
Activity: 2912
Merit: 1060
February 11, 2014, 09:13:12 AM
#8
.
legendary
Activity: 2912
Merit: 1060
February 11, 2014, 09:11:14 AM
#7
.
newbie
Activity: 1
Merit: 0
February 11, 2014, 08:53:48 AM
#6
You can view the raw scripts with https://blockchain.info/rawtx/hash?scripts=true

It looks like the push data operator was changed from 48 to 4d4800, which both mean push 72 bytes on the stack.
full member
Activity: 168
Merit: 100
February 11, 2014, 08:50:37 AM
#5
Interesting, maybe that explains these ...

bitstamp btc withdrawal problem
BTC-e withdrawal issues?
legendary
Activity: 2912
Merit: 1060
February 11, 2014, 08:36:31 AM
#4
.
sr. member
Activity: 406
Merit: 250
February 11, 2014, 08:34:21 AM
#3
How can it be tagged as double spent and still be confirmed? What is going on?
legendary
Activity: 2912
Merit: 1060
February 11, 2014, 08:22:50 AM
#2
.
legendary
Activity: 2912
Merit: 1060
February 11, 2014, 08:19:00 AM
#1
.
Pages:
Jump to: