Origin able to spend around 250 DOT from the treasury at once.

small_tipper

The Ambassador Fellowship had a successful first phase, even with challenges. Volunteers helped the program meet its goals. The team was supposed to get a payment, but some board members left, making it hard to decide things. So, the money was given back to the main fund instead. Now, the program is still going and needs more money to keep growing. The team members who worked hard should get paid, and there's a list of how much each person should get. Thank you for supporting the Ambassador Fellowship.

Deciding

During the first funded phase of the Ambassador Fellowship, we achieved remarkable success — even amidst periods of uncertainty and transition. This success was largely thanks to the dedication of individuals who stepped up as volunteers to ensure we not only met but exceeded our deliverables within the agreed timeframe.

Per the agreement with the Advisory Board (see[ Sprint Overview Document](https://docs.google.com/document/d/1zc0WAzXezZSFryfZ-xlpLPt4xgouvl4mLamy60fO15k/edit?usp=drive_link)), a discretionary payment was to be made to the core team upon successful delivery by May 3, 2025. Through careful financial stewardship — managed solely by myself — $230,000 remained in the Ambassador Fellowship fund. The plan was to distribute $29,000 to the team, with the remaining $201,000 returned to the treasury when the Board stepped down (five weeks later than anticipated).

The delivery deadline was met, and the Advisory Board confirmed the work was completed successfully.

However, during this period, several Board members resigned due to the extended duration of their roles. With diminished capacity and activity, decision-making became increasingly difficult. Ultimately, the remaining funds — including the portion intended for the team — were returned in full to the treasury for administrative ease. As a result, the promised payments were not made.

Today, the Ambassador Fellowship remains active and is preparing a proposal for further funding to support its continued growth. Cohort Two is currently being seeded, and a waitlist for Cohort Three is already forming — a clear sign of the program's community value and continued success. You can find our[ Delivery Report here](https://drive.google.com/file/d/18WwkjxAzOe5SIbSICl5vcQ2ziAtnUCwe/view?usp=drive_link).

After careful consideration and consultation, I believe the fairest path forward is to submit individual compensation requests on behalf of each team member. These individuals fulfilled their commitments and contributed significantly to the Fellowship’s outcomes. The full list of team members and corresponding payment amounts can be found in this[ Spreadsheet](https://docs.google.com/spreadsheets/d/16J8qxv9-Z0ky35yRFn-OlkuxoRZt5s7XO75kwtsFSoQ/edit?gid=755697593#gid=755697593).

Thank you for your continued support of the team, the principle of fairness within the ecosystem, and the enduring impact of the Ambassador Fellowship.

Ambassador Fellowship: Sprint Team Tip Request - Leemo

The Ambassador Fellowship had a successful first phase, even with challenges. Volunteers helped the program meet its goals. The team was supposed to get a payment, but some board members left, making it hard to decide things. So, the money was given back to the treasury instead. Now, the program is still going and needs more funding. The team members did a good job, so they should get paid. There's a list of who should get paid and how much. Thank you for supporting the Ambassador Fellowship.

During the first funded phase of the Ambassador Fellowship, we achieved remarkable success — even amidst periods of uncertainty and transition. This success was largely thanks to the dedication of individuals who stepped up as volunteers to ensure we not only met but exceeded our deliverables within the agreed timeframe.

Per the agreement with the Advisory Board (see[ Sprint Overview Document](https://docs.google.com/document/d/1zc0WAzXezZSFryfZ-xlpLPt4xgouvl4mLamy60fO15k/edit?usp=drive_link)), a discretionary payment was to be made to the core team upon successful delivery by May 3, 2025. Through careful financial stewardship — managed solely by myself — $230,000 remained in the Ambassador Fellowship fund. The plan was to distribute $29,000 to the team, with the remaining $201,000 returned to the treasury when the Board stepped down (five weeks later than anticipated).

The delivery deadline was met, and the Advisory Board confirmed the work was completed successfully.

However, during this period, several Board members resigned due to the extended duration of their roles. With diminished capacity and activity, decision-making became increasingly difficult. Ultimately, the remaining funds — including the portion intended for the team — were returned in full to the treasury for administrative ease. As a result, the promised payments were not made.

Today, the Ambassador Fellowship remains active and is preparing a proposal for further funding to support its continued growth. Cohort Two is currently being seeded, and a waitlist for Cohort Three is already forming — a clear sign of the program's community value and continued success. You can find our[ Delivery Report here](https://drive.google.com/file/d/18WwkjxAzOe5SIbSICl5vcQ2ziAtnUCwe/view?usp=drive_link).

After careful consideration and consultation, I believe the fairest path forward is to submit individual compensation requests on behalf of each team member. These individuals fulfilled their commitments and contributed significantly to the Fellowship’s outcomes. The full list of team members and corresponding payment amounts can be found in this[ Spreadsheet](https://docs.google.com/spreadsheets/d/16J8qxv9-Z0ky35yRFn-OlkuxoRZt5s7XO75kwtsFSoQ/edit?gid=755697593#gid=755697593).

Thank you for your continued support of the team, the principle of fairness within the ecosystem, and the enduring impact of the Ambassador Fellowship.i

Ambassador Fellowship: Sprint Team Tip Request - Arash Torbati

Vote Nay - preimage not on chain. 

The Ambassador Fellowship had a successful first phase, even with challenges. The team did a great job and finished their work on time. They were supposed to get a payment, but some board members left, and the money was returned to the treasury instead. Now, the Ambassador Fellowship is still going and needs more funding. The person in charge thinks it's fair to ask for the team's payment again. You can find more information about the team and their work in the links provided. Thank you for supporting the Ambassador Fellowship.

During the first funded phase of the Ambassador Fellowship, we achieved remarkable success — even amidst periods of uncertainty and transition. This success was largely thanks to the dedication of individuals who stepped up as volunteers to ensure we not only met but exceeded our deliverables within the agreed timeframe.

Per the agreement with the Advisory Board (see[ Sprint Overview Document](https://docs.google.com/document/d/1zc0WAzXezZSFryfZ-xlpLPt4xgouvl4mLamy60fO15k/edit?usp=drive_link)), a discretionary payment was to be made to the core team upon successful delivery by May 3, 2025. Through careful financial stewardship — managed solely by myself — $230,000 remained in the Ambassador Fellowship fund. The plan was to distribute $29,000 to the team, with the remaining $201,000 returned to the treasury when the Board stepped down (five weeks later than anticipated).

The delivery deadline was met, and the Advisory Board confirmed the work was completed successfully.

However, during this period, several Board members resigned due to the extended duration of their roles. With diminished capacity and activity, decision-making became increasingly difficult. Ultimately, the remaining funds — including the portion intended for the team — were returned in full to the treasury for administrative ease. As a result, the promised payments were not made.

Today, the Ambassador Fellowship remains active and is preparing a proposal for further funding to support its continued growth. Cohort Two is currently being seeded, and a waitlist for Cohort Three is already forming — a clear sign of the program's community value and continued success. You can find our[ Delivery Report here](https://drive.google.com/file/d/18WwkjxAzOe5SIbSICl5vcQ2ziAtnUCwe/view?usp=drive_link).

After careful consideration and consultation, I believe the fairest path forward is to submit individual compensation requests on behalf of each team member. These individuals fulfilled their commitments and contributed significantly to the Fellowship’s outcomes. The full list of team members and corresponding payment amounts can be found in this[ Spreadsheet](https://docs.google.com/spreadsheets/d/16J8qxv9-Z0ky35yRFn-OlkuxoRZt5s7XO75kwtsFSoQ/edit?gid=755697593#gid=755697593).

Thank you for your continued support of the team, the principle of fairness within the ecosystem, and the enduring impact of the Ambassador Fellowship.

Ambassador Fellowship: Sprint Team Tip Request - Michelle

Ambassador Fellowship: Sprint Team Tip Request - Luke Schoen

Hello! I went to a big conference about blockchain technology at the University of Miami. I talked about something called tokenization and represented Polkadot. I didn't get paid for my time, so I'm asking the community if they think I should be. I usually charge $100 per hour for my work. I spent 5 hours on a campus tour, 8 hours at the conference, and half a day on Saturday. I'm asking for $1500 for my time. Thank you!

Executed

Hey, everyone!

As many of you are aware based on several social media posts, I was tapped by Chris Wade to help represent the Polkadot ecosystem at the University of Miami's 3rd annual "The Business of Blockchain Technology" Conference across three days. Here's where I spoke on a panel about tokenization:

POLKASSEMBLY WILL NOT UPLOAD IMAGES - WILL EDIT LATER

While I am grateful to the Events Bounty for covering my flight and my hotel costs, I have not been compensated for my time or other costs that were incurred by representing Polkadot (e.g. Uber rides to and from the airport). Moreover, considering this was not previously negotiated with the EB and they do not pay retroactively, I am hoping the community will agree that my time is valuable and that I worthy of compensation as an ad hoc / de facto part-time Polkadot Ambassador.

In my part time role with Ardent through my small business **blockACE**, I charge $100 per hour for my time. Although I spent well over 20 hours as a representative from our ecosystem, I am only asking to be paid for the time I directly interfaced with University of Miami staff or conference attendees. This included 5 hours during Thursday's campus tour, followed by a full 8 hour day for the first day of the conference, and a half day on Saturday.

I respectfully request $1500 (Polkadot gets the friends and family discount) for my time.

Gratefully,

Ryan / Phunky

P.S. - I will circle back later to add more photos and links.&#x20;

Compensation for Polkadot Representation at University of Miami's 3rd Annual Business of Blockchain Conference

This is a ReferendumV2 post. It can only be edited by the proposer of the post .

Untitled Post

Based on the work -> https://forum.polkadot.network/t/a-real-world-polkadot-wallet-drain-why-we-now-need/12934 I am proposing to tip Cyphertux for his swiftness and support&#x20;

TIP: Cyphertux's work on Wallet Drain co-ordination

A person named @subway2023 found 18 problems in a computer program called the Parity Technologies revive Solidity compiler. They told the people who work on the program about these problems over 3 months. These problems helped the program get better and fix some mistakes. The person in charge of the program thinks @subway2023 did a great job and wants to give them a reward of 100. You can see all the problems they found here: [link](https://github.com/paritytech/revive/issues?q=is%3Aissue%20author%3Asubway2023). And here is the place where they talked about giving the reward: [link](https://github.com/paritytech/revive/issues/253#issuecomment-2694530520).

Github user @subway2023 submitted 18 issues over the course of 3 months to the parityech revive Solidity compiler.

The issues submitted to us provide valuable early stage contributions to the project. Some of them lead to bug fixes in the revive compiler and the polkadot-sdk.

As the maintainer of the of the revive compiler I suggest to reward this contributor with 100.

Contributions: [https://github.com/paritytech/revive/issues?q=is%3Aissue%20author%3Asubway2023](https://github.com/paritytech/revive/issues?q=is%3Aissue%20author%3Asubway2023)

Account: [https://github.com/paritytech/revive/issues/253#issuecomment-2694530520](https://github.com/paritytech/revive/issues/253#issuecomment-2694530520)

Small Tip for subway2023

This is a tip created by the [tip-bot](https://github.com/paritytech/substrate-tip-bot/).

### Details

- **Repository:** [polkadot-sdk](https://github.com/paritytech/polkadot-sdk)
- **PR:** [#6905](https://github.com/paritytech/polkadot-sdk/pull/6905)
- **Contributor:** [Krayt78](https://github.com/Krayt78)
- **Tip Size:** small (20 DOT)


SmallTipper

This is a tip created by the [tip-bot](https://github.com/paritytech/substrate-tip-bot/).

### Details

- **Repository:** [polkadot-sdk](https://github.com/paritytech/polkadot-sdk)
- **PR:** [#6931](https://github.com/paritytech/polkadot-sdk/pull/6931)
- **Contributor:** [Krayt78](https://github.com/Krayt78)
- **Tip Size:** small (20 DOT)


Polkadot is a growing ecosystem with many new users in 2025. Some popular projects include Kaito, GigaDOT, $WUD, and DOT Bulls. New users often ask how to perform unique actions on Polkadot, like minting vDOT and transferring DOT to Hydration to buy WUD. A guide was requested for these topics, and NRL created a detailed guide on minting vDOT. The creator was rewarded with a 200 DOT tip for their content creation.

Rejected

The Polkadot ecosystem has had many newcomers in 2025 thanks in part to Kaito, GigaDOT, $WUD, DOT Bulls etc.



On Twitter, Telegram and Discord I often see newcomers ask how to do certain actions unique to Polkadot, such as mint vDOT, and cross-chain transfer DOT to Hydration to buy WUD.



I publicly asked for someone to create a guide on topics like these in return for a 200 DOT tip![Screenshot 2025-05-04 at 18.14.42.png](https://i.ibb.co/nMHTdCcv/mdx-Editor-ET-1746375731799.png)



NRL took me up on it and created this detailed guide on how to mint vDOT:



https://x.com/nrlartt/status/1916443887775764695



This tip is for his content creation.

Tip to NRL for creating vDOT Minting guide

This is a tip created by the [tip-bot](https://github.com/paritytech/substrate-tip-bot/).

### Details

- **Repository:** [polkadot-sdk](https://github.com/paritytech/polkadot-sdk)
- **PR:** [#8401](https://github.com/paritytech/polkadot-sdk/pull/8401)
- **Contributor:** [PolkadotDom](https://github.com/PolkadotDom)
- **Tip Size:** small (20 DOT)


This is a tip created by the [tip-bot](https://github.com/paritytech/substrate-tip-bot/).

### Details

- **Repository:** [polkadot-sdk](https://github.com/paritytech/polkadot-sdk)
- **PR:** [#3811](https://github.com/paritytech/polkadot-sdk/pull/3811)
- **Contributor:** [dharjeezy](https://github.com/dharjeezy)
- **Tip Size:** medium (80 DOT)


[Small Tipper] Referendum #1524

This is a tip created by the [tip-bot](https://github.com/paritytech/substrate-tip-bot/).

### Details

- **Repository:** [polkadot-sdk](https://github.com/paritytech/polkadot-sdk)
- **PR:** [#6630](https://github.com/paritytech/polkadot-sdk/pull/6630)
- **Contributor:** [bennethxyz](https://github.com/bennethxyz)
- **Tip Size:** small (20 DOT)


This is a tip created by the [tip-bot](https://github.com/paritytech/substrate-tip-bot/).

### Details

- **Repository:** [polkadot-sdk](https://github.com/paritytech/polkadot-sdk)
- **PR:** [#7286](https://github.com/paritytech/polkadot-sdk/pull/7286)
- **Contributor:** [EleisonC](https://github.com/EleisonC)
- **Tip Size:** small (20 DOT)


Polkadot Next.js Starter is a project that helps developers make cool frontend applications easily. Here are some important points about it:

- It helps people create apps quickly for events like hackathons.
- Features include wallet connections, Polkadot API for blockchain, and Tailwind CSS for design.
- It uses the Next.js framework for better website performance.
- The project has already attracted attention on Twitter with many views and likes.
- Plans for the future include improving the app and adding new features.
- Funding is requested for development work to continue enhancing the project.
- There are links to the project on GitHub and Twitter for more information.

[Small Tipper] Referendum #1507

The JAM Whitelist Role Authorizer is a project that uses the JAM SDK to create a role-based and whitelist authorization system. It is a contribution to the Polkadot open source ecosystem and shows the potential of the JAM SDK for developing practical and scalable solutions. The project allows managing authorized addresses, assigning roles (administrator, participant, observer), and running an interactive game where participants answer questions under supervision. The system ensures that only authorized addresses can perform specific actions, ensuring transparency and security in decentralized environments. The repository's resources are available in both English and Spanish, making it easy to use and understand for a global audience of developers.

The project uses several JAM SDK components, including jam-types, jam-pvm-common, jam-bootstrap-service, jam-null-authorizer, and jam-pvm-build. These components are used to manage validation of authorized addresses, ensure data compatibility with the PVM runtime environment, configure initial service settings, and build PVM code blobs for services or authorizers.

The project serves as a practical example for other developers wishing to build similar services and encourages the adoption of the JAM SDK. It provides a modular and extensible solution that can adapt to various authorization scenarios in decentralized applications. The project also includes guidance documentation available in multiple languages.

The execution workflow of the project includes assigning roles to participants, viewing the main menu, selecting options for admin validation, participant validation, observer validation, and verification of user roles and identification vectors.

The project has potential applications in the Polkadot Blockchain Academy and in video games like DOOM executed in JAM. It can be used to create a transparent and fair entrance exam process and to manage who can interact with services in JAM.

Hello people, i want to introduce my project “**JAM Whitelist Role Authorizer**”, an implementation that **uses the JAM SDK** to provide a role-based and whitelist authorization system. This project is a significant contribution to the Polkadot open source ecosystem and demonstrates the potential of the JAM SDK to develop practical and scalable solutions.

**What does this project do?**  
The JAM Whitelist Role Authorizer allows managing authorized addresses, assigning roles (administrator, participant, observer), and running an interactive game where participants answer questions under supervision. The system ensures that only authorized addresses can perform specific actions, ensuring transparency and security in decentralized environments.

Additionally, **the repository’s resources are available in both English🇬🇧 and Spanish 🇪🇸**, making it easy to use and understand for a global developers.  
  

Open Source Code: [Github](https://github.com/Themvp07/JAM-Playground-SDK/tree/main)

**JAM SDK Components Used**

1.  **jam-types (Implemented) Description**: This crate contains basic types and structures needed for working with services and authorizers in JAM.  
    **Components Used**:  
    **Authorizer**: Represents the JAM system's authorizer. It contains two main fields:  
    **code\_hash**: A hash representing the program code.  
    **param**: A parameter that can store additional information (e.g., the admin's address). **CodeHash**: Represents a 32-byte hash used to validate whether a hash belongs to a list of valid hashes.  
    **AuthParam**: A parameter used to store additional data related to authorization.  
    **Usage in the Project**:  
    Authorizer is used to manage the validation of authorized addresses.  
    A CodeHash is dynamically generated based on the admin's name and used to verify the authenticity of operations.  
    AuthParam is extended with the admin's address to track who performed certain actions.
2.  **jam-pvm-common (Reviewed for Future Implementation) Description**: Provides common functionalities for working with the PVM (Parity Virtual Machine).  
    **Current Usage**: Not explicitly used in the current code.  
    **Future Suggestion**: It could be used to ensure that data generated by the authorizer is compatible with the PVM runtime environment. For example, you could implement specific serialization/deserialization functions to handle data in the format required by the PVM.
3.  **jam-bootstrap-service (Reviewed, Used as Reference) Description**: A basic service useful for creating initial configurations (genesis) in JAM.  
    **Usage in the Project**: Cloned as a reference to understand how to configure a basic service in JAM.  
    **Future Suggestion**: It could be used to define an initial configuration that includes predefined addresses for the admin, participant, and observer.
4.  **jam-null-authorizer (Used as a Starting Point, but Not Present in the Current Code) Description**: A basic authorizer that allows testing without authorization restrictions.  
    **Current Usage**: Not explicitly used in the current code.  
    **Future Suggestion**: It could be used as a starting point to implement more advanced test cases. For example, it could be integrated to test scenarios where no authorization is required.
5.  **jam-pvm-build (Reviewed but Not Publicly Available) Description**: A CLI tool that allows building PVM code blobs for services or authorizers.  
    **Current Usage**: Not explicitly used in the current code.  
    **Future Suggestion**: It could be used to compile the custom authorizer into a deployable PVM blob.

**Community Value**

This project not only demonstrates how to effectively integrate and use the JAM SDK, but also serves as a practical example for other developers wishing to build similar services. It also:

-   Encourages adoption of the JAM SDK by providing a real,easily adaptable use case for other functional services.
-   Provides a modular and extensible solution that can adapt to various authorization scenarios in decentralized applications.
-   Guidance documentation available in multiple languages.

**Execution worlflow**

1.  Assigning roles to participants  
    ![](https://i.ibb.co/chjVn3NR/1.jpg)
2.  view main menu  
    ![](https://i.ibb.co/5xxMhqgz/2.jpg)
3.  Select option 1: Admin validation and selection of number of questions to ask  
    ![](https://i.ibb.co/1YH35XcZ/3.jpg)
4.  Select option 2: Participant validation and answering questions
    
    ![](https://i.ibb.co/6cxMhkQZ/4.jpg)
5.  Select option 3: Observer validation and viewing answers
    
    ![](https://i.ibb.co/HLvNwX9K/5.jpg)
6.  Select option 4: Verification of user roles and identification vectors
    
    ![](https://i.ibb.co/1GgW27fr/6.jpg)

**Example of ideas for future implementations**  
  

**Potential Application in Polkadot Blockchain Academy**: This role and authorization system could also be adapted to create a useful scenario in the Polkadot Blockchain Academy. For example, the entrance exam could leverage this resource to be more transparent and fair:

-   **Administrator**: Defines the questions and manages the process.
-   **Participant**: Answers the questions within a limit of operations.
-   **Observer**: Monitors the results and ensures impartiality.

By using a blockchain-based system, it is ensured that the process is immutable, transparent, and verifiable by all involved. This could improve trust in the selection process and make it more inclusive for global candidates.

**Connection with video games like DOOM executed in JAM**: The system developed is an essential component for managing who can interact with services in JAM. For example:

-   **Access Restriction**: In the case of DOOM or another video game, it is possible to use this authorizer to restrict who can deploy or run the application.
-   **Role Assignment**: We could assign specific roles, such as administrators who can modify game parameters or users who can only play the game.

In the case of DOOM, these components could be used to:

-   Validate that the DOOM binary has not been modified.
-   Authorize certain users to run the game.
-   Store relevant metadata, such as the player address or game state.

Thank you for your attention, **I hope this resource, documentation and implementation ideas will be useful for everyone**. See you in the decentralized future that is getting closer =)  
  
NOte: Thanks Gav and Parity team by this interesting piece of software

VOTE NAY - Wrong category- [Retroactive Funding] JAM SDK Implementation of reusable service

[Small Tipper] Referendum #1473

root

whitelisted_caller

wish_for_change

staking_admin

treasurer

lease_admin

fellowship_admin

general_admin

auction_admin

referendum_canceller

referendum_killer

big_tipper

small_spender

medium_spender

big_spender

Referenda Small Tipper

Origin able to dispatch a whitelisted call.

Origin for signaling that the network wishes for some change

Origin able to cancel slashes and manage minimum commission.

Origin for spending up to 10,000,000 DOT from the treasury as well as generally administering it.

Origin for managing the composition of the fellowship.

Origin able to spend around 1,000 DOT from the treasury at once.

Origin able to spend around 10,000 DOT from the treasury at once.

Origin able to spend around 100,000 DOT from the treasury at once.

Origin able to spend up to 1,000,000 DOT from the treasury at once.

[30] Origin: SmallTipper