
ordinal-devs
/ordinal-devs249
technical discussion of bitcoin ordinals
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
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
some level of cooking necessary behind the scenes to be able to then cleanly write this code
bitflick
bitflick
flick has been putting their engineer hat on:
- all unit tests pass and are being run on every push via gha
- added a docker-compose.yml to bring up the entire backend + localstack for supercharged local dev
- nailed down the backend errors breaking inscriptions
I think I get to focus on www now.
LET'S FUCKING GO
- all unit tests pass and are being run on every push via gha
- added a docker-compose.yml to bring up the entire backend + localstack for supercharged local dev
- nailed down the backend errors breaking inscriptions
I think I get to focus on www now.
LET'S FUCKING GO
6097
flick the dev 🎩📦
@flick·16:16 20/04/2025
Ended up needing to make a bitcoin/electrs/mempool docker compose w/ local dymanoDB and s3rver (S3) jest test in order to nail down why these different kinds of transactions would seemingly fail as I made changes.
42s of bitflick tests I no longer need to run manually (worth it)
On the plus side, there is now a docker-compose.yml that stands up bitcoind, electrs, and the mempool stack. It works while connected to the local backend! No more spinning these things up one at a time in tmux like a goofus.
https://github.com/0xFlicker/ordinals/tree/main/packages/test
42s of bitflick tests I no longer need to run manually (worth it)
On the plus side, there is now a docker-compose.yml that stands up bitcoind, electrs, and the mempool stack. It works while connected to the local backend! No more spinning these things up one at a time in tmux like a goofus.
https://github.com/0xFlicker/ordinals/tree/main/packages/test
Ended up needing to make a bitcoin/electrs/mempool docker compose w/ local dymanoDB and s3rver (S3) jest test in order to nail down why these different kinds of transactions would seemingly fail as I made changes.
42s of bitflick tests I no longer need to run manually (worth it)
On the plus side, there is now a docker-compose.yml that stands up bitcoind, electrs, and the mempool stack. It works while connected to the local backend! No more spinning these things up one at a time in tmux like a goofus.
https://github.com/0xFlicker/ordinals/tree/main/packages/test
42s of bitflick tests I no longer need to run manually (worth it)
On the plus side, there is now a docker-compose.yml that stands up bitcoind, electrs, and the mempool stack. It works while connected to the local backend! No more spinning these things up one at a time in tmux like a goofus.
https://github.com/0xFlicker/ordinals/tree/main/packages/test
introducing the state necessary for a cloud deployment did break things, then flick went in circles making updates, breaking reveals or state management.
decided to take a step back and do something I've been wanting to do: an end-to-end inscription test, using dynalite and a mock s3, to keep things fixed.
bitflick
decided to take a step back and do something I've been wanting to do: an end-to-end inscription test, using dynalite and a mock s3, to keep things fixed.
bitflick
was hoping this would at least be working by now, unfortunately have to put away as-is to attend to life things like taxes
still debugging lambdas and generally cleaning up vibe coding mess. more metrics and alarms to add. it does things.
everything updated at https://github.com/0xFlicker/ordinals
bitflick
still debugging lambdas and generally cleaning up vibe coding mess. more metrics and alarms to add. it does things.
everything updated at https://github.com/0xFlicker/ordinals
bitflick
it's friday which means we close up shop at work and move into passion projects
new bitflick inscription backend was looking pretty hot last weekend, with portions deployed and IIRC everything compiling and tests passing
connecting to an EVM frame is a little extra, but well understood problem
UI still needs work
new bitflick inscription backend was looking pretty hot last weekend, with portions deployed and IIRC everything compiling and tests passing
connecting to an EVM frame is a little extra, but well understood problem
UI still needs work
inscribing an ordinal from a farcaster wallet from an EVM payment
will be what I work on after I deploy
which is what I will be working on for saturday
bitflick
will be what I work on after I deploy
which is what I will be working on for saturday
bitflick
spring cleaning done, back at it with bitflick
currently inscribing on launchpad locally and working on connecting the creator bits (flick loves creators and wants them to be paid)
next up is finishing the fc miniapp, and finally deploying for realsies
BOOM: lazy buyer-pays creator-first launchpad on BTC
currently inscribing on launchpad locally and working on connecting the creator bits (flick loves creators and wants them to be paid)
next up is finishing the fc miniapp, and finally deploying for realsies
BOOM: lazy buyer-pays creator-first launchpad on BTC
there is a balance fick is trying to strike when it comes to parent inscriptions.
ultimately they belong to the creator but bitflick backend also needs to be able to spend them
right now it is full custody of the backend while being made available for child inscriptions, but would like to move to tapscript that lets the creator also withdraw with a timelock
ultimately they belong to the creator but bitflick backend also needs to be able to spend them
right now it is full custody of the backend while being made available for child inscriptions, but would like to move to tapscript that lets the creator also withdraw with a timelock
I regret to inform you that my mother is coming to visit for the first time in awhile and so I will not be working on bitflick this weekend to focus on house cleaning 🧹
Definitely hit another complexity wall with semi-custodial access to parent inscriptions for purposes of lazy child inscription.
Been rolling with is a 1of2 taproot where one private key can stay with the user in secure local browser storage and the other stays with the platform.
Lots of FE/BE/Security pieces here
Been rolling with is a 1of2 taproot where one private key can stay with the user in secure local browser storage and the other stays with the platform.
Lots of FE/BE/Security pieces here
3 minters, each minting 3 inscriptions, has their genesis payments revealed together and paired with the parent inscription, each inscription then sent to final owner
parent inscription remains with platform to re-use on next batch
efficiencies captured as a platform fee
bitflick is actually getting somewhere
parent inscription remains with platform to re-use on next batch
efficiencies captured as a platform fee
bitflick is actually getting somewhere
now that I moved (again) settled in, launched a dao, been looking at bitflick again. finishing the bits where anyone can go in and launch a collection.
so that I can launch a collection
vs hard coding stuff
so that I can launch a collection
vs hard coding stuff

