You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
npq7721 c136d2b745
Merge pull request #213 from Raptor3um/develop
5 days ago
.github Ft/fix sn not getting contributions (#211) 5 days ago
.settings add fee structure by spork for future 1 year ago
.tx rebranch, implements founder, smartnode collaterals 2 years ago
build-aux/m4 Fixed linker error with Windows cross-compilation. Fixed 32/64 bit issue with windows build. Minor cleanup. 6 months ago
ci v17 9 months ago
contrib clean up (#177) 2 months ago
depends Fix libbacktrace compile on alpine/musl arch. 5 months ago
doc > 1 week ago
docker v17 9 months ago
share v17 9 months ago
src Ft/fix sn not getting contributions (#211) 5 days ago
test Fixed handling and documentation for blocksdir. Pulled in from Bitcoin #14364 and #14409 (#189) 4 weeks ago
utils Build related fixes and typos correctnes 10 months ago
.gitattributes Separate protocol versioning from clientversion 8 years ago
.gitignore testnet4 (#138) 6 months ago
.gitlab-ci.yml CI: Fix Gitlab nowallet and release builds (#3491) 11 months ago
.travis.yml v17 9 months ago
CMakeLists.txt v17 9 months ago clean up dash reference to raptoreum 6 months ago
COPYING fixed testnet getblocktemplate error and update Copyright year 11 months ago rebranch, implements founder, smartnode collaterals 2 years ago add file and build.yaml workflow 6 months ago Update (#212) 5 days ago Merge #13454: Make sure LC_ALL=C is set in all shell scripts 2 years ago Ft/fix sn not getting contributions (#211) 5 days ago Ft/fix sn not getting contributions (#211) 5 days ago rebranch, implements founder, smartnode collaterals 2 years ago

Raptoreum Core Latest v1.13.17.01

CI master develop

The name Raptoreum is derived from the Victorian term for a bird of prey and ium/eum place for a pertaining to in this case birds of prey. The name comes from the team’s extensive experience in the security field with top level skills covering all aspects of it. This is a unique strength in the crypto community and will leverage well into a successful project.

Introduction Raptoreum began as the fairly simple idea, introducing smart contracts which would allow on chain, trustless transfers (goodbye centralized marketplaces) on the Ravencoin codebase, however with the automation of assets and RTM (Raptoreum). The project has quickly evolved, adding innovative features that not only further expand the asset layer, but also introduce features that could help other Blockchain projects. Ravencoin unfortunately suffered several serious breaches of its asset layer so that code base has been abandoned by us. We are currently working with and building on Raptoreum code expending its capabilities significantly.

Raptoreum is now a code fork of Dash and inherits current and optionally future features such as chain locks, oracles etc. We are further expanding capabilities by adding the following features: A) The deployment of a unique asset layer. B) The option to lock X amount of coins or assets into a special transaction. Coins are unlocked at a block number of choice or timestamp. C) Trustless on chain transfers of assets and native coins VIA Smart Contracts. D) Integrating, developing and deploying a VM protocol that would allow for smart contracts in 4 major programming languages as opposed to the situation with Ethereum being limited to solidity.

These additional features open up the power and ease of use of Raptoreum’s features to a greater variety of industries under the Distributed Application umbrella. DAPP's are a critical part of driving widespread adoption as recently seen with DEFI and Raptoreum hopes to help provide further alternatives and possibilities for DAPP developers particularly in the field of opening up new programming languages for DAPP and contract development.

It is one of our goals to not only innovate ideas for Raptoreum but to contribute back to the general crypto community with open-source features that anybody can use to help their Blockchain projects succeed.


Raptoreum Core is released under the terms of the MIT license. See COPYING for more information or see

Development Process

The master branch is meant to be stable. Development is done in separate branches. Tags are created to indicate new official, stable release versions of Raptoreum Core.

The contribution workflow is described in


Testing and code review is the bottleneck for development; we get more pull requests than we can review and test on short notice. Please be patient and 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.

Automated Testing

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. Further details on running and extending unit tests can be found in /src/test/

There are also regression and integration tests, written in Python, that are run automatically on the build server. These tests can be run (if the test dependencies are installed) with: test/functional/

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.

Manual Quality Assurance (QA) Testing

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.