Topic: [ANN] Mergecoin: bitcoin with merged mining patches applied (Read 3648 times)

No.


That twitter account is not related to this project.

---

https://github.com/knotwork/Mergecoin/pull/1


What is "SS++"?

https://en.wikipedia.org/wiki/Request_for_Comments 
The inception of the RFC format occurred in 1969 as part of the seminal ARPANET project.

Is it the same thing?
http://www.mergecoin.com/

this is definitely a scam.
no team +bought twitter followers etc.

guys, is it worth to invest? it pumped a lot at btc38

No, the master branch does not resolve the memory issue, as the issue is not a leak but rather is something all coins will one day face, the sheer amount of outputs, bitcoin keeps them all in RAM.

There is a version with a fix for that, but it has not been made the master branch yet.

Back when I grabbed this and used it, the only fix for the memory was a dirty trick kludge i did not want to use, so that master you just tried is what i am running. i was already throwing RAM at the coin so have no problem that it still legitimately needs lots of RAM.

There is though now a proper fix, that stores the outputs in the database instead of in RAM, it is one of the branches, see the I0Coin resurrected thread.

I am not using it yet myself but the coder seems confident it will work okay.

If so maybe all coins will eventually use it as they too run up against RAM consumption problems.

EDIT oh its the block headers not the outputs that eats the RAM, merged coins have all the merkles of all the coins they are merged with in their headers.

-MarkM-

Ok, I have compiled and run -rescan, it accepts my chain up to
But now I have no nodes to connect :/

Also, memory issue is NOT resolved, it eats 1GB already (vs ~200MB for bitcoind)

Shutting down...

https://github.com/rsnel/i0coin.git

It wasn't me. But supposedly they started with the i0coin everyone was using and patched it using the bitcoin historic record at github to bring it in steps more and more up to date.

I guess doing the updates in stages made each individual pull easier to resolve/apply.

-MarkM-

git remote show origin

So you have created NEW i0coin, NOT make old one working as 0.8.x ?

i see, well then im going to find and clone it and attempt to build a copy for bytecoin, ill post the results here soon

Sounds like its possible that in the near future a working solution appears?

Yes, it seems to be working as a secondary chain.

Apparently it was made by progressively applying bitcoin updates to the old i0coin code all the way from the old bitcoin it was based on up to latest or very recent bitcoin (one that uses the new database instead of BDB for the blockchain).

So basically it is mergedcoin plus the individuation of chains stuff that makes i0coin different from just bitcoin with secondary chain merged mining patches applied.

It should be as easy to adapt all the others from as mergedcoin itself, maybe even easier since for a lot of the places where name of coin appears you can search for i0coin instead of for bitcoin, which is nicer since bitcoin appears in variable names and file names even in all the individual coins are that are not bitcoin.

So really even if we had made mergecoin, it would be easier in some ways to base off of whichever coin first made its own new self from it than from mergecoin itself, unless the first to do so was one with more than just the usual clonecoin copy and paste changes we see so much of nowadays.

(e.g. if devcoin went first, ouch, basing off that would not be so simple as just using mergecoin directly as it changes way more things than the typical clonecoin does.)

I can't remember where I got this new i0coin, git does not conveniently tell me where it pulls from when i do git pull nor even when I do git status, I don't know enough git to have it simply tell me where the repo is.

Presumably it was posted in i0coin's own thread though or maybe some "I made a new i0coin version" thread or something as i did come across it somehow.

-MarkM-

link to the git and will it allow merged mining as a secondary chain?

Link/s to git/s? I can try them all: ixc, i0c, nmc, dvc

The recent I0Coin update to recent Bitcoin code seems to work, so maybe now people can update their merged mined coins based on that instead of needing this "mergecoin" thing for now.

-MarkM-

how is 90% solution not improvement?  just saying its been two years since some merge mine coins updated.  target is always moving anyway.  sometimes its best to make some progress than none.  its can still be sustainable and well developed if no major bugs introduced.  that has nothing to do with which version is targeted.  if new database is biggest hold up why not upgrade to just before new database.

Sounds a lot like greed over improvement. I would rather wait for a sustainable and well developed solution over hacking together something 90% for a quick few extra % income.

not such a bad idea.  if we keep starting over on mergecoin every new bitcoin update then we'll never get anywhere.  a quick update to older version is better than six more months of nothing.  don't think its a waste of time at all.

That seems kind of a waste of everyone's time and effort.

If a coin is going to bother to upgrade at all it might as well upgrade to the latest.

if it would just end up still old code it might as well stick with the old code it already has, though maybe I0Coin and GeistGeld might profit by rebasing themselves on some old merged coin that at least doesn't crash daily doing pointless DNS lookup and doesn't have memory leaks.

Also it might not be hard at all, I don't know as I didn't get to looking at those rejected chunks yet, had too many other things I need to do.

-MarkM-

Here's a thought.  Instead of using the latest Bitcoin version with the new database as your starting point, why not use the last Bitcoin version BEFORE the database change (I think that was 0.7.2).  If it's the new database changes that you're stuck on then worry about that upgrade later.  Using Bitcoin 0.7.2 would allow the merge mined cryptos to at least come close to current.  Some haven't had client updates since 2011! 

I think merged mining has the best capabilities for higher returns by mining with asics. Other currencies are too small and fast saturated when many mine on them. Litecoins cant be mined with asic's yet, pool hopping isnt really possible anymore and having a feeless pool that gives transaction fees too can be done with merged mining too.
So i think merged mining is the best way to maximize profits yet.

Can you tell if the longpoll problem is a serious one? Or wouldnt it matter much when merge mining as much coins as possible? So that the earning at the end is better anyway?

Unfortunately i cant tell much about the techniques. Would setting up a bounty help here?