-
Notifications
You must be signed in to change notification settings - Fork 912
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
listening-for-payments-cli doesn't explain how to distinguish customers #302
Comments
Hello @benapetr. Yes, you need to create one new address for every order (not customers) otherwise you were right you can not distinguish the transactions. There are different ways how to generate many addresses and this should be definitely shown in the portal as well. |
I think we can be a bit careful about amount of details on how HD wallets work, mixing with this page (maybe a seperate page can be linked at top about wallet basics on BIP32/39/44 schemes for actual example on derivations itself using cardano-addresses as an example?). |
yes I don't mind if it's a separate page, but I think this should be definitely covered, because right now for someone who never implemented anything similar, it's not easy to understand how to implement fully operational "merchant" system, where you can track individual orders and manage them all under one wallet with multiple addresses. For example one thing that is extremely unclear to me right now is how to actually USE the secondary addresses, when I follow the cardano-cli commands in example and sign the transaction that has --tx-in UTXO from secondary address, I get
so it seems that secondary addresses need dedicated signing keys? even if they belong to same wallet? if yes, how to generate them? |
I have the same problem |
For starters , what might be helpful is checking out HD Wallets and how derivation works: The Root key above can be derived from cardano-addresses CLI (see README ). Coming to the point, I see that there was already a place holder link as a note, the destination page needs to cover the above , so only the destination page needs to be created 🙂 . We would love to see community to step up and compile the instructions to be included using above, rather than us depending on same two-three individuals creating contents (as 90% of get-started pages is initiated by Tommy/Clark) - before others add corrections/updates , if we really want to make the concept of developer-portal fully successful. |
@katomm I read your https://developers.cardano.org/docs/integrate-cardano/listening-for-payments-cli but there is major issue in that flow - you can't distinguish between individual customers in that model, you can only track what is current balance of that one address. This would work if you only ever had 1 customer.
How would the proper flow look? Each customer has dedicated address? If yes, then how would you generate a secondary address for the same wallet? And how would you send ADA out of it using cardano-cli? I was experimenting with that but ultimately failed every time - https://forum.cardano.org/t/how-to-properly-sign-transaction-from-non-base-address/74462
It would be of great help if that page could be expanded to cover a fully functional model instead of this trivial example that assumes only 1 customer ever. Thanks!
The text was updated successfully, but these errors were encountered: