[BTE] The Bytecoin Information Thread

[movellan]

Prof, here are some entries from the log file. There are no timestamps to the log entries so I don't know if these are recent or ancient. Is the port correct? again my conf file is:

server=1
rpcuser=<username>
rpcpassword=<password>
rpctimeout=30
rpcallowip=127.0.0.1
rpcport=6332
seednode=seed.bte.vima.austin.tx.us

trying connection 86.25.234.163:6333 lastseen=29691.3hrs
trying connection 95.180.104.243:6333 lastseen=23063.8hrs
trying connection 104.200.154.16:6333 lastseen=3220.1hrs
Flushed 9999 addresses to peers.dat  101ms
trying connection 201.153.167.64:6333 lastseen=1733.5hrs
trying connection 100.70.104.230:6333 lastseen=4840.1hrs

No luck yet. Any ideas appreciated.

Thanks, Prof. Post some active nodes and I'll paste them in and see what happens.

I am just moving toward all IPv6.  No change on Bytecoin's part.  I do have an IPv4 port open, however.

I show a connection from a new IP at 2018-03-04 11:43:22 (GMT) this morning that has 58126 blocks.  It disconnected without sending its new blocks to me.  Perhaps that was you.  It is not accepting reconnect requests from my node.

The old seed nodes are dead.  I think new node information has to be given to get connected.  You can do that on command line or the bytecoin.conf file, either one.

I won't post someone else's addresses without permission.  Some people are touchy about that.
Try my address again, I'm monitoring it today to be sure it is stable.

If you are running Linux, I wish you would post the output of the following command.  Perhaps someone else can post the windows command equivalent.  
It turns out that you cannot use onlynet=ipv6 & seednode= at the same time, the client only tries IPv4 seednodes.


dig seed.bte.vima.austin.tx.us


In addition, you may post your address, either IPv4 or IPv6, and I or someone can try to connect to you.  You may private message this to me if, for some reason, you do not want to post it.  Of course, this option works best if you leave the client running for a while.

Also, dig through debug.log and look for things that have [2001:470:b8ac:: or 67.198.113.220 in them.

[ProfMac]

Prof, here are some entries from the log file. There are no timestamps to the log entries so I don't know if these are recent or ancient. Is the port correct? again my conf file is:

server=1
rpcuser=<username>
rpcpassword=<password>
rpctimeout=30
rpcallowip=127.0.0.1
rpcport=6332
seednode=seed.bte.vima.austin.tx.us

trying connection 86.25.234.163:6333 lastseen=29691.3hrs
trying connection 95.180.104.243:6333 lastseen=23063.8hrs
trying connection 104.200.154.16:6333 lastseen=3220.1hrs
Flushed 9999 addresses to peers.dat  101ms
trying connection 201.153.167.64:6333 lastseen=1733.5hrs
trying connection 100.70.104.230:6333 lastseen=4840.1hrs

If you are running Linux, I wish you would post the output of the following command.  Perhaps someone else can post the windows command equivalent.  
It turns out that you cannot use onlynet=ipv6 & seednode= at the same time, the client only tries IPv4 seednodes.


dig seed.bte.vima.austin.tx.us


In addition, you may post your address, either IPv4 or IPv6, and I or someone can try to connect to you.  You may private message this to me if, for some reason, you do not want to post it.  Of course, this option works best if you leave the client running for a while.

Also, dig through debug.log and look for things that have [2001:470:b8ac:: or 67.198.113.220 in them.

If you add

logtimestamps=1

to your bytecoin.conf file, there should be timestamps (in GMT) in your logfile.

I run on the standard port, and your rpcport line is ok.

None of those addresses from your attempted connections show up in my log.  I wonder if you have an old peers.dat file.  You might rename it to something else, to be sure that it initializes to the nodes that were recently good on my machine.

I have also given the command
addnode bte.vima.austin.tx.us onetry
on the internal command line after the client has started.

[movellan]

Prof, running the internal command gave me ONE connection which is running now. Any way to do the same to get more connections? Can I see the IP of the one connection I now have? TIA.

If you add

logtimestamps=1

to your bytecoin.conf file, there should be timestamps (in GMT) in your logfile.

I run on the standard port, and your rpcport line is ok.

None of those addresses from your attempted connections show up in my log.  I wonder if you have an old peers.dat file.  You might rename it to something else, to be sure that it initializes to the nodes that were recently good on my machine.

I have also given the command
addnode bte.vima.austin.tx.us onetry
on the internal command line after the client has started.

[ProfMac]

Prof, running the internal command gave me ONE connection which is running now. Any way to do the same to get more connections? Can I see the IP of the one connection I now have? TIA.

You can type 'help' on the internal command line, and it will give a list of commands.

getpeerinfo

will give information on the currently connected peers.

I do have a new connection, perhaps this is you.  The new connection advertises 58126 blocks, but it never delivers them to my node.

If I run
getblockhash 58122
I get back
0000000000000664b482018d10447f73ba9fdb675740494c73635505d8a46418


If you did rename or delete peers.dat, as I instructed, before you started up your node, it should begin connecting to all the nodes that my node thinks are active the next time you connect.

[ProfMac]

There are IP addresses that show up in my debug.log that my node can't connect back to.  I think the software automatically shares all the IPs that it learns about, so that the blocks get distributed and are safe.  I think we need more active nodes and connections at the moment.

So, some commands that you might want to AVOID except under special circumstances are

listen=0 
connect=<ip>
noconnect
connect=0

[movellan]

Prof,

Yes, it must be my node as it has last block as 58126.

getblockhash 58122 returns:

0000000000000f92d9816911e63b3dc6e0186c07bda22a926e86a8d4050fec05

get blockinfo reurns:


?
[
{
"addr" : "bte.vima.austin.tx.us",
"services" : "00000001",
"lastsend" : 1521883449,
"lastrecv" : 1521883449,
"conntime" : 1521883448,
"version" : 70001,
"subver" : "/Satoshi:0.8.1.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 58122,
"banscore" : 0
}
]
 
Any idea why my block height is well above the one you show? How do we get more nodesup?

There are IP addresses that show up in my debug.log that my node can't connect back to.  I think the software automatically shares all the IPs that it learns about, so that the blocks get distributed and are safe.  I think we need more active nodes and connections at the moment.

So, some commands that you might want to AVOID except under special circumstances are

listen=0 
connect=<ip>
noconnect
connect=0

[ProfMac]

Prof,

 
Any idea why my block height is well above the one you show? How do we get more nodesup?

My electricity was off for a few hours today.  When I booted back up just now, some new nodes connected, and my block count went from 58122 to 58126.  However, there was a re-organization back 16 blocks, and the newest block now is back to Sat Aug 27 01:26:49 2016 instead of last week.  Apparently the nodes have been fragmented for some time.

I think it is important that everyone try to accept connections from each other as well as reach out to each other.  If I get hit by a truck or something and no one else allows each other to connect, the network is still vulnerable.

[movellan]

Prof,

Hopefully you will stay on the green side of the grass for a while yet. I'll continue my node connecting to yours, however some items I use require a daily reboot so I can't always retain the same IP. I'd be glad for any interested to send their node IP via private mail and I will add to my list of nodes.

What I don't understand is when connecting to your node why mine is not reading the list of nodes you have. Any help appreciated.

Prof,

My electricity was off for a few hours today.  When I booted back up just now, some new nodes connected, and my block count went from 58122 to 58126.  However, there was a re-organization back 16 blocks, and the newest block now is back to Sat Aug 27 01:26:49 2016 instead of last week.  Apparently the nodes have been fragmented for some time.

I think it is important that everyone try to accept connections from each other as well as reach out to each other.  If I get hit by a truck or something and no one else allows each other to connect, the network is still vulnerable.

[sudnokpok]

Personally, I have yet to see a change that any alt-coins have made that I can unequivocally regard to be an improvement over Bitcoin at this point (although some of the changes may prove to be so, eventually).  So to me, if I want an additional currency, the best choice is an identical fork of Bitcoin.

[movellan]

Yes, Bitcoin is best. I tried BTE back when it started because it was a clone of Bitcoin. Mined some when BTC network difficulty went too high. Would like to get see it going again.

Personally, I have yet to see a change that any alt-coins have made that I can unequivocally regard to be an improvement over Bitcoin at this point (although some of the changes may prove to be so, eventually).  So to me, if I want an additional currency, the best choice is an identical fork of Bitcoin.

[ProfMac]

Prof,

Hopefully you will stay on the green side of the grass for a while yet. I'll continue my node connecting to yours, however some items I use require a daily reboot so I can't always retain the same IP. I'd be glad for any interested to send their node IP via private mail and I will add to my list of nodes.

What I don't understand is when connecting to your node why mine is not reading the list of nodes you have. Any help appreciated.

In Linux, you might start an investigation session with

Code:

export EPOCH=`date '+%s'`
mv debug.log debug-$EPOCH.log
mv peers.dat peers-$EPOCH.dat
bytecoin-qt &

Then, it should create a new peers.dat that only has the peers it gets from my node.

Then you can search debug.log for
"trying connection"

and that should show the nodes it is trying to connect to.

[movellan]

Prof,

Can't do the linux thing. Can you private mail some node IPs to try adding manually? TIA.

In Linux, you might start an investigation session with

Code:

export EPOCH=`date '+%s'`
mv debug.log debug-$EPOCH.log
mv peers.dat peers-$EPOCH.dat
bytecoin-qt &

Then, it should create a new peers.dat that only has the peers it gets from my node.

Then you can search debug.log for
"trying connection"

and that should show the nodes it is trying to connect to.

[ProfMac]

Prof,

Can't do the linux thing. Can you private mail some node IPs to try adding manually? TIA.

In Linux, you might start an investigation session with

Code:

export EPOCH=`date '+%s'`
mv debug.log debug-$EPOCH.log
mv peers.dat peers-$EPOCH.dat
bytecoin-qt &

Then, it should create a new peers.dat that only has the peers it gets from my node.

Then you can search debug.log for
"trying connection"

and that should show the nodes it is trying to connect to.

I'll look for some.  Meanwhile, manually move those files out of the directory that they are in. 
Someone who can check a windows environment, please post the details of where that directory is located.

[movellan]

Prof,

Not sure what files you want to move but in Windoze are located at:

C:\Users\User\AppData\Roaming\Bytecoin

Have been deleting debug.log and peers.dat before each time I try a new config. Added addresses first using console "onetry" and next adding to Bytecoin.conf. Your node is still the only one standing. Attempted nodes have log entry such as:

2018-03-26 06:07:08 trying connection xxx.xxx.xxx.xxx:6333 lastseen=395012.3hrs
2018-03-26 06:07:13 connection timeout

HTH. Thanks.

In Linux, you might start an investigation session with

Code:

export EPOCH=`date '+%s'`
mv debug.log debug-$EPOCH.log
mv peers.dat peers-$EPOCH.dat
bytecoin-qt &

Then, it should create a new peers.dat that only has the peers it gets from my node.

Then you can search debug.log for
"trying connection"

and that should show the nodes it is trying to connect to.

[/quote]

I'll look for some.  Meanwhile, manually move those files out of the directory that they are in. 
Someone who can check a windows environment, please post the details of where that directory is located.

[/quote]

[movellan]

Prof,

Looks like someone found a new block, 58127. I'm still showing a connection to only your node. No others detected.

[bluecoin_devops]

Add this line in your bytecoin.conf file

addnode=52.205.185.242:6333

Also my mining info shows this:

Code:

{
    "version" : 80101,
    "protocolversion" : 70001,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 58128,
    "connections" : 3,
    "proxy" : "",
    "difficulty" : 1056741.21450361,
    "testnet" : false,
    "keypoololdest" : 1514085788,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "errors" : ""
}

[ProfMac]

Add this line in your bytecoin.conf file

addnode=52.205.185.242:6333

Also my mining info shows this:

I can put you in the dns entry at seed.bte.vima.austin.tx.us if you give permission.


edited 2018-03-29

I decided your post was permission enough.  I have added your address to the
DNS entry.  It is live and tested with dig.

So, I recommend using the following line in your bytecoin.conf or the command line.

Code:

seednode=seed.bte.vima.austin.tx.us

[bluecoin_devops]

Building a blockchain API for this coin.

You can test here.

http://34.233.28.56:3000/getmininginfo

http://34.233.28.56:3000/getnewaddress

[bluecoin_devops]

EDIT:

http://34.233.28.56:3000/getblockcount

[Sotashi_Nokamato]

Many blocks found in the past few hours.

{"block":"58135"}