Nader Dabit: Yeah, totally. People can lose all of their money, and there’s nothing that anyone can do about it. That’s a huge risk for anyone transacting today with most of these decentralized Web3 wallets. You can use something like Coinbase, or another centralized wallet, that is a little bit more – it’s not more secure, it’s actually less secure, but you have a little bit more centralization and maybe protection around those sorts of things.

If you’re the average user, that doesn’t really maybe understand how some of these wallets work, and you accidentally lose your private key, for example, and you delete your wallet, there’s no way to get your money back. If you give someone else your private key, either in a screenshot or however else - maybe they hack your computer - you can lose all of your money. And I think that that is a major concern for people that either don’t know that that’s the case, or don’t know how to mitigate that type of stuff. Even for experienced people that have been in this space for years, you hear people that have made mistakes, and people have been able to get their private keys and they lose their money, for example…

[01:00:18.10] A really popular social engineering hack is someone messaging me on Discord, and trying to somehow get you to screen-share, and then they ask you to open your wallet, and then they kind of like screenshot something there.

So yeah, that’s a big concern… And I think one of the ways that people are going around mitigating that is that we’re building and innovating in the user experience of how to manage that, and having some form of backup, usually through some type of multi-signature wallet, meaning that can give access to a handful of other people, and if they all get together, they can kind of unlock something… Or maybe you have like a social mechanism where you have your mom, or your cousin, or your wife, or something, and all of you can get together to unlock it.

Jerod Santo: Then you leave your wallet on a – you’re filling up gas, and you leave your wallet sitting there, and you drive away to the gas station… Not speaking from personal experience or anything.

Tom Occhino: [00:56:08.15] [laughs] So do you know the expression “In life there are no such things as solutions, we only have the ability to trade off one set of problems for a different set of problems.” I think there are no solutions, only trade-offs. And I have to find attribution for the quote.

What we’ve done is we’ve traded denial of service, which is “Oh, a lot of people visited my host and it went down.” We’ve traded that for something that we affectionately call denial of wallet, which is like “Hey, we’re not going to go down, but we’re going to provision a lot of compute, and that compute costs money.”

So here’s how we’re thinking about solving the denial of wallet problem. The first thing is, we have to have spend controls. If you’re building your profile or portfolio website, there’s no world where you’re willing to spend more than 20 bucks a month to host this thing. It’s like, look, it’s not a business. So spend management and the controls to get it right. And we have some of those things, but I actually don’t want that at all. I want our platform to be so smart that we know the difference and that we alert you when something is happening, such that every time you have that, not only are your costs under control, because we’ve reduced the underlying costs of running and provisioning that compute - which we’re working on with things like in-function concurrency we could get into - but you don’t have to think about it also because you know what happens when that happens, in advance. You’re going to get an alert. You’re going to be able to have control, you’re going to be able to say “I want to use the firewall to be able to rate-limit, or block, or slow traffic.” But in the fullness of time, we make this zero configuration and we just take care of it for you.

And so our platform is getting smarter and smarter to be able to not have the denial of wallet problem. We actually have an active initiative around preventing denial of wallet. So yeah, the sort of like serverless, the original serverless pitfall, which is like “Wow, this thing is working too well.”

Jerod Santo: You’ve got a wallet?

Jerod Santo: Which is who they’re selling it to, right? They want to tap into your nostalgia, and now you have kids or whatever, you have more money than you did before, and you’re going to take everybody to the theater. And they need to at least satisfy the person with the wallet.

Adam Stacoviak: I guess what I meant paying attention to it closely is not like “Man, let me check my watch. Let me check my dashboard this very moment”, but more like just paying attention to it. I think there’s a lot of people who almost live in bliss. Ignorance is bliss. They realize things cost more, they realize things are not the way they were two years ago, they realize money is less free, meaning not only is it worth less, but it also costs more to get it. Interests, right? And these are the levers that the Fed is using, specifically here to the US, and I think it’s probably similar in other markets across the world in how it works… Is that money is less free, you can’t get it as easily, you can’t borrow money as easily, and things cost more. I think that there’s a lot of people out there who are not paying attention to that directly. They’re paying attention to it indirectly by saying “I’ve got less amount in my wallet, I’m not making or I’m making more, or the same, or whatever, but somehow I have less.” They’re paying attention to it in the symptom, not the actual problem. I think a lot of people are like that. And so you mentioned fear, like what do you fear. Specifically, what do you fear then? Go into it more.

Nick Nisi: No wallet.

Chris Benson: You mean I get my wallet back at some point? [laughter]

Jordan Harband: Yeah. I mean, before I get to your question, I think when somebody sponsors me, or they ask “Hey, can I sponsor you?” I’m always appreciative. I say “Yes, of course. Thank you. It really means a lot.” It’s validation for me. Even if it’s $1, it’s still that somebody cares enough to vote with their wallet.

Adam Stacoviak: Yeah. No media is safe unless you have a physical copy. It’s like – I don’t know if you’re into Bitcoin at all, but the “Not your keys, not your wallet” kind of situation. Like, “Hey, not your media, not your –” Like, just because you own the discs too, you still have a license to use the disk. You don’t actually own it. But you can; you know, you have way more freedom than streamed, because you can find a way to change where it’s stored at. I don’t think ripping is against the law. Sharing - I’m not sharing my content with you. I’m not torrenting my media library. That’s not at all why I do any of that stuff. It’s really for convenience for me and my family.

[44:01] The experience of swapping out discs is like caveman, right? It’s like trying to create fire with sticks. Why would you do that? Like, if you have homelab sophistication or curiosities, why would you not find a way to run Plex? Why would you not find a way to have a small NAS, and run ZFS? Of course, not Btrfs or anything else, because nothing else exists besides open ZFS. I don’t know about you, Tim, but that’s how I feel… I’m just kidding. I’m not a hater. I do prefer, but I’m not a hater.

Anna Pobletts: Adam, you were talking about your mobile military ID, or something like that, that you use at Home Depot… This reminded me of a really cool thing that is kind of post passkeys. It’s probably a while out still, but I think it’s the future, and it’s a really cool thing to think about, called verifiable credentials. And it’s basically verified mobile IDs, and things that. And so letting you store your verified military ID in your wallet, in your iPhone wallet, or in your 1Password, and using that to verify over the internet, without you having to scan your phone all the time. And it’s very much similar to a passkey type of protocol. It’s sort of like the next evolution of that, and something that’s kind of coming after passkeys, and I think it’s cool how there’s just so much exciting identity-based new technology coming out in the next few years, I think. It’s just a lot of cool stuff to make your life easier on the internet. And the fact that you brought that up just kind of reminded me of that.

Jerod Santo: Because it’s in there, it’s part of the settings; it’s super-weird… When I have to show my parents that “Yeah, you can just get your passwords out there”, like how? I’m like “Well, I just swipe down and search for passwords.” And it’s had different names throughout the years, throughout the versions, and so it’s really just an unknown feature for so many people… If they had an actual app, just like they have a wallet app - have an app called Passwords, with all this stuff centralized - I think that would go a long way for people realizing how good their password offerings are. Because they have – I mean, you can do one-time password, you can do all kinds of stuff inside there… But people just don’t know about it, so… They should do that.

Jerod Santo: To a certain extent, that’s being built through the dependency graph… So you have the distribution. Of course, there’s different kinds of open source, but let’s just talk about libraries, where I write a library, and maybe it’s really fast JSON parsing, and everybody starts using it… Now I’m in their dependency graph, and now when these companies come to GitHub Sponsors and they say, “We’ve got 300k for the year. Here’s the invoice.” It goes into my – I’m sure I get a wallet, or something, and I’ve got a stash of fake money there that represents the money that I put there… And now I can divvy that out. And you’re showing them “Okay, you’re using this project. That project using superfast JSON library by Jerod. He’s available on GitHub Sponsors”, and so trickle down in that way, right? That’s what you’re trying to build. Or do you guys – is that there today? Can you do that today?

Angelica Hill: I only have two quick thoughts. One was making sure that all dietary requirements are met by the establishments we’re partnering with. Secondarily was a call for the environment, that we not have physical plastic cards, and we make them virtual and perhaps an Apple wallet or an Android wallet… I don’t have an Android device, but an Android device-based card thing…

Matthew Boyle: [06:04] Yeah, I think just to go back to a comment Mat made, firstly it’s about - like, obviously, you’re going to build software to model your problem space. What else are you going to do? And I think that’s such a fair comment, because it seems obvious, but I think one thing that domain-driven design gives you is it gives you sort of principles, ideas, and a framework to work through to help you figure that out.

So I think there’s so many key language and sort of ideas that domain-driven design sort of gives us, that helps us to think about what is the domain and what is the problem space. A couple of examples that I use in the book is - I think I build like a coffee shop system, right? And you may have a domain around ordering; like, ordering could be an entire domain in itself, because it’s like a vertical slice of the business, that has all its own rules, it has its own language, it has its own sort of ideas and thoughts… And so to slice that off into a domain makes a bunch of sense.

And then you may have subdomains off of ordering, like maybe order fulfillment is a subdomain of ordering, and that’s something that you want to kind of model separately, but use some of the same concepts you have in ordering. So that’d be one example.

I think another example I use in the book is like a wallet. You have the sort of domain of a wallet, and within that wallet you might have various different debit, credit, and - less relevant these days, but maybe cryptocurrency would be in your wallet, too… And modeling all those things separately makes sense, but they all kind of belong to this higher order idea of a wallet.

Jack Dorsey: So if you’re ever in a state where you can fund open source developers, not just around Bitcoin, but anything, you might get something back that’s extremely valuable to your company. It would have taken Cash App so much longer if LDK did not exist. And again, they weren’t building that for Square’s interest, they were building it for wallet developers that were not Cash App. Because Cash App had no interest at that time of using Lightning. I’m really proud of that. It just happened, and we didn’t force it to happen. It just happened.

Jack Dorsey: [39:47] So if you're ever in a state where you can fund open source developers, not just around Bitcoin, but anything, you might get something back that's extremely valuable to your company. It would have taken Cash App so much longer if LDK did not exist. And again, they weren't building that for Square's interest, they were building it for wallet developers that were not Cash App. Because Cash App had no interest at that time of using Lightning. I'm really proud of that. It just happened, and we didn't force it to happen. It just happened.

Jerod Santo: Enter your Bitcoin wallet address here for policy help…

Joe Percoco: Other things less so. So right now - and obviously, I think it’s a bit of a stage-dependent answer. Right now, we need to learn very fast, a variety of different things. Hypotheses that we have high conviction on, but nevertheless, we need to get data. So speed really matters. Maybe at a different stage in our journey, as we shift to, “Okay, we’ve gotten a ton of scale”, now we need to convince everyone that has joined our service to give us a high percentage wallet share. From there, we need to focus on high quality, not necessarily high speed.

So the question that applies to a business like ours, at least right now - I’m speed-first, and I think a bunch of the entrepreneurs I respect I think would also shake out speed-first. But the interesting is, does it change as you scale? That’s something that could pose a lot of really interesting debate.

Nicholas Mohnacky: So that’s what I mean by vectorizing and bundling your IQ and your knowledge; and potentially – like, you’re a walking, talking digital wallet of Chris’ intellectual property that you could contribute somewhere else, or just get paid on for everything that you’ve already contributed.

Gerhard Lazu: So we had two DNS tokens, one was for the old setup and one was for the new setup. The one for the old setup I have deleted, because we just didn’t need it… And then we had three DNS tokens left. One of them disappeared. It’s no longer there. And that was the one that was used by cert-manager to renew certificates. So the certificates are now failing to renew. We passed the 30-day threshold, and we have I think another 25 days to renew the certificate. But because the token is not there, the certificate will never be renewed, and then eventually, the certificate will stop being valid. This is the same wallet we use in Fastly. So a lot of stuff is going to break for many people.

Now, I’ve found out about this by just looking through K9s what is happening with the different jobs. There’s jobs which are failing, that are meant to renew things. It’s not the best setup, so the first thing which I’ve done, I’ve set up an alert in Grafana Cloud, when the DNS expires in less than two weeks, or in actually three weeks - whatever; some number of seconds, because that’s how they count them - I get an alert. So it should automatically renew within 30 days. If within 25 days it hasn’t been renewed, I get an alert. So I have 25 days to fix it, roughly.

So what I would like to do is first of all capture this problem in a way that we can refer back to it, and also fix it in a way that we also can refer back to it, like how did we fix it; what went into it, what was added, so that this doesn’t happen again. And adding that alert was one of the actions that I took even before we created an incident. So that’s one of the top things on my list. How does that sound to you both?

Gerhard Lazu: So we had two DNS tokens, one was for the old setup and one was for the new setup. The one for the old setup I have deleted, because we just didn’t need it… And then we had three DNS tokens left. One of them disappeared. It’s no longer there. And that was the one that was used by cert-manager to renew certificates. So the certificates are now failing to renew. We passed the 30-day threshold, and we have I think another 25 days to renew the certificate. But because the token is not there, the certificate will never be renewed, and then eventually, the certificate will stop being valid. This is the same wallet we use in Fastly. So a lot of stuff is going to break for many people.

Now, I’ve found out about this by just looking through K9s what is happening with the different jobs. There’s jobs which are failing, that are meant to renew things. It’s not the best setup, so the first thing which I’ve done, I’ve set up an alert in Grafana Cloud, when the DNS expires in less than two weeks, or in actually three weeks - whatever; some number of seconds, because that’s how they count them - I get an alert. So it should automatically renew within 30 days. If within 25 days it hasn’t been renewed, I get an alert. So I have 25 days to fix it, roughly.

So what I would like to do is first of all capture this problem in a way that we can refer back to it, and also fix it in a way that we also can refer back to it, like how did we fix it; what went into it, what was added, so that this doesn’t happen again. And adding that alert was one of the actions that I took even before we created an incident. So that’s one of the top things on my list. How does that sound to you both?

Patrick Ecker: [48:07] Yeah, yeah, sure. And companies like TinyMCE - they are building a rich-text editor platform with ReScript, and for that it’s also fantastic. These really complex domains - this is where ReScript shines.

On the team, we’ve got, as I said, Hongbo Zhang, who is now also working for Facebook, Cristiano Calcagno, who is one of the cleverest scientists I know. He has been working on the Infer project, if you know that, for code analysis and static analysis of all kinds of languages. He has huge knowledge about analyzing code, which is great for us, because we have a lot of dead code elimination analysis going on right now for ReScript, because it’s fully typed. Super-nice to analyze.

We’ve got Cheng Lou, who has a huge vision on products, and designs, and lean, clean interfaces. I love that as well. Maxim Valcke, who is our master brain on the syntax level. He has been investing so much time into writing a syntax parser that is efficient and small. It’s super-fantastic work. And myself, of course, for working on the documentation; I’ve been doing this within the ReScript Association, as you already mentioned. The ReScript Association was founded with the goal to support the community and support a language with financial infrastructure, so people can send donations to it who are relying on the technology. So if you are a company who wants the language to succeed, the best way to invest money is to invest it in the association. They’re reallocating the money for developing the documentation, growing the editor tooling, working on core essential libraries, finding other projects, organizing conferences… We had like two conferences already - ReasonConf 2018 and 2019, and also a Reason conference in the U.S, which will most likely of course be rebranded to ReScriptConf.

So in the past 2,5 years we also collaborated with research institutes and companies, we collaborated with Ahrefs, which I already mentioned, with the Tezos cryptocurrency - they’re also really invested in this, because they want their crypto wallet apps to be stable, and they chose ReScript for their web frontends, and stuff like that. Or subsidiaries of Tezos, of course. Tezos is a huge project.

So this is how we try to set a foundation for the language on the community side, on the open source side, but also we have a strong commitment on the business side with the core team, who is working at Facebook, and all other companies that depend on it.

Mikeal Rogers: [laughs] And all the money goes into your wallet, and I do all the work… Is that it? [laughs]

Jerod Santo: Yeah, there’s lots of challenges there. I like the idea of really the user’s phone, their network plan, all these things as user concerns that people – I think they are waking up to them more and more, because they are more tangible costs than privacy costs. Trading my privacy is very hard to intellectualize exactly what am I doing here, but especially if I’m on a capped connection, or I’m paying per megabyte, or my battery is dying in the middle of the day, and I’m seeing actually using this application is causing me really hard costs, right there in my wallet - I think people are starting to make decisions around that.

[28:09] We see it happening with the phone operating systems starting to percolate up to the user “What is draining my battery right now?” “Well, it’s this application.” “Oh, you know what - I’m sick of that application. I’m not gonna use it anymore.”

So I think the caring for your user, part of that is for their resources on their devices. And the more you can do on the server, especially when you’re talking about heavy computation, there more you’re actually caring about them in that way… So good point.

Amal Hussein: Exactly. [laughter] Open your wallet, LOL… Funny.

Quincy Larson: It’s hard to get people to pull out their wallet.

Jerod Santo: Do you know what I do know how to do? Get the credit card out of my wallet and swipe it through a thing, so I’ll just keep doing what I know.