Connector Register Front End Flow

[Claire-Bear]

User Story:
As a vendor/connector I want to be able to set my phone as the connector device so that all transactions which occur off of my smart/feature phone result in commission being paid into my wallet.

Acceptance criteria:
Front end flow completed according to the figma designs

[longtomjr]

Open Questions

• Should a new wallet be created on our application for connectors?
  • I don't think it makes sense to create a Nautilus wallet for connectors in the broader context since they already have a device and might want to choose to use an address that is different from their Nautilus address.
  • We can provide both in the future, but I think it will make sense to just stick to one implementation first that works.

Assumptions

• The sign up flow will only be done once per device/installation. There is no requirement to have a way to modify or update the connector details for the first implementation.

General notes

• During the sign up flow the connector's address/id need to be set in a store that is persistent across sessions (local storage)
• A build time configuration need to be set that specifies what tokens/assets is supported
  • For XRP this configuration needs to specify the address of the token issuer that a trust line needs to be set up for.
  • For Algorand the configuration needs to specify the asset ID of the ASA
• If the connector has a Nautilus address (see questions above), the address needs to set up trust lines (for xrpl) or do opt-in transactions (for Algorand) for the pre-configured assets/tokens.

[Claire-Bear]

1. I agree but for now for the purpose of this MVP lets stick to keeping funds within the Nautilus Wallet environment and then we can cater for external wallets in the future. Connectors need to have a wallet and have completed KYC.
2. In future we can add in the ability to configure the connector details but for achieving Milestone 2 for Ripple this is not necessary.