Design TokenScript for attestation tokens #435

Activity

1. AW-STJ

   changed the title [-]Design for TokenScript for attestation tokens[/-] [+]Design TokenScript for attestation tokens (TokenScript Config)[/+] on Nov 28, 2021
2. oleggrib

   assigned

   nicktaras

   on Dec 14, 2021
3. micwallace commented on Apr 14, 2022

   

   micwallace

   on Apr 14, 2022

   More actions

   Yep 100% agree Oleh. As soon as we get this into TokenScript we can take advantage of the TokenScript signing security.
4. AW-STJ commented on Jun 28, 2022

   

   AW-STJ

   on Jun 28, 2022

   ContributorAuthor

   More actions

   I will escalate this with @weiwu-zhang. We had discussed this recently as well.

   If we are hitting this issue again, and is related to attestation.id as well, then its high time to decide on the config before moving forward
5. overseers-desk

   transferred this issue fromSmartTokenLabs/attestationon Jul 4, 2022
6. overseers-desk

   changed the title [-]Design TokenScript for attestation tokens (TokenScript Config)[/-] [+]Design TokenScript for attestation tokens[/+] on Jul 6, 2022
7. micwallace commented on Jul 26, 2022

   

   micwallace

   on Jul 26, 2022

   Last edited by micwallace

   More actions

   Some redundant field have been removed from the negotiator interfaces. Defaults are still set in Outlet but can be overridden. Currently, here is what is required in both client and outlet:

   export interface OffChainTokenConfig {
       title: string;
       image: string;
       tokenOrigin: string;
       unEndPoint: string;
       attestationOrigin: string;
       tokenParser?: any; // Note: This will be changed to tokenSchema, which will be embedded in the XML
       base64senderPublicKeys: {[devconId: string]: string};
       base64attestorPubKey: string;
   }
   

   I have created a dynamic schema parser that works with asn1-schema library to parse & serialize asn1 based on a JSON schema definition. This can be used to parse an arbitrary token schema defined within XML.