Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How can I identify different senders using keysend in Fiber? #278

Open
Flouse opened this issue Oct 23, 2024 · 3 comments
Open

How can I identify different senders using keysend in Fiber? #278

Flouse opened this issue Oct 23, 2024 · 3 comments

Comments

@Flouse
Copy link
Contributor

Flouse commented Oct 23, 2024

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

  • target_pubkey
  • amount
  • custom ID (not currently supported?)
@Flouse 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
@chenyukang
Copy link
Collaborator

I plan to add custom_records for a payment:
chenyukang@7465e56

do you think is it enough?

@chenyukang
Copy link
Collaborator

  • 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.

@Flouse
Copy link
Contributor Author

Flouse commented Oct 29, 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.

Looks great!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants