Statement of Work (SoW): BAC Inc. x Minsta - June 2024

Project Overview

The Minsta project is an open-source template currently managed by Mintbase. BAC Inc. (BAC Inc.) is taking over the management and aims to implement new features to enhance the functionality of the template. The primary objective for June 2024 is to develop and deploy an admin panel with specific functionalities, including NFT filtering and other UX improvements.

Team

Project Manager

Chloe
Email: [e-mail]
NEAR Account: chloe.near

Development Team

Teckas Technologies
LinkedIn: Teckas Technologies

Budget Allocation

June Invoice

• Total Budget for June: $2,500
  • Project Management: $500 (allocated to Chloe)
  • Development Work: $2,000 (allocated to Teckas Technologies)

Payment Details

• Funding Recipient: marmaj-research.sputnik-dao.near
• Payment Method: USDC or USDT on NEAR Protocol
• Payment Deadline: June 30th, 2024

Deliverables

1. Admin Page

• Description: Add an admin page to the template.
• Requirements:
  • The admin page should allow the contract owner to set NFT filtering options for the UI (time-based).
  • Implement basic access controls to determine who can mint.
  • Allow the contract owner to set "share" information for mints.
  • Enable the contract owner to edit leaderboard -> "View Rewards" information.

2. Future Features (Backlog)

• Backlog Features:
  1. Implement additional filters for additional modularity with Minsta streams.
  2. Implement access control for viewing Minsta streams.
  3. Add more wallet connections (how are minting fees handled?).
  4. Video capture and mint (GIF implementation for now).
  5. NFT collection button (mints a copy/edition to the calling account).
  6. Upvote mechanism for displayed mints.
  7. Integration with additional social platforms for sharing.

Timeline

• Start Date: June 1st, 2024
• End Date: June 30th, 2024
• Milestones:
  • Completion of admin page and all listed functionalities, including NFT filtering, by June 30th.

Reporting and Communication

• Progress Reporting: Weekly updates via calls, with notes shared on GitHub discussions for transparency.
• Communication Channels: Telegram for daily communication, GitHub for reporting.

Risks and Contingencies

• Known Risks:

  • Potential delays in development due to unforeseen technical challenges.
  • Dependencies on third-party services for wallet connections and social platform integrations.

• Contingencies:

  • Regular check-ins to identify and mitigate risks early.
  • Allocation of additional resources from Teckas Technologies if necessary.