Hi guys, thanks for the support. I'm still considering open-sourcing the site; keep in mind the only reason it's not yet is because my last worker got voted out. Keeping it closed source protected me from giving everything away without getting paid.
Last week, I ran into server issues/constraints (as mentioned, server upgrade is on the wishlist) which caused some downtime. I then upgraded the bitshares node to latest version so I could have access to the
max-ops-per-account option to get memory usage under control. I had postponed updating the node because I'd seen API changes on GitHub over the last few months and was concerned some of them could be breaking changes.
I've found the issue with the assets pages and some APIs was due to a change in
get_market_history_api, now fixed.
Let me know if there are any other issues.Hi @roadscape and all, i am about to submit a worker proposal that includes work in the new explorer: http://bitshares-explorer.io:9009/#/dashboard.
the worker is mainly for bitshares core development, the explorer development is just 1 of the tasks i was planning to work on. i started to work in a block explorer when the community claimed for it by different channels. it is not my intention to compete with cryptofresh for a worker or anything like that. i really like cryptofresh and it is probably the bitshares company standard. if it is updated and open source my explorer project will never started.
in the other hand i will love to continue with bitshares-explorer.io. we can maybe find a solution working together somehow.
let me know.
Great work,
@oxarbitrage. I'll think about how we could collaborate, but there's room for more than one block explorer. A healthy ecosystem should have options!