 Show Posts
|
|
Pages: [1] 2 3 4 5 »
|
I would recommend you to continue with the project only if you seriously want to do it in the future and have the time and can financially afford it. You will have a hard time attracting interested parties to your pool. However I truly wish you best of luck and success.
I need to work first. Cannot play and need some more time to do something absolutely wonderful. I will take every inch of what you noticed and try to improve. Thank you. |
|
|
|
|
Cannot afford the hosting this month. I'm sorry for that. I must choose between eat or provide this service.
And there is no hashrate at all.
For the bug = made a regression 1 week ago when I implemented the maxDiff and maxDiff Ever (user manager process) and I don't have enough time to take a look.
Will make some changes in the future.
|
|
|
|
Stay connected, don't go to shady solo pools, here you can verify the jobs I send, it's fair enough better
I tried to verify the payout amounts and addresses that you configured on your pool. I am using cgminer in its latest version. Unfortunately it failed completely with your pool. With eg. cgminer you can easily check what happens in case of a block found by querying the pool and see the coinbase transaction it returns. Here's an example with solo.ckpool.org with a correct and expected output: Pool stratum+tcp://solo.ckpool.org:3333:
{
"result": {
"txid": "497ee53104c2840e3ac3bd41d534711a243537de8d7ee6bbe853f4dcc1390cb8",
"hash": "497ee53104c2840e3ac3bd41d534711a243537de8d7ee6bbe853f4dcc1390cb8",
"version": 1,
"size": 219,
"vsize": 219,
"weight": 876,
"locktime": 0,
"vin": [
{
"coinbase": "03c29a0b0004995d5a6304a598bc0e0c890a198600000000000000000a636b706f6f6c112f736f6c6f2e636b706f6f6c2e6f72672f",
"sequence": 4294967295
}
],
"vout": [
{
"value": 6.1784937700000002,
"n": 0,
"scriptPubKey": {
"asm": "OP_DUP OP_HASH160 06040de94c96094d379a25427510d4c3d83fd7aa OP_EQUALVERIFY OP_CHECKSIG",
"desc": "addr(1YourPayoutAddressxxxxxxxxxteJhsz)#3wcn68cg",
"hex": "76a91406040de94c96094d379a25427510d4c3d83fd7aa88ac",
"address": "1YourPayoutAddressxxxxxxxxxteJhsz",
"type": "pubkeyhash"
}
},
{
"value": 0.1260917,
"n": 1,
"scriptPubKey": {
"asm": "OP_DUP OP_HASH160 f4cbe6c6bb3a8535c963169c22963d3a20e76869 OP_EQUALVERIFY OP_CHECKSIG",
"desc": "addr(1PKN98VN2z5gwSGZvGKS2bj8aADZBkyhkZ)#5rs4qewl",
"hex": "76a914f4cbe6c6bb3a8535c963169c22963d3a20e7686988ac",
"address": "1PKN98VN2z5gwSGZvGKS2bj8aADZBkyhkZ",
"type": "pubkeyhash"
}
},
{
"value": 0.0,
"n": 2,
"scriptPubKey": {
"asm": "OP_RETURN aa21a9ed8d6dcf633056c61acab3dded8cd2e93b5547fbb23e3d9cf8b40bfcafe8364c92",
"desc": "raw(6a24aa21a9ed8d6dcf633056c61acab3dded8cd2e93b5547fbb23e3d9cf8b40bfcafe8364c92)#ks50402f",
"hex": "6a24aa21a9ed8d6dcf633056c61acab3dded8cd2e93b5547fbb23e3d9cf8b40bfcafe8364c92",
"type": "nulldata"
}
}
]
},
"error": null,
"id": 0
}
as we see, 2% fee (here 0.1260917 BTC) goes to 1PKN98VN2z5gwSGZvGKS2bj8aADZBkyhkZ (owned by the pool operator) just as promised and promoted on his pool site. The reward of 6.1784937700000002 BTC in that example would go to users payout address. Unfortunately and as not expected, the query does not work at all on your pool as it fails in the beginning with the error: Failed json_rpc_call
For me it looks like that your pool spits out some json incompatible data, with which the mining software cgminer or the bitcoin core linked to it cannot process. Just guessing though. However, the query works against all other known pools available out there without issues, just your pool returns nothing but that error. I personally would avoid your pool under these circumstances, because it means for me: if my miner would find a block then I can't trust that I would get paid. Not to mention that the miner would have problems with the call at all because he can't seem to communicate properly. Can you provide more info on why well-known and widely used mining software such as the latest version of cgminer used here spits out a false check? Strange. Have you tried my method ? I tested the pool with CPUMINER, Antminer, Whatsminer, but not CGMiner tested with 250 Ghs. What command do you use ? Edit : --decode. I'm building CGMiner for osx right now Edit 2 : Got an old version for macOs that doesn't support -decode. I've ping a friend to decode it and try on my side. Will take a look. |
|
|
|
Answer has been made in pm : this functionnality is currently being made (implemented on the pool side, not tested yet, api not implemented, and frontend not implemented). Not necessary for proof of work, mining software have this data. But for a pleasing experience will add it when I will have time to implement it. I work for free. If they need functionnality, they can grant. And you have less than 100 Ths so it's not in my priority order, currently, in this bear market cycle. If my contribution to a better decentralisation and fair job providing doesn't please you, you can Switch to shitty solo pools.
Edit : answer done in the thread and by pm where you haven't responded to my message (where I was asking WHAT EXACT information you needed (bestShare ever or also bestshare per block), I'm sorry if you didn't understood me with my poor english skills)
you should stop spreading lies, you are not making your entry into the pool business any easier. I had answered you by DM Seriously? Sorry dude, but if you try to run a solo pool and ask such questions I'm curious if you know what you're doing. By this you cannot earn reputation and trust. I'm out, I will stick with another solo pool that has been around for long time and they know how stuff work. Sorry man. However thanks for the contact and best wishes to you and your side project. What is the difference between the bestshare and bestever ?
A few suggestions from my side that might help you: - stop bitching about other pools or people. Leave bashing to others who are good at it and have been doing it forever (e.g. Kano). By deliberately and maliciously badmouthing others, you do not make yourself better. Also the community doesn't care if you're coding in your free time or not, there are far more important things in this bussiness. - include "bestshare" and "bestever" information into your statistics - implement more servers spread over all continents (one server is not enough and would be a single point of failure) - blaming others or slipping into the victim role will not help you, but will have the opposite effect - add your instructions for checking the coinbase transaction to your website. You've already put a lot of effort into this great guide and you're the first, so that's a big plus for you. Work this out further in detail step-by-step (for command line) so that potential users will be motivated to check it themselves. - think about how you could advertise with a sponsoring program or something similar to get some first users to mine your pool. I'm optimistic on you, you have potential, you just have to play your cards right first. Don't let it get you down and go for it. I wish you every success with your project. Every beginning is hard and only the tough ones cross the finish line. Kindness is more sexy than telling me via PM I don't understand what I do by not understanding your exact request (in english by the way, sorry that I don't speak well this langage) I really don't bitch, I tell only what I think about mining and tries to improve it, and what I think about it right now. And tired to see that really nobody gives a f; It's highly concentrated, nobody verifies jobs, nobody verifies earnings, PPLNS and scoring is shady as F. Now it's a chance for miners to stop going on shitty highly centralized pools. It's purely pro bono at 0.4% Thanks for your constructive message, really appreciate it and will consider every single point. |
|
|
|
Every new pool will add in for decentralization, so that is to be appreciated. However, also anyone can decode the coinbase data regardless of the (solo) pool, since that data is exchanged via stratum. So there always was a way to verify what address is being rewarded with what amount (if the respective block wins) - and since the block hash is based on that input data, any tampering with the data will result in another hash value that won't meet the target difficulty.
Assuming on block level all is fine, you still have to always trust the pool operator to be fully operational, with up-to-date blockchain and capable to get your winning block out to the network as fast as possible. There are known and proven solo pools out there already, so as a new solo pool operator it will be hard to find trust and acceptance. In fact you can only earn trust with the count of solved blocks.
Node height is available and instantly broadcasted through API and stratum. https://soloblocks.io/api/serversNo solved blocks if no trust. Fixed the trust. No hashrate. No blocks xD. Thinking about closing the pool rn as nobody wants it and the large amount of defiance i've seen even if i'm in Bitcoin since 13 years. Baremetal servers cost a lot for absolutely no reason. Mining is highly centralized right now. I've got dual node failover on the mining pool, 32 Gb RAM and NVMe hard drives, stability is awesome at 0.5 Exahash on 1 pool at these difficulties. I provide Full API, notably server health via https://soloblocks.io/api/serversMost hash farms I know are unable to face the variance... Discouraged by all of these and working had to address them still. Don't know what to do. |
|
|
|
This is months ago now, can we see some results? Currently I am trying soloblocks.io and in my dashboard I see nothing related to bestshare and bestever for my mining work. The whole solo mining is useless for me without these stats. Can you shed some light into, please?
thank you.
Not yet. Working on the pool on my free time. Already implemented a provably fair job broadcasting, that had never been done in 13 years. Don't have enough free time these days for these cosmetic UI improvements such as bestShare in current block and bestShare ever, for just 10 Ths ! Give me time, I'm working a lot today to face the bear market and don't have time on my schedule for these tiny UI changes but will take some time around this month, sorry for that. Stay connected, don't go to shady solo pools, here you can verify the jobs I send, it's fair enough better |
|
|
|
I'm planning to add the maxDiff on current block and maxDiff ever on informations on the Dashboard. You can verify it by yourself with your mining software as they calculate the shareDiff. Sorry for this specific response but I've worked hard to address these issues and the work is done and online and I still have ZERO miners on the pool since 1 year.  yes what now? Are you still planning or is the work done ? You should also watch your own support thread about the pool and give some helpful answers to questions like this. Answer has been made in pm : this functionnality is currently being made (implemented on the pool side, not tested yet, api not implemented, and frontend not implemented). Not necessary for proof of work, mining software have this data. But for a pleasing experience will add it when I will have time to implement it. I work for free. If they need functionnality, they can grant. And you have less than 100 Ths so it's not in my priority order, currently, in this bear market cycle. If my contribution to a better decentralisation and fair job providing doesn't please you, you can Switch to shitty solo pools. Edit : answer done in the thread and by pm where you haven't responded to my message (where I was asking WHAT EXACT information you needed (bestShare ever or also bestshare per block), I'm sorry if you didn't understood me with my poor english skills) |
|
|
|
You can go this site to find out last block details https://explorer.btc.com/btc/blocksThen, check your block header data detail. previous hash and nbits must be the same as last block header detail. ntime can be in 10 minutes varies. merkleroot won't be same. Different pool got different merkleroot, ntime, version. Different pools always got and hash different data of block header. except your pool is a sub-pool. I think you didn't understand the issue I fixed, sorry. |
|
|
|
Excuse me, I manage Soloblocks.io mining pool and have some answers.
Yes. solo pool operators can manipulation of your submits and rippe off you at current start of the art in software of the pool side, eg:
1. Pool can submit your found in a different bitcoin address to the bitcoin network. Because the pool got the coinbase data. This is quite wide practice in altercoin pools in terms of my watching. Some pool operators are gangs and untracable, even by Agents.
Pool cannot submit your found block in a different bitcoin address and I've made a methodology to verify it. It works only on soloblocks.io and you can try it on your own. It was a problem until 2022 and I solved it on my solo pool. Topic about it : https://bitcointalk.org/index.php?topic=5397166.msg60503248#msg605032482. Current miner softwares only got a message indicates the pool accepted this submit. But it does not provide information whether this submit has beem submit to the bitcoin network? or whether bitcoin network has accepted this submit? or confirmed this submit? This is an issue which give the pool operators a back door, I believe. The altercoin pools and miner programs even got worst, they don't provide the height information of block. You never know your submits are accepted by the network or not. They got webpage only indicate few second ago you did submit a share.
Most of shares you submit on solo pools are useless as they don't match network difficulty. The only share that is sent to the network is the share that matches the difficulty and it is manifested by a winning block on the bitcoin blockchain. On soloblocks you can see current realtime height of current job. 3. After you submit your found to the pool, the pool firstly verify your submit with pool's share difficulty and then pool verify your submit with bitcoin network's difficulty. But, the pool never return a feedback information whether your submit is above the network's difficulty. This can be done easily in software, and this is a key issue in transparency of bitcoin network. Actually, the bitcoin core will return a message "under diff, sth like" if submit is below the diff.
So, there is a real risk in crypto coin mining business. When you ran a miner for one year, and got a good submit, then, ripped off or missed.
What can you do? You have to work with reliable pool operator at first place.
I'm planning to add the maxDiff on current block and maxDiff ever on informations on the Dashboard. You can verify it by yourself with your mining software as they calculate the shareDiff. Sorry for this specific response but I've worked hard to address these issues and the work is done and online and I still have ZERO miners on the pool since 1 year. |
|
|
|
Pourquoi on choisirait d'avoir un intermédiaire avec Nicehash ? Tu t'adresses aux personnes pour qui c'est trop nébuleux la location de hashrate ?
Calculs a prendre avec des pincettes, la difficulté bouge, les prix sur Nicehash également
C'est mieux de miner directement avec nicehash, je propose ça pour ceux qui n'y connaissent rien  Oui les calculs sont approximatifs, je me base sur le fait que le prix de nicehash corresponds à 100% de la rentabilité. Un bloc à 6.25 => 1 chance sur 6250 à 0.001 BTC à 100% de la rentabilité. ça peut être légèrement plus ou légèrement moins. |
|
|
|
As I recall it has to do with making sure the code properly handles numbers that are over what 32-bit can natively use.
Hello. I use Big Rat (golang) from Header Hash to get the difficulty of the share. It can handle huge numbers for difficulty to compare shareDiff and networkDiff. I don't use int64 or int32. 1) That means all math calculations using that in go are exceptionally slow compared to the c-library 2) While this may give you digital accuracy to whatever level you require, it wont be infinite, so there must be some default setting you should check. Bitcoin numbers are ridiculously large compared to most other things done in the world, so you better ensure the default setting is big enough. e.g. a 256 bit number can count roughly 1/1000th of all the atoms in the entire universe. When I start my current version of KDB I get it to do decimal place accuracy calculations on current difficulty vs expected answers, to verify there is always enough accuracy I also added coded to cgminer last year (in the public git) to optionally verify the binary you generate can handle 32 to 240 bits of leading zeros on a hash correctly. (the last 16 bits have a value in it for testing) i.e. up to 000000000000000000000000000000000000000000000000000000000000ffff So while you say 'yeah this language will handle it', it is advisable to actually check that yourself rather than just assume it's ok ... 1 - It's an issue with golang yep, I'm looking to reimplement c-library into golang (in fact i wonder if btcsuite has the library) 2 - Going to check if I can change the comparison to a 256 bits number instead. But current max value of big rat is incredibly high 3 - I assume it's ok on current difficulty and for the next 40 years |
|
|
|
As I recall it has to do with making sure the code properly handles numbers that are over what 32-bit can natively use.
Hello. I use Big Rat (golang) from Header Hash to get the difficulty of the share. It can handle huge numbers for difficulty to compare shareDiff and networkDiff. I don't use int64 or int32. |
|
|
|
Hello
I would like to say thanks for what you are doing, and bravo as I read that you did your own code. Quite impressive to me.
Anyway, with all the due respect, I won't point my hashrate personally here for now, just because a BTC block represents a life-changing amount in my country (even with the actual BTC rates) I must stay on long-established efficient pools, I think I will probably have 1 block before the end of my life, and cannot imagine lose it because of (for example) a technical issue of pool.
I notice you proved your good faith, and gives us a way to verify that you are not scamming people. Thanks for that, some other pool operators should take it as an example.
I still have some doubts about the part of your pool is able to manage/operate fine when a block is solved. After some blocks confirmed found by your pool, I will definitely jump into it. It is 100% selfish, I know that if every miner is doing the same as me, your pool wouldn't be able to prove that she is working fine, But my personnal hashrate is too small and actually difficulty too high to take the risk. I hate to think like that, but I really don't have the choice now.
Kind of dilemma when we talk about life changing amount.
Thank you, sincerely for what you are doing, I love solo mining principe, and you are contributing to keep it alive. Unfortunately, at a personnal scale I cannot allow myself to risk my chance now, I would love to be enough wealthy to not consider as a tragedy a orphan block, a lost one or everything else you surely know what I mean.
Will keep an eye on your work, and before your pool found a or two blocks, would love to support you financially if you send a BTC address you own, When your pool will prove she handle block correctly, you can count on me and my few ASICs.
If you are able to prove that I am not in the right way thinking like that, I would be really interested to read it and would consider it seriously
Best regards
Hey iwantmyhomepaidwithbtc2. Don't point your hashrate if you are not confident enough. You can point your hashrate for just 15 minutes and plug back on a PPS pool don't worry =), the dashboard will tell you the odds of finding a block in the next 24h  I've found 1 block every few milliseconds on testnet on multiple addresses. It's multi threaded (via goroutines), you can trust the code For the node, It is hosted on a 64Gb Memory, 1.19 Tb NVME and 1 Gibabyte connexion. I've never seen a bitcoin node with so much space available hahaha. > If you are able to prove that I am not in the right way thinking like that, I would be really interested to read it and would consider it seriously I'm not a marketer or a business man, do what your heart tells you to do It's solo mining so consider the payout scheme before plugging in. You asked for the payout address : 3LzaP3iNz5n9mM7edi6eHGyLGY5Yk31SE8 This address is setup in the pool as payout address (you can verify directly in the jobs (step 5 of my tutorial)). I'm from 2009 in Bitcoin and never bought a single Bitcoin, I have no money left from this period (mining gpu in 2011). All I have is euro to pay for this server, so every satoshi counts |
|
|
|
I have proved mathematically that you can trust jobs I send.
Thanks for providing the detail to validate your statements. I have pointed 315TH at your pool. Awesome <3 Thank you for your trust and hashrate. We are going to make one block. Would be good to know the highest share submitted per worker.
Per worker ? Okay. It seems easy to do, i'll publish something as soon as it's done. |
|
|
|
Kano go back to your cave man..
Why you always bashing people on here.. His pool is more anonymous that yours because it dose not require a sign up or email to be given.
Yes the address is on chain but so is everyone's I think what the OP means is no personal info is required to mine with him.
Lol "go back to your cave man", poor Kano (I take the critics and try to improve though). Thx for the additional info. There is no Google tracker, no Personal Info required. I don't need additional info, I've got only IP from miners (for temporary ban in case of ddos on stratum port) and ... pure share processing OP did you per chance get a copy of the "full solo" pool that was released then deleted by CK.
He only posted the full solo code for a short time then deleted it I have a copy if you require it.
I don't have this code at all, I'm sorry for you, and soloblocks did not inspired from CK's code at all. I've manually implemented it from scratch, starting from bitcoin core's getblocktemplate. |
|
|
|
0.4 % fee Anonymous solo bitcoin mining just opened.
Anonymous mining, SOLO mining, Payment in the coinbase, no registration (just enter your bitcoin address)
Um, not sure where you got the false idea your pool is anonymous. e.g. the only extra information required to be provided to my pool is an email address, which is easy to get. (and everyone logged in here had to provide an email address to use bitcointalk ...) However, in your case their BTC address is publically available, and also being transferred back and forward over the internet to the miners every 3 seconds, whereas it isn't on my pool. If miners want a login without email address, they can ping me. If miners don't want to publicly advertise their address, they can change at every mined block.
False advertising isn't really the best way to create trust.
I have proved mathematically that you can trust jobs I send. Read the topic and don't trust solo mining pool that cannot prove that jobs sent are legit and paid to the right person. |
|
|
|
Ok donc si je comprends bien en payant 0.001BTC on a tous les jours 0.016% de chances de trouver un bloc dans la journée. C'est ça? Et ca dure pendant combien de temps? C'est à vie tant qu'on a pas trouvé un bloc? Si oui sais-tu combien de chances on a de trouver un bloc en un an?
En fait la chance est typiquement de 1 chance sur 5700 à 6250 de tomber un block dans les 24h, et le slot réservé est un slot de 24 h de hashrate. Donc 24 h à 220 ths pour 0.001 ₿ Donc 24 h à 440 ths pour 0.002 ₿ Donc 24 h à 660 ths pour 0.003 ₿ etc... C'est l'équivalent d'un ticket d'euromillions, mais au lieu d'avoir une chance sur 691 908 de tirer les 5 numéros + 1 étoile pour 100k de gain avec 10 tickets à 2.5 euros, ici t'as une chance sur 6250 de tomber un 100 k pour 20 euros Je tiens à dire que à chaque instant vous pouvez vérifier mathématiquement que l'ordre est sur la bonne adresse en utilisant nicehash par vous même et en corrélant avec cette méthode d'analyse du GenTX2 : https://bitcointalk.org/index.php?topic=5405106.0Je suis là pour scammer personne Plutôt envie de faire de la pub sur ce système et ma mining pool est la plus légitime de l'écosystème par sa fiabilité, sa transparence et ses frais réduits, besoin de monter le hashrate donc animer un jeu du genre c'est cool. Bien évidemment je peux communiquer un screen de Nicehash et le total payé à Nicehash. Bon à savoir, il y a 63% de chances de tomber un block en dessous de 100% de Luck et 36 au dessus. Puis c'est toujours quelque chose d'avoir ses propres bitcoin minés dans la coinbase, c'est genre un bitcoin propre. Je dis ça, je dis rien. |
|
|
|
Update : pas de block trouvé : 0.044% de Luck
Pourrais-tu être plus précis stp? Ces 0.044% ne correspondent pas aux "1/6,250 chances de taper un block en 24h avec 0.001 ₿" (soit 0.016%) indiqué plus haut. Pourquoi est-ce que le pourcentage a été multiplié par 3? Tu as totalement raison, ces 0.044 concernent en majorité un ordre de 40 Petahash que j'ai envoyé ya une semaine pendant quelques minutes pour tester une mise à jour. J'avais complètement zappé cet ordre. La Luck est cumulative, c'est à dire que la luck augmente tant que tu n'as pas miné de bloc. Me suis pressé à la fin de l'ordre d'aujourd'hui de partager le résultat et j'ai pas vérifié, j'avais la tronche dans mon travail haha. Bien spotté. |
|
|
|
Update : pas de block trouvé : 0.044% de Luck |
|
|
|
|
