The subscan-multisig-react from subscan-explorer

Check out the screenshot below.

rename extrinsic router to account

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Feature Request: Remember multi-sig member and contacts

Given I have created a multi-sig wallet with several member addresses and their names, 
When I am creating a new multi-sig wallet involving those addresses,

When I input the address, 
Then the app should auto-fill the name field for me.

When I open the address dropdown menu,
Then the list of known addresses should include not only my connected addresses but also those from my contacts

This may be achieved with a "Contacts" section, which saves member addresses with their name labels when this info was provided in the wallet creation process or manually created in the "Add a Contact" form on the "Contacts" page.

ui 改进

Can not click cancel or create button when creating wallet account on mobile

The cancel and confirm buttons are overlapped by footer.

Theme for crab network doesn't seem right

show loading page if rpc disconnected

show loading or freeze page

It should display 0 instead of blank

Refresh enchance

Sometimes refresh action breakdown the apps, seems that account data parse failed

approve/cancel 一个多签交易的时候，默认给了一个签名成员，无法更改为其他成员

发起了一个bond的多签交易，点击展开详情，报错

TypeError: A.toLowerCase is not a function
at main.6f8d488f.chunk.js:1
at main.6f8d488f.chunk.js:1
at Of (main.6f8d488f.chunk.js:1)
at ro (2.34664fa1.chunk.js:2)
at qc (2.34664fa1.chunk.js:2)
at Ss (2.34664fa1.chunk.js:2)
at Ms (2.34664fa1.chunk.js:2)
at js (2.34664fa1.chunk.js:2)
at vs (2.34664fa1.chunk.js:2)
at 2.34664fa1.chunk.js:2
cc @ 2.34664fa1.chunk.js:2
2.34664fa1.chunk.js:2 TypeError: g.map is not a function
at Of (main.6f8d488f.chunk.js:1)
at ro (2.34664fa1.chunk.js:2)
at qc (2.34664fa1.chunk.js:2)
at Ss (2.34664fa1.chunk.js:2)
at Ms (2.34664fa1.chunk.js:2)
at js (2.34664fa1.chunk.js:2)
at vs (2.34664fa1.chunk.js:2)
at 2.34664fa1.chunk.js:2
at t.unstable_runWithPriority (2.34664fa1.chunk.js:2)
at Ui (2.34664fa1.chunk.js:2)
cc @ 2.34664fa1.chunk.js:2
2.34664fa1.chunk.js:2 Uncaught TypeError: A.toLowerCase is not a function
at main.6f8d488f.chunk.js:1
at main.6f8d488f.chunk.js:1
at Of (main.6f8d488f.chunk.js:1)
at ro (2.34664fa1.chunk.js:2)
at qc (2.34664fa1.chunk.js:2)
at Ss (2.34664fa1.chunk.js:2)
at Ms (2.34664fa1.chunk.js:2)
at js (2.34664fa1.chunk.js:2)
at vs (2.34664fa1.chunk.js:2)
at 2.34664fa1.chunk.js:2
DevTools failed to load source map: Could not load content for chrome-extension://ibnejdfjmmkpcnlpebklmnkoeoihofec/dist/TronWeb.node.js.map: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME

When initiating a multi-signature transaction, please calculate and display the value that needs to be reserved

连续点击成员账号，没有每个账户都在新标签页打开链接

prompt user if polkadot extension is not allowed to interact with the app

open Polkadot extension ----> Manage Website access ------> denied access

Access multisig website, there is no tips indicate the apps can not get account information from Polkadot extension.

cancel 交易的时候报错

Dark mode optimization

可以参考 polkadot js 的黑暗模式，设置方法：
https://polkadot.js.org/apps/?rpc=wss://pangolin-rpc.darwinia.network#/settings

@polkadot/extension-dapp failed to detect user account.

Describe the bug
@polkadot/extension-dapp failed to detect user account

To Reproduce
Steps to reproduce the behavior:

Go to 'https://multisig.subscan.io/#n%3Dcrab'
Click on 'Accounts'
See error

Expected behavior
Accounts should show user accounts.

Screenshots

Desktop (please complete the following information):

OS: [macos]
Browser [chrome]
Version [94]

Header element not aligned to the side

The two element blocks "logo" and "menu" are not pushed to the end of the container. In the screenshot below, the content container below is far wider than the header. It's quite rare to see a design like this.

Invalid grant logo in README.md

Network status error

network connection status error after switching network

The error status leading wallet display problem

node 14 or 15

I can only run yarn install with node 14

yarn start produces OOM error and only works under node 15

外部账号不可发送交易

The github link at footer should direct to this repo instead of Subscan essentials

Data structure adpater with subql

The server returned a data structure that did not meet expectations

Support more networks by configuring custom endpoints

Multi-signature accounts with the same parameters (members + threshold) should not only exist in one network at the same time

Describe the bug
参数相同（多签成员+阈值）的多签账号，只能同时存在一个网络

To Reproduce
Steps to reproduce the behavior:

进入kusama网络，点击创建多签钱包，使用a,b,c 3个账号，阈值设置为2/3，创建成功！
切换到polkadot网络，点击创建多签钱包，使用a,b,c 3个账号，阈值设置为2/3，创建成功！
See error：重新切换到 kusama 网络，刚刚创建好的多签钱包消失了

a,b,c为3个固定的地址

Expected behavior
在创建钱包时，用户可以选择是否将这个钱包同步到所有网络。

如果用户选择将这个钱包同步到所有网络

流程示例：
1）进入kusama网络，点击创建多签钱包，使用a,b,c 3个账号，阈值设置为2/3，用户勾选将此钱包同步到所有网络，创建成功！
2）多签钱包支持的所有网络，都按照a,b,c 3个账号，阈值设置为2/3的参数，新增一个多签钱包（如果某网络已添加了一个相同的钱包，自动去重）

如果用户选择不将这个钱包同步到所有网络

流程示例：
1）进入kusama网络，点击创建多签钱包，使用a,b,c 3个账号，阈值设置为2/3，用户未勾选将此钱包同步到所有网络，创建成功！
2）多签钱包仅在当前网络（kusama）创建多签账户，此账户和其他网络相同参数的账户不冲突，可同时存在。

Network info in the URL

Is your feature request related to a problem? Please describe.
When an operator initiates an extrinsic, he would normally copy the URL and share it with other operators. Other operators click the URL and visit the page, they will see either the last chain/network they visited or the default chain/network which is Pangolin. In most cases the default is wrong. Operators will feel confused.

PS: the global fallback default chain should point to a most commonly used chain by traffic, either Polkadot or Kusama.

Describe the solution you'd like
Network info &chain=xxx should be in the URL. The link will reflect the correct chain when visiting the page from a shared link.

Describe alternatives you've considered
The solution may be when the current chain is determined (by the procedure mentioned in issue #25 ), rewrite the URL, and append/replace the chain parameter with the selected chain.

do not reload window if switch network

The window must be reloaded when switching networks to ensure that the keyring is reloaded.

packages/react-api/src/Api.tsx.

keyring.loadAll can not reload after initialized, but then if the API instance change, we must either reload the keyring or use another keyring instance and load the accounts under the network specified by API

To solve the issue described above, it is currently simple to trigger all state refreshes by reloading the page, in fact, https://polkadot.js.org/apps also use this approach to switch network

https://github.com/polkadot-js/apps/blob/813f17bbbcc491e63377852593ddfceb1e0fbeeb/packages/apps/src/Endpoints/index.tsx#L240

But as a SPA, the best practice is to drive view changes through data, at least 2ways here:

use Keyring constructor to generate a new instance as soon as the Polkadot API changed;
keyring can unload the old accounts or reloadable to refresh account;

history loop query or refreshable

#41

can refresh history records manually

按钮失去焦点后会变透明

Specify chain in the URL and remember last choice

There should be a way to specify the target chain in the URL so that third-party wallets can point to the multi-sig app directly with the proper chain selected by default.

As the URL for the multi-sig app is multisig.subscan.io, this could be in the following format, sub-host, or URL parameter:

https://[chainid].multisig.subscan.io
https://multisig.subscan.io/?chain=[chainid]

Either one should work.

Remembering the user's last chain selection would be handy as well:

If chain selection is explicitly specified, use it (fetched from query string or host variable mentioned above)
Otherwise, if the last selected chain info exists in the cookie or local storage, respect that
Otherwise, if the environment states that chain, respect that (not sure when wallet opens an in-wallet app, whether it passes some environment variable)
Otherwise, use the default chain determined by site configuration

Assemble wallet from extrinsic

Is your feature request related to a problem? Please describe.
When visiting an extrinsic link shared by another operator who initiated it, the operator is not able to sign it unless the wallet is created properly already. He must collect members' address info, and register the wallet first.

Describe the solution you'd like
Fetch wallet info from the extrinsic and set up the wallet for the operator if it's not existed.

Describe alternatives you've considered
When creating the wallet for the operator and saving it to local storage, default label names can be assigned to the member addresses. The operator can modify this info later.

Display 3 member address inputs when wallet creation

Since the member threshold for the multi-sig wallet is 2, it implies 2/3 will be the most popular scenario, displaying 3 member inputs directly will be handy for most of the users.

Better hide Initiate Extrinsic button if the account is unavailable

Improvement: display address name/label with address

If the address name/label can be displayed with the address, it will be much more useful when selecting my address.

鼠标悬浮在 icon 上，tooltip 展示操作名

在无法获取到call data 的时候，需要让用户来手动填写call data，用于获取交易参数

目前无法获取通过其他钱包发出的多签交易信息，是不是有自动获取 call data 的方案

Add node version description in package.json

The license icon in the readme doesn't seem right.

It should be Apache-2.0 License

Added call data for confirmed / in progress multi-signature extrinsic

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

subscan-explorer / subscan-multisig-react Goto Github PK

subscan-multisig-react's People

Contributors

Stargazers

Watchers

Forkers

subscan-multisig-react's Issues

Recommend Projects

Recommend Topics

Recommend Org