-
m-relay
<plaiwanone:matrix.org> Can I do e-begging here?
-
m-relay
<lucidlynx:envs.net> What’s e-begging?
-
m-relay
<321bob321:monero.social> oliver twist
-
m-relay
<mark:chat.nicecrew.digital> Does ebegging even works? Do people actually send money to random beggars?
-
m-relay
<mark:chat.nicecrew.digital> Please send me monero, my village needs a well, I'm poor and everyone died but me and I'm sick and a single dad
-
m-relay
<the.king45:matrix.org> 👇♦FREE 🎁 GIFT FOR THERE♦👇
-
m-relay
<the.king45:matrix.org> Come to my telegram group
-
m-relay
<the.king45:matrix.org> To make some money 💰
-
m-relay
<the.king45:matrix.org> Make money essay
-
m-relay
<the.king45:matrix.org> I promise you all 👉NO SCAM ❌
-
m-relay
<the.king45:matrix.org> NO PAYMENT FEES ❌
-
m-relay
<the.king45:matrix.org> I PROMISE YOU ALL 💟
-
m-relay
<the.king45:matrix.org> 👇JOIN OUR TELEGRAM GROUP 👇
-
m-relay
<the.king45:matrix.org>
t.me/+ioqje81ziAYyYTc0
-
m-relay
<the.king45:matrix.org>
t.me/+ioqje81ziAYyYTc0
-
m-relay
<the.king45:matrix.org> @everyone @everyone
-
m-relay
<lucidlynx:envs.net> Hold on why I get my tiniest violin 🎻
-
m-relay
<lucidlynx:envs.net> Hold on whilst I fetch my tiniest violin 🎻
-
m-relay
<shortcow:yatrix.org> Is it worth to send multiple transfers in one transaction? Will the fee be noticeably less than sending each transfer separately?
-
sech1
Yes, the fee will be smaller. 2in/16out transaction is 3.38 KiB, while 1in/2out transaction is 1.5 KiB. So you pay only 2.25x fee for 16 outputs instead of 2
-
m-relay
<mark:chat.nicecrew.digital> If you send the transaction in low priority (and you should), the transaction costs less than a cent, so most people don't care.
-
m-relay
<shortcow:yatrix.org> Thanks
-
m-relay
<eamonsms:matrix.org> Is there a business leader here looking to elevate their brand with tailored, efficient SMS marketing routing solutions? Let’s discuss how we can help you connect with your audience seamlessly and drive results through strategic messaging.
-
m-relay
<shortcow:yatrix.org> Is it ok to see `transaction_created` 3 time in log while creating 1 transaction?
-
m-relay
<shortcow:yatrix.org> Is it ok to see `transaction_created` 3 times in log while creating 1 transaction?
-
m-relay
<shortcow:yatrix.org> Im trying to figure out why transaction fails with `(double spend)` error
-
m-relay
<ofrnxmr:monero.social> Bcuz the node has already seen the tx(?). Either in txpool or already confirmed
-
m-relay
<shortcow:yatrix.org> There is no out transactions in `show_transfers` after rescan_bc hard.
-
m-relay
<shortcow:yatrix.org> Moreover, on one of the wallets I could not fix this error even after restoring from the seed phrase
-
m-relay
<shortcow:yatrix.org> `rescan_spent` also doesnt help
-
m-relay
<shortcow:yatrix.org> Same problem with this wallet. I've just restored it from seed and still cant send XMR
-
m-relay
<shortcow:yatrix.org> ok, fixed it with `flush_txpool`. But, honestly, it very strange behaviour. One failed transaction makes it impossible to use node at all.
-
m-relay
<rucknium:monero.social> shortcow: What network are you making these transactions? Mainnet? Public testnet? Private testnet? Is your node connected to the rest of the network? It looks like the tx was waiting to be mined. Of course a double spend will be rejected.
-
m-relay
<shortcow:yatrix.org> stagenet. yes, connected
-
m-relay
<rucknium:monero.social> Did you check a stagenet block explorer to see if the tx was broadcast to the rest of the network?
-
m-relay
<shortcow:yatrix.org> maybe it takes too long to mine block with my transaction...
-
m-relay
<rucknium:monero.social>
stagenet.xmrchain.net
-
m-relay
<rucknium:monero.social> How long did you wait? Two minutes between blocks on average, but it can take much longer occasionally since mining time is random
-
m-relay
<rucknium:monero.social> The Monero tx relay rules don't allow fee bumping by the way. BTC allows it by "replace by fee".
-
m-relay
<shortcow:yatrix.org> I watch it from time to time, but I didn't pay attention this time. I felt like I spent quite a while trying to solve this problem, well over 2 minutes. Next time I'll look at explorer more carefully
-
m-relay
<rucknium:monero.social> If you still have the ID of the tx that you flushed, you can check if it was eventually confirmed now
-
m-relay
<rucknium:monero.social> Just put it in the search box ^
-
m-relay
<shortcow:yatrix.org> It wasnt.
-
m-relay
<shortcow:yatrix.org> It wasnt
-
m-relay
<rucknium:monero.social> Probably it wasn't broadcast to the rest of the network from your node.
-
m-relay
<shortcow:yatrix.org> Maybe bad `tx-proxy` settings. Thanks
-
m-relay
<rucknium:monero.social> IIRC, there is a command to monerod that displays a summary of txs in the txpool and how many are "failing". You could have used that command to see if your tx was "failing". Failing usually means a double spend, which would mean that a previous tx that you broadcast, spending the same output, was already confirmed
-
m-relay
<shortcow:yatrix.org> Thank you
-
m-relay
<shortcow:yatrix.org> E Listed --anonymous-inbound without listing any --tx-proxy. The latter is necessary for sending local txes over anonymity networks
-
m-relay
<shortcow:yatrix.org> Why? What if i want allow anonymous relaying for others, but not for my own node?
-
m-relay
<shortcow:yatrix.org> Ok, probably because monerod dont know how to connect to tor/i2p
-
m-relay
<shortcow:yatrix.org> But what if i want allow anonymous relaying for others, but not for my own node?
-
m-relay
<rucknium:monero.social> ofrnxmr knows about that topic
-
m-relay
<ofrnxmr:xmr.mx> anonymous-inbound requires tx-proxy to relay your onion addr to peers
-
m-relay
<preland:monero.social> Back in the day, there was discussion to make tx-proxy not required when also using anonymous-inbound, but it was decided against because it allowed certain edge case scenarios to occur
-
m-relay
<preland:monero.social> Also, before I bite the bullet and have to start editing monerod—is it currently possible to make —bootstrap-daemon-address only auto select public nodes using I2P/Tor?
-
m-relay
<preland:monero.social> I’m pretty sure I know the answer, but I’m just making sure before I proceed
-
texxy
chat
-
texxy
how does xmr prevent replay attacks
-
m-relay
<elongated:matrix.org> Replay ?
-
m-relay
<jeffro256:monero.social> texxy: do you mean "double spends"?
-
m-relay
<rucknium:monero.social> When it hard forks? Usually (maybe always), Monero hard forks are also soft forks. Transactions are neither forward- nor backward-compatible.
-
texxy
basically the idea is
-
texxy
an attack intercepts a packet containing tx data
-
texxy
and just replays it to nodes
-
texxy
apparently xmr uses unique nonces and checks for uniqueness
-
m-relay
<jeffro256:monero.social> Why would that be an attack? That's basically how transaction propogation works: it touchs peer A, peer A tells all of its connections about the transaction, they tell their connections, so on and so forth
-
texxy
w8 i was reading this paper wrong
-
texxy
its an issue in account models because they use RPC
-
m-relay
<jeffro256:monero.social> Are you asking what prevents publishing a transaction once an RPC node has the already-signed transaction stored?
-
m-relay
<jeffro256:monero.social> If you wanted to delay it?
-
texxy
no i have realised it is not needed
-
m-relay
<plaiwanone:matrix.org> how2
-
texxy
what i do need to know is if there is a way to avoid ringct because it bloats the blockchain massively
-
m-relay
<ofrnxmr:xmr.mx> No....
-
texxy
it does
-
m-relay
<ofrnxmr:xmr.mx> Public-node doesnt broadcast onion addresses. Monerod isnt knowledgeable about onion or i2p rpc ....
-
m-relay
<ofrnxmr:xmr.mx> Texxy, my response was to preland
-
texxy
oh
-
texxy
well anyway
-
m-relay
<jeffro256:monero.social> texxy: there is no way to avoid RingCT. It is required since fork v6
-
texxy
im talking about new crypto i am making
-
m-relay
<ofrnxmr:xmr.mx> jeffro, you can use bitcoin
-
texxy
big issue with xmr imo is cost to run nodes
-
texxy
right now 16x what is necessary means we are wasting disk
-
texxy
same with stealth addresses
-
m-relay
<ofrnxmr:xmr.mx> how? Its cheaper than btc atm
-
m-relay
<jeffro256:monero.social> Run a pruned node
-
texxy
how do you prune properly?
-
m-relay
<plaiwanone:matrix.org> the sun set so
-
m-relay
<ofrnxmr:xmr.mx> run a pruned btc node*
-
texxy
btc can prune every spent output
-
texxy
xmr cant
-
m-relay
<preland:monero.social> *sigh* thanks for the heads up
-
texxy
so we need security that minimizes waste
-
m-relay
<jeffro256:monero.social> A pruned Monero node is one that stores 1/8 of the chain using a random "stripe"
-
texxy
yup
-
m-relay
<jeffro256:monero.social> It does full validation but only stores part of the data
-
texxy
except
-
m-relay
<ofrnxmr:xmr.mx> Now the question is: does bootsteap work AT ALL with tor/i2p. I dont think so. I2p client tunnels yes, but onion and b32, no
-
texxy
if everyone runs pruned xmr nodes, it slows network speed
-
texxy
and theres also 0 guarantee that everyone doesnt just remove the exact same 1/8
-
m-relay
<ofrnxmr:xmr.mx> No it doesnt
-
texxy
also compare 1/8 to the compression btc gets by removing all stxo
-
m-relay
<jeffro256:monero.social> Not necessarily in the best case, nodes broadcast stripe values so that could be coordinated to work everytime with hopping
-
m-relay
<jeffro256:monero.social> *without
-
texxy
if xmr is successful, most coins will be spent
-
m-relay
<ofrnxmr:xmr.mx> btc pruned nodes are centralization
-
m-relay
<ofrnxmr:xmr.mx> They all require full nodes
-
m-relay
<ofrnxmr:xmr.mx> Monero pruned nodes do not require full nodes
-
texxy
yet we cant efficiently get rid of all the inbetween where an output isnt being useful
-
m-relay
<ofrnxmr:xmr.mx> Each pruned node is in a group (stripe) and each group stores a different section of the blockchain
-
m-relay
<jeffro256:monero.social> Yeah if all BTC nodes removed stxo,s then your sync time would be infinite because no one would be storing the data lol
-
texxy
pruning can avoid centralization by just using super intense compression algorithmns
-
texxy
that way you have "hot" queries and "cold" queries in db
-
texxy
so any arbitrary node stores entire blockchain
-
m-relay
<ofrnxmr:xmr.mx> like bitcoin?
-
texxy
but it avoids super centralization
-
m-relay
<ofrnxmr:xmr.mx> oh wait, no. Bitcoin doesnt work like that
-
m-relay
<ofrnxmr:xmr.mx> texxy, please build this software
-
texxy
what software
-
m-relay
<ofrnxmr:xmr.mx> the prune juice blockchain
-
m-relay
<plaiwanone:matrix.org> This is Gundam
-
m-relay
<plaiwanone:matrix.org> he just keeps staring there
-
m-relay
<plaiwanone:matrix.org> about Buzz Lightyear
-
m-relay
<plaiwanone:matrix.org> "Scorpion"
-
m-relay
<eyeyush:matrix.org> anyone know someone who sell vps, for crypto?
-
texxy
should i make amazon but with crypto?
-
m-relay
<plaiwanone:matrix.org> uh huh
-
m-relay
-
m-relay
<plaiwanone:matrix.org> Coco
-
m-relay
<shortcow:yatrix.org> also i heard about incognet, but i dont now anything about it
-
m-relay
<crispycat:calitabby.net> i'm currently renting a vps from them and it's fine, however i have had a support ticket open for a couple weeks they have not responded to
-
m-relay
<shortcow:yatrix.org> also i heard about incognet, but i dont know anything about it
-
m-relay
<eyeyush:matrix.org> most are expensive
-
m-relay
<shortcow:yatrix.org> No
-
m-relay
<shortcow:yatrix.org> +- common prices
-
m-relay
<eyeyush:matrix.org> The topics are: software, decentralisation, crypto, web3
-
m-relay
<eyeyush:matrix.org> and philosophy, economics and its social, politcial and economical influence.
-
m-relay
-
m-relay
<eyeyush:matrix.org> the second issue is going to be entirely technical and better
-
m-relay
<eyeyush:matrix.org> 3. this is student run college magazine, so currently no ISSN
-
m-relay
<eyeyush:matrix.org> 4. we are in the process of designing the cypherpunk/privacy event vxcircle.org x.com/vxcircleorg around the magazine KALPA (peoplesklub.vxcircle.org) and the website will be build this week
-
m-relay
<eyeyush:matrix.org> anyone interested in submitting article?
-
m-relay
<preland:monero.social> I am cautiously optimistic
-
m-relay
<ofrnxmr:xmr.mx> Monerod doesnt know how to handle a b32 address without a proxy
-
m-relay
<ofrnxmr:xmr.mx> Also, tx-proxy seems to be bypassed when you have bootstrap enabled (probably a bug)
-
m-relay
<plaiwanone:matrix.org> brb
-
m-relay
<plaiwanone:matrix.org> anyone want a ramen?
-
m-relay
<preland:monero.social> Does this also make it impossible to add b32 addresses as peers manually?
-
m-relay
<preland:monero.social> That would explain why I was having issues with that on my testnet
-
m-relay
<ofrnxmr:xmr.mx> yes
-
m-relay
<ofrnxmr:xmr.mx> Monero isnt designed to allow onion or i2p blockchain sync peers
-
m-relay
<ofrnxmr:xmr.mx> It assumes all peers to be ipv4, or (if enabled) ipv6
-
m-relay
<ofrnxmr:xmr.mx> If you want to trick it.. use client tunnels
-
m-relay
<mmxxx:monero.social> seems like an oversight
-
m-relay
<preland:monero.social> I wonder why it was attempting to send stuff to the urls via the protocol anyways…..ughhh
-
m-relay
<plaiwanone:matrix.org> set
-
m-relay
<plaiwanone:matrix.org> sail
-
texxy1
bruh
-
texxy1
who hacked me
-
m-relay
<ofrnxmr:xmr.mx> Me
-
m-relay
<syntheticbird:monero.social> Mii
-
m-relay
<chaser:monero.social> I was able to compress a pruned node's lmdb directory to ~70% of its size, which seems surprisingly low. does anyone know where this redundancy is coming from?
-
m-relay
<syntheticbird:monero.social> excuse me what
-
m-relay
<syntheticbird:monero.social> how did you compressed it exactly?
-
m-relay
<chaser:monero.social> tar -cv "./lmdb" | lzip -9 -o "lmdb.tar.lz"
-
m-relay
<chaser:monero.social> I probably could have shaved a few more percentage points if I used xz
-
m-relay
<vytskalt:matrix.org> hi, i'm trying to run a monero node on my raspberry pi 5 (4gb ram model). I copied the lmdb directory with the blockchain already synced from another pc and when I run the node it just keeps endlessly repeating these logs and not doing anything:
-
m-relay
<vytskalt:matrix.org> ```
-
m-relay
<vytskalt:matrix.org> 2025-02-17 21:37:03.929 I Monero 'Fluorine Fermi' (v0.18.3.4-release)
-
m-relay
<vytskalt:matrix.org> 2025-02-17 21:37:03.930 I Moving from main() into the daemonize now.
-
m-relay
<vytskalt:matrix.org> 2025-02-17 21:37:03.930 I Initializing cryptonote protocol...
-
m-relay
<vytskalt:matrix.org> 2025-02-17 21:37:03.930 I Cryptonote protocol initialized OK
-
m-relay
<vytskalt:matrix.org> 2025-02-17 21:37:03.931 T Blockchain::Blockchain
-
m-relay
<vytskalt:matrix.org> 2025-02-17 21:37:03.931 I Initializing core...
-
m-relay
<vytskalt:matrix.org> 2025-02-17 21:37:03.931 T BlockchainLMDB::BlockchainLMDB
-
m-relay
<vytskalt:matrix.org> 2025-02-17 21:37:03.931 T BlockchainLMDB::get_db_name
-
m-relay
<vytskalt:matrix.org> 2025-02-17 21:37:03.931 I Loading blockchain from folder /home/monero/.bitmonero/lmdb ...
-
m-relay
<vytskalt:matrix.org> I'm using docker compose:
-
m-relay
<vytskalt:matrix.org> ```
-
m-relay
<vytskalt:matrix.org> monerod:
-
m-relay
<vytskalt:matrix.org> container_name: monerod
-
m-relay
<vytskalt:matrix.org> restart: unless-stopped
-
m-relay
<vytskalt:matrix.org> ports:
-
m-relay
<vytskalt:matrix.org> - "18080:18080"
-
m-relay
<vytskalt:matrix.org> - "18089:18089"
-
m-relay
<vytskalt:matrix.org> volumes:
-
m-relay
<vytskalt:matrix.org> - ./monero:/home/monero
-
m-relay
<vytskalt:matrix.org> image: ghcr.io/sethforprivacy/simple-monerod:v0.18.3.4
-
m-relay
<preland:monero.social> I had wanted to try that, but I didn’t think it would work *that* well….
-
m-relay
<preland:monero.social> How long did it take to zip that whole thing lol
-
m-relay
<chaser:monero.social> a long time. around 1.5 days.
-
m-relay
<preland:monero.social> Not surprising
-
m-relay
<ofrnxmr:xmr.mx> Do you have proper permissions for the folder?
-
m-relay
<ofrnxmr:xmr.mx> Also, log-level=4 is very high. Will usr a lot of storage very quickly
-
m-relay
<syntheticbird:monero.social> saying that log-level=4 piped into file is io bottle-necking is an understatement
-
m-relay
<syntheticbird:monero.social> a small VM ran out of RAM in 10 seconds because everything the console output was buffered in RAM
-
m-relay
<vytskalt:matrix.org> I think so. I created a docker container with a shell and was able to access the mounted lmdb folder fine
-
m-relay
<vytskalt:matrix.org> I know. I just wanted to see if there was anything else printed that could give me a clue what is going on.
-
m-relay
<ofrnxmr:xmr.mx> Did ypu try w/o copying the data-dir
-
m-relay
<vytskalt:matrix.org> Yes and it started syncing the chain from scratch
-
m-relay
<ofrnxmr:xmr.mx> Sounds like a problem with your copied datadir
-
m-relay
<vytskalt:matrix.org> I may have copied it while the node was still running
-
m-relay
<ofrnxmr:xmr.mx> compare permissions on the new dir and the copied one
-
m-relay
<ofrnxmr:xmr.mx> Thats probably not a good idea
-
m-relay
<vytskalt:matrix.org> i'll try copying it again with the node shut down then