Could someone help a newb play with mining these? interested in the process
I have i0coin 0.3.25.9 it says no connections 8000 blocks
TIA
Z
Topic: New Ixcoin fork -> I0coin - page 4. (Read 217119 times)
Oh boy. Maybe it is forked into more than one network?
I have only two connections, how many do you have?
Also what block number does yours show, mine says 608697
-MarkM-
610148I have only two connections, how many do you have?
Also what block number does yours show, mine says 608697
-MarkM-
addnode the same ip i did send u for a public node
9 cons atm
Oh boy. Maybe it is forked into more than one network?
I have only two connections, how many do you have?
Also what block number does yours show, mine says 608697
-MarkM-
I have only two connections, how many do you have?
Also what block number does yours show, mine says 608697
-MarkM-
I0coin is a merged-mining coin, Terracoin is not. The merged-mining patches need to be updated to work with the new bitcoin version once the new database type and so on in bitcoin is all in place.
I just updated my bitcoin to use the new type of database, it took a long time but seems to be working. Maybe allow a little more time for any problems to be found then look at updating the merged mining patches. Then all the merged mined coin types will be able to upgrade using those patches.
Meanwhile i0coin difficulty is now so low even CPUs can mine it, difficulty right now is only 7.47686009
Its a good time for people who usually cannot mine anything to snap up some coins, as once all the altcoin upgrade to new code i0coin is probably not going to go away.
-MarkM-
according to i0coind its difficulty is 95 atm I just updated my bitcoin to use the new type of database, it took a long time but seems to be working. Maybe allow a little more time for any problems to be found then look at updating the merged mining patches. Then all the merged mined coin types will be able to upgrade using those patches.
Meanwhile i0coin difficulty is now so low even CPUs can mine it, difficulty right now is only 7.47686009
Its a good time for people who usually cannot mine anything to snap up some coins, as once all the altcoin upgrade to new code i0coin is probably not going to go away.
-MarkM-
I0coin is a merged-mining coin, Terracoin is not. The merged-mining patches need to be updated to work with the new bitcoin version once the new database type and so on in bitcoin is all in place.
I just updated my bitcoin to use the new type of database, it took a long time but seems to be working. Maybe allow a little more time for any problems to be found then look at updating the merged mining patches. Then all the merged mined coin types will be able to upgrade using those patches.
Meanwhile i0coin difficulty is now so low even CPUs can mine it, difficulty right now is only 7.47686009
Its a good time for people who usually cannot mine anything to snap up some coins, as once all the altcoin upgrade to new code i0coin is probably not going to go away.
-MarkM-
I just updated my bitcoin to use the new type of database, it took a long time but seems to be working. Maybe allow a little more time for any problems to be found then look at updating the merged mining patches. Then all the merged mined coin types will be able to upgrade using those patches.
Meanwhile i0coin difficulty is now so low even CPUs can mine it, difficulty right now is only 7.47686009
Its a good time for people who usually cannot mine anything to snap up some coins, as once all the altcoin upgrade to new code i0coin is probably not going to go away.
-MarkM-
There is new coin: Terracoin. It is based on newest Bitcoin git.
Maybe use differences between original bitcoin and terracoin as base to found what changes are need? Terracoin has no merged mining with can add more work.
Maybe use differences between original bitcoin and terracoin as base to found what changes are need? Terracoin has no merged mining with can add more work.
Has anyone looked into possible file size problems? blkindex.dat for i0coin is currently 1.7 GB. Will there be a problem when it hits 2 GB?
http://msdn.microsoft.com/en-us/library/aa366778%28v=vs.85%29.aspx
We need to be sure this update produces 64 bit versions of the i0coin client, both for Windows and Linux.
http://msdn.microsoft.com/en-us/library/aa366778%28v=vs.85%29.aspx
We need to be sure this update produces 64 bit versions of the i0coin client, both for Windows and Linux.
(...), is there any technical reason why it couldn't work with scrypt-based coin too? I'd love to find something to MM with LTC, just for the hell of it. Even if it was only LQC (now dead) that I was merge mining it with.
LTC have different hashing protocol than BTC and other MM coins, it can not be merged.I'm talking about merge-mining scrypt with scrypt.
-- Smoov
All the merged mined coins need updating, so it makes sense to first update the merged mining patch to work with the latest bitcoin before worrying about the details that make the various merged mined coins different from each other.
Basically one can view the merged mined coins as being made by applying two patches to bitcoin, one being the merged mining patch the other being a patch that makes it into a specific coin variant. A patch that changes the name, the ports, the irc channel, the dns bootstrap, the hard coded bootstrap nodes, the checkpoints, the difficulty and reward details, the details of how to form an address from a key, to make the different-looking addresses some coins like to use, and the handshake four bytes that keep the different coins from accidentally crosstalking with each other.
-MarkM-
Basically one can view the merged mined coins as being made by applying two patches to bitcoin, one being the merged mining patch the other being a patch that makes it into a specific coin variant. A patch that changes the name, the ports, the irc channel, the dns bootstrap, the hard coded bootstrap nodes, the checkpoints, the difficulty and reward details, the details of how to form an address from a key, to make the different-looking addresses some coins like to use, and the handshake four bytes that keep the different coins from accidentally crosstalking with each other.
-MarkM-
I kinda figured that I would have to fixed merged mining along with i0coin itself last night.
I was able to modify Bitcoin 0.7.2 into an i0client..too a point.
I was able to compile and run the new i0client, but it would start to throw hash errors somewhere in the ~170000 block area, my suspicion was that it found the first merged mine block.
I am now in the process of trying to integrate the merged mining, at least to the point where the new client can handle it's chain, but it looks like at that point the whole merged mining patch would be in place.
LTC have different hashing protocol than BTC and other MM coins, it can not be merged.
(...), is there any technical reason why it couldn't work with scrypt-based coin too? I'd love to find something to MM with LTC, just for the hell of it. Even if it was only LQC (now dead) that I was merge mining it with.
All the merged mined coins need updating, so it makes sense to first update the merged mining patch to work with the latest bitcoin before worrying about the details that make the various merged mined coins different from each other.
Basically one can view the merged mined coins as being made by applying two patches to bitcoin, one being the merged mining patch the other being a patch that makes it into a specific coin variant. A patch that changes the name, the ports, the irc channel, the dns bootstrap, the hard coded bootstrap nodes, the checkpoints, the difficulty and reward details, the details of how to form an address from a key, to make the different-looking addresses some coins like to use, and the handshake four bytes that keep the different coins from accidentally crosstalking with each other.
If someone is going to tinker with the MM patch/code, I have a somewhat off-topic question about it, like, is there any technical reason why it couldn't work with scrypt-based coin too? I'd love to find something to MM with LTC, just for the hell of it. Even if it was only LQC (now dead) that I was merge mining it with.Basically one can view the merged mined coins as being made by applying two patches to bitcoin, one being the merged mining patch the other being a patch that makes it into a specific coin variant. A patch that changes the name, the ports, the irc channel, the dns bootstrap, the hard coded bootstrap nodes, the checkpoints, the difficulty and reward details, the details of how to form an address from a key, to make the different-looking addresses some coins like to use, and the handshake four bytes that keep the different coins from accidentally crosstalking with each other.
Off the current topic I know, but if someone is already going to be tinkering with it, maybe find out the feasability of it while someone is already poking around?
-- Smoov
All the merged mined coins need updating, so it makes sense to first update the merged mining patch to work with the latest bitcoin before worrying about the details that make the various merged mined coins different from each other.
Basically one can view the merged mined coins as being made by applying two patches to bitcoin, one being the merged mining patch the other being a patch that makes it into a specific coin variant. A patch that changes the name, the ports, the irc channel, the dns bootstrap, the hard coded bootstrap nodes, the checkpoints, the difficulty and reward details, the details of how to form an address from a key, to make the different-looking addresses some coins like to use, and the handshake four bytes that keep the different coins from accidentally crosstalking with each other.
-MarkM-
Basically one can view the merged mined coins as being made by applying two patches to bitcoin, one being the merged mining patch the other being a patch that makes it into a specific coin variant. A patch that changes the name, the ports, the irc channel, the dns bootstrap, the hard coded bootstrap nodes, the checkpoints, the difficulty and reward details, the details of how to form an address from a key, to make the different-looking addresses some coins like to use, and the handshake four bytes that keep the different coins from accidentally crosstalking with each other.
-MarkM-
Maybe I should take another look at just pushing i0coin to 0.7.2. If I (we) are going to make major changes to the i0client, it makes sense just to bring it to the current BTC client level.
That really is the only makes sense option if you can do it that would be great.
Any news about moving code to 0.7x ?
New database is neat...
New database is neat...
I have looked at it, but there is definitely some work to do to make that jump, and I am unsure if it will solve the memory problem. The jump from 3.24 (I0coin version 32509 - actually looks closer to BTC 4.01) to 0.6.3 (with doublec's patch and a couple of my tweaks) did not solve the issue.
Maybe I should take another look at just pushing i0coin to 0.7.2. If I (we) are going to make major changes to the i0client, it makes sense just to bring it to the current BTC client level.
Any news about moving code to 0.7x ?
New database is neat...
New database is neat...
i0coin balances on mmpool.bitparking.com are in the process of being sent out now. You should see your coins appear in the next few hours depending on network speed.
Some more info here: https://bitcointalk.org/index.php?topic=124316.20
at second page and bottom
at second page and bottom
Hmm a new error I have not seen before:
-MarkM-
Code:
************************
EXCEPTION: St9bad_alloc
std::bad_alloc
i0coin in ProcessMessage()
************************
EXCEPTION: St9bad_alloc
std::bad_alloc
i0coin in ProcessMessage()
************************
EXCEPTION: St9bad_alloc
std::bad_alloc
i0coin in ProcessMessage()
************************
EXCEPTION: St9bad_alloc
std::bad_alloc
i0coin in ProcessMessage()
************************
EXCEPTION: St9bad_alloc
std::bad_alloc
i0coin in ProcessMessage()
************************
EXCEPTION: St9bad_alloc
std::bad_alloc
i0coin in ThreadMessageHandler()
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
EXCEPTION: St9bad_alloc
std::bad_alloc
i0coin in ProcessMessage()
************************
EXCEPTION: St9bad_alloc
std::bad_alloc
i0coin in ProcessMessage()
************************
EXCEPTION: St9bad_alloc
std::bad_alloc
i0coin in ProcessMessage()
************************
EXCEPTION: St9bad_alloc
std::bad_alloc
i0coin in ProcessMessage()
************************
EXCEPTION: St9bad_alloc
std::bad_alloc
i0coin in ProcessMessage()
************************
EXCEPTION: St9bad_alloc
std::bad_alloc
i0coin in ThreadMessageHandler()
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
-MarkM-
Same version, I am running your version. The miniUPNP does not work with my router but I used to get 8 connections anyway.
Maybe UPNP doesn't work on most people's routers or they are not using it or something?
Still, if you have incoming port open I should have been able to connect to you unless you are at max connections.
-MarkM-
Maybe UPNP doesn't work on most people's routers or they are not using it or something?
Still, if you have incoming port open I should have been able to connect to you unless you are at max connections.
-MarkM-
Speaking of connections. IS THERE ANYONE OUT THERE?!?! I am not finding connections...
I have 18 connections from my client running v32509. What version of the client are you running? Jump to: