00:37:20 <Franck[m]> Ok I confirmed using monero-gui that the subaddress used by changenow is correct. Waiting for more scan :]
00:37:57 <selsta> Franck[m]: afaik monerod node runs on a raspberry
00:38:09 <selsta> not sure if it has enough resources for both bitcoin and monero
00:38:49 <Franck[m]> It seems that monerod is the one consuming most resources so if it runs, it should be fine.
01:06:12 <gingeropolous> Franck[m], once initial sync is done it should be less resource intensive
01:06:29 <gingeropolous> it would actually be cool if you could post some kind of pic showing it running both
01:07:08 <Franck[m]> I am at `2020-11-13 01:06:10.967 [P2P1]  INFO    global  src/cryptonote_protocol/cryptonote_protocol_handler.inl:1599    Synced 1446532/2229370 (64%, 782838 left, 3% of total synced, estimated 2.0 days left)`
01:08:33 <gingeropolous> thats around where it gets slow
01:09:54 <Franck[m]> https://imgur.com/a/9MvqpJ8
01:11:04 <Franck[m]> The CPU is not even 100%
01:11:07 <Franck[m]> I guess it's the ram and disk
01:15:46 <gingeropolous> fluffypony, ^
01:27:18 <hyc> thanks jtgrassie
01:32:26 <jtgrassie> most welcome
08:59:43 <tibertius> anybody have experience using bisq?
09:05:27 <Franck[m]> If you are interested in providing liquidity please keep a close look to the atomic swap project
09:10:27 <tibertius> which project is this? i am unfamiliar
09:16:48 <Franck[m]> https://ccs.getmonero.org/proposals/h4sh3d-atomic-swap-implementation.html
09:24:31 <Franck[m]> IRC channel is #monero-swap. We (COMIT) are also working on this, matrix channel is #comit-monero:matrix.org .
09:29:08 <tibertius> that's really neat
09:43:21 <endor00[m]> I get that people are excited about atomic swaps, but it's still gonna be a (long) while before atomic swaps go live
09:52:08 <Franck[m]> <endor00[m] "I get that people are excited ab"> How long do you reckon?
09:55:42 <endor00[m]> I don't know for sure, but the project started last month and the proposed timeline is 7 months. Hyping people up so much now that we are in the wait-and-see phase might be counterproductive imo
09:57:00 <endor00[m]> 7 months is an eternity in crypto world - and that's assuming there are no delays nor problems of any kind
10:17:15 <kayabaNerve> endor00[m]: I mean, there's already 2 PoCs. They're just PoCs.
10:17:47 <kayabaNerve> They COULD be hacked into a GUI/reviewed by a couple other devs in a week or two. They just wouldn't benefit the space. From UX/insecurities...
10:18:20 <kayabaNerve> The time is do it properly, and create the relevant infra. That said, COMIT will have a different approach than the team funded by the CCS, so it'll be interesting to see how it works out :)
10:18:51 <endor00[m]> <kayabaNerve "They COULD be hacked into a GUI/"> That would be a terrible idea - especially putting them in the official wallet, which is supposed to be a stable reference design
10:18:58 <sech1> Wait, there's two teams working on atomic swaps now?
10:19:18 <kayabaNerve> Exactly
10:19:27 <kayabaNerve> sech1: Depends on how you count
10:19:27 <endor00[m]> There is such a thing as 'releasing too early'
10:19:30 <sech1> Are they related in any way or completely independent?
10:19:49 <kayabaNerve> Three PoCs exist
10:20:15 <kayabaNerve> I did one of them with PlasmaPower, and I joined h4sh3d for the CCS proposal for a full fledged framework, ready for usage.
10:20:31 <kayabaNerve> So h4shed and co will be developing the design from the CCS proposal.
10:21:02 <endor00[m]> What, a new PoC got released in the last 60 seconds? xD
10:21:07 <kayabaNerve> COMIT also did a PoC, and they're working on turning it into a DEX. As in, making it app with a lot more functionality that also has order discovery.
10:21:25 <kayabaNerve> I forgot one:P It's some Python project for some random BTC fork. I wasn't a fan
10:21:36 <kayabaNerve> I mean, it looked accurate? Great to see yet another impl?
10:22:06 <kayabaNerve> So it's not a DEX like Bisq, yet rather a BTC-XMR swap app, yet it would have an order book...
10:22:34 <kayabaNerve> So that leaves 3 PoCs, 2 projects each with their own developers, 1 framework, and 1 single-market DEX
10:22:57 <kayabaNerve> The framework is planned to have example apps, which would be usable, but no order book functionality.
10:23:11 <kayabaNerve> Just to provide context on scope and differences.
10:23:56 <kayabaNerve> I've been bringing up the potential to collab with Franck[m], yet I think our timelines will be too different. They seem to want something focused for now, while we're working on a larger framework for any app/service.
10:24:19 <kayabaNerve> Both are respectable, and both can benefit from each other. I don't believe it'll become 1 team though/2 teams working on 1 project.
10:26:12 <kayabaNerve> **I brought it up with the Farcaster group as a whole. Franck[m] was the one who responded, as he's keeping an eye on our discussions.
15:43:39 <Matlin> hi
15:44:09 <Matlin> my blockchain is corrupted, does db-salvage actually fix it or just redownload it?
15:44:18 <Matlin> i do not want to redownload
15:47:49 <dEBRUYNE> Worth a try, but it is kind of 50/50
15:47:55 <dEBRUYNE> In case it doesn't work, you will have to redownload
15:47:55 <rbrunner> I would say try to salvage it. I don't think you have something to loose, don't know any better tool
15:50:07 <Matlin> for fucks sake
15:50:30 <Matlin> salvage didnt work
15:50:53 <Matlin> i dont understand why it cant just resume from the last non-corrupted block
15:51:18 <Jaska_> Probably because the blockchain is a single file?
15:51:34 <Matlin> what difference does that make?
15:51:35 <Jaska_> naw thats not it D:
15:54:28 <Matlin> this is very unreliable, just one tiny bit of corruption shouldnt fuck up the entire blockchain that you need to redownload 100GB from scratch :/
15:56:17 <Ymgve> how do you know it's just one tiny bit of corruption though
16:15:39 <artefact> lmdb claims to be crash-proof. do you 100% trust your hardware and filesystem?
16:15:56 <rbrunner> The blockchain file is not simply one block after the other; that database file has a quite complicated internal structure, for fast data access
16:16:37 <rbrunner> And I don't think it's "very unreliable", we would have many more people here with pitchforks if that was the case. Guess you were unlucky.
16:16:49 <Lyza> dEBRUYNE et all, I've still got no auto updater pop up. is it confirmed working for others?
16:17:05 <Jaska_> Matlin already bailed out
16:17:45 <rbrunner> Maybe going back to trusty old Bitcoin then :)
16:17:50 <artefact> damn smart filter
16:18:09 <artefact> extremely trusty indeed. never mind the 60,000 something xbt seized a couple of days ago by the DoJ ;-)
16:32:14 <dEBRUYNE> Lyza: Haven't seen reports of it not working :/
16:33:37 <Lyza> probably a lot of people updated manually since this was a big / important series of updates
16:34:00 <Lyza> I also can update manually, not worried about that, just want to help make sure the auto-update is actually working
17:36:35 <Mochi101> Lyza, updater popup? You mean a message in the daemon about needing an update?
17:37:04 <Mochi101> (I've seen this message in the daemon, so I can confirm that works)
18:41:39 <Ymgve> anyone know the reason why the devs put the tx public key in the extras field and not simply included it as a mandatory field in the tx structure?
18:47:15 <moneromooo> No, but I'll hypthesize that it's possibly because it's not a consensus item.
18:50:12 <binaryFate> afaik it's inherited from the earliest cryptonote code, so who knows for sure the intial rational.
19:34:09 <raecarruth> rotten: hello :)
22:21:37 * algo_max[m] sent a long message:  < https://matrix.org/_matrix/media/r0/download/matrix.org/YqorJnxLkQbmZupdNcDuyPck/message.txt >
22:22:30 <algo_max[m]> (yes I'm running it under root... in docker)
22:28:25 <asymptotically> algo_max[m]: i don't have anything to say about the memory usage, but don't assume that containers/namespaces are perfect. you should still try to run applications as normal users inside a container
22:30:51 <algo_max[m]> yes it's on my todo list actually, just didn't get the time to fix it yet
22:33:06 <algo_max[m]> I'll keep the process running as long as my system's memory permits. Maybe someone could help me diagnose where the memory went.