Summary
The Tempo transaction spec defines per-call value transfers in batch transactions:
pub struct Call {
to: TxKind,
value: U256, // ← Value per call is spec'd
input: Bytes
}
However, the node currently rejects batch transactions with non-zero call values:
error code -32603: Revm error: value transfer in Tempo Transaction not allowed
Context
Expected Behavior
Batch transactions should allow per-call value transfers, enabling atomic operations like:
- ETH transfers + contract calls in one tx
- Multi-recipient payments
- DEX operations with ETH value
Acceptance Criteria
Summary
The Tempo transaction spec defines per-call value transfers in batch transactions:
However, the node currently rejects batch transactions with non-zero call values:
Context
cast batch-sendwith value support, but tests are disabled pending node supportcast batch-send --call "0x...:0.0001ether" --call "0x...::fn()"Expected Behavior
Batch transactions should allow per-call value transfers, enabling atomic operations like:
Acceptance Criteria
valueinCallstructsCAST BATCH-SEND WITH VALUEtest in tempo-foundry CI