12:09:05 <nevvton[m]> #36c3 #CDC Critical Decentralisation Cluster - Program for DAY 03 - please visit: https://www.youtube.com/watch?v=Krftz3Y39sg for livestreamed content and http://decentral.community for full sheduled program ! - Events will be streamed and recorded.
12:09:05 <nevvton[m]> @monero @riat_at
12:09:05 <nevvton[m]>  #monero - #c36c3 C3 , LEIPZIG 1/2
12:09:06 <LobsterMan> YouTube Title: Day 3: Critical Decentralisation Cluster (36c3) Views: 0 Length: Uploaded: 2019-12-29 User: Monero Community Workgroup Likes: 0 Dislikes: 0
19:37:01 <charolastra> isn't the idea of the block height parameter of get_bulk_payments() to not display transactions before that block?
19:37:48 <moneromooo> The idea of the block height parameter of get_bulk_payments() to not display transactions before that block. It may be off by one though.
19:38:56 <charolastra> then why do i get "block_height": 610 payments when at blockheight of 1200?
19:39:33 <moneromooo> I dont know. File a bug if you're sure you're not doing things wrong.
19:40:07 <moneromooo> Include the JSON you sent.
19:40:53 <charolastra> just playing around with the PHP intergration. wanting to make sure i get the concept
19:45:12 <Hail_Spacecake> question about the official monero gui wallet
19:45:17 <Hail_Spacecake> I am trying to send a transaction
19:45:30 <asymptotically> trying to spend your monero? that's crazy talk!
19:45:38 <Hail_Spacecake> and I am realizing that the send screen doesnt have any options to say whether I am doing a shielded or transparent transaction
19:45:55 <asymptotically> there are no shielded or transactions, just transactions
19:46:02 <asymptotically> you might be thinking of zcash
19:46:29 <Hail_Spacecake> shit am I?
19:46:32 <Hail_Spacecake> damnit, yeah
19:47:08 <Hail_Spacecake> right, monero has the thing to optionally add some kind of key to make the transaction visible
19:47:32 <Hail_Spacecake> which I don't want to do in this case, although I am not sure where I'd do that on that screen either
19:48:26 <charolastra> moneromooo: the library redeclares an empty configuration array right after the $min_block_height .... works now :)
19:49:37 <charolastra> Hail_Spacecake: i think it's a view key for the wallet. not per transaction
19:50:12 <moneromooo> A random key is generated for every tx. You can use this key later on to prove things.
19:52:48 <asymptotically> Hail_Spacecake: you can do that after https://www.monero.how/tutorial-how-to-prove-payment - although i'm not sure how you do that in the GUI
20:20:50 <Mochi101> I can't figure out how to create an integrated address using my own payment id
20:21:07 <Mochi101> Is this still possible with the wallet CLI?
20:22:27 <moneromooo> integrated_address abcdefabcdef00
20:23:23 <moneromooo> If it doesn't work, I'll fix.
20:24:37 <Mochi101> Should work the same on Stagenet right?
20:24:49 <moneromooo> Yes.
20:25:00 <Mochi101> [wallet 5AGTfQ]: integrated_address abcdefabcdef00
20:25:01 <Mochi101> Error: failed to parse payment ID or address
20:25:18 <Mochi101> Is there a length limit to payment ID?
20:25:38 <Mochi101> Like... could I use a SHA256 hash there?
20:25:56 <moneromooo> 8 bytes, so 16 hex digigs.
20:26:11 <moneromooo> Oh, I put 12. Sorry. Add 4.
20:26:23 <moneromooo> No, add 2 -_-
20:27:06 <Mochi101> oh that works
20:27:09 <Mochi101> :)
20:27:28 <Mochi101> Man... how can I use that now...
20:27:49 <Mochi101> anything that creates a 16 digit hash?
20:28:25 <asymptotically> take the first 8 bytes of your favourite hash :D
20:28:30 <moneromooo> Sure. sha256sum | cut -b 1-16
20:29:14 * Mochi101 sighs
20:31:37 <Mochi101> I want to be able to create a list... create a hash from it and then use it as a payment id as proof
20:32:22 <asymptotically> proof of what?
20:32:33 <Mochi101> proof that the list isn't altered
20:33:10 <moneromooo> ENEEDMOREDETAILS
20:33:34 <Mochi101> I want to export guesses from my db 5 blocks before a draw and then send a tx using the hash of the list to the Monero blockchain
20:33:54 <Mochi101> the hash as a payment id
20:34:39 <asymptotically> but how will people know that you haven't left one out? or that you actually use the list that you've hashed?
20:35:04 <Mochi101> because they'll be able to hash the list themselves
20:36:48 <Mochi101> I guess I could just use the first 16 characters but that makes things more complocated
20:37:20 <Mochi101> probably it's already too complicated
20:40:58 <asymptotically> are you sure the list is worth it? people still have to trust you, this doesn't really change anything
20:42:38 <Mochi101> probably doesn't matter hey... maybe I'm thinking about this wrong or have the wrong idea in my head... I just tried it and didn't see it on the block explorer
20:43:45 <asymptotically> the 64 bit payment ids get encrypted
20:43:46 <asymptotically> i think
20:44:15 <moneromooo> It does.
20:45:06 <asymptotically> if you want to timestamp something, you can just use opentimestamps ^^
20:45:46 <Mochi101> moneromooo, so there'd be no way really to get the payment id back here? integrated_address abcdefabcdef00ad
20:46:05 <asymptotically> although i don't think it's worth it. using the block hashes for random numbers is nice because it shows you aren't messing with them. doing this doesn't really help anyone, screwing with payments is already visible (people will wonder where their reward is)
21:01:08 <moneromooo> The recipient can.
21:02:15 <moneromooo> Alice gives integrated address to Bob using payment id 42. Bob sends Alice 1 monero using this. 42 does not appear on the chain. Alice receives tx, finds payment id. Alice decrypts it, sees 42. Nobody else can decrypt it. Bob knows it because it was in the clear when he got the integrated addres.s
21:06:02 <Mochi101> Thank you. All is clear now.
21:06:11 <Mochi101> I was mistaken on how that worked.
21:07:30 <Mochi101> Privacy comes at a cost.
22:30:09 <charolastra> how should accounting of different customers be handled? creating individual accounts sounds like overkill. should each customer get a seperate subaddress?
22:34:50 <Mochi101> charolastra, seems that's the way to go right now... really depends on use case though.
22:35:05 <Mochi101> integrated addresses are still a thing
22:36:34 <asymptotically> does hitbtc still do something weird like manually generate a new private spend key for each user?
22:37:46 <charolastra> the first part of integrated addresses seems to stay the same. they could know they are paying the same person
22:39:33 <asymptotically> yeah an integrated address is just a normal address with a different byte at the front and some extra junk on the end
22:40:04 <asymptotically> they didn't use that though, or maybe i'm just imagining this
22:46:05 <Mochi101> You're so imaginary asymptotically
22:47:25 <asymptotically> do i not at least have a small real part? :(
22:48:16 <moneromooo> As close to 0 as you can get without being 0.
22:48:33 <Mochi101> You may very well have, but I cannot know that with certainty.
22:49:13 <asymptotically> wow, first imaginary and now irrational. i can't handle all of this cyberbullying
22:50:14 <moneromooo> Maybe we should bully fractionally less, it's only natural.
22:51:31 <Mochi101> I can't deal with fractions this late at night though moneromooo
22:52:34 <moneromooo> Stop being fractious. It's prime time! Make it count!
22:55:15 <Mochi101> :D