Tried it, how long does the rescan take? because the wallet still reads 0.00. I have headless wallet so I ran "clamd -rescan".
The time it takes is dependent on the number of transactions in your wallet. I think it should take less than 10 minutes if you don't have many. You need to shut down your current clamd first: $ clamd stop Then start a new one: $ clamd -rescan Didn't do anything. Balance still 0.00. I think I have a broken wallet. But repair wallet doesn't help either. Did you try dumpprivkey on that address... get the private key and re-import to a new wallet file... just what I would try.. |
|
|
|
Is there some way with the linux daemon to tell the date / timestamp of the last stake that occurred?
I have over 1.5k split up in small amounts and seems like almost over a week since my last stake.. is that normal?
(Used to seem like almost every day or every other day it would stake)
I don't know of a simple way, but this works for me: $ clamd listtransactions '*' 10 | grep -A10 -E '"category" : "(immature|generate)"' | grep -E '"(category|time)"' | awk '{print $3}' | tr -d ',"' | while read category; do read time; echo "$(date -d @$time) : $category"; done
Change the 10 in the 4th word to a higher number if you have a lot of non-staking transactions since the most recent stake. Thanks, but that shows nothing for me. There is no output. Is it because i'm on version "version" : "v1.4.17-7-gac5324a" ? bump... trying to update, I guess I'll see if that helps... I still don't get why staking seems to have stopped, it says "true" in getstakinginfo & timeoffset is -1 |
|
|
|
Is there some way with the linux daemon to tell the date / timestamp of the last stake that occurred?
I have over 1.5k split up in small amounts and seems like almost over a week since my last stake.. is that normal?
(Used to seem like almost every day or every other day it would stake)
I don't know of a simple way, but this works for me: $ clamd listtransactions '*' 10 | grep -A10 -E '"category" : "(immature|generate)"' | grep -E '"(category|time)"' | awk '{print $3}' | tr -d ',"' | while read category; do read time; echo "$(date -d @$time) : $category"; done
Change the 10 in the 4th word to a higher number if you have a lot of non-staking transactions since the most recent stake. Thanks, but that shows nothing for me. There is no output. Is it because i'm on version "version" : "v1.4.17-7-gac5324a" ? |
|
|
|
|
Is there some way with the linux daemon to tell the date / timestamp of the last stake that occurred?
I have over 1.5k split up in small amounts and seems like almost over a week since my last stake.. is that normal?
(Used to seem like almost every day or every other day it would stake)
|
|
|
|
Possible workarounds include making a separate wallet and importing only the private keys you want to spend from
I made a separate wallet.dat, had coins deposited to that, then just did the splitting from there to an address that is in the other wallet.dat. I don't know if that's ok, but seems to have worked.... ? |
|
|
|
|
Dooglus or other devs.. I need help.
I'm using the daemon on linux. I don't know how to explain this, I'll try.
How do I do the splitting '{"count":c,"amount":a}' thing but within the same wallet - after having done once before with new coins that I deposited to wallet, I'm finding that it might "pull" from the other address to do the splitting ... and mess up.
So, like how do I just split *from* the one address without having touched or messed with coins sitting in other addresses???
Does that make sense?
Thanks in advance..
|
|
|
|
how do I use -staketo just this?: ./clamd -staketo=<addresshere> Yes, or in clam.conf without the hyphen. I use: staketo=xJDCLAMZW9xZEFRfWhxXkcCGYkHAzhsjT5 in clam.conf. If I don't use -staketo where do they end up going? Just to the same address that staked? Thanks. |
|
|
|
Thanks! so for example.. If I have output amounts as piles of 5.. and I set ./clamd -combinelimit=5 (set to 5 or less?) Then it won't combine into larger piles right? ^bump... plus how do I use -staketo just this?: ./clamd -staketo=<addresshere> |
|
|
|
Thanks! so for example.. If I have output amounts as piles of 5.. and I set ./clamd -combinelimit=5 (set to 5 or less?) Then it won't combine into larger piles right? |
|
|
|
They will stake separately, but may be recombined when you stake, depending on your config.
So, how do you set the config so they won't recombine? Thanks. ^bump .. does anyone else happen to know? |
|
|
|
They will stake separately, but may be recombined when you stake, depending on your config.
So, how do you set the config so they won't recombine? Thanks. |
|
|
|
What is the largest amount that is safe to split up using: sendtoaddress theaddressyoursplittingto '{"count":c,"amount":a}'Its fine to do a large amount at one time? Also, those will all stake as separate outputs? Is it better to do this between separate wallet on separate computers? In other words, what if on the same wallet / machine I add more coins at a later date, then I try to do the same thing, will it pull from the other outputs and mess things up? Thanks. |
|
|
|
|
What is USP ? Unique selling point?
|
|
|
|
|
Instead of bickering about the digger, I wish we would focus on the petition system and look forward to what is going to be done *or* options to be voted on / offered available.
My point is the digger happened, get over it. Can we move on?
|
|
|
|
What solutions are currently mainly being considered?
A soft-fork ? What does that all entail?
Does that render all current new clams being staked worthless??
No one has proposed or discussed making CLAMs being staked worthless. Please stop the FUD. I never said it would, I'm asking what will happen.. I thought we were going to be given more info! Please learn the difference between asking questions and making statements. Don't add context to posts or try to look more into it in a negative way - that to me is trollish. Thanks. I don't understand why this was cut out .. I thought we were going to receive more info on this and the petition system a couple days ago? Which is what I mainly want to know. Uggghhhh |
|
|
|
|
What solutions are currently mainly being considered?
A soft-fork ? What does that all entail?
Does that render all current new clams being staked worthless??
I thought we were going to receive more info on this and the petition system a couple days ago?
|
|
|
|
I think the pacing is what would be more important, that said is the Clam Whale almost done digging yet the price is low enough that at this stage a fast dump is a lot better than a slow prolonged one.
He's done digging, apparently. But not done selling. And when you say "better", better for who? It's a zero sum game. Better for the digger means worse for the rest of us, doesn't it? I guess its' all how you look at it, some people are seeing it as a chance to load up on more clam. For every sell there is buys. |
|
|
|
Sorry for the giant post, but there's too much to reply to here...
Making a new coin and leaving CLAM rules unchanged does seem the fairest way to proceed. Then the people who didn't hear about CLAM yet will still have CLAM waiting for them when they finally do hear about it.
Maybe as BAC suggested we should take any discussion of "doogcoin" off this thread, like how discussion of "Bitcoin XT" was moved away from BTC forums - since it really isn't anything to do with CLAM, other than using a snapshot of the CLAM blockchain for its initial distribution.
I took a snapshot of the JD database just as CLAM block 730000 was staked. As the first multiple of 10k after the idea was proposed this seems as good a point as any. Having the snapshot point be in the past prevents any manipulation by people buying CLAM just to increase their initial allocation of "doogcoin". I checked the Poloniex charts and it appears there was no unusual trading before that point.
I know this is kind of off the table for now, I am just curious how quickly you could implement this if you found the need? Hmmm... couldn't large investors / holders (at the time of the snapshot) just dump that new coin down also? I don't see how that's a great solution. |
|
|
|
Not going to list or get in fights about all the things wrong with Java, there is vast amounts of information already available on that.
Regarding the floor, I guess it depends on the rate of dumping by the dumper.
Many other factors to consider as well--- not just a single digger Remember the Millions of coins that have not been claimed yet We could see many more large diggers very soon or down the road. People have to decide if they want to take the risk of supporting future large diggers. Or, what if there isn't really any.. maybe just a bunch of lost forgotten addresses? Could be a very limited supply then, of clam. |
|
|
|
|
Not going to list or get in fights about all the things wrong with Java, there is vast amounts of information already available on that.
Regarding the floor, I guess it depends on the rate of dumping by the dumper.
|
|
|
|
|
Show Posts
