Today on the tech updates stream:
A look at new features planned for Logos Testnet v0.3 and the development behind core protocols.
Open discussion on a range of technical questions around the Logos stack.
https://t.co/7M02MnUUVN
λSQL turns any channel on Logos Blockchain into a decentralised database. Writes to a local SQLite instance are intercepted and posted to a channel; every client following that channel replays the log and applies it locally. SQL replication with the L1 as the ordering layer.
No peer-to-peer setup between devices: coordination happens on chain, so a phone can act as one of the channel's sequencers.
Suited to low-write, fully replicated applications such as password managers.
Coming in Testnet v0.3.
Synchronous atomic composability is very overrated imo. Like, think about what are some specific cross-L2 things *you* are already doing or envision yourself doing that could be more seamless. For me, the top two are:
1. I have coins on Optimism, I want to pay Bob, but Bob is only on Arbitrum.
2. I have coins on Taiko, I want to use a dapp on Polygon, so I need to send-to-self to Polygon in order to use that dapp.
These are not fancy nerd problems that can be fixed by solving synchrony. These are UX problems that can be fixed with:
(i) widely adopting ERC-3770 so that the chain is part of the address, so an address once again becomes a self-contained "how do you pay me" identifier
(ii) a cross-L2 exchange protocol (eg. ERC-7683), so you can do cross-chain sends programmatically without juggling which specific intermediaries to trust and which APIs to connect to
(iii) wallet integration, so sending cross-L2 is done by putting the recipient's ERC-3770 address into the exact same textbox as you use for regular sends today
Solving nerd problems *can* make this much more efficient, especially by making cross-chain swap markets more friendly to liquidity providers, by reducing withdraw times from 1 week (optimistic rollups) to 1 hour (zk rollups today) to 1 slot (ideal zk rollups with proof aggregation). But even there, there's multiple orders of magnitude of unclaimed gains that don't even require getting into synchony.
Warm-up Spaces 👂
Join @Codex_storage, @SecretNetwork and @Acurast
for the second depin:con warm-up Spaces. Learn more about the projects and get insights into the upcoming #DePIN event in Brussels right before @EthCC kicks-off.
Thursday, 04.07 13:00 CEST 🎤
https://t.co/7uad3qnKEw
Want to learn more about decentralised storage and try out Codex?
Don't miss our hands-on workshop at Web3 Social Day, organised with @masknetwork!����
We'll showcase our tech, set up nodes together, and play with the network — it's gonna be fun!🔧
🗓️ July 9
🕒 2 - 4 pm
@mariofusco I think that's just the nature of technology cycles where people ditch entire concepts because of what are probably shortcomings in implementation or more contextual rather than intrinsic issues.
@mariofusco Or that Static Typing was Bad (tm) and duck typing was awesome, only to turn around and start adding static typing to duck-typed languages several years later.