Return amount actually unwrapped in wrapper contract

[arr00]

For contracts intergrating with the wrapper, it would make it much easier to track unwrap requests if the amount unwrapped (burntAmount) was returned on calls to unwrap.

Summary by CodeRabbit

• New Features
  • Unwrap operations now return the amount of tokens unwrapped, providing users with direct confirmation of transaction results. This enhances transparency and eliminates the need for additional queries to verify the exact quantity of tokens removed.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[netlify]

✅ Deploy Preview for confidential-tokens ready!

Name	Link
🔨 Latest commit	ac2f8b2
🔍 Latest deploy log	https://app.netlify.com/projects/confidential-tokens/deploys/6967b183474fde0008331bff
😎 Deploy Preview	https://deploy-preview-288--confidential-tokens.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

This PR modifies the unwrap() methods in ERC7984ERC20Wrapper to return the burnt amount as euint64. Both public unwrap overloads and the internal _unwrap() method signature are updated to return euint64, allowing callers to receive the burntAmount value.

Changes

Cohort / File(s)	Summary
Unwrap Return Value Addition contracts/token/ERC7984/extensions/ERC7984ERC20Wrapper.sol	Updates both public unwrap() method overloads to return euint64; internal _unwrap() now returns euint64; return statements added to propagate burntAmount through unwrap flow

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• Add warning comment about wrapper unwrap flow #276: Modifies the unwrap flow in the same file and adds warnings about using burntAmount as _unwrapRequests key, directly complementing the return value propagation changes.

Suggested reviewers

• Amxx
• james-toussaint

Poem

🐰 The unwrap now returns with pride,
Where burntAmount cannot hide,
Through method calls it flows so bright,
Encrypted tokens set alight!

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: the unwrap functions now return the amount actually unwrapped, which aligns with the modifications to method signatures and implementation.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feat/return-burnt-amount-wrapper

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}