|
Fun fact:
We are now on page 2^8.
Could that be expressed as 2^2^2^2?
|
|
|
|
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? |
|
|
|
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. But at the same time the block is mined with the private key everyone knows, the masternodes make sure the miner is able to withdraw his coins from that address before they get stolen. Do you know what I mean? |
|
|
|
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? |
|
|
|
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? |
|
|
|
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? |
|
|
|
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? |
|
|
|
3 days left to get bonus when pre order GTA V
I'd like to get GTA V for $36. Wil I get San Andreas as well? Yes, when you redeem game, GTA SA will automatically add to you game library How any GB is SA? GB ? you mean hdd requirement ? How big is the download? Because I can't download much. But next month I can. (this is only for SA) Minimum: OS: Microsoft® Windows® 2000/XP Processor: 1Ghz Pentium III or AMD Athlon Processor Memory: 256MB of RAM Graphics: 64MB Video Card (Geforce 3 or better) Hard Drive: 3.6GB of free hard disk space (minimal But do you know how many mb's I need to download from the internet? i really don't know, If you buy GTA V ,GTA SA will add in your library game on steam you can download when u want ? Ok. |
|
|
|
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. |
|
|
|
(...)
Well, if Mr. Spread wasn't banned, maybe he could change it. Ever thought about that? bitman008 is a troll, please ignore him. We can address real issues with real people and leave the trolls talking alone... It was just to help new investors. |
|
|
|
3 days left to get bonus when pre order GTA V
I'd like to get GTA V for $36. Wil I get San Andreas as well? Yes, when you redeem game, GTA SA will automatically add to you game library How any GB is SA? GB ? you mean hdd requirement ? How big is the download? Because I can't download much. But next month I can. (this is only for SA) Minimum: OS: Microsoft® Windows® 2000/XP Processor: 1Ghz Pentium III or AMD Athlon Processor Memory: 256MB of RAM Graphics: 64MB Video Card (Geforce 3 or better) Hard Drive: 3.6GB of free hard disk space (minimal But do you know how many mb's I need to download from the internet? |
|
|
|
As already explained, several time, the feature of "no pools" does not mean that it is impossible to maintain a pool, but rather that they are not economically viable, since anyone can steal the coins form them [...]
Would be somewhat easy to secure by moving coins to a separate wallet as soon as they confirm and make the payouts from there. The only problem I'd see is if a miner would move the coins before the pool does. that's an arm race, with a 50-50 chance for each one to win, so the pool owner can make it profitable by rising the fees and paying the other users from his revenue, but then... it is risky... another solution might be that the pool owner charges a "deposit" from the miners, and if the miner steals something, the deposit is held and the miner banned. But i don't see this growing into large scale. Thats an experiment worth making. Or we could make block times 1 hour so that it would cost too much.  |
|
|
|
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.
I am not against pool,what I am against is that spr is not worth the title of 'no pool'[/b][/size][/color] Well, if Mr. Spread wasn't banned, maybe he could change it. Ever thought about that? |
|
|
|
|
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?
|
|
|
|
As already explained, several time, the feature of "no pools" does not mean that it is impossible to maintain a pool, but rather that they are not economically viable, since anyone can steal the coins form them [...]
Would be somewhat easy to secure by moving coins to a separate wallet as soon as they confirm and make the payouts from there. The only problem I'd see is if a miner would move the coins before the pool does. That's why a pool should have collateral. |
|
|
|
(...)
Where is your proof?
please, do not quote the big red letter trolls. just ignore him... Sorry, ok. |
|
|
|
Sure, I'm just a troll right.
Got anything to discuss instead of trying to say I'm a troll? Just because you can't refute my argument doesn't mean I'm a troll.
Spread's purpose is defeated for the moment, sorry for the sad reality check but instead of calling people trolls why don't you go fix the actual code instead of brining features from other coins while your main edge ("no pools") is flawed..
Edit: between me and you, frankly you're the troll.. Quoting posts while modifying what was wrote there.. ya. pityful.
Your name seems very familiar. Do I know you? |
|
|
|
3 days left to get bonus when pre order GTA V
I'd like to get GTA V for $36. Wil I get San Andreas as well? Yes, when you redeem game, GTA SA will automatically add to you game library How any GB is SA? GB ? you mean hdd requirement ? How big is the download? Because I can't download much. But next month I can. (this is only for SA) |
|
|
|
3 days left to get bonus when pre order GTA V
I'd like to get GTA V for $36. Wil I get San Andreas as well? Yes, when you redeem game, GTA SA will automatically add to you game library How any GB is SA? |
|
|
|
3 days left to get bonus when pre order GTA V
I'd like to get GTA V for $36. Wil I get San Andreas as well? |
|
|
|
|
Show Posts
