Sponsor Challenges

Back to top

The GRAPH

  • The Graph will award 3 prizes to the best new subgraph on The Graph Explorer.

Resources

Subgraph Building Demos

 

Octopus Appchain Challenges

Summary. The Octopus Network is a multichain interoperable cryptonetwork for launching and running Web3.0 Substrate-based application-specific blockchains, aka appchains. 

The Octopus Network supplies new  chances for developing appchains easily on social network, creator economy, music sharing, blockchain game, and other utility apps  with Substrate blockchain framework.

Background. Appchain, aka application-specific blockchain, is a new form of blockchain application among other smart contract platforms. We can get big benefits from appchain on Non-DeFi application aspect. We choose Rust language and Substrate framework to develop appchain, and boot it on the Octopus Network, which supplies out-of-box security, interoperability, infrastructure and community for each appchain.

Challenge Requirements 

  • MUST be a Substrate chain
  • MUST connected and integrated to Octopus Network (very simple)
  • MUST be not kind of DeFi application

Considerations

  • You'd better have a whitepaer (draft)
  • A github codebase
  • A product and usage operation introduction demo (video)
  • More mature, more opportunity

Resources

Back to top

 

CRUST

Decentralized storage on NEAR

Summary. This Challenge includes how to use the Crust cross-chain storage solution to interact with the IPFS network on NEAR; develop NFT applications on NEAR and store Metadata on Crust; develop DApp on NEAR and decentralize Host on Crust; develop Metaverse on NEAR Apply and store/retrieve Metadata with Crust, etc.

Background. Decentralized storage is an indispensable part of the Web3 ecosystem. So how to store a variety of contracts/user data in a decentralized storage network is an important part of the NEAR ecosystem.

Challenge Requirements

  • Use Crust cross-chain solution with NEAR or directly use IPFS and Crust chain
  • [Bonus] Involve IPFSScan as IPFS storage explorer
  • [Bonus] Optimize Crust storage process on NEAR(toolkits/nodejs package/more)

Considerations

  • Open sourced
  • User base/impact

Resources

Back to top

 

CryptoDino

Summary. Turn Dino game in Brave browser into blockchain game, with NFTs to equip on the dinosaur and earning tokens based on how far played.

Background. Lots of people are playing Dino everyday when hitting a snag with Brave, this is a great opportunity for both onboarding new users into crypto and get people more excited to use Brave overall.

Challenge Requirements

  • implement “login with NEAR” to start in Dino
  • issue some skins for Dino on one of the NFT platforms or your own contract
  • show which skins user has while playing Dino
  • allow to equip Dino with one the skins while playing
  • player earns $DINO coin while playing
  • Trade $DINO for skins

Resources

Back to top

 

Stake delegation
  • Allow $FLX holders to delegate their tokens with validators
  • Write a delegation contract that allows users to deposit their FLX and stake it with validators of choice
  • The contract should pay out fees earned by the validator pro rata based on fees earned during staking duration

Delegates also need to be able to set a fee % that is subtracted from the staker's profits and paid to the delegate for it's service

  • Not everyone is technically savvy enough to run their own validators, rather than just hodling there flux, by delegating they can earn rewards based on the validators performance
  • Well-documented code with an emphasis on security. Unit and simulation tests showcasing the code's functionality and edge cases. Allows any $FLX holder to deposit FLX and delegate it to a validator, the validator can use the $FLX delegated to them to stake on the flux oracle contract.

Resources

docs, oracle-monorepo-near code & requester-sample-contract code and support

Back to top

 

Modules
  • Write a custom module on top of the Flux Oracle
  • A module is a contract that's allowed to create new data requests for the Flux Oracle. Your implementation could be many things, get creative!
  • Some ideas of what we'd like to see would be: TWAPs, aggregators and different pricing modules (especially subscription based, allowing protocols *n* data requests for *x* tokens per *e* epoch)
  • We designed our oracle to be extremely modular and allow for many different use cases to be built on top of, we want to see what a group of devs can come up with!
  • We judge on readable, well documented code that has unit and simulation tests to demo your modules features and edge cases. Your module will be judged and ranked on usefulness (for devs / protocols) and creativity.

Resources

docs, oracle-monorepo-near code & requester-sample-contract code) and support

Back to top

 

DODO

Innovating Governance

Summary. Come up with new ways to enhance DODO’s community governance system and bring it closer to being a true DAO.

Background. DODO’s ultimate goal is to become a decentralized autonomous organization with trustless governance in place. At the moment, though, only proposals posted to the Snapshot voting page are considered binding (if a quorum votes to pass them), and their implementation requires input from the DODO team.

We are looking for governance solutions that will help us bridge the gap between the dream and the reality. If you can think of something that can be a “next step” on DODO’s decentralization journey, integrating with our existing business model (e.g. DEX, NFTs, Crowdpooling) but pushing the envelope further toward becoming a DAO, this challenge is for you.

Challenge Requirements

Your proposal should be creative and unique, with original work and research. It should be productive and usable, with the potential to increase user engagement. Of course, the implementation of the idea must be solid as well.

  • Repo on Github

  • Video presentation

Resources

Back to top

 

Mintbase

Efficient token mass minting. Create an application that enables mass minting at Mintbase

Summary. Mintbase envisions a world where anyone can create thousands of tokens to be used in many different ways. To onboard NFTs to the masses, we need tools that help achieve mass minting in an efficient and user-friendly way.

Background. One of our first real-world use cases was ticketing at crypto conferences. This year, we did ticketing for NEARCON and onboarded stores and restaurants in the Lisbon area to mint NFTs backed by real products.

Mintbase recently launched 1M tokens for a partnership with deadmau5 and Portugal. The Man. Our current system allows minting at this scale, but the current user flow can see a lot of improvement.

Challenge Requirements

  • Open-source. Provide a GitHub repository or similar.
  • Uses Mintbase libraries (Mintbase.js), NEAR JS API or NEAR CLI to interact with Mintbase stores (smart contracts)
  • Provide a video demo.
  • Working product. Live app connected to testnet is a bonus.
  • Improves the user experience for creating and managing thousands of tokens.

Considerations

This is an important challenge at Mintbase, but we envision this to be a problem for others in the NEAR ecosystem.

Consider using other tools available in the ecosystem, like Croncat (https://cron.cat/) for scheduling blockchain transactions, for example. 

Resources

Back to top

 

Mintbase

Deadmau5 x Portugal. The Man Spaces. VR ready 3D space for deadmau5 single launch at Mintbase

Summary. Create and mint a 3D model on Mintbase to be used as a template for 3XR.

Background. Mintbase believes the metaverse is the natural technological advancement of the internet.

Earlier this year, Mintbase partnered with 3XR (https://3xr.space), to house all NFTs created at or indexed by Mintbase on 3D/VR spaces.

This challenge will help Mintbase and 3XR experiment on interoperability since the spaces can be used by other apps in the ecosystem, and show creators how their spaces can be used (and valued) by being used to create potentially hundreds or thousands of VR spaces.

Challenge Requirements

  • Low poly 3D model
  • Export model as GLB (glTF binary)
  • Ready for VR
  • A space for music. Impress us with creativity.
  • Deadmau5 and Portugal. The Man props are a bonus.

Considerations

3XR is now launching a tool for minting custom galleries using Mintbase technology and user-created spaces. To celebrate the 1M token deadmau5 and Portugal. The Man launch at Mintbase, we want artists to take a stab at creating a 3D space to be used as a template.

Resources

Back to top

 

OINDAO

A card or strategy game development on NEAR

Summary. A card or strategy game development on NEAR that has a high level of playability, and a complete set of game mechanics.

The game will include the following elements and components:

Game mechanics design. The game type is limited to card or turn-based strategy games. Key assessment criteria include:

    1. Playability and creativity
      1. The completeness of game mechanics design
      2. Game incentives design e.g., PvE models will need to assess the UX with in-game objects, PvP models will need to assess players’ UX with other players
    2. Game balance
      1. The game’s algorithmic model must ensure a balance is present to create a positive gaming experience, the balance includes but is not limited to NFT scarcity, difficulty, probability, and strength
    3. Economic model
      1. The game must integrate the nUSDO as one of the in-game currencies [token contract address to be provided]

Game art design. There is no limitation to the game art style, which can be pixel art, cartoon, or realistic, requirements include:

  1. Smooth graphics
  2. Consistent art style throughout in-game settings
  3. Cohesive music and sound effects

Marketplace integration. The game is required to facilitate NFT transactions through a marketplace, key requirements include:

  1. NFTs must follow the NFT protocol standard NEP171 on NEAR
  2. Paras can be used as the trading platform to trade NFTs

Submission requirements

  • Must be a NEAR-based game written in Rust
  • Open source code via Github
  • A design doc that shows your core algorithm
  • Deployed on testnet

Judging criteria

  • Completeness of the game mechanics in accordance to the Description
  • Code quality
  • Defensibility against potential security breaches
  • Robustness against bots or plug-ins that result in unfair in-game experience

Resources

Back to top

 

Ref Finance

Auto-compounding

Summary. Auto-compounding is the action of automatically 'reinvesting' liquidity incentives (farming rewards or yield farming) into the same or different farm(s).

The feature is now well-known within the AMM ecosystem (cf The AMM Milky Way). PancakeSwap, for example, has a feature called Auto CAKE.

Auto-compounding can also become complex, offering different strategies and adding an additional layer of risks, thus explaining why some dedicated tools, like Yield Yak, have been recently emerging in the market. Beefy Finance and Auto Farm are also well-known within the ecosystem.

Challenge description

In this challenge, you would need to create a demo to prove that your algorithm can manage / execute an end-to-end auto-compounding strategy on Ref Finance.

For example, today the Ref Farming component [6] supports liquidity incentives for a dozen pairs / pools (also called 'seed' at the contract level).

Looking at AURORA <> NEAR, for example, the farm gives dual rewards: AURORA and REF. A strategy could be to swap your AURORA rewards for NEAR, then take advantage of the REF <> NEAR farm. A more detailed process would be:

  1. Claim your AURORA and REF rewards
  2. Withdraw your rewards (from Ref to NEAR wallet)
  3. Deposit your rewards (from NEAR wallet to Ref)
  4. Swap AURORA for NEAR to have REF and NEAR in equal proportion (cf REF <> NEAR pool rate)
  5. Add liquidity to REF <> NEAR pool
  6. Stake your LP tokens (shares) into the farm

As for the action 1, it can be done on a daily basis, for example. The bounty hacker can imagine different components in the strategy, such as the best performing farm to 'reinvest' rewards, or even a multi-farm auto-compounding strategy. Another important feature could be a ROI or PnL tracker, to understand how 'good' the auto-compounding strategy is performing compared to a non-compounding (AS IS) strategy.

Many actions may require scheduled smart contract calls. The bounty hacker is encouraged to use CronCat's solution [7], a scheduler for NEAR blockchain transactions.

Challenge Requirements

  • Skills: JavaScripts, NEAR JS API
  • Open source code
  • A design doc to show your core algorithm
  • Demo deployed on testnet or mainnet

Judging Criteria

  • Correctness of algorithm
  • Simplicity / Elegance of the solution
  • One winner gets all rewards

Resources

References

  1. https://twitter.com/pironidi/status/1462435625383219200?s=20
  2. https://docs.pancakeswap.finance/products/syrup-pool/auto-compounding
  3. https://yieldyak.com/farms
  4. https://www.beefy.finance/
  5. https://autofarm.network/
  6. https://app.ref.finance/farms
  7. https://cron.cat/

Back to top

 

Ref Finance

Zap Swap

Summary. Providing liquidity involves adding two tokens in equal proportion to the ratio of the corresponding pool. If you have already both tokens, the process is quite simple. If you don't, the process often involves swapping one token for another. Then repeating the same process for the other token. For example, let's assume that you have 100 DAI and want to provide liquidity into the REF <> NEAR pool. You would do the following actions:

  1. Swap 50 DAI for REF
  2. Swap 50 DAI for NEAR
  3. Add liquidity with REF and NEAR to the REF <> NEAR pool

A Zap Swap will be directly a Swap from 100 DAI to the corresponding REF <> NEAR LP tokens. A similar feature can be studied and analysed on Trader Joe.

A Zap Swap can be very useful, facilitating the user experience by having access / exposure to any pools with his / her principal.

Challenge description

In this challenge, you would need to create a demo to prove that your solution can manage / execute a Zap Swap. In other words, one or multipe transactions that contain(s) the following actions:

  1. Swap token A for token B
  2. Swap token A for token C
  3. Add liquidity of token B and C in B <> C pool

To keep it simple, you can consider NEAR as token A (token-in) for the solution, NEAR being the 'quote' token for most pairs in Ref Finance.

As a bonus, and with the StableSwap feature coming very soon, we would pay attention to the fact that the solution can scale or be configured to add another swap action to the whole process:

  1. Swap token S for token A
  2. Swap token A for token B
  3. Swap token A for token C
  4. Add liquidity of token B and C in B <> C pool

S being a stablecoin and A being NEAR in our example.

Submission Requirements

  • Skills: JavaScripts, NEAR JS API
  • Open source code
  • A design doc to show your core algorithm
  • Demo deployed on testnet or mainnet

Judging Criteria

  • Correctness of algorithm
  • Simplicity / Elegance of the solution
  • One winner gets all rewards

Resources

References

  1. https://traderjoexyz.com/#/zap

Back to top

 

Ref Finance

Account History (with The Graph)

Summary. Giving to our users the ability to access their Account History is essential. Not only the Account View offers a legible audit trail of the user transactions, but also provides elements of reporting for tax purposes, for example. How much did I buy? When? What's the gain I have made on this trade? Etc.

Today, the Account View is extremely minimal, displaying recent activities, such as Deposit, Swap, and Withdraw along with the time of the transaction.

Challenge description

In this challenge, you would need to create a demo to prove that your solution can display, in a well-organised fashion, any user's recent activities with both Ref Exchange and Ref Farming components of the AMM.

Without logging in accounts with NEAR wallet, users can enter any NEAR Account ID to check public information of that account in Ref.

The bounty hacker MUST use the Graph on NEAR to query relevant data.

The User Interface, Experience and Design will be considered but are not key criteria.

Submission Requirements

  • Skills: JavaScripts, The Graph on NEAR, NEAR JS API
  • Open source code
  • A design doc to show your core solution
  • Demo deployed on testnet or mainnet

Judging Criteria

  • Data accuracy
  • Loading speed
  • Simplicity / Elegance of the solution
  • UI
  • One winner gets all rewards

Resources

References

  1. https://app.ref.finance/account
  2. https://github.com/ref-finance/ref-contracts/tree/main/ref-exchange
  3. https://github.com/ref-finance/ref-contracts/tree/main/ref-farming
  4. https://thegraph.com/docs/supported-networks/near

Back to top

 

Spin

Create an exchange trading statistics dashboard

Summary. The exchange statistics dashboard usually aggregates the most important information about the exchange metrics, including information about the trading volume, number of users, number of trades, etc. Create an exchange statistics dashboard based on the functionality of the Spin spot exchange on testnet. It should be an open-source project with code uploaded to GitHub.

Details. The dashboard should consist of charts that show:

  • trading volume
  • number of users
  • number of trades
  • charts with the breakdown of volumes by trading pairs
  • other information useful for traders and investors

Background. Charts, diagrams and other information about the trading activity is very useful for traders and investors, who want to evaluate the protocol metrics, development and user acquisition progress and general information about traders behavior.  

Objectives. You need to build an informative dashboard with comprehensive information about trading activity on the Spin DEX. The main criteria are the clear design of the dashboard and the list of metrics presented.

Considerations. Brainstorm and shortlist the trading metrics and charts that should be really useful for our users!

Resources. Spin Finance GitHub, site and app (will be available later)

Back to top

 

Spin

Develop API libraries for Spin

Summary. Develop a library that allows interaction with the contract directly to facilitate integrations and tests. Libraries can be written in Python, Node-js and other languages.

Details. Please use Python and Javascript programming languages. 

Libraries can almost completely duplicate the functions of the main contract. For instance:

  • Download list of available markets
  • Pull information about the order book, such as sizes and prices of bids and asks
  • Add, modify and cancel bid and ask orders
  • Pull the list of all active, filled and cancelled orders
  • Other functions

All submissions should be publicly available on GitHub. 

Background. High-quality API is necessary to attract professional traders such as market makers and algorithmic traders to the platform, which in turn leads to the growth of the trading activity on it. 

Objectives. Successfully develop libraries with working code that is compatible with the Spin contract.

Considerations. Brainstorm specific functions that could be helpful for different types of traders, i.e. market makers, algorithmic traders or arb traders.

Resources. Spin Finance GitHub, website and trading app

Back to top

 

Spin

Matching engine black-box testing

Summary. Thinking of the matching engine as a black box, develop and unit test a client bot that massively floods the matching engine with random buy and sell orders.

Details. The expected outcome of the simulated attack is:

  1. A denial of service when Matching Engine stops working due to internal logical contradictions or bugs.
  2. The result of the investigation of crash cases: full log of test load, matching engine outcomes, and other reproducible artefacts.
  3. By simulating the logical operation of the matching engine and edge cases, run fuzzy/black-box testing to exploit potential flaws in the architectural design and operation of the matching engine.

Background. This test solves a wide range of problems, from architectural problems to coding errors, that are part of the broader domain of formal validation and proof. These problems affect the business side of any project because even one mistake can lead to theft of money and the collapse of the business model.

Objectives. We have provided 3 levels of difficulty for the implementation of this challenge:

  • Level 1 – Refusal to work normally: refusal to close previously closed and newly opened orders, without obsolescence of existing orders, etc.
  • Level 2 – Report any test artefacts that can be used to reproduce crashes and provide some details and thoughts on the issue, if any.
  • Level 3 – To actively exploit suitable engine flaws, all artefacts must be present to reproduce all kinds of unexpected behaviour.

Considerations. It would be great to:

  • Develop (or use any available on the market) fuzzy/black-box testing framework.
  • Develop a matching engine API client, and on availability of matching engine source code, develop a continuous integration infrastructure: Docker images, associated infrastructure, compute instances, storage, and more.

Resources. The black box test techniques are described here: https://en.wikipedia.org/wiki/Black-box_testing. The most promising of them in terms of winning the award are https://www.guru99.com/equivalence-partitioning-boundary-value-analysis.html and https://en.wikipedia.org/wiki/All-pairs_testing 

Back to top

 

Spin

Any valuable contribution to improving the Spin DEX

Summary. If you want to build a product not covered by any of our other challenges or improve the code of Spin Finance, you can tackle this task within this challenge. Create or improve anything that will be useful for Spin and our community! This could be a Telegram or Discord bot, improvements to the GitHub code, suggestions for new features - whatever!

Browse all Spin resources and suggest your ideas on how to make it better for our users. Participants can get support from the Spin team both in choosing a product to develop and in the process of working on it.

Background. We want to give the hackathon participants freedom of choice. This is the challenge for those who enjoy creating and optimizing on their own.

Objectives. Free form.

  • Product innovation
  • Utility for Spin and the community
  • Quality of work

Considerations
The crypto community was built with the idea of decentralization and creativity. Any new, even crazy ideas can change the rules of the game. So let's build it together!

Resources. Spin Finance GitHub, site and app (will be available later)

Back to top

 

Akash NEAR Protocol Challenge

Summary. This challenge is to set up a NEAR Validator node on Akash. Providing reproducible deployment files for anyone to us via the awesome Akash repo. This node guide should be relevant to both validators and blockchain nodes that dApps need to access the blockchain.

Objectives

  • Run NEAR chain node and validator node on the Akash decentralized cloud
  • Containerize instances and initialize them on the network

How to connect with Akash on this Challenge

Resources

Deliverables in order of Strategic Value (highest value first)

  • All deployment files submitted to the awesome Akash repo via pull request
  • Readme with instructions to maintain the submission submitted to the awesome Akash repo via pull request
  • Demo video
  • Bonus if you can do both the validator and chain node in a single set of deployment files

Back to top

 

PARAS

Create decentralized apps on top of the NEAR protocol using NFT NEP-171 standard! 

Background. The NFT ecosystem in the NEAR protocol is growing and we want you to be part of it. The scalability of NEAR blockchain in terms of transactions speed and low transaction fee allow developers to do more with the blockchain. 

Objectives
Create a working dapp on top of the NEAR protocol using NFT NEP-171 standard, share the demo link and the GitHub page. 

Ideas
These are some of the ideas that we like to see in this challenge. 

  1. NFT games like Tamagotchi, Animal Kaiser 
  2. NFT Gacha System 
  3. NFT Lending 
  4. NFT Fractionalization 
  5. NFT Trading (e.g NFT + Crypto swap, Wonder Trade) 

Considerations

  1. Be innovative and creative 
  2. Make sure to follow the NEP-171 standards 
  3. Integrate your NFTs with Paras marketplace (Bonus) 

Resources & Links

  1. NEAR NFT standards: https://nomicon.io/Standards/NonFungibleToken/Core.html
  2. NFT implementation: https://github.com/near-examples/NFT
  3. Sample apps: https://github.com/near-apps/
  4. Paras documentation: https://docs.paras.id/
  5. Paras API reference: https://parashq.github.io/

Back to top

 

Aurora

Gaming

Create any game on Aurora

We will reward the best game and the best game that uses the random number feature.

Randomness is not an easy thing for Ethereum, however we have it on Aurora.

To see more info about how random is build in Aurora, see this PR: https://github.com/aurora-is-near/aurora-engine/pull/368

Resources:

Back to top

 

Aurora

Build an NFT marketplace

Build an NFT marketplace (can be a copy of any existing marketplace)

  • List of NFTs owned by a user
  • List of NFTs available to buy
  • Auction models for NFT (optional)

Create a working NFT marketplace dApp, which enables users to trade NFTs on Aurora. The factory smart contract can create a user defined (configurable) NFT contract. Content creators are allowed to receive (ETH, WETH, or any Stable coin) as reward. Additionally allow creators to auction their artwork on the marketplace with the two models (timed and unlimited auction).

Examples:

 

Example task (some info can be copied from here if needed): 

Challenge Description https://gitcoin.co/issue/reef-defi/reef-finance-bounties/2/100026839

Reef chain offers very low transaction fees so it can offer more complex contract functionality and NFT creation will be more accessible to everyone. We are looking for an NFT marketplace dApp with functionality like OpenSea or Rarible. Allow content creators to configure smart contracts for the collection of royalties on their artwork in the future.

Winners:

Another example:

Resources:

Back to top

 

Aurora

Oracles

Build an app using one of the oracles that are already live on Aurora:

  1. https://www.diadata.org/
  2. https://www.fluxprotocol.org/

Resources:

Back to top

 

Catalytics

The Catalytics Challenge

Summary. Catalyst is a dao-based customizable community building, governance, and coordination platform that is enabling the self-organizing and self-governing communities of the future.

We could use your help:
Catalyst is new and is in a soft launch phase where we are making tweaks before making it known that it is available for use.  We’d really like to provide community creators and contributors using Catalyst with some nice looking and easily understood analytics to help provide insights on community growth, member engagement, activity and so on.  These things are important as community owners look to nurture and grow their communities and individuals look for active communities to join that match their interests.

We have the beginnings of an analytics component built into Catalyst, but it’s rough and needs some love and attention.  We believe the recent integration between NEAR and The Graph is going to facilitate our vision by enabling more advanced queries.

Objectives

  • Work with project mentors to define an initial set of metrics (e.g. member growth over time, community activity, value of assets under management, community age, etc…)
  • Work with project mentors to define the data models that will feed that analysis so existing contracts can be upgraded to make it available in a manner The Graph can index.
  • Build the subgraphs (The Graph) that will enable data extraction from the NEAR contracts to populate the data models needed for the analytics.
  • Create appealing and interactive visualizations that represent the analytics. Current work has been using D3 and ReactJs to visualize data available.
  • Build an appealing community dashboard that incorporates the visualizations and can be plugged into the Catalyst platform (React component(s)).
  • Bonus:  build api to make the data used in the visualizations available outside of Catalyst for easy ingestion in other analytics platforms and solutions

Considerations

  • Catalyst is built on NEAR (AssemblyScript contracts) and is heavily integrated with Ceramic Network (IDX) and the very beginnings of The Graph.  The frontend is React.  Familiarity in that tooling would be beneficial but not essential.
  • Only interested in open-source analytics integrations - D3 for instance.
  • Your code needs to be open source and freely available for use in the Catalyst project - customizable at will.

 

Resources

Back to top

 

Aurora

NEAR <> Aurora Integration

Create an application where contracts in NEAR and contracts in Aurora communicate between each other. Mentorship provided by Marcelo Fornet

Examples

  • NEAR Native Token on Aurora (See more details on its own task)
  • Oracle that allows fetching information from NEAR in Aurora (or vice versa).
  • Off-chain tools that allow integration, building and testing of this type of apps easier.

Resources

Back to top

 

Aurora

ERC20-Factory

Create an ERC-20 factory to deploy any ERC-20 token on Aurora. UI for creating the token. This should allow setting all the metadata, name,symbol,decimals. Also total supply and initial owner of the total supply with upgradeability support.

Something similar can be created for NFT.

Marcelo Fornet

Example on NEAR: https://tkn.farm

Example on Ethereum: http://thetokenfactory.com/#/factory

Resources

Back to top

 

Aurora

INFRASTRUCTURE

Create native NEAR support inside Aurora. Description of the task is on the issue. Mentorship provided by Marcelo Fornet.

https://github.com/aurora-is-near/rainbow-bridge/discussions/642

Resources

Back to top

 

NEAR Foundation

Calling all Liberal Artists

Produce a valuable artifact of your choosing to help introduce the world to the future of the web.

Background. While some of the brightest minds of our time have gravitated towards the blockchain industry, we have precious few students with a background in the humanities.

We're sorely missing the input of philosophers and historians, artists and illustrators, people who don't just think outside the box, they live outside the box.

If this challenge resonates with you, come help us see the future today.

Objectives

  1. create an original or derivative work that communicates a valuable message about the future of the web -- this can include a paper, a painting, a song or soliloquy.
  2. capture your work using the most effective medium

Considerations

  • your output does not have to be technical in any way, in fact it may be best to avoid grounding your work in any practical interpretation of existing applications -- we don't need faster horses, we need an inspiring vision of the 1967 Chevy Corvette
  • if your work is derivative, please give credit to the creator

Resources

Back to top

 

NEAR Foundation

Bootcamp Capstone on Web3

Integrate your coding bootcamp capstone project with the NEAR platform in some meaningful way.

Background. According to an Indeed survey of more than 1,000 technical recruiters and HR managers, 72% of employers believe coding bootcamp graduates are just as prepared for work as computer science degree-holders. The demand for computer science professionals currently exceeds the number of workers in the field, making bootcamps an ideal way to quickly join the workforce. (taken from this article)

Coding bootcamps provide short-term, intensive training focused on building job-ready skills. Enrollees explore coding fundamentals, learn industry-standard tools and software, and complete multifaceted coding tasks and projects. Coding bootcamps attract beginners interested in breaking into tech and experienced professionals looking to enhance their skills.

Almost all coding bootcamps include some kind of student portfolio development work, culminating in a final, or capstone, project.

Objectives

  1. Use NEAR for user authentication in your app
  2. Call existing view or change methods on contracts available in the ecosystem or write your own smart contracts to capture valuable information on the blockchain

Considerations

  • The capstone project does not have to be your own -- if you use a project created by other students, please be sure to acknowledge and credit their work by forking a public repository and then building your derivative work.
  • When reading from the blockchain, you don't need a signed transaction so the entire API is available to you for reading (including calling smart contract functions known as view functions)
  • When writing to the blockchain you MUST include a signed transaction

Resources

Back to top

 

NEAR Foundation

Airtable Is the New Excel

Build something by connecting Airtable with NEAR in some meaningful way.

Background. Today (March 2021) more than 250,000 companies use Airtable. The number of paying enterprise customers has grown nearly 350% over the last year. Airtable represents a fundamental shift in how software can be used and created.Its software can penetrate an infinite number of use cases across the modern workforce.  (taken from this article)

Airtable’s ability, in a customized way, to connect everything and everyone in an organization is transformative. It’s an incredibly powerful and empowering collaboration platform. 

Customers have hundreds of projects being shared across production, post-production, marketing, finance—every facet of the business. Airtable allows them to communicate and share in a way that they've never been able to do before.

Objectives

  1. Make a call to the NEAR network and do something useful.
    • You can read some data from the network using the basic fetch API
    • or you can write something by using a custom server-side component to sign transactions (since you can't sign transactions in Airtable)
  2. Update Airtable with data returned from the NEAR network
  3. Consider building an Airtable Interface for your dApp

Considerations

  • when reading from the blockchain, you don't need a signed transaction so the entire API is available to you for reading (including calling smart contract functions known as view functions)
  • when writing to the blockchain you MUST include a signed transaction

Resources

Resources

Back to top

 

NEAR Foundation

Glide Makes All Things Mobile

Build something by connecting Glide with NEAR in some meaningful way.

Background. Build better apps than your developer can. Whether you're a beginner or an IT pro, you can build an amazing Glide App in minutes. Building internal apps can be a slow process but Glide makes it easy to build and deploy functional internal apps quickly -- without knowing how to code.

You can also use your Glide app to test minimum viable products (MVP) internally and with beta users. This will allow you not only to get immediate reactions on your MVP, but allow you to make changes and updates quickly according to feedback from users.

Objectives

  1. create a demo using the Glide platform and any available integrations

Considerations

  • Gide may not have the ability to sign and send transactions to the NEAR platform but you can always build your own server-side components to your submission

Resources

 Back to top

 

HAPI.one

Staking

Develop staking functionality (web+SC)

  1. Stake funds to a NEAR/AURORA validator using near-web3-provider.
  2. Display staked amount. 
  3. Ability to choose the currency

Additional tasks

  1. Add ability to withdraw stake.
  2. Allow any account to stake funds to your staking account. 
  3. Assign different tier (configurable) via smart contract based on staked amount (configurable):
    • Tier 1: <= X AURORA (equivalent)
    • Tier 2: <= Y AURORA (equivalent)
    • ...

Environment

Expected Success Outcomes

  • Completed Logic model
  • Code completion
  • UI/UX convenience
  • Chain interoperability
  • Next steps (how to scale)

Back to top

 

HAPI.one

Lottery functionality

Develop a lottery functionality (SC)

  • Participants join the lottery. N lottery tickets are distributed daily. When the lottery round ends, anyone can call a function to distribute lottery rewards to N pseudo-randomly selected participants.
  • Lottery ticket is a non-transferrable NFT.
  • Blockchain lottery: use pseudo random function to generate random seed.

Environment

Expected Successful Outcomes

  • Completed Logic model
  • Code completion
  • UI/UX convenience
  • Chain interoperability
  • Next steps (how to scale)

Back to top

 

HAPI.one

Merkle tree-based solution

In various distributed and peer-to-peer systems data validation is very important. This is because the same data exists in multiple locations. If a piece of data changes in one place, it is important that the data changes everywhere. Data validation is used to make sure the data is the same everywhere.

Challenge Description. Develop a Merkel tree-based solution for storing and processing transactions on the NEAR blockchain

Environment

Expected Successful Outcomes

  • Completed Logic model
  • Code completion
  • Reliability and safety
  • Chain interoperability
  • Next steps (how to scale)

Back to top

 

HAPI.on

Claiming system

Develop a claiming system for near-based tokens from a smart contract. The system should take into account personal allocations, date/time of the claiming start/finish, duration of claiming. With minimal costs.

Challenge Description. Develop a claiming system for the NEAR blockchain

Environment

Expected Successful Outcomes

  • Completed Logic model
  • Code completion
  • Reliability and safety
  • Chain interoperability
  • Next steps (how to scale)

Back to top

 

HAPI.one

Exchange pool model

Develop an exchange pool model (SC)

  • Pool creator sets:
    • Sell token address
    • Buy token address
    • Buy token raise amount
    • Pool exchange start time
    • Pool exchange end time
  • Sender swaps sell the token into a buy token at a fixed price, set by a pool contract creator. Swaps are allowed only when the pool is active.
  • Senders can withdraw bought tokens after pool exchange ends.
  • Pool creators can withdraw collected sell tokens when pool duration ends.

Environment

Expected Successful Outcomes

  • Completed Logic model
  • Code completion
  • Reliability and safety
  • Chain interoperability
  • Next steps (how to scale)

Back to top