amaclin
Legendary
Offline
Activity: 1260
Merit: 1019
|
|
August 27, 2014, 10:42:53 AM |
|
Hello all, so basically yesterday i pushed a raw transaction here http://eligius.st/~wizkid057/newstats/pushtxn.php and i got this hash i went to blockchain.info and searched for the hash i did knew that if i push a raw tx directly to eligus my tx won't show up on any block explorers but it did You are wrong. Eligius broadcasts all transactions to its peers. In case of non-standard transactions peers reject/drop them. But your transaction was quite standard. It was accepted by bc.i and ghash and other nodes is that a bug or anything? It is normal behavior of bitcoin network. Does that mean that eligius no longer supports (relays and mines) non standard transactions? No, it does not mean that.
|
|
|
|
wizkid057 (OP)
Legendary
Offline
Activity: 1223
Merit: 1006
|
|
August 27, 2014, 12:19:14 PM |
|
Hello all, so basically yesterday i pushed a raw transaction here http://eligius.st/~wizkid057/newstats/pushtxn.php and i got this hash i went to blockchain.info and searched for the hash i did knew that if i push a raw tx directly to eligus my tx won't show up on any block explorers but it did You are wrong. Eligius broadcasts all transactions to its peers. In case of non-standard transactions peers reject/drop them. But your transaction was quite standard. It was accepted by bc.i and ghash and other nodes is that a bug or anything? It is normal behavior of bitcoin network. Does that mean that eligius no longer supports (relays and mines) non standard transactions? No, it does not mean that. The pushtxn script has *always* broadcast valid txns to all peers, which generally includes other pools. This has not changed. Other peers may drop or reject the transaction for whatever reason, but Eligius always broadcasts it.
|
|
|
|
yakuza699
|
|
August 27, 2014, 12:29:15 PM |
|
You are wrong. Eligius broadcasts all transactions to its peers.
Correct. In case of non-standard transactions peers reject/drop them.
Wrong. As far as i know eligius accepts all transactions as long as it pays fee and are non "correct battery horse staple"(or something like that) But your transaction was quite standard. It was accepted by bc.i and ghash and other nodes
Correct. I have never said that my tx was non standard. It is normal behavior of bitcoin network.
I was talking about http://eligius.st/~wizkid057/newstats/pushtxn.php I think you misunderstood me, what i was pointing out is that that eligius doesn't mine the transaction that i push on their site by their own, before(like 1.5 months ago) when i push raw tx on their site they don't show that tx to the network and my transaction will only show up when they mine a block.
|
|
|
|
Luke-Jr
Legendary
Offline
Activity: 2576
Merit: 1186
|
|
August 27, 2014, 01:06:55 PM |
|
Off-topic, but just in case anyone reading here is interested... FreeAbode
Can that thing display the current eligus hashrate and block times? That's what I want on my wall. Haha, no reason it couldn't!
|
|
|
|
amaclin
Legendary
Offline
Activity: 1260
Merit: 1019
|
|
August 27, 2014, 01:51:01 PM |
|
As far as i know eligius accepts all transactions as long as it pays fee and are non "correct battery horse staple"(or something like that)
Right. But you should see the difference between "accepts" and "relays". Eligius relays all valid transactions they don't show that tx to the network and my transaction will only show up when they mine a block. May be it was a temporary problem with "showing site" or relaying transaction in past. Of course, it is possible for Eligius to keep transaction and not broadcast it to network. But as far as I know, they do not do such things.
|
|
|
|
wizkid057 (OP)
Legendary
Offline
Activity: 1223
Merit: 1006
|
|
August 27, 2014, 04:41:06 PM |
|
Of course, it is possible for Eligius to keep transaction and not broadcast it to network. But as far as I know, they do not do such things.
Eligius does not and has never done this with any transactions.
|
|
|
|
not.you
Legendary
Offline
Activity: 1726
Merit: 1018
|
|
August 27, 2014, 05:25:21 PM |
|
Is there a reason my estimated amount went down? My hashrate is unchanged, pool hashrate is mostly the same, difficulty is unchanged. And yet estimated amount has gone down something like 20%.
|
|
|
|
wizkid057 (OP)
Legendary
Offline
Activity: 1223
Merit: 1006
|
|
August 27, 2014, 05:32:28 PM |
|
Is there a reason my estimated amount went down? My hashrate is unchanged, pool hashrate is mostly the same, difficulty is unchanged. And yet estimated amount has gone down something like 20%.
Pool wide hash rate, your hash rate, difficulty, consistent vs intermittent mining are basically the only things that affect the next-block estimates. Cant investigate further without your address... but since there are no issues with the pool's reward system it's probably pointless since it will just be one of the factors I've mentioned.
|
|
|
|
not.you
Legendary
Offline
Activity: 1726
Merit: 1018
|
|
August 27, 2014, 06:10:51 PM |
|
Is there a reason my estimated amount went down? My hashrate is unchanged, pool hashrate is mostly the same, difficulty is unchanged. And yet estimated amount has gone down something like 20%.
Pool wide hash rate, your hash rate, difficulty, consistent vs intermittent mining are basically the only things that affect the next-block estimates. Cant investigate further without your address... but since there are no issues with the pool's reward system it's probably pointless since it will just be one of the factors I've mentioned. As the round goes longer my estimated is going up. I had mined on this address from like Jan to May or something like that and then stopped. Then I started on this one again with my new S3's which would be maybe a little over a month now. Is it possible that all the recent good luck means my only shelved shares are months back in the queue so when a round starts my estimated is low until the round is long enough that only shares from the current round are being paid?
|
|
|
|
wizkid057 (OP)
Legendary
Offline
Activity: 1223
Merit: 1006
|
|
August 27, 2014, 06:29:13 PM |
|
Is there a reason my estimated amount went down? My hashrate is unchanged, pool hashrate is mostly the same, difficulty is unchanged. And yet estimated amount has gone down something like 20%.
Pool wide hash rate, your hash rate, difficulty, consistent vs intermittent mining are basically the only things that affect the next-block estimates. Cant investigate further without your address... but since there are no issues with the pool's reward system it's probably pointless since it will just be one of the factors I've mentioned. As the round goes longer my estimated is going up. I had mined on this address from like Jan to May or something like that and then stopped. Then I started on this one again with my new S3's which would be maybe a little over a month now. Is it possible that all the recent good luck means my only shelved shares are months back in the queue so when a round starts my estimated is low until the round is long enough that only shares from the current round are being paid? Sounds about right. Falls under the consistent mining portion of my previous explanation. Consistent being 24/7 for multiple months, IMO.
|
|
|
|
la7eralus
Newbie
Offline
Activity: 38
Merit: 0
|
|
August 27, 2014, 08:23:55 PM |
|
I've been over the confirmed BTC payout threshold for over a day and a half now, the "timer" has said 0 seconds to enter payout queue for several days now, and my balance still shows a full wallet on eligigius - with no mention of my address whatsoever in the payout queue of my BTC wallet address. Any idea's what's going on? I only started mining with eligius 5 days ago or so now, so i'd wondering if this extended delay normal? Do payouts generally run several days behind?
I suppose it's not that big of a deal as my balance continues to grow, so I'm getting credit for my hashrate, it just worries me because there is no manual withdraw method and as I have been over the payout queue threshold for some time now I'm beginning to wonder if/when it will properly trigger the payout.
Thanks in advance, and hopefully someone familiar with eligius can shed some light on this.
|
|
|
|
sorry2xs
Legendary
Offline
Activity: 924
Merit: 1000
Dark Passenger Bitcoin miner 2013,Bitcoin node
|
|
August 27, 2014, 09:07:40 PM |
|
that is normal check out the faq's i t explains how the pay out queue works
|
Please tip the Node 1MPWKB23NsZsXHANnFwVAWT86mL24fqAjF; KO4UX THAT NO GOOD DO GOODER BAT!!!
|
|
|
la7eralus
Newbie
Offline
Activity: 38
Merit: 0
|
|
August 27, 2014, 10:49:46 PM |
|
I seem to have discovered the issue, and it seems it could be a possible bug.
What seems to have happened: I changed my minimum payout threshold to 0.015 BTC, after the balance had already reached a point higher than that. As such, it didn't seem to "trigger' the payout as the threshold had been bumped lower than the current BTC balance. Once I changed the threshold to something higher than the BTC balance on eligius, once it reached that amount it successfully "triggered" the payout into the queue system.
So, it would appear changing the minumun threshold for payout "jumped" over the trigger, and resetting to an amount yet to be attained it successfully triggered when hitting that point.
|
|
|
|
robyone
Newbie
Offline
Activity: 43
Merit: 0
|
|
August 28, 2014, 01:48:55 PM |
|
Sounds about right. Falls under the consistent mining portion of my previous explanation. Consistent being 24/7 for multiple months, IMO.
does cgminer restart every hour affect profit on Eligius apart from apparent 10-15 seconds no hashing time it takes for a restart? i.e. is it considered a pool hop, do I get less reward than if I would not restart? I ask this because this is only way I seem to be able to keep my 12 hour AVG up on my lemon S3.
|
|
|
|
Luke-Jr
Legendary
Offline
Activity: 2576
Merit: 1186
|
|
August 28, 2014, 01:57:09 PM |
|
Sounds about right. Falls under the consistent mining portion of my previous explanation. Consistent being 24/7 for multiple months, IMO.
does cgminer restart every hour affect profit on Eligius apart from apparent 10-15 seconds no hashing time it takes for a restart? i.e. is it considered a pool hop, do I get less reward than if I would not restart? I ask this because this is only way I seem to be able to keep my 12 hour AVG up on my lemon S3. Eligius does not penalise pool hoppers, so no.
|
|
|
|
wizkid057 (OP)
Legendary
Offline
Activity: 1223
Merit: 1006
|
|
August 28, 2014, 02:08:46 PM |
|
I seem to have discovered the issue, and it seems it could be a possible bug.
What seems to have happened: I changed my minimum payout threshold to 0.015 BTC, after the balance had already reached a point higher than that. As such, it didn't seem to "trigger' the payout as the threshold had been bumped lower than the current BTC balance. Once I changed the threshold to something higher than the BTC balance on eligius, once it reached that amount it successfully "triggered" the payout into the queue system.
So, it would appear changing the minumun threshold for payout "jumped" over the trigger, and resetting to an amount yet to be attained it successfully triggered when hitting that point.
The My Eligius options do not take effect immediately, as is written on the options page. In the case of dropping your minimum payout below your balance in an effort to trigger a payout... I purposely deprioritize such changes for an addtional amount of time (in the code). Eligius is not a bank. Eligius does not have any manual withdraw feature for many reasons, mostly security related. I do not want people abusing the My Eligius settings regularly to that effect, hence the delay in such a change taking effect being an effort to curb such behavior.
|
|
|
|
mdude77
Legendary
Offline
Activity: 1540
Merit: 1001
|
|
August 28, 2014, 10:25:23 PM |
|
I seem to have discovered the issue, and it seems it could be a possible bug.
What seems to have happened: I changed my minimum payout threshold to 0.015 BTC, after the balance had already reached a point higher than that. As such, it didn't seem to "trigger' the payout as the threshold had been bumped lower than the current BTC balance. Once I changed the threshold to something higher than the BTC balance on eligius, once it reached that amount it successfully "triggered" the payout into the queue system.
So, it would appear changing the minumun threshold for payout "jumped" over the trigger, and resetting to an amount yet to be attained it successfully triggered when hitting that point.
The My Eligius options do not take effect immediately, as is written on the options page. How long does it take? I'm at 24 hours since I changed it, still not showing up in payout queue. M
|
I mine at Kano's Pool because it pays the best and is completely transparent! Come join me!
|
|
|
wizkid057 (OP)
Legendary
Offline
Activity: 1223
Merit: 1006
|
|
August 28, 2014, 11:07:14 PM |
|
I seem to have discovered the issue, and it seems it could be a possible bug.
What seems to have happened: I changed my minimum payout threshold to 0.015 BTC, after the balance had already reached a point higher than that. As such, it didn't seem to "trigger' the payout as the threshold had been bumped lower than the current BTC balance. Once I changed the threshold to something higher than the BTC balance on eligius, once it reached that amount it successfully "triggered" the payout into the queue system.
So, it would appear changing the minumun threshold for payout "jumped" over the trigger, and resetting to an amount yet to be attained it successfully triggered when hitting that point.
The My Eligius options do not take effect immediately, as is written on the options page. How long does it take? I'm at 24 hours since I changed it, still not showing up in payout queue. M If you set a minimum below your current balance? I'm not going to disclose the exact timing on that... Otherwise they generally take effect within 24 hours.
|
|
|
|
|
wizkid057 (OP)
Legendary
Offline
Activity: 1223
Merit: 1006
|
|
August 29, 2014, 01:19:21 AM |
|
As always, blockchain.info confusing people. That was a payout in an orphaned block. You were re-paid in the next valid block in txn 4c00d76aa21c52dc2636a4006f4a8671134dd564b63637c550681e24b50ad82a
|
|
|
|
|