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

[SuperClam]

okay now just join this clam things...
but i dont have btc wallet for claim clam...is there free clam for testing just-dice?
thanks

Did you have LTC or DOGE either?
You can get a few CLAMs via JD chat maybe, but that shit sucks grinding that hard for nothing.
Better to buy them or what not.
Also if you have shit for sell you can always try to sell shit in JD or in different posts.  Always good for a little economy for people to be buying and selling things. I buy random shit all the time!

Like prime rib?

[BayAreaCoins]

Like prime rib?

Next one I'm going to make sure they don't forget the damn Horse Radish!

[BayAreaCoins]

New CLAM bet on BitBet.

https://bitbet.us/bet/1121/clam-losing-grip-sells-0-0029-or-lower/

[SuperClam]

New CLAM bet on BitBet.
https://bitbet.us/bet/1121/clam-losing-grip-sells-0-0029-or-lower/

It appears CLAM has since been banned at bitbet.us?


Will be interesting to keep an eye on the above bet - never under-estimate the CLAM

[dooglus]

New CLAM bet on BitBet.
https://bitbet.us/bet/1121/clam-losing-grip-sells-0-0029-or-lower/

It appears CLAM has since been banned at bitbet.us?


Will be interesting to keep an eye on the above bet - never under-estimate the CLAM

MP saying he would ban CLAM bets: http://log.bitcoin-assets.com//?date=23-02-2015#1029748

02:55:23 mircea_popescu: so i'm banning both clam shitcoin and cryptsy from bitbet. anyone want to argue either ?

MP saying the existing bet will run its course: http://log.bitcoin-assets.com//?date=25-02-2015#1033547

19:12:31 BayAreaCoins: MP do you plan on pulling the CLAM bet on BitBet or is it going to run its course? If you do cancel it I assume the coins will just be sent to the payment addresses?
19:13:36 mircea_popescu: which bet is this ?
19:13:47 BayAreaCoins: MP, https://bitbet.us/bet/1121/clam-losing-grip-sells-0-0029-or-lower/
19:13:48 assbot: BitBet - CLAM losing grip -> sells 0.0029 or lower before April 25th :: 0.18 B (3%) on Yes, 5.08 B (97%) on No | closing in 1 month 3 weeks | weight: 93`348 (100`000 to 10) ... ( http://bit.ly/1Dqxbjc )
19:14:19 mircea_popescu: its gonna run.

Recent comment on the bet itself:

#4618: anony-mousse 25-02-15 at 19:18

please, bet more BTC on no. this gon b gud.

It will be interesting to see how it plays out.

[Nthused]

Is there a CLAMs Multipool ?

[maidenvoyage]

Hey
I really liked just-dice when it was BTC.
Then it was closed.
Now it reopens with these CLAMS.
I should import all my BTC Wallet into a program, which I do not know... had to install on my computer...

I mean... I would never do that.. .I hardly believe in the security of the BTC Blockchain.. But then put another algorithm on top of it.

And WHY.. WHY would you add this layer of complexity?

Please bring back BTC investing.
Yours
maidenvoyage

[Vortex20000]

I hardly believe in the security of the BTC Blockchain..

Then why do you hold bitcoin?

And WHY.. WHY would you add this layer of complexity?

How is it complex? The clam wallet is just like any other altcoin wallet (prettier, though).

In fact, you don't even need to own the wallet software to get your clams. Read JD FAQ for more info.

Please bring back BTC investing.

JD closed because it was illegal for Doog to run a BTC gambling site, I think. CLAM is not directly convertable to fiat yet, so I think that's why it's allowed. Again, not sure.

Doog can give more, informative insight into this.

[SuperClam]

I should import all my BTC Wallet into a program, which I do not know... had to install on my computer...

"Should" or "should not" is entirely up to you.
There are likely free CLAMs on the chain for you; you have to make the judgement to claim them or not.

I mean... I would never do that.. .I hardly believe in the security of the BTC Blockchain.. But then put another algorithm on top of it.

There is absolutely Zero risk of coin theft if you follow the recommended method of claiming.
(And there is yet to be even a single reported instance of coin theft, even if you do not).

Once you have retired/emptied your BTC/LTC/DOGE into a new wallet the original wallet is nothing more than meta-data and worthless strings.

And WHY.. WHY would you add this layer of complexity?

It would be difficult to make the process any simpler at this point.
After emptying the wallet, a user must only click File -> Import Wallet, and browse to the wallet.dat file.
Done.

[picolo]

The price of CLAM moves compared to USD; when bitcoin has been going up last month,  the price of clam in btc has been going down.

At the same time, the price of clam has been appreciating in USD : more than 1.7$ right now.

[SuperClam]

The price of CLAM moves compared to USD; when bitcoin has been going up last month,  the price of clam in btc has been going down.
At the same time, the price of clam has been appreciating in USD : more than 1.7$ right now.

Don't forget stake.

Simply maintaining valuation, while simultaneously staking, is a net appreciation of value.

[dooglus]

I was wondering whether the recent drop was caused by someone new "discovering" that they had a bunch of free CLAM, digging them up, and dumping them.

So I plotted the total dug and the total staked over the last few months.

I'm not seeing any drastic upturn in the rate of digging:



Edit: here's how I collected and plotted the data:

Code:

b=$(clamd getblockcount); s=$b; while ((b > s-60*24*7*7)); do echo $(clamd getblock $(clamd getblockhash $b) | grep -e height -e supply -e time -e difficulty | awk '{print $3}' | tr -d ,); ((b -= 300)); done > ~/Documents/clam/getblock.dat

Code:

#!/usr/bin/gnuplot

set terminal wxt size 1400,700
plot sin(x) # resize window with junk plot

set grid
set timefmt "%s"
set xlabel "date"
set xdata time
set xtics format "%b %d"
set key bottom right
plot "~/Documents/clam/getblock.dat" using 6:($3/1e0) title "digsupply" with lines lw 3, \
     "~/Documents/clam/getblock.dat" using 6:($4/1e0) title "stakesupply" with lines lw 3; pause -1

# $1 height
# $2 moneysupply
# $3 digsupply
# $4 stakesupply
# $5 activesupply
# $6 time
# $7 difficulty

[shawn2025]

Mac fag checking in.  Running 1.4.10 and smooth sailing so far.  Staking and all. 
Curious behaviour as the staking icon goes red more than I've ever seen but I can't
see a problem.   

So far so good.  Let me know if I can be of service. 

/s/

[dooglus]

Mac fag checking in.  Running 1.4.10 and smooth sailing so far.  Staking and all. 
Curious behaviour as the staking icon goes red more than I've ever seen but I can't
see a problem.

Does it go red for long periods at a time? Long enough that you can hover the mouse over it and tell me what pops up when it's red?

If you put:
debug=stake
in the clam.conf file in the same folder as your wallet.dat and restart, it will write stake-related stuff to debug.log in the same folder as it stakes.

You could "tail -f debug.log" in that folder and see whether anything looks different when it's red. Staking basically consists of hashing each of your staking outputs every 16 seconds and comparing the result with a target based on the network difficulty. If the output hashes lower than the target, you get to stake a block. "debug=stake" will cause these hashes that are being compared to be logged.

[shawn2025]

Mac fag checking in.  Running 1.4.10 and smooth sailing so far.  Staking and all. 
Curious behaviour as the staking icon goes red more than I've ever seen but I can't
see a problem.

Does it go red for long periods at a time? Long enough that you can hover the mouse over it and tell me what pops up when it's red?

If you put:
debug=stake
in the clam.conf file in the same folder as your wallet.dat and restart, it will write stake-related stuff to debug.log in the same folder as it stakes.

You could "tail -f debug.log" in that folder and see whether anything looks different when it's red. Staking basically consists of hashing each of your staking outputs every 16 seconds and comparing the result with a target based on the network difficulty. If the output hashes lower than the target, you get to stake a block. "debug=stake" will cause these hashes that are being compared to be logged.

I couldn't find an existing one, so I created a clam.conf and added debug=stake.  I'm hoping I did it correctly.  I added a screengrab of data flow. http://imgur.com/Gmcfbf8 When I hover the cursor over the red icon, it sometimes says 0 weight.  And then other times it says not staking because I don't have mature coins.  But then I stake at least once a day. 

Hope this helps.  Thanks for everything! 

/s/

[picolo]

The price of CLAM moves compared to USD; when bitcoin has been going up last month,  the price of clam in btc has been going down.
At the same time, the price of clam has been appreciating in USD : more than 1.7$ right now.

Don't forget stake.

Simply maintaining valuation, while simultaneously staking, is a net appreciation of value.

Someone who bought at 0.004 and invested in just-dice must be sitting on a nice btc and usd profit indeed.

[rocoro]

Mac fag checking in.  Running 1.4.10 and smooth sailing so far.  Staking and all. 
Curious behaviour as the staking icon goes red more than I've ever seen but I can't
see a problem.

Does it go red for long periods at a time? Long enough that you can hover the mouse over it and tell me what pops up when it's red?

If you put:
debug=stake
in the clam.conf file in the same folder as your wallet.dat and restart, it will write stake-related stuff to debug.log in the same folder as it stakes.

You could "tail -f debug.log" in that folder and see whether anything looks different when it's red. Staking basically consists of hashing each of your staking outputs every 16 seconds and comparing the result with a target based on the network difficulty. If the output hashes lower than the target, you get to stake a block. "debug=stake" will cause these hashes that are being compared to be logged.

I couldn't find an existing one, so I created a clam.conf and added debug=stake.  I'm hoping I did it correctly.  I added a screengrab of data flow. http://imgur.com/Gmcfbf8 When I hover the cursor over the red icon, it sometimes says 0 weight.  And then other times it says not staking because I don't have mature coins.  But then I stake at least once a day. 

Hope this helps.  Thanks for everything! 

/s/

Same thing was happening to me on a previous version (1.4.7 i think)  and the 0 weight was also showing.
I haven't seen it happen to me again yet on this latest version.. but I'll watch for it.

[Evil-Dragon]

Mac fag checking in.  Running 1.4.10 and smooth sailing so far.  Staking and all. 
Curious behaviour as the staking icon goes red more than I've ever seen but I can't
see a problem.

Does it go red for long periods at a time? Long enough that you can hover the mouse over it and tell me what pops up when it's red?

If you put:
debug=stake
in the clam.conf file in the same folder as your wallet.dat and restart, it will write stake-related stuff to debug.log in the same folder as it stakes.

You could "tail -f debug.log" in that folder and see whether anything looks different when it's red. Staking basically consists of hashing each of your staking outputs every 16 seconds and comparing the result with a target based on the network difficulty. If the output hashes lower than the target, you get to stake a block. "debug=stake" will cause these hashes that are being compared to be logged.

I couldn't find an existing one, so I created a clam.conf and added debug=stake.  I'm hoping I did it correctly.  I added a screengrab of data flow. http://imgur.com/Gmcfbf8 When I hover the cursor over the red icon, it sometimes says 0 weight.  And then other times it says not staking because I don't have mature coins.  But then I stake at least once a day. 

Hope this helps.  Thanks for everything! 

/s/

Same thing was happening to me on a previous version (1.4.7 i think)  and the 0 weight was also showing.
I haven't seen it happen to me again yet on this latest version.. but I'll watch for it.

It can stay red for up to one minute, i've seen it myself. When you hover over it says 'Not staking because you don't have mature coins'

It doesn't appear to affect staking in the long run, i always just put it down to new blocks being generated and that it was a normal thing.

I have the debug switch on at the moment so i'll try and upload the debug.log next time i see it happen.

[shawn2025]

Mac fag checking in.  Running 1.4.10 and smooth sailing so far.  Staking and all. 
Curious behaviour as the staking icon goes red more than I've ever seen but I can't
see a problem.

Does it go red for long periods at a time? Long enough that you can hover the mouse over it and tell me what pops up when it's red?

If you put:
debug=stake
in the clam.conf file in the same folder as your wallet.dat and restart, it will write stake-related stuff to debug.log in the same folder as it stakes.

You could "tail -f debug.log" in that folder and see whether anything looks different when it's red. Staking basically consists of hashing each of your staking outputs every 16 seconds and comparing the result with a target based on the network difficulty. If the output hashes lower than the target, you get to stake a block. "debug=stake" will cause these hashes that are being compared to be logged.

I couldn't find an existing one, so I created a clam.conf and added debug=stake.  I'm hoping I did it correctly.  I added a screengrab of data flow. http://imgur.com/Gmcfbf8 When I hover the cursor over the red icon, it sometimes says 0 weight.  And then other times it says not staking because I don't have mature coins.  But then I stake at least once a day. 

Hope this helps.  Thanks for everything! 

/s/

Same thing was happening to me on a previous version (1.4.7 i think)  and the 0 weight was also showing.
I haven't seen it happen to me again yet on this latest version.. but I'll watch for it.

It can stay red for up to one minute, i've seen it myself. When you hover over it says 'Not staking because you don't have mature coins'

It doesn't appear to affect staking in the long run, i always just put it down to new blocks being generated and that it was a normal thing.

I have the debug switch on at the moment so i'll try and upload the debug.log next time i see it happen.

I think I caught a red patch in the debug log.  This is the point where it was red and then normalized:

ERROR: AcceptToMemoryPool : ConnectInputs failed 275b33ea6daf21907648b93235e33942d63c759c139efe8135f9e88a02aec89f
ERROR: ConnectInputs() : afa49bad29ccfd608c5aefb44d407fabfea69fa15d3ea1f5c256d783b10daf6e prev tx already used at (nFile=1, nBlockPos=319403622, nTxPos=319404329)
ERROR: AcceptToMemoryPool : ConnectInputs failed afa49bad29ccfd608c5aefb44d407fabfea69fa15d3ea1f5c256d783b10daf6e
ERROR: ConnectInputs() : 58c3a3c1186b5c89c3ac5772eced46233bff83cee7de7c8efc6fe1f3b96029a7 prev tx already used at (nFile=1, nBlockPos=342165995, nTxPos=342168405)
ERROR: AcceptToMemoryPool : ConnectInputs failed 58c3a3c1186b5c89c3ac5772eced46233bff83cee7de7c8efc6fe1f3b96029a7
ERROR: ConnectInputs() : 9236ca795d0acf1016cfaa99887c75e79465376f9d64dfa6f7c02fcbffd2ec62 prev tx already used at (nFile=1, nBlockPos=342323040, nTxPos=342323537)
ERROR: AcceptToMemoryPool : ConnectInputs failed 9236ca795d0acf1016cfaa99887c75e79465376f9d64dfa6f7c02fcbffd2ec62
ERROR: ConnectInputs() : 0b675b9287c686a297de540dbc6909342dcd494164ee73fc7a14484b53e436a1 prev tx already used at (nFile=1, nBlockPos=342592588, nTxPos=342593400)
ERROR: AcceptToMemoryPool : ConnectInputs failed 0b675b9287c686a297de540dbc6909342dcd494164ee73fc7a14484b53e436a1
stake took 0s
stake took 0s
stake took 0s
stake took 0s
SetBestChain: new best=c4f00cb1bd10f1465095c98ace135a9cde9beff8f28f92469835487faf060c35  height=360756  trust=16799287784950803720  blocktrust=156701501658267  date=03/01/15 04:48:48
ProcessBlock: ACCEPTED
stake took 0s
SetBestChain: new best=8e2c754fd4bcadb59b715244d7f885f2059120b7d862f0b0e29f1c01e929a9c7  height=360757  trust=16799443607527302960  blocktrust=155822576499240  date=03/01/15 04:49:20
ProcessBlock: ACCEPTED
stake took 0s
SetBestChain: new best=8aec101da5519366c1b71c094f9ddf4d213860433299fd918f89ef03b83a62d6  height=360758  trust=16799598557078531095  blocktrust=154949551228135  date=03/01/15 04:49:36
ProcessBlock: ACCEPTED

[hoeslayer]

ok I need help here. I only have 2 connections on my wallet and I would like to add more but I don't know how. I am using windows. newest version.
"version" : "v1.4.10","protocolversion" : 60014,
"walletversion" : 60000,
"balance" : 10.15125949,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 360771,
"timeoffset" : 0,
"moneysupply" : 15030823.13048927,
"digsupply" : 299515.81405090,
"stakesupply" : 256421.72641731,
"activesupply" : 555937.54046821,
"connections" : 2,
"proxy" : "",
"ip" : "0.0.0.0",
"difficulty" : {
"proof-of-stake" : 34173.31126671
},
"testnet" : false,
"keypoololdest" : 1424304149,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00000000,
"unlocked_until" : 0,
"errors" : ""
}
how do I add more I kinda need a step by step.
thank you