Author

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

member
Activity: 124
Merit: 10
That's just fine cryptonit, thnxs for the answer...


Not really a fan of the White Sox... I live and was born in Mallorca, Spain... So no actual relation lol!!
legendary
Activity: 3052
Merit: 1053
bit.diamonds | uNiq.diamonds
Just a quick question in between... any news about DMD multipool resuming payments??

I read someone saying the had issues with their wallet, but I have found no updates... Still mining there...

Thnxs!!

hi fellow friend of the white sox

as soon as cryptsy finished their maintainance cloud/multi will continue converting BTC towards DMD

all mining rewards and cloud rewards earned meantime will the be converted nothing is lost just payout delayed

last info by mullick (cryptsy wallet main engineer) was that their resync nearly finsihed and then to will cheack all failed withdraw tx

once the last conbversion round withdraw is fixed and split/send to multi/cloud users we can start a new conversion round

its in the nature of automated systems that u need to finsih one round before u can start next round

at least with the logic we used to code it
member
Activity: 124
Merit: 10
Just a quick question in between... any news about DMD multipool resuming payments??

I read someone saying the had issues with their wallet, but I have found no updates... Still mining there...

Thnxs!!
sr. member
Activity: 393
Merit: 250
danbi

I am sorry, but I can't well translate everything that you speak. also did not understand half of what is said by cryptonit.
language barrier.
no complete understanding of the parameter changeaddress=
leave it as is.




I will try with simpler sentences.

By design, Bitcoin will create new address for the change, when you send coins and there is change remaining.

It is designed this way, because people hope their transactions will remain anonymous. Nobody would know what they have in their own wallet. If you have an coin pile of 100 DMD and send 50 DMD to someone, the change will go to a new address. Nobody will know if that address is yours, until you spend it. It will also not know to which wallet the address belongs.

Some people like this and they demand it work this way. This is how Diamond behaves without setchangeaddress= setting.
This setting is unique to Diamond. I invented it.

When you use the setting, no new address is created for the change. It is send where you specify. It could be the same wallet, or different. It could be your wallet or someone else's.

Sorry for the language problems. English is not my native language. In a conversation both sides need to make some effort to understand each other.
By the way, I post these replies for other people who might have the same questions, too.
sr. member
Activity: 393
Merit: 250
I would always recommend people sync the chain from start. Except people want to use their wallets *now*. In which case I would always recommend they make periodic backups and start from there. A year old backup since we switched algorithms is wiser than starting from scratch.

I do start from scratch test almost every day, but this is to verify that no code changes introduce problems with the existing blockchain. Preserving existing blockchain is what is required if we talk about trust at all.

Considering it could take days, even under the best conditions to sync the chain from scratch, we provide from time to time backups from those "fresh sync" nodes. For those who trust us at least a bit and who have no time to wait. By the way, if people don't trust us, they should read and compile code by themselves, even better write their own wallet -- for we could sneak malicious code in the wallet too, right?

We had few forks in the recent month, all as it seems due to different reasons. Downloading an archive of the current blockchain is the fastest possible way to get people back online. OR, restoring from your own backup a month/week ago. I guess this is why people prefer doing it this way.
The bad blockchains are still being analysed for more details to help prevent it happening in the future (or converge faster), but there aren't many volunteers doing it so that process is slow Smiley


This is silly.

An exchange can have perfect security if they make their OWN backup of the chain every few days. They won't have to trust anyone else and still be able to recover quickly, with full confidence in the blockchain.

This procedure can be done by anyone, not just exchanges, if they don't want to trust someone else's chain. Better safer than sorry.

Due to the algorithm change in the past, syncing Diamond from scratch is painfully slow, until you reach the switch point (about one year ago). Working on fixing this issue, but it is very low priority at the moment, due to the options already mentioned.

The "distiled blockchain" posted on diamond.danbo.bg is generated always from scratch by an isolated node and contains minimal number of orphans and other junk.

Your statement, that Diamond suffers from forks and this is why you need to load an blockchain backup is not correct. You do not have to do this and Diamond is perfectly capable to load/verify it's blockchain.

Thanks for not spreading FUD.

Got the fork impression from posts in the forum.
Maybe you should give a detailed explantion to clear up exactly what is going on.
As it seems unclear.
I got it fixed but unknown why it forked.
I unlocked for minting and 3 transactions within two minutes.
All confirmed. Backed Up this database.
I am unstuck.lol

Never said it was not silly, just exchanges policy as far as I know.
Real question for you , is why won't the blockchain Reorg instead of the users having to restore old blockchains.
Plus this link was not fud , https://www.cryptsy.com/pages/status
It was to help you see their is an issue that needs to be resolved to get your cryptsy wallet working.
 Cool
legendary
Activity: 3052
Merit: 1053
bit.diamonds | uNiq.diamonds
What does work in the wallet and what does not,
if u see any function in wallet that dont work report it please i know none beside inaccurate pos time to mind mousover infos

cloudmining. Data link to spread sheets,
check terms of service https://multipool.bit.diamonds/attachments/Terms_of_use.pdf
roi stats u can find on website https://cloudmining.bit.diamonds/ by click on "roi stats"

Quote
How you need to be real careful with setchange address and your wallet.dat,
like every configuration setting u should know what u do
in case of the diamond.conf changeaddress=address u have to understand that every change is send to that address
if u enter a bad written address or a address which is not under ur control that change can be lost....
better explained by daniel himself https://bitcointalksearch.org/topic/m.11211712


@mister1k
it would be very welcome u support DMD with ur perfect english and create a well written guide
out of my answers and other information sources u trust
if u have follow up questions feel free to ask here

thx for ur ongoing support
hero member
Activity: 896
Merit: 520
...


u said urself auto merging coin piles will adapt the amounts of coin piles
once competition for POS blocks is high enough that some coin pile get no slot in 30 days
the coin pile will start to merge together when minting above 30 days age

u see the solution urself coin pile merge at POS but u dont see that we on our way again there?

now the network fill with coin piles so the POS diff raise again and once high enough coin merge will start again

a few hundred coin pile (even a few thousand pile) in a wallet is absolute no issue for the wallet

but yes once the total amount of transactions reach a point of multiple ten-thousands transactions its time to move coins into a new wallet

for a normal user wallet that will be multiple years 24/7 online wallet
Just to clarify.
Its not merging any two piles into one pile, Its not combining anything.WHEN?
Its split staking. DO you know what that means??
The POS diff  is not increasing!
What is the threshold of the Diff to start merging these piles???
You say when the POS diff increases it will merge??
When the Diff reaches some magic number or after 30 days??
What is the threshold??
How are the piles going to age 30 days if they are split staked maybe up to 9 times in 30 days??
There is not a single input in my wallet older than 041415. Today's date is 042715
It split staked every pile I had. And has merged ZERO.Is this just a onetime thing?

So enlighten me because,as you say, I see the solution yourself??
IF you put half as much effort into learning to Read Write and Speak English, as you do to posting pictures, we might be able to communicate effectively.
Your efforts so far are discouraging. POSTER BOY AT best.
Are you waiting 30 years of the coin roll out to start learning English  v1.0?
Honestly do you think you can be effective not making the effort??
or Does the Sympathy of others restrict you from doing so??
I got no problem admitting I am wrong, don't know what  I'm talking about etc.
I want to be wrong as I profit as well as everyone else, if so.
But if I am right we all Lose. I am trying to avoid that.
I challenge you to construct a Roadmap to Diamond Wealth and Sticky it to this thread.

Roadmap
of the config file and setup for new/old users,
Minimum System requirements for wallet,
What are all the options available to us in the config and how to implement,
How does the minting process function with examples of real world scenarios,
What does work in the wallet and what does not,
What is My weight for minting. What is network weight,
How to clean up the wallet over time from unconfirmed minting/mining transactions,
How to use coin control effectively where Diamond is concerned. Pro and cons,
How to restore the wallet. Steps
How and where to check your not forked,
How does the reactor work/cloudmining. Data link to spread sheets,
How you need to be real careful with setchange address and your wallet.dat,
Etc Etc.
I am sure there is a lot more that could be in this Roadmap/FAQ/readme
You don't even have a readme for the software with any version.
All new /old users would benefit. Like an owners manual.
A Picture won't cut it.
xcel works great for Roadmaps.
You can even paste in your pretty pictures.
Diamond Roadmap to Wealth.

If YOU are NOT into the Continuous Improvement of Diamond, then DON'T put forth the EFFORT.
It will be the same effort as English.
And don't give me the excuse that Pg 1 of this thread has all required information.
Its a unorganized collage of logos and pictures.
IF it was effective people wouldn't need to post the simplest of questions.
Tip of the Day:If your Weight is greater than the network weight your FORKED.


legendary
Activity: 1092
Merit: 1000
This is silly.

An exchange can have perfect security if they make their OWN backup of the chain every few days. They won't have to trust anyone else and still be able to recover quickly, with full confidence in the blockchain.

This procedure can be done by anyone, not just exchanges, if they don't want to trust someone else's chain. Better safer than sorry.

Due to the algorithm change in the past, syncing Diamond from scratch is painfully slow, until you reach the switch point (about one year ago). Working on fixing this issue, but it is very low priority at the moment, due to the options already mentioned.

The "distiled blockchain" posted on diamond.danbo.bg is generated always from scratch by an isolated node and contains minimal number of orphans and other junk.

Your statement, that Diamond suffers from forks and this is why you need to load an blockchain backup is not correct. You do not have to do this and Diamond is perfectly capable to load/verify it's blockchain.

Thanks for not spreading FUD.

Got the fork impression from posts in the forum.
Maybe you should give a detailed explantion to clear up exactly what is going on.
As it seems unclear.
I got it fixed but unknown why it forked.
I unlocked for minting and 3 transactions within two minutes.
All confirmed. Backed Up this database.
I am unstuck.lol

Never said it was not silly, just exchanges policy as far as I know.
Real question for you , is why won't the blockchain Reorg instead of the users having to restore old blockchains.
Plus this link was not fud , https://www.cryptsy.com/pages/status
It was to help you see their is an issue that needs to be resolved to get your cryptsy wallet working.
 Cool
legendary
Activity: 3052
Merit: 1053
bit.diamonds | uNiq.diamonds
http://dmdeu.miningfield.com/  is ready for beeing used
the token expired problem was not be able to be reproduced today and register account did work
hero member
Activity: 505
Merit: 500
danbi

I am sorry, but I can't well translate everything that you speak. also did not understand half of what is said by cryptonit.
language barrier.
no complete understanding of the parameter changeaddress=
leave it as is.


sr. member
Activity: 393
Merit: 250

developers

how, when and how many time it is necessary to apply the setchangeaddress parameter when I am withdrawal from a wallet?
I don't know how it works.

if u dont set a changeaddress ur wallet will create a new address for everytime a transaction create a change returned to u
the change addresses only visible in coin control

when u add it to diamond.conf
changeaddress=youraddress
its always active if u use there ur mainadress u will get the change always back there

if u want to use it only for actual session u can set it at wallet gui


This parameter is needed, that not to increase quantity of the hidden addresses and not to increase the "weight" of the wallet?
if so, then why this feature is not enabled by default?

The wallet does not know what address you want to use for the change and it also does not know if you would not prefer the bitcoin default protocol to create new address for the change, to make it more difficult to track what exactly is in your wallet.

This is why this option can not be enabled by default.

By the way, you could set the change address to some other wallet, not the one for which the configuration is applied.
sr. member
Activity: 393
Merit: 250

That should work for your users, but I believe the exchanges have security policy set , that they always have to let the wallets sync the blockchain and they can't use bootstrap or chain downloads.

 Cool

This is silly.

An exchange can have perfect security if they make their OWN backup of the chain every few days. They won't have to trust anyone else and still be able to recover quickly, with full confidence in the blockchain.

This procedure can be done by anyone, not just exchanges, if they don't want to trust someone else's chain. Better safer than sorry.

Due to the algorithm change in the past, syncing Diamond from scratch is painfully slow, until you reach the switch point (about one year ago). Working on fixing this issue, but it is very low priority at the moment, due to the options already mentioned.

The "distiled blockchain" posted on diamond.danbo.bg is generated always from scratch by an isolated node and contains minimal number of orphans and other junk.

Your statement, that Diamond suffers from forks and this is why you need to load an blockchain backup is not correct. You do not have to do this and Diamond is perfectly capable to load/verify it's blockchain.

Thanks for not spreading FUD.
legendary
Activity: 3052
Merit: 1053
bit.diamonds | uNiq.diamonds
great job guys!
even with miningfield pool have startup troubles with register accounts
u managed to spread hashrate so no pool is above 40% of POW (20% of new blocks)
keep up the good work balancing hashrate between pools

also we can see POS works like a clockwork exact 50% of blocks

legendary
Activity: 3052
Merit: 1053
bit.diamonds | uNiq.diamonds
The massive sell wall on cryptsy is now gone Smiley I wonder whom that could've been.  Back into the rich list.

lets say im pretty impressed how stable price is after all that troubles we had

that make me very optimistic for the future when issues solved
and stability is again a word u can connect with dmd network
sr. member
Activity: 302
Merit: 250
Never before 11 P.M.
The massive sell wall on cryptsy is now gone Smiley I wonder whom that could've been.  Back into the rich list.
legendary
Activity: 3052
Merit: 1053
bit.diamonds | uNiq.diamonds
hmmm seems people get  "token expired" when try to register at
http://dmdeu.miningfield.com/

luis is sleeping already he will look at it tomorrow

If you're having a "token expired" error while registering, empty your browser cache, restart browser and try again.

Also don't take too long to enter all the information

no matter how fast i try it always bring token expired even after delete all cache stuff and restart browser....

there must be a issue
legendary
Activity: 3052
Merit: 1053
bit.diamonds | uNiq.diamonds
cryptonit

I am interested in more safety of the file a wallet.dat, therefore I am interested parameter changeaddress=
example, hypothetical situation:
I posted a few coins in the outgoing transaction.
at this time the wallet creates additional hidden addresses...
and at this time for any reasons there is a failure of an operating system, turned off electricity and other.
under such circumstances the wallet can not manage to create the necessary hidden addresses and the file wallet.dat, will be damaged.
this leads to the loss of coins that have appeared in the wallet after the last backup file wallet.dat.
as example: was 1000 coins (I have a backup wallet.dat 1000 coins). I got 100 coins and sent 50. total wallet should remain in 1050 coins.
system crash (for any reason). wallet.dat damaged.
as a result I have only 1000 coins (backup wallet.dat 1000 coins), but not 1050.
you understand that I want to tell?
Even if such a situation may occur once every 10 years, this could lead to loss of all the coins. I understand that there is still a lot of other options damage wallet.dat, but I'm talking about a parameter changeaddress=  in diamond.conf.
If do not create hidden addresses the probability of damage is much lower.
Correct me if I'm wrong.

If I have 3 addresses in wallet the fact that in this case I need to write in diamond.conf?



the parameter changeaddress=

is allready implemented in code u can add it to ur diamond.conf

just write the address where u want u change to be send

also ur szenario is very unlikely (or even impossible)  to be able use a change address the change address must be created
when its created its stored in wallet.dat only when its existing the transactions which use it for change can be made

so when if u say ur computer crashed before the change address is stored then no transaction happened that use this address.... and nothing lost
hero member
Activity: 505
Merit: 500
cryptonit

I am interested in more safety of the file a wallet.dat, therefore I am interested parameter changeaddress=
example, hypothetical situation:
I posted a few coins in the outgoing transaction.
at this time the wallet creates additional hidden addresses...
and at this time for any reasons there is a failure of an operating system, turned off electricity and other.
under such circumstances the wallet can not manage to create the necessary hidden addresses and the file wallet.dat, will be damaged.
this leads to the loss of coins that have appeared in the wallet after the last backup file wallet.dat.
as example: was 1000 coins (I have a backup wallet.dat 1000 coins). I got 100 coins and sent 50. total wallet should remain in 1050 coins.
system crash (for any reason). wallet.dat damaged.
as a result I have only 1000 coins (backup wallet.dat 1000 coins), but not 1050.
you understand that I want to tell?
Even if such a situation may occur once every 10 years, this could lead to loss of all the coins. I understand that there is still a lot of other options damage wallet.dat, but I'm talking about a parameter changeaddress=  in diamond.conf.
If do not create hidden addresses the probability of damage is much lower.
Correct me if I'm wrong.

If I have 3 addresses in wallet the fact that in this case I need to write in diamond.conf?

member
Activity: 116
Merit: 10
hmmm seems people get  "token expired" when try to register at
http://dmdeu.miningfield.com/

luis is sleeping already he will look at it tomorrow

If you're having a "token expired" error while registering, empty your browser cache, restart browser and try again.

Also don't take too long to enter all the information
legendary
Activity: 3052
Merit: 1053
bit.diamonds | uNiq.diamonds
This parameter is needed, that not to increase quantity of the hidden addresses and not to increase the "weight" of the wallet?
if so, then why this feature is not enabled by default?

because we did take that part unchanged from our bitcoin anchestor

same as all coins who build up on bitcoin code base

but if demand is bog enought we can think about it

that we added the changeaddress= option for diamond.conf seems to me a acceptable solution

because how we know automated what addres people wana use as change address

the risc that no changeaddress setting make wallet heave only exist after a lot years for a normal useage

in that timeframe we can expect code changes that will take care about long term optimization of wallets

so short answer:

yes all kind of stuff to wallet dust optimisations this is on todo list but at low priority because for 99% of users feelable effects are multiple years away


Jump to: