Absolute Core 0.14.0.1
Products designed by you. Create and configure your own items with the option to log your creation on the Absolute blockchain.
Our goal is to allow you to produce excellent quality products that are designed by you using our online configurator. Certain designs have the choice of being recorded in the Absolute blockchain, allow independent verification that the design you made is unique to you.
Find out more about Absolute: https://absify.me/
The One Protocol is Absolutes goal aiming for there only to be one ABS left in circulation. Although this is unlikely due to the mechanics of supply and demand, it allows us to reward you by reducing supply based on the performance of our business. This makes your holdings absolute more valuable.
On a monthly basis we take 10% of our profit margin to buy and then destroy those collected ABS. This destroyed ABS is sent to specific addresses which are then closed off and hardcoded into the system to make sure that they are never used again. We then use these addresses to offset the max supply calculations.
Find out more about the One Protocol: https://absify.me/one-protocol/
Absolute runs a Governance system maintained by LLMQ based Masternodes which can be serviced via: http://proposal.absify.me/
10% Of blockchain rewards are dedicated to our governance system, these super blocks are issued once per week.
Absolute Technical Details
|Block Time||1.5 minutes|
|Block Reward||30 ABS|
|MN Collateral||2500 ABS|
|Rewards split||Miners 20% and MasterNodes 80%|
|Maximum supply||52.5 M|
|One Protocol (As of v.13)||0.48 M|
|Difficulty retargeting algo||Dark Gravity Wave v3|
For building please see INSTALL / proper files in the doc subfolder.
Masternode install scripts are supported on Ubuntu 18.04 and 20.04
master branch is meant to be stable. Development is normally done in separate branches.
Tags are created to indicate new official,
stable release versions of Absolute Core.
The contribution workflow is described in CONTRIBUTING.md.
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.
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/README.md.
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:
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.
Changes to translations as well as new translations can be submitted to Absolute Core's Transifex page.
Translations are periodically pulled from Transifex and merged into the git repository. See the translation process for details on how this works.
Important: We do not accept translation changes as GitHub pull requests because the next pull from Transifex would automatically overwrite them again.