Xian Network | Smart Contracts | Web3 | MAINNET | Python | dPoS
Layer 1 Blockchain
Xian Network is a blockchain application that was built on top of CometBFT.
Smart contracts are native Python, so very easy for developers to jump into. Has fast, inexpensive transactions. Open-source.
The maximum supply of 111,111,111 million is also deflationary with 1% of each transaction burned.
On our chain developers are also rewarded with transaction fees used on their deployed contracts.
Smart Contracts
Native Python - NO SDKs just PYTHON
No Jargon. No Nonsense. Just a simple developer experience that helps you build the next generation of blockchain powered smart apps. Check out the Documentation. Most of the transaction fees are rewarded to you as a developer, when your contract is used!
DAO
The DAO will give node owners voting power over the use of 33.3m $Xian funds, change of rewards, transaction fee cost and responsibility to vote on motions to add or remove nodes. This added layer of transparency and democracy gives the community a greater say on important decisions about the future direction of the platform.
Xian Wallet Web Extension
Interact with applications deployed on the Xian network, or build your own! This wallet features a direct link to websites powered by Xian to make interaction simple and easy. It also includes a development environment so you can build and deploy your own applications without needing to install a custom development environment.
Get the Wallet on Chrome Web Store
Block Explorer
The Block Explorer allows users to explore the blockchain in real time, providing insights into transactions and network activity. You can easily track the current state of blocks and transactions, ensuring transparency and accessibility for users.
Explore the blockchain
Tech FAQ
Q: Python isn't typically used for blockchains because it's slow? How is it supposed to scale?
A: You're correct. That's why we're using CometBFT (written in Go) for the blockchain and networking. Only the application layer, which handles the smart contracts and state, is written in Python and C.
Q: How does the Sandboxing of Smart Contracts work?
A: The sandbox used for executing smart contract code consists of multiple layers: linter, compiler, runtime, and executor. When new smart contract code is provided, it's converted to an Abstract Syntax Tree, which is then analyzed for violations of our enforced rules. The compiler transforms the code into a format that privatizes certain functions. The runtime establishes a highly restricted execution environment for the smart contract, which is traced and lacks access to global Python packages. The executor modifies the internal Python import function to work exclusively with other deployed smart contracts.
Q: How is the computational work measured that results in fixed fees?
A: A tracer module, written in C for speed, measures opcode calls from smart contract executions. It associates each call with a cost we've determined to be appropriate for the computational power used.
Q: How are transactions ordered, if there are no variable GAS fees?
A: Currently, we use the standard transaction ordering of CometBFT, which is explained in the CometBFT documentation. In a nutshell, you can't expect your transactions to be processed in a specific order when they're in the same block.
Q: Can I use any Python package in my smart contracts?
A: No. Only modules specifically made available and compatible with blockchain principles can be used in the sandboxed environment where smart contracts are executed.
Q: Why are you not using CometBFT 1.0?
A: We disagree with some changes included in CometBFT 1.0 (Proposer Based Timestamps). Additionally, the version we're currently using will continue to receive support for years to come.