Domingo_gou

All four crypto payroll payments reconciled. If the fifth is entered incorrectly, who checks?
On September 1, @primus_labs and AllScale completed a technical validation on BNB Chain. Four fictional employees, four sample payroll payments, and on-chain settlement succeeded, with the decrypted amounts matching the test file.
It’s a good start, but businesses pay their employees every month. There’s still a long way to go from a successful one-time test to finance teams feeling comfortable entrusting the system with a whole month’s payroll.
One detail of this partnership is important. AllScale al

The contract ledger is down 30—has the money on-chain gone down too?
A method called withdraw changes balance from 100 to 70.
It looks like 30 was withdrawn, but one question cannot be skipped: exactly how many sats did the transaction pay, and to whom?
In Lambit’s official How to Deploy & Call example, the initial state of the same Vault is balance: 100n, while the UTXO is deployed with satoshis: 1_000n. Then withdraw(amount: 30n) is called, and the demonstrated successor state becomes 70n.
This is a local tutorial workflow.
The documentation does not specify the business unit of balance, nor

The contract only schedules two payments, to A and B.
If the wallet adds a change output, why might Lambit reject it before broadcast?
@op_catlayer's Lambit stateful contract can specify multiple payments via outputs at finalization. These multi-output finalization paths use SIGHASH_ALL, which locks the entire set of outputs into the hashOutputs commitment.
Suppose the original outputs are A+B, and the wallet adds Change when funding. The actual outputs then become A+B+Change. The extra change alters the entire set of outputs. The official documentation says the current funded provider rejects