be me: yesterday I found randomly a paper about 2 Circle STARK friendly hash functions working with Mersenne M31 (RPO-M31 and XHash-M31: Efficient Hash Functions for Circle STARKs by Tomer Ashur1 and Sundas Tariq) then i was: ohhh wow, looks interesting. then: write a rust implementation then start thinking: wait, maybe it could be a good candidate for a Circle STARK friendly AND Bitcoin Script friendly hash function then: start doing analysis and cost estimate then realise that they would NOT be practical to implement in Bitcoin Script... It's a pity for this but still it's very interesting hash functions, and the fact that they natively work with M31 is super promising. Maybe it's worth building a Cairo and Solidity implementation and benchmark the costs. They might be more interesting to use than Poseidon for Circle STARKs M31. Paper: 📄.pdf Rust repo: image
Gm from Hong Kong Nostriches. image
Bitcoiners in Hong Kong, register and come to our event on Monday. We will discuss covenants, Rollups, STARKs, Cashu, Lightning network and more. #BitcoinEvent #BitcoinConference #BitcoinDevsGathering
What can you do with Monero style ring signatures for Nostr ? You can build an Anonymous Voting platform using Nostr identities to vote. Thanks to the Back's Linkable Spontaneous Anonymous Group, you can detect double voting without leaking identities. Check Ringable demo 👇 A client-side anonymous voting platform using Nostr-compatible ring signatures. Ringable allows users to create proposals and vote anonymously as part of a predefined group (a "ring" of public keys). It leverages the cryptographic power of bLSAG ring signatures to ensure that while votes are verified as coming from a valid member of the ring, the specific voter's identity remains hidden. The cryptographic functions are powered by the Nostringer Rust library, compiled to WebAssembly (WASM) for use in the browser. Live demo: Ringable rep: Nostringer: