May jump back into this. Seeing a bit of excitement. Where can you find the latest miner / wallet for BTE (bytecoin)? Btw, did we end up changing the name? Someone suggest OBC (original bytecoin). I'm kind of more partial to just calling it "BYTE", or "BYTE Classic".

Yeah I'm pretty busy at the moment.
Elderly parents are such a worry and time consuming. 

Don't think so, very quiet.

Don't think so, very quiet.

You cannot mine directly to a bytecoin core node, so I have set up a public solo mining pool for easier mining.
There is currently three running, each with different starting diffs:

Diff         1:       stratum+tcp://bytecoin.pool.chainspy.com:3001
Diff   1000:       stratum+tcp://bytecoin.pool.chainspy.com:3004
Diff 10000:       stratum+tcp://bytecoin.pool.chainspy.com:3005

Set your username to your bytecoin address with any or even no worker extension, and any password.
eg:
If you enter an invalid address you will be rejected.
2% fee for using the pool which is sent to bytec1q9ny3xycmfrfev2xquun64sunvvh2zlx2gn63xz

Remember this is a solo mining, so you only get a reward if you're the one to find a valid block.
Difficulty is currently at 7790.512516801227 which is really low. 55.77GH/s gives an average 10 minute block time.

Yes. Most users won't need to use that file anyway.
You can create it if you wish to set some configuration settings, like RPC user and password for example on startup.


I'm not sure. This has happened to mine as well, when I just tested the migration tool.
I think the old wallet contained some old format of addresses, perhaps just some in very early "pubkey" format used in earlier mining; and the migration has converted them over.
You can just ignore them or create new addresses if your receiving in future. Don't think there's an option to delete them.


I don't think it's suppose to. It's more like a sending address book list, not a transaction list.
This is where a browser block explorer comes in handy. (See next post).
Remember a bytecoin transaction can contain many inputs, (and many outputs), so it might not be just one sending address that was used.


Probably guessing the easiest way is to make sure that in Settings > Options > Network; UPnP and NAT-PMP mapping are checked. Oh, and allow the incoming connections setting as well of course.
Then go into your home ISP router/modem and check one or both UPnP and NAT-PMP are switched on inside that too.
The port should be automatically opened for you.

Don't spent too much time on this. If you can't do it, don't worry about it.

Received. Thank you.

This is a common problem. Difficulty gets blasted into orbit, then abandoned. The blockchain then gets stuck.

Why not start mining with me while the diff is currently really low? It's only 5436.852907928366 now, which is about 38.92GH/s for a 10 minute block target.

Point your miner at
stratum+tcp://bytecoin.pool.chainspy.com:3001
username = <your bytecoin address>
password = x

Try https://www.miningrigrentals.com/ if you don't have your own equipment.
You need to rent a SHA256 rig. Really cheap. In fact, you'll struggle to find a rig with such a low hashrate.

Don't blast 100TH/s at it.

Pretty quiet. Only a few of us about. I've got ipv4 and ipv6 nodes running 24/7 at:


Most home internet providers give out dynamic ipv4 addresses (change at random times), that shouldn't be a problem. If you running a node 24/7 then it would be helpful to open up port 6333 (presuming you've kept the default port) so outside nodes can connect to yours; otherwise your firewall will block them.

If you want to to donate; but really I'm the only one mining at the moment so it's not like I've got a shortage of bytecoins. 
bytec1qj4vj5l0y83cvklvgv58mfurp63es5dujhyfstd



Not that I know of. None of the links on bytecoin.biz work anymore. I'll try to get one up and running, but probably be cobbled together quickly and buggy, so expect too much.


By the way, does anyone know who runs bytecoin.biz?

That's weird. You can do a rescanblockchain command from the Window -> Console to look for historic transactions, but this should of been executed when your restored the wallet anyway. Make sure you have the correct wallet selected if you have multi-wallets opened, from the pull-down bar at the top. The pull-down isn't there if only 1 wallet is opened.

The method I used to move my coins over however was:

Created a fresh new wallet in v27.
Backed up this new wallet.
Created a new base58 (legacy) address inside this wallet.
Copied this address to a txt file and saved.
Closed v27 client.
Opened V0.8 client.
Sent a few coins to the new v27 base58 (legacy) address.
Closed v0.8.
Opened v27 and checked had received coins.

Once I checked it with a few coins, I repeated this time with the remaining balance.

v0.8 can only understand base58 (legacy) addresses (starting with number , it won't understand segwit and taproot Bech32 ones, so you won't be able to send to those from v0.8

To import a legacy wallet, select File > Restore Wallet from the top left menu.

You can then File > Migrate it to the new format.

Okay, let's give this one a try.
https://github.com/bytecoin-crypto/bytecoin/releases/tag/v27.0.2

Up, running and synched. Good show. Now, how do I import the v 0.8.1 wallet?

Think I've figured it out now. 
There's both data and config files. I've only changed the data path to bytecoin and not the config path.
I'm pretty busy this weekend, but should get a new binary out this week, after some testing.

The data directory structure for v27 is totally different now from v0.8. Seems to me v27 is attempting to access the old \Roaming\Bytecoin directory and getting confused because v0.8 stuff is inside it.

What I would do is rename the current v0.8 \Bytecoin directory (say to something like Bytecoin_backup), so the \Bytecoin directory doesn't exist. Then when v27 starts up, it will create a new Bytecoin directory and use it's own structure. Of course v0.8 won't work then, but any old wallet(s) should be able to be imported once v27 is working.

And alternate idea would be to add the -datadir=<dir> parameter to bytecoin-qt.exe, for example bytecoin-qt.exe -datadir=C:\mydir
However, you would need to include this everytime you start it up, or it will look somewhere else for the data directory.

Don't forget to backup your wallet if you start deleting directories.

Thank you for letting me know.
I've downloaded, unzipped and run bytecoin-qt.exe in my desktop, laptop and also a fresh Windows 11 development environment in a VM; and it starts syncing with the bytecoin network fine.

I'm using Windows 11 64bit Home edition, version 23H2. I'm unable to replicate the error this end.

I'm afraid I'm going to have to trouble you for more in-depth information what's happening. Does it start syncing or just doesn't start at all? Have you tried a custom datadir path? What version of Windows are you using etc...

Classic "works on my machine" problem.

Windows bytecoin v27.0.1 binaries have been built and released.

I don't own bytecoin.biz, so I've have to put them on the github release page for download:
https://github.com/bytecoin-crypto/bytecoin/releases/tag/v27.0.1

bc1c8f9db7696953511c12464a888357a1543dce5c79d5ca4cf7a7d167377f04  bytecoin-27.0.1-win64.zip

Well it's been a while since I've done any cross compiling (window binary built from inside linux), but I'll give it a go.
Give me a little while to figure it out, I'm confident I can do it.

I don't really understand.

It is the original mainnet blockchain. I only mined onto the end of the stalled chain (stalled for years); first of all using the outdated version 0.8.1 and later when upgraded it to the modern 27.0 version. 1:1 copy still. (Except a few technical changes, such as addresses, magic bytes, ports etc...)

Any coins you, and anyone else, earned/mined years ago will still be spendable.

Originally I tried to merge the latest bitcoin version into both of these. But v27 is so far away from v0.8, with thousands of git commits; I just got tied up in knots.

I tried a different approach. Forked bitcoin v27.0 and just made the bytecoin changes to that; genesis block, port numbers etc...
Found this way much easier. Hopefully moving up to v28.0 should be easy, with just a smaller number of commits to merge.

Mainnet is the original chain still of course, block 75306 at time of writing. But I never had a copy of the testnet chain, so I started a new one; block 21907 currently. It's only the testnet so I guess that doesn't matter.

So the answer to your question is neither I guess. It's based on bitcoin v27.0