Home
This is the UNetwork Mainnet "Ustart"
UNetwork is a revolutionary protocol for publishing and valuing online content that helps online content platforms better align with the interests of their users. Through peer-to-peer network, UNetwork serves as a decentralized distributed network protocol based on blockchain technology. UNetwork Mainnet "Ustart" is implemented in Golang.
- Scalable Universal Smart Contract (EVM-compatible)
- High Optimization of TPS
- Crosschain Interactive Protocol
- China National Crypto Standard (optional module)
- Distributed Storage and File Sharding Solutions Based on IPFS
- P2P Link Layer Encryption
- Node Access Control
- Configurable Block Generation Time
- Configurable Digital Currency Incentive
- Configable Sharding Consensus (in progress)
The requirements to build UNetwork are:
- Go version 1.8 or later
- Glide (a third-party package management tool)
- Properly configured Go environment
To run UNetwork successfully, at least 4 nodes are required. The four nodes can be deployed in the following two way:
- multi-hosts deployment
- single-host deployment
Can I contribute patches to UNetwork project?
Yes! Please open a pull request with signed-off commits. We appreciate your help!
You can also send your patches as emails to the developer mailing list. Please join the UNetwork mailing list or forum and talk to us about it.
Either way, if you don't sign off your patches, we will not accept them. This means adding a line that says "Signed-off-by: Name " at the end of each commit, indicating that you wrote the code and have the right to pass it on as an open source patch.
Also, please write good git commit messages. A good commit message looks like this:
Header line: explain the commit in one line (use the imperative)
Body of commit message is a few lines of text, explaining things
in more detail, possibly giving some background about the issue
being fixed, etc etc.
The body of the commit message can be several paragraphs, and
please do proper word-wrap and keep columns shorter than about
74 characters or so. That way "git log" will show things
nicely even when it's indented.
Make sure you explain your solution and why you're doing what you're
doing, as opposed to describing what you're doing. Reviewers and your
future self can read the patch, but might not understand why a
particular solution was implemented.
Reported-by: whoever-reported-it
Signed-off-by: Your Name <youremail@yourhost.com>
UNetwork is licensed under the Apache License, Version 2.0. See LICENSE for the full license text.