Wallets authorize actions
A wallet manages signing and lets a user approve an action. A connected wallet is not permission to spend. Make the network, recipient, amount and requested approval clear.
Explore XDC walletsWEB3 / BUILT ON XDC
Web3, built around real use.
Connect wallets, smart contracts and real-world workflows on XDC. Start with the fundamentals, then build toward assets, payments and useful applications.
THE BUILDING BLOCKS
A shared network. A programmable experience.
Web3 applications connect a user interface to wallets and contracts. XDC provides the execution and transaction layer; your application supplies the experience and business rules.
Contracts enforce rules
Use Solidity and EVM-compatible tools to define ownership, permissions and transfers. XDC documentation covers familiar Ethereum development tools; validate each dependency on your target network.
Open the developer hubTransactions create a record
Use transaction hashes, receipts and contract events to connect the interface to network outcomes. Show pending, confirmed and failed states distinctly instead of assuming a submitted transaction succeeded.
Explore analytics toolsXDC APPLICATION PATHWAYS
From digital ownership to real-world coordination.
Choose the application around a concrete user need. These are design directions, not a claim that every implementation is provided by the network.
Tokenized assets
Connect asset records to programmable ownership and transfer workflows. Issuer operations, servicing and the rights represented by a token need their own design.
Explore RWA on XDCPayments and commerce
Build applications around native USDC on XDC and inspect Circle’s CCTP V2 integration path. Use the provider’s current documentation for asset and network support.
Circle’s XDC announcementTokens and membership
Explore XRC20 for fungible tokens and XRC721 for unique assets. Memberships and access experiences are application patterns; define issuance, permissions and holder rights explicitly.
XDC token standardsDigital trade
Connect trade documents, counterparties and financing workflows. XDC’s trade-finance ecosystem is a starting point for understanding how applications link on-chain records with business processes.
Explore trade financeEnterprise networks
Evaluate an XDC subnet when participation and governance need a separate network. Document what remains private and what checkpoints or other information reach the public chain.
Explore subnet architectureYOUR FIRST XDC APPLICATION
Start small. Make every state clear.
Use this sequence to turn a concept into a testable application before working with mainnet assets.
Connect to Apothem
Configure chain ID 51 in a supported wallet and use a documented testnet RPC. Keep testnet and mainnet configuration separate.
Network setupFund a test wallet
Request test tokens from the Apothem faucet. Testnet XDC is for development; it is not mainnet XDC.
Open the Apothem faucetDeploy one useful contract
Begin with a small Solidity contract and an explicit permission model. Compile, test and inspect the deployed address before connecting your interface.
Deployment and verification guideComplete the user journey
Exercise rejected signatures, insufficient balances, failed calls and successful receipts. Give users a transaction link and a clear way to recover.
Inspect Apothem transactionsKEEP BUILDING
The application is part of a wider system.
Bring the right people and infrastructure into the project as the scope grows.
Discover applications and providers
Find wallets, infrastructure and independent applications in the preserved XDC ecosystem directory. Check each provider’s current support and operating terms.
Browse the ecosystemContribute with other builders
Use the developer community to discuss integration questions, share experiments and follow ecosystem work. Explore program requirements directly with their organizers.
Find builder programsUnderstand network resilience
Follow XDC’s multiple-client approach and post-quantum work as separate engineering efforts. Compatibility, validator readiness and cryptographic migration each require their own evidence.
Compare client evidenceA few useful answers
Common questions.
Do I need a new programming language to build on XDC?+
XDC supports Solidity and EVM-compatible development. Start from the XDC developer documentation, then validate libraries, RPC behavior and deployment configuration for the network you use.
What is the difference between XDC and USDC?+
XDC is the network’s native token. USDC is a separate stablecoin issued by Circle with native support on XDC. Standard network transactions use XDC for gas; supported sponsored-payment services can abstract that fee from a payer.
Does a token automatically establish real-world ownership?+
A token records contract state. The rights attached to an asset also depend on the issuer’s arrangements and applicable documentation. Design both the digital workflow and the underlying asset process.
Where do AI and quantum fit into Web3 on XDC?+
AI applications can use XDC for payment and contract interactions. Post-quantum research studies future cryptographic protection. Neither means that XDC runs AI models or quantum computers inside its EVM.
Go to the source
Sources & further reading.
KEEP EXPLORING