I built a Bitcoin network signal using physical hardware instead of APIs — here’s why

Hey Indie Hackers 👋

I’ve been building a small SaaS called BlockPulse, focused on one very narrow problem:

“When is it a good moment to broadcast a Bitcoin transaction?”

Most tools rely on:

• public APIs

• mempool charts

• fee estimators

They’re powerful — but they assume users already know how to interpret raw data.

What I noticed

Talking with casual Bitcoin users, the hardest part isn’t choosing a fee.
It’s answering a simpler question first:

“Is this a normal moment on the network, or is something unusual happening?”

That uncertainty alone causes people to:

• overpay fees

• hesitate

• postpone transactions “just in case”

What I tried differently

Instead of another dashboard, I built:

• a physical ESP32 module

• measuring real-time network conditions independently

• producing a simple contextual signal, not charts

No API dependency.
No prediction.
Just: is the network calm, normal, or stressed right now?

Current state

• Working SaaS (React-based)

• 7-day free trial

• Early traction via Reddit discussions (BitcoinBeginners)

• Still validating willingness to pay

My questions for you

• Have you ever replaced complex data with a simpler signal in your product?

• How do you validate monetization when your value is reducing cognitive load rather than adding features?

• Would you start with retail users… or pivot earlier to B2B?

Happy to share lessons (and mistakes) so far.
Thanks for reading 🙏