Test networks only, for now Pearl Swap and our guardian run on Pearl testnet2 and Hyperliquid testnet. No real funds move through the bridge yet.
Status · Node A
GET guardian.enderpearl.ai/status · /operations
Enderpearl A is our guardian host: a Pearl testnet2 full node plus the guardian. Your browser asks it directly when this page opens, then every 30 s while this tab is visible. We relay nothing and fill in nothing. Where it does not answer, you see dashes.
Enderpearl A
EP-A · guardian host
C = A·B · the pearl marks one cell · seed 0xE61C until our guardian answers
Not read yet
This panel reads our guardian from your browser.
The browser could not complete the request.
No figure is shown in place of its answer. Everything below waits, in dashes, until it answers.
From a browser, these look the same
The guardian process or its machine is down. One guardian down costs only its turn: the other two are still a quorum.
A TLS proxy answers for the guardian on port 443. If the proxy stops, nothing answers, even while the guardian runs.
A browser lets this site read another address only when that address allows it, with a CORS header. On 24 Sep 2026 our guardian sent none. Adding it is a one-line change on its proxy.
Your browser is not told which one it was. curl is. If the commands here answer, our guardian is up and only the cross-origin read is missing. Your own network or a browser extension can also block the request.
Check it yourself
curl -s https://guardian.enderpearl.ai/statuscurl -s https://guardian.enderpearl.ai/operationsWhat to look for in the answer
Its reason, in its own words:
A paused guardian refuses every operation until a person clears the pause. One guardian down costs only its turn: the other two can still sign. The figures below are still its own record.
Not read yet
Publishedepoch 1 · 23 Sep 2026
8a8615d24a920f6f3805c299318be5761beca9df218e4bb60a5f61d20bb67c06
LiveconfigHash in its answer
—
A guardian rejects anything built under a different configuration, matched by this hash. So the live value should equal the published one, character for character.
It should match. If it does not, either a new configuration was agreed and this page is behind, or our guardian runs something other than what was agreed. Both are ours to fix. Tell us at ops@enderpearl.ai.
Every operation our guardian agreed to sign, whoever led it, by kind: how many, the payouts it signed for, and the fees the bridge charged on them.
| Kind | What it moves | Signed | Payouts signed for, PRL | Fees charged, PRL |
|---|---|---|---|---|
| Depositdeposit | Native PRL in at a deposit address. PRL released on Hyperliquid. | — | — | — |
| Withdrawalwithdraw | PRL sent back to the treasury on Hyperliquid. Native PRL paid out on Pearl. | — | — | — |
| Returnreturn | PRL sent on Hyperliquid that cannot be paid out, such as below the smallest amount, back to the account it came from. | — | — | — |
| Revertrevert | Native PRL below the smallest amount, back to a Pearl address signed for by the owner of the Hyperliquid account it was for. | — | — | — |
| Fee sweepfee | What the bridge earned, out of the escrow to the one address the configuration names. | — | — | — |
| All kinds | — | — | — |
Reading this table
Fees as configured, epoch 1
Test-network figures are not a commitment to live fees. No guardian can change a fee alone: a changed fee is a changed fingerprint.
The native PRL in escrow that backs PRL on Hyperliquid, counted by our guardian from its own Pearl node. Before it signs, it checks that what circulates stays covered. If it would not be, it stops rather than sign.
Reserve
—
unspent escrow coins, as its own index counts them
Fees charged
—
all kinds: the sum of the fees on what it signed
Outstanding
—
fees on what it signed, not yet taken out by a fee sweep
The fee sweep moves what the bridge has earned to one address named in the configuration, and nowhere else. Each guardian computes what was earned itself. A sweep can never take PRL a circulating token is owed.
Whose turn it is to lead a payment is a hash of the payment and the guardian’s id, so no guardian leads first or more often. These are the operations our guardian led, and where each one stands.
Most recent first, as far as its record shows. The list carries no times, so we reverse the order the guardian returns.
| Kind | Operation | Payout, PRL | Status | Result |
|---|---|---|---|---|
| — | ||||
Not read yet.
Our guardian’s record is one view. The chains keep their own. Look at the treasury and our signer on the Hyperliquid testnet explorer, and look up the escrow on a Pearl testnet2 node.
A native 2 of 3 multi-signature account naming the three guardians. It holds the PRL token supply. The exchange refuses any action without two signatures, including from the key that created it.
0xefb6f8c559bca7b546b3dbc83f652a3fa1239c0d
Our Hyperliquid key, one of the treasury’s three. We use it for nothing else. It has received a deposit, which Hyperliquid requires before an account can submit payouts.
0xc87e693808208c814b79a0ec024f314aa8d4f3fd
A P2TR output with an unspendable internal key. Its script requires 2 signatures from 3 named keys, and every Pearl node enforces it. Look it up on a node you run or trust.
tprl1pxzutjzl6dar32p8389gkhdylnq0659sv4r3xthpj8ytdst2jcuzq2mzte6
Our Pearl signing key and the full set are on Keys.
Every live figure on this page is our guardian’s own record, from its own database, at the time shown. It is never a claim about the other two guardians. The fees, fingerprint and addresses are the published configuration, on Keys.
—
Or ask it yourself, from any machine:
curl -s https://guardian.enderpearl.ai/statusWho runs it
Enderpearl runs this guardian and its host, Enderpearl A. The figures above are its record alone.
Our keys
Published, with the configuration fingerprint. Check them on Keys.
Our signature
Any payout needs two of the three guardians’ signatures, and ours can be one of them. So two colluding guardians could move the escrow.