226
General Discussion / Re: Too many missed and forked blocks due to new wallet
« on: December 12, 2014, 10:02:14 am »
"blockchain_average_delegate_participation": "46.54 %",
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
I can confirm that v0.4.24.1 isn't missing any blocks for me
I am not missing blocks with v0.4.25-RC1 too...
...but I have 8 gb ram on my personal server that host my delegate.
It's getting scary for sure!
"blockchain_average_delegate_participation": "55.49 %",
are some devs watching?
Hmmm, after building the latest and running the client (with the current delegate still going) I get this:Code: [Select]./bitshares_client
Loading blockchain from: /root/.BitShares/chain
Loading config from file: /root/.BitShares/config.json
------------ error --------------
10 assert_exception: Assert Exception
_map->is_open(): Database is not open!
I deleted the keys for delegate.adam before there was a "revoke" feature. It is a symptom of bad voter turnout that an old inactive delegate is in the top 101...
I'd more likely say it's a symptom of a badly designed delegate approval system that allows an inactive delegate to be elected at all.
Why don't we automatically blacklist a delegate if either
a) their reliability falls too low
b) they miss too many consecutive blocks
btc38 changed their API from BTSX to BTS, is your script updated for that?
Evidently not. But there are loads of instances of that particular error in the log, so not sure why it just stopped working now.
My feeds quantity has suddenly dropped to zero on bitshareblocks.com, but the script is still running - any idea what could have happened?