蓝福顺（xvip.btc）

@lanfushun

一个热爱科技和投资的素人，认真生活，佛系更新

Joined May 2026

986 Following

25 Followers

432 Posts

Pinned Tweet

蓝福顺（xvip.btc） @lanfushun

5 months ago

我曾运营几年的推特号，却被无辜永久冻结。累积一夜归零，但这些年我经历过：BRC20 铭文、符文、NFT、MEME、空投、链上打新。 Crypto 真正能活下来的，不是运气最好的人，而是能抓信息差、控制情绪、牛熊周期都能存活的人。 Crypto 是一场认知 × 情绪 × 执行力的长期游戏。AI×Crypto 趋势正在发生！

lanfushun's tweet photo. 我曾运营几年的推特号，却被无辜永久冻结。累积一夜归零，但这些年我经历过：BRC20 铭文、符文、NFT、MEME、空投、链上打新。
Crypto 真正能活下来的，不是运气最好的人，而是能抓信息差、控制情绪、牛熊周期都能存活的人。
Crypto 是一场认知 × 情绪 × 执行力的长期游戏。AI×Crypto 趋势正在发生！ https://t.co/zk153WmamX

2

1

0

0

114

蓝福顺（xvip.btc） @lanfushun

about 23 hours ago

@UrbanBor 优秀的

0

0

0

0

1

蓝福顺（xvip.btc） @lanfushun

about 24 hours ago

@villainmonkey 0x13fc09ca7a43f78e898ec06c39abaf1203d990a4

0

0

0

0

1

蓝福顺（xvip.btc） @lanfushun

1 day ago

0

0

0

0

1

lanfushun retweeted

bitoshi blockamoto 🧱 BITMAP 🟧

3 days ago

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. 💬

blockamoto's tweet photo. 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. 💬

blockamoto's tweet photo. 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. 💬

blockamoto's tweet photo. 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. 💬

blockamoto's tweet photo. 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. 💬

25

144

36

34

10K

lanfushun retweeted

泼天的富贵

1 day ago

之前为了养龙虾冲动消费买的 Mac，今天终于觉得钱没白花看到之前老张@cryptoresetlife 扒 TAO 的时候撞到个有意思的IOTA SN9，Bittensor 子网 9 上的众包练模型，谁出算力谁分奖励，项目方 MacrocosmosAI 出的家用客户端，目前只放了 Mac 版亲测挂了一下，按 SN9 alpha 现价折下来大概 8U 上下，富贵目前已经挖到了大约不到 60U（PS非100%必得）先说好：价格波动大，别当工资，当捡个零花操作就三步：下客户端 https://t.co/Tl4bIf9ob5 注册个 Bittensor 钱包，打开软件选第二个选项，粘自己钱包地址 ⚠️ 第一个别碰，那是给项目方白嫖算力的，奖励到不了你钱包最后提个醒：到账的是 SN9 alpha，不是 U 也不是 TAO，值多少自己查，电费和电脑烫不烫，自己掂量 #TAO #Bittensor #IOTA #SN9

Ouh_web1's tweet photo. 之前为了养龙虾冲动消费买的 Mac，今天终于觉得钱没白花

看到之前老张@cryptoresetlife 扒 TAO 的时候撞到个有意思的IOTA SN9，Bittensor 子网 9 上的众包练模型，谁出算力谁分奖励，项目方 MacrocosmosAI 出的家用客户端，目前只放了 Mac 版

亲测挂了一下，按 SN9 alpha 现价折下来大概 8U 上下，富贵目前已经挖到了大约不到 60U（PS非100%必得）先说好：价格波动大，别当工资，当捡个零花

操作就三步：
下客户端 https://t.co/Tl4bIf9ob5
注册个 Bittensor 钱包，打开软件选第二个选项，粘自己钱包地址
⚠️ 第一个别碰，那是给项目方白嫖算力的，奖励到不了你钱包

最后提个醒：到账的是 SN9 alpha，不是 U 也不是 TAO，值多少自己查，电费和电脑烫不烫，自己掂量

#TAO #Bittensor #IOTA #SN9

23

30

6

23

8K

蓝福顺（xvip.btc） @lanfushun

1 day ago

@0xAUXVI 0x13fc09ca7a43f78e898ec06c39abaf1203d990a4 喜欢这个色彩斑斓

lanfushun's tweet photo. @0xAUXVI 0x13fc09ca7a43f78e898ec06c39abaf1203d990a4
喜欢这个色彩斑斓 https://t.co/Qbr1PrEvpf

0

0

0

0

2

蓝福顺（xvip.btc） @lanfushun

1 day ago

@Mirro7777 来了，你出行开始牛市启动

0

0

0

0

3

lanfushun retweeted

1 day ago

看到退潮实在不忍心于是我决定献祭自己明天定了个6小时的航班希望我的出行能让行情回来并且此条推特抽3个人一人送100u 需要关注我，并且转发

1K

1K

1K

31

68K

蓝福顺（xvip.btc） @lanfushun

1 day ago

@MURCATi 0x30317c1d95bb92cc4d5984eb695056f883449831

0

0

0

0

6

蓝福顺（xvip.btc） @lanfushun

1 day ago

@momochenming @cigrhabana 这玩意在我们这乡下使用可是会很被村头大爷问好几遍的

0

0

0

0

21

蓝福顺（xvip.btc） @lanfushun

1 day ago

@SuperIntelBNB 0x13fc09ca7a43f78e898ec06c39abaf1203d990a4

0

0

0

0

1

lanfushun retweeted

3 days ago

Mint details 👇 5 / 10 / 2026 3PM UTC ( FULLY EXPERIMENTAL DYOR )⚠️

42

359

258

23

45K

蓝福顺（xvip.btc） @lanfushun

1 day ago

10月5日？

3 days ago

Mint details 👇 5 / 10 / 2026 3PM UTC ( FULLY EXPERIMENTAL DYOR )⚠️

42

359

258

23

45K

0

1

0

0

7

蓝福顺（xvip.btc） @lanfushun

1 day ago

I'm joining the @sbrc20_ airdrop list. SBRC-20 — BRC-20, but shielded. Private token transfers on Bitcoin. Complete 3 steps to join: https://t.co/1xwV1dgM0X

2 days ago

🚨 Applications are closing soon! Join now 👉 https://t.co/5Fy338I5zU 100% FREE airdrop — no stupid requirements, no claim fees. Just apply and you’re in. 🫡

197

3K

1K

334

179K

0

0

0

0

2

蓝福顺（xvip.btc） @lanfushun

1 day ago

把fb生态也搞起来拉盘吧，fb6-10u接盘的被套很久了

1 day ago

We heard the $DOG Army wanted more ways to trade $DOG. So we built an order book based pro trading experience for Runes, designed for deeper liquidity and less friction. Come trade DOG/BTC on UniHexa! 🔥

Uni_Hexa's tweet photo. We heard the $DOG Army wanted more ways to trade $DOG.

So we built an order book based pro trading experience for Runes, designed for deeper liquidity and less friction.

Come trade DOG/BTC on UniHexa! 🔥 https://t.co/td8knAyNqC

75

529

212

10

15K

0

0

0

0

9

蓝福顺（xvip.btc） @lanfushun

1 day ago

@MURCATi 让汉语发扬光大 0x13fc09ca7a43f78e898ec06c39abaf1203d990a4

0

0

0

0

2

蓝福顺（xvip.btc） @lanfushun

1 day ago

@Bnh07936543 0x13fc09ca7a43f78e898ec06c39abaf1203d990a4 买了被割肉了，来回点血

0

0

0

0

8

lanfushun retweeted

1 day ago

#中国人能飞还不能起来，之前挣了60多万没卖，准备拿1万出来做市场！ 👍点赞评论区留bsc地址转发这条 #中国人能飞推文，人人有份，每人10u的代币。活动时间24小时！

Bnh07936543's tweet photo. #中国人能飞
还不能起来，之前挣了60多万没卖，
准备拿1万出来做市场！

👍点赞评论区留bsc地址
转发这条 #中国人能飞推文，人人有份，每人10u的代币。活动时间24小时！ https://t.co/MeHxjKi12B

1K

1K

866

37

43K

蓝福顺（xvip.btc） @lanfushun

1 day ago

@umbrellacap_ 0x13fc09ca7a43f78e898ec06c39abaf1203d990a4

0

0

0

0

2

蓝福顺（xvip.btc） @lanfushun

1 day ago

brc2.0这叼毛又开始干活了

Best in Slot | BRC2.0 🧑‍🍳

4 days ago

https://t.co/5jF8B6kxQC

28

88

20

14

21K

0

0

0

0

2

Last Seen Users on Sotwe

Trends for you

Most Popular Users