Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix minor spelling and grammar issues #3

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Fix minor spelling and grammar issues #3

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/source/ledger-rules/dynamic-permissions.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
Dynamic permissions
===================

Openchain supports an implicit permission layout through :ref:`P2PKH accounts <p2pkh-accounts>` (``/p2pkh/<address>/``) and :ref:`thrid party issuance accounts <third-party-issuance-accounts>` (``/asset/p2pkh/<address>/``). It is also possible to dynamically define permissions by submitting transactions modifying a special record: the ``acl`` record.
Openchain supports an implicit permission layout through :ref:`P2PKH accounts <p2pkh-accounts>` (``/p2pkh/<address>/``) and :ref:`third party issuance accounts <third-party-issuance-accounts>` (``/asset/p2pkh/<address>/``). It is also possible to dynamically define permissions by submitting transactions modifying a special record: the ``acl`` record.

Access Control Lists
--------------------
Expand Down Expand Up @@ -39,7 +39,7 @@ The schema of the JSON file that the record contains is the following:
}
]

The contents is an array containing all the applicable permissions. When the ``acl`` record does not exist, this is equivalent to having an empty array.
The content is an array containing all the applicable permissions. When the ``acl`` record does not exist, this is equivalent to having an empty array.

The meaning of the fields within a permission object are the following:

Expand All @@ -48,7 +48,7 @@ The meaning of the fields within a permission object are the following:
- ``addresses``: An array of strings representing the addresses for which signatures are expected.
- ``required``: The number of required signatures from the ``addresses`` array. If the ``addresses`` array contains 3 addresses, and ``required`` is set to 2, that means that for the permission to apply, at least 2 signatures from the 3 addresses specified must be present. This is known as a n-of-m multi-signature scheme.

- ``recursive``: (Default: true) A boolean indicating whether the permission applies recursively to the sub accounts.
- ``recursive``: (Default: true) A boolean indicating whether the permission applies recursively to the sub-accounts.

.. note:: With recursion, lower level permissions overrule higher level permissions.

Expand Down Expand Up @@ -87,4 +87,4 @@ A closed loop ledger can be created by denying ``account_modify`` by default, an
``data_modify``
~~~~~~~~~~~~~~~

This permission is required to modify a ``DATA`` record.
This permission is required to modify a ``DATA`` record.