See: https://hnscan.com/block/1917

Page 1 has 19 TXs and Page 2 has 15 which is a weird split. Also the buttons don't include the block number in them when linking to the pages.

Would be nice to show a list of domains owned by a specific address.

We should have better errors for 1. Node connection errors, 2. Node startup issues.

So if in the middle of the block explorer being up the node goes down, we want to handle this gracefully.

If there is no node available on startup we want better errors for that as well.

This would be a tool that someone could type in a specific domain - and then it would show the release of that domain (if not already) on the network that HNScan is currently connected to.

We should look into the new Docker syntax of splitting the image into 2 builds.

This should allow us to build the first one with dev dependencies, and then build the second without.

Title pretty much explains it all - but would be awesome to have web sockets/live reloading on the home page for blocks and transactions.

Would be great to have a list of the top 1-500 wallets/addresses, as well as add some tags for the more well known addresses - (airdrop, exchanges, etc).

I think we should have Issue and Pull Request templates to better encourage contribution from members outside the immediate HandshakeAlliance organization. This would also ensure more consistent contributions, and better change tracking during the review process.

For instance, we have a "releases.md" file with no documentation on when to add to that file, what constitutes a version change, how frequently it should be updated (all information we could provide in a pull-request template).

(Side note, I almost want to move to a "changelog.md" format instead, because "releases" sounds like major version increments only - which of course has its own benefit, but I suppose that is a conversation for a different time).

Some resources I dug up real quick that might help with this issue:

• https://help.github.com/articles/creating-a-pull-request-template-for-your-repository/
• https://help.github.com/articles/creating-issue-templates-for-your-repository/
• https://semver.org/

Would be nice for us to link the Bids and the Reveals in auction history.

I believe that this can be done if we use the nonce in the reveal to iterate over the bids to match the pairs.

Let's do a review of the GeoIP keys and the map keys and where we have them in our application.

These should be optional for people who are downloading HNScan and running it themselves. We need to ensure that we are handling this gracefully.

With the new testnet the numbers we have in difficulty don't seem correct.

We should label this number so that it's clear what the difficulty actually represents, as well as check the number to confirm correctness.

There is a lot we can do with auction history -

First we want to ensure that we are capturing all types of events and adding them to the history. See: FormatAuctionHistory in util.js

Second, I think we should take any "data" - From Registers or Updates, and present that on a different page. These data packets will most likely be DNS record updates, so it will be nice to show exactly what those updates are.

I'm sure there is a lot more than can be done, so let's use this as a general issue to track updates and improvements to auction history.

Right now it appears that the out of the box Bulma styling has mobile drop-downs always in the "dropped" styling. Would be a great feature, as we add more tools, to make those drop-downs functional on mobile.

We should revamp the about page to be more relevant for SEO and for our new ideas.

We want to build out our client calls in such a way that we support multiple different networks -> HNScan can be connected to a Regtest, Testnet, and Mainnet network all at the same time.

Not sure how exactly we would do this without a DB -> Perhaps make this a feature of Nomenclate.

It would be great to be able to show the % of the names that are claimed from the reserve list. This would be a good indicator of non-crypto adoption in my opinion.

Take a second look at our hash rate -> I'm not 100% sure this is accurate.

Just need a space added here.

Currently our airdrop page utilizes the old method of searching for airdrops. We need to update this for the testnet3 version of airdrops.

We use duration quite often and it's a bit of a cumbersome amount of JS code that we have intermixed with our templates. Moving all of our duration code out to a mixin and then just calling that in the templates would be a much needed improvement.

This is a feature for the Airdrop tool in which we will show the following stats:

• % Airdrop Claimed
• Amount of Claimers
• Amount of Remaining Claimers
• Amount of HNS Claimed
• Amount of HNS Remaining.

Pending transactions cause this 'Received' header to convert to something along the lines of '49 years ago'

Add Current Version: and Source Available At: at the bottom near the footer so that people know this application is open source, and what current version is running.

Looking at the amount of data we have on the name page it's a lot to scroll -> I wonder if we build an arrow onto the right side of a card that allows you to fold the data. For example, you may not want to view the advance card when searching a name so you can click that and fold it down.

Further, we should look into saving the user's preference if we do this so that they are not constantly clicking the fold button as they navigate the site.

Emojis, Block Hashes, Tx ID vs Tx Hash, etc

This may be a bug with Nomenclate, but currently "Reveals" are all showing the same value e.g. https://hnscan.com/name/government

This may be a problem with Nomenclate and/or the daemon so going to have to work from the top down on this one.

https://github.com/lucagez/Debucsser

The search bar should give feedback on if the search failed (right now the Network request just returns a 404 and nothing actually happens on page)

A search will fail in a couple scenarios:

• Most strings with special characters (This includes chars like " ", "$", etc.)
• Any empty string
• Searches exceeding 63 characters

It looks a lot better when we present the data in x10^ format vs e^ format. We are doing this correctly on the home page, but I believe there are some pages in which we still show e^.

Best way to tackle this imo: Write a template function that converts a large number into x10^ format - then we can just place that into all of our templates.

I think our search bar right now is just listening for the enter key to be hit -> That isn't working for some reason on my iPhone. We might want to transition to a form w/ a submit style input which I believe catches all inputs, and also pops up the custom "submit" button while on iPhone.

Right now we don't indicate how long it is until a name changes state. Would be great to show how many more blocks until bidding ends, reveals end, etc.

We should be linking to the actual bid in auction history as well as in Tx history.

For some reason the output address in the transaction listings are being shown incorrectly.

Meta Issue for tracking things on the Airdrop Tool.

• Statistics - #26
• Over time Stats
• In-page claiming
• Separate Faucet with Airdrop claims - possible if we have the merkle tree

I like the peer map we have as it stands, but I do believe that integrating some more information and stats.

Here is a project that does that for Bitcoin, and we can take some inspiration and/or incorporate it into HNScan. https://github.com/ayeowch/bitnodes

Would be great to have a tab on the table to show Name Records that the user can toggle between seeing the records as they are presented on the chain, and then showing the records how they would be viewed when interpreted by DNS.

We need set up an automated build at the Handshake Alliance dockerhub org.

On the final page of the names we are not seeing any results - likely a small bug with the length of names and pagination results:

For production builds, let's add in the ga pageview hit so that sitesearch is able to pick up our stats.

We need to auto generate a sitemap to index some of the larger pages on this site.

Would be nice to have a tool to show the current mempool, and various stats surrounding it:

• number of Txs
• Total amt to be settled
• Number of bids/opens/etc

When transactions are searched that are in the mempool - they are showing some weird behavior and stats.

We should either A. see if this is a bug in our stuff, or if this is simply how the daemon returns data.
B. Wrap mempool transactions so that the data is shown in a better way.

Build tabs into the Transaction page so that you can view bids, reveals, registers, etc.

A master file of commonly used css styling to clean up repetitive code. Would be nice to add .flex/.column/.row/.grow on some classes instead of writing them all the time.

Right now for names with over 13 items in their auction history we are seeing a truncation.

I'm not sure if this is due to the templating system, or if it's coming from Nomenclate.

This issue should go hand in hand with our other feature request looking to build pagination for history.

This might be a non-issue, but for some reason the "test" name returns a 404 when searched and when you try to go to that page https://hnscan.com/name/test.

This is the only name I've found that has this behavior.

For pending transactions of a -1 block height we need to remove the href link and display 'Pending"

Right now our auction history is pretty maintainable, but it can very quickly get out of control.

We need to implement some sort of pagination for this.

Right now in search results HNScan shows a bunch of gibberish from the front page. We should write a nice understandable description tag so that it's easy to know what the purpose of the site is when you come across it on google.

https://HNScan.com/address/hs1qtjr4ulexeu5gj7xnxvkfl9hljfh8yc5fnns8ts for relevant view