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

Got v 27 up and running on another computer. You should e able to see it on your machines. Still having problems getting my old hardware to work with v 27 but continue keeping at it.

Don't like enabling UPnP on any windoze  machine. Too dangerous.

Checked some older BTC core builds and it did have deletion for receiving address. Don't know when that changed.

Got a very quick Bytecoin Block Explorer up and running.
https://chainspy.com

It's very basic and boring. No fancy graphics.
Don't expect too much. Make too many requests and it will probably crash the site.

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.

Considering setting up mining on another machine I have. Need to set up v 27 and check out some antique miners I have for suitability. Will get back to you on this.

A few questions,

1) V 27 did not create a bytecoin.conf file in AppData\Roaming\Bytecoin. Is this normal?

2) V 27 entered a bunch of bech 32, etc addresses in the Receiving Addresses window in addition to the Base 58 addresses that were added when the old wallet was recovered and migrated. Where did these come from? Can I delete these?

3) Can't see the sending address that was used when I made the send. The address showing in the Sending Addresses window is the same as the address I sent the coin to.

4) How do I open port 6333 to receive incoming connections?
 
TIA.

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

Sent some BTE and it now has 5 of 6 confirmations so looks like send is working OK as long as mining is ongoing.

Never knew who was running bytecoin.biz but always suspected it was Ahmed Bodi or one of his associates. He used to point what was then a big ASIC at BTE and ran up well over 100k coins. Quite annoying at the time as the difficulty used to skyrocket and if one didn't have lots of hash power one had to wait for the difficulty to drop again to do any mining.

Look at this,

https://bitcointalksearch.org/topic/m.5518311

from 10 years ago.

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?

All OK now. Had to use an older version wallet for restore and migrate. Totals look OK, transactions seem to have transferred correctly.

I only have 2 peers connected. Are any others available?

The machine this node is on gets its IP address changed at least once daily. Will this be a problem?  TIA and thanks for your efforts in getting this coin up and running again. Please provide an address where I can leave a token of my appreciation. Now all we need is to get it listed on an exchange.

P.S. Is there a block explorer for BTE available?

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 8), it won't understand segwit and taproot Bech32 ones, so you won't be able to send to those from v0.8

Followed instructions, wallet recovered and migrated, but appears empty, no transactions recorded. I know Ihave coins in the old wallet. Any ideas appreciated.

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

Sounds good.

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.

Renaming the  Appdata\Roaming\Bytecoin directory doesn't work. Believe me, v 27 is trying to get it's data from the AppData\Roaming\BITCOIN directory. It's NOT looking in AppData\Roaming\BYTECOIN. It's looking at the WRONG directory for data. it's not going to work unless it can see the correct directory.

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

Running Windows 10 Pro, x64 ver 22H2, 32G ram lots of HD space.

Error message is displayed on startup,

Error: Cannot obtain a lock on data directory C:
\Users\(computer name)\AppData\Roaming\Bitcoin. Bytecoin Core is probably already
running.

Have a Bitcoin Core running on that AppData directory. Current Bytecoin Core 0.8.1 is on \AppData\Roaming\Bytecoin. Copied the Bytecoin v 0.8.1 directory into C:\Program Files. Then copied over the v 27 bin to C;Program Files.

How do I get v 27 to look for it's files on \AppData\Roaming\Bytecoin?

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.

There appears to be an error in your compilation. Bytecoin Core is looking in AppData\Roaming\Bitcoin for it's data instead of AppData\Roaming\Bytecoin.