This relates to @stacks/connect and @stacks/transactions having different "network" types.
@stacks/connect methods uses NetworkString:
export type NetworkString = LiteralUnion<'mainnet' | 'testnet' | 'regtest' | 'devnet', string>;
@stacks/transactions methods uses StacksNetworkName | StacksNetwork:
export declare const StacksNetworks: readonly ["mainnet", "testnet", "devnet", "mocknet"];
export type StacksNetworkName = (typeof StacksNetworks)[number];
So if building a wallet that is accepting the MethodParams<"getAddresses"> of Connect and passing into a @stacks/transactions method such as privateKeyToAddress, there's going to be a type conflict. See the example below:

This relates to @stacks/connect and @stacks/transactions having different "network" types.
@stacks/connect methods uses
NetworkString:export type NetworkString = LiteralUnion<'mainnet' | 'testnet' | 'regtest' | 'devnet', string>;@stacks/transactions methods uses
StacksNetworkName | StacksNetwork:So if building a wallet that is accepting the
MethodParams<"getAddresses">of Connect and passing into a @stacks/transactions method such asprivateKeyToAddress, there's going to be a type conflict. See the example below: