[quote=“hrobeers, post:18, topic:3851”]Projects like PeerAssets and others PeerApps will also benefit from this.
So I’m quite sure there is a need for such an API service.
Having multiple fallbacks also increases reliability of the thin clients by taking away the single point of failure.
The guys at Ethereum would most likely implement it on Ethereum creating Methereum.[/quote]
Such a fallback mechanism is exactly what multiexplorer’s api is all about. It tries multiple services until it gets a response. Unfortunately for peercoin is doesn’t work too well because there are very few APIs that support peercoin. https://multiexplorer.com/api
However, don’t we want the fallback mechanism implemented client side? (js lib)
That multiexplorer API is still a single point of failure.
We might be able to do both though.
[quote=“hrobeers, post:24, topic:3851”]Cool, I’ll be watching this.
However, don’t we want the fallback mechanism implemented client side? (js lib)
That multiexplorer API is still a single point of failure.
We might be able to do both though.[/quote]
Well, multiexplorer is open souce. Multiple people can install the software on their own server. Client side you can fallback to other multiexplorers. If multiexplorer.com is down or retuns an error, your js code can try the same url at othermultiexplorer.com, then if that fails you can fallback to yetanothermultiexplorer.com, etc. This is a technique I call “multi-multiexplorer”. The only problem is that there is only one installed instance of multiexplorer that I know of.