[edit] after some time i let cgminer run i see this : Accepted 0ccd5c51 Diff 5.12K/2048 BSD 0
so i see now 1 accepted is that correct ? that should go faster or do i miss here some things in settings ? ;-)
Most pools use manual and variable difficulty settings per worker. Sounds like this pools start off at 2048 for the miner. If there is a manual setting on the interface, you can set the worker to their lowest value or about 32-ish. With vardiff, the pool will sense the gap between your accepted shares and adjust it over time. It doesn't make much difference mathematically since that 5120(5.12K) share there is like a 160 x 32 diff shares. You just get to see the Accepted message more often.
|
|
|
hello, the app is not working properly. There is no data on any screen.
Tidying up after some hosted hardware failures. Should return to normal shortly.
|
|
|
The potentiometer will go full circle, past max will return to minimum.
|
|
|
No, unconfirmed means it's not there. I'll check if I can add it onto viabtc for you in one of these next cycles they have open for submissions. I would say it's about time for it to return to your wallet, but I guess that won't be good in your particular case.
edit(1): looks promising... viabtc response: Transaction added to acceleration queue
edit(2): confirmed Included In ViaBTC Block 504085 ( 2018-01-13 20:11:45 + 41,993 minutes )
|
|
|
managed to get your tx into viabtc queue this last hour. they should have that confirmed for you in one of their next blocks.
edit: confirmed Included In ViaBTC Block 503988 ( 2018-01-13 06:01:05 + 2,603 minutes )
|
|
|
took a little while, needed to get that parent tx out of the way first: tx: 101fb219c3c1a75f8e89745131b9405c7a0c940a5ec068f71e284776e3afeae4 Included In Blocks 503646 ( 2018-01-11 08:06:17 + 50,065 minutes )
your tx now confirmed; Included In Blocks 503704 ( 2018-01-11 15:25:34 + 9,470 minutes )
|
|
|
Here's two tips if you are trying yourself:
1. A good UTC clock running as mentioned above. 2. Try only with small tx. Don't bother with tx > 1KB, I firmly believe they post that message up to mess with your time.
|
|
|
I'll check if I can grab one of those hourly free viabtc spot for you. There's an unconfirmed parent tx that needs to go through first, so I'll start there.
|
|
|
Where do you want it to end up at?
If you just want it in another wallet, carefully export the private key. Check through the menu. No fees involved.
|
|
|
Included In ViaBTC Block 503386 ( 2018-01-09 20:01:56 + 11,880 minutes )
no block for 10 hours huh. i suppose it's normal that even big pools suffer from bad luck variance.
you're all set otherwise.
|
|
|
Sorry to say it's still stuck. At this time, there are 0 confirmations. Is it too soon to be checking?
Not too soon, but too soon at the same time. Visit here to check for their next block: https://blockchain.info/blocks/ViaBTCThey average about a block per hour, but haven't found one in the last 5. It happens occasionally, averages.
|
|
|
Got you covered. The pending tx for that address : bdbf3d07a4f8272f7695d2aa5a5bc244534d515d315f846ec9f3a71b4bffcc87 was accepted onto viabtc's free acceleration queue. They should have that unstuck for you on their next block.
|
|
|
i figured an extra person will increase the odds at viabtc for you, so i gave it a couple of tries and got through on this last hour. tx: 6dd64abfba3962f90d9db87756672473fed3dc8a3e347159e669332d1dc14585 reply: Transaction added to acceleration queue
it should confirm on their next block.
edit: confirmed Included In ViaBTC Block 503215 ( 2018-01-08 18:31:15 + 13,999 minutes )
|
|
|
these two tx are dead. pending is of no value. it will expire and be forgotten about at some point in the future.
tx1 = af7337db5b6b5b3626d3ff6a7eb9866936a8ca2a336ca4e7e553a5aab2a6a7fe tx2 = d2c8fe92f6f7f76ed967b47e6bfc8a411a5e28f2540c2da95cee6bd9da5c0c0a
tx3 = 04272f25818acfcc8e97ab796cb22921bef9725380b185d08feb9a4fe7a05a19
tx -> tx1 -> tx2 tx -> tx3 (double spend of tx (inputs) and confirmed)
tx1 is no longer valid, therefore tx2 will never confirm.
|
|
|
as of right now, these other parent tx(s) needs to confirm before your's is considered. from bottom to top. e6ba9bfe22b58be8cf500cd042d84759ed9dd3b9845c13f273a779d4635cbe4c 001eec311cdbc54a028a1917e28b9aeb5fa8987803b2dcf272bcb7e0e420f03b 4f1491a2402e69bdf54619fe0a991d4c9290e308331ac88f253797a2e6b318cc 65974ef083877179ccd819ce407102bee828a955da33ad896434b107e90260ee 2fe499f296cf012f10e8b523b9b608c879092b9bb3cd2e8224010f5d38c8a3f8 a616c4bcf80f4e143bb7c0d6cb0c88ea4660bad40a761f1ac39bc5252bc29b5d 7a3131bfa2bd9466ec8f5bce9d5997791f25b5b0f51972aab12808eb5275a407 95218fd7d7bda176b24092cc9d34108ba131e0fc57c97e4e3c9d2d007c2f5fc2 8b6dd79afe277edf9132d2fa1cd16eeba164d46ec3fefd21672220bc370dcce5 41aef5648c48d335e4501aa910f0e9424330850ecfdea4ba0c94cbac4acdf256 d351a5eb3a6d50120256be73369930046a1c7af94ae73b0c41f1a47c420637f5 6a559d1f9c2aa3477a1d5e4fa648cefe96e1983e08b3e94f9a54ca6c73680122
|
|
|
got your tx accepted by viabtc accelerator. https://pool.viabtc.com/tools/txaccelerator/it should finally confirm with their next block. edit: confirmed Included In ViaBTC Block 502807 ( 2018-01-06 07:05:29 + 28,744 minutes )
|
|
|
223 - 0.00033663 Managed to get one onto viabtc queue.
Doesn't solve the problem directly but with the CPFP you put together, you should have an avg sat/B of 434.8 once that confirms. 223 - 0.000448 225 - 0.0015 -- 448 - 0.001948
edit: looks like they went ahead and picked up the other two due to the new sat/B (502775). saves you a few minutes.
|
|
|
reply: Transaction added to acceleration queue
edit: confirmed.
Included In ViaBTC Block 502426 ( 2018-01-03 21:12:39 + 22,189 minutes )
everytime you jumped in to help accelerate, the tx gets confirmed in less than an hour care to share how you do it? or do you have special account on viabtc? it's even more reliable than most free accelerator with open threads on this forum it's seems reliable because you are reading the post after it is accepted. viabtc finds a block every 1.15hours. which is why it appears to resolve within an hour. https://bitcointalk.org/index.php?topic=2669317.msg27272262#msg27272262
|
|
|
|