NWC: use nip44 encryption — fixes missing payment notifications with nip44-only wallets - #148

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-dotnet@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Null should not be used for type parameter 'connectionString' of type 'string'. Use a non-null value, or convert the parameter to a nullable type. (https://xunit.net/xunit.analyzers/rules/xUnit1012)

'CreateInvoiceParams.DescriptionHash.set' is obsolete: 'Set the Description and turn DescriptionHashOnly to true instead'

Possible null reference argument for parameter 'str' in 'BOLT11PaymentRequest BOLT11PaymentRequest.Parse(string str, Network network)'.

Possible null reference argument for parameter 'value' in 'string? Extensions.Value<string>(IEnumerable<JToken> value)'.

Non-nullable property 'ApiKey' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.

Dereference of a possibly null reference.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

The pattern is redundant.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.