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

Hi.

Why in new blockexplorer dont work search by btc, ltc and doge address?

If the outputs are unspent then obviously you can't link them to the transaction that spent them, but for the spent outputs you can. See how blockchain.info does it when you enable 'advanced' mode by clicking somewhere in the lower right corner.


It's Chromium v40 on a 1366x768 screen.

I made a new transaction with a view to taking a screenshot for you. When I visit its page, it's blank:



It turns out that's what gets displayed for any unconfirmed or non-existent transaction. I had to wait for it to confirm before it would show up properly, and editing the txid at all made it show the page without details again. Would be better to show an error message I think if you're not going to support unconfirmed transactions.

Once it had confirmed, I see the too-wide page:



I resized the window to see when it would change the layout. I could make it this narrow before things rearranged themselves:



At that point things are overlapping pretty badly.


People can encode arbitrary messages into addresses, transaction amounts, etc. and have them show up in any block explorer. I doubt CLAMspeech is legally any different than that. I'm thinking of addresses like 1BitcoinEaterAddressDontSendf59kuE, etc.

Wondering if there are any potential legal issues with a block explorer website displaying arbitrary clamspeech text. I guess this goes for any coin which supports in-transaction comments.

The thing is, and this applies to some of your other suggestions also, the explorer is designed to be useable with a number of different coins. As such some of the unique features for a particular coin are not taken into consideration at this stage. I know thats not a perfect solution, bit of a 'fox of all, master of none' situation.


I have now added the burn address which is then taken into consideration when showing the total number of available coins. You can now see 'Spendable Coin Supply'.

I have had a similar discussion with the Sapience community in terms of showing the burn address. My view is that the explorer is simply showing what it sees in the client, without manipulating it too much. I think noting the burn address and number of coins that are not in circulation to be relevant. Again, its somewhat of a one size fits all system, with the possibility to change in the future.


Done.


No, I am happy to hear suggestions / constructive criticism.

I have now made transactions clickable (linked) for inputs on a transaction page. Obviously this is only relevant for inputs though, as outputs are part of the transaction being viewed.

Would be interested to know what browser and screen size you are using that is causing the txids on the transaction page to push right. In theory, unless on a very small screen, like a phone or something, the design should be responsive and not push right (at least on all my screen it does not push right).


Hmm, upon re-reading your edit 4 I realise that I cannot use my usual system to show 'Spendable Coin Supply' as the client already removes the burnt coins from the coinsupply value (so have reversed that change). Usually if there are burnt coins like with Sapience (http://www.blocktree.io/e/XAI) the system deducts the burn address coins from the money supply, and then on the rich list the burnt coins are shown but without a percentage of total supply and labeled as burn coins. I will have a think about how this can be changed to accommodate the Clam situation better - it really only affects the rich list at the moment though as the client already takes into consideration the burnt coins in the 'moneysupply' value. I am flat out at the moment on another project but when I get some time will find a solution to this.

And lastly, thank you for the generous donation 

That's great, thanks! I've been waiting for a reliable CLAM block explorer, and this looks like it might fit the bill.

Please accept a token of our gratitude from JD.

I just noticed you don't display the "CLAMspeech" data that is part of each transaction, and also don't seem to show unconfirmed transactions. Neither is a big deal, but both would be useful additions.

Edit: one other wrinkle maybe worth noting is that the "money supply" is kind of weird for CLAM. Millions of addresses were given 4.6 CLAM each in the initial distribution, and most of them have never transacted since. While those are part of the money supply in some sense it's probably more interesting to only consider coins that have at some point been active.

The "getinfo" RPC call includes these lines:

    "moneysupply" : 15145821.13048927,
    "digsupply" : 317403.40414506,
    "stakesupply" : 371419.72641731,
    "activesupply" : 688823.13056237,

"activesupply" is the sum of "digsupply" (all the 4.6 CLAM initial distribution amounts that have ever moved) and "stakesupply" (all the coins created by staking blocks), and is probably a more interesting statistic to use.

Edit2: and since I'm picking nits, it would be useful if the "Summary ... Block Height   475772" on the front page was a link to the latest block. Currently I have to scroll down to the block list before I see any links at all.

Edit3: I hope all this is seen as useful rather than as bitching... but I'd like to be able to click through a chain of transactions. Currently when viewing a transaction the inputs and outputs link to /address/ pages, but it would be more useful to have them link to the pages for the individual transactions they came from / went to. If that was done, there would be no need to show the full txid in text next to each input, since we could just copy the destination URL if we wanted that information, and the page would then fit on my screen without sideways scrolling (some txids take more horizontal space than others, and the longer ones make the whole page a little wider than my screen).

Edit4: The rich-list lists the official burn address (xCLAMBURNXXXXXXXXXXXXXXXXXXX1HaxZH) as being the 2nd richest address. The client considers coins at that address to be burned, and doesn't include them in the moneysupply. See src/main.cpp:


It would be better not to show that address in the rich-list. They are coins that were left over after the developers did the initial distribution. The address is clearly one that was made up without anyone knowing the private key.

Khashier was redirected to clamsight to preserve search engine indexes.
It may take a little while to get it set up, but I see no reason that khashier could not be operated as well.

---

- Added a notice to users concerning the recent requirement of First/Last Name and Country of Origin to use the Poloniex platform.
- Margin trading added to Poloniex - Please request that they add CLAM to the margin trading platform!

In what order does clamsight list the transactions for an address?

http://clamsight.com/address/x8Smd9f7FPDKts2Rfd33kvouJcgoJ5BrHg is loading for me now, but the first three transactions listed have 109, 7077, and 5489 confirmations, in that order. The oldest of the three transactions is in the middle. Seems like a strange way of doing things:

Probably related to the "double-spend" issue I reported on the last page, visiting:
  http://clamsight.com/address/x8Smd9f7FPDKts2Rfd33kvouJcgoJ5BrHg
seems to hang when loading transactions. I never see any of the 8 transactions it claims exist on that address.

Edit: would it be possible to have khashier back as an alternative block explorer? It's the only vaguely functional block explorer for CLAM I knew of, and now it forwards to CLAMsight, which while being a whole lot prettier than khashier is also a whole lot more broken in various ways.

Of the two, khashier was much more useful when I actually needed to explore the blockchain.

The bitcoin wallet can be imported within the CLAMclient like this: http://clamclient.com/#/import

To import a private key, you can type this into the debug window: importprivkey yourprivatekey
Like this: http://bitcoin.stackexchange.com/questions/5941/how-do-i-import-a-private-key-into-bitcoin-qt

How can I claim CLAM if I have a bitcoin wallet or private key?

Here's a .ai of the CLAMs logo: https://www.dropbox.com/s/szhly00g5eun7l0/clamLogo%20%281%29.ai?dl=0

Thanks Dooglus - I got it working by adding a fee of 0.001 CLAM. Even after cleaning up around 7000 dust transactions in 150 or so transactions it only cost 0.15 CLAM.

Hello Clams!

Does anyone have any clam media assets like logos I could use ? , or can point me to them. If not, someone PM who knows how to design around CLAM.  Thanks!

I collected together the changes since the last release, tagged a new release, and put together the release notes:



xploited is taking a look at it, so hopefully binaries will be available soon.

It won't be a mandatory upgrade. There's nothing that forks the chain in it.

The most notable new feature is that you will now be able to split your balance into multiple pieces quickly and easily without resorting to using raw transactions.

Example:


That sent 31 separate outputs of size 25 CLAM to a single address, and sent change to a new address, as always. It sets the fee automatically too:

At least 3 different parties think they are going to redo y'alls website. Is it possible to open source it maybe?

I know at least Dandi and V1rt were under the impression they where going to work on it.

People can see an example of what Dandi can do at www.Clamcoin.org.  I haven't seen any of v1rts work ever.

I don't think Clamcoin.org is perfect, but I do believe it is a cleaner lay out ect.  I also like the domain name WAY more.  Not interested in removing the Google ads.  We do link your site however and I know Dandi is fine if you use the sites lay out on ClamClient.com, but remove the Google ads.  If you chose to do that it'd be cool if you reference Clamcoin.org as where you got it from since we are reference you as the official site.

The problem with Clamclient is that no one remembers "client" (at least at this point.)  Hell, I even have to think a little to remember it. I do understand the reasoning behind idea behind it.

There has been some intention of re-branding CLAMs for quite a while.
Art/Media assets, website, client, etc. could use a more professional and memorable image.

Does anyone have any opinions, ideas, or thoughts on the matter?

A simple fix; but it fixes a thorn that has been re-occurring for sometime.

Nice job, dooglus.

So I forgot about this issue until whiskey brought it up again today in the Just-Dice chat. I don't use the QT interface myself, so it was easy to forget about.

I finally found and fixed the bug. It was just a display issue. See https://github.com/nochowderforyou/clams/issues/188 for details.

It will be fixed in the next release of the CLAM client.

Size is all that matters, once an output is old enough (510 confirmations since last stake, 4 hours since last transaction). Chance of staking is proportional to size in CLAMs.

Making your outputs larger will increase their chance of staking. But you'll presumably have less of them. Two outputs of size 5 each have pretty much the same chance of staking as a single output of size 10.


Let's look at a contrived example:

An output of size 10 when there is 500k trying to stake will have a 1 in 50k chance of staking each minute. That's a probability of 0.00002

If you split that into two outputs of size 5, each one will have a 1 in 100k chance of staking each minute. That's a 0.99999 chance of not staking for each. So the chance that neither will stake in any given minute is 0.99999 squared, ie. 0.9999800001, and so the probability of 1 or more staking is 0.0000199999. You have a very slightly smaller chance of staking by splitting, but you have a very slightly bigger chance of staking twice in the same minute. For all practical purposes your chance hasn't really changed.

The big advantage of splitting is that when you do stake, only 5 of your 10 CLAMs get frozen for 8 hours while the block matures, and the other 5 can carry on staking.


I think that's pretty normal. You have 2.1k out of 557320 (current network stake weight according to my client - it's just a guess).

You can expect to stake:

>>> 2.1e3 * 1440 / 557320
5.425967128400201

per day, with pretty high variance. 1 to 10 sounds right.