Skip to content

feat: set HPP fast withdrawal time to 24 hours#2693

Open
findmytrueself wants to merge 1 commit into
OffchainLabs:masterfrom
hpp-io:master
Open

feat: set HPP fast withdrawal time to 24 hours#2693
findmytrueself wants to merge 1 commit into
OffchainLabs:masterfrom
hpp-io:master

Conversation

@findmytrueself

Copy link
Copy Markdown

Configure fastWithdrawalTime (86400000 ms) for HPP Mainnet and HPP Sepolia to match the announced fast withdrawal window.

Summary

HPP announced that Arbitrum fast withdrawal is enabled with a 7 day → 24 hour user-facing confirmation window. The bridge UI uses bridgeUiConfig.fastWithdrawalTime (milliseconds) in getBridgeUiConfigForChain / getConfirmationTime to treat fast withdrawal as active and to drive withdrawal ETA strings, approximate duration, and estimated completion (useTransferDuration, getWithdrawalConfirmationDate). Without this field, those flows fall back to the standard challenge-period estimate.

This change sets fastWithdrawalTime to 86400000 (24 hours in ms) for HPP Mainnet and HPP Sepolia in packages/arb-token-bridge-ui/src/util/orbitChainsData.json, aligned with the public announcement.

Steps to test

  1. Run the UI locally (e.g. from packages/arb-token-bridge-ui per repo README).
  2. Select HPP Mainnet (or HPP Sepolia) as the child/source chain for a withdrawal toward Ethereum (or Sepolia).
  3. Confirm the transfer panel / withdrawal flow shows a ~24 hour (or “1 day”) style confirmation estimate instead of the long default challenge period.
  4. Optionally start a test withdrawal and confirm the estimated time remaining / completion logic uses the fast-withdrawal path (no need to wait for on-chain finality; UI copy and timers are enough to verify).

Configure fastWithdrawalTime (86400000 ms) for HPP Mainnet and HPP
Sepolia to match the announced fast withdrawal window.

Co-authored-by: Cursor <cursoragent@cursor.com>
@cla-bot

cla-bot Bot commented May 13, 2026

Copy link
Copy Markdown

We require contributors to sign our Contributor License Agreement. In order for us to review and merge your code, please sign one of the linked documents below to get yourself added. If you're an independent Individual please sign this form: https://na3.docusign.net/Member/PowerFormSigning.aspx?PowerFormId=1353a816-a9c1-47ba-847e-ec79f0f23d31&env=na3&acct=6e152afc-6284-44af-a4c1-d8ef291db402&v=2. If you're with a company (corporate) please sign this form: https://na3.docusign.net/Member/PowerFormSigning.aspx?PowerFormId=2b5fe8ba-51d4-4980-b4ee-605d66e675d4&env=na3&acct=6e152afc-6284-44af-a4c1-d8ef291db402&v=2. To agree to the CLA license, please fill out one of the attached forms.

@findmytrueself

Copy link
Copy Markdown
Author

Hi, I'm unable to complete the CLA DocuSign flow. When I open the PowerForm link from the bot message / contributing docs, DocuSign shows:

"Unable to load PowerForm signing process. Error: Email or name has not been completed."

I've tried a normal browser window and incognito, with extensions disabled. Could someone help with a working signing link or manual CLA onboarding? Thanks.

@CLAassistant

CLAassistant commented May 13, 2026

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

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.

2 participants