the ocean has given me much more than has taken

contribute to concrete -> get rewarded some good-first-issues nice and ready to be worked on!

When VCs get together, they talk about trends and moats and valuations. When builders get together, they talk about where to buy cheap compute.

open-sourcing soon

you are welcome

so true

Demo testnet will be up for a limited time. Start playing now: rts.concretelabs.dev Ready player one.

Ark’s high-level rules, like map setup, ending conditions, and unit & building stats, are all in a Solidity smart contract, while the low-level RTS mechanics, like movement and combat, are built into the chain in the form of a Concrete stateful precompile. New games can be built on top of the same high-performance engine as Ark and use the same base client just by writing Solidity.

Introducing Ark RTS and the Archetype Engine: A new model for fully onchain games Ark RTS is a fully onchain real-time strategy game drawing inspiration from iconic titles like Command & Conquer and Warcraft 3. You can play it right now. No waitlists (see below). Archetype is the engine powering Ark. By vertically integrating the client, smart-contract framework, and the chain, it unlocks multiple novel features for onchain games: ⏳Ticking: The game world is always in action, even when players are not directly interacting with it. 🕹️Real real-time: Instant-feedback interactions and fluid real-time movement. 💾 Quick sync: The custom OP Stack execution engine has a built-in state snapshotter to make syncing the game client extremely fast.

typescriptoors gonna hate me for this

Shoutout to @ETHGlobal & @latticexyz -- the AW hackathon was one of the "aha" moments where I realized how insanely powerful it is to run the same code in the client as onchain, one of the defining features that helped set the direction for Concrete and [redacted].

Bullish on rollup proofs based on general-purpose VMs (like OP Cannon is on MIPS and risc0 on RISC-V). Building a Cannon prover for Concrete took a couple hours and instantly added support for OP Stack fault proofs to every Concrete rollup. Under the program-specific approach (e.g., most zkEVMs), this would take from days to weeks for *every* distinct rollup. Hard to see a landscape full of app-specific rollups without the engineering leverage of general-purpose VM proofs. Program-specific is still the way to go when minimal-overhead validity proofs are required, but I don’t think that will be the case for many of these chains.

literally tick chain 2

stonks so good yes yes yes

Autonomous Worlds are the post-scarcity substrate for meaning

Big thanks to @lermchair and @0xhank for seeding the conversation with their @0xPARC hackathon project and @FlynnCalcutt @cha0sg0d_ and others for their ideas and feedback.

I may or may not have accused @_yonada of being a communist spy at some point while arguing about ticking in Bogotá. This is the result:

on-chain -> onchain application-specific blockchain -> appchain op stack rollup -> ???

How do we build a dashboard for technological progress? Thinking about: - Worldwide available compute, storage, bandwidth, energy, etc. over time - Stats for the price per FLOPS, GB, GB/s, kilowatt-hour - Same stats for tokens/s for various sizes of Large Language Models

look mom it's me