Independent operator on Pearl

We mine on Pearl and run one of the three guardians of Pearl Swap.

Pearl Swap is the bridge between native PRL on Pearl and PRL on Hyperliquid. Its funds move only when two of its three guardians sign. Ours checks every payment against its own Pearl node and its own reading of Hyperliquid before it signs. It cannot move anything alone, and neither can anyone else.

Our guardian, now Checking Configuration Checking Full status

Operator
Enderpearl, independent. Not part of Pearl Research Labs or Pearl Swap.
Guardian
t-mining. Its own record, read live
Threshold
2 of 3. Any two guardians can move the escrow: the native PRL on Pearl that backs the bridge’s PRL on Hyperliquid.
Networks
Pearl Swap and our guardian run on Pearl testnet2 and Hyperliquid testnet. Test networks only, for now.
c[5,10] = 7 = 1·2 + 2·2 + 1·(−1) + 0·(−2) + (−1)·(−2) + 1·2 + 1·0 + (−1)·2 C = A · B · A 12 × 8 · B 8 × 12 · entries −3 to 3 · seed 0x5EED (fixed until our guardian answers) · computed in your browser

Our guardian, live

from your browser · not read yet
Full status
Guardian Checking reading from your browser
Configuration — published ca7ec3a5…
Pearl height — the last Pearl block it has read from its own node, Pearl testnet2
Uptime — since —

What we run

Two jobs: we mine on Pearl, and we co-sign Pearl Swap’s payments. We say which guardian is ours, and its record is public.

Guardian · Pearl Swap

One of the three guardians of Pearl Swap

Every PRL the bridge releases on Hyperliquid is matched one for one by native PRL in an escrow on Pearl. Three guardians hold the keys to it. Any two can move it. One cannot, and that includes ours.

Our id
t-mining
Host
Enderpearl A, with its own Pearl full node, pearld
Keys
Three, made on its own server. Only the public halves leave it.
Our role in the 2 of 3
Mining · Pearl

Mining on Pearl, by useful work

Pearl's proof of work is matrix multiplication, the arithmetic of machine learning. Securing the chain and useful computation are the same act. We mine by doing that work.

C = A·B

We publish figures about our machines only when they are measured and public. There are none yet.

How Pearl's useful work works

How our guardian decides

enderpearl.ai/guardian#checks

It believes nothing it is told. Before it signs a payment, it runs eight checks against its own Pearl node and its own reading of Hyperliquid. These four ideas run through them.

  1. Checks 2, 4 and 5 of 8

    Its own view, its own numbers

    It confirms the source for itself, recomputes every amount from the agreed rules and rebuilds the Pearl transaction or Hyperliquid action byte for byte.

  2. Check 3 of 8

    Destinations from cryptography only

    A deposit pays the Hyperliquid account built into its deposit address. A withdrawal pays the Pearl address in the sender’s own signed request (EIP-712), which it checks against the transfer it saw itself. Never an address on the leader’s word.

  3. Check 6 of 8

    One payout per source

    It checks its own history and never signs two payouts for one source that could both execute.

  4. Check 8 of 8

    Intent before signature

    It writes down its intent to sign, and only then signs, so a crash cannot make it forget.

Any failure is a refusal with a reason, returned to the proposer and recorded. Refusals are normal: a guardian whose view lags refuses until it catches up.

All eight checks, in our words

Where things stand

dated facts only

Test networks only, for now. Nothing in the bridge runs on real networks yet, and the guardians refuse mainnet.

  1. Three operators, three servers

    Each operator set up its own server, its own Pearl node and its own keys.

  2. Our guardian on its own domain

    It answers over HTTPS, on our own domain, where the Status page reads it. How it is set up

  3. Configuration epoch 1 agreed

    One shared configuration for all three guardians. It adds the fee sweep and returns for small deposits, and removes the largest-payment and hourly caps.

  4. First payments, on test networks

    The first payments ran through the bridge on Pearl testnet2 and Hyperliquid testnet, using test PRL.

  5. A new shared configuration, still epoch 1

    It sets limits: 100 PRL a payment, 500 PRL in a rolling hour and 2,000 PRL in a rolling day. Deposits now wait for 12 Pearl confirmations before release. The fees are unchanged. Our guardian has accepted it.

    Configuration fingerprint · epoch 1 · published by Pearl Swap
    ca7ec3a5e73d8e728c3056726846a35455e3d7c180134910d21acca64913f25b
  6. Next

    An outside audit, before real money

    An outside audit of the guardian software comes before any real funds. Until then, the bridge runs on test networks only.

The trust assumption

Two of three keys. One is ours.

Any two of the three guardians can move the escrow. So two colluding guardians could move it. That is the assumption, and we state it plainly.

3 keys, named in the escrow script and on the treasury2 needed

Any two can move it

Two signatures from three named keys move the escrow on Pearl and the treasury on Hyperliquid. Every Pearl node enforces the escrow script. Hyperliquid refuses any treasury action without two, including from the key that created the account.

One cannot

Not us, and not anyone else. Each chain enforces the rule itself. All three guardians prepare every payout first, so one that is down holds up new payments. It never puts escrowed funds at risk.

So we disclose

The three guardians are run by Enderpearl, Deep Nacre and Pearl Swap, each on its own server with its own keys. Pearl Swap names all three, and our guardian's record is public.

Check it yourself

You do not have to take our word for the parts that matter. Read our guardian's own record, and check the keys and addresses where Pearl Swap publishes them.