Describe the solution you'd like

Bounty submission and tipping system for the tipbot

Add the ability to create and vote on plus sponsor activities through a bounty system. Tipbot tracks the bounty details, votes, and donations. Once bounty is completed the bot will pay out the contributor that completed the task.

Set it up so that only Discord moderators can create and complete the bounties. Once a bounty is created any user can vote on and donate to the bounty from the tipbot account. A contributor can submit a completed task to more than one moderator with proof and the moderators vote to pay out the bounty. Once the bounty payout has received 2 votes it pays out.

Requires a few new commands or one large multiplexed command

• bounty-create
• bounty-vote
• bounty-fund
• bounty-submit
• bounty-verify

Initiation

• Only a moderator or higher can submit a new bounty or close one.
• to open one must give { BOUNTY_NAME, ITERATIONS or PAID_IN_FULL, TTL, PAYOUT, INITIATOR, DESCRIPTION }
  • Bot will open a new entry in DATABASE.TABLE for the bounty, assign an ID, and create an entry in the bounties page {qrl.tips website repo}
  • Users can send tips to the bounty, using name or ID to help fund and give incentive
  • Users can also simply vote on the bounty, adding importance to the task, giving better insight to what the community wants worked on first

Submission

• When a user believes they have completed a bounty, they send a message to the bot which notifies a moderator or core member, with some proof of completion {link to work, repo, photo, description etc.}
  • Moderator reviews the task complete and the bounty, and upon approval sends a bounty-verify approval with {users ID, bounty ID,
  • Once 2 mods or admin agree on the completion the bot sends funds to the users tipbot address

Stale Bounties

• If no users complete the task in allotted TTL the bot returns the tipped funds to...
  • The users who donated?
  • Sends them to a general bounty fund?
  • Sends them to the faucet?

Database New tables

Added tables to the database to track the bounty system

bounty

Table to hold the bounty information

+-----------------+--------------+------+-----+---------+----------------+
| Field           | Type         | Null | Key | Default | Extra          |
+-----------------+--------------+------+-----+---------+----------------+
| id              |              |      |     |         |                |
| bounty_name     |              |      |     |         |                |
| mod_id          |              |      |     |         |                |
| guild_id        |              |      |     |         |                |
| payout_limit    |              |      |     |         |                |
| payout_min      |              |      |     |         |                |
| ttl             |              |      |     |         |                |
| initiating_user |              |      |     |         |                |
| description     |              |      |     |         |                |
| active          |              |      |     |         |                |
| status          |              |      |     |         |                |
| time_stamp      |              |      |     |         |                |
+-----------------+--------------+------+-----+---------+----------------+

bounty_votes

Table to hold the votes users send

+------------+--------------+------+-----+---------+----------------+
| Field      | Type         | Null | Key | Default | Extra          |
+------------+--------------+------+-----+---------+----------------+
| id         |              |      |     |         |                |
| bounty_id  |              |      |     |         |                |
| user_id    |              |      |     |         |                |
| vote       |              |      |     |         |                |
| time_stamp |              |      |     |         |                |
+------------+--------------+------+-----+---------+----------------+

bounty_fund

Table to hold the users fund information. If user dictates they can leave any un-spent funds to be donated to the faucet.

Any use that is no longer active or banned after placing bounty funds forfeits their funding contribution.

All fees are taken from the contribution upon returning.

+-------------+--------------+------+-----+---------+----------------+
| Field       | Type         | Null | Key | Default | Extra          |
+-------------+--------------+------+-----+---------+----------------+
| id          |              |      | PRI |         |                |
| bounty_id   |              |      |     |         |                |
| user_id     |              |      |     |         |                |
| fund_amount |              |      |     |         |                |
| donate      |              |      |     |         |                |
| time_stamp  |              |      |     |         |                |
+-------------+--------------+------+-----+---------+----------------+

bounty_submissions

Table to hold the submissions for a user to collect funds. Requires 2 entries from seperate moderators or core members

+-------------+--------------+------+-----+---------+----------------+
| Field       | Type         | Null | Key | Default | Extra          |
+-------------+--------------+------+-----+---------+----------------+
| id          |              |      | PRI |         |                |
| bounty_id   |              |      |     |         |                |
| mod_id      |              |      |     |         |                |
| sub_user_id |              |      |     |         |                |
| proof       |              |      |     |         |                |
| time_stamp  |              |      |     |         |                |
+-------------+--------------+------+-----+---------+----------------+

Bounty_payout

Table to hold the information from contribution payouts

+--------------+--------------+------+-----+---------+----------------+
| Field        | Type         | Null | Key | Default | Extra          |
+--------------+--------------+------+-----+---------+----------------+
| id           |              |      |     |         |                |
| bounty_id    |              |      |     |         |                |
| paid_user_id |              |      |     |         |                |
| tx_id        |              |      |     |         |                |
| time_stamp   |              |      |     |         |                |
+--------------+--------------+------+-----+---------+----------------+

Describe the bug

When a user has signed up with discord and gives a utf-8 type symbols in a username the MySQL database cant process and fails.

To Reproduce

Steps to reproduce the behavior:

1. Either by signing up with utf-8 in username or tipping a user who has this condition in place.
2. see that the bot no longer responds to a message

Expected behavior

User added to database accordingly or a future tip sent with user name as shown stored

What would you like improved?

After a period of time, (15min?), clear the inline tipbot confirmation messages when sending a tip.

Improvement

It seems that the tipbot messages are there to indicate a successful transfer, but after they are read, they served its purpose. Beyond that, for record keeping, a message is also sent in the DM.

Should a public way to indicate a tip is sent be still desired, a cleaner way could be to add an emoji to the person tipping when it's been complete.

Describe the bug

The private message for +random output is missing some information

To Reproduce

Steps to reproduce the behavior:

1. enter +random in the chat
2. Read DM and see it is missing information "...public blockchain to the , helping make..."

Expected behavior

Expected the sentence to read "...public blockchain to the drand network, helping make..." with drand network linking to the https://drand.love site

Screenshots

Describe the bug

When user already has an account, and they attempt to sign up again the DM message with the users address is incorrect. Leads to https://explorer.theqrl.org/a/undefined

To Reproduce

Steps to reproduce the behavior:

1. sign up to the bot
2. sign up again to the bot
3. observe the link provided under address field is undefined

Expected behavior

Link to user wallet in the QRL explorer

Screenshots

Describe the solution you'd like

Allow the ability to tip a role, sending that amount of tip to each user in the role if tipping user has the balance.

example +tip @developer to send a tip to all users in that role.

Describe alternatives you've considered

Alternative is typing out each user in the chat window

Additional context

Transactions are limited to 100 receiving addresses and if the role is over this amount the bot will either need to split into 2 transactions or deny the request.

Describe the bug

Certain amounts when tipping results in the error: "Invalid Amount Given", when it is a completely valid amount (a positive Float of between 10^-9 and 105000000 QRL)

To Reproduce

Steps to reproduce the behavior:

1. Go to the QRL Discord
2. Enter the values 64.01, 32.307, 32.258, or 4.2288 as a tipbot amount
3. See error

Expected behavior

No error with the transaction going through

Screenshots

Environment

• Discord linux application

What would you like improved?

Add message functionality to the +tip command, adding optional message text to the transfer transaction on-chain.

Improvement

Add a way to append a message to the tip transaction giving a user ability to send textual messages on-chain through the tipbot. Message should have some delineation from the tip command to indicate to the bot the message should be sent with the tip.

Possible examples:
+tip @fr1t2 1 msg: MESSAGE TEXT TO SEND, MAX 80 bytes
+tip @fr1t2 1 {MESSAGE TEXT TO SEND, MAX 80 bytes}

Requires:

• Additional parsing of the message sent from users
• Validation and sanitation of text entered
• Additional field for message in the tips database
• A deliminator to signify a message is to be sent.
• Additional checks for message length
• Procedure for message over length
  • Strip additional text
  • Fail entire tip
  • Send tip without message
• Additional function to the send transaction function to add message text

Is this improvement request related to a Bug Report?

no

Right now when someone issues a the +faucet command when they've already withdrawn within a 24 hour period, it responds back with the information that they've already pulled from the faucet recently.

As it can be difficult to discern when the faucet will be ready to pull from again, adding a timer to the faucet response to indicate the next time someone can initiate the faucet command would help.

Suggested by Discord user MrTr3

What would you like improved?

Add the optional argument outputs to the help for +info when you enter the +help command

Currently the help output only states .info - Information about this bot and the QRL Network

Improvement

Would like to have all of the various arguments to give user an idea of what the command can do

Better output can be found with +help infoThis information should be added to the general help output args: {market | exchange | faucet | bot | user | qrl}