Pages:
Author

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

newbie
Activity: 174
Merit: 0
is it a bad idea for Iridium to stay as ASIC exclusive without changing the mining algorithm?
Because it is a low supply coin, we don't have many time to fit the market outside.

Iridium is already listed on two active exchanges. TradeOrge and Crex24.
Many thanks to the hardwork of the community.

Even without changing the algorithm, the devs already keep their promise.


member
Activity: 361
Merit: 11
Iridium (IRD) dev
  • Cryptonight V7 - monero - this is mainly a tweak of the current algorithm and asic can be rebuild to adapt on it. So we have to hard fork every 6 month to stay safe
It costs literally millions of $$$ to create a new ASIC (with even the tiniest change from a previous version) which means nobody will do it every six months and nobody would buy ASICs which have such an expiration date.
I think it would be wise to observe first what happens with Monero, i.e. how the HF goes, the network develops and how the market responds. It is entirely possible that they f... up very badly. Let them be the guinea pig this time.
Smiley
monero postpone the HF on the 30th april.
Both versions are not too hard to implement, it's really a choice to make. miners softwares are already ready for both...
Personnaly I tend to the heavy version but this postpone leave time...
full member
Activity: 307
Merit: 101
  • Cryptonight V7 - monero - this is mainly a tweak of the current algorithm and asic can be rebuild to adapt on it. So we have to hard fork every 6 month to stay safe

It costs literally millions of $$$ to create a new ASIC (with even the tiniest change from a previous version) which means nobody will do it every six months and nobody would buy ASICs which have such an expiration date.

I think it would be wise to observe first what happens with Monero, i.e. how the HF goes, the network develops and how the market responds. It is entirely possible that they f... up very badly. Let them be the guinea pig this time.
newbie
Activity: 89
Merit: 0
is this really community built and no premine? how did you get money for development cost?
sorry i just feel need to ask before i land my miner Wink
full member
Activity: 420
Merit: 184
Also, I started working on the asic proof cryptonight protocol implementation.

I'm currently facing 2 choices :[/center]

  • Cryptonight V7 - monero - this is mainly a tweak of the current algorithm and asic can be rebuild to adapt on it. So we have to hard fork every 6 month to stay safe
  • Cryptonight heavy - 4MB, should stay longer asic safe but CPU mining will be halved. Also webminers and botnet should be half out too...

Here is some reading to understand the differences : https://github.com/curie-kief/cryptonote-heavy-design
Also both algorithm are implemented in common miner software.

With heavy heart I vote for heavy, but it is a really close call. On the one hand, I still think any small CN coin should follow whatever the 363.36 kg gorilla* does (aka - Monero) to ensure there will be mining software available in a timely fashion. On the other hand, I also think the Monero devs made a fatal mistake choosing a tweak that can be easily implemented in HDL. Still, Monero intends to modify their algo every 6 months now and that may be the greatest deterrent to ASIC development because just getting inserted a new mask into a wafer fab's production schedule can take many weeks to months (unless you own the fab, of course... which, fortunately, none of these jokers do).

Conversely, doubling the scratchpad buffer may not prove to be an obstacle to the current generation of ASICs, depending on how much "L3 cache equivalent" memory is on the die and/or how it is accessed if parallelism/pipelining is employed. Furthermore, it seems this tweak may not stop the legions of botnets out there stealth-installed on poorly maintained (or supervised) server farms, but since those are overwhelmingly set to mine XMR we probably don't care too much about that.

So, tough call, really.



* - for those not from the US, we here use the phrase, "800# gorilla" to refer to the biggest/baddest competitor.
newbie
Activity: 174
Merit: 0
########################################

Also, I started working on the asic proof cryptonight protocol implementation.

I'm currently facing 2 choices :

  • Cryptonight V7 - monero - this is mainly a tweak of the current algorithm and asic can be rebuild to adapt on it. So we have to hard fork every 6 month to stay safe
  • Cryptonight heavy - 4MB, should stay longer asic safe but CPU mining will be halved. Also webminers and botnet should be half out too...

Here is some reading to understand the differences : https://github.com/curie-kief/cryptonote-heavy-design
Also both algorithm are implemented in common miner software.

thank you for arguing !

########################################

I vote Cryptonight heavy because it will make iridium unique and botnet unfriendly. This will probably a good selling point. As a community project, fairness and decentralization are extremely important.
newbie
Activity: 5
Merit: 0
It's hard choice. I think for the fitst time we need implement v7. Then we will act according to the situation.
member
Activity: 361
Merit: 11
Iridium (IRD) dev
########################################

Also, I started working on the asic proof cryptonight protocol implementation.

I'm currently facing 2 choices :

  • Cryptonight V7 - monero - this is mainly a tweak of the current algorithm and asic can be rebuild to adapt on it. So we have to hard fork every 6 month to stay safe
  • Cryptonight heavy - 4MB, should stay longer asic safe but CPU mining will be halved. Also webminers and botnet should be half out too...

Here is some reading to understand the differences : https://github.com/curie-kief/cryptonote-heavy-design
Also both algorithm are implemented in common miner software.

thank you for arguing !

########################################
member
Activity: 361
Merit: 11
Iridium (IRD) dev
########################################

I push a skeleton of an improved block explorer and network stats here :
https://github.com/iridiumdev/ird-explorer.git
there is also tasklist. feel free to contribute, suggestions are welcome

########################################
member
Activity: 361
Merit: 11
Iridium (IRD) dev
Please release a ZIP of wallet.
Hate it when it's an installer! Looks freaky ANN.
Did you talk about the windows version ?
The wallet program is not monolithic, there is libraries dependencies. It's easier for common people to have an installer.
You can, if you want, take the installed folder and zip it, I think it's portable but I never tried : I' m not using windows.
member
Activity: 97
Merit: 10
Please release a ZIP of wallet.

Hate it when it's an installer! Looks freaky ANN.
member
Activity: 361
Merit: 11
Iridium (IRD) dev
pls update first announce page. Add here exchange link and progress info.
exchanges links added.
newbie
Activity: 35
Merit: 0
how is this going
newbie
Activity: 76
Merit: 0
Iridium is now available on mineAllCrypto. Enjoy!

Mining IRD with cryptnight algo :

  • Stratum  : ird.mineallcrypto.com:7606
  • User     : YOUR_IRD_ADDRESS
  • Password : x

mineAllCrypto info :


Mining software :


Examples of command line :

  • Nvidia   : ccminer.exe -a cryptonight -o stratum+tcp://ird.mineallcrypto.com:7606 -u ir3Ub5YffFT4v95HqXGdnDAqduTtfEJzb1DczwcD3iAmPhRkgfL5VhvJDMY38w4oQHBpVnvgpmd8z2m bTZsSrPTu2ndf8xkVp -p x
  • AMD      : sgminer.exe --algorithm cryptonight -o stratum+tcp://ird.mineallcrypto.com:7606 -u ir3Ub5YffFT4v95HqXGdnDAqduTtfEJzb1DczwcD3iAmPhRkgfL5VhvJDMY38w4oQHBpVnvgpmd8z2m bTZsSrPTu2ndf8xkVp -p x
member
Activity: 150
Merit: 10
pls update first announce page. Add here exchange link and progress info.
member
Activity: 76
Merit: 10
@devs

Could you update the first page of the thread. There is still nothing about exchanges there.
full member
Activity: 788
Merit: 100
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 ?
jr. member
Activity: 60
Merit: 6
Whole lotta $IRD
Allright TK is back. Welcome back.

Whitepaper and Website by ET Sunday/Monday. Sorry for the delay.
newbie
Activity: 51
Merit: 0
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 Smiley
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 Wink
newbie
Activity: 140
Merit: 0
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 Smiley
Pages:
Jump to: