Pages:
Author

Topic: How do you create an altcoin? - page 13. (Read 21864 times)

member
Activity: 98
Merit: 10
x1 7970 | Aprox. 587 kh/s
April 13, 2013, 05:44:18 PM
#59
Ok, should I just change some numbers and letters in this line?

Code:
32   uint256 hashGenesisBlock("0x12a765e31ffd4059bada1e25190f6e98c99d9714d334efa41a195a7e7e04bfe2");
No!!!. The genesis block process is not as simple as that. You ACTUALLY need to mine it as a regular block. It's also a process that I don't understand. This is probably the thing that will slow you down the most.

Well if i start mining this genesis block am i not just mining litecoins?
full member
Activity: 156
Merit: 100
April 13, 2013, 05:43:11 PM
#58
Ok, should I just change some numbers and letters in this line?

Code:
32   uint256 hashGenesisBlock("0x12a765e31ffd4059bada1e25190f6e98c99d9714d334efa41a195a7e7e04bfe2");
No!!!. The genesis block process is not as simple as that. You ACTUALLY need to mine it as a regular block. It's also a process that I don't understand. This is probably the thing that will slow you down the most.


I did not know this. Looks like I'm goint to learn something today!  Smiley
legendary
Activity: 1862
Merit: 1011
Reverse engineer from time to time
April 13, 2013, 05:41:29 PM
#57
Ok, should I just change some numbers and letters in this line?

Code:
32   uint256 hashGenesisBlock("0x12a765e31ffd4059bada1e25190f6e98c99d9714d334efa41a195a7e7e04bfe2");
No!!!. The genesis block process is not as simple as that. You ACTUALLY need to mine it as a regular block. It's also a process that I don't understand. This is probably the thing that will slow you down the most.
member
Activity: 98
Merit: 10
x1 7970 | Aprox. 587 kh/s
April 13, 2013, 05:41:01 PM
#56
Ive used it before, I have a python script up on mine right now
legendary
Activity: 1862
Merit: 1011
Reverse engineer from time to time
April 13, 2013, 05:40:12 PM
#55
The problem with github, is it's really really hard to use. I am on Windows, and have absolutely no idea how to use it in terms of committing/merging and so on.
hero member
Activity: 632
Merit: 500
April 13, 2013, 05:40:07 PM
#54
Scrypt 'could' make GPUs useless if tuned a certain way.
I remember reading about this in the forums here sometime last year when GPUs started to dominate Litecoin.

What that tuning was, I could not say.


Exactly. Some variable in Scrypt wasn't set high enough. I believe it's the function at line 263 in scypt.c. The "1024", if set higher should render the algorithm hard enough that even GPU couldn't get an advantage. I'm using my very limited knowledge and my memory of what I read though, so I believe I'm 10% correct  Grin
member
Activity: 98
Merit: 10
x1 7970 | Aprox. 587 kh/s
April 13, 2013, 05:38:58 PM
#53
Should I put the binaries and etc. up in this thread when im done?

You should create a github account (it's free I believe) and push your source (and binaries) to your account.
This will be important to keep the project open source and have everything available.

Otherwise you're just creating an RUCoin.

I shall
full member
Activity: 156
Merit: 100
April 13, 2013, 05:37:28 PM
#52
Scrypt 'could' make GPUs useless if tuned a certain way.
I remember reading about this in the forums here sometime last year when GPUs started to dominate Litecoin.

What that tuning was, I could not say.



Interesting, i like the sound of that.
hero member
Activity: 631
Merit: 501
April 13, 2013, 05:37:15 PM
#51
Should I put the binaries and etc. up in this thread when im done?

You should create a github account (it's free I believe) and push your source (and binaries) to your account.
This will be important to keep the project open source and have everything available.

Otherwise you're just creating an RUCoin.
sr. member
Activity: 475
Merit: 255
April 13, 2013, 05:37:09 PM
#50
Lol... people will say all kinds of stuff... I like the thought of exploring the settings for a 'fun coin'.

My guess (and please don't shoot me).... is most of what is needed is in main.cpp as far as default settings go.
Someone with a bit more experience will need to chime in on this one:


32   uint256 hashGenesisBlock("0x12a765e31ffd4059bada1e25190f6e98c99d9714d334efa41a195a7e7e04bfe2");
33   static CBigNum bnProofOfWorkLimit(~uint256(0) >> 20); // Litecoin: starting difficulty is 1 / 2^12

59   int64 nTransactionFee = 0;
60   int64 nMinimumInputValue = CENT / 100;

Block Reward
831  int64 nSubsidy = 50 * COIN;


It seems that everything you need is in main.ccp and main.h. Every other files are "support" files, like to build the keys, define the algorithm and other support functionalities.

As for changing the algorithm, I don't think it's going to be that easy to remove Scrypt and put something else. That Scrypt.c file is scary as hell Cheesy
To be honest I was thinking of doing an alt-coin myself, but ultimately wanted to bring something new on the table in terms of proof-of-work algorithm, as even scrypt proved useless against GPUs.

You can always do a Donkey-Kong proof-of-work :-]]] https://bitcointalksearch.org/topic/m.1812149
member
Activity: 98
Merit: 10
x1 7970 | Aprox. 587 kh/s
April 13, 2013, 05:36:53 PM
#49
Ok, should I just change some numbers and letters in this line?

Code:
32   uint256 hashGenesisBlock("0x12a765e31ffd4059bada1e25190f6e98c99d9714d334efa41a195a7e7e04bfe2");
legendary
Activity: 1862
Merit: 1011
Reverse engineer from time to time
April 13, 2013, 05:36:47 PM
#48
Should I put the binaries and etc. up in this thread when im done?
You first need to create a genesis block. Even when I asked I couldn't fully understand the process.
hero member
Activity: 631
Merit: 501
April 13, 2013, 05:35:50 PM
#47
Scrypt 'could' make GPUs useless if tuned a certain way.
I remember reading about this in the forums here sometime last year when GPUs started to dominate Litecoin.

What that tuning was, I could not say.
member
Activity: 98
Merit: 10
x1 7970 | Aprox. 587 kh/s
April 13, 2013, 05:35:13 PM
#46
Should I put the binaries and etc. up in this thread when im done?
legendary
Activity: 1862
Merit: 1011
Reverse engineer from time to time
April 13, 2013, 05:33:06 PM
#45
Lol... people will say all kinds of stuff... I like the thought of exploring the settings for a 'fun coin'.

My guess (and please don't shoot me).... is most of what is needed is in main.cpp as far as default settings go.
Someone with a bit more experience will need to chime in on this one:


32   uint256 hashGenesisBlock("0x12a765e31ffd4059bada1e25190f6e98c99d9714d334efa41a195a7e7e04bfe2");
33   static CBigNum bnProofOfWorkLimit(~uint256(0) >> 20); // Litecoin: starting difficulty is 1 / 2^12

59   int64 nTransactionFee = 0;
60   int64 nMinimumInputValue = CENT / 100;

Block Reward
831  int64 nSubsidy = 50 * COIN;


It seems that everything you need is in main.ccp and main.h. Every other files are "support" files, like to build the keys, define the algorithm and other support functionalities.

As for changing the algorithm, I don't think it's going to be that easy to remove Scrypt and put something else. That Scrypt.c file is scary as hell Cheesy
To be honest I was thinking of doing an alt-coin myself, but ultimately wanted to bring something new on the table in terms of proof-of-work algorithm, as even scrypt proved useless against GPUs.
member
Activity: 98
Merit: 10
x1 7970 | Aprox. 587 kh/s
April 13, 2013, 05:32:35 PM
#44
Im using scrypt so i hope i won't have a problem there Cheesy
hero member
Activity: 632
Merit: 500
April 13, 2013, 05:29:59 PM
#43
Lol... people will say all kinds of stuff... I like the thought of exploring the settings for a 'fun coin'.

My guess (and please don't shoot me).... is most of what is needed is in main.cpp as far as default settings go.
Someone with a bit more experience will need to chime in on this one:


32   uint256 hashGenesisBlock("0x12a765e31ffd4059bada1e25190f6e98c99d9714d334efa41a195a7e7e04bfe2");
33   static CBigNum bnProofOfWorkLimit(~uint256(0) >> 20); // Litecoin: starting difficulty is 1 / 2^12

59   int64 nTransactionFee = 0;
60   int64 nMinimumInputValue = CENT / 100;

Block Reward
831  int64 nSubsidy = 50 * COIN;


It seems that everything you need is in main.ccp and main.h. Every other files are "support" files, like to build the keys, define the algorithm and other support functionalities.

As for changing the algorithm, I don't think it's going to be that easy to remove Scrypt and put something else. That Scrypt.c file is scary as hell Cheesy
member
Activity: 98
Merit: 10
x1 7970 | Aprox. 587 kh/s
April 13, 2013, 05:29:18 PM
#42
I will create a windows binary and a mac if I can. Im just editing files on debian.
legendary
Activity: 1862
Merit: 1011
Reverse engineer from time to time
April 13, 2013, 05:28:27 PM
#41
And we begin diving into the code, ive got my terminal window open and the git repository cloned Cheesy Lets go! Cheesy
Usually when you start making a coin, you have to realize that there are more people on Windows here than on Unix/Unix-like platforms, so a Windows binary is a must. Whereas Linux users can most of the time make;make install it very easily.
member
Activity: 98
Merit: 10
x1 7970 | Aprox. 587 kh/s
April 13, 2013, 05:25:50 PM
#40
And we begin diving into the code, ive got my terminal window open and the git repository cloned Cheesy Lets go! Cheesy
Pages:
Jump to: