Thomas Jay Rush

The warning was clearly appearant in the server logs, but wasn't communicated to the front end. Woudl have been easier to figure out if it had of been

Just for future reference, this script show you how it works (really poorly) from the command line currently: https://github.com/TrueBlocks/trueblocks-core/blob/master/src/other/build_assets/addName. The backend work would have to be done in this code...

In order to save the name edit, you can send a POST request to `http://localhost:8080/names` with an object of this type. If the address exists, it will be edited. If...

This change requires a re-build of the backend.

It's a great question. For now, can you send it as a single string possibly separated by something like a '|'? The backend won't accept an array for this even...

We spoke about adding this feature (naming addresses) to the 'names' view, but now that we have named addresses in the transaction history view, it would be really nice to...

I use this to play around with adding names: https://github.com/TrueBlocks/addName

@deeayeen Works excellently. There's a couple of smaller related issues: 1) We need an addName button somewhere above the table. 2) Users should be able to edit and add names...

I'm pretty sure all you have to do after updating the backend with the new name (in the same way you would with an edit) is re-direct to the Account...

Our use case is probably not all that typical (but no less useful). We only need `first_block` and `last_block` because we scan the result ourselves for appearances. I imagine that...