Title: coin cloning guide Post by: limar on July 09, 2015, 03:02:59 AM could anyone point how to clone altcoin without having a knowldge of any programming :) heard there is a guide but coudnt find its traces in google.
Title: Re: coin cloning guide Post by: notlist3d on July 09, 2015, 03:20:38 AM What is your goal?
Most coin's that just change like picture and name are literally worth nothing, or close to nothing. Title: Re: coin cloning guide Post by: limar on July 09, 2015, 03:25:04 AM What is your goal? Most coin's that just change like picture and name are literally worth nothing, or close to nothing. want to be in queue of scam dev :) fiest want to learn how this thing works and better understanding of the crypto programming just for sake of curiosity. Title: Re: coin cloning guide Post by: notlist3d on July 09, 2015, 04:50:17 AM What is your goal? Most coin's that just change like picture and name are literally worth nothing, or close to nothing. want to be in queue of scam dev :) fiest want to learn how this thing works and better understanding of the crypto programming just for sake of curiosity. You will find no one who will help to be in "scam dev". Or at least I hope you do not. Title: Re: coin cloning guide Post by: muddafudda on July 10, 2015, 02:03:59 PM Here you go.
1. Pre Installers.
3. Download and Compile QT. 4. The Clone
6. Connecting your nodes.
7. Checkpointing the premine. 8. Clean up You Code. 9. Compiling Clonecoind.
10. Github for release, made easy.
11. Common Errors 12. Quick Logos 13. The Website.
1. Pre Installers. 1a.1a. File Compressor/Extractor Download and install Winrar or an alternate file compression tool. http://www.rarlab.com/download.htm (http://www.rarlab.com/download.htm) 1b. Text Editor. Download and install a text editor such as Sublime Text (http://www.sublimetext.com/). You need a text editor that can easily search and replace case sensitive text. 1c. Download and install MingW http://sourceforge.net/projects/mingw/files/Installer/mingw-get-setup.exe/download (http://sourceforge.net/projects/mingw/files/Installer/mingw-get-setup.exe/download) Double click to install, keep the checkbox for the GUI checked and make sure to install in C:\MinGW. Press continue. From the MinGW GUI interface, go to all packages -> MYSYS Right click on the following installations and mark for installation. msys-base-bin (may highlight other checkboxes which is fine) msys-autoconf-bin msys-automake-bin msys-libtool-bin Click on Installation -> Apply changes. MinGW will now download the remaining packages. Make sure to remove any previous installs of MinGW before starting. Once complete, navigate to C:\MinGW\bin and you should only have a mingw-get application. If you have msys-gcc and msys-w32api you need to delete MinGW and check the correct install packages are selected above. Download and extract mingw32 to C:\mingw32 http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.9.1/theads-posix/dwarf/i686-4.9.1-release-posix-dwarf-rt_v3-rev1.7z/download (http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.9.1/theads-posix/dwarf/i686-4.9.1-release-posix-dwarf-rt_v3-rev1.7z/download) You now need to change the path variables. Go to control panel->system and security->system. Click on advanced system properties->environmental variables. In the top box navigate to PATH and change to Code: C:\mingw32\bin;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\ Checking your MingW install. To start the MingW app navigate to C:\MinGW\msys\1.0\msys.bat, create a desktop shortcut as you will use the msys command as well as the windows command prompts. Double click to start and enter the following to display the version and correct paths. Code: gcc -v Your msys output should look like the following code. Code: $ gcc -v If you are having issues I have uploaded a MinGW install here (https://howtocloneanaltcoin.com/downloads/MinGW.rar) 2. Download and Install Dependencies. Create a deps folder at C:\deps. If you want to cheat you can download the pre-built dependencies here (http://www.mediafire.com/download/y89546s65sf8de5/deps.zip), though it is recommended to build your own. 2a. OpenSLL- Install OpenSSL dependencies on Windows. Download the latest version of OpenSSL https://www.openssl.org/source/openssl-1.0.1j.tar.gz (https://www.openssl.org/source/openssl-1.0.1j.tar.gz) to your deps folder. Open the MinGW shell at C:\MinGW\msys\1.0\msys.bat Code: cd /c/deps/ 2b. Berkeley DB Download http://download.oracle.com/berkeley-db/db-4.8.30.NC.tar.gz (http://download.oracle.com/berkeley-db/db-4.8.30.NC.tar.gz) and place in your deps folder. In the MinGW shell use the following code. Code: cd /c/deps/ 2c. Boost Download Boost to your deps folder. http://sourceforge.net/projects/boost/files/boost/1.55.0/boost_1_55_0.zip/download (http://sourceforge.net/projects/boost/files/boost/1.55.0/boost_1_55_0.zip/download) Make sure to download either the 7z or zip versions. Double click on the folder to extract boost_1_55_0 in your deps folder. This may take several minutes depending on your PC's speed. Using the Windows command prompt, bootstrap and compile boost. To bring up the windows command prompt just type cmd in the windows search bar. Code: cd C:\deps\boost_1_55_0\ 2d. Mini UPNP Download and extract MiniUPNP http://miniupnp.free.fr/files/download.php?file=miniupnpc-1.9.20140911.tar.gz (http://miniupnp.free.fr/files/download.php?file=miniupnpc-1.9.20140911.tar.gz) to your deps folder. Rename folder from "miniupnpc-1.9.20140911" to "miniupnpc" then from a Windows command prompt: Code: cd C:\deps\miniupnpc 2e. Protoc and Libprotobuf: Download and extract http://protobuf.googlecode.com/files/protobuf-2.5.0.zip (http://protobuf.googlecode.com/files/protobuf-2.5.0.zip) to your deps folder. In the msys shell run Code: cd /c/deps/protobuf-2.5.0 2f. libpng Download and extract http://prdownloads.sourceforge.net/libpng/libpng-1.6.14.tar.gz?download (http://prdownloads.sourceforge.net/libpng/libpng-1.6.14.tar.gz?download) to your deps folder. Extract. In msys shell run Code: cd /c/deps/libpng-1.6.14 2g. qrencode Download and extract http://fukuchi.org/works/qrencode/qrencode-3.4.4.tar.gz (http://fukuchi.org/works/qrencode/qrencode-3.4.4.tar.gz) to your deps folder. In msys shell run Code: cd /c/deps/qrencode-3.4.4 3. Download and Compile QT. Download and uncompress http://download.qt-project.org/official_releases/qt/4.8/4.8.6/qt-everywhere-opensource-src-4.8.6.zip (http://download.qt-project.org/official_releases/qt/4.8/4.8.6/qt-everywhere-opensource-src-4.8.6.zip) to C:\Qt\4.8.6. Once again check it resides in C:\Qt\4.8.6 not C:\Qt\4.8.6\4.8.6. Due to a bug in 4.8.6 you will need to apply the patch available here (https://codereview.qt-project.org/#/c/84567/3/tools/configure/configureapp.cpp). For those who can't find or work it out, you need to change the following lines in C:\Qt\4.8.6\tools\configure\configureapp.cpp or download the patched file here (https://www.mediafire.com/?y4urdzfp0k0j0gm) and replace it in C:\Qt\4.8.6\tools\configure\configureapp.cpp Code: 2180 | - const QString mingwPath = dictionary["QMAKESPEC"].endsWith("-g++") ? From your Windows command prompt run Code: cd C:\Qt\4.8.6 Now we are ready to start the cloning process. If you are worried about compilation, it would be wise to jump ahead and ensure everything is working with compiling the client before working with the clone. 4. The Clone In this guide we will be cloning Litecoin. Litecoin is a Scrypt based coin and the original altcoin. I will be calling this coin Clonecoin (CLN). 4a. Download and extract the Litecoin source. https://github.com/litecoin-project/litecoin (https://github.com/litecoin-project/litecoin). In this guide I will be placing the source code in C:\Clonecoin Copy and Replace Litecoin Using your test editor, search out and replace all instances of Litecoin with Clonecoin. Make sure your search is case sensitive and search for all instances Litecoin with Clonecoin, litecoin with clonecoin etc. Run a search without case sensitivity before continuing to ensure you have all instances. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/61a9b7b8ea5db179b30f979d109847e473d0de81 (https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/61a9b7b8ea5db179b30f979d109847e473d0de81) 4c. Copy and Replace LTC. Using your test editor, search out and replace all instances of LTC with CLN. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/7b6a2ad68deb97caab802c460ebfe5104fa72e2c (https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/7b6a2ad68deb97caab802c460ebfe5104fa72e2c) 4d. Change rpc and port numbers. Search for an appropriate port and rpc number http://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers (http://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers). Litecoin uses port 9333 testnet 19333, rpcport 9332 testnet 19332. We will change them to port 10333 testnet 11333, rpcport 10332 testnet 11332 https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/7f149b069f77b3e174ca8a7b10b98287c3e663a9 (https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/7f149b069f77b3e174ca8a7b10b98287c3e663a9) 4e. Change starting letter for addresses. In this case we change the 48 to 28, therefore all addresses will start with C. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/d0621b86a358e93495658d564640144458aab8ee (https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/d0621b86a358e93495658d564640144458aab8ee) 4f. Update client version number. Since its really a fork of Litecoin we will bring the version numbers up to 1.0.0.0. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/95d0bef6e6a7bf27f3ed6d8153fccf8275524ba9 (https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/95d0bef6e6a7bf27f3ed6d8153fccf8275524ba9) 4g. Change Litecoin example addresses to Clonecoin Addresses. Here we change the LTC addresss Ler4HNAEfwYhBmGXcFP2Po1NpRUEiK8km2 to a Clonecoin mystery address starting with c. (see step 6d) https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/9a5321bfb9b0482ed3b435edb815d8eee268b949 (https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/9a5321bfb9b0482ed3b435edb815d8eee268b949) 4h. Change char pchMessageStart and ParseHex. We want these to be unique to Clonecoin. Be wary of changing pchMessageStart to to letters other than a-f. All numbers are fine to use. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/011b9a8e713821d8010a827f7aeacf09c772a267 (https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/011b9a8e713821d8010a827f7aeacf09c772a267) 4i. Change alert keys. We just change these to be different from Litecoin to avoid the Litecoin messages. I will link another guide here on how they work when complete and how to use them. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/0798f246007c9196bcfcf39c2ef2222a660d59d2 (https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/0798f246007c9196bcfcf39c2ef2222a660d59d2) 4j. Remove Merkel root and Genesis Block. These will be replaced later on though for now and in the near future they are no longer needed. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/46bbcb1377ac2db0f8dabc19faffb9ab6f989cb6 4k. Remove Nonce and testnet genesis. We remove the testnet genesis block and nonce. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/24cf6793c02369fc60a8b67645818f0cf7d1252a 4l. Add Epoochtime and Timestamp. To create a genesis block we need an epoochtime and verbal timestamp. The current epoochtime can be found http://www.epochconverter.com/ (http://www.epochconverter.com/) and find the latest news headline for your verbal timestamp. We also replace the testnet timestamp. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/790f9964abdb0543abe1ee1801562a004349e719 4m. Fixing the checkpoints. We comment out the hardcoded checkpoint and change the genesis block checkpoint. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/fe0d86a278f4d6470bee697a25256b0340cfc9fd 4n. Change max money supply and coinbase maturity. We just multiplied total coins by 10 and reduced coin based maturity. The higher the number of confirmations the better for the network. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/c43361429062f04b5697f9e9fca19e2f15d2e634 4o. Change block times from 2.5 minutes to 30 seconds. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/8796946bd1d3d5d15d06ba0e72e4b6bbf1fe1d06 4p. Change re-targeting from the ridiculous 2.5 days to every 5 minutes. This is cutting out a small portion of instamining. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/a3df6e9dc15009bdb22c60a496c109334cc55864 4q. Add premine and change block rewards. Since we initially increased block rewards by x10, we will increase the base reward from 50 to 500. We then add a premine on block 2 as well as a staggered decrease in block sizes. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/ddc36732b46fbc38ca06012be127ff994177192d 4r. Update Images. If you have not already, you will need a splash and logo. You will need to update src/rec/icons- bitcoin.png, bitcoin_testnet.png, bitcoin.icon, bitcoin_testnet.icon all 256x256 pixels. toolbar.png and toolbar_testnet.png to 16x16 pixels. also update src/res/images splash.png, splash_testnet.png and about.png. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/08edb2f2648acc373e60c44fbd0558c514697ff7 4s. Update Seed node- First you will need to create a dedicated node. This is a quick easy guide. Head to https://console.aws.amazon.com and create an account. Click on the EC2 link on the left. AWS pricing can be found http://aws.amazon.com/ec2/pricing/ Create and instance, select Microsoft Windows Server 2012 R2 Base, select your server preference- we chose t2.micro which is free tier eligible. Click Next: Configure Instance Details, highlight Protect against accidental termination, click review and launch. Go to security settings, open all ports and click launch. Create a security key pair and make sure to download it and keep it safe. Launch your instance. On the aws instance home screen click the Elastic IP tab, click allocate Ip address and confirm. While still in the Elastic IP tab, click allocate and allocate to the instance by clicking the top checkbox and identifying your server. Confirm. Your instance will take around 15 minutes to launch. To connect. Click the instance tab, highlight your instance and press connect. Using your key from earlier, you are now able to download a server shortcut and server password. Using your new Elastic IP, replace your new IP removing Litecoin old seed nodes. src/net.cpp Code: static const char *strMainNetDNSSeed[][2] = { 4.t Change the name of the bitcoin-qt.pro file to clonecoin-qt.pro https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/d309822b3b6519ca6424ac74df054ad351db1d88 5. Hashing the Genesis Block and Merkel Root. 5a. Ability to hash Genesis Block.We now need to add the ability to hash a new genesis block so we add the following code to main.cpp. main.cpp Code: if (true && block.GetHash() != hashGenesisBlock) 5b. Compiling Clonecoin Windows QT. Create libleveldb.a and libmemenv.a. Using Msys shell, run. For this we have Clonecoin in C:/Clonecoin Code: cd /C/clonecoin/src/leveldb Open your Clonecoin-qt.pro file. We now need to change the dependency directory locations Code: # Dependency library locations can be customized with: Code: # Dependency library locations can be customized with: Code: genleveldb.commands = cd $$PWD/src/leveldb && CC=$$QMAKE_CC CXX=$$QMAKE_CXX $(MAKE) OPT=\"$$QMAKE_CXXFLAGS Code: #genleveldb.commands = cd $$PWD/src/leveldb && CC=$$QMAKE_CC CXX=$$QMAKE_CXX $(MAKE) OPT=\"$$QMAKE_CXXFLAGS Add to Code: CONFIG += static Code: CONFIG += thread and Code: win32:QMAKE_LFLAGS *= -Wl,--large-address-aware Code: win32:QMAKE_LFLAGS *= -Wl,--large-address-aware -static Now from a the Windows cmd, run Code: set PATH=%PATH%;C:\Qt\4.8.6\bin Your Clonecoin qt should now be available in your C:\clonecoin\release folder after around 5 minutes. If errors occur, scroll up and read them try to identify and fix. 5c. Generating Merkel Root Start your Clonecoin-qt. You should see an error Assertion failed! Navigate to your Clonecoin appdata folder C:\Users\(YOUR*PC*NAME)\AppData\Roaming\Clonecoin and open the debug log in a text editor. The folder is hidden by default, so typing %appdata% in the Windows search bar will bring up access to the roaming\clonecoin folder. Scroll to the bottom of the text to find the following lines. Code: 2014-11-06 17:00:04 LoadBlockIndexDB(): last block file = 0 The bottom hash is the merkel root, we take this and add it to main.cpp Code: assert(block.hashMerkleRoot == uint256("0xd010ddcc6651af0e28e50ee36096e438b7974da9d58f1be95a968b180756a0c8")); https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/c776fb6da5599cc9a3bde9749880d9a1f9a1222a 5d. Hashing the Genesis Block. We now need to recompile the client in Windows cmd. You can remove the path and directory if you still have the client open. Code: set PATH=%PATH%;C:\Qt\4.8.6\bin Restart the client. The previous Merkel error should not occur and the client should appear to hang on launch. It is now hashing your genesis block. How long this takes can vary from a few seconds to minutes. Once the client hangs with a genesis block error, open your debug text file again in your Clonecoin appdata folder C:\Users\(YOUR*PC*NAME)\AppData\Roaming\Clonecoin Code: 2014-11-05 18:29:11 block.nNonce = 2110551 We will now add these to main.ccp. Code: @@ -35,7 +35,7 @@ CTxMemPool mempool; Recompile the Windows QT. From the Windows cmd, run Code: set PATH=%PATH%;C:\Qt\4.8.6\bin Your Clonecoin qt should now be available in your C:\clonecoin\release 6. Connecting your nodes. Now you have your client we need to connect the nodes to check everything is working. You can use testnet though its just as easy to use mainnet. Connect to your server we set up earlier or use another local machine. 6a. Create a conf. file. We only create this now to enable mining to check the network. Your conf. file should be placed in C:\Users\(YOUR**PC**NAME)\AppData\Roaming\clonecoin. To create a conf file, right click->new->text document. Copy and paste the code below replacing a suitable username and password. Click save, change file type to all and save as clonecoin.conf. Or just download this one. (https://www.mediafire.com/?taozsy80yaay1bz) Code: rpcuser=Yourusername 6b. Connect Server- upload your client to the server and start the client. The two clients should connect. Home Network- you may need to add your local ip's to the conf file. To do this type cmd to bring up command prompt, type ipconfig and use the IPv4 address in your addnodes from both machines. Code: rpcuser=Yourusername Once both clients are connected you can start to mine blocks. You can either use the traditional Scrypt miner or type setgenerate true-1 into your main console. Mine as many blocks as you want, checking diff adjustment and ensure block rewards are correct. It is advised to confirm some transactions, send some coins and check the client for any errors or adjustments. In this case I missed the toolbar.png and testnet_toolbar.png as a deliberate example of why you "SHOULD ALWAYS CHECK YOUR CLIENT BEFORE RELEASE" If you want to restart the chain you need to delete the chain by going to your Clonecoin roaming folder on both machines and deleting everything. 7. Checkpointing the premine. If you followed all the steps above you should be sitting with a lovely source code and compiled client. We have a few things to finish and checkpointing the premine is highly important. Many coin launches have been lost by people not knowing or forgetting to do this step. Without a premine you can very likely kiss your premine goodbye to a hash attack on launch. Start your compiled clients on both machines. Since we deleted the blockchain earlier mine your premine, plus 2-3 blocks. Open the concole on the clonecoin client and type getblockhash 1, getblockhash 2, getblockhash 3. We will use these three hashes to checkpoint the premine. We also need some data from the C:\Users\(YOUR**PC**NAME)\AppData\Roaming\clonecoin\debug file. We are looking for the details of the highest checkpointed block, in this case block 3. Code: 2014-11-11 15:02:57 SetBestChain: new best=718732cb3323ceaa46c8fc5fd521e7f7e31e424c59cc2a02e4e39c2c7306a649 [b]height=3[/b] log2_work=22.000022 [b] tx=4 [/b] date=2014-11-11 15:02:57 progress=1.000000 Now we add the block hashes for blocks 1, 2 and 3 and insert the highest block (block 3) details into the checkpoint block details. We also add the estimated number of transactions per day after the checkpoint. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/d5e61c1d0e7678cc165acf9dc1a27c6d23200030. Recompile you client. Back up your C:\Users\(YOUR**PC**NAME)\AppData\Roaming\clonecoin folder. This now has your premine. You now need to check the checkpoints are correct. On the client that does not have the premine, navigate to C:\Users\(YOUR**PC**NAME)\AppData\Roaming\clonecoin and delete all contents besides your wallet.dat(Very Important Do NOT DELETE) and clonecoin.conf files. Restart the client. If your checkpoints are correct the client should update and sync without issues. 8. Clean up your code. Clean up your read me with your new specifications, rewards, website etc. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/13fc52d07ed55d5b95071a043e88b13a6ad92a67 Remove your build deps and changes from clonecoin-qt.pro https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/437d50f106d588edd95fd35eec06b2da7cf3d49e 9. Compiling Clonecoind. Navigate to C:\clonecoin\src\makefile.mingw and open with your text editor. Code: USE_UPNP:=- Code: USE_UPNP:=1 We change the deps to point to the deps we created earlier. If you chose to place your deps in a different folder, change the code to point to your folders. We also -static to LDFLAGS=-Wl,--dynamicbase -Wl,--nxcompat -Wl,--large-address-aware -static for static linked exe, updated UPNP Includes and Lib paths to enable UPNP. In the Msys shell, you can now compile litecoind. Code: cd /c/clonecoin/src Your clonecoind should now be in your C:\clonecoin\src folder. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/6b124d98f059fb42b2b8837b520b6a626ec6f5ef 9b. Remove libleveldb.a and libmemev.a from C:\Clonecoin\src\leveldb. Remove your clonecoin-qt from the release folder and zip for release. Delete the release, debug and build folders. This is your code for release. 10. Github for release, made easy. 1. Create a Github account. 2. Download the latest Github Windows client https://windows.github.com/ (https://windows.github.com/) Run the Github install and use your log in details from Github to log into the client. 3. Navigate to you Github account, click repositories->new. Enter the repository name, description and public or private. Public allows everyone to see your code and is recommended for advanced users who can push codes quickly. Most launches will choose a paid private account, allowing them to pre-load the release source code and open the repository from public to private instantly. Click done, then on the next screen click the green Set up in Desktop button. Allow the browser to launch the Github client, select the location of your Github depositories, usually in the Github folder of your documents. Click ok. You now have a folder that you can update your source code and easily push commits to Github. 10a. Easy Pushing Commits/Launch Code. Copy and paste your source code into the documents/github/yourcoinnamefolder. In your Windows Github client, click on your client name on the left hand side. You Github client should recognise a host of changes if present. Fill in the commit details, select the files that need to be committed, usually all and on by default and press commit. On the top right hand side will be a publish or sync box, click that and the Github Windows client will push the changes and source code to your repository on Github. 10b. Easy Revert Commits. Open your Github client and ensure its sync'd. Highlight your repository. Click on the commit to you wish to rollback, then revert. On the top right hand side will be a publish or sync box, click that and the Github Windows client will push the revert to your repository on Github. 10c. Easy Pushing Updates. Log into your Github Windows client. Click on the altcoin tab in the left and click sync to ensure your local code is up to date. Edit your local code in your documents/github/yourcoinname folder. Once your Github client picks up the changes enter the commit details and commit to Github. 11. Common Errors/Mistakes. I am getting "this" error. Most errors can be solved with a little effort. The compiler will usually display an error message or warning. Read it. If it's UPNP error check your directories in your pro file, then check your UPNP deps, rebuild them. Google it. Most things can be solved far quicker with a little investigation into the errors vs posting in a forum and awaiting reply. I am still seeing the old logos on my desktop shortcuts. Windows cache has cached the image. The easiest way to solve this is run a program such as Glarys Utilities to clear your PC. Also delete the build folder in between builds to ensure your builds are clean. [c]Makefile.Release:291: recipe for target 'release\clonecoin-qt.exe' failed Close your client. 12. Creating your own logo. There are a few easy ways to get a logo. If you have Photoshop and want a easy template try http://apsdfile.com/coin-generator-for-photoshop/ (http://apsdfile.com/coin-generator-for-photoshop/). Install GIMP. GIMP is a free utility available to download from http://www.gimp.org/ (http://www.gimp.org/) and try youtube vids. For those looking for an even faster alternative try tools like http://www.onlinebadgemaker.com/3d-badge-maker (http://www.onlinebadgemaker.com/3d-badge-maker). These can be used for quick launches or temporary images while you wait, purchase or make an official one. 13. The Website. 13a. The Template. Download and install a free website editor. Bluegriffon is a prime example. http://bluegriffon.org/. Find yourself a suitable template at http://www.freshdesignweb.com/free-html5-css3-templates.html. Download and edit the template with all your coin details. 13b. Upload to a website. Create an account at NAMECHEAP (http://www.namecheap.com/?aff=76726), Namecheap (http://www.namecheap.com/?aff=76726) accept BTC and have the most awesome support. Register your domain and hosting at the same time. That way there is no DNS delay. Usually you can pick up a year hosting with domain and ssl if you want for under .15BTC. O may add installing an ssl cert later. If this is a one off coin launch a simple hosting plan will suffice, if your looking to launch more coins, choose a dedicated server or reseller plan. Find more at Namecheap. (http://www.namecheap.com/?aff=76726) Once your order is confirmed log into cpanel with the details provided, enable cloudflare and ssl of you purchased it. Single hosting plans will require support for ssl, dedicated or reseller accounts have the ability to self enable through WHM. In CPanel, go to file manger and upload your site to the public_html folder. Your website should be now viewable on your domain. 14. The Launch. Ninja vs Pumped vs ICO. Launching a coin is the make or break point. Depending on the style of launch will dictate how you prepare. 14a. Prelaunch. The key to a good launch is timing and consistency. Don't release the code early and make sure it works. Create your Bitcointalk account. The earlier the better to get rid of posting restrictions on new accounts. Create accounts on Twitter, Facebook, cryptocointalk, IRC, Reddit and all the usual channels. 14b. The Ninja- This gives the developer more time, no restrictions with no one looking or ready. With these coins you can set the network up early and don't have people looking for the code. Uploading the code to github a minute easily will likely be enough time to stop anyone searching. Website can go live early and some argue it gives miners a better chance. Usually a ninja launch involves a instamine allowing the developers to mine many blocks. 14c. The Pumped. Harder to do. The pre-hype means you will have people looking for the code on Github and websites. Your code needs to be solid to handle a massive intake of hashing power and be prepared for the harshest critics. 14d. The ICO. An advanced pump coin that needs a reliable escrow, good hype and delivery of goods. Most ICO's deliver nothing but BTC to the developer and broken promises to the users. Find a good escrow, take time with your code and remember to keep an open and clear communication. Title: Re: coin cloning guide Post by: bram_vnl on July 10, 2015, 02:11:10 PM respect for all the devs that is a lot of work pff
Title: Re: coin cloning guide Post by: muddafudda on July 10, 2015, 02:18:12 PM respect for all the devs that is a lot of work pff Once you get it nailed you can pull off the whole process in 1-3 hours including site, client, source, social media, seed nodes etc. Title: Re: coin cloning guide Post by: sdmathis on July 10, 2015, 03:40:10 PM respect for all the devs that is a lot of work pff That's just for cloning a coin. If you want to implement any new features, there's a lot more work. Actually, developing a coin (rather than just making a copy and paste clone) is a never-ending and thankless job. Title: Re: coin cloning guide Post by: muddafudda on July 10, 2015, 04:30:43 PM respect for all the devs that is a lot of work pff That's just for cloning a coin. If you want to implement any new features, there's a lot more work. Actually, developing a coin (rather than just making a copy and paste clone) is a never-ending and thankless job. Yes. 99% of dev work goes unrewarded. Title: Re: coin cloning guide Post by: bit1 on July 10, 2015, 05:56:03 PM Interesting,
Somebody have tried Qt 5.5.0 I hear that some changes need be done to compile. Title: Re: coin cloning guide Post by: limar on July 11, 2015, 07:58:33 PM that is amazing for a noob like me its a work for a month but will definately do this and muddafudda appreciate your assistance and help for this guide
Title: Re: coin cloning guide Post by: J1mb0 on July 11, 2015, 08:42:50 PM that is amazing for a noob like me its a work for a month but will definately do this and muddafudda appreciate your assistance and help for this guide This guide is famous (kudos to Mudda) - I am suprised you couldn't find it. Title: Re: coin cloning guide Post by: limar on July 11, 2015, 08:45:16 PM that is amazing for a noob like me its a work for a month but will definately do this and muddafudda appreciate your assistance and help for this guide This guide is famous (kudos to Mudda) - I am suprised you couldn't find it. do you have a link to site i found one for foocoin but it seems that is not working bcoz spent amost 5 days and later someone told me its obsolete Title: Re: coin cloning guide Post by: X68N on July 11, 2015, 11:53:18 PM respect for all the devs that is a lot of work pff That's just for cloning a coin. If you want to implement any new features, there's a lot more work. Actually, developing a coin (rather than just making a copy and paste clone) is a never-ending and thankless job. Yes. 99% of dev work goes unrewarded. That's what why i made a thread, what is your reason being a dev? :) https://bitcointalk.org/index.php?topic=1100446.msg11735245 greetings Title: Re: coin cloning guide Post by: MicroGuy on July 12, 2015, 01:17:43 AM respect for all the devs that is a lot of work pff That's just for cloning a coin. If you want to implement any new features, there's a lot more work. Actually, developing a coin (rather than just making a copy and paste clone) is a never-ending and thankless job. Yes. 99% of dev work goes unrewarded. That's what why i made a thread, what is your reason being a dev? :) https://bitcointalk.org/index.php?topic=1100446.msg11735245 greetings There is a rare breed of idealists (people with food and shelter already covered) that are dedicated to advancing the power and freedom of mankind. Out of this small group there is an even smaller group of developers, and out of that group a handful of altcoin developers. Find the handful, embrace the handful. Title: Re: coin cloning guide Post by: limar on July 12, 2015, 02:00:46 AM respect for all the devs that is a lot of work pff That's just for cloning a coin. If you want to implement any new features, there's a lot more work. Actually, developing a coin (rather than just making a copy and paste clone) is a never-ending and thankless job. Yes. 99% of dev work goes unrewarded. That's what why i made a thread, what is your reason being a dev? :) https://bitcointalk.org/index.php?topic=1100446.msg11735245 greetings There is a rare breed of idealists (people with food and shelter already covered) that are dedicated to advancing the power and freedom of mankind. Out of this small group there is an even smaller group of developers, and out of that group a handful of altcoin developers. Find the handful, embrace the handful. like your statement Find the handful, embrace the handful and one emerging member of this handful group is at your service :D Title: Re: coin cloning guide Post by: kevin1234a on July 12, 2015, 03:24:58 AM interesting guide but remember you guys need to have zlib and gcc compiler to build qrencode and can be installed it in mingw32 initial libraries selection
Title: Re: coin cloning guide Post by: benthach on July 12, 2015, 04:31:04 AM could anyone point how to clone altcoin without having a knowldge of any programming :) heard there is a guide but coudnt find its traces in google. pm bobsurplus for it. chance his team can creating you one for 0.69btc, basically it's just a copy and paste. this guy hang around CIRC right now. Title: Re: coin cloning guide Post by: muddafudda on July 12, 2015, 02:25:07 PM interesting guide but remember you guys need to have zlib and gcc compiler to build qrencode and can be installed it in mingw32 initial libraries selection Hmm, you must have missed this work around for it. In this guide I didn't build the gcc+ compiler into the MingW base, we use a work around. 2 years ago I would have used that approach but do not anymore. Download and extract mingw32 to C:\mingw32 http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.9.1/theads-posix/dwarf/i686-4.9.1-release-posix-dwarf-rt_v3-rev1.7z/download (http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.9.1/theads-posix/dwarf/i686-4.9.1-release-posix-dwarf-rt_v3-rev1.7z/download) You now need to change the path variables. Go to control panel->system and security->system. Click on advanced system properties->environmental variables. In the top box navigate to PATH and change to Code: C:\mingw32\bin;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\ Title: Re: coin cloning guide Post by: dirranbandi on July 29, 2015, 02:37:01 AM I'm amazed by this tutorial, I'm really grateful!!
The current (master) version of litecoin is slightly different from the one used in this tutorial. Anybody knows which is the version of litecoin used in this tutorial? I'd like to use the same... Thanks :) Title: Re: coin cloning guide Post by: murderouskirk on July 29, 2015, 08:51:36 AM Everything you should need in one place. (https://bitcointalk.org/index.php?topic=1060540.0)
The one posted earlier in this thread is the "How to Clone Litecoin- Scrypt Coins- Windows 32 bit Litecoind and Litecoin Cloning Guide. (https://www.brocksmash.com/guide/how-clone-litecoin-scrypt-coins-windows-32-bit-litecoind-and-litecoin-cloning-guide)" link in my thread. Took me a long time to pull that together. Information on this stuff is not typically shared. Not all of it will be 100% spot on for your project. But between them all you should be able to get the job done. Don't be afraid to jump into other links when you get stuck. Odds are the answer is in another castle. If you find it helpful bump the post. Amazingly it's seen extremely little attention. I urge you to figure out your moral line before you start and stick to it once you launch. Many find that once they learn how to clone their desire to make btc outweighs their desire to make something people might like to trade and shitcoins backed by nothing but lies results. Your clone doesn't have to be innovative, but please don't try to trick people into believing it's more than what it is. Title: Re: coin cloning guide Post by: markm on July 29, 2015, 08:53:30 AM That stuff should all be macros / constants / config-file settings, so folks don't have to touch the code to change it all.
Would make it much easier for folks to keep their shitcoins up to date with the latest bitcoin code. -MarkM- Title: Re: coin cloning guide Post by: kevin1234a on July 31, 2015, 02:33:42 AM and it is getting interesting day by day, thanks to u all legends out there.
Title: Re: coin cloning guide Post by: Sumo on July 31, 2015, 02:35:51 AM Wow makes your head spin. Yeah mad props to the coin devs out there. ??? :o ???
Title: Re: coin cloning guide Post by: hendra147 on July 31, 2015, 02:41:13 AM better to buy these coins
I see some sites provide manufacturing coins including block and richlist ::) Title: Re: coin cloning guide Post by: derrend on April 02, 2016, 10:09:35 PM You can create altcoins on the fly using git and docker:
https://github.com/derrend/bitcoinclone Title: Re: coin cloning guide Post by: hsnbrg on November 07, 2016, 09:49:05 PM 7. Checkpointing the premine. ... Recompile you client. Back up your C:\Users\(YOUR**PC**NAME)\AppData\Roaming\clonecoin folder. This now has your premine. You now need to check the checkpoints are correct. On the client that does not have the premine, navigate to C:\Users\(YOUR**PC**NAME)\AppData\Roaming\clonecoin and delete all contents besides your wallet.dat(Very Important Do NOT DELETE) and clonecoin.conf files. Restart the client. If your checkpoints are correct the client should update and sync without issues. On this step, I got "wallet.dat corrupt, salvage failed" message on the client (the one that does not have the premine. I deleted all files except fcoin.conf and wallet.dat). I did everything as marked. However, my premined coins are still immature at this point. Is this right? Does it worth to checkpoint blocks that are not yet matured? Or I need to wait for them to be matured, and include the first 40-50 blocks in the checkpoint.cpp? Title: Re: coin cloning guide Post by: Table8 on June 06, 2017, 11:00:28 AM Quote Now from a the Windows cmd, run Code: C:/mingw32/bin/../lib/gcc/i686-w64-mingw32/4.9.1/../../../../i686-w64-mingw32/bi any idea how to fix? Title: Re: coin cloning guide Post by: pittuk23 on June 23, 2017, 07:24:14 PM Everything you should need in one place. (https://bitcointalk.org/index.php?topic=1060540.0) The one posted earlier in this thread is the "How to Clone Litecoin- Scrypt Coins- Windows 32 bit Litecoind and Litecoin Cloning Guide. (https://www.brocksmash.com/guide/how-clone-litecoin-scrypt-coins-windows-32-bit-litecoind-and-litecoin-cloning-guide)" link in my thread. Took me a long time to pull that together. Information on this stuff is not typically shared. Not all of it will be 100% spot on for your project. But between them all you should be able to get the job done. Don't be afraid to jump into other links when you get stuck. Odds are the answer is in another castle. If you find it helpful bump the post. Amazingly it's seen extremely little attention. I urge you to figure out your moral line before you start and stick to it once you launch. Many find that once they learn how to clone their desire to make btc outweighs their desire to make something people might like to trade and shitcoins backed by nothing but lies results. Your clone doesn't have to be innovative, but please don't try to trick people into believing it's more than what it is. Hi, link is now gone, do you have a current link? Title: Re: coin cloning guide Post by: lowcost on July 12, 2017, 06:30:32 PM please , someone upload a working link. and can someone code a coin here?
Title: Re: coin cloning guide Post by: maiiyeuchong on November 05, 2017, 06:40:26 PM I need to help. I have created a coin for myself, but when sent, can not receive. Why wallet contacted the system it has multiple ports connected to it
http://fs5.directupload.net/images/171105/uncttku6.png http://fs5.directupload.net/images/171105/i8qqsing.png http://fs1.directupload.net/images/171105/el82all8.png Title: Re: coin cloning guide Post by: Jewelettes on May 26, 2018, 02:28:46 AM Looks like a good guide.
If it's incomplete, then at least there's this starting point. I respect the real devs more. Title: Re: coin cloning guide Post by: GoolGaul on June 17, 2018, 09:37:45 PM Excellently thorough guide here.
2 questions. 1) is this all still current? 2) would this work to clone Verium - which is a cpu only variant of BTC using Scrypt Squared. Looking to build a new coin for CPU-only mining, that will be GPU- and ASIC- resistant. Title: Re: coin cloning guide Post by: glenncoin on August 07, 2018, 11:21:37 PM Hi guys does anyone know where or how to change collateral of Pivx Masternode? I'm trying to find the collateral in its main.cpp but I can't find it.
Title: Re: coin cloning guide Post by: BeeKeyyy on August 10, 2018, 10:20:05 PM Here you go. 1. Pre Installers.
Damn this right here will turn everyone into coin developers lmao 3. Download and Compile QT. 4. The Clone
6. Connecting your nodes.
7. Checkpointing the premine. 8. Clean up You Code. 9. Compiling Clonecoind.
10. Github for release, made easy.
11. Common Errors 12. Quick Logos 13. The Website.
1. Pre Installers. 1a.1a. File Compressor/Extractor Download and install Winrar or an alternate file compression tool. http://www.rarlab.com/download.htm (http://www.rarlab.com/download.htm) 1b. Text Editor. Download and install a text editor such as Sublime Text (http://www.sublimetext.com/). You need a text editor that can easily search and replace case sensitive text. 1c. Download and install MingW /download (http://http[Suspicious link removed) Double click to install, keep the checkbox for the GUI checked and make sure to install in C:\MinGW. Press continue. From the MinGW GUI interface, go to all packages -> MYSYS Right click on the following installations and mark for installation. msys-base-bin (may highlight other checkboxes which is fine) msys-autoconf-bin msys-automake-bin msys-libtool-bin Click on Installation -> Apply changes. MinGW will now download the remaining packages. Make sure to remove any previous installs of MinGW before starting. Once complete, navigate to C:\MinGW\bin and you should only have a mingw-get application. If you have msys-gcc and msys-w32api you need to delete MinGW and check the correct install packages are selected above. Download and extract mingw32 to C:\mingw32 http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.9.1/theads-posix/dwarf/i686-4.9.1-release-posix-dwarf-rt_v3-rev1.7z/download (http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.9.1/theads-posix/dwarf/i686-4.9.1-release-posix-dwarf-rt_v3-rev1.7z/download) You now need to change the path variables. Go to control panel->system and security->system. Click on advanced system properties->environmental variables. In the top box navigate to PATH and change to Code: C:\mingw32\bin;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\ Checking your MingW install. To start the MingW app navigate to C:\MinGW\msys\1.0\msys.bat, create a desktop shortcut as you will use the msys command as well as the windows command prompts. Double click to start and enter the following to display the version and correct paths. Code: gcc -v Your msys output should look like the following code. Code: $ gcc -v If you are having issues I have uploaded a MinGW install here (https://howtocloneanaltcoin.com/downloads/MinGW.rar) 2. Download and Install Dependencies. Create a deps folder at C:\deps. If you want to cheat you can download the pre-built dependencies here (http://www.mediafire.com/download/y89546s65sf8de5/deps.zip), though it is recommended to build your own. 2a. OpenSLL- Install OpenSSL dependencies on Windows. Download the latest version of OpenSSL https://www.openssl.org/source/openssl-1.0.1j.tar.gz (https://www.openssl.org/source/openssl-1.0.1j.tar.gz) to your deps folder. Open the MinGW shell at C:\MinGW\msys\1.0\msys.bat Code: cd /c/deps/ 2b. Berkeley DB Download http://download.oracle.com/berkeley-db/db-4.8.30.NC.tar.gz (http://download.oracle.com/berkeley-db/db-4.8.30.NC.tar.gz) and place in your deps folder. In the MinGW shell use the following code. Code: cd /c/deps/ 2c. Boost Download Boost to your deps folder. http://sourceforge.net/projects/boost/files/boost/1.55.0/boost_1_55_0.zip/download (http://sourceforge.net/projects/boost/files/boost/1.55.0/boost_1_55_0.zip/download) Make sure to download either the 7z or zip versions. Double click on the folder to extract boost_1_55_0 in your deps folder. This may take several minutes depending on your PC's speed. Using the Windows command prompt, bootstrap and compile boost. To bring up the windows command prompt just type cmd in the windows search bar. Code: cd C:\deps\boost_1_55_0\ 2d. Mini UPNP Download and extract MiniUPNP http://miniupnp.free.fr/files/download.php?file=miniupnpc-1.9.20140911.tar.gz (http://miniupnp.free.fr/files/download.php?file=miniupnpc-1.9.20140911.tar.gz) to your deps folder. Rename folder from "miniupnpc-1.9.20140911" to "miniupnpc" then from a Windows command prompt: Code: cd C:\deps\miniupnpc 2e. Protoc and Libprotobuf: Download and extract http://protobuf.googlecode.com/files/protobuf-2.5.0.zip (http://protobuf.googlecode.com/files/protobuf-2.5.0.zip) to your deps folder. In the msys shell run Code: cd /c/deps/protobuf-2.5.0 2f. libpng Download and extract http://prdownloads.sourceforge.net/libpng/libpng-1.6.14.tar.gz?download (http://prdownloads.sourceforge.net/libpng/libpng-1.6.14.tar.gz?download) to your deps folder. Extract. In msys shell run Code: cd /c/deps/libpng-1.6.14 2g. qrencode Download and extract http://fukuchi.org/works/qrencode/qrencode-3.4.4.tar.gz (http://fukuchi.org/works/qrencode/qrencode-3.4.4.tar.gz) to your deps folder. In msys shell run Code: cd /c/deps/qrencode-3.4.4 3. Download and Compile QT. Download and uncompress http://download.qt-project.org/official_releases/qt/4.8/4.8.6/qt-everywhere-opensource-src-4.8.6.zip (http://download.qt-project.org/official_releases/qt/4.8/4.8.6/qt-everywhere-opensource-src-4.8.6.zip) to C:\Qt\4.8.6. Once again check it resides in C:\Qt\4.8.6 not C:\Qt\4.8.6\4.8.6. Due to a bug in 4.8.6 you will need to apply the patch available here (https://codereview.qt-project.org/#/c/84567/3/tools/configure/configureapp.cpp). For those who can't find or work it out, you need to change the following lines in C:\Qt\4.8.6\tools\configure\configureapp.cpp or download the patched file here (https://www.mediafire.com/?y4urdzfp0k0j0gm) and replace it in C:\Qt\4.8.6\tools\configure\configureapp.cpp Code: 2180 | - const QString mingwPath = dictionary["QMAKESPEC"].endsWith("-g++") ? From your Windows command prompt run Code: cd C:\Qt\4.8.6 Now we are ready to start the cloning process. If you are worried about compilation, it would be wise to jump ahead and ensure everything is working with compiling the client before working with the clone. 4. The Clone In this guide we will be cloning Litecoin. Litecoin is a Scrypt based coin and the original altcoin. I will be calling this coin Clonecoin (CLN). 4a. Download and extract the Litecoin source. https://github.com/litecoin-project/litecoin (https://github.com/litecoin-project/litecoin). In this guide I will be placing the source code in C:\Clonecoin Copy and Replace Litecoin Using your test editor, search out and replace all instances of Litecoin with Clonecoin. Make sure your search is case sensitive and search for all instances Litecoin with Clonecoin, litecoin with clonecoin etc. Run a search without case sensitivity before continuing to ensure you have all instances. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/61a9b7b8ea5db179b30f979d109847e473d0de81 (https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/61a9b7b8ea5db179b30f979d109847e473d0de81) 4c. Copy and Replace LTC. Using your test editor, search out and replace all instances of LTC with CLN. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/7b6a2ad68deb97caab802c460ebfe5104fa72e2c (https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/7b6a2ad68deb97caab802c460ebfe5104fa72e2c) 4d. Change rpc and port numbers. Search for an appropriate port and rpc number http://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers (http://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers). Litecoin uses port 9333 testnet 19333, rpcport 9332 testnet 19332. We will change them to port 10333 testnet 11333, rpcport 10332 testnet 11332 https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/7f149b069f77b3e174ca8a7b10b98287c3e663a9 (https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/7f149b069f77b3e174ca8a7b10b98287c3e663a9) 4e. Change starting letter for addresses. In this case we change the 48 to 28, therefore all addresses will start with C. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/d0621b86a358e93495658d564640144458aab8ee (https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/d0621b86a358e93495658d564640144458aab8ee) 4f. Update client version number. Since its really a fork of Litecoin we will bring the version numbers up to 1.0.0.0. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/95d0bef6e6a7bf27f3ed6d8153fccf8275524ba9 (https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/95d0bef6e6a7bf27f3ed6d8153fccf8275524ba9) 4g. Change Litecoin example addresses to Clonecoin Addresses. Here we change the LTC addresss Ler4HNAEfwYhBmGXcFP2Po1NpRUEiK8km2 to a Clonecoin mystery address starting with c. (see step 6d) https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/9a5321bfb9b0482ed3b435edb815d8eee268b949 (https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/9a5321bfb9b0482ed3b435edb815d8eee268b949) 4h. Change char pchMessageStart and ParseHex. We want these to be unique to Clonecoin. Be wary of changing pchMessageStart to to letters other than a-f. All numbers are fine to use. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/011b9a8e713821d8010a827f7aeacf09c772a267 (https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/011b9a8e713821d8010a827f7aeacf09c772a267) 4i. Change alert keys. We just change these to be different from Litecoin to avoid the Litecoin messages. I will link another guide here on how they work when complete and how to use them. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/0798f246007c9196bcfcf39c2ef2222a660d59d2 (https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/0798f246007c9196bcfcf39c2ef2222a660d59d2) 4j. Remove Merkel root and Genesis Block. These will be replaced later on though for now and in the near future they are no longer needed. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/46bbcb1377ac2db0f8dabc19faffb9ab6f989cb6 4k. Remove Nonce and testnet genesis. We remove the testnet genesis block and nonce. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/24cf6793c02369fc60a8b67645818f0cf7d1252a 4l. Add Epoochtime and Timestamp. To create a genesis block we need an epoochtime and verbal timestamp. The current epoochtime can be found http://www.epochconverter.com/ (http://www.epochconverter.com/) and find the latest news headline for your verbal timestamp. We also replace the testnet timestamp. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/790f9964abdb0543abe1ee1801562a004349e719 4m. Fixing the checkpoints. We comment out the hardcoded checkpoint and change the genesis block checkpoint. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/fe0d86a278f4d6470bee697a25256b0340cfc9fd 4n. Change max money supply and coinbase maturity. We just multiplied total coins by 10 and reduced coin based maturity. The higher the number of confirmations the better for the network. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/c43361429062f04b5697f9e9fca19e2f15d2e634 4o. Change block times from 2.5 minutes to 30 seconds. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/8796946bd1d3d5d15d06ba0e72e4b6bbf1fe1d06 4p. Change re-targeting from the ridiculous 2.5 days to every 5 minutes. This is cutting out a small portion of instamining. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/a3df6e9dc15009bdb22c60a496c109334cc55864 4q. Add premine and change block rewards. Since we initially increased block rewards by x10, we will increase the base reward from 50 to 500. We then add a premine on block 2 as well as a staggered decrease in block sizes. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/ddc36732b46fbc38ca06012be127ff994177192d 4r. Update Images. If you have not already, you will need a splash and logo. You will need to update src/rec/icons- bitcoin.png, bitcoin_testnet.png, bitcoin.icon, bitcoin_testnet.icon all 256x256 pixels. toolbar.png and toolbar_testnet.png to 16x16 pixels. also update src/res/images splash.png, splash_testnet.png and about.png. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/08edb2f2648acc373e60c44fbd0558c514697ff7 4s. Update Seed node- First you will need to create a dedicated node. This is a quick easy guide. Head to https://console.aws.amazon.com and create an account. Click on the EC2 link on the left. AWS pricing can be found http://aws.amazon.com/ec2/pricing/ Create and instance, select Microsoft Windows Server 2012 R2 Base, select your server preference- we chose t2.micro which is free tier eligible. Click Next: Configure Instance Details, highlight Protect against accidental termination, click review and launch. Go to security settings, open all ports and click launch. Create a security key pair and make sure to download it and keep it safe. Launch your instance. On the aws instance home screen click the Elastic IP tab, click allocate Ip address and confirm. While still in the Elastic IP tab, click allocate and allocate to the instance by clicking the top checkbox and identifying your server. Confirm. Your instance will take around 15 minutes to launch. To connect. Click the instance tab, highlight your instance and press connect. Using your key from earlier, you are now able to download a server shortcut and server password. Using your new Elastic IP, replace your new IP removing Litecoin old seed nodes. src/net.cpp Code: static const char *strMainNetDNSSeed[][2] = { 4.t Change the name of the bitcoin-qt.pro file to clonecoin-qt.pro https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/d309822b3b6519ca6424ac74df054ad351db1d88 5. Hashing the Genesis Block and Merkel Root. 5a. Ability to hash Genesis Block.We now need to add the ability to hash a new genesis block so we add the following code to main.cpp. main.cpp Code: if (true && block.GetHash() != hashGenesisBlock) 5b. Compiling Clonecoin Windows QT. Create libleveldb.a and libmemenv.a. Using Msys shell, run. For this we have Clonecoin in C:/Clonecoin Code: cd /C/clonecoin/src/leveldb Open your Clonecoin-qt.pro file. We now need to change the dependency directory locations Code: # Dependency library locations can be customized with: Code: # Dependency library locations can be customized with: Code: genleveldb.commands = cd $$PWD/src/leveldb && CC=$$QMAKE_CC CXX=$$QMAKE_CXX $(MAKE) OPT=\"$$QMAKE_CXXFLAGS Code: #genleveldb.commands = cd $$PWD/src/leveldb && CC=$$QMAKE_CC CXX=$$QMAKE_CXX $(MAKE) OPT=\"$$QMAKE_CXXFLAGS Add to Code: CONFIG += static Code: CONFIG += thread and Code: win32:QMAKE_LFLAGS *= -Wl,--large-address-aware Code: win32:QMAKE_LFLAGS *= -Wl,--large-address-aware -static Now from a the Windows cmd, run Code: set PATH=%PATH%;C:\Qt\4.8.6\bin Your Clonecoin qt should now be available in your C:\clonecoin\release folder after around 5 minutes. If errors occur, scroll up and read them try to identify and fix. 5c. Generating Merkel Root Start your Clonecoin-qt. You should see an error Assertion failed! Navigate to your Clonecoin appdata folder C:\Users\(YOUR*PC*NAME)\AppData\Roaming\Clonecoin and open the debug log in a text editor. The folder is hidden by default, so typing %appdata% in the Windows search bar will bring up access to the roaming\clonecoin folder. Scroll to the bottom of the text to find the following lines. Code: 2014-11-06 17:00:04 LoadBlockIndexDB(): last block file = 0 The bottom hash is the merkel root, we take this and add it to main.cpp Code: assert(block.hashMerkleRoot == uint256("0xd010ddcc6651af0e28e50ee36096e438b7974da9d58f1be95a968b180756a0c8")); https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/c776fb6da5599cc9a3bde9749880d9a1f9a1222a 5d. Hashing the Genesis Block. We now need to recompile the client in Windows cmd. You can remove the path and directory if you still have the client open. Code: set PATH=%PATH%;C:\Qt\4.8.6\bin Restart the client. The previous Merkel error should not occur and the client should appear to hang on launch. It is now hashing your genesis block. How long this takes can vary from a few seconds to minutes. Once the client hangs with a genesis block error, open your debug text file again in your Clonecoin appdata folder C:\Users\(YOUR*PC*NAME)\AppData\Roaming\Clonecoin Code: 2014-11-05 18:29:11 block.nNonce = 2110551 We will now add these to main.ccp. Code: @@ -35,7 +35,7 @@ CTxMemPool mempool; Recompile the Windows QT. From the Windows cmd, run Code: set PATH=%PATH%;C:\Qt\4.8.6\bin Your Clonecoin qt should now be available in your C:\clonecoin\release 6. Connecting your nodes. Now you have your client we need to connect the nodes to check everything is working. You can use testnet though its just as easy to use mainnet. Connect to your server we set up earlier or use another local machine. 6a. Create a conf. file. We only create this now to enable mining to check the network. Your conf. file should be placed in C:\Users\(YOUR**PC**NAME)\AppData\Roaming\clonecoin. To create a conf file, right click->new->text document. Copy and paste the code below replacing a suitable username and password. Click save, change file type to all and save as clonecoin.conf. Or just download this one. (https://www.mediafire.com/?taozsy80yaay1bz) Code: rpcuser=Yourusername 6b. Connect Server- upload your client to the server and start the client. The two clients should connect. Home Network- you may need to add your local ip's to the conf file. To do this type cmd to bring up command prompt, type ipconfig and use the IPv4 address in your addnodes from both machines. Code: rpcuser=Yourusername Once both clients are connected you can start to mine blocks. You can either use the traditional Scrypt miner or type setgenerate true-1 into your main console. Mine as many blocks as you want, checking diff adjustment and ensure block rewards are correct. It is advised to confirm some transactions, send some coins and check the client for any errors or adjustments. In this case I missed the toolbar.png and testnet_toolbar.png as a deliberate example of why you "SHOULD ALWAYS CHECK YOUR CLIENT BEFORE RELEASE" If you want to restart the chain you need to delete the chain by going to your Clonecoin roaming folder on both machines and deleting everything. 7. Checkpointing the premine. If you followed all the steps above you should be sitting with a lovely source code and compiled client. We have a few things to finish and checkpointing the premine is highly important. Many coin launches have been lost by people not knowing or forgetting to do this step. Without a premine you can very likely kiss your premine goodbye to a hash attack on launch. Start your compiled clients on both machines. Since we deleted the blockchain earlier mine your premine, plus 2-3 blocks. Open the concole on the clonecoin client and type getblockhash 1, getblockhash 2, getblockhash 3. We will use these three hashes to checkpoint the premine. We also need some data from the C:\Users\(YOUR**PC**NAME)\AppData\Roaming\clonecoin\debug file. We are looking for the details of the highest checkpointed block, in this case block 3. Code: 2014-11-11 15:02:57 SetBestChain: new best=718732cb3323ceaa46c8fc5fd521e7f7e31e424c59cc2a02e4e39c2c7306a649 [b]height=3[/b] log2_work=22.000022 [b] tx=4 [/b] date=2014-11-11 15:02:57 progress=1.000000 Now we add the block hashes for blocks 1, 2 and 3 and insert the highest block (block 3) details into the checkpoint block details. We also add the estimated number of transactions per day after the checkpoint. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/d5e61c1d0e7678cc165acf9dc1a27c6d23200030. Recompile you client. Back up your C:\Users\(YOUR**PC**NAME)\AppData\Roaming\clonecoin folder. This now has your premine. You now need to check the checkpoints are correct. On the client that does not have the premine, navigate to C:\Users\(YOUR**PC**NAME)\AppData\Roaming\clonecoin and delete all contents besides your wallet.dat(Very Important Do NOT DELETE) and clonecoin.conf files. Restart the client. If your checkpoints are correct the client should update and sync without issues. 8. Clean up your code. Clean up your read me with your new specifications, rewards, website etc. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/13fc52d07ed55d5b95071a043e88b13a6ad92a67 Remove your build deps and changes from clonecoin-qt.pro https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/437d50f106d588edd95fd35eec06b2da7cf3d49e 9. Compiling Clonecoind. Navigate to C:\clonecoin\src\makefile.mingw and open with your text editor. Code: USE_UPNP:=- Code: USE_UPNP:=1 We change the deps to point to the deps we created earlier. If you chose to place your deps in a different folder, change the code to point to your folders. We also -static to LDFLAGS=-Wl,--dynamicbase -Wl,--nxcompat -Wl,--large-address-aware -static for static linked exe, updated UPNP Includes and Lib paths to enable UPNP. In the Msys shell, you can now compile litecoind. Code: cd /c/clonecoin/src Your clonecoind should now be in your C:\clonecoin\src folder. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/6b124d98f059fb42b2b8837b520b6a626ec6f5ef 9b. Remove libleveldb.a and libmemev.a from C:\Clonecoin\src\leveldb. Remove your clonecoin-qt from the release folder and zip for release. Delete the release, debug and build folders. This is your code for release. 10. Github for release, made easy. 1. Create a Github account. 2. Download the latest Github Windows client https://windows.github.com/ (https://windows.github.com/) Run the Github install and use your log in details from Github to log into the client. 3. Navigate to you Github account, click repositories->new. Enter the repository name, description and public or private. Public allows everyone to see your code and is recommended for advanced users who can push codes quickly. Most launches will choose a paid private account, allowing them to pre-load the release source code and open the repository from public to private instantly. Click done, then on the next screen click the green Set up in Desktop button. Allow the browser to launch the Github client, select the location of your Github depositories, usually in the Github folder of your documents. Click ok. You now have a folder that you can update your source code and easily push commits to Github. 10a. Easy Pushing Commits/Launch Code. Copy and paste your source code into the documents/github/yourcoinnamefolder. In your Windows Github client, click on your client name on the left hand side. You Github client should recognise a host of changes if present. Fill in the commit details, select the files that need to be committed, usually all and on by default and press commit. On the top right hand side will be a publish or sync box, click that and the Github Windows client will push the changes and source code to your repository on Github. 10b. Easy Revert Commits. Open your Github client and ensure its sync'd. Highlight your repository. Click on the commit to you wish to rollback, then revert. On the top right hand side will be a publish or sync box, click that and the Github Windows client will push the revert to your repository on Github. 10c. Easy Pushing Updates. Log into your Github Windows client. Click on the altcoin tab in the left and click sync to ensure your local code is up to date. Edit your local code in your documents/github/yourcoinname folder. Once your Github client picks up the changes enter the commit details and commit to Github. 11. Common Errors/Mistakes. I am getting "this" error. Most errors can be solved with a little effort. The compiler will usually display an error message or warning. Read it. If it's UPNP error check your directories in your pro file, then check your UPNP deps, rebuild them. Google it. Most things can be solved far quicker with a little investigation into the errors vs posting in a forum and awaiting reply. I am still seeing the old logos on my desktop shortcuts. Windows cache has cached the image. The easiest way to solve this is run a program such as Glarys Utilities to clear your PC. Also delete the build folder in between builds to ensure your builds are clean. [c]Makefile.Release:291: recipe for target 'release\clonecoin-qt.exe' failed Close your client. 12. Creating your own logo. There are a few easy ways to get a logo. If you have Photoshop and want a easy template try http://apsdfile.com/coin-generator-for-photoshop/ (http://apsdfile.com/coin-generator-for-photoshop/). Install GIMP. GIMP is a free utility available to download from http://www.gimp.org/ (http://www.gimp.org/) and try youtube vids. For those looking for an even faster alternative try tools like http://www.onlinebadgemaker.com/3d-badge-maker (http://www.onlinebadgemaker.com/3d-badge-maker). These can be used for quick launches or temporary images while you wait, purchase or make an official one. 13. The Website. 13a. The Template. Download and install a free website editor. Bluegriffon is a prime example. http://bluegriffon.org/. Find yourself a suitable template at http://www.freshdesignweb.com/free-html5-css3-templates.html. Download and edit the template with all your coin details. 13b. Upload to a website. Create an account at NAMECHEAP (http://www.namecheap.com/?aff=76726), Namecheap (http://www.namecheap.com/?aff=76726) accept BTC and have the most awesome support. Register your domain and hosting at the same time. That way there is no DNS delay. Usually you can pick up a year hosting with domain and ssl if you want for under .15BTC. O may add installing an ssl cert later. If this is a one off coin launch a simple hosting plan will suffice, if your looking to launch more coins, choose a dedicated server or reseller plan. Find more at Namecheap. (http://www.namecheap.com/?aff=76726) Once your order is confirmed log into cpanel with the details provided, enable cloudflare and ssl of you purchased it. Single hosting plans will require support for ssl, dedicated or reseller accounts have the ability to self enable through WHM. In CPanel, go to file manger and upload your site to the public_html folder. Your website should be now viewable on your domain. 14. The Launch. Ninja vs Pumped vs ICO. Launching a coin is the make or break point. Depending on the style of launch will dictate how you prepare. 14a. Prelaunch. The key to a good launch is timing and consistency. Don't release the code early and make sure it works. Create your Bitcointalk account. The earlier the better to get rid of posting restrictions on new accounts. Create accounts on Twitter, Facebook, cryptocointalk, IRC, Reddit and all the usual channels. 14b. The Ninja- This gives the developer more time, no restrictions with no one looking or ready. With these coins you can set the network up early and don't have people looking for the code. Uploading the code to github a minute easily will likely be enough time to stop anyone searching. Website can go live early and some argue it gives miners a better chance. Usually a ninja launch involves a instamine allowing the developers to mine many blocks. 14c. The Pumped. Harder to do. The pre-hype means you will have people looking for the code on Github and websites. Your code needs to be solid to handle a massive intake of hashing power and be prepared for the harshest critics. 14d. The ICO. An advanced pump coin that needs a reliable escrow, good hype and delivery of goods. Most ICO's deliver nothing but BTC to the developer and broken promises to the users. Find a good escrow, take time with your code and remember to keep an open and clear communication. Title: Re: coin cloning guide Post by: 3x1t on August 16, 2018, 08:26:42 AM As for me, coin cloning is not so convincing doing which can lead many losses, I prefer more reliable ways of earning that I can trust without any doubts.
Title: Re: coin cloning guide Post by: sofmyhad on August 23, 2018, 10:20:03 AM I don't support this deal, I think it can be the one of reasons for the recovering of cryptocurrency market which is possible to be in the nearest time.
Title: Re: coin cloning guide Post by: Jewelettes on August 26, 2018, 06:03:44 AM Here you go. 1. Pre Installers.
3. Download and Compile QT. 4. The Clone
6. Connecting your nodes.
7. Checkpointing the premine. 8. Clean up You Code. 9. Compiling Clonecoind.
10. Github for release, made easy.
11. Common Errors 12. Quick Logos 13. The Website.
1. Pre Installers. 1a.1a. File Compressor/Extractor Download and install Winrar or an alternate file compression tool. http://www.rarlab.com/download.htm (http://www.rarlab.com/download.htm) 1b. Text Editor. Download and install a text editor such as Sublime Text (http://www.sublimetext.com/). You need a text editor that can easily search and replace case sensitive text. 1c. Download and install MingW http://sourceforge.net/projects/mingw/files/Installer/mingw-get-setup.exe/download (http://sourceforge.net/projects/mingw/files/Installer/mingw-get-setup.exe/download) Double click to install, keep the checkbox for the GUI checked and make sure to install in C:\MinGW. Press continue. From the MinGW GUI interface, go to all packages -> MYSYS Right click on the following installations and mark for installation. msys-base-bin (may highlight other checkboxes which is fine) msys-autoconf-bin msys-automake-bin msys-libtool-bin Click on Installation -> Apply changes. MinGW will now download the remaining packages. Make sure to remove any previous installs of MinGW before starting. Once complete, navigate to C:\MinGW\bin and you should only have a mingw-get application. If you have msys-gcc and msys-w32api you need to delete MinGW and check the correct install packages are selected above. Download and extract mingw32 to C:\mingw32 http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.9.1/theads-posix/dwarf/i686-4.9.1-release-posix-dwarf-rt_v3-rev1.7z/download (http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.9.1/theads-posix/dwarf/i686-4.9.1-release-posix-dwarf-rt_v3-rev1.7z/download) You now need to change the path variables. Go to control panel->system and security->system. Click on advanced system properties->environmental variables. In the top box navigate to PATH and change to Code: C:\mingw32\bin;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\ Checking your MingW install. To start the MingW app navigate to C:\MinGW\msys\1.0\msys.bat, create a desktop shortcut as you will use the msys command as well as the windows command prompts. Double click to start and enter the following to display the version and correct paths. Code: gcc -v Your msys output should look like the following code. Code: $ gcc -v If you are having issues I have uploaded a MinGW install here (https://howtocloneanaltcoin.com/downloads/MinGW.rar) 2. Download and Install Dependencies. Create a deps folder at C:\deps. If you want to cheat you can download the pre-built dependencies here (http://www.mediafire.com/download/y89546s65sf8de5/deps.zip), though it is recommended to build your own. 2a. OpenSLL- Install OpenSSL dependencies on Windows. Download the latest version of OpenSSL https://www.openssl.org/source/openssl-1.0.1j.tar.gz (https://www.openssl.org/source/openssl-1.0.1j.tar.gz) to your deps folder. Open the MinGW shell at C:\MinGW\msys\1.0\msys.bat Code: cd /c/deps/ 2b. Berkeley DB Download http://download.oracle.com/berkeley-db/db-4.8.30.NC.tar.gz (http://download.oracle.com/berkeley-db/db-4.8.30.NC.tar.gz) and place in your deps folder. In the MinGW shell use the following code. Code: cd /c/deps/ 2c. Boost Download Boost to your deps folder. http://sourceforge.net/projects/boost/files/boost/1.55.0/boost_1_55_0.zip/download (http://sourceforge.net/projects/boost/files/boost/1.55.0/boost_1_55_0.zip/download) Make sure to download either the 7z or zip versions. Double click on the folder to extract boost_1_55_0 in your deps folder. This may take several minutes depending on your PC's speed. Using the Windows command prompt, bootstrap and compile boost. To bring up the windows command prompt just type cmd in the windows search bar. Code: cd C:\deps\boost_1_55_0\ 2d. Mini UPNP Download and extract MiniUPNP http://miniupnp.free.fr/files/download.php?file=miniupnpc-1.9.20140911.tar.gz (http://miniupnp.free.fr/files/download.php?file=miniupnpc-1.9.20140911.tar.gz) to your deps folder. Rename folder from "miniupnpc-1.9.20140911" to "miniupnpc" then from a Windows command prompt: Code: cd C:\deps\miniupnpc 2e. Protoc and Libprotobuf: Download and extract http://protobuf.googlecode.com/files/protobuf-2.5.0.zip (http://protobuf.googlecode.com/files/protobuf-2.5.0.zip) to your deps folder. In the msys shell run Code: cd /c/deps/protobuf-2.5.0 2f. libpng Download and extract http://prdownloads.sourceforge.net/libpng/libpng-1.6.14.tar.gz?download (http://prdownloads.sourceforge.net/libpng/libpng-1.6.14.tar.gz?download) to your deps folder. Extract. In msys shell run Code: cd /c/deps/libpng-1.6.14 2g. qrencode Download and extract http://fukuchi.org/works/qrencode/qrencode-3.4.4.tar.gz (http://fukuchi.org/works/qrencode/qrencode-3.4.4.tar.gz) to your deps folder. In msys shell run Code: cd /c/deps/qrencode-3.4.4 3. Download and Compile QT. Download and uncompress http://download.qt-project.org/official_releases/qt/4.8/4.8.6/qt-everywhere-opensource-src-4.8.6.zip (http://download.qt-project.org/official_releases/qt/4.8/4.8.6/qt-everywhere-opensource-src-4.8.6.zip) to C:\Qt\4.8.6. Once again check it resides in C:\Qt\4.8.6 not C:\Qt\4.8.6\4.8.6. Due to a bug in 4.8.6 you will need to apply the patch available here (https://codereview.qt-project.org/#/c/84567/3/tools/configure/configureapp.cpp). For those who can't find or work it out, you need to change the following lines in C:\Qt\4.8.6\tools\configure\configureapp.cpp or download the patched file here (https://www.mediafire.com/?y4urdzfp0k0j0gm) and replace it in C:\Qt\4.8.6\tools\configure\configureapp.cpp Code: 2180 | - const QString mingwPath = dictionary["QMAKESPEC"].endsWith("-g++") ? From your Windows command prompt run Code: cd C:\Qt\4.8.6 Now we are ready to start the cloning process. If you are worried about compilation, it would be wise to jump ahead and ensure everything is working with compiling the client before working with the clone. 4. The Clone In this guide we will be cloning Litecoin. Litecoin is a Scrypt based coin and the original altcoin. I will be calling this coin Clonecoin (CLN). 4a. Download and extract the Litecoin source. https://github.com/litecoin-project/litecoin (https://github.com/litecoin-project/litecoin). In this guide I will be placing the source code in C:\Clonecoin Copy and Replace Litecoin Using your test editor, search out and replace all instances of Litecoin with Clonecoin. Make sure your search is case sensitive and search for all instances Litecoin with Clonecoin, litecoin with clonecoin etc. Run a search without case sensitivity before continuing to ensure you have all instances. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/61a9b7b8ea5db179b30f979d109847e473d0de81 (https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/61a9b7b8ea5db179b30f979d109847e473d0de81) 4c. Copy and Replace LTC. Using your test editor, search out and replace all instances of LTC with CLN. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/7b6a2ad68deb97caab802c460ebfe5104fa72e2c (https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/7b6a2ad68deb97caab802c460ebfe5104fa72e2c) 4d. Change rpc and port numbers. Search for an appropriate port and rpc number http://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers (http://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers). Litecoin uses port 9333 testnet 19333, rpcport 9332 testnet 19332. We will change them to port 10333 testnet 11333, rpcport 10332 testnet 11332 https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/7f149b069f77b3e174ca8a7b10b98287c3e663a9 (https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/7f149b069f77b3e174ca8a7b10b98287c3e663a9) 4e. Change starting letter for addresses. In this case we change the 48 to 28, therefore all addresses will start with C. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/d0621b86a358e93495658d564640144458aab8ee (https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/d0621b86a358e93495658d564640144458aab8ee) 4f. Update client version number. Since its really a fork of Litecoin we will bring the version numbers up to 1.0.0.0. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/95d0bef6e6a7bf27f3ed6d8153fccf8275524ba9 (https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/95d0bef6e6a7bf27f3ed6d8153fccf8275524ba9) 4g. Change Litecoin example addresses to Clonecoin Addresses. Here we change the LTC addresss Ler4HNAEfwYhBmGXcFP2Po1NpRUEiK8km2 to a Clonecoin mystery address starting with c. (see step 6d) https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/9a5321bfb9b0482ed3b435edb815d8eee268b949 (https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/9a5321bfb9b0482ed3b435edb815d8eee268b949) 4h. Change char pchMessageStart and ParseHex. We want these to be unique to Clonecoin. Be wary of changing pchMessageStart to to letters other than a-f. All numbers are fine to use. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/011b9a8e713821d8010a827f7aeacf09c772a267 (https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/011b9a8e713821d8010a827f7aeacf09c772a267) 4i. Change alert keys. We just change these to be different from Litecoin to avoid the Litecoin messages. I will link another guide here on how they work when complete and how to use them. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/0798f246007c9196bcfcf39c2ef2222a660d59d2 (https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/0798f246007c9196bcfcf39c2ef2222a660d59d2) 4j. Remove Merkel root and Genesis Block. These will be replaced later on though for now and in the near future they are no longer needed. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/46bbcb1377ac2db0f8dabc19faffb9ab6f989cb6 4k. Remove Nonce and testnet genesis. We remove the testnet genesis block and nonce. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/24cf6793c02369fc60a8b67645818f0cf7d1252a 4l. Add Epoochtime and Timestamp. To create a genesis block we need an epoochtime and verbal timestamp. The current epoochtime can be found http://www.epochconverter.com/ (http://www.epochconverter.com/) and find the latest news headline for your verbal timestamp. We also replace the testnet timestamp. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/790f9964abdb0543abe1ee1801562a004349e719 4m. Fixing the checkpoints. We comment out the hardcoded checkpoint and change the genesis block checkpoint. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/fe0d86a278f4d6470bee697a25256b0340cfc9fd 4n. Change max money supply and coinbase maturity. We just multiplied total coins by 10 and reduced coin based maturity. The higher the number of confirmations the better for the network. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/c43361429062f04b5697f9e9fca19e2f15d2e634 4o. Change block times from 2.5 minutes to 30 seconds. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/8796946bd1d3d5d15d06ba0e72e4b6bbf1fe1d06 4p. Change re-targeting from the ridiculous 2.5 days to every 5 minutes. This is cutting out a small portion of instamining. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/a3df6e9dc15009bdb22c60a496c109334cc55864 4q. Add premine and change block rewards. Since we initially increased block rewards by x10, we will increase the base reward from 50 to 500. We then add a premine on block 2 as well as a staggered decrease in block sizes. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/ddc36732b46fbc38ca06012be127ff994177192d 4r. Update Images. If you have not already, you will need a splash and logo. You will need to update src/rec/icons- bitcoin.png, bitcoin_testnet.png, bitcoin.icon, bitcoin_testnet.icon all 256x256 pixels. toolbar.png and toolbar_testnet.png to 16x16 pixels. also update src/res/images splash.png, splash_testnet.png and about.png. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/08edb2f2648acc373e60c44fbd0558c514697ff7 4s. Update Seed node- First you will need to create a dedicated node. This is a quick easy guide. Head to https://console.aws.amazon.com and create an account. Click on the EC2 link on the left. AWS pricing can be found http://aws.amazon.com/ec2/pricing/ Create and instance, select Microsoft Windows Server 2012 R2 Base, select your server preference- we chose t2.micro which is free tier eligible. Click Next: Configure Instance Details, highlight Protect against accidental termination, click review and launch. Go to security settings, open all ports and click launch. Create a security key pair and make sure to download it and keep it safe. Launch your instance. On the aws instance home screen click the Elastic IP tab, click allocate Ip address and confirm. While still in the Elastic IP tab, click allocate and allocate to the instance by clicking the top checkbox and identifying your server. Confirm. Your instance will take around 15 minutes to launch. To connect. Click the instance tab, highlight your instance and press connect. Using your key from earlier, you are now able to download a server shortcut and server password. Using your new Elastic IP, replace your new IP removing Litecoin old seed nodes. src/net.cpp Code: static const char *strMainNetDNSSeed[][2] = { 4.t Change the name of the bitcoin-qt.pro file to clonecoin-qt.pro https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/d309822b3b6519ca6424ac74df054ad351db1d88 5. Hashing the Genesis Block and Merkel Root. 5a. Ability to hash Genesis Block.We now need to add the ability to hash a new genesis block so we add the following code to main.cpp. main.cpp Code: if (true && block.GetHash() != hashGenesisBlock) 5b. Compiling Clonecoin Windows QT. Create libleveldb.a and libmemenv.a. Using Msys shell, run. For this we have Clonecoin in C:/Clonecoin Code: cd /C/clonecoin/src/leveldb Open your Clonecoin-qt.pro file. We now need to change the dependency directory locations Code: # Dependency library locations can be customized with: Code: # Dependency library locations can be customized with: Code: genleveldb.commands = cd $$PWD/src/leveldb && CC=$$QMAKE_CC CXX=$$QMAKE_CXX $(MAKE) OPT=\"$$QMAKE_CXXFLAGS Code: #genleveldb.commands = cd $$PWD/src/leveldb && CC=$$QMAKE_CC CXX=$$QMAKE_CXX $(MAKE) OPT=\"$$QMAKE_CXXFLAGS Add to Code: CONFIG += static Code: CONFIG += thread and Code: win32:QMAKE_LFLAGS *= -Wl,--large-address-aware Code: win32:QMAKE_LFLAGS *= -Wl,--large-address-aware -static Now from a the Windows cmd, run Code: set PATH=%PATH%;C:\Qt\4.8.6\bin Your Clonecoin qt should now be available in your C:\clonecoin\release folder after around 5 minutes. If errors occur, scroll up and read them try to identify and fix. 5c. Generating Merkel Root Start your Clonecoin-qt. You should see an error Assertion failed! Navigate to your Clonecoin appdata folder C:\Users\(YOUR*PC*NAME)\AppData\Roaming\Clonecoin and open the debug log in a text editor. The folder is hidden by default, so typing %appdata% in the Windows search bar will bring up access to the roaming\clonecoin folder. Scroll to the bottom of the text to find the following lines. Code: 2014-11-06 17:00:04 LoadBlockIndexDB(): last block file = 0 The bottom hash is the merkel root, we take this and add it to main.cpp Code: assert(block.hashMerkleRoot == uint256("0xd010ddcc6651af0e28e50ee36096e438b7974da9d58f1be95a968b180756a0c8")); https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/c776fb6da5599cc9a3bde9749880d9a1f9a1222a 5d. Hashing the Genesis Block. We now need to recompile the client in Windows cmd. You can remove the path and directory if you still have the client open. Code: set PATH=%PATH%;C:\Qt\4.8.6\bin Restart the client. The previous Merkel error should not occur and the client should appear to hang on launch. It is now hashing your genesis block. How long this takes can vary from a few seconds to minutes. Once the client hangs with a genesis block error, open your debug text file again in your Clonecoin appdata folder C:\Users\(YOUR*PC*NAME)\AppData\Roaming\Clonecoin Code: 2014-11-05 18:29:11 block.nNonce = 2110551 We will now add these to main.ccp. Code: @@ -35,7 +35,7 @@ CTxMemPool mempool; Recompile the Windows QT. From the Windows cmd, run Code: set PATH=%PATH%;C:\Qt\4.8.6\bin Your Clonecoin qt should now be available in your C:\clonecoin\release 6. Connecting your nodes. Now you have your client we need to connect the nodes to check everything is working. You can use testnet though its just as easy to use mainnet. Connect to your server we set up earlier or use another local machine. 6a. Create a conf. file. We only create this now to enable mining to check the network. Your conf. file should be placed in C:\Users\(YOUR**PC**NAME)\AppData\Roaming\clonecoin. To create a conf file, right click->new->text document. Copy and paste the code below replacing a suitable username and password. Click save, change file type to all and save as clonecoin.conf. Or just download this one. (https://www.mediafire.com/?taozsy80yaay1bz) Code: rpcuser=Yourusername 6b. Connect Server- upload your client to the server and start the client. The two clients should connect. Home Network- you may need to add your local ip's to the conf file. To do this type cmd to bring up command prompt, type ipconfig and use the IPv4 address in your addnodes from both machines. Code: rpcuser=Yourusername Once both clients are connected you can start to mine blocks. You can either use the traditional Scrypt miner or type setgenerate true-1 into your main console. Mine as many blocks as you want, checking diff adjustment and ensure block rewards are correct. It is advised to confirm some transactions, send some coins and check the client for any errors or adjustments. In this case I missed the toolbar.png and testnet_toolbar.png as a deliberate example of why you "SHOULD ALWAYS CHECK YOUR CLIENT BEFORE RELEASE" If you want to restart the chain you need to delete the chain by going to your Clonecoin roaming folder on both machines and deleting everything. 7. Checkpointing the premine. If you followed all the steps above you should be sitting with a lovely source code and compiled client. We have a few things to finish and checkpointing the premine is highly important. Many coin launches have been lost by people not knowing or forgetting to do this step. Without a premine you can very likely kiss your premine goodbye to a hash attack on launch. Start your compiled clients on both machines. Since we deleted the blockchain earlier mine your premine, plus 2-3 blocks. Open the concole on the clonecoin client and type getblockhash 1, getblockhash 2, getblockhash 3. We will use these three hashes to checkpoint the premine. We also need some data from the C:\Users\(YOUR**PC**NAME)\AppData\Roaming\clonecoin\debug file. We are looking for the details of the highest checkpointed block, in this case block 3. Code: 2014-11-11 15:02:57 SetBestChain: new best=718732cb3323ceaa46c8fc5fd521e7f7e31e424c59cc2a02e4e39c2c7306a649 [b]height=3[/b] log2_work=22.000022 [b] tx=4 [/b] date=2014-11-11 15:02:57 progress=1.000000 Now we add the block hashes for blocks 1, 2 and 3 and insert the highest block (block 3) details into the checkpoint block details. We also add the estimated number of transactions per day after the checkpoint. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/d5e61c1d0e7678cc165acf9dc1a27c6d23200030. Recompile you client. Back up your C:\Users\(YOUR**PC**NAME)\AppData\Roaming\clonecoin folder. This now has your premine. You now need to check the checkpoints are correct. On the client that does not have the premine, navigate to C:\Users\(YOUR**PC**NAME)\AppData\Roaming\clonecoin and delete all contents besides your wallet.dat(Very Important Do NOT DELETE) and clonecoin.conf files. Restart the client. If your checkpoints are correct the client should update and sync without issues. 8. Clean up your code. Clean up your read me with your new specifications, rewards, website etc. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/13fc52d07ed55d5b95071a043e88b13a6ad92a67 Remove your build deps and changes from clonecoin-qt.pro https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/437d50f106d588edd95fd35eec06b2da7cf3d49e 9. Compiling Clonecoind. Navigate to C:\clonecoin\src\makefile.mingw and open with your text editor. Code: USE_UPNP:=- Code: USE_UPNP:=1 We change the deps to point to the deps we created earlier. If you chose to place your deps in a different folder, change the code to point to your folders. We also -static to LDFLAGS=-Wl,--dynamicbase -Wl,--nxcompat -Wl,--large-address-aware -static for static linked exe, updated UPNP Includes and Lib paths to enable UPNP. In the Msys shell, you can now compile litecoind. Code: cd /c/clonecoin/src Your clonecoind should now be in your C:\clonecoin\src folder. https://github.com/HowToCloneAnAltcoin/Clonecoin/commit/6b124d98f059fb42b2b8837b520b6a626ec6f5ef 9b. Remove libleveldb.a and libmemev.a from C:\Clonecoin\src\leveldb. Remove your clonecoin-qt from the release folder and zip for release. Delete the release, debug and build folders. This is your code for release. 10. Github for release, made easy. 1. Create a Github account. 2. Download the latest Github Windows client https://windows.github.com/ (https://windows.github.com/) Run the Github install and use your log in details from Github to log into the client. 3. Navigate to you Github account, click repositories->new. Enter the repository name, description and public or private. Public allows everyone to see your code and is recommended for advanced users who can push codes quickly. Most launches will choose a paid private account, allowing them to pre-load the release source code and open the repository from public to private instantly. Click done, then on the next screen click the green Set up in Desktop button. Allow the browser to launch the Github client, select the location of your Github depositories, usually in the Github folder of your documents. Click ok. You now have a folder that you can update your source code and easily push commits to Github. 10a. Easy Pushing Commits/Launch Code. Copy and paste your source code into the documents/github/yourcoinnamefolder. In your Windows Github client, click on your client name on the left hand side. You Github client should recognise a host of changes if present. Fill in the commit details, select the files that need to be committed, usually all and on by default and press commit. On the top right hand side will be a publish or sync box, click that and the Github Windows client will push the changes and source code to your repository on Github. 10b. Easy Revert Commits. Open your Github client and ensure its sync'd. Highlight your repository. Click on the commit to you wish to rollback, then revert. On the top right hand side will be a publish or sync box, click that and the Github Windows client will push the revert to your repository on Github. 10c. Easy Pushing Updates. Log into your Github Windows client. Click on the altcoin tab in the left and click sync to ensure your local code is up to date. Edit your local code in your documents/github/yourcoinname folder. Once your Github client picks up the changes enter the commit details and commit to Github. 11. Common Errors/Mistakes. I am getting "this" error. Most errors can be solved with a little effort. The compiler will usually display an error message or warning. Read it. If it's UPNP error check your directories in your pro file, then check your UPNP deps, rebuild them. Google it. Most things can be solved far quicker with a little investigation into the errors vs posting in a forum and awaiting reply. I am still seeing the old logos on my desktop shortcuts. Windows cache has cached the image. The easiest way to solve this is run a program such as Glarys Utilities to clear your PC. Also delete the build folder in between builds to ensure your builds are clean. [c]Makefile.Release:291: recipe for target 'release\clonecoin-qt.exe' failed Close your client. 12. Creating your own logo. There are a few easy ways to get a logo. If you have Photoshop and want a easy template try http://apsdfile.com/coin-generator-for-photoshop/ (http://apsdfile.com/coin-generator-for-photoshop/). Install GIMP. GIMP is a free utility available to download from http://www.gimp.org/ (http://www.gimp.org/) and try youtube vids. For those looking for an even faster alternative try tools like http://www.onlinebadgemaker.com/3d-badge-maker (http://www.onlinebadgemaker.com/3d-badge-maker). These can be used for quick launches or temporary images while you wait, purchase or make an official one. 13. The Website. 13a. The Template. Download and install a free website editor. Bluegriffon is a prime example. http://bluegriffon.org/. Find yourself a suitable template at http://www.freshdesignweb.com/free-html5-css3-templates.html. Download and edit the template with all your coin details. 13b. Upload to a website. Create an account at NAMECHEAP (http://www.namecheap.com/?aff=76726), Namecheap (http://www.namecheap.com/?aff=76726) accept BTC and have the most awesome support. Register your domain and hosting at the same time. That way there is no DNS delay. Usually you can pick up a year hosting with domain and ssl if you want for under .15BTC. O may add installing an ssl cert later. If this is a one off coin launch a simple hosting plan will suffice, if your looking to launch more coins, choose a dedicated server or reseller plan. Find more at Namecheap. (http://www.namecheap.com/?aff=76726) Once your order is confirmed log into cpanel with the details provided, enable cloudflare and ssl of you purchased it. Single hosting plans will require support for ssl, dedicated or reseller accounts have the ability to self enable through WHM. In CPanel, go to file manger and upload your site to the public_html folder. Your website should be now viewable on your domain. 14. The Launch. Ninja vs Pumped vs ICO. Launching a coin is the make or break point. Depending on the style of launch will dictate how you prepare. 14a. Prelaunch. The key to a good launch is timing and consistency. Don't release the code early and make sure it works. Create your Bitcointalk account. The earlier the better to get rid of posting restrictions on new accounts. Create accounts on Twitter, Facebook, cryptocointalk, IRC, Reddit and all the usual channels. 14b. The Ninja- This gives the developer more time, no restrictions with no one looking or ready. With these coins you can set the network up early and don't have people looking for the code. Uploading the code to github a minute easily will likely be enough time to stop anyone searching. Website can go live early and some argue it gives miners a better chance. Usually a ninja launch involves a instamine allowing the developers to mine many blocks. 14c. The Pumped. Harder to do. The pre-hype means you will have people looking for the code on Github and websites. Your code needs to be solid to handle a massive intake of hashing power and be prepared for the harshest critics. 14d. The ICO. An advanced pump coin that needs a reliable escrow, good hype and delivery of goods. Most ICO's deliver nothing but BTC to the developer and broken promises to the users. Find a good escrow, take time with your code and remember to keep an open and clear communication. Made my head spin when I start to read this. I'll learn how to code when spinning stops though. Looks like the endless misery of a coin developer revealed ;) Title: Re: coin cloning guide Post by: robertsu on August 26, 2018, 12:28:30 PM The some tokens have a open source code. Sometimes it can be on the Github. There you can to made a copy all code. If really should be have a some small knows in programming.
Title: Re: coin cloning guide Post by: xjasz on December 01, 2018, 12:12:50 AM Why do my images not show up? Do I need to be atleast a jr member?
https://i.ibb.co/6vN2sBC/300.jpg (https://i.ibb.co/6vN2sBC/300.jpg) Title: Re: coin cloning guide Post by: Little_king on December 01, 2018, 03:03:52 AM Why would you want to know a bad way to blockchain? This is why we are having many issue in crypto now as people like you are not met to be here in the first place , adding value to this technology should be every one concern but many are just here to scam people and get rich in a day , but they should always remember that nemesis will fall on them.
Title: Re: coin cloning guide Post by: rricksu on December 01, 2018, 03:12:05 AM could anyone point how to clone altcoin without having a knowldge of any programming :) heard there is a guide but coudnt find its traces in google. I guess they just copy some opensource code and rename every variables into it and basically, implement it with different author. I think that is the way how they clone the code, not literally copying everything in the source code but they study it first. Title: Re: coin cloning guide Post by: foxbitcoin on December 02, 2018, 06:16:11 AM could anyone point how to clone altcoin without having a knowldge of any programming :) heard there is a guide but coudnt find its traces in google. This sentence is true. Anyone with technology can clone and copy the altcoin, but it is very difficult to make the altcoin valuable.Title: Re: coin cloning guide Post by: moijiashiasei on June 25, 2019, 04:00:19 PM could anyone point how to clone altcoin without having a knowldge of any programming :) heard there is a guide but coudnt find its traces in google. This sentence is true. Anyone with technology can clone and copy the altcoin, but it is very difficult to make the altcoin valuable.completed number of altcoin projects can make new coin for you PM me basic package 190 us Title: Re: coin cloning guide Post by: mironkraft on March 01, 2021, 09:38:29 AM 3. Download and Compile QT. Download and uncompress http://download.qt-project.org/official_releases/qt/4.8/4.8.6/qt-everywhere-opensource-src-4.8.6.zip (http://download.qt-project.org/official_releases/qt/4.8/4.8.6/qt-everywhere-opensource-src-4.8.6.zip) to C:\Qt\4.8.6. Once again check it resides in C:\Qt\4.8.6 not C:\Qt\4.8.6\4.8.6. Due to a bug in 4.8.6 you will need to apply the patch available here (https://codereview.qt-project.org/#/c/84567/3/tools/configure/configureapp.cpp). For those who can't find or work it out, you need to change the following lines in C:\Qt\4.8.6\tools\configure\configureapp.cpp or download the patched file here (https://www.mediafire.com/?y4urdzfp0k0j0gm) and replace it in C:\Qt\4.8.6\tools\configure\configureapp.cpp Code: 2180 | - const QString mingwPath = dictionary["QMAKESPEC"].endsWith("-g++") ? From your Windows command prompt run Code: cd C:\Qt\4.8.6 hello, thanks for tutorial, im working on and im facing the next problem Code: C:\qt\4.8.6>configure -release -opensource -confirm-license -static -no-sql-sqlite -no-qt3support -no-opengl -qt-zlib -no-gif -qt-libpng -qt-libmng -no-libtiff -qt-libjpeg -no-dsp -no-vcproj -no-openssl -no-dbus -no-phonon -no-phonon-backend -no-multimedia -no-audio-backend -no-webkit -no-script -no-scripttools -no-declarative -no-declarative-debug -qt-style-windows -qt-style-windowsxp -qt-style-windowsvista -no-style-plastique -no-style-cleanlooks -no-style-motif -no-style-cde -nomake demos -nomake examples how I can fix? (ps: already executed cmd with admin privileges) also, is there any update for this tutorial? thanks, kind regards Title: Re: coin cloning guide Post by: mironkraft on March 04, 2021, 05:45:46 AM hi hi hi! anyone helps?! :o
thanks! Title: Re: coin cloning guide Post by: mironkraft on March 08, 2021, 05:34:07 PM bump for help?
|