[BTE] The Bytecoin Information Thread

[Sotashi_Nokamato]

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.

Again kudos to you ProfMac, for a one man band you're doing a simply amazing job!

Kudos prof!

[Sotashi_Nokamato]

Where can I buy BTE? Current price is 0.001? So, 100 coins is 1 cent? That's a deal!

[achillez]

Where can I buy BTE? Current price is 0.001? So, 100 coins is 1 cent? That's a deal!

Don't get BTE (BitSerial) confused with the original BTE (ByteCoin). The work in this thread is to get the original ByteCoin back online.

[achillez]

Where can I buy BTE? Current price is 0.001? So, 100 coins is 1 cent? That's a deal!

Don't get BTE (BitSerial) confused with the original BTE (ByteCoin). The work in this thread is to get the original ByteCoin back online.

This reminds me - if we bring ByteCoin back from the dead what should it be called? Maybe OBC = Original ByteCoin ?

[ProfMac]

Where can I buy BTE? Current price is 0.001? So, 100 coins is 1 cent? That's a deal!

Don't get BTE (BitSerial) confused with the original BTE (ByteCoin). The work in this thread is to get the original ByteCoin back online.

This reminds me - if we bring ByteCoin back from the dead what should it be called? Maybe OBC = Original ByteCoin ?

I'm considering this path.
http://iounote.vima.austin.tx.us

[Sotashi_Nokamato]

Where can I buy BTE? Current price is 0.001? So, 100 coins is 1 cent? That's a deal!

Don't get BTE (BitSerial) confused with the original BTE (ByteCoin). The work in this thread is to get the original ByteCoin back online.

This reminds me - if we bring ByteCoin back from the dead what should it be called? Maybe OBC = Original ByteCoin ?

I'm considering this path.
http://iounote.vima.austin.tx.us

I can help you with your HTML CSS and Javascript.

[movellan]

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.

[ProfMac]

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]

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.  

[movellan]

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=<username>
rpcpassword=<password>
rpctimeout=30
rpcallowip=127.0.0.1
rpcport=6332

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]

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=<username>
rpcpassword=<password>
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]

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?

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=<username>
rpcpassword=<password>
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]

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?

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=<username>
rpcpassword=<password>
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]

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]

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]

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


Up and running at 173.239.240.19.

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.

[snazir]

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...!

[ProfMac]

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=<be mindful for your system configuration, you may be using 6332 for the standard BTE client>
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"))
        ;

[movellan]

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.

[ProfMac]

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.