00:26:08 <downystreet> I'm having a problem with my node when trying to set it to become public and open port 18089
00:26:39 <downystreet> When I use my external ip for the rpc bind I'm getting 2 errors
00:26:53 <downystreet> 2020-06-14 00:17:52.726 F Error starting server: Failed to bind IPv4 (set to required)
00:27:09 <downystreet> 2020-06-14 00:17:52.768 E Exception in main! Failed to initialize core RPC server.
00:27:19 <downystreet> it then shuts down
00:27:43 <downystreet> when I use my internal ip the daemon will start normally and work fine but I am not able to connect to it with any wallet
00:28:55 <downystreet> Here are the settings I am using to start it --restricted-rpc --rpc-bind-ip 111.111.111.111 --rpc-bind-port 18089 --confirm-external-bind --public-node --rpc-payment-address 49wNldksjfakldjfkladjfkladjsfklj --rpc-payment-credits 250 --rpc-payment-difficulty 1000
00:31:40 <Spaceguide> what settings you use in router ?
00:32:57 <downystreet> i'm port forwarding 18080 and 18089
00:33:48 <Spaceguide> do you specify the Ip from your machine ?
00:36:22 <downystreet> yes im using the external ip from my machine that i use to host a webpage and other nodes
00:37:28 <Spaceguide> I need to set it like external port X ( if needed to Ip ) to internal port Y on internal Ip
00:38:50 <Spaceguide> not running a public node now, didn't play with it already, waiting on a good server..
00:41:42 <downystreet5> got disconnected there
00:43:15 <downystreet5> can anyone here me?
01:11:27 <hcb> Is the "blob" in the get_block RPC function enough to reconstruct a block? If not, what is it missing?
01:11:40 <hcb> I know with Bitcoin you can request entire raw blocks via RPC.
01:11:54 <hcb> I'm working on a project similar to kryptoradio but for Monero.
01:12:24 <hcb> If I sent only the blobs from the get_block RPC function, could a receiver build the blockchain?
01:23:57 <moneromooo> Depends what you mean by block. If you want the actual transactions, you need to request them separately (except the coinbase, which is already present).
01:44:40 <hcb_> I'm trying to get raw binary data for a full block like the result that Bitcoin's getblock RPC function returns when verbosity is 0.
01:45:53 <hcb_> This is the Bitcoin RPC function I'm trying to find for Monero. https://bitcoin-rpc.github.io/en/doc/0.17.99/rpc/blockchain/getblock/
01:46:12 <moneromooo> blob is the raw binary data for the block. It has transaction hashes.
01:46:45 <hcb_> It seems too small to hold actual transactions.
01:47:13 <hcb_> Is it small because there are only coinbase transactions?
01:48:13 <moneromooo> It it small because it has the coinbase tx and transaction hashes. A transaction hash is a 32 byte value that identifies the tx, not the actual tx (which as I said you need to request separately).
01:48:25 <moneromooo> (should you need them)
01:49:40 <hcb_> So if I understand correctly, the coinbase tx is the only one included by default?
01:50:03 <hcb_> I'm trying to put together a full block that a receiver can receive, verify, and add to its blockchain.
01:50:07 <moneromooo> Correct.
01:50:26 <moneromooo> Then you need to request the txes from the tx hashes included in the block.
01:51:06 <moneromooo> You don't have to parse the blob btw, they're also included in the json IIRC.
01:53:27 <hcb_> There's a method called get_transactions that I can use.
01:54:45 <hcb_> When I have all the transactions from a block in hex format, how do I know how to arrange them in the right order so they hash to the right block hash?
01:54:56 <hcb_> Sorry if that's a very basic question.
01:54:59 <moneromooo> You want to have a blockchain built up from RPC, rather than P2P messages ?
01:55:06 <hcb_> Yes
01:55:12 <moneromooo> The tx hashes you get will be in the right order.
01:55:52 <moneromooo> (from get_block)
01:56:04 <hcb_> Thank you, that makes sense. I guess I would assemble a block with a header after that and it would be the same as the one in the data file.
01:57:42 <moneromooo> Depending on what you call header. If you have the blob from get_block and all the tx blobs the block references, you have all you need.
01:58:54 <hcb_> That sounds easy.
01:58:59 <hcb_> Thank you for explaining it.
04:36:36 <Steven_M> Hi all, what's the difference between the --p2p-bind-port switch and the --p2p-external-port switch for monerod?
04:38:11 <selsta> Steven_M: both are explained here: https://monerodocs.org/interacting/monerod-reference/
04:43:01 <Steven_M> selsta: ahh, I see :-)
04:44:01 * Steven_M will BRB
05:17:59 <Steven_M> The percentages in this message seem contradictory: "(99%, 186 left, 64% of total synced..."
05:23:50 <selsta> Steven_M: It means 64% of when you started syncing.
05:25:42 <Steven_M> selsta: ahh, thank you. :-)
07:28:46 <azy> it would be easier for home computers to run a public _tor_ node, right? no requirements to open ports, which is more of an effort typically?
09:30:55 <azy> "The daemon allows to make a node public by simply adding the flag --public-node. Doing so, it will be advertised on the P2P network and people will be able to connect to it" @ https://web.getmonero.org/resources/moneropedia/remote-node.html - advertised how? above this is 'aggregators' which are manually and central, there's no 'p2p list' of public nodes is there? we have to use the likes of moneroworld.com/#nodes ?
09:35:13 <asymptotically> azy: moneroworld.com uses a script to find all of the nodes that have port 18089 open and working. --public-node does what it says it does, you don't need to ask moneroworld, just other nodes on the network
09:35:28 <moneromooo> Advertised by setting the relevant flag in the peers list that nodes share.
09:43:48 <Mochi101> #NoFlagIsIrrelevant
09:45:03 <Mochi101> oh man... wrong channel
09:45:12 <Mochi101> :)
09:51:57 <azy> asymptotically, im not seeing such a list, i just see a couple manually entered nodes with no up(time) checking
09:52:14 <asymptotically> where are you looking? i think that there's a command to print them all in the daemon cli
09:52:49 <azy> if i were looking for a public node to connect to i'd go to https://moneroworld.com/#nodes
09:53:09 <azy> "TOR Remote Nodes Note - I don't check these, at all. No idea if they work..."
09:53:13 <azy> i wanted to automate this
09:53:23 <azy> for regular nodes too, but i dont know if thats necessary
09:55:57 <Mochi101> https://github.com/Gingeropolous/moneriote
09:57:17 <Mochi101> azy, ^^^
10:15:02 <azy> neat
10:19:50 <Mochi101> There will be so much bash it won't be funny.
12:01:38 <xmrpow> Can I somehow limit the ram usage of monerod. I know that lmdb should free up space when other processes need it, but I m having a weird bug on my pool where im getting errors after few days of running it...
12:05:23 <moneromooo> Try looking into cgroups.
12:07:28 <asymptotically> xmrpow: how do you start monerod? systemd service?
12:09:05 <xmrpow> asymptotically: Im just using screen ./monerod  and few other arguements
12:10:06 <asymptotically> xmrpow: have a look at https://github.com/monero-project/monero/blob/master/utils/systemd/monerod.service and https://www.freedesktop.org/software/systemd/man/systemd.resource-control.html (tl;dr: add MemoryMax=1234M)
12:10:26 <xmrpow> thanks ill have a look.
12:10:43 <asymptotically> then it can automatically restart it for you when it crashes and at boot. much nicer than running it in screen :)
12:47:25 <xmrpow> asymptotically: Is there a way to reattach to monerod in order to use monerod command line?
12:47:49 <xmrpow> asymptotically: systemd was a great hint!
12:48:55 <selsta> no way to reattach
12:52:48 <xmrpow> selsta: But how can I check if everything is running fine?
12:53:10 <selsta> e.g. ./monerod status
12:53:26 <selsta> or use tmux or whatever
12:54:52 <xmrpow> selsta: If I detached monerod i cant use the command line of monerod
12:55:50 <selsta> Did you try it?
12:56:29 <xmrpow> ops sorry. Does work.
12:56:37 <xmrpow> Thank you
12:56:44 <xmrpow> cd
22:00:12 <d4ndo[m]> Can't wait for the Monero project to move to radicle.
22:06:54 <d4ndo[m]> I think maybe Tari and radicle would be compatible.
22:07:20 <d4ndo[m]> They could do the blockchain stuff on Tari.
22:07:21 <d4ndo[m]> probably.
22:07:28 <d4ndo[m]> i dont know