Jonathan Chappelow

Also, I suggest approaching this task in pieces. Perhaps look at the content detection / decoding issue first, then worry about the front end stuff later.

Well, how should we enforce this rule? OP_RETURN data can be anything at all. Could be jpeg data. This entire issue is purely amusement.

Good idea. We'll have to spec out exactly how it will work, with particular attention to the fact that mempool is a node-local concept.

I have been seeing my regular transactions (neither spit nor ticket) sitting in mempool for multiple blocks with plenty of free space in those blocks. It's starting to seem like...

Also, `Cache-Control:private` `Expires` is not likely to be useful except perhaps for mempool. Conditional requests are likely to be of more use: - content based w/ `ETag` response header and...

Yes, please do, @njirap. Although please draft an informal but detailed ConOps describing the specific goals and intended use case for the solution you come up with.

Can go in 5.0.1 or 5.1 unless there this is a show-stopper for 5.0.

Much like the design of `rateserver` and the `exchanges` package, there will need to be a separate crawler data provider. The simplest solution is to build an HTTP API into...

For Decred Journal, I can pull stats out of a crawler I run. We will put this issue on the roadmap for 5.1

I posted the following in Matrix. Mirroring here. [decred-public-nodes-2019-06-02.xlsx](https://github.com/decred/dcrdata/files/3249124/decred-public-nodes-2019-06-02.xlsx) [public_nodes.json.gz](https://github.com/decred/dcrdata/files/3249127/public_nodes.json.gz) Service flags: full node = 1 bloom filter support =2 committed filter support = 4 e.g. full node with committed...