Skip to content

Update transferId assignment logic in BridgeTransferLib#314

Open
0xriptide wants to merge 1 commit intoceler-network:mainfrom
0xriptide:patch-3
Open

Update transferId assignment logic in BridgeTransferLib#314
0xriptide wants to merge 1 commit intoceler-network:mainfrom
0xriptide:patch-3

Conversation

@0xriptide
Copy link
Copy Markdown

Refactor withdrawId computation for consistency in transferId assignment by checking the correct wdId instead of request.refId

Refactor withdrawId computation for consistency in transferId assignment by checking the correct wdId instead of request.refId
@alireza237237
Copy link
Copy Markdown

Prompt

@alexchen-security
Copy link
Copy Markdown

Great catch — this is exactly the issue I reported in #319. The records(request.refId) check was effectively dead code since the vault indexes by wdId, not refId.

Your fix looks correct. One thing worth verifying: the same pattern exists in receivePegV2Mint() around line 411 with IPeggedTokenBridgeV2(_bridgeAddr).records(request.refId) — might want to apply the same fix there for consistency.

Happy to review if that helps move this forward.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants