00:53:52 <br-m> <gasperx:matrix.org> Hello everyone,
00:53:52 <br-m> <gasperx:matrix.org> I’m developing a personal-use system where I intend to perform transactions via atomic swaps.
00:53:52 <br-m> <gasperx:matrix.org> I’m currently using a rendezvous/discovery node (please correct me if this terminology isn’t accurate), but I’m having difficulty finding enough peers online and available.[... more lines follow, see https://mrelay.p2pool.observer/e/krrBgeIKNVBVdGN4 ]
05:23:27 <clawmon23> Any thoughts on current market opportunities or new projects worth watching?
11:57:11 <deavmi> Does monero-wallet-rpc only bind and start listening for RPC calls once the block sync is done?
12:06:55 <plowsof> deavmi yes unless you add flag --no-initial-sync 
12:30:39 <deavmi> no initial sync will allow all other components to immediately start
12:30:50 <deavmi> and then synchronization countinues elsewhere (seprate to start up thread)?
12:41:30 <plowsof> correct, you can then poll the wallets height to check if its = to current block height 
12:47:00 <deavmi> ah
12:47:01 <deavmi> neato
12:47:02 <deavmi> thanks plowsof
12:51:41 <deavmi> works :_
12:51:42 <deavmi> * :)
12:56:14 <deavmi> plowsof: should RPC calls take so long though, feels like sometimes I am waiting forever, at least whilstn the blocks are syncing...
12:56:18 <deavmi> Even with that option you provided
12:56:31 <deavmi> Is some internal lock held for the duration of block sync
12:56:32 <deavmi> ?
12:57:19 <deavmi> I wonder if --max-concurrency could be set to somethine maybe...
13:07:03 <deavmi> nvm not that, just gotta wait for this sync I guess
13:07:26 <deavmi> Thing is I open and close an RPC connection, so that initial connection that I get due to --no-initial-sync is not re-used. I should probably look into that
13:08:06 <plowsof> The wallet rpc server does take a bit to start even with no initial sync, i have no idea what you're using but e.g. in python you can start the binary and read stdout and wait to see the rpc init line print. Then make your calls
13:08:46 <deavmi> Using https://github.com/moneropay/go-monero
13:08:57 <plowsof> Ah some calls require the wallet to be synced 
13:09:03 <deavmi> Ah 
13:09:06 <plowsof> Could be encountering that?
13:09:08 <deavmi> Dummy me should have read that
13:09:10 <deavmi> Probably
13:09:37 <deavmi> If I remove the --daemon from monero-wallet-rpc then calls work fine as it (the go library) doesn't see it syncing
13:09:39 <deavmi> makes sense
13:09:43 <deavmi> thanks plowsof, ;)
13:10:08 <deavmi> [15:08:57] <@plowsof> Ah some calls require the wallet to be synced 
13:10:13 <deavmi> Yeah the ones I am doing are getBalance related
13:10:13 <plowsof> There is #monero-community-dev also for none core help and sharing what you're working on too
13:10:15 <deavmi> so makes sense
13:10:23 <deavmi> plowsof: Will join, thanks!
13:11:32 <deavmi> Althogh seems like my first call, getting adresses, even takes some time. I will let the wallet sync and once that's done I will then give this a shot again
13:11:53 <deavmi> Ofc, in whatever I end up building, I'll add timeouts and all for this, go makes that relatively easy from the get-go (no pun intended)
13:12:02 <deavmi> Just tryna get my feet wet with how monero's side of things work