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

[slasi1974]

quit interesting idea is it still active or not?

[BayAreaCoins]

FreeBitcoins.com CLAM faucet is back online.

We are strictly doing offchain transactions for our faucet in order not to shit up the CLAM blockchain any more than necessary.

Our CLAM faucet currently connects to Freebitcoins.com and Just-dice.com... we will be adding more site though!

[jpcfan]

when will new clam wallet come out?


over/under is 36 months


place your wagers now

[tbct_mt2]

Today, Bitcoin has passed exactly 10 years since its born day.

For CLAM, the project started in May of 2014.

Code:

May 24, 2014, 04:33:19 AM

It means the project has nearly four-year history, long enough to be recogised by crypto enthusiasts globally.
Fortunately, CLAM has actually had very solid community around the globe.

[Dimon777]

I downloaded the file to better synchronize the wallet but the problem remained
it does not load what is the reason?

[BayAreaCoins]

Deb from Just-Dice.com made a commit today!  (Her first one ever I believe)

https://github.com/nochowderforyou/clams/commit/d59fba3c5b0bdcdfceb091e08ea430579b1e12a5

We need more people helping get this new client release... Please message dooglus or myself for a link to the Discord if you think you can help.

Thanks!

[vashshawn]

having trouble syncing the current client, even with the current bootstrap..

[BayAreaCoins]

having trouble syncing the current client, even with the current bootstrap..

You need to be a fairly experienced user atm to run a CLAM wallet it seems.

It may be best to just wait for the new wallet to be released.... it's being worked on.

[vashshawn]

I will just delete the blockchain and try loading the bootstrap again and see if it works. I tried the normal download and the torrent.

[Broko82]

having trouble syncing the current client, even with the current bootstrap..

You need to be a fairly experienced user atm to run a CLAM wallet it seems.

It may be best to just wait for the new wallet to be released.... it's being worked on.

I don't think so. I have been running the 1.4.17 client for several months without any issues. I also downloaded the bootstrap file via torrent.
Syncing just needs time. Let it work and the client will download all the necessary data, although it may seem unresponsive for quite some time.

[criptocambio]

Im not sure, but i think it's affecting everyone. Here is my debug.log:

SetBestChain: new best=6bb9fa2bb3c51f7526d153307d68e9acce3e00e1033e53e73f707310$
ProcessBlock: ACCEPTED
receive version message: version 60014, blocks=931607, us=51.158.75.80:31174, t$
stake took 10s


10 seconds to validate a block, as there is a lot of blocks that take only 1 second or less.

Looks like every block minted by just-dice is affected, as every time i receive them, they take more than 10 seconds to validate even in the ones that do not have dust output. Blocks that dont have your addresses, stake as quick as one second or less. Right now, i had put mininput=0.001 in the config file to see if this attack ceases, and hope this does not fork the network as someone can mint a block with outputs smaller than this and my node will reject it.

I saw blocks taking several seconds to validate months before and thought this was because some other software taking resources in my machine other than clam client. Also, the elevation in the difficulty from 90000-100000 to almost 200000 at some times started at the same time i saw these blocks that take a lot of time to validate. Maybe this attack is much more older than we think

Note that the "stake took 10s" is telling you how long your client took to check through your unspent outputs to see whether you had any which were ready to stake. You should be seeing those "stake took Xs" about every 16 seconds, not once per block.

Note also that you should put "logtimestamps=1" in your clam.conf so that every line of your debug,log gets timestamped.

The "mininput" thing won't fork the network. You're not rejecting any transactions, you're just ignoring some of them. They still go into your UTXO database but your wallet doesn't recognize them as belonging to you and so it won't waste time trying to stake them.

The difficulty goes up and down wildly every day due to how it is calculated. I don't think that's anything to worry too much about. How are your "stake took ..." times looking now? Are they back to where they used to be again?

How are your "stake took ..." times looking now? Are they back to where they used to be again?

I still get 5-10 seconds to validate after a block arrives, but then it gets to 0 again. Probably not related to the dust outputs tough, as i already got mininput in the clam.conf

[Faust Roland]

Hi guys,

I have some issues with staking on Raspberry Pi* - it seems it started swapping (not sure how long it was doing that) and I got probably disconected and "forked" in December - found out that I staked every block for few days.
I am resyncing the chain since then. Even with bootstrap it took very long time.
Today I finally finished the sync, but 
1) I am getting some strange logs - ERROR: CheckBlock() : block timestamp too far in the future   ( I have correct date)
2) Seems it takes quite time to accept a new block. While on the block explorer its aready there it takes ~minute before accepted by my node.

Does anyone running on raspberry have similar issues? Is it because the size of blockchain grew out what Raspberry can handle? Or?


* Raspberry Pi 3 Model B 64-bit 1GB RAM

[huu78]

I used to be an old player at Just-Dice playing with Clam. I've never been there for a long time. And this is good news with FreeBitcoins.com coming back. Maybe with the presence of Fauchet, you could say that, you will become a supporter and enliven again in just playing clam.

[Bit-Exo.com]

FreeBitcoins.com CLAM faucet is back online.

We are strictly doing offchain transactions for our faucet in order not to shit up the CLAM blockchain any more than necessary.

Our CLAM faucet currently connects to Freebitcoins.com and Just-dice.com... we will be adding more site though!

Would be awesome to have our site added to the list

[BayAreaCoins]

FreeBitcoins.com CLAM faucet is back online.

We are strictly doing offchain transactions for our faucet in order not to shit up the CLAM blockchain any more than necessary.

Our CLAM faucet currently connects to Freebitcoins.com and Just-dice.com... we will be adding more site though!

Would be awesome to have our site added to the list

I'll message you on skype when I wake up and see if we can work something out <3!

[bolo1970]

  The doge blockchain has become so big that someone invented multidoge, similar to multibit for bitcoin. What happens to all the multibit and multidoge users? They do not have wallet.dat files and will probably lack the technical skills to export keys.  Another question is if I need my BTC/LTC/DOGE wallet update to the latest block before I copy it to the appdata/Roaming/CLAM/?

[Faust Roland]

All nodes I connect has odd timeoffset - between -100 to -60. Also I am pretty sure, that I have correct time at my node. Is there something I can do with that?

$ cli getpeerinfo | grep "addr\|timeoffset" | grep -v local
    "addr" : "151.226.102.252:31174",
    "timeoffset" : -94,
    "addr" : "46.4.113.143:31174",
    "timeoffset" : -97,
    "addr" : "165.227.93.150:31174",
    "timeoffset" : -94,
    "addr" : "95.87.207.152:31174",
    "timeoffset" : -95,
    "addr" : "67.205.153.62:31174",
    "timeoffset" : -88,
    "addr" : "94.23.58.222:31174",
    "timeoffset" : -95,
    "addr" : "124.191.213.74:31174",
    "timeoffset" : -109,
    "addr" : "97.83.177.95:31174",
    "timeoffset" : -95,
    "addr" : "69.121.201.75:31174",
    "timeoffset" : -96,
    "addr" : "82.21.202.185:31174",
    "timeoffset" : -101,
    "addr" : "67.191.63.234:31174",
    "timeoffset" : -92,
    "addr" : "176.58.119.91:31174",
    "timeoffset" : -88,
    "addr" : "193.111.198.69:31174",
    "timeoffset" : -86,
    "addr" : "188.40.206.114:31174",
    "timeoffset" : -79,
    "addr" : "158.129.212.236:31174",
    "timeoffset" : -72,
    "addr" : "178.62.8.78:31174",
    "timeoffset" : -66,

[criptocambio]

All nodes I connect has odd timeoffset - between -100 to -60. Also I am pretty sure, that I have correct time at my node. Is there something I can do with that?

$ cli getpeerinfo | grep "addr\|timeoffset" | grep -v local
    "addr" : "151.226.102.252:31174",
    "timeoffset" : -94,
    "addr" : "46.4.113.143:31174",
    "timeoffset" : -97,
    "addr" : "165.227.93.150:31174",
    "timeoffset" : -94,
    "addr" : "95.87.207.152:31174",
    "timeoffset" : -95,
    "addr" : "67.205.153.62:31174",
    "timeoffset" : -88,
    "addr" : "94.23.58.222:31174",
    "timeoffset" : -95,
    "addr" : "124.191.213.74:31174",
    "timeoffset" : -109,
    "addr" : "97.83.177.95:31174",
    "timeoffset" : -95,
    "addr" : "69.121.201.75:31174",
    "timeoffset" : -96,
    "addr" : "82.21.202.185:31174",
    "timeoffset" : -101,
    "addr" : "67.191.63.234:31174",
    "timeoffset" : -92,
    "addr" : "176.58.119.91:31174",
    "timeoffset" : -88,
    "addr" : "193.111.198.69:31174",
    "timeoffset" : -86,
    "addr" : "188.40.206.114:31174",
    "timeoffset" : -79,
    "addr" : "158.129.212.236:31174",
    "timeoffset" : -72,
    "addr" : "178.62.8.78:31174",
    "timeoffset" : -66,

Either you need to update your clock, or everyone does. This can be caused because of clock drifting, or some other issues. Please sync your computer with an NTP server to be sure your clock is right: Google have a huge NTP server and a nice tutorial here https://developers.google.com/time/guides

The doge blockchain has become so big that someone invented multidoge, similar to multibit for bitcoin. What happens to all the multibit and multidoge users? They do not have wallet.dat files and will probably lack the technical skills to export keys. 

All softwares that tries to manage a criptocurrency portfolio have some sort of way to export private keys. Multibit, for example, have this tutorial:
https://multibit.org/help/v0.5/help_exportingPrivateKeys.html

Access to a wallet.dat is not necessary, as you can import these private keys to any other compatible software. The lack of technical skills, however, can really be a problem for some people: But the wallet technology is quickly getting easier to use. We already have some wallets that you just need to write down some words instead of exporting keys, for example.

Another question is if I need my BTC/LTC/DOGE wallet update to the latest block before I copy it to the appdata/Roaming/CLAM/?

Please do not copy files from other coins inside the CLAM client. They are different, and are not compatible between them. If you need to update your CLAM client, please let it update by itself or use a bootstrap.dat made by dooglus.

[Faust Roland]

All nodes I connect has odd timeoffset - between -100 to -60. Also I am pretty sure, that I have correct time at my node. Is there something I can do with that?

Either you need to update your clock, or everyone does. This can be caused because of clock drifting, or some other issues. Please sync your computer with an NTP server to be sure your clock is right: Google have a huge NTP server and a nice tutorial here https://developers.google.com/time/guides

The Raspberry has the time correctly synchronized. I started the clam node on my work PC (also synced)
Both nodes are connected to the same peer 69.121.201.75:31174, but Raspberry says "timeoffset" : -185, WorkPC says "timeoffset" : 0,
I have no idea whats wrong...


Raspberry

ntpdate -d time1.google.com | sed -n '$s/.*offset //p'
-0.008269 sec

cli getpeerinfo | grep timeoffset
    "addr" : "67.191.63.234:31174",
    "timeoffset" : -182,
    "addr" : "69.121.201.75:31174",
    "timeoffset" : -185,
    "addr" : "94.23.58.222:31174",
    "timeoffset" : -186,
    "addr" : "178.62.8.78:31174",
    "timeoffset" : -137,
    "addr" : "67.205.153.62:31174",
    "timeoffset" : -138,
    "addr" : "82.21.202.185:31174",
    "timeoffset" : -140,
    "addr" : "176.58.119.91:31174",
    "timeoffset" : -113,
    "addr" : "158.129.212.236:31174",
    "timeoffset" : -120,
    "addr" : "74.82.244.243:31174",
    "timeoffset" : -99,
    "addr" : "89.115.82.116:31174",
    "timeoffset" : -98,
    "addr" : "193.111.198.69:31174",
    "timeoffset" : -59,
    "addr" : "151.226.102.252:31174",
    "timeoffset" : -12,
    "addr" : "165.227.93.150:31174",
    "timeoffset" : -12,
    "addr" : "46.4.113.143:31174",
    "timeoffset" : -7,
    "addr" : "95.87.207.152:31174",
    "timeoffset" : -22,
    "addr" : "70.77.101.45:31174",
    "timeoffset" : -1,

Work PC (currently syncing)
ntpdate -d time1.google.com | sed -n '$s/.*offset //p'
host found : time1.google.com
0.000309 sec

        "addr" : "178.62.8.78:31174",
        "timeoffset" : 0,
        "addr" : "67.191.63.234:31174",
        "timeoffset" : -1,
        "addr" : "158.69.32.10:31174",
        "timeoffset" : 0,
        "addr" : "47.214.177.20:31174",
        "timeoffset" : -1,
        "addr" : "89.142.71.41:31174",
        "timeoffset" : -1,
        "addr" : "159.203.5.220:31174",
        "timeoffset" : -1,
        "addr" : "176.58.119.91:31174",
        "timeoffset" : -1,
        "addr" : "95.87.207.152:31174",
        "timeoffset" : 0,
        "addr" : "89.115.82.116:31174",
        "timeoffset" : 0,
        "addr" : "78.46.108.202:31174",
        "timeoffset" : -1,
        "addr" : "69.121.201.75:31174",
        "timeoffset" : 0,
        "addr" : "45.58.115.206:31174",
        "timeoffset" : -2,
        "addr" : "46.4.113.143:31174",
        "timeoffset" : -2,
        "addr" : "185.52.2.48:31174",
        "timeoffset" : 0,
        "addr" : "97.83.177.95:31174",
        "timeoffset" : -1,
        "addr" : "73.170.212.102:31174",
        "timeoffset" : 0,

[Broko82]

I have some difficulties staking recently. I should obtain one coin every ~30 hours, but my last stake dates back to 2 of January 2019.
I am wondering, if something is wrong with my configuration. The wallet seems to be fine.
Just a few minutes ago I got an orphaned block... :-(

Is it normal, to wait such a long time?