Skip to content

Know the risk. Own the next move.

Risk management for Web3 teams. Bring asset exposure, operational controls and the decisions behind them into one reviewable record.

For treasury, security, finance and operations.

Know your exposure.
Bring wallets, venues and dependencies into one view of what could go wrong.
Give controls an owner.
Connect limits, approvals and exceptions to the people responsible for them.
Keep the reasoning.
Carry evidence and decisions forward into the next risk review.

A SHARED VIEW OF RISK

From scattered signals to clear ownership.

A wallet balance is only part of the story. Connect what you hold, the controls around it and the people responsible for the next decision.

risk.registerILLUSTRATIVE WORKSPACE

Exposure

01
TREASURY

Wallet concentration

Where assets are held

DEFI

Protocol dependency

What operations rely on

Controls

02
OPERATIONS

Approval policy

Who can authorize a move

SECURITY

Custody workflow

How access is managed

Review

03
RISK

Decision memo

Why a decision was made

FINANCE

Treasury update

What the team needs to know

Exposure identifiedControl assignedDecision recorded

An illustration of the workflow, using example records.

CLOSE TO REAL OPERATIONS

The context behind every asset move.

Bring exposure, controls and risk memory together so the team can work from the same record.

01 / EXPOSURE

Assets and dependencies

Understand where assets sit and which relationships the team relies on.

Wallets · Venues · Protocols · Counterparties
02 / CONTROLS

Policies close to the work

Give approvals, custody processes and exceptions a clear place in day-to-day operations.

Limits · Approvals · Custody · Escalation
03 / RISK MEMORY

Decisions you can explain

Keep the alert, its owner and supporting evidence together through review and reporting.

Alerts · Mitigations · Evidence · Decision records

THE RISK WORKFLOW

Identify. Control. Review.

Give each signal an owner, a response and a next review. Keep the process clear before markets move.

  1. 01

    Map the exposure

    Name the assets, counterparties and operational dependencies. Give each risk a place in the register.

  2. 02

    Define the control

    Set the threshold, approval path, responsible owner and review cadence before activity grows.

  3. 03

    Review and record

    Follow alerts and exceptions through a decision. Keep the mitigation and evidence with the record.

A RECORD WORTH COMING BACK TO

Keep the why with the decision.

Make a risk review useful to the next person. Keep the original signal, the applicable control and the team's reasoning in view.

AN EXAMPLE REVIEW

A concentration signal needs a decision.

One record connecting treasury, operations and risk.

01 / THE SIGNAL

Exposure at a single venue

Observation
A larger share of treasury assets is held at one venue.
Owner
Treasury, with operations and risk review.
Control to check
The team's concentration policy and approval path.
Evidence to gather
Exposure breakdown, liquidity context and existing commitments.
02 / THE REVIEW
  • Understand the exposureCheck the position and the dependencies behind it.
  • Agree the responseRecord the proposed mitigation, owner and required approvals.
  • Preserve the decisionAttach the reasoning and set the next review.
A decision with its context.

Ready to revisit in a team review or leadership report.

Illustrative workflow. Not live account data or a customer result.

A FEW USEFUL ANSWERS

Before your next risk review.

What is Rmkit?

Rmkit is a risk management tool for Web3 teams. It brings digital asset exposure, operational controls and risk decisions into a clearer review workflow.

Who is it designed for?

Digital asset teams working across treasury, security, finance and operations, who need a shared account of what they hold, how it moves and who owns each risk.

What kinds of risk does it cover?

The product focuses on wallet and venue exposure, protocol and counterparty dependencies, approval and custody workflows, and the alerts and exceptions that need a team decision.

What belongs in a risk record?

The exposure, responsible owner, applicable control, supporting evidence, decision and next review. Keeping these together makes the reasoning easier to revisit and report.

Is the example on this page live data?

No. The register and review example illustrate the operating model. They do not show a live account, connected wallet or customer result.

How can I find out about access and integrations?

Get in touch to discuss your team's workflow and ask about current availability, pricing and supported integrations.

START WITH YOUR OPERATIONS

Less scattered context. Clearer next steps.

Tell us where your team loses sight of exposure, where approvals get difficult and what a better risk review would look like.

Talk about Rmkit Rmkit at Yiplex

Get in touch about your workflow and current availability.