Skip to content

feat: update evently prediction markets on MegaETH#18658

Open
isonips wants to merge 1 commit intoDefiLlama:mainfrom
isonips:feat/add-evently
Open

feat: update evently prediction markets on MegaETH#18658
isonips wants to merge 1 commit intoDefiLlama:mainfrom
isonips:feat/add-evently

Conversation

@isonips
Copy link
Copy Markdown
Contributor

@isonips isonips commented Apr 5, 2026

(Needs to be filled only for new listings)

Name (to be shown on DefiLlama):

evently

Twitter Link:

https://twitter.com/eventlymarket

List of audit links if any:

(none yet)

Website Link:

https://evently.market

Logo (High resolution, will be shown with rounded borders):

(à uploader)

Current TVL:

~$0 (EventlyMarketsV3 pending deployment)

Treasury Addresses (if the protocol has treasury)

0x21CbC99a2E8c68F1C2955991E07c0C22ea895Da1 (MegaETH, Chain ID 4326)

Chain:

MegaETH (Chain ID 4326)

Coingecko ID (so your TVL can appear on Coingecko, leave empty if not listed):
Coinmarketcap ID (so your TVL can appear on Coinmarketcap, leave empty if not listed):
Short Description (to be shown on DefiLlama):

evently is a fully onchain prediction markets protocol on MegaETH. Trade outcomes on crypto, politics, culture and more. Powered by LMSR pricing with a hybrid CLOB + AMM architecture. Positions are ERC-1155 tokens settled in USDm.

Token address and ticker if any:

0xFAfDdbb3FC7688494971a79cc65DCa3EF82079E7 — USDm (base token, not protocol token)

Category (full list at https://defillama.com/categories) *Please choose only one:

Prediction Market

Oracle Provider(s): Specify the oracle(s) used (e.g., Chainlink, Band, API3, TWAP, etc.):

None — markets are resolved manually by designated resolvers onchain.

Implementation Details: Briefly describe how the oracle is integrated into your project:

No external oracle. Resolution is triggered by a permissioned resolver address calling the resolve function on-chain. Dispute mechanism planned for V3.

Documentation/Proof: Provide links to documentation or any other resources that verify the oracle's usage:

https://docs.evently.market

forkedFrom (Does your project originate from another project):

None

methodology (what is being counted as tvl, how is tvl being calculated):

TVL is the total USDm locked in evently smart contracts (EventlyProfiles + EventlyMarketsV3) on MegaETH. Fees: 2.5% per trade via LMSR pricing — 1% to market creator, 1% to protocol treasury, 0.5% to resolver. EventlyMarketsV3 address pending deployment.

Github org/user (Optional, if your code is open source, we can track activity):

https://github.com/isonips/evently

Does this project have a referral program?

No

Summary by CodeRabbit

  • New Features
    • Added support for tracking the evently protocol on MegaETH, including total value locked metrics via profile holdings.
    • Added treasury tracking configuration for evently.
    • Future support for Markets V3 metrics is planned following protocol deployment.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Apr 5, 2026

📝 Walkthrough

Walkthrough

Two new configuration modules added for the Evently project on MegaETH: one defining TVL calculation via sumTokensExport and a methodology description, the other configuring treasury tracking with nullAddress token placeholder. Markets V3 noted as future inclusion.

Changes

Cohort / File(s) Summary
Evently Configuration
projects/evently/index.js, projects/treasury/evently.js
Added dataset configuration for Evently prediction markets on MegaETH, including TVL calculation via USDM token tracking, methodology documentation, and treasury configuration with pending Markets V3 integration.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 Ah, a new prediction market comes to play,
Where USDM and profiles show the way,
On MegaETH's chains, our TVL shall rise,
While Markets V3 waits for its grand prize! 📊✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title 'feat: update evently prediction markets on MegaETH' directly and accurately describes the main objective of the PR: adding integration metadata for the Evently protocol on MegaETH.
Description check ✅ Passed The PR description follows the template structure and provides comprehensive information for a new listing, including all critical sections like Name, Website, Chain, Twitter, Treasury Address, Token Address, Category, Methodology, and Documentation.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@llamabutler
Copy link
Copy Markdown

The adapter at projects/evently exports TVL:

megaeth                   0.00

total                    0.00 

@llamabutler
Copy link
Copy Markdown

The adapter at projects/treasury/evently.js exports TVL:

megaeth                   10.00

total                    10.20 

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (1)
projects/treasury/evently.js (1)

7-9: Prefer explicit USDm treasury token configuration.

Given fee accrual is in USDm, consider explicitly adding USDm here (and optionally disabling default token expansion) so treasury accounting doesn’t rely on helper defaults.

Suggested deterministic config
 const { treasuryExports } = require("../helper/treasury");
 const { nullAddress } = require('../helper/tokenMapping');
+const USDM = '0xFAfDdbb3FC7688494971a79cc65DCa3EF82079E7';

 module.exports = treasuryExports({
   megaeth: {
     owners: ['0x21CbC99a2E8c68F1C2955991E07c0C22ea895Da1'],
+    fetchCoValentTokens: false,
     tokens: [
       nullAddress,
+      USDM,
     ],
   },
 })
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@projects/treasury/evently.js` around lines 7 - 9, The treasury config
currently only lists nullAddress in the tokens array which allows helper
defaults to fill in USDm implicitly; update the tokens array in
projects/treasury/evently.js to explicitly include the USDm token identifier
(add the USDm token alongside nullAddress) and, if present in the surrounding
config, set or add the flag that disables default token expansion (e.g., an
expandTokens: false or similar option) so treasury accounting deterministically
uses USDm rather than relying on helper defaults.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@projects/evently/index.js`:
- Around line 21-26: Update the methodology string in projects/evently/index.js
to reflect the actual current calculation (i.e., TVL only sums PROFILES_V1),
explicitly state that protocol-owned/treasury balances are excluded from TVL and
tracked separately, and keep the note that EventlyMarketsV3 address is pending;
modify the value assigned to the methodology key (the multi-line string shown)
to this corrected wording so it matches the implemented behavior.

---

Nitpick comments:
In `@projects/treasury/evently.js`:
- Around line 7-9: The treasury config currently only lists nullAddress in the
tokens array which allows helper defaults to fill in USDm implicitly; update the
tokens array in projects/treasury/evently.js to explicitly include the USDm
token identifier (add the USDm token alongside nullAddress) and, if present in
the surrounding config, set or add the flag that disables default token
expansion (e.g., an expandTokens: false or similar option) so treasury
accounting deterministically uses USDm rather than relying on helper defaults.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 3a8d2959-6833-4440-80c8-7d144a9f3868

📥 Commits

Reviewing files that changed from the base of the PR and between 3ff8ad0 and eb96cf5.

📒 Files selected for processing (2)
  • projects/evently/index.js
  • projects/treasury/evently.js

Comment on lines +21 to +26
methodology:
"TVL is the total USDM locked in evently smart contracts (Profiles + Prediction Markets V3) on MegaETH. " +
"Fees: 2.5% per trade via LMSR pricing — 1% to market creator, 1% to protocol treasury, 0.5% to resolver. " +
"Revenue: 1% of all trading volume goes to the protocol treasury. " +
"Volume: sum of all USDM traded on prediction markets (TradeExecuted events). " +
"EventlyMarketsV3 address is pending deployment and will be added upon launch.",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Methodology text currently overstates TVL scope.

The implementation only sums PROFILES_V1, but the text says TVL includes Profiles + Markets V3. Please reword to current-state behavior and explicitly state treasury balances are excluded from TVL (tracked separately).

Suggested wording update
-  methodology:
-    "TVL is the total USDM locked in evently smart contracts (Profiles + Prediction Markets V3) on MegaETH. " +
+  methodology:
+    "TVL is the total USDM currently locked in Evently Profiles on MegaETH; EventlyMarketsV3 will be added after deployment. " +
+    "Protocol treasury balances are excluded from TVL and tracked separately. " +
     "Fees: 2.5% per trade via LMSR pricing — 1% to market creator, 1% to protocol treasury, 0.5% to resolver. " +
     "Revenue: 1% of all trading volume goes to the protocol treasury. " +
     "Volume: sum of all USDM traded on prediction markets (TradeExecuted events). " +
-    "EventlyMarketsV3 address is pending deployment and will be added upon launch.",
+    "EventlyMarketsV3 address is pending deployment and will be added upon launch.",

Based on learnings: Protocol-owned liquidity should be excluded from TVL calculations and explained in the methodology field.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@projects/evently/index.js` around lines 21 - 26, Update the methodology
string in projects/evently/index.js to reflect the actual current calculation
(i.e., TVL only sums PROFILES_V1), explicitly state that protocol-owned/treasury
balances are excluded from TVL and tracked separately, and keep the note that
EventlyMarketsV3 address is pending; modify the value assigned to the
methodology key (the multi-line string shown) to this corrected wording so it
matches the implemented behavior.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants