Skip to main content

Redemption delegate

Before implementing, learn about delegates here. Also see juice-delegate-template.


A contract can become a treasury redemption delegate by adhering to IJBRedemptionDelegate3_1_1:

interface IJBRedemptionDelegate3_1_1 is IERC165 {
function didRedeem(JBDidRedeemData3_1_1 calldata data) external payable;

When extending the redemption functionality with a delegate, the protocol will pass a JBDidRedeemData3_1_1 to the didRedeem(...) function:

struct JBDidRedeemData3_1_1 {
address holder;
uint256 projectId;
uint256 currentFundingCycleConfiguration;
uint256 projectTokenCount;
JBTokenAmount reclaimedAmount;
JBTokenAmount forwardedAmount;
address payable beneficiary;
string memo;
bytes dataSourceMetadata;
bytes redeemerMetadata;
struct JBTokenAmount {
address token;
uint256 value;
uint256 decimals;
uint256 currency;

The msg.sender to the delegate will be the payment terminal that facilitated the redemption.

In payment terminals based on the JBPayoutRedemptionPaymentTerminal3_1_1, such as JBETHPaymentTerminal3_1_1's and JBERC20PaymentTerminal3_1_1's, the redemption delegate hook gets called before the reclaimed amount is sent to the redemption beneficiary, but after all internal accounting has been updated. View the docs.

Make sure to only allow trusted contracts to access the didRedeem(...) transaction.


New delegate contracts should be deployed independently. Once deployed, its address can be returned from a data source hook. See how to build a data source for more.