The problem ChainPact solves

ChainPact deems to a decentralized application for creating and managing agreements (or pacts) in a peer to peer fashion.
This includes a set of tailor-made smart contracts and user interfaces for specific use-cases, namely:

• Gig Pact: For use in an employer-employee agreement setting with escrowed payments and timed pro-rated payment calculation
• Proposal Pact: For creating an announcement on blockchain to raise funds for a project or proposal, with support for voting

Challenges I ran into

• Securing smart contracts is a knowledge-oriented task, needed to scrub through a lot of documentations, previous vulnerabilities, known good audit reports to identify potential issues in ChainPact contracts
• Upgradeable smart contracts have their usual catch, identifying potential pitfalls with OpenZeppelin's libraries was a hit or miss, since it is an evolving
• The Graph protocol is a relatively new solution with many rough edges, debugging and logging of issues was a challenge
• The Graph protocol's documentation isn't always very straightforward or detailed, a lot of things during the design and coding of the subgraph
• Identifying user requirements by conversing with users is a tedious task and sometimes it's hard to streamline responses