[ANN] ¤ DMD Diamond 3.0 | Scarce ¤ Valuable ¤ Secure | PoS 3.0 | Masternodes 65% - page 656.

polanskiman

full member

Activity: 266

Merit: 100

Quote from: cryptonit on November 12, 2014, 11:22:33 AM

Quote from: polanskiman on November 12, 2014, 10:11:08 AM

Quote from: cryptonit on November 12, 2014, 10:02:25 AM

how well established ur node is in network is affecting the POS success chances
its the speed how fast the rumor that u found a new block is spreading in network that influnce the success chance

so addnode and listen=1 for sure helping additional a maxconnections=50 too
and static IP give another boost in connections because other wallets easy find u again

but it really should not matter if ur pos try a few times until successful
a unsuccessful POS atempt dont destroy coin-age

so what worry me more than unsuccessful POS atempts is the report like LTCMAXMYR

this have most time the origin in minting inside wrong fork and once return to main chain u need to run the repairwallet command to fix displayed balance

Already have all those configured in the wallet. Failed attempts happen as much as when I had a different configuration. The only thing I do not have is a fixed IP but that's the case for most people and unless paying 60 USD just for having an IP, this is not going to happen for me Wink

i forgot to add latency and when we analyzed that u had like three time higher than me towards the nodes connected with u

Yes that's what I explained earlier. The fact that I am far away (with many links and gateways to go through) is the major problem and unless networks are optimised this will not change for me.

shveicar

legendary

Activity: 1414

Merit: 1013

DMD info: https://diamond-info.github.io/

Why when Bitcoins grows, the price of the Diamonds fall? This is contrary to common sense.

hallared

full member

Activity: 150

Merit: 101

The hen or the egg

Quote from: kiklo on November 12, 2014, 03:56:47 PM

Quote from: cryptonit on November 12, 2014, 01:03:19 PM

Quote from: kiklo on November 12, 2014, 11:52:25 AM

In POS failed mintings are normal, one way to decrease the number that fail , is to use coin control
and combine the smaller amounts into a larger amount.
If you look at your chart everything that was over 13 interest minted, and most everything with under 1 interest failed to mint. We called it Dust when the amount are too small to mint.
So combining the dust (smaller amounts) together for minting will increase the chance of minting.
Fyi: Coin age does reset when you combine the smaller amounts.

Cool

dmd pos have a feature called group stake
coins with age abover 30 days and combined size below 100 dmd
try to mint together and if successful they merged together
manual use of coin control is not required
dmd have successful anti dust mechanism

but as the word pos atempt say they can fail
thats normal behavior and they will try again

What size amounts are Group staked together, because his interest attempts show a very small amount being minted. Which makes it look like the group stake is not working for him.
Question: does the group stake only occur at specific times?

Cool

Group stake only occurs for coins older than 30 days.

Before answering questions about DMD PoS it is suitable to have some knowledge. Please do some reading first.
http://bit.diamonds/community/index.php/topic,46.msg376.html#msg376

kiklo

legendary

Activity: 1092

Merit: 1000

Quote from: cryptonit on November 12, 2014, 01:03:19 PM

Quote from: kiklo on November 12, 2014, 11:52:25 AM

In POS failed mintings are normal, one way to decrease the number that fail , is to use coin control
and combine the smaller amounts into a larger amount.
If you look at your chart everything that was over 13 interest minted, and most everything with under 1 interest failed to mint. We called it Dust when the amount are too small to mint.
So combining the dust (smaller amounts) together for minting will increase the chance of minting.
Fyi: Coin age does reset when you combine the smaller amounts.

Cool

dmd pos have a feature called group stake
coins with age abover 30 days and combined size below 100 dmd
try to mint together and if successful they merged together
manual use of coin control is not required
dmd have successful anti dust mechanism

but as the word pos atempt say they can fail
thats normal behavior and they will try again

What size amounts are Group staked together, because his interest attempts show a very small amount being minted. Which makes it look like the group stake is not working for him.
Question: does the group stake only occur at specific times?

Cool

alba77

newbie

Activity: 11

Merit: 0

Thank you all for your answers. I will try some of the suggestions, and Pos patiently Grin

cryptonit

legendary

Activity: 3052

Merit: 1053

bit.diamonds | uNiq.diamonds

Quote from: kiklo on November 12, 2014, 11:52:25 AM

In POS failed mintings are normal, one way to decrease the number that fail , is to use coin control
and combine the smaller amounts into a larger amount.
If you look at your chart everything that was over 13 interest minted, and most everything with under 1 interest failed to mint. We called it Dust when the amount are too small to mint.
So combining the dust (smaller amounts) together for minting will increase the chance of minting.
Fyi: Coin age does reset when you combine the smaller amounts.

Cool

dmd pos have a feature called group stake
coins with age abover 30 days and combined size below 100 dmd
try to mint together and if successful they merged together
manual use of coin control is not required
dmd have successful anti dust mechanism

but as the word pos atempt say they can fail
thats normal behavior and they will try again

cryptonit

legendary

Activity: 3052

Merit: 1053

bit.diamonds | uNiq.diamonds

Quote from: lecaillou on November 12, 2014, 12:08:34 PM

Me I have no .conf file, 58 connection and no POS failed Grin

It is very important to add the .conf files?

as u proof it works fine without

lecaillou

newbie

Activity: 13

Merit: 0

Me I have no .conf file, 58 connection and no POS failed Grin

It is very important to add the .conf files?

kiklo

legendary

Activity: 1092

Merit: 1000

Quote from: polanskiman on November 12, 2014, 09:18:40 AM

Example:

In POS failed mintings are normal, one way to decrease the number that fail , is to use coin control
and combine the smaller amounts into a larger amount.
If you look at your chart everything that was over 13 interest minted, and most everything with under 1 interest failed to mint. We called it Dust when the amount are too small to mint.
So combining the dust (smaller amounts) together for minting will increase the chance of minting.
Fyi: Coin age does reset when you combine the smaller amounts.

Cool

paladin281978

hero member

Activity: 742

Merit: 500

Quote from: cryptonit on November 12, 2014, 11:19:25 AM

Quote from: paladin281978 on November 12, 2014, 10:08:06 AM

cryptonit

why when I write listen=1 then I have more than 50 connections
but when I write listen=0 then I have a maximum of 10-11 connections?

ur walle feel happy with around 12 connections an dont active establish more
with listen=1 u allow incomming connections to be established above that
up to ur maxconnections setting

I did not understand. Google translator does not understand the meaning of giving. Google does not understand the abbreviated words
what to write in .conf?
this?

listen=1
noirc=0
addnode=193.68.21.19
addnode=54.191.208.14
addnode=54.255.133.30
addnode=54.86.164.216
bantime=600
maxconnections=50

but on the first page stated that it is for:
This is for exchanges, and those who do a lot of transactions.

cryptonit

legendary

Activity: 3052

Merit: 1053

bit.diamonds | uNiq.diamonds

Quote from: polanskiman on November 12, 2014, 10:11:08 AM

Quote from: cryptonit on November 12, 2014, 10:02:25 AM

how well established ur node is in network is affecting the POS success chances
its the speed how fast the rumor that u found a new block is spreading in network that influnce the success chance

so addnode and listen=1 for sure helping additional a maxconnections=50 too
and static IP give another boost in connections because other wallets easy find u again

but it really should not matter if ur pos try a few times until successful
a unsuccessful POS atempt dont destroy coin-age

so what worry me more than unsuccessful POS atempts is the report like LTCMAXMYR

this have most time the origin in minting inside wrong fork and once return to main chain u need to run the repairwallet command to fix displayed balance

Already have all those configured in the wallet. Failed attempts happen as much as when I had a different configuration. The only thing I do not have is a fixed IP but that's the case for most people and unless paying 60 USD just for having an IP, this is not going to happen for me Wink

i forgot to add latency and when we analyzed that u had like three time higher than me towards the nodes connected with u

cryptonit

legendary

Activity: 3052

Merit: 1053

bit.diamonds | uNiq.diamonds

Quote from: paladin281978 on November 12, 2014, 10:08:06 AM

cryptonit

why when I write listen=1 then I have more than 50 connections
but when I write listen=0 then I have a maximum of 10-11 connections?

ur walle feel happy with around 12 connections an dont active establish more
with listen=1 u allow incomming connections to be established above that
up to ur maxconnections setting

polanskiman

full member

Activity: 266

Merit: 100

Quote from: cryptonit on November 12, 2014, 10:02:25 AM

how well established ur node is in network is affecting the POS success chances
its the speed how fast the rumor that u found a new block is spreading in network that influnce the success chance

so addnode and listen=1 for sure helping additional a maxconnections=50 too
and static IP give another boost in connections because other wallets easy find u again

but it really should not matter if ur pos try a few times until successful
a unsuccessful POS atempt dont destroy coin-age

so what worry me more than unsuccessful POS atempts is the report like LTCMAXMYR

this have most time the origin in minting inside wrong fork and once return to main chain u need to run the repairwallet command to fix displayed balance

Already have all those configured in the wallet. Failed attempts happen as much as when I had a different configuration. The only thing I do not have is a fixed IP but that's the case for most people and unless paying 60 USD just for having an IP, this is not going to happen for me Wink

paladin281978

hero member

Activity: 742

Merit: 500

cryptonit

why when I write listen=1 then I have more than 50 connections
but when I write listen=0 then I have a maximum of 10-11 connections?

cryptonit

legendary

Activity: 3052

Merit: 1053

bit.diamonds | uNiq.diamonds

how well established ur node is in network is affecting the POS success chances
its the speed how fast the rumor that u found a new block is spreading in network that influnce the success chance

so addnode and listen=1 for sure helping additional a maxconnections=50 too
and static IP give another boost in connections because other wallets easy find u again

but it really should not matter if ur pos try a few times until successful
a unsuccessful POS atempt dont destroy coin-age

so what worry me more than unsuccessful POS atempts is the report like LTCMAXMYR

this have most time the origin in minting inside wrong fork and once return to main chain u need to run the repairwallet command to fix displayed balance

polanskiman

full member

Activity: 266

Merit: 100

Quote from: cryptonit on November 12, 2014, 09:03:34 AM

Quote from: alba77 on November 12, 2014, 07:09:57 AM

I have some questions about Pos that hopefully someone can answer. I'm using the mac wallet and have tested both of the suggested configs from the OP (connect= and addnode=). Finally a Pos was successful Cheesy

but before that I got a lot of failed attempts. Does this have something to do with the mac wallet? If I remember right someone else wrote about this in the thread a long time ago, or? Is there any special config or other parameters I should use when "Posing"? No big deal really because it finally worked ok, I'm only curious Wink

i have no experience with the mac wallet
do we have mac wallet user here in comunity who can share their experiences?

failed POS atempts can happen but should be something rare
the involved coins should return into balance keep their coin-age and try again

This is not related to the platform so no worries on that side. Failed POS attempts happen for several reasons. One being that you are competing with other coins. And in my case since I am far far away from where all the main nodes are I do get failed POS attempts quite often. As I was told there is nothing I can do about it. Only remedy would be that nodes start popping up in my region which would enable my POS attempts getting submitted to the network faster.

Example:

cryptonit

legendary

Activity: 3052

Merit: 1053

bit.diamonds | uNiq.diamonds

Quote from: alba77 on November 12, 2014, 07:09:57 AM

I have some questions about Pos that hopefully someone can answer. I'm using the mac wallet and have tested both of the suggested configs from the OP (connect= and addnode=). Finally a Pos was successful Cheesy

but before that I got a lot of failed attempts. Does this have something to do with the mac wallet? If I remember right someone else wrote about this in the thread a long time ago, or? Is there any special config or other parameters I should use when "Posing"? No big deal really because it finally worked ok, I'm only curious Wink

i have no experience with the mac wallet
do we have mac wallet user here in comunity who can share their experiences?

failed POS atempts can happen but should be something rare
the involved coins should return into balance keep their coin-age and try again

cryptonit

legendary

Activity: 3052

Merit: 1053

bit.diamonds | uNiq.diamonds

Quote from: LTCMAXMYR on November 12, 2014, 07:37:56 AM

minted a block,the amount is spitted and unusable,
but " has not been successfully broadcast yet", the block is orphaned,
so,how to get back the original coins?

repairwallet in console can free coins
sometimes its required to restart wallet after repairwallet comand to make the changes visible

LTCMAXMYR

hero member

Activity: 609

Merit: 500

DMD,XZC

minted a block,the amount is spitted and unusable,
but " has not been successfully broadcast yet", the block is orphaned,
so,how to get back the original coins?

alba77

newbie

Activity: 11

Merit: 0

I have some questions about Pos that hopefully someone can answer. I'm using the mac wallet and have tested both of the suggested configs from the OP (connect= and addnode=). Finally a Pos was successful Cheesy

but before that I got a lot of failed attempts. Does this have something to do with the mac wallet? If I remember right someone else wrote about this in the thread a long time ago, or? Is there any special config or other parameters I should use when "Posing"? No big deal really because it finally worked ok, I'm only curious Wink

Topic: [ANN] ¤ DMD Diamond 3.0 | Scarce ¤ Valuable ¤ Secure | PoS 3.0 | Masternodes 65% - page 656. (Read 1260677 times)