inkonchain / inkonchain/docs

Docs: Add guide for building onchain games on Ink (Phaser 3 + wagmi)

Open
#613 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
MDX
Stars
36.5k
Forks
481
Avg merge
6h 16m
Merged PRs (30d)
12

Description

🎮 Feature Request: Game Development Guide for Ink

Summary

As the Ink ecosystem grows, there's a significant opportunity to attract game developers building onchain games. Currently, the documentation lacks any guidance for developers who want to combine traditional game frameworks (like Phaser 3) with Ink smart contracts and wallet interactions.

Proposed Section

Add a new documentation page or guide under the Developers section:

Title: Building Onchain Games on Ink

Suggested Content
  1. Overview — Why Ink is great for onchain games (low fees, fast finality, EVM-compatible)
  2. Stack recommendation:
    • Phaser 3 — industry-standard HTML5 game framework
    • wagmi + viem — wallet connection & contract interaction
    • OnchainKit — UI components for wallet UX
  3. Basic integration example — connecting a Phaser 3 game scene to a smart contract (e.g., storing scores onchain, minting NFTs on game events)
  4. Ink-specific tips — RPC endpoint, chain ID (57073), recommended wallets
  5. Example project reference — link to community game projects built on Ink/Base
Why This Matters
  • 🎯 Onchain games are one of the fastest-growing verticals in Web3
  • 🔗 Ink's low fees make microtransactions (in-game actions) economically viable
  • 👨‍💻 This guide would help JS developers transition into Web3 game dev using familiar tools
  • 🌍 Expands Ink developer community beyond DeFi
Additional Context

I'm currently building Base Invaders — a Phaser 3 game integrated with Base/Ink blockchain. Happy to contribute a draft of this guide or provide a working code example as a reference implementation.


Would love to contribute this section if the team is open to it! 🦑

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the Developers section and reviewing its existing guide structure. Use the proposed Phaser 3, wagmi, viem, and OnchainKit topics as the scope, including Ink's RPC endpoint, chain ID 57073, wallet guidance, and a game-to-contract example; done means a complete guide with an example-project reference.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
blockchain, documentation, game-dev
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.