-
m-relay
<m0nero:matrix.org> Hey guys.
-
m-relay
<m0nero:matrix.org> What approach would you recommend to a beginner who really wants to start developing apps on Monero? The only language I somewhat understand is Python. Should I start with the documentation or perhaps something simpler? What resources do you use? Which languages are best suited for developing apps/cli wallet extensions?
-
m-relay
<m0nero:matrix.org> Thanks.
-
m-relay
<syntheticbird:monero.social> Depends you exactly want to do
-
m-relay
<someoneelse495495:matrix.org> Hi, this is more suited for #monero-community-dev. But to answer quickly, it depends on what you want to do. To make a wallet you need to learn the Wallet API. Iirc there are wrapper for at least 5 languages but i don't remember if python is up to date
-
m-relay
<recanman:kernal.eu> Hi, may someone explain how ed25519 signature functionality is implemented? Specifically when signing a message (e.g "hello")
-
m-relay
<recanman:kernal.eu> I haven't been able to find a robust explanation online
-
m-relay
<syntheticbird:monero.social> Hi, I've setup a forgejo instance to mirror monero-project repositories as well as important monero ecosystem one. I learned in #monero-website that gitlab free don't allow pulling mirrors, so I decided to open one myself. I plan on configuring Github Oauth2 for every devs to quickly log into Librejo and setup mirrors for their personal repositories.
-
m-relay
-
andrei_krx
Hey. Our mined blocks periodically become orphaned. We can in logs that RPC submit_block was before entry "BLOCK ADDED AS ALTERNATIVE ON HEIGHT". So, if I understand correctly, we mined block before another block with this height was received. But why monero choose not ours blocks? Is it some p2p block propogation problem here?
-
andrei_krx
-
sech1
PoW of your block is "a2978abceb2b0584293eca20f9e214ba4642c01b94c0d673978d860400" which is definitely not enough for a mainchain block. PoW for the alternative block is "d2603c4051e72d97a3b1360c2865046a3ac080ad9a417032b6fd270400000000" which is more like it (many zeroes in the end)
-
sech1
So you're mining invalid blocks
-
sech1
Check that you didn't forget to remove "--fixed-difficulty" argument for monerod command line
-
andrei_krx
Pow of our block is "a2978abceb2b0584293eca20f9e214ba4642c01b94c0d673978d860400000000" (there is new line that split it in logs)
-
andrei_krx
a2978abceb2b0584293eca20f9e214ba4642c01b94c0d673978d860400000000 < d2603c4051e72d97a3b1360c2865046a3ac080ad9a417032b6fd270400000000
-
sech1
Alternative block arrived 2 minutes after your block, so your block didn't propagate, or you were already mining on an alternative chain. You should check how many nodes you're connected to. It's especially important to be connected to other major pool nodes.
-
andrei_krx
We have 31 in and 1022 out peers according to `get_info` request.
-
andrei_krx
Yeap, this is my question why this block was not propogated :(
-
sech1
1022 out? This is too much
-
sech1
64 in/64 out is much better and will be more than enough, as long as you add other pool nodes as priority nodes
-
sech1
1022 out can also push you above default open files limit in Linux
-
andrei_krx
I was increased limit of open files via systemd configs.
-
andrei_krx
I have no idea how to find another pool nodes. Is it any recommendations?
-
andrei_krx
But it is strange that we push block to 1024 nodes and network didn't accepted it.
-
sech1
supportxmr has a list of their nodes somewhere in the API
-
sech1
You shouldn't push block to 1024 nodes
-
sech1
You should push it to a few dozen nodes that matter for mining, aka pool nodes
-
sech1
And they will start mining on top of your new block immediately, and push it further to the rest of the network
-
sech1
nanopool doesn't publish their nodes at all
-
sech1
I did a research a while ago, and compiled this list (it's probably a bit outdated by now):
paste.debian.net/hidden/27622b21
-
andrei_krx
sech1: how did you collect this ips?
-
sech1
Supportxmr ones are taken directly from their API (I don't remember the URL)
-
sech1
Nanopool and Hashvault were found by observing which nodes broadcast blocks first
-
sech1
Then independently checked, like this one from nanopool:
ipinfo.io/147.135.129.32 - it says "xmr.worker.3.nnpl.xyz"
-
andrei_krx
sech1: FYI: I use Monero 'Fluorine Fermi' (v0.18.3.1-release) with following config:
paste.debian.net/plainh/f7655556 Can I ask you for review?
-
andrei_krx
Still don't understand why part of our blocks is not propogated
-
sech1
You should update to v0.18.3.3
-
sech1
.1 had a few nasty bugs
-
sech1
you don't need more than a few dozen out-peers
-
andrei_krx
Ok. I will make out-peers to 128.
-
andrei_krx
Should I adjust limit-rates or it is unnecessary?
-
andrei_krx
Any recommendations for config to increase peformance node in term of mining pool?
-
sech1
It must be running on a fast SSD and a fast internet connection
-
sech1
and connected to other pool nodes
-
sech1
and preferably run the latest release
-
andrei_krx
sech1: Thanks for your time!
-
andrei_krx
Is it possible to setup log-level by categories in monerod config file?
-
selsta
andrei_krx: yes
-
andrei_krx
I didn't find proper way. Except of url
127.0.0.1:38081/set_log_categories -d '{"categories": "*:INFO,net.p2p.msg:WARNING,net.p2p.traffic:WARNING,blockchain.db.lmdb:WARNING"}' -H 'Content-Type: application/json'
-
andrei_krx
But how to setup it using config file to make it permanently
-
moneromooo
I think something like: "log-level: 0,foo:WARNING,bar*:DEBUG"
-
moneromooo
Might need the space to go.
-
moneromooo
Or : to be = actually.
-
m-relay
<orion_midast:matrix.org> Hey, I am working on a mobile self custody service that will integrate seraidex. Is it fine if I tell my devs to ask here if they have question surrounding monero integration?
-
m-relay
<orion_midast:matrix.org> Hey, I am working on a mobile self custody service (BiorBank) that will integrate seraidex. Is it fine if I tell my devs to ask here if they have question surrounding monero integration?
-
m-relay
<orion_midast:matrix.org> or is there a better channel for this?
-
m-relay
<someoneelse495495:matrix.org> Hi, be aware that most developers are working on IRC and monero.social instance and we have federation issues with matrix.org. So you'll likely never see any answer from them if you stick on matrix.org (sadly).
-
m-relay
<someoneelse495495:matrix.org> If your question concern the usage of wrapper, integrations with a software in the ecosystem, #moner-community-dev is more likely to be the place. #monero-dev is only for core related development, you can preferably ask questions here when its related to the monero node or official wallet implementation
-
m-relay
<orion_midast:matrix.org> so where could my devs ask questions?
-
m-relay
<orion_midast:matrix.org> its for wallet creation we are making multi chain wallet, and monero uses 13 words meanwhile other chains use 12 words or something
-
m-relay
<someoneelse495495:matrix.org> #monero-community-dev I think
-
m-relay
<jeffro256:monero.social> recanman, are you talking about ed25519 in general or Monero specifically?
-
m-relay
<jeffro256:monero.social> Normally ed25519 signing uses the EdDSA algorithm:
en.wikipedia.org/wiki/EdDSA
-
m-relay
<orion_midast:matrix.org> can I get an invite?
-
m-relay
<jeffro256:monero.social> In Monero though, IIRC, we don't do this since we use ring signatures
-
m-relay
<orion_midast:matrix.org> Just checked its a dead chatroom
-
m-relay
<rucknium:monero.social> Goatskey: If you have questions, plenty of people can answer there. Maybe the Monero documentation is so good that few people need to ask questions ;)
-
m-relay
<someoneelse495495:matrix.org> Relayed from rucknium:monero.social: Goatskey If you have questions, plenty of people can answer there. Maybe the Monero documentation is so good that few people need to ask questions ;)