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

Somewhere in storage, I have an Avalon 2, 83 GH/s.  We are already using air conditioning in Austin.  I can rent hashes, if I run a stratum pool.  I figured the cost to mine to the next difficulty change, and decided to write code to fix the problem once and for all instead.

I think it is prudent to be skeptical of all things blockchain.

Having said that, I notice these things:

The coin was strip-mined.
It was stagnant for a really long time.
Without change, it remains vulnerable to a strip-mining attack when we revive it.
I own several existing coins.  The blockchain needs to be viable for them to have value.
This is a serious matter.  A coin that does not produce blocks for 18 months is effectively dead.

I have thought since 2014 about how to protect against strip mining.  I am convinced I have a solution, and I have been coding with strong focus and watching the calendar.  I want my solution to work well enough when I release it, and I don't want to release enough information that someone can scoop me with an implementation that goes in a direction that is philosophically incompatible to me.  That is a delicate dance in cryptocoin country.

So I am releasing my ideas fairly slowly, when the horizon to release an implementation is within view.  I think that, any time now, I can make a code release to GitHub and things will be transparent.  Then the community can make an informed decision.  A bit of my work is on gitgub now, including the mechanism to build a VM to compile the code in, a mechanism to report the SHA-256 of the resulting binaries for crowd-sourced validation.  I do need to clean up the VM generation a bit to solve the "genesis VM" problem.  I was working on that when PersonalLife took some attention, and no one has seemed very interested, so it is on the ToDo list starved for attention.

What I can say for now is that there is a live testing block chain at bte.vima.austin.tx.us:26333  As detailed in an earlier post, the existing client can download this blockchain.  N.B. "As detailed in an earlier post."  As a testing block chain, it has warts and knotholes and changes whimsically.  As soon as I get the code located at https://github.com/a-mcintosh/expt-block1 back ported into the 0.8.1 BTE client's mining code and supported in the getblocktemplate command I will take a few day breather.  I may make a code release then, or I may decide to get the distributed mining pool working first.  LOL.  My estimate for that is "last month."

The difficulty of this coin is LOW right now. All that is needed now is to feed to "Locust" and let them skyrocket tje current difficulty.

Prof, appreciate all the hard work you are putting into BTE, but I am dead set against any fork. Ahmed Bodi tried to go that that route so he could gain control of mining. Please explain further. TIA.

I have the opinion that 3 factors should go into the difficulty adjustment.
This opinion is captured in new technology I am calling Hard Turtle.


1.  The long term mining rate of the coin.

• 600 sec / block since genesis
• adjust the difficulty_0 according to this factor

2.  The interval mining rate of the coin.  This is the standard difficulty adjustment after 2016 blocks, difficulty or difficulty_1.
3.  The time since MedianPrevTime. 

• This should also be 600 sec/block. 
• The value of those difficulty increases (will be) in a calculated table, and called difficulty_2.
• The actual behavior is described very well by a Poisson distribution.  See the link several posts above.
• This can be control without an audit trail by changing the target hash reported in getminingtemplate
• The value of those difficulty increases (will be) in a calculated table, and called difficulty_2.

4.  The new difficulty will be the cube root of difficulty_0 * difficulty_1 * difficulty_2. 

• This is easy to calculate using nBits.
• After calculation, it will be clipped to a factor of 4x change, as is the current practice.

5.  These changes will dovetail very nicely with a distributed mining pool. 

• The difficulty items are nearing the end of development and testing.
• The mining pool has some development work.

6.  The old client will work with these changes for a few Intervals (epochs of 2016 blocks) but as the difficulty starts to steady out, the nBits numbers will eventually differ and cause a hard fork.

7.  I am making the hard fork stronger, and repairing the entire blockchain. 

• This will result in the same transactions as before, but a blockchain with a difficulty near 1.
• It will take fewer hashes to mine 58,000 blocks at difficulty 1 than 300 blocks at difficulty 1,000,000.
• No data will be lost.
• Timestamps will be very similar.
• It took a devil of a long time to work out the logic of mining blocs nunc pro tunc.
• The blockchain repair will occur with a client that also supports the mining pool.  Alternate blocks will generate new rewards, so it will be earn as you repair.

8.  It turns out, I can include a coinbase block for a bitcoin block as well, while I am doing the repair.  Go to the survey a few postings above, and include any bitcoin address that you have been paid to in a coinbase block :-).

This coins is 5 years old!

{"block":"58137"} 

Many blocks found in the past few hours.

{"block":"58135"}

EDIT:

http://34.233.28.56:3000/getblockcount

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

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.

Add this line in your bytecoin.conf file

addnode=52.205.185.242:6333

Also my mining info shows this:

Prof,

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

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.

[/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]

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.

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

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.

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.

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.