Just brought CF back up. As far as I can determine, a double-produced block caused issues with cf sync, which then led to an out-of-memory condition. The node just finished replaying and the site is caught up with the chain.
I'd like to start a dialogue about cryptofresh and its future. My witness has been voted out for a while so I'm maintaining cryptofresh.com (plus witness node) out of pocket, including dev hours and hardware upgrades.
IMV the witness was a convenient method of funding maintenance. I understand the desire for separation of roles, but I have experience with both so it avoided worker overhead. Would voters support a cryptofresh.com maintenance worker?
I'm also evaluating ways to continue development of cryptofresh. Here's a brief list of pending projects/todos:
- fork handling
- upgrading node, evaluate new APIs & check compatibility
- upgrade server
- improve rate bridging calcs
- load charts faster (async generation)
- tuning views
- check API load/performance
- open source
- custom reports
- worker caching bug
Any other issues I should know about?
Topic: Cryptofresh update, feedback (Read 10990 times)
