-
m-relay
<jeffro256:monero.social> Your pool probably requires TLS
-
m-relay
<redhawk18:matrix.org> do you know of a pool that that I can just test with? It doesn't even have to be a real "pool" just something with the same schema for requests to know what I've wrote is correct.
-
m-relay
<jeffro256:monero.social> I'd maybe look into
github.com/jtgrassie/monero-pool
-
m-relay
<redhawk18:matrix.org> I did... thats the exact pool I was trying to connect to...
-
m-relay
<jeffro256:monero.social> Have you tried debugging the server side error messages ?
-
m-relay
<redhawk18:matrix.org> I haven't gotten anything back to really debug, my unit test I wrote for this just fails with a eof which means the websocket was hung up on. Maybe the hosted version of the pool you linked has tls or something, I'm not really sure.
-
m-relay
<redhawk18:matrix.org> Unless your saying I should built it myself to debug server messages?
-
m-relay
<jeffro256:monero.social> ^ Yes
-
m-relay
<jeffro256:monero.social> That will likely be more fruitful than only trying to debug client side
-
Guest56
is the 64-64-24k implementation in external\supercop\crypto-sign\ed25519 also possible in C/C++? There are many files using qhasm
-
Guest56
sech1 jberman?
-
m-relay
<vtnerd:monero.social> You could write c/c++, but you may want to ensure constant runtime to prevent private key leaks. For example, some of the assembly files touch every element in a table and use asm cmov instructions instead of branching to make the constant time guarantee. You could probably use the ref10 implementation as a guide on how to do this.
-
m-relay
<vtnerd:monero.social> Using simple indexes - which is the most straightforward forward to implement it - is not a direct port because of the constant time guarantee of the library. There is a valgrind plugin somewhere (I don't have link right now) that tries to validate whether a function is constant-time
-
Guest56
hmm
-
Guest56
I mean I would get something worse than the qhasm implementations but I wonder if I can still beat ref10
-
m-relay
<redhawk18:matrix.org> I've been working on getting that pool compiled but the pool requires the monero project to be compiled as well and I'm having issues with that I keep having problems with boost
-
m-relay
<redhawk18:matrix.org> ```bash
-
m-relay
<redhawk18:matrix.org> -- Using linker security hardening flags: -pie -Wl,-z,relro -Wl,-z,now -Wl,-z,noexecstack
-
m-relay
<redhawk18:matrix.org> CMake Error at /usr/share/cmake-3.29/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
-
m-relay
<redhawk18:matrix.org> Could NOT find Boost (missing: system filesystem thread date_time chrono
-
m-relay
<redhawk18:matrix.org> regex serialization program_options) (found suitable version "1.81.0",
-
m-relay
<redhawk18:matrix.org> minimum required is "1.58")
-
m-relay
<redhawk18:matrix.org> Call Stack (most recent call first):
-
m-relay
<redhawk18:matrix.org> /usr/share/cmake-3.29/Modules/FindPackageHandleStandardArgs.cmake:600 (_FPHSA_FAILURE_MESSAGE)
-
m-relay
<redhawk18:matrix.org> /usr/share/cmake-3.29/Modules/FindBoost.cmake:2393 (find_package_handle_standard_args)
-
m-relay
<redhawk18:matrix.org> CMakeLists.txt:1091 (find_package)
-
m-relay
<redhawk18:matrix.org> Is it too new?
-
m-relay
<jeffro256:monero.social> It looks like you might have multiple versions installed on your system
-
m-relay
<jeffro256:monero.social> The "found suitable version" is 1.81
-
m-relay
<jeffro256:monero.social> But your package manager shows 1.83
-
m-relay
<jeffro256:monero.social> Can you install all `system filesystem thread date_time chrono regex serialization program_options` for Boost version 1.81?
-
m-relay
<preland:monero.social> Oh no, I’ve seen this story before
-
m-relay
<fede:xmr.mx> no, no, no
-
m-relay
<fede:xmr.mx> pools don't support websocket
-
m-relay
<fede:xmr.mx> stratum as described here:
github.com/xmrig/xmrig-proxy/blob/master/doc/STRATUM.md is based on plain TCP
-
m-relay
<fede:xmr.mx> and the TCP traffic can be optionally encrypted with SSK
-
m-relay
<fede:xmr.mx> *SSL
-
m-relay
<fede:xmr.mx> it's not WebSocket
-
m-relay
<fede:xmr.mx> if you want to do XMR mining with a browser, you'll have to write and host your own WebSocket->TCP proxy
-
m-relay
<redhawk18:matrix.org> This is what I saw that made me think I had to use web sockets, someone brought up that on browser they had to be web sockets and I thought I could use those. Do I just send the requests over a normal http client?
-
m-relay
<fede:xmr.mx> if you aren't making an XMR browser miner, then just use TCP
-
CRTL_FAILURE
Are there any working attacks on ED25519?
-
m-relay
<redhawk18:matrix.org> Sorry I'm super new to lower level stuff so this is my first time learning all of this, so open a socket first and then somehow send a json through that?
-
selsta
.merge+ 9414
-
xmr-pr
Added
-
m-relay
<hardenedsteel:monero.social> is it possible to get block size from get_block_template? or am i looking to wrong place?
-
m-relay
<jeffro256:monero.social> like the block weight ?
-
m-relay
<hardenedsteel:monero.social> like the ``"expected_reward": 600000000000`` i would like to get or calculate the expected block size for the next block
-
m-relay
<hardenedsteel:monero.social> it would be useful for block explorers
-
sech1
It's calculated internally, but it's not passed through to get_block_template RPC
-
sech1
Look for "cumulative_weight" in Blockchain::create_block_template
-
m-relay
<hardenedsteel:monero.social> thanks, i will request feature for it, i dont know c++
-
m-relay
<hardenedsteel:monero.social>
monero-project/monero #9415
-
m-relay
<redhawk18:matrix.org> When waiting to read input from a pool how big should my buffer size be for my response? since everything is over a tcp socket and jsons are sent over the wire
-
m-relay
<redhawk18:matrix.org> When trying to reading responses from a pool how big should my buffer size be for my response? since everything is over a tcp socket and jsons are sent over the wire
-
sech1
XMRig uses 64 KB buffer, but you can probably get away with 1 KB buffer. Stratum responses are small.
-
m-relay
<redhawk18:matrix.org> why 64k if I can only use 1k?