Author

Topic: [ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency - page 6751. (Read 9724130 times)

legendary
Activity: 1176
Merit: 1036
Dash Developer
Yes, this is going to have to be assigned to eduffield as soon as darksend is completed,  Grin

I think it'll take him a week or two.  Cheesy

I think I'd rather have the main DEV out of jail. Not sure about you guys?

The Darkroad marketplace will pop up soon enough.


I wouldn't touch that with a ten foot stick  Smiley
hero member
Activity: 532
Merit: 500
Yes, this is going to have to be assigned to eduffield as soon as darksend is completed,  Grin

I think it'll take him a week or two.  Cheesy

I think I'd rather have the main DEV out of jail. Not sure about you guys?

The Darkroad marketplace will pop up soon enough.

hero member
Activity: 658
Merit: 500
The Buck Stops Here.
Here it is!

https://en.bitcoin.it/wiki/Securing_your_wallet

A pretty paranoid piece, so perhaps incorrect, however if you look down to the section that says Securing the Bitcoin-QT or bitcoind wallet, you'll see what I read.  Perhaps I'm understanding it wrongly.  Or perhaps it's wrong?  Please, smart guys and gals out there, check it out and confirm or clarify for us Smiley

Thanks Smiley

So when a backup is first created, it has all of your old keys plus 100 unused keys. After sending a transaction, it has 99 unused keys. After a total of 100 new-key actions, you will start using keys that are not in your backup. Since the backup does not have the private keys necessary for authorizing spends of these coins, restoring from the old backup will cause you to lose Bitcoins.


I hate to keep bringing this up, but could eduffield, CHAOSiTEC , InternetApe  or someone tell me if this is true or not?  Thanks so much!

It's my understanding that change addresses usually use the unused pool addresses, then every time you use 100 it will make another new 100 addresses to use. So you technically only need to backup whenever that mass generation happens.  

This about sums it up:

The wallet contains a pool of queued keys. By default there are 100 keys in the key pool. The size of the pool is configurable using the "-keypool" command line argument. When you need an address for whatever reason (send, “new address”, generation, etc.), the key is not actually generated freshly, but taken from this pool. A brand new address is generated to fill the pool back to 100. So when a backup is first created, it has all of your old keys plus 100 unused keys. After sending a transaction, it has 99 unused keys. After a total of 100 new-key actions, you will start using keys that are not in your backup. Since the backup does not have the private keys necessary for authorizing spends of these coins, restoring from the old backup will cause you to lose Bitcoins

Yup, that's what I was reading when I realized I would have to take a more active roll in backing up my wallet and wanted to spread the knowledge.  Sorry for being annoying today, but that was my exciting lesson for the day, LOL

So we can summarize this by : When we start to reach 100 transactions in our transction list (receive and send) we can think to make another BACKUP NOW IMMEDIATLY??!!!


As long as you make regular backups of your wallet you'll be fine. Also when i say regular backups, I mean before you do over 100 transactions. Almost impossible unless you've never been proactive with copying your wallet. So really nothing to worry about.

Also, even if you never did backup your wallet and went over 100 transactions and THEN backed it up, you will still have all your crypto. As long as you have access to the wallet. The only time it becomes an issue is when your restoring a backup of a wallet from months ago.
legendary
Activity: 1288
Merit: 1000
Here it is!

https://en.bitcoin.it/wiki/Securing_your_wallet

A pretty paranoid piece, so perhaps incorrect, however if you look down to the section that says Securing the Bitcoin-QT or bitcoind wallet, you'll see what I read.  Perhaps I'm understanding it wrongly.  Or perhaps it's wrong?  Please, smart guys and gals out there, check it out and confirm or clarify for us Smiley

Thanks Smiley

So when a backup is first created, it has all of your old keys plus 100 unused keys. After sending a transaction, it has 99 unused keys. After a total of 100 new-key actions, you will start using keys that are not in your backup. Since the backup does not have the private keys necessary for authorizing spends of these coins, restoring from the old backup will cause you to lose Bitcoins.


I hate to keep bringing this up, but could eduffield, CHAOSiTEC , InternetApe  or someone tell me if this is true or not?  Thanks so much!

It's my understanding that change addresses usually use the unused pool addresses, then every time you use 100 it will make another new 100 addresses to use. So you technically only need to backup whenever that mass generation happens. 

This about sums it up:

The wallet contains a pool of queued keys. By default there are 100 keys in the key pool. The size of the pool is configurable using the "-keypool" command line argument. When you need an address for whatever reason (send, “new address”, generation, etc.), the key is not actually generated freshly, but taken from this pool. A brand new address is generated to fill the pool back to 100. So when a backup is first created, it has all of your old keys plus 100 unused keys. After sending a transaction, it has 99 unused keys. After a total of 100 new-key actions, you will start using keys that are not in your backup. Since the backup does not have the private keys necessary for authorizing spends of these coins, restoring from the old backup will cause you to lose Bitcoins

Yup, that's what I was reading when I realized I would have to take a more active roll in backing up my wallet and wanted to spread the knowledge.  Sorry for being annoying today, but that was my exciting lesson for the day, LOL

So we can summarize this by : When we start to reach 100 transactions in our transction list (receive and send) we can think to make another BACKUP NOW IMMEDIATLY??!!!
hero member
Activity: 966
Merit: 1003
Yes, this is going to have to be assigned to eduffield as soon as darksend is completed,  Grin

I think it'll take him a week or two.  Cheesy
full member
Activity: 280
Merit: 100
The Future Of Work
Can anyone make a decentralized drug market please? Silkroad is fucked. I can sell over there ..
(potato's)
I missed this boat completly , started mining today , 50 coin per day *.*.
This coin can shoot up to 100m marketcap if it has a good running drugmarket. Silkroad is fucked.

The solution is decentralized anonymous market.. so you don't have idiots taking a huge cut loosing coins and general jackassery. It will happen... it has too.

Yes, this is going to have to be assigned to eduffield as soon as darksend is completed,  Grin
newbie
Activity: 42
Merit: 0
Can anyone make a decentralized drug market please? Silkroad is fucked. I can sell over there ..
(potato's)
I missed this boat completly , started mining today , 50 coin per day *.*.
This coin can shoot up to 100m marketcap if it has a good running drugmarket. Silkroad is fucked.

Not into the whole thing, but I can assure you you're not late. The price is extremely low right now.
full member
Activity: 280
Merit: 100
The Future Of Work
Here it is!

https://en.bitcoin.it/wiki/Securing_your_wallet

A pretty paranoid piece, so perhaps incorrect, however if you look down to the section that says Securing the Bitcoin-QT or bitcoind wallet, you'll see what I read.  Perhaps I'm understanding it wrongly.  Or perhaps it's wrong?  Please, smart guys and gals out there, check it out and confirm or clarify for us Smiley

Thanks Smiley

So when a backup is first created, it has all of your old keys plus 100 unused keys. After sending a transaction, it has 99 unused keys. After a total of 100 new-key actions, you will start using keys that are not in your backup. Since the backup does not have the private keys necessary for authorizing spends of these coins, restoring from the old backup will cause you to lose Bitcoins.


I hate to keep bringing this up, but could eduffield, CHAOSiTEC , InternetApe  or someone tell me if this is true or not?  Thanks so much!

It's my understanding that change addresses usually use the unused pool addresses, then every time you use 100 it will make another new 100 addresses to use. So you technically only need to backup whenever that mass generation happens. 

This about sums it up:

The wallet contains a pool of queued keys. By default there are 100 keys in the key pool. The size of the pool is configurable using the "-keypool" command line argument. When you need an address for whatever reason (send, “new address”, generation, etc.), the key is not actually generated freshly, but taken from this pool. A brand new address is generated to fill the pool back to 100. So when a backup is first created, it has all of your old keys plus 100 unused keys. After sending a transaction, it has 99 unused keys. After a total of 100 new-key actions, you will start using keys that are not in your backup. Since the backup does not have the private keys necessary for authorizing spends of these coins, restoring from the old backup will cause you to lose Bitcoins

Yup, that's what I was reading when I realized I would have to take a more active roll in backing up my wallet and wanted to spread the knowledge.  Sorry for being annoying today, but that was my exciting lesson for the day, LOL
full member
Activity: 281
Merit: 100
Can anyone make a decentralized drug market please? Silkroad is fucked. I can sell over there ..
(potato's)
I missed this boat completly , started mining today , 50 coin per day *.*.
This coin can shoot up to 100m marketcap if it has a good running drugmarket. Silkroad is fucked.

The solution is decentralized anonymous market.. so you don't have idiots taking a huge cut loosing coins and general jackassery. It will happen... it has too.
full member
Activity: 126
Merit: 100
Can anyone make a decentralized drug market please? Silkroad is fucked. I can sell over there ..
(potato's)
I missed this boat completly , started mining today , 50 coin per day *.*.
This coin can shoot up to 100m marketcap if it has a good running drugmarket. Silkroad is fucked.
legendary
Activity: 1176
Merit: 1036
Dash Developer
Here it is!

https://en.bitcoin.it/wiki/Securing_your_wallet

A pretty paranoid piece, so perhaps incorrect, however if you look down to the section that says Securing the Bitcoin-QT or bitcoind wallet, you'll see what I read.  Perhaps I'm understanding it wrongly.  Or perhaps it's wrong?  Please, smart guys and gals out there, check it out and confirm or clarify for us Smiley

Thanks Smiley

So when a backup is first created, it has all of your old keys plus 100 unused keys. After sending a transaction, it has 99 unused keys. After a total of 100 new-key actions, you will start using keys that are not in your backup. Since the backup does not have the private keys necessary for authorizing spends of these coins, restoring from the old backup will cause you to lose Bitcoins.


I hate to keep bringing this up, but could eduffield, CHAOSiTEC , InternetApe  or someone tell me if this is true or not?  Thanks so much!

It's my understanding that change addresses usually use the unused pool addresses, then every time you use 100 it will make another new 100 addresses to use. So you technically only need to backup whenever that mass generation happens. 

This about sums it up:

The wallet contains a pool of queued keys. By default there are 100 keys in the key pool. The size of the pool is configurable using the "-keypool" command line argument. When you need an address for whatever reason (send, “new address”, generation, etc.), the key is not actually generated freshly, but taken from this pool. A brand new address is generated to fill the pool back to 100. So when a backup is first created, it has all of your old keys plus 100 unused keys. After sending a transaction, it has 99 unused keys. After a total of 100 new-key actions, you will start using keys that are not in your backup. Since the backup does not have the private keys necessary for authorizing spends of these coins, restoring from the old backup will cause you to lose Bitcoins
full member
Activity: 280
Merit: 100
The Future Of Work
It's my understanding that change addresses usually use the unused pool addresses, then every time you use 100 it will make another new 100 addresses to use. So you technically only need to backup whenever that mass generation happens.  

I was told that every time you send coins and a change address is used, a new one is generated, so that there are always 100 addresses ready to be used. There is no mass generation. That also means that no matter when you make a backup, you have 100 sends left to make the next backup.


either way, I was under the impression that you only need one backup of your wallet and you're good.... as in for life, if your backup holds.  But one could quickly go through a hundred transactions, and if one didn't  periodically back up the wallet, one could lose the most recent transactions. 

Anyway, maybe everyone knows this, but I didn't.  My impression from reading stuff this past 2 months (I am green) was that one backup covered you Smiley
full member
Activity: 280
Merit: 100
The Future Of Work
Is it more profitable to mine DRK directly, or to mine something else like Doge or Mint and then trade for DRK?
It WAS more profitable to mine/buy MINT.
I bought at 7 sat.
And sell 25% at 42 to buy DRK cheap little under 0.001 ..

I'm happy with this...

Right now I'm searching a cpu-coin to mine, to buy more DRK because they still cheap @market. For the moment didn't find.
Mean while still minig DRK...

sigh, gotta have money to make money, LOL.

But you also have to make a move, and those here taking risks deserve your rewards!
full member
Activity: 280
Merit: 100
The Future Of Work
Here it is!

https://en.bitcoin.it/wiki/Securing_your_wallet

A pretty paranoid piece, so perhaps incorrect, however if you look down to the section that says Securing the Bitcoin-QT or bitcoind wallet, you'll see what I read.  Perhaps I'm understanding it wrongly.  Or perhaps it's wrong?  Please, smart guys and gals out there, check it out and confirm or clarify for us Smiley

Thanks Smiley

So when a backup is first created, it has all of your old keys plus 100 unused keys. After sending a transaction, it has 99 unused keys. After a total of 100 new-key actions, you will start using keys that are not in your backup. Since the backup does not have the private keys necessary for authorizing spends of these coins, restoring from the old backup will cause you to lose Bitcoins.


I hate to keep bringing this up, but could eduffield, CHAOSiTEC , InternetApe  or someone tell me if this is true or not?  Thanks so much!

Thank you so much, so it is true, and you can't rely on a single backup make "a long time ago" but rather, need to make backups periodically, and probably a good idea to do so after any large transaction.  Nobody talks about this, so had I not read this, I wouldn't know either.  At least I'm armed with this info now, and I'll backup periodically because of that Smiley

It's my understanding that change addresses usually use the unused pool addresses, then every time you use 100 it will make another new 100 addresses to use. So you technically only need to backup whenever that mass generation happens. 
hero member
Activity: 658
Merit: 500
okay i sold my dark until this dip end .....

bought at 0.0011 sold at same price ......hope this problem with exchange get fixed ...that dump scares me....

Rookie mistake.  Spartans hold.  Especially when DRK is clearly undervalued right now due to hacker dumps.

Check out this graph of BP stock price going through the oil spill.  This is right where I bought in to BP btw:



Love that graph. BP was my first trade. It lead me to my job now. Just bought up 500 more dark btw.
100%!!! I also liken this to tesla. The stock tanked when the cars battery's were catching fire due to drivers crashing into things. Now look at it. People were freaking out that the car would spontaneously combust. Sold all the way down to 120. Up to ~255.
hero member
Activity: 966
Merit: 1003
It's my understanding that change addresses usually use the unused pool addresses, then every time you use 100 it will make another new 100 addresses to use. So you technically only need to backup whenever that mass generation happens.  

I was told that every time you send coins and a change address is used, a new one is generated, so that there are always 100 addresses ready to be used. There is no mass generation. That also means that no matter when you make a backup, you have 100 sends left to make the next backup.
legendary
Activity: 1288
Merit: 1000
Is it more profitable to mine DRK directly, or to mine something else like Doge or Mint and then trade for DRK?
It WAS more profitable to mine/buy MINT.
I bought at 7 sat.
And sell 25% at 42 to buy DRK cheap little under 0.001 ..

I'm happy with this...

Right now I'm searching a cpu-coin to mine, to buy more DRK because they still cheap @market. For the moment didn't find.
Mean while still minig DRK...
legendary
Activity: 1176
Merit: 1036
Dash Developer
Here it is!

https://en.bitcoin.it/wiki/Securing_your_wallet

A pretty paranoid piece, so perhaps incorrect, however if you look down to the section that says Securing the Bitcoin-QT or bitcoind wallet, you'll see what I read.  Perhaps I'm understanding it wrongly.  Or perhaps it's wrong?  Please, smart guys and gals out there, check it out and confirm or clarify for us Smiley

Thanks Smiley

So when a backup is first created, it has all of your old keys plus 100 unused keys. After sending a transaction, it has 99 unused keys. After a total of 100 new-key actions, you will start using keys that are not in your backup. Since the backup does not have the private keys necessary for authorizing spends of these coins, restoring from the old backup will cause you to lose Bitcoins.


I hate to keep bringing this up, but could eduffield, CHAOSiTEC , InternetApe  or someone tell me if this is true or not?  Thanks so much!

It's my understanding that change addresses usually use the unused pool addresses, then every time you use 100 it will make another new 100 addresses to use. So you technically only need to backup whenever that mass generation happens. 
legendary
Activity: 1288
Merit: 1000
Darkcoin has been added to

The CPU Coin List

The CPU Coin List is a sortable page of alternate cryptocurrencies that are still profitable when mined on your CPU. Here is the CPU Coin List thread on Bitcointalk.

Does any one have or want to write a simple description for Darkcoin?

Should be interesting to aggrate some info like :
Lauch date of the coin
The actual number of coin mined
...
newbie
Activity: 51
Merit: 0
okay i sold my dark until this dip end .....

bought at 0.0011 sold at same price ......hope this problem with exchange get fixed ...that dump scares me....

Rookie mistake.  Spartans hold.  Especially when DRK is clearly undervalued right now due to hacker dumps.

Check out this graph of BP stock price going through the oil spill.  This is right where I bought in to BP btw:

https://i.imgur.com/NaAzbsc.png

Love that graph. BP was my first trade. It lead me to my job now. Just bought up 500 more dark btw.
Jump to: