Contingent Transactions
Contingent Transactions are transactions in which the sender has to satisfy requirements defined by the recipient. The recipient can be a smart contract. Based on the data a user holds in his zkKYC he or she can prove satisfying those requirements while the ZKP hides personal identity to stay private. For example if the recipient is a wallet account receiving funds the recipient can choose to accept funds only from legit sources. This feature is implemented in a blockchain node which is checking ERC-20 transactions. It calculates reputation scores according to the function defined by the recipient in the RRC. Only if the sender has a high enough score the transaction can succeed. The networkβs contingent transactions primitive extends the RRC by using its outputs to establish dynamic transaction rejection and acceptance rules. It adds depth to interaction rulesets, allowing users to incorporate unique interactions into their contracts. These programmable transactions enable meritocratic interactions through web3 footprints, compliant liquidity pools via zkKYC, and generally allow DApps to reflect the diverse nature of accounts on the Galactica Network. The concept of contingent transactions is also explained in the Whitepaper.
Last updated