I have mined in the past with no issue. I have updated the wallet and miner. Just tried to mine on nonce-pool and get all rejects. Any ideas?
Anybody else having problems with the pool? Pool is fixed now, to algo v2, somehow we missed a name change. Just tried again and now cannot connect. Currently only stratum port 3390 is open for mining. |
|
|
|
I have mined in the past with no issue. I have updated the wallet and miner. Just tried to mine on nonce-pool and get all rejects. Any ideas?
Anybody else having problems with the pool? Pool is fixed now, to algo v2, somehow we missed a name change. |
|
|
|
We have upgraded our pool to use Videlicet's excellent pool server, in mpos style of course. We could always use some more workers!How about a gpu pool bro? Need the gpu pool miner first. |
|
|
|
We have upgraded our pool to use Videlicet's excellent pool server, in mpos style of course. We could always use some more workers! |
|
|
|
Does the pool cpu miner work or a special miner for your pool?
Your help says to add the -u and -p but not in your bat example.Got it going. Oh yes there is no password, your worker.1234... id is sufficient. |
|
|
|
How much is the bounty for creating a public pool now?
At least 3500. Terms are, Pool needs to be active for atleast 30days. Anything i missed "myfarm"? Edit, from the FAQ Q. Is it possible to create pools? A. If a pool is created, any miner can steal all of the blocks. Theories have been put forth on ways to get around this such as coding in a collateral system, but none have been created. There is currently a 3500 SPR bounty on the creation of a public pool that successfully runs with no stolen coins for 30 days. Double that all up front and maybe I'll open it up to the public.  |
|
|
|
Trying to improve compatibility of my miner, I ended up stumbling on a rather odd situation. I cannot figure out if this is something I should figure out or signal to pool operator. Using sgminer as pulled out from sgminer-5.1-2014-12-20-win32.zip, just downloaded from nicehash. My hardware gives 1141 khs with the following settings: sgminer --no-extranonce -o uk.p2pool.geek.nz:5567 -k qubitcoin -u WALLET -p bleh -I 16 (P2P qubit uk node) Resulting in: sgminer 4.2.2-310-g8985f-dirty - Started: [2015-02-02 18:05:40] - [0 days 00:05:
--------------------------------------------------------------------------------
(5s):1.137M (avg):1.142Mh/s | A:19 R:0 HW:0 WU:4.000/m
ST: 1 SS: 0 NB: 8 LW: 474 GF: 0 RF: 0
Connected to uk.p2pool.geek.nz (stratum) diff 18 as user MCmR2QAnPeHbJWgRT23Rh45
Block: 412ac196... Diff:19.2K Started: [18:10:08] Best share: 39
--------------------------------------------------------------------------------
[P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
GPU 0: 48.0C 39% | 1.139M/1.142Mh/s | R: 0.0% HW:0 WU:4.000/m I:16
--------------------------------------------------------------------------------
[18:05:38] Startup GPU initialization... Using settings from pool uk.p2pool.geek
.nz.
[18:05:38] Startup Pool No = 0
[18:05:39] Initialising kernel qubitcoin.cl with bitalign, unpatched BFI, nfacto
r 10, n 1024
[18:05:40] uk.p2pool.geek.nz difficulty changed to 2.375
[18:05:40] Accepted 4b37fc99 Diff 3.403/2.343 GPU 0
[18:05:41] uk.p2pool.geek.nz difficulty changed to 2.382
[18:05:41] Accepted 0b74b9f3 Diff 22/2.375 GPU 0
[18:05:42] uk.p2pool.geek.nz difficulty changed to 4.709
[18:07:07] Accepted 314b179b Diff 5.193/4.709 GPU 0
[18:07:17] uk.p2pool.geek.nz difficulty changed to 9.408
[18:08:13] Accepted 06739e9b Diff 39/9.408 GPU 0
[18:08:30] uk.p2pool.geek.nz difficulty changed to 18.798
Diff 18 is already extreme for a 1MHs miner, staying at 4.5 would be more appropriate in my opinion but at least I got some initial accepts which confirm me this thing is working and after all, the pool is trying to guess against my luck. Now, let's try again with noncepool: sgminer --no-extranonce -o mine1.myr.nonce-pool.com:3360 -k qubitcoin -u login.worker -p bleh -I 16 sgminer 4.2.2-310-g8985f-dirty - Started: [2015-02-02 18:19:40] - [0 days 00:03:
--------------------------------------------------------------------------------
(5s):1.141M (avg):1.145Mh/s | A:0 R:0 HW:0 WU:4.190/m
ST: 2 SS: 0 NB: 6 LW: 215 GF: 0 RF: 0
Connected to mine1.myr.nonce-pool.com (stratum) diff 512 as user MaxDZ8.wtf
Block: 29351c6b... Diff:18.4K Started: [18:21:58] Best share: 30
--------------------------------------------------------------------------------
[P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
GPU 0: 47.0C 39% | 1.142M/1.145Mh/s | R: 0.0% HW:0 WU:4.190/m I:16
--------------------------------------------------------------------------------
[18:19:33] Started sgminer 4.2.2-310-g8985f-dirty
[18:19:33] * using Jansson 2.6
[18:19:33] Probing for an alive pool
[18:19:38] mine1.myr.nonce-pool.com difficulty changed to 512
[18:19:38] Startup GPU initialization... Using settings from pool mine1.myr.nonc
e-pool.com.
[18:19:38] Startup Pool No = 0
[18:19:38] Initialising kernel qubitcoin.cl with bitalign, unpatched BFI, nfacto
r 10, n 1024
Diff 512, WTF. This apparently relates to the "difficulty multiplier". Please give this a go and provide results, I need to test a few pools to figure out what's going on. Please add this to your command line if you are having issues. --difficulty-multiplier 1 |
|
|
|
I understand what you are saying, but you need PROOF that the address belongs to you and that proof is the private key.
What you have described is more or less the "normal" way to mine blocks.
No, the proof is the hash that you send the masternodes first. This is what happens: The miner sends 6 randomly picked masternodes (that everyone agrees on) an sha2 hash of: their found block + transaction from the private key that everyone must use to mine's address to their own address. Then the masternodes respond with: Ok, if that sha2 hash turns out to be a valid block + transaction to miner's address, we will add it to the blockchain. Then the miner provides the block + transaction to their own address. The masternodes then sha2 hash it and if it matches the first hash provided by the miner, they add it to the blockchain. Or am I still wrong? Wouldn't this lead to centralized distribution? |
|
|
|
|
I understand what you are saying, but you need PROOF that the address belongs to you and that proof is the private key.
What you have described is more or less the "normal" way to mine blocks.
|
|
|
|
Do you think this'll work? Hey guys, I think we can fix pool mining!!
I just need to know how the hashing works (like, what gets hashed and in which order). Can someone please tell me?
Bump. you should take a look at the code, but it goes roughly like this: 1- the whole block is hashed with double sha2. 2- the header, except for the hash above is signed with the private key and the least significant 5 bits of the nonce 3- results from 1 and 2 are appended to the header 4- the header is hashed with X11 5- compare with target, publish if it was reached, start again if not. Basically, we need to take out the whole private key part so that anyone can claim a valid block to their address. Then once we find a block, submit it with our address attached for the funds to be sent to it. This means that if you are mining for a pool, you can submit shares but give the blocks that you find to yourself. But in order to stop people from stealing found blocks, by attaching their own address instead of the block finder, we need to: Send sha2 hash of (found block + miner's address) to 6 (random?) masternodes. Masternodes confirm that they have received the hash and if it is a valid block, will count it. Miner then sends an un sha2'd version of block (found block + miner's address) Masternodes all sign message saying that the block was found and put it onto the blockchain. Attackers will need to control 4 of the 6 masternodes to replace the miner's address with their own. Boom! Done! Hopefully. Although it's probaly not going to work. Will it work? Wouldn't that... enable pools? Umm... No? I don't think you have understood what I've said. Can you take a look again please? This idea makes pools worse, it seems - first of all, you can't have a block + an address. You need to have a coinbase transaction going to the miner. Second, this way, miner is not proving the ability to spend the coinbase tx. Hmm... Ok I think I know what you mean. So how about everyone must mine with the exact same private key to find a block. When a block is found, the funds get sent to the miner's address, which he specifies somehow. But before he releases the block info, first: Miner sends 6 (random?) masternodes an sha2 hash of (the block he found + a transaction to his address). The 6 Masternodes confirm (sign a message maybe) that if the hash turns out to be a valid block, it will be added to the blockchain and the transaction will be confirmed. (this is to stop people from stealing the block) Miner then sends an un sha2'd version of the block he found + a transaction to his address. The 6 Masternodes all sign message saying that the block was found and record it to the blockchain. If the client receives a message from 4 of the 6 masternodes that the block was found + the transaction then they add it to their blockchain. Attackers will need to control 4 of the 6 masternodes to replace the miner's transaction with their own. Does that work? You must have the private key to spend the coins, if everyone had the same one then anyone could spend it, masternodes also can do nothing with the funds without the private key either. |
|
|
|
|
I'm sure this won't make any difference, some folks only read what they want to.
Do we have a pool? Yes.
It's merely a pool server we setup to solo mine to nothing more, we just so happened to let a couple of other small hashrate users in to help out a bit. Is it a risk? Of course it is.
Mr. Spread has done quite a good job at keeping this coin a solo mineable, that doesn't mean that it will always be that way, there a lot of smart folks around here and if there is enough $ involved then one should expect that there will be others trying to get in on the action in some form or another.
|
|
|
|
Smart folks will make a lot of money today. |
|
|
|
ANOTHER POOL DISCOVERED! DUMP!  ...please?  (Obviously a login screen is enough to cause massive dumping.....) I am afraid multipool is coming soon. I am afraid this is bullshit. If pool is workable,multipool is also workable,think about it . No. |
|
|
|
SPR is no a solo-mining(decentralized)coin any longer
Wrong. So you are the owner of that pool and you confirm that SpreadCoin can not be pool mined? What for is then this pool? Is it only for trusted miners? Correct, it is extremely unlikely there will ever be any other pools, this was merely a test to that. |
|
|
|
SPR is no a solo-mining(decentralized)coin any longer
Wrong. |
|
|
|
|
This thread is so much fun.
|
|
|
|
|
Show Posts
