Thanks Shawn!

We'll get you in soon! Just making some final touches on our APIs.

Yeah, our socials have switched over to OpenSecret. When the wallet officially shuts down at the end of the year, won't be using Mutiny anywhere anymore.

Awesome, glad to hear! And yeah I myself am a heavy users of apps that could be self hosted but have a cloud offering that still uses E2EE (like obsidian) so I don't have to trust their cloud as much.

That's kinda what excites me the most about some of this confidential compute stuff. If you could verify that the cloud is running the code you expect, and can't be tampered (or even memory inspected) then it really redefines the relationship we have with the cloud. Instead of being held hostage or dependent upon it, it makes the cloud work for us. Kinda what the whole internet should have been.

Llama 3.1 70B, just text right now. We might be able to expand to images and other models next year.

Always beating me to it lol.

Here's the new stuff we've been working on from the Mutiny team.

Talk to the businesses you are targeting with the idea. Ask about what their problems are in the area you're looking to solve. Present a potential solution midway through. Ask if you solve their problem and if they’re willing to pay for it. If enough people say yes, get letters of intent and start building it/raising funding for it. If not enough say yes then keep iterating on the customer problems until you find something enough people say yes about.

Do not build a single thing until then (unless you need to do a week or two of R&D to prove out difficult tech you're unsure about). The “if you build it they will come” approach to a B2B startup is mostly a lie. If you’re even moderately close to building something in that much demand, then you’ll have no problem doing the talking.

If you can’t talk then don’t build a B2B startup. If you can’t talk then say goodbye to being able to raise funds for your startup too.

Easier said than done. I’m learning the hard way.

You're a good dude man, appreciate your thoughts and your words. The saddest part is this:

All the issues you laid out are indeed issues, but ones that can be worked passed. But changing consumer behavior (even amongst bitcoiners - ie, spending bitcoin) isn't a solvable problem a small startup can tackle within the small timeline they have to work with. Even thinking and talking about new problems that align with us but are more broader than just Bitcoin is challenging and against the status quo.

Your redesigns, pivots, and refocuses have been admirable and no matter what you're doing (with bitcoin or otherwise), hope you get much success, you're on a great life track.

Might be able to help with at least the client side key management part. Expecting users to manage, sync, and secure private keys for normal applications (let alone wallets) may be a big limiting factor. Even if you still want to roll your own, would love to chat as you start thinking about it more.

How are you thinking of doing it? We're exploring combining e2ee / private key management stuff with secure enclaves to add verifiably private and secure use cases to existing applications via JWT / normal user login / oauth.

Could be a cool proof of concept here if you're open to that approach.

Out of everything said so far, this comment puts a lot of things into perspective. Thank you for sharing it.

Go fuck yourself. You don't get to sit there talking shit constantly for years and then all of a sudden say "no offense, much respect" when a "competing" (I use that term very lightly) wallet of yours goes down.

Wow, can't believe we covered all of that lol. Was a fun night, flew by so quickly!

I call this 'splintered payments' but it is currently not possible: https://lightningprivacy.com/en/routing-analysis

You can send multiple MPPs down the same/similar paths but you can't make them split and/or come back together at any point.

A lot of your assumptions here are actually incorrect and you should spend more time researching PWAs before spreading FUD. I'm not going to waste my time disputing all these. Enjoy.

Meh it looks like a logo for a high school basketball team.

Ah, I assumed there was no budget based on the 200k amount and how you said it was drained. Glad the budget worked.

This is one reason budgets on NWC should absolutely be put in place, especially on experimental services, which arguably they all are.

How do you know liquid isn't actually being ran by just one person?

There is a difference between liquid members and liquid functionary members. It's intentionally confusing. The public list is are just partners allowed to peg out.

The people running the network are nowhere on there to be seen and they're the "guardians" in liquid's case.