BitShares Forum
Main => General Discussion => Topic started by: svk on August 02, 2014, 06:45:06 pm
-
For those of you who've missed me talking about my block explorer website, here's an official announcement. I'll take feedback and suggestions in here, and try to keep a list of things people ask me to implement.
The site can be found here: http://www.bitsharesblocks.com
In the block explorer currently you can check incoming blocks, search for any block and check the transactions for that block.
In the delegates listing you'll get a list of all delegates with votes for > 0, and you can search the list by delegate name. You can also click on a delegate to take you to a page with some more info on that delegate, more info will be coming but right now you'll get a list of all votes for that delegate, by block.
Current issues:
Performance of the delegates list is not that good, it's an angularjs issue with big lists, might need to do it differently.Delegate info page layout isn't great due to time constraints!Latencies are objective and can be affected by my server, take the values with a grain of saltFound a bug that was impacting syncing and therefore latencies, fixed
Requested improvements:
Graphics of delegates performance: Still want to do this, might get to it this week (W36) Trend info for delegate's ranking: DoneFilter active feeds
-
+5%
are you going to publish the source code?
-
nice tweak for web wallet to be explorer
-
Nice +5%
-
+5%
are you going to publish the source code?
Thanks. To be honest the code isn't in any shape to be open-sourced, I'd be happy to answer questions though if anyone needs help. I'm using the MEAN stack to build it, polling a wallet daemon with Nodejs, post-treating where necessary and then storing everything with Mongo, serving it up with Express, and the website is done using angularjs.
-
The links at the bottom use the xts: URLs.... but that is for the TEST network.
you want to replace xts with btsx: in your links at the bottom.
-
The links at the bottom use the xts: URLs.... but that is for the TEST network.
you want to replace xts with btsx: in your links at the bottom.
Thanks, was just going by the wiki, didn't think to update the scheme!
-
nice thx
-
+5%
are you going to publish the source code?
Thanks. To be honest the code isn't in any shape to be open-sourced, I'd be happy to answer questions though if anyone needs help. I'm using the MEAN stack to build it, polling a wallet daemon with Nodejs, post-treating where necessary and then storing everything with Mongo, serving it up with Express, and the website is done using angularjs.
Thats the exact same setup i plan to use for the charity delegates backend .. however i can use some help coding. ... i already managed to build a nodejs rpx proxy and some basic express/jade/angular page ...
Once i am at a stage where this thing can be used i probably push it to github and can use some further help ..
I'd really like to setup a team that stands behind the charity delegates .. it will probably soon be to much work to be handled by me alone ..
-
whenever i click on a block none of the transaction details are viewable...
-
whenever i click on a block none of the transaction details are viewable...
Yea it looks like the transactions aren't getting saved properly atm, but I'm at the airport so won't be able to look into it before tomorrow I think :(
-
whenever i click on a block none of the transaction details are viewable...
Think I got it fixed now, let me know if you encounter any other bugs! I'm back to vacationing! ;)
-
The site can be found here: http://www.bitsharesblocks.com
Nice, but how about adding the feature to show the balance for a particular address? That's what people most commonly do with blockchain.info
-
The site can be found here: http://www.bitsharesblocks.com
Nice, but how about adding the feature to show the balance for a particular address? That's what people most commonly do with blockchain.info
Thats not really possible with titan, since it creates a new stealth address for every transaction.
-
The site can be found here: http://www.bitsharesblocks.com
Nice, but how about adding the feature to show the balance for a particular address? That's what people most commonly do with blockchain.info
Thats not really possible with titan, since it creates a new stealth address for every transaction.
Im not fully up to speed on Titan yet, but you can still list all the addresses that you created yourself correct? So what's the issue with listing the balances with each address?
The reason I ask for this feature is that I still havent moved my stake into a new address, because the gui wont tell me which address has the stake in it. I imported one of my AGS addresses and moved 1 XTS as a test, which worked but now after importing my other AGS addresses the gui wont tell which funds are where.
I feel like the gui is trying to hide details from me, which is annoying.
-
The site can be found here: http://www.bitsharesblocks.com
Nice, but how about adding the feature to show the balance for a particular address? That's what people most commonly do with blockchain.info
Thats not really possible with titan, since it creates a new stealth address for every transaction.
Im not fully up to speed on Titan yet, but you can still list all the addresses that you created yourself correct? So what's the issue with listing the balances with each address?
The reason I ask for this feature is that I still havent moved my stake into a new address, because the gui wont tell me which address has the stake in it. I imported one of my AGS addresses and moved 1 XTS as a test, which worked but now after importing my other AGS addresses the gui wont tell which funds are where.
I feel like the gui is trying to hide details from me, which is annoying.
Try wallet_account_balance in the console
If that shows the same issues then try wallet_rescan_blockchain.
Do you have a delegate in your wallet?
-
The site can be found here: http://www.bitsharesblocks.com
Nice, but how about adding the feature to show the balance for a particular address? That's what people most commonly do with blockchain.info
Thats not really possible with titan, since it creates a new stealth address for every transaction.
Im not fully up to speed on Titan yet, but you can still list all the addresses that you created yourself correct? So what's the issue with listing the balances with each address?
The reason I ask for this feature is that I still havent moved my stake into a new address, because the gui wont tell me which address has the stake in it. I imported one of my AGS addresses and moved 1 XTS as a test, which worked but now after importing my other AGS addresses the gui wont tell which funds are where.
I feel like the gui is trying to hide details from me, which is annoying.
Try wallet_account_balance in the console
If that shows the same issues then try wallet_rescan_blockchain.
Do you have a delegate in your wallet?
Thanks I will try that soon.
I havent registered a username if that's what you mean. Im happy just using addresses for now.
-
The site can be found here: http://www.bitsharesblocks.com
Nice, but how about adding the feature to show the balance for a particular address? That's what people most commonly do with blockchain.info
Thats not really possible with titan, since it creates a new stealth address for every transaction.
Im not fully up to speed on Titan yet, but you can still list all the addresses that you created yourself correct? So what's the issue with listing the balances with each address?
The reason I ask for this feature is that I still havent moved my stake into a new address, because the gui wont tell me which address has the stake in it. I imported one of my AGS addresses and moved 1 XTS as a test, which worked but now after importing my other AGS addresses the gui wont tell which funds are where.
I feel like the gui is trying to hide details from me, which is annoying.
Try wallet_account_balance in the console
If that shows the same issues then try wallet_rescan_blockchain.
Do you have a delegate in your wallet?
Thanks I will try that soon.
I havent registered a username if that's what you mean. Im happy just using addresses for now.
Like puppies said I don't think it's possible to determine the balance of a given address. I think you can see who sent a transaction and I'll get that added to my info, but that's all I think.
-
+5%
are you going to publish the source code?
This should be built into the Bitshares wallet.
-
the issue is: i don't allways have my wallet around :) but with a dedicated service i can still check .. i.e. if there are lots of high-value transactions .. or if my delegates is still up&running
also outsiders can get in touch with the blockchain without installing a wallet .. just for learning about it
-
I'm back from vacation and getting some more work in on the site. I did an overhaul of the block and delegate view, and added back and forward buttons to the delegate view so you can browse through the ranks.
Will most likely work on rank histories next, although the whole bitUSD and asset frenzy might steal some of my time.
Feel free to ask for stuff that you feel is missing, and let me know if there are any other issues bothering you, like performance for example.
-
Among various other optimizations, I've got rank changes added today! I calculate the changes for the last 24 hours as well as the last week, they're floating windows updated every 2 minutes, based on the number of votes each delegate had at that point in time. Any delegate saying "n/a" was not yet created at the time, they'll get numbers once they age a bit more :)
Oh and last night I added a simple Asset Trade overview in the single block view, if there are USD transactions or any other asset transactions included in the block, you'll see them there.
Now I think I need to get back to my dayjob for a bit, lol.
-
the change is a very useful feature .. thanks
-
I've added some more improvements today:
- Backend optimisation of api calls
- Account names and addresses shown registration transactions
- Shorts added to block info
- Vote counts added
- Various front-end bug fixes
I passed 100 visitors for the first time yesterday, thanks for using my site :)
-
Another update, I've added some interesting things today and yesterday:
- Asset overview: number of feeds, feed price averages, current supply ++
- Network health overview
- New home page!
- Home page has various stats:
- Number of accounts, number of new accounts last day and week
- Number of delegates, number of new delegates last day and week
- Number of blocks, number of blocks with transactions and empty blocks
- Recent missed blocks with delegate names
- Recent registered account names
- and more..
If you're interested in any stat in particular give me a shout!
-
Good Job! Keep it up!
-
looks awesome!
-
Thanks for the encouragement :)
Yesterday I added sorting to a few of the columns in the delegates table as well as the asset tables. This means you can now sort for the most reliable delegates, or the ones who climbed the most over the last week or day for example. In assets you can sort by bid depth, ask depth and more.
If anyone had issues connecting over the last hours, it's because I updated the site to HTML5 pushstate, and it caused some issues with the server. It's all fixed now though, but what this means is that all the old links to a given block for example won't work because I've removed the ugly /#/. I also changed the asset links from using the id to using the symbol, so it's now "id=USD" instead of "id=22":
http://bitsharesblocks.com/assets/asset?id=USD
-
Your site is very well done. I ended up clicking around on it for some time.
-
Nice job! Thanks! :)
-
Very useful - well done ! Thanks +5%
-
Good job. You may want to show number of fresh/current feeds as opposed to total published feeds in Assets table. Feeds expire after 24 hours.
-
Good job. You may want to show number of fresh/current feeds as opposed to total published feeds in Assets table. Feeds expire after 24 hours.
Yea i realized that earlier too, for now I've added the current status, ie are there enough recent feeds. I'll see if I can add a on/off filter tomorrow to show only active feeds.
In other news, I moved the site and btsx client to a VPS in New York today, so downloads might be faster for those of you over there. Don't think it was slow anyway though? I also streamlined all the api calls and my database while I was at it so things might be a little quicker.
-
Good job. You may want to show number of fresh/current feeds as opposed to total published feeds in Assets table. Feeds expire after 24 hours.
I've now added a filter so that only active feeds are shown. You can toggle it with a checkbox, but it's on by default. Feeds are now also sorted by date by default, from most recent to oldest. We currently have 68 fresh feeds for USD:
http://bitsharesblocks.com/assets/asset?id=USD
I also added slot record history to the delegate info, you can now see a delegate's performance over his last 50 production slots.
-
Looks like the client is down on your server :(
-
Looks like the client is down on your server :(
Hm don't think it's been down today, been working on the frontend a bit and would've noticed.
However, sometimes when I push a new version of the frontend to the server the API calls get refused by Chrome due to http://en.wikipedia.org/wiki/Cross-origin_resource_sharing (http://en.wikipedia.org/wiki/Cross-origin_resource_sharing) for a little while, it's a strange bug I noticed. If you check the console you might see error messages related to that if the site appears to be down. Try closing it and reloading, should work again rapidly.
-
Seems it didn't like my work VPN. Oh well, who needs to do work anyway :).
Sorry for the false alarm. BTW this is what I was seeing:
(http://i.imgur.com/QKt9c9L.png)
-
I had same issue yesterday.
It was gone after few minutes.
UI improvements are clearly visible. I like it. Keep it up!
-
I had same issue yesterday.
It was gone after few minutes.
UI improvements are clearly visible. I like it. Keep it up!
Indeed. Site looks fantastic.
-
Very useful site, will be using it quite a bit. Also the design is simple but clear and easy to use. Thanks for the good work.
-
Since you're already gathering the data about blocks and transactions within the blocks....how hard would it be to add a graph that shows volume for each asset? It would be cool to know when bitUSD, bitCNY, etc. are in high volume periods.
-
Hey svk,
You might already know and be working on it, but it looks like your site's connection to the blockchain is down as all areas appear to be not populated with data.
I tried it from 2 different sources so I don't believe the problem is on my end.
Just a heads up in case you weren't aware.
Thanks.
-
Hey svk,
You might already know and be working on it, but it looks like your site's connection to the blockchain is down as all areas appear to be not populated with data.
I tried it from 2 different sources so I don't believe the problem is on my end.
Just a heads up in case you weren't aware.
Thanks.
the api seems to be working http://beyondbitcoinx.net/delegates/bitsuperlab/
-
Hey svk,
You might already know and be working on it, but it looks like your site's connection to the blockchain is down as all areas appear to be not populated with data.
I tried it from 2 different sources so I don't believe the problem is on my end.
Just a heads up in case you weren't aware.
Thanks.
I had the issue when I was on my work's vpn. Soon as I killed it the site populated correctly. Not sure what's up with that.
-
Hey svk,
You might already know and be working on it, but it looks like your site's connection to the blockchain is down as all areas appear to be not populated with data.
I tried it from 2 different sources so I don't believe the problem is on my end.
Just a heads up in case you weren't aware.
Thanks.
I had the issue when I was on my work's vpn. Soon as I killed it the site populated correctly. Not sure what's up with that.
Hmm Ok weird, it was working on my VPS but now won't load any data anymore, I double checked on my work computer and got the same no data, I'll remote to my home computer and test there as well. Thanks.
Edit: It's randomly working on my VPS again.
-
Hey svk,
You might already know and be working on it, but it looks like your site's connection to the blockchain is down as all areas appear to be not populated with data.
I tried it from 2 different sources so I don't believe the problem is on my end.
Just a heads up in case you weren't aware.
Thanks.
Hey, thanks for the heads up but like the others are saying it does work, it's just a strange bug related to cross origin sharing, which means your browser is blocking the data sent from my back end since it's not on the same domain as your computer.
My http headers are all OK to handle this, but it seems sometimes it just refuses to work. Will investigate once I find the time.
-
Hey svk,
You might already know and be working on it, but it looks like your site's connection to the blockchain is down as all areas appear to be not populated with data.
I tried it from 2 different sources so I don't believe the problem is on my end.
Just a heads up in case you weren't aware.
Thanks.
Hey, thanks for the heads up but like the others are saying it does work, it's just a strange bug related to cross origin sharing, which means your browser is blocking the data sent from my back end since it's not on the same domain as your computer.
My http headers are all OK to handle this, but it seems sometimes it just refuses to work. Will investigate once I find the time.
Thanks for staying on top of things and responding even when it was a false alarm. I'll know next time to just wait for it to come back on it's own.
Recently I built some code that loads dynamic content on other people's websites, I had some initial issues with CORS for some reason so I defaulted to JSONP and that has worked well, not sure if that could be a possible solution though if you want to do more interaction for your visitors than just GETs at some point.
-
Suggestion:
You can split transactions into various types: transfer, bid, ask, ...
and show separately.
If you want to get fancy, do something like this:
"Realtime Bitcoin transaction and trade visualizer. "
http://www.bittumble.com/listen-to-bitcoin/
Would also be cool to show what is being transferred using different images/colors/sounds...
-
Great resource and site... +5%
I've voted for your delegates...
-
Hey svk,
You might already know and be working on it, but it looks like your site's connection to the blockchain is down as all areas appear to be not populated with data.
I tried it from 2 different sources so I don't believe the problem is on my end.
Just a heads up in case you weren't aware.
Thanks.
Hey, thanks for the heads up but like the others are saying it does work, it's just a strange bug related to cross origin sharing, which means your browser is blocking the data sent from my back end since it's not on the same domain as your computer.
My http headers are all OK to handle this, but it seems sometimes it just refuses to work. Will investigate once I find the time.
Thanks for staying on top of things and responding even when it was a false alarm. I'll know next time to just wait for it to come back on it's own.
Recently I built some code that loads dynamic content on other people's websites, I had some initial issues with CORS for some reason so I defaulted to JSONP and that has worked well, not sure if that could be a possible solution though if you want to do more interaction for your visitors than just GETs at some point.
Thanks for the tip, I considered doing that when I first implemented it but decided to go the CORS way, but in the end I should've just gone with JSONP from the start.
I just switched the site over to using JSONP calls, if you notice you're not getting updates do an F5 to get the new version with the proper API calls!
-
congrats, good job.
-
Hey svk,
You might already know and be working on it, but it looks like your site's connection to the blockchain is down as all areas appear to be not populated with data.
I tried it from 2 different sources so I don't believe the problem is on my end.
Just a heads up in case you weren't aware.
Thanks.
Hey, thanks for the heads up but like the others are saying it does work, it's just a strange bug related to cross origin sharing, which means your browser is blocking the data sent from my back end since it's not on the same domain as your computer.
My http headers are all OK to handle this, but it seems sometimes it just refuses to work. Will investigate once I find the time.
Thanks for staying on top of things and responding even when it was a false alarm. I'll know next time to just wait for it to come back on it's own.
Recently I built some code that loads dynamic content on other people's websites, I had some initial issues with CORS for some reason so I defaulted to JSONP and that has worked well, not sure if that could be a possible solution though if you want to do more interaction for your visitors than just GETs at some point.
Thanks for the tip, I considered doing that when I first implemented it but decided to go the CORS way, but in the end I should've just gone with JSONP from the start.
I just switched the site over to using JSONP calls, if you notice you're not getting updates do an F5 to get the new version with the proper API calls!
Nice! You do fast work. Hopefully that ends up being more stable.
-
I've added a market depth chart as well as ask and bid listings for each asset to the asset page. I feel like the asks and bids got inversed somehow though, but I haven't been able to get the GUI working under linux yet so can't check how it looks in the wallet. Anyone able to tell me if my representation is correct or not?
http://bitsharesblocks.com/assets/asset?id=USD
Oh and I also added an about page with some info and links :)
-
awesome!!
-
I want to state again how useful bitsharesblocks.com is: very useful (: .
Some low priority feedback:
Show when last known block was signed (eg "8 sec ago").
Sorting delegates by version might also be useful.
In "LAST 10 BLOCKS" panel missed blocks are not indicated (even though they are visible in "LAST 10 MISSED BLOCKS").
It would be good if missed blocks are indicated also on "blocks" tab (http://bitsharesblocks.com/blocks).
-
Very nice site svk.
About the "shorts range" highlighted region, is that the +/- 10% median price rule ?
-
I want to state again how useful bitsharesblocks.com is: very useful (: .
Some low priority feedback:
Show when last known block was signed (eg "8 sec ago").
Sorting delegates by version might also be useful.
In "LAST 10 BLOCKS" panel missed blocks are not indicated (even though they are visible in "LAST 10 MISSED BLOCKS").
It would be good if missed blocks are indicated also on "blocks" tab (http://bitsharesblocks.com/blocks).
Thanks, really glad you're finding it useful ;)
I'm taking some time off programming this weekend but will see what I can do next week. Sorting by version I can do for sure, and I agree about the missed blocks.
-
Very nice site svk.
About the "shorts range" highlighted region, is that the +/- 10% median price rule ?
Thank you! It is indeed based off the 10% rule and the avg price, not sure if it should be the median rather but they're quite close anyway.
-
Very nice site svk.
About the "shorts range" highlighted region, is that the +/- 10% median price rule ?
Thank you! It is indeed based off the 10% rule and the avg price, not sure if it should be the median rather but they're quite close anyway.
If enough delegates announce a feed (>51) than the "1hr moving average" is defined as the median of the feeds .. (which is not really correct terminology)
if less then 51 feeds are available the 'real' 1hr moving average will be calculated using the market itself.
so the +-10% should always be around the 1hr moving avr.. (which is identical to the feed if 51+ delegates announced a feed)
that's my understanding
-
Very nice site svk.
About the "shorts range" highlighted region, is that the +/- 10% median price rule ?
Thank you! It is indeed based off the 10% rule and the avg price, not sure if it should be the median rather but they're quite close anyway.
If enough delegates announce a feed (>51) than the "1hr moving average" is defined as the median of the feeds .. (which is not really correct terminology)
if less then 51 feeds are available the 'real' 1hr moving average will be calculated using the market itself.
so the +-10% should always be around the 1hr moving avr.. (which is identical to the feed if 51+ delegates announced a feed)
that's my understanding
I find it hard to keep up with all the rule changes, so I really appreciate sites like yours that give visual clues as to what I need to know to trade.
Perhaps some tooltips would help to explain what the significance of the short range is? This explanation from xeroc kind of proves why this is needed.
-
Very nice site svk.
About the "shorts range" highlighted region, is that the +/- 10% median price rule ?
Thank you! It is indeed based off the 10% rule and the avg price, not sure if it should be the median rather but they're quite close anyway.
If enough delegates announce a feed (>51) than the "1hr moving average" is defined as the median of the feeds .. (which is not really correct terminology)
if less then 51 feeds are available the 'real' 1hr moving average will be calculated using the market itself.
so the +-10% should always be around the 1hr moving avr.. (which is identical to the feed if 51+ delegates announced a feed)
that's my understanding
Cool, that was my understanding as well and it's what my "short range" window is based off.
I didn't get much time to work on the site this weekend, but today I've finished reworking the individual delegate info page, the big news is a plot showing the evolution of the sum of votes for that delegate, personally I quite like it :)
FYI if you're a delegate and have a website address associated with your delegate campaign, you can add it to the "public_data" for your account and my website will pick it up and display it. Here's the syntax:
wallet_account_update_registration <account_name> <pay_from_account> {"website":"http://www.mywebsite.com"} [delegate_pay_rate]
Atm only two delegates have this info I think: agsexplorer and myself.
http://bitsharesblocks.com/delegates/delegate?name=delegate.svk31
-
wow .. this looks awesome ..
gonna add a link for the charity delegates this evening ..
-
Yeah, this is pretty much awesome!!
Great Job.
(added you to my votes too. ;) )
-
Very nice site +5%
-
I've added a Charts page with some new stats, it's a work in progress but for now you'll find time plots of BTSX transaction values, BTSX transaction count, total number of accounts, and new accounts per hour.
-
You're killing it with that site. Well done!
-
I've added a Charts page with some new stats, it's a work in progress but for now you'll find time plots of BTSX transaction values, BTSX transaction count, total number of accounts, and new accounts per hour.
Such an awesome site, I'm using it daily.
-
You're killing it with that site. Well done!
I've added a Charts page with some new stats, it's a work in progress but for now you'll find time plots of BTSX transaction values, BTSX transaction count, total number of accounts, and new accounts per hour.
Such an awesome site, I'm using it daily.
Thanks!
On suggestion from bitcoinerS I've added a breakdown of asset transactions to the charts page, you'll find the number of asks, bids and shorts per hour versus time. Will be interesting to see if the number of asset transactions picks up today following the yield implementation. For now this is for all assets, not only for USD for example, might add per asset info later.
I also fixed some bugs in the asset plots so they should update correctly now.
UPDATE: There's something strange going on with the data grouping in the column plots, highstocks appears to incorrectly add up the data making it look like more transactions took place than what really happened. Trying to figure it out, trends should be ok I think but don't trust the numbers in the columns..
Fixed, it was a sorting issue. Somehow highstocks was the treating the data as non-sorted, messing things up. Adding a sort to the data fixed it, but I can't for the life of me tell the difference between the new sorted array and the original array.. Oh well, it works at least.
-
I want to state again how useful bitsharesblocks.com is: very useful (: .
Some low priority feedback:
Show when last known block was signed (eg "8 sec ago").
Sorting delegates by version might also be useful.
In "LAST 10 BLOCKS" panel missed blocks are not indicated (even though they are visible in "LAST 10 MISSED BLOCKS").
It would be good if missed blocks are indicated also on "blocks" tab (http://bitsharesblocks.com/blocks).
You can now sort delegates by version :) I started working on adding missed blocks to the blocks page but it needs some more work, maybe in the next few days I'll find time.
I also added a filter to the asset shorts in the orderbook, which means "invalid" shorts that are way below the 1 hour average price will no longer be shown. This was the case for CNY, the orderbook plot looks much cleaner now.
-
You can now sort delegates by version :) I started working on adding missed blocks to the blocks page but it needs some more work, maybe in the next few days I'll find time.
I also added a filter to the asset shorts in the orderbook, which means "invalid" shorts that are way below the 1 hour average price will no longer be shown. This was the case for CNY, the orderbook plot looks much cleaner now.
I'd like to report a bug on this one (btw do you have any other place for that?):
Version sorting does not work for me on Firefox (v31) and Chrome (Version 37.0.2062.120) on Windows 8.1. It is clickable but no sorting occurs. Delegate reliability sorting works as expected on both browsers. After reliability sorting is performed and then the user clicks on version sorting, the listing returns to default (rank) sorting.
-
You can now sort delegates by version :) I started working on adding missed blocks to the blocks page but it needs some more work, maybe in the next few days I'll find time.
I also added a filter to the asset shorts in the orderbook, which means "invalid" shorts that are way below the 1 hour average price will no longer be shown. This was the case for CNY, the orderbook plot looks much cleaner now.
I'd like to report a bug on this one (btw do you have any other place for that?):
Version sorting does not work for me on Firefox (v31) and Chrome (Version 37.0.2062.120) on Windows 8.1. It is clickable but no sorting occurs. Delegate reliability sorting works as expected on both browsers. After reliability sorting is performed and then the user clicks on version sorting, the listing returns to default (rank) sorting.
Thanks for letting me know, I've fixed it now. They were all flagged as the same version that was why..
You can report bugs here for sure, or by pm or to bitsharesblocks@gmail.com
-
Version sorting works now.
However I see immortal.bitdelegate version as 0.4.13 while it was published as v0.4.15-RC1.
I see your version is synchronized (you have the latest block), so there should be an issue with that.
My client reports correct version.
UPDATE: It seems it is still work in progress, as the site changes on each refresh. It is OK now. GJ!
UPDATE2: You might want to flag those who report 0.4.15 as red as this is not correct (version is bound to be git tag name, but that is not a tag). The delegate must have used manual version update and didn't report it correctly.
-
Version sorting works now.
However I see immortal.bitdelegate version as 0.4.13 while it was published as v0.4.15-RC1.
I see your version is synchronized (you have the latest block), so there should be an issue with that.
My client reports correct version.
UPDATE: It seems it is still work in progress, as the site changes on each refresh. It is OK now. GJ!
Good to hear :) The delegates info on that page refreshes every two minute IIRC, so if you're patient you can just wait a little and it will update.
-
feature request:
can you change the "Estimated Confirmation Time: 10s" on the frontpage into
"average confirmation time: x/2 sec" .. so 5 secs if most delegates are runing fine!?
-
svk I have a feature request too.
Could you show a graph in the asset page of the total circulation/supply of that asset? It would be very interesting to see the growth in BitUSD supply as we approach the next bubble.
-
Could you implement the future to have the option to vote for delegates on the delegate page and/or on each individual delegate page with links added for that purpose?
-
I love the site, very fast and easy to browse delegates and markets.
We should make this a sticky thread
-
feature request:
can you change the "Estimated Confirmation Time: 10s" on the frontpage into
"average confirmation time: x/2 sec" .. so 5 secs if most delegates are runing fine!?
Not sure that's really correct, although I seem to remember you asking BM about this and him confirming it... I'm just reading that confirmation time directly from the client though.
svk I have a feature request too.
Could you show a graph in the asset page of the total circulation/supply of that asset? It would be very interesting to see the growth in BitUSD supply as we approach the next bubble.
Not sure I can get the time history of that from the API calls, will look into it. Would definitely be interesting to have, if it's not available I'll start logging it so we can see it from now on.
Could you implement the future to have the option to vote for delegates on the delegate page and/or on each individual delegate page with links added for that purpose?
Had thought about that but forgot about it, will add it!
I love the site, very fast and easy to browse delegates and markets.
We should make this a sticky thread
Thanks, glad you like it :)
-
The block confirmation time still is 10 secs ... but on _*average*_ .. a transaction is confirmed after 5 secs ..
-
The block confirmation time still is 10 secs ... but on _*average*_ .. a transaction is confirmed after 5 secs ..
Yea I suppose you're right, I'll change it tomorrow as it makes BTSX look even better compared to everything else :)
-
Hey svk,
Quick feature request, maybe worth putting last block or average last X blocks latency in the delegate listing. My delegate (as well as some others apparently) had an issue recently where it was creating blocks at the wrong time and causing other delegates to miss blocks. Having that metric listed would make it easy to spot which delegates might be having issues, then anyone could ping that delegate and request they look at their server times.
Thanks.
-
svk seems like the BIDS are not output correctly.
-
svk seems like the BIDS are not output correctly.
I had a quick look but couldn't immediately see anything wrong, what exactly isn't correct?
-
svk seems like the BIDS are not output correctly.
Think I found it, were you referring to the block view? If so I updated it, should work now.
-
default (unlocked) >>> blockchain_market_order_book USD BTSX
BIDS (* Short Order) | ASKS
TOTAL QUANTITY PRICE | PRICE QUANTITY TOTAL COLLATERAL
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
63.3700 USD 1,730.00100 BTSX 0.036630036630 USD | 0.037683288000 USD 4,151.92918 BTSX 156.4583 USD
2,079.8070 USD 56,939.27181 BTSX 0.036526757962 USD | 0.037732147035 USD 0.09100 BTSX 0.0034 USD
1,000.7525 USD 27,500.00000 BTSX 0.036391000000 USD | 0.038209794699 USD 419,059.89810 BTSX 16,012.1926 USD
2,000.0000 USD 55,000.00000 BTSX 0.036363636364 USD | 0.038353095860 USD 1,174.83033 BTSX 45.0583 USD
10.0000 USD 275.00000 BTSX 0.036363636364 USD | 0.038406767494 USD 1,136,832.68791 BTSX 43,662.0687 USD
396.2692 USD 10,929.09691 BTSX 0.036258183359 USD | 0.038461538462 USD 2.60000 BTSX 0.0999 USD
377.9575 USD 10,424.62507 BTSX 0.036256220000 USD | 0.038461538462 USD 26.00000 BTSX 0.9999 USD
1,000.0000 USD 27,610.00000 BTSX 0.036218761318 USD | 0.038631647961 USD 173,203.80304 BTSX 6,691.1483 USD
10,000.0000 USD 280,000.00000 BTSX 0.035714285714 USD | 0.039215686275 USD 1,275.00000 BTSX 49.9999 USD
49.9999 USD 1,400.00000 BTSX 0.035714285714 USD*| 0.039980009995 USD 12,506.25000 BTSX 499.9999 USD
99.9999 USD 2,875.00000 BTSX 0.034782608696 USD*| 0.039984006397 USD 1.24755 BTSX 0.0498 USD
5.0000 USD 144.93500 BTSX 0.034498223341 USD | 0.040000000000 USD 250.00000 BTSX 10.0000 USD
10,000.0000 USD 289,999.99999 BTSX 0.034482758621 USD | 0.040000000000 USD 60.00000 BTSX 2.4000 USD
and on the website
BIDS (Sell USD)
Price (BTSX/USD) Amount (BTSX)
27.300 6.337
27.377 207.981
27.479 100.075
27.500 200.000
27.500 1.000
27.580 39.627
27.581 37.796
27.610 100.000
28.000 1,000.000
it looks like you are using the "balance" from the RPC call as BTSX as opposed to USD.
-
default (unlocked) >>> blockchain_market_order_book USD BTSX
BIDS (* Short Order) | ASKS
TOTAL QUANTITY PRICE | PRICE QUANTITY TOTAL COLLATERAL
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
63.3700 USD 1,730.00100 BTSX 0.036630036630 USD | 0.037683288000 USD 4,151.92918 BTSX 156.4583 USD
2,079.8070 USD 56,939.27181 BTSX 0.036526757962 USD | 0.037732147035 USD 0.09100 BTSX 0.0034 USD
1,000.7525 USD 27,500.00000 BTSX 0.036391000000 USD | 0.038209794699 USD 419,059.89810 BTSX 16,012.1926 USD
2,000.0000 USD 55,000.00000 BTSX 0.036363636364 USD | 0.038353095860 USD 1,174.83033 BTSX 45.0583 USD
10.0000 USD 275.00000 BTSX 0.036363636364 USD | 0.038406767494 USD 1,136,832.68791 BTSX 43,662.0687 USD
396.2692 USD 10,929.09691 BTSX 0.036258183359 USD | 0.038461538462 USD 2.60000 BTSX 0.0999 USD
377.9575 USD 10,424.62507 BTSX 0.036256220000 USD | 0.038461538462 USD 26.00000 BTSX 0.9999 USD
1,000.0000 USD 27,610.00000 BTSX 0.036218761318 USD | 0.038631647961 USD 173,203.80304 BTSX 6,691.1483 USD
10,000.0000 USD 280,000.00000 BTSX 0.035714285714 USD | 0.039215686275 USD 1,275.00000 BTSX 49.9999 USD
49.9999 USD 1,400.00000 BTSX 0.035714285714 USD*| 0.039980009995 USD 12,506.25000 BTSX 499.9999 USD
99.9999 USD 2,875.00000 BTSX 0.034782608696 USD*| 0.039984006397 USD 1.24755 BTSX 0.0498 USD
5.0000 USD 144.93500 BTSX 0.034498223341 USD | 0.040000000000 USD 250.00000 BTSX 10.0000 USD
10,000.0000 USD 289,999.99999 BTSX 0.034482758621 USD | 0.040000000000 USD 60.00000 BTSX 2.4000 USD
and on the website
BIDS (Sell USD)
Price (BTSX/USD) Amount (BTSX)
27.300 6.337
27.377 207.981
27.479 100.075
27.500 200.000
27.500 1.000
27.580 39.627
27.581 37.796
27.610 100.000
28.000 1,000.000
it looks like you are using the "balance" from the RPC call as BTSX as opposed to USD.
I believe you are correct! The data from the API call is inversed compared to the shorts and asks, didn't notice when I implemented it but always though it was strange there were so few bids! I pushed a fix just now, let me know if it looks correct now pls!
Oh and I left the USD value in the BIDS column, for those of you who are into the whole trading thing, what's your preference? Bids, shorts and asks in the same unit or not, and which unit is preferred?
-
Fantastic thanks for the quick fix, I was rather confused I could not see my bids ;). I like it like this is very easy to see and compare the asks / bids and shorts.
-
Fantastic thanks for the quick fix, I was rather confused I could not see my bids ;). I like it like this is very easy to see and compare the asks / bids and shorts.
Awesome, thanks for letting me know, its been like that for a while now ;)
-
Could you implement the future to have the option to vote for delegates on the delegate page and/or on each individual delegate page with links added for that purpose?
I added this a couple days ago, I'm not really that happy with how it looks but at least it's there for now.
feature request:
can you change the "Estimated Confirmation Time: 10s" on the frontpage into
"average confirmation time: x/2 sec" .. so 5 secs if most delegates are runing fine!?
Ditto for this.
I've also added a Market Cap column to the market issued assets overview, the cap is calculated using Coinmarketcap price data for USD/BTSX and the 1h average price. I've got BTC and CNY prices as well so I'll add the possibility to show the market cap in CNY or BTC once I get time. You can now also tell which assets have sufficient fees, and I only count the valid feeds (newer than 24hrs). I'll see if I can get those prices added to the price history charts for bitUSD, bitCNY and bitBTC.
In other news: my site has been added to Coinmarketcap.com as the block explorer for BTSX, you'll find the link in the Supply column. I'm also providing a feed for them with supply data and asset data.
-
Could you implement the future to have the option to vote for delegates on the delegate page and/or on each individual delegate page with links added for that purpose?
I added this a couple days ago, I'm not really that happy with how it looks but at least it's there for now.
It's very nice! Could you implement it on http://bitsharesblocks.com/delegates
page also , for example on end of the row for each delegate next to the version column ?
-
Could you implement the future to have the option to vote for delegates on the delegate page and/or on each individual delegate page with links added for that purpose?
I added this a couple days ago, I'm not really that happy with how it looks but at least it's there for now.
It's very nice! Could you implement it on http://bitsharesblocks.com/delegates
page also , for example on end of the row for each delegate next to the version column ?
I feel like that table is already a bit overloaded but I'll make some internal tests and see how it looks.
-
What about making the squares "orange" if we have 25-50 valid feeds?
on http://bitsharesblocks.com/assets
-
What about making the squares "orange" if we have 25-50 valid feeds?
on http://bitsharesblocks.com/assets
Good idea :)
-
It would be great to be able to see, not only BitAssets price history, but also price history of the corresponding real Assets and history of price correlation in the same chart.
-
It looks like the front page dashboard view of the last 10 blocks is lagging a couple days behind. Not a big deal since the blocks page appears to be accurate but thought you might want to know.
-
It looks like the front page dashboard view of the last 10 blocks is lagging a couple days behind. Not a big deal since the blocks page appears to be accurate but thought you might want to know.
Works fine for me, might be a cache issue if you've left it open for a long time, try refreshing the page.
@bitcoinerS I might do that at least with btc, USD and cny, but I tried briefly and didn't like the way it looked, will see if I can get it right then push it.
-
It looks like the front page dashboard view of the last 10 blocks is lagging a couple days behind. Not a big deal since the blocks page appears to be accurate but thought you might want to know.
Works fine for me, might be a cache issue if you've left it open for a long time, try refreshing the page.
@bitcoinerS I might do that at least with btc, USD and cny, but I tried briefly and didn't like the way it looked, will see if I can get it right then push it.
Odd looking at the page now without any refreshes it is current. When it was behind before I refreshed it multiple times. Oh well probably just on my end then. Thanks.
-
Not sure if anyone's requested this already but we need the daily volume for each asset as well.
Thanks for all your hard work. You're providing a really great service to the community.
-
Not sure if anyone's requested this already but we need the daily volume for each asset as well.
Thanks for all your hard work. You're providing a really great service to the community.
Added that this morning, it's in the assets overview table, only in USD atm but I'll enable some other units later.
Edit: oh and thanks :)
-
I just saw the latency updated on the Delegate page. IMO this should be removed, as perhaps it unfairly shows Chinese/ROW (rest of world) delegates as having high latencies. Latency will vary depending on where your server is setup.
To be more fair, you could setup servers on opposite sides of the world and use the lowest latency figures provided from both servers, but this may be unrealistic I don't know.
Good work with everything else though, the website is coming along nicely. :)
-
I just saw the latency updated on the Delegate page. IMO this should be removed, as perhaps it unfairly shows Chinese/ROW (rest of world) delegates as having high latencies. Latency will vary depending on where your server is setup.
To be more fair, you could setup servers on opposite sides of the world and use the lowest latency figures provided from both servers, but this may be unrealistic I don't know.
Good work with everything else though, the website is coming along nicely. :)
I think rather than remove we should figure out what figure of latency is acceptable and flag green everything below that mark. I made people miss blocks when my latency was -17 seconds so I'd assume anything over that should definitely be red. Not sure how big the number has to be to mess up block production for the guy before or after you though.
Edit: Forgot to say thank you for continuing to work on and improve the site. It's a great asset to have as a delegate and I check it all the time, thanks!
-
on personal delegate pages the client versions field are on red squares saying: "to old" even if they are running on the latest client version. pls fix ;)
-
I just saw the latency updated on the Delegate page. IMO this should be removed, as perhaps it unfairly shows Chinese/ROW (rest of world) delegates as having high latencies. Latency will vary depending on where your server is setup.
To be more fair, you could setup servers on opposite sides of the world and use the lowest latency figures provided from both servers, but this may be unrealistic I don't know.
Good work with everything else though, the website is coming along nicely. :)
I actually agree with this, and it's one of the reasons it took me so long to get around to adding latencies. What we're really seeing is the latency compared to my server, and as it's in New York some of the Chinese delegates end up looking bad. I'm not quite sure how to deal with it, will have to think about it, setting up a separate server in Asia might be a solution.
There are Chinese delegates with good latencies too though, but I'm not sure where their servers are. I think I'll change the colorcoding, I'll make negative latencies red but keep anything <2s green or something like that, at least for now.
It's interesting information though so I'll keep it up for now, this one for example has consistent negative latencies, probably meaning it's clock is too fast:
http://bitsharesblocks.com/delegates/delegate?name=bitsharesx-delegate
-
on personal delegate pages the client versions field are on red squares saying: "to old" even if they are running on the latest client version. pls fix ;)
Looks fine from my computer at work, can you try again pls?
-
I just saw the latency updated on the Delegate page. IMO this should be removed, as perhaps it unfairly shows Chinese/ROW (rest of world) delegates as having high latencies. Latency will vary depending on where your server is setup.
To be more fair, you could setup servers on opposite sides of the world and use the lowest latency figures provided from both servers, but this may be unrealistic I don't know.
Good work with everything else though, the website is coming along nicely. :)
I think rather than remove we should figure out what figure of latency is acceptable and flag green everything below that mark. I made people miss blocks when my latency was -17 seconds so I'd assume anything over that should definitely be red. Not sure how big the number has to be to mess up block production for the guy before or after you though.
Edit: Forgot to say thank you for continuing to work on and improve the site. It's a great asset to have as a delegate and I check it all the time, thanks!
Yea I set the color codings based on the averages I was seeing, with no real info on what's acceptable or not. I'll relax the criteria and probably change the three latency calculations on the delegate page to include fewer blocks, 10 and 25 blocks maybe rather than 50 and 100, will play around a bit with it.
-
Ooops, I left some debugging code in the block view, so it's spitting out a json string with some block data, please ignore it, I'll remove it once I get home! :-[
-
feature request: list number of published feeds for all delegates and the list of published feeds with prices for a specified delegate.
It is kind of lame that some delegates do not follow their duty to publish feeds .. only 66 delegates published for bitUSD ?!?
even my charity delegates are now publishing feeds payed by delegate.xeroc just to keep the running market running ..
-
feature request: list number of published feeds for all delegates and the list of published feeds with prices for a specified delegate.
It is kind of lame that some delegates do not follow their duty to publish feeds .. only 66 delegates published for bitUSD ?!?
even my charity delegates are now publishing feeds payed by delegate.xeroc just to keep the running market running ..
Yea I wanted to do this as well, and have had other requests for it already, but there's an issue with the client and the api call to get feeds. It's fine if you want to just get feeds for one delegate, but the performance of the call is poor enough that it freezes the client if you try to batch chain it. Vikram pushed some fixes and I'll have a look with the v0.4.17 client to see if it works better now.
I could implement it on my own database as well actually since I already have all the feeds, will check if that's a better way of doing it!
-
Just notice on the assets page the the bid/ask column titles seem backwards. If i'm selling wouldn't i be asking and if I am buying wouldn't I be bidding?
-
What about making the squares "orange" if we have 25-50 valid feeds?
on http://bitsharesblocks.com/assets
Good idea :)
Once most assets are trading I think I would change the colour coding to 0-50 red, 51-55? orange, 56+ green.
A market with 51 feeds is far from being in a good state - it is at the brink of disaster :)
-
*agreed*
I want to code small script this evening to figure out which of the delegates do not publish feeds and announce a down-vote request
-
on personal delegate pages the client versions field are on red squares saying: "to old" even if they are running on the latest client version. pls fix ;)
Looks fine from my computer at work, can you try again pls?
same problem! please check "my" link for example:
http://bitsharesblocks.com/delegates/delegate?name=delegate.liondani
look down to the left:
"Client version:Too old: v0.4.17-RC2"
-
on personal delegate pages the client versions field are on red squares saying: "to old" even if they are running on the latest client version. pls fix ;)
Looks fine from my computer at work, can you try again pls?
same problem! please check "my" link for example:
http://bitsharesblocks.com/delegates/delegate?name=delegate.liondani
look down to the left:
"Client version:Too old: v0.4.17-RC2"
Yea I noticed this as well this morning, I need to update the logic slightly for that page, will do it once I get home.
-
Just notice on the assets page the the bid/ask column titles seem backwards. If i'm selling wouldn't i be asking and if I am buying wouldn't I be bidding?
I agree it feels strange but I'm just using the terminology from the client. Since I've flipped the market I guess I should invert the asks and bids too, will have a look later to see what makes sense.
-
Feature request: graph showing current and historic market peg deviation. If BitAssets are pegging well, we should be able to see it clearly, and these graphs could be great marketing tools.
Thank you svk for all your great work!
-
It seems like the site stopped syncing..
@svk?
-
The client on the website server stopped syncing almost immediately after I went to bed, must've gotten on a fork somehow. It's back up now, sorry about that.
-
Recent updates:
In case you missed it, I recently added a graph to the home page showing the price of BTSX vs USD with 15 and 30-day moving averages. The price is from Coinmarketcap, meaning it's a weighted average over the exchanges they track. You can also find a bigger version of this graph under the Charts tab, where there's also a BTC version. A reminder: you can click on the legend to enable/disable series.
I also updated the version handling logic, it will now distinguish between release candidates and official versions.
I also updated the block view to correctly handle asset transfers, up until now all transfers were counted as BTSX which was obviously incorrect, you'll now see the correct units and values for transfers.
I've had to remove the fee information due it being removed from the block info RPC API, will try to get it back but it's become a bit more complicated due to the addition of fees payable using assets, so will need to add some logic on the backend I think.
Latencies are removed temporarily due to the server finding itself on a fork last night, I'll put them back tomorrow evening I reckon.
Finally, I've received my first donations to the site, so thanks very much to the donors!
-
I have the last version v0.4.17 but on delegates page it stills mentions an older version. (I have refreshed the page several times,reloaded, but same results)
http://www.bitsharesblocks.com/delegates
http://www.bitsharesblocks.com/delegates/delegate?name=delegate.liondani
-
I have the last version v0.4.17 but on delegates page it stills mentions an older version. (I have refreshed the page several times,reloaded, but same results)
http://www.bitsharesblocks.com/delegates
http://www.bitsharesblocks.com/delegates/delegate?name=delegate.liondani
It is OK on my side. However I also noticed some different refresh issues.
Should anything be cashed after I hit CTRL+F5 ?
-
Very strange, I see your delegate as having v0.4.17 liondani, both in the overview and on the delegate page.
I do tend to push updates quite frequently so it's generally a good idea to refresh the page every now and then. Not an expert on browser caching but a simple F5 has been working perfectly for me every time I push an update.
-
it looks like the asset value is not calculated correct. if you take a look.
-
it looks like the asset value is not calculated correct. if you take a look.
The market cap? Looks like the supply of USD has dropped by about $200k, maybe that's why? Going out for dinner so don't have time to investigate right now I'm afraid.
-
Asks are 'for sale orders' and Bids are 'buys'. Your naming them opposite on charts is very confusing. Please correct.
-
Asks are 'for sale orders' and Bids are 'buys'. Your naming them opposite on charts is very confusing. Please correct.
Corrected last night, are they OK now?
Seeing how price feeds are all the rage at the moment, I've added them to the site! In the delegates overview you'll find the count of how many active feeds each delegate currently has, and if you click on a delegate you can see which feeds he has published, the feed prices and the date of publication.
There are surprisingly many delegates with no active feeds, 25 or so!
-
awesome .. thanks for adding that feature ..
we might consider starting a campaign to kick out those lazy delegates soon!
-
I would suggest delegates with 3 or more active feeds be marked with green.
-
I would suggest delegates with 3 or more active feeds be marked with green.
Maybe temporarily yea, while the recommendation from BM is to hold off on new markets, it'll have to wait a few hours though till I get back from work.
-
awesome .. thanks for adding that feature ..
we might consider starting a campaign to kick out those lazy delegates soon!
+5%
-
You are doing an awesome job ..
and I have yet another feature request :)
could we track the minimum required percentage of votes required to become an active delegate as a graph?
-
You are doing an awesome job ..
and I have yet another feature request :)
could we track the minimum required percentage of votes required to become an active delegate as a graph?
Hm could be possible, I have the number of votes over time and could find the last rank at a given block, but I don't have time history of the supply. If an approximation using the current supply is acceptable then it should be possible.
Next up are some fork statistics though I think, then I want to add the possibility of browsing through blocks in the overview, will try to work on that this week-end.
-
you just need to track the "vote" value of the 101st delegate and track that over time .. normalization is over the total supply (2B*1e5)
I don't think it makes sense to take those few destroyed fees into account now .. mayby in 2 years or so
-
I think it is better to have in green squares the number of active feeds when
active feeds >= from the current number of active markets...
(for example right now we have 3 active markets , in green squares should be all delegates with at least 3 feeds for these markets)
The minimum requirement to be green in my opinion is to publish feeds for at least all active markets....
-
you can cheat on that if you publish feeds for inactive markets .. but the idea is good ..
maybe the sum of all feeds for an active market! .. only green if publishes for ALL
-
I've added the frequency of feed updates to the delegates overview, and average latencies are back.
Yesterday I also added some fork info to the home page.
-
Nice additions svk, thanks.
-
I did a major rewrite of block and transaction handling yesterday, both on the backend and the frontend. The backend part meant I had to rebuild the block and transaction database from block 1. I noticed this morning the latencies are really high, I'm guessing it's due to the database rebuilding overloading the server, making the client fall out of sync a little. If the latencies don't fall during the day I'll look into it when I get home.
The rewrite was to handle transactions and fees in assets other than BTSX, as well as adding the possibility to browse through all the blocks in the overview page. I still have to check it some more for bugs, but should be available this evening or tomorrow.
-
I did a major rewrite of block and transaction handling yesterday, both on the backend and the frontend. The backend part meant I had to rebuild the block and transaction database from block 1. I noticed this morning the latencies are really high, I'm guessing it's due to the database rebuilding overloading the server, making the client fall out of sync a little. If the latencies don't fall during the day I'll look into it when I get home.
The rewrite was to handle transactions and fees in assets other than BTSX, as well as adding the possibility to browse through all the blocks in the overview page. I still have to check it some more for bugs, but should be available this evening or tomorrow.
Nice work!!! Thanks! +5%
-
OK it is live! You can now browse trough the entire block history easily, filtering out empty transactions to show only the interesting blocks. To give a better overview I've reduced the number of blocks on the overview page to 20. Transaction values and fees in assets other than BTSX are now accounted for, there might be a block here and there that doesn't have correct fee info, I might reindex the whole thing sometime to get them all correct but there shouldn't be a lot of them so I'll leave it for now.
If you had the site open I might have broken your transaction info, do a refresh to get the latest version.
-
you are doing an awesome work svk. well done!
-
Suggestions:
Create another chart for each delegate's page where:
1. number of times a delegate is voted for and against (VOTES HISTORY (x VOTES)
2. Somehow I don't see negative votes shown anywhere. Vote tally goes up and down, but only up votes are visible in votes history box below.
3. Not only block number should be visible, but also date.
-
How are the feeds per day calculated?
I'm getting some erratic results.
-
How are the feeds per day calculated?
I'm getting some erratic results.
my stats seem ok .. I force publish every 45 minutes which leads to 32 feeds per day
-
How are the feeds per day calculated?
I'm getting some erratic results.
my stats seem ok .. I force publish every 45 minutes which leads to 32 feeds per day
8 hours ago I had 15 feeds, now I have 4. I'm pretty sure I submitted at least 15 in the last 24 hours.
-
How are the feeds per day calculated?
I'm getting some erratic results.
my stats seem ok .. I force publish every 45 minutes which leads to 32 feeds per day
8 hours ago I had 15 feeds, now I have 4. I'm pretty sure I submitted at least 15 in the last 24 hours.
Yea I broke the feeds collection when I reindexed the database, I made a slight change to a variable which of course had unintended consequences.. I've just reindexed the last two days so feeds should be correct now. Currently reindexing from block 50000 up to 595000 lol, will take a little while for everything to be correct.
I also broke the rank changes, they'll be correct once the reindexing finishes :(
-
How are the feeds per day calculated?
I'm getting some erratic results.
my stats seem ok .. I force publish every 45 minutes which leads to 32 feeds per day
8 hours ago I had 15 feeds, now I have 4. I'm pretty sure I submitted at least 15 in the last 24 hours.
now it's ok
for some reason from one minute to another it jumped up (the same with my feed stats)
EDIT: the previous post explains everything ;)
-
Thanks! Keep up the good work!
-
I've had a bit of inspiration and motivation this morning, so I've further improved the blocks overview page. I've enabled the history API for the different pages, and also fixed some bugs in the navigation. The great thing about this is you can now share a page with big or otherwise interesting transactions, like so:
http://bitsharesblocks.com/blocks?top=6019&trx=true
The re-indexing is almost done btw, so normal service should resume shortly.
-
OK reindexing is finally done! Everything looks to be back to normal for me, latencies are a bit high still but they should come down a bit over time as the blocks that were synced after being offline during the upgrade drop out of the last 200 blocks.
-
Any chance of making this open source, at least partially open source?
Cheers :)
-
Older blocks have latencies in the millions... :) Maybe for those you can just list 'n/a'
-
Any chance of making this open source, at least partially open source?
Cheers :)
I dunno, I'm not a formally trained coder and I started out knowing next to nothing about coding in javascript and nodejs, so while everything is functional and logical at least to me, it's not really in a state that's ready to be open-sourced. If there's anything in particular you'd like access to or help with feel free to ask though!
Older blocks have latencies in the millions... :) Maybe for those you can just list 'n/a'
Yea you're right, it's the blocks for which the client wasn't online at the time of their creation, I'll add a filter so they won't show when it's obvious that they're incorrect.
-
Any chance of making this open source, at least partially open source?
Cheers :)
I dunno, I'm not a formally trained coder and I started out knowing next to nothing about coding in javascript and nodejs, so while everything is functional and logical at least to me, it's not really in a state that's ready to be open-sourced. If there's anything in particular you'd like access to or help with feel free to ask though!
Older blocks have latencies in the millions... :) Maybe for those you can just list 'n/a'
Yea you're right, it's the blocks for which the client wasn't online at the time of their creation, I'll add a filter so they won't show when it's obvious that they're incorrect.
But that's the beauty of open source software - hundreds of hands will be able to chip in work. We would see people porting it to other bitshares DACs, and the community would grow tremendously. Give it a thought :)
-
My codes (especially the feed script) are are ugly as hell ..
Maybe we can enhance it collectively and iteratively? But I can understand the open sourcinv a lot of work can sometimes be frustrating
-
Any chance of making this open source, at least partially open source?
Cheers :)
I dunno, I'm not a formally trained coder and I started out knowing next to nothing about coding in javascript and nodejs, so while everything is functional and logical at least to me, it's not really in a state that's ready to be open-sourced. If there's anything in particular you'd like access to or help with feel free to ask though!
This is called the Imposter Syndrome. A lot of people working in the IT field have felt it (I certainly have):
http://valbonneconsulting.wordpress.com/2014/08/16/the-imposter-syndrome-in-software-development/
Don't get too hung up on the "formally trained coder" thing, I've read studies about how a large percentage of computer science graduates come out of schooling can barely program (I've met a handful of comp sci graduates who code, some were impressive, some not so much): http://blog.codinghorror.com/why-cant-programmers-program/
Your code works and results in an excellent and incredibly useful web app. Keep up the great work.
-
Any chance of making this open source, at least partially open source?
Cheers :)
I dunno, I'm not a formally trained coder and I started out knowing next to nothing about coding in javascript and nodejs, so while everything is functional and logical at least to me, it's not really in a state that's ready to be open-sourced. If there's anything in particular you'd like access to or help with feel free to ask though!
This is called the Imposter Syndrome. A lot of people working in the IT field have felt it (I certainly have):
http://valbonneconsulting.wordpress.com/2014/08/16/the-imposter-syndrome-in-software-development/
Don't get too hung up on the "formally trained coder" thing, I've read studies about how a large percentage of computer science graduates come out of schooling can barely program (I've met a handful of comp sci graduates who code, some were impressive, some not so much): http://blog.codinghorror.com/why-cant-programmers-program/
Your code works and results in an excellent and incredibly useful web app. Keep up the great work.
Seconded, noone is an expert in this field yet, and your block explorer website is amazing. Keep up the great work! : D
-
can you bring back the tiny robo avatars on
http://bitsharesblocks.com/delegates ?
-
because we have now 4 active markets (bitUSD,bitCNY,bitBTC,bitGLD)
the minimum acceptable active feeds should be 4 (green) so less than that should get red coloured ...
-
Suggestions:
Create another chart for each delegate's page where:
1. number of times a delegate is voted for and against (VOTES HISTORY (x VOTES)
2. Somehow I don't see negative votes shown anywhere. Vote tally goes up and down, but only up votes are visible in votes history box below.
3. Not only block number should be visible, but also date.
Looks like you updated VOTES HISTORY (x TOTAL VOTES) box and now it shows negative votes too. Thanks. I wonder if there is a way to distinguish between un-votes due to transfer to somebody else’s account from intentional down-votes... This would be very useful.
I would like to see chart showing number of total votes (x TOTAL VOTES) over time, not just vote tally. Number of votes shows how many people are voting for a delegate.
-
Looks like you updated VOTES HISTORY (x TOTAL VOTES) box and now it shows negative votes too. Thanks. I wonder if there is a way to distinguish between un-votes due to transfer to somebody else’s account from intentional down-votes... This would be very useful.
I would like to see chart showing number of total votes (x TOTAL VOTES) over time, not just vote tally. Number of votes shows how many people are voting for a delegate.
There simply are NO downvotes on the blockchain .. the "negative" votes you see are "netto" votes .. and usually have the size of the tx fee.
-
Looks like you updated VOTES HISTORY (x TOTAL VOTES) box and now it shows negative votes too. Thanks. I wonder if there is a way to distinguish between un-votes due to transfer to somebody else’s account from intentional down-votes... This would be very useful.
I would like to see chart showing number of total votes (x TOTAL VOTES) over time, not just vote tally. Number of votes shows how many people are voting for a delegate.
There simply are NO downvotes on the blockchain .. the "negative" votes you see are "netto" votes .. and usually have the size of the tx fee.
ic.
How about a number of votes chart? number of people/accounts vs amount of money voting for/against delegate.
-
How about a number of votes chart?
When you click a delegate you will see the number of votes as percentage to total supply depicted over the time
number of people/accounts vs amount of money voting for/against delegate.
could you do us a favor and stop talking about "downvoting"/"against" delegates .. because such this is just not possible with that blockchain.
If people read you comments they start asking questions about it :-\
besides that, I like the idea .. accounts v. actively voting stake
+5%
-
Any chance of making this open source, at least partially open source?
Cheers :)
I dunno, I'm not a formally trained coder and I started out knowing next to nothing about coding in javascript and nodejs, so while everything is functional and logical at least to me, it's not really in a state that's ready to be open-sourced. If there's anything in particular you'd like access to or help with feel free to ask though!
This is called the Imposter Syndrome. A lot of people working in the IT field have felt it (I certainly have):
http://valbonneconsulting.wordpress.com/2014/08/16/the-imposter-syndrome-in-software-development/
Don't get too hung up on the "formally trained coder" thing, I've read studies about how a large percentage of computer science graduates come out of schooling can barely program (I've met a handful of comp sci graduates who code, some were impressive, some not so much): http://blog.codinghorror.com/why-cant-programmers-program/
Your code works and results in an excellent and incredibly useful web app. Keep up the great work.
Thanks for the encouragement and the article, was an interesting read. I may suffer from a slight case of Imposter Syndrome, haha.
@bitcoinerS Like xeroc says there are no downvotes, only net votes, the negative ones you're seeing are simply votes for someone being removed cause they were unapproved. I'll check if adding the number of votes to the graph adds to the picture. Every single vote will appear to be from a different account though I think due to TITAN.
-
Every single vote will appear to be from a different account though I think due to TITAN.
Oh, ... that is true .. too bad, good, bad, good, ... can't decide ;)
-
there are no downvotes, only net votes, the negative ones you're seeing are simply votes for someone being removed cause they were unapproved.
My understanding is a delegate can lose votes in two cases:
1. Due to shares voting for that delegate being transferred to a different account with different voting preferences or to a market order.
2. Due to account owner un-approving that delegate.
First is unintentional and second is intentional. Distinguishing between them would be useful.
-
Ahh ... that should be possible .. though is some work I guess ;)
-
I've reworked the transactions database and everything to do with votes and ranks for the DNS site, and am currently migrating it to the BTSX server. This means I need to re-index all the transactions, and although it's faster than before it'll still take a little while. Sorry for the disturbance.
The good news is this should make those things much less taxing on the server in the future :)
-
Hey svk, can you provide a json api?
-
Hey svk, can you provide a json api?
Hey, the server is already pretty strained so it depends what you're looking for..
-
I recently discovered that when the collateral mechanics were changed for shorting, a new transaction type was added called "short_op_v2_type". I added this to my code, but it made me wonder what other transactions I might be missing. So I made a little script to determine what transaction types had actually been used so far, here's the list if anyone's interested:
"types" : [
"register_account_op_type",
"withdraw_op_type",
"create_asset_op_type",
"define_delegate_slate_op_type",
"deposit_op_type",
"withdraw_pay_op_type",
"update_account_op_type",
"issue_asset_op_type",
"ask_op_type",
"bid_op_type",
"short_op_type",
"update_feed_op_type",
"cover_op_type",
"short_op_v2_type",
"burn_op_type",
"add_collateral_op_type"
]
I was actually missing a couple, notably burn_op_type and asset creation/issuance. I've now added these to the code and reindexed the transactions. I found an interesting thing too: the transactions BM used to correct the BTSX supply! I know some people were asking for the exact amounts etc, if you're interested it was these two transactions:
http://bitsharesblocks.com/blocks/block?id=555282
http://bitsharesblocks.com/blocks/block?id=555294
The total amount burned: 187,250+100=187,350 BTSX
-
interestingly one can add a cleartext message to burns .. thats nice :)
-
interestingly one can add a cleartext message to burns .. thats nice :)
Yea, there's another one by the account "dump" with the message "like that dump" :)
-
There are still delegates with not properly synchronized timer.
This usually hurts other delegates (missing blocks) and the stats are not properly showing who is responsible for that.
As a result I have the following feature requests:
On delegate pages:
Latency last X blocks
Reliability last X blocks
Perhaps all stats for last X blocks ?
-
There are still delegates with not properly synchronized timer.
This usually hurts other delegates (missing blocks) and the stats are not properly showing who is responsible for that.
As a result I have the following feature requests:
On delegate pages:
Latency last X blocks
Reliability last X blocks
Perhaps all stats for last X blocks ?
Yea I know the latency stats would be useful and it's already implemented but hidden at the moment. I'm just not sure how reliable my latency measurements are, since some of the values are surprisingly high. You can still see them on the individual delegate pages though (for last 50,100 and 200 blocks if available), the current top delegate bts.coin had an average latency of 7.7s over the last 50 blocks for example.
I could add reliability over the last 200 blocks produced as well.
-
There are still delegates with not properly synchronized timer.
This usually hurts other delegates (missing blocks) and the stats are not properly showing who is responsible for that.
As a result I have the following feature requests:
On delegate pages:
Latency last X blocks
Reliability last X blocks
Perhaps all stats for last X blocks ?
Yea I know the latency stats would be useful and it's already implemented but hidden at the moment. I'm just not sure how reliable my latency measurements are, since some of the values are surprisingly high. You can still see them on the individual delegate pages though (for last 50,100 and 200 blocks if available), the current top delegate bts.coin had an average latency of 7.7s over the last 50 blocks for example.
I could add reliability over the last 200 blocks produced as well.
Do you want to include data from another node ?
If you are only using RPC calls and you are willing to do it, I could grant you access to a node on my end. This way you will be able to check the latency on both sides and get better results.
-
That could be an option yes, although I would have to poll your node every 10 secs to update the blocks. If that's ok with you then I guess it could work.
-
That could be an option yes, although I would have to poll your node every 10 secs to update the blocks. If that's ok with you then I guess it could work.
This shouldn't be a problem. Send me a PM if you decide to implement this. I'll setup a node for you.
-
hi svk
first - good work!
at the moment i can not go from X to DNS. is it not possible to integrate something to switch different blockscans from the "main" side www.bitsharesblocks.com? i think it would be much better for the new chains coming.
-
hi svk
first - good work!
at the moment i can not go from X to DNS. is it not possible to integrate something to switch different blockscans from the "main" side www.bitsharesblocks.com? i think it would be much better for the new chains coming.
thanks. that is indeed on my list of things todo, just haven't gotten there yet! easy transitions between chains will come soonish :)
-
.... soonish :)
https://www.youtube.com/watch?feature=player_detailpage&v=gNIwlRClHsQ#t=11
-
.... soonish :)
https://www.youtube.com/watch?feature=player_detailpage&v=gNIwlRClHsQ#t=11
Lol, i should watch that movie again. Soon..
-
+5% +5%
-
hi svk
first - good work!
at the moment i can not go from X to DNS. is it not possible to integrate something to switch different blockscans from the "main" side www.bitsharesblocks.com? i think it would be much better for the new chains coming.
Done! Click the icon on the right side of the nav bar, it will switch sites and also send you to the corresponding page, DNS blocks to BTSX blocks etc.
-
I've seen a minor issue:
When the user opens delegate profile - http://www.bitsharesblocks.com/delegates/delegate?name=emski.bitdelegate (http://www.bitsharesblocks.com/delegates/delegate?name=emski.bitdelegate) for example.
And clicks on "show feeds" checkbox - no feeds are displayed even though that delegate has valid feeds.
Furthermore if the user clicks "show only valid feeds" checkbox then all feeds are displayed. Regardless of how many times "show only valid feeds" checkbox is toggled all the feeds remain displayed but the order changes.
Expected behavior: Clicking on "show feeds" checkbox should display all valid feeds if "show only valid feeds" is checked.
-
I've seen a minor issue:
When the user opens delegate profile - http://www.bitsharesblocks.com/delegates/delegate?name=emski.bitdelegate (http://www.bitsharesblocks.com/delegates/delegate?name=emski.bitdelegate) for example.
And clicks on "show feeds" checkbox - no feeds are displayed even though that delegate has valid feeds.
Furthermore if the user clicks "show only valid feeds" checkbox then all feeds are displayed. Regardless of how many times "show only valid feeds" checkbox is toggled all the feeds remain displayed but the order changes.
Expected behavior: Clicking on "show feeds" checkbox should display all valid feeds if "show only valid feeds" is checked.
It seems to work as expected on my phone using a.delegate.charity, your delegate is a bad example though as all your feeds are valid so they'll all be visible whatever you do.
-
It seems to work as expected on my phone using a.delegate.charity, your delegate is a bad example though as all your feeds are valid so they'll all be visible whatever you do.
That is the idea: The feeds are not visible first time I check "show feeds" on Mozilla 32.0.3/win8.1 . The same happens with other delegates.
UPDATE: Try to open the delegate page directly (not going to the delegates page). It seems this is related to the issue.
Opening this link directly should reproduce the issue: http://www.bitsharesblocks.com/delegates/delegate?name=delegate2.svk31 (http://www.bitsharesblocks.com/delegates/delegate?name=delegate2.svk31)
-
It seems to work as expected on my phone using a.delegate.charity, your delegate is a bad example though as all your feeds are valid so they'll all be visible whatever you do.
That is the idea: The feeds are not visible first time I check "show feeds" on Mozilla 32.0.3/win8.1 . The same happens with other delegates.
UPDATE: Try to open the delegate page directly (not going to the delegates page). It seems this is related to the issue.
Opening this link directly should reproduce the issue: http://www.bitsharesblocks.com/delegates/delegate?name=delegate2.svk31 (http://www.bitsharesblocks.com/delegates/delegate?name=delegate2.svk31)
I can't seem to reproduce your issue with feeds not showing when clicking on the checkbox, however I did find a bug in the sorting when showing all feeds. I've fixed it and it works fine from here at least. Check one of xeroc's delegates to test it, he's got active and non-active feeds:
http://bitsharesblocks.com/delegates/delegate?name=delegate.charity
I've also made a big overhaul of the backends for both sites today and yesterday, adding compression and caching to the api calls as well as the html/js/css, this should speed things up and keep server load down!
-
Seems to be working better - there is no feed rearrangement when toggling "show valid feeds only". The issue I experienced is still reproducible though 1 out of 3 attempts. I think it might be related to network connection. However it is so minor that it shouldn't even be looked at anymore. Good work!
-
I've added a new feature: Accounts! You can now easily browse through all the accounts as well as search for an account by name or id, the name search will work on partial strings. The individual accounts pages doesn't have a lot of information atm cause well, that's all there is basically.
Here's an example search query:
http://www.bitsharesblocks.com/accounts?query=angel
PS. If you don't see the accounts tab or it doesn't work for you, it's probably because the site has been cached locally. The cache expiration is 24hrs, but if you don't feel like waiting you can override it by hitting F5.
-
I've added a new feature: Accounts! You can now easily browse through all the accounts as well as search for an account by name or id, the name search will work on partial strings. The individual accounts pages doesn't have a lot of information atm cause well, that's all there is basically.
Here's an example search query:
http://www.bitsharesblocks.com/accounts?query=angel
PS. If you don't see the accounts tab or it doesn't work for you, it's probably because the site has been cached locally. The cache expiration is 24hrs, but if you don't feel like waiting you can override it by hitting F5.
GJ.
You could add the public data field.
-
I've added a new feature: Accounts! You can now easily browse through all the accounts as well as search for an account by name or id, the name search will work on partial strings. The individual accounts pages doesn't have a lot of information atm cause well, that's all there is basically.
Here's an example search query:
http://www.bitsharesblocks.com/accounts?query=angel
PS. If you don't see the accounts tab or it doesn't work for you, it's probably because the site has been cached locally. The cache expiration is 24hrs, but if you don't feel like waiting you can override it by hitting F5.
GJ.
You could add the public data field.
I'm showing the website field if there is one in the public data, I looked briefly for other fields that could be interesting but didn't see any.
I'll add version though, forgot about that! Actually I hadn't forgotten about it. It's late, I'm tired... :)
-
I've disabled updates of delegate slot records for the time being, the RPC call is simply too heavy for the client and I've identified it as the cause of the high latencies seen for several delegates. The client basically freezes for up to 10 minutes, dropping lots of connections and going out of sync until the record updates are done. Vikram has made a change to the RPC call so once that goes live I'll enable the records again.
https://github.com/BitShares/bitshares_toolkit/issues/858
-
It seems you haven't updated to the latest version .. or something else went wrong .. your page displays a delegate participation of ~40% .. the network itself is at 100%!
-
It seems you haven't updated to the latest version .. or something else went wrong .. your page displays a delegate participation of ~40% .. the network itself is at 100%!
Yea I totally missed the hard fork, was traveling yesterday and was at work all day, and didn't realize the deadline was so close. I even got my delegates voted out but asked BM to kindly vote me back in now that they're upgraded..
As for bitsharesblocks, it's reindexing and it's taking forever, but it should be ready soon now!
-
I've updated the site
client to 0.4.22, but it looks like there's been a few RPC output changes on the asset side. I fixed the market cap calculations but the order booking has changed too so the plots aren't showing up ATM.
I'm in Italy for a wedding though so it'll have to wait until Monday for a fix.
-
I'm in Italy for a wedding though so it'll have to wait until Monday for a fix.
Sure .. we can wait .. take your time for family (comes first - always) .. and have fun at the wedding .. (I love weddings - except maybe for the dancing part :) )
-
Forgot to let you know I fixed everything related to the v0.4.22 RPC changes! ;)
I've also just finished a pass of the individual asset pages and identified a bug in my order book plots that I've fixed. Basically unique points weren't getting summed correctly so the plots were sometimes incorrect. I also added a shorts table that shows the first 10 shorts with interest rates and collateral. Should probably add a cover table too I guess?
I've also started tracking asset supply and collateral in anticipation of the BTS launch, and I've added a supply and collateral chart for each asset. It's only got data starting yesterday but it'll get better with time.
One remaining issue with assets is the new "center_price" given by the client which seems to be stuck, not sure if it's a bug or not. Without it I don't see how to get a recent average price.
-
Great work! +5%
-
I've upgraded the site in anticipation of the BTS hardfork, I realize it's a bit early but due to a technical issue I ended up deploying it a little earlier than planned.
If you see anything incorrect please let me know, I think I got everything covered though.
Next feature coming is a plot of BTS supply over time to track inflation.
I've also started working on some genesis analysis, if you have any particular plots or info you'd like to see for the genesis block give me a shout!
Edit: Forgot to say I added some info to the home page: total BTS tied up as collateral, asset registration fee (they're currently the same for long and short names, bug maybe?), and max delegate pay.
-
Excellent!
-
It doesn't work at the moment. The site is up but no data is retrieved.
I've upgraded the site in anticipation of the BTS hardfork, I realize it's a bit early but due to a technical issue I ended up deploying it a little earlier than planned.
If you see anything incorrect please let me know, I think I got everything covered though.
Next feature coming is a plot of BTS supply over time to track inflation.
I've also started working on some genesis analysis, if you have any particular plots or info you'd like to see for the genesis block give me a shout!
Edit: Forgot to say I added some info to the home page: total BTS tied up as collateral, asset registration fee (they're currently the same for long and short names, bug maybe?), and max delegate pay.
-
It doesn't work at the moment. The site is up but no data is retrieved.
I've upgraded the site in anticipation of the BTS hardfork, I realize it's a bit early but due to a technical issue I ended up deploying it a little earlier than planned.
If you see anything incorrect please let me know, I think I got everything covered though.
Next feature coming is a plot of BTS supply over time to track inflation.
I've also started working on some genesis analysis, if you have any particular plots or info you'd like to see for the genesis block give me a shout!
Edit: Forgot to say I added some info to the home page: total BTS tied up as collateral, asset registration fee (they're currently the same for long and short names, bug maybe?), and max delegate pay.
Yea something weird happened with the API, not quite sure what. I've restarted it now so it's back up.
-
Please consider to hide/remove totally DNS from page since it will confuse new members/investors...
-
Please consider to hide/remove totally DNS from page since it will confuse new members/investors...
It's gone from the bitsharesblocks.com since yesterday, you might be seeing the cached version still. Try F5 :)
I'll probably take down dns.bitsharesblocks.com soon too, unless someone thinks there's a reason to keep it up?
-
Can you integrate the BTS accounts check up in your website? Then we will know the change trend of top 100, top 1000, etc.
-
Can you integrate the BTS accounts check up in your website? Then we will know the change trend of top 100, top 1000, etc.
You mean the genesis block information?
I've just pushed an update with some genesis stats for BTS and BTSX, you'll find it under "Charts". If you can't see it press F5. Layout's not great etc but I figured I'd put it up since people might find it interesting. If you have any ideas on plots or other stats that could be interesting just let me know.
I've also added the current client version running on the bitsharesblocks server to the footer.
@Xeroc I started working on a way to display an alert with the date for upcoming hardforks, will try to get it up before the next one actually happens :)
-
I've added an alert to the home page that will notify you of any upcoming hardforks, with an estimated date for the block of the hardfork in your local timezone!
-
I've added some info related to inflation and supply that I think a lot of people will find interesting! As always, do F5 if you can't see it.
Firstly, on the homepage in the blockchain box you'll see the supply change over the last 24 hours. This is basically any delegate inflation minus the fees paid in the period.
Secondly I've added "BTS Supply and Fees" to the charts section. In there you'll see plots of the BTS supply change over time as well as total supply over time, and finally the BTS fees paid over time. The scale gets messed up on the fees plot because of some huge fees paid, but you can zoom by simply clicking on the plot and dragging out the zone you want.
What you'll notice is we're already down more than 500,000 BTS since yesterday, this is because of the asset bonanza where people are paying 500 BTS to register a new asset, as well as someone paying 500,000 BTS to register the new asset BANK. We've got 77 new assets since yesterday..
http://bitsharesblocks.com/supply
-
http://bitsharesblocks.com/supply
That link leads to /home for me
going through the menu works though
-
http://bitsharesblocks.com/supply
That link leads to /home for me
going through the menu works though
Probably because you had the old version cached, should work if you click it again now.
-
ha .. interesting ..
working now .. there're still things to learn when it comes to angularJS :)
-
ha .. interesting ..
working now .. there're still things to learn when it comes to angularJS :)
That's not angular I'm afraid, it's simply your browser caching all the files from the site for a given duration (24hrs in this case as indicated by my server), so that when you return to the site it uses this cached version to speed things up. Doing a refresh with F5 will force the browser to download the new files, which are then recached for 24 hrs.
-
ha .. interesting ..
working now .. there're still things to learn when it comes to angularJS :)
That's not angular I'm afraid, it's simply your browser caching all the files from the site for a given duration (24hrs in this case as indicated by my server), so that when you return to the site it uses this cached version to speed things up. Doing a refresh with F5 will force the browser to download the new files, which are then recached for 24 hrs.
Yeha .. but with node/angularJS you are capturing everything after the URL/ and route that through the app .. if the app is cache then it does not know about the "new" route .. that's just my view ..
-
ha .. interesting ..
working now .. there're still things to learn when it comes to angularJS :)
That's not angular I'm afraid, it's simply your browser caching all the files from the site for a given duration (24hrs in this case as indicated by my server), so that when you return to the site it uses this cached version to speed things up. Doing a refresh with F5 will force the browser to download the new files, which are then recached for 24 hrs.
Yeha .. but with node/angularJS you are capturing everything after the URL/ and route that through the app .. if the app is cache then it does not know about the "new" route .. that's just my view ..
Yes you're right, everything is in the app.js so if it's cached the new routes won't work, so it's partly an angular issue I guess ;)
-
I enabled Cloudflare protection for the site yesterday but I'm now seeing some issues with the api. It works fine on my home computer but at work and on my phone I'm not getting a response from the API. Anyone else having issues?
Anyone have experience using Cloudflare and hosting an api behind it? I added a page rule but it doesn't appear to be working. Gonna have to contact their support I think.
-
I enabled Cloudflare protection for the site yesterday but I'm now seeing some issues with the api. It works fine on my home computer but at work and on my phone I'm not getting a response from the API. Anyone else having issues?
Anyone have experience using Cloudflare and hosting an api behind it? I added a page rule but it doesn't appear to be working. Gonna have to contact their support I think.
Yes. I have some issues. It is not opening always for me. It currently works though.
-
not having issues here
-
after much inactivity the homepage returns to DNS homepage!!! (?)
Sent from my ALCATEL ONE TOUCH 997D
-
after much inactivity the homepage returns to DNS homepage!!! (?)
Sent from my ALCATEL ONE TOUCH 997D
Now that is weird!! :)
I think I've managed to fix it, I've changed the port for the api to a port supported by Cloudflare and which has a page rule associated to it. It works fine now from my work computer. If you're still having issues please do a refresh!
-
You're not recognising the colour-coding of version for people who compiled themselves and published from CLI: (orange instead of green)
eg.
v0.4.24-5-g1854346
-
You're not recognising the colour-coding of version for people who compiled themselves and published from CLI: (orange instead of green)
eg.
v0.4.24-5-g1854346
Yea i figured it was better that way because that means you're not using an official release, and might be including features that cause crashes.
We all compile it ourselves BTW, to get the official version you need to do "git checkout v0.4.24" after cloning.
-
(http://i.imgur.com/g6wLe6K.png)
not sure what's wrong here.
- SuSE Linux
- Mozilla/5.0 (X11; Linux x86_64; rv:33.0) Gecko/20100101 Firefox/33.0
-
Yea I saw something like that once in Firefox too. I believe it's related to the .sort() javascript function doing something strange in Firefox, I'll have to look into it again to see if I can reproduce it.
-
Svk, I see the share supply on bitsharesblocks.com is approximately 2.5 billion. Are you planning on adding the ability to measure how much non-vested BTS is currently available? Currently the functionality to withdraw isn't even in the client so the non-vested BTS is approximately 0.5 billion BTS less than the share supply reported by bitsharesblocks.com. But when the functionality to withdraw some amount of the vested stake is later added, the calculation will become more complicated. Are you planning on tracking the amount of vested stake that has been withdrawn and using that to calculate available supply? Actually it would probably be a more fair estimate of available supply to use a formula like ((max(1.0, (number of days since November 5, 2014)/730) * 0.5 billion BTS) + (stake in non-vested balances) - (accumulated stake moved out of vested balances)).
The reason I bring this up is because coinmarketcap seems to be using the 2.5 billion supply figure to calculate market cap now even though that is not the fair "available supply". We are essentially pulling a mini-Ripple at the moment. I think coinmarketcap uses data from bitsharesblocks.com, correct? I think it would be good if we have an appropriate available supply value on bitsharesblocks.com that they could use.
-
Svk, I see the share supply on bitsharesblocks.com is approximately 2.5 billion. Are you planning on adding the ability to measure how much non-vested BTS is currently available? Currently the functionality to withdraw isn't even in the client so the non-vested BTS is approximately 0.5 billion BTS less than the share supply reported by bitsharesblocks.com. But when the functionality to withdraw some amount of the vested stake is later added, the calculation will become more complicated. Are you planning on tracking the amount of vested stake that has been withdrawn and using that to calculate available supply? Actually it would probably be a more fair estimate of available supply to use a formula like ((max(1.0, (number of days since November 5, 2014)/730) * 0.5 billion BTS) + (stake in non-vested balances) - (accumulated stake moved out of vested balances)).
The reason I bring this up is because coinmarketcap seems to be using the 2.5 billion supply figure to calculate market cap now even though that is not the fair "available supply". We are essentially pulling a mini-Ripple at the moment. I think coinmarketcap uses data from bitsharesblocks.com, correct? I think it would be good if we have an appropriate available supply value on bitsharesblocks.com that they could use.
Yes I believe they are using one of my api calls to update their data, but I never got confirmation on that except in the case of assets.
There's no way to distinguish between vested and non-vested balances though, so the only real option IMO is to use your formula for vested supply and do "Total supply - share_drop + unvested_vested_supply. We'd have a supply growing daily for two years from 2 billion to 2.5 billion basically.
I'm not sure it's a good idea though, now that CMC is reporting 2.5 billion I'm for just leaving it like that. I could add a tracker for the amount of vested supply that's become available though.
-
FYI - site doesn't work for me currently…
-
FYI - site doesn't work for me currently…
Most likely cache related from the switch to Cloudflare, I had to tweak some settings and I think it broke on some computers as a result. Try doing shift+F5 to force a refresh, there might also be some localstorage items with CLOUDFLARE in the name that you can delete if you have them.
-
FYI - site doesn't work for me currently…
Most likely cache related from the switch to Cloudflare, I had to tweak some settings and I think it broke on some computers as a result. Try doing shift+F5 to force a refresh, there might also be some localstorage items with CLOUDFLARE in the name that you can delete if you have them.
ok will check it ! FYI you'Re now directly linked on bitshares.org more tab ;)
-
I've just pushed a big update to the site. It includes a lot of things but most notably the translation framework is in place! Currently only English and French are available, I'll make another post with some bounties for translations, probably tomorrow. The update includes but is not limited to:
- Translations!
- Delegate public data fields (ann, bid, description, location, website, handle, role currently supported)
- Various bug fixes and improvements on the backend
- Charting fixes: dates and y axis formatting mainly
- Shorting information now uses the correct formula for amounts
- +++
You might need to force a refresh of the site to get the updates, shift+F5 should do the trick. As always , if you see anything incorrect or have any issues, give me a shout!
-
The asset=USD page misses a closing bracket:
PRICE HISTORY (BTS/bitUSD
-
The asset=USD page misses a closing bracket:
PRICE HISTORY (BTS/bitUSD
Indeed, I'll fix it once I get home.
-
Just a quick point, you might already be aware - the site isn't (fully) accessible from locations where only ports 80 and 443 are open. I presume you have API requests going on a different port? The result is that no data is ever displayed, although the pages themselves load.
-
Just a quick point, you might already be aware - the site isn't (fully) accessible from locations where only ports 80 and 443 are open. I presume you have API requests going on a different port? The result is that no data is ever displayed, although the pages themselves load.
Yea that makes sense since the API calls are on a different port. I'm running the site with apache on port 80 but I've been considering switching it over to nginx and also creating a proxy to funnel api calls through something like api.bitsharesblocks.com as well, that would work right?
-
svk, for some reason http://www.bitsharesblocks.com/delegates is filtering out certain delegates from the table such as dev0.nikolai (rank 2), dev.bitsharesblocks (rank 30), and dev-metaexchange.monsterer (rank 67). They are included in the JSON returned by the API, just filtered out by the UI.
The only thing I see that they have in common that other delegates that aren't filtered out don't is that their names all start with a "dev". I think the offending part of the code is in the "render" method of "reactDelegates" class that filters the parsed JSON using the following predicate:
function (a) {
return a.name.toLowerCase().indexOf("dev")
}
-
svk, for some reason http://www.bitsharesblocks.com/delegates is filtering out certain delegates from the table such as dev0.nikolai (rank 2), dev.bitsharesblocks (rank 30), and dev-metaexchange.monsterer (rank 67). They are included in the JSON returned by the API, just filtered out by the UI.
The only thing I see that they have in common that other delegates that aren't filtered out don't is that their names all start with a "dev". I think the offending part of the code is in the "render" method of "reactDelegates" class that filters the parsed JSON using the following predicate:
function (a) {
return a.name.toLowerCase().indexOf("dev")
}
Haha you're right of course, before pushing it to live I was testing filtering performance, I forgot to comment it out before pushing it. In my defense it was 1am so I was a bit tired! Fixed now, thanks.
-
Yea that makes sense since the API calls are on a different port. I'm running the site with apache on port 80 but I've been considering switching it over to nginx and also creating a proxy to funnel api calls through something like api.bitsharesblocks.com as well, that would work right?
As long as everything is on port 80/443, you'll be fine so having a sub-domain for the api makes perfect sense :)
-
(http://i.imgur.com/pJXl6Fd.png)
doesn't make sense to me .. the red color just looks bad :)
-
Interesting.. BTSBOTS's batch market transactions are identified as 'Ask'?
BTW transaction types should include 'cancel an order'.
-
Interesting.. BTSBOTS's batch market transactions are identified as 'Ask'?
BTW transaction types should include 'cancel an order'.
Yes, alt uses a batch order type that results in a transaction json that is a big mess, and I haven't yet taken the time to figure out how to properly parse those transactions. Inside each transaction he makes there are multiple asks and bids, here's an example:
"operations" : [
{
"type" : "ask_op_type",
"data" : {
"amount" : -5647295378,
"ask_index" : {
"order_price" : {
"ratio" : "0.009116877267",
"quote_asset_id" : 14,
"base_asset_id" : 0
},
"owner" : "BTSEzmSPTwQys6AgdJFjLoTioVdLXMWujPzY"
}
}
},
{
"type" : "bid_op_type",
"data" : {
"amount" : -7260131,
"bid_index" : {
"order_price" : {
"ratio" : "0.0086060402284",
"quote_asset_id" : 14,
"base_asset_id" : 0
},
"owner" : "BTSEzmSPTwQys6AgdJFjLoTioVdLXMWujPzY"
}
}
},
{
"type" : "bid_op_type",
"data" : {
"amount" : -6771472,
"bid_index" : {
"order_price" : {
"ratio" : "0.0014288611238",
"quote_asset_id" : 22,
"base_asset_id" : 0
},
"owner" : "BTSEzmSPTwQys6AgdJFjLoTioVdLXMWujPzY"
}
}
},
{
"type" : "ask_op_type",
"data" : {
"amount" : -5647295378,
"ask_index" : {
"order_price" : {
"ratio" : "0.0014841017886",
"quote_asset_id" : 22,
"base_asset_id" : 0
},
"owner" : "BTSEzmSPTwQys6AgdJFjLoTioVdLXMWujPzY"
}
}
},
{
"type" : "ask_op_type",
"data" : {
"amount" : -9035672605,
"ask_index" : {
"order_price" : {
"ratio" : "0.000963457088546",
"quote_asset_id" : 250,
"base_asset_id" : 0
},
"owner" : "BTSEzmSPTwQys6AgdJFjLoTioVdLXMWujPzY"
}
}
},
{
"type" : "bid_op_type",
"data" : {
"amount" : -21169369,
"bid_index" : {
"order_price" : {
"ratio" : "0.000920771559878",
"quote_asset_id" : 250,
"base_asset_id" : 0
},
"owner" : "BTSEzmSPTwQys6AgdJFjLoTioVdLXMWujPzY"
}
}
},
{
"type" : "bid_op_type",
"data" : {
"amount" : -382936,
"bid_index" : {
"order_price" : {
"ratio" : "0.0000872081983",
"quote_asset_id" : 6,
"base_asset_id" : 0
},
"owner" : "BTSEzmSPTwQys6AgdJFjLoTioVdLXMWujPzY"
}
}
},
{
"type" : "ask_op_type",
"data" : {
"amount" : -270875539,
"ask_index" : {
"order_price" : {
"ratio" : "0.0000911262779",
"quote_asset_id" : 6,
"base_asset_id" : 0
},
"owner" : "BTSEzmSPTwQys6AgdJFjLoTioVdLXMWujPzY"
}
}
},
{
"type" : "ask_op_type",
"data" : {
"amount" : -1129459075,
"ask_index" : {
"order_price" : {
"ratio" : "0.0012568445525",
"quote_asset_id" : 21,
"base_asset_id" : 0
},
"owner" : "BTSEzmSPTwQys6AgdJFjLoTioVdLXMWujPzY"
}
}
},
{
"type" : "bid_op_type",
"data" : {
"amount" : -122032,
"bid_index" : {
"order_price" : {
"ratio" : "10.39636579435647",
"quote_asset_id" : 250,
"base_asset_id" : 6
},
"owner" : "BTSEzmSPTwQys6AgdJFjLoTioVdLXMWujPzY"
}
}
},
{
"type" : "ask_op_type",
"data" : {
"amount" : -63822,
"ask_index" : {
"order_price" : {
"ratio" : "10.73746535796045",
"quote_asset_id" : 250,
"base_asset_id" : 6
},
"owner" : "BTSEzmSPTwQys6AgdJFjLoTioVdLXMWujPzY"
}
}
},
{
"type" : "bid_op_type",
"data" : {
"amount" : -773230,
"bid_index" : {
"order_price" : {
"ratio" : "0.75377827493836",
"quote_asset_id" : 250,
"base_asset_id" : 21
},
"owner" : "BTSEzmSPTwQys6AgdJFjLoTioVdLXMWujPzY"
}
}
},
{
"type" : "bid_op_type",
"data" : {
"amount" : -5292342,
"bid_index" : {
"order_price" : {
"ratio" : "0.10391519935325",
"quote_asset_id" : 250,
"base_asset_id" : 14
},
"owner" : "BTSEzmSPTwQys6AgdJFjLoTioVdLXMWujPzY"
}
}
},
{
"type" : "bid_op_type",
"data" : {
"amount" : -4103872,
"bid_index" : {
"order_price" : {
"ratio" : "0.63835386897072",
"quote_asset_id" : 250,
"base_asset_id" : 22
},
"owner" : "BTSEzmSPTwQys6AgdJFjLoTioVdLXMWujPzY"
}
}
},
{
"type" : "ask_op_type",
"data" : {
"amount" : -1128578,
"ask_index" : {
"order_price" : {
"ratio" : "0.65534361043162",
"quote_asset_id" : 250,
"base_asset_id" : 22
},
"owner" : "BTSEzmSPTwQys6AgdJFjLoTioVdLXMWujPzY"
}
}
},
{
"type" : "bid_op_type",
"data" : {
"amount" : 7259168,
"bid_index" : {
"order_price" : {
"ratio" : "0.0086945299727",
"quote_asset_id" : 14,
"base_asset_id" : 0
},
"owner" : "BTSEzmSPTwQys6AgdJFjLoTioVdLXMWujPzY"
}
}
},
{
"type" : "ask_op_type",
"data" : {
"amount" : 5589250291,
"ask_index" : {
"order_price" : {
"ratio" : "0.0091209892616",
"quote_asset_id" : 14,
"base_asset_id" : 0
},
"owner" : "BTSEzmSPTwQys6AgdJFjLoTioVdLXMWujPzY"
}
}
},
{
"type" : "bid_op_type",
"data" : {
"amount" : 6771317,
"bid_index" : {
"order_price" : {
"ratio" : "0.0014436337606",
"quote_asset_id" : 22,
"base_asset_id" : 0
},
"owner" : "BTSEzmSPTwQys6AgdJFjLoTioVdLXMWujPzY"
}
}
},
{
"type" : "ask_op_type",
"data" : {
"amount" : 5589250291,
"ask_index" : {
"order_price" : {
"ratio" : "0.0014847321116",
"quote_asset_id" : 22,
"base_asset_id" : 0
},
"owner" : "BTSEzmSPTwQys6AgdJFjLoTioVdLXMWujPzY"
}
}
},
{
"type" : "bid_op_type",
"data" : {
"amount" : 20977584,
"bid_index" : {
"order_price" : {
"ratio" : "0.000929923741666",
"quote_asset_id" : 250,
"base_asset_id" : 0
},
"owner" : "BTSEzmSPTwQys6AgdJFjLoTioVdLXMWujPzY"
}
}
},
{
"type" : "ask_op_type",
"data" : {
"amount" : 8942800466,
"ask_index" : {
"order_price" : {
"ratio" : "0.000955159170799",
"quote_asset_id" : 250,
"base_asset_id" : 0
},
"owner" : "BTSEzmSPTwQys6AgdJFjLoTioVdLXMWujPzY"
}
}
},
{
"type" : "bid_op_type",
"data" : {
"amount" : 382936,
"bid_index" : {
"order_price" : {
"ratio" : "0.000088110026",
"quote_asset_id" : 6,
"base_asset_id" : 0
},
"owner" : "BTSEzmSPTwQys6AgdJFjLoTioVdLXMWujPzY"
}
}
},
{
"type" : "ask_op_type",
"data" : {
"amount" : 300609899,
"ask_index" : {
"order_price" : {
"ratio" : "0.0000911632181",
"quote_asset_id" : 6,
"base_asset_id" : 0
},
"owner" : "BTSEzmSPTwQys6AgdJFjLoTioVdLXMWujPzY"
}
}
},
{
"type" : "ask_op_type",
"data" : {
"amount" : 1117850058,
"ask_index" : {
"order_price" : {
"ratio" : "0.0012572913187",
"quote_asset_id" : 21,
"base_asset_id" : 0
},
"owner" : "BTSEzmSPTwQys6AgdJFjLoTioVdLXMWujPzY"
}
}
},
{
"type" : "bid_op_type",
"data" : {
"amount" : 135437,
"bid_index" : {
"order_price" : {
"ratio" : "10.39270968600078",
"quote_asset_id" : 250,
"base_asset_id" : 6
},
"owner" : "BTSEzmSPTwQys6AgdJFjLoTioVdLXMWujPzY"
}
}
},
{
"type" : "ask_op_type",
"data" : {
"amount" : 63822,
"ask_index" : {
"order_price" : {
"ratio" : "10.64018828233291",
"quote_asset_id" : 250,
"base_asset_id" : 6
},
"owner" : "BTSEzmSPTwQys6AgdJFjLoTioVdLXMWujPzY"
}
}
},
{
"type" : "bid_op_type",
"data" : {
"amount" : 773230,
"bid_index" : {
"order_price" : {
"ratio" : "0.75355078431618",
"quote_asset_id" : 250,
"base_asset_id" : 21
},
"owner" : "BTSEzmSPTwQys6AgdJFjLoTioVdLXMWujPzY"
}
}
},
{
"type" : "bid_op_type",
"data" : {
"amount" : 5244395,
"bid_index" : {
"order_price" : {
"ratio" : "0.10387391456867",
"quote_asset_id" : 250,
"base_asset_id" : 14
},
"owner" : "BTSEzmSPTwQys6AgdJFjLoTioVdLXMWujPzY"
}
}
},
{
"type" : "bid_op_type",
"data" : {
"amount" : 4103871,
"bid_index" : {
"order_price" : {
"ratio" : "0.63811703937197",
"quote_asset_id" : 250,
"base_asset_id" : 22
},
"owner" : "BTSEzmSPTwQys6AgdJFjLoTioVdLXMWujPzY"
}
}
},
{
"type" : "ask_op_type",
"data" : {
"amount" : 1128552,
"ask_index" : {
"order_price" : {
"ratio" : "0.64940796753075",
"quote_asset_id" : 250,
"base_asset_id" : 22
},
"owner" : "BTSEzmSPTwQys6AgdJFjLoTioVdLXMWujPzY"
}
}
},
{
"type" : "deposit_op_type",
"data" : {
"amount" : 190826970,
"condition" : {
"asset_id" : 0,
"slate_id" : 0,
"type" : "withdraw_signature_type",
"data" : {
"owner" : "BTSEzmSPTwQys6AgdJFjLoTioVdLXMWujPzY",
"memo" : null
}
}
}
},
{
"type" : "deposit_op_type",
"data" : {
"amount" : 963,
"condition" : {
"asset_id" : 14,
"slate_id" : 0,
"type" : "withdraw_signature_type",
"data" : {
"owner" : "BTSEzmSPTwQys6AgdJFjLoTioVdLXMWujPzY",
"memo" : null
}
}
}
},
{
"type" : "deposit_op_type",