big_coins
|
|
September 19, 2014, 07:16:07 AM |
|
Diamond network works fine in POS mode, I just sent 350 coins from one purse to another. But the mode of production new coin, is currently only available to those wallets that have coin. This is a good test of the entire system.
maybe good for system but very bad for the coin as liquidity just got killed.
|
|
|
|
shveicar
Legendary
Offline
Activity: 1414
Merit: 1013
DMD info: https://diamond-info.github.io/
|
|
September 19, 2014, 07:29:52 AM |
|
maybe good for system but very bad for the coin as liquidity just got killed.
On the contrary, very good, that the coin goes through various tests. For example NXT initially operates in 100% POS and they have no problems with liquidity. Soon developers will release a new wallet, and Diamond will be even more high-quality coin. I think soon, many will regret that did not buy a Diamond now at such a low cost
|
|
|
|
utahjohn
|
|
September 19, 2014, 07:31:36 AM |
|
I use intel boards (30 of them) for my farm. Never use powered risers totally not needed and I run 6 GPU per motherboard from 2 PSU's.
What board/cpu/ram combo, I have 1000W PS that is still good ... I'm using the cheap chinese powered USB3 cable risers ... Gigabyte 990FXA-UD3 + cheap ass semperon + 4GB cheap ass ram + cheap ass ribbon risers from mr ping. 2 x 1000w psu second one forced on by shorting pins 3/4 so its allways on Still a big replacement cost for mining but 990FXA-UD3 looks like a good choice if I can find cheap used components (fixed income retired ...) on ebay. Might be better off buying some hashrate when my check arrives, however now have GPU's sitting there on table doing nothing I'd rather be mining groestl directly ...
|
|
|
|
M0ndialu
|
|
September 19, 2014, 07:39:57 AM |
|
groestl mining pool ?
|
|
|
|
cryptonit
Legendary
Offline
Activity: 3038
Merit: 1053
bit.diamonds | uNiq.diamonds
|
|
September 19, 2014, 07:52:06 AM |
|
groestl mining pool ? direct groestl mining is on hold until next wallet release and the POW restart trigger is reached (so expect a week POS only mode because we dont want trigger POW acvtive to early all people must have a chance to upgrade wallet) meanwhile use http://multipool.bit.diamonds/there are a lot algos u can use to earn DMD
|
|
|
|
M0ndialu
|
|
September 19, 2014, 08:04:51 AM |
|
groestl mining pool ? direct groestl mining is on hold until next wallet release and the POW restart trigger is reached (so expect a week POS only mode because we dont want trigger POW acvtive to early all people must have a chance to upgrade wallet) meanwhile use http://multipool.bit.diamonds/there are a lot algos u can use to earn DMD ty
|
|
|
|
paladin281978
|
|
September 19, 2014, 09:01:09 AM |
|
Why DMD so sluggishly responds to changes course BTC compared with other coins?
|
|
|
|
cryptonit
Legendary
Offline
Activity: 3038
Merit: 1053
bit.diamonds | uNiq.diamonds
|
|
September 19, 2014, 10:47:05 AM |
|
Why DMD so sluggishly responds to changes course BTC compared with other coins?
why a rabbit runs faster than a elephant? because he must be able run for his life in a fast zig-zag changing direction his life is short and he have many things to fear the elephant can go slow but straight in the direction he want he dont have to fear anything he can trust in his own strength and durability i really hope we can slow down the value raise we want provide our cloudmining investores good DMD payouts if now DMD even without cloudmining raise so fast guess what happens when cloudmining kicks in...... paladin u can support price stability and counter price raising by sell ur DMD and invest in something that is in your eyes not sluggish
|
|
|
|
danbi
|
|
September 19, 2014, 11:24:34 AM |
|
if mining is turned off. How are coins sent and when they are sent where does the sending fee goto ?
The network does not care if it is an PoW or PoS block. Transactions get included in PoS (minted) blocks as well. The fee should be destroyed in this case. The drawback is, it's 10 times slower.. just as Bitcoin. The fee is destroyed That needs fixing then doesn't it. Make enough transactions and all the coins in circulation eventually will be destroyed. Amazing elementary stuff like this doesnt get fixed. Hehe, "you hold it wrong" With a PoS block, there are *always* new coins generated. As far as I remember however, the "transaction fees" are just dropped on the floor. This is *by design*. For example, you stake 1 DMD. Your earliest chance and least interest is after 7 days. With current 50% per year (365 days), this makes 7/365 DMD of interest, or about (rounded) 0.0192 DMD *created*. The typical transaction fee is 0.001 DMD, so you would have earned (as PoS miner) 0.0202 with the fee included. In fact, you also pay fees for that PoS block -- so a PoW miner could earn it if the next block is PoW. All this gives incentive for PoW miners. Not a perfect system, but burning fees is not really bad. it keeps inflation under control. In theory, with very low PoS rewards, that could happen, just as if you print only 1% of the banknotes in circulation and wear 2% of them -- at some point you will have no banknotes at all. But for Diamond such possibility is decades away.
|
BTC: 15cJkRupKAkGr6sTxj1Uzb6uHbvuRyK1GL DMD: dJZEqNcjiUiMMd8DKBFS9oMWtArAD2GCHr
|
|
|
danbi
|
|
September 19, 2014, 11:31:42 AM |
|
Diamond network works fine in POS mode, I just sent 350 coins from one purse to another. But the mode of production new coin, is currently only available to those wallets that have coin. This is a good test of the entire system.
The "hidden" (*) feature of Diamond is that nothing is lost (except hashrate at pools, sorry about that). The coin mechanics is based on total coins in circulation, so this 'slowdown' just increases the mining at 1 DMD per block interval with just as much. As we have focused initially in fixing PoS, all of the safety nets for PoS are already in place, we just postponed the inevitable fork to fix PoW. Again, this is an inherited bug, the bitcoin/ppcoin/novacoin code Diamond is based on is full of such crap. But, by slowly fixing it instead of just replacing it, as many other coins chose to do (it's way easier for developers), we preserve everyone's investment. (*) It's funny that this feature has been explained so many times by cryptonit and everyone seems to ignore it -- understandable, as Diamond is unique in this regard, and people assume it works just like other coins.
|
BTC: 15cJkRupKAkGr6sTxj1Uzb6uHbvuRyK1GL DMD: dJZEqNcjiUiMMd8DKBFS9oMWtArAD2GCHr
|
|
|
pokeytex
Legendary
Offline
Activity: 1504
Merit: 1002
|
|
September 19, 2014, 11:39:46 AM |
|
Diamond network works fine in POS mode, I just sent 350 coins from one purse to another. But the mode of production new coin, is currently only available to those wallets that have coin. This is a good test of the entire system.
The "hidden" (*) feature of Diamond is that nothing is lost (except hashrate at pools, sorry about that). The coin mechanics is based on total coins in circulation, so this 'slowdown' just increases the mining at 1 DMD per block interval with just as much. As we have focused initially in fixing PoS, all of the safety nets for PoS are already in place, we just postponed the inevitable fork to fix PoW. Again, this is an inherited bug, the bitcoin/ppcoin/novacoin code Diamond is based on is full of such crap. But, by slowly fixing it instead of just replacing it, as many other coins chose to do (it's way easier for developers), we preserve everyone's investment. (*) It's funny that this feature has been explained so many times by cryptonit and everyone seems to ignore it -- understandable, as Diamond is unique in this regard, and people assume it works just like other coins. Just sent you a little surprise for all of your hard work - Thank You!
|
|
|
|
Reggie0
Member
Offline
Activity: 107
Merit: 13
|
|
September 19, 2014, 05:16:31 PM |
|
Your analisys is good and indeed it seems the better way to address the problem. Is there no problem for nActualSpacing > nTargetTimespan?
No, it is part of the normal operation. Doing some more tests, it seems that once we let this "negative" number in, it keeps staying negative. I am experimenting now with adding the same "make positive" code for bnNew as well. Do you see any problems with this?
Probably it will work fine except a little diff disturbance, but it requires testing. Also, while we are at this stage that requires forking, do you have any other code improvement suggestions?
Sorry, I spend only 3 hours to inspect the source code, therefore I'm a beginner:)
|
|
|
|
popshot (OP)
|
|
September 19, 2014, 10:47:39 PM |
|
Sorry, I spend only 3 hours to inspect the source code, therefore I'm a beginner:)
Reggie0, I hope you will become a permanent community member. Thank you for all your insight. ---- Diamond Wallet update 2.0.4 will be realesed in the morning (UTC time). Because it's a hardfork situation PoW fix is deleyed by about 7 days so everyone has a chance to update - Cryptsy here we go again
|
|
|
|
Reggie0
Member
Offline
Activity: 107
Merit: 13
|
|
September 20, 2014, 01:59:52 AM |
|
Reggie0, I hope you will become a permanent community member. Thank you for all your insight. ---- Diamond Wallet update 2.0.4 will be realesed in the morning (UTC time). Because it's a hardfork situation PoW fix is deleyed by about 7 days so everyone has a chance to update - Cryptsy here we go again Thank you! I was since the beginings just in read only mode:)
|
|
|
|
danbi
|
|
September 20, 2014, 10:15:21 AM |
|
Reggie0, I hope you will become a permanent community member. Thank you for all your insight. ---- Diamond Wallet update 2.0.4 will be realesed in the morning (UTC time). Because it's a hardfork situation PoW fix is deleyed by about 7 days so everyone has a chance to update - Cryptsy here we go again Thank you! I was since the beginings just in read only mode:) Okay, what you think about our nActualTimespan pacing code. We are now targeting for if (nActualSpacing < 0) nActualSpacing=nTargetSpacing; if (nActualSpacing > nTargetTimespan) nActualSpacing=nTargetTimespan; The idea is to limit the difficulty drop after a long period of inactivity. Like, for example when a multi pool has hit us and risen the difficulty way above the typical network hash rate and results in long period of no blocks found. Then, without this pacing, difficulty will drop to very low levels and a multi pool could abuse it again. This code has been in use for PoS for months (with first case assigning 1) -- we will now make it work for PoW too.
|
BTC: 15cJkRupKAkGr6sTxj1Uzb6uHbvuRyK1GL DMD: dJZEqNcjiUiMMd8DKBFS9oMWtArAD2GCHr
|
|
|
cryptonit
Legendary
Offline
Activity: 3038
Merit: 1053
bit.diamonds | uNiq.diamonds
|
|
September 20, 2014, 10:17:12 AM Last edit: September 20, 2014, 01:32:20 PM by cryptonit |
|
Reggie0, I hope you will become a permanent community member. Thank you for all your insight. ---- Diamond Wallet update 2.0.4 will be realesed in the morning (UTC time). Because it's a hardfork situation PoW fix is deleyed by about 7 days so everyone has a chance to update - Cryptsy here we go again Thank you! I was since the beginings just in read only mode:) thx for ur loyal support thats the true strength of diamond the people we share a dream and we work to make it come true and our dream isnt about fast easy cash we dream about longterm financial freedom for any serious dmd investor
|
|
|
|
Reggie0
Member
Offline
Activity: 107
Merit: 13
|
|
September 20, 2014, 01:31:56 PM |
|
Reggie0, I hope you will become a permanent community member. Thank you for all your insight. ---- Diamond Wallet update 2.0.4 will be realesed in the morning (UTC time). Because it's a hardfork situation PoW fix is deleyed by about 7 days so everyone has a chance to update - Cryptsy here we go again Thank you! I was since the beginings just in read only mode:) Okay, what you think about our nActualTimespan pacing code. We are now targeting for if (nActualSpacing < 0) nActualSpacing=nTargetSpacing; if (nActualSpacing > nTargetTimespan) nActualSpacing=nTargetTimespan; The idea is to limit the difficulty drop after a long period of inactivity. Like, for example when a multi pool has hit us and risen the difficulty way above the typical network hash rate and results in long period of no blocks found. Then, without this pacing, difficulty will drop to very low levels and a multi pool could abuse it again. This code has been in use for PoS for months (with first case assigning 1) -- we will now make it work for PoW too. Use a nonlinear formula, not limiting: if (nActualSpacing > nTargetTimespan) nActualSpacing=nTargetTimespan+F(nActualSpacing-nTargetTimespan); F could be sqrt or something else which result is below the linear one's. Do simulations which gives the best tradeoff between blockchain blocking and diff. drop.
|
|
|
|
|
chris_dmd
Newbie
Offline
Activity: 57
Merit: 0
|
|
September 20, 2014, 10:17:43 PM |
|
Something strange happening to wallet. Keeps producing " ? " over 100 already?
|
|
|
|
cryptonit
Legendary
Offline
Activity: 3038
Merit: 1053
bit.diamonds | uNiq.diamonds
|
|
September 20, 2014, 10:24:20 PM |
|
Something strange happening to wallet. Keeps producing " ? " over 100 already?
PoW reactivation will happen in about a week time - 27/28 September - block 577850 dont mine now!
|
|
|
|
|