**Finding the Subsquare Team's Beneficiary Address**

Okay, let's get down to brass tacks. I've got this data, and I need to pinpoint the beneficiary address for the Subsquare team on Polkadot. Looking at the structure, I see a list of projects, with the first one clearly identified as "Subsquare." Excellent. Now, I need to check the associated `openGovReferenda` to uncover any beneficiary information.

I'll sift through the referenda linked to Subsquare. Alright, referenda 1722, 1612, 1225, 1001, 631, and also Treasury proposal 336 are on my radar. Now, let's examine these referenda to extract the beneficiary details. Referenda 1722, 1612, 1225, and 1001 all consistently point to `{"chain":"assethub","address":"12sNU8BXivMj1xQmcd4T39ugCyHjmhir8jkPqfAw5ZDESrx4"}`. Both referenda 631 and proposal 336 explicitly list the beneficiary as `"12sNU8BXivMj1xQmcd4T39ugCyHjmhir8jkPqfAw5ZDESrx4"`.

Furthermore, I'm noting the proposer for each of these referenda is also `12sNU8BXivMj1xQmcd4T39ugCyHjmhir8jkPqfAw5ZDESrx4`. This adds another layer of confidence to the findings.

Even better, the project summary for referendum 13 (Treasury Proposal 336) actually explicitly states, "Beneficiary: OpenSquare (12sNU8BXivMj1xQmcd4T39ugCyHjmhir8jkPqfAw5ZDESrx4)." That's the smoking gun!

Therefore, based on this thorough analysis, I'm confident that the beneficiary address for the Subsquare team is `12sNU8BXivMj1xQmcd4T39ugCyHjmhir8jkPqfAw5ZDESrx4`. The consistent use across multiple referenda, along with the explicit confirmation in a project summary, solidifies this conclusion. My extracted value, therefore, is `"12sNU8BXivMj1xQmcd4T39ugCyHjmhir8jkPqfAw5ZDESrx4"`, and the reasoning is ironclad.




**Identifying the Subsquare Team's Beneficiary Address on Kusama**

Alright, let's get down to it. I need to pinpoint the beneficiary address associated with the "Subsquare" team's proposals on the Kusama network, given this raw data. It seems like the information is spread across different governance mechanisms, so I'll need to correlate the data.

I'm looking at `openGovReferenda`, `childBounties`, `treasuryProposals`, and `treasuryTips`. Based on what's available:

*   Referendum 164, titled "Subsquare, dotreasury and statescan retroactive maintenance...", looks promising. The proposer and the beneficiary listed in the `proposalCall` are the same: `ESgz7GLVW7BL5DhRgpVnxSXVwaKt4ytWcrf52TY1GQD1cEb`. This looks very likely.
*   Next, there's Child Bounty 54, with a similar title "Maintenance proposal: dotreasury and statescan Q3 and subsquare...". The beneficiary here is also `ESgz7GLVW7BL5DhRgpVnxSXVwaKt4ytWcrf52TY1GQD1cEb`. This strengthens my hypothesis.
*   Then there's Treasury Proposal 305, which is linked to Referendum 164. I expect a related address, and sure enough, the beneficiary is `ESgz7GLVW7BL5DhRgpVnxSXVwaKt4ytWcrf52TY1GQD1cEb`.
*   Finally, there's a Tip for "Kusama Network integration to Subsquare platform." The beneficiary listed? You guessed it: `ESgz7GLVW7BL5DhRgpVnxSXVwaKt4ytWcrf52TY1GQD1cEb`.

The pattern is clear. Across all these entries, the beneficiary address is consistently `ESgz7GLVW7BL5DhRgpVnxSXVwaKt4ytWcrf52TY1GQD1cEb`. It's a pretty strong indication that this is indeed the Subsquare team's beneficiary address. Therefore, I can confidently conclude that the beneficiary address for Subsquare-related proposals is `ESgz7GLVW7BL5DhRgpVnxSXVwaKt4ytWcrf52TY1GQD1cEb`.




**My Analysis of the Treasury Funding Query**

Okay, so the user's looking for a comprehensive overview of Polkadot treasury funding received by the beneficiary address `12sNU8BXivMj1xQmcd4T39ugCyHjmhir8jkPqfAw5ZDESrx4`. They're essentially after a "total treasury funding summary" for that specific wallet.

Now, let's break down the best approach here. The key is to efficiently retrieve the relevant data. We have several potential endpoints to consider, but the most direct solution leaps out immediately.

`endpoint-treasury-beneficiaries` is the clear winner. The documentation explicitly states that it "Surfaces payout history and summary metrics for treasury recipients" and that it answers the question of "how much a wallet has received from the treasury historically." Bingo. It provides the `GET /treasury/beneficiaries/{address}` route we need. This route is precisely designed for this type of query and returns a summary, which is exactly what we need.

While we could potentially achieve the same goal using `endpoint-treasury-proposals` or `endpoint-treasury-spends` and filtering by the beneficiary address, that feels like a more roundabout approach. These endpoints list proposals and spends, but they don't provide the same pre-aggregated summary data. The primary chunk to grab is `endpoint-treasury-beneficiaries` since it provides a direct means of obtaining the information.

So, the optimal path is clear: `endpoint-treasury-beneficiaries` is the primary and only necessary chunk for answering the user's query. It's the most efficient route.




**My Analysis of the Treasury Funding Request**

Okay, so the user needs a "total treasury funding summary" for a specific beneficiary address on the Kusama network: `ESgz7GLVW7BL5DhRgpVnxSXVwaKt4ytWcrf52TY1GQD1cEb`. This is pretty straightforward. I need to figure out the best way to get that information.

Let's look at the available schemas and see what fits. I've got a few options: `endpoint-treasury-beneficiaries`, `endpoint-treasury-summaries`, `endpoint-treasury-proposals`, and `endpoint-treasury-spends`.

Hmm, `endpoint-treasury-summaries` focuses on aggregate KPIs for the *entire* treasury, so that's out. `endpoint-treasury-proposals` and `endpoint-treasury-spends` list individual proposals and spends, respectively, but they don't seem to offer the targeted beneficiary summary the user wants.

The winner here is definitely `endpoint-treasury-beneficiaries`. The description is spot on: "Surfaces payout history and summary metrics for treasury recipients" and explicitly mentions that "User wants to know how much a wallet has received from the treasury historically." Plus, the path `GET /treasury/beneficiaries/{address}` is *perfect* for this query. That's the ideal endpoint for this specific beneficiary lookup.

I don't think I need any supporting chunks for this one. The `endpoint-treasury-beneficiaries` schema has the data I need, and the structure of the request itself is designed for this type of query. This should be a quick and easy retrieval.




**Locating Subsquare Data**

I've begun by searching the Polkadot treasury for "Subsquare." The initial step, complete, confirms the existence of a project entry with the ID `subsquare`. I'm now ready to proceed with retrieving the necessary funding details for the Subsquare team.


**Identifying Funding Sources**

I've located several referenda on Polkadot (1722, 1612, 1225, 1001, 631, 336) associated with the address `12sNU8BXivMj1xQmcd4T39ugCyHjmhir8jkPqfAw5ZDESrx4`. I also found a Kusama referendum (164) and a child bounty (54) and tip related to `ESgz7GLVW7BL5DhRgpVnxSXVwaKt4ytWcrf52TY1GQD1cEb`. I'm now cross-referencing these addresses with the Polkadot treasury data.


**Analyzing Address Relationships**

I'm now investigating the connections between the addresses identified earlier, specifically those from Step 3 and Step 4, and cross-referencing them. I'm noting that the addresses in those steps don't seem to match the initial search results, particularly for `12sNU8BXivMj1xQmcd4T39ugCyHjmhir8jkPqfAw5ZDESrx4` and `ESgz7GLVW7BL5DhRgpVnxSXVwaKt4ytWcrf52TY1GQD1cEb`. I'm going to re-evaluate the search criteria.


**Calculating Polkadot Funding**

I'm now manually totaling the funding amounts from the Polkadot referenda. Referendum 1722 was rejected, so its contribution is zero. The remaining referenda, 1612, 1225, 1001, 631, and 336, yielded specific amounts in USDC, USDT, and DOT. I've calculated the totals for these currencies.


**Summarizing Network Funding**

I've totaled the Kusama funding, pulling the data together from referendum 164, child bounty 54, and a tip to address `0xf265...`. The resulting total is 3,892.868 KSM. I've now completed the calculation of the grand total, including both Polkadot and Kusama funding. I have determined that Subsquare has received ~$1,191,887.33 total funding.


**Consolidating Financial Data**

I've been reviewing the data to ensure each funding source is properly documented. I've re-confirmed that referendum 1722 was rejected and thus its contribution is zero. I've double-checked my calculations for the amounts from each Polkadot and Kusama funding source, including currencies. I've confirmed beneficiaries for Polkadot and Kusama.


**Verifying Dollar Totals**

I've re-examined the component amounts to confirm accuracy. After converting DOT at $1.52, and KSM at $5.26, I calculated the following: DOT at $81,041.84, KSM at $20,476.48568, and stables at $1,090,369, totaling $1,191,887.32568, which matches the earlier calculation. I've also validated the individual referenda amounts and decimal places, ensuring the amounts align with Polkadot Asset Hub and Subscan.


**Revising Funding Data**

I'm now cross-referencing all data points, specifically focusing on Subsquare's proposal IDs. I've re-confirmed the USD totals, but noticed that Step 1 mentions 8 proposals, while the referenda list contains only 6, indicating a possible gap in data acquisition. I will verify if I missed any. I've re-examined the discrepancies between the proposal IDs and referendum IDs. I've noted a matching relationship between Ref 631 and proposal 759. I'm focusing on the matching and cross checking proposal information.


**Confirming Referenda Details**

I'm now cross-referencing all the data again. I'm verifying the Kusama tip beneficiary and amount, and I'm re-confirming that the details match. I've double-checked all of the amounts for each referenda and, after verifying each entry, I see that I have all the key data points, and that each is correct.


**Finalizing Dollar Figures**

I'm now concluding my review of each source, confirming amounts and beneficiaries. I've re-verified DOT and KSM values, and all USD calculations for USDC, USDT, DOT, and KSM, are correct. The beneficiary for Polkadot is `12sNU8BXivMj1xQmcd4T39ugCyHjmhir8jkPqfAw5ZDESrx4`, and I have completed my work.


**Calculating Proposal Summaries**

I'm now recalculating the Kusama and Polkadot referendum totals, specifically verifying the individual proposal amounts. I'm excluding the rejected proposal, and noting that referendum 1722, which was worth $160,800, was indeed rejected. I've re-confirmed amounts in USDC, USDT and DOT. The Kusama totals include the referendum, bounty and tip.


**Refining Network Summaries**

I'm now consolidating the data into network-specific summaries. I will be sure to focus on the team's primary addresses. I will provide separate totals for Polkadot and Kusama, and then the final total. I will exclude any audit-related bounties. My focus is on the funding provided directly to Subsquare.


**Validating Final Figures**

I'm now running through a final validation. I've confirmed USDC and USDT values across referenda 1612, 1225, and 1001, and I've confirmed that the values are aligned, with the amounts from the initial calculation. I've rechecked the rejected Ref 1722, and confirmed all Kusama data is still accurate, as well.


**Revisiting Referenda Totals**

I'm now back-tracking to verify the overall referenda list. My focus is on ensuring no referenda were overlooked or incorrectly attributed. I'm re-examining the list from Step 1 and cross-referencing against the funding calculations, confirming the inclusion of all relevant proposals, specifically the DOT, USDC and USDT. I'm now cross-referencing the amounts, and beneficiary. I've confirmed that I have all the key data points, and that each is correct.


**Analyzing Proposal Gaps**

I'm now investigating a discrepancy between the stated number of proposals (8) and the number of referenda identified (6). While I've accounted for 5 successful referenda and one rejected, there remains a gap in the data. Upon reviewing the project summary, I have confirmed proposal IDs 155, 206, 336, 464, and 759, and noted that referendum 631 corresponds to TP 759. I'm focusing on the matching and the potential missing ones. I will clarify the scope of my calculation.


**Clarifying Scope Boundaries**

I'm now clarifying the scope of my calculation, specifically addressing the discrepancy between the stated total funding and the sum I calculated. I'm focusing on providing the funding received by the Subsquare team through the explicit data provided by the Polkadot and Kusama Treasury. I'll note the potential gaps in data coverage regarding older proposals. The $1,816,045.18 value may include older data. I will focus on the more recent Treasury V2 referenda and Kusama items.


**Refining Financial Analysis**

I'm now focusing on calculating the most accurate Subsquare funding total based on available data. I'm excluding the potentially irrelevant address identified in Step 3. I've re-confirmed that the funding I will provide is based on a manual aggregation of the referenda and Kusama items from Polkadot and Kusama treasuries only. I've noted that the initial summary total is likely including older data.




**Analyzing Funding Sources**

I'm currently delving into the initial funding for the Subsquare team, also known as OpenSquare. My primary focus is on cross-referencing data from Polkadot, Kusama, and their respective Subsquare instances. I'm keen to isolate and identify the very first funding infusion, but I'm trying to identify the correct sources and how to confirm the initial investment.


**Pinpointing Initial Funding**

I've been looking over the Kusama beneficiary history and have identified several key proposals and council motions. I've noted specific timestamps to pinpoint the earliest funding for OpenSquare, focusing on both Polkadot and Kusama instances. I'm cross-referencing these dates to create a solid timeline for their initial financial support. The `polkadot-CouncilMotion-73` from March 2021 appears to be the first identified, for Polkadot integration.


**Uncovering Early Proposals**

I'm now identifying proposals, focusing on those preceding the already-noted council motion. I've uncovered several earlier treasury proposals on both Polkadot and Kusama, as well as associated discussion topics on OpenSquare's initial proposal to establish its treasury. I'm cross-referencing timestamps to refine the timeline of early financial support and community discussion.


**Discovering Early Funding**

I've just uncovered earlier evidence. It looks like the very first funding requests were Polkadot Treasury Proposal 17 and Kusama Proposal 58. The Polkadot proposal, created October 27, 2020, aimed to create a knowledge tip authoring tool to solve news and knowledge sharing problems. The Kusama proposal, from November 30, 2020, sought to extend the treasury with community remarks. I'm noting the timestamps and purposes of each.


**Confirming Earliest Funding**

I've confirmed Polkadot Treasury Proposal 17 from October 27, 2020, as the earliest funding. This proposal, linked to Council Motion 34, funded a knowledge tip authoring tool, predating Subsquare's existence. I've re-contextualized this as the initial funding for the team now known as OpenSquare. I'm verifying this, and trying to trace any W3F grants to confirm if these were also earlier.


**Tracing Proposal Purposes**

I'm now clarifying the initial purpose of Polkadot Proposal 17, and I've confirmed it was for a knowledge tip authoring tool to generate shareable images. I'm noting the proposer's address, 12sNU8BXivMj1xQmcd4T39ugCyHjmhir8jkPqfAw5ZDESrx4, and comparing it to the Kusama proposal's proposer. I am refining the timeline of these initial treasury contributions.


**Clarifying Project Origins**

I'm now integrating information about dotreasury's inception on Kusama, which was built on Kusama Proposal 58 from November 2020. I'm double-checking the dates. I also found that dotBounties.com, though discussed in November 2020, was not an initial funding source. My latest update confirms Polkadot Proposal 17 as the earliest funding, linked to a knowledge-sharing tool. I'm still trying to find the date of an earlier W3F grant.


**Verifying Initial Funding**

I've just confirmed Polkadot Proposal 17 was *executed*, not just proposed, which makes it the earliest on-chain funding request. While not explicitly marked as executed in Step 1, it's confirmed in Step 5 with Referendum 164. I'm focusing on clarifying and confirming this initial grant as a definitive answer.


**Refining Funding Details**

I'm now revisiting Proposal 17's content and can confirm it wasn't a "milestone," but a stand-alone knowledge tip tool. This clarifies the initial purpose and the proposal's content, which aligns with its October 2020 timestamp. I'm also now noting Kusama Proposal 58's purpose, which was for the reputation and remark system, later known as dotreasury. I'm also adding that the proposer for Polkadot Proposal 17 was `12sNU8BXivMj1xQmcd4T39ugCyHjmhir8jkPqfAw5ZDESrx4`, and the proposer for Kusama Prop 58 was `ESgz7GLVW7BL5DhRgpVnxSXVwaKt4ytWcrf52TY1GQD1cEb`.




**Calculating Subsquare Funding**

I'm focusing now on pinpointing Subsquare's initial funding and quantifying all Polkadot and Kusama treasury disbursements to their team. I'm prioritizing accuracy in the numbers and am verifying the initial funding allocation, separating it from ongoing grants. It seems I am on track to meet the user's needs.


**Analyzing Funding Sources**

I've shifted my attention to specific treasury proposals and tips, differentiating between Polkadot and Kusama funding. I'm noting key details like proposal numbers and dates, as well as the stated purpose for each disbursement. It's helping me paint a clearer picture of OpenSquare's funding.


**Pinpointing First Mentions**

I've traced the initial funding entries. The first Kusama treasury tip for Subsquare integration was in May 2022. I found the first Polkadot funding, Treasury Proposal 155, in August 2022, focusing on Polkadot integration. I'm noting significant funding events, including OpenGov referenda for amounts of USDC, USDT, and DOT.


**Quantifying Dot/KSM Expenditures**

I am now focusing on the specific amounts of DOT and KSM disbursed. I'm extracting key data points from treasury proposals, tips, and child bounties, separating amounts for each category and chain. I'm currently cross-referencing values to ensure consistency in the findings.


**Calculating Total Disbursement Amounts**

I'm now consolidating all the financial data into totals. For Kusama, I've calculated a total of 5,131.978 KSM, combining various proposals and tips. For Polkadot, the totals are 106,540 DOT, 444,124 USDC, and 646,245 USDT. I've also noted rejected proposals, such as Ref 1722 and Prop 17, for completeness. I am focusing on eliminating duplicate and redundant steps.


**Calculating Fiat Equivalence**

I am now calculating the fiat equivalent of the disbursed tokens, focusing on a clear and concise presentation. I'm leveraging the fiat values already present in the data to ensure accuracy and consistency in the summary. My attention is on the initial fiat total provided for the project and how this corresponds to the token disbursements. The initial data mentions totals but doesn't distinguish between chain and projects. I am separating these out.


**Compiling Token Disbursements**

I'm now cataloging all token disbursements, pulling in data for USDC, USDT, DOT, and KSM, across various Polkadot and Kusama treasury proposals and tips. I'm focusing on accurately capturing the amounts and cross-referencing values to verify the results. I'm separating values and compiling them into clear, distinct entries for each token.



**Summarizing Treasury Disbursals**

I've tabulated the detailed KSM disbursement data, including treasury tips and proposals. I have verified that I can account for all token totals. I'm focusing on incorporating proper formatting, complete addresses, and citations. I am making sure to note any API failures, and I'm finalizing the comprehensive list of expenditures.


**Verifying Precise Totals**

I'm now cross-checking and confirming specific amounts from treasury proposals, meticulously converting Planck values to DOT and KSM. I've re-verified Prop 206, Prop 155, Prop 42, and the initial Tip values for DOT, along with Kusama's Prop 151, 96, 75, 58 and a Subsquare Tip. I've also verified Child Bounty 54's value. I'm focusing on ensuring data accuracy.


**Confirming Final Values**

I'm now verifying the final disbursements, cross-referencing all data points. I confirmed the KSM values, including Ref 164 and Child Bounty 54, and Polkadot disbursements, including Ref 1612, 1225, 1001, 631, and 13. My focus is on ensuring these match with my totals, including DOT, KSM, USDC, and USDT. I'm verifying that the total fiat value at submission is accurately reflected. I can confirm the initial Kusama tip on July 9, 2022.


