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.

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

fix: more updates for XLS-70 #250

Open
wants to merge 6 commits into
base: master
Choose a base branch
from
Open

Conversation

mvadari
Copy link
Collaborator

@mvadari mvadari commented Nov 11, 2024

Title says most of it, also some renames to fix numbers + remove the d draft indicator for specs that are soon to be up for voting.

@tequdev tequdev mentioned this pull request Nov 13, 2024
@tequdev
Copy link
Contributor

tequdev commented Nov 13, 2024

It'd be good if this PR could fix what I'm pointing out here
#211


#### 2.1.2. `Flags`
| Flag Name | Flag Value |
|-----------|------------|
|`lsfAccepted`|`0x00010000`|

The `lsfAccepted` flag represents whether the subject of the credential has accepted the credential. If this flag is disabled, the issuer is responsible for this ledger entry's reserve; if the flag is enabled, the subject of the credential is responsible for the reserve instead. This flag is disabled by default, but is enabled as the result of a successful `CredentialAccept` transaction, or if the secondary signing flow is used to create the credential.
The `lsfAccepted` flag represents whether the subject of the credential has accepted the credential. If this flag is disabled, the issuer is responsible for this ledger entry's reserve; if the flag is enabled, the subject of the credential is responsible for the reserve instead. This flag is disabled by default, but is enabled as the result of a successful `CredentialAccept` transaction.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

disabled/enabled sounds inconvenient for flags. Generally flags are set/clear

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mDuo13 what's the norm for docs?

@@ -341,6 +340,7 @@ _Note: the transaction will succeed if (non-expired) credentials are included, b

* If a credential isn't valid, the transaction fails.
* If a credential is expired, the credential is deleted.
* If the transaction is pre-authorized (either via account or via credential), the transaction will succeed.

## 9. RPC: `deposit_authorized`
Copy link

@oleks-rip oleks-rip Dec 2, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add

  • ledger_entry changes (additional field authorized_credentials in deposit_preauth parameter)
  • account_objects / ledger_data changes (added credential as one of the values for type parameter)

@mvadari mvadari mentioned this pull request Dec 12, 2024
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants