SHRASIT Solutions
Services · Blockchain · Smart contracts

Smart contracts and distributed ledgers shipped into production for governments, oil and gas, banks and supply chains. Ethereum, Hyperledger Fabric, R3 Corda and Hashgraph, audited, formally tested, and integrated with the SAP, Maximo and HIS estates we already implement next door.

Block stream · permissioned ledger

Five blocks. One audit trail.

Block #1024

0xa3f10…9b4c

tx

12

Block #1025

0xa40d7…9b9b

tx

19

Block #1026

0xa429e…9bea

tx

26

Block #1027

0xa4465…9c39

tx

33

Block #1028

0xa462c…9c88

tx

40

Finality< 2.0s
Networks shipped to production
0
Smart contracts under audit
0
Lines of Solidity / Go reviewed
0
Avg. audit findings per kLoC
3.2

Honest scoping

When blockchain is the answer, and when it isn’t.

Most blockchain programs that fail in production were the wrong tool from day one. We start every engagement with this conversation, not a slide deck.

Blockchain wins

  • Multiple parties write to a shared record and none of them trusts the others' database.
  • Provenance and tamper-evidence have a regulator or a court at the end of the chain of custody.
  • Settlement and reconciliation across organizations is currently a four-week month-end ritual.
  • Tokenized assets need atomic transfer with built-in compliance and audit trail.
  • Devices, sensors or AI agents need to transact on behalf of humans without an intermediary.
  • Cross-border participants need a neutral substrate and no single operator should hold the keys.

A database wins

  • One organization owns the data and the workflow end-to-end.
  • The dataset is mostly read-heavy and a signed audit log gives you what you need.
  • Latency budget is sub-100ms and throughput is in the millions of TPS range.
  • The dataset is private, regulated and must be deletable on request (GDPR right to erasure).
  • Disputes are resolved by a single regulator who already trusts the operator.
  • Off-chain integration cost would dwarf the integrity guarantee blockchain adds.

Where it ships

Six places we have shipped blockchain into production.

Each one is a real program, not a slide. Pick the closest pattern and we will bring the team that has built it before.

  • Public sector

    Government registries & identity

    Land titles, business registries, professional licenses and self-sovereign identity. Tamper-evident audit trail backed by ministry-level attestation, with citizen-facing wallets that work on a feature phone.

    Platforms

    Hyperledger FabricHyperledger IndyEthereum (permissioned)
    Industry context
  • Supply chain

    Provenance & trace

    Track raw materials, components and finished goods across multi-party supply chains. Lot-level traceability with on-chain custody events, off-chain document anchoring and recall in minutes, not days.

    Platforms

    Hyperledger FabricR3 CordaEthereum L2
    Industry context
  • Smart city

    Credentials & permits

    Verifiable credentials for residency, parking, building permits and utility connections. W3C-compliant DIDs and selective-disclosure proofs so a citizen never has to over-share.

    Platforms

    Hyperledger IndyEthereumPolygon ID
    Industry context
  • Oil & Gas

    Custody-of-asset & hydrocarbon flow

    Lease-allocation, custody transfer and hydrocarbon accounting tied to IoT meters at the wellhead. Joint-venture partners reconcile against the same ledger instead of re-keying each other's spreadsheets.

    Platforms

    Hyperledger FabricR3 Corda
    Industry context
  • Financial services

    B2B settlement & trade finance

    Inter-bank settlement, letters of credit, factoring and invoice finance on a permissioned ledger. Atomic delivery-versus-payment with built-in KYC, sanctions screening and reg reporting.

    Platforms

    R3 CordaHyperledger FabricHashgraph
    Industry context
  • Logistics

    Cold-chain & cross-border freight

    Container-level temperature, shock and chain-of-custody anchored to an immutable ledger. Insurance and customs accept the evidence pack without back-and-forth on the email thread.

    Platforms

    Hyperledger FabricEthereum L2
    Industry context

Platforms

Four platforms. Picked per program, not per fashion.

Our engineers have shipped to all four in production. The choice is driven by participants, regulator, throughput and key-management posture, not by what is trending.

EthereumPlatform

Public-chain reach with EVM tooling.

Public mainnet, L2s (Arbitrum, Optimism, Base, Polygon) and permissioned EVM forks. Default for tokenized assets, DeFi-adjacent settlement and any program where third-party wallets matter.

Largest dev ecosystemERC-20/721/1155 standardsL2 scaling and account abstractionSolidity / Vyper

Typical use case · Tokenized assets, public registries, B2C credentials.

Hyperledger FabricPlatform

Permissioned, modular, enterprise-grade.

Linux Foundation backed, channel-based privacy, pluggable consensus and smart contracts in Go, Java or Node.js. Default for consortium ledgers where membership is the whole point.

Channels for data isolationPluggable ordering serviceMSP-based identityGo / Java / Node chaincode

Typical use case · Government registries, supply-chain trace, custody-of-asset.

R3 CordaPlatform

Built for regulated finance.

Privacy-first design, no global broadcast, point-to-point messaging between parties to a transaction. Default for inter-bank settlement, capital markets and trade finance.

Need-to-know data sharingNotary-service finalityKotlin / Java contractsBuilt-in KYC primitives

Typical use case · Inter-bank settlement, syndicated lending, trade finance.

HashgraphPlatform

DAG-based throughput, asynchronous BFT.

Hedera's public network and private deployments. Sub-second finality, high throughput, fixed and predictable fees. Default for high-volume micropayment and audit-log workloads.

10k+ TPS sustainedFair ordering by consensus timestampPredictable, stable feesSolidity via HSCS

Typical use case · Audit logs, high-volume settlement, data-integrity feeds.

Delivery method

Five steps from contract idea to mainnet operate.

The same shape every program follows. No deploy without an external audit. No operate without a runbook the on-call engineer can actually execute at 3am.

  1. 01

    Discover

    Two-week diagnostic. Decide whether a chain is the right answer at all, and if so, public vs permissioned, on-chain vs off-chain, and the participating parties' onboarding bar.

    Tooling

    • Use-case canvas
    • Threat model v0
    • Regulatory mapping
  2. 02

    Model

    Data, identity and transaction model. Who writes, who reads, who notarizes. Token economics, governance, key-management posture and exit strategy if a participant leaves.

    Tooling

    • State diagrams
    • Token spec
    • Key-management plan
  3. 03

    Build

    Smart contracts, off-chain services and integration into your existing systems of record. CI with property-based tests, fuzzing and gas-profiling on every PR.

    Tooling

    • Hardhat / Foundry
    • Fabric / Corda SDKs
    • Slither / Mythril
  4. 04

    Audit

    Internal review, then a named third-party audit. Findings tracked publicly for open-source contracts, privately under NDA for enterprise. No production deploy without a clean report.

    Tooling

    • Foundry invariants
    • Echidna fuzzing
    • Third-party firms
  5. 05

    Operate

    Run the network. 24/7 node operations, key rotation, governance proposals, incident response and quarterly re-audits when contracts change. Metrics that page humans, not bots.

    Tooling

    • Datadog / Grafana
    • HSM / KMS
    • Runbook drills

Security & audit

The boring parts that keep capital on chain.

Smart contracts are unforgiving. We treat audit, threat modelling and key management as first-class engineering, not a checkbox at the end.

Formal verification

Critical invariants proven with Certora, KEVM or Foundry invariant tests, not just unit tests on the happy path.

Third-party audit

Independent audit firms engaged before mainnet. Findings remediated, re-tested and published or filed under NDA, your call.

Threat modeling

STRIDE per contract, plus chain-specific threats: re-entrancy, oracle manipulation, MEV, governance capture, bridge spoofing.

OWASP for smart contracts

Coverage of the OWASP Smart Contract Top 10: access control, arithmetic, unchecked calls, DoS, time manipulation, frontrunning.

Key management

HSM-backed signing, threshold schemes for multi-sig, ceremonial key generation for genesis, rotation runbooks rehearsed quarterly.

Upgrade & rollback

Proxy patterns where appropriate, immutable where it shouldn't be. Pause switches and migration paths designed before the first deploy.

Audit trail

Six gates, every program

  1. Stage 01

    Genesis

    Threat model, key ceremony and proxy / governance design signed off before line one of contract code.

  2. Stage 02

    PR-time

    Slither, Mythril and Foundry invariants run on every pull request. Gas regressions blocked at the gate.

  3. Stage 03

    Internal

    Two-engineer review pass. Property-based and fuzz tests across the surface area, not just the happy path.

  4. Stage 04

    External

    Independent audit firm. Findings classified Critical / High / Medium / Low with public or NDA report.

  5. Stage 05

    Mainnet

    Staged rollout with circuit-breakers, monitored TVL caps and bug-bounty live from day one.

  6. Stage 06

    Operate

    Quarterly re-audit when contracts change. Public post-mortems for any P1 incident, no exceptions.

Tech stack

The languages and tools we ship with.

Polyglot by necessity. Solidity and Vyper for EVM, Rust for performance-critical paths, Go and Java for Fabric chaincode, Kotlin for Corda, TypeScript and Node for everything that touches a wallet or a UI.

Solidity
Vyper
Rust
Go
Kotlin
Java
TypeScript
Node.js
Hardhat
Foundry
Truffle
Ganache
Anvil
Slither
Mythril
Echidna
Certora
OpenZeppelin
Ethers.js
viem
Web3.js
Hyperledger Fabric SDK
Corda SDK
Hedera SDK
IPFS
The Graph
Chainlink
Polygon
Arbitrum
Optimism

FAQ

Five questions worth answering honestly.

  • Public chain or private chain — how do you decide?

    Public if the participants don't need permission to read or transact and you want third-party wallet ubiquity. Permissioned if regulator, residency or commercial-confidentiality constraints make pseudonymous public participation unworkable. Most enterprise programs we ship are permissioned Fabric or Corda, with a public-chain anchor for tamper-evidence where useful.

  • How do you handle gas fees and unpredictable cost?

    On EVM L1 we design for batch operations and meta-transactions, and we move chatty workloads to an L2 (Arbitrum, Optimism, Polygon) or a Hashgraph-backed feed where fees are predictable. For permissioned chains, gas is non-issue, the cost model becomes infrastructure, not transaction fees.

  • What about regulatory exposure — securities, MiCA, RBI, SAMA?

    We map jurisdiction at the discovery phase. Token engineering is done with counsel, not after. We have shipped programs under SAMA, CBB, RBI and MAS oversight, and we won't deploy anything to mainnet without a written sign-off from your legal and compliance leads.

  • When do you actively recommend NOT using blockchain?

    When the workflow has a single accountable owner, when GDPR right-to-erasure conflicts with on-chain immutability, when latency or throughput needs are outside what any chain delivers, or when the integrity benefit is smaller than the integration cost. We have walked away from engagements on this basis. A signed audit log on Postgres is the right answer more often than the market admits.

  • Can you integrate blockchain with our existing SAP / Oracle / Maximo estate?

    Yes. That is most of what we do. Smart contracts rarely live alone, they sit beside ERP, IWMS, EAM and HIS systems we already implement. Off-chain adapters, event-sourced sync, idempotent writers and reconciliation jobs are the boring parts that decide whether a blockchain program survives its first quarter in production.

Related practices

Talk to sales
Partner with us
Join the team