Skip to content

feat(earn): require NFT permit/approve for univ3 on pancake zap widget - #3307

Merged
viet-nv merged 5 commits into
mainfrom
feat/pancake-nft-permit-approval
Aug 3, 2026
Merged

feat(earn): require NFT permit/approve for univ3 on pancake zap widget#3307
viet-nv merged 5 commits into
mainfrom
feat/pancake-nft-permit-approval

Conversation

@tienkane

@tienkane tienkane commented Aug 1, 2026

Copy link
Copy Markdown
Collaborator

Extend the NFT authorization step to univ3 (PancakeSwapV3) increase liquidity and add an off-chain permit path (usePermitNft) next to the on-chain approve, matching the main liquidity widget. Gating keys off positionId instead of the pancake-infinity-only check; the approval step shows Permit NFT + Approve NFT side by side. Permit stays dormant until the backend returns routerPermitAddress for pancake pools.

Extend the NFT authorization step to univ3 (PancakeSwapV3) increase
liquidity and add an off-chain permit path (usePermitNft) next to the
on-chain approve, matching the main liquidity widget. Gating keys off
positionId instead of the pancake-infinity-only check; the approval step
shows Permit NFT + Approve NFT side by side. Permit stays dormant until
the backend returns routerPermitAddress for pancake pools.
@kyber-ci-bot

Copy link
Copy Markdown

Auto Deploy Pull Request

ADPR instance has been created!

Information

Only apply the new NFT permit/approve requirement for univ3 positions on
ZapRouter v3. On v2 (0x0e97C887b61cCd952a53578B04763E7134429e05) keep the
legacy flow: univ3 zaps straight through and only Pancake Infinity CL
positions need an on-chain NFT approve (no permit). Gating keys off
requiresNftAuth = positionId && (!isZapV2 || isPancakeInfinityCL).
@kyber-ci-bot

Copy link
Copy Markdown

Auto Deploy Pull Request

⚠️ Warning: Application's Ingress not ready after 1m0s

Notes:

  • Please contact SRE team to support investigate this issue.

Comment thread packages/pancake-liquidity-widgets/src/components/Content/index.tsx Outdated
Use zapInfo.routerAddress as the permit spender instead of the optional
routerPermitAddress the pancake route response doesn't provide, so the
permit path activates on v3 (the router that pulls the NFT is the same
contract that verifies the permit).
@kyber-ci-bot

Copy link
Copy Markdown

Auto Deploy Pull Request

⚠️ Warning: Application's Ingress not ready after 1m0s

Notes:

  • Please contact SRE team to support investigate this issue.

@kyber-ci-bot

Copy link
Copy Markdown

Auto Deploy Pull Request

⚠️ Warning: Application's Ingress not ready after 1m0s

Notes:

  • Please contact SRE team to support investigate this issue.

@viet-nv
viet-nv merged commit a410446 into main Aug 3, 2026
3 checks passed
@viet-nv
viet-nv deleted the feat/pancake-nft-permit-approval branch August 3, 2026 10:14
@kyber-ci-bot

Copy link
Copy Markdown

Auto Deploy Pull Request

Clean up resources have been completed!

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