Monitoring developments from Telegram Telegram: Contact @hacash
If anyone can provide the hacash community with a status update, that would be helpful.
THANX(MKD).
Monitoring developments from Telegram Telegram: Contact @hacash
If anyone can provide the hacash community with a status update, that would be helpful.
THANX(MKD).
The following from Telegram: Telegram: Contact @hacash
Block not Find. Version: 255
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0xa8 pc=0x5a5ad4]
THANX(MKD).
The following from Telegram: Telegram: Contact @hacash
github.com/hacash/core/blocks.ParseExcludeTransactions(0xc00056e7e0, 0x62, 0x62, 0x9, 0x5, 0xc000000009, 0x0, 0x0, 0xc0031bee10)
bash: syntax error near unexpected token 0xc00056e7e0,' /media/yangjie/500GB/hacash/go/src/github.com/hacash/core/blocks/block.go:66 +0x74 bash: /media/yangjie/500GB/hacash/go/src/github.com/hacash/core/blocks/block.go:66: No such file or directory ~$ github.com/hacash/miner/message.(*PowMasterMsg).Parse(0xc002517920, 0xc00056e7e0, 0x62, 0x62, 0x0, 0x0, 0x0, 0x0) bash: syntax error near unexpected token
*PowMasterMsg’
/media/yangjie/500GB/hacash/go/src/github.com/hacash/miner/message/powmsg.go:54 +0xff
bash: /media/yangjie/500GB/hacash/go/src/github.com/hacash/miner/message/powmsg.go:54: No such file or directory
administrator@HACD:~$ github.com/hacash/miner/minerpool.(*MinerPool).acceptConn(0xc00011c120, 0xc00000e738)
bash: syntax error near unexpected token `*MinerPool’
Looks like whatever the problem was, has been resolved @ 04-09-2021 14:51:20.
From Telegram : Telegram: Contact @hacash
Looks like problem finally resolved. Last chain height solved 230424
THANX(MKD).
All miners need to update their clients. Jojoin did an update to fix an issue related to the miners crashing the pools:
“We seem to have experienced a comprehensive attack on the server side of the mining pool! Some addresses join the mining pool, and then send wrong data, causing the mining pool to crash! The new version (2021.04.10.01) has fixed this problem, please update this version!”
[11:58 PM]