TechnologyBlockchain

    Blockchain engineering, from bank networks to public chains

    Short answer

    We have built on blockchains since 2016: permissioned networks that banks and regulators run (Quorum, Hyperledger Besu), a bank-backed stablecoin design in cooperation with Visa, app-specific chains on Cosmos SDK and Avalanche, smart contracts on Ethereum and EVM chains, SDKs for a layer 2 network, and the nodes, monitoring and APIs around them. We also operate what we build.

    At a glance
    PermissionedQuorum · Hyperledger Besu
    PublicEthereum · EVM chains · TON · Cosmos SDK
    App chainsAvalanche subnet · Cosmos SDK with IBC
    Since2016

    How a project runs

    Blockchain: from question to running system

    Your pathEach step ends in a written result
    1. 01Use casewho trusts whom · what goes on-chain
    2. 02Chain choicepermissioned or public · validators
    3. 03Contracts and servicescontracts · APIs and indexers
    4. 04Securitythreat model · audit
    5. 05Operatenodes · monitoring

    What we build

    Bank and regulator networksA permissioned Quorum network on AWS that has issued and verified 3M+ documents for a bank, and a Hyperledger Besu network with validators at six regulators and institutions for a national payment network.
    Stablecoins and digital assets for banksA bank-backed stablecoin pegged to the central bank digital currency, on AssetBridge, our banking asset-management layer, designed in cooperation with Visa.
    App-specific chainsAn Avalanche subnet we operate for an AAA free-to-play game, and a Cosmos SDK chain with inter-chain messaging for a Web3 game with over 100,000 players a day.
    Smart contracts and tokensSolidity contracts for title registries, auctions, lending, staking and governance; token design with staking, slashing and reputation; ports across EVM chains.
    SDKs and APIszkSync SDKs in five languages, and our own Blockchain API that tracks transactions, delivers callbacks and manages token contracts for internal systems.
    Identity and trustDecentralized identifiers and verifiable credentials, e-voting, proof of location, and document authentication on permissioned chains.

    Stack

    Technologies we use

    Permissioned
    Quorum, Hyperledger Besu, private proof-of-stake Ethereum networks
    Public and app chains
    Ethereum, Polygon, BSC, Avalanche (C-chain and subnets), Fantom, Harmony, IoTeX, Cosmos SDK and IBC, TON, EOS, Casper
    Contracts
    Solidity, CosmWasm; auctions, lending, staking, escrow, registries, token economics
    Back end
    Rust, Go, Java and Spring with Web3J, Node.js, Python
    Operations
    Validators and nodes, monitoring for servers, nodes and services, AWS, Docker, Kubernetes
    Controls
    Delivery under ISO 27001, ISO 27017, PCI DSS and NIST SP 800-53 environments of our clients

    Proof

    Delivered work

    All work
    Case · Banking · Central Asia

    Bank-backed stablecoin layer, with Visa

    Problem
    A Visa partner bank wanted crypto inside its own products.
    Built
    Business case review and a stablecoin design on AssetBridge.
    VisaStablecoinCBDCBank-issued stablecoin
    Phase 1 accepted; phase 2 approved, pending regulator.
    Case · Banking · Middle East

    Document authentication on a permissioned chain

    Problem
    A bank needed documents verified without office visits.
    Built
    A Quorum network on AWS, built and operated by Vareger.
    QuorumPermissioned blockchainDocument authenticationAWS
    Runs inside ISO 27001 and PCI DSS controls.
    Case · National payments

    National blockchain processing and tokenization

    Problem
    A national payment network needed its own processing.
    Built
    Hyperledger Besu chain, processing centre and fee engine.
    Scale
    Validators at six regulators and institutions
    Hyperledger BesuTokenizationPayment processingPermissioned blockchain
    Live transactions and new tokenized product lines.
    Case · Gaming · Global

    Blockchain layer for an AAA free-to-play game

    Problem
    On-chain items, without players dealing with the chain.
    Built
    Middleware, an Avalanche subnet and item contracts.
    Avalanche subnetMiddlewareOn-chain itemsSmart contracts
    Runs in production, operated by Vareger.
    Case · Gaming · Global

    App-specific chain for a Web3 game

    Problem
    A game needed its own chain for all in-game finance.
    Built
    A Cosmos SDK chain with inter-chain protocol and contracts.
    Cosmos SDKIBCApp-specific chainSmart contracts
    The chain ran all in-game finance of the live game.
    Case · Layer 2 · Global

    zkSync SDKs in five languages

    Problem
    Every integrator needed an SDK in the language it uses.
    Built
    Go, Python, Rust, Android and iOS SDKs, built and maintained.
    zkSyncEthereum layer 2SDKGo
    zkSync docs credit Vareger as the SDK author.

    FAQ

    Questions buyers ask

    Q01Permissioned or public chain?

    Permissioned when the participants are known and a regulator or bank must control who validates, as in our bank and national network work. Public when users and assets must move freely, or when you want anyone to verify the record.

    Q02Do you operate the networks you build?

    Yes, where the client wants it. We still run the bank document network we built in 2018 and the Avalanche subnet behind an AAA game.

    Q03Can you work on an existing code base?

    Yes. Several of our engagements started with a review of existing contracts and services, the gaps between the business and the technical design, and then fixes or new features.

    Q04Do you audit smart contracts?

    We review and test our own contracts and work with independent audit partners for formal audits.

    Next step

    Working on blockchain?

    A 30 minute call with Mykhailo. You leave with a clear view of scope, risks and next step.

    Mykhailo Tiutin

    CTO, Vareger

    Mykhailo Tiutin, CTO, Vareger