commit f1c09cbbdf228cefbfbd339567ba337083e93e52
Author: TomZ <tomz@freedommail.ch>
Date: Wed Sep 2 13:56:38 2020 +0200
Fix sorting in address/utxo call
commit c61b03b05de04c9d53c6fdf413dd1b6d33dc17f6
Author: TomZ <tomz@freedommail.ch>
Date: Wed Sep 2 13:03:43 2020 +0200
Also catch missing services for more complex searches
We did catch it on 'start()' which may not actually use a service that
was missing and only in a followup would the missing service be used.
So also catch the exception for missing service on the other event
handling methods.
This means that we now show a nice "setup needed" message to client when
a call is done that is not supported because of missing backing service.
commit fbcfe60c7d21b309e9c827dd927de0e196d7f5b6
Author: TomZ <tomz@freedommail.ch>
Date: Tue Sep 1 16:03:19 2020 +0200
Also use the complex UTXO lookup to do callbacks.
commit d948225ae7786aa6b62ff9355c2d768a85569642
Author: TomZ <tomz@freedommail.ch>
Date: Tue Sep 1 15:47:48 2020 +0200
Add address/utxo call.
commit cbc4695d4abae1404afe03f34b10427e48f819ae
Author: TomZ <tomz@freedommail.ch>
Date: Tue Sep 1 14:34:31 2020 +0200
Add address/details API call
This mostly implements the API call to list an address.
commit 1d215032af09551e2b3eda314c072a200e5fb37a
Author: TomZ <tomz@freedommail.ch>
Date: Tue Sep 1 14:30:26 2020 +0200
Fix warnings
This fixes warnings from the compiler and the linter.
commit b61e7dd42222537b456a79e14439a0d36007e8d7
Author: TomZ <tomz@freedommail.ch>
Date: Tue Sep 1 14:27:27 2020 +0200
Blockchain::Search: Clean a little and fix bugs
This follows the API docs on the utxoLookup() callback and we indeed
return back the blockheight/etc parameters even if the utxo is already
spent (represented by unspent=false).
commit 7ec3ebf937d7f2fb6a7a18f21d2e8b645db6fe3e
Author: TomZ <tomz@freedommail.ch>
Date: Mon Aug 31 12:24:18 2020 +0200
Fixes and move to v2 url
commit 32b8018af805ce068da7d3e149add66a90c92264
Author: TomZ <tomz@freedommail.ch>
Date: Mon Aug 31 11:29:35 2020 +0200
Build the rest service
commit c386adff9d28a0f844916019602ea0032bbc360a
Author: TomZ <tomz@freedommail.ch>
Date: Sun Aug 30 19:24:29 2020 +0200
Cleanup old code and make vin work
commit 5b88457863892ff8391e42a7eff61cd243851b41
Author: TomZ <tomz@freedommail.ch>
Date: Sun Aug 30 18:42:41 2020 +0200
Output addresses.
commit 46c2ce680409c38f1a67730e23cde942db2ecc46
Author: TomZ <tomz@freedommail.ch>
Date: Sun Aug 30 17:51:03 2020 +0200
Make tx-refs easier for the Blockchain::Search
commit b0591b5a6b57e2eb7022db7b7a351c694220e5ad
Author: TomZ <tomz@freedommail.ch>
Date: Fri Aug 28 18:28:48 2020 +0200
Make printing of tx work better
commit d337ac91ad4ab9eeb768695c639dcbbbcc463837
Author: TomZ <tomz@freedommail.ch>
Date: Fri Aug 28 15:46:04 2020 +0200
Make rest service show a nice help for setup.
commit 5997ff1fa06bd1a6b51ead93eef094a5561fdb53
Author: TomZ <tomz@freedommail.ch>
Date: Wed Aug 26 17:43:09 2020 +0200
Parse the json automatically.
commit 5ed7d6e53761828e2e385e085f44d530449b0b3b
Author: TomZ <tomz@freedommail.ch>
Date: Wed Aug 26 13:07:04 2020 +0200
Start project rest-service.
When we notice a missing backing service we now throw an exception
and on the html handler we push a setup.html file which has helpful
setup information.
The callback on each transaction was only called when individual tx
were fetched, which is "magic" behaviour and I don't like
inconsistencies.
So, also call the callback for each transaction in a block we fetched.
This will most likely benefit some FloweeJS users when they do some stuff
that I didn't think a good idea, at least this way they will not get
a bunch of errors :)
The FloweeJS component uses this class but requires the usage
of the NodeJS 'main' thread. Which needs safe access to the jobs
list at the same time the Flowee workers need access.
Simple solution; add a mutex.
Make the UTXO search callback actually useful for more than tests.
This passes all the data we have and what the user could want to use,
also updating the receiver (bitcore-proxy).
Make the callback happen after we get the indexer status.
Additionally, fix the issue where looking up a txid that failed
would end up being recursive due to us copying the initially requested
hash. Causing it to be a duplicate (which then fails etc).
The usage of a ripe160 for bitcoin addresses in the API and in the
Indexer loses some info, specifically what kind of script it is.
Additionally not all types of scripts fit this mold. At best that means
its not future-proof.
This adds a method to the API in order to select from a Tx the hashed
outscript (thats singlehashed sha256) and refactor the address indexer
to use that instead of the ripe160 address.
The API enums broke a little, so I used the opportunity to break it a
lot and clean up the enums in order to make them more future-proof.
But, yeah, software from before this commit is protocol incompatible
with software after this commit.
This makes the service mostly self-documenting as it serves plain simple
html pages for error messages which show the end points you can use.
This adds support for the "unspent outputs for address" endpoint.
The core APIs in Flowee are quite low-level and especially combining
results from multiple services becomes tedius, verbose and thus
error-prone.
For this reason I wrote a new SearchEngine and related classes which
allow one to create a single compound request, submit it to the engine and
get a callback when it is done.
For instance one can now create a request for a transaction by txid and the
system will split this into a txid-lookup and the actual fetch for the
transaction.
Enough callbacks and options exist to be able to add a lot more details
this way in a simple manner.
tomFlowee
TomZ