Soma
211 posts


Phone? Ha…
This is not going to be a phone.
And of course they’re going to build a consumer hardware device.
sam lessin 🏴☠️@lessin
These aspiring tech platform companies... always with the "we need to build a phone"... jeez theinformation.com/articles/desig…
English

@SukhansAsrani @safe @jaibhavnani yeah makes sense, though this all really depends on the target use case and is not that useful to talk about in the abstract
looking forward to the blog post!
English

@somamine @safe @jaibhavnani Wait for the blog post :)
Revocation / key refresh / DKG is generally necessary for: adding/removing new signers, recovery, redundancy if any of the provider's key shares are compromised.
English

We spent months with top auditors building out an enterprise-grade MPC backend for Waymont.
MPC EOA solutions have unsolvable issues with key recovery and storage - so we pivoted hard.
Self-custody built on @safe is literally 10x safer.
vitalik.eth@VitalikButerin
@yugacohler MPC-based EOAs are fundamentally flawed because they cannot revoke keys (and no, re-sharing doesn't count; the old holders can still recover the key). Smart contract wallets are the only option.
English

@SukhansAsrani @safe @jaibhavnani @SukhansAsrani bumping this as i'm genuinely curious to get your take!
English

@SukhansAsrani @safe @jaibhavnani - what are biggest attack vectors? HSMs + virtualized secure enclaves + good security practices take you quite far
- isn’t every wallet provider subject to insider risk? (e.g. rainbow employee submits malicious update)
- why does revocation matter if user has share client-side?
English

@LindellYehuda @coinhackerio @TalBeerySec @OurielOhayon @coinbase Hey Yehuda!
Another quick follow-up: are there any plans to make WaaS available on the web (with wasm or something), or will it only be on mobile for now?
English

@somamine @coinhackerio @TalBeerySec @OurielOhayon @coinbase Unfortunately that certainly won't be the case... 😀
English

@LindellYehuda @coinhackerio @TalBeerySec @OurielOhayon @coinbase awesome, thanks for the quick reply!
excited to dig in when you guys do open source it, so hoping “not too distant future” is in the next few weeks 😆
English

@somamine @coinhackerio @TalBeerySec @OurielOhayon @coinbase We are very much in favor of open source, and believe that it's very beneficial to the community. There's nothing to confirm right now, but hopefully there will be in the not too distant future.
English

@LindellYehuda @coinhackerio @TalBeerySec @OurielOhayon @coinbase Just tweeted at you -- just curious if you guys are planning on open sourcing the cryptography underlying Waas anytime soon?
I know coinbase open sourced kryptology, but that it was archived for what's presumably the new system powering waas. thanks!
English

@coinhackerio @TalBeerySec @OurielOhayon @coinbase Coinbase certainly cannot recover the users key. The MPC wallet is self custodial.
English

@tracesoftears00 @tryamie @SuperlistHQ @Cron @TextsHQ hey! I unfortunately don't have an amie or superlist invite, but have been looking for a texts invite for the loongest time.
if you're feeling kind, i'd love to get one :) thanks!
English

@ZORAEngineering aight vibes vibes
that + the other stuff in your public repos should be enough rn ty <33
English

@somamine is in a big monorepo with a bunch of other things rn, i absolutely would if it was a neat thing. design system is on npm tho 👀👀🫣
English

@ZORAEngineering ayo! you guys have any plans to open source your sexy new zora frontend?
English

@ZORAEngineering i just wanted to build this experiment on it and then be able to @ you guys like yo check this out
gonna either have to hack my way thru minified source code or you cuties can just share the repo w me? 🥺👉👈
English

@somamine oooo maybe? i have a hunch that we’d focus on open sourcing the design system first & making it robust. any parts in particular you like / wanna see src?
English

turns out jpegs are lower in maslow’s hierarchy than we thought :/
cointelegraph.com/news/looks-bar…
English

@pugson @DeFiDaniel @rainbowdotme @ensdomains appreciate the reply!
1) is rainbow paying pinata to keep the photos pinned?
2) why not link the raw ipfs url (“ipfs://“) on-chain so apps can choose whatever gateway they want to render the image?
with tht you could still obviously route through pinata in the rainbow app
English

@somamine @DeFiDaniel @rainbowdotme @ensdomains if you’re using NFTs then the ENS metadata will point to the NFT using the contract address / token id. more info here: medium.com/the-ethereum-n…
for non-NFT uploads we save a pinata ipfs url in the avatar field
English

@DeFiDaniel @pugson @rainbowdotme @ensdomains ah unfortunately can’t make it! fairly straightforward question tho haha, someone from team just needs to see it 👌 cc @pugson
English

@somamine @pugson @rainbowdotme @ensdomains Learn more or ask question in a twitter Spaces scheduled for later today (@ensdomains )
English

@pugson @DeFiDaniel @rainbowdotme @ensdomains where do uploaded (non-nfts) PFPs and cover photos get stored? ipfs with a link to the cid on-chain? or is the photo literally on-chain?
English

@inversebrah still wonder where it all went wrong after i read a tweet like this and realize i understood everything immediately
English



