polymerdevs / quest-into-the-polyverse-phase-1 Goto Github PK

Experimental idea: Randomly reward users using your channel.

1. An application which randomly rewards users transacting towards a specified destination chain.
2. Every few hours (or after a transaction threshold) application reveals winner of the last cycle and decided a new destination chain.
3. Users transacting in that direction via this UI or any other application operating over the universal channel get rewarded.

Gamification: Reward can be entirely random or proportional to some activity you desire. The reward is revealed at the end of each cycle, which can either be time based or transaction based (users can then spam to reveal the winner early) - play with trade-offs wisely.

User story:

• As an application I want to bridge my protocol tokens between chains from my application interface.

Objectives:

• Build a bridging application that lets users bridge tokens between chains.

Implementation tips:

As an application deploying their own tokens on multiple chain,

• You can choose to deploy a lock and mint bridge that mints wrapped token representations under your project name.
• You can choose to deploy a burn and mint for tokens you first deploy on different chains and whitelist for your bridge.
• To further improve ease of integration you can choose to build the scaffolding of a UI or widget that protocols can then use.

Creative use of Acknowledgements

• In IBC when a packet is sent, it goes through three distinct phases of the packet lifecycle: (1) the initiating sendPacket transaction from the source chain, (2) the corresponding recvPacket transaction on the destination chain that executes a specific action (referred to as the 'onRecvPacket' callback action), and (3) finally a acknowledgment or timeout transaction. The acknowledgment serves as a notification to the originating chain about the receipt of the packet on the destination.

  NOTE: timeouts are currently not supported on testnet

• If the action involves the minting of a specific token on the destination chain, there are ways to improve UX: the user tokens on source are unlocked or not burned in case of a failed onRecvPacket callback action of minting new tokens.

References: Lock/burn and mint bridge , xERC20, OFT

Experimental idea: Allow users to bring BTC in the Superchain and bridge between various OP stack rollups via IBC.

Building in Web3 is all about open-sourced collaborations, present a proposal by studying other contributions like BitcoinMirror, Nomic, suggest a roadmap and let's build it.

Potential roadmap: To help with a future vision of how this project can evolve, think of an OP stack L2 which acts as the hub for minting bitcoin equivalents on any rollup connect to Polymer and acts as the Bitcoin client for Superchain.

Hello, this project is a gamified treasure raffle event.

Gameplay Mechanics: There are 15 boxes in the game (these boxes can be increased or decreased), these boxes are hidden with rewards in a completely random way (the number of rewards and winnings can be changed), including NFT rewards*, there are 3 keys (the number of keys can be increased), these boxes are used to open the chests Can be used for. You open it, you only have 3 rights.

User Settings: Each user is allowed to play only once; This event can be used to reward users who are eligible to win prizes.

repository of codes: https://github.com/Emir236070/crypto-chest/

Concept:
"Crypto Village" is a simulation game that allows players to create and manage a digital village on a decentralized platform. Each player begins as the owner of a parcel of land and builds various structures on it. Starting with limited resources, players engage in various activities to develop their village.

Gameplay:

Players start as landowners and construct buildings on their parcels of land. They begin with limited resources and can earn more by completing tasks rewarded with cryptocurrencies or by trading with other players.
To expand their villages, players construct additional buildings, engage in farming, raise livestock, and carry out other economic activities.
Players can sell their products and buy goods from other players at a decentralized marketplace.
All transactions within the crypto village are recorded on the blockchain, ensuring transparency and tracking of players' digital assets.
Features:

Decentralized reward systems: Players earn cryptocurrencies for completing tasks or interacting with other players.
Real-time economy: The economy fluctuates based on the supply and demand of resources, requiring players to adjust their trading strategies.
Community interaction: Players can trade with other village owners, form alliances, and collaborate to develop their crypto villages together.
Variable weather and events: Random events and weather changes require players to adjust their strategies and prepare their villages accordingly.
"Crypto Village" combines decentralized gaming experience with blockchain technology to provide players with an engaging and interactive experience.

• User story:

  • As an application developer I want to keep track of how fast transactions are being delivered on destination chain.
  • Get early alerts if latency spikes, indicating possible conjunction or network issues.

• Objective:

  • Build a tool that allows developers to input their channel ID and return them average transaction time of past transaction.

• Implementation tips:

  • Help them build alerts and test on the fly, in case a channel has been not used for a while, past transactions (10 or 100) can be used to estimate an average and in case a live tx takes significantly more than - the channel is flagged.

• Future scope

  • Addition to IBC explorer

Experimental idea: A gift link to help friends onboard to a new chain.

User story:

• A users I want to invite my friend to a new chain or rollup and gift them some initial funds to get started.

Objectives:

• The user can top up a vault on the target chain with funds from any chain or wallet they desire.
• User defines a time period in which their friend can claim these funds and generates a link by submitting the transaction.
• This link is then shared with the friend who can input their address and receive funds on the new chain.

Implementation tips:

• If the friend is entering a new chain/rollup then they might not have native gas tokens, its ideal to
  • Deduct the transaction fees from the user creating the gift link, ensuring a zero-cost experience for the recipient.
  • Convert a small portion of the gifted amount into the chain's gas token, equipping the recipient with immediate transaction capabilities.

Future development:

• Expansion into a Gifting Protocol: Envision transforming this platform into a comprehensive gifting ecosystem, allowing for the transfer of both monetary gifts and NFTs.
• Personalized NFT Gifting: Introduce a feature where users can upload an image to the gift, enabling the recipient to mint it as their first NFT.
• Flexible Destination Choices: Empower recipients with the freedom to select their preferred token or chain for receiving the funds, further developing into a payments interface or QR code system to pay or receive funds.
• Secure Timeout Feature: Implement a timeout function, that automatically refunds the funds to the sender if the gift remains unclaimed within the set period.

For this quest we have Catalyst entering as the perfect protocol to help in asset bridging with their cross-chain AMM. Link to their resources.

Note: In testnet Polymer only supports Optimism and Base, your test application should be operational on these chain to qualify.

User story:

• As a user I want to bridge my USDC and swap it on the destination rollup, deposit it into a vault or send to a different address.
• As an application I want to enable my users to deposit into my USDC vaults in a single-click from any other rollup without having to bridge separately.

Objectives:

• Build an interface that application developers can use to enable one-click USDC cross-chain actions. Wherein USDC is bridged via CCTP and an action is performed via Polymer once funds reach the destination.

Implementation tips:

• CCTP is the native bridge for transferring USDC between chains, many times users have to bridge their tokens and then perform an action on another chain.
• You can reduce the UX overhead by designing an interface that developers can to embed in their application and allow for easy cross-chain deposits via CCTP.
• You can choose to deploy a vault contract on Base that the user wishes to deposit funds in, and bridge their test USDC from Optimism.
• Kudos if you can build a deposit UI wherein users can select which chain they want to bridge USDC from and then deposit in the contract/vault directly.
• Fun fact: On mainnet can use Socket or LiFi to enable wider token support.

References: CCTP and testnet contracts

This is your chance to contribute to implementing the ICS27 standard in Solidity!

IBC is a well documented and battle-tested protocol with many developers contributing code/standards to improve its developer experience and help other applications build off of their work. The PIT empowers further contributions, there are a few IBC standards Polymer thinks can be used by a wide variety of applications.

IBC is a complete interop protocol with a well-defined specification, called the the InterChain Standards or ICS for short. There's a clear separation between the state and transport layers on the one hand (this is what Polymer has contributed to for L2-L2 commmunication) and the application layer.

In Phase 1 of the PIT we focus on the application layer. In Cosmos, where IBC originated, many standards have implementations as Go modules. The challenge you're presented with is to implement some of those for the EVM and Solidity.

Similar implementations already exist in EVM and we leave it to your best judgement to establish a fair analysis between them, propose and build a new standard that will help further the cosmosethereum.

Dive into the technicals between various standards which are available in IBC and their counter parts in Ethereum:

• Perform a technical overview of the designs.
• Compare the best features from each of the standards.
• Prepare a functioning solidity implementation and with an intuitive CLI for easier use.

Note: Research paper/proposal also counts as documentation in the rubric.

References: ICS27 go implementation, Create2

The Idea :

The polymer inscription process would embed cryptographic information onto the surface of the chain, ensuring data integrity and authenticity. These inscribed chains could then be used as physical carriers for transmitting messages or transactions across various blockchain platforms, enabling secure cross-chain communication without relying solely on digital interfaces. This concept could find applications in areas like supply chain management, decentralized finance, and secure communication protocols.

This is your chance to contribute to implementing the ICS31 standard in Solidity!

IBC is a well documented and battle-tested protocol with many developers contributing code/standards to improve its developer experience and help other applications build off of their work. The PIT empowers further contributions, there are a few IBC standards Polymer thinks can be used by a wide variety of applications.

IBC is a complete interop protocol with a well-defined specification, called the the InterChain Standards or ICS for short. There's a clear separation between the state and transport layers on the one hand (this is what Polymer has contributed to for L2-L2 commmunication) and the application layer.

In Phase 1 of the PIT we focus on the application layer. In Cosmos, where IBC originated, many standards have implementations as Go modules. The challenge you're presented with is to implement some of those for the EVM and Solidity.

Similar implementations already exist in EVM and we leave it to your best judgement to establish a fair analysis between them, propose and build a new standard that will help further the cosmosethereum.

Dive into the technicals between various standards which are available in IBC and their counter parts in Ethereum:

• Perform a technical overview of the designs.
• Compare the best features from each of the standards.
• Prepare a functioning solidity implementation and with an intuitive CLI for easier use.

Note: Research paper/proposal also counts as documentation in the rubric.

References: ICS31 go implementation

Issue Description:
Recognizing the need for seamless NFT interoperability, we propose integrating the Inter-Blockchain Communication (IBC) protocol to enable the transfer of NFTs between the Base and Optimism chains. IBC provides a standardized and secure framework for cross-chain communication, offering a promising solution to enhance the interoperability of NFTs across different blockchain networks.

Proposed Solution:
Integrate the IBC protocol to establish a secure and standardized communication channel between the Base and Optimism chains, allowing for the frictionless transfer of NFTs. This solution aims to leverage IBC's capabilities for cross-chain token transfers while ensuring compatibility with existing NFT standards like ERC-721 and ERC-1155.

Benefits:

1. Decentralized Interoperability: Enable users to transfer NFTs seamlessly between the Base and Optimism chains in a decentralized manner.
2. Utilize IBC Standards: Leverage the established IBC standards for secure and trustless communication between blockchains.
3. Enhance Ecosystem Collaboration: Contribute to the broader adoption of IBC and encourage collaboration between different blockchain networks.
4. Expand NFT Use Cases: Facilitate new use cases for NFTs by unlocking cross-chain functionalities, providing creators and collectors with increased flexibility.

Implementation Steps:

1. Research IBC protocol specifications and ensure compatibility with NFT standards.
2. Develop and test a prototype of the NFT interoperability solution using IBC.
3. Collaborate with relevant stakeholders, including developers, community members, and blockchain experts.
4. Conduct thorough audits to ensure the security and compliance of the proposed solution.
5. Document and communicate the implementation process for the benefit of developers and users.
6. Deploy the IBC-enabled NFT interoperability solution on both the Base and Optimism chains.

Additional Notes:
This issue is opened to gather community feedback and collaboration on implementing NFT interoperability between the Base and Optimism chains through the IBC protocol. Community insights and contributions are crucial for the success of this initiative.

Labels:

• interoperability
• NFTs
• IBC
• Base chain
• Optimism chain
• enhancement
• cross-chain

Milestone:
This issue is part of a broader effort to enhance blockchain interoperability, particularly focusing on NFTs, and aligns with the ongoing development of decentralized technologies.

NB; I'm not a dev, just an enthusiast for NFTs, IBC and Interoperability. 😁👍

1. To help developers visualize connections and client used by their application - mockups, wireframe, working website flow are welcome.
   1. Links to read more about connections and channels - Link
2. To help developers visualize packet life cycle and retrieve transaction data - suggest creative ways to level up our Packet explorer.
   1. Links to read more about Polymer transactions - Link

• References: mapofzones.com (This is meant to be a starting point, more creative ideas are welcomed)

• User story:

  1. As a new rollup I have to deploy vIBC smart contracts and set up clients and connections in order to connect with Polymer Hub.
  2. As an application developer I want to focus on applying the least possible overhead when adding IBC functionality to my contracts.

• Objective:

  • Build an SDK to help rollups deploy vIBC smart contracts easily.
  • Build an SDK to help application devs to scaffold and test IBC enabled contracts easily.

• Implementation tips:

  • Depending on the user group, there’s different implementation strategies
    1. vIBC SDK for chain developers: TO DO
    2. vIBC SDK for app developers:
       Start from the ibc-app-solidity-template repo and automate some features:
       • add Foundry support
       • add CLI tool to create custom channels, send packets
       • add CLI that implements scaffolding of IBC app templates
       • create an npm package for the Polymer chain registry, see Cosmos equivalent
  • Test out the deployment with different tools like ThirdWeb, Tenderly and more.
  • Build an issue report if required

• Link to relevant contracts - here

We can share our experiences here about what needs to be done when using the network.

User story:

• As a protocol I want to launch tokens on multiple chains so that my users can bridge them between chains easily.

Objectives:

• Build an interface to deploy a token standard on multiple chains with the ability to define a token ticker and token supply.

Implementation tips:

• Users can use the quick start guide for universal channel to deploy contract on different chains in one source transaction.
• Additionally, an added advantage of IBC is that it allows protocols to have sole ownership of their channel, so a protocol can choose to perform a channel handshake process to deploy a custom channel, and then deploy token contract that only their protocol can call.
• You can choose to build a script to perform the channel handshake process for token deploy in-order to make it a seamless process to deploy tokens.
• Feel free to generalize and extend the use-case to multichain deployment of any contract.

References: xERC20, OFT, IBC Channels, IBC Channels (bis)

Issue Description

As the Polymer Blockchain network continues to grow and integrate more dApps, the demand for efficient data indexing and retrieval will becomes increasingly critical. To address this, I propose leveraging Subsquid's decentralized query engine and data lake capabilities to enhance the Polymer network's data processing efficiency, particularly for dApps that require real-time data access and historical data analysis.

Proposed Solution

Subsquid provides a powerful ecosystem for batch extraction of large volumes of data from blockchain networks. It offers high-level libraries for extracting and filtering data, which can be thought of as Extract-Transform-Load (ETL) pipelines. These capabilities could be particularly beneficial for the following areas of the Polymer network:

1. dApp-Specific APIs: Utilize Subsquid's Squid SDK to build custom indexers that serve dApp-specific APIs. This would allow dApps on the Polymer network to sync quickly with historical data and switch seamlessly to real-time data, enhancing user experience and dApp responsiveness.

2. Data Analysis and Forensics: Implement data pipelines using Subsquid's technology to prepare, transform, and load large volumes of on-chain data. This would enable advanced data analysis and forensics, aiding developers and analysts in understanding on-chain activity and making informed decisions.

3. On-Chain Activity Monitoring: Create highly customizable data sources for dashboards and on-chain activity monitoring. By integrating Subsquid's indexing capabilities, Polymer can provide more granular and up-to-date insights into network transactions and events, which is essential for network security and optimization.

Expected Outcome

By integrating Subsquid's technology into the Polymer network, we can expect:

• Improved data indexing speed and accuracy.
• Enhanced query performance for both historical and real-time data.
• A more robust and developer-friendly environment for building and maintaining dApps.

User story:

• As a rollup I want to help users bridge existing tokens from other chains to improve liquidity and prevent unnecessary wrapped tokens on my chain.

Objectives:

• Primary objective: Build a lock and mint bridge with a feature to whitelist L2 and give them minting rights of the token contracts.
• Secondary objective: Build an L2 to L2 token mapping between an existing tokens on a L2 and deploy its corresponding new token contract on a destination L2.

Implementation tips:

• Usually token mapping for a rollup is done between L1 and L2, but given the landscape of rising rollups and liquidity fragmentation it has become important to allow free flow of assets between L2s.
• Polymer is best fit for this task as it uses the native L1<>L2 bridge for settlement when bridging between rollups, thus has the same security as that of the native bridge.
• You need to build a system that deploys a standardized vault for locking tokens on the source, and either mints tokens with the same token ticker on the destination, or mints from an existing contract you provide the rights.
• Note that currently our testnet only supports 2 chains, making this a relatively trivial task. In future a rollup can choose to allow token mapping from another rollup. In that case, you must make sure they mint from the same token contract and not create another representation.

References: Mapping tokens from L1 to L2

explore more on how to bridge from network to network

Experimental idea: Implement ERC404 and build a cross-chain NFT minting game:

1. 10,000 ERC-20 tokens & same number of associated “Replicant” NFTs.
2. If someone buys one full token on a DEX on Optimism testnet, one replicant NFT will be minted on Base.
3. If the token is sold, the connected NFT must be burned.

Gamification: Users initiate a sell from Base with a defined slippage (lower slippage means more points) and users on the Optimism DEX earn points for throwing off price to fail trades due to slippage (higher slippage failed tx means more points).

Note: Having fun with Acknowledgements by building complex onRecvPacket and onAcknowledgment behaviors.

• In IBC when a packet is sent, it goes through three distinct phases of the packet lifecycle: (1) the initiating sendPacket transaction from the source chain, (2) the corresponding recvPacket transaction on the destination chain that executes a specific action (referred to as the 'onRecvPacket' callback action), and (3) finally a acknowledgment or timeout transaction. The acknowledgment serves as a notification to the originating chain about the receipt of the packet on the destination.

  NOTE: timeouts are currently not supported on testnet

• If the action involves the minting of a specific token on the destination chain, there are ways to improve UX: the user tokens on source are unlocked or not burned in case of a failed onRecvPacket callback action of minting new tokens.

Welcome to the Teams for the Polyverse! This issue exists to help developers find like minded people to team up in case they are looking to collaborate with others. Whether you're looking to join a team or find team members, you're in the right place.

Team Requirement Template

Copy and paste the following template, fill in your team's information and add a comment at the bottom:

#### Team Members:
- [Member 1 GitHub Username] - [Role, e.g., Developer, Designer]
- [Member 2 GitHub Username] - [Role]
- ...

#### Looking for Members?:
- Yes, specify roles/positions needed 

#### Project Description:
Our project aims to solve [problem] by building [solution]. We plan to use [technologies]. 
Or link to quest issue. 

You can drop multiple ideas you are open to exploring as well. 

#### How to Reach Us:
- [Discord] - [Contact Information]

Make sure you have joined Polymer's discord community to help fellow devs find you easily.

Finding Team Members

Use the above template to list yourself or a team looking for members with a project description - this will help others find the right fit. Project description is to provide an idea of what makes you tick and help you or others find the right team members. Project is not set in stone, as a team you can choose to change your scope anytime.

You can reach out the to team on discord (recommended) or reply to their comment to show interest and how you can add value to their project.

ABSTRACT
Within the current context of the financial system, DESCENTRALIZED GOVERNANCE is changing how everyone understand new projects and how secures and enhances digital ecosystems.

Polymer is building to contribute towards cross-chain application on Ethtreum Layer -2 (EVM), and working on IBC in the Cosmos ecosystem.

OBJECTIVE
In order to bring descentralized governance, in case that Polymerlabs decides to issue a DAO within the EVM ecosystem, once Testnet evolvess to Mainet .
Snapshot helps DAOs organizing via off-chain by allowing users vote, using their wallets ,and those signed transactions are stored and counted as a final result is shown public.

TLDR:
Think of this as trading baseball cards but protocol.

The NFT Twins Protocol aims to streamline the process of swapping and trading non-fungible tokens (NFTs) by eliminating intermediaries and reducing friction. Its core functionality revolves around creating "twin" NFTs that are esentially mirrored copies of existing NFTs on different blockchain networks.

The protocol works as follows:

1. A user deposits their original NFT into a smart contract vault on the native blockchain.

2. The protocol then creates and mints a "twin" NFT on a desired target blockchain, representing the locked original NFT.

3. This twin NFT can be freely traded, swapped or used just like any regular NFT on the target chain.

4. To redeem the original NFT, the owner simply burns or sends back the twin NFT to the protocol's vault.

5. The protocol then releases the original, locked NFT back to the owner's wallet on the native chain.

By creating these interoperable "twin" NFT representations, users can bypass the need for centralized exchange platforms or other intermediaries. Trades between NFT twins on different chains can occur directly through peer-to-peer atomic swaps using connected smart contracts.

Key benefits include:

• Lower fees compared to centralized exchange platforms
• True asset decentralization and self-custody
• Increased liquidity by interconnecting NFT ecosystems across multiple chains
• Ability to easily move NFTs between chains while retaining full verifiable provenance

The protocol aims to abstractaway the underlying cross-chain mechanisms, providing a seamless experience where NFTs can easily traverse blockchain networks without sacrificing security or ownership.

Purpose: This dApp facilitates the buying and selling of digital assets (NFTs) across different blockchains. Users can explore, purchase, and sell NFTs from various chains using a single platform.

How It Works:

• User Registration and Wallet Integration: Users register on the dApp and connect their wallets from Ethereum, Binance Smart Chain, and other supported blockchains.

• NFT Discovery: Users can explore NFT collections across different blockchains through the dApp. For example, they can browse collections like CryptoKitties on Ethereum or Binance Collectibles on Binance Smart Chain.

• Buying and Selling: Users can purchase NFTs they like or list their own NFTs for sale. Payments can be made using tokens from the user's connected blockchain.

• Cross-Chain Swapping: Users can swap NFTs across different blockchains through the dApp. For instance, a user can exchange an NFT from Ethereum with one from Binance Smart Chain.

• Security and Monitoring: Through IBC, swapping transactions across different blockchains are conducted securely and can be tracked transparently. Users can monitor the status of their transactions at any time.

Keywords:

1. Multi-Chain: This dApp consolidates NFTs from different blockchains onto a single platform, making access easier for users.

2. Use of IBC: IBC enables secure communication between different blockchains, allowing the dApp to facilitate NFT swapping transactions quickly and securely.

3. Creative Ecosystem: Users can explore diverse NFTs across various blockchains and contribute to a broader creative ecosystem by swapping them.

This scenario showcases the potential of IBC and multi-chain dApps by enabling the swapping of NFTs across different blockchains.

This is your chance to contribute to implementing the ICS20 standard in Solidity!

IBC is a well documented and battle-tested protocol with many developers contributing code/standards to improve its developer experience and help other applications build off of their work. The PIT empowers further contributions, there are a few IBC standards Polymer thinks can be used by a wide variety of applications.

IBC is a complete interop protocol with a well-defined specification, called the the InterChain Standards or ICS for short. There's a clear separation between the state and transport layers on the one hand (this is what Polymer has contributed to for L2-L2 commmunication) and the application layer.

In Phase 1 of the PIT we focus on the application layer. In Cosmos, where IBC originated, many standards have implementations as Go modules. The challenge you're presented with is to implement some of those for the EVM and Solidity.

Similar implementations already exist in EVM and we leave it to your best judgement to establish a fair analysis between them, propose and build a new standard that will help further the cosmosethereum.

Dive into the technicals between various standards which are available in IBC and their counter parts in Ethereum:

• Perform a technical overview of the designs.
• Compare the best features from each of the standards.
• Prepare a functioning solidity implementation and with an intuitive CLI for easier use.

Note: Research paper/proposal also counts as documentation in the rubric.

References: ICS20 go implementation, xERC20, OFT

We welcome and encourage new ideas that can improve and expand the Polymer ecosystem. Your innovative concepts and proposals are vital to driving forward the future of interoperability solutions. This document provides a structured approach to submitting your ideas, ensuring they are clearly communicated and efficiently evaluated.

Note: While sharing your idea publicly is not mandatory, we highly encourage it as it can refine your concept into a viable protocol and attract potential contributors. However, if you prefer to develop your project discreetly, you can proceed to registration.

Proposal Template

You can use the following template to propose a new use-case in the comments below.

## TLDR
Our project aims to solve [problem] by building [solution]. We plan to use [standards/libs/eips].

## About the Product 

**User story:** 
- As a [type of user], I want [some goal] so that [some reason].
  
**Objectives:**
- Deliver [feature set] to enable [target audience] to [specific functionality or action], resulting in [desired outcome or benefit].
  
**Implementation tips:**
- Overview of how you plan to build it and where you fit in the user journey. 
- How does Polymer help you improve the UX for a dApp and their end-user. 
  
**References:** Link to standards, repos or libs you are planning to use. 


## About the team (In case you have a team already) 

### Team Name: [Your Team Name]

#### Team Members:
- [Member 1 GitHub Username] - [Role, e.g., Developer, Designer]
- [Member 2 GitHub Username] - [Role]
- ...

#### Looking for Members?:
- [Yes/No] If yes, specify roles/positions needed

#### How to Reach Us:
- [Discord] - [Contact Information]

Make sure you copy and past the Team details in the Team registry with a link to your comment here as Project Description to improve the chances of finding team mates.

What Happens Next?

• Acknowledgment: We'll acknowledge the receipt of your proposal and provide an initial assessment.
• Discussion: Your idea may undergo a discussion phase, where the community or Polymer team can ask questions and suggest enhancements.
• Decision: The Polymer team will make a final decision on whether to proceed with your idea and convert it into an issue.

Regardless of the outcome, we value your contribution and encourage continued participation.

Team should integrate a wallet checker Read only tool or app on discord to automatically verify transactions for quests, instead of team manually verifying different wallets and transactions which will take time and energy..
Something like Collab land.

Hi Polymer team! I’m claiming my contributor badge for completing the New Developer Toolkit tutorial.

Tutorial Repo: https://github.com/0xmohsina/polymertest2.git
Requested badge: Tutorial

This dApp will be a platform that facilitates the buying, selling, and trading of artworks. Different artworks may exist on different blockchains, but communication between these chains can be established using Polymer and IBC Middleware, enabling support for art trading.

foi isso que ele disse