Quote from: cshelswell on August 01, 2018, 08:08:30 PM

Hi prof,

It's been a while since I've actively mined and compiled a wallet. I helped out with BTE way back and still have a wallet.

I've got a virtual Ubuntu box setup and would like to see what's in my wallet and, for now, if you think it's still viable do some GPU / CPU mining.

Just wondering what the best repo is to compile from?

Thanks

"difficulty" : 1056741.21450361
I think that with a 2nd generation ASIC, 83 GH/s, it would take 15 hours or so to mine a block. CPU is currently not useful.
My work all uses the ahmed-bodi repo on GitHub, as mentioned a post or two above. I have a Ubuntu 14.04 virtual machine that I build from scripts. It is public on my GitHub

However ... that possibly controversial thing I mentioned ...

I am going to re-mine the entire block-chain. All the existing transactions will be preserved, including the coinbase transactions.
This will take fewer hashes than mining the current difficulty for the next few hundred blocks. The difficulty should be 1 when all 58,330 or so Legacy blocks have been repair-mined.
Most of my development time has been spent on this aspect of the project. It has been "a learning experience."
Most of the block timestamps will be very similar to the Legacy timestamps.
I will interleave the Legacy blocks (even number, starting with Genesis at 0) with new Repair blocks. The new repair blocks will have nuanced payout structure.
  25% for the current miner, to pay for their help in repairing the Legacy blockchain.
  25% for the people who are registered on that Google form I posted a while back, to create some excitement.
  50% at half the value of the previous Legacy block payouts, to pay me for my development time.

I am almost ready to open this up to the public. Initially, it will be at difficulty 1.0. In addition, I have put in support for "Legacy Time" so that a high hash rate miner will churn out blocks, but the timestamps, which are all Legacy and in the past, will conform to the newer stringent Hard Turtle rules. I expect complete chaos when this is launched, with many people doing things, ahem, that I haven't thought of.

It turns out that it is possible to mine a Legacy *bitcoin* block into this new blockchain.

ROTFL. If you have a bitcoin wallet from 2013, and you do a dumpprivkey on your address, and you take that output and you do a importprivkey to the bytecoin client, you get a bytecoin 8 address. And then, if I/we re-mine a bitcoin coinbase that pays that address into a new BTE-HT block, all the payouts appear as 8 addresses and your imported 8 address works. The transaction has the identical transaction ID. Yes, I have tested this. Yes, I was skeptical. Yes, I read the C++ code really, really carefully. I am toying with the idea of re-mining all the bitcoin coinbase blocks that pay out to address 18bLcVkviErQi75zB8X39jZXxHNpSZggdC. This will give me 80 BTE, not that much really, but it will bring in a huge community of other bitcoin miners who mined at Eligius. This should help revive the coin.

https://docs.google.com/forms/d/e/1FAIpQLSd8yfSnu9pInRhHkJWxNkawb8b-0T5L5TaFpVG52PqbVk1H9A/viewform?usp=sf_link

I am currently working on a small number of tasks.
1. Modify the RPC login so that the username is a bytecoin address and the password is ignored, and multiple people can log in. This will allow miners to run the Garzik minerd miner and use blocktemplate. I will run this client in a virtual machine and the community can mine from it.
2. There are some race conditions when I fetch a Legacy block via RPC and build the internal structures to support blocktemplate and also the internal CPU miner. My experience with race conditions is not in the C++ environment, so this is slow slogging. I want it to be reliable before the chaos begins.
3. For whatever misguided reason, I stopped and made a "vanity address" generator task and put it into the miner. I needed a break, and I learned some more of the data structures in the client, so it was not totally misguided. I am actually quite pleased with this, in a guilty cat that ate the canary sort of way.
4. I also had to master git for the Hard Turtle effort. It has been a busy year. I think that I can publish "orthogonal" branches, for example the vanity address, the Genesis-difficulty adjustment, the standard difficulty modifications, the resurrected code to make a new Genesis block. I suspect that a clever person can "git merge" whichever of these orthogonal branches they want in a clean way. This is at the edge of my current expertise with git, and will take a bit of effort to disentangle all the merges from this year into these orthogonal tasks. I may decide this is too much effort, and just publish my branch as it is.

Most academics really try to clean up all the mess of development before they publish. I am transitioning from finishing a few tasks to editing and publishing the work, and a managed roll-out.