Model around application queries
Design the subgraph around the entities and relationships that the product needs, instead of exposing an unstructured stream of events.
Case 08 · NFT rental & indexing
NFT rentals that connect players with gaming assets held by owners and guilds.
Orium Network is an NFT rental and lending protocol for players and gaming guilds. It lets gaming assets be used through rentals and makes rental status and history available to the product. I contributed to contracts on three chains, led The Graph indexing and supported custom partner mechanics.
Contributed to the protocol on Ethereum, Polygon and Arbitrum and led a subgraph schema covering more than 15 event types. Supported custom rental mechanics for gaming partners.
Rental contracts need an application-facing view of their state. Games and analytics cannot depend on repeatedly reconstructing every contract event from scratch.
Worked on Solidity components for NFT rental and lending across three EVM networks.
Led event indexing and designed the subgraph schema for application and analytics queries.
Supported gaming partners with rental behaviors suited to their integrations.
A player or asset owner initiates a supported rental or lending action. Partner integrations express the rental rules needed by their game.
Gaming asset + rental terms → protocol callThe rental mechanics must match the game integration.The rental contract updates the agreement state and emits events. Those records describe what happened to the rental and become the input for indexing.
Rental state → protocol eventsThe contract is the source of the rental state.The subgraph maps more than 15 event types into entities that applications can query.
Events → subgraph entitiesAn indexed model should match real application questions.The product queries indexed data to show rental status and history. Gaming partners can consume the rental data across the supported chains.
Indexed rentals → player / guild viewA user should be able to see the state of their rental.Design the subgraph around the entities and relationships that the product needs, instead of exposing an unstructured stream of events.
Support partner requirements across the on-chain mechanics and the data consumed by their applications.
Implementation scope recorded in my CV for the July to October 2024 engagement.
Orium’s July 2023 product walkthrough predates my engagement. It explains the product, not my authorship of that feature.
Product context from Orium’s own July 2023 publication. My contribution scope follows the July to October 2024 engagement documented in my CV.
Simplified architecture walkthrough; partner data and private repositories are not included.