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
Are there any optional parameters or best practices when using keysend that could help distinguish between different senders?
Example Inputs for Fiber RPC Method send_payment
target_pubkey
amount
custom ID (not currently supported?)
The text was updated successfully, but these errors were encountered:
Flouse
changed the title
How to add some additional info into a keysend fiber payment
How can I identify different senders using keysend in Fiber?
Oct 23, 2024
custom_records (type: Option<Vec<(u32, Vec<u8>)>): Custom records to attach to the payment. The first element of the tuple is the record type, the second element is the base64 encoded bytes.
custom_records (type: Option<Vec<(u32, Vec<u8>)>): Custom records to attach to the payment. The first element of the tuple is the record type, the second element is the base64 encoded bytes.
docs: https://github.com/nervosnetwork/fiber/blob/main/src/rpc/README.md#method-send_payment
Question
Are there any optional parameters or best practices when using keysend that could help distinguish between different senders?
Example Inputs for Fiber RPC Method
send_payment
The text was updated successfully, but these errors were encountered: