stu 🥪🥞 (@stutxo) 's Twitter Profile
stu 🥪🥞

@stutxo

🔥

ID: 991263989840646145

calendar_today01-05-2018 10:32:06

3,3K Tweet

1,1K Followers

1,1K Following

stu 🥪🥞 (@stutxo) 's Twitter Profile Photo

It’s been one week since our triumphant second place victory at the infamous @plebfi hackathon, and by oh boy what a week it has been. I really did not think it would blow up like this, I was just trying to troll the filter boizz. the way the community has come together to start

It’s been one week since our triumphant second place victory at the infamous @plebfi hackathon, and by oh boy what a week it has been. I really did not think it would blow up like this, I was just trying to troll the filter boizz. the way the community has come together to start
cbspears ◉ (@cbspears) 's Twitter Profile Photo

Imagine you logged off for the weekend because you work for a paper Bitcoin Treasury company and you come back to labitbus.

Imagine you logged off for the weekend because you work for a paper Bitcoin Treasury company and you come back to labitbus.
stu 🥪🥞 (@stutxo) 's Twitter Profile Photo

wrap it before you swap it wrapping looks sorta ok for now, just know the art might break but you dorks don’t seem to care about rarity past the 1k/10k anyway if you're a platform adding wlabitbu, dm me or lifofifo ◉ if you're confused or just lonely

stu 🥪🥞 (@stutxo) 's Twitter Profile Photo

would advise against trying to manually wrap ur labitbu until we have a full sat list i strongly recommend that anyone buying a wrapped labitbu manually track the sat using an explorer like mempool space to confirm provenance for now. fun: some happy miner received a labitbu as

stu 🥪🥞 (@stutxo) 's Twitter Profile Photo

alright so i guess this is happening...you can index labitbu sats with my fork of ord it starts indexing only labitbu pathologies at block 908072 will release sat list after confirming a few things, if you can help with review please take a look 🧡 github.com/labitbu/pathol…

stu 🥪🥞 (@stutxo) 's Twitter Profile Photo

using internal key as an id was most likely a very stupid idea, make sure it’s a NUMS public key (provably unspendable) can use this site to check ty jaonoctus nums-secp256k1.jaonoctus.dev/?pk=96053db5b1…

using internal key as an id was most likely a very stupid idea, make sure it’s a NUMS public key (provably unspendable) 

can use this site to check 

ty <a href="/jaoNoctus/">jaonoctus</a> 

nums-secp256k1.jaonoctus.dev/?pk=96053db5b1…