As you may be aware we’re currently gearing up to release version 0.0.10 of Omni Core. As part of this process we’re publishing a release candidate preview build and asking you guys to let us know what you think.
This is an exciting time for the team and means finally putting to release an enormous amount of effort from an incredibly devoted group of contributors – people I am truly proud to work with.
Omni Core has always been built on top of Bitcoin Core (it’s a great foundation for us to build upon for which we’re eternally grateful to the bitcoin developers!). As of this release, we have added over 16,000 (yes thousand!) lines of new code to the base Bitcoin stack to deliver the Omni reference client, with over 1,100 commits on the 0.0.10 update alone.
What does this mean? Well, in simple terms it means new stuff. New capabilities such as on-chain feature activation and class C (fully prunable) transactions, new features such as distributed token exchange and a new API, new transaction support (eg “send all”), new consensus systems, new parsing code, new bugfixes, new debugging capabilties, new – well… please feel free to check out the release notes for all the gory details (https://github.com/OmniLayer/omnicore/blob/omnicore-0.0.10/src/omnicore/doc/release-notes.md).
What this also means is that for us to feel confident the code is up to scratch and stable for our partners, users and integrators we need to test. We’re making available a release candidate of Omni Core 0.0.10 so you can help us move that process along by testing the release candidate builds and letting us know about any problems you may encounter. The links for the release candidate builds are below – please do let us know about any problems you encounter here (https://github.com/OmniLayer/omnicore/issues) or if you would prefer not to sign in/up with GitHub you can email email@example.com to submit your thoughts, we are extremely appreciative for any and all feedback.
Downloads for Windows 32-bit:
Downloads for Windows 64-bit:
Downloads for OS X:
Downloads for Linux 32-bit:
Downloads for Linux 64-bit:
The Core development team is very excited to be able to share with you our latest update on the Master Core project.
Our first milestone requested initial functional alpha code for the following:
- Single Currency Support – support for currency ID 1; Mastercoin
- Persistence – the ability to maintain the state between closing down and relaunching Master Core
- Consensus – 100% matching consensus with existing implementations, namely OmniWallet and MasterChest
- send_MP RPC call – the ability to send a Master Protocol currency
- getbalance_MP RPC call – the ability to check an address for the balance of a Master Protocol currency/property
- gettransaction_MP RPC call – the ability to lookup a Master Protocol transaction
- listtransactions_MP RPC call – the ability to list the last n Master Protocol transactions for an address (or * for wallet)
It’s been quite a challenge, but we’re pleased to say we’ve been able to deliver on all of these milestones. The next steps will involve improving on the initial alpha code for the first milestone, along with moving towards our second milestone which, at a high level, is multi-currency support and support for all existing smart property transactions.
If you’d like to get a feel for how these RPC calls are looking so far, I’ve prepared a few examples for your perusal here:
I also wanted to take a quick moment to thank our Core developers, the work ethic is just incredible and I feel extremely privileged to be part of such a hard working and knowledgeable team.
Please note: it is important to us to make sure our readers are aware this is a development milestone and not a release. We’re very proud to have achieved the first alpha code for these functions but it is initial alpha code only – there are still lots of quirks to be worked out, testing to be done, and bugs to be resolved. We would like to caution against any usage outside of testing and development.
Zathras, on behalf of Core Dev