digital-asset/daml
1
1
Fork 0
mirror of https://github.com/digital-asset/daml.git synced 2024-09-20 01:07:18 +03:00
Code Issues Projects Releases Wiki Activity

Allow multiple requesters for a commit in the ledger model (#8471)

Browse Source 
CHANGELOG_BEGIN
- Adjust the ledger model to account for multi-party submissions
CHANGELOG_END
This commit is contained in:
Ognjen Maric 2021-01-12 12:49:52 +01:00 committed by GitHub
parent b32177cb0b
commit 7171cb38fa
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/source/concepts/ledger-model/ledger-structure.rst
View File

@ -203,8 +203,7 @@ The transaction structure records the contents of the
changes, but not *who requested them*. This information is added by the notion
of a **commit**: a transaction paired with the parties that
requested it, called the **requesters** of the commit.
In the ledger model, a commit is allowed to have multiple requesters,
although the current Daml Ledger API offers the request functionality only to individual parties.
A commit may have one or more requesters.
Given a commit `(p, tx)` with transaction `tx = act`:sub:`1`\ `, …, act`:sub:`n`, every `act`:sub:`i` is
called a **top-level action** of the commit. A **ledger** is a sequence of
commits. A top-level action of any ledger commit is also a top-level action of
@ -214,7 +213,7 @@ The following EBNF grammar summarizes the structure of commits and ledgers:
::
Commit ::= party Transaction
Commit ::= party+ Transaction
Ledger ::= Commit*
A Daml ledger thus represents the full history of all actions taken by