Git Product home page Git Product logo

wallet's Introduction

Liquality Wallet

Getting started

  • Install NVM
  • Go to this folder repo and run nvm use to takes the right version for node (install if you need it)

Project setup

npm ci

Compiles and hot-reloads for development

npm run dev

and load /dist directory as unpacked extension on Google Chrome.

Developing with wallet-core

If you are simultaneously making changes in the wallet-core lib and you would like to test the wallet with your changes, do the following:

on wallet-core:

yarn
yarn build # or yarn watch

on the wallet:

yarn link /path/to/wallet-core/repo

This will link wallet-core in the wallet with your local version.

If you see dependency errors when you link, try to update any common dependencies to the same version as in wallet-core.

Compiles and minifies for production

npm run build

Lints and fixes files

npm run lint

Run Integration tests

Wallet Integration tests have been written using puppeteer

testNet tests

$ export SEED_WORDS={testNet import wallet 12 words}

Ex: export SEED_WORDS="test1 test2 test3 test4 test5 test6 test7 test8 test9 test10 test11 test12"

$ npm run test:mainnet:prodagent:release

Run single test locally, update the .mocharc.yml values parallel: false jobs: 1 and add .only to the test you want to run.

Releases

Release to Chrome Store

yarn sync-versions

it will update the tag in manifest.json

git tag <TAG NAME>
git push origin <TAG NAME>

Linear.app integration

branch name format: username/liq-xx-title eg: b0b/liq-21-integrate-github-with-linear

License

MIT

wallet's People

Contributors

amritkumarj avatar andonmitev avatar b0b4456 avatar beemi avatar bradleysuira avatar carlsachs avatar dependabot[bot] avatar gr0kchain avatar harshjv avatar jennievon avatar john-light avatar koderholic avatar kraikov avatar lydia-karungi avatar monokh avatar mpwanyi256 avatar renovate-bot avatar renovate[bot] avatar skeremidchiev avatar stephien avatar t0mcr8se avatar tima-t avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

wallet's Issues

Feature request: Trezor hardware wallet support

I would like the ability to connect a Trezor hardware wallet and send/receive/swap using funds/addresses in my hardware wallet.

Edit: Ledger has been supported for a while now, but not Trezor yet

[Feature request] Create different addresses for testnet

Currently Liquality creates the same addresses for testnet accounts as it does for mainnet accounts. I would like for Liquality to generate different addresses for testnet than are generated for mainnet. This is a benefit for privacy and security reasons.

Privacy - because a user can interact with testnets without having to worry about their activity being linked to their mainnet activity. Useful especially when demoing things to other people.

Security - people might be more cavalier with the security of their private keys for testnet accounts, including plugging them into experimental software, etc.

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Warning

These dependencies are deprecated:

Datasource Name Replacement PR?
npm babel-eslint Available
npm eslint-plugin-node Available
npm post-message-stream Unavailable

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

  • Replace dependency eslint-plugin-node with eslint-plugin-n ^14.0.0
  • Update dependency ethers to v5.7.2
  • Update dependency log to v6.3.2
  • Update dependency memoizee to v0.4.17
  • Update dependency puppeteer to v17.1.3
  • Update dependency puppeteer-core to v17.1.3
  • Update dependency qrcode to v1.5.4
  • Update vue-cli monorepo to v4.5.19 (@vue/cli-plugin-babel, @vue/cli-plugin-router, @vue/cli-plugin-vuex, @vue/cli-service)
  • Update actions/setup-node action to v3.8.2
  • Update dependency @eth-optimism/core-utils to v0.13.2
  • Update dependency @ledgerhq/hw-app-eth to v6.38.1
  • Update dependency @ledgerhq/hw-transport to v6.31.3
  • Update dependency @testing-library/jest-dom to v5.17.0
  • Update dependency @vue/devtools to v6.6.4
  • Update dependency amplitude-js to v8.21.9
  • Update dependency bitcoinjs-lib to v6.1.6
  • Update dependency bufio to v1.2.1
  • Update dependency date-fns to v2.30.0
  • Update dependency eslint-plugin-import to v2.30.0
  • Update dependency extension-port-stream to v2.1.1
  • Update dependency i18n-js to v4.4.3
  • Update dependency kcd-scripts to v12.3.0
  • Update dependency node to v16.20.2
  • Update dependency prettier to v2.8.8
  • Update dependency qs to v6.13.0
  • Update dependency sass to v1.79.3
  • Update dependency socket.io-client to v4.8.0
  • Update dependency vue-cli-plugin-browser-extension to ^0.26.0
  • Update actions/cache action to v4
  • Update actions/checkout action to v4
  • Update actions/setup-node action to v4
  • Update actions/upload-artifact action to v4
  • Update dependency @ledgerhq/cryptoassets to v10
  • Update dependency @ledgerhq/cryptoassets to v11
  • Update dependency @ledgerhq/cryptoassets to v12
  • Update dependency @ledgerhq/cryptoassets to v13
  • Update dependency @ledgerhq/cryptoassets to v8
  • Update dependency @ledgerhq/cryptoassets to v9
  • Update dependency @ledgerhq/devices to v8
  • Update dependency @ledgerhq/hw-app-btc to v10
  • Update dependency @testing-library/vue to v7
  • Update dependency @testing-library/vue to v8
  • Update dependency @vue/devtools to v7
  • Update dependency @vue/eslint-config-prettier to v8
  • Update dependency @vue/eslint-config-prettier to v9
  • Update dependency @vue/test-utils to v2
  • Update dependency chai to v5
  • Update dependency copy-webpack-plugin to v10
  • Update dependency copy-webpack-plugin to v11
  • Update dependency copy-webpack-plugin to v12
  • Update dependency copy-webpack-plugin to v7
  • Update dependency copy-webpack-plugin to v8
  • Update dependency copy-webpack-plugin to v9
  • Update dependency date-fns to v3
  • Update dependency date-fns to v4
  • Update dependency eslint to v7
  • Update dependency eslint to v8
  • Update dependency eslint to v9
  • Update dependency eslint-plugin-prettier to v5
  • Update dependency eslint-plugin-promise to v7
  • Update dependency eslint-plugin-vue to v9
  • Update dependency ethers to v6
  • Update dependency extension-port-stream to v3
  • Update dependency extension-port-stream to v4
  • Update dependency husky to v8
  • Update dependency husky to v9
  • Update dependency jest to v28
  • Update dependency jest to v29
  • Update dependency kcd-scripts to v13
  • Update dependency kcd-scripts to v14
  • Update dependency kcd-scripts to v15
  • Update dependency kcd-scripts to v16
  • Update dependency lint-staged to v13
  • Update dependency lint-staged to v14
  • Update dependency lint-staged to v15
  • Update dependency mocha to v10
  • Update dependency node to v18
  • Update dependency node to v20
  • Update dependency node-gyp to v10
  • Update dependency prettier to v3
  • Update dependency puppeteer to v18
  • Update dependency puppeteer to v19
  • Update dependency puppeteer to v20
  • Update dependency puppeteer to v21
  • Update dependency puppeteer to v22
  • Update dependency puppeteer to v23
  • Update dependency puppeteer-core to v18
  • Update dependency puppeteer-core to v19
  • Update dependency puppeteer-core to v20
  • Update dependency puppeteer-core to v21
  • Update dependency puppeteer-core to v22
  • Update dependency puppeteer-core to v23
  • Update dependency sass-loader to v13
  • Update dependency sass-loader to v14
  • Update dependency sass-loader to v15
  • Update dependency sass-loader to v16
  • Update dependency svg-url-loader to v8
  • Update dependency uuid to v10
  • Update dependency uuid to v9
  • Update dependency vue to v3
  • Update dependency vue-router to v4
  • Update dependency vuex to v4
  • Update testing-library monorepo to v6 (major) (@testing-library/jest-dom, @testing-library/vue)
  • Update vue-cli monorepo to v5 (major) (@vue/cli-plugin-babel, @vue/cli-plugin-eslint, @vue/cli-plugin-router, @vue/cli-plugin-unit-jest, @vue/cli-plugin-vuex, @vue/cli-service)
  • 🔐 Create all rate-limited PRs at once 🔐

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

Ignored or Blocked

These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.

Detected dependencies

github-actions
.github/workflows/build-test-prod-mainnet.yml
  • actions/checkout v3
  • actions/setup-node v3.7.0
  • actions/cache v3
  • beemi/puppeteer-headful v1.0.12
  • actions/upload-artifact v3.1.2
.github/workflows/pullrequests.yml
  • actions/checkout v3
  • actions/setup-node v3.7.0
  • actions/cache v3
  • beemi/puppeteer-headful v1.0.11
  • actions/upload-artifact v3.1.2
.github/workflows/release.yml
  • actions/checkout v3
  • actions/setup-node v3.7.0
  • actions/cache v3
  • WyriHaximus/github-action-next-semvers v1.2
  • actions/create-release v1
  • actions/upload-release-asset v1
npm
package.json
  • @chainify/hw-ledger 2.4.1
  • @liquality/cryptoassets 2.12.0
  • @liquality/error-parser 2.2.10
  • @liquality/ethereum-utils ^1.13.12
  • @liquality/terra-networks ^1.13.12
  • @liquality/types ^1.13.12
  • @liquality/wallet-core 4.27.1
  • @terra-money/terra.js 3.1.6
  • @testing-library/vue ^5.8.2
  • amplitude-js 8.18.2
  • babel-eslint ^10.1.0
  • bignumber.js 9.1.1
  • bip39 ^3.0.2
  • bitcoinjs-lib 6.0.2
  • bluebird ^3.7.2
  • bootstrap 4.6.2
  • chai 4.3.6
  • core-js ^3.25.2
  • crypto-js ^4.0.0
  • cryptocurrency-icons 0.18.0
  • date-fns 2.28.0
  • ethers 5.7.0
  • extension-port-stream 2.0.1
  • human-standard-token-abi ^2.0.0
  • i18n-js ^4.1.1
  • lodash-es ^4.17.15
  • log ^6.0.0
  • memoizee ^0.4.15
  • mocha 9.2.2
  • moment ^2.25.3
  • pbkdf2 ^3.1.1
  • post-message-stream ^3.0.0
  • qrcode 1.5.0
  • qs 6.10.3
  • setimmediate ^1.0.5
  • socket.io-client 4.6.1
  • svg-url-loader 7.1.1
  • uuid ^8.1.0
  • v-tooltip ^2.0.3
  • vue ^2.6.11
  • vue-date-pick ^1.4.1
  • vue-js-toggle-button ^1.3.3
  • vue-loader ^17.0.0
  • vue-router ^3.1.6
  • vue-svg-loader ^0.16.0
  • vue-template-compiler ^2.6.14
  • vuex ^3.1.3
  • vuex-persist 3.1.3
  • @babel/eslint-parser ^7.11.0
  • @testing-library/jest-dom 5.16.5
  • @vue/cli-plugin-babel 4.5.15
  • @vue/cli-plugin-eslint ~4.5.0
  • @vue/cli-plugin-router 4.5.15
  • @vue/cli-plugin-unit-jest ^4.5.8
  • @vue/cli-plugin-vuex 4.5.15
  • @vue/cli-service 4.5.15
  • @vue/devtools ^6.4.5
  • @vue/eslint-config-prettier ^6.0.0
  • @vue/test-utils 1.3.6
  • caniuse-lite ^1.0.30001397
  • chai-match ^1.1.1
  • copy-webpack-plugin 6
  • eslint ^6.8.0
  • eslint-plugin-import ^2.23.4
  • eslint-plugin-node ^11.1.0
  • eslint-plugin-prettier ^3.3.1
  • eslint-plugin-promise 5.2.0
  • eslint-plugin-vue ^6.2.2
  • ethereumjs-wallet ^1.0.1
  • husky 7.0.4
  • jest 27.5.1
  • jest-environment-jsdom-fifteen ^1.0.2
  • kcd-scripts 12.0.0
  • lint-staged ^9.5.0
  • markdown-it-vue ^1.1.7
  • node-gyp ^9.0.0
  • prettier 2.5.1
  • priv-key-precommit 0.5.0
  • puppeteer 17.1.2
  • puppeteer-core 17.1.2
  • raw-loader 4.0.2
  • sass 1.49.0
  • sass-loader ^8.0.2
  • sinon-chrome ^3.0.1
  • vue-cli-plugin-browser-extension ^0.25.1
  • @ledgerhq/devices 7.0.7
  • @ledgerhq/hw-transport 6.27.10
  • @ledgerhq/hw-transport-webhid 6.27.10
  • @ledgerhq/cryptoassets 7.3.0
  • @ledgerhq/hw-app-eth 6.30.5
  • @ledgerhq/hw-app-btc 9.1.2
  • @solana/web3.js 1.50.1
  • @eth-optimism/core-utils 0.8.4
  • bufio 1.0.7
nvm
.nvmrc
  • node v16.15.0

  • Check this box to trigger a request for Renovate to run again on this repository

Liquality doesn't list the transactions received of contract call, only recognize the balance

Hi,

Recently I exchanged RBTC to BPRO using moneyonchain.com plataform. On liquality I see the RBTC transaction sending the funds. The transaction was this: https://explorer.rsk.co/tx/0x7dc7ce5cf06aadae17c48ef294eb36fb139f16ba348bb0b50497cdd0521cfd25?__ctab=Transaction

But on Liquality on Birpro asset I see only the balance I received but not the transaction of the Bitpro received. The transaction received should be this one: https://explorer.rsk.co/tx/0x7dc7ce5cf06aadae17c48ef294eb36fb139f16ba348bb0b50497cdd0521cfd25?__ctab=Token%20Transfers

Liquality should show on Bipro asset the transaction received of the value 0.96640397...BITP

`injectedProvider` should default to ask for permission

const RESTRICTED = [
/^chain.buildTransaction$/,
/^chain.buildBatchTransaction$/,
/^chain.sendTransaction$/,
/^chain.sendBatchTransaction$/,
/^wallet.signMessage*$/,
/^swap.generateSecret$/,
/^swap.initiateSwap$/,
/^swap.claimSwap$/,
/^swap.refundSwap$/
]

Better security practice to have a set of whitelisted operations instead of a blacklist. A blacklist is harder to maintain. Default to ask for permission instead.

potential situation: a sensitive CAL method added in the future that isn't updated in the blacklist could be called by any website without a permission prompt.

Product optimization suggestions: help users manage assets more easily

Hello, I am an Internet product designer, and a fan and user of Liquality.

Problem description:
Our users may have many assets on a network, but by default, some of them are hidden by Liquality, such as USDC, USDT and Dai on Polygon
The current product scheme is: users need to search and add an asset in the Manage Asset page. However, when the user searches for USDC, Polygon's USDC is placed last, so he may not notice it.

To facilitate users to view and manage their assets, I have some product optimization suggestions for reference.

1,Add a management link under each network, except BTC
image

2, Only the tokens of the current network are available here.
If we select PUSDC, we will see it on the home page.
image

3, When the user returns to the home page, the selected PUSDC has been displayed.
image

Thank you for taking the time to read my description , I hope Liquality's products are getting better and better

Feature request: Cross-asset, cross-chain payments

Imagine scanning a QR code on a merchant checkout page and being able to pay regardless of what asset is in your wallet and what blockchain that asset is native to. You could have BTC on bitcoin in your wallet, and the recipient could be asking for RBTC on RSK.

You go to checkout, scan the QR code or click the "pay" button, and the wallet automatically populates the recipient address and the payment amount. If the recipient is asking for an asset that you don't have in your wallet, and there is a "path" to make the payment (i.e. the wallet can find an asset in your wallet that it knows a trading pair or path of pairs to the recipient's preferred asset) then you are shown a "sending asset" that you can change (if you have more than one asset in your wallet) and the "recipient asset" that is fixed to whatever the merchant wants to receive. You see the conversion rate, accept, and hit send. The payment is automatically routed to the recipient address, atomically swapped for whatever asset(s) and across whatever network(s) it needs to be to reach the recipient.

Relevant projects that might be useful here, as potential integrations for Liquality's native CAL, are https://interledger.org and https://opendex.network.

Speed up button silently succeeds or fails with no feedback

I think we should give feedback or notification to users to let them know the 'Speed Up' succeed besides the fact that gas fee has been updated after they speed up the transaction cause when it comes to failure with speed up user'll know. I'd like to propose add a speed up record on the deal page, which can tell users directly. But the details need to consider further.

Here is the link where one user talks about it.
https://discord.com/channels/745324936607957022/878230427532423198/932068459133677609

unknown-10

这里体验不是很快,就算我speed up 好像并不会显示我speed up 到底有没成功
The experience here is not very fast, even if I speed up it doesn't seem to show whether my speed up is successful or not.

i'm a user of Liquality wallet and also Moderator of the community. From the user's experience and also my own i'd like to propose one suggestion about 'Speed up' on Liquality:

Finally i really appreciate the team's effort, Liquality wallet has been much smooth recently.

[Ledger] Feature request - BTC addresses

If you connect a Ledger device with Bitcoin addresses (native SegWit Bech32) already used, you can only select the first Address, despite this has already been used and no longer has funds.

  • Enable the option to select an Account from the Ledger device that is not only the first one. Currently, only the first address is available for selection when connecting a Ledger device.

  • Check for used and empty addresses and show the last one used that has funds or the following one that hasn't been used nor has funds (up to a gap limit). This way the expected address is selected (not empty or not used yet).

Another note: change addresses' funds are not being shown as available in the wallet, Liquality needs to check change addresses until a gap limit to look for change addresses with funds

Edit the settings of a custom token (decimal)

Hello,

I would like to modify the configuration of the decimal in a custom token that I added to the wallet.

But I have not found how to delete the custom token (to recreate it afterwards with the correct number of decimal places), or simply update it.

Are there any solutions? Via the javascript inspector for example?

Thanks for your help !

NEAR and Liquality Wallet dApp integration

Description

Hi,

I am trying to use Liquality Wallet with a NEAR account from a dApp you can see the example here:

https://github.com/kujtimprenkuSQA/liquality-near-example/

There are a few things I would like to point out that could really improve the experience and fix some potential bugs/weird behaviors.

(issue) window.near conflicts with other extension wallets

The window.near namespace conflicts with another wallet SenderWallet if both wallets are installed then the window.near will always return the injected options from the SenderWallet and not LiqualityWallet

(bug) window.near.enable() method works only if you confirm the connection.

In the above example if you click the Connect with Near button which in the end calls:

await window.near.enable();

The liquality wallet opens a window to confirm the connection if we confirm it it works perfectly but the issue is if we Cancel or close the window in X at this moment I am not sure why but if we try to call window.near.enable(); for the second time it returns undefined and the popup never opens until you close the Browser and reopen it.

(bug) Actions propertynot being passed down

When trying to call wallet_sendTransaction method through window.near.request() from my understanding I think the actions key/property is not being sent to the sendTransaction function which is exposed by near-js-wallet-provider

const signAndSendTransaction = await window.near.request({
  method: "wallet_sendTransaction",
  params: [
    {
      to: "kujtim.testnet",
      value: "0",
      data: "", 
      actions: [
          "this is an invalid action but does not get triggered"
      ] 
    },
  ],
});

It looks like you are not passing the actions to the sendTransaction method.
In the PermissionSend.vue component you make a call to this method replyPermission (vue store action)

And the replyPermission then dispatches another event executeRequest

Which in the end executes this check, and you can see there's no actions key in the payload for sendTransaction event.

What happens is that in the end this if block is executed since in this case options.actions would be undefined at this point a Transfer action is being created by default.

(issue) there's no way to disconnect/ logout once you're connected.

If you call await window.near.enable(); and confirm the connection then there's no way how you can logout or disconnect from the dApp unles you close the browser window.

ETH fee shown (and USD equivalent) is incorrect

See screenshot. Gas fee in ETH is shown as ~0.0036 and the USD equivalent is shown as $0.01. However at current market price of $4568/ETH 0.0036 is equal to $16.81

The gas estimate in ETH is also wrong: this transaction ended up costing ~0.01 ETH, not the ~0.0036 ETH shown. So the UI was off by nearly a factor of 3.

liquality_fee

Bug - blank screen Get ETH button

If you go to an empty ETH address and click Swap, you are shown a notice with a 'Get ETH' button. If you click on it an empty wallet-like screen is shown and if you click any of the three buttons (Send, Swap, Receive) a blank screen appears.

Liquality_Get_ETH_blank_screen

[Ledger] Feature request - Accounts selection

Enable the option to select an Account from the Ledger device that is not only the first one. Currently, only the first address (Ledger Live derivation path) is available for selection when connecting a Ledger device.

v0.13.0 fails to inject web3 when RSK asset is selected

Steps to reproduce:

  1. Set Default Web3 Wallet toggle to enabled
  2. Set Web3 Asset to RSK
  3. Open browser dev tools and write window.ethereum to console
  4. Receive error: Uncaught ReferenceError: ethereum is not defined

Also there is visible error once console opened:

Error handling response: TypeError: Cannot read property 'mainnet' of undefined
    at chrome-extension://kpfopkelmapcoipemfendmdcghnegimn/js/content-script.js:154:177395

Feature request: Detect whether the user's target wallet has enough fee before the user initiates a cross-chain transaction

In terms of user experience, when a user tries to initiate a cross-chain swap from one chain to another, could the user be informed in advance that the target wallet does not have enough funds to cover the gas fees for the claim, it will greatly prompt the user's experience

Add a feature that checks the target wallet before swap, and if the target wallet does not have enough funds for gas (provided it is needed) it will not allow swap to be initiated.

[Ethereum] Liquality does not work with some dapps

I expect that anywhere MetaMask works, Liquality would work as well. However after some testing I notice that Liquality does not work (or has some UX flaws working) with the following Ethereum dapps:

Dapp URL Attempted connection method
https://client.aragon.org Connect via Unknown
https://curve.fi Connect via MetaMask
https://app.daohaus.club/ Connect via Liquality - Liquality shows up as an option, but the screen goes blank once the approve button is clicked in the Liquality popup
https://oasis.app/connect Connect via MetaMask - this works, but Oasis still suggests installing MetaMask
https://yearn.finance Connect via MetaMask
https://zk.money Connect via MetaMask

Integrate Pocket Network as a default infra provider

What is Pocket Network?
Pocket Network is a decentralized blockchain API built for Web3 apps, relaying data to and from any blockchain through a network of thousands of nodes. The Pocket Network protocol validates all relayed data and proportionally rewards the participating nodes with POKT.

Why Pocket Network?
Instead of deploying to a single service provider, paying absurd fees for random outages and leaked data, you could use Pocket’s trustless API protocol and route your requests to thousands of independent full nodes. Available for all major blockchain networks.

You now don't rely on Infura but on a decentralized network of people providing their services to access any supported blockchain with a huge variety of locations, capacity & availability.

Benefits:

  • Easy management & monitoring via a dashboard
  • No single point of failure
  • Decentralized
  • Incentivizing more people to run full nodes across different chains

How would Pocket be integrated?

  • Use a Pocket endpoints as a default endpoint on the wallet for networks that are supported.

Sign up for a free Application ID on Pocket Network.

Feature request: Automatically switch to the correct network

When I connect to a dapp, sometimes Liquality is still on testnet from the last time I used it when it should be on mainnet for the dapp I am trying to use. It'd be nice if the dapp could send a request to Liquality to open the correct network, and Liquality would pop up and ask: "Would you like to switch from [current network] to [correct network]? Yes/No". This would be similar to the flow when Liquality asks the user which account they want to connect to a dapp with, and in fact could be part of this same flow if that selection still needs to be made.

A related feature that might be useful here is having a setting that enables automatically switching Liquality to the correct network, so that a user can go from dapp to dapp seamlessly, even when dapps are on different networks, without having to manually switch the network.

Feature request: Revoke dapp access permissions

Every time I visit a new dapp, I have to approve its access to my Liquality account. However, as far as I can tell, there is no way to revoke a dapp's access permission once I have granted it. I would like the ability to revoke, one by one, the access permissions for each dapp I have previously granted access.

Release notes?

Hey there, I keep getting hammered with "new release" emails (more than from any of the other repos that I follow), but there are never Release Notes included. Any chance you could include 2-3 bullets maybe to make it easier for us to judge if a specific release is worth checking out? For now I disabled the emails, because it was just not useful without a change log.

[RSK] Cannot see full amount sent

I sent 0.0000001 RBTC but the amount shown on the send screen and activity screen is 0 RBTC. I would like to see precisely how much I am sending.

L3

L4

Proposal: Allow user to enter exact gas fees

Currently there is only the option to set low/medium/high gas fees, with no control over exact rate used. It would be good if there was an advanced setting that allowed for entering in exact fee amount

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.