Author

Topic: [ANN][CLAM] CLAMs, Proof-Of-Chain, Proof-Of-Working-Stake, a.k.a. "Clamcoin" - page 237. (Read 1151373 times)

newbie
Activity: 38
Merit: 0

I agree and that's a large part of the reason, aside from it being unethical, that I'm firmly against any undug CLAM grab. The do well in the future this coin has to grow and that means: a) long term confidence that comes from NOT tinkering with the parameters when it is convenient, and b) bringing new people and services into the ecosystem, which is helped not harmed by having a stronger distribution mechanism.

I certainly agree that a coin needs long time confidence and i would like to see more services for clam (not only gambling sites, cause that wont help the coin on the long run either), what i find unbelievable though is that people in general think, rules on a coin made from starters are set in stone and can never be changed again..yet we are even not sure WHEN the digger will end, maybe beginning next year, maybe in middle of 2016 or after..

What if the next big digger is a huge site with a big BTC/LTC/DOGE wallet that instead of digging and dumping (as this digger appears to be doing) instead sees it in their interest to support CLAM on their site and promote it?

This Site would have all wallets like the digger on the exact date to do the digging, otherwise to promote the coin they just go to an exchange and buy these clam.

That will never happen if the short-sighted decision is made to hurt future diggers in response to THIS digger.

as far as i know, no one wants to remove the digging feature, just slow the digger down..

Greetings, Chuck
legendary
Activity: 1007
Merit: 1000
Should have sold at 0.001+ :-D

It will go back to that price as big players loose and buy back some clams.

  You've got plenty of time to sell at .001.  The price just needs to drop another .0005 and you're there.  Tongue  I'm assuming you meant .01.  Cheesy
hero member
Activity: 1022
Merit: 500
Should have sold at 0.001+ :-D

It will go back to that price as big players loose and buy back some clams.
legendary
Activity: 2968
Merit: 1198
So now it comes full circle again to simply limiting the mining (digging) to an amount that would be equivalent to a PoW coin that has been out for as many months as CLAMs has. Several hundred clams dug per day was a rough approximation I had come up with in the past.

There is no need to stop the digging but it must be limited so that millions of coins cannot get dug in a short period of time. Any low impact solution that does not limit the daily digging in some way will probably not save the coin. I can see it limiting the speed at which diggers can make money and increasing the value of the coin significantly. So diggers might be against it having to wait longer to dig all their coins.
But better CLAMS market cap be $1 million+ again and have to wait to dig your CLAMs than for them to be near worthless as the market cap drops under $100k.

So how long till this vote? And then how long after that for implementation.

I don't share your optimism that slowing the digging will result in a recovered price. Higher than it is currently? Possibly, but I'm skeptical it holds for any meaningful period of time. The problem is that even with slowed digging, there's already a great many more CLAMs out there chasing the same small base of buyers, and the buyers are mainly gamblers at JD. So unless you increase demand for the coin, the base of buyers doesn't increase, and the price doesn't recover, it just keeps slowly dropping.

Now the price might recover initially as confidence is restored in the system and people buy back in to earn their staking income under the delusion that they're "making money" by holding CLAM, but eventually to realize the "profit" they have to cash out to BTC, and when this happens in any meaningful way, the price plummets. This is the long term reality of CLAM. The falling price isn't an anomaly caused by the whale digger, it's the long term trend being accelerated by him.

I agree and that's a large part of the reason, aside from it being unethical, that I'm firmly against any undug CLAM grab. The do well in the future this coin has to grow and that means: a) long term confidence that comes from NOT tinkering with the parameters when it is convenient, and b) bringing new people and services into the ecosystem, which is helped not harmed by having a stronger distribution mechanism.

What if the next big digger is a huge site with a big BTC/LTC/DOGE wallet that instead of digging and dumping (as this digger appears to be doing) instead sees it in their interest to support CLAM on their site and promote it? That will never happen if the short-sighted decision is made to hurt future diggers in response to THIS digger.
legendary
Activity: 2016
Merit: 1115
So now it comes full circle again to simply limiting the mining (digging) to an amount that would be equivalent to a PoW coin that has been out for as many months as CLAMs has. Several hundred clams dug per day was a rough approximation I had come up with in the past.

There is no need to stop the digging but it must be limited so that millions of coins cannot get dug in a short period of time. Any low impact solution that does not limit the daily digging in some way will probably not save the coin. I can see it limiting the speed at which diggers can make money and increasing the value of the coin significantly. So diggers might be against it having to wait longer to dig all their coins.
But better CLAMS market cap be $1 million+ again and have to wait to dig your CLAMs than for them to be near worthless as the market cap drops under $100k.

So how long till this vote? And then how long after that for implementation.

I don't share your optimism that slowing the digging will result in a recovered price. Higher than it is currently? Possibly, but I'm skeptical it holds for any meaningful period of time. The problem is that even with slowed digging, there's already a great many more CLAMs out there chasing the same small base of buyers, and the buyers are mainly gamblers at JD. So unless you increase demand for the coin, the base of buyers doesn't increase, and the price doesn't recover, it just keeps slowly dropping.

Now the price might recover initially as confidence is restored in the system and people buy back in to earn their staking income under the delusion that they're "making money" by holding CLAM, but eventually to realize the "profit" they have to cash out to BTC, and when this happens in any meaningful way, the price plummets. This is the long term reality of CLAM. The falling price isn't an anomaly caused by the whale digger, it's the long term trend being accelerated by him.
legendary
Activity: 1386
Merit: 1023
So now it comes full circle again to simply limiting the mining (digging) to an amount that would be equivalent to a PoW coin that has been out for as many months as CLAMs has. Several hundred clams dug per day was a rough approximation I had come up with in the past.

There is no need to stop the digging but it must be limited so that millions of coins cannot get dug in a short period of time. Any low impact solution that does not limit the daily digging in some way will probably not save the coin. I can see it limiting the speed at which diggers can make money and increasing the value of the coin significantly. So diggers might be against it having to wait longer to dig all their coins.
But better CLAMS market cap be $1 million+ again and have to wait to dig your CLAMs than for them to be near worthless as the market cap drops under $100k.

So how long till this vote? And then how long after that for implementation.
hero member
Activity: 686
Merit: 502

yeah, there's transactions on them from 2011, was the CLAM initial distribution just between that year of may 13 to may 14? That would explain I guess.

No, if there was a balance on the address on the day then it would have been funded.

Ah, Well that would make even more sense, I think the balance is 0 for most of these wallets.

Thank you for your help.
sr. member
Activity: 332
Merit: 250
I like the clowns and the little dogs

yeah, there's transactions on them from 2011, was the CLAM initial distribution just between that year of may 13 to may 14? That would explain I guess.

No, if there was a balance on the address on the day then it would have been funded.
hero member
Activity: 1232
Merit: 738
Mixing reinvented for your privacy | chipmixer.com
running much faster now, forgot about conf files and nodes (been a few years)

Thank you.
or... you could just download the bootstrap file(s) up to the latest block
then synch & redeem & stake from that point
downloading the bootstrap probably will save your bandwith
hero member
Activity: 686
Merit: 502
Does this small red fail image come up when anyone else imports a wallet? is it just normal?

Were your addresses funded in May of '13?  This red icon is what I get when I import
wallets that weren't funded then.

yeah, there's transactions on them from 2011, was the CLAM initial distribution just between that year of may 13 to may 14? That would explain I guess.
sr. member
Activity: 332
Merit: 250
I like the clowns and the little dogs
Does this small red fail image come up when anyone else imports a wallet? is it just normal?

Were your addresses funded in May of '13?  This red icon is what I get when I import
wallets that weren't funded then.
hero member
Activity: 686
Merit: 502
When I try to import my wallet. One wallet I have is from 2011, the other 3 are 2012.

I get the below. It seems to freeze the client for a time, I assume this is when its importing and then nothing... Does this small red fail image come up when anyone else imports a wallet? is it just normal?

legendary
Activity: 1007
Merit: 1000
Hi All,

I have about 5000 Addresses from < 2014 that I have backed up from 2010 onwards. I want to check these all to see if they are in the initial distribution list.

I am quite handy with programming but wondering what the best way to check a large amount of addresses are?

Is there a list of all Bitcoin addresses that were sent clams? the initial distribution list? that I can check against

Regards,


Just dumping and importing the private keys from your addresses into the clam client is probably the simplest method I can think of - easy to script.

Correct me if I am wrong, someone, and there is an easier way.



Thank you,

Seems everytime I try and run the clam client it gets stuck on 35 weeks (syncing) even when I delete the database and start again. been trying to sync for two weeks now.

   You don't need the whole block chain to check addresses.  Up to block 10,000 should be fine.  Not sure if there is a newer bootstrap available.  Once you get to that point.   
hero member
Activity: 686
Merit: 502
running much faster now, forgot about conf files and nodes (been a few years)

Thank you.
legendary
Activity: 1316
Merit: 1000
Hi All,

I have about 5000 Addresses from < 2014 that I have backed up from 2010 onwards. I want to check these all to see if they are in the initial distribution list.

I am quite handy with programming but wondering what the best way to check a large amount of addresses are?

Is there a list of all Bitcoin addresses that were sent clams? the initial distribution list? that I can check against

Regards,


Just dumping and importing the private keys from your addresses into the clam client is probably the simplest method I can think of - easy to script.

Correct me if I am wrong, someone, and there is an easier way.



Thank you,

Seems everytime I try and run the clam client it gets stuck on 35 weeks (syncing) even when I delete the database and start again. been trying to sync for two weeks now.

Here is a current list of nodes which may help (http://www.blocktree.io/peers/CLAM/):

addnode=144.76.185.69
addnode=91.232.105.11
addnode=2a01:4f8:151:6347::2
addnode=176.9.113.75
addnode=45.79.151.194
addnode=88.198.207.8
addnode=168.235.150.242
addnode=109.236.85.42
addnode=192.241.224.61
addnode=162.243.198.51
addnode=192.99.32.187
addnode=74.207.230.61
addnode=104.236.69.34
addnode=2600:3c02::f03c:91ff:fe6e:e806
addnode=159.203.117.103
addnode=203.45.89.214
addnode=199.233.246.224
addnode=5.189.139.227
addnode=23.117.142.67
addnode=86.188.104.174
addnode=75.136.69.71
addnode=93.33.144.9
addnode=109.182.159.47
addnode=151.80.33.164
addnode=86.191.255.223
addnode=52.5.155.203
addnode=99.237.87.158
addnode=213.107.69.133
addnode=91.73.255.52
addnode=2602:306:c5b4:a190:1d42:b1e5:8ad3:adcd
addnode=78.62.83.197
addnode=2605:f700:80:800::4958:58fc
addnode=2605:e000:a901:be00:ac5a:6691:f0a6:d3d7
addnode=89.164.59.191
addnode=2606:a000:8880:e900:9066:ff21:6cb8:b507
addnode=65.182.72.222
addnode=107.170.174.86
addnode=72.10.216.141
addnode=98.238.201.128
addnode=2003:89:ee36:587:6d14:c7da:ef2e:5695
addnode=188.218.135.19
addnode=91.230.202.187
addnode=31.223.129.19
addnode=125.212.124.117
addnode=188.68.49.137
addnode=185.37.86.95
addnode=141.135.135.208
hero member
Activity: 686
Merit: 502
Hi All,

I have about 5000 Addresses from < 2014 that I have backed up from 2010 onwards. I want to check these all to see if they are in the initial distribution list.

I am quite handy with programming but wondering what the best way to check a large amount of addresses are?

Is there a list of all Bitcoin addresses that were sent clams? the initial distribution list? that I can check against

Regards,


Just dumping and importing the private keys from your addresses into the clam client is probably the simplest method I can think of - easy to script.

Correct me if I am wrong, someone, and there is an easier way.



Thank you,

Seems everytime I try and run the clam client it gets stuck on 35 weeks (syncing) even when I delete the database and start again. been trying to sync for two weeks now.
legendary
Activity: 1316
Merit: 1000
Hi All,

I have about 5000 Addresses from < 2014 that I have backed up from 2010 onwards. I want to check these all to see if they are in the initial distribution list.

I am quite handy with programming but wondering what the best way to check a large amount of addresses are?

Is there a list of all Bitcoin addresses that were sent clams? the initial distribution list? that I can check against

Regards,


Just dumping and importing the private keys from your addresses into the clam client is probably the simplest method I can think of - easy to script.

Correct me if I am wrong, someone, and there is an easier way.

hero member
Activity: 568
Merit: 500
https://bit-exo.com/?ref=gamblingbad
I've been asked to make my current thoughts clear.

I don't plan on making any kind of a new coin at the moment. SuperCLAM has stepped up and proposed a polling system (that I don't yet fully understand), and so I am willing to see how that pans out. If we as a community can use the forthcoming polling system to make changes that we want then I don't see the need for a new coin.

I'm not committing to never making a new coin, but I don't think it's likely that I will make one. CLAM is niche enough as it is without further splitting the community into two pieces.

Thanks for make that announcement. And if you plan in future to make a coin i hope u make a new snapshot, so we all can buy clam safetly.
hero member
Activity: 686
Merit: 502
Hi All,

I have about 5000 Addresses from < 2014 that I have backed up from 2010 onwards. I want to check these all to see if they are in the initial distribution list.

I am quite handy with programming but wondering what the best way to check a large amount of addresses are?

Is there a list of all Bitcoin addresses that were sent clams? the initial distribution list? that I can check against

Regards,
hero member
Activity: 724
Merit: 500



ClamChecker is closing  Sad

You mean no one used your shitty-looking site you threw together in an afternoon? Praising yourself about how you're "In it for the community" but as soon as the price goes down you close up shop?  Roll Eyes

I think we should keep discussing coin name ideas just so this idiotic parasite wastes all his money registering the domains for them.
Jump to: