Closed 1xstj closed 1 month ago
Name | Link |
---|---|
Latest commit | 6424432fe0650056627e773e9775dccaa53ab33c |
Latest deploy log | https://app.netlify.com/sites/tangle-docs/deploys/66e43ffb6b49fc0008e66862 |
Deploy Preview | https://deploy-preview-53--tangle-docs.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
We're currently using the term 'vault' in our UI design, similar to systems like Tenderize.me and Symbiotic. However, understanding that Polkadot.JS uses the term 'pool' for similar functionality and to ensure consistency / avoid user confusion:
- Should we maintain 'vault' in our UI and add clarification in our documentation that this corresponds to 'pools' in Polkadot.JS?
- Or should we align our terminology with Polkadot.JS and change all mentions of 'vault' to 'pool' in our UI for both liquid staking / restaking?
cc @AtelyPham @yurixander
In the context of restaking, we will use "vault" instead of "pool."
Ya worth the-emphasizing @monaiuu that we use the word pool when describing things related to staking and liquid staking (because they're built on pool semantics) but we use the term vaults when we are discussing things related to restaking (because the vault secures services, a la bank vault, etc.). Definitely make sure you establish this semantic difference in your vocabulary. We will be using it moving forward.
Ya worth the-emphasizing @monaiuu that we use the word pool when describing things related to staking and liquid staking (because they're built on pool semantics) but we use the term vaults when we are discussing things related to restaking (because the vault secures services, a la bank vault, etc.). Definitely make sure you establish this semantic difference in your vocabulary. We will be using it moving forward.
Yes, on the liquid staking side I'm using the term "pool" both in the code and the UI.
Summary of changes
Provide a detailed description of proposed changes.
-
Proposed area of change
Put an
x
in the boxes that apply.Overview
Anchor System
dApps
Tangle
Protocols
Relayers
Reference issue to close (if applicable)
Specify any issues that can be closed from these changes (e.g. Closes #233).
Code Checklist