> For the complete documentation index, see [llms.txt](https://docs.humandataincome.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.humandataincome.com/datamask/for-developers/ipdw-interplanetary-data-wallet/manifesto.md). # Manifesto ### Introduction The IPDW Manifesto dives into the foundational concepts of Web 3.0, highlighting the role of public and private keys in ensuring secure, decentralized identities. It discusses the evolution of user experience in managing private keys, and how the IPDW leverages these advancements to create a sophisticated, offline data storage mechanism that only exposes data during transactions. The manifesto also outlines the significance of P2P communication strategies like IPFS and IPNS in ensuring data is securely synced across devices without compromising privacy. ### Manifesto Everyone has a key pair, which means that there is a public key and a private key that can be saved in different formats (see the BIP39 standard for mnemonic phrases based on deterministic key generation). In Web 3.0 applications can recognise your wallet address (derived from the public key) to let you act on the distributed ledger (the storage) as a well-identified identity. The blockchains have different replicated and redundant ledgers and different consensus algorithms. There is a competition rush to find the best algorithm to achieve it, increase throughput, security and so on... Let remove the term "blockchain" from the equation, Web 3.0 users are familiar with Private Key usage and management because of applications like Metamask/Trust. These ones simplified the user experience a lot, and right now, managing keys and signing a message using ECDSA is an easy game. Thanks to these applications now users are able to do things that in past were done only by expert users like using GPG messaging systems. Remember "adoption" is the key for the evolution. Poor UX/UI means poor adoption. Why we are talking about these in-famous private keys and public keys? As we know today nothing except a super quantum computer (reliable in matter of years since the time I'm writing this) can defeat/brute force this wonderful thing. They are only vulnerable to social/phishing and similar attacks. One rule to remember: "Humans every time are the vulnerable elements in the chain". Using this assertion we can recreate a lot of computer science related things, now that users are familiar with using them. Surely you have a physical wallet in your bag or pocket, it is offline and only during a transaction it is eye-visible to the other peer. Now let's introduce the **InterPlanetary Data Wallet** as a sophisticated mechanism to store all kind of data, that can works offline and only during a a transaction it can be partially exposed. No worries, it is offline but it can be synced between all your devices using some P2P communication strategies like IPFS and IPNS. Yes, it is encrypted, so it is safe to share it without knowing the passphrase. {% hint style="info" %} ### ***IF YOU LIKED THIS MANIFESTO, PLEASE SHARE THE LINK AND HELP DEFEAT INTERNET DATA CENTRALIZATION!*** {% endhint %} --- # 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://docs.humandataincome.com/datamask/for-developers/ipdw-interplanetary-data-wallet/manifesto.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.