Pages:
Author

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

legendary
Activity: 4004
Merit: 1250
Owner at AltQuick.com
Your wish is my command!

Quote
It's currently syncing

I just updated the bootstrap.dat file.

It goes up to block 2623100 which was staked on Tue Jul  2 23:23:44 UTC 2019.

See https://bitcointalksearch.org/topic/m.9772191 for details.

Could you pass that on to whoever it is you were quoting?

Thanks for everything you do doog.
jr. member
Activity: 80
Merit: 1
FreiExchange Clams wallet has completed syncing.  Please come fill up the order books.

legendary
Activity: 2268
Merit: 1092
But a subsequent withdraw attempt now has the status "Complete: Error"

Following up: the response was a lot more quick this time, although all they did was cancel the failed withdraw.

Happy to say that a subsequent attempt was successful and the tx hit the network within about 15 minutes! Smiley

Was kind of wondering if we were going to get stuck in a loop, with them just cancelling each failed attempt. I'm a bit concerned about the future of CLAM there because the replies ignore the fundamental issues. Do other coins at Poloniex have problems like this?
legendary
Activity: 2940
Merit: 1333
Your wish is my command!

Quote
It's currently syncing

I just updated the bootstrap.dat file.

It goes up to block 2623100 which was staked on Tue Jul  2 23:23:44 UTC 2019.

See https://bitcointalksearch.org/topic/m.9772191 for details.

Could you pass that on to whoever it is you were quoting?
legendary
Activity: 2268
Merit: 1092
Quote
It's currently syncing[...]

Syncing? That word sends a chill through the heart of any long term CLAM user!  Cheesy
jr. member
Activity: 80
Merit: 1
Welcome to FreiExchange. Thanks for your intrest in our modest exchange. We are happy to have you.

Please also join our Telegram group. It is easy to chat with FreiExhange admin there and the rest of our community.

https://t.me/freiexchange

legendary
Activity: 4004
Merit: 1250
Owner at AltQuick.com
just list here you will be fine n00b Wink r.i.p. polo haha ===>

https://freiexchange.com/market/BTI/BTC

Your wish is my command!

Quote
It's currently syncing, market is in place, deposits will open as soon as we have it up to date.

https://freiexchange.com/market/CLAM/BTC

I like that they offer free trading, but charge for withdraws.  Kind of an interesting business idea!

I'm expecting a min investment of at least $50 million from you Gembitz.  Roll Eyes Kiss
legendary
Activity: 2268
Merit: 1092
My ticket was updated yesterday to inform me the withdrawal had completed. It took over 2 weeks to reach the blockchain.

But a subsequent withdraw attempt now has the status "Complete: Error"

Welcome to a day in the life.

Yeah, must be very frustrating. When I opened the first ticket I asked if anything was being done to fix what appears to be a ongoing problem affecting multiple customers, but the only replies were a couple of form responses to say the transaction request was being escalated, and then one saying it had been completed.
legendary
Activity: 4004
Merit: 1250
Owner at AltQuick.com
Re: Poloniex CLAM withdraw problems

I'm still waiting on a ticket re failed withdraw which I opened on 26th June.

My ticket was updated yesterday to inform me the withdrawal had completed. It took over 2 weeks to reach the blockchain.

But a subsequent withdraw attempt now has the status "Complete: Error"

Welcome to a day in the life.
legendary
Activity: 2268
Merit: 1092
Re: Poloniex CLAM withdraw problems

I'm still waiting on a ticket re failed withdraw which I opened on 26th June.

My ticket was updated yesterday to inform me the withdrawal had completed. It took over 2 weeks to reach the blockchain.

But a subsequent withdraw attempt now has the status "Complete: Error"
legendary
Activity: 2968
Merit: 1198
Does this mean there won't be a way for people to short CLAM?

It seems highly unlikely any other exchange will offer that any time soon. You can always borrow OTC though, if you can find a lender.
legendary
Activity: 4004
Merit: 1250
Owner at AltQuick.com
"Beygency: @masecase this is correct. others that will be removed are factom, clam and bts"

Appears CLAMS is being removed off Poloniex July 8th.  (not 100% yet)

I think I was wrong about the delisting... I believe I heard half of this conversation:

"Additionally, it seems Poloniex will effectively remove four margin trading markets. That includes CLAM, but also BitShares, Factom, and Maidsafe." https://themerkle.com/clam-market-crash-costs-poloniexs-bitcoin-lenders-16-202-of-their-balance/

Maybe that is what is happening on July 8th... *facepalm* sorry about that.

Does this mean there won't be a way for people to short CLAM?
legendary
Activity: 4004
Merit: 1250
Owner at AltQuick.com
Maybe Poloniex isn't going to delist us... I figured they were going to announce it last week.

I think they only need to give us 7 days... so if they delist us on the 8th... they could announce on Monday (tomorrow).

Also:  https://www.reddit.com/r/Clamcoin/comments/c3no0r/why_is_clamd_taking_100_of_cpu_for_the_past_month/
legendary
Activity: 2254
Merit: 1290
Is there a Clams TechSupport FAQ or Wiki currently, where these kind of tips and techniques are collected?
Not that I'm aware of (not that that means anything). And I'm hard-pressed to conjure up something that isn't already covered in the application documentation. Also, I think there's enough to take in already without adding edge-case technical administrivia. This particular example is constrained to a specific userland area - that of casual appeal to the community for assistance with trivial issues of compilation instead of RTFM, where the instructions are copy'n'pasta-ready:

https://github.com/nochowderforyou/clams/blob/master/doc/build-unix.md#berkeley-db

If the official docs are unread, that's just as likely to apply to any centralised resource.

Anyway, the issue of binary compatibility of wallet.db is only really an issue for distributors of proprietary OS applications (OS X and Windows - Linux users are free to choose which libraries are linked to) and, strictly speaking (this is cryptocurrency), the provision of binaries introduces security issues. Reflecting this, there is a supported/ing build system (https://github.com/nochowderforyou/clams/blob/master/doc/gitian-building.md) which is deterministic i.e. a hash of the resulting code binaries (Linux, OS X, Windows, depending on selection) will always be the same, so it can be cross-referenced against the published hash. All very open and verifiable.

Cheers

Graham
member
Activity: 67
Merit: 10
You will need to download 4.8, compile it separately and adjust the build process to use the 4.8 headers and libs.

I typically install a newer version and configure using --with-incompatible-bdb. Package "libdb5.3++-dev" or whatever's available.

It means my wallet.dat files won't work with clients that use 4.8, but I never use 4.8 and never share wallets, so I don't care.

It's a UX/UI issue. It's possible to lose access to a wallet by failing to back it up before switching to a later non-backwards-compatible client which, if for some reason proves undesirable to the user, causes them to switch back to the old client. That's when they discover that the new client automatically upgraded their wallet to the new db format which cannot now be read by the old client. That's why the advice (for distributed binaries, i.e. OS X/Windows) is to link against 4.8.

Great support, dooglus, Graham, et.al.

Is there a Clams TechSupport FAQ or Wiki currently, where these kind of tips and techniques are collected?  I see similar types of questions recur.  It would be great to pull this expertise into a ready reference for new users and investors.  There is lots of expert info in the pages here, but not so easy to search.
member
Activity: 67
Merit: 10
My analysis of recent Clam market situation, does it sound about right, anyone have additional or alternate info:

A huge amount of Clam coins were forced on the market by margin calls at Poloniex, in a tiny amount of time, which sold thru all the buy orders.  Something like 300,000+ Clams sold in hours, that's a staggering 10% of the entire circulation,  over $3M in hours versus avg daily volume $20k-200k.  I think far beyond what any whale controls. 

Was not news or fact-driven event, not even a real market event by actual human trading, it was artificial, basically an accident, a glitch.

Because of the margin pool, after the initial trigger sale, it went into an automatic feedback loop: price drop triggers margin calls to sell, which drops the quote price more, which triggers more margin calls, etc.  Many of the investors didn't even intend to sell, it was automatic.  And some or even most of them had profits, and are obviously Clam traders, holders and enthusiasts, so they might well be buying back in now,  except their accounts are frozen while Poloniex sorts it all out.  The margin calls likely extended to other coins in the overall pool, which probably had related effects, resulting in the overall 1800 btc margin lossage figure (i.e. that figure seems way more than can be just from Clams)

So it will take a while to sort out. Right now the trading is very light, people who need to sell or  aftershocks, everyone obviously very nervous and wondering wth happened.

It seems this unfortunate "glitch", was triggered by either a naive whale (who would have profited a lot more by sensibly managing their position), or more likely imo, professional manipulators, who intentionally played the margin exposure and algorithms. It's a heckuva glitch, but I think Clams will recover; whether in days or months, who knows.

*

The reality is, there was no negative news or event, Clam coin functions extremely well, fast and reliable, with ongoing development and many features builtin and service sites offering free anonymous wallets, escrow, games, etc, and is an excellent basic money coin.  Plus the Eco-sensible stake mining, that invites and rewards anyone to support the network, participate in mining without a huge power/computing cost.

Seems to me we just saw several months of steady organic growth, reflecting growing awareness and exciting developments like at FreeBitcoins for example, the Swap feature effectively adding more Anon/Privacy options, and easy convenient access for people who don't want to bother with exchange trading.  (really great contribution BAC, Xploited)  I can see that enthusiasm coming back quickly, once the hysteria dissipates.

The good news is, if the trigger was a whale, that's one less killer whale now,  and if manipulators,  at least Poloniex has turned off the margin, so it will be much harder to repeat.

legendary
Activity: 2254
Merit: 1290
It means my wallet.dat files won't work with clients that use 4.8, but I never use 4.8 and never share wallets, so I don't care.
I'm compelled to nitpick, sorry.

It's a UX/UI issue. It's possible to lose access to a wallet by failing to back it up before switching to a later non-backwards-compatible client which, if for some reason proves undesirable to the user, causes them to switch back to the old client. That's when they discover that the new client automatically upgraded their wallet to the new db format which cannot now be read by the old client. That's why the advice (for distributed binaries, i.e. OS X/Windows) is to link against 4.8.

It may be an edge case and it may be perceived as a userland issue but I categorise it as a development UX/UI issue because of the underlying loose assumption of technical competence on the part of the user without an accompanying specification of the minimum level of technical understanding required to perform basic wallet/chain maintenance operations. (A principle lucidly expressed by my father as: "If a man doesn't understand, it's because he hasn't been told properly.").

Cheers

Graham
legendary
Activity: 2940
Merit: 1333
You will need to download 4.8, compile it separately and adjust the build process to use the 4.8 headers and libs.

I typically install a newer version and configure using --with-incompatible-bdb. Package "libdb5.3++-dev" or whatever's available.

It means my wallet.dat files won't work with clients that use 4.8, but I never use 4.8 and never share wallets, so I don't care.
legendary
Activity: 2254
Merit: 1290
Anybody made client working on ubuntu 19?

Anyone? I have issue installing DB 4.8 on Ubuntu 19.
Your question  was overly casual and didn't really contain enough information to motivate me to find out why you were asking (I've learned to be thrifty with my time). If you had made some/any effort to describe your problem, that might have helped.

You will need to download 4.8, compile it separately and adjust the build process to use the 4.8 headers and libs.

Cheers

Graham
jr. member
Activity: 238
Merit: 5
Anybody made client working on ubuntu 19?

Anyone? I have issue installing DB 4.8 on Ubuntu 19.
Pages:
Jump to: