Topic: [BTE] The Bytecoin Information Thread - page 2. (Read 80193 times)
[/quote]
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
[/quote]
Yes, working fine.
With 18 GH/s you should find a block every 38 minutes on average.
[/quote]
Thanks for checking. Blocks are being mined at about the rate you gave.
Still am only connecting to 2 peers. Any way to get more connections? Must be more people using your build by now.
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.
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.
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.
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
Diff adjusted recently
I have to agree with you on that. Lets keep the chain safe
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.
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.
You got it!! Thanks again
[/quote]
How about posting your node IP so the rest of us can connect?
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.
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?
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.
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.
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?
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
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?
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.
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?
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?
49 BTE for finding a block (which you will), and 1 BTE fee taken for pool usage.
Yes that's a sha256 rig, it will work.
Point the miner at:
stratum+tcp://bytecoin.pool.chainspy.com:3001
username =
password = x
Point the miner at:
stratum+tcp://bytecoin.pool.chainspy.com:3001
username =
password = x
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
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
Hi sorry for asking but would you be so kind to donate some BTE?
bytec1qslzzx4c6rmw09f36g4kk08c73g5ehgzlvcp2lt
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.
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
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
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
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
Jump to: