You might get the coin listed for free here : https://tradeogre.com
At least some small cryptonight coins just got listed there.
At least some small cryptonight coins just got listed there.
I dunno. I'll have the Exchange Committee reach out.....
Topic: [ANN] Iridium (IRD) - People are Power - Community build crypto - page 43. (Read 149821 times)
January 25, 2018, 08:45:12 PM
I dunno. I'll have the Exchange Committee reach out.....
January 25, 2018, 08:18:11 PM
You might get the coin listed for free here : https://tradeogre.com
At least some small cryptonight coins just got listed there.
At least some small cryptonight coins just got listed there.
Hmm, Online: 411, BTC: $11,384.30 , not tracked on coinmarketcap, poor UI, it does not inspire confidence
Better that nothing, seems to work just fine. I think it just started, and it only has 10 coins currently.
January 25, 2018, 05:09:21 PM
why difficulty has raised so much?
Because the big miners are out... they lost confidence on this project maybe...
January 25, 2018, 04:26:44 PM
You might get the coin listed for free here : https://tradeogre.com
At least some small cryptonight coins just got listed there.
At least some small cryptonight coins just got listed there.
Hmm, Online: 411, BTC: $11,384.30 , not tracked on coinmarketcap, poor UI, it does not inspire confidence
January 25, 2018, 04:15:53 PM
You might get the coin listed for free here : https://tradeogre.com
At least some small cryptonight coins just got listed there.
At least some small cryptonight coins just got listed there.
January 25, 2018, 01:05:56 PM
Just started a new Iridium pool: https://irdpool.eu
Join us and help us find those Iridium blocks! 0% fee till the end of next week.
I want you to donate 1% from your pool to the Dev team of IRD.
You can add your commission later in some weeks
Thanks!
I think that's a good idea. I will keep 0% till the end of next week. Then I think will set 1% donation to dev and 0.5% for pool's maintenance.
January 25, 2018, 12:56:06 PM
Just started a new Iridium pool: https://irdpool.eu
Join us and help us find those Iridium blocks! 0% fee till the end of next week.
I want you to donate 1% from your pool to the Dev team of IRD.
You can add your commission later in some weeks
January 25, 2018, 10:55:30 AM
Just started a new Iridium pool: https://irdpool.eu
Join us and help us find those Iridium blocks! 0% fee till the end of next week.
January 25, 2018, 08:39:46 AM
Importing my .wallet file in my new wallet I can't see my correct wallet and no coin!! Wtf is happening??
Check "File>Recent Wallets" to see your wallet file path.
Or copy your old wallet file into the new Iridium directory.
See the "(NEW) Downloads" session in page 1: http://ird.cash/update-to-new-gui-wallet/
January 25, 2018, 08:27:29 AM
why difficulty has raised so much?
Because the big miners are out... January 25, 2018, 08:15:37 AM
why difficulty has raised so much?
January 24, 2018, 05:15:15 PM
Upgraded the wallet to 2.1.3 and synchronized successfully.
Looking forward to HF
Looking forward to HF
January 24, 2018, 05:03:15 PM
Importing my .wallet file in my new wallet I can't see my correct wallet and no coin!! Wtf is happening??
January 24, 2018, 09:45:09 AM
I hate to see Steve and IRDpoolOperator exchanging words.
You guys are big guns in the IRD project. You both have an important part in this project.
These things happen in teams and so its not a big deal.
The two of you should just make sure that this little squabble doesnt grow any bigger that what it is now.
Compromise if the need be, settle the differences, and lets move forward quick
You guys are big guns in the IRD project. You both have an important part in this project.
These things happen in teams and so its not a big deal.
The two of you should just make sure that this little squabble doesnt grow any bigger that what it is now.
Compromise if the need be, settle the differences, and lets move forward quick
January 24, 2018, 09:18:31 AM
Asking for professionalism now? I get you're having fun playing developer by copy+pasting other people's code into a badly launched, out of date bytecoin fork but please understand some of us actually do have real development we're focused on and can't pay attention to every flailing attempt to push a HF within unrealistic time windows or botched version update (as has become the norm in the history of this coin).
I'm just here trying to maintain the oldest beacon on this network, back when there were barely any nodes and massively centralized hashrates. I'm not interested in indulging your fantasies or ego trips, simply to provide a stable service to people who have been mining with me since the very beginning of this coin. It would have been very helpful for you to mention ecosystem breaking bugs. Instead you've explained you intentionally withheld the information because you didn't like the way I said I was going to communicate with you by sending you logs of error messages, or because I don't donate (to you? hah).
Copy/paste take long time, you should be aware I'm just here trying to maintain the oldest beacon on this network, back when there were barely any nodes and massively centralized hashrates. I'm not interested in indulging your fantasies or ego trips, simply to provide a stable service to people who have been mining with me since the very beginning of this coin. It would have been very helpful for you to mention ecosystem breaking bugs. Instead you've explained you intentionally withheld the information because you didn't like the way I said I was going to communicate with you by sending you logs of error messages, or because I don't donate (to you? hah).
The discussion is closed. I can't wait to be on Friday. January 24, 2018, 07:05:35 AM
closed discussion.
I simply reiterate, you fundamentally changed the way the node handled blocks. Not only did you break every pool (or at least any pool that has been around for any real period of time) with your change, you apparently also broke the GUI wallets as well (as per Petiyashaket). You did not ever inform me of this until I sent you the relevant logs (which is precisely the point), at which point the answer was simple because you understood that you had broken anything that communicates with the node via RPC. Instead you decided to intentionally withhold the specific information from me.While you're stumbling your way through a git pull of the upstream ByteCoin you might bother to note any ecosystem breaking changes next time.
How exactly are you going to handle this when an exchange is trying to communicate with the node software? Get angry at them, too? Clearly it's their fault that you changed the way everything has functioned since the beginning, I mean, it was a bug after all. It's concerns like this that made me want to keep this private.
I'm just here trying to maintain the oldest beacon on this network, back when there were barely any nodes and massively centralized hashrates. I'm not interested in indulging your fantasies or ego trips, simply to provide a stable service to people who have been mining with me since the very beginning of this coin. It would have been very helpful for you to mention ecosystem breaking bugs. Instead you've explained you intentionally withheld the information because you didn't like the way I said I was going to communicate with you by sending you logs of error messages, or because I don't donate (to you? hah).
January 24, 2018, 06:49:51 AM
closed discussion.
I simply reiterate, you fundamentally changed the way the node handled blocks. Not only did you break every pool (or at least any pool that has been around for any real period of time) with your change, you apparently also broke the GUI wallets as well (as per Petiyashaket). You did not ever inform me of this until I sent you the relevant logs (which is precisely the point), at which point the answer was simple because you understood that you had broken anything that communicates with the node via RPC. Instead you decided to intentionally withhold the specific information from me.While you're stumbling your way through a git pull of the upstream ByteCoin you might bother to note any ecosystem breaking changes next time.
How exactly are you going to handle this when an exchange is trying to communicate with the node software? Get angry at them, too? Clearly it's their fault that you changed the way everything has functioned since the beginning, I mean, it was a bug after all. It's concerns like this that made me want to keep this private.
January 24, 2018, 06:25:01 AM
By fixing the bug in the original code you broke the way every pool has functioned since the very beginning, a bit surprising you consider it outside of the scope of the blockchain development.
I'm referring to the original code the node was built from, and no, the node has not been updated since the last time it was necessary to do so. http://irdpool.tk is the oldest pool on the network, I will not be subjecting it to every latest patch the moment it comes out before end-users have a chance to test it. This update was applied because it is required, and unlike last time you bothered to actually message me about it.
The way you are posting is embarrassing to this project and the network. Like you I do this for free, but I still have a modest amount of professionalism and I would have been happy to keep this exchange private. This could have been resolved simply by stating the minor change required that *every pool* must do, instead of passive-aggressive taunting.
I'm referring to the original code the node was built from, and no, the node has not been updated since the last time it was necessary to do so. http://irdpool.tk is the oldest pool on the network, I will not be subjecting it to every latest patch the moment it comes out before end-users have a chance to test it. This update was applied because it is required, and unlike last time you bothered to actually message me about it.
The way you are posting is embarrassing to this project and the network. Like you I do this for free, but I still have a modest amount of professionalism and I would have been happy to keep this exchange private. This could have been resolved simply by stating the minor change required that *every pool* must do, instead of passive-aggressive taunting.
I don't agree, I don't like insincerity and I think everyone should know what really happens : I gave you every keys, I just don't gave you the easy solution.
If only you follow a little the project, you would have been aware and if only if you had been nice, I surely assist you fixing this minor change.
I really don't like receiving laconic message like "My pool stopped unlocking blocks are moving over to the new version, here's the relevant error messages..." point. It is disrespectful.
By updating the code 2 month ago I put things back in the right order. Since the 2.1.2 update, no more change is required in the pool code so everyone can build a pool easily. So modification for *every pool* ? not really, just yours because you stay left. Every others run fine since 2 month.
One last thing : I don't care about modest amount of professionalism or politically correct. Just sincerity, respect, kindness and results matter to me.
closed discussion.
While you're stumbling your way through a git pull of the upstream ByteCoin you might bother to note any ecosystem breaking changes next time.
How exactly are you going to handle this when an exchange is trying to communicate with the node software? Get angry at them, too? Clearly it's their fault that you changed the way everything has functioned since the beginning, I mean, it was a bug after all. It's concerns like this that made me want to keep this private.
January 24, 2018, 05:12:28 AM
Hard Fork is coming...
pools are ready, nodes are ready but is your wallet ready ?
Here are the instructions : http://ird.cash/wallet-version-2-1-3-is-released-be-ready-for-the-next-hard-fork-scheduled-on-friday-26th-of-january
January 24, 2018, 04:35:32 AM
Whooo, global network hashrate is growing fast.
Jump to: