mirror of
https://github.com/XRPLF/xrpl-dev-portal.git
synced 2025-11-20 11:45:50 +00:00
Re-add some unintentionally-removed not-enabled markers
This commit is contained in:
@@ -10,7 +10,7 @@ There are two circumstances that could lead to transaction malleability:
|
||||
|
||||
**Use the [tfFullyCanonicalSig flag](transaction-common-fields.html#global-flags)** to guarantee that a transaction is not malleable in this way. Although transactions [signed with Ed25519 keys](cryptographic-keys.html#signing-algorithms) are not vulnerable to this problem, **there is no downside** to using this flag on _all_ transactions.
|
||||
|
||||
If the [RequireFullyCanonicalSig amendment][] is enabled, all transactions are protected against malleability regardless of the tfFullyCanonicalSig flag.
|
||||
If the [RequireFullyCanonicalSig amendment][] :not_enabled: is enabled, all transactions are protected against malleability regardless of the tfFullyCanonicalSig flag.
|
||||
|
||||
2. The transaction is [multi-signed](multi-signing.html) and has more signatures than necessary. Even if the transaction originally did not have more signatures than necessary, it could be malleable if an authorized signer provides an additional signature.
|
||||
|
||||
|
||||
@@ -12,7 +12,7 @@ The types of objects that may appear in the `account_objects` response for an ac
|
||||
- [PayChannel objects](paychannel.html) for open payment channels.
|
||||
- [Check objects](check.html) for pending Checks.
|
||||
- [DepositPreauth objects](depositpreauth-object.html) for deposit preauthorizations. [New in: rippled 1.1.0][]
|
||||
- [Ticket objects](known-amendments.html#tickets) for tickets.
|
||||
- [Ticket objects](known-amendments.html#tickets) :not_enabled: for tickets.
|
||||
|
||||
|
||||
## Request Format
|
||||
|
||||
Reference in New Issue
Block a user