Status · Enderpearl A
GET guardian.enderpearl.ai/status
Our guardian’s record, live.
Your browser asks our guardian 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.
Our guardian, from your browser
Not read yet
This panel reads our guardian from your browser.
Our guardian did not answer this 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
-
1
It is stopped or restarting.
The guardian process has stopped or is not answering. While it is down it signs nothing, and new payouts wait until it is back. It cannot move funds.
-
2
Its proxy or its server is down.
A proxy in front of the guardian takes every request. If the proxy stops, or the server does, nothing answers.
-
3
Something on the way blocked it.
Your network, a firewall or a browser extension can stop this page reading another address, even while our guardian runs.
Your browser is not told which one it was. curl is: if the command answers on your machine, our guardian is up, and something between it and this browser stopped the read.
Check it yourself
Run the command under Where these figures come from on any machine.
What to look for in the answer
- id
- "t-mining"
- configHash
- ca7ec3a5…, the fingerprint Pearl Swap publishes, all 64 characters
- paused
- null, or its reason in words
- pearlHeight
- the last Pearl block it has read from its own node
Our guardian reports that it is paused.
Its reason, in its own words:
It gives no reason.
A paused guardian refuses every operation until a person clears the pause. Every payout needs all three guardians to prepare it, so new payouts wait while one is paused. Escrowed funds stay where they are. The figures below are still its own record.
Configuration
Not read yet
Published by Pearl Swapepoch 1 · since 25 Sep 2026
ca7ec3a5e73d8e728c3056726846a35455e3d7c180134910d21acca64913f25b
LiveconfigHash in its answer
—
A guardian rejects anything built under a different configuration, matched by this hash. So the live value should equal the one Pearl Swap publishes, character for character. Compare it with Pearl Swap’s Key addresses page, not only with this page.
It does not match. 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.
C = A·B · the pearl marks one cell · seed 0xE61C until our guardian answers
What it agreed to sign
/status · signed, earnings.chargedEvery 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 on Pearl; 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 or above the largest, back to the account it came from. | — | — | — |
| Revertrevert | A Pearl deposit below the smallest amount or above the largest, sent back to a Pearl address the owner of its Hyperliquid account signs for. | — | — | — |
| Fee sweepfee | What the bridge earned, out of the escrow to the one address the configuration names. | — | — | — |
| All kinds | — | — | — |
Reading this table
- Amounts are exact to the grain. 1 PRL = 100,000,000 grains.
- A kind it has never signed is missing from its record. We show it as 0.
- Signing is agreeing. A payout also needs a second guardian, and the chain to accept it.
Fees and limits as configured, epoch 1
- To Hyperliquid
- 1 PRL flat. Pearl’s own network fee to send it is extra
- Back to Pearl
- 0.25% plus 0.0001 PRL
- Smallest payment
- 10 PRL
- Largest payment
- 100 PRL
- Releases
- At most 500 PRL in a rolling hour and 2,000 PRL in a rolling day
Test-network figures are not a commitment to live fees. No guardian can change a fee alone: a changed fee is a changed fingerprint.
What the escrow holds, by its count
/status · reserve, earningsThe native PRL in escrow, counted by our guardian from its own Pearl node: what backs the PRL the bridge has released on Hyperliquid, plus fees not yet swept. Before it signs a payout on Hyperliquid, it checks that what circulates stays covered. If it would not be, it pauses and signs nothing.
Reserve
—
unspent escrow coins, counted from its own Pearl node
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
By the guardian’s count, what circulates is the token’s whole supply, as the configuration names it, less what the treasury holds. Our guardian’s record does not report what circulates, so this page does not set it beside the reserve. Whether it has paused is in the panel above.
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.
Payments it took a turn at
/status · ledEach payment has a leader: the guardian whose turn it is builds the payment and asks the other two to check it. A hash of the payment and each guardian’s id sets the order, so no guardian leads first or more often. The turn moves on after a timeout, and a guardian records a payment whenever its turn comes, even if it then finds it already paid. So one payment can be counted by more than one guardian. These are the payments ours took a turn at, counted by where each stands.
- Collecting—Asking the other guardians to sign.
- Ready—Two signatures in hand. The payout is being sent.
- Done—Sent, and its own Pearl node or Hyperliquid accepted it. Another guardian may count the same payout: it is one transaction, and the chain took it once.
- Refused—Every guardian refused it, each with a reason.
- Failed—Hyperliquid turned the payout down. Once that payout’s time runs out, the payment is proposed again. If it keeps failing, it needs an operator.
- Superseded—Already paid when its turn came, paid first by another guardian, or left to the other two once they had signed a payout for it.
Where these figures come from
one source, read by your browserEvery 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, the limits and the fingerprint are the shared configuration’s. Pearl Swap publishes the bridge’s addresses and each guardian’s Pearl public key on its Key addresses page.
- Source
- GET https://guardian.enderpearl.ai/status, public and read-only. The only other address this site’s pages read.
- When
- When the page opens, then every 30 s while this tab is visible. An answer that takes longer than 6 s counts as no answer.
- Round trip
- How long its /status took to answer your browser. The first reading also opens the connection, so it takes longer than the ones after it.
- Amounts
- Exact to the grain. 1 PRL = 100,000,000 grains. Big integers arrive as digit strings, and are read without rounding.
- Pearl height
- The last Pearl block it has read from its own node. It can trail the network’s tip while it catches up. A guardian whose view lags refuses until it does.
- Uptime
- Time since its process last started, from startedAt, measured with your device’s clock. It restarts at zero and says nothing about earlier outages. We show it in whole days, with the day it started, never a time of day. The last answer, as received, carries startedAt exactly as the guardian sends it.
- The other two
- This page reads only our guardian, and this site’s security policy lets your browser ask no other. The other two are mc-mining, run by Deep Nacre, and pearl-swap, run by Pearl Swap, as Pearl Swap’s guardians page names them. Each operator publishes its own guardian’s live state, as we do here. They report their configuration the same way, as configHash, and it should be the same on all three. What each has signed, taken a turn at and charged can differ, because each counts only its own part.
- Not shown
- Anything that cannot be read live. We publish no uptime history, hardware or hashrate figures.
Enderpearl A
our guardian host
- Runs
- pearld, a Pearl testnet2 full node, and our guardian
- Guardian
- t-mining, one of three in Pearl Swap
- Answers at
- guardian.enderpearl.ai · /status (JSON)
- Operated by
- Enderpearl
The last answer, as receivednot read yet
—
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
Made on our own server, and their private halves never leave it. Pearl Swap publishes the public half of our Pearl signing key, with the other two guardians’, on its Key addresses page.
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.