Pages:
Author

Topic: [ANNOUNCE] Ixcoin - a new Bitcoin fork - page 43. (Read 128443 times)

legendary
Activity: 1386
Merit: 1004
August 10, 2011, 03:54:45 PM
#91
How many blocks have been solved?? It keeps downloading and downloading to no end.

It is going to take a bit to download those 580,000 already mined ixcoins.
sr. member
Activity: 266
Merit: 251
August 10, 2011, 03:52:18 PM
#90
So I generated my first 2 blocks less than a second apart.

Why do you say "16*6=96 IXC" when "96 IXC" would suffice¿?¿ 16*6 means nothing as far as i can tell

16*6 is a reference to the X in Ixcoin, as in Hex/Hexadecimal/16.




You're Luke-Jr, aren't you?  This is just another attempt to promote the tonal system.
hero member
Activity: 742
Merit: 500
August 10, 2011, 03:49:10 PM
#89

Also, my math now puts network speed over the 2 GH/s mark. Not a huge amount of interest, but considering this was posed a bit under 3 hours ago and one hour ago was a bit over 1 GH/s... I'm keeping my eye on this one. I still think Namecoin has more promise, since it also fulfills a non-monetary purpose, but I'm keeping my eye on this one.

Nice.  That is 2GH not mining on the bitcoin network.  

Chances are that a substantial portion of that power would not be mining bitcoins anyway. At difficulty 4 you can still CPU mine somewhat effectively. 2 GH/s is what, 10 Radeon 5830s? I get the feeling it's more like a few dozen people on low-end nVidia cards, CPU or throwing one card out of their cluster at the task. Most of this power probably wouldn't be mining bitcoin or namecoin anyway since both have an effective difficulty FAR too high for low-end miners.
member
Activity: 70
Merit: 10
August 10, 2011, 03:47:51 PM
#88
Okay your posting says to use port 8337 but your wiki says use port 8338. Which is it?

Also what is the name of the config file? ixcoin.conf? bitcoin.conf?

Your tutorials dont have proper documentation for anyone to start mining.

How do you expect people to help the project if you don't even have basic documentation?

I'm pretty sure 8337 is for the p2p network and 8338 is for RPC to connect the miner with the daemon.
Also ixcoin.conf.

Edit: Sorry for apparent double posting. There was a post between my 2 responses that has been deleted already.

What would my ixcoin.conf file look like? Post an example please.

rpcuser=youruser
rpcpassword=yourpassword
server=1

and if you want increase your connection limit.
maxconnections=60
I'm just guessing that'd be a good idea in order to decrease rejects because you're more up 2 date with the blockchain.

How many blocks have been solved?? It keeps downloading and downloading to no end.
At the current rate you won't see it "ending" the download. 7418 at the time of writing. They are generated really fast until the difficulty change.
legendary
Activity: 1862
Merit: 1011
Reverse engineer from time to time
August 10, 2011, 03:46:33 PM
#87
How many blocks have been solved?? It keeps downloading and downloading to no end.
legendary
Activity: 3318
Merit: 2008
First Exclusion Ever
August 10, 2011, 03:45:23 PM
#86
*OgNotes exist only in the mind of OgNasty
How would one go about purchasing such mind notes?
hero member
Activity: 602
Merit: 502
August 10, 2011, 03:43:30 PM
#85
Some big company will buy them all and use the currency for internal use. For instance a points or rewards program. Air Miles, maybe.

Like Tim Horton's or Starbucks.

Some big company could just create their own currency.

You just have to open up the source code, choose the amount of coins per block, tweak the genesis block and that's it! You created YouNameItCoins. I can make a GUI to create currencies if you like.

You could even choose 1 million per block. Why wait 4 years anyway?
legendary
Activity: 1386
Merit: 1004
August 10, 2011, 03:43:11 PM
#84

Also, my math now puts network speed over the 2 GH/s mark. Not a huge amount of interest, but considering this was posed a bit under 3 hours ago and one hour ago was a bit over 1 GH/s... I'm keeping my eye on this one. I still think Namecoin has more promise, since it also fulfills a non-monetary purpose, but I'm keeping my eye on this one.

Nice.  That is 2GH not mining on the bitcoin network.  
legendary
Activity: 2492
Merit: 1473
LEALANA Bitcoin Grim Reaper
August 10, 2011, 03:42:43 PM
#83
Okay your posting says to use port 8337 but your wiki says use port 8338. Which is it?

Also what is the name of the config file? ixcoin.conf? bitcoin.conf?

Your tutorials dont have proper documentation for anyone to start mining.

How do you expect people to help the project if you don't even have basic documentation?

I'm pretty sure 8337 is for the p2p network and 8338 is for RPC to connect the miner with the daemon.
Also ixcoin.conf.

Edit: Sorry for apparent double posting. There was a post between my 2 responses that has been deleted already.

What would my ixcoin.conf file look like? Post an example please.
newbie
Activity: 29
Merit: 0
August 10, 2011, 03:42:01 PM
#82
Okay your posting says to use port 8337 but your wiki says use port 8338. Which is it?

Also what is the name of the config file? ixcoin.conf? bitcoin.conf?

Your tutorials dont have proper documentation for anyone to start mining.

How do you expect people to help the project if you don't even have basic documentation?
also 8337 happens to be the bithopper port. couldn't throw it up on my server so i had to bust out a vm.
hero member
Activity: 551
Merit: 500
August 10, 2011, 03:40:46 PM
#81
Okay your posting says to use port 8337 but your wiki says use port 8338. Which is it?

Also what is the name of the config file? ixcoin.conf? bitcoin.conf?

Your tutorials dont have proper documentation for anyone to start mining.

How do you expect people to help the project if you don't even have basic documentation?

ixcoin.conf, point miner to ixcoin.exe, start a solo miner with port 8337. Pretty simple stuff and I have little idea what I'm doing.
hero member
Activity: 742
Merit: 500
August 10, 2011, 03:39:53 PM
#80
Done and done, sir. I can't speak to the purpose but I can speak to the code. A simple KDiff3 comparison of the original bitcoin source and the fork shows very few changes (aside from the obvious bitcoin->ixcoin in nearly every string in every file). The primary change is of course in main.cpp where nSubsidy has been set to 96 and the various necessary changes to the Genesis block have been made. Looks clean to me.

And that is why this is ridiculous. Anyone can change the number of coins per block and announce a new currency. So why? What is the point of creating this?

Well, you'd also have to make the tweaks to create a new genesis block, so at least that part is a bit more difficult than setting nSubsidy = 96.

As for the point, as I said I can't really speak to the purpose other than maybe as an experiment in varying rates of inflation/deflation. It's at least got my attention for its experimental value and I'm considering forking it again to make the ridiculously slow inflation variant I briefly mentioned before... As soon as I wrap my head around the genesis block code anyway Wink

Also, my math now puts network speed over the 2 GH/s mark. Not a huge amount of interest, but considering this was posed a bit under 3 hours ago and one hour ago was a bit over 1 GH/s... I'm keeping my eye on this one. I still think Namecoin has more promise, since it also fulfills a non-monetary purpose, but I'm keeping my eye on this one.
legendary
Activity: 1736
Merit: 1006
August 10, 2011, 03:37:39 PM
#79
Some big company will buy them all and use the currency for internal use. For instance a points or rewards program. Air Miles, maybe.

Like Tim Horton's or Starbucks.
member
Activity: 70
Merit: 10
August 10, 2011, 03:36:03 PM
#78
Okay your posting says to use port 8337 but your wiki says use port 8338. Which is it?

Also what is the name of the config file? ixcoin.conf? bitcoin.conf?

Your tutorials dont have proper documentation for anyone to start mining.

How do you expect people to help the project if you don't even have basic documentation?

I'm pretty sure 8337 is for the p2p network and 8338 is for RPC to connect the miner with the daemon.
Also ixcoin.conf.

Edit: Sorry for apparent double posting. There was a post between my 2 responses that has been deleted already.
member
Activity: 70
Merit: 10
August 10, 2011, 03:31:05 PM
#77
just out of curiosity i pointed my cpu (8mhps) at ixcoin
its been running for about 30 mins now and no block found...whats wrong here?

I'd say it's too slow for single mining (and there are no pools yet for this fork...)
I'm currently mining with 210MH/s and about 50% are getting rejected. It doesn't matter if the difficulty is very low if a new block is found every second and your miner has to start over.

Definitely interesting to see the early block generation in action. I only did pool mining before. But I doubt anyone will use ixcoin. There will be a lot of uses for more forks of bitcoin but right now the first thought is a scam. The community is oversensitive to stuff like that at the moment.
legendary
Activity: 2492
Merit: 1473
LEALANA Bitcoin Grim Reaper
August 10, 2011, 03:30:46 PM
#76
Okay your posting says to use port 8337 but your wiki says use port 8338. Which is it?

Also what is the name of the config file? ixcoin.conf? bitcoin.conf?

Your tutorials dont have proper documentation for anyone to start mining.

How do you expect people to help the project if you don't even have basic documentation?
member
Activity: 98
Merit: 10
August 10, 2011, 03:30:08 PM
#75
Whereas there are currently ~580K Ixcoins (as of 10th August 2011) in existence and it is expected that all 21 million Ixcoins will have been
You announce your project today with ~580K coins already in existence?

A major portion of the 580K IXC have been set aside to promote and develop Ixcoin. For instance, see the Bounties page.
Those bounties sum up to less than 200K. The rest is in your wallet.dat i guess.

Namecoin has at least a real purpose. But this? I don't know. Just because you can mine those coins faster doesn't mean anything. They will just be less worth. The next thing will be OMGcoin , all coins mined within a month.
hero member
Activity: 742
Merit: 500
August 10, 2011, 03:29:02 PM
#74

If you have any doubts as to whether the .exe is compromised, you are welcome to recompile from the source.

Not quite. I would have to INSPECT the source first, and then recompile it.

And you still haven't answered the question: What is the point of this block chain?

Done and done, sir. I can't speak to the purpose but I can speak to the code. A simple KDiff3 comparison of the original bitcoin source and the fork shows very few changes (aside from the obvious bitcoin->ixcoin in nearly every string in every file). The primary change is of course in main.cpp where nSubsidy has been set to 96 and the various necessary changes to the Genesis block have been made. Looks clean to me.
hero member
Activity: 551
Merit: 500
August 10, 2011, 03:28:12 PM
#73
People at 100x the speed you are are the problem
full member
Activity: 172
Merit: 283
Thomas Nasakioto
August 10, 2011, 03:28:07 PM
#72

You seem to have added a get block RPC but apart from that your changes look pretty normal, except that you seem to have neglected to change the four-byte hello sequence that protects each variant from chatting pointlessly with some other variant when people start using patches that allow them to run on non-standard ports.

As long as people stick to the hardcoded networking port, fine. But as soon as some user of mainstream bitcoin hacks his bitcoind to use some weird port that happens to be the port Ixcoin normally uses, you will get told of thousands of nodes all of which will be happy to flood you the same way if your code too is willing to try connecting to a port other than its hardcoded normal port.

So I'd suggest maybe picking a hardcoded hello string for your main net and your test net and get them in use quick before there are so many nodes it is a bit late for such a change.


Good point. We were torn on that one. We didn't change the four-byte hello sequence in the end because we wanted to maximize compatibility with third party Bitcoin apps/websites and minimize adoption difficulty.
Pages:
Jump to: