feat: permits are generated from the calculation results and redirect to the permit claim page

[gentlementlegen]

Resolves #9

Depends on ubiquity-os/permit-generation#10

[gentlementlegen]

Changes in this PR:

The module is now capable of generating permits for the user rewards. It creates the permit and links it inside each user reward information. Last successful run: https://github.com/gentlementlegen/conversation-rewards/actions/runs/8642076491/job/23692567706#step:3:85 You can click on the links to open the reward page.

Later on I believe we want this logic to be moved to the kernel. As they don't communicate yet I thought it'd better to have a first version that is fully autonomous.

Also it currently has a 5 digits precision for rewards, which is maybe not wanted. Let me know if you wanna round number to fewer digits.

Required environment variables to run properly:

• OPENAI_API_KEY
• X25519_PRIVATE_KEY
• SUPABASE_KEY
• SUPABASE_URL

And Knip failing as usual for the same reasons 🤡 and Jest because env variables are not set yet.

[gitcoindev]

Changes in this PR:

The module is now capable of generating permits for the user rewards. It creates the permit and links it inside each user reward information. Last successful run: https://github.com/gentlementlegen/conversation-rewards/actions/runs/8642076491/job/23692567706#step:3:85 You can click on the links to open the reward page.

Later on I believe we want this logic to be moved to the kernel. As they don't communicate yet I thought it'd better to have a first version that is fully autonomous.

Also it currently has a 5 digits precision for rewards, which is maybe not wanted. Let me know if you wanna round number to fewer digits.

Required environment variables to run properly:

• OPENAI_API_KEY
• X25519_PRIVATE_KEY
• SUPABASE_ANON_KEY
• SUPABASE_URL

And Knip failing as usual for the same reasons 🤡 and Jest because env variables are not set yet.

Good catch! I will fix this repository Knip asap, also review the pr today.

[gitcoindev]

Knip config fixed at #11 I am reviewing this pull request now.

[gitcoindev]

I added a few comments to clarify, but overall the pull request is very useful. Good job! I think it would be useful to add documentation about releases, perhaps an automated label in README.md would be fine and add the documentation on generating rewards on different network ids.

[0x4007]

Why five digits of precision? The industry standard is 18.

[molecula451]

looks like 2 npm packages are in conflict @gentlementlegen

[gentlementlegen]

Why five digits of precision? The industry standard is 18.

I am using 18 digits, I meant that the final result can potentially be 4.1654627 WXDAI for example, and I don't recall having such results with the version we have currently for calculating the total.

[whilefoo]

code looks good

[gentlementlegen]

I noticed now that cspell checks are failing (due to unkown word SUPABASE) but I notice just now because this workflow does not run on PRs.
https://github.com/ubiquibot/conversation-rewards/actions/runs/8717404761/job/23912565868#step:5:62

Might wanna consider have it rolling on pull_request as well. I don't know if this was a choice due to the secrets not being populated.

[0x4007]

You can add words to cspell config. Sure you should run on pulls.