File tree Expand file tree Collapse file tree 1 file changed +13
-5
lines changed
Expand file tree Collapse file tree 1 file changed +13
-5
lines changed Original file line number Diff line number Diff line change @@ -73,10 +73,10 @@ A set of bundled TokenScript cards might look like this:
7373</ts : cards >
7474```
7575
76- An alternative pattern would be to treat a these additional cards as a completely different TokenScript instance.
77- i.e. ` tokenScript.getBundledTokenScriptInstance() => TokenScript `
78- The bundled cards from this separate instance can be merged with the current instance and displayed in the UI with minimal
79- changes to the code and no changes to the XML schema.
76+ An alternative pattern would be to treat a these additional cards as a completely different TokenScript instance.
77+ i.e. ` tokenScript.getBundledTokenScriptInstance() => TokenScript `
78+ The bundled cards from this separate instance can be merged with the current instance and displayed in the UI with
79+ minimal changes to the code and no changes to the XML schema.
8080
8181This may be a better approach as it requires additional research to determine the best method.
8282
@@ -110,4 +110,12 @@ When a token fails to resolve a TokenScript for itself, we provide a small XML s
110110
111111## Considerations
112112
113- ## Summary
113+ The main consideration mentioned above is how to implement these features in a way that:
114+
115+ - Limits the changes to TS Engine logic and the XML schema
116+ - Does not create additional requirements for external tools such as TokenScript CLI that will be used to build these bundled cards.
117+
118+ ## Summary
119+
120+ This EIP represents an easy way for us to enable common token features for every single token, on every single chain
121+ in a way that is transparent to the user and customisable for the TokenScript developer.
You can’t perform that action at this time.
0 commit comments