ape-church-contracts

Map Ape Church contract components to addresses and roles.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/MercBert/apechurchpnlchecker --skill ape-church-contracts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ape-church-contracts
Source: https://github.com/MercBert/apechurchpnlchecker/tree/main/.claude/skills/ape-church-contracts
Command: npx skills add https://github.com/MercBert/apechurchpnlchecker --skill ape-church-contracts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a definitive reference for Ape Church's on-chain casino contracts, detailing how GovernanceManager, FeeReceiver, House, ClaimManager, ReferralManager, EXPManager, and related addresses interact to power wagers, payouts, and revenue flow. It equips engineers and analysts to build dashboards, indexers, and analytics tools that accurately reflect the platform's economics and governance.

Core Features & Use Cases

  • Contract architecture mapping: identify core contracts, their roles, and interconnections.
  • Revenue & flow audits: trace platform fees, GP discounts, referrals, and partner payments to the wallet recipients and vaults.
  • Dashboard-ready data: expose per-contract addresses, relationships, and event surfaces for monitoring and analytics.
  • Code references for integration: provide a stable reference for integrating with GovernanceManager and involved contracts in tools and dashboards.

Quick Start

Summarize the Ape Church contract architecture, map core component addresses, and outline standard wager, fee, and payout flows for a project brief.

Frequently Asked Questions about ape-church-contracts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I map Ape Church blockchain contract addresses for dashboard integration?

To map Ape Church blockchain contract addresses, identify core components like GovernanceManager, FeeReceiver, and House, then extract their specific roles and interconnections to generate stable address mappings for your dashboard or indexer integration.

How does revenue flow through Ape Church on-chain casino contracts during payouts?

Revenue flows through Ape Church on-chain casino contracts by routing platform fees, GP discounts, and partner payments via the FeeReceiver to designated vaults and wallet recipients, which you can trace by indexing payout events and wager flows.

What on-chain data surfaces do I need to monitor Ape Church wagering and payout events?

Monitoring Ape Church wagering and payout events requires indexing on-chain data surfaces for per-game fees, P&L, user wagering volume, GP issuance, and payout events, exposing these event indices directly to your analytics dashboards.

Can I trace GP and EXP issuance flows across the Ape Church contract ecosystem?

You can trace GP and EXP issuance flows across the Ape Church contract ecosystem by mapping the EXPManager and EXPBoostManager components, analyzing their event surfaces to track token issuance and boost mechanics for analytics monitoring.

Does the Ape Church architecture support tracking referral and partner payments on-chain?

The Ape Church architecture supports tracking referral and partner payments on-chain by utilizing the ReferralManager contract, allowing you to audit how referral rewards and partner revenue shares flow to specific wallet recipients and vaults.

What are the limitations of building governance analytics for Ape Church contracts?

Building governance analytics for Ape Church contracts requires accurate address mappings for the GovernanceManager and related components, with limitations arising if event indices are incomplete or contract interconnections are not properly mapped before dashboard deployment.