Repository navigation
v11.26.0
-
Xrpl.Wallet.XrplSigningKey : IDisposablesigns with a private key held in abyte[]and clears it onDispose; signing afterwards throwsObjectDisposedException. It is built from the 33-byte key (new XrplSigningKey(ReadOnlySpan<byte>, masterAddress)) or from seed entropy (XrplSigningKey.FromEntropy), and itsSignoverloads (dictionary and typed, with and withoutSignatureRole) produce the same blob and hash asXrplWallet.Sign, through the same routing.XrplWalletsends every signature through one internalSignBytes, which this type supplies with the byte key. Issue #347 -
Xrpl.Keypairs.XrplKeypairstakes keys as bytes:Sign(ReadOnlySpan<byte> message, ReadOnlySpan<byte> privateKey),DerivePublicKey(ReadOnlySpan<byte> privateKey)andDeriveKeyBytes(ReadOnlySpan<byte> entropy, string algorithm), which derives the keys ofXrplWallet.FromEntropywithout encoding a seed string. The key is the 33-byte XRPL form,0xEDor0x00followed by 32 bytes, and a secp256k1 scalar of zero or not below the curve order is refused, so a cleared buffer never signs; the buffers these methods allocate for key material, the Ed25519 expanded key included, are cleared before they return. The secp256k1 scalar still passes through a BouncyCastleBigInteger, which cannot be cleared -
Tests:
TestUSigningKey -
Xrpl,Xrpl.AddressCodec,Xrpl.BinaryCodecandXrpl.Keypairsare 11.26.0.0 -
LedgerRules.FixCleanup3_5_0(defaulttrue) carries rippled 3.5.0'sfixCleanup3_5_0;LedgerRules.FromNodeAsyncreads it, and records whether the node lists the amendment at all, since rippled 3.5.0 treats it as enabled outside a transaction and 3.4.x does not have it. Under it:PaymentFlow, direct MPT payment (beforeMPTokensV2): the cost ismulRatio(amount, rate)rounded up, a cost that overflows exceeds anySendMax, and a partial payment deliversmulRatio(SendMax, 1/rate)rounded down,tecPATH_PARTIALwhen that is zero; an MPT sent between holders chargesaddTransferFee. rippled #8302. Tests:TestUMptDex.Pay_Direct_Fix350_RoundsTheCostUp,Pay_DirectPartial_Fix350_NeverChargesPastSendMax,Pay_DirectPartial_Fix350_NothingDeliveredIsPartialXrplQuality.CeilOut/CeilOutStrict: an XRP input beyond 10^17 drops is clamped to the offer's input instead of throwing; an overflow past 64 bits still throws. The out-of-range case throws the internalAmountRangeException, anOverflowException. rippled #8480XrplAmountMath.DivRound/DivRoundStrict: an MPT operand of any role goes throughNumber, withMPTokensV2or without;MulRoundis unchangedLoanOrigination.Compute: aLoanSetvalue field outside the asset's range (above 10^17 drops of XRP,maxMPTokenAmountof an MPT, an IOU exponent above 80) istecPRECISION_LOSS; without the amendment it istefEXCEPTION, as the node fails on it. rippled #8527VaultShares:WithdrawAssetsandRedeemSharesoverloads take thetransferRatethe withdrawal pays (0 or 1,000,000,000 for none), whichVaultShares.WithdrawalTransferRate(asset, account, destination, assetTransferRate, rules)works out (the asset's rate between two accounts that are neither the withdrawer nor the issuer, otherwise none). A withdrawal by amount burns shares for the amount plus the fee; one by shares delivers the payout less the fee,tecPRECISION_LOSSwhen that leaves nothing.VaultQuote.AssetsDeliveredis what the destination receives. rippled #8267- Tests:
TestUFixCleanup3_5_0.TestUAmountVectorsreplays its rippled 3.4.1 vectors with the amendment off
-
XrplAmountthrowsAmountRangeException(internal, derived fromOverflowException) for an XRP or MPT value out of range, where it threwOverflowExceptionitself -
Xrpl,Xrpl.AddressCodec,Xrpl.BinaryCodecandXrpl.Keypairscarry a readme (PackageReadmeFile):Xrplpacks the repositoryREADME.md, and each base package has its ownREADME.mdinBase/. TheCONTRIBUTING.mdandLICENSElinks of the repositoryREADME.mdare absolute, so they also work on nuget.org.