Starknet Sepolia Faucet
Claim testnet STRK for Cairo development, smart-account testing, and Starknet Sepolia dApps.
No login • No balance • Instant claim
Funding a Starknet Sepolia Account
- Each wallet can claim Starknet Sepolia STRK up to 10 times per day
- There is a 60 minute cooldown between successful claims
- Captcha verification is required before token delivery
- Starknet Sepolia STRK is a testnet token and has no monetary value
- Spam, abuse, or automated draining may result in restriction
Starknet Sepolia STRK gives developers gas for Cairo contracts, account transactions, wallets, dApps, games, bots, and automation. Claim limits help keep this faucet available for builders instead of allowing repeated automated requests to drain the balance.
Use only your public Starknet account address. ZalalenA Faucet does not require login, wallet balance, private keys, seed phrases, or wallet signatures.
Starknet Accounts and Cairo Development
Starknet Sepolia is the public environment for validating Cairo applications before mainnet release. Testnet STRK pays fees for account transactions, deploying contracts, invoking entrypoints, and testing wallet connections.
Starknet uses account contracts. A public address begins with 0x and is a field element, not an Ethereum externally owned account. Fund the deployed account address that will sign your next Starknet transaction.
Testnet STRK works only on Starknet Sepolia. It is not real STRK, has no monetary value, and cannot be used on Ethereum Sepolia or Starknet mainnet.
Claim to the Address That Will Sign
Enter your public Starknet Sepolia account address, complete captcha verification, and click the claim button. If the request passes the faucet rules, testnet STRK is sent to that account.
After the claim, make sure Argent X, Braavos, or your chosen wallet is connected to Starknet Sepolia and displays the same address used for the request. A different account or network will not show the token even when the claim succeeds.
Never enter a private key, seed phrase, recovery password, transaction hash, or Ethereum address that is not a deployed Starknet account you control.
First Starknet Workflow: Claim, Deploy, Invoke, Verify
1. Claim STRK, then confirm the same account address and inspect its balance in a Starknet Sepolia wallet or Voyager.
2. Deploy a Cairo contract or select an existing Sepolia contract, and record its class hash and contract address before wiring it into a frontend.
3. Execute the real account transaction or contract invocation your product needs with the intended account, calldata, and network.
4. Inspect the transaction hash and receipt; repeat once with an intentional invalid calldata or account condition to verify application error handling.
Starknet Sepolia Release Checklist
Before releasing a Starknet integration, verify the selected Sepolia account address, RPC network, class hash, contract address, entrypoint, calldata, and account deployment status. Compare the address receiving the faucet claim with the address the wallet presents for signing.
Test an empty address, a funded account, account deployment, rejected signatures, wrong network selection, and stale UI data. Confirm that the interface displays a transaction hash and explains whether a problem is fee balance, account state, calldata, or contract execution.
Starknet Claim and Transaction Troubleshooting
Cooldown active: Your account may need to wait until the 60 minute cooldown ends before claiming again.
Captcha failed: Refresh the page and complete captcha verification again.
Invalid address: Enter a non-zero Starknet field-element address up to 64 hexadecimal digits. A 64-digit address is valid when it is below the Starknet field limit.
Tokens not visible: Confirm Starknet Sepolia and the same public account in your wallet, then inspect the returned Voyager transaction.
Temporary delay: Faucet demand, RPC conditions, or testnet activity may delay delivery for a short time.
Starknet Faucet Questions
What is a Starknet Sepolia faucet?
A Starknet Sepolia faucet sends free testnet STRK for Cairo development, Starknet dApps, wallets, bots, and automation.
Do I need login to claim?
No. You only need a public Starknet account address and captcha verification.
Do I need wallet balance before claiming?
No. A new Starknet account with zero balance can claim Starknet Sepolia STRK.
Can I use a 64-digit 0x address?
Yes, provided it is a non-zero Starknet field-element address. This faucet accepts valid 1–64 digit hexadecimal Starknet addresses.
Does the faucet need my private key?
No. Only your public account address is required. Never share a private key or recovery phrase.
Account Abstraction Testing on Starknet
Every Starknet user interacts through an account contract. Test the first-user path with a fresh account: fund it, submit a transaction, inspect the receipt, and confirm that the wallet and application agree on the selected Sepolia address.
A successful faucet claim pays fees; it does not deploy an account contract, authorize a signer, or repair an application configured for another network.
Class Hashes, Contract Addresses, and Network Scope
Keep Starknet Sepolia class hashes and deployed contract addresses separate from mainnet and other testnets. A correct balance cannot make a class hash, entrypoint, or calldata from another deployment valid.
Record the faucet transaction hash alongside the deploy and invoke transaction hashes in QA notes. This gives support a traceable path without requesting any secret information.
Testing a Starknet Application from a New Account
Begin with a public Starknet Sepolia account that has no STRK. Claim from the faucet, confirm the account in the selected wallet, and inspect the resulting balance before submitting the next transaction.
Test a successful call and intentional failures such as wrong calldata, a missing deployment, a rejected signature, and the wrong network. A reliable UI identifies the real cause instead of asking users to repeatedly claim more funds.
Fees, Nonces, and Transaction Receipts
Testnet STRK pays Starknet transaction fees. A transaction can still fail because an account is undeployed, a nonce is stale, a signature is rejected, an entrypoint is wrong, or contract execution reverts.
Inspect the transaction receipt and execution result in Voyager before retrying. The faucet transaction hash is evidence of delivery, while the application receipt explains a later contract failure.
Safe Testnet Handling
Starknet Sepolia STRK from ZalalenA Faucet is free testnet gas with no monetary value. It cannot be traded or used on mainnet.
The faucet never requires a wallet connection, signature, login, private key, seed phrase, or recovery password. Only a public account address and captcha are required.
Shared Faucet Access
Cooldowns and request limits protect the faucet for developers, testers, automation workflows, and new users. They preserve the no-login, no-balance, instant-claim experience for legitimate Starknet Sepolia testing.
Confirming a Starknet Claim
Most successful claims are delivered after network confirmation. If the balance does not appear immediately, refresh the wallet, verify Starknet Sepolia is selected, and open the returned transaction link in Voyager.
Keep Starknet Sepolia Separate from Ethereum Sepolia
Both networks use hexadecimal addresses, but they are distinct networks. This faucet sends STRK through a Cairo ERC-20 contract on Starknet Sepolia; it does not fund Ethereum Sepolia.
Cairo Contract Testing
Use the claim to test Cairo deployments, invokes, event handling, wallet prompts, fee estimates, and transaction-state updates. Keep the selected account, contract address, and network visible throughout the flow.
Explorer-First Support
When troubleshooting, use the returned transaction hash in Voyager and compare the recipient account, token transfer, block status, and execution result. That is sufficient for support; private credentials are never needed.
Community