not approved

Immutable record of Random Numbers

$8,000.00 Requested
Ideascale logo View on ideascale
Community Review Results (1 reviewers)
Addresses Challenge
Feasibility
Auditability
Problem:

<p>In gaming there is a need to have an immutable record of pseudo random numbers generated for auditability by gaming authorities .</p>

Yes Votes:
₳ 25,149,008
No Votes:
₳ 34,646,915
Votes Cast:
191

  • download
  • download

Detailed Plan

See our main proposal for BingoToken - Play-To-Earn : https://cardano.ideascale.com/a/dtd/BingoToken-Play-To-Earn/366726-48088

This proposal is to persist the metadata of each game to the Cardano blockchain as a public, immutable and permanent record of all the relevant data associated with that game.

Goal

Build a nodejs service to execute on game completion which should:

o batch all the BingoToken (and ADA if applicable) distributions into a single transaction

o write the game data (game id, numbers drawn, winner info, winning card numbers) to the Cardano Blockchain to provide immutable proof and auditability of the pseudo-random number generator and winning card numbers.

Execution and Programming Language

This part of the application will be written as a standalone nodejs service which will connect to a websocket of the main application and wait for a message to tell it that a game has been completed. The message will include all the information required for token distribution and the metadata which needs to be written to the blockchain in the transaction.

The service will respond to the main application through a websocket message to indicate success or failure.

We will be writing this as a standalone service so that we can isolate the server running this service along with the cardano-cli from the main application backend to enhance security. It also allows us to make this code available as open source.

Open Source License

This nodejs service will use the MIT License and will be made publicly available in a GitHub repository.

Use of Funding

The funding will be used to complete the development as outlined above.

Metrics of Success - 3 Months

The service should be completed and the source code made available in the publicly available in a GitHub repository within 3 months.

(Metrics of Success for 6 and 12 month periods are not applicable)

社区顾问评论 (1)

Comments

close

Playlist

  • EP2: epoch_length

    Authored by: Darlington Kofa

    3分钟24秒
    Darlington Kofa
  • EP1: 'd' parameter

    Authored by: Darlington Kofa

    4分钟3秒
    Darlington Kofa
  • EP3: key_deposit

    Authored by: Darlington Kofa

    3分钟48秒
    Darlington Kofa
  • EP4: epoch_no

    Authored by: Darlington Kofa

    2分钟16秒
    Darlington Kofa
  • EP5: max_block_size

    Authored by: Darlington Kofa

    3分钟14秒
    Darlington Kofa
  • EP6: pool_deposit

    Authored by: Darlington Kofa

    3分钟19秒
    Darlington Kofa
  • EP7: max_tx_size

    Authored by: Darlington Kofa

    4分钟59秒
    Darlington Kofa
0:00
/
~0:00