Architecture
Last updated
Last updated
The V1 Architecture consists of a Bond and an OpenZeppelin clone factory, BondFactory, to create new instances of the Bond contract.
The two entities, Bond and BondFactory, make up the protocol.
An Issuer (EOA) first creates a Bond comprised of many bond shares via the BondFactory. The Issuer can then distribute those bond shares to BondHolder(s) (EOA(s)).
A typical lifecycle starts from issuance and ends when all bond shares have either been redeemed / converted by the bond holders, or burnt by the issuer.
The Bond Factory contract is deployed by the Arbor Admin (multi-sig). The contract assigns the admin role to the deployer and the proxy contract is initialized with the token implementation (Bond contract).
Arbor Finance evaluates Issuer's credit worthiness
Arbor Finance recommends parameters for the issuance
Amount of ERC20 token backing each bond share or
This is known as the collateral token
Amount of collateral each bond share would convert into
Total issuance length
This is known as the maturity date
Total issuance size
This is known as the total supply
The ERC20 token the Bond is denominated
This is known as the payment token
Arbor Finance adds Issuer to the Issuer Allow List
Arbor Finance adds both the Collateral & Payment Tokens to the token allow list
After the issuance has been approved, the issuer will be on the allowed issuer list and their intended collateral token and payment token will be added to the allowed token list. The Bonds are created (minted) at the same time that the collateral is deposited. After a Bond is created, the issuer can sell the Bond through the Arbor Finance App (we use Gnosis' Batch Auction).
These are sold as Zero Coupon Bonds. Another party will purchase these bond shares at a discount by paying with the Payment Token. The purchasers are known as bond holders. At maturity, the bond holders can redeem their bond shares at 1 to 1 for Payment Tokens.
Issuers and Bond Holders can both interact with the bond in a few ways. For a simpler view, look at the state transition diagram. Since the Bond is an ERC20 token, the bond shares may be transferred at any time by any users.
In addition to the actions taken by bond holders, Issuers have the ability to pay, withdrawExcessCollateral, withdrawExcessPayment and sweep. These can be called at any time to affect the Bond.
If there is an excess of collateral in the contract at any time, the Issuer may call withdrawExcessCollateral. This will transfer collateral out of the Bond contract. There are three ways in which the Bond can have an excess amount of collateral in the contract.
The total number of bond shares decrease.
Issuers may burn their excess bonds.
Bond Holders may convert their bonds before maturity.
Bond Holders may redeem their bonds.
The amount of Payment Tokens in the contract covers a portion of the bond shares.
Issuers may pay a portion of the Payment Token to the contract.
(For a convertible bond) The Bond has reached maturity and no longer requires collateral for convertibility.
After maturity, the locked collateral required to potentially convert all bonds is lifted.
There are ways in which the payment requirement can decrease. At any time, the Issuer may also withdrawExcessPayment to reclaim any excess Payment Token in the contract.
The total number of bond shares decrease.
Issuers may burn their excess bonds.
Bond Holders may convert their bonds before maturity.
The Issuer has a utility function, sweep available to retrieve any ERC20 token sent to the Bond contract by mistake.
The Bond Holders can interact with the Bond contract in different ways before and after maturity is reached.
(For a convertible bond) The bond holders may convert their bond shares into the underlying collateral at a pre-determined ratio.
The bond holders may redeem for Payment Token if the bond is fully paid.
The bond holders may redeem the bond.
If the bond is fully paid, redemption will be for Payment Token
If the bond has no payment, redemption will be for Collateral Token
If the bond is partially paid, redemption will be for a pro-rata amount of Payment Token & Collateral Token