ssdnow
Newbie
Offline
Activity: 41
Merit: 0
|
|
January 03, 2018, 02:24:31 AM |
|
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? 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= 34250this 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.comHere I am going to leave a video of how I did everything from 0 https://www.youtube.com/watch?v=5sunNBSJVpQ&feature=youtu.befile .conf 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.
|
|
|
|
NicNacCoin
|
|
January 03, 2018, 02:59:54 AM |
|
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? 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= 34250this 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.comHere I am going to leave a video of how I did everything from 0 https://www.youtube.com/watch?v=5sunNBSJVpQ&feature=youtu.befile .conf 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.No need. I saw the error was gonna happen at 1:45 mark of the video. Trouble shooting steps to try 1. halt all (3) machines 2. rm all stored blockchain from all machines 3. Launch forknoted on (2) servers 1st and get them to connect 4. Launch forknoted on desktop 5. Launch simplewallet
|
|
|
|
ssdnow
Newbie
Offline
Activity: 41
Merit: 0
|
|
January 03, 2018, 03:27:07 AM |
|
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? 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= 34250this 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.comHere I am going to leave a video of how I did everything from 0 https://www.youtube.com/watch?v=5sunNBSJVpQ&feature=youtu.befile .conf 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. I did it step by step as you explained to me and I still have the same error message in simplewalletC:\fork\forknote>simplewallet.exe --config-file configs/technetium.conf Success: Configuration file openned 2018-Jan-02 23:22:16.774509 INFO forknote wallet v2.1.2.1251 () Nor 'generate-new-wallet' neither 'wallet-file' argument was specified. What do you want to do? [O]pen existing wallet, [G]enerate new wallet file, [I]mport wallet or [E]xit. o Specify wallet file name (e.g., wallet.bin). Wallet file name: GA password: ****** 2018-Jan-02 23:22:25.791290 INFO Loading wallet... Sync from timestamp: 1514857800 2018-Jan-02 23:22:25.838320 INFO Opened wallet: TbcFDrKbVmbA4tzNHvF513FCivJXsZ91TGA7eaL36gwUHrW8YYRScdGdrYfFX4YV4DJPWEt759CojLUMACWPMFWe1rpS1KuUW 2018-Jan-02 23:22:25.842823 INFO ********************************************************************** Use "help" command to see the list of available commands. ********************************************************************** 2018-Jan-02 23:22:25.852829 ERROR [BlockchainSynchronizer] Failed to query outdated pool transaction: NodeErrorCategory:3, Network error
[wallet TbcFDr]: 2018-Jan-02 23:22:30.858810 ERROR [BlockchainSynchronizer] Failed to query outdated pool transaction: NodeErrorCategory:3, Network error 2018-Jan-02 23:22:35.870153 ERROR [BlockchainSynchronizer] Failed to query outdated pool transaction: NodeErrorCategory:3, Network error 2018-Jan-02 23:22:40.877934 ERROR [BlockchainSynchronizer] Failed to query outdated pool transaction: NodeErrorCategory:3, Network error 2018-Jan-02 23:22:45.887917 ERROR [BlockchainSynchronizer] Failed to query outdated pool transaction: NodeErrorCategory:3, Network error 2018-Jan-02 23:22:50.893404 ERROR [BlockchainSynchronizer] Failed to query outdated pool transaction: NodeErrorCategory:3, Network error 2018-Jan-02 23:22:55.901803 ERROR [BlockchainSynchronizer] Failed to query outdated pool transaction: NodeErrorCategory:3, Network error2018-Jan-02 23:23:00.909823 ERROR [BlockchainSynchronizer] Failed to query outdated pool transaction: NodeErrorCategory:3, Network error 2018-Jan-02 23:23:05.917073 ERROR [BlockchainSynchronizer] Failed to query outdated pool transaction: NodeErrorCategory:3, Network error 2018-Jan-02 23:23:10.930158 ERROR [BlockchainSynchronizer] Failed to query outdated pool transaction: NodeErrorCategory:3, Network error 2018-Jan-02 23:23:15.949587 ERROR [BlockchainSynchronizer] Failed to query outdated pool transaction: NodeErrorCategory:3, Network error
|
|
|
|
NicNacCoin
|
|
January 03, 2018, 03:58:42 AM |
|
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? 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= 34250this 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.comHere I am going to leave a video of how I did everything from 0 https://www.youtube.com/watch?v=5sunNBSJVpQ&feature=youtu.befile .conf 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. I did it step by step as you explained to me and I still have the same error message in simplewalletC:\fork\forknote>simplewallet.exe --config-file configs/technetium.conf Success: Configuration file openned 2018-Jan-02 23:22:16.774509 INFO forknote wallet v2.1.2.1251 () Nor 'generate-new-wallet' neither 'wallet-file' argument was specified. What do you want to do? [O]pen existing wallet, [G]enerate new wallet file, [I]mport wallet or [E]xit. o Specify wallet file name (e.g., wallet.bin). Wallet file name: GA password: ****** 2018-Jan-02 23:22:25.791290 INFO Loading wallet... Sync from timestamp: 1514857800 2018-Jan-02 23:22:25.838320 INFO Opened wallet: TbcFDrKbVmbA4tzNHvF513FCivJXsZ91TGA7eaL36gwUHrW8YYRScdGdrYfFX4YV4DJPWEt759CojLUMACWPMFWe1rpS1KuUW 2018-Jan-02 23:22:25.842823 INFO ********************************************************************** Use "help" command to see the list of available commands. ********************************************************************** 2018-Jan-02 23:22:25.852829 ERROR [BlockchainSynchronizer] Failed to query outdated pool transaction: NodeErrorCategory:3, Network error
[wallet TbcFDr]: 2018-Jan-02 23:22:30.858810 ERROR [BlockchainSynchronizer] Failed to query outdated pool transaction: NodeErrorCategory:3, Network error 2018-Jan-02 23:22:35.870153 ERROR [BlockchainSynchronizer] Failed to query outdated pool transaction: NodeErrorCategory:3, Network error 2018-Jan-02 23:22:40.877934 ERROR [BlockchainSynchronizer] Failed to query outdated pool transaction: NodeErrorCategory:3, Network error 2018-Jan-02 23:23:10.930158 ERROR [BlockchainSynchronizer] Failed to query outdated pool transaction: NodeErrorCategory:3, Network error 2018-Jan-02 23:23:15.949587 ERROR [BlockchainSynchronizer] Failed to query outdated pool transaction: NodeErrorCategory:3, Network error C:\Users\Crackup\Music\technetium>lib\simplewallet --config-file configs/technetiumcoin.conf Success: Configuration file openned 2018-Jan-02 21:48:51.554000 INFO forknote wallet v2.0.1.1221 () Nor 'generate-new-wallet' neither 'wallet-file' argument was specified. What do you want to do? [O]pen existing wallet, [G]enerate new wallet file, [I]mport wallet or [E]xit. g Specify wallet file name (e.g., wallet.bin). Wallet file name: GA password: **** Sync from timestamp: 1514864938 2018-Jan-02 21:48:58.465000 INFO Generated new wallet: Tbc9gPp3Vih3JWsX75gLr91TxqbuvdJoUe1ufFrCtGKfB1j8tYR84XpTj2pcVmwU661gFfq4EVqJuMBGSaGTmk7q3C1L 2018-Jan-02 21:48:58.465000 INFO view key: f306fea55ad26819f2588b61d9aef3998d46e911c891926c4f8170933f506e01 2018-Jan-02 21:48:58.484000 INFO ********************************************************************** Your wallet has been generated. Use "help" command to see the list of available commands. Always use "exit" command when closing simplewallet to save current session's state. Otherwise, you will possibly need to synchronize your wallet again. Your wallet key is NOT under risk anyway. **********************************************************************
[wallet Tbc9gP]: 2018-Jan-02 21:50:34.051000 INFO Height 1, transaction a7bb9f4ad14af1e3198872f80473d6fb06b5212d01dc352c1575e234075c33dc, received resett 1 of 1 Sync from timestamp: 1514864938 2018-Jan-02 21:54:11.727000 INFO Reset completed successfully. 2018-Jan-02 21:54:12.457000 INFO Height 1, transaction a7bb9f4ad14af1e3198872f80473d6fb06b5212d01dc352c1575e234075c33dc, received 70.368475742208 Those were simply trouble shooting step, no grntee You want to try those 1st in this case I simple made new seeds for the configs on ubuntu 14.04 64 bit Feel free to test yourself using config file param 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=159.89.46.135:22850 seed-node=159.89.176.66:22850
|
|
|
|
ssdnow
Newbie
Offline
Activity: 41
Merit: 0
|
|
January 03, 2018, 04:28:47 AM Last edit: January 03, 2018, 04:49:26 AM by ssdnow |
|
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? 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= 34250this 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.comHere I am going to leave a video of how I did everything from 0 https://www.youtube.com/watch?v=5sunNBSJVpQ&feature=youtu.befile .conf 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. I did it step by step as you explained to me and I still have the same error message in simplewalletC:\fork\forknote>simplewallet.exe --config-file configs/technetium.conf Success: Configuration file openned 2018-Jan-02 23:22:16.774509 INFO forknote wallet v2.1.2.1251 () Nor 'generate-new-wallet' neither 'wallet-file' argument was specified. What do you want to do? [O]pen existing wallet, [G]enerate new wallet file, [I]mport wallet or [E]xit. o Specify wallet file name (e.g., wallet.bin). Wallet file name: GA password: ****** 2018-Jan-02 23:22:25.791290 INFO Loading wallet... Sync from timestamp: 1514857800 2018-Jan-02 23:22:25.838320 INFO Opened wallet: TbcFDrKbVmbA4tzNHvF513FCivJXsZ91TGA7eaL36gwUHrW8YYRScdGdrYfFX4YV4DJPWEt759CojLUMACWPMFWe1rpS1KuUW 2018-Jan-02 23:22:25.842823 INFO ********************************************************************** Use "help" command to see the list of available commands. ********************************************************************** 2018-Jan-02 23:22:25.852829 ERROR [BlockchainSynchronizer] Failed to query outdated pool transaction: NodeErrorCategory:3, Network error
[wallet TbcFDr]: 2018-Jan-02 23:22:30.858810 ERROR [BlockchainSynchronizer] Failed to query outdated pool transaction: NodeErrorCategory:3, Network error 2018-Jan-02 23:22:35.870153 ERROR [BlockchainSynchronizer] Failed to query outdated pool transaction: NodeErrorCategory:3, Network error 2018-Jan-02 23:22:40.877934 ERROR [BlockchainSynchronizer] Failed to query outdated pool transaction: NodeErrorCategory:3, Network error 2018-Jan-02 23:23:10.930158 ERROR [BlockchainSynchronizer] Failed to query outdated pool transaction: NodeErrorCategory:3, Network error 2018-Jan-02 23:23:15.949587 ERROR [BlockchainSynchronizer] Failed to query outdated pool transaction: NodeErrorCategory:3, Network error C:\Users\Crackup\Music\technetium>lib\simplewallet --config-file configs/technetiumcoin.conf Success: Configuration file openned 2018-Jan-02 21:48:51.554000 INFO forknote wallet v2.0.1.1221 () Nor 'generate-new-wallet' neither 'wallet-file' argument was specified. What do you want to do? [O]pen existing wallet, [G]enerate new wallet file, [I]mport wallet or [E]xit. g Specify wallet file name (e.g., wallet.bin). Wallet file name: GA password: **** Sync from timestamp: 1514864938 2018-Jan-02 21:48:58.465000 INFO Generated new wallet: Tbc9gPp3Vih3JWsX75gLr91TxqbuvdJoUe1ufFrCtGKfB1j8tYR84XpTj2pcVmwU661gFfq4EVqJuMBGSaGTmk7q3C1L 2018-Jan-02 21:48:58.465000 INFO view key: f306fea55ad26819f2588b61d9aef3998d46e911c891926c4f8170933f506e01 2018-Jan-02 21:48:58.484000 INFO ********************************************************************** Your wallet has been generated. Use "help" command to see the list of available commands. Always use "exit" command when closing simplewallet to save current session's state. Otherwise, you will possibly need to synchronize your wallet again. Your wallet key is NOT under risk anyway. **********************************************************************
[wallet Tbc9gP]: 2018-Jan-02 21:50:34.051000 INFO Height 1, transaction a7bb9f4ad14af1e3198872f80473d6fb06b5212d01dc352c1575e234075c33dc, received resett 1 of 1 Sync from timestamp: 1514864938 2018-Jan-02 21:54:11.727000 INFO Reset completed successfully. 2018-Jan-02 21:54:12.457000 INFO Height 1, transaction a7bb9f4ad14af1e3198872f80473d6fb06b5212d01dc352c1575e234075c33dc, received 70.368475742208 Those were simply trouble shooting step, no grntee You want to try those 1st in this case I simple made new seeds for the configs on ubuntu 14.04 64 bit Feel free to test yourself using config file param 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=159.89.46.135:22850 seed-node=159.89.176.66:22850 It works great for me, so my problem is with the nodes? I could even mine a few and everything perfectly. If you like, let's talk about PM.
|
|
|
|
growarijo
Full Member
Offline
Activity: 251
Merit: 134
B2B Coin
|
|
January 03, 2018, 11:13:59 PM Last edit: January 03, 2018, 11:30:48 PM by growarijo |
|
Hi slb,
The secret/public key don't work, if I create a new address in walletd with a viewkey of another address anywere in the network I expect the balance to show up and the same address. When I do this now I get a totaly different address, everytime, and no balance visible.
Is this the expected behaviour of keys ?
BTW: Using forknote 2.1.2 after including zawy on forknote 2.1.1 introduces bugs, transactions get cancelled and previous transactions before zawy introduction are gone !!
Kr, Olivier @ b2bcoin.xyz
|
|
|
|
slb (OP)
|
|
January 04, 2018, 12:22:00 AM Last edit: January 04, 2018, 12:35:18 AM by slb |
|
Hi slb,
The secret/public key don't work, if I create a new address in walletd with a viewkey of another address anywere in the network I expect the balance to show up and the same address. When I do this now I get a totaly different address, everytime, and no balance visible.
Is this the expected behaviour of keys ?
BTW: Using forknote 2.1.2 after including zawy on forknote 2.1.1 introduces bugs, transactions get cancelled and previous transactions before zawy introduction are gone !!
Kr, Olivier @ b2bcoin.xyz
Where are you not seeing the transactions? simplwallet or walletd? Is 'reset' helping? There was a bug in 2.1.0 or 2.1.1 which require reset to be performed on update. Import/export wallets from walletd to simplewallet and vice versa works. I do it a couple times per day. You need the secret and view private keys
|
|
|
|
growarijo
Full Member
Offline
Activity: 251
Merit: 134
B2B Coin
|
|
January 04, 2018, 04:28:57 PM |
|
Hi slb,
The secret/public key don't work, if I create a new address in walletd with a viewkey of another address anywere in the network I expect the balance to show up and the same address. When I do this now I get a totaly different address, everytime, and no balance visible.
Is this the expected behaviour of keys ?
BTW: Using forknote 2.1.2 after including zawy on forknote 2.1.1 introduces bugs, transactions get cancelled and previous transactions before zawy introduction are gone !!
Kr, Olivier @ b2bcoin.xyz
Where are you not seeing the transactions? simplwallet or walletd? Is 'reset' helping? There was a bug in 2.1.0 or 2.1.1 which require reset to be performed on update. Import/export wallets from walletd to simplewallet and vice versa works. I do it a couple times per day. You need the secret and view private keys Hi slb, We use 2.1.1 because 2.1.2 deleted (cancelled) our transactions before zawy diff introduction. We use walletd in our web wallet as well as in our gui wallet. Reset is not helping, we get a different address everytime we import the secret/public key. We use secret/public keys from walletd and import them in walletd, but nothing happens even after reset. Kr, Olivier @ b2bcoin.xyz
|
|
|
|
NicNacCoin
|
|
January 04, 2018, 07:22:07 PM |
|
Hi slb,
The secret/public key don't work, if I create a new address in walletd with a viewkey of another address anywere in the network I expect the balance to show up and the same address. When I do this now I get a totaly different address, everytime, and no balance visible.
Is this the expected behaviour of keys ?
BTW: Using forknote 2.1.2 after including zawy on forknote 2.1.1 introduces bugs, transactions get cancelled and previous transactions before zawy introduction are gone !!
Kr, Olivier @ b2bcoin.xyz
Where are you not seeing the transactions? simplwallet or walletd? Is 'reset' helping? There was a bug in 2.1.0 or 2.1.1 which require reset to be performed on update. Import/export wallets from walletd to simplewallet and vice versa works. I do it a couple times per day. You need the secret and view private keys Hi slb, We use 2.1.1 because 2.1.2 deleted (cancelled) our transactions before zawy diff introduction. We use walletd in our web wallet as well as in our gui wallet. Reset is not helping, we get a different address everytime we import the secret/public key. We use secret/public keys from walletd and import them in walletd, but nothing happens even after reset. Kr, Olivier @ b2bcoin.xyz If it helps B2B, import using exported keys from wallet A will always create new wallet address B. This simply re-creates the wallet A transactions from the original wallet address into wallet address B. Both wallet address A and wallet address B are now able to view and spend any coins.
|
|
|
|
slb (OP)
|
|
January 04, 2018, 07:45:02 PM |
|
Hi slb,
The secret/public key don't work, if I create a new address in walletd with a viewkey of another address anywere in the network I expect the balance to show up and the same address. When I do this now I get a totaly different address, everytime, and no balance visible.
Is this the expected behaviour of keys ?
BTW: Using forknote 2.1.2 after including zawy on forknote 2.1.1 introduces bugs, transactions get cancelled and previous transactions before zawy introduction are gone !!
Kr, Olivier @ b2bcoin.xyz
Where are you not seeing the transactions? simplwallet or walletd? Is 'reset' helping? There was a bug in 2.1.0 or 2.1.1 which require reset to be performed on update. Import/export wallets from walletd to simplewallet and vice versa works. I do it a couple times per day. You need the secret and view private keys Hi slb, We use 2.1.1 because 2.1.2 deleted (cancelled) our transactions before zawy diff introduction. We use walletd in our web wallet as well as in our gui wallet. Reset is not helping, we get a different address everytime we import the secret/public key. We use secret/public keys from walletd and import them in walletd, but nothing happens even after reset. Kr, Olivier @ b2bcoin.xyz The problem is some timestamp/timestamp check in the wallet and/or the wallet software. Adding SYNC_FROM_ZERO=1 to the config file of the affected wallets should fix it, but I am not 100% sure
|
|
|
|
growarijo
Full Member
Offline
Activity: 251
Merit: 134
B2B Coin
|
|
January 04, 2018, 09:54:45 PM |
|
Hi slb,
The secret/public key don't work, if I create a new address in walletd with a viewkey of another address anywere in the network I expect the balance to show up and the same address. When I do this now I get a totaly different address, everytime, and no balance visible.
Is this the expected behaviour of keys ?
BTW: Using forknote 2.1.2 after including zawy on forknote 2.1.1 introduces bugs, transactions get cancelled and previous transactions before zawy introduction are gone !!
Kr, Olivier @ b2bcoin.xyz
Where are you not seeing the transactions? simplwallet or walletd? Is 'reset' helping? There was a bug in 2.1.0 or 2.1.1 which require reset to be performed on update. Import/export wallets from walletd to simplewallet and vice versa works. I do it a couple times per day. You need the secret and view private keys Hi slb, We use 2.1.1 because 2.1.2 deleted (cancelled) our transactions before zawy diff introduction. We use walletd in our web wallet as well as in our gui wallet. Reset is not helping, we get a different address everytime we import the secret/public key. We use secret/public keys from walletd and import them in walletd, but nothing happens even after reset. Kr, Olivier @ b2bcoin.xyz If it helps B2B, import using exported keys from wallet A will always create new wallet address B. This simply re-creates the wallet A transactions from the original wallet address into wallet address B. Both wallet address A and wallet address B are now able to view and spend any coins. Hi NicNacCoin, Some small but important info you gave me, thanks for that :-) Kr, Olivier @ b2bcoin.xyz
|
|
|
|
jonathan3306
Newbie
Offline
Activity: 86
Merit: 0
|
|
January 05, 2018, 03:47:40 AM |
|
Good luck with your coin I hope it does well.I will often focus on
|
|
|
|
CryptoCrazy1817
Newbie
Offline
Activity: 2
Merit: 0
|
|
January 06, 2018, 06:17:08 PM |
|
Hi I tried the cryptonote forking and got the following error while making file : cd /home/veda/vedacoin/build/release/src && /usr/bin/cmake -E cmake_link_script CMakeFiles/ConnectivityTool.dir/link.txt --verbose=1 /usr/bin/c++ -pthread -std=c++11 -Wall -Wextra -Wpointer-arith -Wundef -Wvla -Wwrite-strings -Werror -Wno-error=extra -Wno-error=unused-function -Wno-error=deprecated-declarations -Wno-error=sign-compare -Wno-error=strict-aliasing -Wno-error=type-limits -Wno-unused-parameter -Wno-error=unused-variable -Wno-error=undef -Wno-error=uninitialized -Wno-error=unused-result -Wlogical-op -Wno-error=maybe-uninitialized -Wno-error=clobbered -Wno-error=unused-but-set-variable -Wno-error=odr -Wno-reorder -Wno-missing-field-initializers -march=native -maes -O3 -DNDEBUG -Ofast -DNDEBUG -Wno-unused-variable -flto CMakeFiles/ConnectivityTool.dir/ConnectivityTool/ConnectivityTool.cpp.o -o connectivity_tool -rdynamic libCryptoNoteCore.a libCommon.a libLogging.a libCrypto.a libP2P.a libRpc.a libHttp.a libSerialization.a libSystem.a -lboost_system -lboost_filesystem -lboost_thread -lboost_date_time -lboost_chrono -lboost_regex -lboost_serialization -lboost_program_options -lboost_atomic -lpthread -lrt /usr/bin/ld: StreamTools.cpp.o: plugin needed to handle lto object /tmp/ccJfR21L.ltrans1.ltrans.o: In function `std::_Function_handler<void (), handle_request_stat(boost::program_options::variables_map&, unsigned long)::{lambda()#4}>::_M_invoke(std::_Any_data const&) [clone .lto_priv.444]': <artificial>:(.text+0xc83): undefined reference to `Common::write(Common::IOutputStream&, void const*, unsigned long)' <artificial>:(.text+0xcb6): undefined reference to `Common::write(Common::IOutputStream&, void const*, unsigned long)' <artificial>:(.text+0xe0b): undefined reference to `Common::write(Common::IOutputStream&, void const*, unsigned long)' <artificial>:(.text+0xe4e): undefined reference to `Common::write(Common::IOutputStream&, void const*, unsigned long)' /tmp/ccJfR21L.ltrans1.ltrans.o: In function `std::_Function_handler<void (), handle_request_stat(boost::program_options::variables_map&, unsigned long)::{lambda()#3}>::_M_invoke(std::_Any_data const&) [clone .lto_priv.446]': <artificial>:(.text+0x1178): undefined reference to `Common::write(Common::IOutputStream&, void const*, unsigned long)' /tmp/ccJfR21L.ltrans1.ltrans.o:<artificial>:(.text+0x11a5): more undefined references to `Common::write(Common::IOutputStream&, void const*, unsigned long)' follow /tmp/ccJfR21L.ltrans13.ltrans.o: In function `(anonymous namespace)::loadSection(Common::IInputStream&) [clone .lto_priv.382]': <artificial>:(.text+0xdae): undefined reference to `Common::read(Common::IInputStream&, unsigned char&)' <artificial>:(.text+0xde9): undefined reference to `Common::read(Common::IInputStream&, unsigned char&)' <artificial>:(.text+0xe3e): undefined reference to `Common::read(Common::IInputStream&, void*, unsigned long)' <artificial>:(.text+0xe99): undefined reference to `Common::read(Common::IInputStream&, void*, unsigned long)' <artificial>:(.text+0xec4): undefined reference to `Common::read(Common::IInputStream&, void*, unsigned long)' <artificial>:(.text+0xf00): undefined reference to `Common::read(Common::IInputStream&, unsigned char&)' <artificial>:(.text+0xf39): undefined reference to `Common::read(Common::IInputStream&, unsigned char&)' /tmp/ccJfR21L.ltrans20.ltrans.o: In function `(anonymous namespace)::loadValue(Common::IInputStream&, unsigned char) [clone .lto_priv.385]': <artificial>:(.text+0x487): undefined reference to `Common::read(Common::IInputStream&, unsigned char&)' <artificial>:(.text+0x4f4): undefined reference to `Common::read(Common::IInputStream&, void*, unsigned long)' <artificial>:(.text+0x534): undefined reference to `Common::read(Common::IInputStream&, void*, unsigned long)' <artificial>:(.text+0x564): undefined reference to `Common::read(Common::IInputStream&, void*, unsigned long)' <artificial>:(.text+0x5a4): undefined reference to `Common::read(Common::IInputStream&, void*, unsigned long)' <artificial>:(.text+0x5d4): undefined reference to `Common::read(Common::IInputStream&, void*, unsigned long)' /tmp/ccJfR21L.ltrans20.ltrans.o:<artificial>:(.text+0x5f4): more undefined references to `Common::read(Common::IInputStream&, void*, unsigned long)' follow /tmp/ccJfR21L.ltrans20.ltrans.o: In function `(anonymous namespace)::loadValue(Common::IInputStream&, unsigned char) [clone .lto_priv.385]': <artificial>:(.text+0x6cc): undefined reference to `Common::read(Common::IInputStream&, unsigned char&)' <artificial>:(.text+0x707): undefined reference to `Common::read(Common::IInputStream&, unsigned char&)' <artificial>:(.text+0x7a9): undefined reference to `Common::read(Common::IInputStream&, unsigned char&)' <artificial>:(.text+0x839): undefined reference to `Common::read(Common::IInputStream&, unsigned char&)' <artificial>:(.text+0x86c): undefined reference to `Common::read(Common::IInputStream&, void*, unsigned long)' /tmp/ccJfR21L.ltrans20.ltrans.o: In function `CryptoNote::KVBinaryInputStreamSerializer::KVBinaryInputStreamSerializer(Common::IInputStream&)': <artificial>:(.text+0x920): undefined reference to `Common::read(Common::IInputStream&, void*, unsigned long)' /tmp/ccJfR21L.ltrans21.ltrans.o: In function `(anonymous namespace)::writeElementName(Common::IOutputStream&, Common::StringView) [clone .constprop.205]': <artificial>:(.text+0xb7): undefined reference to `Common::write(Common::IOutputStream&, void const*, unsigned long)' <artificial>:(.text+0xc7): undefined reference to `Common::write(Common::IOutputStream&, void const*, unsigned long)' /tmp/ccJfR21L.ltrans21.ltrans.o: In function `Crypto::serialize(Crypto::Signature&, Common::StringView, CryptoNote::ISerializer&) [clone .constprop.191]': <artificial>:(.text+0x1366): undefined reference to `Common::write(Common::IOutputStream&, void const*, unsigned long)' <artificial>:(.text+0x1376): undefined reference to `Common::write(Common::IOutputStream&, void const*, unsigned long)' collect2: error: ld returned 1 exit status src/CMakeFiles/ConnectivityTool.dir/build.make:113: recipe for target 'src/connectivity_tool' failed make[3]: *** [src/connectivity_tool] Error 1 make[3]: Leaving directory '/home/veda/vedacoin/build/release' CMakeFiles/Makefile2:955: recipe for target 'src/CMakeFiles/ConnectivityTool.dir/all' failed make[2]: *** [src/CMakeFiles/ConnectivityTool.dir/all] Error 2 make[2]: Leaving directory '/home/veda/vedacoin/build/release' Makefile:94: recipe for target 'all' failed make[1]: *** [all] Error 2 make[1]: Leaving directory '/home/veda/vedacoin/build/release' Makefile:20: recipe for target 'build-release' failed make: *** [build-release] Error 2
|
|
|
|
PeterDove
Newbie
Offline
Activity: 1
Merit: 0
|
|
January 07, 2018, 06:16:33 PM |
|
Hi,
I would like to create a new coin based on cryptonote adding new information stored in transactions and some other changes. Is there anyone I could hire to work through the source code with me so that I get comfortable with the full design and where everything is before I start making changes?
Regards
Peter Dove
|
|
|
|
ssdnow
Newbie
Offline
Activity: 41
Merit: 0
|
|
January 07, 2018, 06:56:04 PM |
|
@NicNacCoin
I have returned for a new question, could you tell me that there is an additional configuration to be done to the server to create the node so that I can run as I should? or am I doing something wrong or the node that is configured in Vultr does not work for CryptoNote?.
The nodes that I have configured in Vultr run me but I do not know if I'm doing it right, because when connecting from my laptop with Windows it does not connect and simplewallet does not synchronize, when you mount the test node with my .conf everything is connected perfectly, Can you help me with the config of the serer in Vultr? I pass you by private user and password of Vultr you can enter with all the confidence and configure 2 nodez and you warn me to do the test from my lapto, you can pass me your wallet BTC for private donation, Thanks
|
|
|
|
connorwoods
Newbie
Offline
Activity: 33
Merit: 0
|
|
January 10, 2018, 11:28:47 AM |
|
nobody helps me set up the nodes in digitalocean, nothing costs, I have proposed to give a donation and nobody seems, I create 2 nodes just as the tutorial says, but the truth is I do not know if they are working, I still can not synchronize it seems that it does not work for me and nobody wants to win a few satos to configure the nodes, here I leave my images of the nodes and the local daemon with the wallet NODOShttps://imgur.com/PPsMMQKDaemon y Wallethttps://imgur.com/eInBMliAs you can see, if the Nodes are running well, the local Dameon does not pass any more so it does not synchronize and the wallet logic does not synchronize if there is no Daemon synchronizing, if someone is encouraged to help me in the Nodes, thank you very much. perhaps you should try some other algo for your coin cause it seems your not a very competent forknote dev. just saying. i'll be sure to steer clear of technetium
|
|
|
|
slb (OP)
|
|
January 10, 2018, 11:57:39 AM |
|
nobody helps me set up the nodes in digitalocean, nothing costs, I have proposed to give a donation and nobody seems, I create 2 nodes just as the tutorial says, but the truth is I do not know if they are working, I still can not synchronize it seems that it does not work for me and nobody wants to win a few satos to configure the nodes, here I leave my images of the nodes and the local daemon with the wallet NODOSDaemon y WalletAs you can see, if the Nodes are running well, the local Dameon does not pass any more so it does not synchronize and the wallet logic does not synchronize if there is no Daemon synchronizing, if someone is encouraged to help me in the Nodes, thank you very much. Just start mining and check if they have the same block height. Having the same config on all node is really all you need. You should delete any old blockchain folder with the same name of-course.
|
|
|
|
dina dini
|
|
January 10, 2018, 01:15:38 PM |
|
this project I think will be successful, from the team have been great and experienced in the field. good luck this project
|
|
|
|
andrewzhiwen123
Newbie
Offline
Activity: 8
Merit: 0
|
|
January 10, 2018, 04:34:35 PM |
|
When I transfer the coin, there is an error says 'Error: internal node error '. What does it mean?
|
|
|
|
|
|