TrasherDK : the cmake for monero-lws should be relaxed now

ZeroMQ chain subscription support was also added

vtnerd: Yes. cmake passes now :)

vtnerd: But "#error This file requires compiler and library support for the ISO C++ 2011 standard. This support must be enabled with the -std=c++11 or -std=gnu++11 compiler options."

Adding CXX_STANDARD=11 to cmake yields: "Manually-specified variables were not used by the project: CXX_STANDARD" but the build run a bit further before crashing.

[ 3%] Building CXX object src/CMakeFiles/monero-lws-common.dir/config.cpp.o

[ 6%] Building CXX object src/CMakeFiles/monero-lws-common.dir/error.cpp.o

.merges

seems like we can add 6613, 6760, 6761, 6762 6763 to the list ^

How about #6766 Is that one in already?

Hi there

need help with monero transaction building and broadcasting via python

I am getting 'cannot load unsigned_txset'

while I try to hit RPC endpoing `sign_transfer`

any idea where am I going wrong?

Would probably help if you post logs and/or the code somewhere

Hi there, I'm now able to go through the CLSAG signature part on Ledger's hardware wallet but I get an internal error at the end: "total_received < r.second.first". Could this be related to the algebra or something else?

Here is the patch applied to PR #6739: gist.github.com/grydz/dc34efb7e3cd6f91189bf27c2ce62b0b

It looks like it's the code that checks whether the tx does pay each of the intended recipients before sending it.

If it fails, it means your tx or the checking code is wrong.

It's a sanity check to avoid sending a tx which is known to not do what it was meant to do.

moneromooo: based on what grydz told me, the signature check should be failing (and perhaps generation as well, depending on sanity checks...)

Or at least, there was an algebra error in the Ledger CLSAG generation code when the error was seen

That's been fixed, but another algebra error could exist still

I'm going through the Ledger stuff as well, to see if this is the case

That's the outputs I think so that should not break if the input isgs are broken.

Hm ok, so the signature check was not performed

Which means it was incorrect, but this was not a source of the error

ok

At any rate, the algebra error was still there =p

moneromooo, what's the func name of this check?

sanity_check ?

The one in which this assert is. Am I missing your point ? :)

Got it ;)

how much of the stuff in cryptonote.org is relevant to monero as it is today?

like 20%

as i feared

.. is there a cryptonero.org ?

the actual p2p protocol perhaps

i.e. message formatting rules

let me try another angle

for some not-completely-beginner developer, is there some resource (besides the source code) where by reading, understanding and following along, eventually he'd be able to come up with a fully functional monero daemon?

what all the rules and concepts are etc

zero-to-monero?

would that be enough to implement the whole thing?

it's something i've wondered on and off for awhile, i don't really get how it works at lower levels. but for instance, if the rules have changed quite some times because of hardforks, doesn't that entire logic also have to be part of this hypothetical alternative implementation? actually when i phrase it like this the answer must be yes

Yes

i'm swimming a bit out of my depth here so if the questions seem confusing or unclear it's because i don't really know what i'm talking about

Zero to Monero is the closest thing to a protocol spec that exists

but even that doesn't try to fully address the state of consensus rules at each upgrade

It would be far easier to build something on a new chain that doesn't require the baggage of earlier protocol rules

should that stuff be documented? i imagine it would make the life of new programmers who'd like a stab at implementing the protocol much much easier

Go for it :D

But I hold little hope that such an effort would be maintained meticulously as things change

hah, need to understand a lot more about it

Can't hurt (unless it's documented wrong).

and what about the architecture of monerod

is that documented somewhere for developers?

(besides source code :p)

.merge+ 6613 6760 6761 6762 6763

.merges

I'll dig through them tonight once I wake back up again.

ty

.merge- 6111

Removed

^ until moo looked at the functional test p2p stuff