[BTE] The Bytecoin Information Thread - page 21.

ProfMac

legendary

Activity: 1246

Merit: 1002

Quote from: movellan on March 24, 2018, 07:00:42 AM

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

full member

Activity: 368

Merit: 100

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?

Quote from: ProfMac on March 24, 2018, 01:20:15 AM

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=
noconnect
connect=0

ProfMac

legendary

Activity: 1246

Merit: 1002

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=
noconnect
connect=0

ProfMac

legendary

Activity: 1246

Merit: 1002

Quote from: movellan on March 23, 2018, 05:22:08 AM

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.

movellan

full member

Activity: 368

Merit: 100

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.

Quote from: ProfMac on March 22, 2018, 05:00:43 PM

Quote from: movellan on March 22, 2018, 01:23:36 AM

Quote from: ProfMac on March 20, 2018, 04:42:55 PM

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

legendary

Activity: 1246

Merit: 1002

Quote from: movellan on March 22, 2018, 01:23:36 AM

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=
rpcpassword=
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

Quote from: ProfMac on March 20, 2018, 04:42:55 PM

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

full member

Activity: 368

Merit: 100

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=
rpcpassword=
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

Quote from: ProfMac on March 20, 2018, 04:42:55 PM

Quote from: movellan on March 20, 2018, 03:05:30 AM

No luck yet. Any ideas appreciated.

Quote from: ProfMac on March 04, 2018, 03:19:22 PM

Quote from: movellan on March 04, 2018, 03:05:13 PM

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

legendary

Activity: 1246

Merit: 1002

Quote from: movellan on March 20, 2018, 03:05:30 AM

No luck yet. Any ideas appreciated.

Quote from: ProfMac on March 04, 2018, 03:19:22 PM

Quote from: movellan on March 04, 2018, 03:05:13 PM

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.

movellan

full member

Activity: 368

Merit: 100

No luck yet. Any ideas appreciated.

Quote from: ProfMac on March 04, 2018, 03:19:22 PM

Quote from: movellan on March 04, 2018, 03:05:13 PM

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.

ProfMac

legendary

Activity: 1246

Merit: 1002

Testing is going well, but slowly. I am developing on Ubuntu, and I don't have any idea which operating systems people are actively using. Here's a survey to help me find out.

https://docs.google.com/forms/d/e/1FAIpQLSee_fE7gUBgU2r2jjc-vAERrN5jiz9WALJW0HG0cR6_akK5KA/viewform?usp=pp_url&entry.2092041095=Linux+--+Ubuntu

My test blockchain is frequently exposed
bte.vima.austin.tx.us:26333

Some intersting items for your bytecoin.conf file:

Code:

# -- Sample items in bytecoin.conf

# -- of course you timestamp all your logs, why is this even an option?
logtimestamps=1

# -- rpc
rpcport=
port=26333

# -- Test Node
addnode=bte.vima.austin.tx.us

# -- additional items
txindex=1
reindex=1
checkpoints=0

In case you compile your own source:
This number changes from time to time.

Code:

// 2018-03-17
   static MapCheckpoints mapCheckpoints =
   boost::assign::map_list_of
( 1, uint256 ("0x00000000119a96aae529bd633fa52b79cca70f7fd9d3b667c98b7811029da579"))
   ;

snazir

copper member

Activity: 252

Merit: 0

I Would Like Some help to build a windows Client. I Have Built in the current bitcoin build environment using Debian, But I'm not at all sure if I would attract any Users. does anyone know if there are any BTc pools still out there running these Days, I Think it would be great if we all showed the Coinplorer guys some love for providing this service, and if we let them know how great Bytecoin is, However this basic idea is to accept the block with the highest difficulty instead of the block that is first. Then, to keep accepting blocks for at least an hour since the 6th previous block. so for a one man band you're doing a Simply Amazing job...!

movellan

full member

Activity: 368

Merit: 100

Update: more than a week gone by and no connections as yet. Any ideas appreciated.

Up and running at 173.239.240.19.

Quote from: ProfMac on March 04, 2018, 03:19:22 PM

Quote from: movellan on March 04, 2018, 03:05:13 PM

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.

ProfMac

legendary

Activity: 1246

Merit: 1002

Quote from: movellan on March 04, 2018, 03:05:13 PM

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.

movellan

full member

Activity: 368

Merit: 100

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.

ProfMac

legendary

Activity: 1246

Merit: 1002

Quote from: movellan on March 04, 2018, 06:08:15 AM

Perhaps IPv6 is part of the problem. I don't use 6 at all, in fact I block any IPv6 traffic for my own safety reasons. Are you saying that 0.081 will no longer work without an IPv6 connection?

Quote from: ProfMac on March 03, 2018, 03:49:05 PM

Quote from: movellan on March 03, 2018, 12:54:19 AM

No luck so far. Here's my bytecoin.conf that worked forever until the network quit. Adding the seednode line doesn't make any difference; still no connections. What changes will I have to make to get things working again? TIA.

server=1
rpcuser=
rpcpassword=
rpctimeout=30
rpcallowip=127.0.0.1
rpcport=6332

There is something a little unstable in my IPv6 configuration, and I drop the address sometimes.
Please try again, or PM (DM) me your ip and I'll see if I can connect to you.

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.

movellan

full member

Activity: 368

Merit: 100

Perhaps IPv6 is part of the problem. I don't use 6 at all, in fact I block any IPv6 traffic for my own safety reasons. Are you saying that 0.081 will no longer work without an IPv6 connection?

Quote from: ProfMac on March 03, 2018, 03:49:05 PM

Quote from: movellan on March 03, 2018, 12:54:19 AM

No luck so far. Here's my bytecoin.conf that worked forever until the network quit. Adding the seednode line doesn't make any difference; still no connections. What changes will I have to make to get things working again? TIA.

server=1
rpcuser=
rpcpassword=
rpctimeout=30
rpcallowip=127.0.0.1
rpcport=6332

There is something a little unstable in my IPv6 configuration, and I drop the address sometimes.
Please try again, or PM (DM) me your ip and I'll see if I can connect to you.

ProfMac

legendary

Activity: 1246

Merit: 1002

Quote from: movellan on March 03, 2018, 12:54:19 AM

No luck so far. Here's my bytecoin.conf that worked forever until the network quit. Adding the seednode line doesn't make any difference; still no connections. What changes will I have to make to get things working again? TIA.

server=1
rpcuser=
rpcpassword=
rpctimeout=30
rpcallowip=127.0.0.1
rpcport=6332

There is something a little unstable in my IPv6 configuration, and I drop the address sometimes.
Please try again, or PM (DM) me your ip and I'll see if I can connect to you.

movellan

full member

Activity: 368

Merit: 100

No luck so far. Here's my bytecoin.conf that worked forever until the network quit. Adding the seednode line doesn't make any difference; still no connections. What changes will I have to make to get things working again? TIA.

server=1
rpcuser=
rpcpassword=
rpctimeout=30
rpcallowip=127.0.0.1
rpcport=6332

Quote from: ProfMac on March 01, 2018, 09:03:51 PM

Quote from: movellan on February 25, 2018, 03:20:16 AM

I have an old 0.81 BTE wallet that I have tried with some of the bytecoin.conf changes posted here, but it still will not connect to other nodes. Any help appreciated. TIA.

I am online 24/7 with about 85% uptime. I have 1 steady peer connection, also an IPv6 address. I received block 58120 dated Wed Feb 28 09:58:31 2018 (CST, UTC-6)

You can use the address seed.bte.vima.austin.tx.us to try to seed some addresses. When people give permission to me, I will add their address to this seed list.

Add the following line to your bytecoin.conf file:

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

ProfMac

legendary

Activity: 1246

Merit: 1002

Quote from: ProfMac on February 11, 2018, 02:32:40 PM

Quote from: Sotashi_Nokamato on February 10, 2018, 04:02:08 PM

Quote from: ProfMac on February 08, 2018, 02:55:21 AM

No. All of the approaches that try to adjust the difficulty after the fact are working in the wrong part of the system.
I tentatively have a way to exclude blocks that are strip mined, and never include them in the block chain at all. Then the difficulty does not have such wild excursions.

Can you share your code here so I can better understand. Thanks

I am doing some testing. When I am satisfied, I will put the source on GitHub and make an announcement in this thread. I hoped to be finished by last April.

I am repairing the Bytecoin (BTE) block-chain. That is, I am re-calculating the block headers, but keeping all the transactions, and keeping the timestamps similar. The process is not ready to release yet. However, you can peek in and see the progress. This repaired block-chain will occasionally be deleted and re-created during the forthcoming development and testing.

I will have multiple streams of blocks in the repaired chain.
The Legacy blocks will be there, but the timestamps will be adjusted so that they appear to occur not significantly faster than each 10 minutes.
The Legacy blocks, in order to prevent double-spend attacks, will not be usable in transactions until the entire repair is finished.
A stream of new blocks, not yet present, will be there. When I get the stratum pool up and running, this stream will act pretty much like any other coin, and you can mine and spend from it.
I have not made a final decision, but I may keep the difficulty at 1 for the entire repaired chain.
There will be a transition from the time that the chain is repaired, to business as usual on the fully repaired chain.

To peek in:

make an empty directory ~/.bytecoin/26332
add a custom bytecoin.conf
do not add peers.dat
Encrypt your wallet. Back it up. Be cautious.
please don't use addnode, or otherwise connect to clients running the legacy block-chain.

Code:

checkpoints=0
connect=bte.vima.austin.tx.us:26332
listen=0

I have code named my technology Hard Turtle.

ProfMac

legendary

Activity: 1246

Merit: 1002

Quote from: movellan on February 25, 2018, 03:20:16 AM

I have an old 0.81 BTE wallet that I have tried with some of the bytecoin.conf changes posted here, but it still will not connect to other nodes. Any help appreciated. TIA.

I am online 24/7 with about 85% uptime. I have 1 steady peer connection, also an IPv6 address. I received block 58120 dated Wed Feb 28 09:58:31 2018 (CST, UTC-6)

You can use the address seed.bte.vima.austin.tx.us to try to seed some addresses. When people give permission to me, I will add their address to this seed list.

Add the following line to your bytecoin.conf file:

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

Topic: [BTE] The Bytecoin Information Thread - page 21. (Read 80193 times)