Blockchain Developer

Omara – Blockchain Development Scope (RFP Summary)Project OverviewOmara is building a next-generation carbon credit platform that operates fully on-chain.The blockchain layer must support : Tokenisation of already-issued carbon creditsAn on-chain marketplace for purchase, transfer, and retirementA funding mechanism for new projects using escrow + milestone-based releasesAutomatic conversion of investor allocations into tokenised credits once credits are issuedAutomated connectivity with key registries (Verra, Gold Standard, Isometric, Puro.Earth)Transparent, verifiable, auditable on-chain activityThe 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 creditsIssuance ConversionWhen a project receives registry-issued credits : Burn Allocation TokensMint actual Credit TokensDistribute tokens automatically to investorsCredits can then be held, sold, or retired by investors or corporatesMarketplace BasicsOn-chain buy / sell for tokenised creditsOwnership transferRetirement logic (burn + proof)Event logs for all key actions (funding, transfer, retirement)Registry Integrations Automated registry connectivity is required for : VerraGold StandardIsometricPuro.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 batchesMap registry IDs / serials to on-chain token IDsSync 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 ControlsApprove / reject milestonesAuthorise escrow releasesConfirm issuance events linked to registry dataOptional multi-sig for high-privilege actionsExpected DeliverablesSmart ContractsCredit Token ContractAllocation Token ContractProject Funding + Escrow Contract(s)Milestone Tracking logicMarketplace contract(s)Issuance Conversion logicMetadata / registry mapping utilitiesAPIs / Web3 MethodsExpose lightweight methods to : Mint, transfer, and burn tokensFund a project and read escrow statusSubmit and approve milestones (admin side)Trigger issuance conversionRead ownership, allocation, and retirement dataConnect to registry-sync layer (hooks / addresses / IDs)Registry Integration LayerIntegration design and implementation for Verra, Gold Standard, Isometric, Puro.EarthClear mapping logic between registry entries and on-chain tokensBasic error handling and sync-status flagsDocumentationContract architecture overviewRegistry integration architectureDeployment stepsHow to interact with contracts and integration endpointsNo UI work is required — our internal team will integrate your layer into the Omara platform.Tech PreferencesChain choice can be finalised together based on security, cost, and ecosystem.Engagement ExpectationsWe’re looking for a development partner who can provide : A clear implementation plan with milestonesEstimated delivery timelinesClean, secure, and well-documented contractsSupport during integration and initial go-liveCollaboration on optimisation and iterationWhat We’d Like From YouIf 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 structureCommercial proposal for this Phase 1 scope