These assets are disabled at bridge but not at polkaswap's swap whitelist. They should be removed from it.

Hi,

Would it be possible to have the chart container minimized or closed if possible (see below):

So that only the swap container appears (as with the previous version of Polkaswap)

Problem Statement

UX/UI layouts contain inconsistent information, unnecessary metrics, wrong calculated metrics and other related to UX parts.

Description

Layouts require adjusting to changes that were discussed on meeting with Artem, Stefan, Viktor, Alexey.
All required fixes and changes are available on Figma.

Definition of Done

• Apply all changes in Figma
• Fix all comments

In Lenguages like Spanish, French, Serbian. The staking info badge text is overflowing the badge as seen on the following images:

polkaswap.io

Last dev build:

The width of the .status-badge class is hard-coded $status-badge-width: 143px;

Previously raised issues may be found in https://soramitsu.atlassian.net/browse/PW-1133

Documentation: sora-xor/sora-docs#7

Problem statement
Ken token Tokenomics was released with update for using token - https://medium.com/@shibarimoto/kensetsu-ken-356077ebee78

Description

Need to describe a vector of attack on KEN token
0. Buy Ken Token

1. deposit collateral token
2. borrow stablecoin (protocol will buy back KEN token by bad price)
3. repay debt
4. Sell KEN token (with profit)

Another vulnerability is unbacked KUSD token that will be minted without collateral tokens as 1% extra.

Definition of done

• Sequence diagram for vector attack on KEN token
• Description of vulnerability on Confluence

People are still able to stuck at bridge sometimes and dont get retry button. Instead of forwarding them to old unstuck guide, can we add a hidden retry anyway button at bridge history which shows itself after confirming some warning messages?

Hi,

I would like to know if you plan to release a new version of the Hashi bridge that allows me to bridge tokens directly from Sora to an ETH address of my choice (i.e. without the need to first send them to a MetaMask account and then to another address).

See the details in https://github.com/soramitsu/sora-card-backend/issues/147

As a

• User

I want to

• Send transfers to accounts which have signed on-chain identities

So that

• I can easily identify the account ID to a name/email/web/social media account

Preconditions

• Add a new property for the search bar which includes all on-chain identities.
• Add a new property which distinguishes accounts which have been provided judgment of "KnownGood"
• Add a new property which can show accounts with an identity level of "No Judgment", with a warning
• Implement this logic for each client (Polkaswap/SORA mobile/Fearless)

Issues

• Can have different accounts with the same on-chain identity (eg, DisplayName) within different networks. Fearless Wallet will need to be able distinguish on-chain identities between different networks.

Flow

No response

Postconditions

No response

Previously tasks were created in https://soramitsu.atlassian.net/browse/PW-800

Sub-tasks

• #1073
• Data indexing
  • sora-xor/sora-subquery#308
• Technical sub-tasks