Skip to content

Add @moltraffle/elizaos-plugin#310

Open
Hizarcu wants to merge 1 commit intoelizaos-plugins:mainfrom
Hizarcu:add-moltraffle-plugin
Open

Add @moltraffle/elizaos-plugin#310
Hizarcu wants to merge 1 commit intoelizaos-plugins:mainfrom
Hizarcu:add-moltraffle-plugin

Conversation

@Hizarcu
Copy link

@Hizarcu Hizarcu commented Mar 19, 2026

Plugin: @moltraffle/elizaos-plugin

Adds moltraffle.fun plugin to the registry.

npm: https://www.npmjs.com/package/@moltraffle/elizaos-plugin
GitHub: https://github.com/Hizarcu/elizaos-plugin-moltraffle
Homepage: https://moltraffle.fun

What it does

Permissionless on-chain raffles on Base mainnet. Humans and AI agents can create raffles, sell tickets, and earn commission.

Actions (5)

  • LIST_RAFFLES — browse active raffles
  • GET_RAFFLE — full details by address
  • JOIN_RAFFLE — calldata to buy tickets
  • CREATE_RAFFLE — calldata to deploy a new raffle
  • DRAW_WINNER — calldata to trigger Chainlink VRF draw (permissionless)

Usage

import { moltrafflePlugin } from "@moltraffle/elizaos-plugin";
const runtime = new AgentRuntime({ plugins: [moltrafflePlugin] });

All actions return transaction calldata — wallet provider handles signing. Live on Base mainnet.

Summary by CodeRabbit

Release Notes

  • New Features
    • Added @moltraffle/elizaos-plugin to the package registry, making it available for installation and use.

Greptile Summary

This PR registers the @moltraffle/elizaos-plugin community plugin in the ElizaOS plugin registry. The plugin provides permissionless on-chain raffle functionality on Base mainnet, exposing five actions (LIST_RAFFLES, GET_RAFFLE, JOIN_RAFFLE, CREATE_RAFFLE, DRAW_WINNER) that return transaction calldata for wallet signing.

Changes:

  • Adds one registry entry: "@moltraffle/elizaos-plugin": "github:Hizarcu/elizaos-plugin-moltraffle" — correctly placed in alphabetical order between @mazzz/plugin-elizaos-compchembridge and @nuggetslife/plugin-nuggets
  • Fixes a pre-existing missing newline at end of file

Observations:

  • The entry format is consistent with comparable community plugin entries in the registry (e.g. @blockrun/elizaos-plugin follows the same @scope/elizaos-plugin naming pattern)
  • Alphabetical ordering is correct (mazzzmoltrafflenuggetslife)
  • The plugin package was independently surfaced by a third-party aggregator (Agent Tresor), providing additional confidence that it exists in the ecosystem
  • No structural or formatting issues found

Confidence Score: 4/5

  • This PR is safe to merge; it is a well-formed, alphabetically ordered registry entry addition with no structural issues.
  • The change is minimal (one line added, one newline fixed), the JSON format is correct, and the entry follows established patterns in the registry. A score of 4 rather than 5 reflects that the external GitHub repository and npm package availability cannot be fully verified programmatically at review time — standard for third-party community plugin submissions.
  • No files require special attention.

Important Files Changed

Filename Overview
index.json Adds @moltraffle/elizaos-plugin pointing to github:Hizarcu/elizaos-plugin-moltraffle in the correct alphabetical position, and fixes a pre-existing missing newline at end of file.

Sequence Diagram

sequenceDiagram
    participant User/Agent
    participant moltrafflePlugin
    participant MoltraffleAPI
    participant BaseMainnet

    User/Agent->>moltrafflePlugin: LIST_RAFFLES
    moltrafflePlugin->>MoltraffleAPI: fetch active raffles
    MoltraffleAPI-->>moltrafflePlugin: raffle list
    moltrafflePlugin-->>User/Agent: raffle list

    User/Agent->>moltrafflePlugin: GET_RAFFLE (address)
    moltrafflePlugin->>MoltraffleAPI: fetch raffle details
    MoltraffleAPI-->>moltrafflePlugin: raffle details
    moltrafflePlugin-->>User/Agent: full raffle details

    User/Agent->>moltrafflePlugin: JOIN_RAFFLE / CREATE_RAFFLE / DRAW_WINNER
    moltrafflePlugin->>MoltraffleAPI: build transaction calldata
    MoltraffleAPI-->>moltrafflePlugin: calldata
    moltrafflePlugin-->>User/Agent: transaction calldata

    User/Agent->>BaseMainnet: wallet provider signs & submits tx
    BaseMainnet-->>User/Agent: tx confirmation
Loading

Last reviewed commit: "Add @moltraffle/eliz..."

(2/5) Greptile learns from your feedback when you react with thumbs up/down!

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 19, 2026

Walkthrough

A new entry mapping the package @moltraffle/elizaos-plugin to the GitHub repository github:Hizarcu/elizaos-plugin-moltraffle was added to index.json, along with a trailing newline at the end of the file.

Changes

Cohort / File(s) Summary
Configuration
index.json
Added new package mapping entry for @moltraffle/elizaos-plugin pointing to GitHub repository; corrected file ending with trailing newline.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A new plugin joins our index today,
Moltraffle's path now on display,
From Hizarcu's repo it shall arrive,
Mappings grow and registries thrive! 📦✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description provides plugin details (purpose, actions, usage) but does not follow the required Registry Update Checklist template with verification steps. Use the Registry Update Checklist template to verify: package name format, github URL format, alphabetical placement, JSON validity, and confirm the plugin repo meets all requirements (public access, main branch, required topics, images, and agentConfig).
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The title 'Add @moltraffle/elizaos-plugin' clearly and concisely summarizes the main change: adding a new plugin entry to the registry.
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
📝 Coding Plan
  • Generate coding plan for human review comments

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.

Tip

CodeRabbit can use oxc to improve the quality of JavaScript and TypeScript code reviews.

Add a configuration file to your project to customize how CodeRabbit runs oxc.

Copy link
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

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@index.json`:
- Line 360: The index.json entry for "@moltraffle/elizaos-plugin" points to
"github:Hizarcu/elizaos-plugin-moltraffle" but the published package metadata
shows repository "https://github.com/Hizarcu/moltraffle-mainnet.git"; confirm
which repo is authoritative (check the npm package
`@moltraffle/elizaos-plugin`@0.1.1 and the upstream GitHub org), then update the
value for the "@moltraffle/elizaos-plugin" entry to the correct repository
identifier/URL to match the npm package metadata (or change the npm metadata if
the GitHub repo is correct), ensuring the string in index.json equals the
confirmed repository.
🪄 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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: a23e585b-4b91-42bb-b183-b6d03b684d1d

📥 Commits

Reviewing files that changed from the base of the PR and between ce554dd and 0a8065f.

📒 Files selected for processing (1)
  • index.json

"@kudo-dev/plugin-kudo": "github:Kudo-Archi/plugin-kudo",
"@mascotai/plugin-connections": "github:mascotai/plugin-connections",
"@mazzz/plugin-elizaos-compchembridge": "github:Mazzz-zzz/plugin-elizaos-compchembridge",
"@moltraffle/elizaos-plugin": "github:Hizarcu/elizaos-plugin-moltraffle",
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Verify GitHub repository exists and npm package is published

echo "=== Checking GitHub repository ==="
gh repo view Hizarcu/elizaos-plugin-moltraffle --json name,description,url,createdAt,pushedAt,isArchived,visibility

echo -e "\n=== Checking npm package ==="
npm view `@moltraffle/elizaos-plugin` name version description repository homepage

echo -e "\n=== Checking for security advisories ==="
npm audit --package-lock-only --registry=https://registry.npmjs.org `@moltraffle/elizaos-plugin` 2>&1 || echo "Note: Full audit requires package installation"

Repository: elizaos-plugins/registry

Length of output: 580


🏁 Script executed:

#!/bin/bash
# Check if the referenced repository exists and clarify the discrepancy

echo "=== Checking if referenced GitHub repo exists (via curl) ==="
curl -s -I https://github.com/Hizarcu/elizaos-plugin-moltraffle 2>&1 | head -1

echo -e "\n=== Checking npm package registry info in detail ==="
npm view `@moltraffle/elizaos-plugin` --json 2>&1 | python3 << 'PYTHON'
import json, sys
try:
    data = json.load(sys.stdin)
    print(f"Package: {data.get('name')}")
    print(f"Version: {data.get('version')}")
    repo = data.get('repository', {})
    if isinstance(repo, dict):
        print(f"Repository URL: {repo.get('url')}")
    else:
        print(f"Repository: {repo}")
except Exception as e:
    print(f"Error: {e}")
PYTHON

echo -e "\n=== Verifying against index.json entry ==="
echo "index.json references: github:Hizarcu/elizaos-plugin-moltraffle"
echo "npm registry lists repo: (see above)"

Repository: elizaos-plugins/registry

Length of output: 389


🏁 Script executed:

#!/bin/bash
# Verify the actual entry in index.json
echo "=== Content around line 360 in index.json ==="
sed -n '355,365p' index.json

echo -e "\n=== Also check for any other moltraffle or Hizarcu entries ==="
grep -n "moltraffle\|Hizarcu" index.json

Repository: elizaos-plugins/registry

Length of output: 1059


Resolve repository URL mismatch before merging.

The entry format and alphabetical ordering are correct, but there is a critical discrepancy: index.json references github:Hizarcu/elizaos-plugin-moltraffle, however the published npm package (@moltraffle/elizaos-plugin@0.1.1) lists its repository as https://github.com/Hizarcu/moltraffle-mainnet.git.

These are two different repositories. Confirm which repository is the authoritative source for this plugin and update the index.json entry accordingly to match the npm package metadata.

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

In `@index.json` at line 360, The index.json entry for
"@moltraffle/elizaos-plugin" points to
"github:Hizarcu/elizaos-plugin-moltraffle" but the published package metadata
shows repository "https://github.com/Hizarcu/moltraffle-mainnet.git"; confirm
which repo is authoritative (check the npm package
`@moltraffle/elizaos-plugin`@0.1.1 and the upstream GitHub org), then update the
value for the "@moltraffle/elizaos-plugin" entry to the correct repository
identifier/URL to match the npm package metadata (or change the npm metadata if
the GitHub repo is correct), ensuring the string in index.json equals the
confirmed repository.

@Hizarcu
Copy link
Author

Hizarcu commented Mar 19, 2026

Fixed. The npm package metadata was pointing to the old monorepo (moltraffle-mainnet). Published v0.1.2 with the repository field updated to https://github.com/Hizarcu/elizaos-plugin-moltraffle. The index.json entry is correct.

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.

1 participant