Christopher Adams

The uri function documentation should not indicate hex format IDs

1

I think the documentation for the `ERC1155Metadata` contracts `uri()` function is misleading: https://github.com/arcadeum/multi-token-standard/blob/36ebad2194d79f3cf510fcaa80738d61344ff9ab/contracts/tokens/ERC1155/ERC1155Metadata.sol#L23 At first glance, this reads like the function will return the URL with an alphanumeric hexadecimal string...

Don't register documents automatically from the detail page

2

Viewing the document detail page should only result in a `GET` request for the document status. It should not make a non-idempotent `POST` request to register the docproof. The option...

Display the document hash on the detail page

4

The `/detail` page should have a header-level element showing the document hash that is being viewed.

The detail page should surface 400 errors

2

Requesting the status of or registering an invalid docproof returns a `400 Bad Request` from the API. That error should be displayed to the user on the detail page.

Can remove or downplay the submit buttons for manual status updates.

Switch to dark theme

1

To better distinguish the site from our other, similar properties.