Dev Aloft

@_CRFTD_ @__proper @lifofifo @ordinalsbot @trio_xyz @rodarmor @unisat_wallet @satingio @gm7t2 @ChiselXYZ No worries, either works, and no rush! Ready to assist whenever you're ready, and feel free to DM.

@devaloft @__proper @lifofifo @ordinalsbot @trio_xyz @rodarmor @unisat_wallet @satingio @gm7t2 @ChiselXYZ Okay gotcha, yeah it’d be on Block 9s I already own (not consecutive)—but would be open to just holding on to them if y’all also provide the option to purchase rares from your site as well. Once I can get back to my computer, I’ll hop into y’all’s site to check things out.

Hello inscription friends... @lifofifo @ordinalsbot @trio_xyz @rodarmor @unisat_wallet @satingio Any chance this tooling exists...or will? The one by ones are kill'n me.

@_CRFTD_ @__proper @lifofifo @ordinalsbot @trio_xyz @rodarmor @unisat_wallet @satingio @gm7t2 @ChiselXYZ Thanks! If you're trying to inscribe rare sats in bulk that are already in your possession, it will require a little bit of special prep, but it's easily done and won't take long.

@devaloft @__proper @lifofifo @ordinalsbot @trio_xyz @rodarmor @unisat_wallet @satingio @gm7t2 @ChiselXYZ Oooooh! Will check y’all out. Thanks!!

@__proper @lifofifo @_CRFTD_ @ordinalsbot @trio_xyz @rodarmor @unisat_wallet @satingio @gm7t2 @ChiselXYZ Indeed that is true. How can I help, @_CRFTD_?

@lifofifo @_CRFTD_ @ordinalsbot @trio_xyz @rodarmor @unisat_wallet @satingio @gm7t2 Pretty sure you can do this on @ChiselXYZ?

@lifofifo @kfzbtc @OGsatoshis Nah, that would be boring.

@devaloft @kfzbtc @OGsatoshis Ah nice. I thought it was just setting nlocktime on reveal tx.

⏲️ Timelocks 🤝 Ordinals 🔐 Bitcoin Tapscript enables smart contracts to lock UTXOs until a specified block height or time, making self-custodial staking possible for Ordinals and Runes. Yet, timelocking remains rare in the Ordinals space. This is mainly due to: ⛔️ Lack of standards around locking scripts ⛔️ No clear links between the locking address and your Ordinals address ⛔️ Limited wallet support for signing with a tweaked pubkey For timelocking to be more approachable and usable, there’s still plenty of work to be done. But I wanted to make some basic features available for anyone looking to experiment and get the ball rolling. ➔ tx.dev/utxo/timelock 🪄 Generate a timelock address for any Ordinals address 🪄 Unlock a timelocked UTXO (only @unisat_wallet) The process is simple: ⌛️ Generate a timelock address for a specific block height ⌛️ Send Inscriptions or Runes to the timelock address ⌛️ Unlock the UTXO one at a time once the timelock conditions are met If you're experimenting, tag me in @TheWizardsOfOrd holders chat 🧙‍♂️

@lifofifo @kfzbtc @OGsatoshis That transaction's spending a utxo with an OP_CLTV.

@kfzbtc @OGsatoshis This isn't the same thing. Setting `nlocktime` only prevents TX inclusion in a block. It doesn't prevent UTXOs from being spent in other tx.

@Ordinals10K @interfaceChiral Yes, provenance is a concept entirely orthogonal to satoshi binding, so you can easily have unbound children. However, you cannot have children of unbound inscriptions because they're non-transferable.

@interfaceChiral @devaloft Always interested to know more about this, let's see what Dev Aloft says. 🫡

You can quite easily obtain a piece from most of the top Ordinals artists right now - the same cannot be said for 🍋, and that’s by design. But only time will tell what approach was right (and IMO it’s more than likely that many different approach can work), as it would be wrong to claim that scarcity alone drives value. Truth is, there’s a lot of intricacies at play.

@rodarmor @billyrestey Custody here only being necessary so the address remains constant. The relinking could be done by anybody, enabling that flexibility.

@rodarmor @billyrestey While still subject to too-long-mempool-chain, if the platform custodies the parent, it would allow the parent input utxo to be relinked automatically depending on confirmation order or in case of an RBF.

Why don't marketplaces support parent-child collections? Parent-child collections are superior in important ways: - No need to submit JSON metadata for approval to every marketplace. - Appear as a collection in any `ord` instance, which includes ordinals.com. - Children cannot be removed from collections. - The parent can be burned, which guarantees that more items won't be added to the collection later. - Generational provenance: Creators can create a root inscription whose child inscriptions serve as parents for multiple collections, so multiple collections can be tied together as being created by the same person. It even benefits marketplaces! Less code, less moderation, less support. How can I highlight inscriptions which make good use of features like parent child, attractive on-chain metadata, and sat names? These are all things which are unique to inscriptions, and I think we should all want to see more of.

@billyrestey @rodarmor Funnily enough, it would be feasible if we had something akin to SIGHASH_APO.

@rodarmor tons of ppl inscribing simultaneously in a short time period—passing around the parent just wouldn’t have worked. although I agree it is a great standard

@ZedZeroth @thatwagmigirl @satingio @luminexio @ordinalsbot @ChiselXYZ Are you by any chance using the Bring Your Own satoshi option? I do indeed charge more for that one.

@devaloft @thatwagmigirl @satingio @luminexio @ordinalsbot @ChiselXYZ Seems to be a similar $10 markup like the other platforms?

It currently costs less than $1 to inscribe a parent-child micro-inscription via your own local ord setup. But @satingio & @luminexio are both charging close to $15, a 1000%+ markup, all while bitcoin fees themselves are lower than ever. @ordinalsbot are cheaper but don't offer parent-child on rare sats. These limitations in user inscription tools represent the biggest barrier to #OrdinalsGamification 🫤

@pawellwitt @huuep @ChiselXYZ Yup, exactly. It would probably end up being two inscription transactions that Chisel would create automatically, and the second one would return the parent to you.

@devaloft @huuep @ChiselXYZ Got it, thank you. Ok so let’s assume I’d like to inscribe a collection with 1k items using recursion - how would it work? I would need to send you Parent inscription and 1k svg files to inscribe as its children? (Traits would be inscribed separately)

Parent-Child Provenance is the alpha. Unlike smart contract chains like Ethereum, Bitcoin’s decentralized architecture requires a very different design for NFTs. Ordinals is an NFT protocol that does not require smart contracts and aligns with Bitcoin’s core design. Without smart contracts, it's a challenge to create a COLLECTION on Bitcoin. In fact, Ordinals launched in 2023 without a way to actually create a collection on-chain in a decentralized and immutable way. Eventually, Parent-Child Provenance was implemented and became the collection standard of Ordinals. Today, Parent-Child Provenance is still underappreciated. Understanding it begins with understanding Bitcoin. Artists and collectors will benefit by reading the Bitcoin white paper. The Bitcoin revolution is coming.🔥

@thatwagmigirl @ZedZeroth @satingio @luminexio @ordinalsbot @ChiselXYZ Usually $5 per order, but it should amortize in bulk for larger orders.

@ZedZeroth @satingio @luminexio @ordinalsbot What of @ChiselXYZ ?

@pawellwitt @huuep @ChiselXYZ Ah gotcha, nope, that is still the case to simplify bulk inscriptions, where the operation may require multiple transactions and the parent getting automatically passed from one to the next.

@devaloft @huuep @ChiselXYZ Hey, thanks for reaching out. Not really technical issues. Just the fact the we’d have to send each inscription to you to inscribe it. Or has it changed and there’s an easier way now?

@pawellwitt @huuep @ChiselXYZ Hi there, creator of Chisel here. May I ask what issues you run into with bigger collections? Anything I can do to make the experience easier? Thanks so much for using Chisel!

@huuep @ChiselXYZ Thanks. I did try using @ChiselXYZ and it works well if I need to inscribe one or two inscriptions but making a collection could be problematic. Still learning how to do myself 😁

@Elocremarc Why is metadata limited in size?

Delegate inscriptions can themselves have unique inscriptions inside their envelopes. These inscriptions are inaccessible! What if you could access this data? Introducing "/r/delegator/:id" Currently when you create a generative engine like I did with Blob you can only seed generation with unique data from the onchain metadata. Each blob is unique because it seeds the blob engine from its metadata. Each blob inscription has no content inscribed only metadata making them incredibly efficient at using blockspace. However metadata is in CBOR and is limited size. This limits your options. However with "/r/delegator/:id" you get the entire content of the inscription which could be a large file maybe even 4mb. You could use this to inscribe file types not supported in the browser. How? You create a rendering engine for the file type as the delegate and in the content of the delegator you put the file. Then anyone who wants to render that filetype can simply delegate the rendering engine. github.com/ordinals/ord/p…

@marshallmixing @udiWertheimer Have you written an auto-reply script yet?

@udiWertheimer DAY 184: Cats have vertical slit-shaped pupils that help them see in dim light. This adaptation allows them to control the amount of light entering their eyes more effectively than round pupils.

last person to reply to this tweet gets a taproot wizard

@NICOBAR_86 @ChiselXYZ @Dyo0r Dime si necesitas ayuda o preguntas sobre usar la API.

@devaloft @ChiselXYZ 🥹 justo que busco para el lanzamiento de @Dyo0r

By harnessing the power of envelope concatenation, batch inscription orders on common satoshis can now see a mining fee reduction of up to 70% when using @chiselxyz! How is this possible?

@cbspears @ChiselXYZ But, to give a little overview of some other changes: Xverse support for sending parents, client-side order history storage, anchor outputs in commitment transactions, collection manifests, transaction hex downloads for unbroadcast transactions (locktime/etching/nonstandard), …

@devaloft @ChiselXYZ Yoooo! Welcome back into Ordinals!

@cbspears @ChiselXYZ "Back?"I never left 😉 A bunch of other improvements just didn't warrant Twitter announcements :)

However, for common satoshis, all revelation transactions will now only include one input. And thanks to opportunistic batching, this means that you can now make 10,000 (or more!) common-satoshi inscriptions in a single order! Happy inscribing!

Typically, the expensive component of a bitcoin transaction is its inputs, as besides specifying a 36-byte-outpoint, each usually also has a 64-vByte-signature. Chisel's unique algorithm for selecting arbitrary-offset satoshis preclude applying this technique to non-common sats.