burstcoin-observer v0.2.8 (All Platforms)
-
Update:
- renamed to burstcoin-observer
- added crowdfund page/data
- bugfix to prevent sending multiple emails for same fork
- fixed format/layout issues
- refresh interval adjustable for every page
-
Update:
- fixed a lot of minor bugs
- harden code to run more stable
- added some small new features, like links to blockex.
-
@luxe Up dated! Great job!
-
Well, the backend is still quite stupid, on every data refresh all data is reloaded and not updated ... causing some extra traffic ... so if you feel too much resources are used, feel free to increase refresh times. But thanks again for hosting a mirror.
-
@luxe This is a fantastic tool! It will be added to the Android Burst Wallet via the JSON API for loading available pools for the user. It will allow users to select from all the active pools. This solves my problem of finding/loading pool. Thank you so much for the continued development and support.
-IceBurst
-
@luxe https://monitor.burst-team.us/ also updated to latest snapshot. Thanks again for all your work on this.
H.
-
@IceBurst Nice if that data is useful for you :-) But keep in mind that it still is not final datastructure yet. But for the pool it looks ok so far.
@haitch should run more stable now, the fork auto detect is still far from 100% reliable, but should not spam mails anymore.
-
@luxe The last updates have been a lot better at preventing spam :)
-
Seams that the Asset overview has a problem with new created Asset or something, hope i will find some time on WE to find and fix the issue ...
-
Update:
- asset exchange overview bugfix
- added last price on asset exchange overview
- auto build distribution on mvn package
-
@luxe Thanks for all the work! https://monitor.burst-team.us/ has been updated.
-
http://status.burstmining.club/ updated
P.S. Check your zip file as it has faucet.properties and not observer.properties
Thanks for the update !
-
@Focus thanks, i fixed it and and added http://status.burstmining.club/ to op.
-
@luxe Trying to track down an issue with the latest observer. For some weird reason every time I start it up, it last a few hours and then locks up the whole server. The only thing that I did notice so far in the logs is that burst.ninja was unreachable. Don't know if that had anything to do with it.
Is there a debug/logging feature we can activate to see what's going on?
-
I noticed a issue there, too. Sorry for that, currently you could only use a earlier version. Will have no time until WE to look into it.
-
Update:
- asset exchange fixed price and update bug
- check and mail-notification for NetworkState.STUCK (thanks @maxp1256)
- new properties for mail-notification, update observer.properties! (thanks @maxp1256)
-
@luxe, can you add a small ffeature please, the ability to group by type in the list, so that All the pools are listed together and then all the wallets, etc...
-
@Focus, sure i will check that ...
-
Some may have noticed forks in burstcoin network this days ... and i feel like i need to explain something about network observer ...
You can see on the picture below that currently 2 chains exist, the observer will mark the chain will less nodes in the list as FORKED. That does not mean that there is something wrong with it, observer can not know what chain will win in the end. FORKED just marks the 2nd chain.
- (1) the last block height before the fork happened
- (2) the 2nd chain
- All with 'OK' are the first chain
Also observer is not perfect and still has bugs ... it can provide a overview of what happens within the network. The data used on that page comes simply from requesting '...url.../burst?requestType=getMiningInfo' from the url's in the list every few seconds.
-
@luxe hmm can you alter it that it would check last say 2-3 blocks as i think that would show a good indication that fork has happened. Unless as son 2nd block is gotten other chain is integrated into first one?




