Page 3 of 16

Re: Merged mining block number

Posted: Sat Jul 16, 2011 1:28 pm
by nodemaster
doublec wrote:Assuming tests show that things work ok, I think sooner rather than later is better to activate it. This stops the uncertainty that might occur over the change and put people off using namecoin. 24,000 seems reasonable.
Yes, I agree. If we agree to do this (and i see more benefits doing it) then we should do it as soon as possible.

Re: Merged mining block number

Posted: Sat Jul 16, 2011 4:33 pm
by JohnDoe
Agreed on 24,000. We still have a couple months to go so no pressure.

Btw, I made a thread about this on the Bitcoin forum but I don't really get how it works so any help in explaining things would be appreciated.
http://forum.bitcoin.org/index.php?topic=29074.0

Re: Merged mining block number

Posted: Sun Jul 17, 2011 10:08 pm
by nodemaster
okay guys, you asked for it, here we go 8-)

Announcing a new Pool https://alpha.masterpool.eu The only purpose of this alpha pool is to test merged mining.

WARNING! This pool is in ALPHA status. This means your can test, but you get no payouts (we are running on testnet anyway, thus the revenues are not usable on standard bitcoin or namecoin net). Furthermore most of the mined coins will be invalid/orphaned even on testnet. Everything on this site may crash and burn or kill kittens. YOU HAVE BEEN WARNED!

Welcome to the worst pool ever

- Most blocks ORPHANED
- Proportional payment (but 100% Pool Fee) :-D
- No Payouts!
- Pool in fully untested Alpha status
- Most things DON'T work

BUT

- It is running on BTC and NMC testnet
- You can use and test merged mining
- You'll see what you would have mined with merged mining

Here are a few screenshots showing what you might expect: http://www.wuala.com/nodemaster/screens ... ed-mining/

Please choose any miner and try to test this pool (mining URL http://alpha.masterpool.eu:8888)This is more or less a miner test. Thus please report if you have any issues with any miner on this pool. This is only a VPS. Thus please don't hammer it and don't expect it to be fixed within minutes if it crashes! However I'll implement some more features the next days and hopefully get at least BTC testnet ready for payout.

Re: Merged mining block number

Posted: Sun Jul 17, 2011 10:16 pm
by fireballchad
I will throw my tiny 150m/hashes at it for you!

On a side note adding an option to change your password on the site after recovery would be wonderful ;)!

Re: Merged mining block number

Posted: Sun Jul 17, 2011 10:28 pm
by nodemaster
fireballchad wrote:On a side note adding an option to change your password on the site after recovery would be wonderful ;)!
Right. It is on the ToDo list with high priority (also for stable masterpool).

Re: Merged mining block number

Posted: Mon Jul 18, 2011 12:54 am
by fireballchad
Image

I get this with GUI Miner when running OpenCL for an extended period of time.

The Ufasoft CPU miner seems to work fine.

Re: Merged mining block number

Posted: Tue Jul 19, 2011 12:35 am
by moa
24,000 would not be a good idea with the other changes that come into effect at the same time. There is no way to truly test these until we pass block 24,000 right?

Maybe 4-6 weeks after, say 28,000? or 30,000?

Also, be aware these block numbers could come up quite quickly if we have a ramp in value and subsequent nmc mining in the interim in anticipation.

Re: Merged mining block number

Posted: Tue Jul 19, 2011 1:43 am
by vinced
nodemaster wrote:I just put my findings into the wiki: http://dot-bit.org/MergedMining

Please feel free to correct anything in there. I'm no native speaker and my wife is egging me to do family stuff, thus I am in a hurry :lol:

I hope this helps a bit. I'll fledge this out as soon as I have the time.
Very nice! Thank you for writing this up.

I have a namecoin release candidate here: https://github.com/vinced/namecoin/tree/v0.3.24.51-rc1

As before, the bitcoind patched version is here: https://github.com/vinced/namecoin/tree/mergedmine

Changes:

[*] Start block for namecoin is 24000 (this is still open for discussion).
[*] Added validation to make sure the same work is not submitted twice to the same chain.
[*] Previous point required an incompatible change. If you have a testnet-in-a-box, you have to start it over. The proxy script changed too.

Re: Merged mining block number

Posted: Tue Jul 19, 2011 9:33 pm
by gigabytecoin
Ok so the "patched version" of bitcoin is called "mergedmine" then?

And in effect, bitcoin is patched or "different than default settings" but still treats the bitcoin blockchain and bitcoin side of things the exact same way as before? The only difference is... (PLEASE FILL IN THIS BLANK?!)

Re: Merged mining block number

Posted: Fri Jul 22, 2011 2:47 am
by vinced
gigabytecoin wrote:Ok so the "patched version" of bitcoin is called "mergedmine" then?

And in effect, bitcoin is patched or "different than default settings" but still treats the bitcoin blockchain and bitcoin side of things the exact same way as before? The only difference is... (PLEASE FILL IN THIS BLANK?!)
The only difference is that it provides the getworkaux rpc call. This call is used to add some information in the bitcoin coinbase that helps the namecoin blockchain validate the work. Blocks generated by the modified bitcoin will be accepted as usual by the bitcoin network.