Contained Flow

• Contained flow restricts navigation to specific actions as long as the user stays in flow, see https://fioprotocol.atlassian.net/wiki/spaces/DAO/pages/490307585

• Contained flow is not impacted by referrer ID other than a referrer ID can be passed in the url

Referrer Profiles

• Referrer profiles are configs loaded manually by developer to the Dashboard site to enable custom behavior. They contain the following settings:

  • ID - uniquely identifies profile

  • List of domains allowed for registration

  • Allow custom domain registration

  • Action redirect after Sign-in - name of action which the user will have to take after they have signed-in.

    • Sign NFT (Currently the only contained flow available)

  • TPID to use on all FIO Chain transactions

  • Registration site referrecode

  • Registration site API token

Inbound URL Structure

• Signnft

  • Path

    • https://www.someurl/com/ref/{id}

      • {id} - referrer profile ID

  • Parameters

    • action - use SIGNNFT

    • r - redirect url

    • SIGNNFT parameters

      • chain_code

      • contract_address

      • token_id (optional)

      • url (optional)

      • hash (optional)

      • metadata (optional)

        • creator_url

  • Example:

    • https://dapp-dev.fioprotocol.io/ref/uniqueone?action=SIGNNFT&chain_code=ETH&contract_address=FIO5CniznG2z6yVPc4as69si711R1HJMAAnC3Rxjd4kGri4Kp8D8P&token_id=ETH&url=ifg://dfs.sdfs/sdfs&hash=f83klsjlgsldkfjsdlf&metadata=%7B%22creator_url%22:%22https://www.google.com.ua/%22%7D&r=https://www.google.com.ua/

uniqueone

• List of domains allowed for registration

  • uniqueone

• Allow custom domain registration

  • Yes

• Action redirect after Sign-in

  • signnft

• TPID

  • None

• Registration site referrecode

  • uniqueone

• Registration site API token

  • ***

Unique.One

Open

Click model

https://overflow.io/s/KIFQRHG0?node=fb628e33