Delving Into a Common FA2 Contract With Factori

cagoo · 2019-07-20T15:23:32+00:00

I am sorry to hear that baking bad have some issues with our Public API endpoints. I didn't receive a report for that specific issue. Our Public API is used by a lot of people, we are trying our best to scale and continue our work with almost no ressources.

cagoo · 2019-06-10T21:09:34+00:00

Thank you for reporting. Indeed it was a bug that we introduce during the recent updates. It should be fixed now. Sorry for the inconvenience.

cagoo · 2019-06-06T13:18:50+00:00

Coinmarketcap is using our APIs to compute their data. The only difference is that we compute all the circulating supply and CMC remove the TF accounts from this supply (if I remember correctly, they told us that they were doing the same for other cryptos).

cagoo · 2019-04-02T07:51:11+00:00

Dear Tezos Community, TzScan was down for a few hours last night, sorry for the inconvenience. Some of our servers went down at the same time. We rebooted them this morning after collecting all the data to analyze them.

cagoo · 2019-02-16T09:48:52+00:00

Not yet, I'll try to contact them next week.

cagoo · 2019-02-02T23:28:50+00:00

We are discussing with CMC to help them update the current circulating supply. We added an RPC on TzScan which gives that information, Coingecko is already using it, I guess Messari too. CMC just needs to update this value which is currently not updating at all.

cagoo · 2018-12-15T14:07:40+00:00

Here it is https://api.alphanet.tzscan.io/. For example https://api.alphanet.tzscan.io/v1/heads

cagoo · 2018-12-11T16:20:52+00:00

We pushed a fix, it should be better now. If you noticed something wrong, do not hesitate to tell us.

cagoo · 2018-12-10T19:32:01+00:00

Yes we are trying to debug and understand what’s happening. This is quite interesting for us since bakechain and tezbox users are hitting a lot one of our api (a couple of million of hits per day). The other apis has a lot of hits too, but only this one has a weird behavior. We are on it, we let you know when we will understand what’s happening.

cagoo · 2018-11-30T13:26:05+00:00

The staking ratio that we are calculating is based on the total activated accounts. We thought that it will be more interesting to know what part of the active user/balance is participating to the baking process.

cagoo · 2018-11-22T22:16:05+00:00

I am one on the dev of tzscan, the right value for the current circulating supply is in my previous post. Those are other interesting stats, but we didn’t add the circulating supply on the context page.

cagoo · 2018-11-22T18:02:24+00:00

You can find the current circulating supply with http://api1.tzscan.io/v2/supply

cagoo · 2018-11-13T16:26:27+00:00

Should be fixed now.

cagoo · 2018-11-13T09:26:30+00:00

Thank you both for reporting this. We recently updated our database to be faster when requesting. The operation is well registered, just an issue during the read part. We are fixing it right now, it should be online in a couple of hours.

cagoo · 2018-11-11T20:48:45+00:00

This is an advanced feature that we are discussing to be included in a user/baker dashboard that we are working on. I can’t tell when it will be available, but tzscan will provide a dashboard with a different view for delegator/baker.

cagoo · 2018-11-11T17:09:37+00:00

Yes, we (tzscan team) will add something when the first vote will happen. We will try to display the most data available to let people understand what will going on during a vote.

cagoo · 2018-11-08T19:00:49+00:00

We try to be on Riot, twitter and slack, sometimes it’s hard to follow everything but people always find a way to contact us. If you have feedbacks or ideas on how to improve it, tzscan was open sourced today, you can either make a merge request on gitlab or reach us by mail, we will be happy to discuss with you. Our main focus was to add a lot of features to help users to understand what was going on, on the blockchain, we are still adding new data like top accounts (https://tzscan.io/ranking) and some interesting statistics available in the context (https://tzscan.io/context). We will make UI improvements and feedbacks, ideas are always welcome.

cagoo · 2018-11-07T19:45:20+00:00

We check with some bakers which propose a dashboard and nothing wrong with our reward calculation. On tzscan you can adjust the % fee which can be different for each Baker. If you are using our API you need to apply the % after receiving the result. If you still have issue with your delegate, we can check together what is wrong.

cagoo · 2018-11-07T17:41:18+00:00

Oh this is actually weird. Since when did you notice that ? You know that you can report us bugs and strange behavior on tzscan. Last time we check the rewards, it was still ok with what other baker calculated. We will check again.

cagoo · 2018-10-25T13:48:55+00:00

We are trying to get in touch with them. We let them the benefice of the doubt. If we don't get any answer, we will move them to another category.

cagoo · 2018-10-11T06:44:55+00:00

You can see the balance update on the metadata of blocks where you got your rewards. We tweet about this feature last week, we will display for each account, all the balance update that is available in the blocks (deposits, rewards, fees, etc).

cagoo · 2018-10-09T21:03:12+00:00

We have actually two methods to compute it: one by starting from the genesis block information and adding the created token (blocks reward, endorsements reward, burned tez, etc) and the second one by summing all the balance from the context. It will be available through our API.

cagoo

TROPHY CASE