Alter Ego

@pipsandbills

web3 is my alter ego. https://x.com/pipsandbills https://zora.co/@pipsandbills

101 following39 followers

Latest casts

Alter Ego@pipsandbills·
Reply

mobile not very friendly

Alter Ego@pipsandbills·

My estimated Farcaster Protocol retro rewards allocation is 32.2592 tokens. Check yours 👇 snap by @mvr

Alter Ego@pipsandbills·

Guess I would move from farcaster to full port on base app

Alter Ego@pipsandbills·

I was scanning through the @zama token address and noticed 12% (1.32b) of supply was resides in a proxy contract ca: 0xfC8F904F025F1eFF02a0A6C3a6FEa50Bb7E5cFa2 my first guess was what if that was the claim proxy contract (note: it's not a claim contract) for the sake of speculation: let's assume a high end of 12% and a low end of 1% allocated to zama creator program $zama was valuated at $1B in its last funding round, which gives us a speculative price of $0.091 at launch the total zama og nft is 2750 (if season 4 is 1000 winners) allocation per nft: • based on the 12% allocation: each og nft would eligible for 480k $zama • based on a 1% allocation: each og nft would eligible for 40k $zama if the valuation stands true, even a 1% allocation to nft holders is 4 figures! so if you see this, let it inspire you to create for the zama and fhe

Alter Ego@pipsandbills·
Reply

. @zama 's fhe/concrete ml lets you compute on encrypted data without decrypting it. Meaning: • the chain can run anti-money laundering logic • the chain can run compliance checks • the chain can confirm risk scores • the chain can detect sanctioned addresses • the chain can verify user categories but the chain and regulators never sees the user’s data, balances, transfers, and metadata. so if you wanna be a compliant privacy infra/token, it's best to integrate fhe alongside any other model, a proof of this concept can be seen in this paper publication that features zama's concrete ml https://www.researchgate.net/publication/385559721_Privacy-Preserving_Graph-Based_Machine_Learning_with_Fully_Homomorphic_Encryption_for_Collaborative_Anti-Money_Laundering

Alter Ego@pipsandbills·

did you know that tokens like zcash's $zec, monero's $xmr would be delisted from binance in countries like france, italy, spain and poland why? because of a simple anti-money laundering rule. these infra/tokens provide privacy (and selective privacy) but disallow compliance check when needed. if money was laundered through any of them, it might become untraceable because they offer zero visibility checks. but here is the thing: regulators don't need to see the data, they just need to confirm compliance - a specialty of the fhe infra which zama offers

Alter Ego@pipsandbills·
Reply

@zama 's fhe/concrete ml lets you compute on encrypted data without decrypting it. Meaning: • the chain can run anti-money laundering logic • the chain can run compliance checks • the chain can confirm risk scores • the chain can detect sanctioned addresses • the chain can verify user categories but the chain and regulators never sees the user’s data, balances, transfers, and metadata. so if you wanna be a compliant privacy infra/token, it's best to integrate fhe alongside any other model, a proof of this concept can be seen in this paper publication that features zama's concrete ml: https://www.researchgate.net/publication/385559721_Privacy-Preserving_Graph-Based_Machine_Learning_with_Fully_Homomorphic_Encryption_for_Collaborative_Anti-Money_Laundering

Alter Ego@pipsandbills·
Reply

miden is one of the strongest zero-knowledge VMs being built today. It gives you: • private computation (your execution trace stays hidden) • STARK-based cryptography method • verifiable correctness • a scalable zk-first architecture this is huge. but there’s one thing miden cannot give: a guarantee of end-to-end encryption. why? because zk proves correctness, it does not hide data but when you combine that with fhe, you can have computation on a hidden data that has been proved correct! meaning: • storage = encrypted • mempool = encrypted • execution = encrypted • state = encrypted • node visibility = zero this is the actual end-to-end encryption. so with zama inside miden, you could have an end-end encrypted chain that works even if the sequencer operator are malicious tldr miden gives private computation. zama gives private data. put them together and you get something better: a verifiable, encrypted, adversary-proof L2.

Alter Ego@pipsandbills·

going over miden's zk-based privacy architecture and realized something important: miden will launch with a centralized sequencer, and with zk alone, that means the sequencer can still see your data. it's like sending a whatsapp message where the encryption only hides how the message was typed but whatsapp hq can still read the actual message that means the “privacy” tagline isn’t end-to-end yet. what you have is a computation privacy not data privacy but that could be improved with @zama 's fhe integration let's break that down 🧵