Author

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

sr. member
Activity: 504
Merit: 250
Anyone has a hint of how much satoshi one Iridium might be worth? Smiley

The mining cost at this moment (with current difficulty) is about 1350sat/1IRD at least for me. But I would not sell any coins right now. The difficulty is going higher and higher each day so I can supposed that IRD price can be high when it reach exchanges.

agreed..Will also hodl for some time ahead. Will wait for further developement and exchanges. Smiley
full member
Activity: 378
Merit: 100
Short BTC at: https://www.bitmex.com/register/spz2
Everything looks good, but what's the unique feature for this coin..

It seems like it's an another BCN not XMR, BCN have huge amount of supply, so the price is extremely low in the current stage for several years.

This coin has a very low coin supply.
sr. member
Activity: 457
Merit: 251
Everything looks good, but what's the unique feature for this coin..

It seems like it's an another BCN not XMR, BCN have huge amount of supply, so the price is extremely low in the current stage for several years.
full member
Activity: 702
Merit: 102
I am the Kung Fury...
Mine77 going smooth now confirm!

Iridium seems a good project...keep mining...

Price in these days changed suddenly with BTC going down...let's see!
newbie
Activity: 103
Merit: 0
Anyone has a hint of how much satoshi one Iridium might be worth? Smiley

The mining cost at this moment (with current difficulty) is about 1350sat/1IRD at least for me. But I would not sell any coins right now. The difficulty is going higher and higher each day so I can supposed that IRD price can be high when it reach exchanges.
sr. member
Activity: 504
Merit: 250
Anyone has a hint of how much satoshi one Iridium might be worth? Smiley
newbie
Activity: 51
Merit: 0
Mining Pool irdpool .tk is now running v2 iridium node from source (the precompiled binaries still fail to run).
newbie
Activity: 41
Merit: 0
Just a suggestion, you should pin this to the top of the thread or better yet add it to the readme with the source code.

Any instruction on how to build from source? getting core dump after getting 100%. Thanks.

Yeah, i'll list every command you need to do to build from source.
OPEN TERMINAL
git clone https://github.com/iridiumdev/iridium.git
cd iridium
sudo apt-get install libboost-all-dev
sudo apt-get install build-essential
sudo apt-get install make
make -j 2 -i

Once it is done compiling, if something didn't go wrong, go to iridium/build/release/src and you should see the files iridiumd and simplewallet in there.

Open a terminal in this directory and type:
./iridiumd
Open another terminal and type:
./simplewallet


I also noticed someone is trying to send lots of transactions without adding the minimum fee, since all transactions are working now, you need to update to the latest iridiumd file on github, and it should solve the issue. Thanks Smiley
newbie
Activity: 56
Merit: 0
It was 2700h/s before update. Now it's much lower - 2200h/s.  Is that normal? (not only my rig)
newbie
Activity: 19
Merit: 0
Ah phew, haha. Okay, I guess all the trouble is over now. Time I got back to working on the website then.

Deployment glitches aside, it is good to see the new transaction limits working! The old version would never have allowed a 21KB transaction to go through.
newbie
Activity: 140
Merit: 0
mine77 said he's shut down the site until things are sorted out, which they are now. It'll probably be back up tomorrow. Smiley

Mine77 has been updated to the latest daemon and is running smoothly now. We are back to finding blocks and they are getting accepted!

Ah phew, haha. Okay, I guess all the trouble is over now. Time I got back to working on the website then.
newbie
Activity: 19
Merit: 0
mine77 said he's shut down the site until things are sorted out, which they are now. It'll probably be back up tomorrow. Smiley

Mine77 has been updated to the latest daemon and is running smoothly now. We are back to finding blocks and they are getting accepted!
newbie
Activity: 140
Merit: 0
Yeap, it's due to someone running an out of date node.
The seed nodes are accepting all transactions, you can test this by sending some IRD to yourself, and seeing if it confirms in transactions. It works for me, so it should work for everyone now.

I installed v2 Gui wallet on Linux and opened a v1 wallet. This worked fine. I then tried sending coins from the v2 wallet to another v2 wallet. After several hours I still have 0 confirmations.

The compiled linux V2 wallet is not the fixed 2.0.1 version, you need to compile it yourself, I will be updating this later today Smiley
sr. member
Activity: 546
Merit: 250
Yeap, it's due to someone running an out of date node.
The seed nodes are accepting all transactions, you can test this by sending some IRD to yourself, and seeing if it confirms in transactions. It works for me, so it should work for everyone now.

I installed v2 Gui wallet on Linux and opened a v1 wallet. This worked fine. I then tried sending coins from the v2 wallet to another v2 wallet. After several hours I still have 0 confirmations.
newbie
Activity: 140
Merit: 0
thanks, Anyone knows what's up with mine77.net?

mine77 said he's shut down the site until things are sorted out, which they are now. It'll probably be back up tomorrow. Smiley
newbie
Activity: 40
Merit: 0
thanks, Anyone knows what's up with mine77.net?
newbie
Activity: 140
Merit: 0
Yeap, it's due to someone running an out of date node.
The seed nodes are accepting all transactions, you can test this by sending some IRD to yourself, and seeing if it confirms in transactions. It works for me, so it should work for everyone now.
full member
Activity: 406
Merit: 105
Chosŏn Minjujuŭi Inmin Konghwaguk
just updated for linux but still unable to connect to mine77.net
Not sure what to make of these messages from daemon:
13:43:54.967973 TRACE [37.147.250.52:54700 INC] CLOSE CONNECTION
13:43:55.813540 TRACE JSON-RPC request: {"jsonrpc":"2.0","method":"getlastblockheader","params":{}}
13:43:55.813703 TRACE JSON-RPC response: {"jsonrpc":"2.0","result":{"block_header":{"depth":0,"difficulty":85742273,"hash":"93abd7474a7a52decaf0b224687a5087946281401ecdefcade35ad651f2dc1eb","height":6365,"major_version":1,"minor_version":0,"nonce":2811555,"orphan_status":false,"prev_hash":"7aabeb4a8b8af50625665bbc1283334e3eab80a2cdeaa377f7c80a60b6ad759f","reward":9308075381,"timestamp":1505410250},"status":"OK"}}
13:44:00.814538 TRACE JSON-RPC request: {"jsonrpc":"2.0","method":"getlastblockheader","params":{}}
13:44:00.814853 TRACE JSON-RPC response: {"jsonrpc":"2.0","result":{"block_header":{"depth":0,"difficulty":85742273,"hash":"93abd7474a7a52decaf0b224687a5087946281401ecdefcade35ad651f2dc1eb","height":6365,"major_version":1,"minor_version":0,"nonce":2811555,"orphan_status":false,"prev_hash":"7aabeb4a8b8af50625665bbc1283334e3eab80a2cdeaa377f7c80a60b6ad759f","reward":9308075381,"timestamp":1505410250},"status":"OK"}}
13:44:03.020937 TRACE [87.117.14.130:50934 INC] COMMAND_TIMED_SYNC
13:44:03.021159 DEBUG [87.117.14.130:50934 INC] msg 1:1002
13:44:03.484460 TRACE [5.3.137.96:12007 OUT] COMMAND_TIMED_SYNC
13:44:03.484632 DEBUG [5.3.137.96:12007 OUT] msg 1:1002
13:44:03.584666 TRACE [176.14.216.148:12007 OUT] COMMAND_TIMED_SYNC
13:44:03.584871 DEBUG [176.14.216.148:12007 OUT] msg 1:1002




not sure what to make of this either:
13:52:53.027995 INFO [162.217.114.218:44709 INC] Tx verification failed
13:52:53.028036 INFO WRONG TRANSACTION BLOB, Failed to parse, rejected
13:52:53.028071 INFO [162.217.114.218:44709 INC] Tx verification failed
13:55:45.998931 WARNING [149.167.15.12:49269 INC] Exception in connectionHandler: TcpConnection::read


Dev, can you explain?



I get those as well with 2.0.1 wallet
Code:
2017-Sep-14 20:28:05.408700 INFO [core] WRONG TRANSACTION BLOB, Failed to parse, rejected
2017-Sep-14 20:28:05.409200 INFO [protocol] [46.241.28.164:50236 INC] Tx verification failed
2017-Sep-14 20:28:05.409200 INFO [core] WRONG TRANSACTION BLOB, Failed to parse, rejected
2017-Sep-14 20:28:05.409200 INFO [protocol] [46.241.28.164:50236 INC] Tx verification failed
2017-Sep-14 20:28:05.409200 INFO [core] WRONG TRANSACTION BLOB, Failed to parse, rejected
2017-Sep-14 20:28:05.409200 INFO [protocol] [46.241.28.164:50236 INC] Tx verification failed
2017-Sep-14 20:28:05.409200 INFO [core] WRONG TRANSACTION BLOB, Failed to parse, rejected
2017-Sep-14 20:28:05.409700 INFO [protocol] [46.241.28.164:50236 INC] Tx verification failed
I assume that's a node with out of date wallet getting kicked out.
newbie
Activity: 140
Merit: 0
just updated for linux but still unable to connect to mine77.net
Not sure what to make of these messages from daemon:
13:43:54.967973 TRACE [37.147.250.52:54700 INC] CLOSE CONNECTION
13:43:55.813540 TRACE JSON-RPC request: {"jsonrpc":"2.0","method":"getlastblockheader","params":{}}
13:43:55.813703 TRACE JSON-RPC response: {"jsonrpc":"2.0","result":{"block_header":{"depth":0,"difficulty":85742273,"hash":"93abd7474a7a52decaf0b224687a5087946281401ecdefcade35ad651f2dc1eb","height":6365,"major_version":1,"minor_version":0,"nonce":2811555,"orphan_status":false,"prev_hash":"7aabeb4a8b8af50625665bbc1283334e3eab80a2cdeaa377f7c80a60b6ad759f","reward":9308075381,"timestamp":1505410250},"status":"OK"}}
13:44:00.814538 TRACE JSON-RPC request: {"jsonrpc":"2.0","method":"getlastblockheader","params":{}}
13:44:00.814853 TRACE JSON-RPC response: {"jsonrpc":"2.0","result":{"block_header":{"depth":0,"difficulty":85742273,"hash":"93abd7474a7a52decaf0b224687a5087946281401ecdefcade35ad651f2dc1eb","height":6365,"major_version":1,"minor_version":0,"nonce":2811555,"orphan_status":false,"prev_hash":"7aabeb4a8b8af50625665bbc1283334e3eab80a2cdeaa377f7c80a60b6ad759f","reward":9308075381,"timestamp":1505410250},"status":"OK"}}
13:44:03.020937 TRACE [87.117.14.130:50934 INC] COMMAND_TIMED_SYNC
13:44:03.021159 DEBUG [87.117.14.130:50934 INC] msg 1:1002
13:44:03.484460 TRACE [5.3.137.96:12007 OUT] COMMAND_TIMED_SYNC
13:44:03.484632 DEBUG [5.3.137.96:12007 OUT] msg 1:1002
13:44:03.584666 TRACE [176.14.216.148:12007 OUT] COMMAND_TIMED_SYNC
13:44:03.584871 DEBUG [176.14.216.148:12007 OUT] msg 1:1002




not sure what to make of this either:
13:52:53.027995 INFO [162.217.114.218:44709 INC] Tx verification failed
13:52:53.028036 INFO WRONG TRANSACTION BLOB, Failed to parse, rejected
13:52:53.028071 INFO [162.217.114.218:44709 INC] Tx verification failed
13:55:45.998931 WARNING [149.167.15.12:49269 INC] Exception in connectionHandler: TcpConnection::read


Dev, can you explain?



It's because there was a short period of time where transactions were made when the new wallet was configured incorrectly.
All transaction made from now on should be fine, and after 60 blocks those messages should no longer be appearing.
newbie
Activity: 140
Merit: 0
Everything works now if you use the latest v2.0.1 windows wallet Smiley
Block times will take up to 20 minutes for the next few hours now, shortening with time. If you're not sure what wallet you have, just redownload from this link:
https://github.com/iridiumdev/iridium-qt-v2/releases/download/v2.0.1/Iridium-qt-fix.rar

^ This version works with latest Daemons, I can confirm.

I downloaded from this link, but when open wallet and go to Help menu and choose About Irididium wallet it show thta I have v 2.0.0 so it is 2.0.1 or 2.0.0?

It's 2.0.1 I just didn't change it on the about section sorry haha.
Jump to: