DIG Bounty - dApp to display payouts for stores

[MichaelTaylor3D]

Bounty: 1000 USDC

Confirm before starting: To prevent duplication of effort, please confirm with @MichaelTaylor3D before beginning work on this bounty.

Description:

We are looking for a developer to build a dApp that displays the payments made for an arbitrary store ID across all epochs to date. The dApp must retrieve and display payments for each combination of storeID and epoch using special hints. The goal is to show all coins that include CREATE COIN conditions for payments associated with a given storeID.

The developer should ensure that the dApp can handle payments from any storeID dynamically, meaning users can provide a storeID, and the app will display payments from all epochs. Additionally, the dApp should support deeplinks to specific stores for easy access.

Requirements:

• Retrieve Payment Data:

  • The dApp must fetch payment data for any storeID provided, displaying payments across all epochs.
  • Use hints associated with storeID and epoch combinations to look up payments. Each hint can retrieve coins with CREATE COIN conditions for the respective epoch and storeID.
  • A function to fetch coins by hint is available in the DataLayer-Driver repo for NodeJS. The developer can choose to use this function or another method to collect the payment data.

• Frontend (React preferred):

  • The frontend must dynamically handle and display payments for any arbitrary storeID.
  • The dApp should support deeplinks that allow users to share or directly navigate to specific storeIDs.
  • The preferred frontend framework is React due to its routing advantages when served on DIG peers. If you choose a different framework, you must ensure that the routing works correctly in both of the following cases:
    • When the app is mounted in a subdirectory on DIG peers.
    • When the app is mounted at the root on custom domains.
  • You must demonstrate that routing functions correctly in your submission.

• Backend (Optional):

  • If a backend is necessary (if a full frontend solution is not possible), it should provide a lightweight API to serve the payment data.
  • The backend should be implemented in TypeScript to ensure maintainability post-delivery.
  • The backend must efficiently handle requests for payment data by storeID and epoch.

Notes:

• Example Hint:
  • Payment hint: 6d41a13b486a8c1953bf1a142cdf41b7d322fb18c5e6085ae659a325cf9e9395
  • DIG Network payout:
    • Store ID: c7c0bc885b02531d42c72f11e90be6a22f76ac7d467acbfae76bc02d2221c352
    • Epoch: 4, Round: 554
• The dApp should allow users to provide any storeID and retrieve all payment data for all epochs related to that storeID.
• A frontend-only solution is preferred, but if a backend is necessary, it must be lightweight and optimized for dApp usage.

Acceptance Criteria:

• A fully functioning dApp that displays payment data for any arbitrary storeID across all epochs.
• The dApp supports deeplinks to specific storeIDs.
• Proper routing in the dApp when mounted in both subdirectories (on DIG peers) and at the root (on custom domains).
• If a backend is necessary, a working API implemented in TypeScript.
• The project must be delivered with clear instructions for deployment.

---

If you're interested in this bounty, please reach out in the comments for further clarification or any additional resources you may need.

[Anprotaku]

Hello @MichaelTaylor3D , I'm interested in this project, i am working with react with NextJS, amazon amplify etc at my company at the moment. I think a frontend only approach first using tanstack router would be a good start, if not possible using only frontend then switch to using something like NextJS to also implement the backend.

Im not familiar with the Chia blockchain atm but i guess all the information i need to retrieve data from the blockchain etc is in DataLayer-Driver repo and im a quick learner.

I feel like i could develop this project, a few pointers to get started would be appreciated, like how to fetch the required data using the DataLayer-Driver repo etc. After that i think i could handle the UI and etc.