-
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
<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
<321bob321:monero.social> thanks mbll
-
m-relay
<321bob321:monero.social> ^
-
m-relay
<plaiwanone:matrix.org> nope
-
m-relay
<system> file $XMRBKK.pdf too big to download (7265711 > allowed size: 1000000)
-
m-relay
<plaiwanone:matrix.org> $XMRBKK.pdf
-
m-relay
<monerobull:monero.social> is this sus
-
m-relay
<monerobull:monero.social> this seems sus
-
m-relay
<monerobull:monero.social> explain what this is or ill ban for malware
-
m-relay
<monerobull:monero.social> it didnt open in the sandbox so i am suspicious
-
m-relay
<elongated:matrix.org> Delete then ask questions
-
m-relay
<plaiwanone:matrix.org> Sorry just a concept which isn't complete
-
m-relay
<fiatdemise:matrix.org> Great to see progress on multi recipient URI, looking forward to that!
monero-project/monero #9756
-
plowsof
FiatDemise not excited about @MoneroAfrica?
-
m-relay
<fiatdemise:matrix.org> You follow me on X? Nice
-
m-relay
<fiatdemise:matrix.org> Yeah, that guy is just latest in long string of scammers. Worst is psyman169, that guy just doesn't give up
-
midipoet
Just realised that Monero is #20 in the Halal cryptocurrency marketcap charts. keep up the good work people. (
coinranking.com/coins/halal)
-
m-relay
<monerobull:matrix.org> the fuck is this list
-
m-relay
<monerobull:matrix.org> how on earth are scams like XRP halal?
-
m-relay
<monerobull:matrix.org> doge is a dog meme, aren't dogs haram?
-
midipoet
monerobull: please moderate this blasphemy
-
midipoet
or we will all suffer the WRATH
-
m-relay
<monerobull:matrix.org> also wasnt beldex the "first halal certified" coin?
-
plowsof
mashallah-ero midipoet 🙏
-
m-relay
<syntheticbird:monero.social> lmfao
-
midipoet
does anybody recommend a specific API for historic prices/market caps (e.g., coinranking.com API or coinmarketcap.com API, etc), or are those two suitable enough? - research question, not explicit price talk
-
m-relay
<rucknium:monero.social> midipoet: What are your data needs? Which coins, how frequent, and how far back in time?
-
midipoet
Bitcoin, Monero, Firo, ZCash. probably 5Y timelines (as i understand it at the moment). also wondering if it is possible to filter by exchange and/or trading pair, which might also be beneficial. I am assuming that coinranking and coinmarketcap APIs provide this ability, but maybe they don't.
-
m-relay
<rucknium:monero.social> The aggregators will charge you for detailed historical data. You can try that, but I haven't yet. Kraken, which I've used, has maximum granularity for the coins it lists.
-
midipoet
that helps - thanks rucknium
-
m-relay
-
m-relay
<rucknium:monero.social> And one-minute granularity for candles is here:
support.kraken.com/hc/en-us/article…n-High-Low-Close-Volume-Trades-data
-
plowsof
ideally the .csv would be downloaded / parsed by scripts, iirc ive done this for monero with coinmarket caps csv
-
plowsof
(open,close,market cap) if you dont need the advanced stuff as above
-
m-relay
<rucknium:monero.social> midipoet: What are you using the data for, by the way?
-
m-relay
<ohchase:envs.net> Are these trades actual monero transactions? There's no way right. It's just them internally book keeping their reserve right?
-
m-relay
<elongated:matrix.org> every trade that happened on kraken
-
m-relay
<rucknium:monero.social> ohchase: AFAIK, all CEXes perform trades on their internal order book. No on-chain txs. On-chain txs are needed for deposits and withdrawals to/from user accounts, of course.
-
m-relay
<ohchase:envs.net> I guess for monero it's almost "good" they are not on chain. Also now I'm curious and this might be me still not understanding the whole monero functionality (working on it... just a complex project); but they're obviously sending valid transactions because my wallet running monerod from source detects the output all find and dandy, and they have the right and responsibility proba<clipped message>
-
m-relay
<ohchase:envs.net> bly to document that transaction. BUT, is there any way to check if they're creating their transactions like how monerod is? For example could an outside observer with no inside information of Kraken just watch the chain and go, oh yeah that's definitely a kraken withdraw
-
m-relay
<ofrnxmr:xmr.mx> Yes. They can stuff shit in tx-extra or use non-standard fees
-
m-relay
<ofrnxmr:xmr.mx> Some swappers do this, making it obvious when a swap is coming from their service
-
m-relay
<ohchase:envs.net> But that would be the CEX, i'm just saying as a total outside observer with no knowledge from the CEXs, go and do a couple withdraws and then kinda reverse engineer indicators?
-
m-relay
<ofrnxmr:xmr.mx> Even haveno atm uses elevated fees when the tx pool is empty. Those are a standard fee tier, but still differ from what everyone else is doing
-
m-relay
<ofrnxmr:xmr.mx> Not sure what youre asking
-
m-relay
<ohchase:envs.net> Maybe i don't know what i'm asking either lol
-
m-relay
<rucknium:monero.social> ohchase: Yes. This has been done before. If a CEX or other service uses nonstandard wallet code and makes a mistake (intentionally or not), then this can be done
-
m-relay
<ofrnxmr:xmr.mx> If standars fee is 20000/byte, and someone is using 15000 or 25000, then its obvious for any outside observer to see the difference
-
m-relay
<ofrnxmr:xmr.mx> Is a standard 1/2 tx is ~ 1.5kb, but someone is producing 1.6-1.7kb tx, that is also obvious
-
m-relay
<rucknium:monero.social> It has been done before for nonstandard code for user-facing wallets, too. **I** have done it.
-
m-relay
<rucknium:monero.social> On Exodus, for example.
-
m-relay
<rucknium:monero.social> MRL is trying to figure out ways to prevent these fingerprints from appearing
-
m-relay
<rucknium:monero.social> by making it impossible to relay a txs that is nonstandard
-
m-relay
<ohchase:envs.net> Interesting, so could be of value for traders to detect withdraws and maybe use that for pricing speculation
-
m-relay
<rucknium:monero.social> You don't have amounts public like with other coins, so it would be much less useful to traders than the exchange fingerprints on transparent coins' txs
-
m-relay
<ofrnxmr:xmr.mx> Imo node should drop/no-relay tx that are non standard
-
m-relay
<rucknium:monero.social> And it is much easier to figure out when those coins are coming from those CEXes because they are close to the exchange's known wallets on the transparent tx graph of transparent coins.
-
m-relay
<ofrnxmr:xmr.mx> Monero's fee algorithm is at the root of our scaling, using something else should be essentially "banned"
-
m-relay
<ofrnxmr:xmr.mx> Similar logic to not allowing someone to create non-16 ring tx
-
m-relay
<ohchase:envs.net> gotcha, im seeing now there is a desire to totally remove tx_extra. I was just getting into the community when I started reading about the whole reducing tx_extra size because it was decided that the nft stuff wasn't desired
-
m-relay
<ohchase:envs.net> gotcha, im seeing now there is a case/discussion to totally remove tx\_extra. I was just getting into the community when I started reading about the whole reducing tx\_extra size because it was decided that the nft stuff wasn't desired
-
m-relay
<ofrnxmr:xmr.mx> You could create 1/2 transactions that were 100kb. 3 of these takes up a whole block, and as decoys are obviously not the real spends
-
m-relay
<rucknium:monero.social> It's very hard, if not impossible, to prevent someone from embedding data deliberately in a tx even if tx_extra is removed. Basically, cryptographic signatures have free bytes you can insert data into.
-
m-relay
<rucknium:monero.social> But you can make it harder to accidentally create fingerprinted txs
-
m-relay
<ofrnxmr:xmr.mx> Yeah but you cant exceed the data thresholds of the expected data
-
m-relay
<ofrnxmr:xmr.mx> I'd prefer 1.5gb of steg > 1.5kb of tx + 98kb of jpeg
-
m-relay
<ofrnxmr:xmr.mx> Kb*