
from nethereum2,241
Index MUD Store events to rebuild off-chain MUD World state and persist it in PostgreSQL or EF Core-compatible schemas; supports continuous sync and normalized
Provides a complete workflow to process MUD Store events emitted on-chain, rebuild the full world state off-chain, and persist normalized relational tables in PostgreSQL or any EF Core store. It includes quick-start examples for in-memory processing, PostgreSQL normalisation helpers, query utilities, and a processor for continuous sync from block events. Concrete code samples (C#) show how to initialize the processing service, normalise records, and query the generated tables.
Use this skill when a user needs an off-chain indexer for MUD World data: rebuilding current state from Store events, exporting typed tables for analytics or explorer UIs, running a continuous sync job, or integrating with EF Core-based persistence. Triggers include mentions of MUD indexing, StoreEventsLogProcessingService, PostgreSQL normalisation, or building an indexer for MUD world data.
Best fit for developer-focused code assistants and environments that can run or edit C# (.NET) code, such as GitHub Copilot, Codex-style assistants, or Claude/Gemini when paired with a code execution or dev environment.
Documentation-only skill for indexing MUD Store events using the Nethereum .NET library into PostgreSQL or EF Core. No bundled scripts; all content is C# code snippets and dotnet CLI instructions. Clean skill with no security concerns — purely reference material for a niche Ethereum/.NET audience.
Pure documentation skill, no executable code. Very narrow audience (MUD framework + Nethereum + .NET). Well-written but limited applicability.
Nethereum: Keys & Accounts
Practical examples and snippets for generating keys, creating accounts, and encrypting/decrypting keystores using Nethereum for .NET applications.
Nethereum Multicall (batch queries)
Batch multiple Ethereum contract read calls into a single request using Nethereum's Multicall or RPC batching in .NET.