No really... without digging clams will lose ALOT of his charme. And i think it will go down pretty fast then too.
How can you say that after 2 years!? The only reason why CLAM is still alive and kicking is Just-Dice. You can't be that blind. I don't have a problem with digging but that award (4.6) need to be smaller with time. 
Topic: [ANN][CLAM] CLAMs, Proof-Of-Chain, Proof-Of-Working-Stake, a.k.a. "Clamcoin" - page 175. (Read 1151252 times)
February 15, 2016, 09:30:20 AM
February 15, 2016, 06:14:56 AM
I think that Doog and friends bought far to much CLAMs on 0.0009 so we can't expect price increase. Beside that we have big inflation and constant threat of new digger. On the other fronts Just-Dice seems can't attract new users. CLAM is simple not attractive to them any more. You can lose twice on dice game and decreasing CLAMs with no volume.
Two years should be enough for everyone who wanted to sign up for CLAMs to do so. After that date new CLAMs rewards for every BTC, DOGE, LTC address should be drastically reduced or abolished.
Two years should be enough for everyone who wanted to sign up for CLAMs to do so. After that date new CLAMs rewards for every BTC, DOGE, LTC address should be drastically reduced or abolished.
Digging IS the single most effective way to get more clamusers. And in fact I believe these guys will most probably check out justdice and even buy some more clams. Iam, for example, was buying a lot more clams after i found i could dig some coins. So digging is essential to the clam network, in my opinion. Of course potential digs are less the more time goes by. Maybe a bit advertising about the possibility to dig would help to get more digging and Iam pretty sure it will help the price going up too.
Honestly, i think without digging clam will die relatively fast. There simply is no new fresh energy flowing in anymore then. Where should it come from than from people being excited about the possibility to earn free money and check out clams? I mean checking out a new altcoin is pretty time consuming. When you have an reward to do so then wou might do it. If there is no reward at all then why should someone seeing clam from the outside have an interest into checking it out? Because of just-dice? Well, why think about exchanging your bitcoins into a potential risky altcoin when you simply can play on primedice?
No really... without digging clams will lose ALOT of his charme. And i think it will go down pretty fast then too.
February 15, 2016, 06:08:44 AM
If you own CLAM, you can express that opinion via CLAMour.
I notice you have been expressing it in trollboxes as well.
Yes I did. I'm also voted for stop digging.
Experiment with fair distribution is obviously failed after last digger. Why we need to wait for another one? What's the point anyway?
February 15, 2016, 04:21:30 AM
If you own CLAM, you can express that opinion via CLAMour.
I notice you have been expressing it in trollboxes as well.
Yes I did. I'm also voted for stop digging.
Experiment with fair distribution is obviously failed after last digger. Why we need to wait for another one? What's the point anyway?
February 15, 2016, 04:08:54 AM
I think that Doog and friends bought far to much CLAMs on 0.0009 so we can't expect price increase. Beside that we have big inflation and constant threat of new digger. On the other fronts Just-Dice seems can't attract new users. CLAM is simple not attractive to them any more. You can lose twice on dice game and decreasing CLAMs with no volume.
Two years should be enough for everyone who wanted to sign up for CLAMs to do so. After that date new CLAMs rewards for every BTC, DOGE, LTC address should be drastically reduced or abolished.
Two years should be enough for everyone who wanted to sign up for CLAMs to do so. After that date new CLAMs rewards for every BTC, DOGE, LTC address should be drastically reduced or abolished.
If you own CLAM, you can express that opinion via CLAMour.
I notice you have been expressing it in trollboxes as well.
February 15, 2016, 04:00:25 AM
I think that Doog and friends bought far to much CLAMs on 0.0009 so we can't expect price increase. Beside that we have big inflation and constant threat of new digger. On the other fronts Just-Dice seems can't attract new users. CLAM is simple not attractive to them any more. You can lose twice on dice game and decreasing CLAMs with no volume.
Two years should be enough for everyone who wanted to sign up for CLAMs to do so. After that date new CLAMs rewards for every BTC, DOGE, LTC address should be drastically reduced or abolished.
Two years should be enough for everyone who wanted to sign up for CLAMs to do so. After that date new CLAMs rewards for every BTC, DOGE, LTC address should be drastically reduced or abolished.
February 14, 2016, 02:25:37 AM
Downloaded bootstrap.dat, synced from HD, restarted clam-qt and the last 20 or so weeks are syncing now from the network.
Only weird things is, when I want to start clam-qt from the GUI it won't start, only by using Terminal window and then run command ./clam-qt
Only weird things is, when I want to start clam-qt from the GUI it won't start, only by using Terminal window and then run command ./clam-qt
If you're using my bootstrap.dat it's almost always less than 2 weeks out date. I think currently it's only around 4 days old, so it's odd that you're having to sync 20 weeks' worth from the network. I keep the post up to date with the number of blocks it contains, the date of that block, and the checksum of the bootstrap file each time I update the file itself.
I don't know what to tell you about it not starting from the GUI. Which desktop environment are you using?
I run Ubunutu 14.04 LTS. like Ketkius mentioned, I didn't run MAKE INSTALL, so I did run SUDO MAKE INSTALL and started clam-qt from /usr/local/bin but that works only from the terminal console. So I copied these files to a directory in my Home bit same thing. I get this message when I try to start it from the GUI : There is no application installed for “shared library” files.
February 13, 2016, 07:09:28 PM
Downloaded bootstrap.dat, synced from HD, restarted clam-qt and the last 20 or so weeks are syncing now from the network.
Only weird things is, when I want to start clam-qt from the GUI it won't start, only by using Terminal window and then run command ./clam-qt
Only weird things is, when I want to start clam-qt from the GUI it won't start, only by using Terminal window and then run command ./clam-qt
If you're using my bootstrap.dat it's almost always less than 2 weeks out date. I think currently it's only around 4 days old, so it's odd that you're having to sync 20 weeks' worth from the network. I keep the post up to date with the number of blocks it contains, the date of that block, and the checksum of the bootstrap file each time I update the file itself.
I don't know what to tell you about it not starting from the GUI. Which desktop environment are you using?
February 13, 2016, 04:20:17 PM
But when I start ./clam-qt I get this error: error initializing wallet database enviroment /home/username/.clam!
Do you have an existing wallet.dat in that folder, created using an incompatible version of the Berkeley DB? That's what it looks like to me.
Try renaming wallet.dat and trying again. It should make a new one. Use your old client to move any coins from the old wallet to an address in the new one.
I deleted all CLAM things. run sudo app-get update and reinstalled Libtool stuff.
Downloaded everything CLAM again, started form scrtach and it works now.
Downloaded bootstrap.dat, synced from HD, restarted clam-qt and the last 20 or so weeks are syncing now from the network.
Only weird things is, when I want to start clam-qt from the GUI it won't start, only by using Terminal window and then run command ./clam-qt
Does it work to run 'clam-qt' from the terminal when not in the directory that clam-qt is in? You may have forgotten to run 'sudo make install'. I'm not sure what lengths you went to to delete all CLAM things, but there could be an invalid symlink or some such.
February 13, 2016, 03:34:27 PM
But when I start ./clam-qt I get this error: error initializing wallet database enviroment /home/username/.clam!
Do you have an existing wallet.dat in that folder, created using an incompatible version of the Berkeley DB? That's what it looks like to me.
Try renaming wallet.dat and trying again. It should make a new one. Use your old client to move any coins from the old wallet to an address in the new one.
I deleted all CLAM things. run sudo app-get update and reinstalled Libtool stuff.
Downloaded everything CLAM again, started form scrtach and it works now.
Downloaded bootstrap.dat, synced from HD, restarted clam-qt and the last 20 or so weeks are syncing now from the network.
Only weird things is, when I want to start clam-qt from the GUI it won't start, only by using Terminal window and then run command ./clam-qt
February 13, 2016, 11:54:45 AM
But when I start ./clam-qt I get this error: error initializing wallet database enviroment /home/username/.clam!
Do you have an existing wallet.dat in that folder, created using an incompatible version of the Berkeley DB? That's what it looks like to me.
Try renaming wallet.dat and trying again. It should make a new one. Use your old client to move any coins from the old wallet to an address in the new one.
February 12, 2016, 04:13:46 PM
I am trying to build Clam-qt on a (virtual) Linux 14.04 LTS 64 bit. Installed all dependencies but when I run ./automake I get this error:
what am I doing wrong?
Code:
Makefile.am:5: warning: user variable 'GZIP_ENV' defined here ...
/usr/share/automake-1.14/am/distdir.am: ... overrides Automake variable 'GZIP_ENV' defined here
Makefile.am:46: warning: user target 'distcleancheck' defined here ...
/usr/share/automake-1.14/am/distdir.am: ... overrides Automake target 'distcleancheck' defined here
src/Makefile.am:221: warning: user target '.mm.o' defined here ...
/usr/share/automake-1.14/am/depend2.am: ... overrides Automake target '.mm.o' defined here
/usr/share/automake-1.14/am/distdir.am: ... overrides Automake variable 'GZIP_ENV' defined here
Makefile.am:46: warning: user target 'distcleancheck' defined here ...
/usr/share/automake-1.14/am/distdir.am: ... overrides Automake target 'distcleancheck' defined here
src/Makefile.am:221: warning: user target '.mm.o' defined here ...
/usr/share/automake-1.14/am/depend2.am: ... overrides Automake target '.mm.o' defined here
what am I doing wrong?
It looks like those are only warnings. It's letting you know that it's messinga round with some of your environment (GZIP_ENV) and makefile targets. If you run ./configure && make after this, does it actually error?
Yes I got an error running ./configure but after taking a close look it had to do with Berkely DB 4.8.... then I ran: ./configure --with-incompatible-bdb && make and that went OK.
You are right, the ./autogen.sh "errors" were just warnings.
But when I start ./clam-qt I get this error: error initializing wallet database enviroment /home/username/.clam!
February 12, 2016, 03:16:29 PM
278,000 clam profit now. impressive. clamdoge lost big the other night.
running out of whales....feels like were in Japan
running out of whales....feels like were in Japan
February 12, 2016, 02:48:30 PM
I am trying to build Clam-qt on a (virtual) Linux 14.04 LTS 64 bit. Installed all dependencies but when I run ./automake I get this error:
what am I doing wrong?
Code:
Makefile.am:5: warning: user variable 'GZIP_ENV' defined here ...
/usr/share/automake-1.14/am/distdir.am: ... overrides Automake variable 'GZIP_ENV' defined here
Makefile.am:46: warning: user target 'distcleancheck' defined here ...
/usr/share/automake-1.14/am/distdir.am: ... overrides Automake target 'distcleancheck' defined here
src/Makefile.am:221: warning: user target '.mm.o' defined here ...
/usr/share/automake-1.14/am/depend2.am: ... overrides Automake target '.mm.o' defined here
/usr/share/automake-1.14/am/distdir.am: ... overrides Automake variable 'GZIP_ENV' defined here
Makefile.am:46: warning: user target 'distcleancheck' defined here ...
/usr/share/automake-1.14/am/distdir.am: ... overrides Automake target 'distcleancheck' defined here
src/Makefile.am:221: warning: user target '.mm.o' defined here ...
/usr/share/automake-1.14/am/depend2.am: ... overrides Automake target '.mm.o' defined here
what am I doing wrong?
It looks like those are only warnings. It's letting you know that it's messinga round with some of your environment (GZIP_ENV) and makefile targets. If you run ./configure && make after this, does it actually error?
February 12, 2016, 08:03:15 AM
I am trying to build Clam-qt on a (virtual) Linux 14.04 LTS 64 bit. Installed all dependencies but when I run ./automake I get this error:
what am I doing wrong?
Code:
Makefile.am:5: warning: user variable 'GZIP_ENV' defined here ...
/usr/share/automake-1.14/am/distdir.am: ... overrides Automake variable 'GZIP_ENV' defined here
Makefile.am:46: warning: user target 'distcleancheck' defined here ...
/usr/share/automake-1.14/am/distdir.am: ... overrides Automake target 'distcleancheck' defined here
src/Makefile.am:221: warning: user target '.mm.o' defined here ...
/usr/share/automake-1.14/am/depend2.am: ... overrides Automake target '.mm.o' defined here
/usr/share/automake-1.14/am/distdir.am: ... overrides Automake variable 'GZIP_ENV' defined here
Makefile.am:46: warning: user target 'distcleancheck' defined here ...
/usr/share/automake-1.14/am/distdir.am: ... overrides Automake target 'distcleancheck' defined here
src/Makefile.am:221: warning: user target '.mm.o' defined here ...
/usr/share/automake-1.14/am/depend2.am: ... overrides Automake target '.mm.o' defined here
what am I doing wrong?
February 11, 2016, 11:55:54 AM
Thanks for the help. It is importing now and that should get me going. I appreciate the help.
February 11, 2016, 08:22:38 AM
I was not sure if that was the latest or not. The version I have is having trouble syncing. I have to continually close it out and restart to get it to progress.
Dooglus made a bootstrap that he updstes from time to time its here: https://bitcointalksearch.org/topic/m.9772191 February 11, 2016, 08:10:16 AM
I was not sure if that was the latest or not. The version I have is having trouble syncing. I have to continually close it out and restart to get it to progress.
February 11, 2016, 01:33:01 AM
what is the latest windows wallet version and where is the download?
Maybe you should just check the beginning of the thread. February 10, 2016, 07:49:50 PM
what is the latest windows wallet version and where is the download?
Jump to: