UFOHub is a decentralised digital currency with near-instant transaction speeds and negligible transaction fees built upon Proof of Stake 3.0 (PoSV3, BPoS) as introduced by the UFOHub development team.
For more information about UFOHub itself, see https://ufohub.org.
UFOHub is the name of open source software which enables the use of this currency. It takes UFOHub to the next level by building upon Bitcoin Core 0.13.2 with some patches from newer Bitcoin Core versions to offer performance enhancements, wider compatibility with third party services and a more advanced base.
For more information, as well as an immediately useable, binary version of the UFOHub software, see https://www.ufohub.org.
UFOHub is released under the terms of the MIT license. See COPYING for more information or see https://opensource.org/licenses/MIT.
Twitter: https://twitter.com/UFOHub_org Discord: https://discord.gg/NavtdhvwUU FaceBook: https://www.facebook.com/people/UFOHuborg/61552495190836/ Youtube: https://www.youtube.com/@UFOHub_org Website: https://www.ufohub.org/
addnode=116.203.64.255
The master branch is regularly built and tested, but is not guaranteed to be
completely stable. Tags are created
regularly to indicate new official, stable release versions of UFOHub.
Change log can be found in CHANGELOG.md.
The contribution workflow is described in CONTRIBUTING.md.
Testing and code review might be the bottleneck for development. Please help out by testing other people's pull requests, and remember this is a security-critical project where any mistake might cost people lots of money.
Developers are strongly encouraged to write unit tests for new code, and to
submit new unit tests for old code. Unit tests can be compiled and run
(assuming they weren't disabled in configure) with: make check
There are also regression and integration tests of the RPC interface, written
in Python, that are run automatically on the build server.
These tests can be run (if the test dependencies are installed) with: qa/pull-tester/rpc-tests.py
The Travis CI system makes sure that every pull request is built for Windows, Linux, and OS X, and that unit/sanity tests are run automatically.
Changes should be tested by somebody other than the developer who wrote the code. This is especially important for large or high-risk changes. It is useful to add a test plan to the pull request description if testing the changes is not straightforward.