)I'm interested in retrieving some clams from my reddit doge user account, in light of that....
Do you know who would owns the private keys of my dogetipbot address on reddit?,
would it be me, or Mohland of dogetipbot?
Thanks for your help
) 
Topic: [ANN][CLAM] CLAMs, Proof-Of-Chain, Proof-Of-Working-Stake, a.k.a. "Clamcoin" - page 323. (Read 1151252 times)
August 02, 2015, 09:31:14 AM
Sorry...slightly off topic )
I'm interested in retrieving some clams from my reddit doge user account, in light of that....
Do you know who would owns the private keys of my dogetipbot address on reddit?,
would it be me, or Mohland of dogetipbot?
Thanks for your help)
)I'm interested in retrieving some clams from my reddit doge user account, in light of that....
Do you know who would owns the private keys of my dogetipbot address on reddit?,
would it be me, or Mohland of dogetipbot?
Thanks for your help
) 
August 01, 2015, 10:07:55 PM
So does mean that it is showing me other coins that have already been dug up or are this new coins being produced (dug up).
Just curious ass to why it says "DIG" in the debug file. Thinking it was answered I just didn't pick up on it. I know that coins are dug up and all from the previous transactions in the block chain. Is it that when it says "DIG" I'm producing new coins?
Just curious ass to why it says "DIG" in the debug file. Thinking it was answered I just didn't pick up on it. I know that coins are dug up and all from the previous transactions in the block chain. Is it that when it says "DIG" I'm producing new coins?
It says "DIG" each time it accepts a block that moves one of the initial distribution outputs. If you're syncing the blockchain, you'll see it a lot as it accepts lots of blocks quickly. It doesn't distinguish between outputs owned by you and those owned by others.
There's no good reason for it to still be in the debug file really.
If you go to the 'console' page, type 'getinfo' and hit return, you'll see a bunch of information including something like the following:
"moneysupply" : 15250588.13048927,
"digsupply" : 329552.59638718,
"stakesupply" : 476186.72641731,
"activesupply" : 805739.32280449,
The "digsupply" number is the total number of coins from the initial distribution that have moved so far. As your client syncs, that number will increase. The "activesupply" is the sum of "digsupply" and "stakesupply", where "stakesupply" is the total number of coins created by staking.
August 01, 2015, 09:47:35 PM
So does mean that it is showing me other coins that have already been dug up or are this new coins being produced (dug up).
Just curious ass to why it says "DIG" in the debug file. Thinking it was answered I just didn't pick up on it. I know that coins are dug up and all from the previous transactions in the block chain. Is it that when it says "DIG" I'm producing new coins?
Just want to make sure I have all this correct.
Just curious ass to why it says "DIG" in the debug file. Thinking it was answered I just didn't pick up on it. I know that coins are dug up and all from the previous transactions in the block chain. Is it that when it says "DIG" I'm producing new coins?
Just want to make sure I have all this correct.
There is no way to precisely define, let alone identify, when a key has been imported into the client.
That said, the "DIG" you are referring references a distribution output which has moved or staked for the first time.
Plus, Your (Lenore) looking at your debug file. You should know if you imported a private key, or wallet.dat. If not, then the "dig" your seeing are other people digging clams.
August 01, 2015, 06:49:12 PM
So does mean that it is showing me other coins that have already been dug up or are this new coins being produced (dug up).
Just curious ass to why it says "DIG" in the debug file. Thinking it was answered I just didn't pick up on it. I know that coins are dug up and all from the previous transactions in the block chain. Is it that when it says "DIG" I'm producing new coins?
Just want to make sure I have all this correct.
Just curious ass to why it says "DIG" in the debug file. Thinking it was answered I just didn't pick up on it. I know that coins are dug up and all from the previous transactions in the block chain. Is it that when it says "DIG" I'm producing new coins?
Just want to make sure I have all this correct.
There is no way to precisely define, let alone identify, when a key has been imported into the client.
That said, the "DIG" you are referring references a distribution output which has moved or staked for the first time.
August 01, 2015, 06:38:47 PM
So does mean that it is showing me other coins that have already been dug up or are this new coins being produced (dug up).
Just curious ass to why it says "DIG" in the debug file. Thinking it was answered I just didn't pick up on it. I know that coins are dug up and all from the previous transactions in the block chain. Is it that when it says "DIG" I'm producing new coins?
Just want to make sure I have all this correct.
Just curious ass to why it says "DIG" in the debug file. Thinking it was answered I just didn't pick up on it. I know that coins are dug up and all from the previous transactions in the block chain. Is it that when it says "DIG" I'm producing new coins?
Just want to make sure I have all this correct.
August 01, 2015, 05:10:38 PM
Hello everyone, Weird that I tried to post and it wouldn't let me. Saying that I have posted within 360 seconds and I have to slow down. But yet I haven't ever posted. This is my first post however I am a troll.
Probably the previous "post" in that context was your login. I agree that the wording seems wrong.Quote
Anyways. I have a question about the CLAM Client. I was looking threw the debug file. And every once and a while I see the word "DIG". What does that mean. I get what error and accepted mean but every once and a while I see the "DIG" word.
Thank you. Have a great day everyone.
"digging" is when new clams are made active from the initial distribution. That is, if I understand correctly, the initial distribution of CLAMS was such that BTC,LTC, or DOGE addresses which were funded above a certain dust threshold on some date in 2014 (May something?) were set up so that the private key from these addresses could be used to fund a clam address with like 4.6 clams. People refer to new clams being entered into this system from this initual distribution as being "dug up".
August 01, 2015, 03:58:20 PM
Hello everyone, Weird that I tried to post and it wouldn't let me. Saying that I have posted within 360 seconds and I have to slow down. But yet I haven't ever posted. This is my first post however I am a troll.
Anyways. I have a question about the CLAM Client. I was looking threw the debug file. And every once and a while I see the word "DIG". What does that mean. I get what error and accepted mean but every once and a while I see the "DIG" word.
Thank you. Have a great day everyone.
Anyways. I have a question about the CLAM Client. I was looking threw the debug file. And every once and a while I see the word "DIG". What does that mean. I get what error and accepted mean but every once and a while I see the "DIG" word.
Thank you. Have a great day everyone.
August 01, 2015, 01:16:50 AM
EDIT: Also, the more that can get https://github.com/dooglus/bitcoin-seeder/tree/clam working and stable on long-term server resources, the better.
If anyone gets a server set up running that code and acting as a DNS server, please post the domain name so I can add it to the CLAM client source, for inclusion in a future release. Thanks.
July 31, 2015, 11:55:21 PM
Version 1.4.16 of the CLAM client has been released.
See https://github.com/nochowderforyou/clams/releases/tag/v1.4.16 for details and downloads.
See https://github.com/nochowderforyou/clams/releases/tag/v1.4.16 for details and downloads.
We would love to get this one upgraded to STABLE as soon as possible, given the DNS seed part of the changelog.
The more that can test this release and report possible problems - the better.
Thanks
A Mac build would be good too. I would make my own, but the instructions I was following included a step that needed to be done on a Mac and I won't have them in the house.
I understand what you mean, they have terrible manners at the dinner table and they're impossible to potty-train. However, if you make them a nice place in the backyard they can probably get along with your rabbits.
July 31, 2015, 10:11:44 PM
Version 1.4.16 of the CLAM client has been released.
See https://github.com/nochowderforyou/clams/releases/tag/v1.4.16 for details and downloads.
See https://github.com/nochowderforyou/clams/releases/tag/v1.4.16 for details and downloads.
We would love to get this one upgraded to STABLE as soon as possible, given the DNS seed part of the changelog.
The more that can test this release and report possible problems - the better.
Thanks
A Mac build would be good too. I would make my own, but the instructions I was following included a step that needed to be done on a Mac and I won't have them in the house.
July 31, 2015, 10:10:10 PM
Version 1.4.16 of the CLAM client has been released.
See https://github.com/nochowderforyou/clams/releases/tag/v1.4.16 for details and downloads.
See https://github.com/nochowderforyou/clams/releases/tag/v1.4.16 for details and downloads.
We would love to get this one upgraded to STABLE as soon as possible, given the DNS seed part of the changelog.
The more that can test this release and report possible problems - the better.
Thanks
EDIT: Also, the more that can get https://github.com/dooglus/bitcoin-seeder/tree/clam working and stable on long-term server resources, the better.
July 31, 2015, 07:02:23 PM
Version 1.4.16 of the CLAM client has been released.
See https://github.com/nochowderforyou/clams/releases/tag/v1.4.16 for details and downloads.
See https://github.com/nochowderforyou/clams/releases/tag/v1.4.16 for details and downloads.
July 30, 2015, 12:29:58 PM
Still only have 1 active connection. If this is the norm, CLAM looks more centralized then decentralized.
I just downloaded the 1.4.13 windows 64bit wallet and its syncing pretty fast, but its only connected to 1 active connection. This is after filling the clam.conf with a list of active nodes. What am I doing wrong?
Try adding this to clam.conf:
addnode=144.76.185.69:31174
addnode=199.233.246.224:31174
addnode=104.236.69.105:31174
addnode=104.236.149.112:31174
addnode=88.198.207.8:31174
addnode=162.213.195.88:31174
addnode=108.73.85.204:31174
addnode=104.236.83.126:31174
addnode=144.76.64.123:31174
addnode=176.37.47.241:31174
addnode=151.224.82.4:31174
addnode=128.199.167.77:31174
addnode=91.232.105.11:31174
addnode=52.5.155.203:31174
addnode=74.207.230.61:31174
addnode=144.76.239.66:31174
addnode=104.236.69.34:31174
addnode=216.73.219.20:31174
addnode=198.50.243.84:31174
addnode=151.80.33.164:31174
addnode=186.4.30.88:31174
addnode=109.236.85.42:31174
July 30, 2015, 11:17:35 AM
Still only have 1 active connection. If this is the norm, CLAM looks more centralized then decentralized.
I just downloaded the 1.4.13 windows 64bit wallet and its syncing pretty fast, but its only connected to 1 active connection. This is after filling the clam.conf with a list of active nodes. What am I doing wrong?
July 30, 2015, 01:35:07 AM
// Attempt to connect to each IP for each addnode entry until at least one is successful per addnode entry
// (keeping in mind that addnode entries can have many IPs if fNameLookup)
I get a bit lost in C++ code full of classes, vectors and BOOST_*, so I cannot confirm if the code actually does as I have presumed, however, even if it only uses the first IP, most DNS servers rotate multiple records in their reply, so the client would still use at least one random IP for each addnode.
// (keeping in mind that addnode entries can have many IPs if fNameLookup)
I get a bit lost in C++ code full of classes, vectors and BOOST_*, so I cannot confirm if the code actually does as I have presumed, however, even if it only uses the first IP, most DNS servers rotate multiple records in their reply, so the client would still use at least one random IP for each addnode.
It looks to me as if the code does what the comment says it will do: only connect to one IP address from each addnode entry. That should be enough though.
July 29, 2015, 09:18:48 PM
Why not just do this? From a quick look at the source it seems the client will properly handle a DNS lookup with multiple A records in the reply.
addnode=seed.clams.xyz
addnode=clam.just-dice.com
addnode=seed.clams.xyz
addnode=clam.just-dice.com
What does it do with the multiple records? I guessed it would only use one of them for each addnode, but I could be wrong.
This is the bit that stuck out in net.cpp (particularly the second line about multiple IPs if DNS is enabled)
// Attempt to connect to each IP for each addnode entry until at least one is successful per addnode entry
// (keeping in mind that addnode entries can have many IPs if fNameLookup)
I get a bit lost in C++ code full of classes, vectors and BOOST_*, so I cannot confirm if the code actually does as I have presumed, however, even if it only uses the first IP, most DNS servers rotate multiple records in their reply, so the client would still use at least one random IP for each addnode.
July 29, 2015, 02:47:20 PM
Why not just do this? From a quick look at the source it seems the client will properly handle a DNS lookup with multiple A records in the reply.
addnode=seed.clams.xyz
addnode=clam.just-dice.com
addnode=seed.clams.xyz
addnode=clam.just-dice.com
What does it do with the multiple records? I guessed it would only use one of them for each addnode, but I could be wrong.
July 29, 2015, 01:55:55 PM
Uggghhh I can't get my address off the phone, I can't see it.
The wallet keeps saying "Dogecoin wallet has stopped working" when I try to edit to see the whole address
Maybe I should just forget trying to get clams from that.
The wallet keeps saying "Dogecoin wallet has stopped working" when I try to edit to see the whole address
Maybe I should just forget trying to get clams from that.
Thats a problem with many wallets, especially for smartphones. They try to make it simple for the average user but make it annoying for experienced ones.
I dont like the mindset behind. At least it should have a pro checkbox.
Well I finally was able to view one address and I "dug" it in JustDice.. turns out I do have clams!
So I might have more than I think from other change addresses..
Now I just have to figure out how to get or "backup" the file off the phone, what a pain.
That's good news. Also, keep in mind that many of the mobile wallets (especially from a few years ago) tended to use the sending address as the change address so you may not have many in there (or you may, IDK). If your phone is rooted then it shouldn't be too hard to at least get the data files from the app pulled. Then you'll have to see what format they're in. I've played around quite a bit on android phones so send me a PM if you need advice.
Good luck!
July 29, 2015, 01:20:34 PM
I just downloaded the 1.4.13 windows 64bit wallet and its syncing pretty fast, but its only connected to 1 active connection. This is after filling the clam.conf with a list of active nodes. What am I doing wrong?
July 29, 2015, 10:52:40 AM
Uggghhh I can't get my address off the phone, I can't see it.
The wallet keeps saying "Dogecoin wallet has stopped working" when I try to edit to see the whole address
Maybe I should just forget trying to get clams from that.
Thats a problem with many wallets, especially for smartphones. They try to make it simple for the average user but make it annoying for experienced ones.The wallet keeps saying "Dogecoin wallet has stopped working" when I try to edit to see the whole address
Maybe I should just forget trying to get clams from that.
I dont like the mindset behind. At least it should have a pro checkbox.
So I might have more than I think from other change addresses..
Now I just have to figure out how to get or "backup" the file off the phone, what a pain.
It can indeed be a pain; especially for certain wallet software which doesn't provide easy access to keys.
Thankfully, there is a ~12$ USD incentive per distribution eligible address to help motivate you
Jump to: