Pages:
Author

Topic: New Ixcoin fork -> I0coin - page 22. (Read 217119 times)

legendary
Activity: 1078
Merit: 1005
November 30, 2011, 07:41:25 AM
Here's a fun feature included in the latest version of i0coin (32506) as a result of the patches I cherry-picked from the recent bitcoin releases. It's khal's patch to sign and verify messages using bitcoin addreses. If you're the owner of an address you can sign a message with the private key.  Anyone can verify the message is from you by calling 'verifymessage' passing it the address and the result of the sign operation. This is a way of confirming a message comes from someone controlling a particular address. Examples:

Code:
$ i0coind getnewaddress
jMq8wkYNByEqBtcUo5CaWq2mrxuRgyVHWB

$ i0coind signmessage jMq8wkYNByEqBtcUo5CaWq2mrxuRgyVHWB "Hello World"
HL2fs5IirODMtZCCAF9Vqgz5ZPpcmqNWgy7cnl50OlkoYvOC7gLlIqD4Z3Acmuu+idOQoRRo2DmEl9z/MCnnR8Q=

$ i0coind verifymessage jMq8wkYNByEqBtcUo5CaWq2mrxuRgyVHWB HL...MCnnR8Q= "Hello World"
true

$ i0coind verifymessage jMq8wkYNByEqBtcUo5CaWq2mrxuRgyVHWB HL...MCnnR8Q= "Hello"
false

$ i0coind verifymessage jaQ4X3vVN41TaYpicQx7YemmvJWoXEscwS HL...MCnnR8Q= "Hello World"
false

This has uses in having a signed contract in exchange for funds transfer. Or if someone claims ownership of an address (say to show how much money they have or to prove they committed some transfer) you can ask them to prove it by signing a message with the address.
legendary
Activity: 1078
Merit: 1005
November 30, 2011, 05:15:22 AM
So that covers everything but an exchange Smiley
Right, I'm sure one will come when block 150,000 or 160,000 ticks over if not before.
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
November 30, 2011, 04:20:26 AM
I'm still running client 0.3.25 beta I think.  Is that still valid, or do we have to download the new build?
You will need to download the new build before block 150,000 if you are running older than 0.3.25.4, or block 160,000 if you are running 0.3.25.4 itself (this is reported as 32504 in the 'version' field of the 'getinfo' RPC call in the command line client. Latest version is 32506).
So that covers everything but an exchange Smiley
... looks up at the bounties ...
Well there certainly is some incentive for an exchange
and no one has said if they are willing to pay any of the bounties without an exchange since when I asked that before ...
legendary
Activity: 1078
Merit: 1005
November 30, 2011, 02:11:00 AM
I'm still running client 0.3.25 beta I think.  Is that still valid, or do we have to download the new build?
You will need to download the new build before block 150,000 if you are running older than 0.3.25.4, or block 160,000 if you are running 0.3.25.4 itself (this is reported as 32504 in the 'version' field of the 'getinfo' RPC call in the command line client. Latest version is 32506).
legendary
Activity: 1078
Merit: 1005
November 30, 2011, 02:09:33 AM
I've released source and windows binaries for i0coin version 32506 at http://i0coin.bitparking.com/. This version  backports a bunch of fixes from recent bitcoin versions. The most important change however is it enables merged mining as a auxiliary chain on block 160,000. This is a required upgrade before block 160,000, otherwise you'll be left on the wrong side of a fork. This completes the set of bug fixes and merge mining enabling I set out to do so will hopefully be the last 'required upgrade', except for emergency bug fixes.

Hopefully with merged mining, and a stronger hash rate, exchanges and merchants can have some confidence in the coin.
hero member
Activity: 896
Merit: 1000
Seal Cub Clubbing Club
November 30, 2011, 02:06:04 AM
I'm still running client 0.3.25 beta I think.  Is that still valid, or do we have to download the new build?
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
November 30, 2011, 01:17:30 AM
I guess you could just add 2 sets of MM data into Bitcoin - one for namecoin and one for i0coin (after the namecoin data in the coinbase ... assuming namecoin MM ignores the data after it?)

It does because coinbase field also contains the "extra nonce".  My understanding is that Bitcoin supports multiple chains.

You simply need a poolserver capable of generating the proper multi-chain block header, miners willing to mine it, and each individual chain understanding what it is looking for inside the coinbase field.
Actually - technically, bitcoin doesn't directly support merged mining.
What actually happens is that it doesn't care what is in coinbase and thus supports anyone who wants to put whatever they like in there.
i.e. no bitcoin code change was required for merged mining except the ability to tell bitcoind the replacement coinbase value rather than the one it puts there but never validates or looks at it's value
( quite a few of the scamcoin chains have a single block with the coinbase saying 'Kano' coz I felt like it Smiley )
How this was actually implemented in bitcoind was via the new function (getmemorypool) that allows you to tell bitcoind the entire block rather than just the hash
(odd decision that one ...)

The 'extra nonce' is not of interest to bitcoin in any way since the 'nonce' field is actually a specific field in the block and part of the hash ('extra nonce' isn't)
Thus the reason that MM works is that bitcoin doesn't care Smiley
legendary
Activity: 1078
Merit: 1005
November 29, 2011, 11:52:37 PM
It does because coinbase field also contains the "extra nonce".  My understanding is that Bitcoin supports multiple chains.
I've tested merge mining bitcoin as the primary chain (using namecoin patches for getworkaux implementation), with i0coin and namecoin as auxiliary chains and all three chains merge mined producing blocks (on testnet for the chains).
legendary
Activity: 1078
Merit: 1005
November 29, 2011, 06:55:34 PM
I sent you doublec 1000 ioc.  However, if you read my post, the 5 btc and rewards were if you lowered the reward from 48 to 1 within the near future.  The reason to make a coin different than btc or nmc with merged mining.  I can't seem to mine with the new client, it crashes when I find a block. 
Yes, I saw your request for a drop to the reward. I won't be changing i0coin since this changes the value of existing held coins. It would mean i0coin would effectively be a new coin with a large 'premine' given to people who mined previously. My plan was to fix i0coin bugs, implement merged mining, but leave the generation rate, transaction fees, and values as they are since they are what gives a coin variant its identity. Plus I'd like to avoid the claims of arbitrary changing of values by a 'coin dictator'.

For ixcoin you should contact the coin creator with your idea of dropping the rate. If they agree I'd be willing to provide the patches, a pool, etc. I'd be interested in seeing what a slower generation coin does. Current coins seem to have more coins available than people need to use since their is very little non-trading usage of them. Since ixcoin already has a premine and a 'controller' it may not be so bad to change things.

Now that merge mining exists a possibly better approach for these "lets change a coin's features" requests is to create a new chain starting with no premine with the new features. Merge mine it with existing coins. Provide an exchange to trade between new coin and old coin, and see how they go.
legendary
Activity: 1078
Merit: 1005
November 29, 2011, 06:48:11 PM
What's going to happen to all the legacy i0coins?
If you have existing i0coins they will remain usable. This is not creating a new chain like SC 2 did to SC 1. It's operating from the existing blockchain.
legendary
Activity: 1078
Merit: 1005
November 29, 2011, 06:47:05 PM
DoubleC, will you be opening an exchange at block 150,000? On bitparking?
See my reply to a similar question. I haven't yet pushed the version that enables merged mining so it's unlikely that the chain will get any great amount of hash power until that goes through. I'll do that in a day or two, probably switching on at 160,000. I'm currently backporting a number of bitcoin bug fixes that have been done since the original i0coin was released.

It's possible to do an exchange earlier with some form of auto-checkpointing mechanism but that centralizes things around the exchange somewhat (ie. the exchange has control of what blockchain is the 'real' fork). I would imagine most people would be against that.
hero member
Activity: 717
Merit: 501
November 29, 2011, 02:51:07 PM
I sent you doublec 1000 ioc.  However, if you read my post, the 5 btc and rewards were if you lowered the reward from 48 to 1 within the near future.  The reason to make a coin different than btc or nmc with merged mining.  I can't seem to mine with the new client, it crashes when I find a block. 

Nasakioto wants someone to convert ixcoin into merged mining and has also offered a bounty for someone to do so.  I have a bounty for ixc too.  However, I would be extremely happy if one of these coins became a true low inflation cryptocurrency with a 1 block reward. 

But I offer to you 15 BTC if you change the reward such that on or before block 300,000 for ioc or block 100,000 for ixc the reward drops to 1 permanently.  I would also prefer a mandatory automatic transaction fee to prevent attacks and control size.  Also there must be a pool that exists to merge mine btc, nmc, ixc, and ioc all at once before reward is paid and be pretty sure everyone switched and on the new block.

The ixc offered in my ixc reward will still exists, but the 5 BTC is now the new 15 BTC reward.

So either (96 to 1 for ixc) or (48 to 1 for ioc) with merged mining and a pool for 15 BTC.

Dilution is not the solution to pollution.
donator
Activity: 1218
Merit: 1079
Gerald Davis
November 29, 2011, 11:47:03 AM
I guess you could just add 2 sets of MM data into Bitcoin - one for namecoin and one for i0coin (after the namecoin data in the coinbase ... assuming namecoin MM ignores the data after it?)

It does because coinbase field also contains the "extra nonce".  My understanding is that Bitcoin supports multiple chains.

You simply need a poolserver capable of generating the proper multi-chain block header, miners willing to mine it, and each individual chain understanding what it is looking for inside the coinbase field.
legendary
Activity: 1855
Merit: 1016
November 29, 2011, 11:43:19 AM
What's going to happen to all the legacy i0coins?

It will be in some one's wallet, until he/she moves it to some other wallet.
hero member
Activity: 896
Merit: 1000
Seal Cub Clubbing Club
November 29, 2011, 11:17:33 AM
What's going to happen to all the legacy i0coins?
donator
Activity: 3228
Merit: 1226
★Bitvest.io★ Play Plinko or Invest!
November 29, 2011, 10:08:50 AM
DoubleC, will you be opening an exchange at block 150,000? On bitparking?

sr. member
Activity: 324
Merit: 250
November 28, 2011, 01:00:19 PM
I have 2.92 installed.
I get a pango warning about all font fallbacks failing when running from a terminal.
legendary
Activity: 1078
Merit: 1005
November 28, 2011, 04:56:30 AM
None of the text renders for me in the linux gui. I'm using Ubuntu 11.10, anyone know why?
What version of wxWidgets are you using? 2.9,1 exhibits that problem I think. Try 2.9.2.
hero member
Activity: 756
Merit: 500
November 26, 2011, 11:07:28 PM
Is there anyway to do merged mining on windows?
Merged mining should work fine on Windows. Use the windows binaries from http://i0pool.bitparking.com and start i0coin.exe with the "-server" command line option, or run the non-gui version i0coind.exe instead. Install Python for windows and use that to run the merged mining proxy, same as the linux command to run it.

I tried Python on Windows to run the merge mining proxy, somehow it gives errors, if you have the time, can give the steps?  Maybe I did something wrong.
legendary
Activity: 1078
Merit: 1005
November 26, 2011, 10:08:13 PM
Merged mining kills the building of it on OS X the version 32502 works fine.
I pushed a fix to the git repository just now for this. Let me know if it works for you.
Pages:
Jump to: