Z561

ZK-STARK | 🦀 | 🐧

[Z561 @_Z561]

Ok I have a huge announcement. After many decisions, I decided to publish my first book of a series of 2. The title will be "Agebraic Foundations of Cryptography 1". I'll postpone the ZK-STARK book even though I have already written the most of it. This is because I need more context to understand Reed Solomon complexities. This series of books will bring every aspiring cryptographer to the point, skipping elliptic curves complexity because they will be obsolete at some point in the future. I'll focus on algebraic structures which will be the foundation of cryptography inside computers forever (yes, forever until the sun will implode). This means these two books will never be obsolete and will bring foundations for PQ resistant cryptography. I'm going to publish on Google Play books, and avoid ArXiv because of the thousands of policies I do not have the time to solve. At the end of the book, I wrote the proof for the cardinality and order of subgroups for any integer.

[Z561 @_Z561]

I don't remember shit about UUPS, but insert is external, this means we can trigger insertion, and this means we can trigger _hashNodes. If this contract was deployed then .customHasher is true and this means we can trigger compress. There must be a way to call _authorizeUpgrade through compress by analyzing storage stuff in UUPS implementations.

[shielded victor @starkience]

STARKNET HAS THE CHEAPEST PRIVACY SOLUTION:

Shielding and unshielding. Swaps. Transfers. Lending. Borrowing. All priced at ~14cts per Tx. No costs denominated in the % you're swapping.

Try it out yourself. Shield and swap any ERC20 on your Ready or Xverse wallet.

[Z561 @_Z561]

Crazy well made as always.

[Z561 @_Z561]

@starkience @Starknet Crazy well made as always.

[shielded victor @starkience]

Analogy of how the @Starknet privacy pool works:
> Deposit into the pool (aka, shield assets)
> [private]
> [private]
> [private]
> Withdraw from the pool (aka, unshield assets)

Live: https://t.co/9mg8f5GM7F

[Z561 @_Z561]

@lonelysloth_sec You mean Claude code? 😂

[Z561 @_Z561]

@omg_AMZ @windhustler Then you have your answer, Linux is cheap while not being a low standard choice. White person? Seems like we have a racist White gal here. Done replying by the way.

[Z561 @_Z561]

@omg_AMZ @windhustler Ever heard about Linux? There's not only Windows and MacOS. Windows is a low standard choice for normies.

[Z561 @_Z561]

[https://t.co/Xrk8zpaXSl]

[Z561 @_Z561]

@ddimitrovv22 Tf is DAML now 😂😭

[Z561 @_Z561]

@ADPthegreat Robbery, all these kind of platforms must disappear.

[Z561 @_Z561]

@EliBenSasson

[Z561 @_Z561]

@totdking Not for long bro 📈📈📈

[Z561 @_Z561]

Ok this one is important to elaborate on.

IF we talk about ZK-PROOF-FORGERY -> VERIFICATION, then it's true it might be impossible to detect malicious stuff and this is an huge problem for privacy solutions. As Zcash's being a clear proof of this. Nobody knows if there really is a bug or not which is crazy.

IF we talk about SIG(DATA) -> UNSIG(DATA) = DATA -> EXEC -> ZK-PROOF-FORGERY -> VERIFICATION then the Zcash problem doesn't persist because we can monitor events in smart contracts. This is why, for the moment, Starknet legacy is safe.

I bet they considered this problem carefully for STRK20, but for the moment I don't know how all the privacy magic works so I stfu respectfully.

Having said all these things there's one more thing I want to consider.

This field is absolutely new, it's fine there are big security problems to be solved. Back in 1990 every single computer on Earth could be rooted using copy paste exploits because we were still digesting computers diffusion. This is a really hard problem to solve: yes. It is unsolvable? I don't think so.

[Dankrad Feist @dankrad]

This is generally one of the problems with zk. Exploits become impossible to detect.

This is one of the reasons I was always skeptical of zk rollups which only publish state changes. A defi hack on such a chain would be insanely hard to debug, because the only thing that's visible would be a transaction that credits all the funds to the exploiter.

All of which makes me more bullish on constructions like Tempo Zones!

[Z561 @_Z561]

Chapter 13 of Rust book. From chapter 13 one really start accusing fatigue. I love Rust but I'm fucking done. Nonetheless, I'll get to chapter 21. I've also decided to ship my Rust book version using Mintlify. I'm sure many people will like it and prefer my version to the usual Rust book. Rust book is really well made but it has 2 main problems.

- Colors suck. Especially after 10+ chapters you literally throw Navy blue (story doesn't change if you change color, try). Catpuccin syntax highlighting SUCKS. FUCK YOU IF YOU USE CATPUCCIN. Dark Plus for the win.
- Too verbose, especially on stoopid things.

I'm going to fix these things and better clarify when required on complex stuff.

[Z561 @_Z561]

Rate my landing page from 0 to - 0.

https://t.co/dlneQVw6W3

[Z561 @_Z561]

@cantinasecurity @injective 👉🏻 @al_f4lc0n 👈🏻