Wang retweeted
Tesla is officially coming to Vietnam - and we're hiring.
Our mission is to build a world of amazing abundance and we are looking for passionate people to join us in Vietnam and help make that vision a reality.
Current Job Openings:
Sales Manager - lnkd.in/gSME7ySE
Service Manager - lnkd.in/gPd5eDMk
HR Business Partner - lnkd.in/gWMtarR2
Purchasing Manager - lnkd.in/g6FqqH7E
Project Developer, Charging - lnkd.in/gHiKEn39
#Tesla #TeslaVietnam
Wang retweeted
Is NEAR in trouble? 🚨
Dominic Williams (@dominic_w) says Near Intents was built on patented DFINITY technology, brought over by a former employee and used for over two years without a license.
Now NEAR is quietly rolling it back on GitHub, and legal action may be next. #ICP
DFINITY Founder Takes Aim at NEAR’s Privacy Claims
DFINITY (@dfinity) $ICP founder Dominic Williams (@dominic_w) says a PhD engineer’s review raised questions about Near (@NEARProtocol) $NEAR Confidential Intents.
Williams shared the engineer’s assessment, alleging the system relies on a separate permissioned network called FAR, where operators are trusted to protect private data.
The assessment questioned its privacy technology, open-source status and undisclosed node operators.
Wang retweeted
This is craazy. I asked one of our PhD engineers to look into NEAR *Confidential* Intents wondering how they designed their system. Unredacted, word-for-word, this was his answer 😱😱😱
"Everything I found out about the privacy claims and confidential intents is so bad that it seems almost comical and I cannot believe what I am seeing. Apparently they run a completely separate instance of the protocol, which is called FAR (as an opposite to NEAR), and that has a permissioned operator set. The entire confidentiality claim seems to rest upon the fact that it is a permissioned chain and the nodes are trusted to keep things private, there doesn't seem to be any deep technology behind it and it also does not seem to be open source. The entities running the nodes are also not publicly known.
I almost feel weird writing this because it is so absurdly bad that it feels like ... I don't know ... a simulation? I know the usual level of overpromising in Web3 but this is so many levels beyond believable that it still feels unreal."
Wang retweeted
Bitmap Chain 🟧⛓️✨
Replying to @six0Bitmap
I'm made a lot of progress on the Bitmap Terrain Claim Chain now, with a simple hashing schema, to be announced. And I've also simplified the name to:
Bitmap Chain 😏
Wang retweeted
In my man cave
In the future, digital land on Bitcoin will be the foundation for AI, gaming, and decentralized economies.
Owning Bitmap today is like buying the infrastructure of the next digital revolution.
Be the BitMap
🫡☕🤘🟧
Wang retweeted
🚨BREAKING: HUGE FOR DFINITY as they have applied to ICANN for the official .icp internet domain! 🔥
If approved, apps built on $ICP could use familiar web addresses like .com websites, making decentralised technology easier for EVERYONE to access.
$ICP is building the next generation of the internet! 🚀
Not every contribution to Bitmap is code.
@FollowJay has spent countless hours making a video series that explains Bitmap to people who've never heard of it.
That's building too.
web3.tv/@bitmap/videos
Wang retweeted
RUSSIA PLAGUE SCARE: WHAT WE KNOW SO FAR
A mysterious death at Russia’s Anti Plague Institute in Siberia has triggered mass quarantines, conflicting official accounts and apparent efforts to restrict information.
Here is what we know:
• Darya Shipilova, 28, a laboratory technician at the Irkutsk Anti Plague Institute, developed severe pneumonia and died overnight on 1 to 2 October.
• The head of neighboring Buryatia publicly said she had died “possibly from the plague,” while stressing that the diagnosis had not been confirmed.
• Local reporting claimed Shipilova may have been exposed to Yersinia pestis, the bacterium that causes plague, while working in the laboratory. Russian federal authorities deny there was any laboratory accident.
• Nearly 200 contacts were identified. 189 were reportedly hospitalized for observation, while several hospitals were placed under quarantine.
• A major aluminum plant in Shelekhov introduced a mask mandate amid contradictory information surrounding the incident.
• Authorities in Baikalsk posted a warning telling residents to limit travel to Shelekhov. The warning was deleted roughly 2 hours later.
• Russian media outlet REN TV also removed reporting related to the incident.
• Moscow now says Shipilova died from “pneumonia of unknown etiology” and says testing found no pathogen connected to her laboratory work.
• No secondary plague cases have been confirmed. Tests among monitored contacts instead detected 2 COVID 19 cases and 2 rhinovirus cases.
WHY THIS MATTERS:
Pneumonic plague is the most dangerous form of plague. Unlike the more familiar bubonic form, pneumonic plague infects the lungs and can spread directly between people through respiratory droplets during close contact.
Without prompt antibiotic treatment, it can progress rapidly and is frequently fatal. The WHO says untreated pneumonic plague can be fatal within 18 to 24 hours after infection.
That makes any suspected case involving a worker at an anti plague laboratory particularly important to investigate and monitor.
The U.S. government is monitoring the situation and has called on Russia to provide accurate information.
BOTTOM LINE: Russia denies this was plague or a laboratory accident, and there are currently no confirmed secondary plague cases.
But the scale of the quarantine response, conflicting official statements and deletion of public warnings and media reports make the situation worth closely following.
Wang retweeted
Bitmappers…
I’ve been building something for years and it’s finally ready to launch.
It is different.
The tokenomics are built to reward participation.
And what happens after mint is where it gets really interesting.
Are Bitmappers hungry for something new?
Launch or wait?
Wang retweeted
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. 💬
Wang retweeted
Save 100s of sats on Bitcoin inscriptions with this little-known trick.
Optimise your code before you inscribe it.
Smaller file. Lower cost. Same app. ⚡
#Bitcoin #Ordinals #0rdinals
ordinals.com/content/9cafacc…
Wang retweeted
🚨 BOMBAZO: GOOGLE LIBERÓ LA GENERACIÓN DE VÍDEO CON IA
→ Sin suscripciones de pago
→ Completamente GRATIS
Es así de sencillo:
Pasos:
→ Entra en vids.google.com.
→ Inicia sesión con Google.
→ Pulsa «Crear vídeos con IA».
→ Describe tu vídeo y pulsa «Generar».
Wang retweeted
Re: the Bitget hack, DFINITY wishes them well, plus, networks like THORChain should help freeze stolen funds. On the Internet Computer, I would support NNS (Network Nervous System) proposals that froze significant stolen funds. If networks work together, there will be less theft.
Wang retweeted
Only Bitmap owners can summon.
1 creature per Bitmap you hold.
Inscribe the guardian too.
Not a public mint.
Not random art.
The land itself decides what lives on it.
Your district.
Your resident.
Your guardian.
All on Bitcoin.
Hold the Bitmap.
Summon what belongs to it.
bitmapwin.app
U🟧
Wang retweeted
Why build BlockBloom around Bitmap?
Many blockchain games begin by creating a game and issuing assets for it.
We’re starting from a different place: Bitmap already exists, with holders and a community that came before our game.
Our role is to build something worth playing around it.
Farming. Raising animals. Breeding. Gradually turning a piece of land into a place you want to return to.
To us, that’s an interesting way to grow an ecosystem: give an existing asset more things to do, and give its holders more reasons to participate.
Owning a Bitmap doesn’t automatically make a game good. We still have to earn your time through the experience we build.
The asset came first. We’re building another reason to use it.
That’s the idea behind BlockBloom. 🌱
Wang retweeted
Meta has just unveiled their new VR glasses.
• Price: $1,299
• Available Spring 2027
• Weight: 100 grams, about the weight of a deck of cards
• Glasses contain the displays and sensors, while a separate puck houses the processor, battery and storage.
• 5K display with micro-OLED panels
• Pixel density: 37 pixels per degree
• Custom pancake lenses
• Dolby Vision
• Dolby Atmos
• No head straps
• Qualcomm Snapdragon Reality Elite chip
• Battery life: Up to 3 hours of continuous high-resolution media playback
• 45W fast charging
• Full-color passthrough cameras let you see your surroundings while wearing the glasses.
• Open-sided design
• Meta AI integrated directly into the operating system.
• Voice commands, eye tracking and natural hand gestures, with no controllers required
• First IMAX Enhanced-certified VR device, supporting select movies in IMAX's expanded aspect ratio.
• Disney+ will offer select 3D movies
• Streaming services: Partnerships with Disney+, Prime Video, YouTube, DIRECTV, AMC+, Crunchyroll, Plex, ESPN, Tubi and others
• Immersive live sports: Front-row viewing experiences with 8K streaming and 180-degree views
• Works with calling apps including WhatsApp and Zoom
Wang retweeted
Bitmap日报 🟧2026年9月23日星期三
1⃣Bitmap创始人 bitoshi blockamoto(@blockamoto)发推:我取得了一个重大突破,引发社区猜想。他随后放出两段视频:老式电脑星空画面,以及圣路易斯Gateway Arch拱门。有人评论“GATEWAY”,他回复“Yes.”。结合近期ord新增/r/block接口,外界猜测或与Bitmap链上新能力有关。目前细节未公布。teapawt.net/blockamoto/status/2102…
2⃣Bitmap社区资深玩家 SuperMario (@SuperMario_AI )在Satflow 平台出售了 111222.Bitmap,222333.Bitmap,333444.Bitmap,444555.Bitmap,555666.Bitmap,666777.Bitmap,其中,555666.bitmap售价0.021BTC,价值$1,817.87 。感兴趣的朋友可以去Satflow 查看或购买 satflow.com/ordinal/5b03ff5c…
3⃣自称Bitmap隐私链的thebtccodex(@thebtccodex )发推称:进展未停,仔细读过首份公告者已掌握更多信息,架构成型中,下轮披露将更清晰,早期窗口正在收窄。其公告显示,该项目拟推EVM兼容的Bitmap Privacy Chain,可选ZK隐私,Gas用BTCB、结算用BTC,21个验证席各需锁定2100枚Bitmap,不发行新币。teapawt.net/thebtccodex/status/210…
4⃣220万粉丝的大V WallStreetBets (@wallstreetbets)于近期发文:“严肃的问题,比特币的下一个真正的大用例到底是什么? 我们已经有了 Ordinals、Runes、L2s,所有这些 什么才能真正让机构使用比特币,而不仅仅是持有它?”Bitmap社区在评论区积极回应。
发评论,支持Bitmap: teapawt.net/wallstreetbets/status/…
5⃣Ordinals交易平台Ordinals Wallet (@ordinalswallet) 于近期优化了网站,新增了全球销售历史、地板价和交易量功能,Bitmap 交易页面也进行了更新,但bitmap.trade(@bitmaptrade)认为Ordinals Wallet 抄袭了他的设计,截止日前,Ordinals Wallet 没有做出任何回应。teapawt.net/ordinalswallet/status/…
注意:以上仅为信息分享,不构成投资建议。数字资产波动极大,请自行核实并谨慎决策。🫡
🤖 Made with AI



































