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

small_tipper

Executed

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)


SmallTipper

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.

Rejected

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

[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

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:** [#6293](https://github.com/paritytech/polkadot-sdk/pull/6293)
- **Contributor:** [aurexav](https://github.com/aurexav)
- **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:** [#6607](https://github.com/paritytech/polkadot-sdk/pull/6607)
- **Contributor:** [Krayt78](https://github.com/Krayt78)
- **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:** [#7481](https://github.com/paritytech/polkadot-sdk/pull/7481)
- **Contributor:** [clangenb](https://github.com/clangenb)
- **Tip Size:** medium (80 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:** [#7600](https://github.com/paritytech/polkadot-sdk/pull/7600)
- **Contributor:** [huntbounty](https://github.com/huntbounty)
- **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:** [#6616](https://github.com/paritytech/polkadot-sdk/pull/6616)
- **Contributor:** [Krayt78](https://github.com/Krayt78)
- **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:** [#6606](https://github.com/paritytech/polkadot-sdk/pull/6606)
- **Contributor:** [Krayt78](https://github.com/Krayt78)
- **Tip Size:** small (20 DOT)


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

### Details

- **Repository:** [bounties](https://github.com/polkadot-developers/bounties)
- **PR:** [#10](https://github.com/polkadot-developers/bounties/pull/10)
- **Contributor:** [sam0x17](https://github.com/sam0x17)
- **Tip Size:** large (150 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:** [#7003](https://github.com/paritytech/polkadot-sdk/pull/7003)
- **Contributor:** [ayevbeosa](https://github.com/ayevbeosa)
- **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:** [#7320](https://github.com/paritytech/polkadot-sdk/pull/7320)
- **Contributor:** [Nathy-bajo](https://github.com/Nathy-bajo)
- **Tip Size:** small (20 DOT)


Polkadot Experience Beta — Arequipa was a 2-day workshop for developers in Arequipa, Peru. The event focused on teaching participants about the Polkadot ecosystem and blockchain technology. Here are the main points:

1. The workshop was self-funded and did not receive any treasury or bounty funds.
2. Arequipa is an important city for software development in Peru and is known in Silicon Valley for its Techsuyo conference.
3. The workshop covered topics like cryptography, blockchain evolution, decentralized applications, smart contracts, and Rust programming.
4. Participants learned to create interactive logic using Rust and build fully functional blockchains with the Polkadot SDK.
5. The event had great results, including massive participation and inclusion of participants in official Polkadot channels.
6. In June, a hackathon in Lima, Peru, had two teams from Arequipa win first and third place in the smart contracts category using Rust.

**Polkadot Experience Beta — Arequipa**  
  
This tip corresponds to a 2-day workshop run with own funds and that did not receive funds from any treasury or bounty last year.

Polkadot Experience that I carry out to provide workshops to developers in various locations and that last year had its second edition, in this case this request corresponds to the Arequipa Peru edition.

**Full details**: 

[https://docs.google.com/document/d/1PqKg8msrsZp-EGkyakLoHPYLBDpYabxb/edit?usp=sharing&ouid=117666172967964407937&rtpof=true&sd=true](https://docs.google.com/document/d/1PqKg8msrsZp-EGkyakLoHPYLBDpYabxb/edit?usp=sharing&ouid=117666172967964407937&rtpof=true&sd=true)

**Use of funds**: 

[https://docs.google.com/spreadsheets/d/1bxOuZtX-6zKmgXT8GLUW5kkPd0lBGCkw/edit?usp=sharing&ouid=117666172967964407937&rtpof=true&sd=true](https://docs.google.com/spreadsheets/d/1bxOuZtX-6zKmgXT8GLUW5kkPd0lBGCkw/edit?usp=sharing&ouid=117666172967964407937&rtpof=true&sd=true)

**Photo album**: 

[https://drive.google.com/drive/folders/1GFat2ODkD3CuNGWAaR86vk1ebUhOleAB?usp=sharing](https://drive.google.com/drive/folders/1GFat2ODkD3CuNGWAaR86vk1ebUhOleAB?usp=sharing)

**Quick contex**t: Arequipa is the city in Peru with the greatest relevance at the level of software development in the country, for this reason it is preferred by technological giants to carry out recruitment and the Arequipeña community is known in Silicon Valley for annually organizing the Techsuyo conference. These were the reasons for holding 2 days of workshops there.

For 2 days (3 hours per day) a workshop was provided for developers where they were able to explore various resources available in the Polkadot ecosystem by completing theoretical and practical exercises.

Activity agenda:

**Day 1**

The workshop started with a basic introduction to cryptography. This covered:

• Hash functions

• Elliptic curves

We then moved on to a basic introduction to blockchains, covering:

• Blockchain evolution (Bitcoin, Ethereum, Polkadot)

• Decentralized application architecture

• Smart contracts explained

• Key concepts in Rust.

**Workshop**: Participants will be able to create interactive logic using Rust.

**Day 2**

On the second day, we focused on the Polkadot ecosystem and built fully functional blockchains using the Polkadot SDK:

• Introduction to Polkadot and its architecture.

• Solutions available in the Polkadot ecosystem

• Importance of XCM interoperability between chains.

**Workshop**: We learned and successfully completed a implementation about Substrate, the blockchain development framework provided by the Polkadot SDK.

This was the first time that this type of blockchain activities was carried out in Arequipa and **obtaining great results** among which the following can be mentioned:

-   Massive participation during the activities.
-   Inclusion of participants in official channels of the Polkadot ecosystem.

Reference: [https://x.com/polkadot\_per/status/1761799081591017946?s=52&t=xZwu9y0l8ACyMwWB7pH3Rg](https://x.com/polkadot_per/status/1761799081591017946?s=52&t=xZwu9y0l8ACyMwWB7pH3Rg)

![](https://i.ibb.co/q1Kz7wQ/1.png)

It was possible to get interactions on Polkadot official Discord

![](https://i.ibb.co/Fz6Yx7W/2.png)

• Additionally in June a hackathon was held in Lima, Peru where 2 teams made up of Arequipeños **received scholarships from Polkadot Peru to travel to Lima and achieved first and third place** in the smart contracts category with Rust, demonstrating the talent present in the region.

References:

First place repository: [https://github.com/Space4Build/La-Causathon-Chaintrust](https://github.com/Space4Build/La-Causathon-Chaintrust)

Post: [https://x.com/Polkadot\_per/status/1805601736897319361](https://x.com/Polkadot_per/status/1805601736897319361)

![](https://i.ibb.co/x7vd1zs/eq1.jpg)

Third place repository: [https://github.com/Space4Build/La-Causathon-CLAMZ/tree/main](https://github.com/Space4Build/La-Causathon-CLAMZ/tree/main)

Post: [https://x.com/Polkadot\_per/status/1805601754156777526](https://x.com/Polkadot_per/status/1805601754156777526)

![](https://i.ibb.co/VNwwhRX/eq2.jpg)

Tip for 2 days workshop - Polkadot Experience Beta

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