Re:Mt.Gox Withdrawals
by Anderkent on Thursday February 06, 2014 @06:25AM
(#7189799)
A client sets his mining address directly to their MtGox deposit address. Different client tries to withdraw the funds. MtGox grabs a couple output it owns without regard to its age and tries to send it to the withdrawing client. The transaction is delayed because some of these outputs are fresh.
[ Parent
| on HN ]
But "everyone" is poolmining. And the pools are surely professional enough not to mine directly into mtgox?
Not sure if serious. First of all, 'professional'? In bitcoin?
Anyway, how does the pool know the address you gave it is a mtgox deposit address rather than a personal address of yours?
p2pool is one example.
I see, thanks. I don't really see how that could lead to so many dealyed transactions though.
A freshly mined coin is not valid for 120 generations. That's to avoid transactions being voided if the very end of the blockchain switches (if the chain is A->B->C, and you spend coins mined in B in C, but then the chain is overtaken by A->D->E->F, your transaction is invalid (coins genrated in B won't appear in the new chain))