Spike: Validation Mechanism for Staked Masa Tokens in Miner Workflow

[Luka-Loncar]

Objective

The goal of this spike is to determine how a miner can provide a payload to a validator that ensures the wallet associated with the miner has staked Masa tokens. The solution could include a signed payload and facilitate verification of the Ethereum address and staking status.

Questions to Address

Signing Mechanism

• Should the signing of the payload happen on the miner or on the Masa protocol side?
• If signing happens on the miner, what are the security implications of transferring or storing the private key of the Ethereum wallet?
• Can the protocol pre-sign and return the necessary information (payload + signature + public address)?

Separation of Responsibilities

• Should the miner only act as a forwarding mechanism, relaying a pre-signed payload from the protocol?
• What are the implications of requiring the miner to actively participate in signing or validation?

Validation Flow

• How will the validator verify the signature, the public address, and the staked status in a decentralized manner? ( probably SDK toolkit )
• What additional steps or data are needed for the validator to confirm the wallet's staked status?

Acceptance Criteria

• A clear and documented understanding of the best way to handle signing and payload delivery.
• Proof of concept implementation demonstrating the chosen flow.
• A list of next steps and tasks for integrating the solution into the current architecture.

[Luka-Loncar]

Hey @hide-on-bush-x - I've transformed this one into issue, so that I can ask you if this should stay in no status for now still or something was done here?