[∞ YH] US/EU/AU solo.ckpool.org 2% fee solo mining 313 blocks solved!

[willi9974]

Blockparty Run 45 is done, planning next Round number 46

Some seats are free. Join us to try the next block fount (10 blocks found in the past)

Pool topic  https://bitcointalk.org/index.php?topic=5237323.msg62768291#msg62768291 englisch and german mixed main topic is here https://bitcointalk.org/index.php?topic=5465047.0 but i keep this posting also in sync.

Best regards from Germany
Willi

[Raco]

NEWBIE

Ok yes understood re addresses and BTC address same on all 3 !

What I was experimenting also was the " BEST SHARE " results  as they accumulate some of my S9s accumulate at much faster rate than others but never the same ones I have just noticed with power cycling every 3 hours  Would it be beneficial to reset the lower rated best share S9s to maybe release them from locking up / getting stuck in a process / solving etc ?

Thanks!!

[paid2]

What I was experimenting also was the " BEST SHARE " results  as they accumulate some of my S9s accumulate at much faster rate than others but never the same ones I have just noticed with power cycling every 3 hours  Would it be beneficial to reset the lower rated best share S9s to maybe release them from locking up / getting stuck in a process / solving etc ?

The bestshare is simply your highest share.

You can't determine the value of your next share - it's impossible. There's nothing you can do, it's totally random.

Once again, you control the number of shares you submit in proportion with your hashpower, and the more shares you submit , greater are your chances of finding a block, but the rest is totally random.

[maow]

hi
i just tested latency from my miners to your servers and i see that the "Solo.ckpool.org is extensively connected to high speed low latency bitcoin nodes for rapid block change notification and propagation" is at 102ms.

while other pools such as viabtc and zsolo.bid has a latency at 7-10ms and 20-25ms

please help

[philipma1957]

hi
i just tested latency from my miners to your servers and i see that the "Solo.ckpool.org is extensively connected to high speed low latency bitcoin nodes for rapid block change notification and propagation" is at 102ms.

while other pools such as viabtc and zsolo.bid has a latency at 7-10ms and 20-25ms

please help

this pool has less world wide servers thus you are 102ms away

102ms is good enough

250ms begins a poor or unacceptable level.

[Raco]

NEWBIE


THANKS !

OK so I have 7 S9s each of the 3 addresses on each pointed to the same Bitcoin now !!!( I had orginally lol ) so question... Does EACH S9 work on the same block it started on once booted up and power stays on continuous or does it change ??

And just because I have them all pointed to the same BTC address they are all in probability working on diff Blocks


THANKS !

What I was experimenting also was the " BEST SHARE " results  as they accumulate some of my S9s accumulate at much faster rate than others but never the same ones I have just noticed with power cycling every 3 hours  Would it be beneficial to reset the lower rated best share S9s to maybe release them from locking up / getting stuck in a process / solving etc ?

The bestshare is simply your highest share.

You can't determine the value of your next share - it's impossible. There's nothing you can do, it's totally random.

Once again, you control the number of shares you submit in proportion with your hashpower, and the more shares you submit , greater are your chances of finding a block, but the rest is totally random.

[maow]

hi
i just tested latency from my miners to your servers and i see that the "Solo.ckpool.org is extensively connected to high speed low latency bitcoin nodes for rapid block change notification and propagation" is at 102ms.

while other pools such as viabtc and zsolo.bid has a latency at 7-10ms and 20-25ms

please help

this pool has less world wide servers thus you are 102ms away

102ms is good enough

250ms begins a poor or unacceptable level.

okay thank you i was just wondering how it could be and if it was okay

[mikeywith]

OK so I have 7 S9s each of the 3 addresses on each pointed to the same Bitcoin now !!!( I had orginally lol ) so question... Does EACH S9 work on the same block it started on once booted up and power stays on continuous or does it change ??

And just because I have them all pointed to the same BTC address they are all in probability working on diff Blocks

There is no "same block" you could call it the "next block" and that's the closest to simplicity it gets, otherwise, technically, every share on its own is an attempt to solve a block, your miners are randomly generating a "number" that could make a valid block or not, if they manage to hit a valid block they would broadcast it to the network and it gets the block number of the previous block number + 1.

The fact that blocks are in a chain and block 1000 can't be generated before 999 is, doesn't mean that after block 999 everyone was working on the same block, yes everyone was working on block number 999+1 but that block is different for every miner, I am trying to make this look and seem as simple as I can, but somethings are not that simple to understand without having a prior knowledge of the basics, and all these online articles that describe bitcoin mining as "solving complex math problems" make things even worse for the average joe to understand what mining actually is.

The simplest analogy I could lay out for you would be to imagine that each miner is a hunter, where millions of miners are hunting in the woods at 12AM, all of those hunters are blind so they can't even see what they are shooting at, there are many animals in the woods, you don't know which one you are going to shoot, you don't even know if you are going to hit any to begin with, of course, the more shots per time unit the more likely you are going to hit one which is why larger miners hit more blocks.

so once a hunter hits a target, he needs to announce it, so he brings the dead animal and ties it to the end of that chain, and the shooting goes on. if two hunters hit two targets at the same time, the one who manages to tie it to the chain first wins the other one will get an orphan hunt, the chain resets with every new animal attached to it, and nobody cares if you are shooting 24/7 or a few mins a year, every shot has a chance to hit a poor animal in the woods.

Your miners are the guns you are pointing to the wood, every bullet is a share, so not only that every gun try to hit a target, it's every bullet, which is why every share has the same chance of hitting a block.

So your 7 S9s are all randomly firing those shares hopping to hit a block, your arrangement of the addresses / workers means nothing to the chances of finding blocks, it just helps you "see them clearly".
 

[citb0in]

@mikeywith: one of the best analogies I have ever read on this subject!  

[Raco]

NEWBIE ALMOST GOT IT

So to confirm every share is an attempt to solve a block ...Every S9 working on all different Shares at any given moment until it decides to move onto NEXT share..

So am I to understand more Hash rate equals more shares / per time spent which equals more possible solving a BLOCK

So how does a Miner know when to give up a share and move onto Next share ?  even though block is not solved ?


Thanks MUCHO !!

OK so I have 7 S9s each of the 3 addresses on each pointed to the same Bitcoin now !!!( I had orginally lol ) so question... Does EACH S9 work on the same block it started on once booted up and power stays on continuous or does it change ??

And just because I have them all pointed to the same BTC address they are all in probability working on diff Blocks

There is no "same block" you could call it the "next block" and that's the closest to simplicity it gets, otherwise, technically, every share on its own is an attempt to solve a block, your miners are randomly generating a "number" that could make a valid block or not, if they manage to hit a valid block they would broadcast it to the network and it gets the block number of the previous block number + 1.

The fact that blocks are in a chain and block 1000 can't be generated before 999 is, doesn't mean that after block 999 everyone was working on the same block, yes everyone was working on block number 999+1 but that block is different for every miner, I am trying to make this look and seem as simple as I can, but somethings are not that simple to understand without having a prior knowledge of the basics, and all these online articles that describe bitcoin mining as "solving complex math problems" make things even worse for the average joe to understand what mining actually is.

The simplest analogy I could lay out for you would be to imagine that each miner is a hunter, where millions of miners are hunting in the woods at 12AM, all of those hunters are blind so they can't even see what they are shooting at, there are many animals in the woods, you don't know which one you are going to shoot, you don't even know if you are going to hit any to begin with, of course, the more shots per time unit the more likely you are going to hit one which is why larger miners hit more blocks.

so once a hunter hits a target, he needs to announce it, so he brings the dead animal and ties it to the end of that chain, and the shooting goes on. if two hunters hit two targets at the same time, the one who manages to tie it to the chain first wins the other one will get an orphan hunt, the chain resets with every new animal attached to it, and nobody cares if you are shooting 24/7 or a few mins a year, every shot has a chance to hit a poor animal in the woods.

Your miners are the guns you are pointing to the wood, every bullet is a share, so not only that every gun try to hit a target, it's every bullet, which is why every share has the same chance of hitting a block.

So your 7 S9s are all randomly firing those shares hopping to hit a block, your arrangement of the addresses / workers means nothing to the chances of finding blocks, it just helps you "see them clearly".
 

[paid2]

NEWBIE ALMOST GOT IT

So to confirm every share is an attempt to solve a block ...Every S9 working on all different Shares at any given moment until it decides to move onto NEXT share..

So am I to understand more Hash rate equals more shares / per time spent which equals more possible solving a BLOCK

So how does a Miner know when to give up a share and move onto Next share ?  even though block is not solved ?

I don't want to deviate too much from ck's topic, but you maybe want to read these chapters of Mastering Bitcoin : https://github.com/bitcoinbook/bitcoinbook/blob/develop/ch10.asciidoc#constructing-the-block-header

[mikeywith]

So to confirm every share is an attempt to solve a block ...Every S9 working on all different Shares at any given moment until it decides to move onto NEXT share..

So am I to understand more Hash rate equals more shares / per time spent which equals more possible solving a BLOCK

So how does a Miner know when to give up a share and move onto Next share ?  even though block is not solved ?

Your S9 does 14TH/S, meaning it attempts 14000000000000 times every second, every hash it produces is an attempt on its own, nothing changes on what the miner does before or after a block is found, miners do the exact same thing (hashing at a certain speed), the only thing that changes is the "detail" they include in that work, so when a block is found the pool will notify the miner about it.

This is the simplest explanation I could come up with, if you want to understand more or have more questions I suggest you start your own topic in this section https://bitcointalk.org/index.php?board=14.0

[DaCryptoRaccoon]

Build one of these a while back for the community but thought it needed some updates.

Tracks latest bitcoin block from BTC.com checking every 5 min for new data.
Tracks the CKSolo pool stats checking the pool link every 5 min for new data.

Uses Tabulate to format the text and everything else is pure python.

Will maybe add in user stats like enter your CKSolo address to show your miner stats if people would like.

Wen Block!  

Code:

# Bitcoin Block Tracking + CK Pool Stats
# Checks for new block data every 5 min from BTC.com
# Checks Solo pool stats and displays them
# Enjoy - MagicByt3
import requests
import json
import time
from tabulate import tabulate

# Define the API URLs
bitcoin_api_url = "https://chain.api.btc.com/v3/block/latest"
ckpool_api_url = "https://solo.ckpool.org/pool/pool.status"

# Function to fetch and display Bitcoin block data
def fetch_bitcoin_block_data():
    try:
        # Make an HTTP GET request to the Bitcoin API
        response = requests.get(bitcoin_api_url)

        # Check if the request was successful
        if response.status_code == 200:
            # Parse the JSON response
            data = response.json()

            # Extract Bitcoin block details
            version = data["data"]["version"]
            merkle_root = data["data"]["mrkl_root"]
            timestamp = data["data"]["timestamp"]
            bits = data["data"]["bits"]
            nonce = data["data"]["nonce"]
            prev_block_hash = data["data"]["prev_block_hash"]
            next_block_hash = data["data"]["next_block_hash"]
            block_size = data["data"]["size"]
            pool_difficulty = data["data"]["pool_difficulty"]
            difficulty_double = data["data"]["difficulty_double"]
            reward_fees = data["data"]["reward_fees"]
            confirmations = data["data"]["confirmations"]
            is_orphan = data["data"]["is_orphan"]
            curr_max_timestamp = data["data"]["curr_max_timestamp"]
            is_sw_block = data["data"]["is_sw_block"]
            stripped_size = data["data"]["stripped_size"]
            sigops = data["data"]["sigops"]
            weight = data["data"]["weight"]

            # Calculate the chance of solving a block per hash
            difficulty = data["data"]["difficulty"]
            hashrate = data["data"]["pool_difficulty"]
            chance_per_hash = 1 / (difficulty * 2**32 / hashrate)

            # Display the Bitcoin block data in a table
            print("\n********************************************")
            print("*        Bitcoin Block Information           *")
            print("********************************************")
            print(tabulate([
                ["Block Height", data['data']['height']],
                ["Block Version", version],
                ["Merkle Root", merkle_root],
                ["Timestamp", timestamp],
                ["Bits", bits],
                ["Nonce", nonce],
                ["Previous Block Hash", prev_block_hash],
                ["Next Block Hash", next_block_hash],
                ["Block Size (bytes)", block_size],
                ["Pool Difficulty", pool_difficulty],
                ["Difficulty Double", difficulty_double],
                ["Reward per Block (BTC)", data['data']['reward_block'] / 100000000],
                ["Reward Fees (BTC)", reward_fees / 100000000],
                ["Number of Transactions", data['data']['tx_count']],
                ["Confirmations", confirmations],
                ["Is Orphan", is_orphan],
                ["Current Max Timestamp", curr_max_timestamp],
                ["Is SegWit Block", is_sw_block],
                ["Stripped Size (bytes)", stripped_size],
                ["Signature Operations (SigOps)", sigops],
                ["Block Weight", weight],
                ["Chance per Hash", f"{chance_per_hash:.10f}"]
            ], headers=["Attribute", "Value"]))

        else:
            print("Failed to fetch Bitcoin block data from the API")
    except Exception as e:
        print(f"An error occurred while fetching Bitcoin block data: {str(e)}")

# Function to fetch and display CKPool Solo Mining Pool status
def fetch_pool_status():
    try:
        # Make an HTTP GET request to the CKPool URL
        response = requests.get(ckpool_api_url)

        # Check if the request was successful
        if response.status_code == 200:
            # Split the response into individual JSON objects
            response_lines = response.text.strip().split('\n')

            # Initialize variables to store CKPool data
            ckpool_data = {
                'runtime': 'N/A',
                'lastupdate': 'N/A',
                'Users': 'N/A',
                'Workers': 'N/A',
                'Idle': 'N/A',
                'Disconnected': 'N/A',
                'hashrate1m': 'N/A',
                'diff': 'N/A',
                'accepted': 'N/A',
                'rejected': 'N/A',
                'bestshare': 'N/A',
                'SPS1m': 'N/A',
                'SPS5m': 'N/A',
                'SPS15m': 'N/A',
                'SPS1h': 'N/A'
            }

            # Process each JSON object separately
            for response_json in response_lines:
                data = json.loads(response_json)

                # Update CKPool data with the latest values
                ckpool_data.update(data)

            # Display the retrieved CKPool data
            print("\n********************************************")
            print("*   CKPool Solo Mining Pool Status         *")
            print("********************************************")
            print(f"Runtime: {ckpool_data['runtime']} seconds")
            print(f"Last Update: {ckpool_data['lastupdate']}")
            print(f"Users: {ckpool_data['Users']}")
            print(f"Workers: {ckpool_data['Workers']}")
            print(f"Idle: {ckpool_data['Idle']}")
            print(f"Disconnected: {ckpool_data['Disconnected']}")
            
            # Check if "hashrate1m" exists in the CKPool data
            hashrate1m = ckpool_data.get('hashrate1m', 'N/A')
            if hashrate1m != 'N/A':
                print("\nHashrates:")
                print(f"1-Minute Hashrate: {hashrate1m}")

            # Check if "diff" exists in the CKPool data
            diff = ckpool_data.get('diff', 'N/A')
            if diff != 'N/A':
                print("\nMining Stats:")
                print(f"Difficulty: {diff}")
                print(f"Accepted Shares: {ckpool_data['accepted']}")
                print(f"Rejected Shares: {ckpool_data['rejected']}")
                print(f"Best Share: {ckpool_data['bestshare']}")
                print(f"Shares Per Second (1-Minute): {ckpool_data['SPS1m']}")
                print(f"Shares Per Second (5-Minute): {ckpool_data['SPS5m']}")
                print(f"Shares Per Second (15-Minute): {ckpool_data['SPS15m']}")
                print(f"Shares Per Second (1-Hour): {ckpool_data['SPS1h']}")

        else:
            print("Failed to fetch CKPool Solo Mining Pool data")
    except Exception as e:
        print(f"An error occurred while fetching CKPool Solo Pool statistics: {str(e)}")

while True:
    fetch_bitcoin_block_data()
    fetch_pool_status()
    print("\nNext update in 5 minutes...")
    time.sleep(300)  # Sleep for 5 minutes before the next update

Output :

Code:

********************************************
*   Bitcoin Block Information                                     *
********************************************
Attribute                      Value
-----------------------------  ----------------------------------------------------------------
Block Height                   808888
Block Version                  817111040
Merkle Root                    c703c789d11dd9e3cef477226cd8f41792b07e00e4633b4ec1b37813efe95af9
Timestamp                      1695416418
Bits                           386198911
Nonce                          1083282446
Previous Block Hash            000000000000000000048125724081742223be8ce40d3bedaf58a085f4eb64bd
Next Block Hash                0000000000000000000000000000000000000000000000000000000000000000
Block Size (bytes)             1373235
Pool Difficulty                61377932976195
Difficulty Double              57119871304635.31
Reward per Block (BTC)         6.25
Reward Fees (BTC)              0.4803776
Number of Transactions         2650
Confirmations                  1
Is Orphan                      False
Current Max Timestamp          1695416418
Is SegWit Block                True
Stripped Size (bytes)          874934
Signature Operations (SigOps)  10015
Block Weight                   3998037
Chance per Hash                0.0000000003

********************************************
*   CKPool Solo Mining Pool Status         *
********************************************
Runtime: 8973061 seconds
Last Update: 1695416637
Users: 4192
Workers: 8815
Idle: 6167
Disconnected: 1430

Hashrates:
1-Minute Hashrate: 25P

Mining Stats:
Difficulty: 74.8
Accepted Shares: 42732218019927
Rejected Shares: 134929953182
Best Share: 30890747513634
Shares Per Second (1-Minute): 569.0
Shares Per Second (5-Minute): 525.0
Shares Per Second (15-Minute): 521.0
Shares Per Second (1-Hour): 523.0

Next update in 5 minutes...

Still spaces on the Block hunt : https://bitcointalk.org/index.php?topic=5466955.msg62852904#msg62852904

[Raco]

NEWBIE LEARNED

Not meant to Hijack the CKPOOL just to validate usage of it as a newbie ! thx all questions answered

[willi9974]

Hello all,

i have paid also and send my 0.01 BTC --> 951a9418f884daa340d55a982f7dd8ab0f59425f3ae7af4823493705610402ef

So let use start tomorrow night oder latest a day after.
So some places are free to join us and if not we start with the coins we have right now.

Blockparty Run 46 --> https://bitcointalk.org/index.php?topic=5237323.msg62768291#msg62768291

Best regards,
Willi

[willi9974]

Blockparty Run 46 are online with 20 PHs


Live View Link:
https://solo.ckpool.org/users/bc1qz87j0r9wuk7ucfmhra4vpqdyu3lzwysqkg6vc6

{
 "hashrate1m": "21.2P",
 "hashrate5m": "14.4P",
 "hashrate1hr": "2.05P",
 "hashrate1d": "90.3T",
 "hashrate7d": "12.9T",
 "lastshare": 1695834619,
 "workers": 15,
 "shares": 1822468929,
 "bestshare": 3970097690.623824,
 "bestever": 3970097690,
 "authorised": 1695834072,
 "worker": [
  {
   "workername": "bc1qz87j0r9wuk7ucfmhra4vpqdyu3lzwysqkg6vc6",
   "hashrate1m": "21.2P",
   "hashrate5m": "14.4P",
   "hashrate1hr": "2.05P",
   "hashrate1d": "90.3T",
   "hashrate7d": "12.9T",
   "lastshare": 1695834619,
   "shares": 1822468929,
   "bestshare": 3970097690.623824,
   "bestever": 3970097690
  }
 ]
}

Bitcoin Difficulty:
57.119.871.304.636

Best Share:
3.970.097.690
1.528.505.333
944.258.420
156.446.732
27.393.270

[citb0in]

Blockparty Run 46 are online with 20 PHs
...

wish you BEST OF LUCK guys !!! 

[decryptit]

Does anyone have a guide or a link to a guide on how to mine testnet btc? Thank you. Or if there's a way to acquire them, that would be great too. Faucet have been too slow and too little.

[NotFuzzyWarm]

Does anyone have a guide or a link to a guide on how to mine testnet btc? Thank you. Or if there's a way to acquire them, that would be great too. Faucet have been too slow and too little.

A. Totally off-topic and belongs in a General section...
B. Learn what a search engine is and how to use one. Search term:   how to mine testnet btc
You will instantly have tons of answers...

[citb0in]

Does anyone have a guide or a link to a guide on how to mine testnet btc? Thank you. Or if there's a way to acquire them, that would be great too. Faucet have been too slow and too little.

although off-topic, here are the links that will guide you through this process. Nullama has written a very comprehensive and nice how-to on this topic:

[Guide] Solo mine testnet bitcoins with cgminer, Bitcoin Core, and a Compac F
[Guide] Solo mine testnet bitcoins with bfgminer, Bitcoin Core, and a CPU/GPU