←
buz1,980 posts
buz avatar

buz

@buz_eth

Graduated from Jpegs with scars to prove it.

◷ Joined October 2021▧ 254 Photos and videos
buz avatar
buz@buz_eth·Nov 12

The full time job is about to turn into a full team's full time job. *Recruiting* - Ethos Police Officer - Upholding the standards of the reputation network. Benefits - access to all the tools you'll need to find abuse and support to address it swiftly. Pay - discord gifs.

For almost two years, the only way into Ethos was an invite from someone already here. That kept the network small while the scores proved they could tell real people from spam Turns out they can. Really well. So today we're announcing invites are gone... anyone can join Ethos

Post attachment
buz avatar
buz@buz_eth·Nov 7

Big fan of @Fr0oZi and their work. Had some fun running around the game and looking forward to messing around more as it develops

They went digging for coal They came back with a war Nobody leaves. The dragon doesn’t allow it The war is coming to @RobinhoodCrypto. The first to feed the fire stand at the front of it Whitelist open. The FREE mint is coming feedfirerh.com

0:30
buz avatar
buz@buz_eth·Nov 5

I've been a big fan of @wiimee content for going on a year as I wrote in my review 8 months ago (ethos.to/2GHrJC). His witty takes on security are some of my favourites in this space and it's a perfect match for Ethos as he continues to highlight how to avoid scams, dodgy actors and general crypto. If you haven't seen his YouTube, you definitely should check it out. Can't wait to see how he integrates Ethos into them. youtube.com/@wiimee

Meet our newest verified Ethos Curator: @wiimee. Verified Curators are a new tier in the Curators program. Here's what it means, and why WiiMee 🧵

Post attachment
buz avatar
buz@buz_eth·Nov 5

Update on @umia_finance extension and the @SlopCash auction. Umia's team reached out and said they'd update things, and early bidding opens around 16:15 UTC today, so I re-checked the live pages, the contracts and the public code. Short version: this sale is much safer than I feared, but what I flagged is mostly still there and the team haven't publicly addressed/corrected any of the concerns. WHAT'S CHANGED The criteria are out, and the risk for this sale is significantly lower. Nothing for this sales asks for Google, email, an AI account or a centralised exchange. Three ways into the early round: - Contributors: a GitHub proof through the extension. A merged PR or reviews on 5 PRs on SlopCash or elizaOS in Q3, or owning a public repo with 50+ stars. $200k pool. Per wallet, the auction page still says $5k, but the contract was lowered to $3k on 4 Nov and Umia's blog says $3k. - UMIA holders (Umia Pass): 1,000+ UMIA in the bidding wallet for 7 days. $250 base, up to $2.5k with boosts. No extension for the base or the holding boosts. The optional Echo and fomo boosts do need it. - Whitelisted funds and angels: funds have about $200k in total, at the same clearing price as everyone. The contract backs this up: the early round accepts exactly five proof types, all five are the GitHub ones, and the public rounds accept none. The sale terms moved too. The page no longer says the early round is 20% of the auction (9M SLOP) or that funds can take up to 15%. The separate liquidity allocation, 20% of proceeds paired with 9M SLOP, hasn't changed. Nothing is released during the early window; early bids start filling when the public round opens, around 15:50 UTC on 7 Nov. It closes around 15:20 UTC on 10 Nov. WHAT HASN'T CHANGED This is the disappointing part and what would be easy enough for the Umia team to address. It's a quick win to put people at ease. - The auction page still says "nothing from your accounts is shared or linked to your wallet". Umia's 4 Nov blog says the same about GitHub. Umia's own Security page says the contract records on-chain which wallet holds each pseudonymous identity, and Umia holds the key behind that pseudonym. Hidden from the public, maybe. Not unlinked. It's a one-sentence fix. - The real recipes, the rules for what each proof reads and reveals, still aren't published, and Umia's docs still say privacy depends on them. The first early bid made with a proof will show what actually lands on-chain. - The Chrome store still says no data is collected. The extension's own privacy doc says proofs and usage events go to Umia, and that the privacy policy needs an extension section. That policy is still dated 23 March, with no mention of the extension and no deletion period. - Certora audited Umia's contracts, but I still can't find an independent audit of the extension from Reclaim or Umia's proof server. - Open code still doesn't settle it. The store moved to v0.5.0 today, the day bidding opens, while the public repo is still v0.4.0, untouched since 15 Oct. There's probably a simple reason (Umia's app requires 0.5.0 for fomo proofs), but what shipped can't be matched to public code. Two things to add: - Umia's Security page says its proof server never learns your handle. Reclaim has a blinded mode that could deliver that, but Umia's server code switches it off, and the extension, like Reclaim's own extension SDK, only supports the raw mode: the value is revealed to the server, which computes the pseudonym itself. Umia's tests capture GitHub's numeric user ID this way, and that ID maps to a username. Umia's stated reason is fair: an open blinded endpoint would let anyone match handles to on-chain pseudonyms. But the docs don't describe what the code does. The real recipes are private, so I can't confirm production. - The auction's validation contract and the proof verifier share one owner: a plain address, not a multisig or timelock contract. It may be well protected behind the scenes, but that can't be seen from outside. It can change accepted proofs, caps and the permit signer, with no lock once the auction starts, and it was still swapping the 50-star proof around 13:00 UTC today. The two-day timelock in Umia's docs covers protocol-wide settings. RISKS THAT REMAIN - GitHub: in the last public code, approving the site gives the extension all of github.com, including login cookies, until you remove it, and updates land silently. Minor for a hobby account, serious for anyone with org admin or publishing rights, and this lane is aimed at developers. - Echo and fomo boosts: investment and trading accounts under the same access issues as above. Each raises your ceiling by roughly $250 to $1,250, from an extra first-come pool. Pass bids must come from the wallet holding your UMIA, so a fresh wallet isn't an option. I'd skip them. - Linking: Umia can connect your account to your wallet. Its public code has no per-auction input to the pseudonym, which points to the same on-chain fingerprint across launches, linking your wallets, unless the key changes. That isn't confirmed. How long proofs and IP logs are kept still isn't stated. - Next time: the Pass carries over to every Curated launch that offers a lane, and Umia's app code still includes a potential Google verification. Lower risk here doesn't mean lower risk there. Check each launch. - I still think fake extensions and "verify now" DMs are the likeliest way to lose money. For this sale, the lowest-risk routes are the Pass base allocation or the public round, with no extension either way. I still don't think this is bad faith, and publishing narrow criteria was the right call but I've not seen any direct addressing of concerns. Trust me bro shouldn't fly in 2026.

buz@buz_ethNov 3

Bit of morning doomscrolling surfaced an @AzFlin tweet about @umia_finance requiring a chrome extension to be installed for early access waves of the @SlopCash sale. I had some spare claude credits so went deep diving what they were doing.

buz avatar
buz@buz_eth·Nov 3

I hope there are easy answers and quick fixes to sure up trust ahead of the sale. In a world where fridges and nuke alarms are getting hacked, maybe it's worth getting clarity on how your data is getting used and stored. Any errors above can be sent to claude customer support

buz avatar
buz@buz_eth·Nov 3

To be clear, none of this means Umia is acting in bad faith. The auction needs a way to stop one person using 50 wallets. But "nothing linked to your wallet" isn't accurate, the trust all sits with Umia, and the riskiest part (which accounts you'll connect) lands on opening day.

buz avatar
buz@buz_eth·Nov 3

Key questions for Umia: - Per criterion: which site, what's read, what's on-chain? - Is my account scrambled on-chain, and by whose key? - How long are proofs and IP logs kept? - Who holds the admin keys? - Will updates freeze mid-auction? - Any independent audit?

buz avatar
buz@buz_eth·Nov 3

After proving, remove site access and log out - Ignore every "verify now" DM - Read what you sign: sign-in, USDG approval, bid. Never setApprovalForAll, unknown Permit/Permit2, wallet upgrades or seed phrases - Revoke the USDG approval after: revoke.cash

buz avatar
buz@buz_eth·Nov 3

Some security steps: - Simplest: skip it and bid in the public round - Separate VM, Chrome profile or browser, nothing else logged in - Fresh wallet (it won't pass wallet-history criteria like UMIA holdings) - Approve only the site you expect. Read the perm requests

buz avatar
buz@buz_eth·Nov 3

"But it's optional." Only if you skip early access. Days 1-2 (20% of tokens set aside) need a verified wallet or a spot on Umia's allowlist. Days 3-5 don't. The criteria land on opening day, so you'd decide in a rush. Optional means you can say no, not that it's safe.

buz avatar
buz@buz_eth·Nov 3

The code isn't where the risk sits. What it reads on each site, and code it runs there, comes from Umia's server when you verify. Updates land silently. 399 users and no independent audit I can find. Open code today doesn't show what it'll be asked to do on opening day.

buz avatar
buz@buz_eth·Nov 3

"But it's open source." ~NFTBoi. The GitHub repo is a copy of a private one, and the Chrome store version was built from a commit that isn't in it, so nobody outside Umia can check they match. It also still accepts messages from Umia's test sites. github.com/umiafinance/exten…

buz avatar
buz@buz_eth·Nov 3

We don't know the criteria but below are some options with risks allocated. Google or email: critical issue. Your inbox resets everything else Exchange or investor account: high to critical AI accounts (Claude, ChatGPT etc): high GitHub: medium to high (devs) X or Discord: high

buz avatar
buz@buz_eth·Nov 3

zkTLS reads your logged-in session. It doesn't use the limited permissions of a normal "Sign in with Google" button (name and email, no extension), which would be far safer. We don't know which route they'll take. If the extension asks for google domain, it's the first one.

buz avatar
buz@buz_eth·Nov 3

The other criteria drop on opening day. The extension's built-in list already names GitHub, X, Google, Luma, Snapshot and "other". Umia's own store notes name the whole google domain: Gmail, Drive and everything else, with your login cookies. github.com/umiafinance/exten…

buz avatar
buz@buz_eth·Nov 3

Umia's server can also send code that runs on the site you're verifying, in your logged-in session. It's checked for tampering, not approval. Hijacked updates already hit Cyberhaven and Trust Wallet ($8.5m drained): socradar.io/blog/phishing-at… securityweek.com/shai-hulud-…