Hi Everyone,
I’m exploring how users from other chains - starting with Solana - can participate in our prediction markets (on BigMarket.ai) wit the least amount of friction and trust assumptions - e.g. I want them to be able to buy prediction shares, claim winnings etc using only their familiar Phantom wallet.
At a high level, the current solutions for cross chain use cases like this, require the Solana user to;
a) deposit funds on Stacks
b) authenticate with a clarity smart contract
c) authorise the contract call - eg buy shares in Market X
The Problem
Step a) has some difficulty around moving the users deposit from a wallet into an on-chain vault but this is outside the current scope.
This current solutions for b) and c) look like this;
> Solana User Action
> Messaging Layer (e.g. Wormhole)
> Guardian Verification
> Off-chain Relayer
> Clarity Contract
Where both the Guardian verification and attestation layer and the ‘off-chain relayer’ carry trust assumptions and complexity and overall, increase the attack surface area of the application.
Proposed Solution:
Native ed25519-verify support in Clarity
A native function such as:
(ed25519-verify message signature public-key)
could enable a much simpler flow:
Solana User Signature
→ Stacks Transaction
→ Clarity Contract
→ Native Verification
→ Contract Action
Why this could matter:
Broader interoperability:
-
Solana
-
Sui
-
Aptos
-
Near
-
Other Ed25519 ecosystems
Potential use cases:
-
Cross-chain prediction markets
-
DAO voting
-
Identity/authentication
-
Wallet interoperability
-
Delegated execution
-
Trust-minimized governance
Why not just use Wormhole / bridges?
Bridges can move assets, but they do not solve native user authentication without additional trust layers.
Stacks already has strong secp256k1 support, but Ed25519 support could unlock entirely new categories of direct cross-chain participation.
Curious to hear thoughts from:
- Core contributors
- SIP authors
- Clarity devs
- Cross-chain builders
- Solana / Stacks ecosystem participants
Would love feedback.