[BTE] The Bytecoin Information Thread

[cpu6502]

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

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

Code:

178.79.133.60:6333
[2a01:7e00:e000:86b:4ad3:2c87:17a3:1a36]:6333

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.

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

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

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?

[movellan]

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

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

Code:

178.79.133.60:6333
[2a01:7e00:e000:86b:4ad3:2c87:17a3:1a36]:6333

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.

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

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

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?

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://bitcointalk.org/index.php?topic=500987.msg5518311#msg5518311

from 10 years ago.

[cpu6502]

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

Received. Thank you.

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.

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.

[movellan]

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

Received. Thank you.

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.

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.

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.

[cpu6502]

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

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.

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?

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.

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.

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.

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

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.

[cpu6502]

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.

[movellan]

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

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.

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?

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.

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.

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.

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

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.

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.

[manyproblemsonesolution]

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.

Hi can I ask how did you calculate that? I want to start mining today following your instructions

[cpu6502]

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.

Hi can I ask how did you calculate that? I want to start mining today following your instructions

The formula is quite easy:
time = difficulty * (2^32) / hashrate

Time is in seconds, which is 600 for a 10 minute block target.
2^32 = 4294967296



Rearranging the formula for your question gives us:
hashrate = difficulty * (2^32) / time

[manyproblemsonesolution]

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.

Hi can I ask how did you calculate that? I want to start mining today following your instructions

The formula is quite easy:
time = difficulty * (2^32) / hashrate

Time is in seconds, which is 600 for a 10 minute block target.
2^32 = 4294967296



Rearranging the formula for your question gives us:
hashrate = difficulty * (2^32) / time

Awesome!!! Thanks for the response I'll take a look into that site to see what can I rent out, ill keep you posted

[manyproblemsonesolution]

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.

Hi can I ask how did you calculate that? I want to start mining today following your instructions

The formula is quite easy:
time = difficulty * (2^32) / hashrate

Time is in seconds, which is 600 for a 10 minute block target.
2^32 = 4294967296



Rearranging the formula for your question gives us:
hashrate = difficulty * (2^32) / time

Hi sorry for asking but would you be so kind to donate some BTE?

bytec1qslzzx4c6rmw09f36g4kk08c73g5ehgzlvcp2lt

 

[cpu6502]

Hi sorry for asking but would you be so kind to donate some BTE?

bytec1qslzzx4c6rmw09f36g4kk08c73g5ehgzlvcp2lt

 

Where's the fun in that? The mining diff is so ridiculously low, just mine some...

I'll give you a load of testnet BTE ones if you want though.

[manyproblemsonesolution]

Cool you're right let me ask you one more question if you don't mind?

You think this rig works based on your calculations?

https://www.miningrigrentals.com/rigs/225385

Can you provide screenshots/tutorial on how to completely setup the mining process?

Super appreciate it and all your efforts into this

[cpu6502]

Yes that's a sha256 rig, it will work.


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

[cpu6502]

49 BTE for finding a block (which you will), and 1 BTE fee taken for pool usage.

[byteswap]

I see this warning when running bytecoind -daemon

getblockchaininfo                {                                               "chain": "main",                              "blocks": 78296,                              "headers": 78296,                             "bestblockhash": "000000000000414e890fcd8d87efa8066f50b3c624476338973b4f5422ca8a97",        "difficulty": 5436.852907928366,              "time": 1717950999,                           "mediantime": 1717937749,                     "verificationprogress": 1,                    "initialblockdownload": false,                "chainwork": "000000000000000000000000000000000000000000000004d904d9bfbf7fc3e7",            "size_on_disk": 52907765,                     "pruned": false,                              "warnings": "This is a pre-release test build - use at your own risk - do not use for mining or merchant applications"                  }

Any problems with that warning?

[cpu6502]

I see this warning when running bytecoind -daemon

getblockchaininfo                {                                               "chain": "main",                              "blocks": 78296,                              "headers": 78296,                             "bestblockhash": "000000000000414e890fcd8d87efa8066f50b3c624476338973b4f5422ca8a97",        "difficulty": 5436.852907928366,              "time": 1717950999,                           "mediantime": 1717937749,                     "verificationprogress": 1,                    "initialblockdownload": false,                "chainwork": "000000000000000000000000000000000000000000000004d904d9bfbf7fc3e7",            "size_on_disk": 52907765,                     "pruned": false,                              "warnings": "This is a pre-release test build - use at your own risk - do not use for mining or merchant applications"                  }

Any problems with that warning?

You built Bytecoin from the main branch instead of a version release. The warning isn't present if you checked out v27.0.2 and built from there.
I think there is only one git commit difference between the two anyway, so don't worry about the message.

[manyproblemsonesolution]

I see this warning when running bytecoind -daemon

getblockchaininfo                {                                               "chain": "main",                              "blocks": 78296,                              "headers": 78296,                             "bestblockhash": "000000000000414e890fcd8d87efa8066f50b3c624476338973b4f5422ca8a97",        "difficulty": 5436.852907928366,              "time": 1717950999,                           "mediantime": 1717937749,                     "verificationprogress": 1,                    "initialblockdownload": false,                "chainwork": "000000000000000000000000000000000000000000000004d904d9bfbf7fc3e7",            "size_on_disk": 52907765,                     "pruned": false,                              "warnings": "This is a pre-release test build - use at your own risk - do not use for mining or merchant applications"                  }

Any problems with that warning?

You built Bytecoin from the main branch instead of a version release. The warning isn't present if you checked out v27.0.2 and built from there.
I think there is only one git commit difference between the two anyway, so don't worry about the message.

You got it!! Thanks again

[cpu6502]

Just a tip for the person mining lots of coins to the same address at the moment.
You need to regularly consolidate those coins to another address once matured.
The reason behind this is because trying to send coins from an address with hundreds/thousands of inputs will inevitably be too large a transaction size to send.

[byteswap]

Just a tip for the person mining lots of coins to the same address at the moment.
You need to regularly consolidate those coins to another address once matured.
The reason behind this is because trying to send coins from an address with hundreds/thousands of inputs will inevitably be too large a transaction size to send.

That's really good to know great info. What other things can be done to improve this coins usability and wide spread?