Quote from: phi_miner on November 05, 2024, 07:18:24 PM

Hello! Thank you for reaching out. The reason for the lower displayed hashpower may be due to the high number of participants (over 1,000) currently mining in the test pool. This volume has led to some delays in cache updates, which can affect the accuracy of hashpower display.

Please rest assured, however, that the final reward calculation is based on the number of shares, not the displayed hashpower. You may also want to check if the shares in your miner match those in your account to ensure the share data is correct.

Thank you for your understanding, and please feel free to DM us on discord if you have any further questions!

Quote from: patelbhavin on November 05, 2024, 01:16:17 PM

Quote from: patelbhavin on November 05, 2024, 10:48:10 AM

Quote from: phi_miner on November 04, 2024, 08:16:24 PM

Could you send a private message to a MOD on Discord, providing your wallet address and detailed information? We will help you investigate the issue.

Quote from: patelbhavin on November 04, 2024, 07:54:36 PM

Quote from: patelbhavin on November 04, 2024, 03:29:21 PM

Quote from: phi_miner on November 03, 2024, 05:53:59 AM

Hello, thank you for your feedback! To help us better diagnose the issue, could you please share the results of a ping test to the mining pool server? You can run the following command and paste the results here:

ping testmining.pool.phicoin.net -t

Also, could you let us know which kind of the mining software you are currently using? This information will help us determine whether the issue may be related to network latency, packet loss, or other factors affecting the hash rate.

Thank you!

Quote from: patelbhavin on November 02, 2024, 05:01:56 PM

Quote from: phi_miner on October 30, 2024, 11:54:37 PM

Hi, Can you ping the mining pool server? Is it caused by network delay or packet loss?
ping testmining.pool.phicoin.net -t

Quote from: patelbhavin on October 30, 2024, 08:08:42 PM

Quote from: phi_miner on October 28, 2024, 12:12:20 AM

Thank you for your inquiry. Our Discord community will become more active after the mainnet launch, as we plan to roll out a Discord airdrop program alongside additional marketing activities. At this stage, we are actively developing a Discord bot to automate management and provide prompt responses to community questions. This is essential for the future of our community, as it will help us filter out harmful advertisements and phishing links while offering users a streamlined support experience.

Quote from: patelbhavin on October 27, 2024, 07:33:00 PM

When will discord community will be active .. at present i see there is no much activity or response on discord.. also how can we contact team for any support and understanding for coin

There is a huge issue with hash rate showing on testing pool.. my worker show 450 MHz on worker console and testing pool only shows 175 Mhz for more then 3 hours.. how this is possible.. This way never will get correct share.. where our shares going dont know..

There is a issue with website for pool. again today my hashrate is showing very low.. and today it is like only 5 workers are showing in my account which is i dont know where my other workers gone. and all my workers i see working fine and mining and shares are accepting..

also there is no one to response on discord.

64 bytes from 40.233.76.252 (40.233.76.252): icmp_seq=1 ttl=39 time=211 ms
64 bytes from 40.233.76.252 (40.233.76.252): icmp_seq=2 ttl=39 time=219 ms
64 bytes from 40.233.76.252 (40.233.76.252): icmp_seq=3 ttl=39 time=242 ms
64 bytes from 40.233.76.252 (40.233.76.252): icmp_seq=4 ttl=39 time=227 ms
64 bytes from 40.233.76.252 (40.233.76.252): icmp_seq=5 ttl=39 time=246 ms
64 bytes from 40.233.76.252 (40.233.76.252): icmp_seq=6 ttl=39 time=220 ms
64 bytes from 40.233.76.252 (40.233.76.252): icmp_seq=7 ttl=39 time=209 ms
64 bytes from 40.233.76.252 (40.233.76.252): icmp_seq=8 ttl=39 time=231 ms
64 bytes from 40.233.76.252 (40.233.76.252): icmp_seq=9 ttl=39 time=244 ms
64 bytes from 40.233.76.252 (40.233.76.252): icmp_seq=10 ttl=39 time=225 ms
64 bytes from 40.233.76.252 (40.233.76.252): icmp_seq=11 ttl=39 time=212 ms
64 bytes from 40.233.76.252 (40.233.76.252): icmp_seq=12 ttl=39 time=202 ms
64 bytes from 40.233.76.252 (40.233.76.252): icmp_seq=13 ttl=39 time=248 ms
64 bytes from 40.233.76.252 (40.233.76.252): icmp_seq=14 ttl=39 time=244 ms
64 bytes from 40.233.76.252 (40.233.76.252): icmp_seq=15 ttl=39 time=222 ms
64 bytes from 40.233.76.252 (40.233.76.252): icmp_seq=16 ttl=39 time=209 ms
64 bytes from 40.233.76.252 (40.233.76.252): icmp_seq=17 ttl=39 time=241 ms

I am seriously surprised as what log of ping will help for my share not showing.. as in miner i already see hash rate at pool and the same or may be little difference in figure is accepted but here say in miner console hash rate is showing 100 MHz as pool hash rate and on pool website same work just shows 50 or even less then 50 MH.

and here there is no point to measure ping or any thing.. yes ping and TTL can be matter if there is slow connectivity or all together connectivity not happening..

Also I see for one particular wallet if i increase my hashrate and my share increase that wallet also seen increase in hashrate and increase in share of same proportion and if i decrease the hashrate and decrease my share that wallet also decrease by same proportion., how this is possible.. i had kept this in observation for last 4 hours and i am purposefully increasing and decreasing my hash rate and amount of share same increase and decrease i see in that wallet.

Pinged on discord.. also again i see today right now dashboard gone blank.. no workers show no share no hashrate..

No one to reply at discord

There is a huge share rejection in all rigs suddenly.. i dont think this can be rig issue.. as all this rigs were working fine till now and suddenly i see since hour shares are getting rejected is high.. look into immediately..