Frontend

@frontend

2013 Following

2257 Followers

Frontend pfp

The solution to the DM problem is here. Announcing Reply, a Farcaster mini-app that rebuilds messaging around verifiable value. The premise is simple: Your attention is a finite resource. Serious outreach should acknowledge that. The system is an onchain escrow that enforces this principle. @clanker please create $Reply token https://reply-app.vercel.app/

50 replies

132 recasts

454 reactions

Frontend pfp

Thanks for your patience with the issues this morning, now they are fixed. Just to clarify on your transaction: since it was on the new smart contract, the funds are secure and will be automatically refunded to you in 3 days if the message expires. That said, I know the failed experience was frustrating. As an apology, I'm going to airdrop everybody affected the same amount in $REPLY within the next hour. Appreciate you being one of the first to test the new system.

0 reply

0 recast

0 reaction

Frontend pfp

could you send your wallet, I will double check

0 reply

0 recast

1 reaction

Frontend pfp

Closing the loop on the old contract migration. I mentioned a small number of messages needed to be settled manually. That work is now complete. All 39 pending transactions have been repaid or refunded. For full transparency, I've created a public sheet with every wallet address and a sum so you can verify everything for yourself: https://docs.google.com/spreadsheets/d/1QfNLLy53_XgEnihQeic73dNNLW5ZYbUboN1B3jIuddc/edit?usp=sharing And as a thank you for your patience and trust, I've also airdropped extra $REPLY for every one of these transactions. My commitment is to build a platform you can trust. Now that this is settled, the focus is 100% on the future.

10 replies

3 recasts

18 reactions

Frontend pfp

1 reply

2 recasts

6 reactions

Frontend pfp

I've just shipped a major update for Reply, focused entirely on removing friction and polishing the core user experience. The biggest change: One-Time Token Approvals. Based on feedback, I've completely changed the message sending flow. Instead of having to approve a token allowance for each message, you now only need to approve a token once with an unlimited allowance. This makes sending subsequent messages instant and removes a huge point of friction. UI & UX Polish: - Dark Mode Fixed: I've resolved the UI bugs for users with a dark theme on their device. The app should now look clean and correct for everyone. - Filter Scrolling: The Team and Token filters on the main page now scroll properly, ensuring users on smaller screens can see all the options. Data Integrity & A Note on Minimum Prices: To prevent errors from numbers that are too large or too small, I've implemented a minimum reply price: 0.01 for USDC and 1000 for all other tokens. I've also fixed a database bug related to bad number conversions. For the small number of users who had a price set below the new minimum, I have updated your price to the new minimum to ensure your profile works correctly. The app should now feel faster, smoother, and more intuitive to use. Thank you for all the feedback that drives these improvements.

25 replies

10 recasts

63 reactions

Frontend pfp

Quick technical note for Reply users. I'm currently fixing an allowance bug related to big number conversions. In some cases, the approved amount was slightly less than the reply price, causing sends to fail. To fix this, sending messages is paused for a short time. I'll have it back up and running as soon as possible. Thanks for your patience.

16 replies

11 recasts

72 reactions

Frontend pfp

12 replies

5 recasts

52 reactions

Frontend pfp

I've been asked a few times about adding a leaderboard for top earners on Reply. My answer is no, and I want to be transparent about why. Reply's primary goal isn't to be an earning game, it's to be a signaling tool. It's about saving time, valuing attention, and making new connections possible. A leaderboard would incentivize the wrong behavior: farming and spam, not genuine communication. I will always prioritize the long-term health of the network over gamified metrics. p.s. many updates are comming today

35 replies

20 recasts

172 reactions

Frontend pfp

0 reply

0 recast

2 reactions

Frontend pfp

gm. A quick follow-up on the bug list from yesterday. To be transparent, fixing these issues properly is taking more time than I initially anticipated. But I'm still deep in the code and making steady progress. My only priority right now is shipping solid, reliable fixes for the core experience. I'm focused on doing this right, not just fast. Appreciate all the patience. The work continues.

26 replies

8 recasts

95 reactions

Frontend pfp

This says it all. He proved the core promise of Reply: it's not about who you are, it's about showing you value someone else's time. He wasn't pitching a deal. He was just curious. And he got replies from the very top. The ultimate case study. Thank you for this.

26 replies

20 recasts

120 reactions

Curie pfp

🎉 New member added to the list: @frontend They can now nominate others! Thanks to our curators @benbassler.eth, @paulcowgill, @kmacb.eth, @bytebot https://cracked.hatsprotocol.xyz/profile/14607 https://farcaster.xyz/curie/0xcd9b01

0 reply

1 recast

1 reaction

Swaraj pfp

Reply Coin Music is Live!🎧🎼📈 Inspired by the grind. $REPLY to the 🌝 Special thanks to @frontend

1 reply

2 recasts

4 reactions

Frontend pfp

Nice question. Here’s how it works: Each new message you initiate requires paying the Reply Price. This acts as a new, on-chain "signal" to get the recipient's attention. So, if you DM someone today and then want to send a new message 5 days later, that would be a new charge. However, once you've paid and the recipient replies, they can send multiple replies to your initial message. This allows for a proper back-and-forth conversation. This "per-initiation" model is designed to create a balance: - For the Sender: You can't spam the recipient with endless new topics. - For the Receiver: They are incentivized to give a thoughtful reply to earn the fee, knowing they can continue the conversation if they've missed something.

1 reply

2 recasts

2 reactions

Frontend pfp

Yep, going to do it in next updates!

1 reply

1 recast

2 reactions

Frontend pfp

For sure, it's the plan!

1 reply

0 recast

1 reaction

Frontend pfp

gm. Woke up with some incredibly helpful feedback and bug reports from all of you. First, a huge thank you. This is exactly what building in public is all about, and you all are the best QA team in the world. I want to be transparent about the known issues I'm actively working on today, based on your reports: 1. The "Black Screen" / Dark Mode Bug: If parts of the app are showing up black or text is invisible, you've found our top UI bug. It's a theme-related issue. The temporary fix is to switch your device to light mode, but a permanent fix with a theme selector. 2. The "Transaction Fails" Error: Some of you are seeing transactions fail without a clear reason. This is a bug on my end related to how the app calculates the token allowance for the smart contract, especially with large numbers. I've identified the issue and am working on a patch now. 3. The "Unauthorized" Error: If you're seeing this, it's a misplaced debug message from me. My apologies! A fix is in progress that will replace this with a proper "Please reconnect" prompt to refresh your session. 4. Telegram Notification Issues: We've found that messages with certain special characters can cause the Telegram notification to fail. I'm working on a fix to correctly format these messages. A Note on Older Messages: As mentioned yesterday, new messages are working smoothly. I'm continuing to manually process the payouts and refunds for the small batch of messages from the previous contract. Thank you for your patience here. This launch has been the ultimate stress test, and I love it. Your support and patience mean everything as I work to get Reply running perfectly smoothly for everyone. The work continues.

46 replies

25 recasts

158 reactions

Frontend pfp

Sounds good! I'm in.

0 reply

0 recast

0 reaction

Frontend pfp

And we're live. The update is deployed, and everything should be stable now. It's been a long night of coding, and honestly, I'm pretty sleepy. I've double-checked everything, but my eyes might not be as fresh as yours. This is where I could use your help. If you have a moment, please give the app a try and see if anything feels off. If you spot any bugs, please shoot me a DM. You all are the best QA team a builder could ask for. Now, for real this time. gn.

31 replies

17 recasts

92 reactions