Bitcoin Forum
August 18, 2018, 05:01:32 PM *
News: Latest stable version of Bitcoin Core: 0.16.2  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 2 3 4 5 6 7 8 9 10 11 [12] 13 14 »  All
  Print  
Author Topic: [ANN] Forknote - create your own Cryptonote network  (Read 20283 times)
SafeCoins
Member
**
Offline Offline

Activity: 280
Merit: 19


View Profile WWW
December 31, 2017, 09:40:31 PM
 #221

I use the same .conf and I execute forknoted manual, and likewise the node does not run, I use the last compiled version of forknote, it really seems strange to me, I leave you PM so you can review something and you can help me please., Thanks

What are your firewall settings?  Is port 34250 open on the digitalocean servers?

What kind of message are they giving?
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1534611692
Hero Member
*
Offline Offline

Posts: 1534611692

View Profile Personal Message (Offline)

Ignore
1534611692
Reply with quote  #2

1534611692
Report to moderator
1534611692
Hero Member
*
Offline Offline

Posts: 1534611692

View Profile Personal Message (Offline)

Ignore
1534611692
Reply with quote  #2

1534611692
Report to moderator
PaperUnlimited
Newbie
*
Offline Offline

Activity: 9
Merit: 0


View Profile
January 02, 2018, 02:04:36 AM
 #222

Can someone tell me how to reset?

My latest efforts:

- I use the coin2.conf file to create the DB. https://bitcointalk.org/index.php?topic=1079306.msg26865189#msg26865189

- Then I print the genesis tx manually, this gives me the "outs: " and new genesis tx hex.

- I add the new tx hex to the coin2.conf, which creates a new coin3.conf.

- I use the coin3.conf to connect to the DB created with the coin2.conf, which seems to work except the simple wallet still has the "Failed to load: genesis block hash does not match stored state..." error.

- So I delete the old coin2.conf DB and recreate the DB using the coin3.conf.

- Everything connects without an error including simple wallet. But simple wallet still freezes and won't except any commands:

Code:
Wallet file name: coin1
password: ********
2018-Jan-01 18:45:51.227067 INFO    Loading wallet...
Sync from timestamp: 0
2018-Jan-01 18:45:51.349815 INFO    Opened wallet: walletaddress
2018-Jan-01 18:45:51.350168 INFO    **********************************************************************
Use "help" command to see the list of available commands.
**********************************************************************
help
help
exit
NicNacCoin
Sr. Member
****
Offline Offline

Activity: 274
Merit: 250



View Profile WWW
January 02, 2018, 05:31:30 PM
 #223

Can someone tell me how to reset?

My latest efforts:

- I use the coin2.conf file to create the DB. https://bitcointalk.org/index.php?topic=1079306.msg26865189#msg26865189

- Then I print the genesis tx manually, this gives me the "outs: " and new genesis tx hex.

- I add the new tx hex to the coin2.conf, which creates a new coin3.conf.

- I use the coin3.conf to connect to the DB created with the coin2.conf, which seems to work except the simple wallet still has the "Failed to load: genesis block hash does not match stored state..." error.

- So I delete the old coin2.conf DB and recreate the DB using the coin3.conf.

- Everything connects without an error including simple wallet. But simple wallet still freezes and won't except any commands:

Code:
Wallet file name: coin1
password: ********
2018-Jan-01 18:45:51.227067 INFO    Loading wallet...
Sync from timestamp: 0
2018-Jan-01 18:45:51.349815 INFO    Opened wallet: walletaddress
2018-Jan-01 18:45:51.350168 INFO    **********************************************************************
Use "help" command to see the list of available commands.
**********************************************************************
help
help
exit
Which verison of forknote is used?
IMO Forknote 2.1.2 (core Bytecoin 2.1.2) has some issues w/simplewallet hanging on launch (sync wont display like other verison) and on exit (wont close)
forknote wallet v2.1.1.1245 () seems to run smooth but does get buggy at times

try this
https://wiki.bytecoin.org/wiki/Simplewallet_JSON_RPC_API#reset_2

We created a network for a customer recently (PreMine) and had to the same issue but were able to come up with a workaround to get the daemon to correct the Block Reward Mismatch message

ssdnow
Jr. Member
*
Offline Offline

Activity: 37
Merit: 0


View Profile
January 02, 2018, 07:39:02 PM
 #224



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:57677 INC] Exception in connectionHandler: TcpConnection::read
2018-Jan-02 19:36:24.809138 WARNING [207.246.65.66:46316 INC] Exception in connectionHandler: TcpConnection::read
2018-Jan-02 19:36:26.811479 WARNING [207.246.65.66:33803 INC] Exception in connectionHandler: TcpConnection::read
2018-Jan-02 19:36:28.814101 WARNING [207.246.65.66:46890 INC] Exception in connectionHandler: TcpConnection::read
2018-Jan-02 19:36:30.817393 WARNING [207.246.65.66:35115 INC] Exception in connectionHandler: TcpConnection::read
2018-Jan-02 19:36:32.819522 WARNING [207.246.65.66:38274 INC] Exception in connectionHandler: TcpConnection::read
2018-Jan-02 19:36:34.823345 WARNING [207.246.65.66:38731 INC] Exception in connectionHandler: TcpConnection::read
2018-Jan-02 19:36:36.825551 WARNING [207.246.65.66:54882 INC] Exception in connectionHandler: TcpConnection::read
2018-Jan-02 19:36:38.828191 WARNING [207.246.65.66:54645 INC] Exception in connectionHandler: TcpConnection::read
2018-Jan-02 19:36:40.832488 WARNING [207.246.65.66:51703 INC] Exception in connectionHandler: TcpConnection::read
2018-Jan-02 19:36:42.834446 WARNING [207.246.65.66:44667 INC] Exception in connectionHandler: TcpConnection::read
slb
Hero Member
*****
Offline Offline

Activity: 598
Merit: 501


View Profile WWW
January 02, 2018, 10:47:53 PM
 #225

Can someone tell me how to reset?

My latest efforts:

- I use the coin2.conf file to create the DB. https://bitcointalk.org/index.php?topic=1079306.msg26865189#msg26865189

- Then I print the genesis tx manually, this gives me the "outs: " and new genesis tx hex.

- I add the new tx hex to the coin2.conf, which creates a new coin3.conf.

- I use the coin3.conf to connect to the DB created with the coin2.conf, which seems to work except the simple wallet still has the "Failed to load: genesis block hash does not match stored state..." error.

- So I delete the old coin2.conf DB and recreate the DB using the coin3.conf.

- Everything connects without an error including simple wallet. But simple wallet still freezes and won't except any commands:

Code:
Wallet file name: coin1
password: ********
2018-Jan-01 18:45:51.227067 INFO    Loading wallet...
Sync from timestamp: 0
2018-Jan-01 18:45:51.349815 INFO    Opened wallet: walletaddress
2018-Jan-01 18:45:51.350168 INFO    **********************************************************************
Use "help" command to see the list of available commands.
**********************************************************************
help
help
exit
Which verison of forknote is used?
IMO Forknote 2.1.2 (core Bytecoin 2.1.2) has some issues w/simplewallet hanging on launch (sync wont display like other verison) and on exit (wont close)
forknote wallet v2.1.1.1245 () seems to run smooth but does get buggy at times

try this
https://wiki.bytecoin.org/wiki/Simplewallet_JSON_RPC_API#reset_2

We created a network for a customer recently (PreMine) and had to the same issue but were able to come up with a workaround to get the daemon to correct the Block Reward Mismatch message

You should use 2.1.2. The previews version has some serious bugs, especially if you use zawy difficulty algorithm. 

Forknote (create cryptocurrenies easy) - https://bitcointalk.org/index.php?topic=1079306.0
Dashcoin (anonymous cryptocurrency) - https://bitcointalk.org/index.php?topic=1020627.0
ssdnow
Jr. Member
*
Offline Offline

Activity: 37
Merit: 0


View Profile
January 02, 2018, 11:29:15 PM
 #226



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:57677 INC] Exception in connectionHandler: TcpConnection::read
2018-Jan-02 19:36:24.809138 WARNING [207.246.65.66:46316 INC] Exception in connectionHandler: TcpConnection::read
2018-Jan-02 19:36:26.811479 WARNING [207.246.65.66:33803 INC] Exception in connectionHandler: TcpConnection::read
2018-Jan-02 19:36:28.814101 WARNING [207.246.65.66:46890 INC] Exception in connectionHandler: TcpConnection::read
2018-Jan-02 19:36:30.817393 WARNING [207.246.65.66:35115 INC] Exception in connectionHandler: TcpConnection::read
2018-Jan-02 19:36:32.819522 WARNING [207.246.65.66:38274 INC] Exception in connectionHandler: TcpConnection::read
2018-Jan-02 19:36:34.823345 WARNING [207.246.65.66:38731 INC] Exception in connectionHandler: TcpConnection::read
2018-Jan-02 19:36:36.825551 WARNING [207.246.65.66:54882 INC] Exception in connectionHandler: TcpConnection::read
2018-Jan-02 19:36:38.828191 WARNING [207.246.65.66:54645 INC] Exception in connectionHandler: TcpConnection::read
2018-Jan-02 19:36:40.832488 WARNING [207.246.65.66:51703 INC] Exception in connectionHandler: TcpConnection::read
2018-Jan-02 19:36:42.834446 WARNING [207.246.65.66:44667 INC] Exception in connectionHandler: TcpConnection::read

@slb hi.
How about this node? it's already working?
NicNacCoin
Sr. Member
****
Offline Offline

Activity: 274
Merit: 250



View Profile WWW
January 03, 2018, 12:44:44 AM
 #227


Code:
Wallet file name: coin1
password: ********
2018-Jan-01 18:45:51.227067 INFO    Loading wallet...
Sync from timestamp: 0
2018-Jan-01 18:45:51.349815 INFO    Opened wallet: walletaddress
2018-Jan-01 18:45:51.350168 INFO    **********************************************************************
Use "help" command to see the list of available commands.
**********************************************************************
help
help
exit
Which verison of forknote is used?
IMO Forknote 2.1.2 (core Bytecoin 2.1.2) has some issues w/simplewallet hanging on launch (sync wont display like other verison) and on exit (wont close)
forknote wallet v2.1.1.1245 () seems to run smooth but does get buggy at times

try this
https://wiki.bytecoin.org/wiki/Simplewallet_JSON_RPC_API#reset_2

We created a network for a customer recently (PreMine) and had to the same issue but were able to come up with a workaround to get the daemon to correct the Block Reward Mismatch message

You should use 2.1.2. The previews version has some serious bugs, especially if you use zawy difficulty algorithm. 
SLB, can you list serious bugs found in v2.1.1(released this on Sep 11, 2017) and corrected with v2.1.2(released this on Oct 18, 2017)
https://github.com/forknote/forknote/releases reports only
  • simplewallet issues fixed
  • daemon sync issue fixed for some coins
  • minor bug fixes
though https://github.com/forknote/forknote/issues seems to reflect far more issues with v2.1.2.
also for clarification zawy difficulty algorithm is a param option and not a requirement correct?

ssdnow
Jr. Member
*
Offline Offline

Activity: 37
Merit: 0


View Profile
January 03, 2018, 12:54:58 AM
 #228

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.
NicNacCoin
Sr. Member
****
Offline Offline

Activity: 274
Merit: 250



View Profile WWW
January 03, 2018, 01:19:30 AM
 #229

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

ssdnow
Jr. Member
*
Offline Offline

Activity: 37
Merit: 0


View Profile
January 03, 2018, 02:24:31 AM
 #230

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.
NicNacCoin
Sr. Member
****
Offline Offline

Activity: 274
Merit: 250



View Profile WWW
January 03, 2018, 02:59:54 AM
 #231

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.

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
Jr. Member
*
Offline Offline

Activity: 37
Merit: 0


View Profile
January 03, 2018, 03:27:07 AM
 #232

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.



I did it step by step as you explained to me and I still have the same error message in simplewallet

Code:
C:\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
Sr. Member
****
Offline Offline

Activity: 274
Merit: 250



View Profile WWW
January 03, 2018, 03:58:42 AM
 #233

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.



I did it step by step as you explained to me and I still have the same error message in simplewallet

Code:
C:\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
Code:
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
Jr. Member
*
Offline Offline

Activity: 37
Merit: 0


View Profile
January 03, 2018, 04:28:47 AM
 #234

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.



I did it step by step as you explained to me and I still have the same error message in simplewallet

Code:
C:\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
Code:
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 Offline

Activity: 239
Merit: 134


B2B Coin


View Profile WWW
January 03, 2018, 11:13:59 PM
 #235

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
Hero Member
*****
Offline Offline

Activity: 598
Merit: 501


View Profile WWW
January 04, 2018, 12:22:00 AM
 #236

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

Forknote (create cryptocurrenies easy) - https://bitcointalk.org/index.php?topic=1079306.0
Dashcoin (anonymous cryptocurrency) - https://bitcointalk.org/index.php?topic=1020627.0
growarijo
Full Member
***
Offline Offline

Activity: 239
Merit: 134


B2B Coin


View Profile WWW
January 04, 2018, 04:28:57 PM
 #237

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
Sr. Member
****
Offline Offline

Activity: 274
Merit: 250



View Profile WWW
January 04, 2018, 07:22:07 PM
 #238

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
Hero Member
*****
Offline Offline

Activity: 598
Merit: 501


View Profile WWW
January 04, 2018, 07:45:02 PM
 #239

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

Forknote (create cryptocurrenies easy) - https://bitcointalk.org/index.php?topic=1079306.0
Dashcoin (anonymous cryptocurrency) - https://bitcointalk.org/index.php?topic=1020627.0
growarijo
Full Member
***
Offline Offline

Activity: 239
Merit: 134


B2B Coin


View Profile WWW
January 04, 2018, 09:54:45 PM
 #240

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

Pages: « 1 2 3 4 5 6 7 8 9 10 11 [12] 13 14 »  All
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!