thank you chatgpt for your part in making this policy change be least access principle aligned, features encryption at rest, and bitflick backend is now fullstack ARM including all of bitcoin

ordinal-devs

Bitflick exists on 3 cloud providers: vercel (frontend) / AWS (S3/lambdas/dynamodb/sqs/misc) and Akamai for long running services (bitcoind/electrs/mempool/ord)

Previously I only talked to mempool. It was fine for me to add a nginx auth, add a header to mempool requests and call it a day

Now I talk directly to bitcoin rpc and electrs and so now I just want to have the services on my AWS VPC

So I made my first site-to-site VPN from the VPC in AWS to a VPC I have set up in Akamai. Wondering how much that will eat up the savings from running stuff in Akamai 

Anyhoo, everything is deployed (99% from code!), we are just getting everything talking to each other 

bitflick

So now Bitflick is on 2 cloud providers. Vercel + AWS. It was educational to put together a site-to-site VPN but the additional AWS+Akamai costs eliminated all savings from running long running instances on Akamai

tl dr; decided to do a thing (High Availability BTC w/ Snapshots)

So now Bitflick is on 2 cloud providers. Vercel + AWS. It was educational to put together a site-to-site VPN but the additional AWS+Akamai costs eliminated all savings from running long running instances on Akamai

tl dr; decided to do a thing (High Availability BTC w/ Snapshots)

https://warpcast.com/flick/0x26a7e510

This is a perfectly normal backend, and with the new JsonRpc microservice everything can now talk to bitcoin