feat: backend for discussion

[Gift-Naomi]

@tensojka please take a look at what I've done so far. I haven't tested it yet though. I still need to implement the function that resolves starknet address to starknet.id and setup pinata to test it

[tensojka]

Whenever you want another review, re-request review from me please. Thanks

[Gift-Naomi]

@tensojka I've made some changes to the code based on your review. The only thing not working yet is the resolution of starknet.id from address so I commented out the logic for that in ipfs.ts. Please check through and let me know what improvements can be made.

[Gift-Naomi]

Have you tested it? Does Helia give the same hash as IPFS? Is it really async and does it throw an error if it fails?

@tensojka I have tested it out locally and can confirm that all functionalities are operating as expected. However, please note that Pinata requires a premium subscription for pinning by hash. As such, I was unable to fully verify this specific feature. The attached screenshot provides additional context on this matter.

[tensojka]

You can't use pinning by hash – pinning by hash works by Pinata fetching the file according to the hash from IPFS, but we don't want to operate a IPFS node that would serve the file to Pinata. Therefore, you must send the file to Pinata and have them generate the hash. (And check that their hash is the same as the one sent to the client)

[Gift-Naomi]

You can't use pinning by hash – pinning by hash works by Pinata fetching the file according to the hash from IPFS, but we don't want to operate a IPFS node that would serve the file to Pinata. Therefore, you must send the file to Pinata and have them generate the hash. (And check that their hash is the same as the one sent to the client)

Oh okay. Got it!

[Gift-Naomi]

@tensojka I effected the changes you requested. The screenshot below shows that result I got from testing.

[tensojka]

I will get it working tomorrow 👌

[tensojka]

deployed at https://konoha.vote/discussion-api/api/submit