👀

That's nuts! Great work 💪

How does it look like from client perspective? Will mint client be able to tell easily if he's using legacy or TEE mint?

Is it interoperable with inflatable versions?

Seu lindo.

👀

you gotta threat model this better or else it looks like fud. is it better/more secure than the previous implementation?

this has officially piqued my interest in running a cashu mint.

You can use multiple mints in a wallet if you mean that

Can't, it's a one-way street. Hyper scaler TEE's don't die though

no u

tell us how you do that with Google cloud or Amazon nitro

eventually, that's the goal. it's doable

🥜

👀

!

🥜🥜🥜

we march on!

🤘

This is extremely exciting. A big move to help reduce blind trust in the mint. Does this setup open up the possibility for remote attestation? Fixed and auditable code in these enclaves would be huge. If the wallet can verify the code in the enclave then that reduces opportunities for malicious mint modifications.

the trust model of TEE based ecash is jeff bezos won't unplug the computer. not cypherpunk at all my man

yes wallets will be able to verify attestations

Hell yeah. That is a big deal. Less concerns about mint fuckry is definitely directionally good

The signed attestation document can include custom data and a public key, in Nitro. But the problem is what happens if the Cashu TEE restarts, where are the keys?

yes nitro signs it no an HSM cannot do the required math for cashu. even if it does, it exposes itself to the risk that it is lied to about the success/failure of payments from the outside LN node, so it must operate as a closed system. also the HSM can just be smashed an attacker can also just deny access to the mint. they could say that you can get 50% of your ecash back, but only by sending your tokens to them. the user can either do nothing (and lose it) or try (and probably get it back, but also net the attacker money). the second case is the only one that is good for the user

okay nvm this is stupid "hyperscaler TEEs don't die"

Instance retirement - Amazon Elastic Compute Cloud

Identify Amazon EC2 instances that are scheduled for retirement, and learn what actions to take to manage retirement.

I wish I was knowledgeable enough on the subject to understand how it works. Maybe some day. Congratulations tho! 🙌

That’s incredible!! Excited to see all the work.

The only way to have some sort of exit mechanism is full-fledged smart contracts (even then I don't think it is really viable), with *state* that is shared across all transactions that interact with it. And a very efficient execution so that your $30 exit does not cost $200 in fees.

Nut disrespectors just got deez nutz in their mouths

@/dev/fd0 now tell us why this is ruggable

wdym they don’t die? all hardware dies eventually

You accepting ecash?!

Sent directly to your minibits

Thank you for helping grow our privacy infrastructure and innovation in Cashu!

When the mint shuts down, who gets the sats?

from one tee to another?

Weren't you complaining about on chain zaps last week? 👀

For my own personal definition of rugging, the attacker need not receive the funds. For example, if a darknet market is shutdown by cops, all the users with funds on it are rugged. The operator of the market doesn't need to be the recipient of the funds.

I don't quite get what your suggestion was.

study history (rpow)

so you have nothing to say?

yes we're doing all that, no idea what you're rambling about

KMS

it has no unilateral exit, you're like 3 years too late

you seem to be an intelligent person, I wonder why you chose to become a reply guy. waste of your intellect.

export the keys... how / why?

u doing Bitcoin development evolution all by yourself basically 😅 keep building Calle! You are an inspiration ✌️

I have bad news for you. For one, TEEs are not that good. Two, you are walking on a thin ice when it comes to hardware attestation adoption. Don't. Unless you want to leave a world of digial slavery to your children. Hardware owner has the full right to access data processing in full. Period.

#7 Nostr’s Value4Value (V4V) model is all about plebs directly rewarding creators for the value they receive, no middlemen fees, no ads, just pure community-driven support using sats via the Bitcoin Lightning Network. Thanks to

ZAPLIFE.LOL

A decentralized Craigslist running on Nostr

by @PABLOF7z for providing this data. Here are the Top Zapped/Top Zappers from last week, showcasing the creators who received/sent the most engagement: 🔥 Top 3: Most Zapped 1. Name: @Fountain Boost Bot - Zaps Received: 307 - Sats Earned: 513k 2. Name: @calle - Zaps Received: 305 - Sats Earned: 55k 3. Name: @FLASH - Zaps Received: 255 - Sats Earned: 84k 🔥 Top 3: Most Zappers 1. Name: @AQSTR - Zaps Sent: 2733 - Sats Spent: 121k 2. Name: @FL Justin - Zaps Sent: 168 - Sats Spent: 50k 3. Name: noderunner - Zaps Sent: 144 - Sats Spent: 8k 💰 Top 3: Most Sats Received 1. Name: @Fountain Boost Bot - Sats Earned: 514k - Zaps Received: 309 2. Name: @Anix - Sats Earned: “Not mentioned correctly” - Zaps Received: 1 3. Name: @CapScabio - Sats Earned: 250k - Zaps Received: 1 💰 Top 3: Most Sats Sent 1. Name: @El Gorila 🇦🇷 - Sats Spent: 1M - Zaps Sent: 6 2. Name: @Sattrio - Sats Spent: 180k - Zaps Sent: 3 3. Name: @Keith Meola - Sats Spent: 124k - Zaps Sent: 38 Here are the Top Zapped from last week, showcasing notes that received the most engagement: 🔥 Top 3: Most Zapped 1. View quoted note → - Zaps Received: 80 - Sats Earned: 18k 2. View quoted note → - Zaps Received: 47 - Sats Earned: 8k 3. View quoted note → - Zaps Received: 46 - Sats Earned: 5k 🔥 Top 3: Most Sats 1. View quoted note → - Sats Earned: 211k - Zaps Received: 17 2. View quoted note → - Sats Earned: 130k - Zaps Received: 3 3. View quoted note → - Sats Earned: 121k - Zaps Received: 4 #most-zapped_nostr_recap