You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The RN SDK provides a PaymentReferenceCalculator calculates the "short" payment reference but not the "long" payment reference.
Also, the short and long payment Reference aren't in the docs.
Proposed Solution
Add a function to the PaymentReferenceCalculator that calculates the "long" payment reference.
Add documentation about what is short and long payment reference with links to the calcualtor.
Details
The payment reference input to transferFromWithReferenceAndFee() is 8-byte "short" payment reference (see attached image)
The payment reference output from the TransferWithReferenceAndFee event is the "long" keccak256 hash of the 8-byte short payment reference (see attached image)
The payments-subgraph indexes the "long" keccak256 hash of the 8-byte short payment reference
If someone gets the "long" payment reference from the payments-subgraph, there's no way to figure out the corresponding "short" payment reference. I think this is okay 🙆♀️
Problem(s)
The RN SDK provides a PaymentReferenceCalculator calculates the "short" payment reference but not the "long" payment reference.
Also, the short and long payment Reference aren't in the docs.
Proposed Solution
Details
Additional Detail
Reference
transferFromWithReferenceAndFee()
TransferWithReferenceAndFee
eventScreenshots
The text was updated successfully, but these errors were encountered: