OPEN RECOVERY INFRASTRUCTURE / POWERED BY ARKIV

Stay reachable.
Even when your website isn't.

When a website goes down, trust shouldn't disappear with it. RelayLine helps people find publisher-signed backup routes directly from Arkiv, without relying on the original website.

No wallet needed to read recovery routes. Publishing requires wallet approval.

Publisher-attributedRecords tied to a signing wallet
Independently readableNo RelayLine application backend required
Time-aware recordsExpiry and revocation are checked
THE SYSTEM, EXPLAINED

A little redundancy.
A lot more resilience.

RelayLine separates publishing from discovery so people can still find an authorized route when the original service is unavailable.

01 / PUBLISH

Create a recovery record

In your wallet-connected workspace, register a primary website and an alternate HTTPS address. Publishing happens only after you approve a testnet transaction.

02 / VERIFY

Pin the actual publisher

Readers independently establish which wallet to trust. A service name or shared recovery link alone isn't proof of ownership.

03 / REDISCOVER

Find the authorized route

The reader queries Arkiv directly, checks current record authority and presents available evidence without inventing live-uptime guarantees.

TRUST IS EXPLICIT

Recovery you can inspect.
Not just take on faith.

RelayLine uses public, wallet-attributed Arkiv records and an independent reader. Monitor observations may be missing or disputed, backups can fail, and this testnet prototype is not a security-audited availability guarantee.

Explore the protocol and security model
Identity firstReaders pin an independently authenticated publisher wallet
Explicit authorizationExpiry, rotations and revocations are checked
Visible limitationsRecord authenticity does not guarantee site reachability
YOUR CONTINUITY STARTS HERE

Keep a trusted route discoverable.

Manage the services you publish, or look up a publisher's signed recovery record.