> For the complete documentation index, see [llms.txt](https://guide.geyser.fund/geyser-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.geyser.fund/geyser-docs/your-project-guides/success-stories/proof-of-work-book.md). # Proof of Work Book ## Proof of Work by Paco de la India **Proof of Work** is the upcoming book by Paco de la India, documenting his journey across 42 countries using only Bitcoin. After years of living the message of Bitcoin adoption in the real world, Paco launched an ambitious All-or-Nothing campaign on Geyser to fund the final push of the book. The project was already deep into production, with editing completed and the next phase focused on design, print, and distribution. The campaign succeeded because it combined a powerful proof-of-work story, a clear funding need, consistent creator-led content, direct outreach, and close collaboration with the Geyser team. This was more than a book campaign. It was a rallying point for Bitcoiners who had followed Paco’s journey and wanted to help bring his story to life. ### What Made the Project Successful * **Strong Geyser partnership plan**\ Paco worked closely with the Geyser team through weekly coaching calls, content calls, motivation, campaign support, and rapidfire content creation. This gave the campaign structure, accountability, and a consistent rhythm. * **A powerful proof-of-work story**\ Paco was not fundraising around an abstract idea. He had already traveled through 42 countries using Bitcoin, proving the concept through lived experience. This gave the campaign credibility and emotional weight. * **Clear All-or-Nothing momentum**\ The All-or-Nothing model created urgency and focus. Every contribution moved the campaign closer to a visible goal, helping supporters understand that their sats directly mattered. * **Real fundraising need**\ The goal was ambitious, but it was grounded in the real costs of completing the book, including design, print, and distribution. This made the ask feel serious, specific, and worth supporting. * **Consistent article posts and campaign updates**\ Paco kept the campaign active with continued contributions, progress updates, article posts, and public communication. This helped contributors stay engaged and reassured that the project was moving forward. * **Daily creator-led content**\ Paco created his own content every day, with a strong focus on video updates. His consistent presence made the campaign feel personal, human, and alive. * **Direct outreach to the Bitcoin network**\ Paco personally reached out to Bitcoiners in his network, which led to social media boosts, new contributions, and increased visibility across the community. * **Positive and collaborative attitude**\ Paco brought energy, friendliness, and openness to feedback throughout the campaign. His attitude made it easy for the Geyser team and the wider community to support him, improve the campaign, and keep momentum high. ### Features Used * **🎯 All-or-Nothing Campaign**\ Created urgency, focus, and a clear deadline-driven funding target. * **🗞️ Project Posts**\ Kept supporters updated with progress, articles, reflections, and campaign milestones. * **🎥 Video Updates**\ Helped Paco communicate directly with his audience and build trust through frequent, personal storytelling. * **🤝 Geyser Partnership Support**\ Weekly coaching, content strategy, motivation, and rapid-response campaign support helped keep the campaign moving. * **📣 Social Sharing**\ Direct outreach and community amplification helped expand the campaign beyond Paco’s immediate audience. * **📚 Product Pre-Orders**\ The campaign gave supporters a clear way to back the book directly, turning contributions into participation in the final stage of the project. ### Impact Snapshot * Supported the final production push for Proof of Work * Helped bring Paco’s 42-country Bitcoin journey closer to print * Activated Paco’s personal Bitcoin network through direct outreach * Built campaign momentum through daily creator-led content * Maintained supporter engagement through posts, articles, and video updates * Strengthened the collaboration model between Geyser and creators through hands-on coaching and campaign support ### Featured Links & Media * ⚡ Geyser Project: [https://geyser.fund/project/proofofwork](https://geyser.fund/project/proofofwork?hero=geyserpromotion) * 🌍 Paco de la India Socials: ### Creator Tip 💡 > “Show up every day. Your campaign is not just a funding page - it is a live story. The more consistently you share the journey, ask for support, and bring people into the mission, the more your community has a reason to believe and contribute.” --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://guide.geyser.fund/geyser-docs/your-project-guides/success-stories/proof-of-work-book.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.