CryptoMagnus retweeted
🟨 𝗕𝗜𝗧𝗠𝗔𝗣 𝗦𝗔𝗟𝗘 𝗔𝗟𝗘𝗥𝗧 🟨
✨ Sweep Alert ✨
🧹 sg8a just swept 12 bitmap for 0.00365 BTC ($292.45 USD)
🕵️♂️ Buyer: sg8a
🦉 Automated by hootertech
CryptoMagnus retweeted
Gateway: The Districts Update (v0.7.8)
This is me indexing Bitmap Districts directly from Bitcoin Peers without a full node. Live now. 🤫
github.com/Blockamoto/gatewa…
The timeline has levelled up. Play control buttons, track arming, and parallel indexing. ⏯️
You also can set in and out points for ranged indexing.
🔸 Bitmap District indexing 🟧
🔸 Timeline control 🔀
🔸 Play, pause, and stop ⏯️⏹️
🔸 Track arming for parallel indexing ⏺️
🔸 Set in/out point for ranged indexing ⬅️➡️
🔸 Smart auto-in and skip buttons ⏮️⏭️
🔸 Block-tx-out-satpoint nav buttons ⬆️⬇️
There's a lot that needs to be done still, but that is the case with any update I suppose.
First of all, we need the Bitmap tab that shows you a Districts inscription details when you navigate to that block. Yeah, I don't know what happened to that. I'll fix that for the next version v0.7.9.
I had to split the District update from the Parcel update after peer review from @boppleton exposed a blind spot in validation. Cheers mate! 😅
The Parcels version will also give me the opportunity to introduce proper parent/child awareness and validation when the data allows.
I've also not including Bitmap Chain because the design grew into something that could enable consensus fork tracking... which sounds like a bad thing, until you realize that's how Bitcoin works. A ruleset that forks without a chain is a lack of accountability, and that's the idea of Bitmap Chain. But that's a discussion for another day. And so with that, it needs much further scrutiny and design. I actually implemented it first, then had to remove it along with Parcels. Implementing all that took time, and then removing it took more time. But sometimes the treasure isn't in the chest, it's in the map! 🗺️
And with what we know, for v0.8.0, I plan to completely rebuild indexing to be based on a common indexing engine and schema that will allow users to construct custom indexer tracks in-app. If an existing indexer cannot be rebuilt and stated this way, the engine is not good enough. That's quite a big jump! It will take time.
So the deeper Ordinals indexers I was planning can wait until v0.8 when we have custom indexing. Then, the rest of v0.8.x will mainly be focused on validation features, and preparing everything for when we get into v0.9.x versions, which is for enabling Gateway peers. I won't go to in depth because there's a lot I won't know until it's ready.
And that's all I have for now!
You can check for updates within your existing Gateway installation, or download directly here:
github.com/Blockamoto/gatewa…
Enjoy! 🫡
Gateway: The Sats Update (v0.7.7)
Ship fast, fix later. Now we have Sat compatibility in Gateway. It's messy but we'll tidy up when we're done.
github.com/Blockamoto/gatewa…
So, what have we got here?
Now you can enter any sat number and see details.
You can also use @rodarmor style sat names.
You can build a sat ranges index to unlock Ordinals.
Choose live or retained ranges (full Sat history).
Sats tracks inscription ownership.
Powered by Bitcoin Positional System.
Browser extension registers <number>.sat.
I'm purposefully keeping this version very blunt in my announcement delivery because I've been shipping daily feature updates, and it's important I give you the disclaimer that these 0.7 versions are for early public testing. I'm already noticing things that could be better. What I see so far though, it works. And we're almost finished with 0.7 versions now... just one more major feature to go before I tidy up around here.
The v0.7.8 update following this v0.7.7 is what you've all been waiting for... Bitmap! The most exciting and neccesary update for our community, including Bitmap Standard indexing, and Bitmap Chain validation and comparison against alternate rulesets. I will ship the /Blockamoto/bitmap repo with it to include full details on Bitmap Standard, and Bitmap Chain. Gateway will be it's first implementation.
If you're worried that I'm changing core ruleset, that's not the case. The ruleset stays. The Bitmap Standard ruleset keeps core ruleset and makes specific certain points that were assumed to be obvious.
Anyway, this update is supposed to be about Sats...
So go have fun and frollock in the field of Satoshi's!
github.com/Blockamoto/gatewa…
Enjoy 🫡
CryptoMagnus retweeted
I'm preparing Gateway for testing, and I have a few updates.
We need to roll this out carefully, rather than haphazardly.
The first alpha test will be specifically for Bitcoin on Demand.
That means I will be disabling:
🔸 Gateway to Gateway peers
🔸 All non-Bitcoin native indexes
🔸 Yes, that includes Bitmap indexing
I don't want to proliferate a p2p network on shaky ground, and whilst I'm confident with Gateways current capabilities, we need a clean test phase for each layer rather than rolling it all out in one.
What will be in this version:
🔸 Bitcoin on Demand
🔸 Full or ranged Bitcoin indexing
🔸 New Bitcoin address schema
🔸 Block/transaction/output explorer
Regarding the Bitmap index, I'm taking this opportunity to solve the indexer edge cases once and for all. The first step towards that is a full audit of all edge cases rules, where they result in contested outcomes, and which Bitmaps are affected. For each diverging ruleset track, there will be a hash outcome for each new block. Once we're at that stage, we can pressure indexers and marketplaces to expose their current state hash as a proof. This will be a proof of which track the indexer/marketplace is on.
And then we blow up the conversation around edge cases and hash it out between us. Benefits and costs of decision A versus decision B. There is no final "this is the canonical ruleset" declared, just a hash for each possible outcome, and the community who may or may not agree with that outcome or ruleset decision who can audit the outcome of that hash and see exactly which bitmaps are affected.
This is the fairest, most Bitcoin way I can think of solving this problem, and Gateway gives us the opportunity to do this once and for all. I'm even holding back giving @lifofifo a canonical index so this can be handled. We cannot ignore this issue any longer.
And so this is what I'll be implementing into Gateway.
This is rough consensus in action.
Expose the truth and let the community decide, just like Bitcoin.
I'm setting up a bitmap repository to handle rulesets and edge cases to make this fully visible for all.
But first things first, I'll be putting Gateway out soon without any of this. Just Bitcoin. Ordinals will come next. Then Bitmap. Then Gateway peers. Then we can start to open it up to custom indexes before we expand on the p2p capabilities, which is where things will get really exciting.
So stay tuned for that first alpha test. It's coming soon.
Introducing Gateway...
I've been building a new kind of Bitcoin client.
One that ANYBODY can run regardless of storage.
Fetch only what you need, when you need it.
On-demand, directly from Bitcoin peers.
This is at the heart of Gateway.
Sparse-by-default deep on-demand p2p-Bitcoin indexer.
Now, I recommend you feed this post your favourite AI and have it talk to you directly about it, because I'm about to get into the weeds. And I'm very excited, so it's probably better you ask your AI how this applies to you, rather than leaving a comment that it's too complicated or that you don't understand. With that being said, if you're happy to go hardcore old-school style, and actually... read the thing, here it is!
BITCOIN PEERS
Traditionally, Bitcoin clients sync nodes by requesting blocks from other peers one-by-one, from zero.
This is somewhat impractical for everyday users.
Gateway does things differently.
You can certainly sync the entire blockchain using Gateway, and become a full Bitcoin Node, and a useful Bitcoin Peer. You can even bring your existing Core node and plug it in if you already have one.
But that's not the interesting part.
The interesting part is that you don't need that.
Seek data directly from Bitcoin Peers, on-demand.
ON DEMAND
Unlike Core, Gateway does not require you to sync the entire blockchain. You can sync any range, or even just type in a block number in the top bar to fetch the block from a Bitcoin peer directly.
This approach is extremely useful for Blocks, but it has some limitations.
Transactions (and thus, inscriptions) cannot be resolved directly, without knowing the block number. The latter part of that sentence is the important part.
Gateway adds a schema that allows you to type "{tx}.{block}.bitcoin" and resolve a transaction directly from a Bitcoin peer. You can replace {tx} with either tx-hash, or tx-index (which is a new schema for Gateway), and {block} with either block-hash or block-height.
For example: 0.0.bitcoin
This becomes relevant for inscriptions.
An inscription ID is simply:
{tx-id}i{inscription-index}
So you can resolve inscriptions by including block-number in the scheme:
{inscription-ID}.{block}.bitcoin
If you know the transaction index, you can even use that instead of transaction ID in inscription ID.
That means, so long as you know the block number, any inscription can be resolved on Gateway, on-demand, by asking a Bitcoin peer directly.
ORD
When it comes to Ord, this is an extra layer on top of Bitcoin. It is an indexing system that takes Bitcoins already heavy data store, and adds its own index that can take roughly a week to sync.
For the everyday user, this is not practical.
Whilst I've demonstrated how we can fetch inscriptions directly from Bitcoin Peers without Ord, you need to know block number, and the standard in Ord is to use inscription ID, sat number, or inscription number as the key reference.
I've added block in the Gateway schema as a useful primitive that enables purely on-demand inscriptions from Bitcoin peers, but that isn't the current standard.
INDEXES
This is where you can build your own data-store directly from Bitcoin data originated through Bitcoin peers, and either become a useful participant of the network, or take what you need privately.
The baseline index is Bitcoin Blocks.
However, you do not need that to resolve the other indexes.
Each index has an "ephemeral" option, which means to seek the blocks you require from peers, strip the data you need, and discard the blocks. This is useful if you're running this on your everyday computer, and can't be spending so many GigaBytes on Bitcoin.
For example, you can index Bitmap without storing a single block.
The indexes are generally layered, so you can choose what you would like to index and when. If you index Bitcoin Blocks, you will be asked if you also want to index the other downstream indexes in parrallel, since it would be quicker to do that than re-run the index.
If you already have a Bitcoin Node, you can build other indexes on top of that.
But you don't have to have the Bitcoin blocks to sync inscriptions, Bitmap, or any other index we implement.
Now, this is still some heavy lifting, but once we start activating the Gateway peer network, we can supercharge these capabilities.
GATEWAY PEERS
Gateway users can connect to each other in a peer-to-peer network, just as in Bitcoin.
That means that, whatever data you need, you can ask Gateway peers directly and skip indexing directly from Bitcoin data, with Bitcoin as the hashed proof verification layer.
So, anything your Gateway node doesn't know, or is impractical for you to find through Bitcoin peers, can be served by Gateway peers.
This vital peer layer can become more useful as we start adding other cases for the Gateway peer network, for example, you could opt-in to become a persistent relay for a Bitmap or Ord gaming webRTC layer. We can even serve this p2p mesh layer to websites and ordinals over the web, so in the future, you will be able to connect to gateway from a website, or from an Ordinals inscription.
For now though, it requires the Gateway client. But the dream is that you can become a useful OR private participant in Gateway from different angles.
LONG STORY SHORT
A sparse-by-default on-demand bitcoin node, with full-range indexing and p2p sharing with gateway nodes.
EARLY RELEASE TESTERS
I am seeking early testers who are happy to put the client through the ringer, vet the data, or just try and break the thing so we can make sure we ship a proper robust client.
You can comment on this post if you're interested, and I'll share details when it's ready for testing.
At this stage, I just wanted to let you know that I have a client, it's working, it's almost ready for testers.
WHAT NOW?
This is just one of the things I've been working on and excited about recently, but it's the one I think is the most important in terms of vital infrastructure that can benefit the entire stack from Bitcoin peers to Bitmappeers.
Stay glued to my timeline for more! 👀
Comment if you want to get involved. 💬
CryptoMagnus retweeted
Which floors am I sweeping!??
Jks, I received an offer after 6+ years that I couldn’t refuse.
More on this tomorrow. Time to celebrate 🍾
"The walle't signature did verify.. " both with @xverse and @unisat_wallet. Can you fix it @ordinalswallet?
Better, but still recieve "This purchase was already submitted" after signing and pressing "Buy now" button. @ordinalswallet
Check out new chat rooms that @Satflow has built for collections.
Gonna simply leave this here.
Bitmapers know how to reply 😉
