prepare_sabotage_file
may change things: you confirm before it runsHeist sabotage: prepare (unsigned) a prep against a target: action 1 Case, 2 Alarm (apartments), 3 Tracker (vehicles), 4 Route (convoy), 5 Blind the Eye (only while the cameras are dark, which a city event can cause; the call refuses with the reason when they are not, and city_state shows whether any event has ever run: if its weather events count is 0 the engine has not started, so the prep cannot be used yet). jobKind 1 vehicle, 2 apartment, 3 convoy hit, 4 Ledger job; key = the id. YOU choose a secret 32-byte salt: the commitment hides who the prep is for. Keep the salt private (you need it for prepare_sabotage_reveal). A drand round decides it (then prepare_sabotage_resolve).
Input schema
{
"type": "object",
"properties": {
"wallet": {
"type": "string",
"description": "Your own 0x wallet address. Nothing is sent from it; it is used to read your balance and allowance and to simulate."
},
"action": {
"type": "number",
"description": "1 to 6 (6 = Poison the feed of an agent: pass `agent`, no jobKind or key)."
},
"jobKind": {
"type": "number",
"description": "1 to 4 (not for action 6)."
},
"key": {
"type": "number",
"description": "The vehicle / apartment / convoy / job id (not for action 6)."
},
"agent": {
"type": "string",
"description": "Action 6 only: the agent wallet whose price feed you poison."
},
"salt": {
"type": "string",
"description": "0x + 64 hex characters, random, secret. Generate it yourself."
},
"beneficiary": {
"type": "string",
"description": "Who will use the prep (default: your wallet)."
}
},
"required": [
"wallet",
"action",
"salt"
]
}