Skip to content
PalsideDocs
On this page

Wallet

Receive PALS, send to a squad member, and check payments and red packets.

Wallet is the PALS wallet built into your account. It supports the configured token and network for transfers, red packets and tips, without connecting another wallet.

The service must enable payment features first. Until then, Wallet shows Not open yet, and choosing a packet, transfer or tip only says the wallet isn't open yet. This guide does not mean that live payments are already open.

Step 1 of 5

The USD estimate is for display only. If the chain head is over 5 minutes old, pool liquidity is below the operator's minimum, or the price is unavailable, only PALS is shown. This does not mean a zero-dollar price or change the payment amount. The minimum defaults to 0, adding no extra threshold; the pool must still have liquidity.

Receive PALS

Open Receive to copy your address or show a QR code. Check the network and token contract with the sender; a QR code does not prove that a token is genuine. Wallet only tracks the configured PALS contract.

Send to a squad member or another address

Choose Transfer, then Teammate or Address: pick someone from the current squad, or enter the full receiving address and check the network. Then enter an amount. Transfers go directly to the recipient after chain confirmation; there is no accept-or-reject step.

Review the details. Check the recipient and amount. Palside charges no fee and sponsors network fees; see PALS.

Authorize locally. Enter your 6-digit password when requested. Transfers to an address always require it.

Wait for confirmation. Submission is not completion. Only a confirmed chain result is shown as completed.

Transfers to an address reject your own address, the zero address and configured contracts. Sending to the wrong otherwise valid address cannot be undone by Palside.

When the result is unclear

Pending payments are checked every 3 seconds for the first 2 minutes, then gradually less often up to every 30 seconds, without giving up. Opening Wallet or the payment panel checks immediately. You can also choose Refresh status on the pending payment. Continue checking the same operation if the connection failed after submission. Do not create a replacement payment just because a request timed out or a price lock expired.

Leaving the payment screen does not cancel a transaction. An operation whose signature may have left the device cannot safely be treated as unsent. If no definitive result is available, keep it pending and retry the status check when service returns; do not assume a missing activity record means failure.

After reopening or changing devices

Wallet's recovery list reads the pending operations for your account from the service, so you can find them again after restarting, signing back in or using another device. Check an entry's amount, recipient, order ID and available transaction hash, then query its status. This checks the original operation without submitting another payment.

Only an unsubmitted order that is still eligible can return to review. Review its current details and authorize it again; recovery does not silently sign or pay. A possibly submitted operation stays on the status-check path. If a cancelled or expired entry still shows reserved funds, those funds are not proven released. A transaction can also be confirmed while its indexed business record is still catching up.

The list remains available when new payments are closed or the wallet is locked, but it still requires a valid signed-in account and reachable service. A failed lookup is not an empty list. Recovery cannot restore a deleted account, retrieve a lost phrase or reverse a chain transfer.

People whose account links have been removed appear as “Deleted member” in payment and claim history. Open Activity for confirmed records and transaction hashes. If records fail to load, use retry. A loading error is not “no transactions.”

Records with cleared account associations have no link to the original account; public addresses and transaction hashes remain available to check. Packet settlement, refunds and chain reconciliation keep retrying. More than one hour of consecutive failures alerts the operator; an alert is not proof of payment or refund.

Small payments without a password

This option is off by default and requires your local password to enable. Limits come from the service, defaulting to 250 PALS per payment and 1,000 PALS per day. Operators can adjust them; the extension never exceeds those caps. Allowances reset by UTC day, with the reset time shown in your local time. Usage is accounted for locally for this account in this browser. These are not shared server-side spending limits across devices.

Transfers to an address still require a password, and a locked runtime still needs unlocking. A lost device or compromised browser profile can put funds at risk even within these limits.

Send or claim a red packet

Step 1 of 3

Open the red-packet action in a squad or danmaku, choose the amount and count, then review and confirm. The contract holds the funds. Each eligible person can claim once. Blessings allow 24 visible characters. Equal-share packets require a divisible amount, with the nearest valid amount suggested. The hourly limit of 10 packets counts only signed, submitted orders, not quotes. Squad packet senders can also claim; danmaku packet senders cannot claim their own packets.

TypeEligibilityGrab period
SquadMembers of the squad when sent24 hours
DanmakuAccount at least 24 hours old; continuously in the same danmaku for 30 seconds1 hour

A claim credential or queued claim is not money received. Wait for chain confirmation. Automatic claims depend on available sponsorship and the execution service.

A 2-hour settlement window follows the grab deadline for assigned shares. After that window, the service submits a refund for the remainder; chain confirmation is required before it is returned. Refunds can remain pending if automation is unavailable. Check the status in packet details. The extension has no manual refund or cancellation action for a sent packet. Completed claims cannot be taken back.

Danmaku tips offer 10 / 50 / 100 PALS, defaulting to 50, with custom amounts capped at 10000 PALS. Tips on the same line are grouped over 30 seconds. Sponsored payments default to 50 per account per UTC day; exhaustion shows your local reset time.

Protect the address and its funds

The account phrase derives both your identity and a separate wallet key. Losing or leaking it affects both. In Wallet security settings, private-key export requires your local password and is displayed for at most 30 seconds; anyone with that key can control the address's assets.

Before deleting your account, handle the balance and securely retain your phrase or exported wallet key. Deletion removes the wallet binding. Pending orders are reconciled before account links are removed, retaining only amounts and transaction hashes. The same phrase can register again without restoring the old account data. The address, assets and public transactions remain. Details of data visibility are in Security and permissions.