stevebrush
Member
 Offline
Activity: 361
Merit: 11
Iridium (IRD) dev
|
 |
February 07, 2018, 10:25:58 AM |
|
Most of miners comes to the "lower" fee taken by the pool but never look at the transaction fee...
|
|
|
|
Datapotomus
Newbie
Offline
Activity: 2
Merit: 0
|
|
February 07, 2018, 11:48:25 AM |
|
Agreed with waiting till after the dip. Also, you will want the whitepaper completed before you start trading. If the dev watches this thread let me know if you want any help writing the whitepaper. I have a fair amount of technical writing background. Also, sent in a donation in dash. It was small, but all I could at the time. I would suggest everyone do the same thing as well.
|
|
|
|
|
stevebrush
Member
Offline
Activity: 361
Merit: 11
Iridium (IRD) dev
|
|
February 07, 2018, 01:05:27 PM |
|
Agreed with waiting till after the dip. Also, you will want the whitepaper completed before you start trading. If the dev watches this thread let me know if you want any help writing the whitepaper. I have a fair amount of technical writing background. Also, sent in a donation in dash. It was small, but all I could at the time. I would suggest everyone do the same thing as well.
There is already one : https://docs.google.com/document/d/1Xb9u4_k_QzolUh9DTQSLxSATYdHxGdFB7cr7bRzYwhw/edit?usp=sharingbut I agree, it can be updated. Feel free to contact me. |
|
|
|
|
BobTrade
|
|
February 07, 2018, 01:12:21 PM |
|
is there any road map for this 1Q 2018?
|
|
|
|
|
|
sylph93
|
|
February 07, 2018, 04:21:28 PM |
|
Is IRD going to masternodes? IRD distribute a lot many coins in first year. What is plan for years after first year?
I think MN will be required for handling supply, demand level.
|
|
|
|
compiz
Newbie
Offline
Activity: 16
Merit: 0
|
|
February 07, 2018, 05:27:32 PM |
|
who can guide me on how to setup a pool for this coin?
google will guide you, bro  No it doesn't guide at all. All outdated info and for other coins. But hey, thanks for your input. |
|
|
|
|
|
BobTrade
|
|
February 07, 2018, 07:36:03 PM |
|
Is IRD going to masternodes? IRD distribute a lot many coins in first year. What is plan for years after first year?
I think MN will be required for handling supply, demand level.
They said no. I asked already once. |
|
|
|
|
KAMINSKINIK
Newbie
Offline
Activity: 28
Merit: 0
|
|
February 08, 2018, 03:15:33 AM |
|
Sent from one purse to another his purse 500 IRD and they were hanging. With a different purse it was written off, but on the other, they were received, but not available! What should I do?
I can see the tx stuck in mempool. Wait for the next fork, I will increase the max block size again. It will be payed. The problem this tx was sent with a mixin of 6, this made a too big transaction (64 or 65ko)... (It's the same problem for the 3 tx stucked there... I think I won't allow tx > 5 in next release.) Did you sent it with the wallet AND an intentionally mixin of 6 or is it a mixin bug ? : default is 5 but it send 6 ? On the "other" side, just wait 20 blocks after to the tx be confirmed. default is 5 |
|
|
|
|
|
JungleOnion
|
|
February 08, 2018, 05:38:26 AM |
|
Is IRD going to masternodes? IRD distribute a lot many coins in first year. What is plan for years after first year?
I think MN will be required for handling supply, demand level.
Please for the 100000000 time, IRD doesn't need masternodes! but please, I'm curious in your opinion as to how the coin needs MN to handle supply and demand levels. |
|
|
|
|
|
nhiatay
|
|
February 08, 2018, 07:43:52 AM |
|
|
|
|
|
|
stevebrush
Member
Offline
Activity: 361
Merit: 11
Iridium (IRD) dev
|
|
February 08, 2018, 08:08:31 AM |
|
Sent from one purse to another his purse 500 IRD and they were hanging. With a different purse it was written off, but on the other, they were received, but not available! What should I do?
I can see the tx stuck in mempool. Wait for the next fork, I will increase the max block size again. It will be payed. The problem this tx was sent with a mixin of 6, this made a too big transaction (64 or 65ko)... (It's the same problem for the 3 tx stucked there... I think I won't allow tx > 5 in next release.) Did you sent it with the wallet AND an intentionally mixin of 6 or is it a mixin bug ? : default is 5 but it send 6 ? On the "other" side, just wait 20 blocks after to the tx be confirmed. default is 5 Yes, I know this...  I just ask you if you sent this tx with an intentionally mixin at 6 ? |
|
|
|
|
BobTrade
|
|
February 08, 2018, 01:30:18 PM |
|
difficulty is extremely high for a coin that isn't listed on exchange yet...
|
|
|
|
|
kepas
Member
Offline
Activity: 426
Merit: 11
|
|
February 08, 2018, 03:06:40 PM |
|
any news about exchanges?
|
|
|
|
|
kepas
Member
Offline
Activity: 426
Merit: 11
|
|
February 08, 2018, 03:12:37 PM |
|
dev, you can try this exchage: https://tradeogre.com/marketsthey added other new and not new cryptonight coins for free |
|
|
|
|
KAMINSKINIK
Newbie
Offline
Activity: 28
Merit: 0
|
|
February 08, 2018, 04:08:09 PM |
|
Sent from one purse to another his purse 500 IRD and they were hanging. With a different purse it was written off, but on the other, they were received, but not available! What should I do?
I can see the tx stuck in mempool. Wait for the next fork, I will increase the max block size again. It will be payed. The problem this tx was sent with a mixin of 6, this made a too big transaction (64 or 65ko)... (It's the same problem for the 3 tx stucked there... I think I won't allow tx > 5 in next release.) Did you sent it with the wallet AND an intentionally mixin of 6 or is it a mixin bug ? : default is 5 but it send 6 ? On the "other" side, just wait 20 blocks after to the tx be confirmed. default is 5 Yes, I know this... I just ask you if you sent this tx with an intentionally mixin at 6 ? No, I sent it as it was by default 5 and the IRD was hanging. |
|
|
|
|
stevebrush
Member
Offline
Activity: 361
Merit: 11
Iridium (IRD) dev
|
|
February 09, 2018, 08:52:14 AM
Last edit: February 09, 2018, 10:06:31 AM by stevebrush |
|
Sent from one purse to another his purse 500 IRD and they were hanging. With a different purse it was written off, but on the other, they were received, but not available! What should I do?
I can see the tx stuck in mempool. Wait for the next fork, I will increase the max block size again. It will be payed. The problem this tx was sent with a mixin of 6, this made a too big transaction (64 or 65ko)... (It's the same problem for the 3 tx stucked there... I think I won't allow tx > 5 in next release.) Did you sent it with the wallet AND an intentionally mixin of 6 or is it a mixin bug ? : default is 5 but it send 6 ? On the "other" side, just wait 20 blocks after to the tx be confirmed. default is 5 Yes, I know this... I just ask you if you sent this tx with an intentionally mixin at 6 ? No, I sent it as it was by default 5 and the IRD was hanging. Yes I tried and notice this bug, it will be corrected : this is the same with the simplewallet, mixin is always increased by one. (edit) ok, this is a bytecoin feature to hide real output key in any case : transaction sender always add 1 to the asked mixin. I will not change this feature but I will change the "seeing level" in wallets so mixing will match and will have a minimum of 1. |
|
|
|
|
BobTrade
|
|
February 09, 2018, 07:42:33 PM |
|
Idk probably money lacking for listing it. So probably we didn't donate enough... |
|
|
|
|
KAMINSKINIK
Newbie
Offline
Activity: 28
Merit: 0
|
|
February 12, 2018, 07:50:49 AM |
|
Sent from one purse to another his purse 500 IRD and they were hanging. With a different purse it was written off, but on the other, they were received, but not available! What should I do?
I can see the tx stuck in mempool. Wait for the next fork, I will increase the max block size again. It will be payed. The problem this tx was sent with a mixin of 6, this made a too big transaction (64 or 65ko)... (It's the same problem for the 3 tx stucked there... I think I won't allow tx > 5 in next release.) Did you sent it with the wallet AND an intentionally mixin of 6 or is it a mixin bug ? : default is 5 but it send 6 ? On the "other" side, just wait 20 blocks after to the tx be confirmed. default is 5 Yes, I know this... I just ask you if you sent this tx with an intentionally mixin at 6 ? No, I sent it as it was by default 5 and the IRD was hanging. Yes I tried and notice this bug, it will be corrected : this is the same with the simplewallet, mixin is always increased by one. (edit) ok, this is a bytecoin feature to hide real output key in any case : transaction sender always add 1 to the asked mixin. I will not change this feature but I will change the "seeing level" in wallets so mixing will match and will have a minimum of 1. When you Steve plan the next fork to fix this situation, and then 500 IRD hang? |
|
|
|
|
stevebrush
Member
Offline
Activity: 361
Merit: 11
Iridium (IRD) dev
|
|
February 12, 2018, 08:35:04 AM |
|
Sent from one purse to another his purse 500 IRD and they were hanging. With a different purse it was written off, but on the other, they were received, but not available! What should I do?
I can see the tx stuck in mempool. Wait for the next fork, I will increase the max block size again. It will be payed. The problem this tx was sent with a mixin of 6, this made a too big transaction (64 or 65ko)... (It's the same problem for the 3 tx stucked there... I think I won't allow tx > 5 in next release.) Did you sent it with the wallet AND an intentionally mixin of 6 or is it a mixin bug ? : default is 5 but it send 6 ? On the "other" side, just wait 20 blocks after to the tx be confirmed. default is 5 Yes, I know this... I just ask you if you sent this tx with an intentionally mixin at 6 ? No, I sent it as it was by default 5 and the IRD was hanging. Yes I tried and notice this bug, it will be corrected : this is the same with the simplewallet, mixin is always increased by one. (edit) ok, this is a bytecoin feature to hide real output key in any case : transaction sender always add 1 to the asked mixin. I will not change this feature but I will change the "seeing level" in wallets so mixing will match and will have a minimum of 1. When you Steve plan the next fork to fix this situation, and then 500 IRD hang? I'm thinking about this situation as this is a normal behaviour of the protocol. The problem is that stucked transactions should be released after 1 week if they don't find a big enough block and re-balanced to the emitter. Currently, they are not. I'm working on it : Auto cancel after a shorter delay ( 2 or 3 days) or/and a possibility of manually canceling. I have more tests to do... |
|
|
|
stevebrush
Member
Offline
Activity: 361
Merit: 11
Iridium (IRD) dev
|
|
February 12, 2018, 09:11:41 AM |
|
When you Steve plan the next fork to fix this situation, and then 500 IRD hang?
I'm thinking about this situation as this is a normal behaviour of the protocol. The problem is that stucked transactions should be released after 1 week if they don't find a big enough block and re-balanced to the emitter. Currently, they are not. I'm working on it : Auto cancel after a shorter delay ( 2 or 3 days) or/and a possibility of manually canceling. I have more tests to do... Did you try to reset your wallet ? |
|
|
|
|
