The current design utilizes chess.js along with a lichess chessboard for gameplay activity.
This design takes a singular authority approach where a server is needed to maintain user authorization, historical data, data integrity, move validation and more. This brings a challenge of security and maintenance, as well as cultivating the trust and adoption of a new chess platform.
A new approach would be utilizing existing chess platform public api's to integrate the ETHChess framework as a standalone plugin. Users would then be able to integrate their public profiles and utilize the platform gameplay of their choice. The scope of gameplay authorization and validation would rely on their trusted platform of choice, and a recording of events would them be memorialized with IPFS and submitted to the blockchain for the claim dispute resolution process.
The current design utilizes chess.js along with a lichess chessboard for gameplay activity.
This design takes a singular authority approach where a server is needed to maintain user authorization, historical data, data integrity, move validation and more. This brings a challenge of security and maintenance, as well as cultivating the trust and adoption of a new chess platform.
A new approach would be utilizing existing chess platform public api's to integrate the ETHChess framework as a standalone plugin. Users would then be able to integrate their public profiles and utilize the platform gameplay of their choice. The scope of gameplay authorization and validation would rely on their trusted platform of choice, and a recording of events would them be memorialized with IPFS and submitted to the blockchain for the claim dispute resolution process.