• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Flatly)
  • No Skin
Collapse
SmartHoldem Community

Community

Proof-of-Play consensus the gaming chains in the Smartholdem platform

Scheduled Pinned Locked Moved Announcements
proofofplaysmartholdemgamesnodegithub
1 Posts 1 Posters 1.1k Views
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • vlad2323V Offline
    vlad2323V Offline
    vlad2323
    wrote on last edited by vlad2323
    #1

    Proof-of-Play consensus the gaming chains in the Smartholdem platform https://github.com/technologiespro/proof-of-play/blob/master/README.md

    1sth_platform_for_twitter_03_09_2019.jpg

    • a new block is generated when a game event occurs

    • data is serialized into a well-known array instead of objects to reduce the amount of traffic transmitted to other nodes

    • game nodes interact with each other using sockets

    • at the socket level we use additional compression of serialized data

    • separate protocol for receiving static information and query execution on JSON/RPC

    • storage LevelDB keys/values

    • real-time gaming events are broadcast via sockets in DAPPs

    • optional: to develop a load balancer, sharding

    • solve the problem of nat using udp through the stun

    blockData: 0xblockHeight

    • prevBlockHash

    • blockHash

    • blockTime

    • generatorId: address

    • payload: [txsData]

    txsData:[]

    • txtype: bet/play (0/1)

    • txIdSTH: hash

    • gameId: hash-md5

    • amount: sth

    • timestamp: unixtime

    • senderId: address

    • recipientId: address

    • gameValue: 0/1 hash

    • senderSig: from sth

    • affiliateID: address

    • txType: result (2)

    • txIdSTH: hash

    • gameId: hash-md5

    • amountWin: sth

    • timestamp: unixTime

    • senderId: address

    • winnerId: address

    • affiliate: {
      accountId: address
      amount: sth }

    • playerBet: {
      accountId: address
      blockId
      txIndex
      value
      amount }

    • playerPlay: {
      accountId: address
      blockId
      txIndex
      value
      amount }

    • gameResult: 0/1

    1 Reply Last reply
    1

Decentralized Gaming Platform
  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search