or ideally the client-sdk can do polling client-side and offer subscriptions

Is bellow interface method ok? @tiero @bordalix
PaymentNotification(ctx context.Context, pubKey string) (<-chan Payment, error)

Check init solution in here

@sekulicd maybe include a Status key to struct Payment?

@sekulicd maybe include a Status key to struct Payment?

Can you give me more context about status you are expecting?

@sekulicd maybe include a Status key to struct Payment?

Can you give me more context about status you are expecting?

At least success or error

@sekulicd maybe include a Status key to struct Payment?

Can you give me more context about status you are expecting?

At least success or error

My understanding is that when round is finalised all offchain payments are successful, in round and payment domain i dont see any status field that could suggest that smtn failed.

@sekulicd maybe include a Status key to struct Payment?

Can you give me more context about status you are expecting?

At least success or error

My understanding is that when round is finalised all offchain payments are successful, in round and payment domain i dont see any status field that could suggest that smtn failed.

What about claiming transactions?

@sekulicd We have introduced an offline payment scheme now in cl-ark (covenant-less ark) where basically you're credited a VTXO that is with a status “pending”
https://github.com/ark-network/ark/blob/master/api-spec/protobuf/ark/v1/service.proto#L247-L248

Look live example on MutinyNet
https://asp-signet.arklabs.to/v1/vtxos/tark1qwvvzgw0ayvuqyw7754nmgu26nd4a532y0tv2m3y6xyzfhvdrvqmwq3ht683yhmmku2798tseqddxdfdf6tpygyck7nffa5jw0x2xyfpeqc2utzt