Public config files for forknote
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
.gitignore Initial commit Jun 1, 2015
README.md Update README.md Mar 23, 2018
bikercoin.conf Changing DCY alg change + adding coins Dec 31, 2017
bipcoin.conf Fix MAX_TRANSACTION_SIZE_LIMIT for bipcoin Feb 20, 2018
bitcoal.conf Update bitcoal seed nodes Nov 12, 2017
bitsum.conf Changing DCY alg change + adding coins Dec 31, 2017
bytecoin.conf Checkpoints added May 29, 2017
crossnote.testnet.conf Configs for Cryptonote Coin based networks added Jun 16, 2016
dashcoin.conf Update Oct 19, 2017
dashcoin.minergate.conf Moving replay attack protection in separate configs Sep 15, 2017
dashcoin.minergate.replay_attack_protection.conf Moving replay attack protection in separate configs Sep 15, 2017
dashcoin.replay_attack_protection.conf Moving replay attack protection in separate configs Sep 15, 2017
dinastycoin.conf Changing DCY alg change + adding coins Dec 31, 2017
karbowanec.conf Karbo fixes May 12, 2018
leviarcoin.conf not working configs removed. Minergate forked chains added Aug 6, 2017
magnatoj.conf Updating nodes Dec 23, 2016
nicnaccoin.conf removed unneeded params Mar 26, 2018
pluracoin.conf Initial version Mar 8, 2018
quazarcoin.conf Moving replay attack protection in separate configs Sep 15, 2017
quazarcoin.minergate.conf Moving replay attack protection in separate configs Sep 15, 2017
quazarcoin.minergate.replay_attack_protection.conf Moving replay attack protection in separate configs Sep 15, 2017
quazarcoin.replay_attack_protection.conf Moving replay attack protection in separate configs Sep 15, 2017
redwind.conf Updated configs Jul 19, 2016
safecoin.conf Changing DCY alg change + adding coins Dec 31, 2017
turtlecoin Proposed update for algo change, Block 187k Jan 24, 2018
xcicoin.conf 78.47.186.74 node moved to 78.47.184.165 Sep 18, 2017

README.md

Introduction

This repository contains configuration files for active Forknote networks.

How to start

The easiest way to start a Forknote network is to see the configuration file of an already existing coin and modify it.

You can also start from scratch and create a new configuration file by using a simple text editor or by using our configuration wizard.

Parameters

Full list of the available configuration options can be found here - Forknote configuration options

Common mistakes

  • All network clients must have the same configuration file
  • You need at least 2 seed nodes
  • 127.0.0.1 cannot be a seed node
  • Use CRYPTONOTE_NAME with lower case chars only

Tools

Share

To share your configuration make a pull request to https://github.com/forknote/configs or email it to support@forknote.net