Skip to content

Initial flow mockups

Jump to bottom
Doug Petkanics edited this page Nov 17, 2016 · 2 revisions

User Flow

Transaction info

The first user flow is for a user who is about to engage in a transaction via Metamask or some other txn signer, and sees the data that we've provided. Their flow is as follows:

  1. They submit an Ethereum transaction, and Metamask pops up presenting them with a little bit of attestation information.
  2. They click the link in the plugin, and are driven to the page on TAP that hosts all the attestation information for that function.
  3. If they find an attestation particularly helpful, and they are so inclined, they can upvote it. This is an eth transaction and costs gas, so we should think about whether people will do this, or whether we should instead allow them to tip the writer.
  4. If they happen to be a developer who has something to share about this transaction, they can also kick off the "author attestation" flow from this page to leave their own attestation. (Described below).

Attestation Author Flow

The second flow is for someone who wants to leave an attestation. In version 1, this is likely the author of the contract, us, or an early adopter of the platform who wants to invest energy into promoting their brand and providing community feedback around popular contracts.

  1. They will visit TAP, and either select a featured contract, and press the add attestation button on the contract page, or if the contract doesn't yet exist on TAP, they will need to verify the contract by pasting its code and contract address under a "Verify new contract" flow.
  2. They'll author the attestation by filling out the required form fields and checking the appropriate checkboxes. See The sample attestation for the fields to be included. Since attestations are at the method level, and there may be many for a contract, it would be nice if the UI helped facilitate moving from one method to another in writing attestations.
  3. They'll submit the attestation by signing a transaction, which will both place their signed attestation on IPFS and update the blockchain.

Investigative user flow

This describes the case where a user knows that TAP may have audit information on a particular contract, and they want to seek it out themselves. It also describes the power curator.

  1. The user visits TAP on the web.
  2. The user sees the contract they're looking for as one of the featured contracts, or if they don't they can paste the contract address.
  3. This drives them to the contract overview page, which lists all the methods for which they can view attestations. Clicking on any method digs down to the attestation page viewed above with all the info for that page. There they can vote on attestations, write their own, or just browse the information.
Clone this wiki locally