# pDF (Tokenized veDF)

### **What is pDF?**

pPF is the tokenized version of veDF (time-locked DF participating in dForce Lock-up Staking). When you stake DF through Loopfi, you will receive pDF at 1:1 ratio. Each pDF represents 1 DF participating in dForce Lock-up Staking, at maximum lock-up term (4-year)

* pDF holders can receive max boost on DF staking rewards and dForce platform fees without sacrificing liquidity (you can still sell pDF for DF in the liquidity pool).
* pDF can be exchange for DF or other tokens on DEXes to exit from dForce Lock-up Staking.
* pDF stakers will also be rewarded with LPF token, on top of DF staking rewards.
* pDF staking mining and liquidity mining is currently available on Arbitrum only. 

 

### **veDF Staking Rewards**

For DF stakers who stake DF via Loopfi from Layer2 (only Arbitrum is supported for now) or other blockchains foreign to Ethereum, it will automatically max-out the lock-up period to 4-year, so it could benefit from both maximum staking rewards as well as lower gas fee on other chains.

#### <mark style="color:blue;">**On Ethereum (native chain for veDF staking)**</mark>

*For DF tokens bridged over from Arbitrum:* &#x20;

* 0.1% of DF tokens collected from Arbitrum stakers will be rewarded as 'Gas Compensation Incentive' for the trigger of deposit of DF tokens into dForce Staking.
* DF tokens bridged over from Arbitrum will need to wait approximately 7 days before they are deposited into dForce Staking to receive DF staking rewards. &#x20;

*Upon withdrawal of DF rewards from dForce:*&#x20;

* 85% of DF rewards received will be bridged to Arbitrum for distribution. Out of which, 99% (84.15%) to users who stake through Loopfi; 1% (or 0.85%) will be rewarded as 'Gas Compensation Incentive' for the trigger of bridging DF rewards from Ethereum to Arbitrum.&#x20;
* 15% of DF rewards received will be collected by Loopfi Treasury.

<mark style="color:blue;">**On blockchains foreign to Ethereum (non-native chains, only Arbitrum is supported for now):**</mark>

*Upon deposit of DF tokens to dForce through Loopfi on Arbitrum:*

* 99.9% of DF tokens received will be deposited into dForce Staking on Ethereum.
* 0.1% of DF tokens received will be rewarded as 'Gas Compensation Incentive' for the trigger of bridging DF tokens from Arbitrum to Ethereum.
* For cost efficiency consideration, a minimum of 500,000 DF tokens deposited on Arbitrum need to be satisfied before the initiation of any Arbitrum-to-Ethereum bridging transaction.

*For all DF rewards bridged over from Ethereum:*&#x20;

* The trigger of DF rewards distribution to all stakers on Arbitrum will be rewarded with a 'Gas Compensation Incentive', equaling to 0.1% of the to-be-distributed DF rewards.
* There is a discrepancy between the APY displayed on dForce and the actual APY received by Loopfi stakers in consequence of the cross-chain setup.

### **LPF Staking and Liquidity Mining Rewards**

#### **Stake pDF to receive LPF token (pDF staked through Loopfi on Arbitrum will be rewarded with LPF token)**

* 136,986 LPF tokens per day for Year-1
* 82,192 LPF tokens per day for Year-2&#x20;
* 54,795 LPF tokens per day for Year-3

**Provide liquidity to receive LPF token (currently, the following pairs will be supported)**

* LPF/USX (24,657 LPF/day)
* pDF/DF (16,638 LPF/day)

#### **Stake LPF to receive LPF (coming soon)**

* LPF will introduce its veToken staking model in due course, allowing stakers to earn LPF staking rewards.
* LPF staked will receive rewards from anchor partners in the Treasury in the form of their native token, i.e., dForce will receive DF token.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.loopfi.io/how-to-guides/loopfi-for-dforce/pdf-tokenized-vedf.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.