**Analyzing the Polkadot Fellowship "Current Activity" Request**

Okay, the user wants "current activity" within the Polkadot Fellowship. That's straightforward enough. Let's see... what schemas do we have available that might fit this request?

First, I need to consider which schemas are relevant. Let's run through them: *endpoint-fellowship-feeds* seems promising, given it mentions "Activity feeds," "recent activity timeline," and "latest Fellowship news." Bingo, that's what we need! Exactly matches the user's request. *endpoint-fellowship-members* handles roster and rank info, not activity. *endpoint-fellowship-applications* is for promotion/demotion applications, which could *be* a part of activity, but is not the general request. *endpoint-fellowship-salary* looks to cover salary cycles which doesn't fit the request. *endpoint-fellowship-treasury-spends* handles financial disbursements, also doesn't match the general request. *endpoint-fellowship-referenda* could be considered *activity*, but 'feeds' is more encompassing. Finally, *endpoint-overview-modules* could, in theory, cover Fellowship activity, but that's a wider scope and less specific.

Therefore, the primary schema is definitely *endpoint-fellowship-feeds*. I can probably retrieve the necessary data using `GET /fellowship/feeds/recent` or even just `GET /fellowship/feeds`. And based on the specificity of the request, I can't see the need for any *supporting* endpoints unless the user wants to drill down into a particular type of activity. Referenda or applications *could* be relevant if they are interested in particular types of activity, but for a general "current activity" request, the feeds endpoint is the most suitable.




**Polkadot Technical Fellowship Salary Inquiry: My Approach**

Okay, so the user's asking about the Polkadot Technical Fellowship and, specifically, how its compensation works. My initial thought is to dive into the available documentation and see what's out there. I've got a list of potential candidates, so let's break them down and figure out the best approach.

I see several schemas related to the fellowship: `wiki-fellowship-technical`, `wiki-learn-learn-polkadot-technical-fellowship-6`, `wiki-learn-learn-polkadot-technical-fellowship-7`, `wiki-learn-learn-polkadot-technical-fellowship-0`, `wiki-learn-learn-polkadot-technical-fellowship-1`, `wiki-learn-learn-polkadot-technical-fellowship-2`, `wiki-learn-learn-polkadot-technical-fellowship-9`, and `wiki-learn-learn-polkadot-technical-fellowship-10`. I need to figure out which are most relevant and how to synthesize them effectively.

The core of the question seems to be "What is the Polkadot Fellowship?" and "How does the salary system work?" – essentially, a structural and financial overview. I need to be efficient and give the user a complete picture, so that they will be happy with my response.

`wiki-fellowship-technical` seems like the clear frontrunner as the primary source. It promises to cover the fellowship's structure, ranks, membership, promotion, RFC process, *and* salary/compensation. That ticks all the boxes. That's a good place to start, as it should provide the overall picture.

I will then use `wiki-learn-learn-polkadot-technical-fellowship-6` to reinforce salary details, it has specifically mentioned it and I'm guessing that it will be good supporting context.

Then, to add more details, `wiki-learn-learn-polkadot-technical-fellowship-7`, with its table of ranks and salaries, should give a clear numerical breakdown. Finally, `wiki-learn-learn-polkadot-technical-fellowship-0`, which should be able to provide a simple definition, is also a useful supporting piece.

So, in summary, I'll go with `wiki-fellowship-technical` as the main source and bolster it with the supporting schemas mentioned above. That should provide a comprehensive and detailed response to the user's inquiry, covering both the structure of the fellowship and its compensation model.




**Defining the Fellowship**

I'm currently focused on defining the Polkadot Fellowship. I've begun to outline its core function, drawing initial information from the wiki. I'm noting that the Fellowship is a self-governing on-chain body. The question of compensation within the Fellowship also remains a key consideration.


**Analyzing Salary Structure**

I've been analyzing the salary structure, noting the Collectives system's role and its replacement of the Governance V1 Technical Committee. I'm seeing a ranking system from 0-9, and the associated annual salaries, and I've started examining monthly contributor rewards and the requirement of periodic rank defense. I'm also examining the funding method, which is typically via the Treasury, often in USDT. I'm also looking at current on-chain activities, specifically Referendum 499, and a rank 2 member.


**Outlining the Fellowship Structure**

I'm now outlining the structure, including ranks and the manifesto's guidance. I'm focusing on the on-chain nature and Collectives system's role. I've begun drafting section 1, defining the Fellowship as a self-governing expert body replacing the V1 Technical Committee, working on Polkadot/Kusama protocols. I'm also drafting section 2, which states members should receive a monthly allowance comparable to gross income in OECD countries. I'm noting rank and salary details too.




**Navigating the Polkadot Technical Fellowship Onboarding**

Alright, so the user's curious about the Polkadot Technical Fellowship – joining it and what's expected. My initial scan of the schemas reveals a few key documents. The one I want to look at first is `wiki-learn-learn-polkadot-technical-fellowship-9`. It's pretty straightforward with its title, "Becoming a Member," which suggests it'll likely lay out the core tenets and expectations, and most importantly, the Polkassembly link. That's the primary jumping-off point.

Then I'll look at `wiki-fellowship-technical` as it covers the structural, conceptual overview of the entire fellowship. I want to build a high-level understanding of this, including ranks, the membership model, promotion pathways, the RFC process, and compensation models. That will frame the specifics.

Next, I need to find instructions. It looks like `wiki-learn-learn-polkadot-technical-fellowship-10` mentions a fellowship dashboard. Good, I'll bookmark that. It's probably the most practical resource.

I see `wiki-learn-learn-polkadot-technical-fellowship-6` references ranks and salary, and that initial induction starts at rank 0, which is useful to know. I'll read through this and make sure I understand the rank structure.

Finally, while not directly related to *joining*, `wiki-learn-learn-polkadot-technical-fellowship-8` mentions membership management and governance. And `wiki-learn-learn-polkadot-technical-fellowship-1` references the Fellowship Manifesto which may be helpful for building context.

In summary, I'm going to consider these schemas in order of their usefulness:

*   **Primary:** `wiki-learn-learn-polkadot-technical-fellowship-9` (for the actual *how-to* and tenets).
*   **Supporting:** `wiki-fellowship-technical` (broader context), `wiki-learn-learn-polkadot-technical-fellowship-10` (dashboard link), and `wiki-learn-learn-polkadot-technical-fellowship-6` (rank info) to provide the complete picture. I'll begin there and drill down as needed.




**Initiating Polkadot Strategy**

I'm starting to map out my entry into the Polkadot Fellowship. Right now, I am starting by looking into understanding the requirements and the application process. Next, I'll be looking into community discussions to learn more.


**Analyzing Fellowship Applications**

I am now delving into successful Fellowship applications, specifically those from Nathaniel Bajo and Christopher Kalule. I'm focusing on their backgrounds as full-stack developers and their contributions to the Polkadot ecosystem, particularly on-chain systems and cross-chain communication (XCM) for Bajo's case. My next step will be to extract relevant patterns from their profiles and apply them to my potential application.


**Identifying Key Contributers**

I'm now identifying successful applicants within the Polkadot ecosystem. I've noted that most inductees have a full-stack background, and contributed to either Rust, Substrate, or Polkadot SDK. I'm also examining profiles such as Jason Mansfield, who focuses on JAM and execution architecture, and Kunal Drall, a PBA-X graduate with a Substrate/FRAME focus, to identify specific patterns in their backgrounds.


**Outlining My Contribution**

I'm now formulating how my full-stack skills can align with Polkadot's needs. I'm focusing on the examples of Nathaniel Bajo and Christopher Kalule, who successfully integrated their full-stack experience with contributions to Asset Hub payments, XCM, and the Polkadot-SDK. My plan is to register interest through Polkassembly, contribute to the Polkadot Fellows GitHub repository, and consider the Polkadot Blockchain Academy (PBA) program.




**Polkadot Fellowship Task Acquisition - My Analysis**

Alright, let's break this down. The question boils down to finding the Fellowship's active tasks and backlog, likely within a GitHub repository context, given the user's specific mention of GitHub. I need to pinpoint where they would be managing and exposing this work.

Scanning the available schemas, the direct hits are definitely in the "wiki-learn-learn-polkadot-technical-fellowship" family. Specifically:

*   `wiki-learn-learn-polkadot-technical-fellowship-0`: This one is gold. It *explicitly* names the [Polkadot Fellows](https://github.com/polkadot-fellows) repository. That's the core. That's likely where the tasks, issues, and overall Fellowship backlog are managed off-chain. Bingo.

*   `wiki-learn-learn-polkadot-technical-fellowship-3`: This mentions Fellowship governance, RFCs, and whitelisting. Important. RFCs, I know, are Request for Comments. So those RFCs in the `polkadot-fellows/RFCs` repo are also a clear signal for ongoing work and topics.

*   `wiki-learn-learn-polkadot-technical-fellowship-10`: I should flag this one. Induction instructions on the Fellowship dashboard could be relevant to how one finds/starts contributing, and thus, finding tasks.

*   `wiki-learn-learn-polkadot-technical-fellowship-2`: While not a *direct* source of tasks, the public discussion channels (Matrix chat) and YouTube meetings listed there are probably a good starting point to ask and learn what is going on.

The other schemas are less directly useful. `wiki-general-polkadot-v1-28` is a supporting piece, but talks about the RFC submission process, so I am not reading that as the main source of the tasks, but a pointer for how to contribute. `wiki-bounties-tips` focuses on Treasury bounties, which is a funding mechanism, but not specifically the Fellowship's task queue. Treasury bounties and Fellowship tasks can be related, but are still distinct.

So, to summarize for the user, I'd say:

**Primary Source:** `wiki-learn-learn-polkadot-technical-fellowship-0` – Check that [Polkadot Fellows](https://github.com/polkadot-fellows) repository immediately.

**Secondary/Supporting:** `wiki-learn-learn-polkadot-technical-fellowship-3` – Look at the RFCs in the `polkadot-fellows/RFCs` repo. Consider the other schema as useful for onboarding and community/discussion channels.

The user should have a solid starting point now.




**My Analysis of the Bounty Listing Request**

Okay, so the user needs to find work opportunities by listing active bounties and their descriptions. Let's break this down systematically. My initial thought is to look for an endpoint that's designed for listing items, and the naming convention strongly suggests `endpoint-posts-listing` fits the bill. It's meant for displaying a paginated list of governance proposals. Crucially, the documentation explicitly states it supports `Bounty` as a proposal type, which is promising.

Now, how do we define "active"? The standard "active" filter for this type of API is often `status=Deciding`, which is geared towards active voting proposals. However, for bounties, "active" might mean something different, probably reflecting states like "Proposed" or "Funded". The documentation doesn't specify which status filter is needed for bounty activities. Given that the user is looking to *find* work, I am going to assume they want bounties that are open for action.

The documentation for `endpoint-posts-listing` also says "show me recent bounties", "list ... bounties", which, again, fits the user's need to list all bounties. That's a strong indicator.

Now, concerning the "descriptions" part, `endpoint-posts-listing` provides a list of items. Generally, these items will have a title and a short snippet or description. For full descriptions, I would have to use `endpoint-posts-content-summary` or `endpoint-posts-individual`, *but* these are for individual bounty details, and not a list. Because the request is to "list", the list endpoint would be the correct first step.

Let's quickly check the other endpoints. `endpoint-bounty-stats` provides statistics, not the list the user needs. `endpoint-posts-child-bounties` gives child bounties for a parent bounty, which is not what the user wants. `endpoint-bounty-user-activity` tracks bounty claims and awards, and `endpoint-posts-individual` is for a *single* bounty.

The best approach, based on this analysis, is:

*   **Primary:** `endpoint-posts-listing` with `proposalType=Bounty`. This is because the user wants to get a "list" of bounties. This endpoint serves that exact purpose. The `proposalType` filter ensures we get the right kind of items. We might need to consider a different status, but the API itself states `status=Deciding` is the usual "active" filter.

No other endpoint is strictly necessary to answer the prompt as written. Although `endpoint-bounty-stats` could offer additional context, it doesn't provide the list needed.

So, `endpoint-posts-listing` is the initial and best solution to retrieve the list of bounties and potentially includes enough description.




**My Analysis of Finding Work in the Polkadot Ecosystem**

Okay, the user wants to know how to find tasks or contribute to the Polkadot ecosystem, essentially asking "what to work on". The initial plan had some hits, but I need to broaden my approach. My first thought is that "issues" and "tickets" translate to "Bounties" and "Child Bounties" in this context. Polkassembly failed previously, and Subsquare is a good alternative for governance and bounties; it already succeeded in giving an overview and fellowship application, so I should now look at what data Subsquare holds for treasury and bounties. I'll need to check the Subsquare endpoints I have access to, which include `/user/profile`, `/overview/summary`, and `/gov2/referendums`. The user did mention Subscan but with limited "RELEVANT ENDPOINTS." I'll stay within the parameters. I have to avoid retrying Polkassembly. Now, I should expand the search beyond the Fellowship. I'll need a new plan.

The current strategy relies on the previous steps, which were focused on Polkadot Fellowship. The failure of Polkassembly was likely a result of the same. The user's query is broad, and it's time to get a good overview of the whole ecosystem. I'll reframe the search and use the existing tools I have, Subsquare, Polkadot Forum, and Polkadot Wiki.

Here's my refined plan with the steps in order:

*   **Step 5:** Search the Polkadot Wiki for general "Contributing" and "Bounties" information.
*   **Step 6:** Search the Polkadot Forum for "open issues", "bounties", or "work".
*   **Step 7:** Use Subsquare to list active Treasury referenda to see what projects are active.

I'm focusing on broadening the scope and avoiding failed approaches, I can only use 5 steps. I'll stick to this plan and explore each resource to identify opportunities for the user.




**Navigating the Polkadot Contribution Landscape**

Okay, so the question is how to contribute to Polkadot, both as a developer and a community member, and importantly, where to find specific tasks. Let's break this down. First, I need to evaluate the relevant wiki entries. The user's query suggests they're looking for practical entry points and opportunities.

Immediately, a few stand out. The `wiki-technical-docs` entry is a good starting point to understand the technical foundations and available developer resources, like Substrate and the runtime. From there I'll drill down into the community and contribution-focused wikis.

*   `wiki-general-contributing-0` is specific to the wiki itself, which isn't the primary focus here, I'll put it aside for now.
*   `wiki-general-community-14` and `wiki-general-community-15` look promising as they link to jobs, teams, and the overall Polkadot Stack.
*   `wiki-general-build-open-source-0` deals directly with the "Open Source Polkadot Stack" and PR contributions, which is key.
*   `wiki-bounties-tips` is critical for finding treasury-funded "tasks" or bounties.
*   `wiki-general-community-2` is helpful as it points to GitHub and the Forum.

Initially, I thought `wiki-general-build-open-source-0` seemed like the most relevant. It addresses "how to contribute" to the open-source stack directly. However, the user also wants to know "where to find tasks," which is the question's focus. `wiki-bounties-tips` clearly offers that, as do `wiki-general-community-14` and `wiki-general-community-15`.

The "how to contribute" is answered by `wiki-general-build-open-source-0`. But the "where to find tasks" is really the heart of the matter. So, the key is integrating these.

So, here's my refined approach: I'd use `wiki-general-build-open-source-0` as the primary entry, since it addresses contributing to the Polkadot Stack and contributing via PRs.

I will also include these supporting entries:

*   `wiki-general-community-14`, to understand the ecosystem and Polkadot Stack.
*   `wiki-general-community-15`, to know about jobs and the Polkadot Academy.
*   `wiki-bounties-tips` for bounties and treasury tasks.
*   `wiki-general-community-2`, for GitHub and forum discussions.

It's essentially a multi-faceted approach. `wiki-general-build-open-source-0` is the core, with community resources and bounty programs providing practical "tasks". In summary, the combination of contributing to the Polkadot Stack via the open-source approach, coupled with the potential to find paid tasks through bounties, and engaging with the community on GitHub and the Forum, offers the most comprehensive pathway for Polkadot contributions.




**My Revised Strategy for Helping the User Find Work in Polkadot**

Okay, so the user wants to jump into the Polkadot ecosystem and is looking for specific tasks or "tickets" – something concrete to work on. My initial plan involving `polkadot-wiki`, `polkadot-forum`, `subsquare`, and `polkassembly` seems to have hit a snag.  It seems the approach I used earlier (steps 1, 2, 4, 5, 6, 7) didn't give good results and `polkassembly` was outright failing. The common thread here seems to be overly specific queries that didn't yield actionable issues.

Looking closer at what the user wants, "what to work on," I need to frame this within the Polkadot context.  "Work" in Polkadot often means: on-chain *Bounties*, proposing *Treasury Proposals*, joining the *Fellowship* (though the previous attempts may have focused too heavily there), tackling *GitHub Issues* (which I can probably access via the Wiki or Forum), or participating in *Hackathons/Events*.  Since the user is asking about "issues or tickets," *Bounties* are the closest thing to actionable tasks.

Based on the failure with `polkassembly`, likely when searching for "tickets," I'll try to get data on bounties. Both Subsquare and Polkassembly have bounty-related endpoints, but since the previous step failed, I'm leaning toward Subsquare as the primary source.

I've got the data I previously fetched, which was focused on the Fellowship. Now, I need to shift my focus toward *Bounties*.

Here's my updated plan:

1.  Use Subsquare to search for "Bounties" on Polkadot and Kusama (the best option considering `polkassembly` failed).
2.  Use the Polkadot Wiki to find "how to contribute" or "bounties" to find entry points.
3.  Use the Polkadot Forum to search for "open tasks" or "help wanted."

I'll check if the `polkassembly` `/api/v2/Bounty` endpoint works, since the previous failure might have been due to a search, not listing.

My revised approach:

*   **Step 8**: Get a Polkadot overview from Subsquare using the `/overview/summary` endpoint to check if bounties are active.
*   **Step 9**:  Get an overview from Subsquare for Kusama.
*   **Step 10**: Search the Polkadot Wiki for "contribution guide".

But wait, the user isn't just asking "what are the tickets," it's "how do I know what to work on?" Therefore, I'll focus on *Bounties* and *Treasury Proposals*.

Let's refine my approach:

*   **Step 8**: Subsquare `/overview/summary` (Polkadot) - for a quick view of what's active.
*   **Step 9**: Subsquare `/gov2/referendums` with `is_treasury=true` - to find what is being funded.
*   **Step 10**: Polkassembly `/api/v2/Bounty` (Polkadot) - to check if this specific endpoint works now.
*   **Step 11**: Polkadot Wiki search for "contributing".

Because `polkassembly` failed previously, I'll prioritize Subsquare to get a list of bounties.

Okay, let's try this:

1.  Subsquare overview (Polkadot).
2.  Subsquare overview (Kusama).
3.  Polkassembly Bounties (Polkadot) – if this endpoint works.
4.  Wiki search for "contributing".

Considering the user's explicit question, "how do i know what to work on ? are there issues or tickets etc ?," I'll focus on *Bounties* and *Treasury Proposals*.

I need to remember that `polkassembly` failed, and I should avoid it or use a very safe endpoint. Subsquare has the `/overview/summary`. I'll try those and the search on the Wiki.

Here is my updated, final approach:

*   **Step 8**: Subsquare `/overview/summary` for Polkadot – to see bounty/treasury counts.
*   **Step 9**: Subsquare `/overview/summary` for Kusama.
*   **Step 10**: Polkadot Wiki search for "contributing to polkadot" – to find the "how-to."
*   **Step 11**: Polkadot Forum search for "help wanted" or "tasks."

This covers both the "how do I know" (Wiki/



**My Analysis of Contributing to Polkadot Development**

Okay, so the user's asking about how to get involved in Polkadot development and specifically, where to find those juicy issues and tickets. Let's break this down. From the schemas, it's clear there's a lot of information, and we need to zero in on the core SDK stuff, not just the Wiki itself.

My initial thought is that `wiki-general-community-2` seems the most promising, since it specifically calls out the "Polkadot GitHub" – that's gotta be the place for tickets. Also, `wiki-general-community-14` points to the "Polkadot Stack," which sounds like a good place to see what's in progress and how to jump in. Then there is the entry point, `wiki-development-sdk` that is important general SDK context.

I went back and checked the specific "contributing" schemas, but those are all Wiki-centric, which isn't what the user is after.

So, I'm thinking the best route is the GitHub repository. `wiki-general-community-2` has the URL, which is `https://github.com/paritytech/polkadot-sdk/tree/master/polkadot`. That's where I would expect to find the actual code and, more importantly, the issues and tickets related to development. `wiki-general-community-14` is also extremely relevant for contribution opportunities. And of course, the general context is found in `wiki-development-sdk`

Therefore, I'll recommend the following:

*   **Primary:** `wiki-general-community-2` – The main resource for finding issues and tickets within the Polkadot GitHub repository.
*   **Supporting:** `wiki-general-community-14` – A good source for seeing contribution opportunities and the "Polkadot Stack."
*   **Supporting:** `wiki-development-sdk` – Provides general context for the Polkadot SDK.

This should give the user a solid starting point for getting involved in the core Polkadot development.




**Identifying Potential Tasks**

I'm currently trying to figure out what specific tasks I should focus on. I'm starting by exploring the Polkadot Wiki to understand Fellowship backlog and project tasks, then will also search the Polkadot forum for more context.


**Expanding Task Horizons**

I've expanded my search beyond initial resources. I'm now looking into GitHub issues, specifically "good first issues" related to the Fellowship, and also monitoring the Polkadot forum for "help wanted" and "bounties". I am adding Subsquare, to see Treasury/Bounty activity and active referenda. I will be doing this in both the Polkadot and Kusama network. I will also be looking in the wiki for contribution/issue trackers.


**Discovering Bounty Opportunities**

I'm now focusing on specific avenues for contribution. I have found a curated ecosystem task list and am looking at Polkadot's GitHub repositories, including `polkadot-fellows`, `paritytech/polkadot-sdk`, and the wiki. Furthermore, I've identified active bounties, including a UX bounty and a business development travel bounty. Currently, Kusama has 12 and Polkadot has 22 active bounties to pursue.


