Pages:
Author

Topic: Eligius: 0% Fee BTC, 105% PPS NMC, No registration, CPPSRB - page 60. (Read 1061417 times)

full member
Activity: 223
Merit: 132
Hi, I need help mining a transaction:
Code:
010000000147ce0e81fac45653e8f82b4edfb2873c83fc95ee67219a0b2c9a7f9a0020a0c5000000008b48304502205814f0c588383a38c00b7f9d2317f2aeb2649e60dd341e603b22ae79f334f83c02210094a35f42d1c9f32ea700e66354ecd457ab2bcf0247865cb037be886569a5ac7f014104227f4a6de87d345dc08601920c1ab8b9bf4a76868e053f5f90faf307bcf0d72b014be36394a1f8a98bd8f2e5bb2243464fa67eee14e5cfc0888d7f15b7b2a1100c0000000264d31300000000001976a914a90cf97578df33b7d261105f3ba7b7297fd3f77d88ac00000000000000001976a9149f27c31c0bf89cb4958e7fc99c0f9117623b4e4b88ac44a70500
it is non-standard but it has a txfee.
I tried to send it using this page: http://eligius.st/~wizkid057/newstats/pushtxn.php but it doesn't work (it says "Response = 0")
More details on this thread: https://bitcointalksearch.org/topic/m.12188059
Is it possible in some ways to get this tx mined on Eligius?

Quote
bitcoin-cli decoderawtransaction 010000000147ce0e81fac45653e8f82b4edfb2873c83fc95ee67219a0b2c9a7f9a0020a0c500000 0008b48304502205814f0c588383a38c00b7f9d2317f2aeb2649e60dd341e603b22ae79f334f83c 02210094a35f42d1c9f32ea700e66354ecd457ab2bcf0247865cb037be886569a5ac7f014104227 f4a6de87d345dc08601920c1ab8b9bf4a76868e053f5f90faf307bcf0d72b014be36394a1f8a98b d8f2e5bb2243464fa67eee14e5cfc0888d7f15b7b2a1100c0000000264d31300000000001976a91 4a90cf97578df33b7d261105f3ba7b7297fd3f77d88ac00000000000000001976a9149f27c31c0b f89cb4958e7fc99c0f9117623b4e4b88ac44a70500
{
    "txid" : "bc23946a4335370962015d7947e37717568852a83f4b1721ee2a8eed499914a4",
    "version" : 1,
    "locktime" : 370500,
    "vin" : [
        {
            "txid" : "c5a020009a7f9a2c0b9a2167ee95fc833c87b2df4e2bf8e85356c4fa810ece47",
            "vout" : 0,
            "scriptSig" : {
                "asm" : "304502205814f0c588383a38c00b7f9d2317f2aeb2649e60dd341e603b22ae79f334f83c0221009 4a35f42d1c9f32ea700e66354ecd457ab2bcf0247865cb037be886569a5ac7f01 04227f4a6de87d345dc08601920c1ab8b9bf4a76868e053f5f90faf307bcf0d72b014be36394a1f 8a98bd8f2e5bb2243464fa67eee14e5cfc0888d7f15b7b2a110",
                "hex" : "48304502205814f0c588383a38c00b7f9d2317f2aeb2649e60dd341e603b22ae79f334f83c02210 094a35f42d1c9f32ea700e66354ecd457ab2bcf0247865cb037be886569a5ac7f014104227f4a6d e87d345dc08601920c1ab8b9bf4a76868e053f5f90faf307bcf0d72b014be36394a1f8a98bd8f2e 5bb2243464fa67eee14e5cfc0888d7f15b7b2a110"
            },
            "sequence" : 12
        }
    ],
    "vout" : [
        {
            "value" : 0.01299300,
            "n" : 0,
            "scriptPubKey" : {
                "asm" : "OP_DUP OP_HASH160 a90cf97578df33b7d261105f3ba7b7297fd3f77d OP_EQUALVERIFY OP_CHECKSIG",
                "hex" : "76a914a90cf97578df33b7d261105f3ba7b7297fd3f77d88ac",
                "reqSigs" : 1,
                "type" : "pubkeyhash",
                "addresses" : [
                    "1GQrjuC59UuDv3LqbhPHX5mREDY4521f12"
                ]
            }
        },
        {
            "value" : 0.00000000,
            "n" : 1,
            "scriptPubKey" : {
                "asm" : "OP_DUP OP_HASH160 9f27c31c0bf89cb4958e7fc99c0f9117623b4e4b OP_EQUALVERIFY OP_CHECKSIG",
                "hex" : "76a9149f27c31c0bf89cb4958e7fc99c0f9117623b4e4b88ac",
                "reqSigs" : 1,
                "type" : "pubkeyhash",
                "addresses" : [
                    "1FWY5DxbgVSBbCwCDMwsgSPUCKQKWfjYWa"
                ]
            }
        }
    ]
}
bitcoin-cli sendrawtransaction 010000000147ce0e81fac45653e8f82b4edfb2873c83fc95ee67219a0b2c9a7f9a0020a0c500000 0008b48304502205814f0c588383a38c00b7f9d2317f2aeb2649e60dd341e603b22ae79f334f83c 02210094a35f42d1c9f32ea700e66354ecd457ab2bcf0247865cb037be886569a5ac7f014104227 f4a6de87d345dc08601920c1ab8b9bf4a76868e053f5f90faf307bcf0d72b014be36394a1f8a98b d8f2e5bb2243464fa67eee14e5cfc0888d7f15b7b2a1100c0000000264d31300000000001976a91 4a90cf97578df33b7d261105f3ba7b7297fd3f77d88ac00000000000000001976a9149f27c31c0b f89cb4958e7fc99c0f9117623b4e4b88ac44a70500
error: {"code":-26,"message":"64: dust"}


Zero value output.  Would eligius even mine this?
sr. member
Activity: 448
Merit: 250
Craig Wright is scammer.
Hi, I need help mining a transaction:
Code:
010000000147ce0e81fac45653e8f82b4edfb2873c83fc95ee67219a0b2c9a7f9a0020a0c5000000008b48304502205814f0c588383a38c00b7f9d2317f2aeb2649e60dd341e603b22ae79f334f83c02210094a35f42d1c9f32ea700e66354ecd457ab2bcf0247865cb037be886569a5ac7f014104227f4a6de87d345dc08601920c1ab8b9bf4a76868e053f5f90faf307bcf0d72b014be36394a1f8a98bd8f2e5bb2243464fa67eee14e5cfc0888d7f15b7b2a1100c0000000264d31300000000001976a914a90cf97578df33b7d261105f3ba7b7297fd3f77d88ac00000000000000001976a9149f27c31c0bf89cb4958e7fc99c0f9117623b4e4b88ac44a70500
it is non-standard but it has a txfee.
I tried to send it using this page: http://eligius.st/~wizkid057/newstats/pushtxn.php but it doesn't work (it says "Response = 0")
More details on this thread: https://bitcointalksearch.org/topic/m.12188059
Is it possible in some ways to get this tx mined on Eligius?
legendary
Activity: 1223
Merit: 1006
Webserver was hanging hard when I checked on it.  Investigating possible causes.

No worries, mining has been fine.  As always the webserver and mining servers are separate, so mining can always continue if there are webserver issues.

-wk
legendary
Activity: 1274
Merit: 1000
Is the site down?



Seems so


I'm mining Smiley by the proxy I have  my miners running thu .
newbie
Activity: 4
Merit: 0
Looks like the site is down yes i cant enter it aswell.
sr. member
Activity: 318
Merit: 250
Is the site down?
legendary
Activity: 1223
Merit: 1006

~200 BTC in funds awaiting complex code patches to utilize funds held from a blockwitholder for distribution to the share log of that time period for miners affected


Is that from last year or was there another one?
I have not been paying attention here for a while.

-Dave

Nothing new, it's from last year.  Based on some legal advice it was determined best to not immediately do anything with those funds.  I am, however, working on the code to do so.  When it's ready they will be distributed (paid to shelved shares in the share log accumulated at the time of the withholding attack).  At this point that probably will mean some small payouts to some miners who were active at that time.  Hopefully most still are active, anyway.
legendary
Activity: 3500
Merit: 6320
Crypto Swap Exchange

~200 BTC in funds awaiting complex code patches to utilize funds held from a blockwitholder for distribution to the share log of that time period for miners affected


Is that from last year or was there another one?
I have not been paying attention here for a while.

-Dave
legendary
Activity: 1652
Merit: 1001
Don't look at my signature!
I've always held this pool in very high regard, and continue to do so.
As someone who used to mine with you some years ago (back when I had BTC mining equipment), you have never appeared to veer from being honest, efficient, and having integrity.
I hope you guys manage to stay around for as long as possible to highlight how crypto can be done.
legendary
Activity: 1223
Merit: 1006
"Bitcoin XT" is not bitcoin, it's an altcoin... and I don't support scamcoins, so no, you won't find support for it here.

I disagree with your conclusion, if not your decision. It's a variant client, and an attempt at forcing consensus (which will succeed, but probably not in the way Gavin et. al. were hoping). I think it's mainly a tempest in a teapot.

However, it does shine some light on problems that do exist in the current implementation of the reference client. The 1MB limit WILL limit adoption. So does the 10 minute block time. BTC paved the way, but the way I see it, almost every altcoin is technically superiour. First mover advantage does not last forever, and frankly, the Bitcoin Foundation seems more interested in hookers and blow than in improving Bitcoin.

That being said, XT was exactly the wrong approach. It was a demand, whereas consensus requires a request. I agree that it will fail.

Consensus on something like this isn't just 75% of miners, really.  The ramifications of this altcoin (and yes, it is an altcoin at this point) trying to be bitcoin, especially if somehow it managed to succeed would be huge and in my opinion the method of doing so would completely undermine the very nature of bitcoin itself.

It is an altcoin because it is not something that even remotely has bitcoin community consensus as something that should move forward.  It's an attempt to undermine the way such changes are to be implemented.  It defines rules that are not bitcoin.  Just because it's playing by the rules now doesn't mean that it is bitcoin.  It is an altcoin just the same as if someone forked the bitcoin code with a version that changed the block reward back to 50 BTC after some point.  It would not be bitcoin.

A hard fork like this should be hard to do.  75% miner consensus means that transactions sent would need tens of confirmations before you could be reasonably certain that they were confirmed on the correct blockchain.  In reality a hard fork should have so much support that it goes smoothly at a predefined time in the distant future once everyone has been given significant information on the matter and time to adopt it.

In any case, Eligius will not be mining "Bitcoin XT."  I'd prefer not to clutter this thread with discussions about this, also.
legendary
Activity: 1372
Merit: 1022
Anarchy is not chaos.
"Bitcoin XT" is not bitcoin, it's an altcoin... and I don't support scamcoins, so no, you won't find support for it here.

I disagree with your conclusion, if not your decision. It's a variant client, and an attempt at forcing consensus (which will succeed, but probably not in the way Gavin et. al. were hoping). I think it's mainly a tempest in a teapot.

However, it does shine some light on problems that do exist in the current implementation of the reference client. The 1MB limit WILL limit adoption. So does the 10 minute block time. BTC paved the way, but the way I see it, almost every altcoin is technically superiour. First mover advantage does not last forever, and frankly, the Bitcoin Foundation seems more interested in hookers and blow than in improving Bitcoin.

That being said, XT was exactly the wrong approach. It was a demand, whereas consensus requires a request. I agree that it will fail.
legendary
Activity: 1223
Merit: 1006
"Bitcoin XT" is not bitcoin, it's an altcoin... and I don't support scamcoins, so no, you won't find support for it here.
legendary
Activity: 1078
Merit: 1024
Wow, I just noticed that the last block (0000000000000000a7d0521b7fe409c823c9cf00a964a99c59e57fa3b4d8dfc2) was one of the luckiest in pool history at 30sec... there have been a couple of those in the last few weeks. Could the increase in the asics now in circulation have anything to do with this or is it overall pool hashrate or the increased number of miners? Or is it just my noob (not very in-depth) view of the stats?

It is quite simply just luck, which varies greatly in either direction.  The fastest block ever for Eligius was block 277,885 ... which was mined 3 seconds after 277,884. Wink

-wk
Yeah I noticed that and that block was mined on: 2013-12-31 09:01:22. Almost all of the "quickest" blocks from that one to the one just now were mined in the last 4 months or so... since the rise of the asics... it could also just be pure luck...

At this point it's just extreme variance.
sr. member
Activity: 461
Merit: 250
Yup eligius is best pool by far. Bitcoin XT? What is that?
No we will not have two version of coins/chains, at least not until first >1MB block is found and supermajority is not achieved.
Keep up the good work wiz!
hero member
Activity: 812
Merit: 1000
eligius is the best pool out there. Good job guys and thank you.
just a question, what is your opinion about BTC XT? are you going to support it in the pool?
i guess we are going to 2 different BTC coins!
legendary
Activity: 1223
Merit: 1006
Can anyone explain this? In the image below, at the point the arrow is indicating, a block was found. Yet I was awarded practically nothing. The "estimated change" was indeed almost zero, actually negative for some time, for the whole duration of the round. Why? As you can see from the image, my hashrate was normal. It's not because it was hitting the maximum reward either, my current total earnings are more than half a BTC under that, with a total luck of 95.85%. I see no reason why I should not be rewarded for that round..

Just a stats artifact due to the stale block around that time.  The graph left the unpaid portion at the level it would have been if the stale block were valid (~17:00), then an actual block was found around the time of your arrow and the graph corrected.  You'll notice the estimated earnings (blue) are always above the unpaid earnings (purple) except in this instance due to the stale block.  Then when the valid block was found shortly after the estimated earnings appeared again.  Basically just a graph issue in how the unpaid portion is calculated in the case of a stale block.  In reality the increase in unpaid (purple) should be shifted from ~17:00 to where you have your arrow pointing.
hero member
Activity: 536
Merit: 500
Can anyone explain this? In the image below, at the point the arrow is indicating, a block was found. Yet I was awarded practically nothing. The "estimated change" was indeed almost zero, actually negative for some time, for the whole duration of the round. Why? As you can see from the image, my hashrate was normal. It's not because it was hitting the maximum reward either, my current total earnings are more than half a BTC under that, with a total luck of 95.85%. I see no reason why I should not be rewarded for that round..

legendary
Activity: 1223
Merit: 1006
>440 BTC some dating back at least 100 days hasn't been distributed ... so why isn't that a bad thing?

Here I am feeding the trolls...

I've explained exactly why everything is as it is, but you don't care to listen.  But what the heck, I'll do a quick rundown again even more since you're not going to pull the numbers from public data yourself.

~100 BTC in funds for miners who have not yet reached the default or custom set payout thresholds.
~200 BTC in funds awaiting complex code patches to utilize funds held from a blockwitholder for distribution to the share log of that time period for miners affected
~160 BTC in funds for a payout queue backlog caused by a total of 6 failsafe blocks (out of over 300) that requires a cold wallet manual payout that I haven't had a chance to do yet

Around 5% of the bitcoin network (more like 20%-25% of actual miners when you don't count Chinese hardware manufacturers and the like) understands perfectly and sees through your nonsense.

I think I'm done taking troll bait here.  Obviously you have no idea how the reward system works, don't actually care, and are just doing your normal anti-Eligius trolling due to whatever grudge you have against Luke that somehow I fell into when I took over Eligius.... NEARLY THREE YEARS AGO.  Whatever it is, get over the f*** over it and stop this crap.  I'm seriously tired of wasting time with your BS.  It's completely ridiculous.  Find something better to do.  Get a real hobby.  A girlfriend or something, I really don't know.  But leave me the hell alone.

For a moment there I thought you had put whatever nonsense that was fueling your trolling here behind you because I actually saw a few posts here in recent history that were, much to my surprise, actually helpful and informative.

But, seriously, I'm f***ing done.  I'm not wasting my time anymore if you're going to just keep trying to spread FUD and general misinformation constantly. I'm just going to go back to my original policy of just immediately removing your posts from this thread and save the effort.



Edit/Update:  The posts I quoted from kano in this post and the post before it seems to have disappeared.  I did not remove them.
legendary
Activity: 1223
Merit: 1006
legendary
Activity: 1223
Merit: 1006
Note also regarding quoted comments, transaction fees are not always distributed here.

Source?  I do run the pool, and I'm pretty sure this always happens...

For fun, here is some debug output from the reward system for a random block still in my scroll back:

Quote
*** NEW POOL BLOCK @ SHARE ID 404061979740
Solution HEX: 00000003d659d850c9a9976b098074a20c9e300ab462060e04fd37b500000000000000003ee6720 a0cbfbd7135a848d23f431646e1673bd96aea2c59e935372cacb6e80e55d1eaf51814dd0459236b 07
SHA256: 00000000000000000c73f7e21f3f0590715a1e478a1b6a72a15317e8889f7321
Block Height: 370261
Base Block Reward: 2500000000 reward + 40 pool funds
Added 0.01670971 BTC in transaction fees to reward funds for a total of 25.01671011 BTC reward funds
Rewards added to miner balances: 25.01670978 BTC
Pool reward funds updated from 25.01671011 to 0.00000033 BTC

The dust leftover in pool funds is the consequence of only one satoshi resolution possible on rewards once a block is found and is just leftover and added to the next block's reward to make up the difference, as well as the next share down in the share log (new or shelved) potentially being too large to pay this round with available funds.  Internal resolution for share values in the share log is better than 1 satoshi, but when they're actually made into a balance it has to be rounded down to the nearest satoshi since it's impossible to pay out partial satoshis and it is also impossible to pay out more than the pool receives.  Additionally the rounded down portion of any shares is left as a share in the share log to be added to a future block's rewards, so the rounded down portion isn't just forgotten, either.
Pages:
Jump to: