Howdy y'all

I am working on an offline seed generator for monero seeds using dice as a source of entropy.

Does anybody know what the proper amount of dice rolls (on 6 sided dice) are needed to reach proper level of entropy?

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.

Based on some Math from coldcard, a d6 dice provides 2.585 bits of additional entropy per roll

This means:

50 rolls for 128 bit

99 rolls for 256 bit

Would 100 dice rolls (assuming the dice are casino dice with proper random roll) be enough for source of entropy?

Here is a link to sample code of my implementation repo.getmonero.org/monero-project/c…als/-/merge_requests/323#note_16712

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.

From a UX perspective, you would be hard pressed to find anyone who would be willing to roll and record 100 die rolls :P

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.

thank you for the answer

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

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.

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

<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

"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

how many dice per seedword

?

5 ot 6 D6

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

You can even roll partial dice if you put the series of rolls as custom entropy to be hashed.

(so you have fewer rolls to make overall)

as i understand wallet2 API connects to daemon and gets UTXOs for transaction building

Spent or unspent, neither of them knows (except for the ones the wallet owns). But yes.

im doing this wm->setDaemonAddress("...");

and instancing a Monero::Wallet from words

can this thing build and transactions?

build and sign*

the thing im curious about is that we need to create wallets in BTC daemon for UTXOs

is Monero daemon working with the same way?

or when i connect a node like this i can just build and sign transactions?

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

get_outs

called by wallet2::get_outs

Wallet::Wallet::init(const char *argv0, const char *default_log_base_name)

Monero::Wallet::init(const char *argv0, const char *default_log_base_name)

this thing

what are the parameters of this?

from commit f9b22a7b01, does the '--hw-device' option require the user to specify a ':' and a device path afterwards?

what does wallet2 do to connect to nodes?

it may be problematic for iOS and Android

Opens a connection, sends some JSON RPC, gets result as JSON.

With optional SSL.

ummmmm this thing connects to RPC server then

is there an RPC server for testnet i can use?

we have a node setup but i can't use that right now

You use your own server.

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.

<MeowingCat> "is there an RPC server for..." <- 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.

looooooking thank youuuuuuuu

im curious about wallet2 API

where does Monero::WalletManager::setDaemonAddress() connect to?

RPC server or a Monero node??

A... monero node's RRC server.

To be clear, the node and the wallet both have a RPC server, but expose a different set of RPC.

wm->setDaemonAddress("testnet.xmr.sh");

is this wrong?????

MeowingCat: you need the port number "testnet.community.rino.io:28081"

oh that one does it have it lol

trying

do i need to do wallet->init()???

why ask? try it and see

im already trying everything

terminate called after throwing an instance of 'tools::error::wallet_not_initialized'

what(): wallet is not initialized

getting this errorr :(((

Clearly not tried everything yet then.

Looking at what existing working code does should help.

ie, the GUI

i looooked at monero-gui

but couldn't find any usage of these things

Hmm. OK, I'm surprised. Well, use whatever API calls it uses.

there are Monero::Wallet::mainAddress() and Monero::Wallet::address(uint32_t accountIndex = 0U, uint32_t addressIndex = 0U)

i haven't seen anything about setting network

ohh okiiiii i already made it in recoveryWallet() call

testnet parameter

interesting because after wm->setDaemonAddress("testnet.community.rino.io:28081");

wm->connected() is returning true

still getting this terminate called after throwing an instance of 'tools::error::wallet_internal_error'

what(): Failed to get height

Looks like comms to node failed.

Bump log level up, try again, read log, work from there.

terminate called after throwing an instance of 'tools::error::wallet_not_initialized'

what(): wallet is not initialized

this error

w->init("", "walletlogs");

im doing this

but getting this error

i need to understand something

is the way of how wallet2 API works that holding private seed on daemon?

can i just send private view key?

The wallet2 object will hold your secret keys. The seed is that, basically. It can be accessed via RPC, though it is not recommended.

The node daemon does not need it.

i mean

If you mean "I want to give someone my secret key and let them do the work for me", then look at monero-lws.

does wallet2 even provide a way to build and sign transactions without sending private seed anywhere like RPC server??

noooo we will not send private seed anywhere

Then wallet2 can build and sign txes without sending the secret keys anywhere.

we can send private view key if it is needed for building transactions (like for getting UTXOs)

niceeeeeeee

Monero works with UTXOs

then i need to send private view key to RPC server right???

It's like you do not use the information you're given before asking the same question again.

C++ code

im curious about what is wrong here :((((((((((

FWIW, I'm not looking, I'm not familiar with that API as I said before.

tfw moo forgets what c++ code looks like

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

im getting this for this RPC server: testnet.community.rino.io:28081

Bump log level. By default, the wallet does not log (to avoid leaving private info in the log).

i have a Monero::PendingTransaction object how can i serialize it?

MeowingCat: serialization should be like this I think (close enough) irccloud.com/pastebin/ppnofafq/serialization

UkoeHB, loooooooooking thank youuuuu

it only works for objects with the `BEGIN_SERIALIZE()` etc. macros

you mean i can't serialize a TX with things in wallet2_api.h???

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.

okiiii