By depositing into fRenPool, you will earn an immediate return on your Ren. You will also help us secure RenVM by letting us run Darknodes. fRenPool bonds Ren for darknodes and provides you with RenVM fees without having to use any CLI tools or own 100000 Ren. You can freely transfer your bond and even use it in other projects. Potentially allowing you to take a loan against it.

You will earn fees immediately after depositing. However, the withdrawal fee is designed to cost around 1 epoch worth of Ren. You should, therefore, expect to use the first epoch (~4 weeks) to payoff the withdrawal fee.

Short answer: Ren.
Long answer: Darknodes earns fees in the native currency that is transferred across RenVM. For many smaller holders claiming the fees can be a gas-intensive operation. To provide the best service possible, we convert the assets into Ren for you. This is an efficient way for you to earn the fees and auto-compound your income. It also lowers the withdrawal pressure in the first week after an epoch as the new Ren provides a buffer for users leaving the pool.

1 fRen represents 1 Ren when the pool was launched. Over time, 1 fRen will accumulate in value becoming more valuable than Ren. If you only got 500 fRen for your 1000 Ren, don't worry. You will get your 1000 Ren - withdrawal fees + fees back once you withdraw.

The smart contract sets no minimum deposit, but be careful that the gas cost does not become a large percentage of your deposit. We have no control over the gas price and it is your responsibility to include it in your profitability calculations.

An epoch is an internal time length used interally within RenVM. One epoch is currently about 4 weeks (28 days) long.

A darknode is a node participating in running RenVM. To read more about darknodes, vist renproject.io

RenVM is a virtual machine capable of managing secrets. It can sign a Bitcoin transaction without revealing the private key. Its capability of hiding secrets makes applications which would otherwise be impossible possible. An example application of the technology is a dark pool, which is an order book where nobody knows the orders inside.

fRenPool has not been formally audited, but the underlying code has been through internal audits. Outside dependencies are minimal, relying on the Ren registry contract for epochs timing and registering darknodes. The smart contracts are written in Vyper, allowing anyone with knowledge of Python to read the smart contract. Because of the upgradeable nature of the smart contract, the owners can extract all Ren held within. That is why the owner has been set to a 3/5 multi-signature consisting of 2 from Polymer, 2 from Ren, and 1 independent person. No one person or team can execute an admin exploit against the contract.

The queue is a way to get priority withdrawal at the cost of freedom. Your staked Ren will be locked until the next epoch and you can be forced to withdraw.
There is currently no way to queue using the UI and starting a queue may confuse the UI until you withdraw.

To increase your earnings the pool operators bond as much Ren as possible. This can result in the pool running out of Ren for withdrawals. Fear not: you can queue for the upcoming epoch and potentially withdraw with the incoming Ren from fees. If a lot of users have queued, a darknode will be deregistered to provide Ren for withdrawing.

You will get fees for the full duration fRen remains in your wallet. From the moment when Ren is deposited and your fRen was minted to the moment fRen is burned and your Ren is released.

If you have queued, you indicate you want to withdraw and acknowledge other people can withdraw for you. They can now exchange your fRen for Ren. This does not cost you anything extra and even saves gas for you.

If you have queued, you cannot move your Ren. They are frozen. Likewise, you cannot remove the allowance from the PoolLogic contract. You cannot cancel your queue in the epoch after you queued, but by withdrawing 0 in the same epoch you queued in or the second epoch after your queue you cancel your queue.

A queue lasts exactly 2 epochs. The next epoch and the epoch after the next. You can queue again in the epoch after the next, disallowing a queued withdrawal in that epoch but queueing again.