Plug-and-play NFT contracts for content that is interactive, HTML/JS-based, with dynamic and on-chain metadata.
https://t.co/6WC8WNKZGW
My first contribution to the #NFT space. Please retweet to reach web and NFT developers to build the next level of NFT experiences.
❤️🔥
@feindura It's the lack of use cases and incentives. So far no dapp is significantly better for a normie and speculation kill the space. I think it requires something big like a new machine-understable democratic political-economic regime to justify such a change.
@basalganglia00@MerlijnTrader Yeah but hackers or ilegal agents can not hide forever. Ethereum is public. They can not swap to stable coins or exchanges without a trace. It's worst than cash for laundering money.
Now that ZKEVMs are at alpha stage (production-quality performance, remaining work is safety) and PeerDAS is live on mainnet, it's time to talk more about what this combination means for Ethereum.
These are not minor improvements; they are shifting Ethereum into being a fundamentally new and more powerful kind of decentralized network.
To see why, let's look at the two major types of p2p network so far:
BitTorrent (2000): huge total bandwidth, highly decentralized, no consensus
Bitcoin (2009): highly decentralized, consensus, but low bandwidth - because it’s not “distributed” in the sense of work being split up, it’s *replicated*
Now, Ethereum with PeerDAS (2025) and ZK-EVMs (expect small portions of the network using it in 2026), we get: decentralized, consensus and high bandwidth
The trilemma has been solved - not on paper, but with live running code, of which one half (data availability sampling) is *on mainnet today*, and the other half (ZK-EVMs) is *production-quality on performance today* - safety is what remains.
This was a 10-year journey (see the first commit of my original post on DAS here: https://t.co/Fa0jKFgObW , and ZK-EVM attempts started in ~2020), but it's finally here.
Over the next ~4 years, expect to see the full extent of this vision roll out:
* In 2026, large non-ZKEVM-dependent gas limit increases due to BALs and ePBS, and we'll see the first opportunities to run a ZKEVM node
* In 2026-28, gas repricings, changes to state structure, exec payload going into blobs, and other adjustments to make higher gas limits safe
* In 2027-30, large further gas limit increases, as ZKEVM becomes the primary way to validate blocks on the network
A third piece of this is distributed block building.
A long-term ideal holy grail is to get to a future where the full block is *never* constituted in one single place. This will not be necessary for a long time, but IMO it is worth striving for us at least have the capability to do that.
Even before that point, we want the meaningful authority in block building to be as distributed as possible. This can be done either in-protocol (eg. maybe we figure out how to expand FOCIL to make it a primary channel for txs), or out-of-protocol with distributed builder marketplaces. This reduces risk of centralized interference with real-time transaction inclusion, AND it creates a better environment for geographical fairness.
Onward.
@javilop El vibe coding no es simplemente programar con IA, es dejar q la IA lo haga todo sin revisar ni ajustar código, solo alineando el resultado. Si crees q esto es el futuro, entonces crees que solo importa el resultado xq el proceso es automático y crees en una tech sin límites.
@feindura I have had suggested many things on Discord with no answer, as a builder/creator it is also frustrating that vision rigidity. You get feedback from here instead, so you put your efforts on marketing, so your tech doesn't evolve enough to affect the price, so nobody is happy.
@supahfunk Could you be more precise please? 🙏 Does it mean that are you adding/removing vertices in real time? Cause it looks like and it would be awesome to finally have a remesher in threejs!
Ideologies are modern religions, replacing public participation and enslaving democracy with outdated sovereignty models.
We don't need bias, we need data, on-chain proofs, and public software like virtual parliaments to shape the popular will and channel our taxes.
@JeanCavallera@lukso_io a) Why/when it's worthy to use the complexity of data keys instead of simple contract state variables? The use case domain is about interoperability of apps/UPs?
b) Why there is so little built on top of LSP from the team but still waiting for dev community to build?
@peter_szilagyi Take a look at Grasshopper for Rhino, which also allows u to code in c# and py, and it's NURBS based. Doing big changes from code is messier and takes more time for most of the modelling tasks than using visual programming.
@RyanSAdams Money should be something abstract that manifests itself locally/temporarily as concrete like currencies or other assets. Tech can fold this to the user. We should marry with this (decentralized) idea and not with specific implementations. Iterate until specific use cases winners
@feindura Until ready vs iterate with the market, why to choose the riskiest option for everyone? You need to start building positive inertia, otherwise you will be ready with negative inertia. Each time I have a crypto chat with random people in London pubs nobody knows about Lukso...
@JeanCavallera I want to trust random addresses based on on-chain community interaction. Maybe KM can be used as a reputation protocol? it reacts to user tx to set data keys on UPs, and allows to query metrics for a given address. Then dapps can allow interaction just to participative humans.
@sama Even if we can create everything, it doesn't mean we need everything. Computation and imagination (as scarcity) are not the only limits for your expected prosperity. Tech usually amplify the good and the bad too, so please try hard to do not increase misery as well.
@JeanCavallera Categorisation is not trivial, there are many ways to do it, a NFT could have several types or being different per tokenId... but probably worth it to be able to label them somehow.
@sleepyxsign@JeanCavallera You need a LSP8 collection of collections, where parent NFT represent character contract and child LSP8 or LSP7 represent character inventory. There is an example of this on Lukso docs.