PolkaBiz is an important part of the Polkadot ecosystem. They help new businesses and people who want to start their own projects. They give advice and support to make sure these projects are successful. In 2025, PolkaBiz wants to get more funding to keep helping people and make Polkadot a great place for new ideas.

PolkaBiz finds and helps new businesses that have a lot of potential. They have already looked at more than 100 businesses this year. They want to give people who want to start their own businesses a chance to show what they can do. Their program helps businesses grow and also teaches students in special programs.

PolkaBiz thinks that many people who start new businesses in the Web3 world don't know enough about business strategies. This can lead to bad decisions. PolkaBiz helps fill this gap and make sure businesses can succeed.

People who work with PolkaBiz say good things about them. They help a lot of teams and make sure they are ready for the next steps. They work hard to help businesses and students. They want to keep working with PolkaBiz to help more people.

You can read more about their plan here: [PolkaBiz Proposal](https://docs.google.com/document/d/1EdAWrKn2JW3amysB3aFlDmb6uAAQIV9LcC36OZ0VAtc/edit?usp=sharing)

Rejected

medium_spender

**Introduction** PolkaBiz plays a key role in the Polkadot ecosystem, providing mentorship and business expertise to founders, builders, and programs such as PBA, PBA-X, Web3 Foundation, and Scytale Digital. To continue delivering high-value mentorship and guidance, this proposal seeks funding to support the PolkaBiz team for their work in 2025, ensuring Polkadot remains an attractive hub for Web3 entrepreneurship.

PolkaBiz actively identifies and mentors high-potential startups, already screening 100+ startups in 2025. We believe that entrepreneurial minds and ambitious builders deserve a platform to be heard and supported. Our mentorship program not only accelerates startups but also provides a valuable educational experience for students in PBA X and PBA Campus.

**Why a Pitch & Mentor program?** Many Web3 founders lack business strategy and go-to-market expertise. This leads them to make wrong and sometimes detrimental decisions. PolkaBiz fills this gap. By helping founders succeed, we help create an environment where entrepreneurial, ambitious people feel welcomed.

**Feedback from partners**

-   “Mario and Christian put by far the most teams for the founders grants program in touch with us and supported us by preselecting the teams. They significantly contributed to the success of this first invite-only test run.” **David Hawig - Director of Ecosystem Development, Web3 Foundation.**
    
-   “Mario and Christian formed an alliance following their time at PBA in Hong Kong as students on the Founders track we ran at that time. Since then the original Polkabiz idea has become a great tool, proven to identify and nurture entrepreneurs who have places in PBA Campus or PBA-X into the ecosystem. The next step is to use Polkabiz as a means of attracting entrepreneurs to PBA via marketing of the benefits Polkabiz provides, thus creating a new funnel of projects into the ecosystem.Mario and Christian are great at what they do and are tireless in their efforts. We’re really keen to keep working with them to help.“ - **Tim Dobie - Director of Blockchain Academy.**
    
-   “I had the opportunity to work with Polkabiz at PBA Singapore and PBAX Wave 1, where I mentored teams that went through their initial screening and mentoring process. I can vouch for the quality of effort and time Polkabiz invests in mentoring these teams 1:1, which is evident from the qualitative and quantitative feedback received from the participants” - **Dr. Radha Dasari, Technical Education Lead, Web3 Foundation.**
    

See here the details of the full proposal: [https://docs.google.com/document/d/1EdAWrKn2JW3amysB3aFlDmb6uAAQIV9LcC36OZ0VAtc/edit?usp=sharing](https://docs.google.com/document/d/1EdAWrKn2JW3amysB3aFlDmb6uAAQIV9LcC36OZ0VAtc/edit?usp=sharing)

PolkaBiz Business Mentorship & Ecosystem Support

MinIO is a high-performance, S3-compatible object storage that can be used on public clouds, Kubernetes, private clouds, and the edge. Acurast, a decentralized verifiable compute network powered by phones, is partnering with MinIO to provide decentralized storage for Polkadot-native projects and enterprises. The main goal of this partnership is to create an MVP integration of MinIO in Acurast's decentralized compute environment, allowing developers to access MinIO through Acurast's native P2P layer. This will include creating storage buckets, configurable access control, benchmarking replications and costs, and providing detailed developer documentation and examples. Acurast's network uses billions of smartphones to run secure applications on decentralized infrastructure without compromising speed or privacy.

Executed

small_spender

Decentralized object storage that seamlessly slots into place, replacing centralized solutions, is still hard to come by. MinIO ([https://min.io/),](https://min.io/\),) a high-performance and S3-compatible object storage, is already an established standard available on every public cloud, every Kubernetes distribution, private cloud, and the edge.

By activating the storage of Acurast’s ([https://acurast.com/](https://acurast.com/)) worldwide decentralized Cloud combined with MinIO, not only can Polkadot-native projects leverage true decentralized storage, but enterprises are also enabled to simply switch from their existing setup to a decentralized one.

[View full proposal](https://drive.google.com/file/d/1i3KUP3SRIw0nMHr59r2NoaNOGCyLyk5M/view?usp=sharing)

**Context of the Proposal**

The main goal is to build out the MVP integration for MinIO to be run in Acurast’s decentralized compute environment and making it accessible to developers.

-   MVP integration of MinIO object storage in Acurast’s decentralized compute environment
-   Creation of storage buckets and configurable access control
-   Configuration and development in making MinIO exposable through Acurast native P2P layer
-   Benchmarking of required replications and estimated costs per GB storage on Acurast’s network
-   Testing and detailed developer documentation with detailed developer examples of how to access MinIO in Acurast’s compute environment

**About Acurast**

Acurast is the first decentralized verifiable compute network powered by phones.

Acurast is redefining compute by utilizing billions of smartphones – no data centers required. This verifiable, scalable, and confidential compute network enables users to run secure applications on decentralized infrastructure at scale—without compromising speed or privacy.

By leveraging these phones with their Trusted Execution Environments (TEEs) in combination of a Polkadot-powered blockchain, Acurast is perfectly suited for running mission critical workloads with high-security requirements. With over 50,000+ phones onboarded worldwide on its incentivized testnet on Kusama with over 200M transactions processed.

Decentralized High Performance Object Storage (MinIO)

Polkadot had a problem with its software update, which stopped three staking accounts from getting rewards. A proposal has been made to give these accounts the rewards they missed out on. The proposal looks at how much money was in the accounts when the rewards stopped, how many times they didn't get rewards, and how much the rewards would have been worth during that time. Here are the details for each account:

1. Account 138fZsNu67JFtiiWc1eWK2Ev5jCYT6ZirZM288tf99CUHk8K:
   - Last reward: Era 1400
   - Last balance: 8,556 DOT
   - Missed rewards: 197 eras
   - Average yearly reward: 17.18%
   - Missing rewards: 1,603.46 DOT

2. Account 15bt67qghz8hJxCUPgAXmzVxUBHLpPN41RVm2nwMFyLWByVE:
   - Last reward: Era 1646
   - Last balance: 4,261 DOT
   - Missed rewards: 37 eras
   - Average yearly reward: 12.93%
   - Missing rewards: 587.11 DOT

3. Account 12gmcL9eej9jRBFT26vZLF4b7aAe4P9aEYHGHFzJdmf5arPi:
   - Last reward: Era 1402
   - Last balance: 7,110 DOT
   - Missed rewards: 211 eras
   - Average yearly reward: 16.96%
   - Missing rewards: 1,313.76 DOT

**SUMMARY**

The Polkadot runtime upgrade to v1.1.2 introduced an unintentional breaking change that prevented three staking accounts from receiving staking rewards across multiple eras. This proposal seeks to reimburse these accounts for the rewards they should have earned for backing validators and securing the network.

The process was detailed by core developer gpestana in multiple articles compiled in the following Polkadot Forum post:

[Recover corrupted Staking ledgers in Polkadot and Kusama](https://forum.polkadot.network/t/recover-corrupted-staking-ledgers-in-polkadot-and-kusama/9796)

The referendum could not be proposed until the runtime upgrade to v1.4.0, which corrected the balance state of one of the affected accounts ([PR 538](https://github.com/polkadot-fellows/runtimes/pull/538)).

**TIMELINE**

-   2024-02-19 Breaking change introduced in runtime upgrade v1.1.2
-   2024-03-15 Hotfix on runtime upgrade to v1.1.3.
-   2024-10-15 Runtime upgrade to v1.3.3 set the correct ledger/stash status.
-   2025-02-26 The balance issue for one of the accounts was corrected on runtime v.1.4.0.

**PROPOSAL DETAILS**

Each account faced a unique situation, and the analysis took into account the bonded funds at the time rewards ceased, the number of eras the payee account went without receiving rewards, and the average APY during that period.

Below is the information for each affected account:

Affected account: 138fZsNu67JFtiiWc1eWK2Ev5jCYT6ZirZM288tf99CUHk8K

-   Payee account: **12YcbjN5cvqM63oK7WMhNtpTQhtCrrUr4ntzqqrJ4EijvDE8**
-   Last era with rewards: [1400](https://polkadot.subscan.io/extrinsic/20169733-4?event=20169733-1224)
-   Last bonded balance before not receiving rewards (DOT): 8,556
-   Last era with no rewards: [1597](https://polkadot.subscan.io/extrinsic/23007919-2?event=23007919-627)
-   Eras without rewards: 197
-   Average APY during that period (%): 17.18
-   Missing rewards (DOT): **1,603.46**

Affected account: 15bt67qghz8hJxCUPgAXmzVxUBHLpPN41RVm2nwMFyLWByVE

-   Payee account: **15bt67qghz8hJxCUPgAXmzVxUBHLpPN41RVm2nwMFyLWByVE**
-   Last era with rewards: 1646  
    During era 1526, the stash account 14kwUJW6rtjTVW3RusMecvTfDqjEMAt8W159jAGBJqPrwwvC was [wrongly scored with 0](https://polkadot.subscan.io/extrinsic/21972815-4?event=21972815-77) in the 'voterlist'. However, the account 15bt67 kept receiving rewards until era 1646. During era 1683, the account 14kwUJ 'voterlist' score [was updated](https://polkadot.subscan.io/extrinsic/24214751-3?event=24214751-64) and the same account started to receive rewards at era 1684.
-   Last bonded balance before not receiving rewards (DOT): 4,261
-   Last era with no rewards: 1683
-   Eras without rewards: 37
-   Average APY during that period (%): 12.93
-   Missing rewards (DOT): **587.11**

Affected account: 12gmcL9eej9jRBFT26vZLF4b7aAe4P9aEYHGHFzJdmf5arPi

-   Payee account: **12gmcL9eej9jRBFT26vZLF4b7aAe4P9aEYHGHFzJdmf5arPi**
-   Last era with rewards: [1402](https://polkadot.subscan.io/extrinsic/20198278-3?event=20198278-112)
-   Last bonded balance before not receiving rewards (DOT): 7,110
-   Last era with no rewards: 1613
-   Eras without rewards: 211
-   Average APY during that period (%): 16.96
-   Missing rewards (DOT): **1,313.76**

Reimbursement for corrupted staking ledgers

- A group called ChaosDAO, JUST Ventures, and Hydration proposed to get stable money (USDT and USDC) using Polkadot's treasury.
- They want to change 5,001,000 DOT into equal parts of 2,500,000 DOT into USDT and USDC over a year.
- This plan will help keep the value of the treasury steady and safe for future expenses.
- They will sell small amounts of DOT regularly to avoid big price changes and make the process efficient.
- They are using a special method called DCA (Dollar-Cost Averaging) to make the exchange smoother.
- The proposal also aims to use some of the funds to earn interest while they are waiting to convert.
- This plan involves sending funds to different places using a process called XCM.

root

**Track**: Root

**Proposer**: ChaosDAO, JUST Ventures, Hydration

**Date**: March 2025

**Requested allocation**:  5,001,000 DOT

**Short description**:  We proposed a structured approach for the Polkadot Treasury to obtain native USDT and USDC, for the purpose of diversification and enabling it to pay out expenses in a stable asset. Through this referendum, we aspire to renew the schedule presented in proposal #457 and convert 2,500,000 DOT into USDT and 2,500,000 DOT into USDC via the DCA mechanism described in detail below, where an additional 1000 DOT is reserved for transaction fees. This proposal presents a long-term solution to acquire different tokens in exchange for treasury DOT by Polkadot governance participants.

___________________________________________________________________________________

**Context of the proposal:**

Probably one of the most-requested features is the ability to make Treasury proposals in stablecoins like USDT and USDC. This is for many reasons, including less volatility around Treasury proposals and preserving the value of the Polkadot Treasury to ensure funds are available to support a given budget in the future.

With the latest upgrades to Substrate and the Polkadot runtime, the Treasury has a lot more tools available to it for its management, including proposals with non-DOT assets like stablecoins.

As was done in referendum 457, this proposal is to convert 5,000,000 DOT to USDT and USDC over the course of the next year, with 50% going to each. This uses Hydration's DCA feature to convert a little bit each day and ensure a steady flow of stablecoins into the Treasury.

Unlike 457, this referendum sells a fixed amount of DOT per trade rather than acquiring a fixed amount of USDT/C. For better capital efficiency, the full amount of DOT will be also initially converted into aDOT (yield-bearing collateral token) and supplied into the Hydration Borrow feature. By doing so, the Polkadot Treasury will accumulate yield on the dormant DOT, while substantially increasing the DOT supply available for borrowing, thus enabling more DeFi use cases. More details can be found in [this post](https://polkadot.subsquare.io/posts/401). 

Moreover it newly utilizes the “Rolling DCA” feature, which enables renewing the schedule just by sending DOT to the proxy account. This in turn means other governance tracks with lower security assumptions, such as Treasurer, can be used for smaller topups if needed. 

This amount accounts for about 22% of the new DOT expected to be minted into the Treasury over the next year (this could vary based on variables like the staking rate).

**Proposal objective(s) or solution(s):**

The central proposition entails the creation of a schedule that converts DOT into USDT and USDC via the DCA feature on Hydration, a parachain on Polkadot.

The attributes of this proposal are:
- Cost-efficiency (approx. 0.4% of the total amount)
- No necessity to appoint curators who oversee and manage the process
- Conversion is done in small amounts over a longer period which provides a hedge for price volatility and manipulation

DCA schedule parameters: [USDT]

- Total duration with current EMA7 price: 365 days
- Total amount: 2,500,000 DOT
- Trade frequency: One trade every 20 blocks (approx. 4 minutes)
- Per trade: 20 DOT
- Per day: 7200 DOT
- Send to asset hub after accumulating: 5,000 USDT
- Total fee estimation: 0.4% of total amount acquired

DCA schedule parameters: [USDC]

- Total duration with current EMA7 price: 365 days
- Total amount: 2,500,000 DOT
- Trade frequency: One trade every 20 blocks (approx. 4 minutes)
- Per trade: 20 DOT
- Per day: 7200 DOT
- Send to asset hub after accumulating: 5,000 USDC
- Total fee estimation: 0.4% of total amount acquired

Fee estimation breakdown:

- Trade fee: 0.3% (0.25% to Liquidity Providers, 0.05% to the protocol)
- Slippage fee: 0.045% (→AMM)
- Transaction fee on Hydration: 0.035% (→Protocol treasury)
- Transaction fee on Polkadot Asset Hub: 0.02% (→Asset Hub collators)

**Note**: Fees depend heavily on the schedule settings and are estimated based on parameters used. It is worth mentioning that the Hydration protocol also uses dynamic fees based on block space utilization ranging 0.15-5% to protect liquidity providers in times of volatility. All time average trade fees as of proposal submission are around 0.3%.

**Description of steps utilizing XCM to achieve the solution:**

- Send 5,000,001DOT from the Polkadot treasury to the Pure Proxy account [7N4oFqXKgeTXo6CMSY9BVZdHP5J3RhQXY77Fe7qmQwjcxa1w] controlled exclusively by the relay chain sovereign account on Hydration [7KQx4f7yU3hqZHfvDVnSfe6mpgAT8Pxyr67LXHV6nsbZo3Tm]

- After 1 block to process balance state changes on Hydration, schedule sending an XCM program to Transact on Hydration. This will initiate two DCA schedules, each with a total amount of 2,500,000 DOT, swapping 20 DOT to USDT and USDC every 20 blocks.

- Once the first USDT chunk is accumulated, initiate a periodic schedule that sends cross-chain chunks of 5,000 USDT and 5,000 USDC from the Pure Proxy on Hydration to the General Treasury account on the Polkadot Asset Hub [14xmwinmCEz6oRrFdczHKqHgWNMiCysE2KrA4jXXAAM1Eogk], totaling to max. 27500 transactions.

Renewal of treasury USDT and USDC Acquisition

- The proposal is for a sponsorship of Frank Porté in racing events to help Polkadot gain visibility and business opportunities.
- It costs $295,000 USD and covers both real and virtual races until October 2025.
- Frank Porté races in the Porsche Mobil 1 Supercup and the Porsche Carrera Cup Benelux, attracting a large audience.
- The sponsorship aims to connect Polkadot with influential people in business and finance.
- It also offers chances to create new partnerships and strengthen ties with important institutions in Andorra.
- Social media and media exposure will be high, with millions of views and followers expected.
- Unique content like behind-the-scenes access and fan rewards will enhance engagement for Polkadot.

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

Sponsorship Hybrid driver  PORSCHE SUPER CUP - PORSCHE BENELUX 

**Retroactive Funding Proposal: Bounty Manager V2.0**

- Proponent: galaniprojects GmbH
- Address: 143A8aK5Sdiyw8eHMbGKRWz1VdKg75BG2SRVXTFwyHjuujCE
- Date: 20/03/2025
- Requested Funding: 64,368 USDC (59,600€)
- Short Description: Development of Bounty Manager V2.0, a platform for managing bounties with new features and visual updates.
- Website: [https://bountymanager.io](https://bountymanager.io)
- Project Category/Type: Software Development
- Detailed Proposal: [Proposal document](https://github.com/galaniprojects/Polkadot-Bounty-Manager/wiki/Retroactive-Funding-Proposal:-Bounty-Manager-V2.0)
- Context: Bounty Manager V2.0 is a tool to make bounty curation easier with a single platform, improved automation, and a new user interface.
- Payment Terms and Budget: Payment in USDC requested, total of 64,368 USDC.
- Who we are: Galaniprojects GmbH, a Berlin-based company offering software development, project management, quality assurance, and UI/UX design since 2006. They also work on projects for the KILT Parachain. Visit their website [here](https://galaniprojects.de/eng.html).

**Retroactive Funding Proposal**: Bounty Manager V2.0

**Proponent:** galaniprojects GmbH

**Address**: 143A8aK5Sdiyw8eHMbGKRWz1VdKg75BG2SRVXTFwyHjuujCE

**Date:** 20/03/2025

**Requested Funding**: 64,368 USDC (59,600€, 1€ ~ 1.08 USDC on 20/03/2025)

**Short description**: This is a retroactive funding proposal for development of the second version of Bounty Manager. It includes development of a bounties platform interface, additions and improvements to existing functionalities and a comprehensive visual update and overhaul.

**Website**: [https://bountymanager.io](https://bountymanager.io)

**Project Category/Type**: Software Development

**Detailed Proposal:** [Proposal document](https://github.com/galaniprojects/Polkadot-Bounty-Manager/wiki/Retroactive-Funding-Proposal:-Bounty-Manager-V2.0)

**Context:**  
This retroactive proposal outlines the work completed and features introduced in Bounty Manager v2.0, a tool designed to streamline bounty curation processes. In this second version of the Bounty Manager, users can access a single platform that consolidates all bounty information in one convenient location.

Curators benefit from enhanced automation features and quality-of-life improvements, as well as an overhauled UI.

**Payment terms and Budget:  
**We ask for payment in USDC. We cannot accept USDT since we are based in Europe and Tether does not meet the criteria for compliance with MiCa regulation.

Total USDC: 64,368

**Who we are:  
**Galaniprojects GmbH was established in 2006 and is situated in Berlin, Germany. We offer software development, project management, quality assurance and UI/UX design to clients across various industries, including Media & Publishing, Telecommunication, Automotive and Transport, as well as working as implementors on various projects for the KILT Parachain.

Visit our website [here](https://galaniprojects.de/eng.html).

Retroactive Funding Proposal: Bounty Manager V2.0

Snowbridge is a project that lets Polkadot native assets be used on the Ethereum network. It has a list of tokens that can be registered, and you can see all of them on a special website called GitHub. Here are some of the tokens:

1. Polkadot (DOT) - has 10 decimals and is located in a special place called {parents:1,interior:Here}.
2. Kusama (KSM) - has 12 decimals and is in {parents:2,interior:X1(\[GlobalConsensus(Kusama)\])}.
3. Glimmer (GLMR) - has 18 decimals and is in {parents:1,interior:X2(\[Parachain(2004),PalletInstance(10)\])}.
4. Bifrost Native Token (BNC) - has 12 decimals and is in {parents:1,interior:X2(\[Parachain(2030),GeneralKey{length:2,data:0x0001000000000000000000000000000000000000000000000000000000000000)}\])}.
5. Vouche DOT (vDOT) - has 10 decimals and is in {parents:1,interior:X2(\[Parachain(2030),GeneralKey{length:2,data:0x0900000000000000000000000000000000000000000000000000000000000000)}\])}.
6. Hydration (HDX) - has 12 decimals and is in {parents:1,interior:X2(\[Parachain(2034),GeneralIndex(0)\])}.
7. Integrite TEER (TEER) - has 12 decimals and is in {parents:1,interior:X1(\[Parachain(2039)\])}.
8. Ajuna Polkadot AJUN (AJUN) - has 12 decimals and is in {parents:1,interior:X1(\[Parachain(2051)\])}.
9. Polimec (PLMC) - has 10 decimals and is in {parents:1,interior:X1(\[Parachain(3344)\])}.
10. LAOS (LAOS) - has 18 decimals and is in {parents:1,interior:X1(\[Parachain(3370)\])}.

These tokens can be used on both Polkadot and Ethereum because of Snowbridge.

whitelisted_caller

Registers Polkadot native assets on Ethereum. The full list of tokens that will be registered can be viewed here: [https://github.com/Snowfork/snowbridge/blob/dcf3ebf5ff5735a785c1473419eca25fc39792fb/control/preimage/src/commands.rs#L397-L666](https://github.com/Snowfork/snowbridge/blob/dcf3ebf5ff5735a785c1473419eca25fc39792fb/control/preimage/src/commands.rs#L397-L666)

|     |     |     |     |
| --- | --- | --- | --- |
| **Name** | **Symbol** | **Decimals** | **Location** |
| Polkadot | DOT | 10  | {parents:1,interior:Here} |
| Kusama | KSM | 12  | {parents:2,interior:X1(\[GlobalConsensus(Kusama)\])} |
| Glimmer | GLMR | 18  | {parents:1,interior:X2(\[Parachain(2004),PalletInstance(10)\])} |
| Bifrost Native Token | BNC | 12  | {parents:1,interior:X2(\[Parachain(2030),GeneralKey{length:2,data:0x0001000000000000000000000000000000000000000000000000000000000000)}\])} |
| Vouche DOT | vDOT | 10  | {parents:1,interior:X2(\[Parachain(2030),GeneralKey{length:2,data:0x0900000000000000000000000000000000000000000000000000000000000000)}\])} |
| Hydration | HDX | 12  | {parents:1,interior:X2(\[Parachain(2034),GeneralIndex(0)\])} |
| Integrite TEER | TEER | 12  | {parents:1,interior:X1(\[Parachain(2039)\])} |
| Ajuna Polkadot AJUN | AJUN | 12  | {parents:1,interior:X1(\[Parachain(2051)\])} |
| Polimec | PLMC | 10  | {parents:1,interior:X1(\[Parachain(3344)\])} |
| LAOS | LAOS | 18  | {parents:1,interior:X1(\[Parachain(3370)\])} |
| KILT Spiritnet | KILT | 15  | {parents:1,interior:X1(\[Parachain(2086)\])} |
| Astar | ASTR | 18  | {parents:1,interior:X1(\[Parachain(2006)\])} |
| Centrifuge | CFG | 18  | {parents:1,interior:X2(\[Parachain(2031),GeneralKey{length:2,data:0x0001000000000000000000000000000000000000000000000000000000000000)}\])} |
| Subsocial | SUB | 10  | {parents:1,interior:X1(\[Parachain(2101)\])} |
| Phala Token | PHA | 12  | {parents:1,interior:X1(\[Parachain(2035)\])} |
| Parallel | PARA | 12  | {parents:1,interior:X2(\[Parachain(2012),GeneralKey{length:4,data:0x5041524100000000000000000000000000000000000000000000000000000000)}\])} |
| Crust Parachain Native Token | CRU | 12  | {parents:1,interior:X1(\[Parachain(2008)\])} |
| Manta | MANTA | 18  | {parents:1,interior:X1(\[Parachain(2104)\])} |
| Acala | ACA | 12  | {parents:1,interior:X2(\[Parachain(2000),GeneralKey{length:2,data:0x0000000000000000000000000000000000000000000000000000000000000000)}\])} |
| Liquid DOT | LDOT | 10  | {parents:1,interior:X2(\[Parachain(2000),GeneralKey{length:2,data:0x0003000000000000000000000000000000000000000000000000000000000000)}\])} |
| DED | DED | 10  | {parents:1,interior:X3(\[Parachain(1000),PalletInstance(50),GeneralIndex(30)\]),} |
| PINK | PINK | 10  | {parents:1,interior:X3(\[Parachain(1000),PalletInstance(50),GeneralIndex(23)\]),} |
| Kolkadot | KOL | 12  | {parents:1,interior:X3(\[Parachain(1000),PalletInstance(50),GeneralIndex(86)\]),} |
| GAVUN WUD | WUD | 10  | {parents:1,interior:X3(\[Parachain(1000),PalletInstance(50),GeneralIndex(31337)\])} |

[Whitelisted Caller] Register Polkadot Native Assets on Ethereum

The Polkadot Blockchain Academy (PBA) is a program that helps people learn about Polkadot and become skilled in it. They want more money to grow and offer more courses. Here are some reasons why PBA is important:

1. They have helped many people learn about Polkadot and make big contributions to it.
2. Most of their graduates have worked on Polkadot projects.
3. Big companies in the Polkadot world trust PBA and hire their graduates.
4. They make learning easy for people who can't be in person by offering online courses.

With more money, PBA will do these things:

1. Train more people in person.
2. Teach a special course about Polkadot's JAM protocol.
3. Work with universities to teach their courses.
4. Keep helping graduates find jobs and learn more.
5. Make new online courses based on what people need.
6. Help new projects join the Polkadot world.

By giving money to PBA, we can make sure there are enough skilled people to keep Polkadot growing. You can learn more about their plan by visiting their website.

big_spender

**\*\*\*\*This new proposal replaces referenda 1472, we are switching to USDT  and a tranche based funds release schedule to ease pressure on treasury funds, everything else remains the same as 1472.\*\*\*\***

**The Future of Polkadot Depends on Talent**

The Polkadot Blockchain Academy (PBA) is the single largest and most effective pipeline of talent into the Polkadot ecosystem. Over the past three years, close to 750 learners have completed our courses, many of whom now produce significant contributions towards Polkadot or ecosystem projects.

We are at a pivotal moment. The future of Polkadot depends not just on innovation but on a steady stream of highly skilled, motivated builders who can create and execute impactful projects, advance the network's capabilities and drive adoption. The PBA has proven its ability to deliver, our alumni are shaping the ecosystem, and demand for our programs has never been higher.

To capitalize on this momentum, we are requesting nine months of funding to scale our programs and diversify our offerings, making PBA more inclusive, relevant and far-reaching than ever before.

**Why support PBA? A Track Record of Success**

-   We are the largest producer of well educated, Polkadot-native talent – No other initiative has onboarded more developers successfully.
-   Close to 70% of 409 PBA Campus graduates actively contributed to open-source Polkadot-related repositories in 2024.
-   Trusted by ecosystem leaders – Parity, The Web3 Foundation and other top teams recruit directly from our alumni.
-   Expanding accessibility – Our online course, PBA-X, launched in January with 580+ learners, and close to 60% completion rate, proving demand for remote education for a diverse audience. Ongoing Evolution:

**Scaling & Strengthening the Polkadot Talent Engine**

With this funding, we will:

-   Expand PBA’s flagship in-person PBA Campus program (Wave 7) to train and place the next cohort of high-impact developers.
-   Launch The JAM Course, an intensive in person course demystifying Polkadot’s JAM protocol, for top-tier engineers from the Web3 community.
-   Grow university partnerships, integrating PBA content into curricula and securing the next generation of builders.
-   Enhance alumni engagement through ongoing participation orientated events, education, placement and mentorship opportunities.
-   Build upon the success of PBA-X to offer new content based on the needs of the ecosystem, whilst continuing to run the original PBA-X content for 5 more cohorts in 2025.
-   Continue to identify, mentor and funnel new projects into the ecosystem via the Pitch and Mentor program.

Polkadot’s growth depends on its builders. By funding PBA, we secure a sustainable, scalable pipeline of developers, entrepreneurs and advocates who will drive the ecosystem forward.

Follow the below link to find out more about our latest proposal;

[https://docs.google.com/document/d/11fKCbYG79VomgYFK4FDsK534ihmfSDG3wCnmLpo\_kws/edit?tab=t.0](https://docs.google.com/document/d/11fKCbYG79VomgYFK4FDsK534ihmfSDG3wCnmLpo_kws/edit?tab=t.0)

***revised proposal***Polkadot Blockchain Academy, PBA Campus 7, The JAM Course launch, University pilot, ongoing PBA-X evolution, Alumni program.

TimedOut

referendum_canceller

referendum_killer

[Do not vote]

- A new proposal is being made to improve how users can move assets from Ethereum to Polkadot using Snowbridge.
- Many users are frustrated because they can't use their assets once they bridge them, mainly due to not enough liquidity (availability of money) in the system.
- The proposal asks for about $2,000 in DOT tokens to help create a better system for users to pay fees.
- This money will be used to increase the available liquidity for users, making it easier for them to swap assets.
- The goal is to have users enjoy a better experience and help them use their assets throughout the Polkadot ecosystem.
- The funds will be managed by two trusted people to ensure everything is done correctly.
- Overall, this will help more people use Polkadot and make it a better place for everyone.

big_tipper

Provision of Snowbridge ETH Liquidity to Facilitate Fee Swaps

- OpenGuild helps Polkadot grow in Asia by teaching developers.  
- They hold workshops, meetups, and hackathons.  
- They partner with universities and Web3 communities.  
- Their goal is to connect builders to Polkadot’s ecosystem.  
- They support new projects and grants.  
- OpenGuild has 1,500+ members and runs events in many countries.  
- They help Polkadot stay strong in Asia.

Polkadot’s **builder community in SEA & broader Asia** remains **underleveraged**, despite the ecosystem’s **technological advantages**. Considering this year Polkadot have important narratives to push on Polkadot Cloud, Polkadot Hub and JAM**,** with a proven track record of engagement, technical expertise, and deep connections in the region, OpenGuild team propose a **coordinated 12-month activation plan** focused on builder community growth and developer engagement across key strategic markets in particular SEA & support broader Asia community following its success in 2024, with the following specific objectives:

**OPENGUILD'S KEY OBJECTIVES IN 2025-2026**

- **Localized Technical Enablement:**
 
 Offer in-depth workshops, bootcamps, and training focused on Polkadot SDK, Polkadot Smart Contracts, and cross-chain innovation to empower developers with the skills to build on Polkadot.
 
- **Grassroots Community Empowerment:**
 
 Facilitate monthly meetups, and community-driven activities that bring builders together, fostering collaboration and a sense of ownership within the Polkadot ecosystem in different countries.
 
- **Regional Ecosystem Activation:**
 
 Host region-specific Polkadot Hub campaigns, hackathons, and events to amplify adoption and showcase SEA as a leading contributor to Polkadot’s global vision.
 
- **Establish Web3 Community & Tech Universities Partnership** Grow partnerships with Tech Universities and Web3 Communities in Southeast Asia for education and incubation efforts, creating value exchange opportunities through Grants, Hackathon Campaigns, Co-hosted Activities, and continuous updates.
 
- **Career Pathways for Builders:**
 
 Connect talented developers to opportunities within Polkadot’s global ecosystem through mentorship programs, bounties, and ecosystem partnerships.
 
- **Ecosystem Coordination** Coordinating builder community activation efforts with other Asian builder communities partners primarily through the Marketing Bounty, Event Bounty, Web3Foundation grant, EasyA Fast grant, PBA, etc to provide necessary resources.
 

**CORE BENEFITS OF OPENGUILD INITIATIVE**

| | |
| --- | --- |
| Asian Builder Aggregation Hub | Serve as a coordination point for developers in SEA and broader Asia market. |
| Cross-chain Collaboration | Bridge projects built by Asian builders from different ecosystem considering Polkadot as a standing options for collaboration. |
| Accelerated Ecosystem Growth | Provides structured onboarding for new SEA builders and indie projects. |
| Polkadot Cloud & Hub Advocacy in SEA region | Drives awareness and adoption of Polkadot Hub for consumer apps through workshops, and local communication. |
| Regional Standing Position and Communication | Maintain, accelerate Polkadot techstack and ecosystem position in SEA market, and become the main communication channel for builders in region. |

**ABOUT OPENGUILD**

OpenGuild is a community of passionate Web3 builders dedicated to growing the Polkadot ecosystem. Our mission is to discover, connect, and support top talents in Southeast Asia (Vietnam, Thailand, Malaysia, Singapore, Philippines. Indonesia, etc) while also providing valuable resources to builders across Asia. Through collaboration and innovation, we strive to create real impact, develop groundbreaking products, and build a thriving community around Polkadot.

We focus on helping builders and organizations navigate and master Polkadot’s technology by offering well-structured resources, hands-on events, and engaging activities. Our goal is to make it easy for anyone to learn, build, and contribute to the ecosystem.

With 1,500+ members on our Discord, including majority of developers and innovators in marketing and business, plus 3,000 supporters across social media, OpenGuild is becoming the go-to hub for Web3 enthusiasts looking to explore and grow within the Polkadot ecosystem in SEA and broader Asia market.

**OpenGuild Team's Track Record - Check [here](https://openguild.notion.site/OpenGuild-PolkadotSEA-1-Year-Activities-Report-cb9ceec1f58c4bf2bdcbc5e5c65a0b86?pvs=74)**

**DETAILS EXECUTION PLAN - Read our [FULL PROPOSAL](https://openguild.notion.site/PROPOSAL-OpenGuild-Accelerate-Polkadot-Builder-Community-in-SEA-market-154659b1c81780beb814cdaa0a005308?pvs=73)**

**HOW THE SUCCESS OF OPENGUILD BEING SEEN?**

<div class="joplin-table-wrapper"><table style="border-collapse:collapse; width:100%; height:609px;" border="1"><tbody><tr><td style="width:29.1717%; height:21px;">Deliverables</td><td style="width:27.1426%; height:21px;">Key Numbers</td><td style="width:43.6857%; height:21px;">Description</td></tr><tr><td style="width:29.1717%; height:112px;">Monthly Meetups</td><td style="width:27.1426%; height:112px;">42 Meetups</td><td style="width:43.6857%; height:112px;">Organize content curated &amp; community-led monthly mini meetups with builders across SEA countries (Vietnam, Malaysia, Thailand, Singapore, Philippines, Indonesia) by our team and/or coordinate with regional community partners.</td></tr><tr><td style="width:29.1717%; height:112px;">Open Developer Bootcamps</td><td style="width:27.1426%; height:112px;">4 Bootcamps (4 key countries each)200-300 participants</td><td style="width:43.6857%; height:112px;">Organize across SEA countries with more updating Bootcamp Materials focusing on Polkadot Hub before the Buildathon with expected 200 new qualified students, then we provide onboarding flow in Polkadot ecosystem to PBA activations, building projects, career support.</td></tr><tr><td style="width:29.1717%; height:70px;">Community Calls &amp; Office Hours</td><td style="width:27.1426%; height:70px;">40 Weekly Sessions</td><td style="width:43.6857%; height:70px;">Update Polkadot ecosystem, invite Key builders to update information to SEA builders community.</td></tr><tr><td style="width:29.1717%; height:49px;">Polkadot SEA Buildathon 2025</td><td style="width:27.1426%; height:49px;">10 Dapps winning (out of the expectation of at least 50 submitted projects)</td><td style="width:43.6857%; height:49px;">Onboarding at least 10 quality applications in production to Polkadot Hub (Testnet or Mainnet dependable on the state of the chain) and still support other submission to on-going improvement for other grants paths to launch on the chain.</td></tr><tr><td style="width:29.1717%; height:49px;">Coordinate Grant Submissions</td><td style="width:27.1426%; height:49px;">8-15 Projects</td><td style="width:43.6857%; height:49px;">Coordinate with Grant opportunities (Fast Grant, Open-Source Grant, &amp; Ecosystem Grants, etc) to onboarding successful at least 8-15 quality open-source/business-oriented projects with milestones delivered. (This depends on finalization from grants curators).</td></tr><tr><td style="width:29.1717%; height:49px;">Support Channel</td><td style="width:27.1426%; height:49px;">Daily through out the year</td><td style="width:43.6857%; height:49px;">Maintain as builders support communication channel in SEA market, provide mentorship, coordinate with ecosystem players (Marketing Bounty, Meetup Bounty, etc), make sure all builders acquire a mix of resources to go-to-market (including finance, ecosystem connection, marketing support, community engagement).</td></tr><tr><td style="width:29.1717%; height:49px;">Event Representation</td><td style="width:27.1426%; height:49px;">10 Events (at least)</td><td style="width:43.6857%; height:49px;">Represent Polkadot in SEA extraodinary events, acquiring speaking slots for Polkadot’s representatives communication, podcasts and stuffs.</td></tr><tr><td style="width:29.1717%; height:49px;">Established Strategic partners</td><td style="width:27.1426%; height:49px;">20-25 entities</td><td style="width:43.6857%; height:49px;">Establish strategic relationship with more than 20 entities across SEA market (Community Partners, Key Universities, Organizations) for educational and builders onboarding efforts.</td></tr><tr><td style="width:29.1717%; height:49px;">Onboarding open-source projects</td><td style="width:27.1426%; height:49px;"><blockquote>10 projects</blockquote></td><td style="width:43.6857%; height:49px;">Continue our job as finding builders contributing open-source small projects for Open Contribution Bounty.</td></tr></tbody></table></div>

**WHY OPENGUILD IMPORTANT TO POLKADOT ECOSYSTEM IN 2025-2026?**

OpenGuild has grown into an irreplaceable team and community of core contributors to Polkadot in Asia. We’ve built strong connections with key ecosystem players while also becoming deeply embedded in Web3 builder communities across the region—making us a true native Polkadot builder hub in Asia.

2025-2026 is a huge year for Polkadot with major upgrades like Polkadot Cloud, Polkadot Hub, and JAM. OpenGuild is here to bridge the gap for Asian builders, helping them navigate these changes, providing mentorship and guidance, and making sure they have the right tools and knowledge to choose the best blockchain for their Web3 projects.

We’re not just about sharing updates—we’re about creating a welcoming and accessible space where builders across Asia can connect, collaborate, and grow together. Our goal is to make the Polkadot ecosystem easier to approach and work with, ensuring builders feel supported in their journey.

With exciting plans and partnerships in motion, OpenGuild is set to become the go-to builder hub for Southeast Asia and beyond. By tapping into existing resources and upcoming GTM partnerships, we’re making it easier than ever for builders to dive into Polkadot and be part of something big.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

READ OUR FULL PROPOSAL - **[HERE](https://openguild.notion.site/PROPOSAL-OpenGuild-Accelerate-Polkadot-Builder-Community-in-SEA-market-154659b1c81780beb814cdaa0a005308)**

[PROPOSAL] OpenGuild - Accelerate Polkadot Builder Activation in SEA & Broader Asia

- This proposal aims to improve how users can transfer USDT and USDC, which are stablecoins, to the Polkadot system.
- Many users face difficulties because there's not enough liquidity to use these stablecoins once they arrive in Polkadot.
- The proposal asks for funds to create liquidity pools so users can swap their stablecoins for DOT tokens, which they need to pay fees.
- The plan includes converting the stablecoins to wrapped versions and creating pairs with DOT on Polkadot Asset Hub.
- Fixing these issues will help more people use the Polkadot ecosystem, as it currently makes onboarding hard for new users.
- The funds will be managed by a two-person multisignature team to ensure safety.
- The aim is to provide a better user experience and encourage more people to use Polkadot's tools.

Provision of Snowbridge-Wrapped USDT & USDC Liquidity to Facilitate Fee Swaps

- The community made big changes to the Educational & Outreach Track based on feedback from members.
- They also updated other tracks for improvement.
- There is a referendum to get more money for the Anti-Scam Bounty, which helps protect people from scams.
- The Anti-Scam Bounty has been active for three years and helps fund safety activities.
- They are asking for $369,610 to help with their budget.
- Thanks to new tools, the budget has been lowered by 46%.
- More details about spending and future goals can be found in a proposal document.

[Medium Spender] Referendum #1490

PolkaGate is a team of Polkadot enthusiasts who created a MetaMask Snap to improve the user experience for interacting with Substrate-based chains like Polkadot and Kusama. The Snap allows users to manage assets, participate in staking and governance, and transfer tokens directly within MetaMask. The proposal requests retroactive funding for the development and key feature implementations of the PolkaGate MetaMask Snap over the past four months. The requested allocation is 53,600 USD.

Key features of the PolkaGate MetaMask Snap include:
1. Sign Transactions: Execute transactions on supported Polkadot networks.
2. Sign with Metadata: Support for signing transactions even when APIs are unavailable.
3. Fund Transfers: Send tokens (e.g., DOT, KSM) directly within MetaMask.
4. Staking Support: Configure solo and pooled staking, manage rewards, and unstake efficiently.
5. Enhanced UI: Interactive interface with JSX elements for improved usability.
6. Account Export: Securely export accounts as JSON files.
7. Whitelisted dApp Support: Seamless integration with staking platforms, governance dApps, and PolkaGate apps.

The PolkaGate team consists of G. Kami Ekbatanifard (Founder/CEO & Engineering Team Lead), Morteza Chalaki (CFO), Mehran Pourvahab (Blockchain researcher & TS Engineer), Martin Azarbad (UI/UX specialist), and Amir H. Ekbatani (Test engineer).

Upcoming features for the PolkaGate MetaMask Snap include smart contract support, bridging Ethereum to Polkadot, token swapping, and user-requested features. The team is committed to continuously improving the user experience and providing a comprehensive solution for Polkadot and Kusama users.

Proponent: 17VdcY2F3WvhSLFHBGZreubzQNQ3NZzLbQsugGzHmzzprSG (PolkaGate)  
Date: 25.2.2025  
Requested allocation: 53,600 USD  
  
![Polkadot in MetaMask](https://i.ibb.co/CpQJQP87/Polka-Gate-02.png)

**1\. Proposal Overview**

1.1 Introduction  
This proposal seeks retroactive funding for the development and key feature implementations of the PolkaGate MetaMask Snap over the past four months. These updates significantly enhance MetaMask’s usability for Polkadot users by introducing support for staking, fund transfers, and UI improvements.  
  
Product Page:  [https://snaps.metamask.io/snap/npm/polkagate/snap](https://snaps.metamask.io/snap/npm/polkagate/snap)  
Staking Feature Announcement Video: [https://x.com/PolkaGate/status/1889391109610283166](https://x.com/PolkaGate/status/1889391109610283166)

**2\. Context of the Proposal**

2.1 About PolkaGate  
PolkaGate is a dedicated team of Polkadot enthusiasts focused on enhancing the user experience for interacting with Substrate-based chains like Polkadot and Kusama. Through our MetaMask Snap project, we aim to simplify complex processes such as asset management, staking, and governance participation. By integrating seamlessly with MetaMask, PolkaGate empowers users to manage their digital assets and actively engage with the Polkadot network. PolkaGate is committed to lowering entry barriers, making the Polkadot ecosystem more accessible to both newcomers and experienced users.

  
2.2 Overview of Product  
PolkaGate MetaMask Snap enables Polkadot and Kusama users to manage assets and participate in staking and governance directly through MetaMask. This integration extends the Polkadot ecosystem’s accessibility to millions of MetaMask users. The Snap supports multiple tokens, including testnet assets like Westend and Paseo, and displays balances directly on the home page for easy tracking. Users can transfer tokens within MetaMask without relying on external dApps. By integrating directly with MetaMask, users benefit from a frictionless experience in managing assets and participating in staking and governance.  
  

**![](https://i.ibb.co/CsbtYhB5/Meta-Mask-snaps-01-1.png)  
  
3. Features**  
  
PolkaGate Snap extends beyond basic transaction signing by integrating an interactive JSX-supported UI and advanced staking options. It aims to evolve into a full-featured Polkadot wallet within MetaMask.  
  
3.1. Current Features:  
  
Sign Transactions: Execute transactions on supported Polkadot networks.  
Sign with Metadata: Support for signing transactions even when APIs are unavailable.  
Fund Transfers: Send tokens (e.g., DOT, KSM) directly within MetaMask.  
Staking Support: Configure solo and pooled staking, manage rewards, and unstake efficiently.  
Enhanced UI: Interactive interface with JSX elements for improved usability.  
Account Export: Securely export accounts as JSON files. Whitelisted dApp Support: Seamless integration with staking platforms, governance dApps, and PolkaGate apps.  
(Details are in the [full document](https://docs.google.com/document/d/152KdWi5kNr3l04bOPsg4LAzaRW4M8sibArWTIl7MB_Q/edit?usp=sharing))  
  
**4\. Projected Allocation & Budget**

4.1 Team Members and Roles

The PolkaGate team consists of the following key members who have contributed to the project’s success:  
G. Kami Ekbatanifard, PhD — Founder/CEO & Engineering Team Lead  
Morteza Chalaki, BA — CFO  
Mehran Pourvahab, PhD — Blockchain researcher & TS Engineer  
Martin Azarbad, BA — UI/UX specialist  
Amir H. Ekbatani, PhD candidate — Test engineer

4.2 Payment Breakdown  
![](https://i.ibb.co/99wXhjkF/Screenshot-2025-02-25-at-17-36-18.png)  
  

**5\. Upcoming Features**

These upcoming features will enhance the MetaMask Snap by introducing advanced functionalities such as token swapping and improved smart contract support. They align with our vision of continuously improving user experience and providing a comprehensive solution for Polkadot and Kusama users.  
  

Smart Contract Support: Exploring integration with asset hubs.  
Bridge Ethereum to Polkadot  
Token Swapping: Researching seamless in-app swaps.  
User-Requested Features: Prioritizing enhancements based on community feedback.  
  

**6\. Links and References**

In this section, we provide essential links to access our resources and stay connected with the PolkaGate community:

6.1 Official Website and Documentation

Product link:  [https://snaps.metamask.io/snap/npm/polkagate/snap](https://snaps.metamask.io/snap/npm/polkagate/snap)  
Website: [polkagate.xyz](https://polkagate.xyz)  
Documentation: [docs.polkagate.xyz](https://docs.polkagate.xyz)  
X: [x.com/@polkagate](https://x.com/@polkagate)  
YouTube: [youtube.com/@polkagate](https://youtube.com/@polkagate)  
Element: [matrix.to/#/#polkagate:matrix.org](https://matrix.to/#/#polkagate:matrix.org)  
GitHub: [github.com/polkagate](https://github.com/polkagate)  
  

6.2 Notable Announcements

Staking Feature Announcement Video: [Watch on X](https://x.com/PolkaGate/status/1889391109610283166)  
  
  

[Click to view the full document on Google Docs.](https://docs.google.com/document/d/152KdWi5kNr3l04bOPsg4LAzaRW4M8sibArWTIl7MB_Q/edit?usp=sharing)

PolkaGate MetaMask Snap: Retroactive Funding Proposal (Oct 2024 - Jan 2025)

- Polkadot plans to work with Laura Shin and Unchained in 2025.  
- They will share Polkadot news on podcasts, newsletters, and websites.  
- The goal is to teach people about Polkadot’s technology.  
- The audience includes crypto fans, developers, and investors.  
- Podcasts and newsletters will feature Polkadot ads and stories.  
- Success will be measured by views, likes, and feedback.  
- The project starts in March 2025 and runs weekly.  
- The team includes experts in media, finance, and crypto.

In 2025, we hope Polkadot will expand its successful partnership with Laura Shin and Unchained. This collaboration will showcase Polkadot and its related projects across Unchained's media platforms, including our Podcast, Newsletter, and Website. Through this partnership, Polkadot's messaging will reach a highly influential audience in the crypto space, including tech CEOs, CTOs, developers, hedge fund managers, family offices, VCs, traders, and other key players.

**1\. Context of the proposal**

This proposal is presented by Laura Shin and Unchained for the Polkadot DAO, aiming to build off our strategic partnership that enhances the visibility and engagement of the Polkadot ecosystem. As a leading independent media outlet in the cryptocurrency space, Unchained seeks to leverage its platform to promote Polkadot’s initiatives, projects, and community efforts, thereby fostering a deeper understanding of its technology among a broader crypto audience.

**2\. Objective**

**Defining Success:** Success will be measured through a combination of quantitative and qualitative metrics:

Key Performance Indicators (KPIs):

1. Episode Engagement: Deliver guaranteed impressions against all podcast episodes and newsletters that Polkadot will be sponsoring
2. Social Media: Deliver added value impressions from Laura Shin’s Twitter account to create awareness for Polkadot initiatives.
3. Audience Interaction: Enhance listener engagement through comments and shares.
4. Feedback Collection: Attain a positive satisfaction rate from listener surveys at the end of the campaign.

**Quality Assurance:** We will maintain high standards through regular content reviews, listener feedback mechanisms, and analytics assessments to ensure alignment with our success metrics.

**3\. Description**

The primary goal of this proposal is to leverage both the Unchained Podcast and the Unchained newsletter as key marketing vehicles to promote the Polkadot ecosystem. By integrating Polkadot-related content into both platforms, we aim to educate our audience about Polkadot’s technology, projects, and community initiatives, thereby fostering greater engagement and understanding of the Polkadot ecosystem.

**Target audience:** 

Crypto Enthusiasts: Individuals interested in the latest cryptocurrency and blockchain technology developments.

Developers and Technologists: Professionals seeking insights into building on the Polkadot platform.

Investors (Retail, VC’s, and Family Offices): Those looking for information on investment opportunities within the Polkadot ecosystem.

CEO, CTO’s, Project Leads: The leaders of different crypto projects

General Public: Individuals curious about blockchain innovations and their implications.

**Scope of the proposal**

- Podcast Episodes: Each episode will have host-read ads by Laura Shin that cover specific projects or technological advancements within Polkadot.
- Newsletter Content Integration: Regular features in the newsletter that highlight Polkadot projects, summarize podcast episodes, and include educational articles explaining its unique technology and governance model.
- Cross-Promotion Strategies: Utilizing both platforms to drive traffic between the podcast and newsletter, encouraging our audience to visit specific Polkadot-owned and Polkadot affiliate websites.

Assistance we will need to carry on with the project: We will require scripts for the podcast's host-read ads and ad copy for the newsletter.

Currently, we are not collaborating with any other projects in the ecosystem

This proposal is designed for scalability.

By utilizing the Unchained Podcast and newsletter as marketing vehicles for the Polkadot DAO, we aim to create a synergistic relationship that enhances the visibility of the Polkadot ecosystem.

**Milestones and Deliverables**

The following table outlines the key tasks necessary to plan, execute, and follow up on the proposal for promoting the Polkadot ecosystem through the Unchained Podcast and newsletter, with a launch date of March 31, 2025. The plan includes featuring Polkadot in two podcast episodes per week (Tuesdays and Fridays) and weekly newsletter highlights. The costs are outlined based on the discounted rates for both the podcast and newsletter.

<div class="joplin-table-wrapper"><table style="border-collapse: collapse; width: 100%; height: 217px;" border="1"><tbody><tr style="height: 49px;"><td style="width: 24.9608%; height: 49px;">Milestone</td><td style="width: 24.9608%; height: 49px;">Deliverable</td><td style="width: 24.9608%; height: 49px;">Deadline</td><td style="width: 24.9608%; height: 49px;">Cost</td></tr><tr style="height: 21px;"><td style="width: 24.9608%; height: 21px;"><ol><li>Proposal Submission</li></ol></td><td style="width: 24.9608%; height: 21px;">Submit proposal to Polkadot DAO for review</td><td style="width: 24.9608%; height: 21px;">March 11th, 2025</td><td style="width: 24.9608%; height: 21px;">-</td></tr><tr style="height: 21px;"><td style="width: 24.9608%; height: 21px;">&nbsp;</td><td style="width: 24.9608%; height: 21px;">Receive feedback and approval from Polkadot DAO</td><td style="width: 24.9608%; height: 21px;">March 18th, 2025</td><td style="width: 24.9608%; height: 21px;">-</td></tr><tr style="height: 21px;"><td style="width: 24.9608%; height: 21px;"><ol start="2"><li>Content Planning</li></ol></td><td style="width: 24.9608%; height: 21px;">Develop a content calendar for podcast episodes and newsletter integrations focused on Polkadot</td><td style="width: 24.9608%; height: 21px;">March 23th, 2025</td><td style="width: 24.9608%; height: 21px;">&nbsp;</td></tr><tr style="height: 21px;"><td style="width: 24.9608%; height: 21px;">&nbsp;</td><td style="width: 24.9608%; height: 21px;">Finalize content strategy without guest speakers from Polkadot</td><td style="width: 24.9608%; height: 21px;">March 30th, 2025</td><td style="width: 24.9608%; height: 21px;">&nbsp;</td></tr><tr style="height: 21px;"><td style="width: 24.9608%; height: 21px;"><ol start="3"><li>Production Phase</li></ol></td><td style="width: 24.9608%; height: 21px;">Record and edit the first series of podcast episodes</td><td style="width: 24.9608%; height: 21px;">March 30th, 2025</td><td style="width: 24.9608%; height: 21px;">&nbsp;</td></tr><tr style="height: 21px;"><td style="width: 24.9608%; height: 21px;">&nbsp;</td><td style="width: 24.9608%; height: 21px;">Draft and finalize newsletter content related to Polkadot</td><td style="width: 24.9608%; height: 21px;">March 30th, 2025</td><td style="width: 24.9608%; height: 21px;">&nbsp;</td></tr><tr style="height: 21px;"><td style="width: 24.9608%; height: 21px;"><ol start="4"><li>Launch Campaign</li></ol></td><td style="width: 24.9608%; height: 21px;">Publish the first podcast episode featuring Polkadot content/ad reads by Laura Shin</td><td style="width: 24.9608%; height: 21px;">March 31st, 2025</td><td style="width: 24.9608%; height: 21px;">&nbsp;</td></tr><tr style="height: 21px;"><td style="width: 24.9608%; height: 21px;">&nbsp;</td><td style="width: 24.9608%; height: 21px;">Distribute the first newsletter edition highlighting Polkadot as the title sponsor.</td><td style="width: 24.9608%; height: 21px;">March 31st, 2025</td><td style="width: 24.9608%; height: 21px;">&nbsp;</td></tr></tbody></table></div>

**Ongoing Production (Weekly)**

| | | |
| --- | --- | --- |
| Task | Frequence | Cost per week |
| Podcast Episodes Featuring Polkadot | 2 episodes/week | 7,000 USDT (discounted from 9,000 USDT) |
| Newsletter Featuring Polkadot Content | 4 newsletters/week | 1,000 USDT (discounted from 1,500 USDT) |

Annual Cost Breakdown

- Podcast Costs: $8,750 per week x 52 weeks = 455,000 USDT
 - **Polkadot Dicounted Pricing**: 7,000 USDT per week x 52 weeks = 364,000 USDT
- Newsletter Costs: 1,500 USDT per week x 52 weeks = 78,000 USDT
 - **Polkadot Dicounted Pricing**: 1,000 USDT per week x 52 weeks = 52,000 USDT
- Total Annual Cost: 455,000 USDT +$78,000 USDT = 533,000 USDT
 - **Polkadot Dicounted Pricing**: 364,000 USDT + 52,000 USDT = 416,000 USDT (117,000 USDT discount)

**Milestone Packaging in 50,000 USDT Increments**

To meet the requirement that every milestone is at most 50,000 USDT we can break down the annual budget as follows.

**Milestone #1A:** 6 weeks (March to April) Covers the first six podcast episodes (6 weeks) and newsletters (6 editions). Total Cost: Podcasts: 7,000 USDT x 6 = 42,000 USDT Newsletters: 1,000 USDT x 6 = 6,000 USDT Total for Milestone #1A: 48,000 USDT

**Milestone #2A:** 6 weeks (April to May) Covers the first six podcast episodes (6 weeks) and newsletters (6 editions). Total Cost: Podcasts: 7,000 USDT x 6 = 42,000 USDT Newsletters: 1,000 USDT x 6 = 6,000 USDT Total for Milestone #2A: 48,000 USDT

**Milestone #3A through #9A:** Each milestone will be 6 weeks

**5\. Team**

Registered Company: Laura Shin Media, LLC

Address: PO Box 4668 #24974, New York, NY 10163

We ran over 100 host-read, integrated ads for Polkadot on the Unchained Podcast. Below are two examples. Additionally, we delivered over 10 million audio and video impressions for Polkadot through this sponsorship.

- Pre-Roll: [https://youtu.be/GZJz5bRxXFQ?t=117](https://youtu.be/GZJz5bRxXFQ?t=117)
- Midroll: [https://youtu.be/GZJz5bRxXFQ?t=2446](https://youtu.be/GZJz5bRxXFQ?t=2446)

We are one of the top-rated and most trusted media outlets within the crypto community. We have been a Polkadot media partner for one year.

Team Members

1. Laura Shin
 1. Role: Founder and Host of Unchained Podcast
 2. Contribution: Laura leads the overall strategy and content creation for the podcast and newsletter, ensuring that all materials are informative and engaging. With her extensive background in crypto journalism, she will provide insights and in-depth interviews with the most influential personalities within the blockchain ecosystem.
 3. LinkedIn: [https://www.linkedin.com/in/laurashin/](https://www.linkedin.com/in/laurashin/)
 4. Twitter: [https://x.com/laurashin](https://x.com/laurashin)
2. Mohammad Ali
 1. Role: Sales Lead
 2. Contribution: Mohammad brings extensive experience in advertising and marketing, focusing on developing strategies to promote advertising content effectively. His expertise will help drive audience engagement and expand Polkadot’s reach through targeted marketing efforts.
 3. LinkedIn: [https://www.linkedin.com/in/mohammadali2/](https://www.linkedin.com/in/mohammadali2/)
3. Juan Aranovich
 1. Role: Managing Editor at Unchained
 2. Contribution: Juan oversees editorial content and research for the podcast and newsletter, ensuring high-quality information is presented to the audience. His background in economics and finance will contribute to deeper analysis of the crypto ecosystem. LinkedIn: [https://www.linkedin.com/in/juanpabloaranovich/](https://www.linkedin.com/in/juanpabloaranovich/)
4. Scott Williams Jr., CPA
 1. Role: CFO at Laura Shin Media and Unchained
 2. Contribution: Scott provides financial oversight and strategic guidance for the campaign, leveraging his finance background to ensure budget management and effective allocation of resources throughout the project.
 3. LinkedIn: [https://www.linkedin.com/in/scottwilliamsjr/](https://www.linkedin.com/in/scottwilliamsjr/)

Laura Shin's Unchained

- Paseo Network wants to keep doing good work in 2025 and needs money to do it.
- They are asking for $640,000 from the Polkadot treasury to pay for their operations.
- The money will be used to pay for services every three months for a whole year.
- They plan to make it easier to manage money by making some changes.
- These changes include using new helpers, paying at the end of each quarter, and making payments automatic.
- They also want to make sure the people providing services are doing a good job.
- Everyone interested can read more about the proposal and share their thoughts.

To sustain and enhance <a href="https://github.com/paseo-network">Paseo Network's</a> impact, this proposal seeks funding to continue operations in 2025, ensuring the same high level of service from a dedicated group of ecosystem contributors.
We are requesting a top-up of $653,500.00 from the Polkadot treasury to cover operational costs for 2025. The funds will be managed via the original <a href="https://polkadot.subsquare.io/treasury/bounties/37">Paseo Bounty (#37)</a>, with payments distributed quarterly over the 12-month funding period.
Along with this funding request, we are proposing several efficiency improvements to make bounty management more transparent and automated. These include changing the curator set, retroactive payments at the end of each quarter, eliminating the need for manual payout requests, automating validator payouts, and implementing performance-based benchmarks to ensure validators and service providers meet expected reliability standards.
For more information, we encourage ecosystem participants to <a href="https://docs.google.com/document/d/195BTcx_rz3tx-PWIxc7T5VQjeXaolx09ltT7KxYIQ0k/edit?usp=sharing">review the full proposal</a>&nbsp;

Paseo - Developer Testnet Bounty Top-up Request

[Runtime 1.4.2] Upgrade Polkadot Asset Hub and Collectives

- The proposal is about continuing to fund RPC Providers for six months plus one extra month.
- The total funding needed is $171,951.34, which is about $22,142 each month.
- Bounty 31 is a project that helps pay vendors for specific services on Polkadot.
- Service providers will bid for this funding based on the needs set by curators.
- The best providers that meet quality standards will be given the funding.
- This plan helps reduce the need for more proposals and keeps costs fair.
- If providers don't meet the quality, they might lose their funding.

Dear community,
I present this proposal on the authorization of the curators of bounty 31.
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 31 which awards vendors for RPC services on the Polkadot relay-chain as well as its system parachains. The total cost for such provision is USD$171,951.34, which represents $22,141.98 per month without contingency and administrative expenses.
Bounty 31 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 31

- A new call wants to increase the number of validators from 500 to 600.
- This is following a previous change that increased the number from 400 to 500.
- With more validators, Polkadot can support more cores, going from 100 to 120.
- A "validator" helps keep the system safe and running.
- Kusama, a related network, already has 600 validators since January 22, 2025.

[Whitelisted Caller] Increase validator set size to 600

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. It demonstrates how to effectively integrate and use the JAM SDK and serves as a practical example for other developers wishing to build similar services. The project encourages the adoption of the JAM SDK by providing a real, easily adaptable use case for other functional services and offers a modular and extensible solution that can adapt to various authorization scenarios in decentralized applications. Guidance documentation is available in multiple languages.

The execution workflow 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 also suggests potential applications in the Polkadot Blockchain Academy and connection with video games like DOOM executed 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)

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/vxhGQMyx/1.jpg)

2.view main menu

![](https://i.ibb.co/j9JtvvCm/2.jpg)

3.Select option 1: Admin validation and selection of number of questions to ask

![](https://i.ibb.co/5h7B3tKK/3.jpg)

4.Select option 2: Participant validation and answering questions

![](https://i.ibb.co/rXCyxdq/4.jpg)

5.Select option 3: Observer validation and viewing answers

![](https://i.ibb.co/zhZc47b4/5.jpg)

6.Select option 4: Verification of user roles and identification vectors

![](https://i.ibb.co/kgxJqtq1/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 and feel free to share questions and comments =)

Note: Thanks Gav and Parity team by this interesting piece of software

[Retroactive Funding] JAM SDK Implementation of reusable service

- Bearofthenet is a hobby racer from Austria.
- He wants to represent Polkadot, a cryptocurrency, at European racetracks.
- He participates in about 5 racing weekends each year, mostly in Austria and nearby countries.
- Around 200 riders race each weekend, meaning many people will see his special suit.
- He plans to share pictures and videos of his races on social media.
- He needs support to cover the costs of his custom racing suit.
- He loves combining motorsport with technology like web3.

Hello everyone,

On „X“ I am „bearofthenet“.

Im a hobby racer from Austria and would love to represent polkadot on the european racetracks.

In this motorsport you see sponsoring everywhere but i never saw any rider wearing some crypto stuff.  
Just want to say im not a professional attending international races, we are just a group of petrolheads living our dream🔥

I usually attend about 5 race weekends per year, the most tracks are spread over Austria, Hungary, Slovakia and Croatia, eventually italy.

About 200 riders attend per wekend, so minimum 1000 riders will see this exclusive suit per year and ill be wearing that suit minimum for 4 Years.

ill post trackpics and reels tagging Polkadot after every event on X and other social plattforms.

The requested amount will be just enough to cover most costs of this tailormade suit.

Hope you find the idea of combining the passion for motorsport and web3 as exciting as i do.

Bear

![](https://i.ibb.co/QvJ5gYc3/s2.jpg)

![](https://i.ibb.co/ds4b4hm3/s1.jpg)

![](https://i.ibb.co/MyTp6M7s/b1.jpg)

Motorsport Sponsoring Superbike / Polkadot Racesuit

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.

small_tipper

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

Set PoV size limit to 10 Mb

wish_for_change

staking_admin

treasurer

lease_admin

fellowship_admin

general_admin

auction_admin

OpenGov Referenda

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 250 DOT from the treasury at once.

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.

OpenGov Referenda

Referenda Tracks