[-] Rucknium@monero.town 1 points 5 months ago

Right. As far as I know, a LLM will not give you a proper source if you ask it how it knows some information. A website found through a search engine will have a source for its info (or it's probably unreliable if it has no sources).

You as a human being have a right and responsibility to know the source of information and use your reasoning abilities to decide if the source is reliable. An LLM interrupts this process. I don't understand how people are absorbing information without sources or a way to critically think about if the information may be accurate.

[-] Rucknium@monero.town 2 points 5 months ago

The first one isn't text to speech and the second is not FOSS. If you have a good FOSS TTS that has examples of what the voices sound like, I would like to be linked to it :)

[-] Rucknium@monero.town 1 points 5 months ago

Yes it will be text-to-speech again. I will try another voice. Thanks for the feedback.

[-] Rucknium@monero.town 1 points 7 months ago
[-] Rucknium@monero.town 2 points 11 months ago

At the meeting, kayabaNerve (Luke Parker) suggested:

What'd likely be easiest, in a pure-C++ way, is to explicitly intended Monero's DKG to match MRL-0009 (if not already) and have it audited to line up. Then, a Musig2-esque CLSAG should be formalized (likely a modification of MRL-0009's Musig-DN-esque CLSAG?) and Monero should explicitly intended to match it. The fact it lines up should be audited.

My conclusion:

If anyone really wants to work on multisig, especially in the direction of kayabanerve's proposal, please speak up. IMHO, this was a productive conversation, but I don't expect any action to be taken unless more labor [is] put toward the problem.

Meeting log

[-] Rucknium@monero.town 1 points 1 year ago

If you have a Matrix account you should go to https://matrix.to/#/#monero-community-dev:monero.social to get help there and describe your app design. If you are just accepting payments to a website, then you can use BTCPay Server or BitCart.

The Monero blockchain does not hold data in plaintext like other blockchains. You cannot just query the blockchain data through an API. You have to decrypt transactions with private view keys.

23
submitted 1 year ago by Rucknium@monero.town to c/monero@monero.town

Why

Currently, Monero only has one node written in C/C++, many would see this as an issue. Having only one implementation makes us more vulnerable to implementation bugs, having another node will help us to spot and fix these issues.

monerod's code is also a bit of a mess, as many devs who have worked on it would agree. Cuprate is a fresh start and is built with modularity in mind which will lead to a cleaner and easier to understand codebase.

Having a consensus rules document will make it easier for developers to build software to interact with Monero. It will also make it easier to spot potential issues with consensus rules.

15
submitted 1 year ago by Rucknium@monero.town to c/monero@monero.town

Popular documentation like “Mastering Bitcoin” suggests the usage of bx seed for wallet generation.

Secure cryptography requires a source of large, non-guessable numbers. If the random number generator is weak, the resulting cryptographic usage is almost always compromised.

For technical people: in this case, practical wallet security is reduced from 128 bit, 192 bit or 256 bit to a mere 32 bit of unknown key information.

I am not an expert, but if you use a multi-coin wallet that includes Monero, then your Monero could be affected. I don't see a list of wallet software that is affected. It would not be easy to verify that closed-source wallets do not use the exploitable code library.

Q: I used bx to generate my wallets but only use it for non-BTC coins, do I need to worry?

A: Yes. All funds stored on BIP39 mnemonic secrets or BIP32 wallet seeds are affected since the underlying private keys are basically public now.

view more: ‹ prev next ›

Rucknium

joined 1 year ago