HALOWERKKettenwerk
tx / simulate
Answers the question that stands before every signature: what really happens to my assets and my rights. The call is executed against the state of a named block on a simulation interface, never on the chain — this hub holds no private key and broadcasts nothing. Balance changes are not inferred from events but measured: the same simulation reads every touched balance immediately before and immediately after the call, native currency included, so an outflow that emits no event is still.
POST https://kette.halowerk.com/tx/simulateEingaben
| Feld | Typ | Pflicht | Beschreibung |
|---|---|---|---|
| chain | string | Ja | Chain to simulate on. |
| from | string | Ja | Sender address. No signature is needed and none is created. |
| to | string | Ja | Target address. |
| data | string | Nein | Call data. |
| value | string | Nein | Value in wei, decimal or 0x. |
| gas | integer | Nein | Optional gas limit for the simulation. |
| block | string | Nein | "latest" or a block number as decimal string. |
| state_overrides | object | Nein | Optional state overrides per address, in the eth_simulateV1 format (balance, nonce, code, state, stateDiff). |
Vollständiges Eingabeschema anzeigen
{
"type": "object",
"required": [
"chain",
"from",
"to"
],
"additionalProperties": false,
"properties": {
"chain": {
"type": "string",
"enum": [
"ethereum",
"base",
"arbitrum",
"optimism",
"polygon",
"bsc"
],
"description": "Chain to simulate on."
},
"from": {
"type": "string",
"pattern": "^0x[0-9a-fA-F]{40}$",
"description": "Sender address. No signature is needed and none is created."
},
"to": {
"type": "string",
"pattern": "^0x[0-9a-fA-F]{40}$",
"description": "Target address."
},
"data": {
"type": "string",
"pattern": "^0x[0-9a-fA-F]*$",
"default": "0x",
"description": "Call data."
},
"value": {
"type": "string",
"default": "0",
"description": "Value in wei, decimal or 0x."
},
"gas": {
"type": "integer",
"minimum": 21000,
"maximum": 30000000,
"description": "Optional gas limit for the simulation."
},
"block": {
"type": "string",
"default": "latest",
"description": "\"latest\" or a block number as decimal string."
},
"state_overrides": {
"type": "object",
"description": "Optional state overrides per address, in the eth_simulateV1 format (balance, nonce, code, state, stateDiff)."
}
}
}Veröffentlichtes Eingabebeispiel
{
"chain": "ethereum",
"from": "0x0000000000000000000000000000000000000000",
"to": "0x0000000000000000000000000000000000000000",
"data": "0x",
"value": "0",
"block": "latest"
}Ergebnis & Dokumentation
Maschinenlesbare Dokumentation dieses Hubs
Quelle dieser Seite: der veröffentlichte HALOWERK-Katalog. Stand: 2026-11-01, 15:19 UTC.
Weitere Endpunkte dieses Hubs
- Kettenwerk0,004 USDC
bridge / track
POSThttps://kette.halowerk.com/bridge/trackReads the source transaction on chain, identifies the bridge from the contracts it touched, and reports what actually left the wallet. overdue is measured against the usual duration of THAT bridge, and the comparison value is part of the an
- Kettenwerk0,003 USDC
chain / health
POSThttps://kette.halowerk.com/chain/healthQueries every public RPC endpoint this hub knows for a chain in parallel — at least three, usually five — and reports what each one says instead of trusting one. Disagreement is the valuable finding: a single endpoint that lags or serves a
- Kettenwerk0,006 USDC
contract / upgrade risk
POSThttps://kette.halowerk.com/contract/upgrade-riskUpgradeability alone is not a finding — every serious protocol is upgradeable. The finding is who holds the key and how much warning holders get. This endpoint reads the proxy pattern from the EIP-1967 slots, the clone bytecode or an implem