08:32:48 * in order to do `git commit ...` 08:32:48 git asks for an email and a name. 14:12:00 jberman: would you be interested in hopping on a quick call with the AirGap team next week? I think they just have some questions about the tech side of Monero 14:12:30 "We have had multiple AirGap community members approach us and inquire about AirGap supporting Monero. As AirGap and its components is completely open source we usually approach an entity in the ecosystem of a protocol that then helps fund the development and security review of the integration. Would be available for a call to discuss this as well as the potential implementation from a technical side, as we’re currently uncertain if this is even 14:12:30 feasible with AirGap’s two device approach." 14:15:29 https://airgap.it/ 14:16:01 It looks like they build the monerujo sidekick, but for many currencies 15:08:39 Only problem with unsigned transactions is theyre 'huge' .. 1 qr code can only hold 3kb. They would have to implement a 'scrolling qr scanner' into their app (one exists on github already atleast). Monerujo chose to transfer via bluetooth instead. The last time this was mentioned here moneromooo said that there was never an attempt to keep file sizes down so there would be some "easy wins" there. And i believe UkoeHB said that a new 15:08:39 protocol thats being worked on would have a small enough unsigned tx size to fit on a QR code so... They will probably 'wait' for a new protocol... OR a bounty crypto_grampy to reduce the file size of a qr code "so airgap" can easier support us.. 15:13:04 sgp_: 15:17:46 Thanks for the ping 16:46:15 vtnerd: I am confused what to do about this multisig status struct ( https://github.com/monero-project/monero/pull/7852#discussion_r762027864 ). Looking at `wallet2_api.h`, it doesn't `#include` anything except standard libraries... does this mean I can't include `multisig/multisig.h`? 17:44:55 dont you dare publish 17.3 within the next 2-3 hours. i want to sign it too 🥲 17:45:34 do i need to install the beaver ubuntu or can i run from usb stick? 17:48:02 monerobull[m]: it's won't be published before tomorrow but you can add your signatures after it's released 17:48:38 thats less cool though ;) 17:56:17 In which way are the gitian build signatures used ? Is there some automatic process which does something with them ? 17:56:27 * are the multiples gitian build 18:03:13 Trying to send to four different addresses at once, CLI responds with: "Error: transaction was not constructed" 18:11:31 Here is a paste of log level 2: https://paste.debian.net/hidden/25054bea/ 18:13:05 It is 0.17.2.3 with Trezor. 18:21:12 * monerobull[m] uploaded an image: (114KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/oRFTPjtuJXgvKIXNpulFtOOr/20211203_192031_2252203527063728054.jpg > 18:21:14 Linux is garbage 18:22:38 lol 18:22:57 You can compile on other OSs if you want, still using Docker 18:23:14 Why are you booting Linux just for this? 18:23:43 Because the guide said host os should be Ubuntu beaver 18:24:13 And I've never used docker before 18:24:26 Docker on windows is absolute cancer 18:24:28 f[m]1: did you send to multiple integrated addresses? 18:25:18 I think you can't send to both subaddresses and integrated address in one transaction 18:35:48 "Because the guide said host os..." <- > Gitian supports other container mechanisms too but if you have a Debian or Ubuntu-based host the steps can be greatly simplified. 18:35:52 https://github.com/monero-project/monero/blob/6a46f8c40ae069daf22e2bb5b7d72510c00e0eb4/contrib/gitian/DOCKRUN.md 18:36:02 Just run any normal Linux OS 18:36:12 Pop_OS! is very beginner friendly, and is Ubuntu-based. 18:37:25 selsta: Integrated, as in the (old?) format that's longer than a normal address? 18:37:46 integrated as in 106 characters long 18:39:01 No. Haven't seen those in a while. It's 3 main addresses (4..) and one sub (8..). 18:40:24 95 chars 18:41:38 I got Ubuntu to run. It doesn't connect to the internet. 18:50:39 f[m]1: did you specify an external payment id? 18:52:08 "Destinations have to have exactly one output to support encrypted payment ids" 18:52:18 that's the relevant error message 18:54:32 Where would the enc payment id have come from? 18:56:09 I did the gitian build on Debian, and it worked well 19:00:54 Ok, I found out which address is at fault. 19:00:55 Is there anything that indicates I am looking at such an address or would I have to run it through something like `integrated_address` to know? 19:03:42 "I did the gitian build on Debian..." <- I'll try this now. Ubuntu is bloated garbage 19:14:52 Why doesn't debian have a setting for live boot... 19:23:24 f[m]1: integrated addresses are longer 19:32:16 Why does the docker version require linux 19:32:53 This is stupid, i wasted 2 hours and got nowhere :( 19:33:14 * moneromooo feels envious 19:35:24 Last try with mint now 19:38:50 easiest to build from a VM 20:05:30 I'm not having a great time 20:06:14 Btw next dev meeting this or next week? 20:37:07 selsta: I know they were a couple of upgrades ago, but they don't appear to be anymore. 20:43:26 selsta: Oh, my bad. You're right. When I checked the length, I used the data from the log, which had the payment ID already extracted. 20:51:28 When creating a PR, i disable "allow edits by maintainers" right? 20:52:21 Up to you, any edits would be public and visible, so it's fine either way 20:53:21 I think adding my pubkey worked? 20:57:16 Will be signing off. Thanks for the help! 21:00:24 What is meant by start a new shell with your new group membership 21:02:26 Just run the last command, it's just explaining what that does: `su $USER` 21:02:58 With user literally being that or my Linux user? Or GitHub? 21:03:57 Why don't we take this to DM, don't want to clutter this chat anymore. 23:00:40 'Error: No such container: gitian-target 23:00:41 Traceback (most recent call last): 23:00:41     6: from bin/gbuild:313:in `
' 23:00:42     5: from bin/gbuild:313:in `each' 23:00:42     4: from bin/gbuild:315:in `block in
' 23:00:43     3: from bin/gbuild:315:in `each' 23:00:43     2: from bin/gbuild:320:in `block (2 levels) in
' 23:00:44     1: from bin/gbuild:76:in `build_one_configuration' 23:00:44 bin/gbuild:23:in `system!': failed to run on-target true (RuntimeError) 23:00:45 Traceback (most recent call last): 23:00:45   File "./gitian-build.py", line 211, in 23:00:46     main() 23:00:46   File "./gitian-build.py", line 201, in main 23:00:47     build() 23:00:47   File "./gitian-build.py", line 99, in build 23:00:48     rebuild() 23:00:48   File "./gitian-build.py", line 71, in rebuild 23:00:49     subprocess.check_call(['bin/gbuild', '-j', args.jobs, '-m', args.memory, '--commit', 'monero='+args.commit, '--url', 'monero='+args.url, infile]) 23:00:56 oii don't paste in in chat 23:01:18 sorry, is the bridge down? 23:01:52 just real slow i guess 23:02:43 can someone help me figure out why the docker script failed? 23:16:04 * monerobull[m] uploaded an image: (95KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/IWHnAvjraeMlXsfziLxxfkPK/image.png > 23:16:10 scoobybejesus: im stuck on this right now 23:16:27 but it looks kinda done, im not sure? 23:17:03 looks good. not done. let it sit. or start over with more cores and cpu 23:18:11 Building takes a while (especially if you don't have many cores and/or much ram) 23:20:34 scoobybejesus: I restarted with your core settings. It's currently at the same point as in the screenshot 23:21:18 open up another terminal window and open htop and you'll see it's crunching along 23:24:28 Yeah i can see that 23:24:36 Thanks 23:44:44 "jberman: would you be interested..." <- Don't know how helpful I'll be in this conversation, it might be more useful to have someone who has more intimate knowledge of offline signing or hardware wallet integration, but happy to chat :) I'll do some digging on it beforehand too 23:49:15 > as we’re currently uncertain if this is even feasible with AirGap’s two device approach. 23:49:15 But ya as discussed above it definitely should be feasible 23:58:23 Hot view-only wallet scans for received outputs and prepares tx's for signing -> 2nd offline signing wallet signs tx's and passes them to hot wallet -> hot wallet broadcasts tx and saves key image locally (needs key images to calculate balance) 23:58:51 Would imagine the flow would be something like that. There might be UX challenges they'll need to deal with different from other currencies because the view-only wallet can't determine spent outputs and needs the key images to do so, and stuff I may not be seeing like that unsigned tx's are huge like mentioned above too