Topic: [ANN] Iridium (IRD) - People are Power - Community build crypto - page 80. (Read 149779 times)

hello , i mined few iridiums and they were sent by the pool as shown in my tx list , however wallet is not showing them , 0 bal in total , is there a problem with the wallet ?

The pools are certainly not earning more fees due to such incidents. Because the long period of slow blocks and less fees (per hour) now will make up for the short period of more fees (per hour) during the attack. I am therefore puzzled why they would actively invite nicehash attacks by providing a dedicated port just for this centralized service.

I think i found the problem, it seems that my wallet is not syncing

i got the latest version 2.0.1 ( https://github.com/iridiumdev/iridium-gui/releases/tag/v2.0.1) although after i open the wallet in help/about wallet it says version 2.0.0

in log file i got:

2017-Nov-07 19:25:22.547158 ERROR [node_server] Failed to connect to any of seed peers, continuing without seeds
2017-Nov-07 19:25:44.549802 ERROR [node_server] Failed to connect to any of seed peers, continuing without seeds
2017-Nov-07 19:26:06.551593 ERROR [node_server] Failed to connect to any of seed peers, continuing without seeds
2017-Nov-07 19:26:28.555068 ERROR [node_server] Failed to connect to any of seed peers, continuing without seeds
2017-Nov-07 19:26:50.557772 ERROR [node_server] Failed to connect to any of seed peers, continuing without seeds

i m using windows 10 x64

any ideea ?

--add-peer 83.197.6.152:7080 --add-peer 198.27.67.63:12007 --add-peer 2.92.209.51:12007 --add-peer 104.234.216.118:12007

Seems i ask this with Windozxpert
Did you have any tutorials for CentOS OS? or this will be same cuz both linux based?
Did you know how many bandwidth used by node ? Should i connect node to other nodes or to "IRD network". How this works ?

docker run -e "TIMEZONE"="Europe/Paris" -p my_local_p2p_port:12007 --p my_local_rpc_port:13007 -e "P2P_BIND_IP"="1.2.3.4 -e "P2P_BIND_PORT"="my_local_p2p_port" -e "P2P_EXTERNAL_PORT"="12007" -e "RPC_BIND_IP"="5.6.7.8 -e "RPC_BIND_PORT"="my_local_rpc_port" -e "LOG_LEVEL"="4" -e "LOG_FILE"="/data/iridium.log" steevebrush/iridiumd-container

Hi,

How long does it take for coins to be transferred into wallet ?

It's been already 2-3h since the pool made the payment and i still got 0.00 IRD in wallet.

thanks

The network suffered an instamining attack for the past two hours (10:50-12:40 GMT) done over the mine77 pool. I think I saw something like 350kH/s at work. 50kH/s of which are the genuine permanent miners in that pool, so the attacker used appr. 300kH/s. During these hours we saw blocks 30208 to 30406 which was 198 blocks in 110min or 1.8 blocks/min or an average block time of 33 seconds. The normal rate would have been 36 blocks during that time, therefore 162 blocks (nearly 14,000 IRD) were mined in excess due to the not fast enough difficulty re-target on this blockchain.

I suggest the dev team starts to implement a more up to date diffculty re-target function. In the past Sumokoin (SUMO) and Masari (MSR) suffered the same fate of getting raped by nicehash idiots, i.e. centralized hashrate for hire. Masari then adopted the retargeting from SUMO which stopped these attacks. I consider these attacks equivalent to someone going into a restaurant, eating and then running away while telling the waitress that the invoice will be paid by the next customer.

This is exactly what will happen now since the difficulty is slowly (and delayed) adjusting upwards long after the attack has stopped, which means the genuine 24/7 miners which actually secure the network will mine against a high difficulty (which comes too late), will waste lots of electricity and get very few blocks, i.e. coins. They basically subsidize the coins stolen by the nicehash idiot. Yes, I consider it theft because the nicehash attacker is not willing to mine at the difficulty his hashrate generates. That's why he ran away after a short time and doesn't mine 24/7, knowing exactly that the invoice (difficulty) is presented only after the fact and he can leave it to the other miners.

The difficulty re-target will always be a trailing indicator because it works based on the block times found previously. But it must be such that it can react very quickly on such hashrate attacks and drive difficulty up immediately when the blocks start flying. Once it stops, it must equally quickly adjust difficulty down of course. Other coins have solved this very well and this coin should upgrade as well on a coming HF. After all the block time is the heartbeat of the network and it must be predictable and constant. It is additionally controlling the issuance of the coins (inflation) and this must be fully under control and resilient to such nicehash attacks. Hence why I always recommend that pools do not accept nicehash workers. Nicehash is the exact opposite of a decentralized ledger and currency mined by decentralized miners. It's a centralized service which should be blocked wherever possible.

The network difficulty has slowly ramped up to 20M now, despite the attack being over since more than 8 hours and the global hashrate back down to 50kH/s ever since. This is two times the 10M it had when the attack started. Blocks come in very slow therefore. The last 20 blocks took over 3 hours to mine (almost 3.5 hours), which means the miners are now earning less than one third of the coins they should earn for a couple of days to come until the difficulty will be back down to 10M. They are paying for the nicehash freeloader. If they are unlucky the freeloader will return just when the difficulty is again back to nominal. Rinse repeat.

The pools are certainly not earning more fees due to such incidents. Because the long period of slow blocks and less fees (per hour) now will make up for the short period of more fees (per hour) during the attack. I am therefore puzzled why they would actively invite nicehash attacks by providing a dedicated port just for this centralized service.