To contact the bounty creator, send a direct message via the SLP Telegram group.
This bounty is for building one or more smart-contracts that provide additional security to token issuers and also allow token issuers to specify a maximum mintable supply cap for their token. Subsequent bounties may expand upon this initial work.
Currently slp-list trusts all data coming from a single SLPDB instance and does not check the results for accuracy. We should be double checking the results using data from other SLPDB instances and a full node as well as utilizing slp-validate to perform an additional validity check. This work will ensure that tools built on top of this library such as a dividend calculator are as accurate as possible.
A high performance SLP Validator is in development as part of the gs++ project. We wish to have this validator exposed as a C library (in-progress), with bindings for popular languages. To do this, we want to use SWIG with our CMake build system to automatically generate bindings in a variety of languages.
SLPDB does not currently use ACID transactions when processing, this can cause temporarily inconsistent state and prevents the ability to rollback on error. A previous attempt at implementing ACID transactions was performed which resulted in reduced stability.
SLPDB currently performs much extra work than needed resulting in reduced performance due to to InsertReplace operations in db.ts. If these were optimized SLPDB could support more transactions per second. In handleMempoolTransaction UpdateStatistics is called which performs a graphInsertReplace, for larger tokens this takes a long time.