Broadly-scoped RFP: Porting Creepts to Telegram Mini App

RFP Title:

Porting Creets to Telegram App

Wave 2 Intent:

Grow the Cartesi ecosystem

Overview:

Creepts was developed as the first application to showcase the Cartesi Machine computational power as well as tooling versatility by running verifiable computations on a Linux runtime. Creepts had multiple tournaments during 2020 and tens of thousands of gameplay submissions. You can give it a try at https://creepts.cartesi.io

Creepts was built in typescript, but the DApp was created before we had any framework to make it easier to develop Cartesi DApps. The matches are executed locally in the browser using the same game engine that runs inside the Cartesi Machine for gameplay validation. Once the match is done, the gameplay is submitted onchain and the Creepts DApp Node performs the validation by resimulating the match feeding it the moves provided in the submitted log.

The scope of this RFP is porting Creepts to a modern Cartesi framework (Rollups, Co-processor or both combined) and maintaining it as a Mainnet application with a Telegram Mini App client. Proposing teams can reuse the parts they desire, ranging from the typescript frontend made with the Phaser game engine (GitHub - cartesi/creepts-game: A JS and Cartesi-compatible implementation of Creepts game) up to the game simulation logic (GitHub - cartesi/creepts-engine: Creepts Game Engine).

Solution Criteria:

We encourage teams applying for this RFP to submit:

  • Solutions that make usage either of Cartesi Rollups and/or Cartesi Co-processor to validate Creepts matches
  • Solutions that are able to run in production and to be economically viable
2 Likes
  • Doubt: Wouldn’t it be more effective to break this RFP? One to port Creepts to a modern Cartesi Framework (still using the current web client) and another to develop a Telegram mini app client.
  • Doubt: Is it expected that the proposer keep the solution running in mainnet? If yes, for how long? Also, if yes, I think more info should be added to solution criteria regarding it.
    • and maintaining it as a Mainnet application

  • Suggestion: Provide more detail regarding what is expected with “able to run in production”.
  • Suggestion: Provide more detail regarding what is expected with “economically viable”.

Is there anything here that requires a rollup aspect of it? Thinking it’s easier to assess return on investment if it was coprocessor based (driving traffic to coprocessor)

Also, fixing title: “Creets” → “Creepts”

Update

As @claudio.silva pointed out, we also believe this RFP could be split into two: developing a Telegram Mini App client and advancing the Creepts app. We would be open to seeing an RFP focused on the Telegram Mini App aspects, but when it comes to advancing Creepts, we believe it is better suited as a community proposal rather than an RFP.

We encourage submitting a community grant proposal specifically for advancing the Creepts app instead.