sCrypt Official | OP_CAT 🐱

6.4K posts

sCrypt Official | OP_CAT 🐱 banner
sCrypt Official | OP_CAT 🐱

sCrypt Official | OP_CAT 🐱

@scryptplatform

OP_CAT 😺 enjoyer since 2018. Join fellow OP_CAT builders at https://t.co/wddaS9uYAi.

On Chain Entrou em Temmuz 2009
3.9K Seguindo10.4K Seguidores
Davinci Jeremie
Davinci Jeremie@Davincij15·
I'm looking for a Bitcoin second layer that gets it right. Balances are easy to withdraw. Self-custody is the default. Reserves are visible to everyone. Censorship is obvious when it happens. Risk is capped. Settlement to Bitcoin is always possible. If it doesn't exist yet, I'll build it. Who's working on this? 👇
English
252
35
383
48K
sCrypt Official | OP_CAT 🐱
sCrypt Official | OP_CAT 🐱@scryptplatform·
Tools are to AI what oracles are to crypto. Both AI and blockchains are blind by design. LLMs need tools to see the world. Blockchains need oracles to see the world. Tools = AI’s oracle. Oracles = Blockchain’s tool. Same architecture problem. Different stack.
English
1
0
8
641
sCrypt Official | OP_CAT 🐱
sCrypt Official | OP_CAT 🐱@scryptplatform·
#OPCAT allows bridging to be trustless, not trust-minimized as in BitVm
Robin Linus@robin_linus

@boyacaxa @SuperTestnet @idealgroup @liameagen @therealyingtong BitVM isn’t the endgame. The endgame is improving Bitcoin’s scalability and privacy with Shielded CSV. If better opcodes can render BitVM unnecessary, I’m all for it--and we’re contributing to soft-fork proposals that move things that way. eprint.iacr.org/2025/068

English
0
2
7
778
sCrypt Official | OP_CAT 🐱
sCrypt Official | OP_CAT 🐱@scryptplatform·
#OPCAT based quantum resistance offers neutrality, same reason why Satoshi chose secp256k1, not NIST-designed curve secp256r1 (P-256) @opcatlabs/op-cat-and-bitcoins-path-to-quantum-resistance-d416da1a9870" target="_blank" rel="nofollow noopener">medium.com/@opcatlabs/op-…
sCrypt Official | OP_CAT 🐱 tweet media
Shinobi@brian_trollz

To everyone going "NIST this!" or "NIST that!" in regards to quantum safe crypto, and "standardizing around NIST standards!" and "NIST has schemes, why don't we do them already?!": Satoshi SPECIFICALLY chose a curve NOT APPROVED by NIST. Ask yourself why.

English
2
2
14
1.3K
utxo detective
utxo detective@hbeckeri·
I’ll concede. But that serial construction off chain is quite the dev ux struggle Imagine trying to build a hyperliquid style CLOB w/ cancel priority Only way I think would be to have some central sequencer that would handle ordering and then design a contract that uses signatures against a message but not the utxo
English
1
0
1
127
sCrypt Official | OP_CAT 🐱
sCrypt Official | OP_CAT 🐱@scryptplatform·
Ethreum L1 cannot scale since it uses global state and is thus single-threaded. Bitcoin’s UTXO model remains the most horizontally scalable tech, as I explained years ago scryptplatform.medium.com/bitcoin-vs-eth…
vitalik.eth@VitalikButerin

There have recently been some discussions on the ongoing role of L2s in the Ethereum ecosystem, especially in the face of two facts: * L2s' progress to stage 2 (and, secondarily, on interop) has been far slower and more difficult than originally expected * L1 itself is scaling, fees are very low, and gaslimits are projected to increase greatly in 2026 Both of these facts, for their own separate reasons, mean that the original vision of L2s and their role in Ethereum no longer makes sense, and we need a new path. First, let us recap the original vision. Ethereum needs to scale. The definition of "Ethereum scaling" is the existence of large quantities of block space that is backed by the full faith and credit of Ethereum - that is, block space where, if you do things (including with ETH) inside that block space, your activities are guaranteed to be valid, uncensored, unreverted, untouched, as long as Ethereum itself functions. If you create a 10000 TPS EVM where its connection to L1 is mediated by a multisig bridge, then you are not scaling Ethereum. This vision no longer makes sense. L1 does not need L2s to be "branded shards", because L1 is itself scaling. And L2s are not able or willing to satisfy the properties that a true "branded shard" would require. I've even seen at least one explicitly saying that they may never want to go beyond stage 1, not just for technical reasons around ZK-EVM safety, but also because their customers' regulatory needs require them to have ultimate control. This may be doing the right thing for your customers. But it should be obvious that if you are doing this, then you are not "scaling Ethereum" in the sense meant by the rollup-centric roadmap. But that's fine! it's fine because Ethereum itself is now scaling directly on L1, with large planned increases to its gas limit this year and the years ahead. We should stop thinking about L2s as literally being "branded shards" of Ethereum, with the social status and responsibilities that this entails. Instead, we can think of L2s as being a full spectrum, which includes both chains backed by the full faith and credit of Ethereum with various unique properties (eg. not just EVM), as well as a whole array of options at different levels of connection to Ethereum, that each person (or bot) is free to care about or not care about depending on their needs. What would I do today if I were an L2? * Identify a value add other than "scaling". Examples: (i) non-EVM specialized features/VMs around privacy, (ii) efficiency specialized around a particular application, (iii) truly extreme levels of scaling that even a greatly expanded L1 will not do, (iv) a totally different design for non-financial applications, eg. social, identity, AI, (v) ultra-low-latency and other sequencing properties, (vi) maybe built-in oracles or decentralized dispute resolution or other "non-computationally-verifiable" features * Be stage 1 at the minimum (otherwise you really are just a separate L1 with a bridge, and you should just call yourself that) if you're doing things with ETH or other ethereum-issued assets * Support maximum interoperability with Ethereum, though this will differ for each one (eg. what if you're not EVM, or even not financial?) From Ethereum's side, over the past few months I've become more convinced of the value of the native rollup precompile, particuarly once we have enshrined ZK-EVM proofs that we need anyway to scale L1. This is a precompile that verifies a ZK-EVM proof, and it's "part of Ethereum", so (i) it auto-upgrades along with Ethereum, and (ii) if the precompile has a bug, Ethereum will hard-fork to fix the bug. The native rollup precompile would make full, security-council-free, EVM verification accessible. We should spend much more time working out how to design it in such a way that if your L2 is "EVM plus other stuff", then the native rollup precompile would verify the EVM, and you only have to bring your own prover for the "other stuff" (eg. Stylus). This might involve a canonical way of exposing a lookup table between contract call inputs and outputs, and letting you provide your own values to the lookup table (that you would prove separately). This would make it easy to have safe, strong, trustless interoperability with Ethereum. It also enables synchronous composability (see: ethresear.ch/t/combining-pr… and ethresear.ch/t/synchronous-… ). And from there, it's each L2's choice exactly what they want to build. Don't just "extend L1", figure out something new to add. This of course means that some will add things that are trust-dependent, or backdoored, or otherwise insecure; this is unavoidable in a permissionless ecosystem where developers have freedom. Our job should make to make it clear to users what guarantees they have, and to build up the strongest Ethereum that we can.

English
13
42
97
7.8K
utxo detective
utxo detective@hbeckeri·
@scryptplatform Long chains of spends need to be processed serially too though in the UTXO model, which is hard to avoid when making anything that requires stateful utxos
English
1
0
0
104
sCrypt Official | OP_CAT 🐱
sCrypt Official | OP_CAT 🐱@scryptplatform·
@hbeckeri That’s the huge bottleneck: “serially process the ones that read/write from same accounts”. In contrast to accounts, all UTXOs are disjoint, after double spent check
English
1
0
8
302
utxo detective
utxo detective@hbeckeri·
@scryptplatform Global state doesn't necessarily mean single threaded. For ex. solana can process disjoint txs in parallel, only needing to serially process the ones that read/write from same accounts. They are effectively the UTXO model + global state
English
1
0
0
339