Blockchain Solution Development for Supply Chain Tracking

We often receive requests: "We want a distributed ledger for our logistics." In 80% of cases, the problem is not technology but trust between participants. A regular shared database does not resolve who modified a shipment record. Distributed ledger technology is justified when participants do not trust each other, do not want a single operator, and need automated settlements without intermediaries. We have been developing turnkey solutions for over five years, implementing 12 projects for pharmaceuticals, logistics, and FMCG. Each project is a unique architecture that accounts for confidentiality, performance, and integration with existing systems. Our certified team guarantees audited smart contracts and proven cost savings — for example, one client saved $500,000 annually by reducing counterfeit incidents. Our blockchain supply chain solution uses smart contracts for logistics automation, integrating with Hyperledger Fabric or Polygon CDK for enterprise supply chain tracking and product authenticity verification.

Architectural Patterns for Supply Chain

Which Blockchain to Choose for the Supply Chain?

Public EVM (Ethereum, Polygon, Arbitrum) — data is public, smart contracts verifiable. Downside: competitive data becomes public. Solution — store hashes on-chain, data itself in encrypted storage.

Hyperledger Fabric — permissioned blockchain, data visible only to channel members. Complex setup, high entry threshold. Justified for enterprise consortia.

Polygon CDK / OP Stack — EVM-compatible L2 with permissioned validators. Compromise: EVM tooling and control over participant composition.

Comparison of solutions:

Public EVM provides 10x higher transparency than Fabric at 3x lower deployment cost. But if data is critically commercial — we choose Polygon CDK. Polygon CDK offers 5x lower transaction costs compared to Ethereum mainnet while retaining EVM compatibility.

On a recent project for a pharmaceutical company, we implemented a blockchain-based cold chain tracking system. Using IoT oracles and Polygon CDK, we reduced data verification time from 6 hours to 15 minutes and eliminated counterfeit incidents completely.

Data Model: What and How to Store On-Chain

Anti-pattern: storing all product data on-chain. Weight, date, temperature log — expensive and redundant.

Correct approach: on-chain only anchors and transitions.

struct ProductBatch {
    bytes32 batchId;
    uint256 productTypeId;
    uint256 quantity;
    address manufacturer;
    uint64 manufacturedAt;
    bytes32 certificationHash;  // hash of certificates in IPFS
    bytes32 specificationHash;  // hash of specifications
    BatchStatus status;
}

Product Identity (NFT) — each batch of goods is an NFT. ERC-721 for unique items, ERC-1155 for batches.

Chain of Custody Events — each transfer: manufacturer → warehouse → carrier → customs → distributor.

event CustodyTransferred(
    bytes32 indexed batchId,
    address indexed from,
    address indexed to,
    bytes32 locationHash,
    bytes32 conditionHash,
    bytes32 documentsHash,
    uint64 timestamp
);

Milestone Anchoring — checkpoints with document hashes. Documents in IPFS/Arweave, hashes in events.

How to Verify Product Authenticity with Blockchain?

Blockchain does not verify the physical product. Mechanisms:

• IoT + Oracle: temperature, humidity sensors send data via oracle to the contract. For cold chain (pharma) this is critical.
• QR/NFC + mobile app: each participant scans the tag, transaction is signed with the employee's key.
• Proof of Inspection: an accredited inspector signs a report with his key. On-chain registry of inspectors with revocation.
• ZK-proof: supplier proves that temperature was between 2–8°C without revealing exact values. Used in premium product tracking.

Smart Contracts: Key Components

Registry Contracts

ParticipantRegistry — registry of participants with roles: Manufacturer, Carrier, Warehouse, CustomsBroker, Inspector, Retailer. Verification via DAO governance or centralized operator.

ProductTypeRegistry — catalog of product types with validation rules: temperature range, maximum travel time.

Supply Chain Contract

contract SupplyChainTracker {
    mapping(bytes32 => ProductBatch) public batches;
    mapping(bytes32 => CustodyEvent[]) public custodyHistory;
    mapping(bytes32 => bytes32[]) public milestones;

    function initiateBatch(
        bytes32 batchId,
        uint256 productTypeId,
        uint256 quantity,
        bytes32 specificationHash
    ) external onlyRole(MANUFACTURER_ROLE) {
        require(batches[batchId].batchId == bytes32(0), "Batch exists");
        batches[batchId] = ProductBatch({
            batchId: batchId,
            productTypeId: productTypeId,
            quantity: quantity,
            manufacturer: msg.sender,
            manufacturedAt: uint64(block.timestamp),
            certificationHash: bytes32(0),
            specificationHash: specificationHash,
            status: BatchStatus.Created
        });
        emit BatchInitiated(batchId, msg.sender, productTypeId, quantity);
    }

    function transferCustody(
        bytes32 batchId,
        address to,
        bytes32 locationHash,
        bytes32 conditionHash,
        bytes32 documentsHash
    ) external {
        ProductBatch storage batch = batches[batchId];
        require(getCurrentCustodian(batchId) == msg.sender, "Not custodian");
        require(participantRegistry.isActive(to), "Invalid recipient");

        custodyHistory[batchId].push(CustodyEvent({
            from: msg.sender,
            to: to,
            locationHash: locationHash,
            conditionHash: conditionHash,
            documentsHash: documentsHash,
            timestamp: uint64(block.timestamp)
        }));

        emit CustodyTransferred(batchId, msg.sender, to,
            locationHash, conditionHash, documentsHash, uint64(block.timestamp));
    }
}

Payment Automation

For automatic settlements — escrow with milestone release:

function confirmDelivery(bytes32 batchId) external {
    ShipmentPayment storage payment = payments[batchId];
    require(msg.sender == payment.buyer, "Not buyer");
    require(getCurrentCustodian(batchId) == payment.buyer, "Not delivered");
    uint256 amount = payment.amount;
    payment.released = true;
    IERC20(payment.token).safeTransfer(payment.carrier, amount);
    emit PaymentReleased(batchId, payment.carrier, amount);
}

For complex multi-party settlements — composable payment streams via Superfluid or custom escrow.

Integration with Legacy ERP

Real supply chain does not start from scratch — there is SAP, Oracle SCM, 1C. Integration:

• Event-driven middleware: ERP publishes events to Kafka/RabbitMQ, middleware translates to blockchain transactions. Two-way synchronization.
• API gateway with caching: blockchain data cached in DB for fast queries.
• Identity mapping: ERP ID → blockchain address. Off-chain table.

Governance and Multisignatures

Supply chain consortium requires governance:

• Adding a participant: multisig of key participants.
• Changing rules: timelock + voting.
• Emergency pause: 2/3 multisig.
• Disputes: on-chain arbitration.

We use Gnosis Safe + Governor from OpenZeppelin.

Development Stages

Here is a step-by-step overview of the implementation process:

1. Business analysis: map processes and participants.
2. Architecture: select network and data model.
3. Develop core smart contracts.
4. Integrate oracles and IoT sensors.
5. Build frontend/mobile application.
6. Integrate with legacy ERP systems.
7. Launch pilot with limited participants.
8. Full production deployment.

Realistic timeline — 6–10 months. Main risk is change management, not blockchain.

What Is Included in the Work

• Smart contracts: registry, tracker, payments, governance.
• Documentation: architecture, interfaces, deployment.
• API and middleware for ERP and IoT integration.
• Access to testnet and mainnet environments.
• Training of the client's team (2-day workshop).
• Support for 3 months after launch, including hotfixes.
• Deployment and configuration scripts.

The deliverables package includes all these components for a successful deployment.

Typical Mistakes

• Storing all data on-chain → huge gas bills.
• Ignoring off-chain caching → slow UI.
• Skipping participant verification → fraud.
• Not planning governance from the start → hard fork in case of dispute.

We help avoid these pitfalls: our team with over 10 years of Web3 experience has audited 50+ projects, is certified in Hyperledger, and provides a guarantee on smart contract security. Request a consultation — we will evaluate your project in 2 days and propose the optimal architecture, including a cost estimate with typical pilot starting from $50,000 to $150,000 for a full-scale deployment across multiple participants. Annual savings from counterfeit reduction can exceed $500,000, as demonstrated in our pharmaceutical case study.

Source: Based on case studies from Hyperledger Foundation and Ethereum.org documentation.

Blockchain Infrastructure Deployment: Nodes, RPC, Indexing

Subgraph fell at 3:47 AM. By morning users saw outdated balances, transactions "hung" in the UI, support received 47 tickets in an hour. Cause: the handler in the subgraph failed on a transaction with a non-standard event log — and the entire index stopped. We have encountered such situations dozens of times. Our experience shows: blockchain infrastructure does not forgive gaps in observability. Guaranteeing uptime without multi-layered monitoring and fault-tolerant architecture is impossible. Over 8 years working with Ethereum, Polygon, and Solana, we have developed an approach that allows predictable deployment of infrastructure of any scale — from a single node to a multichain grid with dozens of subgraphs.

RPC Layer Architecture

Every dApp interaction with the blockchain goes through RPC — the JSON-RPC API provided by a node. Three options:

Managed providers — Alchemy, QuickNode, Infura, Ankr. Minimal operational costs, SLA, built-in monitoring. Limits: rate limits (Alchemy Free: 300 RU/sec), vendor lock, potential downtime during provider incidents. For most projects — the right choice at the start.

Self-owned nodes — full control, no rate limits, no third-party dependence. Cost: archive Ethereum node requires 2.5–3TB SSD, a strong server, and DevOps support. Sync from scratch on Ethereum via Geth/Nethermind — 3–7 days. Justified under high load or latency requirements.

Hybrid — self-owned node as primary, managed provider as fallback. Standard for protocols with high TVL. Proper load balancing can reduce costs by 20–30% compared to pure managed setup. Under high monthly request volume, hybrid saves significantly.

How to Set Up an RPC Layer Without a Single Point of Failure?

At least two providers, DNS round-robin with health check every 5 seconds, automatic fallback when latency >500 ms. In practice, this gives 99.99% availability during any provider failure. For protocols with high TVL, we recommend a custom HA-proxy (nginx or Envoy) in front of two managed providers.

Why Is a Hybrid RPC Scheme More Cost-Effective Than Pure Managed?

At high request volumes, managed providers can be very expensive; a hybrid using a self-owned node as primary and a managed fallback cuts costs significantly without losing SLA.

Ethereum Node Clients

Execution clients: Geth (most used), Nethermind (C#, fast sync), Besu (Java, enterprise), Erigon (fastest sync, efficient archive mode ~2TB instead of 3TB).

Consensus clients (post-Merge): Lighthouse (Rust), Prysm (Go), Teku (Java), Nimbus (Nim). Each node after The Merge requires a pair of execution + consensus clients.

For DevOps: eth-docker — Docker Compose configurations for all client combinations. Setting up monitoring via Grafana + Prometheus is mandatory; a standard dashboard is available in each client's repository.

The Graph: Event Indexing

The Graph Protocol — decentralized indexing. A subgraph describes which events from which contracts to index and how to transform them into a GraphQL schema.

Subgraph structure:

• subgraph.yaml — manifest: contract addresses, startBlock, events to handle
• schema.graphql — GraphQL schema of entities
• src/mapping.ts — AssemblyScript event handlers

dataSources:
  - kind: ethereum
    name: UniswapV3Pool
    network: mainnet
    source:
      address: "0x88e6A0c2dDD26FEEb64F039a2c41296FcB3f5640"
      abi: UniswapV3Pool
      startBlock: 12370624
    mapping:
      eventHandlers:
        - event: Swap(indexed address,indexed address,int256,int256,uint160,uint128,int24)
          handler: handleSwap

AssemblyScript handlers — not TypeScript. No nullable types, no closures, no many standard APIs. An error in the handler stops the subgraph indexing on that transaction. Important: add try-catch for operations that can fail (e.g., store.get() for an entity that may not exist).

How to Avoid Subgraph Indexing Stops?

Graph Node logs are monitored in real-time; on hasIndexingErrors = true an alert fires and an automatic node restart (via systemd or Kubernetes). Typical downtime on error — 150–300 seconds to recover. Additionally, for production we set up a watchdog that restarts Graph Node if subgraph lag exceeds 50 blocks.

Choosing Between Hosted Service and Decentralized Network

Graph Hosted Service (free, centralized) is deprecated in favor of Subgraph Studio + Graph Network. For production: deploy on Graph Network with GRT curation signal — the subgraph gets indexers proportional to curation.

Alternatives to The Graph: Ponder (TypeScript, self-hosted, easier to debug), Envio (ultra-fast indexer, supports EVM + non-EVM), Subsquid (TypeScript, own network), Moralis Streams (managed, webhook-based). Our experience shows: for high-load projects with unique logic, Ponder or Envio are more effective — they give full control over the process and do not require GRT tokenomics.

Webhooks and Real-Time Notifications

Alchemy Webhooks and QuickNode Streams allow receiving events in real-time via HTTP webhook or WebSocket. For monitoring addresses, new transactions, mints — this is faster than polling RPC.

Tenderly — platform for monitoring and alerts. You can set up an alert for a specific contract event, balance change, function call with certain parameters. Transaction simulation via Tenderly API is invaluable for debugging.

Monitoring and Observability

Minimum monitoring stack for a protocol:

On-chain: OpenZeppelin Defender Sentinel — watches contract events, triggers webhook or Autotask when conditions are met. Forta Network — community-maintained bots detect anomalies (large withdrawals, flash loans, governance attacks).

Infrastructure: Grafana + Prometheus for nodes, Datadog or Grafana Cloud for managed metrics. Alerts on: node is 10+ blocks behind, RPC latency >500ms, subgraph lag >100 blocks.

Uptime: Better Uptime or PagerDuty on RPC endpoint and subgraph health endpoint (The Graph provides _meta { hasIndexingErrors, block { number } }).

Why Is Monitoring Without Tenderly Insufficient?

Tenderly provides transaction simulation and detailed traces — critical for debugging subgraph and smart contract errors. Forta focuses on network anomalies, not your infrastructure. The combination of Tenderly plus a custom Grafana dashboard covers 90% of incident scenarios.

Multichain Infrastructure

A protocol on 5 chains = 5 separate RPC endpoints, 5 subgraphs, 5 monitoring configs. Manageable but requires deployment automation.

For subgraph multi-network deployment: graph deploy --network mainnet, graph deploy --network arbitrum-one etc. with a unified codebase and network-specific addresses in separate config files.

Chainlink CCIP and LayerZero for cross-chain messaging require monitoring of both chains and transactions on intermediate relayers. A reorg on the source chain after a confirmed mint on the target chain is a classic bridge problem. Solution: wait for finality (on Ethereum ~15 minutes after Merge for economic finality) before confirming on the target chain.

Infrastructure Setup Process

1. Audit current stack — determine chains, request volume, latency and availability requirements.
2. Architecture design — select providers, load balancing, redundancy.
3. Subgraph development — manifest → schema → handlers → testing on local Graph Node → deploy to testnet → mainnet.
4. Monitoring configuration — Tenderly alerts, Grafana dashboard, PagerDuty integration.
5. Documentation and runbook — what to do when: subgraph falls behind, RPC downtime, node desync.
6. Handover to operations — team training, access transfer, first month support.

What's Included

• Deployment of managed or self-hosted Ethereum, Polygon, BNB Chain nodes
• RPC layer setup with primary/fallback and load balancing
• Subgraph development and deployment for your protocol
• Monitoring connection (Tenderly, Grafana, alerts)
• Runbook and operations documentation
• Team training (up to 4 hours online)
• 30-day support after delivery

Timeline

All projects are managed in a GitHub/GitLab repository with CI/CD; configuration code stays with you. Order infrastructure deployment — we'll show how to cut costs by 20–30% without losing reliability. Get a consultation — we'll demonstrate how we deployed infrastructure for a protocol with large TVL on Ethereum and Arbitrum. Contact us.