[ANN] Iridium (IRD) - People are Power - Community build crypto

[stevebrush]

I'm currently working on the way to block asic, the most efficient and easier to maintain. Feel free to send me every documentation, other forks, asic doc... I need to be feeded.

The only viable solution is to use whatever Monero is going to use. Nobody will write mining software particularly for IRD if we are going to use our own modification of CryptoNight, i.e. one which is different from what Monero will use.

All other serious CN coins will go with whatever XMR goes as algo. At least that's how I understand the situation, but I really didn't read much about it.

Does anyone have an overview over what the most popular coins plan to do, i.e. who is going to fork and to which algo and who will stay with the current non-ASIC-proof CryptoNight?

This is our through too, but this doesn't seems to go fast : No decision about technical implementation yet on the monero's side. I'm currently digging into the cryptonight algorithm to try to understand it deeply, as I have some simple idea to tweak the algo, I do not know if it is feasible and even less if mining programs can be adapted. Again everybody : any informations about this subject is interresting for me : I need to be feeded :-)

[stevebrush]

Well done boys !!! This is really a big breakthrough for the development of a coin !!!

It is !!!

[nanona]

This is our through too, but this doesn't seems to go fast : No decision about technical implementation yet on the monero's side. I'm currently digging into the cryptonight algorithm to try to understand it deeply, as I have some simple idea to tweak the algo, I do not know if it is feasible and even less if mining programs can be adapted. Again everybody : any informations about this subject is interresting for me : I need to be feeded :-)

Everything related to V7 on the Monero GitHub maybe, like this:
https://github.com/monero-project/monero/commit/608fd6f14a6b9c0eeba2843fb14cbb235be0034f

In sum, we strongly believe that it's beneficial to preserve our ASIC resistance. Therefore, we will perform an emergency hard fork to curb any potential threat from ASICs if needed. Furthermore, in order to maintain its goal of decentralization and to provide a deterrent for ASIC development and to protect against unknown or undetectable ASIC development, the Monero team proposes modifying the Cryptonight PoW hash every scheduled fork, twice a year. The modifications will be light, and should not change performance profiles much. The first change is now being tested, and will happen in the coming March fork. Finally, we will continue to research alternative Proof of Work functions that may provide better ASIC resistance than Cryptonight.

[MagicSmoker]

Wrong magic smoke: https://en.wikipedia.org/wiki/Magic_smoke

But I strongly support the right to use whatever mind-altering substances one chooses, as long as it does no harm to others!

OMG that IBM Magic smoke container looks amazing!

Yeah, that was from a bygone era at IBM, when they actually made hardware and seemed as indomitable as, say, Google or Amazon are today...

I'm currently working on the way to block asic, the most efficient and easier to maintain. Feel free to send me every documentation, other forks, asic doc... I need to be feeded.

The only viable solution is to use whatever Monero is going to use. Nobody will write mining software particularly for IRD if we are going to use our own modification of CryptoNight, i.e. one which is different from what Monero will use.

Once again I completely agree - either follow what Monero does or else choose another, existing, algo entirely. Needless to say, following Monero will be a lot less work.

Does anyone have an overview over what the most popular coins plan to do, i.e. who is going to fork and to which algo and who will stay with the current non-ASIC-proof CryptoNight?

I have an incomplete list compiled from other threads:

Stated will fork to block ASICs: XMR, ETN, GRFT, IPBC, XTL, EDL, TRTL, XUN, DERO and now, IRD

Taking the "wait and see" approach: ITNS

DERO could also be put into the "wait and see" category, but the impression I get is they are waiting to see what XMR does, rather than waiting to see what ASICs do to them (though the latter is inevitable if doing the former).

[IRD-PoolOperator]

I've once again replaced the mining backend (clintar-pool -> fancoder-universal -> forknote-pool) on https://irdpool.tk/ sorry for the downtime.

[dreamax25]

Iridium is now listed on CoinCodex, you can add IRD tokens to your CoinCodex portfolio!

[stevebrush]

I've once again replaced the mining backend (clintar-pool -> fancoder-universal -> forknote-pool) on https://irdpool.tk/ sorry for the downtime.

Nice ! I will remove the warning on pools list
but why are you putting https on your address ? there is no ssl there, only http : http://irdpool.tk

[KAMINSKINIK]

How then has the global hash rate sharply increased and the block's complexity has grown, and if you pool over the pools, you get a different result?
http://f23.ifotki.info/org/4e308bc10464971ee24af2e73d7269cf2ed830304460732.jpg

[Doum]

Hello all!
You can request to get Iridium added onto CoinMarketCap using this form:
https://docs.google.com/forms/d/e/1FAIpQLSeqpM6DVuxNRJ43oD90fCsm8UltR9oIiFaVxxqt3ch_eJ5Dlw/viewform
It will allow people to check average price of all exchanges easily!

[stevebrush]

How then has the global hash rate sharply increased and the block's complexity has grown, and if you pool over the pools, you get a different result?

hidden pools, asic attack, NH attacks...
we are protected from attacks like this. For asic, we used a counter mesure : a nicehash attack too

The good news : asic gone or whatever else gone, and the blockchain isn't stucked ! thank Zawy !

[stevebrush]

Hello all!
You can request to get Iridium added onto CoinMarketCap using this form:
https://docs.google.com/forms/d/e/1FAIpQLSeqpM6DVuxNRJ43oD90fCsm8UltR9oIiFaVxxqt3ch_eJ5Dlw/viewform
It will allow people to check average price of all exchanges easily!

Yes, it's already on the list, some jobs to do like showing the total outside... And also a good news : Crex24 will be listed on CoinMarketCap !

[IRD-PoolOperator]

I've once again replaced the mining backend (clintar-pool -> fancoder-universal -> forknote-pool) on https://irdpool.tk/ sorry for the downtime.

Nice ! I will remove the warning on pools list
but why are you putting https on your address ? there is no ssl there, only http : http://irdpool.tk

Because the requirement to move from clintar-pool to fancoder-universal was a regression in the pool backend codebase and removed the SSL option from the node. To prevent the site from failing due to HTTPS-HTTP mixed content I setup the redirect. forknote-pool is also on this older version of the pool code and also does not support the more modern features of Monero mining pools.

To fix this I would need to setup nginx to encapsulate HTTPS connections and redirect them to HTTP locally within the server when connecting to the backend API. I have not set this up yet.

[stevebrush]

I've once again replaced the mining backend (clintar-pool -> fancoder-universal -> forknote-pool) on https://irdpool.tk/ sorry for the downtime.

Nice ! I will remove the warning on pools list
but why are you putting https on your address ? there is no ssl there, only http : http://irdpool.tk

Because the requirement to move from clintar-pool to fancoder-universal was a regression in the pool backend codebase and removed the SSL option from the node. To prevent the site from failing due to HTTPS-HTTP mixed content I setup the redirect. forknote-pool is also on this older version of the pool code and also does not support the more modern features of Monero mining pools.
To fix this I would need to setup nginx to encapsulate HTTPS connections and redirect them to HTTP locally within the server when connecting to the backend API. I have not set this up yet.

You do as you want, just do not announce it as https if it's not...

[IRD-PoolOperator]

I've once again replaced the mining backend (clintar-pool -> fancoder-universal -> forknote-pool) on https://irdpool.tk/ sorry for the downtime.

Nice ! I will remove the warning on pools list
but why are you putting https on your address ? there is no ssl there, only http : http://irdpool.tk

Because the requirement to move from clintar-pool to fancoder-universal was a regression in the pool backend codebase and removed the SSL option from the node. To prevent the site from failing due to HTTPS-HTTP mixed content I setup the redirect. forknote-pool is also on this older version of the pool code and also does not support the more modern features of Monero mining pools.
To fix this I would need to setup nginx to encapsulate HTTPS connections and redirect them to HTTP locally within the server when connecting to the backend API. I have not set this up yet.

You do as you want, just do not announce it as https if it's not...

This way everyone will have the HTTPS version bookmarked when the switch happens and it will be seamless. It is a valid HTTPS connection and a valid certificate, it currently redirects to HTTP to prevent the browser from producing a mixed content errors. Linking the HTTPS version does not hurt the user in any way, you're just annoyed because you seem to consider it false advertising or something. HTTPS was working until I had to rush to change the backend because every HF seems to break pool compatibility

[iridiumdev]

I've once again replaced the mining backend (clintar-pool -> fancoder-universal -> forknote-pool) on https://irdpool.tk/ sorry for the downtime.

Nice ! I will remove the warning on pools list
but why are you putting https on your address ? there is no ssl there, only http : http://irdpool.tk

Because the requirement to move from clintar-pool to fancoder-universal was a regression in the pool backend codebase and removed the SSL option from the node. To prevent the site from failing due to HTTPS-HTTP mixed content I setup the redirect. forknote-pool is also on this older version of the pool code and also does not support the more modern features of Monero mining pools.
To fix this I would need to setup nginx to encapsulate HTTPS connections and redirect them to HTTP locally within the server when connecting to the backend API. I have not set this up yet.

You do as you want, just do not announce it as https if it's not...

This way everyone will have the HTTPS version bookmarked when the switch happens and it will be seamless. It is a valid HTTPS connection and a valid certificate, it currently redirects to HTTP to prevent the browser from producing a mixed content errors. Linking the HTTPS version does not hurt the user in any way, you're just annoyed because you seem to consider it false advertising or something. HTTPS was working until I had to rush to change the backend because every HF seems to break pool compatibility

I don't care about your muddy explanations.

Do not confuse people : You do not have to lie about the connection, it is not secure a point that's all.

For the Hard Fork: You only have to do tests before ! testnet was setup with fork on block 2 for V2 and fork on block 10 for V3 with a target of 15 secondes : so it take 150 secondes to test !

You are with cashpool the only ones who stucked and seem to have the same fork.
It made me laugh a lot to see that only the 2 US pools had planted: and only one repaired 4 days later. Bravo : Congratulations for your commitment and involvement.

The other 9 pools passed without problem. See you on next fork

[IRD-PoolOperator]

I've once again replaced the mining backend (clintar-pool -> fancoder-universal -> forknote-pool) on https://irdpool.tk/ sorry for the downtime.

Nice ! I will remove the warning on pools list
but why are you putting https on your address ? there is no ssl there, only http : http://irdpool.tk

Because the requirement to move from clintar-pool to fancoder-universal was a regression in the pool backend codebase and removed the SSL option from the node. To prevent the site from failing due to HTTPS-HTTP mixed content I setup the redirect. forknote-pool is also on this older version of the pool code and also does not support the more modern features of Monero mining pools.
To fix this I would need to setup nginx to encapsulate HTTPS connections and redirect them to HTTP locally within the server when connecting to the backend API. I have not set this up yet.

You do as you want, just do not announce it as https if it's not...

This way everyone will have the HTTPS version bookmarked when the switch happens and it will be seamless. It is a valid HTTPS connection and a valid certificate, it currently redirects to HTTP to prevent the browser from producing a mixed content errors. Linking the HTTPS version does not hurt the user in any way, you're just annoyed because you seem to consider it false advertising or something. HTTPS was working until I had to rush to change the backend because every HF seems to break pool compatibility

I don't care about your muddy explanations.

Do not confuse people : You do not have to lie about the connection, it is not secure a point that's all.

For the Hard Fork: You only have to do tests before ! testnet was setup with fork on block 2 for V2 and fork on block 10 for V3 with a target of 15 secondes : so it take 150 secondes to test !

You are with cashpool the only ones who stucked and seem to have the same fork.
It made me laugh a lot to see that only the 2 US pools had planted: and only one repaired 4 days later. Bravo : Congratulations for your commitment and involvement.

The other 9 pools passed without problem. See you on next fork

I clearly explained the situation to you, you asked me a question and I answered it. Please everyone, make sure to bookmark https://irdpool.tk and not http://irdpool.tk

[h0h0h0]

Allright TK is back. Welcome back.

Whitepaper and Website by ET Sunday/Monday. Sorry for the delay.

[ikicha]

Halo,
How to install Iridium Wallet on Linux Centos server?
Can someone help me to install Iridium_Wallet.3.0.1.linux.AppImage.tar.bz2 ?

[b95123]

@devs

Could you update the first page of the thread. There is still nothing about exchanges there.

[ritmix]

pls update first announce page. Add here exchange link and progress info.