did they only send clams to BTC address that are active(with a balance), and what was the date they did the address lookup on the BTC blockchain?
BTC/LTC and Doge. It was may 12th. I added the given chain heights the snapshots were taken at also. Oh, and all addresses that were above dust for the specific coin were included. Bitcoin
height=300377 date=2014-05-12 12:48:17
Litecoin
height=565693 date=2014-05-12 13:06:31
Dogecoin
height=218556 date=2014-05-12 13:09:17
|
|
|
|
I've got a couple of fixes for the issue of private keys not importing from paper wallets. Hope to have it out after some more testing but so far I've managed to import the keys generated by the digibyte paper wallets.
I've been incredible busy with some personal stuff but was going to fix this tomorrow. I know what the issue is and its a reasonable simple fix. There was a change in the base58 conversion for a private keys at some point in the past and the newer client needs to be able to handle both prefixes. It happened during the rebasing of the codebase to match the current bitcoin code. There were significant changes and this was missed in the re-factoring. |
|
|
|
So basically I have to give up my private keys in order to use CLAM? I haven't quite understood that yet.
Just to be sure you understand. You do NOT have to give up your private keys to USE clams. It's just a regular old alt coin as far as usage goes. You DO have to provide your private keys in order to DIG any clams. This is the processes you use to claim your clams from the initial distribution. Yes, I understood that. The problems remains: private keys have to be used. So, like I mentioned, if you don't trust the client, then the solution is to move your coins to a new address/wallet, and then you can import your private keys from the time of the snapshot and there is nothing to worry about. I myself have been too lazy to do this up to this point, but I'm planning to do it soon. This is the approach we suggest everyone takes to be 100% safe. I didn't do it with my addresses where I wrote the code for this and I'm 100% confident its safe but moving your BTC/LTC or DOGE to a different address before you import takes the risk to 0. |
|
|
|
The new website looks great! What is the status of the wallet for OS X? This reddit post suggests a Mac wallet would be out months ago but I don't see one listed. Is this still on the agenda? Thanks! Getting dooglus to repoen just-dice with CLAMS was a real coup for the coin. Congrats! Tha access to a mac for the dev team has been the issue with the OSX release. None of us are mac users, and given the nature of the coin were not comfortable endorsing a community compiled version. Once the current release is finished, which I'm working very hard on getting ready I had planned on looking at the build system. We use gitian builder to compile the client so to provide a deterministic way that other people can verify nothing fishy is going on. The new build system will allow us to compile the osx client in the same manner, cross compiling through gitian. There is sadly no real ETA, but it is first on my list once the current release is done. |
|
|
|
i use electrum for BTC and therefore have no wallet.dat ...
how can I import my electrum wallet to look for CLAMs ?
Certainly, as long as you can access the private keys you and import into clams. I don't use electrum, but I'll take a look into the process for you. |
|
|
|
So.... it seems the wheel doesn't need to be reinvented here, just needs a spoke repair... anyone know xploited personally that can ask? He hasn't responded to any further e-mails since October.
I had a pretty major surgery recently and took some time off to recover. I'm starting to get back in the swing of things so I'll get the paper wallet issue sorted out. Thanks for reminding me! |
|
|
|
I need some nodes, my win wallet still will not sync after being opened for 6 days!!!
"addr" : "74.207.230.61:31174", "addr" : "76.94.201.185:31174", "addr" : "54.75.227.85:31174", "addr" : "66.30.80.136:31174", "addr" : "73.55.207.245:31174", "addr" : "93.103.131.59:31174", "addr" : "109.195.211.62:31174", "addr" : "80.195.253.183:31174", Thanks, let me fix that for you. :0 addnode=74.207.230.61
addnode=76.94.201.185
addnode=54.75.227.85
addnode=66.30.80.136
addnode=73.55.207.245
addnode=93.103.131.59
addnode=109.195.211.62
addnode=80.195.253.183 Dev please add this to your main page post, it will save a lot of headaches! Yes it will, I'll get SuperClam to put it there ASAP. I'm also updating the node list for the new release which will be along VERY shortly. Theres a bunch of fixes going into this one so want to make sure its perfect. Included updates to the networking itself |
|
|
|
I have noticed that none of my stacks has staked for quite a while now.
Anyone else having that problem ?
Are you seeing them staking but then getting orphaned? Or just not staking at all? If the former, sync your system clock then restart the wallet. If the latter, it may just be a sign that the difficulty has increased. I estimate that you need about 150 CLAMs now if you want to stake once per day on average. I made some charts showing how difficulty has risen over time: This one shows the whole history since block 0. The recent hardfork made it about 100 million times easier to stake a block, so the difficulty shot up to compensate: This one shows the difficulty since the recent hardfork: Not staking at all, still have small stacks of some 5-6 clams. I guess I better create 1 stack and sacrifice coin age. Also I have noticed that often clam wallet show high cpu load. Especially compared to other wallets. CoinAge is not taken into account when your staking. So, feel free to sacrifice it! |
|
|
|
Thats awesome! Thanks for the kind words. I know I surely agree, Clams are cool  Long live the great Clam!! |
|
|
|
|
Block explorer is currently undergoing some maint. It will be back up shortly for anyone who noticied its down
EDIT: Its back up
|
|
|
|
|
Block explorer is back up and running!!!!!
|
|
|
|
|
Blockexplorer is currently rebuilding its database.
I've worked out all the kinks, just need it to complete the resync and it will be back online
About 1-2 hours
|
|
|
|
I'm working on Abe sense no one has seems to be able to get it running. No, there is no others. Clams has a few things that make block explorer adaption difficult. if its not up soon I'll put rpcace back online |
|
|
|
To end any discussion that will likely come of it. No, you cannot redeem coin held on Cryptsy as per our ToS. We do not honor snapshots, or anything that involves the private keys etc associated to our wallets.
Everyone is welcome to withdraw coin to their own personal wallets if they wish to take advantage. I see more and more of these types of coins popping up and it is not a practice we will be participating in even if we list the coin.
While I total understand your position I would argue that what Poloniex did was absolutely no security risk and very community friendly. Aka they claimed there wallets (although they didn't have a lot as they had reset there wallet system recently before the snapshot) and then gave them away in a giveaway to there users. Of course a user withdrawing their coins to there own personal wallet at this point would have no effect in claiming clams they might have gotten from coins in cryptsy systems. There yours now as you own the private keys those outputs belong to. Sending them out of your system would have no effect whatsoever. |
|
|
|
Please ensure that you are building the correct version of the CLAMclient and have a working block chain for your services. The block data appears to be incorrect on the explorer linked. Dice and faucet are updated correctly. The explorer though is having issues. I can likely help you with the changes, I'm just not sure how to implement them myself. I know what needs to be changed for it to work. You can catch me on our irc channel, I'm always there. I would love to help you get it running correctly! |
|
|
|
Not that we don't appreciate the services (cause we do!) but your block explorer doesn't work correctly. Porting our coin to ABE has proved to be quite the challenge due to our last fork. I don't have the necessary python skills to do what I need to. Annoyingly I know exactly what needs to be done, just unsure how to do it in the mess known as Abe. The problem is we switched to sha256 block hashing in the new fork for performance reasons but ABE alloys no easy way to switch the way it parses the headers for a chain. I have the current code updates I've made if anyone wants to take a shot. It almost works but after 203500 it parses the block headers incorrectly you can reach me on our IRC channel |
|
|
|
I've just downloaded 2 separate CLAMS Windows clients from 2 different Official links, both stated they are CLAMS 1.4.3.0 but when I look inside the wallet it shows v1.4.2.1 is there something I'm missing or did the Dev just not update that part ?
My client says 1.4.2.1 in the Help->About CLAM dialog too, and I know I'm running 1.4.3.0. I don't know where it gets that version string from. It depends on how its built. The version string can be pulled from git, and a few other places. It will be updated in the next client release which should be tomorrow. The version slipped through the crack on the most recent update. |
|
|
|
im trying to unlock my wallet I got this message "

Error: RPC server was not started, use server=1 to change this. (code -18)
RPC is getting separated from the wallet (code wise). You can choose not to activate it if you don't need to. If you add server=1 to the clam.conf file the RPC will work. |
|
|
|
how to fix: ./miraclecoin-qt: error while loading shared libraries: libdb_cxx-5.1.so: cannot open shared object file: No such file or directory
 Without any more details, I would suggest sudo apt-get install libdb5.1++ libboost-all-dev
Thanks, this ran into more. I just made a windows VM. yeah, I was going to say, that was not a sure fire fix. Would depend on your distro and version, what deps you already have installed etc Glad you got it working |
|
|
|
|
Show Posts
