Use the btsx://bitmeat/transfer url to request support and also include the robo hash. 

Minor: it's "reliability" not "realiability"

Thank you, bytemaster!

I compiled 0.4.7. from scratch, which seems to be really stable so far. Site has rebuilt the data from scratch and is up and running again!

:)

Quote from: happypatty on August 22, 2014, 06:34:05 AM
Hmm I did a fresh checkout of 0.4.5 and seems I'm stuck on block 284575.

Any ideas? This is on Ubuntu 14

Yes.. this is a known issue.   Try this work around.  Clear chain folder and connect via chain server:

https://github.com/BitShares/bitshares_toolkit/wiki/Using-Chain-Servers

We are preparing a fix for the next iteration.

Hmm I did a fresh checkout of 0.4.5 and seems I'm stuck on block 284575.

Any ideas? This is on Ubuntu 14

Recompiling and will update shortly. In a perfect world hard forks won't happen, but they still do, so... it is what it is. :)

Thank you all for alerting me!

Yeah, something's not right about it.  Probably just needs to be updated somehow.

The website seems to be on a minority fork.

That's a great idea and, you will soon see a "delegate profile page". Where can look at historical voting / reliability charts.

Please forgive my poor English! ! !
About Delegates statistics, I think it is very good!
But I think the general BTSX users will not be too concerned about how many blocks delegate production, are more concerned about the reliability of the most recent Delegate, therefore, on this basis can provide delegate details:


Green triangle in the figure can be dragged to learn recently that the Delegate's reliability as whether to vote or concern basis.

Figure information just to show, of course, if you like,
you can vote for my delegates "mister" or "delegate.mister",
thanks!

Quote from: liondani on July 30, 2014, 01:20:53 PM
+5%

Added you to rank list. Thank you!

 +5%

Quote from: happypatty on July 28, 2014, 12:19:35 AM

Quote from: GaltReport on July 28, 2014, 12:12:25 AM
I didn't know that.  That's cold man.

Think about it... let's say the slate for block production is as follows:

D1, D2, D3, D4, D5. Let's say D1 is a good honest guy and D2-D5 are playing dirty.

D1 produces a block, but as soon as he does, D2 builds a longer chain based on last block before D1 and marks it as missed. Then D3 confirms it, and so does D4 and D5. Now they have the longest chain of decent looking blocks. While good guy D1 has bad rep.

That's a shame but I guess I shouldn't be surprised.  Too bad there's no way to fix that.

 +5%

Quote from: Fox on July 28, 2014, 02:23:53 AM
Directing a portion of my delegate pay to happypatty for the effort put forth on delegate statistics.

Thank you.

Appreciate the recognition of my efforts! Anything donated to bitmeat will help keep the monitoring service up & running, as it is not cheap.

Include a topic ID from this forum, and the senders name will automatically be highlited and listed in the donations section with a link to the topic on this forum. Amounts will not be shown, however they will be sorted in a descending order in the donations section.

e.g. if you include 6142 in the memo it would link to this thread. (Look in the URL web address in your browser you will see topic=6142)

100BTSX will be the minimum that will be processed using this system. If you want to be removed send again with "remove" in the memo, simple as that.

(this is work in progress, wanted to get some early feedback)