flow-pie/chamaa.api

Integrate Ethereum (Polygon testnet)

Open

#81 opened on Nov 9, 2025

View on GitHub
 (0 comments) (0 reactions) (0 assignees)HTML (4 forks)auto 404
help wanted

Repository metrics

Stars
 (3 stars)
PR merge metrics
 (PR metrics pending)

Description

Objective

Integrate the Polygon (Ethereum Layer 2) blockchain network to enable on-chain transactions for ChamaaChain’s savings and governance features.

Why Polygon?

Polygon offers fast, low-cost, and eco-friendly transactions—perfect for micro-savings and DAO governance in emerging markets.

Key Tasks

  • Configure Polygon testnet (Mumbai) connection using Alchemy or Infura.
  • Deploy a simple smart contract for on-chain savings records.
  • Implement a service (via Ethers.js or Nethereum) to interact with the contract.
  • Store transaction hashes in the backend DB (PostgreSQL).

Tech Stack

  • Smart Contracts: Solidity
  • Integration: Ethers.js / Nethereum
  • Blockchain Network: Polygon (Mumbai Testnet)
  • Backend: NestJS API

Acceptance Criteria

  • Successful deployment of the smart contract on Polygon testnet.
  • Backend can read/write on-chain transactions.
  • Each user’s transaction hash is stored and retrievable from the database.
  • Tested end-to-end with mock savings and governance data.

References

Future Extension

After testnet validation, migrate to Polygon mainnet and expand smart contracts to include loan approval and voting modules.

Contributor guide

Research direction
Deploy a smart contract on Polygon Mumbai testnet, integrate with NestJS backend using Ethers.js, and store transaction hashes in PostgreSQL.
Tech stack
typescriptnodejspostgresql
Domain
backendblockchain
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
SoliditySmart ContractsNestJS
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40