mariari

Results 137 issues of mariari

iex(mariari@Gensokyo)178> LogicProof.from_noun_plaintext(nullified_plain) :error iex(mariari@Gensokyo)179> nullified_plain 0 This is incorrect as the empty list is 0, and should be considered valid

bug
transparent RM

This ensure that even if the aura of the resource is lost, that they must be maintained as binary This may happen due to our jam and cue being faulty.

transparent RM

The aura around these values may be incorrect and be integers, thus we ensure they are binary. This may be paranoid of me, but when I compose transactions, this may...

transparent RM

Before it would convert deltas into the same number when it goes into Nock, however since the value can be negative, it requires some amount of tagging.

bug
transparent RM

This bug was introduced in: 96448e983760b09cde21f0d535352c91df12e297 However I'm basing it off of: f2b9ffd4e87ace88759ae0d75d6dbb2456865b2f because it introduces the negate/1 function. This bug can be seen in the following way: iex(mariari@Gensokyo)79> Map.merge(%{},...

bug
transparent RM

These newlines are needed for readability Either the action's commitments: MapSet.new([ ])does not match the proof's commitments:MapSet.new([ ])or the action's nullifiers:MapSet.new([])does not match the proof's nullifiers:MapSet.new([ ]) becomes: The following...

enhancement
transparent RM

customer: performer: deadline: estimated: started: actual: completed: confirmed: dependencies: - [ ] supersedes: - --- The flags for `Logging` is: ```elixir @type flag :: :info | :debug | :error ```...

enhancement
event

customer: @mariari performer: @mariari deadline: estimated: started: actual: completed: confirmed: dependencies: - [ ] supersedes: - --- All checks within the Transparent RM is done ```elixir def verify(tx = %Transaction{})...

transparent RM