PSPratyush Shivam

A permissioned network, in production

An Ethereum-compatible network between known companies, run with the same discipline as any other production system.

01 · Context

Freight is business between known companies

Shippers know their forwarders. Forwarders know their carriers. What the industry lacks is not identity, but a single version of the truth.

02 · Challenge

Trust without exposure

Rates, lanes and customer lists are competitive data. A public ledger, visible to everyone forever, works against the grain of the business.

03 · Thinking

Visibility by design

On a permissioned network, each party sees what its role allows and nothing more. Costs are predictable, and there is a clear answer to who can see what.

04 · Engineering

Operated, not just deployed

I designed and run the network layer: onboarding participants, permissioning, monitoring and upgrades, alongside containerised services with automated build, test and release pipelines.

05 · Result

Invisible to the people using it

A dispatcher sees "approved". A carrier sees "paid". Nobody on the platform needs a wallet or has to think about a chain.

06 · What I learned

Production is the real test

Designing a network is one challenge. Running it reliably every day is another, and it is the one customers notice.

Film

One network

Connect once, work with everyone. A thirty-second explanation of the idea behind this work.

Details are described at the level of problem and approach. Implementation specifics stay with the company.