I've created this "Howto": github.com/nonie-sys/monero_extra_entropy/blob/master/README.md

Using some dice to increase the entropy pool.

kayront: you reported a lot of wallet/daemon traffic on startup. I don't see that happening. So please (1) apply moneromooo-monero/bitmonero ea906f3, (2) sync the wallet, (3), restart wallet and daemon with --log-level 1,*dump:TRACE, (4) paste the logs to fpaste.org or paste.debian.net.

Make sure the wallet's synced first so we don't get a lot of sync spam.

I get ~2.5 kB of traffic on startup.

Guys, does anybody know how to run the latest monero gui on Ubuntu 19.04? I downloaded v0.15.0.1 but I get errors and there is to start sh file

Paste the actual error message. If it's more than a couple lines, to some paste site.

there is no ./start-gui.sh file

Is there a monero-wallet-gui binary ?

yes

but how do I run it?

./monero-wallet-gui

moneromooo: noted, I will try it asap

thanks!

hello

hello i have some questions

isnt monero too private

what happens if it gets used to bribe people

is it meant for wide adoption?

No, people get bribed, yes, respectively.

ok, thanks

Wide adoption though, well, it's a balance between this and the chain becoming too unwieldy.

But I certainly would love to be able to use it for mainstream large expenses, like buying a new fridge, say. In time.

<learninandlurkin> Super secret anonymous untraceable refrigeration

You may jest, but I want *everything* I do to not be hoovered and pored over by random creeps at any time without my knowledge.

Including refrigeration related things :)

<learninandlurkin> I'm with you on that one. Hey monero people. A friend of mine has just gotten into XMR and is trying to mine on his windows laptop. He's having an issue where monerod stops syncing after a few hours even though the laptop is set to not sleep or turn off the hard drive when plugged in.

<learninandlurkin> I can't seem to find anyone who's had the same problem online and I've not touched windows in a few years other than for work

<learninandlurkin> so I have basically zero windows monero knowledge

There's a known bug (though not known fix yet) that sounds like that. It's a db corruption unfortunately.

Run with log level 1, and if you get a "MDB_BAD_TXN" in the logs, it's that.

<learninandlurkin> Thanks I'll try that out right now

<learninandlurkin> Is it a case of the blockchain needs to be purged and start again once a fix is found?

Yes.

<learninandlurkin> I'm getting a lot of "transaction with hash HASH not found in db"

Are they errors or warnings ?

<learninandlurkin> warnings I believe

<learninandlurkin> or rather, just info. Sorry I've never used a log level other than 0

so dash cofounder exitscammed

YouTube Title: Bitcoin and Cryptocurrency News 12/4/2019 Views: 1,022 Length: 38:16 Uploaded: 2019-12-04 User: CryptosRUs Likes: 137 Dislikes: 10

Rolling On The Floor Laughing

dash going down to 10 bucks

gets delsisted on the double too from all big exchanges

EVAN DID NOTHING WRONG

Moocowmoo wasn't a cofounder! They committed a github change making him a community member

i want to run two daemons on the same blockchain. one daemon for p2p and the pthe for rpc. could someone help me with configuration please? for rpc I got: ./monerod --data-dir /xmr/blockchain --in-peers 400 --out-peers 400 --rpc-bind-ip 0.0.0.0 --rpc-bind-port 18089 --restricted-rpc --confirm-external-bind --p2p-bind-port 18070 --no-sync --no-zmq

and for the p2p i got: ./monerod --data-dir /xmr/blockchain --in-peers 400 --out-peers 400 --p2p-bind-port 18080 --limit-rate-up 640

what do you think? is this conf ok?

Yesterday

wat

huskar1, 2 daemons using the same chain?

Who changed github what where ?

Dash

not Monero

Mochi103, yes so i can limit the p2p trafic

Is that someone passing off as me, or someone really with that nick ?

They have that nick.

A scammer/core team member of Dash, no less

OK. Sorry for being paranoid ^_^

See github commit

huskar1, I don't think you can run 2 daemons configured to use the same chain... moneromooo would know better than me though

It's possible, though you might experience temporary dizziness, nausea and occasional tickling.

It's not super tested so it might have borked since last time it was given a clean bill of health though.

Feel bork inc.® youtube.com/watch?v=muLAN-kP5pE

YouTube Title: Feel Bork inc. Views: 2,605,523 Length: 2:10 Uploaded: 2016-10-02 User: Rapid Liquid Likes: 88,911 Dislikes: 1,003

The bots are becoming sentient

Mochi103, it is possible and i works in my conf, but I am unsure if I get p2p traffic on the rpc daemon.

is there a way to use a daemon for RPC only, not for p2p?

where would it get the chain data from?

that is not the question

i need a way to start a daemon exclusively for RPC

indeed, but it does beg the question: why do you want RPC access if you've made the daemon braindead by not being able to download and validate the chain at all?

block outgoing packets for p2p from the monero user, and accept inbound packets for the rpc port, and enjoy the zombie

ok I will explain it to you.

maybe you could use --add-exclusive-node 0.0.0.0 or similar

my node is more responsive, with a lower ping if i start two daemons on the same blockchain. one for p2p, where I limit the up-trafic and one exclusively for RPC

the p2p trafic of the rpc daemon is bound to the closed port 18070. it works, but it is a hack.

you could throttle bandwidth at the os if that's the concern

set limits, define priorities, anything is possible

Yes, --offline.

more over I want to start another daemon instance for tor rpc trafic

Offline doesn't apply to RPC in this context.

oh, ok is this documented moo?

In --help, yes. Elsewhere, I don't know.

thank you

is there a good api call I could hit for validate address on the rpc client?

validate_address.

There's not a better one moneromooo ?

:P

/s

Not yet :(

validate_encourage_and_inspire_address

And it returns an "Address from Monero to the People" speech about privacy, etc ?

;)

Just got this message in my CLI daemon: "Transaction spends at least one output which is too young"

This is when the CLI was synchronizing. The message was in red. Problem?

Is your daemon still synchronizing ?