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 is public infrastructure that covers the cost of your first transaction on Arc Network so you can get started without needing to acquire gas yourself. If you have questions about how the system works, who can use it, or what to expect, the answers below cover the most common topics.
ArcPass is a gas sponsorship service for Arc Network. When you create a new wallet on Arc, you need a small amount of native tokens to pay for your first transaction — but getting those tokens is difficult if you have no gas to start with. ArcPass solves this by paying for your first transaction on your behalf through a relay system backed by on-chain smart contracts. You submit your wallet address, ArcPass verifies your eligibility, and the relay worker sends gas directly to your wallet automatically.
Anyone with a new Arc Network wallet is eligible to request sponsorship. Eligibility is checked on-chain: if your wallet has not previously received a sponsorship through the SponsorshipRegistry contract, you qualify. There are no accounts, sign-ups, or identity requirements.
The sponsorship amount is set by the operator deploying ArcPass and is controlled by the SPONSORSHIP_AMOUNT_WEI environment variable. The default is 0.001 native tokens (1,000,000,000,000,000 wei). This is enough to cover a standard first transaction on Arc Network. The amount is fixed per sponsorship and cannot be changed per request.
Yes. ArcPass is free public infrastructure built for the Arc ecosystem. There is no fee, no token requirement, and no sign-up cost. The gas is funded by the SponsorVault treasury maintained by ArcPass operators. You receive the sponsored gas at no cost to you.
No. ArcPass enforces a one-sponsorship-per-wallet policy at the on-chain level through the SponsorshipRegistry contract. Once your wallet has been sponsored, the registry records it permanently and any future requests for the same wallet will be rejected. This limit cannot be bypassed or reset.
ArcPass currently operates on the Arc Network testnet, which has a chain ID of 5042002. The worker verifies the chain ID against the configured RPC endpoint at startup, so it will only process transactions on the correct network. Mainnet deployment is on the roadmap.
Most sponsorship requests are processed within seconds to a few minutes. After you submit your request, the relay worker picks it up and submits the on-chain transaction. Final confirmation depends on Arc Network block times. If the network is congested or the worker has a backlog, it may take longer. You can check the status of your request at any time using GET /sponsorship/:id.
ArcPass accepts standard Ethereum-format wallet addresses: a 0x prefix followed by exactly 40 hexadecimal characters, for a total of 42 characters. Example: 0xAbCd1234.... Addresses are not case-sensitive — both checksummed and lowercase formats are accepted. Any address that does not match this pattern will be rejected at the API level with a validation error.
Yes. ArcPass is released under the MIT license. The full source code — including the Fastify API, worker runtime, Solidity smart contracts, and validation suite — is publicly available and auditable. You can review the implementation, self-host your own instance, or contribute to the project.
If the relay worker encounters an error when submitting your transaction on-chain, it retries automatically. The system will attempt the relay up to 5 times before marking the request as permanently failed. If your request shows a failed status after all retries are exhausted — which can happen due to network issues or insufficient vault balance — you can submit a new sponsorship request. The system treats a new submission as a fresh attempt.