Describe the bug
QR Code Scanner fails to scan input fields on Send Transaction view when scanning QR Code contains an EIP-681 URI

Example URI

ethereum:0x46c69f4424043e720a704330748cf3c593656b9c

To Reproduce
Steps to reproduce the behavior:

1. Go to Send Transaction view
2. Click on QR Code scanner
3. Position QR Code in front of Webcam
4. QR Code scanner closes

We should apply sorting to the list of installed apps in the App Center (we "randomize" the discovery page to make it a bit more "fun"):

1. Upgrades available ahead of up to date apps
2. Alphabetical

cc @bpierre @dizzypaty I've also been wondering if it might be nice to start having sections in the App Center similar to Voting, for the different classes of apps (e.g. "ready" vs. "experiment

I left a review and then got this message

which seems strange as it's telling me something I know.

ordering rule shows false positive when there is an external receive function before the fallback functions. For example, for this contract:

contract Test {
    receive() external payable {
    }

    fallback() external payable {
    }
}

Solhint generates this warning:
`Function order is incorr

Currently, we are not able to
a) symbolically execute init code with symbolic arguments
b) get srcmapping for init code with arguments

We could change ContractCode as follows:

data ContractCode
  = InitCode (ByteString, Buffer)    -- ^ "Constructor" code, during contract creation (possibly with arguments)
  | RuntimeCode ByteString           -- ^ "Instance" code, after contract crea

PAN doesnt work on cryptocompare... it doesnt work for PAN... and it doesnt have to be coin gecko... but it needs to be some service that has PAN

When use formatToEthereumUnits from Web3.Utils it use decimals parameter, and after format BigInt it's may create many redundant zeros at the end. For example if 'decimals' parameter is 18 we have: 990000000000000 wei -> 0.000990000000000000 eth

At old repo already have similar issue:
BANKEX/web3swift#200

and some solution:
https://github.com/v57/web3swift/commi

Describe the solution you'd like and the expected behavior

When sending assets I want to be able to send the full amount of at once without typing in the 8 decimals

Is your feature request related to a problem? Please describe.

Typing sucks