From 5bf2e1c2d2117221b0f05fe1d442f0bfb33f048e Mon Sep 17 00:00:00 2001 From: bt3gl <1130416+bt3gl@users.noreply.github.com> Date: Mon, 13 Jun 2022 23:59:50 -0700 Subject: [PATCH] Update apwine.md --- Top-Immunefi-Vulnerabilities/apwine.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/Top-Immunefi-Vulnerabilities/apwine.md b/Top-Immunefi-Vulnerabilities/apwine.md index faf749a..a0aee4f 100644 --- a/Top-Immunefi-Vulnerabilities/apwine.md +++ b/Top-Immunefi-Vulnerabilities/apwine.md @@ -5,3 +5,11 @@ * [Immunefi blog post](https://medium.com/immunefi/apwine-incorrect-check-of-delegations-bugfix-review-7e401a49c04f)
+ +* The APWine protocol can be used to tokenize future yields. + +* APWine operates by storing Interest Bearing Tokens (IBT) or any other yield-bearing asset in a smart contract for a specified period of time and issuing Future Yield Tokens (FYT) in exchange. + +* Bug: in the PT tokens, one condition wasn’t checked during the burn of those tokens which could lead to the theft of the yield from the protocol after the two periods, i.e. 6 months. (The condition is a `if` on an not address(0), which is called by a burn method). + +* The division of a yield-bearing asset into Principal Tokens (PTs) and Future Yield Tokens is the essential functionality of APWine. A user’s deposits to the protocol are represented by the PTs. At the start of each period, the APWine generates FYT from PTs in a 1:1 ratio.