# Silent Payments: Light Client Protocol

**URL:** <https://delvingbitcoin.org/t/silent-payments-light-client-protocol/891>\
**Category:** wg-silent-payments\
**Tags:** wallet\
**Created:** [May 21, 2024, 9:15am UTC](https://delvingbitcoin.org/t/silent-payments-light-client-protocol/891 "2024-05-21T09:15:50Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![setavenger](https://delvingbitcoin.org/user_avatar/delvingbitcoin.org/setavenger/32/573_2.png) [@setavenger](https://delvingbitcoin.org/u/setavenger)\
**Post date:** [May 22, 2024, 12:19pm UTC](https://delvingbitcoin.org/t/silent-payments-light-client-protocol/891/4 "2024-05-22T12:19:45Z")

</div>

> [@cygnet3](#):
>
> Since Step 2 only calculates the `ScriptPubKey` for `k=0`, we still need to discover the `ScriptPubkey`s where `k>0` in Step 6. The only way to do that is to group all the outputs of a transaction first, and then scan them at once.

I’m not sure I’m understanding the problem you’re describing. Scanning over all outputs you should 100% be able to find all outputs (also those with `k<0`). blindbitd uses [this function](https://github.com/setavenger/go-bip352/blob/27de6d8b3f8aaf0d555e044d7d6edbf0ddb518a3/receive.go#L27) to scan for outputs.

edit: Looking a bit closer at my implementation, I think I see where the confusion comes from. blindbitd uses all taproot outputs of a block as an input for the scan function. Tweaks are not labeled with their corresponding txid. So we have to scan over all outputs of a block. Then you should always find all outputs. This means scanning over all outputs with `k>0` as well. I believe the [PR for Bitcoin core](https://github.com/bitcoin/bitcoin/pull/28241) does not store txids as well. In Oracle I have an index that stores the txid but only the tweaks are served to the client.

---

_[View the full topic](https://delvingbitcoin.org/t/silent-payments-light-client-protocol/891)._
