Overview

Resource Locks are OneBalance’s innovative solution to the inherent latency in cross-chain transactions. It enables cross-chain transactions to execute at the speed of the destination chain, regardless of source chain finality times.

How Resource Locks Work

Resource Locks are managed by OneBalance’s RL Service, which performs four critical functions:

1

Verifies

Validates user on-chain and locked balances

2

Co-signs

Adds signatures to operations, ensures control over account state transition and prevents double-spending

3

Provides Guarantees

Issues security attestations to solvers for immediate delivery, given delayed settlement

4

Tracks Positions

Ensures not yet settled balance follows risk policies to maintain system integrity

This system enables asynchronous execution where intent fulfillment is separated from settlement, dramatically improving user experience.

Evolution of Cross-Chain Bridging

Classical Bridge

Critical Path:

Source chain finality + Destination chain inclusion

Typical Duration:

3 minutes or more

Intent Bridge

Critical Path:

Source chain inclusion + Routing + Destination chain inclusion

Typical Duration:

15-45 seconds

RL-enabled Bridge

Critical Path:

Lock verification + Routing + Destination chain inclusion

Typical Duration:

5-10 seconds

Classical Bridge: Source Chain Finality + Destination Chain Inclusion

Traditional bridges require waiting for source chain finality before processing on the destination chain, resulting in significant delays.

Intent Bridge: Solver Assumes Finality Risk

Intent-based bridges improve speed by having solvers take on the finality risk, but still require source chain inclusion.

Fast Intent Bridge: Lock Provider Eliminates Double-Spend and Finality Risk

OneBalance’s Fast Intent Bridge achieves near-instant cross-chain execution by removing both double-spend risk and finality waiting times through Resource Locks.

Types of Resource Locks

Resource Locks fall into two main categories:

  1. Account-based locks - Locks are implemented at the account level, allowing seamless compatibility with existing user flows and wallet interactions.
  2. Escrow-based locks - Instead of locking accounts, this approach implements an escrow smart contract where users deposit tokens for cross-chain operations.

Currently, OneBalance primarily uses account-based locks for optimal user experience and compatibility.

Once Resource Lock is enabled, transactions can be sent only via OneBalance Toolkit, as otherwise it is impossible to prevent the double-spending in asynchronious execution environment.

For detailed integration instructions, see our Getting Started guide.