Yes, I think the two party commit example really illustrates the capabilities of the system.
Two-Party Commit: Using DataLayer offer files and proofs of inclusion, two people can coordinate a simultaneous (“atomic”) update of their respective data:
- Alice proposes an update, creating an offer file that includes proofs of inclusion of the added and changed rows she proposes to make in her own DataLayer tables and the rows she requests that Bob add or change in his tables.
- She saves the offer file and sends it to Bob.
- Bob opens the offer file and reviews the proposed changes to Alice’s DataLayer tables and the changes she requests of his DataLayer tables.
- If the changes are acceptable, Bob attaches an update to his DataLayer tables that includes at least the changes requested by Alice, and submits the completed offer to the blockchain.
- Both Alice’s and Bob’s DataLayer tables are simultaneously updated. If Bob had not completed the offer, neither table would be updated. Alice could have canceled the offer by updating her singleton, even if the update did not change the data.
D:L is really an excellent concept here for a lot of use cases that a public blockchain can accel at involved especially with transparency and accountability. Pretty interesting.
