Harvmaster/xo-stack
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge branch 'fix-intro-post-content' into 'development'

Browse Source 
revert change

See merge request GeneralProtocols/xo/stack!136
This commit is contained in:
Emergent Reasons
2025-10-16 08:25:17 +00:00
parent 3b6ff76219 73e75ebc94
commit a39d58356d
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
packages/docs/src/blog/2025-10-15-Intro-to-XO-The-Why-and-the-What.md
+1 -1
View File
@@ -30,7 +30,7 @@ The first fundamental pillar of the XO Stack is the concept of templates. A temp
A template-aware wallet can take a template and some contextual data as input and then construct the required transaction(s) independently. This on its own is a huge step forward, but it’s important to understand that this does not completely remove trust from the equation. Instead, it moves the trust from the app to the templates themselves. While a template-aware wallet can use a template to infer what it needs to do to complete an action, it can’t verify that the human readable descriptions are accurate, or determine whether a resulting action is something a user would actually want to do.
So wallet developers and users must decide which template sources to trust. A wallet developer may pre-approve a select few well known and vetted templates, for instance, an Anyhedge template (Anyhedge is the protocol used by BCHBull), or a Pay to Public Key Hash template (for simple sends). Then, if their wallet allows adding custom trusted templates, a user might decide to add several decentralized exchange templates to their wallet’s trusted list, so that they can trade between Bitcoin Cash and fungible tokens, or add funds to liquidity pools. It’s critical, however, that a user treats new or unknown templates with extreme caution like they would any new financial app.
So wallet developers and users must decide which template sources to trust. A wallet developer may pre-approve a select few well known and vetted templates, for instance, an Anyhedge template (Anyhedge is the protocol used by BCHBull), or a Pay to Public Key Hash template (for simple sends). Then, if their wallet allows adding custom trusted templates, a user might decide to add several decentralized exchange templates to their wallet’s trusted list, so that they can trade between Bitcoin Cash and fungible tokens, or add funds to liquidity pools. It’s critical, however, that a user treats new or unknown templates with extreme caution.
Once a trusted set of templates is established, the benefits follow. Any application that makes use of those templates can pass the transaction construction responsibilities on to your wallet without any additional trust required. For example, you could use any number of different dapps that use the Anyhedge protocol to provide derivatives products, or you could use various decentralized exchanges that use the same swap and liquidity pool protocols. In each case, your wallet will be able to provide human readable descriptions of the actions you’re taking, allowing you to check that an application is doing exactly what it says it’s doing. This is still important because, while your wallet can verify the app is using a trusted template, it doesn’t necessarily know what values you entered in the application’s user interface!