Operator
Remove the weakest link, then remove the next
OKcontract Labs advances research in verifiable interfaces, transaction security, and resilient software.
- We make critical operations inspectable and enforceable even when an interface, backend, or administrator fails.
- Our long-term view is that blockchains can become a fortified execution layer for onchain actions first, and eventually for critical operations across the internet.
A cloud account can edit the rule that decides who may act.
Choose a weak link
Chainwall
Approve what should happen. Execute only that.
Treasury, protocol, vault, and smart-account teams define who can act, which contracts and assets they can use, and what approval each action requires. Chainwall stores those settings in contracts and reads the current state again at execution.
The submitted function, arguments, value, deadline, operator, and account must match the approved action before a protected account calls the protocol. Smart contracts make the final decision. Cells powers the console's live application state. LambdaScript is the typed authoring layer for formulas and programs. MiniScript is the compact onchain workflow language that Chainwall executes.
Explore ChainwallStatic app
The console builds the request locally
A static browser app can read contract state and prepare calls without a backend deciding what the team has approved.SDK or bot
Let approved automation propose or run actions
Scripts and bots can propose or execute actions under the same onchain registry, policies, and protected accounts as human operators.Approved catalog
Define precisely what is allowed
Create trusted, programmable onchain action templates for protocol calls, transfers, governance actions, and vault operations.Live approval rule
Chainwall checks who approved this exact action
Current group membership and thresholds must satisfy the approval rule tied to the submitted operation.Allowed calls
Resolve only allowlisted contracts
A reusable workflow verifies if contracts are allowlisted in the registry and rejects a missing or substituted destination.Protected account
Block paths that skip the checks
A guarded Safe or purpose-built Chainwall smart account accepts the approved execution path and rejects unsupported direct calls.Approved destination
The protocol call finally runs
Execution reaches the approved target only after the operation, current rules, workflow, and account path agree.Cells
Async state is a graph. Write it that way.
Cells is the 10 kB TypeScript dataflow runtime behind our products, starting with Chainwall. A Sheet connects writable and computed values, waits for promises, propagates errors, ignores obsolete results, and follows dependencies that change at runtime.
Change either value.
Cells waits 620 ms after typing stops, then resolves the sum after 240 ms. The last stable result remains readable while the next one runs.
Published after the graph settled
debouncer(620) → delayed(a + b, 240)LambdaScript
Turn a formula into a live, typed part of your application.
LambdaScript is the core language for customizing Chainwall policies and interactions. It compiles formulas written by users or loaded from configuration into Cells, so each result stays connected to every input that can change.
Compiling the expression into Cells…
Start with the call that must be allowed
A security claim is useful when another team can inspect the rule, reproduce the test, and see what remains outside the check.
- 01
Write down the exact call.
Name the contract, function, arguments, value, account, deadline, and the person or program allowed to request it.
- 02
Put the decisive check near execution.
Use deterministic code or a smart contract so an interface, backend, or operator cannot replace the approved call before it runs.
- 03
Publish what passed and what remains.
Share the tests, assumptions, and known failures. Name every person, service, contract, and dependency that users must still trust.
Start with the failure. Follow it to the code.
Incident reports trace what failed. Engineering notes show what we built, how it behaves, and where its guarantees stop.
NVIDIA Inception
Protocol Labs
LongHash Ventures
Sparkle Ventures
Optimism
Starknet
Compound
NVIDIA Inception
Protocol Labs
LongHash Ventures
Sparkle Ventures
Optimism
Starknet
Compound
