Zypsy5 Fundamental Web3 Design Principles
IntroductionAs the number of decentralized apps (dApps) grows, it's important to remember certain basic web3 design principles when designing a dApp. Furthermore, developing these apps requires following a set of UI/UX guidelines. This article will summarize a framework of UX standards for blockchain-based distributed applications based on beltran's web3 design principles.Transparent and TrustlessTransparency and trustlessness are two essential elements of web3. Designers should wor...
ZypsyHow to Launch a DAO
IntroductionIf you’ve been learning about web3 for a bit of time, you’ve probably seen the term “DAO” more than a couple of times. As you may have learned, DAOs, or Decentralized Autonomous Organizations, are pretty much everywhere in web3. These new decentralized, community-led entities are the coordination layer of web3 and have been touted as the future of work. In case you’re still wondering what DAOs are, think of them as an organization led by the people working in them. The community o...
ZypsyWeb3 Design Principle: Data Transparency
IntroductionWeb3 is a new paradigm for using the internet that enables people to do things in ways they couldn't before. This new wave of technology allows users to take control of their digital lives and data, by creating a more transparent way of sharing information. Transparency is one of the core components of web3, as the way we display blockchain data will create an impact on how users read the data. Therefore, users in Web3 need to be able to understand and tell where the data or ...
An ownership-based design team for founders
Zypsy5 Fundamental Web3 Design Principles
IntroductionAs the number of decentralized apps (dApps) grows, it's important to remember certain basic web3 design principles when designing a dApp. Furthermore, developing these apps requires following a set of UI/UX guidelines. This article will summarize a framework of UX standards for blockchain-based distributed applications based on beltran's web3 design principles.Transparent and TrustlessTransparency and trustlessness are two essential elements of web3. Designers should wor...
ZypsyHow to Launch a DAO
IntroductionIf you’ve been learning about web3 for a bit of time, you’ve probably seen the term “DAO” more than a couple of times. As you may have learned, DAOs, or Decentralized Autonomous Organizations, are pretty much everywhere in web3. These new decentralized, community-led entities are the coordination layer of web3 and have been touted as the future of work. In case you’re still wondering what DAOs are, think of them as an organization led by the people working in them. The community o...
ZypsyWeb3 Design Principle: Data Transparency
IntroductionWeb3 is a new paradigm for using the internet that enables people to do things in ways they couldn't before. This new wave of technology allows users to take control of their digital lives and data, by creating a more transparent way of sharing information. Transparency is one of the core components of web3, as the way we display blockchain data will create an impact on how users read the data. Therefore, users in Web3 need to be able to understand and tell where the data or ...
An ownership-based design team for founders
Subscribe to Zypsy
Subscribe to Zypsy
Share Dialog
Share Dialog
<100 subscribers
<100 subscribers
Envision a future where web3 technologies are widely adopted. Where each user engages with multiple Dapps, tokens, and chains as they normally would with typical apps. But instead of a centralized server keeping logs of your past interactions, it’s transparent and on-chain for you to view. In this future, we believe that it is necessary for the user to be able to have full transparency and accessibility of their own transaction history.
While most wallets do already provide users with a list of all the transactions and interactions made, wallets are extremely limited in that they only store the transactions of the wallet’s account. When users inevitably interact with multiple Dapps as well as use different wallet addresses, the flaw of not being able to see an overall picture of the user’s transactions becomes apparent.
Below are the 3 things to be aware of when designing for transparency and accessibility in user transaction history.
In e-commerce, it's quite common to see an order history page as the history page helps drive more conversions for habitual buyers. In your browser, the history page allows you to see what websites you’ve visited in the past and if need be, visit them again.
As you can probably tell, a history page is not just a page with a list of past interactions, it’s a page focused on providing the tools necessary for users to achieve their end goals.
In web3, transactions equal interactions. Whether it is you sending a bit of ETH for staking or using your governance tokens to initiate a proposal, all interactions are recorded on the blockchain ledger. If we want to have a future where transparency is a core constituent, allow users to inspect all transactions they have made with the smart contract from a given address.
On the other hand, if you are providing a user with their interaction history, then that means that the data of the transaction hashes are stored somewhere. The history can be stored on a database or on the user’s local indexDB.
In the spirit of transparency, you need to clarify to the user where this data is stored, as how it is stored may pose a potential privacy risk.
Going back to what we’ve discussed previously with the different types of user end goals, you should also provide management tools that support the users in completing their end goals.
If we were to break down the typical goals a user has when visiting the transaction history page, the 2 most common goals would be:
to view a particular transaction
to remove records they deem unwanted
Empower the users by making these processes easier with common tools such as a search bar, filter options, the ability to export the history, and if possible the ability to delete certain data from their history list.
A history page is quite straightforward, and designers can pull from patterns that have been used extensively in e-commerce, fintech, browser history, etc.
The difference here with web3 transaction history is once again the principle of transparency. This requires you to think about how users will be using the list of past transactions and provide them with the necessary information and tools.
Keep in mind it's not just about showing past transactions, but also the whole history of interactions a user had.
Envision a future where web3 technologies are widely adopted. Where each user engages with multiple Dapps, tokens, and chains as they normally would with typical apps. But instead of a centralized server keeping logs of your past interactions, it’s transparent and on-chain for you to view. In this future, we believe that it is necessary for the user to be able to have full transparency and accessibility of their own transaction history.
While most wallets do already provide users with a list of all the transactions and interactions made, wallets are extremely limited in that they only store the transactions of the wallet’s account. When users inevitably interact with multiple Dapps as well as use different wallet addresses, the flaw of not being able to see an overall picture of the user’s transactions becomes apparent.
Below are the 3 things to be aware of when designing for transparency and accessibility in user transaction history.
In e-commerce, it's quite common to see an order history page as the history page helps drive more conversions for habitual buyers. In your browser, the history page allows you to see what websites you’ve visited in the past and if need be, visit them again.
As you can probably tell, a history page is not just a page with a list of past interactions, it’s a page focused on providing the tools necessary for users to achieve their end goals.
In web3, transactions equal interactions. Whether it is you sending a bit of ETH for staking or using your governance tokens to initiate a proposal, all interactions are recorded on the blockchain ledger. If we want to have a future where transparency is a core constituent, allow users to inspect all transactions they have made with the smart contract from a given address.
On the other hand, if you are providing a user with their interaction history, then that means that the data of the transaction hashes are stored somewhere. The history can be stored on a database or on the user’s local indexDB.
In the spirit of transparency, you need to clarify to the user where this data is stored, as how it is stored may pose a potential privacy risk.
Going back to what we’ve discussed previously with the different types of user end goals, you should also provide management tools that support the users in completing their end goals.
If we were to break down the typical goals a user has when visiting the transaction history page, the 2 most common goals would be:
to view a particular transaction
to remove records they deem unwanted
Empower the users by making these processes easier with common tools such as a search bar, filter options, the ability to export the history, and if possible the ability to delete certain data from their history list.
A history page is quite straightforward, and designers can pull from patterns that have been used extensively in e-commerce, fintech, browser history, etc.
The difference here with web3 transaction history is once again the principle of transparency. This requires you to think about how users will be using the list of past transactions and provide them with the necessary information and tools.
Keep in mind it's not just about showing past transactions, but also the whole history of interactions a user had.
No activity yet