...
https://overflow.io/s/W5DIEZP1?node=fb628e33&view=fit
https://overflow.io/s/KIFQRHG0?node=fb628e33
Sign NFT
Visual | Functionality |
---|---|
FIO Address List | |
NFT Signatures List |
|
Sign NFT |
|
Sign NFT Details |
|
Contained Flow
...
Visual
...
Functionality
General
...
...
Contained flow means that the user has accessed the website using an Inbound url which contains referrer id and Contained Flow parameters.
...
When Website is accessed in Contained Flow the following modifications to the flow are applied:
URL parameters are verified to ensure that valid action parameters are provided
Navigation is stripped (see left)
User can only perform these actions:
Sign in
Create Account
Register FIO Address
List of allowed domains is set in Referrer Profile
Flag if custom domains are allowed is set in Referrer Profile
Perform designated action, e.g. Sign NFT
All data is pre-populated and cannot be changed
If action with those parameters has already been executed show Alreday Signed banner
User is forced to one of the flows
Register a FIO Address → Create Account → Perform action → Redirect to url set in Inbound url
Sign in
If FIO Address exists in account
Perform action → Redirect to url set in Inbound url
If FIO Address does not exists in account
Register a FIO Address → Perform action → Redirect to url set in Inbound url
...
Contained Flow is turned off when:
User is redirected to url set in Inbound url
User navigates to another page via url
Browser window is closed
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 - this is the list of domains which will show up in pull-down for domain list for this Contained Flow
Allow custom domain registration - Yes indicates custom domain registration is allowed for this Contained Flow, No - indicates it is not
Action redirect after Sign-in - name of action which the user will have to take after they have signed-in. Currently only signnft is supported.
TPID to use in contained flow.
Registration site referrecode
Registration site API token
...
Inbound URL Structure
...
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/
Referrer Profile Settings
ID
Settings
uniqueone
|
uniqueone
Allow custom domain registration
Yes
Action redirect after Sign-in
signnft
TPID
TBD
Registration site referrecode
TBD
Registration site API token
TBD
...
|
...
Visual
Functionality
Display
Domains as per Referrer Profile