ARCHIVE/xrpl-dev-portal
1
0
Fork 0
mirror of https://github.com/XRPLF/xrpl-dev-portal.git synced 2025-11-27 23:25:51 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update rippled repo URL

Browse Source 
Fix #2070.
This commit is contained in:
mDuo13
2023-09-15 15:21:58 -07:00
parent 47089b12cf
commit f130a7bc60
251 changed files with 471 additions and 471 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
content/resources/contribute-code/contribute-code.md
View File

@@ -16,7 +16,7 @@ The software that powers the XRP Ledger is open-source, so anyone can download,
| XRP Ledger Source Code | |
|:-----------------------|:----------------------------------------------------|
| Repository | <https://github.com/XRPLF/rippled> |
| License | [Multiple; ISC (permissive)](https://github.com/ripple/rippled/blob/develop/LICENSE.md) |
| License | [Multiple; ISC (permissive)](https://github.com/XRPLF/rippled/blob/develop/LICENSE.md) |
| Programming Language | C++ |
If you're not sure where to start, Dev Null Productions provides a detailed and thorough [**Source Code Guide**](https://xrpintel.com/source) that describes the structure and functions of the core XRP Ledger server (`rippled`) implementation.

2
content/resources/known-amendments.ja.md
View File

@@ -1140,7 +1140,7 @@ XRP Ledgerプロトコルの署名要件を変更し、いかなる場合にも
この修正により、単独署名のトランザクションは展性になりません。(署名者が必要以上の署名を提供した場合、[マルチシグのトランザクションはまだ展性であるかもしれません](transaction-malleability.html#マルチシグの展性))。すべてのトランザクションは、tfFullyCanonicalSigフラグに関係なく、署名の完全な正規の形式を使用する必要があります。完全に正規化された署名を作成しない署名ユーティリティはサポートされていません。Ripple社が提供するすべての署名ユーティリティは、少なくとも2014年以降、完全に正規化された署名のみを提供するようになっています。
詳しくは、[`rippled` issue #3042](https://github.com/ripple/rippled/issues/3042)を参照してください。
詳しくは、[`rippled` issue #3042](https://github.com/XRPLF/rippled/issues/3042)を参照してください。
### SHAMapV2

2
content/resources/known-amendments.md
View File

@@ -1140,7 +1140,7 @@ Without this amendment, a transaction is malleable if it uses a secp256k1 signat
With this amendment, no single-signed transactions are malleable. ([Multi-signed transactions may still be malleable](transaction-malleability.html#malleability-with-multi-signatures) if signers provide more signatures than are necessary.) All transactions must use the fully canonical form of the signature, regardless of the `tfFullyCanonicalSig` flag. Signing utilities that do not create fully canonical signatures are not supported. All of Ripple's signing utilities have been providing fully-canonical signatures exclusively since at least 2014.
For more information, see [`rippled` issue #3042](https://github.com/ripple/rippled/issues/3042).
For more information, see [`rippled` issue #3042](https://github.com/XRPLF/rippled/issues/3042).
### SHAMapV2