* 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
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.
Removed properties from `Path` type:
- `MaxFeesPerGas`, based on the sending flow progress appropriate new properties (`TxMaxFeesPerGas`, `ApprovalMaxFeesPerGas`) should be used
Added new properties to `Path` type:
- `RouterInputParamsUuid`, used to identify from which router input params this path was created
- `TxNonce`, used to set nonce for the tx
- `TxMaxFeesPerGas`, used to set max fees per gas for the tx
- `TxEstimatedTime`, used to estimate time for executing the tx
- `ApprovalTxNonce`, used to set nonce for the approval tx
- `ApprovalTxMaxFeesPerGas`, used to set max fees per gas for the approval tx
- `ApprovalTxEstimatedTime`, used to estimate time for executing the approval tx
New request types added:
- `PathTxCustomParams`, used to pass tx custom params from the client
- `PathTxIdentity`, used to uniquely identify path (tx) to which the custom params need to be applied
New endpoints added:
- `SetFeeMode` used to set fee mode (`GasFeeLow`, `GasFeeMedium` or `GasFeeHigh`)
- `SetCustomTxDetails` used to set custom fee mode (`SetCustomTxDetails`), if this mode is set, client needs to provide:
- Max fees per gas
- Max priority fee
- Nonce
- Gas amount
Needed for https://github.com/status-im/status-desktop/issues/16896
Having `PinnedBy` directly in the Message object makes it way simpler in the client to know if a message is pinned. This saves us from having to keep a cache of the pinned messages and comparing all new messages.
* test_: add option to get file from status-backend container
* feat_: automatically create dataDir and logsDir directories
* test_: unskip and update TestInitializeLogging
* fix_: parametrize test
* ci_: use ms precision for func tests docker project_name to
* chore_: rename to extract_data
* fix_: linter
* fix_: set timestamp in python as well
Needed for https://github.com/status-im/status-desktop/issues/16640
In Desktop, we still used a "forked" version of the BlockContact function that had as differences that it didn't leave the chat nor delete the messages.
However, we want to have parity now and those features, so it makes no sense to use a different function.
This is a breaking change because it removes an API, but I took care of removing the use of that function in the Desktop app and Mobile never used it, so it's an inoffensive breaking change.
Additionally, I added the notifications to the messenger response.
From and to chains added to SendDetails type that can be used on the client side if the sending fails
that we can display appropriate ephemeral notifications, saying sending from which chain has failed.
test_: fewer nodes for multiple_contact_requests test
test_: fewer nodes for multiple_contact_requests test
test_: skip multiple_contact_requests test
test_: address review comments
test_: check messages just in event/messages
test_: get expected message by content type
test_: address review comments
Found when fixing https://github.com/status-im/status-desktop/issues/16639
When a message is deleted, we need to delete the pins too as they are no longer available. This was done using an ON DELETE clause (thanks @osmaczko)
I also made sure the SELECT query for the pins doesn't return deleted messages
