|
As promised, I'll show my hobo love, soon as I get home. 24 hours, 1 MH, 100% donation.
|
|
|
|
|
5hAFCUDot9zy5ioNir4KhYAkcHwfUreS3F
|
|
|
|
|
Please delete, no longer needed
|
|
|
|
great trade, thx  |
|
|
|
|
I'll take 10K, for .09 BTC
|
|
|
|
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  |
|
|
|
Ej8DJfyqPUhqZa7g1DQWrMP5o8cryUiHt7 Thanks  |
|
|
|
Mv4zCy3FU3HeJ7Nxxh9XhKwxpRJRkSrhbn Thanks |
|
|
|
EiQBz3wgkXe8KNMXcxm6URHr4zbyaHLbVA I'd love me some nickels |
|
|
|
|
GIL gains popularity, every day. It will be added to Cryptsy soon. Not too late to get in on the ground floor.
|
|
|
|
If this was profitable, why wouldn't you just do this yourself and rake in the profits?
Bingo. Although, it is possible, the OP wants instant BTC, rather than waiting the 1200 confirmations, for the pool rewards |
|
|
|
You are better off making a Scrypt coin, if you haven't noticed, SHA coins are ruled by ASICS, and, despite what people try to tell you, ASIC's have driven up EVERY SHA coin's diff to retarded levels. To chose a source code, find a coin that already closely resembles the stats you wish your coin to have, and modify it. |
|
|
|
|
Or, just open your Cryptsy balances, and mulitply your current portfolio value, by the current value of BTC....
|
|
|
|
|
Hey.
I admire your project, and I hope it succeeds.
I am the developer of GIL. I'd like to sponsor CureCoin with 10K GIL, to start.
If you send me a wallet address, I'll forward them to you, when I get home from work.
GIL is slated to be added to Cryptsy shortly.
Good luck Smiley
|
|
|
|
Son of a bitch, really? Thats all I had to do? Mother fucker... |
|
|
|
Almost 24hrs without access for me. Hmmm
Me too!!! |
|
|
|
|
I can't even get into cryptsy right now...
|
|
|
|
Releasing a coin, without the source. People are not going to be happy about that man. Poor little Linux and Mac users  There is more too releasing sources than just Linux/Mac, How do you know there isn't code in there to steal your wallets, a massive premine or turn your clients into a botnet? Because I know the devs of this particular coin, I'm not worried about that. And, fyi, just because the sourcecode is clean, that doesn't mean the released QT wallet is clean, it could have easily been compiled from different source code. |
|
|
|
Releasing a coin, without the source. People are not going to be happy about that man. Poor little Linux and Mac users |
|
|
|
|
Show Posts
