Dear council members,

Subsequent to the passing of [motion 577](https://kusama.polkassembly.io/motion/577), all of the newly opened collator slots on Statemine were reserved within the first few minutes.  There are members of the community who wish to aid by providing collation services to the Statemine chain.  

This XCM call seeks to increase the number of public collators from 8 to 12 by executing call_data `0x15010c000000` on Statemine.

A member of the community (bLD) [expressed interest](https://matrix.to/#/!QXMnIJzxlnVrvRzhUA:matrix.parity.io/$E60RCBR8RPscdvVrFHactJVUKBZXumAJoyfFYjq7jOg?via=matrix.parity.io&via=matrix.org&via=corepaper.org) via the direction channel and others have voiced their interest and preparedness within the Statemine & Statemint collator channel.  Joe was also party to the conversation and gave an endorsement.

I leave it to the council to decide if these additional slots should be opened. 

Regards,

Further increase of Statemine collators from 8 to 12.

Dear Council,

Presently there are eight collators on Statemine, four of them are operated by Parity as invulnerables and the other four are operated by public entities.  This proposal seeks to reduce the allocation of invulnerables to two and increase the number of publicly occupied slots to eight.   For reference and later comparison, State**mint** posses two invulnerable collators and six from the public.

The rationale is two fold, in the spirit of decentralization I am suggesting we reduce reliance on Parity (invulnerables) and shift to the public.  Secondly, as a matter of fulfilling the purpose of a canary; we should try to mimic or preferably advance beyond the allocations of Statemint.

The XCM message comprises of two encoded calls:

Set Candidates to 8 - `0x150108000000`

and 

Reduce Invulnerables to two -`0x15000850673d59020488a4ffc9d8c6de3062a65977046e6990915617f85fef6d349730fe8102dbc244e7ea2babd9f53236d67403b046154370da5c3ea99def0bd0747a`




Statemine Collator Update - Reduce invulnerables from four to two and increase public collators from four to eight

Dear council,
This motion seeks to reject five proposals for the following reasons:
<ol>
<li><a href="../treasury/196" target="_blank" rel="noopener">196 </a>- Submitted by an unknown parity by error</li>
<li><a href="../treasury/198" target="_blank" rel="noopener">198 </a>- Blockchain Rio 2022 - Event expired, funds no longer required</li>
<li><a href="../treasury/199" target="_blank" rel="noopener">199 </a>- Pais Digital Chile Summit - Event expired, funds no longer required</li>
<li><a href="../treasury/209" target="_blank" rel="noopener">209 </a>- LucasYoda - A revised proposal was submitted in its place</li>
<li><a href="../treasury/211" target="_blank" rel="noopener">211 </a>- Fearless Wallet - Erroneous submission, superseded by 212</li>
</ol>
Voting Aye supports rejecting all of these proposals.
Regards,
&nbsp;

Housekeeping - Rejection of five redundant treasury proposals

Dear Council Members, This motion was created in error while trying to submit motion 575 via extrinsic.
Regards,
&nbsp;

Please reject - Created in error

I've proposed this to close [bounty 15](https://kusama.polkassembly.io/bounty/15).  This bounty was proposed ~20 days ago with a title of `Hello all Kusama decentralized` and for a value of `0.01` KSM.  To present, there are no further details on the purpose of the bounty.

It is my opinion that we should close the bounty to keep the bounty section streamlined on contextualized subject matters.

Proposal to close bounty 15

This is a techincal committee proposal whose proposer address (FhLMxxkXxfgRRnv8hyRbNkpUMZ9umASMsRmKpZruVayaqhL) is shown in on-chain info below. Only this user can edit this description and the title. If you own this account, login and tell us more about your proposal.

Runtime upgrade to 9280

Runtime Upgrade to 9271

Dear All,

This motion seeks to upgrade Kusama's runtime from version 9260 to 9271.  This contains updates from two releases 9270 and 9271.

The following were included in the 9270 upgrade:

- [S] ⏳ pending non-critical audit #11771 Low - [contracts] fixed the bug with transfer value for delegate call
- [S] ✅ trivial #11807 Low - Un-deprecate transactional macro
- [S] ✅ audited #11398 Low - Buy&sell methods for uniques
- [S] ✅ audited #11669 Low - Revamp nomination pool reward scheme
- [S] ✅ audited #11746 Low - Fix nomination pools unbonding logic
- [S] ✅ trivial #11816 Low - Contracts: composable chainextension
- [P] #5798 ❗️ Medium - Westend xcm: collectives parachain is trusted teleporter
- [S] ✅ trivial #11770 Low - Add era to unbonded event
- [S] ✅ trivial #11874 Low - Contracts: allow chainextension::call() to access &mut self

Where as 9271 contained a few minor updates:

- Staking - MigrateToV10
- Nomination Pools - MigrateToV2

Full details on the runtime changes can be found within the [github release](https://github.com/paritytech/polkadot/releases/tag/v0.9.27) with changes associated with runtime 9271 found as an addendum to the bottom of the release.

The setCode hash is `0x5e8e9e34cd303305f690a6e977a8a80f955d0177f370b10f04a4b01d32a7202d`

Regards,



Runtime upgrade to 9271 - SUPERSEDED BY MOTION 530, VOTE NAY

It has now been **4 months** since we kicked off the **Governance Participation Rewards** Project and the **voter shelves** are filling up nicely!
![](https://i.ibb.co/RSF65Gz/Screenshot-2022-07-10-at-11-32-32.png)

### The impact is clear:

In terms of **participating wallets** we have seen a staggering **700% increase**. 
![](https://i.ibb.co/W0M7MpR/Screenshot-2022-07-12-at-22-31-36.png)

In terms of **turnout %** (participating KSM) we have seen a **100% increase** (“community” votes without whale wallets participating).
![](https://i.ibb.co/vHFxQZr/Screenshot-2022-07-10-at-20-50-08.png)

I am submitting this **proposal** to cover **past operational expenses** that we have not been able to cover through our revenues, as well as funding our **website** (includes a quiz + vote module) and miscellaneous related **side projects**.

You can find the full proposal [here](https://docs.google.com/document/d/1l4M16KKLkHxtbgklZR8fA6TjwETvupGnImlO0Aujg1s/edit?usp=sharing) in detail. 


Funding Governance Participation Rewards

This is a techincal committee proposal whose proposer address (F2i6trfXqFknbgB3d9wcd1X98WWdLLktmFtK8Beud75bjTW) is shown in on-chain info below. Only this user can edit this description and the title. If you own this account, login and tell us more about your proposal.

Kusama runtime upgrade v9260

This proposal was submitted in error and was superseded by [Motion 513](https://kusama.polkassembly.io/motion/513).  Please reject and focus your attention on Motion 513.

REJECT - Kusama runtime upgrade to v9260

tl:dr Treasury proposal for organizing a meetup about Polkadot NFTs for 40 people in Brno in the Czech Republic on 28th March 2022.

**Short description:**

- talk about technology behind NFTs
- KodaDot NFT explorer - the usecase for minting and collecting NFTs
- discussion about NFT parachains on Polkadot and Kusama 

**Detailed description:**
Non fungible tokens are familiar to many people while there is still a group of people who don't understand it to the ground level. For better understanding of the topic of NFTs, [Polkadotters](https://twitter.com/Polkadotters1) organized a meetup in Brno which was led by [Crypto DamSky](https://twitter.com/CryptoDamSky), who is a community manager at KodaDot, a NFT explorer for Kusama and Polkadot.

Check the full proposal [here](https://docs.google.com/document/d/1n_sDU4261AW3vSaUx9wXOxFsXzizAXeJ9YVlTw3LAgw/edit?usp=sharing)

Proposal for organizing an explanatory meetup about Polkadot NFTs and NFT explorers

Kusama runtime upgrade to version 9200

Good morning :)

This referenda seeks to increase the minimum commission from 3.0% to 8.5% and keeps all other staking configurations unchanged.  It is being proposed to foster a sustainable environment for all validators in light of reduced on chain returns as well as present market conditions.  

Appreciating that there was no forward discussion I anticipate there will be emphatic responses.  To aid with your decision making I've also included some supporting data for your consideration.

**Effects on validator earnings**

A validator operating at 3% commission can stand to earn (485.2/1000)* 4 * 30 * 0.03 = 1.75 KSM/month, this equates to ~70 USD/mth.  

The proposed configuration allows validators to earn (485.2/1000)* 4 * 30 * 0.085 = 4.94 KSM/mth which equates to ~ 200 USD/mth

**Effects on nominators**

Assuming a total stake of 6600 KSM, at 3% commission a nominator earns ~10.42% APY whereas at 8.5% commission a nominator* would earn ~9.83% APY, a 0.59% difference.

**Validator commission distribution**

Three hundred and eight (308) potential validators would be affected by the change to varying degrees.

- 0.00% - 13 [Chilled stashed]
- 3.00% - 234 - [+5.5%]
- 3.14% - 1 - [+5.36%]
- 4.00% - 6 - [+4.5%]
- 4.20% - 1 - [+4.3%]
- 5.00% - 28 - [+3.5%]
- 5.60% - 1 - [+2.9%]
- 6.00% - 4 - [+2.5%]
- 7.00% - 1 - [+1.5%]
- 8.00% - 19 - [+0.5%]
- 9.00% - 1
- 10.00% - 122
- 13.00% - 1
- 15.00% - 61
- 20.00% - 4
- 50.00% - 10
- 100.00% - 493


YOLO - Setting the Minimum Commission to 8.5%

Dear community,

I submit this proposal on behalf of myself and other participating members of the 1KV.  The proposal attempts to cancel eighteen (18) other proposals numbered seventy four (74) to ninety one (91) inclusive submitted by Paco reasoning given [here](https://twitter.com/paco_dot/status/1544223998636064769?s=20&t=ogqSdkYpxLZXQs-E8tCqhg).

It is in our opinion that the proposals serves no purpose above proposal seventy-one (71) and occupies the public proposal queue with high conviction (0.5 KSM per).   This increases the barrier to entry for other referenda and puts existing technical proposals seventy-two (72) and seventy-three (73) at lower priority. 

Regards,
Will | Paradox

Removal of eighteen (18) proposals on the public referenda queue

Dear community,

Referendum 182 seeks to register an identity for council person JAM.  JAM is one of the early council members and you can get an appreciation of his 'genesis story' [here](https://youtu.be/B0Fex0fSYkQ).  His lack of a registered identity was a personal peeve so with an empty public queue I seized the opportunity for a soft-topic.  

I should have done the same for Bruno via batch but it was a total omission on my part. With [resignation](https://bruno.id/withdrawing-from-polkadot-and-kusama-council/) in mind perhaps it wasn't that bad of an omission.

We are generally caught up with referenda of technical matters, governance can be used for softer matters as well.  Let's see how it goes.

Regards,
Will | Paradox

Get JAM a verified identity!

Dear community,

In this proposal I seek to modify the chain's staking configurations such that the minimum commission is changed from 0% to 3%.  All other parameters that are associated with the configuration remains the same as prior.  

For transparency the previous values are:

- Minimum Nominator Bond : 0.1 KSM
- Minimum Validator Bond: 0 KSM
- Max Nominator Count : 20,000
- Max Validator Count : 4,000
- Chill Threshold: null
- Minimum Commission: 0

The value of 3% was determined after several [days of discussion](https://kusama.polkassembly.io/post/1306) and reflects a conservative position which is further held by low rates of exchange.  We trust that the foregoing would benefit the chain by improving the sustainable operations of validators who have qualified into the active set.

Best Regards,
Will | Paradox

Establishing a Minimum Commission of 3% 

Dear Council,

I write to you in the aftermath [of a failed referendum](https://kusama.polkassembly.io/referendum/155), despite the outcome, a fair majority of the community voted for change. I don’t perceive this as votes strictly for a decrease of the active validator count but votes in principle against disparity of entry into the active set.

With this referendum failed I would like to steer discussion towards determining the root cause of the issue and how it may be addressed. It is my belief that if nPoS receives ‘ideal’ information it would do a better job at levelling stake. This issue, as I perceive it, is that there are barriers towards a natural progression of nominations. If a validator is able to enter the active set with a lower total-stake, their return per KSM would be high and attract nominations, thus helping to level stake. This natural and ideal progression is inhibited by exorbitant commissions, at many times 100% and blocking of nominations.

My suggestions are as follows:

- Establish minimum and maximum commissions on-chain, the values of which can be determined by governance. The establishment of a maximum commission to some reasonable amount like 12.5% should allow fair earning for validators and allow attractive returns for nominators. This change also aids with removing 100% commission duping i.e. fooling a nominator into believing that your commission is lower than it really is. Duping will still exist but it would not be as detrimental.

- Remove blocking of nominations.

- Increase the transaction fee for kicking a nominator and allow this fee to be configurable via governance. This is recommended with the intent to dissuade nominator kick scripts. My suggestion is 0.01 KSM, governance configurable.

Despite having a maximum commission that is <100%, custodial staking services can still make themselves unattractive to nominators by positioning their self-stake higher than average or at average and with maximum commission. Providing that they own their nominated stake (which is generally the case) commission vs staking rewards matter not.

Your thoughts are as always appreciated. I look forward to them. Please see follow up posts with example calculations and suggestions from the community.

I would like to make it abundantly clear that the nPoS system is not making any deliberate attempt to favour any one party. This is just as a circumstance of nominations and the demand on the nPoS system to produce 1000 validators within the 3 nPoS tenets.

Kind Regards,
Will | Paradox

Disparity of the minimum stake requirement (MSR) for entry into the active set

Dear community,

With the upcoming rollout of runtime 9160 we should explore the option of an extrinsic to set a network wide minimum commission.  This discussion relates to metrics associated with the KUSAMA chain.  After the on chain parameter is declared any persons using the staking.validate() extrinsic to change their commission would have to abide by the new threshold.  All existing commission values would remain the same.

I implore those who are contributing to this post to do so in a meaningful and calculated manner.  The goal is to ensure that validators are compensated fairly and that they may continue to operate their nodes in a sustainable manner.  It is not an avenue for undue enrichment.

### Stakeholders
Some of the apparent stakeholders are:

1. Independent Validators
2. Commercial Validators
3. Retail Nominators (everyday person)
4. Commercial Nominators who don't operate their own validator (Karura, ParallelFi etc.)

Parties who self-nominate like many of the exchanges should not be affected by this change.

This thread is opened for us to discuss in an empirical manner what is a reasonable value for this threshold and to appreciate the views of all entities it affects.  A high commission can deter retail nominators from staking and it can encourage commercial nominators to host their own validators. 

### Considerations

I would like to encourage discussions in a structured and meaningful manner.  The proposed commission should consider items like:

1. Rental cost for an appropriately spec'd validator host-machine
2. Compensation for the hours exerted by the validator operator
3. Fair and reasonable profit
4. Fluctuations in era points during a monthly period
5. Fluctuations in token price during a monthly period


### Constants

The following should be used in calculations.

- [Kusama Price](https://kusama.subscan.io/tools/charts?type=price) - USD$256 / 1 KSM
- Total Kusama earned per era = 0.6 KSM
- 30 days per month

### Sample Calculation

Ideal return per month [IR] = ( [Rental Cost] + [Operator Hourly Rate] * 1 (hr) * 30 (days) ) * (1 + ( [Percentage Profit]) / 100);

IR = (80 + 20 * 1 * 30) * (1+(15/100))

IR = (80+600) ~~* 1.15~~

IR = $680/mth or 2.656 KSM

Commission required [CR] to earn 2.656 KSM over 30 days =>

0.6 * [CR]  * 4 (eras) * 30 (days) = 3.054

[CR] = 2.656 / (0.6 * 4 * 30)

[CR] = 0.03689 or 3.7%

**CALCULATION AMENDED TO REMOVE 15% PROFIT**

Allowing for 20% for fluctuations in token price and era points a commission of 4.8% is calculated.  There aren't any validators in the active set with a commission of 4.8%, however those that have 5% offer a return of 17.77% on a total-stake of 4,798.2177 KSM.  The total stake in question is nPoS normalized and should represent the 'general stake'.

I do confess that larger operators would enjoy better returns due to economies of scale but I present the above for general consideration.  I also note that while the token price is set at $256.00 the present price is $170.00.  

I also understand that it is technically possible to submit a proposal to forcefully adjust the commission of validators.  While this sounds a bit excessive it might be an good accompaniment to ensure an even playing field.

Regards,
Will | Paradox



On-chain Minimum Commission - Discussions before launch

Dear community, 

[Fifty-six](https://kusama.polkassembly.io/referendum/176) days have passed since the on-chain minimum commission was set at 3%.  There was an [involved discussion](https://kusama.polkassembly.io/post/1306) leading up to the public vote with some posts raising possible concerns, while others only saw benefits.

Now that sufficient time has elapsed I am reengaging the community to gauge feedback.  Validators, has a minimum commission provided you with desired results?  Nominators, are your returns still in fair good measure? Has the footprint of validators changed to any great extent?

Please share your views and don't be limited to the questions above.



Minimum Commission - Follow up

Good day,
In the aftermath of referendum 238 (Suggesting an increase of the minimum commission), I would like to open the floor for a discussion on the broader topic of staking rates on the Kusama network.
The voting data obtained from <a href="../proposal/108">referendum 238</a> served a greater purpose. It demonstrated that there is legitimate interest on the topic of staking rates and the sustainability of operations for independent validators.
While I agree that increasing the minimum commission is not an absolute answer to the problem; there was a majority (61% by weight) who wished to steer the chain in this direction.
Voting results (by number) To share some brief highlights of information captured within 6 hrs of the votes' end. The results are:
<ul>
<li>411 (27%) Validators, 338 (23%) Nominators and 749 (50%) undefined (neither) participated in the vote.</li>
</ul>
With percentages respective to the total vote:
<ul>
<li>311 (23%) Validators, 124 (8%) Nominators and 474 (32%) of the undefined voted AYE</li>
<li>72 (5%) Validators, 214 (14%) Nominators and 275 (18%) of the undefined voted NAY</li>
</ul>
Interesting facts
<ul>
<li>40 (55.5%) of the 72 validators who voted against the referendum maintains a commission that is &gt; 8.5%</li>
<li>180 (84%) of the 214 nominators who voted against the referendum nominate a validator with a commission &gt; 8.5%</li>
</ul>
It is also quite interesting that there are a number of voters who vote against things like upgrading the chain's runtime.
Of the 71 accounts that voted against Kusama's runtime upgrade (referendum 239), 70 of them participated in referendum 238. From the 70, 1 voted AYE and 69 voted NAY.
If it becomes necessary I would like to produce the data by weight at the last block of the vote. Unfortunately my queries used derive functions which doesn't play well with <code>.at</code>.
&nbsp;
State of staking rates
Amidst the discussion with referendum 238, I didn't get a sense that many appreciated the overarching state of staking rates and what the chain is (or may) be trying to achieve.
The chain's <a href="https://wiki.polkadot.network/docs/learn-staking-advanced#inflation">inflation rate is constant</a> but the amount that is distributed to the treasury and to staking is determinant on the ideal staking rate. Simply put, what doesn't go to staking goes to the treasury.
I would like to identify two out of the three zones; less than ideal and greater than ideal.
When the chain is less than ideally staked it generally encourages staking by increasing staking rewards with each bond added. When it is staked greater than ideal it discourages staking by reducing staking rewards.
In my opinion, the first zone (less than ideal) seems to encourage staking so that the chain can attain high levels of security (backing), this is all good! The second zone seems to discourage staking to encourage other utilization of tokens, perhaps for crowdloans?
We are currently in the second zone and staking rewards have dropped almost by half when compared to the ideal. It should encourage persons to remove their stake but this effect isn't yet seen.
The differential of staking rewards is also going to the treasury which is already quite full. There is also the effect of a squeeze on smaller validator's returns via commission and sustainability of their operations. This is enhanced due to current market conditions.
&nbsp;
Suggestions
I agree that fluctuations of market prices make it difficult to set an absolute 'best' commission level. I do however, believe there is value to looking at staking levels.
Perhaps when the treasury is full and we are above the ideal staking level we could:
<ol>
<li>Reduce the amount that goes to the treasury</li>
<li>Increase in the 'effective commission' which is the current minimum + an increasing amount x.</li>
</ol>
This would imo allow a flexible means by which funds could be transferred to validators during times when generally staking rewards would diminish.
Adam suggested:
<ul>
<li>burned treasury funds get allocated to validators who earned points during that spending period (First suggested by bLd)</li>
<li>minimum required block tip on all transactions, 'merica style 🇺🇸</li>
<li>treasury-subsidized programs that actively pay validators (e.g. TVP gets a quarterly grant to compensate its participants, nominator pools receive grants to actively pay the validators they nominate)</li>
</ul>
Also suggested
<ul>
<li>It was also suggested that as an intermediary step a lower rate of commission be proposed.</li>
<li>Generally there are concerns that if the commission rate goes up then it may never lower.</li>
</ul>
To note with the last point that it is possible for us to schedule a decrease (return to 3%) as part of a batch.
&nbsp;
Independent Validators within the 1KV
In light of the decreased rewards on chain and market conditions, the 1KV allowed an increase of commission by 50% . This has helped shield members of the programme as they can now operate at 15% commission without any risk of not being elected into the active set.
I believe that the rationale behind the decision to increase the maximum commission has merit outside of the 1KV. I am a proud member of the 1KV but I was discouraged to hear some members vote Nay because they're not affected.

Kusama Staking Rates - A discussion in the aftermath of referendum 238

Hello all,

There are two active discussions relating to [validator](https://kusama.polkassembly.io/post/1899)and [collator](https://forum.polkadot.network/t/economic-model-for-system-para-collators/1010/23) economics.  I would like to engage the community in discussion on the topic of what's fair compensation for each role. 

Ultimately I would like to use this information as the basis for requesting funding under a bounty mechanism as described [here](https://kusama.polkassembly.io/post/1899).  The [last discussion](https://kusama.polkassembly.io/post/1306) on the topic of validator compensation was started in January as we tried to establish an initial value for the minimum commission.  

The value determined at the time was $680/mth.  Since then, cost for hosting has increased, our options for reliable hosts have decreased.  Conversely, I believe we can reduce operation man hours.  The market has changed and we need to reasonably conserve on spending as well.

I am suggesting that we each post our thoughts on pricing using the template below:

Validator costs:

- Cost for a bare-metal server from a reliable vendor. - [reference host, cost]
- Number of man hours for upgrades - [hrs, rate]
- Fractional share for tooling, this includes for Grafana, PagerDuty and the like - [cost]
- Backup node, [yes/no], [if yes include cost]

Collator costs:

- Cost for a bare-metal server from a reliable vendor. - [reference host, cost]
- Number of man hours for upgrades - [hrs, rate]
- Fractional share for tooling, this includes for Grafana, PagerDuty and the like - [cost]
- Compensation for loss of staking rewards [yes/no]

With your submissions please consider that the operational demands and responsibilities of a validator is higher than that of a collator.  

Kind Regards,




Validator / Collator - Operational Costs

Hi All,

Two referenda were opened to test the use of batch calls as applied to Open Gov treasury spends.  The first was [referenda 58](https://kusama.polkassembly.io/referenda/58), this was issued on the Big Tipper track which has a spend limit of 33 KSM. The referendum tested two individual spends (8 & 2 KSM) both of which were within the maximum spend of the track and whose total spend was also within the tracks limits.  The second was [referenda 62](https://kusama.polkassembly.io/referenda/62), this was executed on the Small Tipper track which has a spend limit of 8 KSM.  This referendum was tested using two individual spends each within the maximum limit of the track (8 KSM) and with a total (8+8 KSM) exceeding the track's limit.

Both referenda passed and parties received funding.  The passing of these referenda provides us with some information:


**The good**

We (the community) now have added flexibility in the way that we can propose spends.  
   - We can for instance, proportion tips with a finder's fee
   - Group spends together to save on preimage and deposit fees *
   - Use this as a mechanism to directly allocate project funding to the respective major parties

\* - There is an approval risk when grouping spend proposals together. 

**The cautious**
With the good comes some caution, as seen with referendum 62 we can circumvent the total spend limits of a track, there by achieving the benefits of quicker approval times with lower thresholds.  

I believe that the good outweighs the bad and that the community can be that deciding factor whether referenda like 62 are allowed to pass or rejected due to perceived abuse.  It might also be a candidate for a bug fix.  What do you think?

I thank you all for participating in this test, thought it was not exhaustive the information was imo useful.

Regards,





Testing batch calls within OpenGov Treasury Spend tracks.

Dear community,
 
I am engaging you for feedback on a proposal to `Establish a framework for System Collators`. In addition to presenting the framework, the proposal seeks `1,709.34 KSM` to fund a bounty to incentivise collators on the Statemine chain for the period of 6 months. 
 
The document was already presented to current System Collators as well as Joe (W3F) and Zoltan (Encointer) to their satisfaction.
 

**Summary:**

>A System Parachain (S.C.) is defined as any Parachain which attained its lease via governance. This proposal aims to establish a framework for Collators on System Parachains to minimise censorship, maintain liveliness and incentivise efficient performance. 
> 
> It attempts to achieve this by suggesting parameters for the selection, incentivisation and the ideal number of Collators on System Parachains. It is also anticipated that this framework would form a standard that would aid future System Parachains as they are deployed. 
> 
> As a medium term solution, 1,709.34 KSM is requested to fund a bounty to incentivise Collators on the Statemine network for six (6) months. This would be used as a pilot test and re-evaluated before further funding is provided.

 

**Full proposal**

The full proposal can be accessed [here](https://docs.google.com/document/d/1H2T1Nx90HkSAYF_CaOPLG-o3LS7h_QAa2WLDdcSJMs0/edit?usp=sharing). 

 

**Discussion Time frame**

The floor is opened for feedback for the next 1 -2 weeks after which we would submit an on-chain request to fund the bounty and a later request to assign curators.

 
 
**Note:** KSM requested in sections 6.4 and 6.5 are time sensitive and would require recalculation before actual on chain submission.
 
Regards, 
Will | Paradox

System Collators Bounty - Requesting funding for a 6 month pilot.

Dear community,

I am presenting to you [a proposal](https://docs.google.com/document/d/1us8glHDEaXeqNp0Ex8Z5sffy4GTfhrvHzGNzNvp-juw/edit?usp=sharing) which seeks to fund a database analytic and RPC monitoring project for a period of 12 months.  The estimated schedule spans the period of 01-June to 14-September-2023 and would be executed by the three team members of the ParaNodes team. 


The proposal seeks to address three gaps of public knowledge:

1. Database sizing & growth rates
2. Database restoration times
3. RPC (WSS) Endpoint monitoring


To achieve these objectives additional hardware is required and I have presented two options for its procurement.  The first suggests rental of servers for the duration of the project, whereas the second suggests purchase of hardware with a lifespan of 5 years.  Future costs are lower selecting option 2 and any 'discarded' hardware would be donated to a charitable cause.   At present rates, the all in cost for **option 1 is 2,725.45 KSM** whereas the all in cost for **option 2 is 3,005.15 KSM**, both costs contain fees for slippage and are measured against an EMA7 of $32.817/KSM.


Full details can be found in [the proposal document](https://docs.google.com/document/d/1us8glHDEaXeqNp0Ex8Z5sffy4GTfhrvHzGNzNvp-juw/edit?usp=sharing).  


### Summary of Objectives 1 & 2


At the core of any Polkadot/Kusama node is a database, the database has multiple types and configurations.  The project seeks to expand on all useful combination of database types and configurations and monitor its  current size and growth rates. The knowledge is useful to validators, collators, RPC providers, developers, researchers or anyone who intends to roll-out or maintain a Polkadot node.  The information can be useful to prevent unexpected disk consumption or guide new builders with adequate sizing of disks.  The collected data would be presented on the ParaNodes.io website as well as on the Polkadot Wiki.  This project was initiated ~16 months ago, at launch it received welcoming feedback with suggestions to chart data and present growth rates. 

### Summary of Objective 3
Secondly, I wish to establish a system to monitor the availability, performance and consistency of public RPC endpoints on Kusama and Polkadot.  This should provide benefit to end-users and RPC providers themselves.  At present, the treasury is the primary financier of public RPC endpoints for which funds are provided based on self-evaluations, this system intends to provide a third-party evaluation of said services to further guide funding.


Regards,

Will | Paradox






Treasury Proposal - Funding for development of Database Analytics and RPC Endpoint monitoring

0x50617261646f782773205363686564756c6572205465737420426f756e7479

This bounty is primarily designed to fund Collators on System Parachains with a fixed fiat monthly fee of US$300.00.  

Full details on the genesis of this bounty can be found [here](https://docs.google.com/document/d/1H2T1Nx90HkSAYF_CaOPLG-o3LS7h_QAa2WLDdcSJMs0/edit)

Details on monthly spends can be found [here](https://docs.google.com/spreadsheets/d/1XWGigL0t0FQI9fL4I3Wg_W9wgXV4fXYrmn6Bo2eRv9A/edit#gid=329443407)

System Parachains Collator Bounty

Hey All,

During a recent discussion with Polkachu he mentioned that he required some help to pay for his [public payout bot (Payout Guard)](https://polkachu.com/payout_guard).  He operates this service on behalf of the community and has self-funded it for most of its existence. I would like to lend him a show of support with a tip of 10 KSM which funds ~ 6 months of service.

I hope the community shares the sentiment.

Regards,
Paradox

6mths funding for Polkachu's Payout Bot

Dear community,

**Summary:**  This proposal seeks to test the Treasurer's origin in its ability to cancel bounties and slash tips.  The bounties are SPAM and the tipping system is no longer receiving the attention of the Council.  If these actions are successful I am seeking a payout of 32 KSM (8 KSM per item) for use with my public staking rewards payout bot.

**Details:** The Treasurer track has been used to primarily fund recipients using `treasury.spend()`; it has also been used to fund and assign curators to bounties.  I would like to further test its ability to close two SPAMMY bounties entitled "[Catching #KSM Scams And Buying And Burning Rug Nfts](https://kusama.subscan.io/bounty/17)" and "[Help Bring The Ruggables Real Governance](https://kusama.subscan.io/bounty/18)".  I would also like to test use of an extrinsic that hasn't been used often, `tip.slashTip()`, this extrinsic removes a tip and slashes the user's deposit (0.033 KSM x 2) returning it to the treasury.  These are items of house keeping and it is best administered by the public in an open and collective manner.

As a reward, I am proposing a payout of 32 KSM (8KSM x 4) made payable to an account used by my public KSM staking rewards payout bot.  Rewards are divided into two independent branches, 16 KSM if both bounties are indeed closed and another possible 16 KSM if both tips are slashed.  If neither extrinsic is successful then no reward would be issued.

Regards,

Testing Treasurer Track - Close Bounties & Slashing Tips

Dear Community,

I am proposing this tip with multiple goals, in brief they are:

1. To provide a reward to Adam (8 KSM)
2. To test the use of batch statements to issue rewards
3. Fund [an account](https://kusama.subscan.io/account/Gch4VxQ79WhjgQqHomvJbqF3Woza5g5cYgM8SVQdDb9szz1?tab=extrinsic) used for public validator payouts as a `finder's fee` (2 KSM)

The main recipient of funding from this tip is Adam Steebar for compiling and maintaining [details related to Open Governance](https://docs.google.com/spreadsheets/d/1DHgjfaV0bvYVlsQswEM0EltuYnpYl7GJdg24H-sFpiM/edit#gid=663805148) with recent runtime releases.  He has also engaged in discussion on github relating to same [here ](https://github.com/paritytech/polkadot/pull/6398)and [here](https://github.com/paritytech/polkadot/pull/6409).  Despite the outcome I appreciate that he applied his Economics skill set to aid the community.

Additionally, I am taking an opportunity to test batch calls for issuing tips.  In the previous governance model the system required a single primary recipient of tip funding, this test allows for a split of tips among different parties.  If this executes successfully it establishes a model for future payments requiring such action.

Finally, I am directing 20% of this 'Tip' to an account used by a public staking reward payout bot.  This fee is the equivalent of the now debunked finder's fee of the old governance while awarding the recipient the maximum of what would have been a small tip.  

I look forward to a successful test.

Regards,






For analysis of Open Gov parameters 

Dear council,
I have opened a tip for a community member who mistakenly sent <a href="https://kusama.subscan.io/extrinsic/14260416-7" target="_blank" rel="noopener">8 KSM directly to nomination pool 58</a> instead of using using the NominationPools.Bond_Extra extrinsic.&nbsp; By this action and given that no one holds the private key for the destination account; the user is now unable to access funds. Considering the experimental nature of the network and the fairly low token value I would like to reimburse the community member.&nbsp;&nbsp;
In support of the request please find references below
<ul>
<li>All transferred funds to the <a href="https://kusama.subscan.io/account/F3opxRbN5ZavB4LTn2K51eNErsqJkWgkh3DqekS2HWmTd8G">pool's stash address</a> = 204 KSM</li>
<li>Pool's <a href="https://kusama.subscan.io/nomination_pool/58">total bonded</a> = 196 KSM</li>
</ul>
There is some discussion on the topic as a <a href="https://github.com/paritytech/substrate/issues/12308">git issue</a> with input from both Kian and Rob.
Regards,

To aid a community member who lost 8 KSM by mistakenly sending funds directly to a nomination pool stash address

I am proposing a tip to Kauly for an article on setting up a substrate based node on Raspberry Pi 3b or any that use the aarch64 processor.

The Raspberry Pi is a relatively inexpensive computing device that comsumes very little power, it is a suitable device to operate a peer node that occupies a low-power foot print.



For writing an article on running a node on Rasp Pi (aarch64)

Dear community,

I am proposing a tip for Alice und Bob (AuB) to reward him for providing the community with factual information regarding the Acala [aUSD/iBTC](https://twitter.com/AcalaNetwork/status/1558785360670298112) incident.  This incident impacted the perspective of the ecosystem; it was reassuring to see community members with a better understanding quell misinformation using a knowledge first approach.

AuB held a Twitter space in which he answered community based questions and he also posted a fairly concise [twitter thread](https://twitter.com/alice_und_bob/status/1558959878475075584) with salient points.

Alice und Bob was not asked to do this nor did he expect any reward, this is imo an organic use of the tipping system.

Regards,

For analysis and community support during the aUSD event - Hosted Twitter Space, Posted Analysis

Dear community,

I am recommending a tip to Vegas_life_main aka Ccris for supporting efficient operations of the 1KV by identifying a list of participants that became stale.  He defined stale by individually reviewing accounts based on last activity, last binary version, number of faults and last online parameters.

The PR with the list of users may be found [here](https://github.com/w3f/1k-validators-be/pull/1909) and his analysis document can be found [here](https://docs.google.com/spreadsheets/d/1DUmAfl9GpwIGfVzcpH16OrrBSL65IAfgAmPdiAZ6Da4/edit?usp=sharing)

Regards,
Will | Paradox

For supporting efficient operations of the 1KV backend

This is a tip whose proposer address (J11Rp4mjz3vRb2DL51HqRGRjhuEQRyXgtuFskebXb8zMZ9s) is shown in on-chain info below. Only this user can edit this description and the title. If you own this account, login and tell us more about your proposal.

Dear council,

I am proposing a tip to Kami (@nick1979:matrix.org) for a very clever modification of the Polkadot.JS browser extension entitled [Polkadot.JS+](https://github.com/Nick-1979/polkadot-Js-Plus-extension).  The extension offers additional functionality in the areas of transfers, crowdloans, account management and staking.  

Details on the extension's functionality are best obtained [here](https://github.com/Nick-1979/polkadot-Js-Plus-extension/wiki/How-To's) and for ease a few photos are found below:

![](https://github.com/Nick-1979/polkadot-Js-Plus-extension/raw/master/packages/extension-plus/docs/screenshots/accountsPage00.PNG)

![](https://github.com/Nick-1979/polkadot-Js-Plus-extension/raw/master/packages/extension-plus/docs/screenshots/transferFunds00.PNG)

![](https://github.com/Nick-1979/polkadot-Js-Plus-extension/raw/master/packages/extension-plus/docs/screenshots/nominatedValidators00.PNG)

The project's source is open and the recipients address can be verified the bottom of the [repo](https://github.com/Nick-1979/polkadot-Js-Plus-extension).  





Tip for a modified version of the Polkadot.JS extension that provides additional features for transfers and staking.

Dear Council,

I wish to propose a tip for Frazzled, a 1KV candidate for the development of a Twitter bot that alerts users of new Polkadot Binary builds including release candidates. This is particularly useful as a pre-alert to upcoming final releases.

Frazzle's address can be verified within the profile section of the twitter account.

Regards,
Will | Paradox

Polkadot Binary alert Twitter Bot

Dear Council,

I wish to propose a tip to Thousand Validator participant Tugy (Amforc) for [parasnaps.io](https://parasnaps.io/).  This project provides database snapshots for pruned validators databases for Polkadot and Kusama.  Snapshots are provided for both Parity and RocksDB database variants for either of the aforementioned chains.

Tugy's implementation innovates over other snapshot sites in the following ways:

1. He has provided multiple download locations including servers in the East and West of USA, West and Eastern Europe and one in Asia.

This is useful for redundancy and faster downloads depending on the region in which the request originates.

2. Instructions for multiple modes of implementation.

In this case he provides three (3) modes of implementation, the first by shell script, the second by manual download, extract, run and the third via ansible script.

This is a useful addition and somewhat a step-up to existing resources.  The receiver's address can be verified via the footer of the site in reference.

Regards,
Will | Paradox

https://parasnaps.io/ a multi-region snapshot project for Polkadot and Kusama

This is a tip whose proposer address (HqRcfhH8VXMhuCk5JXe28WMgDDuW9MVDVNofe1nnTcefVZn) is shown in on-chain info below. Only this user can edit this description and the title. If you own this account, login and tell us more about your proposal.

Dear council,

I am proposing this tip to CSaint for collating and presenting ecosystem related news and events for the period January 8th - February 12th 2022.   Each weekly newsletter is extremely detailed with sections for organized reading.  The Speed Reading section is quite useful just to capture the main points.

1. [The Glimmer of Moonbeam](https://app.subsocial.network/6111/the-glimmer-of-moonbeam-january-8th-15th-30779)
2. [Astar is Born](https://app.subsocial.network/6111/astar-is-born-january-16th-22nd-30995)
3. [Connecting the Dots](https://app.subsocial.network/6111/connecting-the-do-ts-january-23rd-29th-31139)
4. [Ulitmate Trust](https://app.subsocial.network/6111/ultimate-trust-january-30th-february-5th-31287)
5. [An Efficient Acala](https://app.subsocial.network/6111/an-efficient-acala-february-6th-february-12th-31416)

CSaint ends the newsletter with two interesting sections, Rumours & Alpha and an Opinions.  These sections provides uniqueness to the product and lends some insight to what might be an alternative view.  This newsletter is a testimony of the good work that WagMedia is producing to provide awareness of events occurring in the ecosystem.

The authors tip address is found to the bottom of each article.

**EDIT:** Please note that it was brought to my attention that the first three of these items were [already tipped for 4 KSM ](https://kusama.polkassembly.io/tip/0x25313a2d70d9d3271266bee257e2077f4fa5785ccccaad9fa105ef9edd753d73).  I have informed the council via the direction channel.

Kind Regards,

For 2 weekly Polkadot ecosystem recaps covering Jan 30 - Feb 12 -> https://app.subsocial.network/6111

In this video Alice und Bob suggests three items that if improved would aid with the growth of the ecosystem.  The high level items are:

- Bridges & Channels
- Explorers
- Wallets & UX

For each of the items presented, he explains his why he believes there is a 'bottleneck' and what can, or is being done to address them.  Within his closing remarks he encourages builders and community members to focus effort on these areas for the common good of the ecosystem.



For http://y2u.be/3VF1vJO4qpM - A video that shares a constructive opinion of three growth limiting factors for DOTSAMA

Dear Council,

This tip is proposed to Vegas_Life also known as @ccris02:matrix.org on Matrix.  He has produced a well documented [Grafana dashboard](https://github.com/ccris02/1kvDASH) to capture and report on metrics associated with the scoring of person in the Thousand Validator Programme.

Grafana is a tool used by many if not most of the operators to monitor their validators.  The accessibility of such scoring information is useful as it helps validators align to the rules of the programme which in turn aligns them to become better validators and community members.



For https://github.com/ccris02/1kvDASH - A Grafana Dashboard with pertinent data for members of the 1KV 

Dear Council,

I am absolutely pleased to present to you an amazing [open sourced](https://github.com/helikon-labs/chainviz) visualization tool by Helikon.  At present the visualization shows block production by the respective validator.  Stats are available for each validator by name search or by clicking the respective node on the visual.

I've engaged Kutsal (of Helikon) with respect to implementing more visual cues that could alert validators or nominators as to bad behavior e.g. not earning any era points when actively Paravalidating or not sending action leading up to an offline event.  The possibilities are quite extensive and I'm happy to have it as an addition to the ecosystem.

Kutsal has indicated that he will place the recipient address to the Readme file of git repo as confirmation of ownership.

W O W 

For https://alpha.chainviz.app/ - A visualization tool of the Kusama network

Dear council,

Please find compilation of videos by Jay Chrawnna in support of promoting, discussing or highlighting major events within the Polkadot/Kusama ecosystem. This tip covers fifteen videos delivered by Jay between January 3rd to 21st, 2022 prior to his Treasury Spend approval. It is expected to be the final tip of this nature.

In keeping with the rates approved in the Treasury spend proposal, I suggest that the tip is endorsed for **47.325 KSM**.  This equates to 15 Videos @ $625 + 1 Interview @ $90 using $200/KSM.

**Note**, With the Treasury Proposal approved it is my intention to donate the finders fee equally to the PoKu Charity fund and the PolkaHaus treasury to aid with their initiatives examples of which can be found in the two links provided [link 1](https://twitter.com/PoKuPeople/status/1471560828482572293) [link 2](https://twitter.com/PolkaHaus/status/1487160604011810817).

15 Episodes of SER, Have ya’ Heard?

**1. Monday Jan 3 (3:13)**
- Covering the Robonomics Trajectory, Composable's year of non-stop shipping, SubDAO's extension, Kabocha's funding secured, Bonding on ROME, PhalaWorld Ch. 1.1 and Gavin Wood's 2021 roundup.
-[https://youtu.be/aZh7qZ7pxsM](https://youtu.be/aZh7qZ7pxsM)


**2. Tuesday Jan 4 (4:47)**
- Covering $HDX, $TEER, $CRAB, The Njordson Report by #RMRK, Moonsama, NeonCrisis, and 12 Days of Shibits.
-[https://youtu.be/3UpHMLdxABA](https://youtu.be/3UpHMLdxABA)


**3. Wednesday Jan 5 (4:43)**
- Covering the token channel to Statemine, $KILT’s Polemic plans, xc20 tokens on $MOVR, $CGF’s RWA, HKO token transfers and their incentivized testnet, $CRAB’s Kusama rewards,
$MGX coming in February, 3 early $SUB, $ROME stacking $gOHM, Landsales on Moonsama, Fat contracts on $PHA and a taste of the future.
-[https://youtu.be/dbZwIofcMgY](https://youtu.be/dbZwIofcMgY)


**4. Thursday Jan 6 (5:51)**
- Covering Crustfiles, $EFI, $CRAB and EvolutionLand, Changes on Singular, The Kanaria Question, Update on $ZTG, Oxbrainjar speaks, and Subsocial looks for a new name.
-[https://youtu.be/eklrpfLimFE](https://youtu.be/eklrpfLimFE)


**5. Friday Jan 7 (4:23)**
- Covering $GLMR’s epic launch, xc tokens soon, $ROME's strategy, Moonsama musings, $CRAB's bonuses, long live Subsocial, and some energetic news from the bottom of the globe. 
-[https://youtu.be/MBJAw75Q6Xs](https://youtu.be/MBJAw75Q6Xs)


**6. Monday Jan 10 (5:11) - feat. The work of Singular artist Shiba Tales**
- Covering $CRU, $TAI event update, $GLMR sale and staking, Staking $CLV, Some NFT news, and the Kusamarian Shibit.
-[http://youtu.be/Mzs0sSaFv4w](http://youtu.be/Mzs0sSaFv4w)


**7. Tuesday Jan 11 (5:54) - feat. Seppy & Musician Birb Tapes**
- Covering the launch of $GLMR, $CRU distribution, $RMRK on $KAR, Yuri Gone Wild, Evolution Land updates, Moonsama on Moonbeam, $ZTG codes, $MGX futures, Seppy & the Birb Tapes.
-[https://youtu.be/MSUGQk-LEN8](https://youtu.be/MSUGQk-LEN8)


**8. Wednesday Jan 12 (3:36)**
- Covering rise of $HDX, Pleb tears, $LAYR + $GLMR, Moonsama's new Trailer, What is HRMP? New 1000k program and a package arrives in the mail.
-[https://youtu.be/5YKU25uxB6I](https://youtu.be/5YKU25uxB6I)


**9. Thursday Jan 13 (5:10) - feat. The work of Singular artist Dave Ramico**
- Covering astounding $PICA news feat. $PBLO & $KAOS, $xcKSM, and Solarflare on $GLMR, Polkadot 2.0, $SORA for a slot, $RMRK’s new DAO, and Trippen thru Singular w/ Dave Ramico.
-[https://youtu.be/Tx8Rw7lN3mg](https://youtu.be/Tx8Rw7lN3mg)


**10. Friday Jan 14 (4:42)**
- Covering Moonsama S1 and the Multiverse Bridge, $ROME’s GameFi and Battle plan, Dr. Preposterous, $BRIBE’s $AAVE pool, Yoo's $xcKSM revelation, and $PARA keeping in time.
-[https://youtu.be/Tx8Rw7lN3mg](https://youtu.be/Tx8Rw7lN3mg)


**11. Monday Jan 17 (5:12)**
- Covering $ASTR’s launch, $PICA's new $PBLO DEX and partnership with $RMRK, the Infinity Triangle, Integritee lands a slot, $BNC's new channel, and more waggin’ content.
-[https://youtu.be/slOfXzN277Y](https://youtu.be/slOfXzN277Y)


**12. Tuesday Jan 18 (4:15)**
- Covering $ASTR Stake2Earn, $ACA reward rollout, Moonsama continues to Bloom, $ROME strategy guide, $VARCH on the radar and bonobo of an interruption.
-[https://youtu.be/bUqlB-3pWaA](https://youtu.be/bUqlB-3pWaA)


**13. Wednesday Jan 19 (18:09) - Interview with M. Bulb (Rich) from Decent Partners (Edgeware)**
- Covering, $CHAOS at Composable, Gavin Wood hiring, Moonsama item skins, $PHA's new game, and a whole new perspective w/ Monsierbulb.
-[https://youtu.be/EFoMBLPSQqE](https://youtu.be/EFoMBLPSQqE)


**14. Thursday Jan 20 (3:59)**
- Covering $RMRK gone wild and bonuses on $KAR, $ACA’s 3,3 scheme, $ASTR Dapp staking, Talisman Phase II, and an uncomfortable absence of news about Composable.
-[https://youtu.be/_J5dmJX6IgQ](https://youtu.be/_J5dmJX6IgQ)


**15. Monday Jan 21 (6:45)**
- Covering new faces on the boards, $GENS distribution, the seeds of $KAB, $SUB's new feed, $VARCH banners, the $MGX play book, and $18m. 
-[https://youtu.be/0tWHpFJATD0](https://youtu.be/0tWHpFJATD0)

I do hope the following meets the council with good favour:

Regards, Will | Paradox

Final Tip for 15 SER, Have ya’ Heard? videos delivered between Jan 3-21

Dear Council,

I wish to propose a tip to James Sangalli for development of [https://james-sangalli.github.io/dot-staking-income-web/](https://james-sangalli.github.io/dot-staking-income-web/) an open source web app that allows users to generate their staking rewards in CSV format.

The tool is very light weight i.e. loads and operates quickly and is [opened sourced](https://github.com/James-Sangalli/dot-staking-income-web).  I do hope the council finds it as useful as I have and justly rewards the referenced independent developer.

The recipients address can be associated with the subject material via his addresses listed at the base of the Readme.md file on the github repo.

For https://james-sangalli.github.io/dot-staking-income-web/ - A light weight tool to extract staking rewards and export to CSV

Dear Council,

I am proud to present to you, a tip request for Paulo aka Turboflakes for an extremely well packaged[ open-source tool](https://github.com/turboflakes/scouty) for use by the community entitled Scouty.  Scouty is built using Rust and enables users to execute scripts based on on-chain events.  It can also send contextual info to matrix channels which adds a level of convenience for users on the go.

Possible use cases as presented are:

1. To get notified about on-chain events triggered by certain operations linked to Session, Staking, ImOnline and Democracy pallets.

2. To monitor, intercept and extend functionality as soon as on-chain events are emitted.
 
3. To get access to on-chain data and customize messages written by you delivered to a matrix private room.
 
4. To warm up or cool down your validator node resources by knowing when it goes active or inactive within one session.
 
5. To monitor 1KV nominations and trigger special kudos when your validator becomes independent :)
 
6. To keep up with Referenda and vote from your favourite site - Polkadot.js, Polkassembly, Commonwealth - through a direct link.
 
7. To trigger node backups every other era and publish them online.
 
8. To write your own bash scripts and hook them up to any on-chain event supported by scouty.

I am genuinely very pleased with Turbo's work, he continues to present products with excellent documentation, branding and of course valid use-cases.  I do hope the council would be generous in their tipping and share my views of how awesome this product is.

Regards,
Will | Paradox 

For Scouty, a Rust based tool that executes scripts based on on-chain events

Dear council, 

Please find compilation of videos by Jay Chrawnna in support of promoting, discussing or highlighting major events within the Polkadot/Kusama ecosystem.  To better organize and present his work, I will be compiling a single tip for his work every few weeks.  Jay is preparing a Treasury proposal so I anticipate that such tips would not be necessary in the near future.

It is my humble suggestion that the council endorse the tip at **23.75 KSM** which translates to 1.25 KSM / video.  This should aid Jay to recoup expended funds for production and to aid as a bridge until his Treasury proposal is completed.

**Note, it is my intention to refund Jay any funds I earn as the proposer of the tip.**

I do hope the following meets the council with good favour:

Polkadot/Kusama what the FAQ?

**1. Sunday Dec 19 - “Finders and Tips” (7:13)**

- Complete walkthrough of treasury tipping functions as well as best practices for reporting 
awesome content to the council including providing context, verifying tip address, 
approaching creators, and using Polkassembly + Bonus PDF for those who wish to 
create
- [https://www.youtube.com/watch?v=JN3YcTv0aRM&list=PLtyd7v_I7PGkrOymjT8HwD-_x9VP8Tads&index=20](https://www.youtube.com/watch?v=JN3YcTv0aRM&list=PLtyd7v_I7PGkrOymjT8HwD-_x9VP8Tads&index=20)


Ser, have ya' heard 

**1. Monday Dec 6 (13:34) - Interview with Subsocial (Alex & Beef)**

- Covering Composable's bid for Polkadot and how to get ANGL tokens early, KILT's 
referendum, Karura's Statemine connection, Altair's RMRK bonus and and interview with 
the guys from Subsocial!
- [https://youtu.be/ymBUcE2iQ2M2](https://youtu.be/ymBUcE2iQ2M2)

**2. Thursday Dec. 3 (2:53 min)**

- Covering LBPs, a Basilisk testnet?, Kabocha's crowdloan debate, child-bounties, the 
return of Integritee, and deep Bruno leaks.
- [https://youtu.be/UKaWQ0DUcPY](https://youtu.be/UKaWQ0DUcPY)

**3. Wednesday Dec 8 (16:45) - Interview with Talisman (Alex)**
- Covering the RMRK hackathon, Composable's new NFT magic, OriginTrail's new 
advisor, an awesome interview with Agile from Talisman, and announcing the FOUR 
Spirit Key NFT Winners!

- [https://youtu.be/JsBjvnUGwb0](https://youtu.be/JsBjvnUGwb0)

**4. Thursday Dec 9 (14:21) - Interview with Apes ’n’ Art (Moon-Bearer)**

-Covering the next common good chain, Parity's #AdsforChads campaign, New 
delegating rules on Moonriver, Instrumental's LBP wrap up, and an interview with Apes 
'n' Art creator, MoonB!
- [https://youtu.be/FsQgWOfcXmM](https://youtu.be/FsQgWOfcXmM)

**5. Friday Dec 10 (4:08)**

- Covering Integritee reward boost, new entries in the crowdloans, Manta's Dolphin net, 
and Kanaria Skybreach.

- [https://youtu.be/t3yW3Dqq_HU](https://youtu.be/t3yW3Dqq_HU)

**6. Monday Dec 13 (11:38) - Interview with Zeitgeist (Logan Saether)**

-  Covering Parachain RMRK drops, DEEEP Kanaria conspiracies, and a RMRK 
integration with Edgware, @Gojo_Crypto's nifty crowdloan review, other Reward 
updates, and a tell all victory interview with @logansaether from Zeitgeist.
- [https://youtu.be/gM3rOJ49Phs](https://youtu.be/gM3rOJ49Phs)

**7. Tuesday Dec 14 (14:12) - Interview with Polka Häus (Alex & 0xTaylor)**

- Covering $STRM staking, crowdloan chaos, reward updates for Equalibrium and Interlay 
PLUS Centrifuge and Composable waiting in the wings. We finish with an excellent 
interview with the guys at Polka Häus and another unfortunate instalment of Big Oof. 
- [https://youtu.be/gWPE8W1HIoo](https://youtu.be/gWPE8W1HIoo)

**8. Wednesday Dec 15 (3:41)**

- Covering the Polkadot rebrand and Feliz Navi-DOT competition, Clover's terminated 
Web3 grant, Composable's crowdloan and plans for Kusama treasury, PhalaWorld, Last 
call for GLMR addresses, and about 5 invites to the WagMedia discord.
- [https://youtu.be/Z3oCYP-ackY](https://youtu.be/Z3oCYP-ackY)

**9. Thursday Dec 16 (4:07)**

- DeFi! Covering Clover's imminent double win, Genshiro's Farm Fest extension, Kintsugi 
reward claim, Centrifuge's stategy shift, Mangata after $10M, Phala considering a run on 
DOT, RMRK's Yuletide festival, and the new project from Composable Labs.
- [https://youtu.be/I_X81sciyEg](https://youtu.be/I_X81sciyEg)

**10. Friday Dec 17 (4:37)**

-Covering the Talisman Alpha build, Bribe Protocol, Shakeup on the DOT board with 
some new parachain strategies. Kintsugi goes Decentralized, Moonbeam's $1M bounty, 
SORA's RMRK partnership, and Mangata's Solarpunk Challenge.
- [https://youtu.be/UkppxXBqIyg](https://youtu.be/UkppxXBqIyg)

**11. Monday Dec 20 (17:12) - Interview with Parallel (Yubo)**

-Covering the Polkadot Party, Moonbeams lightning launch, the DOT boards batch 2, 
Composable's $5000 competition, and #unbrickpicasso; Substrapunk raffle, Claiming 
$QTZ and $KINT and an exclusive interview with Yubo Ruan from Parallel.
- [https://youtu.be/RFo4NiEu6wc](https://youtu.be/RFo4NiEu6wc)

**12. Tuesday Dec 21 (3:34)**

-Covering Energy Web's Relay Chain, Kabocha's got plans too, Clover/Sakura 
roadmaps, decentralized calamari, the Snek speaks, and hints and Mangata's 
tokenomics
- [https://youtu.be/ahzE4g4qG70](https://youtu.be/ahzE4g4qG70)

**13. Wednesday Dec 22 (16:50) - Interview with Robonomics (Vitaly)**

-Covering the RMRK Yuletide festival, http://Bit.Country's token & land giveaway, 
Mangata's crowdloan plans, Karura's special announcement, Origin Trail's newest 
continental partnership, and a sweet interview with @vitl2907 of Robonomics
- [https://youtu.be/n33PTyiiyhI](https://youtu.be/n33PTyiiyhI)

**14. Thursday Dec 23 (18:05) - Interview with RMRK (Bruno)**

-Covering Efinity's DOT board dominance, but Composable's new reward plan and 
$10,000 hackathon; Equilibrium's reward lottery, Karura's new Taiga protocol, Subsocial 
handing out banners, Robonomics RMRK integration and Bruno in the studio.
- [https://youtu.be/1MXMmnMskcw](https://youtu.be/1MXMmnMskcw)

**15. Monday Dec 27 (3:32)**

-Covering the Crust victory, Phala's auction bid, OriginTrail V6, Telekom becoming a 
validator, Kabocha making progress, KINT on sale, Instrumental's Q1, http://Bit.Country's 
strange retweet, Kanaria leaks, and the new Moonsama collection.
- [https://youtu.be/ZoFDlYWItM0](https://youtu.be/ZoFDlYWItM0)

**16. Tuesday Dec 28 (4:15)**

-First Kusama lease is nearly over! Taiga's half million rewards and the state of Karura, 
Kintsugi bonus, the BRIBE token, HydraDX launching a crowdloan, and some 
mysterious news on NFTs.
- [https://youtu.be/vWGaTP_tugE](https://youtu.be/vWGaTP_tugE)

**17. Wednesday Dec 29 (4:42)**

-The return of OOOON THEE RADAAAR feat. the Pontem project, Centrifuge's RWA on 
Aave, ROME's first campaign, and Kanaria on Moonsama?
- [https://youtu.be/EZaV_qYzvaI](https://youtu.be/EZaV_qYzvaI)

**18. Thursday Dec 30 (8:16) - NFT Artist Spotlight (Mad Rabbit)**

-Covering the Efinity win, Bribe’s LBP, HDX’s new two token design, Crust for DOT and 
Darwinia back to KSM. http://Sub.ID gets stronger, Donnie sleeps on ROME, and we're 
TRIPPEN thru Singular on Mad Rabbit's Most Offensive Art Collection
- [https://youtu.be/snGea4rTRUk](https://youtu.be/snGea4rTRUk)


Regards,
Will | Paradox












For videos from Dec 6th - 30th which includes 18 'Ser have you heard' videos and 1 educational video on the 'Tipping system'

Dear Council,

I wish to propose a tip to Jim at CertHum for an[ innovative tool ](https://certhum.com/maps/kusama/) that displays the location of ~~active~~ Kusama validators on a global map.  The tool uses peer data from multiple nodes to determine which of them are ~~active ~~validators and retrieves their IP addresses.  With the IP addresses he is able to ascertain their geographic location and plot it on a global map. 

This is a ground up approach to determining validator locations directly from the source as compared to others that use data from third party sources such as Telemetry. 

The tools is particularly useful to get a birds eye picture of the geographic decentralization of Kusama's active validators.  Jim has promised to deliver the Polkadot variant Soon.

The recipient's identity can be verified via https://certhum.com/about-us/ or by inspection of the recipient's verified identity.


Regards,
Will | Paradox

For - https://certhum.com/maps/kusama/ - A tool that displays live geographic location of active Kusama nodes.

Dear council, 

Please find compilation of videos by Jay Chrawnna in support of promoting, discussing or highlighting major events within the Polkadot/Kusama ecosystem.  To better organize and present his work, I will be compiling a single tip for his work every two weeks.  Jay has estimated that a tip of 1 KSM (at current market average) per applicable video would aid with covering his expenses and provide fair compensation for his efforts.

**Note, it is my intention to refund Jay any funds I earn as the proposer of the tip.**

I do hope the following meets the council with good favour:

Ser, have ya' heard 

**1. Friday Dec. 4 - (10.47 min)**

- Zeitgeist opens their crowdloan. Composable introduces Arturo Finance. Genshro’ s Farm Fest, an intro to Darwinia. Bonus interview w/ Sota Watanabe re: Astar’ s winning bid.
- [https://www.youtube.com/watch?v=8trHCb76SIg](https://www.youtube.com/watch?v=8trHCb76SIg)

**2. Thursday Dec. 3 (2:53 min)**

- Interlay’ s crowdloan plan, SORA ’ s as well an an intro on that project. Subsocial’ s monthly review and a peak at Altair’ s NFT Studio.
- [https://www.youtube.com/watch?v=1EKPtIFEclQ](https://www.youtube.com/watch?v=1EKPtIFEclQ)

**3. Wednesday . Dec. 2 (3:54 min)**
- Deep dive into Talisman. Giving away a Key on twitter to those who describe the spirit of
Kusama in gif. How to cast vote re: Encointer. Deep dive on Edgeware treasury proposals.
Chainlink on Moonriver.
- [https://www.youtube.com/watch?v=g2osOvAyJRQ](https://www.youtube.com/watch?v=g2osOvAyJRQ)

**4. Tuesday , Dec. 1 (3:41 min)**

- Deep dive into Encointer and the process of common good. SherpaX crowdloan update,
Genshiro Megaboost winners announced and a look at a recap of OriginTrail’ s Twitter Space by _i_o_t_b
- [https://www.youtube.com/watch?v=71yrKuVdbdo](https://www.youtube.com/watch?v=71yrKuVdbdo)

**5. Monday , Nov . 30 (15:23 min)**

- Dive into Composable’s Instrumental Finance, Calamari Token Claim, HDX tripling wallets.  Bonus interview w/ JAM re: treasuries and the metaverse.

- [https://youtu.be/B0Fex0fSYkQ](https://youtu.be/B0Fex0fSYkQ)

**6. Friday , Nov . 26 (16:28 min)**

- Zeitgeist Beta results, Calamari token distribution, KILT leaks, and Bit.Country’ s Demo
presentation.  Bonus interview w/ Derek Yoo re: Moonbeam’ s slot 2 win.
- [https://www.youtube.com/watch?v=GF6AYuWhdig](https://www.youtube.com/watch?v=GF6AYuWhdig)

**7. Thursday , Nov . 26 (2:52 min)**

- GLMR Rewards address switching, OriginTrail’ s NFT Supercharger , and a deep dive into
Composable’ s Whirlpool.
- [https://www.youtube.com/watch?v=j0NBcKZQEvY](https://www.youtube.com/watch?v=j0NBcKZQEvY)

Space Monkey Interviews

**1. Chat with Sota and Maarten from Astar (43:04 min)**

- Talked motivations to build, the potential of wasm and the road to get there.
- [https://youtu.be/sO6aQOgNnSE](https://youtu.be/sO6aQOgNnSE)

**2. Conversation with Logan, Hutch, and David from the Zeitgeist team (45:15 min)**

- Futarchy concepts, applications; community response to the Beta, and the future of
governance.
- [https://youtu.be/4sv_1v-kZTI](https://youtu.be/4sv_1v-kZTI)

Regards,
Will | Paradox












Compilation - 7 x Ser, have ya' heard videos + 2 x Space Monkey videos

Dear Council,

Abdulbee (an ambassador candidate) has been working on an alternative site for listing jobs within Polkadot / Kusama ecosystem.  The website is functionally complete and is available at [https://www.polkajobs.io/](https://www.polkajobs.io/), it is also supported by a telegram channel found [here](http://t.me/polkajobs).  Abdulbee intends to maintain the site as a free repository for any person/institution to post job listings.  In our discussions he has expressed that he has reached out to 20 projects to ask for their assistance with posting jobs and over the next few days he will be reaching out to more.

In support of his initiative he has compiled a fairly [comprehensive document](https://drive.google.com/file/d/1ug2Po0fYaj5t8ZpMyStL2SULe2NL_PkC/view?usp=sharing) that explains the goals of the project.

Abdulbee's address can be confirmed and associated with the project just above the site's footer.  I hope the council sees this project with good favour and as an alternative option to other similar sites in the ecosystem.

Regards,

Will | Paradox


https://www.polkajobs.io/

Dear Council,

I wish to propose a Jobo_Chao for developing an innovative [network diagram ](https://kusama.d3sjfzcxgz1xj9.amplifyapp.com/) which shows the social relationships between NFT projects on Kusama.  It achieves this by retrieving data on NFT projects from major NFT marketplaces and correlates it to data from Twitter such as tweets, retweets, mentions and quotes.

The network diagram is such that projects found closer to the middle are those that are more intertwined with NFT socialites.  Users may search for a particular project or search for their own Twitter handle to view a filtered scope of their influence within the NFT community.

For a video description/demo, please see mention by Jay Chrawnna here:[ https://youtu.be/jPAwEDvOrOw?t=86]( https://youtu.be/jPAwEDvOrOw?t=86)

The recipients address can be verified by matching twitter addresses on his verified identity within the 'More about this visualization' section of the page.

Regards,

Kusama NFT community visualization tool

Dear Council,

I wish to propose this tip to Abdulbee (an ambassador candidate) for an article he authored entitled ['a systematic guide to exploring substrate'](https://thiscoindaily.com/a-systematic-guide-to-exploring-substrate/).  

The article records Abdulbee's personal journey with understanding and building with substrate.  Within the article he identifies possible hindrances and how he overcame them, he also references other resources that helped him through his journey.

Abdulbee's receiver address can be verified at the end of the article

Regards,



For an article on understanding and building with substrate

Dear Council,

I would like to present to you an educational video authored by Jay Chrawnna on Multi-Signature accounts. Jay covers most of the salient points wrt Multi-signature accounts in this 5 minute video which includes setup, use-cases and a practical example.

Polkadot's account system is very well thought out and I hope to see more videos exploring its features.

Kind Regards,

For an educational video on Multi Signature Accounts

Dear Council,

I would like to present to you an educational video authored by Jay Chrawnna on Multi-Signature accounts.  Jay covers most of the salient points wrt Multi-signature accounts in this 5 minute video which includes setup, use-cases and a practical example.

Polkadot's account system is very well thought out and I hope to see more videos exploring its features.

Kind Regards,




For a quick video on Multi Signature Accounts

Dear Council members,

This tip is being proposed to N4DR0 whose identity can be verified as the author of the subjected project [here](https://github.com/Nadro-J/py-subalert#roadmap).  The project received a tip in July which can be reviewed on [DoTreasury ](https://www.dotreasury.com/ksm/tips/8302412_0x5eeccea3083e0c4c5f5a1280b03c70fabc5297ae51de4ab9fc0de629bb04c315) and [Polkassembly](https://kusama.polkassembly.io/tip/0x5eeccea3083e0c4c5f5a1280b03c70fabc5297ae51de4ab9fc0de629bb04c315).  

This tip is being proposed for the following additional features:

- Era report (Plot a graph over 84 Eras for visual representation of nominated stake whilst showing the difference bonded/unbonded in the last 24hrs)

![https://imgur.com/XO5bkOr](https://i.imgur.com/XO5bkOr.png)
- PhragmenElection council votes  (Notify when a user has voted for a member of council. Off the back of this, a custom solution was built to do more detailed alerting by checking if Twitters character limitation was met and if so, to turn the alert into a .png file and attach it as a tweet.)

![https://i.imgur.com/Ea6IRLZ](https://i.imgur.com/Ea6IRLZ.png)
- Alert when a new tip has been proposed/closed successfully, giving exposure to new content/tools to those that might not check polkadot.js daily.

![https://imgur.com/dWunJKc](https://imgur.com/dWunJKc.png)

![https://imgur.com/aLmCp9I](https://imgur.com/aLmCp9I.png)

N4DR0 spends time outside outside of his regular working hours to maintain the site and address any bugs. 
 He spends further development time working on new features in keeping with the project's roadmap.  This project was also affected by the release of Metadata v14 and N4DR0 spent considerable amounts of time to address any issues to keep the service online and accurate.

He covers all expenses on his own and has devised a strategy of using staking rewards from the receiving account to offset costs.  

I am hopeful that the council would be generous to support this project and support his goal of sustainability.

Kind Regards,

Will | Paradox



Additional work on Twitter bots @PolkadotTxs and @KusamaTxs

Dear Council,

I will like to propose a tip to [https://talkpolkadot.com/ ](https://talkpolkadot.com/) a recently launched media site dedicated to sharing information on Polkadot related, projects, technology, media and events.  This site is developed (in partnership) by GrizzlyAdams[3/75]#4892 aka Judge a community-moderator on Polkadot's Discord server.

The site itself references TalkPolkadot's own resources on YouTube, as well as resources on Twitter, Reddit and Discord.

Their YouTube channel has four (4) videos published which includes:

1. What is Polkadot? - [https://www.youtube.com/watch?v=92rZIjCrIfc](https://www.youtube.com/watch?v=92rZIjCrIfc)
2. Let's Talk Polkadot! - [https://www.youtube.com/watch?v=DfAAf6a0Uw0](https://www.youtube.com/watch?v=DfAAf6a0Uw0)
3. DOTScribe: Polkadot Parachain Crowdloans - [https://www.youtube.com/watch?v=rab_seD3VkU](https://www.youtube.com/watch?v=rab_seD3VkU)
4. Why Polkadot? - [https://www.youtube.com/watch?v=I-GcedEsSzc](https://www.youtube.com/watch?v=I-GcedEsSzc)

The address for the receiver can be verified here at the link below: [https://talkpolkadot.com/about/#contact](https://talkpolkadot.com/about/#contact) it references one of the two hosts.  I have asked the other host to login with a PA linked account to acknowledge the tip.

Best Regards,



For https://talkpolkadot.com/ a website and community hub to showcase Polakdot and Kusama major events and technology.

Dear Council,

I wish to propose a tip to [Parachains.info](https://parachains.info) for their informative website relating to Parachains. This website has become a staple resource within the ecosystem for everything Parachain related.  

Parachains.info takes a multifaceted approach to representing ecosystem data and events by use of custom charts, tables and graphs.  Their site is one that I use personally and recommend to others seeking a single repository of info relating to Parachain projects.

Most recently, their graphical representation of auction timing (seen below) was very helpful in explaining the dynamics of a candle auction and the slim margin by which a lower-bidding parachain won an auction.

![](https://github.com/paradox-tt/Images/blob/main/Parachains.png?raw=true)

The receiving address can be verified here: [https://parachains.info/contact_us](https://parachains.info/contact_us)

I now leave the floor open to Vladimir the Lead Developer of Parachains.info to provide further information.

Regards,
Will | Paradox


Parachains.info - An extremely informative website regarding Parachain projects

Polka-store is a Node.js program written in typescript which scans a Polkadot chain (Polkadot/Kusama/Westend) and stores (hopefully all) balance-relevant transactions in a SQLite database. This database can be used in other projects to easily access the transaction data. What is balance-relevant? 

Currently the following data will be collected:

- Balance transfers (directly and through reserved balance)
- Fees
- Staking rewards
- Staking slashes
- Additionally to the balance-relevant transaction data, also changes in bonded amounts are stored.

The source for the solution is available at [https://github.com/TheGoldenEye/polka-store](https://github.com/TheGoldenEye/polka-store) and Goldeneye's credentials are included on the Readme.md.

Regards,



 A tool to track balance and bonding related transactions.

Dear council,

I would like to propose a tip for VisionStake's medium article found at the link below:

- [https://visionstake.medium.com/how-to-staking-and-select-the-best-polkadot-or-kusama-validators-b772757dd1b0](https://visionstake.medium.com/how-to-staking-and-select-the-best-polkadot-or-kusama-validators-b772757dd1b0)

The article covers all the salient aspects of nomination and delves further by discussing good selection criteria.

VisionStake's id can be associated with the article at the end "Kusama Node 1".

Regards,

For a medium article on nominating and selection criteria for good validators 

Dear Council,

I wish to propose a tip to Polkachu.com for the development of [Scout](https://polkachu.com/scout) a validator lookup tool.  The tool provides nominators with a very fast (cached) lookup for validators that is network independent.  

Some highlighted benefits over other similar systems are:

- The returns are calculated on actual returns over a 90 day window which is an improvement over others that uses estimates based on commission and total stake.  
- It also allows a validator to view the actual nominations of particular nominees.
- There are charts that remove W3F nomination information which may skew results due to its large bond
 
Of particular interest is **Effective Nominators Stake**.  As a validator it is particularly difficult to gauge how much stake is required to be elected into the active set.  This is because the total stake that is visible is nominated stake that must be applied through Phragmen before an active stake can be determined.

Scout attempts to estimate the Effective Nominators Stake by dividing a nominators bond by their component nominations and then summing this figure together.  While this is not an exact approach it gives validators some bearing.

This is certainly a tool I will reference often and I hope the community by large will also benefit from its use.

Regards,
Paradox




For a Validator lookup tool with a few notable features

Dear Council,

I wish to propose a tip to James Sangalli for the development of an open sourced JavaScript module to aid with the selection of validators using input criteria:

- Identity (is verified)
- Commission (within input threshold)
- Validator is not oversubscribed
- Has an acceptable own stake (within input threshold)
- Unique entities i.e. this won't select more than 1 of each type e.g. 1 Zug capital but not 10 Zug capital entities
- Has never been slashed

The repository for the module is available [here ](https://github.com/James-Sangalli/dot-validator-selector) and can also be used to verify the receivers address.  James has also put together a demo site that uses the module that is accessible [here](https://james-sangalli.github.io/dot-validator-selector/).

It is my belief that his initiative is well aligned to support the desired traits of a 'good nominator'.

Best regards,

For a JS module to aid developers and nominators select validators based on input criteria

Dear Council,

I wish to propose a tip to James Agenda whose identity can be verified and associated with the material [here](https://www.holdpolkadot.com/james-agenda).

In this [subjected article](https://www.holdpolkadot.com/post/3-best-ways-on-how-to-participate-in-parachains-auctions-on-polkadot-via-crowdloans) James takes a pro/con approach to comparing three (3) common ways to participate in crowdloans:

1. Via an exchange
2. Using the Project's website
3. Using the Crowdloan module

The article also features some info-graphics of his own creation:

![](https://static.wixstatic.com/media/9aee63_29e7e57b0bb04516ae22a0b151ad8537~mv2.jpg)

![](https://static.wixstatic.com/media/9aee63_be2ec09cc5a640adb7a9fe0d891028c4~mv2.jpg)

Comparison of crowdloan participation methods

Dear Council,

I will like to propose a tip for Martin Jensen for his efforts to develop a web based application to display all chillable nominators on the Polkadot network and provide a mechanism to easily chill (other) them.  At present while the ChillOther extrinsic is permission less many less technical nominators don't know how to find a chillable nominator and thereafter how to chill them.  This application helps simplify the process and reduces reliance on Parity/W3F to issue mass chills when limits are reached.

The application is available [here](https://martinloesethjensen.github.io/dotsama-chill/) and the source code is publicly available [here](https://github.com/martinloesethjensen/dotsama-chill).  The receiver's (Martin's) tip address is found to the base of the readme of the git repo.

![](https://cdn.discordapp.com/attachments/880077073081851904/883090011342381096/Screenshot_2021-09-02_at_22.44.19.png)

The application is stateless and takes a while to load the nominator map.  I have suggested use of [https://elara.patract.io/](https://elara.patract.io/) which should provide a reasonable boost in load time.  Martin also has some ideas that he's currently working on which include:

- Statistics overview:
    - Minimum nominator bond
    - Nominators 
    - Max nominators
    - Chill threshold
    - Chillable amount 
    - Era info
- Identicon on addresses
- Success dialog with block hash and link to subscan
- Error dialog when trying to chill
- Loading states:
    - Loading of nominators below threshold
    - Loading of transaction 
- Empty state (when no nominators can be chilled)

I do hope the council sees it fit to reward Martin for his efforts.

Kind Regards,
Will | Paradox



Development of a web app to display and ChillOther any applicable nominators on Polkadot

Dear Council,

I am proposing this tip to Jay Chrawnna for a video that describes the roles and responsibilities of the council, how the election system works and finally a walkthrough on how to select a council member.  His particular presentation style keeps the attention of the audience with pop-culture references and a well articulated tone.

It is in my opinion that governance is a highly under appreciated aspect of the ecosystem and specifically that many don't understand the duties of the council.  I will also extend my position as to say that many don't know about the voting process and that they can vote with bonded funds.

With this said I hope that Jay's video will aid community members to appreciate all points related to the council and gain their interest in governance by large.

Regards,

An educational video on the roles and responsibilities of the Council and how to elect same.

Dear Council,

I wish to propose a tip for Gr33nHatt3R whose reddit profile can be view [here ](https://www.reddit.com/user/Gr33nHatt3R/), his profile references his Kusama address used within this tip.

His input in the reddit community is invaluable as he aids users with support issues and helps them understand fundamental changes to the ecosystem.  In addition to his role in frontline support he is also responsible for managing the "Mod Queue" of the server.  The "Mod Queue" is a list of flagged posts requiring individual action and in such a large community this queue can be extensive.  While there are other moderators for the community his performance stands out. 

I have recently joined the r/DOT moderation team and I have personally seen his efforts.  Greenhatter has expressed that he has never received any reward either via tip or by the W3F and executes his job out of love for the community.

It is in my opinion that he has contributed to the community positively and a tip will be a gesture of good will and acknowledgement for a job well done.

Kind Regards,

For moderation and great participating in r/DOT a community of 28,000+ members on Reddit

Dear Council,

I am proposing a tip to Ccriss (Discord/Riot) aka Vega_Life for compiling, presenting and hosting [https://polkadir.com/](https://polkadir.com/).  This website holds many resources relating to the ecosystem including those developed community members.  

Ccriss has developed this as a public resource but also a tool for use by the moderation team when directing users for further information.

Proof of ownership is established at the base of the webpage in which the receiver address is clearly stated.

Kind Regards,

For the development of https://polkadir.com/ ; A repository of content relating to many aspects of the ecoystem

Dear Council,

I am proposing this tip to James Agenda the proprietor of HoldPolkadot.com whose identities can be verified [here](https://www.holdpolkadot.com/james-agenda).  James is well known under his alias _-_agenda_-_ on reddit where he contributes to the various Polkadot and Kusama communities.

One of his major achievements is a [blog post](https://www.holdpolkadot.com/post/5-best-places-to-stake-polkadot) that compares five of the ecosystem's more popular staking options.  It has been the topic of much discussion:

- [https://www.reddit.com/r/Polkadot/comments/osmhjs/5_best_places_to_stake_polkadot_imho/](https://www.reddit.com/r/Polkadot/comments/osmhjs/5_best_places_to_stake_polkadot_imho/)

- [https://www.reddit.com/r/dot/comments/osmj3b/5_best_places_to_stake_polkadot_imho/](https://www.reddit.com/r/dot/comments/osmj3b/5_best_places_to_stake_polkadot_imho/)

- [https://www.reddit.com/r/Kusama/comments/osmjss/5_best_places_to_stake_polkadot_and_kusama_imho/](https://www.reddit.com/r/Kusama/comments/osmjss/5_best_places_to_stake_polkadot_and_kusama_imho/)

A key takeaway from the blog post is an infographic seen below:
![](https://static.wixstatic.com/media/9aee63_caea733085ce4ec3a21aff85a47010d5~mv2.jpg/v1/fill/w_1972,h_1268,al_c,q_90/9aee63_caea733085ce4ec3a21aff85a47010d5~mv2.webp)

James continues to interact with stakeholders to ensure the blog post remains relevant and he supports the respective reddit threads.  I see this as good material for new entrants to the community and I hope that the council shares my view.

Kind Regards, 




For holdpolkadot.com and for a well circulated blog post that compares staking options.

Good day Council,

I am proposing this tip to Turboflakes for the development of an open source staking payout application entitled [Crunch](https://github.com/turboflakes/crunch).  This application was developed in rust and is inspired by similar applications by [Stakelink](https://github.com/canontech/staking-payouts) and [CanonTech](https://github.com/canontech/staking-payouts). It innovates further by the addition of an optional Matrix bot to announce pay-outs.

Turbo has also done an excellent job in presenting the app with well illustrated documentation for installation and use.  I do hope you give good consideration to providing him with a tip for his contribution to the community.

Proof of ownership can be determined by visiting the github in which the receiver's address is listed.

Development of a Staking Payout application (in Rust) with an optional Matrix Bot to announce payouts

Dear Councillor, 

I am proposing this Tip to Vega_life aka ccris02 on Riot for developing a repo to store errors and other output displayed by the polkadot binary. He also provides an easy to understand description of the problem and recommended actions (if applicable).

Quite often validator operators would post queries on Riot relating to errors that they've noticed on their nodes.  Example:

> 2021-08-01 20:48:02 Fetching collation failed due to network error hash=0x40aae093c3a7983482487c1dab65caba9661336e9ae012f23d40ba39f656ecc0 para_id=Id(2007) peer_id=PeerId("12D3KooWFxLQp3BTc65R8RW7qeUQRg426N48se2sADWWFHSsriCb") err=Network(Timeout)

At times and in this particular case the error doesn't require any further action by the operator but this is only discovered after consultation.  

This repo aids node operators to search for the error that they're presented with and quickly discover the recommended action.  Others can also contribute as-to aid with the continued growth of the repository. 

Regards,

Development of a repository of polkadot error codes, their meaning and the action required by them.

Dear Council members,

This tip is proposed to nadroj#7528 (Discord) a member of the Polkadot and Kusama Discord community.  He has developed twitter bots [@PolkadotTxs](https://twitter.com/PolkadotTxs) and [@KusamaTxs](https://twitter.com/KusamaTxs) which provides tweets when on-chain referenda are added as well as when there are tagged releases for the Polkadot binaries.  

His current roadmap includes the addition of tweets for Proposals as well as Tips for each respective chain and he has made the source code available via github -> [https://github.com/Nadro-J/py-subalert](https://github.com/Nadro-J/py-subalert)

It is in my opinion that these bots provide additional visibility of on-chain activity as well as providing added visibility for new binary releases which I believe that the Parity team is trying to improve (based on recent questionnaires).  His future development especially in the area of tips would provide publicity for the good work produced by our community.

Kind Regards,








 Development of twitter bots that announce Polkadot Binary and Governance events updates

Dear Council,

This tip is being proposed to Certhum a member of the Thousand Validator Programme for providing public dashboards that display resource usage of their validator nodes on [Kusama ](https://stats.certhum.com/kusama-certhum-maxstake-v03) and [Polkadot](https://stats.certhum.com/polkadot-certhum-maxstake-v01).  

While provision of same has marketing potential it also provides other validators with a reference to compare their own performance against.  This is extremely useful when troubleshooting performance after recent updates or for validators to gauge their relative resource usage.  CertHum has confirmed this community benefit as one of their objectives in their [public release](https://medium.com/certhum/certhum-maxstake-stats-f1f0609b03da) notes:

> ...we ran into situations where we would see issues with our node but couldn’t be sure if it was our configuration, our hosting provider, or a wider issues with the chain. We would have loved to have seen a site like this where we could check the vitals of another *sic* node on the network.

I have further asked CertHum to include the specifications of the validator machines used, any CLI flags used, to display the version of the polkadot binary and to note that INACTIVE/ACTIVE is in context of being in the active set.  They have complied with the request and I believe that these additions would further aid in using the resource as a performance reference.

Best Regards,








Public dashboards of CertHum's validators resource usage

Dear Council/Readers,

I am proposing this tip to Alex Melikhov CEO of [Equilibrium](https://equilibrium.io/en) and its canary project [Genshiro](https://genshiro.equilibrium.io/en)  for a publication on [Coin Telegraph](https://cointelegraph.com/news/how-much-intrigue-is-behind-kusama-s-parachain-auctions).

The article provides a comprehensive analysis of crowdloan contribution statistics and presents the results together with visually appealing and informative charts.  The community benefit in my opinion is two fold, the article itself is quite an interesting read and the exposure of the publication sheds good light on the Kusama Project.

I would also like to take the opportunity to highlight that Alex's good work is testimony of the effort and detail that is put into the Genshiro and Equilibrium projects.  While we must all do our own research one would be wise to do some reading on these projects if you haven't done so already.

Regards,

For a detailed and well publicized report on crowdloan funding

This Tip is being proposed to Stakelink a fellow Thousand Validator member on Kusama.  He has developed a tool that can allow tasks to be executed based on substrate events an example of which is to execute staking reward payouts at the end of an era.  The convention at the moment is to execute a cron job every hour or 30 minutes to coincide with the end of an era.

This git repo can be found here: [https://github.com/stakelink/substrate-crond](https://github.com/stakelink/substrate-crond)

The developer has also mentioned that the tool can be extended based on any event found at [https://polkadot.js.org/docs/substrate/events](https://polkadot.js.org/docs/substrate/events) so those with specific use-cases can build upon it.

Regards,

For a cron like scheduler based on substrate events

Dear Council,

This tip is being proposed to user javascriptjhon (Jhon) on discord, who is also the developer of the popular tool [https://polkaview.network/dot/](https://polkaview.network/dot/).  This tool was frequently used to monitor the minimum dot stake in a graphical and easy to access manner with short load times.  

Jhon continues to provide the community with snapshots of relevant data using simple yet effective visual displays.  While Jhon continues work on the dashboard I believe that the information presented is relevant now and will be a bookmarked/pinned resource for many.

He has also been as kind as to share the source with the community for those who may wish to build on his work.

Git repo - [https://github.com/jhonalino/parachains.network](https://github.com/jhonalino/parachains.network)

Parachain Crowdloan Dashboard - https://www.parachains.network/

Dear Council,

A tip is proposed for Mirek for developing a dashboard for monitoring validator statistics which he has now shared with the wider community.

He has also compiled a list of resources (found on the same page) for his Czech compatriots that is of relevance to staking and the ecosystem by large.

By way of mention to this tip proposal I have advised Mirek that open source solutions are seen favorably by the council and the ecosystem.  I do hope this additional supporting information makes it way to you soon.

Website url - [https://polkadotstats.tech/](https://polkadotstats.tech/)

Tip for a staking tool by Czech Developer (Mirek) - https://polkadotstats.tech/

Dear Council, 

I am proposing this tip to Blockpane a fellow One Thousand Validator (1KV) participant.  He has developed a tool that retrieves data from the One Thousand Validator backend and translates it into an end point for the popular server monitoring software Prometheus.  Data in Prometheus can be translated into alerts or points for trending within accompanying software like Grafana.

The source code for the project can be found here: https://github.com/blockpane/1kv-exporter 

Community benefit:  

As part of the 1KV programme, validators are upheld to additional performance standards when compared to regular node operators.  Should any of these standards be infringed the validator would be deemed as 'invalid' and be exempt from w3f nomination.  Some of these metrics are found on-chain and some relate to connectivity to the w3f telemetry all of which are not natively accessible to local monitoring software like Prometheus.  

This solution provides node operators with a better opportunity to monitor these (additional) metrics and take action where discrepancies are noticed. 

For the development of a tool to export data from the 1KV backed to Prometheus 

Good day Council

This tip is being proposed for TurboFlakes a member of the Thousand Validator Programme.  He has developed a tool that provides a pick of validators based on a user adjustable weighting criteria.  It is anticipated that such a tool would be a beneficial support tool to the community when nominating validators.

The source for the application is available here: https://github.com/turboflakes

TurboFlakes - A validator selection tool with multicriteria adjustment

This tip is proposed for Kusama Go Lunar aka Cryptogolunar on riot.  He is a validator operator and a member of the Thousand Validator Programme (1KV).

One of the many responsibilities of a validator operator is to ensure that binaries are updated to the latest stable release within a reasonable period of time.  The 1KV programme has formalized this by placing timelines for updates based on release-priority.  This tool aids with ensuring compliance to the rules of the 1KV programme and overall good validator management.

The recipient has also made the source code available for others to review or build upon as needed.

Repo: https://github.com/ManifestDemocracy/polkaRelCheck



For the development of a script to auto-update the Polkadot binary upon a new stable release

Dear Council member,

I am proposing this tip to Gilbert Bassey otherwise known as gb#6438 on Polkadot's official discord.  Mr. Bassey is a Polkadot Ambassador and an avid supporter of decentralization.  In this article he compares Kusama's crowdloan module to public ICO's and emphasizes the measures implemented by Kusama to protect the funds of participants.

It is believed that this article would aid community members who have preconceived notions of crowdloans based on association with ICOs.

Best Regards

Tip Proposal - Article on Crowdloans as compared to ICOs

Dear community,
I'm submitting this proposal to cancel a "deferred" slash for era 7126 which would be applied in era 7154.&nbsp; The issue resulting in the slash was deemed to be<a href="https://github.com/paritytech/polkadot-sdk/issues/5778"> bug related</a> and the technical details are still being investigated.&nbsp; Historically, deferred slashes due to bugs were cancelled.
The issue, in my simple interpretation is as follows:
<ul>
<li>There was downtime due to hardware issues</li>
<li>Before the downtime one of my nodes was due to issue a "pre-vote"</li>
<li>When the node was online again, time passed and the prevote was no longer necessary.</li>
<li>The node may have used the local (not sync'd) finalized block as reference and proceeded to issue the pre-vote</li>
<li>Because the pre-vote already issued it resulted in an equivocation which is a slashable offence</li>
<li>Ideally, the node should have determined that time passed and the pre-vote wasn't necessary anymore</li>
</ul>
Given the circumstances and if my interpretation is correct this can happen to any operator who may restart their nodes with a pre-vote "in queue" given a delay in finalized blocks.
The issue was reported immediately but because of the bug, the "slash" was reported some 24 later. Time was also lost while trying to get a technical verdict on whether this was a bug or operator related. Given these delays, it is unlikely to receive a cancellation of the deferral on time. I would however engage the community for a deferral in solidarity.
I have already <a href="https://kusama.subscan.io/extrinsic/0x1721218fbc11aef01268df4b8cdae452a90287f4e0f300eeee8a0e9a9fffa1c4">compensated</a> the slashed parties (rounding up) and I am working on another payout for those affected by any offline time.
Kind Regards, Will | Paradox

Cancel Deferred Slash 7126 - Due to application bug

This was submitted with the era the slash took place.&nbsp; However, upon advice and further investigations this should be submitted with the era the slash is due to be enacted. Please vote nay and review the next referenda.

Cancel Deferred Slash - Era 7126 - Vote Nay

Dear community,
I present this proposal on the authorization of the curators of bounty 25.
This proposal seeks to continue funding of Public RPC Providers for the period of six months plus an additional month's contingency. Funding is issued to bounty 25 which awards vendors for RPC services on the Kusama relay-chain as well as its system parachains. The total cost for such provision is USD$107,237.98, which represents $12,397.21 per month without contingency and administrative fees.
Bounty 25 adopts an tender based procurement model in which service providers bid on requirements as set-out by the curators. The tender requirements are aligned to ecosystem needs and can scale up/down depending on usage. Tenders are scored and the highest scoring providers receive funding. Attention is also being placed on quality of service and should service providers fail to meet said quality-standards they will be penalized or lose funding altogether.
This approach has seen a reduction with independent funding proposals for such services and steering of providers to a "market rate".
Further details can be found <a href="https://docs.google.com/document/d/1WV7n5HVKtO5s0ub6g4uEQAN4Y7SRNcu56QYFXPgN15I/edit?tab=t.0">here</a>
Kind Regards, Will | Paradox | ParaNodes.io

Funding for Public RPC Providers via Bounty 25

Dear Community,

With the passing of [referendum 108](https://kusama.polkassembly.io/referenda/108), we would like to take the next step of assigning a Curator.  This was attempted as an experiment with referendum 108 but it failed, as such we're taking the normal two step approach. 

The proposed curators are:
 
- FrankyWild (frankywild#8573)
- Tim Jansen (Tim Janssen (Won't DM)#8682)
- Husni (pastaMan#9738)

The multi-sig will require 2/3 signatures and is configured as a pure-proxy.  These individuals are members of the Moderation and Anti-scam teams and also have experience with bounty curation. They have also met the requirements as described within section 5.2 of the [original proposal](https://docs.google.com/document/d/1H2T1Nx90HkSAYF_CaOPLG-o3LS7h_QAa2WLDdcSJMs0/edit?usp=sharing).

The team has already setup reporting templates which are available for community viewing [here](https://docs.google.com/spreadsheets/d/1XWGigL0t0FQI9fL4I3Wg_W9wgXV4fXYrmn6Bo2eRv9A/edit?usp=sharing).

Regards,

Assigning Curators for Bounty 20 (System Parachain Collators)

Dear community,
 
This proposal seeks to fund collators of the `Statemine` network for the duration of `6 months` as a pilot. If passed, a Collator will receive a `performance based`, fixed fiat reward of `USD$300.00` per month as well a one time `reimbursement` for work previously provided. The proposal document was presented to current System Collators as well as Joe (W3F) and Zoltan (Encointer) to their satisfaction.
 
Additionally, I am taking the opportunity to test assigning a Curator to the bounty within the same proposal as approving it. This is usually undertaken as a separate process because the bounty needs to be approved before it can be assigned a Curator. Let's see how this goes, no time would be lost due to this experiment. 
 
The Curators are namely:

- FrankyWild (`frankywild#8573`)
- Tim Jansen (`Tim Janssen (Won't DM)#8682`)
- Husni (`pastaMan#9738`)

These individuals are members of the Moderation and Anti-scam teams and also have experience with bounty curation. They have also met the requirements as described within section 5.2 of the proposal.

 

**Summary:**

>A System Parachain (S.C.) is defined as any Parachain which attained its lease via governance. This proposal aims to establish a framework for Collators on System Parachains to minimise censorship, maintain liveliness and incentivise efficient performance. 
> 
> It attempts to achieve this by suggesting parameters for the selection, incentivisation and the ideal number of Collators on System Parachains. It is also anticipated that this framework would form a standard that would aid future System Parachains as they are deployed. 
> 
> As a medium term solution, 1,873.69 KSM is requested to fund a bounty to incentivise Collators on the Statemine network for six (6) months. This would be used as a pilot test and re-evaluated before further funding is provided.

 

**Full proposal**

The full proposal can be accessed [here](https://docs.google.com/document/d/1H2T1Nx90HkSAYF_CaOPLG-o3LS7h_QAa2WLDdcSJMs0/edit?usp=sharing). 

 

**Discussion**

The proposal was left for [open discussion](https://kusama.polkassembly.io/post/2427) for a duration of two weeks and received only one item of feedback.


 
Regards, 
Will | Paradox

Establishing a bounty for Collators of System Parachains.

spend_local

Dear community,

This referendum seeks to test use of the scheduler on the Treasurer track by scheduling actions through the lifecycle of a bounty i.e. approving, funding, assigning a curator and closing.   

It is important to note that after a bounty is approved, it does not become funded until an independent spend period is completed.  On Kusama this spend period cycles every 6 days.  Only after the bounty is funded then a curator can be assigned, this required delay is the reason why approving a bounty and assigning a curator can not be successfully executed in one batch.

When the bounty is funded and if there is no major objection, I would like to disburse funds to `Gch4VxQ79WhjgQqHomvJbqF3Woza5g5cYgM8SVQdDb9szz1` which is used by a public validator payout bot as well as my clean up referendum deposits script for OpenGov and the Fellowship.  

Walk through:

Call data - `0x18020c2301681d048051010000ff23026800e8b2603f6baee5bc32a9b9e4eee9168499fa553d35edb56aef0035ff7e1f165e001d0440db020000ff230768`

The referendum batches three (3) extrinsics using batchAll, meaning that all three must execute successfully or the overall call would fail and all actions, successful or not would be rolled back.  The calls are:

1. bounty.approve(26) - This action approves bounty 26 which is the bounty in question with 25 KSM
2. schedule.ScheduleAfter - This schedules an action of assigning a curator (myself) after 86,400 blocks.  I took the inefficient but risk-free approach of delaying the call to the exact time frame of the spend period i.e. (6 days x 24 hrs x 60 mins x 60 sec)/ blocktime 6s
3. schedule.SchedulerAfter - This schedules closing the bounty after 14 days, this gives a 7 day window after assignment of a curator in which the bounty can be claimed (a 4 day wait in itself).

I hope this brief write-up helps others who may wish to avoid using two extrinsics to make use of their bounty.  Timings can also be adjusted to reduce the lag after the bounty is funded and curator assigned.  If you are using a tighter timeframe, I suggest you use schedule.schedule and target a block_height.

The floor is opened to questions or comments

Regards,
Will | Paradox | Builder of extrinsics




Proof of Concept - Using the Scheduler on the Treasurer Track

Dear Community,

I am proposing the closure of bounty 14 on Kusama as it is now replaced by [bounty 24](https://polkadot.polkassembly.io/bounty/24) on Polkadot.  The bounty originally funded the Moderation Team but the team has since moved their source of funding from Kusama to Polkadot.

The action of closing the bounty would return any remnant funds on the account to the treasury and remove the curator.  In this case the Curator was already removed.  This occurred because the curators did not extend their expiration date and it elapsed.  When such occurs it leaves the Curators open to a permission-less extrinsic to remove them.

Kind Regards,
Will | Paradox | Ecosystem Janitor

Closing Bounty 14 - Moderation Team Bounty

Bounty 24 was created as a test by the W3F Tech Ed team.  This referendum seeks to remove it as part of good chain housekeeping.

Cleanup on aisle 24 - Tech Ed test bounty

Dear community, This referendum falls under the purview of janitorial activites.&nbsp; It seeks to close bounty 23 which was submitted in error.&nbsp; The submitter is attempting to do so with <a href="266">referendum 266</a> but is using a track with the wrong origin.&nbsp;&nbsp; I am also taking the opportunity to close bounty 22 which was submitted by Bill 27 days ago with no affirmative movements since. Regards, Will | Paradox | RCJ (Relay-Chain Janitor).

To close erroneous and spam bounties

Dear community,

### **EDIT: The proposal now seeks $32,640.00 for RPC monitoring only.**

I am resubmitting [a proposal](https://docs.google.com/document/d/1us8glHDEaXeqNp0Ex8Z5sffy4GTfhrvHzGNzNvp-juw/edit?usp=sharing) for Monitoring of public RPC/WSS Endpoints & Node Database Analytics.  This proposal was previous submitted as [referendum 175](https://kusama.subsquare.io/referenda/referendum/175) but failed due to HANC's interference.

Unable to gauge his feedback, I have made the followings revisions:

- I am funding provision of servers for the DB Analytics/Restoration, this reduces the overall cost of the proposal by ~25%
- Reduce the slippage from 10% to 5% in light of a recent market correction

Do note that slippage as well as any excess KSM beyond the asking USD amount is refundable to the treasury.

The goals of the proposal remain the same:

- To become an independent monitor of all WSS providers, displaying key metrics in a visual manner (Dashboard)
- To monitor DB growth, sizes, bloat and restoration times for various DB configurations.

Kind Regards,



Monitoring of public RPC/WSS Endpoints

Dear community,

I present to you [a proposal](https://docs.google.com/document/d/1us8glHDEaXeqNp0Ex8Z5sffy4GTfhrvHzGNzNvp-juw/edit) which aims to develop a technical solution to: 

- Monitor and report on the uptime, performance and integrity of public WSS (RPC) relay-chain endpoints. The data could be used to guide funding of said services, to encourage a service standard or to provide existing providers with a second take on key metrics from a third-party.
- Monitor and trend database growth rates for twenty-four database configurations. This is something that I started and self-funded > 16 months ago. Upon launch it gained interest by technical parties and is now referenced within the Polkadot Wiki. I would like to expand on the project to include growth charts and offer a wider range of database configurations. Further to this, I intend to monitor the restoration times of some of the more popular database configurations.

Additional: Providing that the original scope is met, I'll consider monitoring of database bloat, trend average RAM or CPU usage as well as monitor availability and integrity of bootnodes.

Both major items are not found within any existing public resources and are in my opinion well aligned to Kusama's experimental nature. Full details including budget details can be found in [the proposal document](https://docs.google.com/document/d/1us8glHDEaXeqNp0Ex8Z5sffy4GTfhrvHzGNzNvp-juw/edit). This document was circulated to members of the 1KV/IBP for a week and was open for [public discussion](https://kusama.polkassembly.io/post/2546) for > 2 weeks.

 
Disclosure: As it relates to WSS monitoring, I am presently employed by LuckyFriday which as of last week is now listed as a public RPC provider. I also share good professional relationships with most of the RPC providers. The proposed solution is open sourced such that anyone can operate in-tandem and compare/challenge results. Once up and running these `audits` will be operated and presented without any human intervention. 
 

Kind Regards, 
Will | Paradox

Proposal for Monitoring of public RPC/WSS Endpoints & Node Database Analytics

Dear community,

This referendum was opened to test another aspect of OpenGov.  I can't divulge the specifics at this point in time as it would introduce a bias.  I can however say that the outcome of the vote is inconsequential.  

Even with that said I would prefer a successful outcome to continue funding the account used by a public staking payout bot.

For those not familiar with my previous test please view the details [here](https://kusama.polkassembly.io/post/2151).

Have fun voting.

Regards,

Open Governance Test

Dear community,

This referendum is two fold, it seeks to grant 0xTaylor a tip of 8 KSM but also tests OpenGov to see if it protects against spending more than the track allowance when using multiple transactions.  

0xTaylor is a popular actor within the ecosystem known for his input with security exploit related matters.  It is through his efforts that a blacklist was developed on Polkassembly, thus preventing users from applying usernames like `Admin` or `Administrator` which could otherwise be misleading.  He also reported `Hasura GQL endpoint` exploits to various teams that utilize the service, an example of which can be found [here](https://t.me/rmrkimpl/2717).  0xTaylor is also known for his input within the ChaosDAO and WagMedia communities members of which have endorsed his receipt of a tip.

On the note of security, I took this as an opportunity to test the coding of OpenGov with regards to multiple spends within a single batched transaction.  This proposal seeks to spend 16 KSM in two batches of 8 KSM. The first and 'guaranteed' execution being made to `0xTaylor`, in the unlikely event that there is a bug then another 8 KSM would be awarded to [an account](https://kusama.subscan.io/account/Gch4VxQ79WhjgQqHomvJbqF3Woza5g5cYgM8SVQdDb9szz1) for Public Kusama Staking Rewards Payout BOT.

If the second extrinsic executes then maximum spend per track would essentially be `Max spend` * `Number of transactions that can be fit within a batch`.  

Regards,
 