Post
Topic
Board Service Announcements (Altcoins)
Re: [ANN] Forknote - create your own Cryptonote network
by
ssdnow
on 03/01/2018, 02:24:31 UTC
Hi- @NicNacCoin.
Could you help me in telling me if my node is running well? if what that shows is the right thing, because when entering the wallet that creates with the same .conf that the nodes have, it tells me that there is an error in synchronizing.


Is this node running well? or is it not working as it should be?


Code:
fork@tech2:~/forknote-linux$ ./forknoted --config-file configs/technetium.conf
Success: Configuration file openned: "configs/technetium.conf"
2018-Jan-02 19:36:18.743872 INFO    forknote v2.1.1.1245 ()
2018-Jan-02 19:36:18.744925 INFO    Module folder: ./forknoted
2018-Jan-02 19:36:18.746964 INFO    Opening DB in /home/fork/.technetium/DB
2018-Jan-02 19:36:18.763394 INFO    DB opened in /home/fork/.technetium/DB
2018-Jan-02 19:36:18.766321 INFO    Initializing core...
2018-Jan-02 19:36:18.777807 INFO    Core initialized OK
2018-Jan-02 19:36:18.778304 INFO    Initializing p2p server...
2018-Jan-02 19:36:18.778495 INFO    Generated new peer ID: 7029398983946693145
2018-Jan-02 19:36:18.778632 INFO    Binding on 0.0.0.0:34250
2018-Jan-02 19:36:18.778833 INFO    Net service binded on 0.0.0.0:34250
2018-Jan-02 19:36:18.778966 INFO    Attempting to add IGD port mapping.
2018-Jan-02 19:36:22.784096 INFO    No IGD was found.
2018-Jan-02 19:36:22.784263 INFO    P2p server initialized OK
2018-Jan-02 19:36:22.792004 INFO    Starting core rpc server on address 127.0.0.1:34377
2018-Jan-02 19:36:22.792378 INFO    Core rpc server started ok
2018-Jan-02 19:36:22.792522 INFO    Starting p2p net loop...
2018-Jan-02 19:36:22.792608 INFO    Starting node_server
2018-Jan-02 19:36:22.799842 INFO
2018-Jan-02 19:36:22.799842 INFO    **********************************************************************
2018-Jan-02 19:36:22.799842 INFO    You are now synchronized with the network. You may now start simplewallet.
2018-Jan-02 19:36:22.799842 INFO
2018-Jan-02 19:36:22.799842 INFO    Please note, that the blockchain will be saved only after you quit the daemon with "exit" command                                   or if you use "save" command.
2018-Jan-02 19:36:22.799842 INFO    Otherwise, you will possibly need to synchronize the blockchain again.
2018-Jan-02 19:36:22.799842 INFO
2018-Jan-02 19:36:22.799842 INFO    Use "help" command to see the list of available commands.
2018-Jan-02 19:36:22.799842 INFO    **********************************************************************
2018-Jan-02 19:36:22.802332 WARNING [207.246.65.66:[b]57677[/b] INC] Exception in connectionHandler: TcpConnection::read
2018-Jan-02 19:36:24.809138 WARNING [207.246.65.66:[b]46316[/b] INC] Exception in connectionHandler: TcpConnection::read
2018-Jan-02 19:36:26.811479 WARNING [207.246.65.66:[b]33803[/b] INC] Exception in connectionHandler: TcpConnection::read
2018-Jan-02 19:36:28.814101 WARNING [207.246.65.66:[b]46890[/b] INC] Exception in connectionHandler: TcpConnection::read
2018-Jan-02 19:36:30.817393 WARNING [207.246.65.66:[b]35115[/b] INC] Exception in connectionHandler: TcpConnection::read
2018-Jan-02 19:36:32.819522 WARNING [207.246.65.66:[b]38274[/b] INC] Exception in connectionHandler: TcpConnection::read
2018-Jan-02 19:36:34.823345 WARNING [207.246.65.66:[b]38731[/b] INC] Exception in connectionHandler: TcpConnection::read
2018-Jan-02 19:36:36.825551 WARNING [207.246.65.66:[b]54882[/b] INC] Exception in connectionHandler: TcpConnection::read
2018-Jan-02 19:36:38.828191 WARNING [207.246.65.66:[b]54645[/b] INC] Exception in connectionHandler: TcpConnection::read
2018-Jan-02 19:36:40.832488 WARNING [207.246.65.66:[b]51703[/b] INC] Exception in connectionHandler: TcpConnection::read
2018-Jan-02 19:36:42.834446 WARNING [207.246.65.66:[b]44667[/b] INC] Exception in connectionHandler: TcpConnection::read
Looks like your coins config file has p2p-bind-port=34250
this is just your daemon attempt to connect to 207.246.65.66:(all those other ports) its fine I get that when testing
More interested in what error Simplewallet gives(if any)?
FYI, you should have at minimun 2 nodes.
Once those nodes are up and you get the message "You are now sync.." try connecting with a desktop or laptop.
Are you able to connect to this network using 3rd machine in its current state?

Most error can be fixed by deleting stored blockchain on server.
I tried the simplewallet "reset" but that works like 1 out of 1,000 times.

I've notice after v2.0.6 creating Pre-mine coins and getting block reward mismatch or genesis tx coinbase blah blah blah require workaround.
then if you test min a few blocks with ZAWY params and let your network go unmined for a period of time and mining resumes the difficulty will adjust to diff 1 and then there's the forknoted "height overhead diff" error that requires another fix.

Good luck. reach me by email at support@nicnaccoins.com




Here I am going to leave a video of how I did everything from 0

https://www.youtube.com/watch?v=5sunNBSJVpQ&feature=youtu.be

file .conf

Code:
EMISSION_SPEED_FACTOR=18
DIFFICULTY_TARGET=120
CRYPTONOTE_DISPLAY_DECIMAL_POINT=12
MONEY_SUPPLY=18446744073709551615
GENESIS_BLOCK_REWARD=0
DEFAULT_DUST_THRESHOLD=1000000
MINIMUM_FEE=1000000
CRYPTONOTE_MINED_MONEY_UNLOCK_WINDOW=10
CRYPTONOTE_BLOCK_GRANTED_FULL_REWARD_ZONE=100000
MAX_TRANSACTION_SIZE_LIMIT=100000
CRYPTONOTE_PUBLIC_ADDRESS_BASE58_PREFIX=287
DIFFICULTY_CUT_V1=60
DIFFICULTY_CUT_V2=60
DIFFICULTY_CUT=0
DIFFICULTY_LAG_V1=15
DIFFICULTY_LAG_V2=15
DIFFICULTY_LAG=0
DIFFICULTY_WINDOW_V1=720
DIFFICULTY_WINDOW_V2=720
DIFFICULTY_WINDOW=17
ZAWY_DIFFICULTY_V3=1
ZAWY_DIFFICULTY_DIFFICULTY_BLOCK_VERSION=3
p2p-bind-port=22850
rpc-bind-port=22851
BYTECOIN_NETWORK=a0a5ac32-4450-4c62-c743-c63d3fe13ba5
CRYPTONOTE_NAME=technetium
GENESIS_COINBASE_TX_HEX=010a01ff0001ffffffffffff0f029b2e4c0281c0b02e7c53291a94d1d0cbff8883f8024f5142ee494ffbbd0880712101fff35ac4f45553edcadf0be748fb3dee99d5978f835e21c6949fab34ade1982b
MAX_BLOCK_SIZE_INITIAL=100000
UPGRADE_HEIGHT_V2=1
UPGRADE_HEIGHT_V3=30
seed-node=207.246.65.248:22850
seed-node=207.246.112.171:22850

The servers will be active if you want to test, then I will remove it for security reasons.