From ec325bdbb2af6d7ccacff772ef242a9d7d3becb1 Mon Sep 17 00:00:00 2001 From: k3dz0r Date: Tue, 21 Oct 2025 08:26:43 -0300 Subject: [PATCH] Added method getAssetPrice --- docs/hackathon/rules.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/docs/hackathon/rules.md b/docs/hackathon/rules.md index c0fd3ef1..53a72db5 100644 --- a/docs/hackathon/rules.md +++ b/docs/hackathon/rules.md @@ -13,7 +13,7 @@ One way to find eligible dApps is to use the [Chainlink Ecosystem search tool](h The original dApp must use Chainlink Data Feeds in its on-chain logic. See the [list of supported data feeds](/hackathon/data-feeds). -The interface methods (`latestAnswer`, `getAnswer`, `latestRound`, `getRoundData`, `latestRoundData`) must be called from a smart contract (.sol file). If they are called from the frontend (.ts, .js, .tsx, or .jsx files), the dApp will not be accepted. +The interface methods (`latestAnswer`, `getAnswer`, `latestRound`, `getRoundData`, `latestRoundData`, `getAssetPrice`) must be called from a smart contract (.sol file). If they are called from the frontend (.ts, .js, .tsx, or .jsx files), the dApp will not be accepted. The dApp must be open-source and have been publicly deployed before September 1, 2025, on Ethereum, Polygon, or BNB Chain. @@ -35,6 +35,11 @@ Teams must use their own infrastructure for deployment and testing, including RP Only verified contracts will be accepted—both the original and the migrated versions must be verified on a public block explorer so their source code can be automatically analyzed. +See the example migrations: + +- [Venus Protocol](/hackathon/venus-protocol) +- [Liquity](/hackathon/liquity) + ## Submitting projects Projects must be submitted through the official [Super Hackathon webpage](https://hackathon.superprotocol.com/).