
Dev Eco @Starknet Founder https://nitter.gq/t.co/gOjPWgtOtN Magnitude at @SeismicSys OG-Raider @domaprotocol Builder @RialoHQ
Joined April 2013
- Tweets13.9K
- Following10.3K
- Followers10.4K
- Likes18.4K
Còn đâu những lúc lên 190tr 1 cây vàng, ví dụ giờ mỹ đánh Iran vậy thì vàng có lên hay không các bác?
1
75
Domains: The Connection Between Real-World Assets and Web3
Domains are often viewed as simple web addresses, but their value is much closer to digital real estate: a scarce, memorable name that carries brand recognition, traffic, and identity.
In the traditional internet, domain control is managed through registries and registrars under DNS and ICANN rules. In Web3, naming systems such as ENS serve a similar purpose: turning long wallet addresses into readable identities that can point to wallets, profiles, and applications.
That is the key similarity: both systems make digital destinations easier to find, recognize, and trust.
However, there is an infrastructure gap. Traditional domains work across websites and email, but secondary-market transfers can involve brokers, escrow, and registrar processes. Web3 names are programmable and transferable onchain, yet many operate separately from the DNS infrastructure people already use.
This is where Doma Protocol comes in.
Rather than replacing the existing domain system, Doma enables eligible DNS domains to be tokenized, representing domain control onchain while preserving compatibility with existing registrars, registries, and ICANN-related processes.
Its architecture also introduces ways to separate domain ownership from specific usage permissions, making domain rights more programmable and composable.
This creates a path toward more liquid domain markets, onchain trading, and new DeFi use cases.
My perspective: Doma's most interesting contribution is not simply turning domains into NFTs. It is making the internet's existing naming infrastructure more programmable and financially accessible without asking users to abandon the DNS.
The next evolution of domains may not be about creating a new internet, but connecting the one we already have to Web3.
@domaprotocol @D3inc
🤝 Paid partnership
A domain is more than an address, it can be a passion, a belief, a community or an identity.
That's why new internet domains matter. Feat. @mxchaelho ⤵
Seismic Is Still Building. The Git Activity Speaks for Itself.
While much of the attention in Web3 tends to focus on announcements, launches, and short-term milestones, there is another signal worth paying attention to: consistent engineering work behind the scenes.
Seismic's recent GitHub activity shows that the team is still actively developing and maintaining its infrastructure.
One recent example is PR #522, which backports applicable fixes from upstream Reth v2.10.0 into Seismic's Reth 1.7.0-based fork.
This is not just routine code maintenance. The changes address several important areas of execution client reliability:
Improving Trie iterator boundaries to protect state-root correctness.
Enhancing P2P compatibility through EIP-8-related fixes.
Improving execution control with cancellation handling, concurrency permits, and shared gas limits.
Fixing trusted-peer DNS handling to make node connectivity more reliable.
Standardizing empty revert responses while preserving Seismic-specific behavior.
What stands out is that the team is not simply copying upstream changes. They are adapting each fix to their existing architecture while maintaining the behaviors required by Seismic.
That is the kind of engineering work that often goes unnoticed but matters when building infrastructure intended for production environments.
The important takeaway: Seismic is still shipping code, refining its infrastructure, and working through the technical details behind the project.
Development is not always visible through announcements. Sometimes, the strongest signal is what developers continue to build on GitHub.
@SeismicSys @xealistt @NoxxW3
🤝 Paid partnership
3
12
272





