Three things you need
A supported EVM wallet. Check the wallets offered by the current connection screen. Review each authorization request before signing. Do not disclose your wallet’s private key.
An eligible Perpl account. Review current access, regional restrictions and any referral eligibility on the Vesper connection page before funding for bot access. An invite alone does not prove eligibility.
Available margin on Perpl. Check the current order minimums, position requirements and the size you intend to trade. There is no universal deposit amount that makes a session suitable or safe.
Check access before funding
If eligible, use the Perpl invite link, select Connect Wallet and review the sign-in request. Check whether the referral code jGh4C1kNRTW is applied and review current terms; do not assume the link guarantees access or a fee benefit.
Perpl is built on Monad; see its official documentation. Before using Deposit, verify the current supported network, collateral asset, recipient and fees in the actual interface. Confirm that Vesper recognizes the intended account before transferring funds.
Eligibility checks can take time to update. If an existing account is refused, contact support before creating another account or moving funds.
Generate a restricted trading key
Go to app.perpl.xyz/apikeys and review the permissions required by Vesper. Enable the necessary Trade and read access only; do not grant withdrawal access. Review the expiry and renewal requirements rather than choosing unlimited lifetime by default.
The documented Vesper connection uses an API-Key token and a Secret. Check the current field names and required format; do not confuse an API credential with your wallet’s private key. Keep credentials private and submit them only through the intended Vesper connection form.
Store credentials securely when they are displayed. If a credential is unavailable or expired, review the venue’s recovery or replacement procedure. Do not revoke or replace a key used by an active session without first resolving its orders and positions.
Connect the intended Perpl account
Open sypherscore.com/vesper/connect, switch the venue to Perpl, and connect the same wallet you used on Perpl. Paste the API-Key token and the secret into their intended fields, hit save, and review the signature request. Never paste the wallet’s own private key or seed phrase.
Pick a mode, set the size, press Start
Review the modes actually offered in your account. Labels such as Min cost and Volume describe objectives, not guaranteed cost rankings or returns. Tighter quotes can change turnover and adverse selection; compare measured results under matching conditions.
Review margin, clip size, leverage, inventory cap and loss limits before a signed Start. Then check status, waiting reasons and venue rejections rather than assuming the first orders must appear within a fixed number of seconds.
Reading the dashboard
- Live status
Read the quoting, holding or flattening label with its timestamp and the venue state. A label alone does not prove that current orders or positions match it.
- Activity feed
Use the displayed fills and prices as a session view, then reconcile gaps or delays with venue records. The feed is not independent proof of complete accounting.
- Totals
Read realised P&L, filled turnover, fees and funding together. CPM is cost per $1M of filled turnover under the stated accounting method, not a return forecast or a measure of open-inventory risk.
- Close the tab
The engine runs server-side. Closing the browser is not a Stop request. Service or venue interruptions can still affect a session.
Stop and Forget
Stop requests cancellation and flattening with wallet authorization. Wait for terminal status, independently verify zero positions and no open orders on all affected markets, and review History. Venue or network problems can delay cleanup; exits can incur fees and losses. If the result is unknown, do not start another run. See risk controls.
Forget removes the saved Vesper credential; revocation in Perpl is a separate action. Neither proves that the venue is flat or orderless. Resolve the session first so loss of authorization does not prevent cleanup.
Troubleshooting
- “Referrals only”
Check the account’s eligibility and any update delay. Ask support to clarify an unexpected rejection.
- “Unauthorized”
Read the full error and check the intended account, credential validity, permissions and expiry. Missing Trade scope is one possible cause, not a universal diagnosis. Do not replace an active session’s key blindly.
- No orders appear
Inspect the reported reason: margin, order minimums, permissions, stale data or the mode’s entry conditions can prevent quoting. Do not automatically increase a deposit or disable a control.
- “Pinned to another node”
Do not start a second session or try to bypass the assigned node. Give support the error and session context without credentials. Any recovery must account for existing orders and positions; moving a live session is not an automatic remedy.
Permissions are not a safety guarantee
Key scope. Verify the actual exchange permissions and do not grant withdrawal access. Trading can lose money without any withdrawal.
Protect wallet secrets. Never enter your wallet private key or seed phrase. This connection uses a separate venue API credential, and signatures can grant significant permissions. Inspect the actual request and account before approving.
Forget versus revoke. Deleting a saved key and revoking it at the venue are different actions. Neither confirms that existing orders or positions are closed. Check venue state separately.