implement message reporting tokens #1906

jlucaso1 · 2025-10-12T21:27:17Z

to match whatsmeow implementation of this elements

whiskeysockets-bot · 2025-10-12T21:27:26Z

Thanks for opening this pull request and contributing to the project!

The next step is for the maintainers to review your changes. If everything looks good, it will be approved and merged into the main branch.

In the meantime, anyone in the community is encouraged to test this pull request and provide feedback.

✅ How to confirm it works

If you’ve tested this PR, please comment below with:

Tested and working ✅

This helps us speed up the review and merge process.

📦 To test this PR locally:

# NPM
npm install @whiskeysockets/baileys@WhiskeySockets/Baileys#reporting-tctoken-elements

# Yarn (v2+)
yarn add @whiskeysockets/baileys@WhiskeySockets/Baileys#reporting-tctoken-elements

# PNPM
pnpm add @whiskeysockets/baileys@WhiskeySockets/Baileys#reporting-tctoken-elements

If you encounter any issues or have feedback, feel free to comment as well.

src/Socket/messages-recv.ts

src/Utils/reporting-utils.ts

src/Socket/chats.ts

src/Types/Auth.ts

purpshell · 2025-10-13T09:18:12Z

src/Utils/history.ts


+				if (chat.tcToken) {
+					privacyTokens.push({
+						jid: jidNormalizedUser(chat.id!),


we need to verify LID/PN discrepancy

How is the best way to handle that? 🤔

we can handle same as #1912

src/Utils/messages.ts

src/Socket/messages-send.ts

src/Types/Events.ts

Salientekill · 2025-10-13T19:53:12Z

I got banned for adding the bot to a group with 514 members. If this solves it, it will be of great help. I look forward to this beautiful work.

…history sync

…figuration

…to reporting-tctoken-elements

Santosl2 · 2025-10-26T20:18:34Z

up

- Add reporting token and privacy token handling - Implement tcToken elements for message reporting - Add support for reportingTokens in messages - Update message processing for privacy tokens 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>

jlucaso1 · 2025-11-17T19:12:54Z

Maybe we can get some inspirations here: canove/whaileys#51

…ns and privacy token handling This PR adds support for message reporting tokens and privacy token handling. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>

…ets#1969 to latest Baileys Applied PRs: - WhiskeySockets#2067: libsignal wasm - WhiskeySockets#2057: emit setting events - WhiskeySockets#1969: improve retry logic Note: PRs WhiskeySockets#1991, WhiskeySockets#1981, WhiskeySockets#1906, WhiskeySockets#1892 have conflicts with latest Baileys version and were skipped. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>

…ns and privacy token handling Implements comprehensive privacy token and message reporting token handling to match whatsmeow implementation. New features: - Message reporting token generation for eligible messages - Privacy token storage and retrieval (in-memory by default) - Trusted contact token (tcToken) support for profile pictures and messages - LID (Local Identity) mapping support for privacy tokens Files changed: - NEW: src/Utils/reporting-utils.ts (262 lines) - Modified: 11 files across Socket/, Types/, and Utils/ directories Key improvements: - Automatic message secret generation for reporting-eligible messages - Privacy token handling in message send/receive - Enhanced history sync with privacy token extraction - Profile picture requests now support tcToken parameter All conflicts resolved and build successful. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>

… privacy token handling

purpshell · 2025-12-14T23:15:18Z

Any updates @jlucaso1

…lements

jlucaso1 · 2025-12-16T19:00:54Z

Removed tctoken in favor of #2080
Now only reporting token in this pr

vinikjkkj · 2025-12-16T19:45:26Z

is the changes in src/Utils/process-message.ts related to this PR?

jlucaso1 · 2025-12-16T19:57:50Z

@vinikjkkj thank you. I didnt noticed that. Reverting.

Santosl2 · 2025-12-16T20:14:19Z

Tested and working ✅

canove · 2025-12-19T21:11:58Z

@jlucaso1 left a few coments.

I asked Claude code to check and optimize reporting-utils, and, according to him, there was an improvement in performance.

The changes it made seem to make sense, mainly because it avoids the find inside the loop = O(n*m). I implemented the version with these adjustments in Whaileys (WIP), if you want to take a look.

https://github.com/canove/whaileys/pull/64/changes#diff-321487214369869e332b4749d527c6d9dadfe629700e8d1fdd9754c4354e9c39

vinikjkkj · 2025-12-20T03:55:57Z

instead of creating a "mini-protobuf" implementation (decode/encode varint), we cannot just use existent proto.ReportingTokenInfo?

jlucaso1 · 2025-12-20T11:20:03Z

instead of creating a "mini-protobuf" implementation (decode/encode varint), we cannot just use existent proto.ReportingTokenInfo?

I think is not simple like that. Check what waweb does (WABinary/WAWebReportingTokenProtobufUtils)

…ogic

jlucaso1 · 2025-12-20T11:34:04Z

@canove applied your suggestion, thank you!

extra: added some unit tests to evict regressions

canove · 2025-12-19T20:50:05Z

src/Socket/messages-send.ts


+			if (!isNewsletter) {
+				if (
+					reportingMessage &&


Here, you could put everything in a single if statement to avoid nesting; just add !isNewsletter to the inner if statement.

canove · 2025-12-19T21:00:14Z

src/Socket/messages-send.ts

+					reportingMessage &&
+					shouldIncludeReportingToken(reportingMessage) &&
+					reportingMessage.messageContextInfo?.messageSecret &&
+					msgId


I don't think we need this msgId here; it always exists.

One question: in which cases should we NOT send the reporting token?

Seems like we are not sending on retryResponses neither newsletter. Is that right?

I don't think we need this msgId here; it always exists.

Nice catch, removed.

Yes, that's correct. Based on WhatsApp Web JS (isMsgTypeReportingTokenCompatible):

Should NOT send reporting token:

reactionMessage / encReactionMessage

pollUpdateMessage

encEventResponseMessage

Newsletters (different path, not E2E encrypted) (maybe we need to handle properly in the future, but need to check this logic deeper)

Retries (reportingMessage is only set when !isRetryResend)

Should send: All other regular content messages (text, image, video, audio, document, sticker, etc.)

In this case, we can put !isRetryResend inside de if statement to make it more explicit.

Also, remove the reportingMessage &&, since checking the reportingMessage?.messageContextInfo?.messageSecret does the trick.

…e sending

canove

Just left a comment about adding the !isRetryResend on the if statement to make it more comprehensible. but not blocking.

lgtm

…Token function type safety

github-actions · 2026-01-04T02:17:36Z

This PR is stale because it has been open for 14 days with no activity. Remove the stale label or comment or this will be closed in 14 days

jlucaso1 force-pushed the reporting-tctoken-elements branch 3 times, most recently from 34ac312 to 02f329b Compare October 13, 2025 02:39

jlucaso1 changed the title ~~WIP: implement message reporting tokens and privacy token handling~~ implement message reporting tokens and privacy token handling Oct 13, 2025

jlucaso1 force-pushed the reporting-tctoken-elements branch from 96f2b48 to a2330d2 Compare October 13, 2025 03:39

purpshell reviewed Oct 13, 2025

View reviewed changes

jlucaso1 force-pushed the reporting-tctoken-elements branch from 9156372 to ae1c039 Compare October 13, 2025 14:33

jlucaso1 force-pushed the reporting-tctoken-elements branch from ae1c039 to 8dd1315 Compare October 13, 2025 22:00

jlucaso1 marked this pull request as ready for review October 13, 2025 22:02

jlucaso1 added 5 commits October 15, 2025 14:23

feat: implement message reporting tokens and privacy token handling

330c3d9

feat: add support for privacy tokens in profile picture requests and …

112ea4f

…history sync

chore: pr feedback purpshell

3c58ddc

fix: improve privacy token handling and error messaging in socket con…

3ea2e21

…figuration

feat: enhance privacy token handling with improved sender mapping

79f3938

jlucaso1 force-pushed the reporting-tctoken-elements branch from 51c7201 to 79f3938 Compare October 15, 2025 17:23

jlucaso1 added 2 commits October 19, 2025 13:29

Merge branch 'master' of https://github.com/WhiskeySockets/Baileys in…

16239b6

…to reporting-tctoken-elements

Merge branch 'master' of https://github.com/WhiskeySockets/Baileys in…

0b3a720

…to reporting-tctoken-elements

jlucaso1 mentioned this pull request Nov 17, 2025

fix: cannot send message on new Whatsapp Business limited accounts #2080

Merged

jlucaso1 marked this pull request as draft November 18, 2025 00:13

purpshell force-pushed the master branch from df95836 to 247c717 Compare November 19, 2025 14:35

purpshell force-pushed the master branch from bd1c658 to f46e8b1 Compare November 21, 2025 15:35

Salientekill pushed a commit to Salientekill/Baileys that referenced this pull request Nov 24, 2025

feat: apply PR WhiskeySockets#1906 - add message reporting tokens and…

ca32251

… privacy token handling

github-actions bot removed the Stale label Dec 13, 2025

jlucaso1 added 2 commits December 16, 2025 15:41

chore: removing tc token in favor of #2080

45732b6

Merge remote-tracking branch 'origin/master' into reporting-tctoken-e…

4c00530

…lements

jlucaso1 changed the title ~~implement message reporting tokens and privacy token handling~~ implement message reporting tokens Dec 16, 2025

jlucaso1 requested a review from purpshell December 16, 2025 19:00

jlucaso1 marked this pull request as ready for review December 16, 2025 19:00

jlucaso1 requested review from canove and vinikjkkj December 16, 2025 19:01

chore: revert some unecessary changes

427106f

canove mentioned this pull request Dec 19, 2025

feat: send reporting tokens canove/whaileys#64

Merged

jlucaso1 added 2 commits December 20, 2025 08:33

feat(reporting): enhance reporting token extraction and compilation l…

5b0842b

…ogic

feat(reporting): add unit tests for reporting token utilities

9b8edd1

canove requested changes Dec 20, 2025

View reviewed changes

fix(reporting): streamline reporting token attachment logic in messag…

0cecdb4

…e sending

jlucaso1 requested a review from canove December 20, 2025 13:10

canove approved these changes Dec 20, 2025

View reviewed changes

jlucaso1 added 2 commits December 20, 2025 10:22

fix: adjust reporting token inclusion logic to prevent retries

8417a17

chore: add return type to shouldIncludeReportingToken and improve get…

a0784a3

…Token function type safety

github-actions bot added the Stale label Jan 4, 2026

purpshell merged commit c9c3481 into master Jan 8, 2026
4 checks passed

Uh oh!

implement message reporting tokens #1906

implement message reporting tokens #1906

Conversation

jlucaso1 commented Oct 12, 2025

Uh oh!

whiskeysockets-bot commented Oct 12, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ How to confirm it works

📦 To test this PR locally:

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

purpshell Oct 13, 2025

Choose a reason for hiding this comment

Uh oh!

jlucaso1 Oct 13, 2025

Choose a reason for hiding this comment

Uh oh!

jlucaso1 Oct 13, 2025

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Salientekill commented Oct 13, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Santosl2 commented Oct 26, 2025

Uh oh!

jlucaso1 commented Nov 17, 2025

Uh oh!

purpshell commented Dec 14, 2025

Uh oh!

jlucaso1 commented Dec 16, 2025

Uh oh!

vinikjkkj commented Dec 16, 2025

Uh oh!

jlucaso1 commented Dec 16, 2025

Uh oh!

Santosl2 commented Dec 16, 2025

Uh oh!

canove commented Dec 19, 2025

Uh oh!

vinikjkkj commented Dec 20, 2025

Uh oh!

jlucaso1 commented Dec 20, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

jlucaso1 commented Dec 20, 2025

Uh oh!

canove Dec 19, 2025

Choose a reason for hiding this comment

Uh oh!

canove Dec 19, 2025

Choose a reason for hiding this comment

Uh oh!

jlucaso1 Dec 20, 2025

Choose a reason for hiding this comment

Uh oh!

canove Dec 20, 2025

Choose a reason for hiding this comment

Uh oh!

canove left a comment

Choose a reason for hiding this comment

Uh oh!

github-actions bot commented Jan 4, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

8 participants

whiskeysockets-bot commented Oct 12, 2025 •

edited

Loading

Salientekill commented Oct 13, 2025 •

edited

Loading

jlucaso1 commented Dec 20, 2025 •

edited

Loading