diff --git a/README.md b/README.md
index 550b5d50fa2..7a270927d7c 100644
--- a/README.md
+++ b/README.md
@@ -90,11 +90,9 @@ In cases where a niche expert opinion is desirable, one of the committee members
- [Aeron Buchanan](https://github.com/aeronbuchanan)
- [Gautam Dhameja](https://github.com/gautamdhameja)
- [David Hawig](https://github.com/Noc2)
-- [Diogo Mendonça](https://github.com/dsm-w3f)
- [Sebastian Müller](https://github.com/semuelle)
- [Bill Laboon](https://github.com/laboon)
- [Keegan Quigley](https://github.com/keeganquigley)
-- [Nikhil Ranjan](https://github.com/nikw3f)
- [Raul Romanutti](https://github.com/rrtti)
- [Seraya Takahashi](https://github.com/takahser)
- [Benjamin Weiß](https://github.com/BenWhiteJam)
@@ -105,10 +103,8 @@ In cases where a niche expert opinion is desirable, one of the committee members
Evaluators are individuals able to evaluate the technology delivered as a result of the Grants Program. The committee has the right to add or remove evaluators on the basis of supermajority.
- [David Hawig](https://github.com/Noc2)
-- [Diogo Mendonça](https://github.com/dsm-w3f)
- [Sebastian Müller](https://github.com/semuelle)
- [Keegan Quigley](https://github.com/keeganquigley)
-- [Nikhil Ranjan](https://github.com/nikw3f)
- [Seraya Takahashi](https://github.com/takahser)
#### W3F Operations Team
@@ -116,7 +112,6 @@ Evaluators are individuals able to evaluate the technology delivered as a result
The Operations Team takes care of legal documents, invoicing, and remittances.
- [Melanie Diener](https://github.com/meldien)
-- [Federica Dubbini](https://github.com/fededubbi)
- [Rouven Pérez](https://github.com/RouvenP)
diff --git a/applications/Calamar.md b/applications/Calamar.md
index a7953c14400..ff52a1eae69 100644
--- a/applications/Calamar.md
+++ b/applications/Calamar.md
@@ -69,26 +69,31 @@ As we are gathering feedback, one of the most important features for the users s
- account's name if set
- owned assets accross all listed chains, including dollar values and graphs for visualization.
- list all chain-specific addresses
- - list all related transfers, XCM transfers, extrinsics and calls
+ - list all related transfers, extrinsics and calls
-
+
#### Chain dashboards
Each chain will have own dashboard with statistics and listing of latest blocks, latest transfers, top holders, etc. It makes the explorer more useful even for users who are not searching for specific items.
-
+
-#### Cross-chain transfers
-Important feature is to create good UI for displaying information about XCM teleports and other cross-chain transfers where you can easily see all involved sides (chains, accounts) and other useful data.
+#### Metadata explorer
-- XCM transfer detail
+The runtime metadata of each chain are still evolving and changing but it is not so easy to display them in a structured and human-readable way. There is e.g. a tool https://wiki.polkadot.network/docs/metadata which displays them but only latest version and supports only a few networks. The metadata explorer we are going to implement will support all the networks and also historical versions of the runtime spec.
-
+
-- in transfers table
+#### Item metadata
-
+The metadata information will be deeply integrated into whole Calamar so we can display it in the detail pages of the items. E.g. in extrinsic's detail page we will show info for the call name, error, parameters and link to the metadata explorer for more info.
+
+
+
+#### Search input autocomplete for call and event names
+
+Thanks to the metadata we can also autocomplete and suggest the call and event names when typing into the search input.
### Technology stack
@@ -203,7 +208,7 @@ Even though we have the already working application, there are still many things
| 10. | Website polishing | Add useful information to the website (footer with team logos, contact information, terms, etc.). |
| 11. | Polkadot.js integration | Create a PR to integrate links to the Calamar Explorer into Polkadot.js app. |
-### Milestone 2 - Account detail & Cross-chain transfers
+### Milestone 2 - Account detail & Chain dashboards
- **Estimated duration:** 4 weeks
- **FTE:** 1
@@ -232,10 +237,10 @@ In this milestone we are going to improve [account detail](#account-detail) page
| 10. | Chain dashboard / Top holders | Add top holders list table |
-### Milestone 3 - Universal search & Chain dashboards
+### Milestone 3 - Universal search & Metadata explorer
-- **Estimated duration:** 3 weeks
-- **FTE:** 1
+- **Estimated duration:** 8 weeks
+- **FTE:** 0.375
- **Costs:** $7,500
In this milestone we are going to implement [universal search](#universal-search) and one of the most requested features: [cross-chain transfers](#cross-chain-transfers) detection.
@@ -248,12 +253,16 @@ In this milestone we are going to implement [universal search](#universal-search
| 0d. | Docker | *N/A - will be provided by the first milestone.* |
| 0e. | Article | We will publish an article that explains what was done as part of the grant |
| 1. | Universal search | Search items through all the chains without the knowledge where it belongs. See [Universal search](#universal-search). |
-| 2. | XCM transfers and teleports | Detect cross-chain transfers and display relevant information of involved chains and accounts: from chain, to chain, relayed at chain (reserve), sender, beneficiary, etc. Also add their listings to account detail and chain dashboard. See [Cross-chain transfers](#cross-chain-transfers) for more. |
+| 2. | Metadata explorer | UI interface for exploring metadata retrieved from network's latest and historical versions of runtime spec. See [Metadata explorer](#metadata-explorer).
+| 3. | Show related runtime metadata in items' detail | Show related metadata information directly in detail pages of individual items and interlink to metadata explorer. See [Item metadata](#item-metadata).
+| 4. | Search input autocomplete | Autocomplete extrinsic and event name in the search input. See [Search input autocomplete for call and event names](#search-input-autocomplete-for-call-and-event-names).
## Future Plans
There is a huge potential for future improvements which the Polkadot's community can benefit from.
+We would like to definitely display information about XCM transfers and teleports.
+
As developers of most parachains implement their own custom modules/pallets it opens the opportunity to cooperate and customize Calamar explorer with UI/UX components and logic tailored to their needs.
It relates to various XCM transactions which makes it even more complex and the more types will our explorer support the more it makes the users' lives easier.
diff --git a/applications/Claps.md b/applications/Claps.md
index 885da5632f0..200d8c0b6b8 100644
--- a/applications/Claps.md
+++ b/applications/Claps.md
@@ -3,6 +3,7 @@
- **Team Name:** Taiwan Research-based Biopharmaceutical Manufacturers Association
- **Payment Address:** 0x39D3E0c7AAcfbCa133f08cfb153B4888fd36bA9B (DAI)
- **[Level](https://github.com/w3f/Grants-Program/tree/master#level_slider-levels):** 2
+- **Status:** [Terminated](https://github.com/w3f/Grants-Program/pull/1440#issuecomment-1773610786)
## Overview
diff --git a/applications/CoinFabrik_On_Ink_Integration_Tests_2.md b/applications/CoinFabrik_On_Ink_Integration_Tests_2.md
new file mode 100644
index 00000000000..684228a91ea
--- /dev/null
+++ b/applications/CoinFabrik_On_Ink_Integration_Tests_2.md
@@ -0,0 +1,182 @@
+# CoinFabrik On Ink Integration Tests 2
+- **Team Name:** CoinFabrik (Nektra S.A)
+- **Payment Address:** 0xf488039EDe6B38D7689fDCC6A9FC2dd0EF39D54e (USDC)
+- **[Level](https://github.com/w3f/Grants-Program/tree/master#level_slider-levels):** 2
+
+## Project Overview :page_facing_up:
+
+### Overview
+
+We have discovered that integration tests for ink! contracts lack some of the functionalities, or present implementation differences, when compared to E2E testing.
+
+Integration tests run significantly faster than E2E (end-to-end) tests. If a full range of functionalities were provided, it could reduce testing and QA times.
+
+Our intention is to `flatten the anvil` of ink! integration testing. With a properly flattened anvil, quality tools can be built.
+
+
+### Project Details
+
+We have conducted a comprehensive analysis to identify any missing functionalities in integration tests and implementation differences with E2E tests, and to propose and develop new testing features based on our findings. This analysis was carried as part of a previous grant ([link](https://github.com/w3f/Grant-Milestone-Delivery/pull/998)).
+
+With this new grant, our objective is to implement our findings. Specifically, we aim to address functions in integration testing that have missing implementations or show differences when compared to e2e tests. We will add our contributions into the [ink! project repository](https://github.com/paritytech/ink ) following existing [contribution guidelines](https://github.com/paritytech/ink/blob/master/CONTRIBUTING.md).
+
+### Ecosystem Fit
+
+Having a comprehensive set of functionalities available for integration tests would bring numerous benefits to the entire community, including improved reliability, code quality and maturity, and faster feedback loops.
+
+Integration tests are useful during their development and they are quicker than E2E tests. We learned this while working on fuzzing detection techniques during the [Proof of Concept of Scout](https://github.com/CoinFabrik/web3-grant), which we performed in collaboration with [researchers from the University of Buenos Aires](https://lafhis.dc.uba.ar/home). We believe that having a complete set of functionalities for integration tests would be useful for other teams working in the development of ink! smart contracts.
+
+## Team :busts_in_silhouette:
+
+### Team members
+
+- Ariel Wassbein, Head of Research.
+- Agustin Aon, Technical Lead.
+- Valeria Caracciolo, Business Development.
+- CoinFabrik's development and QA teams.
+
+### Contact
+
+- **Contact Name:** Valeria Caracciolo
+- **Contact Email:** valeria.caracciolo@coinfabrik.com
+- **Website:** https://www.coinfabrik.com/
+
+### Legal Structure
+
+- **Registered Address:** Dr. Emilio Ravignani 2394, C1425 CABA, Argentina.
+- **Registered Legal Entity:** Nektra S.A.
+
+### Team's experience
+
+We are a research and development company specialized in Web3, with a strong background in cybersecurity. Founded in 2014, we have worked on over 200 blockchain-related projects, EVM based and also for Solana, Algorand, and Polkadot. Beyond development, we offer security audits through a dedicated in-house team of senior cybersecurity professionals, currently working on code in Substrate, Solidity, Clarity, Rust, and TEAL.
+
+Our team has an academic background in computer science and mathematics, with work experience focused on cybersecurity and software development, including academic publications, patents turned into products, and conference presentations. Furthermore, we have an ongoing collaboration on knowledge transfer and open-source projects with the University of Buenos Aires.
+
+As well, CoinFabrik has been providing Quality Assurance as a service to development teams, accumulating valuable expertise in the field for a considerable period of time. Our clients highly appreciate this service, and as a result, we are eager to expand our capabilities to the ink! ecosystem.
+
+
+### Team Code Repos
+
+- https://github.com/CoinFabrik
+- https://github.com/CoinFabrik/on-ink-integration-tests
+- https://github.com/CoinFabrik/scout
+- https://github.com/CoinFabrik/web3-grant
+
+### Team LinkedIn Profiles (if available)
+
+- https://www.linkedin.com/in/arielwaissbein/
+- https://www.linkedin.com/in/agustin-aon/
+- https://www.linkedin.com/in/valeriacaracciolo/
+
+
+## Development Status :open_book:
+
+We have identified 24 functions exposed for their usage in integration and E2E tests in the file [env_access.rs](https://github.com/paritytech/ink/blob/master/crates/ink/src/env_access.rs) of the ink! repository. Of these 24 functions, we determined that there are 9 functions to work on with explicit plans, and 13 functions for which there might be implementation differences that remain to be analyzed. Two functions were deemed unfeasible for their implementation in the integration testing environment.
+
+
+**Table 1: Status of functions exposed in integration and e2e testing environments.**
+| Issue Number | Function | Implemented Integration Tests | Implemented Integration E2E Tests | Status |
+|--------------|-----------------------------|-------------------------------|------------------------|------------------------------------------------------------------------------------------------|
+| 1 | default_accounts() | Yes | Yes | Implementation Difference. |
+| 2 | set_contract_storage() | Yes | Yes | Missing limitation on Integration Testing. |
+| 3 | invoke_contract_delegate() | No | Yes | Missing Function Implementation on Integration Testing. |
+| 4 | invoke_contract() | No | Yes | Missing Function Implementation on Integration Testing |
+| 5 | gas_left() | No | Yes | Missing Function Implementation on Integration Testing. Unfeasible Implementation. |
+| 6 | set_code_hash() | No | Yes | Missing Function Implementation on Integration Testing. |
+| 7 | instantiate_contract() | No | Yes | Missing Function Implementation on Integration Testing. |
+| 8 | caller_is_origin() | No | Yes | Missing Function Implementation on Integration Testing. |
+| 9 | code_hash() | No | Yes | Missing Function Implementation on Integration Testing. |
+| 10 | own_code_hash() | No | Yes | Missing Function Implementation on Integration Testing. |
+| 11 | call_runtime() | No | Yes | Missing Function Implementation on Integration Testing. Unfeasible Implementation. |
+| 12 | caller() | Yes | Yes | Pending Analysis for Corrections in Implementation Differences. |
+| 13 | transferred_value() | Yes | Yes | Pending Analysis for Corrections in Implementation Differences. |
+| 14 | weight_to_fee() | Yes | Yes | Pending Analysis for Corrections in Implementation Differences. |
+| 15 | block_timestamp() | Yes | Yes | Pending Analysis for Corrections in Implementation Differences. |
+| 16 | account_id() | Yes | Yes | Pending Analysis for Corrections in Implementation Differences. |
+| 17 | balance() | Yes | Yes | Pending Analysis for Corrections in Implementation Differences. |
+| 18 | block_number() | Yes | Yes | Pending Analysis for Corrections in Implementation Differences. |
+| 19 | minimum_balance() | Yes | Yes | Pending Analysis for Corrections in Implementation Differences. |
+| 20 | terminate_contract() | Yes | Yes | Pending Analysis for Corrections in Implementation Differences. |
+| 21 | transfer() | Yes | Yes | Pending Analysis for Corrections in Implementation Differences. |
+| 22 | hash_bytes() | Yes | Yes | Pending Analysis for Corrections in Implementation Differences. |
+| 23 | hash_encoded() | Yes | Yes | Pending Analysis for Corrections in Implementation Differences. |
+| 24 | ecdsa_recover() | Yes | Yes | Pending Analysis for Corrections in Implementation Differences. |
+
+For these two sets of functions, with explicit implementation plans and pending analysis, the following work remains to be performed.
+- The implementation and correction of implementation differences of the 9 functions with explicit plans. These are the functions with issue numbers 1, 2, 3, 4, 6, 7, 8, 9, 10.
+- An analysis of the remaining 13 functions, which are implemented both for integration and E2E tests, in order to first estimate and then correct implementation differences (if any). These correspond to functions issue numbers 12 through 24.
+- QA: Adding tests to integrate the functions we add or modify to the [ink! project repository](https://github.com/paritytech/ink) following existing [contribution guidelines](https://github.com/paritytech/ink/blob/master/CONTRIBUTING.md).
+- Report Describing our Contribution.
+
+Considering the dependency of several functions on the implementation of `instantiate_contract()`, we propose to split the work above into two milestones. All these implementations or modifications will be pushed into the [ink! project repository](https://github.com/paritytech/ink ) following existing [contribution guidelines](https://github.com/paritytech/ink/blob/master/CONTRIBUTING.md).
+
+We have also identified a bug in the e2e tests. When contracts are in a workspace with dependencies defined in `Cargo.toml`, and these dependencies are inherited in contracts, the e2e tests fail to compile. However, manually specifying dependencies in each contract resolves the issue. We've logged this bug on GitHub [Issue #1919](https://github.com/paritytech/ink/issues/1919) and will be addressing it as part of our work in Milestone 1.
+
+## Development Roadmap :nut_and_bolt:
+
+### Overview
+
+- **Total Estimated Duration:** 4 weeks
+- **Full-Time Equivalent (FTE):** 4 FTE
+(0.50 Project Manager,
+0.50 Tech Lead,
+1 Full time Sr Rust Developer,
+1 Full Time SemiSr Rust Developer,
+1 Full Time QA Specialist)
+- **Total Costs:** 30,000 USD
+
+### Milestone 1: Execution and Further Analysis
+- **Estimated duration:** 4 weeks
+- **FTE:** 4
+- **Costs:** 30,000 USD
+
+| Number | Deliverable | Specification |
+| ----- | ----------- | ------------- |
+| 0a. | License | MIT
+| 0b. | Documentation | We will write a comprehensive report that compares the functionalities of integration tests and E2E (End-to-End) tests. This report will focus on the functions to be implemented/corrected in this milestone, corresponding to issues 1-default_accounts(), 2-set_contract_storage() and 7-instantiate_contract().
Documentation and test cases will be provided for the 13 functions with remaining analysis. If implementation differences are found in these functions, an estimate for their correction and an implementation idea will also be provided in our report.
If applicable, we will suggest additional tests outside of the scope of this milestone. Particularly, for functions declared outside of the env_access.rs file, but that could be related to integration or e2e testing.
+| 0c. | Testing and Testing Guide | The newly developed functionalities will be documented and tested following existing [contribution guidelines](https://github.com/paritytech/ink/blob/master/CONTRIBUTING.md). A testing guide will be included.
+| 0d. | Docker | Does not apply at this stage.
+| 0e. | Article | We will publish an updated report summary in our blog at https://blog.coinfabrik.com/.
+ **1** | Develop | We will develop the missing functionalities or correct implementation differences for functions 1-default_accounts(), 2-set_contract_storage() and 7-instantiate_contract(). All these implementations or modifications will be pushed into the [ink! project repository](https://github.com/paritytech/ink) following existing [contribution guidelines](https://github.com/paritytech/ink/blob/master/CONTRIBUTING.md).
If applicable, we will develop additional tests or make ad hoc improvements to the ink codebase necessary for the completion of this milestone. Particularly for functions declared outside the env_access.rs file that might be related to integration or end-to-end testing.
+ **2** | Review and Estimate | We will review the remaining 13 unanalysed functions, which are implemented both for integration and e2e tests. For these functions we will provide documentation, a test case and an implementation estimation if applicable. These correspond to functions issue numbers 12 through 24.
+ **3** | Quality Assurance | We will adhere to existing [contribution guidelines](https://github.com/paritytech/ink/blob/master/CONTRIBUTING.md) and add necessary tests to integrate the new implemented or corrected functions to the [ink! project repository](https://github.com/paritytech/ink).
+
+
+
+## Future Plans
+
+After finishing the Milestone 1: Execution and Further Analysis, we will submit a new grant proposal to continue with the implementation of the remaining functions. We will include specific references to developments associated with the estimations resulting from the further analysis of functions issue numbers 12 through 24.
+
+### Next Milestone: Execution
+- **Estimated duration:** 4 weeks
+- **FTE:** 4
+- **Costs:** 30,000 USD
+
+
+
+| Number | Deliverable | Specification |
+| ----- | ----------- | ------------- |
+| 0a. | License | MIT
+| 0b. | Documentation | We will write a comprehensive report that compares the functionalities of integration tests and E2E (End-to-End) tests. This report will focus on the the functions to be implemented in this milestone, corresponding to issues 3-invoke_contract_delegate(), 4-invoke_contract(), 6-set_code_hash(), 8-caller_is_origin(), 9-code_hash(), 10-own_code_hash().
Our report will also document the implementation of any missing functionalities, or correct implementation differences, for the 13 functions with issues 12 through 24. For this group, we will document any additional work that was required in order to ensure consistency between integration and e2e tests.
If applicable, we will suggest additional tests outside of the scope of this milestone. Particularly, for functions declared outside of the env_access.rs file, but that could be related to integration or e2e testing.
+| 0c. | Testing and Testing Guide | The newly developed functionalities will be documented and tested following existing [contribution guidelines](https://github.com/paritytech/ink/blob/master/CONTRIBUTING.md). A testing guide will be included.
+| 0d. | Docker | Does not apply at this stage.
+| 0e. | Article | We will publish an updated report summary in our blog at https://blog.coinfabrik.com/.
+ **1** | Development | We will implement the missing functionalities or resolve implementation differences for function issues 3-invoke_contract_delegate(), 4-invoke_contract(), 6-set_code_hash(), 8-caller_is_origin(), 9-code_hash(), 10-own_code_hash().
We will implement any missing functionalities, or correct implementation differences, for the 13 functions with issues 12 through 24. For this group, we will document any additional work required in order to ensure consistency between integration and e2e tests.
All these implementations or modifications will be pushed into the [ink! project repository](https://github.com/paritytech/ink) following existing [contribution guidelines](https://github.com/paritytech/ink/blob/master/CONTRIBUTING.md).
If applicable, we will develop additional tests or make ad hoc improvements to the ink codebase necessary for the completion of this milestone. Particularly for functions declared outside the env_access.rs file that might be related to integration or end-to-end testing.
+**2** | Quality Assurance| We will adhere to existing [contribution guidelines](https://github.com/paritytech/ink/blob/master/CONTRIBUTING.md) and add necessary tests to integrate the new implemented or corrected functions to the [ink! project repository](https://github.com/paritytech/ink).
+
+
+Moving forward, we have two projects in mind:
+
+- Research and develop an advanced testing automation solution for ink! smart contracts.
+- Improve our open source bug-detection tool [Scout](https://coinfabrik.github.io/scout/ ).
+
+
+
+## Referral Program (optional) :moneybag:
+
+## Additional Information :heavy_plus_sign:
+
+**How did you hear about the Grants Program?** Richard Casey from Parity brought this program to our attention, and we have already successfully delivered two applications as a result.
+
+During our inquiries for this application, we briefly consulted Sam Ruberti from the ink! Team and David Hawig from the Web3 Foundation. Their encouragement motivated us to proceed with this presentation.
+
diff --git a/applications/JsonRpsee-socks5-proxy.md b/applications/JsonRpsee-socks5-proxy.md
new file mode 100644
index 00000000000..223844b2069
--- /dev/null
+++ b/applications/JsonRpsee-socks5-proxy.md
@@ -0,0 +1,98 @@
+# JsonRpsee socks5 proxy
+
+* **Team Name:** [gmajor](https://github.com/gmajor-encrypt)
+* **Payment Address:** 0xC3094f0ddce699a1Ad9Ef2621DF68Cd297a4c44F(USDC)
+* **[Level](https://github.com/w3f/Grants-Program/tree/master#level_slider-levels):** 1
+
+## Project Overview :page_facing_up:
+
+RFPs [https://github.com/w3f/Grants-Program/blob/master/docs/RFPs/jsonrpsee-proxy-support.md](https://github.com/w3f/Grants-Program/blob/master/docs/RFPs/jsonrpsee-proxy-support.md)
+
+### Overview
+
+This proposal is to develop a JsonRpsee socks5 middleware proxy.
+
+### Project Details
+
+This proposal is to develop a JsonRpsee [socks5](https://datatracker.ietf.org/doc/html/rfc1928) middleware proxy.
+
+
+### Ecosystem Fit
+
+- Where and how does your project fit into the ecosystem?
+
+ This project is a middleware that can be used to proxy connections using a socks5 proxy. It can be used in any application that uses jsonrpsee as a client.
+
+- Who is your target audience (parachain/dapp/wallet/UI developers, designers, your own user base, some dapp's userbase,
+ yourself)?
+
+ jsonrpsee client developers
+
+- What need(s) does your project meet?
+
+ Enhance the JsonRpsee package and add support for socks5 proxy
+
+- Are there any other projects similar to yours in the Substrate / Polkadot / Kusama ecosystem?
+
+ Nothing
+
+## Team :busts_in_silhouette:
+
+### Team members
+
+* gmajor
+
+### Contact
+
+* **Contact Name:** gmajor
+* **Contact Email:** gmajorencrypt@gmail.com
+* **Website:**
+
+### Legal Structure
+
+individual
+
+### Team's experience
+
+I have many years of PHP development experience and nearly five years of blockchain development experience, familiar
+with PHP, GOLANG, PYTHON, Nodejs, Rust
+
+### Team Code Repos
+
+- https://github.com/gmajor-encrypt/php-scale-codec
+- https://github.com/gmajor-encrypt/php-substrate-api
+- https://github.com/gmajor-encrypt/scale-codec-comparator
+- https://github.com/gmajor-encrypt/sr25519-bindings
+- https://github.com/gmajor-encrypt/xcm-tools
+
+## Development Status :open_book:
+
+Not yet
+
+## Development Roadmap :nut_and_bolt:
+
+### Overview
+
+* **Total Estimated Duration:** 1 months
+* **Total Costs:** 9000 USDC
+
+### Milestone 1
+
+
+* **Estimated duration:** 4 week
+* **FTE:** 1
+* **Costs:** 9000 USDC
+
+| Number | Deliverable | Specification |
+|-------:|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 0a. | License | MIT or Apache 2.0 |
+| 0b. | Documentation | Simple documentation on how to use and how to test |
+| 0c. | Testing and Testing Guide | Core functions will be fully covered by comprehensive unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests. |
+| 1. | Socks5 middleware support | Enable a jsonrpsee client to proxy connections using a socks5 proxy |
+| 2. | Example | I will now provide an example to demonstrate the usage of this socks 5 middleware. |
+| 3. | Pull request | Create pull request merge into [jsonrpsee](https://github.com/paritytech/jsonrpsee) |
+
+
+## Future Plans
+
+If there are any problems with this feature, I will still maintain it.
\ No newline at end of file
diff --git a/applications/Plutonication.md b/applications/Plutonication.md
new file mode 100644
index 00000000000..75c744d1de2
--- /dev/null
+++ b/applications/Plutonication.md
@@ -0,0 +1,497 @@
+# Plutonication
+
+- **Team Name:** Plutonication
+- **Payment Address:** 1WmPE1X9Ykpb7QcVamPtUSRjEZy2GMDeTm5N72DyXYiqMCo (USDT)
+- **[Level](https://github.com/w3f/Grants-Program/tree/master#level_slider-levels):** 2
+
+## Project Overview :page_facing_up:
+
+### Overview
+
+Please provide the following:
+
+#### If the name of your project is not descriptive, a tag line (one sentence summary).
+
+- Communications protocol that enables seamless interactions between dApps and wallets across all platforms.
+
+#### A brief description of your project.
+
+- Plutonication allows users to connect PlutoWallet to other dApps seamlessly on any platforms, accross multiple codebases.
+DApp just generates a QR code and once it is scanned in the wallet, they will pair and the wallet will be able to receive transaction requests from the dApp. It works on the same principle as WalletConnect protocol.
+
+- You can see a short (90 sec) demo here: https://youtu.be/hw2B8-sBc9A?si=O8MiWa0Wq1jxfZdr
+
+#### An indication of how your project relates to / integrates into Substrate / Polkadot / Kusama.
+
+- Currently, the only way to connect your mobile wallet to other dApps is to use Wallet connect protocol, or a very clunky Polkadot Vault (Parity signer).
+
+- We think, we will be good competitors to WalletConnect and that we will do will better than them!
+
+- Our Plutonication Extension already works with most of the web dApps as supposed to WalletConnect, which is implemented into only a handful of dApps.
+
+- WalletConnect is also only available in javascript and we would like to expand it further to other programming languages.
+
+- C# is a very popular programming language for games and there have not been much focus on it in the Polkadot Ecosystem appart from Ajuna Network and their excellent Substrate.NetApi. We are dirrectly communicating with Ajuna developers to help better coordinate the Substrate.NetApi development and Plutonication, so that their are dirrectly compatible with each other.
+
+#### An indication of why your team is interested in creating this project.
+
+- We have been very pationate about Plutonication since the beginning. We have noticed the lack of WalletConnect protocol before it was available.
+
+- We have been working on Plutonication in our free time to prove the concepts are possible.
+
+- We have also landed a second place at Polkadot Global Series: Europe edition 2023 hackathon in Web3 and Tooling category.
+
+### Project Details
+
+We expect the teams to already have a solid idea about your project's expected final state. Therefore, we ask the teams to submit (where relevant):
+
+#### Data models / API specifications of the core functionality
+
+Native Plutonication:
+
+```mermaid
+flowchart LR
+
+subgraph Cloud
+S[Plutonication Websocket Server]
+end
+
+subgraph Any device
+D[dApp using Plutonication]
+end
+
+subgraph Phone
+W["Mobile wallet
+ Private key always stays here"]
+end
+
+S -- Receive signed payload --> D
+D -- Send extrinsic payload --> S
+
+S -- Receive extrinsic payload --> W
+W -- Send signed payload --> S
+
+D -. Scan QR code for establishing connection .-> W;
+```
+
+Plutonication on existing polkadot.js apps:
+```mermaid
+flowchart LR
+
+subgraph Cloud
+S[Plutonication Websocket Server]
+end
+
+subgraph Web
+D[dApp using Polkadot.js] ~~~ E[Plutonication Extension]
+E -. Connection via Polkadot.js extension .- D
+end
+
+subgraph Phone
+W["Mobile wallet
+ Private key always stays here"]
+end
+
+S -- Receive signed payload --> E
+E -- Send extrinsic payload --> S
+
+S -- Receive extrinsic payload --> W
+W -- Send signed payload --> S
+
+E -. Scan QR code for establishing connection .-> W;
+```
+
+#### An overview of the technology stack to be used
+
+1) Plutonication server (Python): Flask, Flask-SocketIO
+2) Mobile Wallet: https://github.com/rostislavLitovkin/plutowallet
+3) Plutonication Native (C#): SocketIOClient, Substrate.NetApi
+4) Plutonication Native (TS): socket.io-client, Polkadot.js
+5) Plutonication Extension: socket.io-client, Polkadot.js extension
+
+#### Documentation of core components, protocols, architecture, etc. to be deployed
+
+##### Plutonication Server
+- Used for reliable establishing of connection.
+- Passes payloads between Wallets and dApps.
+
+##### Mobile Wallet
+- Has access to the private key
+- signs the payloads and sends them back to the dApp.
+- Never exposes the private key
+
+##### dApp
+- needs to have access to either: Plutonication Native / Plutonication Extension
+
+##### Plutonication Native
+- A simple package that allows the dApp get connected with the Mobile Wallet.
+- Connects the dApp with the Plutonication server.
+- Helps to generate a QR code for the Wallet to establish the connection.
+
+##### Plutonication Extension
+- a polkadot.js extension that works with any existing dApp that supports polkadot.js extension.
+- Connects the dApp with the Plutonication server.
+- Generate a QR code for the Wallet to establish the connection.
+
+#### PoC/MVP or other relevant prior work or research on the topic
+- Second place at Polkadot Global Series: Europe edition 2023 hackathon in Web3 and Tooling category.
+- https://github.com/cisar2218/Plutonication
+- Plutonication is integrated to: https://github.com/rostislavLitovkin/plutowallet
+- https://github.com/rostislavLitovkin/plutonicationextension
+
+#### What your project is _not_ or will _not_ provide or implement
+
+- Any improvements to PlutoWallet appart from the things needed for Plutonication to work in the PlutoWallet.
+
+- Although it is planned support Kotlin and Swift programming languages as well, it is not part of this grant proposal.
+
+- We are certainly willing to make PRs to other popular dApps to utilise Plutonication, it is also not part of this grant proposal. We would be willing to do a follow-up grant or get a treasury funding to make the PRs.
+
+### Ecosystem Fit
+
+Help us locate your project in the Polkadot/Substrate/Kusama landscape and what problems it tries to solve by answering each of these questions:
+
+#### Where and how does your project fit into the ecosystem?
+
+- Our project is comparable to WalletConnect, which was also our inspiration.
+
+##### [WalletConnect](https://walletconnect.com/)
+- When we started making our first prototypes in February, WalletConnect was not available in the Polkadot Ecosystem yet.
+Even thought they have taken a lot of time and had a lot more experience then us, they were unable to make quick and elegant deliveries.
+WalletConnect still is not supported by most of the dApps. We think we can do better. Actually, we already did.
+
+- We made a Plutonication Extension, which already allows you to interact with existing dApps, even though they have not implemented the Plutonication standard directly. This can be a perfect middle ground during the transition of popularizing the Plutonication. Even if the user wanted to use a new niche dApp, they can do so with Plutonication.
+
+- Wallet connect is also only supported in javascript. We want to make Plutonication available in more languages, including a very popular C# language, which is mostly used for game development. We will make web3 gaming possible on game consoles, thanks to the Plutonication.
+
+- WalletConnect's server solution (also known as WalletConnect cloud) is not opensourced. We want to be open to everybody and fully opensourced.
+
+##### [SubConnect](https://github.com/Koniverse/SubConnect)
+- This is a great aggregation of wallets. This certainly improves the UX and simplifies the development for developers. However, it is not trying to do the same thing as Plutonication. Plutonication tries to achieve connection between 2 different platforms (like mobile wallet on Android and dApp on web on Windows).
+
+- It may be certainly a good idea to talk to SubWallet to implement Plutonication into the SubConnect solution.
+
+##### [Tesseract](https://github.com/tesseract-one/Tesseract.rs)
+
+- Tesseract is a great solution for connecting a wallet and a dApp together on a single device. However, Plutonication allows wallets and dApps to be connected across different devices.
+
+##### [@talismn/connect](https://github.com/TalismanSociety/talisman-connect)
+
+- This is similar to SubConnect. Once again, we try to solve a completely different problem.
+
+#### Who is your target audience (parachain/dapp/wallet/UI developers, designers, your own user base, some dapp's userbase, yourself)?
+
+- dApps developers - To integrate the Plutonication in their dApps. We will ensure that the developers will receive a good documentation.
+
+- Wallet developers - We are welcoming other wallets to use the Plutonication. We would like to help them make this possible.
+
+- Users - In the end, it will be mainly used by mobile focused users. They will be able to interact with web3 apps on unusual platforms, like game consoles, smartwatches ...
+
+#### What need(s) does your project meet?
+
+- You are unable securely interact with dApps on gaming consoles, smartwatches and other unusual platforms. Without Plutonication, you would have to expose your private key, which is very unsafe.
+
+- You can also interact with existing web dApps with your mobile wallet. Again, you do not need to expose your private key to multiple places (in this case browser extension wallet), which would be very unsafe.
+
+#### Are there any other projects similar to yours in the Substrate / Polkadot / Kusama ecosystem?
+
+- Yes, WalletConnect.
+
+#### If so, how is your project different?
+
+- We support more programming languages. We also have a browser extension that enables Plutonication on existing dApps.
+
+- WalletConnect also mainly focuses on Ethereum ecosystem. We are focusing only on Polkadot.
+
+## Team :busts_in_silhouette:
+
+### Team members
+
+#### Name of team leader:
+
+Rostislav Litovkin
+
+#### Names of team members:
+
+Valentina Gómez
+
+Dušan Jánsky
+
+### Contact
+
+- **Contact Name:** Rostislav Litovkin
+- **Contact Email:** rostislavlitovkin@gmail.com
+- **Website:** https://github.com/cisar2218/Plutonication
+
+### Legal Structure
+
+- **Registered Address:** Píškova 1946/12, 155 00, Prague, Czech republic
+- **Registered Legal Entity:** None
+
+### Team's experience
+
+#### [Rostislav Litovkin](http://rostislavlitovkin.pythonanywhere.com/aboutme)
+- Alumnus at Polkadot Blockchain Academy 2023 in Berkeley
+- Experienced .net MAUI developer, e.g.:
+ - [Galaxy Logic Game](https://github.com/RostislavLitovkin/galaxylogicgamemaui) (successful game for watches and mobiles, 50k+ downloads)
+- Frontend developer at [Calamar explorer](https://calamar.app/)
+- Successful student at Polkadot DevCamp #2
+- Successful student at [Solana Summer School](https://ackeeblockchain.com/school-of-solana)
+- Polkadot Global Series 2023 (Europe) - second place
+- Audience choice prize at EthPrague 2023
+
+#### Valentina Gómez
+- Alumnus at Polkadot Blockchain Academy 2023 - Berkeley.
+- Full stack web developer in TeamClass.
+- Financial Engineer
+
+#### Dušan Jánsky
+- Alumnus at Polkadot Blockchain Academy 2023 in Berkeley
+- Student at Faculty of Electrical Engineering Czech Technical University in Prague - Opens Informatics (specialization in computer games and computer graphics)
+- Fullstack developer at [Universal Scientific Technologies](https://www.ust.cz/)
+- Polkadot Global Series 2023 (Europe) - second place
+
+#### If anyone on your team has applied for a grant at the Web3 Foundation previously, please list the name of the project and legal entity here.
+
+Rostislav Litovkin helped with **Calamar.app - TopMonks s.r.o**
+
+### Team Code Repos
+
+- https://github.com/ThunderFly-aerospace/thumby
+- https://github.com/topmonks/calamar
+- https://github.com/RostislavLitovkin/GalaxyLogicGameMAUI
+- https://github.com/RostislavLitovkin/Uniquery.Net
+
+#### Please also provide the GitHub accounts of all team members. If they contain no activity, references to projects hosted elsewhere or live are also fine.
+
+- https://github.com/cisar2218
+- https://github.com/rostislavlitovkin
+
+### Team LinkedIn Profiles (if available)
+
+- https://www.linkedin.com/in/dusan-jansky-6aab69239/
+- https://www.linkedin.com/in/valentinaga1/
+
+## Development Status :open_book:
+
+If you've already started implementing your project or it is part of a larger repository, please provide a link and a description of the code here. In any case, please provide some documentation on the research and other work you have conducted before applying. This could be:
+
+- The idea was already tested by WalletConnect. Now, we are expanding it further in the Polkadot ecosystem.
+
+- We have already made working MVPs which can be found here:
+
+ - https://github.com/cisar2218/Plutonication
+
+ - https://github.com/rostislavLitovkin/plutowallet
+
+ - https://github.com/rostislavLitovkin/plutonicationextension
+
+## Development Roadmap :nut_and_bolt:
+
+This section should break the development roadmap down into milestones and deliverables. To assist you in defining it, we have created a document with examples for some grant categories [here](../docs/Support%20Docs/grant_guidelines_per_category.md). Since these will be part of the agreement, it helps to describe _the functionality we should expect in as much detail as possible_, plus how we can verify and test that functionality. Whenever milestones are delivered, we refer to this document to ensure that everything has been delivered as expected.
+
+Below we provide an **example roadmap**. In the descriptions, it should be clear how your project is related to Substrate, Kusama or Polkadot. We _recommend_ that teams structure their roadmap as 1 milestone ≈ 1 month.
+
+> :exclamation: If any of your deliverables is based on somebody else's work, make sure you work and publish _under the terms of the license_ of the respective project and that you **highlight this fact in your milestone documentation** and in the source code if applicable! **Projects that submit other people's work without proper attribution will be immediately terminated.**
+
+### Overview
+
+- **Total Estimated Duration:** 2 months
+- **Full-Time Equivalent (FTE):** 0.83 FTE
+- **Total Costs:** 25,000 USD
+
+### Milestone 1 Plutonication Server (Python: Flask)
+
+- **Estimated Duration:** 1 month
+- **FTE:** 0.33
+- **Costs:** 5,000 USD
+
+| Number | Deliverable | Specification |
+| -----: | ----------- | ------------- |
+| **0a.** | License | MIT |
+| **0b.** | Documentation | We will provide both **in code documentation for individual methods**. We will also provide a tutorial on how to run the Plutonication Server locally and in cloud. |
+| **0c.** | Testing and Testing Guide | All of the functions will be end-to-end tested with a sample dApp written in typescript (with Plutonication and Polkadot.js api) and a sample Wallet (PlutoWallet) |
+| **0d.** | Docker | We will provide a Dockerfile(s) that can be used to test all the functionality delivered with this milestone and for running the server in production. |
+| 1. | PlutonicationServerFlask | A Python server with Flask and Flask-SocketIO used for establishing a stable websocket connection between the dApp and Wallet. Use of server is crucial for reliable establishing of connection. |
+| 1a. | create_room | dApp creates room |
+| 1b. | pubkey | Sends an account address (SS58 encoded) from wallet to dApp |
+| 1c. | sign_payload | dApp requests an extrinsic payload signature |
+| 1d. | sign_raw | dApp requests a raw message signature |
+| 1e. | payload_signature | wallet provides an extrinsic payload signature |
+| 1f. | raw_signature | wallet provides a raw message signature |
+| 2. | database requirements | none |
+
+### Milestone 2 Plutonication C# version
+
+- **Estimated duration:** 1 month
+- **FTE:** 0.5
+- **Costs:** 7500 USD
+
+> :exclamation: **The default deliverables 0a-0d below are mandatory for all milestones**, and deliverable 0e at least for the last one.
+
+| Number | Deliverable | Specification |
+| -----: | ----------- | ------------- |
+| **0a.** | License | MIT |
+| **0b.** | Documentation | We will provide both **in code documentation for individual methods** and a **tutorial** explaining how to integrate Plutonication into a c# dApp. |
+| **0c.** | Testing and Testing Guide | All of the functions will be end-to-end tested with a sample dApp written in c# (with Plutonication and Substrate.NetApi) and a sample Wallet (PlutoWallet) |
+| **0d.** | Docker | We will provide a Dockerfile for a sample dApp that can be used to test all the functionality delivered with this milestone. |
+| 1. | PlutonicationDAppClient | This would be a series of methods tailored for use with dApps. We will make sure that it is compatible with Substrate.NetApi |
+| 1a. | Initialize(AccessCredentials ac) -> void | Method used for initializing the PlutonicationDAppClient |
+| 1b. | ReceiveAddress() -> Address | Handles the receiving of SS58 encoded address |
+| 1c. | SendPayloadAsync(Payload payload) -> void | Method used for requesting an extrinsic payload sign |
+| 1d. | SendRawAsync(bytes rawMessage) -> void | Method used for requesting a raw message sign |
+| 2. | PlutonicationWalletClient | This would be a series of methods tailored for use with wallets. |
+| 2a. | SendAddress() -> Address | Sends the SS58 encoded address of the account in the wallet |
+| 2b. | SendSignedPayloadAsync(Payload payload) -> void | Method used for sending a signed extrinsic payload back to the dApp. The signed extrinsic payload will then be added to the extrinsic and submitted to chain. |
+| 2c. | SendSignedRawAsync(bytes signedRaw) -> void | Method used for sending a signed raw message back to the dApp. |
+| 3. | NuGet package | We will provide a NuGet package, which is commonly used it c# development. It is comparable to NPM packages in Javascript world. |
+| 4. | Sample dApp | We will make a sample C# console dApp (with Plutonication and Substrate.NetApi) published to a public github repo. |
+
+### Milestone 3 Plutonication Typescript version
+
+- **Estimated Duration:** 1 month
+- **FTE:** 0.5
+- **Costs:** 7500 USD
+
+| Number | Deliverable | Specification |
+| -----: | ----------- | ------------- |
+| **0a.** | License | MIT |
+| **0b.** | Documentation | We will provide both **in code documentation for individual methods** and a **tutorial** explaining how to integrate Plutonication into a javascript/typescript dApp. |
+| **0c.** | Testing and Testing Guide | All of the functions will be end-to-end tested with a sample dApp written in typescript (with Plutonication and Polkadot.js api) and a sample Wallet (PlutoWallet) |
+| **0d.** | Docker | We will provide a Dockerfile for a sample dApp that can be used to test all the functionality delivered with this milestone. |
+| 1. | PlutonicationDAppClient | This would be a series of methods tailored for use with dApps. We will make sure that it is compatible with polkadot.js api |
+| 1a. | Initialize(AccessCredentials ac) -> void | Method used for initializing the PlutonicationDAppClient |
+| 1b. | ReceiveAddress() -> Address | Handles the receiving of SS58 encoded address |
+| 1c. | SendPayloadAsync(Payload payload) -> void | Method used for requesting an extrinsic payload sign |
+| 1d. | SendRawAsync(Bytes rawMessage) -> void | Method used for requesting a raw message sign |
+| 2. | PlutonicationWalletClient | This would be a series of methods tailored for use with wallets. |
+| 2a. | SendAddress(Address address) -> void | Sends the SS58 encoded address of the account in the wallet |
+| 2b. | SendSignedPayloadAsync(Payload signedPayload) -> void | Method used for sending a signed extrinsic payload back to the dApp. The signed extrinsic payload will then be added to the extrinsic and submitted to chain. |
+| 2c. | SendSignedRawAsync(bytes signedRaw) -> void | Method used for sending a signed raw message back to the dApp. |
+| 3. | QR code pop-up | We will provide a function that would embed an HTML qr code popup into a dApp. The QR code is used for establishing a connection. |
+| 4. | NPM package | We will provide an NPM package, which is commonly used it javascript/typescript development. |
+| 5. | Sample dApp | We will make a sample typescript console dApp (with Plutonication and Polkadot.js api) published to a public github repo. |
+
+### Milestone 4 Plutonication extension
+
+- **Estimated Duration:** 1 month
+- **FTE:** 0.33
+- **Costs:** 5,000 USD
+
+| Number | Deliverable | Specification |
+| -----: | ----------- | ------------- |
+| **0a.** | License | MIT |
+| **0b.** | Documentation | We will provide **inline documentation of the code**. |
+| **0c.** | Testing and Testing Guide | All of the functions will be end-to-end tested with a sample dApp (https://polkadot.js.org/apps/) and a sample Wallet (PlutoWallet) |
+| **0d.** | Docker | We will not provide a docker file |
+| **0e.** | Article | We will publish an article that explains what was done as part of the grant. We will mention how Plutonication is ground-breaking and can be used by anyone. |
+| 1. | Plutonication Extension | This is a [polkadot.js extension](https://github.com/polkadot-js/extension) compatible browser extension for Plutonication. |
+| 1a. | Inject(..) | Injects the browser extension into the polkadot.js dApp. |
+| 1b. | ReceiveAddress(..) | Handles the receiving of SS58 encoded address |
+| 1c. | SendPayloadAsync(..) | Method used for requesting an extrinsic payload sign |
+| 1d. | ReceiveSignedPayloadAsync(..) | Method used for receiving a signed extrinsic payload data. This signed extrinsic payload will then be added to the extrinsic and submitted to chain. (Done automatically by polkadot.js) |
+| 1e. | SendRawAsync(..) | Method used for requesting a raw message sign |
+| 1f. | ReceiveSignedRawAsync(..) | Method used for receiving a signed raw message. |
+| 2. | Chrome browser extension | Released to Chrome Web Store |
+
+## Future Plans
+
+Please include here
+
+#### how you intend to use, enhance, promote and support your project in the short term, and
+
+- Once all of these 4 milestones are completed, we will have a solid ground to start integrating Plutonication to other dApps.
+
+#### the team's long-term plans and intentions in relation to it.
+
+- Our goal would be to create multiple PRs to already popular dApps to utilise Plutonication. At that point, other wallet companies will have a solid motivation to start integrating Plutonication into their wallets too.
+
+- Further plans are to combine Plutonication with PlutoWallet custom layouts (find more in PlutoWallet readme: https://github.com/RostislavLitovkin/PlutoWallet) and make onboarding of new users easier.
+
+- The endgoal would be to become a defaultly used solution for wallet injection.
+
+## Referral Program (optional) :moneybag:
+
+You can find more information about the program [here](../README.md#moneybag-referral-program).
+- **Referrer:** https://github.com/topmonks
+- **Payment Address:** 32NoFbB4x8bZ7YNvjra1DUYcje2B2XQwP3 (BTC)
+
+- They are a grants alumni.
+
+## Additional Information :heavy_plus_sign:
+
+**How did you hear about the Grants Program?** - personal recommendation
+
+Here you can also add any additional information that you think is relevant to this application but isn't part of it already, such as:
+
+#### Work you have already done.
+
+- https://github.com/cisar2218/Plutonication
+
+- https://github.com/rostislavLitovkin/plutonicationextension
+
+- https://github.com/rostislavLitovkin/plutowallet
+
+#### If there are any other teams who have already contributed (financially) to the project.
+
+- Nobody has financially supported the project.
+
+#### Previous grants you may have applied for.
+
+- None yet.
+
+#### Why are you focusing on C#? Do you have any relation to Ajuna?
+
+- I was a c# developer and I still like it to this day. It is probably the best option for game development and in my opinion also the best way to develop mobile applications.
+Originally, I wanted to create a mobile dApp with c# frontend, so I did my research and that is how I discovered Ajuna and their [Substrate.NetApi](https://github.com/SubstrateGaming/Substrate.NET.API).
+It was an excellent tool to get started and without it, I would have probably gave up and moved on. I still noticed that few of the important features were missing, like these:
+ - how to securely connect a foreign wallet to a c# dApp.
+ - how to efficiently query NFT data.
+ - how to elegantly interact with smart contracts (namely ink! contracts) from c#.
+
+- So I started addressing them one by one.
+ - First is Plutonication.
+ - Second is https://github.com/rostislavlitovkin/uniquery.net (this one is already production ready)
+ - Third was just brainstormed during PBA. It might be my next project in the future.
+
+- Regarding Ajuna, I am currently in a very close relationship with them. We discuss a lot of the potential changes and updates made to the Substrate.NetApi.
+They are very supportive to me.
+Last week, I had a chance to represent Ajuna at the Token2049. So, I was showing off all of the projects that have built on the Substrate.NetApi so far ^^.
+
+#### Is Plutonication made just for PlutoWallet?
+
+- Although the name may suggest it, it is not true. The name came from the hackathon, so we figured out a combination of __Pluto + Comunication =__ **Plutonication**. Once we figure out a better name, we will rename it to something more generic. It is totally meant to be used by anyone. We are willing to write a good documentation to make it simple for any developers to use.
+
+#### Can you share some user numbers or other metrics that show adoption of PlutoWallet?
+
+- It is in an MVP stage currently, meaning it works quite well, suports all of the important features, can be run on any platform and demonstrates well the idea of customizable layouts. It is on a good track to get released by the end of this year.
+
+#### Regarding deliverable 4.1, you mean polkadot.js apps, not the extension, correct?
+
+- I truly meant [polkadot.js extension](https://github.com/polkadot-js/extension) (https://polkadot.js.org/docs/extension/usage/).
+This Polkadot.js extension is implemented in polkadot.js.org/apps, which means, that it will also work with polkadot.js apps.
+
+- Also on the demo video, it already works with polkadot.js.org/apps ^^
+
+- What I am trying to say is that it is not just limited to polkadot.js.org/apps, but it can work with any dApp that implements the extension package, which most of the dApps did.
+
+#### Wallet Connect does have both a [Dapp integration guide](https://docs.walletconnect.com/advanced/multichain/polkadot/dapp-integration-guide) and a [wallet integration guide](https://docs.walletconnect.com/advanced/multichain/polkadot/wallet-integration-guide) for Polkadot. Can you compare to this and what is missing that your solution would provide?
+
+- WalletConnect for Polkadot is not available for c#.
+
+- WalletConnect also is not optimised for use with Substrate.NetApi.
+This is very important because all of the c# projects currently building on Polkadot ecosystem are using Substrate.NetApi.
+
+#### You point out that the only way to connect a mobile wallet to a Dapp is through Substrate Connect or Vault, but afaik mobile wallets such as Talisman and Fearless will also let you connect.
+
+- Substrate Connect / Vault are not very elegant and do not work on any device. The device needs to have access to a camera, which for example consoles do not have. Desktops also do not come with webcam out of the box. Smartwatches also do not have access to camera.
+
+- Talisman is not a mobile wallet. Sorry, I do not understand the second part of the question.
+
+#### How do you plan to get developers to use your solution?
+
+- The developers want to provide secure and easy to use dApps. If they do not have to deal about key management, they can focus on other parts of development.
+
+- For users, it is very risky to expose the private key. This way, they never expose their private key. The developers should recognize this risk and solve it with this easy to use solution.
+
+- As far as I know, this is the only solution so far for c# that allows the users to connect their wallet to a Substrate.NetApi dApp.
diff --git a/applications/SpellRouter-proposal.md b/applications/SpellRouter-proposal.md
new file mode 100644
index 00000000000..aa3d7b6ba72
--- /dev/null
+++ b/applications/SpellRouter-proposal.md
@@ -0,0 +1,302 @@
+# SpellRouter - XCM Router by ParaSpell✨
+
+- **Team Name:** ParaSpell✨
+- **Payment Address:** bc1qa7m3f5cm5pcyh7m8f899kx59m93w496ld8nyux BTC
+- **[Level](https://github.com/w3f/Grants-Program/tree/master#level_slider-levels):** 2 🐤
+
+## Project Overview :page_facing_up:
+
+Previously completed grants:
+- [Phase 1](https://github.com/w3f/Grants-Program/pull/1118)
+- [Phase 2](https://github.com/w3f/Grants-Program/pull/1245)
+- [Phase 3](https://github.com/w3f/Grants-Program/pull/1589)
+- [LightSpell](https://github.com/w3f/Grants-Program/pull/1817)
+
+**What we do focus on in ParaSpell✨:**
+
+Our team has focused on the unification of cross-chain communication in the Polkadot and Kusama ecosystems for a while now. Our latest and flagship addition is XCM API also known as LightSpell⚡️. This tool allows you to implement cross-chain interoperability into your application within moments. ParaSpell offers a set of XCM & XCMP Developer tools meant to ease the integration of cross-chain functionality into dApps. As we have learnt by now, cross-chain experience between Parachains can be very diverse. ParaSpell means to unify this experience by doing all the research for developers. We have wrapped all XCM pallets from compatible nodes into simple patterns from which it is easy to create XCM calls. As an example, we provide the image below.
+
+
+
+In this image, we can see, that ParaSpell XCM SDK saves much time for developers. Just one call can contain multiple lines of JSON which would otherwise have to be integrated manually by the developer. ParaSpell does it in marginally fewer lines and hides the complex logic of building messages which ensures, that messages are constructed correctly. This call in the end results in the following lengthy extrinsic:
+
+
+
+This extrinsic can be subscribed to for useful data in front-end applications.
+
+The same call can also be reproduced with the latest addition to our tool pack - XCM API. See the example below.
+
+
+
+### Overview 🎨
+
+ParaSpell is currently split into three main repositories at the moment. XCM Router, XCM API and XCM SDK will be merged into one monorepo package with the intention of sharing types and saving code:
+
+- XCM ROUTER - TBA: Meant to give developers the ability to exchange and transfer assets in one call in a seamless way that allows them to lift complexity from users.
+- [XCM SDK](https://github.com/paraspell/xcm-sdk): Meant to unify cross-chain experience on Polkadot and become a layer 2 protocol that allows for seamless integration of XCM into your dApps.
+- [XCM API](https://github.com/paraspell/xcm-api): Meant to ease the integration of XCM interoperability into your dApp, offload your dApp from heavy computing and save you costs.
+- [Docs](https://github.com/paraspell/docs): Extensive documentation for an overview of ParaSpell, a guide for SDK and API
+
+#### XCM SDK
+
+Few facts about XCM SDK:
+- The core component for XCM API
+- Comprehensive unification of XCM from 43 different Parachains
+- Allows for creating XCM calls with one-line
+- Simple to implement typescript package
+- Completely free with an MIT license
+
+XCM SDK allows developers to use XCM in all three available scenarios:
+- Parachain to Parachain - HRMP
+- Parachain to Relay chain - UMP
+- Relay chain to Parachain - DMP
+
+SDK contains many useful features that allow for easier integration:
+- Builder pattern implementation, easy to construct XCM calls, much more used recently for simplicity of implementation.
+
+- Suggestions, SDK contains TYPES that help to guide developers through integration. For example, they show compatible Parachains that can be used in calls.
+
+
+- Console printouts, SDK allows for printing into the console so developers can always check if the call they constructed is correct.
+
+
+- Exporting registered assets for each compatible node in many useful functions
+
+- Exporting supported XCM pallets for each compatible node in useful functions
+
+And more.
+
+#### XCM API
+XCM API currently supports 43 (this number changes a lot) XCM-compatible Parachains. It brings lots of advantages for developers.
+The advantages of LightSpell⚡️ XCM API for developers:
+- Provides the same functionality as XCM SDK with many benefits
+- Built-in user error prevention for seamless operation
+- Built-in Token authentication for DDoS prevention
+- Easy to use tech stack: Typescript, Nest.js, ParaSpell XCM-SDK
+- Completely free with an MIT license
+- Also designed for simple private deploy
+- API Offloads your server from heavy computing required to construct calls (You receive constructed message already)
+- API saves you server costs (Because of the reason mentioned above)
+- API features Package-less integration (No need to install anything compared to SDK alternatives)
+- API is simple to implement (Constructed to be as dev-friendly as possible)
+- API is already live on the following link: https://api.lightspell.xyz
+
+#### Docs
+Meet our comprehensive docs covering just about every topic developers will meet with when implementing XCM and our tools into their dAPPs.
+
+
+
+#### Architecture 🏗️
+##### Old
+The old design had SDK integrated into dApp:
+
+
+
+The replacement design with XCM API, there is no need for integrating XCM SDK. There is only a need to send the request. No more installing packages. Works way faster and offloads dApp from heavy computing to generate calls.
+
+
+
+##### New
+The newest architecture is similar to the one before it, however, dApps will now be able to call XCM Router through XCM API or integrate it as an independent package. XCM Router will benefit users with ease of exchanging and transferring assets to another chain as well as developers who can hide complex logic from users and integrate this feature with ease without the need for extensive research.
+
+
+
+This architecture is only proof of concept architecture. The final architecture may differ a little (Mostly because we want to make this as efficient as possible so if we find a better solution we will instead resort to it.
+#### Technology Stack 💻️
+- Vue.js
+- Node.js
+- Typescript
+- Polkadot API libraries
+- Nest.js
+
+### Ecosystem Fit 🌳
+
+#### XCM Router
+We strive to bring state-of-the-art technology to the ecosystem with any bright idea we get. SpellRouter XCM Router is no different. The implementation would become the first XCM Router in the Polkadot ecosystem.
+
+We aim to achieve XCM Router functionality by building a sovereign typescript package (for those who wish to implement it as a package) that will also be implemented in LightSpell XCM API (for those implementing LightSpell XCM API already). The core component for generating XCM calls will be ParaSpell XCM SDK. Other functionality regarding exchanges and logic will be unique to the Router itself. The XCM router will serve ecosystem users to transfer their assets cross-chain while giving them the ability to exchange them into different assets all in just one call (3 signatures). There were numerous suggestions for this tool in the ecosystem. Mainly because it brings the following benefits:
+
+- Ability to transfer assets cross-chain via XCM while being able to exchange them for another asset all within one call.
+- Offlift users from the complexity of moving assets to another chain in order to exchange tokens just to send them to another chain later
+- Developers able to hide asset exchange complexity and skip multiple implementation steps
+- Developers save the time required for complex research
+- Complex logic hidden in simple one-line calls
+
+An example of a Router call can be seen below:
+
+
+The choice of exchange Parachain will be automatic in a later version of XCM Router so users will only have to select exchange Parachain manually if they wish to.
+
+A high overview of Router functionality can be seen below:
+
+
+
+
+#### XCM API
+As mentioned in a tweet from Alice&Bob, we need Chain APIs to put XCM on steroids - [link](https://twitter.com/alice_und_bob/status/1664564442456109057?cxt=HHwWgsC9pdGi3JkuAAAA).
+
+We aim to achieve this by utilizing the XCM-SDK technology we built previously.
+Using XCM API compared to implementing XCM SDK into dApp can bring three main benefits:
+- Calls are generated much quicker
+- API is much simpler to implement than SDK
+- No need to install anything (Comes with the benefit of saving space and without issues with dependencies)
+
+Why we chose NestJS for XCM API:
+By choosing Nest.js as our backend HTTP REST API framework, we can harness the power of Node.js, leverage TypeScript's benefits, ensure maintainability through its modular architecture, and take advantage of its extensive community support. This enabled us to build a reliable, scalable, and well-documented XCM API that seamlessly integrates with the existing XCM SDK. In addition, Nest.js offers a powerful code generation feature that allows us to quickly scaffold boilerplate code for controllers, services, modules, and more. By utilizing the Nest.js code generator, we can significantly reduce development time and effort, ensuring rapid prototyping and efficient implementation of the XCM API endpoints. Compared to other TypeScript frameworks, Nest.js stands out with its modular architecture, seamless integration with Node.js, and strong community support, offering developers a scalable and maintainable solution.
+
+As API is now fully implemented we can observe its metrics for the first month it is deployed:
+
+
+We can see, that API serves between 500 to 1000 requests in a day. API uptime is 100%. API is completely free for everyone to use, implement or privately deploy.
+It now features various error prevention mechanisms (Valid wallet address check) and analytic tools to report errors that are not handled by API or report API usage (Strictly without collecting any sensitive user data).
+
+#### XCM SDK
+
+There are not many XCM & XCMP-related development tools released currently. We aim to aid this mostly empty space and help developers understand XCM & XCMP as the current state-of-the-art technology by providing documentation and a set of tools which help them do development tasks more easily and faster.
+
+In Polkadot and Kusama ecosystems, there are few XCM-related tools in development. For example, Moonbeam XCM SDK and Parity Asset Transfer API. We bring a comparison table that compares them to our ParaSpell XCM SDK.
+| Features | ParaSpell XCM SDK | Moonbeam XCM SDK | Parity Asset Transfer API|
+| -----: | ----------- | ------------- | -----------|
+|UMP Support|Implemented|Implemented|Implemented (only for 2 Chains)|
+|DMP Support|Implemented|Implemented|Implemented (only for 2 Chains)|
+|HRMP Support|Implemented|Implemented|To be implemented|
+|No. of chains implemented|45 incl. Relay chains (To change to more chains with next update)|42 incl. Relay chains|4 incl. Relay chains|
+|Support for NFT transfers|Planned to be implemented|Not implemented| Planned to be implemented|
+|Multi-asset transfer support|Planned to be implemented|Not implemented|Planned to be implemented|
+|Multi-location specification|Automatic|Automatic|Required in some scenarios|
+| Build pattern | Integrated as intuitive as possible | Integrated, not as intuitive to implement however | Only function style call construction|
+| Support for asset pallet operations | Integrated | Not integrated | Not integrated|
+| Support for HRMP Channel operations | Integrated users can open & close HRMP channels on their local chain (Useful feature for devs) | Not integrated | Not integrated|
+| Support for checking details that do not change | Integrated & also be covered with some error handling eg (too little amount being sent, not sufficient for XCM transfer) | Integrated in the form of a small "map" for different Tokens & Node IDs | Integrated in form of Map|
+
+We are currently in talks with several Parachain teams that like the idea of unified SDK for XCM transfers as much as we do. SDK that unifies XCM can be very helpful for the entire ecosystem in our opinion. With the introduction of XCM API and soon XCM Router this improves even further.
+
+Our target audiences are Web3 projects and starting/current blockchain developers.
+
+As SDK is also fully developed and its metrics are available to the public we can see, that it is still used a lot by developers in the ecosystem (Even after the API release).
+
+
+## Team :busts_in_silhouette:
+
+### Team members
+
+Dušan Morháč - Student, project Founder & Core Dev. Faculty of Informatics and Information Technologies STU in Bratislava
+
+Michael Absolon - Student, XCM SDK & XCM API Core Dev. Faculty of Informatics and Information Technologies STU in Bratislava
+
+### Contact
+
+- **Contact Name:** Dušan Morháč
+- **Contact Email:** dudo.morhac@gmail.com
+
+
+### Legal Structure
+
+- **Registered Address:** Tomášovská 453/2 Kalinovo 98501 Slovakia
+- **Registered Legal Entity:** Adam Morháč
+
+### Team's experience
+- Dušan is the founder & researcher behind this project and he has successfully presented it at the international conference ICECET2022 held in Prague from which there is an article regarding the XCMP & ParaSpell project. It is published by IEEE - [link](https://ieeexplore.ieee.org/document/9872938). He also successfully presented it at the ICBC 2023 conference held in Dubai. The article was published in [IEEE Enhancing XCMP Interoperability Across Polkadot Paraverse | IEEE Conference Publication](https://ieeexplore.ieee.org/document/10174872). Dušan studies Blockchain technology and had a bachelor's thesis about cross-blockchain sharing from which this idea was born. Dušan continues research on this idea in his Master's thesis. He is actively working on [LightSpell and ParaSpell](https://github.com/paraspell) full-time & has also participated in other ecosystem projects. Recently he attended Polkadot Blockchain Academy 2023 in Buenos Aires which gave him a lot of insight into the ecosystem and he also graduated from the academy successfully. Here is the [NFT that was minted as a certificate by Parity](https://singular.app/collectibles/statemine/20/12).
+
+And here is a certificate in physical form:
+
+
+
+- Michael is a dedicated TypeScript developer with 2 years of full-time experience in the Web2 sphere. Michael's expertise in this field was further solidified in 2019 when he won first place in the Junior Internet Web competition for his online multiplayer game, which was written in JavaScript. In addition to his professional background, Michael also achieved a bachelor's degree in the same computer science University as Dušan and he is currently pursuing a master's degree which focuses on Blockchain. His passion for technology led him to explore Blockchain technology in his free time. He was recently offered the opportunity to work on ParaSpell XCM SDK & LightSpell XCM API with Dušan and he delivered many of the key features SDK & API now offer.
+### Team Code Repos
+
+- https://github.com/paraspell/xcm-api
+- https://github.com/paraspell/xcm-sdk
+- https://github.com/paraspell/docs
+
+### Team Github Profiles 🧑🎓
+
+- https://github.com/dudo50 Dušan Morháč
+- https://github.com/michaeldev5 Michael Absolon
+
+### Team LinkedIn Profiles 🧑🎓
+
+- https://www.linkedin.com/in/dudo50/
+- https://www.linkedin.com/in/michael--absolon/
+
+## Development Status :open_book:
+We are currently finishing maintenance tasks and issues that are open in XCM SDK, XCM API and Docs repositories. After that, we wish to shift our focus to the development of an XCM Router which we already have laid out the structure for and we have basic functionality laid into small steps that will help us achieve making this state-of-the-art technology.
+
+As there are no XCM Routers currently in the ecosystem, this challenging task motivates us to fill the gap once again (Just like with XCM API).
+
+## Development Roadmap :nut_and_bolt:
+
+### Overview
+
+- **Total Estimated Duration:** 5 months
+- **Full-Time Equivalent (FTE):** 1 FTE
+- **Total Costs:** 22 000 USD
+
+### Milestone 1 - Create XCM Router and move all three tools into Monorepo
+
+- **Estimated duration:** 3 months ⌛️
+- **FTE:** 1
+- **Costs:** 12 000 USD 💰️
+
+| Number | Deliverable | Specification |
+| -----: | ----------- | ------------- |
+| 0a. | License | MIT |
+| 0b. | Documentation | We will provide both readme.md and official docs documentation |
+| 0c. | Testing and Testing Guide | Testing guide will be mentioned in official docs|
+| 0e. | Create Medium article about development of early Router | Add article covering early XCM Router version |
+| 1.a | Integrate early version of XCM Router I| This version will contain additional detail about exchange Parachain (XCM Router will not select exchange automatically yet, the developer has to select from a provided list). The first version will feature functions like patterns to create calls. [See an example of function pattern](https://paraspell.github.io/docs/sdk/xcmPallet.html#function-pattern-xcm-call-from-relay-chain-to-parachain) |
+| 1.b | Integrate early version of XCM Router II| Compared to the first version, this version will feature a Builder pattern to enhance the developer experience. [See an example of builder pattern](https://paraspell.github.io/docs/sdk/xcmPallet.html#builder-pattern-xcm-call-from-relay-chain-to-parachain) |
+| 2. | Update docs to cover early XCM Router version| Add comprehensive guide that covers usage of early XCM Router version|
+|3.|Create unit tests for XCM Router|Create unit tests for core features in XCM Router|
+
+### Milestone 2 - Enhance XCM Router and feature automatic tool updating
+
+- **Estimated duration:** 2.5 months ⌛️
+- **FTE:** 1
+- **Costs:** 10 000 USD 💰️
+
+| Number | Deliverable | Specification |
+| -----: | ----------- | ------------- |
+| 0a. | License | MIT |
+| 0b. | Documentation | We will provide both readme.md and official docs documentation |
+| 0c. | Testing and Testing Guide | Testing guide will be mentioned in official docs|
+| 0e. | Create Medium article about development of latest XCM Router | Add article covering new features & improvements brought with SpellRouter☄️ |
+| 1. | Integrate automatic exchange chain selection into XCM Router | Integrate automatic exchange chain selection into the router (If the user wishes they can manually insert it otherwise Router will select automatically). XCM Router will try to select an exchange with the best pool/price. To see the difference between automatic and manual selection feel free to see the [following image](https://user-images.githubusercontent.com/55763425/277431789-cc3892dc-4452-49e1-a201-19edbc6f20d8.png)|
+| 2. | Integrate XCM Router into LightSpell XCM API | Integrate core functionality of XCM Router into LightSpell XCM API |
+|3.a| Update unit tests for new XCM Router functionalities| Update unit tests for new XCM Router functionalities|
+|3.b| Create integration tests for XCM Router|Create integration tests for core features in XCM Router|
+|3.c| Update integration, unit and e2e tests for LightSpell XCM API| Add new integration,unit & e2e tests for core LightSpell XCM API XCM Router integration|
+| 4.a | Cover latest automatic exchange chain selection in XCM Router section (Docs) | Add comprehensive guide covering automatic selection in XCM Router section |
+| 4.b | Cover XCM Router integration in XCM API section (Docs) | Cover XCM Router integration in LightSpell XCM API Section |
+
+## Future Plans 🔭
+- We wish to implement XCM v3 NFT transfer support
+- Once XCMP is out, we deprecate HRMP in SDK in favour of it.
+- Continue shaping XCM API to be as developer-friendly as possible
+- Continue gaining project integrations
+- Make sure XCM API uptime is nearing 100% and API works as should at all times
+- Improve XCM Router and add new ways to simplify call constructions
+
+Our focus will always remain on developer experience as well as being open source, completely free, common good and helpful to others.
+Another future goal that we try to keep is to continue innovating in the XCM area - bringing new state-of-the-art tech.
+
+## Additional Information :heavy_plus_sign:
+
+**How did you hear about the Grants Program?** Personal recommendation
+
+##### Project achievements in chronological order ⌛️
+
+- 📙 Article about the project created & presented at international conference ICECET2022 held in Prague (450 out of 1000+ articles accepted) Link to IEEE publication - [IEEE Sharing Fungible Assets Across Polkadot Paraverse](https://ieeexplore.ieee.org/document/9872938/)
+- 🥈 2nd Prize, Build an XCM-related Tool for Moonbeam - Polkadot North America Hackathon [Hackathon entry](https://devpost.com/software/polkachange-cross-blockchain-transfer-tool)
+- 🥉 3rd Prize, EVM+ DApp for aUSD yield - Polkadot North America Hackathon [Hackathon entry](https://devpost.com/software/polkachange-cross-blockchain-transfer-tool)
+- 🎈 Web 3 Foundation base grant [Application](https://github.com/w3f/Grants-Program/pull/1118), [Delivery](https://github.com/w3f/Grant-Milestone-Delivery/pull/584)
+- 🐍 [Basilisk](https://bsx.fi/) treasury proposal 2 / 2 Approved [link](https://basilisk.subsquare.io/treasury/proposal/2), [link2](https://basilisk.subsquare.io/treasury/proposal/4)
+- 🔭 Web 3 Foundation phase 2 grant Milestone 3 / 3 delivered [Application](https://github.com/w3f/Grants-Program/pull/1245), [Delivery1](https://github.com/w3f/Grant-Milestone-Delivery/pull/670), [Delivery 2 & 3](https://github.com/w3f/Grant-Milestone-Delivery/pull/715)
+- 📕 Article about Polkadot & ParaSpell created & accepted to be presented at international cross-chain conference IEEE ICBC 2023 held in Dubai - [IEEE Enhancing XCMP Interoperability Across Polkadot Paraverse](https://ieeexplore.ieee.org/document/10174872)
+- 💼 Kusama Treasury Funding proposal number 1 - Upgrade SDK, [Application](https://kusama.subsquare.io/referenda/referendum/123s), [Delivery](https://docs.google.com/document/d/1lMY_8EtQ41IX7Zn9VIMAiG1k3oLYN0h_lVj8dWDwZ_k/edit?usp=sharing)
+- 🏗️ Web 3 Foundation phase 3 grant (Make SDK better) Milestone 1 / 1 delivered [Application](https://github.com/w3f/Grants-Program/pull/1589), [Delivery](https://github.com/w3f/Grant-Milestone-Delivery/pull/836)
+- 📘 Article about Polkadot & ParaSpell created & accepted to be presented at international cross-chain conference IEEE BCCA 2023 held in Kuwait [links TBA]
+- 🥈 Second place at sponsored prices Polkadot Global Series APAC 2023 Hackathon: Build a Connected Contract With Moonbeam [Linkedin post announcement](https://www.linkedin.com/posts/angelhack_polkadothackathonapac-koreablockchainweek-activity-7097217757724758016-8pJ_?utm_source=share&utm_medium=member_desktop)
+- 🥇 First place at Polkadot Global Series APAC 2023 Hackathon Finale [Finalist announcement post](https://www.linkedin.com/posts/angelhack_polkadothackathonapac-koreablockchainweek-activity-7097217757724758016-8pJ_?utm_source=share&utm_medium=member_desktop), [Final result](https://drive.google.com/drive/folders/1YxFJ4NO9_mMyNsXoPKboFfYHwHM1AJHv?usp=sharing), [Final result announcement post](https://www.linkedin.com/posts/angelhack_polkadothackathonapac-activity-7108072292718428160-i1dr?utm_source=share&utm_medium=member_desktop)
+- 🚀 Web 3 Foundation phase 4 grant (Build XCM-API) Milestone 1 / 1 delivered [Application](https://github.com/w3f/Grants-Program/pull/1817), [Delivery](https://github.com/w3f/Grant-Milestone-Delivery/pull/972)
+- 👷♂️ Maintenance funded by Kusama treasury from October 2023 until February 2024 [Referenda link](https://kusama.polkassembly.io/referenda/277)
diff --git a/applications/Syncra.md b/applications/Syncra.md
index 20f2ea99ba2..3764804ae1f 100644
--- a/applications/Syncra.md
+++ b/applications/Syncra.md
@@ -3,6 +3,7 @@
- **Team Name:** Syncra
- **Payment Address:** 15Geo1RfLLM1PmPsD4uggts1Ht5LrWUChBDruLPqt5EgFKPB (PolkaDOT - USDT)
- **Level:** 2
+- **Status:** [Terminated](https://github.com/w3f/Grants-Program/pull/1762#issuecomment-1769273868)
## Project Overview
@@ -286,4 +287,4 @@ Web3 Foundation Website, and Personal Recommendation.
### Previous grants you may have applied for
-- Aleph Zero Grants program
\ No newline at end of file
+- Aleph Zero Grants program
diff --git a/applications/index.md b/applications/index.md
index 7b9afc76afe..f00cf5c3f81 100644
--- a/applications/index.md
+++ b/applications/index.md
@@ -51,6 +51,10 @@ Besides, **there is a clear difference between an application being accepted and
| [LimeChain](https://github.com/LimeChain) | [Polkadot Protocol Conformance Tests Research](./Polkadot-Protocol-Conformance-Tests.md) | [GitHub](https://github.com/LimeChain) | ☐ | ☐ | ☐ |
| [KodaDot](https://kodadot.xyz/) | [AssetsHub NFT indexer](./kodadot_assethub_nft_indexer_statemine_statemint.md) | [GitHub](https://github.com/kodadot) | ☐ | ☐ | ☐ |
| [Apollos Collective](https://rhys.tech) | [Infimum](./infimum.md) | [GitHub](https://github.com/rhysbalevicius) | ☐ | ☐ | ☐ |
+| [CoinFabrik](https://www.coinfabrik.com/) | [CoinFabrik On Ink Integration Tests 2](CoinFabrik_On_Ink_Integration_Tests_2.md) | [GitHub](https://github.com/CoinFabrik) | ☐ | ☐ | ☐ |
+| [Plutonication](https://github.com/cisar2218/Plutonication) | [Plutonication](Plutonication.md) | [GitHub](https://github.com/cisar2218/Plutonication) | ☐ | ☐ | ☐ |
+| [gmajor](https://github.com/gmajor-encrypt) | [JsonRpsee socks5 proxy](JsonRpsee-socks5-proxy.md) | [GitHub](https://github.com/gmajor-encrypt) | ☐ | ☐ | ☐ |
+| [ParaSpell](https://github.com/paraspell) | [SpellRouter](SpellRouter-proposal.md) | [GitHub](https://github.com/paraspell) | ☐ | ☐ | ☐ |
[🔝](#top)
@@ -62,17 +66,17 @@ Besides, **there is a clear difference between an application being accepted and
| [ZeroDAO](https://github.com/ZeroDAO) | [Melodot](./Melodot.md) | [GitHub](https://github.com/ZeroDAO) | ☐ | ☒ | ☒ |
| [Starks](https://github.com/tur461) | [XCM tool for NFTs](./xNFT.md) | [GitHub](https://github.com/tur461) | ☐ | ☐ | ☐ |
| [ChainSafe](https://chainsafe.io/) | [Polkadot Snap Maintenance](./maintenance/Substratesnap_Maintenance.md) | [GitHub](https://github.com/ChainSafe/metamask-snap-polkadot) | ☐ | ☐ | ☐ |
-| [justmert](https://github.com/justmert) | [DOTLY: Revolutionizing Polkadot Account Statistics](./dotly.md) | [GitHub](https://github.com/justmert/dotly) | ☐ | ☐ | ☐ |
+| [justmert](https://github.com/justmert) | [DOTLY: Revolutionizing Polkadot Account Statistics](./dotly.md) | [GitHub](https://github.com/justmert/dotly) | ☐ | ☒ | ☒ |
| [Federico Cicciarella](https://www.linkedin.com/in/federicocicciarella/?originalSubdomain=it) | [Tracking Chain](./tracking_chain.md) | [GitHub](https://github.com/TrackingChains/TrackingChain) | ☐ | ☒ | ☐ |
| [TPScore](https://github.com/its-a-setup) | [TPScore](./TPScore.md) | [GitHub](https://github.com/its-a-setup) | ☐ | ☒ | ☒ |
-| [Orochi Network](https://www.orochi.network/) | [Research and development MPC ECDSA](./orochi-network-orosign-part1.md) | [GitHub](https://github.com/orochi-network) | ☐ | ☐ | ☐ |
+| [Orochi Network](https://www.orochi.network/) | [Research and development MPC ECDSA](./orochi-network-orosign-part1.md) | [GitHub](https://github.com/orochi-network) | ☐ | ☒ | ☒ |
| [k/factory](https://k-f.co/) | [On-Chain Automated Treasury Management](./centrifuge-twamm.md) | [GitHub](https://github.com/centrifuge) | ☐ | ☐ | ☐ |
-| [AISLAND DAO](https://aisland.io) | [Aisland Docsig](./Aisland-DocSig.md) | [GitHub](https://github.com/aisland-dao) | ☐ | ☒ | ☐ |
+| [AISLAND DAO](https://aisland.io) | [Aisland Docsig](./Aisland-DocSig.md) | [GitHub](https://github.com/aisland-dao) | ☐ | ☒ | ☒ |
| [Eiger](https://www.eiger.co/) | [Storage solution on Polkadot](./Eiger_Storage_on_Polkadot_1.md) | [GitHub](https://github.com/eigerco) | ☐ | ☐ | ☐ |
| [Salaheldin Soliman](https://github.com/salaheldinsoliman) | [Solang Playground](Solang_Playground.md) | [GitHub](https://github.com/salaheldinsoliman) | ☐ | ☐ | ☐ |
| [P2P.ORG](http://p2p.org/) | [P2P data platform](data_platform_with_deep_indexed_data_and_staking_reports.md) | [GitHub](https://github.com/p2p-org) | ☐ | ☐ | ☐ |
| [CoinFabrik](https://www.coinfabrik.com/) | [CoinFabrik On Ink Integration Tests](CoinFabrik_On_Ink_Integration_Tests.md) | [GitHub](https://github.com/CoinFabrik) | ☐ | ☒ | ☒ |
-| [Stake Plus Inc](https://stake.plus) | [Treasury Tracker](TreasuryTracker.md) | [GitHub](https://github.com/stake-plus) | ☐ | ☐ | ☐ |
+| [Stake Plus Inc](https://stake.plus) | [Treasury Tracker](TreasuryTracker.md) | [GitHub](https://github.com/stake-plus) | ☐ | ☒ | ☒ |
| [MOBR Systems](https://www.mobr.ai) | [Polkadot Analytics Platform](polkadot_analytics_platform.md) | [GitHub](https://github.com/mobr-ai) | ☐ | ☒ | ☐ |
| [Infra3](https://network.infra-3.xyz) | [Hyperdot - Powerful data analysis and creations platform](Hyperdot.md) | [GitHub](https://github.com/Infra3-Network/hyperdot) | ☐ | ☐ | ☐ |
| [David Semakula](https://github.com/davidsemakula) | [ink! analyzer (phase 2)](ink-analyzer-phase-2.md) | [GitHub](https://github.com/ink-analyzer) | ☐ | ☒ | ☐ |
@@ -83,12 +87,12 @@ Besides, **there is a clear difference between an application being accepted and
| [Rust Syndicate x Decentration](https://www.decentration.org/) | [XCMSend](./xcmsend.md) | [GitHub](https://github.com/decentration) | ☐ | ☒ | ☐ |
| [Off Narrative Labs](https://github.com/Off-Narrative-Labs) | [Tuxedo Parachain Support](./tuxedo_parachain.md) | [GitHub](https://github.com/Off-Narrative-Labs) | ☐ | ☐ | ☐ |
| [PolyCrypt GmbH](https://polycry.pt) | [Distributed Cryptography for Polkadot Wallets](./distributed_cryptography_for_polkadot_wallets.md) | [GitHub](https://github.com/perun-network) | ☐ | ☐ | ☐ |
-| [Open Smart Contract](https://github.com/OpenSmartContract) | [ISO20022 PoC](./ISO20022.md) | [GitHub](https://github.com/OpenSmartContract) | ☐ | ☐ | ☐ |
+| [Open Smart Contract](https://github.com/OpenSmartContract) | [ISO20022 PoC](./ISO20022.md) | [GitHub](https://github.com/OpenSmartContract) | ☐ | ☒ | ☒ |
| [DAOsign](https://daosign.org/) | [DAOsign](./DAOsign.md) | [GitHub](https://github.com/DAOsign) | ☐ | ☐ | ☐ |
| [Zondax AG](https://zondax.ch/) | [PoC Polkadot Conformance Tests](./polkadot_tests.md) | [GitHub](https://github.com/zondax) | ☐ | ☐ | ☐ |
| [SO/DA zone](https://github.com/sodazone) | [Ocelloids XCM Transfer Monitoring Service](ocelloids_xcm_monitoring_service.md) | [GitHub](https://github.com/sodazone) | ☐ | ☐ | ☐ |
| [Moonsong Labs](https://moonsonglabs.com/) | [StorageHub](./StorageHub.md) | [GitHub](https://github.com/Moonsong-Labs) | ☐ | ☐ | ☐ |
-| [Jonathan Brown](https://acuity.social/) | [Hybrid Explorer Phase 2](hybrid2.md) | [GitHub](https://github.com/hybrid-explorer) | ☐ | ☐ | ☐ |
+| [Jonathan Brown](https://acuity.social/) | [Hybrid Explorer Phase 2](hybrid2.md) | [GitHub](https://github.com/hybrid-explorer) | ☐ | ☒ | ☐ |
| [Coong Crafts](https://coongcrafts.io/) | [DelightfulDOT](delightfuldot.md) | [GitHub](https://github.com/CoongCrafts) | ☐ | ☐ | ☐ |
| [Lastic](https://www.lastic.xyz/) | [Lastic](Lastic.md) | [GitHub](https://github.com/LasticXYZ) | ☐ | ☐ | ☐ |
@@ -101,7 +105,7 @@ Besides, **there is a clear difference between an application being accepted and
| [Interstellar](https://www.interstellar.gg/) | [Interstellar - Wallet Phase 2](./Interstellar-network2.md) | [GitHub](https://github.com/Interstellar-Network) | ☐ | ☒ | ☒ |
| [Valletech AB](https://valletech.eu/) | [DINFRA](./DINFRA.md) | [GitHub](https://gitlab.com/polkawatch) | ☐ | ☒ | ☐ |
| [DAuth](https://github.com/DAuth-Network) | [DAuth](./dauth_network.md) | [GitHub](https://github.com/DAuth-Network) | ☐ | ☐ | ☐ |
-| [Galaxy.Do](https://galaxy.do) | [Galaxy: Three-dimensional Web for Polkadot Users](./galaxy.md) | [GitHub](https://github.com/7flash) | ☐ | ☒ | ☐ |
+| [Galaxy.Do](https://galaxy.do) | [Galaxy: Three-dimensional Web for Polkadot Users](./galaxy.md) | [GitHub](https://github.com/7flash) | ☐ | ☒ | ☒ |
| [Web3 Labs Ltd](https://www.web3labs.com/) | [Sirato (Epirus) Substrate Explorer - Phase III](./sirato_substrate_phase3.md) | [GitHub](https://github.com/web3labs) | ☐ | ☒ | ☒ |
| [Collective Intelligence Labs](https://collectiveintelligence.dev/)| [Omnichain Infrastructure](./CILA-omnichain-infrastructure.md) | [GitHub](https://github.com/Collective-Intelligence-Labs) | ☐ | ☒ | ☐ |
| [TradeLink](https://tradelink.pro/) | [Sandox](./sandox.md) | [GitHub](https://github.com/BEARlogin) | ☐ | ☒ | ☐ |
@@ -115,7 +119,7 @@ Besides, **there is a clear difference between an application being accepted and
| [Talentica Software](https://www.talentica.com/) | [Implementation Benchmarking Milestone 3](ink-pallet-benchmarking-phase-2.md) | [GitHub](https://github.com/Nikhil-Desai-Talentica) | ☐ | ☒ | ☒ |
| [Deep Ink Ventures GmbH](https://github.com/deep-ink-ventures) | [Stylograph](Stylograph.md) | [GitHub](https://github.com/deep-ink-ventures) | ☐ | ☒ | ☒ |
| [Zeeve](https://www.zeeve.io) | [Ink Playground IDE Improvements](ink-playground-ide-improvements.md) | [GitHub](https://github.com/Zeeve-App) | ☐ | ☐ | ☐ |
-| [Scio Labs](https://scio.xyz/) | [XCM Domain Name Service](xcm-domain-service.md) | [GitHub](https://github.com/scio-labs) | ☐ | ☒ | ☐ |
+| [Scio Labs](https://scio.xyz/) | [XCM Domain Name Service](xcm-domain-service.md) | [GitHub](https://github.com/scio-labs) | ☐ | ☒ | ☒ |
| [Gloslab](https://github.com/smiasojed) | [Contracts performance measurement tool proposal](contracts-tool.md) | [GitHub](https://github.com/smiasojed) | ☐ | ☒ | ☐ |
| [Nikita Orlov PR](https://github.com/stringnick) | [Faucet chat based bot](faucet-bot.md) | [GitHub](https://github.com/stringnick) | ☐ | ☒ | ☒ |
| [Societal Labs Ltd.](https://www.sctl.xyz/) | [Societal Saas Pricing](societal_saas_pricing.md) | [GitHub](https://github.com/sctllabs) | ☐ | ☒ | ☒ |
@@ -126,9 +130,9 @@ Besides, **there is a clear difference between an application being accepted and
| [Zaniyar Jahany](https://github.com/Zaniyar/) | [Grantmaster](grantmaster.md) | [GitHub](https://github.com/Zaniyar/plant2earn/) | ☐ | ☐ | ☐ |
| [FiDi Tech](https://fidi.tech/) | [FiDi DotSight: Analytics Data Platform for DotSama](fidi-dotsight-analytics.md)| [GitHub](https://github.com/fidi-tech) | ☐ | ☒ | ☐ |
| [Ideal Labs](https://www.idealabs.network/) | [Cryptex](cryptex.md)| [GitHub](https://github.com/ideal-lab5) | ☐ | ☒ | ☐ |
-| [Xcavate](https://xcavate.io/) | [Real estate centric lending and asset minting protocol](Xcavate.md)| [GitHub](https://github.com/xcavateblockchain) | ☐ | ☐ | ☐ |
+| [Xcavate](https://xcavate.io/) | [Real estate centric lending and asset minting protocol](Xcavate.md)| [GitHub](https://github.com/xcavateblockchain) | ☐ | ☒ | ☒ |
| [Syncra](https://syncra.xyz) | [No Code DAO Maker and ZK Powered Private Voting Solution](Syncra.md)| [GitHub](https://github.com/SyncraDAO) | ☐ | ☐ | ☐ |
-| [P2P.ORG](http://p2p.org/) | [Validator Monitoring Service](Validator_Monitoring_Service.md)| [GitHub](https://github.com/p2p-org/polkadot_monitoring_service) | ☐ | ☐ | ☐ |
+| [P2P.ORG](http://p2p.org/) | [Validator Monitoring Service](Validator_Monitoring_Service.md)| [GitHub](https://github.com/p2p-org/polkadot_monitoring_service) | ☐ | ☒ | ☒ |
| [Colorful Notion](https://github.com/colorfulnotion) | [Deep Account Analytics in Three Tiers for the Polkadot Data Alliance](DeepAccountAnalytics-PolkadotDataAlliance.md)| [GitHub](https://github.com/colorfulnotion/) | ☐ | ☐ | ☐ |
| [Dastanbek Samatov](https://dastansam.github.io/) | [ISO-8553 PoC implementation](ISO-8583-implementation.md)| [GitHub](https://github.com/dastanbeksamatov) | ☐ | ☒ | ☐ |
| [Eiger](https://www.eiger.co/) | [Substrate Move System Pallet, pt. 1](Substrate_Move_System_Pallet_1.md)| [GitHub](https://github.com/eigerco) | ☐ | ☒ | ☒ |
diff --git a/applications/orochi-network-orosign-part1.md b/applications/orochi-network-orosign-part1.md
index 3e92a275415..3b9aa1db24a 100644
--- a/applications/orochi-network-orosign-part1.md
+++ b/applications/orochi-network-orosign-part1.md
@@ -1,7 +1,7 @@
# Orochi Network's proposal for research and development MPC ECDSA
- **Team Name:** Orochi Network
-- **Payment Address:** 0x2d309e09149259bD2b9a8C88985581B724d058b2 (ETH)
+- **Payment Address:** 167Zj4mv1jBTzJimSe7LngcRS7SBixsx3ZSCFr45Eo1SjWCY (USDT Polkadot)
- **[Level](https://github.com/w3f/Grants-Program/tree/master#level_slider-levels):** 1
## Project Overview :page_facing_up:
diff --git a/applications/project_aurras_mvp_phase_2.md b/applications/project_aurras_mvp_phase_2.md
index accc4756723..cb9f659c9ac 100644
--- a/applications/project_aurras_mvp_phase_2.md
+++ b/applications/project_aurras_mvp_phase_2.md
@@ -1,7 +1,7 @@
# Project Aurras - MVP - Phase 2
- **Team Name:** HugoByte AI Labs Private Limited
-- **Payment Address:** 1G5Fo5KfLSopTFKPRDUZgeCSU5PNY2kkD5 (BTC)
+- **Payment Address:** Fiat 20.10.2023, 06:33 UTC
- **[Level](https://github.com/w3f/Grants-Program/tree/master#level_slider-levels):** 2
## Project Overview :page_facing_up:
diff --git a/docs/Introduction/team.md b/docs/Introduction/team.md
index a267b0379dd..cd279081ef2 100644
--- a/docs/Introduction/team.md
+++ b/docs/Introduction/team.md
@@ -6,7 +6,7 @@ sidebar_position: 5
## W3F Grants Committee
-The committee consists of individuals who know the funding priorities of the Polkadot ecosystem, and is responsible for evaluating grant applications and providing feedback on these.
+The committee consists of individuals who know the funding priorities of the Polkadot ecosystem and is responsible for evaluating grant applications and providing feedback on these.
In cases where a niche expert opinion is desirable, one of the committee members may request such a review.
@@ -14,11 +14,9 @@ In cases where a niche expert opinion is desirable, one of the committee members
- [Aeron Buchanan](https://github.com/aeronbuchanan)
- [Gautam Dhameja](https://github.com/gautamdhameja)
- [David Hawig](https://github.com/Noc2)
-- [Diogo Mendonça](https://github.com/dsm-w3f)
- [Sebastian Müller](https://github.com/semuelle)
- [Bill Laboon](https://github.com/laboon)
- [Keegan Quigley](https://github.com/keeganquigley)
-- [Nikhil Ranjan](https://github.com/nikw3f)
- [Raul Romanutti](https://github.com/rrtti)
- [Seraya Takahashi](https://github.com/takahser)
- [Benjamin Weiß](https://github.com/BenWhiteJam)
@@ -29,10 +27,8 @@ In cases where a niche expert opinion is desirable, one of the committee members
Evaluators are individuals able to evaluate the technology delivered as a result of the Grants Program. The committee has the right to add or remove evaluators on the basis of supermajority.
- [David Hawig](https://github.com/Noc2)
-- [Diogo Mendonça](https://github.com/dsm-w3f)
- [Sebastian Müller](https://github.com/semuelle)
- [Keegan Quigley](https://github.com/keeganquigley)
-- [Nikhil Ranjan](https://github.com/nikw3f)
- [Seraya Takahashi](https://github.com/takahser)
## W3F Operations Team
@@ -40,5 +36,4 @@ Evaluators are individuals able to evaluate the technology delivered as a result
The Operations Team takes care of legal documents, invoicing and remittances.
- [Melanie Diener](https://github.com/meldien)
-- [Federica Dubbini](https://github.com/fededubbi)
- [Rouven Pérez](https://github.com/RouvenP)
diff --git a/docs/RFPs/jsonrpsee-proxy-support.md b/docs/RFPs/jsonrpsee-proxy-support.md
new file mode 100644
index 00000000000..711c6633646
--- /dev/null
+++ b/docs/RFPs/jsonrpsee-proxy-support.md
@@ -0,0 +1,75 @@
+# Socks5 proxy support for JsonRpsee
+
+* **Status:** Open
+* **Proposer:** flipchan
+
+## Project Description :page_facing_up:
+
+[JsonRpsee](https://github.com/paritytech/jsonrpsee) is an opensource Rust library used by several para and relay chain client libraries to connect to chains over ws or rpc.
+
+## Background story
+
+Tor is a anonymization project that has been active for several years. By utilizing a traffic obfusication protocol to route data, it enables users to anonymize their internet traffic. Several blockchain projects leverage this technology to allow users to connect to nodes over tor, inputting the .onion address of the rpc provider.
+
+By providing a .onion address for a rpc/ws node, we can allow users to have more privacy by masking the origination of the request (the sender's ip address).
+
+
+Gavin Wood mentioned onion-routing as an important future feature on Decoded 2023:
+
+
+[In february 2023](https://forum.polkadot.network/t/privhost-public-polkadot-kusama-and-edgeware-nodes-with-tor-v3-onion-support/2093), a small public rpc provider was launched in order to provide .onion rpc endpoints for handful of chains in the ecosystem.
+Privhost was later listed on the [awesome-substrate list](https://github.com/substrate-developer-hub/awesome-substrate#products-and-services).
+
+
+In order to connect to a .onion site, a user must pass it's connection through a tor socks5 proxy in order to resolve the .onion domain and connect.
+
+
+Several ecosystem projects want to add support for connecting to .onion, but are blocked due to JsonRpsee not having support for sock5 proxy.
+
+
+Third party pr's that are waiting for JsonRpsee to support socks5:
+- [Fedimint #391](https://github.com/fedimint/fedimint/issues/391#issuecomment-1643878929)
+- [Uptest #15](https://github.com/uptest-sc/uptest/issues/15)
+
+On 4th of September of 2022 a [pr was created](https://github.com/paritytech/jsonrpsee/issues/870) to start the process of adding socks5 support for JsonRpsee.
+Noone has had time to fix this issue and implement this feature, therefor this RFP.
+
+
+## Motivation
+- Enable client libraries to connect to .onion rpc nodes.
+
+
+### Ecosystem projects that rely on JsonRpsee
+- [Subxt](https://github.com/paritytech/subxt)
+- [Substrate](https://github.com/paritytech/substrate)
+- [Subwasm](https://github.com/chevdor/subwasm)
+- [Uptest](https://github.com/uptest-sc/uptest)
+- [Subway](https://github.com/AcalaNetwork/subway)
+
+## Deliverables :nut_and_bolt:
+
+* **Total Estimated Duration:** 4 weeks
+* **Full-time equivalent (FTE):** 4 weeks
+* **Total Costs:** 9000 USD(may be changed by the future team)
+
+
+### Milestone 1
+
+Please add additional milestones in the same way:
+* **Estimated Duration:** Duration of milestone 1
+* **FTE:** 4 weeks
+* **Costs:** 9000 USD(may be changed by the future team)
+
+
+| Number | Deliverable | Specification |
+| ------------- | ------------- | ------------- |
+| 0a. | License | Apache 2.0 / MIT / Unlicense|
+| 0b. | Documentation | Public documentation with implementation guides and sample code |
+| 0c. | Testing Guide |Rust Unit tests|
+| 0d. | Article |Article explaining how to utilize the socks5 support|
+| 1. | Middleware layer | In order to enable socks5 support, several modifications of the `WsTransportClientBuilder` needs to be implemented, described in [issue #1162](https://github.com/paritytech/jsonrpsee/issues/1162) |
+| 2. | Socks5 support |enable a jsonrpsee client to proxy connections using a socks5 proxy |
+
+
+#### Demonstrations
+- Connect to a .onion rpc node with jsonrpsee.
diff --git a/docs/rfps.md b/docs/rfps.md
index 73ab405b258..62fc4f16dec 100644
--- a/docs/rfps.md
+++ b/docs/rfps.md
@@ -26,6 +26,7 @@ If you find an open RFP here that you think you can address, feel free to [submi
| [anti-collusion_infrastructure.md](RFPs/anti-collusion_infrastructure.md) | 21.09.2023 |
| [formal_guarantees_for_grandpa.md](RFPs/formal_guarantees_for_grandpa.md) | 12.10.2023 |
| [ISO_20022.md](RFPs/ISO_20022.md) | 12.10.2023 |
+| [jsonrpsee-proxy-support.md](RFPs/jsonrpsee-proxy-support.md) | 19.10.2023 |
| [parachain_validation_conformance_testing.md](RFPs/parachain_validation_conformance_testing.md) | 18.01.2023 |
| [sub-consensus.md](RFPs/sub-consensus.md) | 23.02.2022 |
| [user-account-access-analysis.md](RFPs/user-account-access-analysis.md) | 07.01.2023 |