Abelian August Development Update

Over the last month, our development team has been busy with the Abelian code update with the signatures SALRS integration. The progress is a little bit slow due to a problem of storing large keys and signatures with the new Abelian signature scheme.

Progress from August update

● Fully integrated SALRS into the Abelian cryptographic module in the code.

● The code is able to create and sign transactions but can’t verify the signature because of the storage impediment.

● The team is working on migrating the LMDB source to Berkeley DB to test out the storage compatibility on another key-value store.

● Retrieving transaction outputs are not working correctly, because of the DB storage issue.

Hopefully, by the next iteration of the project, we can finish migration from LMDB code to Berkeley DB and do some performance analysis and compatibility.

We welcome direct feedback and ideas and will give a bounty proposal for the scalability problem or the whole codebase as well. Feel free to do some tests and post some improvements if there are any.

Support

To learn more about Abelian and discuss the technical aspects, feel free to connect within one of our official channels below:

Slack: abelian-workspace.slack.com

Telegram: t.me/abeliancoin

Twitter: twitter.com/abeliancoin

Github: github.com/abelian-foundation

Medium: medium.com/abelian