# Beanstalk Obligations

This document has been uploaded to Arweave \[TBA]

***

Pinto is a fork of [Beanstalk](https://bean.money). As part of honoring the obligations created by the April 2022 Beanstalk governance exploit, Pinto allocates a portion of future mints to repay former Beanstalk participants. Repayment is based on a snapshot of Beanstalk state at Ethereum L1 block [21223086](https://etherscan.io/block/21223086) / Arbitrum block [276160746](https://arbiscan.io/block/276160746) (November 19, 2024), corresponding to the Pinto Diamond deployment on Base at block [22622854](https://basescan.org/block/22622854).

### Eligibility

Farmers who held any of the following assets on Beanstalk at the time of the snapshot are eligible:

* [Unripe Beans](https://docs.bean.money/almanac/farm/barn#unripe-assets) or [Unripe LP](https://docs.bean.money/almanac/farm/barn#unripe-assets) (Silo deposits)
* [Fertilizer](https://docs.bean.money/almanac/farm/barn#fertilizer) (Barn Raise participants)
* [Pods](https://docs.bean.money/almanac/farm/field) (Field lenders)

Pinto does not allocate any mints for Beans or liquid LP tokens held on Beanstalk at the time of the snapshot.

To check specific balances, connect the wallet that held assets on Beanstalk to the [Beanstalk Obligations](https://pinto.money/beanstalk) page on the Pinto interface.

### Asset Types

After the Pinto supply exceeds 1 billion, [3% of mints](https://docs.pinto.money/responding-to-state/minting#shipping-routes) are allocated to repaying old Beanstalk debt holders across three asset types:

| Asset                 | Description                                                                                      | Action                   |
| --------------------- | ------------------------------------------------------------------------------------------------ | ------------------------ |
| Beanstalk Silo Tokens | ERC-20 tokens representing recapitalized Unripe asset value (also referred to as Ripening Pinto) | Claim earned Pinto       |
| Beanstalk Fertilizer  | ERC-1155 tokens mirroring the Beanstalk Fertilizer system                                        | Rinse fertilized Pinto   |
| Beanstalk Pods        | Pods in a separate Beanstalk Pod Line                                                            | Harvest Harvestable Pods |

### Distribution

Beanstalk Silo Token holders, active Beanstalk Fertilizer holders, and Beanstalk Pod holders each receive 1/3 of the Pinto mints allocated to repaying old Beanstalk holders (1% of mints each).

If there is no active Beanstalk Fertilizer, Beanstalk Silo Token holders and Beanstalk Pod holders each receive 1/2 of Pinto mints allocated to repaying old Beanstalk holders (1.5% of mints each).

If there are neither active Beanstalk Fertilizer nor Beanstalk Silo Tokens remaining, Beanstalk Pod holders receive 100% of the Pinto mints allocated to repaying old Beanstalk holders (3% of mints).

Once all outstanding Beanstalk Fertilizer, Beanstalk Silo Tokens, and Beanstalk Pods are fully repaid, the 3% of mints previously allocated to honoring Beanstalk debt is distributed to Pinto participants under its normal model: 50% to [Pods](https://docs.pinto.money/resources/glossary#pods) and 50% to [Stalkholders](https://docs.pinto.money/resources/glossary#stalkholders).

### Supply Threshold

Before the Pinto supply reaches 1 billion, 3% of mints are directed to the [Pinto development budget contract](https://docs.pinto.money/resources/contracts#misc). After the supply exceeds 1 billion Pinto, the 3% allocation transitions from the development budget to Beanstalk debt repayment.

Repayment depends on continued protocol growth and minting. See [Disclosures](https://docs.pinto.money/appendix/disclosures) for risk factors.

### Contract Accounts

Some Beanstalk holders were contract accounts (such as multisig wallets or DeFi protocols) that may not exist at the same address on Base. Assets belonging to these accounts are held in a Contract Payback Distributor that supports multiple claiming methods.

### Contracts

Beanstalk Silo Token and Fertilizer repayments are managed by dedicated contracts. Pod repayments are handled directly by the Pinto protocol through a separate repayment Field (Field ID 1).

All payback contracts use the [TransparentUpgradeableProxy](https://docs.openzeppelin.com/contracts/5.x/api/proxy#TransparentUpgradeableProxy) pattern. Users interact with the Proxy address; the Implementation address contains the contract logic. A shared Proxy Admin controls upgrade authorization.

| Contract                     | Type           | Base Address                                                                                                          |
| ---------------------------- | -------------- | --------------------------------------------------------------------------------------------------------------------- |
| Beanstalk Silo Payback       | Proxy          | [0x525C94754C51946a7a3B72580Ce0DF36922E1E64](https://basescan.org/address/0x525C94754C51946a7a3B72580Ce0DF36922E1E64) |
| Beanstalk Silo Payback       | Implementation | [0xDbb10C0cE795FFd3A4003CF0EcC849b25a788EB1](https://basescan.org/address/0xDbb10C0cE795FFd3A4003CF0EcC849b25a788EB1) |
| Beanstalk Barn Payback       | Proxy          | [0x68bDbb0402a3Ca89C7C4af8e41C021635102d158](https://basescan.org/address/0x68bDbb0402a3Ca89C7C4af8e41C021635102d158) |
| Beanstalk Barn Payback       | Implementation | [0x5bb2b891496F9f4db1467755eDc240329EA08E2C](https://basescan.org/address/0x5bb2b891496F9f4db1467755eDc240329EA08E2C) |
| Contract Payback Distributor | Proxy          | [0xbA941Af3292c49b585f4EC5C8164c1dfc893EEdC](https://basescan.org/address/0xbA941Af3292c49b585f4EC5C8164c1dfc893EEdC) |
| Contract Payback Distributor | Implementation | [0xED3Ead9D8b6E57f666E60ccf833f3ed1Be2Dd4c0](https://basescan.org/address/0xED3Ead9D8b6E57f666E60ccf833f3ed1Be2Dd4c0) |
| Proxy Admin                  | —              | [0xE5A707d49968937C860762fB256CE9dC7B1370F0](https://basescan.org/address/0xE5A707d49968937C860762fB256CE9dC7B1370F0) |