[BTE] The Bytecoin Information Thread - page 2.

cpu6502

jr. member

Activity: 24

Merit: 0

Quote from: movellan on June 19, 2024, 05:02:11 AM

Quote from: cpu6502 on May 07, 2024, 04:34:52 PM

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:

Code:

cgminer -o stratum+tcp://bytecoin.pool.chainspy.com:3004 -u bytec1q9ny3xycmfrfev2xquun64sunvvh2zlx2gn63xz.0 -p x

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.

Could not get CGMiner to work with my old mining hardware, but now have it working with BFGMiner running at about 18 GH on your
"bytecoin.pool.chainspy.com:3001" pool. Can you check and see if everything looks OK? TIA

Yes, working fine.
With 18 GH/s you should find a block every 38 minutes on average.

movellan

full member

Activity: 368

Merit: 100

Quote from: cpu6502 on May 07, 2024, 04:34:52 PM

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:

Code:

cgminer -o stratum+tcp://bytecoin.pool.chainspy.com:3004 -u bytec1q9ny3xycmfrfev2xquun64sunvvh2zlx2gn63xz.0 -p x

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.

Could not get CGMiner to work with my old mining hardware, but now have it working with BFGMiner running at about 18 GH on your
"bytecoin.pool.chainspy.com:3001" pool. Can you check and see if everything looks OK? TIA

byteswap

newbie

Activity: 6

Merit: 0

Diff adjusted recently

byteswap

newbie

Activity: 6

Merit: 0

I have to agree with you on that. Lets keep the chain safe

cpu6502

jr. member

Activity: 24

Merit: 0

Quote from: byteswap on June 11, 2024, 07:37:18 AM

Quote from: cpu6502 on June 11, 2024, 05:56:05 AM

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?

I think the most important thing is security of the blockchain. Without that, the coin is worthless.
Network hashrate is only about 80GH/s. It would be trivial at the moment to 51% attack the chain.

We need more consistent decentralized hashrate. Don't be surprised if someone blasts the coin's diff into orbit, then abandons it, leaving the chain stuck.

movellan

full member

Activity: 368

Merit: 100

You got it!! Thanks again
[/quote]

How about posting your node IP so the rest of us can connect?

byteswap

newbie

Activity: 6

Merit: 0

Quote from: cpu6502 on June 11, 2024, 05:56:05 AM

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?

cpu6502

jr. member

Activity: 24

Merit: 0

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.

manyproblemsonesolution

newbie

Activity: 11

Merit: 0

Quote from: cpu6502 on June 09, 2024, 12:07:02 PM

Quote from: byteswap on June 09, 2024, 11:45:27 AM

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

jr. member

Activity: 24

Merit: 0

Quote from: byteswap on June 09, 2024, 11:45:27 AM

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.

byteswap

newbie

Activity: 6

Merit: 0

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

jr. member

Activity: 24

Merit: 0

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

cpu6502

jr. member

Activity: 24

Merit: 0

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

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

manyproblemsonesolution

newbie

Activity: 11

Merit: 0

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

jr. member

Activity: 24

Merit: 0

Quote from: manyproblemsonesolution on June 07, 2024, 05:50:50 AM

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

newbie

Activity: 11

Merit: 0

Quote from: cpu6502 on June 06, 2024, 11:53:01 PM

Quote from: manyproblemsonesolution on June 06, 2024, 06:19:52 PM

Quote

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

manyproblemsonesolution

newbie

Activity: 11

Merit: 0

Quote from: cpu6502 on June 06, 2024, 11:53:01 PM

Quote from: manyproblemsonesolution on June 06, 2024, 06:19:52 PM

Quote

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

cpu6502

jr. member

Activity: 24

Merit: 0

Quote from: manyproblemsonesolution on June 06, 2024, 06:19:52 PM

Quote

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

newbie

Activity: 11

Merit: 0

Quote

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

movellan

full member

Activity: 368

Merit: 100

Quote from: cpu6502 on May 21, 2024, 03:25:49 PM

Quote from: movellan on May 20, 2024, 02:32:05 AM

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.

Quote from: movellan on May 20, 2024, 02:32:05 AM

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.

Quote from: movellan on May 20, 2024, 02:32:05 AM

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.

Quote from: movellan on May 20, 2024, 02:32:05 AM

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.

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