- A new contract is used for estimating L1 fee.
- New contract's addresses are known only for Optimims and Sepolia Optimimsm.
- Old contract and addresses per chain are kept so far, but not in use anymore.
Comparing to other wallets, seems L1 fee is added to the total fee only for the Optimims chain.
So we're doing the same in this commit, disabling L1 fees for other than the Optimism.
While ago we've disabled l1 info cause the estimated L1 fees were significantly higher than they should have been
(if I remember well, the L1 fees were about 1000 times higher than they should have been).
From this point, that wrong value might be coming from unreliable pokt calls/values, these changes bring them back.
* chore(config)_: Integration of new RPC Provider configurations
* default_networks.go
* explicit provider initialization with more granular config (rps limiter, order)
* token overrides made more flexible, support not only infura and grove
* get_status_node.go
* override status-proxy auth instead of passing override config to rpc/client.go
* config.go
* ProviderConfig removed
* client.go
* Now any provider can be enabled/disabled (if user wants to use only his custom RPC urls)
* Use bearer auth instead of URL auth
* Provider order is defined by default_networks.go
* Do not store embedded RPC provider credentials in the DB
* FIXME: TestLoginAndMigrationsStillWorkWithExistingDesktopUser uses deprecated test data (with non-existing related_chain_id in networks table)
* test_: reactivate reliability workflow
* test_: reactivate reliability workflow
* test_: use foundry stable
* test_: remove test branch
* test_: run tests in parallel
* test_: fix zizmor warnings and test it
* test_: remove on push
This is a breaking change which removes `communitytokens` package.
This commit removes old `communitytokens` package, cause previously added `communitytokensv2` package,
which is in use now, will be renamed to `communitytokens` in next commit.
This commit:
- updates both status docker container names to include short git sha locally and BUILD_ID on CI
- updates cleanup command to filter by identifier which could be either git sha or BUILD_ID
- updates the cleanup stage in `jenkins` file to remove docker container via this identifier
This approach is more reliable in cleaning up docker containers and was tested by me on linux-05
This changes updates the logic for generating identity-images to populate the `clock` value instead of initialising with zero. This change also updates the identity-image url format functions to include the `clock` value in the returned url so clients can rely on that url for triggering refetches of identity images when they've been updated.
- `Path` type extended with the following fields:
- `SuggestedMinPriorityFee`, suggested min priority fee by the network
- `SuggestedMaxPriorityFee`, suggested max priority fee by the network
- `CurrentBaseFee`, current network base fee
- The following wallet api endpoints marked as deprecated:
- `GetSuggestedFees`
- `GetTransactionEstimatedTime`
Fixes https://github.com/status-im/status-desktop/issues/15849
The problem was that we generated a "fake" contact request for all synced contacts.
While it's true that even mutual contacts have a contact request, we don't need it anymore once mutual and since we don't sync messages, we had to generate it with a default message and that message looked very out of place after a recovery.
