Topic: [ANN][CLAM] CLAMs, Proof-Of-Chain, Proof-Of-Working-Stake, a.k.a. "Clamcoin" - page 365. (Read 1151252 times)
March 19, 2015, 12:22:48 PM
I keep 10 connections, and I'm using 1.4.10, but I get my last block was conflicted. The last one before that on 1.4.7 was conflicted also. What else can I do to stop generating conflicted blocks?
March 19, 2015, 10:02:59 AM
i will try to CLAM too.
Nice idea
I've to download the wallet and insert my old address with the correct key.
Is it right?
thank you and sorry but i cannot read all the posts since the start
Nice idea
I've to download the wallet and insert my old address with the correct key.
Is it right?
thank you and sorry but i cannot read all the posts since the start
March 18, 2015, 10:07:19 AM
Looking to sell my CLAM from a DOGE wallet.
Who wants it? Looking for BTC. (You'd need to explain to me how I can redeem the clams and send it).
Who wants it? Looking for BTC. (You'd need to explain to me how I can redeem the clams and send it).
March 18, 2015, 09:52:20 AM
Just Dice is fun as 
although I lost everything after getting too greedy I'm going to be coming back to try to win it all back plus some 
although I lost everything after getting too greedy I'm going to be coming back to try to win it all back plus some Better to buy and invest in the bankroll than to chase losses. With staking and the ability to leverage your clams will grow a lot faster.
Right said! I myself going to start investing in justdice first...
March 18, 2015, 05:32:22 AM
March 16, 2015, 08:57:17 PM
Just Dice is fun as although I lost everything after getting too greedy I'm going to be coming back to try to win it all back plus some
although I lost everything after getting too greedy I'm going to be coming back to try to win it all back plus some Better to buy and invest in the bankroll than to chase losses. With staking and the ability to leverage your clams will grow a lot faster.
March 16, 2015, 07:44:16 PM
Just to let you know, I have recently added CLAMs to my casino site.
So if you want to check it out; http://volos-casino.com. We have European roulette http://volos-casino.com/roulette.
If you have any questions feel free to ask.
Site bitcointalk thread: https://bitcointalksearch.org/topic/clams-roulette-launch-990126
Also would like to request if it can be added under "Merchants and Services".
I'm currently working on a site when I have free time, but if I see good response from community I would spend more time on this project.
I would also really appreciate any feedback. Thanks. Have fun and good luck.
So if you want to check it out; http://volos-casino.com. We have European roulette http://volos-casino.com/roulette.
If you have any questions feel free to ask.
Site bitcointalk thread: https://bitcointalksearch.org/topic/clams-roulette-launch-990126
Also would like to request if it can be added under "Merchants and Services".
I'm currently working on a site when I have free time, but if I see good response from community I would spend more time on this project.
I would also really appreciate any feedback. Thanks. Have fun and good luck.
Looks like possible CLAM roulette.
https://bitcointalksearch.org/topic/m.10773184
Having investigated very much yet.
Thank you BayAreaCoins you were faster than me in spreading the word https://bitcointalksearch.org/topic/m.10773184
Having investigated very much yet.
March 16, 2015, 11:35:09 AM
Hi,
Is there any payment gateway to accept Clam for someone
who wants to integrate it to his website?
Something like https://blockchain.info/api/api_receive ?
I didn't see any section related at clamclient.com
Thanks.
Is there any payment gateway to accept Clam for someone
who wants to integrate it to his website?
Something like https://blockchain.info/api/api_receive ?
I didn't see any section related at clamclient.com
Thanks.
March 16, 2015, 11:10:29 AM
New CLAMS faucet
faucet.coin43.com/clams
0.0003 - 0.0005 CLAMS every 30 minutes
pls support faucet and consider donating, direct faucet wallet address available on website
faucet.coin43.com/clams
0.0003 - 0.0005 CLAMS every 30 minutes
pls support faucet and consider donating, direct faucet wallet address available on website
March 16, 2015, 02:19:11 AM
I was just wondering if it was intended that when the wallet starts the first things seen is that you have 0 coins and it's unsynced. Is this just because it doesn't have a simple loading stage? Comparing to bitcoin, when it first shows a balance, it was the last balance before sync, the same spot clam's wallet gets to also, just sooner.
March 15, 2015, 10:59:20 PM
Just-Dice will soon be reaching 100 million bets placed since relaunching with CLAM, so we decided to mark the milestone with a little promotion:
People were talking about a promo for the upcoming 100 millionth bet on Just-Dice, so:
20:36:31 (470587) !*** JD #100000000 milestone giveaway ***! 20 CLAM prize for any bet over 1 CLAM that lands || 5 CLAM prize for any bet under 1 CLAM (but over 0.00000069) ~ PM me if you want to add to the pot.
20:38:00 (1) <@dooglus> → (470587) are you talking about just the 100Mth bet?
20:38:09 (470587) → (1) <@dooglus> Yes sir
20:38:31 (470587) → (1) <@dooglus> CBI and I decided to just start making things interesting and doing milestone prizes
20:38:52 (470587) → (1) <@dooglus> So he backed the 5 on low I am backing the 20 on high
20:39:55 (1) <@dooglus> → (470587) ok, how's this? I'll add 10 times the bet size to the pot, for bets up to 100 CLAM - but only if the bet is 50% or lower chance
20:40:18 (470587) → (1) <@dooglus> Wow, that is very generous of you!
20:40:27 (1) <@dooglus> → (470587) so if the 100Mth bet is 100 CLAM @ 49.5%, they get 1k CLAM bonus
20:40:32 (1) <@dooglus> → (470587) if it's at 51%, they get nothing from me
20:40:38 (470587) → (1) <@dooglus> You want to announce it?
20:40:50 (1) <@dooglus> → (470587) no, I'm in the bath and typing's a pain
20:41:07 (470587) → (1) <@dooglus> Okay that I announce it then?
20:41:17 (1) <@dooglus> → (470587) of course
...
20:43:56 (470587) !**** 100M Milestone Update ****! The owners of Just-Dice have agreed to add 10 times the bet size to the pot, for bets up to 100 CLAM - but only if the bet is 50% or lower chance !!!! Get the word out and post it on the forums.
tldr: the 100 millionth bet gets 10 times its stake as a bonus, win or lose, up to 100*10 = 1000 CLAM, and only if the bet is at 50% or lower chance.
20:36:31 (470587)
20:38:00 (1) <@dooglus> → (470587)
20:38:09 (470587)
20:38:31 (470587)
20:38:52 (470587)
20:39:55 (1) <@dooglus> → (470587)
20:40:18 (470587)
20:40:27 (1) <@dooglus> → (470587)
20:40:32 (1) <@dooglus> → (470587)
20:40:38 (470587)
20:40:50 (1) <@dooglus> → (470587)
20:41:07 (470587)
20:41:17 (1) <@dooglus> → (470587)
...
20:43:56 (470587)
tldr: the 100 millionth bet gets 10 times its stake as a bonus, win or lose, up to 100*10 = 1000 CLAM, and only if the bet is at 50% or lower chance.
March 15, 2015, 10:48:51 PM
I apologise if this has already been answered, but how do you fix 'stuck' txs? The tx has a fee included, but after several hours was still at 0 confirms.
I've tried clamd -rescan and clamd -reindex, neither of which worked. What's the right way to 'unstick' a clam tx?
Edit: It finally went through about 10 minutes after the rescan completed.
I've tried clamd -rescan and clamd -reindex, neither of which worked. What's the right way to 'unstick' a clam tx?
Edit: It finally went through about 10 minutes after the rescan completed.
Welcome to Clams ^^
Your balance is always made up of some finite number of unspent transaction outputs. Those outputs stake independently.If you have the client set to split your outputs when they stake, then your whole balance will still be tied up for 8 hours after it stakes the first time, but after that you'll have lots of separate small outputs staking independently. When any one of those outputs stakes, only that output will be tied up for 8 hours. The rest will continue trying to stake.
* you can spend large (in CLAMs) amounts without creating large (in bytes) transactions; if you have a thousand 0.001 CLAM outputs and try to spend them all at once, the transaction size will probably exceed the network limit
Thanks Doog, in a sense its the same as Change addresses in Bitcoin it combines all outputs to get a large enough amount to send to someone else.
So if its split too small then your txt fee goes up significantly (Assuming Coin age is relatively new as well) when sending coins, when staking though it makes sense to split to have more outputs staking independent of each other.
The first stake still impacts the whole balance, but then the settings you put into the client will take effect after.
Thanks
March 15, 2015, 09:32:01 PM
Really great currency so far. Very excited about its future!
March 15, 2015, 07:44:52 PM
Is that in the standard clam-qt? This tx was *from* me rather than *to* me. Still, what you describe does sound about right.
Yes it is. And this code is for rebroadcasting transactions you made.
I was connected to peers and the height that the client reported was the correct height, but the 'confirmations' box in the gui was reporting 'unconnected'. Not sure what to make of that.
Me neither. I only use the clamd command line version of the client.
Are you sure it said 'unconnected'? I don't see that word anywhere in the sources. Do you mean 'unconfirmed'?
Code:
./qt/transactiontablemodel.cpp: status = tr("Unconfirmed");
That just means "not in a block yet".
Not 'unconfirmed'. I might have 'unconnected' wrong though. Maybe 'not connected' or something similar? It only appeared in the tool tip when hovering over the box, the box itself was empty (no graphical '?' symbol).
March 15, 2015, 06:42:53 PM
Is that in the standard clam-qt? This tx was *from* me rather than *to* me. Still, what you describe does sound about right.
Yes it is. And this code is for rebroadcasting transactions you made.
I was connected to peers and the height that the client reported was the correct height, but the 'confirmations' box in the gui was reporting 'unconnected'. Not sure what to make of that.
Me neither. I only use the clamd command line version of the client.
Are you sure it said 'unconnected'? I don't see that word anywhere in the sources. Do you mean 'unconfirmed'?
Code:
./qt/transactiontablemodel.cpp: status = tr("Unconfirmed");
That just means "not in a block yet".
March 15, 2015, 06:33:04 PM
I apologise if this has already been answered, but how do you fix 'stuck' txs? The tx has a fee included, but after several hours was still at 0 confirms.
I've tried clamd -rescan and clamd -reindex, neither of which worked. What's the right way to 'unstick' a clam tx?
Edit: It finally went through about 10 minutes after the rescan completed.
I've tried clamd -rescan and clamd -reindex, neither of which worked. What's the right way to 'unstick' a clam tx?
Edit: It finally went through about 10 minutes after the rescan completed.
There's code that automatically resends our transactions in the event that they need resending:
Code:
void CWallet::ResendWalletTransactions(bool fForce)
{
if (!fForce)
{
// Do this infrequently and randomly to avoid giving away
// that these are our transactions.
static int64_t nNextTime;
if (GetTime() < nNextTime)
return;
bool fFirst = (nNextTime == 0);
nNextTime = GetTime() + GetRand(30 * 60);
if (fFirst)
return;
// Only do it if there's been a new block since last time
static int64_t nLastTime;
if (nTimeBestReceived < nLastTime)
return;
nLastTime = GetTime();
}
{
if (!fForce)
{
// Do this infrequently and randomly to avoid giving away
// that these are our transactions.
static int64_t nNextTime;
if (GetTime() < nNextTime)
return;
bool fFirst = (nNextTime == 0);
nNextTime = GetTime() + GetRand(30 * 60);
if (fFirst)
return;
// Only do it if there's been a new block since last time
static int64_t nLastTime;
if (nTimeBestReceived < nLastTime)
return;
nLastTime = GetTime();
}
There's a random delay there of up to 30 minutes. I expect that's what you saw.
Is that in the standard clam-qt? This tx was *from* me rather than *to* me. Still, what you describe does sound about right.
I'm unclear on what can cause a transaction to fail to be sent initially. Obviously if you aren't connected to any peers then it won't be sent. I'm not sure what happens if your blockchain is out of sync when you make a transaction - perhaps it delays sending until the sync has finished.
I was connected to peers and the height that the client reported was the correct height, but the 'confirmations' box in the gui was reporting 'unconnected'. Not sure what to make of that.
March 15, 2015, 10:30:29 AM
I apologise if this has already been answered, but how do you fix 'stuck' txs? The tx has a fee included, but after several hours was still at 0 confirms.
I've tried clamd -rescan and clamd -reindex, neither of which worked. What's the right way to 'unstick' a clam tx?
Edit: It finally went through about 10 minutes after the rescan completed.
I've tried clamd -rescan and clamd -reindex, neither of which worked. What's the right way to 'unstick' a clam tx?
Edit: It finally went through about 10 minutes after the rescan completed.
There's code that automatically resends our transactions in the event that they need resending:
Code:
void CWallet::ResendWalletTransactions(bool fForce)
{
if (!fForce)
{
// Do this infrequently and randomly to avoid giving away
// that these are our transactions.
static int64_t nNextTime;
if (GetTime() < nNextTime)
return;
bool fFirst = (nNextTime == 0);
nNextTime = GetTime() + GetRand(30 * 60);
if (fFirst)
return;
// Only do it if there's been a new block since last time
static int64_t nLastTime;
if (nTimeBestReceived < nLastTime)
return;
nLastTime = GetTime();
}
{
if (!fForce)
{
// Do this infrequently and randomly to avoid giving away
// that these are our transactions.
static int64_t nNextTime;
if (GetTime() < nNextTime)
return;
bool fFirst = (nNextTime == 0);
nNextTime = GetTime() + GetRand(30 * 60);
if (fFirst)
return;
// Only do it if there's been a new block since last time
static int64_t nLastTime;
if (nTimeBestReceived < nLastTime)
return;
nLastTime = GetTime();
}
There's a random delay there of up to 30 minutes. I expect that's what you saw.
I'm unclear on what can cause a transaction to fail to be sent initially. Obviously if you aren't connected to any peers then it won't be sent. I'm not sure what happens if your blockchain is out of sync when you make a transaction - perhaps it delays sending until the sync has finished.
March 15, 2015, 04:59:55 AM
Looks like possible CLAM roulette.
https://bitcointalksearch.org/topic/m.10773184
Having investigated very much yet.
https://bitcointalksearch.org/topic/m.10773184
Having investigated very much yet.
March 14, 2015, 08:39:23 PM
I apologise if this has already been answered, but how do you fix 'stuck' txs? The tx has a fee included, but after several hours was still at 0 confirms.
I've tried clamd -rescan and clamd -reindex, neither of which worked. What's the right way to 'unstick' a clam tx?
Edit: It finally went through about 10 minutes after the rescan completed.
Welcome to CLAMs organofcorti I've tried clamd -rescan and clamd -reindex, neither of which worked. What's the right way to 'unstick' a clam tx?
Edit: It finally went through about 10 minutes after the rescan completed.
Obviously, under normal circumstances, they shouldn't get stuck at all.
Would love some details either via thread, PM, git, or #clams IRC @ freenode.
Anything unusual or non-standard about the transaction itself?
Were more than one client/daemon running at the same time with the same wallet/keys?
Was the client properly sync'd to the chain during the time in which the transaction was not confirming?
Anything anomalous in the debug logs file?
March 14, 2015, 08:21:17 PM
I apologise if this has already been answered, but how do you fix 'stuck' txs? The tx has a fee included, but after several hours was still at 0 confirms.
I've tried clamd -rescan and clamd -reindex, neither of which worked. What's the right way to 'unstick' a clam tx?
Edit: It finally went through about 10 minutes after the rescan completed.
I've tried clamd -rescan and clamd -reindex, neither of which worked. What's the right way to 'unstick' a clam tx?
Edit: It finally went through about 10 minutes after the rescan completed.
Welcome to CLAMs organofcorti
Obviously, under normal circumstances, they shouldn't get stuck at all.
Would love some details either via thread, PM, git, or #clams IRC @ freenode.
What details do you need?
Jump to: