@ndcplug.near [Posted on DevHub](/devgovgigs.near/widget/Post?id=1829) ## Solution: 📦 Request for Account Abstraction NEARCON Bounty ###### Requested amount: 3000 USDT ###### Requested sponsor: @neardevgov.near # Overview The following is a request for NEARDevHub to support a** $3,000 USD equivalent bounty for NEARCON for an “Account Abstraction” bounty track**, and a personal offer, for me to provide mentor support on the ground for builders & developer retention and engagement post hackathon (**[for free](https://near.org/s/p?a=nearhacks.near&b=103875504)**) # Why? * Native account abstraction is one of the biggest selling points for NEAR and has been underutilized + undermarketed * Recent Innovations with Account Model: Now with FastAuth, NEP366, mintbase wallet, Keypom with Trial accounts, Namesky we want to showcase the limits of onboarding & near’s account model * Many applications are being hindered by user onboarding as a friction point, and Web3 onboarding still remains one of the biggest pain points in web * Bottleneck in users in the NEAR ecosystem from Web2.5 users. Need to convert these users to the more “native” ecosystem, through progressive onboarding. * Losing voice of share to other chains with Account Abstraction # My Main Objectives * Get at least 7 submissions and 3 quality use cases * Make sure developers are retained into DevHub and other [builder verticals](http://nearbuilders.com). Pipeline projects into product, skilled devs into existing projects. Check [Joe’s Post on Dev Retention](https://near.social/#/devgovgigs.near/widget/gigs-board.pages.Post?id=1818) * Continue developer retention through relevant hackathons like January’s [Account Abstraction hackathon](abstracting.org) * Have a set of unique PoCs by the end on NEARCon to showcase USP of NEAR * Raise excitement and voice of share about upcoming remote accounts and account extensions * Showcase existing solutions and pipeline developer feedback to respective engineering and dev rel teams # Prizes ## General Prize The following bounty is for the team that best leverages NEAR’s account model, to ease onboarding. **This prize would be awarded to the best 3 overall projects** ### Prize Distribution * 1st Place: $1500 * 2nd Place: $1000 * 3rd Place: $500 The following are categories for the bounty that qualify * **Keypom:** use Keypom SDK, contracts, or fork Keypom to build new onboarding use cases. * **Metatransactions**: leverage the ability for a third party to pay transaction fees on behalf on account * **Abstraction on BOS**: build a BOS component, tooling, or gateway that leverages account abstraction * **Cross-chain / Remote accounts:** build a proof of concept that leverages NEAR’s account model to initiate transaction from another blockchain or Web2 service through a NEAR account ## Keypom Keypom is an account abstraction protocol on NEAR that leverages linkdrops that allow users with or without an account to interact with a series of accounts. Keypom has a contract, sdk, and web app you can build on top of. Here are some use cases we are looking to have built out * Trial Accounts * User Args * Integration into dApps (ex; one click trial account), DAOs, and Games * BOS Component (Ex; Analytics for Drops, No Code Drop Generators) ## Meta Transactions In-protocol meta transactions allow for third-party accounts to initiate and pay transaction fees on behalf of the account. Some ideas around meta transactions are to * Build implementation of new sign on flow (Ex; Mintbase Wallet, Fast Auth, Social Recovery) * Build new implementations of Relayers * Integrate into existing application * Create a relayer for swaps of fungible tokens ## Abstraction on BOS Build a [BOS](docs.near.org/bos) component that leverage account abstraction. Some ideas around BOS components include * Keypom drop generators on BOS * A build that leverages account abstraction to post or interact with social DB # Ideas & Resources For more ideas check out (living document) [abstracting.org/ideas ](abstracting.org/ideas) For account abstraction resources (living document) [abstracting.org/resources ](abstracting.org/resources) # Sponsorship Request **DevHub: I am requesting $3000 sponsorship to go entirely towards bounties for NEARCon** _Notes: I am not asking for a Mentor stipend or any compensation for in person facilitation of this bounty and all rewards go to winners for this. I just want to see cool use cases for account abstraction. Also, I have been in talks with @yarotska.near and finalizing an Abstraction Hack ([abstracting.org](abstracting.org)) in January._ Services include * Technical support and on the ground support for teams * Scoping feasibility with builders * Judging (if you need me to) # Evaluation criteria The following is evaluation criterion for judges to consider for submissions who optin to the Abstraction Bounty * **Code complexity & cleanliness:** Does the project’s component design patterns showcase a level of maturity? Are children components easy to run? Does their code run efficiently? Does their project showcase a level of technical complexity? * **Usefulness in NEAR ecosystem & likelihood for communities to fork:** Is this something that other projects could leverage, build on top of. * **Likelihood to continue project into product:** Is this a one time hackathon project or will they continue this into a public good the ecosystem needs? * **Originality of idea:** Is this a novel idea? Is this a use case that would bring external user adoption. If this is based on an idea suggested by an ideas list, how well did they execute the desired ideas.Does the project actually solve a pain point? * **Product / UX:** Does the project have compelling UX? Would a user know how to interact with it without a demo / explanation? Is this integrated to a larger project? * **Innovation**: Does this idea push the limits of NEAR?