Fsight closed - Now explorer.feathercoin.com
-
We have users from all over the world at the moment
:flag_gb: United Kingdom
:flag_br: Brazil
:flag_us: United States
:flag_de: Germany
:flag_ru: Russia
:flag_vn: Vietnam
:flag_cn: China
:flag_in: India
:flag_kr: South Korea
:flag_no: Norway
:flag_pl: Poland
:flag_be: Belgium
:flag_cz: Czechia
:flag_hk: Hong Kong
:flag_hu: Hungary
:flag_nl: Netherlands
:flag_tr: Turkey
:flag_ua: Ukraine
:flag_at: Austria
:flag_ca: Canada
:flag_ec: Ecuador
:flag_es: Spain
:flag_fr: France
:flag_jp: Japan
:flag_ma: Malaysia
:flag_re: Réunion
:flag_ro: Romania
:flag_sg: Singapore
:flag_si: : Slovenia
:flag_za: South AfricaI would love to see more of Africa and the Middle East.
I wanna get that whole map blue!
-
Interesting… I use but not marked…
-
@Lordas said in FSight: Feathercoin Block Explorer + API:
Interesting… I use but not marked…
ooops I am sorry, this would depend on the Ip GeoDatabase and a few other factors…
-
Np mate. Just said that geography is even wider than presented :thumbsup:
-
@aciddude , you forgot Denmark…have a nice day
-
lol guys it’s just a copy and paste from google analytics, if you don’t show up there, maybe you need to use it more ;-)
-
@aciddude You won’t see me on Google-Analytics, unless I turn off noscript … Nice to know it’s an underestimate.
-
It seems one of our leading exchanges has added Fsight to their Feathercoin info page. :-) !!https://www.19800.com/ftc/infoEdit:
Shame - that exchange has now closed -
This has been upgraded to 0.9.6.1 - The latest Feathercoin Core production version.
I’ve also increased the bandwidth on my VPS and increased the allowed connection count for feathercoind.
Hopefully this will help with new users syncing.
-
This has been upgraded to 0.9.6.2 - The latest Feathercoin Core production version.
-
This was down for 6 hours today as the daemon crashed. Back up now and fully synced.
-
@AcidD do you have any plans to update it to 0.13 or even 0.16?
Would be great to have a blockexplorer that can handle the coming Bech32 addresses.
-
@lclc_ said in FSight: Feathercoin Block Explorer + API:
@AcidD do you have any plans to update it to 0.13 or even 0.16?
Would be great to have a blockexplorer that can handle the coming Bech32 addresses.
Hey - it’s on my list of things to do.
I dont think my current version of insight supports Bech32 addresses or any of the cooler stuff we have going on FTC (it’s super old)
I spoke with Bush about porting the insight api but we need to port bitcore and a few other bits before it will work.
The problem for me here is time! - I just dont have it these days :(
-
Hi All,
This has been upgraded to Feathercoin Core 0.13.1.0 and the service has been moved to a more powerful server thanks to @ChekaZ
HTTPS certificate has been renewed as well.
-
@acidd said in FSight: Feathercoin Block Explorer + API:
Hi All,
This has been upgraded to Feathercoin Core 0.13.1.0 and the service has been moved to a more powerful server thanks to @ChekaZ
HTTPS certificate has been renewed as well.
What was needed to change to get it working?
As far as I know some of the RPC calls required are not available anymore with 0.13.
I never got all functions of the explorer working -
@Wellenreiter - where did you get stuck ?
I just moved my code to the new server and fired it up against a 0.13 client and it worked.
In the insight-api code - Any client/daemon greater than 0.9 needs to be synced from RPC.
There’s an environment variable like FORCE_RPC_SYNC=1 that you must have set when running insight.
if it syncs from the daemon it shouldnt need all the calculations for neoscrypt as it reads the already calculated blocks from the daemon.
Yesterday I semi-ported this for Trezarcoin @ChekaZ
explorer.trezarcoin.com - over here a patch was done so that it syncs from RPC - as since it’s a custom PoS/PoW coin the node app crashes over certain things, so i did a patch to force RPC.
-
@acidd Will try
-
@wellenreiter said in FSight: Feathercoin Block Explorer + API:
@acidd Will try
For testing this is what I run to start it.
export INSIGHT_NETWORK="livenet" && export INSIGHT_PUBLIC_PATH=public && export INSIGHT_FORCE_RPC_SYNC=1 && node insight.js
once it’s all working properly I make a .service file with the same parameters.
-
while this has been a great learning experience and fun to host for the community, I am unpinning this as we now have a full Feathercore / bitcore port thanks to @Bushstar
This was a very old repo and should no longer be used.