[ANN] offline transaction builder with peercoinjs-lib


#21

[quote=“thehuntergames, post:19, topic:3851”]Hi
I tested a push tx and it worked! d9a43628b04a3ae9c3ff3c392144fd6a86752bca17aa848fc8f72657c88af1f9

however it says it has a limit of 5 request per day? Is that correct?

There is a need to have a page like this https://blockr.io/tx/push
or better yet, a API that does sendrawtransaction only

Any ideas how we can get this up?[/quote]

5 request per minute This should be enough for most cases :slight_smile:

My API for Peercoin sendrawtransaction is very simple

$.post( "https://multicoins.org/api/v1/tx/push/ppc", { "hex": hexTX }) .done(function( data ) { alert( "Data Loaded: " + JSON.stringify(data) ); }) .fail(function(e) { alert( "error " + JSON.stringify(e)); });


#22

some more complicated solution maybe: bitcoin-js-remote, which i havent gotten working yet myself ::slight_smile: (because yeah it is for bitcoin actually ::slight_smile: )


#23

[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

for instance:

https://multiexplorer.com/api/address_balance/fallback?address=PVjubSWa6L3RrFNNUYFbdQUJTL84qko1P5&include_raw=true&currency=ppc


#24

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.


#25

[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.