Capabilities / Rewards
Milestone programs
Unlock a reward after an observable target.
Implementation boundary
BSC adaptationActual finalized holder conditions and full streamed allocation now drive prefunded milestone root and fixed claims under a real finite EOA grant. Actual main dispatcher completes canonical payments; unknown/revoked steps retain their original commitments. Remaining: Original generic arbitrary milestone conditions are not implemented; current reviewed metric-condition schema is finite. Production fixed program signer/state-callback HTTPS+separate secrets, actual immutable vault/Portal/token/adapter identities and full history RPC, funded native escrow/operator gas, real EOA finite grant and explicit per-scope/model/scheduler permission; no such production run is proved locally.
Current awake evidence
actual local http d1 eip712 evm finite autonomous subset verified
Production verification: not complete. Registered model tools: create_funded_program · prepare_program_execution · inspect_funded_program_execution · execute_funded_program. Registration does not mean enabled or actually run.
Original typed tools
create_milestone_reward
Published limits / Solana reference
{
"max_program_available_pct": 100
}Original capability specification ↗These are source-reported limits. BSC values and venue limits require calibration.
AWAKE