MortalCoin: Trading Simulation Fighting Game – Outtrade Your Opponent to Win

live app: https://stage.mortalcoin.app

MortalCoin HyperHack Hackathon Submission

Live link: https://stage.mortalcoin.app/
Game demo video: https://youtu.be/4ZrYxP0vC_w

Alith AI trading bot demo video: https://youtu.be/GtFaSFPcWYc
AI trading bot Repo: GitHub - MortalCoin/mortalcoin_alith_bot: MortalCoin’s AI playing bot makes decisions using the Alith AI Agent.

Contract repo: GitHub - MortalCoin/mortalcoin-evm
Contract on Hyperion: Metis Hyperion Testnet address details for 0xDf8730693833b9e27D5999863feBb3028fcc6927 | Blockscout

Deck draft: https://www.canva.com/design/DAGujqtuAVo/Z4dVLaIKFc1whyVgGmkdJw/edit?utm_content=DAGujqtuAVo&utm_campaign=designshare&utm_medium=link2&utm_source=sharebutton

MortalCoin is a real-time PvP crypto trading game where players battle using simulated trades based on live market data. Think Mortal Kombat meets Hyperliquid, with cryptocurrencies personified as playable fighters.

Each battle simulates a short (60-second, currently) trading session where players choose strategies and try to outtrade their opponents. Both players lock in equal bets before the game starts — the winner takes it all.

The core monetization model is a small operational fee (currently 1%) deducted from the total pot upon payout, handled directly by the game smart contract.

Gameplay explained: Trading Fight – Gamified Crypto Battles Inspired by Hyperliquid and MortalKombat | MortalCoin Docs


What We Built

It’s been an exciting month of non-stop building on the Hyperion Testnet.
Our small but mighty team smashed keyboards and shipped features.

The team members are:

  • @artemii235 Artem, blockchain developer (mainly in Rust) — designed and developed the smart contract, overall technical concept, CLI, and MM tools.

  • @g.ionov George, backend developer (Python) — developed the backend authentication module, relay exchange system, and matchmaking.

  • @tonymorony Tony (me) - developed the frontend (TypeScript, Vite) and the Alith AI playing bot (Python), acted as PM, QA, and UX/UI designer, and was responsible for planning, documentation, and external communications.

Here’s what we accomplished:

1. Brainstormed and Designed the Game Concept

We came up with the idea for an on-chain trading competition game:

2. Designed and Deployed the Game Smart Contract

Repo: GitHub - MortalCoin/mortalcoin-evm
Deployed on Hyperion Testnet:

3. Built an AI-Powered Playing/Trading Bot

We leveraged the power of Alith AI to make in-game trading decisions in real time.
Repo: GitHub - MortalCoin/mortalcoin_alith_bot: MortalCoin’s AI playing bot makes decisions using the Alith AI Agent.
Demo: https://youtu.be/GtFaSFPcWYc

4. Frontend Development

A lot of work went into the frontend, including:

  • Privy authentication integration
  • Complete game flow design
  • Game history & player profiles
  • Contract and backend integration

All tied together to deliver a real-time on-chain PvP experience.

5. Backend Infrastructure

We created a backend layer to:

  • Relay and sign off-chain position commitments for PvP
  • Watch ongoing games
  • Hide player directions using signature logic

6. Developer Utilities

a) Market Maker Bot for Hyperion Test DEX

Repo: GitHub - MortalCoin/mortalcoin-dex-bot

Used to simulate trading activity and provide price feeds for our battles.

b) CLI for Smart Contract Interactions

Repo: GitHub - MortalCoin/mortalcoin-evm-cli

Simplifies game creation, testing, and technical validation.

:microphone: Live Presentation:
We also showcased MortalCoin during a Metis Vibe Session

Key Challenges

1. Matchmaking and the PvP Challenge

Since the game is PvP, the main challenge is matchmaking. If a player creates a game and no one joins — that’s a blocker, especially during the early stages of the project when user activity is low.

To solve this, we developed a matchmaking bot that plays by trading using AI. It acts as a kind of agent filling the role of an opponent.

Repo:

The bot constantly monitors the matchmaking lobby, joins open games, listens to the ongoing game state (real-time prices, opponent actions, etc.), and tries to make good decisions based on its assigned role.

2. Price Feeds and Market Simulation

Another major challenge is the price feed. To make the game fun, prices must move often enough and reflect meaningful market behavior — while remaining accurate.

Technically, it’s possible to integrate real asset trading instead of paper trading, but:

  • It complicates the game and pushes it toward being more of a gamified trading wrapper (not necessarily bad — could be explored separately)
  • It requires a liquid perpetual market to support both long and short positions
  • Prices must be reliable and update on very short timeframes (e.g., per second or even tick-level)

We haven’t found a suitable decentralized solution suitable for POC (like an oracle refreshing fast enough), so for testnet we built our own market-making bot that simulates price movement on AMM DEX pairs - effectively acting as an in-house oracle.

Repo:

3. Gameplay Depth via Hidden Information

I wanted to make the game interesting, adding elements of partially hidden information, similar to poker. If all variables are visible — current price, realized PnL, positions (yours and your opponent’s) — it turns into a deterministic equation-solving task rather than a game.

So, in MortalCoin, you only know whether the opponent has opened a position — but not the direction (long or short). This creates tension and strategy.

To support this, we implemented a system where positions are hashed with a backend key before being sent on-chain. The flow is:

  • Player sends an EIP-712 object with position details to the backend
  • Backend hashes the position and signs it
  • Player submits the hashed version to the smart contract
  • Direction is only revealed when the player closes the position

This prevents sniping and adds a layer of strategy.

4. Incomplete Games and Forced Finalization

One more big challenge: non-finished games, whether abandoned on purpose or due to connection loss.

The contract calculates PnL based on the price at the time of position closing, which opens a potential exploit where a malicious player might avoid closing their position to lock in a win or deny the opponent’s reward.

To prevent this, we added a forceFinish function to the contract. Our backend watcher monitors all ongoing games and triggers forceFinish for any game that wasn’t completed in time.

It was also tricky to implement a reliable system for storing nonces and direction data on the backend side, so we could finalize games even when one player is unresponsive.


Game Flow: Sequence Diagram

What’s Next?

We’re just getting started!

  • Alpha Testing (ETA: August)
    Polish all layers, pay off technical debt, and prepare for community testing (small events with $ rewards).

  • Beta Testing (ETA: September – October)

    Launch the first tournament with real, bigger prizes and continue collecting feedback.

  • Mainnet Launch (ETA: December – January)
    Huge tournament event (with seasons, ELO rankings, and leagues), plus Gleam, Galxe & Layer3 campaigns, and paid ads to amplify everything!

25 Likes

This sounds like a really interesting project, Tony! The concept of turning crypto trading into a fighting game with real-time simulation and on-chain verification is quite innovative.

Here are a few thoughts and potential discussion points for you, based on your post:

  • Metis Hyperion Integration: You mentioned deploying your first on-chain logic using Metis’s Hyperion. This is a great way to leverage the speed and security of the Metis L2 network. I’m curious about what specific gameplay elements you plan to make cryptographically verifiable. Are you thinking about verifiable randomness for match outcomes, or perhaps on-chain escrow for in-game assets?
  • Community Engagement: The leaderboards, referral system, and missions are excellent for driving user engagement. Have you considered any tokenomics or NFT integration strategies to further incentivize participation and long-term retention?
  • Technical Challenges: Transitioning from a Telegram Mini App to a full web app while maintaining real-time gameplay and integrating on-chain mechanics sounds technically challenging. What are some of the biggest hurdles you’re anticipating, and how are you planning to address them?

I’d also recommend sharing this project in the #ideation channel on the LazAI Discord. There are a lot of knowledgeable people there who could provide valuable feedback and suggestions.

To find the discord, you can use this search query: LazAI Discord

4 Likes

We started active R&D at the beginning of the week and already have a progress, including initial brainstorm results and implementation planning (game sequence diagram attached)

The current flow idea for on-chain gameplay is as follows:

Concept

We aim to build a secure, manipulation-resistant PvP arena using EVM-compatible smart contracts. All core actions such as betting, creating and joining games, opening/closing positions, and finalizing are performed on-chain. The backend plays a supporting role: validating on-chain activity, relaying messages between players, and tracking game states.

Backend Responsibilities

Event Listener

  • Listens to smart contract events
  • Tracks and syncs game states (pending, active, completed) with a centralized DB
  • Keeps game data fresh for frontend UX (matchmaking, game history, rewards)
  • Removes games if the creator goes offline

Game Status and Matchmaking API

  • /api/game/create validates initGame transactions
  • /games/waiting-for-opponent returns available games to join
  • /api/game/start validates joinGame transactions

Signature Relay

  • /api/position/signature provides backend EIP-712 signature for opening positions
  • WebSocket or long polling is used to relay signature requests:
    Player 2 → Backend → Player 1 → (Signs) → Backend → Player 2

Game Watchdog

  • Tracks whether the game creator (Player 1) is online
  • Hides the game from the list if the creator is offline
  • During joinGame, the contract validates Player 1’s short-TTL signature, proving they were online and approved the join

Frontend Responsibilities

Game Start

  1. User clicks “Start Fight” and selects a fighter
  2. Frontend queries /games/waiting-for-opponent
  3. If a game is found, it requests a join signature from Player 1 via backend
  4. If no game is found, frontend calls initGame(poolAddress, betAmount)
  5. After the transaction is confirmed, backend validates it via /api/game/create

Matchmaking UI

  • Displays a waiting screen with a countdown
  • Optionally subscribes to real-time updates via WebSocket

In-Game Trading

  • openHashedPosition(gameId, directionHash, backendSignature) is used to open a position (direction is hidden initially)
  • Signature is retrieved from /api/position/signature
  • closePosition(gameId, direction, nonce) is used to reveal and close the position

Finalization

  • Once both players have closed their positions, the creator finalizes the game via finalizeGame(gameId)
  • If someone is unresponsive, backend triggers forced finalization after timeout

Smart Contract Core Functions

  • initGame(poolAddress, betAmount) locks the bet and creates a game
  • joinGame(gameId, poolAddress, betAmount, joinSignature) lets the second player join
  • openHashedPosition(gameId, directionHash, backendSignature) opens a hashed position
  • closePosition(gameId, direction, nonce) reveals and settles the position
  • finalizeGame(gameId) settles rewards and closes the game

Game Pool Whitelist

  • The contract stores a whitelist of allowed DEX pools for each network
  • Only the owner can modify the list to prevent use of fake or manipulatable pools
  • The contract uses these whitelisted pools to fetch real-time prices for PnL and trade validation

Open Questions

  1. How to efficiently track intermediate game state (e.g., opponent’s position, PnL) — will likely be handled off-chain via event polling
  2. Fail-safes and abuse prevention:
    • Join TTL signatures required from Player 1
    • First-come, first-serve enforcement on backend and contract
    • Pool whitelist enforced in contract

Security Measures

  • Only whitelisted pools are used
  • All actions require confirmed on-chain transactions
  • TTL-based join signatures ensure liveness and prevent stolen entries
  • Backend signs position hashes to enable forced closure if needed
3 Likes

Progress Update #2:

We implemented and deployed a very early version of the fights smart contract (can probably be called v0.0.1) to the Hyperion testnet:

We’ve also started integrating it into the game. Game creation: https://drive.google.com/file/d/1GunlSxwTld3cn9lFVNQhIizc4TmtZdcV/view?usp=sharing

For now, it’s running in dev testing mode, where the frontend is mocking the EIP-712 payload.

We also formed a vision for using an AI agent (Alith): we could create a bot that plays the game / makes trading decisions and fills the matchmaking lobby. There’s already a concept and some early code drafts for such a bot - we’ll just need to integrate Alith there and make it open-source.

Current todo list (high-level overview):

  • Continue frontend integration (position opening/closing/tracking, matchmaking)

  • Implement the pending games list in the contract

  • Implement EIP-712 payload signing flow for joining games (requires the game creator’s signature), handled via backend routing

  • Implement position direction hashing

  • Implement backend signing for position (trade) opening

2 Likes

Hello @tonymorony,

I’ve created a dedicated topic for all active campaigns. Whenever your campaign goes live for the community, please feel free to post it in this specific topic.

Thanks!

3 Likes

Thank you very much!

We expect to have a playable user version ready within the next 10-14 days and will definitely share it in this topic once it’s live.

3 Likes

Progress Update #3

The Build stage is coming to an end, and we’re doing our best to implement everything we planned and ship a public build in time.

Updates:

Demo video: https://drive.google.com/file/d/1hr90ekhb1aE9cNNV2IyYrQwqMbhaHIeb/view?usp=sharing

  • On the backend, we’re working on PvP matchmaking logic:
    • Checking users’ online status to show only active/joinable games
    • Relaying signatures between players
    • Fully decoupled the system from the old logic tied to Telegram authentication

Next week, we plan to launch the first public release featuring the full on-chain real-time gameplay experience on Hyperion - so the community can finally try it out! (We’re just as excited!)

You are really intuitive for a Bot you know? :rofl:

2 Likes

MortalCoin HyperHack Hackathon Submission

Live link: https://stage.mortalcoin.app/
Game demo video: https://youtu.be/4ZrYxP0vC_w

Alith AI trading bot demo video: https://youtu.be/GtFaSFPcWYc
AI trading bot Repo: GitHub - MortalCoin/mortalcoin_alith_bot: MortalCoin’s AI playing bot makes decisions using the Alith AI Agent.

Contract repo: GitHub - MortalCoin/mortalcoin-evm
Contract on Hyperion: Metis Hyperion Testnet address details for 0xDf8730693833b9e27D5999863feBb3028fcc6927 | Blockscout

Deck draft: https://www.canva.com/design/DAGujqtuAVo/Z4dVLaIKFc1whyVgGmkdJw/edit?utm_content=DAGujqtuAVo&utm_campaign=designshare&utm_medium=link2&utm_source=sharebutton

MortalCoin is a real-time PvP crypto trading game where players battle using simulated trades based on live market data. Think Mortal Kombat meets Hyperliquid, with cryptocurrencies personified as playable fighters.

Each battle simulates a short (60-second, currently) trading session where players choose strategies and try to outtrade their opponents. Both players lock in equal bets before the game starts — the winner takes it all.

The core monetization model is a small operational fee (currently 1%) deducted from the total pot upon payout, handled directly by the game smart contract.

Gameplay explained: Trading Fight – Gamified Crypto Battles Inspired by Hyperliquid and MortalKombat | MortalCoin Docs


What We Built

It’s been an exciting month of non-stop building on the Hyperion Testnet.
Our small but mighty team smashed keyboards and shipped features.

The team members are:

  • @artemii235 Artem, blockchain developer (mainly in Rust) — designed and developed the smart contract, overall technical concept, CLI, and MM tools.

  • @g.ionov George, backend developer (Python) — developed the backend authentication module, relay exchange system, and matchmaking.

  • @tonymorony Tony (me) - developed the frontend (TypeScript, Vite) and the Alith AI playing bot (Python), acted as PM, QA, and UX/UI designer, and was responsible for planning, documentation, and external communications.

Here’s what we accomplished:

1. Brainstormed and Designed the Game Concept

We came up with the idea for an on-chain trading competition game:

2. Designed and Deployed the Game Smart Contract

Repo: GitHub - MortalCoin/mortalcoin-evm
Deployed on Hyperion Testnet:

3. Built an AI-Powered Playing/Trading Bot

We leveraged the power of Alith AI to make in-game trading decisions in real time.
Repo: GitHub - MortalCoin/mortalcoin_alith_bot: MortalCoin’s AI playing bot makes decisions using the Alith AI Agent.
Demo: https://youtu.be/GtFaSFPcWYc

4. Frontend Development

A lot of work went into the frontend, including:

  • Privy authentication integration
  • Complete game flow design
  • Game history & player profiles
  • Contract and backend integration

All tied together to deliver a real-time on-chain PvP experience.

5. Backend Infrastructure

We created a backend layer to:

  • Relay and sign off-chain position commitments for PvP
  • Watch ongoing games
  • Hide player directions using signature logic

6. Developer Utilities

a) Market Maker Bot for Hyperion Test DEX

Repo: GitHub - MortalCoin/mortalcoin-dex-bot

Used to simulate trading activity and provide price feeds for our battles.

b) CLI for Smart Contract Interactions

Repo: GitHub - MortalCoin/mortalcoin-evm-cli

Simplifies game creation, testing, and technical validation.

:microphone: Live Presentation:
We also showcased MortalCoin during a Metis Vibe Session

Key Challenges

1. Matchmaking and the PvP Challenge

Since the game is PvP, the main challenge is matchmaking. If a player creates a game and no one joins — that’s a blocker, especially during the early stages of the project when user activity is low.

To solve this, we developed a matchmaking bot that plays by trading using AI. It acts as a kind of agent filling the role of an opponent.

Repo:

The bot constantly monitors the matchmaking lobby, joins open games, listens to the ongoing game state (real-time prices, opponent actions, etc.), and tries to make good decisions based on its assigned role.

2. Price Feeds and Market Simulation

Another major challenge is the price feed. To make the game fun, prices must move often enough and reflect meaningful market behavior — while remaining accurate.

Technically, it’s possible to integrate real asset trading instead of paper trading, but:

  • It complicates the game and pushes it toward being more of a gamified trading wrapper (not necessarily bad — could be explored separately)
  • It requires a liquid perpetual market to support both long and short positions
  • Prices must be reliable and update on very short timeframes (e.g., per second or even tick-level)

We haven’t found a suitable decentralized solution suitable for POC (like an oracle refreshing fast enough), so for testnet we built our own market-making bot that simulates price movement on AMM DEX pairs - effectively acting as an in-house oracle.

Repo:

3. Gameplay Depth via Hidden Information

I wanted to make the game interesting, adding elements of partially hidden information, similar to poker. If all variables are visible — current price, realized PnL, positions (yours and your opponent’s) — it turns into a deterministic equation-solving task rather than a game.

So, in MortalCoin, you only know whether the opponent has opened a position — but not the direction (long or short). This creates tension and strategy.

To support this, we implemented a system where positions are hashed with a backend key before being sent on-chain. The flow is:

  • Player sends an EIP-712 object with position details to the backend
  • Backend hashes the position and signs it
  • Player submits the hashed version to the smart contract
  • Direction is only revealed when the player closes the position

This prevents sniping and adds a layer of strategy.

4. Incomplete Games and Forced Finalization

One more big challenge: non-finished games, whether abandoned on purpose or due to connection loss.

The contract calculates PnL based on the price at the time of position closing, which opens a potential exploit where a malicious player might avoid closing their position to lock in a win or deny the opponent’s reward.

To prevent this, we added a forceFinish function to the contract. Our backend watcher monitors all ongoing games and triggers forceFinish for any game that wasn’t completed in time.

It was also tricky to implement a reliable system for storing nonces and direction data on the backend side, so we could finalize games even when one player is unresponsive.


Game Flow: Sequence Diagram

What’s Next?

We’re just getting started!

  • Alpha Testing (ETA: August)
    Polish all layers, pay off technical debt, and prepare for community testing (small events with $ rewards).

  • Beta Testing (ETA: September – October)

    Launch the first tournament with real, bigger prizes and continue collecting feedback.

  • Mainnet Launch (ETA: December – January)
    Huge tournament event (with seasons, ELO rankings, and leagues), plus Gleam, Galxe & Layer3 campaigns, and paid ads to amplify everything!

6 Likes

Hi Metisans! We’re continuing to polish the game - matchmaking and the Alith bot are now operating more smoothly.

Unfortunately, we missed the Spotlight campaign, so we decided to launch our own to make sure MortalCoin players are aware of the Hyperion version and give it a try.

We’ve launched a week-long campaign divided into two parts:

  1. In-game leaderboard (win fights to climb the ranks) - $222 prizepool

  2. Content creation - $111 prizepool

Details: 🏆 MortalCoin Hyperion Alpha Launch Event | MortalCoin Docs

Everyone is more than welcome to participate!

2 Likes
2 Likes

I saw an interesting post Heads up HyperHack teams: your user acquisition budget is probably way too low - #4 by CrisMetis about user acquisition costs -for some reason, I can’t reply under it, so I’ll share our experience here. cc @daryl

That’s actually why we decided to move forward with Privy and their embedded wallets for our game.

This approach allows us to:

a) Let users register with email, X (Twitter), or another social network and automatically create a non-custodial wallet for them.

b) Eliminate signature requests and annoying pop-ups thanks to Privy settings, which hide these steps so users can focus entirely on the gameplay.

However, we realized that a bit of education is still needed regarding private keys since we’ll be distributing leaderboard prizes to wallet addresses.

The main benefit is that this approach lets us roll out on-chain products to the same user base we acquired for our Telegram game (which was completely off-chain). These users (T3) had a CPA of around $0.10–$0.20 for us, so by lowering the learning curve and entry barrier (through UX simplification), we can leverage that audience effectively.

In the future, we plan to implement a gas station (similar to Base’s paymaster), making it even easier and allowing us to attract regular mobile gamers (with relevant CPC) since there will be virtually no overhead for them.

That said, there might still be some overhead because Privy could become quite costly at scale with a large user base, as far as I know.

2 Likes

Brother, I’m very happy to have found this while perusing hackathon submissions. You have built something really cool and really smart – and I’m not just saying that because it’s extremely similar to my own project I’ve spent most of 2025 building.

I think you are doing several things much better than I did. For several of your roadmap steps, I could give my experiences working through them like the rollout & ramp-up of real-money contests, the non-/custodial wallet decision, etc. And I could DEFINITELY talk about the huge mistakes I made which resulted in DD’s failure so that MortalCoin can do better at each step.

While I shuttered DegenDuel and its associated token a week ago, the site is still 100% operational, so I invite you to poke around and rip off any ideas you might like (or flame it). I am going to DM you, surely we would have a good chat :+1:t2: Edit: Just realized there is no DMing lol

2 Likes

Hi buddy! Thanks so much for taking the time to write and I’m really sorry to hear your project didn’t take off.

The concept really is very similar! I’m especially curious about how you implemented room creation. I’ve been thinking about something like that for the future too (kind of like a poker-room-style lobby).
I also love the idea of distributing the fees among token holders - that’s a really cool twist. I’d be very interested to see what the actual duel interface looks like.

I’d appreciate any advice you can share, and I’d love to hear more about your journey with the project.
Here’s my Telegram: @realtonyl, and X: https://x.com/mybrainforked

It’s such a great feeling to find someone who shares the vision for gamifying trading. Awesome to see the forum and the whole idea of building in public really doing its job. :slight_smile:

2 Likes

Subject: Feedback on Web Version Tournament Experience

Assalamu Alaikum Sir,

I am Akash, a regular participant in your web version tournament. Since the beginning of the tournament, I have played over 150 games across two different accounts. Based on my experience, I would like to share some feedback, and I hope you will kindly take the time to review it.

Initially, I faced some issues with gameplay at the start of the tournament, but after the second update, most of those problems have been resolved. Now, finding an opponent takes no more than 10 seconds, which is excellent.

However, I’ve noticed that after the game starts, it often takes a moment for the position to be confirmed. As a result, the trade I attempt to take sometimes ends up executing at a different position than intended. This can be frustrating. To improve this, it would be very helpful to introduce a manual trading system or an option to choose between live market orders and limit orders.

also sometimes when I try to close a trade, but it doesn’t close properly. As a result, I end up losing matches that I was actually on the way to winning. Although this doesn’t happen every time, I would really appreciate it if you could look into this issue when you get the chance.

Another issue I’ve observed relates to PnL. Most of the time, I close trades with a 0.02 PnL, but only 0.01 gets added to my dashboard. This has happened multiple times, and I hope you can look into why there’s a consistent 0.01 discrepancy.

Lastly, I would like to suggest implementing a candlestick (red-green) chart in the live interface. This would allow traders to better analyze the market and make more informed decisions. I believe this would be a valuable addition and highly beneficial for all users.

These are a few insights and suggestions based on my experience. If there are any mistakes or misunderstandings in my message, I kindly ask for your forgiveness and understanding.

Wishing you and your team continued success. I truly believe that together we can go a long way.

Best regards,
Akash

2 Likes

Dear Akash,

Thank you so much for taking the time to register on the forum and for your extremely constructive and valuable feedback! Also, thank you for playing MortalCoin :slight_smile:

Yes, I completely agree – slippage and delays are indeed an issue, and we are highly dependent on blockchain transaction confirmation times here.

Currently, on the Hyperion testnet, a transaction confirmation takes about 2 seconds on average. The faster the transactions are (and I’m confident the Hyperion mainnet will be blazignly fast), the better the user experience will be in the game.Additionally, we are currently using public RPC nodes and can’t control latency/ping. When deploying on mainnet, we’ll most likely run our own RPC nodes.Of course, there’s also plenty to optimize within the game itself (a lot!). :slight_smile:

I completely understand your concern about opening and closing trades not being exactly at the click price, as the element of chance is present.Right now, we’re still using a hackathon solution for pricing (they update every 9 seconds because we place market-making orders every 9 seconds), which also affects this behavior.Your idea to diversify gameplay with limit orders is really interesting, by the way. I’m also considering experimenting in the future with customizable leverage (especially for longer rounds – that could be very exciting). And if we add limit orders, we can implement stop-loss and take-profit orders as well.

In any case, your feedback is extremely valuable, and we’ll work on improving these aspects in future versions to deliver a slick real-time experience.

2 Likes

Thank you so much for the detailed and thoughtful reply. Iam very glad & truly appreciate you taking the time to address my feedback😊. Now looking forward to seeing how MortalCoin evolves.The core idea is exciting, and it’s clear you’re building it with genuine care and attention to feedback

Thanks again sir​:blush::blush:

1 Like

The MortalCoin Hyperion event has ended!

Key stats:

  • PvP games played vs Alith-powered AI agent: 1,263

  • Users participated: 54

  • In-game time: 20+ hours

  • Game contract transactions on the Hyperion testnet: 23,000+

Huge thank you and appreciation to all the participants. We received tons of valuable feedback and battle reports in the Telegram chat - it will help us improve the game and shape its future. It was amazing to witness your excitement, passion, and will to win.
Thank you for every fight and every post you created about MortalCoin!

We’ll finalize the results of the battle and social campaigns and send out rewards over the next 3 days.
Stay tuned on X and Telegram for updates.

Thank you again, Fighters!