11:26:48 Another merchant accepting Monero. https://aktive-sim-karte.de/ 11:28:57 If you need an anonymous sim card. I dont know how it is in your country but in the EU the mobile phone number seems to be the new unique identifier for a person on the internet. madatory id required for buying a sim card. 11:30:00 Hard to create a free anonymous e-mail account without phone number now a days. 11:30:42 Of course, consumer unit. For your own safety. 11:31:08 Of course. 11:31:12 Please report any use of this criminal site to the consumer protection unit tactical team. 11:31:38 XD 14:30:21 Hello all, 14:30:40 Anyone have an example of a cURL command using /get_outs 14:30:40 for daemon rpc? 14:31:13 I am finding the documentation as written confusing: https://web.getmonero.org/resources/developer-guides/daemon-rpc.html#get_outs 14:32:31 This call is for conversion between an output index and the actual pubkey/the transaction which it's from right? 14:33:19 If it's a ringCT, output, the amounts will be zero for non-coinbase txns? 14:34:58 The description just says "Get outputs. 14:34:58 " but I assume that's what it's for based on the outputs/inputs of the call 14:35:14 curl -v -k -X POST http://127.0.0.1:28081/get_outs -d '{"outputs":[{"amount":1000000000000,"index":0}]}' -H 'Content-Type: application/json' 14:35:38 > < Adreik> If it's a ringCT, output, the amounts will be zero for non-coinbase txns? 14:35:41 Yes 14:36:03 Thanks, 14:36:04 (also for v2 coinbase outs) 14:36:48 That could also be done for denominated outs, I had a patch for this but buggy and I never went back to it. 14:37:43 so is index there not global index? 14:37:55 Because otherwise it seems amount should not be mandatory 14:39:07 Wait, nevermind it doesn't also ask for a txn hash or anything like that. But surely global index should be sufficient for identifying the output uniquely? 14:39:15 It is global index. Amount is needed because those are per amount. 14:40:36 What do you mean by that? Don't outputs with amounts known also have distinct output indices? 14:43:05 That question is not clear. 14:44:28 Documentation says: 14:44:36 Get outputs. 14:44:36 Alias: None. 14:44:37 Inputs: 14:44:37 outputs array of get_outputs_out structure as follows: 14:44:38 amount - unsigned int; 14:44:38 index - unsigned int; 14:46:01 each output has a single global index; the global index is a unique identifier of the output. So for a call to find information on said output, why is knowing the amount also necessary? 14:46:45 Amount is needed because those are per amount. 14:47:00 Also get_outputs_out doesn't seem to exist? 14:47:01 Like, 4 is the fifth output of that amount in blockchain order. 14:47:51 So if an output has a different amount it might have the same index number 14:48:49 e.g. https://xmrchain.net/tx/a898e407e3427200f8356e1d33d08023aa1440e01b2c2ce2fa9dfd5b7fc89c88 <-- has an "amount idx", and this is what that is referring to? 14:49:19 Yes, probably, resp. 14:53:35 does this mean that you can enter any number smaller than the total amount of post-ringCT outputs into that field, enter a value of "0" for the amount and it will map to a ringCT output? [0,0] is a valid output? 14:53:46 Actually I will try and check this myself 14:55:23 Yes (if by "post-ringCT output" you mean "ringCT output, including v2 coinbase outouts"). 15:02:43 Seems like /get_outs should not be returning transaction hashes of "0000000000000000000000000000000000000000000000000000000000000000" 15:04:02 Result of using value of 0 for amount and index from 0 to 9: https://pastebin.com/ch6gwdAA 15:06:27 Are you sure you set the "get me the txid" flag in the request ? 15:07:19 Said flag is not mentioned in the documentation under that method? 15:07:37 But that would explain it 15:08:47 Documentation mentions a "outputs array of *get_outputs_out* structure as follows: 15:08:47 " which does not seem to be mentioned there or in the wallet rpc docs either 15:09:23 I don't know. You can check faster than me. 15:13:35 Well I can't find what "get_outputs_out" is referring to. What does the optional txid flag look like? 15:15:27 But yeah, it definitely seems to me at least that the documentation needs a good refresh. I would offer to put in some time for it but all I know is what's written down there so I don't think that would be very helpful 15:16:31 Looking now, it's "get_txid". 15:17:20 Yep, that works. 15:17:29 The documentation is a losing proposition. I doubt it says much beyond paraphrasing the structures, and it's always going to get out of date. 15:17:50 :( 15:19:33 Anyway, thanks and good evening (or whatever for your timezone)