BitShares Forum
Main => Stakeholder Proposals => Topic started by: roadscape on February 19, 2016, 03:32:31 am
-
I've spent a lot of time on the block explorer (https://cryptofresh.com/) since the launch of 2.0. It brings me great joy to be able to unearth some of the inner workings of Graphene and to share them with the community. Especially with the governance features, I considered it critically important to have a public frontend for voting & committee data, and that's what I built. It was low priority for the wallet, and an ideal task for the block explorer. I am particularly proud of the voting report page (https://cryptofresh.com/ballots) -- it's far from perfect but I would love to work more on this report (and others) and it's a good example of how I can transform rich yet ugly data into something beautiful. And this was just the start..
My goal for the block explorer is to provide maximum utility to the BitShares community as a whole. This is to be accomplished by (1) providing useful reports (especially governance), visualizations, and data aggregation; (2) forming a social hub and information source; and (3) serving as an educational portal while also highlighting our unique selling points.
Block Explorer
Graphene serves an endless supply of data and it's worth it to expose as much of it as possible. As more apps are built on the chain, I plan to expand the site to work with the new data streams. The block explorer serves as a prominent face of BitShares and the pages must be adjusted for wider audiences as our network grows. It will always offer things the wallets can't.. the features from many apps & wallets can be unified as one searchable portal.
Upcoming Features
- Better assets list - add volume, price data, sorting. it should look a lot like CMC.
- Improved asset markets - been waiting for updated APIs, which were just released (https://github.com/cryptonomex/graphene/blob/f7bfcea355b77cd07d0eee0963e8dea0935d3dbc/libraries/app/include/graphene/app/database_api.hpp#L365-L400)!
- Unified search - quickly look up any user, asset, transaction, or block
- More graphs & reports - balances claimed, usage stats, fee income, etc
- Proposals index - all past/upcoming proposed transactions (committee and otherwise)
- Translations - to be a true hub, we need to support more languages
API Development
I've received many requests from developers for various APIs, though I haven't had time to add them all or document any. There's a big void in this space and the block explorer is perfectly poised to fill it. The API is another aspect I've held back on because it's not profitable. Yet developer-friendly API's would be a big step forward in lowering the barrier of entry to BitShares.
Graphene is a very powerful database but its minimal approach means concession of indexes and its initial API methods are a bit limiting. This block explorer uses multiple approaches to extract all the useful data efficiently and allow for queries against it. Providing public access to this data has value but running a documented endpoint comes with responsibility. So ultimately this will need to be an open-source and distributed effort (I'll author a Rails gem + minimal http API app for this worker).
Social Network
Bulletin boards and social networks on our own blockchain are something I'm particularly excited about. I've built a working MVP that allows you to publish posts on the blockchain, and I'll need your help to test it soon. Here's a sneak peek: http://cryptofresh.com/posts
On this prototype you can author posts on the blockchain as well as tip posts (off-chain). It will be ready for public testing this week. This approach uses custom operations, but it supports multiple message sources--meaning it's ready to grow as a content aggregator across a variety of apps running on BitShares. It's already compatible with the "public memo" approach used by the announce (https://cryptofresh.com/u/announce) feature.
Now that we have shown a minimum viable way for accounts to login and submit public messages, it opens many interesting possibilities:
- threaded forum / message board
- community map
- local bitshares
- advertising
- job board
- sharing of PGP keys
- coin-weighed polls
- reputation / feedback
- donation-tracking pages
- dedicated fundraiser pages
- stores & digital downloads
- federated social networks
- "stack exchange" style network
A lot of these features are low-hanging fruit for the Cryptofresh platform. Any of this stuff could be integrated into the wallet or into the witness_node directly, but it's magnitudes easier to test it on our platform.
Worker
I hope that by delivering the initial block explorer features up front I've demonstrated the value and commitment I can bring.
I release my previous work on the block explorer at no cost to the community, but for the next stage I would like to go with a worker proposal. I am requesting 30,000 BTS per day from 3/1 - 5/31 to work towards the goals and priorities outlined in this document, at a rate of 20 hours per week. The pay will vest for 90 days. I will release the block explorer as open-source under MIT license when this worker has been funded in full.
Most of my work is front-end/UI-oriented, so it will be easy for you to watch the progress. I will also provide regular updates.
Witness Resignation
I would also like to take this opportunity to announce that I no longer wish to run a witness node.
Please unvote witness roadscape when you cast your vote for the worker!
Thanks,
roadscape
create_worker roadscape "2016-03-01T00:00:00" "2016-05-31T23:59:59" 3000000000 "Blockchain Explorer and API Development" "https://bitsharestalk.org/index.php/topic,21532.0.html" {"type":"vesting","pay_vesting_period_days":90} false
Blockchain Explorer and API Development (1.14.33)
https://cryptofresh.com/workers
-
+5%
-
You have my full support. Thanks for all your efforts in giving to this community.
-
Great trackrecord, plans look great, rate reasonable, full support! +5%
-
You have my support! Your block explorer has been an invaluable resource to me and everyone else.
I hope you aren't resigning your witness position because of this worker.
-
will release the block explorer as open-source under MIT license when this worker has been funded in full.
I hope your work will be transparent from the beginning.
Releasing it when it is fully funded is not reasonable.
If you got voted out at half way shareholders must have always access to your work.
-
Thanks guys for the support, it means a lot!
@bytemaster No, not specifically anyway.. i'm resigning the witness either way to devote my full attention to upcoming projects.
@btswolf This is not a simple matter. It's a series of tradeoffs.. in the interest of keeping the daily pay as low as possible, I had to push out the release. The ideas within Cryptofresh are more valuable than the code itself, and also I don't think it's reasonable to expect months of work plus all the code for free. Keep in mind that after only 3 months of pay, I will be releasing 6 months-worth of work. I will be cleaning/refactoring the code before releasing the whole package. The refactoring effort will also result in a new repository (the core API layer I described in the post) that I plan to release earlier.
If anyone needs help with their Ruby/Rails app I would be more than happy to assist.
-
will release the block explorer as open-source under MIT license when this worker has been funded in full.
I hope your work will be transparent from the beginning.
Releasing it when it is fully funded is not reasonable.
If you got voted out at half way shareholders must have always access to your work.
You are already using the work, have you been to the cryptofresh site?? This is the problem with people. If you do the work for free, people expect to you keep working for free. If you ask for money, they ignore all the work you have already done.
-
will release the block explorer as open-source under MIT license when this worker has been funded in full.
I hope your work will be transparent from the beginning.
Releasing it when it is fully funded is not reasonable.
If you got voted out at half way shareholders must have always access to your work.
You are already using the work, have you been to the cryptofresh site?? This is the problem with people. If you do the work for free, people expect to you keep working for free. If you ask for money, they ignore all the work you have already done.
Maybe you have to clean your glasses because I didn`t wrote nor think anything you seem to believe to read between the lines!
-
I don't see it on the worker's tab. Can't vote for it.
-
I don't see it on the worker's tab. Can't vote for it.
Go back and forth between tabs and you'll see it.
Edit: but you can't vote right now anyway due to the extensions bug..
-
+5% Thank you for your work.
-
will you opensource the code?
-
will you opensource the code?
He said MIT
-
An early demo of the cryptofresh Post feature, and a call for testers:
https://cryptofresh.com/posts
After logging in with your BitShares account, and can write posts directly on the blockchain.
New posts will appear on the page as they come in, creating a realtime chat experience.
Each account starts out with 100 test credits. Posts consume 5 credits (or more, depending on post length). Tips consume 5 test credits. This is to prevent spam and also a fun experiment. I am working towards a more convenient model but this allows us to start testing right away.
There are 3 main features in play:
1) Logging in
2) Posting
3) Tipping
Replying is not yet functional (but mostly implemented in the backend). Feedback welcome & let me know if anything breaks! :D
-
An early demo of the cryptofresh Post feature, and a call for testers:
https://cryptofresh.com/posts
After logging in with your BitShares account, and can write posts directly on the blockchain.
New posts will appear on the page as they come in, creating a realtime chat experience.
Each account starts out with 100 test credits. Posts consume 5 credits (or more, depending on post length). Tips consume 5 test credits. This is to prevent spam and also a fun experiment. I am working towards a more convenient model but this allows us to start testing right away.
There are 3 main features in play:
1) Logging in
2) Posting
3) Tipping
Replying is not yet functional (but mostly implemented in the backend). Feedback welcome & let me know if anything breaks! :D
nice!
i got confused in the beginning, because i thought you want my BTS password. i know most of customers are stupid, so maybe you should explicid state "don't use your Bitshares account password"
-
Thanks for testing guys, glad to see it's working smoothly!
An early demo of the cryptofresh Post feature, and a call for testers:
https://cryptofresh.com/posts
After logging in with your BitShares account, and can write posts directly on the blockchain.
New posts will appear on the page as they come in, creating a realtime chat experience.
Each account starts out with 100 test credits. Posts consume 5 credits (or more, depending on post length). Tips consume 5 test credits. This is to prevent spam and also a fun experiment. I am working towards a more convenient model but this allows us to start testing right away.
There are 3 main features in play:
1) Logging in
2) Posting
3) Tipping
Replying is not yet functional (but mostly implemented in the backend). Feedback welcome & let me know if anything breaks! :D
nice!
i got confused in the beginning, because i thought you want my BTS password. i know most of customers are stupid, so maybe you should explicid state "don't use your Bitshares account password"
Ah, this is a good point, I changed it to say "Set your Cryptofresh password", hope that helps clear it up!
-
An early demo of the cryptofresh Post feature, and a call for testers:
https://cryptofresh.com/posts
After logging in with your BitShares account, and can write posts directly on the blockchain.
New posts will appear on the page as they come in, creating a realtime chat experience.
Each account starts out with 100 test credits. Posts consume 5 credits (or more, depending on post length). Tips consume 5 test credits. This is to prevent spam and also a fun experiment. I am working towards a more convenient model but this allows us to start testing right away.
There are 3 main features in play:
1) Logging in
2) Posting
3) Tipping
Replying is not yet functional (but mostly implemented in the backend). Feedback welcome & let me know if anything breaks! :D
This is where it starts getting real interesting... ;)
Y'all don't even know what this cat is capable of... though perhaps some suspect.
It's just like you to hide this epic development here in the worker proposal thread.
Mad respect for you Roadscape! You're driven, and adept in a way that so few are... This community is lucky to have you.
“Man cannot discover new oceans unless he has the courage to lose sight of the shore.”
― André Gide
-
All we need now is a guerrilla team that advertises this particular feature and does a little marketing!
-
I don't see it on the worker's tab. Can't vote for it.
Go back and forth between tabs and you'll see it.
Edit: but you can't vote right now anyway due to the extensions bug..
The worker still does not show up in the GUI.
@svk , will it be fixed in the next GUI release?
(http://i.imgur.com/1coRrnW.png)
-
I don't see it on the worker's tab. Can't vote for it.
Go back and forth between tabs and you'll see it.
Edit: but you can't vote right now anyway due to the extensions bug..
The worker still does not show up in the GUI.
@svk , will it be fixed in the next GUI release?
(http://i.imgur.com/1coRrnW.png)
It's simply because there's no api call for fetching workers so I need to iterate over the worker id's, sometimes they resolve fast enough that all the workers show up in the list, sometimes they don't.
There's a very easy way to fix this though, just go to a different tab then back again and you'll see all the workers. Perhaps I can add a hack to force an update after x amount of time, but it probably won't be 100% reliable anyway.
-
All we need now is a guerrilla team that advertises this particular feature and does a little marketing!
All in due time.. :)
-
All we need now is a guerrilla team that advertises this particular feature and does a little marketing!
All in due time.. :)
You know the best way to create an ARMY of these people? Hint...a sharebot that enables other bots on the internet to call upon its functionality to share an FBA for various features...maybe this one? ;)
-
Update:
This week I've focused on polling and aggregating market pair data. This is quite useful and makes it possible to move forward with many of the requested views and APIs. I plan to push the initial changes to production today, along with one redesigned view (asset list). Next week will have more UI updates that take advantage of this new data source!
-
I was hoping to break into the new market API's but they aren't available from my existing RPC connection, so instead I focused on mapping out all the active markets and extracting/indexing the interesting bits. It's something that was preventing me from moving forward on several fronts.
Here's the first page redesign utilizing the new data: https://cryptofresh.com/assets
Next week I'll work on asset detail page improvements (view and select different markets, and minor UI enhance), as well as on connecting to the new APIs that allow me to pull the % change, top bid/ask, etc for markets (or upgrading the platform/schema to accomplish the same thing).
-
today the asset page shows for USD "low volume" but this is not correct, maybe something is not right.
-
today the asset page shows for USD "low volume" but this is not correct, maybe something is not right.
This does seem strange.. but as far as I can tell, USD has simply not been traded in the last 24 hours.
-
Nevermind, I did see some USD trades go through.. looking into it..
-
@Shentist Ok.. fixed! The issue was with the wallet's market history API.. it's supposed to track the latest 200 buckets, but it seems to only track the first 200 buckets. So as a hack a few months ago, I modified my node to track 1000 buckets. And as of a few days ago the BTS-USD market reached 1000 1-hour buckets.. leading to a cutoff of new data.
So now... I track 2000 buckets. 8)
-
@Shentist Ok.. fixed! The issue was with the wallet's market history API.. it's supposed to track the latest 200 buckets, but it seems to only track the first 200 buckets. So as a hack a few months ago, I modified my node to track 1000 buckets. And as of a few days ago the BTS-USD market reached 1000 1-hour buckets.. leading to a cutoff of new data.
So now... I track 2000 buckets. 8)
Interesting :)
-
This week I focused on improving the asset pages. It's not finished but this is all useful market data so I figure I'd release the work in progress sooner than later:
https://cryptofresh.com/a/USD
https://cryptofresh.com/a/MKR_OPEN.BTC
Feedback is appreciated, especially from a trader's perspective.. Any units to flip? Any obvious missing data?
I've also been setting up a new development environment so I can perform more testing with witness_node RPC and websocket connections, and just to generally isolate any experiments. In this environment I will also attempt to reproduce the cli_wallet failures that cryptofresh experienced last night to see if I can gleam any more information on the root cause in a less frantic setting.
Aside from backend and maintenance work, the next feature I'd like to add is a 'universal instant search' to quickly locate accounts, assets, and transactions. I'll begin work on that next week.
-
Great!
-
This week I finished setting up a new dev environment.. I'm now just testing to see if I can get it to crash with compression enabled again; I'm still not sure if the cli_wallet crash last week was due to compression or some other factor.. but once it runs solid for a few days I'll update the production node.
Also, I added an instant search feature, it's at the top of every page:
https://cryptofresh.com/
Next week I plan to update the voting report.. the hardfork is changing some voting logic and it could use an update at any rate. Plus another task or two off the backlog.
-
This week I focused on improving the asset pages. It's not finished but this is all useful market data so I figure I'd release the work in progress sooner than later:
https://cryptofresh.com/a/USD
https://cryptofresh.com/a/MKR_OPEN.BTC
Feedback is appreciated, especially from a trader's perspective.. Any units to flip? Any obvious missing data?
Really nice!
I think the current feed price should be in a more prominent position. Is there a plan for transaction history? What does the top 250 accounts mean?
-
This week I focused on improving the asset pages. It's not finished but this is all useful market data so I figure I'd release the work in progress sooner than later:
https://cryptofresh.com/a/USD
https://cryptofresh.com/a/MKR_OPEN.BTC
Feedback is appreciated, especially from a trader's perspective.. Any units to flip? Any obvious missing data?
Really nice!
I think the current feed price should be in a more prominent position. Is there a plan for transaction history? What does the top 250 accounts mean?
Thanks @cube, feed price is the same thing as "settlement price" price, correct? I've added it above "Details" pane on the right side for now.
Transaction history - you mean to show latest transfers? Or market orders history? Market order history is definitely something I'd like to add there, it's just part of the new API I haven't accessed yet.
Top 250 accounts means "250 accounts with the highest balances and/or debts in this asset" (i.e. the most interesting)
-
This week I focused on improving the asset pages. It's not finished but this is all useful market data so I figure I'd release the work in progress sooner than later:
https://cryptofresh.com/a/USD
https://cryptofresh.com/a/MKR_OPEN.BTC
Feedback is appreciated, especially from a trader's perspective.. Any units to flip? Any obvious missing data?
Really nice!
I think the current feed price should be in a more prominent position. Is there a plan for transaction history? What does the top 250 accounts mean?
Thanks @cube, feed price is the same thing as "settlement price" price, correct? I've added it above "Details" pane on the right side for now.
Transaction history - you mean to show latest transfers? Or market orders history? Market order history is definitely something I'd like to add there, it's just part of the new API I haven't accessed yet.
Top 250 accounts means "250 accounts with the highest balances and/or debts in this asset" (i.e. the most interesting)
Yes, the fed price is the 'settlement price' in the GUI. Settlement price in CF is showing '--'.
Transaction history = 'transacted order history'. Does market order history means that?
The top 250-account list is lumping the highest balances and debts together and this can be confusing. Can it be separately ranked (ie top in balance OR top in debt)?
-
This week I focused on improving the asset pages. It's not finished but this is all useful market data so I figure I'd release the work in progress sooner than later:
https://cryptofresh.com/a/USD
https://cryptofresh.com/a/MKR_OPEN.BTC
Feedback is appreciated, especially from a trader's perspective.. Any units to flip? Any obvious missing data?
Really nice!
I think the current feed price should be in a more prominent position. Is there a plan for transaction history? What does the top 250 accounts mean?
Thanks @cube, feed price is the same thing as "settlement price" price, correct? I've added it above "Details" pane on the right side for now.
Transaction history - you mean to show latest transfers? Or market orders history? Market order history is definitely something I'd like to add there, it's just part of the new API I haven't accessed yet.
Top 250 accounts means "250 accounts with the highest balances and/or debts in this asset" (i.e. the most interesting)
Yes, the fed price is the 'settlement price' in the GUI. Settlement price in CF is showing '--'.
Transaction history = 'transacted order history'. Does market order history means that?
The top 250-account list is lumping the highest balances and debts together and this can be confusing. Can it be separately ranked (ie top in balance OR top in debt)?
Ah, there's actually 2 'settlement prices' -- the 2nd one is part of the "Global settle" feature, and currently only applies to RUB/SEK. But I did add "Price feed" at the top of the right-hand pane. I'll try to clear this up to make it look better though.
And yep, that's what I meant by market order history.
As for the top 250 list, I see what you mean. Maybe it is best to split it into two tables? One for debt positions, the other for balance+orders+collateral balance. Should I combine "Orders" and "Collateral" fields? Or keep them separate?
-
This week I focused on improving the asset pages. It's not finished but this is all useful market data so I figure I'd release the work in progress sooner than later:
https://cryptofresh.com/a/USD
https://cryptofresh.com/a/MKR_OPEN.BTC
Feedback is appreciated, especially from a trader's perspective.. Any units to flip? Any obvious missing data?
Really nice!
I think the current feed price should be in a more prominent position. Is there a plan for transaction history? What does the top 250 accounts mean?
Thanks @cube, feed price is the same thing as "settlement price" price, correct? I've added it above "Details" pane on the right side for now.
Transaction history - you mean to show latest transfers? Or market orders history? Market order history is definitely something I'd like to add there, it's just part of the new API I haven't accessed yet.
Top 250 accounts means "250 accounts with the highest balances and/or debts in this asset" (i.e. the most interesting)
Yes, the fed price is the 'settlement price' in the GUI. Settlement price in CF is showing '--'.
Transaction history = 'transacted order history'. Does market order history means that?
The top 250-account list is lumping the highest balances and debts together and this can be confusing. Can it be separately ranked (ie top in balance OR top in debt)?
Ah, there's actually 2 'settlement prices' -- the 2nd one is part of the "Global settle" feature, and currently only applies to RUB/SEK. But I did add "Price feed" at the top of the right-hand pane. I'll try to clear this up to make it look better though.
And yep, that's what I meant by market order history.
As for the top 250 list, I see what you mean. Maybe it is best to split it into two tables? One for debt positions, the other for balance+orders+collateral balance. Should I combine "Orders" and "Collateral" fields? Or keep them separate?
I see that 'fee price' now. If this information is right above the price chart, it would be easier for the user to compare it with the chart. I think the feed price should be in the same base term as the price chart.
IMHO, balance+orders should be a chart by itself and making collateral another chart.
-
This week I focused on improving the asset pages. It's not finished but this is all useful market data so I figure I'd release the work in progress sooner than later:
https://cryptofresh.com/a/USD
https://cryptofresh.com/a/MKR_OPEN.BTC
Feedback is appreciated, especially from a trader's perspective.. Any units to flip? Any obvious missing data?
Really nice!
I think the current feed price should be in a more prominent position. Is there a plan for transaction history? What does the top 250 accounts mean?
Thanks @cube, feed price is the same thing as "settlement price" price, correct? I've added it above "Details" pane on the right side for now.
Transaction history - you mean to show latest transfers? Or market orders history? Market order history is definitely something I'd like to add there, it's just part of the new API I haven't accessed yet.
Top 250 accounts means "250 accounts with the highest balances and/or debts in this asset" (i.e. the most interesting)
Yes, the fed price is the 'settlement price' in the GUI. Settlement price in CF is showing '--'.
Transaction history = 'transacted order history'. Does market order history means that?
The top 250-account list is lumping the highest balances and debts together and this can be confusing. Can it be separately ranked (ie top in balance OR top in debt)?
Ah, there's actually 2 'settlement prices' -- the 2nd one is part of the "Global settle" feature, and currently only applies to RUB/SEK. But I did add "Price feed" at the top of the right-hand pane. I'll try to clear this up to make it look better though.
And yep, that's what I meant by market order history.
As for the top 250 list, I see what you mean. Maybe it is best to split it into two tables? One for debt positions, the other for balance+orders+collateral balance. Should I combine "Orders" and "Collateral" fields? Or keep them separate?
I see that 'fee price' now. If this information is right above the price chart, it would be easier for the user to compare it with the chart. I think the feed price should be in the same base term as the price chart.
IMHO, balance+orders should be a chart by itself and making collateral another chart.
On OL they have Settlement Price line right on the chart, would that be preferable?
Shouldn't collateral be counted as a type of "order"? Because we already have a table that lists full collateral+debt positions, ordered by collateral ratio. If someone has 1M BTS locked up to create USD, would you expect to see this 1M BTS reflected on the "richlist"?
-
This week I focused on improving the asset pages. It's not finished but this is all useful market data so I figure I'd release the work in progress sooner than later:
https://cryptofresh.com/a/USD
https://cryptofresh.com/a/MKR_OPEN.BTC
Feedback is appreciated, especially from a trader's perspective.. Any units to flip? Any obvious missing data?
Really nice!
I think the current feed price should be in a more prominent position. Is there a plan for transaction history? What does the top 250 accounts mean?
Thanks @cube, feed price is the same thing as "settlement price" price, correct? I've added it above "Details" pane on the right side for now.
Transaction history - you mean to show latest transfers? Or market orders history? Market order history is definitely something I'd like to add there, it's just part of the new API I haven't accessed yet.
Top 250 accounts means "250 accounts with the highest balances and/or debts in this asset" (i.e. the most interesting)
Yes, the fed price is the 'settlement price' in the GUI. Settlement price in CF is showing '--'.
Transaction history = 'transacted order history'. Does market order history means that?
The top 250-account list is lumping the highest balances and debts together and this can be confusing. Can it be separately ranked (ie top in balance OR top in debt)?
Ah, there's actually 2 'settlement prices' -- the 2nd one is part of the "Global settle" feature, and currently only applies to RUB/SEK. But I did add "Price feed" at the top of the right-hand pane. I'll try to clear this up to make it look better though.
And yep, that's what I meant by market order history.
As for the top 250 list, I see what you mean. Maybe it is best to split it into two tables? One for debt positions, the other for balance+orders+collateral balance. Should I combine "Orders" and "Collateral" fields? Or keep them separate?
I see that 'fee price' now. If this information is right above the price chart, it would be easier for the user to compare it with the chart. I think the feed price should be in the same base term as the price chart.
IMHO, balance+orders should be a chart table by itself and making collateral another chart table.
On OL they have Settlement Price line right on the chart, would that be preferable?
Shouldn't collateral be counted as a type of "order"? Because we already have a table that lists full collateral+debt positions, ordered by collateral ratio. If someone has 1M BTS locked up to create USD, would you expect to see this 1M BTS reflected on the "richlist"?
Having it on the chart would be nice.
Sorry, I meant two tables and not charts. The collateral table will show the 1M-bts-locked-up guy in the top list.
-
I have a stupid request:
can the sells be in red and the buys in green? It is the other way around now.
------------------
- last_irreversible_block - is not updating
- if you do not refresh you sometimes have "Next maintenance 5 min. ago" :)
//Edit:
Can we have the settlement price the same direction as the rest of the prices on any given page? Example:
http://cryptofresh.com/a/GOLD
Price top of the page 218,000 (aka BTS/GOLD)
Settlement price 0.00000458 GOLD/BTS
-
I have a stupid request:
can the sells be in red and the buys in green? It is the other way around now.
....
Can we have the settlement price the same direction as the rest of the prices on any given page? Example:
http://cryptofresh.com/a/GOLD
Price top of the page 218,000 (aka BTS/GOLD)
Settlement price 0.00000458 GOLD/BTS
Thanks for doing it man!
-
I have a stupid request:
can the sells be in red and the buys in green? It is the other way around now.
....
Can we have the settlement price the same direction as the rest of the prices on any given page? Example:
http://cryptofresh.com/a/GOLD
Price top of the page 218,000 (aka BTS/GOLD)
Settlement price 0.00000458 GOLD/BTS
Thanks for doing it man!
Aha, you found it. Np. The red/green seemed wrong to me too, but for some reason I thought it was supposed to be that way. I like seeing Buys in green.
- last_irreversible_block - is not updating
- if you do not refresh you sometimes have "Next maintenance 5 min. ago" :)
I've been staring at these for a while, wondering if they're worth keeping around.. should I get rid of them?
-
This week:
Wrapped up changes to the CMC reporting API; trades among 35 assets are being tracked and any new significant trading among them should show up automatically on CMC. It helps make sure we are credited properly for volume on the DEX with minimal delay. Thanks to Ronny for sponsoring this feature!
Updated and cleaned up these reports for the hardfork:
https://cryptofresh.com/workers
https://cryptofresh.com/ballots
Added a balance lookup API and working on a historical asset data API. As I wrap it up, I'll clean up & document the other cryptofresh API endpoints. Now is a good time to send requests for any API's you'd like to see! If you are needing to scrape cryptofresh for something please let me know.
-
Last week was backend work and initial API (https://bitsharestalk.org/index.php/topic,22107.0.html) release.
This week I've focused on view internationalization, refactoring, and visual cleanup of the account and asset pages. These tasks go nicely together and give me a chance to comb over each page. It's a work in progress but I'll release some of the GUI changes today. Within 2 weeks I expect to have Chinese version of the site 80% done and ready for testing. During that period there will also be updates to the home page (more charts and less lists), and possibly the asset/market pages.
-
I've been reconsidering priorities and I'd like to submit a slight change of plans:
Worker:
- I'm not going to wait until the worker is fully funded to release the code. Instead, that's where I'd like to shift my immediate focus -- documenting & releasing the source. To set it free, allow it to be reused, and help others get involved.
- Besides that, the next tasks remain: internationalization, page updates, and as always.. more DEX data.
- No change in my commitment to keep building/improving cryptofresh while my worker is active.
- No immediate plans to launch another worker after this one expires (May 31), but I will continue to support cryptofresh.
Witness:
- I rescind my witness resignation and will resume publishing feeds.
- I also intend to run for a Steem witness position.
I'm glad I held off on the "blockchain social network" aspect of this worker proposal and focused on DEX-specific features! However that aspect is still something I'm very passionate about, and that's why I'm excited about Steem's approach. That being said, I still believe BitShares could benefit greatly from a blockchain-based trollbox and announcement channel (and I'd be happy to work with @svk to add it to the wallet if he has time & the stakeholders still consider it a priority). I'm just going to scrap the threaded discussion and tipping features for now.
Next week I will be taking a break from cryptofresh duties to catch my breath and get witnesses/servers set up properly. Over the following 1-2 weeks I will document & prepare the code for release, and then switch back to completing features. After May 31 I'll make sure cryptofresh continues to run smoothly and be a useful resource. There's still a *lot* more I'd like to do with cryptofresh but need to let the dust settle.
Feedback/questions welcome!
-
Ya'll really kept me on my toes the last few weeks.. only on BitShares can devs
be regularly fired and hired the same day, yet be expected to plan weeks ahead.. :p
Regardless.. it was overall a positive experience & I learned a lot! And most
importantly, I accomplished a lot I wouldn't have without the worker, things that
continue to provide ongoing value for the community.
Thank you for that opportunity.
But it does seem like the right time to shift priorities.
Returns from this worker are diminishing, and I'm running low on steam.
Of course, I'll continue working on cryptofresh, at my own pace.
As always, I'll be focusing my skills and energy where they are most effective.
It's great to see the true leaders stepping up in this community.
Hopefully you can figure out the funding situation :p
Just glad to see @svk's worker (critical) is still in..