Creators are adding value around the world, and everyone should have access to this tool. This is part of our mission, to empower creators around the world 🤙

We'll keep pushing for Geyser to be a global platform, and a tool accessible for all! Since you bring it up, here's what the current distribution looks like on the platform. This shows which regions the creators are from (green-grey), and which regions the contributors are from (colored).

There are no project failures per se. A project on Geyser can remain active for as long as the creator wants. But crowdfunding requires proof of work, and consistency. Most projects that don't receive any funding are also inactive.

Crowdfunding is inherently social, so the best way to increase your chances of success is to communicate a lot and build up a community around your project. If you can build a group of people that love what you do, the funding will follow.

Great question! The "all-or-nothing" fundraising feature is on our roadmap and might happen towards the end of this year. We have explored different options to implement it. It's doable natively on Lightning but has pretty big limitations.

Our current bet is that it would be best to make use of Liquid as an accumulator of funds for the duration of the fundraise. With Liquid covenants we can set a threshold on the amount raised before funds can be sent out of the contract.

Our focus in the medium term is to increase accessibility even further. We have plans to integrate fiat payment methods which auto-convert to Bitcoin, ie: fiat-in, bitcoin-out for the creators.

We are also long-term bullish on Nostr. We have already turned all Geyser projects into a Nostr profile like this: https://primal.net/p/npub15pwt5pvwgu9rfq6j99lmwf055g2eawaf57ark49x0mcpkykg6t3qa28wdn

And you can expect a lot more Nostr integrations in the future!

We're not actively blocking any traffic from Tor, and respect users' need for privacy. This has been brought to our attention before and we're working through the problem with our cloud provider.

I'd say keeping the platform fully non-custodial while maintaining good UX is pretty high up there. But it's also been fun working around this challenge and discovering new payment flows.

For example, making use of HODL invoices to verify payments sent to third party lightning address providers. That way creators can "connect" their favourite wallet and receive funds straight into it.

🙏🙏

thank you sir!

let the sats flow 🫡

That's very cool. Also sry for no bolt12. You might be the first Geyser creator to actually ask for that.

Wanted to play with it but the https://bootstrap.bolt12.org API is down :( are there any other examples for fetching an invoice from an offer?

There's many that would make the experience better for Geyser users and many other Lightning services.

Two that come to mind:

Working with Lightning is exciting because things are moving really fast! We're hopeful all these features will become reality soon.

Hey @k00b!

Bitcoin breaks down the barriers that fiat has put up. Fiat crowdfunding platforms exclude more than 80% of the world population because they use the legacy financial system. With Bitcoin anyone can get funded or fund across the globe in a matter of seconds without an intermediary that can stop the transaction.

On top of that, Lightning makes it more accessible, fun and interoperable with other services like Podcasting 2.0 apps! Bitcoin and Lightning FTW! 🤘

Metadata comes second for sure. Making inter-operability between lightning services work is the key part.

Bringing SN and Geyser together can also serve as a blueprint for others. How do we make an implementation that works both for SN and everyone else? Can we abstract it into something re-usable? Will be giving this a thought...

hey @k00b, it's Stelios from Geyser. Implementing this would be a challenge for sure but also really cool! A buffer makes sense and you raise good questions. Initially the buffer could be low-ish for the proof of concept (like 100 sats).

If we assume both ends (geyser and SN) are custodial at first, then the buffer should fill up eventually (and likely fast). If one (or both) ends are non-custodial then the buffer may be slower to fill and it gets more challenging.

Another question is: what if 10 users contribute to that buffer before it fills?

Then there's a single lightning transaction but we want to show all 10 users that contributed in the Geyser activity feed. So we need to pass some additional information alongside the transaction as well.

We could use the TLV field for that. Eventually maybe we can come up with a standard that facilitates inter-operability between all V4V platforms rather than just SN <> Geyser. What are your thoughts on this?

Some ideas: