-
BobSacmanto[m]
-
BobSacmanto[m]
Its a great fully open source wallet
-
eudaimon36[m]
Hey guys: trying to export transfers from my CLI wallet. Giving this command: export_transfers [all] [2766000 [2766900]] [output=~/Desktop] It outputs: Error: bad min_height parameter: [all]
-
eudaimon36[m]
seems to be ignoring the first option and thinking it is the second
-
ofrnxmr[m]
Error: bad min_height parameter: [all]
-
ofrnxmr[m]
Remove the brackets
-
utis
is it possible to timestamp a document by adding a hash of it to the monero blockchain with a minimal transaction? (how many arbitrary bytes can one get in in one transaction?)
-
sech1
omg we actually found someone needing tx_extra
-
moneromooo
Yes (cleartext payment ids are 256 bits, but obsolete), and max is a lot, technically, but discouraged. It also makes the tx stand out like a lighthouse.
-
ofrnxmr[m]
Sure its possible
-
ofrnxmr[m]
100kb iirc
-
hyc
he just wants to add the hash of the document, not the doc itself
-
hyc
even a 64bit integrated payment ID would be enough for some hashing purposes
-
sech1
256 bits should be enough, even using one of outputs (stealth address) for this could work
-
sech1
even without tx_extra
-
moneromooo
These have to be points though, so you can only stuff 252 bits or so IIRC. Close enough if you add some tooling though.
-
hyc
1-in/2-outs, could split to 128 bits per output
-
sech1
get 256-bit hash, convert it to point the same way Monero does, and use it
-
hyc
to zero-valued outputs, 1 input for fee.
-
sech1
this would require a dedicated script to check the document
-
hyc
two*
-
utis
sech1: what do you mean ``convert it to point . .''?
-
hyc
and there's still the rangeproof that can stash some data
-
sech1
I mean it's highly technical stuff and it will require wallet code modification
-
sech1
there's no simple way to stuff random data in a transaction in any Monero wallet
-
utis
so there's no easy way, then?
-
moneromooo
None that hides the data from observers.
-
utis
and you can't use the hash as the recipient address?
-
hyc
was hiding even a requirement?
-
moneromooo
For utis, it was not :)
-
sech1
there's no recipient address in a transaction, only stealth address
-
sech1
which you can use, but there are rules for it
-
utis
i want this hash publicly visible and preferable findable by some webtool, by someone who hasn't downloaded the blockchain
-
moneromooo
You could use that as a dest address, yes. Then you'd prove by releasing the secret keys, to prove the money was sent there.
-
moneromooo
There's also some format rules there, not all hashes will be valid secret keys, but close enough. Still requires non trivial code modifications.
-
hyc
why even bother to make it valid?
-
moneromooo
So you can make a tx to that address, which creates the proof.
-
moneromooo
Making it valid is just reduce32 though.
-
sech1
if you want a block explorer to show your document hash for a transaction, it must be either tx_extra, or a stealth address
-
sech1
tx_extra is easier but it will be probably removed in the future
-
sech1
moneromooo he could update the document until its 256-bit hash is a valid point, not needing a reduce :)
-
hyc
"it must be a steath address" - a block explorer isn't going to decode any of it.
-
sech1
it should take 16-50 tries at most
-
sech1
block explorer does show stealth addresses
-
moneromooo
Good point :D
-
hyc
any 256 bit number can be stuffed in there and would make no difference to the block explorer
-
sech1
if a stealth address itself is a hash... then it will work
-
moneromooo
If the document is editable though. Maybe you want to prove you saw an existing document at some time.
-
sech1
do nodes even verify stealth addresses before broadcasting and/or mining a transaction?
-
sech1
maybe you can just stuff anything there
-
moneromooo
I think they have to be points from some early-ish fork.
-
sech1
anyway, if it's not editable then you just need a special script to calculate this specific "hash" to make it valid
-
moneromooo
And convince verifiers you're not trying to pull the wool over their eyes with these odd suspicious steps.
-
hyc
I don't see what there is to verify. it'd be the same as burning coins.
-
moneromooo
Well, if you want to prove something, it kinda implies someone is gonna verify that proof.
-
hyc
if you simply want to prove "this document existed at this time" you don't need any txn proof
-
moneromooo
And if the steps aren't straightforward, you need to convince them the steps are sound.
-
moneromooo
Anyway, I think we've just taken the original problem and run with it for fun... 256 bit payment id is probably best here :D
-
hyc
they're still allowed?
-
moneromooo
Yes, anything is allowed. The wallet doesn't generate them anymore though.
-
utis
payment id == destination address? so if i send xmr to the hash, this will show up with a timestamp on exploremonero.com?
-
sech1
it's not destination address
-
sech1
but it does show up in block explorers
-
utis
sounds good
-
moneraut[m]
If you lookup an transaction on
xmrchain.net you see all the “ring members” why do some of those 16 ring members have 0 ring size ?
-
moneraut[m]
Bare with me, I am trying to learn more 😉
-
ofrnxmr[m]
Send a block hash or tx that has 0 rings
-
moneromooo
Probably that the tx creating that output had rings of that size. Can't recall whwther all rings have to have the same size atm, but most txes will have equal ring sizes.
-
moneromooo
0 would be coinbase txes, 16 would be run off the mill txes.
-
moneromooo
I expect old outputs will show 13, or even less.
-
moneromooo
0 is useful as a "dunno" or n/a value.
-
moneromooo
-
ofrnxmr[m]
Yeah, 0 ring size is coinbase outputs, a lot of which are p2pool these days.
-
ofrnxmr[m]
The most ive seen is 5 in a ring - the tx moo send has 5 of those in a ring
-
moneraut[m]
I got it, so its directly from the miner
-
ofrnxmr[m]
-
moneraut[m]
Those 0 ring size are coinbase outputs. I couldn’t find any information / reading on this.
-
ofrnxmr[m]
^
-
moneraut[m]
Thanks
-
moneromooo
FWIW, coinbase txes have no rings.