𝗪𝗜𝗡 𝗰𝗵𝗮𝗻𝗴𝗲𝘀 𝗵𝗮𝗻𝗱𝘀 𝗳𝗼𝘂𝗿 𝘁𝗶𝗺𝗲𝘀 𝗼𝗻 𝗶𝘁𝘀 𝘄𝗮𝘆 𝗳𝗿𝗼𝗺 𝗮𝗻 𝗮𝗽𝗽 𝘁𝗼 𝘁𝗵𝗲 𝗯𝗹𝗮𝗰𝗸 𝗵𝗼𝗹𝗲. 𝗘𝗮𝗰𝗵 𝗵𝗮𝗻𝗱𝗼𝗳𝗳 𝗵𝗮𝘀 𝗮 𝗰𝗹𝗲𝗮𝗿 𝗽𝘂𝗿𝗽𝗼𝘀𝗲. When I explain WINkLink's token loop, I find it helps to follow the token itself rather than the money in the abstract. So let me track WIN through its four roles. 𝗥𝗼𝗹𝗲 𝗼𝗻𝗲: 𝗽𝗮𝘆𝗺𝗲𝗻𝘁. A TRON app pays WIN for an oracle service, whether that's a price feed, a VRF request, an AnyAPI call or an Automation job. 𝗥𝗼𝗹𝗲 𝘁𝘄𝗼: 𝗿𝗲𝘃𝗲𝗻𝘂𝗲. That WIN is counted as oracle service revenue for the quarter. 𝗥𝗼𝗹𝗲 𝘁𝗵𝗿𝗲𝗲: 𝗯𝘂𝘆𝗯𝗮𝗰𝗸. Every unit of that revenue goes toward repurchasing WIN from the market. 𝗥𝗼𝗹𝗲 𝗳𝗼𝘂𝗿: 𝗯𝘂𝗿𝗻. The repurchased WIN is sent to the TRON black hole address, where no key can ever move it. Here's what each role tells a careful observer: ➜ 𝗣𝗮𝘆𝗺𝗲𝗻𝘁 shows the services are being used ➜ 𝗥𝗲𝘃𝗲𝗻𝘂𝗲 shows what that usage earned ➜ 𝗕𝘂𝘆𝗯𝗮𝗰𝗸 shows the rule being followed ➜ 𝗕𝘂𝗿𝗻 shows the result, permanently and publicly Round 1 is the first full cycle on record: 67,357,364,510 WIN burned, about 6.74% of the initial supply, worth $3,590,256.63 at execution. I describe it as a record because every round depends on the revenue earned and the market price when the buyback runs. The loop itself is the constant. Use leads to payment, payment to revenue, revenue to buyback and buyback to burn. You can follow the end of the loop on TRONSCAN: https://t.co/Vd7NCRjKra 𝗙𝗼𝘂𝗿 𝗿𝗼𝗹𝗲𝘀, 𝗼𝗻𝗲 𝗱𝗶𝗿𝗲𝗰𝘁𝗶𝗼𝗻. 𝗙𝗿𝗼𝗺 𝗮𝗻 𝗮𝗽𝗽'𝘀 𝗶𝗻𝘃𝗼𝗶𝗰𝗲 𝘁𝗼 𝘁𝗵𝗲 𝗯𝗹𝗮𝗰𝗸 𝗵𝗼𝗹𝗲. @justinsuntron @WinkLink_Oracle #TronEcoStar