10:13:13 helloe 10:13:58 I came with news of a new coin initiative. The era of Pi is over, it is a 1 week project, come to Kivanet, it does not require ID etc. It is mined from the browser or if you want a mobile application, it is a new project at this stage, I say sign up and try it without giving any critical information, an e-mail and password are enough. It is started with coin transaction, in near f 10:13:58 uture you can trade it in a market and get some dollars. Here is my invitation link that boosts your mining rate: 10:14:00 https://kivanet.com/register.html?code=G7F6MK 10:19:09 dude, sober up 11:03:03 the fucking monerod database is so fragile fml (power outage, DB corrupt, lfg) 11:17:30 it didn't experience it that much 11:17:57 i had faced it only once when i was doing initial sync 11:33:04 spam 11:33:19 plowsof 11:34:41 <3​21bob321:monero.social> Wes inclusive 12:28:56 ya, testing initial sync for 0.18.4.0 12:33:52 refer tips in [#monero-support:monero.social](https://matrix.to/#/%23monero-support:monero.social) group 12:34:34 fast sync has the possibility of corruption 12:58:25 yeah I know 12:59:23 Bitcoin Core has options like pop-blocks to roll back the database, Monero is just like, tough shit start over 13:02:26 LMDB don't have the durability flag during sync 13:02:39 once you sync, monerod add it back and you should be resistant to power outage 13:02:57 db corrupt however is completely unrelated to the db system 13:18:04 Is there anything out there that is better than lmdb? and can be used with monero? 13:20:53 Cuprate will have the option to not use LMDB, will see how much better is it, but at the least it's a bajillion times faster 13:22:16 Cuprate is currently using lmdb 13:22:42 i think the alternative is redDB. Or something like that 13:22:53 i want to experiment with Fjall 13:23:12 Redb 13:23:15 which seems way better than redb 13:23:29 There is also mdbx that we haven't tried fwiw 13:23:55 after initial sync you can switch to `db-sync-mode=safe:sync` 13:24:10 corruption is one thing, I'm talking about not being able to recover from it with something like pop-blocks offered by bitcoin core 13:24:19 shouldn't it be done automatically?? 13:24:24 guys. guys. I know all the monerod options and stuff. I appreciate it. I'm mostly just bitching 13:24:38 bitching is great 13:25:15 that is, `db-sync-mode=fast:async` 13:25:22 Fwiw we have no shutdown code, when we shutdown everything is just abruptly stopped. With redb this causes it to scan the whole db for corruption on startup which takes forever, so we will need to fix that before making redb a legit option 13:25:31 Soomtm 13:26:27 one problem, imo, is that we store the txpool in the same db as the blockchain 13:26:48 so were constantly modifying the db 13:27:37 yikes! that does seem crazy 13:27:38 I don't know shit about databases but I also notice the bitcoin core database is like 1 million different tiny files as opposed to a giat scary monolithic file 13:27:40 considering the txpool is ephemeral, i don't even understand why we're putting this shit into a DB to begin with, it don't need persistence? ( boog900 feel free to correct me ) 13:28:01 that was my thought as well Synthetic 13:28:24 afaik, its Simply to avoid downloading it 💀 13:28:28 That's because we're part of the Hive mind Lyza 13:28:32 one to one comparison with bitcoind is not sensible 13:28:56 Its set to a max of 650mb to begin with, so i dont see jt as a ram issue at all 13:29:10 You could lose a tx of you are the only one to have it 13:29:24 You could lose a tx if you are the only one to have it 13:29:30 And restart 13:29:40 one to one comparison with bitcoind is not practical. 13:29:41 The wallet would lose the tx too 13:29:48 ..So no harm done 13:30:15 Do different than having a tx that failed to relay, then doing a flush_txpool 13:30:27 No different than having a tx that failed to relay, then doing a flush_txpool 13:30:44 i see 13:30:56 extremely unlikely to happen tho 13:31:37 Even if it did, it wouldnt be an issue 13:32:36 unless you and merchant were using the same node .. and doing 0 conf tx's 13:33:20 in any event, i dont think it makes sense to store the txpool in the _same_ db as the blockchain 13:33:33 cuprate have its separate 13:33:39 cuprate uses a 2nd db aiui 13:33:40 cuprate have it separate 14:29:29 so I'm trying to host a restricted monero rpc node publicly (but with a login) and I'm not sure if I should be using an SRV record or an A record. Seems only SRV is supported? 14:40:30 A works 14:40:49 I'm no dns guru, but A works 14:41:15 You have to open ports on the node, of course 14:45:24 and should it be 18081 or 18089? 14:45:33 since I use restricted I would think it's the latter 14:46:28 --rpc-restricted-bind-ip=0.0.0.0 --rpc-restricted-bind-port=18089 14:47:59 then allow incoming for 18089 in your firewall, and port forward it if youre behind a router 17:29:31 Hi, don't want to raise the heated topic much, but just letting you know that personally I see no point in "improving btcpay because other solutions don't have that many integrations/not as mature" etc when bitcart has existed for all this time (if btcpay was released in 2017 somewhere, bitcart first commit was early 2019) with monero support for quite some time which was proven q 17:29:32 uite stable because after some fixes I made noone has ever reported issues in XMR processing, it works butter smooth. And if one node fails it falls back to the next node in the list, so it is very stable 17:29:34 As for the integrations we support shopify, whmcs, woocommerce, even fossbilling (in fact we were the first to add crypto integration to them), odoo and more can be added easily as I just added one endpoint which does all the integration stuff for any e-commerce solution which all btcpay plugins duplicate in each of the plugins: https://docs.bitcart.ai/integrations 17:29:36 And in general I don't understand the point of improving it much. Okay v2 was released, but I log in sometimes and it's always the same, it's centric at one wallet setup, with BTC being always displayed. And monero was always via some hacks or plugins they tried to make 17:29:38 While bitcart supports unlimited number of wallets, it is centered at the concept that you can have many wallets bind to the store. You can even enable a setting and it will pick a random wallet for each new invoice out of those connected of same currency 17:29:40 And as for BTC + XMR scenario bitcart obviously supports it, but it supports literally any currency one would ever need, including those btcpay wouldn't add (e.g. BCH, ETH and more) 17:29:42 I remember I DMed you in twitter asking to try it out but I guess you didn't (: 17:29:44 And if there's something missing that would help merchants onboard easier I am open to adding it. That's the point, Bitcart has all the features already implemented years ago, even email notifications to customers, notifications to merchant itself via telegram discord matrix literally anything with custom templates. 17:29:46 And the main thing is, CCS requires funding but I am fine with adding it for free if it boosts visibility of Bitcart as that's the only issue Bitcart has 17:29:48 Sorry, end rant from my side 18:43:37 So I made an A record in my registrar for xmr.domain.com pointing to my public IP. Nginx is configured to forward traffic for that domain at port 443 to my monero daemon at port 18089. This doesn't work, connection times out. 18:43:38 Port forwarding port 18089 allows me to connect to my daemon via my public IP, but I'd rather not forward another port, and just go through nginx. 18:43:40 This leads me to believe A records are *not* supported. 18:45:24 What're you trying to do exactly? A records just resolve a DNS address to an IP, they have nothing to do with ports. 18:49:25 I'm trying to set up cloudflare for my semi-public monero node so I can let certain people access it for development purposes 18:50:03 so the people I work with don't have to set up their own node but also don't have to trust one not hosted by a trusted party 18:51:08 I don't have a vps to route through so cloudflare's my next best bet for not getting ddossed for hosting a monero node 18:51:39 If you're going to use cloudflare anyway, I'd suggest looking at a cloudflare tunnel, as it does exactly what you're trying to do. 18:52:10 ah I need a tunnel for this? that's unfortunate 18:52:18 No, it's just simpler. 18:52:47 well, what are my options if I don't want to use a tunnel? 18:52:50 You can reverse-proxy RPC all day, but cloudflare only provides marginal protection unless you do a bunch of protection work. 18:53:31 I host other things on the machine hosting this node that I don't want to tunnel, and I feel like specifying what I do and don't want to tunnel is going to be a pain 18:53:34 That being said, what error did you run into reverse proxying it? 18:54:23 Tunnel is a dedicated application that is essentially cloudflare's version of ngrok, AKA: They give you a DNS hostname listening on 443, and it tunnels it to whatever port is listening on the box the tunnel service is on. 18:54:35 It's not a full "route everything" tunnel. 18:55:05 If you've already got a reverse proxy up, the only likely error is somewhere in your nginx config. 18:55:13 connection drops when trying to connect to either xmr.domain.com:443 or xmr.domain.com:18089 with this command `monero-wallet-cli --daemon-address xmr.domain.com:443 --daemon-login domain --trusted-daemon` 18:55:17 says the daemon's not running 18:55:24 if I replace xmr.domain.com:443 with publicip:18089 it does work because I port forwarded that port to make it work 18:55:25 What's in your nginx logs? 18:56:58 Do you have ssl certs configured on the node? Is 443 expecting ssl? 18:57:09 no errors, no info related to domains 18:57:15 yes 18:57:18 but what do you mean with that last part? 18:57:28 should I be specifying https://xmr.domain.com:443 instead? 18:58:13 you mentioned RPC, I don't explicitly proxy RPC connections, just TCP (I use nginx proxy manager) 18:58:48 so I should specify something to proxy the RPC connection? 18:59:05 gonna look into how to do that 19:00:29 That's a unique setup to try to stuff behind cloudflare, sorry I thought you were using standard Nginx, so this one's a bit outside my normal. :) In theory, if it's just proxying the TCP, it should be mostly fine, but I've not played with nginx proxy manager before, so I'll back outta this one. 19:01:21 I've been meaning to replace it with regular nginx but I haven't had the time 20:55:16 New binaries for v0.18.4.0 are now available on getmonero.org 22:13:04 mrnaif is there a way to run bitcart with IP addresses in BITCART_HOST instead of domain names? I ask because I'd like to check it out in a Nix shell, which means hosts file can't be edited 22:13:36 I'd like to explore the API and develop against it locally 22:17:05 Of course! 22:17:06 export BITCART_HOST=1.2.3.4 22:17:08 export BITCART_REVERSEPROXY=nginx 22:17:10 ./setup.sh 22:20:03 ok cool, ty 22:20:24 is there any reason for using nginx in this context though? I'd be running containerless 22:20:58 as far as I can tell it's just redis and postgres together with the actual bitcart service 22:21:35 could even roll with sqlite since it's for dev anyway 22:22:17 or did I misread that about sqlite support 22:22:19 might've done 22:37:19 by god I now understand why you ship this with install scripts and docker 22:41:30 ig that's required thanks to the sheer amount of currencies you support 22:41:39 and them all needing a daemon 22:42:05 There is no sqlite support only postgres. docker is recommended because it configures all env vars. I mean you could set reverseproxy to none then it will expose daemons at ports 5000X, backend to 8000 etc 22:42:06 as for manual you can do but you need is python and nodejs if you want containerless 22:42:39 that's the beauty of it, it's modular and each currency and it's dependencies are in separate container, one daemon implements all blockchain features it represents 22:42:40 and they all have the same universal api 22:44:24 basically you can even roll out your own docker compose but I see no reason to because if in updates I change something you need to update it as well too somehow 22:44:26 and the env vars customize every aspect of how compose is generated 22:44:28 in fact you can even write custom rules or components 22:44:30 this way I even wrote sub applications running under one bitcart deployment 22:45:20 but what the scripts do basically is, install docker if not there, persist env vars, re-build compose file and start 22:45:20 and plugins handling if you installed any