Blockchain Developer

Omara – Blockchain Development Scope (RFP Summary)

Project Overview

Omara is building a next-generation carbon credit platform that operates fully on-chain.

The blockchain layer must support:

• Tokenisation of already-issued carbon credits
• An on-chain marketplace for purchase, transfer, and retirement
• A funding mechanism for new projects using escrow + milestone-based releases
• Automatic conversion of investor allocations into tokenised credits once credits are issued
• Automated connectivity with key registries (Verra, Gold Standard, Isometric, Puro.earth)
• Transparent, verifiable, auditable on-chain activity

The goal is to ensure trust, traceability, and automation across the full lifecycle of carbon credits.

Core Requirements (High-Level)

We want a lean, modular, and gas-efficient blockchain implementation that includes the following core components.

A.Credit Tokenisation (For Issued Credits)

a)Mint tokens representing existing carbon credits

b)Store core metadata (registry, vintage, project, serial number)

c)Enable listing, purchase, and transfer

d)On-chain retirement (token burn + reference to registry retirement)

B.Project Funding + Escrow (For New Projects)

a)Investors fund new projects directly on-chain

b)All funds go into a secure escrow contract

c)Developers define project milestones and amounts

d)Admin validates milestones → escrow releases funds per milestone

e)Investors receive Allocation Tokens representing future credits

Issuance Conversion

When a project receives registry-issued credits:

• Burn Allocation Tokens
• Mint actual Credit Tokens
• Distribute tokens automatically to investors
• Credits can then be held, sold, or retired by investors or corporates

Marketplace Basics

• On-chain buy/sell for tokenised credits
• Ownership transfer
• Retirement logic (burn + proof)
• Event logs for all key actions (funding, transfer, retirement)

Registry Integrations

Automated registry connectivity is required for:

• Verra
• Gold Standard
• Isometric
• Puro.earth

We are not expecting you to build a huge data platform, but we do need:

A simple integration layer (API/webhook/polling) that can:

• Fetch or receive issuance and retirement data for specific projects/credit batches
• Map registry IDs / serials to on-chain token IDs
• Sync status updates (issued / partially issued / retired)
• A clear mechanism to keep registry status and token status consistent.

This can be a thin integration service or smart contract + off-chain service combo — we’re open to your recommended architecture.

Simple Admin Controls

• Approve/reject milestones
• Authorise escrow releases
• Confirm issuance events linked to registry data
• Optional multi-sig for high-privilege actions

Expected Deliverables

• Smart Contracts
• Credit Token Contract
• Allocation Token Contract
• Project Funding + Escrow Contract(s)
• Milestone Tracking logic
• Marketplace contract(s)
• Issuance Conversion logic
• Metadata / registry mapping utilities

APIs / Web3 Methods

Expose lightweight methods to:

• Mint, transfer, and burn tokens
• Fund a project and read escrow status
• Submit and approve milestones (admin side)
• Trigger issuance conversion
• Read ownership, allocation, and retirement data
• Connect to registry-sync layer (hooks/addresses/IDs)

Registry Integration Layer

• Integration design and implementation for Verra, Gold Standard, Isometric, Puro.earth
• Clear mapping logic between registry entries and on-chain tokens
• Basic error handling and sync-status flags

Documentation

• Contract architecture overview
• Registry integration architecture
• Deployment steps
• How to interact with contracts and integration endpoints

No UI work is required — our internal team will integrate your layer into the Omara platform.

Tech Preferences

Chain choice can be finalised together based on security, cost, and ecosystem.

Engagement Expectations

We’re looking for a development partner who can provide:

• A clear implementation plan with milestones
• Estimated delivery timelines
• Clean, secure, and well-documented contracts
• Support during integration and initial go-live
• Collaboration on optimisation and iteration

What We’d Like From You

If you are interested, please share:

• A brief technical approach (1–2 pages is enough)
• Relevant past work (tokenisation, marketplaces, on-chain escrow, registry-style integrations if any)
• Estimated delivery timeline and team structure
• Commercial proposal for this Phase 1 scope