Avatar
Nick Slaney
38609f8bb73a240a557511257c8917120a160657d9cb54d499315c1ff8ab8f0c
MOE maxi

With replit + moneydevkit the agent can now take you entirely from 0 to website with prod global payments in minutes. No signup, no onboarding. Just say “add moneydevkit”

https://v.nostr.build/7y7cQY9CRun5IS86.mp4

Nostr: a p2p hellthread network

Feel free to jump in the discord and I can help you diagnose!

No_route is typically something with the webhook setup, two things to check:

1. Is your site name correct on the dashboard? Go to Webhooks and make sure it matches the url it’s hosted at.

2. Is the code snippet at api/mdk/route.js correct? Agents are pretty good at this part, but good to double check. Just copy / paste what’s in the readme.

We use Webhooks to ping your node when a payment is coming in. If we can’t reach your site then the payment will fail no_route.

Looked like your agent was trying local with ngrok? That can work but you’ll need to adjust the webhook url to your exact ngrok url. We’re working on a more friendly local experience (on mutinynet) and will have that out soon.

The node spinning up / shutting down is normal and expected. It’s how we’re able to support NextJS and serverless infra like netlify and vercel!

Happy to take a look, Claude is going deep :)

This is a cool concept, we started with the prepackaged checkout to start but there’s no reason this shouldn’t work.. we are planning on exposing the lower level stuff that can make something like this easy soon.

Replying to Avatar Nick Slaney

Hi nostr

Today we’re launching our public beta at moneydevkit.com

It’s the fastest, easiest way for anyone to take payments online.

So fast actually, I set the world record from deployed website to production payment (4:38.94). https://v.nostr.build/VaPmy43L3K7i1E1v.mov

Try it for yourself:

npx @moneydevkit/create

npm i @moneydevkit/nextjs

Under the hood, we’re using self custody lightning (can I say that here? 😆), but you don’t need to worry about any of that. Just install the library, paste a few code snippets (or have your agent do it like I did), and take payments.

https://moneydevkit.com

Feel free to ping us on discord at https://discord.gg/Ebb26MrJpT

Hi nostr

Today we’re launching our public beta at moneydevkit.com

It’s the fastest, easiest way for anyone to take payments online.

So fast actually, I set the world record from deployed website to production payment (4:38.94). https://v.nostr.build/VaPmy43L3K7i1E1v.mov

Try it for yourself:

npx @moneydevkit/create

npm i @moneydevkit/nextjs

Under the hood, we’re using self custody lightning (can I say that here? 😆), but you don’t need to worry about any of that. Just install the library, paste a few code snippets (or have your agent do it like I did), and take payments.

hi nostr

We’re testing moneydevkit on mutinynet. If you want to give it a try dm me

Really struck by people asking us about stablecoins.

It’s clear no one has actually tried to use these things.

The stablecoin ecosystem was already fragmented across two coins and n+1 chains, now with everyone issuing their own stablecoin, the whole thing is a disaster.

Any broadly compatible UX has you choosing which coin, which chain, “ONLY DEPOSIT USDC ON SOLANA”

It’s clear that banks / VCs think stablecoins are it, but for normal people doing normal things, the UX is absolutely abysmal.

It is web3 all over again. It’s the third time I’ve seen the crypto playbook in action and it still falls flat.

- big partnerships

- lots of money

- all marketing, no substance

“But Nick the stablecoin UX will be simple, you will just have a bank account and dollars, everything else will be in the background”

That’s great for people with these theoretical bank accounts, but ultimately what you’re talking about is slightly upgraded tradfi, not access and tam increasing internet money.

What we see with moneydevkit is many, many more people being able to generate value online, and the same barriers to entry to accepting value online. Stablecoins are not on a path to fix this meaningfully. They’re on a path to create a new visa, which is ultimately uninteresting and cannabalistic as opposed to generative. We are going much bigger.

Have been thinking about the maple syrup op recently. I realized this year I have many more trees than I thought. I can get much more sap than I can boil at this point.

More sap —> bigger evaporator —> sugar shack

When you have abundance in one area you have to scale to make the finished product. It’s a bit of a jump but worth it to be able to give syrup to more friends. Just have to take the leap sometimes :)

Yeah I just think a bit of give on the core side would go a long way. Mike Schmidt started doing this by putting up a pr to un-deprecate datacarriersize and it’s a good start.

The issue is these guys had good reasons to get people riled up. Could have been defused quickly if there was a consistent, logical argument coming out for changes but there wasn’t for a while. Instead we got gaslighting, “paternalistic censorship” and actively antagonizing comments.

It was a shift in thinking, communicated poorly, and the worst part was otherwise smart respected people dipping to unnecessary lows due to open source bad blood.

The outcome is instead of having a somewhat hard conversation about the reasons for core wanting to nuke mempool policy, we’re now having the conversation about whether people are going to run core at all. Much worse.

The solution isn’t more Luke bashing its core building trust with people again. Arguably the easier thing, the hard part is eating a bit of humble pie.

Lola I like your work and I’ve donated to the rage many times. If you’re feeling defensive about the signal message thing, 🤷🏻‍♂️. You’re not usually the one I’m thinking about I write this.

I’m more concerned with the general tack of “Luke is bad” because it’s pretty well known and sort of ignores what people are actually upset with.

Does Luke suck to work with? Clearly

Is he out over his skis on the csam stuff? Yeah I think so

Is Luke the reason people are running knots? Not really. People are mad at core, and core can fix this with one simple trick.

Literally just bring back datacarriersize and let people do the thing that everyone says does not matter.