03:22:47 <monero-hackerind> Howdy y'all
03:22:47 <monero-hackerind> I am working on an offline seed generator for monero seeds using dice as a source of entropy.
03:22:47 <monero-hackerind> Does anybody know what the proper amount of dice rolls (on 6 sided dice) are needed to reach proper level of entropy?
03:22:53 <monero-hackerind> In seedsigner they use 50 rolls for 12 word seeds and 99 rolls for 24 word seeds. (Which it should not matter as the dice rolls increase entropy and shouldn't directly translate to phrases.
03:23:04 <monero-hackerind> Based on some Math from coldcard, a d6 dice provides 2.585 bits of additional entropy per roll
03:23:04 <monero-hackerind> This means:
03:23:04 <monero-hackerind> 50 rolls for 128 bit
03:23:04 <monero-hackerind> 99 rolls for 256 bit
03:23:39 <monero-hackerind> Would 100 dice rolls (assuming the dice are casino dice with proper random roll) be enough for source of entropy? 
03:24:57 <monero-hackerind> Here is a link to sample code of my implementation https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/323#note_16712
03:42:50 <jeffro256[m]> Yes, I believe Monero's current seed scheme has 256-bits of entropy, so 100 perfect six-sided dice rolls would provide enough entropy. There is a new seed scheme proposed in Jamtis, called Polyseed, which only has 150 bits of entropy. 
03:44:17 <jeffro256[m]> From a UX perspective, you would be hard pressed to find anyone who would be willing to roll and record 100 die rolls :P
03:49:49 <jeffro256[m]> You don't "need" the full entropy of  a seed though if you determine it to be within your security threshold. As long as there is a deterministic formula for converting a sequence of die rolls into a binary string, you could use any number of die rolls. 
03:51:18 <monero-hackerind> thank you for the answer
03:51:54 <monero-hackerind> The random number generator on raspberry PI zero is not something I would trust fully. I've had microcontrollers not take ambient noise or temperature as entropy source so it would not be far fetched to see it fail. The other solution is dedicated crypto chips with a better random generator but it raises cost 
03:52:52 <monero-hackerind> I know the UX is a bit clunky but it is more the option for those who are a little bit more paranoid and are ok with feeding the entropy manually. 
03:54:02 <monero-hackerind> I piggyback on the seed generate function of monero python library so I can just feed it a 32 bytes of entropy generated from a hash of the dicerolls as a string 
05:40:31 <cryptogrampy[m]> <jeffro256[m]> "From a UX perspective, you would..." <- back in my day, we grabbed the dice from the yahtzee set and did 5 rolls at once
08:17:21 <badjabber> "From a UX perspective, you would be hard pressed to find anyone who would be willing to roll and record 100 die rolls :P" <-- I think people would do it
08:17:32 <badjabber> how many dice per seedword
08:17:34 <badjabber> ?
08:17:40 <badjabber> 5 ot 6 D6
08:18:22 <badjabber> roll 5 or 6 D6, look up your word. Repeat 24 times (25th is a checksum word) and u done.  Might be worth the effort to stay offline
08:24:41 <moneromooo> You can even roll partial dice if you put the series of rolls as custom entropy to be hashed.
08:24:55 <moneromooo> (so you have fewer rolls to make overall)
09:13:45 <MeowingCat> as i understand wallet2 API connects to daemon and gets UTXOs for transaction building
09:25:56 <moneromooo> Spent or unspent, neither of them knows (except for the ones the wallet owns). But yes.
09:54:45 <MeowingCat> im doing this wm->setDaemonAddress("...");
09:55:11 <MeowingCat> and instancing a Monero::Wallet from words
09:55:45 <MeowingCat> can this thing build and transactions?
09:55:55 <MeowingCat> build and sign*
09:56:43 <MeowingCat> the thing im curious about is that we need to create wallets in BTC daemon for UTXOs
09:56:59 <MeowingCat> is Monero daemon working with the same way?
09:57:18 <MeowingCat> or when i connect a node like this i can just build and sign transactions?
10:01:39 <MeowingCat> as i understand it is possible to build and sign transactions with cryptonote API tooo but then i need to get something like UTXOs from a node
10:05:09 <moneromooo> get_outs
10:05:29 <moneromooo> called by wallet2::get_outs
10:09:20 <MeowingCat> Wallet::Wallet::init(const char *argv0, const char *default_log_base_name)
10:09:39 <MeowingCat> Monero::Wallet::init(const char *argv0, const char *default_log_base_name)
10:09:41 <MeowingCat> this thing
10:09:55 <MeowingCat> what are the parameters of this?
10:20:21 <ime[m]> from commit f9b22a7b01, does the '--hw-device' option require the user to specify a ':' and a device path afterwards?
10:21:49 <MeowingCat> what does wallet2 do to connect to nodes?
10:22:35 <MeowingCat> it may be problematic for iOS and Android
10:31:02 <moneromooo> Opens a connection, sends some JSON RPC, gets result as JSON. 
10:31:14 <moneromooo> With optional SSL.
10:31:25 <MeowingCat> ummmmm this thing connects to RPC server then
10:33:03 <MeowingCat> is there an RPC server for testnet i can use?
10:33:23 <MeowingCat> we have a node setup but i can't use that right now
10:44:05 <moneromooo> You use your own server.
10:44:43 <moneromooo> Otherwise you don't learn how to use one, you are subject the vagaries of whether it's up or not, and it can just lie to you.
12:31:08 <Elijah[m]> <MeowingCat> "is there an RPC server for..." <- https://monero.fail/?nettype=testnet. Since this is testnet, deceptive nodes (if any) aren't going to cause real damage. This was useful for me because if I run my e-commerce store locally, it uses either my local test net node or if that's behind, I use one of the nodes in monero fail. For production, I use a node run on the cloud. 
12:31:24 <MeowingCat> looooooking thank youuuuuuuu
12:32:10 <MeowingCat> im curious about wallet2 API
12:32:46 <MeowingCat> where does Monero::WalletManager::setDaemonAddress() connect to?
12:32:53 <MeowingCat> RPC server or a Monero node??
12:36:01 <moneromooo> A... monero node's RRC server.
12:38:05 <moneromooo> To be clear, the node and the wallet both have a RPC server, but expose a different set of RPC.
12:43:55 <MeowingCat> wm->setDaemonAddress("https://testnet.xmr.sh/");
12:43:57 <MeowingCat> is this wrong?????
12:45:16 <UkoeHB> MeowingCat: you need the port number "http://testnet.community.rino.io:28081"
12:45:34 <UkoeHB> oh that one does it have it lol
12:45:57 <MeowingCat> trying
12:46:13 <MeowingCat> do i need to do wallet->init()???
12:46:35 <UkoeHB> why ask? try it and see
12:47:06 <MeowingCat> im already trying everything
12:47:07 <MeowingCat> terminate called after throwing an instance of 'tools::error::wallet_not_initialized'
12:47:07 <MeowingCat>   what():  wallet is not initialized
12:47:11 <MeowingCat> getting this errorr :(((
12:47:55 <moneromooo> Clearly not tried everything yet then.
12:48:20 <moneromooo> Looking at what existing working code does should help.
12:48:26 <moneromooo> ie, the GUI
12:48:43 <MeowingCat> i looooked at monero-gui
12:48:52 <MeowingCat> but couldn't find any usage of these things
12:49:17 <moneromooo> Hmm. OK, I'm surprised. Well, use whatever API calls it uses.
13:03:58 <MeowingCat> there are Monero::Wallet::mainAddress() and Monero::Wallet::address(uint32_t accountIndex = 0U, uint32_t addressIndex = 0U)
13:04:25 <MeowingCat> i haven't seen anything about setting network
13:09:13 <MeowingCat> ohh okiiiii i already made it in recoveryWallet() call
13:09:20 <MeowingCat> testnet parameter
13:14:27 <MeowingCat> interesting because after wm->setDaemonAddress("http://testnet.community.rino.io:28081");
13:14:36 <MeowingCat> wm->connected() is returning true
13:21:13 <MeowingCat> still getting this terminate called after throwing an instance of 'tools::error::wallet_internal_error'
13:21:13 <MeowingCat>   what():  Failed to get height
13:25:26 <moneromooo> Looks like comms to node failed.
13:25:53 <moneromooo> Bump log level up, try again, read log, work from there.
13:52:35 <MeowingCat> terminate called after throwing an instance of 'tools::error::wallet_not_initialized'
13:52:36 <MeowingCat>   what():  wallet is not initialized
13:52:37 <MeowingCat> this error
13:52:46 <MeowingCat> w->init("", "walletlogs");
13:52:48 <MeowingCat> im doing this
13:52:51 <MeowingCat> but getting this error
14:05:52 <MeowingCat> i need to understand something
14:06:54 <MeowingCat> is the way of how wallet2 API works that holding private seed on daemon?
14:07:03 <MeowingCat> can i just send private view key?
14:07:46 <moneromooo> The wallet2 object will hold your secret keys. The seed is that, basically. It can be accessed via RPC, though it is not recommended.
14:07:54 <moneromooo> The node daemon does not need it.
14:08:11 <MeowingCat> i mean
14:08:39 <moneromooo> If you mean "I want to give someone my secret key and let them do the work for me", then look at monero-lws.
14:08:46 <MeowingCat> does wallet2 even provide a way to build and sign transactions without sending private seed anywhere like RPC server??
14:09:07 <MeowingCat> noooo we will not send private seed anywhere
14:09:32 <moneromooo> Then wallet2 can build and sign txes without sending the secret keys anywhere.
14:09:34 <MeowingCat> we can send private view key if it is needed for building transactions (like for getting UTXOs)
14:09:42 <MeowingCat> niceeeeeeee
14:10:03 <MeowingCat> Monero works with UTXOs
14:10:17 <MeowingCat> then i need to send private view key to RPC server right???
14:10:39 <moneromooo> It's like you do not use the information you're given before asking the same question again.
14:11:56 <MeowingCat> https://pastebin.com/FWv59kMu
14:12:04 <MeowingCat> C++ code
14:12:12 <MeowingCat> im curious about what is wrong here :((((((((((
14:13:08 <moneromooo> FWIW, I'm not looking, I'm not familiar with that API as I said before.
14:13:11 <plowsof[m]> tfw moo forgets what c++ code looks like 
16:58:58 <MeowingCat> INFO	logging	contrib/epee/src/mlog.cpp:273	New log categories: *:WARNING,net:FATAL,net.http:FATAL,net.ssl:FATAL,net.p2p:FATAL,net.cn:FATAL,daemon.rpc:FATAL,global:INFO,verify:FATAL,serialization:FATAL,daemon.rpc.payment:ERROR,stacktrace:INFO,logging:INFO,msgwriter:INFO
17:00:20 <MeowingCat> im getting this for this RPC server: http://testnet.community.rino.io:28081
17:03:53 <moneromooo> Bump log level. By default, the wallet does not log (to avoid leaving private info in the log).
17:58:07 <MeowingCat> i have a Monero::PendingTransaction object how can i serialize it?
18:09:36 <UkoeHB> MeowingCat: serialization should be like this I think (close enough) https://www.irccloud.com/pastebin/ppnofafq/serialization
18:10:42 <MeowingCat> UkoeHB, loooooooooking thank youuuuu
18:13:00 <UkoeHB> it only works for objects with the `BEGIN_SERIALIZE()` etc. macros
18:23:22 <MeowingCat> you mean i can't serialize a TX with things in wallet2_api.h???
18:26:03 <UkoeHB> MeowingCat: no, I mean "it only works for objects with the `BEGIN_SERIALIZE()` etc. macros". You have to go look at objects to see if they are serializable.
18:31:46 <MeowingCat> okiiii