SECTION 1: APPLICANT INFORMATION
Provide personal or organisational details, including applicant name, contact information, and any associated organisation. This information ensures proper identification and communication throughout the grant process.
Applicant Name: Yaniv Baruch
Project Name: Playnance
Project Description:
Team Members and Roles: Our team consists of 31 individuals, primarily divided between technology and marketing, with a focus on combining innovative technical solutions with effective marketing strategies.
Here is the list of core team members:
- Pini Peter, Founder & CEO
- Roman Levi, Chief Technical Officer
- Yaniv Baruch, COO
- Avi Hatami, CRO
- Nikolay Schebelev, Chief data analyst
- Dmitry Kobetz, Head of DevOps
Project Links:
- Website: https://www.playnance.com/
- Twitter: @Playnancetech
- Telegram: Telegram: Contact @asanad222
Contact Information
Point of Contact : Yaniv Baruch
Point of Contact’s TG handle: @themistergreen
Email: yb@playnance.com
Do you acknowledge that your team will be subject to a KYC requirement?: Yes
SECTION 2a: Team and Product Information
Provide details on your team’s past and current experience. Any details relating to past projects, recent achievements and any past experience utilizing incentives. Additionally, please provide further details on the state of your product, audience segments, and how you expect incentives to impact the product’s long-term growth and sustainability.
Team experience:
Playnance is an innovative Web3 iGaming studio. We act at the conflux of GameFi, iGaming, and DeFi to create new, engaging, and secure experiences for players and partners.
Playnance LTD was founded in 2020. The headquarters is in Tel-Aviv, Israel. Today, there is also a MENA head office in Dubai, UAE.
Since then we have grown to the biggest game on Polygon PoS with over 14M transactions to date and 9% market share of all Polygon PoS transactions.
Is your project composable with other projects on Arbitrum? No
Do you have any comparable protocols within the Arbitrum ecosystem or other blockchains? No
How do you measure and think about retention internally? (metrics, target KPIs)
TBD
Do you agree to remove team-controlled wallets from all milestone metrics AND exclude team-controlled wallets from any incentives included in your plan: Yes
Did you utilize a grants consultant or other third party not named as a grantee to draft this proposal? If so, please disclose the details of that arrangement here, including conflicts of interest (Note: this does NOT disqualify an applicant): No
SECTION 2b: PROTOCOL DETAILS
Provide details about the Arbitrum protocol requirements relevant to the grant. This information ensures that the applicant is aligned with the technical specifications and commitments of the grant.
Is the protocol native to Arbitrum?:
No, we are currently live on Polygon and Arbitrum Orbit.
On what other networks is the protocol deployed?:
Currently, the game is live on Polygon.
What date did you deploy on Arbitrum mainnet?:
No deployment to Arbitrum mainnet, but a deployment to Arbitrum Orbit on 1st of March, 2024
Do you have a native token?:
Not yet, we are planning to launch in the next months.
Past Incentivization: What liquidity mining/incentive programs, if any, have you previously run? Please share results and dashboards, as applicable?
We currently run an upvsdown referral program and got over 2K users from our program. You can join the program here: UpVsDown referral program
As part of our launch on Arbitrum Orbit we will be running a similar referral program.
Current Incentivization: How are you currently incentivizing your protocol?
TBD - information about our game token will be subject to further announcements for our L3.
Have you received a grant from the DAO, Foundation, or any Arbitrum ecosystem related program?
No
Protocol Performance:
UpvsDown is currently doing about 9% of all Polygon PoS transactions. We are planning to onboard all these users to Arbitrum Orbit through our own Anytrust L3 settling on Arbitrum One.
Protocol Roadmap:
Protocol Roadmap: [Describe relevant roadmap details for your protocol or relevant products to your grant application. Include tangible milestones over the next 12 months.]
Q1 2024:
• Wallet Beta Release: 500 daily players
• Protocol Closed Beta: first games and players onboarding
• Tokenomics for utility token and stablecoin
Q2 2024:
• Protocol Official Release
• Wallet Release
• New Game Release
• TGE and Token Events
Q3 2024:
• Bridge Release
• Exchange Release
• 2 New Games Releases
Q4 2024:
• Release of open API for gasless blockchain
• Token Ecosystem Releases
• 2 New Games Releases.
Audit History & Security Vendors: Our game was audited by Certik on Polygon PoS.
Security Incidents:
None
SECTION 3: GRANT INFORMATION
Detail the requested grant size, provide an overview of the budget breakdown, specify the funding and contract addresses, and describe any matching funds if relevant.
Requested Grant Size: 3,600,000 ARB
Justification for the size of the grant:
We are #1 game on Polygon in terms of daily transactions (9% of total Polygon transactions) and we will be the #1 game in the Arbitrum ecosystem.
Statistics:
https://dune.com/playnance_team/playnance-daily-turnover
Funding Address: 0x56238a9f3A19F5e4Ac031787eAE4A6Eaf59cfA4a
- Grant Breakdown
Ongoing gaming and onboarding incentives - 80%
Ongoing retention incentives - 10%
Infrastructure for running, operating, and maintaining the Arbitrum Orbit chain - 10%
Funding Address Characteristics:
SECTION 4: GRANT OBJECTIVES, EXECUTION AND MILESTONES
Clearly outline the primary objectives of the program and the Key Performance Indicators (KPIs), execution strategy, and milestones used to measure success. This helps reviewers understand what the program aims to achieve and how progress will be assessed.
Objectives:
- Research & Development: Advance technology and improve platform features.
- Community Building: Foster engagement and interaction among users.
- User Growth: Support initiatives that expand the project’s reach.
Execution Strategy:
- Community Building:
- Organise regular community events, such as AMAs, webinars, and meetups, to facilitate interaction among users.
- Start a community ambassador program to empower passionate users to promote engagement within their networks and locality.
- User Growth:
- Onboarding new partners and affiliates
- Our goal is to bring 10M users to our Arbitrum Orbit L3 per year
Here are some mechanisms to consider within the incentive design:
-
Tiered Reward Structure: Implement a tiered reward affiliates system with 3 tiers. 15% of our players use the affiliate system and our goal is to increase it to 27%.
-
Automated system to onboard new partners: Playnance - Whitelabel Program
We currently have 40 B2B partners and by the end of 2024 we will have 100 B2B partners.
Specify the KPIs that will be used to measure success in achieving the grant objectives and designate a source of truth for governance to use to verify accuracy.
Grant Timeline and Milestones:
How will receiving a grant enable you to foster growth or innovation within the Arbitrum ecosystem?
Receiving a grant would provide significant opportunities to foster growth and innovation within the Arbitrum ecosystem in several ways.
Do you accept the funding of your grant streamed linearly for the duration of your grant proposal, and that the multisig holds the power to halt your stream?
Yes
SECTION 5: Data and Reporting
OpenBlock Labs has developed a comprehensive data and reporting checklist for tracking essential metrics across participating protocols. Teams must adhere to the specifications outlined in the provided link here: [Onboarding Checklist from OBL 27]
Along with this list, please answer the following:
Is your team prepared to comply with OBL’s data requirements for the entire life of the program and three months following and then handoff to the Arbitrum DAO? Are there any special requests/considerations that should be considered?
Yes, we are ready to accommodate and fulfill the necessary data requests.
Does your team agree to provide bi-weekly program updates on the Arbitrum Forum thread that reference your OBL dashboard? Yes
First Offense: *In the event that a project does not provide a bi-weekly update, they will be reminded by an involved party (council, advisor, or program manager). Upon this reminder, the project is given 72 hours to complete the requirement or their funding will be halted.
Second Offense: Discussion with an involved party (advisor, pm, council member) that will lead to understanding if funds should keep flowing or not.
Third Offense: Funding is halted permanently
Does your team agree to provide a final closeout report not later than two weeks from the ending date of your program? This report should include summaries of work completed, final cost structure, whether any funds were returned, and any lessons the grantee feels came out of this grant. Where applicable, be sure to include final estimates of acquisition costs of any users, developers, or assets onboarded to Arbitrum chains. (NOTE: No future grants from this program can be given until a closeout report is provided.) Yes
Does your team acknowledge that failure to comply with any of the above requests can result in the halting of the program’s funding stream?: Yes