Smart Contract Engineer

Blockchain Lab analysis

Frameworks other people will import: architecture, audit, release, and the prototypes that sit next to the protocol.

It does not own Infernet's off-chain provers, the client, or the company's next round. A library engineer who cannot name the pause and upgrade paths will not survive the interview the posting describes.

Blockchain Lab analysis

Public reporting and the employer’s own releases. Not a relationship with Blockchain Lab. Not a credit opinion.

Founded

2023

Base

Distributed. No single headquarters is stated on the roles we store.

Status

Private. No token price, circulating supply, or revenue is treated as a fact in this brief.

People

A January 2025 secondary profile put the team near 30. That number is not current headcount.

1. 8 Nov 2023

   Seed, announced by the lead

   $25 million

   Archetype posted that it was leading Ritual's $25 million round. Blockworks called it a seed. Named participants in that coverage include Accomplice and Robot Ventures. Preqin also lists dao5, Anagram, Hack VC, and Dialectic. Some later blogs mislabel this round a Series A.

2. March 2025

   Series A, database-reported

   $25 million, unconfirmed here

   Preqin records a further $25 million with Accel, Avra, Hypersphere, and Polychain as new names, plus returning funds. This dossier did not find a Ritual press release for that round. Treat it as a database entry until the company confirms it.

• Runway and round status are not something you can read in a filing. Private company, one confirmed round.
• Mainnet, token, and fee switch are not facts this dossier will assert. The job text sometimes says mainnet. That is the employer's word. Ask what is actually in production.
• Stale reqs. The smart-contract posting was last updated on the board on 24 July 2024.
• The category is crowded and narrative-heavy. A coprocessor that cannot show a paid workload is a research project with a payroll.

Ask them

• Which round is the company actually operating on, and is the March 2025 Series A closed?
• What is live: Infernet, a testnet, a mainnet, a token? Who pays for inference today?
• Why has this specific req not been updated, and who would you report to?
• What is the public status of the Polychain / Eclipse matter?
• Is the role worldwide remote, or remote inside a list of countries the posting never names?

• Archetype announcement, 8 Nov 2023
• Blockworks seed coverage, Nov 2023
• Preqin asset profile, including the reported 2025 round

If a figure is not in those sources, it is not in this brief on purpose.

Illustrative preparation

Not the employer’s onboarding plan.

1. Days 1–30: map what is already open source against what the posting claims you will own. Write the gap down.
2. Days 31–60: one release, however small, with an audit note and a migration. Shipping cadence is the only evidence the req is real.
3. Days 61–90: a prototype beside the protocol team that fails closed when inference does not return. Document what you refused to abstract.

A week you can rehearse

• Read the contracts the way an integrator calls them. List every admin, pause, and upgrade.
• Diff one release the company has already shipped, if one is public. If none is public, that is the finding.
• Write the unhappy tests the posting implies: a bad proof, a replay, a partial return from the coprocessor.

Illustrative preparation

• Walk an upgrade through a proxy. Say who can brick the funds.
• Explain why a proof verification on an L2 is not the same gas and trust story as on L1.
• Show a repository. A description of 'familiarity with Foundry' is not a library.

Proof you can build before you apply

• A small registry with roles, a pause, and tests, on synthetic assets. The lab on this desk is that exercise. It does not prove you can audit Ritual's code. It proves you can show an unhappy path.

Open Controlled asset registry. A local registry with roles, a pause, and tests. Synthetic assets only.

• Canon
• Asset registry blueprint
• ABI tools

• The hiring manager cannot say what is in production.
• They will not discuss the founder's Polychain matter at all, even to say it is closed.
• The offer is options at a valuation they will not describe, and the posting is still the July 2024 text.

Employer stated. Ritual is hiring someone to own open-source contract libraries: design, audit, release, and prototypes next to the core protocol.

• Building and maintaining core smart contract frameworks and libraries
• Managing smart-contract release lifecycles; from architecting to audit to post-release
• Spearheading research into novel smart contract functionality beyond the EVM
• Collaborating with a cross-functional team of engineers, designers, researchers, product managers, and operations teammates to create best-in-class products
• General mastery of software engineering principles

Source: the employer’s public Greenhouse record, job 4135728007. Open the original. First seen by this desk 2026-10-06. Nothing above the fold is a substitute for that page.

Blockchain Lab analysis. These lines are a reading of the advertisement. They are not extra hiring requirements.

• Read the contract the way an integrator will call it, not the way the README describes it.
• Trace pause, role, and upgrade paths before treating a transfer as final.
• Write tests for the unhappy path: replay, stale oracle, and a partial fill.

• Compensation, unless a figure appears in the header. None of these eighteen postings stated one.
• Closing date, and the day the role was first published. The board timestamp is an update.
• Which countries may apply. “Remote” alone is not worldwide eligibility. If the employer wrote “worldwide”, that sentence is theirs — still ask which entity can hire you.
• Visa sponsorship, on-call, and the employing subsidiary.