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
Orium Network
NFT rentals needed contracts that games could use and data they could query.
I contributed to a multi-chain NFT rental and lending protocol, then connected contract events to the application through The Graph and partner integrations.
Result
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.
My part
What I did
Rental contracts need an application-facing view of their state. Games and analytics cannot depend on repeatedly reconstructing every contract event from scratch.
01
Protocol development
Worked on Solidity components for NFT rental and lending across three EVM networks.
02
The Graph integration
Led event indexing and designed the subgraph schema for application and analytics queries.
03
Partner mechanics
Supported gaming partners with rental behaviors suited to their integrations.
How it worksSimplified walkthrough. No live transactions.
From contract events to a usable rental experience
Application + wallet
A user initiates a supported rental or lending action through the protocol.
User action → protocol callThe application needs to express the protocol’s mechanics.Example state, not live data
- Action
- Requested
- Contract
- Previous state
- Application data
- Previous view
Solidity
The relevant contract changes its state and emits the events that describe the action.
Contract state → eventsThe contract is the source of the rental state.Example state, not live data
- Action
- Executed
- Contract
- Updated state
- Application data
- Event emitted
The Graph
The subgraph maps more than 15 event types into entities that applications can query.
Events → subgraph entitiesAn indexed model should match real application questions.Example state, not live data
- Action
- Indexed
- Contract
- Updated state
- Application data
- Entities updated
Game + analytics integration
Partners use the indexed view to support their rental interfaces and analytics across supported chains.
Queryable state → partner experienceUseful protocol data must be accessible to the product.Example state, not live data
- Action
- Available
- Contract
- Updated state
- Application data
- Queryable rental view
Trade-offs
Decisions I made
Connect contracts and integration
Support partner requirements across the on-chain mechanics and the data consumed by their applications.
Links and records
See the work
Career record
Three chains · 15+ event types
Implementation scope recorded in my CV for the July to October 2024 engagement.
Architecture walkthrough
Contract-to-subgraph flow
The flow explains the boundary between authoritative contract state, indexed entities and partner applications.
Contribution scope from the July to October 2024 engagement, as documented in my CV.
Simplified architecture walkthrough; partner data and private repositories are not included.