Luxvoid embeds a cryptographic chip inside physical metal.
Tap the chip → BTC/LTC fires a permanent tombstone transaction → SPV proof verifies on CKB → bridges to EVM (LitVM) as NFT.
Sub-second. No oracles. No multisig. No trusted third parties.
The asset's existence on EVM is mathematically linked to its physical counterpart's Bitcoin anchoring.
Governments aren't asking the industry to adopt physical-to-digital traceability. They're mandating it.
Luxvoid's Cryptographic chip-in-metal infrastructure is already built to meet those requirements.
The customers aren't optional. The regulations are already law.
This is what physical-asset RWA looks like when it's built on cryptography, not promises. 🏛️⛓️ #BTC #LTC #LITVM #EVM #RWA #DIGITALIZED #ASSETS
We’re very happy to see crypto-agility being taken seriously by others in the industry.
Native account abstraction for EOAs is clearly the right path for Ethereum.
Right now, Ethereum EOAs are tightly linked to ECDSA keys. In practice, that means regular user accounts are bound to one cryptographic signature system.
EIP-8141 tries to move Ethereum closer to full native account abstraction, where user authorization is decoupled from one protocol-defined signature path.
In simple terms, the proposal introduces a new Ethereum transaction type that breaks a transaction into separate “frames” and allows accounts to define their own validation logic.
Think of a normal Ethereum transaction today as one bundled action:
“Here is my ECDSA signature. I am the sender. I pay gas. Now execute this action.”
EIP-8141 wants to split that into modular steps:
“First, run this validation logic.”
“Then approve who is allowed to act.”
“Then decide who pays gas.”
“Then execute one or more actions.”
This would make Ethereum EOAs far more flexible — or, as we would put it in @NIST terms, more crypto-agile.
And crypto-agility is the key to post-quantum readiness.
The deeper problem is not simply choosing a new post-quantum signature scheme. It is giving accounts the ability to use different signature schemes, and allowing multiple schemes to coexist at the same time.
This is also why we think CKB’s architecture is worth studying in this context.
On CKB, transaction authorization already lives in programmable Lock Scripts, not in a hardcoded signature scheme at the protocol layer.
That means new signature algorithms can be deployed at the script, or “application,” layer; coexist with existing schemes; and be adopted permissionlessly.
SPHINCS+ is already live on CKB mainnet. @quantumpurse already uses it. Other post-quantum schemes can follow the same path.
If Ethereum adopts EIP-8141, it will be moving toward crypto-agility through native account abstraction.
CKB was designed around cryptographic flexibility from the start.
Survival favors the chains best able to adapt to a changing environment.
This is why we CKB ✊
We have officially open-sourced the Chiral protocol on #NervosNetwork#CKB.
Dive into the details: https://t.co/VxJWJo9A0r
Explore the code and share your feedback:
https://t.co/e1ezi1OUSx
@AIIA8881@NervosNetwork I remember you were very enthusiastic about CKB until your project was rejected. Were you one of the people you describe as Jiǔcài, or did you come across new information that changed your mind?
🚴 Fiber Dev Log 32 🚴
Getting Fiber ready for v0.9 ⚡
This cycle was all about release hardening. We shipped v0.9.0-rc4 and spent most of our time improving reliability, security, and stability across channels, watchtowers, routing, funding flows, and developer tooling.
Shipped:
• Fiber v0.9.0-rc4
• Security hardening across gossip, RPCs, and channel validation
• More reliable channel funding and recovery handling
• Watchtower stability improvements
• CCH payment and routing improvements
• fiber-js and npm release improvements
Polishing a few final pieces before v0.9 lands 🏁
Full dev log: https://t.co/pzPLjIoMGL
@AIIA8881@NervosNetwork They've remained strangely silent. Either they know something we don't and are confident, or they're simply powerless to do anything.
@drakonzbg@FiberDevs No one asked me to buy CKB. I studied it carefully and chose it myself. Yes, some things changed, especially what I believed was support from companies in Hong Kong, but the decision was mine. I won't insult or blame the CKB team for a decision I made myself.
@drakonzbg@FiberDevs I'm on a ship in the middle of the sea, waiting to see what the captain will do, with my faith in God intact. Every adventurer looks foolish before success. I just hope I won't be the fool in the end.
@drakonzbg@FiberDevs 2026 has brought strong progress for CKB, but institutional adoption remains the biggest challenge. Whether capital attracts developers or developers attract capital, my hope remains in God, for He is capable of all things.
@drakonzbg@FiberDevs Yesterday, I renewed my confidence in CKB and increased my holdings.
It seems we are standing at a crossroads.
Either an astonishing and spectacular rise...
Or a devastating collapse.
📣₿itcoin Light v.1.2.0 is now live! Including:
⚡️ Full Bitcoin Lightning Support
📨 Pay Lightning invoices
📊 Move between bitcoin:native & Lightning
🌐 Taproot support
🔃 Bitcoin and Nervos syncing
✅ Various stability fixes and UI polish
📲Download now! https://t.co/Kr0vEsEMG4