dev9

[dev9 @Bitmapbuilder]

What is a hyperstructure and why? 🟧The Metaverse #Bitmap

https://t.co/gsJKjYiTlv

[Casey @rodarmor]

Ord 0.29.1 is now available! A couple of notable changes:

- Correctly deserialize Bitcoin Core RPC responses containing anchor outputs

- New recursive endpoint `/r/block/<QUERY>` that returns the entire block

Share and enjoy!

https://t.co/LMkqMVDyE6

[dev9 @Bitmapbuilder]

🚁💯💯💯

🦒
🟧🟧🟧🟧🟧🟧🟧🟧🟧🟧🟧🟧🟧🟧🟧

[9 @block9ine]

This might genuinely be the biggest update to happen in Bitmap.

Blixworld now subscribes to the Bitmap Live OCI(onchain index), built by @boppleton . We’ve integrated it, tested it, and it’s ridiculously fast.

Let me explain why I think this is such a big deal 👇

We built an entire data pipeline to keep Blix up to date with Bitmap. As a builder, you need reliable data. You need to know what exists, what’s changed, and where the chain is right now.

Now, we can plug into a live on-chain index and get the data we need, right up to the tip of Bitcoin, yes, the latest block.

Think about that for a second.

An evolving collection. A persistent, on-chain record. A live index that applications can build on.

And it changes what we need to build ourselves.

We can now look at our existing pipeline, strip out unnecessary complexity, and make Blix leaner, faster and more efficient. Less reinventing the wheel and more building the actual experience.

That’s what great infrastructure does. It doesn’t just give you something new. It makes everything built on top of it better.

And I want to give bop his flowers here.

I think we should rename Bop to boptimisation, because this guy has a knack for getting right down to the granular level of compute, finding the elegant solution, and making things work the way they should.

In a landscape where most people are just trying to get things working, what bop does is rare.

It’s easy to overlook work like this. It’s not always flashy. It doesn’t necessarily make for the loudest announcement. But if you’re building full-time in Bitcoin, you understand how valuable it is to have someone in your corner who cares about efficiency, reliability and doing things properly.

That’s an asset beyond comprehension.

Bitmap has some incredibly interesting mechanics, and having infrastructure that can serve live, on-chain data to builders opens up possibilities that are genuinely exciting.

For blixworld, this means our platform can serve Bitmaps right up to the live tip of Bitcoin, with data validated against the chain rather than relying entirely on our own bespoke pipeline.

We’re building a persistent network of expression. A place where people can create, build, and bring their communities to life.

And the foundations matter.

So, well done Bitmap. And a massive thank you to @boppleton for building something we can actually rely on.

The work might be misunderstood by many, but builders know.

This is the kind of work that moves an ecosystem forward.

Be the Bopmap 🟧

[dev9 @Bitmapbuilder]

@six0Bitmap @boppleton Then after that, it's just a few to pull through r/block if someone wants the latest block.

[dev9 @Bitmapbuilder]

If you're eluding to a full opt-in rebuild from scratch, like what a marketplace may want to do after inspecting the simple ruleset it uses and wanting to ensure its re-applied to every inscriptionID it indexes to its own stored list, than yea 1000 marketplaces/bapps at once would be heavy. But that won't happen, most users will just cache the sat lists inscriptions already inscribed from 0-969999 through 12 instant fetches from cloudflare's edge /content

[dev9 @Bitmapbuilder]

Its kind of the opposite, now marketplaces, builders, and frequent users can fetch their own on-chain copy of the on-chain index and save it persistently in cache or files, and then after hold a much faster access equivalent, with no longer the need to fetch from https://t.co/5yVDglKRUf or use bandwidth.

[dev9 @Bitmapbuilder]

@boppleton Nice to be able to stop and continue at will

[dev9 @Bitmapbuilder]

I have my own understanding and explanations as to why the Live OCI is one of the most next level indexer + ledger construct ever built.

But I gave the link to AI and asked it to analyze, name and define it in its own words, I like it..🟧

[bop @boppleton]

📙 you can now build a full bitmap index on-chain with the LiveOCI dashboard

📚 [Local Indexing] tab: pulls inscription IDs, u can also enable images, blocktributes, sats etc

🔎 use [Compare] tab to diff check an outside index (.csv or json)

🔗https://t.co/haqWou4MTb

[dev9 @Bitmapbuilder]

@six0Bitmap OCI gets updated regularly, those were flagged a while back, should be patched in next update afaik.

[9 @block9ine]

If we don't build it, it won't happen...

be the bitmap 🟧

[dev9 @Bitmapbuilder]

@six0Bitmap Yes, this is the valid one, some indexers would seemingly skip over these negative number inscriptions, blind to them so to speak. It was not an intentional thing as in abiding by some bitmap rule.

https://t.co/nMZgt9G4nb

[dev9 @Bitmapbuilder]

@six0Bitmap 7a0f4c0f9da979e02aaf16859ccc68b0294b6ca13762f225080a0edcf264f0a9i0

[dev9 @Bitmapbuilder]

Nothing in the bitmap ruleset was ever said about cursed inscriptions, because it has nothing to do with bitmap, its an ord issue... FiF is the rule.

Older versions of ord did not see cursed inscriptions (those with the negative numbers still today), and so if their index list still dates from then, that explains the so called "edge cases".

But they are not bitmap edge cases according to the bitmap ruleset, just cases of some indexers not seeing them and indexing the second in line as the first.

In the raw witness data, there is no mistaking them.

[dev9 @Bitmapbuilder]

Nothing Bitmap was ever said about cursed inscriptions, because it has nothing to do with bitmap, its an ord issue... FiF is the rule.

Older versions of ord did not see cursed inscriptions (those with the negative numbers still today), and so if their index list still dates from then, that explains the so called "edge cases". But they are not bitmap edge cases according to the bitmap ruleset, just cases of indexers not seeing them and thinking the second in line is the first. In the raw witness data, there is no mistaking them.

[dev9 @Bitmapbuilder]

waow, that's very sus, def worth investigating this closely... 2 people that know each other getting drained to the same wallet offers a very strong opportunity to find the correlation between both.. timeframes in which you both got drained and what you both did in common with those wallets. Let me know if I can help.

[dev9 @Bitmapbuilder]

🔥🦒🟧

[9 @block9ine]

3 and a bit hours folks, it would make my day if you could pull up 🟧

[dev9 @Bitmapbuilder]

@Tomb52O @BitMap_News Really sorry man, that must have felt miserable. Anything specific makes you think that? Specific wallet make or some kind of seed analysis to come to that conclusion?

[dev9 @Bitmapbuilder]

@Tomb52O @BitMap_News Wtf... Any idea how? Through what vector of attack?

[dev9 @Bitmapbuilder]

@BitMap_News

[dev9 @Bitmapbuilder]

🟧Sit back and Bitmap Friday

[Bitmap News | 16.bitmap @BitMap_News]

The Bitmapping continues...

https://t.co/p6BzPiI302