backend revamp

[617a7aa]

created api project and scheduled-send-manyproject.
both are CF workers which will replace the current backend.
api is the HTTP API for frontend
scheduled-send-many is a scheduled worker which will run every 2 minutes and can send up to 100 airdrops per minute

this will initially be able to send up to 1000 airdrops every 10 minutes, an improvement of 40x, but is able to be expanded to 2000 every 10 minutes (80x)

[314159265359879]

For as far as I understand this, it looks good to me. Lets stress test this again with an at Everyone in discord when it is live?
Maybe @cryptopanter can do an actual code review if that is needed?

[314159265359879]

Deploying with Cloudflare Pages

Latest commit: 048629b
Status: ✅ Deploy successful!
Preview URL: https://5100cd27.nothing.pages.dev

View logs

Should I be able to use this faucet? or not yet connected?
I get the "try again later" error.

[617a7aa]

thank you @314159265359879 for your review. this PR is still a draft and is not ready for deployment yet. the faucet preview website deployment hasn't been changed so it should still work if the main one does.

frontend hasn't been updated to use the new backend because backend is still failing tests. will connect frontend up when the backend works lol

[617a7aa]

this PR is inactive for now. it requires a library which is in the works, but not fully live yet. using the @stacks/* libraries in a worker is really tough.

i'm having issues with them compiling to unsafe evals which workers won't allow in the runtime. waiting for the lightweight esm-based library from @aulneau for this to happen.

for the meantime, we could potentially start work on the frontend UI but that will require @syvita/design to do some mockups - we're currently working on daoOS primarily, so this may get postponed for a while.

[617a7aa]

[cryptopanter]

this PR is inactive for now. it requires a library which is in the works, but not fully live yet. using the @stacks/* libraries in a worker is really tough.

i'm having issues with them compiling to unsafe evals which workers won't allow in the runtime. waiting for the lightweight esm-based library from @aulneau for this to happen.

for the meantime, we could potentially start work on the frontend UI but that will require @syvita/design to do some mockups - we're currently working on daoOS primarily, so this may get postponed for a while.

What's wrong with Stacks library?... And let me know when it's ready for test 🎩... Btw, should Huzz also join this repo?

[617a7aa]

What's wrong with Stacks library?

it's not designed for something as locked down as a webworker. their runtimes are significantly different from other runtimes that the stacks libraries are used for (websites, node etc)

Btw, should Huzz also join this repo?

he can if he wants to work on it!