[ANN][CLAM] CLAMs, Proof-Of-Chain, Proof-Of-Working-Stake, a.k.a. "Clamcoin"

[dooglus]

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

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?

[wttbs]

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

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.

[kunac]

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.

[SuperClam]

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.

If you own CLAM, you can express that opinion via CLAMour. 
I notice you have been expressing it in trollboxes as well.

[kunac]

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?

[andulolika]

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?

The point is that if everyone wanted the digging out it would be out already, not even 50% of the network agrees with it yet. They holders and they know what it means.

[SebastianJu]

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.

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.

[kunac]

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.

[andulolika]

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.

Yes yes we all know how big role JD implies but dont forget that only 50% of the bankroll is being offsited,  if you count the clams out of jd id say there is more people staking. And if you want to end up digging/lower it why dont you make a clamour and start promoting it, hell you can even find someone to promote it for you.
My auto-mouthfuck dog had a decent share in my opinion for a while. If a dog fucking his own mouth can do it you can too.

[Faust Roland]

Hi, is possible to stake with coins on multisignature address where you have only 1 key in the wallet?

I suppose no, but this feature would help create trustless staking pools.

Imagine 1-of-2 address, where 1 key can sign only stake transactions, while the other can withdraw them.
Pool would have the staking key and user would have the spending key.

But, just thinking aloud...

[dooglus]

Hi, is possible to stake with coins on multisignature address where you have only 1 key in the wallet?

I suppose no, but this feature would help create trustless staking pools.

Imagine 1-of-2 address, where 1 key can sign only stake transactions, while the other can withdraw them.
Pool would have the staking key and user would have the spending key.

But, just thinking aloud...

I've read threads on the peercoin forum where they talk about this. I don't think it's possible as things currently stand, but it could be added if there's support for it.

[marilyn4325]

Is it possible to use UTF8 for CLAM speech? I tried the sendtoaddress command (after fixing clamd, pull request issued) on an UTF8 terminal, so clamd should get the UTF8 string. I used this string as the CLAM speech parameter "test2 äöü 象形字", transaction: 2e7d31559f88322bbd66ea361f312c695fb62984ae133b7661cd21dcb2110366. I don't know if the UTF8 characters made it into the transaction, looks like khashier.com doesn't show it, but it looks like the typical 2 bytes UTF8 chars.
Update: khashier supports already UTF8, test with the text 嗨!: http://khashier.com/tx/e4d5c2f48e8da1c0ed800edf87281dddb9b8d1c5e612e18b173015c7946707b0
Looks like some kind of command line encoding problem on my Linux machine or in the clamd command line program.

[tspacepilot]

Is it possible to use UTF8 for CLAM speech? I tried the sendtoaddress command (after fixing clamd, pull request issued) on an UTF8 terminal, so clamd should get the UTF8 string. I used this string as the CLAM speech parameter "test2 äöü 象形字", transaction: 2e7d31559f88322bbd66ea361f312c695fb62984ae133b7661cd21dcb2110366. I don't know if the UTF8 characters made it into the transaction, looks like khashier.com doesn't show it, but it looks like the typical 2 bytes UTF8 chars.
Update: khashier supports already UTF8, test with the text 嗨!: http://khashier.com/tx/e4d5c2f48e8da1c0ed800edf87281dddb9b8d1c5e612e18b173015c7946707b0
Looks like some kind of command line encoding problem on my Linux machine or in the clamd command line program.

Not sure if its applicable, but is it possible to give a file as an arg for you clamd clamspeech?  If so, that might avoid any tinkering by the shell/locale.

[marilyn4325]

Not sure if its applicable, but is it possible to give a file as an arg for you clamd clamspeech?  If so, that might avoid any tinkering by the shell/locale.

No, this is not implemented.

I debugged it a bit more and this is what I found so far: When using a terminal with UTF8 (e.g. echo $LANG = en_US.UTF-8) and calling the clamd client, the UTF8 string is encoded as \u strings. If I use "ä" (UTF8 sequence 0xc3 0xa4), then I can see the ASCII text "\u00c3\u00a4" in the RPC request string. Now I think the problem is that in univalue_read.cpp, the function getJsonToken does some strange looking codepoint conversion which I don't understand. But looks like it expects UTF16 (already too late and some beers).

If it converts it back to UTF8, then one possible solution would be to detect if the terminal is in UTF8 mode for the client, and then converting the UTF8 characters to UTF16 for the RPC call. Shouldn't be too difficult, just the inverse code of what you have in getJsonToken. If someone wants to do it, write here, otherwise I'll try it tomorrow.

[marilyn4325]

I found a solution. Now I can send this string "test äöüß 嗨" and khashier shows it:
http://khashier.com/tx/3b0fd2ecba309e4d5f24b007d9972f2841f4d36aa7a613561be5b648dcffc198
I created a pull-request where we can discuss it, if it is not good.

[cryptospout]

Need some clams?


https://cryptospout.com/offer_wall/clam_offer_wall.html

[dooglus]

Need some clams?

You missed an R in EARNING.

[cryptospout]

Today I fucked up by buying an image off Fiverr

[marilyn4325]

Today I fucked up by buying an image off Fiverr

Fiverr is terrible. You need to have really good luck to find a good designer. Once I tried it for a logo and they just stole an image with minimal modifications (adding text with a standard font), which one of my customers noted. I asked the original author of the image and he didn't know about it and gave no permission. Never again. Now I use always http://en.99designs.de . It's the best for custom logos, graphics and websites. More expensive, but original and you get multiple drafts from different professional artists.

[Kefkius]

Is it possible to use UTF8 for CLAM speech? I tried the sendtoaddress command (after fixing clamd, pull request issued) on an UTF8 terminal, so clamd should get the UTF8 string. I used this string as the CLAM speech parameter "test2 äöü 象形字", transaction: 2e7d31559f88322bbd66ea361f312c695fb62984ae133b7661cd21dcb2110366. I don't know if the UTF8 characters made it into the transaction, looks like khashier.com doesn't show it, but it looks like the typical 2 bytes UTF8 chars.
Update: khashier supports already UTF8, test with the text 嗨!: http://khashier.com/tx/e4d5c2f48e8da1c0ed800edf87281dddb9b8d1c5e612e18b173015c7946707b0
Looks like some kind of command line encoding problem on my Linux machine or in the clamd command line program.

Isn't it technically possible to use any character encoding in clamspeech? Whether or not UTF8 is supported seems to be an issue for whatever is parsing/presenting the clamspeech. After all, the bytes are there, it's just a matter of encoding them as characters for human consumption.