Edit - Ok don't listen to me - Stratum was crashed before - but now seems to be working again.
Topic: [ANN] ¤ DMD Diamond 3.0 | Scarce ¤ Valuable ¤ Secure | PoS 3.0 | Masternodes 65% - page 653. (Read 1260677 times)
November 16, 2014, 05:56:47 AM
Edit - Ok don't listen to me - Stratum was crashed before - but now seems to be working again.
November 16, 2014, 02:19:46 AM
http://multipool.bit.diamonds/
[email protected]
INVEST ONCE -> EARN EACH DAY!
no power cost
no maintenance
no heat
no noise
nothing beside payouts
http://multipool.bit.diamonds/
email [email protected] for more infos
What's the best way to invest into DMD?
In my opinion you should split your investment into the following:
By buying 50% DMD direct and 50% into DMD Cloudmining
This way you can maximize your profit and stabilize the coin.
http://multipool.bit.diamonds/
[email protected]
Also by providing your referrer wallet address we can make sure both the investor and referrer both get bonus shares.
Got no referrer still want the bonus shares? Ask for a referrer here someone sure willing help ya get bonus shares.
November 16, 2014, 02:03:34 AM
another factor that lead to orphaned minting blocks is have a wallet without password protection
when u start a wallet without password protection its always unlocked for minting
if u start such a wallet and it is not full sync it try sometimes to mint even if not sync and that lead to guaranteed orphan attempts
better have a password protection and only unlock for minting when wallet is fully synced
edit:
lot people say their coin are 7 days old why they dont mint
POS from 7-30 days coin age only work for big coin pile
(small pile only very rare success here) and it cut the coin pile into 2 smaller pile.
so wait until ur coin age is above 30 days. then also medium sized coin pile will success in POS
and small coin pile will use group stake mechanism and try together (max 100 dmd) to mint and merge them into a single coin pile (max 100 DMD)
POS explained here:
http://bit.diamonds/community/index.php/topic,46.msg376.html#msg376
when u start a wallet without password protection its always unlocked for minting
if u start such a wallet and it is not full sync it try sometimes to mint even if not sync and that lead to guaranteed orphan attempts
better have a password protection and only unlock for minting when wallet is fully synced
edit:
lot people say their coin are 7 days old why they dont mint
POS from 7-30 days coin age only work for big coin pile
(small pile only very rare success here) and it cut the coin pile into 2 smaller pile.
so wait until ur coin age is above 30 days. then also medium sized coin pile will success in POS
and small coin pile will use group stake mechanism and try together (max 100 dmd) to mint and merge them into a single coin pile (max 100 DMD)
POS explained here:
http://bit.diamonds/community/index.php/topic,46.msg376.html#msg376
November 16, 2014, 01:57:58 AM
hello
some problem my stake
my wallet write
minting
your weight 1588
network weight is 958451
expected time to earn reward is 4 days
and the problem 3 days later no refreshing minting info .
my oldest coin is 2014.10.24 recieved my wallet
what the problem
my conf :
listen=0
noirc=1
connect=193.68.21.19
connect=54.191.208.14
connect=54.255.133.30
connect=54.86.164.216
bantime=600
thx
some problem my stake
my wallet write
minting
your weight 1588
network weight is 958451
expected time to earn reward is 4 days
and the problem 3 days later no refreshing minting info .
my oldest coin is 2014.10.24 recieved my wallet
what the problem
my conf :
listen=0
noirc=1
connect=193.68.21.19
connect=54.191.208.14
connect=54.255.133.30
connect=54.86.164.216
bantime=600
thx
ur coins are below 30 days old there the minting of small coin pile have very much luck involved
if u only plan have wallet open 2 days a month for minting wait until coins over 30 days age
if u mint 24/7 dont worry minting will happen
the crystal globe expected time to mint we display is no way a indicator u will mint in that timeframe
it just give ya a small idea about the region
ur minting will happen most likely
u can /10 *10 the value to have a more realistic view
so a 4 days displayed is more like between 1 and 40 days
also it does only refresh in unregular intervals.
i see most time estimated time to mint 1 hour and i mint like 2-10 times a day and not 24 times like a 1 hour estimate would make me expect
i think we will leave the weight u and network displayed but remove that estimated time when it create so much confusion
there is so much variables no one can calculate a expected time why we should display one
November 15, 2014, 09:50:20 PM
got 2 new minted blocks, but orphaned,
total 4 minted blocks, and 2 minted bloks orphaned
mine and mint in a wallet,and the same time ,
the mined blocks orphaned below 1/1000,but minted blocks orphaned 1/2
i don't know why.
Status: 0/unconfirmed
Date: 2014/11/16 08:05
Debit: 0.00 DMD
Net amount: -516.00 DMD
Transaction ID: 5e6a85731de67e3dbc518a34665a143390b5a79816324d4f6e18d8973fbb9a89
Status: 0/unconfirmed
Date: 2014/11/12 19:48
Debit: 0.00 DMD
Net amount: -345.00 DMD
Transaction ID: 9321a544ced3a3f2f465339d6ab0742d7a27f3dba2678016cceaedec84c94ac3
November 15, 2014, 07:02:27 PM
hello
anybody knows what happen the http://dmdpool.digsys.bg/
almost 2 days write We are investingating issues in the backend. Your shares and hashrate are safe and we will fix things ASAP.
Blockupdate disabled, blocks and transactions confirmations are delayed
thanks
anybody knows what happen the http://dmdpool.digsys.bg/
almost 2 days write We are investingating issues in the backend. Your shares and hashrate are safe and we will fix things ASAP.
Blockupdate disabled, blocks and transactions confirmations are delayed
thanks
ditto. An update on the problem and solution are in order IMO.
November 15, 2014, 06:55:04 PM
hello
anybody knows what happen the http://dmdpool.digsys.bg/
almost 2 days write We are investingating issues in the backend. Your shares and hashrate are safe and we will fix things ASAP.
Blockupdate disabled, blocks and transactions confirmations are delayed
thanks
anybody knows what happen the http://dmdpool.digsys.bg/
almost 2 days write We are investingating issues in the backend. Your shares and hashrate are safe and we will fix things ASAP.
Blockupdate disabled, blocks and transactions confirmations are delayed
thanks
I am sure Danbi is busy with real life. You are still mining it is just the stats and payouts have stopped. He is fast to fix it when he gets back online.
November 15, 2014, 02:40:47 PM
hello
some problem my stake
my wallet write
minting
your weight 1588
network weight is 958451
expected time to earn reward is 4 days
and the problem 3 days later no refreshing minting info .
my oldest coin is 2014.10.24 recieved my wallet
what the problem
my conf :
listen=0
noirc=1
connect=193.68.21.19
connect=54.191.208.14
connect=54.255.133.30
connect=54.86.164.216
bantime=600
thx
some problem my stake
my wallet write
minting
your weight 1588
network weight is 958451
expected time to earn reward is 4 days
and the problem 3 days later no refreshing minting info .
my oldest coin is 2014.10.24 recieved my wallet
what the problem
my conf :
listen=0
noirc=1
connect=193.68.21.19
connect=54.191.208.14
connect=54.255.133.30
connect=54.86.164.216
bantime=600
thx
November 15, 2014, 02:03:58 PM
hello
anybody knows what happen the http://dmdpool.digsys.bg/
almost 2 days write We are investingating issues in the backend. Your shares and hashrate are safe and we will fix things ASAP.
Blockupdate disabled, blocks and transactions confirmations are delayed
thanks
anybody knows what happen the http://dmdpool.digsys.bg/
almost 2 days write We are investingating issues in the backend. Your shares and hashrate are safe and we will fix things ASAP.
Blockupdate disabled, blocks and transactions confirmations are delayed
thanks
November 15, 2014, 08:09:41 AM
question: if we could code a way where mining rewards at dmd multipool will be converted into dmd cloudmining shares instead if dmd payouts. are there people who would use that payout option? we dont wana code something if noone gona use it. until yet i had 1 miner requesting thst new feature are there more who want this?
I would be glad of such a possibility. Current Situation of Mining very depressing. November 15, 2014, 08:09:03 AM
question: if we could code a way where mining rewards at dmd multipool will be converted into dmd cloudmining shares instead if dmd payouts. are there people who would use that payout option? we dont wana code something if noone gona use it. until yet i had 1 miner requesting thst new feature are there more who want this?
Cryptonit - that sounds interesting but I would want the choice available. Maybe if it was a switch or something that I could turn on or off?
what i think could be possible is that u get a second btc address for mining and deepending on address it creates shares or dmd but have to crosscheck that with multipool dev
Ah that sounds better - I like having the choice. Thanks.
November 15, 2014, 07:52:06 AM
I think I will soon stop mining at the multipool. In fact stop mining for good. Rewards are getting thiner and thiner every day and ccminer is unable to mine script coins which are the most profitable lately.
November 15, 2014, 07:39:25 AM
question: if we could code a way where mining rewards at dmd multipool will be converted into dmd cloudmining shares instead if dmd payouts. are there people who would use that payout option? we dont wana code something if noone gona use it. until yet i had 1 miner requesting thst new feature are there more who want this?
Cryptonit - that sounds interesting but I would want the choice available. Maybe if it was a switch or something that I could turn on or off?
what i think could be possible is that u get a second btc address for mining and deepending on address it creates shares or dmd but have to crosscheck that with multipool dev
November 15, 2014, 06:49:58 AM
question: if we could code a way where mining rewards at dmd multipool will be converted into dmd cloudmining shares instead if dmd payouts. are there people who would use that payout option? we dont wana code something if noone gona use it. until yet i had 1 miner requesting thst new feature are there more who want this?
Cryptonit - that sounds interesting but I would want the choice available. Maybe if it was a switch or something that I could turn on or off?
November 15, 2014, 05:57:03 AM
question: if we could code a way where mining rewards at dmd multipool will be converted into dmd cloudmining shares instead if dmd payouts. are there people who would use that payout option? we dont wana code something if noone gona use it. until yet i had 1 miner requesting thst new feature are there more who want this?
November 14, 2014, 11:04:31 PM
ROI @dmdcoin Cloudmining :
20,7% in 45 Days (over all)
(estimate 167% ROI per year! and add 50% POS on top!)
27,2% for a pre 1st September Investor.
(estimate 220% ROI per year! and add 50% POS on top!)
http://multipool.bit.diamonds/
email [email protected]
November 14, 2014, 10:39:21 PM
I have not seen a new post to this thread in almost 24 hours. Is everyone okay? Its unusual for everyone to be so quiet. 
everything is fine
CEO (alex) came home from a crypto-related business trip
and we are analyzing the results and possible opportunities
from time to time i have to work serious and cant be only entertainer on forum threads
November 14, 2014, 09:04:18 PM
I have not seen a new post to this thread in almost 24 hours. Is everyone okay? Its unusual for everyone to be so quiet.
November 13, 2014, 11:27:17 PM
Write 100 times the following (your choice where to write):
"I will not use addnode=1, noirc=0 or listen=1 if I am generating blocks, PoW or PoS. I Promise!"
"I will not use addnode=1, noirc=0 or listen=1 if I am generating blocks, PoW or PoS. I Promise!"
ok so CTO says use this conf for heavy mining and minting
Quote
Example entries in the config file:
listen=0
noirc=1
connect=193.68.21.19
connect=54.191.208.14
connect=54.255.133.30
connect=54.86.164.216
bantime=600
and delete old peers.dat
listen=0
noirc=1
connect=193.68.21.19
connect=54.191.208.14
connect=54.255.133.30
connect=54.86.164.216
bantime=600
and delete old peers.dat
i run the other "normal" conf and have no POS issues
fact is run the normal conf supports network with more possible peers
run the suggested "save" conf reduce ur chance to fall into a fork and
as we learned now to have ur wallet overloaded with serve nodes blockdata
and by this have limited resources left for minting
@daniel is wallet utilizing multiple CPU cores so we can say a multicore CPU can handle the tasks more easy?
i run a 8 core CPU so maybe thats the reason i never experienced any minting issues even with 50 connections?
I have 8 cores as well so I don't think that's the problem.
November 13, 2014, 09:16:48 PM
There seems to be some common myths of how POS works and why attempts fail.
By design, PoS is random. It can be forced of course, by modifying code to try to stake as many of your coins as possible, but this will *not* produce more rewards for you and will only result you having to wait longer for the next stake. The code is adjusted so staking happens 'regularly'. (except, it's random so no guarantees when)
This is not exactly as interest in the bank, where you have contract at which date exactly the bank pays back interest.
It is common misconception, that being 'away' from other nodes impacts your PoS negatively. While *in theory* it is so, one has to do some math to understand why it's not an issue *at all*. For example:
The current Internet has a maximum RTT of under 200ms worldwide. (ok, maybe 300?) If you are connected via two way satellite connection, that should go up to 600ms. This is .. 0.6 seconds for your block to reach the other node(s).
Compare that with the designed PoS interval of 600 seconds per PoS block. It is sometimes less, sometimes more. We talk statistics here, so it's essentially 600 seconds in the long run. This means, you have 1:1000 chance to miss a block in case you are connected via high-latency satellite link to the rest of the network. Should happen once every 1000 PoS blocks you discover, in the long run. (again, we talk statistics here, not someone's bad luck, or.. see below)
Now, if you are lucky, within Europe we have < 60ms RTT, so that gives "us" 1:10000 or 10 times better chances. This means, we could lose a PoS block every 10,000 blocks we generate, instead of "you poor satellite connected guys" who will lose one every 1000 blocks generated. Of course, next time your wallet will PoS, it will (statistically) succeed and because the coins were sitting there longer, you would generate the same profit (in percentages, more in absolute numbers).
By the way, there are many more factors, that influence the block acceptance and in general, they do introduce much larger delays, so the above examples are a bit extreme. Life is actually better with regards to RTT influence on PoS.
The real issues, besides doing PoS in a fork are different. It's one of the typical human sins, greed ;-)
More is not always better.
I am talking about the number of peers here!
There is a reason, why the wallet opens no more than 12 such connections by itself.
The reason is, the more connections you have, the more time you spend servicing them. Further, peers can request you feed them blocks, and if you have say 50 connections, each just booted, you spend pretty much all your time sending them blocks. This leaves you no time for PoS.
So even if you found a PoS (or PoW, same, or even greater problem) block, it will sit in the queue waiting to be sent to other nodes, while you feed them existing blocks (sometimes having to read from disk, do a lot of hash calculations etc).
In summary, PoS and large number of connections are a big no-no.
So those of you, who are having such difficulties
[teacher hat on]
Write 100 times the following (your choice where to write):
"I will not use addnode=1, noirc=0 or listen=1 if I am generating blocks, PoW or PoS. I Promise!"
If, after writing it 100 times, you still do not understand why, try writing it 100 more times. It helps, with time.
[teacher hat off]
Oh, and by the way, you will help reduce the network forks. Thanks!
By design, PoS is random. It can be forced of course, by modifying code to try to stake as many of your coins as possible, but this will *not* produce more rewards for you and will only result you having to wait longer for the next stake. The code is adjusted so staking happens 'regularly'. (except, it's random
This is not exactly as interest in the bank, where you have contract at which date exactly the bank pays back interest.
It is common misconception, that being 'away' from other nodes impacts your PoS negatively. While *in theory* it is so, one has to do some math to understand why it's not an issue *at all*. For example:
The current Internet has a maximum RTT of under 200ms worldwide. (ok, maybe 300?) If you are connected via two way satellite connection, that should go up to 600ms. This is .. 0.6 seconds for your block to reach the other node(s).
Compare that with the designed PoS interval of 600 seconds per PoS block. It is sometimes less, sometimes more. We talk statistics here, so it's essentially 600 seconds in the long run. This means, you have 1:1000 chance to miss a block in case you are connected via high-latency satellite link to the rest of the network. Should happen once every 1000 PoS blocks you discover, in the long run. (again, we talk statistics here, not someone's bad luck, or.. see below)
Now, if you are lucky, within Europe we have < 60ms RTT, so that gives "us" 1:10000 or 10 times better chances. This means, we could lose a PoS block every 10,000 blocks we generate, instead of "you poor satellite connected guys" who will lose one every 1000 blocks generated. Of course, next time your wallet will PoS, it will (statistically) succeed and because the coins were sitting there longer, you would generate the same profit (in percentages, more in absolute numbers).
By the way, there are many more factors, that influence the block acceptance and in general, they do introduce much larger delays, so the above examples are a bit extreme. Life is actually better with regards to RTT influence on PoS.
The real issues, besides doing PoS in a fork are different. It's one of the typical human sins, greed ;-)
More is not always better.
I am talking about the number of peers here!
There is a reason, why the wallet opens no more than 12 such connections by itself.
The reason is, the more connections you have, the more time you spend servicing them. Further, peers can request you feed them blocks, and if you have say 50 connections, each just booted, you spend pretty much all your time sending them blocks. This leaves you no time for PoS.
So even if you found a PoS (or PoW, same, or even greater problem) block, it will sit in the queue waiting to be sent to other nodes, while you feed them existing blocks (sometimes having to read from disk, do a lot of hash calculations etc).
In summary, PoS and large number of connections are a big no-no.
So those of you, who are having such difficulties
[teacher hat on]
Write 100 times the following (your choice where to write):
"I will not use addnode=1, noirc=0 or listen=1 if I am generating blocks, PoW or PoS. I Promise!"
If, after writing it 100 times, you still do not understand why, try writing it 100 more times. It helps, with time.
[teacher hat off]
Oh, and by the way, you will help reduce the network forks. Thanks!
I remember being told by you and Cryptonit the following:
https://bitcointalk.org/index.php?topic=580725.msg7861165;topicseen#msg7861165
https://bitcointalk.org/index.php?topic=580725.msg7856213;topicseen#msg7856213
https://bitcointalk.org/index.php?topic=580725.msg7856220;topicseen#msg7856220
Latency not an issue anymore?
What is addnode=1 ? I though addnode=IP
Jump to: