03:18:49 <starracer> hello
12:16:02 <m-relay> <f​ineopal:nope.chat> Is there a way to get_transfer of an address based on label?
12:16:50 <m-relay> <f​ineopal:nope.chat> Or what's the idiomatic way of detecting payment of an account's sub address?
12:21:47 <m-relay> <o​frnxmr:xmr.mx> https://docs.getmonero.org/rpc-library/wallet-rpc/#incoming_transfers ?
12:22:10 <m-relay> <o​frnxmr:xmr.mx> https://docs.getmonero.org/rpc-library/wallet-rpc/#get_balance ?
12:22:43 <m-relay> <f​ineopal:nope.chat> I don't see a label input in both of these methods.
12:23:40 <m-relay> <o​frnxmr:xmr.mx> Use the subaddress index
12:24:34 <m-relay> <f​ineopal:nope.chat> Currently, I am following this flow: create_address (with label) -> query with get_address (get subaddress index from label) -> do periodic get_transfers from the index.
12:24:46 <m-relay> <f​ineopal:nope.chat> Yeah.
12:25:08 <m-relay> <f​ineopal:nope.chat> Just wondering if this is a reasonable way.
12:25:56 <m-relay> <f​ineopal:nope.chat> Currently, I am following this flow: create\_address a subaddress (with label) -> query with get\_address (get subaddress index from label) -> do periodic get\_transfers from the index.
12:26:46 <m-relay> <o​frnxmr:xmr.mx> You can use also use tx-notify
14:40:34 <ruidx> fineopal: you can track payments with payment_id, it's basically what you are looking for in terms of "get transfer by label" but it creates `integrated address` and it's an old way to receive payments, more modern approach is to use subaddresses and track them by major and minor indices (account_index and subaddress_index)
18:30:26 <m-relay> <f​ineopal:nope.chat> Yeah, I settled on using subaddress indices. Thanks.