Pages:
Author

Topic: 4,000 BTE bounty for patching Bytecoin to merged mine (Read 3157 times)

legendary
Activity: 2912
Merit: 1060
I'm revoking the bounty. I no longer have the funds.

Anon136 and BladeRunner, feel free to do what you wish. Thanks for the support.

Unfortunately, we didn't gain mass support.

Im still trying to figure out if I owe a bounty and if so to who. BTE is certainly been gaining market support.

Well this merged mining bounty is canceled but you can donate to ahmed I think it is.
full member
Activity: 205
Merit: 100
Cheif Oompa Loompa.
I'm revoking the bounty. I no longer have the funds.

Anon136 and BladeRunner, feel free to do what you wish. Thanks for the support.

Unfortunately, we didn't gain mass support.

Im still trying to figure out if I owe a bounty and if so to who. BTE is certainly been gaining market support.
legendary
Activity: 2912
Merit: 1060
I'm revoking the bounty. I no longer have the funds.

Anon136 and BladeRunner, feel free to do what you wish. Thanks for the support.

Unfortunately, we didn't gain mass support.
legendary
Activity: 1722
Merit: 1217
You told me master earlier. I was under that assumption.
https://bitcointalksearch.org/topic/m.2764701

But sure, I will release the bounty once the following are complete:
I have a windows binary. Is this patched? http://www.bytehits.info/bytecoin-0.8.1-win32.7z
I sucessfully add it to a p2pool node as a slave mergedmine coin. I plan to use my own p2pool.
The fork begins and people support it. Have you set the block at which it begins?
And I find the first block. This won't take long with 22 ghs.

sounds good. keep us posted.
hero member
Activity: 518
Merit: 500
Bitrated user: ahmedbodi.
ive not used knotwork's repo, if you ask markm himself he'll tell you he never got it to work. I modified doublec's bitcoin source and then created the bytecoin wallets from there
legendary
Activity: 2198
Merit: 1014
Franko is Freedom
I have just now forked bitcoin to a new repo, https://github.com/knotwork/Mergecoin.git

This is to be the Mergecoin repo.

I am going to clone it at home and try to get the merged mining patches to apply.

If I can do that I can then push the changes back up to the repo and presto we will have the wonderful common ancestor repo from which all the merged mined coins can then update themselves, and from which bytecoin (and any other bitcoin clone that wants to add merged mining) can also create a new version of itself.

-MarkM-


You have created the Adam of new MM coins. Smiley
legendary
Activity: 2912
Merit: 1060
No rush. I am excited though.
hero member
Activity: 518
Merit: 500
Bitrated user: ahmedbodi.
yep it compiles into a daemon just not a qt yet, a few more commits needed yet thats why its currently in beta, so any input is welcome
legendary
Activity: 2912
Merit: 1060
Mark I welcome your opinion on bounty satisfaction.
legendary
Activity: 2940
Merit: 1090
What aux-chain I.D. was chosen for this chain? It has to be different from the others, you know that, right?

Also i think they might be indexes into an array in coinbase, so skipping a bunch of numbers probably isn't a good idea either as it would waste space in the parent blockchain maybe in all blockchains. So probably using the next number available is the way to go?

-MarkM-
legendary
Activity: 2912
Merit: 1060
PS. a daemon would be a nice addition.
legendary
Activity: 2912
Merit: 1060
Hmm you're the expert, but I think a hardform is required. NMC had to do it. Others came mm stock from the beginning.

Anyway, you are close to 3,000 bte. We will have to find the other guy.
hero member
Activity: 518
Merit: 500
Bitrated user: ahmedbodi.
thats the binary for the non merged mined bytecoin. I requested everyone interested to pm me for a copy of the source for the merged mined copy. So that i can compile a list and then decide based on feedback where to go from there. keep it as slave or hardfork and move to master. I dont believe that a hardfork is neccesary from my discussion when using bytecoin as a slave so no fork and block has been set. I shall pm you later with a copy
legendary
Activity: 2912
Merit: 1060
You told me master earlier. I was under that assumption.
https://bitcointalksearch.org/topic/m.2764701

But sure, I will release the bounty once the following are complete:
I have a windows binary. Is this patched? http://www.bytehits.info/bytecoin-0.8.1-win32.7z
I sucessfully add it to a p2pool node as a slave mergedmine coin. I plan to use my own p2pool.
The fork begins and people support it. Have you set the block at which it begins?
And I find the first block. This won't take long with 22 ghs.
hero member
Activity: 518
Merit: 500
Bitrated user: ahmedbodi.
precisly. our plans is to operate 4 pools offering bitcoin merged mining various other coins including BTE and doing auto exchange or sending each coin to specified address as the user wishes once we are out of beta stages.
legendary
Activity: 2912
Merit: 1060
The new client can mine bte UNDER btc?
hero member
Activity: 518
Merit: 500
Bitrated user: ahmedbodi.
im not sure if its 0.8.3 i believe it was 0.8.1 ill have to check the source for you and get back
donator
Activity: 362
Merit: 250
Is it based on 0.8.3?
hero member
Activity: 518
Merit: 500
Bitrated user: ahmedbodi.
the new client that i released is for merged mining as a slave Huh thats how we got it to work
full member
Activity: 182
Merit: 100
fml
All the merged mined coins all need the same basic template from which to update themselves:

A copy of bitcoin with the merged mining patches applied.

Given that, each coin then only needs to fork it and apply their own usually pretty trivial modifications that makes them different from each other, such as their coins per block, their difficulty adjustment system, their default ports, their IRC channel or channels, their magic handshake bytes, and the cosmetics.

So really the best place to start is with a good recent stable copy of bitcoin.

Otherwise its a huge waste of programmer time with everyone hacking directly at just one coin instead of all being able to work from the common ancestor, which is bitcoin with ONLY the merged mining patches applied.

NOTE that doing it this way would also allow I0coin and geistgeld, the most troublesome / hardest to merge, to be updated too, allowing more people to be able to successfully merge the full panoply of merged mined coins.

So for anyone who is actually going to merged mine, having this raw "pure bitcoin with ONLY merged mining patches applied" is pretty much a no-brainer, allowing all merged coins to then be upgraded thus allowing all miners who merge to maximise their merges.

(To update Bytecoin you would diff it against the version of bitcoin it was forked from, then apply that diff as a patch to the "raw bitcoin with ONLY merged mining patches applied" repo, nice and simple. Oh and pick a block number at which merged mining will turn on.)

-MarkM-


Why is every single post you make, TLDR. You are smart, we get it Roll Eyes
Pages:
Jump to: