This topic contains 8 replies, has 1 voice, and was last updated by Daved Daly 1 year, 2 months ago.
January 7, 2018 at 4:10 pm #5270
While the self miner is generally of low impact, I feel that the miner should stop hashing whena vald hash is found, until the next block notification.
Seems weird we are submitting hashes which won’t count for anything extra.January 7, 2018 at 9:33 pm #5278
Agree with that, actually it would be even better to request a new JSE data when a hash is submitted 😉January 8, 2018 at 12:42 am #5280
Requesting a new “jse data” doesn’t make any sense to me.
The block wouldn’t have changed. you’d be requesting the same data.
Self mining you only earn one lotto ticket max per block. (something I think which is way too low. But the self mining sees like an afterthought, and not intended to provide much rewards. But then the whole reward system, website miners, seems low as well.)January 9, 2018 at 5:10 am #5287
well then how about… those who submit more hashes get more lotto tickets? increasing their chances of being picked for the payout… basically right now (as I understand it) if we have 1500 miners going.. and all 1500 find a hash.. all have a chance to get the payout (up to 200 people)
but let’s say… I find 10 hashes in that 30 second block and other miners find 3… then my chances of getting the reward should be higher.. .not that I will get it every time, but it should be higher than someone who only mined 1.
That would be fair right? otherwise we are technically hashing for free after 1January 9, 2018 at 11:40 am #5288
No. if all accounts are logged in to the same username, self mining gets you one lotto ticket per block.
If your signed into multiple accounts, you will probably be banned.
Yes, we are hashing for free after one lotto ticket per block.
This is because it’s technically possible to tie in a fpga or asic and win 99.99% of the lotto tickets, without a 1 ticket per block limit.January 9, 2018 at 11:47 am #5289
I think I misread what you meant, but the reason for the limitation hold.
You would think if you find more hashes per block should get you more tickets per block, but for keeping everything fair it’s limited.
Thus my suggestion to stop hashing till the next block when you find a valid hash.January 9, 2018 at 7:27 pm #5295
just saying, the more hashes I find in that 30 seconds, should increase my chances of my lotto ticket being called.
If another of my tickets is called again, the system checks to see if i’ve already been paid and refuses the second ticket and moves onto the next.January 9, 2018 at 7:31 pm #5296
not sure if i am explaining it well so forgive me if I sound redundant..
say i mine and find 5 hashes per block. as it stands, I get one ticket… I should get 5.
when the system does its payout operation, I should have 5 tickets in the hat. If my name is pulled, I get my .005 JSE. the next ticket is pulled… if it is my ticket again, the system destroys that ticket and throws it away, and pulls the next ticket.
overall I still only get one payout, but my name will be in the hat more than just one time.January 10, 2018 at 10:42 am #5300
As stated directly in the whitepaper, (you did read that right?)
powered hashing hardware and return a better hash every time. The algorithm for
rewarding webmasters will focus on impressions as well as hashing. Automated checks
are run hourly to remove any statistically improbable mining. Manual reviews are also in
place to prevent fraud attempts.
Again, what I described is clearly possible… they just use some fairly undisclosed, centralized anti-fraud prevention in place… as well the one ticket per block makes hooking up hashing hardware not worthwhile.
And I’m still not sure what people think about the original proposal…
Regardless of how some think it should work (more valid hashes per bloc gets you more tickets), it does not work that way… and the reasoning is clear… to make it useless to cheat.