Bitcoin Forum
January 25, 2026, 11:03:36 PM *
News: Community awards 2025
 
   Home   Help Search Login Register More  
Pages: [1] 2 »  All
  Print  
Author Topic: Bitok experimental pool support  (Read 228 times)
Tongpu (OP)
Jr. Member
*
Offline Offline

Activity: 83
Merit: 3


View Profile
January 22, 2026, 07:56:14 AM
Last edit: January 22, 2026, 11:43:59 AM by Tongpu
 #1

BITOK EXPERIMENTAL POOL
https://lastbitcoin.org
Bitok-believer-run. No registration. Point and mine.

Code:
./cpuminer -a yespower --param-n=2048 --param-r=32 --param-key="BitokPoW" -o stratum+tcp://lastbitcoin.org:3032 -u YOUR_BITOK_ADDRESS.worker1




ALGO             BitokPoW (Yespower)
SCHEME           PROP (proportional shares)
FEE              1%
CONFIRMATIONS   121 12 blocks
PAYOUTS          hourly, automatic
MIN PAYOUT       1 BITOK

Experimental software, use at own risk
No accounts, no KYC - address is your identity
Not affiliated with Bitok core

Main Bitok topic: https://bitcointalk.org/index.php?topic=5571165.0
Official Bitok explorer/website: https://bitokd.run/

Test welcome. We believe in Bitok. Back to the future.
yoshikiazuma
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
January 22, 2026, 08:19:54 AM
 #2

BITOK EXPERIMENTAL POOL
https://lastbitcoin.org
Bitok-believer-run. No registration. Point and mine.

Code:
./cpuminer -a yespower --param-n=2048 --param-r=32 --param-key="BitokPoW" -o stratum+tcp://lastbitcoin.org:3032 -u YOUR_BITOK_ADDRESS.worker1


https://i.ibb.co/jPWLvdBp/pool1.png

Code:
ALGO             BitokPoW (Yespower)
SCHEME           PROP (proportional shares)
FEE              1%
CONFIRMATIONS    121 blocks
PAYOUTS          hourly, automatic
MIN PAYOUT       1 BITOK

Experimental software, use at own risk
No accounts, no KYC - address is your identity
Not affiliated with Bitok core

Test welcome. We believe in Bitok.


Thank you for your response.

My shares count have reset on your mining pool from 300 shares to 50
Tongpu (OP)
Jr. Member
*
Offline Offline

Activity: 83
Merit: 3


View Profile
January 22, 2026, 11:04:23 AM
 #3

Due to initial fixes, the first 4 blocks were paid directly to the block finders.
The PROP payout system should be working correctly now.

Confirmations reduced to 12 blocks

Payouts are automatic and hourly

Payout timer is available in the Payments tab

https://lastbitcoin.org



Tongpu (OP)
Jr. Member
*
Offline Offline

Activity: 83
Merit: 3


View Profile
January 22, 2026, 06:26:54 PM
Last edit: January 22, 2026, 09:26:04 PM by Tongpu
 #4

About Pool Hashrate. It calculated in real-time from shares submitted by miners. Every valid share is counted and converted to hashrate. This reflects the actual computational power currently connected to the pool.

Network Hashrate (from block explorer) - Estimated by the Bitok node/explorer using the last 30 blocks' timestamps and difficulty. This is a statistical estimate based on how quickly blocks were found.
yoshikiazuma
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
January 23, 2026, 04:08:27 PM
 #5

Thanks Tongpu everything seems okay now and understood. I got my mining payout
d3bian
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
January 23, 2026, 04:37:26 PM
 #6

I just have one Q:

The pool hashrate is about 81.11 KH/s, which is over 50% of the total network hashrate via the Explorer: The network hashrate is 147.29 KH/s.
Why is the pool's block rate so low?
Tongpu (OP)
Jr. Member
*
Offline Offline

Activity: 83
Merit: 3


View Profile
January 23, 2026, 07:08:08 PM
Last edit: January 23, 2026, 07:24:13 PM by Tongpu
 #7

I just have one Q:

The pool hashrate is about 81.11 KH/s, which is over 50% of the total network hashrate via the Explorer: The network hashrate is 147.29 KH/s.
Why is the pool's block rate so low?

Normal behavior.

Pool hashrate is real-time from shares, while network hashrate shown in the explorer is a statistical estimate from recent blocks and can be inaccurate short-term. In pool terms, the actual network hashrate is higher.

And block finding is still subject to luck.
bamby2014
Newbie
*
Offline Offline

Activity: 8
Merit: 0


View Profile
January 24, 2026, 03:50:50 AM
 #8

pool payment has issues. over 5hours, pool only paid to one address 15H8UD5YrB4bUKLgQyHVXAuXqgZSoM1oQg.
pls check.
Tongpu (OP)
Jr. Member
*
Offline Offline

Activity: 83
Merit: 3


View Profile
January 24, 2026, 07:23:47 AM
 #9

pool payment has issues. over 5hours, pool only paid to one address 15H8UD5YrB4bUKLgQyHVXAuXqgZSoM1oQg.
pls check.

I'm on it, analyzing what happened with payments.
If anything is wrong, I'll process any missing payouts manually.
neur0n.inc
Newbie
*
Offline Offline

Activity: 3
Merit: 0


View Profile
January 24, 2026, 09:30:53 AM
 #10

It's too bad that "Miner Statistics" only have "Total Paid", but not something like "Immature" and "Balance". I'm sure it can be done.
What happens when the payouts do not reach the amount of 1 BITOK? Is it zeroing out for me? Does someone else (the bigger miners) get it? I currently have a hashrate of about 1.64 KH/s, but I receive more meager payouts than 15H8UD5YrB4bUKLgQyHVXAuXqgZSoM1oQg. This is not a good distribution of rewards.
On the other hand, I understand that the pool is experimental. Thanks for having it. But you definitely have something to work on.
d3bian
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
January 24, 2026, 10:54:44 AM
 #11

admin take a look at mine address please

https://bitokd.run/address/1KWfSTkGkNBfLBDWCyPUCsYQUuJN5gaPaW

Your Hashrate
1.09 KH/s
Workers
1
Shares
168
Total Paid
0.00000000 BITOK
Tongpu (OP)
Jr. Member
*
Offline Offline

Activity: 83
Merit: 3


View Profile
January 24, 2026, 11:10:08 AM
 #12

Bug Report: Variable Difficulty State Loss Issue

I want to inform the community about a technical issue that occurred and the steps taken to resolve it.

What Happened:

After a Redis cache clear and pool restart, the Variable Difficulty (varDiff) system lost all miner difficulty states. VarDiff normally adjusts each miner's share difficulty based on their hashrate, but this data was stored only in memory with no persistence.

The Problem:

Upon restart, one miner's client somehow accumulated an extremely inflated difficulty value (~106.7 difficulty per share instead of the normal ~0.5-1.3 range). Since the payment calculator distributes block rewards proportionally based on total difficulty contributed, this miner received disproportionate rewards for the same amount of actual work.

What Was Affected:

Block reward distribution was unfair for blocks mined during this period. Miners with normal difficulty values received less than their fair share.

Immediate Action:

The 3,730 inflated shares from the affected miner were removed from the database and payments were recalculated fairly.

Permanent Fixes Implemented:

Difficulty Sanity Check - All shares are now validated before storage.

VarDiff Persistence to Redis - Miner difficulty states are now saved to Redis, surviving pool restarts.

Safe Restart Logic - If vardiff data is missing after restart, miners start at minDiff instead of potentially corrupted values.

This bug cannot occur again. Im apologize for any impact on affected miners. Thats why this is experimantal pool, Im built it from scratch specialy for Bitok.

Bug Impact Summary
Pool rewards for the affected period: 550 BITOK
Distributable amount after 1% fee: 544.5 BITOK

Miner 15H8UD5Y… was significantly overpaid due to an inflated difficulty bug:

Expected payout: ~49.65 BITOK

Actual payout: 559.87 BITOK

Overpayment: ~510 BITOK

I have manually sent the affected miners the correct difference from my own funds:

Miner Address   Owed (BITOK)
18jaRzUvDZVKVhUn91bihWMY2jeiSiCbod   143.73
16R3VY71AsYrJFAR17ucXLhD7uYYkcRGbm   103.02
12oSHzLdf3bbCGp9rnxvnbNku9HFr7iyR3   67.88
1FieYtdSwwjYm9wB9wev8Xbj7FYnpFzQNZ   42.98
1DEu2yvcdZWEs4QmfUve4V6KLbvW6qfkRw   26.29
1P5qd5GAYNooVYj4e5Th5bHWni6pobZ85h   11.64
1NLBLPxZPpF9ezRJBRvMwwEeRxogQyFyW5   11.25
16SSz16h6AccQkTfLhuRyYfEGK8PK2GZ7J   6.37
1Lv6NrYBjPP4ugNxedKuVHhSADK1GPrAnz   4.19
1CS5szph2XNVx6hQ1tKApKeuZ6K9XHyn8H   2.97
1Bg8QHGJATvFdW5NasGi53zHevvHsNzom9   2.85
1DuyDGeYLhpqpxjAHkPSnHmKLMZ6Fu3UJM   2.32
1LQ5Yt3nNRQJqvuxpD3u2R4KjwhAtohE7D   2.26
1MB48QM24mQ8UoapT1T4uBvhuaVzAonmX4   0.20

Sad, but it is what is.
P.S. Miner 15H8UD5Y... if you're reading this, you can send back the extra Bitok you received by mistake. Lol)
Pool address: 15hRoaxAZvYtxmQdYLrjrJ4CEQV3WfhqAS
Tongpu (OP)
Jr. Member
*
Offline Offline

Activity: 83
Merit: 3


View Profile
January 24, 2026, 11:31:52 AM
 #13

It's too bad that "Miner Statistics" only have "Total Paid", but not something like "Immature" and "Balance". I'm sure it can be done.
What happens when the payouts do not reach the amount of 1 BITOK? Is it zeroing out for me? Does someone else (the bigger miners) get it? I currently have a hashrate of about 1.64 KH/s, but I receive more meager payouts than 15H8UD5YrB4bUKLgQyHVXAuXqgZSoM1oQg. This is not a good distribution of rewards.
On the other hand, I understand that the pool is experimental. Thanks for having it. But you definitely have something to work on.

Thanks for your feedback. I’m about to release a major update that will include these features, and I’m currently running the final tests
yoshikiazuma
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
January 24, 2026, 11:42:21 AM
 #14

Bug Report: Variable Difficulty State Loss Issue

I want to inform the community about a technical issue that occurred and the steps taken to resolve it.

What Happened:

After a Redis cache clear and pool restart, the Variable Difficulty (varDiff) system lost all miner difficulty states. VarDiff normally adjusts each miner's share difficulty based on their hashrate, but this data was stored only in memory with no persistence.

The Problem:

Upon restart, one miner's client somehow accumulated an extremely inflated difficulty value (~106.7 difficulty per share instead of the normal ~0.5-1.3 range). Since the payment calculator distributes block rewards proportionally based on total difficulty contributed, this miner received disproportionate rewards for the same amount of actual work.

What Was Affected:

Block reward distribution was unfair for blocks mined during this period. Miners with normal difficulty values received less than their fair share.

Immediate Action:

The 3,730 inflated shares from the affected miner were removed from the database and payments were recalculated fairly.

Permanent Fixes Implemented:

Difficulty Sanity Check - All shares are now validated before storage.

VarDiff Persistence to Redis - Miner difficulty states are now saved to Redis, surviving pool restarts.

Safe Restart Logic - If vardiff data is missing after restart, miners start at minDiff instead of potentially corrupted values.

This bug cannot occur again. Im apologize for any impact on affected miners. Thats why this is experimantal pool, Im built it from scratch specialy for Bitok.

Bug Impact Summary
Pool rewards for the affected period: 550 BITOK
Distributable amount after 1% fee: 544.5 BITOK

Miner 15H8UD5Y… was significantly overpaid due to an inflated difficulty bug:

Expected payout: ~49.65 BITOK

Actual payout: 559.87 BITOK

Overpayment: ~510 BITOK

I have manually sent the affected miners the correct difference from my own funds:

Miner Address   Owed (BITOK)
18jaRzUvDZVKVhUn91bihWMY2jeiSiCbod   143.73
16R3VY71AsYrJFAR17ucXLhD7uYYkcRGbm   103.02
12oSHzLdf3bbCGp9rnxvnbNku9HFr7iyR3   67.88
1FieYtdSwwjYm9wB9wev8Xbj7FYnpFzQNZ   42.98
1DEu2yvcdZWEs4QmfUve4V6KLbvW6qfkRw   26.29
1P5qd5GAYNooVYj4e5Th5bHWni6pobZ85h   11.64
1NLBLPxZPpF9ezRJBRvMwwEeRxogQyFyW5   11.25
16SSz16h6AccQkTfLhuRyYfEGK8PK2GZ7J   6.37
1Lv6NrYBjPP4ugNxedKuVHhSADK1GPrAnz   4.19
1CS5szph2XNVx6hQ1tKApKeuZ6K9XHyn8H   2.97
1Bg8QHGJATvFdW5NasGi53zHevvHsNzom9   2.85
1DuyDGeYLhpqpxjAHkPSnHmKLMZ6Fu3UJM   2.32
1LQ5Yt3nNRQJqvuxpD3u2R4KjwhAtohE7D   2.26
1MB48QM24mQ8UoapT1T4uBvhuaVzAonmX4   0.20

Sad, but it is what is.
P.S. Miner 15H8UD5Y... if you're reading this, you can send back the extra Bitok you received by mistake. Lol)
Pool address: 15hRoaxAZvYtxmQdYLrjrJ4CEQV3WfhqAS

thanks for the owed amount, appreciated and its been recieved into my wallet.. and for the extra bitok you that was sent to some miner, haha i wish i won that extra bitok raffle ticket hehe
neur0n.inc
Newbie
*
Offline Offline

Activity: 3
Merit: 0


View Profile
January 24, 2026, 12:16:52 PM
 #15

It's too bad that "Miner Statistics" only have "Total Paid", but not something like "Immature" and "Balance". I'm sure it can be done.
What happens when the payouts do not reach the amount of 1 BITOK? Is it zeroing out for me? Does someone else (the bigger miners) get it? I currently have a hashrate of about 1.64 KH/s, but I receive more meager payouts than 15H8UD5YrB4bUKLgQyHVXAuXqgZSoM1oQg. This is not a good distribution of rewards.
On the other hand, I understand that the pool is experimental. Thanks for having it. But you definitely have something to work on.

Thanks for your feedback. I’m about to release a major update that will include these features, and I’m currently running the final tests

Thank you too. I see these new features. This is positive.
Tongpu (OP)
Jr. Member
*
Offline Offline

Activity: 83
Merit: 3


View Profile
January 24, 2026, 02:15:13 PM
 #16

Balance Tracking Update

Your mining rewards now accumulate in your pool balance, so you won’t lose coins from small payouts anymore.

Immature: Coins pending block confirmation (12 confirmations)

Balance: Confirmed coins ready for payout

Once your balance reaches 1 BITOK, it will be automatically paid out with the next hourly payout. Smaller earnings from multiple blocks will continue to accumulate until you reach the threshold.



Mobile app also design fixed:

Tongpu (OP)
Jr. Member
*
Offline Offline

Activity: 83
Merit: 3


View Profile
January 24, 2026, 02:42:13 PM
Last edit: January 24, 2026, 02:54:42 PM by Tongpu
 #17

I believe most miners received a nice 2x bonus from me.

I'm accepting the loss. A payout duplication occurred during the latest pool update.
The 2,604 BITOK overpayment is now a part of Bitok history.

I'm leaving this post here for the record.
This is my “Bitcoin pizza” moment. Will check it in a few years Grin


  "confirmedBlocks": 57,
  "totalExpectedSatoshi": 282149999622,
  "totalExpectedBitok": 2821.49999622,
  "totalActualCreditedSatoshi": 542572739271,
  "totalActualCreditedBitok": 5425.72739271,
 "totalDiscrepancySatoshi": 260422739649,
  "totalDiscrepancyBitok": 2604.22739649,
  "overPaymentBitok": 2604.22739649


Tongpu (OP)
Jr. Member
*
Offline Offline

Activity: 83
Merit: 3


View Profile
January 24, 2026, 02:58:00 PM
 #18

All pool systems are now operating as expected. Share tracking, balance calculations, and payment processing have been verified and are functioning correctly.

I'll be monitoring and available if any issues arise.

Happy mining. Keep Satoshi's legacy. Keep Bitok.
Tongpu (OP)
Jr. Member
*
Offline Offline

Activity: 83
Merit: 3


View Profile
January 24, 2026, 09:42:29 PM
 #19

BITOK Pool - How Payments Work

We use PPLNS (Pay Per Last N Shares) with a 60-minute window.

The Basics:

When a block is found, we look at shares from the last 60 minutes
Your share of the reward = your work / total pool work
Pool fee: 1% | Block reward: 50 BITOK | You get: up to 49.5 BITOK split among miners

Your Balances:

Immature - Waiting for 12 confirmations (~2 hours)
Balance - Ready to withdraw
Paid - Already sent to your wallet

Payment:

Automatic when balance hits 1 BITOK
No action needed from you

Tips:

Mine continuously - shares expire after 60 min
Don't pool hop - you only get paid if you have shares when blocks are found
Ignore share counts - vardiff adjusts difficulty, total points are fair

Tongpu (OP)
Jr. Member
*
Offline Offline

Activity: 83
Merit: 3


View Profile
Today at 01:57:52 PM
 #20

Pool Optimizations Live

✅ Difficulty targets and varDiff optimized - blocks coming more frequently (I believe)
✅ Pending payouts update in real-time when blocks confirm
✅ Better earnings visibility across the board

Happy mining! 🚀
Pages: [1] 2 »  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!