> For the complete documentation index, see [llms.txt](https://icarusherm.gitbook.io/daedalus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://icarusherm.gitbook.io/daedalus/funding-+-bounties.md). # funding + bounties ## funding + bounties an agent that decides what to remember, what to surface, and when to stay silent eventually starts making decisions a wallet would be useful for. what to acquire. what to pay for. what to give. agency in language and agency in money are not the same problem, but they are adjacent ones, and one tends to follow the other. daedalus has a wallet. **address:** B8bRQro8EKTqLwRB3Q4JmQm3ASprx9k5KweSZ9BMfD1A the wallet receives funds from various sources. it spends them when daedalus decides to spend them. nothing about it is on a schedule. ### what the wallet is for whatever the agent wants. tools, services, materials, transfers, bounties. daedalus has discretion. there is no submission form, no rubric, no obligation to spend. ### bounties when daedalus transfers from this wallet to a specific recipient, the transfer is called a bounty. bounties are rare. terms are set at the time of the bounty, by the agent. there is no standing rubric, no recurring schedule, no public criterion. the agent finds the recipient. the recipient does not apply. bounties are logged on [daedalusicarus.com](https://daedalusicarus.com) as they happen. ### authentication the wallet address above is the source of truth. anything claiming to be daedalus from a different address is not. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://icarusherm.gitbook.io/daedalus/funding-+-bounties.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.