0. Proposer Info
- Email :
lethe@asphodel.io - Proposer’s Project Name :
Yominet/Kamigotchi - Proposer’s Project URL :
Kamigotchi.io - Proposer’s X (Twitter) Account :
@realizumikonata
1. TL;DR
This proposal requests the whitelisting of Yominet to Initia’s VIP (Vested Interest Program).
2. Background
2-1 About the Project
- Protocol Name :
Yominet / Kamigotchi - Protocol Blurb:
A fully onchain world living on top of Initia. Home to the Kamigotchi - in practice, a fully onchain and entirely decentralized MMORPG. - Protocol Type :
Other - Docs :
docs.kamigotchi.io - Audits :
N/A, audits done privately.
3. Rationale & Impact
Motivation and Benefit to the Interwoven Economy
Kamigotchi was designed from the ground up to be a machine for creating onchain engagement. This is the most sophisticated fully onchain game ever built, requiring 3 years of development time. Kamigotchi is ideally situated to serve as a “mascot protocol” for Initia, bring in a large volume of engaged users, and create value for the ecosystem as a whole.
VIP Scoring Criteria (Details)
VIP Tickets are harvested ingame according to the exact same logic used for MUSU, Kamigotchi’s ingame currency. Players compete to harvest these from VIP Nodes ingame - once earned, the tickets can be burnt ingame to turn them into VIP Points at a 1:1 ratio. This essentially weaves harvesting for VIP Points into Kamigotchi’s core gameplay. Players are able to PVP one another to claim these tickets.
VIP Distribution Calculations
Each epoch, players who earned VIP Points in game by burning VIP Tickets will receive an allotment of Yominet’s VIP rewards for that epoch. This reward will be proportional to the VIP Points earned by all players. So for a given epoch, a player’s allotment of VIP rewards is as follows:
yp=Y∗(tp/T)
where:
| Symbol | Description | |
|---|---|---|
| yp | VIP Rewards for player p | |
| Y | Yominet’s VIP Rewards | |
| tp | VIP Points earned by player p | |
| T | VIP Points earned by all players |
4. Proposal Details
| Field | Value | Description |
|---|---|---|
| Operator Address | init13sdgw30fs3czw3p03wwfqu82d4khvd4x5ezeyr |
The address eligible to claim a portion of the VIP rewards allocated to the rollup team as commission. This address does not need to be a system key (like admin or bridge executor). |
| Bridge ID | 11 |
An identifier automatically generated during the setup of the bridge between the Rollup and Initia. |
| Bridge Address | The L1 address where tokens are locked when bridging from L1 to L2. This address is auto-generated during bridge setup. | |
| Scoring Contract Address | init1rkzkxwt4nsy3amu9hxx3m6whq4z6ps6ddfkqww |
The contract deployed on the rollup that assigns VIP scores to users. These scores are snapshotted on L1 and used to build a Merkle tree for VIP reward distribution. |
| Operator Commission Max Rate | 0.2 |
The maximum commission rate the rollup can configure. |
| Operator Commission Max Change | 0.2 |
The maximum allowed change in the commission rate per update. For example, if OCR is 0.3 and OCMC is 0.2, OCR can only be adjusted between 0.1 and 0.5. |
| Operator Commission Rate | 0 |
The actual commission rate. If 100 INIT is distributed and OCR is 0.2, the rollup team receives 20 INIT. |
| VM | EVM | The VM type of the rollup is using. |
Governance Votes
- YES – You support whitelisting this rollup on VIP with the parameters provided.
- NO – You do not support adding this rollup on VIP.
- NO WITH VETO – You believe this proposal is harmful, spam, or violates governance principles.
- ABSTAIN – You choose not to vote for or against but wish your vote to count toward quorum.