Update:
1 2013-11-30 1132.29
2 2013-12-04 1111.56
3 2017-01-04 1088.45
4 2013-11-29 1065.36
5 2013-12-03 1050.57
6 2017-01-03 1020.56
7 2017-01-02 1013.00
8 2017-01-05 1005.35
9 2013-12-02 1000.49
10 2013-11-28 998.56
11 2017-01-01 987.47
12 2013-12-05 975.06
13 2016-12-29 967.02
14 2016-12-28 955.98
15 2016-12-31 955.73
16 2016-12-30 951.07
17 2013-12-01 945.67
18 2013-12-10 941.56
19 2013-11-27 937.09
20 2014-01-06 936.62
21 2016-12-27 922.42
22 2017-01-06 914.26
23 2017-01-08 913.92
24 2017-01-10 902.61
25 2016-12-24 900.20
26 2016-12-26 898.97
27 2016-12-23 897.77
28 2017-01-19 895.00
29 2013-12-06 894.36
30 2017-01-09 892.60
|
|
|
|
Update:
1 2013-11-30 1132.29
2 2013-12-04 1111.56
3 2017-01-04 1088.45
4 2013-11-29 1065.36
5 2013-12-03 1050.57
6 2017-01-03 1020.56
7 2017-01-02 1013.00
8 2017-01-05 1005.35
9 2013-12-02 1000.49
10 2013-11-28 998.56
11 2017-01-01 987.47
12 2013-12-05 975.06
13 2016-12-29 967.02
14 2016-12-28 955.98
15 2016-12-31 955.73
16 2016-12-30 951.07
17 2013-12-01 945.67
18 2013-12-10 941.56
19 2013-11-27 937.09
20 2014-01-06 936.62
21 2016-12-27 922.42
22 2017-01-06 914.26
23 2017-01-08 913.92
24 2017-01-10 902.61
25 2016-12-24 900.20
26 2016-12-26 898.97
27 2016-12-23 897.77
28 2013-12-06 894.36
29 2017-01-09 892.60
30 2013-12-11 890.42
31 2014-01-11 883.00
32 2013-12-13 882.99
33 2014-01-05 881.82
34 2017-01-18 879.11
35 2017-01-17 878.62
|
|
|
|
Earlier today I somehow managed to corrupt a wallet.dat file that had 10k CLAMs in it. $ clamd
Clam server starting
Error: wallet.dat corrupt, salvage failed
$
All attempts at salvaging the private key failed until I remembered this old post: I looked for 'undelete' programs, but didn't find anything that looked useful. I found this thread, but the git repository seems to have died. So I wrote my own simple "privkey finder":
It turns out the code in that thread worked as-is on the CLAM wallet, and provided the private key I needed to recover the 10k CLAMs. It spat out the privkey in hex format. I then used http://clamaddress.org/ to convert it to the WIF format that 'importprivkey' accepts. Phew! |
|
|
|
My wallet has been syncing for a week now and I am still 8 weeks out. I used the bootstrap and it is still taking forever any suggestions?
I will create a boostrap, put it in a password protected tarball and upload it to mega. Bear in mind, I will share a secret passphrase only with myself. I will be the only one who will be able to bootstrap a chain. I will laugh hard at ur attempts to guess a password to that archive. Plain text bootstraps are available. You can publish your encrypted copy if you like but why would anyone care? |
|
|
|
My wallet has been syncing for a week now and I am still 8 weeks out. I used the bootstrap and it is still taking forever any suggestions?
Is it still using the bootstrap file? |
|
|
|
Update:
1 2013-11-30 1132.29
2 2013-12-04 1111.56
3 2017-01-04 1088.45
4 2013-11-29 1065.36
5 2013-12-03 1050.57
6 2017-01-03 1020.56
7 2017-01-02 1013.00
8 2017-01-05 1005.35
9 2013-12-02 1000.49
10 2013-11-28 998.56
11 2017-01-01 987.47
12 2013-12-05 975.06
13 2016-12-29 967.02
14 2016-12-28 955.98
15 2016-12-31 955.73
16 2016-12-30 951.07
17 2013-12-01 945.67
18 2013-12-10 941.56
19 2013-11-27 937.09
20 2014-01-06 936.62
21 2016-12-27 922.42
22 2017-01-06 914.26
23 2017-01-08 913.92
24 2017-01-10 902.61
25 2016-12-24 900.20
26 2016-12-26 898.97
27 2016-12-23 897.77
28 2013-12-06 894.36
29 2017-01-09 892.60
30 2013-12-11 890.42
31 2014-01-11 883.00
32 2013-12-13 882.99
33 2014-01-05 881.82
34 2017-01-17 878.62
35 2016-12-25 874.03
|
|
|
|
Update (I had to go down to 48th place to get yesterday's price on the list):
1 2013-11-30 1132.29
2 2013-12-04 1111.56
3 2017-01-04 1088.45
4 2013-11-29 1065.36
5 2013-12-03 1050.57
6 2017-01-03 1020.56
7 2017-01-02 1013.00
8 2017-01-05 1005.35
9 2013-12-02 1000.49
10 2013-11-28 998.56
11 2017-01-01 987.47
12 2013-12-05 975.06
13 2016-12-29 967.02
14 2016-12-28 955.98
15 2016-12-31 955.73
16 2016-12-30 951.07
17 2013-12-01 945.67
18 2013-12-10 941.56
19 2013-11-27 937.09
20 2014-01-06 936.62
21 2016-12-27 922.42
22 2017-01-06 914.26
23 2017-01-08 913.92
24 2017-01-10 902.61
25 2016-12-24 900.20
26 2016-12-26 898.97
27 2016-12-23 897.77
28 2013-12-06 894.36
29 2017-01-09 892.60
30 2013-12-11 890.42
31 2014-01-11 883.00
32 2013-12-13 882.99
33 2014-01-05 881.82
34 2016-12-25 874.03
35 2013-12-09 867.49
36 2017-01-07 863.89
37 2013-12-12 862.85
38 2013-12-14 860.41
39 2014-01-12 858.24
40 2014-01-07 857.96
41 2016-12-22 855.94
42 2013-11-26 849.32
43 2013-12-15 838.37
44 2014-01-15 837.66
45 2013-11-23 832.85
46 2014-01-20 831.00
47 2014-01-10 829.44
48 2017-01-16 828.25
49 2014-01-16 828.18
50 2017-01-14 826.98
Check out 48th and 49th places - the price moved 7 cents in 3 years, and people say Bitcoin is volatile!  |
|
|
|
Hey guys. I just posted a suggestion on freewallet.org for the developer to integrate CLAM into their wallet service. I think this would be excellent for the CLAM comunity as we are in need of a mobile wallet, and it also would spread awareness about the CLAM project. Please for "CLAM Wallet" at: https://freewallet.org/voteA couple of things: 1) I read here that freewallet.org holds user private keys, so you have to trust them not to exit-scam. I'm not sure that's a good idea. Most wallets let the user have exclusive control of their own private keys. 2) I don't see any way of voting on the page you linked to. Do I need to make an account or something first? Edit: oh, it was because I had javascript disabled. Never mind... |
|
|
|
Noob question: with 10 CLAM how long am I supposed to wait (on average) to stake anything?
If you run "getstakinginfo" in the client's debug window it will show you something like this: $ clamd getstakinginfo
{
"enabled" : true,
"staking" : true,
"errors" : "",
"currentblocksize" : 1000,
"currentblocktx" : 0,
"pooledtx" : 0,
"difficulty" : 139725.8096014384,
"search-interval" : 16,
"weight" : 21368.11582037,
"netstakeweight" : 1508267.639858975,
"expectedtime" : 4508
} The 'weight' is the number of CLAMs your wallet is staking. The 'expectedtime' is the expected number of seconds until your next stake. The above wallet has 21k CLAMs and should stake every 4.5k seconds. Extrapolating from that, 10 CLAMs should stake every 4.5k * 21k / 10 = 9450000 seconds = 109 days. A general rule of thumb is that you need around 1000 CLAMs to stake once per day, so it makes sense that if you have 100 times less than 1000 CLAMs it will take 100 times more than 1 day. Also, that 1000 CLAMs number is probably out of date now. It goes up as more CLAMs are staked. |
|
|
|
Additionally, last I knew, the Just-Dice trollbox was posting random chat-lines as well.
It still does that. The only warning I would personally offer would be that eventually, in order to prevent spam, transaction fees are likely to be handled differently in the future.
It's interesting that you say that. I was thinking about fees recently when I noticed that the Just-Dice hot wallet was full of tiny unspent outputs, and that the wallet server was pegged at 100% disk write. It seems the faucet testing referred to here is responsible for most of the dust I'm seeing: Looking for more CLAM faucet testers for FreeBitcoins.com
It seems the faucet is mostly sending outputs of 0.0001 CLAMs, worth roughly a hundredth of a US cent each. I was wondering how best to deal with it. It costs more to spend than it is worth, and so the logical response is to never spend it, and to set a minimum deposit amount. Any deposit less than the minimum would be considered a donation. I ended up changing the hot wallet client code such that it never spends the dust outputs, but instead merges them whenever the wallet stakes. That is free to do, and so the cost of handling the dust is passed on to all the full nodes in terms of bandwidth and storage, but at least the UTXO set isn't being polluted. Here's an example of a staking transaction tidying up a bunch of faucet dust. [Edit: another example, this time from an old hot wallet that is no longer staking; people apparently set an address in the faucet then forget about it, causing an endless torrent of blockchain spam for others to clean up] I spoke to Kef about the dust from the faucet. I recognize that it makes no sense to ask people to stop spamming the blockchain. Maybe Kef/BAC would comply, but the next guy might not. We can't trust that CLAM users are going to be responsible. Better to limit the "damage" they can do, if such limiting is needed. Currently I'm not sure it is. Individual recipients of the dust can refuse to honor the tiny deposits if they don't want to deal with it, and maybe that's enough. If there ended up being enough dust that the blocks fill up a fee market will presumably develop, as it did in Bitcoin. Personally I wasn't going to even bring the subject up, other than asking Kef if he can aggregate users payings into larger amounts and set a minimum withdrawal amount for the site. But since both the faucet and the subject of fees preventing spam both came up in this thread recently I figured I would mention it. Edit: I should probably be clear that I have no problem with the faucet site. It's just that a lot of its outputs end up at Just-Dice, and they had been causing technical trouble until I found a way of dealing with them. They'll still be bloating the chain and the Just-Dice hot wallet, but not the UTXO set any more. |
|
|
|
I was wondering if you could post an updated version of the bootstrap. The one linked above is 2 years old.
Check it again: I made an updated bootstrap.dat file for people having trouble syncing their client.
It goes up to block 1326600 which was staked on Thu Jan 5 18:38:24 UTC 2017.
That's just 3 days ago. |
|
|
|
Q. there is no way to predict when a whale will appear and create a massive dump?
A. true
Q. You know that during a big dump money always goes from the small fishes to the whales?
A. true
A. So don't risk your money when it can disappear due to one whale dumping on BTC.
Keep your money safe away from the bitcoin sharks.
Username checks out. |
|
|
|
I was asking how to generate the private key (xpriv) from the word sequence so I could import it. The link dooglus posted will do it, and so will https://bip32jp.github.io/english/Then you would have to generate a qr code from the text string that is the xpriv key. But I haven't done that, because it's a lot of steps, poses risks and it's inconvenient. The BIP39 tool will generate the QR code for any field you click on. So it's as simple as opening the page on an offline machine, entering your 12 word seed, entering the "Account" number on the BIP44 tab, and clicking on the "Account Extended Private Key" in the BIP44 tab to display its QR code. |
|
|
|
I recently received a query from a guy who has a bunch of old redeemed Casascius coins (physical Bitcoin). He was asking how to claim the CLAMs associated with them. Casascius coins have their private key hidden beneath a tamper-evident hologram, in " mini format". In response to his query I updated Just-Dice.com so that it will now recognize and accept private keys in mini format. Just do this in the chat: /dig <address> <mini-key> And the site will dig up the CLAMs and credit them to your account after 6 confirmations. Make sure the coins have already been redeemed. Just-Dice will use your private key and immediately forget it, but in the event that your BTC are somehow stolen I would rather not be a suspect. So empty the address before telling anyone your private key. |
|
|
|
For those in east coast, how do you deal with this volatility during the early hours of the morning???
Turn the phone to 'silent' mode and get a good night's sleep. As the old saying goes, if you can't stand the Bitcoin-heat stay out of the Bitcoin-kitchen.  |
|
|
|
The "classic" one had days older than 7 (or 10) fade from black to light grey, but still be thick type. After another 7 (or 10) days the text for that date was presented in ordinary type. So 4 categories in total: today, last week (or 10 days), last 2 weeks (or 20 days), and older.
Could you quote an example of this please? It looks to me like he was just showing positions 11 through 20 in a faded out color, like this: 9. 2013-02-16 W. Avg: 27.16
10. 2013-02-15 W. Avg: 26.99
11. 2013-02-18 W. Avg: 26.76
12. 2013-02-17 W. Avg: 26.40
Note how #11 is newer than #10, but is faded out because it's not in the top 10. |
|
|
|
Update - despite the sub $900 drop today the volume weighted average price stayed just over $1000:
1 2013-11-30 1132.29
2 2013-12-04 1111.56
3 2017-01-04 1088.45
4 2013-11-29 1065.36
5 2013-12-03 1050.57
6 2017-01-03 1020.56
7 2017-01-02 1013.00
8 2017-01-05 1005.35
9 2013-12-02 1000.49
10 2013-11-28 998.56
11 2017-01-01 987.47
12 2013-12-05 975.06
13 2016-12-29 967.02
14 2016-12-28 955.98
15 2016-12-31 955.73
16 2016-12-30 951.07
17 2013-12-01 945.67
18 2013-12-10 941.56
19 2013-11-27 937.09
20 2014-01-06 936.62
|
|
|
|
darn, i am downloading now the core , did i need this to download this core  it paste 4 hours and still i am a year and half behind , at this rate its gonna take few days ( i think) You don't need to download the blockchain past the first 10k blocks, but if you do want it, see my bootstrap.dat post for a link to a copy of the full blockchain. It will be faster to download it from there. |
|
|
|
Very cool. Was thinking it might be nice to have different years have diff color font to help visualisation a little bit.. But anyway interesting way to look at the price. Thanks
Well, we really only have two "years": late 2013, early 2014, and late 2016, early 2017... |
|
|
|
|
Show Posts
