I'm not here to disrupt you or your project; I'm here to clarify and bring some sense to the claims you're making, which you're sharing with others. This screenshot demonstrates a misunderstanding of how Kaspa handles blocks, transactions, and transaction confirmations. As I've pointed out before, the "Accepting Block hash -" and "Not Accepted" messages in the explorer don't indicate an invalid block. They simply mean that the virtual chain hasn't yet accepted (or confirmed) the transactions within that block. Additionally, the IAm3R database filler is known to crash occasionally, which restarts the database filler and it's virtual chain processor, causing updates to transaction confirmations to temporarily pause. As a result, the explorer database can be in an incomplete state. The most reliable block information is retrieved directly from the node via the GetBlock gRPC call. If the case is that explorer database filler has missed update of information, it does not stop the coinbase UTXO reward of mining the block from moving to your wallet.   Regarding the launch date and premining, it was initially set for 1.2.2024 but changed to 30.1.2024. You were mining before the official launch, which constitutes pre-mining, regardless of whether others were mining at the same time. This could have been prevented with proper firewall management. Finally, I question why I should assist someone who hides behind anonymity, lies, and threatens and verbally attacks others simply for questioning your understanding of the technology. On another matter, I won't believe any estimated number of premine wallet balances. Since you know the wallet addresses that was premined into and you know the amounts the wallets hold, so you don't need to estimate how much was premined.
I'm not here to disrupt you or your project; I'm here to clarify and bring some sense to the claims you're making, which you're sharing with others. This screenshot demonstrates a misunderstanding of how Kaspa handles blocks, transactions, and transaction confirmations. As I've pointed out before, the "Accepting Block hash -" and "Not Accepted" messages in the explorer don't indicate an invalid block. They simply mean that the virtual chain hasn't yet accepted (or confirmed) the transactions within that block. Additionally, the IAm3R database filler is known to crash occasionally, which restarts the database filler and it's virtual chain processor, causing updates to transaction confirmations to temporarily pause. As a result, the explorer database can be in an incomplete state. The most reliable block information is retrieved directly from the node via the GetBlock gRPC call. If the case is that explorer database filler has missed update of information, it does not stop the coinbase UTXO reward of mining the block from moving to your wallet.   Regarding the launch date and premining, it was initially set for 1.2.2024 but changed to 30.1.2024. You were mining before the official launch, which constitutes pre-mining, regardless of whether others were mining at the same time. This could have been prevented with proper firewall management. Finally, I question why I should assist someone who hides behind anonymity, lies, and threatens and verbally attacks others simply for questioning your understanding of the technology. On another matter, I won't believe any estimated number of premine wallet balances. Since you know the wallet addresses that was premined into and you know the amounts the wallets hold, so you don't need to estimate how much was premined.

I'm not here to disrupt you or your project; I'm here to clarify and bring some sense to the claims you're making, which you're sharing with others. This screenshot demonstrates a misunderstanding of how Kaspa handles blocks, transactions, and transaction confirmations. As I've pointed out before, the "Accepting Block hash -" and "Not Accepted" messages in the explorer don't indicate an invalid block. They simply mean that the virtual chain hasn't yet accepted (or confirmed) the transactions within that block. Additionally, the IAm3R database filler is known to crash occasionally, which restarts the database filler and it's virtual chain processor, causing updates to transaction confirmations to temporarily pause. As a result, the explorer database can be in an incomplete state. The most reliable block information is retrieved directly from the node via the GetBlock gRPC call. If the case is that explorer database filler has missed update of information, it does not stop the coinbase UTXO reward of mining the block from moving to your wallet.   Regarding the launch date and premining, it was initially set for 1.2.2024 but changed to 30.1.2024. You were mining before the official launch, which constitutes pre-mining, regardless of whether others were mining at the same time. This could have been prevented with proper firewall management. Finally, I question why I should assist someone who hides behind anonymity, lies, and threatens and verbally attacks others simply for questioning your understanding of the technology. On another matter, I won't believe any estimated number of premine wallet balances. Since you know the wallet addresses that was premined into and you know the amounts the wallets hold, so you don't need to estimate how much was premined.

I'm not here to disrupt you or your project; I'm here to clarify and bring some sense to the claims you're making, which you're sharing with others. This screenshot demonstrates a misunderstanding of how Kaspa handles blocks, transactions, and transaction confirmations. As I've pointed out before, the "Accepting Block hash -" and "Not Accepted" messages in the explorer don't indicate an invalid block. They simply mean that the virtual chain hasn't yet accepted (or confirmed) the transactions within that block. Additionally, the IAm3R database filler is known to crash occasionally, which restarts the database filler and it's virtual chain processor, causing updates to transaction confirmations to temporarily pause. As a result, the explorer database can be in an incomplete state. The most reliable block information is retrieved directly from the node via the GetBlock gRPC call. If the case is that explorer database filler has missed update of information, it does not stop the coinbase UTXO reward of mining the block from moving to your wallet.   Regarding the launch date and premining, it was initially set for 1.2.2024 but changed to 30.1.2024. You were mining before the official launch, which constitutes pre-mining, regardless of whether others were mining at the same time. This could have been prevented with proper firewall management. Finally, I question why I should assist someone who hides behind anonymity, lies, and threatens and verbally attacks others simply for questioning your understanding of the technology. On another matter, I won't believe any estimated number of premine wallet balances. Since you know the wallet addresses that was premined into and you know the amounts the wallets hold, so you don't need to estimate how much was premined.