[BTE] The Bytecoin Information Thread

[ProfMac]

I built an instance of ckpool and connected a 1.15 TH/s miner to it.  I mined 7 blocks in 8 hours.  This was configured as a standalone miner, so it was not suitable as a mining pool with many users.

I identified a configuration problem that created difficulties at block 58414.  I have pushed that problem back to block  58463.

The database support, ckdb, did not build effortlessly so I can't bring up multi-user support at the moment.

[1714169851]

1714169851

[1714169851]

1714169851

[1714169851]

1714169851

[1714169851]

1714169851

[movellan]

Don't you mean ahead from 58414to 58463?  You just can't jump 50 blocks ahead.

I built an instance of ckpool and connected a 1.15 TH/s miner to it.  I mined 7 blocks in 8 hours.  This was configured as a standalone miner, so it was not suitable as a mining pool with many users.

I identified a configuration problem that created difficulties at block 58414.  I have pushed that problem back to block  58463.

The database support, ckdb, did not build effortlessly so I can't bring up multi-user support at the moment.

[ProfMac]

Don't you mean ahead from 58414to 58463?  You just can't jump 50 blocks ahead.

I built an instance of ckpool and connected a 1.15 TH/s miner to it.  I mined 7 blocks in 8 hours.  This was configured as a standalone miner, so it was not suitable as a mining pool with many users.

I identified a configuration problem that created difficulties at block 58414.  I have pushed that problem back to block  58463.

The database support, ckdb, did not build effortlessly so I can't bring up multi-user support at the moment.

I mean, the code I am running treats some things differently after for block 58463 and before vs 58464 and after.  Previously the limit was 58414, I had forgotten that, and it made a problem.

[movellan]

OK, that makes it clearer. I see the block count currently went from 58414 to 58421. Did you mine those with the new code?

Don't you mean ahead from 58414to 58463?  You just can't jump 50 blocks ahead.

I built an instance of ckpool and connected a 1.15 TH/s miner to it.  I mined 7 blocks in 8 hours.  This was configured as a standalone miner, so it was not suitable as a mining pool with many users.

I identified a configuration problem that created difficulties at block 58414.  I have pushed that problem back to block  58463.

The database support, ckdb, did not build effortlessly so I can't bring up multi-user support at the moment.

I mean, the code I am running treats some things differently after for block 58463 and before vs 58464 and after.  Previously the limit was 58414, I had forgotten that, and it made a problem.

[ProfMac]

OK, that makes it clearer. I see the block count currently went from 58414 to 58421. Did you mine those with the new code?

I mined these blocks with a slightly modified version of the Ahmed-Bodi code that I modified about 18 months ago.  This is the same code that all of you have connected with on my server.  The version that actually produced and accepted blocks had some preliminary ideas for Hard Turtle technology.  Originally I had activated them at block 58414.  I no longer remember why I chose that block number, but at the time it seemed safely far in the future.  This was not a complete solution and it rejected some blocks.

I pushed the activation block back to 58463, the end of the current interval, so they are now de-activated.  This preliminary technology is mostly obsolete, but that version of the client does have some programming jigs in place to let me get a better view of how the code works.

This past month I made a version of the client that works with cpuminer from https://github.com/pooler/cpuminer.git and allows anyone to put their bytecoin 8-address in as either "user" or "pass."  This version exposes the getblocktemplate (GBT) interface.  Last month I bought a mining contract on eBay to test this before I made an announcement, and the test failed.  This left me with a client that anyone could use with a cpu miner, but not with an ASIC.  This may be advantageous as we are fighting against strip-mining, but I still wanted to be able to use contract miners.

I decided to look for a stratum server and test whether it would work with a contract from eBay and my modifications.  The  mining of blocks 58414 to 58421 was a test of the ckpool stratum server with bytecoin.  I bought an 8 hour mining contract on eBay.  The ckpool server is on a linode, so that my personal equipment is not exposed to lots of mischief.  This test succeeded in a solo-mining configuration as you saw, but has some other problems.

I haven't decided whether to look for other stratum servers, or make some modifications to ckpool.  I haven't found a good forum to discuss these choices, so I am going much of this project alone.  
----

Sigh, this is my first major C++ project.  At this point I think I have pretty good comprehension of the block-chain structure, the code of the source client, the trade offs involved in the various decisions, a specialized application concept for the near future, and I have made "Hello World" on the Android.  

My current thought is to completely re-mine the bytecoin block-chain leaving it at difficulty 1, with all existing transactions intact, and compatible with both the legacy client and the Hard Turtle client, forking at the next interval or so.  I believe this can be accomplished in a single evening using an eBay mining contract.  There are some administrative / design decisions that go along with this.  I may re-mine the block-chain several times, once for each decision, then "let the market decide."

I think I am at the point where I can publish some of the design alternatives for comment.  I wanted to be sure I was clear headed on the ideas before I did this, and also that I was knowledgeable enough that I could finish coding faster than someone with a hostile  agenda.

[movellan]

I'm not a coder, but I think I get the gist of what you are trying to do. I want to use the current client to mine, but am leery about what will happen when block 48464 is reached. I suspect Ahmed Bodi and his clones will be waiting to scarf all the blocks with large ASIC machines. This seems all the more likely as at current difficulty mining BTC with anything but an S9 or better is a waste of time and electricity. Will your code be in place and working when 48464 is reached?

BTW, I still cannot connect to any machine other than your two. Is any one else running a node besides you and I? TIA.

[ProfMac]

I'm not a coder, but I think I get the gist of what you are trying to do. I want to use the current client to mine, but am leery about what will happen when block 48464 is reached. I suspect Ahmed Bodi and his clones will be waiting to scarf all the blocks with large ASIC machines. This seems all the more likely as at current difficulty mining BTC with anything but an S9 or better is a waste of time and electricity. Will your code be in place and working when 48464 is reached?

BTW, I still cannot connect to any machine other than your two. Is any one else running a node besides you and I? TIA.

Oh, I have never been able to make reliable time-frame estimates.  I can pretty much turn on the Hard Turtle extensions now, but they are not fully tested.  The problem is that there is no windows client.  I have spent my time on the extensions, and assume that someone else can compile a windows client when the time comes, and if not I can do it at the end.

So long as we are the steadfast miners, all we have to do is refuse to honor strip mined blocks, and I can do that manually, so I am not really very worried.

[Sotashi_Nokamato]

I have a full node running and the block count is 58,421.

[Sotashi_Nokamato]

I have a full node running and the block count is 58,421.

I sold some coins. Thanks

[Sotashi_Nokamato]

WARNING: NODEJS APPS WALLET CRAWLERS.

I recently lost 35 coins after downloading from npm a module to connect to mongoDb. If anyone can donate me 70 coins I can get my lost coins back and some extra. This is a wonderful opportunity to help me in Christmas.

[Sotashi_Nokamato]

Giving away 100 coins to the first 100 addresses. Paste your address here

[Sotashi_Nokamato]

Hard Turtle Coin is near.

[steemium]

Just was checking the charts about Bytecoin
For example this https://stocksneural.net/crypto/BCN/USD
Now I think it's good to invest in all cryptocurrencies!

There under the chart I read that BCN was strted in July, 2012.
Is it really so old coin?

[ProfMac]

Just was checking the charts about Bytecoin
For example this https://stocksneural.net/crypto/BCN/USD
Now I think it's good to invest in all cryptocurrencies!

There under the chart I read that BCN was strted in July, 2012.
Is it really so old coin?

You might notice that this thread is annotated BTE.  It is not about BCN.
BTE was released on April 1, 2013.
Despite what the chart says, you may have a difficult time finding any public verifiable information about BCN prior to April 1, 2013.

[Sotashi_Nokamato]

Only 20 blocks to go.

[Sotashi_Nokamato]

17 blocks to go...

[Sotashi_Nokamato]

16 blocks to go...

[Sotashi_Nokamato]

13 Blocks to go...

Get your rigs ready!!!

[ProfMac]

13 Blocks to go...

Get your rigs ready!!!

Beginning at block 58464, a new block will have to be 3204 seconds newer than the median time of the previous 11 blocks for my node to accept it.

This is a change.  Previously, it only had to be 1 second newer.

This is 6 block-times of 534 seconds each.  This allows the difficulty to rise at 12.3% each interval (2016 blocks).  This is the historical rise calculated from the genesis block to block 469573 of the bitcoin chain.  At a target time of 600 seconds per block, the block would be 3600 seconds newer.

You may wish to allocate your hashpower with this in mind.

In addition, the timestamp cannot be more than 1 minute in the future.  Previously, this limit was 2 hours.

These are some preliminary changes toward Hard Turtle technology.

I will monitor the situation for the unexpected.

[Sotashi_Nokamato]

Go HARD TURTLE!