Changelog

Welcome to the Common Feedback Portal!

Here, you can report bugs, share feedback, and suggest new ideas to help us improve.

Select the platform you’re providing feedback for:

Thank you for helping us make Common even better!

Consideration

Ability to stake AZERO directly from Common

From a user point of view, Aleph Zero is the same, so from Aleph Zero's point of view, it's not helpful to view staking, trading and other AZERO activities as different parts of the user's journey. Integrating the AZERO staking dashboard to Common would ensure continuous journey and linkage between azero trading and azero staking. Buy AZERO from Common and stake directly; or unstake AZERO from Common and use it to trade!

Crypto Rockin Over 1 year ago

DEX and Bridge (WASM)

Bug Report: USDT Transactions Appear in Activity but Not Reflected in Wallet Balance

Wallet: Common Extension Wallet (Testnet) Issue Type: Balance display not synchronized with transaction history Description: In the Activities tab of the Common Testnet Wallet, I noticed two incoming transactions of USDT (Tether USD): +46.87 USDT +62.5 USDT However, in the Tokens tab, the USDT balance remains at $0.00, and the tokens are not displayed at all. Steps to Reproduce: Open Common Extension Wallet on the Testnet. Navigate to the Activities tab. Observe incoming USDT transactions from address 0x5B49...7077. Switch to the Tokens tab. USDT balance still shows $0.00, despite the transactions being listed in activity. Expected Behavior: After receiving USDT, the token should be reflected in the wallet balance under the Tokens tab. Actual Behavior: USDT appears in the Activities log, but the balance does not update in the Tokens section. Additional Info: Device: Android Platform/Browser: Mises Browser Extension Version: Common Testnet Wallet (version unknown)

sabila rosa 16 days ago

1

Extension

Bridging fees data are missing

I’ve noticed that the explorer currently only allows users to view the fees for EVM transactions and shielding, but there’s no option to see the bridging fees. This is a significant issue, as it’s unreasonable to expect people to always record the bridging fees separately. Even if they forgetting to do so and later needing to check in the explorer only to find that the information isn’t available is highly inconvenient. A lot people urgently need this for accounting and tax purposes.
In general, a compliance-focused chain should provide all relevant details, including bridging fees, in a comprehensive CSV file. Unfortunately, without this feature, both individuals and companies that depend on accurate accounting will be unable to use Common and zkos. All fees must be clearly visible in the Explorer, especially on a compliance-focused chain. Please prioritize adding a feature that allows all bridging fees to be viewed in the EVM Explorer as soon as possible.

Pauli 4 months ago

6

Extension

Consideration

Single Click Address Copy

Hi, Absolutely in love with how smooth common extension is. Just had some feedback based on personal experience. It would be useful to have the option of copying the wallet address somewhere on the main page of the extension in 1 click rather than having to go through the receive button and getting to the address in 3 clicks. Best, Haider.

haiderwaseem 4 months ago

1

Extension

Planned

Common security safe

It Should be possible to add an extra layer of security to the common wallet, such as a secondary wallet secured with a different password. This would ensure that even if a hacker took control of a user’s wallet, their funds would still remain secure. For instance, when transferring assets into a private vault for confidentiality, there could be an option to lock access with an additional password. This way, even if the main wallet were breached, the private funds would stay protected and could still be retrieved by the rightful owner. If a hacker compress the wallet, and if common had such a dual-protection system, some would have had the opportunity to restore the wallet and reclaim their private funds. The hacker would have only been able to access the publicly visible tokens. Ultimately, it would be each individual's responsibility to safeguard the vault’s password.

Pauli 2 months ago

2

DEX and Bridge (WASM)

Planned

Error Tools

One of the biggest challenges with cryptocurrency is the complexity of interacting with different blockchains, connecting to dapps, and effectively using your tokens. It would be highly beneficial if the Common App and Browser extension incorporated features that prevent user errors, such as: Insufficient funds for transactions or bridge fees. Selecting the wrong network. Transaction failures due to incorrect address input, and more. These errors should be automatically corrected for the user, ensuring that mistakes are eliminated and transactions are never failed. The tool should, of course, be manually adjustable, allowing experienced traders to turn it off as needed.

Pauli About 2 months ago

DEX and Bridge (WASM)

Planned

Double protection of funds of the users

Is there a possibility of having double protection in the common wallet, such as a second wallet with another password, even if a user lost their wallet to a hacker they will still have their funds safe. I mean, to put your funds in the secret vault for privacy there could be the option of shielding this access by password, this way even if the wallet was hacked the private funds would be protected and could be rescued by the user, I suffered a hack on a cosmos wallet, if there was this double protection there would still be the chance to restore the wallet and recover the private funds, the hacker would only have access to the public tokens. It would be everyone's responsibility to keep the safe's password.

Daniel 2 months ago

1

DEX and Bridge (WASM)

Planned

Hello. I am very satisfied with the smooth remittance process of this COMMON extension. A common mistake is to send all the remaining balance in the wallet. If you do that, you won't be able to perform the next operation. I think there is a function to prevent such mistakes by setting it so that one remittance's worth of gas fee is always left over. I may do this sometimes, but I often think about it. Thank you in advance.

高阪佳純 4 months ago

1

Extension

Consideration

UI Feedback

Total Balance Visibility It would be great to have an overview of my total balance across both shielded and public addresses. Currently, once assets are shielded, it’s inconvenient to manually click between views and calculate the total myself. A unified balance display would improve usability and reduce friction. Unshielding UX Improvement While I understand that unshielding is essentially just sending assets back to my public address, having a dedicated “Unshield” button would be a big UX improvement. It would reduce the risk of human error (like copy-pasting the wrong address) and make the flow more intuitive, especially for less technical users.

Martin Dadak 16 days ago

1

Web App