Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.arcpass.vibepas.xyz/llms.txt

Use this file to discover all available pages before exploring further.

ArcPass sponsors the first transaction for wallets that meet a set of eligibility criteria. These checks exist to ensure that sponsorship reaches genuine new wallets on Arc Network and that the system is protected from abuse. Before you submit a sponsorship request, make sure your wallet satisfies every requirement below.

​
Eligibility criteria

​
1. Your wallet must be registered with ArcPass

Before you can request a sponsorship, you must register your wallet address with ArcPass. Registration is a one-time step that creates a record for your address in the system. 
POST /wallets/register
Content-Type: application/json

{
  "walletAddress": "0xYourWalletAddress"
}
If you submit a sponsorship request for an unregistered address, the request will be rejected.

​
2. Your wallet address must be a valid Ethereum address

The address you provide must follow the standard Ethereum format: the 0x prefix followed by exactly 40 hexadecimal characters. Both uppercase and lowercase hex characters are accepted. Valid: 0xAbCd1234... (42 characters total)
Invalid: AbCd1234... (missing 0x), 0xAbCd12 (too short) The API validates this format on every request and returns an error immediately if the address does not match.

​
3. Your wallet must not have been previously sponsored

ArcPass sponsors each wallet exactly once. If your wallet has already received a sponsorship — from any prior request — your new request will be rejected.
This check is enforced on-chain by the SponsorshipRegistry contract. When your request is processed, ArcPass calls sponsorshipCount(yourAddress) on the registry. If the count is greater than zero, the sponsorship transfer is refused at the contract level, not just at the API level. This makes the check tamper-proof and verifiable by anyone.

​
4. Your wallet must not be blocked

If your wallet address has been flagged — for example, due to abuse of the rate limits — it will be marked as blocked. Blocked wallets cannot receive sponsorship and any request submitted for a blocked address will be rejected.

​
5. No duplicate pending requests

ArcPass does not allow more than one pending sponsorship request per wallet at the same time. If you already have a request in the pending or approved state, you must wait for it to reach a terminal state (completed, rejected, or failed) before submitting a new one.

​
6. You must pass rate limiting

ArcPass enforces rate limits at two levels to protect the system:
  • Per-wallet limit: A single wallet address can submit a limited number of requests within a rolling time window.
  • Per-IP limit: A single IP address can submit a limited number of requests within the same window.
Exceeding either limit will cause your request to be blocked. If you breach the threshold repeatedly, your wallet or IP address may be auto-blocked for a period of time.
Replay protection also applies: if you send two identical requests (same wallet address and same IP) within a 5-second window, the second request is rejected as a duplicate.

​
Summary

CriterionRequired
Wallet registered with ArcPassYes
Valid Ethereum address format (0x + 40 hex chars)Yes
No prior sponsorship (on-chain check)Yes
Wallet not blockedYes
No duplicate pending request for this walletYes
Within per-wallet and per-IP rate limitsYes

​
What to do if your request is rejected

If your sponsorship request is rejected, first check whether your wallet has already been sponsored by calling isSponsored(yourAddress) on the SponsorshipRegistry contract — the contract address is shown on the ArcPass home page. If isSponsored returns true, your wallet is already funded and you do not need another sponsorship. If you believe your wallet has never been sponsored and the rejection is in error, contact ArcPass support with your wallet address and request ID.