NEO

Overview This repository is a csharp implementation of the neo blockchain. It is jointly maintained by the neo core developers and neo global development community. Visit the tutorials to get started. Project structure An overview of the project folders can be seen below. /src/neo/Cryptography/ General cryptography implementation, including ECC. /src/neo/IO/ Data structures used for caching and collection interaction. /src/neo/Ledger/ Classes responsible for the state control, including the MemoryPool and Blockchain . /src/neo/Network/ Peer-to-peer protocol implementation. /src/neo/Persistence/ Classes used to allow other classes to access application state. /src/neo/Plugins/ Interfaces used to extend Neo, including the storage interface. /src/neo/SmartContract/ Native contracts, ApplicationEngine , InteropService and other smart-contract related classes. /src/neo/Wallets/ Wallet and account implementation. /src/Neo.Extensions/ Extensions to expand the existing functionality. /src/Neo.Json/ Neo's JSON specification. /tests/ All unit tests. Related projects Code references are provided for all platform building blocks. That includes the base library, the VM, a command line application and the compiler. neo: The core libraries for NEO. neo-node: The node-cli implementation to start a NEO node, and Plugins(including DBFT, RpcServer, Oracle, ApplicationLogs, etc.). neo-vm: The Neo Virtual Machine implementation. neo-express: A private net optimized for development scenarios. neo-devpack-dotnet: These are the official tools used to convert a C smart-contract into a neo executable file . neo-proposals: NEO Enhancement Proposals (NEPs) describe standards for the NEO platform, including core protocol specifications, client APIs, and contract standards. neo-non-native-contracts: Includes non-native contracts that live on the blockchain, included but not limited to NeoNameService. Opening a new issue Please feel free to create new issues to suggest features or ask questions. Feature request Bug report Questions If you found a security issue, please refer to our security policy. We welcome contributions to the Neo project! To ensure a smooth collaboration process, please follow these guidelines: Branch Rules master - The NEO-4 development branch. master-n3 - The NEO-3 development branch. Important : All pull requests must be based on the master or/and master-n3 branch. 1. Fork the repository and create your feature branch from master or/and master-n3 : 3. Test your changes thoroughly to ensure they don't break existing functionality. 5. Push to your fork and create a pull request against the master or/and master-n3 branch: 6. Create a Pull Request targeting the master or/and master-n3 branch with: Clear title and description Reference to any related issues Summary of changes made Development Workflow Feature branches are merged into master or/and master-n3 . Create a release branch from master or/and master-n3 periodically. Only hotfix branches are merged into release branches. For more detailed contribution guidelines, please check our documentation or reach out to the maintainers. Bounty program You can be rewarded by finding security issues. Please refer to our bounty program page for more information.