Improvements to 1.0.1 ⟁ DO NOT USE

V1.0.1 Improvements to ⟁ Ups contract

Important

This is not working in testing, do not use this release. A 1.0.2 release will indicate it is working.

Changes

• Improved README for setup by project owner
• Upvote Refunds = will send back the extra if not an exact multiple of upvote token
• Fixed bug of reward token not being able to be received after contract setup, now must be registered reward token in config + use memo deposit

Notes

This will likely be the final release with single token voting and reward mechanisms (one reward + one upvote token per contract). Future releases may contain different contract table structures and actions, making them incompatible with this release. Please consider carefully if you need to use case of multiple tokens before deploying this version. Always compile the code yourself for security. Contract has not been audited, and should only be used after testing for every possible use case on testnet before deploying and using on main net, at your own risk.

Full Changelog: https://github.com/currentxchange/ups/commits/v1.0.0

Initial Release ⟁

Initial release of the ⟁ Ups contract

• Core functionality as described in readme.me
• Added refunds for transfers that are irregular amounts

Notes:

Functionality of removing a user from the system was partially tested. The contract stores an array of names in the purgatory and purgatory and purg_content fields in the internallog tables when a user has too many records to delete. This part wasn't tested. Contract has not been audited, and should only be used after testing for every possible use case on testnet before deploying and using on mainnet.

Full Changelog: https://github.com/currentxchange/ups/commits/v1.0.0