Darnit, i want to buy more!
stimated Confirmation Time 16 hours (queue position 939)
Lol and getting higher:
Estimated Confirmation Time 16 hours (queue position 1048)
Holy hell: Estimated Confirmation Time 18 hours (queue position 1304) Thats not the real time, I had over 24 hours but in about 20 minutes it showed 2 confirmations. Not sure why it does that now but seems to be delay. Ye it went through. Now, let the price rize to 0.00035  2861.43026243SMC on my account  |
|
|
|
Darnit, i want to buy more!
stimated Confirmation Time 16 hours (queue position 939)
Lol and getting higher:
Estimated Confirmation Time 16 hours (queue position 1048)
Holy hell: Estimated Confirmation Time 18 hours (queue position 1304) |
|
|
|
|
Darnit, i want to buy more!
stimated Confirmation Time 16 hours (queue position 939)
Lol and getting higher:
Estimated Confirmation Time 16 hours (queue position 1048)
|
|
|
|
|
Well,
It seems for me it has not yet corrected itself.
I still have 3 transactions pending, 2 of which are from the 11th 00:44AM which are double spends.
Any clue when they will be removed?
Also a transfer of 0.10x BTC is still pending, this one is more critical as its current value is 46,50 which at the moment is quite much for me.
|
|
|
|
P2Pool UpdateWe intend to update the network information for p2pool in our official repo. The updated code is available now, but the network wont officially be live until the listed date.This involves a change to how long a share is valid, currently a share is only valid for 3 blocks. This setting was borrowed from Litecoin, and it has proven to be too low for us. With this new update it will be adjusted to 12, that should hopefully improve the p2pool experience for people with low hashrates everyone. As every worker's share will now be valid for a longer period. Another change (thanks to roy7) in this update is that share difficulty is now calculated on a per-worker basis instead of on a per-node basis, so share difficulties should be lower, to make it more like mining on your own node (if you're mining on a public node). This update requires a hard fork of the network, which means we will have two p2pool networks running in parallell for some time while everyone interested updates to the newer version. Don't panic, it won't be like hardforking a wallet, no paid coins will go invalid. It just means that to benefit from this update you need to upgrade to the new settings. It might also mean that blocks will come a little slower for a while if not everyone comes along with the update (as we will split into two). The point of this pre-announcement is to mitigate that. Also moving to this new network means that the we'll get a new sharechain, a.k.a. any shares from the old network won't transfer over. The p2pool scanner and all the seed nodes will be upgraded to this version on 13th february at 22.00 GMT. Any node left on the old network will continue operating as normal, but will not show up in the scanner until upgraded. Hopefully people will catch on fast and update. Cool i was waiting for this. With a bit of luck, i might be able to set up a p2pnode for myself now  |
|
|
|
i think im going to buy again, with 0.1298BTC
its on transfer now....
Advise, wait a few hours. I'm driving the price down to 0.6, if possible 0.5. Started at 0.9 this morning. 0.5 is a good buy moment, after 35000block it's grow time. to late 1800SMC |
|
|
|
|
i think im going to buy again, with 0.1298BTC
its on transfer now....
|
|
|
|
I am a normal user, affected by this issue and lost money, now all bitcoin transactions should be stopped to prevent this happening, or the dead of bitcoin.
How did you lose money? Please elaborate. Well, then someone who has been here longer then yesterday. I have a payment of 0.10btc pending since yesterday. I cannot find it in the blockchain so i hope it will correct itself. |
|
|
|
Thank you, was looking for more info  |
|
|
|
Well, things just got a bit wierder. So i made a blockchain wallet to relay all my BTC there, make a new wallet and send it back. So, first, offcourse 0.01 sent, went good. Then the rest in small transfers. 0.02 0.1 0.2 And then the last 0.10724272 which is including a total fee of 0.002 All of the transfers went trough, confirmd ect. Except for 1 the last transaction of 0.10724272 It is not known on the network, is still unconfirmed. Status: 0/onbevestigd
Datum: 11-2-2014 19:16
Aan: 1AgfBT3XNuwF9J49R7hiv5Py6spppEmQ2i
Debet: -0.10704272 BTC
Transactiekosten: -0.0002 BTC
Netto bedrag: -0.10724272 BTC
Transactie-ID:: a2b9beae85e11f8fdc8937fed8995b22b43048e6ec01a876e81c9dd8f8e95542 sorry for the dutchPlease note that the copy's of the 2 transactions i sent yesterday are still unconfirmed. Getting stranger for me. Stop making transactions and read the link I posted above. Ye ill stop it, seems we have to ride it out. Its now in a blockchain wallet protected under a 16 random char password. Safe enough for the coming days. |
|
|
|
Well, things just got a bit wierder. So i made a blockchain wallet to relay all my BTC there, make a new wallet and send it back. So, first, offcourse 0.01 sent, went good. Then the rest in small transfers. 0.02 0.1 0.2 And then the last 0.10724272 which is including a total fee of 0.002 All of the transfers went trough, confirmd ect. Except for 1 the last transaction of 0.10724272 It is not known on the network, is still unconfirmed. Status: 0/onbevestigd
Datum: 11-2-2014 19:16
Aan: 1AgfBT3XNuwF9J49R7hiv5Py6spppEmQ2i
Debet: -0.10704272 BTC
Transactiekosten: -0.0002 BTC
Netto bedrag: -0.10724272 BTC
Transactie-ID:: a2b9beae85e11f8fdc8937fed8995b22b43048e6ec01a876e81c9dd8f8e95542 sorry for the dutchPlease note that the copy's of the 2 transactions i sent yesterday are still unconfirmed. Getting stranger for me. |
|
|
|
Great well done. Solved. As it should be. I dunno why but I mostly prefer android Bitcoin Wallet. Its working great for me. And I am not a miner, so I dont need qt I am quite happy this happened because it is proof positive that you cannot double spend. So i am happy about that Im not, takes valueble time away from mining. Although i see your point i was trying to see the brighter side of the issue. Even from a bad situation some good comes from it however inconvenient it may be... Also as a miner i am sure you must have several wallets 1 for mining one for payments etc etc. Nope, using 1 wallet with a 15char random generated password backed up over 5 harddrives and 2 diffrent locations |
|
|
|
Great well done. Solved. As it should be. I dunno why but I mostly prefer android Bitcoin Wallet. Its working great for me. And I am not a miner, so I dont need qt I am quite happy this happened because it is proof positive that you cannot double spend. So i am happy about that Im not, takes valueble time away from mining. |
|
|
|
i'm wondering about something. I'm mining on p2pool, current node http://p2pool.etyd.org/However, i'm also seeing that there are a lot of blocks found in the last hours, when i check my miner i see shares being accepted. But, i havent recieved any transactions for 8 hours already but in that timespan about 14 blocks have been found already. Either i'm missing something or i'm not getting payed all the time. Anyone who can explain? You only get paid if you have shares in the sharechain. Click on Graphs and find your address, you can see a history graph of how much value you had in the share chain plotted over time. If you run less than a couple MH you might try mining on my east node for now, I'm running a test patch to p2pool to lower variance for smaller miners. (Your shares are worth less value but you find them more often, so payments are more steady. You don't make any more/less income though.) Pool link in my sig. (West node is not running test patch.) US is a bit far from the EU, so better not do that But this is what i'm seeing in my miner:  setup your own node, and payout issues will go away. im assuming you have quite a bit of horsepower if your payouts are this large. i was getting sporadic payments with 600kh/s. setup my own node, and never had an issue again This is the payout scheme for me btw:  setup your own node, and payout issues will go away. im assuming you have quite a bit of horsepower if your payouts are this large. i was getting sporadic payments with 600kh/s. setup my own node, and never had an issue again Do you have a good how-to? I have 2 VPS's at my disposal, 1 windows, 1 linux 1. get a linux wallet 2. setup this p2pool - https://github.com/donSchoe/p2pool-vtcif you are not familiar with compiling stuff in linux, try to run p2p in windows. The link in 2 describes how. I know my linux quite a bit, ill try it today. |
|
|
|
you just received free money then...? Probably, but no incoming transfers so that seems a bit wierd to me. What i think i'm going to do is boot up a second pc and install QT there. then transfer all of it to that wallet and see what happens. |
|
|
|
|
Ok, seems betarigs approved the transfers, however i still have a higher balance then i first had.
Also i still see the other 2 transactions, even after doing a -rescan & restarting the QT
|
|
|
|
|
7.5 hours in, still not corrected.....
|
|
|
|
Someone is having fun modifying (just the signature not the amount, fee, source, or receiver) and rebroadcasting your tx due to signature malleability. Not sure if it is just to be an ass, or to prove a point.
However each tx in the pair uses the same inputs so only one can be confirmed in a block and the network will then drop the other as a double spend.
Ah ok, so i'll just have to ride it out then? Also after that, will my balance return to the number i had expected? And how long can it take? |
|
|
|
|
Show Posts
