A technical writer on our team needed screenshots of the admin dashboard. The dashboard is behind SSO login (Okta).

She asked me to help. I wrote a Playwright script with the login flow. It broke after the next Okta update. I fixed it. Then IT enabled MFA. Script broke again. I added TOTP handling. Then they rotated the client secret.

Three weeks of back-and-forth for 6 screenshots.

The problem

Most screenshot automation tools assume you can script the login. But modern auth is designed to resist automation:

• OAuth redirects across domains
• CAPTCHA challenges
• MFA (TOTP, push notifications, hardware keys)
• SSO providers that change their UI regularly
• Session cookies with short TTLs

You end up maintaining auth code that’s more complex than the actual screenshot capture.

Just log in yourself

Heroshot opens a real browser:

npx heroshot config

The technical writer logs in herself. Through Okta, with MFA, the whole thing. She does this every day anyway. Takes 15 seconds.

Then she clicks the elements she wants to screenshot. Heroshot saves:

1. The screenshot config (which pages, which elements)
2. The browser session, encrypted

Next time anyone runs npx heroshot, it restores the session. No login flow. If the session expires, she runs npx heroshot config --reset and logs in again.

For the CI pipeline

The session is encrypted with a generated key stored on your machine. To use it in CI:

# On your laptop
npx heroshot session-key
# Copy the key

# In GitHub Actions
env:
  HEROSHOT_SESSION_KEY: ${{ secrets.HEROSHOT_SESSION_KEY }}

steps:
  - run: npx heroshot

That’s it. CI decrypts the session and captures authenticated screenshots. No Okta credentials in CI. No login scripts. No DevOps engineer required.

Multiple accounts

Need screenshots from different user roles? Admin view, regular user view, read-only view?

Use separate config files:

# Log in as admin
npx heroshot config -c .heroshot/admin.json

# Log in as regular user
npx heroshot config -c .heroshot/user.json

Each config has its own session. Capture both:

npx heroshot -c .heroshot/admin.json
npx heroshot -c .heroshot/user.json

Who should take the screenshots?

The person who knows the product. That’s usually not the DevOps engineer writing Playwright scripts. It’s the technical writer, the product manager, or the designer.

With a visual picker, they don’t need to know CSS selectors, Playwright APIs, or how OAuth works. They log in and click.

From theory to production-ready patterns — traceability, selective disclosure, credentials, and reconciliation with actual runnable examples.

Most blockchain content for enterprises stays at the “hello world” or high-level architecture stage. Developers and architects need concrete patterns they can adapt to real regulated environments, consortiums, and future-proof security requirements.

That’s why I created enterprise-blockchain — a TypeScript repository packed with operational case studies, protocol-agnostic modules, and advanced crypto integrations.

It’s designed for developers who want to move beyond toy examples and start building production-grade enterprise solutions.

What This Repo Actually Gives You

• Four real business case studies with runnable examples
• Protocol adapters for Hyperledger Fabric, Besu (EVM), and Corda
• Security modules: Multi-Party Computation (MPC), Hardware Security Module (HSM) patterns, and Post-Quantum cryptography (ML-KEM / Kyber, ML-DSA / Dilithium, hybrid schemes)
• Fully typed, tested, and easy to explore

The focus is operational: how blockchain actually changes system behavior around auditability, provenance, privacy boundaries, and cross-organization coordination.

The Four Runnable Case Studies

1. Food Recall Response

   Simulate a contaminated batch recall across producers, distributors, and retailers. See how traceability can reduce response time dramatically.

2. Consortium Order Sharing

   Selective disclosure of purchase orders using privacy-friendly patterns (inspired by Besu privacy groups). Only the right parties see the details — others get verifiable proofs.

3. Hospital Staffing Clearance

   Credential verification and sanction-list checks. Critical for regulated industries like healthcare.

4. Aid Voucher Reconciliation

   Humanitarian aid settlement with automated exception reporting and strong audit trails.

Each scenario lives in its own examples/ folder and can be run with a single command.

Advanced Security That Goes Beyond Basic Signing

Security in enterprise blockchain isn’t just “use a wallet.” This repo includes practical implementations:

• MPC (Multi-Party Computation): Additive secret sharing, sealed-bid auctions, joint risk calculations, and quantum-resistant key sharing.
• HSM Patterns: PKCS#11-style key management, ECDSA transaction signing, 3-of-5 threshold root key ceremonies, and DEK/KEK envelope encryption.
• Post-Quantum Primitives: ML-KEM (Kyber), ML-DSA (Dilithium), and hybrid KEMs — because quantum threats are coming faster than many expect.

You can try them directly:

npm run example:mpc-auction
npm run example:hsm-tx-signing
npm run example:hsm-key-ceremony

Protocol Adapters — Write Once, Target Multiple Platforms

The core domain logic stays platform-agnostic, while clean adapters handle the differences:

• Hyperledger Fabric (using @hyperledger/fabric-gateway)
• Besu / Ethereum Enterprise (using ethers)
• Corda (REST gateway style)

There’s even a ready-to-use Solidity contract (ConsortiumOrderRegistry.sol) for quick EVM testing.

This approach lets you model business rules once and project them to different ledgers without heavy refactoring.

Quick Start (Literally 2 Minutes)

git clone https://github.com/psavelis/enterprise-blockchain.git
cd enterprise-blockchain
npm install

npm run typecheck
npm run examples

Then explore individual demos:

• npm run example:food-recall
• npm run example:order-sharing
• npm run demo:adapters
• npm run verify (runs lint + tests + formatting)

Everything works offline and includes quality gates via GitHub Actions.

Who Is This For?

• Enterprise architects and developers evaluating Fabric, Besu, or Corda
• Teams building consortium solutions with privacy and compliance needs
• Security engineers interested in MPC + HSM + post-quantum in TypeScript
• Anyone tired of blockchain tutorials that never reach real operational patterns

If you’re working on (or planning) enterprise blockchain projects, this repo can save you weeks of research and experimentation.

⭐ If you find this useful, please star the repository — it helps more developers discover practical enterprise patterns instead of just hype.

👉 https://github.com/psavelis/enterprise-blockchain

Contributions are welcome! New case studies, additional protocol adapters, improved docs, or security examples are especially appreciated. Just run npm run verify before opening a PR.

What’s Next?

I’d love to expand this with more real-world scenarios. What enterprise use case would you like to see implemented next?

Drop a comment below:

• Your biggest pain point when working with enterprise blockchain
• Which platform (Fabric, Besu, Corda, or others) you work with most
• Whether you’d like a deep-dive on MPC or post-quantum integration

Let’s make enterprise blockchain more practical and production-ready together.

showdev #blockchain #typescript #hyperledger #enterprise #opensource #cryptography