You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 2, 2021. It is now read-only.
SWAP should make sure that the user never ovepromises on his cheques.
If a peer ever writes a cheque that increases the total amount of uncashed cheques above the total amount of balance in the chequebook (assuming no hardDeposits), he risks that his chequebook fires a chequeBounced event and that peers will disconnect (?) from his.
Proposed solution:
Keep track of the amount of all submitted cheques (cashed / uncashed),
keep track of the amount of money deposited. *
Make sure that 1 never goes above 2. Auto-send more funds or temporarily halt all operations until there is money again in the chequebook.
the chequebook fires a Deposit event when money is deposited and money can be deposited also outside of the SWARM repository. Therefore, the SWARM sourcecode should just assume naively that only money is deposited via it's own process, but when it attempts to submit money (3), it should query the smart-contract for deposit events before depositing itself, to make sure that the internal account of deposit equals the blockchain count of deposit.
The text was updated successfully, but these errors were encountered:
In step 1 we need to keep track of all sent cheques not all submitted ones. Not sure wether the method in step 2 is sufficient, there could also be withdrawals in-between.
SWAP should make sure that the user never ovepromises on his cheques.
If a peer ever writes a cheque that increases the total amount of uncashed cheques above the total amount of balance in the chequebook (assuming no hardDeposits), he risks that his chequebook fires a chequeBounced event and that peers will disconnect (?) from his.
Proposed solution:
The text was updated successfully, but these errors were encountered: