YAS
229 posts

YAS
@yetanotherswap
Yet Another Swap on @Starknet. Crafted by @yetanotherco and forged by @class_lambda.

Mina on Aligned incoming: The kimchi integration from @o1_labs is done we will be merging it soon and after that we will start testing some e2e integrations. This will be a great way to use @MinaProtocol tech on Ethereum and different L2s. For the impatient you can check the PR: github.com/yetanotherco/a…







People ask me why we have our own Circle STARK implementation (Stwo), separate of plonky3. Stwo's main and only goal is to accelerate Starknet. Through fast cairo and recursion proofs. This concreteness allows us to advance fast and write optimized code.

Private Testnet Update Over the last few days we have been onboarding different validators to our first testnet using Cosmos SDK. This version includes a Plonk + KZG verifier we will be adding more in the new versions. Aligned has now 10 validators that have been extremely helpful providing valuable feedback. Thank you! We will be onboarding a couple of more people to this first version and then fully open it to the public. Check it out here: explorer.alignedlayer.com


@thisisrj @alignedlayer To align or not to align that is the question.








Accelerating Storage Proof adoption: We are happy to share our first aligned partnership with @HerodotusDev ! Together, we will make interoperability between Ethereum layers faster, cheaper, and more accessible than ever before. Developers can now build any secure interoperable and data-intensive protocol while still enjoying competitive fees.

We have just ran the verification of a pairing computation of arkworks using SP1 of @SuccinctLabs. We did not have to make any modifications to the Arkworks code. I am testing ideas for @alignedlayer. We’re trying different ideas to aggregate proofs and post them in Ethereum after a few hours. Proof time was around 18 minutes, and proof size was 568 MB. The advantages of SP1 are the fact that it is open-source, has relatively fast proof generation. The problem is that it has larger proof sizes. On the other hand, @RiscZero has continuations (which makes proof smaller and breaks down computations into smaller pieces that can be handled separately), and smaller proof sizes, but it is has some closed-source part and it seems slower in CPU (we didn’t run benchmarks). We believe that the best solution will take approaches from both worlds.

We have just ran the verification of a pairing computation of arkworks using SP1 of @SuccinctLabs. We did not have to make any modifications to the Arkworks code. I am testing ideas for @alignedlayer. We’re trying different ideas to aggregate proofs and post them in Ethereum after a few hours. Proof time was around 18 minutes, and proof size was 568 MB. The advantages of SP1 are the fact that it is open-source, has relatively fast proof generation. The problem is that it has larger proof sizes. On the other hand, @RiscZero has continuations (which makes proof smaller and breaks down computations into smaller pieces that can be handled separately), and smaller proof sizes, but it is has some closed-source part and it seems slower in CPU (we didn’t run benchmarks). We believe that the best solution will take approaches from both worlds.



Celestia is the most minimal blockchain you could build.

